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-2018 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 276 2018-05-20 11:51:40
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-2018 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> PC-Alpine builds with LibreSSL and supports S/MIME.
185 <LI> NTLM authentication support with the ntlm library, in Unix systems.
186 Based on code provided by Maciej W. Rozycki.
188 <LI> Add -dict option to PC-Pico, which allows users to choose a dictionary
189 when spelling. Sample usage: -dict "en_US, de_DE, fr_FR".
191 <LI> Improvements to the configure stage of compilation. Some of
192 these contributed by Helmut Grohne. See
193 <A href="https://bugs.debian.org/876164">Bug 876164</A> in Debian.
195 <LI> Add "remove password" command to the management screen for the
196 password file encryption key. This allows users to use their password file
197 without entering a master password.
202 Bugs that have been addressed include:
204 <LI> Crash when attempting to bounce a message due to lack of space in
205 allocated space for key menu array. Reported by David Sewell.
207 <LI> Crash when a CA certificate failed to load, and user attempted to
208 view certificate information of other certificate authorities.
210 <LI> Deactivate some color code from Pico (as standalone editor in the
211 windows version) until I find a way to activate it again. This is
212 not critical and it is not something that PC-Pico must have (some
213 of it already exists in other ways, like color support, what does
214 not exist is the more complex code that Unix-Pico has with color
215 codes for specific colors.)
217 <LI> Update build.bat file to add /DWINVER=0x0501 so that Alpine can
218 build when using Visual Studio 2017. Fix contributed by
219 Ulf-Dietrich Braunmann.
221 <LI> When the locale is not set up to UTF-8, alpine might determine the
222 width of a character incorrectly. Reported by Alexandre Fedotov.
224 <LI> When colors are edited from the main setup configuration screen, some
225 color settings are not updated until Alpine is restarted. Reported by
228 <LI> If the first part of a message is multipart/alternative, and the
229 first part of this is also a multipart type, then Alpine might
230 fail to select the first text part when replying to a message.
231 Reported by Lucio Chiappetti.
233 <LI> TLS 1.2 works does not work if Alpine is compiled with openssl >= 1.1.0.
234 Reported and patched by Kyle George.
236 <LI> If the directory where Alpine saves the certificates if empty,
237 alpine would not create a self-signed certificate to encrypt the
240 <LI> S/MIME: The list of public certificates is freed before it is
241 reused when a signature fails to verify. This causes Alpine to
242 crash. Patch submitted by Linus Torvalds.
244 <LI> S/MIME: A message could fail to verify its signature even if the
245 certificate was saved when the message was open. Based on a report
246 by David Woodhouse to the RedHat bugzilla system.
250 Version 2.21 addresses bugs found in previous releases and has several
256 <LI> PC-Alpine: New configuration option "Aspell Dictionaries" allows a
257 user to choose the dictionary used to spell check, in case the user
258 communicates in more than one language. Examples of values for the
259 variable are "en_US" or "de_DE", etc. Only the first 10
260 dictionaries are offered.
262 <LI> Unix-Alpine: Connect securely to a LDAP server on a secure port.
263 Based on a contribution by Wang Kang.
265 <LI> Colors configured in Alpine are inherited in the composer.
267 <LI> When Alpine is compiled with password file and SMIME support
268 the password file is encrypted using a private key/public
269 certificate pair. If one such pair cannot be found, one will be
270 created. <A HREF="h_password_file_support">Learn more</A>.
272 <LI> Alpine builds with any version of OpenSSL greater than or equal
273 to 1.0.0c. This includes version 1.1.0. Alpine also builds with
276 <LI> New SHORTSUBJECT, SHORTSUBJKEY and SHORTSUBJKEYINIT token for index
277 format, which removes text in the SUBJECT between "[" and
280 <LI> New SMARTTIME24 token for index screen. It is close to SMARTDATETIME
281 but it differns in that it gives the time in which the message was
282 sent for messages that are less than a week old. it uses a 24 hour
285 <LI> Alpine will include attachments when forwarding some
286 multipart/alternative messages for which it did not use to include
289 <LI> New configuration option
290 <a href="h_config_alt_reply_menu"><!--#echo var="FEAT_alternate-reply-menu"--></a>
291 which adds more ways to control features and variables when you
292 start to reply to a message.
294 <LI> Added support for RFC 2971 - IMAP ID extension.
296 <LI> Add configuration <A href="h_config_ignore_size"><!--#echo var="FEAT_ignore-size-changes"--></A>
297 that allows users to ignore errors in the computation of the size
298 of a message from defective servers.
300 <LI> SMIME: Upgrade the default signature digest from sha1 to sha-256, since
301 clients such as Thunderbird do not validate signatures that use sha1 digest.
303 <LI> Add the configuration variable "default-directories", which is called
304 <A href="h_config_history"><!--#echo var="VAR_default-directories"--></A>
305 variable saves a list of directories that are readily accessible
306 for save or export of attachments. This makes it easier to save
307 attachments in directories that are hard to navigate to, or that
308 are accessed frequently.
310 <LI> When a filename is attached and its name is encoded, the save
311 attachment command will offer to save the file in the encoded form.
312 This might work for some users, but the save command will have a
313 subcommand ^N to decode the file name and save the file with the
316 <LI> The TAB key allows autocomplete in the Fcc field in the composer headers,
317 as well as autocompletes automatically when only one possibility exists
318 for the ^J attach command.
320 <LI> Add support for the "TYPE" and "VALUE" attributes of
323 <LI> Ignore message from smtp server after a successful authentication
326 <LI> When a message is saved in the Form Letter folder, add the ability
327 to save the role being used to compose such message so that settings
328 such as the SMTP server set in the role can be used when sending
329 such form message. Suggested and patched by Frank Doepper.
331 <LI> If SSLDIR is defined somehow, do not disable S/MIME if the
332 SSLCERTSDIR is not found.
334 <LI> When Alpine sends an attachment, it will set the boundary attribute
335 in lower case, as some SMTP servers, such as those of libero.it
336 reject messages if the boundary attribute is in uppercase.
338 <LI> Add the ability to change the private key and certificates used
339 to encrypt a password file in the SMIME setup configuration screen.
340 <A HREF="h_config_smime_password_file_certificates">Learn more</A>
342 <LI> SMIME: The ctrl-E command that gives information on the certificate
343 is only available for messages that have a signed or encrypted
346 <LI> SMIME: If a message contains a RFC822 attachment that is
347 signed/decrypted add the ability to view its SMIME information.
349 <LI> SMIME: Certificate information in the S/MIME screen is available
350 for certificates stored in a container.
352 <LI> SMIME: Offer the common name of the person, instead of the name of
353 file containing the certificate, as the name to be displayed in the
354 certificate management screen for certificate authorities.
355 Suggested by Matthias Rieber.
357 <LI> SMIME: Management of several alternate name (SAN) certificates is
358 improved. When importing a SAN certificate, also import a certificate
359 for the filename, besides for the e-mail addresses in the
360 certificate. Suggested by Matthias Rieber.
362 <LI> SMIME: add full year when displaying information about a certificate
363 in the certificate management screen. Suggested by Matthias Rieber.
365 <LI> SMIME: sort certificates by some type of alphabetical order in the
368 <LI> SMIME: Alpine will ask users if they wish to save S/MIME
369 certificates included in signatures, when the option "Validate
370 Using Certificate Store Only" is enabled. If the user does not wish
371 to save it, validation will fail.
373 <LI> HTML: Add support for decoding entities in hexadecimal notation.
374 Suggested by Tulipánt Gergely.
376 <LI> The "#" command, when used as part of an aggregate
377 operation will allow users to select the role used in either
378 replying, forwarding or replying to the group of selected messages,
379 Suggested by Hisashi T Fujinaka.
381 <LI> If the charset of a message can not be determined, use the value set
382 in the <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A> for its value.
384 <LI> Resizing setup screen will redraw screen.
386 <LI> Unix Alpine only. Experimental: If Alpine/Pico finds a UCS4 code
387 in the width ambiguous zone, it will use other means to determine
388 the width, such as call wcwidth.
390 <LI> Pico: Code reorganization in the search command to make it easier to
391 add subcommands of the search command.
393 <LI> Pico: Search command can do a case sensitive match. Use the Ctrl-^
394 subcommand of the search command to bring this choice into view.
396 <LI> Pico: Add the ability to search for strings in the beginning or end
397 of a line. Use the Ctrl-^ subcommand of the search command to bring
398 this choice into view.
400 <LI> For a multipart/alternative message, the Take Address command will
401 work on the part that is being read.
403 <LI> When sending a message, allow for 512 characters of consecutive
404 non-white space before folding the subject line.
406 <LI> Make sure titlebar (the line at the top of the screen) always
407 contains the name of the folder/newsgroup that is open, if this
410 <LI> The feature <a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
411 will also scramble the name, version and operating system in the
412 message-id header. Based on a contribution by Dennis Davis, which
413 is itself based on a contribution by Mark Hills.
415 <LI> Change in logic in imap_set_password function to make Alpine ask if
416 a user wants to save a password before reading the password file.
418 <LI> When exporting all parts of a message, if two attachments have the same
419 name, do not overwrite a file more than once, but instead add a counter
420 number to the filename to make a new file that does not exist in the file
423 <LI> Add the Control-R subcommand to the save command for attachments.
424 This subcommand toggles if the saving will be done in binary mode
425 for text attachments. When a user saves an attachment using binary
426 mode it will be saved as it was sent, otherwise the attachment will
427 be transformed to UTF-8 for further transformation through internal
428 and user defined filters for saving.
430 <LI> Add command line argument -smimedir, which allows to specify
431 the default path for a directory that contains the public, private,
432 and ca directories. This is useful in case a user has a backup of
433 old certificates that cannot be installed in the ~/.alpine-smime
436 <LI> Reimplementation of the code that allows the .pinerc file to be a
437 symbolic link by Kyle George from tcpsoft.com to use realpath.
439 <LI> When saving an attachment, the "^T" command leads to a screen where the
440 "A" command can be used to add a file. A directory can be added by
441 pressing "^X" after the "A" command. Added after a suggestion by
444 <LI> When saving an attachment, the ^Y and ^V commands allow a user to
445 scroll through the history of directories used to save attachments,
446 while preserving the given name of the file. Suggested by Peter
449 <LI> SMIME: Turn off automatic signing and encrypting of a message when
450 bouncing. Suggested after a discussion with Matthias Rieber.
452 <LI> When messages are selected, warn the user if a message that is not
453 selected will be bounced, or if not all selected messages will be
454 bounced. Suggested by Ulf-Dietrich Braumann.
456 <LI> The bounce command adds a subcommand to choose a role.
458 <LI> When selecting messages by number, the "." character can
459 be used to specify the message on which the cursor is on.
461 <LI> When Alpine opens an attachment, it sometimes changes the extension
462 of the file that is being opened and replaces it by another for the
463 same mime type. If Alpine finds that the extension of the file
464 corresponds with the mime type, according to the mime-types file,
465 then it will keep it, and no substitution will be made.
467 <LI> Set no restrictions on the length of encoded subjects, but encode
468 words in length of no more than 75 characters.
473 Bugs that have been addressed include:
475 <LI> SMIME: Crash when a certificate has an invalid date of validity. Also
476 Alpine will use the function ASN1_TIME_print to determine the date
477 of validity. Reported by Ben Stienstra.
479 <LI> SMIME: Crash when attempting to unlock the password file and an
480 incorrect password is entered.
482 <LI> SMIME: Crash when checking the signature of a message that contains
483 a RFC822 attached message. Reported by Holger Trapp and Björn
486 <LI> SMIME: Cancelling entering password to unlock key will not reprompt.
488 <LI> SMIME: fix a bug that did not allow users to transfer certificates to
489 remote containers. Reported by Matthias Rieber.
491 <LI> SMIME: certificates included in messages were not being transferred
492 to a remote container.
494 <LI> SMIME: Crash if public certificates are located in an inaccessible
495 remote server and the private key is not available.
497 <LI> SMIME: Alpine does not remove temporary files created when adding a
498 CA certificate to a container. Reported by Holger Trapp.
500 <LI> SMIME: When reading a local certificate, Alpine converts the name
501 of the certificate to lowercase, which may make Alpine not be able
502 to read such certificate. Reported by Dennis Davis.
504 <LI> SMIME: If the option "Remember S/MIME Passphrase" is disabled, then
505 entering a password to read an encrypted message will make Alpine
506 forget the key and not ask the password to unlock it again in case
507 it is necessary to unlock it again. Reported by Ulf-Dietrich
510 <LI> Alpine would use freed memory while trying to compute the color
511 of the titlebar. This happened when trying to continue a postponed
514 <LI> Alpine failed to read an encrypted password file if too many
515 passwords were saved in the password file.
517 <LI> When selecting messages while in Threaded Index Screen, some
518 messages other than top of threads could appear in the index, making
519 Alpine display messages "out of the screen."
521 <LI> The index format would be chopped at the position of an unrecognized
522 token, instead of skipping the token as intended.
524 <LI> Work in progress: Avoid calling non-safe functions when Alpine
525 receives a signal. See bug report
526 <A HREF="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825772">here.</A>
528 <LI> Crash when attempting to read a message after a bounce command.
529 In order to produce a crash one needed to use the ^T subcommand and
530 do a search in a LDAP directory. The crash is produced by changes
531 to the text in the title bar. Reported by Heinrich Mislik in the
534 <LI> HTML messages that contain UTF-8 may wrap at the wrong position,
535 making Alpine not display the correct character at the position
536 that wrapping is done. Reported by Wang Kang.
538 <LI> Pico: Searching for a string that is too long causes Pico to crash
541 <LI> Fix vulnerability in regex library. This only affects those who use
542 this library, such as the windows version of Alpine. See
543 <A HREF="http://www.kb.cert.org/vuls/id/695940">http://www.kb.cert.org/vuls/id/695940</A>
546 <LI> Alpine would not set include and lib paths for OpenSSL if this was
547 installed in /usr/local/ssl.
549 <LI> If the .pinerc file is a symbolic link, Alpine might not write its
550 contents when saving its configuration.
552 <LI> The _INIT_ token does not skip over non-alphanumeric characters in
553 the name. Reported by Andreas Fehr.
555 <LI> When opening an INBOX folder in a context different from the
556 incoming folders collection, from the command line, Alpine would
557 open the INBOX folder from the incoming folders collection.
559 <LI> Mismatch in size of UCS and CELL caused a corruption in the
560 content of a pointer, which made the speller in PC-Alpine get the
561 content of a word incorrectly.
563 <LI> Skip testing openssl compatibility version when cross-compilation
564 is detected. Fix contributed by Antti Seppälä
566 <LI> Alpine fails to remove temporary files used during a display or sending
567 filter. Fix contributed by Phil Brooke.
569 <LI> When the index is in zoomed state, adding new messages to the
570 selection would not show those messages if those messages are on
571 top of the current message in the top of the screen. Reported by
572 Ulf-Dietrich Braumann. In addition, when the user scrolls through
573 the index, this scroll smoothly, without jumping pages. Reported
576 <LI> Crash when reviewing history of saving attachments.
578 <LI> Crash when canceling a goto command on a local collection that has
579 not been expanded and attempting to expand such collection.
581 <LI> Crash in Pico when forwarding messages that contain a direction mark
582 at the end of a line. Reported by James Mingo.
584 <LI> Solve compilation errors when Alpine is built with Visual Studio 2015.
589 Version 2.20 addresses bugs found in previous releases and has several
597 <LI> Upgrade UW-IMAP to Panda IMAP from
598 <A HREF="https://github.com/jonabbey/panda-imap">https://github.com/jonabbey/panda-imap</A>.
599 <LI> S/MIME: Add screen to manage certificates.
600 <LI> S/MIME: Signatures are validated using the user's certificates instead
601 of the ones included in the message. Behavior can be disabled by
602 disabling the option <A href="h_config_smime_use_cert_store">
603 <!--#echo var="FEAT_smime-use-storey-only"--></A>, which is enabled
605 <LI> S/MIME: sign messages using intermediate certificates when needed
607 <LI> S/MIME: validation of certificates for servers that modify signed
609 <LI> S/MIME: signed and encrypted messages will be signed first and
610 encrypted second, so that they can be decoded by other clients.
611 <LI> S/MIME: add the sender certificate to the list of certificates in
612 encrypted messages to make it possible for the sender to decrypt
613 the message they sent.
614 <LI> S/MIME: When transferring certificates to a local container, create
615 container with default names PublicContainer, PrivateContainer and
616 CAContainer, as appropriate for these files, unless the user has
617 provided some other names.
618 <LI> S/MIME: Forwarding a message will include the signed part as part
619 of the text and not as a multipart message, just as the reply
621 <LI> HTML: Style tag in body of html message causes Alpine to not write
622 its content until a new </style>
623 <LI> HTML: <BR>, <BR />, and <BR/> are considered
624 the same inline tag; the same is valid for the <HR> tag.
625 <LI> Add support to selective expunge through a subcommand of the
626 select-apply commands. Read more in the <A
627 HREF="h_index_cmd_expunge">help</A> for the expunge command.
628 <LI> Pico: New subcommand of the search command, allows to reverse the
630 <LI> Unix Alpine: If a password file is defined, and S/MIME is enabled,
631 the key and certificate used to encrypt the password file are saved
632 in the ~/.alpine-smime/.pwd directory, or in the directory specified
633 by the -pwdcertdir command line option.
634 <A HREF="h_password_file_support">Learn more</A>.
635 <LI> Add /tls1, /tls1_1, /tls1_2 and /dtls1 to the definition of a
636 server to use different ways to connect using ssl, for
637 example {server.com/tls1} will attempt to connect to
638 server.com at the ssl imap port (port 993) and establish a
639 connection using TLSv1. These flags can be used in
640 conjunction with the /ssl flag, the ssl flag is redundant.
641 Conversely, however, the /ssl flag does not imply any of
642 these flags; the /ssl flag means SSLv3 or, if not available,
643 SSLv2 in the SSL port.
644 <LI> Alpine does not attempt to automatically reopen a collection
645 that was not opened due to cancellation by the user.
646 Instead, the user must try to open it explicitly.
647 <LI> Alpine searches for a certificate that matches an email address in
648 all addresses in a certificate (instead of just the first
649 one) but when it tries to unlock the certificate, it asks
650 for the password for the first email address in that
652 <LI> Style tag in body of html message causes Alpine to not write its content
653 until a new </style>
654 <LI> Experimental: Write the content-type of a message in
655 lowercase, as some non-compliant servers do not understand
656 uppercase content-type, such as those of GMX.de.
657 <LI> Experimental: Do not send the RSET command before attempting
658 to send a message, as this causes a delay in some evily managed
660 <LI> Opening a folder updates recent count in maildrops (this
661 already works for other types of folders)
662 <LI> Automatically redraw screen after opening an attachment
663 instead of simply clearing it.
664 <LI> Pico: Justification works without need of a predefined quote
665 string. This allows justification of blocks of text that are
666 indented with spaces.
667 <LI> Decode the name of attachment names, so they can be written as part
668 of the description of the part.
669 <LI> Check bounds and tie strings off to improve security. Contributed
671 <LI> Replace tabs by spaces in From and Subject fields to control for
672 size in screen of these fields. Change only in index screen display.
673 <LI> Aggregate operations allows bouncing a list of messages using a role.
674 Suggested by Ulf-Dietrich Braumann.
675 <LI> Disable saving new passwords to the password file. Implemented
676 by Louis Raphael from dpslabs.com. <A HREF="h_config_disable_password_file_saving">Learn more.</A>
677 <LI> Makefile: Add $(LIBINTL) to the flags to link rpdump, rpload,
678 alpined and alpineldap because MAC OSX 10.8 x86_64 needs it. Reported by
684 Bugs that have been addressed include:
686 <LI> Fix _INIT_ token for reply quote string to include support for 8-bit
687 in personal names. Reported by Lev Gorenstein.
688 <LI> When writing the .pinerc file, lines were truncated if they were longer
689 than 10,000 characters. This could cause data corruption, so now lines
690 are allowed to be of any length.
691 <LI> In Unix Alpine (but not in MAC OSX) fix a problem that made Alpine
692 remove attachments before they were open by a mailcap viewer. It
693 requires that the user has an equivalent to a command such as "ps
694 auxww" to list the list of processes, and check if there is any
695 program using the attachment. The default is "/bin/ps auxww", but
696 it can be changed at compile time with the option --with-ps-cmd.
697 See the help of the variable
698 <a href="h_config_psleep"><!--#echo var="VAR_mailcap-check-interval"--></a>
699 for more information.
700 <LI> S/MIME: signed messages that contained an attachment would not validate.
701 <LI> S/MIME: signed and encrypted messages from Thunderbird would not
702 validate. Thanks to Andreas Schamanek for testing, debugging and
703 advising during the process of fixing this problem.
704 <LI> S/MIME: Forwarding messages with multipart content-type failed to be signed
705 with "Error writing pipe" message. Reported by Andreas Schamanek
707 <LI> S/MIME: Certificates are lost when using a pinerc file outside of the
709 <LI> S/MIME: Accessing the S/MIME configuration screen would deinitialize
710 SMIME making it not possible to sign or encrypt messages.
711 <LI> S/MIME: Forwarding a signed message might make the body contain mime
712 information that is not part of the body, and hence making the body
713 of the message seem wrong.
714 <LI> S/MIME Alpine would compute incorrectly the signature of a message
715 that contains 8bit if the option "Enable 8bit ESMTP Negotiation" is
716 enabled, the message contains 8bit characters and the smtp server
717 supports 8bit sending.
718 <LI> When replying to several messages, subject will be decoded first,
719 and then stripped from re/fwd before they are compared to determine
720 the subject of the replied message.
721 <LI> Crash when tcp connection to NNTP server was lost after connection
722 had been established, but lost immediately afterwards.
723 <LI> Crash with message "lock when already locked", when painting
724 an index was based on scores that needed information from a remote
725 addressbook in the same server as the folder opened. Reported by
727 <LI> Crash in message/rfc822 attachments encoded in base64.
728 <LI> Postponed messages whose content-type is text/html, text/enriched and
729 text/richtext are sent with that content-type, even though, after
730 resuming composition, Alpine had changed its type to text/plain.
731 <LI> Alpine cannot handle correctly some characters in the Windows-1256
732 character set, which might lead to a crash or a corruption in the
733 screen. Work was done to contain the bug. A more complete fix will
734 be done in a future release. Reported by Professor Robert Funnell.
735 <LI> WebAlpine: add _GNU_SOURCE to make pubcookie build.
736 <LI> WebAlpine: fail to build with debug disabled. Fix from Sam Hathaway.
737 <LI> Save command did not warn of existence of a message with a deleted
738 attachment in an aggregate save, unless cursor was positioned on a message
739 with a deleted attachment. Reported by Florian Herzig.
740 <LI> Transformation of UTF-8 to MUTF7 was not being done when creating a folder
742 <LI> DATE tokens were not internally transformed to UTF-8, which made their
743 values not appear complete in the screen. Reported by Werner Scheinast.
744 <LI> Fixes to configure script so that it will not require PAM for every system.
745 <LI> Fix to configure script so that it will use CPPFLAGS instead of
746 CPPCFLAGS, and so the --with-ssl-include-dir option take effect
747 during the build. Fix by Ulf-Dietrich Braumann.
748 <LI> Fix in WebAlpine: do not use deprecated dereference in pointer,
749 needs to use tcl_getstringresult() instead. Reported by
750 Ulf-Dietrich Braumann.
751 <LI> Quoted string in URL Viewers configuration variable were not
752 unquoted before passing to viewer.
753 <LI> Fix in configure script to detect location of tcl library; add
754 /usr/local in FreeBSD and fix a bug in configure script that used
755 $alpine_TCLINC instead of $alpine_TCLINC/tcl.h. Reported and fixed
757 <LI> Move SSL configurations from UW-IMAP to configure script, and
758 update OpenSSL configuration for Mac OS X.
759 <LI> Remove -lregex from linker flags when building --with-supplied-regex.
760 <LI> When the download of an attachment is interrumpted, Alpine stills
761 caches what was downloaded, making the download incomplete for
762 subsequent calls of Alpine attempting to open the attachment. In the
763 future, Alpine will not cache any downloaded part of the attachment
764 when it is interrupted.
770 Version 2.11 addresses bugs found in previous releases and has a few
778 <LI> Alpine requires version 1.0.0c of Openssl to build.
779 <LI> Increase encryption of S/MIME encrypted messages.
780 <LI> Pico: Improvements in justification of paragraphs: lines that begin
781 with a quote string, followed by a space were considered individual paragraphs,
782 now they are considered part of a paragraph. Based on earlier joint work
784 <LI> Unix Alpine: Allow local .pinerc file to be a symbolic link.
785 <LI> Experimental extended support of recognition of UTF-8 in urls based on
786 information from <A HREF="http://url.spec.whatwg.org">http://url.spec.whatwg.org</A>.
787 <LI> Added recognition of ws and wss URIs.
788 <LI> Add ability to <A HREF="h_config_folder_color">color folder names</A>,
789 <A HREF="h_config_directory_color">directory names</A>,
790 and <A HREF="h_config_folder_list_color">text</A> in the FOLDER SCREEN.
791 <LI> Add the ability to <A HREF="h_config_indextoken_color">color any token</A>
792 used in the display of the INDEX SCREEN.
793 <LI> New option <A HREF="h_config_preserve_field"><!--#echo var="FEAT_preserve-original-fields"--></A>
794 that adds the ability to preserve To: and Cc: fields when replying to a
795 message, as specified by original sender.
796 <LI> Add a _SILENT_ token to the <A HREF="h_config_display_filters">list of tokens</A>
797 for a display filter, so that Alpine will not redraw the screen when it is unnecessary.
798 <LI> Quota command includes subcommands for printing, forwarding, etc.
802 Bugs that have been addressed include:
805 <LI> Crash when a non-compliant SMTP server closes a connection without a QUIT command.
806 <LI> Crash when resizing the screen in a configuration screen.
807 <LI> Do not bail out during a tcp timeout, instead close connection and avoid crash.
808 <LI> Do not use a shell to open a browser.
809 <LI> Configure script did not test for crypto or pam libraries.
810 <LI> Configure script attempted to build web component, even if header file tcl.h was not present.
811 <LI> Change Cygwin directory separator to "/".
812 <LI> Alpine could set List- headers, contrary to RFC 2369.
816 Version 2.10 addresses bugs found in previous releases and has a few
824 <LI> Quota report for IMAP folders that support it (press the "@" command in the index screen of such folder).
825 <LI> Search a folder for the content of any header with the ";" command.
826 <LI> Foreign characters are decoded correctly in IMAP folder names.
827 <LI> Question about breaking connection to slow servers includes their name.
828 <LI> Internal x-alpine-help: resource locator for sending links to internal help.
829 <LI> OpenSuse: Alpine find location of OpenSSL certificates.
830 <LI> Cygwin: Alpine builds without need of patch.
831 <LI> Recognition of proper mime type for docx, xlsx, and pptx files.
832 <LI> When composing a message, Alpine will create a new thread when the subject is erased.
833 <LI> Add support for strong encryption of password file when S/MIME is built in.
837 Bugs that have been addressed include:
841 <LI> Alpine will close a folder after confirming with user their intention and not reopen it.
842 <LI> Double allocation of memory in Pico.
843 <LI> Alpine does not give warning of message sent and posted upon receipt by email of message posted in newsgroup.
844 <LI> Handling of STYLE html parameter may make Alpine not display the content of a message.
845 <LI> Not recognition of environment variables in some options.
846 <LI> Not display of login prompt during initial keystrokes.
847 <LI> justification of long urls breaks them.
848 <LI> Incorrect New Mail message when envelope is not available.
849 <LI> Incorrect display of PREFDATE, PREFDATETIME and PREFTIME tokens.
850 <LI> Crash when resizing the screen after display of LDAP search.
851 <LI> Crash when redrawing screen while opening a remote folder collection.
852 <LI> Infinite loop in scrolltool function during notification of new mail.
853 <LI> No repaint of the screen after midnight was done when the SMARTDATE token is used in the index screen.
854 <LI> No display of signed and encrypted S/MIME messages.
855 <LI> Alpine will not build with OpenSSL.
856 <LI> Crash for double locking in calls to c-client.
857 <LI> Bad recognition of mime-encoded text may make Alpine not print the subject of a message.
858 <LI> Ignore the references header when threading messages
859 <LI> No update of colors in index screen after update to addressbook.
863 Version 2.01 addresses bugs found in previous releases and has a few
871 <LI> Fixed non-ASCII web alpine handling
872 <LI> Added web alpine help.
873 <LI> Allow web alpine inbox on second IMAP server.
874 <LI> Allow web alpine config reset after bad inbox-path gets set.
875 <LI> Added web alpine ability to create group contact from contact list members.
876 <LI> Backed out web alpine coercing of default sort-key of arrival to date/reverse.
877 <LI> Tidied up web alpine script layout.
878 <LI> Fixed web alpine status message ordering
879 <LI> Added web alpine Fcc setting via Contacts in Compose
880 <LI> Fixed web alpine autodraft attachment issues
881 <LI> Fixed web alpine problems with recent count maintenance
882 <LI> Fixed web alpine newmail arrival display in message list
883 <LI> Added web alpine confirmation to folder create for Move/Copy
884 <LI> Added web alpine user-domain support
885 <LI> Fixed web alpine to support INBOX-within-a-collection deletion
889 Bugs that have been addressed include:
893 <LI> In web alpine fixed delete all selected within a search result to reorient
894 correctly to whole-mailbox message list.
895 <LI> Fixed web alpine delete in view page to be sensitive to sort
896 <LI> Fixed web alpine open of folder within directory from folder manager page.
897 <LI> Fixed web alpine open of folder within directory from left column's recent cache.
898 <LI> Fixed web alpine problems with spaces in special folder names like Drafts
899 <LI> Fixed web alpine adding contacts from message list and view
900 <LI> Fixed web alpine create of non-existent fcc
901 <LI> Remove mistakenly left debugger statement in web alpine javascript.
902 <LI> Some UNIX alpine build problems fixed
903 <LI> Crash in pico and pilot when nl_langinfo returned something unrecognizable
904 or NULL. Add recognition of "646" to nl_langinfo wrapper. This is returned
905 by locale charmap call on some Solaris 8 systems.
906 <LI> MacOS Keychain logins were not working correctly with generic host names, like
907 imap.gmail.com, as opposed to specific instances like rx-in-209.google.com, causing
908 new password requests when not needed
909 <LI> Possible crash in WhereIs command while in FOLDER LIST when cursor is located on the
910 last folder in the list
911 <LI> Change to S/MIME get_x509_subject_email so that X509v3 alternative names are
912 looked for along with the email address
913 <LI> Changes to configure to get spellcheck options with work with arguments.
914 <LI> Add change from Mark Crispin of panda.com to at least minimally handle non-ascii hostname
915 returned by gethostname (iPhone can do this)
916 <LI> Fixed a bug that prevents a filter that moves a message into a local folder
917 from also setting the DELETE flag in that moved message. Fix from Eduardo Chappa.
918 <LI> Changed size of shellpath in open_system_pipe from 32 to MAXPATH. Fix from
919 Jake Scott of marganstanley.com.
920 <LI> Buffer overflow bug in c-client's tmail/dmail, fix from Mark Crispin. This
921 is not used in alpine.
922 <LI> Imapd server crash from unguarded fs_give in IDLE code, fix from Crispin.
923 Apparently this causes RIM Blackberry BIS service problems. This is not
925 <LI> Tmail uninitialized pointer fix from Neil Hoggarth. Not used in alpine.
926 <LI> Buffer overflow possibility in RFC822BUFFER routines in c-client library.
927 Fix from Ludwig Nussel of SUSE and from Crispin.
928 <LI> Include whole filename in export filename history
929 <LI> Fix display bug in pico when Replace command is canceled. Fix from Eduardo Chappa.
934 addressed bugs found in previous releases and had a few additions as well.
940 <LI> Redesigned Web Alpine interface
941 <LI> Experimental <A HREF="h_mainhelp_smime">S/MIME support</A> added
942 in UNIX versions of Alpine
943 <LI> Attempt to include the attachment filename as part of the name of the
944 temporary file used when viewing an attachment with an external program.
945 Add some randomness to that filename to make it hard to predict the filename.
946 Add a filename extension, usually derived from the type/subtype, to the
947 temporary filename. This was previously done only on Windows and MacOS X.
948 <LI> Enhance address completion in the composer (TAB command) so that it looks
949 through nicknames, fullnames, and addresses from the address book; addresses
950 from the message being viewed, if any; and the results from
951 <A HREF="h_direct_config">LDAP Directory Server</A>
952 lookups for all of the defined directory servers that have the
953 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
955 <LI> Make the default character set setting more liberal in what it will accept
956 from the UNIX nl_langinfo call and the various values of LANG seen in the wild
957 <LI> Remove the Alpine revision number from the titlebar in released versions
958 while leaving it there in snapshot versions
959 <LI> Add a <A HREF="h_config_quell_asterisks">feature</A> to suppress the
960 display of asterisks when you type a password for Alpine
961 <LI> Add line wrapping when displaying <EM>PRE</EM> formatted sections of HTML
963 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
964 feature is turned on convert not only the dates in the index screen but also
965 the dates in the MESSAGE VIEW
969 Bugs addressed in the 2.00 release included:
973 <LI> Crash when using tab-completion for selecting a Save filename
974 <LI> Make Web Alpine help text images relative for more portability
975 <LI> Fixed attach save of html parts in Web Alpine
976 <LI> Viewing, printing, exporting, replying, and bouncing of message
977 digests was broken. Replying and bouncing should not have been
978 allowed at all for digests. It would be nice to have a more standard
979 index-like view of a message digest but that has not been addressed
980 with this minor bug fix.
981 <LI> Adjust wrapping of HTML messages so that the margins specified by
982 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
983 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>
984 are observed correctly
985 <LI> Interrupt of WhereIs command in index was broken
986 <LI> The <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
987 option did not work correctly interpreting unknown characters in message headers
988 <LI> Long address lines could cause blank continuation lines
989 <LI> Save to a local default INBOX failed if the primary collection was also local,
990 which it is by default. The save went to ~/mail/inbox instead.
991 <LI> Make a default save folder of "inbox" always mean the real
992 inbox, not the inbox in the primary collection
993 <LI> Address book entries with lots of addresses would be truncated when
994 entered in the composer with a screen size wider than 270 or so charcters
995 <LI> Some fields in the index screen were truncated when the screen width was
996 wider than 256 characters
997 <LI> Crash when TABing to next folder, the next folder with new mail is a POP
998 folder, and there is a more than 10 minute pause between typing the TAB
1004 addressed bugs found in previous releases and had a few additions as well.
1010 <LI> Add the possibility of setting a default role
1011 (see <A HREF="h_role_select">Roles Screen</A>)
1012 which may be convenient if your work flow involves acting in one
1013 role for a while then switching to another role and staying in the
1014 new role for another period of time
1015 <LI> When Saving and the IMAP server problem "Message to save shrank!"
1016 is encountered, ask the user if he or she wants to continue with the
1017 risky Save anyway instead of aborting. This may be helpful if your
1018 IMAP server is broken in this way but be aware that it is possible there
1019 was a real error instead of just a broken server implementation.
1020 <LI> Some configure adjustments for Kerberos detection and
1021 for SCO OpenServer 5 support
1022 <LI> Hide INBOX in a collection if it also appears as an
1023 <A HREF="h_config_enable_incoming">Incoming Folder</A>
1024 <LI> Show asterisks for feedback when the user is typing a password
1025 <LI> Performance improvement for threading of large folders
1026 <LI> Previously, the search used to find
1027 Pattern matches containing To patterns searched for both To
1028 and Resent-To headers. The relatively complicated search this
1029 produces causes problems when using some deficient IMAP servers.
1030 Now the default is to look only for To headers and ignore the
1031 presence of Resent-To. The previous behavior may be restored
1032 with the <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> feature.
1034 <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
1035 to help with reading malformed unlabeled messages
1036 <LI><A HREF="h_config_suppress_user_agent"><!--#echo var="FEAT_suppress-user-agent-when-sending"--></A> option added
1037 <LI> Map some Shift-LeftArrow escape sequences to LeftArrow
1038 <LI> Add feature <A HREF="h_config_warn_if_fcc_blank"><!--#echo var="FEAT_warn-if-blank-fcc"--></A>
1042 Bugs addressed in the 1.10(962) release included:
1046 <LI> Crash when encountering certain errors from an SMTP server
1047 <LI> Crash in composer caused by overflow in replace_pat()
1048 <LI> Hang when authenticating to an SMTP server that fails with a
1049 "connection disconnected" error
1050 <LI> Bug in handling of trailing tab character in flowed text
1051 <LI> Security enhancement for mailcap parameter substitution
1052 <LI> <A HREF="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></A>
1053 did not work if the message being replied to was not flowed text
1054 and <A HREF="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></A>
1056 <LI> Don't allow printer to be changed through hidden config screen
1057 if system administrator didn't want it to be allowed
1058 <LI> Attempts are sometimes made to set the Forwarded flag when alpine
1059 should know that it won't work, causing error messages to appear
1060 <LI> A <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
1061 of double-quote double-quote didn't work right
1062 <LI> Quoting wasn't being done to protect special characters from the
1064 <A HREF="h_config_browser"><!--#echo var="VAR_url-viewers"--></A>
1066 <LI> On MacOS X message attachments should be shown internally instead of
1067 being shown using the Mail application
1068 <LI> When replying to a message with a charset of X-UNKNOWN Alpine would
1069 sometimes set the outgoing charset to X-UNKNOWN, making the result
1071 <LI> When the sending of a message failed lines with leading spaces had one
1072 additional space inserted in each of those lines when the user
1073 was returned to the composer
1074 <LI> The <A HREF="h_index_cmd_whereis">WhereIs</A> command missed some index lines
1075 that contained non-ascii characters because it was truncating the
1076 line being searched so that it was shorter than what was visible on
1078 <LI> When composing, an attachment with a long name that causes wrapping in
1079 just the wrong place would generate an error and cause the send
1080 of the attachment to fail
1081 <LI> After calling the file browser to attach a file in the composer, a resize
1082 of the window when back in the composer would redraw the last screen that
1083 had been shown in the browser instead of the current composer screen
1084 <LI> Possible crash in index screen when encountering unparseable addresses
1085 or when using one of the PRIORITY tokens or the HEADER token in the
1086 <a href="h_config_index_format"><!--#echo var="VAR_index-format"--></a>
1087 <LI> Problems with Header Color editing if the configuration option
1088 <a href="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></a>
1089 was inadvertently changed to the Empty Value in the hidden config screen
1090 <LI> When resuming the final postponed message from an Exchange server the user
1091 could get a certificate validation failure because alpine was trying
1092 to validate the canonical name of the folder instead of the name the
1094 <LI> Windows line endings in a mimetypes file on a Unix system cause a
1095 failure to find a match
1096 <LI> Make matching of extension names case independent in mimetypes files
1097 <LI> Windows dialog boxes for entering text were not working correctly
1098 <LI> Replying to or Forwarding multipart/alternative messages which had a
1099 single text/html part did not work well
1100 <LI> Printing the print confirmation page caused a crash
1101 <LI> A To line with a long, quoted personal name could display incorrectly
1102 if it was close to the same width as the screen
1103 <LI> When <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
1104 and <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
1105 are turned on hide (0/0) when the folder is empty
1106 <LI> Folder completion while Saving didn't work if the collection being
1107 saved to was the local home directory
1112 was an evolutionary release based on
1113 <A HREF="http://www.washington.edu/pine/">Pine</A>, which was also
1114 developed at the University of Washington.
1115 It is upwards-compatible for existing Pine users.
1121 <LI> Ground-up reorganization of source code around addition
1122 of "pith/" core routine library.
1123 <LI> Fundamental improvement in Alpine's internal text handling, which
1124 is now based exclusively on Unicode. This allows displaying incoming
1125 messages and producing outgoing messages in many different languages.
1126 <LI> Ground-up reorganization of build and install procedures
1127 based on GNU Build System's autotools. NOTE, the included IMAP library
1128 build is not based on autotools, so some features will not work. However,
1129 it should get built automatically during the Alpine build process.
1130 <LI> Web-based version included built on TCL designed to run under
1131 a suitable CGI-supporting web server such as Apache.
1136 Details on changes in previous (prerelease) versions of Alpine
1137 may be found at the following URL:
1139 <CENTER><SAMP><A HREF="http://repo.or.cz/alpine.git">http://repo.or.cz/alpine.git</A></SAMP></CENTER>
1144 <H2>Getting Help</H2>
1146 <DT>Online Help</DT>
1148 Every Alpine screen and command has associated help text
1149 accessible via the "?" key (or Ctrl-G in text-input contexts).
1154 The most current source of information about Alpine,
1155 including new version availability, is the web page at
1157 <CENTER><SAMP><A HREF="http://repo.or.cz/alpine.git">http://repo.or.cz/alpine.git</A></SAMP></CENTER>
1161 Frequently Asked Questions (and answers) may be found at the following
1164 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/faq/">http://www.washington.edu/alpine/faq/</A></SAMP></CENTER>
1169 <H2>Additional Information</H2>
1171 General Alpine configuration information can be found
1172 <A HREF="h_news_config">here</A>.
1174 This is revision (<!--#echo var="ALPINE_REVISION"-->) of the Alpine software.
1175 Alpine mailbox and <A HREF="https://github.com/jonabbey/panda-imap/">IMAP</A> server
1176 access is provided by the IMAP Toolkit Environment (c-client library)
1177 version <!--#echo var="C_CLIENT_VERSION"-->.
1179 Alpine was developed until 2009 by the Office of Computing
1180 & Communications at the University of Washington in Seattle.
1181 Since then, the effort of developing Alpine has been continued by
1182 a community of volunteers who make good software even better!
1185 Alpine Copyright 2013-2018 Eduardo Chappa,
1186 <BR> Copyright 2006-2008 University of Washington.
1189 Additional legal notices can be found <A HREF="h_news_legal">here</A>,
1190 or instead you can find the Apache License, version 2.0 at the web URL:
1193 <CENTER><A HREF="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</A></CENTER>
1196 <End of Release Notes>
1199 ====== h_password_file_support ======
1202 <TITLE>Encryption for Password File Support Explained</TITLE>
1205 <H1>Encryption for Password File Support Explained</H1>
1209 <LI><A HREF="#content">Explanation</A>
1210 <LI><A HREF="#example_existing_key">Example of Use of Existing Key and Certificate</A>
1211 <LI><A HREF="#example_self_signed">Example of Creating Master Password</A>
1214 <P><A NAME="content">Unix Alpine Only.</A>
1216 <P> If your version of Alpine has been built with password file support
1217 then you can use a special file to save your passwords, and avoid typing
1218 them every time you open a connection to a remote server.
1220 <P> If, in addition, your version of Alpine was built with SMIME support, then your
1221 password file will be encrypted with a strong key. There are two ways in
1222 which this can happen: Alpine will either use a matching private key and
1223 public certificate pair that you already own, or it will create one for
1224 you, just for purposes of encrypting this file. We describe both processes
1227 <P> Initially, Alpine will scan your public and private directories for a
1228 certificate/private key pair that works. Alpine will pick the first pair
1229 that it finds that matches.
1231 <P> Once a pair has been chosen, it will be copied to the directory
1232 ~/.alpine-smime/.pwd, and from then on, Alpine will use the pair found in
1233 that directory. The first time this process is done, this directory will
1234 be created, a key/certificate pair will be copied to it, from then on
1235 this pair will be used to encrypt and decrypt your password file.
1237 <P> If you want to use a specific key and certificate pair to encrypt
1238 your password file, you can create the directory ~/.alpine-smime/.pwd
1239 manually, and then create your preferred key/certificate pair there.
1240 Alpine will use this key regardless of if it has expired, or if it is
1241 self-signed. These issues do not affect the encryption or decryption
1242 of the password file.
1244 <P> If you prefer not to use the directory ~/.alpine-smime/.pwd to save
1245 your key/certificate pair, you can specify a different one with the
1246 -pwdcertdir command line option in Alpine. If the directory specified by
1247 this option is not found Alpine will fail to encrypt and decrypt your
1248 password file. However if it exists, Alpine will search for a
1249 key/certificate pair in that
1250 directory, and if it does not find one, it will create one and save it
1253 <P> Alpine does not care about the names of the key and certificates in
1254 this directory, but the private key must have ".key" extension
1255 and your public certificate must have the ".crt" extension. The
1256 name of the private key will be used in the prompt when you are asked
1257 to unlock your key to decrypt your password.
1259 <P> If Alpine cannot find a suitable private key and public certificate
1260 pair to encrypt your password, it will create one. You will be asked to
1261 create a "Master Password" to protect such key. At this moment
1262 there are no restrictions on passwords, other than they have to be at
1263 least 8 characters long, but future versions of Alpine will include
1264 functionality to restrict master passwords, as set up by the administrator
1265 of the system in the pine.conf.fixed file.
1267 <P><A NAME="example_existing_key"><B>Example of Use of Existing Key and Certificate</B></A>
1269 <P>Assume you have a private key called peter@address.com.key in your,
1270 ~/.alpine-smime/private directory, and a public certificate called
1271 peter@address.com.crt in your ~/.alpine-smime/public directory, and these
1272 are your only key/certificate pair.
1274 <P> When Alpine starts for the first time, without command line options,
1275 it will check if the directory ~/.alpine-smime/.pwd exists, and if not,
1276 it will create it. Then it will go through your keys and certificates and
1277 find a pair that it can use, and copy the files peter@address.com.key,
1278 and peter@address.com.crt to the ~/.alpine-smime/.pwd directory. Alternatively
1279 you can do the same by copying these files by yourself. This can be done
1280 with the sequence of commands
1283 mkdir ~/.alpine-smime/.pwd
1284 cp ~/.alpine-smime/private/peter@address.com.key ~/.alpine-smime/.pwd
1285 cp ~/.alpine-smime/public/peter@address.com.crt ~/.alpine-smime/.pwd
1288 <P> When Alpine starts, you will be asked the password to unlock your
1289 private key with the prompt.
1292 Enter password of key <peter@address.com> to unlock password file:
1295 <P> If you prefer to use different names for your private and public keys
1296 in the ~/.alpine-smime/.pwd directory, you can do so, but you must
1297 preserve the extension of the files. For example, you can use the names
1298 private_key.key and public_cert.crt instead. In this case, the prompt you
1299 will see when you are asked to unlock your private key will read
1302 Enter password of key <private_key> to unlock password file:
1305 <P>Observe that you do not need to use an existing key/certificate pair,
1306 and that you can create a new private key/public certificate pair to
1307 encrypt and decrypt your password file. Alpine provides a mechanism to
1308 change the encryption key for this file in the S/MIME configuration
1311 <P><A NAME="example_self_signed"><B>Example of Creating Master Password</B></A>
1313 <P> If Alpine cannot find a suitable private key and public certificate pair
1314 to encrypt your password file, it will create one. When doing so, it will
1315 start the process with the following warning:
1318 Creating a Master Password for your Password file.
1321 <P> Then Alpine will ask you to enter your Master Password:
1324 Create master password (attempt 1 of 3):
1327 <P> Once you enter this password, and it validates according to system policy,
1328 you will be asked to confirm this password.
1331 Confirm master password (attempt 1 of 3):
1334 <P> If you input the same password, then Alpine will set that as your
1335 Master Password, and you will use this password to unlock your key in the
1338 <P> If you would like to switch your Master Password in the future, you can
1339 do so by creating a new public key and public certificate pair. You can do
1340 so in the S/MIME configuration screen, in the "Manage Key and
1341 Certificate for Password File" section, simply enter your current
1342 password to unlock your current key and then press "C" to create
1349 ====== h_tls_failure_details ======
1352 <TITLE>Certificate Validation Details</TITLE>
1355 <H1>Certificate Validation Details</H1>
1357 This screen gives details as to why the certificate validation failed: the
1358 name of the desired server system; the reason for failure; and the name on
1359 the certificate. This is primarily of interest to experts.
1365 ====== h_tls_failure ======
1368 <TITLE>TLS or SSL Failure</TITLE>
1371 <H1>TLS or SSL Failure</H1>
1373 An attempt was made to establish a secure, encrypted connection to the
1374 server system using either Transport Layer Security (TLS) or the older
1375 Secure Sockets Layer (SSL). This attempt failed.
1378 You should contact your server system management for more assistance.
1379 The problem is probably at the server system and not in Alpine or your local
1380 system. The text in this screen may be helpful for the server system
1381 management in debugging the problem,
1387 ====== h_tls_validation_failure ======
1390 <TITLE>TLS and SSL Certificate Validation Failures</TITLE>
1393 <H1>TLS and SSL Certificate Validation Failures</H1>
1395 An attempt was made to establish a secure, encrypted connection to the
1396 server system using either Transport Layer Security (TLS) or the older
1397 Secure Sockets Layer (SSL).
1400 An important part of this procedure is server certificate validation. A
1401 server certificate is an "electronic identification card" for the server
1402 system that is signed by a well-known certificate authority (CA). Alpine
1403 compares the server system identity in the server certificate with the
1404 name of the server system to which it is trying to connect. Alpine also
1405 verifies that the CA signature is authentic.
1408 Some common failure conditions are:
1412 <LI> [UNIX Alpine] Self signed certificate. This means that the server system
1413 signed its own certificate. This does not necessarily indicate anything
1414 bad; the server operators may simply have elected to not purchase a
1415 signed certificate from a certificate authority.
1417 <LI> [UNIX Alpine] Unable to get local issuer certificate. This means that
1418 the signature on the server system is from an unknown certificate authority.
1419 It can also mean that no certificate authority certificates have been
1420 installed on the local UNIX system.
1422 <LI> [PC Alpine] Self-signed certificate or untrusted authority. This is
1423 the same as either of the above two conditions in UNIX Alpine. Note that
1424 Windows systems typically have a full set of certificate authority
1425 certificates installed, so it is more likely to be a self-signed
1426 certificate than an unknown certificate authority.
1428 <LI> Server name does not match certificate. This means that the server
1429 presented a proper signed certificate for a name other than the desired
1434 Any of these conditions can indicate that you are being attacked and have
1435 been directed to an imposter server that will record your password and
1436 your private mail messages. It can also mean something innocuous.
1439 If you are certain that the problem is innocuous, you can append the
1443 <CENTER><SAMP>/novalidate-cert</SAMP></CENTER>
1446 to the server system name where it appears in your configuration (e.g. the
1447 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>,
1448 a folder-collection, or a news or SMTP server). This will
1449 disable certificate validation. On the other hand, if you are attacked,
1450 you will get no warning if you do this.
1453 <End of Cert Validation Failures help>
1456 ====== h_release_tlscerts ======
1459 <TITLE>TLS and SSL usage note</TITLE>
1462 <H1>TLS and SSL usage note</H1>
1465 When using Alpine from Unix or Windows 2000,
1466 server certificates must be signed by a trusted certificate authority.
1467 You may relax this requirement (at the cost of some security) by using
1469 <A HREF="h_folder_server_syntax">NoValidate-Cert</A>
1470 modifier in the mailbox name.
1473 <CENTER><SAMP>{foo.example.com/novalidate-cert}INBOX</SAMP></CENTER>
1476 The fully-qualified host name of the server should be used
1477 so that it matches the host name in the server certificate.
1479 Here is an example of a host specification that directs Alpine to use
1480 the SSL port (993) and an encrypted data stream.
1482 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
1484 <End of TLS usage help>
1487 ====== h_news_config ======
1490 <TITLE>Alpine Configuration</TITLE>
1493 <H1>Alpine Configuration</H1>
1495 <H2>Using Environment Variables</H2>
1497 The values of Alpine configuration options may include environment variables
1498 that are replaced by the value of the variable at the time Alpine is run
1499 (and also at the time the config option is changed).
1500 The syntax to use environment variables is a subset of the common Unix
1501 shell dollar-syntax.
1504 <P><CENTER><SAMP>$VAR</SAMP></CENTER><P>
1506 appears in the value of an Alpine configuration option it is looked up in the
1507 environent (using getenv("VAR")) and its
1508 looked-up value replaces the <SAMP>$VAR</SAMP> part of the option value.
1509 To include a literal dollar sign you may precede the dollar sign with another
1511 In other words, if the text
1513 <P><CENTER><SAMP>$$text</SAMP></CENTER><P>
1515 is the value of a configuration option, it will be expanded to
1517 <P><CENTER><SAMP>$text</SAMP></CENTER><P>
1519 and no environment lookup will be done.
1520 For Unix Alpine it will also work to use a backslash character to
1521 escape the special meaning of the dollar sign, but $$ is preferable since
1522 it works for both PC-Alpine and Unix Alpine, allowing the configuration option
1523 to be in a shared configuration file.
1526 This all sounds more complicated than it actually is.
1527 An example may make it clearer.
1528 Unfortunately, the way in which environment variables are set is OS-dependent
1529 and command shell-dependent.
1530 In some Unix command shells you may use
1532 <P><CENTER><SAMP>PERSNAME="Fred Flintstone"</SAMP></CENTER><P>
1533 <CENTER><SAMP>export PERSNAME</SAMP></CENTER><P>
1535 Now, if you use Alpine's Setup/Config screen to set
1537 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=$PERSNAME</SAMP></CENTER><P>
1539 the <SAMP>$PERSNAME</SAMP> would be replaced by <SAMP>Fred Flintstone</SAMP>
1540 so that this would be equivalent to
1542 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=Fred Flintstone</SAMP></CENTER><P>
1544 Note, environment variable substitution happens after configuration
1545 options that are lists are split into the separate elements of the list,
1546 so a single environment variable can't contain a list of values.
1549 The environment variable doesn't have to be the only thing
1550 after the equal sign.
1551 However, if the name of the variable is not at the end of the line or
1552 followed by a space (so that you can tell where the variable name ends),
1553 it must be enclosed in curly braces like
1555 <P><CENTER><SAMP>${VAR}</SAMP></CENTER><P>
1557 It is always ok to use the braces even if you don't need to.
1559 It is also possible to set a default value for an environment variable.
1560 This default value will be used if the environment variable is not
1561 set (that is, if getenv("VAR") returns NULL).
1562 The syntax used to set a default value is
1564 <P><CENTER><SAMP>${VAR:-default value}</SAMP></CENTER><P>
1566 If the config file contains
1568 <P><CENTER><SAMP>personal-name=${VAR:-Fred Flintstone}</SAMP></CENTER><P>
1570 then when Alpine is run <SAMP>VAR</SAMP> will be looked up in the environment.
1571 If <SAMP>VAR</SAMP> is found then <SAMP>personal-name</SAMP> will have
1572 the value that <SAMP>VAR</SAMP> was set to, otherwise,
1573 <SAMP>personal-name</SAMP> will be set to <SAMP>Fred Flintstone</SAMP>,
1575 (Note that the variable is called "personal-name" in the config
1576 file but is displayed in the config screen as
1577 "<!--#echo var="VAR_personal-name"-->".
1578 In general, the value that goes into a config file is never exactly the
1579 same as the value you see on the screen.)
1582 An example where an environment variable might be useful is the
1583 variable <SAMP>Inbox-Path</SAMP> in the global configuration file.
1584 Suppose most users used the server
1586 <P><CENTER><SAMP>imapserver.example.com</SAMP></CENTER><P>
1588 but that there were some exceptions who used
1590 <P><CENTER><SAMP>altimapserver.example.com</SAMP></CENTER><P>
1592 In this case, the system manager might include the following line in
1593 the systemwide default Alpine configuration file
1595 <P><CENTER><SAMP>Inbox-Path=${IMAPSERVER:-imapserver.example.com}</SAMP></CENTER><P>
1597 For the exceptional users adding
1599 <P><CENTER><SAMP>IMAPSERVER=altimapserver.example.com</SAMP></CENTER><P>
1601 to their environment should work.
1603 Another example might be the case where a user has to use a different
1604 SMTP server from work and from home.
1605 The setup might be something as simple as
1607 <P><CENTER><SAMP>smtp-server=$SMTP</SAMP></CENTER><P>
1609 or perhaps a default value could be given.
1610 Note that, as mentioned above, the variable <SAMP>SMTP</SAMP> cannot contain
1611 a list of SMTP servers.
1614 <H2>Configuration precedence</H2>
1616 There are several levels of Alpine configuration. Configuration values at
1617 a given level override corresponding values at lower levels. In order of
1618 increasing precedence:
1621 <LI> built-in defaults
1623 <!--chtml if pinemode="os_windows"-->
1624 config file from command line or provided
1625 by "PINECONF" environment variable
1629 <LI> personal configuration file
1630 <LI> personal exceptions configuration file
1631 <LI> command-line options
1632 <!--chtml if pinemode="os_windows"--><!--chtml else-->
1633 <LI> system-wide pine.conf.fixed file<!--chtml endif-->
1636 The values in both the personal configuration file and the
1637 <A HREF="h_config_exceptions">exceptions</A>
1638 configuration file may be set using the Setup command.
1639 Setup/Config is the command to change most of the personal configuration
1641 The other Setup subcommands are also used to change the configuration,
1642 for example, Setup/AddressBook, Setup/Rules, and so on.
1643 Changing the personal exceptions configuration is very similar.
1644 To change a value in the Config screen you would use the command
1645 Setup/eXceptions/Config.
1646 Likewise for the other Setup subcommands (Setup/eXceptions/Rules and so on).
1648 There are a couple exceptions to the rule that configuration values are replaced
1649 by the value of the same option in a higher-precedence file.
1650 The Feature-List variable has values that are additive, but can be
1651 negated by prepending "no-" in front of an individual feature name.
1652 So for features, each individual feature's value is replaced by the value
1653 of the same feature in a higher-precedence file.
1654 Note that this is done automatically for you when you change these values via
1655 the Setup/Config command.
1656 The other exception to the <EM>replace</EM> semantics happens when you
1657 use <A HREF="h_config_inheritance">configuration inheritance</A>
1661 <H2>File name defaults</H2>
1665 <BR> <exe dir> = directory where pine.exe found.
1666 <BR> <pinerc dir> = directory where pinerc found.
1667 <BR> # = default file name is overridable in pinerc.
1668 <BR> $HOME, if not explicitly set, defaults to root of the current drive.
1669 <BR> $MAILCAPS, if set, is used in lieu of the default mailcap search paths.
1670 <BR> + between the mailcap paths implies that the two files are combined.
1671 <BR> ; between other default paths implies that the first one found is used.
1673 Alpine looks for most support files in the same directory it finds its
1674 personal configuration file (pinerc). The -p command-line flag may be
1675 used to specify a particular path name for the pinerc file. If a
1676 pinerc file does not exist, it will be created (if directory permissions
1677 allow). In PC-Alpine, if -p or $PINERC are not defined, Alpine will look
1678 in $HOME\PINE and the directory containing the PINE.EXE. If a PINERC
1679 file does not exist in either one, it will create one in the first of those
1680 two directories that is writable. In detail:
1685 executable <DOS search path>\pine.exe
1686 help index <exe dir>\pine.ndx
1687 help text <exe dir>\pine.hlp
1689 pers config $PINERC ; $HOME\pine\PINERC ; <exe dir>\PINERC
1690 except config $PINERCEX ; $HOME\pine\PINERCEX ; <exe dir>\PINERCEX
1691 global cfg $PINECONF
1693 debug <pinerc dir>\pinedebg.txtN
1694 crash <pinerc dir>\pinecrsh.txt
1695 signature# <pinerc dir>\pine.sig
1696 addressbook# <pinerc dir>\addrbook
1697 mailcap# <pinerc dir>\mailcap + <exe dir>\mailcap
1698 mimetypes# <pinerc dir>\mimetype + <exe dir>\mimetype
1699 newsrc# $HOME\newsrc (if exists, else) <pinerc dir>\newsrc
1700 sentmail# $HOME\mail\sentmail.mtx
1701 postponed# $HOME\mail\postpond.mtx
1702 interrupted $HOME\mail\intruptd
1706 executable <Unix search path>/pine
1707 persnl cfg ~/.pinerc
1708 except cfg ~/.pinercex
1709 global cfg <!--#echo var="PINE_CONF_PATH"-->
1710 fixed cfg <!--#echo var="PINE_CONF_FIXED_PATH"-->
1711 local help <!--#echo var="PINE_INFO_PATH"-->
1713 interrupted ~/.pine-interrupted-mail
1714 debug ~/.pine-debugN
1717 signature# <pinerc dir>/.signature
1718 addressbook# <pinerc dir>/.addressbook
1719 postponed# ~/mail/postponed-msgs
1720 sentmail# ~/mail/sent-mail
1721 mailcap# ~/.mailcap + /etc/mailcap
1722 + /usr/etc/mailcap + /usr/local/etc/mailcap
1723 mimetypes# ~/.mime.types + /etc/mime.types + /usr/local/lib/mime.types
1725 news-spool varies across Unix flavors, e.g. /var/spool/news or /usr/spool/news
1726 active-news varies across Unix flavors, e.g. /usr/lib/news/active
1727 lock files /tmp/.<!--#echo var="MAIL_SPOOL_LOCK_PATH"-->
1728 inbox <!--#echo var="MAIL_SPOOL_PATH"-->
1729 password /etc/passwd
1731 Unix Alpine and PC-Alpine:
1733 .ab* remote addressbook support files
1734 a[1-9]* temporary (while Alpine is running) addressbook files
1739 <H2>Mailcap files</H2>
1741 Alpine honors the mailcap configuration system for specifying external
1742 programs for handling attachments. The mailcap file maps MIME attachment
1743 types to the external programs loaded on your system that can display
1744 and/or print the file. A sample mailcap file comes bundled with the Alpine
1745 distribution. It includes comments that explain the syntax you need to
1746 use for mailcap. With the mailcap file, any program (mail readers,
1747 newsreaders, WWW clients) can use the same configuration for handling
1751 <H2>MIME-Types files</H2>
1753 Alpine uses mime-types files (.mime.types or MIMETYPE) to determine
1754 what Content-Type to use for labeling an attached file, based on
1755 the file extension. That is, this file provides a mapping between
1756 filename extensions and MIME content-types.
1759 <H2>Environment variables</H2>
1761 PC-Alpine uses the following environment variables:
1764 <DD>Optional path to pinerc file.</DD>
1766 <DD>Optional path to personal exceptions configuration file.</DD>
1768 <DD>Optional path to global pine config file.</DD>
1770 <DT>TMPDIR, TMP, or TEMP</DT>
1773 <DD>A <B>semicolon</B> delimited list of path names to mailcap files.</DD>
1774 <DT>USER_DICTIONARY</DT>
1775 <DD>Used to specify the file to contain the user's spell check
1776 dictionary. The default is <SAMP>DICT.U</SAMP> in the same
1777 directory as the <SAMP>SPELL32.DLL</SAMP></DD>
1780 Unix Alpine uses the following environment variables:
1783 <DD>Tells Alpine what kind of terminal is being used.</DD>
1785 <DD>Determines if Alpine will try to display IMAGE attachments.</DD>
1787 <DD>If not set, default is "/bin/sh".</DD>
1788 <DT>TMPDIR, TMP, or TEMP</DT>
1790 <DD>A <B>colon</B> delimited list of path names to mailcap files.</DD>
1792 <!--chtml if pinemode="os_windows"-->
1794 <H2>Common PC-Alpine Configuration Problems</H2>
1796 <H3>Configuration settings aren't being saved</H3>
1798 <P>This problem can happen if you run pine from one directory and
1799 then decide to move your pine directory to another location. PC-Alpine
1800 stores certain variables, including the configuration location, in the
1801 Windows Registry (which you shouldn't ever need to manually edit). There
1802 are a couple of ways to go about removing or resetting the values in the
1806 1) Run PC-Alpine's registry value deletion command. This can be done by
1807 running: "<your pine directory>\pine.exe -registry clear" from the DOS
1808 prompt. You could create a shortcut to pine.exe and change the "Target"
1809 value to the above command.
1812 2) Tell PC-Alpine where to look for the configuration file. Configuration
1813 information is stored in a file called the PINERC. With the "-p PINERC"
1814 option, you can tell PC-Alpine the location of your pinerc. An example of
1815 this would be to run: "<your pine directory>\pine.exe -p C:\pine\mypinerc".
1816 Again, you can use the DOS prompt or the shortcut method explained in (1).
1819 Additionally, there is the "-registry set" option, which will actively
1820 set registry values to the current setting, and is therefore useful with
1821 the "-p PINERC" option.
1825 <End of Configuration Notes>
1828 ====== h_news_legal ======
1831 <TITLE>Alpine Legal Notices</TITLE>
1835 <H1>Alpine Legal Notices</H1>
1837 Alpine and its constituent programs are covered by the Apache License Version 2.0.
1841 <End of Alpine Legal Notices>
1844 ===== h_info_on_mbox =====
1847 <TITLE>Information on mbox driver</TITLE>
1850 <H1>Information on "Missing Mail" and the "mbox" driver</H1>
1852 Beginning with Pine 4.00 (Pine came before Alpine)
1853 a new INBOX access method is
1854 available as part of the standard configuration. It is called the
1855 "mbox" driver and it works like this:<P>
1859 If the file "mbox" exists in the user's home directory, and
1860 is in Unix mailbox format, then when INBOX is opened this file will be
1861 selected as INBOX instead of the mail spool file. Messages will be
1862 automatically transferred from the mail spool file into the mbox
1867 The advantage of this method is that, after new mail has been copied
1868 from the system mail spool, all subsequent access is confined to the
1869 user's home directory, which is desirable on some systems. However, a
1870 possible disadvantage is that mail tools other than those from the
1871 University of Washington will not know to look for mail in the user's
1872 mbox file. For example, POP or IMAP servers other than those from the
1873 University of Washington, and many "new mail notification"
1874 programs may not work as expected with this driver enabled.<P>
1876 To disable this behavior, either remove/rename the "mbox"
1877 file or find the <A HREF="h_config_disable_drivers"><!--#echo var="VAR_disable-these-drivers"--></A>
1878 option in Setup/Config
1879 and add "mbox" to it:
1881 <CENTER><SAMP><!--#echo var="VAR_disable-these-drivers"-->=mbox</SAMP></CENTER>
1883 <End of help on this topic>
1886 ===== h_info_on_locking =====
1889 <TITLE>FAQs on Alpine Locking</TITLE>
1892 <H1>What Systems Managers Need to Know about Alpine File Locking</H1>
1894 There is an extensive section on locking in the Alpine technical notes;
1895 this information is intended to provide answers to some common questions:<P>
1897 <LI> Why did locking change in Pine 4.00?<BR>
1898 The actual locking mechanisms did not change in 4.00.
1899 What changed is that when one particular locking mechanism used by Alpine
1900 fails, Alpine now issues a warning message. Prior to Pine 4.00, the locking
1901 failure would occur, but no warning was issued.<P>
1903 <LI> Is this what the "Mailbox vulnerable" message is about?<BR>
1904 Yes. It means that Alpine was unable to create a lockfile in the
1905 spool directory, generally because of overly restrictive protections on the
1906 spool directory. The correct permissions on the spool directory for
1907 running Alpine are 1777, i.e. read-write-execute permission for everyone,
1908 with the sticky-bit set, so only owners of a file can delete them.<P>
1910 <LI> Why does Alpine require that the mail spool directory have 1777
1912 Alpine was designed to run without special privileges. This means that in
1913 order to create a lockfile in the spool directory, it is necessary to have
1914 the spool directory permissions be world-writable.<P>
1916 <LI> Can't you create the lockfile somewhere else?<BR>
1917 No. The lockfile in question must be in the mail spool directory, because
1918 that's where the mail delivery program expects to find it, and the purpose
1919 of the file is to coordinate access between the mail client (Alpine) and the
1920 mail delivery program.<P>
1922 <LI> Isn't having the spool directory world-writable a big security risk?<BR>
1923 No. Remember that the individual mail files in the spool directory are
1924 NOT world-writable, only the containing directory. Setting the "sticky
1925 bit" -- indicated by the "1" before the "777" mode
1926 -- means that only the owner of the file (or root) can delete files in the
1927 directory. So the only bad behavior that is invited by the 1777 mode is that
1929 create a random file in the spool directory. If the spool directory is
1930 under quota control along with home directories, there is little incentive
1931 for anyone to do this, and even without quotas a periodic scan for
1932 non-mail files usually takes care of the problem. <P>
1934 <LI> Why not run Alpine as setgid mail?<BR>
1935 Alpine was never designed to run with privileges, and to do so introduces a
1936 significant security vulnerability. For example, if a user suspends Alpine,
1937 the resulting shell will have group privileges. This is one example of
1938 why we strongly recommend against running Alpine as a privileged program.
1939 In addition, a "privileged mailer " paradigm would mean that normal
1941 could not test Alpine versions or other mailers that had not been installed
1942 by the system administrators.<P>
1945 <LI> Are there any alternatives to creating .lock files in the spool dir?<BR>
1946 There are, but they all have different sets of tradeoffs, and not all will
1947 work on all systems. Some examples:<UL>
1948 <LI> Use lock system calls. Works fine on a few systems, provided mail
1949 spool is local. Doesn't work reliably if NFS is used.
1950 Doesn't work unless <B>all</B> the mail programs accessing the spool dir
1952 <LI> Deliver mail to user's home directory. An excellent solution, highly
1953 recommended -- but one which is incompatible with some "legacy"
1954 mail tools that always look in the spool directory for the mail.
1957 <LI> Are these spool directory lock files the only kinds of locks used by
1959 No. Alpine also creates lockfiles in the /tmp directory. For normal Unix
1960 mailbox format folders, these are used to coordinate access between
1961 multiple Alpine sessions. <P>
1964 <A HREF="h_config_quell_lock_failure_warnings">"<!--#echo var="FEAT_quell-lock-failure-warnings"-->"</A> feature added in Pine 4.01?<BR>
1965 This is for people who are content to live dangerously, or who have
1966 specific knowledge that the spool directory lockfiles are superfluous on
1967 their system (because both Alpine and the mail delivery program are using
1968 system call file locking in a context that works reliably, e.g. not NFS.)<P>
1970 <LI> Where can I find more details on how Alpine locking works?<BR>
1971 See the Alpine Technical Notes.<P>
1975 <End of help on this topic>
1978 ===== h_finding_help ====
1981 <TITLE>Finding more information and requesting help</TITLE>
1984 <H1>Places to Look for More Answers</H1>
1985 If you have questions about or problems with Alpine that you cannot resolve
1986 after consulting the program's internal, context-sensitive help screens, here
1987 are additional information resources that you may find helpful:
1990 <LI> Alpine's top-level <A HREF="main_menu_tx">MAIN MENU HELP</A>.<P>
1992 <LI> Alpine's <A HREF="h_help_index">Help Index</A>.<P>
1994 <LI> Alpine's internal <A HREF="h_news">Release Notes</A>. They contain a
1995 listing of changes in Alpine <!--#echo var="ALPINE_VERSION"-->
1996 since the last version, which may be useful for you to be aware of,
1997 <B>especially</B> if a "problem" you are encountering is actually
1998 a change in the way an aspect of Alpine works. There, you will also find notes
1999 on Alpine configuration.<P>
2001 <LI> The main site for Alpine contains information on configuring and solving problems
2002 with Alpine, it can be found at
2004 <CENTER><A HREF="http://alpine.freeiz.com/alpine/">http://alpine.freeiz.com/alpine/</A></CENTER>
2006 <LI> The Alpine Information Center (maintained by the University of
2007 Washington) World Wide Web site contains, among other things
2009 <LI>a collection of Frequently Asked Questions (and answers!) about Alpine
2010 <LI>an overview of the basics for beginning Alpine users
2011 <LI>Technical Notes for systems administrators
2012 <LI>archives (including a searchable index) of the alpine-info
2013 mailing list, on which matters of interest to systems/email administrators,
2014 developers, trainers, user support personnel, and others involved with Alpine
2015 messaging on a "technical" level are discussed.
2017 The Alpine Information Center can be accessed with a WWW browser at:<P>
2018 <CENTER><A HREF="http://www.washington.edu/alpine/">http://www.washington.edu/alpine/</A></CENTER>
2021 <H1>Requesting help</H1>
2022 If the internal help, the Release Notes, the Alpine Information Center, and your
2023 local online and print resources do not help you resolve a problem, please
2024 start by contacting your local computer support staff and asking for help.
2026 This is especially true if:
2028 <li>You suddenly have trouble sending or receiving mail.
2029 <li>You receive a "disk quota exceeded" message.
2030 <li>You have forgotten your password.
2031 <li>You think your account may have been compromised.
2032 <li>You need help viewing an attachment.
2033 <li>You need to know how to configure your:
2034 <A HREF="h_config_nntp_server">NNTP (news) server</A>,
2035 <A HREF="h_config_smtp_server">SMTP (sending mail) server</A>,
2036 <A HREF="h_config_ldap_server">LDAP (directory lookup) server</A>, or
2037 <A HREF="h_config_inbox_path">INBOX (incoming mail) path</A>.
2038 <li>You want to know what alternative editors or spellcheckers you may be able to use.
2039 <li>You want to block email from a particular person.
2040 <li>You're going on vacation and need to autorespond to incoming mail.
2041 <li>You want to automatically file or filter incoming messages.
2044 In all of these cases,
2045 you should contact <B>your</B> support staff, because <B>only they</B>
2046 will be able to assist you effectively. Your support staff may be, depending on who
2047 provides you with the email account you use Alpine with, for example:<UL>
2048 <LI> the computing help desk of (a department of) your university, school,
2050 <LI> the customer service center of your Internet Service Provider; or
2051 <LI> the friendly volunteer helpers of your Freenet; or
2052 <LI> the person who setup your computer and internet connection.
2055 Due to the large number of Alpine installations worldwide, and because we
2056 receive no funding for it, the University of Washington <B>cannot provide
2057 individual support services outside the University of Washington</B>.
2059 If you have no local computing support to turn to, the worldwide <b>comp.mail.pine</b>
2060 newsgroup can be a valuable source of information and assistance for Alpine
2063 For systems/email administrators, developers, trainers, user support
2064 personnel, and others involved with Alpine messaging on a "technical"
2065 level, the mailing list alpine-info is available; for information on
2066 subscribing and posting to it, see
2068 <CENTER><A HREF="http://www.washington.edu/alpine/alpine-info/subscribing.html">http://www.washington.edu/alpine/alpine-info/subscribing.html</A></CENTER>
2071 Regardless of whom you are asking for help with Alpine, remember
2072 to provide as much detail as you can about the
2073 nature of any problem you are encountering, such as
2075 <LI>when it first occurred;
2076 <LI>what, if anything, happened that might have brought it about;
2077 <LI>whether it still persists;
2078 <LI>whether it is reproducible, and if so, how;
2079 <LI>what, if anything, you already tried to solve it.
2081 It may also be helpful if you specify what version of Alpine you are using
2082 <!--chtml if pinemode="running"-->
2083 -- this is <!--#echo var="ALPINE_VERSION"--> --
2085 and on what system, and when the copy of Alpine you are using was created
2086 <!--chtml if pinemode="running"-->
2087 -- for this copy: <!--#echo var=ALPINE_COMPILE_DATE-->
2090 <!--chtml if pinemode="running"-->
2092 When the Alpine program you are currently using was installed, a support
2093 contact email address may have been set up; in that case, you can simply select
2094 this link now to send a message to it:<BR>
2095 <A HREF="X-Alpine-Gripe:_LOCAL_ADDRESS_?local"><!--#echo var="_LOCAL_FULLNAME_"--></A><P>
2097 <!--chtml if [ -r PINE_INFO_PATH ]-->
2098 <HR WIDTH="75%">Local Support Contacts:<P>
2099 <!--#include file="PINE_INFO_PATH"-->
2103 <End of help on this topic>
2106 ===== new_user_greeting ======
2109 <TITLE>NEW USER GREETING</TITLE>
2112 <CENTER><<<This message will appear only once>>></CENTER>
2114 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
2115 We hope you will explore Alpine's many capabilities. From the MAIN MENU,
2116 select Setup/Config to see many of the options available to you. Also note
2117 that all screens have context-sensitive help text available.<P>
2118 <!--chtml if pinemode="phone_home"-->
2120 This software was originally created and maintained as a public
2121 service by the University of Washington until 2009; updates are made
2122 available as a public service of the Alpine community. It is always
2123 helpful to have an idea of how many users are using Alpine. Are you
2124 willing to be counted as an Alpine user? Pressing
2125 <A HREF="X-Alpine-Phone-Home:">Return</A>
2126 will send an anonymous (meaning, your real email address will not be revealed)
2127 message to the Alpine developers for purposes of tallying.
2129 <!--To Exit this screen and continue your Alpine session press "E".-->
2131 To Exit this screen and continue your Alpine session press "Return".
2135 ===== new_alpine_user_greeting ======
2138 <TITLE>NEW ALPINE USER GREETING</TITLE>
2141 <CENTER><<<This message will appear only once>>></CENTER>
2143 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
2144 Your Alpine configuration file indicates that you may have used Pine before
2146 If you are familiar with the way Pine works, you should be comfortable
2148 Your Pine configuration file is automatically used for Alpine.
2149 The Release Notes may be viewed by pressing
2150 "R" now or while in the MAIN MENU.
2152 <!--chtml if pinemode="phone_home"-->
2154 This software was originally created and maintained as a public
2155 service by the University of Washington until 2009; updates are made
2156 available as a public service of the Alpine community. It is always
2157 helpful to have an idea of how many users are using Alpine. Are you
2158 willing to be counted as an Alpine user? Pressing
2159 <A HREF="X-Alpine-Phone-Home:">Return</A>
2160 will send an anonymous (meaning, your real email address will not be revealed)
2161 message to the Alpine developers for purposes of tallying.
2163 <!--To Exit this screen and continue your Alpine session press "E".-->
2165 To Exit this screen and continue your Alpine session press "Return".
2169 ===== new_version_greeting ======
2172 <TITLE>NEW VERSION GREETING</TITLE>
2175 <CENTER><<<This message will appear only once>>></CENTER>
2177 <H1>Welcome to Alpine version <!--#echo var="ALPINE_VERSION"-->!</H1>
2178 Your Alpine configuration file indicates that you may not have used
2179 this version of Alpine before. This version's significant changes are
2180 documented in the Release Notes, which may be viewed by pressing
2181 "R" now or while in the MAIN MENU.
2183 <!--chtml if pinemode="phone_home"-->
2185 This software was originally created and maintained as a public
2186 service by the University of Washington until 2009; updates are made
2187 available as a public service of the Alpine community. It is always
2188 helpful to have an idea of how many users are using Alpine. Are you
2189 willing to be counted as an Alpine user? Pressing
2190 <A HREF="X-Alpine-Phone-Home:">Return</A>
2191 will send an anonymous (meaning, your real email address will not be revealed)
2192 message to the Alpine developers for purposes of tallying.
2194 <!--To Exit this screen and continue your Alpine session press "E".-->
2196 To Exit this screen and continue your Alpine session press "Return".
2201 ===== main_menu_tx ======
2204 <TITLE>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</TITLE>
2207 <H1>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</H1>
2209 Version <!--#echo var="ALPINE_VERSION"-->
2210 <!--chtml if pinemode="running"-->
2211 <BR>(built <!--#echo var=ALPINE_COMPILE_DATE-->)
2214 <CENTER>Copyright 2013-2018 Eduardo Chappa,
2215 <BR>Copyright 2006-2008 University of Washington.
2219 When you are viewing a help screen, there may be links to
2220 other topics highlighted (in Reverse video) in the text.
2222 The word "Introduction" in the TABLE OF CONTENTS below should be
2224 If you type carriage return (or V for View Link, see the commands at the
2225 bottom of the screen) you will be taken to a new help screen to view the
2227 The commands at the bottom of the screen should then include
2228 "P Prev Help".
2229 If you type "P" you will end up back here.
2230 If you type "E" for Exit, you will be back out of help and returned
2231 to the place you were in Alpine when you entered Help.
2232 In this case, you would go back to the MAIN MENU.
2233 There are also other links that are highlighted in bold (or the color used
2234 by your terminal to display bold).
2235 The items after the Introduction in the TABLE OF CONTENTS are all examples
2237 In order to view those links, you first have to make the link you want
2238 to view the current link.
2239 The "NextLink" and "PrevLink" commands
2240 (see bottom of screen) can do that for you.
2243 <H2>TABLE OF CONTENTS</H2>
2245 <LI> <A HREF="h_mainhelp_intro">Introduction</A>
2246 <LI> <A HREF="h_mainhelp_pinehelp">Alpine Help</A>
2247 <!--chtml if [ -r PINE_INFO_PATH ]-->
2248 <LI> <A HREF="h_mainhelp_localsupport">Local Support Contacts</A>
2250 <LI> <A HREF="h_mainhelp_cmds">Giving Commands in Alpine</A>
2251 <LI> <A HREF="h_mainhelp_config">Alpine Configuration</A>
2252 <LI> <A HREF="h_mainhelp_status">Titlebar Line</A>
2253 <LI> <A HREF="h_mainhelp_mainmenu">Main Menu</A>
2254 <LI> <A HREF="h_mainhelp_index">Index of Messages</A>
2255 <LI> <A HREF="h_mainhelp_reading">Reading Messages</A>
2256 <LI> <A HREF="h_mainhelp_composing">Composing Messages</A>
2257 <LI> <A HREF="h_mainhelp_readingnews">Reading News</A>
2258 <LI> <A HREF="h_mainhelp_abooks">Address Books</A>
2259 <LI> <A HREF="h_mainhelp_ldap">LDAP Directories</A>
2260 <LI> <A HREF="h_mainhelp_folders">Folders</A>
2261 <LI> <A HREF="h_mainhelp_collections">Collection Lists</A>
2262 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
2263 <LI> <A HREF="h_mainhelp_color">Color Setup</A>
2264 <LI> <A HREF="h_mainhelp_filtering">Filtering</A>
2265 <LI> <A HREF="h_mainhelp_roles">Roles</A>
2266 <LI> <A HREF="h_mainhelp_patterns">Patterns</A>
2267 <LI> <A HREF="h_mainhelp_keywords">Keywords (or Flags, or Labels)</A>
2268 <LI> <A HREF="h_mainhelp_mouse">Using a Mouse</A>
2269 <LI> <A HREF="h_mainhelp_cmdlineopts">Command Line Options</A>
2270 <LI> <A HREF="h_mainhelp_securing">Securing Your Alpine Session</A>
2271 <LI> <A HREF="h_mainhelp_smime">S/MIME</A>
2272 <LI> <A HREF="h_mainhelp_problems">Reporting Problems</A>
2273 <LI> <A HREF="X-Alpine-Config:">Show Supported Options in this Alpine</A>
2274 <LI> <A HREF="h_help_index">Index to Alpine's Online Help</A>
2278 <End of help on this topic>
2281 ===== h_mainhelp_intro ======
2284 <TITLE>Introduction</TITLE>
2287 <H1>Introduction</H1>
2289 Alpine is an "Alternatively Licensed Program for Internet
2290 News and Email" produced until 2009 by the University of Washington.
2291 It is intended to be an easy-to-use program for
2292 sending, receiving, and filing Internet electronic mail messages and
2293 bulletin board (Netnews/Usenet) messages. Alpine supports the following
2294 Internet protocols and specifications: SMTP (Simple Mail Transport Protocol),
2295 NNTP (Network News Transport Protocol), MIME (Multipurpose Internet Mail
2296 Extensions), IMAP (Internet Message Access Protocol), and LDAP (Lightweight
2297 Directory Access Protocol).<p>
2299 Although originally designed for inexperienced email users, Alpine has
2300 evolved to support many advanced features. There are an ever-growing
2301 number of configuration and personal-preference options, though which of
2302 them are available to you is determined by your local system managers.
2304 <H2>WHAT ALPINE DOES...</H2>
2306 Alpine is a "mail user agent" (MUA), which is a program that
2308 compose and read messages using Internet mail standards. (Whether you
2309 can correspond with others on the Internet depends on whether or not your
2310 computer is connected to the Internet.) Alpine also allows reading and
2311 posting messages on the Internet "net news" system, provided
2312 that your site operates a suitable news server.
2314 <H2>WHAT ALPINE DOES NOT DO...</H2>
2316 A "mail user agent" such as Alpine is just one part of a
2317 messaging system. Here are some things that are <B>not</B> done by Alpine,
2318 but require other programs:<P>
2320 <LI> Actual relaying of email... which is done by "message transfer
2322 <LI> Vacation messages... automatically responding to incoming messages
2323 <LI> Anything to do with "talk"... which has nothing to do with
2325 <LI> Anything to do with "irc"... which has nothing to do with email.
2326 <LI> List processing... resending one message to a list of recipients.
2330 <End of help on this topic>
2334 ===== h_mainhelp_pinehelp ======
2337 <TITLE>Alpine Help</TITLE>
2340 <H1>Alpine Help</H1>
2342 Alpine help is generally context-sensitive. In other words, each Alpine screen you
2343 use will have its own help text, explaining the choices available for that
2344 screen. This general help section, on the other hand, attempts to give an
2345 overall picture of what Alpine is capable of doing, as well as pointers to
2346 additional help sections about specific topics.<p>
2348 Much of the help text contains links to further help topics, similar to
2349 how the World Wide Web works.
2350 You may choose a link to view using the "NextLink" and
2351 "PrevLink" commands to change the link that is highlighted.
2352 The "View Link" command will then show you the highlighted link.
2353 Similar to the Back button in a web browser, the "Prev Help" command
2354 will return you to where you were before viewing the link, and "Exit Help"
2355 will return you to the location in Alpine before you asked for help.
2356 For example, if you are reading this text in Alpine you may return to the
2357 help table of contents with the "Prev Help" command or you may view the
2358 Release notes link in the next paragraph and then return here with
2359 "Prev Help".
2362 In addition to this general help on Alpine, <A HREF="h_news">Release Notes</A>
2363 on the current Alpine version are also available from the MAIN MENU: Press
2364 <!--chtml if pinemode="function_key"-->
2369 to browse the release notes. These include changes since the last release,
2370 configuration information, the history of the Alpine
2371 project, credits, and legal notices.
2373 Alpine releases are available via the world wide web at
2376 HREF="http://repo.or.cz/alpine.git">http://repo.or.cz/alpine.git</A></SAMP
2380 If you would like to print <EM>all</EM> of Alpine's internal help text
2381 (not recommended) for a little light bedtime reading, then press
2382 <!--chtml if pinemode="function_key"-->
2387 now. (This assumes that the
2388 copy of Alpine you are using has been properly configured for printing
2391 <End of help on this topic>
2394 ===== h_mainhelp_localsupport ======
2397 <TITLE>Local Support Contacts</TITLE>
2400 <H1>Local Support Contacts</H1>
2402 <!--chtml if [ -r PINE_INFO_PATH ]-->
2403 <!--#include file="PINE_INFO_PATH"-->
2405 No Local Support Contacts configured.
2409 <End of help on this topic>
2413 ===== h_mainhelp_cmds ======
2416 <TITLE>Giving Commands in Alpine</TITLE>
2419 <H1>Giving Commands in Alpine</H1>
2421 Unless configured otherwise
2422 (<A HREF="h_config_blank_keymenu"><!--#echo var="FEAT_disable-keymenu"--></A>)
2423 the bottom two lines of the screen are always used to list the
2424 commands you can give. You press the keys that are highlighted to give
2425 the command. The commands for getting help and going back to the main
2426 menu are always present (except when viewing help as you are now).
2427 <!--chtml if pinemode="function_key"-->
2430 Pressing O (meaning "Other Commands") changes the keys
2431 you see at the bottom of any screen. In some cases there are 3 or
2433 sets of keys that can be seen by using the O key. <EM>All commands are
2434 active</EM>, even if they are not currently showing at the bottom of your
2435 screen. In other words, you <EM>never</EM> need to press the O key, except to
2436 remind yourself of the proper key to press to perform an operation.
2438 <H2>Control Key Commands</H2>
2439 When composing mail, and in a few other places, in Alpine you
2440 have to use Control keys. This means pressing the Control key (usually labeled
2441 "Ctrl") and the
2442 letter indicated at the same time. Usually, this is shown with a
2443 "^" in front of the letter. On some systems, certain control
2444 characters are intercepted before they get to Alpine. As a work-around,
2445 you can press the ESCAPE key twice followed by the desired key. For
2446 example, if Ctrl-O (^O) does not work on your system, try typing
2447 "ESC ESC O".
2449 <H2>Paging Up and Down</H2>
2450 The "+" and "-" keys are used for
2451 moving to the next or previous page. The space bar is a synonym for
2452 "+". You may also use Ctrl-V to page down and Ctrl-Y to page
2453 up as you do in the message composer. On screens with a WhereIs (search)
2454 command, W or Ctrl-W followed by Ctrl-V will move to the bottom of the
2455 message or list, and W or Ctrl-W followed by Ctrl-Y will move to the top
2456 of the message or list.
2459 The return key is usually a synonym for a frequently used
2460 command. When viewing a message, there is currently not a default
2461 command, so RETURN does nothing; when in the index, it is synonymous with
2462 "view msg". In the key menu at the bottom of the screen, whatever is
2463 enclosed in square brackets [] is the same as the return key.
2465 <H2>Control Keys Not Used By Alpine</H2>
2466 Most commands in Alpine are single letters, with -- we hope -- some mnemonic
2467 value, but in places where Alpine is expecting text input, e.g. in the composer or
2468 at prompts for file/folder names, control keys must be used for editing and
2469 navigation functions.
2472 Alpine has used nearly all the control keys available. There are, however,
2473 certain control keys that are reserved by other programs or for technical
2474 reasons. Alpine does not use any of these keys:
2476 <DT>Ctrl-S</DT> <DD>Used by Unix as "stop output"</DD>
2477 <DT>Ctrl-Q</DT> <DD>Used by Unix as "resume output"</DD>
2478 <DT>Ctrl-]</DT> <DD>Often used by Telnet as escape key</DD>
2481 Note: Ctrl-S and Ctrl-Q can be subject to
2482 <A HREF="h_special_xon_xoff">special handling</A>.
2484 In addition, while the ESC key alone is not used for command input,
2485 Alpine will recognize two consecutive ESC key presses followed by a letter
2486 key as a substitute for control key input. For example, the control key
2487 <SAMP>Ctrl-X</SAMP> can alternatively be entered using the
2488 three keystrokes: <SAMP>ESC ESC x</SAMP>.
2489 This is useful if the communication program you are using
2490 (e.g. Telnet) has its own, conflicting, idea of what certain control
2494 <H2>Repainting the Screen</H2>
2495 Sometimes what is displayed on the screen will be
2496 incorrect due to noise on the phone line or other causes and you will want
2497 to repaint the whole screen to make it correct. You can use the Ctrl-L
2498 command to do this. It never hurts to do it when in doubt.
2501 <End of help on this topic>
2504 ===== h_mainhelp_status ======
2507 <TITLE>Titlebar Line</TITLE>
2510 <H1>Titlebar Line</H1>
2512 The top line of the screen is Alpine's titlebar line. It will always display
2513 the current version of Alpine and will also convey information about the
2514 status of the program. This is where you look to find out what
2515 collection, folder and message number is active and where you are in Alpine.
2518 If the titlebar line says "READONLY" it means that the open folder
2519 (typically your INBOX) is "locked" by another mail session --
2520 most likely a more recent session of Alpine has taken the INBOX lock.
2523 If the titlebar line says "CLOSED" it means that you are trying to
2525 folder on a remote mail server, and for some reason, communication with
2526 the mail server has either been lost, or never successfully established.
2527 This can be a result of trying to open a non-existent folder, or one
2528 stored on an invalid or non-operational server, or it can mean that Alpine
2529 has been suspended for more that 30 minutes while accessing a remote mail
2533 <End of help on this topic>
2536 ===== h_mainhelp_mainmenu ======
2539 <TITLE>Main Menu</TITLE>
2544 The Main Menu lists Alpine's main options.
2545 The key or keys you must type to enter your
2546 choice are to the left of each option or command name.
2547 You can type either uppercase or lowercase letters,
2548 and you should not press <Return> after typing the
2549 letter (unless you are specifically asking for the default,
2550 highlighted command).
2553 From the Main Menu you can choose to read online help, write (compose) and
2554 send a message, look at an index of your mail messages, open or maintain
2555 your mail folders, update your address book, configure Alpine, and quit Alpine.
2556 There are additional options listed at
2557 the bottom of the screen as well.
2560 The Help command usually returns context-sensitive help information.
2561 However, in the Main Menu you get the most general help, which includes
2562 a Table of Contents.
2563 The last entry in the Table of Contents is an Index of help topics,
2564 so this is a good place to go if you are having trouble finding how
2567 <H2>Main Menu Commands</H2>
2568 The Alpine main menu lists the most common Alpine functions. A <a
2569 href="h_main_menu_commands">full list of these
2570 commands</a> and what they do is available.
2572 <End of help on this topic>
2575 ===== h_mainhelp_abooks ======
2578 <TITLE>Address Books</TITLE>
2581 <H1>Address Books</H1>
2584 As you use email, you can build a list of your regular email correspondents
2586 Address Book. At the Alpine MAIN MENU, press A to see the Address Book List
2588 personal address book will be highlighted. Press <Return> to view it.
2589 You can use the address book to store email addresses for individuals or
2590 groups, to create easily
2591 remembered "nicknames" for these addresses, and to quickly retrieve an email
2592 address when you are composing a message.
2594 There are two ways to add addresses to your address book: you can add them
2595 manually or take them from messages (by pressing T to access the Take command).
2596 With either method, you specify nicknames for your correspondents. A single
2597 address book entry (or nickname) can point to just one email address, or, it can
2598 point to more than one. When it points to more than one, it is called a
2599 distribution list. Each distribution list has a nickname, a full name, and a
2600 list of addresses. These
2601 addresses may be actual addresses, other nicknames in your address book, or
2606 Additional information is available in Alpine's online help:
2608 <li><a href="h_abook_opened">The Alpine Address Book</a></li>
2611 <End of help on this topic>
2614 ===== h_mainhelp_ldap ======
2622 LDAP (Lightweight Directory Access Protocol) is a standard means of accessing
2623 an organization's shared
2624 directories. Essentially, using LDAP, Alpine is able to find email addresses in
2626 books, rather like the White Pages provided by the phone company. As an Alpine
2628 necessary to know much about how this works, only how to use it and how to
2632 More information on configuring LDAP is available in Alpine's online help:
2634 <li><a href="h_direct_config">Setup LDAP Directory Servers</a></li>
2637 Additional help on using LDAP in Alpine is also available:
2639 <li><a href="h_ldap_view">LDAP Response View Explained</a></li>
2642 <End of help on this topic>
2645 ===== h_mainhelp_index ======
2648 <TITLE>Index of Messages</TITLE>
2651 <H1>Index of Messages</H1>
2653 In Alpine's message index, the selected message is highlighted. The first
2654 column on the left is blank, shows a "+" if the message was
2655 sent directly to you (i.e., it is not a
2656 copy or from a list), or a "-" if you were explicitly Cc'd.
2658 The second column may be blank, or it may contain:
2660 <li>"N" if the message is new (unread), </li>
2661 <li>"A" if you have answered the message (using the Reply command), </li>
2662 <li>"D" if you have marked the message for deletion.</li>
2666 Note: If you answer a message as well as mark it deleted (in either order),
2667 you will only see the "D".
2670 The rest of the columns in the message line show you the message
2671 number, date sent, sender, size, and subject. For details, press ? (Help).
2672 The behavior and appearance of the Index screen is highly configurable.
2673 In the Setup/Config screen search (with the WhereIs command) for options
2674 that contain the words "index" or "thread" to see
2675 many of the configuration possibilities.
2677 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
2678 option may be used to configure the look of the standard MESSAGE INDEX lines
2679 in many different ways.
2680 Find <!--#echo var="VAR_index-format"--> in the Setup/Config screen and
2681 read the help text there for more information.
2683 Most of the commands you need to handle your messages are visible at the
2684 bottom of the screen, and you can press O (OTHER CMDS) to see additional
2685 commands that are available.
2686 You do not need to see these "other commands"
2687 on the screen to use them. That is, you never need to press O as a prefix
2688 for any other command.
2691 Additional information is available in Alpine's online help:
2693 <li><a href="h_mail_index">Message Index Commands</a></li>
2696 <End of help on this topic>
2699 ===== h_mainhelp_reading ======
2702 <TITLE>Reading Messages</TITLE>
2705 <H1>Reading Messages</H1>
2707 The message text screen shows you the text of the message along with
2708 its header. If a message has attachments, those will be listed (but not
2709 displayed) also. The titlebar line displays information about the currently
2710 open message, folder and collection. You see the name of the collection
2711 (if there is one) in angle brackets, then the name of the folder, then the
2712 message number and finally the position within the current message (in
2713 percent). If the message is marked for deletion
2714 "DEL" will appear in the
2715 upper right as well.
2718 As with every Alpine screen, the bottom two lines show you the commands
2721 <P>Additional information is available in Alpine's online help:
2723 <li><a href="h_mail_view">Message Text Screen</a></li>
2724 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a></li>
2725 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a></li>
2728 <End of help on this topic>
2731 ===== h_mainhelp_composing ======
2734 <TITLE>Composing Messages</TITLE>
2737 <H1>Composing Messages</H1>
2739 To write a message, press C (Compose). You see the Compose Message
2740 screen, which is divided into two parts: the header area and the message
2741 text area. The header area is where information on the recipient (the To:
2742 field) and the subject line go, while the message text area contains the
2743 actual text of the email message. Different commands are available to you
2744 when your cursor is in different areas on this screen. To see additional
2745 help on commands in either the message text or header area, type
2746 <Control>G (Get help).
2749 To move around, use the arrow keys or Ctrl-N (Next line) and Ctrl-P
2750 (Previous line); to correct typing errors, use <Backspace> or <Delete>.
2752 <P>The following information from Alpine's online help may prove useful:
2754 <li><a href="h_composer_to">Message Header Commands</a></li>
2755 <li><a href="h_compose_richhdr">Rich Header Command</a></li>
2756 <li><a href="h_composer">Composer Commands</a></li>
2757 <li><a href="h_edit_nav_cmds">Composer Editing Commands</a></li>
2758 <li><a href="h_config_change_your_from">Changing your From Address</a></li>
2759 <li><a href="h_compose_send">Send Command</a></li>
2760 <li><a href="h_compose_spell">Spell Check Command</a></li>
2763 <End of help on this topic>
2766 ===== h_mainhelp_collections ======
2769 <TITLE>Collection Lists</TITLE>
2772 <H1>Collection Lists</H1>
2774 Collection lists are Alpine's way of organizing groups of folders. Each
2775 "collection" can reside on a different server, for example, and contain a
2776 different group of mail folders.
2779 For more information on this, see:
2781 <li><a href="h_what_are_collections">Folder Collections Explained</a></li>
2784 Additional information relating to collection lists is also available in
2788 <li><a href="h_collection_maint">Setup Collection List Screen</a></li>
2789 <li><a href="h_collection_screen">Collection List Screen</a></li>
2792 <End of help on this topic>
2795 ===== h_mainhelp_folders ======
2798 <TITLE>Folders</TITLE>
2803 Messages can quickly accumulate in your INBOX folder. If you use email
2804 often, you soon could have hundreds. You need to delete messages you do
2805 not want, and you can use folders to organize messages you wish to save. A
2806 folder is a collection of one or more messages that are stored (just like
2807 the messages in your INBOX) so you can access and manage them.
2810 You can organize your email messages into different folders by topic,
2811 correspondent, date, or any other category that is meaningful to you. You
2812 can create your own folders, and Alpine automatically provides three:
2814 <li>The INBOX folder: messages sent to you are listed in this folder.
2815 When you first start Alpine and go to the Message Index screen, you are
2816 looking at the list of messages in your INBOX folder. Every incoming
2817 message remains in your INBOX until you delete it or save it in another
2819 <li>The sent-mail folder: copies of messages you send are stored in this
2821 convenient if you cannot remember whether you actually sent a message and want
2823 if you want to send a message again.</li>
2824 <li>The saved-messages folder: copies of messages you save are stored in this
2826 unless you choose to save them to other folders you create yourself.</li>
2830 More information about folders is available in Alpine's online help:
2832 <li><a href="h_folder_open">Explanation of Folder Selection</a></li>
2833 <li><a href="h_folder_maint">Help for Folder List</a></li>
2834 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a></li>
2835 <li><a href="h_folder_fcc">Folder Select for Fcc ("sent-mail")
2837 <li><a href="h_folder_save">Folder Select for Save Explained</a></li>
2840 <End of help on this topic>
2843 ===== h_mainhelp_color ======
2846 <TITLE>Color</TITLE>
2851 If the terminal emulator you are using is capable of displaying color or if
2852 you are using PC-Alpine, then it is possible to set up Alpine so that various
2853 parts of the display will be shown in colors you configure. This is done
2854 using the Setup Color screen, available from the MAIN MENU by selecting
2855 the Setup command followed by "K" for Kolor (because "C"
2856 stands for Config in this context).
2859 For example, you may color things like the titlebar, the current item,
2860 the keymenu, and the status messages.
2861 You may also color lines in the index, and headers and quoted text in the
2862 MESSAGE TEXT screen.
2863 You use the Color Setup screen for configuring most of this, but you must
2864 use the IndexColor setup for coloring whole index lines.
2865 These are available from the MAIN MENU under Setup/Kolor and Setup/Rules/IndexColor.
2868 The following entries in Alpine's online help provide additional information
2869 about how to use color:
2871 <LI> <A HREF="h_color_setup">Color Setup screen</A>
2872 <LI> <A HREF="h_rules_incols">Index Line Color</A>
2873 <LI> <A HREF="h_config_quote_color">quoted text</A> in message view
2874 <LI> <A HREF="h_config_customhdr_pattern">text associated with user-defined headers</A> in message view
2877 <End of help on this topic>
2880 ===== h_mainhelp_mouse ======
2883 <TITLE>Using a Mouse</TITLE>
2886 <H1>Using a Mouse</H1>
2888 If you are using PC-Alpine mouse support is turned on automatically.
2889 If you are using UNIX Alpine within an X terminal window or within
2890 a terminal emulator that supports an xterm-style mouse, then you may
2891 turn on support for the mouse with the feature
2892 <A HREF="h_config_enable_mouse"><!--#echo var="FEAT_enable-mouse-in-xterm"--></A>.
2893 For UNIX Alpine you will also need to set the $DISPLAY environment variable.
2895 PC-Alpine offers considerable mouse support. You can view what is
2896 "clickable" by dragging your mouse over any screen; when the
2897 arrow cursor changes into a hand, you found something. Mouse-click
2898 possibilities include navigating between screens and folders and
2899 double-clicking on hyperlinks to open your Web browser.
2900 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
2901 screen. Examples of right-click options include "copy" after
2902 selecting text to copy and "View in New Window" when you click
2903 on a particular message in the Message Index. The menu choices available
2904 to you will vary based upon what screen is open, where on the screen your
2905 cursor is located, and even what action you have already taken.
2906 Within a folder, you may set the "Important" flag on any
2909 X terminal mouse support is more limited but still quite powerful.
2910 As with PC-Alpine, clicking on any of the commands in the keymenu at
2911 the bottom of the screen will execute that command as if you typed it.
2912 Double-clicking on a link, for example the link to the
2913 <!--#echo var="FEAT_enable-mouse-in-xterm"--> feature in the paragraph above,
2914 will take you to that link.
2915 Double-clicking on an index line will view the message, and so on.
2917 <End of help on this topic>
2920 ===== h_mainhelp_keywords ======
2923 <TITLE>Keywords</TITLE>
2928 Within a folder, you may set the "Important" flag on any
2930 This doesn't have any system-defined meaning and is only called
2931 the Important flag because many users use it to signify that a message
2932 is important to them in some way.
2934 You may also define your own set of keywords.
2935 You might know these as user defined flags or as labels.
2936 These are similar to the Important flag but you choose the names for yourself.
2938 Alpine will only display keywords that
2939 have been added by you in the Flag Details screen or
2940 that have been configured by you using the Setup/Config option
2941 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
2942 Keywords set by other means (for example, by another email client) will not
2943 show up in Alpine unless you configure Alpine to know about them.
2944 They will show up in the Flag Details screen, but will not show up, for example,
2948 The following entries in Alpine's online help provide additional information
2949 about how to use keywords:
2951 <li><A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--> config option</A></li>
2952 <li><A HREF="h_common_flag">Flag command to set keywords</A></li>
2955 <End of help on this topic>
2958 ===== h_mainhelp_roles ======
2961 <TITLE>Roles</TITLE>
2966 You may play different roles depending on who you are replying to. For
2967 example, if you are replying to a message addressed to help-desk you may
2968 be acting as a Help Desk Worker. That role may require that you use a
2969 different return address and/or a different signature.
2972 To configure roles, go to the MAIN MENU and use the Setup command
2973 followed by "Rules" and then "Roles".
2974 The following entries in Alpine's online help provide additional information
2978 <li><a href="h_rules_roles">Setup Roles Screen</a></li>
2979 <li><a href="h_role_select">Roles Screen</a></li>
2982 <End of help on this topic>
2985 ===== h_mainhelp_filtering ======
2988 <TITLE>Filtering</TITLE>
2993 The software that actually delivers mail (the stuff that happens
2994 before Alpine is involved) for you is in a better position to do mail filtering
2996 If possible, you may want to look into using that sort of mail filtering to
2997 deliver mail to different folders, delete it, or forward it.
2998 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
3001 Filtering is a way to automatically move certain messages from one folder
3002 to another or to automatically delete messages.
3003 You may also automatically set the state (Important, New, Deleted, Answered) of messages
3004 and set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
3005 Alpine doesn't have the ability to forward mail to another address or
3006 to deliver vacation messages.
3009 To configure filtering, go to the MAIN MENU and use the Setup command
3010 followed by "Rules" and then "Filters".
3011 The following entries in Alpine's online help provide additional information
3012 about how to use filtering:
3014 <LI> <A HREF="h_rules_filter">Filtering Setup screen</A>
3017 <End of help on this topic>
3020 ===== h_mainhelp_patterns ======
3023 <TITLE>Patterns</TITLE>
3028 Patterns are used with Roles, Filtering, Index Coloring,
3029 Scoring, Other Rules, and Search Rules, so it may help you to understand exactly how Patterns work.
3030 The following entries in Alpine's online help provide information
3031 about using Patterns:
3033 <LI> <A HREF="h_rule_patterns">Patterns</A>
3036 <End of help on this topic>
3039 ===== h_mainhelp_cmdlineopts ======
3042 <TITLE>Command Line Options</TITLE>
3045 <H1>Command Line Options</H1>
3047 Alpine accepts a number of command line arguments, allowing you, for
3048 example, to start Alpine and immediately access a particular folder.
3049 Many of these arguments overlap with options in the Alpine configuration file.
3050 If there is a difference, then an option set on the command line takes
3052 Alpine expects command line arguments (other than addresses) to be
3053 preceded by a "-" (dash) as normally used by UNIX programs.
3054 A <a href="h_command_line_options">full list</a> of command line
3055 possibilities is available.
3057 <End of help on this topic>
3060 ===== h_mainhelp_config ======
3063 <TITLE>Alpine Configuration</TITLE>
3066 <H1>Alpine Configuration</H1>
3068 Unless it has been administratively disabled, the Setup command on the
3069 MAIN MENU has several subcommands that allow you to modify Alpine's behavior.
3070 The possible subcommands are for general Configuration settings,
3071 Printer settings, Changing your Password, Signature setup,
3072 AddressBook setup, Collection Lists setup, Rules (including Roles, Filters,
3073 Scores, Search, Indexcolor, and Other rules), LDAP Directory setup,
3074 and Color configuration.
3075 In particular, the "Config" subcommand has many features you may
3076 set or unset and many other configuration variables that may be set to change
3077 the way Alpine works.
3078 Every one of the hundreds of options available in that configuration settings
3079 screen has help text associated with it.
3080 You may read that text by moving the cursor to highlight the option and then
3081 typing the Help command.
3083 These settings are stored in your personal
3084 "pinerc" configuration file (or, optionally, they may be stored
3085 <A HREF="h_config_remote_config">remotely</A>),
3086 but on shared systems these settings
3087 may be over-ridden by a system-wide control file (due to local site
3088 security or support policies). A global pine configuration file can also
3089 be used to set default values for all Alpine users on a particular system.
3090 Power users may be interested in splitting their personal configuration
3091 data into two pieces, a generic piece and
3092 <A HREF="h_config_exceptions">exceptions</A> which apply to
3093 a particular platform.
3094 They may also be interested in <A HREF="h_config_inheritance">configuration inheritance</A>.
3095 General Alpine configuration information can be found
3096 <A HREF="h_news_config">here</A>.
3098 <End of help on this topic>
3101 ===== h_mainhelp_aggops ======
3104 <TITLE>Aggregate Operations</TITLE>
3107 <H1>Aggregate Operations</H1>
3109 When you are in the MESSAGE INDEX, the available commands
3110 (for example, Delete, Undelete, Save, Reply, and so on)
3111 normally act on a single message.
3112 So, for example, if you press the Delete command, the currently highlighted
3113 message is marked Deleted.
3114 These commands that normally act on a single message may be applied to
3115 several messages at once instead.
3117 By default this feature is turned on, but it could be administratively turned
3118 off to reduce complexity.
3120 <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>
3121 in the Setup/Config screen is used to turn it off or on.
3122 When this feature is turned on, the four commands "Select",
3123 "SelectCur", "ZoomMode", and "Apply"
3125 The two selection commands allow you to mark a set of
3126 messages as being "selected".
3127 The "ZoomMode" command will toggle between
3128 displaying only the selected messages and displaying all the messages.
3129 The "Apply" command allows you to
3130 apply one of the regular MESSAGE INDEX commands to all of the selected
3131 messages instead of to only the highlighted message.
3133 An example aggregate operation would be to catch up when reading
3135 That is, get rid of all the messages in the news group so that you can
3137 The easiest way to do this in Alpine is to use aggregate operations.
3138 You want to Delete all of the messages in the group.
3139 You could start at the top and type "D" once for every message.
3140 A much faster method is to first Select all of the messages in the group,
3141 and then Delete all of them.
3142 This would take four keystrokes:
3144 <CENTER><SAMP>; a (to select all messages)</SAMP></CENTER>
3146 <CENTER><SAMP>a d (to delete all selected messages)</SAMP></CENTER>
3148 Another use of Select is to use it for searching for a particular message
3149 or set of messages in a large folder.
3150 You may know that the message was From a certain user.
3151 You could select all messages from that user to start, and use Zoom to
3152 look at only those messages.
3153 If there were still too many messages to look at you could Narrow the
3154 set of messages further by selecting from all of those messages only
3155 the ones that were after a certain date, or contained a particular phrase
3156 in the Subject, or were too a particular address, and so on.
3157 That may be the end of what you are doing, or you may want to use Apply to
3158 Save or Forward or Print all of the selected messages.
3160 Some related help topics are
3162 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
3163 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
3164 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
3165 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
3166 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
3167 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
3170 <End of help on this topic>
3173 ===== h_mainhelp_readingnews ======
3176 <TITLE>Reading News</TITLE>
3179 <H1>Reading News</H1>
3182 Alpine can read and post to Internet (or USENET) newsgroups, using the same
3183 commands as for mail. Similar to mailing lists but existing on a larger scale,
3184 Usenet newsgroups allow groups of people with common interests to discuss
3185 particular topics. You might find newsgroups related to your career, or you
3186 might wish to check out the online discussion among the fans of your favorite
3189 <H2>Configuring Alpine for Reading News</H2>
3190 Alpine often arrives
3191 pre-configured by your system administrator to automatically access the
3192 newsgroups offered by your organization, Internet Service Provider, or
3193 school. PC-Alpine users, and those attempting to customize Unix Alpine, will
3194 need additional details on <a href="h_configuring_news">how to
3195 configure Alpine to read news</a>.
3197 <H2>Accessing Newsgroups</H2>
3198 The first step in reading news is to access the newsgroups collections
3199 screen from Alpine. If everything is configured properly, you should be able
3200 to do this by first typing L (folder List), then selecting the folder
3201 collection listed as "News." The actual name of this collection may differ
3202 from system to system.
3204 <H2>Subscribing to Newsgroups</H2>
3206 Once you have accessed the news collection, you need to subscribe to a
3207 newsgroup that interests you. Subscribing to a newsgroup means that Alpine
3208 will keep a record of the newsgroups in which you are interested and which
3209 articles in those newsgroups have been read.
3211 <H2>Using Newsgroups</H2>
3212 Alpine uses the similar commands to read news as to read mail. For example,
3213 the D command marks messages as Deleted (or "Dismissed," if you prefer),
3214 and the R command Replies to a news posting. Basically, Alpine allows you to
3215 read news as if it were mail, so you don't need to change the way you
3216 interact with Alpine.
3218 There is also additional Alpine help available on
3219 <A HREF="h_reading_news">how to use Alpine to read news</A>.
3221 <End of help on this topic>
3224 ===== h_mainhelp_securing ======
3227 <TITLE>Securing your Alpine Session</TITLE>
3230 <H1>Securing your Alpine Session</H1>
3232 By default, Alpine will attempt to connect to an IMAP server on the normal
3233 IMAP service port (143).
3234 If the Alpine you are using has been built to
3235 support "Transport Layer Security" (TLS)
3236 and "Secure Sockets Layer" (SSL)
3237 (check by clicking <A HREF="X-Alpine-Config:">here</A>),
3238 and the server offers the STARTTLS capability, then a secure (encrypted)
3239 session will be established.
3241 When you are connected to a remote folder the titlebar will contain a plus sign
3242 in the far right column if the connection is encrypted using TLS or SSL.
3243 Similarly, when you are being prompted for a password a plus sign will appear in the prompt
3244 if the connection is encrypted.
3246 <H2>More Information on Alpine with SSL and TLS</H2>
3248 <LI> <A HREF="h_release_tlscerts">TLS and SSL Usage Note</A> </LI>
3249 <LI> <A HREF="h_folder_server_syntax">/SSL</A> option for older servers which support port 993 SSL but not TLS </LI>
3250 <LI> <A HREF="h_config_alt_auth"><!--#echo var="FEAT_try-alternative-authentication-driver-first"--></A> feature </LI>
3251 <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>
3253 <H2>Here are some other security-related features and options</H2>
3256 <LI> <A HREF="h_config_disable_password_caching"><!--#echo var="FEAT_disable-password-caching"--></A> feature to disable password caching </LI>
3257 <LI> <A HREF="h_config_disable_password_file_saving"><!--#echo var="FEAT_disable-password-file-saving"--></A> Disable password file saving</LI>
3258 <LI> <A HREF="h_config_mailcap_params"><!--#echo var="FEAT_enable-mailcap-param-substitution"--></A> feature </LI>
3259 <LI> <A HREF="h_config_disable_auths"><!--#echo var="VAR_disable-these-authenticators"--></A> option </LI>
3262 <End of help on this topic>
3265 ===== h_mainhelp_problems ======
3268 <TITLE>Reporting Problems</TITLE>
3271 <H1>Reporting Problems</H1>
3273 We ask that you first read the relevant help screens and then seek
3274 assistance from your own local support staff. Once you are sure that your
3275 difficulty is not a local configuration problem, you might look at the
3276 help section explaining where to look for
3277 <A HREF="h_finding_help">more information</A> and where to
3282 Eduardo Chappa <chappa@gmx.com>
3286 <End of help on this topic>
3289 ===== h_main_menu_commands ======
3292 <TITLE>MAIN MENU COMMANDS</TITLE>
3295 <H1>MAIN MENU COMMANDS</H1>
3297 <!--chtml if pinemode="function_key"-->
3298 Available Commands --
3299 Group 1 Available Commands -- Group 2<BR>
3300 ------------------------------
3301 --------------------
3303 F1 Show this help text F1 Show this help text<BR>
3304 F2 Show all other available commands F2 Show other commands<BR>
3305 F3 Quit Alpine<BR>
3306 F4 Execute current MAIN MENU command F4 <A
3307 HREF="h_common_compose">Compose</A> a message<BR>
3308 F5 Select previous command up on menu F5 <A
3309 HREF="h_common_folders">FOLDER LIST</A> screen<BR>
3310 F6 Select next command down on menu F6 <A
3311 HREF="h_common_goto">Goto</A> a specified folder<BR>
3312
3313 F7 <A
3314 HREF="h_common_index">MESSAGE INDEX</A> screen<BR>
3315
3316 F8 <A
3317 HREF="h_main_journal">Journal</A> of status messages<BR>
3318 F9 Display <A
3319 HREF="h_main_release_notes">Release Notes</A> notes F9 <A
3320 HREF="h_main_setup">SETUP</A> menus<BR>
3322 HREF="h_main_kblock">Lock Keyboard</A> F10 <A
3323 HREF="h_main_addrbook">ADDRESS BOOK</A> screen<BR>
3324
3326 HREF="h_common_role">Compose message using a role</a><BR>
3328 General Alpine Commands Main Menu Screen Commands<BR>
3329 --------------------- --------------------------<BR>
3330 ? Show Help Text O Show all Other available commands<BR>
3331 C <A
3332 HREF="h_common_compose">Compose</A> a message P Select Previous command up on menu<BR>
3333 I <A
3334 HREF="h_common_index">MESSAGE INDEX</A> screen N Select Next command down on menu<BR>
3335 L <A
3336 HREF="h_common_folders">FOLDER LIST</A> screen R Display Alpine <A HREF="h_main_release_notes">Release Notes</A><BR>
3337 A <A
3338 HREF="h_main_addrbook">ADDRESS BOOK</A> screen K <A
3339 HREF="h_main_kblock">Lock Keyboard</A><BR>
3340 S <A
3341 HREF="h_main_setup">SETUP</A> functions G <A
3342 HREF="h_common_goto">Goto</A> a specified folder<BR>
3343 Q Quit Alpine J <A HREF="h_main_journal">Journal</A> of status messages<BR>
3344 # <A
3345 HREF="h_common_role">Compose message using a role</a><BR>
3351 <LI>For help on a particular command, highlight the bold text associated
3352 with it above and hit Return.
3353 <LI> The availability of certain commands (e.g. some of the options under
3354 SETUP) is determined by Alpine configuration files and system capabilities.
3355 At some sites, certain commands may not be available due to security or
3359 <End of help on this topic>
3363 ===== h_command_line_options ======
3366 <TITLE>COMMAND LINE OPTIONS</TITLE>
3369 <H1>COMMAND LINE OPTIONS</H1>
3370 Possible starting arguments for Alpine:
3374 <DT> <EM>[addresses]</EM>
3376 <DD> Send-to: If you give <EM>Alpine</EM> an argument or arguments which
3377 do not begin with a dash, <EM>Alpine</EM> treats them as email addresses.
3378 <EM>Alpine</EM> will startup in
3379 the composer with a message started to the addresses specified.
3380 Once the message is sent, the <EM>Alpine</EM> session closes.
3381 Standard input redirection is allowed.
3382 Separate multiple addresses with a space between them.
3383 Addresses are placed in the "To" field only.
3386 <DT> < <EM>file</EM>
3388 <DD> <EM>Alpine</EM> will startup in the composer with <EM>file</EM> read
3389 into the body of the message.
3390 Once the message is sent, the <EM>Alpine</EM> session closes.
3393 <DT> -attach <EM>file</EM>
3395 <DD> Go directly into composer with given file attached.
3398 <DT> -attachlist <EM>file-list</EM>
3400 <DD> Go directly into composer with given files attached.
3401 This must be the last option on the command line.
3404 <DT> -attach_and_delete <EM>file</EM>
3406 <DD> Go directly into composer with given file attached, delete when finished.
3409 <DT> -aux <EM>local_directory</EM>
3411 <DD> <EM>PC-Alpine</EM> only.
3412 This tells <EM>PC-Alpine</EM> the local directory to use for storing auxiliary
3413 files, like debug files, address books, and signature files. The pinerc may
3419 <DD> If the personal configuration file doesn't already exist, exit.
3420 This might be useful if the configuration file is accessed using some
3421 remote filesystem protocol. If the remote mount is missing this will cause
3422 <EM>Alpine</EM> to quit instead of creating a new pinerc.
3427 <DD> When used with the <CODE>-f</CODE> option, apply the <EM>n</EM>th context.
3428 This is used when there are multiple folder collections (contexts) and you
3429 want to open a folder not in the primary collection.
3434 <DD> Configuration: Prints a sample system configuration file to the
3435 screen or standard output. To generate an initial system configuration
3439 pine -conf > <!--#echo var="PINE_CONF_PATH"-->
3443 To generate a system configuration file using settings from an old
3444 system configuration file, execute
3447 pine -P old-pine.conf -conf > <!--#echo var="PINE_CONF_PATH"-->
3450 A system configuration file is not required.
3453 <DT> -copy_abook <<EM>local_abook_file</EM>> <<EM>remote_abook_folder</EM>>
3455 <DD> Copy an address book file to a remote address book folder.
3456 If the remote folder doesn't exist, it will be created.
3457 If it exists but the first message in the folder isn't a remote address
3458 book header message, the copy will be aborted.
3459 This flag will not usually be used by a user.
3460 Instead, the user will create a remote address book from within <EM>Alpine</EM>
3461 and copy entries from the local address book by using aggregate Save in
3462 the address book screen.
3465 <DT> -copy_pinerc <<EM>local_pinerc_file</EM>> <<EM>remote_pinerc_folder</EM>>
3467 <DD> Copy a pinerc configuration file to a remote pinerc folder.
3468 If the remote folder doesn't exist, it will be created.
3469 If it exists but the first message in the folder isn't a remote pinerc
3470 header message, the copy will be aborted.
3471 This flag may be useful to users who already have a local pinerc file and
3472 would like to convert it to a remote pinerc folder and use that instead.
3473 This gives a way to bootstrap that conversion without having to manually
3474 reset all of the variables in the remote pinerc folder.
3477 <DT> -d <EM>debug-level</EM>
3479 <DD> Debug Level: Sets the level of debugging information written by
3481 <EM>debug-level</EM> can be set to any integer 0-9.
3482 A debug level of 0 turns off debugging for the session.
3483 (Actually there are some levels higher than 9, but you probably don't
3487 <DT> -d <EM>keywords</EM>
3489 <DD> You may use a more detailed version of the debugging flag to set
3490 the debug level in separate parts of <EM>Alpine</EM>.
3491 The possibilities are flush, timestamp, imap=0..4, tcp, numfiles=0..31, and
3493 <EM>Flush</EM> causes debugging information to be flushed immediately to
3494 the debug file as it is written.
3495 <EM>Verbose</EM> is the general debugging verbosity level.
3496 <EM>Timestamp</EM> causes timestamps to be added to the debug file, which
3497 is useful when you are trying to figure out what is responsible for delays.
3498 <EM>Numfiles</EM> sets the number of debug files saved.
3499 <EM>Imap</EM> sets the debug level for the debugging statements related
3500 to the conversation with the IMAP server, and more generally, for the
3501 debugging related to <EM>Alpine</EM>'s interaction with the C-Client library.
3502 <EM>Tcp</EM> turns on some TCP/IP debugging.
3505 <DT> -f <EM>folder</EM>
3507 <DD> Startup folder: <EM>Alpine</EM> will open this folder in place
3508 of the standard INBOX.
3511 <DT> -F <EM>file</EM>
3513 <DD> Open named text file for viewing and forwarding.
3518 <DD> Help: Prints the list of available command-line arguments to the
3524 <DD> <EM>Alpine</EM> will start up in the FOLDER INDEX
3525 screen instead of the MAIN MENU.
3528 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"-->=i</EM>.
3531 <DT> -I <EM>a,b,c,...</EM>
3533 <DD> Initial Keystrokes: <EM>Alpine</EM> will execute this comma-separated
3534 sequence of commands upon startup.
3535 This allows users to get <EM>Alpine</EM> to start in any
3536 of its menus/screens.
3537 You cannot include any input to the composer in the initial keystrokes.
3538 The key <Return> is represented by a ``CR'' in
3539 the keystroke list; the spacebar is designated by the letters ``SPACE''.
3540 Control keys are two character sequences beginning with ``^'', such as
3542 A tab character is ``TAB''.
3543 Function keys are ``F1'' - ``F12'' and the arrow keys are ``UP'',
3544 ``DOWN'', ``LEFT'', and ``RIGHT''.
3545 A restriction is that you can't mix function keys and character keys in this
3546 list even though you can, in some cases, mix them when running <EM>Alpine</EM>.
3547 A user can always use only <EM>character</EM> keys in the startup list even
3548 if he or she is using <EM>function</EM> keys normally, or vice versa.
3549 If an element in this list is a string of characters surrounded by double
3550 quotes (") then it will be expanded into the individual characters in
3551 the string, excluding the double quotes.
3554 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"--></EM>
3559 <DD> For <EM>PC-Alpine</EM> only, this option prompts the user for
3560 some basic information to help with getting properly set up.
3565 <DD> Function-Key Mode: When invoked in this way, <EM>Alpine</EM> expects
3566 the input of commands to be function-keys.
3567 Otherwise, commands are linked to the regular character keys.
3570 Configuration equivalent: <EM><!--#echo var="FEAT_use-function-keys"--></EM> included in
3571 <EM>Feature-List</EM>.
3576 <DD> Message-Number: When specified, <EM>Alpine</EM> starts up in the
3577 FOLDER INDEX screen with the current message being the specified
3583 <DD> <EM>PC-Alpine</EM> only.
3584 This tells <EM>PC-Alpine</EM> not to display the splash screen upon startup.
3585 This may be helpful for certain troubleshooting or terminal server scenarios.
3588 <DT> -o <EM>folder</EM>
3590 <DD> Opens the INBOX (or a folder specified via the -f argument) ReadOnly.
3593 <DT> -p <EM>pinerc</EM>
3595 <DD> Uses the named file as the personal configuration file instead of
3596 <EM>~/.pinerc</EM> or the default PINERC search sequence <EM>PC-Alpine</EM> uses.
3597 Alpinerc may be either a local file or a remote configuration folder.
3600 <DT> -P <EM>pinerc</EM>
3602 <DD> Uses the named file as the system wide configuration file instead of
3603 <EM><!--#echo var="PINE_CONF_PATH"--></EM> on UNIX, or nothing on <EM>PC-Alpine</EM>.
3604 Alpinerc may be either a local file or a remote configuration folder.
3607 <DT> -passfile <EM>passfile</EM>
3609 <DD> This tells <EM>Alpine</EM> what file should be used as the password file.
3610 This should be a fully-qualified filename.
3613 <DT> -pinerc <EM>file</EM>
3615 <DD> Output fresh pinerc configuration to <EM>file</EM>, preserving the
3616 settings of variables that the user has made.
3617 Use <EM>file</EM> set to ``-'' to make output go to standard out.
3622 <DD> Restricted Mode: For UNIX <EM>Alpine</EM> only.
3623 <EM>Alpine</EM> in restricted mode can only send email to itself.
3624 Save and export are limited.
3627 <DT> -registry <EM>cmd</EM>
3629 <DD> For <EM>PC-Alpine</EM> only, this option affects the values of
3630 <EM>Alpine</EM>'s registry entries.
3631 Possible values for <EM>cmd</EM> are set, clear, and dump.
3632 <EM>Set</EM> will always reset <EM>Alpine</EM>'s registry
3633 entries according to its current settings.
3634 <EM>Clear</EM> will clear the registry values.
3635 <EM>Clearsilent</EM> will clear the registry values without any dialogs.
3636 <EM>Dump</EM> will display the values of current registry settings.
3637 Note that the dump command is currently disabled.
3638 Without the -registry option, <EM>PC-Alpine</EM> will write values into
3639 the registry only if there currently aren't any values set.
3642 <DT> -sort <EM>key</EM>
3644 <DD> Sort-Key: Specifies the order messages will be displayed in for the
3645 FOLDER INDEX screen.
3646 <EM>Key</EM> can have the following values:
3647 arrival, date, subject, orderedsubj, thread, from, size, score, to, cc,
3648 arrival/reverse, date/reverse, subject/reverse, orderedsubj/reverse, thread/reverse,
3649 from/reverse, size/reverse, score/reverse, to/reverse, and cc/reverse.
3650 The default value is "arrival".
3651 The <EM>key</EM> value reverse is equivalent to arrival/reverse.
3654 Configuration equivalent: <EM><!--#echo var="VAR_sort-key"--></EM>.
3659 <DD> For <EM>PC-Alpine</EM> only, this option removes references to Alpine
3660 in Windows settings. The registry settings are removed and
3661 the password cache is cleared.
3664 <DT> -url <EM>url</EM>
3666 <DD> Open the given URL.
3671 <DD> Version: Print version information to the screen.
3674 <DT> -x <EM>exceptions_config</EM>
3676 <DD> Configuration settings in the exceptions configuration override your normal
3678 <EM>Exceptions_config</EM> may be either a local file or a remote Alpine configuration folder.
3683 <DD> Enable Suspend: When run with this flag, the key sequence ctrl-z
3684 will suspend the <EM>Alpine</EM> session.
3687 Configuration equivalent: <EM><!--#echo var="FEAT_enable-suspend"--></EM> included in
3688 <EM>Feature-List</EM>.
3691 <DT> -<EM>option</EM>=<EM>value</EM>
3693 <DD> Assign <EM>value</EM> to the config option <EM>option</EM>.
3694 For example, <EM>-signature-file=sig1</EM> or
3695 <EM>-Feature-List=signature-at-bottom</EM>.
3696 Note: Feature-List values are
3697 additive and features may be preceded with no- to turn them off.
3698 Also, as a special case, the "Feature-List=" part of that may be
3699 omitted. For example, <EM>-signature-at-bottom</EM> is equivalent to
3700 <EM>-Feature-List=signature-at-bottom</EM>.
3705 <End of help on this topic>
3708 ===== h_configuring_news ======
3711 <TITLE>CONFIGURING NEWS</TITLE>
3714 <H1>CONFIGURING NEWS</H1>
3715 Alpine can access news folders in any one of three different ways:
3717 <DT>REMOTE NNTP</DT>
3718 <DD>Using the Network News Transport Protocol (NNTP) to
3719 access news on a remote news server. In this case the newsrc file is
3720 stored on the machine where Alpine is running.
3723 To specify a remote news-collection accessed via NNTP use the
3724 SETUP/collectionList screen's "Add" command. Set the
3725 Server: value to the NNTP server's hostname appended with the
3726 communication method "/service=NNTP", and set the Path:
3727 value to the "#news." namespace (without the quotes). See
3728 the "<A HREF="h_composer_cntxt_server">Server:</A>" field's
3729 help text for a more complete explanation of access method, and the
3730 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3731 text for a more complete explanation of "namespace".
3733 Instead of specifying a news-collection, you may simply set the
3734 <A HREF="h_config_nntp_server">NNTP Server</A>
3735 option, which will cause Alpine to create a default news-collection for you.
3736 Another NNTP option that may be of interest is
3737 <A HREF="h_config_nntprange"><!--#echo var="VAR_nntp-range"--></A>.
3739 <DT>REMOTE IMAP</DT>
3740 <DD>Using the Internet Message Access Protocol (IMAP) to
3741 access news on a remote news server. In this case, your newsrc file is
3742 stored on the news server, in your home directory, so you must have an
3743 account on the news server, but you would be running Alpine on a different
3744 machine. The news server must be running an IMAPd server process.
3747 To specify a remote news-collection accessed via IMAP use the
3748 SETUP/collectionList screen's "Add" command. Set the
3749 Server: value to the IMAP server's hostname, and set the Path: value
3750 to the "#news." namespace (without the quotes). See the
3751 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3752 text for a more complete explanation of "namespace".
3757 <DD>Using local file access to the news database. In this
3758 case, your newsrc file is stored on the news server, in your home
3759 directory, so you must have an account on the news server, and you would
3760 be running Alpine on the same machine.
3763 To specify a local news-collection use the SETUP/collectionList
3764 screen's "Add" command. Leave the Server: value blank, and
3765 set the Path: value to the "#news." namespace (without the
3766 quotes). See the "<A HREF="h_composer_cntxt_path">Path:</A>"
3767 field's help text for a more complete explanation of "namespace".
3774 NOTE: Should no news-collection be defined as above, Alpine will
3775 automatically create one using the Setup/Config screen's
3776 "<!--#echo var="VAR_nntp-server"-->" variable's value if defined. The collection
3777 will be created as a "Remote NNTP" as described above.
3781 If you are a PC-Alpine user, either option 1 (NNTP) or option 2 (IMAP) is
3782 possible. If you don't have an account on the news server, or if the news
3783 server is not running an IMAP daemon, then you must use NNTP. (If you are not
3784 sure, ask your service provider, university, or company for help.) In
3785 this case, your Unix .newsrc file can be transferred to your PC. A good
3786 place to put it would be in the same directory as your PINERC file, under
3787 the name NEWSRC, but you can
3788 <A HREF="h_config_newsrc_path">specify a different location</A>
3789 via Alpine's Setup/Config screen.
3792 Other configuration features related to news are
3793 <A HREF="h_config_8bit_nntp"><!--#echo var="FEAT_enable-8bit-nntp-posting"--></A>.
3794 <A HREF="h_config_compose_news_wo_conf"><!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></A>,
3795 <A HREF="h_config_news_uses_recent"><!--#echo var="FEAT_news-approximates-new-status"--></A>,
3796 <A HREF="h_config_news_cross_deletes"><!--#echo var="FEAT_news-deletes-across-groups"--></A>,
3797 <A HREF="h_config_news_catchup"><!--#echo var="FEAT_news-offers-catchup-on-close"--></A>,
3798 <A HREF="h_config_post_wo_validation"><!--#echo var="FEAT_news-post-without-validation"--></A>,
3799 <A HREF="h_config_read_in_newsrc_order"><!--#echo var="FEAT_news-read-in-newsrc-order"--></A>, and
3800 <A HREF="h_config_quell_post_prompt"><!--#echo var="FEAT_quell-extra-post-prompt"--></A>.
3803 <End of help on this topic>
3806 ===== h_reading_news ======
3809 <TITLE>READING NEWS</TITLE>
3812 <H1>READING NEWS</H1>
3814 Alpine uses almost the same commands for manipulating news folders as for
3815 mail folders. This means, for example, that when you are done with a
3816 message, you would use "D" to mark it as Deleted (or Dismissed,
3817 if you prefer.) This "mail-like" behavior differs from that of
3818 most newsreaders, wherein a message is implicitly dismissed after you have
3819 looked at it once. We strongly believe that Alpine should offer as much
3820 consistency as possible between mail and news, so the mail paradigm --
3821 wherein a message does not magically disappear without explicit action by
3822 the user -- is used for news as well. <P>
3824 If you answer a message in a news folder, the index view will show the
3825 "A" flag as usual; but the industry standard file Alpine uses to
3826 keep track of what news as been read has no way of storing this flag, so
3827 it will not be preserved across sessions. The Deleted flag is the only
3828 one that is preserved when you leave and then return to a newsgroup. As an
3829 additional note on replies, when you Reply to a newsgroup message and say
3830 you want to reply to all recipients, Alpine will ask if you want to post the
3831 message to all the newsgroups listed in the original message. <P>
3833 If you would like Alpine to mark more-or-less recent news messages as
3834 "New", then set the
3835 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
3836 feature (which is set by default). This will cause messages after the last one you have marked as
3837 Deleted to appear with "N" status in the MESSAGE INDEX. The
3838 "N" status often makes it easier to distinguish later news
3839 articles from those you've previously seen, but not yet disposed of via
3840 the "D" key. Note that this is an approximation, not an exact
3841 record of which messages you have not seen.
3844 A frequent operation in news-reading is "catching up" -- that
3845 is, getting rid of all the messages in the newsgroup so that you can
3846 "start fresh." The easiest way to do this in Alpine is via the
3847 Select command. You would enter the following four keystrokes:
3848 <tt>;aad</tt> to select all messaged, and then apply the delete (or
3849 dismiss) command to all of them.
3852 There are also additional details on
3853 <A HREF="h_configuring_news">configuring news</a>.
3856 <End of help on this topic>
3859 ====== h_help_index ======
3862 <TITLE>Help Index</TITLE>
3867 <li><a href="h_mainhelp_abooks">Address Books</a></li>
3868 <li><a href="h_abook_top">ADDRESS BOOK LIST COMMANDS</a>
3869 <li><a href="h_main_addrbook">Address Book Command</a>
3870 <li><a href="h_abook_view">Address Book View Explained</a>
3871 <li><a href="h_compose_addrcomplete">Address Completion</a>
3872 <li><a href="h_abook_select_listmode">Address Listmode Selection from Composer Explained</a>
3873 <li><a href="h_abook_select_checks">Address Selection from Composer Explained</a>
3874 <li><a href="h_composer_abook_comment">Addressbook Comment Explained</a>
3875 <li><a href="h_composer_abook_fcc">Addressbook Fcc Explained</a>
3876 <li><a href="h_composer_abook_add_folder">Addressbook Folder Name Field Explained</a>
3877 <li><a href="h_composer_abook_full">Addressbook Fullname Explained</a>
3878 <li><a href="h_composer_abook_add_nick">Addressbook NickName Field Explained</a>
3879 <li><a href="h_composer_abook_nick">Addressbook Nickname Explained</a>
3880 <li><a href="h_abook_select_addr">Addressbook Selection Explained</a>
3881 <li><a href="h_abook_select_top">Addressbook Selection Navigation Explained</a>
3882 <li><a href="h_composer_abook_add_server">Addressbook Server Name Field Explained</a>
3883 <li><a href="h_mainhelp_aggops">Aggregate Operations</a>
3884 <li><a href="h_mainhelp_config">Alpine Configuration</a>
3885 <li><a href="h_mainhelp_pinehelp">Alpine Help</a>
3886 <li><a href="h_news_legal">Alpine Legal Notices</a>
3887 <li><a href="h_compose_alted">Alt Editor Command</a>
3888 <li><a href="h_index_cmd_apply">Apply Command</a>
3889 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a>
3890 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a>
3891 <li><a href="h_mainhelp_filtering">Blocking Messages</a>
3892 <li><a href="h_composer_browse">BROWSER</a>
3893 <li><a href="h_common_bounce">Bounce Command</a>
3894 <li><a href="h_compose_cancel">Cancel Command</a>
3895 <li><a href="h_config_change_your_from">Changing your From Address</a>
3896 <li><a href="h_collection_screen">COLLECTION LIST screen</a>
3897 <li><a href="h_mainhelp_color">Color</a>
3898 <li><a href="h_composer_ctrl_j">COMPOSER ATTACH</a>
3899 <li><a href="h_composer">COMPOSER COMMANDS</a>
3900 <li><a href="h_mainhelp_composing">Composing Messages</a>
3901 <li><a href="h_mainhelp_collections">Collection Lists</a>
3902 <li><a href="h_composer_cntxt_nick">Collection Nickname Explained</a>
3903 <li><a href="h_composer_cntxt_path">Collection Path: Explained</a>
3904 <li><a href="h_composer_cntxt_server">Collection Server: Explained</a>
3905 <li><a href="h_composer_cntxt_view">Collection View: Explained</a>
3906 <li><a href="h_mainhelp_cmdlineopts">Command Line Options</a>
3907 <li><a href="h_common_compose">Compose Command</a>
3908 <li><a href="h_edit_nav_cmds">Composer Editing Commands Explained</a>
3909 <li><a href="h_common_conditional_cmds">Conditional Commands</a>
3910 <li><a href="h_reply_token_conditionals">Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</a>
3911 <li><a href="h_mainhelp_config">Configuration</a>
3912 <li><a href="h_composer_custom_free">CUSTOMIZED HEADER FIELD</a>
3913 <li><a href="h_config_dflt_color">Default Color</a>
3914 <li><a href="h_common_delete">Delete and Undelete Commands</a>
3915 <li><a href="h_composer_qserv_cn">Directory Query Form Explained</a>
3916 <li><a href="h_special_list_commands">Email List Commands Explained</a>
3917 <li><a href="h_composer_search">Explanation of Composer Whereis Command </a>
3918 <li><a href="h_folder_open">Explanation of Folder Selection</a>
3919 <li><a href="h_special_xon_xoff">Explanation of Alpine's XOFF/XON Handling</a>
3920 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a>
3921 <li><a href="h_ge_export">Export File Selection</a>
3922 <li><a href="h_ge_allparts">Export Message File Selection</a>
3923 <li><a href="h_index_cmd_expunge">Expunge/Exclude Command</a>
3924 <li><a href="h_info_on_locking">FAQs on Alpine Locking</a>
3925 <li><a href="h_config_allow_chg_from">FEATURE: <!--#echo var="FEAT_allow-changing-from"--></a>
3926 <li><a href="h_config_allow_talk">FEATURE: <!--#echo var="FEAT_allow-talk"--></a>
3927 <li><a href="h_config_alt_compose_menu">FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></a>
3928 <li><a href="h_config_alt_role_menu">FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></a>
3929 <li><a href="h_config_alt_reply_menu">FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></a>
3930 <li><a href="h_config_force_low_speed">FEATURE: <!--#echo var="FEAT_assume-slow-link"--></a>
3931 <li><a href="h_config_auto_read_msgs">FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></a>
3932 <li><a href="h_config_auto_open_unread">FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></a>
3933 <li><a href="h_config_auto_unselect">FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></a>
3934 <li><a href="h_config_auto_unzoom">FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></a>
3935 <li><a href="h_config_auto_zoom">FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></a>
3936 <li><a href="h_config_use_boring_spinner">FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></a>
3937 <li><a href="h_config_check_mail_onquit">FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></a>
3938 <li><a href="h_config_combined_abook_display">FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></a>
3939 <li><a href="h_config_combined_folder_display">FEATURE: <!--#echo var="FEAT_combined-folder-display"--></a>
3940 <li><a href="h_config_combined_subdir_display">FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></a>
3941 <li><a href="h_config_cancel_confirm">FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></a>
3942 <li><a href="h_config_lame_list_mode">FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></a>
3943 <li><a href="h_config_compose_rejects_unqual">FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></a>
3944 <li><a href="h_config_send_filter_dflt">FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></a>
3945 <li><a href="h_config_compose_news_wo_conf">FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></a>
3946 <li><a href="h_config_del_from_dot">FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></a>
3947 <li><a href="h_config_compose_maps_del">FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></a>
3948 <li><a href="h_config_confirm_role">FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></a>
3949 <li><a href="h_config_tab_no_prompt">FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></a>
3950 <li><a href="h_config_dates_to_local">FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></a>
3951 <li><a href="h_config_copy_to_to_from">FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></a>
3952 <li><a href="h_config_del_skips_del">FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></a>
3953 <li><a href="h_config_disable_config_cmd">FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></a>
3954 <li><a href="h_config_disable_index_locale_dates">FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></a>
3955 <li><a href="h_config_disable_kb_lock">FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></a>
3956 <li><a href="h_config_blank_keymenu">FEATURE: <!--#echo var="FEAT_disable-keymenu"--></a>
3957 <li><a href="h_config_disable_password_caching">FEATURE: <!--#echo var="FEAT_disable-password-caching"--></a>
3958 <li><a href="h_config_disable_password_cmd">FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></a>
3959 <li><a href="h_config_disable_pipes_in_sigs">FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></a>
3960 <li><a href="h_config_disable_pipes_in_templates">FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></a>
3961 <li><a href="h_config_disable_regex">FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
3962 <li><a href="h_config_disable_roles_setup">FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></a>
3963 <li><a href="h_config_disable_roles_sigedit">FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></a>
3964 <li><a href="h_config_disable_roles_templateedit">FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></a>
3965 <li><a href="h_config_input_history">FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></a>
3966 <li><a href="h_config_disable_collate">FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></a>
3967 <li><a href="h_config_disable_shared">FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></a>
3968 <li><a href="h_config_disable_signature_edit">FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></a>
3969 <li><a href="h_config_take_fullname">FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></a>
3970 <li><a href="h_config_take_lastfirst">FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></a>
3971 <li><a href="h_config_disable_reset_disp">FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></a>
3972 <li><a href="h_config_disable_sender">FEATURE: <!--#echo var="FEAT_disable-sender"--></a>
3973 <li><a href="h_config_quell_dead_letter">FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></a>
3974 <li><a href="h_config_quell_flowed_text">FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></a>
3975 <li><a href="h_downgrade_multipart_to_text">FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></a>
3976 <li><a href="h_config_8bit_smtp">FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></a>
3977 <li><a href="h_config_8bit_nntp">FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></a>
3978 <li><a href="h_config_enable_agg_ops">FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></a>
3979 <li><a href="h_config_enable_alt_ed">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></a>
3980 <li><a href="h_config_alt_ed_now">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></a>
3981 <li><a href="h_config_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></a>
3982 <li><a href="h_config_relaxed_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></a>
3983 <li><a href="h_config_compose_bg_post">FEATURE: <!--#echo var="FEAT_enable-background-sending"--></a>
3984 <li><a href="h_config_enable_bounce">FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></a>
3985 <li><a href="h_config_cruise_mode">FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></a>
3986 <li><a href="h_config_cruise_mode_delete">FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></a>
3987 <li><a href="h_config_compose_dsn">FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></a>
3988 <li><a href="h_config_enable_dot_files">FEATURE: <!--#echo var="FEAT_enable-dot-files"--></a>
3989 <li><a href="h_config_enable_lessthan_exit">FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></a>
3990 <li><a href="h_config_fast_recent">FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></a>
3991 <li><a href="h_config_enable_flag">FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></a>
3992 <li><a href="h_config_flag_screen_default">FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></a>
3993 <li><a href="h_config_flag_screen_kw_shortcut">FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></a>
3994 <li><a href="h_config_enable_full_hdr_and_text">FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></a>
3995 <li><a href="h_config_enable_full_hdr">FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></a>
3996 <li><a href="h_config_allow_goto">FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></a>
3997 <li><a href="h_config_enable_dot_folders">FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></a>
3998 <li><a href="h_config_enable_incoming">FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></a>
3999 <li><a href="h_config_enable_incoming_checking">FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></a>
4000 <li><a href="h_config_enable_jump">FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></a>
4001 <li><a href="h_config_show_delay_cue">FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></a>
4002 <li><a href="h_config_mailcap_params">FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></a>
4003 <li><a href="h_config_enable_mouse">FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></a>
4004 <li><a href="h_config_enable_view_addresses">FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></a>
4005 <li><a href="h_config_enable_view_attach">FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></a>
4006 <li><a href="h_config_enable_view_arrows">FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></a>
4007 <li><a href="h_config_enable_view_url">FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></a>
4008 <li><a href="h_config_enable_view_web_host">FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></a>
4009 <li><a href="h_config_enable_mulnewsrcs">FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></a>
4010 <li><a href="h_config_enable_xterm_newmail">FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></a>
4011 <li><a href="h_config_enable_newmail_short_text">FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>
4012 <li><a href="h_config_sub_lists">FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></a>
4013 <li><a href="h_config_enable_y_print">FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></a>
4014 <li><a href="h_config_prefix_editing">FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></a>
4015 <li><a href="h_config_enable_search_and_repl">FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></a>
4016 <li><a href="h_config_sigdashes">FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></a>
4017 <li><a href="h_config_new_thread_blank_subject">FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></a>
4018 <li><a href="h_config_can_suspend">FEATURE: <!--#echo var="FEAT_enable-suspend"--></a>
4019 <li><a href="h_config_enable_tab_complete">FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></a>
4020 <li><a href="h_config_enable_take_export">FEATURE: <!--#echo var="FEAT_enable-take-export"--></a>
4021 <li><a href="h_config_enable_role_take">FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></a>
4022 <li><a href="h_config_tray_icon">FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></a>
4023 <li><a href="h_config_enable_pipe">FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></a>
4024 <li><a href="h_config_verbose_post">FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></a>
4025 <li><a href="h_config_expanded_addrbooks">FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></a>
4026 <li><a href="h_config_expanded_distlists">FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></a>
4027 <li><a href="h_config_expanded_folders">FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></a>
4028 <li><a href="h_config_expose_hidden_config">FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></a>
4029 <li><a href="h_config_expunge_manually">FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></a>
4030 <li><a href="h_config_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></a>
4031 <li><a href="h_config_full_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></a>
4032 <li><a href="h_config_no_fcc_attach">FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></a>
4033 <li><a href="h_config_force_arrow">FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></a>
4034 <li><a href="h_config_ignore_size">FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></a>
4035 <li><a href="h_config_forward_as_attachment">FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></a>
4036 <li><a href="h_config_preserve_field">FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></a>
4037 <li><a href="h_config_quell_empty_dirs">FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></a>
4038 <li><a href="h_config_hide_nntp_path">FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></a>
4039 <li><a href="h_config_attach_in_reply">FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></a>
4040 <li><a href="h_config_fcc_on_bounce">FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></a>
4041 <li><a href="h_config_include_header">FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></a>
4042 <li><a href="h_config_auto_include_reply">FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></a>
4043 <li><a href="h_config_incoming_checking_total">FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></a>
4044 <li><a href="h_config_incoming_checking_recent">FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></a>
4045 <li><a href="h_config_add_ldap">FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></a>
4046 <li><a href="h_config_maildrops_preserve_state">FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></a>
4047 <li><a href="h_config_mark_fcc_seen">FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></a>
4048 <li><a href="h_config_mark_for_cc">FEATURE: <!--#echo var="FEAT_mark-for-cc"--></a>
4049 <li><a href="h_config_mulnews_as_typed">FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></a>
4050 <li><a href="h_config_news_uses_recent">FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></a>
4051 <li><a href="h_config_news_cross_deletes">FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></a>
4052 <li><a href="h_config_news_catchup">FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></a>
4053 <li><a href="h_config_post_wo_validation">FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></a>
4054 <li><a href="h_config_read_in_newsrc_order">FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></a>
4055 <li><a href="h_config_nntp_search_uses_overview">FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></a>
4056 <li><a href="h_config_thread_sorts_by_arrival">FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></a>
4057 <li><a href="h_config_expunge_inbox">FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></a>
4058 <li><a href="h_config_expunge_stayopens">FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></a>
4059 <li><a href="h_config_pass_c1_control">FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></a>
4060 <li><a href="h_config_pass_control">FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></a>
4061 <li><a href="h_config_predict_nntp_server">FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></a>
4062 <li><a href="h_config_prefer_plain_text">FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></a>
4063 <li><a href="h_config_preopen_stayopens">FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></a>
4064 <li><a href="h_config_preserve_start_stop">FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></a>
4065 <li><a href="h_config_quell_folder_internal_msg">FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></a>
4066 <li><a href="h_config_quell_checks_comp">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></a>
4067 <li><a href="h_config_quell_checks_comp_inbox">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></a>
4068 <li><a href="h_config_quell_partial">FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></a>
4069 <li><a href="h_config_quell_local_lookup">FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></a>
4070 <li><a href="h_config_ff_between_msgs">FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></a>
4071 <li><a href="h_config_print_from">FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></a>
4072 <li><a href="h_config_print_index">FEATURE: <!--#echo var="FEAT_print-index-enabled"--></a>
4073 <li><a href="h_config_custom_print">FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></a>
4074 <li><a href="h_config_prune_uses_iso">FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></a>
4075 <li><a href="h_config_quell_personal_name_prompt">FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></a>
4076 <li><a href="h_config_quell_ssl_largeblocks">FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></a>
4077 <li><a href="h_config_quell_user_id_prompt">FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></a>
4078 <li><a href="h_config_quit_wo_confirm">FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></a>
4079 <li><a href="h_config_quote_replace_noflow">FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></a>
4080 <li><a href="h_config_next_thrd_wo_confirm">FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></a>
4081 <li><a href="h_config_auto_reply_to">FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></a>
4082 <li><a href="h_config_inbox_no_confirm">FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></a>
4083 <li><a href="h_config_save_aggregates">FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></a>
4084 <li><a href="h_config_save_part_wo_confirm">FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></a>
4085 <li><a href="h_config_save_advances">FEATURE: <!--#echo var="FEAT_save-will-advance"--></a>
4086 <li><a href="h_config_save_wont_delete">FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></a>
4087 <li><a href="h_config_quote_all_froms">FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></a>
4088 <li><a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
4089 <li><a href="h_config_select_wo_confirm">FEATURE: <!--#echo var="FEAT_select-without-confirm"--></a>
4090 <li><a href="h_config_auto_fcc_only">FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></a>
4091 <li><a href="h_config_send_wo_confirm">FEATURE: <!--#echo var="FEAT_send-without-confirm"--></a>
4092 <li><a href="h_config_separate_fold_dir_view">FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></a>
4093 <li><a href="h_config_show_cursor">FEATURE: <!--#echo var="FEAT_show-cursor"--></a>
4094 <li><a href="h_config_textplain_int">FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></a>
4095 <li><a href="h_config_select_in_bold">FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></a>
4096 <li><a href="h_config_show_sort">FEATURE: <!--#echo var="FEAT_show-sort"--></a>
4097 <li><a href="h_config_single_list">FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></a>
4098 <li><a href="h_config_sig_at_bottom">FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></a>
4099 <li><a href="h_config_slash_coll_entire">FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></a>
4100 <li><a href="h_config_sort_fcc_alpha">FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></a>
4101 <li><a href="h_config_sort_save_alpha">FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></a>
4102 <li><a href="h_config_always_spell_check">FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></a>
4103 <li><a href="h_config_winpos_in_config">FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></a>
4104 <li><a href="h_config_strip_sigdashes">FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>
4105 <li><a href="h_config_strip_ws_before_send">FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></a>
4106 <li><a href="h_config_quells_asterisks">FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></a>
4107 <li><a href="h_config_quell_attach_ext_warn">FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></a>
4108 <li><a href="h_config_quell_attach_extra_prompt">FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></a>
4109 <li><a href="h_config_no_bezerk_zone">FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></a>
4110 <li><a href="h_config_quell_charset_warning">FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></a>
4111 <li><a href="h_config_quell_content_id">FEATURE: <!--#echo var="FEAT_quell-content-id"--></a>
4112 <li><a href="h_config_quell_post_prompt">FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></a>
4113 <li><a href="h_config_quell_filtering_done_message">FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></a>
4114 <li><a href="h_config_quell_filtering_messages">FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></a>
4115 <li><a href="h_config_quell_full_hdr_reset">FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></a>
4116 <li><a href="h_config_quell_imap_env">FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></a>
4117 <li><a href="h_config_quell_lock_failure_warnings">FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></a>
4118 <li><a href="h_config_quell_domain_warn">FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></a>
4119 <li><a href="h_config_quell_news_env">FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></a>
4120 <li><a href="h_config_quell_host_after_url">FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></a>
4121 <li><a href="h_config_quell_beeps">FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></a>
4122 <li><a href="h_config_quell_tz_comment">FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></a>
4123 <li><a href="h_config_suppress_user_agent">FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></a>
4124 <li><a href="h_config_tab_checks_recent">FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></a>
4125 <li><a href="h_config_tab_uses_unseen">FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></a>
4126 <li><a href="h_config_tab_new_only">FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></a>
4127 <li><a href="h_config_termcap_wins">FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></a>
4128 <li><a href="h_config_color_thrd_import">FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></a>
4129 <li><a href="h_config_alt_auth">FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></a>
4130 <li><a href="h_config_unsel_wont_advance">FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></a>
4131 <li><a href="h_config_use_current_dir">FEATURE: <!--#echo var="FEAT_use-current-dir"--></a>
4132 <li><a href="h_config_use_fk">FEATURE: <!--#echo var="FEAT_use-function-keys"--></a>
4133 <li><a href="h_config_use_reg_start_for_stayopen">FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></a>
4134 <li><a href="h_config_use_resentto">FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></a>
4135 <li><a href="h_config_use_sender_not_x">FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></a>
4136 <li><a href="h_config_suspend_spawns">FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></a>
4137 <li><a href="h_config_use_system_translation">FEATURE: Use System Translation</a>
4138 <li><a href="h_config_vertical_list">FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></a>
4139 <li><a href="h_config_warn_if_fcc_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></a>
4140 <li><a href="h_config_warn_if_subj_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></a>
4141 <li><a href="h_config_warn_if_no_to_or_cc">FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></a>
4142 <li><a href="h_mainhelp_filtering">Filtering</a>
4143 <li><a href="h_finding_help">Finding more information and requesting help</a>
4144 <li><a href="h_common_flag">Flag Command</a>
4145 <li><a href="h_config_quell_flowed_text">Flowed Text</a>
4146 <li><a href="h_mainhelp_folders">Folders</a>
4147 <li><a href="h_what_are_collections">Folder Collections Explained</a>
4148 <li><a href="h_common_folders">Folder List Command</a>
4149 <li><a href="h_folder_fcc">Folder Select for Fcc Explained</a>
4150 <li><a href="h_folder_save">Folder Select for Save Explained</a>
4151 <li><a href="h_folder_server_syntax">Folder Server Name Syntax</a>
4152 <li><a href="h_config_change_your_from">From Address, Changing</a>
4153 <li><a href="main_menu_tx">GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</a>
4154 <li><a href="h_pine_for_windows">GETTING HELP IN ALPINE</a>
4155 <li><a href="h_common_goto">Goto Command</a>
4156 <li><a href="h_common_hdrmode">HdrMode Command</a>
4157 <li><a href="h_mainhelp_pinehelp">Help</a>
4158 <li><a href="h_special_help_nav">Help Text Navigation Explained</a>
4159 <li><a href="h_folder_maint">Help for Folder List</a>
4160 <li><a href="h_valid_folder_names">IMAP</a>
4161 <li><a href="h_ge_import">Import File Selection</a>
4162 <li><a href="h_mainhelp_index">Index of Messages</a>
4163 <li><a href="h_composer_ins_m">INSERT MESSAGE</a>
4164 <li><a href="h_composer_ins">INSERT TEXT FILE</a>
4165 <li><a href="h_address_format">INTERNET EMAIL ADDRESS FORMAT</a>
4166 <li><a href="h_info_on_mbox">Information on mbox driver</a>
4167 <li><a href="h_mainhelp_intro">Introduction</a>
4168 <li><a href="h_main_journal">Journal Command</a>
4169 <li><a href="h_common_jump">Jump Command</a>
4170 <li><a href="h_compose_justify">Justify Command</a>
4171 <li><a href="h_main_kblock">Keyboard Lock Command</a>
4172 <li><a href="h_mainhelp_keywords">Keywords (or Flags, or Labels)</a>
4173 <li><a href="h_mainhelp_ldap">LDAP</a>
4174 <li><a href="h_config_ldap_opts_tls">LDAP FEATURE: Attempt-TLS-On-Connection</a>
4175 <li><a href="h_config_ldap_opts_nosub">LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</a>
4176 <li><a href="h_config_ldap_opts_rhs">LDAP FEATURE: Lookup-Addrbook-Contents</a>
4177 <li><a href="h_config_ldap_opts_tlsmust">LDAP FEATURE: Require-TLS-On-Connection</a>
4178 <li><a href="h_config_ldap_opts_ldaps">LDAP FEATURE: Require-LDAPS-On-Connection</a>
4179 <li><a href="h_config_ldap_opts_ref">LDAP FEATURE: Save-Search-Criteria-Not-Result</a>
4180 <li><a href="h_config_ldap_opts_impl">LDAP FEATURE: Use-Implicitly-From-Composer</a>
4181 <li><a href="h_config_ldap_binddn">LDAP OPTION: Bind-DN</a>
4182 <li><a href="h_config_ldap_cust">LDAP OPTION: Custom-Search-Filter</a>
4183 <li><a href="h_config_ldap_email_attr">LDAP OPTION: EmailAttribute</a>
4184 <li><a href="h_config_ldap_gn_attr">LDAP OPTION: GivennameAttribute</a>
4185 <li><a href="h_config_ldap_server">LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></a>
4186 <li><a href="h_config_ldap_cn_attr">LDAP OPTION: NameAttribute</a>
4187 <li><a href="h_config_ldap_nick">LDAP OPTION: Nickname</a>
4188 <li><a href="h_config_ldap_port">LDAP OPTION: Port</a>
4189 <li><a href="h_config_ldap_base">LDAP OPTION: Search-Base</a>
4190 <li><a href="h_config_ldap_searchrules">LDAP OPTION: Search-Rule</a>
4191 <li><a href="h_config_ldap_searchtypes">LDAP OPTION: Search-Type</a>
4192 <li><a href="h_config_ldap_size">LDAP OPTION: Sizelimit</a>
4193 <li><a href="h_config_ldap_sn_attr">LDAP OPTION: SurnameAttribute</a>
4194 <li><a href="h_config_ldap_time">LDAP OPTION: Timelimit</a>
4195 <li><a href="h_ldap_view">LDAP Response View Explained</a>
4196 <li><a href="h_maildrop">Mail Drop: What is it?</a>
4197 <li><a href="h_mainhelp_mainmenu">MAIN MENU</a>
4198 <li><a href="h_mail_index">MESSAGE INDEX COMMANDS</a>
4199 <li><a href="h_mail_view">MESSAGE TEXT SCREEN</a>
4200 <li><a href="h_compose_markcutpaste">Mark, Cut and Paste Commands</a>
4201 <li><a href="h_common_index">Message Index Command</a>
4202 <li><a href="h_mainhelp_mouse">Mouse</a>
4203 <li><a href="h_mainhelp_aggops">Multiple Message Operations</a>
4204 <li><a href="new_user_greeting">NEW USER GREETING</a>
4205 <li><a href="new_version_greeting">NEW VERSION GREETING</a>
4206 <li><a href="h_mainhelp_readingnews">News Reading</a>
4207 <li><a href="h_folder_subscribe">Newsgroup Subcribe Screen explained</a>
4208 <li><a href="h_folder_postnews">Newsgroup selecting for Posting explained</a>
4209 <li><a href="h_common_nextnew">NextNew Command</a>
4210 <li><a href="h_abook_select_nick">Nickname Selection Explained</a>
4211 <li><a href="h_mainhelp_readingnews">NNTP</a>
4212 <li><a href="h_config_address_book">OPTION: <!--#echo var="VAR_address-book"--></a>
4213 <li><a href="h_config_abook_formats">OPTION: <!--#echo var="VAR_addressbook-formats"--></a>
4214 <li><a href="h_config_ab_sort_rule">OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></a>
4215 <li><a href="h_config_alt_addresses">OPTION: <!--#echo var="VAR_alt-addresses"--></a>
4216 <li><a href="h_config_active_msg_interval">OPTION: <!--#echo var="VAR_busy-cue-rate"--></a>
4217 <li><a href="h_config_color_style">OPTION: Color Style</a>
4218 <li><a href="h_config_wordseps">OPTION: <!--#echo var="VAR_composer-word-separators"--></a>
4219 <li><a href="h_config_composer_wrap_column">OPTION: <!--#echo var="VAR_composer-wrap-column"--></a>
4220 <li><a href="h_config_index_color_style">OPTION: <!--#echo var="VAR_current-indexline-style"--></a>
4221 <li><a href="h_config_cursor_style">OPTION: Cursor Style</a>
4222 <li><a href="h_config_custom_hdrs">OPTION: <!--#echo var="VAR_customized-hdrs"--></a>
4223 <li><a href="h_config_deadlets">OPTION: <!--#echo var="VAR_dead-letter-files"--></a>
4224 <li><a href="h_config_comp_hdrs">OPTION: <!--#echo var="VAR_default-composer-hdrs"--></a>
4225 <li><a href="h_config_default_fcc">OPTION: <!--#echo var="VAR_default-fcc"--></a>
4226 <li><a href="h_config_def_save_folder">OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></a>
4227 <li><a href="h_config_disable_auths">OPTION: <!--#echo var="VAR_disable-these-authenticators"--></a>
4228 <li><a href="h_config_disable_drivers">OPTION: <!--#echo var="VAR_disable-these-drivers"--></a>
4229 <li><a href="h_config_char_set">OPTION: Display Character Set</a>
4230 <li><a href="h_config_display_filters">OPTION: <!--#echo var="VAR_display-filters"--></a>
4231 <li><a href="h_config_download_cmd">OPTION: <!--#echo var="VAR_download-command"--></a>
4232 <li><a href="h_config_download_prefix">OPTION: <!--#echo var="VAR_download-command-prefix"--></a>
4233 <li><a href="h_config_editor">OPTION: <!--#echo var="VAR_editor"--></a>
4234 <li><a href="h_config_empty_hdr_msg">OPTION: <!--#echo var="VAR_empty-header-message"--></a>
4235 <li><a href="h_config_fcc_rule">OPTION: <!--#echo var="VAR_fcc-name-rule"--></a>
4236 <li><a href="h_config_file_dir">OPTION: File Directory</a>
4237 <li><a href="h_config_folder_spec">OPTION: <!--#echo var="VAR_folder-collections"--></a>
4238 <li><a href="h_config_reopen_rule">OPTION: <!--#echo var="VAR_folder-reopen-rule"--></a>
4239 <li><a href="h_config_fld_sort_rule">OPTION: <!--#echo var="VAR_folder-sort-rule"--></a>
4240 <li><a href="h_config_font_char_set">OPTION: Font Character Set</a>
4241 <li><a href="h_config_font_name">OPTION: Font Name</a>
4242 <li><a href="h_config_font_size">OPTION: Font Size</a>
4243 <li><a href="h_config_font_style">OPTION: Font Style</a>
4244 <li><a href="h_config_form_folder">OPTION: <!--#echo var="VAR_form-letter-folder"--></a>
4245 <li><a href="h_config_glob_addrbook">OPTION: <!--#echo var="VAR_global-address-book"--></a>
4246 <li><a href="h_config_goto_default">OPTION: <!--#echo var="VAR_goto-default-rule"--></a>
4247 <li><a href="h_config_header_general_color">OPTION: Header General Color</a>
4248 <li><a href="h_config_image_viewer">OPTION: <!--#echo var="VAR_image-viewer"--></a>
4249 <li><a href="h_config_inbox_path">OPTION: <!--#echo var="VAR_inbox-path"--></a>
4250 <li><a href="h_config_archived_folders">OPTION: <!--#echo var="VAR_incoming-archive-folders"--></a>
4251 <li><a href="h_config_psleep">OPTION: <!--#echo var="VAR_mailcap-check-interval"--></a>
4252 <li><a href="h_config_incoming_interv">OPTION: <!--#echo var="VAR_incoming-check-interval"--></a>
4253 <li><a href="h_config_incoming_second_interv">OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></a>
4254 <li><a href="h_config_incoming_list">OPTION: <!--#echo var="VAR_incoming-check-list"--></a>
4255 <li><a href="h_config_incoming_timeo">OPTION: <!--#echo var="VAR_incoming-check-timeout"--></a>
4256 <li><a href="h_config_incoming_folders">OPTION: <!--#echo var="VAR_incoming-folders"--></a>
4257 <li><a href="h_config_inc_startup">OPTION: <!--#echo var="VAR_incoming-startup-rule"--></a>
4258 <li><a href="h_config_incunseen_color">OPTION: Incoming Unseen Color</a>
4259 <li><a href="h_config_index_arrow_color">OPTION: Index Arrow Color</a>
4260 <li><a href="h_config_index_color">OPTION: Index Colors</a>
4261 <li><a href="h_config_index_format">OPTION: <!--#echo var="VAR_index-format"--></a>
4262 <li><a href="h_config_index_from_color">OPTION: Index From Color</a>
4263 <li><a href="h_config_index_opening_color">OPTION: Index Opening Color</a>
4264 <li><a href="h_config_index_pri_color">OPTION: Index Priority Symbol Colors</a>
4265 <li><a href="h_config_index_subject_color">OPTION: Index Subject Color</a>
4266 <li><a href="h_config_init_cmd_list">OPTION: <!--#echo var="VAR_initial-keystroke-list"--></a>
4267 <li><a href="h_config_key_char_set">OPTION: Keyboard Character Set</a>
4268 <li><a href="h_config_keylabel_color">OPTION: KeyLabel Color</a>
4269 <li><a href="h_config_keyname_color">OPTION: KeyName Color</a>
4270 <li><a href="h_config_keywords">OPTION: <!--#echo var="VAR_keywords"--></a>
4271 <li><a href="h_config_kw_color">OPTION: Keyword Colors</a>
4272 <li><a href="h_config_kw_braces">OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></a>
4273 <li><a href="h_config_prune_date">OPTION: <!--#echo var="VAR_last-time-prune-questioned"--></a>
4274 <li><a href="h_config_last_vers">OPTION: <!--#echo var="VAR_last-version-used"--></a>
4275 <li><a href="h_config_literal_sig">OPTION: <!--#echo var="VAR_literal-signature"--></a>
4276 <li><a href="h_config_mailcheck">OPTION: <!--#echo var="VAR_mail-check-interval"--></a>
4277 <li><a href="h_config_mailchecknoncurr">OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></a>
4278 <li><a href="h_config_mailcap_path">OPTION: <!--#echo var="VAR_mailcap-search-path"--></a>
4279 <li><a href="h_config_maildropcheck">OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></a>
4280 <li><a href="h_config_maxremstream">OPTION: <!--#echo var="VAR_max-remote-connections"--></a>
4281 <li><a href="h_config_metamsg_color">OPTION: Meta-Message Color</a>
4282 <li><a href="h_config_mimetype_path">OPTION: <!--#echo var="VAR_mimetype-search-path"--></a>
4283 <li><a href="h_config_new_ver_quell">OPTION: <!--#echo var="VAR_new-version-threshold"--></a>
4284 <li><a href="h_config_fifopath">OPTION: NewMail FIFO Path</a>
4285 <li><a href="h_config_newmailwidth">OPTION: <!--#echo var="VAR_newmail-window-width"--></a>
4286 <li><a href="h_config_news_active">OPTION: <!--#echo var="VAR_news-active-file-path"--></a>
4287 <li><a href="h_config_news_spec">OPTION: <!--#echo var="VAR_news-collections"--></a>
4288 <li><a href="h_config_news_spool">OPTION: <!--#echo var="VAR_news-spool-directory"--></a>
4289 <li><a href="h_config_newsrc_path">OPTION: <!--#echo var="VAR_newsrc-path"--></a>
4290 <li><a href="h_config_nntprange">OPTION: <!--#echo var="VAR_nntp-range"--></a>
4291 <li><a href="h_config_nntp_server">OPTION: <!--#echo var="VAR_nntp-server"--></HEAD></a>
4292 <li><a href="h_config_normal_color">OPTION: Normal Color</a>
4293 <li><a href="h_config_opening_sep">OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></a>
4294 <li><a href="h_config_oper_dir">OPTION: <!--#echo var="VAR_operating-dir"--></a>
4295 <li><a href="h_config_pat_old">OPTION: Patterns</a>
4296 <li><a href="h_config_pat_filts">OPTION: <!--#echo var="VAR_patterns-filters2"--></a>
4297 <li><a href="h_config_pat_other">OPTION: <!--#echo var="VAR_patterns-other"--></a>
4298 <li><a href="h_config_pat_roles">OPTION: <!--#echo var="VAR_patterns-roles"--></a>
4299 <li><a href="h_config_pat_scores">OPTION: <!--#echo var="VAR_patterns-scores2"--></a>
4300 <li><a href="h_config_pers_name">OPTION: <!--#echo var="VAR_personal-name"--></a>
4301 <li><a href="h_config_print_cat">OPTION: <!--#echo var="VAR_personal-print-category"--></a>
4302 <li><a href="h_config_print_command">OPTION: <!--#echo var="VAR_personal-print-command"--></a>
4303 <li><a href="h_config_post_char_set">OPTION: <!--#echo var="VAR_posting-character-set"--></a>
4304 <li><a href="h_config_postponed_folder">OPTION: <!--#echo var="VAR_postponed-folder"--></a>
4305 <li><a href="h_config_print_font_char_set">OPTION: Print-Font-Char-Set</a>
4306 <li><a href="h_config_print_font_name">OPTION: Print-Font-Name</a>
4307 <li><a href="h_config_print_font_size">OPTION: Print-Font-Size</a>
4308 <li><a href="h_config_print_font_style">OPTION: Print-Font-Style</a>
4309 <li><a href="h_config_printer">OPTION: Printer</a>
4310 <li><a href="h_config_prompt_color">OPTION: Prompt Color</a>
4311 <li><a href="h_config_pruned_folders">OPTION: <!--#echo var="VAR_pruned-folders"--></a>
4312 <li><a href="h_config_pruning_rule">OPTION: <!--#echo var="VAR_pruning-rule"--></a>
4313 <li><a href="h_config_quote_color">OPTION: Quote Colors</a>
4314 <li><a href="h_config_quote_replace_string">OPTION: <!--#echo var="VAR_quote-replace-string"--></a>
4315 <li><a href="h_config_quote_suppression">OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></a>
4316 <li><a href="h_config_read_message_folder">OPTION: <!--#echo var="VAR_read-message-folder"--></a>
4317 <li><a href="h_config_remote_abook_history">OPTION: <!--#echo var="VAR_remote-abook-history"--></a>
4318 <li><a href="h_config_abook_metafile">OPTION: <!--#echo var="VAR_remote-abook-metafile"--></a>
4319 <li><a href="h_config_remote_abook_validity">OPTION: <!--#echo var="VAR_remote-abook-validity"--></a>
4320 <li><a href="h_config_reply_indent_string">OPTION: <!--#echo var="VAR_reply-indent-string"--></a>
4321 <li><a href="h_config_reply_intro">OPTION: <!--#echo var="VAR_reply-leadin"--></a>
4322 <li><a href="h_config_reverse_color">OPTION: Reverse Color</a>
4323 <li><a href="h_config_rshcmd">OPTION: <!--#echo var="VAR_rsh-command"--></a>
4324 <li><a href="h_config_rsh_open_timeo">OPTION: <!--#echo var="VAR_rsh-open-timeout"--></a>
4325 <li><a href="h_config_rshpath">OPTION: <!--#echo var="VAR_rsh-path"--></a>
4326 <li><a href="h_config_saved_msg_name_rule">OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></a>
4327 <li><a href="h_config_scroll_margin">OPTION: <!--#echo var="VAR_scroll-margin"--></a>
4328 <li><a href="h_config_slctbl_color">OPTION: Selectable Item Color</a>
4329 <li><a href="h_config_sending_filter">OPTION: <!--#echo var="VAR_sending-filters"--></a>
4330 <li><a href="h_config_sendmail_path">OPTION: <!--#echo var="VAR_sendmail-path"--></a>
4331 <li><a href="h_config_signature_color">OPTION: Signature Color</a>
4332 <li><a href="h_config_signature_file">OPTION: <!--#echo var="VAR_signature-file"--></a>
4333 <li><a href="h_config_smtp_server">OPTION: <!--#echo var="VAR_smtp-server"--></a>
4334 <li><a href="h_config_sort_key">OPTION: <!--#echo var="VAR_sort-key"--></a>
4335 <li><a href="h_config_speller">OPTION: <!--#echo var="VAR_speller"--></a>
4336 <li><a href="h_config_aspell_dictionary">OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></a>
4337 <li><a href="h_config_sshcmd">OPTION: <!--#echo var="VAR_ssh-command"--></a>
4338 <li><a href="h_config_ssh_open_timeo">OPTION: <!--#echo var="VAR_ssh-open-timeout"--></a>
4339 <li><a href="h_config_sshpath">OPTION: <!--#echo var="VAR_ssh-path"--></a>
4340 <li><a href="h_config_status_color">OPTION: Status Color</a>
4341 <li><a href="h_config_status_msg_delay">OPTION: <!--#echo var="VAR_status-message-delay"--></a>
4342 <li><a href="h_config_permlocked">OPTION: <!--#echo var="VAR_stay-open-folders"--></a>
4343 <li><a href="h_config_tcp_open_timeo">OPTION: <!--#echo var="VAR_tcp-open-timeout"--></a>
4344 <li><a href="h_config_tcp_query_timeo">OPTION: <!--#echo var="VAR_tcp-query-timeout"--></a>
4345 <li><a href="h_config_tcp_readwarn_timeo">OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></a>
4346 <li><a href="h_config_tcp_writewarn_timeo">OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></a>
4347 <li><a href="h_config_thread_disp_style">OPTION: <!--#echo var="VAR_threading-display-style"--></a>
4348 <li><a href="h_config_thread_exp_char">OPTION: <!--#echo var="VAR_threading-expanded-character"--></a>
4349 <li><a href="h_config_thread_index_style">OPTION: <!--#echo var="VAR_threading-index-style"--></a>
4350 <li><a href="h_config_thread_indicator_char">OPTION: <!--#echo var="VAR_threading-indicator-character"--></a>
4351 <li><a href="h_config_thread_lastreply_char">OPTION: <!--#echo var="VAR_threading-lastreply-character"--></a>
4352 <li><a href="h_config_title_color">OPTION: Title Color</a>
4353 <li><a href="h_config_titleclosed_color">OPTION: Title Closed Color</a>
4354 <li><a href="h_config_titlebar_color_style">OPTION: <!--#echo var="VAR_titlebar-color-style"--></a>
4355 <li><a href="h_config_unk_char_set">OPTION: <!--#echo var="VAR_unknown-character-set"--></a>
4356 <li><a href="h_config_upload_cmd">OPTION: <!--#echo var="VAR_upload-command"--></a>
4357 <li><a href="h_config_upload_prefix">OPTION: <!--#echo var="VAR_upload-command-prefix"--></a>
4358 <li><a href="h_config_browser">OPTION: <!--#echo var="VAR_url-viewers"--></a>
4359 <li><a href="h_config_history">OPTION: <!--#echo var="VAR_default-directories"--></a>
4360 <li><a href="h_config_domain_name">OPTION: <!--#echo var="VAR_use-only-domain-name"--></a>
4361 <li><a href="h_config_user_dom">OPTION: <!--#echo var="VAR_user-domain"--></a>
4362 <li><a href="h_config_user_id">OPTION: <!--#echo var="VAR_user-id"--></a>
4363 <li><a href="h_config_user_input_timeo">OPTION: <!--#echo var="VAR_user-input-timeout"--></a>
4364 <li><a href="h_config_viewer_headers">OPTION: <!--#echo var="VAR_viewer-hdrs"--></a>
4365 <li><a href="h_config_customhdr_pattern">OPTION: Viewer Header Color Pattern</a>
4366 <li><a href="h_config_customhdr_color">OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></a>
4367 <li><a href="h_config_viewer_margin_left">OPTION: <!--#echo var="VAR_viewer-margin-left"--></a>
4368 <li><a href="h_config_viewer_margin_right">OPTION: <!--#echo var="VAR_viewer-margin-right"--></a>
4369 <li><a href="h_config_viewer_overlap">OPTION: <!--#echo var="VAR_viewer-overlap"--></a>
4370 <li><a href="h_config_window_position">OPTION: Window-Position</a>
4371 <li><a href="h_mainhelp_patterns">Patterns</a>
4372 <li><a href="h_config_role_abookfrom">PATTERNS: Address in Address Book</a>
4373 <li><a href="h_config_role_age">PATTERNS: Age Interval</a>
4374 <li><a href="h_config_role_alltextpat">PATTERNS: AllText Pattern</a>
4375 <li><a href="h_config_role_bom">PATTERNS: Beginning of Month</a>
4376 <li><a href="h_config_role_boy">PATTERNS: Beginning of Year</a>
4377 <li><a href="h_config_role_bodytextpat">PATTERNS: BodyText Pattern</a>
4378 <li><a href="h_config_role_cat_cmd">PATTERNS: Categorizer Command</a>
4379 <li><a href="h_config_role_cat_cmd_example">PATTERNS: Categorizer Command Example</a>
4380 <li><a href="h_config_role_ccpat">PATTERNS: Cc Pattern</a>
4381 <li><a href="h_config_role_cat_limit">PATTERNS: Character Limit</a>
4382 <li><a href="h_config_role_charsetpat">PATTERNS: Character Set Pattern</a>
4383 <li><a href="h_config_role_comment">PATTERNS: Comment</a>
4384 <li><a href="h_config_role_fldr_type">PATTERNS: Current Folder Type</a>
4385 <li><a href="h_config_role_cat_status">PATTERNS: Exit Status Interval</a>
4386 <li><a href="h_config_role_arbpat">PATTERNS: Extra Headers Pattern</a>
4387 <li><a href="h_config_role_frompat">PATTERNS: From Pattern</a>
4388 <li><a href="h_config_role_keywordpat">PATTERNS: Keyword Pattern</a>
4389 <li><a href="h_config_role_stat_ans">PATTERNS: Message Answered Status</a>
4390 <li><a href="h_config_role_stat_del">PATTERNS: Message Deleted Status</a>
4391 <li><a href="h_config_role_stat_imp">PATTERNS: Message Important Status</a>
4392 <li><a href="h_config_role_stat_new">PATTERNS: Message New Status</a>
4393 <li><a href="h_config_role_stat_recent">PATTERNS: Message Recent Status</a>
4394 <li><a href="h_config_role_newspat">PATTERNS: News Pattern</a>
4395 <li><a href="h_config_role_nick">PATTERNS: Nickname</a>
4396 <li><a href="h_config_role_particpat">PATTERNS: Participant Pattern</a>
4397 <li><a href="h_config_role_stat_8bitsubj">PATTERNS: Raw 8-bit in Subject</a>
4398 <li><a href="h_config_role_recippat">PATTERNS: Recipient Pattern</a>
4399 <li><a href="h_config_role_scorei">PATTERNS: Score Interval</a>
4400 <li><a href="h_config_role_senderpat">PATTERNS: Sender Pattern</a>
4401 <li><a href="h_config_role_size">PATTERNS: Size Interval</a>
4402 <li><a href="h_config_role_subjpat">PATTERNS: Subject Pattern</a>
4403 <li><a href="h_config_role_topat">PATTERNS: To Pattern</a>
4404 <li><a href="h_config_filt_opts_nonterm">PATTERNS FEATURE: Dont-Stop-Even-if-Rule-Matches</a>
4405 <li><a href="h_config_filt_opts_notdel">PATTERNS FEATURE: Move-Only-if-Not-Deleted</a>
4406 <li><a href="h_config_filt_opts_sentdate">PATTERNS FEATURE: Use-Date-Header-For-Age</a>
4407 <li><a href="h_config_filt_rule_type">PATTERNS FILTER ACTION: Filter Action</a>
4408 <li><a href="h_config_filter_kw_clr">PATTERNS FILTER ACTION: Clear These Keywords</a>
4409 <li><a href="h_config_filt_stat_ans">PATTERNS FILTER ACTION: Set Answered Status</a>
4410 <li><a href="h_config_filt_stat_del">PATTERNS FILTER ACTION: Set Deleted Status</a>
4411 <li><a href="h_config_filt_stat_imp">PATTERNS FILTER ACTION: Set Important Status</a>
4412 <li><a href="h_config_filt_stat_new">PATTERNS FILTER ACTION: Set New Status</a>
4413 <li><a href="h_config_filter_kw_set">PATTERNS FILTER ACTION: Set These Keywords</a>
4414 <li><a href="h_config_incol">PATTERNS INDEXCOLOR ACTION: Index Line Color</a>
4415 <li><a href="h_config_set_index_format">PATTERNS OTHER ACTION: Set Index Format</a>
4416 <li><a href="h_config_perfolder_sort">PATTERNS OTHER ACTION: Set Sort Order</a>
4417 <li><a href="h_config_other_startup">PATTERNS OTHER ACTION: Set Startup Rule</a>
4418 <li><a href="h_config_role_inick">PATTERNS ROLE ACTION: Initialize Values From Role</a>
4419 <li><a href="h_config_role_setfcc">PATTERNS ROLE ACTION: Set Fcc</a>
4420 <li><a href="h_config_role_setfrom">PATTERNS ROLE ACTION: Set From</a>
4421 <li><a href="h_config_role_setlitsig">PATTERNS ROLE ACTION: Set Literal Signature</a>
4422 <li><a href="h_config_role_setotherhdr">PATTERNS ROLE ACTION: Set Other Headers</a>
4423 <li><a href="h_config_role_setreplyto">PATTERNS ROLE ACTION: Set Reply-To</a>
4424 <li><a href="h_config_role_setsig">PATTERNS ROLE ACTION: Set Signature</a>
4425 <li><a href="h_config_role_settempl">PATTERNS ROLE ACTION: Set Template</a>
4426 <li><a href="h_config_role_usenntp">PATTERNS ROLE ACTION: Use NNTP Server</a>
4427 <li><a href="h_config_role_usesmtp">PATTERNS ROLE ACTION: Use SMTP Server</a>
4428 <li><a href="h_config_role_scoreval">PATTERNS SCORE ACTION: Score Value</a>
4429 <li><a href="h_config_role_scorehdrtok">PATTERNS SCORE ACTION: Score Value From Header</a>
4430 <li><a href="h_config_role_composeuse">PATTERNS USE: Compose Use</a>
4431 <li><a href="h_config_role_forwarduse">PATTERNS USE: Forward Use</a>
4432 <li><a href="h_config_role_replyuse">PATTERNS USE: Reply Use</a>
4433 <li><a href="h_pipe_command">Pipe Command SubOptions</a>
4434 <li><a href="h_common_pipe">Pipe Command</a>
4435 <li><a href="h_valid_folder_names">POP</a>
4436 <li><a href="h_common_postpone">Postpone Command</a>
4437 <li><a href="h_common_print">Print Command</a>
4438 <li><a href="h_mainhelp_readingnews">Reading News</a>
4439 <li><a href="h_news">RELEASE NOTES for Alpine</a>
4440 <li><a href="h_mainhelp_roles">Roles</a>
4441 <li><a href="h_role_select">ROLES SCREEN</a>
4442 <li><a href="h_compose_readfile">Read File Command</a>
4443 <li><a href="h_mainhelp_reading">Reading Messages</a>
4444 <li><a href="h_main_release_notes">Release Notes Command</a>
4445 <li><a href="h_common_reply">Reply and Forward Commands</a>
4446 <li><a href="h_compose_richhdr">Rich Header Command</a>
4447 <li><a href="h_common_role">Role Command</a>
4448 <li><a href="h_mainhelp_smime">S/MIME</a>
4449 <li><a href="h_index_cmd_select">Searching for Messages</a>
4450 <li><a href="h_address_display">SEARCH RESULTS INDEX</a>
4451 <li><a href="h_address_select">SEARCH RESULTS INDEX</a>
4452 <li><a href="h_simple_index">SELECT POSTPONED MESSAGE</a>
4453 <li><a href="h_abook_config">SETUP ADDRESS BOOKS SCREEN</a>
4454 <li><a href="h_collection_maint">SETUP COLLECTION LIST screen</a>
4455 <li><a href="h_color_setup">SETUP COLOR COMMANDS</a>
4456 <li><a href="h_direct_config">SETUP LDAP DIRECTORY SERVERS SCREEN</a>
4457 <li><a href="h_rules_roles">SETUP ROLES SCREEN</a>
4458 <li><a href="h_rules_incols">SETUP INDEX COLORS SCREEN</a>
4459 <li><a href="h_rules_filter">SETUP FILTERING SCREEN</a>
4460 <li><a href="h_rules_score">SETUP SCORING SCREEN</a>
4461 <li><a href="h_common_save">Save and Export Commands</a>
4462 <li><a href="h_mainhelp_securing">Securing Your Alpine Session</a>
4463 <li><a href="h_index_cmd_select">Selecting: Select and WhereIs/Select</a>
4464 <li><a href="h_compose_send">Send Command</a>
4465 <li><a href="h_folder_server_syntax">Server Name Syntax</a>
4466 <li><a href="h_main_setup">Setup Command</a>
4467 <li><a href="X-Alpine-Config:">Show Supported Options in this Alpine</a>
4468 <li><a href="h_composer_sigedit">Signature Editor Commands Explained</a>
4469 <li><a href="h_simple_text_view">Simple Text View Screen Explained</a>
4470 <li><a href="h_mainhelp_smime">S/MIME</a>
4471 <li><a href="h_config_smime_dont_do_smime">S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></a>
4472 <li><a href="h_config_smime_encrypt_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></a>
4473 <li><a href="h_config_smime_remember_passphrase">S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></a>
4474 <li><a href="h_config_smime_sign_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></a>
4475 <li><a href="h_config_smime_use_cert_store">S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></a>
4476 <li><a href="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></a>
4477 <li><a href="h_config_smime_cacertcon">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></a>
4478 <li><a href="h_config_smime_cacertdir">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></a>
4479 <li><a href="h_config_smime_privkeycon">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-container"--></a>
4480 <li><a href="h_config_smime_privkeydir">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-directory"--></a>
4481 <li><a href="h_config_smime_pubcertcon">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-container"--></a>
4482 <li><a href="h_config_smime_pubcertdir">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></a>
4483 <li><a href="h_config_smime_transfer_cacert_to_con">S/MIME: Transfer CA Certs to Container</a>
4484 <li><a href="h_config_smime_transfer_cacert_to_dir">S/MIME: Transfer CA Certs to Directory</a>
4485 <li><a href="h_config_smime_transfer_priv_to_con">S/MIME: Transfer Private Keys to Container</a>
4486 <li><a href="h_config_smime_transfer_priv_to_dir">S/MIME: Transfer Private Keys to Directory</a>
4487 <li><a href="h_config_smime_transfer_pub_to_con">S/MIME: Transfer Public Certs to Container</a>
4488 <li><a href="h_config_smime_transfer_pub_to_dir">S/MIME: Transfer Public Certs to Directory</a>
4489 <li><a href="h_config_smime_public_certificates">S/MIME: Manage Public Certificates</a>
4490 <li><a href="h_config_smime_private_keys">S/MIME: Manage Private Keys</a>
4491 <li><a href="h_config_smime_certificate_authorities">S/MIME: Manage Certificate Authorities</a>
4492 <li><a href="h_index_cmd_sort">Sort Command</a>
4493 <li><a href="h_compose_spell">Spell Check Command</a>
4494 <li><a href="h_common_suspend">Suspend Command</a>
4495 <li><a href="h_compose_addrcomplete">THE MESSAGE COMPOSER'S ADDRESS COMPLETION</a>
4496 <li><a href="h_composer_attachment">THE MESSAGE COMPOSER'S ATTCHMNT FIELD</a>
4497 <li><a href="h_composer_bcc">THE MESSAGE COMPOSER'S BCC FIELD</a>
4498 <li><a href="h_composer_cc">THE MESSAGE COMPOSER'S CC FIELD</a>
4499 <li><a href="h_composer_from">THE MESSAGE COMPOSER'S FROM FIELD</a>
4500 <li><a href="h_composer_lcc">THE MESSAGE COMPOSER'S LCC FIELD</a>
4501 <li><a href="h_composer_news">THE MESSAGE COMPOSER'S NEWSGRPS LINE</a>
4502 <li><a href="h_composer_reply_to">THE MESSAGE COMPOSER'S REPLY-TO FIELD</a>
4503 <li><a href="h_composer_to">THE MESSAGE COMPOSER'S TO FIELD</a>
4504 <li><a href="h_abook_opened">THE ALPINE ADDRESS BOOK</a>
4505 <li><a href="h_abook_select_nicks_take">Take Address Nickname Selection Explained</a>
4506 <li><a href="h_takeaddr_screen">Take Address Screen Explained</a>
4507 <li><a href="h_common_take">TakeAddr Command</a>
4508 <li><a href="h_mainhelp_status">Titlebar Line</a>
4509 <li><a href="h_index_tokens">Tokens for Index and Replying</a>
4510 <li><a href="h_config_usenone_color">Use None Color</a>
4511 <li><a href="h_config_usenormal_color">Use Normal Color</a>
4512 <li><a href="h_config_usetransparent_color">Use Transparent Color</a>
4513 <li><a href="h_whatis_vcard">VCARD EXPLAINED</a>
4514 <li><a href="h_view_cmd_hilite">View Hilite and Next item/Previous item</a>
4515 <li><a href="h_view_cmd_viewattch">ViewAttch Command</a>
4516 <li><a href="h_index_cmd_whereis">WhereIs Command</a>
4517 <li><a href="h_view_cmd_whereis">WhereIs Command</a>
4518 <li><a href="h_index_cmd_zoom">ZoomMode Command</a>
4519 <li><a href="h_config_browser_xterm"><!--#echo var="VAR_url-viewers"--> and X windows applications</a>
4523 <End of Help Index>
4528 ============== h_config_remote_config =============
4531 <TITLE>Remote Configuration</TITLE>
4534 <H1>Remote Configuration</H1>
4536 You may use the command line argument "-p pinerc" to tell
4537 Alpine to use a non-default configuration file.
4538 There are two types of storage for configuration information.
4539 <EM>Local</EM> configuration files are used by default.
4540 These are just regular files on the UNIX system or on the PC.
4541 The file "<CODE>.pinerc</CODE>" is the default for Unix Alpine and the
4542 file "<CODE>PINERC</CODE>" is the default for PC-Alpine.
4543 <EM>Remote</EM> configuration folders are stored on an IMAP server.
4544 The advantage of using a remote configuration is that the same information
4545 may be accessed from multiple platforms.
4546 For example, if you use one computer at work and another at home, the same
4547 configuration could be used from both places.
4548 A configuration change from one place would be seen in both places.
4549 To use a remote configuration you simply give a
4550 <A HREF="h_valid_folder_names">remote folder name</A>
4551 as the argument to the "-p" command line option.
4552 The command line might look something like:
4554 <CENTER><SAMP>pine -p {my.imap.server}remote_pinerc</SAMP></CENTER>
4556 If there are special characters in the command shell you use, you may need to
4557 quote the last argument (to protect the curly braces from the shell).
4558 The command might look like:
4560 <CENTER><SAMP>pine -p "{my.imap.server}remote_pinerc"</SAMP></CENTER>
4562 You should choose a folder name for a folder that does not yet exist.
4563 It will be created containing an empty configuration.
4564 Do not use a folder that you wish to store regular mail messages in.
4566 The Setup/RemoteConfigSetup command will help you convert from a local
4567 configuration to a remote configuration.
4568 It will create a remote configuration for you and copy your current local
4569 configuration to it.
4570 It will also help you convert local address books into remote address books
4571 and local signature files into literal signatures contained in the
4572 remote configuration file.
4574 If the Setup/RemoteConfigSetup command doesn't do what you want, you
4575 may copy a local pinerc file to a remote configuration folder by hand
4576 by using the command line option "-copy_pinerc".
4578 Another command line option, which is somewhat related to remote
4579 configuration, is the option "-x exceptions_config".
4580 The configuration settings in the exceptions configuration override
4581 your default settings.
4582 It may be useful to store the default configuration (the -p argument) remotely
4583 and to have the exceptions configuration stored in a local file.
4584 You might put generic configuration information in the remote configuration
4585 and platform-specific configuration on each platform in the exceptions
4587 The arguments to the "-p" and "-x" options
4588 can be either remote folders or local files.
4590 There is another command line argument that works only with PC-Alpine and
4591 which may prove useful when using a remote configuration.
4592 The option "-aux local_directory" allows you to tell PC-Alpine where
4593 to store your local auxiliary files.
4594 This only has an effect if your configuration file is remote.
4595 Some examples of auxiliary files are debug files, address book files, and
4598 <End of help on this topic>
4601 ============== h_config_exceptions =============
4604 <TITLE>Generic and Exceptional Configuration</TITLE>
4607 <H1>Generic and Exceptional Configuration</H1>
4609 If you use Alpine from more than one platform it may be convenient
4610 to split your configuration information into two pieces, a generic piece
4611 and exceptions that apply to a particular platform.
4612 For example, suppose you use Alpine from home and from work.
4613 Most of your configuration settings are probably the
4614 same in both locations, so those settings belong in the generic settings
4616 However, you may use a different SMTP server and INBOX
4617 from home than you do from work.
4619 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
4621 <A HREF="h_config_inbox_path">"<!--#echo var="VAR_inbox-path"-->"</A>
4623 part of your exceptional configuration so that they could be different in the
4626 The command line option "-x exceptions_config"
4627 may be used to split your configuration into generic and exceptional pieces.
4628 "Exceptions_config" may be either local or remote.
4629 The regular Alpine configuration file will contain the generic data, and
4630 "exceptions_config" will contain the exceptional data.
4632 For Unix Alpine, if you don't have a "-x" command line option,
4633 Alpine will look for the file "<CODE>.pinercex</CODE>"
4634 in the same local directory that the regular config file is located in (usually
4635 the Unix home directory).
4636 If the regular config file is remote (because the command line option
4637 "-p remote_config" was used) then Unix Alpine looks in the Unix home
4638 directory for "<CODE>.pinercex</CODE>".
4639 If the file does not already exist then no exceptions will be used.
4640 You can force exceptions to be used by using the "-x" option or
4641 by creating an empty "<CODE>.pinercex</CODE>" file.
4643 For PC-Alpine, if you don't have a "-x" command line option,
4644 PC-Alpine will use the value of the
4645 environment variable <CODE>$PINERCEX</CODE>.
4646 If that is not set, PC-Alpine will look for
4647 the local file "<CODE>PINERCEX</CODE>"
4648 in the same local directory that the regular config file is located in.
4649 If the regular config file is remote (because the command line option
4650 "-p remote_config" was used) then PC-Alpine looks in the
4651 local directory specified by the "-aux local_directory" command
4652 line argument, or the directory <CODE>$HOME\PINE</CODE>, or
4653 in the <CODE><PINE.EXE </CODE>directory<CODE>></CODE>.
4655 When you have an exception configuration there is a new command
4656 in the Alpine Setup screen, Setup/eXceptions.
4657 It toggles between exceptions and the regular configuration.
4658 This is the usual way to make changes in your exceptional configuration data.
4659 For example, you would type "S" for Setup, "X" for
4660 eXception, then follow that with one of the Setup commands, like "C"
4661 for Config or "K" for Kolor.
4663 For most people, splitting the configuration information into two pieces is
4664 going to be most useful if the generic information is accessed
4665 <A HREF="h_config_remote_config">remotely</A>).
4666 That data will be the same no matter where you access it from and if you
4667 change it that change will show up everywhere.
4668 The exceptional data will most commonly be in a local file, so that the
4669 contents may easily be different on each computing platform used.
4671 If you already have a local configuration file with settings you like
4672 you may find that the command Setup/RemoteConfigSetup is useful
4673 in helping you convert to a remote configuration.
4674 The command line flag "-copy_pinerc"
4677 <End of help on this topic>
4680 ============== h_config_inheritance =============
4683 <TITLE>Configuration Inheritance</TITLE>
4686 <H1>Configuration Inheritance</H1>
4688 Configuration inheritance is a power user feature.
4689 It is confusing and not completely supported by the configuration
4691 We start with an explanation of how configuration works in hopes of making
4692 it easier to describe how inheritance works.
4694 Alpine uses a hierarchy of configuration values from different locations.
4695 There are five ways in which each configuration option (configuration
4696 variable) can be set.
4697 In increasing order of precedence they are:
4700 <LI> the system-wide configuration file.
4702 <LI> the personal configuration file
4704 <LI> the personal exceptions file
4706 <LI> a command line argument
4708 <LI> the system-wide <EM>fixed</EM> configuration file (Unix Alpine only)
4711 The fixed configuration file is normally
4712 <CODE><!--#echo var="PINE_CONF_FIXED_PATH"--></CODE>.
4714 The system-wide configuration file is normally
4715 <CODE><!--#echo var="PINE_CONF_PATH"--></CODE> for Unix Alpine and is normally not
4717 For PC-Alpine, if the environment variable <EM>$PINECONF</EM> is set, that
4718 is used for the system-wide configuration.
4719 This location can be set or changed on the command line with the -P flag.
4720 The system-wide configuration file can be either a local file or a
4721 remote configuration folder.
4723 For Unix Alpine, the personal configuration file is normally the file
4724 <CODE>.pinerc</CODE> in the user's home directory.
4725 This can be changed with the -p command line flag.
4726 For PC-Alpine, the personal configuration file is in
4727 <CODE>$PINERC</CODE> or <CODE><AlpineRC registry value></CODE> or
4728 <CODE>$HOME\PINE\PINERC</CODE> or
4729 <CODE><PINE.EXE </CODE>dir<CODE>>\PINERC</CODE>.
4730 This can be changed with the -p command line flag.
4731 If -p is used, the configuration data may be in a local file or a remote config
4734 For Unix Alpine, the personal exceptions configuration file is named
4735 <CODE>.pinercex</CODE> and is in the same directory as the personal
4736 configuration file, if that configuration file is not remote, and is in
4737 the home directory if the personal configuration file is remote.
4738 If the file exists, then exceptions are turned on.
4739 If it doesn't, then you are not using exceptions.
4740 Alternatively, you may change the location of the exceptions configuration
4741 by using the command line argument "-x <exceptions_config>".
4742 Like the personal configuration data, exceptions_config may be
4743 either local or remote.
4745 For PC-Alpine, the personal exceptions configuration file is named
4746 <CODE>PINERCEX</CODE> and is in the same directory as the personal
4747 configuration file unless the personal configuration file is remote.
4748 In that case, it is in the local directory specfied by the
4749 "-aux local_directory" command line argument.
4750 (In the case that the personal configuration is remote and there is no
4751 "-aux" command line argument, Alpine searches for
4752 a PINERCEX file in the directory <CODE>$HOME\PINE</CODE> and
4753 the directory <CODE><PINE.EXE </CODE>dir<CODE>></CODE>.)
4754 If the file exists, then exceptions are turned on.
4755 If it doesn't, then you are not using exceptions.
4756 You may change the location of the exceptions configuration
4757 by using the command line argument "-x <exceptions_config>".
4759 environment variable <CODE>$PINERCEX</CODE> (if there is no "-x"
4762 To reiterate, the value of a configuration option is taken from the
4763 last location in the list above in which it is set.
4764 Or, thinking about it slightly differently, a default value for an option
4765 is established in the system-wide configuration file (or internally by Alpine
4766 if there is no value in the system-wide file).
4767 That default remains in effect until and unless it is overridden by a value in a
4768 location further down the list, in which case a new "default"
4769 value is established.
4770 As we continue down the list of locations we either retain the
4771 value at each step or establish a new value.
4772 The value that is still set after going through the whole list of
4773 configuration locations is the one that is used.
4775 So, for example, if an option is set in the system-wide configuration
4776 file and in the personal configuration file, but is not set in the
4777 exceptions, on the command line, or in the fixed file; then the value
4778 from the personal configuration file is the one that is used.
4779 Or, if it is set in the system-wide config, in the personal config, not
4780 in the exceptions, but is set on the command line; then the value
4781 on the command line is used.
4783 Finally we get to inheritance.
4784 For configuration options that are lists, like "<!--#echo var="VAR_smtp-server"-->" or
4785 "<!--#echo var="VAR_incoming-folders"-->",
4786 the inheritance mechanism makes it possible to <EM>combine</EM>
4787 the values from different locations instead of <EM>replacing</EM> the value.
4788 This is true of all configuration lists other than the "Feature-List",
4789 for which you may already set whatever you want at
4790 any configuration location (by using the "no-" prefix if
4793 To use inheritance, set the first item in a configuration list to the
4794 token "INHERIT", without the quotes.
4795 If the first item is "INHERIT",
4796 then instead of replacing the default value established so far, the rest of
4797 the list is appended to the default value established so far and that is
4800 Here is an example which may make it clearer. Suppose we have:
4803 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4804 Personal config : smtp-server = INHERIT, mysmtp.home
4805 Exceptions config : smtp-server = <No Value Set>
4806 Command line : smtp-server = <No Value Set>
4807 Fixed config : smtp-server = <No Value Set>
4811 This would result in an effective smtp-server option of
4814 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home
4817 The "INHERIT" token can be used in any of the configuration files
4818 and the effect cascades.
4819 For example, if we change the above example to:
4822 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4823 Personal config : smtp-server = INHERIT, mysmtp.home
4824 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4825 Command line : smtp-server = <No Value Set>
4826 Fixed config : smtp-server = <No Value Set>
4830 This would result in:
4833 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home, yoursmtp.org
4836 Unset variables are skipped over (the default value is carried forward) so
4840 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4841 Personal config : smtp-server = <No Value Set>
4842 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4843 Command line : smtp-server = <No Value Set>
4844 Fixed config : smtp-server = <No Value Set>
4851 smtp-server = smtp1.corp.com, smtp2.corp.com, yoursmtp.org
4855 If any later configuration location has a value set (for a particular list
4856 option) which does <EM>not</EM> begin with "INHERIT",
4857 then that value replaces whatever value has been defined up to that point.
4858 In other words, that cancels out any previous inheritance.
4861 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4862 Personal config : smtp-server = INHERIT, mysmtp.org
4863 Exceptions config : smtp-server = yoursmtp.org
4864 Command line : smtp-server = <No Value Set>
4865 Fixed config : smtp-server = <No Value Set>
4872 smtp-server = yoursmtp.org
4876 For some configuration options, like "<!--#echo var="VAR_viewer-hdr-colors"-->" or
4877 "<!--#echo var="VAR_patterns-roles"-->", it is
4878 difficult to insert the value "INHERIT" into the list of values
4879 for the option using the normal Setup tools.
4880 In other words, the color setting screen (for example) does not
4881 provide a way to input the text "INHERIT" as the first
4882 item in the <!--#echo var="VAR_viewer-hdr-colors"--> option.
4883 The way to do this is to either edit the pinerc file directly and manually
4885 on the <A HREF="h_config_expose_hidden_config"><!--#echo var="FEAT_expose-hidden-config"--></A>
4886 feature and insert it using the Setup/Config screen.
4888 <End of help on this topic>
4891 ============== h_special_xon_xoff =============
4894 <TITLE>Explanation of Alpine's XOFF/XON Handling</TITLE>
4897 <H1>XOFF/XON Handling within Alpine</H1>
4899 By default, Alpine treats Ctrl-S or Ctrl-Q (sometimes known as XOFF
4900 and XON) as normal characters, even though Alpine does not use them.
4901 However, the printer, modem, or communication software you are using may
4902 be configured for "software flow control," which means that
4903 XON/XOFF must be treated as special characters by the operating system.
4904 If you see messages such as "^S not defined for this screen",
4905 then your system is probably using software flow control. In this case
4906 you will need to set the
4907 <A HREF="h_config_preserve_start_stop">"<!--#echo var="FEAT_preserve-start-stop-characters"-->"</A>
4910 If you <EM>do</EM> set this
4911 feature, be advised that if you accidentally hit a Ctrl-S, Alpine will
4912 mysteriously freeze up with no warning. In this case, try typing a Ctrl-Q
4913 and see if that puts things right. Printing via the
4914 "attached-to-ansi" or
4915 "attached-to-wyse"
4916 option will automatically enable software
4917 flow-control handling for the duration of the printing.
4919 <End of help on this topic>
4922 ============= h_special_help_nav =============
4925 <TITLE>Help Text Navigation Explained</TITLE>
4928 <H1>Help Text Navigation Explained</H1>
4930 Alpine contains extensive context-sensitive help text. At any point,
4931 pressing the "?" key will bring up a page of help text
4932 explaining the options available to you. You can leave the help
4933 text screen and return to normal Alpine operation by pressing
4935 <!--chtml if pinemode="function_key"-->
4940 key to Exit Help at any time.
4943 Within the help screen you might find a word or phrase displayed in
4944 inverse text and others displayed in bold typeface. Such words and
4945 phrases are used to tell you Alpine has more information available on
4946 the topic they describe.
4947 The inverted text is the "selected" topic.
4948 Use the arrow keys, Ctrl-F, and Ctrl-B to change which of the phrases
4949 displayed in bold type
4950 is "selected".
4951 Hit the Return key to display the information Alpine has available on that
4952 topic. While viewing such additional information, the
4953 <!--chtml if pinemode="function_key"-->
4958 key will return you to the previous help screen, and the
4959 <!--chtml if pinemode="function_key"-->
4964 key will Exit the Help system altogether.
4967 The "N" command will tell you the internal name of the help text you are
4968 reading each time, so that you can send this name in the text of a message
4969 and create a direct link to that internal help using the x-pine-help URL
4970 scheme. For example, the direct link to this item is
4971 x-pine-help:h_special_help_nav. If you add this text to a message, then
4972 a person using Pine to read such message would have a direct link to this
4976 When you are finished reading this help text, you can press the
4977 <!--chtml if pinemode="function_key"-->
4982 key to return to the previously displayed help text.
4985 <End of help on this topic>
4988 ============= h_special_list_commands =============
4991 <TITLE>Email List Commands Explained</TITLE>
4994 <H1>Email List Commands Explained</H1>
4996 Electonic mail lists provide a way for like-minded users to join in
4997 discussions on topics of interest. The email list itself is
4999 single address that participants send messages to when they have
5000 something of interest to share with other members of the list. The
5001 receiving computer then, either automatically or after review by the
5002 list's owner (or moderator), sends a copy of that message to each
5006 Usually, subscribing and unsubscribing is done by sending requests in
5007 an email message to a special address setup to handle managing list
5008 membership. Often this is the name of the list followed by
5009 <I>-request</I>. This address is almost <EM>never</EM> the same as
5010 the address used to send messages to the list.
5013 Unfortunately, email list participation commands are more a matter
5014 of convention than standard, and thus may vary from list to list.
5015 Increasingly, list management software is adding information to
5016 the copy of the postings as they're copied to the list members that
5017 explains how to do the various list management functions.
5020 Alpine will recognize this information and offer the management commands
5021 they represent in a simple display. One or more of the following
5022 operations will be made available:
5027 A method to get help on subscribing, unsubscribing,
5028 an explanation of what the list is about, or special instructions
5029 for participation. This may be in the form of a reply in response
5030 to an email message, or instructions on how to connect to a Web site.
5033 <DT>Unsubscribe</DT>
5035 A method to get your email addressed removed from the list of
5036 recipients of the email list.
5041 A method to get your email address added to the list of recipients
5042 of the email list. It may be in the form of a message sent to
5043 a special address or you may be connected to a web site.
5049 A method used to post to the email list. However, it might also
5050 indicate that no posting is allowed directly to the list.
5055 A method to contact the list owner for special questions you might
5056 have regarding the list.
5061 A method to view an archive of previous messages posted to the list.
5062 This may be in the form of a mail folder on a remote computer, an
5063 IMAP mailbox or even a Web site.
5068 <End of help on this topic>
5071 ============= h_quota_command =============
5074 <TITLE>Quota Screen Explained</TITLE>
5077 <H1>Quota Screen Explained</H1>
5079 <P> This screen summarizes the quota report for this mailbox in the
5080 IMAP server. For each resource that you have a quota, this reports summarizes
5083 <P> Your IMAP server administrator may have set a quota based either on
5084 the total size of your mailbox (STORAGE), or the number of messages in
5085 your mailbox (MESSAGES), or some other criteria. This will be reported
5086 to you indicating the type of quota, its total use and its limit.
5088 <P> The report for STORAGE is reported in kibibytes (KiB). One kibibyte is
5089 1024 bytes. Each of the characters that you see in this help text is one
5090 byte, and this help text is about 1 kibibyte in size. Small messages sent
5091 by Alpine are normally less than 4 kibibytes in size (which includes
5092 headers and text). Other email programs may send messages with bigger
5093 sizes when they send messages, since they send plain text and an
5094 alternative part in HTML.
5096 <P> A convenient way to save space for the STORAGE type of quota is by
5097 deleting attachments. This is done on each individual message by pressing
5098 the "V" command while reading the message text, then moving the cursor
5099 to the position of the attachment that is to be deleted, then pressing
5100 "D" to delete such attachment, going back to reading the
5101 message with the "<" command and pressing "S" to
5102 save the message in the same folder you are reading from. The saved
5103 message will not have the attachment that was marked deleted. Now you
5104 can delete and expunge the message with the unwanted attachment.
5107 <End of help on this topic>
5110 ============= h_mail_thread_index =============
5113 <TITLE>THREAD INDEX COMMANDS</TITLE>
5116 <H1>THREAD INDEX COMMANDS</H1>
5117 <!--chtml if pinemode="function_key"-->
5118 Available Commands -- Group 1 Available Commands -- Group 2<BR>
5119 ------------------------------- -----------------------------<BR>
5120 F1 Show Help Text F1 Show Help Text<BR>
5121 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
5122 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
5123 F4 View current thread F4 Quit Alpine<BR>
5124 F5 Move to previous thread F5 <A HREF="h_common_compose">Compose</A> a message<BR>
5125 F6 Move to next thread F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5126 F7 Show previous screen F7 <A HREF="h_common_nextnew">Next new</A> thread<BR>
5127 F8 Show next screen F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
5128 F9 <A HREF="h_common_delete">Mark thread for deletion</A> F9 <A HREF="h_common_print">Print</A> index<BR>
5129 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
5130 F11 <A HREF="h_common_reply">Reply</A> to thread F11 <A HREF="h_common_save">Save</A> messages into an email folder<BR>
5131 F12 <A HREF="h_common_reply">Forward</A> messages F12 <A HREF="h_common_save">Export</A> messages into a plain file<BR>
5133 Available Commands -- Group 3<BR>
5134 -----------------------------<BR>
5135 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>
5136 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>
5137 F6 F9 <A HREF="h_common_hdrmode">Full Header Mode</A> F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
5139 Available Commands -- Group 4<BR>
5140 -----------------------------<BR>
5141 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
5142 F6 <A HREF="h_common_role">Compose using a role</A><BR>
5145 Navigating the List of Threads Operations on the Current Thread<BR>
5146 ------------------------------- ---------------------------------<BR>
5147 P Move to the previous thread > View Thread % <A HREF="h_common_print">Print</A><BR>
5148 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>
5149 - Show previous screen D <A HREF="h_common_delete">Mark thread for deletion</A><BR>
5150 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
5151 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>
5152 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>
5153 specific thread E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5154 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>
5155 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
5157 Miscellaneous Operations General Alpine Commands<BR>
5158 ------------------------ ---------------------<BR>
5159 G <A HREF="h_common_goto">Goto</A> a specified folder O Show all other available commands<BR>
5160 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ? Show Helptext Q Quit Alpine<BR>
5161 H <A HREF="h_common_hdrmode">Full header mode</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5162 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> C <A HREF="h_common_compose">Compose</A> a new message<BR>
5163 Z <A HREF="h_index_cmd_zoom">Zoom</A> # <A HREF="h_common_role">Compose using a role</A><BR>
5164 ; <A HREF="h_index_cmd_select">Select</A> A <A HREF="h_index_cmd_apply">Apply</A> L COLLECTION LIST Screen<BR>
5165 : Select Messages in Current Thread<BR>
5171 <LI>For help on a particular command, highlight the bold text associated
5172 with it above and hit Return.
5173 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5176 <H2>Description of the THREAD INDEX Screen</H2>
5178 The THREAD INDEX displays summary information from each
5179 thread (conversation) in the current folder.
5180 This is useful if you want to quickly
5181 scan new threads, or find a particular thread without having to go
5182 through the text of each message, or to quickly get rid of junk
5184 The current thread is always highlighted.
5185 Each line of the THREAD INDEX contains the following columns: <P>
5188 <DD> The markings on the left side of the thread tell you about its
5189 status. You may see one or more of the following codes on any given
5192 <LI> "D" for Deleted. All of the messages in this thread are marked for deletion but not yet eXpunged from the folder.
5193 <LI> "A" for Answered. All of the messages in this thread are marked answered.
5194 <LI> "N" for New. At least one message in the thread is New (you haven't looked at it yet).
5195 <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.
5196 <LI> "-" for cc-to-you. The "-" indicates that a
5197 message in the thread was sent to you as a cc:. This symbol will only show up if
5199 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
5200 <LI> "X" for selected. You have selected at least one message in the thread by using the
5201 "select" command. (Some systems may optionally allow selected
5202 messages to be denoted by the index line being displayed in bold
5204 <LI> "*" for Important. You have previously used the "Flag" command
5205 to mark at least one message in this thread as "important".
5208 <DT>THREAD NUMBER:</DT>
5209 <DD>Threads in a folder are numbered, from one through the number
5210 of threads in the folder, to help you know where you are in the folder.
5213 <DT>DATE STARTED:</DT>
5214 <DD>The date the thread was started. This is actually from the Date header
5215 of the first message in the thread. It doesn't take different time zones
5216 into account.</DD><P>
5218 <DT>WHO STARTED THE THREAD:</DT>
5219 <DD>This is usually the name of the sender of the first message in the thread, taken from
5220 the From header of the message.
5221 If there is no personal name given in that
5222 address, then the email address is used instead.
5223 If the message is from you (or from one of your
5224 <A HREF="h_config_alt_addresses">alternate addresses</A>),
5225 then the recipient's name is shown here instead, with the characters
5226 "To: " inserted before the name.
5227 (The idea of this is that if you started the thread you would rather see who
5228 the mail was sent to instead of that the mail was from you.)
5229 In Newsgroups, if you are
5230 the sender and there are no email recipients, the newsgroup name will be
5231 listed after the "To: ".
5235 <DD>The number in parentheses is the number of messages in the thread.</DD><P>
5238 <DD>As much of the thread's subject line as will fit on the screen.
5239 This is the subject of the first message in the thread.</DD>
5243 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5246 <End of help on this topic>
5249 ============= h_mail_index =============
5252 <TITLE>MESSAGE INDEX COMMANDS</TITLE>
5255 <H1>MESSAGE INDEX COMMANDS</H1>
5256 <!--chtml if pinemode="function_key"-->
5257 Available Commands -- Group 1 Available Commands -- Group 2<BR>
5258 ------------------------------- -----------------------------<BR>
5259 F1 Show Help Text F1 Show Help Text<BR>
5260 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
5261 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
5262 F4 View current message F4 Quit Alpine<BR>
5263 F5 Move to previous message F5 <A HREF="h_common_compose">Compose</A> a message<BR>
5264 F6 Move to next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5265 F7 Show previous screen of messages F7 <A HREF="h_common_nextnew">Next new</A> message<BR>
5266 F8 Show next screen of messages F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
5267 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
5268 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
5269 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
5270 F12 <A HREF="h_common_reply">Forward</A> message F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
5272 Available Commands -- Group 3<BR>
5273 -----------------------------<BR>
5274 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>
5275 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>
5276 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>
5278 Available Commands -- Group 4<BR>
5279 -----------------------------<BR>
5280 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
5281 F6 <A HREF="h_common_role">Compose using a role</A> F10 <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread<BR>
5284 Navigating the List of Messages Operations on the Current Message<BR>
5285 ------------------------------- ---------------------------------<BR>
5286 P Move to the previous message > View % <A HREF="h_common_print">Print</A><BR>
5287 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>
5288 - Show previous screen of messages D <A HREF="h_common_delete">Mark for deletion</A><BR>
5289 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
5290 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>
5291 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>
5292 specific message E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5293 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>
5294 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
5295 Miscellaneous Operations<BR>
5296 ------------------------<BR>
5297 G <A HREF="h_common_goto">Goto</A> a specified folder General Alpine Commands<BR>
5298 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ---------------------<BR>
5299 H <A HREF="h_common_hdrmode">Full header mode</A> O Show all other available commands<BR>
5300 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> ? Show Help text Q Quit Alpine<BR>
5301 Z <A HREF="h_index_cmd_zoom">Zoom</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5302 ; <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>
5303 : Select Current message # <A HREF="h_common_role">Compose using a role</A><BR>
5304 / <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread L COLLECTION LIST Screen<BR>
5310 <LI>For help on a particular command, highlight the bold text associated
5311 with it above and hit Return.
5312 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5315 <H2>Description of the MESSAGE INDEX Screen</H2>
5317 The MESSAGE INDEX displays summary information from each
5318 message in the current folder.
5319 This is useful if you want to quickly
5320 scan new messages, or find a particular message without having to go
5321 through the text of each message, or to quickly get rid of junk
5324 The current message is always highlighted
5325 and many commands operate on the current message.
5326 For example, the Delete command will delete the current message.
5327 If the folder is sorted by either Threads or OrderedSubject, then, depending
5328 on some of your configuration settings, a single line in the index may
5329 refer to an entire thread or to a subthread.
5330 If that is the case, then the commands that normally operate on the current
5331 message will operate on the thread or subthread instead.
5332 For example, the Delete command will delete the whole collapsed thread
5333 instead of just a single message.
5335 Each line of the MESSAGE INDEX contains the following columns (by default --
5336 you can change this with the
5337 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
5338 in the SETUP CONFIGURATION screen): <P>
5341 <DD> The markings on the left side of the message tell you about its
5342 status. You may see one or more of the following codes on any given
5345 <LI> "D" for Deleted. You have marked this message for deletion but not
5346 yet eXpunged the folder.
5347 <LI> "N" for New. You have not looked at the text of the message yet.
5348 <LI> "A" for Answered. Any time you reply to a message it is considered
5350 <LI> "F" for Forwarded. Similar to Answered, this is set whenever you
5352 <LI> "+" for direct-to-you. The "+" indicates that a message was sent
5353 directly to your account, your copy is not part of a cc: or a
5355 <LI> "-" for cc-to-you. The "-" indicates that a
5356 message was sent to you as a cc:. This symbol will only show up if
5358 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
5359 <LI> "X" for selected. You have selected the message by using the
5360 "select" command. (Some systems may optionally allow selected
5361 messages to be denoted by the index line being displayed in bold
5363 <LI> "*" for Important. You have previously used the "Flag" command
5364 to mark this message as "important".
5367 <DT>MESSAGE NUMBER:</DT>
5368 <DD>Messages in a folder are numbered, from one through the number
5369 of messages in the folder, to help you know where you are in the folder.
5370 These numbers are always in increasing order, even if you sort the folder
5371 in a different way.</DD><P>
5374 <DD>The date the message was sent. By default, messages are
5375 ordered by arrival time, not by date sent. Most of the time, arrival time
5376 and date sent (effectively departure time) are similar. Sometimes,
5377 however, the index will appear to be out of order because a message took a
5378 long time in delivery or because the sender is in a different time
5379 zone than you are. This date is just the date from the Date header
5380 field in the message.</DD><P>
5382 <DT>WHO SENT THE MESSAGE:</DT>
5383 <DD>This is usually the name of the sender of the message, taken from
5384 the From header of the message.
5385 If there is no personal name given in that
5386 address, then the email address is used instead.
5387 If the message is from you (or from one of your
5388 <A HREF="h_config_alt_addresses">alternate addresses</A>),
5389 then the recipient's name is shown here instead, with the characters
5390 "To: " inserted before the name.
5391 (The idea of this is that if you sent the mail you would rather see who
5392 the mail was sent to instead of that the mail was from you.
5393 This behavior may be changed by modifying the <!--#echo var="VAR_index-format"--> option mentioned
5395 In particular, use the FROM token or the FROMORTONOTNEWS token
5396 in place of the FROMORTO token.)
5397 In Newsgroups, if you are
5398 the sender and there are no email recipients, the newsgroup name will be
5399 listed after the "To: ". </DD><P>
5402 <DD>The number in parentheses is the number of characters in the message.
5403 It may have a suffix of K, M, or G which means the number should be
5404 multiplied by one thousand, one million, or one billion to get the
5405 size of the message.</DD><P>
5408 <DD>As much of the message's subject line as will fit on the screen.</DD>
5412 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5415 <End of help on this topic>
5418 ============= h_mail_view ========================
5421 <TITLE>MESSAGE TEXT SCREEN</TITLE>
5424 <H1>MESSAGE TEXT SCREEN</H1>
5425 <!--chtml if pinemode="function_key"-->
5426 Available Commands -- Group 1 Available Commands -- Group 2<BR>
5427 ------------------------------- ------------------------------<BR>
5428 F1 Show Help Text F1 Show Help Text<BR>
5429 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
5430 F3 <A HREF="h_common_index">MESSAGE INDEX</A> Screen F3 MAIN MENU Screen<BR>
5431 F4 <A HREF="h_view_cmd_viewattch">View attachment</A> F4 Quit Alpine<BR>
5432 F5 Display previous message F5 <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5433 F6 Display next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5434 F7 Previous screen of this message F7 <A HREF="h_common_compose">Compose</A> message<BR>
5435 F8 Next screen of this message F8 <A HREF="h_view_cmd_whereis">Whereis</A><BR>
5436 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
5437 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
5438 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
5439 F12 <A HREF="h_common_reply">Forward</A> F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
5441 Available Commands -- Group 3<BR>
5442 ------------------------------<BR>
5443 F1 Show Help Text<BR>
5444 F2 Toggle to see more commands<BR>
5445 F3 <A HREF="h_view_cmd_hilite">View hilited</A><BR>
5446 F4 Select current message<BR>
5447 F5 Previous selectable item<BR>
5448 F6 Next selectable item<BR>
5449 F7 <A HREF="h_common_jump">Jump</A> to message number<BR>
5450 F8 <A HREF="h_common_nextnew">Next new</A> message<BR>
5451 F9 <A HREF="h_common_hdrmode">Display full headers</A><BR>
5452 F10 <A HREF="h_common_bounce">Bounce</A> message<BR>
5453 F11 <A HREF="h_common_flag">Flag</A> message<BR>
5454 F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
5455 Available Commands -- Group 4<BR>
5456 F5 <A HREF="h_common_role">Compose using a role</A><BR>
5458 Operations on the Current Message<BR>
5459 ---------------------------------<BR>
5461 - Show previous page of this msg S <A HREF="h_common_save">Save</A> into an email folder<BR>
5462 Spc (space bar) Show next page E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5463 > <A HREF="h_view_cmd_viewattch">View attachment</A> B <A HREF="h_common_bounce">Bounce</A><BR>
5464 R <A HREF="h_common_reply">Reply</A> to message F <A HREF="h_common_reply">Forward</A> message<BR>
5465 D <A HREF="h_common_delete">Mark for deletion</A> Ret View <A HREF="h_view_cmd_hilite">hilited</A> item<BR>
5466 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>
5467 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>
5468 % <A HREF="h_common_print">Print</A> * <A HREF="h_common_flag">Flag</A> message<BR>
5469 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>
5471 Navigating the List of Messages Other Commands<BR>
5472 ------------------------------- ----------------------------<BR>
5473 P Display previous message G <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5474 N Display next message H <A HREF="h_common_hdrmode">Full header mode</A> on/off<BR>
5475 J <A HREF="h_common_jump">Jump</A> to a specific message : Select Current message<BR>
5476 Tab <A HREF="h_common_nextnew">Next new</A> message A <A HREF="h_config_prefer_plain_text">Toggle Prefer Plain Text</A><BR>
5478 General Alpine Commands<BR>
5479 ---------------------<BR>
5480 O Show all other available commands<BR>
5481 ? Show Help text Q Quit Alpine<BR>
5482 M MAIN MENU Screen L <A HREF="h_common_folders">FOLDER LIST</A> Screen (or COLLECTION LIST Screen)<BR>
5483 < <A HREF="h_common_index">MESSAGE INDEX</A> Screen C <A HREF="h_common_compose">Compose</A> a new message<BR>
5484 # <A HREF="h_common_role">Compose using a role</A><BR>
5490 <LI>For help on a particular command, highlight the bold text associated
5491 with it above and hit Return.
5492 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5495 <H2>Description of the MESSAGE TEXT Screen</H2>
5497 The top line of the view message screen displays status
5498 information about the currently open collection and folder and about the
5499 current message. It shows the name of the collection in angle brackets
5500 and then the name of the folder. The line also displays the number
5501 of messages in the folder, the number of the current message and the
5502 percentage of the current message that has been displayed on the screen.
5503 If the message is marked for deletion "DEL" will appear in the upper
5505 If the message has been answered (but not deleted) "ANS" will show
5509 NOTE: to rapidly move to the end of a message, hit the
5510 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5511 (or Ctrl-W) key followed
5512 by Ctrl-V. Similarly,
5513 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5514 followed by Ctrl-Y will take you to the beginning of
5517 <H2>Explanation of Alternate Character Sets</H2>
5519 Alpine attempts to stay out of the way so that it won't prevent you from
5520 viewing mail in any character set. It will simply send the message to
5521 your display device. If the device is capable of displaying the
5522 message as it was written it will do so. If not, the display may be
5523 partially or totally incorrect.
5524 If the message contains characters that are not representable in your
5525 <A HREF="h_config_char_set">"Display Character Set"</A>
5526 variable in your configuration, then a warning message will be printed
5527 to your screen at the beginning of the message display.
5528 It is probably best to use UNIX Alpine in a terminal emulator
5529 capable of displaying UTF-8 characters.
5530 See <A HREF="h_config_char_set">Display Character Set</A> for a little
5531 more information about character set settings.
5534 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5537 <End of help on this topic>
5540 ======= h_index_cmd_select =======
5543 <TITLE>Selecting: Select and WhereIs/Select</TITLE>
5546 <H1>Selecting: Select and WhereIs/Select</H1>
5548 Aggregate operations give you the ability to process a group of messages
5549 at once. Acting on multiple messages requires two steps: (1) selecting a
5550 set of messages and then; (2) applying a command to that set. The first
5551 part is handled by the select command. Select allows you to
5552 select messages based on their status (read, answered, etc.), contents,
5553 date, size, or keywords.
5554 You may also select based on one of your Rules or based on threads,
5555 and there are quick options to select a specific message or range of messages,
5556 to select the current message, or to select all messages.
5559 We describe the various selection criteria briefly:
5564 <DD> Marks all the messages in the folder as selected.
5568 <DD> Selects the currently highlighted message or currently highlighted
5569 set of messages if in a threaded view.
5572 <DT>select by Number</DT>
5573 <DD> Select by message number. This may be a comma-separated list instead or
5575 Each element in the list may be either a single message number or a range
5576 of numbers with a dash between the lowest and highest member of the range.
5577 Some examples are 7 to select only message number 7; 2-5 to select messages
5578 2 through 5; and 2-5,7-9,11 to select messages 2, 3, 4, 5, 7, 8, 9, and 11.
5579 The word "end" or the character "$" may be used as a
5580 substitute for the highest numbered message in the folder, while the
5581 character "." represents the message number holding the position
5582 of the cursor in the folder.
5583 If in a separate thread index where the numbers refer to threads instead of
5584 to messages, then you will be selecting all of the messages in the
5585 referenced threads instead of selecting by message number.
5588 <DT>select by Date</DT>
5589 <DD> Select by either the date stored in the Date headers of each message,
5590 or by the date when the messages arrived.
5591 This does not adjust for different time zones, but just checks to see what
5592 day the message was sent on.
5593 You may type in a date. If you do, the date should be in the form
5594 <P><SAMP><CENTER>DD-Mon-YYYY</CENTER></SAMP><P>
5596 <P><SAMP><CENTER>24-Nov-2004</CENTER></SAMP><P>
5598 <P><SAMP><CENTER>09-Nov-2004</CENTER></SAMP><P>
5599 If the date you want is close to the current date, it is probably
5600 easier to use the "^P Prev Day" or "^N Next Day" commands to change the default date that
5601 is displayed, instead of typing in the date yourself.
5602 Or, the "^X Cur Msg" command may be used to fill in
5603 the date of the currently highlighted message.
5605 There are six possible settings that are selected using the
5606 "^W Toggle When" command.
5607 Three of them select messages based on the Date headers.
5608 They are "SENT SINCE", "SENT BEFORE",
5609 and "SENT ON".
5610 SINCE is all messages with the selected date or later.
5611 BEFORE is all messages earlier than the selected date (not including the day
5613 ON is all messages sent on the selected date.
5614 The other three select messages in the same way but they use the arrival
5615 times of the messages instead of the Date headers included in the messages.
5616 Those three are "ARRIVED SINCE", "ARRIVED BEFORE",
5617 and "ARRIVED ON".
5618 When you save a message from one folder to another the arrival time is
5622 <DT>select by Text</DT>
5623 <DD> Selects messages based on the message contents.
5624 This allows you to select a set of messages based on whether or not the
5625 message headers or message body contain specified text.
5626 You may look for text in the Subject, the From header,
5627 the To header, or the Cc header.
5628 You may also choose Recipient, which searches for the text in
5629 either the To or the Cc header;
5630 or Participant, which means To or Cc or From.
5631 Besides those specific header searches, you may also search the entire
5632 header and text of the message with "All Text", or just the
5633 body of the message.
5635 To search for the absence of text, first type the "! Not" command
5636 before typing the specific type of text search.
5637 For example, you could type "!" followed by "S" to
5638 search for all messages that do not contain a particular word in their
5641 If you choose a Subject search, you may use the subject from the current
5642 message by typing the "^X Cur Subject" command.
5643 You may then edit it further if you wish.
5644 For example, you might select the subject of a reply and edit the
5645 "Re: " off of the front of it in order to search for
5646 the original message being replied to.
5647 All of the other header searches allow you to use addresses from the
5648 headers of the current message if you want to.
5649 You may use the "^T Cur To", "^R Cur From", or
5650 "^W Cur Cc".
5651 In each case, if there is more than one address, only the first is offered.
5654 <DT>select by Status</DT>
5655 <DD> Selects messages based on their status.
5656 You may select all New, Important, Deleted, Answered, Recent, or Unseen
5658 Or, if you first type the "! Not" command, you get not New,
5659 or not Important, and so on.
5660 If you select Deleted messages, you will get all messages with their
5662 Likewise for Important messages, all messages that you have flagged as
5663 being Important with the
5664 <A HREF="h_common_flag">Flag</A> command.
5665 The "New" and "Answered" choices are a little bit odd
5666 because they try to match what you see on the screen by default.
5667 "New" is a shorthand for messages that are Unseen, Undeleted,
5669 If you have looked at the message, or deleted it, or answered it; then it
5670 is not considered "New ".
5671 "! New" is the opposite of "New".
5673 "Answered" is another one that is a little different.
5674 It means that the message has been Answered <EM>and</EM> is not deleted.
5675 And to make it even more confusing, "! Answered" is not
5676 the opposite of "Answered"!
5677 Instead, "! Answered" stands for messages that are
5678 both Unanswered <EM>and</EM> not deleted.
5680 The other two types were added later because the special nature of the
5681 New flag was not what was wanted by all users.
5682 New does match what you see in the index by default, but if you use
5683 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5684 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5685 be exactly what you want.
5686 "Unseen" simply selects all unseen messages, whether or not
5687 they are deleted or answered, and
5688 "Recent" selects all of the messages that have been added to
5689 the folder since you started this Alpine session.
5690 (That's not technically quite true. If there are multiple mail clients
5691 reading an IMAP mailbox, each message will be marked as Recent in only
5692 one of the client's sessions.)
5695 <DT>select by siZe</DT>
5696 <DD> Selects messages based on their size being smaller than or larger
5697 than the size you specify.
5698 The size is the number of bytes.
5699 You may use the suffix "K" or "k" to mean 1,000 times
5701 For example, 7K is the same as 7000.
5702 The suffix "M" or "m" means 1,000,000 times the number,
5703 and the suffix "G" or "g" means 1,000,000,000 times.
5704 Use the "^W" command to toggle back and forth between Smaller
5708 <DT>select by Keyword</DT>
5709 <DD> Selects messages that either have or do not have
5710 (using the "! Not" command)
5711 a particular <A HREF="h_config_keywords">Keyword</A> set.
5712 One way to select a keyword is to use the "^T To List"
5713 command to select one from your list of keywords.
5715 <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.
5718 <DT>select by Rule</DT>
5719 <DD> Selects messages that either match or don't match
5720 (using the "! Not" command)
5721 one of the Rules you have defined.
5722 The most likely method of filling in the Rule is to use the
5723 "^T To List"
5724 command to select one of your Rules.
5725 All of the Rules you have defined will be in the list, including
5726 Rules for Searching, Indexcolors, Filtering, Roles, Score setting, and Other.
5727 They may not all make sense for this purpose, but they are all there for
5729 You might find it useful to define some rules solely for the purpose
5730 of being used by the Select command.
5731 There is a special category for such Rules. They are called Search Rules.
5733 Unfortunately, Alpine does not allow all possible Rules to be defined.
5734 For example, there is no logical OR operation.
5735 OR is accomplished in the Filter Rules or the other types of Rules by
5736 simply defining two rules, one that matches the first part of the OR
5737 and another that matches the second part.
5738 But you can't do that here, since you only have a single Rule to work with.
5739 Likewise, the order of Rules is usually important.
5740 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5741 a message, then that stops the search for a further match.
5742 This means that you may be confused if you try to use Select by Rule to
5743 check your Filter rules because the order is important when filtering but
5744 is not considered here.
5747 <DT>select by tHread</DT>
5748 <DD> Selects all of the messages in the current thread.
5752 After you have an initial selection, the next and subsequent selection
5753 commands modify the selection.
5754 The select command changes. It first gives
5755 you selection "alteration" options: "unselect All",
5756 "unselect Current",
5757 "Broaden selection" (implements a logical OR), and
5758 "Narrow selection" (implements a logical AND).
5759 After you choose either Broaden or Narrow, you then choose one of the
5760 selection criteria listed above (by Text or Number or ...).
5761 You may use select as many times as you wish to get the selected set right.
5764 The WhereIs command has a feature (Ctrl-X) to
5765 select all the messages that match the WhereIs search. WhereIs searches
5766 through just the text that appears on the MESSAGE INDEX screen.
5767 This method is often slower than using the select command itself, unless the
5768 line you are looking for is not too far away in the index.
5771 The availability of the aggregate operations commands is determined by the
5772 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
5773 Feature-List option in your Alpine
5774 configuration, which defaults to set.
5776 <A HREF="h_config_auto_zoom">"<!--#echo var="FEAT_auto-zoom-after-select"-->"</A>
5778 <A HREF="h_config_select_wo_confirm">"<!--#echo var="FEAT_select-without-confirm"-->"</A>
5779 affect the behavior of the Select command.
5782 <End of help on this topic>
5785 ======= h_select_rule =======
5788 <TITLE>Select: Rule</TITLE>
5791 <H1>Select: Rule</H1>
5793 You are selecting messages that either match or don't match
5794 one of the Rules you have defined.
5795 You may either type the nickname of the Rule at the prompt, or use the
5796 "^T To List"
5797 command to select one of your Rules.
5798 All of the Rules you have defined will be in the list, including
5799 Rules for Indexcolors, Filtering, Roles, Score setting, and Other.
5800 They may not all make sense for this purpose, but they are all there for
5802 Rules may be added by using the Setup/Rules screen off of the main Alpine
5805 Unfortunately, Alpine does not allow all possible Rules to be defined.
5806 For example, there is no logical OR operation.
5807 OR is accomplished in the Filter Rules or the other types of Rules by
5808 simply defining two rules, one that matches the first part of the OR
5809 and another that matches the second part.
5810 But you can't do that here, since you only have a single Rule to work with.
5811 Likewise, the order of Rules is usually important.
5812 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5813 a message, then that stops the search for a further match.
5814 This means that you may be confused if you try to use Select by Rule to
5815 check your Filter rules because the order is important when filtering but
5816 is not considered here.
5819 <End of help on this topic>
5822 ======= h_select_text =======
5825 <TITLE>Select: Text</TITLE>
5828 <H1>Select: Text</H1>
5830 You are selecting messages based on the contents of the message.
5831 This allows you to select a set of messages based on whether or not the
5832 message headers or message body contain specified text.
5833 You may look for text in the Subject, the From header,
5834 the To header, or the Cc header.
5835 You may also choose Recipient, which searches for the text in
5836 either the To or the Cc header;
5837 or Participant, which means either the To header, or the Cc header,
5839 Besides those specific header searches, you may also search the entire
5840 header and text of the message with "All Text", or just the
5841 body of the message with "Body".
5843 To search for the absence of text, first type the "! Not" command
5844 before typing the specific type of text search.
5845 For example, you could type "!" followed by "S" to
5846 search for all messages that do not contain a particular word in their
5849 If you choose a Subject search, you may use the subject from the current
5850 message by typing the "^X Cur Subject" command.
5851 You may then edit it further if you wish.
5852 For example, you might select the subject of a reply and edit the
5853 "Re: " off of the front of it in order to search for
5854 the original message being replied to.
5855 All of the other header searches allow you to use addresses from the
5856 headers of the current message if you want to.
5857 You may use the "^T Cur To", "^R Cur From", or
5858 "^W Cur Cc".
5859 In each case, if there is more than one address, only the first is offered.
5862 <End of help on this topic>
5865 ======= h_select_status =======
5868 <TITLE>Select: Status</TITLE>
5871 <H1>Select: Status</H1>
5873 You are selecting messages based on the status of the message.
5874 For example, whether or not the message has been marked Deleted or Important,
5875 or whether or not it has been Answered or is New.
5876 If you first type the "! Not" command, you will get the
5877 opposite: not Deleted, not Important, and so on.
5879 If you select Deleted messages, you will get all messages with their
5881 Likewise for Important messages, all messages that you have flagged as
5882 being Important with the
5883 <A HREF="h_common_flag">Flag</A> command.
5884 The "New" and "Answered" choices are a little bit odd
5885 because they try to match what you see on the screen by default.
5886 "New" is a shorthand for messages that are Unseen, Undeleted,
5888 If you have looked at the message, or deleted it, or answered it; then it
5889 is not considered "New ".
5890 "! New" is the opposite of "New".
5892 "Answered" is another one that is a little different.
5893 It means that the message has been Answered <EM>and</EM> is not deleted.
5894 And to make it even more confusing, "! Answered" is not
5895 the opposite of "Answered"!
5896 Instead, "! Answered" stands for messages that are
5897 both Unanswered <EM>and</EM> not deleted.
5899 (The New and Answered options may seem counter-intuitive.
5900 The reason it is done this way is
5901 because, by default, a Deleted message will show up with the "D"
5902 symbol in the MAIL INDEX screen even if it is New or Answered.
5903 The Delete symbol overrides the New and Answered symbols, because you
5904 usually don't care about the message anymore once you've deleted it.
5905 Similarly, you usually only care about whether a message is Answered or
5906 not if it is not Deleted.
5907 Once it is Deleted you've put it out of your mind.)
5909 The other two options were added later because the special nature of the
5910 New flag was not what was wanted by all users.
5911 New does match what you see in the index by default, but if you use
5912 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5913 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5914 be exactly what you expect.
5915 "Unseen" simply selects all unseen messages, whether or not
5916 they are deleted or answered, and
5917 "Recent" selects all of the messages that have been added to
5918 the folder since you started this Alpine session.
5919 (That's not technically quite true. If there are multiple mail clients
5920 reading an IMAP mailbox, each message will be marked as Recent in only
5921 one of the client's sessions.
5922 That behavior can be convenienent for some purposes, like filtering, but
5923 it isn't usually what you expect when selecting.)
5926 <End of help on this topic>
5929 ======= h_index_cmd_apply =======
5932 <TITLE>Apply Command</TITLE>
5935 <H1>Apply Command</H1>
5938 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->A<!--chtml endif-->)
5939 is the second step of most aggregate operations. Apply
5940 becomes active any time there is a defined set of selected messages. The
5941 following commands can be applied to a selected message set: delete,
5942 undelete, reply, forward,
5943 <!--chtml if pinemode="os_windows"-->
5947 print, take address, save, export, bounce, and flag.
5950 The behavior of some of these commands in an aggregate sense is not easy to
5951 explain. Try them out to see what they do.
5953 <A HREF="h_config_auto_unzoom">"<!--#echo var="FEAT_auto-unzoom-after-apply"-->"</A>
5954 affects the behavior of the Apply command, as does the feature
5955 <A HREF="h_config_auto_unselect">"<!--#echo var="FEAT_auto-unselect-after-apply"-->"</A>.
5958 <End of help on this topic>
5961 ======= h_index_cmd_zoom =======
5964 <TITLE>ZoomMode Command</TITLE>
5967 <H1>ZoomMode Command</H1>
5969 Another action you might want to take on a set of selected messages is to
5970 zoom in on them. Like apply, zoom only becomes active when messages have
5973 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->Z<!--chtml endif-->)
5974 is a toggle command that allows you to
5975 zoom-in (and only see the selected messages) and zoom-out (to see all
5976 messages in the folder). Neither apply nor zoom removes the markings that
5977 define the selected set; you need to use a select command in order
5981 <End of help on this topic>
5984 ======= h_index_collapse_expand =======
5987 <TITLE>Collapse/Expand Command</TITLE>
5990 <H1>Collapse/Expand Command</H1>
5992 The Collapse/Expand command is only available from the MESSAGE INDEX screen when
5993 the folder is sorted by either Threads or OrderedSubject, and the
5994 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
5995 is set to something other than "none".
5996 By default, this command collapses or expands the subthread that starts at
5997 the currently highlighted message, if any.
5998 If the subthread is already collapsed, then this command expands it.
5999 If the subthread is expanded, then this command collapses it.
6000 If there are no more messages below the current message in the
6001 thread tree (that is, there are no replies to the current message) then
6002 this command does nothing.
6005 The behavior of this command is affected by the option
6006 <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>.
6007 Normally, this command Collapses or Expands the subthread that
6008 starts at the currently highlighted message.
6009 If the above option is set, then this command Collapses or Expands the
6010 entire current thread instead of just the subthread.
6011 The current thread is simply the top-level thread that contains the
6015 <End of help on this topic>
6018 ======= h_index_cmd_sort =======
6021 <TITLE>Sort Command</TITLE>
6024 <H1>Sort Command</H1>
6026 In Alpine's generic configuration, messages are presented in the order in
6027 which they arrive. This default can be changed in the SETUP CONFIGURATION
6028 with the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
6029 You can also re-sort the folder on demand with the sort
6030 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
6032 Your sorting options are:
6035 <LI> <A HREF="h_index_sort_arrival">A</A>rrival
6036 <LI> <A HREF="h_index_sort_date">D</A>ate
6037 <LI> <A HREF="h_index_sort_subj">S</A>ubject
6038 <LI> <A HREF="h_index_sort_ordsubj">O</A>rderedSubject
6039 <LI> t<A HREF="h_index_sort_thread">H</A>read
6040 <LI> <A HREF="h_index_sort_from">F</A>rom
6041 <LI> si<A HREF="h_index_sort_size">Z</A>e
6042 <LI> scor<A HREF="h_index_sort_score">E</A>,
6043 <LI> <A HREF="h_index_sort_to">T</A>o
6044 <LI> <A HREF="h_index_sort_cc">C</A>c
6048 The Reverse option will toggle the order the index is currently
6049 sorted by, but will not change the relative sort order.
6052 Sorting a folder does not actually rearrange the way the folder is saved,
6053 it just re-arranges how the messages are presented to you. This means
6054 that Alpine has to do the work of sorting every time you change sort order.
6055 Sometimes, especially with PC-Alpine or with large folders, this could take
6059 <End of help on this topic>
6062 ======= h_index_sort_default =======
6065 <TITLE>SORT OPTION: Default</TITLE>
6068 <H1>SORT OPTION: Default</H1>
6070 The <EM>Default</EM> sort option just means to use the default sort order
6072 <li><a href="h_config_sort_key"><!--#echo var="VAR_sort-key"--></a>
6073 option in Setup/Config.
6076 <End of help on this topic>
6079 ======= h_index_sort_arrival =======
6082 <TITLE>SORT OPTION: Arrival</TITLE>
6085 <H1>SORT OPTION: Arrival</H1>
6087 The <EM>Arrival</EM> sort option arranges messages in the MESSAGE INDEX
6088 in the order that they exist in the folder. This is usually the same as the
6089 order in which they arrived. This option is comparable to not sorting
6090 the messages at all.
6093 <End of help on this topic>
6096 ======= h_index_sort_date =======
6099 <TITLE>SORT OPTION: Date</TITLE>
6102 <H1>SORT OPTION: Date</H1>
6104 The <EM>Date</EM> sort option arranges messages in the MESSAGE INDEX
6105 according to the date and time they were
6109 On a folder like INBOX, sorting by "Date" should be almost
6110 identical to sorting by "Arrival".
6113 <End of help on this topic>
6116 ======= h_index_sort_subj =======
6119 <TITLE>SORT OPTION: Subject</TITLE>
6122 <H1>SORT OPTION: Subject</H1>
6124 The <EM>Subject</EM> sort option arranges messages in the MESSAGE INDEX
6128 Messages with the same subject are
6129 first grouped together, and then the groups of like-subject messages
6130 are arranged alphabetically.
6133 Alpine ignores leading "Re:" and
6134 "re:" and trailing "(fwd)" when determining the
6135 likeness and alphabetical order of subject lines.
6138 <End of help on this topic>
6141 ======= h_index_sort_ordsubj =======
6144 <TITLE>SORT OPTION: OrderedSubject</TITLE>
6147 <H1>SORT OPTION: OrderedSubject</H1>
6149 The <EM>OrderedSubject</EM> sort option arranges messages in the
6150 MESSAGE INDEX by grouping all messages with the same subject
6151 together, similar to sort by <A HREF="h_index_sort_subj">S</A>ubject.
6154 However, <EM>OrderedSubj</EM> then arranges the groups of like-subject
6155 messages by the date of the oldest message in the group.
6158 This sort method provides for pseudo threading of conversations within
6160 You may want to try sorting by Thread instead.
6163 <End of help on this topic>
6166 ======= h_index_sort_thread =======
6169 <TITLE>SORT OPTION: Thread</TITLE>
6172 <H1>SORT OPTION: Thread</H1>
6174 The <EM>Thread</EM> sort option arranges messages in the
6175 MESSAGE INDEX by grouping all messages that indicate
6176 they are part of a conversation (discussion thread) taking
6177 place within a mailbox or newsgroup. This indication is
6178 based on information in the message's header -- specifically
6179 its <tt>References:</tt>, <tt>Message-ID:</tt>, and <tt>Subject:</tt> fields.
6182 <End of help on this topic>
6185 ======= h_index_sort_from =======
6188 <TITLE>SORT OPTION: From</TITLE>
6191 <H1>SORT OPTION: From</H1>
6193 The <EM>From</EM> sort option arranges messages in the MESSAGE INDEX
6194 by the name of the author of the message.
6197 Messages with the same author are grouped together. Groups of
6198 messages are then put into alphabetical order according to message
6202 <End of help on this topic>
6205 ======= h_index_sort_size =======
6208 <TITLE>SORT OPTION: Size</TITLE>
6211 <H1>SORT OPTION: Size</H1>
6213 The <EM>Size</EM> sort option arranges messages in the MESSAGE INDEX
6214 by their relative sizes.
6217 <End of help on this topic>
6220 ======= h_index_sort_score =======
6223 <TITLE>SORT OPTION: Score</TITLE>
6226 <H1>SORT OPTION: Score</H1>
6228 The <EM>Score</EM> sort option arranges messages in the MESSAGE INDEX
6232 Messages with the same score are sorted in arrival order.
6233 Scores are something you create using the
6234 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
6237 <End of help on this topic>
6240 ======= h_index_sort_to =======
6243 <TITLE>SORT OPTION: To</TITLE>
6246 <H1>SORT OPTION: To</H1>
6248 The <EM>To</EM> sort option arranges messages in the MESSAGE INDEX
6249 by the names of the recipients of the message.
6252 Messages with the same recipients are grouped together. Groups of
6253 messages are then put into alphabetical order according to message
6257 <End of help on this topic>
6260 ======= h_index_sort_cc =======
6263 <TITLE>SORT OPTION: Cc</TITLE>
6266 <H1>SORT OPTION: Cc</H1>
6268 The <EM>Cc</EM> sort option arranges messages in the MESSAGE INDEX by
6269 the names of the carbon copy addresses of the message.
6272 <End of help on this topic>
6275 ======= h_index_cmd_whereis =======
6278 <TITLE>WhereIs Command</TITLE>
6281 <H1>WhereIs Command</H1>
6284 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
6285 command lets you search the MESSAGE INDEX for a word.
6286 It scans through whatever you see, usually the name of the author
6287 and the Subject line.
6288 WhereIs has special subcommands to let you find the beginning of the
6289 index (Ctrl-Y -- first message)
6290 or the end of the index (Ctrl-V -- last message).
6292 Note that WhereIs only searches through the visible text on the screen.
6293 For example, if only part of the Subject of a message is shown because it
6294 is long, then only the visible portion of the Subject is searched.
6295 Also note that WhereIs does not "see" the
6296 "X" in column one of Index entries for selected messages
6297 so it can't be used to search for
6298 selected messages (use "Zoom" instead).
6301 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
6303 WhereIs can also be used as a quick way to select messages that match the
6304 string being searched for.
6305 Instead of typing carriage return to search for the next match, type
6306 Ctrl-X to select all matches.
6307 Once again, this only selects matches that are (or would be if the right
6308 index line was on the screen) visible.
6309 Truncated From lines or Subjects will cause matches to be missed.
6310 Although WhereIs is sometimes convenient for quick matching, the Select
6311 command is usually more powerful and usually faster.
6314 <End of help on this topic>
6317 ======= h_view_cmd_whereis =======
6320 <TITLE>WhereIs Command</TITLE>
6323 <H1>WhereIs Command</H1>
6326 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
6327 command does a "find in current message" operation. You
6328 type in text and Alpine will try to find it in the message you are
6329 reading. WhereIs also has subcommands to jump to the beginning (Ctrl-Y)
6330 or end (Ctrl-V) of the message.
6331 That is, to rapidly move to the end of a message, hit the
6332 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
6333 (or Ctrl-W) key followed
6334 by Ctrl-V. Similarly,
6335 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
6336 followed by Ctrl-Y will take you to the beginning of a message.
6339 <End of help on this topic>
6342 ======= h_view_cmd_hilite =======
6345 <TITLE>View Hilite and Next item/Previous item</TITLE>
6348 <H1>View Hilite and Next item/Previous item</H1>
6350 Sometimes messages may be in the form of formatted HTML text
6351 or they may contain URLs or Web server hostnames.
6352 When any of the features
6353 <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>,
6354 <A HREF="h_config_enable_view_web_host">"<!--#echo var="FEAT_enable-msg-view-web-hostnames"-->"</A>,
6355 <A HREF="h_config_enable_view_attach">"<!--#echo var="FEAT_enable-msg-view-attachments"-->"</A>,
6357 <A HREF="h_config_enable_view_addresses">"<!--#echo var="FEAT_enable-msg-view-addresses"-->"</A>
6358 are enabled, Alpine will represent such selectable items in the text
6359 in bold typeface. One of the selectable items will be displayed in
6360 inverse video (highlighted). This is the "currently selected" item.
6361 Press the Return key to view the currently selected item.
6364 The Up and Down Arrows keys can be used to change the selected item
6365 (also see the feature
6366 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
6367 If there are no selectable items in the direction of the arrow you
6368 pressed, Alpine will scroll the display in that direction until one
6369 becomes visible. To "jump" forwards/backwards among selectable
6370 items in the message text, use the Previous and Next item commands,
6371 <!--chtml if pinemode="function_key"-->F5 and F6
6372 <!--chtml else-->^B and ^F<!--chtml endif-->.
6375 <End of help on this topic>
6378 ======= h_view_cmd_viewattch =======
6381 <TITLE>ViewAttch Command</TITLE>
6384 <H1>ViewAttch Command</H1>
6387 The View/Save Attachment
6388 (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->V<!--chtml endif-->)
6389 command allows you to handle MIME attachments to a message you have
6390 received. Alpine shows you a list of the message attachments -- you just
6391 choose the attachment you want. You may either view or save the
6392 selected attachment.
6395 Because many attachments require external programs for display, there
6396 is some system configuration that has to happen before you can
6397 actually display attachments. Hopefully much of that will have been
6398 done already by your system administrator. MIME configuration is
6399 handled with the "mailcap" configuration file. (See the section
6400 on configuration in the
6401 <A HREF="h_news">release notes</A> for more information.)
6404 <End of help on this topic>
6407 ======= h_index_cmd_expunge =======
6410 <TITLE>Expunge/Exclude Command</TITLE>
6413 <H1>Expunge/Exclude Command</H1>
6416 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->X<!--chtml endif-->)
6417 is the command Alpine uses to actually remove all messages
6418 marked for deletion. With regular email files, expunge literally deletes
6419 the text from the current folder. With newsgroups or shared mailboxes,
6420 you don't have permission to actually remove the message, so it is an
6421 exclude -- Alpine removes the message from your view of the folder even
6422 though it is not technically gone.
6424 <P> A selective expunge command is available in IMAP folders that support
6425 the UID EXPUNGE extension in <A
6426 HREF="http://tools.ietf.org/html/rfc4315">RFC 4315</A> as well as for all
6427 other folders (local folders in all formats, POP3 inbox, and newsgroups)
6428 as a subcommand of the apply command. If some selected messages are marked
6429 deleted, then the apply command will offer the eXpunge command, which when
6430 executed will only expunge those messages that are selected and deleted.
6433 Observe that the expunge command (when not used from the apply command)
6434 will expunge/exclude all deleted messages from the folder, and so all
6435 messages marked deleted will be expunged, regardless of if they are
6436 selected or not. In other words, there is no protection against
6437 potentially expunging more messages than only those that have been
6438 selected and deleted.
6441 The configuration features
6442 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
6444 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>
6445 affect the behavior of the Expunge command.
6448 <End of help on this topic>
6451 ======= h_common_compose =======
6454 <TITLE>Compose Command</TITLE>
6457 <H1>Compose Command</H1>
6459 The Compose command takes you into the Alpine message composer where you
6460 can start a new message for sending. This is where you type in the
6461 message's text and specify its recipient list (the "To:"
6462 address), where copies should be directed (e.g., "Fcc",
6463 "Cc:" or "Bcc:"), and which files, if any, should
6464 be attached to the message.
6467 When you type this command, Alpine will also automatically check for any
6468 interrupted (i.e., a message that was being composed when your modem
6469 or network connection was broken) or previously postponed messages and
6470 offer you a chance to continue working on those.
6474 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6476 <End of help on this topic>
6479 ======= h_common_index =======
6482 <TITLE>Message Index Command</TITLE>
6485 <H1>Message Index Command</H1>
6487 The Index command takes you to the MESSAGE INDEX screen that displays a
6488 summary caption for each message in the currently-open folder. One
6489 message will be highlighted; this is the "Current" message.
6490 The message commands available from this screen (e.g. View, Reply,
6491 Forward, Delete, Print, Save, etc) apply to the current message.
6494 <End of help on this topic>
6497 ======= h_common_folders =======
6500 <TITLE>Folder List Command</TITLE>
6503 <H1>Folder List Command</H1>
6505 This Folder List command takes you to the FOLDER LIST screen that displays
6506 the names of all your message folders and allows you to view, rename,
6507 delete, and add folders. You can open (view) a different folder than the
6508 one currently open by highlighting the desired one (using the arrow keys
6509 or their control-key equivalents) and pressing RETURN.
6512 If you have multiple folder collections defined (see the Help text for
6513 the FOLDER LIST screen to learn more about Collections), you may need
6514 to press Return to expand the collection and display all of the
6518 <End of help on this topic>
6521 ======= h_main_addrbook =======
6524 <TITLE>Address Book Command</TITLE>
6527 <H1>Address Book Command</H1>
6529 This command, available only from the MAIN MENU, takes you
6530 to the ADDRESS BOOK management screen. From here, your personal address
6531 book(s) may be updated.
6534 <End of help on this topic>
6537 ======= h_main_setup =======
6540 <TITLE>Setup Command</TITLE>
6543 <H1>Setup Command</H1>
6545 The Setup command, available only from the MAIN MENU, prompts you for
6546 one of several configuration screens, including the SETUP CONFIGURATION
6547 screen, by which you may activate optional Alpine features.
6550 <End of help on this topic>
6553 ======= h_main_release_notes =======
6556 <TITLE>Release Notes Command</TITLE>
6559 <H1>Release Notes Command</H1>
6561 This command displays information about Alpine <!--#echo var="ALPINE_VERSION"-->,
6562 as well as pointers to further information such as history and legal notes.
6565 <End of help on this topic>
6568 ======= h_main_kblock =======
6571 <TITLE>Keyboard Lock Command</TITLE>
6574 <H1>Keyboard Lock Command</H1>
6576 This command allows your Alpine session to be protected
6577 during a temporary absence from your terminal.
6580 <End of help on this topic>
6583 ======= h_main_journal =======
6586 <TITLE>Journal Command</TITLE>
6589 <H1>Journal Command</H1>
6591 This command displays a list of all the status messages Alpine has
6592 displayed (on the third line from the bottom of the screen). This may
6593 be useful if a message disappeared before you had a chance to read it.
6596 <End of help on this topic>
6599 ======= h_common_role =======
6602 <TITLE>Role Command</TITLE>
6605 <H1>Role Command</H1>
6607 The Role command is similar to the Compose command except that it starts
6608 off by letting you select a <A HREF="h_rules_roles">role</A>
6609 to be used for the composition.
6610 You may set up alternate roles by using Setup/Rules/Roles.
6613 <End of help on this topic>
6616 ======= h_common_conditional_cmds =======
6619 <TITLE>Conditional Commands</TITLE>
6622 <H1>Conditional Commands</H1>
6624 The presence or absence of certain commands, particularly in the
6625 MESSAGE INDEX and MESSAGE TEXT screens, is determined by
6626 whether or not specific features are set in your Alpine configuration.
6627 (You can access the SETUP CONFIGURATION screen, where they are found, from
6628 Alpine's MAIN MENU.) To see if a desired command's availability is
6629 conditioned on a feature setting, see the command's help text (highlight
6630 the phrase associated with the command and hit Return).
6634 commands may be administratively disabled by your system manager;
6635 if they don't work, please check with your local help desk.
6639 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6641 <End of help on this topic>
6644 ======= h_common_pipe =======
6647 <TITLE>Pipe Command</TITLE>
6650 <H1>Pipe Command</H1>
6653 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->|<!--chtml endif-->)
6654 allows you to send a message to a specified Unix command for external
6656 This command's availability is controlled by the
6657 <A HREF="h_config_enable_pipe">"<!--#echo var="FEAT_enable-unix-pipe-cmd"-->"</A>
6659 By default, the processed text of the message is sent to the command
6660 you specify and the output is captured by Alpine and shown to you.
6661 When you run the pipe command, there are some sub-commands which may be
6662 used to alter this behavior.
6663 These sub-commands are described <A HREF="h_pipe_command">here</A>.
6666 <End of help on this topic>
6669 ======= h_common_goto =======
6672 <TITLE>Goto Command</TITLE>
6675 <H1>Goto Command</H1>
6678 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->G<!--chtml endif-->)
6679 is the command that lets you bypass Alpine's folder selection screens
6680 and jump directly to a new folder. You can select any folder in the
6681 world: one in your current collection, one in a different collection or
6682 one in a collection you've never even used before.
6685 Alpine will help you as much as possible to narrow in on the folder you want.
6686 However, if the folder is outside of your defined collections, you are
6687 going to have to enter the exact folder location using the correct
6688 <A HREF="h_valid_folder_names">syntax</A>
6689 for a remote folder and/or fully-qualified path name.
6692 <End of help on this topic>
6695 ======= h_common_nextnew =======
6698 <TITLE>NextNew Command</TITLE>
6701 <H1>NextNew Command</H1>
6703 When you press the TAB key, Alpine advances to the next
6704 "interesting" message.
6705 This will be the next message you have not seen before, or the next message
6706 you have flagged Important, whichever comes first.
6707 Unread messages that have been deleted are not considered interesting.
6708 (A note about reading news. Alpine expects you to "Delete" news
6709 articles after you have read them if you want to remove them from future
6710 consideration. See <A HREF="h_mainhelp_readingnews">Reading News</A> for
6714 The NextNew command is affected by the feature
6715 <A HREF="h_config_tab_new_only">"<!--#echo var="FEAT_tab-visits-next-new-message-only"-->"</A>,
6716 which causes Alpine to only consider Unread messages interesting, not messages
6720 This command behaves a little differently when it finds there are no more
6721 interesting messages left in the current folder.
6722 If the current folder is one of your Incoming Message Folders
6723 (<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>)
6724 or it is a newsgroup, then Alpine will try to find the next folder or
6725 newsgroup that contains <EM>Recent</EM> messages and will ask you
6726 if you want to open that folder.
6727 This behavior may be modified by using the
6728 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
6729 feature that causes Alpine to look for Unseen messages instead of Recent
6731 The NextNew command's behavior is also affected by the configuration features
6732 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A>,
6734 <A HREF="h_config_tab_no_prompt">"<!--#echo var="FEAT_continue-tab-without-confirm"-->"</A>.
6737 <End of help on this topic>
6740 ======= h_common_jump =======
6743 <TITLE>Jump Command</TITLE>
6746 <H1>Jump Command</H1>
6748 This is Alpine's way of allowing you to go straight to a specific message.
6749 Just press "J" and then enter the message number. By default, Alpine is also
6750 configured such that typing in any number automatically jumps you to that
6752 (<A HREF="h_config_enable_jump">"<!--#echo var="FEAT_enable-jump-shortcut"-->"</A>
6753 in the SETUP CONFIGURATION).
6756 <End of help on this topic>
6759 ======= h_common_flag =======
6762 <TITLE>Flag Command</TITLE>
6765 <H1>Flag Command</H1>
6768 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6769 is the command that allows users to manipulate the status flags that
6770 appear on the left side of the MESSAGE INDEX screen. The most common
6771 use of this is to mark a message as important. This is something of a
6772 note to yourself to get back to that message. You may also use the
6773 flag command to set (or unset) the flags that indicate that a message
6774 is new, answered, deleted, or forwarded.<P>
6776 Provided the mail server supports it,
6777 you may also manipulate user-defined keywords
6778 for a message using the flag command.
6779 These keywords will be available if you use the Flag Details screen that you
6780 can get to after typing the
6781 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6783 They will be listed after the Important, New, Answered, Deleted , and Forwarded flags,
6784 which are always present.
6785 You may add new keywords by using the Add KW command from the Flag Details screen
6786 or by defining them in the <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
6788 The availability of the flag command is determined by the
6789 <A HREF="h_config_enable_flag">"<!--#echo var="FEAT_enable-flag-cmd"-->"</A>
6790 feature in your Alpine configuration. Also, it is possible that Flag could be
6791 administratively disabled by your system manager; if it doesn't work,
6792 please check with your local help desk before reporting a bug.
6793 The behavior of the flag command may be modified by the
6794 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
6795 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
6798 <End of help on this topic>
6801 ======= h_common_hdrmode =======
6804 <TITLE>HdrMode Command</TITLE>
6807 <H1>HdrMode Command</H1>
6809 Every email message comes with some header lines that you normally
6810 don't see (and don't want to see).
6811 These include anywhere from 3-20 lines (or more) added by the
6812 Internet mail transport system to record the route your message took,
6813 for diagnostic purposes.
6814 These are normally of no import and simply
6815 add clutter, so Alpine suppresses them in the MESSAGE TEXT display.
6816 This also includes other non-standard headers the message may contain.
6817 If you want to see these headers, there is a way to reveal them.
6821 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6822 command is a toggle that controls Alpine's handling of these header
6823 lines. Normally, full headers is "off" and you only see a
6824 few lines about who a message is to and who it is from. When you
6826 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6827 to turn full headers on, Alpine will show you
6828 the normal header lines as well as delivery headers, comment headers,
6829 MIME headers, and any other headers present.
6832 Several different Alpine commands honor the header mode -- it affects how
6833 messages are displayed, how they appear in forward and reply email, how
6834 they are printed, how they are saved, and how they are exported.
6835 <!--chtml if pinemode="os_windows"-->
6837 The pipe command is also affected.
6841 The presence or absence of the Header Mode command is determined by the
6842 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
6843 Feature-List option in your Alpine configuration.
6846 If you have also turned on the
6847 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
6848 option then the HdrMode command actually rotates through three states
6849 instead of just two.
6850 The first is the normal view with long quotes suppressed.
6851 The second is the normal view but with the long quotes included.
6852 The last enables the display of all headers in the message.
6853 When using Export, Pipe, Print, Forward, or Reply the quotes are
6854 never suppressed, so the first two states are identical.
6857 The behavior of the Header Mode command may be altered slightly by
6859 <A HREF="h_config_quell_full_hdr_reset">"<!--#echo var="FEAT_quell-full-header-auto-reset"-->"</A>
6860 Feature-List option in your Alpine configuration.
6861 In particular, it will cause the Header Mode to be persistent when moving
6862 from message to message instead of resetting to the default for each message.
6866 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6868 <End of help on this topic>
6871 ======= h_common_print =======
6874 <TITLE>Print Command</TITLE>
6877 <H1>Print Command</H1>
6880 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->%<!--chtml endif-->)
6881 command allows you to print a copy of a message.
6882 There are many SETUP CONFIGURATION features that affect the
6883 Print command, including
6884 <A HREF="h_config_enable_y_print">"<!--#echo var="FEAT_enable-print-via-y-command"-->"</A>,
6885 <A HREF="h_config_print_index">"<!--#echo var="FEAT_print-index-enabled"-->"</A>,
6886 <A HREF="h_config_custom_print">"<!--#echo var="FEAT_print-offers-custom-cmd-prompt"-->"</A>,
6887 <A HREF="h_config_print_from">"<!--#echo var="FEAT_print-includes-from-line"-->"</A>, and
6888 <A HREF="h_config_ff_between_msgs">"<!--#echo var="FEAT_print-formfeed-between-messages"-->"</A>.
6889 You set up for printing by using the Printer option of the Setup command
6894 <End of help on this topic>
6897 ======= h_common_take =======
6900 <TITLE>TakeAddr Command</TITLE>
6903 <H1>TakeAddr Command</H1>
6906 With the Take Address
6907 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->T<!--chtml endif-->)
6908 command, you can extract email addresses from an
6909 incoming message and save them in an address book. This is an easy way
6910 to add to your address book and avoid having to remember the email
6911 addresses of the people who write to you.
6914 If the message is just to you individually, then you will only need to
6915 provide a nickname. If the message contains more than one email address,
6916 then you will see an address
6917 selection screen that lets you choose the address you want to save into
6918 your address book, or lets you choose several of them add to a
6919 personal distribution list.
6922 Once you've added an entry to your address book, you can use it from the
6923 message composer by typing the nickname of the entry into one of the
6924 header fields (for example, into the To: field), or you can use ^T from
6925 the header field to select the entry from your address book.
6928 If the configuration feature
6929 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
6930 is set, the behavior of the Take command is altered slightly.
6933 <End of help on this topic>
6936 ======= h_ge_import =======
6939 <TITLE>Import File Selection</TITLE>
6942 <H1>Import File Selection</H1>
6944 You are importing a file that you previously
6945 exported from Alpine.
6946 You are now being asked for the name of that file.
6947 The easiest way to select a file is probably with the "^T"
6948 "To Files" command.
6949 Alternatively, you may type in a file name.
6950 It may be an absolute pathname.
6951 Otherwise, it is a file located in your home directory
6952 or current working directory
6953 <!--chtml if pinemode="running"-->
6954 (which, at least for your current Alpine "session,"
6955 is "<!--#echo var="CURRENT_DIR"-->")
6956 <!--chtml endif-->, depending on the
6957 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6958 In any case, you finish by typing a carriage return to accept the
6959 file name that is displayed.
6961 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6962 is turned on you may use TAB to complete partially typed in names.
6964 You may cancel the import operation by typing "^C" after exiting
6967 <End of help on this topic>
6970 ======= h_ge_allparts =======
6973 <TITLE>Export Message File Selection</TITLE>
6976 <H1>Export Message File Selection</H1>
6978 You are Exporting a message from an Alpine mail folder
6979 to a plain text file.
6980 You also have the option of exporting all of the attachments associated
6982 You are now being asked for the name of the file to export <EM>to</EM>.
6983 The easiest way to select a file is probably with the "^T"
6984 "To Files" subcommand.
6985 After returning from that subcommand you will still be allowed to
6986 edit the name you have selected.
6987 Alternatively, you may type in a file name.
6988 It may be an absolute pathname.
6989 Otherwise, it is a file located in your home directory
6990 or current working directory
6991 <!--chtml if pinemode="running"-->
6992 (which, at least for your current Alpine "session,"
6993 is "<!--#echo var="CURRENT_DIR"-->")
6994 <!--chtml endif-->, depending on the
6995 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6996 In any case, you finish by typing a carriage return to accept the
6997 file name that is displayed.
6999 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
7000 is turned on you may use TAB to complete partially typed in names.
7002 The message you are exporting appears to have some attachments.
7003 If you wish to save <EM>all</EM> of the attachments at once,
7004 type the "^P" "AllParts" command to turn on
7005 saving of the attachments.
7006 You may turn it back off by typing "^P" again, which will now
7007 be labeled "NoAllParts" instead.
7008 If you want to save the parts the command displayed should be
7009 "NoAllParts"!
7010 When you choose to save attachments like this, the attachments will be saved
7011 in a newly created directory.
7012 That directory will have the same name as the file name you choose here,
7013 with the letters ".d" appended.
7014 If that directory already exists, then the letters ".d_1" will
7015 be tried, then ".d_2" and so on until a name that doesn't exist
7017 For example, if you select the file name
7019 <CENTER><SAMP>filename</SAMP></CENTER>
7021 to export the message to, then the directory used for the attachments will be
7023 <CENTER><SAMP>filename.d</SAMP></CENTER>
7027 <CENTER><SAMP>filename.d_<n></SAMP></CENTER>
7029 The attachments will then be put into files inside that directory.
7030 The names for the attachment files will be derived from the attachments
7032 This is done in the same way as the default values are derived if you
7033 save them one at a time.
7034 (The "filename" parameter from the Content-Disposition header
7035 is the first choice. If that doesn't exist, the "name"
7036 parameter from the Content-Type header is used.)
7037 If a name for a particular attachment is not available, then the
7038 part number of the attachment is used, with the characters "part_"
7040 An example of that would be
7042 <CENTER><SAMP>part_2.1</SAMP></CENTER>
7044 If you want to save only some of the attachments or if you want more control
7045 over the directory and filename where an attachment is saved you may
7046 cancel out of this command and View the attachment list.
7047 From there you can save each attachment individually.
7049 You may cancel the Export operation by typing "^C" after exiting
7052 <End of help on this topic>
7055 ======= h_ge_export =======
7058 <TITLE>Export File Selection</TITLE>
7061 <H1>Export File Selection</H1>
7063 You are Exporting or Saving something from within the Alpine world
7064 (a message, an attachment, etc.)
7065 to a plain text file.
7066 You are now being asked for the name of the file to export <EM>to</EM>.
7067 The easiest way to select a file is probably with the "^T"
7068 "To Files" subcommand.
7069 After returning from that subcommand you will still be allowed to
7070 edit the name you have selected.
7071 Alternatively, you may type in a file name.
7072 It may be an absolute pathname.
7073 Otherwise, it is a file located in your home directory
7074 or current working directory
7075 <!--chtml if pinemode="running"-->
7076 (which, at least for your current Alpine "session,"
7077 is "<!--#echo var="CURRENT_DIR"-->")
7078 <!--chtml endif-->, depending on the
7079 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
7080 In any case, you finish by typing a carriage return to accept the
7081 file name that is displayed.
7083 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
7084 is turned on you may use TAB to complete partially typed in names.
7086 If the object you are exporting is a message with some attachments,
7087 you may wish to save all of the attachments by typing the "^P"
7088 "AllParts" command to turn on saving of the attachments.
7089 This subcommand will only be visible if the message actually has attachments.
7090 You may also View the attachment list and save individual attachments from
7093 If you are SAVING a text part (text/plain, text/html, etc.) you can use
7094 the Control-R subcommand to toggle if saving will be done in binary mode,
7095 meaning that the attachment will be decoded, but will not be transformed
7096 to UTF-8 for further processing (either in internal filters, or user
7097 supplied filters.) This is useful in case you either want to preserve
7098 the text as it was encoded originally to you, or the attachment was
7099 incorrectly attached (the attachment is not of text type) and you need
7100 the original text to process the attachment.
7102 You may cancel the Export operation by typing "^C" after exiting
7105 <End of help on this topic>
7108 ======= h_common_save =======
7111 <TITLE>Save and Export Commands</TITLE>
7114 <H1>Save and Export Commands</H1>
7117 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->S<!--chtml endif-->)
7119 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->E<!--chtml endif-->)
7120 are the two alternatives Alpine gives you to keep a copy of the message
7121 you are reading. If you want to keep the message within Alpine's email
7122 world, use "Save"; if you want to use the message in another
7123 program, use "Export".
7126 When you Save a message, it is put into an existing folder or into a new
7127 folder in one of your existing folder collections. The message stays in
7128 email format and can be read by Alpine again. Alpine may use a special format
7129 for its mail folders -- never edit an Alpine folder by hand or with any
7130 program other than Alpine. The exact behavior of the Save command can be
7132 <A HREF="h_config_quote_all_froms">"<!--#echo var="FEAT_save-will-quote-leading-froms"-->"</A>,
7133 <A HREF="h_config_save_wont_delete">"<!--#echo var="FEAT_save-will-not-delete"-->"</A>,
7135 <A HREF="h_config_save_advances">"<!--#echo var="FEAT_save-will-advance"-->"</A>
7136 feature list settings.
7137 The name of the folder offered as a default is controlled by the option
7138 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>.
7141 When you use Export, the message is placed in a plain text file in your
7143 <!--chtml if pinemode="running"-->
7144 (which, in the present configuration of your system, is
7145 "<!--#echo var="HOME_DIR"-->")
7147 or current working directory
7148 <!--chtml if pinemode="running"-->
7149 (which, at least for your current Alpine "session,"
7150 is "<!--#echo var="CURRENT_DIR"-->")
7151 <!--chtml endif-->, depending on the
7152 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
7153 configuration setting. In the normal case, only minimal
7154 headers are exported with the message; however, if the full header mode
7155 (whose availability may be disabled by setting the feature
7156 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
7157 in SETUP CONFIGURATION) is
7158 toggled on, then complete headers are exported along with the message
7159 text. (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
7160 defined, they may affect the contents of the exported file.)
7163 <End of help on this topic>
7166 ======= h_common_bounce =======
7169 <TITLE>Bounce Command</TITLE>
7172 <H1>Bounce Command</H1>
7175 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->B<!--chtml endif-->)
7176 command allows you to re-send, or "remail", a
7177 message, as if you were never in the loop. It is analogous to crossing
7178 out your address on a postal letter, writing a different address on the
7179 envelope, and putting it into the mailbox. Bounce is used primarily to
7180 redirect email that was sent to you in error.
7181 Also, some owners of email
7182 lists need the bounce command to handle list traffic.
7183 Bounce is not anonymous.
7184 A ReSent-From header is added to the message so that the recipient may
7185 tell that you Bounced it to them.
7188 The presence or absence of the Bounce command is determined by the
7189 <A HREF="h_config_enable_bounce">"<!--#echo var="FEAT_enable-bounce-cmd"-->"</A>
7190 feature in your Alpine configuration.
7192 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A>
7193 affects the behavior of the Bounce command.
7194 Also, it is possible that Bounce could be
7195 administratively disabled by your system manager; if it doesn't work,
7196 please check with your local help desk before reporting a bug.
7199 <End of help on this topic>
7202 ======= h_common_reply =======
7205 <TITLE>Reply and Forward Commands</TITLE>
7209 <H1>Reply and Forward Commands</H1>
7212 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->R<!--chtml endif-->)
7214 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->F<!--chtml endif-->)
7215 are your two alternatives for following up on the
7216 message you are reading. You would use reply if you want to get email
7217 back to the author of the message and/or the other people who have
7218 already seen it. You use forward if you want somebody new to see the
7222 In the normal case, the only thing that you must supply when forwarding a
7223 message is the name/email address of the new recipient.
7224 Alpine will include the text of the forwarded message.
7225 Alpine will also include any attachments to the message.
7226 There is space above the forwarded text for you to include additional comments.
7229 When replying, you usually have to answer some questions.
7230 If the message is to multiple people and/or specified with a Reply-To: header,
7231 then you will have to decide who should get the reply.
7232 You also need to decide whether or not to include the previous
7233 message in your reply.
7234 Some of this is configurable.
7235 Specifically, see the
7236 <A HREF="h_config_include_header">"<!--#echo var="FEAT_include-header-in-reply"-->"</A>,
7237 <A HREF="h_config_auto_include_reply">"<!--#echo var="FEAT_include-text-in-reply"-->"</A>,
7238 <A HREF="h_config_attach_in_reply">"<!--#echo var="FEAT_include-attachments-in-reply"-->"</A>,
7240 <A HREF="h_config_auto_reply_to">"<!--#echo var="FEAT_reply-always-uses-reply-to"-->"</A>
7241 configuration features.
7244 Both the Reply and Forward commands react to the full header mode toggle.
7245 If the full header mode is on, then all the header and delivery lines are
7246 included with the text of the message in your reply/forward.
7249 Other configuration features that affect the Reply command are
7250 <A HREF="h_config_sig_at_bottom">"<!--#echo var="FEAT_signature-at-bottom"-->"</A>,
7251 <A HREF="h_config_sigdashes">"<!--#echo var="FEAT_enable-sigdashes"-->"</A>, and
7252 <A HREF="h_config_strip_sigdashes">"<!--#echo var="FEAT_strip-from-sigdashes-on-reply"-->"</A>.
7255 <End of help on this topic>
7258 ======= h_common_delete =======
7261 <TITLE>Delete and Undelete Commands</TITLE>
7264 <H1>Delete and Undelete Commands</H1>
7267 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->D<!--chtml endif-->)
7269 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->U<!--chtml endif-->)
7270 allow you to change the Deleted flag for the current message.
7271 Delete marks a message Deleted (turns on the Deleted flag) and Undelete
7273 In the MESSAGE INDEX, deleted messages have a "D" in the status field
7274 at the left hand edge of the index line.
7275 When viewing a deleted message, the letters "DEL" will be present
7276 in the upper right hand corner of the screen.
7277 Delete simply <EM>marks</EM> a message Deleted, it does not actually
7278 get rid of the message.
7279 The eXpunge command (available from the MESSAGE INDEX screen) actually
7280 removes all of the deleted messages in a folder.
7281 Once a message is eXpunged, it can't be retrieved.
7284 The Delete command is affected by the setting of the configuration feature
7285 <A HREF="h_config_del_skips_del">"<!--#echo var="FEAT_delete-skips-deleted"-->"</A>.
7288 <End of help on this topic>
7291 ======= h_common_postpone =======
7294 <TITLE>Postpone Command</TITLE>
7297 <H1>Postpone Command</H1>
7300 <!--chtml if pinemode="function_key"-->(F11)<!--chtml else-->(^O)<!--chtml endif-->
7301 command allows you to temporarily stop working on the current
7302 message so you may read
7303 other messages or compose another message. When you want to resume a
7304 message later, start to compose and answer "yes" to the
7305 "Continue postponed composition?" question. You may
7306 postpone as many messages as you like.
7309 Note: If a <A HREF="h_config_form_folder"><!--#echo var="VAR_form-letter-folder"--></A> is defined
7310 in the Setup/Config screen, then the Postpone command will prompt you for
7311 the folder in which to store your outgoing message.
7314 <End of help on this topic>
7317 ======= h_compose_cancel =======
7320 <TITLE>Cancel Command</TITLE>
7323 <H1>Cancel Command</H1>
7326 <!--chtml if pinemode="function_key"-->
7332 The Cancel command returns you to Alpine's normal mail processing and
7333 causes the message currently under composition to be thrown out.
7334 The message text <EM>will be lost</EM>.
7337 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
7338 will be preserved in the file named
7339 <!--chtml if pinemode="os_windows"-->
7340 "DEADLETR".
7342 "dead.letter" in your home directory.
7344 If you unintentionally cancel a message, look there for its text.
7347 <End of help on this topic>
7350 ======= h_compose_addrcomplete =======
7353 <TITLE>Address Completion</TITLE>
7356 <H1>Address Completion</H1>
7358 When entering addresses in the address fields of the composer (To, Cc, etc.)
7359 the TAB key may be used to help complete the address.
7360 Type a partial nickname and tap the TAB key to complete the typing.
7361 The unambiguous part of the name will be filled in automatically.
7362 Typing TAB twice in succession will bring up a selection list of possibilities,
7363 making it easy to find and choose the correct address.
7366 The matching algorithm is rather ad hoc.
7367 The search starts with a search of your address book.
7368 It counts as a match if the nickname, address, or fullname field of an
7369 entry begins with the text typed in so far. It is also a match if
7370 a later word in the fullname (for example, the middle name or last name)
7371 begins with the entered text.
7373 Next comes an LDAP search.
7374 The search will happen for any servers that have the
7375 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
7376 feature set. You can set or unset the feature for each server independently
7377 in the Setup/Directory screen.
7379 Finally, if you are replying to or forwarding a message, that message is
7380 searched for likely candidate addresses that match the typed-in text.
7383 <End of help on this topic>
7386 ======= h_compose_richhdr =======
7389 <TITLE>Rich Header Command</TITLE>
7392 <H1>Rich Header Command</H1>
7394 The Rich Header command allows you to toggle between the list of
7395 all message headers available for editing and those that are most
7399 Use this toggle to expose headers that are not normally visible by
7401 This set usually includes the
7405 and "Newsgroups"
7407 If you are posting to a newsgroup the set of defaults is a little different.
7408 Obviously, in that case, the Newsgroups header is of interest so is not
7410 For news posting the hidden set includes the
7415 and "Lcc:"
7417 You won't normally want to edit these, which is why they are hidden,
7418 but it is sometimes useful to be able to set them manually.
7421 The default sets of headers listed above can be altered.
7422 Any header that you have added to the
7423 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
7424 option, but not to the
7425 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
7426 option will appear when you use the Rich Headers command to
7427 make the Rich Headers visible.
7428 (Headers listed in the <!--#echo var="VAR_default-composer-hdrs"--> list will be visible
7429 even without toggling the Rich Headers command.)
7432 <End of help on this topic>
7435 ======= h_compose_send =======
7438 <TITLE>Send Command</TITLE>
7441 <H1>Send Command</H1>
7444 <!--chtml if pinemode="function_key"-->
7449 tells Alpine you are finished composing.
7450 Before actually sending it, though, Alpine will ask you to confirm
7451 your intention, and, at the same time, redisplayed the message text
7452 with the recipients at the top of the screen to give you the opportunity
7453 to review and verify that the message is addressed to the people
7457 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
7458 then this confirmation prompt and any options it allows are skipped.
7461 This confirmation prompt may also offer, depending
7462 on your particular Setup/Config, options allowing you to set
7463 <A HREF="h_config_compose_dsn">delivery status notifications</A>,
7464 include attachments in the "Fcc" (if you had previously
7465 specified that they <A HREF="h_config_no_fcc_attach">exclude attachments</A>,
7466 observe details of the
7467 <A HREF="h_config_verbose_post">message submission process</A>,
7468 choose the filter through which the
7469 <A HREF="h_config_sending_filter">outgoing text should first pass</A>,
7470 or turn of flowed text generation.
7473 <End of help on this topic>
7476 ======= h_compose_markcutpaste =======
7479 <TITLE>Mark, Cut and Paste Commands</TITLE>
7482 <H1>Mark, Cut and Paste Commands</H1>
7484 You can define a "block" of text, which can subsequently
7486 copied as a unit, by setting a mark at the start of the block (Ctrl-^) and
7487 then moving the cursor to the end of the desired text block. You can then
7488 "cut" the block out
7489 <!--chtml if pinemode="function_key"-->
7494 move the cursor, and "paste" it
7495 <!--chtml if pinemode="function_key"-->
7500 in the new location. Also, you can paste more than once, allowing you
7501 to use this feature to copy a block of text.<P>
7504 <!--chtml if pinemode="function_key"-->
7509 without having marked anything, Alpine will delete
7510 a single line. If you delete a group of lines together, Alpine keeps them
7511 in the same buffer, so
7512 <!--chtml if pinemode="function_key"-->
7517 will restore them as a block. About
7518 terminology: Mark is shown as "^^". The first "^" means you should
7519 hold down the "Control" key on your keyboard. The second "^" means
7520 "type the character ^".
7523 <End of help on this topic>
7526 ======= h_compose_justify =======
7529 <TITLE>Justify Command</TITLE>
7532 <H1>Justify Command</H1>
7535 <!--chtml if pinemode="function_key"-->
7540 command reformats the text in the paragraph the cursor is in.
7541 Paragraphs are separated by one blank line or a line beginning with a space.
7542 This is useful when you have been editing a paragraph and the lines become
7543 uneven. The text is left aligned or justified and the right is ragged. If
7544 the text is already justified as typed with auto-wrap, no justification will
7548 If you have set a <A HREF="h_compose_markcutpaste">mark</A> to select a
7549 block of text, the Justify command is modified.
7550 Instead of automatically justifying the current paragraph you will be
7551 asked if you want to justify the paragraph, justify the selected region,
7552 or adjust the quote level of the selected region.
7553 Adjusting the quote level only works if you are using standard
7554 "> " or ">" quotes, which is the default if you haven't
7555 changed "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>".
7558 When composing a reply containing included text, the justify command
7559 will reformat text to the right of the
7560 "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>",
7561 adding or removing indented lines as needed. Paragraphs are separated
7562 by a blank line, a line containing only the <!--#echo var="VAR_reply-indent-string"-->, or a
7563 line containing the indent string and one or more blank spaces.
7564 Included text that was previously indented (or "quoted") is
7568 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
7569 in 1999 and its wide-spread adoption since then, you will usually be better off if you
7571 "> " or ">" quotes.
7574 <End of help on this topic>
7577 ======= h_compose_spell =======
7580 <TITLE>Spell Check Command</TITLE>
7583 <H1>Spell Check Command</H1>
7585 The "To Spell"
7586 <!--chtml if pinemode="function_key"-->
7591 command calls an external spell checking program to look over the
7592 message you are composing. By default, Alpine uses
7594 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
7596 if it knows where to find "aspell".
7597 If there is no "aspell" command available but the command "ispell" is available
7598 then the command used is
7600 <CENTER><SAMP>ispell -l</SAMP></CENTER>
7602 Otherwise, the ancient "spell" command is used.
7604 For PC-Alpine, you must install the aspell library code that you
7606 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
7609 <End of help on this topic>
7612 ======= h_compose_alted =======
7615 <TITLE>Alt Editor Command</TITLE>
7618 <H1>Alt Editor Command</H1>
7620 The "Alt Editor" command's availability depends on the
7621 Setup/Config variable "<A HREF="h_config_editor"><!--#echo var="VAR_editor"--></A>".
7624 When the variable specifies a valid editor on your system, this
7625 command will launch it with the current text of your message
7629 <End of help on this topic>
7632 ======= h_compose_readfile =======
7635 <TITLE>Read File Command</TITLE>
7638 <H1>Read File Command</H1>
7640 The "Read File"
7641 <!--chtml if pinemode="function_key"-->
7646 command allows you to copy in text from an existing file. You will be
7647 prompted for the name of a file to be inserted into the message. The file
7648 name is relative to your home directory
7649 <!--chtml if pinemode="running"-->
7650 (which, in the present configuration of your system, is
7651 "<!--#echo var="HOME_DIR"-->")
7653 or current working directory
7654 <!--chtml if pinemode="running"-->
7655 (which, at least for your current Alpine "session,"
7656 is "<!--#echo var="CURRENT_DIR"-->")
7657 <!--chtml endif-->, depending on the
7658 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
7659 configuration setting; or, the file name must be specified as a full path name
7660 <!--chtml if pinemode="os_windows"-->
7661 -- for example: "A:\PAPER.TXT"
7663 -- for example: "/tmp/wisdom-of-the-day"
7665 (without the quotation marks).
7668 The file will be inserted where the cursor is located. <B>The
7669 file to be read must be on the same system as Alpine.</B> If you use Alpine on a
7670 Unix machine but have files on a PC or Mac, the files must be transferred
7671 to the system Alpine is running on before they can be read. Please ask your
7672 local computer support people about the correct way to transfer a file to
7676 <End of help on this topic>
7679 ======= h_config_tray_icon =======
7682 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></TITLE>
7685 <H1>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></H1>
7689 This option restores a behavior of previous versions of PC-Alpine.
7691 versions, when started, installed a PC-Alpine icon in the notification
7692 tray of Window's Taskbar. The primary use of this icon was to indicate
7693 new mail arrival by turning red (while the Taskbar icon remained green).
7694 Additionally, the icon now changes to yellow to signify that a mail folder
7695 has been closed unexpectedly.
7698 Rather than add another icon to the Taskbar, this version of PC-Alpine will
7699 color its Taskbar entry's icon red (as well as the icon in the Window
7700 Title). This feature is only provided for backwards compatibility.
7703 <End of help on this topic>
7706 ======= h_common_suspend =======
7709 <TITLE>Suspend Command</TITLE>
7712 <H1>Suspend Command</H1>
7714 With the <A HREF="h_config_can_suspend"><!--#echo var="FEAT_enable-suspend"--></A> feature
7715 enabled, you can, at almost any time, temporarily halt your Alpine session,
7716 <!--chtml if pinemode="os_windows"-->
7717 minimizing it into an icon.
7719 and return to your system prompt.
7723 <End of help on this topic>
7726 ======= h_pipe_command =======
7729 <TITLE>Pipe Command SubOptions</TITLE>
7732 <H1>Pipe Command SubOptions</H1>
7734 By default, when you use the Pipe command, the processed text of the
7735 message is sent to the Unix command
7736 you specify and the output is captured by Alpine and shown to you.
7737 (This command is available in PC-Alpine, as well, but there aren't many
7738 Windows commands that work well with piping.)
7739 There are some sub-commands that may be used to alter this behavior.
7740 These are toggles that switch the behavior between two possibilities.
7741 They can be combined in any way you wish.
7743 By default, the prompt at the bottom of the screen looks like
7745 <CENTER><SAMP>Pipe message 37 to :</SAMP></CENTER>
7749 <CENTER><SAMP>Pipe messages to :</SAMP></CENTER>
7751 if you are piping more than one message.
7753 The sub-command options are:
7755 <DT>Shown Text or Raw Text</DT>
7756 <DD>This option toggles between sending the shown (processed) text
7757 of the message to the Unix command, and sending the
7758 raw (unprocessed) text of the message to the Unix command.
7759 The default is to send the shown text.
7760 The raw version of the message will contain all of the headers and any
7761 MIME encoding that the message contains.
7762 If you've selected the Raw Text then the prompt will have the additional word
7763 "RAW" in it, like
7765 <CENTER><SAMP>Pipe RAW messages to :</SAMP></CENTER>
7767 You can experiment with this option by piping to something simple like the
7768 Unix "cat" command.
7770 <DT>Captured Output or Free Output</DT>
7771 <DD>This option toggles between having Alpine capture the output of
7772 the Unix pipe command for display, and not capturing it.
7773 If the command you are piping to is a filter that will produce output
7774 you want to view, then you want to capture that output
7775 for display (the default).
7776 If the Unix command doesn't produce output or handles the display itself,
7777 then you want free output.
7778 When you've selected the Free Output option the prompt will change to
7780 <CENTER><SAMP>Pipe messages to (uncaptured) :</SAMP></CENTER>
7783 <DT>No Delimiter or With Delimiter</DT>
7784 <DD>This option controls whether or not a Unix mailbox style delimiter
7785 will come before the text of the message.
7786 This is the delimiter used in the common Unix mailbox format.
7787 It's the single line that begins with the five characters
7788 "From" followed by a <SPACE> character.
7789 You'll usually only want to include this if the Unix command requires
7790 input in the format of a traditional Unix mailbox file.
7791 When you've selected the With Delimiter option the prompt will change to
7793 <CENTER><SAMP>Pipe messages to (delimited) :</SAMP></CENTER>
7796 <DT>To Same Pipe or To Individual Pipes</DT>
7797 <DD>This option only shows up if you are running an aggregate
7799 That is, the command was Apply Pipe, not just Pipe.
7800 You have the option of piping all of the selected messages through a
7801 single pipe to a single instance of the Unix command,
7802 or piping each individual message through a separate pipe to separate
7803 instances of the Unix command.
7804 The default is that all of the output will go through a single pipe
7805 to a single instance of the command.
7806 You can try this option with a command like "less", with Free
7808 When you've selected the Individual Pipes option the prompt will change to
7810 <CENTER><SAMP>Pipe messages to (new pipe) :</SAMP></CENTER>
7816 As mentioned earlier, the options can be combined in any way you wish.
7817 You may leave them all off, turn them all on, or turn some of them on
7818 and some of them off.
7819 If you use the pipe command a second time in the same session the default
7820 options will be what you used the last time.
7823 <End of help on this topic>
7826 ========== h_emptydir_subfolder_name =========
7829 <TITLE>ENTER SUBFOLDER NAME</TITLE>
7832 <H1>Enter Subfolder Name</H1>
7835 This is the name of a new subfolder in the directory you are creating.
7836 Because empty directories are hidden and therefore not useful, you must also
7837 create a subfolder in the directory you are creating in order that the
7838 directory remains visible.
7840 Alternatively, you may turn off the configuration feature
7841 <A HREF="h_config_quell_empty_dirs"><!--#echo var="FEAT_quell-empty-directories"--></A>
7842 so that empty directories remain visible.
7843 If you do that, you will not be required to create the subfolder when you
7847 <End of help on this topic>
7850 ========== h_incoming_add_folder_name =========
7853 <TITLE>ENTER FOLDER NAME</TITLE>
7856 <H1>Enter Folder Name</H1>
7859 This is the name of the folder on the previously specified server.
7860 By default the folder name is interpreted as defining a section of your personal
7861 folder area. This area and how you specify it are defined by the
7862 server, if one is specified.
7865 To define a folder outside the default area, prefix
7866 the path with the namespace to use when interpreting the
7867 given path. If a namespace is specified, the folder name begins with the
7868 sharp (#) character followed by the name of the namespace
7869 and then the namespace's path-element-delimiter. Aside from the
7870 name's format, namespaces can also imply access rights, content
7871 policy, audience, location, and, occasionally, access methods.
7874 Each server exports its own set (possibly of size one) of
7876 For a more detailed explanation read about
7877 <A HREF="h_folder_name_namespaces">Namespaces</A>.
7880 To specify the default for INBOX on the server you can usually just enter
7881 "INBOX", and the server will understand the special meaning of
7885 <End of help on this topic>
7888 ========== h_incoming_add_folder_host =========
7891 <TITLE>ENTER INCOMING FOLDER SERVER</TITLE>
7894 <H1>Enter Incoming Folder Server</H1>
7896 You are being asked for the name of the server for use with this incoming
7898 If the folder is on the machine where Alpine is running, then just enter
7899 RETURN without typing a server name.
7902 If the folder is on an IMAP server then type the server's name followed
7904 You may use the ^X command if the server is the same as the server that
7908 You may have to add optional extra information to the server name.
7909 For example, if the IMAP server is using a non-standard port number you
7910 would specify that by appending a colon (:) followed by the port number
7914 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7917 or you may need to specify a different protocol if the server is not an
7918 IMAP server. For example:
7921 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7927 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7930 for an NNTP news server.
7931 For an explanation of all of the possibilities, see
7932 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7936 There is a special command (^W) if you want to set up a folder that gets its
7938 <A HREF="h_maildrop">Mail Drop</A>.
7939 If you type that command, you will be prompted for the information for
7940 both the Mail Drop folder and the destination folder.
7943 <End of help on this topic>
7946 ========== h_incoming_add_inbox =========
7949 <TITLE>ENTER INBOX SERVER</TITLE>
7952 <H1>Enter INBOX Server</H1>
7954 You are being asked for the name of the server for use with
7956 Type the server's name followed by RETURN.
7959 You may have to add optional extra information to the server name.
7960 For example, if the server is using a non-standard port number you
7961 would specify that by appending a colon (:) followed by the port number
7965 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7968 or you may need to specify a different protocol if the server is not an
7969 IMAP server. For example:
7972 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7978 For an explanation of all of the possibilities, see
7979 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7983 If the INBOX folder is on the machine where Alpine is running, then just enter
7984 RETURN without typing a server name.
7987 There is a special command (^W) if you want to set up a folder that gets its
7989 <A HREF="h_maildrop">Mail Drop</A>.
7990 If you type that command, you will be prompted for the information for
7991 both the Mail Drop folder and the destination folder, which will be used
7992 as your INBOX folder.
7995 <End of help on this topic>
7998 ========== h_incoming_add_maildrop_destn =========
8001 <TITLE>ENTER DESTINATION SERVER</TITLE>
8004 <H1>Enter Destination Server</H1>
8006 You are being asked for the name of the server where the destination
8007 folder is for use with this Mail Drop incoming folder.
8008 That is, you are using a Mail Drop for this incoming folder and
8009 you've already entered
8010 the server and folder name for the Mail Drop.
8011 Now you need to enter the server for the destination folder
8012 where the mail should be copied to.
8013 Mail will come from the Mail Drop and be copied to the destination folder.
8016 Type the server's name followed by RETURN.
8017 If the folder is local to this computer, just type RETURN without entering
8021 You may have to add optional extra information to the server name.
8022 For example, if the server is using a non-standard port number you
8023 would specify that by appending a colon (:) followed by the port number
8027 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
8030 For an explanation of all of the possibilities, see
8031 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
8035 <End of help on this topic>
8038 ========== h_inbox_add_maildrop_destn =========
8041 <TITLE>ENTER DESTINATION SERVER</TITLE>
8044 <H1>Enter Destination Server</H1>
8046 You are being asked for the name of the server where the destination
8047 folder is for use with your Mail Drop INBOX.
8048 That is, you are using a Mail Drop for your INBOX and you've already entered
8049 the server and folder name for the Mail Drop.
8050 Now you need to enter the server for the destination folder
8051 where the mail should be copied to.
8052 Mail will come from the Mail Drop and be copied to the destination folder.
8055 Type the server's name followed by RETURN.
8056 If the folder is local to this computer, just type RETURN without entering
8060 You may have to add optional extra information to the server name.
8061 For example, if the server is using a non-standard port number you
8062 would specify that by appending a colon (:) followed by the port number
8066 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
8069 For an explanation of all of the possibilities, see
8070 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
8074 <End of help on this topic>
8077 ========== h_inbox_add_maildrop =========
8080 <TITLE>ENTER MAILDROP SERVER</TITLE>
8083 <H1>Enter Mail Drop Server</H1>
8085 You are being asked for the name of the Mail Drop server for use with
8089 Type the server's name followed by RETURN.
8092 You may have to add optional extra information to the server name.
8093 For example, if the server is using a non-standard port number you
8094 would specify that by appending a colon (:) followed by the port number
8098 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
8101 or you may need to specify a different protocol if the server is not an
8102 IMAP server. For example:
8105 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
8111 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
8114 for an NNTP news server.
8115 For an explanation of all of the possibilities, see
8116 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
8120 <End of help on this topic>
8123 ========== h_incoming_add_maildrop =========
8126 <TITLE>ENTER MAILDROP SERVER</TITLE>
8129 <H1>Enter Mail Drop Server</H1>
8131 You are being asked for the name of the Mail Drop server for use with
8132 this incoming folder.
8135 Type the server's name followed by RETURN.
8136 You may use the ^X command if the server is the same as the server that
8140 You may have to add optional extra information to the server name.
8141 For example, if the server is using a non-standard port number you
8142 would specify that by appending a colon (:) followed by the port number
8146 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
8149 or you may need to specify a different protocol if the server is not an
8150 IMAP server. For example:
8153 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
8159 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
8162 for an NNTP news server.
8163 For an explanation of all of the possibilities, see
8164 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
8168 If the Mail Drop folder is on the machine where Alpine is running, then just enter
8169 RETURN without typing a server name.
8172 <End of help on this topic>
8175 ========== h_maildrop =========
8178 <TITLE>WHAT IS A MAIL DROP?</TITLE>
8181 <H1>What is a Mail Drop?</H1>
8183 In some situaions it may make sense to have your mail delivered to one
8184 folder (the Mail Drop) and then when you want to read mail that has been
8185 delivered to the Mail Drop folder Alpine will move it to another
8187 Often the Mail Drop will be a remote folder and messages will be moved from
8188 there to a local destination folder.
8191 One example where this might make sense is if the Mail Drop folder is accessible
8192 only with the POP protocol.
8193 You could designate your POP inbox as the Mail Drop folder and have Alpine move
8194 mail from there to a local (on the same machine Alpine is running on)
8195 destination folder, where you'll read it.
8198 A Mail Drop may only be used as your Inbox or as an
8199 <A HREF="h_config_enable_incoming">"Incoming folder"</A>.
8202 There is no attempt to synchronize the contents of the destination folder
8203 with the contents of the Mail Drop folder.
8204 All that happens is that all of the messages in the Mail Drop folder are
8205 copied to the destination folder and then they are deleted and expunged (if possible)
8206 from the Mail Drop folder.
8207 The next time a check for new mail is made, any messages in the Mail
8208 Drop folder are once again copied to the destination folder and deleted
8209 and expunged from the Mail Drop folder.
8210 (If the Mail Drop folder is a news group, then the messages can't be
8211 expunged from the newsgroup. Instead, only Recent messages are copied from
8212 the newsgroup to the destination folder.)
8215 Configuration of a Mail Drop is a little different from configuration of
8216 a folder that does not use a Mail Drop because you have to specify two
8217 folder names instead of one.
8218 The two folders may be any types of folders that Alpine can normally use.
8219 They don't have to be a remote folder and a local folder, that is
8220 simply the most common usage.
8221 When you use a Mail Drop folder Alpine will periodically re-open the Mail
8222 Drop to check for new mail.
8223 The new-mail checks will happen at the frequency set with the
8224 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option,
8225 but with a minimum time
8226 (<A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>)
8228 Because of this minimum you may notice that new mail does not
8229 appear promptly when you expect it.
8230 The reason for this is to protect the server from over-zealous opening and
8231 closing of the Mail Drop folder.
8232 If the user initiates the check by typing ^L (Ctrl-L) or the Next command when at
8233 the end of the folder index, then the check will happen, regardless of how
8234 long it has been since the previous check.
8236 If there is new mail, that mail will be copied to the destination folder
8237 and then will be deleted from the Mail Drop.
8238 Note that using a Mail Drop with a local destination folder does not make
8239 sense if you read mail from more than one machine, because the mail is
8240 downloaded to the destination folder (which is accessible from only one
8241 machine) and deleted from the Mail Drop.
8243 The feature <A HREF="h_config_maildrops_preserve_state"><!--#echo var="FEAT_maildrops-preserve-state"--></A> modifies the operation of Mail Drops.
8246 The actual syntax used by Alpine for a folder that uses a Mail Drop is:
8249 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
8251 The brackets are not literal.
8253 <CENTER><SAMP><DELIM></SAMP></CENTER>
8255 is a single character that does not appear in the MailDropFolder name.
8256 If the name doesn't contain spaces then it can be a space character.
8257 The two folder names are full technical
8258 <A HREF="h_valid_folder_names">folder names</A>
8260 Here are a couple examples to give you an idea what is being talked about:
8263 <CENTER><SAMP>#move {popserver.example.com/pop3}inbox localfolder</SAMP></CENTER>
8265 <CENTER><SAMP>#move+{nntpserver.example.com/nntp}#news.comp.mail.pine+local folder</SAMP></CENTER>
8268 A #move folder may only be used as an
8269 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
8271 When you are in the FOLDER LIST of Incoming Message Folders (after turning
8273 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
8275 the Add command has a subcommand "Use Mail Drop"
8276 which may be helpful for defining the folder in your Alpine configuration.
8277 The same is true when you edit the
8278 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
8279 option in Setup/Config.
8280 Each of these configuration methods will also create the DestinationFolder
8281 if it doesn't already exist.
8282 If you are having problems, make sure the DestinationFolder exists.
8285 <End of help on this topic>
8288 ========== h_save =========
8291 <TITLE>CHOOSE A FOLDER TO SAVE INTO</TITLE>
8294 <H1>Choose a Folder to Save Into</H1>
8296 After Exiting from this help text,
8297 type the name of the folder you want to save into and press RETURN.
8299 Press ^T to get a list of your folders to choose from.
8300 Press ^C to cancel the Save.
8302 If you have Folder Collections defined you may use
8303 Ctrl-P (Previous collection) and Ctrl-N (Next collection) to switch
8304 the collection being saved to.
8306 If Tab Completion is enabled (it is enabled by default)
8307 you may type a Tab character to have Alpine complete the folder name for you.
8309 If Partial Match Lists is enabled (it is enabled by default) you may type
8310 Ctrl-X to get a list of matches to the prefix you've typed in so far.
8312 If the Ctrl-R subcommand is present that means you can decide to Delete or
8313 not Delete the message you are saving after you save it.
8314 The label on that key gives the action to switch to.
8315 If it says Delete and you type Ctrl-R the label displayed will change to
8316 No Delete and the source message will be deleted after the save. If it
8317 says No Delete and you type Ctrl-R the label displayed will change to
8318 Delete and the message will not be deleted.
8319 You can control the default for the Delete parameter with the
8320 configuration feature <!--#echo var="FEAT_save-will-not-delete"-->.
8322 Similarly, if the Ctrl-W subcommand is present that means you can decide
8323 to Preserve the order of the messages being saved or not.
8324 If it is labeled Preserve Order and you type Ctrl-W, the resulting Saved messages
8325 will be in the same order as you see them in the source folder now.
8326 The opposite action (which is usually the default) is that you don't care
8328 The Saved messages may or may not be in the same order in the destination folder.
8329 There may be a performance penalty for choosing to save the messages in order.
8330 You can control the default for the Preserve Order parameter with the
8331 configuration feature
8332 <!--#echo var="FEAT_save-aggregates-copy-sequence"-->.
8335 If you haven't disabled the Save Input History and you've already done a
8336 Save earlier in this session then you may use the Up and Down arrows to retrieve
8337 a folder name used in a previous Save.
8340 <End of help on this topic>
8343 ============= h_simple_index ========================
8346 <TITLE>SELECT POSTPONED MESSAGE</TITLE>
8349 <H1>POSTPONED MESSAGE SELECTION COMMANDS</H1>
8350 <!--chtml if pinemode="function_key"-->
8352 Navigating the List of Messages General Alpine Commands
8353 ------------------------------- -----------------------
8354 F5 Move to previous message F1 Show this help text
8355 F6 Move to next message
8356 F7 Show previous screen of messages
8357 F8 Show next screen of messages
8359 Message Selection Commands
8360 --------------------------
8361 F3 Exit the Message Select menu (canceling Send command)
8362 F4 Select the currently highlighted message
8363 F9 Mark the currently highlighted message as deleted
8364 F10 Undelete (remove deletion mark from) the highlighted message
8368 Navigating the List of Messages General Alpine Commands
8369 ------------------------------- -----------------------
8370 P Move to previous message ? Show this help text
8371 N Move to next message
8372 - Show previous screen of messages
8373 Spc (space bar) Show next screen of messages
8375 Message Selection Commands
8376 --------------------------
8377 E Exit the Message Select menu (canceling Send command)
8378 S Select the currently highlighted message
8379 D Mark the currently highlighted message as deleted
8380 U Undelete (remove deletion mark from) the highlighted message
8384 <H2>Description of the Select Postponed Message Screen</H2>
8386 This screen allows you to select one of several previously postponed
8387 messages in order to continue composition. Your options are very limited
8388 -- the screen is not meant to let you manipulate these messages. However,
8389 you may now delete messages from this list. Once you choose a message,
8390 Alpine reads it in and puts you into the regular message composer.
8393 Messages do not stay in this postponed state automatically. If you select
8394 a message and then want to postpone it again, use the normal postpone
8395 (Ctrl-O) command in the composer.
8398 If you exit this screen without selecting a message, the Compose command
8399 that got you here is canceled. Other than messages explicitly marked
8400 "Deleted", no messages will be removed.
8403 <End of help on this topic>
8406 ============= h_collection_screen ========================
8409 <TITLE>COLLECTION LIST screen</TITLE>
8412 <H1>COLLECTION LIST screen</H1>
8414 The COLLECTION LIST screen is used to select one of your
8415 collection definitions to display the folders they contain. See
8416 <A HREF="h_what_are_collections">Folder Collections Explained</A> for
8417 detailed explanation of collections.<P>
8419 To manage your collection definitions (Add, Change, Delete, etc.), use
8420 the <A HREF="h_collection_maint">Setup/collectionList</A> command on Alpine's
8424 <End of help on this topic>
8427 ============= h_collection_maint ========================
8430 <TITLE>SETUP COLLECTION LIST screen</TITLE>
8433 <H1>SETUP COLLECTION LIST screen</H1>
8435 The SETUP COLLECTION LIST screen lets you manage your collection
8437 <A HREF="h_what_are_collections">Folder Collections Explained</A>
8438 for detailed explanation of collections.<P>
8440 Maintenance commands include:
8443 <!--chtml if pinemode="function_key"-->
8450 <DD>Modify attributes of the selected collection definition.
8453 <!--chtml if pinemode="function_key"-->
8460 <DD>Create a new collection definition.
8464 <!--chtml if pinemode="function_key"-->
8471 <DD>Delete the selected collection definition.<BR>
8472 NOTE: The folders and directories referred to by the
8473 collection definition are <EM>NOT</EM> deleted. Folders must
8474 be deleted, if that's what you wish to do, from the
8475 <A HREF="h_folder_maint">FOLDER LIST screen</A>, which shows the
8476 individual folders in a collection.
8480 <!--chtml if pinemode="function_key"-->
8487 <DD>Change the order of the displayed collections. Alpine will offer
8488 to move the currently selected collection one position UP
8494 <End of help on this topic>
8497 ============ h_what_are_collections ==========
8500 <TITLE>Folder Collections Explained</TITLE>
8503 <H1>Folder Collections Explained</H1>
8506 Those of you with simple mail configurations will just see a list of all the
8507 folders you have when choosing FOLDER LIST from Alpine's MAIN MENU.
8508 The special folders for INBOX, sent mail and saved messages
8509 will appear at the top of the list. All others are in alphabetical order.
8512 or your system administrator have defined more than one collection or if
8513 you have a collection (for newsgroups or email folders) defined on your
8514 system, then you will see the COLLECTION LIST screen first when choosing
8515 FOLDER LIST from Alpine's MAIN MENU.
8517 <H2>Why have multiple folder collections?</H2>
8519 For Alpine users who only maintain email folders (and not too many) on one host,
8520 a single folder collection is probably sufficient.<P>
8522 However, people who have more than one email account - for example, one
8523 at their university, and one with their personal Internet Service Provider -
8524 will have different sets of folders on different hosts, and they may want to
8525 access them all from the same installation of Alpine, rather than use different
8526 software and/or log into other hosts to manipulate messages in different
8527 accounts. (If in doubt whether one of your email accounts can be accessed
8528 with Alpine, contact the technical support people for that account.) Even people
8529 who have only one email account on one host, but have dozens or
8530 hundreds of email folders, may want to arrange these folders together in a
8532 That is where multiple collections come in.
8534 <H2>Types of Collections</H2>
8536 <DT>INCOMING FOLDERS</DT>
8537 <DD>"Incoming Message Folders"
8538 is a special collection typically used to supplement your single INBOX.
8539 All the folders here are meant to be ones that receive incoming messages,
8540 which you intend to check more or less frequently.
8541 You may have multiple folders like this because you or your systems
8542 administrator have set up an external program or you may have set up
8543 Alpine to filter incoming
8544 messages into different folders, based on certain criteria such as
8545 sender, recipient, or subject; or because you have multiple accounts and
8546 wish to check their INBOXes easily. This collection is established by
8548 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
8549 feature in the SETUP CONFIGURATION screen, which is accessed from the
8554 <DD>You can also define a collection specifically for
8555 newsgroups. Alpine does this for you implicitly when you
8556 <A HREF="h_config_nntp_server">define an NNTP Server</A>
8557 in your Alpine configuration. The news collection appears last in the
8558 COLLECTION LIST (though you can shuffle it up in the order of presentation),
8559 and Alpine knows not to save messages there.
8562 <DT>DEFAULT COLLECTION</DT>
8563 <DD>This is the default collection for your saved and sent messages folders.
8569 <H2>Defining Collections</H2>
8571 In the absence of any folder-collection definitions, Alpine will assume a
8572 single default folder collection.
8573 <!--chtml if pinemode="os_windows"-->
8575 If necessary, Alpine will create the directory
8576 "mail" in your Unix home directory
8577 to hold your folders.
8581 <A HREF="h_collection_maint">Setup/collectionList screen</A>, called up from
8582 the MAIN MENU, to manage your collection list.
8584 <End of help on this topic>
8587 ===== h_select_address_screen =====
8590 <TITLE>SELECT AN ADDRESS SCREEN</TITLE>
8593 <H1>SELECT AN ADDRESS SCREEN</H1>
8595 <!--chtml if pinemode="function_key"-->
8598 -------------------------------
8600 F3 Exit without selecting anything
8601 F4 Select the highlighted address
8602 F5 Move highlight to previous address
8603 F6 Move highlight to next address
8604 F7 Previous page of addresses
8605 F8 Next page of addresses
8611 Navigation General Alpine Commands
8612 ------------------------- -----------------------
8613 P Prev Address ? Display this help text
8614 N Next Address E Exit without selecting anything
8615 - Previous page % Print
8616 Spc (space bar) Next page
8620 ------------------------------------------------
8621 S Select the highlighted address
8625 <H2>Description of the Select Address Screen</H2>
8627 This screen gives you an easy way to select an address from all of
8628 the address book entries that match the prefix typed so far.
8631 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8634 <End of help on this topic>
8637 ===== h_select_rule_screen =====
8640 <TITLE>SELECT A RULE SCREEN</TITLE>
8643 <H1>SELECT A RULE SCREEN</H1>
8645 <!--chtml if pinemode="function_key"-->
8648 -------------------------------
8650 F3 Exit without selecting anything
8651 F4 Select the highlighted rule
8652 F5 Move highlight to previous rule
8653 F6 Move highlight to next rule
8654 F7 Previous page of rules
8655 F8 Next page of rules
8661 Navigation General Alpine Commands
8662 ------------------------- -----------------------
8663 P Prev Rule ? Display this help text
8664 N Next Rule E Exit without selecting anything
8665 - Previous page % Print
8666 Spc (space bar) Next page
8670 ------------------------------------------------
8671 S Select the highlighted rule
8675 <H2>Description of the Select Rule Screen</H2>
8677 This screen just gives you an easy way to select a rule from all of your
8679 The list of rules presented is the list of nicknames of all of the rules
8680 defined using Setup/Rules.
8681 For selecting messages, it is likely that the Indexcolor rules and possibly
8682 the Roles rules will be most useful.
8683 The others are there also, in case you find a use for them.
8685 In order for this to be useful for selecting messages, the nicknames of
8686 the rules have to be different.
8687 Alpine actually just gets the nickname of the rule that you select and then
8688 looks up that rule using the nickname.
8689 So if there are duplicate nicknames, the first rule that has that
8690 nickname will be used.
8693 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8696 <End of help on this topic>
8699 ===== h_select_priority_screen =====
8702 <TITLE>SELECT A PRIORITY SCREEN</TITLE>
8705 <H1>SELECT A PRIORITY SCREEN</H1>
8707 <!--chtml if pinemode="function_key"-->
8710 -------------------------------
8712 F3 Exit without selecting anything
8713 F4 Select the highlighted priority
8714 F5 Move highlight to previous priority
8715 F6 Move highlight to next priority
8716 F7 Previous page of priorities
8717 F8 Next page of priorities
8723 Navigation General Alpine Commands
8724 ------------------------- -----------------------
8725 P Prev Priority ? Display this help text
8726 N Next Priority E Exit without selecting anything
8727 - Previous page % Print
8728 Spc (space bar) Next page
8732 ------------------------------------------------
8733 S Select the highlighted priority
8737 <H2>Description of the Select Priority Screen</H2>
8739 This screen gives you a way to select a priority for the message you are sending.
8740 This priority will be placed in the non-standard X-Priority header of your outgoing mail.
8741 Some mail programs will display an indication of the priority level to
8742 the recipient of the message, some will ignore it.
8743 Even in cases where the mail programs of both the sender and the recipient
8744 agree on the meaning of this header, keep in mind that it is
8745 something that the sender sets so it is only an indication
8746 of the priority that the sender attaches to the mail.
8747 Alpine can be made to display an indication of this priority in incoming
8748 messages by use of one of the tokens
8749 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
8750 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
8751 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
8754 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8757 <End of help on this topic>
8760 ===== h_select_keyword_screen =====
8763 <TITLE>SELECT A KEYWORD SCREEN</TITLE>
8766 <H1>SELECT A KEYWORD SCREEN</H1>
8768 <!--chtml if pinemode="function_key"-->
8771 -------------------------------
8773 F3 Exit without selecting anything
8774 F4 Select the highlighted keyword
8775 F5 Move highlight to previous keyword
8776 F6 Move highlight to next keyword
8777 F7 Previous page of keywords
8778 F8 Next page of keywords
8784 Navigation General Alpine Commands
8785 ------------------------- -----------------------
8786 P Prev Keyword ? Display this help text
8787 N Next Keyword E Exit without selecting anything
8788 - Previous page % Print
8789 Spc (space bar) Next page
8793 ------------------------------------------------
8794 S Select the highlighted keyword
8798 <H2>Description of the Select Keyword Screen</H2>
8800 This screen just gives you an easy way to select a keyword.
8801 The list of keywords presented is the list of all keywords defined in your
8802 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8803 If you have given a keyword a nickname, that nickname is displayed
8804 instead of the actual keyword.
8807 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8810 <End of help on this topic>
8813 ===== h_select_charset_screen =====
8816 <TITLE>SELECT A CHARACTER SET SCREEN</TITLE>
8819 <H1>SELECT A CHARACTER SET SCREEN</H1>
8821 <!--chtml if pinemode="function_key"-->
8824 -------------------------------
8826 F3 Exit without selecting anything
8827 F4 Select the highlighted character set
8828 F5 Move highlight to previous character set
8829 F6 Move highlight to next character set
8830 F7 Previous page of character sets
8831 F8 Next page of character sets
8837 Navigation General Alpine Commands
8838 ------------------------- -----------------------
8839 P Prev Character Set ? Display this help text
8840 N Next Character Set E Exit without selecting anything
8841 - Previous page % Print
8842 Spc (space bar) Next page
8846 ------------------------------------------------
8847 S Select the highlighted character set
8851 <H2>Description of the Select A Character Set Screen</H2>
8853 This screen just gives you an easy way to select a character set from the
8854 set of character sets Alpine knows about.
8855 The list presented will vary slightly depending on what option you are
8856 selecting the character set for.
8859 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8862 <End of help on this topic>
8865 ===== h_select_multcharsets_screen =====
8868 <TITLE>SELECT CHARACTER SETS SCREEN</TITLE>
8871 <H1>SELECT CHARACTER SETS SCREEN</H1>
8873 <!--chtml if pinemode="function_key"-->
8876 -------------------------------
8878 F3 Exit without selecting anything
8879 F4 Select the highlighted charset (or chosen charsets in ListMode)
8880 F5 Move highlight to previous charset
8881 F6 Move highlight to next charset
8882 F7 Previous page of charsets
8883 F8 Next page of charsets
8884 F9 Toggle choices when using ListMode
8885 F10 Turn on/off ListMode (makes it easy to choose multiple charsets)
8891 Navigation General Alpine Commands
8892 ------------------------- -----------------------
8893 P Prev Charset ? Display this help text
8894 N Next Charset E Exit without selecting anything
8895 - Previous page % Print
8896 Spc (space bar) Next page
8900 ------------------------------------------------
8901 S Select the highlighted charset (or chosen charsets in ListMode)
8902 L Turn on ListMode (makes it easy to choose multiple charsets)
8904 X Toggle choices when using ListMode
8908 <H2>Description of the Select Character Set Screen</H2>
8910 This screen just gives you an easy way to select a character set or a list of
8912 The list of character sets presented is the list of all character sets known to
8914 You may select other character sets by typing them in directly.
8917 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8920 <End of help on this topic>
8923 ===== h_select_multkeyword_screen =====
8926 <TITLE>SELECT KEYWORDS SCREEN</TITLE>
8929 <H1>SELECT KEYWORDS SCREEN</H1>
8931 <!--chtml if pinemode="function_key"-->
8934 -------------------------------
8936 F3 Exit without selecting anything
8937 F4 Select the highlighted keyword (or chosen keywords in ListMode)
8938 F5 Move highlight to previous keyword
8939 F6 Move highlight to next keyword
8940 F7 Previous page of keywords
8941 F8 Next page of keywords
8942 F9 Toggle choices when using ListMode
8943 F10 Turn on/off ListMode (makes it easy to choose multiple keywords)
8949 Navigation General Alpine Commands
8950 ------------------------- -----------------------
8951 P Prev Keyword ? Display this help text
8952 N Next Keyword E Exit without selecting anything
8953 - Previous page % Print
8954 Spc (space bar) Next page
8958 ------------------------------------------------
8959 S Select the highlighted keyword (or chosen keywords in ListMode)
8960 L Turn on ListMode (makes it easy to choose multiple keywords)
8962 X Toggle choices when using ListMode
8966 <H2>Description of the Select Keyword Screen</H2>
8968 This screen just gives you an easy way to select a keyword or a list of
8970 The list of keywords presented is the list of all keywords defined in your
8971 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8972 If you have given a keyword a nickname, that nickname is displayed
8973 instead of the actual keyword.
8976 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8979 <End of help on this topic>
8982 ===== h_select_incoming_to_monitor =====
8985 <TITLE>SELECT FOLDERS TO CHECK SCREEN</TITLE>
8988 <H1>SELECT FOLDERS TO CHECK SCREEN</H1>
8990 <!--chtml if pinemode="function_key"-->
8993 -------------------------------
8995 F3 Exit without selecting anything
8996 F4 Select the marked folders
8997 F5 Move highlight to previous folder
8998 F6 Move highlight to next folder
8999 F7 Previous page of folders
9000 F8 Next page of folders
9001 F9 Toggle choices on or off
9007 Navigation General Alpine Commands
9008 ------------------------- -----------------------
9009 P Prev Folder ? Display this help text
9010 N Next Folder ^C exit without changing anything
9011 - Previous page % Print
9012 Spc (space bar) Next page
9016 ------------------------------------------------
9017 S Select the marked folders
9018 X Toggle choices on or off
9022 <H2>Description of the Select Folders to Check Screen</H2>
9024 This screen is only useful if the feature
9025 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
9027 By default, when you set that feature all of your incoming folders
9028 will be checked periodically for Unseen messages.
9029 By using this screen, you may restrict the set of monitored folders to
9030 a subset of all of the incoming folders.
9032 Mark the folders you want to monitor for Unseen messages with
9034 When you've finished marking all your selections use the Select
9035 command to register your choices.
9036 To return to the default of checking all incoming folders
9037 delete all folders or unmark all folders.
9040 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9043 <End of help on this topic>
9046 ===== h_role_select =====
9049 <TITLE>ROLES SCREEN</TITLE>
9052 <H1>ROLES SCREEN</H1>
9053 <H2>ROLES COMMANDS</H2>
9054 <!--chtml if pinemode="function_key"-->
9057 -------------------------------
9059 F3 Exit without a selection
9060 F4 Select a role to use in composition
9061 F5 Move to previous role
9062 F6 Move to next role
9063 F7 Previous page of roles
9064 F8 Next page of roles
9065 F11 Change Default Role
9066 F12 Whereis (search role nicknames)
9070 Navigation General Alpine Commands
9071 ------------------------- -----------------------
9072 P Prev Role ? Display this help text
9073 N Next Role E Exit without a selection
9075 Spc (space bar) Next page
9076 W WhereIs (search for word in role nicknames)
9078 Select Role Commands
9079 ------------------------------------------------
9080 [Return] Select highlighted role
9081 D Change Default Role
9085 <H2>Description of the Roles Screen</H2>
9087 With this screen you select a role to be used in the composition of a
9089 Use the Previous and Next commands to highlight the role you wish to
9091 When you type carriage return you will be placed in the composer using the highlighted role.
9093 You don't have any non-default <A HREF="h_rules_roles">roles</A>
9094 available unless you set them up.
9095 You may do so by using the Setup/Rules command on the MAIN MENU.
9097 By using the D command, you may set a default role that will persist until
9098 you change it or until you exit Alpine.
9099 The D command toggles through three states: set the default role, unset the
9100 default role, and leave the default role as it is.
9102 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9105 <End of help on this topic>
9108 ===== h_role_abook_select =====
9111 <TITLE>SELECT ADDRESS BOOK SCREEN</TITLE>
9114 <H1>SELECT ADDRESS BOOK SCREEN</H1>
9116 <!--chtml if pinemode="function_key"-->
9119 -------------------------------
9121 F3 Exit screen without selecting anything
9122 F4 Select highlighted address book
9123 F5 Move to previous address book
9124 F6 Move to next address book
9125 F7 Previous page of address books
9126 F8 Next page of address books
9131 Navigation General Alpine Commands
9132 ------------------------- -----------------------
9133 P Previous addrbook ? Display this help text
9136 Spc (space bar) Next page
9139 Select Role Commands
9140 ------------------------------------------------
9141 S Select highlighted address book
9142 E Exit screen without selecting anything
9146 <H2>Description of the Select Address Book Screen</H2>
9148 This screen helps you select one of your address books.
9149 Use the Previous and Next commands to highlight the address book you wish to
9152 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9155 <End of help on this topic>
9158 ======== h_rule_patterns =============
9161 <TITLE>PATTERNS</TITLE>
9165 Patterns are used with Roles, Filtering, Index Coloring,
9166 Scoring, Other Rules, and Search Rules.
9167 Patterns are compared with a message to see if there is a match.
9168 For Filtering, the messages being checked are all the messages in the
9169 folder, one at a time.
9170 For Index Line Coloring, each message that is visible on the screen is
9171 checked for matches with the Index Coloring Patterns.
9172 Roles are used with the Reply, Forward, and Compose commands.
9173 For Reply, the message used to compare the Pattern with is the message
9175 for Forward, the message used to compare the Pattern with is the message
9177 and for Compose, there is no message, so the parts of the Pattern that depend
9178 on a message (everything other than Current Folder Type and the
9179 Beginning of Month and Year)
9181 Only the Current Folder Type matters for Compose (plus the Beginning of
9182 Month or Year, which you wouldn't usually use for a Role).
9183 For Scoring, the message being scored is compared with all of the Score
9184 Patterns, and the Score Values from the ones that match are added together to
9185 get the message's score.
9186 For Other Rules, there is no message. Only the Current Folder Type is checked
9189 Each Pattern has several possible parts, all of which are optional.
9190 In order for there to be a match, <EM>ALL</EM> of the
9191 <EM>defined</EM> parts of the Pattern must match the message.
9192 If a part is not defined it is considered a match, but note that a filtering
9193 Pattern must have at least one defined part or it will be ignored.
9194 For example, if the To pattern is not defined it will be
9197 <CENTER>To pattern = <No Value Set></CENTER>
9199 That is considered a match because it is not defined.
9200 This means that the Pattern with nothing defined is a match if the
9201 Current Folder Type matches, but there is an exception that was mentioned
9202 in the previous paragraph.
9203 Because filtering is a potentially destructive action, filtering Patterns
9204 with nothing other than Current Folder Type defined are ignored.
9205 If you really want a filtering Pattern to match all messages (subject to
9206 Current Folder Type) the best way to do it is to define a Score interval
9207 that includes all possible scores.
9208 This would be the score interval <SAMP>(-INF,INF)</SAMP>.
9209 This can be used even if you haven't defined any rules to Set Scores.
9211 There are six predefined header patterns called the To, From, Sender, Cc, News,
9212 and Subject patterns.
9213 Besides those six predefined header patterns, you may add
9214 additional header patterns with header fieldnames of your choosing.
9215 You add an extra header pattern by placing the cursor on one of the
9216 patterns while in the role editor and using the "eXtraHdr" command.
9217 The Recip pattern is a header pattern that stands for Recipient (To OR Cc)
9218 and the Partic pattern is a header pattern that stands for
9219 Participant (From OR To OR Cc).
9220 (Defining the Recip pattern does not have the same effect as defining both
9221 the To and Cc patterns. Recip is To <EM>OR</EM> Cc, not To <EM>AND</EM> Cc.)
9222 Similar to the header patterns are the AllText pattern and the BodyText pattern.
9223 Instead of comparing this pattern's text against only the contents of
9224 a particular header field, the text for the AllText pattern is compared
9225 with text anywhere in the message's header or body, and the text for the
9226 BodyText pattern is compared with text anywhere in the message's body.
9228 Any of the header patterns, the AllText pattern, or the BodyText pattern may be negated with the
9229 "!" "toggle NOT" command.
9230 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9231 "!" at the beginning of the pattern line.
9232 When the "!" is present, it reverses the meaning of the match.
9233 That is, if the pattern matches then it is considered to NOT be a match, and
9234 if it does not match it is considered to be a match.
9236 Don't make the mistake of putting the "!" in the data field for
9238 For example, if you type the characters "!urgent" into the Subject
9239 pattern, the pattern will look like:
9242 Subject pattern = !urgent
9245 This means you want to match the 7 character sequence "!urgent".
9246 In order to match messages that do not have "urgent" in
9247 their Subject field, first type the characters "urgent" followed
9248 by carriage return for the value of the Subject pattern, then negate it
9249 by typing the "!" command.
9253 ! Subject pattern = urgent
9256 The contents of each of these header patterns (or the AllText or BodyText patterns) may
9257 be a complete email address, part of an address, or a random set of
9258 characters to match against.
9259 It may also be a list of such patterns, which means you
9260 are looking for a match against the first pattern in the list <EM>OR</EM>
9261 the second pattern <EM>OR</EM> the third and so on.
9262 For example, a Subject pattern equal to
9265 Subject pattern = urgent
9270 would match all messages with a subject that contained at least one
9272 It would also match subjects containing the words "alerts" or
9273 "Urgently".
9275 The same example with "NOT" turned on would be
9278 ! Subject pattern = urgent
9283 which would match all messages with a subject that did <EM>NOT</EM> contain any of
9285 You can use the "Add Value" command to add new words to the list,
9286 or you can enter them as a comma-separated list.
9288 (It is not possible to specify two patterns that must <EM>BOTH</EM> be
9289 present for a match.
9290 It is only possible to specify that <EM>EITHER</EM> pattern1 <EM>OR</EM>
9291 pattern2 must be present,
9292 and that is exactly what using a list does.)
9294 The "Current Folder Type" and the "Score Interval" are
9295 also part of the Pattern, although the "Score Interval" is not used
9296 when checking for matches for Scoring.
9297 There are five similar settings that relate to the status of the message.
9298 These settings rely on the message being New or not, Deleted or not,
9299 Answered or not, Important or not, and Recent or not.
9300 There are also some other miscellaneous settings.
9301 The first is the Age of the message in days.
9302 Another is the Size of the message, in bytes.
9303 The third is a setting that detects whether or not the Subject of a
9304 message contains raw 8-bit characters (unencoded characters with the most
9305 significant bit set).
9306 There is a setting that detects whether or not this is the first time
9307 Alpine has been run this month (doesn't depend on individual messages),
9308 and another that detects whether or not this is the first time Alpine has
9310 Other parts of the Pattern detect whether or not the From address of a
9311 message appears in your address book, whether or not certain keywords
9312 are set for a message, and whether or not certain character sets are
9315 <H2>Parts of a Pattern</H2>
9317 <H3>Header patterns</H3>
9319 A header pattern is simply text that is searched for in the corresponding
9321 For example, if a Pattern has a From header pattern with the value
9322 "@company.com", then only messages that have a From header
9323 that contains the text "@company.com" will be possible
9325 Matches don't have to be exact.
9326 For example, if the relevant field of a message contains the text
9327 "mailbox@domain" somewhere
9328 in it, then header patterns of "box", or "x@d", or
9329 "mailbox@domain" are all matches.
9331 All parts of the Pattern must match so, for example,
9332 if a message matches a defined
9333 From pattern, it still must be checked against the other parts of the
9334 Pattern that have been defined.
9335 The To header pattern is a slightly special case.
9336 If the message being checked has a Resent-To header
9337 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, the addresses
9338 there are used in place of the addresses in the To header.
9339 This is only true for the To header.
9340 Resent-cc and Resent-From headers are never used unless you add them
9341 with the eXtraHdrs command.
9343 The meaning of a header pattern may be negated with the
9344 "!" "toggle NOT" command.
9345 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9346 "!" at the beginning of the pattern line.
9347 It would look something like
9350 ! From pattern = susan@example.com
9353 When the "!" is present, it reverses the meaning of the match.
9355 If you want to check for the presence of a header field but don't care
9356 about its value, then
9357 the empty pattern that you get by entering a pair of
9358 double quotes ("") should match any message that
9359 has the corresponding header field.
9361 <H3><A NAME="pattern_alltext">AllText patterns</A></H3>
9363 AllText patterns are just like header patterns except that the text is
9364 searched for anywhere in the message's headers or body, not just in the
9365 contents of a particular header field.
9368 <H3><A NAME="pattern_bodytext">BodyText patterns</A></H3>
9370 BodyText patterns are just like header patterns except that the text is
9371 searched for anywhere in the message's body, not just in the
9372 contents of a particular header field.
9375 If there is more than one header pattern or AllText pattern or BodyText pattern
9376 for which you want to take the
9377 same action there is a shorthand notation that may be used.
9378 Any of these patterns may be a list of patterns instead of
9379 just a single pattern.
9380 If any one of the patterns in the list matches the message
9381 then it is considered a match.
9382 For example, if "company1" and "company2" both required
9383 you to use the same role when replying to messages, you might have
9384 a To pattern that looks like
9387 To pattern = company1.com
9391 This means that if the mail you are replying to was addressed to
9392 either "anything@company1.com" or "anything@company2.com",
9393 then this Pattern is a match and the same actions will be taken.
9395 The meaning of an AllText or BodyText pattern may be negated with the
9396 "!" "toggle NOT" command.
9397 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9398 "!" at the beginning of the pattern line.
9399 When the "!" is present, it reverses the meaning of the match.
9401 A technicality: Since comma is the character used to separate multiple values
9402 in any of the fields that may have multiple values (such as header patterns,
9403 AllText patterns, BodyText patterns, keywords, folder lists, and so on),
9404 you must escape comma with a
9405 backslash (\) if you want to include a literal comma in one of those fields.
9406 In other words, if you type a backslash followed by a comma it will
9407 be interpreted as a comma by Alpine, instead of as a separator between
9409 All other backslashes (those not followed by a comma) are literal
9410 backslashes and should not be escaped.
9411 It's unlikely you'll ever need to enter a literal comma or backslash in
9412 any of the patterns.
9414 <H3><A NAME="pattern_current_folder">Current Folder Type</A></H3>
9416 The "Current Folder Type" may be set to one of four different
9417 values: "Any", "News", "Email", or
9418 "Specific".
9419 If the value is set to "News", then the
9420 Pattern will only match if the currently open folder is a newsgroup.
9421 The value "Email" only matches if the current folder is not news and
9422 the value "Any" causes any folder to match.
9423 If the value of "Current Folder Type" is set to "Specific",
9424 then you must fill in a value for "Folder", which is on the line
9425 below the "Specific" line.
9426 In this case you will only get a match if the currently open folder is
9427 the specific folder you list.
9428 You may give a list of folders instead of just a single
9429 folder name, in which case the Pattern will match if the open folder is
9430 any one of the folders in the list.
9431 The name of each folder in the list may be either "INBOX",
9432 the technical specification
9433 of the folder (like what appears in your configuration file) or, if the
9434 folder is one of your incoming folders, it may be the nickname you've given
9436 Here are some samples of specific folder names:
9438 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
9440 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
9442 <CENTER><SAMP>mail/local-folder</SAMP></CENTER>
9444 The easiest way to fill in the "Folder" field is to use
9445 the "T" command that is available when the "Folder" line is
9446 highlighted, or to use the "Take" command with the configuration
9448 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
9451 When reading a newsgroup, there may be a performance penalty
9452 incurred when collecting the information necessary to check whether
9453 or not a Pattern matches a message.
9454 For this reason, the default Current Folder Type is set to "Email".
9455 If you have Patterns with a Current Folder Type of either
9456 "Any" or "News" and those Patterns are used for
9457 Index Line Coloring or Scoring, you may experience
9458 slower screen redrawing in the MESSAGE INDEX screen when in a newsgroup.
9460 <H3><A NAME="pattern_age_interval">Age Interval</A></H3>
9462 The "Age Interval" may be set to an interval of message
9463 ages that should be considered a match.
9464 Like the other parts of the Pattern, if it is unset it will be ignored.
9465 The Age Interval looks like
9467 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
9469 where "min_age" and "max_age" are integers greater
9470 than or equal to zero.
9471 The special value "INF" may be used for
9472 the max value. It represents infinity.
9474 Actually, this option may be defined as a list of intervals instead
9475 of just a single interval.
9476 The list is separated by commas.
9479 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
9481 When there is an Age Interval defined, it is a match if the age, in days, of
9482 the message is contained in any of the intervals.
9483 The intervals include both endpoints.
9485 Even though this option is called Age, it isn't actually
9486 the <EM>age</EM> of the message.
9487 Instead, it is how many days ago the message arrived in one of your folders.
9488 If the current time is a little past midnight, then a message that arrived
9489 just before midnight arrived yesterday, even though the message is only
9491 By default, the date being used is not the date in the Date
9492 header of the message.
9493 It is the date that the message arrived in one of your folders.
9494 When you Save a message from one folder to another that arrival date
9496 If you would like to use the date in the Date header that is possible.
9498 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
9499 near the bottom of the rule definition.
9500 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
9502 <H3><A NAME="pattern_size_interval">Size Interval</A></H3>
9504 The "Size Interval" may be set to an interval of message
9505 sizes that should be considered a match.
9506 Like the other parts of the Pattern, if it is unset it will be ignored.
9507 The Size Interval looks like
9509 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
9511 where "min_size" and "max_size" are integers greater
9512 than or equal to zero.
9513 The special value "INF" may be used for
9514 the max value. It represents infinity.
9516 Actually, this option may be defined as a list of intervals instead
9517 of just a single interval.
9518 The list is separated by commas.
9521 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
9523 When there is a Size Interval defined, it is a match if the size, in bytes, of
9524 the message is contained in any of the intervals.
9525 The intervals include both endpoints.
9527 <H3><A NAME="pattern_score_interval">Score Interval</A></H3>
9529 The "Score Interval" may be set to an interval of message
9530 scores that should be considered a match.
9531 Like the other parts of the Pattern, if it is unset it will be ignored.
9532 The Score Interval looks like
9534 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
9536 where "min_score" and "max_score" are positive or
9537 negative integers, with min_score less than or equal to max_score.
9538 The special values "-INF" and "INF" may be used for
9539 the min and max values to represent negative and positive infinity.
9541 Actually, a list of intervals may be used if you wish.
9542 A list would look like
9544 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
9546 When there is a Score Interval defined, it is a match if the score for
9547 the message is contained in any of the intervals in the list.
9548 The intervals include the endpoints.
9549 The score for a message is calculated by looking at every Score rule defined and
9550 adding up the Score Values for the ones that match the message.
9551 When deciding whether or not a Pattern matches a message for purposes of
9552 calculating the score, the Score Interval is ignored.
9554 <H3><A NAME="pattern_message_status">Message Status</A></H3>
9556 There are five separate message status settings.
9557 By default, all five are set to the value "Don't care", which
9558 will match any message.
9559 The value "Yes" means that the particular status must be true
9560 for a match, and the value "No" means that the particular
9561 status must not be true for a match.
9562 For example, one of the five Message Status settings is whether a message
9563 is marked Important or not.
9564 A "Yes" means that the message must be Important to be
9565 considered a match and "No" means that the message must not be
9566 Important to be considered a match.
9567 The same is true of the other four message status settings that depend
9568 on whether or not the message is New; whether the message has
9569 been Answered or not; whether the message has been Deleted or not, and
9570 whether the message is Recent or not.
9572 The nomenclature for New and Recent is a bit confusing:
9574 New means that the message is Unseen.
9575 It could have been in your mailbox for a long time but if you haven't looked
9576 at it, it is still considered New.
9577 That matches the default Alpine index display that shows an N for such a
9580 Recent means that the message was added to this folder since the last time
9581 you opened the folder.
9582 Alpine also shows an N by default for these types of messages.
9583 If you were to run two copies of Alpine that opened a folder one right after
9584 the other, a message would only show up as Recent in (at most) the first
9587 <H3><A NAME="pattern_message_keywords">Message Keywords</A></H3>
9589 Keywords are similar to Message Status, but they are chosen by the user.
9590 Provided the mail server allows for it, you may add a set of possible keywords
9591 to a folder and then you may set those keywords or not for each message
9592 in the folder (see <A HREF="h_common_flag">Flag Command</A>).
9593 The syntax of this part of the Pattern is similar to the header patterns.
9594 It is a list of keywords.
9595 The Keyword part of the Pattern is a match if the message has any of
9596 the keywords in the list set.
9597 Like other parts of the Pattern, if this is unset it will be ignored.
9599 <H3><A NAME="pattern_message_charsets">Message Character Sets</A></H3>
9601 A message may use one or more character sets.
9602 This part of the Pattern matches messages that make use of one or more of
9603 the character sets specified in the pattern.
9604 It will be considered a match if a message uses any of the character
9605 sets in the list you give here.
9608 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
9609 GB2312) you may also use some shorthand names that Alpine provides.
9610 These names are more understandable shorthand names for sets of
9611 character set names.
9612 Two examples are "Cyrillic" and "Greek".
9613 Selecting one of these shorthand names is equivalent to selecting all of
9614 the character sets that make up the set.
9615 You can see all of these shorthand names and the lists of character sets
9616 they stand for by typing the "T" command with the Character
9617 Set pattern highlighted.
9618 The syntax of this part of the Pattern is similar to the header patterns
9619 and the Message Keywords pattern.
9620 It is a list of character sets (or shorthand names).
9621 The Character Set part of the Pattern is a match if the message uses any
9622 of the character sets in the list.
9623 Like other parts of the Pattern, if this is unset it will be ignored.
9625 <H3><A NAME="pattern_8bit_subject">Raw 8-bit in Subject</A></H3>
9627 It seems that lots of unwanted email contains unencoded 8-bit characters
9629 Normally, characters with the 8th bit set are not allowed in the Subject
9630 header unless they are MIME-encoded.
9631 This option gives you a way to match messages that have Subjects that
9632 contain unencoded 8-bit characters.
9633 By default, the value of this option is "Don't care", which
9634 will match any message.
9635 The value "Yes" means that there must be raw 8-bit characters in
9636 the Subject of the message in order for there to be a match,
9637 and the value "No" is the opposite.
9638 Setting this option will affect performance in large folders because the
9639 subject of each message in the folder has to be checked.
9641 <H3><A NAME="pattern_bom">Beginning of Month</A></H3>
9643 This option gives you a way to take some action once per month.
9644 By default, the value of this option is "Don't care", which
9646 The value "Yes" means that this must be the first time Alpine has
9647 been run this month in order to count as a match,
9648 and the value "No" is the opposite.
9650 <H3><A NAME="pattern_boy">Beginning of Year</A></H3>
9652 This option gives you a way to take some action once per year.
9653 By default, the value of this option is "Don't care", which
9655 The value "Yes" means that this must be the first time Alpine has
9656 been run this year in order to count as a match,
9657 and the value "No" is the opposite.
9659 <H3><A NAME="pattern_abookfrom">Address in Address Books</A></H3>
9661 This option gives you a way to match messages that have an address
9662 that is in one of your address books.
9663 Only the simple entries in your address books are searched.
9664 Address book distribution lists are ignored!
9665 By default, the value of this option is "Don't care", which
9666 will match any message.
9667 The value "Yes, in any address book" means the address
9668 from the message must be in at least one of your
9669 address books in order to be a match.
9670 The value "No, not in any address book"
9671 means none of the addresses may
9672 be in any of your address books in order to be a match.
9673 The values "Yes, in specific address books" and
9674 "No, not in any of specific address books" are similar but instead
9675 of depending on all address books you are allowed to give a list of address
9677 The addresses from the message that are checked for are determined by the
9678 setting you have for "Types of addresses to check for in address book".
9679 If you set this to "From" the From address from the message will
9680 be looked up in the address book.
9681 If you set it to only "To" then the To addresses will be used.
9682 If any of the To addresses are in the address book then it is considered
9683 a match for "Yes" or not a match for "No".
9684 You could set it to both From and To, in which case all of the From and To
9686 The "Reply-To" and "Sender" cases are a little unusual.
9687 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
9688 exists or the From address if there is no Reply-To address.
9689 Same for the Sender address.
9690 Setting this option may affect performance in large folders because the
9691 From and Reply-To of each message in the folder have to be checked.
9693 <H3><A NAME="pattern_categorizer">Categorizer Command</A></H3>
9695 This is a command that is run with its standard input set to the message
9696 being checked and its standard output discarded.
9697 The full directory path should be specified.
9698 The command will be run and then its exit status will be checked against
9699 the Exit Status Interval, which defaults to just the value zero.
9700 If the exit status of the command falls in the interval, it is considered
9701 a match, otherwise it is not a match.
9704 This option may actually be a list of commands.
9705 The first one that exists and is executable is used.
9706 That makes it possible to use the same configuration with Unix Alpine and
9710 If none of the commands in the list exists and is executable then the rule
9711 is <EM>not</EM> a match.
9712 If it is possible that the command may not exist, you should be careful
9713 to structure your rules so that nothing destructive
9714 happens when the command does not exist.
9715 For example, you might have a filter that filters away spam when there is
9716 a match but does nothing when there is not a match.
9717 That would continue to work correctly if the command didn't exist.
9718 However, if you have a filter that filters away spam when there is not
9719 a match and keeps it when there is a match, that would filter everything
9720 if the categorizer command didn't exist.
9722 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
9723 setup for the bogofilter filter.
9726 <End of help on this topic>
9729 ===== h_rules_roles =====
9732 <TITLE>SETUP ROLES SCREEN</TITLE>
9735 <H1>SETUP ROLES SCREEN</H1>
9736 <H2>SETUP ROLES COMMANDS</H2>
9737 <!--chtml if pinemode="function_key"-->
9739 Available Commands -- Group 1 Available Commands -- Group 2
9740 ------------------------------- ------------------------------
9741 F1 Show Help Text F1 Show Help Text
9742 F2 See commands in next group F2 See commands in next group
9743 F3 Back to MAIN Alpine menu
9744 F4 Change configuration for role
9745 F5 Move to previous role F5 Include file in role config
9746 F6 Move to next role F6 Exclude file from config
9747 F7 Previous page of roles
9748 F8 Next page of roles
9749 F9 Add new role F9 Replicate existing role
9750 F10 Delete existing role
9751 F11 Shuffle the order of roles
9752 F12 Whereis (search role nicknames)
9756 Navigation General Alpine Commands
9757 ------------------------- -----------------------
9758 P Prev Role ? Display this help text
9759 N Next Role E Back to MAIN Alpine menu
9761 Spc (space bar) Next page
9762 W WhereIs (search for word in role nicknames)
9764 Setup Roles Commands
9765 ------------------------------------------------
9766 A Add new role $ Shuffle the order of roles
9767 D Delete existing role C Change configuration for highlighted role
9768 R Replicate existing role
9769 I Include file in role config X Exclude file from role config
9773 <H2>Description of the Setup Roles Screen</H2>
9775 This screen lets you add, delete, modify, or change the order of the rules
9776 that determine the role you are playing when composing a message.
9778 You may play different roles depending on who you are replying to.
9779 For example, if you are replying to a message addressed to help-desk you
9780 may be acting as a Help Desk Worker.
9781 That role may require that you use a different return address and/or
9782 a different signature.
9785 If you set up roles they work like this: Each role has a set of
9786 "Uses", which indicate whether or not a role is eligible to be
9787 considered for a particular use; a "Pattern",
9788 which is used to decide which of the eligible roles is used; and a set
9789 of "Actions", which are taken when that role is used.
9790 When you reply to a message, the message you are replying to is compared
9791 with the Patterns of the roles marked as eligible for use when replying.
9792 The comparisons start with the first eligible role and keep going until there
9794 If a match is found, the matching role's Actions are taken.
9796 It is also possible to set a default role and to change that role during
9797 your Alpine session.
9798 When you start Alpine no default role will be set.
9799 You may set or change the current default role by using the "D"
9800 command in the role selection screen.
9801 You'll see that screen while composing a message and being asked to select
9803 An easy way to get to that screen is to use the <A HREF="h_common_role">Role Command</A> to
9805 You may find a default role useful if you normally perform the duties of one
9806 of your roles for a while, then you switch to another role and stay in the
9807 new role for another period of time.
9808 It may be easier than using the Role Command to select the role each time you
9813 There are three types of use to be configured;
9814 one for Replying, one for Forwarding, and one for Composing.
9815 These indicate whether or not you want a role to be considered when you
9816 type the Reply, Forward, or Compose commands.
9817 (The Role command is an alternate form of the Compose command, and it is
9818 not affected by these settings.)
9819 Each of these Use types has three possible values.
9820 The value "Never"
9821 means that the role will never be considered as a candidate for use with
9822 the corresponding command.
9823 For example, if you set a role's Reply Use to Never, then when you Reply to
9824 a message, that role won't even be considered.
9825 (That isn't quite true. If the message you are replying to matches some other
9826 role that requires confirmation,
9827 then there will be a ^T command available which allows you to select a role
9828 from all of your roles, not just the reply-eligible roles.)
9831 The options "With confirmation" and "Without confirmation"
9832 both mean that you do want to consider this role when using the corresponding
9834 For either of these settings the role's Pattern will
9835 be checked to see if it matches the message.
9836 For Reply Use, the message used to compare the Pattern with is the message
9838 For Forward Use, the message used to compare the Pattern with is the message
9840 For Compose Use, there is no message, so the parts of the Pattern that depend
9841 on a message (everything other than Current Folder Type) are ignored.
9842 In all cases, the Current Folder Type is checked if defined.
9843 If there is a match then this role will either be used without confirmation
9844 or will be the default when confirmation is asked for, depending on
9845 which of the two options is selected.
9846 If confirmation is requested, you will have a chance to
9847 choose No Role instead of the offered role, or to
9848 change the role to any one of your other roles (with the ^T command).
9850 <H2>Role Patterns</H2>
9852 In order to determine whether or not a message matches a role the message is
9853 compared with the Role's Pattern.
9854 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9855 Scoring, Other Rules, and Search Rules, so are described in only one place,
9856 "<A HREF="h_rule_patterns">here</A>".
9858 Since header patterns, AllText patterns, and BodyText patterns that are unset are ignored,
9859 a role that has all header patterns unset, the AllText pattern unset,
9860 the BodyText pattern unset,
9861 the Score Interval unset, and the Current Folder Type set to
9862 "Any" may be used as a default role.
9863 It should be put last in the list of roles since the matching
9864 starts at the beginning and proceeds until one of the roles is a match.
9865 If no roles at all match, then Alpine will
9866 use its regular methods of defining the role.
9867 If you wanted to, you could define a different "default" role
9868 for Replying, Forwarding, and Composing by setting the
9869 "Use" fields appropriately.
9871 <H2>Role Actions</H2>
9873 Once a role match is found, the role's Actions are taken.
9874 For each role there are several possible actions that may be defined.
9875 They are actions to set the From address, the Reply-To address,
9876 the Fcc, the Signature, the Template file, and Other Headers.
9880 The From address is the address used on the From line of the message
9883 <H3>Set Reply-To</H3>
9885 The Reply-To address is the address used on the Reply-To line of the message
9887 You don't need a Reply-To address unless it is different from the From address.
9889 <H3>Set Other Headers</H3>
9891 If you want to set the value of the From or Reply-To headers, use
9892 the specific fields "Set From" or "Set Reply-To".
9893 If you want to set the values of other headers, use this field.
9894 This field is similar to the
9895 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> configuration option.
9896 Each header you specify here must include the header tag
9897 ("To:", "Approved:", etc.)
9898 and may optionally include a value for that header.
9899 It is different from the <!--#echo var="VAR_customized-hdrs"--> in that the value you give
9900 for a header here will replace any value that already exists.
9901 For example, if you are Replying to a message there will be at least one
9902 address in the To header (the address you are Replying to).
9903 However, if you Reply using a role that sets the To header, that role's
9904 To header value will be used instead.
9908 The Fcc is used as the Fcc for the message you are sending.
9910 <H3>Set Signature or Set LiteralSig</H3>
9912 The Signature is the name of a file to be used as the signature file when
9913 this role is being used.
9914 If the name of the file has a vertical bar following it (|)
9915 then it is assumed that the file is a program that should be run to
9916 produce the signature.
9917 If the LiteralSig is set, then it is used instead of the signature file.
9918 LiteralSig is just a different way to store the signature.
9919 It is stored in the pine configuration file instead of in a separate
9921 If the <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined
9922 either in the role or as the default signature in the Setup/Config screen,
9923 then the signature file is ignored.
9925 <H3>Set Template</H3>
9927 A Template is the name of a file to be included in the message when this
9929 If the name of the file has a vertical bar following it (|)
9930 then it is assumed that the file is a program that should be run to
9931 produce the template.
9934 Both signature files and template files may be stored remotely on an IMAP
9936 In order to do that you just give the file a remote name.
9937 This works just like the regular
9938 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>
9939 option that is configured from the Setup/Configuration screen.
9940 A remote signature file name might look like:
9942 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
9944 Once you have named the remote signature or template file you create its
9945 contents by using the "F" "editFile" command when the
9946 cursor is on the "Set Signature" or "Set Template"
9947 line of the role editor.
9950 Both signature files and template files (or the output of signature programs
9951 and template file programs) may contain special tokens
9952 that are replaced with contents
9953 that depend on the message being replied to or forwarded.
9954 See the help for the individual fields inside the role editor for more
9955 information on tokens.
9957 <H3>Use SMTP Server</H3>
9959 If this field has a value, then it will be used as the SMTP server
9960 to send mail when this role is being used (unless the SMTP server variable
9961 is set in the system-wide fixed configuration file).
9962 It has the same semantics as the
9963 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
9964 variable in the Setup/Config screen.
9965 When you postpone the composition this SMTP server list will be saved
9966 with the postponed composition and it cannot be changed later.
9967 Because of that, you may want to make this a list of SMTP servers
9968 with the preferred server at the front of the list and alternate servers
9972 If any of the actions are left unset, then the action depends on what
9973 is present in the "Initialize settings using role" field.
9974 If you've listed the nickname of another one of your roles there, then the
9975 corresponding action from that role will be used here.
9976 If that action is also blank, or if there is no nickname specified,
9977 then Alpine will do whatever it normally does to set these actions.
9978 This depends on other configuration options and features you've set.
9980 <H2>Command Descriptions</H2>
9984 The Add command is used to add a new role definition to your set of
9986 The new role will be added after the highlighted role.
9990 The Delete command deletes the currently highlighted role.
9994 The Change command lets you edit the nickname, Uses, Pattern,
9995 and Actions of the currently highlighted role.
9999 The Shuffle command allows you to change the order of the roles.
10000 You may move the currently highlighted role up or down in the list.
10001 The order of the roles is important since the roles are tested for a
10002 match starting with the first role and continuing until a match is found.
10003 You should place the roles with more specific Patterns near the beginning
10004 of the list, and those with more general Patterns near the end so that
10005 the more specific matches will happen when appropriate.
10009 The Replicate command is used to copy an existing role and modify it.
10010 The new role will be added after the highlighted role.
10012 <H3>IncludeFile</H3>
10014 The IncludeFile command allows you to add a roles file to your configuration.
10015 Usually, your roles will be contained in your Alpine configuration file.
10016 If you wish, some or all of your roles may be stored in a separate file.
10017 If a roles file already exists (maybe it was made by somebody else using
10018 Alpine), you may insert it before the currently highlighted role.
10019 You may also insert an empty file or a file that does not yet exist.
10020 Once you have an empty roles file in your configuration, you may use
10021 the Shuffle command to move roles into it.
10022 In fact, that's the only way to get the initial role into the file.
10024 <H3>eXcludeFile</H3>
10026 The eXcludeFile command removes a roles file from your roles configuration.
10027 A limitation of the program is that in order to exclude a roles file
10028 that file must have at least one role
10029 in it, otherwise you won't be able to highlight a line in the file.
10030 So you may have to add a dummy role to the file in order to exclude the file.
10032 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10035 <End of help on this topic>
10038 ===== h_rules_other =====
10041 <TITLE>SETUP OTHER RULES SCREEN</TITLE>
10044 <H1>SETUP OTHER RULES SCREEN</H1>
10045 <H2>SETUP OTHER RULES COMMANDS</H2>
10046 <!--chtml if pinemode="function_key"-->
10048 Available Commands -- Group 1 Available Commands -- Group 2
10049 ------------------------------- ------------------------------
10050 F1 Show Help Text F1 Show Help Text
10051 F2 See commands in next group F2 See commands in next group
10052 F3 Back to MAIN Alpine menu
10053 F4 Change configuration for rule
10054 F5 Move to previous rule F5 Include file in rule config
10055 F6 Move to next rule F6 Exclude file from config
10056 F7 Previous page of rules
10057 F8 Next page of rules
10058 F9 Add new rule F9 Replicate existing rule
10059 F10 Delete existing rule
10060 F11 Shuffle the order of rules
10061 F12 Whereis (search rule nicknames)
10065 Navigation General Alpine Commands
10066 ------------------------- -----------------------
10067 P Prev rule ? Display this help text
10068 N Next rule E Back to MAIN Alpine menu
10070 Spc (space bar) Next page
10071 W WhereIs (search for word in rule nicknames)
10073 Setup Other Rules Commands
10074 ------------------------------------------------
10075 A Add new rule $ Shuffle the order of rules
10076 D Delete existing rule C Change configuration for highlighted rule
10077 R Replicate existing rule
10078 I Include file in rule config X Exclude file from rule config
10082 <H2>Description of the Setup Other Rules Screen</H2>
10084 This is where you may set various actions that do not fit well into the
10085 other Rules categories.
10089 Other Rules are a little different from the rest of the Rules because
10090 they depend only on the current folder, and not on a particular message.
10091 In order to determine whether or not a rule's actions should be applied
10092 the current folder is compared with the rule's Pattern, which consists
10093 of only the Current Folder Type.
10094 Current Folder Type works the same for Other Rules as it does for Roles,
10095 Filtering, Index Coloring, and Scoring.
10096 Keep in mind that the only part of the Pattern that applies to Other
10097 Rules is the Current Folder Type when looking at the description of
10099 "<A HREF="h_rule_patterns">here</A>".
10101 <H2>The Actions</H2>
10103 <H3>Set Sort Order</H3>
10105 When you enter a new folder, these rules will be checked to see if you
10106 have set a sort order that is different from your default sort order.
10107 The default is set in the Setup/Config screen with
10108 the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
10109 If the Sort Order action is set, then the folder will be displayed sorted in
10110 that sort order instead of in the default order.
10112 A possible point of confusion arises when you change the configuration
10113 of the Sort Order for the currently open folder.
10114 The folder will normally be re-sorted when you go back to viewing the
10116 However, if you have manually sorted the folder with the
10118 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
10119 command, then it will not be re-sorted until the next time it is opened.
10121 <H3>Set Index Format</H3>
10123 When you enter a new folder, these rules will be checked to see if you
10124 have set an Index Format that is different from your default Index Format,
10125 which is set with the
10126 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
10127 If so, the index will be displayed with this format instead of the default.
10129 <H3>Set Startup Rule</H3>
10131 When you enter a new folder, these rules will be checked to see if you
10132 have set a startup rule that is different from the default startup rule.
10133 The default for incoming folders is set in the Setup/Config screen with
10134 the "<!--#echo var="VAR_incoming-startup-rule"-->" option.
10135 The default for folders other than INBOX that are not part of your
10136 incoming collection
10137 (see <A HREF="h_config_enable_incoming"><!--#echo var="FEAT_enable-incoming-folders"--></A> feature)
10138 is to start with the last message in the folder.
10139 If the Startup Rule is set to something other than "default",
10140 then the rule will determine which message will be the current message when
10141 the folder is first opened.
10143 The various startup rule possibilities work the same here as they do in
10144 the incoming collection, so check
10145 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
10148 <H2>Command Descriptions</H2>
10152 The Add command is used to add a new rule definition to your set of
10154 The new rule will be added after the highlighted rule.
10158 The Delete command deletes the currently highlighted rule.
10162 The Change command lets you edit the nickname, Pattern,
10163 and Action of the currently highlighted rule.
10167 The Shuffle command allows you to change the order of the rules.
10168 You may move the currently highlighted rule up or down in the list.
10169 The order of the rules is important since the rules are tested for a
10170 match starting with the first rule and continuing until a match is found.
10171 You should place the rules with more specific Patterns near the beginning
10172 of the list, and those with more general Patterns near the end so that
10173 the more specific matches will happen when appropriate.
10177 The Replicate command is used to copy an existing rule definition and modify it.
10178 The new rule will be added after the highlighted rule.
10180 <H3>IncludeFile</H3>
10182 The IncludeFile command allows you to add a rules file to your configuration.
10183 Usually, your rules will be contained in your Alpine configuration file.
10184 If you wish, some or all of your rules may be stored in a separate file.
10185 If a rules file already exists (maybe it was made by somebody else using
10186 Alpine), you may insert it before the currently highlighted rule.
10187 You may also insert an empty file or a file that does not yet exist.
10188 Once you have an empty rules file in your configuration, you may use
10189 the Shuffle command to move rules into it.
10190 In fact, that's the only way to get the initial rule into the file.
10192 <H3>eXcludeFile</H3>
10194 The eXcludeFile command removes a rules file from your rules configuration.
10195 A limitation of the program is that in order to exclude a rules file
10196 that file must have at least one rule
10197 in it, otherwise you won't be able to highlight a line in the file.
10198 So you may have to add a dummy rule to the file in order to exclude the file.
10200 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10203 <End of help on this topic>
10206 ===== h_rules_srch =====
10209 <TITLE>SETUP SEARCH RULES SCREEN</TITLE>
10212 <H1>SETUP SEARCH RULES SCREEN</H1>
10213 <H2>SETUP SEARCH RULES COMMANDS</H2>
10214 <!--chtml if pinemode="function_key"-->
10216 Available Commands -- Group 1 Available Commands -- Group 2
10217 ------------------------------- ------------------------------
10218 F1 Show Help Text F1 Show Help Text
10219 F2 See commands in next group F2 See commands in next group
10220 F3 Back to MAIN Alpine menu
10221 F4 Change configuration for rule
10222 F5 Move to previous rule F5 Include file in rule config
10223 F6 Move to next rule F6 Exclude file from config
10224 F7 Previous page of rules
10225 F8 Next page of rules
10226 F9 Add new rule F9 Replicate existing rule
10227 F10 Delete existing rule
10228 F11 Shuffle the order of rules
10229 F12 Whereis (search rule nicknames)
10233 Navigation General Alpine Commands
10234 ------------------------- -----------------------
10235 P Prev rule ? Display this help text
10236 N Next rule E Back to MAIN Alpine menu
10238 Spc (space bar) Next page
10239 W WhereIs (search for word in rule nicknames)
10241 Setup Search Rules Commands
10242 ------------------------------------------------
10243 A Add new rule $ Shuffle the order of rules
10244 D Delete existing rule C Change configuration for highlighted rule
10245 R Replicate existing rule
10246 I Include file in rule config X Exclude file from rule config
10250 <H2>Description of the Setup Search Rules Screen</H2>
10252 One of the commands that becomes available when that feature is turned on
10253 is the "; Select" command, which is used in the MESSAGE INDEX
10254 screen to select a set of messages.
10255 One way of selecting messages is to use a Rule.
10256 All of the messages that match (or don't match if you wish)
10257 a Rule's Pattern will be selected.
10259 Any of your Rules may be used for this purpose.
10260 You might already have Rules set up for filtering, index line color, scores, or roles;
10261 and you may use any of those Rules with the Select command.
10262 However, you might find it more convenient to set up a separate set of Rules
10263 just for this purpose without having to worry about what other effects
10265 That is the purpose of these Select Rules.
10268 Each rule has a "Pattern"
10269 that is used to decide which messages are selected when you use it with
10270 the Select command.
10274 In order to determine whether or not a message should be selected
10275 the message is compared with the rule's Pattern.
10276 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10277 Scoring, Other Rules, and Search Rules, so are described in only one place,
10278 "<A HREF="h_rule_patterns">here</A>".
10280 <H2>Command Descriptions</H2>
10284 The Add command is used to add a new rule definition to your set of
10286 The new rule will be added after the highlighted rule.
10290 The Delete command deletes the currently highlighted rule.
10294 The Change command lets you edit the nickname and Pattern
10295 of the currently highlighted rule.
10299 The Shuffle command allows you to change the order of the rules.
10300 This affects only the order they are presented in when you use the
10301 ^T subcommand of the Select by Rule command.
10302 You may move the currently highlighted rule up or down in the list.
10306 The Replicate command is used to copy an existing rule definition and modify it.
10307 The new rule will be added after the highlighted rule.
10309 <H3>IncludeFile</H3>
10311 The IncludeFile command allows you to add a rules file to your configuration.
10312 Usually, your rules will be contained in your Alpine configuration file.
10313 If you wish, some or all of your rules may be stored in a separate file.
10314 If a rules file already exists (maybe it was made by somebody else using
10315 Alpine), you may insert it before the currently highlighted rule.
10316 You may also insert an empty file or a file that does not yet exist.
10317 Once you have an empty rules file in your configuration, you may use
10318 the Shuffle command to move rules into it.
10319 In fact, that's the only way to get the initial rule into the file.
10321 <H3>eXcludeFile</H3>
10323 The eXcludeFile command removes a rules file from your rules configuration.
10324 A limitation of the program is that in order to exclude a rules file
10325 that file must have at least one rule
10326 in it, otherwise you won't be able to highlight a line in the file.
10327 So you may have to add a dummy rule to the file in order to exclude the file.
10329 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10332 <End of help on this topic>
10335 ===== h_rules_incols =====
10338 <TITLE>SETUP INDEX LINE COLORS SCREEN</TITLE>
10341 <H1>SETUP INDEX LINE COLORS SCREEN</H1>
10342 <H2>SETUP INDEX LINE COLORS COMMANDS</H2>
10343 <!--chtml if pinemode="function_key"-->
10345 Available Commands -- Group 1 Available Commands -- Group 2
10346 ------------------------------- ------------------------------
10347 F1 Show Help Text F1 Show Help Text
10348 F2 See commands in next group F2 See commands in next group
10349 F3 Back to MAIN Alpine menu
10350 F4 Change configuration for rule
10351 F5 Move to previous rule F5 Include file in rule config
10352 F6 Move to next rule F6 Exclude file from config
10353 F7 Previous page of rules
10354 F8 Next page of rules
10355 F9 Add new rule F9 Replicate existing rule
10356 F10 Delete existing rule
10357 F11 Shuffle the order of rules
10358 F12 Whereis (search rule nicknames)
10362 Navigation General Alpine Commands
10363 ------------------------- -----------------------
10364 P Prev rule ? Display this help text
10365 N Next rule E Back to MAIN Alpine menu
10367 Spc (space bar) Next page
10368 W WhereIs (search for word in rule nicknames)
10370 Setup Index Color Commands
10371 ------------------------------------------------
10372 A Add new rule $ Shuffle the order of rules
10373 D Delete existing rule C Change configuration for highlighted rule
10374 R Replicate existing rule
10375 I Include file in rule config X Exclude file from rule config
10379 <H2>Description of the Setup Index Line Colors Screen</H2>
10381 Index Line Color causes lines in the MESSAGE INDEX screen to be colored.
10382 This action is only available if your terminal is capable of displaying
10383 color and color display has been enabled with the
10384 <A HREF="h_config_color_style">Color Style</A> option within the
10385 Setup Color screen.
10386 (In PC-Alpine, color is always enabled so there is no option to turn on.)
10387 This screen lets you add, delete, modify, or change the order of the rules
10388 that cause the lines in the MESSAGE INDEX to be displayed in different
10391 Each rule has a "Pattern",
10392 which is used to decide which of the rules is used; and the color that
10393 is used if the Pattern matches a particular message.
10395 <H2>Index Color Patterns</H2>
10397 In order to determine whether or not a message matches an Index Color Rule
10398 the message is compared with the rule's Pattern.
10399 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10400 Scoring, Other Rules, and Search Rules, so are described in only one place,
10401 "<A HREF="h_rule_patterns">here</A>".
10404 If none of the Index Color rules is a match for a particular index line,
10405 then the color used is set using
10406 the <A HREF="h_color_setup">Setup Kolor</A> screen.
10408 <H2>Index Line Color</H2>
10410 This is the color that index lines are colored when there is a matching
10412 This colors the whole index line, except possibly the status letters,
10413 which may be colored separately using
10414 the <A HREF="h_color_setup">Setup Kolor</A> screen.
10416 <H2>Command Descriptions</H2>
10420 The Add command is used to add a new rule definition to your set of
10422 The new rule will be added after the highlighted rule.
10426 The Delete command deletes the currently highlighted rule.
10430 The Change command lets you edit the nickname, Pattern,
10431 and Index Line Color of the currently highlighted rule.
10435 The Shuffle command allows you to change the order of the rules.
10436 You may move the currently highlighted rule up or down in the list.
10437 The order of the rules is important since the rules are tested for a
10438 match starting with the first rule and continuing until a match is found.
10439 You should place the rules with more specific Patterns near the beginning
10440 of the list, and those with more general Patterns near the end so that
10441 the more specific matches will happen when appropriate.
10445 The Replicate command is used to copy an existing rule definition and modify it.
10446 The new rule will be added after the highlighted rule.
10448 <H3>IncludeFile</H3>
10450 The IncludeFile command allows you to add a rules file to your configuration.
10451 Usually, your rules will be contained in your Alpine configuration file.
10452 If you wish, some or all of your rules may be stored in a separate file.
10453 If a rules file already exists (maybe it was made by somebody else using
10454 Alpine), you may insert it before the currently highlighted rule.
10455 You may also insert an empty file or a file that does not yet exist.
10456 Once you have an empty rules file in your configuration, you may use
10457 the Shuffle command to move rules into it.
10458 In fact, that's the only way to get the initial rule into the file.
10460 <H3>eXcludeFile</H3>
10462 The eXcludeFile command removes a rules file from your rules configuration.
10463 A limitation of the program is that in order to exclude a rules file
10464 that file must have at least one rule
10465 in it, otherwise you won't be able to highlight a line in the file.
10466 So you may have to add a dummy rule to the file in order to exclude the file.
10468 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10471 <End of help on this topic>
10474 ===== h_rules_filter =====
10477 <TITLE>SETUP FILTERING SCREEN</TITLE>
10480 <H1>SETUP FILTERING SCREEN</H1>
10481 <H2>SETUP FILTERING COMMANDS</H2>
10482 <!--chtml if pinemode="function_key"-->
10484 Available Commands -- Group 1 Available Commands -- Group 2
10485 ------------------------------- ------------------------------
10486 F1 Show Help Text F1 Show Help Text
10487 F2 See commands in next group F2 See commands in next group
10488 F3 Back to MAIN Alpine menu
10489 F4 Change configuration for filter
10490 F5 Move to previous filter F5 Include file in filter config
10491 F6 Move to next filter F6 Exclude file from config
10492 F7 Previous page of filters
10493 F8 Next page of filters
10494 F9 Add new filter F9 Replicate existing filter
10495 F10 Delete existing filter
10496 F11 Shuffle the order of filters
10497 F12 Whereis (search filter nicknames)
10501 Navigation General Alpine Commands
10502 ------------------------- -----------------------
10503 P Prev Filter ? Display this help text
10504 N Next Filter E Back to MAIN Alpine menu
10506 Spc (space bar) Next page
10507 W WhereIs (search for word in filter nicknames)
10509 Setup Filters Commands
10510 ------------------------------------------------
10511 A Add new filter $ Shuffle the order of filters
10512 D Delete existing filter C Change configuration for highlighted filter
10513 R Replicate existing filter
10514 I Include file in filter config X Exclude file from filter config
10518 <H2>Description of the Setup Filtering Screen</H2>
10520 This screen lets you add, delete, modify, or change the order of the rules
10521 that determine the filtering Alpine does on folders you view.
10523 The software that actually delivers mail (the stuff that happens
10524 before Alpine is involved) for you is in a better position to do mail filtering
10525 than Alpine itself.
10526 If possible, you may want to look into using that sort of mail filtering to
10527 deliver mail to different folders, delete it, or forward it.
10528 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
10530 Filtering is a way to automatically move certain messages from one folder
10531 to another or to delete messages.
10532 It can also be used to set message status (Important, Deleted, New,
10533 Answered) and to set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
10534 Alpine doesn't have the ability to forward mail to another address or
10535 to deliver vacation messages.
10537 Each filtering rule has a "Pattern" and a "Filter Action".
10538 When a folder is opened, when new mail arrives in an open folder, or
10539 when mail is Expunged from a folder; each
10540 message is compared with the Patterns of your filtering rules.
10541 The comparisons start with the first rule and keep going until there
10543 If a match is found, the message may be deleted or moved, depending on
10544 the setting of the Filter Action.
10545 If the message is not deleted, it may have its status altered.
10549 When setting up a Pattern used to delete messages,
10550 it is recommended that you test the Pattern first with a "Move"
10551 folder specified in
10552 case unintended matches occur. Messages that are deleted will be removed
10553 from the folder and <EM>unrecoverable</EM> from within Alpine after the
10554 next Expunge command or once the folder being filtered has been closed.
10556 <H2>Filter Patterns</H2>
10558 In order to determine whether or not a message matches a filter the message is
10559 compared with the Filter's Pattern.
10560 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10561 Scoring, Other Rules, and Search Rules, so are described in only one place,
10562 "<A HREF="h_rule_patterns">here</A>".
10564 Since filtering is a potentially destructive action, if you have a filtering
10565 Pattern with nothing other than Current Folder Type set, that filtering
10568 <H2>Filter Actions</H2>
10570 Once a filter match is found for a particular message, there are some actions
10572 First, the message may have its status changed.
10573 This is the same message status that you can manipulate manually using the
10574 <a href="h_common_flag">Flag Command</a>.
10575 There are always four elements of message status that you can control.
10576 You can set or clear the Important status, the New status, the Deleted
10577 status, and the Answered status.
10578 Of course, if the filter is going to delete the message,
10579 then there is no point in setting message status.
10580 You may also be able to set user-defined keywords for a message.
10581 Read a little about keywords in the help text for the
10582 <A HREF="h_common_flag">Flag</A> command.
10584 Second, the filter may delete or move the message.
10585 Deleting the message marks it Deleted and removes it from view.
10586 It is effectively gone forever (though it technically is still there until
10587 the next expunge command, which may happen implicitly).
10588 Moving the message moves it from the open folder into the folder
10589 listed on the "Folder List" line of the filter configuration.
10590 If you list more than one folder name (separated by commas) then the message
10591 will be copied to each of those folders.
10592 In any case, if "Delete" or "Move" is set then the
10593 message is removed from the current folder.
10594 If you just want to set the messages status without deleting it from
10595 the folder, then set the filter action to
10596 "Just Set Message Status".
10598 (There is no way to do a Copy instead of a Move, due to the difficulties
10599 involved in keeping track of whether or not a message has
10600 already been copied.)
10602 <H2>Command Descriptions</H2>
10606 The Add command is used to add a new filter definition to your set of
10608 The new filter will be added after the highlighted filter.
10612 The Delete command deletes the currently highlighted filter.
10616 The Change command lets you edit the nickname, Pattern,
10617 and Folder of the currently highlighted filter.
10621 The Shuffle command allows you to change the order of the filters.
10622 You may move the currently highlighted filter up or down in the list.
10623 The order of the filters is important since the filters are tested for a
10624 match starting with the first filter and continuing until a match is found.
10625 You should place the filters with more specific Patterns near the beginning
10626 of the list, and those with more general Patterns near the end so that
10627 the more specific matches will happen when appropriate.
10631 The Replicate command is used to copy an existing filter and modify it.
10632 The new filter will be added after the highlighted filter.
10634 <H3>IncludeFile</H3>
10636 The IncludeFile command allows you to add a filters file to your configuration.
10637 Usually, your filters will be contained in your Alpine configuration file.
10638 If you wish, some or all of your filters may be stored in a separate file.
10639 If a filters file already exists (maybe it was made by somebody else using
10640 Alpine), you may insert it before the currently highlighted filter.
10641 You may also insert an empty file or a file that does not yet exist.
10642 Once you have an empty filters file in your configuration, you may use
10643 the Shuffle command to move filters into it.
10644 In fact, that's the only way to get the initial filter into the file.
10646 <H3>eXcludeFile</H3>
10648 The eXcludeFile command removes a filters file from your filters configuration.
10649 A limitation of the program is that in order to exclude a filters file
10650 that file must have at least one filter
10651 in it, otherwise you won't be able to highlight a line in the file.
10652 So you may have to add a dummy filter to the file in order to exclude the file.
10654 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10657 <H3>Performance Considerations</H3>
10658 The number and type of patterns being tested can
10659 adversely effect performance. Issues to be aware
10663 <LI> The more filters you have defined the longer it will take to run down
10664 the list. Deleting unused filters is a good idea.
10665 <LI> Filtering in newsgroups served by an NNTP server will be slow
10666 if your patterns include tests other than "From:"
10667 or "Subject:".
10670 <End of help on this topic>
10673 ===== h_rules_score =====
10676 <TITLE>SETUP SCORING SCREEN</TITLE>
10679 <H1>SETUP SCORING SCREEN</H1>
10680 <H2>SETUP SCORING COMMANDS</H2>
10681 <!--chtml if pinemode="function_key"-->
10683 Available Commands -- Group 1 Available Commands -- Group 2
10684 ------------------------------- ------------------------------
10685 F1 Show Help Text F1 Show Help Text
10686 F2 See commands in next group F2 See commands in next group
10687 F3 Back to MAIN Alpine menu
10688 F4 Change configuration for rule
10689 F5 Move to previous rule F5 Include file in rule config
10690 F6 Move to next rule F6 Exclude file from config
10691 F7 Previous page of rules
10692 F8 Next page of rules
10693 F9 Add new rule F9 Replicate existing rule
10694 F10 Delete existing rule
10695 F11 Shuffle the order of rules
10696 F12 Whereis (search rule nicknames)
10700 Navigation General Alpine Commands
10701 ------------------------- -----------------------
10702 P Prev rule ? Display this help text
10703 N Next rule E Back to MAIN Alpine menu
10705 Spc (space bar) Next page
10706 W WhereIs (search for word in rule nicknames)
10708 Setup Scoring Commands
10709 ------------------------------------------------
10710 A Add new rule $ Shuffle the order of rules
10711 D Delete existing rule C Change configuration for highlighted rule
10712 R Replicate existing rule
10713 I Include file in rule config X Exclude file from rule config
10717 <H2>Description of the Setup Scoring Screen</H2>
10719 Most people will not use scores at all, but if you do use them, here's how
10720 they work in Alpine.
10721 Using this screen, you may define Scoring rules.
10722 The score for a message is calculated by looking at every Score rule defined
10723 and adding up the Score Values for the ones that match the message.
10724 If there are no matches for a message, it has a score of zero.
10725 Message scores may be used a couple of ways in Alpine.
10727 <H3>Sorting by Score</H3>
10729 One of the methods you may use to sort message indexes is to sort by
10731 The scores of all the messages in a folder will be calculated and then
10732 the index will be ordered by placing the messages in order of ascending or
10735 <H3>Scores for use in Patterns</H3>
10737 The Patterns used for Roles, Index Line Coloring, and Filtering have a
10738 category labeled "Score Interval".
10739 When a message is being compared with a Pattern to check for a match, if
10740 the Score Interval is set only messages that have a score somewhere in
10741 the interval are a match.
10743 <H2>Scoring Rule Patterns</H2>
10745 In order to determine whether or not a message matches a scoring rule
10746 the message is compared with the rule's Pattern.
10747 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10748 Scoring, Other Rules, and Search Rules, so are described in only one place,
10749 "<A HREF="h_rule_patterns">here</A>".
10752 Actually, Scoring rule Patterns are slightly different from the other types of
10753 Patterns because Scoring rule Patterns don't contain a Score Interval.
10754 In other words, when calculating the score for a message, which is done
10755 by looking at the Scoring rule Patterns, scores aren't used.
10757 <H2>Score Value</H2>
10759 This is the value that will be added to the score for a message if the
10760 rule's Pattern is a match.
10761 Each individual Score Value is an integer between -100 and 100, and the
10762 values from matching rules are added together to get a message's score.
10763 There is also a way to extract the value from a particular header of each
10764 message. See the help text for Score Value for further information.
10766 <H2>Command Descriptions</H2>
10770 The Add command is used to add a new scoring rule definition.
10771 The new rule will be added after the highlighted rule.
10775 The Delete command deletes the currently highlighted scoring rule.
10779 The Change command lets you edit the nickname, Pattern,
10780 and Score Value of the currently highlighted scoring rule.
10784 The Shuffle command allows you to change the order of the scoring rules.
10785 You may move the currently highlighted rule up or down in the list.
10786 The order of the rules is important since the rules are tested for a
10787 match starting with the first rule and continuing until a match is found.
10788 You should place the rules with more specific Patterns near the beginning
10789 of the list, and those with more general Patterns near the end so that
10790 the more specific matches will happen when appropriate.
10794 The Replicate command is used to copy an existing rule and modify it.
10795 The new rule will be added after the highlighted rule.
10797 <H3>IncludeFile</H3>
10799 The IncludeFile command allows you to add a rules file to your configuration.
10800 Usually, your rules will be contained in your Alpine configuration file.
10801 If you wish, some or all of your rules may be stored in a separate file.
10802 If a rules file already exists (maybe it was made by somebody else using
10803 Alpine), you may insert it before the currently highlighted rule.
10804 You may also insert an empty file or a file that does not yet exist.
10805 Once you have an empty rules file in your configuration, you may use
10806 the Shuffle command to move rules into it.
10807 In fact, that's the only way to get the initial rule into the file.
10809 <H3>eXcludeFile</H3>
10811 The eXcludeFile command removes a rules file from your rules configuration.
10812 A limitation of the program is that in order to exclude a rules file
10813 that file must have at least one rule
10814 in it, otherwise you won't be able to highlight a line in the file.
10815 So you may have to add a dummy rule to the file in order to exclude the file.
10817 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10820 <End of help on this topic>
10823 ===== h_direct_config =====
10826 <TITLE>SETUP LDAP DIRECTORY SERVERS SCREEN</TITLE>
10829 <H1>SETUP LDAP DIRECTORY SERVERS SCREEN</H1>
10830 <H2>SETUP LDAP DIRECTORY SERVERS COMMANDS</H2>
10831 <!--chtml if pinemode="function_key"-->
10834 -------------------------------
10836 F3 Back to MAIN Alpine menu
10837 F4 Change configuration for directory server
10838 F5 Move to previous directory server
10839 F6 Move to next directory server
10840 F7 Previous page of directory servers
10841 F8 Next page of directory servers
10842 F9 Add new directory server
10843 F10 Delete existing directory server
10844 F11 Shuffle the order of directory servers
10845 F12 Whereis (search directory server titles)
10849 Navigation General Alpine Commands
10850 ------------------------- -----------------------
10851 P Prev Directory Server ? Display this help text
10852 N Next Directory Server E Back to MAIN Alpine menu
10854 Spc (space bar) Next page
10855 W WhereIs (search for word in directory server titles)
10857 Setup LDAP Directory Server Commands
10858 ------------------------------------------------
10859 A Add new directory server $ Shuffle the order of directory servers
10860 D Delete existing dir server C Change configuration for highlighted server
10864 <H2>Description of the Setup LDAP Directory Servers Screen</H2>
10866 This screen lets you add, delete, modify, or change the order of your
10867 directory servers. You may also set some optional behavior for each server.
10868 The "Add Dir" command brings up a blank form to
10869 fill in. You will have to supply at least the name of the LDAP server.
10870 You will often have to supply a search base to be used with that server,
10871 as well. Once the form has been brought up on your screen, there is help
10872 available for each of the options you may set.
10874 The "Del Dir" command allows you to remove a directory server
10875 from your configuration.
10877 The "Change" command is similar to the "Add Dir" command.
10878 The difference is that instead of bringing up a form for a new server
10879 configuration, you are changing the configuration of an existing entry.
10880 For example, you might want to correct a typing error, change a
10881 nickname, or change one of the options set for that server.
10883 The "Shuffle" command is used to change the order of directory
10886 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10889 <End of help on this topic>
10892 ============= h_address_display ========================
10895 <TITLE>SEARCH RESULTS INDEX</TITLE>
10898 <H1>SEARCH RESULTS INDEX</H1>
10899 This screen shows the results, if any, of your Directory Server search.
10900 Commands (besides those for screen navigation) are:
10903 <!--chtml if pinemode="function_key"-->
10909 <DD>See the full information for the selected entry.
10912 <!--chtml if pinemode="function_key"-->
10916 <!--chtml endif--></DT>
10917 <DD>Compose a message with the selected entry as the recipient.
10920 <!--chtml if pinemode="function_key"-->
10924 <!--chtml endif--></DT>
10925 <DD>Compose a message with the selected entry as the recipient. This differs
10926 from Compose in that you may select a role before beginning your composition.
10929 <!--chtml if pinemode="function_key"-->
10933 <!--chtml endif--></DT>
10934 <DD>Send the full information for the selected entry as an
10935 email message to someone else.
10938 <!--chtml if pinemode="function_key"-->
10944 <DD>Save to your address book:
10946 <LI>the result of the search (as just found through your query) for the
10948 <LI>the selected entry for repeated Directory Server searching when used
10952 Export to a file (external to Alpine):
10954 <LI>the full information for the selected entry; or
10955 <LI>the email address from the selected entry; or
10956 <LI>the selected entry in <A HREF="h_whatis_vcard">vCard</A> format.
10959 <!--chtml if pinemode="function_key"-->
10965 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10966 displayed text, not the full records for each entry.)
10968 <End of help on this topic>
10971 ============= h_address_select ========================
10974 <TITLE>SEARCH RESULTS INDEX</TITLE>
10977 <H1>SEARCH RESULTS INDEX</H1>
10978 This screen shows the results, if any, of your Directory Server search.
10979 Commands (besides those for screen navigation) are:
10983 <DD>Select this entry for use.
10986 <DD>Exit without selecting any of the entries.
10990 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10991 displayed text, not the full records for each entry.)
10993 <End of help on this topic>
10996 ===== h_folder_maint =====
10999 <TITLE>Help for Folder List</TITLE>
11002 <H1>FOLDER LIST COMMANDS</H1>
11003 <!--chtml if pinemode="function_key"-->
11005 Available Commands -- Group 1 Available Commands -- Group 2
11006 ------------------------------- ------------------------------
11007 F1 Show Help Text F1 Show Help Text
11008 F2 See commands in next group F2 See commands in next group
11009 F3 MAIN MENU Screen F3 Quit Alpine
11010 F4 Select folder and view it F4 MAIN MENU Screen
11011 F5 Move to previous folder
11012 F6 Move to next folder F6 Specify a folder to go to
11013 F7 Show previous screen of listing F7 Show MESSAGE INDEX of current folder
11014 F8 Show next screen of listing F8 Compose a message
11015 F9 Add a new folder F9 Print folder listing
11016 F10 Delete selected folder
11017 F11 Rename selected folder
11018 F12 Whereis (search folder names)
11020 Available Commands -- Group 3
11022 F2 See commands in next group
11023 F5 Go to next new message
11024 (or count recent messages if <A HREF="h_config_tab_checks_recent"><!--#echo var="FEAT_tab-checks-recent"--></A> is set)
11025 F8 Compose a message using roles
11026 F9 Export folder to a file
11027 F10 Import the file back to a folder
11031 Navigating the Folder Screen Operations on the Selected Folder
11032 ---------------------------- ---------------------------------
11033 P Move to previous folder V View Index of selected folder
11034 N Move to next folder D Delete
11035 - Show previous page of listing R Rename
11036 Spc (space bar) Show next page E Export to file
11037 U Import from file to folder
11039 FOLDER LIST Screen Commands General Alpine Command
11040 --------------------------- -----------------------
11041 A Add a folder O Show all other available commands
11042 G Specify a folder to go to ? Show Help text
11043 I Show MESSAGE INDEX of current folder M MAIN MENU Screen
11044 W Whereis (search folder names) Q Quit Alpine
11045 % Print folder listing C Compose a message
11046 # Compose a message using roles
11050 These commands are only available in the FOLDER LIST screen when the
11051 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"
11052 feature</A> is set in the SETUP CONFIGURATION screen:<DL>
11054 <DD>Select folders by certain criteria:<UL>
11055 <LI>All: of limited use, since there is no Apply command.
11056 <LI>by Property: <UL>
11057 <LI>folder contains messages not yet seen
11058 <LI>folder contains new messages
11059 <LI>folder contains exactly as many, more, or fewer messages
11060 than a given number
11063 <LI>contained in name of folder (Name Select)
11064 <LI>contained in messages in folder (Content Select)
11068 <DT>Select current:</DT>
11069 <DD>Select the folder the cursor is on. (Can be used to "manually"
11070 add one or more folders to a set created with the Select command described
11072 <DT>Zoom mode:</DT>
11073 <DD>Toggles display of only selected folders or all folders on and off.</DD>
11077 <A HREF="h_config_tab_checks_recent">"<!--#echo var="FEAT_tab-checks-recent"-->"</A>
11078 is set then the TAB key will display the number of recent messages and
11079 the total number of messages in the highlighted folder.
11081 The "Export" command causes the lowest common denominator style
11082 mailbox to be written to a file.
11083 If the file already exists, you are asked if you want to delete it.
11084 If you say No, then the operation is aborted.
11085 Export might be a reasonable way to store a backup or an archival copy of
11087 The exported-to file is a local file on the system where you are running Alpine.
11088 The "Import" command is the opposite of the Export command.
11089 It reads a file created by Export and asks where it should save it in your
11091 This could be a new folder or an existing folder.
11092 If the folder already exists, the messages from the exported file will be
11093 appended to the folder.
11095 <CENTER>Description of the FOLDER LIST Screen</CENTER>
11097 The purpose of the FOLDER LIST screen is to help you browse and manage
11098 the folders and directories (also known as "hierarchy")
11099 contained within a collection.
11102 Folders and directories are arranged alphabetically across lines of
11103 the screen. Directories, if present, are denoted by a special
11104 character at the end of the name known as the hierarchy delimiter
11105 (typically, "/"). By default, folders and directories are
11106 mixed together. The
11107 "<A HREF="h_config_fld_sort_rule"><!--#echo var="VAR_folder-sort-rule"--></A>"
11108 configuration option can be used to group directories toward the
11109 beginning or end of the list.
11112 The Next/Prev Page commands help browse the list, the Next/Prev Fldr
11113 commands change the "selected" (i.e., highlighted) folder or
11114 directory, and the View Fldr/Dir commands will "open" the
11115 selected item. Folder and directory management is provided via the
11116 Rename, Delete and Add commands.
11118 <P><CENTER>About Folders</CENTER>
11119 What are Folders?<P>
11121 Folders are simply files where messages are kept. Every message has to be
11122 in a folder. Most every Alpine user starts out with 3 folders: an INBOX, a
11123 folder for sent mail and a folder for saved messages.<P>
11125 You may create as many other folders as you wish. They must be given
11126 names that can be filenames on the filesystem.
11129 You can move messages from one folder to another by opening the original
11130 folder and saving messages into the other folder just as you can save
11131 message from your INBOX to any other folder.<P>
11133 Folders are typically just files in the filesystem. However, the files
11135 folders have some special formatting in them (so that Alpine knows where one
11136 message ends and another begins) and should <EM>not</EM> be edited outside of
11137 Alpine. If you want copies of your messages in text files that you can edit
11138 or otherwise manipulate, use the Export command to copy them from Alpine into
11139 your regular file area.
11142 FOR MORE INFORMATION: See the section on
11143 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11145 <CENTER>About Directories</CENTER>
11147 A directory is simply a container used to group folders within a
11148 folder list. You can create as many directories as you like. And
11149 directories can even contain directories themselves.
11152 SPECIAL NOTES: When accessing folders on an IMAP server, it is important
11153 to note that not all IMAP servers support directories. If you find that
11154 the Add command fails to offer the "Create Directory" subcommand,
11155 then it's likely that directories are not supported by the server serving
11156 in that collection.
11159 Similarly, servers that do provide for directories may not do so in
11160 the same way. On some servers, for example, each folder name you
11161 create is at the same time capable of being a directory. When this
11162 happens, Alpine will display both the folder name and the name of the
11163 directory (with trailing hierarchy delimiter) in the folder list.
11166 Another issue with IMAP access, though with a much smaller set of servers,
11167 is that not all servers accept the request to list out the available
11168 folders and directories in the same way. If you find yourself having
11169 trouble viewing folders on your server, you might investigate the
11170 "<A HREF="h_config_lame_list_mode"><!--#echo var="FEAT_enable-lame-list-mode"--></A>"
11174 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11177 <End of help on this topic>
11180 ========= h_valid_folder_names ========
11183 <TITLE>Explanation of Valid Folder Names</TITLE>
11186 <H1>Folder Name Syntax Explained</H1>
11188 Once your folder collections are defined, you can usually refer to
11189 folders by their simple (unqualified) name, or pick from a FOLDER LIST
11190 display. However, understanding the complete syntax for folder names,
11191 both local and remote, is handy when using the Goto command and when
11192 you are adding new folder collections via the Setups/collectionList screen.
11194 An Alpine folder name looks like
11197 <CENTER><SAMP>[{<remote-specification>}][#<namespace>]<namespace-specific-part></SAMP></CENTER>
11200 The square brackets ([]) mean that the part is optional.
11203 If there is no remote-specification, then the folder name is interpreted
11204 locally on the computer running Alpine.
11205 Local folder names depend on the operating system used by the computer
11206 running Alpine, as well as the configuration of that system. For example,
11207 "C:\PINE\FOLDERS\OCT-94" might exist on a PC, and
11208 "~/mail/september-1994" might be a reasonable folder name on a
11209 system running Unix.
11212 Alpine users have the option of using folders that are stored on some other
11213 computer. Alpine accesses remote folders via IMAP (the Internet Message
11214 Access Protocol), or in the case of news, via NNTP (the Network News
11215 Transport Protocol). To be able to access remote folders in Alpine, the
11216 remote host must be running the appropriate server software (imapd or
11217 nntpd) and you must correctly specify the name of the folder to Alpine,
11218 including the domain name of the remote machine. For example,
11220 <CENTER><SAMP>{monet.art.example.com}INBOX</SAMP></CENTER>
11222 could be a remote folder specification, and so could
11224 <CENTER><SAMP>{unixhost.art.example.com}~/mail/september-1994</SAMP></CENTER>
11227 <CENTER><SAMP>{winhost.art.example.com}\mymail\SEP-94</SAMP></CENTER>
11229 Note that in the case of remote folders, the directory/file path in the specification is
11230 determined by the operating system of the remote computer, <B>not</B> by
11231 the operating system of the computer on which you are running Alpine.
11233 As you can tell, the name of the computer is in {} brackets
11234 followed immediately by the name of the folder. (In each of these cases the
11235 optional namespace is missing.) If, as in these
11236 examples, there is no remote access protocol specified, then IMAP is
11238 <A HREF="h_folder_server_syntax">here</A>
11239 for a more detailed look at what options can be placed between the brackets.
11240 If there are no brackets at all, then the folder name is interpreted locally
11241 on the computer on which you are running Alpine.
11244 To the right of the brackets when a server name is present, or at the
11245 start of the foldername if no server is present, the sharp sign,
11246 "#", holds special meaning. It indicates a folder name
11247 outside the area reserved for your personal folders. In fact, it's
11248 used to indicate both the name of the folder, and a special phrase
11249 telling Alpine how to interpret the name that follows.
11252 So, for example, Alpine can be used to access a newsgroup that might be
11253 available on your computer using:
11255 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
11257 The sharp sign indicates the folder name is outside your personal
11258 folder area. The "news." phrase after it tells Alpine to
11259 interpret the remainder of the name as a newsgroup.
11262 Similarly, to access a newsgroup on your IMAP server, you might
11263 use something like:
11265 <CENTER><SAMP>{wharhol.art.example.com}#news.comp.mail.misc</SAMP></CENTER>
11268 There are a number of such special phrases (or "namespaces")
11269 available. For a more detailed explanation read about
11270 <A HREF="h_folder_name_namespaces">Namespaces</A>.
11273 Note that "INBOX" has special meaning in both local and remote folder
11274 names. The name INBOX refers to your "principal incoming
11275 message folder" and will be mapped to the actual file name used for your
11276 INBOX on any given host. Therefore, a name like
11277 "{xxx.art.example.com}INBOX" refers to whatever file is used to
11278 store incoming mail for you on that particular host.
11281 <End of help on this topic>
11284 ======= h_folder_name_namespaces =======
11287 <TITLE>FOLDER NAME NAMESPACES EXPLAINED</TITLE>
11290 <H1>Folder Name Namespaces Explained</H1>
11292 An Alpine folder name looks like
11295 <CENTER><SAMP>[{<remote-specification>}][#<namespace>][<namespace-specific-part>]</SAMP></CENTER>
11298 The local part of a folder name has an optional "Namespace" which
11299 tells Alpine how to interpret the rest of the name.
11302 By default the folder name is interpreted as defining a section of your personal
11303 folder area. This area and how you specify it are defined by the
11304 server, if one is specified, or, typically, the home
11305 directory, if no server is defined.
11308 If a namespace is specified, it begins with the
11309 sharp, "#", character followed by the name of the namespace
11310 and then the namespace's path-element-delimiter. Aside from the
11311 path's format, namespaces can also imply access rights, content
11312 policy, audience, location, and, occasionally, access methods.
11315 Each server exports its own set (possibly of size one) of
11316 namespaces. Hence, it's likely communication with your server's
11317 administrator will be required for specific configurations. Some of
11318 the more common namespaces, however, include:
11322 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
11323 names are hierarchically defined with each level delimited by a period.
11325 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
11329 <DD>This specifies a folder area that the server may export to the general
11333 <DD>This specifies a folder area that the server may export to groups
11337 <DD>This specifies a folder area that is the same as that it may have
11338 exported via the "File Transfer Protocol".
11341 <DD>This specifies the personal folder area associated with folders
11342 and directories that were created using the MH message handling system.
11345 <DD>This namespace is interpreted locally by Alpine. It has an unusual interpretation and format.
11347 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
11349 The #move namespace is followed by two folder names separated by a delimiter
11351 The delimiter character may be any character that does not appear in
11352 the MailDropFolder name.
11353 The meaning of #move is that mail will be copied from the MailDropFolder to
11354 the DestinationFolder and then deleted (if possible) from the MailDropFolder.
11355 Periodic checks at frequency
11356 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A>, but with a minimum
11357 time between checks set by
11358 <A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>,
11359 are made for new mail arriving in the MailDropFolder.
11360 An example that copies mail from a POP inbox to a local folder follows
11362 <CENTER><SAMP>#move+{popserver.example.com/pop3/ssl}inbox+local folder</SAMP></CENTER>
11364 To you it appears that mail is being delivered to the local folder when it
11365 is copied from the MailDropFolder, and you read mail from the local folder.
11367 Note that if the DestinationFolder does not exist then the messages are not
11368 copied from the MailDropFolder.
11369 A #move folder may only be used as an
11370 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
11372 When you are in the FOLDER LIST of Incoming Message Folders (after turning
11374 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
11376 the Add command has a subcommand "Use Mail Drop"
11377 which may be helpful for defining the folder in your Alpine configuration.
11378 The same is true when you edit the
11379 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
11380 option in Setup/Config.
11381 Each of these configuration methods will also create the DestinationFolder
11382 if it doesn't already exist.
11383 If you are having problems, make sure the DestinationFolder exists.
11384 You may find some more useful information about Mail Drops at
11385 <A HREF="h_maildrop">What is a Mail Drop?</A>.
11390 In addition, the server may support access to other user's folders,
11391 provided you have suitable permissions. Common methods use a prefix
11392 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
11393 indicate the root of the other user's folder area.
11396 No, nothing's simple.
11399 <End of help on this topic>
11402 ============= h_whatis_vcard ========================
11405 <TITLE>VCARD EXPLAINED</TITLE>
11408 <H1>What is the vCard format?</H1>
11409 A "vCard" is a sort of electronic business card, for exchanging
11410 information about and among people and organizations electronically.
11411 More information about vCard can be found (as of May 1998) on the WWW site
11412 of the Internet Mail Consortium at the URL:
11414 <CENTER><A HREF="http://www.imc.org/pdi/">http://www.imc.org/pdi/</A></CENTER>
11416 <End of help on this topic>
11419 ===== h_folder_open =====
11422 <TITLE>Explanation of Folder Selection</TITLE>
11427 This screen is designed to allow you to quickly and easily survey your
11428 folders and select one to open.
11429 <!--chtml if pinemode="function_key"-->
11431 Navigating the List of Folders General Alpine Commands
11432 ------------------------------ -----------------------
11433 P Move to previous folder ? Show this help text
11434 N Move to next folder
11435 - Show previous screen of folders
11436 Spc (space bar) Show next screen
11437 W WhereIs (search folder names)
11439 Folder Selection Commands
11440 -------------------------
11441 E Exit the Folder Select menu (without selecting a folder)
11442 S Select the currently highlighted folder
11446 Navigating the List of Folders General Alpine Commands
11447 ------------------------------ -----------------------
11448 F5 Move to previous folder F1 Show this help text
11449 F6 Move to next folder
11450 F7 Show previous screen of folders
11451 F8 Show next screen of folders
11452 F12 WhereIs (search folder names)
11454 Folder Selection Commands
11455 -------------------------
11456 F3 Exit the Folder Select menu (without selecting a folder)
11457 F4 Select the currently highlighted folder
11461 FOR MORE INFORMATION: See the section on
11462 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11464 <End of help on this topic>
11467 ===== h_folder_subscribe =====
11470 <TITLE>Newsgroup Subcribe Screen explained</TITLE>
11473 <H1>FOLDER SUBSCRIBE HELP</H1>
11475 This screen is designed to help you subscribe to newsgroups you are
11476 not currently subscribed to. The screen display is a list of all
11477 available newsgroups (or possibly a partial list if you specified a
11478 partial name when entering the screen). Groups you have already
11479 subscribed to have the letters "SUB" next to them. You may
11480 select a single new group to subscribe to by moving the cursor to that
11481 group and pressing "S" or carriage return. Alternatively,
11482 you may change into ListMode with the "ListMode" command.
11483 The display will change slightly so that each group has a checkbox in
11484 front of it. Use the cursor and the Set/Unset command to place an
11485 "X" in front of each newsgroup you wish to subscribe to.
11488 When you are finished marking groups, the "Subscribe"
11489 command will subscribe you to those groups you have marked. Note, you
11490 may not unsubscribe to groups with this command. Instead of the
11491 "A" "Subscribe" command, use the "D"
11495 <!--chtml if pinemode="function_key"-->
11497 Navigating the List of Newsgroups General Alpine Commands
11498 --------------------------------- -----------------------
11499 F5 Move to previous group F1 Show this help text
11500 F6 Move to next group
11501 F7 Show previous screen of groups
11502 F8 Show next screen of groups
11503 F12 WhereIs (search group names)
11506 Group Selection Commands
11507 -------------------------
11508 F3 Exit the News Subscribe menu (without selecting any groups)
11509 F4 Subscribe to the currently highlighted newsgroup
11513 Navigating the List of Newsgroups General Alpine Commands
11514 --------------------------------- -----------------------
11515 P Move to previous group ? Show this help text
11516 N Move to next group
11517 - Show previous screen of groups
11518 Spc (space bar) Show next screen
11519 W WhereIs (search group names)
11522 Group Selection Commands
11523 -------------------------
11524 E Exit the News Subscribe menu (without selecting any groups)
11525 S Subscribe to the currently highlighted newsgroup
11529 When in ListMode, there is an additional command for marking groups to
11532 <!--chtml if pinemode="function_key"-->
11535 -------------------------
11536 F9 Set or unset the highlighted group
11541 -------------------------
11542 X Set or unset the highlighted group
11546 <End of help on this topic>
11549 ===== h_folder_postnews =====
11552 <TITLE>Newsgroup selecting for Posting explained</TITLE>
11555 This screen is designed to allow you to quickly and easily survey
11556 the available newsgroups and select one to post news to.
11558 <!--chtml if pinemode="function_key"-->
11560 Navigating the List of Newsgroups General Alpine Commands
11561 --------------------------------- -----------------------
11562 F5 Move to previous group F1 Show this help text
11563 F6 Move to next group
11564 F7 Show previous screen of groups
11565 F8 Show next screen of groups
11566 F12 WhereIs (search group names)
11568 Group Selection Commands
11569 -------------------------
11570 F3 Exit the Selection menu (without selecting a group)
11571 F4 Select the currently highlighted newsgroup
11575 Navigating the List of Newsgroups General Alpine Commands
11576 --------------------------------- -----------------------
11577 P Move to previous group ? Show this help text
11578 N Move to next group
11579 - Show previous screen of groups
11580 Spc (space bar) Show next screen of groups
11581 W WhereIs (search group names)
11583 Group Selection Commands
11584 -------------------------
11585 E Exit the Selection menu (without selecting a group)
11586 S Select the currently highlighted newsgroup
11590 <End of help on this topic>
11593 ===== h_folder_save =====
11596 <TITLE>Folder Select for Save Explained</TITLE>
11599 This screen is designed to allow you to quickly and easily survey your
11600 folders and select one to use for saving the current message.
11603 <!--chtml if pinemode="function_key"-->
11605 Navigating the List of Folders General Alpine Commands
11606 ------------------------------ -----------------------
11607 F5 Move to previous folder F1 Show this help text
11608 F6 Move to next folder
11609 F7 Show previous screen of folders
11610 F8 Show next screen of folders
11611 F12 WhereIs (search folder names)
11613 Folder Selection Commands
11614 -------------------------
11615 F3 Exit the Folder Select menu (without selecting a folder)
11616 F4 Select the currently highlighted folder
11617 F11 AddNew folder (just like Select, but you type in a new folder name)
11621 Navigating the List of Folders General Alpine Commands
11622 ------------------------------ -----------------------
11623 P Move to previous folder ? Show this help text
11624 N Move to next folder
11625 - Show previous screen of folders
11626 Spc (space bar) Show next screen of folders
11627 W WhereIs (search folder names)
11629 Folder Selection Commands
11630 -------------------------
11631 E Exit the Folder Select menu (without selecting a folder)
11632 S Select the currently highlighted folder
11633 A AddNew folder (just like Select, but you type in a new folder name)
11637 FOR MORE INFORMATION: See the section on
11638 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11640 <End of help on this topic>
11643 ===== h_folder_fcc =====
11646 <TITLE>Folder Select for Fcc Explained</TITLE>
11649 This screen is designed to allow you to quickly and easily survey your
11650 folders and select one to use as the file carbon copy (fcc) for the
11654 <!--chtml if pinemode="function_key"-->
11656 Navigating the List of Folders General Alpine Commands
11657 ------------------------------ -----------------------
11658 F5 Move to previous folder F1 Show this help text
11659 F6 Move to next folder
11660 F7 Show previous screen of folders
11661 F8 Show next screen of folders
11662 F12 WhereIs (search folder names)
11664 Folder Selection Commands
11665 -------------------------
11666 F3 Exit the Folder Select menu (without selecting a folder)
11667 F4 Select the currently highlighted folder
11668 F11 AddNew folder (just like Select, but you type in a new folder name)
11672 Navigating the List of Folders General Alpine Commands
11673 ------------------------------ -----------------------
11674 P Move to previous folder ? Show this help text
11675 N Move to next folder
11676 - Show previous screen of folders
11677 Spc (space bar) Show next screen of folders
11678 W WhereIs (search folder names)
11680 Folder Selection Commands
11681 -------------------------
11682 E Exit the Folder Select menu (without selecting a folder)
11683 S Select the currently highlighted folder
11684 A AddNew folder (just like Select, but you type in a new folder name)
11688 FOR MORE INFORMATION: See the section on
11689 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11691 <End of help on this topic>
11694 ===== h_folder_pattern_roles =====
11697 <TITLE>Folder Select for Current Folder Explained</TITLE>
11700 This screen is designed to allow you to quickly and easily survey your
11701 folders and select one to use as the specific Current Folder
11705 <!--chtml if pinemode="function_key"-->
11707 Navigating the List of Folders General Alpine Commands
11708 ------------------------------ -----------------------
11709 F5 Move to previous folder F1 Show this help text
11710 F6 Move to next folder
11711 F7 Show previous screen of folders
11712 F8 Show next screen of folders
11713 F12 WhereIs (search folder names)
11715 Folder Selection Commands
11716 -------------------------
11717 F3 Exit the Folder Select menu (without selecting a folder)
11718 F4 Select the currently highlighted folder
11719 F11 AddNew folder (just like Select, but you type in a new folder name)
11723 Navigating the List of Folders General Alpine Commands
11724 ------------------------------ -----------------------
11725 P Move to previous folder ? Show this help text
11726 N Move to next folder
11727 - Show previous screen of folders
11728 Spc (space bar) Show next screen of folders
11729 W WhereIs (search folder names)
11731 Folder Selection Commands
11732 -------------------------
11733 E Exit the Folder Select menu (without selecting a folder)
11734 S Select the currently highlighted folder
11735 A AddNew folder (just like Select, but you type in a new folder name)
11739 FOR MORE INFORMATION: See the section on
11740 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11742 <End of help on this topic>
11745 ===== h_folder_stayopen_folders =====
11748 <TITLE>Folder Select Explained</TITLE>
11751 This screen is designed to allow you to quickly and easily survey your
11752 folders and select one to use as a Stay-Open folder.
11755 <!--chtml if pinemode="function_key"-->
11757 Navigating the List of Folders General Alpine Commands
11758 ------------------------------ -----------------------
11759 F5 Move to previous folder F1 Show this help text
11760 F6 Move to next folder
11761 F7 Show previous screen of folders
11762 F8 Show next screen of folders
11763 F12 WhereIs (search folder names)
11765 Folder Selection Commands
11766 -------------------------
11767 F3 Exit the Folder Select menu (without selecting a folder)
11768 F4 Select the currently highlighted folder
11769 F11 AddNew folder (just like Select, but you type in a new folder name)
11773 Navigating the List of Folders General Alpine Commands
11774 ------------------------------ -----------------------
11775 P Move to previous folder ? Show this help text
11776 N Move to next folder
11777 - Show previous screen of folders
11778 Spc (space bar) Show next screen of folders
11779 W WhereIs (search folder names)
11781 Folder Selection Commands
11782 -------------------------
11783 E Exit the Folder Select menu (without selecting a folder)
11784 S Select the currently highlighted folder
11785 A AddNew folder (just like Select, but you type in a new folder name)
11789 FOR MORE INFORMATION: See the section on
11790 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11792 <End of help on this topic>
11795 ===== h_folder_action_roles =====
11798 <TITLE>Folder Select Explained</TITLE>
11801 This screen is designed to allow you to quickly and easily survey your
11802 folders and select one to use as the folder into which messages
11803 matching this filter will be moved.
11806 <!--chtml if pinemode="function_key"-->
11808 Navigating the List of Folders General Alpine Commands
11809 ------------------------------ -----------------------
11810 F5 Move to previous folder F1 Show this help text
11811 F6 Move to next folder
11812 F7 Show previous screen of folders
11813 F8 Show next screen of folders
11814 F12 WhereIs (search folder names)
11816 Folder Selection Commands
11817 -------------------------
11818 F3 Exit the Folder Select menu (without selecting a folder)
11819 F4 Select the currently highlighted folder
11820 F11 AddNew folder (just like Select, but you type in a new folder name)
11824 Navigating the List of Folders General Alpine Commands
11825 ------------------------------ -----------------------
11826 P Move to previous folder ? Show this help text
11827 N Move to next folder
11828 - Show previous screen of folders
11829 Spc (space bar) Show next screen of folders
11830 W WhereIs (search folder names)
11832 Folder Selection Commands
11833 -------------------------
11834 E Exit the Folder Select menu (without selecting a folder)
11835 S Select the currently highlighted folder
11836 A AddNew folder (just like Select, but you type in a new folder name)
11840 FOR MORE INFORMATION: See the section on
11841 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11843 <End of help on this topic>
11846 ===== h_abook_config =====
11849 <TITLE>SETUP ADDRESS BOOKS SCREEN</TITLE>
11852 <H1>SETUP ADDRESS BOOKS SCREEN</H1>
11853 <H2>SETUP ADDRESS BOOKS COMMANDS</H2>
11854 <!--chtml if pinemode="function_key"-->
11857 -------------------------------
11859 F3 Back to MAIN Alpine menu
11860 F4 Change configuration for address book
11861 F5 Move to previous address book
11862 F6 Move to next address book
11863 F7 Previous page of address books
11864 F8 Next page of address books
11865 F9 Add new address book
11866 F10 Delete existing address book
11867 F11 Shuffle the order of address books
11868 F12 Whereis (search address book titles)
11872 Navigation General Alpine Commands
11873 ----------------------- -----------------------
11874 P Prev Address Book ? Display this help text
11875 N Next Address Book E Back to MAIN Alpine menu
11877 Spc (space bar) Next page
11878 W WhereIs (search for word in address book titles)
11880 Setup Address Books Commands
11881 ------------------------------------------------
11882 A Add new address book $ Shuffle the order of address books
11883 D Delete existing address book C Change configuration for address book
11887 <H2>Description of the Setup Address Books Screen</H2>
11889 This screen lets you add, delete, modify, or change the order of your
11890 address books. The "Add Abook" command brings up a blank form to
11891 fill in. If you are adding a remote address book on an IMAP server
11892 you should fill in the name of the IMAP server. Otherwise, leave
11893 that field blank. (Note that remote IMAP address books are an Alpine
11894 concept and are unlikely to interoperate with other mail clients.)
11895 For a remote address book, fill in the name of the remote folder
11896 in the Folder field. This should be a folder that is used only for
11897 this one purpose, not a general purpose folder you expect to store
11899 <P>If you are adding a local address book, fill in the
11900 Folder Name field with a local file name (e.g., .addressbook).
11902 <B>Please note:</B> Remote address books stored on an IMAP server are
11903 of an entirely different format (namely, a special-purpose
11904 "mail folder") than that of the local addressbook familiar
11905 to Alpine users. Therefore,
11906 you cannot use "add a remote address book" to make an existing
11907 Alpine .addressbook file you may have on a remote IMAP server accessible to
11908 Alpine running on a different host.
11911 The "Del Abook" command allows you to remove an address book
11912 from your configuration. It will also ask you if you wish to remove
11913 the data for that address book, which would erase all traces of the
11914 address book if you answer Yes.
11917 The "Change" command is similar to the "Add Abook" command.
11918 The difference is that instead of adding a new address book to your
11919 configuration, you are changing the configuration of an existing entry.
11920 For example, you might want to correct a typing error or change a
11921 nickname. The "Change" command is not a move command. If you
11922 change the folder name or server name the data will not be moved for you.
11925 The "Shuffle" command is used for two purposes. If you shuffle
11926 an address book toward another address book in the same group then
11927 the order of those two address books will be swapped. If you shuffle
11928 the last Personal address book down towards the Global address book
11929 section, it will become a Global address book. If you shuffle
11930 the first Global address book up it will become a Personal address
11931 book. The main difference between Personal and Global address
11932 books is that Global address books are forced read-only.
11934 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11937 <End of help on this topic>
11940 ===== h_abook_top =====
11943 <TITLE>ADDRESS BOOK LIST COMMANDS</TITLE>
11946 <H1>ADDRESS BOOK LIST COMMANDS</H1>
11947 <!--chtml if pinemode="function_key"-->
11949 Available Commands -- Group 1 Available Commands -- Group 2
11950 ------------------------------- ------------------------------
11951 F1 Show Help Text F1 Show Help Text
11952 F2 See commands in next group F2 See commands in next group
11953 F3 Exit to MAIN MENU F3 Quit Alpine
11954 F4 View/Edit selected address book
11955 F5 Move to previous address book F5 FOLDER LIST screen
11956 F6 Move to next address book F6 Specify a folder to go to
11957 F7 Previous page F7 MESSAGE INDEX screen
11958 F8 Next page F9 Print list of address books
11959 F12 Whereis (search for word)
11963 Navigation General Alpine Commands
11964 ----------------------- -----------------------
11965 P Previous Entry ? Display this help text
11966 N Next Entry O Show all other available commands
11967 - Previous page < Back to MAIN Alpine menu
11968 Spc (space bar) Next page Q Quit Alpine
11969 W WhereIs (search for word) L FOLDER LIST screen
11970 G Specify a folder to go to
11971 Address Book Commands I MESSAGE INDEX screen
11972 ------------------------------------------------
11973 > View/Edit selected address book
11975 > Search on selected directory server
11977 % Print list of address books and directory servers
11981 <H2>Description of the Address Book List Screen</H2>
11983 From this screen you may choose which address book you wish to view
11984 or edit. For more information on address books, view one of your
11985 address books (with
11986 <!--chtml if pinemode="function_key"-->
11990 <!--chtml endif-->)
11991 and see the Help Text there.<P>
11993 You may also choose a directory server on which to search for entries.
11994 You do that by highlighting the directory server line and using
11995 <!--chtml if pinemode="function_key"-->
11999 <!--chtml endif-->.<P>
12001 If you wish to define new address books or directory servers go to the Main
12002 menu and choose Setup. You may then either choose to setup AddressBooks or
12003 Directory (among other things). It's possible that the Directory option
12004 will not be there if the Alpine you are using does not contain LDAP directory
12005 lookup functionality.
12008 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
12010 <End of help on this topic>
12013 ===== h_abook_opened =====
12016 <TITLE>THE ALPINE ADDRESS BOOK</TITLE>
12019 <H1>THE ALPINE ADDRESS BOOK</H1>
12020 <H2>ADDRESS BOOK COMMANDS</H2>
12022 <!--chtml if pinemode="function_key"-->
12023 Available Commands -- Group 1 Available Commands -- Group 2
12024 ------------------------------- ------------------------------
12025 F1 Show Help Text F1 Show Help Text
12026 F2 See commands in next group F2 See commands in next group
12027 F3 Exit this screen F3 Quit Alpine
12028 F4 View/Edit selected entry F4 Go to MAIN MENU screen
12029 F5 Move to previous entry F5 FOLDER LIST screen
12030 F6 Move to next entry F6 Specify a folder to go to
12031 F7 Previous page of address book F7 MESSAGE INDEX screen
12032 F8 Next page of address book F8 Compose to entry using roles
12033 F9 Add new entry to address book F9 Print address book
12034 F10 Delete selected entry F10 TakeAddr to another addrbook
12035 F11 Compose to selected entry F11 Save or Export addrbook selections
12036 F12 Whereis (search address book) F12 Forward entry by mail
12038 Available Commands -- Group 3
12039 ------------------------------
12040 F3 Select F6 Zoom (or unZoom)
12041 F5 Select Current F7 Apply Command to Selection
12043 Address Book Navigation General Alpine Commands
12044 ----------------------- -----------------------
12045 P Prev Address ? Display this help text
12046 N Next Address O Show all other available commands
12047 - Previous page of address book M Back to MAIN MENU
12048 Spc (space bar) Next page Q Quit Alpine
12049 W WhereIs (search for word C Compose message to selected addr
12050 or name in address book) # Compose to addr using roles
12051 < To List of Address Books if L FOLDER LIST screen
12052 more than one, else to MAIN G Specify a folder to go to
12053 I MESSAGE INDEX screen
12055 Address Book Commands
12056 ----------------------------------------------------
12057 > View/Update selected entry D Delete selected entries
12058 % Print address book S Save or Export address book selections
12059 F Forward entries by mail @ Add new entry to address book
12061 ; Select command Z Toggle Zoom Mode
12062 : Select highlighted entry A Apply command to selected entries
12066 Note: The presence or absence of the final four commands above is
12067 controlled by the option
12068 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>.
12071 <H2>Description of the Address Book Screen</H2>
12073 This screen lets you edit and manage entries in your address book. It
12074 also acts as a short-cut for composing messages to people in the address
12075 book. When, from this screen, you press <!--chtml if pinemode="function_key"-->F11<!--chtml else-->"C"<!--chtml endif--> for ComposeTo, the
12076 message starts "pre-addressed" to whatever address book entry is
12077 currently selected. If you use the <!--chtml if pinemode="function_key"-->F8<!--chtml else-->"#"<!--chtml endif--> for Role, you may first select a
12078 role to use in your composition.
12080 Alpine's address book helps you keep a list of addresses you send email to so
12081 you do not have to remember addresses that are often complex. Each entry
12082 in the address book has five fields, all of them optional. The three
12083 elements that are usually visible on the ADDRESS BOOK display, are: <DL>
12085 <P><DT>NICKNAME: <DD>A short easy-to-remember label to identify the entry.
12086 This is what you type in as you are addressing the message in the
12087 composer. If there is a matching entry in your address book(s),
12088 Alpine will extract the corresponding FullName and Address fields to
12089 generate the actual address for your message.
12091 <P><DT>FULLNAME: <DD>A longer field where you can put the full name
12093 person or organization. Usually the full names are put in last
12094 name first so they sort nicely in alphabetical order. Whatever
12095 you put as the name here will appear on the message when it is
12096 finally delivered. Examples:<PRE>
12097 Garcia Marquez, Gabriel
12099 Alpine-Info mailing list
12100 Library materials renewal requests
12102 "George III, King of Great Britain, 1738-1820"
12104 (In the second-to-last example, no comma is used in the name so that
12105 the family name appears first in the address book and when the entry is
12106 used in the composer.
12107 In the last example, retaining the commas is intended;
12108 double-quotation marks surround the name to
12109 prevent the transposition of its parts when the entry is used in
12112 <P><DT>ADDRESS: <DD>This is the actual email address itself. This must be
12113 a valid Internet address that conforms to the Internet message
12114 header standard, RFC-822. (See also <A HREF="h_address_format">Explanation of Address formats</A>.)</DL>
12116 The two fields that aren't usually visible are:<DL>
12118 <P><DT>FCC: <DD>The name of the folder you would like a copy of any outgoing
12119 message to this address to be saved in. If this field is set, and
12120 this address is the first one in the message's To: header, then
12121 Alpine will use this folder name for the FCC in lieu of the normal
12124 <P><DT>COMMENTS: <DD>This field contains arbitrary text for your convenience.
12127 Due to screen width limitations, these last two fields do not show up in
12128 the normal ADDRESS BOOK display. You may select the
12129 "View/Update" command to
12130 view or modify them. You may use the configuration variable
12131 <A HREF="h_config_abook_formats">"<!--#echo var="VAR_addressbook-formats"-->"</A>
12132 to add these fields to your ADDRESS BOOK
12133 display, or to modify the format of the display.
12135 <H2>Sorting the Address book</H2>
12137 By default, address book entries are sorted alphabetically on the full
12138 name with distribution lists sorted to the end. Sorting can be changed by
12139 resetting the address book sort rule in the Alpine SETUP CONFIGURATION screen
12140 --assuming you have "write" permission for the address book file.
12142 Unlike the sorting of folders (which only changes presentation), sorting an
12143 address book actually changes the file as it is kept on the computer. For
12144 this reason you won't be able to sort a shared or system-wide address
12147 <H2>Adding New Entries</H2>
12149 The easiest way to add new entries to your address book is to use the
12150 "TakeAddr" command when viewing a message.
12151 This command allows you to take addresses from the header and body of the
12152 message and put them into your address book, without having to type
12156 To manually add a new entry from within the address book screen, use the AddNew
12157 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->"@"<!--chtml endif-->) command.
12158 Use this command both for adding a simple alias and for adding a
12161 <H2>Distribution Lists</H2>
12163 Address book entries can be simple cases of aliases (a single nickname is linked
12164 to a single email address) or distribution lists (a single nickname
12165 pointing at more than one email address). Each distribution list has a
12166 nickname, a full name and a list of addresses. The addresses may be
12167 actual addresses or they may be other nicknames in your address book.
12168 They may even refer to other distribution lists.
12169 There's really no difference between a simple alias and a distribution list,
12170 other than the number of addresses.
12171 Therefore, you can turn a simple alias with one address into a distribution
12172 list simply by adding more addresses.
12173 To add entries to an existing list or alias
12174 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
12175 a single address from the list if the cursor is placed on the address;
12176 it will delete the entire distribution list if the cursor is on the
12177 nickname/fullname line. View/Update may also be used to delete addresses
12180 Address field entries in distribution lists may take any one of three
12181 forms: a nickname existing in any of the defined address books, a normal
12182 address of the form "jsmith@art.example.com", or a complete
12183 fullname/address combination, e.g. "John Smith
12184 <jsmith@art.example.com>".
12186 Distribution lists in Alpine address books can only be used by the person or
12187 people who have access to that address book. They are not usually used to
12188 implement discussion groups, but can be used to facilitate small
12189 discussion groups if all the participants have access to the same shared
12192 <H2>FCC and Comments</H2>
12194 As mentioned above, each entry in the address book also has two other optional
12195 fields, Fcc and Comments. The command to look at or change either of these
12196 is the same View/Update command used for all of the fields (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->">"<!--chtml endif-->). The
12197 Comments field is just for your own use. The Fcc field overrides the
12198 default Fcc if this address is the first one on the To line. The WhereIs
12199 command may be used to search for particular strings in the address book,
12200 including fields that are not visible (like Comment and Fcc by default).
12202 <H2>Aggregate Operations</H2>
12205 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
12206 is turned on (the default), then the four commands "Select",
12207 "Select Current", "Zoom", and "Apply"
12208 are available. The two selection commands allow you to mark a set of
12209 address book entries as being selected. If you have more than one address
12210 book, the selections may be in more than one of those address books.
12211 The "Zoom" command will toggle between displaying only the selected
12212 entries and all of the entries. The "Apply" command allows you to
12213 apply one of the regular address book commands to all of the selected
12214 entries. Usually the address book commands apply to only the entry
12215 highlighted by the cursor. The "Apply" command works with the
12216 commands "ComposeTo", "Delete", "Print",
12217 "Save", "Forward", and "Role".
12219 <H2>Exporting and Forwarding Address book entries</H2>
12221 Under the save option, when you use the Export (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->"X"<!--chtml endif-->) command, the currently highlighted
12222 address book entry is placed in a plain text file in your home directory
12223 <!--chtml if pinemode="running"-->
12224 (which, in the present configuration of your system, is
12225 "<!--#echo var="HOME_DIR"-->")
12227 or current working directory
12228 <!--chtml if pinemode="running"-->
12229 (which, at least for your current Alpine "session,"
12230 is "<!--#echo var="CURRENT_DIR"-->")
12231 <!--chtml endif-->, depending on the
12232 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
12233 configuration setting. If you have some entries selected and use the
12234 Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Export command, all of the selected addresses will be
12235 placed in the text file.
12237 When you use the Forward (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->"F"<!--chtml endif-->) command, the currently highlighted
12238 address book entry is placed in a special attachment and you are put into
12239 the composer. You can fill in some comments in the body of the message,
12240 if you'd like, and send it to somebody else who uses Alpine. The recipient
12241 may use the TakeAddr command on that message to insert the address book
12242 entry you sent in their own address book. If you have some entries
12243 selected and use the Apply Forward command all of the selected entries
12244 will be forwarded in a single message. You may
12245 use Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Forward to forward a copy of an entire address book.
12246 The recipient must be using Alpine in order to receive this correctly.
12247 One way for the recipient to handle this might be to create an empty
12248 address book and then "Take" your forwarded address book entries into
12249 that empty address book.
12251 <H2>Multiple and/or Site-Wide Address books</H2>
12253 You may have more than one personal address book. In addition, there may
12254 be one or more global address books. This capability allows you to have
12255 multiple personal address books (some of which may be shared) and it also
12256 allows system administrators to implement site-wide address books that
12257 contain entries for users on multiple machines within the organization.
12260 <DD> If you enter a nickname when composing a message, your
12261 personal address books will be searched through in order, and then the
12262 global address book(s) searched. If more than one address book has an entry
12263 for the nickname, Alpine uses the first one that it finds, so an entry in
12264 your personal address book would override a global address book entry. If
12265 after searching all the address books there is still no match, (Unix) Alpine
12266 then searches the local host password file on the assumption that you have
12267 entered a local user name rather than an address book nickname.
12268 You may change the search order of your address books with the <!--chtml if pinemode="function_key"-->F3<!--chtml else-->$<!--chtml endif--> Shuffle
12269 command, but global address books are always searched after personal
12272 <P><DT>Tab completion
12274 <A HREF="h_config_enable_tab_complete"><!--#echo var="FEAT_enable-tab-completion"--></A>
12275 feature is turned on (the default) then the Tab key may be used
12276 in the composer to complete partially typed nicknames in the To
12277 or Cc lines. You type the first few letters of a nickname and then
12278 press the Tab key. It there is only one nickname that matches it will
12279 be filled in by Alpine. If there is more than one the unambiguous part
12280 of the nicknames will be filled in. For example, if your address book or
12281 books contains only the two entries "barley" and "barbecue"
12282 beginning with the letters "ba", then if you type "ba"
12283 followed by a Tab character Alpine will fill in "bar" and stop.
12284 If you then type a second Tab character you will be presented with a list
12285 of matching nicknames to select from. Alternatively, you could type another
12286 "b" resulting in "barb" and then a Tab would fill
12287 in the entire "barbecue" entry.
12290 <DD> You define multiple personal address books in the
12291 <A HREF="h_abook_config">SETUP AddressBooks</A> screen, which you may reach
12292 from the MAIN MENU.
12293 You may add as many as you like. Global address books are usually
12294 site-wide address books defined by the System administrator, but
12295 you may define global address books of your own just like you define
12296 personal address books.
12298 <P><DT>Creating and updating
12299 <DD> Personal address books are normally created empty
12300 and populated by explicit additions from within Alpine, e.g. via the
12301 TakeAddr command. Unlike personal address books, global address books may
12302 not be modified/updated from within Alpine; that is, they are Read-Only.
12303 Thus, global address books are created, populated and updated outside of
12304 Alpine. They might be hand-edited, generated by a program from another
12305 database, or by copying an existing address book. They might also be
12306 some other user's personal address book, and so be modified normally by
12307 that user but accessed Read-Only by you. See the Alpine Technical
12308 Notes document (included in the Alpine distribution) for more information on
12312 <DD>There are two different types of address books in Alpine.
12313 A local address book is stored in a regular file and the normal file
12314 access permissions apply. A remote address book is stored on an IMAP
12315 server in a special folder that contains only messages pertaining to
12316 that address book. The last message in the remote folder contains a
12317 copy of the address book data, and that data is copied to a local cache
12318 file in your home directory. From there it is accessed just like a local
12319 address book. The name of the cache file is kept track of in a special
12321 <A HREF="h_config_abook_metafile"><!--#echo var="VAR_remote-abook-metafile"--></A>,
12322 the name of which is stored in
12323 your Alpine configuration file the first time you use a remote address book.
12324 Just as local Alpine address books use a format that only Alpine understands,
12325 remote Alpine address books do the same and other mail reading programs
12326 are unlikely to be able to understand them.<P>
12327 While global address books are explicitly intended to be shared, there is
12328 nothing to prevent you from sharing a personal address book with other
12329 Alpine users. This might be useful in the case of a small workgroup.
12330 However, it is recommended that updates to shared personal address books
12331 be done when other Alpine users are not accessing the address book. Alpine
12332 does not do any file-locking to manage concurrent updates to the
12333 addressbook, but it does check to see if the file has been modified before
12334 making any changes. Consequently, inadvertent concurrent updates will
12335 only cause other Alpine users to have to restart their address book
12336 operation, which will cause Alpine to reopen the updated file.
12338 <P><DT>Converting to Remote
12339 <DD>The easiest way to convert an existing local
12340 address book into a remote address book is to create an empty new remote
12341 personal address book by typing "A" to execute the
12342 "Add Pers Abook" command in the SETUP Addressbook screen.
12343 Make sure you add a <EM>personal</EM> address book, not a <EM>global</EM>
12345 After you have added the empty
12346 remote address book, go into the screen for the address book you wish
12347 to copy and "Select" "All".
12348 This selects every entry in that
12349 address book. Then type the command "Apply Save".
12350 You will be asked for the address book to save to. You may use ^P and ^N
12351 to get to the new empty address book, then hit RETURN and the addresses
12353 At this point you'll probably want to unselect all the entries in the local
12354 address book before proceeding. You do that with
12355 "Select" "unselect All".
12359 <LI><A HREF="h_address_format">Explanation of Address formats</A>
12362 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
12365 <End of help on this topic>
12368 ===== h_abook_select_addr =====
12371 <TITLE>Addressbook Selection Explained</TITLE>
12374 <H1>SELECT ADDRESS</H1>
12375 <!--chtml if pinemode="function_key"-->
12377 Navigating the List of Messages General Alpine Commands
12378 ------------------------------- -----------------------
12379 F5 Move to previous entry F1 Show this help text
12380 F6 Move to next entry
12381 F7 Show previous screen of address book
12382 F8 Show next screen of address book
12383 F12 WhereIs (search through address book)
12385 Address Selection Commands
12386 --------------------------
12387 F3 Exit the Address Select screen (without selecting an address)
12388 F4 Select the currently highlighted entry
12392 Navigating the List of Messages General Alpine Commands
12393 ------------------------------- -----------------------
12394 P Move to previous entry ? Show this help text
12395 N Move to next entry
12396 - Show previous screen of address book
12397 Spc (space bar) Show next screen of address book
12398 W WhereIs (search through address book)
12400 Address Selection Commands
12401 --------------------------
12402 E Exit the Address Select screen (without selecting an address)
12403 S Select the currently highlighted entry
12408 This screen is designed to let you easily scan your address book(s) in
12409 order to select an entry for the message you are composing. You cannot
12410 edit your address book in any way at this time, for address book
12411 maintenance, select the address book command when not composing a message.
12414 If you are composing a message and know the nickname of the person/list you
12415 want, you can bypass this screen by simply typing in the nickname on the
12416 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12417 selecting an entry does not cancel your message.
12420 FOR MORE INFORMATION on addressing see
12421 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12422 <A HREF="h_abook_opened">Address Book Screen's</A>
12425 <End of help on this topic>
12428 ===== h_abook_select_top =====
12431 <TITLE>Addressbook Selection Navigation Explained</TITLE>
12434 <H1>NAVIGATING WHILE SELECTING ADDRESSES</H1>
12435 <!--chtml if pinemode="function_key"-->
12437 Navigating the List of Address Books General Alpine Commands
12438 ------------------------------------ -----------------------
12439 F4 View the highlighted address book
12440 F5 Move to previous address book F1 Show this help text
12441 F6 Move to next address book
12442 F7 Show previous screen of address books
12443 F8 Show next screen of address books
12444 F12 WhereIs (search through address books)
12446 Address Selection Commands
12447 --------------------------
12448 F3 Exit the Address Select screen (without selecting an address)
12449 F4 Select the currently selected entries (if using ListMode)
12450 F9 Change to ListMode
12454 Navigating the List of Address Books General Alpine Commands
12455 ------------------------------------ -----------------------
12456 > View the highlighted address book
12457 P Move to previous address book ? Show this help text
12458 N Move to next address book
12459 - Show previous screen of address books
12460 Spc (space bar) Show next screen of address books
12461 W WhereIs (search through address books)
12463 Address Selection Commands
12464 --------------------------
12465 E Exit the Address Select screen (without selecting an address)
12466 S Select the currently selected entries (if using ListMode)
12467 L Change to ListMode
12472 This screen is designed to let you easily scan your address book(s) in
12473 order to select entries for the message you are composing. You cannot
12474 edit your address book in any way at this time. For address book
12475 maintenance, select the address book command when not composing a message.
12478 If you are composing a message and know the nickname of the person/list you
12479 want, you can bypass this screen by simply typing in the nickname on the
12480 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12481 selecting an entry does not cancel your message.
12484 The ListMode command will add a column at the left edge of the screen.
12485 You mark the entries that you wish to select with the "X" command.
12486 This allows you to choose more than one entry at a time.
12489 An alternative method of composing a message to entries in your
12490 address book(s) is to first use the "Select" command from
12491 the address book maintenance screen and then the "Apply"
12492 "ComposeTo" command to start the composer composing to the
12496 FOR MORE INFORMATION on addressing see
12497 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12498 <A HREF="h_abook_opened">Address Book Screen's</A>
12501 <End of help on this topic>
12504 ===== h_abook_select_listmode =====
12507 <TITLE>Address Listmode Selection from Composer Explained</TITLE>
12510 <H1>COMPOSER: SELECT ADDRESSES</H1>
12511 <!--chtml if pinemode="function_key"-->
12513 Navigating the List of Messages General Alpine Commands
12514 ------------------------------- -----------------------
12515 F5 Move to previous entry F1 Show this help text
12516 F6 Move to next entry
12517 F7 Show previous screen of address book
12518 F8 Show next screen of address book
12519 F12 WhereIs (search through address book)
12521 Address Selection Commands
12522 --------------------------
12523 F3 Exit the Address Select screen (without selecting an address)
12524 F4 Select the currently highlighted entry
12525 F9 Change to ListMode
12529 Navigating the List of Messages General Alpine Commands
12530 ------------------------------- -----------------------
12531 P Move to previous entry ? Show this help text
12532 N Move to next entry
12533 - Show previous screen of address book
12534 Spc (space bar) Show next screen of address book
12535 W WhereIs (search through address book)
12537 Address Selection Commands
12538 --------------------------
12539 E Exit the Address Select screen (without selecting an address)
12540 S Select the currently highlighted entry
12541 L Change to ListMode
12546 This screen is designed to let you easily scan your address book(s) in
12547 order to select entries for the message you are composing. You cannot
12548 edit your address book in any way at this time, for address book
12549 maintenance, select the address book command when not composing a message.
12552 If you are composing a message and know the nickname of the person/list you
12553 want, you can bypass this screen by simply typing in the nickname on the
12554 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12555 selecting an entry does not cancel your message.
12558 The ListMode command will add a column at the left edge of the screen.
12559 You mark the entries that you wish to select with the "X" command.
12560 This allows you to choose more than one entry at a time.
12563 An alternative method of composing a message to entries in your
12564 address book(s) is to first use the "Select" command from
12565 the address book maintenance screen and then the "Apply"
12566 "ComposeTo" command to start the composer composing to the
12570 FOR MORE INFORMATION on addressing see
12571 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12572 <A HREF="h_abook_opened">Address Book Screen's</A>
12575 <End of help on this topic>
12578 ===== h_abook_select_checks =====
12581 <TITLE>Address Selection from Composer Explained</TITLE>
12584 <H1>COMPOSER: SELECT ADDRESSES</H1>
12585 <!--chtml if pinemode="function_key"-->
12587 Navigating the List of Messages General Alpine Commands
12588 ------------------------------- -----------------------
12589 F5 Move to previous entry F1 Show this help text
12590 F6 Move to next entry
12591 F7 Show previous screen of address book
12592 F8 Show next screen of address book
12593 F12 WhereIs (search through address book)
12595 Address Selection Commands
12596 --------------------------
12597 F3 Exit the Address Select screen (without selecting an address)
12598 F4 Select the currently highlighted entry
12599 F8 Either Sets or Unsets all entries in this address book
12600 F9 Set or Unset the highlighted entry
12604 Navigating the List of Messages General Alpine Commands
12605 ------------------------------- -----------------------
12606 P Move to previous entry ? Show this help text
12607 N Move to next entry
12608 - Show previous screen of address book
12609 Spc (space bar) Show next screen of address book
12610 W WhereIs (search through address book)
12612 Address Selection Commands
12613 --------------------------
12614 E Exit the Address Select screen (without selecting an address)
12615 S Select the currently highlighted entry
12616 X Set or Unset the highlighted entry
12617 A Either Sets or Unsets all entries in this address book
12622 Mark the entries you wish to select with the "X Set/Unset"
12623 command. Type "S Select" to select all of the entries you
12624 have marked, just as if you had typed them in by hand.
12627 An alternative method of composing a message to entries in your
12628 address book(s) is to first use the "Select" command from
12629 the address book maintenance screen and then the "Apply"
12630 "ComposeTo" command to start the composer composing to the
12634 FOR MORE INFORMATION on addressing see
12635 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12636 <A HREF="h_abook_opened">Address Book Screen's</A>
12639 <End of help on this topic>
12642 ===== h_abook_select_nicks_take =====
12645 <TITLE>Take Address Nickname Selection Explained</TITLE>
12648 <H1>TAKEADDR: SELECT NICKNAME</H1>
12649 <!--chtml if pinemode="function_key"-->
12651 Navigating the List of Messages General Alpine Commands
12652 ------------------------------- -----------------------
12653 F5 Move to previous entry F1 Show this help text
12654 F6 Move to next entry
12655 F7 Show previous screen of address book
12656 F8 Show next screen of address book
12657 F12 WhereIs (search through address book)
12659 Message Selection Commands
12660 --------------------------
12661 F3 Exit the Nickname Select screen (without selecting an address)
12662 F4 Select the currently highlighted entry
12666 Navigating the List of Messages General Alpine Commands
12667 ------------------------------- -----------------------
12668 P Move to previous entry ? Show this help text
12669 N Move to next entry
12670 - Show previous screen of address book
12671 Spc (space bar) Show next screen of address book
12672 W WhereIs (search through address book)
12674 Message Selection Commands
12675 --------------------------
12676 E Exit the Nickname Select screen (without selecting an address)
12677 S Select the currently highlighted entry
12682 This screen is designed to let you modify or add to an existing
12683 address book entry. You have already selected the name(s) and
12684 address(es) through "Take Address". This screen simply lets
12685 you scan your address books and select the nickname to be
12686 changed/augmented. If you want to add a new entry, then you are in
12687 the wrong place-- Select "Exit" command.
12690 FOR MORE INFORMATION on addressing see
12691 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12692 <A HREF="h_abook_opened">Address Book Screen's</A>
12695 <End of help on this topic>
12698 ===== h_abook_select_nick =====
12701 <TITLE>Nickname Selection Explained</TITLE>
12704 <H1>SELECT NICKNAME</H1>
12705 <!--chtml if pinemode="function_key"-->
12707 Navigating the List of Messages General Alpine Commands
12708 ------------------------------- -----------------------
12709 F5 Move to previous entry F1 Show this help text
12710 F6 Move to next entry
12711 F7 Show previous screen of address book
12712 F8 Show next screen of address book
12713 F12 WhereIs (search through address book)
12715 Message Selection Commands
12716 --------------------------
12717 F3 Exit the Nickname Select screen (without selecting an address)
12718 F4 Select the currently highlighted entry
12722 Navigating the List of Messages General Alpine Commands
12723 ------------------------------- -----------------------
12724 P Move to previous entry ? Show this help text
12725 N Move to next entry
12726 - Show previous screen of address book
12727 Spc (space bar) Show next screen of address book
12728 W WhereIs (search through address book)
12730 Message Selection Commands
12731 --------------------------
12732 E Exit the Nickname Select screen (without selecting an address)
12733 S Select the currently highlighted entry
12738 This screen is designed to let you look at the nicknames in your address
12739 books before choosing a new one.
12742 FOR MORE INFORMATION on addressing see
12743 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12744 <A HREF="h_abook_opened">Address Book Screen's</A>
12747 <End of help on this topic>
12750 ===== h_takeaddr_screen =====
12753 <TITLE>Take Address Screen Explained</TITLE>
12756 <H1>TAKE ADDRESS COMMANDS</H1>
12757 <!--chtml if pinemode="function_key"-->
12759 Navigating the List of Addresses Address Selection Commands
12760 -------------------------------- --------------------------
12761 F5 Move to previous entry F3 Exit without taking address
12762 F6 Move to next entry F4 Take current address(es)
12763 F7 Show previous page of address list
12764 F8 Show next page of address list
12765 F2 WhereIs (search list)
12767 Mode Toggle F9 Set/Unset current address
12768 ----------- F10 Set all
12769 F12 Toggle between List and single mode F11 Unset all
12773 Navigating the List of Addresses Address Selection Commands
12774 -------------------------------- --------------------------
12775 P Move to previous entry < Exit without taking address
12776 N Move to next entry T Take address
12777 - Show previous page of address list
12778 Spc (space bar) Show next page of address list
12779 W WhereIs (search list) List Mode
12781 Single Mode X Set/Unset current address
12782 ----------- A Set all addresses
12783 L Switch to list mode U Unset all addresses
12784 S Switch to single mode
12788 <H2>Description of the Take Address Screen</H2>
12790 This screen is designed to let you select one or more address/name
12791 combinations from the current message and put them into your address book.
12792 The cursor is initially placed on the line with the message author.
12793 Other lines include the names of people and/or mailing lists who also
12794 received the message. Other people "involved" in the
12795 message (e.g. the person named as Reply-To:) are also listed here.
12798 The simple case is adding a new, single entry into your address book. To
12799 do this, simply highlight the correct line and press
12800 <!--chtml if pinemode="function_key"-->
12805 To create a new list or add to an existing list, switch the screen display
12806 into List Mode by pressing
12807 <!--chtml if pinemode="function_key"-->
12812 In List Mode, you select the
12813 group of addresses you wish to manipulate by marking them with an
12816 <!--chtml if pinemode="function_key"-->
12821 command will turn the "X" on for the
12822 highlighted address if it was off or turn it off if it was previously on.
12823 The SetAll command will select all of the addresses, and the UnSetAll
12824 command will turn off all the selections. Once you've gotten the
12825 selection the way you want it, you may create a new list by pressing
12826 <!--chtml if pinemode="function_key"-->
12833 In both the simple and list cases, after choosing to take the address,
12834 you will be asked for the nickname of the entry. Typing in a new name
12835 creates the new entry/list. Entering an existing nickname will replace
12836 the entry (simple case) or add to the list (list case). Alternatively,
12837 you can press Ctrl-T at the nickname prompt and select an existing
12838 nickname from your address book.
12841 You will normally start in Single Mode, unless you used the Apply command
12842 to startup the TakeAddr screen, in which case you will start in List Mode.
12843 You may switch between the two modes at any time. If you've already
12844 selected several addresses in List Mode, those will be remembered when you
12845 switch to Single Mode and then back to List Mode. The set of addresses
12846 that are pre-selected when you start in List Mode are the From addresses
12847 of all of the messages you are operating on. You may, of course, easily
12848 erase those selections with the UnSetAll command.
12851 If you have more than one writable address book, you will be prompted for
12852 the name of the address book you wish to add the new entry to before
12853 anything else. You can use ^N and ^P to choose among the defined address
12854 books, or type in the address book name.
12857 FOR MORE INFORMATION on addressing see
12858 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12859 <A HREF="h_abook_opened">Address Book Screen's</A>
12862 <End of help on this topic>
12865 ===== h_takeexport_screen =====
12868 <TITLE>Take Export Screen Explained</TITLE>
12871 <H1>TAKE EXPORT COMMANDS</H1>
12872 <!--chtml if pinemode="function_key"-->
12874 Navigating the List of Addresses Address Selection Commands
12875 -------------------------------- --------------------------
12876 F5 Move to previous entry F3 Exit without taking address
12877 F6 Move to next entry F4 Take current address(es)
12878 F7 Show previous page of address list
12879 F8 Show next page of address list
12880 F2 WhereIs (search list)
12882 Mode Toggle F9 Set/Unset current address
12883 ----------- F10 Set all
12884 F12 Toggle between List and single mode F11 Unset all
12888 Navigating the List of Addresses Address Selection Commands
12889 -------------------------------- --------------------------
12890 P Move to previous entry < Exit without taking address
12891 N Move to next entry T Take address
12892 - Show previous page of address list
12893 Spc (space bar) Show next page of address list
12894 W WhereIs (search list) List Mode
12896 Single Mode X Set/Unset current address
12897 ----------- A Set all addresses
12898 L Switch to list mode U Unset all addresses
12899 S Switch to single mode
12903 <H2>Description of the Take Export Screen</H2>
12905 This screen is designed to let you select one or more addresses
12906 from the current message and put them into a file.
12907 Only the user@domain_name part of each address is put into the file.
12910 To put a single entry into a file simply highlight the correct line and press
12911 <!--chtml if pinemode="function_key"-->
12916 To put more than one entry into a file
12917 switch the screen display
12918 into List Mode by pressing
12919 <!--chtml if pinemode="function_key"-->
12924 In List Mode, you select the
12925 group of addresses you wish to manipulate by marking them with an
12928 <!--chtml if pinemode="function_key"-->
12933 command will turn the "X" on for the
12934 highlighted address if it was off or turn it off if it was previously on.
12935 The SetAll command will select all of the addresses, and the UnSetAll
12936 command will turn off all the selections. Once you've gotten the
12937 selection the way you want it, you may put the addresses in a file by typing
12938 <!--chtml if pinemode="function_key"-->
12945 You will be asked for the name of a file to put the addresses in.
12946 If the file already exists, you will be asked whether you want to Overwrite
12947 (replace) the contents of the file or Append to the contents of the file.
12950 <End of help on this topic>
12953 ============= h_abook_view ========================
12956 <TITLE>Address Book View Explained</TITLE>
12959 This function allows you to view the contents of an address book entry. You
12960 can only view one entry at a time.
12964 <!--chtml if pinemode="function_key"-->
12971 Display this help text.
12974 <!--chtml if pinemode="function_key"-->
12981 Go back to index of address book entries.
12984 <!--chtml if pinemode="function_key"-->
12991 Update (modify) this entry.
12994 <!--chtml if pinemode="function_key"-->
13000 <DD>Compose a message to the address(es) in this entry.
13003 <!--chtml if pinemode="function_key"-->
13009 <DD>Compose a message to the address(es) in this entry using roles.
13012 <!--chtml if pinemode="function_key"-->
13019 Show the previous page of the current entry.
13022 <!--chtml if pinemode="function_key"-->
13029 Show the next page of the current entry.
13032 <!--chtml if pinemode="function_key"-->
13038 <DD>Print the current entry. You can select the
13039 printer or the print command via the "Setup" command
13043 <!--chtml if pinemode="function_key"-->
13049 <DD>Search the entry for a string of letters. If it is
13050 found, move to it. The string can be one word or a phrase.
13051 If there are multiple occurrences, the cursor moves to the
13052 first occurrence beyond the current cursor position.
13055 <!--chtml if pinemode="function_key"-->
13061 <DD>Begin composition of a new mail message with the displayed
13062 text already inserted in the message body.
13066 <End of help on this topic>
13069 ============= h_ldap_view ========================
13072 <TITLE>LDAP Response View Explained</TITLE>
13075 This function allows you to view the contents of a directory entry. You
13076 can only view one entry at a time.
13080 <!--chtml if pinemode="function_key"-->
13087 Display this help text.
13090 <!--chtml if pinemode="function_key"-->
13096 <DD>Go back to index of search results.
13099 <!--chtml if pinemode="function_key"-->
13105 <DD>Compose a message to the address(es) in this entry.
13108 <!--chtml if pinemode="function_key"-->
13114 <DD>Compose a message to the address(es) in this entry using roles.
13117 <!--chtml if pinemode="function_key"-->
13124 Show the previous page of the current entry.
13127 <!--chtml if pinemode="function_key"-->
13134 Show the next page of the current entry.
13137 <!--chtml if pinemode="function_key"-->
13143 <DD>Print the current entry on paper. You can select the
13144 printer or the print command via the "Setup" command
13148 <!--chtml if pinemode="function_key"-->
13154 <DD>Search the entry for a string of letters. If it is
13155 found, move to it. The string can be one word or a phrase.
13156 If there are multiple occurrences, the cursor moves to the
13157 first occurrence beyond the current cursor position.
13160 <!--chtml if pinemode="function_key"-->
13166 <DD>Begin composition of a new mail message with the displayed
13167 text already inserted in the message body.
13170 <!--chtml if pinemode="function_key"-->
13176 <DD>Save the displayed entry to one of your address books or export
13180 <End of help on this topic>
13183 ===== h_attachment_screen =====
13186 <TITLE>Attachment Index Screen Explained</TITLE>
13189 The "ATTACHMENT INDEX" displays a list of the current
13190 message's attachments, and allows various operations on them. The
13191 first attachment is usually the message text, but does not include the
13192 header portion of the message.
13194 Available commands include:
13199 <DD>Show this help text.
13201 <DT>Msg #<I>num</I></DT>
13202 <DD>Leave this screen without displaying or saving any attachments.
13205 <DD>View the currently selected attachment.
13207 <DT>Prev Attach</DT>
13208 <DD>Move to previous attachment.
13210 <DT>Next Attach</DT>
13211 <DD>Move to next attachment.
13214 <DD>Previous page of the listed attachments.
13217 <DD>Next page of the listed attachments.
13220 <DD>Mark the currently selected attachment for Deletion.
13221 This does not modify the current message by deleting the attachment from
13222 it, but instead the delete flag <EM>only</EM> has an effect when saving
13223 the message to a folder.
13224 Attachments marked for deletion are not copied to the destination folder
13225 along with the rest of the message when it is saved.
13226 It is ok for the destination folder to be the same as the current folder.
13227 In addition, the delete mark <EM>only</EM> applies to this Alpine session.
13230 <DD>Turn off the Delete flag for the selected attachment.
13233 <DD>Save the selected attachment to a file. If the attachment is of
13234 type "RFC822/Message", then the attachment will be saved to
13235 the specified mail folder.
13238 <DD>If the attachment is of
13239 type "RFC822/Message", then "Export" is used to
13240 copy the message to a file in the same way this command works on
13241 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
13244 <DD>Pipe the attachment contents into a UNIX command (if enabled).
13245 A description of the Pipe sub-commands is <A HREF="h_pipe_command">here</A>.
13248 <DD>Find a matching string in the attachment list.
13250 <DT>AboutAttch</DT>
13251 <DD>Examine various aspects of the selected attachment.
13254 <DD>Print the selected attachment.
13257 <DD>Forward the selected attachment as an attachment.
13262 All attachments can be saved or piped into a UNIX command, but some may
13263 not be readily displayed by either Alpine or an external tool. In such
13264 cases, the reason why the message cannot be displayed is displayed on
13265 Alpine's message line.
13267 <End of help on this topic>
13270 ============= h_mail_text_att_view ========================
13273 <TITLE>Attachment View Screen Explained</TITLE>
13276 This function allows you to view the contents of a text attachment. You
13277 can only view one attachment at a time.
13279 Available commands include:
13284 <DD>Display this help text
13286 <DT>AttchIndex</DT>
13287 <DD>Leave viewer and return to the "ATTACHMENT INDEX" screen
13290 <DD>Show the previous page of the current attachment.
13293 <DD>Show the next page of the current attachment by pressing the space bar.
13296 <DD>Mark the viewed attachment for Deletion. The delete
13297 flag <EM>only</EM> has affect when saving the message to a folder.
13298 Attachments marked for deletion are exluded from the messsage when
13299 it is saved. In addition, the delete mark <EM>only</EM> applies to
13300 this Alpine session.
13303 <DD>Turn off the Delete flag for the selected attachment.
13306 <DD>Copy the current attachment to a file. If you just enter
13307 a filename, the attachment will be saved with that name in
13308 your home directory
13309 <!--chtml if pinemode="running"-->
13310 (which, in the present configuration of your system, is
13311 "<!--#echo var="HOME_DIR"-->")
13313 or current working directory
13314 <!--chtml if pinemode="running"-->
13315 (which, at least for your current Alpine "session,"
13316 is "<!--#echo var="CURRENT_DIR"-->")
13317 <!--chtml endif-->, depending on the
13318 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13319 configuration setting. You may enter the full
13320 path and filename to save it in another directory instead.
13323 <DD>If the attachment is of
13324 type "RFC822/Message", then "Export" is used to
13325 copy the message to a file in the same way this command works on
13326 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
13327 (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
13328 defined, they may affect the contents of the exported file.)
13331 <DD>Pipe the attachment contents into a UNIX command (if enabled)
13334 <DD>Search the attachment for a string of letters. If it is
13335 found, move to it. The string can be one word or a phrase.
13336 If there are multiple occurrences, the cursor moves to the
13337 first occurrence beyond the current cursor position.
13340 <DD>Print the current attachment on paper. You can select the
13341 printer or the print command via the "Setup" command
13345 <DD>Forward the selected attachment as an attachment.
13348 <End of help on this topic>
13351 ============= h_journal ==============
13354 <TITLE>Recent Message Journal Explained</TITLE>
13358 The following commands are available on this screen:
13362 <DD>Show this help text
13365 <DD>Exit Viewer, and go back to mail processing
13368 <DD>Show the previous page text
13371 <DD>Show the next page of text by pressing the space bar
13374 <DD>Print the displayed text on paper. You can select the
13375 printer or the print command via the "Setup" command
13379 <DD>Begin composition of a new mail message with the displayed
13380 text already inserted in the message body.
13383 <DD>Copy the displayed text to a file. If you just enter
13384 a filename, the text will be saved with that name in
13387 <!--chtml if pinemode="running"-->
13388 (which, in the present configuration of your system, is
13389 "<!--#echo var="HOME_DIR"-->")
13391 or current working directory
13392 <!--chtml if pinemode="running"-->
13393 (which, at least for your current Alpine "session,"
13394 is "<!--#echo var="CURRENT_DIR"-->")
13395 <!--chtml endif-->, depending on the
13396 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13397 configuration setting. You may enter the full
13398 path and filename to save it in another directory instead.
13401 <DD>Search the text for a string of letters. If it is
13402 found, move to it. The string can be one word or a phrase.
13403 If there are multiple occurrences, the cursor moves to the
13404 first occurrence beyond the current cursor position.
13407 <End of help on this topic>
13410 ============= h_debugjournal ==============
13413 <TITLE>Debug Journal Explained</TITLE>
13417 The following commands are available on this screen:
13421 <DD>Show this help text
13424 <DD>Exit Viewer, and go back to mail processing
13426 <DT>Timestamps</DT>
13427 <DD>Turn on or off timestamps.
13430 <DD>Set the level of debugging you want to see. The level may be any number
13431 in the range 0-9. Higher numbers show more debugging detail. Note that the
13432 debugging information has already been captured. This setting just causes the
13433 debugging information that you see to be filtered. If you set this to
13434 the number "5" then you will be shown all of the debugging information
13435 at levels 5 and below.
13436 It's actually a bit more complicated than that. A fixed amount of memory
13437 is used to store the debug information.
13438 Since the amount of memory used is limited the debugging information
13439 has to be trimmed back when it gets too large.
13442 <DD>Show the previous page text
13445 <DD>Show the next page of text by pressing the space bar
13448 <DD>Print the displayed text on paper. You can select the
13449 printer or the print command via the "Setup" command
13453 <DD>Begin composition of a new mail message with the displayed
13454 text already inserted in the message body.
13457 <DD>Copy the displayed text to a file. If you just enter
13458 a filename, the text will be saved with that name in
13461 <!--chtml if pinemode="running"-->
13462 (which, in the present configuration of your system, is
13463 "<!--#echo var="HOME_DIR"-->")
13465 or current working directory
13466 <!--chtml if pinemode="running"-->
13467 (which, at least for your current Alpine "session,"
13468 is "<!--#echo var="CURRENT_DIR"-->")
13469 <!--chtml endif-->, depending on the
13470 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13471 configuration setting. You may enter the full
13472 path and filename to save it in another directory instead.
13475 <DD>Search the text for a string of letters. If it is
13476 found, move to it. The string can be one word or a phrase.
13477 If there are multiple occurrences, the cursor moves to the
13478 first occurrence beyond the current cursor position.
13481 <End of help on this topic>
13484 ============= h_simple_text_view ==============
13487 <TITLE>Simple Text View Screen Explained</TITLE>
13491 The following commands are available on this screen:
13495 <DD>Show this help text
13498 <DD>Exit Viewer, and go back to mail processing
13501 <DD>Show the previous page text
13504 <DD>Show the next page of text by pressing the space bar
13507 <DD>Print the displayed text on paper. You can select the
13508 printer or the print command via the "Setup" command
13512 <DD>Begin composition of a new mail message with the displayed
13513 text already inserted in the message body.
13516 <DD>Copy the displayed text to a file. If you just enter
13517 a filename, the attachment will be saved with that name in
13520 <!--chtml if pinemode="running"-->
13521 (which, in the present configuration of your system, is
13522 "<!--#echo var="HOME_DIR"-->")
13524 or current working directory
13525 <!--chtml if pinemode="running"-->
13526 (which, at least for your current Alpine "session,"
13527 is "<!--#echo var="CURRENT_DIR"-->")
13528 <!--chtml endif-->, depending on the
13529 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13530 configuration setting. You may enter the full
13531 path and filename to save it in another directory instead.
13534 <DD>Search the attachment for a string of letters. If it is
13535 found, move to it. The string can be one word or a phrase.
13536 If there are multiple occurrences, the cursor moves to the
13537 first occurrence beyond the current cursor position.
13540 <End of help on this topic>
13543 ======= h_pine_for_windows ========
13546 <TITLE>GETTING HELP IN PC-ALPINE</TITLE>
13549 <H1>Getting Help In PC-Alpine</H1>
13552 PC-Alpine offers general and specific help text. From the <A
13553 HREF="main_menu_tx">MAIN MENU</A>, you will find an overview in the MAIN
13554 MENU HELP and the <A HREF="h_news">Release Notes</A>. On all screens,
13555 specific help for that screen is available from the toolbar Help menu or
13557 <!--chtml if pinemode="function_key"-->
13558 "F1" key.
13560 "?" or "Ctrl-G" keys. "Ctrl-G" is used where
13561 typing "?" would be mistaken as entering text.
13565 Although this version of Alpine is for Microsoft Windows, it is not
13566 considered a full "Graphical User Interface" application.
13567 Yet, many of the controls that Windows users are accustomed to seeing,
13568 such as scrollbars and toolbars, are available.
13571 PC-Alpine offers considerable mouse support. You can view what is
13572 "click-able" by dragging your mouse over any screen; when the
13573 arrow cursor changes into a hand, you found something. Mouse-click
13574 possibilities include navigating between screens and folders and
13575 double-clicking on hyperlinks to open your Web browser.
13576 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
13577 screen. Examples of right-click options include "copy" after
13578 selecting text to copy and "View in New Window" when you click
13579 on a particular message in the Message Index. The menu choices available
13580 to you will vary based upon what screen is open, where on the screen your
13581 cursor is located, and even what action you have already taken.
13584 <End of help on this topic>
13587 ===== h_composer =====
13590 <TITLE>COMPOSER COMMANDS</TITLE>
13593 <H1>COMPOSER COMMANDS</H1>
13595 CURSOR MOTION KEYS |EDITING KEYS<BR>
13596 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13597 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13598 ^P (Up Arrow) Previous line | ^^ Set a <A HREF="h_compose_markcutpaste">mark</A><BR>
13599 ^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>
13600 ^A Beginning of line | delete current line<BR>
13601 ^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>
13602 ^Y Previous page | cut with ^K, or unjustify<BR>
13603 ^V Next page |-------------------------------------<BR>
13604 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13605 ---------------------------------------| <!--chtml if pinemode="function_key"-->F6<!--chtml else-->^W<!--chtml endif--> <A HREF="h_composer_search">Whereis</A> (search for string)<BR>
13606 MESSAGE COMMANDS | GENERAL COMMANDS | <!--chtml if pinemode="function_key"-->F12<!--chtml else-->^T <!--chtml endif--> <A HREF="h_compose_spell">Spell checker</A><BR>
13607 <!--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>
13608 <!--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>
13609 <!--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>
13614 <LI>For help on a particular command, highlight the bold text associated
13615 with it above and hit Return.
13616 <LI> The availability of certain commands
13617 is determined by Alpine configuration files and system capabilities.
13618 At some sites, certain commands may not be available due to security or
13620 <LI>Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
13622 <LI>For special handling of Ctrl-S and Ctrl-Q see special comments regarding
13623 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
13627 HINT: To move rapidly to the bottom of a message you are composing,
13628 enter ^W^V. To go to the top, ^W^Y. These can be used in conjunction
13629 with the Mark and Cut commands to eliminate large amounts of unwanted
13632 <H2>Description of Composer</H2>
13634 Alpine has a built-in editing program that allows you to compose messages
13635 without having to leave Alpine. The editor is designed to be very simple to
13636 use so that you can get started writing email right away.
13639 Messages are usually just text, about 80 columns wide. Using upper and
13640 lower case is encouraged. On some systems the size limit of the message
13641 is about 100,000 characters, which is about 2,000 lines. You can include
13642 punctuation and special characters found on most keyboards, but you can't
13643 include characters with diacritical marks and certain special symbols.
13646 Text automatically wraps as you type past the end of a line so you do not
13647 have to hit return. Using the
13648 "<A HREF="h_compose_justify">Justify</A>" command,
13649 you can also reformat text explicitly, perhaps after you have
13653 You can include other text files with the
13654 "<A HREF="h_compose_readfile">Read File</A>" command,
13655 which will prompt you for the name of the file to insert at the
13656 current cursor postion.
13660 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13663 <End of help on this topic>
13666 ====== h_composer_browse =====
13669 <TITLE>BROWSER</TITLE>
13673 This screen lets you browse your files and directories. To go to another
13674 directory (identified by "(dir)"), move the cursor to it and
13675 choose "Select" (the default choice on the menu);
13676 or choose "Goto" and enter the name of the directory.
13677 <!--chtml if pinemode="os_windows"-->
13679 In Unix Alpine, you may use
13680 "~" to refer to your home directory or "~user" to refer
13681 to another's home directory.
13682 <!--chtml endif--><P>
13683 To select a file, move the cursor to it and
13684 choose "Select" (the default choice on the menu).
13687 <LI>Note <B>if</B> you are currently using the BROWSER for choosing a file for
13689 message body (that is, you chose "Read File" with the cursor under
13691 "----- Message Text -----" line
13692 while composing, then "To Files"): Since the file
13693 selected will become part of the message text, it must be in a format
13694 suitable for that (Alpine does not check!), such as a plain text file.
13695 Files of other formats (for example, graphics, databases, software
13696 programs) should be
13697 <B>attached</B> to the message instead --
13698 by moving the cursor in the COMPOSE MESSAGE screen into the
13699 message header area and pressing
13700 <!--chtml if pinemode="function_key"-->
13707 Note <B>if</B> you are currently using the BROWSER for saving a message
13708 attachment, or exporting a message, to a file: You can use the Add command to
13709 provide the name for a new file to save/export to, and then select that name
13710 to use it for the save/export operation. Back at the prompt
13711 "EXPORT: Copy message to file in ..." hit Enter, then choose
13712 either Overwrite or Append (it doesn't make a difference, since the file is
13713 so far empty). Note: If you cancel the
13714 operation at that point, the file created with the Add command will remain
13719 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13722 <End of help on this topic>
13725 ====== h_composer_ins =====
13728 <TITLE>INSERT TEXT FILE</TITLE>
13731 <H1>INSERT TEXT FILE</H1>
13733 Use this function to insert a text file. The file name
13734 given can be an absolute file path name for your system
13735 <!--chtml if pinemode="os_windows"-->
13736 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
13737 with a relative pathname, or simply a file name without
13738 drive or directory specification.
13740 (for example, "/tmp/exported.earlier" on Unix hosts),
13741 a file in your home directory, or a file path relative to your
13742 home directory. In Unix Alpine, you may use "~" to refer to
13743 your home directory or "~user" to refer to another
13744 account's home directory.
13747 No wild card characters may be used.
13748 The file must reside on the system running Alpine.
13751 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13752 feature is set, names are relative to your current working directory
13753 <!--chtml if pinemode="running"-->
13754 (which, at least for your current Alpine "session,"
13755 is "<!--#echo var="CURRENT_DIR"-->")
13757 rather than your home directory
13758 <!--chtml if pinemode="running"-->
13759 (which, in the present configuration of your system, is
13760 "<!--#echo var="HOME_DIR"-->")
13764 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13767 <End of help on this topic>
13770 ====== h_composer_ins_m =====
13773 <TITLE>INSERT MESSAGE</TITLE>
13776 <H1>INSERT MESSAGE</H1>
13778 Type in the number of a message in the currently open folder to insert it
13781 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13784 <End of help on this topic>
13787 ====== h_composer_search =====
13790 <TITLE>Explanation of Composer Whereis Command </TITLE>
13793 <H1>Help For Whereis Command</H1>
13795 Whereis is used to search the message for a word or part of a word.
13796 When searching in the composer, only the message part of your mail is
13797 searched, and the cursor is put on the first occurrence appearing
13798 after the location of the cursor. The search will wrap to the
13799 beginning of the message when it no longer finds matches in the
13800 remainder of the message.
13802 To search for the same string a second time, press
13803 <!--chtml if pinemode="function_key"-->
13808 to begin search and then just press RETURN to accept the previous
13809 search string shown in square brackets rather than entering a new
13812 The "Search" prompt has several sub-command available:
13816 <DD> Takes you to this help page.
13819 <DD> Cancels the prompt. No search takes place.
13821 <DT>First Line</DT>
13822 <DD> Takes you back to the composer with the cursor on the first character
13823 of the first line of text.
13826 <DD> Takes you back to the composer with the cursor on the last character
13827 of the last line of text.
13829 <DT>Replace (Optional)</DT>
13830 <DD> This sub-command is enabled by the
13831 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13832 feature (which is on by default); see its help screen for details on how replacing works.
13836 <End of help on this topic>
13839 ====== h_sigedit_search =====
13842 <TITLE>Explanation of Whereis Command </TITLE>
13845 <H1>Help For Whereis Command</H1>
13847 Whereis is used to search for a word or part of a word.
13848 When searching the cursor is put on the first occurrence appearing
13849 after the location of the cursor. The search will wrap to the
13850 beginning of the signature when it no longer finds matches in the
13851 remainder of the signature.
13853 To search for the same string a second time, press
13854 <!--chtml if pinemode="function_key"-->
13859 to begin search and then just press RETURN to accept the previous
13860 search string shown in square brackets rather than entering a new
13863 The "Search" prompt has several sub-command available:
13867 <DD> Takes you to this help page.
13870 <DD> Cancels the prompt. No search takes place.
13872 <DT>First Line</DT>
13873 <DD> Takes you back to the composer with the cursor on the first character
13874 of the first line of text.
13877 <DD> Takes you back to the composer with the cursor on the last character
13878 of the last line of text.
13880 <DT>Replace (Optional)</DT>
13881 <DD> This sub-command is enabled by the
13882 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13883 feature (which is on by default); see its help screen for details on how replacing works.
13887 <End of help on this topic>
13890 ======= h_composer_to ====
13893 <TITLE>THE MESSAGE COMPOSER'S TO FIELD</TITLE>
13896 <H1>THE MESSAGE COMPOSER'S TO FIELD</H1>
13898 <H2>The "To:" field</H2>
13899 The address you enter here must be a valid email address that is reachable
13902 <H2>Email Address Format</H2>
13903 You may enter a full name and email address,
13904 <!--chtml if pinemode="os_windows"-->
13906 a local (meaning, on the same
13907 host as the one you are running Alpine on) username that Alpine will
13910 the nickname of someone in a
13911 <A HREF="h_abook_opened">Alpine Address Book</A>, or a local
13912 mail alias defined by your system administrator. When you move the cursor
13913 out of this field, the nicknames will be expanded to the addresses in your
13914 address book, and the local usernames will be expanded to include the
13915 persons' actual names. You may enter as many addresses as you wish, but they
13916 must be separated by commas. You can move around this and other header fields
13917 with the arrow keys and use many of the usual composer editing keys.
13920 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13924 <H2>MESSAGE HEADER COMMANDS</H2>
13925 <!--chtml if pinemode="function_key"-->
13926 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13927 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13928 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13929 ^P (Up Arrow) Previous line |<BR>
13930 ^N (Down Arrow) Next line | F9 Cut marked text or<BR>
13931 ^A Beginning of line | delete current line<BR>
13932 ^E End of line | F10 Undelete line(s)<BR>
13933 F7 Previous page | ^W <A HREF="h_composer_search">Whereis</A> (search text)<BR>
13934 F8 Next page |-------------------------------------<BR>
13935 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13936 ----------------------------------------|<BR>
13937 MESSAGE COMMANDS | GENERAL COMMANDS | F12 To Addressbook/Browser<BR>
13938 F3 <A HREF="h_compose_cancel">Cancel</A> | F1 Get help | F4 Attach File<BR>
13939 F11 <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13940 F2 <A HREF="h_compose_send">Send</A> | | F5 <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13942 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13943 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13944 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13945 ^P (Up Arrow) Previous line | <BR>
13946 ^N (Down Arrow) Next line | ^K Cut marked text or<BR>
13947 ^A Beginning of line | delete current line<BR>
13948 ^E End of line | ^U Undelete line(s)<BR>
13949 ^Y Previous page |<BR>
13950 ^V Next page |-------------------------------------<BR>
13951 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13952 ----------------------------------------| ^R <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13953 MESSAGE COMMANDS | GENERAL COMMANDS | ^T To Addressbook/Browser<BR>
13954 ^C <A HREF="h_compose_cancel">Cancel</A> | ^G Get help | ^J Attach File<BR>
13955 ^O <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13956 ^X <A HREF="h_compose_send">Send</A> | | TAB <A HREF="h_compose_addrcomplete">Address Completion</A><BR>
13962 <LI>For help on a particular command, highlight the bold text associated
13963 with it above and hit Return.
13964 <LI> The availability of certain commands
13965 is determined by Alpine configuration files and system capabilities.
13966 At some sites, certain commands may not be available due to security or
13972 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13974 <End of help on this topic>
13977 ======= h_composer_cc ====
13980 <TITLE>THE MESSAGE COMPOSER'S CC FIELD</TITLE>
13983 <H1>THE MESSAGE COMPOSER'S CC FIELD</H1>
13984 The Cc: field is just like the To: field, except it is used for addressees
13985 that you wish to send a "carbon" copy to. That is, the message is
13986 not directly meant directly "for" these recipients, but you wanted
13987 them to see the message. The only difference the recipients see is that their
13988 name is in the Cc: field, rather than the To: field.
13990 For help with Cc: field editing
13991 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13994 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13998 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14000 <End of help on this topic>
14003 ======= h_composer_bcc ====
14006 <TITLE>THE MESSAGE COMPOSER'S BCC FIELD</TITLE>
14009 <H1>THE MESSAGE COMPOSER'S BCC FIELD</H1>
14010 The "Bcc:" (Blind carbon copy) header is used when you wish to send
14011 a copy of the message to one or more people whose addresses you do not
14012 wish disclosed, either to reduce clutter or for confidentiality.
14014 The format of the Bcc: field is just the same as the To: and Cc: fields in
14015 the way the addresses are entered. The recipients listed here will
14016 receive a copy of the message, but --assuming your site's mail transport
14017 software is properly configured-- their addresses will not show up in the
14018 headers of the message, as delivered to all of the recipients. The To:
14019 and Cc: recipients will not know a copy was sent to the Bcc: recipients.
14021 Note: if there is no To: or Cc: or Lcc: address in the message, Alpine
14022 will automatically generate and place in the To: field a pseudo-address of
14023 "undisclosed-recipients: ;"
14024 or whatever string has been specified in the
14025 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
14028 The reason for this is to avoid embarrassment caused by some Internet
14029 mail transfer software that interprets a "missing" To: header as
14030 an error and replaces it with an Apparently-to: header that may contain
14031 the addresses you entered on the Bcc: line. In addition, it may be
14032 less disconcerting to Bcc: recipients to see <B>something</B> in the To: field.
14034 You can manipulate what text ends up on the (originally) empty To:
14035 field. Just remember to put a colon and semicolon at the end of the
14036 field, which is a special notation denoting that it is not a real address.
14038 For information on message header editing
14039 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14042 <LI><A HREF="h_address_format">Explanation of Address formats</A>
14046 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14048 <End of help on this topic>
14051 ======= h_composer_lcc ====
14054 <TITLE>THE MESSAGE COMPOSER'S LCC FIELD</TITLE>
14057 <H1>THE MESSAGE COMPOSER'S LCC FIELD</H1>
14058 The "Lcc:" (List carbon copy) header is intended to be used when
14059 you wish to send a message to a list of people but avoid having all
14060 of their addresses visible, in order to reduce clutter when the
14061 message is received.
14063 It is similar to the
14064 <A HREF="h_composer_bcc">"Bcc" (Blind carbon copy) header</A>
14066 addressees are hidden, but Lcc is designed to work specifically with
14067 distribution lists you have created in your
14068 <A HREF="h_abook_opened">Alpine Address Book</A>. Placing
14069 the nickname of the list on the Lcc line will result in the full name of
14070 your Alpine Address Book list being placed on the To: line of the message,
14071 using a special notation that distinguishes it from a real address. You
14072 must leave the To: line blank for your list name to appear there.
14074 For example, if you have this list entered in your Address Book:<PRE>
14076 largo Key Largo List DISTRIBUTION LIST:
14079 walter@mgm.com</PRE>
14082 and you enter "largo" on the Lcc: line while composing a message,
14083 the result is:<PRE>
14085 To : Key Largo List: ;
14089 Lcc : Key Largo List <bogie@mgm.com>,
14094 Each recipient listed on the Lcc: line receives a copy of the message
14095 without their address being visible (as though they were listed on the
14096 Bcc: line). The colon-semicolon notation used to put the full-name of the
14097 list on the To: line is a special address format that doesn't specify any
14098 actual addressees, but does give some information to the recipients of the
14101 Note: if after entering an LCC, you delete the list name that is placed
14102 on the To: line, then recipients will see <PRE>
14103 To: undisclosed-recipients: ;</PRE>
14105 (or whatever string is defined in the
14106 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
14107 variable) just as in the BCC case.
14109 For help with Lcc: field editing
14110 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14113 <LI><A HREF="h_address_format">Explanation of Address formats</A>
14117 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14119 <End of help on this topic>
14122 ======= h_composer_from =======
14125 <TITLE>THE MESSAGE COMPOSER'S FROM FIELD</TITLE>
14128 <H1>THE MESSAGE COMPOSER'S FROM FIELD</H1>
14130 This header carries your return address. It is the address toward which
14131 replies (and often, future unrelated correspondence) will be directed,
14132 unless you have <A HREF="h_config_custom_hdrs">defined an optional
14133 "Reply-To:" header</A> in the SETUP CONFIGURATION screen. Make
14134 sure this address is correct.
14136 For help with message header editing
14137 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14140 <LI><A HREF="h_address_format">Explanation of Address formats</A>
14144 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14146 <End of help on this topic>
14149 ======= h_composer_reply_to =======
14152 <TITLE>THE MESSAGE COMPOSER'S REPLY-TO FIELD</TITLE>
14155 <H1>THE MESSAGE COMPOSER'S REPLY-TO FIELD</H1>
14157 Most people should not need this header. The Reply-To: header is used in
14158 cases where you would like replies to your messages to be directed to an
14159 address other than your normal "From:" address. This is atypical,
14160 but can happen when you use multiple machines and do not have the same account
14161 name on each one, or when you wish to direct certain replies to accounts
14162 or folders designated for specific classes of correspondence.
14164 For help with message header editing
14165 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14168 <LI><A HREF="h_address_format">Explanation of Address formats</A>
14173 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14175 <End of help on this topic>
14178 ======= h_composer_custom_addr ====
14181 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
14184 <H1>CUSTOMIZED HEADER FIELD</H1>
14185 This is a customized header, i.e. not one that is part of Alpine's normal
14186 set of Compose headers.
14188 For help with message header editing
14189 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14192 <LI><A HREF="h_address_format">Explanation of Address formats</A>
14196 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14198 <End of help on this topic>
14201 ======= h_composer_custom_free ====
14204 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
14207 <H1>CUSTOMIZED HEADER FIELD</H1>
14208 This is a customized header, i.e. not one that is part of Alpine's normal
14209 set of Compose headers.
14211 This field consists of arbitrary text.
14213 For help with message header editing
14214 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14217 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14219 <End of help on this topic>
14222 ====== h_composer_news =====
14225 <TITLE>THE MESSAGE COMPOSER'S NEWSGRPS LINE</TITLE>
14228 <h1>THE MESSAGE COMPOSER'S NEWSGRPS LINE</h1>
14229 Use the newsgroups line to specify any and all USENET newsgroups to which
14230 your message should be posted. When composing a message from scratch, this
14231 line may be hidden. If so, just press the rich headers command
14232 (<!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif-->)
14233 to make it visible.
14235 <EM>Be aware</EM> that when you post to a newsgroup thousands of
14236 people will be reading your message. Also, you or your system manager
14237 must have defined an "<!--#echo var="VAR_nntp-server"-->" in your Alpine configuration
14238 in order for you to be able to post.
14240 For help with message header editing
14241 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14243 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14246 <End of help on this topic>
14249 ======= h_composer_fcc ====
14252 <TITLE>THE MESSAGE COMPOSER'S FCC FIELD</TITLE>
14255 <H1>THE MESSAGE COMPOSER'S FCC FIELD</H1>
14256 The FCC (File Carbon Copy) specifies the folder used to keep a copy of
14257 each outgoing message. The default value can be configured with the
14258 "<!--#echo var="VAR_default-fcc"-->" and "<!--#echo var="VAR_fcc-name-rule"-->" options. You can change or remove
14259 the file carbon copy on any message you send by editing the FCC header.<p>
14261 You may type ^T to get a list of all your folders and select one to use as
14262 the FCC for this message.<P>
14264 For help with message header editing
14265 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14268 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14270 <End of help on this topic>
14273 ======= h_composer_subject ====
14276 <TITLE>THE MESSAGE COMPOSER'S SUBJECT FIELD</TITLE>
14279 <H1>THE MESSAGE COMPOSER'S SUBJECT FIELD</H1>
14281 The subject header provides a place to enter a few words that summarize
14282 the topic of the message you are sending. You may leave this line blank,
14283 but it is considered a courtesy to use a meaningful subject.<p>
14285 For help with message header editing
14286 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14289 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14291 <End of help on this topic>
14294 ======= h_composer_attachment ====
14297 <TITLE>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</TITLE>
14300 <H1>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</H1>
14302 The "Attchmnt:" field is where you specify what file or
14303 files you'd like attached to
14304 the message you are composing. Those files must reside on the machine
14305 running Alpine. If your file is on a PC or Mac and you run Alpine with an
14306 account on a Unix machine, you'll have to transfer it before attaching it.
14307 Contact local computer support people for assistance with transferring.
14311 given can be an absolute file path name for your system
14312 <!--chtml if pinemode="os_windows"-->
14313 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
14314 with a relative pathname, or simply a file name without
14315 drive or directory specification.
14317 (for example, "/tmp/exported.earlier" on Unix hosts),
14318 a file in your home directory, or a file path relative to your
14319 home directory. In Unix Alpine, you may use "~" to refer to
14320 your home directory or "~user" to refer to another
14321 account's home directory.
14322 <!--chtml endif--><P>
14323 No wild card characters may be used.
14325 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
14326 feature is set, names are relative to your current working directory
14327 <!--chtml if pinemode="running"-->
14328 (which, at least for your current Alpine "session,"
14329 is "<!--#echo var="CURRENT_DIR"-->")
14331 rather than your home directory
14332 <!--chtml if pinemode="running"-->
14333 (which, in the present configuration of your system, is
14334 "<!--#echo var="HOME_DIR"-->")
14338 Alpine uses MIME encoding for attachments, so binaries and files of any
14339 length can safely be delivered to any MIME-capable mail reading program.
14340 If you send an attachment to someone who does not have a MIME-capable mail
14341 reading program yet, then the main message text will be readable, but
14342 attachments (even attachments that are just plain text) are not.
14345 Typing the filename on the Attchmnt: line achieves the same
14346 result as using the
14347 <!--chtml if pinemode="function_key"-->
14351 <!--chtml endif--> command.
14354 If you Forward a message with attachments, you may delete them from your
14355 Forwarded message by editing the Attchmnt header line.
14358 For help with message header editing
14359 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14362 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14364 <End of help on this topic>
14367 ======= h_composer_ctrl_j ====
14370 <TITLE>COMPOSER ATTACH</TITLE>
14374 <!--chtml if pinemode="function_key"-->
14378 <!--chtml endif--> command:
14379 At the "File to attach:" prompt, enter the name of the
14380 existing file to attach to your message.
14382 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
14384 you need only enter the beginning of the filename (enough of it to uniquely
14385 identify the file) and press TAB to complete it.
14387 Or, press ^T to use the BROWSER screen for
14388 selecting the file. <P>
14389 For more information on attaching files, see the help screen for the
14391 <A HREF="h_composer_attachment">Attchmnt: field</A>, which is normally hidden,
14392 but can be revealed using the
14393 <!--chtml if pinemode="function_key"-->
14398 command with the cursor positioned above the
14399 "----- Message Text -----" line in the COMPOSE MESSAGE screen.
14401 <End of help on this topic>
14404 ======= h_edit_nav_cmds =========
14407 <TITLE>Composer Editing Commands Explained</TITLE>
14410 <H1>EDITING and NAVIGATION COMMANDS</H1>
14411 <!--chtml if pinemode="function_key"-->
14413 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
14414 ^B (Left Arrow) Back character | ^D Delete current character
14415 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14416 ^P (Up Arrow) Previous line |
14417 ^N (Down Arrow) Next line | F9 Cut marked text or
14418 ^A Beginning of line | delete current line
14419 ^E End of line | F10 Undelete line(s)
14421 F8 Next page |-------------------------------------
14422 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
14423 ----------------------------------------|
14424 EXIT COMMANDS | GENERAL COMMANDS | F12 To Addressbook
14425 F3 Cancel | F1 Get help | F12 RichView (expand lists)
14426 F2 eXit/save | ^Z Suspend | ^L Redraw Screen
14430 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
14431 ^B (Left Arrow) Back character | ^D Delete current character
14432 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14433 ^P (Up Arrow) Previous line |
14434 ^N (Down Arrow) Next line | ^K Cut marked text or
14435 ^A Beginning of line | delete current line
14436 ^E End of line | ^U Undelete line(s)
14438 ^V Next page |-------------------------------------
14439 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
14440 ----------------------------------------|
14441 EXIT COMMANDS | GENERAL COMMANDS | ^T To Addressbook
14442 ^C Cancel | ^G Get help | ^R RichView (expand lists)
14443 ^X eXit/save | ^Z Suspend | ^L Redraw Screen
14446 <End of help on this topic>
14449 ===== h_composer_sigedit =====
14452 <TITLE>Signature Editor Commands Explained</TITLE>
14455 <H1>SIGNATURE EDITOR COMMANDS</H1>
14456 <!--chtml if pinemode="function_key"-->
14458 CURSOR MOTION KEYS |EDITING KEYS
14459 ^B (Left Arrow) Back character | ^D Delete current character
14460 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14461 ^P (Up Arrow) Previous line | ^^ Set a mark
14462 ^N (Down Arrow) Next line | F9 Cut marked text or
14463 ^A Beginning of line | delete current line
14464 ^E End of line | F10 Paste text, undelete lines
14465 F7 Previous page | cut with ^K, or unjustify
14466 F8 Next page |-------------------------------------
14467 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14468 ---------------------------------------| F6 Whereis (search for string)
14469 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
14470 F3 Cancel | F1 Get help | F4 Justify paragraph
14471 | ^Z Suspend | ^L Redraw Screen
14472 F2 Send | F6 Alt. editor | F5 Read in a file
14476 CURSOR MOTION KEYS |EDITING KEYS
14477 ^B (Left Arrow) Back character | ^D Delete current character
14478 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14479 ^P (Up Arrow) Previous line | ^^ Set a mark
14480 ^N (Down Arrow) Next line | ^K Cut marked text or
14481 ^A Beginning of line | delete current line
14482 ^E End of line | ^U Paste text, undelete lines
14483 ^Y Previous page | cut with ^K, or unjustify
14484 ^V Next page |-------------------------------------
14485 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14486 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
14487 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
14488 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
14489 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
14490 ^X Send | ^_ Alt. editor | ^R Read in a file
14494 NOTE: The presence or absence of the following commands is determined
14495 by "Feature-List" options in your Alpine configuration. Also,
14496 some of these commands may be administratively disabled by your system
14497 manager; if they don't work, please check with your local help desk
14498 before reporting a bug.
14501 <LI>Suspend (suspends Alpine and gives a system prompt)
14502 <LI>Alternate editor (allows you to compose with your own editor)
14506 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
14510 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
14511 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
14513 <End of help on this topic>
14516 ===== h_composer_commentedit =====
14519 <TITLE>Comment Editor Commands Explained</TITLE>
14522 <H1>COMMENT EDITOR COMMANDS</H1>
14523 <!--chtml if pinemode="function_key"-->
14525 CURSOR MOTION KEYS |EDITING KEYS
14526 ^B (Left Arrow) Back character | ^D Delete current character
14527 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14528 ^P (Up Arrow) Previous line | ^^ Set a mark
14529 ^N (Down Arrow) Next line | F9 Cut marked text or
14530 ^A Beginning of line | delete current line
14531 ^E End of line | F10 Paste text, undelete lines
14532 F7 Previous page | cut with ^K, or unjustify
14533 F8 Next page |-------------------------------------
14534 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14535 ---------------------------------------| F6 Whereis (search for string)
14536 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
14537 F3 Cancel | F1 Get help | F4 Justify paragraph
14538 | ^Z Suspend | ^L Redraw Screen
14539 F2 Send | F6 Alt. editor | F5 Read in a file
14543 CURSOR MOTION KEYS |EDITING KEYS
14544 ^B (Left Arrow) Back character | ^D Delete current character
14545 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14546 ^P (Up Arrow) Previous line | ^^ Set a mark
14547 ^N (Down Arrow) Next line | ^K Cut marked text or
14548 ^A Beginning of line | delete current line
14549 ^E End of line | ^U Paste text, undelete lines
14550 ^Y Previous page | cut with ^K, or unjustify
14551 ^V Next page |-------------------------------------
14552 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14553 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
14554 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
14555 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
14556 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
14557 ^X Send | ^_ Alt. editor | ^R Read in a file
14561 NOTE: The presence or absence of the following commands is determined
14562 by "Feature-List" options in your Alpine configuration. Also,
14563 some of these commands may be administratively disabled by your system
14564 manager; if they don't work, please check with your local help desk
14565 before reporting a bug.
14568 <LI>Suspend (suspends Alpine and gives a system prompt)
14569 <LI>Alternate editor (allows you to compose with your own editor)
14573 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
14577 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
14578 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
14580 <End of help on this topic>
14583 ======= h_composer_abook_nick =======
14586 <TITLE>Addressbook Nickname Explained</TITLE>
14589 This is a short nickname for this address book entry. If it is used in
14590 place of an address from the composer, the composer will fill in the
14591 address(es) for the entry that matches the nickname.
14594 Look <A HREF="h_edit_nav_cmds">here</A>
14595 to see the available Editing and Navigation commands.
14597 <End of help on this topic>
14600 ======= h_composer_abook_full =======
14603 <TITLE>Addressbook Fullname Explained</TITLE>
14606 This is the full name field for this entry. If this is going to be a
14607 distribution list (more than one address), it should be a descriptive
14608 phrase describing the list. It will be included in the mail header if you
14609 put the list in the To: or CC: field, or in the To: line if you put the
14610 list in the Lcc: field. It's OK to leave this field blank (and OK to
14611 leave any of the other fields blank, too). If this address book entry is
14612 going to be a simple entry with just one address, then this field is the
14613 person's name. When you send mail to this entry, this is the field to the
14614 left of the brackets. That is, it is the most readable part of the
14615 address. For example, in the sample address:
14617 John Doe <jdoe@some.domain>
14619 "John Doe" is the full name field. If you are sorting your address book
14620 with one of the options that uses full names, then it might be useful to
14621 enter the full name as "Last, First", for example:
14625 so that it will be sorted using Doe instead of John. This will be changed
14626 back into John Doe when you use it.
14628 Look <A HREF="h_edit_nav_cmds">here</A>
14629 to see the available Editing and Navigation commands.
14631 <End of help on this topic>
14634 ======= h_composer_abook_fcc =======
14637 <TITLE>Addressbook Fcc Explained</TITLE>
14640 If this entry is the first one in the To: line of an outgoing message,
14641 this field will be used for the Fcc (File Carbon Copy) instead of whatever
14642 you would normally get (which depends on which
14643 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
14646 If this field consists of two double quotes ("") that tells Alpine
14647 that you don't want any Fcc associated with this entry.
14649 Look <A HREF="h_edit_nav_cmds">here</A>
14650 to see the available Editing and Navigation commands.
14652 <End of help on this topic>
14655 ====== h_config_combined_abook_display =====
14658 <TITLE>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></TITLE>
14661 <H1>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></H1>
14663 This feature affects the address book display screens.
14664 Normally, expanding an address book from the ADDRESS BOOK LIST screen
14665 will cause the remaining address books and directory servers to disappear
14666 from the screen, leaving only the entries of the expanded address book.
14667 If this feature is set, then the other address books will remain on the screen,
14668 so that all of the address books can be present at once.
14671 The way that commands work won't be changed.
14672 For example, the Select All command will select all of the entries in the
14673 current address book, not all of the entries in all of the address books.
14674 The WhereIs command will change a little.
14675 It will search through all of the text on the screen plus all of the entries
14676 from expanded address books.
14679 When this feature is set, the setting of the feature
14680 <A HREF="h_config_expanded_addrbooks">"<!--#echo var="FEAT_expanded-view-of-addressbooks"-->"</A>
14683 <End of help on this topic>
14686 ====== h_config_titlebar_color_style =====
14689 <TITLE>OPTION: <!--#echo var="VAR_titlebar-color-style"--></TITLE>
14692 <H1>OPTION: <!--#echo var="VAR_titlebar-color-style"--></H1>
14694 This option affects the colors used to display the titlebar (the top
14695 line on the screen) when viewing a message.
14698 The available options include:
14703 <DD>The color of the titlebar will be the color you set for the
14704 <A HREF="h_config_title_color">Title Color</A>.
14705 The Title Color may be set by using the
14706 <A HREF="h_color_setup">Setup Kolor</A> screen.
14710 <DD>The color of the titlebar will be the same as the color of the
14711 index line corresponding to the message being viewed.
14712 The rules that determine what color the index line will be may be set
14713 up by going to the Setup/Rules/Indexcolor screen.
14714 If the index line for a message is not colored explicitly by the
14715 Indexcolor rules, then the titlebar will be colored the same as for
14716 the "default" option above (which is not the same color that
14717 the index line itself will have).
14720 <DT>reverse-indexline</DT>
14721 <DD>This is similar to the "indexline" option except the
14722 foreground and background colors from the corresponding index line will
14724 For example, if the index line color is red letters on a white background,
14725 then the titlebar will be white letters on a red background.
14726 If the index line for a message is not colored explicitly by the
14727 Indexcolor rules, then the titlebar will be colored the same as for
14728 the "default" option above (which is not the same color that
14729 the index line itself will have).
14736 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14738 <End of help on this topic>
14741 ====== h_config_index_color_style =====
14744 <TITLE>OPTION: <!--#echo var="VAR_current-indexline-style"--></TITLE>
14747 <H1>OPTION: <!--#echo var="VAR_current-indexline-style"--></H1>
14749 This option affects the colors used to display the current line in the
14750 MESSAGE INDEX screen.
14751 If you do not have Index Color Rules defined, then this option will
14752 have no effect in the index.
14753 Those Rules may be defined by going to the Setup/Rules/Indexcolor screen.
14756 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
14757 is turned on and the
14758 <A HREF="h_config_incunseen_color">Incoming Unseen Color</A>
14759 is set to something other than the default, then
14760 this option also affects the color used to display the current folder
14761 in the Incoming FOLDER LIST screen.
14764 The available options include:
14768 <DT>flip-colors</DT>
14769 <DD>This is the default.
14770 If an index line is colored because it matches one of your
14771 Index Color Rules, then its colors will be reversed when it is the currently
14773 For example, if the line is normally red text on a blue background, then
14774 when it is the current line it will be drawn as blue text on a red background.
14776 The rest of the option values all revert to this flip-colors behavior if
14777 there is no Reverse Color defined.
14781 <DD>With this option the Reverse color is always used to highlight the
14785 <DT>reverse-fg</DT>
14786 <DD>The foreground part of the Reverse Color is used to highlight
14788 If this would cause the text to be unreadable (because the foreground and
14789 background colors are the same) or if it would cause no change in the
14790 color of the index line, then the colors are flipped instead.
14792 Some people think this works particularly well if you use different
14793 background colors to emphasize "interesting" lines,
14794 but always with the same Normal foreground color,
14795 and you use a different foreground color for the Reverse Color.
14798 <DT>reverse-fg-no-ambiguity</DT>
14799 <DD>With the "reverse-fg" rule above, it is possible that
14800 the resulting color will be exactly the same as the regular Reverse
14802 That can lead to some possible confusion because an
14803 "interesting"
14804 line that is the current line will be displayed exactly the same as a
14805 non-interesting line that is current.
14806 You can't tell whether the line is just a regular current line or if it is
14807 an "interesting" current line by looking at the color.
14808 Setting the option to this value removes that ambiguity.
14809 It is the same as the "reverse-fg" setting unless the resulting
14810 interesting current line would look just like a non-interesting current line.
14811 In that case, the interesting line's colors are simply flipped (like in the
14814 As an alternative way to preserve the line's interestingness in this case,
14815 you may find that using both a different foreground and a different
14816 background color for the interesting line will help.
14819 <DT>reverse-bg</DT>
14820 <DD>The background part of the Reverse Color is used to highlight
14822 If this would cause the text to be unreadable (because the foreground and
14823 background colors are the same) or if it would cause no change in the
14824 color of the index line, then the colors are flipped instead.
14826 Some people think this works particularly well if you use different
14827 foreground colors to emphasize "interesting" lines,
14828 but always with the same Normal background color,
14829 and you use a different background color for the Reverse Color.
14832 <DT>reverse-bg-no-ambiguity</DT>
14833 <DD>As with the "reverse-fg" case, the "reverse-bg"
14834 rule may also result in a color that is exactly the same as the regular
14836 Setting the option to this value removes that ambiguity.
14837 It is the same as the "reverse-bg" setting unless the resulting
14838 current line has the same color as the Reverse Color.
14839 In that case, the interesting line's colors are simply flipped (like in the
14847 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14849 <End of help on this topic>
14852 ====== h_config_expanded_addrbooks =====
14855 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></TITLE>
14858 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></H1>
14860 If multiple address books (either personal or global) are defined, and you
14861 wish to have them all expanded implicitly upon entering the ADDRESS BOOK
14862 screen, then set this feature. This feature will have no effect unless the
14864 <A HREF="h_config_combined_abook_display">"<!--#echo var="FEAT_combined-addrbook-display"-->"</A>
14867 <End of help on this topic>
14870 ====== h_config_combined_folder_display =====
14873 <TITLE>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></TITLE>
14876 <H1>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></H1>
14878 This feature affects the folder list display screens.
14879 Normally, each folder list is viewed within its collection only. This
14880 command allows folder lists to be viewed within a single screen that
14881 combines the contents of all collections.
14884 The way that commands work won't be changed.
14885 For example, the Select All command will select all of the folders in the
14886 current collection, not all of the entries in all of the collections.
14887 The WhereIs command will change a little.
14888 It will search through all of the folders in the current collection as well
14889 as all the folder in any other expanded collection.
14892 When this feature is set, the setting of the feature
14893 <A HREF="h_config_expanded_folders">"<!--#echo var="FEAT_expanded-view-of-folders"-->"</A>
14896 <End of help on this topic>
14899 ====== h_config_combined_subdir_display =====
14902 <TITLE>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></TITLE>
14905 <H1>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></H1>
14907 This feature affects the Folder List screen when
14909 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14910 feature is enabled. Normally, selecting a directory from the Folder
14911 List takes you into a new screen displaying only the contents of
14915 Enabling this feature will cause the contents of the selected
14917 displayed within the boundaries of the "Collection" it
14918 is a part of. All previously displayed collections will remain
14922 The way that commands work won't be changed.
14923 For example, the Select All command will select all of the folders in the
14924 directory, as opposed to all of the entries in all of the collections.
14925 The WhereIs command will change a little.
14926 It will search through all of the folders in the current collection as well
14927 as all the folder in any other expanded collection.
14930 <End of help on this topic>
14933 ====== h_config_separate_fold_dir_view =====
14936 <TITLE>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></TITLE>
14939 <H1>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></H1>
14941 This feature affects folder collections wherein a folder
14942 and directory can have the same name. By default, Alpine displays them
14943 only once, denoting that it is both a folder and directory by appending
14944 the folder name with the hierarchy character enclosed
14945 in square brackets.
14949 Enabling this feature will cause Alpine to display such names
14950 separately marking the name representing a directory with a trailing
14951 hierarchy delimiter (typically the slash, "/", character).
14954 The feature also alters the command set slightly. By default, the
14955 right-arrow descends into the directory, while hitting the Return key will
14956 cause the folder by that name to be opened.
14959 With this feature set, the Return key will open the highlighted folder, or
14960 enter the highlighted directory.
14963 <End of help on this topic>
14966 ====== h_config_expanded_folders =====
14969 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></TITLE>
14972 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></H1>
14974 If multiple folder collections are defined, and you
14975 wish to have them all expanded implicitly upon entering the FOLDER LIST
14976 screen, then set this feature. This feature will have no effect unless the
14978 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14981 <End of help on this topic>
14984 ======= h_config_ldap_server =======
14987 <TITLE>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
14990 <H1>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
14991 This is the name of the host where an LDAP server is running.
14992 For redundancy, this may be a space-delimited set of server names, in which
14993 case the first server that answers is used.
14994 Each of the server names may be optionally followed by
14995 a colon and a port number.
14996 If this form is used then the port number configured below in the
14997 <EM>port</EM> field is not used.
14999 To find out whether your organization has its own LDAP server,
15000 contact its computing support staff.
15002 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
15005 <End of help on this topic>
15008 ======= h_config_ldap_base =======
15011 <TITLE>LDAP OPTION: Search-Base</TITLE>
15014 <H1>LDAP OPTION: Search-Base</H1>
15016 This is the search base to be used on this server. It functions as a filter
15017 by restricting your searches in the LDAP server database
15018 to the specified contents of the specified fields. Without it, searches
15019 submitted to this directory server may fail. It might be something
15023 O = <Your Organization Name>, C = US
15025 or it might be blank.
15026 (Some LDAP servers actually ignore anything specified here.)
15028 If in doubt what parameters you should specify here,
15029 contact the maintainers of the LDAP server.
15031 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
15034 <End of help on this topic>
15037 ======= h_config_ldap_port =======
15040 <TITLE>LDAP OPTION: Port</TITLE>
15043 <H1>LDAP OPTION: Port</H1>
15045 This is the TCP port number to be used with this LDAP server. If you leave
15046 this blank port 389 will be used.
15048 <End of help on this topic>
15051 ======= h_config_ldap_nick =======
15054 <TITLE>LDAP OPTION: Nickname</TITLE>
15057 <H1>LDAP OPTION: Nickname</H1>
15059 This is a nickname to be used in displays. If you don't supply a
15060 nickname the server name
15061 (<A HREF="h_config_ldap_server">"<!--#echo var="VAR_ldap-servers"-->"</A>)
15062 will be used instead. This option is strictly for your convenience.
15064 <End of help on this topic>
15067 ======= h_config_ldap_binddn =======
15070 <TITLE>LDAP OPTION: Bind-DN</TITLE>
15073 <H1>LDAP OPTION: Bind-DN</H1>
15075 You may need to authenticate to the LDAP server before you are able to use it.
15076 This is the Distinguished Name to bind to when authenticating to this server.
15077 Try leaving this blank until you know you need it.
15079 Alpine only knows about LDAP Simple authentication.
15080 It does not attempt LDAP SASL authentication.
15081 The DN and password will be sent in the clear unless TLS encryption is
15082 being used on this connection.
15083 Because of this, you may want to set the LDAP feature
15084 <A HREF="h_config_ldap_opts_tls">"Attempt-TLS-On-Connection"</A>
15086 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
15087 if you are going to be providing a password.
15089 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
15092 <End of help on this topic>
15095 ======= h_config_ldap_opts_impl =======
15098 <TITLE>LDAP FEATURE: Use-Implicitly-From-Composer</TITLE>
15101 <H1>LDAP FEATURE: Use-Implicitly-From-Composer</H1>
15103 Set this to have lookups done to this server implicitly from the composer.
15104 If an address doesn't look like a fully-qualified address, it will be looked
15105 up in your address books, and if it doesn't match a nickname there, then it
15106 will be looked up on the LDAP servers that have this feature set.
15107 The lookups will also be done when using the address completion feature
15108 (TAB command) in the composer if any of the serves have this feature set.
15109 Also see the LDAP feature
15110 <A HREF="h_config_ldap_opts_rhs">"Lookup-Addrbook-Contents"</A>
15111 and the Setup/Config feature
15112 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
15114 <End of help on this topic>
15117 ======= h_config_ldap_opts_tls =======
15120 <TITLE>LDAP FEATURE: Attempt-TLS-On-Connection</TITLE>
15123 <H1>LDAP FEATURE: Attempt-TLS-On-Connection</H1>
15125 When connecting to this server Alpine will attempt to use TLS encryption
15127 Also see the closely related feature
15128 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
15130 Note that if this option is set, then
15131 <A HREF="h_config_ldap_opts_ldaps">
15132 "Require-LDAPS-On-Connection"</A>
15133 can not be enabled for this server. You must disable this feature in
15135 <A HREF="h_config_ldap_opts_ldaps">
15136 "Require-LDAPS-On-Connection"</A>
15138 <End of help on this topic>
15141 ======= h_config_ldap_opts_tlsmust =======
15144 <TITLE>LDAP FEATURE: Require-TLS-On-Connection</TITLE>
15147 <H1>LDAP FEATURE: Require-TLS-On-Connection</H1>
15149 When connecting to this server Alpine will attempt to use TLS encryption
15151 If the StartTLS operation fails then the connection will not be used.
15153 Note that if this option is set, then
15154 <A HREF="h_config_ldap_opts_ldaps">
15155 "Require-LDAPS-On-Connection"</A>
15156 can not be enabled for this server. You must disable this feature in
15158 <A HREF="h_config_ldap_opts_ldaps">
15159 "Require-LDAPS-On-Connection"</A>
15161 <End of help on this topic>
15164 ======= h_config_ldap_opts_ldaps =======
15167 <TITLE>LDAP FEATURE: Require-LDAPS-On-Connection</TITLE>
15170 <H1>LDAP FEATURE: Require-LDAPS-On-Connection</H1>
15172 When connecting to this server Alpine will use LDAPS (LDAP over SSL/TLS)
15175 This feature can not be used along with
15176 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
15178 <A HREF="h_config_ldap_opts_tls">"Attempt-TLS-On-Connection"</A>.
15179 If you want to connect using StartTLS to this server, you must disable
15180 this feature first.
15182 <End of help on this topic>
15185 ====== h_config_ldap_opts_rhs =====
15188 <TITLE>LDAP FEATURE: Lookup-Addrbook-Contents</TITLE>
15191 <H1>LDAP FEATURE: Lookup-Addrbook-Contents</H1>
15193 Normally implicit LDAP lookups from the composer are done only for the
15194 strings you type in from the composer screen. In other words, you type in
15195 something in the To or CC field and press return, then the string is looked up.
15196 First that string is looked up in your address books. If a match is found
15197 there, then the results of that match are looked up again. If you place
15198 a string in your address book that you want to have looked up on the LDAP
15199 directory server, you need to turn on this feature. If you set this feature
15200 for a server, you almost always will also want to set the
15201 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
15202 feature. An example might serve to best illustrate this feature.
15204 If an LDAP lookup of "William Clinton" normally returns an
15206 address of pres@whitehouse.gov, then you might put an entry in your address
15207 book that looks like:
15209 <CENTER><SAMP>Nickname = bill</SAMP></CENTER><BR>
15210 <CENTER><SAMP>Address = "William Clinton"</SAMP></CENTER>
15212 Now, when you type "bill" into an
15213 address field in the composer Alpine will
15214 find the "bill" entry in your address book.
15215 It will replace "bill" with
15216 "William Clinton".
15217 It will then search for an entry with that nickname
15218 in your address book and not find one. If this feature
15219 is set, Alpine will then attempt to lookup
15220 "William Clinton" on the LDAP server and find the entry with address
15221 pres@whitehouse.gov.
15223 A better way to accomplish the same thing is probably to use the feature
15224 <A HREF="h_config_ldap_opts_ref">"Save-Search-Criteria-Not-Result"</A>.
15226 <End of help on this topic>
15229 ====== h_config_ldap_opts_ref =====
15232 <TITLE>LDAP FEATURE: Save-Search-Criteria-Not-Result</TITLE>
15235 <H1>LDAP FEATURE: Save-Search-Criteria-Not-Result</H1>
15237 Normally when you save the results of an LDAP directory lookup to your
15238 address book the results of the lookup are saved. If this feature is set
15239 and the entry being saved was found on this directory server, then the
15240 search criteria is saved instead of the results of the search. When this
15241 address book entry is used in the future, instead of copying the results
15242 from the address book the directory lookup will be done again. This could
15243 be useful if the copied result might become stale because the data on
15244 the directory server changes (for example, the entry's email address changes).
15245 You probably don't want to set this feature if the server is at all slow or
15248 The way this actually works is that instead of saving the email address
15249 in your address book, Alpine saves enough information to look up the same
15250 directory entry again. In particular, it saves the server name and the
15251 distinguished name of the entry. It's possible that the server administrators
15252 might change the format of distinguished names on the server, or that the
15253 entry might be removed from the server. If Alpine notices this, you will be warned
15254 and a backup copy of the email address will be used. You may want to create
15255 a new entry in this case, since you will get the annoying warning every
15256 time you use the old entry. You may do that by Saving the entry to a new
15257 nickname in the same address book. You will be asked whether or not you
15258 want to use the backup email address.
15260 A related feature in the Setup/Config screen is
15261 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
15263 <End of help on this topic>
15266 ======= h_config_ldap_opts_nosub =======
15269 <TITLE>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</TITLE>
15272 <H1>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</H1>
15274 Spaces in your input are normally handled specially.
15275 Each space character is replaced
15278 <CENTER><SAMP>* <SPACE></SAMP></CENTER>
15280 in the search query (but not by "* <SPACE> *").
15281 The reason this is done is so the input string
15283 <CENTER><SAMP>Greg Donald</SAMP></CENTER>
15285 (which is converted to "Greg* Donald") will match
15286 the names "Greg Donald",
15287 "Gregory Donald", "Greg F. Donald", and
15288 "Gregory F Donald"; but it won't match "Greg McDonald".
15289 If the "Search-Rule" you were using was "begins-with",
15290 then it would also match the name "Greg Donaldson".
15292 Turning on this feature will disable this substitution.
15294 <End of help on this topic>
15297 ====== h_config_ldap_searchtypes =======
15300 <TITLE>LDAP OPTION: Search-Type</TITLE>
15303 <H1>LDAP OPTION: Search-Type</H1>
15305 This affects the way that LDAP searches are done.
15306 In particular, this tells the server where to look for the string to be matched.
15307 If set to "name" then the string that is being searched for will
15308 be compared with the string in the
15309 "Name" field on the server
15310 (technically, it is the "commonname" field on the server).
15311 "Surname" means we're looking for a
15312 match in the "Surname" field on the
15313 server (actually the "sn" field).
15314 "Givenname" really is "givenname"
15315 and "email" is the electronic mail address (this is actually the field
15316 called "mail" or "electronicmail" on the server).
15317 The other three types are combinations of
15318 the types listed so far. "Name-or-email"
15319 means the string should appear
15320 in either the "name" field OR the "email" field.
15321 Likewise, "surname-or-givenname"
15322 means "surname" OR "givenname"
15323 and "sur-or-given-or-name-or-email" means the obvious thing.
15325 This search TYPE is combined with the
15326 search <A HREF="h_config_ldap_searchrules">RULE</A>
15327 to form the actual search query.
15329 The usual default value for this
15330 option is "sur-or-given-or-name-or-email".
15331 This type of search may be slow on some servers.
15332 Try "name-or-email", which is often
15333 faster, or just "name" if the performance seems to be a problem.
15335 Some servers have been configured with different attribute names for
15337 In other words, instead of using the attribute name "mail"
15338 for the email address field, the server might be configured to use something
15339 else, for example, "rfc822mail" or "internetemailaddress".
15340 Alpine can be configured to use these different attribute names by using
15341 the four configuration options:
15343 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
15346 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
15349 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
15352 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
15355 <End of help on this topic>
15358 ====== h_config_ldap_searchrules =======
15361 <TITLE>LDAP OPTION: Search-Rule</TITLE>
15364 <H1>LDAP OPTION: Search-Rule</H1>
15366 This affects the way that LDAP searches are done.
15367 If set to "equals" then
15368 only exact matches count.
15369 "Contains" means that the string you type in
15370 is a substring of what you are matching against.
15371 "Begins-with" and "ends-with"
15372 mean that the string starts or ends with the string you type in.
15374 Spaces in your input are normally handled specially, but you can turn that
15375 special handling off with the
15376 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
15379 The usual default value for this option is "begins-with".
15381 <End of help on this topic>
15384 ======= h_config_ldap_email_attr =======
15387 <TITLE>LDAP OPTION: EmailAttribute</TITLE>
15390 <H1>LDAP OPTION: EmailAttribute</H1>
15392 This is the name of the attribute that is searched for when looking for
15393 an email address. The default value for this option is "mail" or
15394 "electronicmail".
15395 If the server you are using uses a different attribute name for the email
15396 address, put that attribute name here.
15398 This will affect the search filter used if your Search-Type is one that
15399 contains a search for "email".
15400 It will also cause the attribute value matching this attribute name to be used
15401 as the email address when you look up an entry from the composer.
15403 <End of help on this topic>
15406 ======= h_config_ldap_sn_attr =======
15409 <TITLE>LDAP OPTION: SurnameAttribute</TITLE>
15412 <H1>LDAP OPTION: SurnameAttribute</H1>
15414 This is the name of the attribute that is searched for when looking for
15415 the surname of the entry. The default value for this option is "sn".
15416 If the server you are using uses a different attribute name for the surname,
15417 put that attribute name here.
15418 This will affect the search filter used if your Search-Type is one that
15419 contains a search for "surname".
15421 <End of help on this topic>
15424 ======= h_config_ldap_gn_attr =======
15427 <TITLE>LDAP OPTION: GivennameAttribute</TITLE>
15430 <H1>LDAP OPTION: GivennameAttribute</H1>
15432 This is the name of the attribute that is searched for when looking for
15433 the given name of the entry. The default value for this option is "givenname".
15434 If the server you are using uses a different attribute name for the given name,
15435 put that attribute name here.
15436 This will affect the search filter used if your Search-Type is one that
15437 contains a search for "givenname".
15439 <End of help on this topic>
15442 ======= h_config_ldap_cn_attr =======
15445 <TITLE>LDAP OPTION: NameAttribute</TITLE>
15448 <H1>LDAP OPTION: NameAttribute</H1>
15450 This is the name of the attribute that is searched for when looking for
15451 the name of the entry. The default value for this option is "cn", which
15452 stands for common name.
15453 If the server you are using uses a different attribute name for the name,
15454 put that attribute name here.
15455 This will affect the search filter used if your Search-Type is one that
15456 contains a search for "name".
15458 <End of help on this topic>
15461 ======= h_config_ldap_time =======
15464 <TITLE>LDAP OPTION: Timelimit</TITLE>
15467 <H1>LDAP OPTION: Timelimit</H1>
15469 This places a limit on the number of seconds the LDAP search will continue.
15470 The default is 30 seconds. A value of 0 means no limit. Note that some servers
15471 may place limits of their own on searches.
15473 <End of help on this topic>
15476 ======= h_config_ldap_size =======
15479 <TITLE>LDAP OPTION: Sizelimit</TITLE>
15482 <H1>LDAP OPTION: Sizelimit</H1>
15484 This places a limit on the number of entries returned by the LDAP server.
15485 A value of 0 means no limit. The default is 0. Note that some servers
15486 may place limits of their own on searches.
15488 <End of help on this topic>
15491 ======= h_config_ldap_cust =======
15494 <TITLE>LDAP OPTION: Custom-Search-Filter</TITLE>
15497 <H1>LDAP OPTION: Custom-Search-Filter</H1>
15499 This one is for advanced users only! If you define this, then the
15500 "Search-Type" and "Search-Rule" defined are both ignored.
15501 However, the feature
15502 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
15503 is still in effect.
15504 That is, the space substitution will take place even in a custom filter unless
15507 If your LDAP service stops working and you suspect it might be because
15508 of your custom filter, just delete this filter and try using the
15509 "Search-Type" and "Search-Rule" instead.
15510 Another option that sometimes causes trouble is the
15511 <A HREF="h_config_ldap_base">"Search-Base"</A> option.
15513 This variable may be set to the string representation of an LDAP search
15514 filter (see RFC1960). In the places where you want the address string to be
15515 substituted in, put a '%s' in this filter string. Here are some examples:
15517 A "Search-Type" of "name" with "Search-Rule" of "begins-with"
15518 is equivalent to the "Custom-Search-Filter"
15522 When you try to match against the string "string" the program replaces
15523 the "%s" with "string" (without the quotes). You may have multiple "%s"'s and
15524 they will all be replaced with the string. There is a limit of 10 "%s"'s.
15526 A "Search-Type" of "name-or-email" with "Search-Rule"
15527 of "contains" is equivalent to
15529 (|(cn=*%s*)(mail=*%s*))
15532 If your server uses a different attribute <EM>name</EM> than
15533 Alpine uses by default,
15534 (for example, it uses "rfc822mail" instead of "mail"),
15535 then you may be able to use one or more of the four attribute configuration
15536 options instead of defining a custom filter:
15538 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
15541 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
15544 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
15547 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
15550 <End of help on this topic>
15553 ======= h_composer_abook_comment =======
15556 <TITLE>Addressbook Comment Explained</TITLE>
15559 This is a comment to help you remember what this entry is. The WhereIs
15560 command searches comments so that it is easier to find an entry with a comment
15561 you know about attached to it. This field is not used in the outgoing message.
15563 Look <A HREF="h_edit_nav_cmds">here</A>
15564 to see the available Editing and Navigation commands.
15566 <End of help on this topic>
15569 ======= h_composer_abook_addrs =======
15572 <TITLE>Addressbook Lists</TITLE>
15575 <H1>Addressbook Lists</H1>
15577 This is a list of addresses to send to when sending to this address book
15578 entry. Each member of the list may be an address or another nickname from
15579 any of your address books. If it is an address, it is OK to include the
15580 full name field as well as the electronic address portion of that address.
15581 For example, the following are all legitimate entries in this field:
15583 <DL><DT> </DT>
15584 <DD>john (a nickname in your address book)
15585 <DD>jdoe@some.domain
15586 <DD>John Doe <jdoe@some.domain>
15589 The addresses should be listed separated by commas, just like you would
15590 enter them from the composer.
15594 The only difference between a distribution list and a simple entry with a
15595 single address, is that a distribution list has more than one address
15596 listed in the Addresses: field, whereas a simple personal entry has just
15601 For individual address book entries, if there is a full name in the
15602 Fullname: field (filling in the Fullname: field is not required), it is
15603 used. If the full name is specified in the Address: field and not in the
15604 Fullname: field, then the full name from the Address: field is used.
15608 If you type the nickname of a distribution list from one of your address
15609 books in the Lcc: field, then the full name of that list is used in the
15610 To: field. If you put a list in the To: or Cc: fields, that list will be
15611 expanded into all of its addresses. If the list has a full name, then
15612 that will appear at the beginning of the addresses.
15614 <DL><DT> </DT>
15615 <DD>Sewing Club <john@somewhere>, nancy@something.else, Sal
15616 <sal@here.there>
15619 If the first address in the distribution list also has a full name, then
15620 the list full name and that full name are combined into something like the
15623 <DL><DT> </DT>
15624 <DD>Sewing Club -- John Smith <john@somewhere>
15628 If you specify a list via Lcc, the full name is used in the To: line. If
15629 you specify a list in the To: or Cc: fields, then it uses the same method
15630 as for individual entries for filling in the full name.
15634 For help with editing and navigation commands, check the Help for the
15638 <End of help on this topic>
15641 ======= h_config_role_nick =======
15644 <TITLE>Nickname Explained</TITLE>
15647 <H1>Nickname Explained</H1>
15649 This is a nickname to help you.
15650 You should have a different nickname for each role you define.
15651 The nickname will be used in the SETUP ROLE RULES screen to allow you to
15652 pick a role to edit.
15653 It will also be used when you send a message to let you know you are
15654 sending with a different role than you use by default, and
15655 it will be useful for choosing a role when composing with the Role command
15656 or when composing with one of the Role Uses set to With Confirmation.
15657 This field is not used in the outgoing message.
15659 Look <A HREF="h_edit_nav_cmds">here</A>
15660 to see the available Editing and Navigation commands.
15662 <End of help on this topic>
15665 ======= h_config_role_comment =======
15668 <TITLE>Comment Explained</TITLE>
15671 <H1>Comment Explained</H1>
15673 This is a comment to help you.
15674 This comment does not play any functional role, it is simply an optional
15675 comment to help you remember what the rule is for.
15677 Look <A HREF="h_edit_nav_cmds">here</A>
15678 to see the available Editing and Navigation commands.
15680 <End of help on this topic>
15683 ======= h_config_other_nick =======
15686 <TITLE>Nickname Explained</TITLE>
15689 <H1>Nickname Explained</H1>
15691 This is a nickname to help you.
15692 You should have a different nickname for each rule you define.
15693 The nickname will be used in the SETUP OTHER RULES screen to allow you to
15694 pick a rule to edit.
15696 Look <A HREF="h_edit_nav_cmds">here</A>
15697 to see the available Editing and Navigation commands.
15699 <End of help on this topic>
15702 ======= h_config_score_nick =======
15705 <TITLE>Nickname Explained</TITLE>
15708 <H1>Nickname Explained</H1>
15710 This is a nickname to help you.
15711 You should have a different nickname for each scoring rule you define.
15712 The nickname will be used in the SETUP SCORING RULES screen to allow you to
15713 pick a rule to edit.
15715 Look <A HREF="h_edit_nav_cmds">here</A>
15716 to see the available Editing and Navigation commands.
15718 <End of help on this topic>
15721 ======= h_config_incol_nick =======
15724 <TITLE>Nickname Explained</TITLE>
15727 <H1>Nickname Explained</H1>
15729 This is a nickname to help you.
15730 You should have a different nickname for each color rule you define.
15731 The nickname will be used in the SETUP INDEX COLOR RULES screen to allow you to
15732 pick a rule to edit.
15734 Look <A HREF="h_edit_nav_cmds">here</A>
15735 to see the available Editing and Navigation commands.
15737 <End of help on this topic>
15740 ======= h_config_filt_nick =======
15743 <TITLE>Nickname Explained</TITLE>
15746 <H1>Nickname Explained</H1>
15748 This is a nickname to help you.
15749 You should have a different nickname for each filtering rule you define.
15750 The nickname will be used in the SETUP FILTERING RULES screen to allow you to
15751 pick a rule to edit.
15753 Look <A HREF="h_edit_nav_cmds">here</A>
15754 to see the available Editing and Navigation commands.
15756 <End of help on this topic>
15759 ======= h_config_score_topat =======
15762 <TITLE>"To:" Pattern Explained</TITLE>
15765 <H1>"To:" Pattern Explained</H1>
15767 Any text you enter as the "To pattern"
15768 will be compared to the recipients from the To: line of
15769 the message being scored.
15770 When the text you entered matches
15771 all or part of the To: line of a message, then the Score Value
15772 you have specified will be added to the score for the message.
15773 (Any other non-blank parts of the Pattern must match, too.)
15776 You may enter a complete email address, part of an address, or a
15777 list of addresses or partial addresses.
15782 To pattern = friend@public.com
15784 To pattern = rated.net
15786 To pattern = xxx@adults.com
15788 fool@motleyfool.com
15792 Each of those are valid To patterns.
15795 Messages match those patterns if any of the
15796 addresses in the To: line of the message contains the pattern.
15797 If the pattern is a list of patterns
15798 (like the last example above) then it is a match if any of the patterns in
15799 the list match any of the addresses in the To: line.
15800 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15801 present for a match.
15802 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15803 address2 must be present.
15804 That is exactly what using a list does.)
15807 Some messages may be "bounced" to you, and will
15808 have a "Resent-To:" header line.
15809 If the message contains a Resent-To: line
15810 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15811 Alpine will look for
15812 matches to your "To patterns" there, and <EM>NOT</EM> in
15813 the original To: line.
15816 When entering a pattern, you may choose an address from your address book
15817 with the "T" command.
15820 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15821 "!" "toggle NOT" command.
15822 This changes the meaning of the To pattern so that it has the opposite meaning.
15823 It will be considered a match if there are no matches between the
15824 addresses in the To: line and the list of To patterns.
15826 Don't make the mistake of putting the "!" in the data field for
15828 For example, if you type the characters "!frizzle" into the To
15829 pattern, the pattern will look like:
15832 To pattern = !frizzle
15835 This means you want to match the 8 character sequence "!frizzle".
15836 In order to match messages that do not have "frizzle" in
15837 their To field, first type the characters "frizzle" followed
15838 by carriage return for the value of the To pattern, then negate it
15839 by typing the "!" command.
15840 It should end up looking like
15843 ! To pattern = frizzle
15846 You are not limited to using the six standard header patterns that are
15847 normally shown (To, From, Sender, Cc, News, and Subject).
15848 You may add any other header to a Pattern by
15849 using the "eXtraHdr" command to specify a different
15850 message header line; and then the Add or Change command to fill in
15851 a pattern for the new header line, just like you would for a standard header.
15853 A technicality: Since comma is the character used to separate multiple
15854 values in a pattern field, you have to escape comma with a backslash (\) if
15855 you want to include a literal comma in the field.
15856 In other words, if you type a backslash followed by a comma it will
15857 be interpreted as a comma by Alpine, instead of as a separator between
15859 All other backslashes are literal backslashes and should not be escaped.
15861 Look "<A HREF="h_rule_patterns">here</A>"
15862 for more information on Patterns.
15864 Look <A HREF="h_edit_nav_cmds">here</A>
15865 to see the available Editing and Navigation commands.
15867 <End of help on this topic>
15870 ======= h_config_incol_topat =======
15873 <TITLE>"To:" Pattern Explained</TITLE>
15876 <H1>"To:" Pattern Explained</H1>
15878 Any text you enter as the "To pattern"
15879 will be compared to the recipients from the To: lines of
15880 the messages in the index.
15881 When the text you entered matches
15882 all or part of the To: line of a message, then the Index Line Color you have
15883 specified will be used for that line in the index.
15884 (Any other non-blank parts of the Pattern must match, too.)
15887 You may enter a complete email address, part of an address, or a
15888 list of addresses or partial addresses.
15893 To pattern = friend@public.com
15894 To pattern = rated.net
15895 To pattern = xxx@adults.com
15897 fool@motleyfool.com
15901 Each of those are valid To patterns.
15904 Messages match those patterns if any of the
15905 addresses in the To: line of the message contains the pattern.
15906 If the pattern is a list of patterns
15907 (like the last example above) then it is a match if any of the patterns in
15908 the list match any of the addresses in the To: line.
15909 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15910 present for a match.
15911 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15912 address2 must be present.
15913 That is exactly what using a list does.)
15916 Some messages may be "bounced" to you, and will
15917 have a "Resent-To:" header line.
15918 If the message contains a Resent-To: line
15919 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15920 Alpine will look for
15921 matches to your "To patterns" there, and <EM>NOT</EM> in
15922 the original To: line.
15925 When entering a pattern, you may choose an address from your address book
15926 with the "T" command.
15929 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15930 "!" "toggle NOT" command.
15931 This changes the meaning of the To pattern so that it has the opposite meaning.
15932 It will be considered a match if there are no matches between the
15933 addresses in the To: line and the list of To patterns.
15935 Don't make the mistake of putting the "!" in the data field for
15937 For example, if you type the characters "!frizzle" into the To
15938 pattern, the pattern will look like:
15941 To pattern = !frizzle
15944 This means you want to match the 8 character sequence "!frizzle".
15945 In order to match messages that do not have "frizzle" in
15946 their To field, first type the characters "frizzle" followed
15947 by carriage return for the value of the To pattern, then negate it
15948 by typing the "!" command.
15949 It should end up looking like
15952 ! To pattern = frizzle
15956 You are not limited to using the six standard header patterns that are
15957 normally shown (To, From, Sender, Cc, News, and Subject).
15958 You may add any other header to a Pattern by
15959 using the "eXtraHdr" command to specify a different
15960 message header line; and then the Add or Change command to fill in
15961 a pattern for the new header line, just like you would for a standard header.
15963 A technicality: Since comma is the character used to separate multiple
15964 values in a pattern field, you have to escape comma with a backslash (\) if
15965 you want to include a literal comma in the field.
15966 In other words, if you type a backslash followed by a comma it will
15967 be interpreted as a comma by Alpine, instead of as a separator between
15969 All other backslashes are literal backslashes and should not be escaped.
15971 Look "<A HREF="h_rule_patterns">here</A>"
15972 for more information on Patterns.
15974 Look <A HREF="h_edit_nav_cmds">here</A>
15975 to see the available Editing and Navigation commands.
15977 <End of help on this topic>
15980 ======= h_config_other_topat =======
15983 <TITLE>"To:" Pattern Explained</TITLE>
15986 <H1>"To:" Pattern Explained</H1>
15988 For some of the OTHER RULES actions, there is no message that is being
15990 If that is the case, then only the Current Folder Type is checked.
15991 In particular, this To pattern is ignored.
15992 Actions that fall into this category include both
15993 Sort Order and Index Format.
15995 A technicality: Since comma is the character used to separate multiple
15996 values in a pattern field, you have to escape comma with a backslash (\) if
15997 you want to include a literal comma in the field.
15998 In other words, if you type a backslash followed by a comma it will
15999 be interpreted as a comma by Alpine, instead of as a separator between
16001 All other backslashes are literal backslashes and should not be escaped.
16003 Look "<A HREF="h_rule_patterns">here</A>"
16004 for more information on Patterns.
16006 Look <A HREF="h_edit_nav_cmds">here</A>
16007 to see the available Editing and Navigation commands.
16009 <End of help on this topic>
16012 ======= h_config_filt_topat =======
16015 <TITLE>"To:" Pattern Explained</TITLE>
16018 <H1>"To:" Pattern Explained</H1>
16020 Any text you enter as the "To pattern"
16021 will be compared to the recipients from the To: line of
16022 messages when Alpine opens folders.
16023 When the text you entered matches
16024 all or part of the To: line of a message, then the Filter Action you have
16025 specified will be carried out.
16026 (Any other non-blank parts of the Pattern must match, too.)
16029 You may enter a complete email address, part of an address, or a
16030 list of addresses or partial addresses.
16035 To pattern = friend@public.com
16036 To pattern = rated.net
16037 To pattern = xxx@adults.com
16039 fool@motleyfool.com
16043 Each of those are valid To patterns.
16046 Messages match those patterns if any of the
16047 addresses in the To: line of the message contains the pattern.
16048 If the pattern is a list of patterns
16049 (like the last example above) then it is a match if any of the patterns in
16050 the list match any of the addresses in the To: line.
16051 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
16052 present for a match.
16053 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
16054 address2 must be present.
16055 That is exactly what using a list does.)
16058 Some messages may be "bounced" to you, and will
16059 have a "Resent-To:" header line.
16060 If the message contains a Resent-To: line
16061 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
16062 Alpine will look for
16063 matches to your "To patterns" there, and <EM>NOT</EM> in
16064 the original To: line.
16067 When entering a pattern, you may choose an address from your address book
16068 with the "T" command.
16071 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
16072 "!" "toggle NOT" command.
16073 This changes the meaning of the To pattern so that it has the opposite meaning.
16074 It will be considered a match if there are no matches between the
16075 addresses in the To: line and the list of To patterns.
16077 Don't make the mistake of putting the "!" in the data field for
16079 For example, if you type the characters "!frizzle" into the To
16080 pattern, the pattern will look like:
16083 To pattern = !frizzle
16086 This means you want to match the 8 character sequence "!frizzle".
16087 In order to match messages that do not have "frizzle" in
16088 their To field, first type the characters "frizzle" followed
16089 by carriage return for the value of the To pattern, then negate it
16090 by typing the "!" command.
16091 It should end up looking like
16094 ! To pattern = frizzle
16098 You are not limited to using the six standard header patterns that are
16099 normally shown (To, From, Sender, Cc, News, and Subject).
16100 You may add any other header to a Pattern by
16101 using the "eXtraHdr" command to specify a different
16102 message header line; and then the Add or Change command to fill in
16103 a pattern for the new header line, just like you would for a standard header.
16105 A technicality: Since comma is the character used to separate multiple
16106 values in a pattern field, you have to escape comma with a backslash (\) if
16107 you want to include a literal comma in the field.
16108 In other words, if you type a backslash followed by a comma it will
16109 be interpreted as a comma by Alpine, instead of as a separator between
16111 All other backslashes are literal backslashes and should not be escaped.
16113 Look "<A HREF="h_rule_patterns">here</A>"
16114 for more information on Patterns.
16116 Look <A HREF="h_edit_nav_cmds">here</A>
16117 to see the available Editing and Navigation commands.
16119 <End of help on this topic>
16122 ======= h_config_role_topat =======
16125 <TITLE>"To:" Pattern Explained</TITLE>
16128 <H1>"To:" Pattern Explained</H1>
16130 Any text you enter as the "To pattern"
16131 will be compared to the recipients from the To: line of
16132 the message being replied to or forwarded.
16133 (Any other non-blank parts of the Pattern must match, too.)
16134 In the case of the Compose command, this pattern and the other header
16135 patterns are ignored.
16138 You may enter a complete email address, part of an address, or a
16139 list of addresses or partial addresses.
16144 To pattern = friend@public.com
16145 To pattern = rated.net
16146 To pattern = xxx@adults.com
16148 fool@motleyfool.com
16152 Each of those are valid To patterns.
16155 Messages match those patterns if any of the
16156 addresses in the To: line of the message contains the pattern.
16157 If the pattern is a list of patterns
16158 (like the last example above) then it is a match if any of the patterns in
16159 the list match any of the addresses in the To: line.
16160 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
16161 present for a match.
16162 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
16163 address2 must be present.
16164 That is exactly what using a list does.)
16167 Some messages may be "bounced" to you, and will
16168 have a "Resent-To:" header line.
16169 If the message contains a Resent-To: line
16170 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
16171 Alpine will look for
16172 matches to your "To patterns" there, and <EM>NOT</EM> in
16173 the original To: line.
16176 When entering a pattern, you may choose an address from your address book
16177 with the "T" command.
16180 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
16181 "!" "toggle NOT" command.
16182 This changes the meaning of the To pattern so that it has the opposite meaning.
16183 It will be considered a match if there are no matches between the
16184 addresses in the To: line and the list of To patterns.
16186 Don't make the mistake of putting the "!" in the data field for
16188 For example, if you type the characters "!frizzle" into the To
16189 pattern, the pattern will look like:
16192 To pattern = !frizzle
16195 This means you want to match the 8 character sequence "!frizzle".
16196 In order to match messages that do not have "frizzle" in
16197 their To field, first type the characters "frizzle" followed
16198 by carriage return for the value of the To pattern, then negate it
16199 by typing the "!" command.
16200 It should end up looking like
16203 ! To pattern = frizzle
16207 You are not limited to using the six standard header patterns that are
16208 normally shown (To, From, Sender, Cc, News, and Subject).
16209 You may add any other header to a Pattern by
16210 using the "eXtraHdr" command to specify a different
16211 message header line; and then the Add or Change command to fill in
16212 a pattern for the new header line, just like you would for a standard header.
16214 A technicality: Since comma is the character used to separate multiple
16215 values in a pattern field, you have to escape comma with a backslash (\) if
16216 you want to include a literal comma in the field.
16217 In other words, if you type a backslash followed by a comma it will
16218 be interpreted as a comma by Alpine, instead of as a separator between
16220 All other backslashes are literal backslashes and should not be escaped.
16222 Look "<A HREF="h_rule_patterns">here</A>"
16223 for more information on Patterns.
16225 Look <A HREF="h_edit_nav_cmds">here</A>
16226 to see the available Editing and Navigation commands.
16228 <End of help on this topic>
16231 ======= h_config_role_frompat =======
16234 <TITLE>"From:" Pattern Explained</TITLE>
16237 <H1>"From:" Pattern Explained</H1>
16239 This is just like the "To pattern" except that it is compared with
16240 the address in the From: line of the message
16241 instead of the addresses from the To: line.
16242 See the help for the To pattern for more information on header patterns.
16244 Look "<A HREF="h_rule_patterns">here</A>"
16245 for more information on Patterns.
16247 Look <A HREF="h_edit_nav_cmds">here</A>
16248 to see the available Editing and Navigation commands.
16250 <End of help on this topic>
16253 ======= h_config_role_senderpat =======
16256 <TITLE>"Sender:" Pattern Explained</TITLE>
16259 <H1>"Sender:" Pattern Explained</H1>
16261 This is just like the "To pattern" except that it is compared with
16262 the address from the Sender: line of the message
16263 instead of the addresses from the To: line.
16264 See the help for the To pattern for more information on header patterns.
16266 Look "<A HREF="h_rule_patterns">here</A>"
16267 for more information on Patterns.
16269 Look <A HREF="h_edit_nav_cmds">here</A>
16270 to see the available Editing and Navigation commands.
16272 <End of help on this topic>
16275 ======= h_config_role_ccpat =======
16278 <TITLE>"Cc:" Pattern Explained</TITLE>
16281 <H1>"Cc:" Pattern Explained</H1>
16283 This is just like the "To pattern" except that it is compared with
16284 the addresses from the Cc: line of the message
16285 instead of the addresses from the To: line.
16286 See the help for the To pattern for more information on header patterns.
16288 Look "<A HREF="h_rule_patterns">here</A>"
16289 for more information on Patterns.
16291 Look <A HREF="h_edit_nav_cmds">here</A>
16292 to see the available Editing and Navigation commands.
16294 <End of help on this topic>
16297 ======= h_config_role_recippat =======
16300 <TITLE>Recipient Pattern Explained</TITLE>
16303 <H1>Recipient Pattern Explained</H1>
16305 This is just like the "To pattern" except that it is compared with
16306 the addresses from both the To: line and the Cc: line of the
16307 message instead of just the addresses from the To: line.
16308 In other words, it is considered a match if the pattern matches
16309 <EM>EITHER</EM> an address in the To: line <EM>OR</EM> an address
16311 (Notice that defining the Recipient pattern does not have the same
16312 effect as defining both the To and Cc patterns.
16313 Recipient is To <EM>OR</EM> Cc; not To <EM>AND</EM> Cc.
16314 It is equivalent to having two different rules;
16315 one with a To pattern and the other with the same Cc pattern.)
16317 A technicality: Since comma is the character used to separate multiple
16318 values in a pattern field, you have to escape comma with a backslash (\) if
16319 you want to include a literal comma in the field.
16320 In other words, if you type a backslash followed by a comma it will
16321 be interpreted as a comma by Alpine, instead of as a separator between
16323 All other backslashes are literal backslashes and should not be escaped.
16325 Look "<A HREF="h_rule_patterns">here</A>"
16326 for more information on Patterns.
16328 Look <A HREF="h_edit_nav_cmds">here</A>
16329 to see the available Editing and Navigation commands.
16331 <End of help on this topic>
16334 ======= h_config_role_particpat =======
16337 <TITLE>Participant Pattern Explained</TITLE>
16340 <H1>Participant Pattern Explained</H1>
16342 This is just like the "To pattern" except that it is compared with
16343 the addresses from the From: line, the To: line, and the Cc: line of the
16344 message instead of just the addresses from the To: line.
16345 In other words, it is considered a match if the pattern matches
16346 <EM>EITHER</EM> an address in the From: line, <EM>OR</EM> an address
16347 in the To: line, <EM>OR</EM> an address in the Cc: line.
16348 (Notice that defining the Participant pattern does not have the same
16349 effect as defining all of the From, To, and Cc patterns.
16350 Participant is From <EM>OR</EM> To <EM>OR</EM> Cc; not
16351 From <EM>AND</EM> To <EM>AND</EM> Cc.
16352 It is equivalent to having three different rules;
16353 one with a From pattern, another with the same To pattern, and a third with
16354 the same Cc pattern.)
16356 A technicality: Since comma is the character used to separate multiple
16357 values in a pattern field, you have to escape comma with a backslash (\) if
16358 you want to include a literal comma in the field.
16359 In other words, if you type a backslash followed by a comma it will
16360 be interpreted as a comma by Alpine, instead of as a separator between
16362 All other backslashes are literal backslashes and should not be escaped.
16364 Look "<A HREF="h_rule_patterns">here</A>"
16365 for more information on Patterns.
16367 Look <A HREF="h_edit_nav_cmds">here</A>
16368 to see the available Editing and Navigation commands.
16370 <End of help on this topic>
16373 ======= h_config_role_newspat =======
16376 <TITLE>News Pattern Explained</TITLE>
16379 <H1>News Pattern Explained</H1>
16381 If this pattern is non-blank, then for this rule to be considered a
16382 match, at least one of the newsgroups from
16383 the Newsgroups line of the message must match this pattern.
16384 If this pattern is a list of patterns, then at least one of the
16385 newsgroups must match at least one of the patterns.
16386 (Any other non-blank parts of the Pattern must match, too.)
16388 It is possible to add a <EM>NOT</EM> to the News Pattern meaning with the
16389 "!" "toggle NOT" command.
16390 This changes the meaning of the News pattern so that it has the opposite meaning.
16391 It will be considered a match if there are no matches between the
16392 addresses in the Newsgroups: line and the list of News patterns.
16394 Don't make the mistake of putting the "!" in the data field for
16396 For example, if you type the characters "!frizzle" into the News
16397 pattern, the pattern will look like:
16400 News pattern = !frizzle
16403 This means you want to match the 8 character sequence "!frizzle".
16404 In order to match messages that do not have "frizzle" in
16405 their Newsgroups header, first type the characters "frizzle" followed
16406 by carriage return for the value of the News pattern, then negate it
16407 by typing the "!" command.
16408 It should end up looking like
16411 ! News pattern = frizzle
16414 A technicality: Since comma is the character used to separate multiple
16415 values in a pattern field, you have to escape comma with a backslash (\) if
16416 you want to include a literal comma in the field.
16417 In other words, if you type a backslash followed by a comma it will
16418 be interpreted as a comma by Alpine, instead of as a separator between
16420 All other backslashes are literal backslashes and should not be escaped.
16423 Look "<A HREF="h_rule_patterns">here</A>"
16424 for more information on Patterns.
16426 Look <A HREF="h_edit_nav_cmds">here</A>
16427 to see the available Editing and Navigation commands.
16429 <End of help on this topic>
16432 ======= h_config_role_subjpat =======
16435 <TITLE>"Subject:" Pattern Explained</TITLE>
16438 <H1>"Subject:" Pattern Explained</H1>
16440 This is similar to the other parts of the Pattern.
16441 It is compared with
16442 the contents from the Subject of the message.
16444 Look "<A HREF="h_rule_patterns">here</A>"
16445 for more information on Patterns.
16447 It is possible to add a <EM>NOT</EM> to the Subject Pattern meaning with the
16448 "!" "toggle NOT" command.
16449 This changes the meaning of the Subject pattern so that it has the opposite meaning.
16450 It will be considered a match if there are no matches between the
16451 text in the Subject: line and the list of Subject patterns.
16454 If you wish to have a header pattern that is not one of the six standard
16455 header patterns, you may add it with the "eXtraHdr" command.
16457 A technicality: Since comma is the character used to separate multiple
16458 values in a pattern field, you have to escape comma with a backslash (\) if
16459 you want to include a literal comma in the field.
16460 In other words, if you type a backslash followed by a comma it will
16461 be interpreted as a comma by Alpine, instead of as a separator between
16463 All other backslashes are literal backslashes and should not be escaped.
16465 Look <A HREF="h_edit_nav_cmds">here</A>
16466 to see the available Editing and Navigation commands.
16468 <End of help on this topic>
16471 ======= h_config_role_alltextpat =======
16474 <TITLE>AllText Pattern Explained</TITLE>
16477 <H1>AllText Pattern Explained</H1>
16479 This is similar to the header patterns.
16480 Instead of comparing with text in a particular header field it
16481 is compared with all of the text in the message header and body.
16483 It is possible to add a <EM>NOT</EM> to the AllText Pattern meaning with the
16484 "!" "toggle NOT" command.
16485 This changes the meaning of the AllText pattern so that it has the opposite meaning.
16486 It will be considered a match if there are no matches between the
16487 text of the message and the list of AllText patterns.
16489 Don't make the mistake of putting the "!" in the data field for
16491 For example, if you type the characters "!frizzle" into the AllText
16492 pattern, the pattern will look like:
16495 AllText pattern = !frizzle
16498 This means you want to match the 8 character sequence "!frizzle".
16499 In order to match messages that do not have "frizzle" in
16500 the text of the message, first type the characters "frizzle" followed
16501 by carriage return for the value of the AllText pattern, then negate it
16502 by typing the "!" command.
16503 It should end up looking like
16506 ! AllText pattern = frizzle
16509 It is possible that you may notice degraded performance when using
16512 A technicality: Since comma is the character used to separate multiple
16513 values in a pattern field, you have to escape comma with a backslash (\) if
16514 you want to include a literal comma in the field.
16515 In other words, if you type a backslash followed by a comma it will
16516 be interpreted as a comma by Alpine, instead of as a separator between
16518 All other backslashes are literal backslashes and should not be escaped.
16520 Look "<A HREF="h_rule_patterns">here</A>"
16521 for more information on Patterns.
16523 Look <A HREF="h_edit_nav_cmds">here</A>
16524 to see the available Editing and Navigation commands.
16526 <End of help on this topic>
16529 ======= h_config_role_bodytextpat =======
16532 <TITLE>BodyText Pattern Explained</TITLE>
16535 <H1>BodyText Pattern Explained</H1>
16537 This is similar to the header patterns.
16538 Instead of comparing with text in a particular header field it
16539 is compared with all of the text in the message body.
16541 It is possible to add a <EM>NOT</EM> to the BodyText Pattern meaning with the
16542 "!" "toggle NOT" command.
16543 This changes the meaning of the BodyText pattern so that it has the opposite meaning.
16544 It will be considered a match if there are no matches between the
16545 text of the body of the message and the list of BodyText patterns.
16547 Don't make the mistake of putting the "!" in the data field for
16549 For example, if you type the characters "!frizzle" into the BodyText
16550 pattern, the pattern will look like:
16553 BdyText pattern = !frizzle
16556 This means you want to match the 8 character sequence "!frizzle".
16557 In order to match messages that do not have "frizzle" in
16558 their BodyText, first type the characters "frizzle" followed
16559 by carriage return for the value of the BodyText pattern, then negate it
16560 by typing the "!" command.
16561 It should end up looking like
16564 ! BodyText pattern = frizzle
16567 It is possible that you may notice degraded performance when using
16570 A technicality: Since comma is the character used to separate multiple
16571 values in a pattern field, you have to escape comma with a backslash (\) if
16572 you want to include a literal comma in the field.
16573 In other words, if you type a backslash followed by a comma it will
16574 be interpreted as a comma by Alpine, instead of as a separator between
16576 All other backslashes are literal backslashes and should not be escaped.
16578 Look "<A HREF="h_rule_patterns">here</A>"
16579 for more information on Patterns.
16581 Look <A HREF="h_edit_nav_cmds">here</A>
16582 to see the available Editing and Navigation commands.
16584 <End of help on this topic>
16587 ======= h_config_role_charsetpat =======
16590 <TITLE>Character Set Pattern Explained</TITLE>
16593 <H1>Character Set Pattern Explained</H1>
16595 A message may use one or more character sets.
16596 This part of the Pattern matches messages that make use of
16597 certain specified character sets.
16598 It will be considered a match if a message uses any of the character
16599 sets in the list you give here.
16602 When filling in a value for this field, you may use
16603 the "T" command, which presents you with a large list of
16604 possible character sets to choose from.
16605 You may also just type in the name of a character set, and it need not
16606 be one that Alpine knows about.
16609 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
16610 GB2312) you may also use some shorthand names that Alpine provides.
16611 These names are more understandable shorthand names for sets of
16612 character set names.
16613 Two examples are "Cyrillic" and "Greek".
16614 Selecting one of these shorthand names is equivalent to selecting all of
16615 the character sets that make up the set.
16616 You can see all of these shorthand names and the lists of character sets
16617 they stand for by typing the "T" command.
16620 For the purposes of this Pattern,
16621 Alpine will search through a message for all of the text parts and
16622 collect the character sets declared for each part.
16623 It will also look in the Subject line for a character set used there.
16624 Alpine does not actually look at the text of the message or the text
16625 of the Subject to determine if a declared character set is actually
16626 used, it looks only at the declarations themselves in the MIME part headers
16627 and in the Subject.
16630 It is possible to add a <EM>NOT</EM> to the Character Set Pattern meaning with the
16631 "!" "toggle NOT" command.
16632 This changes the meaning of the Character Set pattern so that
16633 it has the opposite meaning.
16634 It will be considered a match if none of the character sets in the
16635 list are used in a message.
16637 Don't make the mistake of putting the "!" in the data field for
16639 For example, if you type the characters "!GB2312" into the
16640 Character Set pattern, the pattern will look like:
16643 Charset pattern = !GB2312
16646 This means you want to match the 7 character sequence "!GB2312".
16647 In order to match messages that do not have the
16648 character set "GB2312"
16649 set, first type the characters "GB2312" followed
16650 by carriage return for the value of the Character Set pattern, then negate it
16651 by typing the "!" command.
16652 It should end up looking like
16655 ! Charset pattern = GB2312
16658 A technicality: Since comma is the character used to separate multiple
16659 values in a pattern field, you have to escape comma with a backslash (\) if
16660 you want to include a literal comma in the field.
16661 In other words, if you type a backslash followed by a comma it will
16662 be interpreted as a comma by Alpine, instead of as a separator between
16664 All other backslashes are literal backslashes and should not be escaped.
16666 Look "<A HREF="h_rule_patterns">here</A>"
16667 for more information on Patterns.
16669 Look <A HREF="h_edit_nav_cmds">here</A>
16670 to see the available Editing and Navigation commands.
16672 <End of help on this topic>
16675 ======= h_config_role_keywordpat =======
16678 <TITLE>Keyword Pattern Explained</TITLE>
16681 <H1>Keyword Pattern Explained</H1>
16683 A folder may have user-defined keywords.
16684 These are similar to the Important flag, which the user may set using the
16686 The difference is that the Important flag is always present for each folder.
16687 User-defined keywords are picked by the user.
16688 You may add new keywords by defining them in the
16689 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
16690 After you have added a potential keyword with the <!--#echo var="VAR_keywords"--> option,
16691 the Flag command may be used to set or clear the keyword on individual messages.
16692 If you have given a keyword a nickname when configuring it,
16693 that nickname may be used instead of the actual keyword.
16696 When filling in a value for this field, it may be easiest to use
16697 the "T" command, which presents you with a list of the keywords
16698 you have defined to choose from.
16701 This part of the Pattern matches messages with certain keywords set.
16702 It will be considered a match if a message has any of the keywords in the
16704 A keyword that you have not defined using the
16705 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16706 will not be a match.
16709 It is possible to add a <EM>NOT</EM> to the Keyword Pattern meaning with the
16710 "!" "toggle NOT" command.
16711 This changes the meaning of the Keyword pattern so that it has the opposite meaning.
16712 It will be considered a match if none of the keywords in the list are set
16714 A keyword that you have not defined using the
16715 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16716 will not be a match, so a <EM>NOT</EM> of that keyword does match.
16718 Don't make the mistake of putting the "!" in the data field for
16720 For example, if you type the characters "!frizzle" into the Keyword
16721 pattern, the pattern will look like:
16724 Keyword pattern = !frizzle
16727 This means you want to match the 8 character sequence "!frizzle".
16728 In order to match messages that do not have the keyword "frizzle"
16729 set, first type the characters "frizzle" followed
16730 by carriage return for the value of the Keyword pattern, then negate it
16731 by typing the "!" command.
16732 It should end up looking like
16735 ! Keyword pattern = frizzle
16738 A technicality: Since comma is the character used to separate multiple
16739 values in a pattern field, you have to escape comma with a backslash (\) if
16740 you want to include a literal comma in the field.
16741 In other words, if you type a backslash followed by a comma it will
16742 be interpreted as a comma by Alpine, instead of as a separator between
16744 All other backslashes are literal backslashes and should not be escaped.
16746 Look "<A HREF="h_rule_patterns">here</A>"
16747 for more information on Patterns.
16749 Look <A HREF="h_edit_nav_cmds">here</A>
16750 to see the available Editing and Navigation commands.
16752 <End of help on this topic>
16755 ======= h_config_role_arbpat =======
16758 <TITLE>Extra Header Patterns Explained</TITLE>
16761 <H1>Extra Header Patterns Explained</H1>
16763 The header patterns that come after the Participant pattern but before the
16764 AllText pattern are extra header patterns that you have added to a rule's
16765 Pattern. These are just like the other header patterns except that
16766 the contents of the particular header listed on the left hand side will
16767 be used for comparisons.
16769 The "eXtraHdr" command may be used to add more of these
16770 header patterns to the rule you are editing.
16772 The "RemoveHdr" command may be used to delete the highlighted
16773 extra header pattern from the rule you are editing.
16775 It is possible to add a <EM>NOT</EM> to the Extra Header Pattern meaning with the
16776 "!" "toggle NOT" command.
16777 This changes the meaning of the pattern so that it has the opposite meaning.
16778 It will be considered a match if there are no matches between the
16779 text in the header line and the list of patterns.
16781 Don't make the mistake of putting the "!" in the data field for
16783 For example, if you type the characters "!frizzle" into the
16784 pattern, the pattern will look like:
16787 Xyz pattern = !frizzle
16790 This means you want to match the 8 character sequence "!frizzle".
16791 In order to match messages that do not have "frizzle" in
16792 their Xyz field, first type the characters "frizzle" followed
16793 by carriage return for the value of the pattern, then negate it
16794 by typing the "!" command.
16795 It should end up looking like
16798 ! Xyz pattern = frizzle
16802 A technicality: Since comma is the character used to separate multiple
16803 values in a pattern field, you have to escape comma with a backslash (\) if
16804 you want to include a literal comma in the field.
16805 In other words, if you type a backslash followed by a comma it will
16806 be interpreted as a comma by Alpine, instead of as a separator between
16808 All other backslashes are literal backslashes and should not be escaped.
16810 Look "<A HREF="h_rule_patterns">here</A>"
16811 for more information on Patterns.
16813 Look <A HREF="h_edit_nav_cmds">here</A>
16814 to see the available Editing and Navigation commands.
16816 <End of help on this topic>
16819 ======= h_config_role_cat_cmd =======
16822 <TITLE>Categorizer Command Explained</TITLE>
16825 <H1>Categorizer Command Explained</H1>
16827 This is a command that is run with its standard input set to the message
16828 being checked and its standard output discarded.
16829 The full directory path should be specified.
16830 The command will be run and then its exit status will be checked against
16831 the Exit Status Interval, which defaults to just the value zero.
16832 If the exit status of the command falls in the interval, it is considered
16833 a match, otherwise it is not a match.
16836 This option may actually be a list of commands.
16837 The first one that exists and is executable is used.
16838 That makes it possible to use the same configuration with Unix Alpine and
16842 If none of the commands in the list exists and is executable then the rule
16843 is <EM>not</EM> a match.
16844 If it is possible that the command may not exist, you should be careful
16845 to structure your rules so that nothing destructive
16846 happens when the command does not exist.
16847 For example, you might have a filter that filters away spam when there is
16848 a match but does nothing when there is not a match.
16849 That would cause no harm if the command didn't exist.
16850 However, if you have a filter that filters away spam when there is not
16851 a match and keeps it when there is a match, that would filter everything
16852 if the categorizer command didn't exist.
16854 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
16855 setup for the bogofilter filter.
16858 Look "<A HREF="h_rule_patterns">here</A>"
16859 for more information on Patterns.
16861 Look <A HREF="h_edit_nav_cmds">here</A>
16862 to see the available Editing and Navigation commands.
16864 <End of help on this topic>
16867 ======= h_config_role_cat_cmd_example =======
16870 <TITLE>Categorizer Command Example</TITLE>
16873 <H1>Categorizer Command Example</H1>
16876 (<A HREF="http://bogofilter.sourceforge.net/">http://bogofilter.sourceforge.net/</A>)
16877 is a mail filter that attempts to classify mail as spam or
16878 non-spam using statistical analysis of the message content.
16879 When run with no arguments and a message as standard input, it exits with
16880 exit status 0 if it thinks a message is spam and 1 if it thinks
16882 To use bogofilter as your Categorizer Command you would simply set Command to
16883 the pathname of the bogofilter program.
16886 <CENTER><SAMP>Command = /usr/local/bin/bogofilter</SAMP></CENTER>
16888 Exit status of zero is what you are interested in, so you'd set the
16889 Exit Status Interval to
16891 <CENTER><SAMP>Exit Status Interval = (0,0)</SAMP></CENTER>
16894 In order to prevent downloading an entire huge message to check for spam, you
16895 might want to set the Character Limit to a few thousand characters (the
16896 assumption being that the spam will reveal itself in those characters)
16898 <CENTER><SAMP>Character Limit = 50000</SAMP></CENTER>
16901 You would probably use bogofilter in an Alpine Filter Rule, and have the action
16902 be to move the message to a spam folder.
16903 It would usually be wise to also check the "Message is Recent"
16904 part of the rule so that messages are only checked when they first arrive,
16905 and to restrict the Current Folder Type to just your INBOX.
16906 The reason for checking only Recent messages is to save the time it takes
16907 to run bogofilter on each message.
16908 As an experiment, you might start out by using this in an Indexcolor Rule
16909 instead of a Filter Rule.
16910 In that case, you probably wouldn't check the Recent checkbox.
16912 The use described above assumes that you are somehow maintaining bogofilter's
16913 database of words associated with spam and non-spam messages.
16914 One way to start your database would be to select a bunch of spam messages
16915 in Alpine (you might Save spam messages to a special folder or use Alpine's
16916 Select command to select several) and then Apply
16917 (<A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>)
16918 a pipe command to the spam messages.
16919 For example, you could have a shell script or an alias
16920 called <EM>this_is_spam</EM>, which would simply be the command
16922 <CENTER><SAMP>bogofilter -s</SAMP></CENTER>
16925 It is probably best to use the pipe command's Raw Text, With Delimiter,
16926 and Free Output options,
16927 which are at the bottom of the screen when you type the pipe command.
16928 That's because bogofilter expects the raw message as input, and uses
16929 the Delimiters to tell when a new message starts.
16930 You would not need to use a separate pipe for each message, because
16931 bogofilter can handle multiple messages at once.
16933 Similarly, you would select a group of non-spam messages
16934 and run them through a <EM>this_is_nonspam</EM> script
16935 that was something like
16937 <CENTER><SAMP>bogofilter -n</SAMP></CENTER>
16940 For the more adventurous, the next step might be to automate the upkeep of
16941 the bogofilter database.
16942 It might make more sense to have bogofilter be part of the delivery process,
16943 but it is also possible to do it entirely from within Alpine.
16944 Instead of using just plain "bogofilter" as the Categorizer Command,
16945 the "-u" argument will cause bogofilter to update the database.
16947 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16949 You'd want a couple more aliases or shell scripts called something like
16950 <EM>change_to_spam</EM>
16952 <CENTER><SAMP>bogofilter -Ns</SAMP></CENTER>
16955 <EM>change_to_nonspam</EM>
16957 <CENTER><SAMP>bogofilter -Sn</SAMP></CENTER>
16959 When you run across a message in your INBOX that should have been
16960 classified as spam you would pipe it to the change_to_spam script, and
16961 when you run across a message in your spam folder that should have been
16962 left in your INBOX you would pipe it through change_to_nonspam.
16965 There is a technical problem with this approach.
16966 Alpine may check your filters more than once.
16967 In particular, every time you start Alpine the filters will be checked for
16969 Also, if you have any filters that depend on message state (New, Deleted, etc.)
16970 then Alpine will recheck for matches in messages that have changed state
16971 at the time you close the folder and before expunging.
16972 This is usually ok.
16973 However, in this case it is a problem because the command
16975 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16977 has the side effect of updating the database.
16978 So you run the risk of updating the database multiple times for a single
16979 message instead of updating it just once per message.
16980 There are some ways to work around this problem.
16981 What you need is a way to mark the message after you have run the filter.
16982 One way to mark messages is with the use of a keyword (say "Bogo").
16983 Besides having the filter move the message to a spam folder, also have it
16984 set the Bogo keyword.
16985 (Note that you will have to set up the "Bogo" keyword in the
16986 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in Setup/Config.)
16987 This rule can only set the Bogo keyword for the messages that it matches.
16988 You will also need to add a second rule right after this one that
16989 matches all the messages that don't have the Bogo keyword set
16990 (put the keyword in the Keyword pattern and toggle
16991 the Not with the ! command)
16992 and takes the action of setting it.
16993 Then change the "bogofilter -u" rule so that it won't be a match
16994 (and so it won't re-run the bogofilter command) if the keyword is already
16997 What you will end up with is a rule that runs "bogofilter -u"
16998 on all messages that don't have the Bogo keyword set.
16999 This will have the side effect of inserting that message in the bogofilter
17000 database, match or not.
17001 If this rule matches (it is spam), the Bogo keyword will be set and
17002 the message will be moved to a spam folder.
17003 If it does not match, the
17004 following rule will mark the message by turning on the keyword.
17005 This second rule should be a non-terminating
17006 (<A HREF="h_config_filt_opts_nonterm">Dont-Stop-Even-if-Rule-Matches</A>)
17007 rule so that it doesn't stop the filtering process before the rest of
17008 your rules are consulted.
17011 In summary, the first rule is something like
17013 Nickname = bogofilter -u rule
17014 Current Folder Type =
17018 ! Keyword pattern = Bogo
17020 External Categorizer Commands =
17021 Command = /usr/local/bin/bogofilter -u
17022 Exit Status Interval = (0,0)
17023 Character Limit = <No Value Set: using "-1"> (optionally set this)
17029 Set These Keywords = Bogo
17032 and the following rule is
17034 Nickname = Set Bogo Keyword
17035 Current Folder Type =
17039 ! Keyword pattern = Bogo
17042 (*) Just Set Message Status
17044 Set These Keywords = Bogo
17047 [X] dont-stop-even-if-rule-matches
17050 If it is possible for you to insert bogofilter in the delivery process instead
17051 of having it called from Alpine you could prevent having to wait
17052 for the bogofilter processing while you read your mail.
17053 You would have bogofilter add a header to the message at the time of delivery
17054 that identified it as spam or nonspam.
17055 With this method, you could avoid using a Categorizer Command while running Alpine,
17056 and just match on the header instead.
17057 You might still want to use the scripts mentioned above to initialize the
17058 database or to re-classify wrongly classified messages.
17061 Finally, it isn't for the faint-hearted,
17062 but it is also possible to run bogofilter from PC-Alpine.
17063 You can install Cygwin from
17064 <A HREF="http://www.cygwin.com/">http://www.cygwin.com/</A> and
17065 then compile bogofilter in the cygwin environment, and run it from
17067 You would end up with a Categorizer command that looked something like
17069 <CENTER><SAMP>Command = C:\cygwin\bin\bogofilter.exe -u</SAMP></CENTER>
17071 Note that the ".exe" extension is explicit,
17072 and that the bogofilter.exe executable should be in the same directory
17076 <End of help on this topic>
17079 ======= h_config_role_cat_status =======
17082 <TITLE>Exit Status Interval Explained</TITLE>
17085 <H1>Exit Status Interval Explained</H1>
17087 The categorizer command is run and the result is the exit status of
17089 If that exit status falls in the Exit Status Interval
17090 then it is considered a match, otherwise it is not a match.
17091 Of course for the entire rule to match, it must also be checked against
17092 the other defined parts of the Pattern.
17094 The Exit Status Interval defaults to the single value 0 (zero).
17095 If you define it, it should be set to something like:
17097 <CENTER><SAMP>(min_exit_value,max_exit_value)</SAMP></CENTER>
17099 where "min_exit_value" and "max_exit_value" are integers.
17100 The special values "INF" and "-INF" may be used for large
17101 positive and negative integers.
17103 Actually, a list of intervals may be used if you wish.
17104 A list would look like
17106 <CENTER><SAMP>(min_exit_value1,max_exit_value1),(min_exit_value2,max_exit_value2),...</SAMP></CENTER>
17108 When there is an Exit Status Interval defined, it is a match if the exit status
17109 of the categorizer command is contained in any of the intervals.
17110 The intervals include both endpoints.
17112 The default interval is
17114 <CENTER><SAMP>(0,0)</SAMP></CENTER>
17116 and it matches only if the command exits with exit status equal to zero.
17119 Look "<A HREF="h_rule_patterns">here</A>"
17120 for more information on Patterns.
17122 Look <A HREF="h_edit_nav_cmds">here</A>
17123 to see the available Editing and Navigation commands.
17125 <End of help on this topic>
17128 ======= h_config_role_cat_limit =======
17131 <TITLE>Character Limit Explained</TITLE>
17134 <H1>Character Limit Explained</H1>
17136 Setting this option makes it possible to limit how much of the message
17137 is made available to the categorizer command as input.
17138 The default value (-1) means that the entire message is fed to the
17140 A value of 0 (zero) means that only the headers of the message are
17142 A positive integer means that the headers plus that many characters from
17143 the body of the message are passed to the categorizer.
17146 Look "<A HREF="h_rule_patterns">here</A>"
17147 for more information on Patterns.
17149 Look <A HREF="h_edit_nav_cmds">here</A>
17150 to see the available Editing and Navigation commands.
17152 <End of help on this topic>
17155 ======= h_config_role_age =======
17158 <TITLE>Age Interval Explained</TITLE>
17161 <H1>Age Interval Explained</H1>
17163 The Age Interval, if defined, is part of the Pattern.
17164 If you use this, it should be set to something like:
17166 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
17168 where "min_age" and "max_age" are non-negative integers.
17169 The special value "INF" may be used for the max value.
17170 It represents infinity.
17172 In rare cases it may be useful to use the more general form of the value,
17173 which is a comma-separated list of intervals.
17174 It would look something like:
17176 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
17178 When there is an Age Interval defined, it is a match if the age, in days, of
17179 the message is contained in the interval.
17180 The interval includes both endpoints.
17181 If the option is set to a list of intervals then it is a match if the
17182 age of the message is contained in any of the intervals.
17184 Even though this option is called Age, it isn't actually
17185 the <EM>age</EM> of the message.
17186 Instead, it is how many days ago the message arrived in one of your folders.
17187 If the current time is a little past midnight, then a message that arrived
17188 just before midnight arrived yesterday, even though the message is only
17190 By default, the date being used is not the date in the Date
17191 header of the message.
17192 It is the date that the message arrived in one of your folders.
17193 When you Save a message from one folder to another that arrival date
17195 If you would like to use the date in the Date header that is possible.
17197 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
17198 near the bottom of the rule definition.
17200 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
17203 <CENTER><SAMP>(2,2)</SAMP></CENTER>
17205 matches all messages that arrived on the day before yesterday.
17208 <CENTER><SAMP>(180,INF)</SAMP></CENTER>
17210 matches all messages that arrived at least 180 days before today.
17213 <CENTER><SAMP>(0,1)</SAMP></CENTER>
17215 matches all messages that arrived today or yesterday.
17218 Look "<A HREF="h_rule_patterns">here</A>"
17219 for more information on Patterns.
17221 Look <A HREF="h_edit_nav_cmds">here</A>
17222 to see the available Editing and Navigation commands.
17224 <End of help on this topic>
17227 ======= h_config_role_size =======
17230 <TITLE>Size Interval Explained</TITLE>
17233 <H1>Size Interval Explained</H1>
17235 The Size Interval, if defined, is part of the Pattern.
17236 If you use this, it should be set to something like:
17238 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
17240 where "min_size" and "max_size" are non-negative integers.
17241 The special value "INF" may be used for the max value.
17242 It represents infinity.
17244 In rare cases it may be useful to use the more general form of the value,
17245 which is a comma-separated list of intervals.
17246 It would look something like:
17248 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
17250 When there is a Size Interval defined, it is a match if the size of
17251 the message is contained in the interval.
17252 The interval includes both endpoints.
17253 If the option is set to a list of intervals then it is a match if the
17254 size of the message is contained in any of the intervals.
17258 <CENTER><SAMP>(10000,50000)</SAMP></CENTER>
17260 matches all messages with sizes greater than or equal to 10000, and less
17261 than or equal to 50000.
17264 <CENTER><SAMP>(100000,INF)</SAMP></CENTER>
17266 matches all messages with sizes greater than or equal to 100000.
17269 Look "<A HREF="h_rule_patterns">here</A>"
17270 for more information on Patterns.
17272 Look <A HREF="h_edit_nav_cmds">here</A>
17273 to see the available Editing and Navigation commands.
17275 <End of help on this topic>
17278 ======= h_config_role_scorei =======
17281 <TITLE>Score Interval Explained</TITLE>
17284 <H1>Score Interval Explained</H1>
17286 The Score Interval, if defined, is part of the Pattern.
17287 If you use this, it should be set to something like:
17289 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
17291 where "min_score" and "max_score" are integers between
17293 The special values "-INF" and "INF" may be used for
17294 the min and max values.
17295 These represent negative and positive infinity.
17297 Actually, the value may be a list of intervals rather than just a
17298 single interval if that is useful.
17299 The elements of the list are separated by commas like:
17301 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
17303 When there is a Score Interval defined, it is a match if the score for
17304 the message is contained in any of the intervals.
17305 The intervals include both endpoints.
17306 The score for a message is calculated by looking at every scoring rule
17307 defined and adding up the Score Values for the rules that match the message.
17308 Scoring rules are created using the
17309 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
17312 Look "<A HREF="h_rule_patterns">here</A>"
17313 for more information on Patterns.
17315 Look <A HREF="h_edit_nav_cmds">here</A>
17316 to see the available Editing and Navigation commands.
17318 <End of help on this topic>
17321 ======= h_config_role_fldr_type =======
17324 <TITLE>Current Folder Type Explained</TITLE>
17327 <H1>Current Folder Type Explained</H1>
17329 The Current Folder Type is part of the role's Pattern.
17330 It refers to the type of the currently open folder, which is the folder
17331 you were last looking at from the MESSAGE INDEX or MESSAGE TEXT screen.
17332 In order for a role to be considered a match, the current folder must
17333 be of the type you set here.
17334 The three types "Any", "News", and "Email" are
17335 all what you might think.
17337 If the Current Folder Type for a role's Pattern is set to "News", for
17339 that role will only be a match if the current folder is a newsgroup and
17340 the rest of the Pattern matches.
17341 The value "Specific" may be used when you want to limit the match
17342 to a specific folder (not just a specific type of folder), or to a list of
17345 In order to match a specific folder you Select the "Specific"
17346 button <EM>AND</EM> fill in
17347 the name (or list of names) of
17348 the folder in the "Folder List" field.
17349 If the current folder is any of the folders in the list, that is considered
17351 The name of each folder in the list may be either "INBOX",
17352 the technical specification
17353 of the folder (like what appears in your configuration file) or, if the
17354 folder is one of your incoming folders, it may be the nickname you've given
17356 Here are a couple samples of specific folder names:
17358 <CENTER><SAMP>{monet.art.example.com/user=vincent}mail/art-class</SAMP></CENTER>
17360 <CENTER><SAMP>{news.example.com/nntp/user=peter}#news.comp.mail.pine</SAMP></CENTER>
17362 Observe that in order for an external folder (IMAP, POP, News) to be a match,
17363 you must also add the /user= option in the definition of the incoming folder.
17365 The easiest way to fill in the "Folder List" field is to use
17366 the "T" command that is available when the "Folder List" line is
17367 highlighted, or to use the "Take" command with the configuration
17369 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
17371 Note that you won't be able to edit the "Folder List" line unless the
17372 Current Folder Type is set to "Specific", and any value that
17373 "Folder List" has is ignored unless the type
17374 is set to "Specific".
17376 When reading a newsgroup, there may be a performance penalty
17377 incurred when collecting the information necessary to check a Pattern.
17378 For this reason, the default Current Folder Type is set to "Email".
17380 Look "<A HREF="h_rule_patterns">here</A>"
17381 for more information on Patterns.
17383 Look <A HREF="h_edit_nav_cmds">here</A>
17384 to see the available Editing and Navigation commands.
17386 <End of help on this topic>
17389 ======= h_config_filt_rule_type =======
17392 <TITLE>Filter Action Explained</TITLE>
17395 <H1>Filter Action Explained</H1>
17397 The Filter Action specifies the action to be taken when the Pattern is a
17399 It may be set to "Delete" "Move", or
17400 "Just Set Message Status".
17402 If it is set to "Delete", then the message that matches the
17403 Pattern will be deleted from the open folder.
17405 If it is set to "Move", then the name of the folder to which
17406 the matching message should be moved is given in the "Folder List" field on the
17407 next line of the screen.
17408 A list of folders separated by commas may be given, in which case the
17409 message will be copied to all of the folders in the list before it is
17412 If it is set to neither of those two values (it is set to the value
17413 labeled "Just Set Message Status") then the message status
17414 setting will happen
17415 but the message will not be deleted or moved.
17417 If you are Moving a message you may also set Message Status if you wish.
17419 The easiest way to fill in the "Folder List" field is to use
17420 the T command that is available when the "Folder List" line is
17422 Note that you won't be able to edit the "Folder List" line unless the
17423 Filter Action is set to "Move", and any value that
17424 "Folder List" has is ignored unless the type
17425 is set to "Move".
17427 There are a few tokens that may be used in the names in the Folder List.
17428 They are all related to the date on which the filtering is taking place.
17429 The tokens are words surrounded by underscores.
17430 For example, if you want your filter to move messages to a folder named
17431 <P><CENTER><SAMP>abc-year-mon</SAMP></CENTER><P>
17432 you could specify the folder as
17433 <P><CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER><P>
17434 which would result in a file named something like
17435 <P><CENTER><SAMP>abc-2004-oct</SAMP></CENTER><P>
17437 <P><CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER><P>
17438 which would result in a file named something like
17439 <P><CENTER><SAMP>abc-04-10</SAMP></CENTER><P>
17440 The available tokens are listed
17441 <A HREF="h_index_tokens">here</A>.
17443 Look "<A HREF="h_rule_patterns">here</A>"
17444 for more information on Patterns.
17446 Look <A HREF="h_edit_nav_cmds">here</A>
17447 to see the available Editing and Navigation commands.
17449 <End of help on this topic>
17452 ======= h_config_score_fldr_type =======
17455 <TITLE>Current Folder Type Explained</TITLE>
17458 <H1>Current Folder Type Explained</H1>
17460 The Current Folder Type is part of the scoring rule's Pattern.
17461 It refers to the type of the folder that
17462 the message being scored is in.
17463 In order for a rule to be considered a match, the current folder must
17464 be of the type you set here.
17465 The three types "Any", "News", and "Email" are
17466 all what you might think.
17468 If the Current Folder Type for a Pattern is set to "News", for
17470 that Pattern will only match if the current folder is a newsgroup and
17471 the rest of the Pattern matches.
17472 The value "Specific" may be used when you want to limit the match
17473 to a specific folder (not just a specific type of folder), or to a list of
17476 In order to match a specific folder you Select the "Specific"
17477 button <EM>AND</EM> fill in
17478 the name (or list of names) of
17479 the folder in the "Folder List" field.
17480 If the current folder is any of the folders in the list, that is considered
17482 The name of each folder in the list may be either "INBOX", the technical specification
17483 of the folder (like what appears in your configuration file) or, if the
17484 folder is one of your incoming folders, it may be the nickname you've given
17486 Here are a couple samples of specific folder names:
17488 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17490 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17492 The easiest way to fill in the "Folder List" field is to use
17493 the T command that is available when the "Folder List" line is
17495 Note that you won't be able to edit the "Folder List" line unless the
17496 Current Folder Type is set to "Specific", and any value that
17497 "Folder List" has is ignored unless the type
17498 is set to "Specific".
17500 When reading a newsgroup, there may be a performance penalty
17501 incurred when collecting the information necessary to check a Pattern.
17502 For this reason, the default Current Folder Type is set to "Email".
17503 For example, if you have Index Line Coloring rules that have Score Intervals
17504 defined then the scores for all the visible messages will need to be calculated.
17505 If some of your Scoring rules have
17506 a Current Folder Type of
17507 "Any" or "News" this may cause the MESSAGE INDEX
17508 screen to draw more slowly when in a newsgroup.
17510 Look "<A HREF="h_rule_patterns">here</A>"
17511 for more information on Patterns.
17513 Look <A HREF="h_edit_nav_cmds">here</A>
17514 to see the available Editing and Navigation commands.
17516 <End of help on this topic>
17519 ======= h_config_other_fldr_type =======
17522 <TITLE>Current Folder Type Explained</TITLE>
17525 <H1>Current Folder Type Explained</H1>
17527 The Current Folder Type is part of the rule's Pattern.
17528 It refers to the type of the folder being viewed.
17529 In order for a rule to be considered a match, the current folder must
17530 be of the type you set here.
17531 The three types "Any", "News", and "Email" are
17532 all what you might think.
17534 If the Current Folder Type for a Pattern is set to "News", for
17536 that Pattern will only match if the current folder is a newsgroup.
17537 The value "Specific" may be used when you want to limit the match
17538 to a specific folder (not just a specific type of folder), or to a list of
17541 In order to match a specific folder you Select the "Specific"
17542 button <EM>AND</EM> fill in
17543 the name (or list of names) of
17544 the folder in the "Folder List" field.
17545 If the current folder is any of the folders in the list, that is considered
17547 The name of each folder in the list may be either "INBOX", the technical specification
17548 of the folder (like what appears in your configuration file) or, if the
17549 folder is one of your incoming folders, it may be the nickname you've given
17551 Here are a couple samples of specific folder names:
17553 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17555 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17557 The easiest way to fill in the "Folder List" field is to use
17558 the T command that is available when the "Folder List" line is
17560 Note that you won't be able to edit the "Folder List" line unless the
17561 Current Folder Type is set to "Specific", and any value that
17562 "Folder List" has is ignored unless the type
17563 is set to "Specific".
17565 Look "<A HREF="h_rule_patterns">here</A>"
17566 for more information on Patterns.
17568 Look <A HREF="h_edit_nav_cmds">here</A>
17569 to see the available Editing and Navigation commands.
17571 <End of help on this topic>
17574 ======= h_config_incol_fldr_type =======
17577 <TITLE>Current Folder Type Explained</TITLE>
17580 <H1>Current Folder Type Explained</H1>
17582 The Current Folder Type is part of the Line Coloring rule's Pattern.
17583 It refers to the type of the folder for which the MESSAGE INDEX is
17585 In order for a rule to be considered a match, the current folder must
17586 be of the type you set here.
17587 The three types "Any", "News", and "Email" are
17588 all what you might think.
17590 If the Current Folder Type for a Pattern is set to "News", for
17592 that Pattern will only match if the current folder is a newsgroup and
17593 the rest of the Pattern matches.
17594 The value "Specific" may be used when you want to limit the match
17595 to a specific folder (not just a specific type of folder), or to a list of
17598 In order to match a specific folder you Select the "Specific"
17599 button <EM>AND</EM> fill in
17600 the name (or list of names) of
17601 the folder in the "Folder List" field.
17602 If the current folder is any of the folders in the list, that is considered
17604 The name of each folder in the list may be either "INBOX", the technical specification
17605 of the folder (like what appears in your configuration file) or, if the
17606 folder is one of your incoming folders, it may be the nickname you've given
17608 Here are a couple samples of specific folder names:
17610 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17612 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17614 The easiest way to fill in the "Folder List" field is to use
17615 the T command that is available when the "Folder List" line is
17617 Note that you won't be able to edit the "Folder List" line unless the
17618 Current Folder Type is set to "Specific", and any value that
17619 "Folder List" has is ignored unless the type
17620 is set to "Specific".
17622 When reading a newsgroup, there may be a performance penalty
17623 incurred when collecting the information necessary to check a Pattern.
17624 For this reason, the default Current Folder Type is set to "Email".
17625 For example, a rule with a non-Normal Index Line Color
17626 and a Current Folder Type of
17627 "Any" or "News" may cause the MESSAGE INDEX
17628 screen to draw more slowly when in a newsgroup.
17630 Look "<A HREF="h_rule_patterns">here</A>"
17631 for more information on Patterns.
17633 Look <A HREF="h_edit_nav_cmds">here</A>
17634 to see the available Editing and Navigation commands.
17636 <End of help on this topic>
17639 ======= h_config_filt_fldr_type =======
17642 <TITLE>Current Folder Type Explained</TITLE>
17645 <H1>Current Folder Type Explained</H1>
17647 The Current Folder Type is part of the Filtering rule's Pattern.
17648 It refers to the type of the folder for which the filtering is being done.
17649 In order for a rule to be considered a match, the current folder must
17650 be of the type you set here.
17651 The three types "Any", "News", and "Email" are
17652 all what you might think.
17654 If the Current Folder Type for a Pattern is set to "News", for
17656 that Pattern will only match if the current folder is a newsgroup and
17657 the rest of the Pattern matches.
17658 The value "Specific" may be used when you want to limit the match
17659 to a specific folder (not just a specific type of folder), or to a list of
17662 In order to match a specific folder you Select the "Specific"
17663 button <EM>AND</EM> fill in
17664 the name (or list of names) of
17665 the folder in the "Folder List" field.
17666 If the current folder is any of the folders in the list, that is considered
17668 The name of each folder in the list may be either "INBOX", the technical specification
17669 of the folder (like what appears in your configuration file) or, if the
17670 folder is one of your incoming folders, it may be the nickname you've given
17672 Here are a couple samples of specific folder names:
17674 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17676 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17678 The easiest way to fill in the "Folder List" field is to use
17679 the T command that is available when the "Folder List" line is
17681 Note that you won't be able to edit the "Folder List" line unless the
17682 Current Folder Type is set to "Specific", and any value that
17683 "Folder List" has is ignored unless the type
17684 is set to "Specific".
17686 When reading a newsgroup, there may be a performance penalty
17687 incurred when collecting the information necessary to check a Pattern.
17688 For this reason, the default Current Folder Type is set to "Email".
17689 For example, a rule with a Current Folder Type of either
17690 "Any" or "News" may cause the filtering to happen
17691 more slowly when opening a newsgroup.
17693 Look "<A HREF="h_rule_patterns">here</A>"
17694 for more information on Patterns.
17696 Look <A HREF="h_edit_nav_cmds">here</A>
17697 to see the available Editing and Navigation commands.
17699 <End of help on this topic>
17702 ======= h_config_role_stat_imp =======
17705 <TITLE>Message Important Status Explained</TITLE>
17708 <H1>Message Important Status Explained</H1>
17710 This part of the Pattern may have one of three possible values.
17711 The default value is "Don't care", which matches any message.
17712 The other two values are "Yes", which means the message must be
17713 flagged "Important" in order to be a match; or "No", which
17714 means the message must <EM>not</EM> be flagged "Important" in order
17717 Look "<A HREF="h_rule_patterns">here</A>"
17718 for more information on Patterns.
17720 Look <A HREF="h_edit_nav_cmds">here</A>
17721 to see the available Editing and Navigation commands.
17723 <End of help on this topic>
17726 ======= h_config_role_stat_new =======
17729 <TITLE>Message New Status Explained</TITLE>
17732 <H1>Message New Status Explained</H1>
17734 This part of the Pattern may have one of three possible values.
17735 The default value is "Don't care", which matches any message.
17736 The other two values are "Yes", which means the message must be
17737 "New" in order to be a match; or "No", which
17738 means the message must <EM>not</EM> be "New" in order
17740 "New" is the same as <EM>Unseen</EM> and not "New" is the
17741 same as <EM>Seen</EM>.
17743 The nomenclature for New and Recent is a bit confusing:
17745 New means that the message is Unseen.
17746 It could have been in your mailbox for a long time but if you haven't looked
17747 at it, it is still considered New.
17748 That matches the default Alpine index display that shows an N for such a
17751 Recent means that the message was added to this folder since the last time
17752 you opened the folder.
17753 Alpine also shows an N by default for these types of messages.
17754 If you were to run two copies of Alpine that opened a folder one right after
17755 the other, a message would only show up as Recent in (at most) the first
17758 Look "<A HREF="h_rule_patterns">here</A>"
17759 for more information on Patterns.
17761 Look <A HREF="h_edit_nav_cmds">here</A>
17762 to see the available Editing and Navigation commands.
17764 <End of help on this topic>
17767 ======= h_config_role_stat_recent =======
17770 <TITLE>Message Recent Status Explained</TITLE>
17773 <H1>Message Recent Status Explained</H1>
17775 This part of the Pattern may have one of three possible values.
17776 The default value is "Don't care", which matches any message.
17777 The other two values are "Yes", which means the message must be
17778 "Recent" in order to be a match; or "No", which
17779 means the message must <EM>not</EM> be "Recent" in order
17781 "Recent" means that the message was added to the folder since
17782 the last time the folder was opened.
17783 If more than one mail client has the folder opened, the message will
17784 appear to be "Recent" to only one of the clients.
17786 The nomenclature for New and Recent is a bit confusing:
17788 New means that the message is Unseen.
17789 It could have been in your mailbox for a long time but if you haven't looked
17790 at it, it is still considered New.
17791 That matches the default Alpine index display that shows an N for such a
17794 Recent means that the message was added to this folder since the last time
17795 you opened the folder.
17796 Alpine also shows an N by default for these types of messages.
17797 If you were to run two copies of Alpine that opened a folder one right after
17798 the other, a message would only show up as Recent in (at most) the first
17801 Look "<A HREF="h_rule_patterns">here</A>"
17802 for more information on Patterns.
17804 Look <A HREF="h_edit_nav_cmds">here</A>
17805 to see the available Editing and Navigation commands.
17807 <End of help on this topic>
17810 ======= h_config_role_stat_del =======
17813 <TITLE>Message Deleted Status Explained</TITLE>
17816 <H1>Message Deleted Status Explained</H1>
17818 This part of the Pattern may have one of three possible values.
17819 The default value is "Don't care", which matches any message.
17820 The other two values are "Yes", which means the message must be
17821 marked "Deleted" in order to be a match; or "No", which
17822 means the message must <EM>not</EM> be marked "Deleted" in order
17825 If you are thinking of using this part of the Pattern as a way to prevent
17826 messages from being filtered more than once in a Filter Pattern,
17827 take a look at the Filter Option
17828 <A HREF="h_config_filt_opts_notdel">"Move-Only-if-Not-Deleted"</A>
17830 It should work better than using this field since it will hide the filtered
17831 messages even if they are already Deleted.
17832 That option is at the bottom of the Filter configuration screen.
17834 Look "<A HREF="h_rule_patterns">here</A>"
17835 for more information on Patterns.
17837 Look <A HREF="h_edit_nav_cmds">here</A>
17838 to see the available Editing and Navigation commands.
17840 <End of help on this topic>
17843 ======= h_config_role_stat_ans =======
17846 <TITLE>Message Answered Status Explained</TITLE>
17849 <H1>Message Answered Status Explained</H1>
17851 This part of the Pattern may have one of three possible values.
17852 The default value is "Don't care", which matches any message.
17853 The other two values are "Yes", which means the message must be
17854 marked "Answered" in order to be a match; or "No", which
17855 means the message must <EM>not</EM> be marked "Answered" in order
17858 Look "<A HREF="h_rule_patterns">here</A>"
17859 for more information on Patterns.
17861 Look <A HREF="h_edit_nav_cmds">here</A>
17862 to see the available Editing and Navigation commands.
17864 <End of help on this topic>
17867 ======= h_config_role_abookfrom =======
17870 <TITLE>Address in Address Book Explained</TITLE>
17873 <H1>Address in Address Book Explained</H1>
17875 This option gives you a way to match messages that contain an address
17876 that is in one of your address books.
17877 Only the simple entries in your address books are searched.
17878 Address book distribution lists are ignored!
17880 This part of the Pattern may have one of five possible values.
17881 The default value is "Don't care", which matches any message.
17882 The value "Yes, in any address book" means at least one of the addresses
17883 from the message must be in at least one of your
17884 address books in order to be a match.
17885 The value "No, not in any address book"
17886 means none of the addresses may
17887 be in any of your address books in order to be a match.
17889 The values "Yes, in specific address books" and
17890 "No, not in any of specific address books" are similar but instead
17891 of depending on all address books you are allowed to give a list of address
17893 Usually this would be a single address book but it may be a
17894 list of address books as well.
17895 For each of these "specific" address book options you Select which
17896 of the Specific options you want (Yes or No) <EM>AND</EM> fill in the
17897 name (or list of names) of the address book in the
17898 "Abook List" field.
17899 The names to be used are those that appear in the ADDRESS BOOK LIST screen.
17900 The easiest way to fill in the Abook List field it to use
17901 the "T" command that is available when the "Abook List"
17902 line is highlighted.
17903 Note that you won't be able to edit the "Abook List" line unless the
17904 option is set to one of the two "Specific", values.
17906 The addresses from the message that are checked for are determined by the
17907 setting you have for "Types of addresses to check for in address book".
17908 If you set this to "From" the From address from the message will
17909 be looked up in the address book.
17910 If you set it to "To" instead then the To addresses will be used.
17911 If any of the To addresses are in the address book then it is considered
17912 a match for "Yes" or not a match for "No".
17913 You could set it to both From and To, in which case all of the From and To
17914 addresses are used.
17915 The "Reply-To" and "Sender" cases are a little unusual.
17916 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
17917 exists or the From address if there is no Reply-To address.
17918 Same for the Sender address.
17920 Look "<A HREF="h_rule_patterns">here</A>"
17921 for more information on Patterns.
17923 Look <A HREF="h_edit_nav_cmds">here</A>
17924 to see the available Editing and Navigation commands.
17926 <End of help on this topic>
17929 ======= h_config_inabook_from =======
17932 <TITLE>From</TITLE>
17937 Setting the From line will cause the address from the From header line
17938 of the message to be checked for in the address book.
17940 <End of help on this topic>
17943 ======= h_config_inabook_replyto =======
17946 <TITLE>Reply-To</TITLE>
17951 Setting the Reply-To line will cause the address from the Reply-To header line
17952 of the message to be checked for in the address book.
17953 However, if there is no Reply-To header line in the message the From header
17954 line will be used instead.
17955 We understand this is dumb but we don't have an easy way around it.
17957 <End of help on this topic>
17960 ======= h_config_inabook_sender =======
17963 <TITLE>Sender</TITLE>
17968 Setting the Sender line will cause the address from the Sender header line
17969 of the message to be checked for in the address book.
17970 However, if there is no Sender header line in the message the From header
17971 line will be used instead.
17972 We understand this is dumb but we don't have an easy way around it.
17974 <End of help on this topic>
17977 ======= h_config_inabook_to =======
17985 Setting the To line will cause the address from the To header line
17986 of the message to be checked for in the address book.
17988 <End of help on this topic>
17991 ======= h_config_inabook_cc =======
17999 Setting the CC line will cause the address from the CC header line
18000 of the message to be checked for in the address book.
18002 <End of help on this topic>
18005 ======= h_config_role_stat_8bitsubj =======
18008 <TITLE>Raw 8-bit in Subject Explained</TITLE>
18011 <H1>Raw 8-bit in Subject Explained</H1>
18013 It seems that lots of unwanted email contains unencoded 8-bit characters
18015 Normally, characters with the 8th bit set are not allowed in the Subject
18016 header unless they are MIME-encoded.
18017 This option gives you a way to match messages that have Subjects that
18018 contain unencoded 8-bit characters.
18020 This part of the Pattern may have one of three possible values.
18021 The default value is "Don't care", which matches any message.
18022 The other two values are "Yes", which means the Subject of
18023 the message must contain unencoded 8-bit characters (characters with the
18024 most significant bit set)
18025 in order to be a match; or "No", which
18026 means the Subject must <EM>not</EM>
18027 contain unencoded 8-bit characters in order to be a match.
18029 Look "<A HREF="h_rule_patterns">here</A>"
18030 for more information on Patterns.
18032 Look <A HREF="h_edit_nav_cmds">here</A>
18033 to see the available Editing and Navigation commands.
18035 <End of help on this topic>
18038 ======= h_config_role_bom =======
18041 <TITLE>Beginning of Month</TITLE>
18044 <H1>Beginning of Month</H1>
18046 This option gives you a limited ability to take different actions depending on whether
18047 this is the first time Alpine has been run this month or not.
18048 Though it would be nice to have such an option available, this is not the
18049 same as whether or not this is the first time a paricular folder has been
18051 If you want some action (probably Filtering) to take place in a folder each
18052 month, then you will need to be sure that the folder is opened during the
18053 first Alpine session of the month in order for this option to be helpful.
18055 This part of the Pattern may have one of three possible values.
18056 The default value is "Don't care", which matches any message.
18057 The other two values are "Yes", which means this is the first
18058 time Alpine has been run this month;
18059 or "No", which
18060 means this is not the first time Alpine has been run this month.
18062 Look "<A HREF="h_rule_patterns">here</A>"
18063 for more information on Patterns.
18065 Here are some technical details.
18066 The way that Alpine decides if it is the beginning of the month or not is
18067 to compare today's date with the date stored in the
18068 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
18069 variable in the config file.
18070 If the month of today's date is later than the month stored in the variable,
18071 then this is considered to be the first time you have run Alpine this month, and
18072 that turns the Beginning of the Month option on.
18074 Look <A HREF="h_edit_nav_cmds">here</A>
18075 to see the available Editing and Navigation commands.
18077 <End of help on this topic>
18080 ======= h_config_role_boy =======
18083 <TITLE>Beginning of Year</TITLE>
18086 <H1>Beginning of Year</H1>
18088 This option gives you a limited ability to take different actions depending on whether
18089 this is the first time Alpine has been run this year or not.
18090 Though it would be nice to have such an option available, this is not the
18091 same as whether or not this is the first time a paricular folder has been
18093 If you want some action (probably Filtering) to take place in a folder each
18094 year, then you will need to be sure that the folder is opened during the
18095 first Alpine session of the year in order for this option to be helpful.
18097 This part of the Pattern may have one of three possible values.
18098 The default value is "Don't care", which matches any message.
18099 The other two values are "Yes", which means this is the first
18100 time Alpine has been run this year;
18101 or "No", which
18102 means this is not the first time Alpine has been run this year.
18104 Look "<A HREF="h_rule_patterns">here</A>"
18105 for more information on Patterns.
18107 Here are some technical details.
18108 The way that Alpine decides if it is the beginning of the year or not is
18109 to compare today's date with the date stored in the
18110 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
18111 variable in the config file.
18112 If the year of today's date is later than the year stored in the variable,
18113 then this is considered to be the first time you have run Alpine this year, and
18114 that turns the Beginning of the Year option on.
18116 Look <A HREF="h_edit_nav_cmds">here</A>
18117 to see the available Editing and Navigation commands.
18119 <End of help on this topic>
18122 ======= h_config_role_inick =======
18125 <TITLE>Initialize Values From Role Explained</TITLE>
18128 <H1>Initialize Values From Role Explained</H1>
18130 This is a power user feature.
18131 You will usually want to leave this field empty.
18132 The value of this field is the nickname of another one of your roles.
18133 The Action values from that other role
18134 are used as the initial values of the Action items for this role.
18135 If you put something in any of the action fields for this role, that will
18136 override whatever was in the corresponding field of the initializer role.
18138 You might use this field if the "Action" part of one of your roles
18139 is something you want to use in more than one role.
18140 Instead of filling in those action values again for each role, you
18141 may give the nickname of the role where the values are filled in.
18142 It's just a shortcut way to define Role Actions.
18144 Here's an example to help explain how this works.
18145 Suppose you have a role with nickname "role1" and role1 has
18146 (among other things)
18148 <CENTER><SAMP>Set Reply-To = The Pres <president@example.com></SAMP></CENTER>
18151 If in "role2" you set "Initialize settings using role" to
18152 "role1", then role2 will inherit the Set Reply-To value
18153 from role1 by default (and any of the other inheritable action values
18157 <CENTER><SAMP>Set Reply-To = <No Value Set></SAMP></CENTER>
18159 defined, the Reply-To used with role2 would be "The Pres <president@example.com>"
18160 However, if role2 had
18162 <CENTER><SAMP>Set Reply-To = VP <vicepresident@example.com></SAMP></CENTER>
18164 defined, then the Reply-To used with role2 would be "VP <vicepresident@example.com>" instead.
18167 you may choose a nickname from your list of roles by using the
18168 "T" command.
18169 If the role you are using to initialize also has a role it initializes from,
18170 then that initialization happens first.
18171 That is, inheritance works as expected with the grandparent and
18172 great-grandparent (and so on) roles having the expected effect.
18174 Look <A HREF="h_edit_nav_cmds">here</A>
18175 to see the available Editing and Navigation commands.
18177 <End of help on this topic>
18180 ======= h_config_role_setfrom =======
18183 <TITLE>Set From Explained</TITLE>
18186 <H1>Set From Explained</H1>
18188 This describes part of the action to be taken if the Pattern for this
18190 This field consists of a single address that will be used as the From
18191 address on the message you are sending.
18192 This should be a fully-qualified address like
18194 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
18198 <CENTER><SAMP>user@domain</SAMP></CENTER>
18201 you may choose an address from your address book with the
18202 "T" command.
18204 If this is left blank, then your normal From address will be used.
18206 You may also find it useful to add the changed From address to the
18207 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
18208 configuration option.
18210 Look <A HREF="h_edit_nav_cmds">here</A>
18211 to see the available Editing and Navigation commands.
18213 <End of help on this topic>
18216 ======= h_config_role_setreplyto =======
18219 <TITLE>Set Reply-To Explained</TITLE>
18222 <H1>Set Reply-To Explained</H1>
18224 This describes part of the action to be taken if the Pattern for this
18226 This field consists of a single address that will be used as the Reply-To
18227 address on the message you are sending.
18228 This may be a fully-qualified address like
18230 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
18234 <CENTER><SAMP>user@domain</SAMP></CENTER>
18237 you may choose an address from your address book with the
18238 "T" command.
18240 If this is left blank, then there won't be a Reply-To address unless
18241 you have configured one specially with the
18242 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>"
18243 configuration option.
18245 Look <A HREF="h_edit_nav_cmds">here</A>
18246 to see the available Editing and Navigation commands.
18248 <End of help on this topic>
18251 ======= h_config_role_setfcc =======
18254 <TITLE>Set Fcc Explained</TITLE>
18257 <H1>Set Fcc Explained</H1>
18259 This describes part of the action to be taken if the Pattern for this
18261 This field consists of a single folder name that will be used in
18262 the Fcc field of the message you are sending.
18263 You may put anything here that you would normally type into the Fcc
18264 field from the composer.
18266 In addition, an fcc of "" (two double quotation marks) means
18269 A blank field here means that Alpine will use its normal rules for deciding
18270 the default value of the Fcc field.
18271 For many roles, perhaps most, it may make more sense for you to use the
18272 other Alpine facilities for setting the Fcc.
18273 In particular, if you want the Fcc to depend on who you are sending the
18274 message to then the <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
18275 is probably more useful.
18276 In that case, you would want to leave the Fcc field here blank.
18277 However, if you have a role that depends on who the message you are replying
18278 to was From, or what address that message was sent to;
18279 then it might make sense to set the Fcc for that role here.
18282 you may choose a folder from your folder collections by using the
18283 "T" command.
18285 Look <A HREF="h_edit_nav_cmds">here</A>
18286 to see the available Editing and Navigation commands.
18288 <End of help on this topic>
18291 ======= h_config_role_usesmtp =======
18294 <TITLE>Use SMTP Server Explained</TITLE>
18297 <H1>Use SMTP Server Explained</H1>
18299 This describes part of the action to be taken if the Pattern for this
18301 If this field has a value, then it will be used as the SMTP server
18302 to send mail when this role is being used (unless the SMTP server variable
18303 is set in the system-wide fixed configuration file).
18304 It has the same semantics as the
18305 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
18306 variable in the Setup/Config screen.
18308 If you are using this to post from home when you are at home and from
18309 work when you are at work you need to be careful about postponing messages.
18310 When you postpone a composition that was using a role with this variable
18311 set, the SMTP server list will be saved
18312 with the postponed composition.
18313 It cannot be changed later.
18314 Because of this, you may want to make this a list of SMTP servers
18315 with the preferred server at the front of the list and alternate servers
18317 In your "Home" role you would put the home SMTP server first and
18318 the work SMTP server last.
18319 In your "Work" role you would put the work SMTP server first and
18320 the home SMTP server last.
18321 Then if you start a composition as "Work", postpone
18322 it, and then later resume it from home the work SMTP server will fail but
18323 the home SMTP server later in the list will succeed.
18325 You may be able to simplify things by making the regular
18326 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
18327 variable in the Setup/Config screen a list instead of using roles
18328 to set the SMTP server.
18331 Look <A HREF="h_edit_nav_cmds">here</A>
18332 to see the available Editing and Navigation commands.
18334 <End of help on this topic>
18337 ======= h_config_role_usenntp =======
18340 <TITLE>Use NNTP Server Explained</TITLE>
18343 <H1>Use NNTP Server Explained</H1>
18345 This describes part of the action to be taken if the Pattern for this
18347 If this field has a value, then it will be used as the NNTP server
18348 to post to newsgroups when this role is being used (unless the NNTP server
18350 is set in the system-wide fixed configuration file).
18351 It has the same semantics as the
18352 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
18353 variable in the Setup/Config screen.
18355 This role setting can facilitate posting to the right nntp server for someone
18356 who reads news from various news sources. The feature
18357 <A HREF="h_config_predict_nntp_server">"<!--#echo var="FEAT_predict-nntp-server"-->"</A>
18358 allows for setting the correct <!--#echo var="VAR_nntp-server"--> without having to individually
18359 set a role for that <!--#echo var="VAR_nntp-server"-->, but for greater flexibility, setting
18360 nntp servers for roles may be more desirable for some people.
18362 If you are using this to post from home when you are at home and from
18363 work when you are at work you need to be careful about postponing messages.
18364 When you postpone a composition that was using a role with this variable
18365 set, the NNTP server list will be saved
18366 with the postponed composition.
18367 It cannot be changed later.
18368 Because of this, you may want to make this a list of NNTP servers
18369 with the preferred server at the front of the list and alternate servers
18371 In your "Home" role you would put the home NNTP server first and
18372 the work NNTP server last.
18373 In your "Work" role you would put the work NNTP server first and
18374 the home NNTP server last.
18375 Then if you start a composition as "Work", postpone
18376 it, and then later resume it from home the work NNTP server will fail but
18377 the home NNTP server later in the list will succeed.
18379 You may be able to simplify things by making the regular
18380 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
18381 variable in the Setup/Config screen a list instead of using roles
18382 to set the NNTP server.
18385 Look <A HREF="h_edit_nav_cmds">here</A>
18386 to see the available Editing and Navigation commands.
18388 <End of help on this topic>
18391 ======= h_config_role_setotherhdr =======
18394 <TITLE>Set Other Headers Explained</TITLE>
18397 <H1>Set Other Headers Explained</H1>
18399 This describes part of the action to be taken if the Pattern for this
18401 This field gives you a way to set values for headers besides
18402 "From" and "Reply-To".
18403 If you want to set either of those, use the specific
18404 "Set From" and "Set Reply-To" settings above.
18406 This field is similar to the
18407 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" option.
18408 Each header you specify here must include the header tag
18409 ("To:", "Approved:", etc.)
18410 and may optionally include a value for that header.
18411 In order to see these headers when you compose using this role you
18412 must use the rich header
18413 <!--chtml if pinemode="function_key"-->(F5)
18414 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
18415 Here's an example that shows how you might set the To address.
18417 <CENTER><SAMP>Set Other Hdrs = To: Full Name <user@domain></SAMP></CENTER>
18419 Headers set in this way are different from headers set with the
18420 <!--#echo var="VAR_customized-hdrs"--> option in that the value you give for a header here
18421 will replace any value that already exists.
18422 For example, if you are Replying to a message there will already be at
18423 least one address in the To header (the address you are Replying to).
18424 However, if you Reply using a role that sets the To header, that role's
18425 To header value will be used instead.
18427 Limitation: Because commas are used to separate the list of
18428 Other Headers, it is not possible to have the value of a
18429 header contain a comma;
18430 nor is there currently an "escape" mechanism provided
18433 Look <A HREF="h_edit_nav_cmds">here</A>
18434 to see the available Editing and Navigation commands.
18436 <End of help on this topic>
18439 ======= h_config_role_setlitsig =======
18442 <TITLE>Set Literal Signature Explained</TITLE>
18445 <H1>Set Literal Signature Explained</H1>
18447 This describes part of the action to be taken if the Pattern for this
18449 This field contains the actual text for your signature, as opposed to
18450 the name of a file containing your signature.
18451 If this is defined it takes precedence over any value set in the
18452 "Set Signature" field.
18454 This is simply a different way to store the signature.
18455 The signature is stored inside your Alpine configuration file instead of in
18457 Tokens work the same way they do with
18458 <A HREF="h_config_role_setsig">Set Signature</A>, so refer to the
18459 help text there for more information.
18462 The two character sequence \n (backslash followed by
18463 the character n) will be used to signify a line-break in your signature.
18464 You don't have to enter the \n, but it will be visible in the
18465 CHANGE THIS ROLE RULE window after you are done editing the signature.
18467 Look <A HREF="h_edit_nav_cmds">here</A>
18468 to see the available Editing and Navigation commands.
18470 <End of help on this topic>
18473 ======= h_config_role_setsig =======
18476 <TITLE>Set Signature Explained</TITLE>
18479 <H1>Set Signature Explained</H1>
18481 This describes part of the action to be taken if the Pattern for this
18484 If either the default <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A>
18485 option from Setup/Config
18486 or the "Set LiteralSig" option for this role are defined,
18487 then this option will be ignored.
18488 You can tell that that is the case because the value of this
18489 option will show up as
18491 <CENTER><SAMP><Ignored: using LiteralSig instead></SAMP></CENTER>
18493 You may either use all Literal Signatures (signatures stored in your
18494 configuration file) throughout Alpine, or all signature files.
18495 You can't mix the two.
18497 This field consists of a filename that will be used as the signature
18498 file when using this role.
18500 If the filename is followed by a vertical bar (|) then instead
18501 of reading the contents of the file the file is assumed to be a
18502 program that will produce the text to be used on its standard output.
18503 The program can't have any arguments and doesn't receive any input from Alpine,
18504 but the rest of the processing works as if the contents came from a file.
18506 Instead of storing the data in a local file, the
18507 signature data may be stored remotely in an IMAP folder.
18508 In order to do this,
18509 you must use a remote name for the signature.
18510 A remote signature name might look like:
18512 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
18515 The syntax used here is the same as the syntax used for a remote
18516 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
18517 Note that you may not access an existing signature file remotely,
18518 you have to create a new <EM>folder</EM> that contains the signature data.
18519 If the name you use here for the signature data is a remote name, then when
18520 you edit the file using the "F" command the data will
18521 be saved remotely in the folder.
18522 You aren't required to do anything special to create the folder, it
18523 gets created if you use a remote name.
18526 If you type "F" you may edit the contents of the file (as opposed to
18527 the name of the file) you have specified.
18528 If you type "T" you may use a browser to choose an existing filename.
18530 Besides containing regular text, a signature file may also
18531 contain (or a signature program may produce) tokens that are replaced with text
18532 that depends on the message you are replying to or forwarding.
18533 The tokens all look like _word_ (a word surrounded by underscores).
18534 For example, if the token
18536 <CENTER><SAMP>_DATE_</SAMP></CENTER>
18538 is included in the text of the signature file, then when you reply to
18539 or forward a message, the token will be replaced with the actual date
18540 the message you are replying to or forwarding was sent.
18542 If you use a role that has a signature file for a plain composition
18543 (that is, not a reply or forward) then there is no original message, so
18544 any tokens that depend on the message will be replaced with nothing.
18545 So if you want a signature file to be useful for new compositions it
18546 shouldn't include any of the tokens that depend on the message being
18547 replied to or forwarded.
18549 The list of available tokens is
18550 <A HREF="h_index_tokens">here</A>.
18552 Actually, for the adventurous, there is a way to conditionally include text based
18553 on whether or not a token would result in specific replacement text.
18554 For example, you could include some text based on whether or not
18555 the _NEWS_ token would result in any newsgroups if it was used.
18556 It's explained in detail
18557 <A HREF="h_reply_token_conditionals">here</A>.
18559 In the very unlikely event that you want to include a literal token in
18560 a signature file, you must precede it with a backslash character.
18561 For example, to include the literal text _DATE_ you must actually use
18563 It is not possible to have a literal backslash followed by an expanded token.
18565 A blank field here means that Alpine will use its normal rules for deciding
18566 which file (if any) to use for the signature file.
18568 An alternate method for storing the signature is available in
18569 <A HREF="h_config_role_setlitsig">Set Literal Signature</A>.
18571 Look <A HREF="h_edit_nav_cmds">here</A>
18572 to see the available Editing and Navigation commands.
18574 <End of help on this topic>
18577 ======= h_config_role_settempl =======
18580 <TITLE>Set Template Explained</TITLE>
18583 <H1>Set Template Explained</H1>
18585 This describes part of the action to be taken if the Pattern for this
18587 This field consists of a filename that will be used as the template
18588 file when using this role.
18589 The template file is a file that is included at the top of the message you
18592 If the filename is followed by a vertical bar (|) then instead
18593 of reading the contents of the file the file is assumed to be a
18594 program that will produce the text to be used on its standard output.
18595 The program can't have any arguments and doesn't receive any input from Alpine,
18596 but the rest of the processing works as if the contents came from a file.
18598 Instead of storing the data in a local file, the
18599 template may be stored remotely in an IMAP folder.
18600 In order to do this,
18601 you must use a remote name for the template.
18602 A remote template name might look like:
18604 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/templ3</SAMP></CENTER>
18607 The syntax used here is the same as the syntax used for a remote
18608 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
18609 Note that you may not access an existing template file remotely,
18610 you have to create a new <EM>folder</EM> that contains the template data.
18611 If the name you use here for the template is a remote name, then when
18612 you edit the file using the "F" command the data will
18613 be saved remotely in the folder.
18614 You aren't required to do anything special to create the folder, it
18615 gets created if you use a remote name.
18617 If you type "F" you may edit the contents of the file (as opposed to
18618 the name of the file) you have specified.
18619 If you type "T" you may use a browser to choose an existing filename.
18621 Besides containing regular text, the template file may also
18622 contain (or a template file program may produce) tokens that are replaced with text
18623 that depends on the message you are replying to or forwarding.
18624 The tokens all look like _word_ (a word surrounded by underscores).
18625 For example, if the token
18627 <CENTER><SAMP>_DATE_</SAMP></CENTER>
18629 is included in the text of the template file, then when you reply to
18630 or forward a message, the token will be replaced with the actual date
18631 the message you are replying to or forwarding was sent.
18633 If you use a role that has a template file for a plain composition
18634 (that is, not a reply or forward) then there is no original message, so
18635 any tokens that depend on the message will be replaced with nothing.
18636 So if you want a template file to be useful for new compositions it
18637 shouldn't include any of the tokens that depend on the message being
18638 replied to or forwarded.
18640 The list of available tokens is
18641 <A HREF="h_index_tokens">here</A>.
18643 Actually, for the adventurous, there is a way to conditionally include text based
18644 on whether or not a token would result in specific replacement text.
18645 For example, you could include some text based on whether or not
18646 the _NEWS_ token would result in any newsgroups if it was used.
18647 It's explained in detail
18648 <A HREF="h_reply_token_conditionals">here</A>.
18650 In the very unlikely event that you want to include a literal token in
18651 a template file, you must precede it with a backslash character.
18652 For example, to include the literal text _DATE_ you must actually use
18654 It is not possible to have a literal backslash followed by an expanded token.
18656 A blank template field means that Alpine will not use a template file when
18657 this role is being used.
18659 Look <A HREF="h_edit_nav_cmds">here</A>
18660 to see the available Editing and Navigation commands.
18662 <End of help on this topic>
18665 ======= h_config_filt_stat_imp =======
18668 <TITLE>Set Important Status Explained</TITLE>
18671 <H1>Set Important Status Explained</H1>
18673 This describes part of the action to be taken if the Pattern for this
18675 If set to "Don't change it" then this does nothing.
18676 If set to "Set this state" then the Important flag is set
18677 for the matching message.
18678 If set to "Clear this state" then the Important flag is cleared
18679 for the matching message.
18680 The important flag usually causes an asterisk to show up in the MESSAGE
18682 It may also be useful when selecting a set of messages
18683 with the Select command.
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_new =======
18694 <TITLE>Set New Status Explained</TITLE>
18697 <H1>Set New 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 New.
18704 If set to "Clear this state" then the
18705 matching message is marked Seen.
18707 Look <A HREF="h_edit_nav_cmds">here</A>
18708 to see the available Editing and Navigation commands.
18710 <End of help on this topic>
18713 ======= h_config_filt_stat_ans =======
18716 <TITLE>Set Answered Status Explained</TITLE>
18719 <H1>Set Answered Status Explained</H1>
18721 This describes part of the action to be taken if the Pattern for this
18723 If set to "Don't change it" then this does nothing.
18724 If set to "Set this state" then the Answered flag is set
18725 for the matching message.
18726 If set to "Clear this state" then the Answered flag is cleared
18727 for the matching message.
18729 Look <A HREF="h_edit_nav_cmds">here</A>
18730 to see the available Editing and Navigation commands.
18732 <End of help on this topic>
18735 ======= h_config_filt_stat_del =======
18738 <TITLE>Set Deleted Status Explained</TITLE>
18741 <H1>Set Deleted Status Explained</H1>
18743 This describes part of the action to be taken if the Pattern for this
18745 If set to "Don't change it" then this does nothing.
18746 If set to "Set this state" then the
18747 matching message is marked Deleted.
18748 If set to "Clear this state" then the
18749 matching message is marked UnDeleted.
18751 You should not use this option unless you are prepared to have matching
18752 messages expunged from the folder permanently.
18753 For example, if you type the Expunge command, this filter is applied
18754 before the expunge, so matching messages will be marked Deleted and then
18755 will be permanently expunged from the folder.
18756 However, since the index isn't redrawn in between the time that the message
18757 is marked Deleted and the time that you are asked to expunge, the only
18758 indication that you are expunging the message comes in the number of messages
18760 The same thing may happen when you close a folder.
18761 It is also possible that an expunge not initiated by you will
18762 delete matching messages.
18764 Look <A HREF="h_edit_nav_cmds">here</A>
18765 to see the available Editing and Navigation commands.
18767 <End of help on this topic>
18770 ======= h_config_role_scoreval =======
18773 <TITLE>Score Value Explained</TITLE>
18776 <H1>Score Value Explained</H1>
18778 A message's score is the sum of the Score Values from all of the Scoring rules
18779 with Patterns that match the message.
18780 The value you give here is the Score Value associated with this rule.
18781 A Score Value is an integer between -100 and 100, with the default
18784 Alternatively, if the
18785 <A HREF="h_config_role_scorehdrtok">"Score From Header"</A>
18787 (on the line right below the "Score Value" field)
18788 then the "Score Value" is ignored and
18789 the "Score From Header" field is used instead.
18791 Look <A HREF="h_edit_nav_cmds">here</A>
18792 to see the available Editing and Navigation commands.
18794 <End of help on this topic>
18797 ======= h_config_role_scorehdrtok =======
18800 <TITLE>Score Value From Header Explained</TITLE>
18803 <H1>Score Value From Header Explained</H1>
18805 This option provides a way to use a number that appears in the headers of your
18806 messages as the message's score, or as a component of that score.
18807 If this field is defined then it is used instead of the "Score Value".
18808 The idea behind this option is that there may be a score embedded in the
18809 headers of messages that has already been calculated outside of Alpine.
18810 For example, messages delivered to you may contain an "X-Spam" header and
18811 somewhere in that header there is a score.
18813 The value for this option is the name of the header followed by parentheses
18814 with two arguments inside:
18816 <CENTER><SAMP>HeaderName(field_number,field_separators)</SAMP></CENTER>
18818 No space is allowed between the comma and the start of the field_separators.
18819 It would be interpreted as the first separator if it was there.
18820 Field 0 is the whole line, Field 1 is the data up to the first separator, Field 2
18821 starts after that and goes to the second separator, and so on.
18822 It's easier to explain with examples.
18824 <CENTER><SAMP>X-Spam(2," ")</SAMP></CENTER>
18826 In the above example the header that is used is the "X-Spam" header.
18827 The value of that header (the part after the colon and the space) is split
18828 into fields separated by spaces.
18830 <CENTER><SAMP>Field1 <space> Field2 <space> Field3 ...</SAMP></CENTER>
18832 The second field is selected and converted to an integer. It only makes sense
18833 if Field2 really is an integer.
18835 Here's an example of a SpamAssassin header.
18836 The exact look of the header will vary, but if your incoming mail
18837 contains headers that look like the following
18839 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
18841 you might want to use the hits value as a score.
18842 Since the score is an integer value you can't make use of the decimal part of
18844 you might split off the hits=10 part as a score by using the characters "="
18845 and "." as your separators.
18847 <CENTER><SAMP>X-Spam-Status(2,"=.")</SAMP></CENTER>
18849 The first field starts with the Y in Yes and goes until the "=" after
18851 The second field is "10" so the score value would be 10.
18853 Another example we've seen has headers that look like
18855 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
18857 Because there are two equals before the 7% the value
18859 <CENTER><SAMP>X-Spam(3,"=%")</SAMP></CENTER>
18861 should capture the probability as the score.
18863 The Score From Header scoring value actually works just like the
18864 regular Score Value in that the rest of the pattern has to match before
18865 it is used and the scores from all the different scoring rules that
18866 match for a particular message are added together.
18867 When using the Score From Header method it may (or may not) make sense to
18868 use only a single scoring rule with a pattern that matches every message.
18870 Look <A HREF="h_edit_nav_cmds">here</A>
18871 to see the available Editing and Navigation commands.
18873 <End of help on this topic>
18876 ======= h_config_role_replyuse =======
18879 <TITLE>Reply Use Explained</TITLE>
18882 <H1>Reply Use Explained</H1>
18884 This option determines how this particular role will be used when Replying
18886 There are three possible values for this option.
18887 The value "Never"
18888 means that this role will not be a candidate for use when Replying.
18889 The role's Pattern will not be checked for a match, however the role will
18890 be available to be manually switched to if there is a confirmation prompt.
18893 The options "With confirmation" and "Without confirmation"
18894 mean that you do want to consider this role when Replying.
18895 For either of these settings, the role's Pattern will be compared with
18896 the message being replied to.
18897 If there is a match then this role will either be used without confirmation
18898 or will be the default when confirmation is asked for, depending on
18899 which of the two options is selected.
18900 If confirmation is requested, you will also have a chance to
18901 manually change the role to any one of your other roles.
18904 You won't be prompted for confirmation if none of your role Patterns
18905 match the message being replied to.
18906 This is independent of the value of the current option.
18907 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18908 feature may be used to change this behavior.
18910 <End of help on this topic>
18913 ======= h_config_role_forwarduse =======
18916 <TITLE>Forward Use Explained</TITLE>
18919 <H1>Forward Use Explained</H1>
18921 This option determines how this particular role will be used when Forwarding
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 Forwarding.
18926 The role's Pattern will not be checked for a match, however the role will
18927 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 Forwarding.
18932 For either of these settings, the role's Pattern will be compared with
18933 the message being forwarded.
18934 If there is a match then this role will either be used without confirmation
18935 or will be the default when confirmation is asked for, depending on
18936 which of the two options is selected.
18937 If confirmation is requested, you will also have a chance to
18938 manually change the role to any one of your other roles.
18941 You won't be prompted for confirmation if none of your role Patterns
18942 match the message being forwarded.
18943 This is independent of the value of the current option.
18944 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18945 feature may be used to change this behavior.
18947 <End of help on this topic>
18950 ======= h_config_role_composeuse =======
18953 <TITLE>Compose Use Explained</TITLE>
18956 <H1>Compose Use Explained</H1>
18958 This option determines how this particular role will be used when Composing
18959 a new message using the "Compose" command.
18960 This does not affect what happens when using the "Role" command
18961 to compose a new message.
18962 The "Role" command allows you to select a role from all of the
18963 roles you have defined, regardless of what Uses you've assigned to those
18967 There are three possible values for this option.
18968 The value "Never"
18969 means that this role will not be a candidate for use when Composing.
18970 The role's Current Folder Type will not be checked for a match, however the role
18971 will be available to be manually switched to if there is a confirmation prompt.
18974 The options "With confirmation" and "Without confirmation"
18975 mean that you do want to consider this role when Composing.
18976 For either of these settings,
18977 the role's Current Folder Type will be checked (since there is no message
18978 to compare with, the rest of the Pattern is considered a match).
18979 If there is a match then this role will either be used without confirmation
18980 or will be the default when confirmation is asked for, depending on
18981 which of the two options is selected.
18982 If confirmation is requested, you will also have a chance to
18983 manually change the role to any one of your other roles.
18986 When using the Compose command the role checking is a little different
18987 because there is no message being replied to or forwarded.
18988 Because of this the Current Folder Type is checked but the header pattern
18989 fields, the AllText pattern, the BodyText pattern, and the Score Interval are all ignored.
18990 A role is considered to be a match if it is a candidate for Compose Use and
18991 its Current Folder Type matches the currently open folder.
18992 This could be useful if you want to set a role based on the folder you
18993 are reading, or the type of folder you are reading.
18996 You won't be prompted for confirmation if none of your role Patterns
18998 This is independent of the value of the current option.
18999 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
19000 feature may be used to change this behavior.
19002 <End of help on this topic>
19005 ======= h_config_filter_folder =======
19008 <TITLE>Filter Folder Explained</TITLE>
19011 <H1>Filter Folder Explained</H1>
19013 When the Filter Action is set to "Move",
19014 the folder or folders specified here will be used to store messages matching
19015 the provided pattern.
19018 If you set the Filter Action to "Move" you must give a folder name
19023 you may choose a folder from your folder collections by using the
19024 "T" command.
19026 Besides regular text, the folder name may also contain
19027 tokens that are replaced with text representing the current date
19028 when you run Alpine.
19029 For example, if the folder name you use is
19031 <CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER>
19033 that is replaced with something like
19035 <CENTER><SAMP>abc-2004-oct</SAMP></CENTER>
19039 <CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER>
19043 <CENTER><SAMP>abc-04-10</SAMP></CENTER>
19045 The token names must be surrounded by underscores in order to be recognized
19047 The tokens that may be used are those that are derived from the current date.
19048 They're listed near the bottom of the list of tokens give
19049 <A HREF="h_index_tokens">here</A>.
19051 Look "<A HREF="h_rule_patterns">here</A>"
19052 for more information on Patterns.
19054 Look <A HREF="h_edit_nav_cmds">here</A>
19055 to see the available Editing and Navigation commands.
19057 <End of help on this topic>
19060 ======= h_config_filter_kw_set =======
19063 <TITLE>Set These Keywords Explained</TITLE>
19066 <H1>Set These Keywords Explained</H1>
19068 This describes part of the action to be taken if the Pattern for this
19070 Read a little about keywords in the help text for the
19071 <A HREF="h_common_flag">Flag</A> command.
19072 This option is a list of keywords that will be Set when there is a match.
19073 If you wish, you may choose keywords from the list of keywords you have
19074 defined with the "T" command.
19075 You may add new keywords by defining them in the
19076 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
19077 If you have given a keyword a nickname when configuring it,
19078 that nickname may be used instead of the actual keyword.
19081 Look <A HREF="h_edit_nav_cmds">here</A>
19082 to see the available Editing and Navigation commands.
19084 <End of help on this topic>
19087 ======= h_config_filter_kw_clr =======
19090 <TITLE>Clear These Keywords Explained</TITLE>
19093 <H1>Clear These Keywords Explained</H1>
19095 This describes part of the action to be taken if the Pattern for this
19097 Read a little about keywords in the help text for the
19098 <A HREF="h_common_flag">Flag</A> command.
19099 This option is a list of keywords that will be Cleared when there is a match.
19100 If you wish, you may choose keywords from the list of keywords you have
19101 defined with the "T" command.
19102 You may add new keywords by defining them in the
19103 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
19104 If you have given a keyword a nickname when configuring it,
19105 that nickname may be used instead of the actual keyword.
19108 Look <A HREF="h_edit_nav_cmds">here</A>
19109 to see the available Editing and Navigation commands.
19111 <End of help on this topic>
19114 ======= h_index_tokens =======
19117 <TITLE>Tokens for Index and Replying</TITLE>
19121 This set of special tokens may be used in the
19122 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option,
19123 in the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
19124 in signature files,
19125 in template files used in
19126 <A HREF="h_rules_roles">"roles"</A>, and in the folder name
19127 that is the target of a Filter Rule.
19128 Some of them aren't available in all situations.
19130 The tokens are used as they appear below for the "<!--#echo var="VAR_index-format"-->"
19131 option, but they must be surrounded by underscores for the
19132 "<!--#echo var="VAR_reply-leadin"-->" option, in signature and template files,
19133 and in the target of Filter Rules.
19137 <H1><EM>Tokens Available for all Cases (except Filter Rules)</EM></H1>
19142 This token represents the Subject the sender gave the message.
19143 Alternatives for use in the index screen are SHORTSUBJECT,
19144 SUBJKEY, SHORTSUBJKEY, SUBJKEYINIT, SHORTSUBJKEYINIT, SUBJECTTEXT,
19145 SUBJKEYTEXT, and SUBJKEYINITTEXT.
19146 You may color the subject text in the MESSAGE INDEX screen differently by using the
19147 <A HREF="h_config_index_subject_color">Index Subject Color</A> and the
19148 <A HREF="h_config_index_opening_color">Index Opening Color</A>
19149 options available from
19150 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19155 This token represents the personal name (or email address if the name
19156 is unavailable) of the person specified in the message's "From:"
19158 You may color the from text in the MESSAGE INDEX screen differently by using the
19159 <A HREF="h_config_index_from_color">Index From Color</A>
19160 option available from
19161 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19166 This is similar to the "FROM" token, only it is always the
19167 email address, never the personal name.
19168 For example, "mailbox@domain".
19173 This is the same as the "ADDRESS" except that the
19174 domain part of the address is left off.
19175 For example, "mailbox".
19180 This token represents the personal name (or email address) of the person
19181 listed in the message's "Sender:" header field.
19186 This token represents the personal names (or email addresses if the names
19187 are unavailable) of the persons specified in the
19188 message's "To:" header field.
19193 This token represents the newsgroups from the
19194 message's "Newsgroups:" header field <EM>and</EM>
19195 the personal names (or email addresses if the names
19196 are unavailable) of the persons specified in the
19197 message's "To:" header field.
19202 Same as "NEWSANDTO" except in the opposite order.
19207 This token represents the newsgroups from the
19208 message's "Newsgroups:" header field.
19213 This token represents the personal names (or email addresses if the names
19214 are unavailable) of the persons specified in the
19215 message's "Cc:" header field.
19220 This token represents the personal names (or email addresses if the names
19221 are unavailable) of the persons specified in both the
19222 message's "To:" header field and
19223 the message's "Cc:" header field.
19226 <DT>NEWSANDRECIPS</DT>
19228 This token represents the newsgroups from the
19229 message's "Newsgroups:" header field <EM>and</EM>
19230 the personal names (or email addresses if the names
19231 are unavailable) of the persons specified in the
19232 message's "To:" and "Cc:" header fields.
19235 <DT>RECIPSANDNEWS</DT>
19237 Same as "NEWSANDRECIPS" except in the opposite order.
19242 This token represents the initials from the personal name
19243 of the person specified in the message's "From:"
19245 If there is no personal name, it is blank.
19250 This token represents the date on which the message was sent, according
19251 to the "Date" header field.
19252 It has the format MMM DD. For example, "Oct 23".
19254 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>,
19255 which adjusts for the timezone the message was sent from,
19256 may have an effect on the value of this token as well as the values of
19257 all of the other DATE or TIME tokens.
19258 Some of the DATE and TIME tokens are displayed in a locale-specific
19259 way unless the option
19260 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is set.
19265 This token represents the date on which the message was sent, according
19266 to the "Date" header field.
19267 It is "Today" if the message was sent today,
19268 "Yesterday" for yesterday,
19269 "Wednesday" if it was last Wednesday, and so on. If the
19270 message is from last year and is more than six months old it includes the year, as well.
19271 See the SMARTDATE alternatives below, as well.
19276 This token represents the most relevant elements of the date on which
19277 the message was sent (according to the "Date" header field),
19278 in a compact form. If the message was sent today, only the time is used
19279 (e.g. "9:22am", "10:07pm"); if it was sent during
19280 the past week, the day of the week and the hour are used
19281 (e.g. "Wed09am", "Thu10pm"); other dates are
19282 given as date, month, and year (e.g. "23Aug00",
19283 "9Apr98").
19286 <DT>SMARTTIME24</DT>
19288 This token has the structure "day hour:minute"
19289 (e.g. "Sun 19:03") for messages dated less than a week
19290 from the current date, or "month day" (e.g.
19291 "Nov 23") for messages dated less than 6 months
19292 ago, or "day/month/year" (e.g "06/Jan/16")
19293 for messages dated more than 6 months ago. It uses 9 characters
19294 of the width of the screen, and it left aligned.
19297 <DT>SMARTDATETIME</DT>
19299 This is a combination of SMARTDATE and SMARTTIME.
19300 It is SMARTDATE unless the SMARTDATE value is "Today", in which
19301 case it is SMARTTIME.
19302 See the SMARTDATETIME alternatives below, as well.
19307 This token represents the date on which the message was sent, according
19308 to the "Date" header field.
19309 It has the format YYYY-MM-DD. For example, "1998-10-23".
19312 <DT>SHORTDATEISO</DT>
19314 This token represents the date on which the message was sent, according
19315 to the "Date" header field.
19316 It has the format YY-MM-DD. For example, "98-10-23".
19319 <DT>SHORTDATE1</DT>
19321 This token represents the date on which the message was sent, according
19322 to the "Date" header field.
19323 It has the format MM/DD/YY. For example, "10/23/98".
19326 <DT>SHORTDATE2</DT>
19328 This token represents the date on which the message was sent, according
19329 to the "Date" header field.
19330 It has the format DD/MM/YY. For example, "23/10/98".
19333 <DT>SHORTDATE3</DT>
19335 This token represents the date on which the message was sent, according
19336 to the "Date" header field.
19337 It has the format DD.MM.YY. For example, "23.10.98".
19340 <DT>SHORTDATE4</DT>
19342 This token represents the date on which the message was sent, according
19343 to the "Date" header field.
19344 It has the format YY.MM.DD. For example, "98.10.23".
19349 This token represents the date on which the message was sent, according
19350 to the "Date" header field.
19351 It has the format MMM DD, YYYY. For example, "Oct 23, 1998".
19354 <DT>SMARTDATE alternatives</DT>
19356 There are several versions of SMARTDATE that are all the same except
19357 for the way they format dates far in the past.
19358 SMARTDATE formats the date using the information from your locale settings
19359 to format the date string. It may end up formatting dates so that they look
19360 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
19362 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
19363 may have an effect on the values of these tokens.
19364 If you want more control you may use one of the following.
19366 <DT>SMARTDATE</DT> <DD>If the option
19367 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
19368 then this will be locale specific. Control this with the
19369 LC_TIME locale setting on a UNIX system. On Windows
19370 the Regional Options control panel may be used to set the Short date
19371 format. At the programming level, the strftime routine is what Alpine
19372 uses to print the date.
19373 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
19374 to SMARTDATES1.</DD>
19375 <DT>SMARTDATEISO</DT> <DD>DATEISO format. See text above.</DD>
19376 <DT>SMARTDATESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
19377 <DT>SMARTDATES1</DT> <DD>SHORTDATE1 format.</DD>
19378 <DT>SMARTDATES2</DT> <DD>SHORTDATE2 format.</DD>
19379 <DT>SMARTDATES3</DT> <DD>SHORTDATE3 format.</DD>
19380 <DT>SMARTDATES4</DT> <DD>SHORTDATE4 format.</DD>
19384 <DT>SMARTDATETIME alternatives</DT>
19386 There are several versions of SMARTDATETIME that are all very similar.
19387 The ones that end in 24 use a 24-hour clock for Today's messages instead
19388 of a 12-hour clock.
19389 The other variation is
19390 for the way they format dates far in the past.
19391 SMARTDATETIME and SMARTDATETIME24 format the date using the information from your locale settings
19392 to format the date string. It may end up formatting dates so that they look
19393 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
19395 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
19396 may have an effect on the values of these tokens.
19397 The possible choices are:
19399 <DT>SMARTDATETIME</DT> <DD>If the option
19400 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
19401 then this will be locale specific. Control this with the
19402 LC_TIME locale setting on a UNIX system. On Windows
19403 the Regional Options control panel may be used to set the Short date
19404 format. At the programming level, the strftime routine is what Alpine
19405 uses to print the date.
19406 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
19407 to SMARTDATETIMES1.</DD>
19408 <DT>SMARTDATETIME24</DT> <DD>Use TIME24 for Today</DD>
19409 <DT>SMARTDATETIMEISO</DT> <DD>DATEISO format. See text above.</DD>
19410 <DT>SMARTDATETIMEISO24</DT> <DD>Use TIME24 for Today</DD>
19411 <DT>SMARTDATETIMESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
19412 <DT>SMARTDATETIMESHORTISO24</DT> <DD>Use TIME24 for Today</DD>
19413 <DT>SMARTDATETIMES1</DT> <DD>SHORTDATE1 format.</DD>
19414 <DT>SMARTDATETIMES124</DT> <DD>Use TIME24 for Today</DD>
19415 <DT>SMARTDATETIMES2</DT> <DD>SHORTDATE2 format.</DD>
19416 <DT>SMARTDATETIMES224</DT> <DD>Use TIME24 for Today</DD>
19417 <DT>SMARTDATETIMES3</DT> <DD>SHORTDATE3 format.</DD>
19418 <DT>SMARTDATETIMES324</DT> <DD>Use TIME24 for Today</DD>
19419 <DT>SMARTDATETIMES4</DT> <DD>SHORTDATE4 format.</DD>
19420 <DT>SMARTDATETIMES424</DT> <DD>Use TIME24 for Today</DD>
19426 This token represents the date on which the message was sent, according
19427 to the "Date" header field.
19428 It looks like "Sat, 23 Oct 1998".
19429 This token is never converted in any locale-specific way.
19434 This token represents the date on which the message was sent, according
19435 to the "Date" header field.
19436 It is your operating system's idea of the preferred date representation for the current locale.
19437 Internally it uses the %x version of the date from the strftime routine.
19442 This token represents the time at which the message was sent, according
19443 to the "Date" header field.
19444 It is the preferred time representation for the current locale.
19445 Internally it uses the %X version of the time from the strftime routine.
19448 <DT>PREFDATETIME</DT>
19450 This token represents the date and time at which the message was sent, according
19451 to the "Date" header field.
19452 It is the preferred date and time representation for the current locale.
19453 Internally it uses the %c version of the time from the strftime routine.
19458 This token represents the day of the month on which the message was sent,
19459 according to the "Date" header field.
19460 For example, "23" or "9".
19465 This token represents the day of the month on which the message was sent,
19466 according to the "Date" header field.
19467 For example, "23" or "09".
19468 It is always 2 digits.
19471 <DT>DAYORDINAL</DT>
19473 This token represents the ordinal number that is the day of
19474 the month on which the message was sent,
19475 according to the "Date" header field.
19476 For example, "23rd" or "9th".
19481 This token represents the day of the week on which the message was sent,
19482 according to the "Date" header field.
19483 For example, "Sunday" or "Wednesday".
19486 <DT>DAYOFWEEKABBREV</DT>
19488 This token represents the day of the week on which the message was sent,
19489 according to the "Date" header field.
19490 For example, "Sun" or "Wed".
19493 <DT>MONTHABBREV</DT>
19495 This token represents the month the message was sent, according
19496 to the "Date" header field.
19497 For example, "Oct".
19502 This token represents the month in which the message was sent, according
19503 to the "Date" header field.
19504 For example, "October".
19509 This token represents the month in which the message was sent, according
19510 to the "Date" header field.
19511 For example, "10" or "9".
19514 <DT>MONTH2DIGIT</DT>
19516 This token represents the month in which the message was sent, according
19517 to the "Date" header field.
19518 For example, "10" or "09".
19519 It is always 2 digits.
19524 This token represents the year the message was sent, according
19525 to the "Date" header field.
19526 For example, "1998" or "2001".
19529 <DT>YEAR2DIGIT</DT>
19531 This token represents the year the message was sent, according
19532 to the "Date" header field.
19533 For example, "98" or "01".
19534 It is always 2 digits.
19539 This token represents the time at which the message was sent, according
19540 to the "Date" header field.
19541 There is no adjustment made for different time zones, so you'll get
19542 the time the message was sent according to the time zone the sender
19544 It has the format HH:MM. For example, "17:28".
19549 This token represents the time at which the message was sent, according
19550 to the "Date" header field.
19551 This time is for a 12 hour clock.
19552 It has the format HH:MMpm.
19553 For example, "5:28pm" or "11:13am".
19558 This token represents the numeric timezone from
19559 the "Date" header field.
19560 It has the format [+-]HHMM. For example, "-0800".
19566 <H1><EM>Tokens Available Only for <!--#echo var="VAR_index-format"--></EM></H1>
19571 This token represents the message's current position in the folder that,
19572 of course, may change as the folder is sorted or new mail arrives.
19577 This token represents a three character wide field displaying various
19578 aspects of the message's state.
19579 The first character is either blank,
19580 a '*' for message marked Important, or a '+' indicating a message
19581 addressed directly to you (as opposed to your having received it via a
19582 mailing list, for example).
19584 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>"
19585 is set, if the first character would have been
19586 blank then it will instead be a '-' if the message is cc'd to you.
19587 The second character is typically blank,
19588 though the arrow cursor may occupy it if either the
19589 "<A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>"
19591 "<A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A>" feature
19592 is set (or you actually are on a slow link).
19593 The third character is either '<A HREF="h_flag_deleted">D</A>' (Deleted),
19594 '<A HREF="h_flag_answered">A</A>' (Answered),
19595 '<A HREF="h_flag_forwarded">F</A>' (Forwarded),
19596 '<A HREF="h_flag_new">N</A>' (New), or blank.
19598 If you are using a threaded view of the index and this message is at the
19599 top of a collapsed portion of a thread,
19600 then this token refers to all of the messages in the collapsed portion of
19601 the thread instead of just the top message.
19602 The first character will be a '*' if <EM>any</EM> of the messages in the thread
19603 are marked Important, else a '+' if any of the messages are addressed
19604 to you, else a '-' if any of the messages are cc'd to you.
19605 The third character will be a 'D' if <EM>all</EM> of the messages
19606 in the collapsed thread are marked deleted,
19607 an 'A' if <EM>all</EM> of the messages
19608 in the collapsed thread are marked answered,
19609 it will be an 'N' if any of
19610 the messages are undeleted and unseen, and it will be blank otherwise.
19613 <DT>FULLSTATUS</DT>
19615 This token represents a less abbreviated alternative
19616 to the "STATUS" token.
19617 It is six characters wide.
19618 The first character is '+', '-', or blank, the
19619 second blank, the third either '*' or blank, the fourth
19620 '<A HREF="h_flag_new">N</A>' or blank,
19621 the fifth '<A HREF="h_flag_answered">A</A>'
19622 or blank, and the sixth character is
19623 either '<A HREF="h_flag_deleted">D</A>' or
19626 If you are using a threaded view of the index and this message is at the
19627 top of a collapsed portion of a thread,
19628 then this token refers to all of the messages in the collapsed portion of
19629 the thread instead of just the top message.
19630 The first character is '+', '-', or blank depending on whether <EM>any</EM>
19631 of the messages in the collapsed thread are addressed to you or cc'd to you.
19632 The third character will be '*' if any of the messages are marked
19634 The fourth character will be 'N' if all of the messages in the thread
19635 are New, else 'n' if some of the messages in the thread are New, else blank.
19636 The fifth character will be 'A' or 'a' or blank, and the sixth character
19637 will be 'D' or 'd' or blank.
19640 <DT>IMAPSTATUS</DT>
19642 This token represents an even less abbreviated alternative to the
19643 "STATUS" token.
19644 It differs from "FULLSTATUS" in only the fourth character, which is
19645 an 'N' if the message is new to this folder since the last time
19646 it was opened <EM>and</EM> it has not been viewed, an 'R' (Recent) if the message
19647 is new to the folder and has been viewed, a 'U' (Unseen) if the message is not
19648 new to the folder since it was last opened <EM>but</EM> has not been
19649 viewed, or a blank if the message has been in the folder since it was
19650 last opened and has been viewed.
19652 If you are using a threaded view of the index and this message is at the
19653 top of a collapsed portion of a thread,
19654 then the fourth character will be
19655 'N' if all of the messages in the thread are unseen and recent;
19656 else 'n' if some of the messages in the thread are unseen and recent;
19657 else 'U' if all of the messages in the thread are unseen and not recent;
19658 else 'u' if some of the messages in the thread are unseen and not recent;
19659 else 'R' if all of the messages in the thread are seen and recent;
19660 else 'r' if some of the messages in the thread are seen and recent;
19664 <DT>SHORTIMAPSTATUS</DT>
19666 This is the same as the last four of the six characters of IMAPSTATUS,
19667 so the '+' To Me information will be missing.
19672 This token represents the total size, in bytes, of the message.
19673 If a "K" (Kilobyte)
19674 follows the number, the size is approximately 1,000
19675 times that many bytes (rounded to the nearest 1,000).
19676 If an "M" (Megabyte) follows the number, the size is approximately
19677 1,000,000 times that many bytes.
19678 Commas are not used in this field.
19679 This field is seven characters wide, including the enclosing parentheses.
19680 Sizes are rounded when "K" or "M" is present.
19681 The progression of sizes used looks like:
19684 <CENTER><SAMP>0 1 ... 9999 10K ... 999K 1.0M ... 99.9M 100M ... 2000M</SAMP></CENTER>
19690 This token represents the total size, in bytes, of the message.
19691 If a "K" (Kilobyte)
19692 follows the number, the size is approximately 1,000
19693 times that many bytes (rounded to the nearest 1,000).
19694 If an "M" (Megabyte) follows the number, the size is approximately
19695 1,000,000 times that many bytes.
19696 Commas are used if the number shown is 1,000 or greater.
19697 The SIZECOMMA field is one character wider than the SIZE field.
19698 Sizes are rounded when "K" or "M" is present.
19699 The progression of sizes used looks like:
19702 <CENTER><SAMP>0 1 ... 99,999 100K ... 9,999K 10.0M ... 999.9M 1,000M ... 2,000M</SAMP></CENTER>
19708 This token represents the total size of the message, expressed in
19709 kilobytes or megabytes, as most appropriate.
19710 These are 1,024 byte kilobytes and 1,024 x 1,024 byte megabytes.
19711 The progression of sizes used looks like:
19714 <CENTER><SAMP>0K 1K ... 1023K 1.0M ... 99.9M 100M ... 2047M</SAMP></CENTER>
19718 <DT>SIZENARROW</DT>
19720 This token represents the total size, in bytes, of the message.
19721 If a "K" (Kilobyte)
19722 follows the number, the size is approximately 1,000
19723 times that many bytes.
19724 If an "M" (Megabyte) follows the number, the size is approximately
19725 1,000,000 times that many bytes.
19726 If a "G" (Gigabyte) follows the number, the size is approximately
19727 1,000,000,000 times that many bytes.
19728 This field uses only five characters of screen width, including the enclosing
19730 The progression of sizes used looks like:
19733 <CENTER><SAMP>0 1 ... 999 1K ... 99K .1M ... .9M 1M ... 99M .1G ... .9G 1G 2G</SAMP></CENTER>
19737 <DT>DESCRIPSIZE</DT>
19739 This token is intended to represent a more useful description of the
19740 message than just its size, but it isn't very useful at this point.
19741 The plus sign in this view means there are attachments.
19742 Note that including this token in
19743 the "<!--#echo var="VAR_index-format"-->" could slow down the
19744 display a little while Alpine collects the necessary information.
19747 <DT>SHORTSUBJECT</DT>
19748 <DD> This token is the same as SUBJECT, but removes
19749 text between "[" and "]". Typically text enclosed
19750 between these characters corresponds to mailing list names, and may be
19751 unnecessary or unwanted in some instances.
19756 This token is the same as the SUBJECT token unless keywords are set for
19758 In that case, a list of keywords enclosed in braces will be prepended to
19759 the subject of the message.
19760 Only those keywords that you have defined in your
19761 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19762 in Setup/Config are considered in the list.
19763 In other words, keywords that have been set by some other means, perhaps
19764 by another email program, won't show up unless included in
19765 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19766 Having this set in the <!--#echo var="VAR_index-format"--> will also cause the keywords to be
19767 prepended to the subject in the MESSAGE TEXT screen.
19768 If you have given a keyword a nickname
19769 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19770 instead of the actual keyword.
19771 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19772 option may be used to modify this token slightly.
19773 It is also possible to color keywords in the index using the
19774 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19777 <DT>SHORTSUBJKEY</DT>
19778 <DD> This token is the same as SUBJKEY, but it is based on
19779 SHORTSUBJECT, instead of in SUBJECT.
19782 <DT>SUBJKEYINIT</DT>
19784 This token is the same as the SUBJKEY token except that instead of
19785 prepending a list of keywords to the subject, a list of first initials
19786 of keywords will be prepended instead.
19787 For example, if a message has the keywords <EM>Work</EM> and <EM>Now</EM>
19788 set (or Work and Now are the Alpine nicknames of keywords that are set)
19789 then the SUBJKEY token would cause a result like
19791 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
19793 whereas the SUBJKEYINIT token would give
19795 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
19797 Only those keywords that you have defined in your
19798 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19799 in Setup/Config are considered in the list.
19800 In other words, keywords that have been set by some other means, perhaps
19801 by another email program, won't show up unless included in
19802 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19803 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19804 option may be used to modify this token slightly.
19805 It is also possible to color keywords in the index using the
19806 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19809 <DT>SHORTSUBJKEYINIT</DT>
19810 <DD> This token is the same as SUBJKEYINIT, but it is based on
19811 SHORTSUBJECT, instead of in SUBJECT.
19814 <DT>SUBJECTTEXT</DT>
19816 Same as SUBJECT but if there is room in the Subject field for more text,
19817 the opening part of the text of the message is displayed after the subject.
19818 The time needed to fetch the text may cause a performance problem
19819 which can, of course, be avoided by using the SUBJECT version of
19820 the Subject instead.
19821 You may color this opening text differently by using the
19822 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19823 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19824 You may adjust the characters that are displayed between the Subject and the
19825 opening text with the option
19826 <A HREF="h_config_opening_sep"><!--#echo var="VAR_opening-text-separator-chars"--></A>.
19829 <DT>SUBJKEYTEXT</DT>
19831 Same as SUBJKEY but with the opening message text.
19834 <DT>OPENINGTEXT</DT>
19836 This is similar to SUBJECTTEXT.
19837 Instead of combining the Subject and the opening text in a single
19838 field in the index screen this token allows you to allocate a
19839 separate column just for the opening text of the message.
19840 The time needed to fetch this text may cause a performance problem.
19841 You may color this opening text differently by using the
19842 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19843 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19846 <DT>OPENINGTEXTNQ</DT>
19848 This is very similar to OPENINGTEXT.
19849 The NQ stands for No Quotes.
19850 The only difference is that quoted text (lines beginning with >) is deleted.
19851 For some messages this may be confusing.
19852 For example, a message might have a line preceding some quoted
19853 text that reads something like "On May 8th person A said."
19854 That no longer makes sense after the quoted text is deleted and it
19855 will appear that person A said whatever the text after the quote
19856 is, even though that is really person B talking.
19859 <DT>SUBJKEYINITTEXT</DT>
19861 Same as SUBJKEYINIT but with the opening message text.
19866 This is a space-delimited list of keywords that are set for the message.
19867 Only those keywords that you have defined in your
19868 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19869 in Setup/Config are considered in the list.
19870 In other words, keywords that have been set by some other means, perhaps
19871 by another email program, won't show up unless included in
19872 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19873 If you have given a keyword a nickname
19874 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19875 instead of the actual keyword.
19876 It is also possible to color keywords in the index using the
19877 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19878 This token defaults to an arbitrary width of 5.
19879 You should set it to whatever width suits you using something
19880 like KEY(17) in the <!--#echo var="VAR_index-format"-->.
19885 This is a list of keyword initials that are set for the message.
19886 If you have given a keyword a nickname
19887 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), the initial of that nickname
19888 is displayed instead of the initial of the actual keyword.
19889 It is also possible to color keyword initials in the index using the
19890 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19891 This token defaults to an arbitrary width of 2.
19892 You should set it to whatever width suits you using something
19893 like KEYINIT(3) in the <!--#echo var="VAR_index-format"-->.
19898 The X-Priority header is a non-standard header that is used in a
19899 somewhat standard way by many mail programs.
19900 Alpine expects the value of this header to be a digit with a value
19901 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
19902 Since this priority is something that the sender sets it is only an indication
19903 of the priority that the sender attaches to the mail and it is therefore almost
19904 totally unreliable for use as a filtering criterion.
19905 This token will display the numeric value of the priority if it is between
19907 It will be suppressed (blank) if the value is 3, which is normal priority.
19908 This token may be colored with the
19909 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19912 <DT>PRIORITYALPHA</DT>
19914 This is a more verbose interpretation of the X-Priority field.
19915 Once again nothing is displayed unless the value of the field
19917 The values displayed for those values are:
19920 <TR> <TD>1</TD> <TD>Highest</TD> </TR>
19921 <TR> <TD>2</TD> <TD>High</TD> </TR>
19922 <TR> <TD>4</TD> <TD>Low</TD> </TR>
19923 <TR> <TD>5</TD> <TD>Lowest</TD> </TR>
19926 This token may be colored with the
19927 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19932 This is a one character, non-numeric version of the X-Priority field.
19933 If the value of the X-Priority header is 1 or 2 an exclamation
19934 point is displayed.
19935 If the value is 4 or 5 a "v" (think down arrow) is displayed.
19936 This token may be colored with the
19937 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19942 This is a one column wide field that represents the number of attachments
19943 a message has. It will be blank if there are no attachments, a single
19944 digit for one to nine attachments, or an asterisk for more than nine.
19945 Note that including this token in
19946 the "<!--#echo var="VAR_index-format"-->" could slow down the
19947 display a little while Alpine collects the necessary information.
19952 This token represents <EM>either</EM> the personal name (or email address) of
19953 the person listed in the message's "From:" header
19954 field, <EM>or</EM>, if that address is yours or one of your
19955 <A HREF="h_config_alt_addresses">alternate addresses</A>,
19956 the first person specified in the
19957 message's "To:" header field
19958 with the prefix "To: " prepended.
19959 If the from address is yours and there is also no "To" address,
19960 Alpine will use the address on the "Cc" line.
19961 If there is no address there, either, Alpine will look for a newsgroup name
19962 from the "Newsgroups" header field and put
19963 that after the "To: " prefix.
19966 <DT>FROMORTONOTNEWS</DT>
19968 This is almost the same as <EM>FROMORTO</EM>.
19969 The difference is that newsgroups aren't considered.
19970 When a message is from you, doesn't have a To or Cc, and does have
19971 a Newsgroups header; this token will be your name instead of the name
19972 of the newsgroup (like it would be with FROMORTO).
19977 This is a different sort of token.
19978 It allows you to display a label within each index line.
19979 It will be the same fixed text for each line.
19980 It is different from all the other tokens in that there is no space column
19981 displayed after this token.
19982 Instead, it is butted up against the following field.
19983 It also has a different syntax.
19984 The text to display is given following a colon after the
19985 word "TEXT".
19988 <CENTER><SAMP>TEXT:abc=</SAMP></CENTER>
19990 would insert the literal text "abc=" (without the quotes)
19991 into the index display line.
19992 You must quote the text if it includes space characters, like
19994 <CENTER><SAMP>TEXT:"abc = "</SAMP></CENTER>
20000 This allows you to display the text from a particular header line in the
20002 The syntax for this token is substantially different from all the others
20003 in order that you might be able to display a portion of the text following
20004 a particular header.
20005 The header name you are interested in is given following a colon
20006 after the word "HEADER".
20009 <CENTER><SAMP>HEADER:X-Spam</SAMP></CENTER>
20011 would display the text of the X-Spam header, if any.
20012 Like for other index tokens a width field may (and probably should)
20015 <CENTER><SAMP>HEADER:X-Spam(10)</SAMP></CENTER>
20017 displays the first ten characters of the X-Spam header.
20018 Unlike other index tokens, the syntax for HEADER is more flexible.
20019 An optional second argument comes after a comma inside the parentheses.
20020 It specifies the "field" number.
20021 By default, the field separator is a space character.
20022 No extra space characters are allowed in the argument list.
20024 <CENTER><SAMP>HEADER:X-Spam(10,2)</SAMP></CENTER>
20026 would display the second field, left-justified, in a 10 character
20028 The second field would consist of all the text after the first space
20029 up to the next space or the end of the header.
20030 The default field number is zero, which stands for the entire line.
20031 There is also an optional third argument that is a list of field
20032 separators. It defaults to a space character.
20035 <CENTER><SAMP>HEADER:X-Spam(10,2,:% )</SAMP></CENTER>
20037 would cause the field separators to be any of colon, percent,
20038 or space (there is a space character between the percent and the
20039 right parenthesis).
20040 The first field runs from the start of the header value up to the first
20041 colon, percent, or space; the second goes from there to the next; and so on.
20042 In order to use a comma character as a field separator you must escape
20043 it by preceding it with a backslash (\).
20044 The same is true of the backslash character itself.
20045 There is one further optional argument.
20046 It is an R or an L to specify right or left adjustment of the text
20048 The default is to left justify, however if you are displaying numbers
20049 you might prefer to right justify.
20051 Here's an example of a SpamAssassin header.
20052 The exact look of the header will vary, but if your incoming mail
20053 contains headers that look like the following
20055 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
20057 you might want to display the hits value.
20058 The first field starts with the Y in Yes.
20059 To get what you're interested in you might use "=" and
20060 space as the field separators and display the third field, like
20062 <CENTER><SAMP>HEADER:X-Spam-Status(4,3,= )</SAMP></CENTER>
20064 or maybe you would break at the dot instead
20066 <CENTER><SAMP>HEADER:X-Spam-Status(2,2,=.,R)</SAMP></CENTER>
20068 Another example we've seen has headers that look like
20070 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
20072 Because there are two equals and a comma before the 7% and a comma
20073 after it, the token
20075 <CENTER><SAMP>HEADER:X-Spam(3,4,=\,,R)</SAMP></CENTER>
20077 should display the probability (for example 7% or 83%) right justified
20083 This gives an alternative way to display the current message in the
20084 MESSAGE INDEX screen.
20085 Usually the current message is indicated by the line being shown in
20087 Instead, if the ARROW token is included in your <!--#echo var="VAR_index-format"-->,
20088 the current line will include an "arrow" that
20091 <CENTER><SAMP>-></SAMP></CENTER>
20093 in the ARROW token's field.
20094 For all of the non-current messages, the ARROW field will be filled
20096 If you use the fixed-field width feature the length of the "arrow"
20098 The arrow will be drawn as width-1 dashes followed by a greater than sign.
20099 For example, if you use ARROW(3) you will get
20101 <CENTER><SAMP>--></SAMP></CENTER>
20103 and ARROW(1) will give you just
20105 <CENTER><SAMP>></SAMP></CENTER>
20107 It is also possible to set the color of the ARROW field.
20108 By default (and for non-current messages) the arrow is colored the same
20109 as the index line it is part of.
20110 You may set it to be another color with the
20111 <A HREF="h_config_index_arrow_color">Index Arrow Color</A> option available from
20112 the <A HREF="h_color_setup">Setup Kolor</A> screen.
20118 <a href="h_rules_score">score</a>
20120 This will be six columns wide to accomodate the widest possible score.
20121 You will probably want to use the <!--#echo var="VAR_index-format"--> fixed-field width feature
20122 to limit the width of the field to the widest score that
20123 you use (e.g. SCORE(3) if your scores are always between 0 and 999).
20124 If you have not defined any score rules the scores will all be zero.
20125 If any of your score rules contain AllText or BodyText patterns
20126 then including SCORE in the <!--#echo var="VAR_index-format"-->
20127 may slow down the display of the MESSAGE INDEX screen.
20132 <H1><EM>Tokens Available for all but <!--#echo var="VAR_index-format"--></EM></H1>
20137 This token represents the current newsgroup if there is one.
20138 For example, "comp.mail.pine".
20143 This token represents the message ID of the message.
20144 This token does not work with Filter Rule folder names.
20149 This token represents the current date.
20150 It has the format MMM DD. For example, "Oct 23".
20153 <DT>CURDATEISO</DT>
20155 This token represents the current date.
20156 It has the format YYYY-MM-DD. For example, "1998-10-23".
20159 <DT>CURDATEISOS</DT>
20161 This token represents the current date.
20162 It has the format YY-MM-DD. For example, "98-10-23".
20165 <DT>CURPREFDATE</DT>
20167 This token represents the current date.
20168 It is your operating system's idea of the preferred date representation for the current locale.
20169 Internally it uses the %x version of the date from the strftime routine.
20172 <DT>CURPREFTIME</DT>
20174 This token represents the current time.
20175 It is the preferred time representation for the current locale.
20176 Internally it uses the %X version of the time from the strftime routine.
20179 <DT>CURPREFDATETIME</DT>
20181 This token represents the current date and time.
20182 It is the preferred date and time representation for the current locale.
20183 Internally it uses the %c version of the time from the strftime routine.
20188 This token represents the current time.
20189 It has the format HH:MM. For example, "17:28".
20194 This token represents the current time.
20195 This time is for a 12 hour clock.
20196 It has the format HH:MMpm.
20197 For example, "5:28pm" or "11:13am".
20202 This token represents the current day of the month.
20203 For example, "23" or "9".
20206 <DT>CURDAY2DIGIT</DT>
20208 This token represents the current day of the month.
20209 For example, "23" or "09".
20210 It is always 2 digits.
20213 <DT>CURDAYOFWEEK</DT>
20215 This token represents the current day of the week.
20216 For example, "Sunday" or "Wednesday".
20219 <DT>CURDAYOFWEEKABBREV</DT>
20221 This token represents the current day of the week.
20222 For example, "Sun" or "Wed".
20227 This token represents the current month.
20228 For example, "10" or "9".
20231 <DT>CURMONTH2DIGIT</DT>
20233 This token represents the current month.
20234 For example, "10" or "09".
20235 It is always 2 digits.
20238 <DT>CURMONTHLONG</DT>
20240 This token represents the current month.
20241 For example, "October".
20244 <DT>CURMONTHABBREV</DT>
20246 This token represents the current month.
20247 For example, "Oct".
20252 This token represents the current year.
20253 For example, "1998" or "2001".
20256 <DT>CURYEAR2DIGIT</DT>
20258 This token represents the current year.
20259 For example, "98" or "01".
20260 It is always 2 digits.
20265 This token represents last month.
20266 For example, if this is November (the 11th month),
20267 it is equal to "10" or if this is October (the 10th month),
20268 it is "9".
20269 It is possible that this and the other tokens beginning with LASTMONTH
20270 below could be useful when used with a Filtering Rule that
20271 has the "Beginning of Month" option set.
20274 <DT>LASTMONTH2DIGIT</DT>
20276 This token represents last month.
20277 For example, if this is November (the 11th month),
20278 it is equal to "10" or if this is October (the 10th month),
20279 it is "09".
20280 It is always 2 digits.
20283 <DT>LASTMONTHLONG</DT>
20285 This token represents last month.
20286 For example, if this is November the value is "October".
20289 <DT>LASTMONTHABBREV</DT>
20291 This token represents last month.
20292 For example, if this is November the value is "Oct".
20295 <DT>LASTMONTHYEAR</DT>
20297 This token represents what the year was a month ago.
20298 For example, if this is October, 1998, it is "1998".
20299 If this is January, 1998, it is "1997".
20302 <DT>LASTMONTHYEAR2DIGIT</DT>
20304 This token represents what the year was a month ago.
20305 For example, if this is October, 1998, it is "98".
20306 If this is January, 1998, it is "97".
20311 This token represents last year.
20312 For example, if this is 1998, it equals "1997".
20313 It is possible that this
20314 could be useful when used with a Filtering Rule that
20315 has the "Beginning of Year" option set.
20318 <DT>LASTYEAR2DIGIT</DT>
20320 This token represents last year.
20321 For example, if this is 1998, it equals "97".
20322 It is always 2 digits.
20327 This token represents the nickname of the
20328 role currently being used. If no role is being used,
20329 then no text will be printed for this token.
20330 This token does not work with Filter Rule folder names.
20335 <H1><EM>Token Available Only for <!--#echo var="VAR_reply-leadin"--></EM></H1>
20336 See the help for the
20337 <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option
20338 to see why you might want to use this.
20339 Since the <!--#echo var="VAR_reply-leadin"--> contains free text this token
20340 must be surrounded by underscores when used.
20345 This is an end of line marker.
20350 <H1><EM>Token Available Only for Templates and Signatures</EM></H1>
20355 This token is different from the others.
20356 When it is replaced it is replaced with nothing, but it sets an Alpine
20357 internal variable that tells the composer to start with the cursor
20358 positioned at the position where this token was.
20359 If both the template file and the signature file contain
20360 a "CURSORPOS" token, then the position in the template file
20362 If there is a template file and neither it nor the signature file contains
20363 a "CURSORPOS" token, then the cursor is positioned
20364 after the end of the contents of the
20365 template file when the composer starts up.
20370 <End of help on this topic>
20373 ======= h_reply_token_conditionals =======
20376 <TITLE>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</TITLE>
20379 <H1>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</H1>
20381 Conditional text inclusion may be used with
20382 the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
20383 in signature files, and in template files used in
20384 <A HREF="h_rules_roles">"roles"</A>.
20385 It may <EM>not</EM> be used with the
20386 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
20389 There is a limited if-else capability for including text.
20390 The if-else condition is based
20391 on whether or not a given token would result in replacement text you
20393 The syntax of this conditional inclusion is
20395 <CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER>
20397 The left parenthesis must follow the underscore immediately, with no
20399 It means the token is expanded and the results of that expansion are
20400 compared against the "match_this" argument.
20401 If there is an exact match, then the "if_matched" text is used
20402 as the replacement text.
20403 Otherwise, the "if_not_matched" text is used.
20404 One of the most useful values for the "match_this" argument is
20405 the empty string, "".
20406 In that case the expansion is compared against the empty string.
20408 Here's an example to make it clearer.
20409 This text could be included in one of your template files:
20411 <CENTER><SAMP>_NEWS_("", "I'm replying to email", "I'm replying to news")</SAMP></CENTER>
20413 If that is included in a template file that you are using while replying
20414 to a message (because you chose to use the role it was part of),
20415 and that message has a newsgroup header and a newsgroup in that header,
20418 <CENTER><SAMP>I'm replying to news</SAMP></CENTER>
20420 will be included in the message you are about to compose.
20421 On the other hand, if the message you are replying to does not have
20422 a newsgroup, then the text
20424 <CENTER><SAMP>I'm replying to email</SAMP></CENTER>
20426 would be included instead.
20427 This would also work in signature files and in
20428 the "<!--#echo var="VAR_reply-leadin"-->" option.
20429 If the "match_this", "if_matched",
20430 or "if_not_matched" arguments contain
20431 spaces, parentheses, or commas;
20432 they have to be quoted with double quotation marks (like in the example
20434 If you want to include a literal quote (") in the text you must escape the
20435 quote by preceding it with a backslash (\) character.
20436 If you want to include a literal backslash character you must escape it
20437 by preceding it with another backslash.
20439 The comma followed by "if_not_matched" is optional.
20440 If there is no "if_not_matched"
20441 present then no text is included if the not_matched case is true.
20442 Here's another example:
20444 <CENTER><SAMP>_NEWS_("", "", "This msg was seen in group: _NEWS_.")</SAMP></CENTER>
20446 Here you can see that tokens may appear in the arguments.
20447 The same is true for tokens with the conditional parentheses.
20448 They may appear in arguments,
20449 though you do have to be careful to get the quoting and escaping of
20450 nested double quotes correct.
20451 If this was in the signature file being used and you were replying to a message
20452 sent to comp.mail.pine the resulting text would be:
20454 <CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER>
20456 If you were replying to a message that wasn't sent to any newsgroup the
20457 resulting text would be a single blank line.
20458 The reason you'd get a blank line is because the end of the line is
20459 outside of the conditional, so is always included.
20460 If you wanted to get rid of that blank line you could do so by moving
20461 the end of line inside the conditional.
20462 In other words, it's ok to have multi-line
20463 "if_matched" or "if_not_matched" arguments in your
20465 The text just continues until the next double quotation, even if it's not
20468 Here's an example for use in the "<!--#echo var="VAR_reply-leadin"-->":
20470 <CENTER><SAMP>On _DAYDATE_, _FROM__CURNEWS_("", "", "seen in _CURNEWS_,") wrote</SAMP></CENTER>
20472 If this was in your <!--#echo var="VAR_reply-leadin"--> and you were replying to a message
20473 while reading the newsgroup comp.mail.pine the resulting text would be:
20475 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone, seen in comp.mail.pine, wrote:</SAMP></CENTER>
20477 If you were replying to a message while reading an email folder instead
20478 of a newsgroup the resulting leadin text would be
20480 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
20482 Here's one more (contrived) example illustrating a matching argument
20483 that is not the empty string.
20485 <CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER>
20487 If this was the value of your "<!--#echo var="VAR_reply-leadin"-->" option and you
20489 a message that was sent today, then the value of the "<!--#echo var="VAR_reply-leadin"-->"
20492 <CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER>
20494 But if you were replying to a message sent on Oct. 27 (and that wasn't
20495 today) you would get
20497 <CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER>
20500 <End of help on this topic>
20503 ======= h_composer_cntxt_nick =======
20506 <TITLE>Collection Nickname Explained</TITLE>
20509 <H1>Collection Edit Help -- Nickname Field</H1>
20511 This field is provided so you can add a short nickname to use when
20512 referring to this collection within Alpine. Spaces are allowed, and
20513 you don't need to use double-quotes. However, the double-quote
20514 character is not allowed.
20516 Look <A HREF="h_edit_nav_cmds">here</A>
20517 to see the available Editing and Navigation commands.
20519 <End of help on this topic>
20522 ======= h_folder_server_syntax =======
20525 <TITLE>Server Name Syntax</TITLE>
20528 <H1>Server Name Syntax</H1>
20530 This help describes the syntax that may be used for server names
20531 that may be associated with remote folders or SMTP servers.
20534 A server name is the hostname of the server.
20535 It's a good idea to use the host's fully-qualified network name.
20538 <CENTER><SAMP>foo.example.com</SAMP></CENTER>
20541 However, IP addresses are allowed if surrounded
20542 with square-brackets.
20545 <CENTER><SAMP>[127.0.0.1]</SAMP></CENTER>
20548 An optional network port number may be supplied by appending
20549 a colon (:) followed by the port number
20550 to the server name.
20551 By default, the IMAP port number, 143, is used.
20554 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
20557 Besides server name and optional port number, various other optional
20558 parameters may be supplied that alter Alpine's interaction with the server.
20559 A parameter is supplied by appending a slash (/) character followed by
20560 the parameter's name and,
20561 depending on the particular parameter, the value assigned to that
20562 name, to the server name (and optional port number).
20563 Parameter names are <EM>not</EM> case sensitive.
20564 Currently supported parameters include:
20569 <DD>This parameter requires an associated value, and is intended to
20570 provide the username identifier with which to establish the server
20572 If your SMTP server offers SMTP AUTH authentication, adding this
20574 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
20575 option will cause Alpine to attempt to authenticate to the server using the
20577 Similarly, if your NNTP server offers NNTP "AUTHINFO SASL"
20578 or "AUTHINFO USER" authentication, adding this parameter to the
20579 <A HREF="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></A>
20580 option (or to the server name for any folder collection using NNTP)
20581 will cause Alpine to attempt
20582 to authenticate to the server using the supplied username.
20583 An example might be:
20586 <CENTER><SAMP>/user=katie</SAMP></CENTER>
20593 Normally, when a new connection is made an attempt is made to
20594 negotiate a secure (encrypted) session using Transport Layer Security (TLS).
20595 If that fails then a non-encrypted connection will be attempted instead.
20596 This is a unary parameter indicating communication with the server must
20597 take place over a TLS connection. If the attempt to use TLS fails then
20598 this parameter will cause the connection to fail instead of falling
20599 back to an unsecure connection.
20602 <CENTER><SAMP>/tls</SAMP></CENTER>
20609 This is a unary parameter indicating communication with the server should
20610 take place over a Secure Socket Layer connection. The server must support
20611 this method, and be prepared to accept connections on the appropriate
20612 port (993 by default).
20613 Alpine must be linked with an SSL library for this option to be operational.
20616 <CENTER><SAMP>/ssl</SAMP></CENTER>
20623 This parameter indicates that the connection to the server will be made
20624 over the SSL port, but using the TLSv1 protocol, instead of the usual
20625 SSLv3 or SSLv2 protocols.
20626 Alpine must be linked with an SSL library for this option to be operational.
20629 <CENTER><SAMP>/tls1</SAMP></CENTER>
20636 This parameter indicates that the connection to the server will be made
20637 over the SSL port, but using the DTLSv1 protocol, instead of the usual
20638 SSLv3 or SSLv2 protocols.
20639 Alpine must be linked with an SSL library for this option to be operational.
20642 <CENTER><SAMP>/dtls1</SAMP></CENTER>
20649 This parameter indicates that the connection to the server will be made
20650 over the SSL port, but using the TLSv1.1 protocol, instead of the usual
20651 SSLv3 or SSLv2 protocols.
20652 Alpine must be linked with an SSL library for this option to be operational.
20655 <CENTER><SAMP>/tls1_1</SAMP></CENTER>
20662 This parameter indicates that the connection to the server will be made
20663 over the SSL port, but using the TLSv1.2 protocol, instead of the usual
20664 SSLv3 or SSLv2 protocols.
20665 Alpine must be linked with an SSL library for this option to be operational.
20668 <CENTER><SAMP>/tls1_2</SAMP></CENTER>
20674 <DT>NoValidate-Cert</DT>
20675 <DD>Do not validate certificates (for TLS or SSL connections) from the server.
20676 This is needed if the server uses self-signed certificates or if Alpine
20677 cannot validate the certificate for some other known reason.
20682 <DD>This is a unary parameter (that means it does not have a value)
20683 indicating that the connection be logged in as
20684 "anonymous" rather than a specific user.
20685 Not all servers offer anonymous
20686 access; those which do generally only offer read-only access to certain
20687 "public" folders.
20690 <CENTER><SAMP>/anonymous</SAMP></CENTER>
20696 <DD>This is a unary parameter indicating that the connection use the
20697 most secure authentication method mutually supported by Alpine and the
20699 Alpine is capable of authenticating connections to
20700 the server using several methods.
20701 By default, Alpine will attempt each
20702 method until either a connection is established or the
20703 list of methods is exhausted.
20704 This parameter causes Alpine to instead fail
20705 the connection if the first (generally most "secure") method fails.
20708 <CENTER><SAMP>/secure</SAMP></CENTER>
20714 <DD>This is a unary parameter for use with the
20715 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> option.
20716 It indicates that the connection should be made to the Submit server
20717 (<A HREF="http://www.ietf.org/rfc/rfc2476.txt">RFC 3676</A>)
20718 (port 587) instead of the SMTP port (25).
20719 At the time this help was written the submit option was equivalent to
20720 specifying port 587.
20723 <CENTER><SAMP>/submit</SAMP></CENTER>
20727 <CENTER><SAMP>host:587</SAMP></CENTER>
20733 <DD>This is a unary parameter indicating that the connection be established
20734 in a verbose mode. Basically, it causes Alpine to log the communication with
20735 the server in Alpine's debug file.
20736 Normally, the pine -d command-line flag would be used instead.
20741 <DD>By default, Alpine attempts to login using "rsh",
20742 the UNIX remote shell program.
20743 Including "NoRsh" will cause connections to this server to skip
20744 the "rsh" attempt.
20745 This might be useful to avoid long timeouts caused by rsh firewalls, for
20751 <DD>This option makes sense only for IMAP servers that do not perform
20752 a SEARCH command correctly. If your filtering rules
20753 fail to filter some messages, that should have been filtered, then this
20754 option will make Alpine download all data necessary data to perform that
20755 search. There is a performance penalty when using this option. Downloading
20756 the data to perfom the search will take longer than requesting the IMAP
20757 server to perform the filtering, but the filtering will be done correctly.
20763 <DD>This parameter requires an associated value. The default value is
20764 "IMAP" which indicates communication with the server based
20765 on the IMAP4rev1 protocol (defined in RFC 3501 -- see
20766 <A HREF="http://www.imap.org/docs/rfc3501.html">http://www.imap.org/docs/rfc3501.html</A>).</DD>
20768 Other service values include:
20771 <DD>This value indicates communication with the server takes place via
20772 the Network News Transfer Protocol. Use this to define a collection
20773 of newsgroups on a remote news server. So
20776 <CENTER><SAMP>/service=NNTP</SAMP></CENTER>
20780 <CENTER><SAMP>/NNTP</SAMP></CENTER>
20783 is the way to specify NNTP access.
20788 <DD>This value indicates communication with the server takes place via the
20789 Post Office Protocol 3 protocol.
20792 <CENTER><SAMP>/service=POP3</SAMP></CENTER>
20796 <CENTER><SAMP>/POP3</SAMP></CENTER>
20799 Note that there are several important issues
20800 to consider when selecting this option:
20802 <LI> POP3 provides access to only your INBOX. In other words,
20803 secondary folders such as your "saved-messages" are inaccessible.
20804 <LI> Alpine's implementation of POP3 does not follow the traditional POP
20805 model and will leave your mail on the server. Refer to the
20806 <A HREF="h_maildrop">Mail Drop</A> functionality for a possible way around this problem.
20807 <LI> See the discussion about new-mail checking in <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
20814 Note that it is possible to include more than one parameter in a server
20815 specification by concatenating the parameters. For example:
20818 <CENTER><SAMP>foo.example.com:port/user=katie/novalidate-cert/debug</SAMP></CENTER>
20822 <End of help on this topic>
20825 ======= h_composer_cntxt_server =======
20828 <TITLE>Collection Server: Explained</TITLE>
20831 <H1>Collection Edit Help -- Server Field</H1>
20833 This collection's "Server:" definition indicates the
20834 hostname of the server providing access to the folders in this
20836 The syntax of this server name is the same as for other server names used
20837 in remote folder names in
20838 Alpine and is described
20839 <A HREF="h_folder_server_syntax">here</A>.
20842 <End of help on this topic>
20845 ======= h_composer_cntxt_path =======
20848 <TITLE>Collection Path: Explained</TITLE>
20851 <H1>Collection Edit Help -- Path Field</H1>
20853 The collection's "Path:" definition indicates the location
20854 of the folders in this collection. If the path or any of its components
20855 do not exist, Alpine will prompt you for their creation when exiting the
20859 By default the path is interpreted as defining a section of your personal
20860 folder area. This area and how you specify it are defined by the
20861 server, if one is specified in the collection, or, typically, the home
20862 directory if no server is defined.
20865 To define a collection outside the default "area", prefix
20866 the path with the "namespace" to use when interpreting the
20867 given path. If a namespace is specified, the Path begins with the
20868 sharp, "#", character followed by the name of the namespace
20869 and then the namespace's path-element-delimiter. Aside from the
20870 path's format, namespaces can also imply access rights, content
20871 policy, audience, location, and, occasionally, access methods.
20874 Each server exports its own set (possibly of size one) of
20875 namespaces. Hence, it's likely communication with your server's
20876 administrator will be required for specific configurations. Some of
20877 the more common namespaces, however, include:
20881 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
20882 names are hierarchically defined with each level delimited by a period.
20885 <DD>This specifies a folder area that the server may export to the general
20889 <DD>This specifies a folder area that the folder may export to groups
20893 <DD>This specifies a folder area that is the same as that it may have
20894 exported via the "File Transfer Protocol".
20897 <DD>This specifies the personal folder area associated with folders
20898 and directories that were created using the MH message handling system.
20903 In addition, the server may support access to other user's folders,
20904 provided you have suitable permissions. Common methods use a prefix
20905 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
20906 indicate the root of the other user's folder area.
20909 No, nothing's simple.
20912 <End of help on this topic>
20915 ======= h_composer_cntxt_view =======
20918 <TITLE>Collection View: Explained</TITLE>
20921 <H1>Collection Edit Help -- View Field</H1>
20923 The collection's "View:" definition provides a way to limit
20924 the displayed list of folders within a collection. By default, only
20925 folders that contain the specified characters anywhere in their name
20926 are shown in the collection's folder list.
20929 Additionally, you can use a wildcard character to better control
20930 the list of folders selected for display. The wildcard specifier is
20931 the star, "*", character.
20934 So, for example, to define a collection of all folders ending with
20935 "c", you'd specify a view of "*c" (without the
20936 quote characters!). Or, similarly, to define a collection of folders
20937 whose names start with "a" and end with "z", you'd
20938 specify a view of "a*z".
20941 <End of help on this topic>
20944 ======= h_composer_abook_add_server =======
20947 <TITLE>Addressbook Server Name Field Explained</TITLE>
20950 This field should be left blank if the address book is stored in a regular
20951 file on this system. If it is a remote address book stored on an IMAP
20952 server then this is the name of that IMAP server.
20954 Look <A HREF="h_edit_nav_cmds">here</A>
20955 to see the available Editing and Navigation commands.
20957 <End of help on this topic>
20960 ======= h_composer_abook_add_folder =======
20963 <TITLE>Addressbook Folder Name Field Explained</TITLE>
20966 For a remote address book (one for which the Server Name is filled in)
20967 this is the name of a folder on the remote server. The address book data
20968 will be stored in this folder. This folder should be used only for
20969 storing this single address book, not for other address books or for
20972 For a local address book (one for which the Server Name is not filled in)
20973 this is the name of a file in which the address book will be stored.
20974 The file is in the same directory as the Alpine configuration file if the
20975 configuration file is local.
20976 If the configuration file is remote, then this will be in the home directory
20977 for Unix Alpine and in the directory specified by the
20978 "-aux local_directory" command line argument.
20980 Look <A HREF="h_edit_nav_cmds">here</A>
20981 to see the available Editing and Navigation commands.
20983 <End of help on this topic>
20986 ======= h_composer_abook_add_nick =======
20989 <TITLE>Addressbook NickName Field Explained</TITLE>
20992 This is just an optional nickname for this address book. If present, it
20993 is used in some of the displays and error messages in the address book
20994 maintenance screens. It is for your convenience only and serves no
20997 Look <A HREF="h_edit_nav_cmds">here</A>
20998 to see the available Editing and Navigation commands.
21000 <End of help on this topic>
21003 ======= h_composer_qserv_cn =======
21006 <TITLE>Directory Query Form Explained</TITLE>
21010 Fill in as many of these fields as you wish to narrow down your
21011 search. All the fields you fill in must match in order for an entry
21012 to be returned. You may use the wildcard character "*" in
21013 any of the fields, it matches any zero or more characters at that
21014 point in the string. There are no implicit wildcards, so the match is
21015 exact unless you include wildcards.
21018 Note that if an attribute isn't present at all, then the match will fail.
21019 For example, if a server doesn't support the Locality attribute, then no
21020 matter what you put in the Locality field (other than leaving it empty)
21021 the search will fail.
21024 This field, the Common Name field, is typically a person's full name.
21027 <H1>EDITING and NAVIGATION COMMANDS</H1>
21028 <!--chtml if pinemode="function_key"-->
21030 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
21031 ^B (Left Arrow) Back character | ^D Delete current character
21032 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
21033 ^P (Up Arrow) Previous line |
21034 ^N (Down Arrow) Next line | F9 Cut marked text or
21035 ^A Beginning of line | delete current line
21036 ^E End of line | F10 Undelete line(s)
21038 F8 Next page |-------------------------------------
21039 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
21040 ----------------------------------------|
21041 EXIT COMMANDS | GENERAL COMMANDS | F5 Restore previous search
21042 F2 Cancel | F1 Get help |
21043 F3 Search | ^Z Suspend | ^L Redraw Screen
21047 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
21048 ^B (Left Arrow) Back character | ^D Delete current character
21049 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
21050 ^P (Up Arrow) Previous line |
21051 ^N (Down Arrow) Next line | ^K Cut marked text or
21052 ^A Beginning of line | delete current line
21053 ^E End of line | ^U Undelete line(s)
21055 ^V Next page |-------------------------------------
21056 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
21057 ----------------------------------------|
21058 EXIT COMMANDS | GENERAL COMMANDS | ^R Restore previous search
21059 ^C Cancel | ^G Get help |
21060 ^X Search | ^Z Suspend | ^L Redraw Screen
21064 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21066 <End of help on this topic>
21069 ======= h_composer_qserv_sn =======
21071 The Surname is usually the family name of a person.
21073 <End of help on this topic>
21074 ======= h_composer_qserv_gn =======
21076 This is the part of a person's name that isn't the surname or initials.
21078 <End of help on this topic>
21079 ======= h_composer_qserv_mail =======
21081 This is the email address of a person.
21083 <End of help on this topic>
21084 ======= h_composer_qserv_org =======
21086 This is the organization a person belongs to.
21088 <End of help on this topic>
21089 ======= h_composer_qserv_unit =======
21091 This is the organizational unit a person belongs to.
21093 <End of help on this topic>
21094 ======= h_composer_qserv_country =======
21096 This is the country a person belongs to.
21098 <End of help on this topic>
21099 ======= h_composer_qserv_state =======
21101 This is the state a person belongs to.
21103 <End of help on this topic>
21104 ======= h_composer_qserv_locality =======
21106 This is the locality a person belongs to.
21108 <End of help on this topic>
21109 ======= h_composer_qserv_custom =======
21111 This one is for advanced users only! If you put something in this field,
21112 then the rest of the fields are ignored.
21114 This field may be set to the string representation of an LDAP search
21115 filter (see RFC1960). Here are some examples:
21117 To search for an entry with a surname equal to "clinton" you could set
21118 the custom filter to:
21122 This is equivalent to putting "clinton" in the SurName field.
21123 To search for an entry that has a surname that begins with "clint" and
21124 has a givenname equal to "william" you could use:
21126 (&(sn=clint*)(givenname=william))
21128 This is equivalent to setting the SurName field to "clint*" and the
21129 GivenName field to "william".
21130 To search for an entry where either the common name OR the email address
21131 contains "abcde" you could use:
21133 (|(cn=*abcde*)(mail=*abcde*))
21135 That isn't equivalent to anything you can do by setting the other fields
21138 <End of help on this topic>
21139 ======= h_composer_qserv_qq =======
21141 This one is a little different from the rest of the categories. It causes
21142 a search to be formed from the configured search filter that you filled
21143 in when you added the directory server to your configuration. It can also
21144 be combined with the other fields if you'd like.
21146 <End of help on this topic>
21147 ======= h_address_format =======
21150 <TITLE>INTERNET EMAIL ADDRESS FORMAT</TITLE>
21153 <H1>INTERNET EMAIL ADDRESS FORMAT</H1>
21155 A valid email address on the Internet has a username, an "@" sign,
21156 and then a domain, with no spaces.
21157 For example, jsmith@art.example.com might be the email address
21159 with the username "jsmith" who has an account in the domain
21160 "art.example.com". The number of dot-separated segments on the
21161 right of the "@" sign can vary - a shorter example would be
21162 isabelle@elsewhere.edu (the shortest possible form: here, only the
21163 organization's domain is specified after the "@" sign); a longer
21165 jsingh@shakti.edutech.example.com
21166 (here, the name of the host "shakti" in the domain
21167 edutech.example.com is also specified).
21169 If you do not know the exact email address of someone you want to write
21170 to, ask them what it is using other means of communication than email; or
21172 finding people's addresses that are available on the Internet.
21174 If you are sending to someone on the same system as you are, you can leave
21175 the "@" sign and all the information to its right off of the
21176 address, and Alpine will fill it in automatically,
21178 <A HREF="h_config_compose_rejects_unqual">"<!--#echo var="FEAT_compose-rejects-unqualified-addrs"-->"</A> is set in SETUP CONFIGURATION.
21181 When an email address you send a message to is not reachable -- either because
21182 it is simply an incorrect address, or because email can temporarily not be
21183 delivered to it due to a technical problem on the way to or at the recipient's
21184 end -- you will almost always get an error notification email message back.
21186 If you encounter problems with, or have questions about, email delivery or
21187 email address syntax, contact your local network computing consultants.
21189 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21192 <End of help on this topic>
21195 ======= h_flag_user_flag =======
21198 <TITLE>STATUS FLAG: User Defined Keyword</TITLE>
21201 <H1>STATUS FLAG: User Defined Keyword</h1>
21203 This is a keyword that is defined for this folder.
21204 It was most likely defined by the owner of the folder.
21205 Alpine will not set or clear this flag on its own.
21208 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21210 <End of help on this topic>
21213 ======= h_flag_important =======
21215 <title>STATUS FLAG: Important</title>
21217 <h1>STATUS FLAG: Important</h1>
21220 The <EM>Important</EM> flag, indicated by an asterisk in Alpine's
21222 screen, can only be set by the user, and is intended to be used in
21223 whatever fashion makes sense to you. You are the only one that can set or
21227 <End of help on this topic>
21230 ======= h_flag_new =======
21232 <title>STATUS FLAG: New</title>
21234 <h1>STATUS FLAG: New</h1>
21237 The <EM>New</EM> flag, indicated by the letter 'N' in Alpine's
21238 MESSAGE INDEX screen,
21239 is automatically set when messages are delivered to your Inbox (or other
21240 folder specified outside of Alpine). Likewise, it is cleared automatically
21241 the first time you read the message it is associated with.
21244 Sometimes it's helpful in prioritizing your mail. For example, perhaps
21245 a message isn't weighty enough to assign it an <A HREF="h_flag_important">Important</A> flag, but
21246 you'd like to be reminded of it next time you read mail. This can be done
21247 easily by <A HREF="h_common_flag">explicitly</A> resetting the <EM>New</EM> flag.
21251 <End of help on this topic>
21254 ======= h_flag_answered =======
21256 <title>STATUS FLAG: Answered</title>
21258 <h1>STATUS FLAG: Answered</h1>
21260 The <EM>Answered</EM> flag, indicated by the letter 'A' in Alpine's
21262 screen, is automatically set when you reply to a message. This flag is not
21263 automatically cleared.
21266 <End of help on this topic>
21269 ======= h_flag_forwarded =======
21271 <title>STATUS FLAG: Forwarded</title>
21273 <h1>STATUS FLAG: Forwarded</h1>
21275 The <EM>Forwarded</EM> flag, indicated by the letter 'F' in Alpine's
21277 screen, is automatically set when you forward a message. This flag is not
21278 automatically cleared.
21281 <End of help on this topic>
21284 ======= h_flag_deleted =======
21286 <title>STATUS FLAG: Deleted</title>
21288 <h1>STATUS FLAG: Deleted</h1>
21290 The <EM>Deleted</EM> flag, indicated by the letter 'D' in Alpine's
21292 screen, is set when you use the ""D Delete" command.
21294 when you use the "U Undelete" command.
21297 Messages marked with this flag will be permanently removed from
21298 the folder when you issue the <A HREF="h_index_cmd_expunge">Expunge</A>
21300 when you indicate acceptance of their removal upon leaving the folder.
21303 Note, there can be other actions implicit in the
21304 "D Delete" command,
21305 such as advancing to the next message, that may be momentarily undesirable.
21306 For this reason, it's sometimes useful to set or clear the <EM>Deleted</EM>
21307 flag <A HREF="h_common_flag">explicitly</A>.
21310 <End of help on this topic>
21313 ====== h_config_incoming_timeo ======
21316 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></TITLE>
21319 <H1>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></H1>
21321 This option has no effect unless the feature
21322 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21323 is set, which in turn has no effect unless
21324 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21327 Sets the time in seconds that Alpine will
21328 attempt to open a network connection used for monitoring for Unseen
21329 messages in Incoming Folders. The default is 5.
21330 If a connection has not completed within this many seconds Alpine will
21331 give up and consider it a failed connection.
21334 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21336 <End of help on this topic>
21339 ====== h_config_psleep ======
21342 <TITLE>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</TITLE>
21345 <H1>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</H1>
21348 In the good old days a mailcap viewer was used to examine an
21349 attachment before saving it, and after viewing the attachment control
21350 would return to the operating system when the viewer was closed. Therefore,
21351 when the mailcap viewer returned control to the operating system, it
21352 could be assumed that the user who opened the attachment was done
21353 examining it, and the copy of the attachment that was used, could be removed.
21356 However, today this assumption is not longer valid. Some viewers return
21357 control to the operating system before they actually read the attachment
21358 to be examined. This causes Alpine to delete the attachment before it
21359 is read by the viewer, causing the viewer to fail opening the attachment.
21362 In order to work around this problem, Alpine checks, after the viewer has
21363 returned control to the operating system, if there is any process that is
21364 using the attachment. This variable controls the number of seconds that
21365 must elapse between checks. Once it is found that no process is using the
21366 attachment, this is removed.
21369 The minimum value for this variable is 60 (checks will be made once per
21370 minute), and the maximum value is 600 (checks will be made once every 10
21371 minutes). The default value is 60.
21375 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21377 <End of help on this topic>
21380 ====== h_config_incoming_interv ======
21383 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval"--></TITLE>
21386 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval"--></H1>
21388 This option has no effect unless the feature
21389 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21390 is set, which in turn has no effect unless
21391 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21394 This option specifies, in seconds, how often Alpine will check
21395 for new mail and state changes in Incoming Folders when Incoming Folders
21396 Checking is turned on.
21397 The default is 3 minutes (180).
21398 This value applies only to folders that are local to the system that
21399 Alpine is running on or that are accessed using the IMAP protocol.
21401 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>
21402 applies to all other monitored folders.
21405 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21407 <End of help on this topic>
21410 ====== h_config_incoming_second_interv ======
21413 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></TITLE>
21416 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></H1>
21418 This option has no effect unless the feature
21419 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21420 is set, which in turn has no effect unless
21421 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21424 This option together with the option
21425 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
21426 specifies, in seconds, how often Alpine will check
21427 for new mail and state changes in Incoming Folders when Incoming Folders
21428 Checking is turned on.
21429 The default for this option is 3 minutes (180).
21430 For folders that are local to this system or
21431 that are accessed using the IMAP protocol
21432 the value of the option
21433 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
21435 For all other monitored folders, the value of this option is used.
21437 The reason there are two separate options is because it is usually
21438 less expensive to check local and IMAP folders than it is to check
21439 other types, like POP or NNTP folders.
21440 You may want to set this secondary value to a higher number than
21441 the primary check interval.
21444 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21446 <End of help on this topic>
21449 ====== h_config_incoming_list ======
21452 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-list"--></TITLE>
21455 <H1>OPTION: <!--#echo var="VAR_incoming-check-list"--></H1>
21457 This option has no effect unless the feature
21458 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21459 is set, which in turn has no effect unless
21460 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21463 When monitoring the Incoming Message Folders for Unseen messages Alpine will
21464 normally monitor all Incoming Folders.
21465 You may use this option to restrict the list of monitored folders to a
21466 subset of all Incoming Folders.
21469 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21471 <End of help on this topic>
21474 ====== h_config_pers_name ======
21477 <TITLE>OPTION: <!--#echo var="VAR_personal-name"--></TITLE>
21480 <H1>OPTION: <!--#echo var="VAR_personal-name"--></H1>
21482 This value is used to determine the full name part of the "From" address
21483 on messages you send.
21484 <!--chtml if pinemode="os_windows"-->
21485 PC-Alpine requires that this be set in order to properly construct the "From" address.
21487 If unset, Unix Alpine will obtain your full name from
21488 the system password file. PC-Alpine, on the other hand, requires that this be set.
21491 If you want to change the value of what gets included in the From header
21492 in messages you send (other than just the Personal Name)
21493 look <A HREF="h_config_change_your_from">here</A> for a description.
21495 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21497 <End of help on this topic>
21500 ====== h_config_pruned_folders ======
21503 <title>OPTION: <!--#echo var="VAR_pruned-folders"--></title>
21506 <h1>OPTION: <!--#echo var="VAR_pruned-folders"--></h1>
21508 This variable allows you to define a list of one or more folders that
21509 Alpine will offer to prune for you in the same way it automatically offers
21510 to prune your "sent-mail" folder each month.
21511 Each folder in this list must be a folder in your default folder collection
21512 (the first folder collection if you have more than one), and it is just
21513 the relative name of the folder in the collection, not the fully-qualified name.
21514 It is similar to sent-mail.
21515 Instead of something like
21517 <CENTER><SAMP><!--#echo var="VAR_pruned-folders"-->={servername}mail/folder</SAMP></CENTER>
21519 the correct value to use would be
21521 <CENTER><SAMP>folder</SAMP></CENTER>
21523 There is an assumption here that your first collection is the folders in
21525 <CENTER><SAMP>{servername}mail</SAMP></CENTER>
21528 Once a month, for each folder listed, Alpine will offer to move
21529 the contents of the folder to a new folder of the same name but with
21530 the previous month's date appended. Alpine will then look for any such
21531 date-appended folder names created for a previous month, and offer each
21532 one it finds for deletion.
21535 If you decline the first offer, no mail is moved and no new folder is
21539 The new folders will be created
21540 in your default folder collection.
21544 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21546 <End of help on this topic>
21549 ====== h_config_upload_cmd ======
21552 <TITLE>OPTION: <!--#echo var="VAR_upload-command"--></TITLE>
21555 <H1>OPTION: <!--#echo var="VAR_upload-command"--></H1>
21557 This option affects the behavior of the Composer's "Read File"
21558 (^R in the message body) and "Attach File" (^J in the header)
21559 commands. It specifies
21560 a Unix program name, and any necessary command line arguments, that Alpine can
21561 use to transfer files from your personal computer into messages that you are
21564 <B>Note:</B> this facility is intended for use with serial line transfer
21565 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
21566 to work with TCP/IP file transfer programs such as ftp.<P>
21568 If a program is specified, the commands listed above are modified to offer a
21569 subcommand (^Y) to activate the transfer. Obviously, the Unix program
21570 specified here must match the transfer program or protocol available on the
21571 personal computer.<P>
21573 Alpine expects to exchange uploaded data via a file on your Unix system. When
21574 the specified upload program finishes, Alpine expects the uploaded data to be
21575 contained in this file.<P>
21577 When upload is invoked via the "Read File" subcommand, Alpine
21579 temporary file name that it will pass to the specified Unix program. Alpine
21580 will read the resulting uploaded text from this file and then delete it when
21581 the upload command is finished.<P>
21583 When upload is invoked via the "Attach File" subcommand, Alpine will
21585 you for the name of the file that is to contain the uploaded information that
21586 it is to attach. Alpine will attach this file to the composition, but will
21587 <B>not</B> delete this file after the upload command is finished.<P>
21589 The special token "_FILE_" may be included among the Unix program's
21591 line arguments. Alpine will replace this symbol with the name of the file
21592 being used to exchange the uploaded information. This token allows you to
21593 position the file name where it is required in the Unix program's command
21596 If the "_FILE_" token is not present in the specified command, the
21597 temporary file's name is automatically appended to the specified Unix
21598 program. In other words, you don't need to use "_FILE_" if it is the
21599 <B>last</B> command line argument.
21601 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21603 <End of help on this topic>
21606 ====== h_config_upload_prefix ======
21609 <TITLE>OPTION: <!--#echo var="VAR_upload-command-prefix"--></TITLE>
21612 <H1>OPTION: <!--#echo var="VAR_upload-command-prefix"--></H1>
21614 This option is used in conjunction with the <!--#echo var="VAR_upload-command"--> option.
21615 It defines text to be written to the terminal emulator (via standard output)
21616 immediately prior to starting upload command. This is useful for
21617 integrated serial line file transfer agents that permit command passing
21618 (e.g., Kermit's APC method).<P>
21620 The special token "_FILE_" may be included in the string specification.
21621 That symbol will be replaced with the (Alpine-created) name of the temporary
21622 file in which Alpine will expect to find the uploaded file.
21624 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21626 <End of help on this topic>
21629 ====== h_config_download_cmd ======
21632 <TITLE>OPTION: <!--#echo var="VAR_download-command"--></TITLE>
21635 <H1>OPTION: <!--#echo var="VAR_download-command"--></H1>
21637 This option affects the behavior of the Export command. It specifies a Unix
21638 program name, and any necessary command line arguments, that Alpine can use to
21639 transfer the exported message to your personal computer's disk.<P>
21640 Note: this facility is intended for use with serial line transfer
21641 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
21642 to work with TCP/IP file transfer programs such as ftp.<P>
21643 If a program is specified, the Export command is modified to offer a
21644 subcommand (^V) to activate the transfer (in lieu of saving it to
21645 the machine where Alpine is running). Obviously, the Unix program
21646 specified here must match the transfer program or protocol available on the
21647 personal computer.<P>
21649 When this subcommand is selected and before Alpine invokes the specified Unix
21650 program, Alpine will create a temporary file containing the text of the
21651 exported message. Alpine uses this file to pass the exported message text to
21652 the specified Unix program.<P>
21654 The special token "_FILE_" may be included among the Unix program's command
21655 line arguments. Alpine will replace this symbol with the temporary file's name
21656 before executing the Unix program. This token allows you to position the
21657 file name where it is required in the Unix program's command line arguments.
21659 If the "_FILE_" token is not present in the specified command, the
21660 temporary file's name is automatically appended to the specified Unix
21661 program. In other words, you don't need to use "_FILE_" if it is the
21662 <B>last</B> command line argument.
21664 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21666 <End of help on this topic>
21669 ====== h_config_download_prefix ======
21672 <TITLE>OPTION: <!--#echo var="VAR_download-command-prefix"--></TITLE>
21675 <H1>OPTION: <!--#echo var="VAR_download-command-prefix"--></H1>
21677 This option is used in conjunction with the <!--#echo var="VAR_download-command"--> option.
21678 It defines text to be written to the terminal emulator (via standard output)
21679 immediately prior to starting the download command. This is useful for
21680 integrated serial line file transfer agents that permit command passing
21681 (e.g., Kermit's APC method).
21683 The special token "_FILE_" may be included in the string
21685 That symbol will be replaced with the (Alpine-created) name of the temporary
21686 file into which Alpine will place the message to be downloaded.
21688 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21690 <End of help on this topic>
21693 ====== h_config_mailcap_path ======
21696 <TITLE>OPTION: <!--#echo var="VAR_mailcap-search-path"--></TITLE>
21699 <H1>OPTION: <!--#echo var="VAR_mailcap-search-path"--></H1>
21700 This variable is used to replace Alpine's default mailcap file search path.
21701 It takes one or more file names (full paths must be specified) in which to
21702 look for mail capability data. The default search path can be found in this
21703 <A HREF="h_news_config">Alpine Configuration</A> help, near the bottom.
21704 If there is more than one file name listed, list members should be delimited
21706 <!--chtml if pinemode="os_windows"-->
21707 a semi-colon (;) under Windows; for example:<PRE>
21708 C:\MYCONFIG\MAILCAP.TXT;H:\NETCONFIG\MAILCAP.TXT
21711 a colon (:) under UNIX; for example:<PRE>
21712 ~/.mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
21716 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21719 <End of help on this topic>
21722 ====== h_config_mimetype_path ======
21725 <TITLE>OPTION: <!--#echo var="VAR_mimetype-search-path"--></TITLE>
21728 <H1>OPTION: <!--#echo var="VAR_mimetype-search-path"--></H1>
21730 This variable is used to replace Alpine's default mime.types file search path.
21731 It takes one or more file names (full paths must be specified) in which to
21732 look for file-name-extension to MIME type mapping data. The default search
21733 path can be found in this
21734 <A HREF="h_news_config">Alpine Configuration</A> help.
21738 If there is more than one file name listed, list members should be delimited
21739 by a colon (:) under UNIX and a semi-colon (;) under Windows.
21741 <End of help on this topic>
21743 ====== h_config_set_att_ansi ======
21745 <TITLE>OPTION: Set printer to attached ansi printer</TITLE>
21748 <H1>OPTION: Set printer to attached ansi printer</H1>
21750 Type "S" to set your printer to "attached-to-ansi".<BR>
21751 It is OK to include "attached-to-ansi" in your personal list below.
21753 <End of help on this topic>
21755 ====== h_config_set_att_ansi2 ======
21757 <TITLE>OPTION: Set printer to attached ansi printer (no formfeed)</TITLE>
21760 <H1>OPTION: Set printer to attached ansi printer (no formfeed)</H1>
21762 Type "S" to set your printer to "attached-to-ansi-no-formfeed".<BR>
21763 It is OK to include "attached-to-ansi-no-formfeed" in your personal
21768 This is the same as the "attached-to-ansi" option except that a
21769 formfeed character will not be appended to the end of the print job.
21770 If your printer already ejects the paper by itself at the end of the
21771 job, you may prefer the "no-formfeed" form of this printer so that you
21772 don't get an extra blank page between print jobs.
21775 <End of help on this topic>
21777 ====== h_config_set_att_wyse ======
21779 <TITLE>OPTION: Set printer to attached Wyse60 printer</TITLE>
21782 <H1>OPTION: Set printer to attached Wyse60 printer</H1>
21784 Type "S" to set your printer to "attached-to-wyse".<BR>
21785 It is OK to include "attached-to-wyse" in your personal list below.
21787 This is very similar to "attached-to-ansi".
21788 The only difference is in the control characters sent to turn the printer
21790 The ansi version of the printer uses ESC LEFT_BRACKET 5 i
21791 to turn on the printer and ESC LEFT_BRACKET 4 i
21793 The Wyse version uses Ctrl-R for on, and Ctrl-T for off.
21794 <End of help on this topic>
21796 ====== h_config_set_att_wyse2 ======
21798 <TITLE>OPTION: Set printer to attached Wyse60 printer (no formfeed)</TITLE>
21801 <H1>OPTION: Set printer to attached Wyse60 printer (no formfeed)</H1>
21803 Type "S" to set your printer to "attached-to-wyse-no-formfeed".<BR>
21804 It is OK to include "attached-to-wyse-no-formfeed" in your personal
21809 This is the same as the "attached-to-wyse" option except that a
21810 formfeed character will not be appended to the end of the print job.
21811 If your printer already ejects the paper by itself at the end of the
21812 job, you may prefer the "no-formfeed" form of this printer so that you
21813 don't get an extra blank page between print jobs.
21816 <End of help on this topic>
21818 ====== h_config_set_stand_print ======
21821 <TITLE>OPTION: Set default printer</TITLE>
21823 <H1>OPTION: Set default printer</H1>
21825 Move to the printer you want and type "S" to set it to be your
21826 default printer. This list is not modifiable by you and has been
21827 set up by the system administrators. If there is more than one printer
21828 listed in the Command List, you will be able to cycle through that
21829 whole list at the time you print, starting with your default.
21830 It is OK to include entries from this Standard list in your personal
21833 <End of help on this topic>
21836 ====== h_config_set_custom_print ======
21839 <TITLE>OPTION: Set default printer</TITLE>
21841 <H1>OPTION: Set default printer</H1>
21843 You may add as many print commands as you want to your personal list.
21844 Specify one of them as your default printer by moving to the printer
21845 you want and typing "S". If there is more than one printer listed
21846 in the Command List, you will be able to cycle through that list at
21847 the time you print, starting with your default. It is OK to include
21848 entries from the Standard list above or to include the command
21849 "attached-to-ansi", "attached-to-ansi-no-formfeed", "attached-to-wyse", or
21850 "attached-to-wyse-no-formfeed" as one of the entries here.
21852 <End of help on this topic>
21855 ====== h_config_user_id =====
21858 <TITLE>OPTION: <!--#echo var="VAR_user-id"--></TITLE>
21861 <H1>OPTION: <!--#echo var="VAR_user-id"--></H1>
21863 This value is used as part of the "From" address on messages you send.
21864 It is also the default login name for remote IMAP server access. Set this
21865 to the username part you want to appear on outgoing email.
21867 If you want to change the value of what gets included in the From header
21868 in messages you send (other than just the User ID)
21869 look <A HREF="h_config_change_your_from">here</A> for a description.
21872 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21874 <End of help on this topic>
21877 ====== h_config_user_dom =====
21880 <TITLE>OPTION: <!--#echo var="VAR_user-domain"--></TITLE>
21883 <H1>OPTION: <!--#echo var="VAR_user-domain"--></H1>
21885 This value specifies the domain part (right-hand side) of your return
21886 address on outgoing email and is also used as the default domain for email
21887 composed to a local user.
21888 <!--chtml if pinemode="os_windows"-->
21889 This value is required for PC-Alpine. If you are unsure as to what this should be,
21890 contact your local help desk, system administrator, or Internet Service Provider.
21892 If unset, Unix Alpine will obtain the domain from
21893 the system. Often this value will be set for your whole site by the
21894 system administrator.<P>
21896 If you set this, see also the <A HREF="h_config_quell_local_lookup">
21897 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
21899 If you want to change the value of what gets included in the From header
21900 in messages you send (other than just the User Domain)
21901 look <A HREF="h_config_change_your_from">here</A> for a description.
21903 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21905 <End of help on this topic>
21908 ====== h_config_smtp_server =====
21911 <TITLE>OPTION: <!--#echo var="VAR_smtp-server"--></TITLE>
21914 <H1>OPTION: <!--#echo var="VAR_smtp-server"--></H1>
21915 This value specifies the name of one or more SMTP
21916 (Simple Mail Transfer Protocol) servers for sending mail.
21917 <!--chtml if pinemode="os_windows"-->
21918 You must have an SMTP server for use with PC-Alpine.
21920 normally set up by a system administrator for use by all members of a given
21921 campus or department.
21922 Contact your local help desk to ask what SMTP
21923 servers you should use.
21925 Unix Alpine users may not need to set an SMTP server.
21926 Alpine will attempt to execute the program (usually sendmail) that is used
21927 to insert mail into the mail system.
21928 If this works for you, you may leave this option blank.
21929 If there is an SMTP server running on the Unix host you may be able to
21930 improve sending performance slightly by setting the SMTP server option
21931 to "localhost" or to the actual name of the Unix host.
21933 If the Unix host doesn't work the way Alpine was expecting you will need to
21934 set the value of this option.
21936 normally set up by a system administrator for use by all members of a given
21937 campus or department.
21938 Contact your local help desk to ask what SMTP
21939 servers you should use.
21942 Your SMTP server may offer SMTP AUTH authentication.
21943 It may even require it.
21944 If your SMTP server offers SMTP AUTH authentication you may specify a
21945 "user" name parameter to cause Alpine to attempt to authenticate.
21946 This parameter requires an associated value,
21947 the username identifier with which to establish the server
21949 An example might be:
21952 <CENTER><SAMP>smtpserver.example.com/user=katie</SAMP></CENTER>
21955 If AUTH authentication is offered by the server, this will cause Alpine to
21957 If AUTH authentication is not offered by the server, this will cause Alpine
21958 to fail sending with an error similar to:
21961 <CENTER><SAMP>Error: SMTP authentication not available</SAMP></CENTER>
21964 Another type of authentication that is used by some ISPs is called
21965 "POP before SMTP" or "IMAP before SMTP",
21966 which means that you have to authenticate
21967 yourself to the POP or IMAP server by opening a mailbox before you
21969 To do this, you usually only have to open your INBOX.
21972 You may tell Alpine to use the
21973 <A HREF="http://www.ietf.org/rfc/rfc2476.txt">Message Submission</A>
21974 port (587) instead of the SMTP port (25) by including the "submit"
21977 At this time "/submit" is simply equivalent to specifying
21978 port 587, though it may imply more than that at some point in the future.
21979 Some ISPs are blocking port 25 in order to reduce the amount of spam
21980 being sent to their users.
21981 You may find that the submit option allows you to get around such a block.
21984 <CENTER><SAMP>smtpserver.example.com/submit</SAMP></CENTER>
21987 To specify any non-standard port number on the SMTP server you may follow
21988 the hostname with a colon followed by the portnumber.
21991 <CENTER><SAMP>smtpserver.example.com:12345</SAMP></CENTER>
21994 Normally, when a connection is made to the Smtp-Server Alpine will attempt
21995 to negotiate a secure (encrypted) session using Transport Layer Security (TLS).
21996 If that fails then a non-encrypted connection will be attempted instead.
21997 You may specify that a TLS connection is required if you wish.
21998 If you append "/tls" to the name then the connection will fail
21999 instead of falling back to a non-secure connection.
22002 <CENTER><SAMP>smtpserver.example.com/tls</SAMP></CENTER>
22006 For more details about server name possibilities see
22007 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
22011 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22014 <End of help on this topic>
22017 ====== h_config_nntp_server =====
22020 <TITLE>OPTION: <!--#echo var="VAR_nntp-server"--></TITLE></HEAD>
22022 <H1>OPTION: <!--#echo var="VAR_nntp-server"--></H1>
22024 This value specifies the name of one or more NNTP
22025 (Network News Transfer Protocol)
22026 servers for reading and posting USENET news.
22027 NNTP servers are normally
22028 set up by a system administrator for use by all members of a given campus
22030 Contact your local help desk to ask what NNTP servers you should use.
22031 <!--chtml if pinemode="os_windows"--><!--chtml else-->
22032 Often Unix Alpine users will find that this variable has been
22033 set for the whole system (and they don't have to worry about it).
22035 When you define an NNTP server here, Alpine implicitly defines a news
22036 collection for you, assuming that server as the news server and assuming
22037 that you will use the NNTP protocol and a local newsrc configuration file
22039 For more about reading news with Alpine, see
22040 <A HREF="h_reading_news">how to use Alpine to read news</A>.
22042 Your NNTP server may offer NNTP "AUTHINFO SASL"
22043 or "AUTHINFO USER" authentication.
22044 It may even require it.
22045 If your NNTP server does offer such authentication you may specify a user name
22046 parameter to cause Alpine to attempt to authenticate.
22047 The same is true for the server name in a folder collection that uses NNTP.
22048 This parameter requires an associated value,
22049 the username identifier with which to establish the server connection.
22050 An example might be:
22053 <CENTER><SAMP>nntpserver.example.com/user=katie</SAMP></CENTER>
22056 If authentication is offered by the server, this will cause Alpine to
22058 If authentication is not offered by the server, this will cause Alpine
22059 to fail with an error similar to:
22062 <CENTER><SAMP>Error: NNTP authentication not available</SAMP></CENTER>
22064 For more details about the server name possibilities see
22065 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
22067 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22069 <End of help on this topic>
22072 ====== h_config_inbox_path =====
22075 <TITLE>OPTION: <!--#echo var="VAR_inbox-path"--></TITLE>
22078 <H1>OPTION: <!--#echo var="VAR_inbox-path"--></H1>
22080 This value overrides the default value of your INBOX name/path/location.
22081 <!--chtml if pinemode="os_windows"-->
22082 PC-Alpine users must specify an inbox path and it must be a folder on an
22085 Unix and VMS Alpine users will often find that this variable
22086 has been pre-configured by your system administrator.
22088 You may be able to specify an alternate INBOX that is either a local folder
22089 or a folder on an IMAP server.
22091 A typical remote <!--#echo var="VAR_inbox-path"--> entry would be: {monet.art.example.com}INBOX
22092 where "monet.art.example.com" is replaced by the name of your IMAP
22095 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22096 details on the syntax of folder definitions.
22098 See <A HREF="h_info_on_mbox">Missing mail and the mbox driver</A> if your
22099 mail is disappearing.
22101 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22103 <End of help on this topic>
22106 ====== h_config_change_your_from =====
22109 <TITLE>How to Change your From Address</TITLE>
22112 <H1>How to Change your From Address</H1>
22114 If the From address that Alpine includes in mail that you send is not correct,
22115 you may want to configure a different default value for the From address.
22116 You may follow these directions to change the default:
22120 <LI> Go to the Main Alpine Menu
22121 <LI> From there type the Setup Command
22122 <LI> From there type the Config Command
22126 You've probably already seen this SETUP CONFIGURATION screen.
22127 If not, there are many options you may want to set here.
22128 To set the value of the From header you may use the
22129 <A href="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> option.
22130 Find it by scrolling down a few pages or use the WhereIs command to
22131 search for "customized".
22132 You may want to read the help text associated with the option.
22134 To add a custom From header, type the Add command and enter the
22135 full header line, including the leading "From: ".
22138 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
22140 Now exit the Setup command and try sending mail to yourself to see
22141 what the From line looks like.
22143 When you are in the composer you may edit the custom From line by typing
22144 Ctrl-R while your cursor is in the headers of the message and then moving
22145 to the From line and editing.
22146 If you want to leave the default value the same but add the possibility
22147 of being able to edit the header when you compose, add just the header
22148 name without a value.
22151 <CENTER><SAMP>From:</SAMP></CENTER>
22153 If you change your From address you may also find it useful to add the
22154 changed From address to the
22155 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
22156 configuration option.
22159 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22161 <End of help on this topic>
22164 ====== h_config_default_fcc =====
22167 <TITLE>OPTION: <!--#echo var="VAR_default-fcc"--></TITLE>
22170 <H1>OPTION: <!--#echo var="VAR_default-fcc"--></H1>
22172 This value specifies where a copy of outgoing mail should be saved. If
22173 this is not a path name, it will be in the default collection for saves.
22174 Any valid folder specification, local or IMAP, is allowed. This default
22175 folder carbon copy only applies when the
22176 <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
22177 is set to use the default folder.
22178 <!--chtml if pinemode="os_windows"-->
22179 PC-Alpine default is "SENTMAIL" (normally stored as SENTMAIL.MTX)
22181 Unix Alpine default
22182 is normally "sent-mail" in the default folder collection.
22185 If you access your email through an IMAP server, especially if you often switch between Unix Alpine
22186 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on your
22187 IMAP server (remember that in order to later access this remote folder through Alpine, it
22188 must be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
22189 for more information). An example:<p>
22190 <CENTER><SAMP>{monet.art.example.com}mail/sent-mail</SAMP></CENTER>
22192 To suppress saving of outgoing mail, set: <!--#echo var="VAR_default-fcc"-->=""
22194 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22195 details on the syntax of folder definitions.
22198 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22200 <End of help on this topic>
22203 ====== h_config_def_save_folder =====
22206 <TITLE>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></TITLE>
22209 <H1>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></H1>
22211 This option determines the default folder name for save-message operations
22212 ("saves").
22214 If this is not a path name, it will be in the default collection for saves.
22215 Any valid folder specification, local or IMAP, is allowed. This default
22216 folder only applies when the
22217 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
22218 doesn't override it.
22219 <!--chtml if pinemode="os_windows"-->
22220 PC-Alpine default is "SAVEMAIL" (normally stored as SAVEMAIL.MTX).
22222 Unix Alpine default
22223 is normally "saved-messages" in the default folder collection.
22225 If you access your email through an IMAP server, especially if you often switch between Unix
22226 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on an
22227 IMAP server (remember that in order to later access this remote folder through Alpine, it
22228 should be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
22229 for more information). An example:<p>
22230 <CENTER><SAMP>{monet.art.example.com}mail/saved-messages</SAMP></CENTER>
22232 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22233 details on the syntax of folder definitions.
22236 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22238 <End of help on this topic>
22241 ====== h_config_postponed_folder =====
22244 <TITLE>OPTION: <!--#echo var="VAR_postponed-folder"--></TITLE>
22247 <H1>OPTION: <!--#echo var="VAR_postponed-folder"--></H1>
22249 This value overrides the default name for the folder where postponed
22250 messages are saved. If this is not a path name, it will be in the default
22251 collection for message Saves. Any valid folder specification, local or
22252 remote, is allowed.
22254 is "POSTPOND" (stored as POSTPOND.MTX).
22255 The Unix Alpine default is normally "postponed-msgs"
22256 in the default collection.
22258 Tip: If you are using different installations of (PC-)Alpine -- for example, PC-Alpine on your personal
22259 computer at home, and Unix Alpine on campus -- you can postpone a composition begun with one Alpine and
22260 resume it later with the other if you set this option to the <B>same folder on the same IMAP host</B>
22261 in all Alpine copies you use.
22262 (Remember that in order to later access this remote folder through Alpine, it must be in a folder
22263 collection. See <A HREF="h_what_are_collections">Folder Collections Extensions Explained</a>
22264 for more information). An
22266 <CENTER><SAMP>{monet.art.example.com}mail/postponed-msgs</SAMP></CENTER>
22268 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22269 details on the syntax of folder definitions.
22272 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22274 <End of help on this topic>
22277 ====== h_config_read_message_folder =====
22280 <TITLE>OPTION: <!--#echo var="VAR_read-message-folder"--></TITLE>
22283 <H1>OPTION: <!--#echo var="VAR_read-message-folder"--></H1>
22285 By virtue of specifying a folder name here, Alpine will be configured to
22286 save all messages that you have read during a session into the designated
22287 "read messages" folder. This allows you to more easily distinguish
22288 between your really new email (in your INBOX) and those that you have
22289 already read. Depending on how you define the
22290 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
22291 setting, you may or may not be asked when you quit
22292 Alpine if you want read messages to be moved to this folder. In either
22293 case, moving the messages means they will be deleted from your INBOX.
22295 If this is not a path name, it will be in the default collection for
22296 saves. Any valid folder specification, local or remote (via IMAP), is
22297 allowed. There is no default for the name of the read message folder.
22299 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22300 details on the syntax of folder definitions.
22303 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22305 <End of help on this topic>
22308 ====== h_config_form_folder =====
22311 <TITLE>OPTION: <!--#echo var="VAR_form-letter-folder"--></TITLE>
22314 <H1>OPTION: <!--#echo var="VAR_form-letter-folder"--></H1>
22316 A "<!--#echo var="VAR_form-letter-folder"-->" is a mail folder that is intended to
22317 contain messages that you have composed and that are intended to be
22318 sent in their original form repeatedly.
22321 Setting this variable will alter Alpine's usual behavior when you
22322 execute the Compose command. Normally, Alpine offers a chance to
22323 continue a postponed or interrupted message should one or the other
22324 exist. When this variable is set to a folder name that exists, Alpine
22325 will also offer the chance to select a message from the folder to
22326 insert into the composer (much like when continuing a postponed message).
22327 The difference, however, is that Alpine will not automatically delete
22328 the selected message from the Form Letter Folder.
22330 Setting this variable will also affect Alpine's behavior when you
22331 Postpone a message from the composer. Normally, Alpine simply stashes
22332 the message away in your
22333 "<A HREF="h_config_postponed_folder"><!--#echo var="VAR_postponed-folder"--></A>".
22334 Regardless of the specified folder's existence, Alpine will ask which
22335 folder you intend the message to be stored in. Choose the
22336 "F" option to store the message in your Form Letter Folder.
22337 This is the most common way to add a message to the folder.
22340 Another method of adding messages to the folder is via the Alpine
22341 composer's <SAMP>Fcc:</SAMP> field. If you are sending a message that
22342 you expect to send in the same form again, you can enter the Form
22343 Letter Folder's name in this field. Alpine, as usual, will copy the
22344 message as it's sent. Note, when you later select this message from
22345 your Form Letter Folder, it will have the same recipients as the original
22349 To delete a message from the Form Letter Folder, you can either select
22350 the folder from a suitable FOLDER LIST screen, or use the Delete
22351 command in the MESSAGE INDEX offered when selecting from the folder as
22352 part of the Compose command. You can delete a Form Letter Folder just
22353 as any other folder from a suitable FOLDER LIST screen.
22356 You may find that the <A HREF="h_rules_roles">"Roles"</A>
22357 facility can be used
22358 to replace the Form Letter Folder.
22361 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22362 details on the syntax of folder definitions.
22366 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22368 <End of help on this topic>
22371 ====== h_config_archived_folders =====
22374 <TITLE>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></TITLE>
22377 <H1>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></H1>
22380 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>,
22381 only more general. You may archive
22382 any of the folders in your incoming collection. This is a list of folder
22383 pairs, with the first separated from the second in the pair by a space.
22384 The first folder in a pair is the folder you want to archive, and the
22385 second folder is the folder that read messages from the first should be
22386 moved to. Depending on how you define the
22387 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
22388 setting, you may or may not be asked when you
22389 leave the first folder if you want read messages to be moved to the
22390 second folder. In either case, moving the messages means they will be
22391 deleted from the first folder.
22393 The name of the first folder in each pair can be either the technical
22394 specification of the folder (like what appears in your configuration file)
22395 or (much easier) the nickname that you gave the folder when you made it
22396 an incoming folder.
22399 <CENTER><SAMP>{monet.art.example.com}inbox {monet.art.example.com}mail/inbox-archive</SAMP></CENTER>
22400 <p>or, using nicknames:<p>
22401 <CENTER><SAMP>inbox inbox-archive</SAMP></CENTER>
22403 If these are not path names, they will be in the default collection for
22404 saves. Any valid folder specification, local or remote (via IMAP), is
22405 allowed. There is no default.
22407 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22408 details on the syntax of folder definitions.
22411 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22413 <End of help on this topic>
22416 ====== h_config_newsrc_path ======
22419 <TITLE>OPTION: <!--#echo var="VAR_newsrc-path"--></TITLE>
22422 <H1>OPTION: <!--#echo var="VAR_newsrc-path"--></H1>
22424 This option overrides the default name Alpine uses for your "newsrc" news
22425 status and subscription file. If set, Alpine will take this value as the
22426 full pathname for the desired newsrc file.<P>
22428 If this option is <B>not</B> set,
22429 <!--chtml if pinemode="os_windows"-->
22430 PC-Alpine looks first for $HOME\NEWSRC (where $HOME defaults to the root
22431 of the current drive, e.g. "C:\") and then it looks in the same
22432 directory as your pinerc file for NEWSRC.
22434 Unix Alpine looks for the file ~/.newsrc (that is, the file named .newsrc in
22435 your account's home directory).
22438 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22441 <End of help on this topic>
22444 ====== h_config_literal_sig =====
22447 <TITLE>OPTION: <!--#echo var="VAR_literal-signature"--></TITLE>
22450 <H1>OPTION: <!--#echo var="VAR_literal-signature"--></H1>
22452 With this option your actual signature, as opposed to
22453 the name of a file containing your signature,
22454 is stored in the Alpine configuration file.
22455 If this is defined it takes precedence over the <!--#echo var="VAR_signature-file"--> option.
22458 This is simply a different way to store the signature.
22459 The signature is stored inside your Alpine configuration file instead of in
22461 Tokens work the same way they do with the
22462 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A> so look there for
22466 The Setup/Signature command on Alpine's MAIN MENU will edit
22467 the "<!--#echo var="VAR_literal-signature"-->" by default. However, if no
22468 "<!--#echo var="VAR_literal-signature"-->" is defined and the file named in the
22469 "<!--#echo var="VAR_signature-file"-->" option exists, then the latter will be used
22473 The two character sequence \n (backslash followed by
22474 the character n) will be used to signify a line-break in your signature.
22475 You don't have to enter the \n, but it will be visible in the
22476 SETUP CONFIGURATION window after you are done editing the signature.
22480 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22482 <End of help on this topic>
22485 ====== h_config_signature_file =====
22488 <TITLE>OPTION: <!--#echo var="VAR_signature-file"--></TITLE>
22491 <H1>OPTION: <!--#echo var="VAR_signature-file"--></H1>
22493 If a <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined,
22494 then this "<!--#echo var="VAR_signature-file"-->" option will be ignored.
22495 You can tell that that is the case because the value of the
22496 "<!--#echo var="VAR_signature-file"-->" will show up as
22498 <CENTER><SAMP><Ignored: using <!--#echo var="VAR_literal-signature"--> instead></SAMP></CENTER>
22500 You may either use all Literal Signatures (signatures stored in your
22501 configuration file) throughout Alpine, or all signature files.
22502 You can't mix the two.
22504 This is the name of a file that will be automatically inserted into
22506 It typically contains information such as your
22507 name, email address and organizational affiliation.
22509 signature into the message as soon as you enter the composer so you
22510 can choose to remove it or edit it on a message by message basis.
22511 Signature file placement in message replies is controlled by the
22512 "<A HREF="h_config_sig_at_bottom"><!--#echo var="FEAT_signature-at-bottom"--></A>"
22513 setting in the feature list.
22516 The default file name is
22517 <!--chtml if pinemode="os_windows"-->
22518 "PINE.SIG" in the same directory as your PINERC file if your
22519 PINERC file is a local file.
22520 If your PINERC file is remote, then it will be in the directory specified
22521 by the "-aux local_directory" command line option.
22523 ".signature".
22527 To create or edit your signature file choose Setup from the MAIN MENU
22528 and then select S for Signature (Main/Setup/Signature). This puts you
22529 into the Signature Editor where you can enter a <EM>few</EM> lines of
22530 text containing your identity and affiliation.
22533 If the filename is followed by a vertical bar (|) then instead
22534 of reading the contents of the file the file is assumed to be a
22535 program that will produce the text to be used on its standard output.
22536 The program can't have any arguments and doesn't receive any input from Alpine,
22537 but the rest of the processing works as if the contents came from a file.
22540 Instead of storing the data in a local file, the
22541 signature data may be stored remotely in an IMAP folder.
22542 In order to do this,
22543 you must use a remote name for the file.
22544 A remote <!--#echo var="VAR_signature-file"--> name might look like:
22546 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/signature</SAMP></CENTER>
22549 The syntax used here is the same as the syntax used for remote configuration
22550 files from the command line.
22551 Note that you may not access an existing signature file remotely,
22552 you have to create a new <EM>folder</EM> that contains the signature data.
22553 If the name you use here for the signature file is a remote name, then when
22554 you edit the file from the Setup/Signature command the data will be stored
22555 remotely in the folder.
22556 You aren't required to do anything special to create the folder, it
22557 gets created automatically if you use a remote name.
22560 Besides regular text, the signature file may also contain
22561 (or a signature program may produce) tokens that
22562 are replaced with text that usually depends on the message you are replying
22564 For example, if the signature file contains the token
22566 <CENTER><SAMP>_DATE_</SAMP></CENTER>
22568 anywhere in the text, then that token is replaced by the date
22569 the message you are replying to or forwarding was sent.
22572 <CENTER><SAMP>_CURDATE_</SAMP></CENTER>
22574 that is replaced with the current date.
22575 The first is an example of a token that depends on the message you
22576 are replying to (or forwarding) and the second is an example which
22577 doesn't depend on anything other than the current date.
22578 You have to be a little careful with this facility since tokens that
22579 depend on the message you are replying to or forwarding will be replaced
22580 by nothing in the case where you are composing a new message from scratch.
22581 The use of <A HREF="h_rules_roles">"roles"</A> may help you
22583 It allows you to use different signature files in different cases.
22586 The list of tokens available for use in the signature file is
22587 <A HREF="h_index_tokens">here</A>.
22590 Instead of, or along with the use of "roles" to give you
22591 different signature files in different situations, there is also
22592 a way to conditionally include text based
22593 on whether or not a token would result in specific replacement text.
22594 For example, you could include some text based on whether or not
22595 the _NEWS_ token would result in any newsgroups if it was used.
22596 This is explained in detail
22597 <A HREF="h_reply_token_conditionals">here</A>.
22598 This isn't for the faint of heart.
22600 In the very unlikely event that you want to include a literal token
22601 in the signature you must precede it with a backslash character.
22604 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
22606 would produce something like
22608 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
22610 It is not possible to have a literal backslash followed by an expanded token.
22612 An alternate method for storing the signature data is available by using the
22613 <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> configuration option.
22614 This variable will be used by default.
22617 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22619 <End of help on this topic>
22622 ====== h_config_init_cmd_list =====
22625 <TITLE>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></TITLE>
22628 <H1>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></H1>
22630 The initial keystroke--or command--list option lets you start Alpine at
22631 any place you like.
22632 Whatever keystrokes you specify here will be executed
22633 by Alpine upon startup as a macro.
22634 The words SPACE, TAB, DOWN, UP, LEFT, and
22635 RIGHT indicate the pressing of those keys.
22636 CR indicates the pressing of the RETURN key.
22637 F1 through F12 represent the function keys, and ^ followed
22638 by a character indicates that key pressed along with the control key (in
22639 other words, ^P means Ctrl-P).
22640 As a shortcut notation, an element of the list may be several characters
22641 surrounded by double-quotes (").
22642 That will be expanded into the individual keystrokes
22643 (excluding the double-quote characters).
22644 For example, the quoted-string
22646 <P><CENTER>"ABC"</CENTER>
22649 is interpreted the same as the three separate list members
22651 <P><CENTER>A and B and C</CENTER>
22654 which is also the same as
22656 <P><CENTER>A,B,C</CENTER>
22659 An example: To view message 1 on startup,
22660 you could use an <!--#echo var="VAR_initial-keystroke-list"--> equal to
22662 <P><CENTER>I,J,1,CR,V</CENTER>
22665 An equivalent version of this is
22667 <P><CENTER>"IJ1",CR,V</CENTER>
22670 Restrictions: You cannot pre-type into the composer with the initial
22671 keystroke list, and you cannot mix function key commands with letter
22675 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22678 <End of help on this topic>
22681 ====== h_config_comp_hdrs =====
22684 <title>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></title>
22687 <h1>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></h1>
22689 You can control which headers you want visible when composing outgoing
22690 email using this option.
22691 You can specify any of the regular set, any
22692 <A HREF="h_compose_richhdr">Rich Header</A>,
22693 or any <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22694 that you have already defined.
22695 If you use this setting at all, you must specify all the
22696 headers you want to see, you can't just add to the regular header set.
22697 The default set is To:, Cc:, Attchmnt:, and Subject:.<p>
22699 Note that the "Newsgroups:" header will be abbreviated in the Composer
22700 display, but should be spelled out in full here.<p>
22702 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22704 <End of help on this topic>
22707 ====== h_config_custom_hdrs =====
22710 <TITLE>OPTION: <!--#echo var="VAR_customized-hdrs"--></TITLE>
22713 <H1>OPTION: <!--#echo var="VAR_customized-hdrs"--></H1>
22715 You may add your own custom headers to outgoing messages.
22716 Each header you specify here must include the header tag
22717 (<A HREF="h_composer_reply_to">Reply-To:</A>, Approved:, etc.)
22718 and may optionally include a value for that header.
22719 If you want to see these custom headers each time you compose a message,
22720 you must add them to your
22721 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> list,
22722 otherwise they become part
22723 of the rich header set that you only see when you press the
22724 <A HREF="h_compose_richhdr">Rich Header</A>
22725 <!--chtml if pinemode="function_key"-->(F5)
22726 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
22727 (If you are looking for a way to change which headers are <EM>displayed</EM>
22728 when you view a message, take a look at the
22729 <A HREF="h_config_viewer_headers"><!--#echo var="VAR_viewer-hdrs"--></A>
22731 Here's an example that shows how you might set your From address
22733 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
22735 and another showing how you might set a Reply-To address
22737 <CENTER><SAMP>Reply-To: user@example.com</SAMP></CENTER>
22739 You may also set non-standard header values here.
22740 For example, you could add
22742 <CENTER><SAMP>Organization: My Organization Name</SAMP></CENTER>
22746 <CENTER><SAMP>X-Favorite-Colors: Purple and Gold</SAMP></CENTER>
22748 If you include a value after the colon then that header will be included
22749 in your outgoing messages unless you delete it before sending.
22750 If a header in the <!--#echo var="VAR_customized-hdrs"--> list has only a tag but no value, then
22751 it will not be included in outgoing messages unless you edit a value
22755 <CENTER><SAMP>Reply-To:</SAMP></CENTER>
22757 is in the list, then the Reply-To header will be available for editing
22758 but won't be included unless a value is added while in the composer.
22760 It's actually a little more complicated than that.
22761 The values of headers that you set with the <!--#echo var="VAR_customized-hdrs"--> option are
22763 If the message you are about to compose already has a value for a header,
22764 that value is used instead of a value from your <!--#echo var="VAR_customized-hdrs"-->.
22765 For example, if you are Replying to a message the Subject field
22766 will already be filled in.
22767 In that case, if the <!--#echo var="VAR_customized-hdrs"--> list contains a Subject line, the
22768 custom subject will <EM>NOT</EM> be used.
22769 The subject derived from the subject of the message you are Replying
22770 to will be used instead.
22772 It is also possible to make header setting even more complicated and more
22774 <A HREF="h_rules_roles">Roles</A>,
22775 but if all you want to do is set a default value for a header, you don't
22776 need to think about Roles.
22778 If you change your From address you may also find it useful to add the
22779 changed From address to the
22780 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
22781 configuration option.
22783 Limitation: Because commas are used to separate the list of
22784 <!--#echo var="VAR_customized-hdrs"-->, it is not possible to have the value of a
22785 header contain a comma.
22786 Nor is there currently an "escape" mechanism provided
22789 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22792 <End of help on this topic>
22795 ====== h_config_viewer_headers =====
22798 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdrs"--></TITLE>
22801 <H1>OPTION: <!--#echo var="VAR_viewer-hdrs"--></H1>
22803 You may change the default list of headers that are viewed by listing
22804 the headers you want to view here. If the headers in your
22805 "<!--#echo var="VAR_viewer-hdrs"-->" list are present in the message, then they
22806 will be shown. The order of the headers you list will be honored. If
22807 the special value "all-except" is included as the first
22808 header in the "<!--#echo var="VAR_viewer-hdrs"-->" list, then all headers in the
22809 message except those in the list will be shown. The values are all
22813 Note that once you put anything in the "<!--#echo var="VAR_viewer-hdrs"-->" list,
22814 then the original default headers are ignored. So, if you just wanted
22815 to add the header Organization to the list, you would have to list
22816 Organization plus all of the other headers originally in the default
22817 list. If you just included Organization and nothing else, then you
22818 would see only the Organization header, nothing else.
22821 The default list of headers includes:
22840 If you are looking for a way to control which headers are included in
22841 outgoing mail and are visible or not in the composer, take a look at the
22843 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22844 and <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> instead of
22848 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22850 <End of help on this topic>
22853 ====== h_config_viewer_margin_left =====
22856 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-left"--></TITLE>
22859 <H1>OPTION: <!--#echo var="VAR_viewer-margin-left"--></H1>
22861 This variable controls the left-hand vertical margin's width in
22862 Alpine's Message Viewing screen.
22863 Its value is the number of space characters preceding each displayed line.
22864 For consistency with
22865 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>,
22866 you may specify the column number to start in
22867 (column numbering begins with number 1)
22868 instead of the width of the margin by appending a lower case letter
22869 "c" to the number.
22870 For example, a value of "2c" means to start the text in column two,
22871 which is entirely equivalent to a value of "1", which means to
22872 leave a margin of 1 space.
22874 The default is a left margin of 0 (zero).
22875 Misconfigurations (for example, negative values or values with starting
22876 left columns greater than the ending right column)
22877 are silently ignored.
22878 If the number of columns for text between the <!--#echo var="VAR_viewer-margin-left"--> and
22879 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22883 <End of help on this topic>
22886 ====== h_config_viewer_margin_right =====
22889 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-right"--></TITLE>
22892 <H1>OPTION: <!--#echo var="VAR_viewer-margin-right"--></H1>
22894 This variable controls the right-hand vertical margin's width in
22895 Alpine's Message Viewing screen.
22896 Its value is the number of space characters following each displayed line.
22897 You may specify the column number to end the text in
22898 (column numbering begins with number 1)
22899 instead of the width of the margin by appending a lower case letter
22900 "c" to the number.
22901 For example, a value of "76c" means to end the text in column 76.
22902 If the screen is 80 characters wide, this is equivalent to a value
22903 of "4", which means to leave a margin of 4 spaces.
22904 However, if you use different size screens at different times, then these
22905 two values are not equivalent.
22907 The default right margin is 4.
22908 Misconfigurations (for example, negative values or values with starting
22909 left columns greater than the ending right column)
22910 are silently ignored.
22911 If the number of columns for text between the
22912 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
22913 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22917 <End of help on this topic>
22920 ====== h_config_quote_suppression =====
22923 <TITLE>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></TITLE>
22926 <H1>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></H1>
22928 This option should be used with care.
22929 It will cause some of the quoted text to be eliminated from the
22930 display when viewing a message in the MESSAGE TEXT screen.
22931 For example, if you set the <!--#echo var="VAR_quote-suppression-threshold"--> to the
22932 value "5",
22933 this will cause quoted text that is longer than five lines to be truncated.
22934 Quoted text of five or fewer consecutive lines will be displayed in its entirety.
22935 Quoted text of more than six lines will have the first five lines displayed
22936 followed by a line that looks something like
22938 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
22940 As a special case, if exactly one line of quoted text would be hidden, the
22941 entire quote will be shown instead.
22942 So for the above example, quoted text that is exactly six lines long will
22943 will be shown in its entirety.
22944 (In other words, instead of hiding a single line and adding a line
22945 that announces that one line was hidden, the line is just shown.)
22947 If the sender of a message has carefully chosen the quotes that he or she
22948 includes, hiding those quotes may change the meaning of the message.
22949 For that reason, Alpine requires that when you want to set the value of this
22950 variable to something less than four lines, you actually have to set it
22951 to the negative of that number.
22952 So if you want to set this option to "3", you actually have to
22953 set it to "-3".
22954 The only purpose of this is to get you to think about whether or not you
22955 really want to do this!
22956 If you want to delete all quoted text you set the value of this option
22957 to the special value "-10".
22959 The legal values for this option are
22963 <TD> 0 </TD>
22964 <TD> Default, don't hide anything </TD>
22967 <TD> -1,-2,-3 </TD>
22968 <TD> Suppress quote lines past 1, 2, or 3 lines </TD>
22971 <TD> 4,5,6,... </TD>
22972 <TD> Suppress if more than that many lines </TD>
22975 <TD> -10 </TD>
22976 <TD> Suppress all quoted lines </TD>
22980 If you set this option to a non-default value you may sometimes wish to
22981 view the quoted text that is not shown.
22982 When this is the case, the
22983 <A HREF="h_common_hdrmode">HdrMode Command</A>
22984 may be used to show the hidden text.
22985 Typing the "H" command once will show the hidden text.
22986 Typing a second "H" will also turn on Full Header mode.
22987 The presence or absence of the HdrMode command is determined by the
22988 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
22989 Feature-List option in your Alpine configuration, so you will want to
22990 be sure that is turned on if you use quote suppression.
22992 For the purposes of this option, a quote is a line that begins with the
22993 character ">".
22995 Quotes are only suppressed when displaying a message on the screen.
22996 The entire quote will be left intact when printing or forwarding or something
22999 <End of help on this topic>
23002 ====== h_config_saved_msg_name_rule =====
23005 <TITLE>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></TITLE>
23008 <H1>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></H1>
23010 This option determines the default folder name when saving
23014 The default option is "default-folder", which is the folder
23015 called "saved-messages" in Unix Alpine and
23016 "savemail" in PC-Alpine. To change the default folder, modify
23017 the Alpine option called
23018 <A HREF="h_config_def_save_folder">"<!--#echo var="VAR_default-saved-msg-folder"-->"</A>.
23021 Choosing any of the "by-" options cause Alpine to attempt to
23022 get the chosen option's value for the message being saved (or for the
23023 first message being saved if using an aggregrate save).
23024 For example, if "by-from" is chosen, Alpine attempts to get the
23025 value of who the message came from (i.e. the from address).
23026 Alpine then attempts to save the message to a folder matching that value.
23027 If "by-from" is chosen and no value is obtained, Alpine uses
23028 "by-sender".
23029 The opposite is also true.
23030 If "by-recipient" is chosen and the message was posted to a
23031 newsgroup, Alpine will use the newsgroup name.
23032 If "by-replyto" is chosen and no value is obtained, Alpine uses
23033 "by-from".
23036 If any of the "by-realname" options are chosen, Alpine will attempt
23037 to use the personal name part of the address instead of the mailbox part.
23038 If any of the "by-nick" options are chosen, the
23039 address is looked up in your address book and if found, the
23040 nickname for that entry is used.
23041 Only simple address book entries are checked, not distribution lists.
23042 Similarly, if any of the
23043 "by-fcc" options are chosen, the fcc from the corresponding
23044 address book entry is used.
23045 If by-realname, or the by-nick or by-fcc lookups result in no value,
23046 then if the chosen option ends with the "then-from",
23047 "then-sender", "then-replyto",
23048 or "then-recip" suffix, Alpine
23049 reverts to the same behavior as "by-from",
23050 "by-sender", "by-replyto", or "by-recip"
23051 depending on which option was specified.
23052 If the chosen option doesn't end with one of
23053 the "then-" suffixes, then Alpine reverts to the default
23054 folder when no match is found in the address book.
23057 Choosing the option called "last-folder-used", causes Alpine
23058 to save to the folder that you saved to the last time you saved a
23059 message. The first time you save a message in an Alpine session, Alpine
23060 attempts to save the message to the default folder.
23063 Here is an example to make some of the options clearer.
23064 If the message is From
23066 <CENTER><SAMP>Fred Flintstone <flint@bedrock.org></SAMP></CENTER>
23068 and this rule is set to "by-from", then the default folder offered
23069 in the save dialog would be "flint".
23071 If this rule is set to "by-realname-of-from" then the default would
23072 be "Fred Flintstone".
23074 If this rule is set to "by-nick-of-from" then Alpine will search
23075 for the address "flint@bedrock.org" in your address book.
23076 If an entry is found and it has a nickname associated with it, that nickname
23077 will be offered as the default folder.
23078 If not, the default saved message folder will be offered as the default.
23080 If this rule is set to "by-fcc-of-from" then Alpine will search
23081 for the address "flint@bedrock.org" in your address book.
23082 If an entry is found and it has an Fcc associated with it, that Fcc
23083 will be offered as the default folder.
23084 If not, the default saved message folder will be offered as the default.
23086 If this rule is set to "by-nick-of-from-then-from" then Alpine will search
23087 for the address "flint@bedrock.org" in your address book.
23088 If an entry is found and it has a nickname associated with it, that nickname
23089 will be offered as the default folder.
23090 If it is not found (or has no nickname) then the default offered will be
23091 the same as it would be for the "by-from" rule.
23092 That is, it would be "flint"
23095 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23097 <End of help on this topic>
23100 ====== h_config_fcc_rule =====
23103 <TITLE>OPTION: <!--#echo var="VAR_fcc-name-rule"--></TITLE>
23106 <H1>OPTION: <!--#echo var="VAR_fcc-name-rule"--></H1>
23108 This option determines the default name for folder carbon copy. Choose
23112 <DT>default-fcc</DT>
23113 <DD>This is the normal default, the value of which is set in the
23114 "<!--#echo var="VAR_default-fcc"-->" variable as specified earlier in this
23118 <DT>last-fcc-used</DT>
23119 <DD> Causes Alpine to use the folder that was last
23120 used in the fcc field
23123 <DT>by-nickname</DT>
23124 <DD>Means that Alpine will use the nickname
23125 from your address book that matches the first address in the To line.
23126 If there is no match, it will use the value of the
23127 "<!--#echo var="VAR_default-fcc"-->" variable.
23130 <DT>by-recipient</DT>
23131 <DD>Means Alpine will form a folder name
23132 based on the left hand side of the first address in the To line.
23135 <DT>by-nick-then-recip</DT>
23136 <DD>Means that it will use the
23137 matching nickname from your address book if there is one, otherwise it
23138 will extract the recipient name from the address and use that (like
23142 <DT>current-folder</DT>
23143 <DD>Causes a copy to be written to
23144 the currently open folder, unless that is the INBOX. In the case
23145 where the current folder is the INBOX, the "<!--#echo var="VAR_default-fcc"-->" is
23151 Note: Whatever the fcc specified by the rule here, it will be
23152 over-ridden by any fcc entries you have in your address book.
23156 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23158 <End of help on this topic>
23161 ====== h_config_sort_key =====
23164 <TITLE>OPTION: <!--#echo var="VAR_sort-key"--></TITLE>
23167 <H1>OPTION: <!--#echo var="VAR_sort-key"--></H1>
23169 This option determines the order in which messages will be displayed in
23170 the MESSAGE INDEX screen. Choose from:
23173 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
23174 <LI> <A HREF="h_index_sort_date">Date</A>
23175 <LI> <A HREF="h_index_sort_subj">Subject</A>
23176 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
23177 <LI> <A HREF="h_index_sort_thread">Thread</A>
23178 <LI> <A HREF="h_index_sort_from">From</A>
23179 <LI> <A HREF="h_index_sort_size">Size</A>
23180 <LI> <A HREF="h_index_sort_score">Score</A>
23181 <LI> <A HREF="h_index_sort_to">To</A>
23182 <LI> <A HREF="h_index_sort_cc">Cc</A>
23186 Each type of sort may also be reversed.
23187 Normal default is by "Arrival".
23190 A possible point of confusion arises when you change the configuration
23191 of the <!--#echo var="VAR_sort-key"-->.
23192 The folder will normally be re-sorted when you go back to viewing the
23194 However, if you have manually sorted the folder with the
23196 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
23197 command, then it will not be re-sorted until the next time it is opened.
23201 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23203 <End of help on this topic>
23206 ====== h_config_other_startup =====
23209 <TITLE>OPTION: Set Startup Rule</TITLE>
23212 <H1>OPTION: Set Startup Rule</H1>
23214 This option determines which message will be the <EM>current message</EM> when
23215 the folder is first opened.
23216 It works the same way that the option
23217 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
23218 works, so look there for help.
23219 It may be used for any folder, not just incoming folders.
23223 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23225 <End of help on this topic>
23228 ====== h_config_perfolder_sort =====
23231 <TITLE>Set Sort Order</TITLE>
23234 <H1>Set Sort Order</H1>
23236 This option determines the order in which messages will be displayed in
23237 the MESSAGE INDEX screen when the Current Folder Type set in the
23238 Pattern is a match. Choose from:
23241 <LI> <A HREF="h_index_sort_default">Default</A>
23242 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
23243 <LI> <A HREF="h_index_sort_date">Date</A>
23244 <LI> <A HREF="h_index_sort_subj">Subject</A>
23245 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
23246 <LI> <A HREF="h_index_sort_thread">Thread</A>
23247 <LI> <A HREF="h_index_sort_from">From</A>
23248 <LI> <A HREF="h_index_sort_size">Size</A>
23249 <LI> <A HREF="h_index_sort_score">Score</A>
23250 <LI> <A HREF="h_index_sort_to">To</A>
23251 <LI> <A HREF="h_index_sort_cc">Cc</A>
23255 Each type of sort may also be reversed.
23256 Normal default is by "Arrival".
23259 A possible point of confusion arises when you change the configuration
23260 of the Sort Order for the currently open folder.
23261 The folder will normally be re-sorted when you go back to viewing the
23263 However, if you have manually sorted the folder with the
23265 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
23266 command, then it will not be re-sorted until the next time it is opened.
23270 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23272 <End of help on this topic>
23275 ====== h_config_fld_sort_rule =====
23278 <TITLE>OPTION: <!--#echo var="VAR_folder-sort-rule"--></TITLE>
23281 <H1>OPTION: <!--#echo var="VAR_folder-sort-rule"--></H1>
23283 This option controls the order in which folder list entries will be
23284 presented in the FOLDER LIST screen. Choose one of the following:
23287 <DT>Alphabetical</DT>
23288 <DD>sort by alphabetical name independent of type
23291 <DT>Alpha-with-dirs-last</DT>
23292 <DD>sort by alphabetical name grouping directory entries
23293 to the end of the list
23296 <DT>Alpha-with-dirs-first</DT>
23297 <DD>sort by alphabetical name grouping directory entries
23298 to the start of the list
23302 The normal default is "Alphabetical".
23306 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23308 <End of help on this topic>
23311 ====== h_config_ab_sort_rule =====
23314 <TITLE>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></TITLE>
23317 <H1>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></H1>
23319 This option controls the order in which address book entries will be
23320 presented. Choose one of the following:
23324 <DD>use fullname field, lists mixed in
23327 <DT>fullname-with-lists-last</DT>
23328 <DD>use fullname field, but put lists at end
23332 <DD>use nickname field, lists mixed in
23335 <DT>nickname-with-lists-last</DT>
23336 <DD>use nickname field, but put lists at end
23340 <DD>don't change order of file
23345 The normal default is "fullname-with-lists-last".
23346 If you use an address book from more than one computer and those
23347 computers sort the address book differently then the sort order
23348 will be the order where the last change to the address book was
23350 There are two reasons the sorting might be different on different
23352 First, the <!--#echo var="VAR_addrbook-sort-rule"--></a> may be set differently in the two
23354 Second, the collation rules on the two computers may be different.
23355 For example, one system might ignore special characters while the other
23356 doesn't or one may sort upper and lower case letters together while
23358 In any case, the order you see is the order on the system where the
23359 last change was made, for example by an address book edit or a
23360 Take Address command.
23364 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23366 <End of help on this topic>
23369 ====== h_config_post_char_set =====
23372 <TITLE>OPTION: <!--#echo var="VAR_posting-character-set"--></TITLE>
23375 <H1>OPTION: <!--#echo var="VAR_posting-character-set"--></H1>
23377 The <!--#echo var="VAR_posting-character-set"--> configuration option is used
23378 when sending messages.
23382 When sending a message the text typed in the composer is
23383 labeled with the character set specified by this option.
23384 If the composed text is not fully representable in the
23385 specified <!--#echo var="VAR_posting-character-set"-->, then it is labeled as "UTF-8."
23389 Attachments are labeled with your
23390 <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>.
23393 Generally, there should be little need to set this option.
23395 default behavior is to label composed text as specifically as
23396 possible. That is, if the composed text has no non-ASCII characters,
23397 it is labeled as "US-ASCII." Similarly, if it is composed of
23398 only ISO-8859-15 characters, it is labeled as such. Alpine will
23399 attempt to automatically detect a number of character sets including ISO-8859-15,
23400 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
23401 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, and EUC-KR.
23402 If the message contains a mix of character sets,
23403 it is labeled as "UTF-8."
23407 This setting is provided to allow you to force a particular character set that
23408 Alpine does not automatically detect. For example, if a message is representable
23409 in more than one character set then Alpine may choose a different default
23411 Lastly, by setting this option explicitly to
23412 "UTF-8" all non-ASCII messages you send will be labeled as
23413 "UTF-8" instead of something more specific.
23416 In the Setup/Config screen you may choose from a list of all the
23417 character sets Alpine knows about by using the "T" ToCharsets command.
23421 <A HREF="h_config_char_set">"Display Character Set"</A>
23422 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
23423 are closely related.
23424 Setting the feature
23425 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23426 should cause this option to be ignored.
23430 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23432 <End of help on this topic>
23435 ====== h_config_unk_char_set =====
23438 <TITLE>OPTION: <!--#echo var="VAR_unknown-character-set"--></TITLE>
23441 <H1>OPTION: <!--#echo var="VAR_unknown-character-set"--></H1>
23443 The <!--#echo var="VAR_unknown-character-set"--> configuration option is used
23444 when reading or replying to messages.
23448 A text message should either be made up of all US-ASCII characters
23449 or it should contain a charset label which tells the software which
23450 character set encoding to use to interpret the message.
23451 Sometimes a malformed message may be unlabeled but contain non-ascii text.
23452 This message is outside of the standards so any attempt to read it could fail.
23453 When Alpine attempts to read such a message it will try to interpret the
23454 text in the character set you specify here.
23455 For example, if you have correspondents who send you unlabeled messages that
23456 are usually made up of characters from the WINDOWS-1251 character set, setting
23457 this <!--#echo var="VAR_unknown-character-set"--> to <CODE>WINDOWS-1251</CODE> will
23458 allow you to read those messages.
23459 Of course, if the unlabeled message is actually in some other character set,
23460 then you may see garbage on your screen.
23462 Instead of just unlabeled text, this option also affects text which is labeled
23463 with the charsets "X-Unknown", "MISSING_PARAMETER_VALUE"
23464 or "US-ASCII".
23467 In the Setup/Config screen you may choose from a list of all the
23468 character sets Alpine knows about by using the "T" ToCharsets command.
23472 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23474 <End of help on this topic>
23477 ====== h_config_char_set =====
23480 <TITLE>OPTION: Display Character Set</TITLE>
23483 <H1>OPTION: Display Character Set</H1>
23485 The Display Character Set configuration option is used when viewing messages.
23487 Alpine uses Unicode characters internally and
23488 it is a goal for Alpine to handle email in many different languages.
23489 Alpine will properly display only left-to-right character sets
23490 in a fixed-width font. Specifically, Alpine assumes that a fixed-width
23491 font is in use, in the sense that
23492 characters are assumed to take up zero, one, or two character cell
23493 widths from left to right on the screen. This is true even in PC-Alpine.
23496 Alpine recognizes some local character sets that are right-to-left
23497 (Arabic, Hebrew, and Thai) or not representable in a fixed-width font
23498 (Arabic) and properly converts texts in these character sets to/from
23499 Unicode; however, there are known display bugs with these character
23503 There are three possible configuration character settings and some
23504 environment variable settings that can affect how Alpine
23505 handles international characters.
23506 The first two of these are only available in UNIX Alpine.
23507 The three configuration options are
23508 Display Character Set,
23509 Keyboard Character Set, and
23510 <!--#echo var="VAR_posting-character-set"-->.
23511 The Keyboard Character Set defaults to being the same value
23512 as the Display Character Set, and that is usually correct, because
23513 the keyboard almost always produces characters in the same character set
23514 as the display displays.
23515 The Display Character Set is the character set that Alpine
23516 will attempt to use when sending characters to the display.
23519 By default, the Display Character Set variable is not set and UNIX Alpine
23520 will attempt to get this information from the environment.
23521 In particular, the <CODE>nl_langinfo(CODESET)</CODE> call is used.
23522 This usually depends on the setting of the environment variables LANG or LC_CTYPE.
23523 An explicit configuration setting for Display Character Set will,
23524 of course, override any default setting.
23526 For PC-Alpine the Display Character Set
23527 and the Keyboard Character Set
23528 are always equivalent to <CODE>UTF-8</CODE> and this is not settable.
23531 It is probably best to use UNIX Alpine in a terminal emulator
23532 capable of displaying UTF-8 characters, since that will allow you to
23533 view just about any received text that is correctly formatted (note,
23534 however, the above comments about known index display bugs with certain
23535 character sets). You'll need to have an emulator that uses a UTF-8 font
23536 and you'll need to set up your environment to use a UTF-8 charmap. For
23537 example, on a Linux system you might include
23539 <CENTER> <CODE>setenv LANG en_US.UTF-8</CODE> </CENTER>
23542 or something similar in your UNIX startup files.
23543 You'd also have to select a UTF-8 font in your terminal emulator.
23546 The types of values that the character set variables may be set to are
23547 <CODE>UTF-8</CODE>, <CODE>ISO-8859-1</CODE>, or <CODE>EUC-JP</CODE>.
23548 The <CODE>ISO-2022</CODE> character sets are not supported for input or
23549 for display, but as a special case, <CODE>ISO-2022-JP</CODE> is supported
23550 for use only as a <!--#echo var="VAR_posting-character-set"-->.
23551 In the Setup/Config screen you may choose from a list of all the
23552 character sets Alpine knows about by using the "T" ToCharsets command.
23553 Here is a list of many of the possible character sets:
23557 <TR> <TD>UTF-8</TD> <TD>Unicode</TD> </TR>
23558 <TR> <TD>US-ASCII</TD> <TD>7 bit American English characters</TD> </TR>
23559 <TR> <TD>ISO-8859-1</TD> <TD>8 bit European "Latin 1" character set</TD> </TR>
23560 <TR> <TD>ISO-8859-2</TD> <TD>8 bit European "Latin 2" character set</TD> </TR>
23561 <TR> <TD>ISO-8859-3</TD> <TD>8 bit European "Latin 3" character set</TD> </TR>
23562 <TR> <TD>ISO-8859-4</TD> <TD>8 bit European "Latin 4" character set</TD> </TR>
23563 <TR> <TD>ISO-8859-5</TD> <TD>8 bit Latin and Cyrillic</TD> </TR>
23564 <TR> <TD>ISO-8859-6</TD> <TD>8 bit Latin and Arabic</TD> </TR>
23565 <TR> <TD>ISO-8859-7</TD> <TD>8 bit Latin and Greek</TD> </TR>
23566 <TR> <TD>ISO-8859-8</TD> <TD>8 bit Latin and Hebrew</TD> </TR>
23567 <TR> <TD>ISO-8859-9</TD> <TD>8 bit European "Latin 5" character set</TD> </TR>
23568 <TR> <TD>ISO-8859-10</TD> <TD>8 bit European "Latin 6" character set</TD> </TR>
23569 <TR> <TD>ISO-8859-11</TD> <TD>Latin and Thai</TD> </TR>
23570 <TR> <TD>ISO-8859-12</TD> <TD>Reserved</TD> </TR>
23571 <TR> <TD>ISO-8859-13</TD> <TD>8 bit European "Latin 7" character set</TD> </TR>
23572 <TR> <TD>ISO-8859-14</TD> <TD>8 bit European "Latin 8" character set</TD> </TR>
23573 <TR> <TD>ISO-8859-15</TD> <TD>8 bit European "Latin 9" character set</TD> </TR>
23574 <TR> <TD>ISO-8859-16</TD> <TD>8 bit European "Latin 10" character set</TD> </TR>
23575 <TR> <TD>KOI8-R</TD> <TD>8 bit Latin and Russian</TD> </TR>
23576 <TR> <TD>KOI8-U</TD> <TD>8 bit Latin and Ukranian</TD> </TR>
23577 <TR> <TD>WINDOWS-1251</TD> <TD>8 bit Latin and Russian</TD> </TR>
23578 <TR> <TD>TIS-620</TD> <TD>8 bit Latin and Thai</TD> </TR>
23579 <TR> <TD>VISCII</TD> <TD>8 bit Latin and Vietnamese</TD> </TR>
23580 <TR> <TD>GBK</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23581 <TR> <TD>GB2312</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23582 <TR> <TD>CN-GB</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23583 <TR> <TD>BIG5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
23584 <TR> <TD>BIG-5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
23585 <TR> <TD>EUC-JP</TD> <TD>Latin and Japanese</TD> </TR>
23586 <TR> <TD>SHIFT-JIS</TD> <TD>Latin and Japanese</TD> </TR>
23587 <TR> <TD>EUC-KR</TD> <TD>Latin and Korean</TD> </TR>
23588 <TR> <TD>KSC5601</TD> <TD>Latin and Korean</TD> </TR>
23592 When reading incoming email, Alpine understands many different
23593 character sets and is able to convert the incoming mail into Unicode.
23594 The Unicode will be converted to the Display Character Set
23595 for display on your terminal.
23596 Characters typed at the keyboard will be converted from the
23597 Keyboard Character Set to Unicode for Alpine's internal
23599 You may find that you can read some malformed messages that do not
23600 contain a character set label by setting the option
23601 <A HREF="h_config_unk_char_set">"<!--#echo var="VAR_unknown-character-set"-->"</A>.
23604 The <!--#echo var="VAR_posting-character-set"--> is used when sending messages.
23605 The default behavior obtained by leaving this variable unset is usually
23606 what is wanted. In that default case, Alpine will attempt
23607 to label the message with the most specific character set from the
23608 rather arbitrary set
23610 US-ASCII, ISO-8859-15,
23611 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
23612 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, EUC-KR, and UTF-8.
23615 For example, if the message is made up of only US-ASCII characters, it
23616 will be labeled US-ASCII. Otherwise, if it is all ISO-8859-15 characters,
23617 that will be the label. If that doesn't work the same is tried for the
23618 remaining members of the list.
23621 It might make sense to set <!--#echo var="VAR_posting-character-set"--> to an
23622 explicit value instead.
23623 For example, if you usually send messages in Greek, setting this
23624 option to ISO-8859-7 will result in messages being labeled as
23625 US-ASCII if there are no non-ascii characters, ISO-8859-7 if there
23626 are only Greek characters, or UTF-8 if there are some characters
23627 that aren't representable in ISO-8859-7.
23628 Another possibility is to set this option explicitly to UTF-8.
23630 Alpine labels only ascii messages as US-ASCII and all other
23635 <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
23636 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
23637 are closely related to this option.
23638 Setting the feature
23639 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23640 should cause this option to be ignored.
23643 When displaying a message, Alpine compares this setting to the character
23644 set specified in the message. If not all of the
23645 characters in the message can be displayed using the Display Character Set
23646 then Alpine places an editorial
23647 comment in the displayed text (enclosed in square-brackets) indicating
23648 that some characters may not be displayed correctly.
23649 This comment may be eliminated by turning on the option
23650 <A HREF="h_config_quell_charset_warning"><!--#echo var="FEAT_quell-charset-warning"--></A>.
23654 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23656 <End of help on this topic>
23659 ====== h_config_key_char_set =====
23662 <TITLE>OPTION: Keyboard Character Set</TITLE>
23665 <H1>OPTION: Keyboard Character Set</H1>
23669 The Keyboard Character Set identifies the character set of the characters
23670 coming from your keyboard.
23671 It defaults to having the same value as your
23672 <A HREF="h_config_char_set">"Display Character Set"</A>,
23673 which in turn defaults to a value obtained from your environment.
23674 It is unlikely that you will need to use this option, because the keyboard
23675 almost always produces the same kind of characters as the display displays.
23678 This character set is also used when accessing files in your local
23680 The names of the files are assumed to be in the same character set as
23681 what the keyboard produces, as well as the contents of the files.
23684 In the Setup/Config screen you may choose from a list of all the
23685 character sets Alpine knows about by using the "T" ToCharsets command.
23689 <A HREF="h_config_char_set">"Display Character Set"</A>
23690 and <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
23691 are closely related.
23692 Setting the feature
23693 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23694 should cause this option to be ignored.
23698 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23700 <End of help on this topic>
23703 ====== h_config_editor =====
23706 <TITLE>OPTION: <!--#echo var="VAR_editor"--></TITLE>
23709 <H1>OPTION: <!--#echo var="VAR_editor"--></H1>
23711 <!--#echo var="VAR_editor"--> specifies the program invoked by ^_ in the Composer. This is
23712 normally an alternative to Alpine's internal composer (Pico). You could use
23713 this setting to specify an alternate editor to use occasionally or if you
23714 have a favorite editor and want to use it all the time (see the
23715 <A HREF="h_config_alt_ed_now">"<!--#echo var="FEAT_enable-alternate-editor-implicitly"-->"</A> setting). <P>
23716 If you specify multiple editors for this option, ^_ will invoke the first one
23717 of those specified that exists and is executable. When specifying a program
23718 for use here, make sure that the format of the text it saves -- which, when
23719 you exit it, will become the message body in Alpine -- is appropriate
23720 for the body of an email message; avoid proprietary formats that may result in
23721 a message body that the recipient of your message will be unable to decipher.
23723 <!--chtml if pinemode="os_windows"-->
23725 If you are in doubt about what editors are available on your system, or which
23726 of them may be appropriate for specification here, ask your local computing
23730 Note that if <a href="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></a> is
23731 unset, outgoing text will be set as flowed. In most cases this will be fine,
23732 but if the editor has a "flowed text" mode, it would be best to
23736 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23739 <End of help on this topic>
23742 ====== h_config_speller =====
23745 <TITLE>OPTION: <!--#echo var="VAR_speller"--></TITLE>
23748 <H1>OPTION: <!--#echo var="VAR_speller"--></H1>
23752 For PC-Alpine, you must install the aspell library code that you
23754 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
23756 This option affects the behavior of the ^T (spell check) command in the
23757 Composer. It specifies the program invoked by ^T in the Composer.
23758 By default, Alpine uses
23760 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
23762 if it knows where to find "aspell".
23763 If there is no "aspell" command available but the command "ispell" is available
23764 then the command used is
23766 <CENTER><SAMP>ispell -l</SAMP></CENTER>
23768 Otherwise, the ancient "spell" command is used.
23770 If you specify a value for this command (with full pathname) then that is what
23771 will be used instead of any of the defaults.
23773 spell-checking program, Alpine appends a tempfile name (where the message is
23774 passed) to the command line. Alpine expects the speller to correct the
23775 spelling in that file. When you exit from that program Alpine will read the
23776 tempfile back into the composer.
23778 Don't set this speller option to the standard Unix spell command.
23779 That won't work because spell works in a different way.
23783 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23785 <End of help on this topic>
23788 ====== h_config_aspell_dictionary =====
23791 <TITLE>OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></TITLE>
23794 <H1>OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></H1>
23798 This option specifies a list of dictionaries you will use with
23799 aspell. A sample entry is "en_US" for american english, or
23800 "en_GB" for brittish english.
23804 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23806 <End of help on this topic>
23809 ====== h_config_display_filters =====
23812 <TITLE>OPTION: <!--#echo var="VAR_display-filters"--></TITLE>
23815 <H1>OPTION: <!--#echo var="VAR_display-filters"--></H1>
23817 This option defines a list of text-filtering commands (programs or
23818 scripts) that may be used to filter text portions of received messages
23819 prior to their use (e.g., presentation in the "MESSAGE TEXT"
23820 display screen, exporting to a text file).
23821 For security reasons, the full path name of the
23822 filter command must be specified.
23825 The command is executed and the message is piped into its standard input.
23826 The standard output of the command is read back by Alpine. The
23827 "_TMPFILE_" token (see below) overrides this default behavior.
23830 The filter's use is based on the configured "trigger" string. The
23831 format of a filter definition is:
23834 <CENTER><trigger> <command> <arguments></CENTER>
23837 You can specify as many filters as you wish, separating them with a comma.
23838 Each filter can have only one trigger and command. Thus, two trigger
23839 strings that invoke the same command require separate filter
23843 The "trigger" is simply text that, if found in the message,
23844 will invoke the associated command. If the trigger contains any space
23845 characters, it must be placed within quotes. Likewise, should you
23846 wish a filter to be invoked unconditionally, define the trigger as the
23847 null string, "" (two consecutive double-quote characters). If the
23848 trigger string is found anywhere in the text of the message the filter
23849 is invoked. Placing the trigger text within the tokens defined below
23850 changes where within the text the trigger must be before considering
23854 Trigger Modifying Tokens:
23856 <DT>_CHARSET(<VAR>string</VAR>)_</DT>
23857 <DD>This token tells Alpine to invoke the supplied command
23858 if the text is in a character set matching <VAR>string</VAR>
23859 (e.g., ISO-8859-2 or ISO-2022-JP).
23863 <DT>_LEADING(<VAR>string</VAR>)_</DT>
23864 <DD>This token tells Alpine to invoke the supplied command
23865 if the enclosed <VAR>string</VAR> is found to be the first
23866 non-whitespace text.
23867 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23868 the space character.
23871 <DT>_BEGINNING(<VAR>string</VAR>)_</DT>
23872 <DD>This token tells Alpine to invoke the supplied command
23873 if the enclosed <VAR>string</VAR> is found at the beginning
23874 of any line in the text.
23875 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23876 the space character.
23881 The "command" and "arguments" portion is simply
23882 the command line to be invoked if the trigger string is found. Below
23883 are tokens that Alpine will recognize and replace with special values
23884 when the command is actually invoked.
23887 Command Modifying Tokens:
23891 <DD>When the command is executed, this token is
23892 replaced with the path and name of the temporary
23893 file containing the text to be filtered. Alpine
23894 expects the filter to replace this data with the
23898 NOTE: Use of this token implies that the text to
23899 be filtered is not piped into standard input of the
23900 executed command and its standard output is ignored.
23901 Alpine restores the tty modes before invoking the
23902 filter in case the filter interacts with the user
23903 via its own standard input and output.
23906 <DT>_RESULTFILE_</DT>
23907 <DD>When the command is executed, this token is
23908 replaced with the path and name of a temporary
23909 file intended to contain a status message from the
23910 filter. Alpine displays this in the message status
23914 <DT>_DATAFILE_</DT>
23915 <DD>When the command is executed, this token is
23916 replaced with the path and name of a temporary
23917 file that Alpine creates once per session and deletes
23918 upon exit. The file is intended to be used by the
23919 filter to store state information between instances
23923 <DT>_PREPENDKEY_</DT>
23924 <DD>When the command is executed, this token indicates that a random
23925 number will be passed down the input stream before the message text.
23926 This number could be used as a session key. It is sent in this way to
23927 improve security. The number is unique to the current Alpine session
23928 and is only generated once per session.
23932 <DD>When the filter is executed, this token tells Alpine not to repaint
23933 the screen while the command is being executed. This can be used with
23934 filters that do not interact with the user, and therefore repainting
23935 the screen is not necessary.
23941 <A HREF="h_config_disable_reset_disp"><!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></A> is related.
23943 Performance caveat/considerations:
23945 Testing for the trigger and invoking the filter doesn't come for free.
23946 There is overhead associated with searching for the trigger string, testing
23947 for the filter's existence and actually piping the text through the filter.
23948 The impact can be reduced if the Trigger Modifying Tokens above are
23951 <End of help on this topic>
23954 ====== h_config_sending_filter =====
23957 <TITLE>OPTION: <!--#echo var="VAR_sending-filters"--></TITLE>
23960 <H1>OPTION: <!--#echo var="VAR_sending-filters"--></H1>
23962 This option defines a list of text-filtering commands (programs and
23963 scripts) that may be selectively invoked to process a message just before
23964 it is sent. If set, the Composer's ^X (Send) command will allow you to
23965 select which filter (or none) to apply to the message before it is sent.
23966 For security reasons, the full path of the filter program must be
23970 Command Modifying Tokens:
23973 <DT>_RECIPIENTS_</DT>
23974 <DD>When the command is executed, this token is replaced
23975 with the space delimited list of recipients of the
23976 message being sent.
23981 When the command is executed, this token is
23982 replaced with the path and name of the temporary
23983 file containing the text to be filtered. Alpine
23984 expects the filter to replace this data with the
23988 NOTE: Use of this token implies that the text to
23989 be filtered is not piped into standard input of the
23990 executed command and its standard output is ignored.
23991 Alpine restores the tty modes before invoking the
23992 filter in case the filter interacts with the user
23993 via its own standard input and output.
23996 <DT>_RESULTFILE_</DT>
23997 <DD>When the command is executed, this token is
23998 replaced with the path and name of a temporary
23999 file intended to contain a status message from the
24000 filter. Alpine displays this in the message status
24004 <DT>_DATAFILE_</DT>
24005 <DD>When the command is executed, this token is replaced
24006 in the command line with the path and name of a
24007 temporary file that Alpine creates once per session
24008 and deletes upon exit. The file is intended to be
24009 used by the filter to store state information between
24010 instances of the filter.
24013 <DT>_PREPENDKEY_</DT>
24014 <DD>When the command is executed, this token indicates
24015 that a random number will be passed down the input
24016 stream before the message text. This number could
24017 be used as a session key. It is sent in this way
24018 to improve security. The number is unique to the
24019 current Alpine session and is only generated once per
24023 <DT>_INCLUDEALLHDRS_</DT>
24024 <DD>When the command is executed, this token indicates
24025 that the headers of the message will be passed down the input stream
24026 before the message text.
24029 <DT>_MIMETYPE_</DT>
24030 <DD>When the command is executed, this token is replaced in the
24031 command name with a temporary file name used to accept any new MIME
24032 Content-Type information necessitated by the output of the filter.
24033 Upon the filter's exit, if the file contains new MIME type
24034 information, Alpine verifies its format and replaces the outgoing
24035 message's MIME type information with that contained in the file. This
24036 is basically a cheap way of sending something other than Text/Plain.
24041 NOTE: Only the body text, which is visible in the Composer, is piped
24042 through this filter. Attachments are not sent to the filter.
24044 Sending filters are not used if the feature
24045 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set.
24048 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24050 <End of help on this topic>
24053 ====== h_config_keywords =====
24056 <TITLE>OPTION: <!--#echo var="VAR_keywords"--></TITLE>
24059 <H1>OPTION: <!--#echo var="VAR_keywords"--></H1>
24061 You may define your own set of keywords and optionally set them on a
24062 message by message basis.
24063 These are similar to the "Important" flag which the user
24064 may set using the Flag command.
24065 The difference is that the Important flag is always present for each folder.
24066 User-defined keywords are chosen by the user.
24067 You may set up the list of possible keywords here, or you may add keywords
24068 from the Flag Details screen that you
24069 can get to after typing the
24070 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
24072 After the keywords have been defined,
24073 then you use the <A HREF="h_common_flag">Flag command</A>
24074 to set or clear the keywords in each message.
24075 The behavior of the flag command may be modified by using the
24076 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
24077 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
24080 Keywords may be used when Selecting messages (Select Keyword).
24081 Keywords may also be used in the Patterns of Rules (Filters, Indexcolors, etc).
24082 Filter Rules may be used to set keywords automatically.
24083 Keywords may be displayed as part of the Subject of a message by using
24084 the SUBJKEY or SUBJKEYINIT tokens in the
24085 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
24086 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
24087 option may be used to modify the display of keywords using
24088 SUBJKEY and SUBJKEYINIT slightly.
24089 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
24090 screen by using the KEY or KEYINIT tokens.
24091 It is also possible to color keywords in the index using the
24092 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
24093 Keywords are not supported by all mail servers.
24096 You may give keywords nicknames if you wish.
24097 If the keyword definition you type in contains a SPACE character, then the
24098 actual value of the keyword is everything after the last SPACE and the
24099 nickname for that keyword is everything before the last SPACE.
24100 For example, suppose you are trying to interoperate with another email program
24101 that uses a particular keyword with an unpleasant name.
24102 Maybe it uses a keyword called
24104 <CENTER><SAMP>VendorName.SoftwareName.08</SAMP></CENTER>
24106 but for you that keyword means that the message is work-related.
24107 You could define a keyword to have the value
24109 <CENTER><SAMP>Work VendorName.SoftwareName.08</SAMP></CENTER>
24111 and then you would use the name "Work" when dealing with
24112 that keyword in Alpine.
24113 If you defined it as
24115 <CENTER><SAMP>My Work VendorName.SoftwareName.08</SAMP></CENTER>
24117 the nickname would be everything before the last SPACE, that is the nickname
24118 would be "My Work".
24120 Some commonly used keywords begin with dollar signs.
24121 This presents a slight complication, because the dollar sign is normally used
24123 <A HREF="h_news_config">environment variable expansion</A>
24124 in the Alpine configuration.
24125 In order to specify a keyword that begins with a dollar sign you must
24126 precede the dollar sign with a second dollar sign to escape its special
24128 For example, if you want to include the keyword
24130 <CENTER><SAMP>$Label1</SAMP></CENTER>
24132 as one of your possible keywords, you must enter the text
24134 <CENTER><SAMP>$$Label1</SAMP></CENTER>
24139 There are a couple limitations.
24140 First, not all servers support keywords.
24141 Second, some servers (including the IMAP server included with Alpine)
24142 have a per folder limit on the number of keywords that may be defined.
24143 This count commonly includes every keyword you have ever used in the
24144 folder, even if it is no longer being used.
24145 In other words, you can add keywords but you cannot remove them easily.
24146 If you have changed keywords over the life of a folder and find that
24147 you have reached such a limit, one possible solution might be to copy
24148 all of the messages to a newly created folder (using Alpine) and then
24149 delete the original and rename the new folder.
24150 The reason this might work is that only the keywords currently set in
24151 any of the messages will be used in the new folder, hopefully putting you
24156 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24158 <End of help on this topic>
24161 ====== h_config_alt_addresses =====
24164 <TITLE>OPTION: <!--#echo var="VAR_alt-addresses"--></TITLE>
24167 <H1>OPTION: <!--#echo var="VAR_alt-addresses"--></H1>
24169 This option provides a place for you to list alternate email addresses
24171 Each address in the list should be the actual email address part of an
24172 address, without the full name field or the angle brackets.
24176 <CENTER><SAMP>user@example.com</SAMP></CENTER>
24179 The matching is case-insensitive, so this would match any of
24180 <SAMP>User@example.com</SAMP>, <SAMP>user@Example.Com</SAMP>, or
24181 <SAMP>USER@EXAMPLE.COM</SAMP> as well.
24184 If set, the option affects the behavior of the Reply
24185 command and the "+" symbol in the MESSAGE INDEX, which denotes that
24186 a message has been addressed specifically to you.
24189 In the default INDEX display
24190 the personal name (or email address) of
24191 the person listed in the message's "From:" header
24192 field is usually displayed except when that address is yours or one of your
24193 alternate addresses.
24194 In that case you will usually see the name of
24195 the first person specified in the
24196 message's "To:" header field
24197 with the prefix "To: " prepended.
24200 With respect to Reply, the reply-to-all option will exclude addresses
24205 <A HREF="h_config_copy_to_to_from"><!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></A>
24206 is somewhat related to this option.
24209 In addition to a list of actual addresses,
24210 you may use regular expressions (as used with egrep with the ignore case flag)
24211 to describe the addresses you want to match.
24212 Alpine will somewhat arbitrarily interpret your entry as a regular
24213 expression if it contains any of the characters
24214 *, |, +, ?, {, [, ^, $, or \.
24215 Otherwise, it will be treated literally.
24217 <a href="h_config_disable_regex"><!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
24218 may be used to turn off regular expression processing regardless of whether or not
24219 special characters appear in the entry.
24222 A description of how regular expressions work is beyond the
24223 scope of this help text, but some examples follow.
24229 <CENTER><SAMP>.*@example.com</SAMP></CENTER>
24232 in the <!--#echo var="VAR_alt-addresses"--> list would mean that any
24233 address with a domain name of <SAMP>example.com</SAMP> (such as
24234 <SAMP>fred@example.com</SAMP> or <SAMP>wilma@example.com</SAMP>) will be considered
24235 one of your alternate addresses.
24236 Strictly speaking, the dot in <SAMP>example.com</SAMP> ought to be escaped with
24237 a backslash, as in <SAMP>example\.com</SAMP>, and a dollar sign anchor ought
24238 to come at the end of the expression to prevent a match of <SAMP>example.com.org</SAMP>.
24239 Complicating things further, the dollar sign
24240 is special in the Alpine configuration (it signifies environment variable expansion)
24241 so the dollar sign should be doubled or backslash escaped for Alpine's sake.
24242 Quotes around the whole expression will not escape the dollar sign successfully.
24243 So this example should look like
24246 <CENTER><SAMP>.*@example\.com$$</SAMP></CENTER>
24253 <CENTER><SAMP>^fred[0-9]*@example.com$$</SAMP></CENTER>
24257 <SAMP>fred3@example.com</SAMP> or <SAMP>fred17@example.com</SAMP> as well
24258 as <SAMP>fred@example.com</SAMP>.
24261 You could match all addresses that look like
24262 <SAMP>fred+stuff@example.com</SAMP> for any value of <SAMP>stuff</SAMP> with the
24266 <CENTER><SAMP>^fred\+.*@example.com$$</SAMP></CENTER>
24269 Notice that you have to escape the plus sign with a backslash because plus
24270 is a special character in regular expressions.
24271 If you wanted to match plain <SAMP>fred</SAMP> as well as <SAMP>fred+stuff</SAMP>
24275 <CENTER><SAMP>^fred(()|\+.*)@example.com$$</SAMP></CENTER>
24278 would do it, but it would be easier to just add fred@example.com as a
24282 One more example, a match of all first-level subdomains, is given by
24285 <CENTER><SAMP>^fred@[[:alnum:]_-]*\.example\.com$$</SAMP></CENTER>
24289 Because the regular expression matching is based on an old library
24290 (<SAMP>hs_regex</SAMP>) the regular expressions might not work exactly as you expect,
24291 but they should be close.
24295 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24297 <End of help on this topic>
24300 ====== h_config_abook_formats =====
24303 <TITLE>OPTION: <!--#echo var="VAR_addressbook-formats"--></TITLE>
24306 <H1>OPTION: <!--#echo var="VAR_addressbook-formats"--></H1>
24308 This option specifies the format that address books are displayed in.
24309 Normally, address books are displayed with the nicknames in the first
24310 column, the fullnames in the second column, and addresses in the third
24311 column. The system figures out reasonable defaults for the widths of
24312 the columns. An address book may be given a different format by
24313 listing special tokens in the order you want them to display. The
24314 possible tokens are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT.
24315 So, for example, to get the default behavior you could list
24318 <CENTER><!--#echo var="VAR_addressbook-formats"-->=NICKNAME FULLNAME ADDRESS</CENTER>
24321 (You can also use the token DEFAULT to get the default behavior for
24322 an address book format.)
24325 The tokens are separated by spaces. "<!--#echo var="VAR_addressbook-formats"-->"
24326 is a list, so if you have more than one address book you may have a
24327 separate format for each by putting its format at the corresponding
24328 location in the "<!--#echo var="VAR_addressbook-formats"-->" list.
24332 Listed first are the personal address books, then the global address
24333 books. So, if you have two personal address books and one global
24334 address book, you may have up to three formats in the
24335 "<!--#echo var="VAR_addressbook-formats"-->" list. If
24336 "<!--#echo var="VAR_addressbook-formats"-->" doesn't have as many elements as there
24337 are address books, the last element is used repeatedly.
24341 Each of the tokens may also be optionally followed by parentheses with
24342 either a number or a percentage inside the parentheses. For example,
24343 <SAMP>FULLNAME(13)</SAMP> means to allocate 13 characters of space to
24344 the fullnames column, <SAMP>FULLNAME(20%)</SAMP> means to allocate 20%
24345 of the available space (the screen width minus the space for
24346 inter-column spaces) to the fullnames column, while plain
24347 <SAMP>FULLNAME</SAMP> means the system will attempt to figure out a
24348 reasonable number of columns.
24351 There are always 2 spaces between every column, so if you use
24352 fixed column widths (like 13) you should remember to take that into
24357 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24359 <End of help on this topic>
24362 ====== h_config_set_index_format =====
24365 <TITLE>Set Index Format</TITLE>
24368 <H1>Set Index Format</H1>
24370 This option is used to customize the content of lines in the
24371 <A HREF="h_mail_index">MESSAGE INDEX screen</A>.
24372 This action works exactly like the regular
24373 "<!--#echo var="VAR_index-format"-->" option in the Setup/Config screen,
24374 except that you can have a folder-specific value for it if you specify it here.
24375 Consult the help for
24376 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
24377 for more information.
24381 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24383 <End of help on this topic>
24386 ====== h_config_index_format =====
24389 <TITLE>OPTION: <!--#echo var="VAR_index-format"--></TITLE>
24392 <H1>OPTION: <!--#echo var="VAR_index-format"--></H1>
24394 This option is used to customize the content of lines in the
24395 <A HREF="h_mail_index">MESSAGE INDEX screen</A>. Each line is intended
24396 to convey some amount of immediately relevant information about each
24397 message in the current folder.
24400 Alpine provides a pre-defined set of informational fields with
24401 reasonable column widths automatically computed. You can, however,
24402 replace this default set by listing special tokens in the order you
24403 want them displayed.
24406 The list of available tokens is
24407 <A HREF="h_index_tokens">here</A>.
24410 Spaces are used to separate listed tokens. Additionally, you can
24411 specify how much of the screen's width the token's associated data
24412 should occupy on the index line by appending to the token a pair of
24413 parentheses enclosing either a number or percentage. For example,
24414 "SUBJECT(13)" means to allocate 13 characters of space to the subject
24415 column, and "SUBJECT(20%)" means to
24416 allocate 20% of the available space
24417 to the subjects column, while plain "SUBJECT" means the system will
24418 attempt to figure out a reasonable amount of space.
24421 There is always one space between every pair of columns, so if you use fixed
24422 column widths (like 13) you should remember to take that into account.
24423 Several of the fields are virtually fixed-width, so it doesn't make
24424 much sense to specify the width for them. The fields STATUS,
24425 FULLSTATUS, IMAPSTATUS, MSGNO, the DATE fields, SIZE,
24426 and DESCRIPSIZE all fall into that category.
24427 You <EM>may</EM> specify widths for those if you wish, but
24428 you're probably better off letting the system pick those widths. <P>
24431 The default is equivalent to:
24434 <CENTER><SAMP>STATUS MSGNO SMARTDATETIME24 FROMORTO(33%) SIZENARROW SUBJKEY(67%)</SAMP></CENTER>
24437 This means that the four fields without percentages will be allocated
24438 first, and then 33% and 67% of the <EM>remaining</EM> space will go to
24439 the from and subject fields. If one of those two fields is specified
24440 as a percentage and the other is left for the system to choose, then
24441 the percentage is taken as an absolute percentage of the screen, not
24442 of the space remaining after allocating the first four columns. It
24443 doesn't usually make sense to do it that way. If you leave off all
24444 the widths, then the subject and from fields (if both are present) are
24445 allocated space in a 2 to 1 ratio, which is almost exactly the same as
24449 What you are most likely to do with this configuration option is to
24450 specify which fields appear at all, which order they appear in, and the
24451 percentage of screen that is used for the from and subject fields if you
24452 don't like the 2 to 1 default.
24455 If you want to retain the default format that Pine 4.64 had, use
24458 <CENTER><SAMP><!--#echo var="VAR_index-format"-->=STATUS MSGNO DATE FROMORTO(33%) SIZE SUBJKEY(67%)</SAMP></CENTER>
24460 <EM>and</EM> set the feature
24461 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>.
24463 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24465 <End of help on this topic>
24468 ====== h_config_reply_intro =====
24471 <TITLE>OPTION: <!--#echo var="VAR_reply-leadin"--></TITLE>
24474 <H1>OPTION: <!--#echo var="VAR_reply-leadin"--></H1>
24476 This option is used to customize the content of the introduction line
24477 that is included when replying to a message and including the original
24478 message in the reply.
24479 The normal default (what you will get if you delete this variable) looks
24482 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
24484 where the day of the week is only included if it is available in the
24486 You can replace this default with text of your own.
24487 The text may contain tokens that are replaced with text
24488 that depends on the message you are replying to.
24489 For example, the default is equivalent to:
24491 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
24494 Since this variable includes regular text mixed with special tokens
24495 the tokens have to be surrounded by underscore characters.
24496 For example, to use the token "<SAMP>PREFDATE</SAMP>"
24497 you would need to use "<SAMP>_PREFDATE_</SAMP>",
24498 not "<SAMP>PREFDATE</SAMP>".
24500 The list of available tokens is
24501 <A HREF="h_index_tokens">here</A>.
24504 By default, the text is all on a single line and is followed by a blank line.
24505 If your "<!--#echo var="VAR_reply-leadin"-->" turns out to be longer
24506 than 80 characters when replying to a particular message, it is shortened.
24507 However, if you use the token
24509 <CENTER><SAMP>_NEWLINE_</SAMP></CENTER>
24512 anywhere in the value, no end of line or blank line is appended, and no
24513 shortening is done.
24514 The _NEWLINE_ token may be used to get rid of the blank line following
24515 the text, to add more blank lines, or to form a multi-line
24516 "<!--#echo var="VAR_reply-leadin"-->".
24517 To clarify how _NEWLINE_ works recall that the default value is:
24519 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
24522 That is equivalent to
24524 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE__NEWLINE_</SAMP></CENTER>
24527 In the former case, two newlines are added automatically because
24528 no _NEWLINE_ token appears in the value of the option (for backwards
24529 compatibility). In the latter case, the newlines are explicit.
24530 If you want to remove the blank line that follows the
24531 "<!--#echo var="VAR_reply-leadin"-->" text use a single
24532 _NEWLINE_ token like
24534 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE_</SAMP></CENTER>
24537 Because of the backwards compatibility problem, it is not possible to
24538 remove all of the ends of lines, because then there will be no _NEWLINE_ tokens
24539 and that will cause the automatic adding of two newlines!
24540 If you want, you may embed newlines in the middle of the text, as well,
24541 producing a multi-line "<!--#echo var="VAR_reply-leadin"-->".
24544 By default, no attempt is made to localize the date.
24545 If you prefer a localized form you may find that one of the tokens
24546 _PREFDATE_ or _PREFDATETIME_ is a satisfactory substitute.
24547 If you want more control one of the many other date tokens, such as _DATEISO_,
24551 For the adventurous, there is a way to conditionally include text based
24552 on whether or not a token would result in specific replacement text.
24553 For example, you could include some text based on whether or not
24554 the _NEWS_ token would result in any newsgroups if it was used.
24555 It's explained in detail
24556 <A HREF="h_reply_token_conditionals">here</A>.
24559 In the very unlikely event that you want to include a literal token
24560 in the introduction line you must precede it with a backslash character.
24563 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
24565 would produce something like
24567 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
24569 It is not possible to have a literal backslash followed by an expanded token.
24572 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24574 <End of help on this topic>
24577 ====== h_config_remote_abook_history =====
24580 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-history"--></TITLE>
24583 <H1>OPTION: <!--#echo var="VAR_remote-abook-history"--></H1>
24585 Sets how many extra copies of
24586 remote address book
24587 data will be kept in each remote address book folder.
24588 The default is three.
24589 These extra copies are simply old versions of the data. Each time a change
24590 is made a new copy of the address book data is appended to the folder. Old
24591 copies are trimmed, if possible, when Alpine exits.
24592 An old copy can be put back into use by
24593 deleting and expunging newer versions of the data from the folder.
24594 Don't delete the first message from the folder. It is a special header
24595 message for the remote address book and it must be there.
24596 This is to prevent regular folders from being used as remote address book
24597 folders and having their data destroyed.
24599 This option is also used to determine how many extra copies of remote
24600 Alpine configuration files are kept.
24603 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24605 <End of help on this topic>
24608 ====== h_config_remote_abook_validity =====
24611 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-validity"--></TITLE>
24614 <H1>OPTION: <!--#echo var="VAR_remote-abook-validity"--></H1>
24616 Sets the minimum number of minutes that a
24617 remote address book will be considered up to date.
24618 Whenever an entry contained in a remote address book is used,
24619 if more than this many minutes have
24620 passed since the last check the remote server will be queried to see if the
24621 address book has changed.
24622 If it has changed, the local copy is updated.
24623 The default value is five minutes.
24624 The special value of -1 means never check.
24625 The special value of zero means only check when the address book is first
24628 No matter what the value, the validity check is always done when the
24629 address book is about to be changed by the user.
24630 The check can be initiated manually by typing <EM>^L</EM> (Ctrl-L)
24631 while in the address book maintenance screen for the remote address book.
24634 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24636 <End of help on this topic>
24639 ====== h_config_user_input_timeo =====
24642 <TITLE>OPTION: <!--#echo var="VAR_user-input-timeout"--></TITLE>
24645 <H1>OPTION: <!--#echo var="VAR_user-input-timeout"--></H1>
24647 If this is set to an integer greater than zero, then this is the number
24648 of <EM>hours</EM> to wait for user input before Alpine times out.
24650 in the midst of composing a message or is waiting for user response to
24651 a question, then it will not timeout.
24652 However, if Alpine is sitting idle waiting for
24653 the user to tell it what to do next and the user does not give any
24654 input for this many hours, Alpine will exit.
24655 No expunging or moving of read
24656 messages will take place.
24657 It will exit similarly to the way it would exit
24658 if it received a hangup signal.
24659 This may be useful for cleaning up unused Alpine sessions that have been
24660 forgotten by their owners.
24661 The Alpine developers envision system administrators
24662 setting this to a value of several hours (24?) so that it won't surprise
24663 a user who didn't want to be disconnected.
24666 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24668 <End of help on this topic>
24671 ====== h_config_ssh_open_timeo =====
24674 <TITLE>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></TITLE>
24677 <H1>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></H1>
24679 Sets the time in seconds that Alpine will
24680 attempt to open a UNIX secure shell connection.
24681 The default is 15, the minimum non-zero value is 5,
24682 and the maximum is unlimited. If this is set to zero ssh connections
24683 will be completely disabled.
24686 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24688 <End of help on this topic>
24691 ====== h_config_rsh_open_timeo =====
24694 <TITLE>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></TITLE>
24697 <H1>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></H1>
24699 Sets the time in seconds that Alpine will
24700 attempt to open a UNIX remote shell connection.
24701 The default is 15, the minimum non-zero value is 5,
24702 and the maximum is unlimited. If this is set to zero rsh connections
24703 will be completely disabled.
24704 This might be useful if rsh connections will never work in your environment
24705 but are causing delays due to firewalls or some other reason.
24708 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24710 <End of help on this topic>
24713 ====== h_config_tcp_open_timeo =====
24716 <TITLE>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></TITLE>
24719 <H1>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></H1>
24721 Sets the time in seconds that Alpine will
24722 attempt to open a network connection. The default is 30, the minimum is 5,
24723 and the maximum is system defined (typically 75). If a connection has not
24724 completed within this many seconds Alpine will give up and consider it 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_readwarn_timeo =====
24736 <TITLE>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></TITLE>
24739 <H1>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></H1>
24741 Sets the time in seconds that Alpine will
24742 wait for a network read before warning you that things are moving slowly
24743 and possibly giving you the option to break the connection.
24744 The default is 15 seconds. The minimum is 5 seconds and the maximumn is
24747 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24750 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24752 <End of help on this topic>
24755 ====== h_config_tcp_writewarn_timeo =====
24758 <TITLE>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></TITLE>
24761 <H1>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></H1>
24763 Sets the time in seconds that Alpine will
24764 wait for a network write before warning you that things are moving slowly
24765 and possibly giving you the option to break the connection.
24766 The default is 0 which means it is unset. If set to a non-zero value, the
24767 minimum is 5 and the maximum is 1000.
24769 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24772 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24774 <End of help on this topic>
24777 ====== h_config_tcp_query_timeo =====
24780 <TITLE>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></TITLE>
24783 <H1>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></H1>
24785 When Alpine times out a network read or write it will normally just display
24786 a message saying "Still waiting".
24787 However, if enough time has elapsed since it started waiting it will offer
24788 to let you break the connection.
24789 That amount of time is set by this option, which defaults to 60 seconds,
24790 has a minimum of 5 seconds, and a maximum of 1000 seconds.
24793 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24795 <End of help on this topic>
24798 ====== h_config_incoming_folders =====
24801 <TITLE>OPTION: <!--#echo var="VAR_incoming-folders"--></TITLE>
24804 <H1>OPTION: <!--#echo var="VAR_incoming-folders"--></H1>
24806 This is a list of one or more folders other than <EM>INBOX</EM> that
24807 may receive new messages.
24808 It is related to the
24809 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
24811 This variable is normally manipulated with the Add, Delete, and Rename
24812 commands in the FOLDER LIST for the Incoming Message Folders collection.
24815 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24817 <End of help on this topic>
24820 ====== h_config_folder_spec =====
24823 <TITLE>OPTION: <!--#echo var="VAR_folder-collections"--></TITLE>
24826 <H1>OPTION: <!--#echo var="VAR_folder-collections"--></H1>
24828 This is a list of one or more collections where saved mail is stored.
24829 The first collection in this list is the default
24830 collection for <EM>Save</EM>s,
24831 including <A HREF="h_config_default_fcc"><!--#echo var="VAR_default-fcc"--></A>.
24833 This variable is normally manipulated using the Setup/collectionList screen.
24836 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24838 <End of help on this topic>
24841 ====== h_config_news_spec =====
24844 <TITLE>OPTION: <!--#echo var="VAR_news-collections"--></TITLE>
24847 <H1>OPTION: <!--#echo var="VAR_news-collections"--></H1>
24849 This is a list of collections where news folders are located.
24851 This variable is normally manipulated using the Setup/collectionList screen.
24854 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24856 <End of help on this topic>
24859 ====== h_config_address_book =====
24862 <TITLE>OPTION: <!--#echo var="VAR_address-book"--></TITLE>
24865 <H1>OPTION: <!--#echo var="VAR_address-book"--></H1>
24867 A list of personal address books.
24868 Each entry in the list is an
24869 optional nickname followed by a pathname or file name relative to the home
24871 The nickname is separated from the rest of the line with whitespace.
24872 Instead of a local pathname or file name, a remote folder name can be given.
24873 This causes the address book to
24874 be a Remote address book.
24876 Use the Setup/AddressBook screen to modify this variable.
24879 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24881 <End of help on this topic>
24884 ====== h_config_glob_addrbook =====
24887 <TITLE>OPTION: <!--#echo var="VAR_global-address-book"--></TITLE>
24890 <H1>OPTION: <!--#echo var="VAR_global-address-book"--></H1>
24892 A list of shared address books. Each entry in the list is an
24893 optional nickname followed by a pathname or file name relative to the home
24895 A SPACE character separates the nickname from the rest of the line.
24896 Instead of a local pathname or file name, a remote folder name can be given.
24897 This causes the address book to
24898 be a Remote address book.
24899 Global address books are
24900 defined to be ReadOnly.
24902 Use the Setup/AddressBook screen to modify this variable.
24905 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24907 <End of help on this topic>
24910 ====== h_config_last_vers =====
24913 <TITLE>OPTION: <!--#echo var="VAR_last-version-used"--></TITLE>
24916 <H1>OPTION: <!--#echo var="VAR_last-version-used"--></H1>
24918 This is set automatically by Alpine.
24919 It is used to keep track of the last version of Alpine that
24920 was run by the user.
24921 Whenever the version number increases, a new version message is printed out.
24922 This may not be set in the system-wide configuration files.
24925 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24927 <End of help on this topic>
24930 ====== h_config_printer =====
24933 <TITLE>OPTION: Printer</TITLE>
24936 <H1>OPTION: Printer</H1>
24938 Your default printer selection.
24940 Use the Setup/Printer screen to modify this variable.
24943 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24945 <End of help on this topic>
24948 ====== h_config_print_cat =====
24951 <TITLE>OPTION: <!--#echo var="VAR_personal-print-category"--></TITLE>
24954 <H1>OPTION: <!--#echo var="VAR_personal-print-category"--></H1>
24956 This is an internal Alpine variable.
24957 It will be equal to 1, 2, or 3 depending on whether the default printer is
24958 attached, standard, or a personal print command.
24960 Use the Setup/Printer screen to modify this variable.
24963 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24965 <End of help on this topic>
24968 ====== h_config_print_command =====
24971 <TITLE>OPTION: <!--#echo var="VAR_personal-print-command"--></TITLE>
24974 <H1>OPTION: <!--#echo var="VAR_personal-print-command"--></H1>
24976 List of personal print commands.
24978 Use the Setup/Printer screen to modify this variable.
24981 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24983 <End of help on this topic>
24986 ====== h_config_pat_old =====
24989 <TITLE>OPTION: Patterns</TITLE>
24992 <H1>OPTION: Patterns</H1>
24994 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by the
24995 options Patterns-Roles, Patterns-Filters, Patterns-Scores, Patterns-Indexcolors,
24996 and Patterns-Other.
24997 Patterns-Scores and Patterns-Filters have been replaced since then by
24998 Patterns-Scores2 and Patterns-Filters2.
25000 Use the Setup/Rules screens to modify these variable.
25003 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25005 <End of help on this topic>
25008 ====== h_config_pat_roles =====
25011 <TITLE>OPTION: <!--#echo var="VAR_patterns-roles"--></TITLE>
25014 <H1>OPTION: <!--#echo var="VAR_patterns-roles"--></H1>
25016 List of rules used for roles.
25017 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by this and
25020 Use the Setup/Rules/Roles screen to modify this variable.
25023 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25025 <End of help on this topic>
25028 ====== h_config_pat_filts =====
25031 <TITLE>OPTION: <!--#echo var="VAR_patterns-filters2"--></TITLE>
25034 <H1>OPTION: <!--#echo var="VAR_patterns-filters2"--></H1>
25036 List of rules used for filters.
25038 Use the Setup/Rules/Filters screen to modify this variable.
25041 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25043 <End of help on this topic>
25046 ====== h_config_pat_scores =====
25049 <TITLE>OPTION: <!--#echo var="VAR_patterns-scores2"--></TITLE>
25052 <H1>OPTION: <!--#echo var="VAR_patterns-scores2"--></H1>
25054 List of rules used for scoring.
25056 Use the Setup/Rules/SetScores screen to modify this variable.
25059 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25061 <End of help on this topic>
25064 ====== h_config_pat_other =====
25067 <TITLE>OPTION: <!--#echo var="VAR_patterns-other"--></TITLE>
25070 <H1>OPTION: <!--#echo var="VAR_patterns-other"--></H1>
25072 List of rules used for miscellaneous configuration.
25074 Use the Setup/Rules/Other screen to modify this variable.
25077 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25079 <End of help on this topic>
25082 ====== h_config_pat_incols =====
25085 <TITLE>OPTION: patterns-indexcolors</TITLE>
25088 <H1>OPTION: patterns-indexcolors</H1>
25090 List of rules used for coloring lines in the index.
25092 Use the Setup/Rules/Indexcolor screen to modify this variable.
25095 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25097 <End of help on this topic>
25100 ====== h_config_pat_srch =====
25103 <TITLE>OPTION: patterns-search</TITLE>
25106 <H1>OPTION: patterns-search</H1>
25108 List of rules used only for searching with the Select command in the MESSAGE INDEX.
25110 Use the Setup/Rules/searCh screen to modify this variable.
25113 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25115 <End of help on this topic>
25118 ====== h_config_font_name =====
25121 <TITLE>OPTION: Font Name</TITLE>
25124 <H1>OPTION: Font Name</H1>
25128 Name of normal font.
25130 Use the pulldown Config menu to modify this variable.
25133 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25135 <End of help on this topic>
25138 ====== h_config_font_size =====
25141 <TITLE>OPTION: Font Size</TITLE>
25144 <H1>OPTION: Font Size</H1>
25148 Size of normal font.
25150 Use the pulldown Config menu to modify this variable.
25153 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25155 <End of help on this topic>
25158 ====== h_config_font_style =====
25161 <TITLE>OPTION: Font Style</TITLE>
25164 <H1>OPTION: Font Style</H1>
25168 Style of normal font.
25170 Use the pulldown Config menu to modify this variable.
25173 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25175 <End of help on this topic>
25178 ====== h_config_font_char_set =====
25181 <TITLE>OPTION: Font Character Set</TITLE>
25184 <H1>OPTION: Font Character Set</H1>
25188 Character set of normal font.
25190 Use the pulldown Config menu to modify this variable.
25193 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25195 <End of help on this topic>
25198 ====== h_config_print_font_name =====
25201 <TITLE>OPTION: Print-Font-Name</TITLE>
25204 <H1>OPTION: Print-Font-Name</H1>
25208 Name of printer font.
25210 Use the pulldown Config menu to modify this variable.
25213 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25215 <End of help on this topic>
25218 ====== h_config_print_font_size =====
25221 <TITLE>OPTION: Print-Font-Size</TITLE>
25224 <H1>OPTION: Print-Font-Size</H1>
25228 Size of printer font.
25230 Use the pulldown Config menu to modify this variable.
25233 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25235 <End of help on this topic>
25238 ====== h_config_print_font_style =====
25241 <TITLE>OPTION: Print-Font-Style</TITLE>
25244 <H1>OPTION: Print-Font-Style</H1>
25248 Style of printer font.
25250 Use the pulldown Config menu to modify this variable.
25253 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25255 <End of help on this topic>
25258 ====== h_config_print_font_char_set =====
25261 <TITLE>OPTION: Print-Font-Char-Set</TITLE>
25264 <H1>OPTION: Print-Font-Char-Set</H1>
25268 Character set of printer font.
25270 Use the pulldown Config menu to modify this variable.
25273 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25275 <End of help on this topic>
25278 ====== h_config_window_position =====
25281 <TITLE>OPTION: Window-Position</TITLE>
25284 <H1>OPTION: Window-Position</H1>
25288 Position on the screen of the Alpine window.
25290 Alpine normally maintains this variable itself, and it is set automatically.
25291 This variable is provided to those who wish to use the same window position
25292 across different machines from the same configuration.
25293 <A HREF="h_config_winpos_in_config"><!--#echo var="FEAT_store-window-position-in-config"--></A>
25294 must also be set for this setting to be used.
25296 The format for this variable is of the form: <CODE>CxR+X+Y</CODE>, where
25297 C is the number of columns, R is the number of rows, and X and Y specify the
25298 top left corner of the window.
25301 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25303 <End of help on this topic>
25306 ====== h_config_cursor_style =====
25309 <TITLE>OPTION: Cursor Style</TITLE>
25312 <H1>OPTION: Cursor Style</H1>
25318 Use the pulldown Config menu to modify this variable.
25321 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25323 <End of help on this topic>
25326 ====== h_config_ldap_servers =====
25329 <TITLE>OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
25332 <H1>OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
25334 List of LDAP servers and associated data.
25336 Use the Setup/Directory screen to modify this variable.
25339 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25341 <End of help on this topic>
25344 ====== h_config_sendmail_path =====
25347 <TITLE>OPTION: <!--#echo var="VAR_sendmail-path"--></TITLE>
25350 <H1>OPTION: <!--#echo var="VAR_sendmail-path"--></H1>
25352 This names the path to an
25353 alternative program, and any necessary arguments, to be used in posting
25354 mail messages. See the Technical notes for more information.
25357 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25359 <End of help on this topic>
25362 ====== h_config_oper_dir =====
25365 <TITLE>OPTION: <!--#echo var="VAR_operating-dir"--></TITLE>
25368 <H1>OPTION: <!--#echo var="VAR_operating-dir"--></H1>
25370 This names the root of the
25371 tree to which you are restricted when reading and writing folders and
25372 files. It is usually used in the system-wide,
25373 <EM>fixed</EM> configuration file.
25376 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25378 <End of help on this topic>
25381 ====== h_config_rshpath =====
25384 <TITLE>OPTION: <!--#echo var="VAR_rsh-path"--></TITLE>
25387 <H1>OPTION: <!--#echo var="VAR_rsh-path"--></H1>
25389 Sets the name of the command used to open a UNIX remote shell
25390 connection. The default is typically <CODE>/usr/ucb/rsh</CODE>.
25393 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25395 <End of help on this topic>
25398 ====== h_config_rshcmd =====
25401 <TITLE>OPTION: <!--#echo var="VAR_rsh-command"--></TITLE>
25404 <H1>OPTION: <!--#echo var="VAR_rsh-command"--></H1>
25406 Sets the format of the command used to
25407 open a UNIX remote shell connection. The default is
25408 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
25409 provided command. The first is for the command's pathname, the second is
25410 for the host to connnect to, the third is for the user to connect as, and
25411 the fourth is for the connection method (typically <CODE>imap</CODE>).
25414 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25416 <End of help on this topic>
25419 ====== h_config_sshpath =====
25422 <TITLE>OPTION: <!--#echo var="VAR_ssh-path"--></TITLE>
25425 <H1>OPTION: <!--#echo var="VAR_ssh-path"--></H1>
25427 Sets the name of the command used to open a UNIX secure shell
25428 connection. The default is typically <CODE>/usr/bin/ssh</CODE>.
25431 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25433 <End of help on this topic>
25436 ====== h_config_sshcmd =====
25439 <TITLE>OPTION: <!--#echo var="VAR_ssh-command"--></TITLE>
25442 <H1>OPTION: <!--#echo var="VAR_ssh-command"--></H1>
25444 Sets the format of the command used to
25445 open a UNIX secure shell connection. The default is
25446 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
25447 provided command. The first is for the command's pathname, the second is
25448 for the host to connnect to, the third is for the user to connect as, and
25449 the fourth is for the connection method (typically <CODE>imap</CODE>).
25452 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25454 <End of help on this topic>
25457 ====== h_config_new_ver_quell =====
25460 <TITLE>OPTION: <!--#echo var="VAR_new-version-threshold"--></TITLE>
25463 <H1>OPTION: <!--#echo var="VAR_new-version-threshold"--></H1>
25465 When a new version of Alpine is run for the first time it offers a
25466 special explanatory screen to the user upon startup. This option
25467 helps control when and if that special screen appears for users that
25468 have previously run Alpine. It takes as its value an Alpine version
25469 number. Alpine versions less than the specified value will supress this
25470 special screen while versions equal to or greater than that specified
25471 will behave normally.
25474 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25476 <End of help on this topic>
25479 ====== h_config_disable_drivers =====
25482 <TITLE>OPTION: <!--#echo var="VAR_disable-these-drivers"--></TITLE>
25485 <H1>OPTION: <!--#echo var="VAR_disable-these-drivers"--></H1>
25487 This variable is a list of mail drivers that will be disabled.
25488 The candidates for disabling are listed below.
25489 There may be more in the future if you compile Alpine with
25490 a newer version of the c-client library.
25507 The <EM>mbox</EM> driver enables the following behavior: if there is a
25508 file called <CODE>mbox</CODE>
25509 in your home directory, and if that file is either empty or in Unix mailbox
25510 format, then every time you open <EM>INBOX</EM> the <EM>mbox</EM> driver
25511 will automatically transfer mail from the system mail spool directory into the
25512 <CODE>mbox</CODE> file and
25513 delete it from the spool directory. If you disable the <EM>mbox</EM> driver,
25514 this will not happen.
25517 It is not recommended to disable the driver that supports the system default
25518 mailbox format. On most non-SCO systems, that driver is the
25519 <EM>unix</EM> driver.
25520 On most SCO systems, it is the <EM>mmdf</EM> driver.
25521 The system default driver may be
25522 configured to something else on your system; check with your system manager
25523 for additional information.
25526 It is most likely not very useful for you to disable any of the drivers other
25527 than possibly <EM>mbox</EM>.
25528 You could disable some of the others if you know for
25529 certain that you don't need them but the performance gain in doing so
25533 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25535 <End of help on this topic>
25538 ====== h_config_disable_auths =====
25541 <TITLE>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></TITLE>
25544 <H1>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></H1>
25546 This variable is a list of SASL (Simple Authentication and Security
25547 Layer) authenticators that will be disabled.
25548 SASL is a mechanism for
25549 authenticating to IMAP, POP3, SMTP, and other network servers.
25552 Alpine matches its list of supported authenticators with the server to
25553 determine the most secure authenticator that is supported by both.
25554 If no matching authenticators are found, Alpine will revert to plaintext
25555 login (or, in the case of SMTP, will be unable to authenticate at all).
25557 The candidates for disabling can be found <A HREF="X-Alpine-Config:">here</A>.
25560 Normally, you will not disable any authenticators.
25561 There are two exceptions:
25564 <LI> You use a broken server that advertises an authenticator,
25565 but does not actually implement it.
25566 <LI> You have a Kerberos-capable version of Alpine and the server is
25567 also Kerberos-capable, but you can not obtain Kerberos
25568 credentials on the server machine, thus you desire to disable
25569 GSSAPI (which in turn disables Alpine's Kerberos support).
25572 It is never necessary to disable authenticators, since Alpine will try
25573 other authenticators before giving up.
25574 However, disabling the relevant authenticator avoids annoying error messages.
25577 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25579 <End of help on this topic>
25582 ====== h_config_abook_metafile =====
25585 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></TITLE>
25588 <H1>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></H1>
25590 This is usually set by Alpine and is the name of a file
25591 that contains data about
25592 remote address books and remote configuration files.
25595 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25597 <End of help on this topic>
25600 ====== h_config_composer_wrap_column =====
25603 <TITLE>OPTION: <!--#echo var="VAR_composer-wrap-column"--></TITLE>
25606 <H1>OPTION: <!--#echo var="VAR_composer-wrap-column"--></H1>
25609 This option specifies an aspect of Alpine's Composer. This gives the
25610 maximum width that auto-wrapped lines will have. It's also the maximum
25611 width of lines justified using the <A HREF="h_compose_justify">^J
25612 Justify</A> command. The normal default
25613 is "74". The largest allowed setting is normally "80"
25615 prevent very long lines from being sent in outgoing mail. When the mail
25616 is actually sent, trailing spaces will be stripped off of each line.
25620 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25622 <End of help on this topic>
25625 ====== h_config_deadlets =====
25628 <TITLE>OPTION: <!--#echo var="VAR_dead-letter-files"--></TITLE>
25631 <H1>OPTION: <!--#echo var="VAR_dead-letter-files"--></H1>
25634 This option affects Alpine's behavior when you cancel a message being
25635 composed. Alpine's usual behavior is to write the canceled message to
25637 <!--chtml if pinemode="os_windows"-->
25638 "DEADLETR",
25640 "dead.letter" in your home directory,
25642 overwriting any previous message.
25644 If you set this option to a value higher than one, then that many copies
25645 of dead letter files will be saved.
25646 For example, if you set this option to "3" then you may have
25648 <!--chtml if pinemode="os_windows"-->
25649 "DEADLETR",
25650 "DEADLETR2", and
25651 "DEADLETR3".
25653 "dead.letter",
25654 "dead.letter2", and
25655 "dead.letter3" in your home directory.
25657 In this example, the most recently cancelled message will be in
25658 <!--chtml if pinemode="os_windows"-->
25659 "DEADLETR",
25661 "dead.letter",
25663 and the third most recently cancelled message will be in
25664 <!--chtml if pinemode="os_windows"-->
25665 "DEADLETR3".
25667 "dead.letter3".
25669 The fourth most recently cancelled message will no longer be saved.
25672 If you set this option to zero, then NO record of canceled messages is
25676 <A HREF="h_config_quell_dead_letter"><!--#echo var="FEAT_quell-dead-letter-on-cancel"--></A>
25677 is set, that overrides whatever you set for this option.
25678 If this option had existed at the time, then the Quell feature would not
25679 have been added, but it is still there for backwards compatibility.
25680 So, in order for this option to have the desired effect, make sure the
25681 Quell feature is turned off.
25685 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25687 <End of help on this topic>
25690 ====== h_config_maxremstream =====
25693 <TITLE>OPTION: <!--#echo var="VAR_max-remote-connections"--></TITLE>
25696 <H1>OPTION: <!--#echo var="VAR_max-remote-connections"--></H1>
25698 This option affects low-level behavior of Alpine.
25699 The default value for this option is <EM>3</EM>.
25700 If your INBOX is accessed using the IMAP protocol
25701 from an IMAP server, that connection is kept open throughout the
25702 duration of your Alpine session, independent of the value of this option.
25703 The same is true of any
25704 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
25706 This option controls Alpine's behavior when connecting to remote IMAP folders
25707 other than your INBOX or your <!--#echo var="VAR_stay-open-folders"-->.
25708 It specifies the maximum number of remote IMAP connections (other than
25709 those mentioned above) that Alpine will use for accessing the rest of your
25711 If you set this option to zero, you will turn off most remote connection
25713 It's difficult to understand exactly what this option does, and it is usually
25714 fine to leave it set to its default value.
25715 It is probably more likely that you will be interested in setting the
25716 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A> option
25717 instead of changing the value of this option.
25718 A slightly longer explanation of what is going on with this option
25719 is given in the next paragraphs.
25722 There are some time costs involved in opening and closing remote IMAP
25723 folders, the main costs being the time you have to wait for the connection
25724 to the server and the time for the folder to open.
25725 Opening a folder may involve not only the time the server takes to do its
25726 processing but time that Alpine uses to do filtering.
25727 These times can vary widely.
25728 They depend on how loaded the server is, how large
25729 the folder being opened is, and how you set up filtering, among other things.
25730 Once Alpine has opened a connection to a particular folder, it will attempt
25731 to keep that connection open in case you use it again.
25732 In order to do this,
25733 Alpine will attempt to use the <!--#echo var="VAR_max-remote-connections"--> (the value of
25734 this option) IMAP connections you have alloted for this purpose.
25736 For example, suppose the value of this option is set to "2".
25737 If your INBOX is accessed on a remote server using the IMAP protocol, that
25738 doesn't count as one of the remote connections but it is always kept open.
25739 If you then open another IMAP folder, that would be your first
25740 remote connection counted as one of the <!--#echo var="VAR_max-remote-connections"--> connections.
25741 If you open a third folder the second will be left open, in case you
25743 You won't be able to tell it has been left open.
25744 It will appear to be closed when you leave the folder but the connection
25745 will remain in the background.
25746 Now suppose you go back to the second folder (the first folder after the
25748 A connection to that folder is still open so you won't have to wait
25749 for the startup time to open it.
25750 Meanwhile, the connection to the third folder will be left behind.
25751 Now, if you open a fourth folder, you will bump into the
25752 <!--#echo var="VAR_max-remote-connections"--> limit, because this will be the third folder other
25753 than INBOX and you have the option set to "2".
25754 The connection that is being used for
25755 the third folder will be re-used for this new fourth folder.
25756 If you go back to the third folder after this, it is no longer already
25757 connected when you get there.
25758 You'll still save some time since Alpine will re-use the connection to the
25759 fourth folder and you have already logged in on that connection,
25760 but the folder will have to be re-opened from scratch.
25762 If a folder is large and the startup cost is dominated by the time it takes
25763 to open that folder or to run filters on it, then it will pay to make the
25764 value of this option large enough to keep it open.
25765 On the other hand, if you only revisit a handful of folders or if
25766 the folders are small, then it might
25767 make more sense to keep this number small so that the reconnect
25768 time (the time to start up a new connection and authenticate)
25769 is eliminated instead.
25771 You may also need to consider the impact on the server.
25772 On the surface, a larger number here may cause a larger impact on the
25773 server, since you will have more connections open to the server.
25774 On the other hand, not only will <EM>you</EM> be avoiding the startup costs
25775 associated with reopening a folder, but the <EM>server</EM> will be
25776 avoiding those costs as well.
25778 When twenty five minutes pass without any active use of an IMAP connection
25779 being saved for possible re-use, that connection will be shut down,
25783 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25785 <End of help on this topic>
25788 ====== h_config_permlocked =====
25791 <TITLE>OPTION: <!--#echo var="VAR_stay-open-folders"--></TITLE>
25794 <H1>OPTION: <!--#echo var="VAR_stay-open-folders"--></H1>
25796 This option affects low-level behavior of Alpine.
25797 There is no default value for this option.
25798 It is related to the options
25799 <A HREF="h_config_preopen_stayopens">"<!--#echo var="FEAT_preopen-stayopen-folders"-->"</A>,
25800 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>,
25801 and <A HREF="h_config_expunge_stayopens">"<!--#echo var="FEAT_offer-expunge-of-stayopen-folders"-->"</A>.
25804 Note: changes made to this list take effect the next time you open a
25805 folder in the list.
25808 This is a list of folders that will be permanently kept open once they
25810 The names in this list may be either the nickname of an Incoming folder
25811 or the full technical specification of a folder.
25812 The folders in this list need not be remote IMAP folders, they could usefully
25813 be local folders, as well.
25814 If a folder in the list is a newsgroup or is not accessed either locally
25815 or via IMAP, then the entry will be ignored.
25816 For example, folders accessed via NNTP or POP3 will not be kept open, since
25817 the way that new mail is found with those protocols involves closing and
25818 reopening the connection.
25820 Once a Stay Open folder has been opened, new-mail checking will continue
25821 to happen on that folder for the rest of the Alpine session.
25822 Your INBOX is always implicitly included in this Stay-Open list and doesn't
25823 need to be added explicitly.
25825 Another difference that you may notice between a Stay Open folder and a
25826 non-Stay Open folder is which message is selected as the current message
25827 when you enter the folder index.
25828 Normally, the starting position for an incoming folder (which most Stay Open
25829 folders will likely be) is controlled by the
25830 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
25831 However, if a folder is a Stay Open folder, when you re-enter the folder
25832 after the first time the current message will be the same as it was when
25833 you left the folder.
25834 An exception is made if you use the TAB command to get to the folder.
25835 In that case, the message number will be incremented by one from what it
25836 was when you left the folder.
25838 The above special behavior is thought to be useful.
25839 However, it is special and different from what you might at first expect.
25841 <A HREF="h_config_use_reg_start_for_stayopen"><!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></A>
25842 may be used to turn off this special treatment.
25844 If the message that was current when you left the folder no longer exists,
25845 then the regular startup rule will be used instead.
25849 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25851 <End of help on this topic>
25854 ====== h_config_viewer_overlap =====
25857 <title>OPTION: <!--#echo var="VAR_viewer-overlap"--></title>
25860 <h1>OPTION: <!--#echo var="VAR_viewer-overlap"--></h1>
25862 This option specifies an aspect of Alpine's Message Viewing screen. When
25863 the space bar is used to page forward in a message, the number of lines
25864 specified by the "<!--#echo var="VAR_viewer-overlap"-->" variable will be repeated from the
25865 bottom of the screen. That is, if this was set to two lines, then the
25866 bottom two lines of the screen would be repeated on the top of the next
25867 screen. The normal default value is "2".<p>
25869 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25871 <End of help on this topic>
25874 ====== h_config_scroll_margin =====
25877 <TITLE>OPTION: <!--#echo var="VAR_scroll-margin"--></TITLE>
25880 <H1>OPTION: <!--#echo var="VAR_scroll-margin"--></H1>
25882 This option controls when Alpine's line-by-line scrolling occurs.
25883 Typically, when a selected item is at the top or bottom screen edge
25884 and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are struck, the
25885 displayed items are scrolled down or up by a single line.
25888 This option allows you to tell Alpine the number of lines from the top and
25889 bottom screen edge that line-by-line paging should occcur. For example,
25890 setting this value to one (1) will cause Alpine to scroll the display
25891 vertically when you move to select an item on the display's top or
25895 By default, this variable is zero, indicating that scrolling happens
25896 when you move up or down to select an item immediately off the display's
25897 top or bottom edge.
25901 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25903 <End of help on this topic>
25906 ====== h_config_wordseps =====
25909 <TITLE>OPTION: <!--#echo var="VAR_composer-word-separators"--></TITLE>
25912 <H1>OPTION: <!--#echo var="VAR_composer-word-separators"--></H1>
25914 This option affects how a "word" is defined in the composer.
25915 The definition of a word is used when using the Forward Word and Backward
25916 Word commands in the composer, as well as when using the spell checker.
25917 Whitespace is always considered a word separator.
25918 Punctuation (like question marks, periods, commas, and so on) is always
25919 a word separator if it comes at the end of a word.
25920 By default, a punctuation character that is in the middle of a word does
25921 not break up that word as long as the character before and the character
25922 after it are both alphanumeric.
25923 If you add a character to this option it will be considered a
25924 word separator even when it occurs in the middle of an alphanumeric word.
25925 For example, if you want to skip through each part of an address instead
25926 of skipping the whole address at once you might want to include "@"
25927 and "." in this list.
25928 If you want the word-skipper to stop on each part of a UNIX filename you
25929 could add "/" to the list.
25930 The equal sign and dash are other possibilities you might find helpful.
25933 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25935 <End of help on this topic>
25938 ====== h_config_reply_indent_string =====
25941 <TITLE>OPTION: <!--#echo var="VAR_reply-indent-string"--></TITLE>
25944 <H1>OPTION: <!--#echo var="VAR_reply-indent-string"--></H1>
25946 This option specifies an aspect of Alpine's Reply command.
25947 When a message is replied to and the text of the message is included, the
25948 included text usually has the string "> " prepended
25949 to each line indicating it is quoted text.
25950 (In case you haven't seen this before, "string" is a technical term
25951 that means chunk of text.)
25954 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
25955 in 1999 and its wide-spread adoption since then, you will usually be better off if you
25956 use one of the standard values,
25957 "> " or ">", for this option.
25960 This option specifies a different value for that string.
25961 If you wish to use a string that begins or ends with a space,
25962 enclose the string in double quotes.
25965 Besides simple text, the prepended string can be based
25966 on the message being replied to.
25967 The following tokens are substituted for the message's corresponding value:
25971 <DD>This token gets replaced with the message sender's "username".
25972 If the name is longer than six characters, only the first six characters are
25977 <DD>This token gets replaced with the nickname of the message sender's
25978 address as found in your addressbook.
25979 If no addressbook entry is found,
25980 Alpine replaces the characters "_NICK_" with nothing.
25981 If the nickname is longer than six characters, only the first six characters are
25986 <DD>This token gets replaced with the initials of the sender of the message.
25992 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
25993 feature is enabled, you are given the opportunity to edit the string, whether
25994 it is the default or one automatically generated using the above tokens.
25996 If you change your <!--#echo var="VAR_reply-indent-string"-->
25997 so that it is not equal to the default value of "> ", then
25998 quoted text will not be flowed
25999 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
26001 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
26002 set to the default value.
26005 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26007 <End of help on this topic>
26010 ====== h_config_quote_replace_string =====
26013 <TITLE>OPTION: <!--#echo var="VAR_quote-replace-string"--></TITLE>
26016 <H1>OPTION: <!--#echo var="VAR_quote-replace-string"--></H1>
26018 This option specifies what string to use as a quote when <b>viewing</b> a
26019 message. The standard way of quoting messages when replying is the string
26020 "> " (quote space).
26021 With this variable set, viewing a message will
26022 replace occurrences of
26023 "> " and ">" with the replacement string.
26024 This setting works best when
26025 <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
26026 or the equivalent setting in your correspondents' mail programs
26027 is set to the default
26028 "> ", but it will also work fine with the
26029 <!--#echo var="VAR_reply-indent-string"--> set to ">".
26031 By default, this setting will only work on messages that are flowed, which is
26032 the default way of sending messages for many mail clients including
26033 Alpine. Enable the feature
26034 <A HREF="h_config_quote_replace_noflow"><!--#echo var="FEAT_quote-replace-nonflowed"--></A>
26035 to also have quote-replacement performed on non-flowed messages.
26038 Setting this option will replace ">" and
26039 "> " with the new setting. This string may include trailing
26040 spaces. To preserve those spaces enclose the full string in double quotes.
26042 No padding to separate the text of the message from the quote string is
26043 added. This means that if you do not add trailing spaces to the value of
26044 this variable, text will be displayed right next to the quote string,
26045 which may be undesirable. This can be avoided by adding a new string
26046 separated by a space from your selection of quote string replacement. This
26047 last string will be used for padding. For example, setting this variable to
26048 <br>">" " " has the effect of setting
26049 ">" as the <!--#echo var="VAR_quote-replace-string"-->, with the text padded by
26050 a space from the last quote string to make it more readable.
26052 One possible setting for this variable could be
26053 " " (four spaces wrapped in quotes), which
26054 would have the effect of indenting each level of quoting four spaces and
26055 removing the ">"'s. Different levels of quoting could be made
26056 more discernible by setting colors for quoted text.
26058 Replying to or forwarding the viewed message will preserve the original
26059 formatting of the message, so quote-replacement will not be performed on
26060 messages that are being composed.
26063 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26065 <End of help on this topic>
26068 ====== h_config_empty_hdr_msg =====
26071 <TITLE>OPTION: <!--#echo var="VAR_empty-header-message"--></TITLE>
26074 <H1>OPTION: <!--#echo var="VAR_empty-header-message"--></H1>
26076 When sending, if both the To and Cc fields are empty and you
26077 are sending the message to a Bcc,
26078 Alpine will put a special address in the To line. The default value is:
26081 <CENTER><SAMP>undisclosed-recipients: ;</SAMP></CENTER>
26084 The reason for this is to avoid embarrassment caused by some Internet
26085 mail transfer software that interprets a "missing"
26086 <SAMP>To:</SAMP> header as an error and replaces it with an
26087 <SAMP>Apparently-to:</SAMP> header that may contain the addresses you
26088 entered on the <SAMP>Bcc:</SAMP> line, defeating the purpose of the
26089 Bcc. You may change the part of this message that comes before the
26090 ": ;" by setting the "<!--#echo var="VAR_empty-header-message"-->"
26091 variable to something else.
26094 The normal default is "undisclosed-recipients".
26098 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26100 <End of help on this topic>
26103 ====== h_config_status_msg_delay =====
26106 <TITLE>OPTION: <!--#echo var="VAR_status-message-delay"--></TITLE>
26109 <H1>OPTION: <!--#echo var="VAR_status-message-delay"--></H1>
26111 This option has evolved over time, causing the possible values to be
26113 Read carefully before you set this option.
26114 First we explain what the option does, then there is a longer discussion
26117 If this is set to zero, the default value, it has <EM>no</EM> effect.
26118 Positive and negative values serve two similar, but different purposes.
26120 If it is set to a positive number, it causes the cursor to move to the
26121 status line whenever a status message is printed and pause there for this
26123 It will probably only be useful if the
26124 <A HREF="h_config_show_cursor">"<!--#echo var="FEAT_show-cursor"-->"</A> feature is
26126 Setting this option to a positive number can only be used to
26127 <EM>increase</EM> the status message delay.
26128 This may be useful for Braille displays, or other non-traditional displays.
26130 If it is set to a negative number the interpretation is a bit complicated.
26131 Negative numbers are used to <EM>decrease</EM> the amount of delay Alpine uses to
26132 allow you to read important status messages.
26133 Of course, this may cause you to miss some important messages.
26134 If you see a message flash by but miss what it says you can use the
26135 Journal command from the MAIN MENU to read it.
26136 If you set this option to a negative value, the delay will be
26137 no more than one second less than the absolute value
26138 of the value you set.
26139 So if you set it to -1, the delay will be no more than zero seconds, no
26141 If you set it to -2, the delay will be no more than 1 second.
26142 And so on, -3 is 2 seconds, -4 is 3 seconds, ...
26143 If the delay that Alpine would have used by default is less than this delay,
26144 then the smaller delay set by Alpine will be used.
26145 Setting this option to a negative value can only reduce the amount of
26146 delay, never increase it.
26148 Here is a more detailed explanation.
26149 Status messages are the messages that show up spontaneously in the
26150 status message line, usually the third line from the bottom of the screen.
26151 By default, Alpine assigns each status message it produces a minimum
26153 Some status messages have a minimum display time of zero.
26154 You can see an example of such a message by paging up in this help text
26155 until you reach the top of the screen.
26156 If you try to page past the top you will see the message
26158 <CENTER><SAMP>[Already at start of help text]</SAMP></CENTER>
26160 in the status line.
26161 If there is another more important use of the status message line this message
26162 might be replaced quickly, or it even might not be shown at all.
26163 However, if there is no reason to get rid of the message, it might stay
26164 there for several seconds while you read the help.
26165 An example where it is replaced immediately happens when you page up in
26166 the help text past the top of the screen, but then type the "WhereIs"
26167 command right after paging up.
26168 The message will disappear immediately without causing a delay (unless you
26169 have set this option to a positive value) to allow you to type input for
26170 the "WhereIs" command.
26171 Since it isn't a very important message, Alpine has set its minimum display
26172 time to zero seconds.
26174 Other messages have minimum display times of three or more seconds.
26175 These are usually error messages that Alpine thinks you ought to see.
26176 For example, it might be a message about a failed Save or a failed folder open.
26177 It is often the case that this minimum display time won't delay you in
26178 any way because the status message line is not needed for another reason.
26179 However, there are times when Alpine has to delay what it is doing in
26180 order to display a status message for the minimum display time.
26181 This happens when a message is being displayed and Alpine wants to ask
26182 for input from the keyboard.
26183 For example, when you Save a message you use the status message line.
26184 You get a prompt there asking for the name of the folder to save to.
26185 If there is a status message being displayed that has not
26186 yet displayed for its minimum
26187 time Alpine will display that status message surrounded with the characters
26188 > and < to show you that it is delaying.
26189 That might happen, for example, if you tried to save to a folder that
26190 caused an error, then followed that immediately with another Save command.
26191 You might find yourself waiting for a status message like
26193 <CENTER><SAMP>[>Can't get write access to mailbox, access is readonly<]</SAMP></CENTER>
26195 to finish displaying for three seconds.
26196 If that is something you find happening to you frequently, you may use
26197 negative values of this option to decrease or eliminate that delay, at
26198 the risk of missing the message.
26201 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26203 <End of help on this topic>
26206 ====== h_config_active_msg_interval =====
26209 <TITLE>OPTION: <!--#echo var="VAR_busy-cue-rate"--></TITLE>
26212 <H1>OPTION: <!--#echo var="VAR_busy-cue-rate"--></H1>
26214 When Alpine is delayed for some reason it usually shows that
26215 something is happening with a small animated display in the status
26216 message line near the bottom of the screen.
26217 This option sets how frequently the characters (for example, a spinning bar)
26218 in the active status message lines are updated.
26219 At most, it can be set to be udpated 20 times per second.
26222 Setting this value to zero will prevent display of the animations
26226 The option <A HREF="h_config_use_boring_spinner"><!--#echo var="FEAT_busy-cue-spinner-only"--></A>
26227 can be used to remove the randomness from this animated display.
26231 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26233 <End of help on this topic>
26236 ====== h_config_mailchecknoncurr =====
26239 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></TITLE>
26242 <H1>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></H1>
26244 This option is closely related to the
26245 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26246 option, as well as the
26247 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A> and
26248 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> options.
26249 If the "<!--#echo var="VAR_mail-check-interval"-->" option is set to zero, then automatic
26250 new-mail checking is disabled and this option will have no effect.
26252 Normally this option is set to zero, which means that the value used will be
26253 the same as the value for the "<!--#echo var="VAR_mail-check-interval"-->".
26254 If you set this option to a value different from zero
26255 (usually larger than the value for "<!--#echo var="VAR_mail-check-interval"-->")
26256 then that is the check interval that will be used
26257 for folders that are not the currently open folder or the INBOX.
26258 You may not even have any folders that are noncurrent and not the INBOX.
26259 If you do, it is likely that they are due to
26260 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
26261 you have configured.
26262 This option also affects the rate of mail checking done on cached
26263 connections to folders you previously had open but are no longer actively
26265 You aren't expected to understand that last sentence, but if you are interested
26267 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>
26268 and the related options.
26271 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26273 <End of help on this topic>
26276 ====== h_config_fifopath =====
26279 <TITLE>OPTION: NewMail FIFO Path</TITLE>
26282 <H1>OPTION: NewMail FIFO Path</H1>
26284 This option is only available in UNIX Alpine.
26285 However, there is a very similar feature built in to PC-Alpine.
26286 In PC-Alpine's Config menu at the top of the screen
26287 is an option called "New Mail Window".
26289 You may have Alpine create a FIFO special file (also called a named pipe) where
26290 it will send a one-line message each time a new message is received in
26291 the current folder, the INBOX, or any open
26292 <A HREF="h_config_permlocked"><!--#echo var="VAR_stay-open-folders"--></A>.
26293 To protect against two different Alpines both writing to the same FIFO, Alpine
26294 will only create the FIFO and write to it if it doesn't already exist.
26296 A possible way to use this option would be to have a separate window
26297 on your screen running the command
26299 <CENTER><SAMP>cat filename</SAMP></CENTER>
26301 where "filename" is the name of the file given for this option.
26302 Because the file won't exist until after you start Alpine, you must <EM>first</EM>
26303 start Alpine and <EM>then</EM> run the "cat" command.
26304 You may be tempted to use "tail -f filename" to view the new
26306 However, the common implementations of the tail command will not do what you
26309 The width of the messages produced for the FIFO may be altered with the
26310 <A HREF="h_config_newmailwidth"><!--#echo var="VAR_newmail-window-width"--></A> option.
26312 On some systems, fifos may only be created in a local filesystem.
26313 In other words, they may not be in NFS filesystems.
26314 This requirement is not universal.
26315 If the system you are using supports it, it should work.
26316 (It is often the case that your home directory is in an NFS filesystem.
26317 If that is the case, you might try using a file in the "/tmp"
26318 filesystem, which is usually a local filesytem.)
26319 Even when it is possible to use an NFS-mounted filesystem as a place to name
26320 the fifo (for example, your home directory), it will still be the case that
26321 the reader (probably the "cat" command) and the
26322 writer (Alpine) of the fifo must be running on the same system.
26325 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26327 <End of help on this topic>
26330 ====== h_config_newmailwidth =====
26333 <TITLE>OPTION: <!--#echo var="VAR_newmail-window-width"--></TITLE>
26336 <H1>OPTION: <!--#echo var="VAR_newmail-window-width"--></H1>
26338 For UNIX Alpine, this option is only useful if you have turned on the
26339 <A HREF="h_config_fifopath">NewMail FIFO Path</A> option.
26340 That option causes new mail messages to be sent to a fifo file.
26341 Those messages will be 80 characters wide by default.
26342 You can change the width of those messages by changing this option.
26343 For example, if you are reading those messages in another window you might
26344 want to set this width to the width of that other window.
26346 If you are using PC-Alpine, it has an option in the Config menu to turn
26347 on the "New Mail Window".
26348 This present option also controls the width of that window.
26351 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26353 <End of help on this topic>
26356 ====== h_config_mailcheck =====
26359 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval"--></TITLE>
26362 <H1>OPTION: <!--#echo var="VAR_mail-check-interval"--></H1>
26364 This option specifies, in seconds,
26365 how often Alpine will check for new mail.
26366 If set to zero, new-mail checking is disabled.
26367 (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
26368 current message is the last message of the folder.)
26369 There is a minimum value for this option, normally 15 seconds.
26370 The default value is normally 150 seconds.
26371 The higher you set this option, the easier it is on the server.
26373 There are some situations where automatic new-mail checking does not work.
26374 See the discussion about new-mail checking in
26375 <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
26377 The new-mail checking will not happen exactly at the frequency that you specify.
26378 For example, Alpine may elect to defer a non-INBOX mail check if you
26380 Or, it may check more frequently than you have specified if that is
26381 thought to be necessary to keep the server from closing the connection
26382 to the folder due to inactivity.
26383 If Alpine checks for new mail as a side effect of another command, it will reset
26384 the timer, so that new-mail checking may seem to happen irregularly instead of
26385 every X seconds like clockwork.
26387 If you are anxious to know about new mail as soon as possible, set the check
26388 interval low, and you'll know about the new mail by approximately
26389 that amount of time after it arrives.
26390 If you aren't so worried about knowing right away, set this option to a
26392 That will save the server some processing time and may save you some of
26393 the time you spend waiting for new-mail checks to happen if you are
26394 dealing with a slow server or slow network connection.
26396 If you suspect that new-mail checking is causing slow downs for you,
26397 you may want to look into the options
26398 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>,
26399 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> and
26400 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A>,
26401 which refine when mail checking is done.
26403 If the mailbox being checked uses a <A HREF="h_maildrop">Mail Drop</A> then
26404 there is a minimum time
26405 (<A HREF="h_config_maildropcheck">"<!--#echo var="VAR_maildrop-check-minimum"-->"</A>)
26406 between new-mail checks.
26407 Because of this minimum you may notice that new mail does not
26408 appear promptly when you expect it.
26409 The reason for this is to protect the server from over-zealous opening and
26410 closing of the Mail Drop folder, since that is a costly operation.
26413 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26415 <End of help on this topic>
26418 ====== h_config_quell_checks_comp =====
26421 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></TITLE>
26424 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></H1>
26426 This option is closely related to the
26427 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26429 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
26430 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A>.
26432 If this option is set, then the normal new-mail checking that happens
26433 while you are composing will not happen for folders other than your
26434 INBOX (which depends on the setting
26435 of "<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->").
26437 You might want to set this option if you are experiencing delays while
26438 composing that you think might be related to the speed of the new-mail
26441 Even with this option turned on, an occasional new-mail check may be done
26442 in order to keep the server from killing the connection to the folder.
26443 For example, IMAP servers may remove a connection to a folder if there
26444 has been no activity on the connection for 30 minutes or more.
26445 Instead of letting that happen, Alpine will check for new mail before the
26446 30 minutes is up even though you have turned on this feature to quell
26449 Besides new-mail checks, checkpoint operations on the folders
26450 will also be quelled when you set this option.
26451 The purpose of checkpointing is to write the changes to a folder out to
26452 disk periodically in order to avoid losing those changes when system or
26453 software problems occur.
26454 New-mail checking and checkpointing while you are not composing are not
26455 affected by this option.
26458 <End of help on this topic>
26461 ====== h_config_quell_checks_comp_inbox =====
26464 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></TITLE>
26467 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></H1>
26469 This option is closely related to the
26470 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26472 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
26473 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>.
26475 If this option is set, then the normal new-mail checking that happens
26476 while you are composing will not happen for your INBOX.
26477 Checking of other folders is controlled in a similar way with the
26478 "<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->" option.
26480 You might want to set this option if you are experiencing delays while
26481 composing that you think might be related to the speed of the new-mail
26484 Even with this option turned on, an occasional new-mail check may be done
26485 in order to keep the server from killing the connection to the folder.
26486 For example, IMAP servers may remove a connection to a folder if there
26487 has been no activity on the connection for 30 minutes or more.
26488 Instead of letting that happen, Alpine will check for new mail before the
26489 30 minutes is up even though you have turned on this feature to quell
26492 Besides new-mail checks, checkpoint operations on the INBOX
26493 will also be quelled when you set this option.
26494 The purpose of checkpointing is to write the changes to a folder out to
26495 disk periodically in order to avoid losing those changes when system or
26496 software problems occur.
26497 New-mail checking and checkpointing while you are not composing are not
26498 affected by this option.
26500 <End of help on this topic>
26503 ====== h_config_maildropcheck =====
26506 <TITLE>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></TITLE>
26509 <H1>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></H1>
26511 New-mail checking for a
26512 <A HREF="h_maildrop">Mail Drop</A> is a little different from new
26513 mail checking for a regular folder.
26514 One of the differences is that the connection to the Mail Drop is not
26515 kept open and so the cost of checking
26516 (delay for you and additional load for the server) may be significant.
26517 Because of this additional cost we set a minimum time that
26518 must pass between checks.
26519 This minimum only applies to the automatic checking done by Alpine.
26520 If you force a check by typing ^L (Ctrl-L) or by typing the Next command when you are
26521 at the end of a folder index, then the check is done right away.
26523 This option specifies, in seconds, the <EM>minimum</EM> time between Mail Drop
26525 You may want to set this minimum high in order to avoid experiencing some
26526 of the delays associated with the checks.
26527 Note that the time between checks is still controlled by the regular
26528 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option.
26529 When Alpine is about to do an automatic check for new mail (because
26530 the <!--#echo var="VAR_mail-check-interval"--> has expired) then if the time since the last
26532 of any open Mail Drops has been greater than the <!--#echo var="VAR_maildrop-check-minimum"-->,
26533 the Mail Drop is checked for new mail as well.
26534 Therefore, it is only useful to set this option to a value that is higher
26535 than the <!--#echo var="VAR_mail-check-interval"-->.
26537 If this option is set to zero, automatic Mail Drop new-mail
26538 checking is disabled.
26539 There is a minimum value, normally 60 seconds.
26540 The default value is normally 60 seconds as well.
26541 This applies to the INBOX and to the currently open folder if that is
26542 different from the INBOX.
26546 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26548 <End of help on this topic>
26551 ====== h_config_nntprange =====
26554 <TITLE>OPTION: <!--#echo var="VAR_nntp-range"--></TITLE>
26557 <H1>OPTION: <!--#echo var="VAR_nntp-range"--></H1>
26559 This option applies only to newsgroups accessed using the NNTP protocol.
26560 It does not, for example,
26561 apply to newsgroups accessed using an IMAP-to-NNTP proxy.
26564 When you open a connection to a News server using the NNTP protocol, you
26565 normally have access to all of the articles in each newsgroup.
26566 If a server keeps a large backlog of messages it may speed performance
26567 some to restrict attention to only the newer messages in a group.
26568 This option allows you to set how many article numbers should be checked
26569 when opening a newsgroup.
26570 You can think of "<!--#echo var="VAR_nntp-range"-->" as specifying the maximum number
26571 of messages you ever want to see.
26572 For example, if you only ever wanted to look at the last 500 messages in each
26573 newsgroup you could set this option to 500.
26574 In actuality, it isn't quite that.
26575 Instead, for performance reasons, it specifies the range of article
26576 numbers to be checked, beginning
26577 with the highest numbered article and going backwards from there.
26578 If there are messages that have been canceled or deleted
26579 their article numbers are still counted as part of the range.
26581 So, more precisely, setting the "<!--#echo var="VAR_nntp-range"-->" will cause article
26583 <P><CENTER>last_article_number - <!--#echo var="VAR_nntp-range"--> + 1 through last_article_number</CENTER>
26585 to be considered when reading a newsgroup.
26586 The number of messages that show up in your index will be less than or equal
26587 to the value of "<!--#echo var="VAR_nntp-range"-->".
26590 The purpose of this option is simply to speed up access when reading news.
26591 The speedup comes because Alpine can ignore all but the last <!--#echo var="VAR_nntp-range"--> article
26592 numbers, and can avoid downloading any information about the ignored articles.
26593 There is a cost you pay for this speedup.
26594 That cost is that there is no way for you to see those ignored articles.
26595 The articles that come before the range you specify are invisible to you and
26596 to Alpine, as if they did not exist at all.
26597 There is no way to see those messages using, for example, an unexclude command
26598 or something similar.
26599 The only way to see those articles is to set this option high enough (or
26600 set it to zero) and then to reopen the newsgroup.
26603 If this option is set to 0 (which is also the default),
26604 then the range is unlimited.
26605 This option applies globally to all NNTP servers and to all newsgroups
26607 There is no way to set different values for different newsgroups or servers.
26611 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26613 <End of help on this topic>
26616 ====== h_config_news_active =====
26619 <title>OPTION: <!--#echo var="VAR_news-active-file-path"--></title>
26622 <h1>OPTION: <!--#echo var="VAR_news-active-file-path"--></h1>
26624 This option tells Alpine where to look for the "active file" for newsgroups
26625 when accessing news locally, rather than via NNTP. The default path is
26626 usually "/usr/lib/news/active".<p>
26628 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26630 <End of help on this topic>
26633 ====== h_config_news_spool =====
26636 <title>OPTION: <!--#echo var="VAR_news-spool-directory"--></title>
26639 <h1>OPTION: <!--#echo var="VAR_news-spool-directory"--></h1>
26641 This option tells Alpine where to look for the "news spool" for newsgroups
26642 when accessing news locally, rather than via NNTP. The default path is
26643 usually "/var/spool/news".<p>
26645 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26647 <End of help on this topic>
26650 ====== h_config_image_viewer =====
26653 <title>OPTION: <!--#echo var="VAR_image-viewer"--></title>
26656 <h1>OPTION: <!--#echo var="VAR_image-viewer"--></h1>
26658 This option specifies the program Alpine should call to view MIME
26659 attachments of type IMAGE (e.g. GIF or TIFF). The Image Viewer setting is
26660 no longer needed, but remains for backward compatibility. The more
26661 general method for associating external printing and viewing programs with
26662 specific MIME data types is to use the system's (or your personal)
26663 "mailcap" configuration file.<p>
26665 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26667 <End of help on this topic>
26670 ====== h_config_domain_name =====
26673 <TITLE>OPTION: <!--#echo var="VAR_use-only-domain-name"--></TITLE>
26676 <H1>OPTION: <!--#echo var="VAR_use-only-domain-name"--></H1>
26678 This option is used only if the
26679 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> option is <B>not</B>
26680 set. If set to "Yes" (and <!--#echo var="VAR_user-domain"--> is not used), then Alpine
26681 strips the hostname from your return ("From") address and when
26682 completing unqualified addresses that you enter into the composer.
26684 If you set this, see also the <A HREF="h_config_quell_local_lookup">
26685 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
26688 <!--chtml if pinemode="os_windows"-->
26689 <P>This option is not applicable to PC-Alpine.
26694 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26697 <End of help on this topic>
26700 ====== h_config_prune_date =====
26703 <TITLE>OPTION: Last-Time-Prune Question</TITLE>
26706 <H1>OPTION: Last-Time-Prune Question</H1>
26708 This value records the last time you were asked about deleting old
26710 It is set automatically by Alpine at the beginning of each month.
26711 In the past, if you wished to suppress the monthly sent-mail
26712 pruning feature, you could set this to a date in the future.
26713 This value is relative to the year 1900, so
26714 to set this, for example, to October 2005, use 105.10.
26716 You can still do that if you wish, or you can use the
26717 <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option, which is probably
26718 a little more convenient to use.
26721 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26723 <End of help on this topic>
26726 ====== h_config_goto_default =====
26729 <TITLE>OPTION: <!--#echo var="VAR_goto-default-rule"--></TITLE>
26732 <H1>OPTION: <!--#echo var="VAR_goto-default-rule"--></H1>
26734 This value affects Alpine's behavior when you use the Goto command.
26735 Alpine's usual behavior has two parts. If your current folder is
26736 "Inbox", Alpine will offer the last open folder as the
26737 default. If the current folder is other than "Inbox",
26738 "Inbox" is offered as the default.
26741 The available options include:
26745 <DT>folder-in-first-collection</DT>
26747 <DD> Alpine will offer the most recently visited folder in the default
26748 collection found in the "Collection List" screen as the default.
26751 <DT> inbox-or-folder-in-first-collection</DT>
26753 <DD> If the current folder is "Inbox",
26754 Alpine will offer the most recently visited folder in the
26755 default collection found in the "Collection List" screen.
26756 If the current folder is other than "Inbox",
26757 "Inbox" is offered as the default.
26760 <DT> inbox-or-folder-in-recent-collection</DT>
26762 <DD> This is Alpine's default behavior.
26763 If the current folder is "Inbox",
26764 Alpine will offer the last open
26765 folder as the default.
26766 If the current folder is other than "Inbox",
26767 "Inbox" is offered as the default.
26770 <DT> first-collection-with-inbox-default</DT>
26772 <DD> Instead of offering the most recently visited folder in the default
26773 collection, the default collection is offered but with "Inbox" as
26774 the default folder.
26775 If you type in a folder name it will be in the default collection.
26776 If you simply accept the default, however, your "Inbox" will be opened.
26779 <DT> most-recent-folder</DT>
26781 <DD> The last accepted value simply causes the most recently opened
26782 folder to be offered as the default regardless of the currently opened
26788 NOTE: The default while a newsgroup is open remains the same; the last
26793 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26795 <End of help on this topic>
26798 ====== h_config_thread_lastreply_char =====
26801 <TITLE>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></TITLE>
26804 <H1>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></H1>
26806 The <!--#echo var="VAR_threading-lastreply-character"--> option has a small effect on the MESSAGE
26807 INDEX display when using a
26808 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
26809 of "show-thread-structure", "mutt-like", or
26810 "show-structure-in-from"; and sorting by Threads or OrderedSubject.
26811 The value of this option is a single character.
26812 This character is used instead of the vertical line character when there are
26813 no more replies directly to the parent of the current message.
26814 It can be used to "round-off" the bottom of the vertical line
26815 by setting it to a character such as a backslash (\) or
26816 a backquote (`).
26817 The default value of this option is the backslash character (\).
26818 This option may not be set to the Empty Value.
26819 In that case, the default will be used instead.
26823 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26825 <End of help on this topic>
26828 ====== h_config_thread_indicator_char =====
26831 <TITLE>OPTION: <!--#echo var="VAR_threading-indicator-character"--></TITLE>
26834 <H1>OPTION: <!--#echo var="VAR_threading-indicator-character"--></H1>
26836 The <!--#echo var="VAR_threading-indicator-character"--> option has a small effect on the MESSAGE
26837 INDEX display when using a
26838 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26839 than "none" and sorting by Threads or OrderedSubject.
26840 The value of this option is a single character.
26841 This character is used to indicate that part of a thread (a conversation) is
26842 hidden beneath a message.
26843 The message could be expanded
26844 if desired with the "/" Collapse/Expand command.
26845 By default, the value of this option is the greater than sign (>).
26847 If this option is set to the Empty Value, then the column (and the following
26848 blank column) will be deleted from the display.
26851 This option is closely related to the
26852 <A HREF="h_config_thread_exp_char"><!--#echo var="VAR_threading-expanded-character"--></A> option.
26853 Another similar option that affects the thread display is the
26854 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26858 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26860 <End of help on this topic>
26863 ====== h_config_thread_exp_char =====
26866 <TITLE>OPTION: <!--#echo var="VAR_threading-expanded-character"--></TITLE>
26869 <H1>OPTION: <!--#echo var="VAR_threading-expanded-character"--></H1>
26871 The <!--#echo var="VAR_threading-expanded-character"--> option has a small effect on the MESSAGE
26872 INDEX display when using a
26873 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26874 than "none".
26875 The value of this option is a single character.
26876 This character is used to indicate that part of a thread has been expanded
26877 and could be collapsed if desired with
26878 the "/" Collapse/Expand command.
26879 By default, the value of this option is a dot (.).
26881 If this option is set to the Empty Value, then the column (and the following
26882 blank column) will be deleted from the display.
26885 This option is closely related to the
26886 <A HREF="h_config_thread_indicator_char"><!--#echo var="VAR_threading-indicator-character"--></A> option.
26887 Another similar option that affects the thread display is the
26888 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26892 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26894 <End of help on this topic>
26897 ====== h_config_thread_index_style =====
26900 <TITLE>OPTION: <!--#echo var="VAR_threading-index-style"--></TITLE>
26903 <H1>OPTION: <!--#echo var="VAR_threading-index-style"--></H1>
26905 When a folder is sorted by Threads or OrderedSubject,
26906 this option will affect the INDEX displays.
26909 The possible values for this option are:
26912 <DT>regular-index-with-expanded-threads</DT>
26913 <DD>This is the default display.
26914 If the configuration option
26915 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26916 is set to something other than "none", then this setting
26917 will cause Alpine to start off with a MESSAGE INDEX with all of
26918 the threads expanded.
26919 That is, each message will have a line in the MESSAGE INDEX display.
26920 The Collapse/Expand command (/) may be used to manually collapse or
26921 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26923 This setting affects the display when the folder is first threaded.
26924 The collapsed state may also be re-initialized by re-sorting the folder manually
26925 using the SortIndex command ($).
26926 After re-sorting the threads will once again all be expanded, even if you
26927 have previously collapsed some of them.
26929 If "<!--#echo var="VAR_threading-display-style"-->" is set to "none", then
26930 the display will be the regular default Alpine MESSAGE INDEX, but sorted
26931 in a different order.
26934 <DT>regular-index-with-collapsed-threads</DT>
26935 <DD>If the configuration option
26936 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26937 is set to something other than "none", then this setting
26938 will cause Alpine to start out with all of the threads collapsed instead of
26939 starting out with all of the threads expanded.
26940 The Collapse/Expand command (/) may be used to manually collapse or
26941 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26943 This setting affects the display when the folder is first threaded.
26944 The collapsed state may also be re-initialized by re-sorting the folder manually
26945 using the SortIndex command ($).
26946 After re-sorting the threads will once again all be collapsed, even if you
26947 have previously expanded some of them.
26950 <DT>separate-index-screen-always</DT>
26951 <DD>With this setting and the next, you will see an index of threads
26953 index of messages, provided you have sorted by Threads or OrderedSubject.
26955 The THREAD INDEX contains a '*' in the first column if any message in the thread
26956 is marked Important.
26957 If not, it contains a '+' if any message in the thread is to you.
26958 The second column is blank. The third column contains a 'D' if all of the
26959 messages in the thread are deleted.
26960 Otherwise, it contains an 'N' if any of the messages in the thread are New.
26962 When you view a particular thread from the THREAD INDEX you will be
26963 in the MESSAGE INDEX display
26964 but the index will only contain messages from the thread you are viewing.
26967 <DT>separate-index-screen-except-for-single-messages</DT>
26968 <DD>This is very similar to the option above.
26969 When you are in the THREAD INDEX, one of the available commands
26970 is "ViewThd".
26971 With the setting "separate-index-screen-always" (the option above)
26972 when you view a particular thread you will be in the
26973 MESSAGE INDEX display and the index will only contain messages from
26974 the thread you are viewing.
26975 If the thread you are viewing consists of a single message, the MESSAGE INDEX
26976 will be an index with only one message in it.
26977 If you use this "separate-index-screen-except-for-single-messages"
26978 setting instead, then that index that contains a single message
26979 will be skipped and you will go directly from the THREAD INDEX into the
26980 MESSAGE TEXT screen.
26987 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26989 <End of help on this topic>
26992 ====== h_config_thread_disp_style =====
26995 <TITLE>OPTION: <!--#echo var="VAR_threading-display-style"--></TITLE>
26998 <H1>OPTION: <!--#echo var="VAR_threading-display-style"--></H1>
27000 When a folder is sorted by Threads or OrderedSubject,
27001 this option will affect the MESSAGE INDEX display.
27002 By default, Alpine will display the MESSAGE INDEX in the
27003 "show-thread-structure" style if a folder is sorted
27004 by Threads or OrderedSubject.
27007 The possible values for this option are:
27011 <DD>Regular index display.
27012 The same index line as would be displayed without threading is used.
27013 The only difference will be in the order of the messages.
27016 <DT>show-thread-structure</DT>
27017 <DD>Threaded Subjects will be indented and vertical bars and horizontal
27018 lines will be added to make it easier to see the relationships among
27019 the messages in a thread (a conversation).
27023 <DD>This is the same as the option above except that the Subject
27024 is suppressed (is blank) if it matches the previous Subject in the thread.
27025 The name comes from the email client <A HREF="http://www.mutt.org/">Mutt</A>.
27026 Here is an example of what a mutt-like index might look like.
27027 In this example, the first column represents the message number, the
27028 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
27029 is set to "regular-index-with-expanded-threads", and the
27030 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A>
27031 is set to a backslash:
27033 1 Some topic
27034 2 . Subject original message in thread
27035 3 |-> reply to 2
27036 4 . |-> another reply to 2
27037 5 . | \-> reply to 4
27038 6 . | \-> reply to 5
27039 7 | \-> reply to 6
27040 8 |-> another reply to 2
27041 9 . |->New subject another reply to 2 but with a New subject
27042 10 | |-> reply to 9
27043 11 | \-> another reply to 9
27044 12 | \-> reply to 11
27045 13 \-> final reply to 2
27046 14 Next topic
27050 <DT>indent-subject-1</DT>
27051 <DD>Threaded Subjects will be indented one space per level of the conversation.
27052 The bars and lines that show up in the show-thread-structure display will
27053 not be there with this style.
27056 <DT>indent-subject-2</DT>
27057 <DD>Same as above but indent two spaces per level instead of one space.
27060 <DT>indent-from-1</DT>
27061 <DD>Similar to indent-subject-1, except that instead of indenting the
27062 Subject field one space the From field of a thread will be indented one
27063 space per level of the conversation.
27066 <DT>indent-from-2</DT>
27067 <DD>Same as above but indent two spaces per level instead of one space.
27070 <DT>show-structure-in-from</DT>
27071 <DD>The structure of the thread is illustrated with indenting, vertical bars,
27072 and horizontal lines just like with the show-thread-structure option, but
27073 the From field is used to show the relationships instead of the Subject field.
27080 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27082 <End of help on this topic>
27085 ====== h_config_pruning_rule =====
27088 <TITLE>OPTION: <!--#echo var="VAR_pruning-rule"--></TITLE>
27091 <H1>OPTION: <!--#echo var="VAR_pruning-rule"--></H1>
27093 By default, Alpine will ask at the beginning of each month whether or not
27094 you want to rename your sent-mail folder to a name like sent-mail-month-year.
27095 (See the feature <A HREF="h_config_prune_uses_iso"><!--#echo var="FEAT_prune-uses-yyyy-mm"--></A> to
27096 change the format of the folder to sent-mail-yyyy-mm.)
27097 It will also ask whether you would like to delete old sent-mail folders.
27098 If you have defined
27099 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>
27101 <A HREF="h_config_pruned_folders"><!--#echo var="VAR_pruned-folders"--></A>
27102 Alpine will also ask about pruning those folders.
27105 With this option you may provide an automatic answer to these questions.
27106 The default value is to ask you what you'd like to do.
27109 The six possible values for this option are:
27112 <DT>ask about rename, ask about deleting</DT>
27113 <DD>This is the default.
27114 Alpine will ask whether you want to rename the folders and whether you
27115 want to delete each of the old folders.
27118 <DT>ask about rename, don't delete</DT>
27119 <DD>Alpine will ask whether you want to rename the folders, but won't
27120 ask about or delete old folders.
27123 <DT>always rename, ask about deleting</DT>
27124 <DD>This means you want to always answer yes and have Alpine automatically
27125 rename the folder if possible.
27126 You will also be asked about deleting old folders.
27129 <DT>always rename, don't delete</DT>
27130 <DD>This means you want to always answer yes and have Alpine automatically
27131 rename the folder if possible.
27132 There will be no deleting of old folders.
27135 <DT>don't rename, ask about deleting</DT>
27136 <DD>This means you want to always answer no.
27137 Alpine will not rename the folder.
27138 You will be asked about deleting old folders.
27141 <DT>don't rename, don't delete</DT>
27142 <DD>This means you want to always answer no.
27143 Alpine will not rename the folder.
27144 There will be no deleting of old folders, either.
27150 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27152 <End of help on this topic>
27155 ====== h_config_reopen_rule =====
27158 <TITLE>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></TITLE>
27161 <H1>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></H1>
27163 Alpine normally checks for new mail in the currently open folder
27164 and in the INBOX every few <A HREF="h_config_mailcheck">minutes</A>.
27167 There are some situations where automatic new-mail checking does not work.
27168 For example, if a mail folder is opened using the POP protocol or a newsgroup
27169 is being read using the NNTP protocol, then new-mail checking is disabled.
27172 It may be possible to check for new mail in these cases by reopening the
27174 Alpine does not do this for you automatically, but you may do the commands
27175 manually to cause this to happen.
27176 You reopen by going back to the folder list screen from the message
27177 index screen with the "<" command,
27178 and then going back into the message index screen with
27179 the ">" command.
27180 (Actually, any method you would normally use to open a folder will work the
27181 same as the "<" followed by ">" method.
27182 For example, the GoTo Folder command will work, or you may use L to go to the
27183 Folder List screen and Carriage Return to reopen the folder.)
27186 There are some cases where Alpine knows that reopening the folder should
27187 be useful as a way to discover new mail.
27188 At the time of this writing, connections made using the POP protocol,
27189 news reading using the NNTP protocol, local news reading, and local
27190 ReadOnly folders that are in the traditional UNIX or the MMDF format all
27191 fall into this category.
27192 There are other cases where it <EM>may</EM> be a way to discover new mail, but Alpine
27193 has no way of knowing, so it might also just be an exercise in futility.
27194 All remote, ReadOnly folders other than those listed just above fall into this
27196 The setting of this option together with the type of folder
27197 controls how Alpine will react to the apparent attempt to reopen a folder.
27200 If you don't reopen, then you will just be back in
27201 the message index with no change.
27202 You left the index and came back, but the folder remained "open"
27204 However, if you do reopen the folder, the folder is closed and then reopened.
27205 In this case, the current state of the open folder is lost.
27206 The New status, Important and Answered flags,
27207 selected state, Zoom state, collapsed or expanded state of threads,
27208 current message number,
27209 and any other temporary state is all lost when the reopen happens.
27210 For POP folders (but not NNTP newsgroups) the Deleted flags are also lost.
27213 In the possibilities listed below, the text says "POP/NNTP" in
27215 That really implies the case where Alpine knows it is a good way to discover
27216 new mail, which is more than just POP and NNTP, but POP and NNTP are
27217 the cases of most interest.
27218 This option probably has more possible values than it deserves. They are:
27221 <DT>Always reopen</DT>
27222 <DD>Alpine will not ask whether you want to reopen but will just do the reopen
27223 whenever you type a command that implies a reopen, regardless of the
27225 In other words, it is assumed you would always answer Yes if asked
27229 <DT>Yes for POP/NNTP, Ask about other remote [Yes]</DT>
27230 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
27231 will ask you whether to reopen other remote folders,
27232 with a default answer of Yes.
27235 <DT>Yes for POP/NNTP, Ask about other remote [No]</DT>
27236 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
27237 will ask you whether to reopen other remote folders,
27238 with a default answer of No.
27241 <DT>Yes for POP/NNTP, No for other remote</DT>
27242 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, and
27243 will assume a No answer for all other remote folders.
27246 <DT>Always ask [Yes]</DT>
27247 <DD>Alpine will not differentiate based on access method.
27248 It will always ask for all remote folders, with a default answer of Yes.
27251 <DT>Always ask [No]</DT>
27252 <DD>Alpine will not differentiate based on access method.
27253 It will always ask for all remote folders, with a default answer of No.
27256 <DT>Ask about POP/NNTP [Yes], No for other remote</DT>
27257 <DD>Alpine will ask if the access method is POP or NNTP, with a default answer
27259 It will never attempt to reopen other remote folders.
27262 <DT>Ask about POP/NNTP [No], No for other remote</DT>
27263 <DD>This is the default.
27264 Alpine will ask if the access method is POP or NNTP, with a default answer
27266 It will never attempt to reopen other remote folders.
27269 <DT>Never reopen</DT>
27270 <DD>Alpine will never attempt to reopen already open folders.
27275 Remember, wherever it says POP or NNTP above it really means POP or NNTP or
27276 any of the other situations where it is likely that reopening is a good way
27277 to discover new mail.
27280 There is an alternative that may be of useful in some situations.
27281 Instead of manually checking for new mail you can set up a
27282 <A HREF="h_maildrop">Mail Drop</A>
27283 and automatically check for new mail.
27287 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27289 <End of help on this topic>
27292 ====== h_config_inc_startup =====
27295 <TITLE>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></TITLE>
27298 <H1>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></H1>
27300 This value affects Alpine's behavior when opening the "INBOX" or
27301 one of the "INCOMING MESSAGE FOLDERS".
27302 It determines which message will be the <EM>current message</EM> when
27303 the folder is first opened.
27304 The default value is "first-unseen".
27307 The seven possible values for this option are:
27310 <DT>first-unseen</DT>
27311 <DD>The current message is set to the first
27312 unseen message that has not been marked deleted, or the last message if
27313 all of the messages have been seen previously.
27314 Messages which have not been seen or which have been seen but re-marked
27315 as New are considered unseen messages.
27316 See the note at the bottom of this help about newsgroups.
27319 <DT>first-recent</DT>
27320 <DD>Similar to the default, but rather than starting on the first
27321 unseen message Alpine starts on the first <EM>recent</EM> message.
27322 A message is recent if it arrived since the last time the folder was
27323 open. This value causes the current message to be set to the first
27324 recent message if there is one, otherwise to the last
27325 message in the folder.
27328 <DT>first-important</DT>
27329 <DD>This will result in the current message being set to the first
27330 message marked Important (but not Deleted).
27331 If no messages are marked Important, then it will be the last message.
27332 Messages are marked Important by <EM>you</EM>, not by the sender, using
27334 <A HREF="h_common_flag">Flag command</A>.
27335 Or they may be marked Important by an Alpine
27336 <A HREF="h_mainhelp_filtering">Filter</A>
27337 that you have set up.
27340 <DT>first-important-or-unseen</DT>
27341 <DD>This selects the first of the first unseen and the first important
27345 <DT>first-important-or-recent</DT>
27346 <DD>This selects the first of the first recent and the first important
27351 <DD>Simply starts you on the <EM>first</EM> undeleted message in the folder.
27352 If all messages are deleted you start on the last message.
27356 <DD>Simply starts you on the <EM>last</EM> undeleted message in the folder
27357 If all messages are deleted you start on the last message.
27362 NOTE: For newsgroups in the incoming collection, "first-unseen" and
27363 "first-recent" are the same and are affected by whether or not the
27365 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
27367 Also, there is no permanent storage in news for an Important flag.
27368 This means that no messages will be marked Important when a newsgroup is
27373 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27375 <End of help on this topic>
27378 ====== h_config_browser =====
27381 <TITLE>OPTION: <!--#echo var="VAR_url-viewers"--></TITLE>
27384 <H1>OPTION: <!--#echo var="VAR_url-viewers"--></H1>
27385 <!--chtml if pinemode="os_windows"-->
27386 PC-Alpine users do not need to enter anything here, unless:<UL>
27387 <LI> they want to override, for use with Alpine, the application defined
27388 in the Windows operating system for handling URLs; or
27389 <LI> they are (planning on) using the same configuration file with
27393 Note that if using a viewer that has a space in its path, you should
27394 use the DOS name for that directory or file. Example:
27396 url-viewer=C:\Progra~1\mozilla\mozilla.exe
27400 This option affects Alpine's handling of URLs that are found in
27401 messages you read. Normally, only URLs Alpine can handle directly
27402 are automatically offered for selection in the "Message
27403 Text" screen. When one or more applications
27404 capable of deciphering URLs on their command line are added here, Alpine
27405 will choose the first available to display URLs it cannot handle directly.
27406 A viewer's availability is based on its being specified with a <B>full
27407 directory path</B> and the evaluation of any optionally supplied
27408 parameters described below.
27411 Additionally, to support various connection methods and applications, each
27412 entry in this list can optionally begin with one or more of
27413 the following special tokens. The allowed tokens include:
27417 <DT>_TEST(<VAR>test-string</VAR>)_</DT>
27419 The <VAR>test-string</VAR> is a shell command that Alpine will run to
27420 evaluate a viewer's availability. The command specified by the test
27421 string is run and if its resulting exit status is non-zero, Alpine will
27422 not consider the associated viewer for use.
27425 <DT>_SCHEME(<VAR>scheme-list</VAR>)_</DT>
27427 The <VAR>scheme-list</VAR> is a list of one or more (comma-delimited)
27428 URL schemes that are to be used with the associated viewer. This is
27429 the way to configure Alpine to recognize URLs other than the built-in set.
27431 It can also be used to override Alpine's built-in handlers.
27432 For example, you could specify "news" in the <VAR>scheme-list</VAR>,
27433 and Alpine would use (provided it passed all other criteria) the associated
27434 viewer when it encounterd a URL of the form "news:comp.mail.pine".
27440 By default, Alpine will simply append a space character followed by the
27441 selected URL prior to launching the command in your specified SHELL. You can
27442 optionally specify where in the command the selected URL should appear
27443 by using the "_URL_" token. All occurrences found in the command
27444 will be replaced with the selected URL before the command is handed
27445 to the shell. If such replacement occurs, the default appending of the
27446 selected URL does not take place.
27449 NOTE: If the viewer you specify has any command-line arguments,
27450 including the "_URL_" token, you will need to add a
27451 double-quote character before the command path and after the last
27452 argument (see the "lynx" example below).
27455 So, here are some example entries:
27457 url-viewers = _TEST("test -n '${DISPLAY}'")_ /usr/local/bin/netscape
27458 "/usr/local/bin/lynx _URL_"
27459 C:\BIN\NETSCAPE.BAT
27462 This example shows that for the first viewer in the list to be used
27463 the environment variable "DISPLAY" must be defined. If it
27464 is, then the path and file "/usr/local/bin/netscape" must exist.
27465 If neither condition is met,
27466 then the path and file "/usr/local/bin/lynx" must exist.
27467 If it does, then the "_URL_" token is replaced by the selected URL.
27468 If the path to "lynx" is invalid,
27469 then the final path and file C:\BIN\NETSCAPE.BAT must exist.
27471 entry is a DOS/Windows path. This is one way to support Alpine running
27472 on more than one architecture with the same configuration file.<P>
27474 <!--chtml if pinemode="os_windows"-->
27476 Note that depending on the type of browser used and the method of
27477 its invocation (such as whether it will open in a separate window) from
27478 the MESSAGE TEXT screen, the browser may "supplant"
27479 the MESSAGE TEXT screen, and you will have to quit the browser to return to
27480 it (for example, when using Lynx; to exit Lynx, use the "Q" command).
27481 In other words, launching the browser from Alpine may make Alpine
27482 "disappear" (although it is still "running")
27483 until you close the browser again.<P>
27484 <UL><LI><A HREF="h_config_browser_xterm">Defining <!--#echo var="VAR_url-viewers"--> in an X windows
27485 environment: for advanced users and systems administrators</A>
27488 <P>If you are unsure what browsers are available on your system or how to
27489 specify them in Alpine's <!--#echo var="VAR_url-viewers"--> option for best usability, contact your
27490 local computing support staff.
27492 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27495 <End of help on this topic>
27498 ====== h_config_history =====
27501 <TITLE>OPTION: <!--#echo var="VAR_default-directories"--></TITLE>
27504 <H1>OPTION: <!--#echo var="VAR_default-directories"--></H1>
27506 This option allows you to input a list of directories that Alpine will offer
27507 for you to use when you are saving or exporting attachments. This is useful
27508 when navigating to specific directories becomes too tedious, or when you
27509 need to do this on a daily basis, and want Alpine to remember this on a
27512 The list of directories saved here can be accessed using the ^Y and ^V commands
27513 in the save prompt for attachments, or the export command.
27516 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27519 <End of help on this topic>
27522 ====== h_config_browser_xterm =====
27525 <TITLE><!--#echo var="VAR_url-viewers"--> and X windows applications</TITLE>
27528 <H1>Defining <!--#echo var="VAR_url-viewers"--> in an X windows
27529 environment: for advanced users and systems administrators</H1>
27530 If you are using Alpine with an X-terminal (emulator) and want to define an
27531 X windows-based application in <!--#echo var="VAR_url-viewers"-->,
27532 you may want to do so in a manner that causes any <B>already</B>
27533 invoked viewer application to be used for viewing URLs you select from Alpine
27534 messages, and a <B>new</B> URL-viewer process to be
27535 started <B>only</B> if the same application has <B>not already</B>
27536 been launched -- for one reason, to avoid file-locking contentions among
27537 multiple invocations of the same URL-viewer application.
27538 (The example entries set in the help screen for the "<!--#echo var="VAR_url-viewers"-->"
27539 option does not do this.) A method of doing that would be:<OL>
27541 the _TEST(<VAR>test-string</VAR>)_ token in the <B>first</B> entry to
27542 check (using commands appropriate for your Unix shell
27543 in place of <VAR>test-string</VAR>) for the presence of a
27544 lockfile created by the URL-viewer application -- which implies that the
27545 application is already running, though this is not foolproof.
27546 Following that in the same <!--#echo var="VAR_url-viewers"--> entry, specify the
27547 application with its appropriate command line option(s) to
27548 show the URL selected from the Alpine message in an already open window of
27549 that application, or perhaps in a new window of that application.
27552 <B>second</B> entry for the <!--#echo var="VAR_url-viewers"--> option, specify the same
27553 application without those command line options, but this time using the
27554 _TEST(...)_ token to check whether the environment variable "DISPLAY"
27556 <LI> If you will be using Alpine (with the same .pinerc file) outside of the X
27557 windows environment (for instance, using VT-100 terminal emulation), you
27558 may wish to specify a non-X windows URL-viewer application such as Lynx
27561 How exactly you define your <!--#echo var="VAR_url-viewers"--> entries to do this will depend on
27562 the command shell, the URL-viewer application(s), and possibly the specific
27563 version of the latter, you are using.
27566 line options for the Netscape browser for showing URLs (selected from Alpine)
27567 when Netscape is already running are discussed in the document
27568 "Remote Control of UNIX Netscape"
27569 found at the URL (as of 12 Aug. 1998):
27572 <CENTER><A HREF="http://home.netscape.com/newsref/std/x-remote.html">http://home.netscape.com/newsref/std/x-remote.html</A></CENTER>
27574 <P>(If the URL-viewer application is
27575 <B>not</B> running on the same host as Alpine, but being launched from an
27576 applications server, you may not be able to use the command line options for
27577 using an existing invocation of the application in Alpine's <!--#echo var="VAR_url-viewers"--> entry.)
27579 <!--chtml if this-method="shown-to-work"-->
27580 An example using the Korn shell and the Netscape browser (first entry wrapped
27581 because of its length, but should all appear on one line):
27583 url-viewers = _TEST("test -L /myhomedir/.netscape/lock")_ "/usr/local/bin/netscape -remote 'openURL(_URL_, new-window)' &"<BR>
27585 _TEST("test -n '${DISPLAY}'")_ "/usr/local/bin/netscape &"<BR>
27586 "/usr/local/bin/lynx '_URL_'"
27591 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27593 <End of help on this topic>
27596 ====== h_config_enable_full_hdr =====
27599 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></TITLE>
27602 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></H1>
27604 This feature enables the "H Full Headers" command which toggles between
27605 the display of all headers in the message and the normal edited view of
27606 headers. The Full Header command also controls which headers are included
27607 for Export, Pipe, Print, Forward, and Reply functions. (For Reply, the
27608 Full Header mode will respect the
27609 <A HREF="h_config_include_header">"Include-Headers-in-Reply"</A>
27612 If Full Header mode is turned on and you Forward a message, you will
27613 be asked if you'd like to forward the message as an attachment, as opposed
27614 to including the text of the message in the body of your new message.
27616 If you have also turned on the
27617 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
27618 option then the Full Headers command actually rotates through three states
27619 instead of just two.
27620 The first is the normal view with long quotes suppressed.
27621 The second is the normal view but with the long quotes included.
27622 The last enables the display of all headers in the message.
27623 When using Export, Pipe, Print, Forward, or Reply the quotes are
27624 never suppressed, so the first two states are identical.
27626 Normally, the Header Mode will reset
27627 to the default behavior when moving to a new message.
27628 The mode can be made to persist from message to message by setting the feature
27629 <A HREF="h_config_quell_full_hdr_reset"><!--#echo var="FEAT_quell-full-header-auto-reset"--></A>.
27632 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27634 <End of help on this topic>
27637 ====== h_config_enable_full_hdr_and_text =====
27640 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></TITLE>
27643 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></H1>
27645 This feature affects how the "H Full Headers" command displays
27646 message text. If set, the raw message text will be displayed. This
27647 especially affects MIME formatted email, where the entire MIME format
27648 will be displayed. This feature similarly affects how messages are
27649 included for the Export, Pipe, Print, Forward, and Reply functions.
27651 When viewing a raw message that has attachments with this feature set,
27652 you will not be able to view attachments without first leaving full
27653 headers mode. This is because MIME parsing is not done on the raw message.
27656 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27658 <End of help on this topic>
27661 ====== h_config_enable_pipe =====
27664 <TITLE>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></TITLE>
27667 <H1>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></H1>
27669 This feature enables the "| Pipe" command that sends the current message
27670 to the specified command for external processing.
27673 A short description of how the pipe command works is given
27674 <A HREF="h_pipe_command">here</A>.
27678 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27680 <End of help on this topic>
27683 ====== h_config_quell_full_hdr_reset =====
27686 <TITLE>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></TITLE>
27689 <H1>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></H1>
27691 The <A HREF="h_common_hdrmode">HdrMode Command</A>
27692 normally resets to the default state when switching to a new message.
27693 For example, if you've used the "H" command to turn on Full
27694 Headers for a message you are viewing, and then you type the Next command
27695 to look at the next message, the full headers will no longer be shown.
27696 Setting this feature disables that reset.
27697 Instead, the Header Mode remains the same from message to message.
27700 The presence or absence of the HdrMode command is determined by the
27701 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
27702 Feature-List option.
27705 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27707 <End of help on this topic>
27710 ====== h_config_enable_tab_complete =====
27713 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></TITLE>
27716 <H1>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></H1>
27718 This feature enables the TAB key when at a prompt for a filename. In this
27719 case, TAB will cause the partial name already entered to be automatically
27720 completed, provided the partial name is unambiguous.
27721 This feature is on by default.
27723 Similarly, this feature also enables TAB completion of address book
27724 nicknames when at a prompt for a nickname,
27725 or when typing in an address field in the composer.
27727 <End of help on this topic>
27730 ====== h_config_quit_wo_confirm =====
27733 <TITLE>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></TITLE>
27736 <H1>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></H1>
27738 This feature controls whether or not Alpine will ask for confirmation when a
27739 Quit command is received.
27741 <End of help on this topic>
27744 ====== h_config_quote_replace_noflow =====
27747 <TITLE>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></TITLE>
27750 <H1>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></H1>
27752 This feature, which is only active when
27753 <A HREF="h_config_quote_replace_string"><!--#echo var="VAR_quote-replace-string"--></A> is
27755 enables quote-replacement on non-flowed messages. It is off
27756 by default because a non-flowed message is more dependent on its format,
27757 and thus quote-replacement may cause less-than-pleasing results.
27758 Setting this feature will cause quote-replacement similar to that of flowed
27759 messages, but with the added possibility of long lines being wrapped
27760 into new lines if the Quote-Replacement-String is longer than the string
27761 it is replacing, which is "> ".
27763 <End of help on this topic>
27766 ====== h_config_enable_jump =====
27769 <TITLE>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></TITLE>
27772 <H1>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></H1>
27774 When this feature is set you may enter a number (followed by RETURN)
27775 and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT
27776 screens. In other words, it obviates the need for typing the "J" for the
27779 <End of help on this topic>
27782 ====== h_config_enable_alt_ed =====
27785 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></TITLE>
27788 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></H1>
27790 If this feature is set (the default), and the
27791 <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27792 <B>is not</B> set, entering
27793 the ^_ (Ctrl-underscore) key while composing a message will prompt you
27794 for the name of the editor you would like to use.
27796 If the environment variable $EDITOR is set, its value will be offered as
27799 If the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27800 <B>is</B> set, the ^_ key will activate the specified
27801 editor without prompting, in which case it is not necessary to
27802 set the "<!--#echo var="FEAT_enable-alternate-editor-cmd"-->" feature.
27805 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27807 <End of help on this topic>
27810 ====== h_config_alt_ed_now =====
27813 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></TITLE>
27816 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></H1>
27818 If this feature and the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A>
27819 variable are both set, Alpine will
27820 automatically activate the specified editor when the cursor is moved from
27821 the header of the message being composed into the message text. For
27822 replies, the alternate editor will be activated immediately. If this
27823 feature is set but the "<!--#echo var="VAR_editor"-->" variable is not set, then Alpine will
27824 automatically ask for the name of an alternate editor when the cursor
27825 is moved out of the header being composed, or if a reply is being done.
27828 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27831 <End of help on this topic>
27834 ====== h_config_enable_bounce =====
27837 <TITLE>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></TITLE>
27839 <H1>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></H1>
27842 Setting this feature enables the "B Bounce" command, which will prompt
27843 for an address and *remail* the message to the new recipient. This command
27844 is used to re-direct messages that you have received in error, or need to
27845 be redirected for some other reason (e.g. list moderation). The final
27846 recipient will see a header indicating that you have Resent the msg, but
27847 the message's From: header will show the original author of the message,
27848 and replies to it will go back to that author, and not to you.
27850 <End of help on this topic>
27853 ====== h_config_enable_agg_ops =====
27856 <TITLE>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></TITLE>
27859 <H1>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></H1>
27861 When this feature is set you may use the commands and subcommands that relate to
27862 performing operations on more than one message at a time. We call these
27863 "aggregate operations". In particular, the
27864 <!--chtml if pinemode="function_key"-->"F5
27865 <!--chtml else-->";
27866 <!--chtml endif--> Select",
27868 <!--chtml if pinemode="function_key"-->
27874 <!--chtml if pinemode="function_key"-->
27879 Zoom" commands are enabled by this feature. Select is used to
27880 "tag" one or more messages meeting the specified criteria. Apply can
27881 then be used to apply any message command to all of the selected/tagged
27882 messages. Further, the Zoom command allows you to toggle the MESSAGE INDEX
27883 view between just those Selected and all messages in the folder.
27885 This feature also enables the
27886 <!--chtml if pinemode="function_key"-->
27892 subcommand in the MESSAGE INDEX
27893 WhereIs command that causes all messages matching the WhereIs argument to
27894 become selected; and the Select, Select Current, and ZoomMode commands in the
27895 <A HREF="h_folder_maint">FOLDER LIST screen</A>.
27897 Some related help topics are
27899 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
27900 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
27901 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
27902 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
27903 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
27904 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
27908 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27910 <End of help on this topic>
27914 ====== h_config_enable_flag =====
27917 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></TITLE>
27920 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></H1>
27922 Setting this feature enables the
27923 <A HREF="h_common_flag">"* Flag"</A>
27924 command that allows you to
27925 manipulate the status flags associated with a message. By default, Flag
27926 will set the "Important" flag, which results in an asterisk being
27927 displayed in column one of the MESSAGE INDEX for such messages.
27929 <End of help on this topic>
27932 ====== h_config_flag_screen_default =====
27935 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></TITLE>
27938 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></H1>
27940 The feature modifies the behavior of the
27941 <a href="h_common_flag">Flag</a>
27942 command (provided it too is
27943 <A HREF="h_config_enable_flag">enabled</A>).
27944 By default, when the "* Flag" command is selected,
27945 Alpine offers a prompt to set one of several flags and also offers the
27946 option of entering the detailed flag manipulation screen via the "^T"
27947 key. Enabling this feature causes Alpine to immediately enter the detailed
27948 flag screen rather than first offer the simple prompt.
27950 <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.
27952 <End of help on this topic>
27955 ====== h_config_flag_screen_kw_shortcut =====
27958 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></TITLE>
27961 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></H1>
27963 This feature modifies the behavior of the
27964 <a href="h_common_flag">Flag</a> command
27965 and the <A HREF="h_index_cmd_select">Select</A> command.
27966 This feature is set by default.
27967 When this feature is not set, when the "* Flag" command is selected,
27968 Alpine offers a prompt to set one of several flags and also offers the
27969 option of entering the detailed flag manipulation screen via the "^T"
27972 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
27973 defined, then enabling this feature adds a shortcut way to set or unset
27975 You use "*" followed by the first letter of a keyword (or the nickname of
27976 a keyword if you've given it a nickname) and that will set the keyword.
27978 An example is easier to understand than the explanation.
27979 The flag command can always be used to set the system flags.
27980 For example, to set the Answered flag you would type
27982 <CENTER><SAMP>* A</SAMP></CENTER>
27984 Now suppose you have defined a keyword "Work" using the <!--#echo var="VAR_keywords"-->
27985 option in the Config screen.
27986 By default, to set a keyword like "Work" you would usually
27987 have to go to the Flag Details screen using
27988 the "^T To Flag Details" command.
27989 Instead, if you have enabled this feature, you may type
27991 <CENTER><SAMP>* W</SAMP></CENTER>
27993 to set the Work flag, or
27995 <CENTER><SAMP>* ! W</SAMP></CENTER>
27998 Just like for the other flag setting commands, the case of the letter does
27999 not matter, so "w" or "W" both set the "Work"
28002 Notice that you can only use this trick for one keyword that begins
28003 with "W".
28004 If you happen to have a "Work" keyword and another keyword that is
28005 "WIFI" the "* W" command will set the first one in
28006 your list of keywords.
28007 Also, there are five letters that are reserved for system
28008 flags and the NOT command.
28009 If you type "* A" it will always set the Answered flag, not
28010 your "Aardvark" keyword.
28011 In order to set the "Aardvark" keyword you'll still have to use
28012 the Flag Details screen.
28014 Because enabling the
28015 <A HREF="h_config_flag_screen_default"><!--#echo var="FEAT_enable-flag-screen-implicitly"--></A>
28016 option causes Alpine to skip directly to the Flag Details screen when the
28017 Flag command is used,
28018 setting it will cause this feature to have no effect at all.
28020 Similarly, when Selecting by Keyword, setting this option will allow you
28021 to use Keyword initials instead of full keywords.
28023 <End of help on this topic>
28026 ====== h_config_can_suspend =====
28029 <TITLE>FEATURE: <!--#echo var="FEAT_enable-suspend"--></TITLE>
28032 <H1>FEATURE: <!--#echo var="FEAT_enable-suspend"--></H1>
28034 Setting this feature will allow you to type ^Z (Control Z) to
28035 <!--chtml if pinemode="os_windows"-->
28036 minimize Alpine into its icon, bringing into focus whatever
28037 application is running behind the PC-Alpine window.
28039 temporarily suspend Alpine.
28042 This does not exit Alpine, but puts it in the background to watch
28043 for new mail and such. Normally, you type a command, such
28044 as "fg" at your system prompt to return to your Alpine session.
28047 The <A HREF="h_config_suspend_spawns"><!--#echo var="FEAT_use-subshell-for-suspend"--></A> feature
28048 adjusts whether Alpine is placed into the background of the shell its
28049 running in or starts a news shell.
28054 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28056 <End of help on this topic>
28059 ====== h_config_take_lastfirst ======
28062 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></TITLE>
28065 <H1>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></H1>
28067 Normally, when TakeAddr is used to copy an address from a message into
28068 an address book entry, Alpine will attempt to rewrite the full name of the
28069 address in the form
28072 Last, First<P>
28076 First Last
28079 It does this because many people find it useful to sort by Last name
28080 instead of First name. If this feature is set, then the TakeAddr command
28081 will not attempt to reverse the name in this manner.
28083 <End of help on this topic>
28085 ====== h_config_disable_regex ======
28088 <TITLE>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></TITLE>
28091 <H1>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></H1>
28094 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
28095 option is interpreted as a regular expression.
28096 One type of address that might cause trouble is an address that
28097 contains a plus sign.
28098 If you want to have an address with a plus as one of your
28099 <!--#echo var="VAR_alt-addresses"-->
28100 and you don't want to use regular expressions, then setting this
28101 feature will cause Alpine to treat the addresses you list literally instead.
28103 <End of help on this topic>
28105 ====== h_config_take_fullname ======
28108 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></TITLE>
28111 <H1>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></H1>
28113 Normally, when TakeAddr is used to copy an address or addresses
28114 from a message into an address book entry, Alpine will try to preserve
28115 the full name associated with each address in the list of addresses.
28116 The reason for this is so that if the entry is a list or later becomes a
28117 list, then information about the individual addresses in the list
28119 If you would rather just have the simple addresses in the list of addresses,
28120 set this feature. For example, with the default setting you might
28121 see something like this in the ADDRESS BOOK editor after you type TakeAddr
28125 Fullname : Bedrock Elders
28128 Addresses : Fred Flintstone <flint@bedrock.org>,
28129 Barney Rubble <rubble@bedrock.org>
28132 but with this feature set it would look like
28136 Fullname : Bedrock Elders
28139 Addresses : flint@bedrock.org,
28143 instead. Note the difference in the Addresses field.
28145 <End of help on this topic>
28147 ====== h_config_print_from ======
28150 <TITLE>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></TITLE>
28153 <H1>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></H1>
28155 If this feature is set, then the Berkeley-mail style From line is included
28156 at the start of each message that is printed. This line looks something
28157 like the following, with the address replaced by the address from the
28158 From line of the message being printed:
28160 From user@domain.somewhere.com Mon May 13
28163 <End of help on this topic>
28166 ====== h_config_expanded_distlists ======
28169 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></TITLE>
28172 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></H1>
28173 If this feature is set, then distribution lists in the address book
28174 screen will always be expanded automatically.
28176 <End of help on this topic>
28179 ====== h_config_compose_news_wo_conf ======
28182 <TITLE>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></TITLE>
28185 <H1>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></H1>
28186 This feature controls one aspect of Alpine's Composer. If you enter the
28187 composer while reading a newsgroup, you will normally be prompted to
28188 determine whether you intend the new message to be posted to the current
28189 newsgroup or not. If this feature is set, Alpine will not prompt you
28190 in this situation, and will assume that you do indeed wish to post
28191 to the newsgroup you are reading.
28193 <End of help on this topic>
28196 ====== h_config_compose_rejects_unqual ======
28199 <TITLE>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></TITLE>
28202 <H1>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></H1>
28204 This feature controls one aspect of the message composer; in particular,
28205 what happens when an unqualified name is entered into an address header.
28206 If set, unqualified names entered as addresses will be treated as errors
28207 unless they match an addressbook nickname. Alpine will not attempt to turn
28208 them into complete addresses by adding your local domain.<P>
28210 A complete (fully qualified) address is one containing a username followed
28211 by an "@" ("at") symbol, followed by a domain name (e.g.
28212 "jsmith@example.com"). An unqualified name is one <B>without</B>
28213 the "@" symbol and domain name (e.g. "jsmith").
28215 (See also <A HREF="h_address_format">Explanation of Address formats</A>.)
28219 When you enter a fully qualified address, Alpine does not interpret or
28220 modify it, but simply passes it on to the mail-transport-agent (MTA) for
28221 your system. Alpine conforms to the Internet standards governing message
28222 headers and will not send an unqualifed name to the MTA. Therefore, when
28223 you enter an unqualified name, Alpine will normally attempt to turn it into
28224 a fully qualified address, first by checking to see if you have entered a
28225 matching nickname in your addressbook, or failing that, by simply adding
28226 your own domain to the name entered. So if your address is
28227 "jsmith@example.com" and you enter "fred", then (assuming
28228 "fred" is not a nickname in your addressbook), Alpine will turn
28229 that into "fred@example.com".<P>
28231 There are situations where it is not desirable for Alpine to interpret such
28232 unqualified names as valid (local) addresses. For example, if "fred"
28233 turned out to be a typo (intended to be an addressbook nickname), but
28234 there actually was a "fred" in your local domain, the message might
28235 be mis-delivered without your realizing it. In order to reduce the likelihood
28236 of such accidents, setting this feature will cause Alpine to treat such
28237 addresses as errors, and require that you explicitly enter the full local
28238 address (e.g. "fred@example.com") or correct the name so that it
28239 matches an address book nickname.<P>
28241 Consider this a safety feature against mis-directed mail.
28244 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28246 <End of help on this topic>
28249 ====== h_config_quell_local_lookup ======
28252 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></TITLE>
28255 <H1>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></H1>
28257 This feature controls an aspect of Alpine's Composer, and if needed, will
28258 usually be set by your system manager in Alpine's system-wide configuration
28259 file. Specifically, if this feature is set, Alpine will not attempt to look
28260 in the system password file to find a Full Name for the entered address.
28262 Normally, names you enter into address fields (e.g. To: or Cc:) are
28263 checked against your address book(s) to see if they match an address book
28264 nickname. Failing that, (in Unix Alpine) the name is then checked against
28265 the Unix password file. If the entered name matches a username in the
28266 system password file, Alpine extracts the corresponding Full Name information
28267 for that individual, and adds that to the address being entered.
28269 However, password file matching can have surprising (incorrect) results if
28270 other users of the system do not receive mail at the domain you are using.
28271 That is, if either the
28272 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> or
28273 <A HREF="h_config_domain_name">"<!--#echo var="VAR_use-only-domain-name"-->"</A>
28275 is set such that the administrative domain of other users on the system
28276 isn't accurately reflected, Alpine should be told that a passwd file match
28277 is coincidental, and Full Name info will be incorrect. For example, a
28278 personal name from the password file could get falsely paired with the
28279 entered name as it is turned into an address in the configured domain.
28281 If you are seeing this behavior, enabling this feature will prevent Unix
28282 Alpine from looking up names in the password file to find the Full Name
28283 for incomplete addresses you enter.<P>
28285 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28288 <End of help on this topic>
28291 ====== h_config_tab_checks_recent ======
28294 <TITLE>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></TITLE>
28297 <H1>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></H1>
28299 In a FOLDER LIST screen, the TAB key usually just changes which
28300 folder is highlighted.
28301 If this feature is set, then the TAB key will cause the number of
28302 recent messages and the total number of messages in the highlighted folder
28303 to be displayed instead.
28306 <End of help on this topic>
28309 ====== h_config_maildrops_preserve_state ======
28312 <TITLE>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></TITLE>
28315 <H1>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></H1>
28317 This feature affects the way <A HREF="h_maildrop">Mail Drops</A> work.
28318 Normally, when mail is moved from a Mail Drop folder to a destination
28319 folder, it is delivered as new mail.
28320 Any Seen/New, Answered, Important/Flagged state that has changed will be
28322 All of the mail will be considered unSeen, unAnswered, and unImportant after
28325 If this feature is set, then the state changes that have been made
28326 to the messages in the Mail Drop folder will be preserved.
28328 In any case, messages that are already marked Deleted when the
28329 mail is to be moved from the Mail Drop will be ignored.
28331 <End of help on this topic>
28334 ====== h_config_preopen_stayopens ======
28337 <TITLE>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></TITLE>
28340 <H1>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></H1>
28342 This feature is related to the option
28343 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
28344 Normally, Stay Open folders are only opened on demand, when the user
28346 From then on they are kept open for the duration of the session.
28347 However, if this feature is set, then the Stay Open folders will all be
28348 opened at startup, at the same time that the INBOX is opened.
28351 <End of help on this topic>
28354 ====== h_config_expunge_inbox ======
28357 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></TITLE>
28360 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></H1>
28362 The INBOX is normally treated differently from regular folders in several
28364 One of the differences is that the normal "close" sequence of
28365 events is deferred until Alpine is exited, instead of happening when you
28366 leave the INBOX to view another folder.
28367 The "close" sequence normally includes the Expunging
28368 of deleted messages
28369 (either automatically or after a prompt, controlled by the features
28370 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
28371 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
28372 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
28374 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>.
28377 If this feature is set the "close" sequence handling will take
28378 place every time you leave the INBOX.
28379 The INBOX will still be kept open, but the offer to Expunge and the archiving
28380 to the <!--#echo var="VAR_read-message-folder"-->
28381 will take place each time you leave the INBOX instead of only once at the
28382 end of the session.
28385 <End of help on this topic>
28388 ====== h_config_expunge_stayopens ======
28391 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></TITLE>
28394 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></H1>
28396 This feature is related to the option
28397 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
28398 Stay Open folders are treated differently from regular folders in several
28400 One of the differences is that the normal "close" sequence of
28401 events is deferred until Alpine is exited, instead of happening when you
28402 leave the folder to view another folder.
28403 The "close" sequence normally includes the Expunging
28404 of deleted messages
28405 (either automatically or after a prompt, controlled by the features
28406 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
28407 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
28408 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
28410 <A HREF="h_config_archived_folders"><!--#echo var="VAR_incoming-archive-folders"--></A>.
28413 If this feature is set the "close" sequence handling will take
28414 place when you leave the Stay Open folder.
28415 The folder will still be kept open, but the offer to Expunge and the archiving
28416 will take place each time you leave the folder instead of only once at the
28417 end of the session.
28418 This feature does not affect the INBOX, which will still only be processed
28419 when you exit Alpine.
28420 However, there is a similar feature that affects only the INBOX called
28421 <A HREF="h_config_expunge_inbox">"<!--#echo var="FEAT_offer-expunge-of-inbox"-->"</A>.
28424 <End of help on this topic>
28427 ====== h_config_preserve_start_stop ======
28430 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></TITLE>
28433 <H1>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></H1>
28435 This feature controls how special control key characters, typically
28436 Ctrl-S and Ctrl-Q, are interpreted when input to Alpine. These characters
28437 are known as the "stop" and "start" characters and are sometimes used in
28438 communications paths to control data flow between devices that operate at
28443 By default, Alpine turns the system's handling of these special characters
28444 off except during printing. However, if you see Alpine reporting input errors
28447 [ Command "^Q" not defined for this screen.]
28449 and, at the same time, see your display become garbled, then it is likely
28450 that setting this option will solve the problem. Be aware, though, that
28451 enabling this feature will also cause Alpine to ostensibly "hang"
28452 whenever the Ctrl-S key combination is entered as the system is now
28453 interpreting such input as a "stop output" command. To "start
28454 output" again, simply type Ctrl-Q.
28456 <End of help on this topic>
28459 ====== h_config_enable_incoming ======
28462 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></TITLE>
28465 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></H1>
28467 Alpine's Incoming Message Folders collection
28468 provides a convenient way to access multiple incoming folders.
28469 It is also useful if you have accounts on multiple computers.
28472 If set, this feature defines a pseudo-folder collection called
28473 "INCOMING MESSAGE FOLDERS". Initially, the only folder included
28474 in this collection will be your INBOX, which will no longer show up in
28475 your Default folder collection.
28478 You may add more folders to the Incoming Message Folders collection by
28480 <!--chtml if pinemode="function_key"-->
28485 Add" command in the FOLDER LIST screen. You will be prompted for
28486 the host the folder is stored on (which defaults to the same host used
28487 for your INBOX), a nickname, and the actual folder name. Once a set
28488 of Incoming Message Folders are defined, the TAB key (in MESSAGE INDEX
28489 or MESSAGE TEXT screens) may be used to scan the folders for those
28490 with Recent messages. If you add more folders to
28491 your <!--#echo var="VAR_incoming-folders"--> collection, turning this feature back off will have
28494 NOTE: Normally the software that actually delivers mail (the stuff that happens
28495 before Alpine is involved) is in a better position to do delivery filtering
28496 than is Alpine itself.
28497 If possible, you may want to look at programs such as
28498 "filter" or "procmail", which are examples of delivery
28499 filtering programs.
28500 If you'd prefer to have Alpine do the filtering for you, you may set that
28502 Look <A HREF="h_rules_filter">here</A> for help with Alpine filtering.
28505 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28507 <End of help on this topic>
28510 ====== h_config_enable_incoming_checking ======
28513 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></TITLE>
28516 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></H1>
28518 This feature is only operational if you have enabled the optional
28519 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> collection.
28520 If you do have Incoming Message Folders and you also set this feature,
28521 then the number of Unseen messages in each folder will be displayed
28522 in the FOLDER LIST screen for the Incoming Message Folders.
28523 The number of Unseen messages in a folder will be displayed in parentheses
28524 to the right of the name of each folder.
28525 If there are no Unseen messages in a folder then only the name
28526 is displayed, not a set of parentheses with zero inside them.
28527 A redraw command, Ctrl-L, can be used in the FOLDER LIST screen for
28528 the Incoming Message Folders to cause an immediate update.
28530 If a check for Unseen messages fails for a particular folder then Alpine
28531 will no longer attempt to check that folder for the duration of the
28532 session and this will be indicated by a question mark inside the
28536 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>,
28537 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>,
28538 <A HREF="h_config_incoming_list"><!--#echo var="VAR_incoming-check-list"--></A>,
28539 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>,
28540 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>, and
28541 <A HREF="h_config_incoming_timeo"><!--#echo var="VAR_incoming-check-timeout"--></A>
28542 all affect how this feature behaves.
28545 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28547 <End of help on this topic>
28550 ====== h_config_incoming_checking_total ======
28553 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></TITLE>
28556 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></H1>
28558 This option has no effect unless the feature
28559 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
28560 is set, which in turn has no effect unless
28561 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28564 When incoming folder checking is turned on the default is to display
28565 the number of unseen messages in each folder.
28566 More precisely, it is the number of undeleted unseen messages.
28567 Using this option you may also display the total number of messages
28569 Instead of a single number representing the number of unseen messages
28570 you will get two numbers separated by a slash character.
28571 The first is the number of unseen messages and the second is the
28572 total number of messages.
28574 You may also use the recent message count instead of the unseen message
28575 count by turning on the feature
28576 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></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_incoming_checking_recent ======
28587 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></TITLE>
28590 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></H1>
28592 This option has no effect unless the feature
28593 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
28594 is set, which in turn has no effect unless
28595 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28598 When incoming folder checking is turned on the default is to display
28599 the number of unseen messages in each folder.
28600 More precisely, it is the number of undeleted unseen messages.
28601 Using this option you may display the number of recent messages instead
28602 of the number of unseen messages.
28603 A message is only counted as recent if this is the first session to
28604 see it, so the recent count might be less than the unseen count.
28605 The difference between the two would be accounted for by the unseen messages
28606 in the folder which were there previously but have not been looked at yet.
28608 If you simultaneously run more than one email client at a time
28609 (for example, you run more than one Alpine in parallel) then turning
28610 this feature on can cause some confusion.
28611 The confusion stems from the fact that each message is only considered to be
28612 recent in one session.
28613 That means that the counts of new messages may be different in the two
28614 Alpines running side by side, because each incoming message will only be
28615 counted as recent in one of the two sessions.
28617 You may also display the total number of messages
28618 in each folder by using the
28619 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
28623 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28625 <End of help on this topic>
28628 ====== h_config_attach_in_reply ======
28631 <TITLE>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></TITLE>
28634 <H1>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></H1>
28636 This feature controls an aspect of Alpine's Reply command. If set, any MIME
28637 attachments that were part of the original message will automatically be
28638 included in the Reply.
28640 <End of help on this topic>
28643 ====== h_config_include_header =====
28646 <TITLE>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></TITLE>
28649 <H1>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></H1>
28651 This feature controls an aspect of Alpine's Reply command. If set, and the
28652 original message is being included in the reply, then headers from that
28653 message will also be part of the reply.
28655 <End of help on this topic>
28658 ====== h_config_sig_at_bottom =====
28661 <TITLE>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></TITLE>
28664 <H1>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></H1>
28666 This feature controls an aspect of Alpine's Reply command. If this feature
28667 is set, and the original message is being included in the reply, then the
28668 contents of your signature file (if any) will be inserted after the included
28671 This feature does not affect the results of a Forward command.
28673 <End of help on this topic>
28676 ====== h_config_sigdashes =====
28679 <TITLE>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></TITLE>
28682 <H1>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></H1>
28684 This feature enables support for the common USENET news convention
28685 of preceding a message signature with the special line consisting of
28686 the three characters "-- " (i.e., dash, dash, and space).
28690 "<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>" exists,
28691 Alpine will insert the special line before including the file's text (unless
28692 the special line already exists somewhere in the file's text).
28695 In addition, when you Reply or Followup to a message containing one of
28696 these special lines and choose to include its text, Alpine will observe
28697 the convention of not including text beyond the special line in your
28699 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
28700 mode is enabled and turned on, then Alpine <EM>will</EM>
28701 include the text beyond the special line regardless of the setting of
28705 See also "<a href="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>"
28706 for a related feature.
28710 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28712 <End of help on this topic>
28715 ====== h_config_new_thread_blank_subject =====
28718 <TITLE>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></TITLE>
28721 <H1>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></H1>
28723 When this feature is enabled (the default) Alpine will create a new thread
28724 every time that the subject line becomes empty at any time during composition.
28727 This behavior is particularly useful in case you are replying to a message.
28728 Replying to a message causes the message to be in the same thread than the
28729 original message that is being replied to. However, many authors want to create
28730 a new message (in a different thread) while replying to a message, and they do
28731 this by changing the full subject, by first deleting the original subject and
28732 typing the new subject of the current message.
28735 Enabling this feature causes that any time that the subject is deleted, the
28736 message being composed will be considered the first message of a new thread.
28740 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28742 <End of help on this topic>
28745 ====== h_config_strip_sigdashes =====
28748 <TITLE>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></TITLE>
28751 <H1>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></H1>
28753 This feature doesn't do anything if the feature
28754 "<A HREF="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></A>" is turned on.
28755 However, if the "<!--#echo var="FEAT_enable-sigdashes"-->" feature is not turned on,
28756 then turning on this feature enables support for the convention
28757 of not including text beyond the sigdashes line when Replying or Following
28758 up to a message and including the text of that message.
28759 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
28760 mode is enabled and turned on, then Alpine <EM>will</EM>
28761 include the text beyond the special line regardless of the setting of
28764 In other words, this is a way to turn on the signature stripping behavior
28765 without also turning on the dashes-adding behavior.
28768 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28770 <End of help on this topic>
28773 ====== h_config_forward_as_attachment =====
28776 <TITLE>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></TITLE>
28779 <H1>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></H1>
28781 This feature affects the way forwarded message text is handled. When set, rather than
28782 include the text of the forwarded message below any additional text you provide in the
28783 composer, the forwarded message is attached in its entirety to the message you send.
28785 This is useful in that it keeps the text you provide in the composer distinct from the
28786 text of the forwarded message. Similarly, it allows the recipient to
28787 conveniently operate on the forwarded message. For example, they might reply directly to
28788 the sender of the forwarded message, or process it as part of a spam report.
28790 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28792 <End of help on this topic>
28795 ====== h_config_preserve_field =====
28798 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></TITLE>
28801 <H1>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></H1>
28803 This feature affects Alpine's behavior when one replies to a message.
28804 When you receive a message, some or all of the recipients of the message
28805 have been added to the To: and Cc: fields. If you reply to such message,
28806 and this feature is disabled, then the original sender of the message is
28807 added to the To: field, and all other recipients are added to the Cc:
28808 field, while your address is added to the From: field.
28811 However, if this feature is enabled, then Alpine will preserve the
28812 original fields as sent in the original message, so the Cc: and To:
28813 fields will be preserved. The sender's address will be added to the To:
28814 field, while your address is added to the From: field.
28817 The behavior of this feature is that replies to all messages will behave
28818 in the way described above. If you only intend this to happen on a per
28819 message basis, then keep this feature disabled, and when replying to a
28820 message you will see a new option in the menu for the "Reply to all
28821 recipients?" question. In this case, pressing "p" will
28822 make Alpine toggle its question so you can preserve the To: and Cc:
28823 fields for that message only.
28826 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28828 <End of help on this topic>
28831 ====== h_config_sub_lists =====
28834 <TITLE>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></TITLE>
28837 <H1>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></H1>
28839 This feature affects the subcommands available when Saving,
28840 or when Opening a new folder. If set, the subcommand ^X ListMatches will be
28841 available. This command allows you to type in a substring of the folder
28842 you are looking for and when you type ^X it will display all folders
28843 that contain that substring in their names.
28844 This feature is set by default.
28847 <End of help on this topic>
28850 ====== h_config_scramble_message_id =====
28853 <TITLE>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></TITLE>
28856 <H1>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></H1>
28858 Normally the Message-ID header that Alpine generates when sending a message
28859 contains the name of the computer from which the message is being sent.
28860 Some believe that this hostname could be used by spammers or could
28861 be used by others for nefarious purposes.
28862 If this feature is set, that name will be transformed with a simple
28863 Rot13 transformation.
28864 The result will still have the correct syntax for a Message-ID but the
28865 part of the MessageID that is often a domain name will not be an actual
28866 domain name because the letters will be scrambled.
28868 In addition, other information such as the name program, version, and
28869 a code for operating system used to build Alpine, will be encoded using
28870 the Rot13 transformation, except for the version number which will be
28871 encoded using a Rot5 transformation.
28873 It is possible (but unlikely?) that some spam detection
28874 software will use that as a reason to reject the mail as spam.
28875 It has also been reported that some spam detection software uses the
28876 fact that there are no dots after the "@" as a reason to reject
28878 If your PC-Alpine Message-ID is using a name without a dot that is because
28879 that is what Windows thinks is your "Full computer name".
28880 The method used to set this varies from one type of Windows to another but
28881 check under Settings -> Control Panel -> System and
28882 look for Network Identification or Computer Name or something similar.
28883 How to set it is beyond the scope of Alpine.
28886 <End of help on this topic>
28889 ====== h_downgrade_multipart_to_text =====
28892 <TITLE>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></TITLE>
28895 <H1>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></H1>
28898 This feature affects Alpine's behavior when sending mail. Internet
28899 standards require Alpine to translate all non-ASCII characters in
28900 messages that it sends using MIME encoding. This encoding can be
28901 ostensibly broken for recipients if any agent between Alpine and the
28902 recipient, such as an email list expander, appends text to the
28903 message, such as list information or advertising. When sending such
28904 messages Alpine attempts to protect such encoding by placing extra
28905 MIME boundaries around the message text.
28907 These extra boundaries are invisible to recipients that
28908 use MIME-aware email programs (the vast majority). However, if
28909 you correspond with users of email programs that are not MIME-aware,
28910 or do not handle the extra boundaries gracefully, you can
28911 use this feature to prevent Alpine from including the extra
28912 MIME information. Of course, it will increase the likelihood
28913 that non-ASCII text you send may appear corrupt to the recipient.
28915 <End of help on this topic>
28918 ====== h_config_show_sort =====
28921 <TITLE>FEATURE: <!--#echo var="FEAT_show-sort"--></TITLE>
28924 <H1>FEATURE: <!--#echo var="FEAT_show-sort"--></H1>
28926 If this feature is set and there is sufficient space on the screen,
28927 a short indication of the current sort order will be
28928 added in the titlebar (the top line on the screen), before the name
28930 For example, with the default Arrival sort in effect,
28931 the display would have the characters
28933 <P><CENTER>[A]</CENTER><P>
28935 added between the title of the screen and the folder name.
28936 The letters are the same as the letters you may type to manually
28937 sort a folder with the SortIndex command ($).
28938 The letters in the table below are the ones that may show
28939 up in the titlebar line.
28942 <TR> <TD> A </TD> <TD> <EM>A</EM>rrival </TD> </TR>
28943 <TR> <TD> S </TD> <TD> <EM>S</EM>ubject </TD> </TR>
28944 <TR> <TD> F </TD> <TD> <EM>F</EM>rom </TD> </TR>
28945 <TR> <TD> T </TD> <TD> <EM>T</EM>o </TD> </TR>
28946 <TR> <TD> C </TD> <TD> <EM>C</EM>c </TD> </TR>
28947 <TR> <TD> D </TD> <TD> <EM>D</EM>ate </TD> </TR>
28948 <TR> <TD> Z </TD> <TD> si<EM>Z</EM>e </TD> </TR>
28949 <TR> <TD> O </TD> <TD> <EM>O</EM>rderedsubject </TD> </TR>
28950 <TR> <TD> E </TD> <TD> scor<EM>E</EM> </TD> </TR>
28951 <TR> <TD> H </TD> <TD> t<EM>H</EM>read </TD> </TR>
28954 If the sort order is Reversed, the letter above will be preceded by the letter
28955 "R", for example
28957 <P><CENTER>[RS]</CENTER><P>
28959 means that a Reverse Subject sort is in effect.
28960 For the case where the sort is in Reverse Arrival order, the "A" is
28961 left out, and just an "R" is shown.
28963 <P><CENTER>[R]</CENTER>
28966 <End of help on this topic>
28969 ====== h_config_disable_reset_disp =====
28972 <TITLE>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></TITLE>
28975 <H1>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></H1>
28979 This feature affects Alpine's behavior when using
28980 <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>.
28981 Normally, before the display filter is run, the terminal mode is reset
28982 to what it was before you started Alpine.
28983 This may be necessary if the filter requires the use of the terminal.
28984 For example, it may need to interact with you.
28985 If you set this feature, then the terminal mode will not be reset.
28986 One thing that turning on this feature should fix is the coloring of
28987 <A HREF="h_config_quote_color">quoted text</A> in the message view, which
28988 breaks because the terminal reset resets the color state of the terminal.
28991 <End of help on this topic>
28994 ====== h_config_disable_sender =====
28997 <TITLE>FEATURE: <!--#echo var="FEAT_disable-sender"--></TITLE>
29000 <H1>FEATURE: <!--#echo var="FEAT_disable-sender"--></H1>
29002 This feature affects Alpine's generation of the "Sender:" or
29003 <A HREF="h_config_use_sender_not_x">"X-X-Sender"</A>
29005 By default, Alpine will generate such a header in situations where the
29006 username or domain are not the same as
29007 the "From:" header on the message.
29008 With this feature set,
29009 no "Sender:" or "X-X-Sender" header will be generated.
29010 This may be desirable on a system that is virtually hosting many domains,
29011 and the sysadmin has other methods available for tracking a message to
29014 See also <A HREF="h_config_allow_chg_from">"<!--#echo var="FEAT_allow-changing-from"-->"</A>.
29017 <End of help on this topic>
29020 ====== h_config_use_sender_not_x =====
29023 <TITLE>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></TITLE>
29026 <H1>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></H1>
29028 Normally Alpine adds a header line
29029 labeled "X-X-Sender", if the sender is
29030 different from the From: line.
29031 The standard specifies that this header
29032 line should be labeled "Sender", not "X-X-Sender".
29033 Setting this feature causes
29034 "Sender" to be used instead of "X-X-Sender".
29036 See also <A HREF="h_config_disable_sender">"<!--#echo var="FEAT_disable-sender"-->"</A>.
29039 <End of help on this topic>
29042 ====== h_config_use_fk =====
29045 <TITLE>FEATURE: <!--#echo var="FEAT_use-function-keys"--></TITLE>
29048 <H1>FEATURE: <!--#echo var="FEAT_use-function-keys"--></H1>
29050 This feature specifies that Alpine will respond to function keys instead of
29051 the normal single-letter commands. In this mode, the key menus at the
29052 bottom of each screen will show function key designations instead of the
29053 normal mnemonic key.
29056 <End of help on this topic>
29059 ====== h_config_cancel_confirm =====
29062 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></TITLE>
29065 <H1>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></H1>
29067 This feature affects what happens when you type ^C to cancel a composition.
29068 By default, if you attempt to cancel a composition by typing ^C, you will be
29069 asked to confirm the cancellation by typing a "C"
29070 for <EM>C</EM>onfirm.
29071 It logically ought to be a "Y" for <EM>Y</EM>es, but that is
29072 risky because the "^C Y" needed to cancel a message
29073 is close (on the keyboard) to the "^X Y" needed to send a message.
29075 If this feature is set the confirmation asked for
29076 will be a "<EM>Y</EM>es"
29077 instead of a "<EM>C</EM>onfirm" response.
29080 <End of help on this topic>
29083 ====== h_config_compose_maps_del =====
29086 <TITLE>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></TITLE>
29089 <H1>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></H1>
29091 This feature affects the behavior of the DELETE key.
29092 If set, Delete will be equivalent to ^D, and delete
29093 the current character. Normally Alpine defines the Delete key
29094 to be equivalent to ^H, which deletes the <EM>previous</EM>
29098 <End of help on this topic>
29101 ====== h_config_compose_bg_post =====
29104 <TITLE>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></TITLE>
29107 <H1>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></H1>
29109 This feature affects the behavior of Alpine's mail sending. If set, this
29110 feature enables a subcommand in the composer's "Send?" confirmation
29111 prompt. The subcommand allows you to tell Alpine to handle the actual
29112 posting in the background. While this feature usually allows posting
29113 to appear to happen very fast, it has no affect on the actual delivery
29114 time it takes a message to arrive at its destination.
29119 <LI>This feature will have no effect if the feature
29120 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A>
29122 <LI>This feature isn't supported on all systems. All DOS and Windows,
29123 as well as several Unix ports, do not recognize this feature.
29124 <LI>Error handling is significantly different when this feature is
29125 enabled. Any message posting failure results in the message
29126 being appended to your "Interrupted" mail folder. When you
29127 type the <A HREF="h_common_compose">C</A>ompose command,
29128 Alpine will notice this folder and
29129 offer to extract any messages contained. Upon continuing a
29130 failed message, Alpine will display the nature of the failure
29131 in the status message line.
29132 <LI> <EM>WARNING</EM>: Under extreme conditions, it is possible
29133 for message data to
29134 get lost. <EM>Do</EM> <EM>not</EM> enable this feature
29135 if you typically run close to any sort of disk-space limits or quotas.
29138 <End of help on this topic>
29141 ====== h_config_compose_dsn =====
29144 <TITLE>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></TITLE>
29147 <H1>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></H1>
29149 This feature affects the behavior of Alpine's mail sending. If set, this
29150 feature enables a subcommand in the composer's "Send?" confirmation
29151 prompt. The subcommand allows you to tell Alpine to request the type of
29152 Delivery Status Notification (DSN) that you would like. Most users will
29153 be happy with the default, and need not enable this feature.
29156 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
29157 then this feature has no effect and the type of DSN is not selectable.
29160 Turning on this feature and then turning on the DSNOpts from the send
29161 prompt reveals four on-off toggles at the bottom of the screen.
29162 The "X" command toggles between NoErrRets and ErrRets. NoErrRets requests
29163 that no notification be returned to you, even if there is a delivery
29164 failure. The "D" key toggles between Delay and NoDelay. This tells the
29165 server that you are willing (or not) to receive delay notifications, which
29166 happen when there is an unusual delay at some mail server (in that mail
29167 server's opinion). The "S" key toggles between Success and NoSuccess.
29168 Success requests that you be sent a DSN message when the message is
29169 successfully delivered to the recipients mailbox. Setting NoErrRets will
29170 automatically turn off Delay and Success notification, and will flip the
29171 toggles to show that. Similarly, turning on Delay and/or Success will
29172 automatically toggle the "X" key to ErrRets. The fourth command, the
29173 "H" key, toggles between RetHdrs and RetFull. RetFull requests that
29174 the full message be returned in any failed DSN. RetHdrs requests that
29175 only the headers be returned in any failed DSN. Notice that this command
29176 applies only to failed delivery status reports. For delay or success
29177 reports, the full message is never returned, only the headers are returned.
29180 If you don't enable the DSN feature or if you don't turn it on for a
29181 particular message, the default is that you will be notified about failures,
29182 you might be notified about delays, and you won't be notified about
29183 successes. You will usually receive the full message back when there is
29187 If you turn on the DSNOpts the default is to return as much information as
29188 possible to you. That is, by default, the Success and Delay options are
29189 turned on and the full message will be returned on failure.
29192 The sending prompt will display the current DSN request (if any) in a
29193 shorthand form. It will be:
29195 <P><CENTER>[Never]</CENTER>
29198 if you have requested NoErrRets. Otherwise, it will look something like:
29200 <P><CENTER>[FDS-Hdrs]</CENTER>
29203 The "F" will always be there, indicating that you will be notified
29204 of failures. (Alpine doesn't provide a way to request no failure notification
29205 and at the same time request either success or delay notification. The only
29206 way to request no failure notifications is to request no notifications at
29207 all with NoErrRets.) The "D" and/or "S" will be present if you have
29208 requested Delay and/or Success notification. If one of those is missing,
29209 that means you are requesting no notification of the corresponding type.
29210 After the dash it will say either Hdrs or Full. Hdrs means to return only
29211 the headers and Full means to return the full message (applies to
29212 failure notifications only).
29215 NOTE: This feature relies on your system's mail transport agent or
29217 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
29218 having the negotiation mechanism introduced in
29219 "Extended SMTP" (ESMTP) and the specific extension called
29220 "Delivery Status Notification" (DSN). If the mail tranport agent you
29221 are using doesn't support DSN, a short warning will be shown to you on
29222 the message line at the bottom of the screen after you send your message,
29223 but your message will have been sent anyway.
29226 Note that DSNs don't provide a mechanism to request read receipts. That
29227 is, if you request notification on success you are notified when the
29228 message is delivered to the mailbox, not when the message is read.
29231 ESMTP allows for graceful migration to upgraded mail transfer agents, but
29232 it is possible that this feature might cause problems for some servers.
29235 <End of help on this topic>
29238 ====== h_config_auto_zoom =====
29241 <TITLE>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></TITLE>
29244 <H1>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></H1>
29246 This feature affects the behavior of the Select command.
29247 If set, the select command will automatically perform a zoom
29248 after the select is complete.
29249 This feature is set by default.
29251 Some related help topics are
29253 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
29254 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
29255 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
29256 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
29257 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
29258 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
29262 <End of help on this topic>
29265 ====== h_config_auto_unzoom =====
29268 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></TITLE>
29271 <H1>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></H1>
29273 This feature affects the behavior of the Apply command. If set, and if
29274 you are currently looking at a Zoomed Index view of selected messages,
29275 the Apply command will do the operation you specify, but then will
29276 implicitly do an "UnZoom", so that you will automatically be back in
29277 the normal Index view after the Apply.
29278 This feature is set by default.
29281 Some related help topics are
29283 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
29284 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
29285 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
29286 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
29287 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
29288 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
29291 <End of help on this topic>
29294 ====== h_config_auto_unselect =====
29297 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></TITLE>
29300 <H1>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></H1>
29302 This feature affects the behavior of the Apply command. If set,
29303 the Apply command will do the operation you specify, but then will
29304 implicitly do an "UnSelect All", so that you will automatically be back in
29305 the normal Index view after the Apply.
29308 Some related help topics are
29310 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
29311 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
29312 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
29313 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
29314 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
29315 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
29318 <End of help on this topic>
29321 ====== h_config_fast_recent =====
29324 <TITLE>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></TITLE>
29327 <H1>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></H1>
29329 This feature controls the behavior of the TAB key when traversing folders
29331 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
29332 collection or in optional <!--#echo var="VAR_news-collections"-->.
29336 (<A HREF="h_common_nextnew">NextNew</A>)
29337 key is pressed, the default behavior is to
29338 explicitly examine the status of the folder for the number of recent
29339 messages (messages delivered since the last time it was viewed).
29340 Depending on the size and number of messages in the folder, this test
29341 can be time consuming.
29344 Enabling this feature will cause Alpine to only test for the existence of
29345 any recent messages rather than to obtain the count. This is much faster
29346 in many cases. The downside is that you're not given the number of recent
29347 messages when prompted to view the next folder.
29349 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
29350 is turned on, then the present feature will have no effect.
29354 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29356 <End of help on this topic>
29359 ====== h_config_arrow_nav =====
29362 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></TITLE>
29365 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></H1>
29367 This feature controls the behavior of the left and right arrow keys.
29368 If set, the left and right arrow keys will operate like the usual
29369 navigation keys < and >.
29370 This feature is set by default.
29373 If you set this feature, and do not like the changed behavior of the up/down
29375 keys when navigating through the FOLDER LIST screen --
29376 <B>first</B> from column to column, if more than one folder is
29378 and <B>then</B> from row to row -- you may either also wish to set the feature
29379 "<A HREF="h_config_relaxed_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></A>",
29380 "<A HREF="h_config_single_list"><!--#echo var="FEAT_single-column-folder-list"--></A>", or
29381 use the ^P/^N (instead of up/down arrow) keys to move up/down the list of
29382 folders in each column.
29385 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29387 <End of help on this topic>
29390 ====== h_config_relaxed_arrow_nav =====
29393 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></TITLE>
29396 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></H1>
29398 This feature controls the behavior of the left, right, up and down
29399 arrow keys in the FOLDER LIST screen when the "<A
29400 HREF="h_config_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation"--></A>" feature is
29402 This feature is set by default.
29406 When this feature is set, the left and right
29407 arrow keys in the FOLDER LIST screen
29408 move the highlight bar to the left or right, and the up and
29409 down arrows move it up or down.
29412 When the "<!--#echo var="FEAT_enable-arrow-navigation"-->" feature is set and this
29413 feature is not set;
29414 the left and right arrow keys in the Folder List screen strictly
29415 track the commands bound to the '<' and '>' keys, and the up
29416 and down arrow keys move the highlight bar to the previous and next
29417 folder or directory name.
29421 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29423 <End of help on this topic>
29426 ====== h_config_alt_compose_menu =====
29429 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></TITLE>
29432 <H1>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></H1>
29434 This feature controls the menu that is displayed when Compose is selected.
29435 If set, a list of options will be presented, with each option representing
29436 the type of composition that could be used. This feature is most useful for
29437 users who want to avoid being prompted with each option separately, or who
29438 want to avoid the checking of remote postponed or form letter folders.
29439 The possible types of composition are:
29442 New, for starting a new composition. Note that if New is selected and roles
29443 are set, roles are checked for matches and applied according to the setting
29444 of the matching role.
29447 Interrupted, for continuing an interrupted composition. This option is only
29448 offered if an interrupted message folder is detected.
29451 Postponed, for continuing postponed compositions. This option is offered
29452 if a <!--#echo var="VAR_postponed-folder"--> is set in the config REGARDLESS OF whether or not
29453 the postponed folder actually exists. This option is especially handy
29454 for avoiding having to check for the existence of a remote postponed folder.
29457 Form, for using form letters. This option is offered if the <!--#echo var="VAR_form-letter-folder"-->
29458 is set in the config, and is not checked for existence for reasons similar
29459 to those explained by the postponed option.
29462 setRole, for selecting a role to apply to a composition.
29465 <End of help on this topic>
29468 ====== h_config_alt_role_menu =====
29471 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></TITLE>
29474 <H1>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></H1>
29476 Normally the <A HREF="h_common_role">Role Command</A> allows you to choose
29477 a role and compose a new message using that role.
29478 When this feature is set, the role command will first ask whether you want to
29479 Compose a new message, Forward the current message, Reply to the
29480 current message, or Bounce the current message.
29481 If you are not in the MESSAGE INDEX and are not viewing a message,
29482 then there is no current message and the question will be skipped.
29483 After you have chosen to Compose, Forward, Reply, or Bounce you will
29484 then choose the role to be used.
29486 When Bouncing the "Set From" address is used for the
29487 Resent-From header, the "Set Fcc" value is used for the Fcc
29488 provided that the option
29489 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A> is turned on,
29490 and the "Use SMTP Server" value is used for the SMTP server, if
29492 Other actions of the role are ignored when Bouncing.
29495 <End of help on this topic>
29498 ====== h_config_always_spell_check =====
29501 <TITLE>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></TITLE>
29504 <H1>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></H1>
29506 When this feature is set, every composed message will be spell-checked before
29509 <End of help on this topic>
29512 ====== h_config_quell_asterisks =====
29515 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></TITLE>
29518 <H1>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></H1>
29520 When you are running Alpine you will sometimes be asked for a password
29521 in a prompt on the third line from the bottom of the screen.
29522 Normally each password character you type will cause an asterisk to echo
29523 on the screen. That gives you some feedback to know that your typing is
29525 There is a very slight security risk in doing it this way because someone
29526 watching over your shoulder might be able to see how many characters there
29527 are in your password.
29528 If you'd like to suppress the echoing of the asterisks set this feature.
29530 <End of help on this topic>
29533 ====== h_config_quell_flowed_text =====
29536 <TITLE>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></TITLE>
29539 <H1>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></H1>
29541 Alpine generates flowed text where possible.
29542 The method for generating flowed text is defined by
29543 <A HREF="http://www.ietf.org/rfc/rfc3676.txt">RFC 3676</A>,
29544 the benefit of doing so is
29545 to send message text that can properly be viewed both on normal width displays
29546 and on displays with smaller or larger than normal screen widths.
29547 With flowed text, a space at the end of a line tells the receiving mail
29548 client that the following line belongs to the same paragraph.
29549 Quoted text will also be affected, with only the innermost
29550 level of ">" quoting being followed by a space.
29551 However, if you have changed the
29552 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29553 so that it is not equal to the default value of "> ", then
29554 quoted text will not be flowed.
29555 For this reason, we recommend that you leave your
29556 "<!--#echo var="VAR_reply-indent-string"-->" set to the default.
29558 This feature turns off the generation of flowed text, as it might be
29559 desired to more tightly control how a message is displayed on the receiving end.
29561 If this feature is <EM>not</EM> set, you can control on a message by message
29562 basis whether or not flowed text is generated.
29563 You do this by typing ^V at the Send confirmation prompt that you get
29564 after typing ^X to send a message.
29565 ^V is a toggle that turns flowing off and back on if typed again.
29566 If for some reason flowing cannot be done on a particular message, then the
29567 ^V command will not be available.
29568 This would be the case, for example, if this feature was set, or if your
29569 "<!--#echo var="VAR_reply-indent-string"-->" was set to a non-default value.
29571 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
29572 then the opportunity to control on a message by message basis
29573 whether or not flowed text is generated is lost.
29575 When this feature is not set and you have typed ^V to turn off flowing,
29576 the Send confirmation prompt will change to look like
29578 <CENTER><SAMP>Send message (not flowed)?</SAMP></CENTER>
29580 <A HREF="h_config_strip_ws_before_send">"<!--#echo var="FEAT_strip-whitespace-before-send"-->"</A> will
29581 also turn off the sending of flowed text messages, but it differs in that
29582 it also trims all trailing white space from a message before sending it.
29584 If alternate editors are used extensively, be aware that a message will still
29585 be sent flowed if this feature is unset. In most cases this will be fine,
29586 but if the editor has a "flowed text" mode, it would be best to
29589 <End of help on this topic>
29592 ====== h_config_strip_ws_before_send =====
29595 <TITLE>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></TITLE>
29598 <H1>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></H1>
29600 By default, trailing whitespace is not stripped from
29601 a message before sending. Trailing whitespace should have no effect on an
29602 email message, and in flowed text can aid in delimiting paragraphs.
29603 However, the old behavior of stripping trailing whitespace was in place
29604 to better deal with older clients that couldn't handle certain types of
29605 text encodings. This feature restores the old behavior
29607 Trailing whitespace is of aid to flowed-text-formatted messages, which are
29608 generated by default but can be turned off via the
29609 <A HREF="h_config_quell_flowed_text">"<!--#echo var="FEAT_quell-flowed-text"-->"</A> feature.
29610 <!--#echo var="FEAT_strip-whitespace-before-send"--> also has the effect of turning off sending
29613 <End of help on this topic>
29616 ====== h_config_alt_reply_menu =====
29619 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></TITLE>
29622 <H1>FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></H1>
29624 Note that if this option is enabled, then the option
29625 <A HREF="h_config_auto_include_reply"><!--#echo var="FEAT_include-text-in-reply"--></A>
29626 is ignored. See below to understand why.
29628 When you reply to a message, a series of questions are asked that
29629 determines how your reply will be handled by Alpine. This feature only
29630 affects the result of the first question you are asked, and its purpose is
29631 to set values that could override defaults set in Alpine's main
29632 configuration screen. As a result, this menu allows you to configure even
29633 more features than you would be able to do without this option. For
29634 example, this menu always allows you to override or select a <A
29635 HREF="h_rules_roles">Role</A> if you have defined one, or allows you to
29636 override your indent string, regardless of if you have enabled
29637 <A HREF="h_config_prefix_editing"><!--#echo var="FEAT_enable-reply-indent-string-editing"--></A>.
29638 The full list of options can be found below.
29640 Here is an example of how this option works. After you press Reply,
29641 if you see "A Inc Attach" in the menu, it means that
29642 if you press "A", then Alpine will include the attachments
29643 of the original message, and the default is not to include them.
29644 Conversely, if you see "A No Attach"
29645 then by pressing "A" Alpine will not include
29646 attachments in your reply, and the default is that Alpine will
29647 include them in your reply. The value that you see when you
29648 start your reply is controlled by the option
29649 <A HREF="h_config_attach_in_reply">
29650 <!--#echo var="FEAT_include-attachments-in-reply"-->
29651 </A>. If the feature is enabled, then Alpine will display
29652 "A No Attach" to override the default behavior. You can
29653 toggle between the two values of this option by pressing "A".
29654 Remember that the value that you see in the menu is the action that will
29655 be done when you press the associated command.
29657 Below are your options:
29659 <LI><B>A</B>: This determines if Alpine will include or not the
29660 attachments sent to you in the message that you are replying to. The default
29661 is to use the value of the configuration option
29662 <A HREF="h_config_attach_in_reply"><!--#echo var="FEAT_include-attachments-in-reply"--></A> and can be overriden by using this command.
29664 <LI><B>H</B>: This command determines if the headers of a message are
29665 included in the body of the message that is being replied to. By default
29666 Alpine will use the value of the configuration option
29667 <A HREF="h_config_include_header"><!--#echo var="FEAT_include-header-in-reply"--></A>.
29668 Observe that by toggling this option to include headers, text will be toggled
29669 to be included by default.
29671 <LI><B>R</B>: Can be used to set a role different from the default.
29673 <LI><B>S</B>: Determines if Alpine will strip the signature from a
29674 message. The default is to strip the signature when the message is not
29675 viewed in headers mode, and you either have enabled
29676 <A HREF="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></A>
29678 <A HREF="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></A>.
29680 <LI><B>Ctrl-R</B>: Can be used to edit the
29681 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>.
29684 In order to include the text of the original message in the reply
29685 you either need to press 'y' to include the original text, or 'n' to
29686 exclude it from the reply. Pressing return will execute the default
29687 action, which is to include text only if the option
29688 <A HREF="h_config_auto_include_reply"><!--#echo var="FEAT_include-text-in-reply"--></A>
29689 is enabled. However, notice that the default is to include text if you edit the
29690 reply indent string or if you explicitly set through this menu that you
29691 want headers included in the reply message.
29694 <End of help on this topic>
29697 ====== h_config_del_from_dot =====
29700 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></TITLE>
29703 <H1>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></H1>
29705 This feature controls the behavior of the Ctrl-K command in the composer.
29706 If set, ^K will cut from the current cursor position to the end of the line,
29707 rather than cutting the entire line.
29710 <End of help on this topic>
29713 ====== h_config_print_index =====
29716 <TITLE>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></TITLE>
29719 <H1>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></H1>
29721 This feature controls the behavior of the Print command when in the
29722 MESSAGE INDEX screen. If set, the print command will give you a prompt
29723 asking if you wish to print the message index, or the currently highlighted
29724 message. If not set, the message will be printed.
29727 <End of help on this topic>
29730 ====== h_config_allow_talk =====
29733 <TITLE>FEATURE: <!--#echo var="FEAT_allow-talk"--></TITLE>
29736 <H1>FEATURE: <!--#echo var="FEAT_allow-talk"--></H1>
29740 By default, permission for others to "talk" to your terminal is turned
29741 off when you are running Alpine. When this feature is set, permission is
29742 instead turned on. If enabled, you may see unexpected messages in the
29743 middle of your Alpine screen from someone attempting to contact you via the
29744 "talk" program.
29747 NOTE: The "talk" program has nothing to do with Alpine or email. The
29748 talk daemon on your system will attempt to print a message on your screen
29749 when someone else is trying to contact you. If you wish to see these
29750 messages while you are running Alpine, you should enable this feature.
29753 If you do enable this feature and see a "talk" message, you must
29754 suspend or quit Alpine before you can respond.
29757 <End of help on this topic>
29760 ====== h_config_send_filter_dflt =====
29763 <TITLE>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></TITLE>
29766 <H1>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></H1>
29767 If you have <A HREF="h_config_sending_filter">"<!--#echo var="VAR_sending-filters"-->"</A>
29768 configured, setting this feature will cause
29769 the first filter in the <!--#echo var="VAR_sending-filters"--> list to be offered as the default
29770 instead of unfiltered, the usual default.
29773 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29775 <End of help on this topic>
29778 ====== h_config_custom_print =====
29781 <TITLE>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></TITLE>
29784 <H1>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></H1>
29786 When this feature is set, the print command will have an additional
29787 subcommand called "C CustomPrint". If selected, you will have
29788 the opportunity to enter any system print command --instead of being
29789 restricted to using those that have been previously configured in the
29790 printer setup menu.
29793 <End of help on this topic>
29796 ====== h_config_enable_dot_files =====
29799 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></TITLE>
29802 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></H1>
29804 When this feature is set, files beginning with dot (".") will be
29805 visible in the file browser. For example, you'll be able to select them
29806 when using the browser to add an attachment to a message.
29808 <End of help on this topic>
29811 ====== h_config_enable_dot_folders =====
29814 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></TITLE>
29817 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></H1>
29819 When this feature is set, folders beginning with dot (".") may be added
29822 <End of help on this topic>
29825 ====== h_config_ff_between_msgs =====
29828 <TITLE>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></TITLE>
29831 <H1>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></H1>
29833 Setting this feature causes a formfeed to be printed between messages when
29834 printing multiple messages (with Apply Print command).
29836 <End of help on this topic>
29839 ====== h_config_blank_keymenu =====
29842 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></TITLE>
29845 <H1>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></H1>
29847 If this feature is set the command key menu that normally appears on the
29848 bottom two lines of the screen will not usually be there. Asking for
29849 help with ^G or ? will cause the key menu to appear instead of causing
29850 the help message to come up. If you want to actually see the help text,
29851 another ^G or ? will show it to you. After the key menu has popped
29852 up with the help key it will remain there for an O for Other command but
29853 disappear if any other command is typed.
29855 <End of help on this topic>
29858 ====== h_config_enable_mouse =====
29861 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></TITLE>
29864 <H1>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></H1>
29866 This feature controls whether or not an X terminal mouse can be used with
29867 Alpine. If set, and the $DISPLAY variable indicates that an X terminal is
29868 being used, the left mouse button on the mouse can be used to select text
29870 Clicking on a command at the bottom of the screen will behave as if you had
29871 typed that command.
29872 Clicking on an index line will move the current message highlight to
29874 Double-clicking on an index line will view the message.
29875 Double-clicking on a link will view the link.
29877 This type of mouse support will also work in some terminal emulators which are
29878 not actually X terminals, but which have extra code to support the xterm
29880 For those emulators you not only need to turn this feature on but you also
29881 have to set the $DISPLAY environment variable even though it isn't needed
29883 That will cause Alpine to think that it is an xterm and to properly interpret the
29884 escape sequences sent by the mouse.
29886 Note: if this feature is set, the behavior of X terminal cut-and-paste is
29887 also modified. It is sometimes possible to hold the shift key down while clicking
29888 left or middle mouse buttons for the normal xterm cut/paste operations.
29889 There is also an Alpine command to toggle this mode on or off.
29890 The command is Ctrl-\ (Control-backslash).
29892 <End of help on this topic>
29895 ====== h_config_enable_xterm_newmail =====
29898 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></TITLE>
29901 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></H1>
29903 This feature controls whether or not Alpine will attempt to announce new
29904 mail arrival when it is running in an X terminal window and that window
29905 is iconified. If set, and the $DISPLAY variable indicates that an X
29906 terminal is being used, Alpine will send appropriate escape sequences to
29907 the X terminal to modify the label on Alpine's icon to indicate that new
29908 mail has arrived. Alpine will also modify the Alpine window's title to
29910 See also <a href="h_config_enable_newmail_short_text"><!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>.
29912 <End of help on this topic>
29914 ====== h_config_enable_newmail_short_text =====
29917 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></TITLE>
29920 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></H1>
29922 This feature controls the text to be displayed in an icon in the event
29923 of a new message arrival. Normally, the message will
29924 be the one that is displayed on the screen. This feature shortens the
29925 message to a count of the number of new messages in brackets. This may be
29926 more useful for those who use the window's title bar in the task bar as a
29927 new mail indicator. This feature is only useful if the
29928 <A HREF="h_config_enable_xterm_newmail"><!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></A>
29929 feature is also set. Like the <!--#echo var="FEAT_enable-newmail-in-xterm-icon"-->
29930 feature, this feature is only relevant when run in an xterm environment.
29932 <End of help on this topic>
29934 ====== h_config_copy_to_to_from =====
29937 <TITLE>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></TITLE>
29940 <H1>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></H1>
29942 This feature affects the From address used when Replying to a message.
29943 It is probably only useful if you have some
29944 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
29946 When enabled, it checks to see if any of the addresses in the To or Cc
29947 fields of the message you are replying to is one of your addresses.
29948 If it is, and there is only one of them, then that address is used as
29949 the From address in the message you are composing.
29950 In other words, you will be using a From address that is the same
29951 as the To address that was used to get the mail to you in the first place.
29954 If a role is being used and it has a From address defined, that From address will
29955 be used rather than the one derived from this feature.
29959 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29961 <End of help on this topic>
29964 ====== h_config_prefix_editing =====
29967 <TITLE>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></TITLE>
29970 <H1>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></H1>
29972 This feature affects the Reply command's "Include original message
29973 in Reply?" prompt. When enabled, it causes the
29974 "Edit Indent String" sub-command to appear which allows
29975 you to edit the string Alpine would otherwise use to denote included
29976 text from the message being replied to.<P>
29978 Thus, you can change Alpine's default message quote character (usually
29979 an angle bracket) on a per message basis. So you could change your quoted message to
29980 look, for example, like this:<p>
29982 <pre>On Tues, 26 Jan 1999, John Q. Smith wrote:
29984 John: I just wanted to say hello and to congratulate you
29985 John: on a job well done!</pre><p>
29987 The configuration option
29988 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29989 may be used to change what appears as the default string to be edited.
29991 NOTE: Edited <!--#echo var="VAR_reply-indent-string"--> only apply to the message
29992 currently being replied to.
29994 If you change your <!--#echo var="VAR_reply-indent-string"-->
29995 so that it is not equal to the default value of "> ", then
29996 quoted text will not be flowed
29997 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
29999 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
30000 set to the default value.
30003 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30005 <End of help on this topic>
30008 ====== h_config_enable_search_and_repl =====
30011 <TITLE>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></TITLE>
30014 <H1>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></H1>
30016 This feature modifies the behavior of Alpine's composer. Setting this
30017 feature causes Alpine to offer the "^R Replace" subcommand, which
30018 allows you to search and replace text strings in a message you are composing,
30019 inside the "^W Where is" command.
30023 To search and replace text, first enter the text to be replaced at the
30024 "Search: " prompt. Then, rather than pressing Enter to just search for that
30025 text, press ^R, which turns the prompt into
30029 Search (to replace):
30033 and then press Enter. The cursor will highlight the first occurrence
30034 of the text string you entered, and the prompt will show:
30038 Replace "<your text string>" with :
30042 where <your text string> is what you entered at the previous prompt;
30043 here, enter the replacement text. To only replace the highlighted
30044 occurrence, simply press Enter now; to replace all occurrences in the
30045 message, press ^X (Repl All), then Enter. You will then be asked to confirm
30050 The command ^R toggles between "Replace" and "Don't Replace"; its subcommand
30051 ^X toggles between "Replace All" and "Replace One."
30055 If you previously searched for text in a message, it will be offered for
30056 re-use as part of the prompt, shown in [ ] brackets.
30059 <End of help on this topic>
30062 ====== h_config_enable_view_attach =====
30065 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></TITLE>
30068 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></H1>
30070 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
30071 Setting this feature causes Alpine to present attachments in boldface.
30072 The first available attachment is displayed in inverse. This is the
30073 "selected" attachment. Pressing RETURN will cause Alpine to display
30074 the selected attachment. Use the arrow keys to change which of the
30075 attachments displayed in boldface is the current selection.
30079 Speaking of arrow keys, the Up and Down Arrows will select the next
30080 and previous attachments if one is available on the screen for selection.
30081 Otherwise, they will simply adjust the viewed text one line up or down.
30085 Similarly, when selectable items are present in a message, the Ctrl-F key
30086 can be used to select the next item in the message independent of which
30087 portion of the viewed message is currently displayed. The Ctrl-B key can
30088 be used to select the previous item in the same way.
30090 <End of help on this topic>
30093 ====== h_config_enable_y_print =====
30096 <TITLE>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></TITLE>
30099 <H1>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></H1>
30101 This feature modifies the behavior of Alpine's Print command.
30103 By default, Alpine's print command is available by pressing the "%" key.
30104 (This command is a substantial change from Pine versions before 4.00 --
30105 where the print command was "Y" -- based on numerous complaints about
30106 printing being invoked inadvertently, since Y also means "Yes.")
30110 This feature is supplied to mitigate any disruption or anxiety users
30111 might feel as a result of this change.
30115 Enabling this feature will cause Alpine to recognize both the old
30116 command, "Y" for Prynt, as well the new "%" method for invoking
30117 printing. Note, key menu labels are not changed as a result of
30118 enabling this feature.
30122 <End of help on this topic>
30125 ====== h_config_enable_lessthan_exit =====
30128 <TITLE>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></TITLE>
30131 <H1>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></H1>
30133 If this feature is set, then on screens where there is an Exit command
30134 but no < command, the < key will perform the same function as the Exit
30136 This feature is set by default.
30138 <End of help on this topic>
30141 ====== h_config_enable_view_url =====
30144 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></TITLE>
30147 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></H1>
30148 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
30149 When this feature is set (the default) Alpine will select possible URLs from the
30150 displayed text and display them in boldface for selection.
30152 The first available URL is displayed in inverse. This is the
30153 "selected" URL. Pressing RETURN will cause Alpine to display
30154 the selected URL via either built-in means as with mailto:, imap:,
30155 news:, and nntp:, or via an external application as defined
30156 by the <A HREF="h_config_browser">"url-viewer"</A>
30159 Use the arrow keys to change which of the URLs displayed in boldface
30160 is the current selection.
30162 Speaking of arrow keys, the Up and Down Arrows will select the next
30163 and previous URL if one is available on the screen for selection (unless
30164 you have set the feature
30165 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
30166 Otherwise, they will simply adjust the viewed text one line up or down.
30168 Similarly, when selectable items are present in a message, the Ctrl-F
30169 key can be used to select the next item in the message independent
30170 of which portion of the viewed message is currently displayed. The
30171 Ctrl-B key can be used to select the previous item in the same way.
30174 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30176 <End of help on this topic>
30179 ====== h_config_enable_view_web_host =====
30182 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></TITLE>
30185 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></H1>
30187 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
30188 When this feature is set (the default) Alpine will select possible web hostnames
30189 from the displayed text and display them in boldface for selection.
30190 This can be useful when you receive messages referencing World Wide Web
30191 sites without the use of complete URLs; for example, specifying only
30192 "www.some.site.com" (which will <B>not</B> become a
30194 item by setting <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>)
30195 rather than explicitly
30196 "http://www.some.site.com".
30198 The first available hostname is displayed in inverse. This is the
30199 "selected" hostname. Pressing RETURN will cause Alpine to display
30200 the selected hostname via an external application as defined
30201 by the <A HREF="h_config_browser">"url-viewer"</A>
30204 Use the arrow keys (unless you have set the feature
30205 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
30206 to change which of the hostnames displayed in
30207 boldface is the current selection.
30209 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
30210 key can be used to select the next web hostname in the message independent
30211 of which portion of the viewed message is currently displayed. The
30212 Ctrl-B key can be used to select the previous web hostnames in the same way.
30215 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30217 <End of help on this topic>
30220 ====== h_config_enable_view_addresses =====
30223 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></TITLE>
30226 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></H1>
30228 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
30229 Setting this feature causes Alpine to select possible email addresses
30230 from the displayed text and display them in boldface for selection.
30233 The first available email address is displayed in inverse. This is the
30234 "selected" address. Pressing RETURN will cause Alpine to enter
30235 the message composition screen with the To: field filled in with the
30238 Use the arrow keys (unless you have set the feature
30239 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
30240 to change which of the hostnames displayed in
30241 boldface is the current selection.
30243 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
30244 key can be used to select the next web hostname in the message independent
30245 of which portion of the viewed message is currently displayed. The
30246 Ctrl-B key can be used to select the previous web hostnames in the same way.
30249 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30251 <End of help on this topic>
30254 ====== h_config_enable_view_arrows =====
30257 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></TITLE>
30260 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></H1>
30262 This feature modifies Up and Down arrow key behavior in Alpine's
30263 MESSAGE TEXT screen when selectable Attachments, URL's, or
30264 web-hostnames are presented. Alpine's usual behavior is to move to
30265 the next or previous selectable item if currently displayed or
30266 simply to adjust the screen view by one line.
30270 Setting this feature causes the UP and Down arrow key to behave as
30271 if no selectable items were present in the message.
30275 Note, the Ctrl-F (next selectable item) and Ctrl-B (previous selectable
30276 item) functionality is unchanged.
30279 <End of help on this topic>
30282 ====== h_config_quell_charset_warning =====
30285 <TITLE>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></TITLE>
30288 <H1>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></H1>
30290 By default, if the message you are viewing contains characters that are
30291 not representable in your
30292 <A HREF="h_config_char_set">"Display Character Set"</A>
30294 add a warning to the start of the displayed text.
30295 If this option is set, then that editorial message will be suppressed.
30297 Setting this feature also suppresses the comment about the character set
30299 For example, when viewing a message you might see
30301 <CENTER><SAMP>From: "[ISO-8859-2] Name" <address></SAMP></CENTER>
30303 in the From header if your Character-Set is something other than ISO-8859-2.
30304 If you set this feature, the comment about the character set will
30305 no longer be there.
30307 <End of help on this topic>
30310 ====== h_config_quell_host_after_url =====
30313 <TITLE>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></TITLE>
30316 <H1>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></H1>
30318 By default, links in HTML text are displayed with the host the link
30319 references appended, within square brackets, to the link text. Alpine
30320 does this to help indicate where a link will take you, particularly when
30321 the link text might suggest a different destination.
30324 Setting this feature will prevent the server name from being appended
30325 to the displayed text.
30328 <End of help on this topic>
30331 ====== h_config_prefer_plain_text =====
30334 <TITLE>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></TITLE>
30337 <H1>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></H1>
30339 A message being viewed may contain alternate versions of the same content.
30340 Those alternate versions are supposed to be ordered by the sending software such that the
30341 first alternative is the least preferred and the last alternative is the
30342 most preferred. Alpine will normally display the most-preferred version that
30343 it knows how to display. This is most often encountered where the two
30344 alternate versions are a plain text version and an HTML version, with the
30345 HTML version listed last as the most preferred.
30347 If this option is set, then any plain text version will be preferred to
30348 all other versions.
30350 When viewing a message there is a command "A TogglePreferPlain",
30351 which will temporarily change the sense of this option.
30352 If this option is set you will first see the plain text version of a
30354 If you then type the "A" command, you will see the most preferred version,
30355 most likely HTML, instead.
30356 Typing the "A" command a second time will switch it back.
30357 Alternatively, if the present option is not set you will originally see
30358 the most preferred version of the message and typing "A" will switch to
30359 the plain text version.
30361 <End of help on this topic>
30364 ====== h_config_pass_control =====
30367 <TITLE>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></TITLE>
30370 <H1>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></H1>
30372 It is probably not useful to set this option.
30373 This is a legacy option left behind "just in case".
30374 Multi-byte characters that have an octet that has the same
30375 value as a control character are permitted through whether or not
30376 this option is turned on.
30378 This feature controls how certain characters contained in messages are
30380 If set, all characters in a message will be sent to the
30381 screen. Normally, control characters are displayed as shown below to
30382 avoid a garbled screen and to
30383 avoid inadvertently changing terminal setup parameters.
30384 Control characters are usually displayed as two character sequences like
30385 <P><CENTER><SAMP> ^C </SAMP></CENTER><P>
30387 <P><CENTER><SAMP> ^[ </SAMP></CENTER><P>
30389 <P><CENTER><SAMP> ^? </SAMP></CENTER><P>
30391 <P><CENTER><SAMP> ~E </SAMP></CENTER><P>
30392 for the character with value 133 (0x85).
30393 (The DEL character is displayed as ^?, regular control characters are displayed
30394 as the character ^ followed by the character obtained by adding the
30395 five low-order bits of the character to 0x40, and the C1
30396 control characters 0x80 - 0x9F are displayed as the character ~ followed by the
30397 character obtained by adding the
30398 five low-order bits of the character to 0x40.)
30399 Sometimes, in cases where changing a single control character into a
30400 two-character sequence would confuse Alpine's display routines,
30401 a question mark is substituted for the control character.
30403 If you wish to filter out regular control characters but pass the
30404 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
30405 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.
30407 <End of help on this topic>
30410 ====== h_config_pass_c1_control =====
30413 <TITLE>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></TITLE>
30416 <H1>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></H1>
30418 It is probably not useful to set this option.
30419 This is a legacy option left behind "just in case".
30420 Multi-byte characters that have an octet that has the same
30421 value as a control character are permitted through whether or not
30422 this option is turned on.
30424 If the feature <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
30425 is set, then this feature has no effect.
30426 However, if you wish to filter out regular control characters but pass the
30427 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
30428 you may leave <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
30429 unset and set this feature.
30431 <End of help on this topic>
30434 ====== h_config_fcc_on_bounce =====
30437 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></TITLE>
30440 <H1>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></H1>
30442 This feature controls an aspect of Alpine's behavior when bouncing a
30443 message. If set, normal FCC ("File Carbon Copy") processing will be
30444 done, just as if you had composed a message to the address you are
30445 bouncing to. If not set, no FCC of the message will be saved.
30447 <End of help on this topic>
30450 ====== h_config_show_cursor =====
30453 <TITLE>FEATURE: <!--#echo var="FEAT_show-cursor"--></TITLE>
30456 <H1>FEATURE: <!--#echo var="FEAT_show-cursor"--></H1>
30458 This feature controls an aspect of Alpine's displays. If set, the system
30459 cursor will move to convenient locations in the displays. For example,
30460 to the beginning of the status field of the highlighted index line, or
30461 to the highlighted word after a successful WhereIs command. It is intended
30462 to draw your attention to an "interesting" spot on the screen.
30464 <End of help on this topic>
30467 ====== h_config_sort_fcc_alpha =====
30470 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></TITLE>
30473 <H1>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></H1>
30475 This feature controls an aspect of Alpine's FOLDER LIST screen.
30476 If set, the default Fcc folder will be sorted alphabetically with the other
30477 folders instead of appearing right after the INBOX.
30479 <End of help on this topic>
30482 ====== h_config_sort_save_alpha =====
30485 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></TITLE>
30488 <H1>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></H1>
30490 This feature controls an aspect of Alpine's FOLDER LIST screen.
30491 If set, the default save folder will be sorted alphabetically with the other
30492 folders instead of appearing right after the INBOX (and default FCC folder).
30494 <End of help on this topic>
30497 ====== h_config_single_list =====
30500 <TITLE>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></TITLE>
30503 <H1>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></H1>
30505 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
30506 the folders will be listed one per line instead of several per line
30507 in the FOLDER LIST display.
30509 <End of help on this topic>
30512 ====== h_config_vertical_list =====
30515 <TITLE>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></TITLE>
30518 <H1>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></H1>
30520 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
30521 the folders will be listed alphabetically down the columns rather
30522 than across the columns as is the default.
30524 <End of help on this topic>
30527 ====== h_config_verbose_post =====
30530 <TITLE>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></TITLE>
30533 <H1>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></H1>
30534 This feature controls an aspect of Alpine's message sending. When enabled,
30535 Alpine will send a VERB (i.e., VERBose) command early in the posting process
30536 intended to cause the SMTP server to provide a more detailed account of
30537 the transaction. This feature is typically only useful to system
30538 administrators and other support personel as an aid in troublshooting
30541 Note, this feature relies on a specific capability of the system's mail
30542 transport agent or configured
30543 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>.
30544 It is possible that this
30545 feature will cause problems for some tranport agents, and may result in
30546 sending failure. In addition, as the verbose output comes from the mail
30547 transport agent, it is likely to vary from one system to another.
30549 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30551 <End of help on this topic>
30554 ====== h_config_auto_reply_to =====
30557 <TITLE>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></TITLE>
30560 <H1>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></H1>
30562 This feature controls an aspect of Alpine's Reply command. If set, Alpine
30563 will not prompt when a message being replied to contains a "Reply-To:"
30564 header value, but will simply use its value (as opposed to using the
30565 "From:" field's value).
30569 Note: Using the "Reply-To:" address is usually the preferred behavior,
30570 however, some mailing list managers choose to place the list's address in
30571 the "Reply-To:" field of any message sent out to the list. In such
30572 cases, this feature makes it all too easy for personal replies to be
30573 inadvertently sent to the entire mail list, so be careful!
30575 <End of help on this topic>
30578 ====== h_config_del_skips_del =====
30581 <TITLE>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></TITLE>
30584 <H1>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></H1>
30586 This feature controls an aspect of Alpine's Delete command. If set, this
30587 feature will cause the Delete command to advance past following messages that
30588 are marked deleted. In other words, pressing "D" will both mark the
30589 current message deleted and advance to the next message that is not marked
30591 This feature is set by default.
30593 <End of help on this topic>
30595 ====== h_config_expunge_manually =====
30598 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></TITLE>
30601 <H1>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></H1>
30603 Normally, when you close a folder that contains deleted messages you are
30604 asked if you want to expunge those messages from the folder permanently.
30605 If this feature is set, you won't be asked and the deleted messages will
30606 remain in the folder.
30607 If you choose to set this feature you will have to expunge the
30608 messages manually using the eXpunge command, which you can use while
30609 in the MESSAGE INDEX screen.
30610 If you do not expunge deleted messages the size of your
30611 folder will continue to increase until you are out of disk space.
30614 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30616 <End of help on this topic>
30619 ====== h_config_auto_expunge =====
30622 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></TITLE>
30625 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></H1>
30627 This features controls an aspect of Alpine's eXpunge command. If set, you
30628 will <B>not</B> be prompted to confirm your intent before the expunge takes
30630 Actually, this is only true for the INBOX folder and for folders in the
30631 Incoming Folders collection. See the feature
30632 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>.
30635 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30637 <End of help on this topic>
30640 ====== h_config_full_auto_expunge =====
30643 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></TITLE>
30646 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></H1>
30648 This features controls an aspect of Alpine's eXpunge command. If set, you
30649 will <B>not</B> be prompted to confirm your intent before the expunge
30650 takes place. This feature sets this behavior for all folders, unlike the
30651 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
30652 feature that works only for incoming folders.
30655 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30657 <End of help on this topic>
30660 ====== h_config_auto_read_msgs =====
30663 <TITLE>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></TITLE>
30666 <H1>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></H1>
30667 This feature controls an aspect of Alpine's behavior upon quitting. If set,
30669 <A HREF="h_config_read_message_folder">"<!--#echo var="VAR_read-message-folder"-->"</A>
30670 option is also set, then Alpine will
30671 automatically transfer all read messages to the designated folder and mark
30672 them as deleted in the INBOX. Messages in the INBOX marked with an
30673 "N" (meaning New, or unseen) are not affected.
30676 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30678 <End of help on this topic>
30681 ====== h_config_auto_fcc_only =====
30684 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></TITLE>
30687 <H1>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></H1>
30688 This features controls an aspect of Alpine's composer.
30689 The only time this feature will be used is if you attempt to send mail
30690 that has no recipients but does have an Fcc.
30691 Normally, Alpine will ask if you really mean to copy the message only to
30693 That is, it asks if you really meant to have no recipients.
30694 If this feature is set, you
30695 will <B>not</B> be prompted to confirm your intent to make only a copy
30696 of a message with no recipients.
30698 This feature is closely related to
30699 <A HREF="h_config_warn_if_no_to_or_cc"><!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></A>.
30700 The difference between this feature and that feature is that this feature
30701 considers a Bcc to be a recipient while that feature will ask for confirmation
30702 even if there is a Bcc when there is no To, Cc, or Newsgroup.
30703 The default values also differ. This feature defaults to asking the question
30704 and you have to turn it off.
30705 The <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--> feature defaults to not asking
30706 unless you turn it on.
30710 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30712 <End of help on this topic>
30715 ====== h_config_mark_fcc_seen =====
30718 <TITLE>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></TITLE>
30721 <H1>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></H1>
30723 This features controls the way Fccs (File carbon copies) are
30724 made of the messages you send.
30727 Normally, when Alpine saves a copy of a message you sent as an Fcc, that
30728 copy will be marked as Unseen.
30729 When you look at the folder it was saved in the message will appear to
30730 be a New message until you read it.
30731 When this feature is enabled, the message will be marked as having
30736 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30738 <End of help on this topic>
30741 ====== h_config_no_fcc_attach =====
30744 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></TITLE>
30747 <H1>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></H1>
30749 This features controls the way Fcc's (File carbon copies) are
30750 made of the messages you send.
30753 Normally, Alpine saves an exact copy of your message as it was sent.
30754 When this feature is enabled, the "body" of the message
30755 you send (the text you type in the composer) is preserved in the
30756 copy as before, however all attachments are replaced with text
30757 explaining what had been sent rather than the attachments themselves.
30760 This feature also affects Alpine's "Send ?" confirmation prompt
30761 in that a new "^F Fcc Attchmnts" option becomes available which
30762 allows you to interactively set whether or not attachments are saved
30767 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30769 <End of help on this topic>
30772 ====== h_config_read_in_newsrc_order =====
30775 <TITLE>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></TITLE>
30778 <H1>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></H1>
30780 This feature controls the order in which newsgroups will be presented. If
30781 set, they will be presented in the same order as they occur in your
30782 <!--chtml if pinemode="os_windows"-->
30785 ".newsrc"
30787 file (the default location of which can be changed with the
30788 <A HREF="h_config_newsrc_path">"<!--#echo var="VAR_newsrc-path"-->"</A> option).
30790 If not set, the newsgroups will be presented in alphabetical order.
30793 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30795 <End of help on this topic>
30798 ====== h_config_quell_tz_comment =====
30801 <TITLE>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></TITLE>
30804 <H1>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></H1>
30806 Normally, when Alpine generates a Date header for outgoing mail,
30807 it will try to include the symbolic timezone at the end of the
30808 header inside parentheses.
30809 The symbolic timezone is often three characters long, but on
30810 some operating systems, it may be longer.
30811 Apparently there are some SMTP servers in the world that will reject an
30812 incoming message if it has a Date header longer than about 80 characters.
30813 If this feature is set, the symbolic timezone normally generated by
30814 Alpine will not be included.
30815 You probably don't need to worry about this feature unless you run into
30816 the problem described above.
30819 <End of help on this topic>
30822 ====== h_config_post_wo_validation =====
30825 <TITLE>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></TITLE>
30828 <H1>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></H1>
30830 This feature controls whether the NNTP server is queried as newsgroups
30831 are entered for posting. Validation over slow links (e.g. dialup using
30832 SLIP or PPP) can cause delays. Set this feature to eliminate such delays.
30834 <End of help on this topic>
30837 ====== h_config_send_wo_confirm =====
30840 <TITLE>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></TITLE>
30843 <H1>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></H1>
30845 By default, when you send or post a message you will be asked to confirm
30846 with a question that looks something like:
30849 <CENTER><SAMP>Send message?</SAMP></CENTER>
30852 If this feature is set, you
30853 will <B>not</B> be prompted to confirm your intent to send
30854 and your message will be sent.
30856 If this feature is set it disables some possibilities and renders some
30857 other features meaningless.
30858 You will not be able to use
30859 <A HREF="h_config_sending_filter">Sending Filters</A>,
30860 Verbose sending mode,
30861 <A HREF="h_config_compose_bg_post">Background Sending</A>,
30862 <A HREF="h_config_compose_dsn">Delivery Status Notifications</A>,
30863 or ^V to turn off the generation of flowed text for this message.
30864 These options are normally available as suboptions in the Send prompt, but
30865 with no Send prompt the options are gone.
30868 A somewhat related feature is
30869 <A HREF="h_config_quell_post_prompt">"<!--#echo var="FEAT_quell-extra-post-prompt"-->"</A>,
30870 which may be used to eliminate the extra confirmation
30871 question when posting to a newsgroup.
30874 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30876 <End of help on this topic>
30879 ====== h_config_quell_filtering_done_message =====
30882 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></TITLE>
30885 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></H1>
30887 If you use Filter Rules that move messages or set status of messages
30888 you sometimes see a message from Alpine that looks like
30891 <CENTER><SAMP>filtering done</SAMP></CENTER>
30894 If this feature is set, this message will be suppressed.
30896 <A HREF="h_config_quell_filtering_messages"><!--#echo var="FEAT_quell-filtering-messages"--></A>
30897 is set then this message will be suppressed regardless.
30901 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30903 <End of help on this topic>
30906 ====== h_config_quell_filtering_messages =====
30909 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></TITLE>
30912 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></H1>
30914 If you use Filter Rules that move messages or set status of messages
30915 you sometimes see messages from Alpine that look like
30918 <CENTER><SAMP><filter name>: Moving 2 filtered messages to <folder name></SAMP></CENTER>
30924 <CENTER><SAMP><filter name>: Setting flags in 5 messages</SAMP></CENTER>
30930 <CENTER><SAMP>Processing filter <filter name></SAMP></CENTER>
30933 If this feature is set, these messages will be suppressed.
30935 <A HREF="h_config_quell_filtering_done_message"><!--#echo var="FEAT_quell-filtering-done-message"--></A>
30940 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30942 <End of help on this topic>
30945 ====== h_config_quell_post_prompt =====
30948 <TITLE>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></TITLE>
30951 <H1>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></H1>
30953 By default, when you post a message to a newsgroup you are asked to confirm
30954 that you want to post with the question
30957 <CENTER><SAMP>Posted message may go to thousands of readers. Really post?</SAMP></CENTER>
30960 If this feature is set, you
30961 will <B>not</B> be prompted to confirm your intent to post to a newsgroup
30962 and your message will be posted.
30966 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30968 <End of help on this topic>
30971 ====== h_config_check_mail_onquit =====
30974 <TITLE>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></TITLE>
30977 <H1>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></H1>
30979 If this feature is set, Alpine will check for new mail after you give the
30981 If new mail has arrived since the previous check, you will be notified
30982 and given the choice of quitting or not quitting.
30985 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30987 <End of help on this topic>
30990 ====== h_config_inbox_no_confirm =====
30993 <TITLE>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></TITLE>
30996 <H1>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></H1>
30998 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
30999 command and there are no more folders or newsgroups to visit, you are asked
31000 if you want to return to the INBOX.
31001 If this feature is set you will not be asked.
31002 It will be assumed that you do want to return to the INBOX.
31005 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31007 <End of help on this topic>
31010 ====== h_config_dates_to_local =====
31013 <TITLE>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></TITLE>
31016 <H1>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></H1>
31018 Normally, the message dates that you see in the
31019 MESSAGE INDEX and MESSAGE VIEW are displayed in the timezone they were sent from.
31020 For example, if a message was sent to you from a few timezones to the east
31021 it might appear that it was sent from the future;
31022 or if it was sent from somewhere to the west it might appear
31023 as if it is from yesterday even though it was sent only a few minutes ago.
31024 If this feature is set an attempt will be made to convert the dates
31025 to your local timezone to be displayed.
31027 Note that this does not affect the results of Select by Date or of
31028 anything else other than these displayed dates.
31029 When viewing the message you may look at the original unconverted value of the Date
31030 header by using the <A HREF="h_common_hdrmode">HdrMode Command</A>.
31033 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31035 <End of help on this topic>
31038 ====== h_config_tab_no_prompt =====
31041 <TITLE>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></TITLE>
31044 <H1>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></H1>
31046 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
31047 command and there is a problem checking a folder, you are asked
31048 whether you want to continue with the search in the following folder or not.
31049 This question gives you a chance to stop the NextNew processing.
31050 (The checking problem might be caused by the fact that the folder does not
31051 exist, or by an authentication problem, or by a server problem
31055 If this feature is set you will not be asked.
31056 It will be assumed that you do want to continue.
31059 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31061 <End of help on this topic>
31064 ====== h_config_input_history =====
31067 <TITLE>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></TITLE>
31070 <H1>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></H1>
31072 Many of the prompts that ask for input in the status line near the
31073 bottom of the screen will respond to Up Arrow and Down Arrow
31074 with the history of previous entries.
31075 For example, in the MESSAGE INDEX screen when you use the WhereIs
31076 command the text you entered will be remembered and can be recalled
31077 by using the Up Arrow key.
31078 Another example, when saving a message the folders saved to will
31079 be remembered and can be recalled using the arrow keys.
31081 In the Save prompt, some users prefer that the Up and Down arrow keys
31082 be used for the Previous Collection and Next Collection commands
31083 instead of for a history of previous saves.
31084 If this option is set the Up and Down arrow keys will become synonyms for the
31085 Previous Collection and Next Collection (^P and ^N) commands in the
31086 prompt for the name of a folder to Save to or in the prompt for the
31087 name of a folder to GoTo.
31088 When this feature is not set (the default), ^P and ^N will change the
31089 collection and the arrow keys will show the history.
31092 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31094 <End of help on this topic>
31097 ====== h_config_confirm_role =====
31100 <TITLE>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></TITLE>
31103 <H1>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></H1>
31105 If you have roles, when you Reply to or Forward a message, or Compose
31106 a new message, Alpine
31107 will search through your roles for one that matches.
31108 Normally, if no matches are found you will be placed into the composer
31109 with no opportunity to select a role.
31110 If this feature is set, then you will be asked to confirm that you don't
31112 This will give you the opportunity to select a role (with the ^T command).
31113 If you confirm no role with a Return, you will be placed in
31114 the composer with no role.
31115 You may also confirm with either an "N" or a "Y".
31116 These behave the same as if you pressed the Return.
31117 (The "N" and "Y" answers are available because they
31118 match what you might type if there was a role match.)
31120 If you are using the alternate form of the Compose command called
31121 "Role", then all of your roles will be available to you,
31122 independent of the value of this feauture and of the values set for all of
31123 Reply Use, Forward Use, and Compose Use.
31126 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31128 <End of help on this topic>
31131 ====== h_config_news_cross_deletes =====
31134 <TITLE>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></TITLE>
31137 <H1>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></H1>
31139 This feature controls what Alpine does when you delete a message in a
31140 newsgroup that appears in more than one newsgroup. Such a message
31141 is sometimes termed a "crossposting" in that it was posted
31142 across several newsgroups.
31145 Alpine's default behavior when you delete such a message is to remove
31146 only the copy in the current newsgroup from view when you use the
31147 "Exclude" command or the next time you visit the newsgroup.
31150 Enabling this feature causes Alpine to remove every occurrence of the
31151 message from all newsgroups it appears in and to which you are
31155 NOTE: As currently implemented, enabling this feature may increase the
31156 time it takes the Expunge command and newsgroup closing to complete.
31160 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31162 <End of help on this topic>
31165 ====== h_config_news_catchup =====
31168 <TITLE>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></TITLE>
31171 <H1>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></H1>
31173 This feature controls what Alpine does as it closes a newsgroup.
31174 When set, Alpine will offer to delete all messages from the newsgroup
31175 as you are quitting Alpine or opening a new folder.
31178 This feature is useful if you typically read all the interesting messages
31179 in a newsgroup each time you open it. This feature saves you from
31180 having to delete each message in a newsgroup as you read it or from
31181 selecting all the messages and doing an
31182 <A HREF="h_config_enable_agg_ops">aggregate delete</A> before you
31183 move on to the next folder or newsgroup.
31187 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31189 <End of help on this topic>
31192 ====== h_config_next_thrd_wo_confirm =====
31195 <TITLE>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></TITLE>
31198 <H1>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></H1>
31200 This feature controls an aspect of Alpine's Next and Prev commands in
31201 the case where you are using one of the
31202 "separate-index-screen" styles for the configuration option
31203 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
31204 and currently have the folder sorted by a Threaded or OrderedSubject sort.
31205 When you are Viewing a particular thread you have a
31206 MESSAGE INDEX of only the messages in that thread.
31207 If you press the Next command with the last message in the thread highlighted
31208 you will normally be asked if you want to "View next thread?",
31209 assuming there is a next thread to view.
31210 If this feature is set it will be assumed that you always want to view the
31211 next thread and you won't be asked to confirm that.
31212 Similarly, if the first message of the thread is highlighted and you
31213 press the Prev command, this feature will prevent the question
31214 "View previous thread".
31216 This feature only has an effect in the MESSAGE INDEX screen.
31217 If you then view a particular message from that screen and press the
31218 Next command, you will be sent to the next thread without being asked,
31219 independent of the setting of this feature.
31222 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A> also has some similar effects.
31224 <End of help on this topic>
31227 ====== h_config_kw_braces =====
31230 <TITLE>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></TITLE>
31233 <H1>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></H1>
31235 This option controls a minor aspect of Alpine's MESSAGE INDEX and MESSAGE
31237 If you have modified the
31238 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
31239 so that either the "SUBJKEY" or "SUBJKEYINIT" tokens
31240 are used to display keywords or their initials along with the Subject; then
31241 this option may be used to modify the resulting display slightly.
31242 By default, the keywords or initials displayed for these tokens will be
31243 surrounded with curly braces ({ and }) and a trailing space.
31244 For example, if keywords "Work" and "Now" are set for
31245 a message, the "SUBJKEY" token will normally look like
31247 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
31249 and the SUBJKEYINIT token would look like
31251 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
31253 The default character before the keywords is the left brace ({) and the
31254 default after the keywords is the right brace followed by a space (} ).
31256 This option allows you to change that.
31257 You should set it to two values separated by a space.
31258 The values may be quoted if they include space characters.
31259 So, for example, the default value could be specified explicitly by setting this
31262 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="{" "} "</SAMP></CENTER>
31264 The first part wouldn't need to be quoted (but it doesn't hurt).
31265 The second part does need the quotes because it includes a space character.
31266 If you wanted to change the braces to brackets you could use
31268 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="[" "] "</SAMP></CENTER>
31270 Inside the quotes you can use backslash quote to mean quote, so
31272 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="\"" "\" "</SAMP></CENTER>
31276 <CENTER><SAMP>"Work Now" actual subject</SAMP></CENTER>
31278 It is also possible to color keywords in the index using the
31279 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
31281 It is not possible to change the fact that a space character is used to
31282 separate the keywords if more than one keyword is set for a message.
31283 It is also not possible to change the fact that there are no separators
31284 between the keyword initials if more than one keyword is set.
31286 <End of help on this topic>
31289 ====== h_config_opening_sep =====
31292 <TITLE>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></TITLE>
31295 <H1>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></H1>
31297 This option controls a minor aspect of Alpine's MESSAGE INDEX screen.
31298 With some setups the text of the subject is followed
31299 by the opening text of the message if there is any room available in the index line.
31300 If you have configured your
31301 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
31302 to include one of the Subject tokens that causes this behavior
31303 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), then this option may be used
31304 to modify what is displayed slightly.
31305 By default, the Subject is separated from the opening text of the message by
31306 the three characters space dash space;
31308 <CENTER><SAMP>" - "</SAMP></CENTER>
31310 Use this option to set it to something different.
31311 The value must be quoted if it includes any space characters.
31312 For example, the default value could be specified explicitly by setting this
31315 <CENTER><SAMP><!--#echo var="VAR_opening-text-separator-chars"-->=" - "</SAMP></CENTER>
31317 <End of help on this topic>
31320 ====== h_config_select_wo_confirm =====
31323 <TITLE>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></TITLE>
31326 <H1>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></H1>
31328 This feature controls an aspect of Alpine's Save, Export, and Goto commands.
31329 These commands all take text input to specify the name of the folder or
31330 file to be used, but allow you to press ^T for a list of possible names.
31331 If set, the selected name will be used immediately, without further
31332 opportunity to confirm or edit the name.
31334 Some related help topics are
31336 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
31337 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
31338 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
31339 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
31340 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
31341 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>.
31344 <End of help on this topic>
31347 ====== h_config_save_part_wo_confirm =====
31350 <TITLE>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></TITLE>
31353 <H1>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></H1>
31355 This feature controls an aspect of Alpine's Save command.
31356 By default, when you Save a message that has some deleted parts, you will
31357 be asked to confirm that you want to Save with a prompt that looks like:
31359 <CENTER><SAMP>Saved copy will NOT include entire message! Continue?</SAMP></CENTER>
31361 If this feature is set, you will not be asked.
31363 <End of help on this topic>
31366 ====== h_config_use_resentto =====
31369 <TITLE>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></TITLE>
31372 <H1>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></H1>
31374 This feature is turned off by default because turning it on causes problems
31375 with some deficient IMAP servers.
31376 In Alpine <A HREF="h_mainhelp_filtering">Filters</A> and other types of Rules, if the
31377 <A HREF="h_rule_patterns">Pattern</A>
31378 contains a To header pattern and this feature is turned on,
31379 then a check is made in the message to see
31380 if a Resent-To header is present, and that is used instead of the To header.
31381 If this feature is not turned on, then the regular To header will always
31385 <End of help on this topic>
31388 ====== h_config_use_reg_start_for_stayopen =====
31391 <TITLE>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></TITLE>
31394 <H1>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></H1>
31396 This feature affects which message is selected as the current message
31398 <A HREF="h_config_permlocked">Stay Open</A> folder.
31400 Normally, the starting position for an incoming folder (which most Stay Open
31401 folders will likely be) is controlled by the
31402 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
31403 However, if a folder is a Stay Open folder, when you re-enter the folder
31404 after the first time the current message will be the same as it was when
31405 you left the folder.
31406 An exception is made if you use the TAB command to get to the folder.
31407 In that case, the message number will be incremented by one from what it
31408 was when you left the folder.
31410 The above special behavior is thought to be useful.
31411 However, it is special and different from what you might at first expect.
31412 If this feature is set, then Stay Open folders will not be treated specially
31413 as far as the startup rule is concerned.
31416 <End of help on this topic>
31419 ====== h_config_use_current_dir =====
31422 <TITLE>FEATURE: <!--#echo var="FEAT_use-current-dir"--></TITLE>
31425 <H1>FEATURE: <!--#echo var="FEAT_use-current-dir"--></H1>
31427 This feature controls an aspect of several commands.
31428 If set, your "current working directory"
31429 <!--chtml if pinemode="running"-->
31430 (which, at least for your current Alpine "session,"
31431 is "<!--#echo var="CURRENT_DIR"-->")
31433 will be used instead of your home directory
31434 <!--chtml if pinemode="running"-->
31435 (which, in the present configuration of your system, is
31436 "<!--#echo var="HOME_DIR"-->")
31438 for all of the following operations:<UL>
31439 <LI> Export in the MESSAGE INDEX and MESSAGE TEXT screens
31440 <LI> Attachment Save in the MESSAGE TEXT and ATTACHMENT TEXT screens
31441 <LI> <!--chtml if pinemode="function_key"-->F4
31442 <!--chtml else-->Ctrl-R
31443 <!--chtml endif--> file inclusion in the COMPOSER
31444 <LI> <!--chtml if pinemode="function_key"-->F5
31445 <!--chtml else-->Ctrl-J
31446 <!--chtml endif--> file attachment in the COMPOSER
31448 <!--chtml if pinemode="os_windows"-->
31450 If you are starting PC-Alpine from a desktop icon or the Start menu,
31451 you can set the "current drive"
31452 by specifying it in the "Start in:"
31453 box found in the Shortcut tab of the Properties.
31457 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31461 <End of help on this topic>
31464 ====== h_config_save_wont_delete =====
31467 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></TITLE>
31470 <H1>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></H1>
31472 This feature controls one aspect of the Save command. If set, Save will
31473 not mark the message "deleted" (its default behavior) after
31474 it has been copied to the designated folder.
31477 <End of help on this topic>
31480 ====== h_config_use_boring_spinner =====
31483 <TITLE>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></TITLE>
31486 <H1>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></H1>
31488 When Alpine is delayed for some reason it usually shows that
31489 something is happening with a small animated display in the status
31490 message line near the bottom of the screen.
31491 Setting this feature will cause that animation to be the same
31492 each time instead of having Alpine choose a random animation.
31493 You may turn the animation off altogether by setting the
31494 <A HREF="h_config_active_msg_interval"><!--#echo var="VAR_busy-cue-rate"--></A>
31498 <End of help on this topic>
31501 ====== h_config_unsel_wont_advance =====
31504 <TITLE>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></TITLE>
31507 <H1>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></H1>
31509 This feature controls one aspect of the Unselect Current message command.
31510 Normally, when the Unselect current message command (:) is typed when the
31511 current message is selected, the message will be unselected and the next
31512 message will become the current message.
31513 If this feature is set, the cursor will not advance to the next message.
31514 Instead, the current message will remain the current message after
31518 <End of help on this topic>
31521 ====== h_config_prune_uses_iso =====
31524 <TITLE>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></TITLE>
31527 <H1>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></H1>
31529 By default, Alpine asks monthly whether or not you would like to rename
31530 some folders to a new name containing the date.
31531 It also asks whether or not you would like to delete some old folders.
31532 See the <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option for an
31536 By default, the name used when renaming a folder looks like
31538 <CENTER><SAMP><foldername>-<month>-<year></SAMP></CENTER>
31540 For example, the first time you run Alpine in May of 2004,
31541 the folder "sent-mail" might be renamed to
31543 <CENTER><SAMP>sent-mail-apr-2004</SAMP></CENTER>
31545 If this feature is set, the name used will be of the form
31547 <CENTER><SAMP><foldername>-<yyyy>-<mm></SAMP></CENTER>
31549 where "yyyy" is the year and "mm" is the two-digit
31550 month (01, 02, ..., 12).
31551 For the April, 2004 example above, it would instead be
31553 <CENTER><SAMP>sent-mail-2004-04</SAMP></CENTER>
31555 because April is the 4th month of the year.
31556 A reason you might want to set this feature is so that the folders
31557 will sort in chronological order.
31560 <End of help on this topic>
31563 ====== h_config_save_advances =====
31566 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-advance"--></TITLE>
31569 <H1>FEATURE: <!--#echo var="FEAT_save-will-advance"--></H1>
31571 This feature controls one aspect of the Save command. If set, Save will
31572 (in addition to copying the current message to the designated folder) also
31573 advance to the next message.
31576 <End of help on this topic>
31579 ====== h_config_force_arrow =====
31582 <TITLE>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></TITLE>
31585 <H1>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></H1>
31587 This feature affects Alpine's MESSAGE INDEX display routine.
31588 If set, the normal inverse-video cursor will be
31589 replaced by a simple "arrow" cursor, which normally occupies the
31590 second column of the index display.
31592 This is the same index cursor you get if you turn on
31593 <A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>, but the index
31594 line coloring will still be present if this feature is turned on and
31595 <!--#echo var="FEAT_assume-slow-link"--> is off.
31597 An alternative version of the Arrow cursor is available by including the
31598 <A HREF="h_config_index_arrow_color">ARROW</A>
31600 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
31602 It ought to be the case that this feature also affects the ATTACHMENT INDEX,
31603 but that is not implemented.
31606 <End of help on this topic>
31609 ====== h_config_ignore_size =====
31612 <TITLE>FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></TITLE>
31615 <H1>FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></H1>
31617 When you have an account residing in an IMAP server, Alpine records the
31618 size of each message as reported by the server. However, when Alpine saves
31619 a message in such IMAP server, Alpine will compute the size of the message
31620 independently, from the data it received. If these two numbers do not
31621 match for a message, Alpine asks you if you still want to take the risk of
31622 saving such message, since data corruption or loss of data could result
31626 Sometimes the root of this problem is that the IMAP server does not
31627 compute sizes correctly, and there will not be loss of information when
31628 saving such message. Enabling this feature will make Alpine ignore such
31629 error and continue saving the message without producing any warnings or
31630 ever stopping the process, as if there had not been any error. This option
31631 applies to all IMAP servers that you use, so if you enable this feature,
31632 size discrepancy warnings will not be given for any IMAP server you
31636 Example of a server where you could reproduce this problem is the Gmail
31637 IMAP server. Another example can be found in some versions of the Exchange
31641 It is recommended that this feature be disabled most of the time and only
31642 enabled when you find a server which you can determine that has the above
31643 mentioned defect, but be disabled again after making the save operation
31647 <End of help on this topic>
31650 ====== h_config_force_low_speed =====
31653 <TITLE>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></TITLE>
31656 <H1>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></H1>
31660 This feature affects Alpine's display routines. If set, the normal
31661 inverse-video cursor (used to highlight the current item in a list) will be
31662 replaced by an "arrow" cursor and other
31663 screen update optimizations for
31664 low-speed links (e.g. 2400 bps dialup connections) will be activated.
31665 One of the optimizations is that colored index lines (set up with Indexcolor
31666 Rules) will not be colored.
31667 If you are just turning this feature on because you like using
31668 the "arrow" cursor you may have an arrow cursor with index line
31669 coloring by turning this feature off and the
31670 <A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A> on.
31673 <End of help on this topic>
31676 ====== h_config_show_delay_cue =====
31679 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></TITLE>
31682 <H1>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></H1>
31684 If set, this feature will cause an asterisk to appear in the upper
31685 left-hand corner of the screen whenever Alpine checks for new mail.
31686 Two asterisks whenever Alpine saves (checkpoints) the state of the current
31689 <!--chtml if pinemode="os_windows"-->
31691 In addition, PC-Alpine will display a less-than symbol, '<', when
31692 it is trying to open a network connection (e.g, to open your INBOX
31694 server) or read from the network connection. A greater-than symbol,
31695 will be displayed when PC-Alpine is trying to write to the network
31696 connection (e.g, sending a command to your IMAP server).
31700 <End of help on this topic>
31703 ====== h_config_color_style =====
31706 <TITLE>OPTION: Color Style</TITLE>
31709 <H1>OPTION: Color Style</H1>
31713 If the terminal or terminal emulator you are using is capable of displaying
31714 colors, this option controls whether or not color will be used in Alpine.
31715 If you turn color on and things are set up correctly,
31716 you should see color appear on the screen immmediately.
31717 Modern terminal emulators are usually capable of displaying colors.
31719 The available options include:
31724 <DD>Don't use color.
31727 <DT>use-termdef</DT>
31728 <DD>In order to decide if your terminal is capable of color, Alpine looks in
31729 the terminal capabilities database, TERMINFO or TERMCAP, depending on
31730 how Alpine was compiled.
31731 This is a good option to choose if you switch between a color and a non-color
31732 terminal with the same Alpine configuration.
31733 Alpine will know to use color on the color terminal because it is described
31734 in the termcap entry, and Alpine will know to use black and white on the
31735 non-color terminal.
31736 The Alpine Technical Notes
31737 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/tech-notes/">http://www.washington.edu/alpine/tech-notes/</A></SAMP></CENTER>
31738 have more information on configuring a TERMCAP or TERMINFO
31739 entry for color Alpine.
31740 This is usually something a system administrator does.
31743 <DT>force-ansi-8color</DT>
31744 <DD>This is probably the setting that most people should use.
31745 Because setting up a termcap entry is confusing and because the
31746 terminal capabilities database is often not correctly configured for color,
31747 this choice and the next may be easier for you to use.
31748 If your terminal emulator responds to ANSI color escape sequences, which
31749 many do, this option will cause Alpine to believe your terminal will respond
31750 to the escape sequences that produce eight different foreground and background
31752 The escape sequences used to set the foreground colors are
31754 <P><CENTER>ESC [ 3 <color_number> m</CENTER><P>
31756 where the color_number is an ASCII digit between 0 and 7.
31757 The numbers 0 through 7 should correspond to the colors black, red, green,
31758 yellow, blue, magenta, cyan, and white.
31759 Some terminal emulators use a pre-ANSI scheme that swaps
31760 the colors blue and red and the colors yellow and cyan.
31761 This will cause the default colors to be different, but other than that
31762 things should work fine.
31763 There is also a 9th color available, the last one shown, which is the default
31764 color from the terminal emulator.
31765 When used as a background color some people refer to this color as
31766 "transparent", which is why the letters "TRAN" are
31767 shown in the color swatch of the SETUP COLOR screen.
31768 The foreground transparent color is shown as
31769 the color of the "TRAN" text.
31770 (The transparent color will not work correctly in a PC-Alpine configuration.)
31771 The escape sequences used to set the background colors are the same
31772 as for the foreground colors except a "4" replaces the "3".
31773 The escape sequences for foreground and background default colors (transparent)
31776 Note: With the Tera Term terminal emulator this setting works well.
31777 You should also have the Tera Term "Full color" option turned OFF.
31778 You may find the "Full color" option in Tera Term's "Setup"
31779 menu, in the "Window" submenu.
31782 <DT>force-ansi-16color</DT>
31783 <DD>Many terminal emulators know about the same eight colors above
31785 This option attempts to use all 16 colors.
31786 The same escape sequences as for the eight-color terminal are used
31787 for the first eight colors.
31788 The escape sequences used to set foreground colors 8-15 are the same as
31789 for 0-7 except the "3" is replaced with a "9".
31790 The background color sequences for colors 8-15 are the same as for 0-7
31791 except the "4" is replaced with "10".
31792 You can tell if the 16 colors are working by turning on this option
31793 and then going into one of the color configuration screens, for example,
31794 the configuration screen for Normal Color.
31795 If you see 16 different colors to select from (plus a 17th for
31796 the transparent color), it's working.
31799 <DT>force-xterm-256color</DT>
31800 <DD>Some versions of xterm (and some other terminal emulators)
31801 have support for 256 colors.
31802 The escape sequences used to set the foreground colors are
31804 <P><CENTER>ESC [ 38 ; 5 ; <color_number> m</CENTER><P>
31806 where the color_number is an ASCII digit between 0 and 255.
31807 Background colors are the same with the 38 replaced with a 48.
31808 The numbers 0 through 15 are probably similar to the 16 color version
31809 above, then comes a 6x6x6 color cube, followed by 24 colors of gray.
31810 The terminal default (transparent) color is the 257th color at the bottom.
31811 Some terminal emulators will misinterpret these escape sequences causing
31812 the terminal to blink or overstrike characters or to do something else
31815 The PuTTY terminal emulator has an option called "Allow terminal to
31816 use xterm 256-colour mode" which allows PuTTY to work well with
31817 this 256-color setting.
31823 The normal default is "no-color".
31826 Once you've turned on color you may set the
31827 colors of many objects on the screen individually.
31828 For example, you may add colors to the status letters on the MESSAGE
31830 Most categories of color that Alpine supports are configurable here.
31831 For example, "Normal Color"
31832 is the color used to display most of the text in Alpine, and
31833 "Reverse Color" is used to display highlighted text, such as the
31834 current message in the MESSAGE INDEX.
31836 Lines in the MESSAGE INDEX may also be colored.
31837 Use Setup Rules to get to the Indexcolor configuration screen.
31841 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31843 <End of help on this topic>
31846 ====== h_config_disable_index_locale_dates =====
31849 <TITLE>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></TITLE>
31852 <H1>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></H1>
31854 This feature affects the display of dates in the MESSAGE INDEX.
31855 Normally an attempt is made to localize the dates
31856 used in the MESSAGE INDEX display to your locale.
31857 This is controlled with the
31858 LC_TIME locale setting on a UNIX system.
31859 On Windows the Regional Options control panel may be used to set the date format.
31860 At the programming level, Alpine is using the strftime routine
31861 to print the parts of a date.
31863 If this feature is set, dates are displayed in English and
31864 with the conventions of the United States.
31868 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31870 <End of help on this topic>
31873 ====== h_config_auto_open_unread =====
31876 <TITLE>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></TITLE>
31879 <H1>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></H1>
31881 This feature controls the behavior of the TAB key when traversing folders
31883 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
31884 collection or in optional <!--#echo var="VAR_news-collections"-->.
31887 (<A HREF="h_common_nextnew">NextNew</A>)
31888 key is pressed, and there
31889 are no more unseen messages in the current (incoming message or news)
31890 folder, Alpine will search the list of folders in the current collection for
31891 one containing New or Recent (new since the last time the folder was
31893 This behavior may be modified slightly with the
31894 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
31895 feature that causes Alpine to look for Unseen messages instead of Recent
31897 Normally, when such a folder is found, Alpine will ask
31898 whether you wish to open the folder. If this feature is set, Alpine will
31899 automatically open the folder without prompting.
31901 This feature also affects some other similar situations.
31903 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
31904 that is equal to one of the "separate-" values, and you are
31905 viewing a thread; then when you type the NextNew command and are at the
31906 end of the current thread you will automatically go to the next thread
31907 if this feature is set.
31908 By default, you would be asked if you want to view the next thread.
31909 You will also be asked at times whether or not you want to view the next
31910 thread after you delete the last message in the thread.
31911 Setting this feature will also cause that question to be skipped.
31915 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31917 <End of help on this topic>
31920 ====== h_config_auto_include_reply =====
31923 <TITLE>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></TITLE>
31926 <H1>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></H1>
31928 This feature controls an aspect of Alpine's Reply command. Normally, Alpine
31929 will ask whether you wish to include the original message in your reply.
31930 If this feature is set and the feature
31931 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
31932 is <EM>not</EM> set, then the original message will be included in the reply
31933 automatically, without prompting.
31935 <End of help on this topic>
31938 ====== h_config_select_in_bold =====
31941 <TITLE>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></TITLE>
31944 <H1>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></H1>
31946 This feature controls an aspect of Alpine's
31947 <A HREF="h_config_enable_agg_ops">"aggregate operation"</A>
31949 particular, the Select and WhereIs commands. Select and WhereIs (with the
31950 ^X subcommand) will search the current folder for messages meeting a
31951 specified criteria, and "tag" the resulting messages with an
31952 "X" in the
31953 first column of the applicable lines in the MESSAGE INDEX. If this feature
31954 is set, instead of using the "X" to denote a selected message,
31956 attempt to display those index lines in boldface. Whether this is
31957 preferable to the "X" will depend on personal taste and the type of
31958 terminal being used.
31961 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31963 <End of help on this topic>
31966 ====== h_config_alt_auth =====
31969 <TITLE>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></TITLE>
31972 <H1>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></H1>
31974 This feature affects how Alpine connects to IMAP servers.
31975 It's utility has largely been overtaken by events,
31976 but it may still be useful in some circumstances.
31977 If you only connect to modern IMAP servers that support
31978 "TLS" you can ignore this feature.
31984 By default, Alpine will attempt to connect to an IMAP server on the
31985 normal IMAP service port (143), and if the server offers "Transport Layer
31986 Security" (TLS) and Alpine has been compiled with encryption capability,
31987 then a secure (encrypted) session will be negotiated.
31990 With this feature enabled, before connecting on the normal IMAP port, Alpine
31991 will first attempt to connect to an alternate IMAP service port (993) used
31992 specifically for encrypted IMAP sessions via the Secure Sockets Layer
31994 If the SSL attempt fails, Alpine will then try the default
31995 behavior described in the previous paragraph.
31998 TLS negotiation on the normal port is preferred, and supersedes the use of
31999 SSL on port 993, but older servers may not provide TLS support.
32000 This feature may be convenient when accessing IMAP servers that do not support
32001 TLS, but do support SSL connections on port 993.
32002 However, it is important to understand that with this feature enabled,
32003 Alpine will <EM>attempt</EM> to make a secure connection if that is possible,
32004 but it will proceed to make an insecure connection if that is the only
32005 option offered by the server, or if the Alpine in question has been built
32006 without encryption capability.
32009 Note that this feature specifies a per-user (or system-wide) default
32010 behavior, but host/folder specification flags may be used to control the
32011 behavior of any specific connection.
32012 This feature interacts with some of
32013 the possible host/folder path specification flags as follows:
32016 The <SAMP>/tls</SAMP> host flag, for example,
32019 <CENTER><SAMP>{foo.example.com/tls}INBOX</SAMP></CENTER>
32021 will over-ride this feature for the specified host by bypassing the
32022 SSL connection attempt.
32023 Moreover, with <SAMP>/tls</SAMP> specified,
32024 the connection attempt will fail if the
32025 service on port 143 does not offer TLS support.
32028 The <SAMP>/ssl</SAMP> host flag, for example,
32031 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
32033 will insist on an SSL connection for the specified host,
32034 and will fail if the SSL service on port 993 is not available.
32035 Alpine will not subsequently retry a connection
32036 on port 143 if <SAMP>/ssl</SAMP> is specified.
32040 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32042 <End of help on this topic>
32045 ====== h_config_file_dir ======
32048 <TITLE>OPTION: File Directory</TITLE>
32051 <H1>OPTION: File Directory</H1>
32055 This value affects the Composer's "^J Attach" command,
32056 the Attachment Index Screen's "S Save" command, and the
32057 Message Index's "E Export" command.
32060 Normally, when a filename is supplied that lacks a leading "path"
32061 component, Alpine assumes the file exists in the user's home directory.
32062 Under Windows operating systems, this definition isn't always clear. This
32063 feature allows you to explictly set where Alpine should look for files
32064 without a leading path.
32067 NOTE: this feature's value is ignored if either
32068 <A HREF="h_config_use_current_dir"><!--#echo var="FEAT_use-current-dir"--></A> feature
32069 is set or the PINERC has a value for the "<!--#echo var="VAR_operating-dir"-->" variable.
32073 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32075 <End of help on this topic>
32078 ====== h_config_quote_all_froms =====
32081 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></TITLE>
32084 <H1>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></H1>
32086 This feature controls an aspect of the Save command (and also the way
32087 outgoing messages are saved to an FCC folder). If set, Alpine will add
32088 a leading ">" character in front of message lines beginning with "From"
32089 when they are saved to another folder, including lines syntactically
32090 distinguishable from the type of message separator line commonly used on
32094 The default behavior is that a ">" will be prepended only to lines
32095 beginning with "From " that might otherwise be confused with a message
32096 separator line on Unix systems. If pine is the only mail program you use,
32097 this default is reasonable. If another program you use has trouble
32098 displaying a message with an unquoted "From " saved by Alpine, you should
32099 enable this feature. This feature only applies to the common Unix mailbox
32100 format that uses message separator lines beginning with "From ". If
32101 Alpine has been configured to use a different mailbox format (possibly
32102 incompatible with other mail programs), then this issue does not arise,
32103 and the feature is irrelevant.
32106 <End of help on this topic>
32109 ====== h_config_normal_color =====
32112 <TITLE>OPTION: Normal Color</TITLE>
32115 <H1>OPTION: Normal Color</H1>
32117 Sets the color Alpine normally uses.
32118 The foreground color is the color of the actual character and the
32119 background color is the color of the area behind the character.
32120 By default this color is black characters on a white background.
32122 <A HREF="h_color_setup">Descriptions of the available commands</A>
32124 Look <A HREF="h_edit_nav_cmds">here</A>
32125 to see the available Editing and Navigation commands.
32127 <End of help on this topic>
32130 ====== h_config_reverse_color =====
32133 <TITLE>OPTION: Reverse Color</TITLE>
32136 <H1>OPTION: Reverse Color</H1>
32138 Sets the color Alpine uses for reverse video characters.
32139 The foreground color is the color of the actual character and the
32140 background color is the color of the area behind the character.
32142 <A HREF="h_color_setup">Descriptions of the available commands</A>
32144 Look <A HREF="h_edit_nav_cmds">here</A>
32145 to see the available Editing and Navigation commands.
32147 <End of help on this topic>
32150 ====== h_config_title_color =====
32153 <TITLE>OPTION: Title Color</TITLE>
32156 <H1>OPTION: Title Color</H1>
32158 Sets the color Alpine uses for the titlebar (the top line on the screen).
32159 The foreground color is the color of the actual character and the
32160 background color is the color of the area behind the character.
32161 By default, the Title Color is black characters on a yellow background.
32163 The actual titlebar color may be different from the Title Color if
32165 <A HREF="h_config_titlebar_color_style">"<!--#echo var="VAR_titlebar-color-style"-->"</A>
32166 is set to some value other than the default.
32167 It may also be different if the current folder is closed and the
32168 <A HREF="h_config_titleclosed_color">Title Closed Color</A>
32169 color is set to something different from the Title Color.
32171 <A HREF="h_color_setup">Descriptions of the available commands</A>
32173 Look <A HREF="h_edit_nav_cmds">here</A>
32174 to see the available Editing and Navigation commands.
32176 <End of help on this topic>
32179 ====== h_config_titleclosed_color =====
32182 <TITLE>OPTION: Title Closed Color</TITLE>
32185 <H1>OPTION: Title Closed Color</H1>
32187 Sets the color Alpine uses for the titlebar (the top line on the screen)
32188 when the current folder is closed.
32189 The foreground color is the color of the actual character and the
32190 background color is the color of the area behind the character.
32191 By default, the Title Color Closed Color is white characters on a red background.
32193 By setting this color to something noticeable you will be alerted to the
32194 fact that the current folder is closed, perhaps unexpectedly.
32196 <End of help on this topic>
32199 ====== h_config_status_color =====
32202 <TITLE>OPTION: Status Color</TITLE>
32205 <H1>OPTION: Status Color</H1>
32207 Sets the color Alpine uses for status messages written to the message
32208 line near the bottom of the screen.
32209 The foreground color is the color of the actual character and the
32210 background color is the color of the area behind the character.
32211 By default, the Status Color is the same as the Reverse Color.
32213 <A HREF="h_color_setup">Descriptions of the available commands</A>
32215 Look <A HREF="h_edit_nav_cmds">here</A>
32216 to see the available Editing and Navigation commands.
32218 <End of help on this topic>
32221 ====== h_config_index_opening_color =====
32224 <TITLE>OPTION: Index Opening Color</TITLE>
32227 <H1>OPTION: Index Opening Color</H1>
32229 With some setups the text of the subject is followed
32230 by the opening text of the message if there is any room available in the index line.
32231 If you have configured your
32232 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
32233 to include one of the Subject tokens that causes this behavior
32234 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), you may set the color of
32235 this opening text with this option.
32236 This coloring takes place for all but the current index line, and the Opening
32237 Color appears to be in front of any color from an Index Color Rule.
32239 By default the Index Opening Color is gray characters on a white background.
32242 <A HREF="h_color_setup">Descriptions of the available commands</A>
32244 Look <A HREF="h_edit_nav_cmds">here</A>
32245 to see the available Editing and Navigation commands.
32247 <End of help on this topic>
32250 ====== h_config_index_pri_color =====
32253 <TITLE>OPTION: Index Priority Symbol Colors</TITLE>
32256 <H1>OPTION: Index Priority Symbol Colors</H1>
32258 The X-Priority header is a non-standard header that is used in a
32259 somewhat standard way by many mail programs.
32260 Alpine expects the value of this header to be a digit with a value
32261 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
32262 Alpine can be made to display an indication of this priority in
32263 messages by use of one of the tokens
32264 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
32265 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
32266 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
32269 You may set the color used to draw these tokens by use of the colors
32270 Index High Priority Symbol Color and Index Low Priority Symbol Color.
32271 This coloring takes place for all but the current index line, and the Priority
32272 Color appears to be in front of any color from an Index Color Rule.
32273 If the priority has a value of 1 or 2 the High Priority color will be
32275 and if the value is 4 or 5 the Low Priority color will be used.
32277 If you don't set these colors the index line will be colored in the same color as
32278 the bulk of the index line.
32281 <A HREF="h_color_setup">Descriptions of the available commands</A>
32283 Look <A HREF="h_edit_nav_cmds">here</A>
32284 to see the available Editing and Navigation commands.
32286 <End of help on this topic>
32289 ====== h_config_index_subject_color =====
32292 <TITLE>OPTION: Index Subject Color</TITLE>
32295 <H1>OPTION: Index Subject Color</H1>
32297 You may set the color used to draw the Subject part of the index line.
32298 This coloring takes place for all but the current index line, and the Subject
32299 Color appears to be in front of any color from an Index Color Rule.
32301 If you don't set this color it will be colored in the same color as
32302 the bulk of the index line.
32305 <A HREF="h_color_setup">Descriptions of the available commands</A>
32307 Look <A HREF="h_edit_nav_cmds">here</A>
32308 to see the available Editing and Navigation commands.
32310 <End of help on this topic>
32313 ====== h_config_index_from_color =====
32316 <TITLE>OPTION: Index From Color</TITLE>
32319 <H1>OPTION: Index From Color</H1>
32321 You may set the color used to draw the From part of the index line.
32322 This coloring takes place for all but the current index line, and the From
32323 Color appears to be in front of any color from an Index Color Rule.
32325 If you don't set this color it will be colored in the same color as
32326 the bulk of the index line.
32329 <A HREF="h_color_setup">Descriptions of the available commands</A>
32331 Look <A HREF="h_edit_nav_cmds">here</A>
32332 to see the available Editing and Navigation commands.
32334 <End of help on this topic>
32337 ====== h_config_index_arrow_color =====
32340 <TITLE>OPTION: Index Arrow Color</TITLE>
32343 <H1>OPTION: Index Arrow Color</H1>
32345 If you have configured your
32346 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
32347 to include the "ARROW" token, you may set the color of
32348 the arrow displayed with this option.
32349 If you don't set the color it will be colored in the same color as
32350 the bulk of the index line.
32353 <A HREF="h_color_setup">Descriptions of the available commands</A>
32355 Look <A HREF="h_edit_nav_cmds">here</A>
32356 to see the available Editing and Navigation commands.
32358 <End of help on this topic>
32361 ====== h_config_index_color =====
32364 <TITLE>OPTION: Index Colors</TITLE>
32367 <H1>OPTION: Index Colors</H1>
32369 You may add color to the single character symbols that give the status
32370 of each message in the MESSAGE INDEX.
32371 By default the characters "+", "*", "D",
32372 "A", and "N" show up near the left hand side of the
32373 screen depending on whether the message is addressed to you, and whether
32374 the message is marked Important, is Deleted, is Answered, or is New.
32375 The color for each of those characters may be specified by setting the
32376 "Index-to-me" Symbol Color,
32377 the "Index-important" Symbol Color,
32378 the "Index-deleted" Symbol Color,
32379 the "Index-answered" Symbol Color,
32380 and the "Index-new" Symbol Color.
32381 There are also two other symbol colors called "Index-recent"
32382 and "Index-unseen".
32383 These two colors will only be used if you have configured your
32384 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
32385 to include the "IMAPSTATUS" or "SHORTIMAPSTATUS" token.
32387 The default colors for these symbols are:
32389 <TR> <TD> Index-to-me </TD> <TD> black on cyan </TD> </TR>
32390 <TR> <TD> Index-important </TD> <TD> white on bright red </TD> </TR>
32391 <TR> <TD> Index-deleted </TD> <TD> same as Normal Color </TD> </TR>
32392 <TR> <TD> Index-answered </TD> <TD> bright red on yellow </TD> </TR>
32393 <TR> <TD> Index-new </TD> <TD> white on magenta </TD> </TR>
32394 <TR> <TD> Index-recent </TD> <TD> same as Normal Color </TD> </TR>
32395 <TR> <TD> Index-unseen </TD> <TD> same as Normal Color </TD> </TR>
32398 Besides coloring the message status symbols, you may also color the
32400 This is done by using the
32401 <A HREF="h_rules_incols">SETUP INDEX LINE COLORS</A> screen, which you
32402 may get to with the commands <EM>S</EM>etup/<EM>R</EM>ules/<EM>I</EM>ndexcolor.
32403 When the entire line is colored that color will be "behind" the
32404 status symbol colors talked about in the paragraph above.
32407 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
32408 in the index using the
32409 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>);
32410 the <A HREF="h_config_index_arrow_color">ARROW</A> cursor;
32412 <A HREF="h_config_index_subject_color">Index Subject Color</A>;
32413 the From field using
32414 <A HREF="h_config_index_from_color">Index From Color</A>;
32416 <A HREF="h_config_index_opening_color">Index Opening</A> text.
32418 <A HREF="h_color_setup">Descriptions of the available commands</A>
32420 Look <A HREF="h_edit_nav_cmds">here</A>
32421 to see the available Editing and Navigation commands.
32423 <End of help on this topic>
32426 ====== h_config_metamsg_color =====
32429 <TITLE>OPTION: Meta-Message Color</TITLE>
32432 <H1>OPTION: Meta-Message Color</H1>
32434 Sets the color Alpine uses in the MESSAGE TEXT screen for messages to you
32435 that aren't part of the message itself.
32436 For example, an attachment that isn't shown might produce a meta
32437 message something like:
32439 <CENTER><SAMP> [ Part 2, "comment" Text/PLAIN (Name: "file") ]</SAMP></CENTER>
32442 <A HREF="h_config_quote_suppression"><!--#echo var="VAR_quote-suppression-threshold"--></A>
32443 option you might see
32445 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
32447 Warnings about suspicious looking URLs in HTML will also be colored
32450 The foreground color is the color of the actual character and the
32451 background color is the color of the area behind the character.
32452 By default, the Meta-Message Color is black characters on a yellow background.
32454 <A HREF="h_color_setup">Descriptions of the available commands</A>
32456 Look <A HREF="h_edit_nav_cmds">here</A>
32457 to see the available Editing and Navigation commands.
32459 <End of help on this topic>
32462 ====== h_config_keylabel_color =====
32465 <TITLE>OPTION: KeyLabel Color</TITLE>
32468 <H1>OPTION: KeyLabel Color</H1>
32470 Sets the color Alpine uses for the labels of the keys in the two-line
32471 menu at the bottom of the screen.
32472 For example, some of the screens have a "P PrevMsg" command.
32473 This option sets the color used when displaying "PrevMsg".
32474 The foreground color is the color of the actual character and the
32475 background color is the color of the area behind the character.
32476 By default, the KeyLabel Color is the same as the Normal Color.
32478 WARNING: Some terminal emulators have the property that the screen will scroll
32479 down one line whenever a character is written to the character cell in the
32480 lower right corner of the screen.
32481 Alpine can usually avoid writing a character in that corner of the screen.
32482 However, if you have defined a KeyLabel Color then Alpine does have to write
32483 a character in that cell in order to color the cell correctly.
32484 If you find that your display sometimes scrolls up a line this could be
32486 The most obvious symptom is probably that the titlebar at the top of the
32487 screen scrolls off the screen.
32488 Try setting KeyLabel Color to Default to see if that fixes the problem.
32490 <A HREF="h_color_setup">Descriptions of the available commands</A>
32492 Look <A HREF="h_edit_nav_cmds">here</A>
32493 to see the available Editing and Navigation commands.
32495 <End of help on this topic>
32498 ====== h_config_keyname_color =====
32501 <TITLE>OPTION: KeyName Color</TITLE>
32504 <H1>OPTION: KeyName Color</H1>
32506 Sets the color Alpine uses for the names of the keys in the two-line
32507 menu at the bottom of the screen.
32508 For example, some of the screens have a "P PrevMsg" command.
32509 This option sets the color used when displaying the "P".
32510 The foreground color is the color of the actual character and the
32511 background color is the color of the area behind the character.
32512 By default, the KeyName Color is the same as the Reverse Color.
32514 <A HREF="h_color_setup">Descriptions of the available commands</A>
32516 Look <A HREF="h_edit_nav_cmds">here</A>
32517 to see the available Editing and Navigation commands.
32519 <End of help on this topic>
32522 ====== h_config_slctbl_color =====
32525 <TITLE>OPTION: Selectable Item Color</TITLE>
32528 <H1>OPTION: Selectable Item Color</H1>
32530 Sets the color Alpine uses for selectable items, such as URLs.
32531 The foreground color is the color of the actual character and the
32532 background color is the color of the area behind the character.
32533 By default, the Selectable Item Color is the same as the Normal Color,
32534 except that it is bold.
32536 <A HREF="h_color_setup">Descriptions of the available commands</A>
32538 Look <A HREF="h_edit_nav_cmds">here</A>
32539 to see the available Editing and Navigation commands.
32541 <End of help on this topic>
32544 ====== h_config_quote_color =====
32547 <TITLE>OPTION: Quote Colors</TITLE>
32550 <H1>OPTION: Quote Colors</H1>
32552 Sets the colors Alpine uses for coloring quoted text in the MESSAGE TEXT
32554 If a line begins with a > character (or space followed by >)
32555 it is considered a quote.
32556 That line will be given the Quote1 Color (first level quote).
32557 If there is a second level of quoting then the Quote2 Color will be used.
32558 Alpine considers there to be a second level of quoting if that first > is
32559 followed by another > (or space followed by >).
32560 If there are characters other than whitespace and > signs, then it isn't
32561 considered another level of quoting.
32562 Similarly, if there is a third level of quoting the Quote3 Color will be
32564 If there are more levels after that the Quote Colors are re-used.
32565 If you define all three colors then it would repeat like Color1, Color2, Color3,
32566 Color1, Color2, Color3, ...
32567 If you only define the first two it would be
32568 Color1, Color2, Color1, Color2, ...
32569 If you define only the Quote1 Color, then the entire quote would be that
32570 color regardless of the quoting levels.
32571 By default, the Quote1 Color is black characters on a greenish-blue background;
32572 the Quote2 Color is black characters on a dull yellow background; and
32573 the Quote3 Color is black characters on a green background.
32575 <A HREF="h_color_setup">Descriptions of the available commands</A>
32577 Look <A HREF="h_edit_nav_cmds">here</A>
32578 to see the available Editing and Navigation commands.
32580 <End of help on this topic>
32583 ====== h_config_folder_color =====
32586 <TITLE>OPTION: Folder Color</TITLE>
32589 <H1>OPTION: Folder Color</H1>
32591 Sets the colors Alpine uses for coloring a folder in the FOLDER LIST
32592 screen. By default, the Folder Color is the normal text color.
32595 If you set a color for this feature, other than the normal color
32596 (the default), or a color for
32597 <A HREF="h_config_directory_color">Directory Color</A>, then directories
32598 will be colored according to the color specified in the
32599 <A HREF="h_config_directory_color">Directory Color</A> option. In this
32600 case, the color will be the only indication that the colored name
32601 refers to a directory. The normal behavior is that Alpine
32602 indicates that a name refers to a directory by appending a
32603 separator (like "/" or ".") to the name of
32607 If a folder is a directory, then the folder name will be painted
32608 according to the color defined by this variable, and a separator
32609 indicator (like "/" or ".") will be added
32611 indicator will be painted according to the color defined in the
32612 <A HREF="h_config_directory_color">Directory Color</A> option.
32615 <End of help on this topic>
32618 ====== h_config_directory_color =====
32621 <TITLE>OPTION: Directory Color</TITLE>
32624 <H1>OPTION: Directory Color</H1>
32626 Sets the colors Alpine uses for coloring a directory in the FOLDER LIST
32627 screen. By default, the Folder Color is the normal text color.
32629 If you set a color for this feature, other than the normal color
32630 (the default), or a color for
32631 <A HREF="h_config_folder_color">Folder Color</A>, then folders
32632 will be colored according to the color specified in the
32633 <A HREF="h_config_folder_color">Folder Color</A> option. In this
32634 case, the color will be the only indication that the colored name
32635 refers to a directory. The normal behavior is that Alpine
32636 indicates that a name refers to a directory by appending a
32637 separator (like "/" or ".") to the name of
32640 If a folder is a directory, then the folder name will be painted
32641 according to the color defined by the option
32642 <A HREF="h_config_folder_color">Folder Color</A>, and the separator
32643 indicator (like "/" or ".") will be added
32644 after the name. That
32645 indicator will be painted according to the color defined in this
32648 <End of help on this topic>
32651 ====== h_config_folder_list_color =====
32654 <TITLE>OPTION: Folder-List Color</TITLE>
32657 <H1>OPTION: Folder-List Color</H1>
32659 Sets the colors Alpine uses for coloring normal text in the FOLDER LIST
32660 screen. By default, the Folder-List Color is the normal text color.
32662 This text refers to the informative text that Alpine displays so you
32663 can recognize each collection. The color of the content of each collection
32664 is determined by the options <A HREF="h_config_folder_color">Folder Color</A>
32665 and <A HREF="h_config_directory_color">Directory Color</A>.
32668 <A HREF="h_config_folder_color">Folder Color</A>
32669 and <A HREF="h_config_directory_color">Directory Color</A>, configuring
32670 this option does not affect the way that Alpine reports folders,
32671 directories and folders that are directories.
32673 <End of help on this topic>
32676 ====== h_config_incunseen_color =====
32679 <TITLE>OPTION: Incoming Unseen Color</TITLE>
32682 <H1>OPTION: Incoming Unseen Color</H1>
32685 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
32686 is turned on it is possible to highlight the folders that contain
32687 unseen messages by coloring them with this color.
32688 By default, this is the same as the Normal Color and no highlighting is done.
32690 Usually the "current" folder (the folder the cursor is on)
32691 is highlighted using reverse video.
32692 If the current folder is colored because it contains unseen messages then
32693 the color used to show that it is also the current folder is controlled
32695 <A HREF="h_config_index_color_style"><!--#echo var="VAR_current-indexline-style"--></A>
32696 feature at the top of the SETUP COLOR screen.
32698 <A HREF="h_color_setup">Descriptions of the available commands</A>
32700 Look <A HREF="h_edit_nav_cmds">here</A>
32701 to see the available Editing and Navigation commands.
32703 <End of help on this topic>
32706 ====== h_config_signature_color =====
32709 <TITLE>OPTION: Signature Color</TITLE>
32712 <H1>OPTION: Signature Color</H1>
32714 Sets the color Alpine uses for coloring the signature in the MESSAGE TEXT
32715 screen. According to USENET conventions, the signature is defined as the
32716 paragraph following the "sigdashes", that is, the special line
32717 consisting of the three characters
32718 "-- " (i.e., dash, dash, and space). Alpine allows for one
32719 empty line right after the sigdashes to be considered as part of the
32721 By default, the Signature Color is blue characters on a white background.
32723 <A HREF="h_color_setup">Descriptions of the available commands</A>
32725 Look <A HREF="h_edit_nav_cmds">here</A>
32726 to see the available Editing and Navigation commands.
32728 <End of help on this topic>
32731 ====== h_config_prompt_color =====
32734 <TITLE>OPTION: Prompt Color</TITLE>
32737 <H1>OPTION: Prompt Color</H1>
32739 Sets the color Alpine uses for confirmation prompts and questions that
32740 appear in the status line near the bottom of the screen.
32741 The foreground color is the color of the actual character and the
32742 background color is the color of the area behind the character.
32743 By default, the Prompt Color is the same as the Reverse Color.
32745 <A HREF="h_color_setup">Descriptions of the available commands</A>
32747 Look <A HREF="h_edit_nav_cmds">here</A>
32748 to see the available Editing and Navigation commands.
32750 <End of help on this topic>
32753 ====== h_config_header_general_color =====
32756 <TITLE>OPTION: Header General Color</TITLE>
32759 <H1>OPTION: Header General Color</H1>
32761 Sets the color Alpine uses for the headers of a message in the MESSAGE TEXT
32763 The foreground color is the color of the actual character and the
32764 background color is the color of the area behind the character.
32765 By default, this is the same as the Normal Color.
32767 It is also possible to set the colors for specific header fields, for
32768 example the Subject, using
32769 <A HREF="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></A>.
32770 If both a Header General Color and a specific Viewer Header Color are set
32771 the specific color will override the general color, as you would expect.
32773 <A HREF="h_color_setup">Descriptions of the available commands</A>
32775 Look <A HREF="h_edit_nav_cmds">here</A>
32776 to see the available Editing and Navigation commands.
32778 <End of help on this topic>
32781 ====== h_config_incol =====
32784 <TITLE>Index Line Color</TITLE>
32787 <H1>Index Line Color</H1>
32789 This option is used to set the color of a line in the index when the
32790 message for that line matches the Pattern.
32791 This colors the whole index line, except possibly the status letters,
32792 which may be colored separately using the
32793 <A HREF="h_color_setup">Setup Kolor</A> screen.
32794 The foreground color is the color of the actual characters and the
32795 background color is the color of the area behind the characters.
32797 <A HREF="h_color_setup">Descriptions of the available commands</A>
32799 Look <A HREF="h_edit_nav_cmds">here</A>
32800 to see the available Editing and Navigation commands.
32802 <End of help on this topic>
32805 ====== h_config_usetransparent_color =====
32808 <TITLE>OPTION: Use Transparent Color</TITLE>
32811 <H1>OPTION: Use Transparent Color</H1>
32813 This is a special color supported by some terminal emulators.
32814 It is intended to result in the default foreground or background color
32815 from the terminal emulator.
32816 This is the color the terminal was displaying characters in before you started Alpine.
32817 The reason it is called Transparent is because you could set the foreground color
32818 to some specific color, like Red, and then set the background color to the
32819 Transparent Color. If it works as expected, the background color from the terminal
32820 window in which Alpine is running will show through but with the Red characters
32823 <A HREF="h_color_setup">Descriptions of the available commands</A>
32825 Look <A HREF="h_edit_nav_cmds">here</A>
32826 to see the available Editing and Navigation commands.
32828 <End of help on this topic>
32831 ====== h_config_usenormal_color =====
32834 <TITLE>OPTION: Use Normal Color</TITLE>
32837 <H1>OPTION: Use Normal Color</H1>
32839 When you use this color value, the actual color used will be the same
32840 as the corresponding Normal Color.
32841 For example if your Normal Color is black on white and you set both
32842 the foreground and background colors here to use the Normal Color, you'll
32843 get black on white. If you later change the Normal Color to red on blue
32844 this color will also change to red on blue.
32846 <A HREF="h_color_setup">Descriptions of the available commands</A>
32848 Look <A HREF="h_edit_nav_cmds">here</A>
32849 to see the available Editing and Navigation commands.
32851 <End of help on this topic>
32854 ====== h_config_usenone_color =====
32857 <TITLE>OPTION: Use None Color</TITLE>
32860 <H1>OPTION: Use None Color</H1>
32862 This is a special color that simply means to leave the color alone.
32863 It is useful for Index symbols and for Keyword Colors used in the Subject
32864 field of an index line.
32865 The most likely use is to set an explicit foreground color and then set
32866 the background color to the None Color.
32867 That will cause the symbol or keyword to be drawn in the foreground color
32868 with a background equal to whatever color the rest of the index line is already
32870 You will see no visible effect unless you have assigned Indexcolor Rules to
32871 color index lines or you have set an actual color for the Reverse Color.
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_dflt_color =====
32884 <TITLE>OPTION: Default Color</TITLE>
32887 <H1>OPTION: Default Color</H1>
32889 Setting default will cause the color to be the default color.
32890 Unsetting default is normally done by choosing a color, but in some cases
32891 you may want to declare the current default color to be your non-default
32893 For example, the default Keyname Color is the same as the Reverse Color.
32894 Whenever the Reverse Color changes the Keyname Color will also change, unless
32895 you've changed it or unset the default box.
32897 <A HREF="h_color_setup">Descriptions of the available commands</A>
32899 Look <A HREF="h_edit_nav_cmds">here</A>
32900 to see the available Editing and Navigation commands.
32902 <End of help on this topic>
32905 ====== h_config_bold_slctbl =====
32908 <TITLE>OPTION: Bold</TITLE>
32911 <H1>OPTION: Bold</H1>
32913 The color for this particular section may have the Bold attribute turned
32915 Setting bold will cause the characters to be bold.
32917 <A HREF="h_color_setup">Descriptions of the available commands</A>
32919 Look <A HREF="h_edit_nav_cmds">here</A>
32920 to see the available Editing and Navigation commands.
32922 <End of help on this topic>
32925 ====== h_config_kw_color =====
32928 <TITLE>OPTION: Keyword Colors</TITLE>
32931 <H1>OPTION: Keyword Colors</H1>
32933 Sets the colors Alpine uses for Keyword fields in the MESSAGE INDEX screen.
32934 Keywords are displayed as part of the Subject by default.
32935 They are also displayed as part of the Subject if the tokens
32936 "SUBJKEY", "SUBJKEYTEXT", "SUBJKEYINIT", or "SUBJKEYINITTEXT" are used in the
32937 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
32938 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
32939 screen by using the "KEY" or "KEYINIT" tokens.
32941 For example, you might have set up a Keyword
32942 "Work" using the
32943 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
32944 You could cause that Keyword to show up as a special color
32945 by setting up the Keyword Color using this option, and then including it
32946 in the MESSAGE INDEX screen using one of the tokens listed above in the
32947 <!--#echo var="VAR_index-format"-->.
32949 <A HREF="h_color_setup">Descriptions of the available commands</A>
32951 Look <A HREF="h_edit_nav_cmds">here</A>
32952 to see the available Editing and Navigation commands.
32954 <End of help on this topic>
32957 ====== h_config_customhdr_color =====
32960 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></TITLE>
32963 <H1>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></H1>
32965 Sets the colors Alpine uses for specific header fields in the MESSAGE TEXT screen.
32966 For example, you may set the color of the Subject header or the From header.
32967 The foreground color is the color of the actual character and the
32968 background color is the color of the area behind the character.
32970 In addition to setting the colors for particular headers (like the Subject)
32971 you may also set a color to be used for all headers unless overridden by a
32972 more specific Viewer Header Color.
32974 <A HREF="h_config_header_general_color">Header General Color</A>.
32977 there is an additional line on the
32978 screen labeled "Pattern to match".
32979 If you leave that blank, then the whole field for that header will
32981 However, if you give a pattern to match, the coloring will only take place
32982 if there is a match for that pattern in the value of the field.
32983 For example, if you are working on a color for the Subject header and
32984 you fill in a pattern of "important", then only Subjects that
32985 contain the word "important" will be colored.
32987 If the pattern you enter is a comma-separated list of patterns, then coloring
32988 happens if any of those patterns matches.
32990 <A HREF="h_color_setup">Descriptions of the available commands</A>
32992 Look <A HREF="h_edit_nav_cmds">here</A>
32993 to see the available Editing and Navigation commands.
32995 <End of help on this topic>
32998 ====== h_config_indextoken_color =====
33001 <TITLE>OPTION: <!--#echo var="VAR_index-token-colors"--></TITLE>
33004 <H1>OPTION: <!--#echo var="VAR_index-token-colors"--></H1>
33006 This option allows you to set up the color in which any token, not specified by the
33007 previous options, will be colored in the MESSAGE INDEX screen.
33009 In order to use this option, you must press the "I" <B>IndxHdr</B> command, and add
33010 a token that can be used in the index format.
33011 The list of available tokens is <A HREF="h_index_tokens">here</A>.
33013 If you fail to enter a valid token your entry will be ignored, and you will be asked to
33014 enter a new one. Once you have entered a valid token, a line will be added to the
33015 configuration screen that you can use to set up the colors in which that token will
33016 be painted. This is done in the same way that you configure colors for other
33019 <A HREF="h_color_setup">Descriptions of the available commands</A>
33021 Look <A HREF="h_edit_nav_cmds">here</A>
33022 to see the available Editing and Navigation commands.
33024 <End of help on this topic>
33027 ====== h_config_customhdr_pattern =====
33030 <TITLE>OPTION: Viewer Header Color Pattern</TITLE>
33033 <H1>OPTION: Viewer Header Color Pattern</H1>
33035 If you leave this blank, then the whole field for the header will
33037 If you give a pattern to match, the coloring will only take place
33038 if there is a match for that pattern in the value of the field.
33039 For example, if you are working on a color for the Subject header and
33040 you fill in a pattern of "important", then only Subjects that
33041 contain the word "important" will be colored.
33043 For address headers (like From and To) and for the Newsgroups header,
33044 a pattern match will cause only the matched addresses or newsgroups to be
33046 If there is no pattern to match, then all of the addresses or newsgroups
33047 in the relevant header will be colored.
33049 The matching pattern may be a comma-separated list of patterns to match
33050 instead of a single pattern.
33051 For example, you could use the pattern "important,urgent" which would
33052 cause a match if either the word "important" or the word
33053 "urgent" appeared in the value of the header.
33054 You could list several comma-separated email addresses in the Header
33055 From Color pattern so that those addresses will be colored when any of
33056 them appear in the From header.
33058 To add a new matching pattern or change the existing pattern use the
33059 <!--chtml if pinemode="function_key"-->
33064 "Change" command that is available when the "Pattern to
33065 match" line is highlighted.
33067 <!--chtml if pinemode="function_key"-->
33072 "Delete" command may be used to quickly remove all patterns
33073 for a particular header.
33075 <End of help on this topic>
33078 ====== h_color_setup =====
33081 <TITLE>SETUP COLOR COMMANDS</TITLE>
33084 <H1>SETUP COLOR COMMANDS</H1>
33085 <!--chtml if pinemode="function_key"-->
33087 Available Commands -- Group 1
33088 -------------------------------
33089 F1 Display this help text
33090 F2 Show other available commands
33091 F3 Exit to MAIN MENU
33092 F4 Select the highlighted foreground or background color
33093 F5 Move to previous line
33094 F6 Move to next line
33097 F9 Add a config section for a header field
33098 F10 Restore all default colors (for all sections)
33099 F11 Print color configuration screen
33100 F12 Whereis (search for word)
33102 Available Commands -- Group 2
33103 -------------------------------
33104 F1 Display this help text
33105 F2 Show other available commands
33106 F5 Delete config section for highlighted header field
33107 F6 Shuffle the order of Header Color sections
33112 -------------------------------------------------
33113 ? Display this help text E Exit back to MAIN MENU
33114 P Previous Line N Next Line
33115 - Previous page Spc (space bar) Next page
33116 W WhereIs (search for word) % Print color configuration screen
33118 Color Setup Commands
33119 ------------------------------------------------
33120 * Select the highlighted foreground or background color
33121 A Add a config section for a header field
33122 D Delete config section for highlighted header field
33123 R Restore all default colors (for all sections)
33124 $ Shuffle the order of Header Color sections
33128 <H2>Description of the Setup Color Screen</H2>
33130 From this screen you may turn on color and set the colors of
33131 various parts of the Alpine display.
33132 For help on turning on color move your cursor into the Color Style section
33133 at the top of the Setup Color screen and ask for help.
33136 There are several sections in the Setup Color Screen.
33137 At the top are some settings that handle the style of color used
33138 with your terminal emulator (UNIX only), and some settings that
33139 control how the current indexline and the titlebar are colored.
33140 After that comes a long section called GENERAL COLORS that allows
33141 you to set the color of many elements in the Alpine screens.
33142 For example, the color of the titlebar, status messages,
33143 selectable links, quotes and signatures in messages, and so on.
33144 After that is a section called INDEX COLORS that allows you to
33145 set the colors of various pieces of the displayed index lines in
33146 the MESSAGE INDEX screen.
33147 The next section is HEADER COLORS. This is for coloring headers of
33148 messages in the MESSAGE TEXT screen in just about any way you would like.
33149 Finally, the KEYWORD COLORS section allows you to highlight
33150 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
33151 in the MESSAGE INDEX screen.
33154 To change a color, highlight the color you want to change (for example,
33155 the Status Color) by moving
33156 the cursor into it.
33157 You may want to read the help text for the color to see a brief desription
33158 of what you are coloring.
33159 Then press "C" for Change to set the color to something new.
33160 That will put you into a screen with two columns of colors, one for
33161 the foreground color and one for the background color.
33162 The foreground color is just the color you want the actual characters
33163 to be and the background color is the color of the rest of the rectangle
33164 behind the characters.
33165 Select the foreground and background colors desired by using the Next and
33166 Prev keys to highlight the color, and the * command to select it.
33168 To set a color to its default value, set the X in the Default line at
33169 the bottom of the list of colors.
33172 The HEADER COLORS section is a little bit different from the others.
33173 Besides coloring the specific fields that Alpine knows about, you may also
33174 color specific header fields when viewing a message in the MESSAGE TEXT
33176 For example, you may color the Subject header a particular color.
33177 There are a few commands for use with headers.
33178 The "AddHeader" command adds a section to the color
33179 configuration screen that allows you to set the color for that header.
33180 You'll be asked for the name of the header field you want to color.
33181 If you wanted to color the Subject, you would answer
33182 with the word "subject".
33183 Once you've added a header field, the color setting works just like the
33184 other color fields, except that there is an additional line on the
33185 configuration screen labeled "Pattern to match".
33186 If you leave that blank, then the whole field for that header will always
33188 However, if you give a pattern to match, the coloring will only take place
33189 if there is a match for that pattern in the value of the field.
33190 For example, if you are working on a color for the Subject header and
33191 you fill in a pattern of "important", then only Subjects that
33192 contain the word "important" will be colored.
33194 The "DeleteHdr" command removes a header section from the
33195 configuration altogether.
33196 The "Shuffle" command changes the order of header sections.
33197 This is only necessary if you use header sections with pattern fields.
33198 For example, if you have two Subject sections, one with one pattern and
33199 another with another pattern, and the subject for a particular message
33200 happens to match both, then the color from the first match is used.
33203 The command "RestoreDefs" will restore all of the default colors.
33204 Each section will change to the default value used for that section when
33205 color is first enabled.
33206 When you restore all default colors the color settings for the Header Colors
33207 will be unset (since that's the default), but the header fields you've
33208 added will remain so that you may easily reset them.
33209 In order to get rid of them completely you'd have to use
33210 the "DeleteHdr" command.
33213 Remember that <A HREF="h_rules_incols">Index Line Colors</A>
33214 may be set with matching rules and that is configured separately from
33215 the rest of the color settings described here.
33216 It is configured in the Setup/Rules/Indexcolors section of the configuration screen
33217 instead of in the Setup/Kolor section.
33220 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33222 <End of help on this topic>
33225 ====== h_config_news_uses_recent ======
33228 <TITLE>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></TITLE>
33231 <H1>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></H1>
33233 This feature causes certain messages to be marked as "New" in the
33234 MESSAGE INDEX of newsgroups.
33235 This feature is set by default.
33239 When opening a newsgroup, Alpine will consult your "newsrc" file and
33240 determine the last message you have previously disposed of via the "D"
33241 key. If this feature is set, any subsequent messages will be shown in the
33242 Index with an "N", and the first of these messages will be highlighted.
33243 Although this is only an approximation of true "New" or "Unseen"
33244 status, it provides a useful cue to distinguish more-or-less recent
33245 messages from those you have seen previously, but are not yet ready to
33250 Background: your "newsrc" file (used to store message status information
33251 for newsgroups) is only capable of storing a single flag, and Alpine uses
33252 this to record whether or not you are "done with" a message, as
33253 indicated by marking the message as "Deleted". Unfortunately, this
33254 means that Alpine has no way to record exactly which messages you have
33255 previously seen, so it normally does not show the "N" status flag for
33256 any messages in a newsgroup. This feature enables a starting
33257 *approximation* of seen/unseen status that may be useful.
33259 <End of help on this topic>
33262 ====== h_config_expose_hidden_config =====
33265 <TITLE>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></TITLE>
33268 <H1>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></H1>
33270 If set, this causes configuration options and features that are normally
33271 hidden from view to be editable in the Setup/Config screen.
33274 The purpose of this feature is to allow you to change configuration
33275 features and variables that are normally hidden.
33276 This is particularly useful if you are using a remote configuration,
33277 where it is difficult to edit the contents manually, but it may also be used
33278 on a local pinerc configuration file.
33280 If set, several configuration variables and features that are normally
33281 hidden from view will show up in the Setup/Configuration screen.
33282 They will be at the bottom of the configuration screen.
33283 You can find them by searching for the words "hidden configuration".
33286 Note that this is an advanced feature that should be used with care.
33287 The reason that this part of the configuration is normally hidden is because
33288 there is a significant potential for causing problems if you change these
33290 If something breaks after a change try changing it back to see if that is
33291 what is causing the problem.
33292 There are also some variables that are normally hidden because they are
33293 manipulated through Alpine in other ways.
33294 For example, colors are normally set using the Setup/Kolors screen and
33295 the "<!--#echo var="VAR_address-book"-->" variable is normally set using
33296 the Setup/AddressBooks screen, so there is little reason to edit these directly.
33297 The "<!--#echo var="VAR_incoming-folders"-->" variable is normally changed by using
33298 the Add, Delete, and Rename commands in the FOLDER LIST screen,
33299 and the "<!--#echo var="VAR_last-time-prune-questioned"-->" variable is normally used
33300 internally by Alpine and not set directly by the user.
33303 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33305 <End of help on this topic>
33308 ====== h_config_disable_signature_edit =====
33311 <TITLE>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></TITLE>
33314 <H1>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></H1>
33316 If set, this disables the editing of signature files from within
33317 the Setup/Config screen.
33320 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33322 <End of help on this topic>
33325 ====== h_config_disable_roles_templateedit =====
33328 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></TITLE>
33331 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></H1>
33333 If set, this disables the editing of template files within the
33337 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33339 <End of help on this topic>
33342 ====== h_config_disable_roles_sigedit =====
33345 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></TITLE>
33348 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></H1>
33350 If set, this disables the editing of signature files within the
33354 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33356 <End of help on this topic>
33359 ====== h_config_disable_roles_setup =====
33362 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></TITLE>
33365 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></H1>
33367 If set, this disables the Setup/Rules/Roles command.
33370 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33372 <End of help on this topic>
33375 ====== h_config_disable_pipes_in_templates =====
33378 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></TITLE>
33381 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></H1>
33383 By default, if a template file name is followed by a vertical bar (|) then
33384 that causes the file to be executed to produce the text for the template.
33385 If this feature is set, then this is not allowed.
33388 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33390 <End of help on this topic>
33393 ====== h_config_disable_pipes_in_sigs =====
33396 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></TITLE>
33399 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></H1>
33401 By default, if a signature file name is followed by a vertical bar (|) then
33402 that causes the file to be executed to produce the text for the signature.
33403 If this feature is set, then this is not allowed.
33406 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33408 <End of help on this topic>
33411 ====== h_config_disable_password_cmd =====
33414 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></TITLE>
33417 <H1>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></H1>
33419 If set, then the Setup/Newpassword command is disabled.
33422 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33424 <End of help on this topic>
33427 ====== h_config_disable_password_caching =====
33430 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></TITLE>
33433 <H1>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></H1>
33435 Normally, loginname/password combinations are cached in Alpine so that
33436 you do not have to enter the same password more than once in a session.
33437 A disadvantage to this approach is that the password must be stored in
33438 the memory image of the running Alpine in order that it can be re-used.
33439 In the event that Alpine crashes and produces a core dump, and that core
33440 dump is readable by others, the loginname and password could be read
33441 from the core dump.
33443 If this feature is set, then the passwords will not be cached and you
33444 will have to retype the password whenever Alpine needs it.
33445 Even with this feature set there is still some chance that the core
33446 file will contain a password, so care should be taken to make the
33447 core files unreadable.
33449 NOTE: If PASSFILE caching is enabled, this does not disable it.
33450 That is a separate and independent feature.
33452 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33454 <End of help on this topic>
33457 ====== h_config_disable_password_file_saving =====
33460 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></TITLE>
33463 <H1>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></H1>
33465 This feature changes the behavior of Alpine when a login name and password combination
33466 for a specific server is not found in the password file. The default behavior is that
33467 Alpine will ask the user if they wish to save this information in the password file for future
33468 use. It is assumed that if a user created a password file it is because they intend
33469 to use it, but in some instances a user might want to save some passwords and not others.
33470 In this case, enabling this feature will make Alpine not add any more passwords to the
33471 password file and will only use the passwords that it already saved. If you wish to allow
33472 Alpine to save more passwords in the password file, disable this feature.
33475 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33477 <End of help on this topic>
33480 ====== h_config_disable_kb_lock =====
33483 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></TITLE>
33486 <H1>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></H1>
33488 If set, then the Keyboard Lock command is removed from the MAIN MENU.
33491 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33493 <End of help on this topic>
33496 ====== h_config_disable_config_cmd =====
33499 <TITLE>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></TITLE>
33502 <H1>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></H1>
33504 If set, then the Setup/Config screen is disabled.
33507 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33509 <End of help on this topic>
33512 ====== h_config_allow_chg_from =====
33515 <TITLE>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></TITLE>
33518 <H1>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></H1>
33520 This feature affects Alpine's handling of the "From:" header field
33521 in the "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" configuration
33524 If this feature is set then the From line can be changed just like
33525 all the other header fields that can be changed.
33526 This feature defaults to <EM>ON</EM>.
33528 Even with this feature turned ON (the default) you will not be able
33529 to change the From header unless you add it to your list of
33530 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>.
33531 You may also want to change the
33532 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
33533 if you want the From header to always show up in the composer without
33534 having to type the Rich Headers command first.
33536 Note that many sites restrict the use of this feature in order to
33537 reduce the chance of falsified addresses and misdirected mail.
33538 If you want to change the value of what gets included in the From header
33539 in messages you send
33540 look <A HREF="h_config_change_your_from">here</A> for a description.
33543 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33545 <End of help on this topic>
33548 ====== h_config_disable_collate =====
33551 <TITLE>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></TITLE>
33554 <H1>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></H1>
33556 This is a hard to understand feature that should only be used in rare cases.
33557 Normally, the C function call
33559 <CENTER><SAMP>setlocale(LC_COLLATE, "")</SAMP></CENTER>
33562 If you want to try turning it off,
33563 setting this feature will turn it off.
33564 This part of the locale has to do with the sort order
33565 of characters in your locale.
33568 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33570 <End of help on this topic>
33573 ====== h_config_quell_attach_extra_prompt =====
33576 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></TITLE>
33579 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></H1>
33581 By default, when you attempt to view an attachment externally
33582 from the "Attachment View" screen, you are asked if you
33583 really want to view the selected attachment.
33586 If this feature is set, you will <B>not</B> be prompted to confirm
33587 your selection. Prior to Alpine and to Pine 4.50, the default behavior was to not
33588 prompt. This feature was added for those wanting to preserve that
33589 behavior (along with
33590 <A HREF="h_config_quell_attach_ext_warn"><!--#echo var="FEAT_quell-attachment-extension-warn"--></A>).
33594 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33596 <End of help on this topic>
33599 ====== h_config_quell_attach_ext_warn =====
33602 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></TITLE>
33605 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></H1>
33608 This feature suppresses the extra warning you can get when trying
33609 to view an attachment for which there is no mime-type match. Turning
33610 on this feature will just run the program according to extension
33611 instead of first warning the user that it will run according to the
33614 This feature can be used along side
33615 <A HREF="h_config_quell_attach_extra_prompt"><!--#echo var="FEAT_quell-attachment-extra-prompt"--></A>
33616 to preserve the behavior exhibited in Pine versions prior to Pine 4.50.
33619 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33621 <End of help on this topic>
33624 ====== h_config_mailcap_params =====
33627 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></TITLE>
33630 <H1>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></H1>
33632 If set, this will allow mailcap named parameter substitution to occur
33633 in mailcap entries.
33634 By default, this is turned off to prevent security problems that may occur
33635 with some incorrect mailcap configurations.
33636 For more information, see RFC1524 and look for "named parameters" in the
33640 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33642 <End of help on this topic>
33645 ====== h_config_disable_shared =====
33648 <TITLE>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></TITLE>
33651 <H1>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></H1>
33653 If this feature is set, the automatic search for namespaces "ftp",
33654 "imapshared", and "imappublic" by the underlying library
33656 The reason this feature exists is because there are some implementations
33657 of system password lookup routines that are very slow when presented with
33658 a long loginname that does not exist.
33659 This feature could be set to prevent the delay at startup time when the
33660 names above are searched for in the password file.
33663 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33665 <End of help on this topic>
33668 ====== h_config_hide_nntp_path =====
33671 <TITLE>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></TITLE>
33674 <H1>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></H1>
33676 Normally the Path header that Alpine generates when posting to a newsgroup
33677 contains the name of the computer from which the message is being sent and
33679 Some believe that this information is used by spammers.
33680 If this feature is set, that information will be replaced with the text
33682 <CENTER><SAMP>not-for-mail</SAMP></CENTER>
33686 It should be noted that many servers being connected to will still reveal
33687 the information that this feature attempts to protect.
33690 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33692 <End of help on this topic>
33695 ====== h_config_no_bezerk_zone =====
33698 <TITLE>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></TITLE>
33701 <H1>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></H1>
33703 POSIX mandates a timezone in UNIX mailbox format folder delimiters
33704 (the line that begins with From <SPACE>).
33705 Some versions of Berkeley mail have trouble with this, and don't recognize
33706 the line as a message delimiter.
33707 If this feature is set, the timezone will be left off the delimiter line.
33710 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33712 <End of help on this topic>
33715 ====== h_config_quell_domain_warn =====
33718 <TITLE>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></TITLE>
33721 <H1>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></H1>
33723 When your configuration is set up so that your domain name contains no dots,
33724 it is usually a configuration error.
33725 By default, Alpine will warn you about this when you start it up.
33726 You will see a warning message that looks like
33729 <CENTER><SAMP>Incomplete maildomain "<domain>".</SAMP></CENTER>
33732 If this feature is set, the warning is turned off.
33735 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33737 <End of help on this topic>
33740 ====== h_config_quell_imap_env =====
33743 <TITLE>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></TITLE>
33746 <H1>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></H1>
33748 In the MESSAGE INDEX screen, if the open folder is being accessed
33749 using IMAP, Alpine normally tries to paint the index lines on the screen
33750 as soon as the information arrives from the IMAP server.
33751 This means that the index information makes it onto the screen more quickly
33752 than it otherwise would.
33753 This sometimes results in behavior that bothers some users.
33754 For example, when paging to a new page of the index, it may be possible for
33755 the lines to be painted on the screen in a random order, rather than from
33759 Setting this feature causes Alpine to wait for all of the information
33760 to be gathered before it paints the index screen.
33761 Once it collects all of the information, the screen will be painted quickly
33762 from top to bottom.
33765 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33767 <End of help on this topic>
33770 ====== h_config_quell_news_env =====
33773 <TITLE>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></TITLE>
33776 <H1>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></H1>
33778 In the MESSAGE INDEX screen, if the open folder is being accessed
33779 using NNTP (News), Alpine normally tries to paint the index lines on the screen
33780 as soon as the information arrives from the NNTP server.
33781 This means that the index information makes it onto the screen more quickly
33782 than it otherwise would.
33783 This sometimes results in behavior that bothers some users.
33784 For example, when paging to a new page of the index, it may be possible for
33785 the lines to be painted on the screen in a random order, rather than from
33789 Setting this feature causes Alpine to wait for all of the information
33790 to be gathered before it paints the index screen.
33791 Once it collects all of the information, the screen will be painted quickly
33792 from top to bottom.
33795 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33797 <End of help on this topic>
33800 ====== h_config_quell_content_id =====
33803 <TITLE>FEATURE: <!--#echo var="FEAT_quell-content-id"--></TITLE>
33806 <H1>FEATURE: <!--#echo var="FEAT_quell-content-id"--></H1>
33808 This feature changes the behavior of Alpine when sending messages.
33809 It is intended to work around a bug in Microsoft's Outlook XP mail user
33811 As of this writing, Microsoft has acknowledged the bug but
33812 has not added it to the Knowledge Base.
33813 We have been told that there will be a post-SP1 hotfix for Outlook XP.
33814 This particular bug has bug fix number OfficeQFE:4781.
33815 The nature of the bug is that messages with attachments that
33816 contain a Content-ID header (which standard Alpine attachments do)
33817 do not show the attachment indicator (a paperclip) when viewed with
33819 So the user has no indication that the message contains an attachment.
33822 If this feature is set then Alpine will remove most Content-ID headers
33823 before sending a message.
33824 If an attachment is of type MESSAGE, then the existing Content-ID headers
33825 inside the message will be left intact.
33826 This would only happen with Alpine if a message was forwarded as an attachment
33827 or if a message with a message attached was forwarded.
33828 Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded,
33829 the Content-ID headers of the alternative parts will not be removed.
33832 Because the Content-ID header is a standard part of MIME it is possible
33833 that setting this feature will break something.
33834 For example, if an attachment has a Content-ID header that is necessary
33835 for the correct functioning of that attachment, it is possible that Alpine
33836 may remove that header when the attachment is forwarded.
33837 However, it seems fairly safe at this time.
33841 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33843 <End of help on this topic>
33846 ====== h_config_winpos_in_config =====
33849 <TITLE>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></TITLE>
33852 <H1>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></H1>
33857 Normally, PC-Alpine will store its window size and position in the
33859 This is convenient if you want to use the same remote
33860 configuration from more than one PC.
33861 If you use multiple configuration files to start PC-Alpine, you may want
33862 to store the window size and position in the configuration file instead
33863 of in the Registry.
33864 Setting this feature causes the value to be stored in
33865 <A HREF="h_config_window_position">Window-Position</A>.
33869 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33871 <End of help on this topic>
33874 ====== h_config_quell_ssl_largeblocks =====
33877 <TITLE>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></TITLE>
33880 <H1>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></H1>
33884 This feature changes the behavior of fetching messages
33885 and attachments so that the message data is fetched in chunks no larger
33887 This works around a bug in Microsoft's SSL/TLS support.
33888 Some versions of Microsoft SSL are not able to read full-sized (16K)
33890 Some servers will send such packets and this will
33891 cause PC-Alpine to crash with the error
33894 <CENTER><SAMP>incomplete SecBuffer exceeds maximum buffer size</SAMP></CENTER>
33897 Microsoft is aware of the problem and has developed a hotfix for it, it is
33898 discussed in article 300562 in the Microsoft Knowledge Base.
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_partial =====
33909 <TITLE>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></TITLE>
33912 <H1>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></H1>
33914 Partial fetching is a feature of the IMAP protocol.
33916 will use partial fetching when copying the contents of a message or attachment
33917 from the IMAP server to Alpine.
33918 This means that the fetch will be done in many
33919 small chunks instead of one big chunk. The main benefit of this approach is
33920 that the fetch becomes interruptible. That is, the user can type <EM>^C</EM>
33921 to stop the fetch early. In some cases partial fetching may cause a performance
33922 problem so that the fetching of data takes significantly longer when partial
33923 fetching is used. Turning on this feature will turn off partial fetching.
33926 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33928 <End of help on this topic>
33931 ====== h_config_quell_personal_name_prompt =====
33934 <TITLE>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></TITLE>
33937 <H1>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></H1>
33939 PC-Alpine only. This feature quells the prompting for a
33940 <A HREF="h_config_pers_name">personal name</A>. This
33941 prompt normally happens before composing a message, and only happens when
33942 there is no personal name already set.
33945 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33947 <End of help on this topic>
33950 ====== h_config_quell_user_id_prompt =====
33953 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></TITLE>
33956 <H1>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></H1>
33958 PC-Alpine only. This feature quells the prompting for a
33959 <A HREF="h_config_user_id"><!--#echo var="VAR_user-id"--></A>
33960 if the information can be obtained from the login name used
33961 to open the INBOX. Normally, this prompt happens before composing
33962 a message, and only happens when there is no user-id already set
33963 in the configuration.
33965 With this feature set, composing a message is only possible after
33966 establishing a connection to the INBOX.
33969 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33971 <End of help on this topic>
33974 ====== h_config_save_aggregates =====
33977 <TITLE>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></TITLE>
33980 <H1>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></H1>
33982 This feature will optimize an aggregate copy operation, if
33983 possible, by issuing a single IMAP <EM>COPY</EM> command with a
33984 list of the messages to be copied.
33985 This feature is set by default.
33986 This may reduce network traffic and elapsed time for the Save.
33987 <EM>However, many IMAP servers (including the UW IMAP server) do
33988 not preserve the order of messages when this optimization is applied.</EM>
33989 If this feature is not set,
33990 Alpine will copy each message individually and the order of the messages
33994 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33996 <End of help on this topic>
33999 ====== h_config_use_system_translation =====
34002 <TITLE>FEATURE: Use System Translation</TITLE>
34005 <H1>FEATURE: Use System Translation</H1>
34009 Alpine normally uses its own internal software to convert between the multi-byte
34010 representation of characters and the Unicode representation of those
34012 It converts from the multi-byte characters your keyboard produces to Unicode,
34013 and from Unicode to the multi-byte characters your display expects.
34014 Alpine also uses its own internal software to decide how much space on
34015 the screen a particular Unicode character will occupy.
34018 Setting this feature tells Alpine to use the system-supplied routines to
34019 perform these tasks instead.
34020 In particular there are three tasks and three system routines that will
34021 be used for these tasks.
34024 To convert from multi-byte to Unicode the routine
34027 <CENTER><SAMP>mbstowcs</SAMP></CENTER>
34031 To convert from Unicode to multi-byte the routine
34034 <CENTER><SAMP>wcrtomb</SAMP></CENTER>
34038 And to find the screen width a particular Unicode character will
34039 occupy the routine used is
34042 <CENTER><SAMP>wcwidth</SAMP></CENTER>
34045 This feature has been only lightly tested.
34046 The internal routines should normally be used unless you run into
34047 a problem that you think may be solved by using the system routines.
34048 Note that your environment needs to be set up for these
34049 routines to work correctly.
34050 In particular, the LANG or LC_CTYPE variable in your environment will
34055 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34057 <End of help on this topic>
34060 ====== h_config_suspend_spawns =====
34063 <TITLE>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></TITLE>
34066 <H1>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></H1>
34068 This feature affects Alpine's behavior when process suspension is enabled
34069 and then activated via the Ctrl-Z key. Alpine suspension allows one to
34070 temporarily interact with the operating system command "shell"
34072 quitting Alpine, and then subsequently resume the still-active Alpine session.
34075 When the <A HREF="h_config_can_suspend">"<!--#echo var="FEAT_enable-suspend"-->"</A> feature
34076 is set and subsequently the Ctrl-Z key
34077 is pressed, Alpine will normally suspend itself and return temporary control
34078 to Alpine's parent shell process. However, if this feature is set, Alpine
34079 will instead create an inferior subshell process. This is useful when the
34080 parent process is not intended to be used interactively. Examples include
34081 invoking Alpine via the -e argument of the Unix "xterm" program,
34082 or via a menu system.<P>
34084 Note that one typically resumes a suspended Alpine by entering the Unix
34085 "fg" command, but if this feature is set, it will be necessary to
34086 enter the "exit" command instead.
34089 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34091 <End of help on this topic>
34094 ====== h_config_8bit_smtp =====
34097 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></TITLE>
34100 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></H1>
34102 This feature affects Alpine's behavior when sending mail.
34103 By default, this feature is set.
34105 require that all electronic mail messages traversing the global Internet
34106 consist of 7bit ASCII characters unless a pair of cooperating mail
34107 transfer agents explicitly agree to allow 8bit messages. In general,
34108 then, exchanging messages in non-ASCII characters requires MIME encoding.
34110 However, there are now Internet standards that allow for unencoded 8bit
34111 exchange of messages between cooperating systems. When this feature is set
34112 Alpine will try to negotiate unencoded 8bit transmission during the
34113 sending process. Should the negotiation fail, Alpine will fall back to its
34114 ordinary encoding rules.
34116 Note, this feature relies on your system's mail transport agent or
34117 configured <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
34118 having the negotiation mechanism introduced in
34119 "Extended SMTP" (ESMTP) and the specific extension called
34120 "8BITMIME".
34122 ESMTP allows for graceful migration to upgraded mail transfer agents, but
34123 it is possible that this feature might cause problems for some servers.
34125 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34127 <P><End of help on this topic>
34130 ====== h_config_8bit_nntp =====
34133 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></TITLE>
34136 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></H1>
34138 This feature affects Alpine's behavior when posting news.
34142 The Internet standard for exchanging USENET news messages (RFC-1036)
34143 specifies that USENET messages should conform to Internet mail standards
34144 and contain only 7bit characters, but much of the news transport software
34145 in use today is capable of successfully sending messages containing 8bit
34146 characters. Hence, many people believe that it is appropriate to send 8bit
34147 news messages without any MIME encoding.
34151 Moreover, there is no Internet standard for explicitly negotiating 8bit
34152 transfer, as there is for Internet email. Therefore, Alpine provides the
34153 option of posting unencoded 8bit news messages, though not as the default.
34154 Setting this feature will turn OFF Alpine's MIME encoding of newsgroup
34155 postings that contain 8bit characters.
34159 Note, articles may cross a path or pass through news transport software
34160 that is unsafe or even hostile to 8bit characters. At best this will only
34161 cause the posting to become garbled. The safest way to transmit 8bit
34162 characters is to leave Alpine's MIME encoding turned on, but recipients
34163 who lack MIME-aware tools are often annoyed when they receive MIME-encoded
34166 <End of help on this topic>
34169 ====== h_config_mark_for_cc =====
34172 <TITLE>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></TITLE>
34175 <H1>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></H1>
34177 This feature affects Alpine's MESSAGE INDEX display.
34178 By default, a '+' is displayed in the first column if the
34179 message is addressed directly to you.
34180 When this feature is set and the message is not addressed to you, then a
34181 '-' character is displayed if the message is instead Cc'd directly
34186 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34188 <End of help on this topic>
34191 ====== h_config_tab_uses_unseen =====
34194 <TITLE>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></TITLE>
34197 <H1>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></H1>
34199 This feature affects Alpine's behavior when using the TAB
34200 <A HREF="h_common_nextnew">NextNew Command</A>
34201 to move from one folder to the next.
34202 Alpine's usual behavior is to search for folders
34203 with <EM>Recent</EM> messages in them.
34204 Recent messages are messages that have arrived since the last time the
34208 Setting this feature causes Alpine to search for <EM>Unseen</EM>
34209 messages instead of Recent messages.
34210 Unseen messages remain Unseen until you view them (or flag then as Seen with
34211 the <A HREF="h_common_flag">Flag Command</A>).
34212 Setting this feature allows you to locate messages you have not read
34213 instead of only recently received messages.
34214 When this feature is set, the feature
34215 <A HREF="h_config_fast_recent">"<!--#echo var="FEAT_enable-fast-recent-test"-->"</A>
34216 will have no effect, so the checking may be slower.
34219 Another reason why you might want to use this feature is that Alpine sometimes
34220 opens folders implicitly behind the scenes, and this clears the
34221 Recent status of all messages in the folder.
34222 One example where this happens is when Saving or filtering a
34223 message to another folder.
34224 If that message has some <A HREF="h_config_keywords">keywords</A>
34225 set, then because of some shortcomings
34226 in the IMAP specification, the best way to ensure that those keywords are
34227 still set in the saved copy of the message is to open the folder and
34228 set the keywords explicitly.
34229 Because this clears the Recent status of all messages in that folder the
34230 folder will not be found by the NextNew command unless this feature is set.
34233 <End of help on this topic>
34236 ====== h_config_tab_new_only =====
34239 <TITLE>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></TITLE>
34242 <H1>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></H1>
34244 This feature affects Alpine's behavior when using the TAB key to move from
34245 one message to the next. Alpine's usual behavior is to select the next
34246 unread message or message flagged as "Important".
34250 Setting this feature causes Alpine to skip the messages flagged as important,
34251 and select unread messages exclusively. Tab behavior when there are no
34252 new messages left to select remains unchanged.
34254 <End of help on this topic>
34257 ====== h_config_warn_if_subj_blank =====
34260 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></TITLE>
34263 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></H1>
34265 This feature affects Alpine's behavior when you send a message being
34267 If this option is set, Alpine will check to see if the message about to be sent
34268 has a subject or not.
34269 If not, you will be asked if you want to send the message anyway.
34273 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34275 <End of help on this topic>
34278 ====== h_config_warn_if_fcc_blank =====
34281 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></TITLE>
34284 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></H1>
34286 This feature affects Alpine's behavior when you send a message being
34288 If this option is set, Alpine will check to see if the message about to be sent
34290 If not, you will be asked if you want to send the message anyway.
34294 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34296 <End of help on this topic>
34299 ====== h_config_warn_if_no_to_or_cc =====
34302 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></TITLE>
34305 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></H1>
34307 This feature affects Alpine's behavior when you send a message being
34309 If this option is set, Alpine will check to see if the message about to be sent
34310 has either a To address, a Cc address, or a Newsgroup.
34311 If none of these is set,
34312 you will be asked if you want to send the message anyway.
34315 This feature is closely related to
34316 <A HREF="h_config_auto_fcc_only"><!--#echo var="FEAT_fcc-only-without-confirm"--></A>.
34317 Alpine will normally ask if you want to copy a message only to the Fcc.
34318 This feature also applies to cases where there is a Bcc but still no To, Cc,
34320 If the <!--#echo var="FEAT_fcc-only-without-confirm"--> feature is set and you are sending a
34321 message with only an Fcc, then you won't be asked about sending with
34322 a blank To and Cc and Newsgroups header even if this feature is set.
34323 Similarly, if you have already been asked if you want to send to the Fcc
34324 only and you have answered Yes, then you won't be asked again about sending with
34325 blank To, Cc, and Newsgroups headers even if this feature is set.
34329 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34331 <End of help on this topic>
34334 ====== h_config_quell_dead_letter =====
34337 <TITLE>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></TITLE>
34340 <H1>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></H1>
34342 This feature affects Alpine's behavior when you cancel a message being
34343 composed. Alpine's usual behavior is to write the canceled message to
34345 <!--chtml if pinemode="os_windows"-->
34346 "DEADLETR",
34348 "dead.letter" in your home directory,
34350 overwriting any previous message. Under
34351 some conditions (some routine), this can introduce a noticeable delay.
34352 Setting this feature will cause Alpine NOT to write canceled compositions
34355 NOTE: Enabling this feature means NO record of canceled messages is
34358 This feature affects the newer option
34359 <A HREF="h_config_deadlets"><!--#echo var="VAR_dead-letter-files"--></A>, which specifies the
34360 number of dead letter files to keep around.
34361 If this feature is set, then the <!--#echo var="VAR_dead-letter-files"--> option has no effect.
34364 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34366 <End of help on this topic>
34369 ====== h_config_quell_beeps =====
34372 <TITLE>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></TITLE>
34375 <H1>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></H1>
34377 This feature affects Alpine's behavior when it displays status message
34378 (e.g., Error complaints, New mail warnings, etc). Setting this feature
34379 will not affect the display of such messages, but will cause those that
34380 emit a beep to become silent.
34384 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34386 <End of help on this topic>
34389 ====== h_config_suppress_user_agent =====
34392 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></TITLE>
34395 <H1>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></H1>
34397 If this feature is set then Alpine will not generate a
34398 <CODE>User-Agent</CODE> header in outgoing messages.
34401 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34403 <End of help on this topic>
34406 ====== h_config_quell_lock_failure_warnings =====
34409 <TITLE>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></TITLE>
34412 <H1>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></H1>
34414 This feature affects Alpine's behavior when it encounters a problem
34415 acquiring a mail folder lock. Typically, a secondary file associated
34416 with the mail folder being opened is created as part of the locking
34417 process. On some systems, such file creation has been administratively
34418 precluded by the system configuration.
34420 Alpine issues a warning when such failures occur, which can become bothersome
34421 if the system is configured to disallow such actions. Setting this
34422 feature causes Alpine to remain silent when this part of lock creation fails.
34424 WARNING: systems that have been configured in a way that precludes locking
34425 introduce some risk of mail folder corruption when more than one program
34426 attempts to modify the mail folder. This is most likely to occur to one's
34427 INBOX or other incoming message folder.
34429 See also <A HREF="h_info_on_locking">"What Systems Managers Need to Know about Alpine File Locking"</A>.
34432 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34434 <End of help on this topic>
34437 ====== h_config_enable_role_take ======
34440 <TITLE>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></TITLE>
34443 <H1>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></H1>
34445 Normally, the Take command takes addresses from a message and helps you
34446 put them into your Address Book.
34447 If you use Rules for Indexcolors, Roles, Filtering, or Scoring;
34448 you may find it useful
34449 to be able to Take information from a message's headers and put it into
34451 When this feature is set, you will be given an extra prompt that gives
34452 you the choice to Take into the Address Book or Take into a rule.
34454 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34457 <End of help on this topic>
34460 ====== h_config_enable_take_export ======
34463 <TITLE>FEATURE: <!--#echo var="FEAT_enable-take-export"--></TITLE>
34466 <H1>FEATURE: <!--#echo var="FEAT_enable-take-export"--></H1>
34468 Normally, the Take command takes addresses from a message and helps you
34469 put them into your Address Book.
34470 When this feature is set, you will be given an extra prompt that gives you
34471 the choice to Take addresses into a file instead of your Address
34473 Only the user@domain_name part of the address is put in the file.
34475 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34478 <End of help on this topic>
34481 ====== h_config_quell_folder_internal_msg ======
34484 <TITLE>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></TITLE>
34487 <H1>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></H1>
34489 This feature determines whether or not Alpine will create
34490 "pseudo messages" in folders that are in standard Unix or
34493 Alpine will normally create these pseudo messages when they are not already
34494 present in a standard Unix or MMDF folder. Their purpose is to record
34495 certain mailbox state data needed for correct IMAP and POP server
34496 operation, and also for Alpine to be able to mark messages as Answered when
34497 the Reply has been postponed.<P>
34499 Sites that do not use IMAP/POP for remote mail access, and that need to
34500 support mail tools that are adversely affected by the presence of the
34501 pseudo-messages (e.g. some mail notification tools) may enable this
34502 feature to tell Alpine not to create them. Note that Alpine's
34503 "Answered" flag
34504 capability will be adversely affected if this is done.<P>
34506 Note too that, even if this feature is enabled, Alpine will not remove
34507 pseudo-messages when it encounters them (e.g. those created by UW's imapd
34508 or ipopd servers.) This feature has no effect on folders that are not in
34509 standard Unix or MMDF format, as pseudo-messages are not needed in the
34510 other formats to record mailbox state information.
34512 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34515 <End of help on this topic>
34518 ====== h_config_mulnews_as_typed ======
34521 <TITLE>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></TITLE>
34524 <H1>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></H1>
34526 This feature will be of little use to most users.
34527 It has no effect unless the feature
34528 <A HREF="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></A>
34531 When the <!--#echo var="FEAT_enable-multiple-newsrcs"--> feature is set
34532 then the setting of this feature may have an effect on the names of the
34534 Normally, the name of the news server will be canonicalized before it is
34535 used in the newsrc file name.
34536 For example, if you type the news server name
34539 <CENTER><SAMP>servername</SAMP></CENTER>
34542 it is likely that the canonical name will be something like
34545 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
34548 Or it may be the case that
34551 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
34554 is really an alias (a DNS CNAME) for
34557 <CENTER><SAMP>othername.example.com</SAMP></CENTER>
34560 If this feature is not set, then the canonicalized names will be used.
34561 If this feature is set, then the name you typed in (or put in your
34562 configuration) will be used.
34565 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34568 <End of help on this topic>
34571 ====== h_config_quell_empty_dirs ======
34574 <TITLE>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></TITLE>
34577 <H1>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></H1>
34579 This feature causes Alpine to remove from the display any directories
34580 that do not contain at least one file or directory. This can be useful
34581 to prevent overly cluttered folder lists when a collection is stored on
34582 a server that treats all names as both a folder and a directory.
34585 Note, enabling this feature can cause surprising behavior! For example,
34586 you can still use Add to create a directory, but unless you immediately
34587 enter that directory and create a folder, that newly created directory
34588 may not be displayed next time you enter the folder list.
34591 The description above is not quite correct.
34592 Only directories which potentially may hold messages are hidden if empty.
34593 That is, a directory which is really just a directory and is not selectable
34594 as a folder will not be hidden.
34595 Such directories can occur on servers that treat most names as both a folder
34597 These directories are typically created implicitly when a folder is created
34598 inside a directory that does not yet exist.
34602 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34604 <End of help on this topic>
34607 ====== h_config_termcap_wins =====
34610 <TITLE>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></TITLE>
34613 <H1>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></H1>
34615 This feature may affect Alpine's low-level input routines. Termcap (or
34616 terminfo, depending on how your copy of Alpine was compiled and linked)
34617 is the name of the database that describes terminal capabilities. In
34618 particular, it describes the sequences of characters that various keys
34622 An example would be the Up Arrow key on the keyboard. Up
34623 Arrow is not a distinct character on most Unix systems. When you press
34624 the Up Arrow key a short sequence of characters are produced. This
34625 sequence is supposed to be described in the termcap database by the
34626 "ku" capability (or by the "kcuu1" capability if you
34627 are using terminfo instead of termcap).
34630 By default, Alpine defines some terminal
34631 escape sequences that are commonly used. For example, the sequence
34632 "ESC O A" is recognized as an Up Arrow key. The sequence
34633 "ESC [ A"
34634 is also recognized as an Up Arrow key. These are chosen because common
34635 terminals like VT100's or ANSI standard terminals produce these
34636 sequences when you press the Up Arrow key.
34639 If your system's termcap
34640 (terminfo) database assigns some other function to the sequence
34641 "ESC O A"
34642 it is usually ignored by Alpine. Also, if your termcap (terminfo)
34643 database assigns a sequence that doesn't begin with an escape
34644 character (<SAMP>ESC</SAMP>) it is usually ignored by Alpine.
34645 This usually works fine
34646 because most terminals emit the escape sequences that Alpine has defined
34647 by default. We have also found that it is usually better to have these
34648 defaults take precedence over the definitions contained in the database
34649 because the defaults are more likely to be correct than the database.
34652 There are some terminals where this breaks down. If you want Alpine to
34653 believe the definitions given in your termcap (terminfo) database in
34654 preference to the defaults the Alpine itself sets up, then you may turn
34655 this feature on. Then, sequences of characters that are defined in
34656 both termcap (terminfo) and in Alpine's set of defaults will be
34657 interpreted the way that termcap (terminfo) says they should be
34658 interpreted. Also, if your terminal capabilities database assigns a
34659 sequence that doesn't begin with escape, it will not be ignored.
34663 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34665 <End of help on this topic>
34668 ====== h_config_cruise_mode =====
34671 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></TITLE>
34674 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></H1>
34676 This feature affects Alpine's behavior when you hit the
34677 "Space Bar" at
34678 the end of a displayed message. Typically, Alpine complains that the end
34679 of the text has already been reached. Setting this feature causes such
34680 keystrokes to be interpreted as if the "Tab" key had been hit, thus
34681 taking you to the next "interesting" message,
34682 or scanning ahead to the
34683 next incoming folder with "interesting" messages.
34687 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34689 <End of help on this topic>
34692 ====== h_config_cruise_mode_delete =====
34695 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></TITLE>
34698 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></H1>
34700 This feature modifies the behavior of Alpine's
34701 <A HREF="h_config_cruise_mode">"<!--#echo var="FEAT_enable-cruise-mode"-->"</A> feature.
34702 Setting this feature causes Alpine to implicitly delete read
34703 messages when it moves on to display the next "interesting" message.
34705 NOTE: Beware when enabling this feature AND the
34706 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
34710 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34712 <End of help on this topic>
34715 ====== h_config_slash_coll_entire =====
34718 <TITLE>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></TITLE>
34721 <H1>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></H1>
34723 The slash (/) command is available from the MESSAGE INDEX screen when
34724 the folder is sorted by either Threads or OrderedSubject, and the
34725 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
34726 is set to something other than "none".
34727 Normally, the slash command Collapses or Expands the subthread that
34728 starts at the currently highlighted message, if any.
34729 If this option is set, then the slash command Collapses or Expands the
34730 <EM>entire</EM> current thread instead of just the subthread.
34731 The current thread is simply the top-level thread that contains the
34736 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34738 <End of help on this topic>
34741 ====== h_config_color_thrd_import =====
34744 <TITLE>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></TITLE>
34747 <H1>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></H1>
34749 This option affects only the THREAD INDEX screen.
34750 Whether or not you ever see a THREAD INDEX screen depends on the setting
34751 of the configuration option
34752 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
34753 and on the sort order of the index.
34756 If a message within a thread is flagged as Important
34757 and this option is set, then
34758 the entire line in the THREAD INDEX will be colored the color of the
34759 Index-important Symbol, which can be set using the
34760 <A HREF="h_color_setup">Setup Kolor</A> screen.
34764 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34766 <End of help on this topic>
34769 ====== h_config_allow_goto =====
34772 <TITLE>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></TITLE>
34775 <H1>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></H1>
34777 This feature modifies the behavior of Alpine's file browser. Setting this
34778 feature causes Alpine to offer the "G Goto" command in the file browser.
34779 That is the default.
34783 The Goto command allows you to explicitly type in the desired directory.
34785 <End of help on this topic>
34787 ====== h_config_add_ldap =====
34790 <TITLE>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></TITLE>
34793 <H1>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></H1>
34795 If both the Directory option
34796 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
34797 and this feature are set,
34798 then when an implicit directory lookup is done from the
34799 composer you will automatically be prompted to add the result of the
34800 directory lookup to your address book.
34803 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34805 <End of help on this topic>
34808 ===== h_patterns_compat_behavior =====
34811 <TITLE>Rules Behavior Changes in Pine 4.50</TITLE>
34814 <H1>Rules Behavior Changes in Pine 4.50</H1>
34816 In Alpine, Rules that contain unrecognized elements
34818 In most cases, the unrecognized elements will be something that was
34819 added as a new Rules feature in a later version of Alpine.
34820 In versions of Pine <EM>prior</EM> to 4.50, Pine did <EM>not</EM>
34821 ignore rules that contained unrecognized elements.
34822 For example, a new element of Rules that was added in Pine 4.50 is
34824 Suppose you add an Indexcolor rule, using version Pine 4.50 or later, that colors
34825 all messages older than a week red.
34826 Now, if you run Pine 4.44 using that same configuration file, it will not
34827 recognize the Age interval and so will just ignore it.
34828 That means that all messages will match that rule so all messages will
34829 be colored red when using Pine version 4.44.
34832 This behavior was considered a bug so it is fixed in Alpine and Pine 4.50 and later.
34833 However, since the behavior still exists in versions prior to Pine 4.50 and
34834 since Filtering is a potentially destructive operation, another measure
34835 was taken to attempt to avoid unintentional Filtering of messages.
34836 The first time that you run Alpine or a Pine that is version 4.50 or greater,
34837 the rules in your Filters configuration variable ("Patterns-Filters")
34838 will be copied to a new Filters configuration variable
34839 with a different name ("Patterns-Filters2").
34840 From then on, Alpine will continue to use the new
34842 Of course, Pine version 4.44 or lower will continue to use the old
34844 That means that if you are using Alpine
34845 and also using a version of Pine that is older than 4.50, they will not
34846 share the configuration information about Filters.
34847 If you make a change in one version you won't see it in the other version.
34850 Since Scoring can be used to trigger Filtering, the same thing has been
34851 done for Score rules.
34852 The old configuration variable name is ("Patterns-Scores")
34853 and the new name is ("Patterns-Scores2").
34854 The same is not true of Role, Indexcolor, and Other rules that are
34855 thought to be less harmful when a mistake is made.
34858 <End of help on this topic>
34861 ======= h_config_filt_opts_sentdate =======
34864 <TITLE>PATTERN FEATURE: Use-Date-Header-For-Age</TITLE>
34867 <H1>PATTERN FEATURE: Use-Date-Header-For-Age</H1>
34869 By default, the Age interval of a Pattern uses a message's time of
34870 arrival to compute the age of the message.
34871 If this feature is set, the date in the message's Date header will
34874 <End of help on this topic>
34877 ======= h_config_filt_opts_notdel =======
34880 <TITLE>FILTER FEATURE: Move-Only-if-Not-Deleted</TITLE>
34883 <H1>FILTER FEATURE: Move-Only-if-Not-Deleted</H1>
34885 If this option is set then a message will be moved into the
34886 specified folder only if it is not marked for deletion.
34887 This is useful if you have multiple Alpine sessions running
34888 simultaneously and you don't want messages to be filtered into a
34889 folder more than once.
34890 It is also useful if you want to filter
34891 only the "undeleted" messages in a newsgroup into a folder.
34892 This method is not foolproof.
34893 There may be cases where a message
34894 gets marked deleted and so it is never filtered into the folder.
34895 For example, if you deleted it in another Alpine session or another mail
34896 program that didn't use the filtering rule.
34898 This option has no effect if the Filter Action is not set to Move.
34900 <End of help on this topic>
34903 ======= h_config_filt_opts_nonterm =======
34906 <TITLE>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</TITLE>
34909 <H1>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</H1>
34911 If this option is set then this is a non-terminating rule.
34912 Usually, for each message, Alpine searches through the Filter Rules until
34913 a match is found and then it performs the action associated with that rule.
34914 Rules following the match are not considered.
34915 If this option is set then the search for matches will continue at the next
34918 If a non-terminating rule matches then the actions associated with
34919 that rule, except for any implied deletion of the message, are performed
34920 before the match for the next rule is checked.
34921 For example, if the non-terminating rule sets the Important status, then that
34922 status will be set when the next rule is considered.
34923 However, if the non-terminating rule Moves the message, the message will
34924 actually be copied instead of copied and deleted so that it is still there
34926 A moved message is deleted after all the relevant rules have been checked.
34927 The name of the "Move" action is confusing in this case because
34928 a single message can be moved to more than one folder.
34929 It turns the Move into a Copy instead, but it is still followed by a deletion
34932 This option may be useful if you want to have a single message filtered to
34933 two different folders because it matches two different Patterns.
34934 For example, suppose you normally filter messages to a particular mailing
34935 list into one folder, and messages addressed directly to you into a second
34937 If a message is sent to both you and the list (and you can tell that by
34938 looking at the headers of the message) this option may give you a convenient
34939 way to capture a copy to each folder.
34940 (It may also cause you to capture two copies to each folder,
34941 depending on whether your mail system delivers one or two copies of the
34942 message to you and on how the list works.)
34944 <End of help on this topic>
34947 ===== h_mainhelp_smime ======
34950 <TITLE>S/MIME Overview</TITLE>
34953 <H1>S/MIME Overview</H1>
34955 S/MIME is a standard for the public key encryption and signing of email.
34956 UNIX Alpine contains a basic implementation of S/MIME based on
34957 the <A HREF="http://www.openssl.org/">OpenSSL</A> libraries. The
34958 same support can be provided using the
34959 <A HREF="http://www.libressl.org/">LibreSSL</A> libraries. The
34960 support for S/MIME in PC-Alpine is fully based on the LibreSSL libraries.
34961 To check if this version of Alpine supports S/MIME look at
34962 <A HREF="X-Alpine-Config:">Supported Options in this Alpine</A> and look
34963 for "S/MIME" under the "Encryption" heading.
34967 <LI> There is no provision for checking for CRLs
34968 (Certificate Revocation Lists) in Alpine.
34969 <LI> This built-in S/MIME implementation is not compatible with and does not help with PGP.
34970 <LI> There is no mechanism available for feeding either an entire incoming
34971 or an entire outgoing message to an external
34972 filter and using that external filter to do S/MIME or PGP processing.
34973 <LI> Because the implementation currently uses OpenSSL, there is only a very
34974 limited integration with the Mac OS Keychain (the storing and access of
34975 public certificates).
34978 The S/MIME configuration screen is reached by going to the Main Menu and typing
34979 the "S Setup" command followed by "M S/MIME".
34982 <H2>S/MIME BASICS</H2>
34984 In order to digitally sign messages you send you must have a public/private key-pair.
34985 This may be obtained from a public Certificate Authority (CA) such as Thawte, Verisign, Comodo,
34986 or GoDaddy; or from a smaller CA such as a university which provides certificates for its
34987 users or a company which provides certificates for its workers.
34988 These certificates are bound to an email address, so the identity being verified is the
34989 email address not a person's name.
34991 Mail is signed by using the sender's private key, which only the owner of the private key
34993 The signature is verified using the signer's public key, which anyone can
34995 With Alpine, the first time you receive a signed message the public key of the
34996 sender will be stored for future use.
34999 Mail is encrypted using the recipient's public key and decrypted by
35000 the recipient with their private key.
35003 You need a key of your own in order to sign outgoing messages and to have others
35004 encrypt messages sent to you.
35005 You do not need a key of your own to verify signed messages sent by others or to
35006 encrypt messages sent to others.
35008 <H2>ALPINE S/MIME CERTIFICATE STORAGE</H2>
35010 By default UNIX Alpine stores the certificates it uses in a directory in your
35012 The directory name is
35014 <CENTER><SAMP>.alpine-smime</SAMP></CENTER>
35016 For PC-Alpine, the equivalent directory is called
35017 <CENTER><SAMP>alpine-smime</SAMP></CENTER>
35018 and is also located under your home directory.
35020 Within that directory are three subdirectories.
35021 Each of the three subdirectories contains files with PEM-encoded contents,
35022 the default format for OpenSSL.
35023 The "<SAMP>public</SAMP>" directory contains public certificates.
35024 The files within that directory have names that are email addresses with the
35025 suffix "<SAMP>.crt</SAMP>" appended.
35026 An example filename is
35028 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
35030 The "<SAMP>private</SAMP>" directory contains private keys, probably just one for
35032 These are also email addresses but with the suffix "<SAMP>.key</SAMP>" instead.
35033 The third directory is "<SAMP>ca</SAMP>" and it contains certificates for any Certificate
35034 Authorities that you want to trust but that aren't contained in the set of system CAs.
35035 Those files may have arbitrary names as long as they end with the
35036 suffix "<SAMP>.crt</SAMP>".
35038 <H2>HOW TO SIGN AND ENCRYPT</H2>
35040 If you have a certificate you may sign outgoing messages.
35041 After typing the Ctrl-X command to send a message you will see the prompt
35043 <CENTER><SAMP>Send message?</SAMP></CENTER>
35045 Available subcommands include "G Sign" and "E Encrypt".
35046 Typing the "G" command will change the prompt to
35048 <CENTER><SAMP>Send message (Signed)?</SAMP></CENTER>
35050 Typing the "E" command will change the prompt to
35052 <CENTER><SAMP>Send message (Encrypted)?</SAMP></CENTER>
35054 You may even type both to get
35056 <CENTER><SAMP>Send message (Encrypted, Signed)?</SAMP></CENTER>
35059 <H2>HOW TO READ SIGNED OR ENCRYPTED MESSAGES</H2>
35061 The reading of a signed message should not require any special action on
35063 There should be an editorial addition at the start of the message which
35066 <CENTER><SAMP>This message was cryptographically signed.</SAMP></CENTER>
35070 <CENTER><SAMP>This message was cryptographically signed but the signature could not be verified.</SAMP></CENTER>
35072 If an encrypted message is sent to you the encrypted text will not
35074 You will have to type the "Ctrl-D Decrypt" command (from the screen where
35075 you are viewing the message) and supply your passphrase when asked.
35077 For a signed or encrypted message there is also a "Ctrl-E Security" command
35078 which gives you some information about the certificate used to sign or encrypt the message.
35080 <H2>MISCELLANEOUS</H2>
35082 If you have access to a private certificate in the PKCS12 format, which
35083 would sometimes be in a file with a ".p12" extension, then you can
35084 use the following commands to generate private keys, public and certificate
35085 authorities certificates. In the examples below, we assume that the
35086 certificate in the p12 format is called "certificate.p12", and
35087 that your email address is "your@address.com".
35090 In order to create a private key use the command
35092 <CENTER><SAMP>openssl pkcs12 -in certificate.p12 -out your@address.com.key</SAMP></CENTER>
35094 In order to create a public certificate use the command
35097 openssl pkcs12 -in certificate.p12 -clcerts -nokeys -out your@address.com.crt
35100 In order to create a certificate authority certificate use the command
35103 openssl pkcs12 -in certificate.p12 -cacerts -nokeys -out certificate-ca.crt
35106 <P> If the previous command produces an empty file, it means that the
35107 certificate authority was not included in the .p12 file, so you will have
35108 to get it from some other sources. You will need these certificates, so
35109 that you can validate correctly signatures.
35112 After you have exported these certificates and keys, you can use the import
35113 command in Alpine, from the S/MIME configuration screen,
35114 to import these certificates into Alpine. They will be available for use
35115 as soon as you import them.
35117 <End of help on this topic>
35120 ====== h_config_smime_pubcertdir =====
35123 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></TITLE>
35126 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></H1>
35130 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35131 is set then this option will have no effect.
35133 Normally, Public Certificates for use with S/MIME will be stored in the directory
35134 which is the value of this option.
35135 Those certificates will be stored in PEM format, one certificate per file.
35136 The name of the file for the certificate corresponding to
35138 <CENTER><SAMP>emailaddress</SAMP></CENTER>
35142 <CENTER><SAMP>emailaddress.crt</SAMP></CENTER>
35144 For example, a file for user@example.com would be in the file
35146 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
35150 Use the Setup/SMIME screen to modify this variable.
35152 Typically, the public certificates that you have will come from S/MIME signed
35153 messages that are sent to you.
35154 Alpine will extract the public certificate from the signed message and store
35155 it in the certificates directory.
35156 These PEM format public certificates look something like:
35158 -----BEGIN CERTIFICATE-----
35159 MIIFvTCCBKWgAwIBAgIQD4fYFHVI8T20yN4nus097DANBgkqhkiG9w0BAQUFADCB
35160 rjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2Ug
35161 Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExho
35163 2b9KGqDyMWW/rjNnmpjzjT2ObGM7lRA8lke4FLOLajhrz4ogO3b4DFfAAM1VSZH8
35164 D6sOwOLJZkLY8FRsfk63K+2EMzA2+qAzMKupgeTLqXIf
35165 -----END CERTIFICATE-----
35169 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35173 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35175 <End of help on this topic>
35178 ====== h_config_smime_pubcertcon =====
35181 <TITLE>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></TITLE>
35184 <H1>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></H1>
35187 If this option is set it will be used instead of
35188 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
35190 This option gives you a way to store certificates remotely on an IMAP server
35191 instead of storing the certificates one per file locally.
35192 In order to do that you just give this option a remote folder name for a folder
35193 which does not yet exist.
35194 The name is similar to the name you might use for a remote configuration file.
35195 A remote folder name might look something like:
35197 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/publiccerts</SAMP></CENTER>
35200 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
35201 about the syntax of folder names.
35203 Use the Setup/SMIME screen to modify this variable.
35206 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35210 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35212 <End of help on this topic>
35215 ====== h_config_smime_privkeydir =====
35218 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></TITLE>
35221 <H1>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></H1>
35224 In order to sign outgoing S/MIME messages you will need a
35225 personal digital ID certificate.
35226 You will usually get such a certificate from a certificate authority such as
35228 (In order to encrypt outgoing messages you don't need a personal digital ID, you
35229 need the public certificate of the recipient instead.)
35231 <A HREF="h_config_smime_privkeycon"><!--#echo var="VAR_smime-private-key-container"--></A>
35232 is set then this option will have no effect.
35234 Normally, Private Keys for use with S/MIME will be stored in the directory
35235 which is the value of this option.
35236 Those certificates will be stored in PEM format, one certificate per file.
35237 The name of the file for the certificate corresponding to your
35239 <CENTER><SAMP>emailaddress</SAMP></CENTER>
35243 <CENTER><SAMP>emailaddress.key</SAMP></CENTER>
35245 For example, if your address is user@example.com the name of the file would be
35247 <CENTER><SAMP>user@example.com.key</SAMP></CENTER>
35251 Use the Setup/SMIME screen to modify this variable.
35253 Typically, the private key that you have will come from a Certificate
35255 The private key should be stored in a PEM format file that
35256 looks something like:
35258 -----BEGIN RSA PRIVATE KEY-----
35259 Proc-Type: 4,ENCRYPTED
35260 DEK-Info: DES-EDE3-CBC,2CBD328FD84CF5C6
35262 YBEXYLgLU9NJoc1V+vJ6UvcF08RX54S6jXsmgL0b5HGkudG6fhnmHkH7+UCvM5NI
35263 SXO/F8iuZDfs1VGG0NyitkFZ0Zn2vfaGovBvm15gx24b2xnZDLRB7/bNZkurnK5k
35264 VjAjZ2xXn2hFp2GJwqRdmxYNqsKGu52B99oti5HUWuZ2GFRaWjn5hYOqeApZE2uA
35266 oSRqfI51UdSRt0tmGhHeTvybUVrHm9eKft8TTGf+qSBqzSc55CsmoVbRzw4Nfhix
35267 m+4TJybNGNfAgOctSkEyY/OCb49fRRQTCBZVIhzLGGmpYmkO55HbIA==
35268 -----END RSA PRIVATE KEY-----
35272 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35276 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35278 <End of help on this topic>
35281 ====== h_config_smime_privkeycon =====
35284 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-container"--></TITLE>
35287 <H1>OPTION: <!--#echo var="VAR_smime-private-key-container"--></H1>
35290 If this option is set it will be used instead of
35291 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35293 This option gives you a way to store keys remotely on an IMAP server
35294 instead of storing the keys one per file locally.
35295 In order to do that you just give this option a remote folder name for a folder
35296 which does not yet exist.
35297 The name is similar to the name you might use for a remote configuration file.
35298 A remote folder name might look something like:
35300 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/privatekeys</SAMP></CENTER>
35303 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
35304 about the syntax of folder names.
35306 Use the Setup/SMIME screen to modify this variable.
35309 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35313 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35315 <End of help on this topic>
35318 ====== h_config_smime_cacertdir =====
35321 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></TITLE>
35324 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></H1>
35328 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>
35329 is set then this option will have no effect.
35331 CACert is a shorthand name for certification authority certificate.
35332 Normally Alpine will use the CACerts that are located in the standard system
35333 location for CACerts.
35334 It may be the case that one of your correspondents has a Digital ID which has
35335 been signed by a certificate authority that is not in the regular set of system certificate
35337 You may supplement the system list by adding further certificates of your own.
35338 These should be stored in the directory
35339 which is the value of this option.
35340 The certificates will be stored in PEM format, one certificate per file.
35341 The names of the files can be anything ending in ".crt".
35343 Use the Setup/SMIME screen to modify this variable.
35345 These PEM format CA certificates look very similar to your public
35346 certificates for particular email addresses
35347 (<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>).
35350 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35354 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35356 <End of help on this topic>
35359 ====== h_config_smime_cacertcon =====
35362 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></TITLE>
35365 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></H1>
35368 If this option is set it will be used instead of
35369 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
35371 This option gives you a way to store certificates remotely on an IMAP server
35372 instead of storing the certificates one per file locally.
35373 In order to do that you just give this option a remote folder name for a folder
35374 which does not yet exist.
35375 The name is similar to the name you might use for a remote configuration file.
35376 A remote folder name might look something like:
35378 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/cacerts</SAMP></CENTER>
35381 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
35382 about the syntax of folder names.
35384 Use the Setup/SMIME screen to modify this variable.
35387 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35391 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35393 <End of help on this topic>
35396 ========== h_config_smime_sign_by_default ==========
35399 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></TITLE>
35402 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></H1>
35405 This feature only has an effect if your version of Alpine includes
35406 support for S/MIME.
35407 It affects Alpine's behavior when you send a message.
35408 If this option is set, the "Sign" option will default to ON when sending messages.
35410 Only the default value is affected.
35411 In any case, you may still toggle the Signing option on or off before sending
35412 with the "G Sign" command (provided you have a personal digital ID
35416 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35421 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35423 <End of help on this topic>
35426 ========== h_config_smime_use_cert_store ==========
35429 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></TITLE>
35432 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></H1>
35435 This feature only has an effect if your version of Alpine includes
35436 support for S/MIME.
35437 It affects Alpine's behavior when you validate a message, and should
35438 not be disabled, unless you are performing a test.
35440 There are two important aspects of validation: validation of the message
35441 (that is, the message was not modified after it was sent)
35442 as well as validation of the identity of the sender. This option has to
35443 do with the latter.
35445 In order to validate that the message came from the sender in the message
35446 and not an impersonator, Alpine can
35447 either use the certificates that come in the message, or the ones that
35448 you have personally stored. If this feature is enabled (the default) then
35449 Alpine will use certificates that you have already saved in your store
35450 and not those that come in the message to validate the sender of the
35451 message. In particular, the first time that you receive a signed message
35452 from a sender, and their certificate does not validate against your
35453 store, then you will be asked if you wish to save such certificate. If
35454 you do not wish to save the certificate, then Alpine will fail to validate
35455 the signature of the message. Otherwise, Alpine will proceed to validate
35456 the signature of the message. This behavior helps you prevent against impersonation, because
35457 it is assumed that you trust the certificates that you have saved, and
35458 might not trust those that came with the message that you are validating.
35461 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35466 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35468 <End of help on this topic>
35471 ========== h_config_smime_pubcerts_in_keychain ==========
35474 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></TITLE>
35477 <H1>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></H1>
35480 If this feature is set the Mac OS X default keychain will be used as the place
35481 to store public certificates instead of a
35482 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
35484 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
35487 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35491 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35493 <End of help on this topic>
35496 ========== h_config_smime_dont_do_smime ==========
35499 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></TITLE>
35502 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></H1>
35505 Setting this feature turns off all of Alpine's S/MIME support.
35506 You might want to set this if you are having trouble due to the S/MIME support.
35509 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35514 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35516 <End of help on this topic>
35519 ========== h_config_smime_encrypt_by_default ==========
35522 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></TITLE>
35525 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></H1>
35528 This feature only has an effect if your version of Alpine includes
35529 support for S/MIME.
35530 It affects Alpine's behavior when you send a message.
35531 If this option is set, the "Encrypt" option will default to ON when sending messages.
35533 Only the default value is affected.
35534 In any case, you may still toggle the Encrypt option on or off before sending
35535 with the "E Encrypt" command (provided you have a the public digital ID
35536 for the recipient).
35539 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35544 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35546 <End of help on this topic>
35549 ========== h_config_smime_remember_passphrase ==========
35552 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></TITLE>
35555 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></H1>
35558 This feature only has an effect if your version of Alpine includes
35559 support for S/MIME.
35560 If this option is set, you will only have to enter your passphrase for your private key
35561 once during an Alpine session.
35564 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35569 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35571 <End of help on this topic>
35574 ====== h_config_smime_transfer_pub_to_con =====
35577 <TITLE>S/MIME: Transfer Public Certs to Container</TITLE>
35580 <H1>S/MIME: Transfer Public Certs to Container</H1>
35583 The Transfer command will copy the public certificates in your configured
35584 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
35585 to the container in your configured
35586 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
35587 This might be useful if you decide to switch from using a cert directory to a cert
35590 Warning: Any previous contents in the container will be lost.
35593 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35597 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35599 <End of help on this topic>
35602 ====== h_config_smime_transfer_pub_to_dir =====
35605 <TITLE>S/MIME: Transfer Public Certs to Directory</TITLE>
35608 <H1>S/MIME: Transfer Public Certs to Directory</H1>
35611 The Transfer command will copy the public certificates in your configured
35612 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35613 to the directory in your configured
35614 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
35615 This might be useful if you decide to switch from using a cert container to a cert
35619 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35623 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35625 <End of help on this topic>
35628 ====== h_config_smime_transfer_priv_to_con =====
35631 <TITLE>S/MIME: Transfer Private Keys to Container</TITLE>
35634 <H1>S/MIME: Transfer Private Keys to Container</H1>
35637 The Transfer command will copy the private keys in your configured
35638 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35639 to the container in your configured
35640 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
35641 This might be useful if you decide to switch from using a key directory to a key
35644 Warning: Any previous contents in the container will be lost.
35647 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35651 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35653 <End of help on this topic>
35656 ====== h_config_smime_transfer_priv_to_dir =====
35659 <TITLE>S/MIME: Transfer Private Keys to Directory</TITLE>
35662 <H1>S/MIME: Transfer Private Keys to Directory</H1>
35665 The Transfer command will copy the private keys in your configured
35666 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
35667 to the directory in your configured
35668 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35669 This might be useful if you decide to switch from using a key container to a key
35673 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35677 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35679 <End of help on this topic>
35682 ====== h_config_smime_transfer_cacert_to_con =====
35685 <TITLE>S/MIME: Transfer CA Certs to Container</TITLE>
35688 <H1>S/MIME: Transfer CA Certs to Container</H1>
35691 The Transfer command will copy the CA certificates in your configured
35692 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>
35693 to the container in your configured
35694 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
35695 This might be useful if you decide to switch from using a CA cert directory to a CA cert
35698 Warning: Any previous contents in the container will be lost.
35701 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35705 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35707 <End of help on this topic>
35710 ====== h_config_smime_transfer_cacert_to_dir =====
35713 <TITLE>S/MIME: Transfer CA Certs to Directory</TITLE>
35716 <H1>S/MIME: Transfer CA Certs to Directory</H1>
35719 The Transfer command will copy the CA certificates in your configured
35720 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
35721 to the directory in your configured
35722 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
35723 This might be useful if you decide to switch from using a CA cert container to a CA cert
35727 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35731 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35733 <End of help on this topic>
35736 ====== h_config_smime_transfer_pubcon_to_key =====
35739 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
35742 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
35744 Mac OS X Alpine only.
35746 The Transfer command will copy the public certificates in your configured
35747 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35748 to your default Mac OS X Keychain.
35749 This might be useful if you decide to switch from using a cert container to using
35750 the Keychain to store your public certs, which you may do by using the
35752 <A HREF="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></A>.
35755 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35759 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35761 <End of help on this topic>
35764 ====== h_config_smime_transfer_pubkey_to_con =====
35767 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
35770 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
35773 The Transfer command will copy the public certificates in your configured
35774 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35775 to your default Mac OS X Keychain.
35776 This might be useful if you decide to switch from using a cert container to using
35777 the Keychain to store your public certs.
35780 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35784 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35786 <End of help on this topic>
35789 ====== h_config_smime_public_certificates =====
35792 <TITLE>S/MIME: Manage Public Certificates</TITLE>
35795 <H1>S/MIME: Manage Public Certificates</H1>
35798 This menu item allows you to manage your public certificates, this
35799 may include your own public certificate, but it normally includes
35800 certificates of people you correspond with. These certificates are
35801 saved by Alpine automatically when they are found in signed messages
35802 that you receive. This interface allows you to manage them, by
35803 giving you the option to delete them, or trust them (in the case
35804 of self-signed certificates).
35807 Please note that Alpine will not validate a message that was sent to you
35808 using a self-signed certificate, unless you decide to trust that certificate.
35809 Internally, a certificate is trusted by copying it to the
35810 <A HREF="h_config_smime_certificate_authorities">Certificate Authorities</A>
35811 collection. If you decide that you want to stop trusting a self-signed
35812 certificate, you must delete such certificate from such collection.
35814 The <B>I</B> Import command available in this screen allows you to
35815 import a command to this collection.
35818 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35822 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35824 <End of help on this topic>
35827 ====== h_config_smime_private_keys =====
35830 <TITLE>S/MIME: Manage Private Keys</TITLE>
35833 <H1>S/MIME: Manage Private Keys</H1>
35836 This option allows you to manage your private key. Normally a person has only
35837 one key, in the same way that a person only has one valid passport, or ID card,
35838 at any given time. This option allows you to manage private keys. You can
35839 delete them or import them. Additionally, you can view information
35840 about your public certificate, such as the issuer and the dates of validity
35841 of such certificate, among others.
35844 If you have more than one e-mail address for which you want to use the
35845 same private key, you must add all those addresses to the private key at
35846 the moment that the key is generated. When you receive a signed message using
35847 a key generated for several e-mail addresses, Alpine will save a
35848 certificate for each e-mail address included in such certificate.
35850 The <B>I</B> Import command available in this screen allows you to
35851 import a command to this collection.
35854 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35858 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35860 <End of help on this topic>
35863 ====== h_config_smime_certificate_authorities =====
35866 <TITLE>S/MIME: Manage Certificate Authorities</TITLE>
35869 <H1>S/MIME: Manage Certificate Authorities</H1>
35872 This collection contains certificates that are needed to validate the
35873 certificate of another person, and therefore contains certificates that
35874 you trust. Typically a certificate is signed by another entity, called a
35875 certificate authority. This option allows you to manage which certificates
35876 you trust, allowing you to import them and to delete them or view information
35877 about each certificate, such as the issuer and the dates of validity
35878 of such certificate.
35880 The <B>I</B> Import command available in this screen allows you to
35881 import a command to this collection.
35884 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35888 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35890 <End of help on this topic>
35893 ====== h_config_smime_password_file_certificates =====
35896 <TITLE>S/MIME: Manage Password File Certificates</TITLE>
35899 <H1>S/MIME: Manage Password File Certificates</H1>
35902 This option allows you to manage the certificates that are used to
35903 encrypt and decrypt your password file. This is useful in case you
35904 want to change the certificates used to encrypt your password file.
35906 Depending on the version of Alpine that you used for the first time
35907 to set this up, you might have had to enter a password to enter this
35908 screen. In the case that you did not enter a password to enter this
35909 screen, you should know two things that are important:
35911 <LI> If anyone takes control of your computer (for example, if you
35912 left it unattended) then that person can add a password to your
35913 password file and make it unreadable to you in the future.
35914 <LI> If anyone can access your computer (this includes remote access)
35915 then that person can steal your password file and decrypt it without
35916 your help. This gives access to that person to the same services you
35917 have access and such person can use your name to access that service.
35918 In particular, that person can try to hack into your service provider
35919 with your name on it, or that person could try to send spam with
35922 <P> Needless to say, this is not advisable. You should keep your
35923 password file protected. In order to do so, all you need to do is use
35924 the "Create Key" command to create a key. Once you do this,
35925 Alpine will use that key, encrypted with the password used to create that
35926 key, to protect your password file.
35928 In this screen you can import a new key to encrypt your password file,
35929 and read cryptographic information on your current key.
35931 To import a new key press "RETURN" and enter the location of
35932 the new key. You will be asked to enter the password of the new key. If
35933 this part of the process is successful, Alpine will search for the
35934 certificate that matches that key. If your key is named
35935 "your_email@address.com.key", then Alpine will look for your
35936 certificate in the same directory in the file named
35937 "your_email@address.com.crt", otherwise it will look for it
35938 as part of your key (that is, it will look to see if your certificate
35939 is in the file "your_email@address.com.key"), if all of this
35940 fails, Alpine will ask you to enter the location of the certificate
35941 that matches the key you unlocked. If a certificate is found, it will be
35942 used, and in this case, the password file will be read, decrypted with the
35943 old key and encrypted with the new key. Once this is done, the new key and
35944 certificates are saved, and the old keys are permanently deleted.
35946 Alpine does not create a backup of your password file, or your old keys
35947 that will be replaced. If you need to keep old copies, you will have to do
35948 this operation outside Alpine.
35950 Observe that you can use this screen to remove the password for the key.
35951 As explained earlier, this is not advisable, but you can always restore the
35952 password to encrypt your password file by creating a new key.
35954 Be safe and keep your password file encrypted with a password.
35956 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35960 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35962 <End of help on this topic>
35965 ====== h_certificate_information =====
35968 <TITLE>S/MIME: Certificate Information Screen</TITLE>
35971 <H1>S/MIME: Certificate Information Screen</H1>
35974 The CERTIFICATE INFORMATION screen shows you information contained in a certificate
35975 such as its owner, e-mail address, issuer, and interval of validity,
35978 In the case of public certificates, this screen shows you if there was a
35979 failure when attempting to validate such message. If the certificate is
35980 self-signed, then the <B>T</B> Trust command will be available, which
35981 you can use to trust such certificate and make Alpine not fail validating
35982 signatures signed with such certificate.
35984 You can also mark a certificate deleted, with the <B>D</B> command, or
35985 remove the deleted mark with the <B>U</B> undelete command.
35987 In the case of your private key, Alpine shows you the information
35988 from your public key. Additionally, Alpine allows you to see public
35989 and private information about your key, with the <B>B</B> and
35990 <B>R</B> commands respectively.
35992 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35996 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35998 <End of help on this topic>
36001 ====== h_config_smime_manage_public_menu =====
36004 <TITLE>S/MIME: Menu of Commands to Manage Public Certificates</TITLE>
36007 <H1>S/MIME: Commands that Manage Public Certificates</H1>
36010 This screen allows you to manage your public certificates.
36012 The format of this screen is as follows. There are five fields: The
36013 leftmost field is normally empty, but it could contain the letter
36014 "D" to indicate that that certificate has been marked for
36015 deletion. The next field is the e-mail address of the owner of the
36016 certificate, shown in its entirety. The third and fourth field are the
36017 first and last day validity for that certificate, respectively. The date
36018 is displayed in the user's locale unless the option
36019 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>
36020 is set. In this case, the month, day and year are represented by two
36021 digits, and the format used is mm/dd/yy. Finally, the fifth
36022 field is what can be displayed of the MD5 hash of the certificate. You can
36023 use any of the last three fields to distinguish between two certificates
36024 for the same owner.
36026 Available commands in this screen and a short description of what they
36029 <LI> <B>I</B> Imports a public certificate to this collection.
36030 <LI> <B>V</B> View information about a certificate such as the name of the person the
36031 certificate was issued to, its dates of validity, and validity status.
36032 <LI> <B>D</B> Marks a certificate deleted.
36033 <LI> <B>U</B> Removes the deletion mark on a certificate.
36034 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
36035 <LI> <B>T</B> This command is only available for self-signed certificates, and allows you to
36036 trust a certificate by copying it to the collection of trusted certificates.
36039 All commands provide feedback to let you know about their success or failure.
36042 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
36046 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36048 <End of help on this topic>
36051 ====== h_config_smime_manage_private_menu =====
36054 <TITLE>S/MIME: Menu of Commands to Manage Private Keys</TITLE>
36057 <H1>S/MIME: Commands that Manage Private Keys</H1>
36060 This screen allows you to manage your private key.
36062 The format of this screen is as follows. There are five fields: The
36063 leftmost field is normally empty, but it could contain the letter
36064 "D" to indicate that that certificate has been marked for
36065 deletion. The next field is the e-mail address of the owner of the
36066 certificate, shown in its entirety. The third field is the first day of
36067 validity for that certificate; the fourth field in the last day that that
36068 certificate is valid, and the fifth field is what can be displayed of the
36069 MD5 hash of the public certificate corresponding to this private key. You
36070 can use any of the last three fields to distinguish between two
36071 certificates for the same owner.
36073 Available commands and a short description of what they do follows.
36075 <LI> <B>I</B> Imports a new public key to this collection.
36076 <LI> <B>V</B> View information about the public certificate corresponding to this
36078 <LI> <B>D</B> Marks a key to be deleted.
36079 <LI> <B>U</B> Removes the deletion mark on a key.
36080 <LI> <B>X</B> Removes all keys marked deleted permanently (cannot be undone).
36081 Note that expunging a private key does not remove the public key, which must
36082 be removed separately.
36085 All commands provide feedback to let you know about their success or failure.
36088 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
36092 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36094 <End of help on this topic>
36097 ====== h_config_smime_manage_cacerts_menu =====
36100 <TITLE>S/MIME: Menu of Commands to Manage Certificate Authorities</TITLE>
36103 <H1>S/MIME: Commands that Manage Certificate Authorities</H1>
36106 This screen allows you to manage your collection of certificates that you
36109 The format of this screen is as follows. There are five fields: The
36110 leftmost field is normally empty, but it could contain the letter
36111 "D" to indicate that that certificate has been marked for
36112 deletion. The next field is the e-mail address of the owner of the
36113 certificate, shown in its entirety. The third field is the first day of
36114 validity for that certificate; the fourth field in the last day that that
36115 certificate is valid, and the fifth field is what can be displayed of the
36116 MD5 hash of the certificate. You can use any of the last three fields to
36117 distinguish between two certificates for the same owner.
36119 Available commands and a short description of what they do follows.
36121 <LI> <B>I</B> Imports a trusted certificate to this collection. This is
36122 done by reading the certificate and validating it. Once a certificate
36123 is found to be valid, it is saved, adding the extension ".crt"
36124 to the certificate, if necessary.
36125 <LI> <B>V</B> View information about this certificate, such as its issuer
36126 and validity dates.
36127 <LI> <B>D</B> Marks a certificate to be deleted.
36128 <LI> <B>U</B> Removes the deletion mark on a certificate.
36129 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
36132 All commands provide feedback to let you know about their success or failure.
36135 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
36139 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36141 <End of help on this topic>
36144 ====== h_config_lame_list_mode =====
36147 <TITLE>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></TITLE>
36150 <H1>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></H1>
36152 This feature modifies the method Alpine uses to ask your IMAP
36153 server for folder names to display in the FOLDER LIST screen.
36154 It is intended to compensate for a small set of IMAP servers that
36155 are programmed to ignore a part of the request, and thus respond
36156 to Alpine's query with nonsensical results.
36159 If you find that Alpine is erroneously displaying blank folder lists,
36160 try enabling this feature.
36163 NOTE: Enabling this feature has consequences for the Goto and Save
36164 commands. Many servers allow access to folders outside the area
36165 reserved for your personal folders via some reserved character,
36166 typically '#' (sharp), '~' (tilde) or '/' (slash). This mechanism
36167 allows, at the Goto and Save prompts, quick access to folders
36168 outside your personal folder collection without requiring a specific
36169 collection definition. This behavior will generally not be available
36170 when this feature is enabled.
36174 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36176 <End of help on this topic>
36179 ====== h_config_enable_mulnewsrcs =====
36182 <TITLE>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></TITLE>
36185 <H1>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></H1>
36187 This feature makes it so Alpine can use multiple newsrcs based on
36188 the news server being connected to, which allows for separate lists
36189 of subscribed-to newsgroups. When this feature is not set, there is only
36190 one list of newsgroups.
36192 Under this feature, the name of a newsrc is based on the news server.
36193 For example, if your <a href="h_config_newsrc_path"><!--#echo var="VAR_newsrc-path"--></a>
36194 is set to ".newsrc", and the news server you are connecting to is
36195 news.example.com, then the newsrc to be used is .newsrc-news.example.com.
36196 Setting this feature for the first time will allow for the option of using
36197 your old newsrc the next time you read news.
36199 If this feature is set, then the feature
36200 <A HREF="h_config_mulnews_as_typed"><!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></A>
36201 also may affect the name of the newsrc file that is used.
36204 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36206 <End of help on this topic>
36209 ======= h_ab_export_vcard =======
36212 <TITLE>Address Book Export Format</TITLE>
36215 <H1>Address Book Export Format</H1>
36217 You are exporting address book data from Alpine to a file outside of Alpine.
36218 You are being asked to choose the format of the export.
36219 Here are the choices:
36222 <DT><EM>A</EM>ddress List</DT>
36224 The addresses from the address book entries you are saving
36225 from will be saved one address per line.
36226 Address book lists (those with more than one address) will have
36227 all of their addresses saved separately.
36230 <DT><EM>V</EM>Card</DT>
36232 The entries will be saved in
36233 <A HREF="h_whatis_vcard">vCard</A> format.
36236 <DT><EM>T</EM>ab Separated</DT>
36238 The entries will be saved in tab-separated columns.
36239 There will be just 4 columns of data that correspond to Alpine's
36240 Nickname field, Full Name field, Address field, and Comment field.
36241 It might prove useful to Select only the Simple, non-List address book
36242 entries before Saving.
36245 <DT><EM>^C</EM> Cancel</DT>
36247 Cancel out of the Save.
36254 <End of help on this topic>
36257 ====== h_config_predict_nntp_server =====
36260 <TITLE>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></TITLE>
36263 <H1>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></H1>
36265 This feature allows Alpine to assume that the open NNTP server at the
36266 time of composition is the NNTP server to which the message should be
36267 posted. This is especially recommended when there are multiple News
36268 collections. If this feature is not set, Alpine will try to post to the first server in
36269 the <a href="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></a> variable. Setting
36270 this feature also negates the need to add News collection servers to
36271 the <!--#echo var="VAR_nntp-server"--> variable.
36273 This feature can be especially handy when used in conjunction with
36274 <a href="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></a>.
36277 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36279 <End of help on this topic>
36282 ====== h_config_nntp_search_uses_overview =====
36285 <TITLE>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></TITLE>
36288 <H1>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></H1>
36290 This feature should probably be turned on unless it causes trouble.
36291 The results of the NNTP overview command (XOVER) may be used to help
36292 with some searches in news groups.
36293 It should result in quicker response time.
36294 Turning this feature on apparently causes search results which are
36295 different from what you would get with the feature turned off on some
36299 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36301 <End of help on this topic>
36304 ====== h_config_thread_sorts_by_arrival =====
36307 <TITLE>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></TITLE>
36310 <H1>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></H1>
36312 This feature affects how a threading sort arranges threads. The default way
36313 to arrange threads is by the date of the earliest message in the thread.
36314 This feature arranges threads by the last message to arrive in a thread.
36316 This feature causes old threads that get recent messages to sort to the bottom,
36317 where previously a message arrival to a thread would not rearrange the order of
36321 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36323 <End of help on this topic>
36326 ====== h_config_textplain_int =====
36329 <TITLE>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></TITLE>
36332 <H1>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></H1>
36334 This feature modifies the method Alpine uses to display Text/Plain
36335 MIME attachments from the Attachment Index screen. Normally, the
36336 "View" command searches for any externally defined (usually
36338 "<A HREF="h_config_mailcap_path">Mailcap</A>" file) viewer,
36339 and displays the selected text within that viewer.
36342 Enabling this feature causes Alpine to ignore any external viewer
36343 settings and always display text with Alpine's internal viewer.
36347 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36349 <End of help on this topic>
36352 ====== h_config_wp_columns =====
36355 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></TITLE>
36358 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></H1>
36362 This configuration setting specifies the number of horizontal characters
36363 used to format various WebAlpine pages. Smaller values will tend to reduce
36364 the amount of horizontal scrolling required to view pages within narrow
36365 browsers, such as those found on PDAs, and larger values will tend to
36366 spread more information across the page.
36369 The Message List page uses the width to determine how many characters
36370 to assign each field. Note, a smaller value may result in a disproportionate
36371 amount of blank space between fields on each line. Similarly, a large
36372 value may result in cramped fields or horizontal scrolling.
36375 The Message View page uses this value to determine when to wrap lines
36376 in displayed message text. Note, a smaller value may result in jagged
36377 right margins or confusing quoting. A larger value may cause lines of text to
36378 run beyond the browser's right edge, requiring horizontal scrolling.
36382 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36384 <End of help on this topic>
36387 ====== h_config_wp_state =====
36390 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></TITLE>
36393 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></H1>
36397 Various aspects of cross-session state.
36401 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36403 <End of help on this topic>
36406 ====== h_config_wp_aggstate =====
36409 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></TITLE>
36412 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></H1>
36416 Aggregate operations tab state.
36420 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36422 <End of help on this topic>
36425 ====== h_config_wp_indexlines =====
36428 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></TITLE>
36431 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></H1>
36435 Number of index lines in table.
36439 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36441 <End of help on this topic>
36444 ====== h_config_wp_indexheight =====
36447 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></TITLE>
36450 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></H1>
36454 Index table row height.
36458 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36460 <End of help on this topic>
36463 ====== h_config_rss_news =====
36466 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss_news"--></TITLE>
36469 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-news"--></H1>
36477 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36479 <End of help on this topic>
36482 ====== h_config_rss_weather =====
36485 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></TITLE>
36488 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></H1>
36496 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36498 <End of help on this topic>
36501 ====== h_config_send_confirms_only_expanded =====
36504 <TITLE>FEATURE: send-confirms-only-expanded</TITLE>
36507 <H1>FEATURE: send-confirms-only-expanded (Web Alpine Only)</H1>
36509 This Web Alpine option specifies whether or not a Send confirmations
36510 happens when a composed message is readied for sending or not. The
36511 default behavior is to not confirm that the nicknames were expanded to
36512 the intended addresses.
36516 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36518 <End of help on this topic>
36521 ====== h_config_enable_jump_command =====
36524 <TITLE>FEATURE: enable-jump-command</TITLE>
36527 <H1>FEATURE: enable-jump-command (Web Alpine Only)</H1>
36529 This Web Alpine option specifies whether or not a Jump command is
36530 offered in the Message List and Message View pages. The command is
36531 implemented as an input field in the left column of the List and View
36535 When enabled and a number is entered in the input field while the
36536 Message List is displayed, the Message List is reframed with the
36537 specified message. While viewing a message, the message associated
36538 with the specified message number is displayed.
36542 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36544 <End of help on this topic>
36547 ====== h_config_enable_newmail_sound =====
36550 <TITLE>FEATURE: enable-newmail-sound</TITLE>
36553 <H1>FEATURE: enable-newmail-sound (Web Alpine Only)</H1>
36555 This Web Alpine option specifies whether or not a sound file is sent
36556 to the web browser along with the newmail notification message.
36561 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36563 <End of help on this topic>
36566 ====== h_config_render_html_internally =====
36569 <TITLE>FEATURE: render-html-internally</TITLE>
36572 <H1>FEATURE: render-html-internally (Web Alpine Only)</H1>
36574 By default, Web Alpine will pass cleansed HTML text you receive in messages
36575 to the browser for display (rendering). This feature causes Web Alpine to convert
36576 the HTML text into plain text in the same way Unix and PC-Alpine do.
36581 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36583 <End of help on this topic>
36586 ====== h_config_role_undo =====
36587 Yes, remember changes and exit back to list of roles; No, discard changes
36588 made in this screen; ^C, cancel exit and stay in this config screen.
36589 ====== h_exit_editor =====
36590 S, save changes and exit from the editor; D, do not save changes but
36591 do exit from the editor; or ^C, cancel exit and stay in the editor.
36592 ====== h_config_undo =====
36593 Yes, save changes and exit; No, exit without saving any changes made since
36594 entering this CONFIGURATION screen; ^C, cancel exit and stay in config screen.
36595 ====== h_os_index_whereis =====
36596 Enter ^V or ^Y to go immediately to the last or first message in the index.
36597 Or, enter the match string followed by RETURN.
36598 ====== h_os_index_whereis_agg =====
36599 Enter ^V or ^Y to go immediately to the last or first message in the index,
36600 Or, enter the match string followed by RETURN (or ^X to select all matches).
36601 =========== h_oe_add_full ==================
36602 Type the full name of the person being added and press the RETURN key.
36603 Press ^C to cancel addition.
36604 =========== h_oe_add_nick ==================
36605 Type a short nickname and press RETURN. A nickname is a short easy-to-
36606 remember word, name or initials like "joe", or "wcfields." ^C to cancel.
36607 ========== h_oe_add_addr ================
36608 Type the e-mail address and press RETURN.
36609 Press ^C to cancel addition.
36610 ========== h_oe_crlst_full ==============
36611 Type a long name or description for the list that you are creating and
36612 press RETURN. Press ^C to cancel creation of list.
36613 =========== h_oe_crlst_nick =============
36614 Type a nickname (short, easy-to-remember name or single word) for the list
36615 you are creating and press RETURN. Press ^C to cancel.
36616 ========== h_oe_crlst_addr ==============
36617 Type an e-mail address, or a nickname already in the address book that you
36618 want to be part of this list and press RETURN.
36619 ========== h_oe_adlst_addr =============
36620 Type an e-mail address or a nickname already in the address book that you
36621 want to add to this list and press RETURN.
36622 ========== h_oe_editab_nick ============
36623 Change the nickname using the arrow keys and delete key. Press RETURN
36624 when done. Press ^C to cancel editing and leave the nickname as it was.
36625 ========== h_oe_editab_full ============
36626 Change the full name using the arrow keys and delete key. Press RETURN
36627 when done. Press ^C to cancel editing and leave the full name as it was.
36628 ========== h_oe_editab_addr ============
36629 Change the address using the arrow keys and delete key. Press RETURN
36630 when done. Press ^C to cancel editing and leave the address as it was.
36631 ========== h_oe_editab_fcc ============
36632 Change the fcc using the arrow keys and delete key. Press RETURN when
36633 done. Press ^C to cancel editing and leave the fcc as it was.
36634 ========== h_oe_editab_comment ============
36635 Change the comment field using the arrow keys and delete key. Press RETURN
36636 when done. Press ^C to cancel editing and leave the comment as it was.
36637 ====== h_ab_forward =====
36638 Yes, expand nicknames and qualify local names with your current domain name;
36639 No, leave nicknames and local names as is; ^C, cancel.
36640 ========== h_ab_export ==========
36641 Type the name of a file to write the addresses into and
36642 press RETURN. You may also specify an absolute path. Use ^C to cancel.
36643 ========== h_ab_edit_a_field ==========
36644 Edit any of the fields of the currently selected entry by typing one of the
36645 letters at the bottom of the screen. Press ^C to cancel edit.
36646 ====== h_ab_del_data_revert =====
36647 Press B to completely delete addrbook and revert to default, C to delete config
36648 and revert while leaving data, or D to only delete data (make it empty).
36649 ====== h_ab_del_data_modify =====
36650 Press B to completely delete addrbook, C to delete configuration while leaving
36651 data, or D to delete data (make it empty) but leave config. ^C to cancel.
36652 ====== h_ab_del_config_modify =====
36653 Yes, remove this address book from my configuration.
36654 No, make no changes now.
36655 ====== h_ab_del_config_revert =====
36656 Yes, remove this address book from my config and revert to default.
36657 No, make no changes now.
36658 ====== h_ab_del_default =====
36659 Yes, remove this default address book from my configuration.
36660 No, make no changes now.
36661 ====== h_ab_really_delete =====
36662 Yes, delete the actual contents of the address book, not just the
36663 configuration. No, don't delete the data after all, cancel and start over.
36664 ====== h_ab_del_ignore =====
36665 Press I to ignore all the default address books for this category. Press R to
36666 remove this one address book and add the others to your personal list.
36667 ====== h_ab_del_dir_ignore =====
36668 Press I to ignore all the default directory servers for this category.
36669 Press R to remove this one server and add the others to your personal list.
36670 ====== h_ab_copy_dups =====
36671 Yes, overwrite the existing entry.
36672 No, skip duplicates but save the rest. Press ^C to cancel.
36673 ====== h_confirm_cancel =====
36674 Type C to Confirm that you want to abandon the message you are composing.
36675 Type N or ^C to cancel out of the cancel and keep composing.
36676 ====== h_ab_text_or_vcard =====
36677 Text, start composer with displayed text already included.
36678 VCard, start composer with address book entry attached as a vCard. ^C cancels.
36679 ====== h_ab_backup_or_ldap =====
36680 Backup, copy email address from entry and allow editing of it.
36681 LDAP, copy LDAP search criteria, do not allow editing of it. ^C cancels.
36682 ====== h_ldap_text_or_vcard =====
36683 Text: export displayed text for selected entry. Address: export only the
36684 email address. VCard: export entry in vCard format. ^C cancels.
36685 ====== h_ab_save_exp =====
36686 Save, save entry or entries to an address book.
36687 Export, save to file outside of pine. ^C cancels save.
36688 ====== h_ab_add =====
36689 A, add a brand new entry to this address book.
36690 E, edit the entry that is currently highlighted. ^C to cancel.
36691 ====== h_ab_shuf =====
36692 U, swap order of highlighted address book and the one above it.
36693 D, swap order of highlighted address book and the one below it. ^C to cancel.
36694 ====== h_ab_shuf_up =====
36695 U, swap order of highlighted address book and the one above it.
36696 Press ^C to cancel.
36697 ====== h_ab_shuf_down =====
36698 D, swap order of highlighted address book and the one below it.
36699 Press ^C to cancel.
36700 ====== h_folder_prop =====
36701 Count is # of messages in the folder, Unseen means messages that have not
36702 been read, New means messages that were Recently added to the folder.
36703 ====== h_role_shuf =====
36704 U, swap order of highlighted rule and the one above it.
36705 D, swap order of highlighted rule and the one below it. ^C to cancel.
36706 ====== h_role_shuf_up =====
36707 U, swap order of highlighted rule and the one above it.
36708 Press ^C to cancel.
36709 ====== h_role_shuf_down =====
36710 D, swap order of highlighted rule and the one below it.
36711 Press ^C to cancel.
36712 ====== h_incoming_shuf =====
36713 B, swap order of highlighted directory and the one before it.
36714 F, swap order of highlighted directory and the one after it. ^C to cancel.
36715 ====== h_incoming_shuf_up =====
36716 B, swap order of highlighted directory and the one before it.
36717 Press ^C to cancel.
36718 ====== h_incoming_shuf_down =====
36719 F, swap order of highlighted directory and the one after it.
36720 Press ^C to cancel.
36721 ====== h_dir_shuf =====
36722 U, swap order of highlighted directory and the one above it.
36723 D, swap order of highlighted directory and the one below it. ^C to cancel.
36724 ====== h_dir_shuf_up =====
36725 U, swap order of highlighted directory and the one above it.
36726 Press ^C to cancel.
36727 ====== h_dir_shuf_down =====
36728 D, swap order of highlighted directory and the one below it.
36729 Press ^C to cancel.
36730 ====== h_hdrcolor_shuf =====
36731 U, swap order of highlighted Header Color and the one above it.
36732 D, swap order of highlighted Header Color and the one below it. ^C to cancel.
36733 ====== h_hdrcolor_shuf_up =====
36734 U, swap order of highlighted Header Color and the one above it.
36735 Press ^C to cancel.
36736 ====== h_hdrcolor_shuf_down =====
36737 D, swap order of highlighted Header Color and the one below it.
36738 Press ^C to cancel.
36739 ========== h_oe_editab_al ============
36740 Change the address using the arrow keys and delete key. Press RETURN
36741 when done. Press ^C to cancel editing and leave the address as it was.
36742 ========== h_dir_comp_search ===============
36743 Type a string to look for just like you would in the composer. Your configured
36744 rules for the servers with the implicit flag set will be used.
36745 ========== h_oe_searchab ===============
36746 Type the word or name you want to search for and press RETURN. If you press
36747 RETURN without entering anything the word in [] will be searched for.
36748 ========== h_oe_chooseabook ==========
36749 Choose the address book you want to save the new entry in.
36750 Use ^N or ^P to change address books. ^C to cancel.
36751 ========== h_oe_takeaddr ==========
36752 Edit the e-mail address using the arrow and delete keys. Press RETURN
36753 when done. Press ^C to cancel adding this entry to the address book.
36754 ========== h_oe_take_replace ==========
36755 Press R to replace the old entry with this new data. You will still have
36756 another chance to cancel. N to enter another nickname. ^C to cancel now.
36757 ========== h_oe_take_replace_or_add ==========
36758 Press R to replace the old entry. Press A to add the selected addresses to
36759 the old existing list. N to enter another nickname. ^C to cancel now.
36760 ========== h_oe_takename ==========
36761 Edit the full name to be correct using the arrow and delete keys. Press RETURN
36762 when done. Press ^C to cancel adding this entry to the address book.
36763 ========== h_oe_takenick ==========
36764 Type a nickname (short easy-to-remember name, initials or single word) for this
36765 entry in the address book and press RETURN. Press ^C to cancel addition.
36766 ========== h_oe_jump ==========
36767 Type the message number you want to jump to and press RETURN. The word "end"
36768 represents the last message. Press ^C to cancel jumping to another message.
36769 ========== h_oe_jump_thd ==========
36770 Type the thread number you want to jump to and press RETURN. The word "end"
36771 represents the last thread. Press ^C to cancel jumping to another thread.
36772 ========== h_oe_debuglevel ==========
36773 Higher number shows more debugging details.
36774 Press ^C if you want to cancel the change.
36775 ========== h_oe_broach ==========
36776 Type the name of the folder you want to open and press RETURN. Press ^P/^N
36777 to go to the previous/next collections in the list. Press ^C to cancel goto.
36778 ========== h_oe_foldsearch ==========
36779 Type the text you want to search for in foldernames and press RETURN. If you
36780 press RETURN without entering anything, any text in [] will be searched for.
36781 ========== h_oe_foldrename ==========
36782 Change the old name of the folder to the new name using the arrow and
36783 delete keys and press RETURN. Press ^C to cancel rename.
36784 ========== h_oe_login ==========
36785 Enter your login name for the host you are opening the mailbox on. Just press
36786 RETURN to use your login from this host as is, or edit it with delete key.
36787 ========== h_oe_passwd ==========
36788 Type your password for the host and login shown as part of the prompt.
36789 Press ^C to cancel opening folder.
36790 ========== h_oe_choosep ==========
36791 Enter the number associated with the printer you want to select. Press ^C to
36792 cancel the printer selection. The current selection is highlighted.
36793 ========== h_oe_customp ==========
36794 Type the name of the Unix print command and press RETURN. Press ^C to
36795 cancel the printer selection.
36796 ========== h_oe_searchview ==========
36797 Type the word or name you want to search for and press RETURN. If you press
36798 RETURN without entering anything the word in [] will be searched for.
36799 ========== h_oe_keylock ==========
36800 The keyboard is in use and locked by another user. Only that user can
36801 unlock this keyboard by typing the password.
36802 ========== h_wt_expire ==========
36803 At the beginning of each month Alpine offers to rename your current sent-mail
36804 folder to one named for the month so you have a sent-mail folder for each month
36805 ========== h_wt_delete_old ==========
36806 It is the beginning of the month, and we need to conserve disk
36807 space. Please delete any sent-mail that you do not need.
36808 ========== h_select_sort ==========
36809 Select the order for sorting the index by typing the capitalized letter.
36810 Arrival is by arrival in your mailbox; Date is by time/day message was sent.
36811 ========== h_no_F_arg ============
36812 Enter name of file to be opened.
36814 ========== h_sticky_personal_name ==========
36815 Type in your name as you want it to appear on outgoing email. This entry
36816 will be saved into your Alpine configuration file.
36817 ========== h_sticky_inbox ============
36818 INBOX syntax is usually {complete.machine.name}INBOX
36819 This entry will be saved in your Alpine configuration file.
36820 ========== h_sticky_smtp ============
36821 The name of the computer on your campus that relays your outgoing email
36822 to the Internet. This entry will be saved in your Alpine configuration file.
36823 ========== h_sticky_user_id ==========
36824 The username or login-id part of your email address. This entry will be
36825 saved in your Alpine configuration file.
36826 ========== h_sticky_domain ==========
36827 The domain part of your email address, NOT the name of your PC. This
36828 entry will be saved in your Alpine configuration file.
36829 ========== h_bounce =========
36830 Enter the address or nickname of the intended recipient. Alpine will resend
36831 the message, which will retain the original author's From: address.
36832 ========== h_incoming_add_folder_nickname =========
36833 Enter an (optional) nickname that will be used in lieu of the actual
36834 host and folder names in the FOLDER LIST display.
36835 ========== h_anon_forward ==========
36836 Enter the address of your intended recipient, or ^C to cancel.
36837 Example: jsmith@somewhere.edu
36838 ========== h_news_subscribe ==========
36839 Enter the name of the newsgroup to which you wish to subscribe,
36840 or ^C to cancel. Example: comp.mail.pine
36841 ========== h_pipe_msg ==========
36842 Enter the name of the Unix command to which you wish to send this
36843 message, or ^C to cancel.
36844 ========== h_pipe_attach ==========
36845 Enter the name of the Unix command to which you wish to send this
36846 attachment, or ^C to cancel.
36847 ========== h_select_by_num ==========
36848 Enter a list of message numbers (or number ranges), or ^C to cancel. "end"
36849 is the last message. "." is the current message. Example: 1-.,7-9,11,19,35-end
36850 ========== h_select_by_thrdnum ==========
36851 Enter a list of message numbers (or number ranges), or ^C to cancel. "end"
36852 is the last message. "." is the current message. Example: 1-.,7-9,11,19,35-end
36853 ========== h_select_txt_from ==========
36854 Messages with From: headers containing the entered string will be selected.
36855 ^C to cancel. ^G again to see original options.
36856 ========== h_select_txt_not_from ==========
36857 Messages without From: headers containing the entered string will be selected.
36858 ^C to cancel. ^G again to see original options.
36859 ========== h_select_txt_to ==========
36860 Messages with To: headers containing the entered string will be selected.
36861 ^C to cancel. ^G again to see original options.
36862 ========== h_select_txt_not_to ==========
36863 Messages without To: headers containing the entered string will be selected.
36864 ^C to cancel. ^G again to see original options.
36865 ========== h_select_txt_cc ==========
36866 Messages with Cc: headers containing the entered string will be selected.
36867 ^C to cancel. ^G again to see original options.
36868 ========== h_select_txt_not_cc ==========
36869 Messages without Cc: headers containing the entered string will be selected.
36870 ^C to cancel. ^G again to see original options.
36871 ========== h_select_txt_subj ==========
36872 Messages with Subject: headers containing the entered string will be selected.
36873 ^C to cancel. ^X enters Subject: line of current message.
36874 ========== h_select_txt_not_subj ==========
36875 Messages without Subject headers containing the entered string will be selected.
36876 ^C to cancel. ^X enters Subject: line of current message.
36877 ========== h_select_txt_all ==========
36878 All messages containing the entered string will be selected. Headers and body,
36879 but not encoded attachments, will be compared. Enter ^C to cancel.
36880 ========== h_select_txt_not_all ==========
36881 All messages that don't contain the entered string will be selected. Headers
36882 and body, but not encoded attachments, will be compared. Enter ^C to cancel.
36883 ========== h_select_txt_body ==========
36884 All messages containing the entered string will be selected. Body text, but
36885 not headers or encoded attachments, will be compared. ^C to cancel.
36886 ========== h_select_txt_not_body ==========
36887 All messages that don't contain the entered string will be selected. Body
36888 text, but not headers or encoded attachments, will be compared. ^C to cancel.
36889 ========== h_select_txt_recip ==========
36890 Messages with Cc: or To: headers containing the entered string will be selected.
36891 ^C to cancel. ^G again to see original options.
36892 ========== h_select_txt_not_recip ==========
36893 Messages without Cc: or To: headers containing the string will be selected.
36894 ^C to cancel. ^G again to see original options.
36895 ========== h_select_txt_partic ==========
36896 Messages with Cc, To, or From headers containing the string will be selected.
36897 ^C to cancel. ^G again to see original options.
36898 ========== h_select_txt_not_partic ==========
36899 Messages without Cc, To, or From headers containing the string will be selected.
36900 ^C to cancel. ^G again to see original options.
36901 ========== h_select_date ==========
36902 If typed, date may be in DD-MMM-YYYY format (04-Jul-2006) or in ISO format
36903 (2006-07-04). ^P/^N also changes default date. ^X enters date of current msg.
36904 ========== h_attach_index_whereis ==========
36905 Enter some text that appears in the Attachment Index entry for the desired
36906 attachment. The first attachment containing that text will be highlighted.
36907 ========== h_kb_lock ==========
36908 Keystrokes entered here (up to a RETURN) comprise a password that must
36909 be entered again later in order to unlock the keyboard.
36910 ========== h_compose_default ==========
36911 N, compose a new message. R, set a role.
36913 ========== h_untranslatable ==========
36914 Send using UTF-8 character set; Send but replace untranslatable characters
36915 with question marks; return to the composer; or cancel message altogether.
36916 ========== h_compose_intrptd ==========
36917 N, compose a new msg. I, continue interrupted msg. R, set a role.
36919 ========== h_compose_postponed ==========
36920 N, compose a new message. P, continue postponed msg. R, set a role.
36922 ========== h_compose_intrptd_postponed ==========
36923 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
36924 R, set a role. ^C to cancel.
36925 ========== h_compose_form ==========
36926 N, compose a new message. F, use form letter. R, set a role.
36928 ========== h_compose_intrptd_form ==========
36929 N, compose a new msg. I, continue interrupted msg. F, use form letter.
36930 R, set a role. ^C to cancel.
36931 ========== h_compose_postponed_form ==========
36932 N, compose a new message. P, continue postponed msg. F, use form letter.
36933 R, set a role. ^C to cancel.
36934 ========== h_compose_intrptd_postponed_form ==========
36935 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
36936 F, use form letter. R, set a role. ^C to cancel.
36937 ========== h_config_context_del_except ==========
36938 If you delete the last exceptional collection you can only add it back by
36939 manually editing the exceptions config file.
36940 ========== h_config_whereis ==========
36941 To move quickly to a particular line, enter a search string or
36943 ========== h_config_edit_scorei ==========
36944 Enter interval in the form (min,max). -INF and INF may be used to represent
36945 -infinity and infinity. ^C to cancel change. RETURN to accept change.
36946 ========== h_config_add ==========
36947 Enter desired value; use normal editing keys to modify (e.g. ^K, ^D). Just
36948 pressing RETURN sets the Empty Value (this turns off any global default).
36949 ========== h_config_add_custom_color ==========
36950 Enter a header fieldname. For example, "subject" or "from".
36952 ========== h_config_add_pat_hdr ==========
36953 Enter a header fieldname. For example, "reply-to" or "organization" or
36954 any fieldname you want that isn't included already.
36955 ========== h_config_print_opt_choice ==========
36956 You may edit either the initialization string (characters printed before
36957 printing starts) or the trailer string. Choose one or ^C to cancel.
36958 ========== h_config_print_init ==========
36959 Enter a C-style string for this. You may use common backslash escapes like
36960 \\n for newline, \\ooo for octal character, and \\xhh for hex character.
36961 ========== h_config_change ==========
36962 Edit the existing value using arrow keys, ^K to delete entire entry, ^D to
36963 delete current (highlighted) character, etc. Enter ^C to cancel change.
36964 ========== h_config_replace_add ==========
36965 Replace ignores the current default, Add places the current default in your
36966 editing buffer as if you had typed it in.
36967 ========== h_config_insert_after ==========
36968 Enter a nickname for this print command. (InsertBefore puts the new item
36969 before the current line, InsertAfter puts it after the current line.)
36970 ========== h_config_print_cmd ==========
36971 Enter command to be executed for the printer. Use normal editing keys
36972 to modify, ^C to cancel, carriage return to accept current value.
36973 ========== h_config_role_del ==========
36974 Answering Yes will remove this rule completely from your rules list.
36975 ========== h_config_role_addfile ==========
36976 Type the name of a file to add to your configuration. You don't need to
36977 use a file, you may add rules directly (with Add) without using a file.
36978 ========== h_config_role_delfile ==========
36979 Answering Yes will remove this rule file completely from your rules list.
36980 The rules data file itself will not be removed.
36981 ========== h_config_print_del ==========
36982 Answering Yes will remove this printer completely from your printer list.
36983 ========== h_config_print_name_cmd ==========
36984 You may edit the Nickname of this printer, the Command to be executed when
36985 printing, or change the Options associated with this printer.
36986 ========== h_send_check_fcc ==========
36987 Yes, send message without an Fcc.
36988 No, return to composer.
36989 ========== h_send_check_subj ==========
36990 Yes, send message without a Subject.
36991 No, return to composer.
36992 ========== h_send_check_to_cc ==========
36993 Yes, send message without a To address, or a Cc address, or a Newsgroup.
36994 No, return to composer.
36995 ========== h_send_fcc_only ==========
36996 Yes, copy message to Fcc only and send to NO recipients.
36997 No, return to composer.
36998 ========== h_send_prompt ==========
36999 Yes, send the message.
37000 No or ^C, return to composer.
37001 ========== h_send_prompt_flowed ==========
37002 Yes, send the message. No or ^C, return to composer.
37003 What's Flowed? See Do Not Send Flowed Text in config screen.
37004 ========== h_send_prompt_dsn ==========
37005 Yes, send the message. No or ^C, return to composer.
37006 What's DSNOpts? See Enable Delivery Status Notification in config screen.
37007 ========== h_send_prompt_dsn_flowed ==========
37008 Yes, send the message. No or ^C, return to composer. What's DSNOpts? See
37009 Enable Delivery Status Notification. What's Flowed? See Do Not Send Flowed Text.
37010 ========== h_role_confirm ==========
37011 Yes, use displayed role. No, compose without a role.
37012 ^C, cancel the message. ^T, select a role from your other eligible roles.
37013 ========== h_norole_confirm ==========
37014 Return, compose without a role.
37015 ^C, cancel the message. ^T, select a role from your eligible roles.
37016 ========== h_custom_print ==========
37017 Enter a Unix command that accepts its data on standard input.
37018 Alpine will display any information the command sends to standard output.
37019 ========== h_convert_abooks_and_sigs ==========
37020 You will be given the opportunity to convert address books and signature files
37021 to remote configurations.
37022 ========== h_convert_abooks ==========
37023 You will be given the opportunity to convert address books to remote
37025 ========== h_flag_keyword ==========
37026 Enter the name of the keyword you want to add for this folder.
37027 No spaces, parentheses, braces, percents or asterisks are allowed.
37028 ========== h_select_keyword ==========
37029 Enter the keyword you want to match, or use ^T to select a keyword from a list
37030 of possible keywords for this folder. Use ! to look for non-matches instead.
37031 ========== h_type_keyword ==========
37032 Enter the keyword you want to add. You may add a nickname in the next step.
37033 No spaces, parentheses, braces, percents or asterisks are allowed.
37034 ========== h_type_keyword_nickname ==========
37035 Enter an optional nickname for the keyword you want to add.
37036 Type Carriage return to use the keyword name instead of a nickname.
37037 ========== h_convert_sigs ==========
37038 You will be given the opportunity to convert signature files to remote
37040 ========== h_convert_abook ==========
37041 Yes is fairly safe. You will be ADDing a remote address book that is a copy
37042 of the current address book. The current abook won't be removed automatically.
37043 ========== h_convert_sig ==========
37044 Answering Yes copies the contents of the signature file into your Alpine
37045 configuration file. After that, the contents of the file will not be used.
37046 ========== h_save_addman ==========
37047 Enter the simple name of the folder you want to add. Carriage return to
37048 accept what you have typed so far. ^C to get back to SELECT FOLDER screen.
37049 ========== h_reopen_folder ==========
37050 Yes reopens the folder, as if you were starting over. This uncovers new mail.
37051 No leaves the folder index as it was without discovering new mail.
37052 ========== h_convert_pinerc_server ==========
37053 This is the name of the host (computer) where the remote Alpine configuration
37054 will be stored. This should be an IMAP server that you have permission to use.
37055 ========== h_convert_pinerc_folder ==========
37056 Enter the correct remote folder name. This folder is special and should
37057 contain only configuration data. It shouldn't contain other mail messages.
37058 ========== h_role_compose ==========
37059 Compose a New message, Reply to current message, Forward current message, or
37060 Bounce message. Then you will be asked to choose one of your Roles to be used.
37061 ========== h_role_aggregate ==========
37062 Compose a reply, or forward, or bounce the selected messages. Then you
37063 will be asked to choose one of your Roles to be used for this operation.
37064 ========== h_save_size_changed ==========
37065 The reported size of a message is not the same as the actual size. Answer Yes
37066 to continue and hope for the best or No to Cancel the entire Save.
37067 ========== h_select_by_larger_size ==========
37068 Enter a number or ^C to cancel. All messages greater than this many characters
37069 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
37070 ========== h_select_by_smaller_size ==========
37071 Enter a number or ^C to cancel. All messages less than this many characters
37072 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
37073 ========== h_preserve_field ==========
37074 Use 'p' to toggle between preserving or not preserving the original To:
37075 and Cc: fields of the message. Enter ^C to cancel message.