| blob | 599aaa14f409483104258638f0ad4897c44d412a |
1 # $Id: pine.hlp 1266 2009-07-14 18:39:12Z hubert@u.washington.edu $
2 #
3 # T H E A L P I N E M E S S A G E S Y S T E M
4 #
5 #/* ========================================================================
6 # * Copyright 2013-2015 Eduardo Chappa
7 # * Copyright 2006-2008 University of Washington
8 # *
9 # * Licensed under the Apache License, Version 2.0 (the "License");
10 # * you may not use this file except in compliance with the License.
11 # * You may obtain a copy of the License at
12 # *
13 # * http://www.apache.org/licenses/LICENSE-2.0
14 # *
15 # * ========================================================================
16 # */
17 #
18 Help text for the Alpine mailer
20 This file is in a format created to be turned into text strings in a C
21 program.
23 There are two shell scripts that run on this. Cmplhelp.sh is the
24 first and turns this into a C file (helptext.c) of text strings that
25 are compiled and linked. The other program, cmplhlp2.sh, turns this
26 into a .h file (helptext.h) with extern string definitions of the
27 strings in the .c file. The code that actually processes these files
28 while alpine is running is in help.c
30 The lines with "===== xxxx ====" divide the different help screens. The
31 xxx is the name of the variable that strings will be put in, which are
32 also declared in helptext.h.
34 # is a comment
36 Help text screen text can be either plain text OR HTML. The latter is
37 denoted by the first line starting with "<HTML>". The former is simply
38 displayed as it's formatted here.
40 HTML is limited to simple formatting ala HTML 2.0. No forms, or tables.
41 In addition a small set of tools are are available to customize the HTML
42 screen's text:
44 1a) Default and function key bindings are separated like this:
46 <!--chtml if pinemode="function_key"-->
47 Function key bindings here
48 <!--chtml else-->
49 Default key bindings here
50 <!--chtml endif-->
53 1b) A way to distinguish HTML text that is to be displayed when
54 pine is running vs. when the text is served up outside Alpine
55 (someday) can be done via:
57 <!--chtml if pinemode="running"-->
58 Text displayed when viewed within a running pine session
59 <!--chtml else-->
60 Text displayed when HTML viewed outside pine (using chtml aware server)
61 <!--chtml endif-->
63 1c) A way to distinguish HTML text that is to be displayed under
64 PC-Alpine vs. not is available via:
66 <!--chtml if pinemode="os_windows"-->
67 Text displayed under PC-Alpine
68 <!--chtml else-->
69 Text displayed otherwise
70 <!--chtml endif-->
72 WARNING ABOUT CHTML "if-else-endif" CLAUSES: They don't nest.
74 2a) Several "server side include" commented elements are supported:
76 <!--#include file="textfile"-->
78 The file "textfile" will be inserted into the HTML text directly.
79 Alpine does no formatting of the text. At some point we might want to
80 look at the first line for <HTML> but not today.
82 2b) Various bits of Alpine's running state can be inserted into the
83 HTML text as well using the special comment:
85 <!--#echo var="variable"-->
87 Where "variable" is one of either:
89 ALPINE_VERSION
90 ALPINE_REVISION
91 ALPINE_COMPILE_DATE
92 ALPINE_TODAYS_DATE
93 C_CLIENT_VERSION
94 _LOCAL_FULLNAME_
95 _LOCAL_ADDRESS_
96 _BUGS_FULLNAME_
97 _BUGS_ADDRESS_
98 CURRENT_DIR
99 HOME_DIR
100 PINE_CONF_PATH
101 PINE_CONF_FIXED_PATH
102 PINE_INFO_PATH
103 MAIL_SPOOL_PATH
104 MAIL_SPOOL_LOCK_PATH
105 VAR_<VARNAME> - where <VARNAME> is config variable name
106 FEAT_<FEATURENAME> - where <FEATURENAME> is config feature name
108 3) The URL scheme "X-Alpine-Gripe:" is available to insert links to
109 pine's composer such that various debugging data can be attached to the
110 message. Aside from normal email addresses, this can be set to
111 either "_LOCAL_ADDRESS_" for the configured local help address, or
112 "_BUGS_ADDRESS_" for the configured local bug reporting address.
113 Aside from the special tokens above, the default behavior only differs
114 from "mailto:" by the insertion of a special Subject: prefix that
115 consists of a randomly-generated token for tracking purposes.
116 Several optional parameters can be included to control what is
117 attached or offered for attachment to the message:
119 ?config -- Automatically attaches the user's configuration
120 information to the trouble report
121 ?keys -- Automatically attaches the user's most recent
122 keystrokes
123 ?curmsg -- Causes the user to get an offer to attach the
124 current message to the trouble report
125 ?local -- Automatically attaches the result of the script
126 defined by VAR_BUGS_EXTRAS
128 For HTML-format sections, the help screen dividers "===== xxxx ====" must
129 contain one and only one space after the first and before the second set of
130 equal signs.
132 Note to authors of this file: to mark sections that need further revision,
133 please use the text string on the following line consistently so that it is
134 easy to find those places again in this file:
135 *revision needed*
137 NOTE: Several sections of help text which weren't being used were removed
138 at RCS version number 4.122. In particular, there were some placeholders
139 with help text for the config screen and the composer that didn't have any
140 reasonable place to be called from.
141 Dummy change to get revision in pine.hlp
142 ============= h_revision =================
143 Alpine Commit 108 2015-10-24 10:47:29
144 ============= h_news =================
145 <HTML>
146 <HEAD>
147 <TITLE>RELEASE NOTES for Alpine</TITLE>
148 </HEAD>
149 <BODY>
150 <H1>Alpine Release Notes</H1>
151 <DIV ALIGN=CENTER>
152 Version <!--#echo var="ALPINE_VERSION"--> (<!--#echo var="ALPINE_REVISION"-->)
153 <BR>
154 <!--chtml if pinemode="running"-->
155 (built <!--#echo var=ALPINE_COMPILE_DATE-->)
156 <!--chtml endif-->
158 <BR>
159 <BR>Copyright 2013-2015 Eduardo Chappa
160 <BR>Copyright 2006-2008 University of Washington
161 </DIV>
163 <P>
164 Alpine is an "Alternatively Licensed Program for Internet
165 News and Email" produced until 2009 by the University of Washington.
166 It is intended to be an easy-to-use program for
167 sending, receiving, and filing Internet electronic mail messages and
168 bulletin board (Netnews) messages. Alpine is designed to run on a wide
169 variety of Unix® operating systems. A version for Microsoft Windows®
170 is available as is a world wide web based version designed to run under the
171 Apache web server.
174 <H2>New in Alpine <!--#echo var="ALPINE_VERSION"--> (<!--#echo var="ALPINE_REVISION"-->)</H2>
176 Version <!--#echo var="ALPINE_VERSION"--> (<!--#echo var="ALPINE_REVISION"-->)
177 addresses bugs found in previous releases and has a few additions as well.
179 <P>
180 Additions include:
181 <UL>
182 <LI> Ignore message from smtp server after a successful authentication
183 challenge.
185 <LI> If SSLDIR is defined somehow, do not disable S/MIME if the
186 SSLCERTSDIR is not found.
188 <LI> When Alpine sends an attachment, it will set the boundary attribute
189 in lower case, as some SMTP servers, such as those of libero.it
190 reject messages if the boundary attribute is in uppercase.
192 <LI> SMIME: The ^E command that gives infromation on the certificate
193 is only available for messages that have a signed or encrypted
194 part.
196 <LI> SMIME: If a message contains a RFC822 atachment that is
197 signed/decrypted add the ability to view its SMIME information.
199 <LI> SMIME: Certificate information in the S/MIME screen is available
200 for certificates stored in a cotainer.
202 <LI> SMIME: Offer the common name of the person, instead of the name of
203 file containing the certificate, as the name to be displayed in the
204 certificate management screen for certificate authorities.
205 Suggested by Matthias Rieber.
207 <LI> SMIME: Management of several alternate name (SAN) certificates is
208 improved. When importing a SAN certificate, also import a certificate
209 for the filename, besides for the e-mail addresses in the
210 certificate. Suggested by Matthias Rieber.
212 <LI> SMIME: add full year when displaying information about a certificate
213 in the certificate management screen. Suggested by Matthias Rieber.
215 <LI> SMIME: sort certificates by some type of alphabetical order in the
216 displayed name.
218 <LI> HTML: Add support for decoding entities in hexadecimal notation.
219 Suggested by Tulipánt Gergely.
221 <LI> If the charset of a message can not be determined, use the value set
222 in the <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A> for its value.
224 <LI> Resizing setup screen will redraw screen.
226 <LI> Unix Alpine only. Experimental: If Alpine/Pico finds a UCS4 code
227 in the width ambiguous zone, it will use other means to determine
228 the width, such as call wcwidth.
230 <LI> Pico: Code reorganization in the search command to make it easier to
231 add subcommands of the search command.
233 <LI> Pico: Search command can do a case sensitive match. Use the Ctrl-^
234 subcommand of the search command to bring this choice into view.
236 <LI> Pico: Add the ability to search for strings in the beginning or end
237 of a line. Use the Ctrl-^ subcommand of the search command to bring
238 this choice into view.
240 <LI> For a multipart/alternative message, the Take Address command will
241 work on the part that is being read.
243 <LI> When sending a message, allow for 512 characters of consecutive
244 non-white space before folding the subject line.
246 <LI> Make sure titlebar (the line at the top of the screen) always
247 contains the name of the folder/newsgroup that is open, if this
248 fits in the title.
250 <LI> The feature <a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
251 will also scramble the name, version and operative system in the message-id header.
252 Based on a contribution by Dennis Davis, which is itself based on a contribution by
253 Mark Hills.
255 <LI> Change in logic in imap_set_password function to make Alpine ask if
256 a user wants to save a password before reading the password file.
258 <LI> Add the Control-R subcommand to the save command for attachments.
259 This subcommand toggles if the saving will be done in binary mode
260 for text attachments. When a user saves an attachment using binary
261 mode it will be saved as it was sent, otherwise the attachment will
262 be transformed to UTF-8 for further transformation through internal
263 and user defined filters for saving.
265 <LI> Add command line argument -smimedir, which allows to specify
266 the default path for a directory that contains the public, private,
267 and ca directories. This is useful in case a user has a backup of
268 old certificates that cannot be installed in the ~/.alpine-smime
269 dir.
271 <LI> Reimplementation of the code that allows the .pinerc file to be a
272 symbolic link by Kyle George from tcpsoft.com to use realpath.
274 <LI> When saving an attachment, the "^T" command leads to a screen where the
275 "A" command can be used to add a file. A directory can be added by
276 pressing "^X" after the "A" command. Added after a suggestion by
277 Stefan Goessling.
279 <LI> When saving an attachment, the ^Y and ^V commands allow a user to
280 scroll through the history of directories used to save attachments,
281 while preserving the given name of the file. Suggested by Peter
282 Koellner.
284 <LI> SMIME: Turn off automatic signing and encrypting of a message when
285 bouncing. Suggested after a discussion with Matthias Rieber.
286 </UL>
289 <P>
290 Bugs that have been addressed include:
291 <UL>
292 <LI> SMIME: Crash when a certificate has an invalid date of validity. Also
293 Alpine will use the function ASN1_TIME_print to determine the date
294 of validity. Reported by Ben Stienstra.
296 <LI> SMIME: Crash when atempting to unlock the password file and an
297 incorrect password is entered.
299 <LI> SMIME: Crash when checking the signature of a message that contains
300 a RFC822 attached message. Reported by Holger Trapp and Björn
301 Krellner.
303 <LI> SMIME: Cancelling entering password to unlock key will not reprompt.
305 <LI> SMIME: fix a bug that did not allow users to transfer certificates to
306 remote containers. Reported by Matthias Rieber.
308 <LI> SMIME: certificates included in messages were not being transferred
309 to a remote container.
311 <LI> SMIME: Crash if public certificates are located in an inaccessible
312 remote server and the private key is not available.
314 <LI> Pico: Searching for a string that is too long causes Pico to crash
315 in the next search.
317 <LI> Fix vulnerability in regex library. This only affects those who use
318 this library, such as the windows version of Alpine. See
319 <A HREF="http://www.kb.cert.org/vuls/id/695940">http://www.kb.cert.org/vuls/id/695940</A>
320 for more details.
322 <LI> Alpine would not set include and lib paths for OpenSSL if this was
323 installed in /usr/local/ssl.
325 <LI> If the .pinerc file is a symbolic link, Alpine might not write its
326 contents when saving its configuration.
328 <LI> The _INIT_ token does not skip over non-alpha numeric characters in
329 the name. Reported by Andreas Fehr.
331 <LI> Mismatch in size of UCS and CELL caused a corruption in the
332 content of a pointer, which made the speller in PC-Alpine get the
333 content of a word incorrectly.
335 <LI> Skip testing openssl compatibility version when cross-compilation
336 is detected. Fix contributed by Antti Seppälä
338 <LI> Alpine fails to remove temporary files used during a display or sending
339 filter. Fix contributed by Phil Brooke.
341 <LI> When the index is in zoomed state, adding new messages to the
342 selection would not show those messages if those messages are on
343 top of the current message in the top of the screen. Reported by
344 Ulf-Dietrich Braumann.
346 <LI> Crash when reviewing history of saving attachments.
348 <LI> Crash in Pico when forwarding messages that contain a direction mark
349 at the end of a line. Reported by James Mingo.
350 </UL>
353 <P>
354 Version 2.20 addresses bugs found in previous releases and has several
355 additions as well.
357 <P>
358 Additions include:
359 <P>
361 <UL>
362 <LI> Upgrade UW-IMAP to Panda IMAP from
363 <A HREF="https://github.com/jonabbey/panda-imap">https://github.com/jonabbey/panda-imap</A>.
364 <LI> S/MIME: Add screen to manage certificates.
365 <LI> S/MIME: Signatures are validated using the user's certificates instead
366 of the ones included in the message. Behavior can be disabled by
367 disabling the option <A href="h_config_smime_use_cert_store">
368 <!--#echo var="FEAT_smime-use-storey-only"--></A>, which is enabled
369 by default.
370 <LI> S/MIME: sign messages using intermediate certificates when needed
371 and possible.
372 <LI> S/MIME: validation of certificates for servers that modify signed
373 content.
374 <LI> S/MIME: signed and encrypted messages will be signed first and
375 encrypted second, so that they can be decoded by other clients.
376 <LI> S/MIME: add the sender certificate to the list of certificates in
377 encrypted messages to make it possible for the sender to decrypt
378 the message they sent.
379 <LI> S/MIME: When transferring certificates to a local container, create
380 container with default names PublicContainer, PrivateContainer and
381 CAContainer, as appropriate for these files, unless the user has
382 provided some other names.
383 <LI> S/MIME: Forwarding a message will include the signed part as part
384 of the text and not as a multipart message, just as the reply
385 command does.
386 <LI> HTML: Style tag in body of html message causes Alpine to not write
387 its content until a new </style>
388 <LI> HTML: <BR>, <BR />, and <BR/> are considered
389 the same inline tag; the same is valid for the <HR> tag.
390 <LI> Add support to selective expunge through a subcommand of the
391 select-apply commands. Read more in the <A
392 HREF="h_index_cmd_expunge">help</A> for the expunge command.
393 <LI> Pico: New subcommand of the search command, allows to reverse the
394 direction of search.
395 <LI> Unix Alpine: If a password file is defined, and S/MIME is enabled,
396 the key and certificate used to encrypt the password file are saved
397 in the ~/.alpine-smime/.pwd directory, or in the directory specified
398 by the -pwdcertdir command line option.
399 <A HREF="h_password_file_support">Learn more</A>.
400 <LI> Add /tls1, /tls1_1, /tls1_2 and /dtls1 to the definition of a
401 server to use different ways to connect using ssl, for
402 example {server.com/tls1} will attempt to connect to
403 server.com at the ssl imap port (port 993) and establish a
404 connection using TLSv1. These flags can be used in
405 conjunction with the /ssl flag, the ssl flag is redundant.
406 Conversely, however, the /ssl flag does not imply any of
407 these flags; the /ssl flag means SSLv3 or, if not available,
408 SSLv2 in the SSL port.
409 <LI> Alpine does not attempt to automatically reopen a collection
410 that was not opened due to cancellation by the user.
411 Instead, the user must try to open it explicitly.
412 <LI> Alpine searches for a certificate that matches an email address in
413 all addresses in a certificate (instead of just the first
414 one) but when it tries to unlock the certificate, it asks
415 for the password for the first email address in that
416 certificate.
417 <LI> Style tag in body of html message causes Alpine to not write its content
418 until a new </style>
419 <LI> Experimental: Write the content-type of a message in
420 lowercase, as some non-compliant servers do not understand
421 uppercase content-type, such as those of GMX.de.
422 <LI> Experimental: Do not send the RSET command before attempting
423 to send a message, as this causes a delay in some evily managed
424 servers.
425 <LI> Opening a folder updates recent count in maildrops (this
426 already works for other types of folders)
427 <LI> Automatically redraw screen after opening an attachment
428 instead of simply clearing it.
429 <LI> Pico: Justification works without need of a predefined quote
430 string. This allows justification of blocks of text that are
431 indented with spaces.
432 <LI> Decode the name of attachment names, so they can be written as part
433 of the description of the part.
434 <LI> Check bounds and tie strings off to improve security. Contributed
435 by James Jerkins.
436 <LI> Replace tabs by spaces in From and Subject fields to control for
437 size in screen of these fields. Change only in index screen display.
438 <LI> Aggregate operations allows bouncing a list of messages using a role.
439 Suggested by Ulf-Dietrich Braumann.
440 <LI> Disable saving new passwords to the password file. Implemented
441 by Louis Raphael from dpslabs.com. <A HREF="h_config_disable_password_file_saving">Learn more.</A>
442 <LI> Makefile: Add $(LIBINTL) to the flags to link rpdump, rpload,
443 alpined and alpineldap because MAC OSX 10.8 x86_64 needs it. Reported by
444 Charles M. Register.
445 </UL>
448 <P>
449 Bugs that have been addressed include:
450 <UL>
451 <LI> Fix _INIT_ token for reply quote string to include support for 8-bit
452 in personal names. Reported by Lev Gorenstein.
453 <LI> When writing the .pinerc file, lines were truncated if they were longer
454 than 10,000 characters. This could cause data corruption, so now lines
455 are allowed to be of any length.
456 <LI> In Unix Alpine (but not in MAC OSX) fix a problem that made Alpine
457 remove attachments before they were open by a mailcap viewer. It
458 requires that the user has an equivalent to a command such as "ps
459 auxww" to list the list of processes, and check if there is any
460 program using the attachment. The default is "/bin/ps auxww", but
461 it can be changed at compile time with the option --with-ps-cmd.
462 See the help of the variable
463 <a href="h_config_psleep"><!--#echo var="VAR_mailcap-check-interval"--></a>
464 for more information.
465 <LI> S/MIME: signed messages that contained an attachment would not validate.
466 <LI> S/MIME: signed and encrypted messages from Thunderbird would not
467 validate. Thanks to Andreas Schamanek for testing, debugging and
468 advising during the process of fixing this problem.
469 <LI> S/MIME: Forwarding messages with multipart content-type failed to be signed
470 with "Error writing pipe" message. Reported by Andreas Schamanek
471 and Stefan Mueller.
472 <LI> S/MIME: Certificates are lost when using a pinerc file outside of the
473 home directory.
474 <LI> S/MIME: Accessing the S/MIME configuration screen would deinitialize
475 SMIME making it not possible to sign or encrypt messages.
476 <LI> S/MIME: Forwarding a signed message might make the body contain mime
477 information that is not part of the body, and hence making the body
478 of the message seem wrong.
479 <LI> S/MIME Alpine would compute incorrectly the signature of a message
480 that contains 8bit if the option "Enable 8bit ESMTP Negotiation" is
481 enabled, the message contains 8bit characters and the smtp server
482 supports 8bit sending.
483 <LI> When replying to several messages, subject will be decoded first,
484 and then stripped from re/fwd before they are compared to determine
485 the subject of the replied message.
486 <LI> Crash when tcp connection to NNTP server was lost after connection
487 had been established, but lost immediately afterwards.
488 <LI> Crash with message "lock when already locked", when painting
489 an index was based on scores that needed information from a remote
490 addressbook in the same server as the folder opened. Reported by
491 Peter Koellner.
492 <LI> Crash in message/rfc822 attachments encoded in base64.
493 <LI> Postponed messages whose content-type is text/html, text/enriched and
494 text/richtext are sent with that content-type, even though, after
495 resuming composition, Alpine had changed its type to text/plain.
496 <LI> Alpine cannot handle correctly some characters in the Windows-1256
497 character set, which might lead to a crash or a corruption in the
498 screen. Work was done to contain the bug. A more complete fix will
499 be done in a future release. Reported by Professor Robert Funnell.
500 <LI> WebAlpine: add _GNU_SOURCE to make pubcookie build.
501 <LI> WebAlpine: fail to build with debug disabled. Fix from Sam Hathaway.
502 <LI> Save command did not warn of existence of a message with a deleted
503 attachment in an aggregate save, unless cursor was positioned on a message
504 with a deleted attachment. Reported by Florian Herzig.
505 <LI> Transformation of UTF-8 to MUTF7 was not being done when creating a folder
506 in an IMAP server.
507 <LI> DATE tokens were not internally transformed to UTF-8, which made their
508 values not appear complete in the screen. Reported by Werner Scheinast.
509 <LI> Fixes to configure script so that it will not require PAM for every system.
510 <LI> Fix to configure script so that it will use CPPFLAGS instead of
511 CPPCFLAGS, and so the --with-ssl-include-dir option take effect
512 during the build. Fix by Ulf-Dietrich Braumann.
513 <LI> Fix in WebAlpine: do not use deprecated dereference in pointer,
514 needs to use tcl_getstringresult() instead. Reported by
515 Ulf-Dietrich Braumann.
516 <LI> Quoted string in URL Viewers configuration variable were not
517 unquoted before passing to viewer.
518 <LI> Fix in configure script to detect location of tcl library; add
519 /usr/local in FreeBSD and fix a bug in configure script that used
520 $alpine_TCLINC instead of $alpine_TCLINC/tcl.h. Reported and fixed
521 by Werner Scheinast.
522 <LI> Move SSL configurations from UW-IMAP to configure script, and
523 update OpenSSL configuration for Mac OS X.
524 <LI> Remove -lregex from linker flags when building --with-supplied-regex.
525 <LI> When the download of an attachment is interrumpted, Alpine stills
526 caches what was downloaded, making the download incomplete for
527 subsequent calls of Alpine attempting to open the attachment. In the
528 future, Alpine will not cache any downloaded part of the attachment
529 when it is interrupted.
530 </UL>
531 <P>
534 <P>
535 Version 2.11 addresses bugs found in previous releases and has a few
536 additions as well.
538 <P>
539 Additions include:
540 <P>
542 <UL>
543 <LI> Alpine requires version 1.0.0c of Openssl to build.
544 <LI> Increase encryption of S/MIME encrypted messages.
545 <LI> Pico: Improvements in justification of paragraphs: lines that begin
546 with a quote string, followed by a space were considered individual paragraphs,
547 now they are considered part of a paragraph. Based on earlier joint work
548 with Jeff Franklin.
549 <LI> Unix Alpine: Allow local .pinerc file to be a symbolic link.
550 <LI> Experimental extended support of recognition of UTF-8 in urls based on
551 information from <A HREF="http://url.spec.whatwg.org">http://url.spec.whatwg.org</A>.
552 <LI> Added recognition of ws and wss URIs.
553 <LI> Add ability to <A HREF="h_config_folder_color">color folder names</A>,
554 <A HREF="h_config_directory_color">directory names</A>,
555 and <A HREF="h_config_folder_list_color">text</A> in the FOLDER SCREEN.
556 <LI> Add the ability to <A HREF="h_config_indextoken_color">color any token</A>
557 used in the display of the INDEX SCREEN.
558 <LI> New option <A HREF="h_config_preserve_field"><!--#echo var="FEAT_preserve-original-fields"--></A>
559 that adds the ability to preserve To: and Cc: fields when replying to a
560 message, as specified by original sender.
561 <LI> Add a _SILENT_ token to the <A HREF="h_config_display_filters">list of tokens</A>
562 for a display filter, so that Alpine will not redraw the screen when it is unnecessary.
563 <LI> Quota command includes subcommands for printing, forwarding, etc.
564 </UL>
566 <P>
567 Bugs that have been addressed include:
568 <P>
569 <UL>
570 <LI> Crash when a non-compliant SMTP server closes a connection without a QUIT command.
571 <LI> Crash when resizing the screen in a configuration screen.
572 <LI> Do not bail out during a tcp timeout, instead close connection and avoid crash.
573 <LI> Do not use a shell to open a browser.
574 <LI> Configure script did not test for crypto or pam libraries.
575 <LI> Configure script attempted to build web component, even if header file tcl.h was not present.
576 <LI> Change Cygwin directory separator to "/".
577 <LI> Alpine could set List- headers, contrary to RFC 2369.
578 </UL>
580 <P>
581 Version 2.10 addresses bugs found in previous releases and has a few
582 additions as well.
584 <P>
585 Additions include:
586 <P>
588 <UL>
589 <LI> Quota report for IMAP folders that support it (press the "@" command in the index screen of such folder).
590 <LI> Search a folder for the content of any header with the ";" command.
591 <LI> Foreign characters are decoded correctly in IMAP folder names.
592 <LI> Question about breaking connection to slow servers includes their name.
593 <LI> Internal x-alpine-help: resource locator for sending links to internal help.
594 <LI> OpenSuse: Alpine find location of OpenSSL certificates.
595 <LI> Cygwin: Alpine builds without need of patch.
596 <LI> Recognition of proper mime type for docx, xlsx, and pptx files.
597 <LI> When composing a message, Alpine will create a new thread when the subject is erased.
598 <LI> Add support for strong encryption of password file when S/MIME is built in.
599 </UL>
601 <P>
602 Bugs that have been addressed include:
603 <P>
605 <UL>
606 <LI> Alpine will close a folder after confirming with user their intention and not reopen it.
607 <LI> Double allocation of memory in Pico.
608 <LI> Alpine does not give warning of message sent and posted upon receipt by email of message posted in newsgroup.
609 <LI> Handling of STYLE html parameter may make Alpine not display the content of a message.
610 <LI> Not recognition of environment variables in some options.
611 <LI> Not display of login prompt during initial keystrokes.
612 <LI> justification of long urls breaks them.
613 <LI> Incorrect New Mail message when envelope is not available.
614 <LI> Incorrect display of PREFDATE, PREFDATETIME and PREFTIME tokens.
615 <LI> Crash when resizing the screen after display of LDAP search.
616 <LI> Crash when redrawing screen while opening a remote folder collection.
617 <LI> Infinite loop in scrolltool function during notification of new mail.
618 <LI> No repaint of the screen after midnight was done when the SMARTDATE token is used in the index screen.
619 <LI> No display of signed and encrypted S/MIME messages.
620 <LI> Alpine will not build with OpenSSL.
621 <LI> Crash for double locking in calls to c-client.
622 <LI> Bad recognition of mime-encoded text may make Alpine not print the subject of a message.
623 <LI> Ignore the references header when threading messages
624 <LI> No update of colors in index screen after update to addressbook.
625 </UL>
627 <P>
628 Version 2.01 addresses bugs found in previous releases and has a few
629 additions as well.
631 <P>
632 Additions include:
633 <P>
635 <UL>
636 <LI> Fixed non-ASCII web alpine handling
637 <LI> Added web alpine help.
638 <LI> Allow web alpine inbox on second IMAP server.
639 <LI> Allow web alpine config reset after bad inbox-path gets set.
640 <LI> Added web alpine ability to create group contact from contact list members.
641 <LI> Backed out web alpine coercing of default sort-key of arrival to date/reverse.
642 <LI> Tidied up web alpine script layout.
643 <LI> Fixed web alpine status message ordering
644 <LI> Added web alpine Fcc setting via Contacts in Compose
645 <LI> Fixed web alpine autodraft attachment issues
646 <LI> Fixed web alpine problems with recent count maintenance
647 <LI> Fixed web alpine newmail arrival display in message list
648 <LI> Added web alpine confirmation to folder create for Move/Copy
649 <LI> Added web alpine user-domain support
650 <LI> Fixed web alpine to support INBOX-within-a-collection deletion
651 </UL>
653 <P>
654 Bugs that have been addressed include:
655 <P>
657 <UL>
658 <LI> In web alpine fixed delete all selected within a search result to reorient
659 correctly to whole-mailbox message list.
660 <LI> Fixed web alpine delete in view page to be sensitive to sort
661 <LI> Fixed web alpine open of folder within directory from folder manager page.
662 <LI> Fixed web alpine open of folder within directory from left column's recent cache.
663 <LI> Fixed web alpine problems with spaces in special folder names like Drafts
664 <LI> Fixed web alpine adding contacts from message list and view
665 <LI> Fixed web alpine create of non-existent fcc
666 <LI> Remove mistakenly left debugger statement in web alpine javascript.
667 <LI> Some UNIX alpine build problems fixed
668 <LI> Crash in pico and pilot when nl_langinfo returned something unrecognizable
669 or NULL. Add recognition of "646" to nl_langinfo wrapper. This is returned
670 by locale charmap call on some Solaris 8 systems.
671 <LI> MacOS Keychain logins were not working correctly with generic host names, like
672 imap.gmail.com, as opposed to specific instances like rx-in-209.google.com, causing
673 new password requests when not needed
674 <LI> Possible crash in WhereIs command while in FOLDER LIST when cursor is located on the
675 last folder in the list
676 <LI> Change to S/MIME get_x509_subject_email so that X509v3 alternative names are
677 looked for along with the email address
678 <LI> Changes to configure to get spellcheck options with work with arguments.
679 <LI> Add change from Mark Crispin of panda.com to at least minimally handle non-ascii hostname
680 returned by gethostname (iPhone can do this)
681 <LI> Fixed a bug that prevents a filter that moves a message into a local folder
682 from also setting the DELETE flag in that moved message. Fix from Eduardo Chappa.
683 <LI> Changed size of shellpath in open_system_pipe from 32 to MAXPATH. Fix from
684 Jake Scott of marganstanley.com.
685 <LI> Buffer overflow bug in c-client's tmail/dmail, fix from Mark Crispin. This
686 is not used in alpine.
687 <LI> Imapd server crash from unguarded fs_give in IDLE code, fix from Crispin.
688 Apparently this causes RIM Blackberry BIS service problems. This is not
689 used in alpine.
690 <LI> Tmail uninitialized pointer fix from Neil Hoggarth. Not used in alpine.
691 <LI> Buffer overflow possibility in RFC822BUFFER routines in c-client library.
692 Fix from Ludwig Nussel of SUSE and from Crispin.
693 <LI> Include whole filename in export filename history
694 <LI> Fix display bug in pico when Replace command is canceled. Fix from Eduardo Chappa.
695 </UL>
697 <P>
698 Version 2.00
699 addressed bugs found in previous releases and had a few additions as well.
700 <P>
701 Additions included:
702 <P>
704 <UL>
705 <LI> Redesigned Web Alpine interface
706 <LI> Experimental <A HREF="h_mainhelp_smime">S/MIME support</A> added
707 in UNIX versions of Alpine
708 <LI> Attempt to include the attachment filename as part of the name of the
709 temporary file used when viewing an attachment with an external program.
710 Add some randomness to that filename to make it hard to predict the filename.
711 Add a filename extension, usually derived from the type/subtype, to the
712 temporary filename. This was previously done only on Windows and MacOS X.
713 <LI> Enhance address completion in the composer (TAB command) so that it looks
714 through nicknames, fullnames, and addresses from the address book; addresses
715 from the message being viewed, if any; and the results from
716 <A HREF="h_direct_config">LDAP Directory Server</A>
717 lookups for all of the defined directory servers that have the
718 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
719 feature set.
720 <LI> Make the default character set setting more liberal in what it will accept
721 from the UNIX nl_langinfo call and the various values of LANG seen in the wild
722 <LI> Remove the Alpine revision number from the titlebar in released versions
723 while leaving it there in snapshot versions
724 <LI> Add a <A HREF="h_config_quell_asterisks">feature</A> to suppress the
725 display of asterisks when you type a password for Alpine
726 <LI> Add line wrapping when displaying <EM>PRE</EM> formatted sections of HTML
727 <LI> When the
728 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
729 feature is turned on convert not only the dates in the index screen but also
730 the dates in the MESSAGE VIEW
731 </UL>
733 <P>
734 Bugs addressed in the 2.00 release included:
735 <P>
737 <UL>
738 <LI> Crash when using tab-completion for selecting a Save filename
739 <LI> Make Web Alpine help text images relative for more portability
740 <LI> Fixed attach save of html parts in Web Alpine
741 <LI> Viewing, printing, exporting, replying, and bouncing of message
742 digests was broken. Replying and bouncing should not have been
743 allowed at all for digests. It would be nice to have a more standard
744 index-like view of a message digest but that has not been addressed
745 with this minor bug fix.
746 <LI> Adjust wrapping of HTML messages so that the margins specified by
747 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
748 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>
749 are observed correctly
750 <LI> Interrupt of WhereIs command in index was broken
751 <LI> The <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
752 option did not work correctly interpreting unknown characters in message headers
753 <LI> Long address lines could cause blank continuation lines
754 <LI> Save to a local default INBOX failed if the primary collection was also local,
755 which it is by default. The save went to ~/mail/inbox instead.
756 <LI> Make a default save folder of "inbox" always mean the real
757 inbox, not the inbox in the primary collection
758 <LI> Address book entries with lots of addresses would be truncated when
759 entered in the composer with a screen size wider than 270 or so charcters
760 <LI> Some fields in the index screen were truncated when the screen width was
761 wider than 256 characters
762 <LI> Crash when TABing to next folder, the next folder with new mail is a POP
763 folder, and there is a more than 10 minute pause between typing the TAB
764 and typing the Yes
765 </UL>
767 <P>
768 Version 1.10(962)
769 addressed bugs found in previous releases and had a few additions as well.
770 <P>
771 Additions included:
772 <P>
774 <UL>
775 <LI> Add the possibility of setting a default role
776 (see <A HREF="h_role_select">Roles Screen</A>)
777 which may be convenient if your work flow involves acting in one
778 role for a while then switching to another role and staying in the
779 new role for another period of time
780 <LI> When Saving and the IMAP server problem "Message to save shrank!"
781 is encountered, ask the user if he or she wants to continue with the
782 risky Save anyway instead of aborting. This may be helpful if your
783 IMAP server is broken in this way but be aware that it is possible there
784 was a real error instead of just a broken server implementation.
785 <LI> Some configure adjustments for Kerberos detection and
786 for SCO OpenServer 5 support
787 <LI> Hide INBOX in a collection if it also appears as an
788 <A HREF="h_config_enable_incoming">Incoming Folder</A>
789 <LI> Show asterisks for feedback when the user is typing a password
790 <LI> Performance improvement for threading of large folders
791 <LI> Previously, the search used to find
792 Pattern matches containing To patterns searched for both To
793 and Resent-To headers. The relatively complicated search this
794 produces causes problems when using some deficient IMAP servers.
795 Now the default is to look only for To headers and ignore the
796 presence of Resent-To. The previous behavior may be restored
797 with the <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> feature.
798 <LI> Add an
799 <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
800 to help with reading malformed unlabeled messages
801 <LI><A HREF="h_config_suppress_user_agent"><!--#echo var="FEAT_suppress-user-agent-when-sending"--></A> option added
802 <LI> Map some Shift-LeftArrow escape sequences to LeftArrow
803 <LI> Add feature <A HREF="h_config_warn_if_fcc_blank"><!--#echo var="FEAT_warn-if-blank-fcc"--></A>
804 </UL>
806 <P>
807 Bugs addressed in the 1.10(962) release included:
808 <P>
810 <UL>
811 <LI> Crash when encountering certain errors from an SMTP server
812 <LI> Crash in composer caused by overflow in replace_pat()
813 <LI> Hang when authenticating to an SMTP server that fails with a
814 "connection disconnected" error
815 <LI> Bug in handling of trailing tab character in flowed text
816 <LI> Security enhancement for mailcap parameter substitution
817 <LI> <A HREF="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></A>
818 did not work if the message being replied to was not flowed text
819 and <A HREF="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></A>
820 was not turned on
821 <LI> Don't allow printer to be changed through hidden config screen
822 if system administrator didn't want it to be allowed
823 <LI> Attempts are sometimes made to set the Forwarded flag when alpine
824 should know that it won't work, causing error messages to appear
825 <LI> A <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
826 of double-quote double-quote didn't work right
827 <LI> Quoting wasn't being done to protect special characters from the
828 MacOS X shell when
829 <A HREF="h_config_browser"><!--#echo var="VAR_url-viewers"--></A>
830 was not defined
831 <LI> On MacOS X message attachments should be shown internally instead of
832 being shown using the Mail application
833 <LI> When replying to a message with a charset of X-UNKNOWN Alpine would
834 sometimes set the outgoing charset to X-UNKNOWN, making the result
835 unreadable
836 <LI> When the sending of a message failed lines with leading spaces had one
837 additional space inserted in each of those lines when the user
838 was returned to the composer
839 <LI> The <A HREF="h_index_cmd_whereis">WhereIs</A> command missed some index lines
840 that contained non-ascii characters because it was truncating the
841 line being searched so that it was shorter than what was visible on
842 the screen
843 <LI> When composing, an attachment with a long name that causes wrapping in
844 just the wrong place would generate an error and cause the send
845 of the attachment to fail
846 <LI> After calling the file browser to attach a file in the composer, a resize
847 of the window when back in the composer would redraw the last screen that
848 had been shown in the browser instead of the current composer screen
849 <LI> Possible crash in index screen when encountering unparseable addresses
850 or when using one of the PRIORITY tokens or the HEADER token in the
851 <a href="h_config_index_format"><!--#echo var="VAR_index-format"--></a>
852 <LI> Problems with Header Color editing if the configuration option
853 <a href="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></a>
854 was inadvertently changed to the Empty Value in the hidden config screen
855 <LI> When resuming the final postponed message from an Exchange server the user
856 could get a certificate validation failure because alpine was trying
857 to validate the canonical name of the folder instead of the name the
858 user used
859 <LI> Windows line endings in a mimetypes file on a Unix system cause a
860 failure to find a match
861 <LI> Make matching of extension names case independent in mimetypes files
862 <LI> Windows dialog boxes for entering text were not working correctly
863 <LI> Replying to or Forwarding multipart/alternative messages which had a
864 single text/html part did not work well
865 <LI> Printing the print confirmation page caused a crash
866 <LI> A To line with a long, quoted personal name could display incorrectly
867 if it was close to the same width as the screen
868 <LI> When <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
869 and <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
870 are turned on hide (0/0) when the folder is empty
871 <LI> Folder completion while Saving didn't work if the collection being
872 saved to was the local home directory
873 </UL>
875 <P>
876 Version 1.00
877 was an evolutionary release based on
878 <A HREF="http://www.washington.edu/pine/">Pine</A>, which was also
879 developed at the University of Washington.
880 It is upwards-compatible for existing Pine users.
882 <P>
883 Changes included:
884 <P>
885 <UL>
886 <LI> Ground-up reorganization of source code around addition
887 of "pith/" core routine library.
888 <LI> Fundamental improvement in Alpine's internal text handling, which
889 is now based exclusively on Unicode. This allows displaying incoming
890 messages and producing outgoing messages in many different languages.
891 <LI> Ground-up reorganization of build and install procedures
892 based on GNU Build System's autotools. NOTE, the included IMAP library
893 build is not based on autotools, so some features will not work. However,
894 it should get built automatically during the Alpine build process.
895 <LI> Web-based version included built on TCL designed to run under
896 a suitable CGI-supporting web server such as Apache.
897 </UL>
899 <P>
901 Details on changes in previous (prerelease) versions of Alpine
902 may be found at the following URL:
903 <P>
904 <CENTER><SAMP><A HREF="http://patches.freeiz.com/alpine/release/">http://patches.freeiz.com/alpine/release/</A></SAMP></CENTER>
905 <P>
907 <HR WIDTH="75%"><P>
909 <H2>Getting Help</H2>
910 <DL>
911 <DT>Online Help</DT>
912 <DD>
913 Every Alpine screen and command has associated help text
914 accessible via the "?" key (or Ctrl-G in text-input contexts).
915 </DD>
917 <DT>Web Help</DT>
918 <DD>
919 The most current source of information about Alpine,
920 including new version availability, is the web page at
921 <P>
922 <CENTER><SAMP><A HREF="http://patches.freeiz.com/alpine/">http://patches.freeiz.com/alpine/</A></SAMP></CENTER>
923 </DD>
924 </DL>
926 Frequently Asked Questions (and answers) may be found at the following
927 URL:
928 <P>
929 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/faq/">http://www.washington.edu/alpine/faq/</A></SAMP></CENTER>
930 <P>
932 <HR WIDTH="75%"><P>
934 <H2>Additional Information</H2>
936 General Alpine configuration information can be found
937 <A HREF="h_news_config">here</A>.
938 <P>
939 This is revision (<!--#echo var="ALPINE_REVISION"-->) of the Alpine software.
940 Alpine mailbox and <A HREF="https://github.com/jonabbey/panda-imap/">IMAP</A> server
941 access is provided by the IMAP Toolkit Environment (c-client library)
942 version <!--#echo var="C_CLIENT_VERSION"-->.
943 <P>
944 Alpine was developed until 2009 by the Office of Computing
945 & Communications at the University of Washington in Seattle.
946 Since then, the effort of developing Alpine has been continued by
947 a community of volunteers who make good software even better!
949 <P>
950 Alpine Copyright 2013-2015 Eduardo Chappa,
951 <BR> Copyright 2006-2008 University of Washington.
953 <P>
954 Additional legal notices can be found <A HREF="h_news_legal">here</A>,
955 or instead you can find the Apache License, version 2.0 at the web URL:
957 <P>
958 <CENTER><A HREF="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</A></CENTER>
960 <P>
961 <End of Release Notes>
962 </BODY>
963 </HTML>
964 ====== h_password_file_support ======
965 <HTML>
966 <HEAD>
967 <TITLE>Encryption for Password File Support Explained</TITLE>
968 </HEAD>
969 <BODY>
970 <H1>Encryption for Password File Support Explained</H1>
972 Index<BR>
973 <OL>
974 <LI><A HREF="#content">Explanation</A>
975 <LI><A HREF="#example">Example</A>
976 </OL>
978 <P><A NAME="content">Unix Alpine Only.</A>
980 <P> If your version of Alpine has been built with password file support
981 then you can use a special file to save your passwords, and avoid typing
982 them every time you open a connection to a remote server.
984 <P> If your version of Alpine was built with SMIME support, and you have a
985 public certificate/private key pair, then Alpine will use such pair to
986 encrypt your password file. If you have more than one key/certificate
987 pair, Alpine will pick the first pair that it finds that works. You can also
988 select a pair, and the way to do this is explained below.
990 <P> Once a pair has been chosen, it will be copied to the directory
991 ~/.alpine-smime/.pwd, and from then on, Alpine will use the pair found in
992 that directory. The first time this process is done, this directory will
993 be created, a key/certificate pair will be copied to it, and this pair
994 will be used in the future to encrypt and decrypt your password file. You
995 can create this directory and copy any key/certificate pair there. You
996 can add a self-signed certificate there, if you like, and you can let
997 this certificate expire. This will not affect the encryption and decryption
998 of the password file.
1000 <P> If you prefer not to use the directory ~/.alpine-smime/.pwd to save
1001 your key/certificate pair, you can specify a different one with the
1002 -pwdcertdir command line option in Alpine. If the directory specified by
1003 this option is not found or there is no valid key/certificate pair there,
1004 Alpine will fail to encrypt and decrypt your password file. In other words,
1005 Alpine will not initialize this directory for you.
1007 <P> Alpine does not care about the names of the key and certificates in
1008 this directory, but the private key must have ".key" extension
1009 and your public certificate must have the ".crt" extension. The
1010 name of the private key will be used in the prompt when you are asked
1011 to unlock your key to decrypt your password.
1013 <P><A NAME="example">An example follows</A>
1015 <P>Assume you have a private key called peter@address.com.key in your,
1016 ~/.alpine-smime/private directory, and a public certificate called
1017 peter@address.com.crt in your ~/.alpine-smime/public directory, and these
1018 are your only key/certificate pair.
1020 <P> When Alpine starts for the first time, without command line options,
1021 it will check if the directory ~/.alpine-smime/.pwd exists, and if not,
1022 it will create it. Then it will go through your keys and certificates and
1023 find a pair that it can use, and copy the files peter@address.com.key,
1024 and peter@address.com.crt to the ~/.alpine-smime/.pwd directory. Alternatively
1025 you can do the same by copying these files by yourself. This can be done
1026 with the sequence of commands
1028 <PRE>
1029 mkdir ~/.alpine-smime/.pwd
1030 cp ~/.alpine-smime/private/peter@address.com.key ~/.alpine-smime/.pwd
1031 cp ~/.alpine-smime/public/peter@address.com.crt ~/.alpine-smime/.pwd
1032 </PRE>
1034 <P> When Alpine starts, you will be asked the password to unlock your
1035 private key with the prompt.
1037 <PRE>
1038 Enter password of key <peter@address.com> to unlock password file:
1039 </PRE>
1041 <P> If you prefer to use different names for your private and public keys
1042 in the ~/.alpine-smime/.pwd directory, you can do so, but you must
1043 preserve the extension of the files. For example, you can use the names
1044 private_key.key and public_cert.crt instead. In this case, the prompt you
1045 will see when you are asked to unlock your private key will read
1047 <PRE>
1048 Enter password of key <private_key> to unlock password file:
1049 </PRE>
1051 <P>Observe that you do not need to use an existing key/certificate pair,
1052 and that you can create a new private key/public certificate pair to
1053 encrypt and decrypt your password. However, once one is used, Alpine does
1054 not provide a mechanism to switch the encryption and decryption files to
1055 another key/certificate pair. This will be implemented in a future
1056 release of Alpine.
1058 <P>
1059 <End of help>
1060 </BODY>
1061 </HTML>
1062 ====== h_tls_failure_details ======
1063 <HTML>
1064 <HEAD>
1065 <TITLE>Certificate Validation Details</TITLE>
1066 </HEAD>
1067 <BODY>
1068 <H1>Certificate Validation Details</H1>
1070 This screen gives details as to why the certificate validation failed: the
1071 name of the desired server system; the reason for failure; and the name on
1072 the certificate. This is primarily of interest to experts.
1074 <P>
1075 <End of help>
1076 </BODY>
1077 </HTML>
1078 ====== h_tls_failure ======
1079 <HTML>
1080 <HEAD>
1081 <TITLE>TLS or SSL Failure</TITLE>
1082 </HEAD>
1083 <BODY>
1084 <H1>TLS or SSL Failure</H1>
1086 An attempt was made to establish a secure, encrypted connection to the
1087 server system using either Transport Layer Security (TLS) or the older
1088 Secure Sockets Layer (SSL). This attempt failed.
1090 <P>
1091 You should contact your server system management for more assistance.
1092 The problem is probably at the server system and not in Alpine or your local
1093 system. The text in this screen may be helpful for the server system
1094 management in debugging the problem,
1096 <P>
1097 <End of help>
1098 </BODY>
1099 </HTML>
1100 ====== h_tls_validation_failure ======
1101 <HTML>
1102 <HEAD>
1103 <TITLE>TLS and SSL Certificate Validation Failures</TITLE>
1104 </HEAD>
1105 <BODY>
1106 <H1>TLS and SSL Certificate Validation Failures</H1>
1108 An attempt was made to establish a secure, encrypted connection to the
1109 server system using either Transport Layer Security (TLS) or the older
1110 Secure Sockets Layer (SSL).
1112 <P>
1113 An important part of this procedure is server certificate validation. A
1114 server certificate is an "electronic identification card" for the server
1115 system that is signed by a well-known certificate authority (CA). Alpine
1116 compares the server system identity in the server certificate with the
1117 name of the server system to which it is trying to connect. Alpine also
1118 verifies that the CA signature is authentic.
1120 <P>
1121 Some common failure conditions are:
1122 <P>
1124 <UL>
1125 <LI> [UNIX Alpine] Self signed certificate. This means that the server system
1126 signed its own certificate. This does not necessarily indicate anything
1127 bad; the server operators may simply have elected to not purchase a
1128 signed certificate from a certificate authority.
1130 <LI> [UNIX Alpine] Unable to get local issuer certificate. This means that
1131 the signature on the server system is from an unknown certificate authority.
1132 It can also mean that no certificate authority certificates have been
1133 installed on the local UNIX system.
1135 <LI> [PC Alpine] Self-signed certificate or untrusted authority. This is
1136 the same as either of the above two conditions in UNIX Alpine. Note that
1137 Windows systems typically have a full set of certificate authority
1138 certificates installed, so it is more likely to be a self-signed
1139 certificate than an unknown certificate authority.
1141 <LI> Server name does not match certificate. This means that the server
1142 presented a proper signed certificate for a name other than the desired
1143 name.
1144 </UL>
1146 <P>
1147 Any of these conditions can indicate that you are being attacked and have
1148 been directed to an imposter server that will record your password and
1149 your private mail messages. It can also mean something innocuous.
1151 <P>
1152 If you are certain that the problem is innocuous, you can append the
1153 option
1155 <P>
1156 <CENTER><SAMP>/novalidate-cert</SAMP></CENTER>
1157 <P>
1159 to the server system name where it appears in your configuration (e.g. the
1160 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>,
1161 a folder-collection, or a news or SMTP server). This will
1162 disable certificate validation. On the other hand, if you are attacked,
1163 you will get no warning if you do this.
1165 <P>
1166 <End of Cert Validation Failures help>
1167 </BODY>
1168 </HTML>
1169 ====== h_release_tlscerts ======
1170 <HTML>
1171 <HEAD>
1172 <TITLE>TLS and SSL usage note</TITLE>
1173 </HEAD>
1174 <BODY>
1175 <H1>TLS and SSL usage note</H1>
1177 <P>
1178 When using Alpine from Unix or Windows 2000,
1179 server certificates must be signed by a trusted certificate authority.
1180 You may relax this requirement (at the cost of some security) by using
1181 the
1182 <A HREF="h_folder_server_syntax">NoValidate-Cert</A>
1183 modifier in the mailbox name.
1185 <P>
1186 <CENTER><SAMP>{foo.example.com/novalidate-cert}INBOX</SAMP></CENTER>
1187 <P>
1189 The fully-qualified host name of the server should be used
1190 so that it matches the host name in the server certificate.
1191 <P>
1192 Here is an example of a host specification that directs Alpine to use
1193 the SSL port (993) and an encrypted data stream.
1194 <P>
1195 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
1196 <P>
1197 <End of TLS usage help>
1198 </BODY>
1199 </HTML>
1200 ====== h_news_config ======
1201 <HTML>
1202 <HEAD>
1203 <TITLE>Alpine Configuration</TITLE>
1204 </HEAD>
1205 <BODY>
1206 <H1>Alpine Configuration</H1>
1208 <H2>Using Environment Variables</H2>
1210 The values of Alpine configuration options may include environment variables
1211 that are replaced by the value of the variable at the time Alpine is run
1212 (and also at the time the config option is changed).
1213 The syntax to use environment variables is a subset of the common Unix
1214 shell dollar-syntax.
1215 For example, if
1217 <P><CENTER><SAMP>$VAR</SAMP></CENTER><P>
1219 appears in the value of an Alpine configuration option it is looked up in the
1220 environent (using getenv("VAR")) and its
1221 looked-up value replaces the <SAMP>$VAR</SAMP> part of the option value.
1222 To include a literal dollar sign you may precede the dollar sign with another
1223 dollar sign.
1224 In other words, if the text
1226 <P><CENTER><SAMP>$$text</SAMP></CENTER><P>
1228 is the value of a configuration option, it will be expanded to
1230 <P><CENTER><SAMP>$text</SAMP></CENTER><P>
1232 and no environment lookup will be done.
1233 For Unix Alpine it will also work to use a backslash character to
1234 escape the special meaning of the dollar sign, but $$ is preferable since
1235 it works for both PC-Alpine and Unix Alpine, allowing the configuration option
1236 to be in a shared configuration file.
1237 <P>
1239 This all sounds more complicated than it actually is.
1240 An example may make it clearer.
1241 Unfortunately, the way in which environment variables are set is OS-dependent
1242 and command shell-dependent.
1243 In some Unix command shells you may use
1245 <P><CENTER><SAMP>PERSNAME="Fred Flintstone"</SAMP></CENTER><P>
1246 <CENTER><SAMP>export PERSNAME</SAMP></CENTER><P>
1248 Now, if you use Alpine's Setup/Config screen to set
1250 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=$PERSNAME</SAMP></CENTER><P>
1252 the <SAMP>$PERSNAME</SAMP> would be replaced by <SAMP>Fred Flintstone</SAMP>
1253 so that this would be equivalent to
1255 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=Fred Flintstone</SAMP></CENTER><P>
1257 Note, environment variable substitution happens after configuration
1258 options that are lists are split into the separate elements of the list,
1259 so a single environment variable can't contain a list of values.
1261 <P>
1262 The environment variable doesn't have to be the only thing
1263 after the equal sign.
1264 However, if the name of the variable is not at the end of the line or
1265 followed by a space (so that you can tell where the variable name ends),
1266 it must be enclosed in curly braces like
1268 <P><CENTER><SAMP>${VAR}</SAMP></CENTER><P>
1270 It is always ok to use the braces even if you don't need to.
1271 <P>
1272 It is also possible to set a default value for an environment variable.
1273 This default value will be used if the environment variable is not
1274 set (that is, if getenv("VAR") returns NULL).
1275 The syntax used to set a default value is
1277 <P><CENTER><SAMP>${VAR:-default value}</SAMP></CENTER><P>
1279 If the config file contains
1281 <P><CENTER><SAMP>personal-name=${VAR:-Fred Flintstone}</SAMP></CENTER><P>
1283 then when Alpine is run <SAMP>VAR</SAMP> will be looked up in the environment.
1284 If <SAMP>VAR</SAMP> is found then <SAMP>personal-name</SAMP> will have
1285 the value that <SAMP>VAR</SAMP> was set to, otherwise,
1286 <SAMP>personal-name</SAMP> will be set to <SAMP>Fred Flintstone</SAMP>,
1287 the default value.
1288 (Note that the variable is called "personal-name" in the config
1289 file but is displayed in the config screen as
1290 "<!--#echo var="VAR_personal-name"-->".
1291 In general, the value that goes into a config file is never exactly the
1292 same as the value you see on the screen.)
1294 <P>
1295 An example where an environment variable might be useful is the
1296 variable <SAMP>Inbox-Path</SAMP> in the global configuration file.
1297 Suppose most users used the server
1299 <P><CENTER><SAMP>imapserver.example.com</SAMP></CENTER><P>
1301 but that there were some exceptions who used
1303 <P><CENTER><SAMP>altimapserver.example.com</SAMP></CENTER><P>
1305 In this case, the system manager might include the following line in
1306 the systemwide default Alpine configuration file
1308 <P><CENTER><SAMP>Inbox-Path=${IMAPSERVER:-imapserver.example.com}</SAMP></CENTER><P>
1310 For the exceptional users adding
1312 <P><CENTER><SAMP>IMAPSERVER=altimapserver.example.com</SAMP></CENTER><P>
1314 to their environment should work.
1315 <P>
1316 Another example might be the case where a user has to use a different
1317 SMTP server from work and from home.
1318 The setup might be something as simple as
1320 <P><CENTER><SAMP>smtp-server=$SMTP</SAMP></CENTER><P>
1322 or perhaps a default value could be given.
1323 Note that, as mentioned above, the variable <SAMP>SMTP</SAMP> cannot contain
1324 a list of SMTP servers.
1325 <P>
1327 <H2>Configuration precedence</H2>
1329 There are several levels of Alpine configuration. Configuration values at
1330 a given level override corresponding values at lower levels. In order of
1331 increasing precedence:
1332 <P>
1333 <UL>
1334 <LI> built-in defaults
1335 <LI> system-wide
1336 <!--chtml if pinemode="os_windows"-->
1337 config file from command line or provided
1338 by "PINECONF" environment variable
1339 <!--chtml else-->
1340 pine.conf file
1341 <!--chtml endif-->
1342 <LI> personal configuration file
1343 <LI> personal exceptions configuration file
1344 <LI> command-line options
1345 <!--chtml if pinemode="os_windows"--><!--chtml else-->
1346 <LI> system-wide pine.conf.fixed file<!--chtml endif-->
1347 </UL>
1348 <P>
1349 The values in both the personal configuration file and the
1350 <A HREF="h_config_exceptions">exceptions</A>
1351 configuration file may be set using the Setup command.
1352 Setup/Config is the command to change most of the personal configuration
1353 options.
1354 The other Setup subcommands are also used to change the configuration,
1355 for example, Setup/AddressBook, Setup/Rules, and so on.
1356 Changing the personal exceptions configuration is very similar.
1357 To change a value in the Config screen you would use the command
1358 Setup/eXceptions/Config.
1359 Likewise for the other Setup subcommands (Setup/eXceptions/Rules and so on).
1360 <P>
1361 There are a couple exceptions to the rule that configuration values are replaced
1362 by the value of the same option in a higher-precedence file.
1363 The Feature-List variable has values that are additive, but can be
1364 negated by prepending "no-" in front of an individual feature name.
1365 So for features, each individual feature's value is replaced by the value
1366 of the same feature in a higher-precedence file.
1367 Note that this is done automatically for you when you change these values via
1368 the Setup/Config command.
1369 The other exception to the <EM>replace</EM> semantics happens when you
1370 use <A HREF="h_config_inheritance">configuration inheritance</A>
1371 for option lists.
1372 <P>
1374 <H2>File name defaults</H2>
1376 Notes:<P>
1378 <BR> <exe dir> = directory where pine.exe found.
1379 <BR> <pinerc dir> = directory where pinerc found.
1380 <BR> # = default file name is overridable in pinerc.
1381 <BR> $HOME, if not explicitly set, defaults to root of the current drive.
1382 <BR> $MAILCAPS, if set, is used in lieu of the default mailcap search paths.
1383 <BR> + between the mailcap paths implies that the two files are combined.
1384 <BR> ; between other default paths implies that the first one found is used.
1385 </P>
1386 Alpine looks for most support files in the same directory it finds its
1387 personal configuration file (pinerc). The -p command-line flag may be
1388 used to specify a particular path name for the pinerc file. If a
1389 pinerc file does not exist, it will be created (if directory permissions
1390 allow). In PC-Alpine, if -p or $PINERC are not defined, Alpine will look
1391 in $HOME\PINE and the directory containing the PINE.EXE. If a PINERC
1392 file does not exist in either one, it will create one in the first of those
1393 two directories that is writable. In detail:
1394 <PRE>
1396 PC-Alpine:
1398 executable <DOS search path>\pine.exe
1399 help index <exe dir>\pine.ndx
1400 help text <exe dir>\pine.hlp
1402 pers config $PINERC ; $HOME\pine\PINERC ; <exe dir>\PINERC
1403 except config $PINERCEX ; $HOME\pine\PINERCEX ; <exe dir>\PINERCEX
1404 global cfg $PINECONF
1406 debug <pinerc dir>\pinedebg.txtN
1407 crash <pinerc dir>\pinecrsh.txt
1408 signature# <pinerc dir>\pine.sig
1409 addressbook# <pinerc dir>\addrbook
1410 mailcap# <pinerc dir>\mailcap + <exe dir>\mailcap
1411 mimetypes# <pinerc dir>\mimetype + <exe dir>\mimetype
1412 newsrc# $HOME\newsrc (if exists, else) <pinerc dir>\newsrc
1413 sentmail# $HOME\mail\sentmail.mtx
1414 postponed# $HOME\mail\postpond.mtx
1415 interrupted $HOME\mail\intruptd
1417 Unix Alpine:
1419 executable <Unix search path>/pine
1420 persnl cfg ~/.pinerc
1421 except cfg ~/.pinercex
1422 global cfg <!--#echo var="PINE_CONF_PATH"-->
1423 fixed cfg <!--#echo var="PINE_CONF_FIXED_PATH"-->
1424 local help <!--#echo var="PINE_INFO_PATH"-->
1426 interrupted ~/.pine-interrupted-mail
1427 debug ~/.pine-debugN
1428 crash ~/.pine-crash
1429 newsrc# ~/.newsrc
1430 signature# <pinerc dir>/.signature
1431 addressbook# <pinerc dir>/.addressbook
1432 postponed# ~/mail/postponed-msgs
1433 sentmail# ~/mail/sent-mail
1434 mailcap# ~/.mailcap + /etc/mailcap
1435 + /usr/etc/mailcap + /usr/local/etc/mailcap
1436 mimetypes# ~/.mime.types + /etc/mime.types + /usr/local/lib/mime.types
1438 news-spool varies across Unix flavors, e.g. /var/spool/news or /usr/spool/news
1439 active-news varies across Unix flavors, e.g. /usr/lib/news/active
1440 lock files /tmp/.<!--#echo var="MAIL_SPOOL_LOCK_PATH"-->
1441 inbox <!--#echo var="MAIL_SPOOL_PATH"-->
1442 password /etc/passwd
1444 Unix Alpine and PC-Alpine:
1446 .ab* remote addressbook support files
1447 a[1-9]* temporary (while Alpine is running) addressbook files
1449 </PRE>
1450 <P>
1452 <H2>Mailcap files</H2>
1454 Alpine honors the mailcap configuration system for specifying external
1455 programs for handling attachments. The mailcap file maps MIME attachment
1456 types to the external programs loaded on your system that can display
1457 and/or print the file. A sample mailcap file comes bundled with the Alpine
1458 distribution. It includes comments that explain the syntax you need to
1459 use for mailcap. With the mailcap file, any program (mail readers,
1460 newsreaders, WWW clients) can use the same configuration for handling
1461 MIME-encoded data.
1462 <P>
1464 <H2>MIME-Types files</H2>
1466 Alpine uses mime-types files (.mime.types or MIMETYPE) to determine
1467 what Content-Type to use for labeling an attached file, based on
1468 the file extension. That is, this file provides a mapping between
1469 filename extensions and MIME content-types.
1470 <P>
1472 <H2>Environment variables</H2>
1474 PC-Alpine uses the following environment variables:
1475 <DL>
1476 <DT>PINERC</DT>
1477 <DD>Optional path to pinerc file.</DD>
1478 <DT>PINERCEX</DT>
1479 <DD>Optional path to personal exceptions configuration file.</DD>
1480 <DT>PINECONF</DT>
1481 <DD>Optional path to global pine config file.</DD>
1482 <DT>HOME</DT>
1483 <DT>TMPDIR, TMP, or TEMP</DT>
1484 <DT>COMSPEC</DT>
1485 <DT>MAILCAPS</DT>
1486 <DD>A <B>semicolon</B> delimited list of path names to mailcap files.</DD>
1487 <DT>USER_DICTIONARY</DT>
1488 <DD>Used to specify the file to contain the user's spell check
1489 dictionary. The default is <SAMP>DICT.U</SAMP> in the same
1490 directory as the <SAMP>SPELL32.DLL</SAMP></DD>
1491 </DL>
1493 Unix Alpine uses the following environment variables:
1494 <DL>
1495 <DT>TERM</DT>
1496 <DD>Tells Alpine what kind of terminal is being used.</DD>
1497 <DT>DISPLAY</DT>
1498 <DD>Determines if Alpine will try to display IMAGE attachments.</DD>
1499 <DT>SHELL</DT>
1500 <DD>If not set, default is "/bin/sh".</DD>
1501 <DT>TMPDIR, TMP, or TEMP</DT>
1502 <DT>MAILCAPS</DT>
1503 <DD>A <B>colon</B> delimited list of path names to mailcap files.</DD>
1504 </DL>
1505 <!--chtml if pinemode="os_windows"-->
1506 <P>
1507 <H2>Common PC-Alpine Configuration Problems</H2>
1509 <H3>Configuration settings aren't being saved</H3>
1511 <P>This problem can happen if you run pine from one directory and
1512 then decide to move your pine directory to another location. PC-Alpine
1513 stores certain variables, including the configuration location, in the
1514 Windows Registry (which you shouldn't ever need to manually edit). There
1515 are a couple of ways to go about removing or resetting the values in the
1516 registry.
1518 <P>
1519 1) Run PC-Alpine's registry value deletion command. This can be done by
1520 running: "<your pine directory>\pine.exe -registry clear" from the DOS
1521 prompt. You could create a shortcut to pine.exe and change the "Target"
1522 value to the above command.
1524 <P>
1525 2) Tell PC-Alpine where to look for the configuration file. Configuration
1526 information is stored in a file called the PINERC. With the "-p PINERC"
1527 option, you can tell PC-Alpine the location of your pinerc. An example of
1528 this would be to run: "<your pine directory>\pine.exe -p C:\pine\mypinerc".
1529 Again, you can use the DOS prompt or the shortcut method explained in (1).
1531 <P>
1532 Additionally, there is the "-registry set" option, which will actively
1533 set registry values to the current setting, and is therefore useful with
1534 the "-p PINERC" option.
1536 <!--chtml endif-->
1537 <P>
1538 <End of Configuration Notes>
1539 </BODY>
1540 </HTML>
1541 ====== h_news_legal ======
1542 <html>
1543 <head>
1544 <TITLE>Alpine Legal Notices</TITLE>
1545 </head>
1546 <body>
1548 <H1>Alpine Legal Notices</H1>
1550 Alpine and its constituent programs are covered by the Apache License Version 2.0.
1553 <P>
1554 <End of Alpine Legal Notices>
1555 </BODY>
1556 </HTML>
1557 ===== h_info_on_mbox =====
1558 <HTML>
1559 <HEAD>
1560 <TITLE>Information on mbox driver</TITLE>
1561 </HEAD>
1562 <BODY>
1563 <H1>Information on "Missing Mail" and the "mbox" driver</H1>
1565 Beginning with Pine 4.00 (Pine came before Alpine)
1566 a new INBOX access method is
1567 available as part of the standard configuration. It is called the
1568 "mbox" driver and it works like this:<P>
1570 <P>
1571 <BLOCKQUOTE>
1572 If the file "mbox" exists in the user's home directory, and
1573 is in Unix mailbox format, then when INBOX is opened this file will be
1574 selected as INBOX instead of the mail spool file. Messages will be
1575 automatically transferred from the mail spool file into the mbox
1576 file.
1577 </BLOCKQUOTE>
1579 <P>
1580 The advantage of this method is that, after new mail has been copied
1581 from the system mail spool, all subsequent access is confined to the
1582 user's home directory, which is desirable on some systems. However, a
1583 possible disadvantage is that mail tools other than those from the
1584 University of Washington will not know to look for mail in the user's
1585 mbox file. For example, POP or IMAP servers other than those from the
1586 University of Washington, and many "new mail notification"
1587 programs may not work as expected with this driver enabled.<P>
1589 To disable this behavior, either remove/rename the "mbox"
1590 file or find the <A HREF="h_config_disable_drivers"><!--#echo var="VAR_disable-these-drivers"--></A>
1591 option in Setup/Config
1592 and add "mbox" to it:
1593 <P>
1594 <CENTER><SAMP><!--#echo var="VAR_disable-these-drivers"-->=mbox</SAMP></CENTER>
1595 <P>
1596 <End of help on this topic>
1597 </BODY>
1598 </HTML>
1599 ===== h_info_on_locking =====
1600 <HTML>
1601 <HEAD>
1602 <TITLE>FAQs on Alpine Locking</TITLE>
1603 </HEAD>
1604 <BODY>
1605 <H1>What Systems Managers Need to Know about Alpine File Locking</H1>
1607 There is an extensive section on locking in the Alpine technical notes;
1608 this information is intended to provide answers to some common questions:<P>
1609 <OL>
1610 <LI> Why did locking change in Pine 4.00?<BR>
1611 The actual locking mechanisms did not change in 4.00.
1612 What changed is that when one particular locking mechanism used by Alpine
1613 fails, Alpine now issues a warning message. Prior to Pine 4.00, the locking
1614 failure would occur, but no warning was issued.<P>
1616 <LI> Is this what the "Mailbox vulnerable" message is about?<BR>
1617 Yes. It means that Alpine was unable to create a lockfile in the
1618 spool directory, generally because of overly restrictive protections on the
1619 spool directory. The correct permissions on the spool directory for
1620 running Alpine are 1777, i.e. read-write-execute permission for everyone,
1621 with the sticky-bit set, so only owners of a file can delete them.<P>
1623 <LI> Why does Alpine require that the mail spool directory have 1777
1624 protections?<BR>
1625 Alpine was designed to run without special privileges. This means that in
1626 order to create a lockfile in the spool directory, it is necessary to have
1627 the spool directory permissions be world-writable.<P>
1629 <LI> Can't you create the lockfile somewhere else?<BR>
1630 No. The lockfile in question must be in the mail spool directory, because
1631 that's where the mail delivery program expects to find it, and the purpose
1632 of the file is to coordinate access between the mail client (Alpine) and the
1633 mail delivery program.<P>
1635 <LI> Isn't having the spool directory world-writable a big security risk?<BR>
1636 No. Remember that the individual mail files in the spool directory are
1637 NOT world-writable, only the containing directory. Setting the "sticky
1638 bit" -- indicated by the "1" before the "777" mode
1639 -- means that only the owner of the file (or root) can delete files in the
1640 directory. So the only bad behavior that is invited by the 1777 mode is that
1641 anyone could
1642 create a random file in the spool directory. If the spool directory is
1643 under quota control along with home directories, there is little incentive
1644 for anyone to do this, and even without quotas a periodic scan for
1645 non-mail files usually takes care of the problem. <P>
1647 <LI> Why not run Alpine as setgid mail?<BR>
1648 Alpine was never designed to run with privileges, and to do so introduces a
1649 significant security vulnerability. For example, if a user suspends Alpine,
1650 the resulting shell will have group privileges. This is one example of
1651 why we strongly recommend against running Alpine as a privileged program.
1652 In addition, a "privileged mailer " paradigm would mean that normal
1653 users
1654 could not test Alpine versions or other mailers that had not been installed
1655 by the system administrators.<P>
1658 <LI> Are there any alternatives to creating .lock files in the spool dir?<BR>
1659 There are, but they all have different sets of tradeoffs, and not all will
1660 work on all systems. Some examples:<UL>
1661 <LI> Use lock system calls. Works fine on a few systems, provided mail
1662 spool is local. Doesn't work reliably if NFS is used.
1663 Doesn't work unless <B>all</B> the mail programs accessing the spool dir
1664 use the same calls.
1665 <LI> Deliver mail to user's home directory. An excellent solution, highly
1666 recommended -- but one which is incompatible with some "legacy"
1667 mail tools that always look in the spool directory for the mail.
1668 </UL><P>
1670 <LI> Are these spool directory lock files the only kinds of locks used by
1671 Alpine?<BR>
1672 No. Alpine also creates lockfiles in the /tmp directory. For normal Unix
1673 mailbox format folders, these are used to coordinate access between
1674 multiple Alpine sessions. <P>
1676 <LI> What about the
1677 <A HREF="h_config_quell_lock_failure_warnings">"<!--#echo var="FEAT_quell-lock-failure-warnings"-->"</A> feature added in Pine 4.01?<BR>
1678 This is for people who are content to live dangerously, or who have
1679 specific knowledge that the spool directory lockfiles are superfluous on
1680 their system (because both Alpine and the mail delivery program are using
1681 system call file locking in a context that works reliably, e.g. not NFS.)<P>
1683 <LI> Where can I find more details on how Alpine locking works?<BR>
1684 See the Alpine Technical Notes.<P>
1686 </OL>
1687 <P>
1688 <End of help on this topic>
1689 </BODY>
1690 </HTML>
1691 ===== h_finding_help ====
1692 <HTML>
1693 <HEAD>
1694 <TITLE>Finding more information and requesting help</TITLE>
1695 </HEAD>
1696 <BODY>
1697 <H1>Places to Look for More Answers</H1>
1698 If you have questions about or problems with Alpine that you cannot resolve
1699 after consulting the program's internal, context-sensitive help screens, here
1700 are additional information resources that you may find helpful:
1701 <P>
1702 <UL>
1703 <LI> Alpine's top-level <A HREF="main_menu_tx">MAIN MENU HELP</A>.<P>
1705 <LI> Alpine's <A HREF="h_help_index">Help Index</A>.<P>
1707 <LI> Alpine's internal <A HREF="h_news">Release Notes</A>. They contain a
1708 listing of changes in Alpine <!--#echo var="ALPINE_VERSION"-->
1709 since the last version, which may be useful for you to be aware of,
1710 <B>especially</B> if a "problem" you are encountering is actually
1711 a change in the way an aspect of Alpine works. There, you will also find notes
1712 on Alpine configuration.<P>
1714 <LI> The main site for Alpine contains information on configuring and solving problems
1715 with Alpine, it can be found at
1717 <CENTER><A HREF="http://patches.freeiz.com/alpine/">http://patches.freeiz.com/alpine/</A></CENTER>
1719 <LI> The Alpine Information Center (maintained by the University of
1720 Washington) World Wide Web site contains, among other things
1721 <UL>
1722 <LI>a collection of Frequently Asked Questions (and answers!) about Alpine
1723 <LI>an overview of the basics for beginning Alpine users
1724 <LI>Technical Notes for systems administrators
1725 <LI>archives (including a searchable index) of the alpine-info
1726 mailing list, on which matters of interest to systems/email administrators,
1727 developers, trainers, user support personnel, and others involved with Alpine
1728 messaging on a "technical" level are discussed.
1729 </UL>
1730 The Alpine Information Center can be accessed with a WWW browser at:<P>
1731 <CENTER><A HREF="http://www.washington.edu/alpine/">http://www.washington.edu/alpine/</A></CENTER>
1732 </UL>
1733 <P><HR WIDTH="75%">
1734 <H1>Requesting help</H1>
1735 If the internal help, the Release Notes, the Alpine Information Center, and your
1736 local online and print resources do not help you resolve a problem, please
1737 start by contacting your local computer support staff and asking for help.
1738 <p>
1739 This is especially true if:
1740 <ul>
1741 <li>You suddenly have trouble sending or receiving mail.
1742 <li>You receive a "disk quota exceeded" message.
1743 <li>You have forgotten your password.
1744 <li>You think your account may have been compromised.
1745 <li>You need help viewing an attachment.
1746 <li>You need to know how to configure your:
1747 <A HREF="h_config_nntp_server">NNTP (news) server</A>,
1748 <A HREF="h_config_smtp_server">SMTP (sending mail) server</A>,
1749 <A HREF="h_config_ldap_server">LDAP (directory lookup) server</A>, or
1750 <A HREF="h_config_inbox_path">INBOX (incoming mail) path</A>.
1751 <li>You want to know what alternative editors or spellcheckers you may be able to use.
1752 <li>You want to block email from a particular person.
1753 <li>You're going on vacation and need to autorespond to incoming mail.
1754 <li>You want to automatically file or filter incoming messages.
1755 </ul>
1757 In all of these cases,
1758 you should contact <B>your</B> support staff, because <B>only they</B>
1759 will be able to assist you effectively. Your support staff may be, depending on who
1760 provides you with the email account you use Alpine with, for example:<UL>
1761 <LI> the computing help desk of (a department of) your university, school,
1762 employer, ... ; or
1763 <LI> the customer service center of your Internet Service Provider; or
1764 <LI> the friendly volunteer helpers of your Freenet; or
1765 <LI> the person who setup your computer and internet connection.
1766 </UL>
1768 Due to the large number of Alpine installations worldwide, and because we
1769 receive no funding for it, the University of Washington <B>cannot provide
1770 individual support services outside the University of Washington</B>.
1771 <P>
1772 If you have no local computing support to turn to, the worldwide <b>comp.mail.pine</b>
1773 newsgroup can be a valuable source of information and assistance for Alpine
1774 user issues.
1775 <P>
1776 For systems/email administrators, developers, trainers, user support
1777 personnel, and others involved with Alpine messaging on a "technical"
1778 level, the mailing list alpine-info is available; for information on
1779 subscribing and posting to it, see
1780 <P>
1781 <CENTER><A HREF="http://www.washington.edu/alpine/alpine-info/subscribing.html">http://www.washington.edu/alpine/alpine-info/subscribing.html</A></CENTER>
1782 <P>
1784 Regardless of whom you are asking for help with Alpine, remember
1785 to provide as much detail as you can about the
1786 nature of any problem you are encountering, such as
1787 <UL>
1788 <LI>when it first occurred;
1789 <LI>what, if anything, happened that might have brought it about;
1790 <LI>whether it still persists;
1791 <LI>whether it is reproducible, and if so, how;
1792 <LI>what, if anything, you already tried to solve it.
1793 </UL>
1794 It may also be helpful if you specify what version of Alpine you are using
1795 <!--chtml if pinemode="running"-->
1796 -- this is <!--#echo var="ALPINE_VERSION"--> --
1797 <!--chtml endif-->
1798 and on what system, and when the copy of Alpine you are using was created
1799 <!--chtml if pinemode="running"-->
1800 -- for this copy: <!--#echo var=ALPINE_COMPILE_DATE-->
1801 <!--chtml endif-->
1803 <!--chtml if pinemode="running"-->
1804 <P>
1805 When the Alpine program you are currently using was installed, a support
1806 contact email address may have been set up; in that case, you can simply select
1807 this link now to send a message to it:<BR>
1808 <A HREF="X-Alpine-Gripe:_LOCAL_ADDRESS_?local"><!--#echo var="_LOCAL_FULLNAME_"--></A><P>
1809 <!--chtml endif-->
1810 <!--chtml if [ -r PINE_INFO_PATH ]-->
1811 <HR WIDTH="75%">Local Support Contacts:<P>
1812 <!--#include file="PINE_INFO_PATH"-->
1813 <HR WIDTH="75%">
1814 <!--chtml endif-->
1815 <P>
1816 <End of help on this topic>
1817 </BODY>
1818 </HTML>
1819 ===== new_user_greeting ======
1820 <HTML>
1821 <HEAD>
1822 <TITLE>NEW USER GREETING</TITLE>
1823 </HEAD>
1824 <BODY>
1825 <CENTER><<<This message will appear only once>>></CENTER>
1826 <BR>
1827 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
1828 We hope you will explore Alpine's many capabilities. From the MAIN MENU,
1829 select Setup/Config to see many of the options available to you. Also note
1830 that all screens have context-sensitive help text available.<P>
1831 <!--chtml if pinemode="phone_home"-->
1832 SPECIAL REQUEST:
1833 This software was originally created and maintained as a public
1834 service by the University of Washington until 2009; updates are made
1835 available as a public service of the Alpine community. It is always
1836 helpful to have an idea of how many users are using Alpine. Are you
1837 willing to be counted as an Alpine user? Pressing
1838 <A HREF="X-Alpine-Phone-Home:">Return</A>
1839 will send an anonymous (meaning, your real email address will not be revealed)
1840 message to the Alpine developers for purposes of tallying.
1841 <P>
1842 <!--To Exit this screen and continue your Alpine session press "E".-->
1843 <!--chtml else-->
1844 To Exit this screen and continue your Alpine session press "Return".
1845 <!--chtml endif-->
1846 </BODY>
1847 </HTML>
1848 ===== new_alpine_user_greeting ======
1849 <HTML>
1850 <HEAD>
1851 <TITLE>NEW ALPINE USER GREETING</TITLE>
1852 </HEAD>
1853 <BODY>
1854 <CENTER><<<This message will appear only once>>></CENTER>
1855 <BR>
1856 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
1857 Your Alpine configuration file indicates that you may have used Pine before
1858 but not Alpine.
1859 If you are familiar with the way Pine works, you should be comfortable
1860 using Alpine.
1861 Your Pine configuration file is automatically used for Alpine.
1862 The Release Notes may be viewed by pressing
1863 "R" now or while in the MAIN MENU.
1864 <P>
1865 <!--chtml if pinemode="phone_home"-->
1866 SPECIAL REQUEST:
1867 This software was originally created and maintained as a public
1868 service by the University of Washington until 2009; updates are made
1869 available as a public service of the Alpine community. It is always
1870 helpful to have an idea of how many users are using Alpine. Are you
1871 willing to be counted as an Alpine user? Pressing
1872 <A HREF="X-Alpine-Phone-Home:">Return</A>
1873 will send an anonymous (meaning, your real email address will not be revealed)
1874 message to the Alpine developers for purposes of tallying.
1875 <P>
1876 <!--To Exit this screen and continue your Alpine session press "E".-->
1877 <!--chtml else-->
1878 To Exit this screen and continue your Alpine session press "Return".
1879 <!--chtml endif-->
1880 </BODY>
1881 </HTML>
1882 ===== new_version_greeting ======
1883 <HTML>
1884 <HEAD>
1885 <TITLE>NEW VERSION GREETING</TITLE>
1886 </HEAD>
1887 <BODY>
1888 <CENTER><<<This message will appear only once>>></CENTER>
1889 <BR>
1890 <H1>Welcome to Alpine version <!--#echo var="ALPINE_VERSION"-->!</H1>
1891 Your Alpine configuration file indicates that you may not have used
1892 this version of Alpine before. This version's significant changes are
1893 documented in the Release Notes, which may be viewed by pressing
1894 "R" now or while in the MAIN MENU.
1895 <P>
1896 <!--chtml if pinemode="phone_home"-->
1897 SPECIAL REQUEST:
1898 This software was originally created and maintained as a public
1899 service by the University of Washington until 2009; updates are made
1900 available as a public service of the Alpine community. It is always
1901 helpful to have an idea of how many users are using Alpine. Are you
1902 willing to be counted as an Alpine user? Pressing
1903 <A HREF="X-Alpine-Phone-Home:">Return</A>
1904 will send an anonymous (meaning, your real email address will not be revealed)
1905 message to the Alpine developers for purposes of tallying.
1906 <P>
1907 <!--To Exit this screen and continue your Alpine session press "E".-->
1908 <!--chtml else-->
1909 To Exit this screen and continue your Alpine session press "Return".
1910 <!--chtml endif-->
1911 </BODY>
1912 </HTML>
1914 ===== main_menu_tx ======
1915 <HTML>
1916 <HEAD>
1917 <TITLE>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</TITLE>
1918 </HEAD>
1919 <BODY>
1920 <H1>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</H1>
1921 <DIV ALIGN=CENTER>
1922 Version <!--#echo var="ALPINE_VERSION"-->
1923 <!--chtml if pinemode="running"-->
1924 <BR>(built <!--#echo var=ALPINE_COMPILE_DATE-->)
1925 <!--chtml endif-->
1926 </DIV>
1927 <CENTER>Copyright 2013-2015 Eduardo Chappa,
1928 <BR>Copyright 2006-2008 University of Washington.
1929 </CENTER>
1931 <P>
1932 When you are viewing a help screen, there may be links to
1933 other topics highlighted (in Reverse video) in the text.
1934 Here is an example.
1935 The word "Introduction" in the TABLE OF CONTENTS below should be
1936 highlighted.
1937 If you type carriage return (or V for View Link, see the commands at the
1938 bottom of the screen) you will be taken to a new help screen to view the
1939 Introduction.
1940 The commands at the bottom of the screen should then include
1941 "P Prev Help".
1942 If you type "P" you will end up back here.
1943 If you type "E" for Exit, you will be back out of help and returned
1944 to the place you were in Alpine when you entered Help.
1945 In this case, you would go back to the MAIN MENU.
1946 There are also other links that are highlighted in bold (or the color used
1947 by your terminal to display bold).
1948 The items after the Introduction in the TABLE OF CONTENTS are all examples
1949 of such links.
1950 In order to view those links, you first have to make the link you want
1951 to view the current link.
1952 The "NextLink" and "PrevLink" commands
1953 (see bottom of screen) can do that for you.
1954 <P>
1956 <H2>TABLE OF CONTENTS</H2>
1957 <OL>
1958 <LI> <A HREF="h_mainhelp_intro">Introduction</A>
1959 <LI> <A HREF="h_mainhelp_pinehelp">Alpine Help</A>
1960 <!--chtml if [ -r PINE_INFO_PATH ]-->
1961 <LI> <A HREF="h_mainhelp_localsupport">Local Support Contacts</A>
1962 <!--chtml endif-->
1963 <LI> <A HREF="h_mainhelp_cmds">Giving Commands in Alpine</A>
1964 <LI> <A HREF="h_mainhelp_config">Alpine Configuration</A>
1965 <LI> <A HREF="h_mainhelp_status">Titlebar Line</A>
1966 <LI> <A HREF="h_mainhelp_mainmenu">Main Menu</A>
1967 <LI> <A HREF="h_mainhelp_index">Index of Messages</A>
1968 <LI> <A HREF="h_mainhelp_reading">Reading Messages</A>
1969 <LI> <A HREF="h_mainhelp_composing">Composing Messages</A>
1970 <LI> <A HREF="h_mainhelp_readingnews">Reading News</A>
1971 <LI> <A HREF="h_mainhelp_abooks">Address Books</A>
1972 <LI> <A HREF="h_mainhelp_ldap">LDAP Directories</A>
1973 <LI> <A HREF="h_mainhelp_folders">Folders</A>
1974 <LI> <A HREF="h_mainhelp_collections">Collection Lists</A>
1975 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
1976 <LI> <A HREF="h_mainhelp_color">Color Setup</A>
1977 <LI> <A HREF="h_mainhelp_filtering">Filtering</A>
1978 <LI> <A HREF="h_mainhelp_roles">Roles</A>
1979 <LI> <A HREF="h_mainhelp_patterns">Patterns</A>
1980 <LI> <A HREF="h_mainhelp_keywords">Keywords (or Flags, or Labels)</A>
1981 <LI> <A HREF="h_mainhelp_mouse">Using a Mouse</A>
1982 <LI> <A HREF="h_mainhelp_cmdlineopts">Command Line Options</A>
1983 <LI> <A HREF="h_mainhelp_securing">Securing Your Alpine Session</A>
1984 <LI> <A HREF="h_mainhelp_smime">S/MIME</A>
1985 <LI> <A HREF="h_mainhelp_problems">Reporting Problems</A>
1986 <LI> <A HREF="X-Alpine-Config:">Show Supported Options in this Alpine</A>
1987 <LI> <A HREF="h_help_index">Index to Alpine's Online Help</A>
1988 </OL>
1990 <P>
1991 <End of help on this topic>
1992 </BODY>
1993 </HTML>
1994 ===== h_mainhelp_intro ======
1995 <HTML>
1996 <HEAD>
1997 <TITLE>Introduction</TITLE>
1998 </HEAD>
1999 <BODY>
2000 <H1>Introduction</H1>
2002 Alpine is an "Alternatively Licensed Program for Internet
2003 News and Email" produced until 2009 by the University of Washington.
2004 It is intended to be an easy-to-use program for
2005 sending, receiving, and filing Internet electronic mail messages and
2006 bulletin board (Netnews/Usenet) messages. Alpine supports the following
2007 Internet protocols and specifications: SMTP (Simple Mail Transport Protocol),
2008 NNTP (Network News Transport Protocol), MIME (Multipurpose Internet Mail
2009 Extensions), IMAP (Internet Message Access Protocol), and LDAP (Lightweight
2010 Directory Access Protocol).<p>
2012 Although originally designed for inexperienced email users, Alpine has
2013 evolved to support many advanced features. There are an ever-growing
2014 number of configuration and personal-preference options, though which of
2015 them are available to you is determined by your local system managers.
2017 <H2>WHAT ALPINE DOES...</H2>
2019 Alpine is a "mail user agent" (MUA), which is a program that
2020 allows you to
2021 compose and read messages using Internet mail standards. (Whether you
2022 can correspond with others on the Internet depends on whether or not your
2023 computer is connected to the Internet.) Alpine also allows reading and
2024 posting messages on the Internet "net news" system, provided
2025 that your site operates a suitable news server.
2027 <H2>WHAT ALPINE DOES NOT DO...</H2>
2029 A "mail user agent" such as Alpine is just one part of a
2030 messaging system. Here are some things that are <B>not</B> done by Alpine,
2031 but require other programs:<P>
2032 <UL>
2033 <LI> Actual relaying of email... which is done by "message transfer
2034 agents".
2035 <LI> Vacation messages... automatically responding to incoming messages
2036 <LI> Anything to do with "talk"... which has nothing to do with
2037 email.
2038 <LI> Anything to do with "irc"... which has nothing to do with email.
2039 <LI> List processing... resending one message to a list of recipients.
2040 </UL>
2042 <P>
2043 <End of help on this topic>
2044 </BODY>
2045 </HTML>
2047 ===== h_mainhelp_pinehelp ======
2048 <HTML>
2049 <HEAD>
2050 <TITLE>Alpine Help</TITLE>
2051 </HEAD>
2052 <BODY>
2053 <H1>Alpine Help</H1>
2055 Alpine help is generally context-sensitive. In other words, each Alpine screen you
2056 use will have its own help text, explaining the choices available for that
2057 screen. This general help section, on the other hand, attempts to give an
2058 overall picture of what Alpine is capable of doing, as well as pointers to
2059 additional help sections about specific topics.<p>
2061 Much of the help text contains links to further help topics, similar to
2062 how the World Wide Web works.
2063 You may choose a link to view using the "NextLink" and
2064 "PrevLink" commands to change the link that is highlighted.
2065 The "View Link" command will then show you the highlighted link.
2066 Similar to the Back button in a web browser, the "Prev Help" command
2067 will return you to where you were before viewing the link, and "Exit Help"
2068 will return you to the location in Alpine before you asked for help.
2069 For example, if you are reading this text in Alpine you may return to the
2070 help table of contents with the "Prev Help" command or you may view the
2071 Release notes link in the next paragraph and then return here with
2072 "Prev Help".
2073 <P>
2075 In addition to this general help on Alpine, <A HREF="h_news">Release Notes</A>
2076 on the current Alpine version are also available from the MAIN MENU: Press
2077 <!--chtml if pinemode="function_key"-->
2078 "F9"
2079 <!--chtml else-->
2080 "R"
2081 <!--chtml endif-->
2082 to browse the release notes. These include changes since the last release,
2083 configuration information, the history of the Alpine
2084 project, credits, and legal notices.
2086 Alpine releases are available via the world wide web at
2087 <P>
2088 <CENTER><SAMP><A
2089 HREF="http://patches.freeiz.com/alpine/release/">http://patches.freeiz.com/alpine/release/</A></SAMP
2090 ></CENTER>
2091 <P>
2093 If you would like to print <EM>all</EM> of Alpine's internal help text
2094 (not recommended) for a little light bedtime reading, then press
2095 <!--chtml if pinemode="function_key"-->
2096 "F12"
2097 <!--chtml else-->
2098 "Z"
2099 <!--chtml endif-->
2100 now. (This assumes that the
2101 copy of Alpine you are using has been properly configured for printing
2102 at your site.)
2103 <P>
2104 <End of help on this topic>
2105 </BODY>
2106 </HTML>
2107 ===== h_mainhelp_localsupport ======
2108 <HTML>
2109 <HEAD>
2110 <TITLE>Local Support Contacts</TITLE>
2111 </HEAD>
2112 <BODY>
2113 <H1>Local Support Contacts</H1>
2115 <!--chtml if [ -r PINE_INFO_PATH ]-->
2116 <!--#include file="PINE_INFO_PATH"-->
2117 <!--chtml else-->
2118 No Local Support Contacts configured.
2119 <!--chtml endif-->
2121 <P>
2122 <End of help on this topic>
2123 </BODY>
2124 </HTML>
2126 ===== h_mainhelp_cmds ======
2127 <HTML>
2128 <HEAD>
2129 <TITLE>Giving Commands in Alpine</TITLE>
2130 </HEAD>
2131 <BODY>
2132 <H1>Giving Commands in Alpine</H1>
2134 Unless configured otherwise
2135 (<A HREF="h_config_blank_keymenu"><!--#echo var="FEAT_disable-keymenu"--></A>)
2136 the bottom two lines of the screen are always used to list the
2137 commands you can give. You press the keys that are highlighted to give
2138 the command. The commands for getting help and going back to the main
2139 menu are always present (except when viewing help as you are now).
2140 <!--chtml if pinemode="function_key"-->
2141 <!--chtml else-->
2142 <p>
2143 Pressing O (meaning "Other Commands") changes the keys
2144 you see at the bottom of any screen. In some cases there are 3 or
2145 even 4 different
2146 sets of keys that can be seen by using the O key. <EM>All commands are
2147 active</EM>, even if they are not currently showing at the bottom of your
2148 screen. In other words, you <EM>never</EM> need to press the O key, except to
2149 remind yourself of the proper key to press to perform an operation.
2151 <H2>Control Key Commands</H2>
2152 When composing mail, and in a few other places, in Alpine you
2153 have to use Control keys. This means pressing the Control key (usually labeled
2154 "Ctrl") and the
2155 letter indicated at the same time. Usually, this is shown with a
2156 "^" in front of the letter. On some systems, certain control
2157 characters are intercepted before they get to Alpine. As a work-around,
2158 you can press the ESCAPE key twice followed by the desired key. For
2159 example, if Ctrl-O (^O) does not work on your system, try typing
2160 "ESC ESC O".
2161 <!--chtml endif-->
2162 <H2>Paging Up and Down</H2>
2163 The "+" and "-" keys are used for
2164 moving to the next or previous page. The space bar is a synonym for
2165 "+". You may also use Ctrl-V to page down and Ctrl-Y to page
2166 up as you do in the message composer. On screens with a WhereIs (search)
2167 command, W or Ctrl-W followed by Ctrl-V will move to the bottom of the
2168 message or list, and W or Ctrl-W followed by Ctrl-Y will move to the top
2169 of the message or list.
2171 <H2>Return Key</H2>
2172 The return key is usually a synonym for a frequently used
2173 command. When viewing a message, there is currently not a default
2174 command, so RETURN does nothing; when in the index, it is synonymous with
2175 "view msg". In the key menu at the bottom of the screen, whatever is
2176 enclosed in square brackets [] is the same as the return key.
2178 <H2>Control Keys Not Used By Alpine</H2>
2179 Most commands in Alpine are single letters, with -- we hope -- some mnemonic
2180 value, but in places where Alpine is expecting text input, e.g. in the composer or
2181 at prompts for file/folder names, control keys must be used for editing and
2182 navigation functions.
2183 <P>
2185 Alpine has used nearly all the control keys available. There are, however,
2186 certain control keys that are reserved by other programs or for technical
2187 reasons. Alpine does not use any of these keys:
2188 <DL>
2189 <DT>Ctrl-S</DT> <DD>Used by Unix as "stop output"</DD>
2190 <DT>Ctrl-Q</DT> <DD>Used by Unix as "resume output"</DD>
2191 <DT>Ctrl-]</DT> <DD>Often used by Telnet as escape key</DD>
2192 </DL>
2193 <P>
2194 Note: Ctrl-S and Ctrl-Q can be subject to
2195 <A HREF="h_special_xon_xoff">special handling</A>.
2196 <P>
2197 In addition, while the ESC key alone is not used for command input,
2198 Alpine will recognize two consecutive ESC key presses followed by a letter
2199 key as a substitute for control key input. For example, the control key
2200 <SAMP>Ctrl-X</SAMP> can alternatively be entered using the
2201 three keystrokes: <SAMP>ESC ESC x</SAMP>.
2202 This is useful if the communication program you are using
2203 (e.g. Telnet) has its own, conflicting, idea of what certain control
2204 characters mean.
2207 <H2>Repainting the Screen</H2>
2208 Sometimes what is displayed on the screen will be
2209 incorrect due to noise on the phone line or other causes and you will want
2210 to repaint the whole screen to make it correct. You can use the Ctrl-L
2211 command to do this. It never hurts to do it when in doubt.
2213 <P>
2214 <End of help on this topic>
2215 </BODY>
2216 </HTML>
2217 ===== h_mainhelp_status ======
2218 <HTML>
2219 <HEAD>
2220 <TITLE>Titlebar Line</TITLE>
2221 </HEAD>
2222 <BODY>
2223 <H1>Titlebar Line</H1>
2225 The top line of the screen is Alpine's titlebar line. It will always display
2226 the current version of Alpine and will also convey information about the
2227 status of the program. This is where you look to find out what
2228 collection, folder and message number is active and where you are in Alpine.
2229 <P>
2231 If the titlebar line says "READONLY" it means that the open folder
2232 (typically your INBOX) is "locked" by another mail session --
2233 most likely a more recent session of Alpine has taken the INBOX lock.
2234 <P>
2236 If the titlebar line says "CLOSED" it means that you are trying to
2237 access a
2238 folder on a remote mail server, and for some reason, communication with
2239 the mail server has either been lost, or never successfully established.
2240 This can be a result of trying to open a non-existent folder, or one
2241 stored on an invalid or non-operational server, or it can mean that Alpine
2242 has been suspended for more that 30 minutes while accessing a remote mail
2243 server.
2245 <P>
2246 <End of help on this topic>
2247 </BODY>
2248 </HTML>
2249 ===== h_mainhelp_mainmenu ======
2250 <HTML>
2251 <HEAD>
2252 <TITLE>Main Menu</TITLE>
2253 </HEAD>
2254 <BODY>
2255 <H1>Main Menu</H1>
2257 The Main Menu lists Alpine's main options.
2258 The key or keys you must type to enter your
2259 choice are to the left of each option or command name.
2260 You can type either uppercase or lowercase letters,
2261 and you should not press <Return> after typing the
2262 letter (unless you are specifically asking for the default,
2263 highlighted command).
2264 <P>
2266 From the Main Menu you can choose to read online help, write (compose) and
2267 send a message, look at an index of your mail messages, open or maintain
2268 your mail folders, update your address book, configure Alpine, and quit Alpine.
2269 There are additional options listed at
2270 the bottom of the screen as well.
2272 <P>
2273 The Help command usually returns context-sensitive help information.
2274 However, in the Main Menu you get the most general help, which includes
2275 a Table of Contents.
2276 The last entry in the Table of Contents is an Index of help topics,
2277 so this is a good place to go if you are having trouble finding how
2278 to do something.
2280 <H2>Main Menu Commands</H2>
2281 The Alpine main menu lists the most common Alpine functions. A <a
2282 href="h_main_menu_commands">full list of these
2283 commands</a> and what they do is available.
2284 <P>
2285 <End of help on this topic>
2286 </BODY>
2287 </HTML>
2288 ===== h_mainhelp_abooks ======
2289 <HTML>
2290 <HEAD>
2291 <TITLE>Address Books</TITLE>
2292 </HEAD>
2293 <BODY>
2294 <H1>Address Books</H1>
2297 As you use email, you can build a list of your regular email correspondents
2298 in your Alpine
2299 Address Book. At the Alpine MAIN MENU, press A to see the Address Book List
2300 screen. Your
2301 personal address book will be highlighted. Press <Return> to view it.
2302 You can use the address book to store email addresses for individuals or
2303 groups, to create easily
2304 remembered "nicknames" for these addresses, and to quickly retrieve an email
2305 address when you are composing a message.
2306 <P>
2307 There are two ways to add addresses to your address book: you can add them
2308 manually or take them from messages (by pressing T to access the Take command).
2309 With either method, you specify nicknames for your correspondents. A single
2310 address book entry (or nickname) can point to just one email address, or, it can
2311 point to more than one. When it points to more than one, it is called a
2312 distribution list. Each distribution list has a nickname, a full name, and a
2313 list of addresses. These
2314 addresses may be actual addresses, other nicknames in your address book, or
2315 other
2316 distribution lists.
2318 <P>
2319 Additional information is available in Alpine's online help:
2320 <ul>
2321 <li><a href="h_abook_opened">The Alpine Address Book</a></li>
2322 </ul>
2323 <P>
2324 <End of help on this topic>
2325 </BODY>
2326 </HTML>
2327 ===== h_mainhelp_ldap ======
2328 <HTML>
2329 <HEAD>
2330 <TITLE>LDAP</TITLE>
2331 </HEAD>
2332 <BODY>
2333 <H1>LDAP</H1>
2335 LDAP (Lightweight Directory Access Protocol) is a standard means of accessing
2336 an organization's shared
2337 directories. Essentially, using LDAP, Alpine is able to find email addresses in
2338 large address
2339 books, rather like the White Pages provided by the phone company. As an Alpine
2340 user, it is not
2341 necessary to know much about how this works, only how to use it and how to
2342 configure
2343 it.
2344 <P>
2345 More information on configuring LDAP is available in Alpine's online help:
2346 <ul>
2347 <li><a href="h_direct_config">Setup LDAP Directory Servers</a></li>
2348 </ul>
2349 <P>
2350 Additional help on using LDAP in Alpine is also available:
2351 <ul>
2352 <li><a href="h_ldap_view">LDAP Response View Explained</a></li>
2353 </ul>
2354 <P>
2355 <End of help on this topic>
2356 </BODY>
2357 </HTML>
2358 ===== h_mainhelp_index ======
2359 <HTML>
2360 <HEAD>
2361 <TITLE>Index of Messages</TITLE>
2362 </HEAD>
2363 <BODY>
2364 <H1>Index of Messages</H1>
2366 In Alpine's message index, the selected message is highlighted. The first
2367 column on the left is blank, shows a "+" if the message was
2368 sent directly to you (i.e., it is not a
2369 copy or from a list), or a "-" if you were explicitly Cc'd.
2370 <P>
2371 The second column may be blank, or it may contain:
2372 <ul>
2373 <li>"N" if the message is new (unread), </li>
2374 <li>"A" if you have answered the message (using the Reply command), </li>
2375 <li>"D" if you have marked the message for deletion.</li>
2376 </ul>
2378 <P>
2379 Note: If you answer a message as well as mark it deleted (in either order),
2380 you will only see the "D".
2382 <P>
2383 The rest of the columns in the message line show you the message
2384 number, date sent, sender, size, and subject. For details, press ? (Help).
2385 The behavior and appearance of the Index screen is highly configurable.
2386 In the Setup/Config screen search (with the WhereIs command) for options
2387 that contain the words "index" or "thread" to see
2388 many of the configuration possibilities.
2389 In particular, the
2390 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
2391 option may be used to configure the look of the standard MESSAGE INDEX lines
2392 in many different ways.
2393 Find <!--#echo var="VAR_index-format"--> in the Setup/Config screen and
2394 read the help text there for more information.
2395 <P>
2396 Most of the commands you need to handle your messages are visible at the
2397 bottom of the screen, and you can press O (OTHER CMDS) to see additional
2398 commands that are available.
2399 You do not need to see these "other commands"
2400 on the screen to use them. That is, you never need to press O as a prefix
2401 for any other command.
2403 <P>
2404 Additional information is available in Alpine's online help:
2405 <ul>
2406 <li><a href="h_mail_index">Message Index Commands</a></li>
2407 </ul>
2408 <P>
2409 <End of help on this topic>
2410 </BODY>
2411 </HTML>
2412 ===== h_mainhelp_reading ======
2413 <HTML>
2414 <HEAD>
2415 <TITLE>Reading Messages</TITLE>
2416 </HEAD>
2417 <BODY>
2418 <H1>Reading Messages</H1>
2420 The message text screen shows you the text of the message along with
2421 its header. If a message has attachments, those will be listed (but not
2422 displayed) also. The titlebar line displays information about the currently
2423 open message, folder and collection. You see the name of the collection
2424 (if there is one) in angle brackets, then the name of the folder, then the
2425 message number and finally the position within the current message (in
2426 percent). If the message is marked for deletion
2427 "DEL" will appear in the
2428 upper right as well.
2430 <P>
2431 As with every Alpine screen, the bottom two lines show you the commands
2432 available.
2434 <P>Additional information is available in Alpine's online help:
2435 <ul>
2436 <li><a href="h_mail_view">Message Text Screen</a></li>
2437 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a></li>
2438 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a></li>
2439 </ul>
2440 <P>
2441 <End of help on this topic>
2442 </BODY>
2443 </HTML>
2444 ===== h_mainhelp_composing ======
2445 <HTML>
2446 <HEAD>
2447 <TITLE>Composing Messages</TITLE>
2448 </HEAD>
2449 <BODY>
2450 <H1>Composing Messages</H1>
2452 To write a message, press C (Compose). You see the Compose Message
2453 screen, which is divided into two parts: the header area and the message
2454 text area. The header area is where information on the recipient (the To:
2455 field) and the subject line go, while the message text area contains the
2456 actual text of the email message. Different commands are available to you
2457 when your cursor is in different areas on this screen. To see additional
2458 help on commands in either the message text or header area, type
2459 <Control>G (Get help).
2461 <P>
2462 To move around, use the arrow keys or Ctrl-N (Next line) and Ctrl-P
2463 (Previous line); to correct typing errors, use <Backspace> or <Delete>.
2465 <P>The following information from Alpine's online help may prove useful:
2466 <ul>
2467 <li><a href="h_composer_to">Message Header Commands</a></li>
2468 <li><a href="h_compose_richhdr">Rich Header Command</a></li>
2469 <li><a href="h_composer">Composer Commands</a></li>
2470 <li><a href="h_edit_nav_cmds">Composer Editing Commands</a></li>
2471 <li><a href="h_config_change_your_from">Changing your From Address</a></li>
2472 <li><a href="h_compose_send">Send Command</a></li>
2473 <li><a href="h_compose_spell">Spell Check Command</a></li>
2474 </ul>
2475 <P>
2476 <End of help on this topic>
2477 </BODY>
2478 </HTML>
2479 ===== h_mainhelp_collections ======
2480 <HTML>
2481 <HEAD>
2482 <TITLE>Collection Lists</TITLE>
2483 </HEAD>
2484 <BODY>
2485 <H1>Collection Lists</H1>
2487 Collection lists are Alpine's way of organizing groups of folders. Each
2488 "collection" can reside on a different server, for example, and contain a
2489 different group of mail folders.
2491 <P>
2492 For more information on this, see:
2493 <ul>
2494 <li><a href="h_what_are_collections">Folder Collections Explained</a></li>
2495 </ul>
2496 <P>
2497 Additional information relating to collection lists is also available in
2498 Alpine's online
2499 help:
2500 <ul>
2501 <li><a href="h_collection_maint">Setup Collection List Screen</a></li>
2502 <li><a href="h_collection_screen">Collection List Screen</a></li>
2503 </ul>
2504 <P>
2505 <End of help on this topic>
2506 </BODY>
2507 </HTML>
2508 ===== h_mainhelp_folders ======
2509 <HTML>
2510 <HEAD>
2511 <TITLE>Folders</TITLE>
2512 </HEAD>
2513 <BODY>
2514 <H1>Folders</H1>
2516 Messages can quickly accumulate in your INBOX folder. If you use email
2517 often, you soon could have hundreds. You need to delete messages you do
2518 not want, and you can use folders to organize messages you wish to save. A
2519 folder is a collection of one or more messages that are stored (just like
2520 the messages in your INBOX) so you can access and manage them.
2522 <P>
2523 You can organize your email messages into different folders by topic,
2524 correspondent, date, or any other category that is meaningful to you. You
2525 can create your own folders, and Alpine automatically provides three:
2526 <ul>
2527 <li>The INBOX folder: messages sent to you are listed in this folder.
2528 When you first start Alpine and go to the Message Index screen, you are
2529 looking at the list of messages in your INBOX folder. Every incoming
2530 message remains in your INBOX until you delete it or save it in another
2531 folder. </li>
2532 <li>The sent-mail folder: copies of messages you send are stored in this
2533 folder. This is
2534 convenient if you cannot remember whether you actually sent a message and want
2535 to check, or
2536 if you want to send a message again.</li>
2537 <li>The saved-messages folder: copies of messages you save are stored in this
2538 folder
2539 unless you choose to save them to other folders you create yourself.</li>
2540 </ul>
2542 <P>
2543 More information about folders is available in Alpine's online help:
2544 <ul>
2545 <li><a href="h_folder_open">Explanation of Folder Selection</a></li>
2546 <li><a href="h_folder_maint">Help for Folder List</a></li>
2547 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a></li>
2548 <li><a href="h_folder_fcc">Folder Select for Fcc ("sent-mail")
2549 Explained</a></li>
2550 <li><a href="h_folder_save">Folder Select for Save Explained</a></li>
2551 </ul>
2552 <P>
2553 <End of help on this topic>
2554 </BODY>
2555 </HTML>
2556 ===== h_mainhelp_color ======
2557 <HTML>
2558 <HEAD>
2559 <TITLE>Color</TITLE>
2560 </HEAD>
2561 <BODY>
2562 <H1>Color</H1>
2564 If the terminal emulator you are using is capable of displaying color or if
2565 you are using PC-Alpine, then it is possible to set up Alpine so that various
2566 parts of the display will be shown in colors you configure. This is done
2567 using the Setup Color screen, available from the MAIN MENU by selecting
2568 the Setup command followed by "K" for Kolor (because "C"
2569 stands for Config in this context).
2571 <P>
2572 For example, you may color things like the titlebar, the current item,
2573 the keymenu, and the status messages.
2574 You may also color lines in the index, and headers and quoted text in the
2575 MESSAGE TEXT screen.
2576 You use the Color Setup screen for configuring most of this, but you must
2577 use the IndexColor setup for coloring whole index lines.
2578 These are available from the MAIN MENU under Setup/Kolor and Setup/Rules/IndexColor.
2580 <P>
2581 The following entries in Alpine's online help provide additional information
2582 about how to use color:
2583 <UL>
2584 <LI> <A HREF="h_color_setup">Color Setup screen</A>
2585 <LI> <A HREF="h_rules_incols">Index Line Color</A>
2586 <LI> <A HREF="h_config_quote_color">quoted text</A> in message view
2587 <LI> <A HREF="h_config_customhdr_pattern">text associated with user-defined headers</A> in message view
2588 </UL>
2589 <P>
2590 <End of help on this topic>
2591 </BODY>
2592 </HTML>
2593 ===== h_mainhelp_mouse ======
2594 <HTML>
2595 <HEAD>
2596 <TITLE>Using a Mouse</TITLE>
2597 </HEAD>
2598 <BODY>
2599 <H1>Using a Mouse</H1>
2601 If you are using PC-Alpine mouse support is turned on automatically.
2602 If you are using UNIX Alpine within an X terminal window or within
2603 a terminal emulator that supports an xterm-style mouse, then you may
2604 turn on support for the mouse with the feature
2605 <A HREF="h_config_enable_mouse"><!--#echo var="FEAT_enable-mouse-in-xterm"--></A>.
2606 For UNIX Alpine you will also need to set the $DISPLAY environment variable.
2607 <P>
2608 PC-Alpine offers considerable mouse support. You can view what is
2609 "clickable" by dragging your mouse over any screen; when the
2610 arrow cursor changes into a hand, you found something. Mouse-click
2611 possibilities include navigating between screens and folders and
2612 double-clicking on hyperlinks to open your Web browser.
2613 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
2614 screen. Examples of right-click options include "copy" after
2615 selecting text to copy and "View in New Window" when you click
2616 on a particular message in the Message Index. The menu choices available
2617 to you will vary based upon what screen is open, where on the screen your
2618 cursor is located, and even what action you have already taken.
2619 Within a folder, you may set the "Important" flag on any
2620 message.
2621 <P>
2622 X terminal mouse support is more limited but still quite powerful.
2623 As with PC-Alpine, clicking on any of the commands in the keymenu at
2624 the bottom of the screen will execute that command as if you typed it.
2625 Double-clicking on a link, for example the link to the
2626 <!--#echo var="FEAT_enable-mouse-in-xterm"--> feature in the paragraph above,
2627 will take you to that link.
2628 Double-clicking on an index line will view the message, and so on.
2629 <P>
2630 <End of help on this topic>
2631 </BODY>
2632 </HTML>
2633 ===== h_mainhelp_keywords ======
2634 <HTML>
2635 <HEAD>
2636 <TITLE>Keywords</TITLE>
2637 </HEAD>
2638 <BODY>
2639 <H1>Keywords</H1>
2641 Within a folder, you may set the "Important" flag on any
2642 message.
2643 This doesn't have any system-defined meaning and is only called
2644 the Important flag because many users use it to signify that a message
2645 is important to them in some way.
2646 <P>
2647 You may also define your own set of keywords.
2648 You might know these as user defined flags or as labels.
2649 These are similar to the Important flag but you choose the names for yourself.
2650 <P>
2651 Alpine will only display keywords that
2652 have been added by you in the Flag Details screen or
2653 that have been configured by you using the Setup/Config option
2654 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
2655 Keywords set by other means (for example, by another email client) will not
2656 show up in Alpine unless you configure Alpine to know about them.
2657 They will show up in the Flag Details screen, but will not show up, for example,
2658 in the index line.
2660 <P>
2661 The following entries in Alpine's online help provide additional information
2662 about how to use keywords:
2663 <ul>
2664 <li><A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--> config option</A></li>
2665 <li><A HREF="h_common_flag">Flag command to set keywords</A></li>
2666 </ul>
2667 <P>
2668 <End of help on this topic>
2669 </BODY>
2670 </HTML>
2671 ===== h_mainhelp_roles ======
2672 <HTML>
2673 <HEAD>
2674 <TITLE>Roles</TITLE>
2675 </HEAD>
2676 <BODY>
2677 <H1>Roles</H1>
2679 You may play different roles depending on who you are replying to. For
2680 example, if you are replying to a message addressed to help-desk you may
2681 be acting as a Help Desk Worker. That role may require that you use a
2682 different return address and/or a different signature.
2684 <P>
2685 To configure roles, go to the MAIN MENU and use the Setup command
2686 followed by "Rules" and then "Roles".
2687 The following entries in Alpine's online help provide additional information
2688 about how to
2689 use roles:
2690 <ul>
2691 <li><a href="h_rules_roles">Setup Roles Screen</a></li>
2692 <li><a href="h_role_select">Roles Screen</a></li>
2693 </ul>
2694 <P>
2695 <End of help on this topic>
2696 </BODY>
2697 </HTML>
2698 ===== h_mainhelp_filtering ======
2699 <HTML>
2700 <HEAD>
2701 <TITLE>Filtering</TITLE>
2702 </HEAD>
2703 <BODY>
2704 <H1>Filtering</H1>
2706 The software that actually delivers mail (the stuff that happens
2707 before Alpine is involved) for you is in a better position to do mail filtering
2708 than Alpine itself.
2709 If possible, you may want to look into using that sort of mail filtering to
2710 deliver mail to different folders, delete it, or forward it.
2711 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
2713 <P>
2714 Filtering is a way to automatically move certain messages from one folder
2715 to another or to automatically delete messages.
2716 You may also automatically set the state (Important, New, Deleted, Answered) of messages
2717 and set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
2718 Alpine doesn't have the ability to forward mail to another address or
2719 to deliver vacation messages.
2721 <P>
2722 To configure filtering, go to the MAIN MENU and use the Setup command
2723 followed by "Rules" and then "Filters".
2724 The following entries in Alpine's online help provide additional information
2725 about how to use filtering:
2726 <UL>
2727 <LI> <A HREF="h_rules_filter">Filtering Setup screen</A>
2728 </UL>
2729 <P>
2730 <End of help on this topic>
2731 </BODY>
2732 </HTML>
2733 ===== h_mainhelp_patterns ======
2734 <HTML>
2735 <HEAD>
2736 <TITLE>Patterns</TITLE>
2737 </HEAD>
2738 <BODY>
2739 <H1>Patterns</H1>
2741 Patterns are used with Roles, Filtering, Index Coloring,
2742 Scoring, Other Rules, and Search Rules, so it may help you to understand exactly how Patterns work.
2743 The following entries in Alpine's online help provide information
2744 about using Patterns:
2745 <UL>
2746 <LI> <A HREF="h_rule_patterns">Patterns</A>
2747 </UL>
2748 <P>
2749 <End of help on this topic>
2750 </BODY>
2751 </HTML>
2752 ===== h_mainhelp_cmdlineopts ======
2753 <HTML>
2754 <HEAD>
2755 <TITLE>Command Line Options</TITLE>
2756 </HEAD>
2757 <BODY>
2758 <H1>Command Line Options</H1>
2760 Alpine accepts a number of command line arguments, allowing you, for
2761 example, to start Alpine and immediately access a particular folder.
2762 Many of these arguments overlap with options in the Alpine configuration file.
2763 If there is a difference, then an option set on the command line takes
2764 precedence.
2765 Alpine expects command line arguments (other than addresses) to be
2766 preceded by a "-" (dash) as normally used by UNIX programs.
2767 A <a href="h_command_line_options">full list</a> of command line
2768 possibilities is available.
2769 <P>
2770 <End of help on this topic>
2771 </BODY>
2772 </HTML>
2773 ===== h_mainhelp_config ======
2774 <HTML>
2775 <HEAD>
2776 <TITLE>Alpine Configuration</TITLE>
2777 </HEAD>
2778 <BODY>
2779 <H1>Alpine Configuration</H1>
2781 Unless it has been administratively disabled, the Setup command on the
2782 MAIN MENU has several subcommands that allow you to modify Alpine's behavior.
2783 The possible subcommands are for general Configuration settings,
2784 Printer settings, Changing your Password, Signature setup,
2785 AddressBook setup, Collection Lists setup, Rules (including Roles, Filters,
2786 Scores, Search, Indexcolor, and Other rules), LDAP Directory setup,
2787 and Color configuration.
2788 In particular, the "Config" subcommand has many features you may
2789 set or unset and many other configuration variables that may be set to change
2790 the way Alpine works.
2791 Every one of the hundreds of options available in that configuration settings
2792 screen has help text associated with it.
2793 You may read that text by moving the cursor to highlight the option and then
2794 typing the Help command.
2795 <P>
2796 These settings are stored in your personal
2797 "pinerc" configuration file (or, optionally, they may be stored
2798 <A HREF="h_config_remote_config">remotely</A>),
2799 but on shared systems these settings
2800 may be over-ridden by a system-wide control file (due to local site
2801 security or support policies). A global pine configuration file can also
2802 be used to set default values for all Alpine users on a particular system.
2803 Power users may be interested in splitting their personal configuration
2804 data into two pieces, a generic piece and
2805 <A HREF="h_config_exceptions">exceptions</A> which apply to
2806 a particular platform.
2807 They may also be interested in <A HREF="h_config_inheritance">configuration inheritance</A>.
2808 General Alpine configuration information can be found
2809 <A HREF="h_news_config">here</A>.
2810 <P>
2811 <End of help on this topic>
2812 </BODY>
2813 </HTML>
2814 ===== h_mainhelp_aggops ======
2815 <HTML>
2816 <HEAD>
2817 <TITLE>Aggregate Operations</TITLE>
2818 </HEAD>
2819 <BODY>
2820 <H1>Aggregate Operations</H1>
2822 When you are in the MESSAGE INDEX, the available commands
2823 (for example, Delete, Undelete, Save, Reply, and so on)
2824 normally act on a single message.
2825 So, for example, if you press the Delete command, the currently highlighted
2826 message is marked Deleted.
2827 These commands that normally act on a single message may be applied to
2828 several messages at once instead.
2829 <P>
2830 By default this feature is turned on, but it could be administratively turned
2831 off to reduce complexity.
2832 The feature
2833 <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>
2834 in the Setup/Config screen is used to turn it off or on.
2835 When this feature is turned on, the four commands "Select",
2836 "SelectCur", "ZoomMode", and "Apply"
2837 are available.
2838 The two selection commands allow you to mark a set of
2839 messages as being "selected".
2840 The "ZoomMode" command will toggle between
2841 displaying only the selected messages and displaying all the messages.
2842 The "Apply" command allows you to
2843 apply one of the regular MESSAGE INDEX commands to all of the selected
2844 messages instead of to only the highlighted message.
2845 <P>
2846 An example aggregate operation would be to catch up when reading
2847 a news group.
2848 That is, get rid of all the messages in the news group so that you can
2849 start fresh.
2850 The easiest way to do this in Alpine is to use aggregate operations.
2851 You want to Delete all of the messages in the group.
2852 You could start at the top and type "D" once for every message.
2853 A much faster method is to first Select all of the messages in the group,
2854 and then Delete all of them.
2855 This would take four keystrokes:
2856 <P>
2857 <CENTER><SAMP>; a (to select all messages)</SAMP></CENTER>
2858 <BR>
2859 <CENTER><SAMP>a d (to delete all selected messages)</SAMP></CENTER>
2860 <P>
2861 Another use of Select is to use it for searching for a particular message
2862 or set of messages in a large folder.
2863 You may know that the message was From a certain user.
2864 You could select all messages from that user to start, and use Zoom to
2865 look at only those messages.
2866 If there were still too many messages to look at you could Narrow the
2867 set of messages further by selecting from all of those messages only
2868 the ones that were after a certain date, or contained a particular phrase
2869 in the Subject, or were too a particular address, and so on.
2870 That may be the end of what you are doing, or you may want to use Apply to
2871 Save or Forward or Print all of the selected messages.
2872 <P>
2873 Some related help topics are
2874 <UL>
2875 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
2876 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
2877 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
2878 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
2879 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
2880 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
2881 </UL>
2882 <P>
2883 <End of help on this topic>
2884 </BODY>
2885 </HTML>
2886 ===== h_mainhelp_readingnews ======
2887 <HTML>
2888 <HEAD>
2889 <TITLE>Reading News</TITLE>
2890 </HEAD>
2891 <BODY>
2892 <H1>Reading News</H1>
2894 <H2>Background</H2>
2895 Alpine can read and post to Internet (or USENET) newsgroups, using the same
2896 commands as for mail. Similar to mailing lists but existing on a larger scale,
2897 Usenet newsgroups allow groups of people with common interests to discuss
2898 particular topics. You might find newsgroups related to your career, or you
2899 might wish to check out the online discussion among the fans of your favorite
2900 television show.
2902 <H2>Configuring Alpine for Reading News</H2>
2903 Alpine often arrives
2904 pre-configured by your system administrator to automatically access the
2905 newsgroups offered by your organization, Internet Service Provider, or
2906 school. PC-Alpine users, and those attempting to customize Unix Alpine, will
2907 need additional details on <a href="h_configuring_news">how to
2908 configure Alpine to read news</a>.
2910 <H2>Accessing Newsgroups</H2>
2911 The first step in reading news is to access the newsgroups collections
2912 screen from Alpine. If everything is configured properly, you should be able
2913 to do this by first typing L (folder List), then selecting the folder
2914 collection listed as "News." The actual name of this collection may differ
2915 from system to system.
2917 <H2>Subscribing to Newsgroups</H2>
2919 Once you have accessed the news collection, you need to subscribe to a
2920 newsgroup that interests you. Subscribing to a newsgroup means that Alpine
2921 will keep a record of the newsgroups in which you are interested and which
2922 articles in those newsgroups have been read.
2924 <H2>Using Newsgroups</H2>
2925 Alpine uses the similar commands to read news as to read mail. For example,
2926 the D command marks messages as Deleted (or "Dismissed," if you prefer),
2927 and the R command Replies to a news posting. Basically, Alpine allows you to
2928 read news as if it were mail, so you don't need to change the way you
2929 interact with Alpine.
2930 <P>
2931 There is also additional Alpine help available on
2932 <A HREF="h_reading_news">how to use Alpine to read news</A>.
2933 <P>
2934 <End of help on this topic>
2935 </BODY>
2936 </HTML>
2937 ===== h_mainhelp_securing ======
2938 <HTML>
2939 <HEAD>
2940 <TITLE>Securing your Alpine Session</TITLE>
2941 </HEAD>
2942 <BODY>
2943 <H1>Securing your Alpine Session</H1>
2945 By default, Alpine will attempt to connect to an IMAP server on the normal
2946 IMAP service port (143).
2947 If the Alpine you are using has been built to
2948 support "Transport Layer Security" (TLS)
2949 and "Secure Sockets Layer" (SSL)
2950 (check by clicking <A HREF="X-Alpine-Config:">here</A>),
2951 and the server offers the STARTTLS capability, then a secure (encrypted)
2952 session will be established.
2953 <P>
2954 When you are connected to a remote folder the titlebar will contain a plus sign
2955 in the far right column if the connection is encrypted using TLS or SSL.
2956 Similarly, when you are being prompted for a password a plus sign will appear in the prompt
2957 if the connection is encrypted.
2959 <H2>More Information on Alpine with SSL and TLS</H2>
2960 <UL>
2961 <LI> <A HREF="h_release_tlscerts">TLS and SSL Usage Note</A> </LI>
2962 <LI> <A HREF="h_folder_server_syntax">/SSL</A> option for older servers which support port 993 SSL but not TLS </LI>
2963 <LI> <A HREF="h_config_alt_auth"><!--#echo var="FEAT_try-alternative-authentication-driver-first"--></A> feature </LI>
2964 <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>
2965 </UL>
2966 <H2>Here are some other security-related features and options</H2>
2967 <P>
2968 <UL>
2969 <LI> <A HREF="h_config_disable_password_caching"><!--#echo var="FEAT_disable-password-caching"--></A> feature to disable password caching </LI>
2970 <LI> <A HREF="h_config_disable_password_file_saving"><!--#echo var="FEAT_disable-password-file-saving"--></A> Disable password file saving</LI>
2971 <LI> <A HREF="h_config_mailcap_params"><!--#echo var="FEAT_enable-mailcap-param-substitution"--></A> feature </LI>
2972 <LI> <A HREF="h_config_disable_auths"><!--#echo var="VAR_disable-these-authenticators"--></A> option </LI>
2973 </UL>
2974 <P>
2975 <End of help on this topic>
2976 </BODY>
2977 </HTML>
2978 ===== h_mainhelp_problems ======
2979 <HTML>
2980 <HEAD>
2981 <TITLE>Reporting Problems</TITLE>
2982 </HEAD>
2983 <BODY>
2984 <H1>Reporting Problems</H1>
2986 We ask that you first read the relevant help screens and then seek
2987 assistance from your own local support staff. Once you are sure that your
2988 difficulty is not a local configuration problem, you might look at the
2989 help section explaining where to look for
2990 <A HREF="h_finding_help">more information</A> and where to
2991 get assistance.
2992 <P>
2994 <ADDRESS>
2995 Eduardo Chappa <chappa@gmx.com>
2996 </ADDRESS>
2998 <P>
2999 <End of help on this topic>
3000 </BODY>
3001 </HTML>
3002 ===== h_main_menu_commands ======
3003 <HTML>
3004 <HEAD>
3005 <TITLE>MAIN MENU COMMANDS</TITLE>
3006 </HEAD>
3007 <BODY>
3008 <H1>MAIN MENU COMMANDS</H1>
3010 <!--chtml if pinemode="function_key"-->
3011 Available Commands --
3012 Group 1 Available Commands -- Group 2<BR>
3013 ------------------------------
3014 --------------------
3015 ----------<BR>
3016 F1 Show this help text F1 Show this help text<BR>
3017 F2 Show all other available commands F2 Show other commands<BR>
3018 F3 Quit Alpine<BR>
3019 F4 Execute current MAIN MENU command F4 <A
3020 HREF="h_common_compose">Compose</A> a message<BR>
3021 F5 Select previous command up on menu F5 <A
3022 HREF="h_common_folders">FOLDER LIST</A> screen<BR>
3023 F6 Select next command down on menu F6 <A
3024 HREF="h_common_goto">Goto</A> a specified folder<BR>
3025
3026 F7 <A
3027 HREF="h_common_index">MESSAGE INDEX</A> screen<BR>
3028
3029 F8 <A
3030 HREF="h_main_journal">Journal</A> of status messages<BR>
3031 F9 Display <A
3032 HREF="h_main_release_notes">Release Notes</A> notes F9 <A
3033 HREF="h_main_setup">SETUP</A> menus<BR>
3034 F10 <A
3035 HREF="h_main_kblock">Lock Keyboard</A> F10 <A
3036 HREF="h_main_addrbook">ADDRESS BOOK</A> screen<BR>
3037
3038 F11 <A
3039 HREF="h_common_role">Compose message using a role</a><BR>
3040 <!--chtml else-->
3041 General Alpine Commands Main Menu Screen Commands<BR>
3042 --------------------- --------------------------<BR>
3043 ? Show Help Text O Show all Other available commands<BR>
3044 C <A
3045 HREF="h_common_compose">Compose</A> a message P Select Previous command up on menu<BR>
3046 I <A
3047 HREF="h_common_index">MESSAGE INDEX</A> screen N Select Next command down on menu<BR>
3048 L <A
3049 HREF="h_common_folders">FOLDER LIST</A> screen R Display Alpine <A HREF="h_main_release_notes">Release Notes</A><BR>
3050 A <A
3051 HREF="h_main_addrbook">ADDRESS BOOK</A> screen K <A
3052 HREF="h_main_kblock">Lock Keyboard</A><BR>
3053 S <A
3054 HREF="h_main_setup">SETUP</A> functions G <A
3055 HREF="h_common_goto">Goto</A> a specified folder<BR>
3056 Q Quit Alpine J <A HREF="h_main_journal">Journal</A> of status messages<BR>
3057 # <A
3058 HREF="h_common_role">Compose message using a role</a><BR>
3059 <!--chtml endif-->
3061 <P>
3062 NOTE:
3063 <OL>
3064 <LI>For help on a particular command, highlight the bold text associated
3065 with it above and hit Return.
3066 <LI> The availability of certain commands (e.g. some of the options under
3067 SETUP) is determined by Alpine configuration files and system capabilities.
3068 At some sites, certain commands may not be available due to security or
3069 support concerns.
3070 </OL>
3071 <P>
3072 <End of help on this topic>
3073 </BODY>
3074 </HTML>
3076 ===== h_command_line_options ======
3077 <HTML>
3078 <HEAD>
3079 <TITLE>COMMAND LINE OPTIONS</TITLE>
3080 </HEAD>
3081 <BODY>
3082 <H1>COMMAND LINE OPTIONS</H1>
3083 Possible starting arguments for Alpine:
3085 <DL COMPACT>
3087 <DT> <EM>[addresses]</EM>
3089 <DD> Send-to: If you give <EM>Alpine</EM> an argument or arguments which
3090 do not begin with a dash, <EM>Alpine</EM> treats them as email addresses.
3091 <EM>Alpine</EM> will startup in
3092 the composer with a message started to the addresses specified.
3093 Once the message is sent, the <EM>Alpine</EM> session closes.
3094 Standard input redirection is allowed.
3095 Separate multiple addresses with a space between them.
3096 Addresses are placed in the "To" field only.
3097 <P>
3099 <DT> < <EM>file</EM>
3101 <DD> <EM>Alpine</EM> will startup in the composer with <EM>file</EM> read
3102 into the body of the message.
3103 Once the message is sent, the <EM>Alpine</EM> session closes.
3104 <P>
3106 <DT> -attach <EM>file</EM>
3108 <DD> Go directly into composer with given file attached.
3109 <P>
3111 <DT> -attachlist <EM>file-list</EM>
3113 <DD> Go directly into composer with given files attached.
3114 This must be the last option on the command line.
3115 <P>
3117 <DT> -attach_and_delete <EM>file</EM>
3119 <DD> Go directly into composer with given file attached, delete when finished.
3120 <P>
3122 <DT> -aux <EM>local_directory</EM>
3124 <DD> <EM>PC-Alpine</EM> only.
3125 This tells <EM>PC-Alpine</EM> the local directory to use for storing auxiliary
3126 files, like debug files, address books, and signature files. The pinerc may
3127 be local or remote.
3128 <P>
3130 <DT> -bail
3132 <DD> If the personal configuration file doesn't already exist, exit.
3133 This might be useful if the configuration file is accessed using some
3134 remote filesystem protocol. If the remote mount is missing this will cause
3135 <EM>Alpine</EM> to quit instead of creating a new pinerc.
3136 <P>
3138 <DT> -c <EM>n</EM>
3140 <DD> When used with the <CODE>-f</CODE> option, apply the <EM>n</EM>th context.
3141 This is used when there are multiple folder collections (contexts) and you
3142 want to open a folder not in the primary collection.
3143 <P>
3145 <DT> -conf
3147 <DD> Configuration: Prints a sample system configuration file to the
3148 screen or standard output. To generate an initial system configuration
3149 file, execute
3151 <PRE><CODE>
3152 pine -conf > <!--#echo var="PINE_CONF_PATH"-->
3153 </CODE></PRE>
3154 <P>
3156 To generate a system configuration file using settings from an old
3157 system configuration file, execute
3159 <PRE><CODE>
3160 pine -P old-pine.conf -conf > <!--#echo var="PINE_CONF_PATH"-->
3161 </CODE></PRE>
3162 <P>
3163 A system configuration file is not required.
3164 <P>
3166 <DT> -copy_abook <<EM>local_abook_file</EM>> <<EM>remote_abook_folder</EM>>
3168 <DD> Copy an address book file to a remote address book folder.
3169 If the remote folder doesn't exist, it will be created.
3170 If it exists but the first message in the folder isn't a remote address
3171 book header message, the copy will be aborted.
3172 This flag will not usually be used by a user.
3173 Instead, the user will create a remote address book from within <EM>Alpine</EM>
3174 and copy entries from the local address book by using aggregate Save in
3175 the address book screen.
3176 <P>
3178 <DT> -copy_pinerc <<EM>local_pinerc_file</EM>> <<EM>remote_pinerc_folder</EM>>
3180 <DD> Copy a pinerc configuration file to a remote pinerc folder.
3181 If the remote folder doesn't exist, it will be created.
3182 If it exists but the first message in the folder isn't a remote pinerc
3183 header message, the copy will be aborted.
3184 This flag may be useful to users who already have a local pinerc file and
3185 would like to convert it to a remote pinerc folder and use that instead.
3186 This gives a way to bootstrap that conversion without having to manually
3187 reset all of the variables in the remote pinerc folder.
3188 <P>
3190 <DT> -d <EM>debug-level</EM>
3192 <DD> Debug Level: Sets the level of debugging information written by
3193 <EM>Alpine</EM>.
3194 <EM>debug-level</EM> can be set to any integer 0-9.
3195 A debug level of 0 turns off debugging for the session.
3196 (Actually there are some levels higher than 9, but you probably don't
3197 want to see them.)
3198 <P>
3200 <DT> -d <EM>keywords</EM>
3202 <DD> You may use a more detailed version of the debugging flag to set
3203 the debug level in separate parts of <EM>Alpine</EM>.
3204 The possibilities are flush, timestamp, imap=0..4, tcp, numfiles=0..31, and
3205 verbose=0..9.
3206 <EM>Flush</EM> causes debugging information to be flushed immediately to
3207 the debug file as it is written.
3208 <EM>Verbose</EM> is the general debugging verbosity level.
3209 <EM>Timestamp</EM> causes timestamps to be added to the debug file, which
3210 is useful when you are trying to figure out what is responsible for delays.
3211 <EM>Numfiles</EM> sets the number of debug files saved.
3212 <EM>Imap</EM> sets the debug level for the debugging statements related
3213 to the conversation with the IMAP server, and more generally, for the
3214 debugging related to <EM>Alpine</EM>'s interaction with the C-Client library.
3215 <EM>Tcp</EM> turns on some TCP/IP debugging.
3216 <P>
3218 <DT> -f <EM>folder</EM>
3220 <DD> Startup folder: <EM>Alpine</EM> will open this folder in place
3221 of the standard INBOX.
3222 <P>
3224 <DT> -F <EM>file</EM>
3226 <DD> Open named text file for viewing and forwarding.
3227 <P>
3229 <DT> -h
3231 <DD> Help: Prints the list of available command-line arguments to the
3232 screen.
3233 <P>
3235 <DT> -i
3237 <DD> <EM>Alpine</EM> will start up in the FOLDER INDEX
3238 screen instead of the MAIN MENU.
3239 <P>
3241 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"-->=i</EM>.
3242 <P>
3244 <DT> -I <EM>a,b,c,...</EM>
3246 <DD> Initial Keystrokes: <EM>Alpine</EM> will execute this comma-separated
3247 sequence of commands upon startup.
3248 This allows users to get <EM>Alpine</EM> to start in any
3249 of its menus/screens.
3250 You cannot include any input to the composer in the initial keystrokes.
3251 The key <Return> is represented by a ``CR'' in
3252 the keystroke list; the spacebar is designated by the letters ``SPACE''.
3253 Control keys are two character sequences beginning with ``^'', such as
3254 ``^I''.
3255 A tab character is ``TAB''.
3256 Function keys are ``F1'' - ``F12'' and the arrow keys are ``UP'',
3257 ``DOWN'', ``LEFT'', and ``RIGHT''.
3258 A restriction is that you can't mix function keys and character keys in this
3259 list even though you can, in some cases, mix them when running <EM>Alpine</EM>.
3260 A user can always use only <EM>character</EM> keys in the startup list even
3261 if he or she is using <EM>function</EM> keys normally, or vice versa.
3262 If an element in this list is a string of characters surrounded by double
3263 quotes (") then it will be expanded into the individual characters in
3264 the string, excluding the double quotes.
3265 <P>
3267 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"--></EM>
3268 <P>
3270 <DT> -install
3272 <DD> For <EM>PC-Alpine</EM> only, this option prompts the user for
3273 some basic information to help with getting properly set up.
3274 <P>
3276 <DT> -k
3278 <DD> Function-Key Mode: When invoked in this way, <EM>Alpine</EM> expects
3279 the input of commands to be function-keys.
3280 Otherwise, commands are linked to the regular character keys.
3281 <P>
3283 Configuration equivalent: <EM><!--#echo var="FEAT_use-function-keys"--></EM> included in
3284 <EM>Feature-List</EM>.
3285 <P>
3287 <DT> -n <EM>n</EM>
3289 <DD> Message-Number: When specified, <EM>Alpine</EM> starts up in the
3290 FOLDER INDEX screen with the current message being the specified
3291 message number.
3292 <P>
3294 <DT> -nosplash
3296 <DD> <EM>PC-Alpine</EM> only.
3297 This tells <EM>PC-Alpine</EM> not to display the splash screen upon startup.
3298 This may be helpful for certain troubleshooting or terminal server scenarios.
3299 <P>
3301 <DT> -o <EM>folder</EM>
3303 <DD> Opens the INBOX (or a folder specified via the -f argument) ReadOnly.
3304 <P>
3306 <DT> -p <EM>pinerc</EM>
3308 <DD> Uses the named file as the personal configuration file instead of
3309 <EM>~/.pinerc</EM> or the default PINERC search sequence <EM>PC-Alpine</EM> uses.
3310 Alpinerc may be either a local file or a remote configuration folder.
3311 <P>
3313 <DT> -P <EM>pinerc</EM>
3315 <DD> Uses the named file as the system wide configuration file instead of
3316 <EM><!--#echo var="PINE_CONF_PATH"--></EM> on UNIX, or nothing on <EM>PC-Alpine</EM>.
3317 Alpinerc may be either a local file or a remote configuration folder.
3318 <P>
3320 <DT> -passfile <EM>passfile</EM>
3322 <DD> This tells <EM>Alpine</EM> what file should be used as the password file.
3323 This should be a fully-qualified filename.
3324 <P>
3326 <DT> -pinerc <EM>file</EM>
3328 <DD> Output fresh pinerc configuration to <EM>file</EM>, preserving the
3329 settings of variables that the user has made.
3330 Use <EM>file</EM> set to ``-'' to make output go to standard out.
3331 <P>
3333 <DT> -r
3335 <DD> Restricted Mode: For UNIX <EM>Alpine</EM> only.
3336 <EM>Alpine</EM> in restricted mode can only send email to itself.
3337 Save and export are limited.
3338 <P>
3340 <DT> -registry <EM>cmd</EM>
3342 <DD> For <EM>PC-Alpine</EM> only, this option affects the values of
3343 <EM>Alpine</EM>'s registry entries.
3344 Possible values for <EM>cmd</EM> are set, clear, and dump.
3345 <EM>Set</EM> will always reset <EM>Alpine</EM>'s registry
3346 entries according to its current settings.
3347 <EM>Clear</EM> will clear the registry values.
3348 <EM>Clearsilent</EM> will clear the registry values without any dialogs.
3349 <EM>Dump</EM> will display the values of current registry settings.
3350 Note that the dump command is currently disabled.
3351 Without the -registry option, <EM>PC-Alpine</EM> will write values into
3352 the registry only if there currently aren't any values set.
3353 <P>
3355 <DT> -sort <EM>key</EM>
3357 <DD> Sort-Key: Specifies the order messages will be displayed in for the
3358 FOLDER INDEX screen.
3359 <EM>Key</EM> can have the following values:
3360 arrival, date, subject, orderedsubj, thread, from, size, score, to, cc,
3361 arrival/reverse, date/reverse, subject/reverse, orderedsubj/reverse, thread/reverse,
3362 from/reverse, size/reverse, score/reverse, to/reverse, and cc/reverse.
3363 The default value is "arrival".
3364 The <EM>key</EM> value reverse is equivalent to arrival/reverse.
3365 <P>
3367 Configuration equivalent: <EM><!--#echo var="VAR_sort-key"--></EM>.
3368 <P>
3370 <DT> -uninstall
3372 <DD> For <EM>PC-Alpine</EM> only, this option removes references to Alpine
3373 in Windows settings. The registry settings are removed and
3374 the password cache is cleared.
3375 <P>
3377 <DT> -url <EM>url</EM>
3379 <DD> Open the given URL.
3380 <P>
3382 <DT> -v
3384 <DD> Version: Print version information to the screen.
3385 <P>
3387 <DT> -x <EM>exceptions_config</EM>
3389 <DD> Configuration settings in the exceptions configuration override your normal
3390 default settings.
3391 <EM>Exceptions_config</EM> may be either a local file or a remote Alpine configuration folder.
3392 <P>
3394 <DT> -z
3396 <DD> Enable Suspend: When run with this flag, the key sequence ctrl-z
3397 will suspend the <EM>Alpine</EM> session.
3398 <P>
3400 Configuration equivalent: <EM><!--#echo var="FEAT_enable-suspend"--></EM> included in
3401 <EM>Feature-List</EM>.
3402 <P>
3404 <DT> -<EM>option</EM>=<EM>value</EM>
3406 <DD> Assign <EM>value</EM> to the config option <EM>option</EM>.
3407 For example, <EM>-signature-file=sig1</EM> or
3408 <EM>-Feature-List=signature-at-bottom</EM>.
3409 Note: Feature-List values are
3410 additive and features may be preceded with no- to turn them off.
3411 Also, as a special case, the "Feature-List=" part of that may be
3412 omitted. For example, <EM>-signature-at-bottom</EM> is equivalent to
3413 <EM>-Feature-List=signature-at-bottom</EM>.
3414 <P>
3416 </DL>
3417 <P>
3418 <End of help on this topic>
3419 </BODY>
3420 </HTML>
3421 ===== h_configuring_news ======
3422 <HTML>
3423 <HEAD>
3424 <TITLE>CONFIGURING NEWS</TITLE>
3425 </HEAD>
3426 <BODY>
3427 <H1>CONFIGURING NEWS</H1>
3428 Alpine can access news folders in any one of three different ways:
3429 <DL>
3430 <DT>REMOTE NNTP</DT>
3431 <DD>Using the Network News Transport Protocol (NNTP) to
3432 access news on a remote news server. In this case the newsrc file is
3433 stored on the machine where Alpine is running.
3435 <P>
3436 To specify a remote news-collection accessed via NNTP use the
3437 SETUP/collectionList screen's "Add" command. Set the
3438 Server: value to the NNTP server's hostname appended with the
3439 communication method "/service=NNTP", and set the Path:
3440 value to the "#news." namespace (without the quotes). See
3441 the "<A HREF="h_composer_cntxt_server">Server:</A>" field's
3442 help text for a more complete explanation of access method, and the
3443 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3444 text for a more complete explanation of "namespace".
3445 <P>
3446 Instead of specifying a news-collection, you may simply set the
3447 <A HREF="h_config_nntp_server">NNTP Server</A>
3448 option, which will cause Alpine to create a default news-collection for you.
3449 Another NNTP option that may be of interest is
3450 <A HREF="h_config_nntprange"><!--#echo var="VAR_nntp-range"--></A>.
3452 <DT>REMOTE IMAP</DT>
3453 <DD>Using the Internet Message Access Protocol (IMAP) to
3454 access news on a remote news server. In this case, your newsrc file is
3455 stored on the news server, in your home directory, so you must have an
3456 account on the news server, but you would be running Alpine on a different
3457 machine. The news server must be running an IMAPd server process.
3459 <P>
3460 To specify a remote news-collection accessed via IMAP use the
3461 SETUP/collectionList screen's "Add" command. Set the
3462 Server: value to the IMAP server's hostname, and set the Path: value
3463 to the "#news." namespace (without the quotes). See the
3464 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3465 text for a more complete explanation of "namespace".
3467 </DD>
3469 <DT>LOCAL</DT>
3470 <DD>Using local file access to the news database. In this
3471 case, your newsrc file is stored on the news server, in your home
3472 directory, so you must have an account on the news server, and you would
3473 be running Alpine on the same machine.
3475 <P>
3476 To specify a local news-collection use the SETUP/collectionList
3477 screen's "Add" command. Leave the Server: value blank, and
3478 set the Path: value to the "#news." namespace (without the
3479 quotes). See the "<A HREF="h_composer_cntxt_path">Path:</A>"
3480 field's help text for a more complete explanation of "namespace".
3482 </DD>
3483 </DL>
3485 <P>
3487 NOTE: Should no news-collection be defined as above, Alpine will
3488 automatically create one using the Setup/Config screen's
3489 "<!--#echo var="VAR_nntp-server"-->" variable's value if defined. The collection
3490 will be created as a "Remote NNTP" as described above.
3492 <P>
3494 If you are a PC-Alpine user, either option 1 (NNTP) or option 2 (IMAP) is
3495 possible. If you don't have an account on the news server, or if the news
3496 server is not running an IMAP daemon, then you must use NNTP. (If you are not
3497 sure, ask your service provider, university, or company for help.) In
3498 this case, your Unix .newsrc file can be transferred to your PC. A good
3499 place to put it would be in the same directory as your PINERC file, under
3500 the name NEWSRC, but you can
3501 <A HREF="h_config_newsrc_path">specify a different location</A>
3502 via Alpine's Setup/Config screen.
3504 <P>
3505 Other configuration features related to news are
3506 <A HREF="h_config_8bit_nntp"><!--#echo var="FEAT_enable-8bit-nntp-posting"--></A>.
3507 <A HREF="h_config_compose_news_wo_conf"><!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></A>,
3508 <A HREF="h_config_news_uses_recent"><!--#echo var="FEAT_news-approximates-new-status"--></A>,
3509 <A HREF="h_config_news_cross_deletes"><!--#echo var="FEAT_news-deletes-across-groups"--></A>,
3510 <A HREF="h_config_news_catchup"><!--#echo var="FEAT_news-offers-catchup-on-close"--></A>,
3511 <A HREF="h_config_post_wo_validation"><!--#echo var="FEAT_news-post-without-validation"--></A>,
3512 <A HREF="h_config_read_in_newsrc_order"><!--#echo var="FEAT_news-read-in-newsrc-order"--></A>, and
3513 <A HREF="h_config_quell_post_prompt"><!--#echo var="FEAT_quell-extra-post-prompt"--></A>.
3515 <P>
3516 <End of help on this topic>
3517 </BODY>
3518 </HTML>
3519 ===== h_reading_news ======
3520 <HTML>
3521 <HEAD>
3522 <TITLE>READING NEWS</TITLE>
3523 </HEAD>
3524 <BODY>
3525 <H1>READING NEWS</H1>
3527 Alpine uses almost the same commands for manipulating news folders as for
3528 mail folders. This means, for example, that when you are done with a
3529 message, you would use "D" to mark it as Deleted (or Dismissed,
3530 if you prefer.) This "mail-like" behavior differs from that of
3531 most newsreaders, wherein a message is implicitly dismissed after you have
3532 looked at it once. We strongly believe that Alpine should offer as much
3533 consistency as possible between mail and news, so the mail paradigm --
3534 wherein a message does not magically disappear without explicit action by
3535 the user -- is used for news as well. <P>
3537 If you answer a message in a news folder, the index view will show the
3538 "A" flag as usual; but the industry standard file Alpine uses to
3539 keep track of what news as been read has no way of storing this flag, so
3540 it will not be preserved across sessions. The Deleted flag is the only
3541 one that is preserved when you leave and then return to a newsgroup. As an
3542 additional note on replies, when you Reply to a newsgroup message and say
3543 you want to reply to all recipients, Alpine will ask if you want to post the
3544 message to all the newsgroups listed in the original message. <P>
3546 If you would like Alpine to mark more-or-less recent news messages as
3547 "New", then set the
3548 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
3549 feature (which is set by default). This will cause messages after the last one you have marked as
3550 Deleted to appear with "N" status in the MESSAGE INDEX. The
3551 "N" status often makes it easier to distinguish later news
3552 articles from those you've previously seen, but not yet disposed of via
3553 the "D" key. Note that this is an approximation, not an exact
3554 record of which messages you have not seen.
3555 <P>
3557 A frequent operation in news-reading is "catching up" -- that
3558 is, getting rid of all the messages in the newsgroup so that you can
3559 "start fresh." The easiest way to do this in Alpine is via the
3560 Select command. You would enter the following four keystrokes:
3561 <tt>;aad</tt> to select all messaged, and then apply the delete (or
3562 dismiss) command to all of them.
3564 <P>
3565 There are also additional details on
3566 <A HREF="h_configuring_news">configuring news</a>.
3568 <P>
3569 <End of help on this topic>
3570 </BODY>
3571 </HTML>
3572 ====== h_help_index ======
3573 <HTML>
3574 <HEAD>
3575 <TITLE>Help Index</TITLE>
3576 </HEAD>
3577 <BODY>
3578 <H1>Help Index</H1>
3579 <ul>
3580 <li><a href="h_mainhelp_abooks">Address Books</a></li>
3581 <li><a href="h_abook_top">ADDRESS BOOK LIST COMMANDS</a>
3582 <li><a href="h_main_addrbook">Address Book Command</a>
3583 <li><a href="h_abook_view">Address Book View Explained</a>
3584 <li><a href="h_compose_addrcomplete">Address Completion</a>
3585 <li><a href="h_abook_select_listmode">Address Listmode Selection from Composer Explained</a>
3586 <li><a href="h_abook_select_checks">Address Selection from Composer Explained</a>
3587 <li><a href="h_composer_abook_comment">Addressbook Comment Explained</a>
3588 <li><a href="h_composer_abook_fcc">Addressbook Fcc Explained</a>
3589 <li><a href="h_composer_abook_add_folder">Addressbook Folder Name Field Explained</a>
3590 <li><a href="h_composer_abook_full">Addressbook Fullname Explained</a>
3591 <li><a href="h_composer_abook_add_nick">Addressbook NickName Field Explained</a>
3592 <li><a href="h_composer_abook_nick">Addressbook Nickname Explained</a>
3593 <li><a href="h_abook_select_addr">Addressbook Selection Explained</a>
3594 <li><a href="h_abook_select_top">Addressbook Selection Navigation Explained</a>
3595 <li><a href="h_composer_abook_add_server">Addressbook Server Name Field Explained</a>
3596 <li><a href="h_mainhelp_aggops">Aggregate Operations</a>
3597 <li><a href="h_mainhelp_config">Alpine Configuration</a>
3598 <li><a href="h_mainhelp_pinehelp">Alpine Help</a>
3599 <li><a href="h_news_legal">Alpine Legal Notices</a>
3600 <li><a href="h_compose_alted">Alt Editor Command</a>
3601 <li><a href="h_index_cmd_apply">Apply Command</a>
3602 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a>
3603 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a>
3604 <li><a href="h_mainhelp_filtering">Blocking Messages</a>
3605 <li><a href="h_composer_browse">BROWSER</a>
3606 <li><a href="h_common_bounce">Bounce Command</a>
3607 <li><a href="h_compose_cancel">Cancel Command</a>
3608 <li><a href="h_config_change_your_from">Changing your From Address</a>
3609 <li><a href="h_collection_screen">COLLECTION LIST screen</a>
3610 <li><a href="h_mainhelp_color">Color</a>
3611 <li><a href="h_composer_ctrl_j">COMPOSER ATTACH</a>
3612 <li><a href="h_composer">COMPOSER COMMANDS</a>
3613 <li><a href="h_mainhelp_composing">Composing Messages</a>
3614 <li><a href="h_mainhelp_collections">Collection Lists</a>
3615 <li><a href="h_composer_cntxt_nick">Collection Nickname Explained</a>
3616 <li><a href="h_composer_cntxt_path">Collection Path: Explained</a>
3617 <li><a href="h_composer_cntxt_server">Collection Server: Explained</a>
3618 <li><a href="h_composer_cntxt_view">Collection View: Explained</a>
3619 <li><a href="h_mainhelp_cmdlineopts">Command Line Options</a>
3620 <li><a href="h_common_compose">Compose Command</a>
3621 <li><a href="h_edit_nav_cmds">Composer Editing Commands Explained</a>
3622 <li><a href="h_common_conditional_cmds">Conditional Commands</a>
3623 <li><a href="h_reply_token_conditionals">Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</a>
3624 <li><a href="h_mainhelp_config">Configuration</a>
3625 <li><a href="h_composer_custom_free">CUSTOMIZED HEADER FIELD</a>
3626 <li><a href="h_config_dflt_color">Default Color</a>
3627 <li><a href="h_common_delete">Delete and Undelete Commands</a>
3628 <li><a href="h_composer_qserv_cn">Directory Query Form Explained</a>
3629 <li><a href="h_special_list_commands">Email List Commands Explained</a>
3630 <li><a href="h_composer_search">Explanation of Composer Whereis Command </a>
3631 <li><a href="h_folder_open">Explanation of Folder Selection</a>
3632 <li><a href="h_special_xon_xoff">Explanation of Alpine's XOFF/XON Handling</a>
3633 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a>
3634 <li><a href="h_ge_export">Export File Selection</a>
3635 <li><a href="h_ge_allparts">Export Message File Selection</a>
3636 <li><a href="h_index_cmd_expunge">Expunge/Exclude Command</a>
3637 <li><a href="h_info_on_locking">FAQs on Alpine Locking</a>
3638 <li><a href="h_config_allow_chg_from">FEATURE: <!--#echo var="FEAT_allow-changing-from"--></a>
3639 <li><a href="h_config_allow_talk">FEATURE: <!--#echo var="FEAT_allow-talk"--></a>
3640 <li><a href="h_config_alt_compose_menu">FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></a>
3641 <li><a href="h_config_alt_role_menu">FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></a>
3642 <li><a href="h_config_force_low_speed">FEATURE: <!--#echo var="FEAT_assume-slow-link"--></a>
3643 <li><a href="h_config_auto_read_msgs">FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></a>
3644 <li><a href="h_config_auto_open_unread">FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></a>
3645 <li><a href="h_config_auto_unselect">FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></a>
3646 <li><a href="h_config_auto_unzoom">FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></a>
3647 <li><a href="h_config_auto_zoom">FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></a>
3648 <li><a href="h_config_use_boring_spinner">FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></a>
3649 <li><a href="h_config_check_mail_onquit">FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></a>
3650 <li><a href="h_config_combined_abook_display">FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></a>
3651 <li><a href="h_config_combined_folder_display">FEATURE: <!--#echo var="FEAT_combined-folder-display"--></a>
3652 <li><a href="h_config_combined_subdir_display">FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></a>
3653 <li><a href="h_config_cancel_confirm">FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></a>
3654 <li><a href="h_config_lame_list_mode">FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></a>
3655 <li><a href="h_config_compose_rejects_unqual">FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></a>
3656 <li><a href="h_config_send_filter_dflt">FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></a>
3657 <li><a href="h_config_compose_news_wo_conf">FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></a>
3658 <li><a href="h_config_del_from_dot">FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></a>
3659 <li><a href="h_config_compose_maps_del">FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></a>
3660 <li><a href="h_config_confirm_role">FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></a>
3661 <li><a href="h_config_tab_no_prompt">FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></a>
3662 <li><a href="h_config_dates_to_local">FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></a>
3663 <li><a href="h_config_copy_to_to_from">FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></a>
3664 <li><a href="h_config_del_skips_del">FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></a>
3665 <li><a href="h_config_disable_config_cmd">FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></a>
3666 <li><a href="h_config_disable_index_locale_dates">FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></a>
3667 <li><a href="h_config_disable_kb_lock">FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></a>
3668 <li><a href="h_config_blank_keymenu">FEATURE: <!--#echo var="FEAT_disable-keymenu"--></a>
3669 <li><a href="h_config_disable_password_caching">FEATURE: <!--#echo var="FEAT_disable-password-caching"--></a>
3670 <li><a href="h_config_disable_password_cmd">FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></a>
3671 <li><a href="h_config_disable_pipes_in_sigs">FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></a>
3672 <li><a href="h_config_disable_pipes_in_templates">FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></a>
3673 <li><a href="h_config_disable_regex">FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
3674 <li><a href="h_config_disable_roles_setup">FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></a>
3675 <li><a href="h_config_disable_roles_sigedit">FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></a>
3676 <li><a href="h_config_disable_roles_templateedit">FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></a>
3677 <li><a href="h_config_input_history">FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></a>
3678 <li><a href="h_config_disable_collate">FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></a>
3679 <li><a href="h_config_disable_shared">FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></a>
3680 <li><a href="h_config_disable_signature_edit">FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></a>
3681 <li><a href="h_config_take_fullname">FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></a>
3682 <li><a href="h_config_take_lastfirst">FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></a>
3683 <li><a href="h_config_disable_reset_disp">FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></a>
3684 <li><a href="h_config_disable_sender">FEATURE: <!--#echo var="FEAT_disable-sender"--></a>
3685 <li><a href="h_config_quell_dead_letter">FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></a>
3686 <li><a href="h_config_quell_flowed_text">FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></a>
3687 <li><a href="h_downgrade_multipart_to_text">FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></a>
3688 <li><a href="h_config_8bit_smtp">FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></a>
3689 <li><a href="h_config_8bit_nntp">FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></a>
3690 <li><a href="h_config_enable_agg_ops">FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></a>
3691 <li><a href="h_config_enable_alt_ed">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></a>
3692 <li><a href="h_config_alt_ed_now">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></a>
3693 <li><a href="h_config_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></a>
3694 <li><a href="h_config_relaxed_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></a>
3695 <li><a href="h_config_compose_bg_post">FEATURE: <!--#echo var="FEAT_enable-background-sending"--></a>
3696 <li><a href="h_config_enable_bounce">FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></a>
3697 <li><a href="h_config_cruise_mode">FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></a>
3698 <li><a href="h_config_cruise_mode_delete">FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></a>
3699 <li><a href="h_config_compose_dsn">FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></a>
3700 <li><a href="h_config_enable_dot_files">FEATURE: <!--#echo var="FEAT_enable-dot-files"--></a>
3701 <li><a href="h_config_enable_lessthan_exit">FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></a>
3702 <li><a href="h_config_fast_recent">FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></a>
3703 <li><a href="h_config_enable_flag">FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></a>
3704 <li><a href="h_config_flag_screen_default">FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></a>
3705 <li><a href="h_config_flag_screen_kw_shortcut">FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></a>
3706 <li><a href="h_config_enable_full_hdr_and_text">FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></a>
3707 <li><a href="h_config_enable_full_hdr">FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></a>
3708 <li><a href="h_config_allow_goto">FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></a>
3709 <li><a href="h_config_enable_dot_folders">FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></a>
3710 <li><a href="h_config_enable_incoming">FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></a>
3711 <li><a href="h_config_enable_incoming_checking">FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></a>
3712 <li><a href="h_config_enable_jump">FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></a>
3713 <li><a href="h_config_show_delay_cue">FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></a>
3714 <li><a href="h_config_mailcap_params">FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></a>
3715 <li><a href="h_config_enable_mouse">FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></a>
3716 <li><a href="h_config_enable_view_addresses">FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></a>
3717 <li><a href="h_config_enable_view_attach">FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></a>
3718 <li><a href="h_config_enable_view_arrows">FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></a>
3719 <li><a href="h_config_enable_view_url">FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></a>
3720 <li><a href="h_config_enable_view_web_host">FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></a>
3721 <li><a href="h_config_enable_mulnewsrcs">FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></a>
3722 <li><a href="h_config_enable_xterm_newmail">FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></a>
3723 <li><a href="h_config_enable_newmail_short_text">FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>
3724 <li><a href="h_config_sub_lists">FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></a>
3725 <li><a href="h_config_enable_y_print">FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></a>
3726 <li><a href="h_config_prefix_editing">FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></a>
3727 <li><a href="h_config_enable_search_and_repl">FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></a>
3728 <li><a href="h_config_sigdashes">FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></a>
3729 <li><a href="h_config_new_thread_blank_subject">FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></a>
3730 <li><a href="h_config_can_suspend">FEATURE: <!--#echo var="FEAT_enable-suspend"--></a>
3731 <li><a href="h_config_enable_tab_complete">FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></a>
3732 <li><a href="h_config_enable_take_export">FEATURE: <!--#echo var="FEAT_enable-take-export"--></a>
3733 <li><a href="h_config_enable_role_take">FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></a>
3734 <li><a href="h_config_tray_icon">FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></a>
3735 <li><a href="h_config_enable_pipe">FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></a>
3736 <li><a href="h_config_verbose_post">FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></a>
3737 <li><a href="h_config_expanded_addrbooks">FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></a>
3738 <li><a href="h_config_expanded_distlists">FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></a>
3739 <li><a href="h_config_expanded_folders">FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></a>
3740 <li><a href="h_config_expose_hidden_config">FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></a>
3741 <li><a href="h_config_expunge_manually">FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></a>
3742 <li><a href="h_config_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></a>
3743 <li><a href="h_config_full_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></a>
3744 <li><a href="h_config_no_fcc_attach">FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></a>
3745 <li><a href="h_config_force_arrow">FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></a>
3746 <li><a href="h_config_forward_as_attachment">FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></a>
3747 <li><a href="h_config_preserve_field">FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></a>
3748 <li><a href="h_config_quell_empty_dirs">FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></a>
3749 <li><a href="h_config_hide_nntp_path">FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></a>
3750 <li><a href="h_config_attach_in_reply">FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></a>
3751 <li><a href="h_config_fcc_on_bounce">FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></a>
3752 <li><a href="h_config_include_header">FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></a>
3753 <li><a href="h_config_auto_include_reply">FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></a>
3754 <li><a href="h_config_incoming_checking_total">FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></a>
3755 <li><a href="h_config_incoming_checking_recent">FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></a>
3756 <li><a href="h_config_add_ldap">FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></a>
3757 <li><a href="h_config_maildrops_preserve_state">FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></a>
3758 <li><a href="h_config_mark_fcc_seen">FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></a>
3759 <li><a href="h_config_mark_for_cc">FEATURE: <!--#echo var="FEAT_mark-for-cc"--></a>
3760 <li><a href="h_config_mulnews_as_typed">FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></a>
3761 <li><a href="h_config_news_uses_recent">FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></a>
3762 <li><a href="h_config_news_cross_deletes">FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></a>
3763 <li><a href="h_config_news_catchup">FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></a>
3764 <li><a href="h_config_post_wo_validation">FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></a>
3765 <li><a href="h_config_read_in_newsrc_order">FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></a>
3766 <li><a href="h_config_nntp_search_uses_overview">FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></a>
3767 <li><a href="h_config_thread_sorts_by_arrival">FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></a>
3768 <li><a href="h_config_expunge_inbox">FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></a>
3769 <li><a href="h_config_expunge_stayopens">FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></a>
3770 <li><a href="h_config_pass_c1_control">FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></a>
3771 <li><a href="h_config_pass_control">FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></a>
3772 <li><a href="h_config_predict_nntp_server">FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></a>
3773 <li><a href="h_config_prefer_plain_text">FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></a>
3774 <li><a href="h_config_preopen_stayopens">FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></a>
3775 <li><a href="h_config_preserve_start_stop">FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></a>
3776 <li><a href="h_config_quell_folder_internal_msg">FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></a>
3777 <li><a href="h_config_quell_checks_comp">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></a>
3778 <li><a href="h_config_quell_checks_comp_inbox">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></a>
3779 <li><a href="h_config_quell_partial">FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></a>
3780 <li><a href="h_config_quell_local_lookup">FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></a>
3781 <li><a href="h_config_ff_between_msgs">FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></a>
3782 <li><a href="h_config_print_from">FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></a>
3783 <li><a href="h_config_print_index">FEATURE: <!--#echo var="FEAT_print-index-enabled"--></a>
3784 <li><a href="h_config_custom_print">FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></a>
3785 <li><a href="h_config_prune_uses_iso">FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></a>
3786 <li><a href="h_config_quell_personal_name_prompt">FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></a>
3787 <li><a href="h_config_quell_ssl_largeblocks">FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></a>
3788 <li><a href="h_config_quell_user_id_prompt">FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></a>
3789 <li><a href="h_config_quit_wo_confirm">FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></a>
3790 <li><a href="h_config_quote_replace_noflow">FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></a>
3791 <li><a href="h_config_next_thrd_wo_confirm">FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></a>
3792 <li><a href="h_config_auto_reply_to">FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></a>
3793 <li><a href="h_config_inbox_no_confirm">FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></a>
3794 <li><a href="h_config_save_aggregates">FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></a>
3795 <li><a href="h_config_save_part_wo_confirm">FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></a>
3796 <li><a href="h_config_save_advances">FEATURE: <!--#echo var="FEAT_save-will-advance"--></a>
3797 <li><a href="h_config_save_wont_delete">FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></a>
3798 <li><a href="h_config_quote_all_froms">FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></a>
3799 <li><a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
3800 <li><a href="h_config_select_wo_confirm">FEATURE: <!--#echo var="FEAT_select-without-confirm"--></a>
3801 <li><a href="h_config_auto_fcc_only">FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></a>
3802 <li><a href="h_config_send_wo_confirm">FEATURE: <!--#echo var="FEAT_send-without-confirm"--></a>
3803 <li><a href="h_config_separate_fold_dir_view">FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></a>
3804 <li><a href="h_config_show_cursor">FEATURE: <!--#echo var="FEAT_show-cursor"--></a>
3805 <li><a href="h_config_textplain_int">FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></a>
3806 <li><a href="h_config_select_in_bold">FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></a>
3807 <li><a href="h_config_show_sort">FEATURE: <!--#echo var="FEAT_show-sort"--></a>
3808 <li><a href="h_config_single_list">FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></a>
3809 <li><a href="h_config_sig_at_bottom">FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></a>
3810 <li><a href="h_config_slash_coll_entire">FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></a>
3811 <li><a href="h_config_sort_fcc_alpha">FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></a>
3812 <li><a href="h_config_sort_save_alpha">FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></a>
3813 <li><a href="h_config_always_spell_check">FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></a>
3814 <li><a href="h_config_winpos_in_config">FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></a>
3815 <li><a href="h_config_strip_sigdashes">FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>
3816 <li><a href="h_config_strip_ws_before_send">FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></a>
3817 <li><a href="h_config_quells_asterisks">FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></a>
3818 <li><a href="h_config_quell_attach_ext_warn">FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></a>
3819 <li><a href="h_config_quell_attach_extra_prompt">FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></a>
3820 <li><a href="h_config_no_bezerk_zone">FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></a>
3821 <li><a href="h_config_quell_charset_warning">FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></a>
3822 <li><a href="h_config_quell_content_id">FEATURE: <!--#echo var="FEAT_quell-content-id"--></a>
3823 <li><a href="h_config_quell_post_prompt">FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></a>
3824 <li><a href="h_config_quell_filtering_done_message">FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></a>
3825 <li><a href="h_config_quell_filtering_messages">FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></a>
3826 <li><a href="h_config_quell_full_hdr_reset">FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></a>
3827 <li><a href="h_config_quell_imap_env">FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></a>
3828 <li><a href="h_config_quell_lock_failure_warnings">FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></a>
3829 <li><a href="h_config_quell_domain_warn">FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></a>
3830 <li><a href="h_config_quell_news_env">FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></a>
3831 <li><a href="h_config_quell_host_after_url">FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></a>
3832 <li><a href="h_config_quell_beeps">FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></a>
3833 <li><a href="h_config_quell_tz_comment">FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></a>
3834 <li><a href="h_config_suppress_user_agent">FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></a>
3835 <li><a href="h_config_tab_checks_recent">FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></a>
3836 <li><a href="h_config_tab_uses_unseen">FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></a>
3837 <li><a href="h_config_tab_new_only">FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></a>
3838 <li><a href="h_config_termcap_wins">FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></a>
3839 <li><a href="h_config_color_thrd_import">FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></a>
3840 <li><a href="h_config_alt_auth">FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></a>
3841 <li><a href="h_config_unsel_wont_advance">FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></a>
3842 <li><a href="h_config_use_current_dir">FEATURE: <!--#echo var="FEAT_use-current-dir"--></a>
3843 <li><a href="h_config_use_fk">FEATURE: <!--#echo var="FEAT_use-function-keys"--></a>
3844 <li><a href="h_config_use_reg_start_for_stayopen">FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></a>
3845 <li><a href="h_config_use_resentto">FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></a>
3846 <li><a href="h_config_use_sender_not_x">FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></a>
3847 <li><a href="h_config_suspend_spawns">FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></a>
3848 <li><a href="h_config_use_system_translation">FEATURE: Use System Translation</a>
3849 <li><a href="h_config_vertical_list">FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></a>
3850 <li><a href="h_config_warn_if_fcc_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></a>
3851 <li><a href="h_config_warn_if_subj_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></a>
3852 <li><a href="h_config_warn_if_no_to_or_cc">FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></a>
3853 <li><a href="h_mainhelp_filtering">Filtering</a>
3854 <li><a href="h_finding_help">Finding more information and requesting help</a>
3855 <li><a href="h_common_flag">Flag Command</a>
3856 <li><a href="h_config_quell_flowed_text">Flowed Text</a>
3857 <li><a href="h_mainhelp_folders">Folders</a>
3858 <li><a href="h_what_are_collections">Folder Collections Explained</a>
3859 <li><a href="h_common_folders">Folder List Command</a>
3860 <li><a href="h_folder_fcc">Folder Select for Fcc Explained</a>
3861 <li><a href="h_folder_save">Folder Select for Save Explained</a>
3862 <li><a href="h_folder_server_syntax">Folder Server Name Syntax</a>
3863 <li><a href="h_config_change_your_from">From Address, Changing</a>
3864 <li><a href="main_menu_tx">GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</a>
3865 <li><a href="h_pine_for_windows">GETTING HELP IN ALPINE</a>
3866 <li><a href="h_common_goto">Goto Command</a>
3867 <li><a href="h_common_hdrmode">HdrMode Command</a>
3868 <li><a href="h_mainhelp_pinehelp">Help</a>
3869 <li><a href="h_special_help_nav">Help Text Navigation Explained</a>
3870 <li><a href="h_folder_maint">Help for Folder List</a>
3871 <li><a href="h_valid_folder_names">IMAP</a>
3872 <li><a href="h_ge_import">Import File Selection</a>
3873 <li><a href="h_mainhelp_index">Index of Messages</a>
3874 <li><a href="h_composer_ins_m">INSERT MESSAGE</a>
3875 <li><a href="h_composer_ins">INSERT TEXT FILE</a>
3876 <li><a href="h_address_format">INTERNET EMAIL ADDRESS FORMAT</a>
3877 <li><a href="h_info_on_mbox">Information on mbox driver</a>
3878 <li><a href="h_mainhelp_intro">Introduction</a>
3879 <li><a href="h_main_journal">Journal Command</a>
3880 <li><a href="h_common_jump">Jump Command</a>
3881 <li><a href="h_compose_justify">Justify Command</a>
3882 <li><a href="h_main_kblock">Keyboard Lock Command</a>
3883 <li><a href="h_mainhelp_keywords">Keywords (or Flags, or Labels)</a>
3884 <li><a href="h_mainhelp_ldap">LDAP</a>
3885 <li><a href="h_config_ldap_opts_tls">LDAP FEATURE: Attempt-TLS-On-Connection</a>
3886 <li><a href="h_config_ldap_opts_nosub">LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</a>
3887 <li><a href="h_config_ldap_opts_rhs">LDAP FEATURE: Lookup-Addrbook-Contents</a>
3888 <li><a href="h_config_ldap_opts_tlsmust">LDAP FEATURE: Require-TLS-On-Connection</a>
3889 <li><a href="h_config_ldap_opts_ref">LDAP FEATURE: Save-Search-Criteria-Not-Result</a>
3890 <li><a href="h_config_ldap_opts_impl">LDAP FEATURE: Use-Implicitly-From-Composer</a>
3891 <li><a href="h_config_ldap_binddn">LDAP OPTION: Bind-DN</a>
3892 <li><a href="h_config_ldap_cust">LDAP OPTION: Custom-Search-Filter</a>
3893 <li><a href="h_config_ldap_email_attr">LDAP OPTION: EmailAttribute</a>
3894 <li><a href="h_config_ldap_gn_attr">LDAP OPTION: GivennameAttribute</a>
3895 <li><a href="h_config_ldap_server">LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></a>
3896 <li><a href="h_config_ldap_cn_attr">LDAP OPTION: NameAttribute</a>
3897 <li><a href="h_config_ldap_nick">LDAP OPTION: Nickname</a>
3898 <li><a href="h_config_ldap_port">LDAP OPTION: Port</a>
3899 <li><a href="h_config_ldap_base">LDAP OPTION: Search-Base</a>
3900 <li><a href="h_config_ldap_searchrules">LDAP OPTION: Search-Rule</a>
3901 <li><a href="h_config_ldap_searchtypes">LDAP OPTION: Search-Type</a>
3902 <li><a href="h_config_ldap_size">LDAP OPTION: Sizelimit</a>
3903 <li><a href="h_config_ldap_sn_attr">LDAP OPTION: SurnameAttribute</a>
3904 <li><a href="h_config_ldap_time">LDAP OPTION: Timelimit</a>
3905 <li><a href="h_ldap_view">LDAP Response View Explained</a>
3906 <li><a href="h_maildrop">Mail Drop: What is it?</a>
3907 <li><a href="h_mainhelp_mainmenu">MAIN MENU</a>
3908 <li><a href="h_mail_index">MESSAGE INDEX COMMANDS</a>
3909 <li><a href="h_mail_view">MESSAGE TEXT SCREEN</a>
3910 <li><a href="h_compose_markcutpaste">Mark, Cut and Paste Commands</a>
3911 <li><a href="h_common_index">Message Index Command</a>
3912 <li><a href="h_mainhelp_mouse">Mouse</a>
3913 <li><a href="h_mainhelp_aggops">Multiple Message Operations</a>
3914 <li><a href="new_user_greeting">NEW USER GREETING</a>
3915 <li><a href="new_version_greeting">NEW VERSION GREETING</a>
3916 <li><a href="h_mainhelp_readingnews">News Reading</a>
3917 <li><a href="h_folder_subscribe">Newsgroup Subcribe Screen explained</a>
3918 <li><a href="h_folder_postnews">Newsgroup selecting for Posting explained</a>
3919 <li><a href="h_common_nextnew">NextNew Command</a>
3920 <li><a href="h_abook_select_nick">Nickname Selection Explained</a>
3921 <li><a href="h_mainhelp_readingnews">NNTP</a>
3922 <li><a href="h_config_address_book">OPTION: <!--#echo var="VAR_address-book"--></a>
3923 <li><a href="h_config_abook_formats">OPTION: <!--#echo var="VAR_addressbook-formats"--></a>
3924 <li><a href="h_config_ab_sort_rule">OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></a>
3925 <li><a href="h_config_alt_addresses">OPTION: <!--#echo var="VAR_alt-addresses"--></a>
3926 <li><a href="h_config_active_msg_interval">OPTION: <!--#echo var="VAR_busy-cue-rate"--></a>
3927 <li><a href="h_config_color_style">OPTION: Color Style</a>
3928 <li><a href="h_config_wordseps">OPTION: <!--#echo var="VAR_composer-word-separators"--></a>
3929 <li><a href="h_config_composer_wrap_column">OPTION: <!--#echo var="VAR_composer-wrap-column"--></a>
3930 <li><a href="h_config_index_color_style">OPTION: <!--#echo var="VAR_current-indexline-style"--></a>
3931 <li><a href="h_config_cursor_style">OPTION: Cursor Style</a>
3932 <li><a href="h_config_custom_hdrs">OPTION: <!--#echo var="VAR_customized-hdrs"--></a>
3933 <li><a href="h_config_deadlets">OPTION: <!--#echo var="VAR_dead-letter-files"--></a>
3934 <li><a href="h_config_comp_hdrs">OPTION: <!--#echo var="VAR_default-composer-hdrs"--></a>
3935 <li><a href="h_config_default_fcc">OPTION: <!--#echo var="VAR_default-fcc"--></a>
3936 <li><a href="h_config_def_save_folder">OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></a>
3937 <li><a href="h_config_disable_auths">OPTION: <!--#echo var="VAR_disable-these-authenticators"--></a>
3938 <li><a href="h_config_disable_drivers">OPTION: <!--#echo var="VAR_disable-these-drivers"--></a>
3939 <li><a href="h_config_char_set">OPTION: Display Character Set</a>
3940 <li><a href="h_config_display_filters">OPTION: <!--#echo var="VAR_display-filters"--></a>
3941 <li><a href="h_config_download_cmd">OPTION: <!--#echo var="VAR_download-command"--></a>
3942 <li><a href="h_config_download_prefix">OPTION: <!--#echo var="VAR_download-command-prefix"--></a>
3943 <li><a href="h_config_editor">OPTION: <!--#echo var="VAR_editor"--></a>
3944 <li><a href="h_config_empty_hdr_msg">OPTION: <!--#echo var="VAR_empty-header-message"--></a>
3945 <li><a href="h_config_fcc_rule">OPTION: <!--#echo var="VAR_fcc-name-rule"--></a>
3946 <li><a href="h_config_file_dir">OPTION: File Directory</a>
3947 <li><a href="h_config_folder_spec">OPTION: <!--#echo var="VAR_folder-collections"--></a>
3948 <li><a href="h_config_reopen_rule">OPTION: <!--#echo var="VAR_folder-reopen-rule"--></a>
3949 <li><a href="h_config_fld_sort_rule">OPTION: <!--#echo var="VAR_folder-sort-rule"--></a>
3950 <li><a href="h_config_font_char_set">OPTION: Font Character Set</a>
3951 <li><a href="h_config_font_name">OPTION: Font Name</a>
3952 <li><a href="h_config_font_size">OPTION: Font Size</a>
3953 <li><a href="h_config_font_style">OPTION: Font Style</a>
3954 <li><a href="h_config_form_folder">OPTION: <!--#echo var="VAR_form-letter-folder"--></a>
3955 <li><a href="h_config_glob_addrbook">OPTION: <!--#echo var="VAR_global-address-book"--></a>
3956 <li><a href="h_config_goto_default">OPTION: <!--#echo var="VAR_goto-default-rule"--></a>
3957 <li><a href="h_config_header_general_color">OPTION: Header General Color</a>
3958 <li><a href="h_config_image_viewer">OPTION: <!--#echo var="VAR_image-viewer"--></a>
3959 <li><a href="h_config_inbox_path">OPTION: <!--#echo var="VAR_inbox-path"--></a>
3960 <li><a href="h_config_archived_folders">OPTION: <!--#echo var="VAR_incoming-archive-folders"--></a>
3961 <li><a href="h_config_psleep">OPTION: <!--#echo var="VAR_mailcap-check-interval"--></a>
3962 <li><a href="h_config_incoming_interv">OPTION: <!--#echo var="VAR_incoming-check-interval"--></a>
3963 <li><a href="h_config_incoming_second_interv">OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></a>
3964 <li><a href="h_config_incoming_list">OPTION: <!--#echo var="VAR_incoming-check-list"--></a>
3965 <li><a href="h_config_incoming_timeo">OPTION: <!--#echo var="VAR_incoming-check-timeout"--></a>
3966 <li><a href="h_config_incoming_folders">OPTION: <!--#echo var="VAR_incoming-folders"--></a>
3967 <li><a href="h_config_inc_startup">OPTION: <!--#echo var="VAR_incoming-startup-rule"--></a>
3968 <li><a href="h_config_incunseen_color">OPTION: Incoming Unseen Color</a>
3969 <li><a href="h_config_index_arrow_color">OPTION: Index Arrow Color</a>
3970 <li><a href="h_config_index_color">OPTION: Index Colors</a>
3971 <li><a href="h_config_index_format">OPTION: <!--#echo var="VAR_index-format"--></a>
3972 <li><a href="h_config_index_from_color">OPTION: Index From Color</a>
3973 <li><a href="h_config_index_opening_color">OPTION: Index Opening Color</a>
3974 <li><a href="h_config_index_pri_color">OPTION: Index Priority Symbol Colors</a>
3975 <li><a href="h_config_index_subject_color">OPTION: Index Subject Color</a>
3976 <li><a href="h_config_init_cmd_list">OPTION: <!--#echo var="VAR_initial-keystroke-list"--></a>
3977 <li><a href="h_config_key_char_set">OPTION: Keyboard Character Set</a>
3978 <li><a href="h_config_keylabel_color">OPTION: KeyLabel Color</a>
3979 <li><a href="h_config_keyname_color">OPTION: KeyName Color</a>
3980 <li><a href="h_config_keywords">OPTION: <!--#echo var="VAR_keywords"--></a>
3981 <li><a href="h_config_kw_color">OPTION: Keyword Colors</a>
3982 <li><a href="h_config_kw_braces">OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></a>
3983 <li><a href="h_config_prune_date">OPTION: <!--#echo var="VAR_last-time-prune-questioned"--></a>
3984 <li><a href="h_config_last_vers">OPTION: <!--#echo var="VAR_last-version-used"--></a>
3985 <li><a href="h_config_literal_sig">OPTION: <!--#echo var="VAR_literal-signature"--></a>
3986 <li><a href="h_config_mailcheck">OPTION: <!--#echo var="VAR_mail-check-interval"--></a>
3987 <li><a href="h_config_mailchecknoncurr">OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></a>
3988 <li><a href="h_config_mailcap_path">OPTION: <!--#echo var="VAR_mailcap-search-path"--></a>
3989 <li><a href="h_config_maildropcheck">OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></a>
3990 <li><a href="h_config_maxremstream">OPTION: <!--#echo var="VAR_max-remote-connections"--></a>
3991 <li><a href="h_config_metamsg_color">OPTION: Meta-Message Color</a>
3992 <li><a href="h_config_mimetype_path">OPTION: <!--#echo var="VAR_mimetype-search-path"--></a>
3993 <li><a href="h_config_new_ver_quell">OPTION: <!--#echo var="VAR_new-version-threshold"--></a>
3994 <li><a href="h_config_fifopath">OPTION: NewMail FIFO Path</a>
3995 <li><a href="h_config_newmailwidth">OPTION: <!--#echo var="VAR_newmail-window-width"--></a>
3996 <li><a href="h_config_news_active">OPTION: <!--#echo var="VAR_news-active-file-path"--></a>
3997 <li><a href="h_config_news_spec">OPTION: <!--#echo var="VAR_news-collections"--></a>
3998 <li><a href="h_config_news_spool">OPTION: <!--#echo var="VAR_news-spool-directory"--></a>
3999 <li><a href="h_config_newsrc_path">OPTION: <!--#echo var="VAR_newsrc-path"--></a>
4000 <li><a href="h_config_nntprange">OPTION: <!--#echo var="VAR_nntp-range"--></a>
4001 <li><a href="h_config_nntp_server">OPTION: <!--#echo var="VAR_nntp-server"--></HEAD></a>
4002 <li><a href="h_config_normal_color">OPTION: Normal Color</a>
4003 <li><a href="h_config_opening_sep">OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></a>
4004 <li><a href="h_config_oper_dir">OPTION: <!--#echo var="VAR_operating-dir"--></a>
4005 <li><a href="h_config_pat_old">OPTION: Patterns</a>
4006 <li><a href="h_config_pat_filts">OPTION: <!--#echo var="VAR_patterns-filters2"--></a>
4007 <li><a href="h_config_pat_other">OPTION: <!--#echo var="VAR_patterns-other"--></a>
4008 <li><a href="h_config_pat_roles">OPTION: <!--#echo var="VAR_patterns-roles"--></a>
4009 <li><a href="h_config_pat_scores">OPTION: <!--#echo var="VAR_patterns-scores2"--></a>
4010 <li><a href="h_config_pers_name">OPTION: <!--#echo var="VAR_personal-name"--></a>
4011 <li><a href="h_config_print_cat">OPTION: <!--#echo var="VAR_personal-print-category"--></a>
4012 <li><a href="h_config_print_command">OPTION: <!--#echo var="VAR_personal-print-command"--></a>
4013 <li><a href="h_config_post_char_set">OPTION: <!--#echo var="VAR_posting-character-set"--></a>
4014 <li><a href="h_config_postponed_folder">OPTION: <!--#echo var="VAR_postponed-folder"--></a>
4015 <li><a href="h_config_print_font_char_set">OPTION: Print-Font-Char-Set</a>
4016 <li><a href="h_config_print_font_name">OPTION: Print-Font-Name</a>
4017 <li><a href="h_config_print_font_size">OPTION: Print-Font-Size</a>
4018 <li><a href="h_config_print_font_style">OPTION: Print-Font-Style</a>
4019 <li><a href="h_config_printer">OPTION: Printer</a>
4020 <li><a href="h_config_prompt_color">OPTION: Prompt Color</a>
4021 <li><a href="h_config_pruned_folders">OPTION: <!--#echo var="VAR_pruned-folders"--></a>
4022 <li><a href="h_config_pruning_rule">OPTION: <!--#echo var="VAR_pruning-rule"--></a>
4023 <li><a href="h_config_quote_color">OPTION: Quote Colors</a>
4024 <li><a href="h_config_quote_replace_string">OPTION: <!--#echo var="VAR_quote-replace-string"--></a>
4025 <li><a href="h_config_quote_suppression">OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></a>
4026 <li><a href="h_config_read_message_folder">OPTION: <!--#echo var="VAR_read-message-folder"--></a>
4027 <li><a href="h_config_remote_abook_history">OPTION: <!--#echo var="VAR_remote-abook-history"--></a>
4028 <li><a href="h_config_abook_metafile">OPTION: <!--#echo var="VAR_remote-abook-metafile"--></a>
4029 <li><a href="h_config_remote_abook_validity">OPTION: <!--#echo var="VAR_remote-abook-validity"--></a>
4030 <li><a href="h_config_reply_indent_string">OPTION: <!--#echo var="VAR_reply-indent-string"--></a>
4031 <li><a href="h_config_reply_intro">OPTION: <!--#echo var="VAR_reply-leadin"--></a>
4032 <li><a href="h_config_reverse_color">OPTION: Reverse Color</a>
4033 <li><a href="h_config_rshcmd">OPTION: <!--#echo var="VAR_rsh-command"--></a>
4034 <li><a href="h_config_rsh_open_timeo">OPTION: <!--#echo var="VAR_rsh-open-timeout"--></a>
4035 <li><a href="h_config_rshpath">OPTION: <!--#echo var="VAR_rsh-path"--></a>
4036 <li><a href="h_config_saved_msg_name_rule">OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></a>
4037 <li><a href="h_config_scroll_margin">OPTION: <!--#echo var="VAR_scroll-margin"--></a>
4038 <li><a href="h_config_slctbl_color">OPTION: Selectable Item Color</a>
4039 <li><a href="h_config_sending_filter">OPTION: <!--#echo var="VAR_sending-filters"--></a>
4040 <li><a href="h_config_sendmail_path">OPTION: <!--#echo var="VAR_sendmail-path"--></a>
4041 <li><a href="h_config_signature_color">OPTION: Signature Color</a>
4042 <li><a href="h_config_signature_file">OPTION: <!--#echo var="VAR_signature-file"--></a>
4043 <li><a href="h_config_smtp_server">OPTION: <!--#echo var="VAR_smtp-server"--></a>
4044 <li><a href="h_config_sort_key">OPTION: <!--#echo var="VAR_sort-key"--></a>
4045 <li><a href="h_config_speller">OPTION: <!--#echo var="VAR_speller"--></a>
4046 <li><a href="h_config_sshcmd">OPTION: <!--#echo var="VAR_ssh-command"--></a>
4047 <li><a href="h_config_ssh_open_timeo">OPTION: <!--#echo var="VAR_ssh-open-timeout"--></a>
4048 <li><a href="h_config_sshpath">OPTION: <!--#echo var="VAR_ssh-path"--></a>
4049 <li><a href="h_config_status_color">OPTION: Status Color</a>
4050 <li><a href="h_config_status_msg_delay">OPTION: <!--#echo var="VAR_status-message-delay"--></a>
4051 <li><a href="h_config_permlocked">OPTION: <!--#echo var="VAR_stay-open-folders"--></a>
4052 <li><a href="h_config_tcp_open_timeo">OPTION: <!--#echo var="VAR_tcp-open-timeout"--></a>
4053 <li><a href="h_config_tcp_query_timeo">OPTION: <!--#echo var="VAR_tcp-query-timeout"--></a>
4054 <li><a href="h_config_tcp_readwarn_timeo">OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></a>
4055 <li><a href="h_config_tcp_writewarn_timeo">OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></a>
4056 <li><a href="h_config_thread_disp_style">OPTION: <!--#echo var="VAR_threading-display-style"--></a>
4057 <li><a href="h_config_thread_exp_char">OPTION: <!--#echo var="VAR_threading-expanded-character"--></a>
4058 <li><a href="h_config_thread_index_style">OPTION: <!--#echo var="VAR_threading-index-style"--></a>
4059 <li><a href="h_config_thread_indicator_char">OPTION: <!--#echo var="VAR_threading-indicator-character"--></a>
4060 <li><a href="h_config_thread_lastreply_char">OPTION: <!--#echo var="VAR_threading-lastreply-character"--></a>
4061 <li><a href="h_config_title_color">OPTION: Title Color</a>
4062 <li><a href="h_config_titleclosed_color">OPTION: Title Closed Color</a>
4063 <li><a href="h_config_titlebar_color_style">OPTION: <!--#echo var="VAR_titlebar-color-style"--></a>
4064 <li><a href="h_config_unk_char_set">OPTION: <!--#echo var="VAR_unknown-character-set"--></a>
4065 <li><a href="h_config_upload_cmd">OPTION: <!--#echo var="VAR_upload-command"--></a>
4066 <li><a href="h_config_upload_prefix">OPTION: <!--#echo var="VAR_upload-command-prefix"--></a>
4067 <li><a href="h_config_browser">OPTION: <!--#echo var="VAR_url-viewers"--></a>
4068 <li><a href="h_config_domain_name">OPTION: <!--#echo var="VAR_use-only-domain-name"--></a>
4069 <li><a href="h_config_user_dom">OPTION: <!--#echo var="VAR_user-domain"--></a>
4070 <li><a href="h_config_user_id">OPTION: <!--#echo var="VAR_user-id"--></a>
4071 <li><a href="h_config_user_input_timeo">OPTION: <!--#echo var="VAR_user-input-timeout"--></a>
4072 <li><a href="h_config_viewer_headers">OPTION: <!--#echo var="VAR_viewer-hdrs"--></a>
4073 <li><a href="h_config_customhdr_pattern">OPTION: Viewer Header Color Pattern</a>
4074 <li><a href="h_config_customhdr_color">OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></a>
4075 <li><a href="h_config_viewer_margin_left">OPTION: <!--#echo var="VAR_viewer-margin-left"--></a>
4076 <li><a href="h_config_viewer_margin_right">OPTION: <!--#echo var="VAR_viewer-margin-right"--></a>
4077 <li><a href="h_config_viewer_overlap">OPTION: <!--#echo var="VAR_viewer-overlap"--></a>
4078 <li><a href="h_config_window_position">OPTION: Window-Position</a>
4079 <li><a href="h_mainhelp_patterns">Patterns</a>
4080 <li><a href="h_config_role_abookfrom">PATTERNS: Address in Address Book</a>
4081 <li><a href="h_config_role_age">PATTERNS: Age Interval</a>
4082 <li><a href="h_config_role_alltextpat">PATTERNS: AllText Pattern</a>
4083 <li><a href="h_config_role_bom">PATTERNS: Beginning of Month</a>
4084 <li><a href="h_config_role_boy">PATTERNS: Beginning of Year</a>
4085 <li><a href="h_config_role_bodytextpat">PATTERNS: BodyText Pattern</a>
4086 <li><a href="h_config_role_cat_cmd">PATTERNS: Categorizer Command</a>
4087 <li><a href="h_config_role_cat_cmd_example">PATTERNS: Categorizer Command Example</a>
4088 <li><a href="h_config_role_ccpat">PATTERNS: Cc Pattern</a>
4089 <li><a href="h_config_role_cat_limit">PATTERNS: Character Limit</a>
4090 <li><a href="h_config_role_charsetpat">PATTERNS: Character Set Pattern</a>
4091 <li><a href="h_config_role_comment">PATTERNS: Comment</a>
4092 <li><a href="h_config_role_fldr_type">PATTERNS: Current Folder Type</a>
4093 <li><a href="h_config_role_cat_status">PATTERNS: Exit Status Interval</a>
4094 <li><a href="h_config_role_arbpat">PATTERNS: Extra Headers Pattern</a>
4095 <li><a href="h_config_role_frompat">PATTERNS: From Pattern</a>
4096 <li><a href="h_config_role_keywordpat">PATTERNS: Keyword Pattern</a>
4097 <li><a href="h_config_role_stat_ans">PATTERNS: Message Answered Status</a>
4098 <li><a href="h_config_role_stat_del">PATTERNS: Message Deleted Status</a>
4099 <li><a href="h_config_role_stat_imp">PATTERNS: Message Important Status</a>
4100 <li><a href="h_config_role_stat_new">PATTERNS: Message New Status</a>
4101 <li><a href="h_config_role_stat_recent">PATTERNS: Message Recent Status</a>
4102 <li><a href="h_config_role_newspat">PATTERNS: News Pattern</a>
4103 <li><a href="h_config_role_nick">PATTERNS: Nickname</a>
4104 <li><a href="h_config_role_particpat">PATTERNS: Participant Pattern</a>
4105 <li><a href="h_config_role_stat_8bitsubj">PATTERNS: Raw 8-bit in Subject</a>
4106 <li><a href="h_config_role_recippat">PATTERNS: Recipient Pattern</a>
4107 <li><a href="h_config_role_scorei">PATTERNS: Score Interval</a>
4108 <li><a href="h_config_role_senderpat">PATTERNS: Sender Pattern</a>
4109 <li><a href="h_config_role_size">PATTERNS: Size Interval</a>
4110 <li><a href="h_config_role_subjpat">PATTERNS: Subject Pattern</a>
4111 <li><a href="h_config_role_topat">PATTERNS: To Pattern</a>
4112 <li><a href="h_config_filt_opts_nonterm">PATTERNS FEATURE: Dont-Stop-Even-if-Rule-Matches</a>
4113 <li><a href="h_config_filt_opts_notdel">PATTERNS FEATURE: Move-Only-if-Not-Deleted</a>
4114 <li><a href="h_config_filt_opts_sentdate">PATTERNS FEATURE: Use-Date-Header-For-Age</a>
4115 <li><a href="h_config_filt_rule_type">PATTERNS FILTER ACTION: Filter Action</a>
4116 <li><a href="h_config_filter_kw_clr">PATTERNS FILTER ACTION: Clear These Keywords</a>
4117 <li><a href="h_config_filt_stat_ans">PATTERNS FILTER ACTION: Set Answered Status</a>
4118 <li><a href="h_config_filt_stat_del">PATTERNS FILTER ACTION: Set Deleted Status</a>
4119 <li><a href="h_config_filt_stat_imp">PATTERNS FILTER ACTION: Set Important Status</a>
4120 <li><a href="h_config_filt_stat_new">PATTERNS FILTER ACTION: Set New Status</a>
4121 <li><a href="h_config_filter_kw_set">PATTERNS FILTER ACTION: Set These Keywords</a>
4122 <li><a href="h_config_incol">PATTERNS INDEXCOLOR ACTION: Index Line Color</a>
4123 <li><a href="h_config_set_index_format">PATTERNS OTHER ACTION: Set Index Format</a>
4124 <li><a href="h_config_perfolder_sort">PATTERNS OTHER ACTION: Set Sort Order</a>
4125 <li><a href="h_config_other_startup">PATTERNS OTHER ACTION: Set Startup Rule</a>
4126 <li><a href="h_config_role_inick">PATTERNS ROLE ACTION: Initialize Values From Role</a>
4127 <li><a href="h_config_role_setfcc">PATTERNS ROLE ACTION: Set Fcc</a>
4128 <li><a href="h_config_role_setfrom">PATTERNS ROLE ACTION: Set From</a>
4129 <li><a href="h_config_role_setlitsig">PATTERNS ROLE ACTION: Set Literal Signature</a>
4130 <li><a href="h_config_role_setotherhdr">PATTERNS ROLE ACTION: Set Other Headers</a>
4131 <li><a href="h_config_role_setreplyto">PATTERNS ROLE ACTION: Set Reply-To</a>
4132 <li><a href="h_config_role_setsig">PATTERNS ROLE ACTION: Set Signature</a>
4133 <li><a href="h_config_role_settempl">PATTERNS ROLE ACTION: Set Template</a>
4134 <li><a href="h_config_role_usenntp">PATTERNS ROLE ACTION: Use NNTP Server</a>
4135 <li><a href="h_config_role_usesmtp">PATTERNS ROLE ACTION: Use SMTP Server</a>
4136 <li><a href="h_config_role_scoreval">PATTERNS SCORE ACTION: Score Value</a>
4137 <li><a href="h_config_role_scorehdrtok">PATTERNS SCORE ACTION: Score Value From Header</a>
4138 <li><a href="h_config_role_composeuse">PATTERNS USE: Compose Use</a>
4139 <li><a href="h_config_role_forwarduse">PATTERNS USE: Forward Use</a>
4140 <li><a href="h_config_role_replyuse">PATTERNS USE: Reply Use</a>
4141 <li><a href="h_pipe_command">Pipe Command SubOptions</a>
4142 <li><a href="h_common_pipe">Pipe Command</a>
4143 <li><a href="h_valid_folder_names">POP</a>
4144 <li><a href="h_common_postpone">Postpone Command</a>
4145 <li><a href="h_common_print">Print Command</a>
4146 <li><a href="h_mainhelp_readingnews">Reading News</a>
4147 <li><a href="h_news">RELEASE NOTES for Alpine</a>
4148 <li><a href="h_mainhelp_roles">Roles</a>
4149 <li><a href="h_role_select">ROLES SCREEN</a>
4150 <li><a href="h_compose_readfile">Read File Command</a>
4151 <li><a href="h_mainhelp_reading">Reading Messages</a>
4152 <li><a href="h_main_release_notes">Release Notes Command</a>
4153 <li><a href="h_common_reply">Reply and Forward Commands</a>
4154 <li><a href="h_compose_richhdr">Rich Header Command</a>
4155 <li><a href="h_common_role">Role Command</a>
4156 <li><a href="h_mainhelp_smime">S/MIME</a>
4157 <li><a href="h_index_cmd_select">Searching for Messages</a>
4158 <li><a href="h_address_display">SEARCH RESULTS INDEX</a>
4159 <li><a href="h_address_select">SEARCH RESULTS INDEX</a>
4160 <li><a href="h_simple_index">SELECT POSTPONED MESSAGE</a>
4161 <li><a href="h_abook_config">SETUP ADDRESS BOOKS SCREEN</a>
4162 <li><a href="h_collection_maint">SETUP COLLECTION LIST screen</a>
4163 <li><a href="h_color_setup">SETUP COLOR COMMANDS</a>
4164 <li><a href="h_direct_config">SETUP LDAP DIRECTORY SERVERS SCREEN</a>
4165 <li><a href="h_rules_roles">SETUP ROLES SCREEN</a>
4166 <li><a href="h_rules_incols">SETUP INDEX COLORS SCREEN</a>
4167 <li><a href="h_rules_filter">SETUP FILTERING SCREEN</a>
4168 <li><a href="h_rules_score">SETUP SCORING SCREEN</a>
4169 <li><a href="h_common_save">Save and Export Commands</a>
4170 <li><a href="h_mainhelp_securing">Securing Your Alpine Session</a>
4171 <li><a href="h_index_cmd_select">Selecting: Select and WhereIs/Select</a>
4172 <li><a href="h_compose_send">Send Command</a>
4173 <li><a href="h_folder_server_syntax">Server Name Syntax</a>
4174 <li><a href="h_main_setup">Setup Command</a>
4175 <li><a href="X-Alpine-Config:">Show Supported Options in this Alpine</a>
4176 <li><a href="h_composer_sigedit">Signature Editor Commands Explained</a>
4177 <li><a href="h_simple_text_view">Simple Text View Screen Explained</a>
4178 <li><a href="h_mainhelp_smime">S/MIME</a>
4179 <li><a href="h_config_smime_dont_do_smime">S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></a>
4180 <li><a href="h_config_smime_encrypt_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></a>
4181 <li><a href="h_config_smime_remember_passphrase">S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></a>
4182 <li><a href="h_config_smime_sign_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></a>
4183 <li><a href="h_config_smime_use_cert_store">S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></a>
4184 <li><a href="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></a>
4185 <li><a href="h_config_smime_cacertcon">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></a>
4186 <li><a href="h_config_smime_cacertdir">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></a>
4187 <li><a href="h_config_smime_privkeycon">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-container"--></a>
4188 <li><a href="h_config_smime_privkeydir">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-directory"--></a>
4189 <li><a href="h_config_smime_pubcertcon">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-container"--></a>
4190 <li><a href="h_config_smime_pubcertdir">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></a>
4191 <li><a href="h_config_smime_transfer_cacert_to_con">S/MIME: Transfer CA Certs to Container</a>
4192 <li><a href="h_config_smime_transfer_cacert_to_dir">S/MIME: Transfer CA Certs to Directory</a>
4193 <li><a href="h_config_smime_transfer_priv_to_con">S/MIME: Transfer Private Keys to Container</a>
4194 <li><a href="h_config_smime_transfer_priv_to_dir">S/MIME: Transfer Private Keys to Directory</a>
4195 <li><a href="h_config_smime_transfer_pub_to_con">S/MIME: Transfer Public Certs to Container</a>
4196 <li><a href="h_config_smime_transfer_pub_to_dir">S/MIME: Transfer Public Certs to Directory</a>
4197 <li><a href="h_config_smime_public_certificates">S/MIME: Manage Public Certificates</a>
4198 <li><a href="h_config_smime_private_keys">S/MIME: Manage Private Keys</a>
4199 <li><a href="h_config_smime_certificate_authorities">S/MIME: Manage Certificate Authorities</a>
4200 <li><a href="h_index_cmd_sort">Sort Command</a>
4201 <li><a href="h_compose_spell">Spell Check Command</a>
4202 <li><a href="h_common_suspend">Suspend Command</a>
4203 <li><a href="h_compose_addrcomplete">THE MESSAGE COMPOSER'S ADDRESS COMPLETION</a>
4204 <li><a href="h_composer_attachment">THE MESSAGE COMPOSER'S ATTCHMNT FIELD</a>
4205 <li><a href="h_composer_bcc">THE MESSAGE COMPOSER'S BCC FIELD</a>
4206 <li><a href="h_composer_cc">THE MESSAGE COMPOSER'S CC FIELD</a>
4207 <li><a href="h_composer_from">THE MESSAGE COMPOSER'S FROM FIELD</a>
4208 <li><a href="h_composer_lcc">THE MESSAGE COMPOSER'S LCC FIELD</a>
4209 <li><a href="h_composer_news">THE MESSAGE COMPOSER'S NEWSGRPS LINE</a>
4210 <li><a href="h_composer_reply_to">THE MESSAGE COMPOSER'S REPLY-TO FIELD</a>
4211 <li><a href="h_composer_to">THE MESSAGE COMPOSER'S TO FIELD</a>
4212 <li><a href="h_abook_opened">THE ALPINE ADDRESS BOOK</a>
4213 <li><a href="h_abook_select_nicks_take">Take Address Nickname Selection Explained</a>
4214 <li><a href="h_takeaddr_screen">Take Address Screen Explained</a>
4215 <li><a href="h_common_take">TakeAddr Command</a>
4216 <li><a href="h_mainhelp_status">Titlebar Line</a>
4217 <li><a href="h_index_tokens">Tokens for Index and Replying</a>
4218 <li><a href="h_config_usenone_color">Use None Color</a>
4219 <li><a href="h_config_usenormal_color">Use Normal Color</a>
4220 <li><a href="h_config_usetransparent_color">Use Transparent Color</a>
4221 <li><a href="h_whatis_vcard">VCARD EXPLAINED</a>
4222 <li><a href="h_view_cmd_hilite">View Hilite and Next item/Previous item</a>
4223 <li><a href="h_view_cmd_viewattch">ViewAttch Command</a>
4224 <li><a href="h_index_cmd_whereis">WhereIs Command</a>
4225 <li><a href="h_view_cmd_whereis">WhereIs Command</a>
4226 <li><a href="h_index_cmd_zoom">ZoomMode Command</a>
4227 <li><a href="h_config_browser_xterm"><!--#echo var="VAR_url-viewers"--> and X windows applications</a>
4228 </UL>
4230 <P>
4231 <End of Help Index>
4232 </BODY>
4233 </HTML>
4236 ============== h_config_remote_config =============
4237 <HTML>
4238 <HEAD>
4239 <TITLE>Remote Configuration</TITLE>
4240 </HEAD>
4241 <BODY>
4242 <H1>Remote Configuration</H1>
4244 You may use the command line argument "-p pinerc" to tell
4245 Alpine to use a non-default configuration file.
4246 There are two types of storage for configuration information.
4247 <EM>Local</EM> configuration files are used by default.
4248 These are just regular files on the UNIX system or on the PC.
4249 The file "<CODE>.pinerc</CODE>" is the default for Unix Alpine and the
4250 file "<CODE>PINERC</CODE>" is the default for PC-Alpine.
4251 <EM>Remote</EM> configuration folders are stored on an IMAP server.
4252 The advantage of using a remote configuration is that the same information
4253 may be accessed from multiple platforms.
4254 For example, if you use one computer at work and another at home, the same
4255 configuration could be used from both places.
4256 A configuration change from one place would be seen in both places.
4257 To use a remote configuration you simply give a
4258 <A HREF="h_valid_folder_names">remote folder name</A>
4259 as the argument to the "-p" command line option.
4260 The command line might look something like:
4261 <P>
4262 <CENTER><SAMP>pine -p {my.imap.server}remote_pinerc</SAMP></CENTER>
4263 <P>
4264 If there are special characters in the command shell you use, you may need to
4265 quote the last argument (to protect the curly braces from the shell).
4266 The command might look like:
4267 <P>
4268 <CENTER><SAMP>pine -p "{my.imap.server}remote_pinerc"</SAMP></CENTER>
4269 <P>
4270 You should choose a folder name for a folder that does not yet exist.
4271 It will be created containing an empty configuration.
4272 Do not use a folder that you wish to store regular mail messages in.
4273 <P>
4274 The Setup/RemoteConfigSetup command will help you convert from a local
4275 configuration to a remote configuration.
4276 It will create a remote configuration for you and copy your current local
4277 configuration to it.
4278 It will also help you convert local address books into remote address books
4279 and local signature files into literal signatures contained in the
4280 remote configuration file.
4281 <P>
4282 If the Setup/RemoteConfigSetup command doesn't do what you want, you
4283 may copy a local pinerc file to a remote configuration folder by hand
4284 by using the command line option "-copy_pinerc".
4285 <P>
4286 Another command line option, which is somewhat related to remote
4287 configuration, is the option "-x exceptions_config".
4288 The configuration settings in the exceptions configuration override
4289 your default settings.
4290 It may be useful to store the default configuration (the -p argument) remotely
4291 and to have the exceptions configuration stored in a local file.
4292 You might put generic configuration information in the remote configuration
4293 and platform-specific configuration on each platform in the exceptions
4294 configuration.
4295 The arguments to the "-p" and "-x" options
4296 can be either remote folders or local files.
4297 <P>
4298 There is another command line argument that works only with PC-Alpine and
4299 which may prove useful when using a remote configuration.
4300 The option "-aux local_directory" allows you to tell PC-Alpine where
4301 to store your local auxiliary files.
4302 This only has an effect if your configuration file is remote.
4303 Some examples of auxiliary files are debug files, address book files, and
4304 signature files.
4305 <P>
4306 <End of help on this topic>
4307 </BODY>
4308 </HTML>
4309 ============== h_config_exceptions =============
4310 <HTML>
4311 <HEAD>
4312 <TITLE>Generic and Exceptional Configuration</TITLE>
4313 </HEAD>
4314 <BODY>
4315 <H1>Generic and Exceptional Configuration</H1>
4317 If you use Alpine from more than one platform it may be convenient
4318 to split your configuration information into two pieces, a generic piece
4319 and exceptions that apply to a particular platform.
4320 For example, suppose you use Alpine from home and from work.
4321 Most of your configuration settings are probably the
4322 same in both locations, so those settings belong in the generic settings
4323 configuration.
4324 However, you may use a different SMTP server and INBOX
4325 from home than you do from work.
4326 The
4327 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
4328 and
4329 <A HREF="h_config_inbox_path">"<!--#echo var="VAR_inbox-path"-->"</A>
4330 options could be
4331 part of your exceptional configuration so that they could be different in the
4332 two places.
4333 <P>
4334 The command line option "-x exceptions_config"
4335 may be used to split your configuration into generic and exceptional pieces.
4336 "Exceptions_config" may be either local or remote.
4337 The regular Alpine configuration file will contain the generic data, and
4338 "exceptions_config" will contain the exceptional data.
4339 <P>
4340 For Unix Alpine, if you don't have a "-x" command line option,
4341 Alpine will look for the file "<CODE>.pinercex</CODE>"
4342 in the same local directory that the regular config file is located in (usually
4343 the Unix home directory).
4344 If the regular config file is remote (because the command line option
4345 "-p remote_config" was used) then Unix Alpine looks in the Unix home
4346 directory for "<CODE>.pinercex</CODE>".
4347 If the file does not already exist then no exceptions will be used.
4348 You can force exceptions to be used by using the "-x" option or
4349 by creating an empty "<CODE>.pinercex</CODE>" file.
4350 <P>
4351 For PC-Alpine, if you don't have a "-x" command line option,
4352 PC-Alpine will use the value of the
4353 environment variable <CODE>$PINERCEX</CODE>.
4354 If that is not set, PC-Alpine will look for
4355 the local file "<CODE>PINERCEX</CODE>"
4356 in the same local directory that the regular config file is located in.
4357 If the regular config file is remote (because the command line option
4358 "-p remote_config" was used) then PC-Alpine looks in the
4359 local directory specified by the "-aux local_directory" command
4360 line argument, or the directory <CODE>$HOME\PINE</CODE>, or
4361 in the <CODE><PINE.EXE </CODE>directory<CODE>></CODE>.
4362 <P>
4363 When you have an exception configuration there is a new command
4364 in the Alpine Setup screen, Setup/eXceptions.
4365 It toggles between exceptions and the regular configuration.
4366 This is the usual way to make changes in your exceptional configuration data.
4367 For example, you would type "S" for Setup, "X" for
4368 eXception, then follow that with one of the Setup commands, like "C"
4369 for Config or "K" for Kolor.
4370 <P>
4371 For most people, splitting the configuration information into two pieces is
4372 going to be most useful if the generic information is accessed
4373 <A HREF="h_config_remote_config">remotely</A>).
4374 That data will be the same no matter where you access it from and if you
4375 change it that change will show up everywhere.
4376 The exceptional data will most commonly be in a local file, so that the
4377 contents may easily be different on each computing platform used.
4378 <P>
4379 If you already have a local configuration file with settings you like
4380 you may find that the command Setup/RemoteConfigSetup is useful
4381 in helping you convert to a remote configuration.
4382 The command line flag "-copy_pinerc"
4383 may also be useful.
4384 <P>
4385 <End of help on this topic>
4386 </BODY>
4387 </HTML>
4388 ============== h_config_inheritance =============
4389 <HTML>
4390 <HEAD>
4391 <TITLE>Configuration Inheritance</TITLE>
4392 </HEAD>
4393 <BODY>
4394 <H1>Configuration Inheritance</H1>
4396 Configuration inheritance is a power user feature.
4397 It is confusing and not completely supported by the configuration
4398 user interface.
4399 We start with an explanation of how configuration works in hopes of making
4400 it easier to describe how inheritance works.
4401 <P>
4402 Alpine uses a hierarchy of configuration values from different locations.
4403 There are five ways in which each configuration option (configuration
4404 variable) can be set.
4405 In increasing order of precedence they are:
4406 <P>
4407 <OL>
4408 <LI> the system-wide configuration file.
4410 <LI> the personal configuration file
4412 <LI> the personal exceptions file
4414 <LI> a command line argument
4416 <LI> the system-wide <EM>fixed</EM> configuration file (Unix Alpine only)
4417 </OL>
4418 <P>
4419 The fixed configuration file is normally
4420 <CODE><!--#echo var="PINE_CONF_FIXED_PATH"--></CODE>.
4421 <P>
4422 The system-wide configuration file is normally
4423 <CODE><!--#echo var="PINE_CONF_PATH"--></CODE> for Unix Alpine and is normally not
4424 set for PC-Alpine.
4425 For PC-Alpine, if the environment variable <EM>$PINECONF</EM> is set, that
4426 is used for the system-wide configuration.
4427 This location can be set or changed on the command line with the -P flag.
4428 The system-wide configuration file can be either a local file or a
4429 remote configuration folder.
4430 <P>
4431 For Unix Alpine, the personal configuration file is normally the file
4432 <CODE>.pinerc</CODE> in the user's home directory.
4433 This can be changed with the -p command line flag.
4434 For PC-Alpine, the personal configuration file is in
4435 <CODE>$PINERC</CODE> or <CODE><AlpineRC registry value></CODE> or
4436 <CODE>$HOME\PINE\PINERC</CODE> or
4437 <CODE><PINE.EXE </CODE>dir<CODE>>\PINERC</CODE>.
4438 This can be changed with the -p command line flag.
4439 If -p is used, the configuration data may be in a local file or a remote config
4440 folder.
4441 <P>
4442 For Unix Alpine, the personal exceptions configuration file is named
4443 <CODE>.pinercex</CODE> and is in the same directory as the personal
4444 configuration file, if that configuration file is not remote, and is in
4445 the home directory if the personal configuration file is remote.
4446 If the file exists, then exceptions are turned on.
4447 If it doesn't, then you are not using exceptions.
4448 Alternatively, you may change the location of the exceptions configuration
4449 by using the command line argument "-x <exceptions_config>".
4450 Like the personal configuration data, exceptions_config may be
4451 either local or remote.
4452 <P>
4453 For PC-Alpine, the personal exceptions configuration file is named
4454 <CODE>PINERCEX</CODE> and is in the same directory as the personal
4455 configuration file unless the personal configuration file is remote.
4456 In that case, it is in the local directory specfied by the
4457 "-aux local_directory" command line argument.
4458 (In the case that the personal configuration is remote and there is no
4459 "-aux" command line argument, Alpine searches for
4460 a PINERCEX file in the directory <CODE>$HOME\PINE</CODE> and
4461 the directory <CODE><PINE.EXE </CODE>dir<CODE>></CODE>.)
4462 If the file exists, then exceptions are turned on.
4463 If it doesn't, then you are not using exceptions.
4464 You may change the location of the exceptions configuration
4465 by using the command line argument "-x <exceptions_config>".
4466 or with the
4467 environment variable <CODE>$PINERCEX</CODE> (if there is no "-x"
4468 option).
4469 <P>
4470 To reiterate, the value of a configuration option is taken from the
4471 last location in the list above in which it is set.
4472 Or, thinking about it slightly differently, a default value for an option
4473 is established in the system-wide configuration file (or internally by Alpine
4474 if there is no value in the system-wide file).
4475 That default remains in effect until and unless it is overridden by a value in a
4476 location further down the list, in which case a new "default"
4477 value is established.
4478 As we continue down the list of locations we either retain the
4479 value at each step or establish a new value.
4480 The value that is still set after going through the whole list of
4481 configuration locations is the one that is used.
4482 <P>
4483 So, for example, if an option is set in the system-wide configuration
4484 file and in the personal configuration file, but is not set in the
4485 exceptions, on the command line, or in the fixed file; then the value
4486 from the personal configuration file is the one that is used.
4487 Or, if it is set in the system-wide config, in the personal config, not
4488 in the exceptions, but is set on the command line; then the value
4489 on the command line is used.
4490 <P>
4491 Finally we get to inheritance.
4492 For configuration options that are lists, like "<!--#echo var="VAR_smtp-server"-->" or
4493 "<!--#echo var="VAR_incoming-folders"-->",
4494 the inheritance mechanism makes it possible to <EM>combine</EM>
4495 the values from different locations instead of <EM>replacing</EM> the value.
4496 This is true of all configuration lists other than the "Feature-List",
4497 for which you may already set whatever you want at
4498 any configuration location (by using the "no-" prefix if
4499 necessary).
4500 <P>
4501 To use inheritance, set the first item in a configuration list to the
4502 token "INHERIT", without the quotes.
4503 If the first item is "INHERIT",
4504 then instead of replacing the default value established so far, the rest of
4505 the list is appended to the default value established so far and that is
4506 the new value.
4507 <P>
4508 Here is an example which may make it clearer. Suppose we have:
4509 <P>
4510 <PRE>
4511 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4512 Personal config : smtp-server = INHERIT, mysmtp.home
4513 Exceptions config : smtp-server = <No Value Set>
4514 Command line : smtp-server = <No Value Set>
4515 Fixed config : smtp-server = <No Value Set>
4516 </PRE>
4517 <P>
4519 This would result in an effective smtp-server option of
4520 <P>
4521 <PRE>
4522 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home
4523 </PRE>
4524 <P>
4525 The "INHERIT" token can be used in any of the configuration files
4526 and the effect cascades.
4527 For example, if we change the above example to:
4528 <P>
4529 <PRE>
4530 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4531 Personal config : smtp-server = INHERIT, mysmtp.home
4532 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4533 Command line : smtp-server = <No Value Set>
4534 Fixed config : smtp-server = <No Value Set>
4535 </PRE>
4536 <P>
4538 This would result in:
4539 <P>
4540 <PRE>
4541 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home, yoursmtp.org
4542 </PRE>
4543 <P>
4544 Unset variables are skipped over (the default value is carried forward) so
4545 that, for example:
4546 <P>
4547 <PRE>
4548 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4549 Personal config : smtp-server = <No Value Set>
4550 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4551 Command line : smtp-server = <No Value Set>
4552 Fixed config : smtp-server = <No Value Set>
4553 </PRE>
4554 <P>
4556 produces:
4557 <P>
4558 <PRE>
4559 smtp-server = smtp1.corp.com, smtp2.corp.com, yoursmtp.org
4560 </PRE>
4561 <P>
4563 If any later configuration location has a value set (for a particular list
4564 option) which does <EM>not</EM> begin with "INHERIT",
4565 then that value replaces whatever value has been defined up to that point.
4566 In other words, that cancels out any previous inheritance.
4567 <P>
4568 <PRE>
4569 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4570 Personal config : smtp-server = INHERIT, mysmtp.org
4571 Exceptions config : smtp-server = yoursmtp.org
4572 Command line : smtp-server = <No Value Set>
4573 Fixed config : smtp-server = <No Value Set>
4574 </PRE>
4575 <P>
4577 results in:
4578 <P>
4579 <PRE>
4580 smtp-server = yoursmtp.org
4581 </PRE>
4582 <P>
4584 For some configuration options, like "<!--#echo var="VAR_viewer-hdr-colors"-->" or
4585 "<!--#echo var="VAR_patterns-roles"-->", it is
4586 difficult to insert the value "INHERIT" into the list of values
4587 for the option using the normal Setup tools.
4588 In other words, the color setting screen (for example) does not
4589 provide a way to input the text "INHERIT" as the first
4590 item in the <!--#echo var="VAR_viewer-hdr-colors"--> option.
4591 The way to do this is to either edit the pinerc file directly and manually
4592 insert it, or turn
4593 on the <A HREF="h_config_expose_hidden_config"><!--#echo var="FEAT_expose-hidden-config"--></A>
4594 feature and insert it using the Setup/Config screen.
4595 <P>
4596 <End of help on this topic>
4597 </BODY>
4598 </HTML>
4599 ============== h_special_xon_xoff =============
4600 <HTML>
4601 <HEAD>
4602 <TITLE>Explanation of Alpine's XOFF/XON Handling</TITLE>
4603 </HEAD>
4604 <BODY>
4605 <H1>XOFF/XON Handling within Alpine</H1>
4607 By default, Alpine treats Ctrl-S or Ctrl-Q (sometimes known as XOFF
4608 and XON) as normal characters, even though Alpine does not use them.
4609 However, the printer, modem, or communication software you are using may
4610 be configured for "software flow control," which means that
4611 XON/XOFF must be treated as special characters by the operating system.
4612 If you see messages such as "^S not defined for this screen",
4613 then your system is probably using software flow control. In this case
4614 you will need to set the
4615 <A HREF="h_config_preserve_start_stop">"<!--#echo var="FEAT_preserve-start-stop-characters"-->"</A>
4616 feature.
4617 <P>
4618 If you <EM>do</EM> set this
4619 feature, be advised that if you accidentally hit a Ctrl-S, Alpine will
4620 mysteriously freeze up with no warning. In this case, try typing a Ctrl-Q
4621 and see if that puts things right. Printing via the
4622 "attached-to-ansi" or
4623 "attached-to-wyse"
4624 option will automatically enable software
4625 flow-control handling for the duration of the printing.
4626 <P>
4627 <End of help on this topic>
4628 </BODY>
4629 </HTML>
4630 ============= h_special_help_nav =============
4631 <HTML>
4632 <HEAD>
4633 <TITLE>Help Text Navigation Explained</TITLE>
4634 </HEAD>
4635 <BODY>
4636 <H1>Help Text Navigation Explained</H1>
4638 Alpine contains extensive context-sensitive help text. At any point,
4639 pressing the "?" key will bring up a page of help text
4640 explaining the options available to you. You can leave the help
4641 text screen and return to normal Alpine operation by pressing
4642 the
4643 <!--chtml if pinemode="function_key"-->
4644 F3 function
4645 <!--chtml else-->
4646 "E"
4647 <!--chtml endif-->
4648 key to Exit Help at any time.
4650 <P>
4651 Within the help screen you might find a word or phrase displayed in
4652 inverse text and others displayed in bold typeface. Such words and
4653 phrases are used to tell you Alpine has more information available on
4654 the topic they describe.
4655 The inverted text is the "selected" topic.
4656 Use the arrow keys, Ctrl-F, and Ctrl-B to change which of the phrases
4657 displayed in bold type
4658 is "selected".
4659 Hit the Return key to display the information Alpine has available on that
4660 topic. While viewing such additional information, the
4661 <!--chtml if pinemode="function_key"-->
4662 F3 function
4663 <!--chtml else-->
4664 "P"
4665 <!--chtml endif-->
4666 key will return you to the previous help screen, and the
4667 <!--chtml if pinemode="function_key"-->
4668 F2 function
4669 <!--chtml else-->
4670 "E"
4671 <!--chtml endif-->
4672 key will Exit the Help system altogether.
4674 <P>
4675 The "N" command will tell you the internal name of the help text you are
4676 reading each time, so that you can send this name in the text of a message
4677 and create a direct link to that internal help using the x-pine-help URL
4678 scheme. For example, the direct link to this item is
4679 x-pine-help:h_special_help_nav. If you add this text to a message, then
4680 a person using Pine to read such message would have a direct link to this
4681 help text.
4683 <P>
4684 When you are finished reading this help text, you can press the
4685 <!--chtml if pinemode="function_key"-->
4686 F3 function
4687 <!--chtml else-->
4688 "P"
4689 <!--chtml endif-->
4690 key to return to the previously displayed help text.
4692 <P>
4693 <End of help on this topic>
4694 </BODY>
4695 </HTML>
4696 ============= h_special_list_commands =============
4697 <HTML>
4698 <HEAD>
4699 <TITLE>Email List Commands Explained</TITLE>
4700 </HEAD>
4701 <BODY>
4702 <H1>Email List Commands Explained</H1>
4704 Electonic mail lists provide a way for like-minded users to join in
4705 discussions on topics of interest. The email list itself is
4706 represented by a
4707 single address that participants send messages to when they have
4708 something of interest to share with other members of the list. The
4709 receiving computer then, either automatically or after review by the
4710 list's owner (or moderator), sends a copy of that message to each
4711 member of the list.
4713 <P>
4714 Usually, subscribing and unsubscribing is done by sending requests in
4715 an email message to a special address setup to handle managing list
4716 membership. Often this is the name of the list followed by
4717 <I>-request</I>. This address is almost <EM>never</EM> the same as
4718 the address used to send messages to the list.
4720 <P>
4721 Unfortunately, email list participation commands are more a matter
4722 of convention than standard, and thus may vary from list to list.
4723 Increasingly, list management software is adding information to
4724 the copy of the postings as they're copied to the list members that
4725 explains how to do the various list management functions.
4727 <P>
4728 Alpine will recognize this information and offer the management commands
4729 they represent in a simple display. One or more of the following
4730 operations will be made available:
4732 <DL>
4733 <DT>Help</DT>
4734 <DD>
4735 A method to get help on subscribing, unsubscribing,
4736 an explanation of what the list is about, or special instructions
4737 for participation. This may be in the form of a reply in response
4738 to an email message, or instructions on how to connect to a Web site.
4739 </DD>
4741 <DT>Unsubscribe</DT>
4742 <DD>
4743 A method to get your email addressed removed from the list of
4744 recipients of the email list.
4745 </DD>
4747 <DT>Subscribe</DT>
4748 <DD>
4749 A method to get your email address added to the list of recipients
4750 of the email list. It may be in the form of a message sent to
4751 a special address or you may be connected to a web site.
4752 <DD>
4753 </DD>
4755 <DT>Post</DT>
4756 <DD>
4757 A method used to post to the email list. However, it might also
4758 indicate that no posting is allowed directly to the list.
4759 </DD>
4761 <DT>Owner</DT>
4762 <DD>
4763 A method to contact the list owner for special questions you might
4764 have regarding the list.
4765 </DD>
4767 <DT>Archive</DT>
4768 <DD>
4769 A method to view an archive of previous messages posted to the list.
4770 This may be in the form of a mail folder on a remote computer, an
4771 IMAP mailbox or even a Web site.
4772 </DD>
4773 </DL>
4775 <P>
4776 <End of help on this topic>
4777 </BODY>
4778 </HTML>
4779 ============= h_quota_command =============
4780 <HTML>
4781 <HEAD>
4782 <TITLE>Quota Screen Explained</TITLE>
4783 </HEAD>
4784 <BODY>
4785 <H1>Quota Screen Explained</H1>
4787 <P> This screen summarizes the quota report for this mailbox in the
4788 IMAP server. For each resource that you have a quota, this reports summarizes
4789 its use and limit.
4791 <P> Your IMAP server administrator may have set a quota based either on
4792 the total size of your mailbox (STORAGE), or the number of messages in
4793 your mailbox (MESSAGES), or some other criteria. This will be reported
4794 to you indicating the type of quota, its total use and its limit.
4796 <P> The report for STORAGE is reported in kibibytes (KiB). One kibibyte is
4797 1024 bytes. Each of the characters that you see in this help text is one
4798 byte, and this help text is about 1 kibibyte in size. Small messages sent
4799 by Alpine are normally less than 4 kibibytes in size (which includes
4800 headers and text). Other email programs may send messages with bigger
4801 sizes when they send messages, since they send plain text and an
4802 alternative part in HTML.
4804 <P> A convenient way to save space for the STORAGE type of quota is by
4805 deleting attachments. This is done on each individual message by pressing
4806 the "V" command while reading the message text, then moving the cursor
4807 to the position of the attachment that is to be deleted, then pressing
4808 "D" to delete such attachment, going back to reading the
4809 message with the "<" command and pressing "S" to
4810 save the message in the same folder you are reading from. The saved
4811 message will not have the attachment that was marked deleted. Now you
4812 can delete and expunge the message with the unwanted attachment.
4814 <P>
4815 <End of help on this topic>
4816 </BODY>
4817 </HTML>
4818 ============= h_mail_thread_index =============
4819 <HTML>
4820 <HEAD>
4821 <TITLE>THREAD INDEX COMMANDS</TITLE>
4822 </HEAD>
4823 <BODY>
4824 <H1>THREAD INDEX COMMANDS</H1>
4825 <!--chtml if pinemode="function_key"-->
4826 Available Commands -- Group 1 Available Commands -- Group 2<BR>
4827 ------------------------------- -----------------------------<BR>
4828 F1 Show Help Text F1 Show Help Text<BR>
4829 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
4830 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
4831 F4 View current thread F4 Quit Alpine<BR>
4832 F5 Move to previous thread F5 <A HREF="h_common_compose">Compose</A> a message<BR>
4833 F6 Move to next thread F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
4834 F7 Show previous screen F7 <A HREF="h_common_nextnew">Next new</A> thread<BR>
4835 F8 Show next screen F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
4836 F9 <A HREF="h_common_delete">Mark thread for deletion</A> F9 <A HREF="h_common_print">Print</A> index<BR>
4837 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
4838 F11 <A HREF="h_common_reply">Reply</A> to thread F11 <A HREF="h_common_save">Save</A> messages into an email folder<BR>
4839 F12 <A HREF="h_common_reply">Forward</A> messages F12 <A HREF="h_common_save">Export</A> messages into a plain file<BR>
4840 <BR>
4841 Available Commands -- Group 3<BR>
4842 -----------------------------<BR>
4843 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>
4844 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>
4845 F6 F9 <A HREF="h_common_hdrmode">Full Header Mode</A> F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
4846 <BR>
4847 Available Commands -- Group 4<BR>
4848 -----------------------------<BR>
4849 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
4850 F6 <A HREF="h_common_role">Compose using a role</A><BR>
4851 <BR>
4852 <!--chtml else-->
4853 Navigating the List of Threads Operations on the Current Thread<BR>
4854 ------------------------------- ---------------------------------<BR>
4855 P Move to the previous thread > View Thread % <A HREF="h_common_print">Print</A><BR>
4856 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>
4857 - Show previous screen D <A HREF="h_common_delete">Mark thread for deletion</A><BR>
4858 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
4859 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>
4860 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>
4861 specific thread E <A HREF="h_common_save">Export</A> as a plain text file<BR>
4862 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>
4863 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
4864 <BR>
4865 Miscellaneous Operations General Alpine Commands<BR>
4866 ------------------------ ---------------------<BR>
4867 G <A HREF="h_common_goto">Goto</A> a specified folder O Show all other available commands<BR>
4868 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ? Show Helptext Q Quit Alpine<BR>
4869 H <A HREF="h_common_hdrmode">Full header mode</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
4870 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> C <A HREF="h_common_compose">Compose</A> a new message<BR>
4871 Z <A HREF="h_index_cmd_zoom">Zoom</A> # <A HREF="h_common_role">Compose using a role</A><BR>
4872 ; <A HREF="h_index_cmd_select">Select</A> A <A HREF="h_index_cmd_apply">Apply</A> L COLLECTION LIST Screen<BR>
4873 : Select Messages in Current Thread<BR>
4874 <!--chtml endif-->
4875 <P>
4877 NOTE:
4878 <OL>
4879 <LI>For help on a particular command, highlight the bold text associated
4880 with it above and hit Return.
4881 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
4882 </OL>
4884 <H2>Description of the THREAD INDEX Screen</H2>
4886 The THREAD INDEX displays summary information from each
4887 thread (conversation) in the current folder.
4888 This is useful if you want to quickly
4889 scan new threads, or find a particular thread without having to go
4890 through the text of each message, or to quickly get rid of junk
4891 threads, etc.
4892 The current thread is always highlighted.
4893 Each line of the THREAD INDEX contains the following columns: <P>
4894 <DL>
4895 <DT>STATUS:</DT>
4896 <DD> The markings on the left side of the thread tell you about its
4897 status. You may see one or more of the following codes on any given
4898 thread:
4899 <UL>
4900 <LI> "D" for Deleted. All of the messages in this thread are marked for deletion but not yet eXpunged from the folder.
4901 <LI> "A" for Answered. All of the messages in this thread are marked answered.
4902 <LI> "N" for New. At least one message in the thread is New (you haven't looked at it yet).
4903 <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.
4904 <LI> "-" for cc-to-you. The "-" indicates that a
4905 message in the thread was sent to you as a cc:. This symbol will only show up if
4906 the feature
4907 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
4908 <LI> "X" for selected. You have selected at least one message in the thread by using the
4909 "select" command. (Some systems may optionally allow selected
4910 messages to be denoted by the index line being displayed in bold
4911 type instead.)
4912 <LI> "*" for Important. You have previously used the "Flag" command
4913 to mark at least one message in this thread as "important".
4914 </UL></DD><P>
4916 <DT>THREAD NUMBER:</DT>
4917 <DD>Threads in a folder are numbered, from one through the number
4918 of threads in the folder, to help you know where you are in the folder.
4919 </DD><P>
4921 <DT>DATE STARTED:</DT>
4922 <DD>The date the thread was started. This is actually from the Date header
4923 of the first message in the thread. It doesn't take different time zones
4924 into account.</DD><P>
4926 <DT>WHO STARTED THE THREAD:</DT>
4927 <DD>This is usually the name of the sender of the first message in the thread, taken from
4928 the From header of the message.
4929 If there is no personal name given in that
4930 address, then the email address is used instead.
4931 If the message is from you (or from one of your
4932 <A HREF="h_config_alt_addresses">alternate addresses</A>),
4933 then the recipient's name is shown here instead, with the characters
4934 "To: " inserted before the name.
4935 (The idea of this is that if you started the thread you would rather see who
4936 the mail was sent to instead of that the mail was from you.)
4937 In Newsgroups, if you are
4938 the sender and there are no email recipients, the newsgroup name will be
4939 listed after the "To: ".
4940 </DD><P>
4942 <DT>SIZE:</DT>
4943 <DD>The number in parentheses is the number of messages in the thread.</DD><P>
4945 <DT>SUBJECT:</DT>
4946 <DD>As much of the thread's subject line as will fit on the screen.
4947 This is the subject of the first message in the thread.</DD>
4948 </DL>
4950 <P><UL>
4951 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
4952 </UL>
4953 <P>
4954 <End of help on this topic>
4955 </BODY>
4956 </HTML>
4957 ============= h_mail_index =============
4958 <HTML>
4959 <HEAD>
4960 <TITLE>MESSAGE INDEX COMMANDS</TITLE>
4961 </HEAD>
4962 <BODY>
4963 <H1>MESSAGE INDEX COMMANDS</H1>
4964 <!--chtml if pinemode="function_key"-->
4965 Available Commands -- Group 1 Available Commands -- Group 2<BR>
4966 ------------------------------- -----------------------------<BR>
4967 F1 Show Help Text F1 Show Help Text<BR>
4968 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
4969 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
4970 F4 View current message F4 Quit Alpine<BR>
4971 F5 Move to previous message F5 <A HREF="h_common_compose">Compose</A> a message<BR>
4972 F6 Move to next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
4973 F7 Show previous screen of messages F7 <A HREF="h_common_nextnew">Next new</A> message<BR>
4974 F8 Show next screen of messages F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
4975 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
4976 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
4977 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
4978 F12 <A HREF="h_common_reply">Forward</A> message F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
4979 <BR>
4980 Available Commands -- Group 3<BR>
4981 -----------------------------<BR>
4982 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>
4983 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>
4984 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>
4985 <BR>
4986 Available Commands -- Group 4<BR>
4987 -----------------------------<BR>
4988 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
4989 F6 <A HREF="h_common_role">Compose using a role</A> F10 <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread<BR>
4990 <BR>
4991 <!--chtml else-->
4992 Navigating the List of Messages Operations on the Current Message<BR>
4993 ------------------------------- ---------------------------------<BR>
4994 P Move to the previous message > View % <A HREF="h_common_print">Print</A><BR>
4995 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>
4996 - Show previous screen of messages D <A HREF="h_common_delete">Mark for deletion</A><BR>
4997 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
4998 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>
4999 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>
5000 specific message E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5001 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>
5002 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
5003 Miscellaneous Operations<BR>
5004 ------------------------<BR>
5005 G <A HREF="h_common_goto">Goto</A> a specified folder General Alpine Commands<BR>
5006 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ---------------------<BR>
5007 H <A HREF="h_common_hdrmode">Full header mode</A> O Show all other available commands<BR>
5008 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> ? Show Help text Q Quit Alpine<BR>
5009 Z <A HREF="h_index_cmd_zoom">Zoom</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5010 ; <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>
5011 : Select Current message # <A HREF="h_common_role">Compose using a role</A><BR>
5012 / <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread L COLLECTION LIST Screen<BR>
5013 <!--chtml endif-->
5014 <P>
5016 NOTE:
5017 <OL>
5018 <LI>For help on a particular command, highlight the bold text associated
5019 with it above and hit Return.
5020 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5021 </OL>
5023 <H2>Description of the MESSAGE INDEX Screen</H2>
5025 The MESSAGE INDEX displays summary information from each
5026 message in the current folder.
5027 This is useful if you want to quickly
5028 scan new messages, or find a particular message without having to go
5029 through the text of each message, or to quickly get rid of junk
5030 messages, etc.
5031 <P>
5032 The current message is always highlighted
5033 and many commands operate on the current message.
5034 For example, the Delete command will delete the current message.
5035 If the folder is sorted by either Threads or OrderedSubject, then, depending
5036 on some of your configuration settings, a single line in the index may
5037 refer to an entire thread or to a subthread.
5038 If that is the case, then the commands that normally operate on the current
5039 message will operate on the thread or subthread instead.
5040 For example, the Delete command will delete the whole collapsed thread
5041 instead of just a single message.
5042 <P>
5043 Each line of the MESSAGE INDEX contains the following columns (by default --
5044 you can change this with the
5045 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
5046 in the SETUP CONFIGURATION screen): <P>
5047 <DL>
5048 <DT>STATUS:</DT>
5049 <DD> The markings on the left side of the message tell you about its
5050 status. You may see one or more of the following codes on any given
5051 message:
5052 <UL>
5053 <LI> "D" for Deleted. You have marked this message for deletion but not
5054 yet eXpunged the folder.
5055 <LI> "N" for New. You have not looked at the text of the message yet.
5056 <LI> "A" for Answered. Any time you reply to a message it is considered
5057 to be answered.
5058 <LI> "F" for Forwarded. Similar to Answered, this is set whenever you
5059 forward a message.
5060 <LI> "+" for direct-to-you. The "+" indicates that a message was sent
5061 directly to your account, your copy is not part of a cc: or a
5062 mailing list.
5063 <LI> "-" for cc-to-you. The "-" indicates that a
5064 message was sent to you as a cc:. This symbol will only show up if
5065 the feature
5066 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
5067 <LI> "X" for selected. You have selected the message by using the
5068 "select" command. (Some systems may optionally allow selected
5069 messages to be denoted by the index line being displayed in bold
5070 type.)
5071 <LI> "*" for Important. You have previously used the "Flag" command
5072 to mark this message as "important".
5073 </UL></DD><P>
5075 <DT>MESSAGE NUMBER:</DT>
5076 <DD>Messages in a folder are numbered, from one through the number
5077 of messages in the folder, to help you know where you are in the folder.
5078 These numbers are always in increasing order, even if you sort the folder
5079 in a different way.</DD><P>
5081 <DT>DATE SENT:</DT>
5082 <DD>The date the message was sent. By default, messages are
5083 ordered by arrival time, not by date sent. Most of the time, arrival time
5084 and date sent (effectively departure time) are similar. Sometimes,
5085 however, the index will appear to be out of order because a message took a
5086 long time in delivery or because the sender is in a different time
5087 zone than you are. This date is just the date from the Date header
5088 field in the message.</DD><P>
5090 <DT>WHO SENT THE MESSAGE:</DT>
5091 <DD>This is usually the name of the sender of the message, taken from
5092 the From header of the message.
5093 If there is no personal name given in that
5094 address, then the email address is used instead.
5095 If the message is from you (or from one of your
5096 <A HREF="h_config_alt_addresses">alternate addresses</A>),
5097 then the recipient's name is shown here instead, with the characters
5098 "To: " inserted before the name.
5099 (The idea of this is that if you sent the mail you would rather see who
5100 the mail was sent to instead of that the mail was from you.
5101 This behavior may be changed by modifying the <!--#echo var="VAR_index-format"--> option mentioned
5102 above.
5103 In particular, use the FROM token or the FROMORTONOTNEWS token
5104 in place of the FROMORTO token.)
5105 In Newsgroups, if you are
5106 the sender and there are no email recipients, the newsgroup name will be
5107 listed after the "To: ". </DD><P>
5109 <DT>SIZE:</DT>
5110 <DD>The number in parentheses is the number of characters in the message.
5111 It may have a suffix of K, M, or G which means the number should be
5112 multiplied by one thousand, one million, or one billion to get the
5113 size of the message.</DD><P>
5115 <DT>SUBJECT:</DT>
5116 <DD>As much of the message's subject line as will fit on the screen.</DD>
5117 </DL>
5119 <P><UL>
5120 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5121 </UL>
5122 <P>
5123 <End of help on this topic>
5124 </BODY>
5125 </HTML>
5126 ============= h_mail_view ========================
5127 <HTML>
5128 <HEAD>
5129 <TITLE>MESSAGE TEXT SCREEN</TITLE>
5130 </HEAD>
5131 <BODY>
5132 <H1>MESSAGE TEXT SCREEN</H1>
5133 <!--chtml if pinemode="function_key"-->
5134 Available Commands -- Group 1 Available Commands -- Group 2<BR>
5135 ------------------------------- ------------------------------<BR>
5136 F1 Show Help Text F1 Show Help Text<BR>
5137 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
5138 F3 <A HREF="h_common_index">MESSAGE INDEX</A> Screen F3 MAIN MENU Screen<BR>
5139 F4 <A HREF="h_view_cmd_viewattch">View attachment</A> F4 Quit Alpine<BR>
5140 F5 Display previous message F5 <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5141 F6 Display next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5142 F7 Previous screen of this message F7 <A HREF="h_common_compose">Compose</A> message<BR>
5143 F8 Next screen of this message F8 <A HREF="h_view_cmd_whereis">Whereis</A><BR>
5144 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
5145 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
5146 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
5147 F12 <A HREF="h_common_reply">Forward</A> F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
5148 <BR>
5149 Available Commands -- Group 3<BR>
5150 ------------------------------<BR>
5151 F1 Show Help Text<BR>
5152 F2 Toggle to see more commands<BR>
5153 F3 <A HREF="h_view_cmd_hilite">View hilited</A><BR>
5154 F4 Select current message<BR>
5155 F5 Previous selectable item<BR>
5156 F6 Next selectable item<BR>
5157 F7 <A HREF="h_common_jump">Jump</A> to message number<BR>
5158 F8 <A HREF="h_common_nextnew">Next new</A> message<BR>
5159 F9 <A HREF="h_common_hdrmode">Display full headers</A><BR>
5160 F10 <A HREF="h_common_bounce">Bounce</A> message<BR>
5161 F11 <A HREF="h_common_flag">Flag</A> message<BR>
5162 F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
5163 Available Commands -- Group 4<BR>
5164 F5 <A HREF="h_common_role">Compose using a role</A><BR>
5165 <!--chtml else-->
5166 Operations on the Current Message<BR>
5167 ---------------------------------<BR>
5168 <BR>
5169 - Show previous page of this msg S <A HREF="h_common_save">Save</A> into an email folder<BR>
5170 Spc (space bar) Show next page E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5171 > <A HREF="h_view_cmd_viewattch">View attachment</A> B <A HREF="h_common_bounce">Bounce</A><BR>
5172 R <A HREF="h_common_reply">Reply</A> to message F <A HREF="h_common_reply">Forward</A> message<BR>
5173 D <A HREF="h_common_delete">Mark for deletion</A> Ret View <A HREF="h_view_cmd_hilite">hilited</A> item<BR>
5174 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>
5175 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>
5176 % <A HREF="h_common_print">Print</A> * <A HREF="h_common_flag">Flag</A> message<BR>
5177 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>
5178 <BR>
5179 Navigating the List of Messages Other Commands<BR>
5180 ------------------------------- ----------------------------<BR>
5181 P Display previous message G <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5182 N Display next message H <A HREF="h_common_hdrmode">Full header mode</A> on/off<BR>
5183 J <A HREF="h_common_jump">Jump</A> to a specific message : Select Current message<BR>
5184 Tab <A HREF="h_common_nextnew">Next new</A> message A <A HREF="h_config_prefer_plain_text">Toggle Prefer Plain Text</A><BR>
5185 <BR>
5186 General Alpine Commands<BR>
5187 ---------------------<BR>
5188 O Show all other available commands<BR>
5189 ? Show Help text Q Quit Alpine<BR>
5190 M MAIN MENU Screen L <A HREF="h_common_folders">FOLDER LIST</A> Screen (or COLLECTION LIST Screen)<BR>
5191 < <A HREF="h_common_index">MESSAGE INDEX</A> Screen C <A HREF="h_common_compose">Compose</A> a new message<BR>
5192 # <A HREF="h_common_role">Compose using a role</A><BR>
5193 <!--chtml endif-->
5194 <P>
5196 NOTE:
5197 <OL>
5198 <LI>For help on a particular command, highlight the bold text associated
5199 with it above and hit Return.
5200 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5201 </OL>
5203 <H2>Description of the MESSAGE TEXT Screen</H2>
5205 The top line of the view message screen displays status
5206 information about the currently open collection and folder and about the
5207 current message. It shows the name of the collection in angle brackets
5208 and then the name of the folder. The line also displays the number
5209 of messages in the folder, the number of the current message and the
5210 percentage of the current message that has been displayed on the screen.
5211 If the message is marked for deletion "DEL" will appear in the upper
5212 right corner.
5213 If the message has been answered (but not deleted) "ANS" will show
5214 in the corner.
5215 <P>
5217 NOTE: to rapidly move to the end of a message, hit the
5218 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5219 (or Ctrl-W) key followed
5220 by Ctrl-V. Similarly,
5221 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5222 followed by Ctrl-Y will take you to the beginning of
5223 a message.
5225 <H2>Explanation of Alternate Character Sets</H2>
5227 Alpine attempts to stay out of the way so that it won't prevent you from
5228 viewing mail in any character set. It will simply send the message to
5229 your display device. If the device is capable of displaying the
5230 message as it was written it will do so. If not, the display may be
5231 partially or totally incorrect.
5232 If the message contains characters that are not representable in your
5233 <A HREF="h_config_char_set">"Display Character Set"</A>
5234 variable in your configuration, then a warning message will be printed
5235 to your screen at the beginning of the message display.
5236 It is probably best to use UNIX Alpine in a terminal emulator
5237 capable of displaying UTF-8 characters.
5238 See <A HREF="h_config_char_set">Display Character Set</A> for a little
5239 more information about character set settings.
5241 <P><UL>
5242 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5243 </UL>
5244 <P>
5245 <End of help on this topic>
5246 </BODY>
5247 </HTML>
5248 ======= h_index_cmd_select =======
5249 <HTML>
5250 <HEAD>
5251 <TITLE>Selecting: Select and WhereIs/Select</TITLE>
5252 </HEAD>
5253 <BODY>
5254 <H1>Selecting: Select and WhereIs/Select</H1>
5256 Aggregate operations give you the ability to process a group of messages
5257 at once. Acting on multiple messages requires two steps: (1) selecting a
5258 set of messages and then; (2) applying a command to that set. The first
5259 part is handled by the select command. Select allows you to
5260 select messages based on their status (read, answered, etc.), contents,
5261 date, size, or keywords.
5262 You may also select based on one of your Rules or based on threads,
5263 and there are quick options to select a specific message or range of messages,
5264 to select the current message, or to select all messages.
5265 <P>
5267 We describe the various selection criteria briefly:
5268 <P>
5270 <DL>
5271 <DT>select All</DT>
5272 <DD> Marks all the messages in the folder as selected.
5273 </DD>
5275 <DT>select Cur</DT>
5276 <DD> Selects the currently highlighted message or currently highlighted
5277 set of messages if in a threaded view.
5278 </DD>
5280 <DT>select by Number</DT>
5281 <DD> Select by message number. This may be a comma-separated list instead or
5282 a single entry.
5283 Each element in the list may be either a single message number or a range
5284 of numbers with a dash between the lowest and highest member of the range.
5285 Some examples are 7 to select only message number 7; 2-5 to select messages
5286 2 through 5; and 2-5,7-9,11 to select messages 2, 3, 4, 5, 7, 8, 9, and 11.
5287 The word "end" may be used as a substitute for the highest numbered
5288 message in the folder.
5289 If in a separate thread index where the numbers refer to threads instead of
5290 to messages, then you will be selecting all of the messages in the
5291 referenced threads instead of selecting by message number.
5292 </DD>
5294 <DT>select by Date</DT>
5295 <DD> Select by either the date stored in the Date headers of each message,
5296 or by the date when the messages arrived.
5297 This does not adjust for different time zones, but just checks to see what
5298 day the message was sent on.
5299 You may type in a date. If you do, the date should be in the form
5300 <P><SAMP><CENTER>DD-Mon-YYYY</CENTER></SAMP><P>
5301 For example,
5302 <P><SAMP><CENTER>24-Nov-2004</CENTER></SAMP><P>
5303 or
5304 <P><SAMP><CENTER>09-Nov-2004</CENTER></SAMP><P>
5305 If the date you want is close to the current date, it is probably
5306 easier to use the "^P Prev Day" or "^N Next Day" commands to change the default date that
5307 is displayed, instead of typing in the date yourself.
5308 Or, the "^X Cur Msg" command may be used to fill in
5309 the date of the currently highlighted message.
5310 <P>
5311 There are six possible settings that are selected using the
5312 "^W Toggle When" command.
5313 Three of them select messages based on the Date headers.
5314 They are "SENT SINCE", "SENT BEFORE",
5315 and "SENT ON".
5316 SINCE is all messages with the selected date or later.
5317 BEFORE is all messages earlier than the selected date (not including the day
5318 itself).
5319 ON is all messages sent on the selected date.
5320 The other three select messages in the same way but they use the arrival
5321 times of the messages instead of the Date headers included in the messages.
5322 Those three are "ARRIVED SINCE", "ARRIVED BEFORE",
5323 and "ARRIVED ON".
5324 When you save a message from one folder to another the arrival time is
5325 preserved.
5326 </DD>
5328 <DT>select by Text</DT>
5329 <DD> Selects messages based on the message contents.
5330 This allows you to select a set of messages based on whether or not the
5331 message headers or message body contain specified text.
5332 You may look for text in the Subject, the From header,
5333 the To header, or the Cc header.
5334 You may also choose Recipient, which searches for the text in
5335 either the To or the Cc header;
5336 or Participant, which means To or Cc or From.
5337 Besides those specific header searches, you may also search the entire
5338 header and text of the message with "All Text", or just the
5339 body of the message.
5340 <P>
5341 To search for the absence of text, first type the "! Not" command
5342 before typing the specific type of text search.
5343 For example, you could type "!" followed by "S" to
5344 search for all messages that do not contain a particular word in their
5345 Subjects.
5346 <P>
5347 If you choose a Subject search, you may use the subject from the current
5348 message by typing the "^X Cur Subject" command.
5349 You may then edit it further if you wish.
5350 For example, you might select the subject of a reply and edit the
5351 "Re: " off of the front of it in order to search for
5352 the original message being replied to.
5353 All of the other header searches allow you to use addresses from the
5354 headers of the current message if you want to.
5355 You may use the "^T Cur To", "^R Cur From", or
5356 "^W Cur Cc".
5357 In each case, if there is more than one address, only the first is offered.
5358 </DD>
5360 <DT>select by Status</DT>
5361 <DD> Selects messages based on their status.
5362 You may select all New, Important, Deleted, Answered, Recent, or Unseen
5363 messages.
5364 Or, if you first type the "! Not" command, you get not New,
5365 or not Important, and so on.
5366 If you select Deleted messages, you will get all messages with their
5367 Deleted flag set.
5368 Likewise for Important messages, all messages that you have flagged as
5369 being Important with the
5370 <A HREF="h_common_flag">Flag</A> command.
5371 The "New" and "Answered" choices are a little bit odd
5372 because they try to match what you see on the screen by default.
5373 "New" is a shorthand for messages that are Unseen, Undeleted,
5374 and Unanswered.
5375 If you have looked at the message, or deleted it, or answered it; then it
5376 is not considered "New ".
5377 "! New" is the opposite of "New".
5378 <P>
5379 "Answered" is another one that is a little different.
5380 It means that the message has been Answered <EM>and</EM> is not deleted.
5381 And to make it even more confusing, "! Answered" is not
5382 the opposite of "Answered"!
5383 Instead, "! Answered" stands for messages that are
5384 both Unanswered <EM>and</EM> not deleted.
5385 <P>
5386 The other two types were added later because the special nature of the
5387 New flag was not what was wanted by all users.
5388 New does match what you see in the index by default, but if you use
5389 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5390 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5391 be exactly what you want.
5392 "Unseen" simply selects all unseen messages, whether or not
5393 they are deleted or answered, and
5394 "Recent" selects all of the messages that have been added to
5395 the folder since you started this Alpine session.
5396 (That's not technically quite true. If there are multiple mail clients
5397 reading an IMAP mailbox, each message will be marked as Recent in only
5398 one of the client's sessions.)
5399 </DD>
5401 <DT>select by siZe</DT>
5402 <DD> Selects messages based on their size being smaller than or larger
5403 than the size you specify.
5404 The size is the number of bytes.
5405 You may use the suffix "K" or "k" to mean 1,000 times
5406 the number.
5407 For example, 7K is the same as 7000.
5408 The suffix "M" or "m" means 1,000,000 times the number,
5409 and the suffix "G" or "g" means 1,000,000,000 times.
5410 Use the "^W" command to toggle back and forth between Smaller
5411 and Larger.
5412 </DD>
5414 <DT>select by Keyword</DT>
5415 <DD> Selects messages that either have or do not have
5416 (using the "! Not" command)
5417 a particular <A HREF="h_config_keywords">Keyword</A> set.
5418 One way to select a keyword is to use the "^T To List"
5419 command to select one from your list of keywords.
5420 The
5421 <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.
5422 </DD>
5424 <DT>select by Rule</DT>
5425 <DD> Selects messages that either match or don't match
5426 (using the "! Not" command)
5427 one of the Rules you have defined.
5428 The most likely method of filling in the Rule is to use the
5429 "^T To List"
5430 command to select one of your Rules.
5431 All of the Rules you have defined will be in the list, including
5432 Rules for Searching, Indexcolors, Filtering, Roles, Score setting, and Other.
5433 They may not all make sense for this purpose, but they are all there for
5434 flexibility.
5435 You might find it useful to define some rules solely for the purpose
5436 of being used by the Select command.
5437 There is a special category for such Rules. They are called Search Rules.
5438 <P>
5439 Unfortunately, Alpine does not allow all possible Rules to be defined.
5440 For example, there is no logical OR operation.
5441 OR is accomplished in the Filter Rules or the other types of Rules by
5442 simply defining two rules, one that matches the first part of the OR
5443 and another that matches the second part.
5444 But you can't do that here, since you only have a single Rule to work with.
5445 Likewise, the order of Rules is usually important.
5446 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5447 a message, then that stops the search for a further match.
5448 This means that you may be confused if you try to use Select by Rule to
5449 check your Filter rules because the order is important when filtering but
5450 is not considered here.
5451 </DD>
5453 <DT>select by tHread</DT>
5454 <DD> Selects all of the messages in the current thread.
5455 </DD>
5456 </DL>
5458 After you have an initial selection, the next and subsequent selection
5459 commands modify the selection.
5460 The select command changes. It first gives
5461 you selection "alteration" options: "unselect All",
5462 "unselect Current",
5463 "Broaden selection" (implements a logical OR), and
5464 "Narrow selection" (implements a logical AND).
5465 After you choose either Broaden or Narrow, you then choose one of the
5466 selection criteria listed above (by Text or Number or ...).
5467 You may use select as many times as you wish to get the selected set right.
5468 <P>
5470 The WhereIs command has a feature (Ctrl-X) to
5471 select all the messages that match the WhereIs search. WhereIs searches
5472 through just the text that appears on the MESSAGE INDEX screen.
5473 This method is often slower than using the select command itself, unless the
5474 line you are looking for is not too far away in the index.
5475 <P>
5477 The availability of the aggregate operations commands is determined by the
5478 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
5479 Feature-List option in your Alpine
5480 configuration, which defaults to set.
5481 The features
5482 <A HREF="h_config_auto_zoom">"<!--#echo var="FEAT_auto-zoom-after-select"-->"</A>
5483 and
5484 <A HREF="h_config_select_wo_confirm">"<!--#echo var="FEAT_select-without-confirm"-->"</A>
5485 affect the behavior of the Select command.
5487 <P>
5488 <End of help on this topic>
5489 </BODY>
5490 </HTML>
5491 ======= h_select_rule =======
5492 <HTML>
5493 <HEAD>
5494 <TITLE>Select: Rule</TITLE>
5495 </HEAD>
5496 <BODY>
5497 <H1>Select: Rule</H1>
5499 You are selecting messages that either match or don't match
5500 one of the Rules you have defined.
5501 You may either type the nickname of the Rule at the prompt, or use the
5502 "^T To List"
5503 command to select one of your Rules.
5504 All of the Rules you have defined will be in the list, including
5505 Rules for Indexcolors, Filtering, Roles, Score setting, and Other.
5506 They may not all make sense for this purpose, but they are all there for
5507 flexibility.
5508 Rules may be added by using the Setup/Rules screen off of the main Alpine
5509 menu.
5510 <P>
5511 Unfortunately, Alpine does not allow all possible Rules to be defined.
5512 For example, there is no logical OR operation.
5513 OR is accomplished in the Filter Rules or the other types of Rules by
5514 simply defining two rules, one that matches the first part of the OR
5515 and another that matches the second part.
5516 But you can't do that here, since you only have a single Rule to work with.
5517 Likewise, the order of Rules is usually important.
5518 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5519 a message, then that stops the search for a further match.
5520 This means that you may be confused if you try to use Select by Rule to
5521 check your Filter rules because the order is important when filtering but
5522 is not considered here.
5524 <P>
5525 <End of help on this topic>
5526 </BODY>
5527 </HTML>
5528 ======= h_select_text =======
5529 <HTML>
5530 <HEAD>
5531 <TITLE>Select: Text</TITLE>
5532 </HEAD>
5533 <BODY>
5534 <H1>Select: Text</H1>
5536 You are selecting messages based on the contents of the message.
5537 This allows you to select a set of messages based on whether or not the
5538 message headers or message body contain specified text.
5539 You may look for text in the Subject, the From header,
5540 the To header, or the Cc header.
5541 You may also choose Recipient, which searches for the text in
5542 either the To or the Cc header;
5543 or Participant, which means either the To header, or the Cc header,
5544 or the From header.
5545 Besides those specific header searches, you may also search the entire
5546 header and text of the message with "All Text", or just the
5547 body of the message with "Body".
5548 <P>
5549 To search for the absence of text, first type the "! Not" command
5550 before typing the specific type of text search.
5551 For example, you could type "!" followed by "S" to
5552 search for all messages that do not contain a particular word in their
5553 Subjects.
5554 <P>
5555 If you choose a Subject search, you may use the subject from the current
5556 message by typing the "^X Cur Subject" command.
5557 You may then edit it further if you wish.
5558 For example, you might select the subject of a reply and edit the
5559 "Re: " off of the front of it in order to search for
5560 the original message being replied to.
5561 All of the other header searches allow you to use addresses from the
5562 headers of the current message if you want to.
5563 You may use the "^T Cur To", "^R Cur From", or
5564 "^W Cur Cc".
5565 In each case, if there is more than one address, only the first is offered.
5567 <P>
5568 <End of help on this topic>
5569 </BODY>
5570 </HTML>
5571 ======= h_select_status =======
5572 <HTML>
5573 <HEAD>
5574 <TITLE>Select: Status</TITLE>
5575 </HEAD>
5576 <BODY>
5577 <H1>Select: Status</H1>
5579 You are selecting messages based on the status of the message.
5580 For example, whether or not the message has been marked Deleted or Important,
5581 or whether or not it has been Answered or is New.
5582 If you first type the "! Not" command, you will get the
5583 opposite: not Deleted, not Important, and so on.
5584 <P>
5585 If you select Deleted messages, you will get all messages with their
5586 Deleted flag set.
5587 Likewise for Important messages, all messages that you have flagged as
5588 being Important with the
5589 <A HREF="h_common_flag">Flag</A> command.
5590 The "New" and "Answered" choices are a little bit odd
5591 because they try to match what you see on the screen by default.
5592 "New" is a shorthand for messages that are Unseen, Undeleted,
5593 and Unanswered.
5594 If you have looked at the message, or deleted it, or answered it; then it
5595 is not considered "New ".
5596 "! New" is the opposite of "New".
5597 <P>
5598 "Answered" is another one that is a little different.
5599 It means that the message has been Answered <EM>and</EM> is not deleted.
5600 And to make it even more confusing, "! Answered" is not
5601 the opposite of "Answered"!
5602 Instead, "! Answered" stands for messages that are
5603 both Unanswered <EM>and</EM> not deleted.
5604 <P>
5605 (The New and Answered options may seem counter-intuitive.
5606 The reason it is done this way is
5607 because, by default, a Deleted message will show up with the "D"
5608 symbol in the MAIL INDEX screen even if it is New or Answered.
5609 The Delete symbol overrides the New and Answered symbols, because you
5610 usually don't care about the message anymore once you've deleted it.
5611 Similarly, you usually only care about whether a message is Answered or
5612 not if it is not Deleted.
5613 Once it is Deleted you've put it out of your mind.)
5614 <P>
5615 The other two options were added later because the special nature of the
5616 New flag was not what was wanted by all users.
5617 New does match what you see in the index by default, but if you use
5618 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5619 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5620 be exactly what you expect.
5621 "Unseen" simply selects all unseen messages, whether or not
5622 they are deleted or answered, and
5623 "Recent" selects all of the messages that have been added to
5624 the folder since you started this Alpine session.
5625 (That's not technically quite true. If there are multiple mail clients
5626 reading an IMAP mailbox, each message will be marked as Recent in only
5627 one of the client's sessions.
5628 That behavior can be convenienent for some purposes, like filtering, but
5629 it isn't usually what you expect when selecting.)
5631 <P>
5632 <End of help on this topic>
5633 </BODY>
5634 </HTML>
5635 ======= h_index_cmd_apply =======
5636 <HTML>
5637 <HEAD>
5638 <TITLE>Apply Command</TITLE>
5639 </HEAD>
5640 <BODY>
5641 <H1>Apply Command</H1>
5643 Apply
5644 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->A<!--chtml endif-->)
5645 is the second step of most aggregate operations. Apply
5646 becomes active any time there is a defined set of selected messages. The
5647 following commands can be applied to a selected message set: delete,
5648 undelete, reply, forward,
5649 <!--chtml if pinemode="os_windows"-->
5650 <!--chtml else-->
5651 pipe,
5652 <!--chtml endif-->
5653 print, take address, save, export, bounce, and flag.
5654 <P>
5656 The behavior of some of these commands in an aggregate sense is not easy to
5657 explain. Try them out to see what they do.
5658 The feature
5659 <A HREF="h_config_auto_unzoom">"<!--#echo var="FEAT_auto-unzoom-after-apply"-->"</A>
5660 affects the behavior of the Apply command, as does the feature
5661 <A HREF="h_config_auto_unselect">"<!--#echo var="FEAT_auto-unselect-after-apply"-->"</A>.
5663 <P>
5664 <End of help on this topic>
5665 </BODY>
5666 </HTML>
5667 ======= h_index_cmd_zoom =======
5668 <HTML>
5669 <HEAD>
5670 <TITLE>ZoomMode Command</TITLE>
5671 </HEAD>
5672 <BODY>
5673 <H1>ZoomMode Command</H1>
5675 Another action you might want to take on a set of selected messages is to
5676 zoom in on them. Like apply, zoom only becomes active when messages have
5677 been selected.
5678 ZoomMode
5679 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->Z<!--chtml endif-->)
5680 is a toggle command that allows you to
5681 zoom-in (and only see the selected messages) and zoom-out (to see all
5682 messages in the folder). Neither apply nor zoom removes the markings that
5683 define the selected set; you need to use a select command in order
5684 to do that.
5686 <P>
5687 <End of help on this topic>
5688 </BODY>
5689 </HTML>
5690 ======= h_index_collapse_expand =======
5691 <HTML>
5692 <HEAD>
5693 <TITLE>Collapse/Expand Command</TITLE>
5694 </HEAD>
5695 <BODY>
5696 <H1>Collapse/Expand Command</H1>
5698 The Collapse/Expand command is only available from the MESSAGE INDEX screen when
5699 the folder is sorted by either Threads or OrderedSubject, and the
5700 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
5701 is set to something other than "none".
5702 By default, this command collapses or expands the subthread that starts at
5703 the currently highlighted message, if any.
5704 If the subthread is already collapsed, then this command expands it.
5705 If the subthread is expanded, then this command collapses it.
5706 If there are no more messages below the current message in the
5707 thread tree (that is, there are no replies to the current message) then
5708 this command does nothing.
5710 <P>
5711 The behavior of this command is affected by the option
5712 <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>.
5713 Normally, this command Collapses or Expands the subthread that
5714 starts at the currently highlighted message.
5715 If the above option is set, then this command Collapses or Expands the
5716 entire current thread instead of just the subthread.
5717 The current thread is simply the top-level thread that contains the
5718 current message.
5720 <P>
5721 <End of help on this topic>
5722 </BODY>
5723 </HTML>
5724 ======= h_index_cmd_sort =======
5725 <HTML>
5726 <HEAD>
5727 <TITLE>Sort Command</TITLE>
5728 </HEAD>
5729 <BODY>
5730 <H1>Sort Command</H1>
5732 In Alpine's generic configuration, messages are presented in the order in
5733 which they arrive. This default can be changed in the SETUP CONFIGURATION
5734 with the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
5735 You can also re-sort the folder on demand with the sort
5736 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
5737 command.
5738 Your sorting options are:
5739 <P>
5740 <UL>
5741 <LI> <A HREF="h_index_sort_arrival">A</A>rrival
5742 <LI> <A HREF="h_index_sort_date">D</A>ate
5743 <LI> <A HREF="h_index_sort_subj">S</A>ubject
5744 <LI> <A HREF="h_index_sort_ordsubj">O</A>rderedSubject
5745 <LI> t<A HREF="h_index_sort_thread">H</A>read
5746 <LI> <A HREF="h_index_sort_from">F</A>rom
5747 <LI> si<A HREF="h_index_sort_size">Z</A>e
5748 <LI> scor<A HREF="h_index_sort_score">E</A>,
5749 <LI> <A HREF="h_index_sort_to">T</A>o
5750 <LI> <A HREF="h_index_sort_cc">C</A>c
5751 </UL>
5753 <P>
5754 The Reverse option will toggle the order the index is currently
5755 sorted by, but will not change the relative sort order.
5757 <P>
5758 Sorting a folder does not actually rearrange the way the folder is saved,
5759 it just re-arranges how the messages are presented to you. This means
5760 that Alpine has to do the work of sorting every time you change sort order.
5761 Sometimes, especially with PC-Alpine or with large folders, this could take
5762 a while.
5764 <P>
5765 <End of help on this topic>
5766 </BODY>
5767 </HTML>
5768 ======= h_index_sort_default =======
5769 <HTML>
5770 <HEAD>
5771 <TITLE>SORT OPTION: Default</TITLE>
5772 </HEAD>
5773 <BODY>
5774 <H1>SORT OPTION: Default</H1>
5776 The <EM>Default</EM> sort option just means to use the default sort order
5777 set in the
5778 <li><a href="h_config_sort_key"><!--#echo var="VAR_sort-key"--></a>
5779 option in Setup/Config.
5781 <P>
5782 <End of help on this topic>
5783 </BODY>
5784 </HTML>
5785 ======= h_index_sort_arrival =======
5786 <HTML>
5787 <HEAD>
5788 <TITLE>SORT OPTION: Arrival</TITLE>
5789 </HEAD>
5790 <BODY>
5791 <H1>SORT OPTION: Arrival</H1>
5793 The <EM>Arrival</EM> sort option arranges messages in the MESSAGE INDEX
5794 in the order that they exist in the folder. This is usually the same as the
5795 order in which they arrived. This option is comparable to not sorting
5796 the messages at all.
5798 <P>
5799 <End of help on this topic>
5800 </BODY>
5801 </HTML>
5802 ======= h_index_sort_date =======
5803 <HTML>
5804 <HEAD>
5805 <TITLE>SORT OPTION: Date</TITLE>
5806 </HEAD>
5807 <BODY>
5808 <H1>SORT OPTION: Date</H1>
5810 The <EM>Date</EM> sort option arranges messages in the MESSAGE INDEX
5811 according to the date and time they were
5812 sent.
5814 <P>
5815 On a folder like INBOX, sorting by "Date" should be almost
5816 identical to sorting by "Arrival".
5818 <P>
5819 <End of help on this topic>
5820 </BODY>
5821 </HTML>
5822 ======= h_index_sort_subj =======
5823 <HTML>
5824 <HEAD>
5825 <TITLE>SORT OPTION: Subject</TITLE>
5826 </HEAD>
5827 <BODY>
5828 <H1>SORT OPTION: Subject</H1>
5830 The <EM>Subject</EM> sort option arranges messages in the MESSAGE INDEX
5831 by subject.
5833 <P>
5834 Messages with the same subject are
5835 first grouped together, and then the groups of like-subject messages
5836 are arranged alphabetically.
5838 <P>
5839 Alpine ignores leading "Re:" and
5840 "re:" and trailing "(fwd)" when determining the
5841 likeness and alphabetical order of subject lines.
5843 <P>
5844 <End of help on this topic>
5845 </BODY>
5846 </HTML>
5847 ======= h_index_sort_ordsubj =======
5848 <HTML>
5849 <HEAD>
5850 <TITLE>SORT OPTION: OrderedSubject</TITLE>
5851 </HEAD>
5852 <BODY>
5853 <H1>SORT OPTION: OrderedSubject</H1>
5855 The <EM>OrderedSubject</EM> sort option arranges messages in the
5856 MESSAGE INDEX by grouping all messages with the same subject
5857 together, similar to sort by <A HREF="h_index_sort_subj">S</A>ubject.
5859 <P>
5860 However, <EM>OrderedSubj</EM> then arranges the groups of like-subject
5861 messages by the date of the oldest message in the group.
5863 <P>
5864 This sort method provides for pseudo threading of conversations within
5865 a folder.
5866 You may want to try sorting by Thread instead.
5868 <P>
5869 <End of help on this topic>
5870 </BODY>
5871 </HTML>
5872 ======= h_index_sort_thread =======
5873 <HTML>
5874 <HEAD>
5875 <TITLE>SORT OPTION: Thread</TITLE>
5876 </HEAD>
5877 <BODY>
5878 <H1>SORT OPTION: Thread</H1>
5880 The <EM>Thread</EM> sort option arranges messages in the
5881 MESSAGE INDEX by grouping all messages that indicate
5882 they are part of a conversation (discussion thread) taking
5883 place within a mailbox or newsgroup. This indication is
5884 based on information in the message's header -- specifically
5885 its <tt>References:</tt>, <tt>Message-ID:</tt>, and <tt>Subject:</tt> fields.
5887 <P>
5888 <End of help on this topic>
5889 </BODY>
5890 </HTML>
5891 ======= h_index_sort_from =======
5892 <HTML>
5893 <HEAD>
5894 <TITLE>SORT OPTION: From</TITLE>
5895 </HEAD>
5896 <BODY>
5897 <H1>SORT OPTION: From</H1>
5899 The <EM>From</EM> sort option arranges messages in the MESSAGE INDEX
5900 by the name of the author of the message.
5902 <P>
5903 Messages with the same author are grouped together. Groups of
5904 messages are then put into alphabetical order according to message
5905 author.
5907 <P>
5908 <End of help on this topic>
5909 </BODY>
5910 </HTML>
5911 ======= h_index_sort_size =======
5912 <HTML>
5913 <HEAD>
5914 <TITLE>SORT OPTION: Size</TITLE>
5915 </HEAD>
5916 <BODY>
5917 <H1>SORT OPTION: Size</H1>
5919 The <EM>Size</EM> sort option arranges messages in the MESSAGE INDEX
5920 by their relative sizes.
5922 <P>
5923 <End of help on this topic>
5924 </BODY>
5925 </HTML>
5926 ======= h_index_sort_score =======
5927 <HTML>
5928 <HEAD>
5929 <TITLE>SORT OPTION: Score</TITLE>
5930 </HEAD>
5931 <BODY>
5932 <H1>SORT OPTION: Score</H1>
5934 The <EM>Score</EM> sort option arranges messages in the MESSAGE INDEX
5935 by their scores.
5937 <P>
5938 Messages with the same score are sorted in arrival order.
5939 Scores are something you create using the
5940 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
5942 <P>
5943 <End of help on this topic>
5944 </BODY>
5945 </HTML>
5946 ======= h_index_sort_to =======
5947 <HTML>
5948 <HEAD>
5949 <TITLE>SORT OPTION: To</TITLE>
5950 </HEAD>
5951 <BODY>
5952 <H1>SORT OPTION: To</H1>
5954 The <EM>To</EM> sort option arranges messages in the MESSAGE INDEX
5955 by the names of the recipients of the message.
5957 <P>
5958 Messages with the same recipients are grouped together. Groups of
5959 messages are then put into alphabetical order according to message
5960 recipients.
5962 <P>
5963 <End of help on this topic>
5964 </BODY>
5965 </HTML>
5966 ======= h_index_sort_cc =======
5967 <HTML>
5968 <HEAD>
5969 <TITLE>SORT OPTION: Cc</TITLE>
5970 </HEAD>
5971 <BODY>
5972 <H1>SORT OPTION: Cc</H1>
5974 The <EM>Cc</EM> sort option arranges messages in the MESSAGE INDEX by
5975 the names of the carbon copy addresses of the message.
5977 <P>
5978 <End of help on this topic>
5979 </BODY>
5980 </HTML>
5981 ======= h_index_cmd_whereis =======
5982 <HTML>
5983 <HEAD>
5984 <TITLE>WhereIs Command</TITLE>
5985 </HEAD>
5986 <BODY>
5987 <H1>WhereIs Command</H1>
5989 The WhereIs
5990 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
5991 command lets you search the MESSAGE INDEX for a word.
5992 It scans through whatever you see, usually the name of the author
5993 and the Subject line.
5994 WhereIs has special subcommands to let you find the beginning of the
5995 index (Ctrl-Y -- first message)
5996 or the end of the index (Ctrl-V -- last message).
5997 <P>
5998 Note that WhereIs only searches through the visible text on the screen.
5999 For example, if only part of the Subject of a message is shown because it
6000 is long, then only the visible portion of the Subject is searched.
6001 Also note that WhereIs does not "see" the
6002 "X" in column one of Index entries for selected messages
6003 so it can't be used to search for
6004 selected messages (use "Zoom" instead).
6005 <P>
6006 If the feature
6007 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
6008 is turned on,
6009 WhereIs can also be used as a quick way to select messages that match the
6010 string being searched for.
6011 Instead of typing carriage return to search for the next match, type
6012 Ctrl-X to select all matches.
6013 Once again, this only selects matches that are (or would be if the right
6014 index line was on the screen) visible.
6015 Truncated From lines or Subjects will cause matches to be missed.
6016 Although WhereIs is sometimes convenient for quick matching, the Select
6017 command is usually more powerful and usually faster.
6019 <P>
6020 <End of help on this topic>
6021 </BODY>
6022 </HTML>
6023 ======= h_view_cmd_whereis =======
6024 <HTML>
6025 <HEAD>
6026 <TITLE>WhereIs Command</TITLE>
6027 </HEAD>
6028 <BODY>
6029 <H1>WhereIs Command</H1>
6031 The WhereIs
6032 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
6033 command does a "find in current message" operation. You
6034 type in text and Alpine will try to find it in the message you are
6035 reading. WhereIs also has subcommands to jump to the beginning (Ctrl-Y)
6036 or end (Ctrl-V) of the message.
6037 That is, to rapidly move to the end of a message, hit the
6038 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
6039 (or Ctrl-W) key followed
6040 by Ctrl-V. Similarly,
6041 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
6042 followed by Ctrl-Y will take you to the beginning of a message.
6044 <P>
6045 <End of help on this topic>
6046 </BODY>
6047 </HTML>
6048 ======= h_view_cmd_hilite =======
6049 <HTML>
6050 <HEAD>
6051 <TITLE>View Hilite and Next item/Previous item</TITLE>
6052 </HEAD>
6053 <BODY>
6054 <H1>View Hilite and Next item/Previous item</H1>
6056 Sometimes messages may be in the form of formatted HTML text
6057 or they may contain URLs or Web server hostnames.
6058 When any of the features
6059 <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>,
6060 <A HREF="h_config_enable_view_web_host">"<!--#echo var="FEAT_enable-msg-view-web-hostnames"-->"</A>,
6061 <A HREF="h_config_enable_view_attach">"<!--#echo var="FEAT_enable-msg-view-attachments"-->"</A>,
6062 or
6063 <A HREF="h_config_enable_view_addresses">"<!--#echo var="FEAT_enable-msg-view-addresses"-->"</A>
6064 are enabled, Alpine will represent such selectable items in the text
6065 in bold typeface. One of the selectable items will be displayed in
6066 inverse video (highlighted). This is the "currently selected" item.
6067 Press the Return key to view the currently selected item.
6068 <P>
6070 The Up and Down Arrows keys can be used to change the selected item
6071 (also see the feature
6072 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
6073 If there are no selectable items in the direction of the arrow you
6074 pressed, Alpine will scroll the display in that direction until one
6075 becomes visible. To "jump" forwards/backwards among selectable
6076 items in the message text, use the Previous and Next item commands,
6077 <!--chtml if pinemode="function_key"-->F5 and F6
6078 <!--chtml else-->^B and ^F<!--chtml endif-->.
6080 <P>
6081 <End of help on this topic>
6082 </BODY>
6083 </HTML>
6084 ======= h_view_cmd_viewattch =======
6085 <HTML>
6086 <HEAD>
6087 <TITLE>ViewAttch Command</TITLE>
6088 </HEAD>
6089 <BODY>
6090 <H1>ViewAttch Command</H1>
6093 The View/Save Attachment
6094 (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->V<!--chtml endif-->)
6095 command allows you to handle MIME attachments to a message you have
6096 received. Alpine shows you a list of the message attachments -- you just
6097 choose the attachment you want. You may either view or save the
6098 selected attachment.
6100 <P>
6101 Because many attachments require external programs for display, there
6102 is some system configuration that has to happen before you can
6103 actually display attachments. Hopefully much of that will have been
6104 done already by your system administrator. MIME configuration is
6105 handled with the "mailcap" configuration file. (See the section
6106 on configuration in the
6107 <A HREF="h_news">release notes</A> for more information.)
6109 <P>
6110 <End of help on this topic>
6111 </BODY>
6112 </HTML>
6113 ======= h_index_cmd_expunge =======
6114 <HTML>
6115 <HEAD>
6116 <TITLE>Expunge/Exclude Command</TITLE>
6117 </HEAD>
6118 <BODY>
6119 <H1>Expunge/Exclude Command</H1>
6121 Expunge/Exclude
6122 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->X<!--chtml endif-->)
6123 is the command Alpine uses to actually remove all messages
6124 marked for deletion. With regular email files, expunge literally deletes
6125 the text from the current folder. With newsgroups or shared mailboxes,
6126 you don't have permission to actually remove the message, so it is an
6127 exclude -- Alpine removes the message from your view of the folder even
6128 though it is not technically gone.
6130 <P> A selective expunge command is available in IMAP folders that support
6131 the UID EXPUNGE extension in <A
6132 HREF="http://tools.ietf.org/html/rfc4315">RFC 4315</A> as well as for all
6133 other folders (local folders in all formats, POP3 inbox, and newsgroups)
6134 as a subcommand of the apply command. If some selected messages are marked
6135 deleted, then the apply command will offer the eXpunge command, which when
6136 executed will only expunge those messages that are selected and deleted.
6138 <P>
6139 Observe that the expunge command (when not used from the apply command)
6140 will expunge/exclude all deleted messages from the folder, and so all
6141 messages marked deleted will be expunged, regardless of if they are
6142 selected or not. In other words, there is no protection against
6143 potentially expunging more messages than only those that have been
6144 selected and deleted.
6145 <P>
6147 The configuration features
6148 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
6149 and
6150 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>
6151 affect the behavior of the Expunge command.
6153 <P>
6154 <End of help on this topic>
6155 </BODY>
6156 </HTML>
6157 ======= h_common_compose =======
6158 <HTML>
6159 <HEAD>
6160 <TITLE>Compose Command</TITLE>
6161 </HEAD>
6162 <BODY>
6163 <H1>Compose Command</H1>
6165 The Compose command takes you into the Alpine message composer where you
6166 can start a new message for sending. This is where you type in the
6167 message's text and specify its recipient list (the "To:"
6168 address), where copies should be directed (e.g., "Fcc",
6169 "Cc:" or "Bcc:"), and which files, if any, should
6170 be attached to the message.
6172 <P>
6173 When you type this command, Alpine will also automatically check for any
6174 interrupted (i.e., a message that was being composed when your modem
6175 or network connection was broken) or previously postponed messages and
6176 offer you a chance to continue working on those.
6178 <P>
6179 <UL>
6180 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6181 </UL><P>
6182 <End of help on this topic>
6183 </BODY>
6184 </HTML>
6185 ======= h_common_index =======
6186 <HTML>
6187 <HEAD>
6188 <TITLE>Message Index Command</TITLE>
6189 </HEAD>
6190 <BODY>
6191 <H1>Message Index Command</H1>
6193 The Index command takes you to the MESSAGE INDEX screen that displays a
6194 summary caption for each message in the currently-open folder. One
6195 message will be highlighted; this is the "Current" message.
6196 The message commands available from this screen (e.g. View, Reply,
6197 Forward, Delete, Print, Save, etc) apply to the current message.
6199 <P>
6200 <End of help on this topic>
6201 </BODY>
6202 </HTML>
6203 ======= h_common_folders =======
6204 <HTML>
6205 <HEAD>
6206 <TITLE>Folder List Command</TITLE>
6207 </HEAD>
6208 <BODY>
6209 <H1>Folder List Command</H1>
6211 This Folder List command takes you to the FOLDER LIST screen that displays
6212 the names of all your message folders and allows you to view, rename,
6213 delete, and add folders. You can open (view) a different folder than the
6214 one currently open by highlighting the desired one (using the arrow keys
6215 or their control-key equivalents) and pressing RETURN.
6217 <P>
6218 If you have multiple folder collections defined (see the Help text for
6219 the FOLDER LIST screen to learn more about Collections), you may need
6220 to press Return to expand the collection and display all of the
6221 folders in it.
6223 <P>
6224 <End of help on this topic>
6225 </BODY>
6226 </HTML>
6227 ======= h_main_addrbook =======
6228 <HTML>
6229 <HEAD>
6230 <TITLE>Address Book Command</TITLE>
6231 </HEAD>
6232 <BODY>
6233 <H1>Address Book Command</H1>
6235 This command, available only from the MAIN MENU, takes you
6236 to the ADDRESS BOOK management screen. From here, your personal address
6237 book(s) may be updated.
6239 <P>
6240 <End of help on this topic>
6241 </BODY>
6242 </HTML>
6243 ======= h_main_setup =======
6244 <HTML>
6245 <HEAD>
6246 <TITLE>Setup Command</TITLE>
6247 </HEAD>
6248 <BODY>
6249 <H1>Setup Command</H1>
6251 The Setup command, available only from the MAIN MENU, prompts you for
6252 one of several configuration screens, including the SETUP CONFIGURATION
6253 screen, by which you may activate optional Alpine features.
6255 <P>
6256 <End of help on this topic>
6257 </BODY>
6258 </HTML>
6259 ======= h_main_release_notes =======
6260 <HTML>
6261 <HEAD>
6262 <TITLE>Release Notes Command</TITLE>
6263 </HEAD>
6264 <BODY>
6265 <H1>Release Notes Command</H1>
6267 This command displays information about Alpine <!--#echo var="ALPINE_VERSION"-->,
6268 as well as pointers to further information such as history and legal notes.
6270 <P>
6271 <End of help on this topic>
6272 </BODY>
6273 </HTML>
6274 ======= h_main_kblock =======
6275 <HTML>
6276 <HEAD>
6277 <TITLE>Keyboard Lock Command</TITLE>
6278 </HEAD>
6279 <BODY>
6280 <H1>Keyboard Lock Command</H1>
6282 This command allows your Alpine session to be protected
6283 during a temporary absence from your terminal.
6285 <P>
6286 <End of help on this topic>
6287 </BODY>
6288 </HTML>
6289 ======= h_main_journal =======
6290 <HTML>
6291 <HEAD>
6292 <TITLE>Journal Command</TITLE>
6293 </HEAD>
6294 <BODY>
6295 <H1>Journal Command</H1>
6297 This command displays a list of all the status messages Alpine has
6298 displayed (on the third line from the bottom of the screen). This may
6299 be useful if a message disappeared before you had a chance to read it.
6301 <P>
6302 <End of help on this topic>
6303 </BODY>
6304 </HTML>
6305 ======= h_common_role =======
6306 <HTML>
6307 <HEAD>
6308 <TITLE>Role Command</TITLE>
6309 </HEAD>
6310 <BODY>
6311 <H1>Role Command</H1>
6313 The Role command is similar to the Compose command except that it starts
6314 off by letting you select a <A HREF="h_rules_roles">role</A>
6315 to be used for the composition.
6316 You may set up alternate roles by using Setup/Rules/Roles.
6318 <P>
6319 <End of help on this topic>
6320 </BODY>
6321 </HTML>
6322 ======= h_common_conditional_cmds =======
6323 <HTML>
6324 <HEAD>
6325 <TITLE>Conditional Commands</TITLE>
6326 </HEAD>
6327 <BODY>
6328 <H1>Conditional Commands</H1>
6330 The presence or absence of certain commands, particularly in the
6331 MESSAGE INDEX and MESSAGE TEXT screens, is determined by
6332 whether or not specific features are set in your Alpine configuration.
6333 (You can access the SETUP CONFIGURATION screen, where they are found, from
6334 Alpine's MAIN MENU.) To see if a desired command's availability is
6335 conditioned on a feature setting, see the command's help text (highlight
6336 the phrase associated with the command and hit Return).
6338 <P>
6339 Also note that some
6340 commands may be administratively disabled by your system manager;
6341 if they don't work, please check with your local help desk.
6343 <P>
6344 <UL>
6345 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6346 </UL><P>
6347 <End of help on this topic>
6348 </BODY>
6349 </HTML>
6350 ======= h_common_pipe =======
6351 <HTML>
6352 <HEAD>
6353 <TITLE>Pipe Command</TITLE>
6354 </HEAD>
6355 <BODY>
6356 <H1>Pipe Command</H1>
6358 Pipe
6359 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->|<!--chtml endif-->)
6360 allows you to send a message to a specified Unix command for external
6361 processing.
6362 This command's availability is controlled by the
6363 <A HREF="h_config_enable_pipe">"<!--#echo var="FEAT_enable-unix-pipe-cmd"-->"</A>
6364 feature.
6365 By default, the processed text of the message is sent to the command
6366 you specify and the output is captured by Alpine and shown to you.
6367 When you run the pipe command, there are some sub-commands which may be
6368 used to alter this behavior.
6369 These sub-commands are described <A HREF="h_pipe_command">here</A>.
6371 <P>
6372 <End of help on this topic>
6373 </BODY>
6374 </HTML>
6375 ======= h_common_goto =======
6376 <HTML>
6377 <HEAD>
6378 <TITLE>Goto Command</TITLE>
6379 </HEAD>
6380 <BODY>
6381 <H1>Goto Command</H1>
6383 Goto
6384 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->G<!--chtml endif-->)
6385 is the command that lets you bypass Alpine's folder selection screens
6386 and jump directly to a new folder. You can select any folder in the
6387 world: one in your current collection, one in a different collection or
6388 one in a collection you've never even used before.
6389 <P>
6391 Alpine will help you as much as possible to narrow in on the folder you want.
6392 However, if the folder is outside of your defined collections, you are
6393 going to have to enter the exact folder location using the correct
6394 <A HREF="h_valid_folder_names">syntax</A>
6395 for a remote folder and/or fully-qualified path name.
6397 <P>
6398 <End of help on this topic>
6399 </BODY>
6400 </HTML>
6401 ======= h_common_nextnew =======
6402 <HTML>
6403 <HEAD>
6404 <TITLE>NextNew Command</TITLE>
6405 </HEAD>
6406 <BODY>
6407 <H1>NextNew Command</H1>
6409 When you press the TAB key, Alpine advances to the next
6410 "interesting" message.
6411 This will be the next message you have not seen before, or the next message
6412 you have flagged Important, whichever comes first.
6413 Unread messages that have been deleted are not considered interesting.
6414 (A note about reading news. Alpine expects you to "Delete" news
6415 articles after you have read them if you want to remove them from future
6416 consideration. See <A HREF="h_mainhelp_readingnews">Reading News</A> for
6417 more information.)
6419 <P>
6420 The NextNew command is affected by the feature
6421 <A HREF="h_config_tab_new_only">"<!--#echo var="FEAT_tab-visits-next-new-message-only"-->"</A>,
6422 which causes Alpine to only consider Unread messages interesting, not messages
6423 flagged Important.
6425 <P>
6426 This command behaves a little differently when it finds there are no more
6427 interesting messages left in the current folder.
6428 If the current folder is one of your Incoming Message Folders
6429 (<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>)
6430 or it is a newsgroup, then Alpine will try to find the next folder or
6431 newsgroup that contains <EM>Recent</EM> messages and will ask you
6432 if you want to open that folder.
6433 This behavior may be modified by using the
6434 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
6435 feature that causes Alpine to look for Unseen messages instead of Recent
6436 messages.
6437 The NextNew command's behavior is also affected by the configuration features
6438 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A>,
6439 and
6440 <A HREF="h_config_tab_no_prompt">"<!--#echo var="FEAT_continue-tab-without-confirm"-->"</A>.
6442 <P>
6443 <End of help on this topic>
6444 </BODY>
6445 </HTML>
6446 ======= h_common_jump =======
6447 <HTML>
6448 <HEAD>
6449 <TITLE>Jump Command</TITLE>
6450 </HEAD>
6451 <BODY>
6452 <H1>Jump Command</H1>
6454 This is Alpine's way of allowing you to go straight to a specific message.
6455 Just press "J" and then enter the message number. By default, Alpine is also
6456 configured such that typing in any number automatically jumps you to that
6457 message
6458 (<A HREF="h_config_enable_jump">"<!--#echo var="FEAT_enable-jump-shortcut"-->"</A>
6459 in the SETUP CONFIGURATION).
6461 <P>
6462 <End of help on this topic>
6463 </BODY>
6464 </HTML>
6465 ======= h_common_flag =======
6466 <HTML>
6467 <HEAD>
6468 <TITLE>Flag Command</TITLE>
6469 </HEAD>
6470 <BODY>
6471 <H1>Flag Command</H1>
6473 Flag
6474 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6475 is the command that allows users to manipulate the status flags that
6476 appear on the left side of the MESSAGE INDEX screen. The most common
6477 use of this is to mark a message as important. This is something of a
6478 note to yourself to get back to that message. You may also use the
6479 flag command to set (or unset) the flags that indicate that a message
6480 is new, answered, deleted, or forwarded.<P>
6482 Provided the mail server supports it,
6483 you may also manipulate user-defined keywords
6484 for a message using the flag command.
6485 These keywords will be available if you use the Flag Details screen that you
6486 can get to after typing the
6487 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6488 command.
6489 They will be listed after the Important, New, Answered, Deleted , and Forwarded flags,
6490 which are always present.
6491 You may add new keywords by using the Add KW command from the Flag Details screen
6492 or by defining them in the <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
6494 The availability of the flag command is determined by the
6495 <A HREF="h_config_enable_flag">"<!--#echo var="FEAT_enable-flag-cmd"-->"</A>
6496 feature in your Alpine configuration. Also, it is possible that Flag could be
6497 administratively disabled by your system manager; if it doesn't work,
6498 please check with your local help desk before reporting a bug.
6499 The behavior of the flag command may be modified by the
6500 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
6501 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
6503 <P>
6504 <End of help on this topic>
6505 </BODY>
6506 </HTML>
6507 ======= h_common_hdrmode =======
6508 <HTML>
6509 <HEAD>
6510 <TITLE>HdrMode Command</TITLE>
6511 </HEAD>
6512 <BODY>
6513 <H1>HdrMode Command</H1>
6515 Every email message comes with some header lines that you normally
6516 don't see (and don't want to see).
6517 These include anywhere from 3-20 lines (or more) added by the
6518 Internet mail transport system to record the route your message took,
6519 for diagnostic purposes.
6520 These are normally of no import and simply
6521 add clutter, so Alpine suppresses them in the MESSAGE TEXT display.
6522 This also includes other non-standard headers the message may contain.
6523 If you want to see these headers, there is a way to reveal them.
6524 <P>
6526 The Header Mode
6527 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6528 command is a toggle that controls Alpine's handling of these header
6529 lines. Normally, full headers is "off" and you only see a
6530 few lines about who a message is to and who it is from. When you
6531 press
6532 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6533 to turn full headers on, Alpine will show you
6534 the normal header lines as well as delivery headers, comment headers,
6535 MIME headers, and any other headers present.
6536 <P>
6538 Several different Alpine commands honor the header mode -- it affects how
6539 messages are displayed, how they appear in forward and reply email, how
6540 they are printed, how they are saved, and how they are exported.
6541 <!--chtml if pinemode="os_windows"-->
6542 <!--chtml else-->
6543 The pipe command is also affected.
6544 <!--chtml endif-->
6545 <P>
6547 The presence or absence of the Header Mode command is determined by the
6548 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
6549 Feature-List option in your Alpine configuration.
6551 <P>
6552 If you have also turned on the
6553 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
6554 option then the HdrMode command actually rotates through three states
6555 instead of just two.
6556 The first is the normal view with long quotes suppressed.
6557 The second is the normal view but with the long quotes included.
6558 The last enables the display of all headers in the message.
6559 When using Export, Pipe, Print, Forward, or Reply the quotes are
6560 never suppressed, so the first two states are identical.
6562 <P>
6563 The behavior of the Header Mode command may be altered slightly by
6564 turning on the
6565 <A HREF="h_config_quell_full_hdr_reset">"<!--#echo var="FEAT_quell-full-header-auto-reset"-->"</A>
6566 Feature-List option in your Alpine configuration.
6567 In particular, it will cause the Header Mode to be persistent when moving
6568 from message to message instead of resetting to the default for each message.
6570 <P>
6571 <UL>
6572 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6573 </UL><P>
6574 <End of help on this topic>
6575 </BODY>
6576 </HTML>
6577 ======= h_common_print =======
6578 <HTML>
6579 <HEAD>
6580 <TITLE>Print Command</TITLE>
6581 </HEAD>
6582 <BODY>
6583 <H1>Print Command</H1>
6585 The Print
6586 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->%<!--chtml endif-->)
6587 command allows you to print a copy of a message.
6588 There are many SETUP CONFIGURATION features that affect the
6589 Print command, including
6590 <A HREF="h_config_enable_y_print">"<!--#echo var="FEAT_enable-print-via-y-command"-->"</A>,
6591 <A HREF="h_config_print_index">"<!--#echo var="FEAT_print-index-enabled"-->"</A>,
6592 <A HREF="h_config_custom_print">"<!--#echo var="FEAT_print-offers-custom-cmd-prompt"-->"</A>,
6593 <A HREF="h_config_print_from">"<!--#echo var="FEAT_print-includes-from-line"-->"</A>, and
6594 <A HREF="h_config_ff_between_msgs">"<!--#echo var="FEAT_print-formfeed-between-messages"-->"</A>.
6595 You set up for printing by using the Printer option of the Setup command
6596 on the MAIN MENU.
6597 <P>
6599 <P>
6600 <End of help on this topic>
6601 </BODY>
6602 </HTML>
6603 ======= h_common_take =======
6604 <HTML>
6605 <HEAD>
6606 <TITLE>TakeAddr Command</TITLE>
6607 </HEAD>
6608 <BODY>
6609 <H1>TakeAddr Command</H1>
6612 With the Take Address
6613 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->T<!--chtml endif-->)
6614 command, you can extract email addresses from an
6615 incoming message and save them in an address book. This is an easy way
6616 to add to your address book and avoid having to remember the email
6617 addresses of the people who write to you.
6618 <P>
6620 If the message is just to you individually, then you will only need to
6621 provide a nickname. If the message contains more than one email address,
6622 then you will see an address
6623 selection screen that lets you choose the address you want to save into
6624 your address book, or lets you choose several of them add to a
6625 personal distribution list.
6626 <P>
6628 Once you've added an entry to your address book, you can use it from the
6629 message composer by typing the nickname of the entry into one of the
6630 header fields (for example, into the To: field), or you can use ^T from
6631 the header field to select the entry from your address book.
6632 <P>
6634 If the configuration feature
6635 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
6636 is set, the behavior of the Take command is altered slightly.
6638 <P>
6639 <End of help on this topic>
6640 </BODY>
6641 </HTML>
6642 ======= h_ge_import =======
6643 <HTML>
6644 <HEAD>
6645 <TITLE>Import File Selection</TITLE>
6646 </HEAD>
6647 <BODY>
6648 <H1>Import File Selection</H1>
6650 You are importing a file that you previously
6651 exported from Alpine.
6652 You are now being asked for the name of that file.
6653 The easiest way to select a file is probably with the "^T"
6654 "To Files" command.
6655 Alternatively, you may type in a file name.
6656 It may be an absolute pathname.
6657 Otherwise, it is a file located in your home directory
6658 or current working directory
6659 <!--chtml if pinemode="running"-->
6660 (which, at least for your current Alpine "session,"
6661 is "<!--#echo var="CURRENT_DIR"-->")
6662 <!--chtml endif-->, depending on the
6663 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6664 In any case, you finish by typing a carriage return to accept the
6665 file name that is displayed.
6666 When the feature
6667 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6668 is turned on you may use TAB to complete partially typed in names.
6669 <P>
6670 You may cancel the import operation by typing "^C" after exiting
6671 this help.
6672 <P>
6673 <End of help on this topic>
6674 </BODY>
6675 </HTML>
6676 ======= h_ge_allparts =======
6677 <HTML>
6678 <HEAD>
6679 <TITLE>Export Message File Selection</TITLE>
6680 </HEAD>
6681 <BODY>
6682 <H1>Export Message File Selection</H1>
6684 You are Exporting a message from an Alpine mail folder
6685 to a plain text file.
6686 You also have the option of exporting all of the attachments associated
6687 with the message.
6688 You are now being asked for the name of the file to export <EM>to</EM>.
6689 The easiest way to select a file is probably with the "^T"
6690 "To Files" subcommand.
6691 After returning from that subcommand you will still be allowed to
6692 edit the name you have selected.
6693 Alternatively, you may type in a file name.
6694 It may be an absolute pathname.
6695 Otherwise, it is a file located in your home directory
6696 or current working directory
6697 <!--chtml if pinemode="running"-->
6698 (which, at least for your current Alpine "session,"
6699 is "<!--#echo var="CURRENT_DIR"-->")
6700 <!--chtml endif-->, depending on the
6701 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6702 In any case, you finish by typing a carriage return to accept the
6703 file name that is displayed.
6704 When the feature
6705 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6706 is turned on you may use TAB to complete partially typed in names.
6707 <P>
6708 The message you are exporting appears to have some attachments.
6709 If you wish to save <EM>all</EM> of the attachments at once,
6710 type the "^P" "AllParts" command to turn on
6711 saving of the attachments.
6712 You may turn it back off by typing "^P" again, which will now
6713 be labeled "NoAllParts" instead.
6714 If you want to save the parts the command displayed should be
6715 "NoAllParts"!
6716 When you choose to save attachments like this, the attachments will be saved
6717 in a newly created directory.
6718 That directory will have the same name as the file name you choose here,
6719 with the letters ".d" appended.
6720 If that directory already exists, then the letters ".d_1" will
6721 be tried, then ".d_2" and so on until a name that doesn't exist
6722 is found.
6723 For example, if you select the file name
6724 <P>
6725 <CENTER><SAMP>filename</SAMP></CENTER>
6726 <P>
6727 to export the message to, then the directory used for the attachments will be
6728 <P>
6729 <CENTER><SAMP>filename.d</SAMP></CENTER>
6730 <P>
6731 or perhaps
6732 <P>
6733 <CENTER><SAMP>filename.d_<n></SAMP></CENTER>
6734 <P>
6735 The attachments will then be put into files inside that directory.
6736 The names for the attachment files will be derived from the attachments
6737 if possible.
6738 This is done in the same way as the default values are derived if you
6739 save them one at a time.
6740 (The "filename" parameter from the Content-Disposition header
6741 is the first choice. If that doesn't exist, the "name"
6742 parameter from the Content-Type header is used.)
6743 If a name for a particular attachment is not available, then the
6744 part number of the attachment is used, with the characters "part_"
6745 prepended.
6746 An example of that would be
6747 <P>
6748 <CENTER><SAMP>part_2.1</SAMP></CENTER>
6749 <P>
6750 If you want to save only some of the attachments or if you want more control
6751 over the directory and filename where an attachment is saved you may
6752 cancel out of this command and View the attachment list.
6753 From there you can save each attachment individually.
6754 <P>
6755 You may cancel the Export operation by typing "^C" after exiting
6756 this help.
6757 <P>
6758 <End of help on this topic>
6759 </BODY>
6760 </HTML>
6761 ======= h_ge_export =======
6762 <HTML>
6763 <HEAD>
6764 <TITLE>Export File Selection</TITLE>
6765 </HEAD>
6766 <BODY>
6767 <H1>Export File Selection</H1>
6769 You are Exporting or Saving something from within the Alpine world
6770 (a message, an attachment, etc.)
6771 to a plain text file.
6772 You are now being asked for the name of the file to export <EM>to</EM>.
6773 The easiest way to select a file is probably with the "^T"
6774 "To Files" subcommand.
6775 After returning from that subcommand you will still be allowed to
6776 edit the name you have selected.
6777 Alternatively, you may type in a file name.
6778 It may be an absolute pathname.
6779 Otherwise, it is a file located in your home directory
6780 or current working directory
6781 <!--chtml if pinemode="running"-->
6782 (which, at least for your current Alpine "session,"
6783 is "<!--#echo var="CURRENT_DIR"-->")
6784 <!--chtml endif-->, depending on the
6785 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6786 In any case, you finish by typing a carriage return to accept the
6787 file name that is displayed.
6788 When the feature
6789 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6790 is turned on you may use TAB to complete partially typed in names.
6791 <P>
6792 If the object you are exporting is a message with some attachments,
6793 you may wish to save all of the attachments by typing the "^P"
6794 "AllParts" command to turn on saving of the attachments.
6795 This subcommand will only be visible if the message actually has attachments.
6796 You may also View the attachment list and save individual attachments from
6797 there.
6798 <P>
6799 If you are SAVING a text part (text/plain, text/html, etc.) you can use
6800 the Control-R subcommand to toggle if saving will be done in binary mode,
6801 meaning that the attachment will be decoded, but will not be transformed
6802 to UTF-8 for further processing (either in internal filters, or user
6803 supplied filters.) This is useful in case you either want to preserve
6804 the text as it was encoded originally to you, or the attachment was
6805 incorrectly attached (the attachment is not of text type) and you need
6806 the original text to process the attachment.
6807 <P>
6808 You may cancel the Export operation by typing "^C" after exiting
6809 this help.
6810 <P>
6811 <End of help on this topic>
6812 </BODY>
6813 </HTML>
6814 ======= h_common_save =======
6815 <HTML>
6816 <HEAD>
6817 <TITLE>Save and Export Commands</TITLE>
6818 </HEAD>
6819 <BODY>
6820 <H1>Save and Export Commands</H1>
6822 Save
6823 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->S<!--chtml endif-->)
6824 and Export
6825 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->E<!--chtml endif-->)
6826 are the two alternatives Alpine gives you to keep a copy of the message
6827 you are reading. If you want to keep the message within Alpine's email
6828 world, use "Save"; if you want to use the message in another
6829 program, use "Export".
6830 <P>
6832 When you Save a message, it is put into an existing folder or into a new
6833 folder in one of your existing folder collections. The message stays in
6834 email format and can be read by Alpine again. Alpine may use a special format
6835 for its mail folders -- never edit an Alpine folder by hand or with any
6836 program other than Alpine. The exact behavior of the Save command can be
6837 configured with the
6838 <A HREF="h_config_quote_all_froms">"<!--#echo var="FEAT_save-will-quote-leading-froms"-->"</A>,
6839 <A HREF="h_config_save_wont_delete">"<!--#echo var="FEAT_save-will-not-delete"-->"</A>,
6840 and
6841 <A HREF="h_config_save_advances">"<!--#echo var="FEAT_save-will-advance"-->"</A>
6842 feature list settings.
6843 The name of the folder offered as a default is controlled by the option
6844 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>.
6845 <P>
6847 When you use Export, the message is placed in a plain text file in your
6848 home directory
6849 <!--chtml if pinemode="running"-->
6850 (which, in the present configuration of your system, is
6851 "<!--#echo var="HOME_DIR"-->")
6852 <!--chtml endif-->
6853 or current working directory
6854 <!--chtml if pinemode="running"-->
6855 (which, at least for your current Alpine "session,"
6856 is "<!--#echo var="CURRENT_DIR"-->")
6857 <!--chtml endif-->, depending on the
6858 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
6859 configuration setting. In the normal case, only minimal
6860 headers are exported with the message; however, if the full header mode
6861 (whose availability may be disabled by setting the feature
6862 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
6863 in SETUP CONFIGURATION) is
6864 toggled on, then complete headers are exported along with the message
6865 text. (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
6866 defined, they may affect the contents of the exported file.)
6868 <P>
6869 <End of help on this topic>
6870 </BODY>
6871 </HTML>
6872 ======= h_common_bounce =======
6873 <HTML>
6874 <HEAD>
6875 <TITLE>Bounce Command</TITLE>
6876 </HEAD>
6877 <BODY>
6878 <H1>Bounce Command</H1>
6880 The Bounce
6881 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->B<!--chtml endif-->)
6882 command allows you to re-send, or "remail", a
6883 message, as if you were never in the loop. It is analogous to crossing
6884 out your address on a postal letter, writing a different address on the
6885 envelope, and putting it into the mailbox. Bounce is used primarily to
6886 redirect email that was sent to you in error.
6887 Also, some owners of email
6888 lists need the bounce command to handle list traffic.
6889 Bounce is not anonymous.
6890 A ReSent-From header is added to the message so that the recipient may
6891 tell that you Bounced it to them.
6892 <P>
6894 The presence or absence of the Bounce command is determined by the
6895 <A HREF="h_config_enable_bounce">"<!--#echo var="FEAT_enable-bounce-cmd"-->"</A>
6896 feature in your Alpine configuration.
6897 The feature
6898 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A>
6899 affects the behavior of the Bounce command.
6900 Also, it is possible that Bounce could be
6901 administratively disabled by your system manager; if it doesn't work,
6902 please check with your local help desk before reporting a bug.
6904 <P>
6905 <End of help on this topic>
6906 </BODY>
6907 </HTML>
6908 ======= h_common_reply =======
6909 <HTML>
6910 <HEAD>
6911 <TITLE>Reply and Forward Commands</TITLE>
6912 </HEAD>
6913 <BODY>
6915 <H1>Reply and Forward Commands</H1>
6917 Replying
6918 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->R<!--chtml endif-->)
6919 and Forwarding
6920 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->F<!--chtml endif-->)
6921 are your two alternatives for following up on the
6922 message you are reading. You would use reply if you want to get email
6923 back to the author of the message and/or the other people who have
6924 already seen it. You use forward if you want somebody new to see the
6925 message.
6926 <P>
6928 In the normal case, the only thing that you must supply when forwarding a
6929 message is the name/email address of the new recipient.
6930 Alpine will include the text of the forwarded message.
6931 Alpine will also include any attachments to the message.
6932 There is space above the forwarded text for you to include additional comments.
6933 <P>
6935 When replying, you usually have to answer some questions.
6936 If the message is to multiple people and/or specified with a Reply-To: header,
6937 then you will have to decide who should get the reply.
6938 You also need to decide whether or not to include the previous
6939 message in your reply.
6940 Some of this is configurable.
6941 Specifically, see the
6942 <A HREF="h_config_include_header">"<!--#echo var="FEAT_include-header-in-reply"-->"</A>,
6943 <A HREF="h_config_auto_include_reply">"<!--#echo var="FEAT_include-text-in-reply"-->"</A>,
6944 <A HREF="h_config_attach_in_reply">"<!--#echo var="FEAT_include-attachments-in-reply"-->"</A>,
6945 and
6946 <A HREF="h_config_auto_reply_to">"<!--#echo var="FEAT_reply-always-uses-reply-to"-->"</A>
6947 configuration features.
6948 <P>
6950 Both the Reply and Forward commands react to the full header mode toggle.
6951 If the full header mode is on, then all the header and delivery lines are
6952 included with the text of the message in your reply/forward.
6953 <P>
6955 Other configuration features that affect the Reply command are
6956 <A HREF="h_config_sig_at_bottom">"<!--#echo var="FEAT_signature-at-bottom"-->"</A>,
6957 <A HREF="h_config_sigdashes">"<!--#echo var="FEAT_enable-sigdashes"-->"</A>, and
6958 <A HREF="h_config_strip_sigdashes">"<!--#echo var="FEAT_strip-from-sigdashes-on-reply"-->"</A>.
6960 <P>
6961 <End of help on this topic>
6962 </BODY>
6963 </HTML>
6964 ======= h_common_delete =======
6965 <HTML>
6966 <HEAD>
6967 <TITLE>Delete and Undelete Commands</TITLE>
6968 </HEAD>
6969 <BODY>
6970 <H1>Delete and Undelete Commands</H1>
6972 Delete
6973 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->D<!--chtml endif-->)
6974 and Undelete
6975 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->U<!--chtml endif-->)
6976 allow you to change the Deleted flag for the current message.
6977 Delete marks a message Deleted (turns on the Deleted flag) and Undelete
6978 removes the mark.
6979 In the MESSAGE INDEX, deleted messages have a "D" in the status field
6980 at the left hand edge of the index line.
6981 When viewing a deleted message, the letters "DEL" will be present
6982 in the upper right hand corner of the screen.
6983 Delete simply <EM>marks</EM> a message Deleted, it does not actually
6984 get rid of the message.
6985 The eXpunge command (available from the MESSAGE INDEX screen) actually
6986 removes all of the deleted messages in a folder.
6987 Once a message is eXpunged, it can't be retrieved.
6988 <P>
6990 The Delete command is affected by the setting of the configuration feature
6991 <A HREF="h_config_del_skips_del">"<!--#echo var="FEAT_delete-skips-deleted"-->"</A>.
6993 <P>
6994 <End of help on this topic>
6995 </BODY>
6996 </HTML>
6997 ======= h_common_postpone =======
6998 <HTML>
6999 <HEAD>
7000 <TITLE>Postpone Command</TITLE>
7001 </HEAD>
7002 <BODY>
7003 <H1>Postpone Command</H1>
7005 The postpone
7006 <!--chtml if pinemode="function_key"-->(F11)<!--chtml else-->(^O)<!--chtml endif-->
7007 command allows you to temporarily stop working on the current
7008 message so you may read
7009 other messages or compose another message. When you want to resume a
7010 message later, start to compose and answer "yes" to the
7011 "Continue postponed composition?" question. You may
7012 postpone as many messages as you like.
7014 <P>
7015 Note: If a <A HREF="h_config_form_folder"><!--#echo var="VAR_form-letter-folder"--></A> is defined
7016 in the Setup/Config screen, then the Postpone command will prompt you for
7017 the folder in which to store your outgoing message.
7019 <P>
7020 <End of help on this topic>
7021 </BODY>
7022 </HTML>
7023 ======= h_compose_cancel =======
7024 <HTML>
7025 <HEAD>
7026 <TITLE>Cancel Command</TITLE>
7027 </HEAD>
7028 <BODY>
7029 <H1>Cancel Command</H1>
7031 Cancel
7032 <!--chtml if pinemode="function_key"-->
7033 (F2)
7034 <!--chtml else-->
7035 (^C)
7036 <!--chtml endif-->
7038 The Cancel command returns you to Alpine's normal mail processing and
7039 causes the message currently under composition to be thrown out.
7040 The message text <EM>will be lost</EM>.
7042 <P>
7043 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
7044 will be preserved in the file named
7045 <!--chtml if pinemode="os_windows"-->
7046 "DEADLETR".
7047 <!--chtml else-->
7048 "dead.letter" in your home directory.
7049 <!--chtml endif-->
7050 If you unintentionally cancel a message, look there for its text.
7052 <P>
7053 <End of help on this topic>
7054 </BODY>
7055 </HTML>
7056 ======= h_compose_addrcomplete =======
7057 <HTML>
7058 <HEAD>
7059 <TITLE>Address Completion</TITLE>
7060 </HEAD>
7061 <BODY>
7062 <H1>Address Completion</H1>
7064 When entering addresses in the address fields of the composer (To, Cc, etc.)
7065 the TAB key may be used to help complete the address.
7066 Type a partial nickname and tap the TAB key to complete the typing.
7067 The unambiguous part of the name will be filled in automatically.
7068 Typing TAB twice in succession will bring up a selection list of possibilities,
7069 making it easy to find and choose the correct address.
7071 <P>
7072 The matching algorithm is rather ad hoc.
7073 The search starts with a search of your address book.
7074 It counts as a match if the nickname, address, or fullname field of an
7075 entry begins with the text typed in so far. It is also a match if
7076 a later word in the fullname (for example, the middle name or last name)
7077 begins with the entered text.
7078 <P>
7079 Next comes an LDAP search.
7080 The search will happen for any servers that have the
7081 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
7082 feature set. You can set or unset the feature for each server independently
7083 in the Setup/Directory screen.
7084 <P>
7085 Finally, if you are replying to or forwarding a message, that message is
7086 searched for likely candidate addresses that match the typed-in text.
7088 <P>
7089 <End of help on this topic>
7090 </BODY>
7091 </HTML>
7092 ======= h_compose_richhdr =======
7093 <HTML>
7094 <HEAD>
7095 <TITLE>Rich Header Command</TITLE>
7096 </HEAD>
7097 <BODY>
7098 <H1>Rich Header Command</H1>
7100 The Rich Header command allows you to toggle between the list of
7101 all message headers available for editing and those that are most
7102 common.
7104 <P>
7105 Use this toggle to expose headers that are not normally visible by
7106 default.
7107 This set usually includes the
7108 "Bcc:",
7109 "Fcc:",
7110 "Lcc:",
7111 and "Newsgroups"
7112 headers.
7113 If you are posting to a newsgroup the set of defaults is a little different.
7114 Obviously, in that case, the Newsgroups header is of interest so is not
7115 hidden.
7116 For news posting the hidden set includes the
7117 "To:",
7118 "Cc:",
7119 "Bcc:",
7120 "Fcc:",
7121 and "Lcc:"
7122 headers.
7123 You won't normally want to edit these, which is why they are hidden,
7124 but it is sometimes useful to be able to set them manually.
7126 <P>
7127 The default sets of headers listed above can be altered.
7128 Any header that you have added to the
7129 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
7130 option, but not to the
7131 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
7132 option will appear when you use the Rich Headers command to
7133 make the Rich Headers visible.
7134 (Headers listed in the <!--#echo var="VAR_default-composer-hdrs"--> list will be visible
7135 even without toggling the Rich Headers command.)
7137 <P>
7138 <End of help on this topic>
7139 </BODY>
7140 </HTML>
7141 ======= h_compose_send =======
7142 <HTML>
7143 <HEAD>
7144 <TITLE>Send Command</TITLE>
7145 </HEAD>
7146 <BODY>
7147 <H1>Send Command</H1>
7149 The Send command
7150 <!--chtml if pinemode="function_key"-->
7151 (F3)
7152 <!--chtml else-->
7153 (^X)
7154 <!--chtml endif-->
7155 tells Alpine you are finished composing.
7156 Before actually sending it, though, Alpine will ask you to confirm
7157 your intention, and, at the same time, redisplayed the message text
7158 with the recipients at the top of the screen to give you the opportunity
7159 to review and verify that the message is addressed to the people
7160 you intended.
7161 <P>
7162 If the feature
7163 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
7164 then this confirmation prompt and any options it allows are skipped.
7166 <P>
7167 This confirmation prompt may also offer, depending
7168 on your particular Setup/Config, options allowing you to set
7169 <A HREF="h_config_compose_dsn">delivery status notifications</A>,
7170 include attachments in the "Fcc" (if you had previously
7171 specified that they <A HREF="h_config_no_fcc_attach">exclude attachments</A>,
7172 observe details of the
7173 <A HREF="h_config_verbose_post">message submission process</A>,
7174 choose the filter through which the
7175 <A HREF="h_config_sending_filter">outgoing text should first pass</A>,
7176 or turn of flowed text generation.
7178 <P>
7179 <End of help on this topic>
7180 </BODY>
7181 </HTML>
7182 ======= h_compose_markcutpaste =======
7183 <HTML>
7184 <HEAD>
7185 <TITLE>Mark, Cut and Paste Commands</TITLE>
7186 </HEAD>
7187 <BODY>
7188 <H1>Mark, Cut and Paste Commands</H1>
7190 You can define a "block" of text, which can subsequently
7191 be deleted or
7192 copied as a unit, by setting a mark at the start of the block (Ctrl-^) and
7193 then moving the cursor to the end of the desired text block. You can then
7194 "cut" the block out
7195 <!--chtml if pinemode="function_key"-->
7196 "F9",
7197 <!--chtml else-->
7198 "Ctrl-K",
7199 <!--chtml endif-->
7200 move the cursor, and "paste" it
7201 <!--chtml if pinemode="function_key"-->
7202 "F10",
7203 <!--chtml else-->
7204 "Ctrl-U",
7205 <!--chtml endif-->
7206 in the new location. Also, you can paste more than once, allowing you
7207 to use this feature to copy a block of text.<P>
7209 If you press
7210 <!--chtml if pinemode="function_key"-->
7211 "F9"
7212 <!--chtml else-->
7213 "^K"
7214 <!--chtml endif-->
7215 without having marked anything, Alpine will delete
7216 a single line. If you delete a group of lines together, Alpine keeps them
7217 in the same buffer, so
7218 <!--chtml if pinemode="function_key"-->
7219 F10
7220 <!--chtml else-->
7221 ^U
7222 <!--chtml endif-->
7223 will restore them as a block. About
7224 terminology: Mark is shown as "^^". The first "^" means you should
7225 hold down the "Control" key on your keyboard. The second "^" means
7226 "type the character ^".
7228 <P>
7229 <End of help on this topic>
7230 </BODY>
7231 </HTML>
7232 ======= h_compose_justify =======
7233 <HTML>
7234 <HEAD>
7235 <TITLE>Justify Command</TITLE>
7236 </HEAD>
7237 <BODY>
7238 <H1>Justify Command</H1>
7240 The Justify
7241 <!--chtml if pinemode="function_key"-->
7242 (F4)
7243 <!--chtml else-->
7244 (^J)
7245 <!--chtml endif-->
7246 command reformats the text in the paragraph the cursor is in.
7247 Paragraphs are separated by one blank line or a line beginning with a space.
7248 This is useful when you have been editing a paragraph and the lines become
7249 uneven. The text is left aligned or justified and the right is ragged. If
7250 the text is already justified as typed with auto-wrap, no justification will
7251 be done.
7253 <P>
7254 If you have set a <A HREF="h_compose_markcutpaste">mark</A> to select a
7255 block of text, the Justify command is modified.
7256 Instead of automatically justifying the current paragraph you will be
7257 asked if you want to justify the paragraph, justify the selected region,
7258 or adjust the quote level of the selected region.
7259 Adjusting the quote level only works if you are using standard
7260 "> " or ">" quotes, which is the default if you haven't
7261 changed "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>".
7263 <P>
7264 When composing a reply containing included text, the justify command
7265 will reformat text to the right of the
7266 "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>",
7267 adding or removing indented lines as needed. Paragraphs are separated
7268 by a blank line, a line containing only the <!--#echo var="VAR_reply-indent-string"-->, or a
7269 line containing the indent string and one or more blank spaces.
7270 Included text that was previously indented (or "quoted") is
7271 not preserved.
7273 <P>
7274 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
7275 in 1999 and its wide-spread adoption since then, you will usually be better off if you
7276 use the standard
7277 "> " or ">" quotes.
7279 <P>
7280 <End of help on this topic>
7281 </BODY>
7282 </HTML>
7283 ======= h_compose_spell =======
7284 <HTML>
7285 <HEAD>
7286 <TITLE>Spell Check Command</TITLE>
7287 </HEAD>
7288 <BODY>
7289 <H1>Spell Check Command</H1>
7291 The "To Spell"
7292 <!--chtml if pinemode="function_key"-->
7293 (F12)
7294 <!--chtml else-->
7295 (^T)
7296 <!--chtml endif-->
7297 command calls an external spell checking program to look over the
7298 message you are composing. By default, Alpine uses
7299 <P>
7300 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
7301 <P>
7302 if it knows where to find "aspell".
7303 If there is no "aspell" command available but the command "ispell" is available
7304 then the command used is
7305 <P>
7306 <CENTER><SAMP>ispell -l</SAMP></CENTER>
7307 <P>
7308 Otherwise, the ancient "spell" command is used.
7309 <P>
7310 For PC-Alpine, you must install the aspell library code that you
7311 may get from
7312 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
7314 <P>
7315 <End of help on this topic>
7316 </BODY>
7317 </HTML>
7318 ======= h_compose_alted =======
7319 <HTML>
7320 <HEAD>
7321 <TITLE>Alt Editor Command</TITLE>
7322 </HEAD>
7323 <BODY>
7324 <H1>Alt Editor Command</H1>
7326 The "Alt Editor" command's availability depends on the
7327 Setup/Config variable "<A HREF="h_config_editor"><!--#echo var="VAR_editor"--></A>".
7329 <P>
7330 When the variable specifies a valid editor on your system, this
7331 command will launch it with the current text of your message
7332 already filled in.
7334 <P>
7335 <End of help on this topic>
7336 </BODY>
7337 </HTML>
7338 ======= h_compose_readfile =======
7339 <HTML>
7340 <HEAD>
7341 <TITLE>Read File Command</TITLE>
7342 </HEAD>
7343 <BODY>
7344 <H1>Read File Command</H1>
7346 The "Read File"
7347 <!--chtml if pinemode="function_key"-->
7348 (F5)
7349 <!--chtml else-->
7350 (^R)
7351 <!--chtml endif-->
7352 command allows you to copy in text from an existing file. You will be
7353 prompted for the name of a file to be inserted into the message. The file
7354 name is relative to your home directory
7355 <!--chtml if pinemode="running"-->
7356 (which, in the present configuration of your system, is
7357 "<!--#echo var="HOME_DIR"-->")
7358 <!--chtml endif-->
7359 or current working directory
7360 <!--chtml if pinemode="running"-->
7361 (which, at least for your current Alpine "session,"
7362 is "<!--#echo var="CURRENT_DIR"-->")
7363 <!--chtml endif-->, depending on the
7364 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
7365 configuration setting; or, the file name must be specified as a full path name
7366 <!--chtml if pinemode="os_windows"-->
7367 -- for example: "A:\PAPER.TXT"
7368 <!--chtml else-->
7369 -- for example: "/tmp/wisdom-of-the-day"
7370 <!--chtml endif-->
7371 (without the quotation marks).
7373 <P>
7374 The file will be inserted where the cursor is located. <B>The
7375 file to be read must be on the same system as Alpine.</B> If you use Alpine on a
7376 Unix machine but have files on a PC or Mac, the files must be transferred
7377 to the system Alpine is running on before they can be read. Please ask your
7378 local computer support people about the correct way to transfer a file to
7379 your Alpine system.
7381 <P>
7382 <End of help on this topic>
7383 </BODY>
7384 </HTML>
7385 ======= h_config_tray_icon =======
7386 <HTML>
7387 <HEAD>
7388 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></TITLE>
7389 </HEAD>
7390 <BODY>
7391 <H1>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></H1>
7393 PC-Alpine only.
7394 <P>
7395 This option restores a behavior of previous versions of PC-Alpine.
7396 These
7397 versions, when started, installed a PC-Alpine icon in the notification
7398 tray of Window's Taskbar. The primary use of this icon was to indicate
7399 new mail arrival by turning red (while the Taskbar icon remained green).
7400 Additionally, the icon now changes to yellow to signify that a mail folder
7401 has been closed unexpectedly.
7403 <P>
7404 Rather than add another icon to the Taskbar, this version of PC-Alpine will
7405 color its Taskbar entry's icon red (as well as the icon in the Window
7406 Title). This feature is only provided for backwards compatibility.
7408 <P>
7409 <End of help on this topic>
7410 </BODY>
7411 </HTML>
7412 ======= h_common_suspend =======
7413 <HTML>
7414 <HEAD>
7415 <TITLE>Suspend Command</TITLE>
7416 </HEAD>
7417 <BODY>
7418 <H1>Suspend Command</H1>
7420 With the <A HREF="h_config_can_suspend"><!--#echo var="FEAT_enable-suspend"--></A> feature
7421 enabled, you can, at almost any time, temporarily halt your Alpine session,
7422 <!--chtml if pinemode="os_windows"-->
7423 minimizing it into an icon.
7424 <!--chtml else-->
7425 and return to your system prompt.
7426 <!--chtml endif-->
7428 <P>
7429 <End of help on this topic>
7430 </BODY>
7431 </HTML>
7432 ======= h_pipe_command =======
7433 <HTML>
7434 <HEAD>
7435 <TITLE>Pipe Command SubOptions</TITLE>
7436 </HEAD>
7437 <BODY>
7438 <H1>Pipe Command SubOptions</H1>
7440 By default, when you use the Pipe command, the processed text of the
7441 message is sent to the Unix command
7442 you specify and the output is captured by Alpine and shown to you.
7443 (This command is available in PC-Alpine, as well, but there aren't many
7444 Windows commands that work well with piping.)
7445 There are some sub-commands that may be used to alter this behavior.
7446 These are toggles that switch the behavior between two possibilities.
7447 They can be combined in any way you wish.
7448 <P>
7449 By default, the prompt at the bottom of the screen looks like
7450 <P>
7451 <CENTER><SAMP>Pipe message 37 to :</SAMP></CENTER>
7452 <P>
7453 or
7454 <P>
7455 <CENTER><SAMP>Pipe messages to :</SAMP></CENTER>
7456 <P>
7457 if you are piping more than one message.
7458 <P>
7459 The sub-command options are:
7460 <DL>
7461 <DT>Shown Text or Raw Text</DT>
7462 <DD>This option toggles between sending the shown (processed) text
7463 of the message to the Unix command, and sending the
7464 raw (unprocessed) text of the message to the Unix command.
7465 The default is to send the shown text.
7466 The raw version of the message will contain all of the headers and any
7467 MIME encoding that the message contains.
7468 If you've selected the Raw Text then the prompt will have the additional word
7469 "RAW" in it, like
7470 <P>
7471 <CENTER><SAMP>Pipe RAW messages to :</SAMP></CENTER>
7472 <P>
7473 You can experiment with this option by piping to something simple like the
7474 Unix "cat" command.
7475 </DD>
7476 <DT>Captured Output or Free Output</DT>
7477 <DD>This option toggles between having Alpine capture the output of
7478 the Unix pipe command for display, and not capturing it.
7479 If the command you are piping to is a filter that will produce output
7480 you want to view, then you want to capture that output
7481 for display (the default).
7482 If the Unix command doesn't produce output or handles the display itself,
7483 then you want free output.
7484 When you've selected the Free Output option the prompt will change to
7485 <P>
7486 <CENTER><SAMP>Pipe messages to (uncaptured) :</SAMP></CENTER>
7487 <P>
7488 </DD>
7489 <DT>No Delimiter or With Delimiter</DT>
7490 <DD>This option controls whether or not a Unix mailbox style delimiter
7491 will come before the text of the message.
7492 This is the delimiter used in the common Unix mailbox format.
7493 It's the single line that begins with the five characters
7494 "From" followed by a <SPACE> character.
7495 You'll usually only want to include this if the Unix command requires
7496 input in the format of a traditional Unix mailbox file.
7497 When you've selected the With Delimiter option the prompt will change to
7498 <P>
7499 <CENTER><SAMP>Pipe messages to (delimited) :</SAMP></CENTER>
7500 <P>
7501 </DD>
7502 <DT>To Same Pipe or To Individual Pipes</DT>
7503 <DD>This option only shows up if you are running an aggregate
7504 pipe command.
7505 That is, the command was Apply Pipe, not just Pipe.
7506 You have the option of piping all of the selected messages through a
7507 single pipe to a single instance of the Unix command,
7508 or piping each individual message through a separate pipe to separate
7509 instances of the Unix command.
7510 The default is that all of the output will go through a single pipe
7511 to a single instance of the command.
7512 You can try this option with a command like "less", with Free
7513 Output enabled.
7514 When you've selected the Individual Pipes option the prompt will change to
7515 <P>
7516 <CENTER><SAMP>Pipe messages to (new pipe) :</SAMP></CENTER>
7517 <P>
7518 </DD>
7519 </DL>
7521 <P>
7522 As mentioned earlier, the options can be combined in any way you wish.
7523 You may leave them all off, turn them all on, or turn some of them on
7524 and some of them off.
7525 If you use the pipe command a second time in the same session the default
7526 options will be what you used the last time.
7528 <P>
7529 <End of help on this topic>
7530 </BODY>
7531 </HTML>
7532 ========== h_emptydir_subfolder_name =========
7533 <HTML>
7534 <HEAD>
7535 <TITLE>ENTER SUBFOLDER NAME</TITLE>
7536 </HEAD>
7537 <BODY>
7538 <H1>Enter Subfolder Name</H1>
7540 <P>
7541 This is the name of a new subfolder in the directory you are creating.
7542 Because empty directories are hidden and therefore not useful, you must also
7543 create a subfolder in the directory you are creating in order that the
7544 directory remains visible.
7545 <P>
7546 Alternatively, you may turn off the configuration feature
7547 <A HREF="h_config_quell_empty_dirs"><!--#echo var="FEAT_quell-empty-directories"--></A>
7548 so that empty directories remain visible.
7549 If you do that, you will not be required to create the subfolder when you
7550 create a directory.
7552 <P>
7553 <End of help on this topic>
7554 </BODY>
7555 </HTML>
7556 ========== h_incoming_add_folder_name =========
7557 <HTML>
7558 <HEAD>
7559 <TITLE>ENTER FOLDER NAME</TITLE>
7560 </HEAD>
7561 <BODY>
7562 <H1>Enter Folder Name</H1>
7564 <P>
7565 This is the name of the folder on the previously specified server.
7566 By default the folder name is interpreted as defining a section of your personal
7567 folder area. This area and how you specify it are defined by the
7568 server, if one is specified.
7570 <P>
7571 To define a folder outside the default area, prefix
7572 the path with the namespace to use when interpreting the
7573 given path. If a namespace is specified, the folder name begins with the
7574 sharp (#) character followed by the name of the namespace
7575 and then the namespace's path-element-delimiter. Aside from the
7576 name's format, namespaces can also imply access rights, content
7577 policy, audience, location, and, occasionally, access methods.
7579 <P>
7580 Each server exports its own set (possibly of size one) of
7581 namespaces.
7582 For a more detailed explanation read about
7583 <A HREF="h_folder_name_namespaces">Namespaces</A>.
7585 <P>
7586 To specify the default for INBOX on the server you can usually just enter
7587 "INBOX", and the server will understand the special meaning of
7588 that word.
7590 <P>
7591 <End of help on this topic>
7592 </BODY>
7593 </HTML>
7594 ========== h_incoming_add_folder_host =========
7595 <HTML>
7596 <HEAD>
7597 <TITLE>ENTER INCOMING FOLDER SERVER</TITLE>
7598 </HEAD>
7599 <BODY>
7600 <H1>Enter Incoming Folder Server</H1>
7602 You are being asked for the name of the server for use with this incoming
7603 folder.
7604 If the folder is on the machine where Alpine is running, then just enter
7605 RETURN without typing a server name.
7607 <P>
7608 If the folder is on an IMAP server then type the server's name followed
7609 by RETURN.
7610 You may use the ^X command if the server is the same as the server that
7611 the INBOX is on.
7613 <P>
7614 You may have to add optional extra information to the server name.
7615 For example, if the IMAP server is using a non-standard port number you
7616 would specify that by appending a colon (:) followed by the port number
7617 to the server name
7619 <P>
7620 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7621 <P>
7623 or you may need to specify a different protocol if the server is not an
7624 IMAP server. For example:
7626 <P>
7627 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7628 <P>
7630 for a POP server or
7632 <P>
7633 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7634 <P>
7636 for an NNTP news server.
7637 For an explanation of all of the possibilities, see
7638 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7639 for folders.
7641 <P>
7642 There is a special command (^W) if you want to set up a folder that gets its
7643 mail from a
7644 <A HREF="h_maildrop">Mail Drop</A>.
7645 If you type that command, you will be prompted for the information for
7646 both the Mail Drop folder and the destination folder.
7648 <P>
7649 <End of help on this topic>
7650 </BODY>
7651 </HTML>
7652 ========== h_incoming_add_inbox =========
7653 <HTML>
7654 <HEAD>
7655 <TITLE>ENTER INBOX SERVER</TITLE>
7656 </HEAD>
7657 <BODY>
7658 <H1>Enter INBOX Server</H1>
7660 You are being asked for the name of the server for use with
7661 the INBOX folder.
7662 Type the server's name followed by RETURN.
7664 <P>
7665 You may have to add optional extra information to the server name.
7666 For example, if the server is using a non-standard port number you
7667 would specify that by appending a colon (:) followed by the port number
7668 to the server name
7670 <P>
7671 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7672 <P>
7674 or you may need to specify a different protocol if the server is not an
7675 IMAP server. For example:
7677 <P>
7678 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7679 <P>
7681 for a POP server.
7682 <P>
7684 For an explanation of all of the possibilities, see
7685 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7686 for folders.
7688 <P>
7689 If the INBOX folder is on the machine where Alpine is running, then just enter
7690 RETURN without typing a server name.
7692 <P>
7693 There is a special command (^W) if you want to set up a folder that gets its
7694 mail from a
7695 <A HREF="h_maildrop">Mail Drop</A>.
7696 If you type that command, you will be prompted for the information for
7697 both the Mail Drop folder and the destination folder, which will be used
7698 as your INBOX folder.
7700 <P>
7701 <End of help on this topic>
7702 </BODY>
7703 </HTML>
7704 ========== h_incoming_add_maildrop_destn =========
7705 <HTML>
7706 <HEAD>
7707 <TITLE>ENTER DESTINATION SERVER</TITLE>
7708 </HEAD>
7709 <BODY>
7710 <H1>Enter Destination Server</H1>
7712 You are being asked for the name of the server where the destination
7713 folder is for use with this Mail Drop incoming folder.
7714 That is, you are using a Mail Drop for this incoming folder and
7715 you've already entered
7716 the server and folder name for the Mail Drop.
7717 Now you need to enter the server for the destination folder
7718 where the mail should be copied to.
7719 Mail will come from the Mail Drop and be copied to the destination folder.
7721 <P>
7722 Type the server's name followed by RETURN.
7723 If the folder is local to this computer, just type RETURN without entering
7724 a server name.
7726 <P>
7727 You may have to add optional extra information to the server name.
7728 For example, if the server is using a non-standard port number you
7729 would specify that by appending a colon (:) followed by the port number
7730 to the server name
7732 <P>
7733 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7734 <P>
7736 For an explanation of all of the possibilities, see
7737 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7738 for folders.
7740 <P>
7741 <End of help on this topic>
7742 </BODY>
7743 </HTML>
7744 ========== h_inbox_add_maildrop_destn =========
7745 <HTML>
7746 <HEAD>
7747 <TITLE>ENTER DESTINATION SERVER</TITLE>
7748 </HEAD>
7749 <BODY>
7750 <H1>Enter Destination Server</H1>
7752 You are being asked for the name of the server where the destination
7753 folder is for use with your Mail Drop INBOX.
7754 That is, you are using a Mail Drop for your INBOX and you've already entered
7755 the server and folder name for the Mail Drop.
7756 Now you need to enter the server for the destination folder
7757 where the mail should be copied to.
7758 Mail will come from the Mail Drop and be copied to the destination folder.
7760 <P>
7761 Type the server's name followed by RETURN.
7762 If the folder is local to this computer, just type RETURN without entering
7763 a server name.
7765 <P>
7766 You may have to add optional extra information to the server name.
7767 For example, if the server is using a non-standard port number you
7768 would specify that by appending a colon (:) followed by the port number
7769 to the server name
7771 <P>
7772 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7773 <P>
7775 For an explanation of all of the possibilities, see
7776 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7777 for folders.
7779 <P>
7780 <End of help on this topic>
7781 </BODY>
7782 </HTML>
7783 ========== h_inbox_add_maildrop =========
7784 <HTML>
7785 <HEAD>
7786 <TITLE>ENTER MAILDROP SERVER</TITLE>
7787 </HEAD>
7788 <BODY>
7789 <H1>Enter Mail Drop Server</H1>
7791 You are being asked for the name of the Mail Drop server for use with
7792 your INBOX.
7794 <P>
7795 Type the server's name followed by RETURN.
7797 <P>
7798 You may have to add optional extra information to the server name.
7799 For example, if the server is using a non-standard port number you
7800 would specify that by appending a colon (:) followed by the port number
7801 to the server name
7803 <P>
7804 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7805 <P>
7807 or you may need to specify a different protocol if the server is not an
7808 IMAP server. For example:
7810 <P>
7811 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7812 <P>
7814 for a POP server or
7816 <P>
7817 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7818 <P>
7820 for an NNTP news server.
7821 For an explanation of all of the possibilities, see
7822 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7823 for folders.
7825 <P>
7826 <End of help on this topic>
7827 </BODY>
7828 </HTML>
7829 ========== h_incoming_add_maildrop =========
7830 <HTML>
7831 <HEAD>
7832 <TITLE>ENTER MAILDROP SERVER</TITLE>
7833 </HEAD>
7834 <BODY>
7835 <H1>Enter Mail Drop Server</H1>
7837 You are being asked for the name of the Mail Drop server for use with
7838 this incoming folder.
7840 <P>
7841 Type the server's name followed by RETURN.
7842 You may use the ^X command if the server is the same as the server that
7843 the INBOX is on.
7845 <P>
7846 You may have to add optional extra information to the server name.
7847 For example, if the server is using a non-standard port number you
7848 would specify that by appending a colon (:) followed by the port number
7849 to the server name
7851 <P>
7852 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7853 <P>
7855 or you may need to specify a different protocol if the server is not an
7856 IMAP server. For example:
7858 <P>
7859 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7860 <P>
7862 for a POP server or
7864 <P>
7865 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7866 <P>
7868 for an NNTP news server.
7869 For an explanation of all of the possibilities, see
7870 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7871 for folders.
7873 <P>
7874 If the Mail Drop folder is on the machine where Alpine is running, then just enter
7875 RETURN without typing a server name.
7877 <P>
7878 <End of help on this topic>
7879 </BODY>
7880 </HTML>
7881 ========== h_maildrop =========
7882 <HTML>
7883 <HEAD>
7884 <TITLE>WHAT IS A MAIL DROP?</TITLE>
7885 </HEAD>
7886 <BODY>
7887 <H1>What is a Mail Drop?</H1>
7889 In some situaions it may make sense to have your mail delivered to one
7890 folder (the Mail Drop) and then when you want to read mail that has been
7891 delivered to the Mail Drop folder Alpine will move it to another
7892 destination folder.
7893 Often the Mail Drop will be a remote folder and messages will be moved from
7894 there to a local destination folder.
7896 <P>
7897 One example where this might make sense is if the Mail Drop folder is accessible
7898 only with the POP protocol.
7899 You could designate your POP inbox as the Mail Drop folder and have Alpine move
7900 mail from there to a local (on the same machine Alpine is running on)
7901 destination folder, where you'll read it.
7903 <P>
7904 A Mail Drop may only be used as your Inbox or as an
7905 <A HREF="h_config_enable_incoming">"Incoming folder"</A>.
7907 <P>
7908 There is no attempt to synchronize the contents of the destination folder
7909 with the contents of the Mail Drop folder.
7910 All that happens is that all of the messages in the Mail Drop folder are
7911 copied to the destination folder and then they are deleted and expunged (if possible)
7912 from the Mail Drop folder.
7913 The next time a check for new mail is made, any messages in the Mail
7914 Drop folder are once again copied to the destination folder and deleted
7915 and expunged from the Mail Drop folder.
7916 (If the Mail Drop folder is a news group, then the messages can't be
7917 expunged from the newsgroup. Instead, only Recent messages are copied from
7918 the newsgroup to the destination folder.)
7920 <P>
7921 Configuration of a Mail Drop is a little different from configuration of
7922 a folder that does not use a Mail Drop because you have to specify two
7923 folder names instead of one.
7924 The two folders may be any types of folders that Alpine can normally use.
7925 They don't have to be a remote folder and a local folder, that is
7926 simply the most common usage.
7927 When you use a Mail Drop folder Alpine will periodically re-open the Mail
7928 Drop to check for new mail.
7929 The new-mail checks will happen at the frequency set with the
7930 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option,
7931 but with a minimum time
7932 (<A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>)
7933 between checks.
7934 Because of this minimum you may notice that new mail does not
7935 appear promptly when you expect it.
7936 The reason for this is to protect the server from over-zealous opening and
7937 closing of the Mail Drop folder.
7938 If the user initiates the check by typing ^L (Ctrl-L) or the Next command when at
7939 the end of the folder index, then the check will happen, regardless of how
7940 long it has been since the previous check.
7941 <P>
7942 If there is new mail, that mail will be copied to the destination folder
7943 and then will be deleted from the Mail Drop.
7944 Note that using a Mail Drop with a local destination folder does not make
7945 sense if you read mail from more than one machine, because the mail is
7946 downloaded to the destination folder (which is accessible from only one
7947 machine) and deleted from the Mail Drop.
7948 <P>
7949 The feature <A HREF="h_config_maildrops_preserve_state"><!--#echo var="FEAT_maildrops-preserve-state"--></A> modifies the operation of Mail Drops.
7951 <P>
7952 The actual syntax used by Alpine for a folder that uses a Mail Drop is:
7954 <P>
7955 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
7956 <P>
7957 The brackets are not literal.
7958 <P>
7959 <CENTER><SAMP><DELIM></SAMP></CENTER>
7960 <P>
7961 is a single character that does not appear in the MailDropFolder name.
7962 If the name doesn't contain spaces then it can be a space character.
7963 The two folder names are full technical
7964 <A HREF="h_valid_folder_names">folder names</A>
7965 as used by Alpine.
7966 Here are a couple examples to give you an idea what is being talked about:
7968 <P>
7969 <CENTER><SAMP>#move {popserver.example.com/pop3}inbox localfolder</SAMP></CENTER>
7970 <P>
7971 <CENTER><SAMP>#move+{nntpserver.example.com/nntp}#news.comp.mail.pine+local folder</SAMP></CENTER>
7972 <P>
7974 A #move folder may only be used as an
7975 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
7976 an Inbox.
7977 When you are in the FOLDER LIST of Incoming Message Folders (after turning
7978 on the
7979 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
7980 option)
7981 the Add command has a subcommand "Use Mail Drop"
7982 which may be helpful for defining the folder in your Alpine configuration.
7983 The same is true when you edit the
7984 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
7985 option in Setup/Config.
7986 Each of these configuration methods will also create the DestinationFolder
7987 if it doesn't already exist.
7988 If you are having problems, make sure the DestinationFolder exists.
7990 <P>
7991 <End of help on this topic>
7992 </BODY>
7993 </HTML>
7994 ========== h_save =========
7995 <HTML>
7996 <HEAD>
7997 <TITLE>CHOOSE A FOLDER TO SAVE INTO</TITLE>
7998 </HEAD>
7999 <BODY>
8000 <H1>Choose a Folder to Save Into</H1>
8002 After Exiting from this help text,
8003 type the name of the folder you want to save into and press RETURN.
8004 <P>
8005 Press ^T to get a list of your folders to choose from.
8006 Press ^C to cancel the Save.
8007 <P>
8008 If you have Folder Collections defined you may use
8009 Ctrl-P (Previous collection) and Ctrl-N (Next collection) to switch
8010 the collection being saved to.
8011 <P>
8012 If Tab Completion is enabled (it is enabled by default)
8013 you may type a Tab character to have Alpine complete the folder name for you.
8014 <P>
8015 If Partial Match Lists is enabled (it is enabled by default) you may type
8016 Ctrl-X to get a list of matches to the prefix you've typed in so far.
8017 <P>
8018 If the Ctrl-R subcommand is present that means you can decide to Delete or
8019 not Delete the message you are saving after you save it.
8020 The label on that key gives the action to switch to.
8021 If it says Delete and you type Ctrl-R the label displayed will change to
8022 No Delete and the source message will be deleted after the save. If it
8023 says No Delete and you type Ctrl-R the label displayed will change to
8024 Delete and the message will not be deleted.
8025 You can control the default for the Delete parameter with the
8026 configuration feature <!--#echo var="FEAT_save-will-not-delete"-->.
8027 <P>
8028 Similarly, if the Ctrl-W subcommand is present that means you can decide
8029 to Preserve the order of the messages being saved or not.
8030 If it is labeled Preserve Order and you type Ctrl-W, the resulting Saved messages
8031 will be in the same order as you see them in the source folder now.
8032 The opposite action (which is usually the default) is that you don't care
8033 about the order.
8034 The Saved messages may or may not be in the same order in the destination folder.
8035 There may be a performance penalty for choosing to save the messages in order.
8036 You can control the default for the Preserve Order parameter with the
8037 configuration feature
8038 <!--#echo var="FEAT_save-aggregates-copy-sequence"-->.
8040 <P>
8041 If you haven't disabled the Save Input History and you've already done a
8042 Save earlier in this session then you may use the Up and Down arrows to retrieve
8043 a folder name used in a previous Save.
8045 <P>
8046 <End of help on this topic>
8047 </BODY>
8048 </HTML>
8049 ============= h_simple_index ========================
8050 <HTML>
8051 <HEAD>
8052 <TITLE>SELECT POSTPONED MESSAGE</TITLE>
8053 </HEAD>
8054 <BODY>
8055 <H1>POSTPONED MESSAGE SELECTION COMMANDS</H1>
8056 <!--chtml if pinemode="function_key"-->
8057 <PRE>
8058 Navigating the List of Messages General Alpine Commands
8059 ------------------------------- -----------------------
8060 F5 Move to previous message F1 Show this help text
8061 F6 Move to next message
8062 F7 Show previous screen of messages
8063 F8 Show next screen of messages
8065 Message Selection Commands
8066 --------------------------
8067 F3 Exit the Message Select menu (canceling Send command)
8068 F4 Select the currently highlighted message
8069 F9 Mark the currently highlighted message as deleted
8070 F10 Undelete (remove deletion mark from) the highlighted message
8071 </PRE>
8072 <!--chtml else-->
8073 <PRE>
8074 Navigating the List of Messages General Alpine Commands
8075 ------------------------------- -----------------------
8076 P Move to previous message ? Show this help text
8077 N Move to next message
8078 - Show previous screen of messages
8079 Spc (space bar) Show next screen of messages
8081 Message Selection Commands
8082 --------------------------
8083 E Exit the Message Select menu (canceling Send command)
8084 S Select the currently highlighted message
8085 D Mark the currently highlighted message as deleted
8086 U Undelete (remove deletion mark from) the highlighted message
8087 </PRE>
8088 <!--chtml endif-->
8089 <P>
8090 <H2>Description of the Select Postponed Message Screen</H2>
8092 This screen allows you to select one of several previously postponed
8093 messages in order to continue composition. Your options are very limited
8094 -- the screen is not meant to let you manipulate these messages. However,
8095 you may now delete messages from this list. Once you choose a message,
8096 Alpine reads it in and puts you into the regular message composer.
8097 <P>
8099 Messages do not stay in this postponed state automatically. If you select
8100 a message and then want to postpone it again, use the normal postpone
8101 (Ctrl-O) command in the composer.
8102 <P>
8104 If you exit this screen without selecting a message, the Compose command
8105 that got you here is canceled. Other than messages explicitly marked
8106 "Deleted", no messages will be removed.
8108 <P>
8109 <End of help on this topic>
8110 </BODY>
8111 </HTML>
8112 ============= h_collection_screen ========================
8113 <HTML>
8114 <HEAD>
8115 <TITLE>COLLECTION LIST screen</TITLE>
8116 </HEAD>
8117 <BODY>
8118 <H1>COLLECTION LIST screen</H1>
8120 The COLLECTION LIST screen is used to select one of your
8121 collection definitions to display the folders they contain. See
8122 <A HREF="h_what_are_collections">Folder Collections Explained</A> for
8123 detailed explanation of collections.<P>
8125 To manage your collection definitions (Add, Change, Delete, etc.), use
8126 the <A HREF="h_collection_maint">Setup/collectionList</A> command on Alpine's
8127 MAIN MENU.
8129 <P>
8130 <End of help on this topic>
8131 </BODY>
8132 </HTML>
8133 ============= h_collection_maint ========================
8134 <HTML>
8135 <HEAD>
8136 <TITLE>SETUP COLLECTION LIST screen</TITLE>
8137 </HEAD>
8138 <BODY>
8139 <H1>SETUP COLLECTION LIST screen</H1>
8141 The SETUP COLLECTION LIST screen lets you manage your collection
8142 definitions. See
8143 <A HREF="h_what_are_collections">Folder Collections Explained</A>
8144 for detailed explanation of collections.<P>
8146 Maintenance commands include:
8147 <DL>
8148 <DT>Change
8149 <!--chtml if pinemode="function_key"-->
8150 (F4)
8151 <!--chtml else-->
8152 (C)
8153 <!--chtml endif-->
8154 </DT>
8156 <DD>Modify attributes of the selected collection definition.
8158 <DT>Add Cltn
8159 <!--chtml if pinemode="function_key"-->
8160 (F9)
8161 <!--chtml else-->
8162 (A)
8163 <!--chtml endif-->
8164 </DT>
8166 <DD>Create a new collection definition.
8167 </DD>
8169 <DT>Del Cltn
8170 <!--chtml if pinemode="function_key"-->
8171 (F10)
8172 <!--chtml else-->
8173 (D)
8174 <!--chtml endif-->
8175 </DT>
8177 <DD>Delete the selected collection definition.<BR>
8178 NOTE: The folders and directories referred to by the
8179 collection definition are <EM>NOT</EM> deleted. Folders must
8180 be deleted, if that's what you wish to do, from the
8181 <A HREF="h_folder_maint">FOLDER LIST screen</A>, which shows the
8182 individual folders in a collection.
8183 </DD>
8185 <DT>Shuffle
8186 <!--chtml if pinemode="function_key"-->
8187 (F11)
8188 <!--chtml else-->
8189 ($)
8190 <!--chtml endif-->
8191 </DT>
8193 <DD>Change the order of the displayed collections. Alpine will offer
8194 to move the currently selected collection one position UP
8195 or DOWN.
8196 </DD>
8197 </DL>
8199 <P>
8200 <End of help on this topic>
8201 </BODY>
8202 </HTML>
8203 ============ h_what_are_collections ==========
8204 <HTML>
8205 <HEAD>
8206 <TITLE>Folder Collections Explained</TITLE>
8207 </HEAD>
8208 <BODY>
8209 <H1>Folder Collections Explained</H1>
8212 Those of you with simple mail configurations will just see a list of all the
8213 folders you have when choosing FOLDER LIST from Alpine's MAIN MENU.
8214 The special folders for INBOX, sent mail and saved messages
8215 will appear at the top of the list. All others are in alphabetical order.
8216 <P>
8217 If you
8218 or your system administrator have defined more than one collection or if
8219 you have a collection (for newsgroups or email folders) defined on your
8220 system, then you will see the COLLECTION LIST screen first when choosing
8221 FOLDER LIST from Alpine's MAIN MENU.
8222 <P>
8223 <H2>Why have multiple folder collections?</H2>
8224 <P>
8225 For Alpine users who only maintain email folders (and not too many) on one host,
8226 a single folder collection is probably sufficient.<P>
8228 However, people who have more than one email account - for example, one
8229 at their university, and one with their personal Internet Service Provider -
8230 will have different sets of folders on different hosts, and they may want to
8231 access them all from the same installation of Alpine, rather than use different
8232 software and/or log into other hosts to manipulate messages in different
8233 accounts. (If in doubt whether one of your email accounts can be accessed
8234 with Alpine, contact the technical support people for that account.) Even people
8235 who have only one email account on one host, but have dozens or
8236 hundreds of email folders, may want to arrange these folders together in a
8237 meaningful way.<BR>
8238 That is where multiple collections come in.
8240 <H2>Types of Collections</H2>
8241 <DL>
8242 <DT>INCOMING FOLDERS</DT>
8243 <DD>"Incoming Message Folders"
8244 is a special collection typically used to supplement your single INBOX.
8245 All the folders here are meant to be ones that receive incoming messages,
8246 which you intend to check more or less frequently.
8247 You may have multiple folders like this because you or your systems
8248 administrator have set up an external program or you may have set up
8249 Alpine to filter incoming
8250 messages into different folders, based on certain criteria such as
8251 sender, recipient, or subject; or because you have multiple accounts and
8252 wish to check their INBOXes easily. This collection is established by
8253 setting the
8254 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
8255 feature in the SETUP CONFIGURATION screen, which is accessed from the
8256 MAIN MENU.
8257 </DD>
8259 <DT>NEWS</DT>
8260 <DD>You can also define a collection specifically for
8261 newsgroups. Alpine does this for you implicitly when you
8262 <A HREF="h_config_nntp_server">define an NNTP Server</A>
8263 in your Alpine configuration. The news collection appears last in the
8264 COLLECTION LIST (though you can shuffle it up in the order of presentation),
8265 and Alpine knows not to save messages there.
8266 </DD>
8268 <DT>DEFAULT COLLECTION</DT>
8269 <DD>This is the default collection for your saved and sent messages folders.
8270 </DD>
8271 </DL>
8273 <P>
8275 <H2>Defining Collections</H2>
8276 <P>
8277 In the absence of any folder-collection definitions, Alpine will assume a
8278 single default folder collection.
8279 <!--chtml if pinemode="os_windows"-->
8280 <!--chtml else-->
8281 If necessary, Alpine will create the directory
8282 "mail" in your Unix home directory
8283 to hold your folders.
8284 <!--chtml endif-->
8285 <P>
8286 You can use the
8287 <A HREF="h_collection_maint">Setup/collectionList screen</A>, called up from
8288 the MAIN MENU, to manage your collection list.
8289 <P>
8290 <End of help on this topic>
8291 </BODY>
8292 </HTML>
8293 ===== h_select_address_screen =====
8294 <HTML>
8295 <HEAD>
8296 <TITLE>SELECT AN ADDRESS SCREEN</TITLE>
8297 </HEAD>
8298 <BODY>
8299 <H1>SELECT AN ADDRESS SCREEN</H1>
8300 <H2>COMMANDS</H2>
8301 <!--chtml if pinemode="function_key"-->
8302 <PRE>
8303 Available Commands
8304 -------------------------------
8305 F1 Show Help Text
8306 F3 Exit without selecting anything
8307 F4 Select the highlighted address
8308 F5 Move highlight to previous address
8309 F6 Move highlight to next address
8310 F7 Previous page of addresses
8311 F8 Next page of addresses
8312 F11 Print
8313 F12 WhereIs
8314 </PRE>
8315 <!--chtml else-->
8316 <PRE>
8317 Navigation General Alpine Commands
8318 ------------------------- -----------------------
8319 P Prev Address ? Display this help text
8320 N Next Address E Exit without selecting anything
8321 - Previous page % Print
8322 Spc (space bar) Next page
8323 W WhereIs
8325 Select Command
8326 ------------------------------------------------
8327 S Select the highlighted address
8328 </PRE>
8329 <!--chtml endif-->
8331 <H2>Description of the Select Address Screen</H2>
8333 This screen gives you an easy way to select an address from all of
8334 the address book entries that match the prefix typed so far.
8336 <P><UL>
8337 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8338 </UL>
8339 <P>
8340 <End of help on this topic>
8341 </BODY>
8342 </HTML>
8343 ===== h_select_rule_screen =====
8344 <HTML>
8345 <HEAD>
8346 <TITLE>SELECT A RULE SCREEN</TITLE>
8347 </HEAD>
8348 <BODY>
8349 <H1>SELECT A RULE SCREEN</H1>
8350 <H2>COMMANDS</H2>
8351 <!--chtml if pinemode="function_key"-->
8352 <PRE>
8353 Available Commands
8354 -------------------------------
8355 F1 Show Help Text
8356 F3 Exit without selecting anything
8357 F4 Select the highlighted rule
8358 F5 Move highlight to previous rule
8359 F6 Move highlight to next rule
8360 F7 Previous page of rules
8361 F8 Next page of rules
8362 F11 Print
8363 F12 WhereIs
8364 </PRE>
8365 <!--chtml else-->
8366 <PRE>
8367 Navigation General Alpine Commands
8368 ------------------------- -----------------------
8369 P Prev Rule ? Display this help text
8370 N Next Rule E Exit without selecting anything
8371 - Previous page % Print
8372 Spc (space bar) Next page
8373 W WhereIs
8375 Select Command
8376 ------------------------------------------------
8377 S Select the highlighted rule
8378 </PRE>
8379 <!--chtml endif-->
8381 <H2>Description of the Select Rule Screen</H2>
8383 This screen just gives you an easy way to select a rule from all of your
8384 defined rules.
8385 The list of rules presented is the list of nicknames of all of the rules
8386 defined using Setup/Rules.
8387 For selecting messages, it is likely that the Indexcolor rules and possibly
8388 the Roles rules will be most useful.
8389 The others are there also, in case you find a use for them.
8390 <P>
8391 In order for this to be useful for selecting messages, the nicknames of
8392 the rules have to be different.
8393 Alpine actually just gets the nickname of the rule that you select and then
8394 looks up that rule using the nickname.
8395 So if there are duplicate nicknames, the first rule that has that
8396 nickname will be used.
8398 <P><UL>
8399 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8400 </UL>
8401 <P>
8402 <End of help on this topic>
8403 </BODY>
8404 </HTML>
8405 ===== h_select_priority_screen =====
8406 <HTML>
8407 <HEAD>
8408 <TITLE>SELECT A PRIORITY SCREEN</TITLE>
8409 </HEAD>
8410 <BODY>
8411 <H1>SELECT A PRIORITY SCREEN</H1>
8412 <H2>COMMANDS</H2>
8413 <!--chtml if pinemode="function_key"-->
8414 <PRE>
8415 Available Commands
8416 -------------------------------
8417 F1 Show Help Text
8418 F3 Exit without selecting anything
8419 F4 Select the highlighted priority
8420 F5 Move highlight to previous priority
8421 F6 Move highlight to next priority
8422 F7 Previous page of priorities
8423 F8 Next page of priorities
8424 F11 Print
8425 F12 WhereIs
8426 </PRE>
8427 <!--chtml else-->
8428 <PRE>
8429 Navigation General Alpine Commands
8430 ------------------------- -----------------------
8431 P Prev Priority ? Display this help text
8432 N Next Priority E Exit without selecting anything
8433 - Previous page % Print
8434 Spc (space bar) Next page
8435 W WhereIs
8437 Select Command
8438 ------------------------------------------------
8439 S Select the highlighted priority
8440 </PRE>
8441 <!--chtml endif-->
8443 <H2>Description of the Select Priority Screen</H2>
8445 This screen gives you a way to select a priority for the message you are sending.
8446 This priority will be placed in the non-standard X-Priority header of your outgoing mail.
8447 Some mail programs will display an indication of the priority level to
8448 the recipient of the message, some will ignore it.
8449 Even in cases where the mail programs of both the sender and the recipient
8450 agree on the meaning of this header, keep in mind that it is
8451 something that the sender sets so it is only an indication
8452 of the priority that the sender attaches to the mail.
8453 Alpine can be made to display an indication of this priority in incoming
8454 messages by use of one of the tokens
8455 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
8456 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
8457 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
8459 <P><UL>
8460 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8461 </UL>
8462 <P>
8463 <End of help on this topic>
8464 </BODY>
8465 </HTML>
8466 ===== h_select_keyword_screen =====
8467 <HTML>
8468 <HEAD>
8469 <TITLE>SELECT A KEYWORD SCREEN</TITLE>
8470 </HEAD>
8471 <BODY>
8472 <H1>SELECT A KEYWORD SCREEN</H1>
8473 <H2>COMMANDS</H2>
8474 <!--chtml if pinemode="function_key"-->
8475 <PRE>
8476 Available Commands
8477 -------------------------------
8478 F1 Show Help Text
8479 F3 Exit without selecting anything
8480 F4 Select the highlighted keyword
8481 F5 Move highlight to previous keyword
8482 F6 Move highlight to next keyword
8483 F7 Previous page of keywords
8484 F8 Next page of keywords
8485 F11 Print
8486 F12 WhereIs
8487 </PRE>
8488 <!--chtml else-->
8489 <PRE>
8490 Navigation General Alpine Commands
8491 ------------------------- -----------------------
8492 P Prev Keyword ? Display this help text
8493 N Next Keyword E Exit without selecting anything
8494 - Previous page % Print
8495 Spc (space bar) Next page
8496 W WhereIs
8498 Select Command
8499 ------------------------------------------------
8500 S Select the highlighted keyword
8501 </PRE>
8502 <!--chtml endif-->
8504 <H2>Description of the Select Keyword Screen</H2>
8506 This screen just gives you an easy way to select a keyword.
8507 The list of keywords presented is the list of all keywords defined in your
8508 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8509 If you have given a keyword a nickname, that nickname is displayed
8510 instead of the actual keyword.
8512 <P><UL>
8513 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8514 </UL>
8515 <P>
8516 <End of help on this topic>
8517 </BODY>
8518 </HTML>
8519 ===== h_select_charset_screen =====
8520 <HTML>
8521 <HEAD>
8522 <TITLE>SELECT A CHARACTER SET SCREEN</TITLE>
8523 </HEAD>
8524 <BODY>
8525 <H1>SELECT A CHARACTER SET SCREEN</H1>
8526 <H2>COMMANDS</H2>
8527 <!--chtml if pinemode="function_key"-->
8528 <PRE>
8529 Available Commands
8530 -------------------------------
8531 F1 Show Help Text
8532 F3 Exit without selecting anything
8533 F4 Select the highlighted character set
8534 F5 Move highlight to previous character set
8535 F6 Move highlight to next character set
8536 F7 Previous page of character sets
8537 F8 Next page of character sets
8538 F11 Print
8539 F12 WhereIs
8540 </PRE>
8541 <!--chtml else-->
8542 <PRE>
8543 Navigation General Alpine Commands
8544 ------------------------- -----------------------
8545 P Prev Character Set ? Display this help text
8546 N Next Character Set E Exit without selecting anything
8547 - Previous page % Print
8548 Spc (space bar) Next page
8549 W WhereIs
8551 Select Command
8552 ------------------------------------------------
8553 S Select the highlighted character set
8554 </PRE>
8555 <!--chtml endif-->
8557 <H2>Description of the Select A Character Set Screen</H2>
8559 This screen just gives you an easy way to select a character set from the
8560 set of character sets Alpine knows about.
8561 The list presented will vary slightly depending on what option you are
8562 selecting the character set for.
8564 <P><UL>
8565 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8566 </UL>
8567 <P>
8568 <End of help on this topic>
8569 </BODY>
8570 </HTML>
8571 ===== h_select_multcharsets_screen =====
8572 <HTML>
8573 <HEAD>
8574 <TITLE>SELECT CHARACTER SETS SCREEN</TITLE>
8575 </HEAD>
8576 <BODY>
8577 <H1>SELECT CHARACTER SETS SCREEN</H1>
8578 <H2>COMMANDS</H2>
8579 <!--chtml if pinemode="function_key"-->
8580 <PRE>
8581 Available Commands
8582 -------------------------------
8583 F1 Show Help Text
8584 F3 Exit without selecting anything
8585 F4 Select the highlighted charset (or chosen charsets in ListMode)
8586 F5 Move highlight to previous charset
8587 F6 Move highlight to next charset
8588 F7 Previous page of charsets
8589 F8 Next page of charsets
8590 F9 Toggle choices when using ListMode
8591 F10 Turn on/off ListMode (makes it easy to choose multiple charsets)
8592 F11 Print
8593 F12 WhereIs
8594 </PRE>
8595 <!--chtml else-->
8596 <PRE>
8597 Navigation General Alpine Commands
8598 ------------------------- -----------------------
8599 P Prev Charset ? Display this help text
8600 N Next Charset E Exit without selecting anything
8601 - Previous page % Print
8602 Spc (space bar) Next page
8603 W WhereIs
8605 Select Command
8606 ------------------------------------------------
8607 S Select the highlighted charset (or chosen charsets in ListMode)
8608 L Turn on ListMode (makes it easy to choose multiple charsets)
8609 1 Turn off ListMode
8610 X Toggle choices when using ListMode
8611 </PRE>
8612 <!--chtml endif-->
8614 <H2>Description of the Select Character Set Screen</H2>
8616 This screen just gives you an easy way to select a character set or a list of
8617 character sets.
8618 The list of character sets presented is the list of all character sets known to
8619 Alpine.
8620 You may select other character sets by typing them in directly.
8622 <P><UL>
8623 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8624 </UL>
8625 <P>
8626 <End of help on this topic>
8627 </BODY>
8628 </HTML>
8629 ===== h_select_multkeyword_screen =====
8630 <HTML>
8631 <HEAD>
8632 <TITLE>SELECT KEYWORDS SCREEN</TITLE>
8633 </HEAD>
8634 <BODY>
8635 <H1>SELECT KEYWORDS SCREEN</H1>
8636 <H2>COMMANDS</H2>
8637 <!--chtml if pinemode="function_key"-->
8638 <PRE>
8639 Available Commands
8640 -------------------------------
8641 F1 Show Help Text
8642 F3 Exit without selecting anything
8643 F4 Select the highlighted keyword (or chosen keywords in ListMode)
8644 F5 Move highlight to previous keyword
8645 F6 Move highlight to next keyword
8646 F7 Previous page of keywords
8647 F8 Next page of keywords
8648 F9 Toggle choices when using ListMode
8649 F10 Turn on/off ListMode (makes it easy to choose multiple keywords)
8650 F11 Print
8651 F12 WhereIs
8652 </PRE>
8653 <!--chtml else-->
8654 <PRE>
8655 Navigation General Alpine Commands
8656 ------------------------- -----------------------
8657 P Prev Keyword ? Display this help text
8658 N Next Keyword E Exit without selecting anything
8659 - Previous page % Print
8660 Spc (space bar) Next page
8661 W WhereIs
8663 Select Command
8664 ------------------------------------------------
8665 S Select the highlighted keyword (or chosen keywords in ListMode)
8666 L Turn on ListMode (makes it easy to choose multiple keywords)
8667 1 Turn off ListMode
8668 X Toggle choices when using ListMode
8669 </PRE>
8670 <!--chtml endif-->
8672 <H2>Description of the Select Keyword Screen</H2>
8674 This screen just gives you an easy way to select a keyword or a list of
8675 keywords.
8676 The list of keywords presented is the list of all keywords defined in your
8677 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8678 If you have given a keyword a nickname, that nickname is displayed
8679 instead of the actual keyword.
8681 <P><UL>
8682 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8683 </UL>
8684 <P>
8685 <End of help on this topic>
8686 </BODY>
8687 </HTML>
8688 ===== h_select_incoming_to_monitor =====
8689 <HTML>
8690 <HEAD>
8691 <TITLE>SELECT FOLDERS TO CHECK SCREEN</TITLE>
8692 </HEAD>
8693 <BODY>
8694 <H1>SELECT FOLDERS TO CHECK SCREEN</H1>
8695 <H2>COMMANDS</H2>
8696 <!--chtml if pinemode="function_key"-->
8697 <PRE>
8698 Available Commands
8699 -------------------------------
8700 F1 Show Help Text
8701 F3 Exit without selecting anything
8702 F4 Select the marked folders
8703 F5 Move highlight to previous folder
8704 F6 Move highlight to next folder
8705 F7 Previous page of folders
8706 F8 Next page of folders
8707 F9 Toggle choices on or off
8708 F11 Print
8709 F12 WhereIs
8710 </PRE>
8711 <!--chtml else-->
8712 <PRE>
8713 Navigation General Alpine Commands
8714 ------------------------- -----------------------
8715 P Prev Folder ? Display this help text
8716 N Next Folder ^C exit without changing anything
8717 - Previous page % Print
8718 Spc (space bar) Next page
8719 W WhereIs
8721 Select Command
8722 ------------------------------------------------
8723 S Select the marked folders
8724 X Toggle choices on or off
8725 </PRE>
8726 <!--chtml endif-->
8728 <H2>Description of the Select Folders to Check Screen</H2>
8730 This screen is only useful if the feature
8731 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
8732 is set.
8733 By default, when you set that feature all of your incoming folders
8734 will be checked periodically for Unseen messages.
8735 By using this screen, you may restrict the set of monitored folders to
8736 a subset of all of the incoming folders.
8737 <P>
8738 Mark the folders you want to monitor for Unseen messages with
8739 an "X".
8740 When you've finished marking all your selections use the Select
8741 command to register your choices.
8742 To return to the default of checking all incoming folders
8743 delete all folders or unmark all folders.
8745 <P><UL>
8746 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8747 </UL>
8748 <P>
8749 <End of help on this topic>
8750 </BODY>
8751 </HTML>
8752 ===== h_role_select =====
8753 <HTML>
8754 <HEAD>
8755 <TITLE>ROLES SCREEN</TITLE>
8756 </HEAD>
8757 <BODY>
8758 <H1>ROLES SCREEN</H1>
8759 <H2>ROLES COMMANDS</H2>
8760 <!--chtml if pinemode="function_key"-->
8761 <PRE>
8762 Available Commands
8763 -------------------------------
8764 F1 Show Help Text
8765 F3 Exit without a selection
8766 F4 Select a role to use in composition
8767 F5 Move to previous role
8768 F6 Move to next role
8769 F7 Previous page of roles
8770 F8 Next page of roles
8771 F11 Change Default Role
8772 F12 Whereis (search role nicknames)
8773 </PRE>
8774 <!--chtml else-->
8775 <PRE>
8776 Navigation General Alpine Commands
8777 ------------------------- -----------------------
8778 P Prev Role ? Display this help text
8779 N Next Role E Exit without a selection
8780 - Previous page
8781 Spc (space bar) Next page
8782 W WhereIs (search for word in role nicknames)
8784 Select Role Commands
8785 ------------------------------------------------
8786 [Return] Select highlighted role
8787 D Change Default Role
8788 </PRE>
8789 <!--chtml endif-->
8791 <H2>Description of the Roles Screen</H2>
8793 With this screen you select a role to be used in the composition of a
8794 message.
8795 Use the Previous and Next commands to highlight the role you wish to
8796 use.
8797 When you type carriage return you will be placed in the composer using the highlighted role.
8798 <P>
8799 You don't have any non-default <A HREF="h_rules_roles">roles</A>
8800 available unless you set them up.
8801 You may do so by using the Setup/Rules command on the MAIN MENU.
8802 <P>
8803 By using the D command, you may set a default role that will persist until
8804 you change it or until you exit Alpine.
8805 The D command toggles through three states: set the default role, unset the
8806 default role, and leave the default role as it is.
8807 <P><UL>
8808 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8809 </UL>
8810 <P>
8811 <End of help on this topic>
8812 </BODY>
8813 </HTML>
8814 ===== h_role_abook_select =====
8815 <HTML>
8816 <HEAD>
8817 <TITLE>SELECT ADDRESS BOOK SCREEN</TITLE>
8818 </HEAD>
8819 <BODY>
8820 <H1>SELECT ADDRESS BOOK SCREEN</H1>
8821 <H2>COMMANDS</H2>
8822 <!--chtml if pinemode="function_key"-->
8823 <PRE>
8824 Available Commands
8825 -------------------------------
8826 F1 Show Help Text
8827 F3 Exit screen without selecting anything
8828 F4 Select highlighted address book
8829 F5 Move to previous address book
8830 F6 Move to next address book
8831 F7 Previous page of address books
8832 F8 Next page of address books
8833 F12 Whereis
8834 </PRE>
8835 <!--chtml else-->
8836 <PRE>
8837 Navigation General Alpine Commands
8838 ------------------------- -----------------------
8839 P Previous addrbook ? Display this help text
8840 N Next addrbook
8841 - Previous page
8842 Spc (space bar) Next page
8843 W WhereIs
8845 Select Role Commands
8846 ------------------------------------------------
8847 S Select highlighted address book
8848 E Exit screen without selecting anything
8849 </PRE>
8850 <!--chtml endif-->
8852 <H2>Description of the Select Address Book Screen</H2>
8854 This screen helps you select one of your address books.
8855 Use the Previous and Next commands to highlight the address book you wish to
8856 select.
8857 <P><UL>
8858 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8859 </UL>
8860 <P>
8861 <End of help on this topic>
8862 </BODY>
8863 </HTML>
8864 ======== h_rule_patterns =============
8865 <HTML>
8866 <HEAD>
8867 <TITLE>PATTERNS</TITLE>
8868 </HEAD>
8869 <BODY>
8870 <H1>PATTERNS</H1>
8871 Patterns are used with Roles, Filtering, Index Coloring,
8872 Scoring, Other Rules, and Search Rules.
8873 Patterns are compared with a message to see if there is a match.
8874 For Filtering, the messages being checked are all the messages in the
8875 folder, one at a time.
8876 For Index Line Coloring, each message that is visible on the screen is
8877 checked for matches with the Index Coloring Patterns.
8878 Roles are used with the Reply, Forward, and Compose commands.
8879 For Reply, the message used to compare the Pattern with is the message
8880 being replied to;
8881 for Forward, the message used to compare the Pattern with is the message
8882 being forwarded;
8883 and for Compose, there is no message, so the parts of the Pattern that depend
8884 on a message (everything other than Current Folder Type and the
8885 Beginning of Month and Year)
8886 are not used.
8887 Only the Current Folder Type matters for Compose (plus the Beginning of
8888 Month or Year, which you wouldn't usually use for a Role).
8889 For Scoring, the message being scored is compared with all of the Score
8890 Patterns, and the Score Values from the ones that match are added together to
8891 get the message's score.
8892 For Other Rules, there is no message. Only the Current Folder Type is checked
8893 for Other Rules.
8894 <P>
8895 Each Pattern has several possible parts, all of which are optional.
8896 In order for there to be a match, <EM>ALL</EM> of the
8897 <EM>defined</EM> parts of the Pattern must match the message.
8898 If a part is not defined it is considered a match, but note that a filtering
8899 Pattern must have at least one defined part or it will be ignored.
8900 For example, if the To pattern is not defined it will be
8901 displayed as
8902 <P>
8903 <CENTER>To pattern = <No Value Set></CENTER>
8904 <P>
8905 That is considered a match because it is not defined.
8906 This means that the Pattern with nothing defined is a match if the
8907 Current Folder Type matches, but there is an exception that was mentioned
8908 in the previous paragraph.
8909 Because filtering is a potentially destructive action, filtering Patterns
8910 with nothing other than Current Folder Type defined are ignored.
8911 If you really want a filtering Pattern to match all messages (subject to
8912 Current Folder Type) the best way to do it is to define a Score interval
8913 that includes all possible scores.
8914 This would be the score interval <SAMP>(-INF,INF)</SAMP>.
8915 This can be used even if you haven't defined any rules to Set Scores.
8916 <P>
8917 There are six predefined header patterns called the To, From, Sender, Cc, News,
8918 and Subject patterns.
8919 Besides those six predefined header patterns, you may add
8920 additional header patterns with header fieldnames of your choosing.
8921 You add an extra header pattern by placing the cursor on one of the
8922 patterns while in the role editor and using the "eXtraHdr" command.
8923 The Recip pattern is a header pattern that stands for Recipient (To OR Cc)
8924 and the Partic pattern is a header pattern that stands for
8925 Participant (From OR To OR Cc).
8926 (Defining the Recip pattern does not have the same effect as defining both
8927 the To and Cc patterns. Recip is To <EM>OR</EM> Cc, not To <EM>AND</EM> Cc.)
8928 Similar to the header patterns are the AllText pattern and the BodyText pattern.
8929 Instead of comparing this pattern's text against only the contents of
8930 a particular header field, the text for the AllText pattern is compared
8931 with text anywhere in the message's header or body, and the text for the
8932 BodyText pattern is compared with text anywhere in the message's body.
8933 <P>
8934 Any of the header patterns, the AllText pattern, or the BodyText pattern may be negated with the
8935 "!" "toggle NOT" command.
8936 You can tell that <EM>NOT</EM> has been turned on by looking for the character
8937 "!" at the beginning of the pattern line.
8938 When the "!" is present, it reverses the meaning of the match.
8939 That is, if the pattern matches then it is considered to NOT be a match, and
8940 if it does not match it is considered to be a match.
8941 <P>
8942 Don't make the mistake of putting the "!" in the data field for
8943 a pattern.
8944 For example, if you type the characters "!urgent" into the Subject
8945 pattern, the pattern will look like:
8946 <P>
8947 <PRE>
8948 Subject pattern = !urgent
8949 </PRE>
8950 <P>
8951 This means you want to match the 7 character sequence "!urgent".
8952 In order to match messages that do not have "urgent" in
8953 their Subject field, first type the characters "urgent" followed
8954 by carriage return for the value of the Subject pattern, then negate it
8955 by typing the "!" command.
8956 It should look like
8957 <P>
8958 <PRE>
8959 ! Subject pattern = urgent
8960 </PRE>
8961 <P>
8962 The contents of each of these header patterns (or the AllText or BodyText patterns) may
8963 be a complete email address, part of an address, or a random set of
8964 characters to match against.
8965 It may also be a list of such patterns, which means you
8966 are looking for a match against the first pattern in the list <EM>OR</EM>
8967 the second pattern <EM>OR</EM> the third and so on.
8968 For example, a Subject pattern equal to
8969 <P>
8970 <PRE>
8971 Subject pattern = urgent
8972 emergency
8973 alert
8974 </PRE>
8975 <P>
8976 would match all messages with a subject that contained at least one
8977 of those words.
8978 It would also match subjects containing the words "alerts" or
8979 "Urgently".
8980 <P>
8981 The same example with "NOT" turned on would be
8982 <P>
8983 <PRE>
8984 ! Subject pattern = urgent
8985 emergency
8986 alert
8987 </PRE>
8988 <P>
8989 which would match all messages with a subject that did <EM>NOT</EM> contain any of
8990 those words.
8991 You can use the "Add Value" command to add new words to the list,
8992 or you can enter them as a comma-separated list.
8993 <P>
8994 (It is not possible to specify two patterns that must <EM>BOTH</EM> be
8995 present for a match.
8996 It is only possible to specify that <EM>EITHER</EM> pattern1 <EM>OR</EM>
8997 pattern2 must be present,
8998 and that is exactly what using a list does.)
8999 <P>
9000 The "Current Folder Type" and the "Score Interval" are
9001 also part of the Pattern, although the "Score Interval" is not used
9002 when checking for matches for Scoring.
9003 There are five similar settings that relate to the status of the message.
9004 These settings rely on the message being New or not, Deleted or not,
9005 Answered or not, Important or not, and Recent or not.
9006 There are also some other miscellaneous settings.
9007 The first is the Age of the message in days.
9008 Another is the Size of the message, in bytes.
9009 The third is a setting that detects whether or not the Subject of a
9010 message contains raw 8-bit characters (unencoded characters with the most
9011 significant bit set).
9012 There is a setting that detects whether or not this is the first time
9013 Alpine has been run this month (doesn't depend on individual messages),
9014 and another that detects whether or not this is the first time Alpine has
9015 been run this year.
9016 Other parts of the Pattern detect whether or not the From address of a
9017 message appears in your address book, whether or not certain keywords
9018 are set for a message, and whether or not certain character sets are
9019 used in a message.
9021 <H2>Parts of a Pattern</H2>
9023 <H3>Header patterns</H3>
9025 A header pattern is simply text that is searched for in the corresponding
9026 header field.
9027 For example, if a Pattern has a From header pattern with the value
9028 "@company.com", then only messages that have a From header
9029 that contains the text "@company.com" will be possible
9030 matches.
9031 Matches don't have to be exact.
9032 For example, if the relevant field of a message contains the text
9033 "mailbox@domain" somewhere
9034 in it, then header patterns of "box", or "x@d", or
9035 "mailbox@domain" are all matches.
9036 <P>
9037 All parts of the Pattern must match so, for example,
9038 if a message matches a defined
9039 From pattern, it still must be checked against the other parts of the
9040 Pattern that have been defined.
9041 The To header pattern is a slightly special case.
9042 If the message being checked has a Resent-To header
9043 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, the addresses
9044 there are used in place of the addresses in the To header.
9045 This is only true for the To header.
9046 Resent-cc and Resent-From headers are never used unless you add them
9047 with the eXtraHdrs command.
9048 <P>
9049 The meaning of a header pattern may be negated with the
9050 "!" "toggle NOT" command.
9051 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9052 "!" at the beginning of the pattern line.
9053 It would look something like
9054 <P>
9055 <PRE>
9056 ! From pattern = susan@example.com
9057 </PRE>
9058 <P>
9059 When the "!" is present, it reverses the meaning of the match.
9060 <P>
9061 If you want to check for the presence of a header field but don't care
9062 about its value, then
9063 the empty pattern that you get by entering a pair of
9064 double quotes ("") should match any message that
9065 has the corresponding header field.
9067 <H3><A NAME="pattern_alltext">AllText patterns</A></H3>
9069 AllText patterns are just like header patterns except that the text is
9070 searched for anywhere in the message's headers or body, not just in the
9071 contents of a particular header field.
9072 <P>
9074 <H3><A NAME="pattern_bodytext">BodyText patterns</A></H3>
9076 BodyText patterns are just like header patterns except that the text is
9077 searched for anywhere in the message's body, not just in the
9078 contents of a particular header field.
9079 <P>
9081 If there is more than one header pattern or AllText pattern or BodyText pattern
9082 for which you want to take the
9083 same action there is a shorthand notation that may be used.
9084 Any of these patterns may be a list of patterns instead of
9085 just a single pattern.
9086 If any one of the patterns in the list matches the message
9087 then it is considered a match.
9088 For example, if "company1" and "company2" both required
9089 you to use the same role when replying to messages, you might have
9090 a To pattern that looks like
9091 <P>
9092 <PRE>
9093 To pattern = company1.com
9094 company2.com
9095 </PRE>
9096 <P>
9097 This means that if the mail you are replying to was addressed to
9098 either "anything@company1.com" or "anything@company2.com",
9099 then this Pattern is a match and the same actions will be taken.
9100 <P>
9101 The meaning of an AllText or BodyText pattern may be negated with the
9102 "!" "toggle NOT" command.
9103 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9104 "!" at the beginning of the pattern line.
9105 When the "!" is present, it reverses the meaning of the match.
9106 <P>
9107 A technicality: Since comma is the character used to separate multiple values
9108 in any of the fields that may have multiple values (such as header patterns,
9109 AllText patterns, BodyText patterns, keywords, folder lists, and so on),
9110 you must escape comma with a
9111 backslash (\) if you want to include a literal comma in one of those fields.
9112 In other words, if you type a backslash followed by a comma it will
9113 be interpreted as a comma by Alpine, instead of as a separator between
9114 pattern values.
9115 All other backslashes (those not followed by a comma) are literal
9116 backslashes and should not be escaped.
9117 It's unlikely you'll ever need to enter a literal comma or backslash in
9118 any of the patterns.
9120 <H3><A NAME="pattern_current_folder">Current Folder Type</A></H3>
9122 The "Current Folder Type" may be set to one of four different
9123 values: "Any", "News", "Email", or
9124 "Specific".
9125 If the value is set to "News", then the
9126 Pattern will only match if the currently open folder is a newsgroup.
9127 The value "Email" only matches if the current folder is not news and
9128 the value "Any" causes any folder to match.
9129 If the value of "Current Folder Type" is set to "Specific",
9130 then you must fill in a value for "Folder", which is on the line
9131 below the "Specific" line.
9132 In this case you will only get a match if the currently open folder is
9133 the specific folder you list.
9134 You may give a list of folders instead of just a single
9135 folder name, in which case the Pattern will match if the open folder is
9136 any one of the folders in the list.
9137 The name of each folder in the list may be either "INBOX",
9138 the technical specification
9139 of the folder (like what appears in your configuration file) or, if the
9140 folder is one of your incoming folders, it may be the nickname you've given
9141 the folder.
9142 Here are some samples of specific folder names:
9143 <P>
9144 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
9145 <P>
9146 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
9147 <P>
9148 <CENTER><SAMP>mail/local-folder</SAMP></CENTER>
9149 <P>
9150 The easiest way to fill in the "Folder" field is to use
9151 the "T" command that is available when the "Folder" line is
9152 highlighted, or to use the "Take" command with the configuration
9153 feature
9154 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
9155 turned on.
9156 <P>
9157 When reading a newsgroup, there may be a performance penalty
9158 incurred when collecting the information necessary to check whether
9159 or not a Pattern matches a message.
9160 For this reason, the default Current Folder Type is set to "Email".
9161 If you have Patterns with a Current Folder Type of either
9162 "Any" or "News" and those Patterns are used for
9163 Index Line Coloring or Scoring, you may experience
9164 slower screen redrawing in the MESSAGE INDEX screen when in a newsgroup.
9166 <H3><A NAME="pattern_age_interval">Age Interval</A></H3>
9168 The "Age Interval" may be set to an interval of message
9169 ages that should be considered a match.
9170 Like the other parts of the Pattern, if it is unset it will be ignored.
9171 The Age Interval looks like
9172 <P>
9173 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
9174 <P>
9175 where "min_age" and "max_age" are integers greater
9176 than or equal to zero.
9177 The special value "INF" may be used for
9178 the max value. It represents infinity.
9179 <P>
9180 Actually, this option may be defined as a list of intervals instead
9181 of just a single interval.
9182 The list is separated by commas.
9183 It can look like
9184 <P>
9185 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
9186 <P>
9187 When there is an Age Interval defined, it is a match if the age, in days, of
9188 the message is contained in any of the intervals.
9189 The intervals include both endpoints.
9190 <P>
9191 Even though this option is called Age, it isn't actually
9192 the <EM>age</EM> of the message.
9193 Instead, it is how many days ago the message arrived in one of your folders.
9194 If the current time is a little past midnight, then a message that arrived
9195 just before midnight arrived yesterday, even though the message is only
9196 a few minutes old.
9197 By default, the date being used is not the date in the Date
9198 header of the message.
9199 It is the date that the message arrived in one of your folders.
9200 When you Save a message from one folder to another that arrival date
9201 is preserved.
9202 If you would like to use the date in the Date header that is possible.
9203 Turn on the option
9204 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
9205 near the bottom of the rule definition.
9206 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
9208 <H3><A NAME="pattern_size_interval">Size Interval</A></H3>
9210 The "Size Interval" may be set to an interval of message
9211 sizes that should be considered a match.
9212 Like the other parts of the Pattern, if it is unset it will be ignored.
9213 The Size Interval looks like
9214 <P>
9215 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
9216 <P>
9217 where "min_size" and "max_size" are integers greater
9218 than or equal to zero.
9219 The special value "INF" may be used for
9220 the max value. It represents infinity.
9221 <P>
9222 Actually, this option may be defined as a list of intervals instead
9223 of just a single interval.
9224 The list is separated by commas.
9225 It can look like
9226 <P>
9227 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
9228 <P>
9229 When there is a Size Interval defined, it is a match if the size, in bytes, of
9230 the message is contained in any of the intervals.
9231 The intervals include both endpoints.
9233 <H3><A NAME="pattern_score_interval">Score Interval</A></H3>
9235 The "Score Interval" may be set to an interval of message
9236 scores that should be considered a match.
9237 Like the other parts of the Pattern, if it is unset it will be ignored.
9238 The Score Interval looks like
9239 <P>
9240 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
9241 <P>
9242 where "min_score" and "max_score" are positive or
9243 negative integers, with min_score less than or equal to max_score.
9244 The special values "-INF" and "INF" may be used for
9245 the min and max values to represent negative and positive infinity.
9246 <P>
9247 Actually, a list of intervals may be used if you wish.
9248 A list would look like
9249 <P>
9250 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
9251 <P>
9252 When there is a Score Interval defined, it is a match if the score for
9253 the message is contained in any of the intervals in the list.
9254 The intervals include the endpoints.
9255 The score for a message is calculated by looking at every Score rule defined and
9256 adding up the Score Values for the ones that match the message.
9257 When deciding whether or not a Pattern matches a message for purposes of
9258 calculating the score, the Score Interval is ignored.
9260 <H3><A NAME="pattern_message_status">Message Status</A></H3>
9262 There are five separate message status settings.
9263 By default, all five are set to the value "Don't care", which
9264 will match any message.
9265 The value "Yes" means that the particular status must be true
9266 for a match, and the value "No" means that the particular
9267 status must not be true for a match.
9268 For example, one of the five Message Status settings is whether a message
9269 is marked Important or not.
9270 A "Yes" means that the message must be Important to be
9271 considered a match and "No" means that the message must not be
9272 Important to be considered a match.
9273 The same is true of the other four message status settings that depend
9274 on whether or not the message is New; whether the message has
9275 been Answered or not; whether the message has been Deleted or not, and
9276 whether the message is Recent or not.
9277 <P>
9278 The nomenclature for New and Recent is a bit confusing:
9279 <P>
9280 New means that the message is Unseen.
9281 It could have been in your mailbox for a long time but if you haven't looked
9282 at it, it is still considered New.
9283 That matches the default Alpine index display that shows an N for such a
9284 message.
9285 <P>
9286 Recent means that the message was added to this folder since the last time
9287 you opened the folder.
9288 Alpine also shows an N by default for these types of messages.
9289 If you were to run two copies of Alpine that opened a folder one right after
9290 the other, a message would only show up as Recent in (at most) the first
9291 Alpine session.
9293 <H3><A NAME="pattern_message_keywords">Message Keywords</A></H3>
9295 Keywords are similar to Message Status, but they are chosen by the user.
9296 Provided the mail server allows for it, you may add a set of possible keywords
9297 to a folder and then you may set those keywords or not for each message
9298 in the folder (see <A HREF="h_common_flag">Flag Command</A>).
9299 The syntax of this part of the Pattern is similar to the header patterns.
9300 It is a list of keywords.
9301 The Keyword part of the Pattern is a match if the message has any of
9302 the keywords in the list set.
9303 Like other parts of the Pattern, if this is unset it will be ignored.
9305 <H3><A NAME="pattern_message_charsets">Message Character Sets</A></H3>
9307 A message may use one or more character sets.
9308 This part of the Pattern matches messages that make use of one or more of
9309 the character sets specified in the pattern.
9310 It will be considered a match if a message uses any of the character
9311 sets in the list you give here.
9313 <P>
9314 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
9315 GB2312) you may also use some shorthand names that Alpine provides.
9316 These names are more understandable shorthand names for sets of
9317 character set names.
9318 Two examples are "Cyrillic" and "Greek".
9319 Selecting one of these shorthand names is equivalent to selecting all of
9320 the character sets that make up the set.
9321 You can see all of these shorthand names and the lists of character sets
9322 they stand for by typing the "T" command with the Character
9323 Set pattern highlighted.
9324 The syntax of this part of the Pattern is similar to the header patterns
9325 and the Message Keywords pattern.
9326 It is a list of character sets (or shorthand names).
9327 The Character Set part of the Pattern is a match if the message uses any
9328 of the character sets in the list.
9329 Like other parts of the Pattern, if this is unset it will be ignored.
9331 <H3><A NAME="pattern_8bit_subject">Raw 8-bit in Subject</A></H3>
9333 It seems that lots of unwanted email contains unencoded 8-bit characters
9334 in the Subject.
9335 Normally, characters with the 8th bit set are not allowed in the Subject
9336 header unless they are MIME-encoded.
9337 This option gives you a way to match messages that have Subjects that
9338 contain unencoded 8-bit characters.
9339 By default, the value of this option is "Don't care", which
9340 will match any message.
9341 The value "Yes" means that there must be raw 8-bit characters in
9342 the Subject of the message in order for there to be a match,
9343 and the value "No" is the opposite.
9344 Setting this option will affect performance in large folders because the
9345 subject of each message in the folder has to be checked.
9347 <H3><A NAME="pattern_bom">Beginning of Month</A></H3>
9349 This option gives you a way to take some action once per month.
9350 By default, the value of this option is "Don't care", which
9351 will always match.
9352 The value "Yes" means that this must be the first time Alpine has
9353 been run this month in order to count as a match,
9354 and the value "No" is the opposite.
9356 <H3><A NAME="pattern_boy">Beginning of Year</A></H3>
9358 This option gives you a way to take some action once per year.
9359 By default, the value of this option is "Don't care", which
9360 will always match.
9361 The value "Yes" means that this must be the first time Alpine has
9362 been run this year in order to count as a match,
9363 and the value "No" is the opposite.
9365 <H3><A NAME="pattern_abookfrom">Address in Address Books</A></H3>
9367 This option gives you a way to match messages that have an address
9368 that is in one of your address books.
9369 Only the simple entries in your address books are searched.
9370 Address book distribution lists are ignored!
9371 By default, the value of this option is "Don't care", which
9372 will match any message.
9373 The value "Yes, in any address book" means the address
9374 from the message must be in at least one of your
9375 address books in order to be a match.
9376 The value "No, not in any address book"
9377 means none of the addresses may
9378 be in any of your address books in order to be a match.
9379 The values "Yes, in specific address books" and
9380 "No, not in any of specific address books" are similar but instead
9381 of depending on all address books you are allowed to give a list of address
9382 books to look in.
9383 The addresses from the message that are checked for are determined by the
9384 setting you have for "Types of addresses to check for in address book".
9385 If you set this to "From" the From address from the message will
9386 be looked up in the address book.
9387 If you set it to only "To" then the To addresses will be used.
9388 If any of the To addresses are in the address book then it is considered
9389 a match for "Yes" or not a match for "No".
9390 You could set it to both From and To, in which case all of the From and To
9391 addresses are used.
9392 The "Reply-To" and "Sender" cases are a little unusual.
9393 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
9394 exists or the From address if there is no Reply-To address.
9395 Same for the Sender address.
9396 Setting this option may affect performance in large folders because the
9397 From and Reply-To of each message in the folder have to be checked.
9399 <H3><A NAME="pattern_categorizer">Categorizer Command</A></H3>
9401 This is a command that is run with its standard input set to the message
9402 being checked and its standard output discarded.
9403 The full directory path should be specified.
9404 The command will be run and then its exit status will be checked against
9405 the Exit Status Interval, which defaults to just the value zero.
9406 If the exit status of the command falls in the interval, it is considered
9407 a match, otherwise it is not a match.
9408 <P>
9410 This option may actually be a list of commands.
9411 The first one that exists and is executable is used.
9412 That makes it possible to use the same configuration with Unix Alpine and
9413 PC-Alpine.
9414 <P>
9416 If none of the commands in the list exists and is executable then the rule
9417 is <EM>not</EM> a match.
9418 If it is possible that the command may not exist, you should be careful
9419 to structure your rules so that nothing destructive
9420 happens when the command does not exist.
9421 For example, you might have a filter that filters away spam when there is
9422 a match but does nothing when there is not a match.
9423 That would continue to work correctly if the command didn't exist.
9424 However, if you have a filter that filters away spam when there is not
9425 a match and keeps it when there is a match, that would filter everything
9426 if the categorizer command didn't exist.
9427 <P>
9428 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
9429 setup for the bogofilter filter.
9431 <P>
9432 <End of help on this topic>
9433 </BODY>
9434 </HTML>
9435 ===== h_rules_roles =====
9436 <HTML>
9437 <HEAD>
9438 <TITLE>SETUP ROLES SCREEN</TITLE>
9439 </HEAD>
9440 <BODY>
9441 <H1>SETUP ROLES SCREEN</H1>
9442 <H2>SETUP ROLES COMMANDS</H2>
9443 <!--chtml if pinemode="function_key"-->
9444 <PRE>
9445 Available Commands -- Group 1 Available Commands -- Group 2
9446 ------------------------------- ------------------------------
9447 F1 Show Help Text F1 Show Help Text
9448 F2 See commands in next group F2 See commands in next group
9449 F3 Back to MAIN Alpine menu
9450 F4 Change configuration for role
9451 F5 Move to previous role F5 Include file in role config
9452 F6 Move to next role F6 Exclude file from config
9453 F7 Previous page of roles
9454 F8 Next page of roles
9455 F9 Add new role F9 Replicate existing role
9456 F10 Delete existing role
9457 F11 Shuffle the order of roles
9458 F12 Whereis (search role nicknames)
9459 </PRE>
9460 <!--chtml else-->
9461 <PRE>
9462 Navigation General Alpine Commands
9463 ------------------------- -----------------------
9464 P Prev Role ? Display this help text
9465 N Next Role E Back to MAIN Alpine menu
9466 - Previous page
9467 Spc (space bar) Next page
9468 W WhereIs (search for word in role nicknames)
9470 Setup Roles Commands
9471 ------------------------------------------------
9472 A Add new role $ Shuffle the order of roles
9473 D Delete existing role C Change configuration for highlighted role
9474 R Replicate existing role
9475 I Include file in role config X Exclude file from role config
9476 </PRE>
9477 <!--chtml endif-->
9479 <H2>Description of the Setup Roles Screen</H2>
9481 This screen lets you add, delete, modify, or change the order of the rules
9482 that determine the role you are playing when composing a message.
9483 <P>
9484 You may play different roles depending on who you are replying to.
9485 For example, if you are replying to a message addressed to help-desk you
9486 may be acting as a Help Desk Worker.
9487 That role may require that you use a different return address and/or
9488 a different signature.
9489 <P>
9490 Roles are optional.
9491 If you set up roles they work like this: Each role has a set of
9492 "Uses", which indicate whether or not a role is eligible to be
9493 considered for a particular use; a "Pattern",
9494 which is used to decide which of the eligible roles is used; and a set
9495 of "Actions", which are taken when that role is used.
9496 When you reply to a message, the message you are replying to is compared
9497 with the Patterns of the roles marked as eligible for use when replying.
9498 The comparisons start with the first eligible role and keep going until there
9499 is a match.
9500 If a match is found, the matching role's Actions are taken.
9501 <P>
9502 It is also possible to set a default role and to change that role during
9503 your Alpine session.
9504 When you start Alpine no default role will be set.
9505 You may set or change the current default role by using the "D"
9506 command in the role selection screen.
9507 You'll see that screen while composing a message and being asked to select
9508 a role.
9509 An easy way to get to that screen is to use the <A HREF="h_common_role">Role Command</A> to
9510 compose a message.
9511 You may find a default role useful if you normally perform the duties of one
9512 of your roles for a while, then you switch to another role and stay in the
9513 new role for another period of time.
9514 It may be easier than using the Role Command to select the role each time you
9515 compose a message.
9517 <H2>Role Uses</H2>
9519 There are three types of use to be configured;
9520 one for Replying, one for Forwarding, and one for Composing.
9521 These indicate whether or not you want a role to be considered when you
9522 type the Reply, Forward, or Compose commands.
9523 (The Role command is an alternate form of the Compose command, and it is
9524 not affected by these settings.)
9525 Each of these Use types has three possible values.
9526 The value "Never"
9527 means that the role will never be considered as a candidate for use with
9528 the corresponding command.
9529 For example, if you set a role's Reply Use to Never, then when you Reply to
9530 a message, that role won't even be considered.
9531 (That isn't quite true. If the message you are replying to matches some other
9532 role that requires confirmation,
9533 then there will be a ^T command available which allows you to select a role
9534 from all of your roles, not just the reply-eligible roles.)
9535 <P>
9537 The options "With confirmation" and "Without confirmation"
9538 both mean that you do want to consider this role when using the corresponding
9539 command.
9540 For either of these settings the role's Pattern will
9541 be checked to see if it matches the message.
9542 For Reply Use, the message used to compare the Pattern with is the message
9543 being replied to.
9544 For Forward Use, the message used to compare the Pattern with is the message
9545 being forwarded.
9546 For Compose Use, there is no message, so the parts of the Pattern that depend
9547 on a message (everything other than Current Folder Type) are ignored.
9548 In all cases, the Current Folder Type is checked if defined.
9549 If there is a match then this role will either be used without confirmation
9550 or will be the default when confirmation is asked for, depending on
9551 which of the two options is selected.
9552 If confirmation is requested, you will have a chance to
9553 choose No Role instead of the offered role, or to
9554 change the role to any one of your other roles (with the ^T command).
9556 <H2>Role Patterns</H2>
9558 In order to determine whether or not a message matches a role the message is
9559 compared with the Role's Pattern.
9560 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9561 Scoring, Other Rules, and Search Rules, so are described in only one place,
9562 "<A HREF="h_rule_patterns">here</A>".
9563 <P>
9564 Since header patterns, AllText patterns, and BodyText patterns that are unset are ignored,
9565 a role that has all header patterns unset, the AllText pattern unset,
9566 the BodyText pattern unset,
9567 the Score Interval unset, and the Current Folder Type set to
9568 "Any" may be used as a default role.
9569 It should be put last in the list of roles since the matching
9570 starts at the beginning and proceeds until one of the roles is a match.
9571 If no roles at all match, then Alpine will
9572 use its regular methods of defining the role.
9573 If you wanted to, you could define a different "default" role
9574 for Replying, Forwarding, and Composing by setting the
9575 "Use" fields appropriately.
9577 <H2>Role Actions</H2>
9579 Once a role match is found, the role's Actions are taken.
9580 For each role there are several possible actions that may be defined.
9581 They are actions to set the From address, the Reply-To address,
9582 the Fcc, the Signature, the Template file, and Other Headers.
9584 <H3>Set From</H3>
9586 The From address is the address used on the From line of the message
9587 you are sending.
9589 <H3>Set Reply-To</H3>
9591 The Reply-To address is the address used on the Reply-To line of the message
9592 you are sending.
9593 You don't need a Reply-To address unless it is different from the From address.
9595 <H3>Set Other Headers</H3>
9597 If you want to set the value of the From or Reply-To headers, use
9598 the specific fields "Set From" or "Set Reply-To".
9599 If you want to set the values of other headers, use this field.
9600 This field is similar to the
9601 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> configuration option.
9602 Each header you specify here must include the header tag
9603 ("To:", "Approved:", etc.)
9604 and may optionally include a value for that header.
9605 It is different from the <!--#echo var="VAR_customized-hdrs"--> in that the value you give
9606 for a header here will replace any value that already exists.
9607 For example, if you are Replying to a message there will be at least one
9608 address in the To header (the address you are Replying to).
9609 However, if you Reply using a role that sets the To header, that role's
9610 To header value will be used instead.
9612 <H3>Set Fcc</H3>
9614 The Fcc is used as the Fcc for the message you are sending.
9616 <H3>Set Signature or Set LiteralSig</H3>
9618 The Signature is the name of a file to be used as the signature file when
9619 this role is being used.
9620 If the name of the file has a vertical bar following it (|)
9621 then it is assumed that the file is a program that should be run to
9622 produce the signature.
9623 If the LiteralSig is set, then it is used instead of the signature file.
9624 LiteralSig is just a different way to store the signature.
9625 It is stored in the pine configuration file instead of in a separate
9626 signature file.
9627 If the <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined
9628 either in the role or as the default signature in the Setup/Config screen,
9629 then the signature file is ignored.
9631 <H3>Set Template</H3>
9633 A Template is the name of a file to be included in the message when this
9634 role is being used.
9635 If the name of the file has a vertical bar following it (|)
9636 then it is assumed that the file is a program that should be run to
9637 produce the template.
9639 <P>
9640 Both signature files and template files may be stored remotely on an IMAP
9641 server.
9642 In order to do that you just give the file a remote name.
9643 This works just like the regular
9644 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>
9645 option that is configured from the Setup/Configuration screen.
9646 A remote signature file name might look like:
9647 <P>
9648 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
9649 <P>
9650 Once you have named the remote signature or template file you create its
9651 contents by using the "F" "editFile" command when the
9652 cursor is on the "Set Signature" or "Set Template"
9653 line of the role editor.
9655 <P>
9656 Both signature files and template files (or the output of signature programs
9657 and template file programs) may contain special tokens
9658 that are replaced with contents
9659 that depend on the message being replied to or forwarded.
9660 See the help for the individual fields inside the role editor for more
9661 information on tokens.
9663 <H3>Use SMTP Server</H3>
9665 If this field has a value, then it will be used as the SMTP server
9666 to send mail when this role is being used (unless the SMTP server variable
9667 is set in the system-wide fixed configuration file).
9668 It has the same semantics as the
9669 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
9670 variable in the Setup/Config screen.
9671 When you postpone the composition this SMTP server list will be saved
9672 with the postponed composition and it cannot be changed later.
9673 Because of that, you may want to make this a list of SMTP servers
9674 with the preferred server at the front of the list and alternate servers
9675 later in the list.
9677 <P>
9678 If any of the actions are left unset, then the action depends on what
9679 is present in the "Initialize settings using role" field.
9680 If you've listed the nickname of another one of your roles there, then the
9681 corresponding action from that role will be used here.
9682 If that action is also blank, or if there is no nickname specified,
9683 then Alpine will do whatever it normally does to set these actions.
9684 This depends on other configuration options and features you've set.
9686 <H2>Command Descriptions</H2>
9688 <H3>Add</H3>
9690 The Add command is used to add a new role definition to your set of
9691 roles.
9692 The new role will be added after the highlighted role.
9694 <H3>Delete</H3>
9696 The Delete command deletes the currently highlighted role.
9698 <H3>Change</H3>
9700 The Change command lets you edit the nickname, Uses, Pattern,
9701 and Actions of the currently highlighted role.
9703 <H3>Shuffle</H3>
9705 The Shuffle command allows you to change the order of the roles.
9706 You may move the currently highlighted role up or down in the list.
9707 The order of the roles is important since the roles are tested for a
9708 match starting with the first role and continuing until a match is found.
9709 You should place the roles with more specific Patterns near the beginning
9710 of the list, and those with more general Patterns near the end so that
9711 the more specific matches will happen when appropriate.
9713 <H3>Replicate</H3>
9715 The Replicate command is used to copy an existing role and modify it.
9716 The new role will be added after the highlighted role.
9718 <H3>IncludeFile</H3>
9720 The IncludeFile command allows you to add a roles file to your configuration.
9721 Usually, your roles will be contained in your Alpine configuration file.
9722 If you wish, some or all of your roles may be stored in a separate file.
9723 If a roles file already exists (maybe it was made by somebody else using
9724 Alpine), you may insert it before the currently highlighted role.
9725 You may also insert an empty file or a file that does not yet exist.
9726 Once you have an empty roles file in your configuration, you may use
9727 the Shuffle command to move roles into it.
9728 In fact, that's the only way to get the initial role into the file.
9730 <H3>eXcludeFile</H3>
9732 The eXcludeFile command removes a roles file from your roles configuration.
9733 A limitation of the program is that in order to exclude a roles file
9734 that file must have at least one role
9735 in it, otherwise you won't be able to highlight a line in the file.
9736 So you may have to add a dummy role to the file in order to exclude the file.
9737 <P><UL>
9738 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9739 </UL>
9740 <P>
9741 <End of help on this topic>
9742 </BODY>
9743 </HTML>
9744 ===== h_rules_other =====
9745 <HTML>
9746 <HEAD>
9747 <TITLE>SETUP OTHER RULES SCREEN</TITLE>
9748 </HEAD>
9749 <BODY>
9750 <H1>SETUP OTHER RULES SCREEN</H1>
9751 <H2>SETUP OTHER RULES COMMANDS</H2>
9752 <!--chtml if pinemode="function_key"-->
9753 <PRE>
9754 Available Commands -- Group 1 Available Commands -- Group 2
9755 ------------------------------- ------------------------------
9756 F1 Show Help Text F1 Show Help Text
9757 F2 See commands in next group F2 See commands in next group
9758 F3 Back to MAIN Alpine menu
9759 F4 Change configuration for rule
9760 F5 Move to previous rule F5 Include file in rule config
9761 F6 Move to next rule F6 Exclude file from config
9762 F7 Previous page of rules
9763 F8 Next page of rules
9764 F9 Add new rule F9 Replicate existing rule
9765 F10 Delete existing rule
9766 F11 Shuffle the order of rules
9767 F12 Whereis (search rule nicknames)
9768 </PRE>
9769 <!--chtml else-->
9770 <PRE>
9771 Navigation General Alpine Commands
9772 ------------------------- -----------------------
9773 P Prev rule ? Display this help text
9774 N Next rule E Back to MAIN Alpine menu
9775 - Previous page
9776 Spc (space bar) Next page
9777 W WhereIs (search for word in rule nicknames)
9779 Setup Other Rules Commands
9780 ------------------------------------------------
9781 A Add new rule $ Shuffle the order of rules
9782 D Delete existing rule C Change configuration for highlighted rule
9783 R Replicate existing rule
9784 I Include file in rule config X Exclude file from rule config
9785 </PRE>
9786 <!--chtml endif-->
9788 <H2>Description of the Setup Other Rules Screen</H2>
9790 This is where you may set various actions that do not fit well into the
9791 other Rules categories.
9793 <H2>Patterns</H2>
9795 Other Rules are a little different from the rest of the Rules because
9796 they depend only on the current folder, and not on a particular message.
9797 In order to determine whether or not a rule's actions should be applied
9798 the current folder is compared with the rule's Pattern, which consists
9799 of only the Current Folder Type.
9800 Current Folder Type works the same for Other Rules as it does for Roles,
9801 Filtering, Index Coloring, and Scoring.
9802 Keep in mind that the only part of the Pattern that applies to Other
9803 Rules is the Current Folder Type when looking at the description of
9804 Patterns given
9805 "<A HREF="h_rule_patterns">here</A>".
9807 <H2>The Actions</H2>
9809 <H3>Set Sort Order</H3>
9811 When you enter a new folder, these rules will be checked to see if you
9812 have set a sort order that is different from your default sort order.
9813 The default is set in the Setup/Config screen with
9814 the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
9815 If the Sort Order action is set, then the folder will be displayed sorted in
9816 that sort order instead of in the default order.
9817 <P>
9818 A possible point of confusion arises when you change the configuration
9819 of the Sort Order for the currently open folder.
9820 The folder will normally be re-sorted when you go back to viewing the
9821 index.
9822 However, if you have manually sorted the folder with the
9823 Sort
9824 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
9825 command, then it will not be re-sorted until the next time it is opened.
9827 <H3>Set Index Format</H3>
9829 When you enter a new folder, these rules will be checked to see if you
9830 have set an Index Format that is different from your default Index Format,
9831 which is set with the
9832 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
9833 If so, the index will be displayed with this format instead of the default.
9835 <H3>Set Startup Rule</H3>
9837 When you enter a new folder, these rules will be checked to see if you
9838 have set a startup rule that is different from the default startup rule.
9839 The default for incoming folders is set in the Setup/Config screen with
9840 the "<!--#echo var="VAR_incoming-startup-rule"-->" option.
9841 The default for folders other than INBOX that are not part of your
9842 incoming collection
9843 (see <A HREF="h_config_enable_incoming"><!--#echo var="FEAT_enable-incoming-folders"--></A> feature)
9844 is to start with the last message in the folder.
9845 If the Startup Rule is set to something other than "default",
9846 then the rule will determine which message will be the current message when
9847 the folder is first opened.
9848 <P>
9849 The various startup rule possibilities work the same here as they do in
9850 the incoming collection, so check
9851 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
9852 for more help.
9854 <H2>Command Descriptions</H2>
9856 <H3>Add</H3>
9858 The Add command is used to add a new rule definition to your set of
9859 rules.
9860 The new rule will be added after the highlighted rule.
9862 <H3>Delete</H3>
9864 The Delete command deletes the currently highlighted rule.
9866 <H3>Change</H3>
9868 The Change command lets you edit the nickname, Pattern,
9869 and Action of the currently highlighted rule.
9871 <H3>Shuffle</H3>
9873 The Shuffle command allows you to change the order of the rules.
9874 You may move the currently highlighted rule up or down in the list.
9875 The order of the rules is important since the rules are tested for a
9876 match starting with the first rule and continuing until a match is found.
9877 You should place the rules with more specific Patterns near the beginning
9878 of the list, and those with more general Patterns near the end so that
9879 the more specific matches will happen when appropriate.
9881 <H3>Replicate</H3>
9883 The Replicate command is used to copy an existing rule definition and modify it.
9884 The new rule will be added after the highlighted rule.
9886 <H3>IncludeFile</H3>
9888 The IncludeFile command allows you to add a rules file to your configuration.
9889 Usually, your rules will be contained in your Alpine configuration file.
9890 If you wish, some or all of your rules may be stored in a separate file.
9891 If a rules file already exists (maybe it was made by somebody else using
9892 Alpine), you may insert it before the currently highlighted rule.
9893 You may also insert an empty file or a file that does not yet exist.
9894 Once you have an empty rules file in your configuration, you may use
9895 the Shuffle command to move rules into it.
9896 In fact, that's the only way to get the initial rule into the file.
9898 <H3>eXcludeFile</H3>
9900 The eXcludeFile command removes a rules file from your rules configuration.
9901 A limitation of the program is that in order to exclude a rules file
9902 that file must have at least one rule
9903 in it, otherwise you won't be able to highlight a line in the file.
9904 So you may have to add a dummy rule to the file in order to exclude the file.
9905 <P><UL>
9906 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9907 </UL>
9908 <P>
9909 <End of help on this topic>
9910 </BODY>
9911 </HTML>
9912 ===== h_rules_srch =====
9913 <HTML>
9914 <HEAD>
9915 <TITLE>SETUP SEARCH RULES SCREEN</TITLE>
9916 </HEAD>
9917 <BODY>
9918 <H1>SETUP SEARCH RULES SCREEN</H1>
9919 <H2>SETUP SEARCH RULES COMMANDS</H2>
9920 <!--chtml if pinemode="function_key"-->
9921 <PRE>
9922 Available Commands -- Group 1 Available Commands -- Group 2
9923 ------------------------------- ------------------------------
9924 F1 Show Help Text F1 Show Help Text
9925 F2 See commands in next group F2 See commands in next group
9926 F3 Back to MAIN Alpine menu
9927 F4 Change configuration for rule
9928 F5 Move to previous rule F5 Include file in rule config
9929 F6 Move to next rule F6 Exclude file from config
9930 F7 Previous page of rules
9931 F8 Next page of rules
9932 F9 Add new rule F9 Replicate existing rule
9933 F10 Delete existing rule
9934 F11 Shuffle the order of rules
9935 F12 Whereis (search rule nicknames)
9936 </PRE>
9937 <!--chtml else-->
9938 <PRE>
9939 Navigation General Alpine Commands
9940 ------------------------- -----------------------
9941 P Prev rule ? Display this help text
9942 N Next rule E Back to MAIN Alpine menu
9943 - Previous page
9944 Spc (space bar) Next page
9945 W WhereIs (search for word in rule nicknames)
9947 Setup Search Rules Commands
9948 ------------------------------------------------
9949 A Add new rule $ Shuffle the order of rules
9950 D Delete existing rule C Change configuration for highlighted rule
9951 R Replicate existing rule
9952 I Include file in rule config X Exclude file from rule config
9953 </PRE>
9954 <!--chtml endif-->
9956 <H2>Description of the Setup Search Rules Screen</H2>
9958 One of the commands that becomes available when that feature is turned on
9959 is the "; Select" command, which is used in the MESSAGE INDEX
9960 screen to select a set of messages.
9961 One way of selecting messages is to use a Rule.
9962 All of the messages that match (or don't match if you wish)
9963 a Rule's Pattern will be selected.
9964 <P>
9965 Any of your Rules may be used for this purpose.
9966 You might already have Rules set up for filtering, index line color, scores, or roles;
9967 and you may use any of those Rules with the Select command.
9968 However, you might find it more convenient to set up a separate set of Rules
9969 just for this purpose without having to worry about what other effects
9970 they may cause.
9971 That is the purpose of these Select Rules.
9973 <P>
9974 Each rule has a "Pattern"
9975 that is used to decide which messages are selected when you use it with
9976 the Select command.
9978 <H2>Patterns</H2>
9980 In order to determine whether or not a message should be selected
9981 the message is compared with the rule's Pattern.
9982 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9983 Scoring, Other Rules, and Search Rules, so are described in only one place,
9984 "<A HREF="h_rule_patterns">here</A>".
9986 <H2>Command Descriptions</H2>
9988 <H3>Add</H3>
9990 The Add command is used to add a new rule definition to your set of
9991 rules.
9992 The new rule will be added after the highlighted rule.
9994 <H3>Delete</H3>
9996 The Delete command deletes the currently highlighted rule.
9998 <H3>Change</H3>
10000 The Change command lets you edit the nickname and Pattern
10001 of the currently highlighted rule.
10003 <H3>Shuffle</H3>
10005 The Shuffle command allows you to change the order of the rules.
10006 This affects only the order they are presented in when you use the
10007 ^T subcommand of the Select by Rule command.
10008 You may move the currently highlighted rule up or down in the list.
10010 <H3>Replicate</H3>
10012 The Replicate command is used to copy an existing rule definition and modify it.
10013 The new rule will be added after the highlighted rule.
10015 <H3>IncludeFile</H3>
10017 The IncludeFile command allows you to add a rules file to your configuration.
10018 Usually, your rules will be contained in your Alpine configuration file.
10019 If you wish, some or all of your rules may be stored in a separate file.
10020 If a rules file already exists (maybe it was made by somebody else using
10021 Alpine), you may insert it before the currently highlighted rule.
10022 You may also insert an empty file or a file that does not yet exist.
10023 Once you have an empty rules file in your configuration, you may use
10024 the Shuffle command to move rules into it.
10025 In fact, that's the only way to get the initial rule into the file.
10027 <H3>eXcludeFile</H3>
10029 The eXcludeFile command removes a rules file from your rules configuration.
10030 A limitation of the program is that in order to exclude a rules file
10031 that file must have at least one rule
10032 in it, otherwise you won't be able to highlight a line in the file.
10033 So you may have to add a dummy rule to the file in order to exclude the file.
10034 <P><UL>
10035 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10036 </UL>
10037 <P>
10038 <End of help on this topic>
10039 </BODY>
10040 </HTML>
10041 ===== h_rules_incols =====
10042 <HTML>
10043 <HEAD>
10044 <TITLE>SETUP INDEX LINE COLORS SCREEN</TITLE>
10045 </HEAD>
10046 <BODY>
10047 <H1>SETUP INDEX LINE COLORS SCREEN</H1>
10048 <H2>SETUP INDEX LINE COLORS COMMANDS</H2>
10049 <!--chtml if pinemode="function_key"-->
10050 <PRE>
10051 Available Commands -- Group 1 Available Commands -- Group 2
10052 ------------------------------- ------------------------------
10053 F1 Show Help Text F1 Show Help Text
10054 F2 See commands in next group F2 See commands in next group
10055 F3 Back to MAIN Alpine menu
10056 F4 Change configuration for rule
10057 F5 Move to previous rule F5 Include file in rule config
10058 F6 Move to next rule F6 Exclude file from config
10059 F7 Previous page of rules
10060 F8 Next page of rules
10061 F9 Add new rule F9 Replicate existing rule
10062 F10 Delete existing rule
10063 F11 Shuffle the order of rules
10064 F12 Whereis (search rule nicknames)
10065 </PRE>
10066 <!--chtml else-->
10067 <PRE>
10068 Navigation General Alpine Commands
10069 ------------------------- -----------------------
10070 P Prev rule ? Display this help text
10071 N Next rule E Back to MAIN Alpine menu
10072 - Previous page
10073 Spc (space bar) Next page
10074 W WhereIs (search for word in rule nicknames)
10076 Setup Index Color Commands
10077 ------------------------------------------------
10078 A Add new rule $ Shuffle the order of rules
10079 D Delete existing rule C Change configuration for highlighted rule
10080 R Replicate existing rule
10081 I Include file in rule config X Exclude file from rule config
10082 </PRE>
10083 <!--chtml endif-->
10085 <H2>Description of the Setup Index Line Colors Screen</H2>
10087 Index Line Color causes lines in the MESSAGE INDEX screen to be colored.
10088 This action is only available if your terminal is capable of displaying
10089 color and color display has been enabled with the
10090 <A HREF="h_config_color_style">Color Style</A> option within the
10091 Setup Color screen.
10092 (In PC-Alpine, color is always enabled so there is no option to turn on.)
10093 This screen lets you add, delete, modify, or change the order of the rules
10094 that cause the lines in the MESSAGE INDEX to be displayed in different
10095 colors.
10096 <P>
10097 Each rule has a "Pattern",
10098 which is used to decide which of the rules is used; and the color that
10099 is used if the Pattern matches a particular message.
10101 <H2>Index Color Patterns</H2>
10103 In order to determine whether or not a message matches an Index Color Rule
10104 the message is compared with the rule's Pattern.
10105 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10106 Scoring, Other Rules, and Search Rules, so are described in only one place,
10107 "<A HREF="h_rule_patterns">here</A>".
10109 <P>
10110 If none of the Index Color rules is a match for a particular index line,
10111 then the color used is set using
10112 the <A HREF="h_color_setup">Setup Kolor</A> screen.
10114 <H2>Index Line Color</H2>
10116 This is the color that index lines are colored when there is a matching
10117 Pattern.
10118 This colors the whole index line, except possibly the status letters,
10119 which may be colored separately using
10120 the <A HREF="h_color_setup">Setup Kolor</A> screen.
10122 <H2>Command Descriptions</H2>
10124 <H3>Add</H3>
10126 The Add command is used to add a new rule definition to your set of
10127 rules.
10128 The new rule will be added after the highlighted rule.
10130 <H3>Delete</H3>
10132 The Delete command deletes the currently highlighted rule.
10134 <H3>Change</H3>
10136 The Change command lets you edit the nickname, Pattern,
10137 and Index Line Color of the currently highlighted rule.
10139 <H3>Shuffle</H3>
10141 The Shuffle command allows you to change the order of the rules.
10142 You may move the currently highlighted rule up or down in the list.
10143 The order of the rules is important since the rules are tested for a
10144 match starting with the first rule and continuing until a match is found.
10145 You should place the rules with more specific Patterns near the beginning
10146 of the list, and those with more general Patterns near the end so that
10147 the more specific matches will happen when appropriate.
10149 <H3>Replicate</H3>
10151 The Replicate command is used to copy an existing rule definition and modify it.
10152 The new rule will be added after the highlighted rule.
10154 <H3>IncludeFile</H3>
10156 The IncludeFile command allows you to add a rules file to your configuration.
10157 Usually, your rules will be contained in your Alpine configuration file.
10158 If you wish, some or all of your rules may be stored in a separate file.
10159 If a rules file already exists (maybe it was made by somebody else using
10160 Alpine), you may insert it before the currently highlighted rule.
10161 You may also insert an empty file or a file that does not yet exist.
10162 Once you have an empty rules file in your configuration, you may use
10163 the Shuffle command to move rules into it.
10164 In fact, that's the only way to get the initial rule into the file.
10166 <H3>eXcludeFile</H3>
10168 The eXcludeFile command removes a rules file from your rules configuration.
10169 A limitation of the program is that in order to exclude a rules file
10170 that file must have at least one rule
10171 in it, otherwise you won't be able to highlight a line in the file.
10172 So you may have to add a dummy rule to the file in order to exclude the file.
10173 <P><UL>
10174 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10175 </UL>
10176 <P>
10177 <End of help on this topic>
10178 </BODY>
10179 </HTML>
10180 ===== h_rules_filter =====
10181 <HTML>
10182 <HEAD>
10183 <TITLE>SETUP FILTERING SCREEN</TITLE>
10184 </HEAD>
10185 <BODY>
10186 <H1>SETUP FILTERING SCREEN</H1>
10187 <H2>SETUP FILTERING COMMANDS</H2>
10188 <!--chtml if pinemode="function_key"-->
10189 <PRE>
10190 Available Commands -- Group 1 Available Commands -- Group 2
10191 ------------------------------- ------------------------------
10192 F1 Show Help Text F1 Show Help Text
10193 F2 See commands in next group F2 See commands in next group
10194 F3 Back to MAIN Alpine menu
10195 F4 Change configuration for filter
10196 F5 Move to previous filter F5 Include file in filter config
10197 F6 Move to next filter F6 Exclude file from config
10198 F7 Previous page of filters
10199 F8 Next page of filters
10200 F9 Add new filter F9 Replicate existing filter
10201 F10 Delete existing filter
10202 F11 Shuffle the order of filters
10203 F12 Whereis (search filter nicknames)
10204 </PRE>
10205 <!--chtml else-->
10206 <PRE>
10207 Navigation General Alpine Commands
10208 ------------------------- -----------------------
10209 P Prev Filter ? Display this help text
10210 N Next Filter E Back to MAIN Alpine menu
10211 - Previous page
10212 Spc (space bar) Next page
10213 W WhereIs (search for word in filter nicknames)
10215 Setup Filters Commands
10216 ------------------------------------------------
10217 A Add new filter $ Shuffle the order of filters
10218 D Delete existing filter C Change configuration for highlighted filter
10219 R Replicate existing filter
10220 I Include file in filter config X Exclude file from filter config
10221 </PRE>
10222 <!--chtml endif-->
10224 <H2>Description of the Setup Filtering Screen</H2>
10226 This screen lets you add, delete, modify, or change the order of the rules
10227 that determine the filtering Alpine does on folders you view.
10228 <P>
10229 The software that actually delivers mail (the stuff that happens
10230 before Alpine is involved) for you is in a better position to do mail filtering
10231 than Alpine itself.
10232 If possible, you may want to look into using that sort of mail filtering to
10233 deliver mail to different folders, delete it, or forward it.
10234 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
10235 <P>
10236 Filtering is a way to automatically move certain messages from one folder
10237 to another or to delete messages.
10238 It can also be used to set message status (Important, Deleted, New,
10239 Answered) and to set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
10240 Alpine doesn't have the ability to forward mail to another address or
10241 to deliver vacation messages.
10242 <P>
10243 Each filtering rule has a "Pattern" and a "Filter Action".
10244 When a folder is opened, when new mail arrives in an open folder, or
10245 when mail is Expunged from a folder; each
10246 message is compared with the Patterns of your filtering rules.
10247 The comparisons start with the first rule and keep going until there
10248 is a match.
10249 If a match is found, the message may be deleted or moved, depending on
10250 the setting of the Filter Action.
10251 If the message is not deleted, it may have its status altered.
10253 <P>
10254 <EM>NOTE:</EM>
10255 When setting up a Pattern used to delete messages,
10256 it is recommended that you test the Pattern first with a "Move"
10257 folder specified in
10258 case unintended matches occur. Messages that are deleted will be removed
10259 from the folder and <EM>unrecoverable</EM> from within Alpine after the
10260 next Expunge command or once the folder being filtered has been closed.
10262 <H2>Filter Patterns</H2>
10264 In order to determine whether or not a message matches a filter the message is
10265 compared with the Filter's Pattern.
10266 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10267 Scoring, Other Rules, and Search Rules, so are described in only one place,
10268 "<A HREF="h_rule_patterns">here</A>".
10269 <P>
10270 Since filtering is a potentially destructive action, if you have a filtering
10271 Pattern with nothing other than Current Folder Type set, that filtering
10272 rule is ignored.
10274 <H2>Filter Actions</H2>
10276 Once a filter match is found for a particular message, there are some actions
10277 that may be taken.
10278 First, the message may have its status changed.
10279 This is the same message status that you can manipulate manually using the
10280 <a href="h_common_flag">Flag Command</a>.
10281 There are always four elements of message status that you can control.
10282 You can set or clear the Important status, the New status, the Deleted
10283 status, and the Answered status.
10284 Of course, if the filter is going to delete the message,
10285 then there is no point in setting message status.
10286 You may also be able to set user-defined keywords for a message.
10287 Read a little about keywords in the help text for the
10288 <A HREF="h_common_flag">Flag</A> command.
10289 <P>
10290 Second, the filter may delete or move the message.
10291 Deleting the message marks it Deleted and removes it from view.
10292 It is effectively gone forever (though it technically is still there until
10293 the next expunge command, which may happen implicitly).
10294 Moving the message moves it from the open folder into the folder
10295 listed on the "Folder List" line of the filter configuration.
10296 If you list more than one folder name (separated by commas) then the message
10297 will be copied to each of those folders.
10298 In any case, if "Delete" or "Move" is set then the
10299 message is removed from the current folder.
10300 If you just want to set the messages status without deleting it from
10301 the folder, then set the filter action to
10302 "Just Set Message Status".
10303 <P>
10304 (There is no way to do a Copy instead of a Move, due to the difficulties
10305 involved in keeping track of whether or not a message has
10306 already been copied.)
10308 <H2>Command Descriptions</H2>
10310 <H3>Add</H3>
10312 The Add command is used to add a new filter definition to your set of
10313 filters.
10314 The new filter will be added after the highlighted filter.
10316 <H3>Delete</H3>
10318 The Delete command deletes the currently highlighted filter.
10320 <H3>Change</H3>
10322 The Change command lets you edit the nickname, Pattern,
10323 and Folder of the currently highlighted filter.
10325 <H3>Shuffle</H3>
10327 The Shuffle command allows you to change the order of the filters.
10328 You may move the currently highlighted filter up or down in the list.
10329 The order of the filters is important since the filters are tested for a
10330 match starting with the first filter and continuing until a match is found.
10331 You should place the filters with more specific Patterns near the beginning
10332 of the list, and those with more general Patterns near the end so that
10333 the more specific matches will happen when appropriate.
10335 <H3>Replicate</H3>
10337 The Replicate command is used to copy an existing filter and modify it.
10338 The new filter will be added after the highlighted filter.
10340 <H3>IncludeFile</H3>
10342 The IncludeFile command allows you to add a filters file to your configuration.
10343 Usually, your filters will be contained in your Alpine configuration file.
10344 If you wish, some or all of your filters may be stored in a separate file.
10345 If a filters file already exists (maybe it was made by somebody else using
10346 Alpine), you may insert it before the currently highlighted filter.
10347 You may also insert an empty file or a file that does not yet exist.
10348 Once you have an empty filters file in your configuration, you may use
10349 the Shuffle command to move filters into it.
10350 In fact, that's the only way to get the initial filter into the file.
10352 <H3>eXcludeFile</H3>
10354 The eXcludeFile command removes a filters file from your filters configuration.
10355 A limitation of the program is that in order to exclude a filters file
10356 that file must have at least one filter
10357 in it, otherwise you won't be able to highlight a line in the file.
10358 So you may have to add a dummy filter to the file in order to exclude the file.
10359 <P><UL>
10360 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10361 </UL>
10362 <P>
10363 <H3>Performance Considerations</H3>
10364 The number and type of patterns being tested can
10365 adversely effect performance. Issues to be aware
10366 of include:
10367 <P>
10368 <UL>
10369 <LI> The more filters you have defined the longer it will take to run down
10370 the list. Deleting unused filters is a good idea.
10371 <LI> Filtering in newsgroups served by an NNTP server will be slow
10372 if your patterns include tests other than "From:"
10373 or "Subject:".
10374 </UL>
10375 <P>
10376 <End of help on this topic>
10377 </BODY>
10378 </HTML>
10379 ===== h_rules_score =====
10380 <HTML>
10381 <HEAD>
10382 <TITLE>SETUP SCORING SCREEN</TITLE>
10383 </HEAD>
10384 <BODY>
10385 <H1>SETUP SCORING SCREEN</H1>
10386 <H2>SETUP SCORING COMMANDS</H2>
10387 <!--chtml if pinemode="function_key"-->
10388 <PRE>
10389 Available Commands -- Group 1 Available Commands -- Group 2
10390 ------------------------------- ------------------------------
10391 F1 Show Help Text F1 Show Help Text
10392 F2 See commands in next group F2 See commands in next group
10393 F3 Back to MAIN Alpine menu
10394 F4 Change configuration for rule
10395 F5 Move to previous rule F5 Include file in rule config
10396 F6 Move to next rule F6 Exclude file from config
10397 F7 Previous page of rules
10398 F8 Next page of rules
10399 F9 Add new rule F9 Replicate existing rule
10400 F10 Delete existing rule
10401 F11 Shuffle the order of rules
10402 F12 Whereis (search rule nicknames)
10403 </PRE>
10404 <!--chtml else-->
10405 <PRE>
10406 Navigation General Alpine Commands
10407 ------------------------- -----------------------
10408 P Prev rule ? Display this help text
10409 N Next rule E Back to MAIN Alpine menu
10410 - Previous page
10411 Spc (space bar) Next page
10412 W WhereIs (search for word in rule nicknames)
10414 Setup Scoring Commands
10415 ------------------------------------------------
10416 A Add new rule $ Shuffle the order of rules
10417 D Delete existing rule C Change configuration for highlighted rule
10418 R Replicate existing rule
10419 I Include file in rule config X Exclude file from rule config
10420 </PRE>
10421 <!--chtml endif-->
10423 <H2>Description of the Setup Scoring Screen</H2>
10425 Most people will not use scores at all, but if you do use them, here's how
10426 they work in Alpine.
10427 Using this screen, you may define Scoring rules.
10428 The score for a message is calculated by looking at every Score rule defined
10429 and adding up the Score Values for the ones that match the message.
10430 If there are no matches for a message, it has a score of zero.
10431 Message scores may be used a couple of ways in Alpine.
10433 <H3>Sorting by Score</H3>
10435 One of the methods you may use to sort message indexes is to sort by
10436 score.
10437 The scores of all the messages in a folder will be calculated and then
10438 the index will be ordered by placing the messages in order of ascending or
10439 descending score.
10441 <H3>Scores for use in Patterns</H3>
10443 The Patterns used for Roles, Index Line Coloring, and Filtering have a
10444 category labeled "Score Interval".
10445 When a message is being compared with a Pattern to check for a match, if
10446 the Score Interval is set only messages that have a score somewhere in
10447 the interval are a match.
10449 <H2>Scoring Rule Patterns</H2>
10451 In order to determine whether or not a message matches a scoring rule
10452 the message is compared with the rule's Pattern.
10453 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10454 Scoring, Other Rules, and Search Rules, so are described in only one place,
10455 "<A HREF="h_rule_patterns">here</A>".
10457 <P>
10458 Actually, Scoring rule Patterns are slightly different from the other types of
10459 Patterns because Scoring rule Patterns don't contain a Score Interval.
10460 In other words, when calculating the score for a message, which is done
10461 by looking at the Scoring rule Patterns, scores aren't used.
10463 <H2>Score Value</H2>
10465 This is the value that will be added to the score for a message if the
10466 rule's Pattern is a match.
10467 Each individual Score Value is an integer between -100 and 100, and the
10468 values from matching rules are added together to get a message's score.
10469 There is also a way to extract the value from a particular header of each
10470 message. See the help text for Score Value for further information.
10472 <H2>Command Descriptions</H2>
10474 <H3>Add</H3>
10476 The Add command is used to add a new scoring rule definition.
10477 The new rule will be added after the highlighted rule.
10479 <H3>Delete</H3>
10481 The Delete command deletes the currently highlighted scoring rule.
10483 <H3>Change</H3>
10485 The Change command lets you edit the nickname, Pattern,
10486 and Score Value of the currently highlighted scoring rule.
10488 <H3>Shuffle</H3>
10490 The Shuffle command allows you to change the order of the scoring rules.
10491 You may move the currently highlighted rule up or down in the list.
10492 The order of the rules is important since the rules are tested for a
10493 match starting with the first rule and continuing until a match is found.
10494 You should place the rules with more specific Patterns near the beginning
10495 of the list, and those with more general Patterns near the end so that
10496 the more specific matches will happen when appropriate.
10498 <H3>Replicate</H3>
10500 The Replicate command is used to copy an existing rule and modify it.
10501 The new rule will be added after the highlighted rule.
10503 <H3>IncludeFile</H3>
10505 The IncludeFile command allows you to add a rules file to your configuration.
10506 Usually, your rules will be contained in your Alpine configuration file.
10507 If you wish, some or all of your rules may be stored in a separate file.
10508 If a rules file already exists (maybe it was made by somebody else using
10509 Alpine), you may insert it before the currently highlighted rule.
10510 You may also insert an empty file or a file that does not yet exist.
10511 Once you have an empty rules file in your configuration, you may use
10512 the Shuffle command to move rules into it.
10513 In fact, that's the only way to get the initial rule into the file.
10515 <H3>eXcludeFile</H3>
10517 The eXcludeFile command removes a rules file from your rules configuration.
10518 A limitation of the program is that in order to exclude a rules file
10519 that file must have at least one rule
10520 in it, otherwise you won't be able to highlight a line in the file.
10521 So you may have to add a dummy rule to the file in order to exclude the file.
10522 <P><UL>
10523 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10524 </UL>
10525 <P>
10526 <End of help on this topic>
10527 </BODY>
10528 </HTML>
10529 ===== h_direct_config =====
10530 <HTML>
10531 <HEAD>
10532 <TITLE>SETUP LDAP DIRECTORY SERVERS SCREEN</TITLE>
10533 </HEAD>
10534 <BODY>
10535 <H1>SETUP LDAP DIRECTORY SERVERS SCREEN</H1>
10536 <H2>SETUP LDAP DIRECTORY SERVERS COMMANDS</H2>
10537 <!--chtml if pinemode="function_key"-->
10538 <PRE>
10539 Available Commands
10540 -------------------------------
10541 F1 Show Help Text
10542 F3 Back to MAIN Alpine menu
10543 F4 Change configuration for directory server
10544 F5 Move to previous directory server
10545 F6 Move to next directory server
10546 F7 Previous page of directory servers
10547 F8 Next page of directory servers
10548 F9 Add new directory server
10549 F10 Delete existing directory server
10550 F11 Shuffle the order of directory servers
10551 F12 Whereis (search directory server titles)
10552 </PRE>
10553 <!--chtml else-->
10554 <PRE>
10555 Navigation General Alpine Commands
10556 ------------------------- -----------------------
10557 P Prev Directory Server ? Display this help text
10558 N Next Directory Server E Back to MAIN Alpine menu
10559 - Previous page
10560 Spc (space bar) Next page
10561 W WhereIs (search for word in directory server titles)
10563 Setup LDAP Directory Server Commands
10564 ------------------------------------------------
10565 A Add new directory server $ Shuffle the order of directory servers
10566 D Delete existing dir server C Change configuration for highlighted server
10567 </PRE>
10568 <!--chtml endif-->
10570 <H2>Description of the Setup LDAP Directory Servers Screen</H2>
10572 This screen lets you add, delete, modify, or change the order of your
10573 directory servers. You may also set some optional behavior for each server.
10574 The "Add Dir" command brings up a blank form to
10575 fill in. You will have to supply at least the name of the LDAP server.
10576 You will often have to supply a search base to be used with that server,
10577 as well. Once the form has been brought up on your screen, there is help
10578 available for each of the options you may set.
10579 <P>
10580 The "Del Dir" command allows you to remove a directory server
10581 from your configuration.
10582 <P>
10583 The "Change" command is similar to the "Add Dir" command.
10584 The difference is that instead of bringing up a form for a new server
10585 configuration, you are changing the configuration of an existing entry.
10586 For example, you might want to correct a typing error, change a
10587 nickname, or change one of the options set for that server.
10588 <P>
10589 The "Shuffle" command is used to change the order of directory
10590 servers.
10591 <P><UL>
10592 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10593 </UL>
10594 <P>
10595 <End of help on this topic>
10596 </BODY>
10597 </HTML>
10598 ============= h_address_display ========================
10599 <HTML>
10600 <HEAD>
10601 <TITLE>SEARCH RESULTS INDEX</TITLE>
10602 </HEAD>
10603 <BODY>
10604 <H1>SEARCH RESULTS INDEX</H1>
10605 This screen shows the results, if any, of your Directory Server search.
10606 Commands (besides those for screen navigation) are:
10607 <DL>
10608 <DT>View
10609 <!--chtml if pinemode="function_key"-->
10610 (F4)
10611 <!--chtml else-->
10612 (V)
10613 <!--chtml endif-->
10614 </DT>
10615 <DD>See the full information for the selected entry.
10617 <DT>Compose
10618 <!--chtml if pinemode="function_key"-->
10619 (F9)
10620 <!--chtml else-->
10621 (C)
10622 <!--chtml endif--></DT>
10623 <DD>Compose a message with the selected entry as the recipient.
10625 <DT>Role
10626 <!--chtml if pinemode="function_key"-->
10627 (F2)
10628 <!--chtml else-->
10629 (#)
10630 <!--chtml endif--></DT>
10631 <DD>Compose a message with the selected entry as the recipient. This differs
10632 from Compose in that you may select a role before beginning your composition.
10634 <DT>Forward
10635 <!--chtml if pinemode="function_key"-->
10636 (F10)
10637 <!--chtml else-->
10638 (F)
10639 <!--chtml endif--></DT>
10640 <DD>Send the full information for the selected entry as an
10641 email message to someone else.
10643 <DT>Save
10644 <!--chtml if pinemode="function_key"-->
10645 (F11)
10646 <!--chtml else-->
10647 (S)
10648 <!--chtml endif-->
10649 </DT>
10650 <DD>Save to your address book:
10651 <UL>
10652 <LI>the result of the search (as just found through your query) for the
10653 selected entry; or
10654 <LI>the selected entry for repeated Directory Server searching when used
10655 in the future.
10656 </UL>
10657 or<BR>
10658 Export to a file (external to Alpine):
10659 <UL>
10660 <LI>the full information for the selected entry; or
10661 <LI>the email address from the selected entry; or
10662 <LI>the selected entry in <A HREF="h_whatis_vcard">vCard</A> format.
10663 </UL>
10664 <DT>WhereIs
10665 <!--chtml if pinemode="function_key"-->
10666 (F12)
10667 <!--chtml else-->
10668 (W)
10669 <!--chtml endif-->
10670 </DT>
10671 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10672 displayed text, not the full records for each entry.)
10673 </DL>
10674 <End of help on this topic>
10675 </BODY>
10676 </HTML>
10677 ============= h_address_select ========================
10678 <HTML>
10679 <HEAD>
10680 <TITLE>SEARCH RESULTS INDEX</TITLE>
10681 </HEAD>
10682 <BODY>
10683 <H1>SEARCH RESULTS INDEX</H1>
10684 This screen shows the results, if any, of your Directory Server search.
10685 Commands (besides those for screen navigation) are:
10686 <DL>
10687 <DT>Select
10688 </DT>
10689 <DD>Select this entry for use.
10691 <DT>ExitSelect
10692 <DD>Exit without selecting any of the entries.
10694 <DT>WhereIs
10695 </DT>
10696 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10697 displayed text, not the full records for each entry.)
10698 </DL>
10699 <End of help on this topic>
10700 </BODY>
10701 </HTML>
10702 ===== h_folder_maint =====
10703 <HTML>
10704 <HEAD>
10705 <TITLE>Help for Folder List</TITLE>
10706 </HEAD>
10707 <BODY>
10708 <H1>FOLDER LIST COMMANDS</H1>
10709 <!--chtml if pinemode="function_key"-->
10710 <PRE>
10711 Available Commands -- Group 1 Available Commands -- Group 2
10712 ------------------------------- ------------------------------
10713 F1 Show Help Text F1 Show Help Text
10714 F2 See commands in next group F2 See commands in next group
10715 F3 MAIN MENU Screen F3 Quit Alpine
10716 F4 Select folder and view it F4 MAIN MENU Screen
10717 F5 Move to previous folder
10718 F6 Move to next folder F6 Specify a folder to go to
10719 F7 Show previous screen of listing F7 Show MESSAGE INDEX of current folder
10720 F8 Show next screen of listing F8 Compose a message
10721 F9 Add a new folder F9 Print folder listing
10722 F10 Delete selected folder
10723 F11 Rename selected folder
10724 F12 Whereis (search folder names)
10726 Available Commands -- Group 3
10727 F1 Show Help Text
10728 F2 See commands in next group
10729 F5 Go to next new message
10730 (or count recent messages if <A HREF="h_config_tab_checks_recent"><!--#echo var="FEAT_tab-checks-recent"--></A> is set)
10731 F8 Compose a message using roles
10732 F9 Export folder to a file
10733 F10 Import the file back to a folder
10734 </PRE>
10735 <!--chtml else-->
10736 <PRE>
10737 Navigating the Folder Screen Operations on the Selected Folder
10738 ---------------------------- ---------------------------------
10739 P Move to previous folder V View Index of selected folder
10740 N Move to next folder D Delete
10741 - Show previous page of listing R Rename
10742 Spc (space bar) Show next page E Export to file
10743 U Import from file to folder
10745 FOLDER LIST Screen Commands General Alpine Command
10746 --------------------------- -----------------------
10747 A Add a folder O Show all other available commands
10748 G Specify a folder to go to ? Show Help text
10749 I Show MESSAGE INDEX of current folder M MAIN MENU Screen
10750 W Whereis (search folder names) Q Quit Alpine
10751 % Print folder listing C Compose a message
10752 # Compose a message using roles
10753 </PRE>
10754 <!--chtml endif-->
10755 <P>
10756 These commands are only available in the FOLDER LIST screen when the
10757 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"
10758 feature</A> is set in the SETUP CONFIGURATION screen:<DL>
10759 <DT>Select:</DT>
10760 <DD>Select folders by certain criteria:<UL>
10761 <LI>All: of limited use, since there is no Apply command.
10762 <LI>by Property: <UL>
10763 <LI>folder contains messages not yet seen
10764 <LI>folder contains new messages
10765 <LI>folder contains exactly as many, more, or fewer messages
10766 than a given number
10767 </UL>
10768 <LI>by Text: <UL>
10769 <LI>contained in name of folder (Name Select)
10770 <LI>contained in messages in folder (Content Select)
10771 </UL>
10772 </UL></DD>
10774 <DT>Select current:</DT>
10775 <DD>Select the folder the cursor is on. (Can be used to "manually"
10776 add one or more folders to a set created with the Select command described
10777 above.)</DD>
10778 <DT>Zoom mode:</DT>
10779 <DD>Toggles display of only selected folders or all folders on and off.</DD>
10780 </DL>
10781 <P>
10782 If the feature
10783 <A HREF="h_config_tab_checks_recent">"<!--#echo var="FEAT_tab-checks-recent"-->"</A>
10784 is set then the TAB key will display the number of recent messages and
10785 the total number of messages in the highlighted folder.
10786 <P>
10787 The "Export" command causes the lowest common denominator style
10788 mailbox to be written to a file.
10789 If the file already exists, you are asked if you want to delete it.
10790 If you say No, then the operation is aborted.
10791 Export might be a reasonable way to store a backup or an archival copy of
10792 a folder.
10793 The exported-to file is a local file on the system where you are running Alpine.
10794 The "Import" command is the opposite of the Export command.
10795 It reads a file created by Export and asks where it should save it in your
10796 folders.
10797 This could be a new folder or an existing folder.
10798 If the folder already exists, the messages from the exported file will be
10799 appended to the folder.
10800 <P>
10801 <CENTER>Description of the FOLDER LIST Screen</CENTER>
10803 The purpose of the FOLDER LIST screen is to help you browse and manage
10804 the folders and directories (also known as "hierarchy")
10805 contained within a collection.
10807 <P>
10808 Folders and directories are arranged alphabetically across lines of
10809 the screen. Directories, if present, are denoted by a special
10810 character at the end of the name known as the hierarchy delimiter
10811 (typically, "/"). By default, folders and directories are
10812 mixed together. The
10813 "<A HREF="h_config_fld_sort_rule"><!--#echo var="VAR_folder-sort-rule"--></A>"
10814 configuration option can be used to group directories toward the
10815 beginning or end of the list.
10817 <P>
10818 The Next/Prev Page commands help browse the list, the Next/Prev Fldr
10819 commands change the "selected" (i.e., highlighted) folder or
10820 directory, and the View Fldr/Dir commands will "open" the
10821 selected item. Folder and directory management is provided via the
10822 Rename, Delete and Add commands.
10824 <P><CENTER>About Folders</CENTER>
10825 What are Folders?<P>
10827 Folders are simply files where messages are kept. Every message has to be
10828 in a folder. Most every Alpine user starts out with 3 folders: an INBOX, a
10829 folder for sent mail and a folder for saved messages.<P>
10831 You may create as many other folders as you wish. They must be given
10832 names that can be filenames on the filesystem.
10833 <P>
10835 You can move messages from one folder to another by opening the original
10836 folder and saving messages into the other folder just as you can save
10837 message from your INBOX to any other folder.<P>
10839 Folders are typically just files in the filesystem. However, the files
10840 that are
10841 folders have some special formatting in them (so that Alpine knows where one
10842 message ends and another begins) and should <EM>not</EM> be edited outside of
10843 Alpine. If you want copies of your messages in text files that you can edit
10844 or otherwise manipulate, use the Export command to copy them from Alpine into
10845 your regular file area.
10847 <P>
10848 FOR MORE INFORMATION: See the section on
10849 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
10850 <P>
10851 <CENTER>About Directories</CENTER>
10852 <P>
10853 A directory is simply a container used to group folders within a
10854 folder list. You can create as many directories as you like. And
10855 directories can even contain directories themselves.
10857 <P>
10858 SPECIAL NOTES: When accessing folders on an IMAP server, it is important
10859 to note that not all IMAP servers support directories. If you find that
10860 the Add command fails to offer the "Create Directory" subcommand,
10861 then it's likely that directories are not supported by the server serving
10862 in that collection.
10864 <P>
10865 Similarly, servers that do provide for directories may not do so in
10866 the same way. On some servers, for example, each folder name you
10867 create is at the same time capable of being a directory. When this
10868 happens, Alpine will display both the folder name and the name of the
10869 directory (with trailing hierarchy delimiter) in the folder list.
10871 <P>
10872 Another issue with IMAP access, though with a much smaller set of servers,
10873 is that not all servers accept the request to list out the available
10874 folders and directories in the same way. If you find yourself having
10875 trouble viewing folders on your server, you might investigate the
10876 "<A HREF="h_config_lame_list_mode"><!--#echo var="FEAT_enable-lame-list-mode"--></A>"
10877 feature.
10878 <P>
10879 <UL>
10880 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10881 </UL>
10882 <P>
10883 <End of help on this topic>
10884 </BODY>
10885 </HTML>
10886 ========= h_valid_folder_names ========
10887 <HTML>
10888 <HEAD>
10889 <TITLE>Explanation of Valid Folder Names</TITLE>
10890 </HEAD>
10891 <BODY>
10892 <H1>Folder Name Syntax Explained</H1>
10894 Once your folder collections are defined, you can usually refer to
10895 folders by their simple (unqualified) name, or pick from a FOLDER LIST
10896 display. However, understanding the complete syntax for folder names,
10897 both local and remote, is handy when using the Goto command and when
10898 you are adding new folder collections via the Setups/collectionList screen.
10899 <P>
10900 An Alpine folder name looks like
10902 <P>
10903 <CENTER><SAMP>[{<remote-specification>}][#<namespace>]<namespace-specific-part></SAMP></CENTER>
10904 <P>
10906 The square brackets ([]) mean that the part is optional.
10908 <P>
10909 If there is no remote-specification, then the folder name is interpreted
10910 locally on the computer running Alpine.
10911 Local folder names depend on the operating system used by the computer
10912 running Alpine, as well as the configuration of that system. For example,
10913 "C:\PINE\FOLDERS\OCT-94" might exist on a PC, and
10914 "~/mail/september-1994" might be a reasonable folder name on a
10915 system running Unix.
10917 <P>
10918 Alpine users have the option of using folders that are stored on some other
10919 computer. Alpine accesses remote folders via IMAP (the Internet Message
10920 Access Protocol), or in the case of news, via NNTP (the Network News
10921 Transport Protocol). To be able to access remote folders in Alpine, the
10922 remote host must be running the appropriate server software (imapd or
10923 nntpd) and you must correctly specify the name of the folder to Alpine,
10924 including the domain name of the remote machine. For example,
10925 <P>
10926 <CENTER><SAMP>{monet.art.example.com}INBOX</SAMP></CENTER>
10927 <P>
10928 could be a remote folder specification, and so could
10929 <P>
10930 <CENTER><SAMP>{unixhost.art.example.com}~/mail/september-1994</SAMP></CENTER>
10931 and
10932 <P>
10933 <CENTER><SAMP>{winhost.art.example.com}\mymail\SEP-94</SAMP></CENTER>
10934 <P>
10935 Note that in the case of remote folders, the directory/file path in the specification is
10936 determined by the operating system of the remote computer, <B>not</B> by
10937 the operating system of the computer on which you are running Alpine.
10938 <P>
10939 As you can tell, the name of the computer is in {} brackets
10940 followed immediately by the name of the folder. (In each of these cases the
10941 optional namespace is missing.) If, as in these
10942 examples, there is no remote access protocol specified, then IMAP is
10943 assumed. Check
10944 <A HREF="h_folder_server_syntax">here</A>
10945 for a more detailed look at what options can be placed between the brackets.
10946 If there are no brackets at all, then the folder name is interpreted locally
10947 on the computer on which you are running Alpine.
10949 <P>
10950 To the right of the brackets when a server name is present, or at the
10951 start of the foldername if no server is present, the sharp sign,
10952 "#", holds special meaning. It indicates a folder name
10953 outside the area reserved for your personal folders. In fact, it's
10954 used to indicate both the name of the folder, and a special phrase
10955 telling Alpine how to interpret the name that follows.
10957 <P>
10958 So, for example, Alpine can be used to access a newsgroup that might be
10959 available on your computer using:
10960 <P>
10961 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
10962 <P>
10963 The sharp sign indicates the folder name is outside your personal
10964 folder area. The "news." phrase after it tells Alpine to
10965 interpret the remainder of the name as a newsgroup.
10967 <P>
10968 Similarly, to access a newsgroup on your IMAP server, you might
10969 use something like:
10970 <P>
10971 <CENTER><SAMP>{wharhol.art.example.com}#news.comp.mail.misc</SAMP></CENTER>
10973 <P>
10974 There are a number of such special phrases (or "namespaces")
10975 available. For a more detailed explanation read about
10976 <A HREF="h_folder_name_namespaces">Namespaces</A>.
10978 <P>
10979 Note that "INBOX" has special meaning in both local and remote folder
10980 names. The name INBOX refers to your "principal incoming
10981 message folder" and will be mapped to the actual file name used for your
10982 INBOX on any given host. Therefore, a name like
10983 "{xxx.art.example.com}INBOX" refers to whatever file is used to
10984 store incoming mail for you on that particular host.
10986 <P>
10987 <End of help on this topic>
10988 </BODY>
10989 </HTML>
10990 ======= h_folder_name_namespaces =======
10991 <HTML>
10992 <HEAD>
10993 <TITLE>FOLDER NAME NAMESPACES EXPLAINED</TITLE>
10994 </HEAD>
10995 <BODY>
10996 <H1>Folder Name Namespaces Explained</H1>
10998 An Alpine folder name looks like
11000 <P>
11001 <CENTER><SAMP>[{<remote-specification>}][#<namespace>][<namespace-specific-part>]</SAMP></CENTER>
11002 <P>
11004 The local part of a folder name has an optional "Namespace" which
11005 tells Alpine how to interpret the rest of the name.
11007 <P>
11008 By default the folder name is interpreted as defining a section of your personal
11009 folder area. This area and how you specify it are defined by the
11010 server, if one is specified, or, typically, the home
11011 directory, if no server is defined.
11013 <P>
11014 If a namespace is specified, it begins with the
11015 sharp, "#", character followed by the name of the namespace
11016 and then the namespace's path-element-delimiter. Aside from the
11017 path's format, namespaces can also imply access rights, content
11018 policy, audience, location, and, occasionally, access methods.
11020 <P>
11021 Each server exports its own set (possibly of size one) of
11022 namespaces. Hence, it's likely communication with your server's
11023 administrator will be required for specific configurations. Some of
11024 the more common namespaces, however, include:
11026 <DL>
11027 <DT>#news.</DT>
11028 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
11029 names are hierarchically defined with each level delimited by a period.
11030 <P>
11031 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
11032 <P>
11033 </DD>
11034 <DT>#public/</DT>
11035 <DD>This specifies a folder area that the server may export to the general
11036 public.
11037 </DD>
11038 <DT>#shared/</DT>
11039 <DD>This specifies a folder area that the server may export to groups
11040 of users.
11041 </DD>
11042 <DT>#ftp/</DT>
11043 <DD>This specifies a folder area that is the same as that it may have
11044 exported via the "File Transfer Protocol".
11045 </DD>
11046 <DT>#mh/</DT>
11047 <DD>This specifies the personal folder area associated with folders
11048 and directories that were created using the MH message handling system.
11049 </DD>
11050 <DT>#move/</DT>
11051 <DD>This namespace is interpreted locally by Alpine. It has an unusual interpretation and format.
11052 <P>
11053 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
11054 <P>
11055 The #move namespace is followed by two folder names separated by a delimiter
11056 character.
11057 The delimiter character may be any character that does not appear in
11058 the MailDropFolder name.
11059 The meaning of #move is that mail will be copied from the MailDropFolder to
11060 the DestinationFolder and then deleted (if possible) from the MailDropFolder.
11061 Periodic checks at frequency
11062 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A>, but with a minimum
11063 time between checks set by
11064 <A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>,
11065 are made for new mail arriving in the MailDropFolder.
11066 An example that copies mail from a POP inbox to a local folder follows
11067 <P>
11068 <CENTER><SAMP>#move+{popserver.example.com/pop3/ssl}inbox+local folder</SAMP></CENTER>
11069 <P>
11070 To you it appears that mail is being delivered to the local folder when it
11071 is copied from the MailDropFolder, and you read mail from the local folder.
11072 <P>
11073 Note that if the DestinationFolder does not exist then the messages are not
11074 copied from the MailDropFolder.
11075 A #move folder may only be used as an
11076 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
11077 an Inbox.
11078 When you are in the FOLDER LIST of Incoming Message Folders (after turning
11079 on the
11080 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
11081 option)
11082 the Add command has a subcommand "Use Mail Drop"
11083 which may be helpful for defining the folder in your Alpine configuration.
11084 The same is true when you edit the
11085 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
11086 option in Setup/Config.
11087 Each of these configuration methods will also create the DestinationFolder
11088 if it doesn't already exist.
11089 If you are having problems, make sure the DestinationFolder exists.
11090 You may find some more useful information about Mail Drops at
11091 <A HREF="h_maildrop">What is a Mail Drop?</A>.
11092 </DD>
11093 </DL>
11094 <P>
11096 In addition, the server may support access to other user's folders,
11097 provided you have suitable permissions. Common methods use a prefix
11098 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
11099 indicate the root of the other user's folder area.
11101 <P>
11102 No, nothing's simple.
11104 <P>
11105 <End of help on this topic>
11106 </BODY>
11107 </HTML>
11108 ============= h_whatis_vcard ========================
11109 <HTML>
11110 <HEAD>
11111 <TITLE>VCARD EXPLAINED</TITLE>
11112 </HEAD>
11113 <BODY>
11114 <H1>What is the vCard format?</H1>
11115 A "vCard" is a sort of electronic business card, for exchanging
11116 information about and among people and organizations electronically.
11117 More information about vCard can be found (as of May 1998) on the WWW site
11118 of the Internet Mail Consortium at the URL:
11119 <P>
11120 <CENTER><A HREF="http://www.imc.org/pdi/">http://www.imc.org/pdi/</A></CENTER>
11121 <P>
11122 <End of help on this topic>
11123 </BODY>
11124 </HTML>
11125 ===== h_folder_open =====
11126 <HTML>
11127 <HEAD>
11128 <TITLE>Explanation of Folder Selection</TITLE>
11129 </HEAD>
11130 <BODY>
11131 <BR>
11132 <BR>
11133 This screen is designed to allow you to quickly and easily survey your
11134 folders and select one to open.
11135 <!--chtml if pinemode="function_key"-->
11136 <PRE>
11137 Navigating the List of Folders General Alpine Commands
11138 ------------------------------ -----------------------
11139 P Move to previous folder ? Show this help text
11140 N Move to next folder
11141 - Show previous screen of folders
11142 Spc (space bar) Show next screen
11143 W WhereIs (search folder names)
11145 Folder Selection Commands
11146 -------------------------
11147 E Exit the Folder Select menu (without selecting a folder)
11148 S Select the currently highlighted folder
11149 </PRE>
11150 <!--chtml else-->
11151 <PRE>
11152 Navigating the List of Folders General Alpine Commands
11153 ------------------------------ -----------------------
11154 F5 Move to previous folder F1 Show this help text
11155 F6 Move to next folder
11156 F7 Show previous screen of folders
11157 F8 Show next screen of folders
11158 F12 WhereIs (search folder names)
11160 Folder Selection Commands
11161 -------------------------
11162 F3 Exit the Folder Select menu (without selecting a folder)
11163 F4 Select the currently highlighted folder
11164 </PRE>
11165 <!--chtml endif-->
11166 <P>
11167 FOR MORE INFORMATION: See the section on
11168 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11169 <P>
11170 <End of help on this topic>
11171 </BODY>
11172 </HTML>
11173 ===== h_folder_subscribe =====
11174 <HTML>
11175 <HEAD>
11176 <TITLE>Newsgroup Subcribe Screen explained</TITLE>
11177 </HEAD>
11178 <BODY>
11179 <H1>FOLDER SUBSCRIBE HELP</H1>
11181 This screen is designed to help you subscribe to newsgroups you are
11182 not currently subscribed to. The screen display is a list of all
11183 available newsgroups (or possibly a partial list if you specified a
11184 partial name when entering the screen). Groups you have already
11185 subscribed to have the letters "SUB" next to them. You may
11186 select a single new group to subscribe to by moving the cursor to that
11187 group and pressing "S" or carriage return. Alternatively,
11188 you may change into ListMode with the "ListMode" command.
11189 The display will change slightly so that each group has a checkbox in
11190 front of it. Use the cursor and the Set/Unset command to place an
11191 "X" in front of each newsgroup you wish to subscribe to.
11192 <P>
11194 When you are finished marking groups, the "Subscribe"
11195 command will subscribe you to those groups you have marked. Note, you
11196 may not unsubscribe to groups with this command. Instead of the
11197 "A" "Subscribe" command, use the "D"
11198 UnSbscrbe command.
11199 <P>
11201 <!--chtml if pinemode="function_key"-->
11202 <PRE>
11203 Navigating the List of Newsgroups General Alpine Commands
11204 --------------------------------- -----------------------
11205 F5 Move to previous group F1 Show this help text
11206 F6 Move to next group
11207 F7 Show previous screen of groups
11208 F8 Show next screen of groups
11209 F12 WhereIs (search group names)
11210 F9 Use ListMode
11212 Group Selection Commands
11213 -------------------------
11214 F3 Exit the News Subscribe menu (without selecting any groups)
11215 F4 Subscribe to the currently highlighted newsgroup
11216 </PRE>
11217 <!--chtml else-->
11218 <PRE>
11219 Navigating the List of Newsgroups General Alpine Commands
11220 --------------------------------- -----------------------
11221 P Move to previous group ? Show this help text
11222 N Move to next group
11223 - Show previous screen of groups
11224 Spc (space bar) Show next screen
11225 W WhereIs (search group names)
11226 L Use ListMode
11228 Group Selection Commands
11229 -------------------------
11230 E Exit the News Subscribe menu (without selecting any groups)
11231 S Subscribe to the currently highlighted newsgroup
11232 </PRE>
11233 <!--chtml endif-->
11234 <P>
11235 When in ListMode, there is an additional command for marking groups to
11236 subscribe to:
11237 <P>
11238 <!--chtml if pinemode="function_key"-->
11239 <PRE>
11240 ListMode Commands
11241 -------------------------
11242 F9 Set or unset the highlighted group
11243 </PRE>
11244 <!--chtml else-->
11245 <PRE>
11246 ListMode Commands
11247 -------------------------
11248 X Set or unset the highlighted group
11249 </PRE>
11250 <!--chtml endif-->
11251 <P>
11252 <End of help on this topic>
11253 </BODY>
11254 </HTML>
11255 ===== h_folder_postnews =====
11256 <HTML>
11257 <HEAD>
11258 <TITLE>Newsgroup selecting for Posting explained</TITLE>
11259 </HEAD>
11260 <BODY>
11261 This screen is designed to allow you to quickly and easily survey
11262 the available newsgroups and select one to post news to.
11263 <P>
11264 <!--chtml if pinemode="function_key"-->
11265 <PRE>
11266 Navigating the List of Newsgroups General Alpine Commands
11267 --------------------------------- -----------------------
11268 F5 Move to previous group F1 Show this help text
11269 F6 Move to next group
11270 F7 Show previous screen of groups
11271 F8 Show next screen of groups
11272 F12 WhereIs (search group names)
11274 Group Selection Commands
11275 -------------------------
11276 F3 Exit the Selection menu (without selecting a group)
11277 F4 Select the currently highlighted newsgroup
11278 </PRE>
11279 <!--chtml else-->
11280 <PRE>
11281 Navigating the List of Newsgroups General Alpine Commands
11282 --------------------------------- -----------------------
11283 P Move to previous group ? Show this help text
11284 N Move to next group
11285 - Show previous screen of groups
11286 Spc (space bar) Show next screen of groups
11287 W WhereIs (search group names)
11289 Group Selection Commands
11290 -------------------------
11291 E Exit the Selection menu (without selecting a group)
11292 S Select the currently highlighted newsgroup
11293 </PRE>
11294 <!--chtml endif-->
11295 <P>
11296 <End of help on this topic>
11297 </BODY>
11298 </HTML>
11299 ===== h_folder_save =====
11300 <HTML>
11301 <HEAD>
11302 <TITLE>Folder Select for Save Explained</TITLE>
11303 </HEAD>
11304 <BODY>
11305 This screen is designed to allow you to quickly and easily survey your
11306 folders and select one to use for saving the current message.
11307 <P>
11309 <!--chtml if pinemode="function_key"-->
11310 <PRE>
11311 Navigating the List of Folders General Alpine Commands
11312 ------------------------------ -----------------------
11313 F5 Move to previous folder F1 Show this help text
11314 F6 Move to next folder
11315 F7 Show previous screen of folders
11316 F8 Show next screen of folders
11317 F12 WhereIs (search folder names)
11319 Folder Selection Commands
11320 -------------------------
11321 F3 Exit the Folder Select menu (without selecting a folder)
11322 F4 Select the currently highlighted folder
11323 F11 AddNew folder (just like Select, but you type in a new folder name)
11324 </PRE>
11325 <!--chtml else-->
11326 <PRE>
11327 Navigating the List of Folders General Alpine Commands
11328 ------------------------------ -----------------------
11329 P Move to previous folder ? Show this help text
11330 N Move to next folder
11331 - Show previous screen of folders
11332 Spc (space bar) Show next screen of folders
11333 W WhereIs (search folder names)
11335 Folder Selection Commands
11336 -------------------------
11337 E Exit the Folder Select menu (without selecting a folder)
11338 S Select the currently highlighted folder
11339 A AddNew folder (just like Select, but you type in a new folder name)
11340 </PRE>
11341 <!--chtml endif-->
11342 <P>
11343 FOR MORE INFORMATION: See the section on
11344 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11345 <P>
11346 <End of help on this topic>
11347 </BODY>
11348 </HTML>
11349 ===== h_folder_fcc =====
11350 <HTML>
11351 <HEAD>
11352 <TITLE>Folder Select for Fcc Explained</TITLE>
11353 </HEAD>
11354 <BODY>
11355 This screen is designed to allow you to quickly and easily survey your
11356 folders and select one to use as the file carbon copy (fcc) for the
11357 current message.
11358 <P>
11360 <!--chtml if pinemode="function_key"-->
11361 <PRE>
11362 Navigating the List of Folders General Alpine Commands
11363 ------------------------------ -----------------------
11364 F5 Move to previous folder F1 Show this help text
11365 F6 Move to next folder
11366 F7 Show previous screen of folders
11367 F8 Show next screen of folders
11368 F12 WhereIs (search folder names)
11370 Folder Selection Commands
11371 -------------------------
11372 F3 Exit the Folder Select menu (without selecting a folder)
11373 F4 Select the currently highlighted folder
11374 F11 AddNew folder (just like Select, but you type in a new folder name)
11375 </PRE>
11376 <!--chtml else-->
11377 <PRE>
11378 Navigating the List of Folders General Alpine Commands
11379 ------------------------------ -----------------------
11380 P Move to previous folder ? Show this help text
11381 N Move to next folder
11382 - Show previous screen of folders
11383 Spc (space bar) Show next screen of folders
11384 W WhereIs (search folder names)
11386 Folder Selection Commands
11387 -------------------------
11388 E Exit the Folder Select menu (without selecting a folder)
11389 S Select the currently highlighted folder
11390 A AddNew folder (just like Select, but you type in a new folder name)
11391 </PRE>
11392 <!--chtml endif-->
11393 <P>
11394 FOR MORE INFORMATION: See the section on
11395 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11396 <P>
11397 <End of help on this topic>
11398 </BODY>
11399 </HTML>
11400 ===== h_folder_pattern_roles =====
11401 <HTML>
11402 <HEAD>
11403 <TITLE>Folder Select for Current Folder Explained</TITLE>
11404 </HEAD>
11405 <BODY>
11406 This screen is designed to allow you to quickly and easily survey your
11407 folders and select one to use as the specific Current Folder
11408 in a Pattern.
11409 <P>
11411 <!--chtml if pinemode="function_key"-->
11412 <PRE>
11413 Navigating the List of Folders General Alpine Commands
11414 ------------------------------ -----------------------
11415 F5 Move to previous folder F1 Show this help text
11416 F6 Move to next folder
11417 F7 Show previous screen of folders
11418 F8 Show next screen of folders
11419 F12 WhereIs (search folder names)
11421 Folder Selection Commands
11422 -------------------------
11423 F3 Exit the Folder Select menu (without selecting a folder)
11424 F4 Select the currently highlighted folder
11425 F11 AddNew folder (just like Select, but you type in a new folder name)
11426 </PRE>
11427 <!--chtml else-->
11428 <PRE>
11429 Navigating the List of Folders General Alpine Commands
11430 ------------------------------ -----------------------
11431 P Move to previous folder ? Show this help text
11432 N Move to next folder
11433 - Show previous screen of folders
11434 Spc (space bar) Show next screen of folders
11435 W WhereIs (search folder names)
11437 Folder Selection Commands
11438 -------------------------
11439 E Exit the Folder Select menu (without selecting a folder)
11440 S Select the currently highlighted folder
11441 A AddNew folder (just like Select, but you type in a new folder name)
11442 </PRE>
11443 <!--chtml endif-->
11444 <P>
11445 FOR MORE INFORMATION: See the section on
11446 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11447 <P>
11448 <End of help on this topic>
11449 </BODY>
11450 </HTML>
11451 ===== h_folder_stayopen_folders =====
11452 <HTML>
11453 <HEAD>
11454 <TITLE>Folder Select Explained</TITLE>
11455 </HEAD>
11456 <BODY>
11457 This screen is designed to allow you to quickly and easily survey your
11458 folders and select one to use as a Stay-Open folder.
11459 <P>
11461 <!--chtml if pinemode="function_key"-->
11462 <PRE>
11463 Navigating the List of Folders General Alpine Commands
11464 ------------------------------ -----------------------
11465 F5 Move to previous folder F1 Show this help text
11466 F6 Move to next folder
11467 F7 Show previous screen of folders
11468 F8 Show next screen of folders
11469 F12 WhereIs (search folder names)
11471 Folder Selection Commands
11472 -------------------------
11473 F3 Exit the Folder Select menu (without selecting a folder)
11474 F4 Select the currently highlighted folder
11475 F11 AddNew folder (just like Select, but you type in a new folder name)
11476 </PRE>
11477 <!--chtml else-->
11478 <PRE>
11479 Navigating the List of Folders General Alpine Commands
11480 ------------------------------ -----------------------
11481 P Move to previous folder ? Show this help text
11482 N Move to next folder
11483 - Show previous screen of folders
11484 Spc (space bar) Show next screen of folders
11485 W WhereIs (search folder names)
11487 Folder Selection Commands
11488 -------------------------
11489 E Exit the Folder Select menu (without selecting a folder)
11490 S Select the currently highlighted folder
11491 A AddNew folder (just like Select, but you type in a new folder name)
11492 </PRE>
11493 <!--chtml endif-->
11494 <P>
11495 FOR MORE INFORMATION: See the section on
11496 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11497 <P>
11498 <End of help on this topic>
11499 </BODY>
11500 </HTML>
11501 ===== h_folder_action_roles =====
11502 <HTML>
11503 <HEAD>
11504 <TITLE>Folder Select Explained</TITLE>
11505 </HEAD>
11506 <BODY>
11507 This screen is designed to allow you to quickly and easily survey your
11508 folders and select one to use as the folder into which messages
11509 matching this filter will be moved.
11510 <P>
11512 <!--chtml if pinemode="function_key"-->
11513 <PRE>
11514 Navigating the List of Folders General Alpine Commands
11515 ------------------------------ -----------------------
11516 F5 Move to previous folder F1 Show this help text
11517 F6 Move to next folder
11518 F7 Show previous screen of folders
11519 F8 Show next screen of folders
11520 F12 WhereIs (search folder names)
11522 Folder Selection Commands
11523 -------------------------
11524 F3 Exit the Folder Select menu (without selecting a folder)
11525 F4 Select the currently highlighted folder
11526 F11 AddNew folder (just like Select, but you type in a new folder name)
11527 </PRE>
11528 <!--chtml else-->
11529 <PRE>
11530 Navigating the List of Folders General Alpine Commands
11531 ------------------------------ -----------------------
11532 P Move to previous folder ? Show this help text
11533 N Move to next folder
11534 - Show previous screen of folders
11535 Spc (space bar) Show next screen of folders
11536 W WhereIs (search folder names)
11538 Folder Selection Commands
11539 -------------------------
11540 E Exit the Folder Select menu (without selecting a folder)
11541 S Select the currently highlighted folder
11542 A AddNew folder (just like Select, but you type in a new folder name)
11543 </PRE>
11544 <!--chtml endif-->
11545 <P>
11546 FOR MORE INFORMATION: See the section on
11547 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11548 <P>
11549 <End of help on this topic>
11550 </BODY>
11551 </HTML>
11552 ===== h_abook_config =====
11553 <HTML>
11554 <HEAD>
11555 <TITLE>SETUP ADDRESS BOOKS SCREEN</TITLE>
11556 </HEAD>
11557 <BODY>
11558 <H1>SETUP ADDRESS BOOKS SCREEN</H1>
11559 <H2>SETUP ADDRESS BOOKS COMMANDS</H2>
11560 <!--chtml if pinemode="function_key"-->
11561 <PRE>
11562 Available Commands
11563 -------------------------------
11564 F1 Show Help Text
11565 F3 Back to MAIN Alpine menu
11566 F4 Change configuration for address book
11567 F5 Move to previous address book
11568 F6 Move to next address book
11569 F7 Previous page of address books
11570 F8 Next page of address books
11571 F9 Add new address book
11572 F10 Delete existing address book
11573 F11 Shuffle the order of address books
11574 F12 Whereis (search address book titles)
11575 </PRE>
11576 <!--chtml else-->
11577 <PRE>
11578 Navigation General Alpine Commands
11579 ----------------------- -----------------------
11580 P Prev Address Book ? Display this help text
11581 N Next Address Book E Back to MAIN Alpine menu
11582 - Previous page
11583 Spc (space bar) Next page
11584 W WhereIs (search for word in address book titles)
11586 Setup Address Books Commands
11587 ------------------------------------------------
11588 A Add new address book $ Shuffle the order of address books
11589 D Delete existing address book C Change configuration for address book
11590 </PRE>
11591 <!--chtml endif-->
11593 <H2>Description of the Setup Address Books Screen</H2>
11595 This screen lets you add, delete, modify, or change the order of your
11596 address books. The "Add Abook" command brings up a blank form to
11597 fill in. If you are adding a remote address book on an IMAP server
11598 you should fill in the name of the IMAP server. Otherwise, leave
11599 that field blank. (Note that remote IMAP address books are an Alpine
11600 concept and are unlikely to interoperate with other mail clients.)
11601 For a remote address book, fill in the name of the remote folder
11602 in the Folder field. This should be a folder that is used only for
11603 this one purpose, not a general purpose folder you expect to store
11604 messages in.
11605 <P>If you are adding a local address book, fill in the
11606 Folder Name field with a local file name (e.g., .addressbook).
11607 <P>
11608 <B>Please note:</B> Remote address books stored on an IMAP server are
11609 of an entirely different format (namely, a special-purpose
11610 "mail folder") than that of the local addressbook familiar
11611 to Alpine users. Therefore,
11612 you cannot use "add a remote address book" to make an existing
11613 Alpine .addressbook file you may have on a remote IMAP server accessible to
11614 Alpine running on a different host.
11615 <P>
11617 The "Del Abook" command allows you to remove an address book
11618 from your configuration. It will also ask you if you wish to remove
11619 the data for that address book, which would erase all traces of the
11620 address book if you answer Yes.
11621 <P>
11623 The "Change" command is similar to the "Add Abook" command.
11624 The difference is that instead of adding a new address book to your
11625 configuration, you are changing the configuration of an existing entry.
11626 For example, you might want to correct a typing error or change a
11627 nickname. The "Change" command is not a move command. If you
11628 change the folder name or server name the data will not be moved for you.
11629 <P>
11631 The "Shuffle" command is used for two purposes. If you shuffle
11632 an address book toward another address book in the same group then
11633 the order of those two address books will be swapped. If you shuffle
11634 the last Personal address book down towards the Global address book
11635 section, it will become a Global address book. If you shuffle
11636 the first Global address book up it will become a Personal address
11637 book. The main difference between Personal and Global address
11638 books is that Global address books are forced read-only.
11639 <P><UL>
11640 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11641 </UL>
11642 <P>
11643 <End of help on this topic>
11644 </BODY>
11645 </HTML>
11646 ===== h_abook_top =====
11647 <HTML>
11648 <HEAD>
11649 <TITLE>ADDRESS BOOK LIST COMMANDS</TITLE>
11650 </HEAD>
11651 <BODY>
11652 <H1>ADDRESS BOOK LIST COMMANDS</H1>
11653 <!--chtml if pinemode="function_key"-->
11654 <PRE>
11655 Available Commands -- Group 1 Available Commands -- Group 2
11656 ------------------------------- ------------------------------
11657 F1 Show Help Text F1 Show Help Text
11658 F2 See commands in next group F2 See commands in next group
11659 F3 Exit to MAIN MENU F3 Quit Alpine
11660 F4 View/Edit selected address book
11661 F5 Move to previous address book F5 FOLDER LIST screen
11662 F6 Move to next address book F6 Specify a folder to go to
11663 F7 Previous page F7 MESSAGE INDEX screen
11664 F8 Next page F9 Print list of address books
11665 F12 Whereis (search for word)
11666 </PRE>
11667 <!--chtml else-->
11668 <PRE>
11669 Navigation General Alpine Commands
11670 ----------------------- -----------------------
11671 P Previous Entry ? Display this help text
11672 N Next Entry O Show all other available commands
11673 - Previous page < Back to MAIN Alpine menu
11674 Spc (space bar) Next page Q Quit Alpine
11675 W WhereIs (search for word) L FOLDER LIST screen
11676 G Specify a folder to go to
11677 Address Book Commands I MESSAGE INDEX screen
11678 ------------------------------------------------
11679 > View/Edit selected address book
11680 or
11681 > Search on selected directory server
11683 % Print list of address books and directory servers
11684 </PRE>
11685 <!--chtml endif-->
11687 <H2>Description of the Address Book List Screen</H2>
11689 From this screen you may choose which address book you wish to view
11690 or edit. For more information on address books, view one of your
11691 address books (with
11692 <!--chtml if pinemode="function_key"-->
11693 F4
11694 <!--chtml else-->
11695 ">"
11696 <!--chtml endif-->)
11697 and see the Help Text there.<P>
11699 You may also choose a directory server on which to search for entries.
11700 You do that by highlighting the directory server line and using
11701 <!--chtml if pinemode="function_key"-->
11702 F4
11703 <!--chtml else-->
11704 ">"
11705 <!--chtml endif-->.<P>
11707 If you wish to define new address books or directory servers go to the Main
11708 menu and choose Setup. You may then either choose to setup AddressBooks or
11709 Directory (among other things). It's possible that the Directory option
11710 will not be there if the Alpine you are using does not contain LDAP directory
11711 lookup functionality.
11713 <P><UL>
11714 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11715 </UL><P>
11716 <End of help on this topic>
11717 </BODY>
11718 </HTML>
11719 ===== h_abook_opened =====
11720 <HTML>
11721 <HEAD>
11722 <TITLE>THE ALPINE ADDRESS BOOK</TITLE>
11723 </HEAD>
11724 <BODY>
11725 <H1>THE ALPINE ADDRESS BOOK</H1>
11726 <H2>ADDRESS BOOK COMMANDS</H2>
11727 <PRE>
11728 <!--chtml if pinemode="function_key"-->
11729 Available Commands -- Group 1 Available Commands -- Group 2
11730 ------------------------------- ------------------------------
11731 F1 Show Help Text F1 Show Help Text
11732 F2 See commands in next group F2 See commands in next group
11733 F3 Exit this screen F3 Quit Alpine
11734 F4 View/Edit selected entry F4 Go to MAIN MENU screen
11735 F5 Move to previous entry F5 FOLDER LIST screen
11736 F6 Move to next entry F6 Specify a folder to go to
11737 F7 Previous page of address book F7 MESSAGE INDEX screen
11738 F8 Next page of address book F8 Compose to entry using roles
11739 F9 Add new entry to address book F9 Print address book
11740 F10 Delete selected entry F10 TakeAddr to another addrbook
11741 F11 Compose to selected entry F11 Save or Export addrbook selections
11742 F12 Whereis (search address book) F12 Forward entry by mail
11744 Available Commands -- Group 3
11745 ------------------------------
11746 F3 Select F6 Zoom (or unZoom)
11747 F5 Select Current F7 Apply Command to Selection
11748 <!--chtml else-->
11749 Address Book Navigation General Alpine Commands
11750 ----------------------- -----------------------
11751 P Prev Address ? Display this help text
11752 N Next Address O Show all other available commands
11753 - Previous page of address book M Back to MAIN MENU
11754 Spc (space bar) Next page Q Quit Alpine
11755 W WhereIs (search for word C Compose message to selected addr
11756 or name in address book) # Compose to addr using roles
11757 < To List of Address Books if L FOLDER LIST screen
11758 more than one, else to MAIN G Specify a folder to go to
11759 I MESSAGE INDEX screen
11761 Address Book Commands
11762 ----------------------------------------------------
11763 > View/Update selected entry D Delete selected entries
11764 % Print address book S Save or Export address book selections
11765 F Forward entries by mail @ Add new entry to address book
11767 ; Select command Z Toggle Zoom Mode
11768 : Select highlighted entry A Apply command to selected entries
11770 <!--chtml endif-->
11771 </PRE>
11772 Note: The presence or absence of the final four commands above is
11773 controlled by the option
11774 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>.
11775 <P>
11777 <H2>Description of the Address Book Screen</H2>
11779 This screen lets you edit and manage entries in your address book. It
11780 also acts as a short-cut for composing messages to people in the address
11781 book. When, from this screen, you press <!--chtml if pinemode="function_key"-->F11<!--chtml else-->"C"<!--chtml endif--> for ComposeTo, the
11782 message starts "pre-addressed" to whatever address book entry is
11783 currently selected. If you use the <!--chtml if pinemode="function_key"-->F8<!--chtml else-->"#"<!--chtml endif--> for Role, you may first select a
11784 role to use in your composition.
11785 <P>
11786 Alpine's address book helps you keep a list of addresses you send email to so
11787 you do not have to remember addresses that are often complex. Each entry
11788 in the address book has five fields, all of them optional. The three
11789 elements that are usually visible on the ADDRESS BOOK display, are: <DL>
11791 <P><DT>NICKNAME: <DD>A short easy-to-remember label to identify the entry.
11792 This is what you type in as you are addressing the message in the
11793 composer. If there is a matching entry in your address book(s),
11794 Alpine will extract the corresponding FullName and Address fields to
11795 generate the actual address for your message.
11797 <P><DT>FULLNAME: <DD>A longer field where you can put the full name
11798 of the
11799 person or organization. Usually the full names are put in last
11800 name first so they sort nicely in alphabetical order. Whatever
11801 you put as the name here will appear on the message when it is
11802 finally delivered. Examples:<PRE>
11803 Garcia Marquez, Gabriel
11804 Henscheid, Eckhard
11805 Alpine-Info mailing list
11806 Library materials renewal requests
11807 Kim An-guk
11808 "George III, King of Great Britain, 1738-1820"
11809 </PRE>
11810 (In the second-to-last example, no comma is used in the name so that
11811 the family name appears first in the address book and when the entry is
11812 used in the composer.
11813 In the last example, retaining the commas is intended;
11814 double-quotation marks surround the name to
11815 prevent the transposition of its parts when the entry is used in
11816 the composer.)
11818 <P><DT>ADDRESS: <DD>This is the actual email address itself. This must be
11819 a valid Internet address that conforms to the Internet message
11820 header standard, RFC-822. (See also <A HREF="h_address_format">Explanation of Address formats</A>.)</DL>
11822 The two fields that aren't usually visible are:<DL>
11824 <P><DT>FCC: <DD>The name of the folder you would like a copy of any outgoing
11825 message to this address to be saved in. If this field is set, and
11826 this address is the first one in the message's To: header, then
11827 Alpine will use this folder name for the FCC in lieu of the normal
11828 FCC folder name.
11830 <P><DT>COMMENTS: <DD>This field contains arbitrary text for your convenience.
11831 </DL>
11832 <P>
11833 Due to screen width limitations, these last two fields do not show up in
11834 the normal ADDRESS BOOK display. You may select the
11835 "View/Update" command to
11836 view or modify them. You may use the configuration variable
11837 <A HREF="h_config_abook_formats">"<!--#echo var="VAR_addressbook-formats"-->"</A>
11838 to add these fields to your ADDRESS BOOK
11839 display, or to modify the format of the display.
11841 <H2>Sorting the Address book</H2>
11843 By default, address book entries are sorted alphabetically on the full
11844 name with distribution lists sorted to the end. Sorting can be changed by
11845 resetting the address book sort rule in the Alpine SETUP CONFIGURATION screen
11846 --assuming you have "write" permission for the address book file.
11847 <P>
11848 Unlike the sorting of folders (which only changes presentation), sorting an
11849 address book actually changes the file as it is kept on the computer. For
11850 this reason you won't be able to sort a shared or system-wide address
11851 book.
11853 <H2>Adding New Entries</H2>
11855 The easiest way to add new entries to your address book is to use the
11856 "TakeAddr" command when viewing a message.
11857 This command allows you to take addresses from the header and body of the
11858 message and put them into your address book, without having to type
11859 them in.
11860 <P>
11862 To manually add a new entry from within the address book screen, use the AddNew
11863 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->"@"<!--chtml endif-->) command.
11864 Use this command both for adding a simple alias and for adding a
11865 distribution list.
11867 <H2>Distribution Lists</H2>
11869 Address book entries can be simple cases of aliases (a single nickname is linked
11870 to a single email address) or distribution lists (a single nickname
11871 pointing at more than one email address). Each distribution list has a
11872 nickname, a full name and a list of addresses. The addresses may be
11873 actual addresses or they may be other nicknames in your address book.
11874 They may even refer to other distribution lists.
11875 There's really no difference between a simple alias and a distribution list,
11876 other than the number of addresses.
11877 Therefore, you can turn a simple alias with one address into a distribution
11878 list simply by adding more addresses.
11879 To add entries to an existing list or alias
11880 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
11881 a single address from the list if the cursor is placed on the address;
11882 it will delete the entire distribution list if the cursor is on the
11883 nickname/fullname line. View/Update may also be used to delete addresses
11884 from a list.
11885 <P>
11886 Address field entries in distribution lists may take any one of three
11887 forms: a nickname existing in any of the defined address books, a normal
11888 address of the form "jsmith@art.example.com", or a complete
11889 fullname/address combination, e.g. "John Smith
11890 <jsmith@art.example.com>".
11891 <P>
11892 Distribution lists in Alpine address books can only be used by the person or
11893 people who have access to that address book. They are not usually used to
11894 implement discussion groups, but can be used to facilitate small
11895 discussion groups if all the participants have access to the same shared
11896 address book.
11898 <H2>FCC and Comments</H2>
11900 As mentioned above, each entry in the address book also has two other optional
11901 fields, Fcc and Comments. The command to look at or change either of these
11902 is the same View/Update command used for all of the fields (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->">"<!--chtml endif-->). The
11903 Comments field is just for your own use. The Fcc field overrides the
11904 default Fcc if this address is the first one on the To line. The WhereIs
11905 command may be used to search for particular strings in the address book,
11906 including fields that are not visible (like Comment and Fcc by default).
11908 <H2>Aggregate Operations</H2>
11910 If the feature
11911 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
11912 is turned on (the default), then the four commands "Select",
11913 "Select Current", "Zoom", and "Apply"
11914 are available. The two selection commands allow you to mark a set of
11915 address book entries as being selected. If you have more than one address
11916 book, the selections may be in more than one of those address books.
11917 The "Zoom" command will toggle between displaying only the selected
11918 entries and all of the entries. The "Apply" command allows you to
11919 apply one of the regular address book commands to all of the selected
11920 entries. Usually the address book commands apply to only the entry
11921 highlighted by the cursor. The "Apply" command works with the
11922 commands "ComposeTo", "Delete", "Print",
11923 "Save", "Forward", and "Role".
11925 <H2>Exporting and Forwarding Address book entries</H2>
11927 Under the save option, when you use the Export (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->"X"<!--chtml endif-->) command, the currently highlighted
11928 address book entry is placed in a plain text file in your home directory
11929 <!--chtml if pinemode="running"-->
11930 (which, in the present configuration of your system, is
11931 "<!--#echo var="HOME_DIR"-->")
11932 <!--chtml endif-->
11933 or current working directory
11934 <!--chtml if pinemode="running"-->
11935 (which, at least for your current Alpine "session,"
11936 is "<!--#echo var="CURRENT_DIR"-->")
11937 <!--chtml endif-->, depending on the
11938 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
11939 configuration setting. If you have some entries selected and use the
11940 Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Export command, all of the selected addresses will be
11941 placed in the text file.
11942 <P>
11943 When you use the Forward (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->"F"<!--chtml endif-->) command, the currently highlighted
11944 address book entry is placed in a special attachment and you are put into
11945 the composer. You can fill in some comments in the body of the message,
11946 if you'd like, and send it to somebody else who uses Alpine. The recipient
11947 may use the TakeAddr command on that message to insert the address book
11948 entry you sent in their own address book. If you have some entries
11949 selected and use the Apply Forward command all of the selected entries
11950 will be forwarded in a single message. You may
11951 use Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Forward to forward a copy of an entire address book.
11952 The recipient must be using Alpine in order to receive this correctly.
11953 One way for the recipient to handle this might be to create an empty
11954 address book and then "Take" your forwarded address book entries into
11955 that empty address book.
11957 <H2>Multiple and/or Site-Wide Address books</H2>
11959 You may have more than one personal address book. In addition, there may
11960 be one or more global address books. This capability allows you to have
11961 multiple personal address books (some of which may be shared) and it also
11962 allows system administrators to implement site-wide address books that
11963 contain entries for users on multiple machines within the organization.
11964 <P><DL>
11965 <DT>Searching
11966 <DD> If you enter a nickname when composing a message, your
11967 personal address books will be searched through in order, and then the
11968 global address book(s) searched. If more than one address book has an entry
11969 for the nickname, Alpine uses the first one that it finds, so an entry in
11970 your personal address book would override a global address book entry. If
11971 after searching all the address books there is still no match, (Unix) Alpine
11972 then searches the local host password file on the assumption that you have
11973 entered a local user name rather than an address book nickname.
11974 You may change the search order of your address books with the <!--chtml if pinemode="function_key"-->F3<!--chtml else-->$<!--chtml endif--> Shuffle
11975 command, but global address books are always searched after personal
11976 address books.
11978 <P><DT>Tab completion
11979 <DD> If the
11980 <A HREF="h_config_enable_tab_complete"><!--#echo var="FEAT_enable-tab-completion"--></A>
11981 feature is turned on (the default) then the Tab key may be used
11982 in the composer to complete partially typed nicknames in the To
11983 or Cc lines. You type the first few letters of a nickname and then
11984 press the Tab key. It there is only one nickname that matches it will
11985 be filled in by Alpine. If there is more than one the unambiguous part
11986 of the nicknames will be filled in. For example, if your address book or
11987 books contains only the two entries "barley" and "barbecue"
11988 beginning with the letters "ba", then if you type "ba"
11989 followed by a Tab character Alpine will fill in "bar" and stop.
11990 If you then type a second Tab character you will be presented with a list
11991 of matching nicknames to select from. Alternatively, you could type another
11992 "b" resulting in "barb" and then a Tab would fill
11993 in the entire "barbecue" entry.
11995 <P><DT>Defining
11996 <DD> You define multiple personal address books in the
11997 <A HREF="h_abook_config">SETUP AddressBooks</A> screen, which you may reach
11998 from the MAIN MENU.
11999 You may add as many as you like. Global address books are usually
12000 site-wide address books defined by the System administrator, but
12001 you may define global address books of your own just like you define
12002 personal address books.
12004 <P><DT>Creating and updating
12005 <DD> Personal address books are normally created empty
12006 and populated by explicit additions from within Alpine, e.g. via the
12007 TakeAddr command. Unlike personal address books, global address books may
12008 not be modified/updated from within Alpine; that is, they are Read-Only.
12009 Thus, global address books are created, populated and updated outside of
12010 Alpine. They might be hand-edited, generated by a program from another
12011 database, or by copying an existing address book. They might also be
12012 some other user's personal address book, and so be modified normally by
12013 that user but accessed Read-Only by you. See the Alpine Technical
12014 Notes document (included in the Alpine distribution) for more information on
12015 this.
12017 <P><DT>Accessing
12018 <DD>There are two different types of address books in Alpine.
12019 A local address book is stored in a regular file and the normal file
12020 access permissions apply. A remote address book is stored on an IMAP
12021 server in a special folder that contains only messages pertaining to
12022 that address book. The last message in the remote folder contains a
12023 copy of the address book data, and that data is copied to a local cache
12024 file in your home directory. From there it is accessed just like a local
12025 address book. The name of the cache file is kept track of in a special
12026 file called the
12027 <A HREF="h_config_abook_metafile"><!--#echo var="VAR_remote-abook-metafile"--></A>,
12028 the name of which is stored in
12029 your Alpine configuration file the first time you use a remote address book.
12030 Just as local Alpine address books use a format that only Alpine understands,
12031 remote Alpine address books do the same and other mail reading programs
12032 are unlikely to be able to understand them.<P>
12033 While global address books are explicitly intended to be shared, there is
12034 nothing to prevent you from sharing a personal address book with other
12035 Alpine users. This might be useful in the case of a small workgroup.
12036 However, it is recommended that updates to shared personal address books
12037 be done when other Alpine users are not accessing the address book. Alpine
12038 does not do any file-locking to manage concurrent updates to the
12039 addressbook, but it does check to see if the file has been modified before
12040 making any changes. Consequently, inadvertent concurrent updates will
12041 only cause other Alpine users to have to restart their address book
12042 operation, which will cause Alpine to reopen the updated file.
12044 <P><DT>Converting to Remote
12045 <DD>The easiest way to convert an existing local
12046 address book into a remote address book is to create an empty new remote
12047 personal address book by typing "A" to execute the
12048 "Add Pers Abook" command in the SETUP Addressbook screen.
12049 Make sure you add a <EM>personal</EM> address book, not a <EM>global</EM>
12050 address book.
12051 After you have added the empty
12052 remote address book, go into the screen for the address book you wish
12053 to copy and "Select" "All".
12054 This selects every entry in that
12055 address book. Then type the command "Apply Save".
12056 You will be asked for the address book to save to. You may use ^P and ^N
12057 to get to the new empty address book, then hit RETURN and the addresses
12058 will be copied.
12059 At this point you'll probably want to unselect all the entries in the local
12060 address book before proceeding. You do that with
12061 "Select" "unselect All".
12063 </DL>
12064 <UL>
12065 <LI><A HREF="h_address_format">Explanation of Address formats</A>
12066 </UL>
12067 <P><UL>
12068 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
12069 </UL>
12070 <P>
12071 <End of help on this topic>
12072 </BODY>
12073 </HTML>
12074 ===== h_abook_select_addr =====
12075 <HTML>
12076 <HEAD>
12077 <TITLE>Addressbook Selection Explained</TITLE>
12078 </HEAD>
12079 <BODY>
12080 <H1>SELECT ADDRESS</H1>
12081 <!--chtml if pinemode="function_key"-->
12082 <PRE>
12083 Navigating the List of Messages General Alpine Commands
12084 ------------------------------- -----------------------
12085 F5 Move to previous entry F1 Show this help text
12086 F6 Move to next entry
12087 F7 Show previous screen of address book
12088 F8 Show next screen of address book
12089 F12 WhereIs (search through address book)
12091 Address Selection Commands
12092 --------------------------
12093 F3 Exit the Address Select screen (without selecting an address)
12094 F4 Select the currently highlighted entry
12095 </PRE>
12096 <!--chtml else-->
12097 <PRE>
12098 Navigating the List of Messages General Alpine Commands
12099 ------------------------------- -----------------------
12100 P Move to previous entry ? Show this help text
12101 N Move to next entry
12102 - Show previous screen of address book
12103 Spc (space bar) Show next screen of address book
12104 W WhereIs (search through address book)
12106 Address Selection Commands
12107 --------------------------
12108 E Exit the Address Select screen (without selecting an address)
12109 S Select the currently highlighted entry
12110 </PRE>
12111 <!--chtml endif-->
12112 <P>
12114 This screen is designed to let you easily scan your address book(s) in
12115 order to select an entry for the message you are composing. You cannot
12116 edit your address book in any way at this time, for address book
12117 maintenance, select the address book command when not composing a message.
12118 <P>
12120 If you are composing a message and know the nickname of the person/list you
12121 want, you can bypass this screen by simply typing in the nickname on the
12122 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12123 selecting an entry does not cancel your message.
12124 <P>
12126 FOR MORE INFORMATION on addressing see
12127 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12128 <A HREF="h_abook_opened">Address Book Screen's</A>
12129 help text.
12130 <P>
12131 <End of help on this topic>
12132 </BODY>
12133 </HTML>
12134 ===== h_abook_select_top =====
12135 <HTML>
12136 <HEAD>
12137 <TITLE>Addressbook Selection Navigation Explained</TITLE>
12138 </HEAD>
12139 <BODY>
12140 <H1>NAVIGATING WHILE SELECTING ADDRESSES</H1>
12141 <!--chtml if pinemode="function_key"-->
12142 <PRE>
12143 Navigating the List of Address Books General Alpine Commands
12144 ------------------------------------ -----------------------
12145 F4 View the highlighted address book
12146 F5 Move to previous address book F1 Show this help text
12147 F6 Move to next address book
12148 F7 Show previous screen of address books
12149 F8 Show next screen of address books
12150 F12 WhereIs (search through address books)
12152 Address Selection Commands
12153 --------------------------
12154 F3 Exit the Address Select screen (without selecting an address)
12155 F4 Select the currently selected entries (if using ListMode)
12156 F9 Change to ListMode
12157 </PRE>
12158 <!--chtml else-->
12159 <PRE>
12160 Navigating the List of Address Books General Alpine Commands
12161 ------------------------------------ -----------------------
12162 > View the highlighted address book
12163 P Move to previous address book ? Show this help text
12164 N Move to next address book
12165 - Show previous screen of address books
12166 Spc (space bar) Show next screen of address books
12167 W WhereIs (search through address books)
12169 Address Selection Commands
12170 --------------------------
12171 E Exit the Address Select screen (without selecting an address)
12172 S Select the currently selected entries (if using ListMode)
12173 L Change to ListMode
12174 </PRE>
12175 <!--chtml endif-->
12176 <P>
12178 This screen is designed to let you easily scan your address book(s) in
12179 order to select entries for the message you are composing. You cannot
12180 edit your address book in any way at this time. For address book
12181 maintenance, select the address book command when not composing a message.
12182 <P>
12184 If you are composing a message and know the nickname of the person/list you
12185 want, you can bypass this screen by simply typing in the nickname on the
12186 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12187 selecting an entry does not cancel your message.
12188 <P>
12190 The ListMode command will add a column at the left edge of the screen.
12191 You mark the entries that you wish to select with the "X" command.
12192 This allows you to choose more than one entry at a time.
12193 <P>
12195 An alternative method of composing a message to entries in your
12196 address book(s) is to first use the "Select" command from
12197 the address book maintenance screen and then the "Apply"
12198 "ComposeTo" command to start the composer composing to the
12199 selected entries.
12200 <P>
12202 FOR MORE INFORMATION on addressing see
12203 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12204 <A HREF="h_abook_opened">Address Book Screen's</A>
12205 help text.
12206 <P>
12207 <End of help on this topic>
12208 </BODY>
12209 </HTML>
12210 ===== h_abook_select_listmode =====
12211 <HTML>
12212 <HEAD>
12213 <TITLE>Address Listmode Selection from Composer Explained</TITLE>
12214 </HEAD>
12215 <BODY>
12216 <H1>COMPOSER: SELECT ADDRESSES</H1>
12217 <!--chtml if pinemode="function_key"-->
12218 <PRE>
12219 Navigating the List of Messages General Alpine Commands
12220 ------------------------------- -----------------------
12221 F5 Move to previous entry F1 Show this help text
12222 F6 Move to next entry
12223 F7 Show previous screen of address book
12224 F8 Show next screen of address book
12225 F12 WhereIs (search through address book)
12227 Address Selection Commands
12228 --------------------------
12229 F3 Exit the Address Select screen (without selecting an address)
12230 F4 Select the currently highlighted entry
12231 F9 Change to ListMode
12232 </PRE>
12233 <!--chtml else-->
12234 <PRE>
12235 Navigating the List of Messages General Alpine Commands
12236 ------------------------------- -----------------------
12237 P Move to previous entry ? Show this help text
12238 N Move to next entry
12239 - Show previous screen of address book
12240 Spc (space bar) Show next screen of address book
12241 W WhereIs (search through address book)
12243 Address Selection Commands
12244 --------------------------
12245 E Exit the Address Select screen (without selecting an address)
12246 S Select the currently highlighted entry
12247 L Change to ListMode
12248 </PRE>
12249 <!--chtml endif-->
12250 <P>
12252 This screen is designed to let you easily scan your address book(s) in
12253 order to select entries for the message you are composing. You cannot
12254 edit your address book in any way at this time, for address book
12255 maintenance, select the address book command when not composing a message.
12256 <P>
12258 If you are composing a message and know the nickname of the person/list you
12259 want, you can bypass this screen by simply typing in the nickname on the
12260 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12261 selecting an entry does not cancel your message.
12262 <P>
12264 The ListMode command will add a column at the left edge of the screen.
12265 You mark the entries that you wish to select with the "X" command.
12266 This allows you to choose more than one entry at a time.
12267 <P>
12269 An alternative method of composing a message to entries in your
12270 address book(s) is to first use the "Select" command from
12271 the address book maintenance screen and then the "Apply"
12272 "ComposeTo" command to start the composer composing to the
12273 selected entries.
12274 <P>
12276 FOR MORE INFORMATION on addressing see
12277 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12278 <A HREF="h_abook_opened">Address Book Screen's</A>
12279 help text.
12280 <P>
12281 <End of help on this topic>
12282 </BODY>
12283 </HTML>
12284 ===== h_abook_select_checks =====
12285 <HTML>
12286 <HEAD>
12287 <TITLE>Address Selection from Composer Explained</TITLE>
12288 </HEAD>
12289 <BODY>
12290 <H1>COMPOSER: SELECT ADDRESSES</H1>
12291 <!--chtml if pinemode="function_key"-->
12292 <PRE>
12293 Navigating the List of Messages General Alpine Commands
12294 ------------------------------- -----------------------
12295 F5 Move to previous entry F1 Show this help text
12296 F6 Move to next entry
12297 F7 Show previous screen of address book
12298 F8 Show next screen of address book
12299 F12 WhereIs (search through address book)
12301 Address Selection Commands
12302 --------------------------
12303 F3 Exit the Address Select screen (without selecting an address)
12304 F4 Select the currently highlighted entry
12305 F8 Either Sets or Unsets all entries in this address book
12306 F9 Set or Unset the highlighted entry
12307 </PRE>
12308 <!--chtml else-->
12309 <PRE>
12310 Navigating the List of Messages General Alpine Commands
12311 ------------------------------- -----------------------
12312 P Move to previous entry ? Show this help text
12313 N Move to next entry
12314 - Show previous screen of address book
12315 Spc (space bar) Show next screen of address book
12316 W WhereIs (search through address book)
12318 Address Selection Commands
12319 --------------------------
12320 E Exit the Address Select screen (without selecting an address)
12321 S Select the currently highlighted entry
12322 X Set or Unset the highlighted entry
12323 A Either Sets or Unsets all entries in this address book
12324 </PRE>
12325 <!--chtml endif-->
12326 <P>
12328 Mark the entries you wish to select with the "X Set/Unset"
12329 command. Type "S Select" to select all of the entries you
12330 have marked, just as if you had typed them in by hand.
12331 <P>
12333 An alternative method of composing a message to entries in your
12334 address book(s) is to first use the "Select" command from
12335 the address book maintenance screen and then the "Apply"
12336 "ComposeTo" command to start the composer composing to the
12337 selected entries.
12338 <P>
12340 FOR MORE INFORMATION on addressing see
12341 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12342 <A HREF="h_abook_opened">Address Book Screen's</A>
12343 help text.
12344 <P>
12345 <End of help on this topic>
12346 </BODY>
12347 </HTML>
12348 ===== h_abook_select_nicks_take =====
12349 <HTML>
12350 <HEAD>
12351 <TITLE>Take Address Nickname Selection Explained</TITLE>
12352 </HEAD>
12353 <BODY>
12354 <H1>TAKEADDR: SELECT NICKNAME</H1>
12355 <!--chtml if pinemode="function_key"-->
12356 <PRE>
12357 Navigating the List of Messages General Alpine Commands
12358 ------------------------------- -----------------------
12359 F5 Move to previous entry F1 Show this help text
12360 F6 Move to next entry
12361 F7 Show previous screen of address book
12362 F8 Show next screen of address book
12363 F12 WhereIs (search through address book)
12365 Message Selection Commands
12366 --------------------------
12367 F3 Exit the Nickname Select screen (without selecting an address)
12368 F4 Select the currently highlighted entry
12369 </PRE>
12370 <!--chtml else-->
12371 <PRE>
12372 Navigating the List of Messages General Alpine Commands
12373 ------------------------------- -----------------------
12374 P Move to previous entry ? Show this help text
12375 N Move to next entry
12376 - Show previous screen of address book
12377 Spc (space bar) Show next screen of address book
12378 W WhereIs (search through address book)
12380 Message Selection Commands
12381 --------------------------
12382 E Exit the Nickname Select screen (without selecting an address)
12383 S Select the currently highlighted entry
12384 </PRE>
12385 <!--chtml endif-->
12386 <P>
12388 This screen is designed to let you modify or add to an existing
12389 address book entry. You have already selected the name(s) and
12390 address(es) through "Take Address". This screen simply lets
12391 you scan your address books and select the nickname to be
12392 changed/augmented. If you want to add a new entry, then you are in
12393 the wrong place-- Select "Exit" command.
12394 <P>
12396 FOR MORE INFORMATION on addressing see
12397 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12398 <A HREF="h_abook_opened">Address Book Screen's</A>
12399 help text.
12400 <P>
12401 <End of help on this topic>
12402 </BODY>
12403 </HTML>
12404 ===== h_abook_select_nick =====
12405 <HTML>
12406 <HEAD>
12407 <TITLE>Nickname Selection Explained</TITLE>
12408 </HEAD>
12409 <BODY>
12410 <H1>SELECT NICKNAME</H1>
12411 <!--chtml if pinemode="function_key"-->
12412 <PRE>
12413 Navigating the List of Messages General Alpine Commands
12414 ------------------------------- -----------------------
12415 F5 Move to previous entry F1 Show this help text
12416 F6 Move to next entry
12417 F7 Show previous screen of address book
12418 F8 Show next screen of address book
12419 F12 WhereIs (search through address book)
12421 Message Selection Commands
12422 --------------------------
12423 F3 Exit the Nickname Select screen (without selecting an address)
12424 F4 Select the currently highlighted entry
12425 </PRE>
12426 <!--chtml else-->
12427 <PRE>
12428 Navigating the List of Messages General Alpine Commands
12429 ------------------------------- -----------------------
12430 P Move to previous entry ? Show this help text
12431 N Move to next entry
12432 - Show previous screen of address book
12433 Spc (space bar) Show next screen of address book
12434 W WhereIs (search through address book)
12436 Message Selection Commands
12437 --------------------------
12438 E Exit the Nickname Select screen (without selecting an address)
12439 S Select the currently highlighted entry
12440 </PRE>
12441 <!--chtml endif-->
12442 <P>
12444 This screen is designed to let you look at the nicknames in your address
12445 books before choosing a new one.
12446 <P>
12448 FOR MORE INFORMATION on addressing see
12449 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12450 <A HREF="h_abook_opened">Address Book Screen's</A>
12451 help text.
12452 <P>
12453 <End of help on this topic>
12454 </BODY>
12455 </HTML>
12456 ===== h_takeaddr_screen =====
12457 <HTML>
12458 <HEAD>
12459 <TITLE>Take Address Screen Explained</TITLE>
12460 </HEAD>
12461 <BODY>
12462 <H1>TAKE ADDRESS COMMANDS</H1>
12463 <!--chtml if pinemode="function_key"-->
12464 <PRE>
12465 Navigating the List of Addresses Address Selection Commands
12466 -------------------------------- --------------------------
12467 F5 Move to previous entry F3 Exit without taking address
12468 F6 Move to next entry F4 Take current address(es)
12469 F7 Show previous page of address list
12470 F8 Show next page of address list
12471 F2 WhereIs (search list)
12472 --------------
12473 Mode Toggle F9 Set/Unset current address
12474 ----------- F10 Set all
12475 F12 Toggle between List and single mode F11 Unset all
12476 </PRE>
12477 <!--chtml else-->
12478 <PRE>
12479 Navigating the List of Addresses Address Selection Commands
12480 -------------------------------- --------------------------
12481 P Move to previous entry < Exit without taking address
12482 N Move to next entry T Take address
12483 - Show previous page of address list
12484 Spc (space bar) Show next page of address list
12485 W WhereIs (search list) List Mode
12486 ---------
12487 Single Mode X Set/Unset current address
12488 ----------- A Set all addresses
12489 L Switch to list mode U Unset all addresses
12490 S Switch to single mode
12491 </PRE>
12492 <!--chtml endif-->
12494 <H2>Description of the Take Address Screen</H2>
12496 This screen is designed to let you select one or more address/name
12497 combinations from the current message and put them into your address book.
12498 The cursor is initially placed on the line with the message author.
12499 Other lines include the names of people and/or mailing lists who also
12500 received the message. Other people "involved" in the
12501 message (e.g. the person named as Reply-To:) are also listed here.
12502 <P>
12504 The simple case is adding a new, single entry into your address book. To
12505 do this, simply highlight the correct line and press
12506 <!--chtml if pinemode="function_key"-->
12507 F4.
12508 <!--chtml else-->
12509 "T".
12510 <!--chtml endif-->
12511 To create a new list or add to an existing list, switch the screen display
12512 into List Mode by pressing
12513 <!--chtml if pinemode="function_key"-->
12514 F12.
12515 <!--chtml else-->
12516 "L".
12517 <!--chtml endif-->
12518 In List Mode, you select the
12519 group of addresses you wish to manipulate by marking them with an
12520 "X".
12521 The Set/Unset
12522 <!--chtml if pinemode="function_key"-->
12523 (F9)
12524 <!--chtml else-->
12525 ("X")
12526 <!--chtml endif-->
12527 command will turn the "X" on for the
12528 highlighted address if it was off or turn it off if it was previously on.
12529 The SetAll command will select all of the addresses, and the UnSetAll
12530 command will turn off all the selections. Once you've gotten the
12531 selection the way you want it, you may create a new list by pressing
12532 <!--chtml if pinemode="function_key"-->
12533 F4.
12534 <!--chtml else-->
12535 "T".
12536 <!--chtml endif-->
12537 <P>
12539 In both the simple and list cases, after choosing to take the address,
12540 you will be asked for the nickname of the entry. Typing in a new name
12541 creates the new entry/list. Entering an existing nickname will replace
12542 the entry (simple case) or add to the list (list case). Alternatively,
12543 you can press Ctrl-T at the nickname prompt and select an existing
12544 nickname from your address book.
12545 <P>
12547 You will normally start in Single Mode, unless you used the Apply command
12548 to startup the TakeAddr screen, in which case you will start in List Mode.
12549 You may switch between the two modes at any time. If you've already
12550 selected several addresses in List Mode, those will be remembered when you
12551 switch to Single Mode and then back to List Mode. The set of addresses
12552 that are pre-selected when you start in List Mode are the From addresses
12553 of all of the messages you are operating on. You may, of course, easily
12554 erase those selections with the UnSetAll command.
12555 <P>
12557 If you have more than one writable address book, you will be prompted for
12558 the name of the address book you wish to add the new entry to before
12559 anything else. You can use ^N and ^P to choose among the defined address
12560 books, or type in the address book name.
12561 <P>
12563 FOR MORE INFORMATION on addressing see
12564 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12565 <A HREF="h_abook_opened">Address Book Screen's</A>
12566 help text.
12567 <P>
12568 <End of help on this topic>
12569 </BODY>
12570 </HTML>
12571 ===== h_takeexport_screen =====
12572 <HTML>
12573 <HEAD>
12574 <TITLE>Take Export Screen Explained</TITLE>
12575 </HEAD>
12576 <BODY>
12577 <H1>TAKE EXPORT COMMANDS</H1>
12578 <!--chtml if pinemode="function_key"-->
12579 <PRE>
12580 Navigating the List of Addresses Address Selection Commands
12581 -------------------------------- --------------------------
12582 F5 Move to previous entry F3 Exit without taking address
12583 F6 Move to next entry F4 Take current address(es)
12584 F7 Show previous page of address list
12585 F8 Show next page of address list
12586 F2 WhereIs (search list)
12587 --------------
12588 Mode Toggle F9 Set/Unset current address
12589 ----------- F10 Set all
12590 F12 Toggle between List and single mode F11 Unset all
12591 </PRE>
12592 <!--chtml else-->
12593 <PRE>
12594 Navigating the List of Addresses Address Selection Commands
12595 -------------------------------- --------------------------
12596 P Move to previous entry < Exit without taking address
12597 N Move to next entry T Take address
12598 - Show previous page of address list
12599 Spc (space bar) Show next page of address list
12600 W WhereIs (search list) List Mode
12601 ---------
12602 Single Mode X Set/Unset current address
12603 ----------- A Set all addresses
12604 L Switch to list mode U Unset all addresses
12605 S Switch to single mode
12606 </PRE>
12607 <!--chtml endif-->
12609 <H2>Description of the Take Export Screen</H2>
12611 This screen is designed to let you select one or more addresses
12612 from the current message and put them into a file.
12613 Only the user@domain_name part of each address is put into the file.
12614 <P>
12616 To put a single entry into a file simply highlight the correct line and press
12617 <!--chtml if pinemode="function_key"-->
12618 F4.
12619 <!--chtml else-->
12620 "T".
12621 <!--chtml endif-->
12622 To put more than one entry into a file
12623 switch the screen display
12624 into List Mode by pressing
12625 <!--chtml if pinemode="function_key"-->
12626 F12.
12627 <!--chtml else-->
12628 "L".
12629 <!--chtml endif-->
12630 In List Mode, you select the
12631 group of addresses you wish to manipulate by marking them with an
12632 "X".
12633 The Set/Unset
12634 <!--chtml if pinemode="function_key"-->
12635 (F9)
12636 <!--chtml else-->
12637 ("X")
12638 <!--chtml endif-->
12639 command will turn the "X" on for the
12640 highlighted address if it was off or turn it off if it was previously on.
12641 The SetAll command will select all of the addresses, and the UnSetAll
12642 command will turn off all the selections. Once you've gotten the
12643 selection the way you want it, you may put the addresses in a file by typing
12644 <!--chtml if pinemode="function_key"-->
12645 F4.
12646 <!--chtml else-->
12647 "T".
12648 <!--chtml endif-->
12649 <P>
12651 You will be asked for the name of a file to put the addresses in.
12652 If the file already exists, you will be asked whether you want to Overwrite
12653 (replace) the contents of the file or Append to the contents of the file.
12654 <P>
12656 <End of help on this topic>
12657 </BODY>
12658 </HTML>
12659 ============= h_abook_view ========================
12660 <HTML>
12661 <HEAD>
12662 <TITLE>Address Book View Explained</TITLE>
12663 </HEAD>
12664 <BODY>
12665 This function allows you to view the contents of an address book entry. You
12666 can only view one entry at a time.
12667 <P>
12668 <DL>
12669 <DT>Help
12670 <!--chtml if pinemode="function_key"-->
12671 (F1)
12672 <!--chtml else-->
12673 (?)
12674 <!--chtml endif-->
12675 </DT>
12676 <DD>
12677 Display this help text.
12679 <DT>Abook
12680 <!--chtml if pinemode="function_key"-->
12681 (F3)
12682 <!--chtml else-->
12683 (<)
12684 <!--chtml endif-->
12685 </DT>
12686 <DD>
12687 Go back to index of address book entries.
12689 <DT>Update
12690 <!--chtml if pinemode="function_key"-->
12691 (F4)
12692 <!--chtml else-->
12693 (U)
12694 <!--chtml endif-->
12695 </DT>
12696 <DD>
12697 Update (modify) this entry.
12699 <DT>ComposeTo
12700 <!--chtml if pinemode="function_key"-->
12701 (F5)
12702 <!--chtml else-->
12703 (C)
12704 <!--chtml endif-->
12705 </DT>
12706 <DD>Compose a message to the address(es) in this entry.
12708 <DT>Role
12709 <!--chtml if pinemode="function_key"-->
12710 (F6)
12711 <!--chtml else-->
12712 (#)
12713 <!--chtml endif-->
12714 </DT>
12715 <DD>Compose a message to the address(es) in this entry using roles.
12717 <DT>Prev Page
12718 <!--chtml if pinemode="function_key"-->
12719 (F7)
12720 <!--chtml else-->
12721 (-)
12722 <!--chtml endif-->
12723 </DT>
12724 <DD>
12725 Show the previous page of the current entry.
12727 <DT>Next Page
12728 <!--chtml if pinemode="function_key"-->
12729 (F8)
12730 <!--chtml else-->
12731 (Space)
12732 <!--chtml endif-->
12733 </DT>
12734 <DD>
12735 Show the next page of the current entry.
12737 <DT>Print
12738 <!--chtml if pinemode="function_key"-->
12739 (F9)
12740 <!--chtml else-->
12741 (%)
12742 <!--chtml endif-->
12743 </DT>
12744 <DD>Print the current entry. You can select the
12745 printer or the print command via the "Setup" command
12746 on the MAIN MENU.
12748 <DT>WhereIs
12749 <!--chtml if pinemode="function_key"-->
12750 (F10)
12751 <!--chtml else-->
12752 (W)
12753 <!--chtml endif-->
12754 </DT>
12755 <DD>Search the entry for a string of letters. If it is
12756 found, move to it. The string can be one word or a phrase.
12757 If there are multiple occurrences, the cursor moves to the
12758 first occurrence beyond the current cursor position.
12760 <DT>Fwd Email
12761 <!--chtml if pinemode="function_key"-->
12762 (F11)
12763 <!--chtml else-->
12764 (F)
12765 <!--chtml endif-->
12766 </DT>
12767 <DD>Begin composition of a new mail message with the displayed
12768 text already inserted in the message body.
12770 </DL>
12771 <P>
12772 <End of help on this topic>
12773 </BODY>
12774 </HTML>
12775 ============= h_ldap_view ========================
12776 <HTML>
12777 <HEAD>
12778 <TITLE>LDAP Response View Explained</TITLE>
12779 </HEAD>
12780 <BODY>
12781 This function allows you to view the contents of a directory entry. You
12782 can only view one entry at a time.
12783 <P>
12784 <DL>
12785 <DT>Help
12786 <!--chtml if pinemode="function_key"-->
12787 (F1)
12788 <!--chtml else-->
12789 (?)
12790 <!--chtml endif-->
12791 </DT>
12792 <DD>
12793 Display this help text.
12795 <DT>Results Index
12796 <!--chtml if pinemode="function_key"-->
12797 (F3)
12798 <!--chtml else-->
12799 (<)
12800 <!--chtml endif-->
12801 </DT>
12802 <DD>Go back to index of search results.
12804 <DT>ComposeTo
12805 <!--chtml if pinemode="function_key"-->
12806 (F5)
12807 <!--chtml else-->
12808 (C)
12809 <!--chtml endif-->
12810 </DT>
12811 <DD>Compose a message to the address(es) in this entry.
12813 <DT>Role
12814 <!--chtml if pinemode="function_key"-->
12815 (F6)
12816 <!--chtml else-->
12817 (#)
12818 <!--chtml endif-->
12819 </DT>
12820 <DD>Compose a message to the address(es) in this entry using roles.
12822 <DT>Prev Page
12823 <!--chtml if pinemode="function_key"-->
12824 (F7)
12825 <!--chtml else-->
12826 (-)
12827 <!--chtml endif-->
12828 </DT>
12829 <DD>
12830 Show the previous page of the current entry.
12832 <DT>Next Page
12833 <!--chtml if pinemode="function_key"-->
12834 (F8)
12835 <!--chtml else-->
12836 (Space)
12837 <!--chtml endif-->
12838 </DT>
12839 <DD>
12840 Show the next page of the current entry.
12842 <DT>Print
12843 <!--chtml if pinemode="function_key"-->
12844 (F9)
12845 <!--chtml else-->
12846 (%)
12847 <!--chtml endif-->
12848 </DT>
12849 <DD>Print the current entry on paper. You can select the
12850 printer or the print command via the "Setup" command
12851 on the MAIN MENU.
12853 <DT>WhereIs
12854 <!--chtml if pinemode="function_key"-->
12855 (F10)
12856 <!--chtml else-->
12857 (W)
12858 <!--chtml endif-->
12859 </DT>
12860 <DD>Search the entry for a string of letters. If it is
12861 found, move to it. The string can be one word or a phrase.
12862 If there are multiple occurrences, the cursor moves to the
12863 first occurrence beyond the current cursor position.
12865 <DT>Fwd Email
12866 <!--chtml if pinemode="function_key"-->
12867 (F11)
12868 <!--chtml else-->
12869 (F)
12870 <!--chtml endif-->
12871 </DT>
12872 <DD>Begin composition of a new mail message with the displayed
12873 text already inserted in the message body.
12875 <DT>Save
12876 <!--chtml if pinemode="function_key"-->
12877 (F12)
12878 <!--chtml else-->
12879 (S)
12880 <!--chtml endif-->
12881 </DT>
12882 <DD>Save the displayed entry to one of your address books or export
12883 it to a file.
12884 </DL>
12885 <P>
12886 <End of help on this topic>
12887 </BODY>
12888 </HTML>
12889 ===== h_attachment_screen =====
12890 <HTML>
12891 <HEAD>
12892 <TITLE>Attachment Index Screen Explained</TITLE>
12893 </HEAD>
12894 <BODY>
12895 The "ATTACHMENT INDEX" displays a list of the current
12896 message's attachments, and allows various operations on them. The
12897 first attachment is usually the message text, but does not include the
12898 header portion of the message.
12899 <P>
12900 Available commands include:
12901 <P>
12902 <DL>
12904 <DT>Help</DT>
12905 <DD>Show this help text.
12907 <DT>Msg #<I>num</I></DT>
12908 <DD>Leave this screen without displaying or saving any attachments.
12910 <DT>View</DT>
12911 <DD>View the currently selected attachment.
12913 <DT>Prev Attach</DT>
12914 <DD>Move to previous attachment.
12916 <DT>Next Attach</DT>
12917 <DD>Move to next attachment.
12919 <DT>Prev Page</DT>
12920 <DD>Previous page of the listed attachments.
12922 <DT>Next Page</DT>
12923 <DD>Next page of the listed attachments.
12925 <DT>Delete</DT>
12926 <DD>Mark the currently selected attachment for Deletion.
12927 This does not modify the current message by deleting the attachment from
12928 it, but instead the delete flag <EM>only</EM> has an effect when saving
12929 the message to a folder.
12930 Attachments marked for deletion are not copied to the destination folder
12931 along with the rest of the message when it is saved.
12932 It is ok for the destination folder to be the same as the current folder.
12933 In addition, the delete mark <EM>only</EM> applies to this Alpine session.
12935 <DT>Undelete</DT>
12936 <DD>Turn off the Delete flag for the selected attachment.
12938 <DT>Save</DT>
12939 <DD>Save the selected attachment to a file. If the attachment is of
12940 type "RFC822/Message", then the attachment will be saved to
12941 the specified mail folder.
12943 <DT>Export</DT>
12944 <DD>If the attachment is of
12945 type "RFC822/Message", then "Export" is used to
12946 copy the message to a file in the same way this command works on
12947 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
12949 <DT>Pipe</DT>
12950 <DD>Pipe the attachment contents into a UNIX command (if enabled).
12951 A description of the Pipe sub-commands is <A HREF="h_pipe_command">here</A>.
12953 <DT>WhereIs</DT>
12954 <DD>Find a matching string in the attachment list.
12956 <DT>AboutAttch</DT>
12957 <DD>Examine various aspects of the selected attachment.
12959 <DT>Print</DT>
12960 <DD>Print the selected attachment.
12962 <DT>Forward</DT>
12963 <DD>Forward the selected attachment as an attachment.
12964 </DL>
12966 <P>
12968 All attachments can be saved or piped into a UNIX command, but some may
12969 not be readily displayed by either Alpine or an external tool. In such
12970 cases, the reason why the message cannot be displayed is displayed on
12971 Alpine's message line.
12972 <P>
12973 <End of help on this topic>
12974 </BODY>
12975 </HTML>
12976 ============= h_mail_text_att_view ========================
12977 <HTML>
12978 <HEAD>
12979 <TITLE>Attachment View Screen Explained</TITLE>
12980 </HEAD>
12981 <BODY>
12982 This function allows you to view the contents of a text attachment. You
12983 can only view one attachment at a time.
12984 <P>
12985 Available commands include:
12986 <P>
12987 <DL>
12989 <DT>Help</DT>
12990 <DD>Display this help text
12992 <DT>AttchIndex</DT>
12993 <DD>Leave viewer and return to the "ATTACHMENT INDEX" screen
12995 <DT>Prev Page</DT>
12996 <DD>Show the previous page of the current attachment.
12998 <DT>Next Page</DT>
12999 <DD>Show the next page of the current attachment by pressing the space bar.
13001 <DT>Delete</DT>
13002 <DD>Mark the viewed attachment for Deletion. The delete
13003 flag <EM>only</EM> has affect when saving the message to a folder.
13004 Attachments marked for deletion are exluded from the messsage when
13005 it is saved. In addition, the delete mark <EM>only</EM> applies to
13006 this Alpine session.
13008 <DT>Undelete</DT>
13009 <DD>Turn off the Delete flag for the selected attachment.
13011 <DT>Save</DT>
13012 <DD>Copy the current attachment to a file. If you just enter
13013 a filename, the attachment will be saved with that name in
13014 your home directory
13015 <!--chtml if pinemode="running"-->
13016 (which, in the present configuration of your system, is
13017 "<!--#echo var="HOME_DIR"-->")
13018 <!--chtml endif-->
13019 or current working directory
13020 <!--chtml if pinemode="running"-->
13021 (which, at least for your current Alpine "session,"
13022 is "<!--#echo var="CURRENT_DIR"-->")
13023 <!--chtml endif-->, depending on the
13024 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13025 configuration setting. You may enter the full
13026 path and filename to save it in another directory instead.
13028 <DT>Export</DT>
13029 <DD>If the attachment is of
13030 type "RFC822/Message", then "Export" is used to
13031 copy the message to a file in the same way this command works on
13032 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
13033 (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
13034 defined, they may affect the contents of the exported file.)
13036 <DT>Pipe</DT>
13037 <DD>Pipe the attachment contents into a UNIX command (if enabled)
13039 <DT>WhereIs</DT>
13040 <DD>Search the attachment for a string of letters. If it is
13041 found, move to it. The string can be one word or a phrase.
13042 If there are multiple occurrences, the cursor moves to the
13043 first occurrence beyond the current cursor position.
13045 <DT>Print</DT>
13046 <DD>Print the current attachment on paper. You can select the
13047 printer or the print command via the "Setup" command
13048 on the MAIN MENU.
13050 <DT>Forward</DT>
13051 <DD>Forward the selected attachment as an attachment.
13052 </DL>
13053 <P>
13054 <End of help on this topic>
13055 </BODY>
13056 </HTML>
13057 ============= h_journal ==============
13058 <HTML>
13059 <HEAD>
13060 <TITLE>Recent Message Journal Explained</TITLE>
13061 </HEAD>
13062 <BODY>
13064 The following commands are available on this screen:
13065 <P>
13066 <DL>
13067 <DT>Help</DT>
13068 <DD>Show this help text
13070 <DT>Exit</DT>
13071 <DD>Exit Viewer, and go back to mail processing
13073 <DT>Prev Page</DT>
13074 <DD>Show the previous page text
13076 <DT>Next Page</DT>
13077 <DD>Show the next page of text by pressing the space bar
13079 <DT>Print</DT>
13080 <DD>Print the displayed text on paper. You can select the
13081 printer or the print command via the "Setup" command
13082 on the MAIN MENU.
13084 <DT>Fwd Email</DT>
13085 <DD>Begin composition of a new mail message with the displayed
13086 text already inserted in the message body.
13088 <DT>Save</DT>
13089 <DD>Copy the displayed text to a file. If you just enter
13090 a filename, the text will be saved with that name in
13091 your
13092 home directory
13093 <!--chtml if pinemode="running"-->
13094 (which, in the present configuration of your system, is
13095 "<!--#echo var="HOME_DIR"-->")
13096 <!--chtml endif-->
13097 or current working directory
13098 <!--chtml if pinemode="running"-->
13099 (which, at least for your current Alpine "session,"
13100 is "<!--#echo var="CURRENT_DIR"-->")
13101 <!--chtml endif-->, depending on the
13102 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13103 configuration setting. You may enter the full
13104 path and filename to save it in another directory instead.
13106 <DT>WhereIs</DT>
13107 <DD>Search the text for a string of letters. If it is
13108 found, move to it. The string can be one word or a phrase.
13109 If there are multiple occurrences, the cursor moves to the
13110 first occurrence beyond the current cursor position.
13111 </DL>
13112 <P>
13113 <End of help on this topic>
13114 </BODY>
13115 </HTML>
13116 ============= h_debugjournal ==============
13117 <HTML>
13118 <HEAD>
13119 <TITLE>Debug Journal Explained</TITLE>
13120 </HEAD>
13121 <BODY>
13123 The following commands are available on this screen:
13124 <P>
13125 <DL>
13126 <DT>Help</DT>
13127 <DD>Show this help text
13129 <DT>Exit</DT>
13130 <DD>Exit Viewer, and go back to mail processing
13132 <DT>Timestamps</DT>
13133 <DD>Turn on or off timestamps.
13135 <DT>DebugView</DT>
13136 <DD>Set the level of debugging you want to see. The level may be any number
13137 in the range 0-9. Higher numbers show more debugging detail. Note that the
13138 debugging information has already been captured. This setting just causes the
13139 debugging information that you see to be filtered. If you set this to
13140 the number "5" then you will be shown all of the debugging information
13141 at levels 5 and below.
13142 It's actually a bit more complicated than that. A fixed amount of memory
13143 is used to store the debug information.
13144 Since the amount of memory used is limited the debugging information
13145 has to be trimmed back when it gets too large.
13147 <DT>Prev Page</DT>
13148 <DD>Show the previous page text
13150 <DT>Next Page</DT>
13151 <DD>Show the next page of text by pressing the space bar
13153 <DT>Print</DT>
13154 <DD>Print the displayed text on paper. You can select the
13155 printer or the print command via the "Setup" command
13156 on the MAIN MENU.
13158 <DT>Fwd Email</DT>
13159 <DD>Begin composition of a new mail message with the displayed
13160 text already inserted in the message body.
13162 <DT>Save</DT>
13163 <DD>Copy the displayed text to a file. If you just enter
13164 a filename, the text will be saved with that name in
13165 your
13166 home directory
13167 <!--chtml if pinemode="running"-->
13168 (which, in the present configuration of your system, is
13169 "<!--#echo var="HOME_DIR"-->")
13170 <!--chtml endif-->
13171 or current working directory
13172 <!--chtml if pinemode="running"-->
13173 (which, at least for your current Alpine "session,"
13174 is "<!--#echo var="CURRENT_DIR"-->")
13175 <!--chtml endif-->, depending on the
13176 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13177 configuration setting. You may enter the full
13178 path and filename to save it in another directory instead.
13180 <DT>WhereIs</DT>
13181 <DD>Search the text for a string of letters. If it is
13182 found, move to it. The string can be one word or a phrase.
13183 If there are multiple occurrences, the cursor moves to the
13184 first occurrence beyond the current cursor position.
13185 </DL>
13186 <P>
13187 <End of help on this topic>
13188 </BODY>
13189 </HTML>
13190 ============= h_simple_text_view ==============
13191 <HTML>
13192 <HEAD>
13193 <TITLE>Simple Text View Screen Explained</TITLE>
13194 </HEAD>
13195 <BODY>
13197 The following commands are available on this screen:
13198 <P>
13199 <DL>
13200 <DT>Help</DT>
13201 <DD>Show this help text
13203 <DT>Exit</DT>
13204 <DD>Exit Viewer, and go back to mail processing
13206 <DT>Prev Page</DT>
13207 <DD>Show the previous page text
13209 <DT>Next Page</DT>
13210 <DD>Show the next page of text by pressing the space bar
13212 <DT>Print</DT>
13213 <DD>Print the displayed text on paper. You can select the
13214 printer or the print command via the "Setup" command
13215 on the MAIN MENU.
13217 <DT>Fwd Email</DT>
13218 <DD>Begin composition of a new mail message with the displayed
13219 text already inserted in the message body.
13221 <DT>Save</DT>
13222 <DD>Copy the displayed text to a file. If you just enter
13223 a filename, the attachment will be saved with that name in
13224 your
13225 home directory
13226 <!--chtml if pinemode="running"-->
13227 (which, in the present configuration of your system, is
13228 "<!--#echo var="HOME_DIR"-->")
13229 <!--chtml endif-->
13230 or current working directory
13231 <!--chtml if pinemode="running"-->
13232 (which, at least for your current Alpine "session,"
13233 is "<!--#echo var="CURRENT_DIR"-->")
13234 <!--chtml endif-->, depending on the
13235 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13236 configuration setting. You may enter the full
13237 path and filename to save it in another directory instead.
13239 <DT>WhereIs</DT>
13240 <DD>Search the attachment for a string of letters. If it is
13241 found, move to it. The string can be one word or a phrase.
13242 If there are multiple occurrences, the cursor moves to the
13243 first occurrence beyond the current cursor position.
13244 </DL>
13245 <P>
13246 <End of help on this topic>
13247 </BODY>
13248 </HTML>
13249 ======= h_pine_for_windows ========
13250 <HTML>
13251 <HEAD>
13252 <TITLE>GETTING HELP IN PC-ALPINE</TITLE>
13253 </HEAD>
13254 <BODY>
13255 <H1>Getting Help In PC-Alpine</H1>
13257 <P>
13258 PC-Alpine offers general and specific help text. From the <A
13259 HREF="main_menu_tx">MAIN MENU</A>, you will find an overview in the MAIN
13260 MENU HELP and the <A HREF="h_news">Release Notes</A>. On all screens,
13261 specific help for that screen is available from the toolbar Help menu or
13262 with the
13263 <!--chtml if pinemode="function_key"-->
13264 "F1" key.
13265 <!--chtml else-->
13266 "?" or "Ctrl-G" keys. "Ctrl-G" is used where
13267 typing "?" would be mistaken as entering text.
13268 <!--chtml endif-->
13270 <P>
13271 Although this version of Alpine is for Microsoft Windows, it is not
13272 considered a full "Graphical User Interface" application.
13273 Yet, many of the controls that Windows users are accustomed to seeing,
13274 such as scrollbars and toolbars, are available.
13276 <P>
13277 PC-Alpine offers considerable mouse support. You can view what is
13278 "click-able" by dragging your mouse over any screen; when the
13279 arrow cursor changes into a hand, you found something. Mouse-click
13280 possibilities include navigating between screens and folders and
13281 double-clicking on hyperlinks to open your Web browser.
13282 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
13283 screen. Examples of right-click options include "copy" after
13284 selecting text to copy and "View in New Window" when you click
13285 on a particular message in the Message Index. The menu choices available
13286 to you will vary based upon what screen is open, where on the screen your
13287 cursor is located, and even what action you have already taken.
13289 <P>
13290 <End of help on this topic>
13291 </BODY>
13292 </HTML>
13293 ===== h_composer =====
13294 <HTML>
13295 <HEAD>
13296 <TITLE>COMPOSER COMMANDS</TITLE>
13297 </HEAD>
13298 <BODY>
13299 <H1>COMPOSER COMMANDS</H1>
13301 CURSOR MOTION KEYS |EDITING KEYS<BR>
13302 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13303 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13304 ^P (Up Arrow) Previous line | ^^ Set a <A HREF="h_compose_markcutpaste">mark</A><BR>
13305 ^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>
13306 ^A Beginning of line | delete current line<BR>
13307 ^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>
13308 ^Y Previous page | cut with ^K, or unjustify<BR>
13309 ^V Next page |-------------------------------------<BR>
13310 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13311 ---------------------------------------| <!--chtml if pinemode="function_key"-->F6<!--chtml else-->^W<!--chtml endif--> <A HREF="h_composer_search">Whereis</A> (search for string)<BR>
13312 MESSAGE COMMANDS | GENERAL COMMANDS | <!--chtml if pinemode="function_key"-->F12<!--chtml else-->^T <!--chtml endif--> <A HREF="h_compose_spell">Spell checker</A><BR>
13313 <!--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>
13314 <!--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>
13315 <!--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>
13317 <P>
13318 NOTE:
13319 <OL>
13320 <LI>For help on a particular command, highlight the bold text associated
13321 with it above and hit Return.
13322 <LI> The availability of certain commands
13323 is determined by Alpine configuration files and system capabilities.
13324 At some sites, certain commands may not be available due to security or
13325 support concerns.
13326 <LI>Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
13327 Ctrl-\, ESC.
13328 <LI>For special handling of Ctrl-S and Ctrl-Q see special comments regarding
13329 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
13330 </OL>
13332 <P>
13333 HINT: To move rapidly to the bottom of a message you are composing,
13334 enter ^W^V. To go to the top, ^W^Y. These can be used in conjunction
13335 with the Mark and Cut commands to eliminate large amounts of unwanted
13336 text in a Reply.
13338 <H2>Description of Composer</H2>
13340 Alpine has a built-in editing program that allows you to compose messages
13341 without having to leave Alpine. The editor is designed to be very simple to
13342 use so that you can get started writing email right away.
13344 <P>
13345 Messages are usually just text, about 80 columns wide. Using upper and
13346 lower case is encouraged. On some systems the size limit of the message
13347 is about 100,000 characters, which is about 2,000 lines. You can include
13348 punctuation and special characters found on most keyboards, but you can't
13349 include characters with diacritical marks and certain special symbols.
13351 <P>
13352 Text automatically wraps as you type past the end of a line so you do not
13353 have to hit return. Using the
13354 "<A HREF="h_compose_justify">Justify</A>" command,
13355 you can also reformat text explicitly, perhaps after you have
13356 deleted some text.
13358 <P>
13359 You can include other text files with the
13360 "<A HREF="h_compose_readfile">Read File</A>" command,
13361 which will prompt you for the name of the file to insert at the
13362 current cursor postion.
13364 <P>
13365 <UL>
13366 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13367 </UL>
13368 <P>
13369 <End of help on this topic>
13370 </BODY>
13371 </HTML>
13372 ====== h_composer_browse =====
13373 <HTML>
13374 <HEAD>
13375 <TITLE>BROWSER</TITLE>
13376 </HEAD>
13377 <BODY>
13378 <H1>BROWSER</H1>
13379 This screen lets you browse your files and directories. To go to another
13380 directory (identified by "(dir)"), move the cursor to it and
13381 choose "Select" (the default choice on the menu);
13382 or choose "Goto" and enter the name of the directory.
13383 <!--chtml if pinemode="os_windows"-->
13384 <!--chtml else-->
13385 In Unix Alpine, you may use
13386 "~" to refer to your home directory or "~user" to refer
13387 to another's home directory.
13388 <!--chtml endif--><P>
13389 To select a file, move the cursor to it and
13390 choose "Select" (the default choice on the menu).
13391 <P>
13392 <UL>
13393 <LI>Note <B>if</B> you are currently using the BROWSER for choosing a file for
13394 inclusion in the
13395 message body (that is, you chose "Read File" with the cursor under
13396 the
13397 "----- Message Text -----" line
13398 while composing, then "To Files"): Since the file
13399 selected will become part of the message text, it must be in a format
13400 suitable for that (Alpine does not check!), such as a plain text file.
13401 Files of other formats (for example, graphics, databases, software
13402 programs) should be
13403 <B>attached</B> to the message instead --
13404 by moving the cursor in the COMPOSE MESSAGE screen into the
13405 message header area and pressing
13406 <!--chtml if pinemode="function_key"-->
13407 F6.
13408 <!--chtml else-->
13409 Ctrl-J.
13410 <!--chtml endif-->
13412 <P><LI>
13413 Note <B>if</B> you are currently using the BROWSER for saving a message
13414 attachment, or exporting a message, to a file: You can use the Add command to
13415 provide the name for a new file to save/export to, and then select that name
13416 to use it for the save/export operation. Back at the prompt
13417 "EXPORT: Copy message to file in ..." hit Enter, then choose
13418 either Overwrite or Append (it doesn't make a difference, since the file is
13419 so far empty). Note: If you cancel the
13420 operation at that point, the file created with the Add command will remain
13421 0 bytes in size.
13423 </UL>
13424 <P><UL>
13425 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13426 </UL>
13427 <P>
13428 <End of help on this topic>
13429 </BODY>
13430 </HTML>
13431 ====== h_composer_ins =====
13432 <HTML>
13433 <HEAD>
13434 <TITLE>INSERT TEXT FILE</TITLE>
13435 </HEAD>
13436 <BODY>
13437 <H1>INSERT TEXT FILE</H1>
13439 Use this function to insert a text file. The file name
13440 given can be an absolute file path name for your system
13441 <!--chtml if pinemode="os_windows"-->
13442 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
13443 with a relative pathname, or simply a file name without
13444 drive or directory specification.
13445 <!--chtml else-->
13446 (for example, "/tmp/exported.earlier" on Unix hosts),
13447 a file in your home directory, or a file path relative to your
13448 home directory. In Unix Alpine, you may use "~" to refer to
13449 your home directory or "~user" to refer to another
13450 account's home directory.
13451 <!--chtml endif-->
13452 <P>
13453 No wild card characters may be used.
13454 The file must reside on the system running Alpine.
13455 <P>
13456 If the
13457 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13458 feature is set, names are relative to your current working directory
13459 <!--chtml if pinemode="running"-->
13460 (which, at least for your current Alpine "session,"
13461 is "<!--#echo var="CURRENT_DIR"-->")
13462 <!--chtml endif-->
13463 rather than your home directory
13464 <!--chtml if pinemode="running"-->
13465 (which, in the present configuration of your system, is
13466 "<!--#echo var="HOME_DIR"-->")
13467 <!--chtml endif-->
13468 .
13469 <P><UL>
13470 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13471 </UL>
13472 <P>
13473 <End of help on this topic>
13474 </BODY>
13475 </HTML>
13476 ====== h_composer_ins_m =====
13477 <HTML>
13478 <HEAD>
13479 <TITLE>INSERT MESSAGE</TITLE>
13480 </HEAD>
13481 <BODY>
13482 <H1>INSERT MESSAGE</H1>
13484 Type in the number of a message in the currently open folder to insert it
13485 into your message.
13486 <P><UL>
13487 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13488 </UL>
13489 <P>
13490 <End of help on this topic>
13491 </BODY>
13492 </HTML>
13493 ====== h_composer_search =====
13494 <HTML>
13495 <HEAD>
13496 <TITLE>Explanation of Composer Whereis Command </TITLE>
13497 </HEAD>
13498 <BODY>
13499 <H1>Help For Whereis Command</H1>
13501 Whereis is used to search the message for a word or part of a word.
13502 When searching in the composer, only the message part of your mail is
13503 searched, and the cursor is put on the first occurrence appearing
13504 after the location of the cursor. The search will wrap to the
13505 beginning of the message when it no longer finds matches in the
13506 remainder of the message.
13508 To search for the same string a second time, press
13509 <!--chtml if pinemode="function_key"-->
13510 "F6"
13511 <!--chtml else-->
13512 "^W"
13513 <!--chtml endif-->
13514 to begin search and then just press RETURN to accept the previous
13515 search string shown in square brackets rather than entering a new
13516 search string.<P>
13518 The "Search" prompt has several sub-command available:
13520 <DL>
13521 <DT>Get Help</DT>
13522 <DD> Takes you to this help page.
13524 <DT>Cancel</DT>
13525 <DD> Cancels the prompt. No search takes place.
13527 <DT>First Line</DT>
13528 <DD> Takes you back to the composer with the cursor on the first character
13529 of the first line of text.
13531 <DT>Last Line</DT>
13532 <DD> Takes you back to the composer with the cursor on the last character
13533 of the last line of text.
13535 <DT>Replace (Optional)</DT>
13536 <DD> This sub-command is enabled by the
13537 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13538 feature (which is on by default); see its help screen for details on how replacing works.
13540 </DL>
13542 <End of help on this topic>
13543 </BODY>
13544 </HTML>
13545 ====== h_sigedit_search =====
13546 <HTML>
13547 <HEAD>
13548 <TITLE>Explanation of Whereis Command </TITLE>
13549 </HEAD>
13550 <BODY>
13551 <H1>Help For Whereis Command</H1>
13553 Whereis is used to search for a word or part of a word.
13554 When searching the cursor is put on the first occurrence appearing
13555 after the location of the cursor. The search will wrap to the
13556 beginning of the signature when it no longer finds matches in the
13557 remainder of the signature.
13559 To search for the same string a second time, press
13560 <!--chtml if pinemode="function_key"-->
13561 "F6"
13562 <!--chtml else-->
13563 "^W"
13564 <!--chtml endif-->
13565 to begin search and then just press RETURN to accept the previous
13566 search string shown in square brackets rather than entering a new
13567 search string.<P>
13569 The "Search" prompt has several sub-command available:
13571 <DL>
13572 <DT>Get Help</DT>
13573 <DD> Takes you to this help page.
13575 <DT>Cancel</DT>
13576 <DD> Cancels the prompt. No search takes place.
13578 <DT>First Line</DT>
13579 <DD> Takes you back to the composer with the cursor on the first character
13580 of the first line of text.
13582 <DT>Last Line</DT>
13583 <DD> Takes you back to the composer with the cursor on the last character
13584 of the last line of text.
13586 <DT>Replace (Optional)</DT>
13587 <DD> This sub-command is enabled by the
13588 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13589 feature (which is on by default); see its help screen for details on how replacing works.
13591 </DL>
13593 <End of help on this topic>
13594 </BODY>
13595 </HTML>
13596 ======= h_composer_to ====
13597 <HTML>
13598 <HEAD>
13599 <TITLE>THE MESSAGE COMPOSER'S TO FIELD</TITLE>
13600 </HEAD>
13601 <BODY>
13602 <H1>THE MESSAGE COMPOSER'S TO FIELD</H1>
13604 <H2>The "To:" field</H2>
13605 The address you enter here must be a valid email address that is reachable
13606 from your site.
13608 <H2>Email Address Format</H2>
13609 You may enter a full name and email address,
13610 <!--chtml if pinemode="os_windows"-->
13611 <!--chtml else-->
13612 a local (meaning, on the same
13613 host as the one you are running Alpine on) username that Alpine will
13614 complete for you,
13615 <!--chtml endif-->
13616 the nickname of someone in a
13617 <A HREF="h_abook_opened">Alpine Address Book</A>, or a local
13618 mail alias defined by your system administrator. When you move the cursor
13619 out of this field, the nicknames will be expanded to the addresses in your
13620 address book, and the local usernames will be expanded to include the
13621 persons' actual names. You may enter as many addresses as you wish, but they
13622 must be separated by commas. You can move around this and other header fields
13623 with the arrow keys and use many of the usual composer editing keys.
13624 <P>
13625 <UL>
13626 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13627 </UL>
13629 <P>
13630 <H2>MESSAGE HEADER COMMANDS</H2>
13631 <!--chtml if pinemode="function_key"-->
13632 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13633 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13634 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13635 ^P (Up Arrow) Previous line |<BR>
13636 ^N (Down Arrow) Next line | F9 Cut marked text or<BR>
13637 ^A Beginning of line | delete current line<BR>
13638 ^E End of line | F10 Undelete line(s)<BR>
13639 F7 Previous page | ^W <A HREF="h_composer_search">Whereis</A> (search text)<BR>
13640 F8 Next page |-------------------------------------<BR>
13641 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13642 ----------------------------------------|<BR>
13643 MESSAGE COMMANDS | GENERAL COMMANDS | F12 To Addressbook/Browser<BR>
13644 F3 <A HREF="h_compose_cancel">Cancel</A> | F1 Get help | F4 Attach File<BR>
13645 F11 <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13646 F2 <A HREF="h_compose_send">Send</A> | | F5 <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13647 <!--chtml else-->
13648 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13649 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13650 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13651 ^P (Up Arrow) Previous line | <BR>
13652 ^N (Down Arrow) Next line | ^K Cut marked text or<BR>
13653 ^A Beginning of line | delete current line<BR>
13654 ^E End of line | ^U Undelete line(s)<BR>
13655 ^Y Previous page |<BR>
13656 ^V Next page |-------------------------------------<BR>
13657 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13658 ----------------------------------------| ^R <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13659 MESSAGE COMMANDS | GENERAL COMMANDS | ^T To Addressbook/Browser<BR>
13660 ^C <A HREF="h_compose_cancel">Cancel</A> | ^G Get help | ^J Attach File<BR>
13661 ^O <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13662 ^X <A HREF="h_compose_send">Send</A> | | TAB <A HREF="h_compose_addrcomplete">Address Completion</A><BR>
13663 <!--chtml endif-->
13665 <P>
13666 NOTE:
13667 <OL>
13668 <LI>For help on a particular command, highlight the bold text associated
13669 with it above and hit Return.
13670 <LI> The availability of certain commands
13671 is determined by Alpine configuration files and system capabilities.
13672 At some sites, certain commands may not be available due to security or
13673 support concerns.
13674 </OL>
13676 <P>
13677 <UL>
13678 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13679 </UL><P>
13680 <End of help on this topic>
13681 </BODY>
13682 </HTML>
13683 ======= h_composer_cc ====
13684 <HTML>
13685 <HEAD>
13686 <TITLE>THE MESSAGE COMPOSER'S CC FIELD</TITLE>
13687 </HEAD>
13688 <BODY>
13689 <H1>THE MESSAGE COMPOSER'S CC FIELD</H1>
13690 The Cc: field is just like the To: field, except it is used for addressees
13691 that you wish to send a "carbon" copy to. That is, the message is
13692 not directly meant directly "for" these recipients, but you wanted
13693 them to see the message. The only difference the recipients see is that their
13694 name is in the Cc: field, rather than the To: field.
13695 <P>
13696 For help with Cc: field editing
13697 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13698 <P>
13699 <UL>
13700 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13701 </UL>
13702 <P>
13703 <UL>
13704 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13705 </UL><P>
13706 <End of help on this topic>
13707 </BODY>
13708 </HTML>
13709 ======= h_composer_bcc ====
13710 <HTML>
13711 <HEAD>
13712 <TITLE>THE MESSAGE COMPOSER'S BCC FIELD</TITLE>
13713 </HEAD>
13714 <BODY>
13715 <H1>THE MESSAGE COMPOSER'S BCC FIELD</H1>
13716 The "Bcc:" (Blind carbon copy) header is used when you wish to send
13717 a copy of the message to one or more people whose addresses you do not
13718 wish disclosed, either to reduce clutter or for confidentiality.
13719 <P>
13720 The format of the Bcc: field is just the same as the To: and Cc: fields in
13721 the way the addresses are entered. The recipients listed here will
13722 receive a copy of the message, but --assuming your site's mail transport
13723 software is properly configured-- their addresses will not show up in the
13724 headers of the message, as delivered to all of the recipients. The To:
13725 and Cc: recipients will not know a copy was sent to the Bcc: recipients.
13726 <P>
13727 Note: if there is no To: or Cc: or Lcc: address in the message, Alpine
13728 will automatically generate and place in the To: field a pseudo-address of
13729 "undisclosed-recipients: ;"
13730 or whatever string has been specified in the
13731 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
13732 variable.
13733 <P>
13734 The reason for this is to avoid embarrassment caused by some Internet
13735 mail transfer software that interprets a "missing" To: header as
13736 an error and replaces it with an Apparently-to: header that may contain
13737 the addresses you entered on the Bcc: line. In addition, it may be
13738 less disconcerting to Bcc: recipients to see <B>something</B> in the To: field.
13739 <P>
13740 You can manipulate what text ends up on the (originally) empty To:
13741 field. Just remember to put a colon and semicolon at the end of the
13742 field, which is a special notation denoting that it is not a real address.
13743 <P>
13744 For information on message header editing
13745 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13746 <P>
13747 <UL>
13748 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13749 </UL>
13750 <P>
13751 <UL>
13752 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13753 </UL><P>
13754 <End of help on this topic>
13755 </BODY>
13756 </HTML>
13757 ======= h_composer_lcc ====
13758 <HTML>
13759 <HEAD>
13760 <TITLE>THE MESSAGE COMPOSER'S LCC FIELD</TITLE>
13761 </HEAD>
13762 <BODY>
13763 <H1>THE MESSAGE COMPOSER'S LCC FIELD</H1>
13764 The "Lcc:" (List carbon copy) header is intended to be used when
13765 you wish to send a message to a list of people but avoid having all
13766 of their addresses visible, in order to reduce clutter when the
13767 message is received.
13768 <P>
13769 It is similar to the
13770 <A HREF="h_composer_bcc">"Bcc" (Blind carbon copy) header</A>
13771 in that individual
13772 addressees are hidden, but Lcc is designed to work specifically with
13773 distribution lists you have created in your
13774 <A HREF="h_abook_opened">Alpine Address Book</A>. Placing
13775 the nickname of the list on the Lcc line will result in the full name of
13776 your Alpine Address Book list being placed on the To: line of the message,
13777 using a special notation that distinguishes it from a real address. You
13778 must leave the To: line blank for your list name to appear there.
13779 <P>
13780 For example, if you have this list entered in your Address Book:<PRE>
13782 largo Key Largo List DISTRIBUTION LIST:
13783 bogie@mgm.com
13784 lauren@mgm.com
13785 walter@mgm.com</PRE>
13788 and you enter "largo" on the Lcc: line while composing a message,
13789 the result is:<PRE>
13791 To : Key Largo List: ;
13792 Cc :
13793 Bcc :
13794 Fcc : sent-mail
13795 Lcc : Key Largo List <bogie@mgm.com>,
13796 lauren@mgm.com,
13797 walter@mgm.com
13798 Subject :</PRE>
13800 Each recipient listed on the Lcc: line receives a copy of the message
13801 without their address being visible (as though they were listed on the
13802 Bcc: line). The colon-semicolon notation used to put the full-name of the
13803 list on the To: line is a special address format that doesn't specify any
13804 actual addressees, but does give some information to the recipients of the
13805 message.
13806 <P>
13807 Note: if after entering an LCC, you delete the list name that is placed
13808 on the To: line, then recipients will see <PRE>
13809 To: undisclosed-recipients: ;</PRE>
13811 (or whatever string is defined in the
13812 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
13813 variable) just as in the BCC case.
13814 <P>
13815 For help with Lcc: field editing
13816 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13817 <P>
13818 <UL>
13819 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13820 </UL>
13821 <P>
13822 <UL>
13823 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13824 </UL><P>
13825 <End of help on this topic>
13826 </BODY>
13827 </HTML>
13828 ======= h_composer_from =======
13829 <HTML>
13830 <HEAD>
13831 <TITLE>THE MESSAGE COMPOSER'S FROM FIELD</TITLE>
13832 </HEAD>
13833 <BODY>
13834 <H1>THE MESSAGE COMPOSER'S FROM FIELD</H1>
13836 This header carries your return address. It is the address toward which
13837 replies (and often, future unrelated correspondence) will be directed,
13838 unless you have <A HREF="h_config_custom_hdrs">defined an optional
13839 "Reply-To:" header</A> in the SETUP CONFIGURATION screen. Make
13840 sure this address is correct.
13841 <P>
13842 For help with message header editing
13843 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13844 <P>
13845 <UL>
13846 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13847 </UL>
13848 <P>
13849 <UL>
13850 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13851 </UL><P>
13852 <End of help on this topic>
13853 </BODY>
13854 </HTML>
13855 ======= h_composer_reply_to =======
13856 <HTML>
13857 <HEAD>
13858 <TITLE>THE MESSAGE COMPOSER'S REPLY-TO FIELD</TITLE>
13859 </HEAD>
13860 <BODY>
13861 <H1>THE MESSAGE COMPOSER'S REPLY-TO FIELD</H1>
13863 Most people should not need this header. The Reply-To: header is used in
13864 cases where you would like replies to your messages to be directed to an
13865 address other than your normal "From:" address. This is atypical,
13866 but can happen when you use multiple machines and do not have the same account
13867 name on each one, or when you wish to direct certain replies to accounts
13868 or folders designated for specific classes of correspondence.
13869 <P>
13870 For help with message header editing
13871 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13872 <P>
13873 <UL>
13874 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13875 </UL>
13877 <P>
13878 <UL>
13879 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13880 </UL><P>
13881 <End of help on this topic>
13882 </BODY>
13883 </HTML>
13884 ======= h_composer_custom_addr ====
13885 <HTML>
13886 <HEAD>
13887 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
13888 </HEAD>
13889 <BODY>
13890 <H1>CUSTOMIZED HEADER FIELD</H1>
13891 This is a customized header, i.e. not one that is part of Alpine's normal
13892 set of Compose headers.
13893 <P>
13894 For help with message header editing
13895 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13896 <P>
13897 <UL>
13898 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13899 </UL>
13900 <P>
13901 <UL>
13902 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13903 </UL><P>
13904 <End of help on this topic>
13905 </BODY>
13906 </HTML>
13907 ======= h_composer_custom_free ====
13908 <HTML>
13909 <HEAD>
13910 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
13911 </HEAD>
13912 <BODY>
13913 <H1>CUSTOMIZED HEADER FIELD</H1>
13914 This is a customized header, i.e. not one that is part of Alpine's normal
13915 set of Compose headers.
13916 <P>
13917 This field consists of arbitrary text.
13918 <P>
13919 For help with message header editing
13920 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13921 <P>
13922 <UL>
13923 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13924 </UL><P>
13925 <End of help on this topic>
13926 </BODY>
13927 </HTML>
13928 ====== h_composer_news =====
13929 <HTML>
13930 <HEAD>
13931 <TITLE>THE MESSAGE COMPOSER'S NEWSGRPS LINE</TITLE>
13932 </HEAD>
13933 <BODY>
13934 <h1>THE MESSAGE COMPOSER'S NEWSGRPS LINE</h1>
13935 Use the newsgroups line to specify any and all USENET newsgroups to which
13936 your message should be posted. When composing a message from scratch, this
13937 line may be hidden. If so, just press the rich headers command
13938 (<!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif-->)
13939 to make it visible.
13940 <P>
13941 <EM>Be aware</EM> that when you post to a newsgroup thousands of
13942 people will be reading your message. Also, you or your system manager
13943 must have defined an "<!--#echo var="VAR_nntp-server"-->" in your Alpine configuration
13944 in order for you to be able to post.
13945 <P>
13946 For help with message header editing
13947 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13948 <P><UL>
13949 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13950 </UL>
13951 <P>
13952 <End of help on this topic>
13953 </BODY>
13954 </HTML>
13955 ======= h_composer_fcc ====
13956 <HTML>
13957 <HEADER>
13958 <TITLE>THE MESSAGE COMPOSER'S FCC FIELD</TITLE>
13959 </HEADER>
13960 <BODY>
13961 <H1>THE MESSAGE COMPOSER'S FCC FIELD</H1>
13962 The FCC (File Carbon Copy) specifies the folder used to keep a copy of
13963 each outgoing message. The default value can be configured with the
13964 "<!--#echo var="VAR_default-fcc"-->" and "<!--#echo var="VAR_fcc-name-rule"-->" options. You can change or remove
13965 the file carbon copy on any message you send by editing the FCC header.<p>
13967 You may type ^T to get a list of all your folders and select one to use as
13968 the FCC for this message.<P>
13970 For help with message header editing
13971 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13972 <P>
13973 <UL>
13974 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13975 </UL><P>
13976 <End of help on this topic>
13977 </BODY>
13978 </HTML>
13979 ======= h_composer_subject ====
13980 <HTML>
13981 <HEADER>
13982 <TITLE>THE MESSAGE COMPOSER'S SUBJECT FIELD</TITLE>
13983 </HEADER>
13984 <BODY>
13985 <H1>THE MESSAGE COMPOSER'S SUBJECT FIELD</H1>
13987 The subject header provides a place to enter a few words that summarize
13988 the topic of the message you are sending. You may leave this line blank,
13989 but it is considered a courtesy to use a meaningful subject.<p>
13991 For help with message header editing
13992 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13993 <P>
13994 <UL>
13995 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13996 </UL><P>
13997 <End of help on this topic>
13998 </BODY>
13999 </HTML>
14000 ======= h_composer_attachment ====
14001 <HTML>
14002 <HEAD>
14003 <TITLE>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</TITLE>
14004 </HEAD>
14005 <BODY>
14006 <H1>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</H1>
14008 The "Attchmnt:" field is where you specify what file or
14009 files you'd like attached to
14010 the message you are composing. Those files must reside on the machine
14011 running Alpine. If your file is on a PC or Mac and you run Alpine with an
14012 account on a Unix machine, you'll have to transfer it before attaching it.
14013 Contact local computer support people for assistance with transferring.
14015 <P>
14016 The file name
14017 given can be an absolute file path name for your system
14018 <!--chtml if pinemode="os_windows"-->
14019 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
14020 with a relative pathname, or simply a file name without
14021 drive or directory specification.
14022 <!--chtml else-->
14023 (for example, "/tmp/exported.earlier" on Unix hosts),
14024 a file in your home directory, or a file path relative to your
14025 home directory. In Unix Alpine, you may use "~" to refer to
14026 your home directory or "~user" to refer to another
14027 account's home directory.
14028 <!--chtml endif--><P>
14029 No wild card characters may be used.
14030 <P>If the
14031 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
14032 feature is set, names are relative to your current working directory
14033 <!--chtml if pinemode="running"-->
14034 (which, at least for your current Alpine "session,"
14035 is "<!--#echo var="CURRENT_DIR"-->")
14036 <!--chtml endif-->
14037 rather than your home directory
14038 <!--chtml if pinemode="running"-->
14039 (which, in the present configuration of your system, is
14040 "<!--#echo var="HOME_DIR"-->")
14041 <!--chtml endif-->
14042 .
14043 <P>
14044 Alpine uses MIME encoding for attachments, so binaries and files of any
14045 length can safely be delivered to any MIME-capable mail reading program.
14046 If you send an attachment to someone who does not have a MIME-capable mail
14047 reading program yet, then the main message text will be readable, but
14048 attachments (even attachments that are just plain text) are not.
14049 <P>
14051 Typing the filename on the Attchmnt: line achieves the same
14052 result as using the
14053 <!--chtml if pinemode="function_key"-->
14054 F6
14055 <!--chtml else-->
14056 Ctrl-J
14057 <!--chtml endif--> command.
14058 <P>
14060 If you Forward a message with attachments, you may delete them from your
14061 Forwarded message by editing the Attchmnt header line.
14062 <P>
14064 For help with message header editing
14065 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14066 <P>
14067 <UL>
14068 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14069 </UL><P>
14070 <End of help on this topic>
14071 </BODY>
14072 </HTML>
14073 ======= h_composer_ctrl_j ====
14074 <HTML>
14075 <HEAD>
14076 <TITLE>COMPOSER ATTACH</TITLE>
14077 </HEAD>
14078 <BODY>
14079 After the
14080 <!--chtml if pinemode="function_key"-->
14081 F6
14082 <!--chtml else-->
14083 Ctrl-J
14084 <!--chtml endif--> command:
14085 At the "File to attach:" prompt, enter the name of the
14086 existing file to attach to your message.
14087 When the feature
14088 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
14089 is set
14090 you need only enter the beginning of the filename (enough of it to uniquely
14091 identify the file) and press TAB to complete it.
14093 Or, press ^T to use the BROWSER screen for
14094 selecting the file. <P>
14095 For more information on attaching files, see the help screen for the
14096 composer's
14097 <A HREF="h_composer_attachment">Attchmnt: field</A>, which is normally hidden,
14098 but can be revealed using the
14099 <!--chtml if pinemode="function_key"-->
14100 F5
14101 <!--chtml else-->
14102 Ctrl-R
14103 <!--chtml endif-->
14104 command with the cursor positioned above the
14105 "----- Message Text -----" line in the COMPOSE MESSAGE screen.
14106 <P>
14107 <End of help on this topic>
14108 </BODY>
14109 </HTML>
14110 ======= h_edit_nav_cmds =========
14111 <HTML>
14112 <HEAD>
14113 <TITLE>Composer Editing Commands Explained</TITLE>
14114 </HEAD>
14115 <BODY>
14116 <H1>EDITING and NAVIGATION COMMANDS</H1>
14117 <!--chtml if pinemode="function_key"-->
14118 <PRE>
14119 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
14120 ^B (Left Arrow) Back character | ^D Delete current character
14121 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14122 ^P (Up Arrow) Previous line |
14123 ^N (Down Arrow) Next line | F9 Cut marked text or
14124 ^A Beginning of line | delete current line
14125 ^E End of line | F10 Undelete line(s)
14126 F7 Previous page |
14127 F8 Next page |-------------------------------------
14128 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
14129 ----------------------------------------|
14130 EXIT COMMANDS | GENERAL COMMANDS | F12 To Addressbook
14131 F3 Cancel | F1 Get help | F12 RichView (expand lists)
14132 F2 eXit/save | ^Z Suspend | ^L Redraw Screen
14133 </PRE>
14134 <!--chtml else-->
14135 <PRE>
14136 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
14137 ^B (Left Arrow) Back character | ^D Delete current character
14138 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14139 ^P (Up Arrow) Previous line |
14140 ^N (Down Arrow) Next line | ^K Cut marked text or
14141 ^A Beginning of line | delete current line
14142 ^E End of line | ^U Undelete line(s)
14143 ^Y Previous page |
14144 ^V Next page |-------------------------------------
14145 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
14146 ----------------------------------------|
14147 EXIT COMMANDS | GENERAL COMMANDS | ^T To Addressbook
14148 ^C Cancel | ^G Get help | ^R RichView (expand lists)
14149 ^X eXit/save | ^Z Suspend | ^L Redraw Screen
14150 </PRE>
14151 <!--chtml endif-->
14152 <End of help on this topic>
14153 </BODY>
14154 </HTML>
14155 ===== h_composer_sigedit =====
14156 <HTML>
14157 <HEAD>
14158 <TITLE>Signature Editor Commands Explained</TITLE>
14159 </HEAD>
14160 <BODY>
14161 <H1>SIGNATURE EDITOR COMMANDS</H1>
14162 <!--chtml if pinemode="function_key"-->
14163 <PRE>
14164 CURSOR MOTION KEYS |EDITING KEYS
14165 ^B (Left Arrow) Back character | ^D Delete current character
14166 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14167 ^P (Up Arrow) Previous line | ^^ Set a mark
14168 ^N (Down Arrow) Next line | F9 Cut marked text or
14169 ^A Beginning of line | delete current line
14170 ^E End of line | F10 Paste text, undelete lines
14171 F7 Previous page | cut with ^K, or unjustify
14172 F8 Next page |-------------------------------------
14173 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14174 ---------------------------------------| F6 Whereis (search for string)
14175 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
14176 F3 Cancel | F1 Get help | F4 Justify paragraph
14177 | ^Z Suspend | ^L Redraw Screen
14178 F2 Send | F6 Alt. editor | F5 Read in a file
14179 </PRE>
14180 <!--chtml else-->
14181 <PRE>
14182 CURSOR MOTION KEYS |EDITING KEYS
14183 ^B (Left Arrow) Back character | ^D Delete current character
14184 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14185 ^P (Up Arrow) Previous line | ^^ Set a mark
14186 ^N (Down Arrow) Next line | ^K Cut marked text or
14187 ^A Beginning of line | delete current line
14188 ^E End of line | ^U Paste text, undelete lines
14189 ^Y Previous page | cut with ^K, or unjustify
14190 ^V Next page |-------------------------------------
14191 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14192 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
14193 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
14194 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
14195 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
14196 ^X Send | ^_ Alt. editor | ^R Read in a file
14197 </PRE>
14198 <!--chtml endif-->
14200 NOTE: The presence or absence of the following commands is determined
14201 by "Feature-List" options in your Alpine configuration. Also,
14202 some of these commands may be administratively disabled by your system
14203 manager; if they don't work, please check with your local help desk
14204 before reporting a bug.
14205 <P>
14206 <UL>
14207 <LI>Suspend (suspends Alpine and gives a system prompt)
14208 <LI>Alternate editor (allows you to compose with your own editor)
14209 </UL>
14210 <P>
14212 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
14213 Ctrl-\, ESC
14214 <P>
14216 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
14217 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
14218 <P>
14219 <End of help on this topic>
14220 </BODY>
14221 </HTML>
14222 ===== h_composer_commentedit =====
14223 <HTML>
14224 <HEAD>
14225 <TITLE>Comment Editor Commands Explained</TITLE>
14226 </HEAD>
14227 <BODY>
14228 <H1>COMMENT EDITOR COMMANDS</H1>
14229 <!--chtml if pinemode="function_key"-->
14230 <PRE>
14231 CURSOR MOTION KEYS |EDITING KEYS
14232 ^B (Left Arrow) Back character | ^D Delete current character
14233 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14234 ^P (Up Arrow) Previous line | ^^ Set a mark
14235 ^N (Down Arrow) Next line | F9 Cut marked text or
14236 ^A Beginning of line | delete current line
14237 ^E End of line | F10 Paste text, undelete lines
14238 F7 Previous page | cut with ^K, or unjustify
14239 F8 Next page |-------------------------------------
14240 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14241 ---------------------------------------| F6 Whereis (search for string)
14242 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
14243 F3 Cancel | F1 Get help | F4 Justify paragraph
14244 | ^Z Suspend | ^L Redraw Screen
14245 F2 Send | F6 Alt. editor | F5 Read in a file
14246 </PRE>
14247 <!--chtml else-->
14248 <PRE>
14249 CURSOR MOTION KEYS |EDITING KEYS
14250 ^B (Left Arrow) Back character | ^D Delete current character
14251 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14252 ^P (Up Arrow) Previous line | ^^ Set a mark
14253 ^N (Down Arrow) Next line | ^K Cut marked text or
14254 ^A Beginning of line | delete current line
14255 ^E End of line | ^U Paste text, undelete lines
14256 ^Y Previous page | cut with ^K, or unjustify
14257 ^V Next page |-------------------------------------
14258 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14259 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
14260 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
14261 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
14262 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
14263 ^X Send | ^_ Alt. editor | ^R Read in a file
14264 </PRE>
14265 <!--chtml endif-->
14267 NOTE: The presence or absence of the following commands is determined
14268 by "Feature-List" options in your Alpine configuration. Also,
14269 some of these commands may be administratively disabled by your system
14270 manager; if they don't work, please check with your local help desk
14271 before reporting a bug.
14272 <P>
14273 <UL>
14274 <LI>Suspend (suspends Alpine and gives a system prompt)
14275 <LI>Alternate editor (allows you to compose with your own editor)
14276 </UL>
14277 <P>
14279 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
14280 Ctrl-\, ESC
14281 <P>
14283 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
14284 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
14285 <P>
14286 <End of help on this topic>
14287 </BODY>
14288 </HTML>
14289 ======= h_composer_abook_nick =======
14290 <HTML>
14291 <HEAD>
14292 <TITLE>Addressbook Nickname Explained</TITLE>
14293 </HEAD>
14294 <BODY>
14295 This is a short nickname for this address book entry. If it is used in
14296 place of an address from the composer, the composer will fill in the
14297 address(es) for the entry that matches the nickname.
14298 <P>
14300 Look <A HREF="h_edit_nav_cmds">here</A>
14301 to see the available Editing and Navigation commands.
14302 <P>
14303 <End of help on this topic>
14304 </BODY>
14305 </HTML>
14306 ======= h_composer_abook_full =======
14307 <HTML>
14308 <HEAD>
14309 <TITLE>Addressbook Fullname Explained</TITLE>
14310 </HEAD>
14311 <BODY>
14312 This is the full name field for this entry. If this is going to be a
14313 distribution list (more than one address), it should be a descriptive
14314 phrase describing the list. It will be included in the mail header if you
14315 put the list in the To: or CC: field, or in the To: line if you put the
14316 list in the Lcc: field. It's OK to leave this field blank (and OK to
14317 leave any of the other fields blank, too). If this address book entry is
14318 going to be a simple entry with just one address, then this field is the
14319 person's name. When you send mail to this entry, this is the field to the
14320 left of the brackets. That is, it is the most readable part of the
14321 address. For example, in the sample address:
14322 <PRE>
14323 John Doe <jdoe@some.domain>
14324 </PRE>
14325 "John Doe" is the full name field. If you are sorting your address book
14326 with one of the options that uses full names, then it might be useful to
14327 enter the full name as "Last, First", for example:
14328 <PRE>
14329 Doe, John
14330 </PRE>
14331 so that it will be sorted using Doe instead of John. This will be changed
14332 back into John Doe when you use it.
14333 <P>
14334 Look <A HREF="h_edit_nav_cmds">here</A>
14335 to see the available Editing and Navigation commands.
14336 <P>
14337 <End of help on this topic>
14338 </BODY>
14339 </HTML>
14340 ======= h_composer_abook_fcc =======
14341 <HTML>
14342 <HEAD>
14343 <TITLE>Addressbook Fcc Explained</TITLE>
14344 </HEAD>
14345 <BODY>
14346 If this entry is the first one in the To: line of an outgoing message,
14347 this field will be used for the Fcc (File Carbon Copy) instead of whatever
14348 you would normally get (which depends on which
14349 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
14350 you've chosen).
14351 <P>
14352 If this field consists of two double quotes ("") that tells Alpine
14353 that you don't want any Fcc associated with this entry.
14354 <P>
14355 Look <A HREF="h_edit_nav_cmds">here</A>
14356 to see the available Editing and Navigation commands.
14357 <P>
14358 <End of help on this topic>
14359 </BODY>
14360 </HTML>
14361 ====== h_config_combined_abook_display =====
14362 <HTML>
14363 <HEAD>
14364 <TITLE>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></TITLE>
14365 </HEAD>
14366 <BODY>
14367 <H1>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></H1>
14369 This feature affects the address book display screens.
14370 Normally, expanding an address book from the ADDRESS BOOK LIST screen
14371 will cause the remaining address books and directory servers to disappear
14372 from the screen, leaving only the entries of the expanded address book.
14373 If this feature is set, then the other address books will remain on the screen,
14374 so that all of the address books can be present at once.
14376 <P>
14377 The way that commands work won't be changed.
14378 For example, the Select All command will select all of the entries in the
14379 current address book, not all of the entries in all of the address books.
14380 The WhereIs command will change a little.
14381 It will search through all of the text on the screen plus all of the entries
14382 from expanded address books.
14384 <P>
14385 When this feature is set, the setting of the feature
14386 <A HREF="h_config_expanded_addrbooks">"<!--#echo var="FEAT_expanded-view-of-addressbooks"-->"</A>
14387 has an effect.
14388 <P>
14389 <End of help on this topic>
14390 </BODY>
14391 </HTML>
14392 ====== h_config_titlebar_color_style =====
14393 <HTML>
14394 <HEAD>
14395 <TITLE>OPTION: <!--#echo var="VAR_titlebar-color-style"--></TITLE>
14396 </HEAD>
14397 <BODY>
14398 <H1>OPTION: <!--#echo var="VAR_titlebar-color-style"--></H1>
14400 This option affects the colors used to display the titlebar (the top
14401 line on the screen) when viewing a message.
14403 <P>
14404 The available options include:
14405 <P>
14407 <DL>
14408 <DT>default</DT>
14409 <DD>The color of the titlebar will be the color you set for the
14410 <A HREF="h_config_title_color">Title Color</A>.
14411 The Title Color may be set by using the
14412 <A HREF="h_color_setup">Setup Kolor</A> screen.
14413 </DD>
14415 <DT>indexline</DT>
14416 <DD>The color of the titlebar will be the same as the color of the
14417 index line corresponding to the message being viewed.
14418 The rules that determine what color the index line will be may be set
14419 up by going to the Setup/Rules/Indexcolor screen.
14420 If the index line for a message is not colored explicitly by the
14421 Indexcolor rules, then the titlebar will be colored the same as for
14422 the "default" option above (which is not the same color that
14423 the index line itself will have).
14424 </DD>
14426 <DT>reverse-indexline</DT>
14427 <DD>This is similar to the "indexline" option except the
14428 foreground and background colors from the corresponding index line will
14429 be reversed.
14430 For example, if the index line color is red letters on a white background,
14431 then the titlebar will be white letters on a red background.
14432 If the index line for a message is not colored explicitly by the
14433 Indexcolor rules, then the titlebar will be colored the same as for
14434 the "default" option above (which is not the same color that
14435 the index line itself will have).
14436 </DD>
14437 </DL>
14439 <P>
14441 <UL>
14442 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14443 </UL><P>
14444 <End of help on this topic>
14445 </BODY>
14446 </HTML>
14447 ====== h_config_index_color_style =====
14448 <HTML>
14449 <HEAD>
14450 <TITLE>OPTION: <!--#echo var="VAR_current-indexline-style"--></TITLE>
14451 </HEAD>
14452 <BODY>
14453 <H1>OPTION: <!--#echo var="VAR_current-indexline-style"--></H1>
14455 This option affects the colors used to display the current line in the
14456 MESSAGE INDEX screen.
14457 If you do not have Index Color Rules defined, then this option will
14458 have no effect in the index.
14459 Those Rules may be defined by going to the Setup/Rules/Indexcolor screen.
14460 <P>
14461 If the option
14462 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
14463 is turned on and the
14464 <A HREF="h_config_incunseen_color">Incoming Unseen Color</A>
14465 is set to something other than the default, then
14466 this option also affects the color used to display the current folder
14467 in the Incoming FOLDER LIST screen.
14469 <P>
14470 The available options include:
14471 <P>
14473 <DL>
14474 <DT>flip-colors</DT>
14475 <DD>This is the default.
14476 If an index line is colored because it matches one of your
14477 Index Color Rules, then its colors will be reversed when it is the currently
14478 highlighted line.
14479 For example, if the line is normally red text on a blue background, then
14480 when it is the current line it will be drawn as blue text on a red background.
14481 <P>
14482 The rest of the option values all revert to this flip-colors behavior if
14483 there is no Reverse Color defined.
14484 </DD>
14486 <DT>reverse</DT>
14487 <DD>With this option the Reverse color is always used to highlight the
14488 current line.
14489 </DD>
14491 <DT>reverse-fg</DT>
14492 <DD>The foreground part of the Reverse Color is used to highlight
14493 the current line.
14494 If this would cause the text to be unreadable (because the foreground and
14495 background colors are the same) or if it would cause no change in the
14496 color of the index line, then the colors are flipped instead.
14497 <P>
14498 Some people think this works particularly well if you use different
14499 background colors to emphasize "interesting" lines,
14500 but always with the same Normal foreground color,
14501 and you use a different foreground color for the Reverse Color.
14502 </DD>
14504 <DT>reverse-fg-no-ambiguity</DT>
14505 <DD>With the "reverse-fg" rule above, it is possible that
14506 the resulting color will be exactly the same as the regular Reverse
14507 Color.
14508 That can lead to some possible confusion because an
14509 "interesting"
14510 line that is the current line will be displayed exactly the same as a
14511 non-interesting line that is current.
14512 You can't tell whether the line is just a regular current line or if it is
14513 an "interesting" current line by looking at the color.
14514 Setting the option to this value removes that ambiguity.
14515 It is the same as the "reverse-fg" setting unless the resulting
14516 interesting current line would look just like a non-interesting current line.
14517 In that case, the interesting line's colors are simply flipped (like in the
14518 default behavior).
14519 <P>
14520 As an alternative way to preserve the line's interestingness in this case,
14521 you may find that using both a different foreground and a different
14522 background color for the interesting line will help.
14523 </DD>
14525 <DT>reverse-bg</DT>
14526 <DD>The background part of the Reverse Color is used to highlight
14527 the current line.
14528 If this would cause the text to be unreadable (because the foreground and
14529 background colors are the same) or if it would cause no change in the
14530 color of the index line, then the colors are flipped instead.
14531 <P>
14532 Some people think this works particularly well if you use different
14533 foreground colors to emphasize "interesting" lines,
14534 but always with the same Normal background color,
14535 and you use a different background color for the Reverse Color.
14536 </DD>
14538 <DT>reverse-bg-no-ambiguity</DT>
14539 <DD>As with the "reverse-fg" case, the "reverse-bg"
14540 rule may also result in a color that is exactly the same as the regular
14541 Reverse Color.
14542 Setting the option to this value removes that ambiguity.
14543 It is the same as the "reverse-bg" setting unless the resulting
14544 current line has the same color as the Reverse Color.
14545 In that case, the interesting line's colors are simply flipped (like in the
14546 default behavior).
14547 </DD>
14548 </DL>
14550 <P>
14552 <UL>
14553 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14554 </UL><P>
14555 <End of help on this topic>
14556 </BODY>
14557 </HTML>
14558 ====== h_config_expanded_addrbooks =====
14559 <HTML>
14560 <HEAD>
14561 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></TITLE>
14562 </HEAD>
14563 <BODY>
14564 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></H1>
14566 If multiple address books (either personal or global) are defined, and you
14567 wish to have them all expanded implicitly upon entering the ADDRESS BOOK
14568 screen, then set this feature. This feature will have no effect unless the
14569 feature
14570 <A HREF="h_config_combined_abook_display">"<!--#echo var="FEAT_combined-addrbook-display"-->"</A>
14571 is also set.
14572 <P>
14573 <End of help on this topic>
14574 </BODY>
14575 </HTML>
14576 ====== h_config_combined_folder_display =====
14577 <HTML>
14578 <HEAD>
14579 <TITLE>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></TITLE>
14580 </HEAD>
14581 <BODY>
14582 <H1>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></H1>
14584 This feature affects the folder list display screens.
14585 Normally, each folder list is viewed within its collection only. This
14586 command allows folder lists to be viewed within a single screen that
14587 combines the contents of all collections.
14589 <P>
14590 The way that commands work won't be changed.
14591 For example, the Select All command will select all of the folders in the
14592 current collection, not all of the entries in all of the collections.
14593 The WhereIs command will change a little.
14594 It will search through all of the folders in the current collection as well
14595 as all the folder in any other expanded collection.
14597 <P>
14598 When this feature is set, the setting of the feature
14599 <A HREF="h_config_expanded_folders">"<!--#echo var="FEAT_expanded-view-of-folders"-->"</A>
14600 has an effect.
14601 <P>
14602 <End of help on this topic>
14603 </BODY>
14604 </HTML>
14605 ====== h_config_combined_subdir_display =====
14606 <HTML>
14607 <HEAD>
14608 <TITLE>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></TITLE>
14609 </HEAD>
14610 <BODY>
14611 <H1>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></H1>
14613 This feature affects the Folder List screen when
14614 the
14615 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14616 feature is enabled. Normally, selecting a directory from the Folder
14617 List takes you into a new screen displaying only the contents of
14618 that directory.
14620 <P>
14621 Enabling this feature will cause the contents of the selected
14622 directory to be
14623 displayed within the boundaries of the "Collection" it
14624 is a part of. All previously displayed collections will remain
14625 in the screen.
14627 <P>
14628 The way that commands work won't be changed.
14629 For example, the Select All command will select all of the folders in the
14630 directory, as opposed to all of the entries in all of the collections.
14631 The WhereIs command will change a little.
14632 It will search through all of the folders in the current collection as well
14633 as all the folder in any other expanded collection.
14635 <P>
14636 <End of help on this topic>
14637 </BODY>
14638 </HTML>
14639 ====== h_config_separate_fold_dir_view =====
14640 <HTML>
14641 <HEAD>
14642 <TITLE>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></TITLE>
14643 </HEAD>
14644 <BODY>
14645 <H1>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></H1>
14647 This feature affects folder collections wherein a folder
14648 and directory can have the same name. By default, Alpine displays them
14649 only once, denoting that it is both a folder and directory by appending
14650 the folder name with the hierarchy character enclosed
14651 in square brackets.
14654 <P>
14655 Enabling this feature will cause Alpine to display such names
14656 separately marking the name representing a directory with a trailing
14657 hierarchy delimiter (typically the slash, "/", character).
14659 <P>
14660 The feature also alters the command set slightly. By default, the
14661 right-arrow descends into the directory, while hitting the Return key will
14662 cause the folder by that name to be opened.
14664 <P>
14665 With this feature set, the Return key will open the highlighted folder, or
14666 enter the highlighted directory.
14668 <P>
14669 <End of help on this topic>
14670 </BODY>
14671 </HTML>
14672 ====== h_config_expanded_folders =====
14673 <HTML>
14674 <HEAD>
14675 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></TITLE>
14676 </HEAD>
14677 <BODY>
14678 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></H1>
14680 If multiple folder collections are defined, and you
14681 wish to have them all expanded implicitly upon entering the FOLDER LIST
14682 screen, then set this feature. This feature will have no effect unless the
14683 feature
14684 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14685 is also set.
14686 <P>
14687 <End of help on this topic>
14688 </BODY>
14689 </HTML>
14690 ======= h_config_ldap_server =======
14691 <HTML>
14692 <HEAD>
14693 <TITLE>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
14694 </HEAD>
14695 <BODY>
14696 <H1>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
14697 This is the name of the host where an LDAP server is running.
14698 For redundancy, this may be a space-delimited set of server names, in which
14699 case the first server that answers is used.
14700 Each of the server names may be optionally followed by
14701 a colon and a port number.
14702 If this form is used then the port number configured below in the
14703 <EM>port</EM> field is not used.
14704 <P>
14705 To find out whether your organization has its own LDAP server,
14706 contact its computing support staff.
14707 <P><UL>
14708 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14709 </UL>
14710 <P>
14711 <End of help on this topic>
14712 </BODY>
14713 </HTML>
14714 ======= h_config_ldap_base =======
14715 <HTML>
14716 <HEAD>
14717 <TITLE>LDAP OPTION: Search-Base</TITLE>
14718 </HEAD>
14719 <BODY>
14720 <H1>LDAP OPTION: Search-Base</H1>
14722 This is the search base to be used on this server. It functions as a filter
14723 by restricting your searches in the LDAP server database
14724 to the specified contents of the specified fields. Without it, searches
14725 submitted to this directory server may fail. It might be something
14726 like:
14728 <PRE>
14729 O = <Your Organization Name>, C = US
14730 </PRE>
14731 or it might be blank.
14732 (Some LDAP servers actually ignore anything specified here.)
14733 <P>
14734 If in doubt what parameters you should specify here,
14735 contact the maintainers of the LDAP server.
14736 <P><UL>
14737 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14738 </UL>
14739 <P>
14740 <End of help on this topic>
14741 </BODY>
14742 </HTML>
14743 ======= h_config_ldap_port =======
14744 <HTML>
14745 <HEAD>
14746 <TITLE>LDAP OPTION: Port</TITLE>
14747 </HEAD>
14748 <BODY>
14749 <H1>LDAP OPTION: Port</H1>
14751 This is the TCP port number to be used with this LDAP server. If you leave
14752 this blank port 389 will be used.
14753 <P>
14754 <End of help on this topic>
14755 </BODY>
14756 </HTML>
14757 ======= h_config_ldap_nick =======
14758 <HTML>
14759 <HEAD>
14760 <TITLE>LDAP OPTION: Nickname</TITLE>
14761 </HEAD>
14762 <BODY>
14763 <H1>LDAP OPTION: Nickname</H1>
14765 This is a nickname to be used in displays. If you don't supply a
14766 nickname the server name
14767 (<A HREF="h_config_ldap_server">"<!--#echo var="VAR_ldap-servers"-->"</A>)
14768 will be used instead. This option is strictly for your convenience.
14769 <P>
14770 <End of help on this topic>
14771 </BODY>
14772 </HTML>
14773 ======= h_config_ldap_binddn =======
14774 <HTML>
14775 <HEAD>
14776 <TITLE>LDAP OPTION: Bind-DN</TITLE>
14777 </HEAD>
14778 <BODY>
14779 <H1>LDAP OPTION: Bind-DN</H1>
14781 You may need to authenticate to the LDAP server before you are able to use it.
14782 This is the Distinguished Name to bind to when authenticating to this server.
14783 Try leaving this blank until you know you need it.
14784 <P>
14785 Alpine only knows about LDAP Simple authentication.
14786 It does not attempt LDAP SASL authentication.
14787 The DN and password will be sent in the clear unless TLS encryption is
14788 being used on this connection.
14789 Because of this, you may want to set the LDAP feature
14790 <A HREF="h_config_ldap_opts_tls">"Attempt-TLS-On-Connection"</A>
14791 or the feature
14792 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
14793 if you are going to be providing a password.
14794 <P><UL>
14795 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14796 </UL>
14797 <P>
14798 <End of help on this topic>
14799 </BODY>
14800 </HTML>
14801 ======= h_config_ldap_opts_impl =======
14802 <HTML>
14803 <HEAD>
14804 <TITLE>LDAP FEATURE: Use-Implicitly-From-Composer</TITLE>
14805 </HEAD>
14806 <BODY>
14807 <H1>LDAP FEATURE: Use-Implicitly-From-Composer</H1>
14809 Set this to have lookups done to this server implicitly from the composer.
14810 If an address doesn't look like a fully-qualified address, it will be looked
14811 up in your address books, and if it doesn't match a nickname there, then it
14812 will be looked up on the LDAP servers that have this feature set.
14813 The lookups will also be done when using the address completion feature
14814 (TAB command) in the composer if any of the serves have this feature set.
14815 Also see the LDAP feature
14816 <A HREF="h_config_ldap_opts_rhs">"Lookup-Addrbook-Contents"</A>
14817 and the Setup/Config feature
14818 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
14819 <P>
14820 <End of help on this topic>
14821 </BODY>
14822 </HTML>
14823 ======= h_config_ldap_opts_tls =======
14824 <HTML>
14825 <HEAD>
14826 <TITLE>LDAP FEATURE: Attempt-TLS-On-Connection</TITLE>
14827 </HEAD>
14828 <BODY>
14829 <H1>LDAP FEATURE: Attempt-TLS-On-Connection</H1>
14831 When connecting to this server Alpine will attempt to use TLS encryption
14832 on the connection.
14833 Also see the closely related feature
14834 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
14835 <P>
14836 <End of help on this topic>
14837 </BODY>
14838 </HTML>
14839 ======= h_config_ldap_opts_tlsmust =======
14840 <HTML>
14841 <HEAD>
14842 <TITLE>LDAP FEATURE: Require-TLS-On-Connection</TITLE>
14843 </HEAD>
14844 <BODY>
14845 <H1>LDAP FEATURE: Require-TLS-On-Connection</H1>
14847 When connecting to this server Alpine will attempt to use TLS encryption
14848 on the connection.
14849 If the StartTLS operation fails then the connection will not be used.
14850 <P>
14851 <End of help on this topic>
14852 </BODY>
14853 </HTML>
14854 ====== h_config_ldap_opts_rhs =====
14855 <HTML>
14856 <HEAD>
14857 <TITLE>LDAP FEATURE: Lookup-Addrbook-Contents</TITLE>
14858 </HEAD>
14859 <BODY>
14860 <H1>LDAP FEATURE: Lookup-Addrbook-Contents</H1>
14862 Normally implicit LDAP lookups from the composer are done only for the
14863 strings you type in from the composer screen. In other words, you type in
14864 something in the To or CC field and press return, then the string is looked up.
14865 First that string is looked up in your address books. If a match is found
14866 there, then the results of that match are looked up again. If you place
14867 a string in your address book that you want to have looked up on the LDAP
14868 directory server, you need to turn on this feature. If you set this feature
14869 for a server, you almost always will also want to set the
14870 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
14871 feature. An example might serve to best illustrate this feature.
14872 <P>
14873 If an LDAP lookup of "William Clinton" normally returns an
14874 entry with an
14875 address of pres@whitehouse.gov, then you might put an entry in your address
14876 book that looks like:
14877 <P>
14878 <CENTER><SAMP>Nickname = bill</SAMP></CENTER><BR>
14879 <CENTER><SAMP>Address = "William Clinton"</SAMP></CENTER>
14880 <P>
14881 Now, when you type "bill" into an
14882 address field in the composer Alpine will
14883 find the "bill" entry in your address book.
14884 It will replace "bill" with
14885 "William Clinton".
14886 It will then search for an entry with that nickname
14887 in your address book and not find one. If this feature
14888 is set, Alpine will then attempt to lookup
14889 "William Clinton" on the LDAP server and find the entry with address
14890 pres@whitehouse.gov.
14891 <P>
14892 A better way to accomplish the same thing is probably to use the feature
14893 <A HREF="h_config_ldap_opts_ref">"Save-Search-Criteria-Not-Result"</A>.
14894 <P>
14895 <End of help on this topic>
14896 </BODY>
14897 </HTML>
14898 ====== h_config_ldap_opts_ref =====
14899 <HTML>
14900 <HEAD>
14901 <TITLE>LDAP FEATURE: Save-Search-Criteria-Not-Result</TITLE>
14902 </HEAD>
14903 <BODY>
14904 <H1>LDAP FEATURE: Save-Search-Criteria-Not-Result</H1>
14906 Normally when you save the results of an LDAP directory lookup to your
14907 address book the results of the lookup are saved. If this feature is set
14908 and the entry being saved was found on this directory server, then the
14909 search criteria is saved instead of the results of the search. When this
14910 address book entry is used in the future, instead of copying the results
14911 from the address book the directory lookup will be done again. This could
14912 be useful if the copied result might become stale because the data on
14913 the directory server changes (for example, the entry's email address changes).
14914 You probably don't want to set this feature if the server is at all slow or
14915 unreliable.
14916 <P>
14917 The way this actually works is that instead of saving the email address
14918 in your address book, Alpine saves enough information to look up the same
14919 directory entry again. In particular, it saves the server name and the
14920 distinguished name of the entry. It's possible that the server administrators
14921 might change the format of distinguished names on the server, or that the
14922 entry might be removed from the server. If Alpine notices this, you will be warned
14923 and a backup copy of the email address will be used. You may want to create
14924 a new entry in this case, since you will get the annoying warning every
14925 time you use the old entry. You may do that by Saving the entry to a new
14926 nickname in the same address book. You will be asked whether or not you
14927 want to use the backup email address.
14928 <P>
14929 A related feature in the Setup/Config screen is
14930 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
14931 <P>
14932 <End of help on this topic>
14933 </BODY>
14934 </HTML>
14935 ======= h_config_ldap_opts_nosub =======
14936 <HTML>
14937 <HEAD>
14938 <TITLE>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</TITLE>
14939 </HEAD>
14940 <BODY>
14941 <H1>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</H1>
14943 Spaces in your input are normally handled specially.
14944 Each space character is replaced
14945 by
14946 <P>
14947 <CENTER><SAMP>* <SPACE></SAMP></CENTER>
14948 <P>
14949 in the search query (but not by "* <SPACE> *").
14950 The reason this is done is so the input string
14951 <P>
14952 <CENTER><SAMP>Greg Donald</SAMP></CENTER>
14953 <P>
14954 (which is converted to "Greg* Donald") will match
14955 the names "Greg Donald",
14956 "Gregory Donald", "Greg F. Donald", and
14957 "Gregory F Donald"; but it won't match "Greg McDonald".
14958 If the "Search-Rule" you were using was "begins-with",
14959 then it would also match the name "Greg Donaldson".
14960 <P>
14961 Turning on this feature will disable this substitution.
14962 <P>
14963 <End of help on this topic>
14964 </BODY>
14965 </HTML>
14966 ====== h_config_ldap_searchtypes =======
14967 <HTML>
14968 <HEAD>
14969 <TITLE>LDAP OPTION: Search-Type</TITLE>
14970 </HEAD>
14971 <BODY>
14972 <H1>LDAP OPTION: Search-Type</H1>
14974 This affects the way that LDAP searches are done.
14975 In particular, this tells the server where to look for the string to be matched.
14976 If set to "name" then the string that is being searched for will
14977 be compared with the string in the
14978 "Name" field on the server
14979 (technically, it is the "commonname" field on the server).
14980 "Surname" means we're looking for a
14981 match in the "Surname" field on the
14982 server (actually the "sn" field).
14983 "Givenname" really is "givenname"
14984 and "email" is the electronic mail address (this is actually the field
14985 called "mail" or "electronicmail" on the server).
14986 The other three types are combinations of
14987 the types listed so far. "Name-or-email"
14988 means the string should appear
14989 in either the "name" field OR the "email" field.
14990 Likewise, "surname-or-givenname"
14991 means "surname" OR "givenname"
14992 and "sur-or-given-or-name-or-email" means the obvious thing.
14993 <P>
14994 This search TYPE is combined with the
14995 search <A HREF="h_config_ldap_searchrules">RULE</A>
14996 to form the actual search query.
14997 <P>
14998 The usual default value for this
14999 option is "sur-or-given-or-name-or-email".
15000 This type of search may be slow on some servers.
15001 Try "name-or-email", which is often
15002 faster, or just "name" if the performance seems to be a problem.
15003 <P>
15004 Some servers have been configured with different attribute names for
15005 these four fields.
15006 In other words, instead of using the attribute name "mail"
15007 for the email address field, the server might be configured to use something
15008 else, for example, "rfc822mail" or "internetemailaddress".
15009 Alpine can be configured to use these different attribute names by using
15010 the four configuration options:
15011 <P><UL>
15012 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
15013 </UL>
15014 <P><UL>
15015 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
15016 </UL>
15017 <P><UL>
15018 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
15019 </UL>
15020 <P><UL>
15021 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
15022 </UL>
15023 <P>
15024 <End of help on this topic>
15025 </BODY>
15026 </HTML>
15027 ====== h_config_ldap_searchrules =======
15028 <HTML>
15029 <HEAD>
15030 <TITLE>LDAP OPTION: Search-Rule</TITLE>
15031 </HEAD>
15032 <BODY>
15033 <H1>LDAP OPTION: Search-Rule</H1>
15035 This affects the way that LDAP searches are done.
15036 If set to "equals" then
15037 only exact matches count.
15038 "Contains" means that the string you type in
15039 is a substring of what you are matching against.
15040 "Begins-with" and "ends-with"
15041 mean that the string starts or ends with the string you type in.
15042 <P>
15043 Spaces in your input are normally handled specially, but you can turn that
15044 special handling off with the
15045 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
15046 feature.
15047 <P>
15048 The usual default value for this option is "begins-with".
15049 <P>
15050 <End of help on this topic>
15051 </BODY>
15052 </HTML>
15053 ======= h_config_ldap_email_attr =======
15054 <HTML>
15055 <HEAD>
15056 <TITLE>LDAP OPTION: EmailAttribute</TITLE>
15057 </HEAD>
15058 <BODY>
15059 <H1>LDAP OPTION: EmailAttribute</H1>
15061 This is the name of the attribute that is searched for when looking for
15062 an email address. The default value for this option is "mail" or
15063 "electronicmail".
15064 If the server you are using uses a different attribute name for the email
15065 address, put that attribute name here.
15066 <P>
15067 This will affect the search filter used if your Search-Type is one that
15068 contains a search for "email".
15069 It will also cause the attribute value matching this attribute name to be used
15070 as the email address when you look up an entry from the composer.
15071 <P>
15072 <End of help on this topic>
15073 </BODY>
15074 </HTML>
15075 ======= h_config_ldap_sn_attr =======
15076 <HTML>
15077 <HEAD>
15078 <TITLE>LDAP OPTION: SurnameAttribute</TITLE>
15079 </HEAD>
15080 <BODY>
15081 <H1>LDAP OPTION: SurnameAttribute</H1>
15083 This is the name of the attribute that is searched for when looking for
15084 the surname of the entry. The default value for this option is "sn".
15085 If the server you are using uses a different attribute name for the surname,
15086 put that attribute name here.
15087 This will affect the search filter used if your Search-Type is one that
15088 contains a search for "surname".
15089 <P>
15090 <End of help on this topic>
15091 </BODY>
15092 </HTML>
15093 ======= h_config_ldap_gn_attr =======
15094 <HTML>
15095 <HEAD>
15096 <TITLE>LDAP OPTION: GivennameAttribute</TITLE>
15097 </HEAD>
15098 <BODY>
15099 <H1>LDAP OPTION: GivennameAttribute</H1>
15101 This is the name of the attribute that is searched for when looking for
15102 the given name of the entry. The default value for this option is "givenname".
15103 If the server you are using uses a different attribute name for the given name,
15104 put that attribute name here.
15105 This will affect the search filter used if your Search-Type is one that
15106 contains a search for "givenname".
15107 <P>
15108 <End of help on this topic>
15109 </BODY>
15110 </HTML>
15111 ======= h_config_ldap_cn_attr =======
15112 <HTML>
15113 <HEAD>
15114 <TITLE>LDAP OPTION: NameAttribute</TITLE>
15115 </HEAD>
15116 <BODY>
15117 <H1>LDAP OPTION: NameAttribute</H1>
15119 This is the name of the attribute that is searched for when looking for
15120 the name of the entry. The default value for this option is "cn", which
15121 stands for common name.
15122 If the server you are using uses a different attribute name for the name,
15123 put that attribute name here.
15124 This will affect the search filter used if your Search-Type is one that
15125 contains a search for "name".
15126 <P>
15127 <End of help on this topic>
15128 </BODY>
15129 </HTML>
15130 ======= h_config_ldap_time =======
15131 <HTML>
15132 <HEAD>
15133 <TITLE>LDAP OPTION: Timelimit</TITLE>
15134 </HEAD>
15135 <BODY>
15136 <H1>LDAP OPTION: Timelimit</H1>
15138 This places a limit on the number of seconds the LDAP search will continue.
15139 The default is 30 seconds. A value of 0 means no limit. Note that some servers
15140 may place limits of their own on searches.
15141 <P>
15142 <End of help on this topic>
15143 </BODY>
15144 </HTML>
15145 ======= h_config_ldap_size =======
15146 <HTML>
15147 <HEAD>
15148 <TITLE>LDAP OPTION: Sizelimit</TITLE>
15149 </HEAD>
15150 <BODY>
15151 <H1>LDAP OPTION: Sizelimit</H1>
15153 This places a limit on the number of entries returned by the LDAP server.
15154 A value of 0 means no limit. The default is 0. Note that some servers
15155 may place limits of their own on searches.
15156 <P>
15157 <End of help on this topic>
15158 </BODY>
15159 </HTML>
15160 ======= h_config_ldap_cust =======
15161 <HTML>
15162 <HEAD>
15163 <TITLE>LDAP OPTION: Custom-Search-Filter</TITLE>
15164 </HEAD>
15165 <BODY>
15166 <H1>LDAP OPTION: Custom-Search-Filter</H1>
15168 This one is for advanced users only! If you define this, then the
15169 "Search-Type" and "Search-Rule" defined are both ignored.
15170 However, the feature
15171 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
15172 is still in effect.
15173 That is, the space substitution will take place even in a custom filter unless
15174 you disable it.
15175 <P>
15176 If your LDAP service stops working and you suspect it might be because
15177 of your custom filter, just delete this filter and try using the
15178 "Search-Type" and "Search-Rule" instead.
15179 Another option that sometimes causes trouble is the
15180 <A HREF="h_config_ldap_base">"Search-Base"</A> option.
15181 <P>
15182 This variable may be set to the string representation of an LDAP search
15183 filter (see RFC1960). In the places where you want the address string to be
15184 substituted in, put a '%s' in this filter string. Here are some examples:
15185 <P>
15186 A "Search-Type" of "name" with "Search-Rule" of "begins-with"
15187 is equivalent to the "Custom-Search-Filter"
15188 <PRE>
15189 (cn=%s*)
15190 </PRE>
15191 When you try to match against the string "string" the program replaces
15192 the "%s" with "string" (without the quotes). You may have multiple "%s"'s and
15193 they will all be replaced with the string. There is a limit of 10 "%s"'s.
15194 <P>
15195 A "Search-Type" of "name-or-email" with "Search-Rule"
15196 of "contains" is equivalent to
15197 <PRE>
15198 (|(cn=*%s*)(mail=*%s*))
15199 </PRE>
15200 <P>
15201 If your server uses a different attribute <EM>name</EM> than
15202 Alpine uses by default,
15203 (for example, it uses "rfc822mail" instead of "mail"),
15204 then you may be able to use one or more of the four attribute configuration
15205 options instead of defining a custom filter:
15206 <P><UL>
15207 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
15208 </UL>
15209 <P><UL>
15210 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
15211 </UL>
15212 <P><UL>
15213 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
15214 </UL>
15215 <P><UL>
15216 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
15217 </UL>
15218 <P>
15219 <End of help on this topic>
15220 </BODY>
15221 </HTML>
15222 ======= h_composer_abook_comment =======
15223 <HTML>
15224 <HEAD>
15225 <TITLE>Addressbook Comment Explained</TITLE>
15226 </HEAD>
15227 <BODY>
15228 This is a comment to help you remember what this entry is. The WhereIs
15229 command searches comments so that it is easier to find an entry with a comment
15230 you know about attached to it. This field is not used in the outgoing message.
15231 <P>
15232 Look <A HREF="h_edit_nav_cmds">here</A>
15233 to see the available Editing and Navigation commands.
15234 <P>
15235 <End of help on this topic>
15236 </BODY>
15237 </HTML>
15238 ======= h_composer_abook_addrs =======
15239 <HTML>
15240 <HEAD>
15241 <TITLE>Addressbook Lists</TITLE>
15242 </HEAD>
15243 <BODY>
15244 <H1>Addressbook Lists</H1>
15246 This is a list of addresses to send to when sending to this address book
15247 entry. Each member of the list may be an address or another nickname from
15248 any of your address books. If it is an address, it is OK to include the
15249 full name field as well as the electronic address portion of that address.
15250 For example, the following are all legitimate entries in this field:
15252 <DL><DT> </DT>
15253 <DD>john (a nickname in your address book)
15254 <DD>jdoe@some.domain
15255 <DD>John Doe <jdoe@some.domain>
15256 </DL>
15258 The addresses should be listed separated by commas, just like you would
15259 enter them from the composer.
15261 <P>
15263 The only difference between a distribution list and a simple entry with a
15264 single address, is that a distribution list has more than one address
15265 listed in the Addresses: field, whereas a simple personal entry has just
15266 one address.
15268 <P>
15270 For individual address book entries, if there is a full name in the
15271 Fullname: field (filling in the Fullname: field is not required), it is
15272 used. If the full name is specified in the Address: field and not in the
15273 Fullname: field, then the full name from the Address: field is used.
15275 <P>
15277 If you type the nickname of a distribution list from one of your address
15278 books in the Lcc: field, then the full name of that list is used in the
15279 To: field. If you put a list in the To: or Cc: fields, that list will be
15280 expanded into all of its addresses. If the list has a full name, then
15281 that will appear at the beginning of the addresses.
15283 <DL><DT> </DT>
15284 <DD>Sewing Club <john@somewhere>, nancy@something.else, Sal
15285 <sal@here.there>
15286 </DL>
15288 If the first address in the distribution list also has a full name, then
15289 the list full name and that full name are combined into something like the
15290 following:
15292 <DL><DT> </DT>
15293 <DD>Sewing Club -- John Smith <john@somewhere>
15294 </DL>
15297 If you specify a list via Lcc, the full name is used in the To: line. If
15298 you specify a list in the To: or Cc: fields, then it uses the same method
15299 as for individual entries for filling in the full name.
15301 <P>
15303 For help with editing and navigation commands, check the Help for the
15304 Nickname: field.
15306 <P>
15307 <End of help on this topic>
15308 </BODY>
15309 </HTML>
15310 ======= h_config_role_nick =======
15311 <HTML>
15312 <HEAD>
15313 <TITLE>Nickname Explained</TITLE>
15314 </HEAD>
15315 <BODY>
15316 <H1>Nickname Explained</H1>
15318 This is a nickname to help you.
15319 You should have a different nickname for each role you define.
15320 The nickname will be used in the SETUP ROLE RULES screen to allow you to
15321 pick a role to edit.
15322 It will also be used when you send a message to let you know you are
15323 sending with a different role than you use by default, and
15324 it will be useful for choosing a role when composing with the Role command
15325 or when composing with one of the Role Uses set to With Confirmation.
15326 This field is not used in the outgoing message.
15327 <P>
15328 Look <A HREF="h_edit_nav_cmds">here</A>
15329 to see the available Editing and Navigation commands.
15330 <P>
15331 <End of help on this topic>
15332 </BODY>
15333 </HTML>
15334 ======= h_config_role_comment =======
15335 <HTML>
15336 <HEAD>
15337 <TITLE>Comment Explained</TITLE>
15338 </HEAD>
15339 <BODY>
15340 <H1>Comment Explained</H1>
15342 This is a comment to help you.
15343 This comment does not play any functional role, it is simply an optional
15344 comment to help you remember what the rule is for.
15345 <P>
15346 Look <A HREF="h_edit_nav_cmds">here</A>
15347 to see the available Editing and Navigation commands.
15348 <P>
15349 <End of help on this topic>
15350 </BODY>
15351 </HTML>
15352 ======= h_config_other_nick =======
15353 <HTML>
15354 <HEAD>
15355 <TITLE>Nickname Explained</TITLE>
15356 </HEAD>
15357 <BODY>
15358 <H1>Nickname Explained</H1>
15360 This is a nickname to help you.
15361 You should have a different nickname for each rule you define.
15362 The nickname will be used in the SETUP OTHER RULES screen to allow you to
15363 pick a rule to edit.
15364 <P>
15365 Look <A HREF="h_edit_nav_cmds">here</A>
15366 to see the available Editing and Navigation commands.
15367 <P>
15368 <End of help on this topic>
15369 </BODY>
15370 </HTML>
15371 ======= h_config_score_nick =======
15372 <HTML>
15373 <HEAD>
15374 <TITLE>Nickname Explained</TITLE>
15375 </HEAD>
15376 <BODY>
15377 <H1>Nickname Explained</H1>
15379 This is a nickname to help you.
15380 You should have a different nickname for each scoring rule you define.
15381 The nickname will be used in the SETUP SCORING RULES screen to allow you to
15382 pick a rule to edit.
15383 <P>
15384 Look <A HREF="h_edit_nav_cmds">here</A>
15385 to see the available Editing and Navigation commands.
15386 <P>
15387 <End of help on this topic>
15388 </BODY>
15389 </HTML>
15390 ======= h_config_incol_nick =======
15391 <HTML>
15392 <HEAD>
15393 <TITLE>Nickname Explained</TITLE>
15394 </HEAD>
15395 <BODY>
15396 <H1>Nickname Explained</H1>
15398 This is a nickname to help you.
15399 You should have a different nickname for each color rule you define.
15400 The nickname will be used in the SETUP INDEX COLOR RULES screen to allow you to
15401 pick a rule to edit.
15402 <P>
15403 Look <A HREF="h_edit_nav_cmds">here</A>
15404 to see the available Editing and Navigation commands.
15405 <P>
15406 <End of help on this topic>
15407 </BODY>
15408 </HTML>
15409 ======= h_config_filt_nick =======
15410 <HTML>
15411 <HEAD>
15412 <TITLE>Nickname Explained</TITLE>
15413 </HEAD>
15414 <BODY>
15415 <H1>Nickname Explained</H1>
15417 This is a nickname to help you.
15418 You should have a different nickname for each filtering rule you define.
15419 The nickname will be used in the SETUP FILTERING RULES screen to allow you to
15420 pick a rule to edit.
15421 <P>
15422 Look <A HREF="h_edit_nav_cmds">here</A>
15423 to see the available Editing and Navigation commands.
15424 <P>
15425 <End of help on this topic>
15426 </BODY>
15427 </HTML>
15428 ======= h_config_score_topat =======
15429 <HTML>
15430 <HEAD>
15431 <TITLE>"To:" Pattern Explained</TITLE>
15432 </HEAD>
15433 <BODY>
15434 <H1>"To:" Pattern Explained</H1>
15436 Any text you enter as the "To pattern"
15437 will be compared to the recipients from the To: line of
15438 the message being scored.
15439 When the text you entered matches
15440 all or part of the To: line of a message, then the Score Value
15441 you have specified will be added to the score for the message.
15442 (Any other non-blank parts of the Pattern must match, too.)
15443 <P>
15445 You may enter a complete email address, part of an address, or a
15446 list of addresses or partial addresses.
15447 For example:
15448 <P>
15450 <PRE>
15451 To pattern = friend@public.com
15453 To pattern = rated.net
15455 To pattern = xxx@adults.com
15456 admin@msn.com
15457 fool@motleyfool.com
15458 </PRE>
15460 <P>
15461 Each of those are valid To patterns.
15462 <P>
15464 Messages match those patterns if any of the
15465 addresses in the To: line of the message contains the pattern.
15466 If the pattern is a list of patterns
15467 (like the last example above) then it is a match if any of the patterns in
15468 the list match any of the addresses in the To: line.
15469 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15470 present for a match.
15471 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15472 address2 must be present.
15473 That is exactly what using a list does.)
15474 <P>
15476 Some messages may be "bounced" to you, and will
15477 have a "Resent-To:" header line.
15478 If the message contains a Resent-To: line
15479 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15480 Alpine will look for
15481 matches to your "To patterns" there, and <EM>NOT</EM> in
15482 the original To: line.
15483 <P>
15485 When entering a pattern, you may choose an address from your address book
15486 with the "T" command.
15487 <P>
15489 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15490 "!" "toggle NOT" command.
15491 This changes the meaning of the To pattern so that it has the opposite meaning.
15492 It will be considered a match if there are no matches between the
15493 addresses in the To: line and the list of To patterns.
15494 <P>
15495 Don't make the mistake of putting the "!" in the data field for
15496 the pattern.
15497 For example, if you type the characters "!frizzle" into the To
15498 pattern, the pattern will look like:
15499 <P>
15500 <PRE>
15501 To pattern = !frizzle
15502 </PRE>
15503 <P>
15504 This means you want to match the 8 character sequence "!frizzle".
15505 In order to match messages that do not have "frizzle" in
15506 their To field, first type the characters "frizzle" followed
15507 by carriage return for the value of the To pattern, then negate it
15508 by typing the "!" command.
15509 It should end up looking like
15510 <P>
15511 <PRE>
15512 ! To pattern = frizzle
15513 </PRE>
15514 <P>
15515 You are not limited to using the six standard header patterns that are
15516 normally shown (To, From, Sender, Cc, News, and Subject).
15517 You may add any other header to a Pattern by
15518 using the "eXtraHdr" command to specify a different
15519 message header line; and then the Add or Change command to fill in
15520 a pattern for the new header line, just like you would for a standard header.
15521 <P>
15522 A technicality: Since comma is the character used to separate multiple
15523 values in a pattern field, you have to escape comma with a backslash (\) if
15524 you want to include a literal comma in the field.
15525 In other words, if you type a backslash followed by a comma it will
15526 be interpreted as a comma by Alpine, instead of as a separator between
15527 pattern values.
15528 All other backslashes are literal backslashes and should not be escaped.
15529 <P>
15530 Look "<A HREF="h_rule_patterns">here</A>"
15531 for more information on Patterns.
15532 <P>
15533 Look <A HREF="h_edit_nav_cmds">here</A>
15534 to see the available Editing and Navigation commands.
15535 <P>
15536 <End of help on this topic>
15537 </BODY>
15538 </HTML>
15539 ======= h_config_incol_topat =======
15540 <HTML>
15541 <HEAD>
15542 <TITLE>"To:" Pattern Explained</TITLE>
15543 </HEAD>
15544 <BODY>
15545 <H1>"To:" Pattern Explained</H1>
15547 Any text you enter as the "To pattern"
15548 will be compared to the recipients from the To: lines of
15549 the messages in the index.
15550 When the text you entered matches
15551 all or part of the To: line of a message, then the Index Line Color you have
15552 specified will be used for that line in the index.
15553 (Any other non-blank parts of the Pattern must match, too.)
15554 <P>
15556 You may enter a complete email address, part of an address, or a
15557 list of addresses or partial addresses.
15558 For example:
15559 <P>
15561 <PRE>
15562 To pattern = friend@public.com
15563 To pattern = rated.net
15564 To pattern = xxx@adults.com
15565 admin@msn.com
15566 fool@motleyfool.com
15567 </PRE>
15569 <P>
15570 Each of those are valid To patterns.
15571 <P>
15573 Messages match those patterns if any of the
15574 addresses in the To: line of the message contains the pattern.
15575 If the pattern is a list of patterns
15576 (like the last example above) then it is a match if any of the patterns in
15577 the list match any of the addresses in the To: line.
15578 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15579 present for a match.
15580 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15581 address2 must be present.
15582 That is exactly what using a list does.)
15583 <P>
15585 Some messages may be "bounced" to you, and will
15586 have a "Resent-To:" header line.
15587 If the message contains a Resent-To: line
15588 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15589 Alpine will look for
15590 matches to your "To patterns" there, and <EM>NOT</EM> in
15591 the original To: line.
15592 <P>
15594 When entering a pattern, you may choose an address from your address book
15595 with the "T" command.
15596 <P>
15598 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15599 "!" "toggle NOT" command.
15600 This changes the meaning of the To pattern so that it has the opposite meaning.
15601 It will be considered a match if there are no matches between the
15602 addresses in the To: line and the list of To patterns.
15603 <P>
15604 Don't make the mistake of putting the "!" in the data field for
15605 the pattern.
15606 For example, if you type the characters "!frizzle" into the To
15607 pattern, the pattern will look like:
15608 <P>
15609 <PRE>
15610 To pattern = !frizzle
15611 </PRE>
15612 <P>
15613 This means you want to match the 8 character sequence "!frizzle".
15614 In order to match messages that do not have "frizzle" in
15615 their To field, first type the characters "frizzle" followed
15616 by carriage return for the value of the To pattern, then negate it
15617 by typing the "!" command.
15618 It should end up looking like
15619 <P>
15620 <PRE>
15621 ! To pattern = frizzle
15622 </PRE>
15623 <P>
15625 You are not limited to using the six standard header patterns that are
15626 normally shown (To, From, Sender, Cc, News, and Subject).
15627 You may add any other header to a Pattern by
15628 using the "eXtraHdr" command to specify a different
15629 message header line; and then the Add or Change command to fill in
15630 a pattern for the new header line, just like you would for a standard header.
15631 <P>
15632 A technicality: Since comma is the character used to separate multiple
15633 values in a pattern field, you have to escape comma with a backslash (\) if
15634 you want to include a literal comma in the field.
15635 In other words, if you type a backslash followed by a comma it will
15636 be interpreted as a comma by Alpine, instead of as a separator between
15637 pattern values.
15638 All other backslashes are literal backslashes and should not be escaped.
15639 <P>
15640 Look "<A HREF="h_rule_patterns">here</A>"
15641 for more information on Patterns.
15642 <P>
15643 Look <A HREF="h_edit_nav_cmds">here</A>
15644 to see the available Editing and Navigation commands.
15645 <P>
15646 <End of help on this topic>
15647 </BODY>
15648 </HTML>
15649 ======= h_config_other_topat =======
15650 <HTML>
15651 <HEAD>
15652 <TITLE>"To:" Pattern Explained</TITLE>
15653 </HEAD>
15654 <BODY>
15655 <H1>"To:" Pattern Explained</H1>
15657 For some of the OTHER RULES actions, there is no message that is being
15658 compared against.
15659 If that is the case, then only the Current Folder Type is checked.
15660 In particular, this To pattern is ignored.
15661 Actions that fall into this category include both
15662 Sort Order and Index Format.
15663 <P>
15664 A technicality: Since comma is the character used to separate multiple
15665 values in a pattern field, you have to escape comma with a backslash (\) if
15666 you want to include a literal comma in the field.
15667 In other words, if you type a backslash followed by a comma it will
15668 be interpreted as a comma by Alpine, instead of as a separator between
15669 pattern values.
15670 All other backslashes are literal backslashes and should not be escaped.
15671 <P>
15672 Look "<A HREF="h_rule_patterns">here</A>"
15673 for more information on Patterns.
15674 <P>
15675 Look <A HREF="h_edit_nav_cmds">here</A>
15676 to see the available Editing and Navigation commands.
15677 <P>
15678 <End of help on this topic>
15679 </BODY>
15680 </HTML>
15681 ======= h_config_filt_topat =======
15682 <HTML>
15683 <HEAD>
15684 <TITLE>"To:" Pattern Explained</TITLE>
15685 </HEAD>
15686 <BODY>
15687 <H1>"To:" Pattern Explained</H1>
15689 Any text you enter as the "To pattern"
15690 will be compared to the recipients from the To: line of
15691 messages when Alpine opens folders.
15692 When the text you entered matches
15693 all or part of the To: line of a message, then the Filter Action you have
15694 specified will be carried out.
15695 (Any other non-blank parts of the Pattern must match, too.)
15696 <P>
15698 You may enter a complete email address, part of an address, or a
15699 list of addresses or partial addresses.
15700 For example:
15701 <P>
15703 <PRE>
15704 To pattern = friend@public.com
15705 To pattern = rated.net
15706 To pattern = xxx@adults.com
15707 admin@msn.com
15708 fool@motleyfool.com
15709 </PRE>
15711 <P>
15712 Each of those are valid To patterns.
15713 <P>
15715 Messages match those patterns if any of the
15716 addresses in the To: line of the message contains the pattern.
15717 If the pattern is a list of patterns
15718 (like the last example above) then it is a match if any of the patterns in
15719 the list match any of the addresses in the To: line.
15720 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15721 present for a match.
15722 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15723 address2 must be present.
15724 That is exactly what using a list does.)
15725 <P>
15727 Some messages may be "bounced" to you, and will
15728 have a "Resent-To:" header line.
15729 If the message contains a Resent-To: line
15730 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15731 Alpine will look for
15732 matches to your "To patterns" there, and <EM>NOT</EM> in
15733 the original To: line.
15734 <P>
15736 When entering a pattern, you may choose an address from your address book
15737 with the "T" command.
15738 <P>
15740 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15741 "!" "toggle NOT" command.
15742 This changes the meaning of the To pattern so that it has the opposite meaning.
15743 It will be considered a match if there are no matches between the
15744 addresses in the To: line and the list of To patterns.
15745 <P>
15746 Don't make the mistake of putting the "!" in the data field for
15747 the pattern.
15748 For example, if you type the characters "!frizzle" into the To
15749 pattern, the pattern will look like:
15750 <P>
15751 <PRE>
15752 To pattern = !frizzle
15753 </PRE>
15754 <P>
15755 This means you want to match the 8 character sequence "!frizzle".
15756 In order to match messages that do not have "frizzle" in
15757 their To field, first type the characters "frizzle" followed
15758 by carriage return for the value of the To pattern, then negate it
15759 by typing the "!" command.
15760 It should end up looking like
15761 <P>
15762 <PRE>
15763 ! To pattern = frizzle
15764 </PRE>
15765 <P>
15767 You are not limited to using the six standard header patterns that are
15768 normally shown (To, From, Sender, Cc, News, and Subject).
15769 You may add any other header to a Pattern by
15770 using the "eXtraHdr" command to specify a different
15771 message header line; and then the Add or Change command to fill in
15772 a pattern for the new header line, just like you would for a standard header.
15773 <P>
15774 A technicality: Since comma is the character used to separate multiple
15775 values in a pattern field, you have to escape comma with a backslash (\) if
15776 you want to include a literal comma in the field.
15777 In other words, if you type a backslash followed by a comma it will
15778 be interpreted as a comma by Alpine, instead of as a separator between
15779 pattern values.
15780 All other backslashes are literal backslashes and should not be escaped.
15781 <P>
15782 Look "<A HREF="h_rule_patterns">here</A>"
15783 for more information on Patterns.
15784 <P>
15785 Look <A HREF="h_edit_nav_cmds">here</A>
15786 to see the available Editing and Navigation commands.
15787 <P>
15788 <End of help on this topic>
15789 </BODY>
15790 </HTML>
15791 ======= h_config_role_topat =======
15792 <HTML>
15793 <HEAD>
15794 <TITLE>"To:" Pattern Explained</TITLE>
15795 </HEAD>
15796 <BODY>
15797 <H1>"To:" Pattern Explained</H1>
15799 Any text you enter as the "To pattern"
15800 will be compared to the recipients from the To: line of
15801 the message being replied to or forwarded.
15802 (Any other non-blank parts of the Pattern must match, too.)
15803 In the case of the Compose command, this pattern and the other header
15804 patterns are ignored.
15805 <P>
15807 You may enter a complete email address, part of an address, or a
15808 list of addresses or partial addresses.
15809 For example:
15810 <P>
15812 <PRE>
15813 To pattern = friend@public.com
15814 To pattern = rated.net
15815 To pattern = xxx@adults.com
15816 admin@msn.com
15817 fool@motleyfool.com
15818 </PRE>
15820 <P>
15821 Each of those are valid To patterns.
15822 <P>
15824 Messages match those patterns if any of the
15825 addresses in the To: line of the message contains the pattern.
15826 If the pattern is a list of patterns
15827 (like the last example above) then it is a match if any of the patterns in
15828 the list match any of the addresses in the To: line.
15829 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15830 present for a match.
15831 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15832 address2 must be present.
15833 That is exactly what using a list does.)
15834 <P>
15836 Some messages may be "bounced" to you, and will
15837 have a "Resent-To:" header line.
15838 If the message contains a Resent-To: line
15839 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15840 Alpine will look for
15841 matches to your "To patterns" there, and <EM>NOT</EM> in
15842 the original To: line.
15843 <P>
15845 When entering a pattern, you may choose an address from your address book
15846 with the "T" command.
15847 <P>
15849 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15850 "!" "toggle NOT" command.
15851 This changes the meaning of the To pattern so that it has the opposite meaning.
15852 It will be considered a match if there are no matches between the
15853 addresses in the To: line and the list of To patterns.
15854 <P>
15855 Don't make the mistake of putting the "!" in the data field for
15856 the pattern.
15857 For example, if you type the characters "!frizzle" into the To
15858 pattern, the pattern will look like:
15859 <P>
15860 <PRE>
15861 To pattern = !frizzle
15862 </PRE>
15863 <P>
15864 This means you want to match the 8 character sequence "!frizzle".
15865 In order to match messages that do not have "frizzle" in
15866 their To field, first type the characters "frizzle" followed
15867 by carriage return for the value of the To pattern, then negate it
15868 by typing the "!" command.
15869 It should end up looking like
15870 <P>
15871 <PRE>
15872 ! To pattern = frizzle
15873 </PRE>
15874 <P>
15876 You are not limited to using the six standard header patterns that are
15877 normally shown (To, From, Sender, Cc, News, and Subject).
15878 You may add any other header to a Pattern by
15879 using the "eXtraHdr" command to specify a different
15880 message header line; and then the Add or Change command to fill in
15881 a pattern for the new header line, just like you would for a standard header.
15882 <P>
15883 A technicality: Since comma is the character used to separate multiple
15884 values in a pattern field, you have to escape comma with a backslash (\) if
15885 you want to include a literal comma in the field.
15886 In other words, if you type a backslash followed by a comma it will
15887 be interpreted as a comma by Alpine, instead of as a separator between
15888 pattern values.
15889 All other backslashes are literal backslashes and should not be escaped.
15890 <P>
15891 Look "<A HREF="h_rule_patterns">here</A>"
15892 for more information on Patterns.
15893 <P>
15894 Look <A HREF="h_edit_nav_cmds">here</A>
15895 to see the available Editing and Navigation commands.
15896 <P>
15897 <End of help on this topic>
15898 </BODY>
15899 </HTML>
15900 ======= h_config_role_frompat =======
15901 <HTML>
15902 <HEAD>
15903 <TITLE>"From:" Pattern Explained</TITLE>
15904 </HEAD>
15905 <BODY>
15906 <H1>"From:" Pattern Explained</H1>
15908 This is just like the "To pattern" except that it is compared with
15909 the address in the From: line of the message
15910 instead of the addresses from the To: line.
15911 See the help for the To pattern for more information on header patterns.
15912 <P>
15913 Look "<A HREF="h_rule_patterns">here</A>"
15914 for more information on Patterns.
15915 <P>
15916 Look <A HREF="h_edit_nav_cmds">here</A>
15917 to see the available Editing and Navigation commands.
15918 <P>
15919 <End of help on this topic>
15920 </BODY>
15921 </HTML>
15922 ======= h_config_role_senderpat =======
15923 <HTML>
15924 <HEAD>
15925 <TITLE>"Sender:" Pattern Explained</TITLE>
15926 </HEAD>
15927 <BODY>
15928 <H1>"Sender:" Pattern Explained</H1>
15930 This is just like the "To pattern" except that it is compared with
15931 the address from the Sender: line of the message
15932 instead of the addresses from the To: line.
15933 See the help for the To pattern for more information on header patterns.
15934 <P>
15935 Look "<A HREF="h_rule_patterns">here</A>"
15936 for more information on Patterns.
15937 <P>
15938 Look <A HREF="h_edit_nav_cmds">here</A>
15939 to see the available Editing and Navigation commands.
15940 <P>
15941 <End of help on this topic>
15942 </BODY>
15943 </HTML>
15944 ======= h_config_role_ccpat =======
15945 <HTML>
15946 <HEAD>
15947 <TITLE>"Cc:" Pattern Explained</TITLE>
15948 </HEAD>
15949 <BODY>
15950 <H1>"Cc:" Pattern Explained</H1>
15952 This is just like the "To pattern" except that it is compared with
15953 the addresses from the Cc: line of the message
15954 instead of the addresses from the To: line.
15955 See the help for the To pattern for more information on header patterns.
15956 <P>
15957 Look "<A HREF="h_rule_patterns">here</A>"
15958 for more information on Patterns.
15959 <P>
15960 Look <A HREF="h_edit_nav_cmds">here</A>
15961 to see the available Editing and Navigation commands.
15962 <P>
15963 <End of help on this topic>
15964 </BODY>
15965 </HTML>
15966 ======= h_config_role_recippat =======
15967 <HTML>
15968 <HEAD>
15969 <TITLE>Recipient Pattern Explained</TITLE>
15970 </HEAD>
15971 <BODY>
15972 <H1>Recipient Pattern Explained</H1>
15974 This is just like the "To pattern" except that it is compared with
15975 the addresses from both the To: line and the Cc: line of the
15976 message instead of just the addresses from the To: line.
15977 In other words, it is considered a match if the pattern matches
15978 <EM>EITHER</EM> an address in the To: line <EM>OR</EM> an address
15979 in the Cc: line.
15980 (Notice that defining the Recipient pattern does not have the same
15981 effect as defining both the To and Cc patterns.
15982 Recipient is To <EM>OR</EM> Cc; not To <EM>AND</EM> Cc.
15983 It is equivalent to having two different rules;
15984 one with a To pattern and the other with the same Cc pattern.)
15985 <P>
15986 A technicality: Since comma is the character used to separate multiple
15987 values in a pattern field, you have to escape comma with a backslash (\) if
15988 you want to include a literal comma in the field.
15989 In other words, if you type a backslash followed by a comma it will
15990 be interpreted as a comma by Alpine, instead of as a separator between
15991 pattern values.
15992 All other backslashes are literal backslashes and should not be escaped.
15993 <P>
15994 Look "<A HREF="h_rule_patterns">here</A>"
15995 for more information on Patterns.
15996 <P>
15997 Look <A HREF="h_edit_nav_cmds">here</A>
15998 to see the available Editing and Navigation commands.
15999 <P>
16000 <End of help on this topic>
16001 </BODY>
16002 </HTML>
16003 ======= h_config_role_particpat =======
16004 <HTML>
16005 <HEAD>
16006 <TITLE>Participant Pattern Explained</TITLE>
16007 </HEAD>
16008 <BODY>
16009 <H1>Participant Pattern Explained</H1>
16011 This is just like the "To pattern" except that it is compared with
16012 the addresses from the From: line, the To: line, and the Cc: line of the
16013 message instead of just the addresses from the To: line.
16014 In other words, it is considered a match if the pattern matches
16015 <EM>EITHER</EM> an address in the From: line, <EM>OR</EM> an address
16016 in the To: line, <EM>OR</EM> an address in the Cc: line.
16017 (Notice that defining the Participant pattern does not have the same
16018 effect as defining all of the From, To, and Cc patterns.
16019 Participant is From <EM>OR</EM> To <EM>OR</EM> Cc; not
16020 From <EM>AND</EM> To <EM>AND</EM> Cc.
16021 It is equivalent to having three different rules;
16022 one with a From pattern, another with the same To pattern, and a third with
16023 the same Cc pattern.)
16024 <P>
16025 A technicality: Since comma is the character used to separate multiple
16026 values in a pattern field, you have to escape comma with a backslash (\) if
16027 you want to include a literal comma in the field.
16028 In other words, if you type a backslash followed by a comma it will
16029 be interpreted as a comma by Alpine, instead of as a separator between
16030 pattern values.
16031 All other backslashes are literal backslashes and should not be escaped.
16032 <P>
16033 Look "<A HREF="h_rule_patterns">here</A>"
16034 for more information on Patterns.
16035 <P>
16036 Look <A HREF="h_edit_nav_cmds">here</A>
16037 to see the available Editing and Navigation commands.
16038 <P>
16039 <End of help on this topic>
16040 </BODY>
16041 </HTML>
16042 ======= h_config_role_newspat =======
16043 <HTML>
16044 <HEAD>
16045 <TITLE>News Pattern Explained</TITLE>
16046 </HEAD>
16047 <BODY>
16048 <H1>News Pattern Explained</H1>
16050 If this pattern is non-blank, then for this rule to be considered a
16051 match, at least one of the newsgroups from
16052 the Newsgroups line of the message must match this pattern.
16053 If this pattern is a list of patterns, then at least one of the
16054 newsgroups must match at least one of the patterns.
16055 (Any other non-blank parts of the Pattern must match, too.)
16056 <P>
16057 It is possible to add a <EM>NOT</EM> to the News Pattern meaning with the
16058 "!" "toggle NOT" command.
16059 This changes the meaning of the News pattern so that it has the opposite meaning.
16060 It will be considered a match if there are no matches between the
16061 addresses in the Newsgroups: line and the list of News patterns.
16062 <P>
16063 Don't make the mistake of putting the "!" in the data field for
16064 the pattern.
16065 For example, if you type the characters "!frizzle" into the News
16066 pattern, the pattern will look like:
16067 <P>
16068 <PRE>
16069 News pattern = !frizzle
16070 </PRE>
16071 <P>
16072 This means you want to match the 8 character sequence "!frizzle".
16073 In order to match messages that do not have "frizzle" in
16074 their Newsgroups header, first type the characters "frizzle" followed
16075 by carriage return for the value of the News pattern, then negate it
16076 by typing the "!" command.
16077 It should end up looking like
16078 <P>
16079 <PRE>
16080 ! News pattern = frizzle
16081 </PRE>
16082 <P>
16083 A technicality: Since comma is the character used to separate multiple
16084 values in a pattern field, you have to escape comma with a backslash (\) if
16085 you want to include a literal comma in the field.
16086 In other words, if you type a backslash followed by a comma it will
16087 be interpreted as a comma by Alpine, instead of as a separator between
16088 pattern values.
16089 All other backslashes are literal backslashes and should not be escaped.
16090 <P>
16092 Look "<A HREF="h_rule_patterns">here</A>"
16093 for more information on Patterns.
16094 <P>
16095 Look <A HREF="h_edit_nav_cmds">here</A>
16096 to see the available Editing and Navigation commands.
16097 <P>
16098 <End of help on this topic>
16099 </BODY>
16100 </HTML>
16101 ======= h_config_role_subjpat =======
16102 <HTML>
16103 <HEAD>
16104 <TITLE>"Subject:" Pattern Explained</TITLE>
16105 </HEAD>
16106 <BODY>
16107 <H1>"Subject:" Pattern Explained</H1>
16109 This is similar to the other parts of the Pattern.
16110 It is compared with
16111 the contents from the Subject of the message.
16112 <P>
16113 Look "<A HREF="h_rule_patterns">here</A>"
16114 for more information on Patterns.
16115 <P>
16116 It is possible to add a <EM>NOT</EM> to the Subject Pattern meaning with the
16117 "!" "toggle NOT" command.
16118 This changes the meaning of the Subject pattern so that it has the opposite meaning.
16119 It will be considered a match if there are no matches between the
16120 text in the Subject: line and the list of Subject patterns.
16121 <P>
16123 If you wish to have a header pattern that is not one of the six standard
16124 header patterns, you may add it with the "eXtraHdr" command.
16125 <P>
16126 A technicality: Since comma is the character used to separate multiple
16127 values in a pattern field, you have to escape comma with a backslash (\) if
16128 you want to include a literal comma in the field.
16129 In other words, if you type a backslash followed by a comma it will
16130 be interpreted as a comma by Alpine, instead of as a separator between
16131 pattern values.
16132 All other backslashes are literal backslashes and should not be escaped.
16133 <P>
16134 Look <A HREF="h_edit_nav_cmds">here</A>
16135 to see the available Editing and Navigation commands.
16136 <P>
16137 <End of help on this topic>
16138 </BODY>
16139 </HTML>
16140 ======= h_config_role_alltextpat =======
16141 <HTML>
16142 <HEAD>
16143 <TITLE>AllText Pattern Explained</TITLE>
16144 </HEAD>
16145 <BODY>
16146 <H1>AllText Pattern Explained</H1>
16148 This is similar to the header patterns.
16149 Instead of comparing with text in a particular header field it
16150 is compared with all of the text in the message header and body.
16151 <P>
16152 It is possible to add a <EM>NOT</EM> to the AllText Pattern meaning with the
16153 "!" "toggle NOT" command.
16154 This changes the meaning of the AllText pattern so that it has the opposite meaning.
16155 It will be considered a match if there are no matches between the
16156 text of the message and the list of AllText patterns.
16157 <P>
16158 Don't make the mistake of putting the "!" in the data field for
16159 the pattern.
16160 For example, if you type the characters "!frizzle" into the AllText
16161 pattern, the pattern will look like:
16162 <P>
16163 <PRE>
16164 AllText pattern = !frizzle
16165 </PRE>
16166 <P>
16167 This means you want to match the 8 character sequence "!frizzle".
16168 In order to match messages that do not have "frizzle" in
16169 the text of the message, first type the characters "frizzle" followed
16170 by carriage return for the value of the AllText pattern, then negate it
16171 by typing the "!" command.
16172 It should end up looking like
16173 <P>
16174 <PRE>
16175 ! AllText pattern = frizzle
16176 </PRE>
16177 <P>
16178 It is possible that you may notice degraded performance when using
16179 AllText Patterns.
16180 <P>
16181 A technicality: Since comma is the character used to separate multiple
16182 values in a pattern field, you have to escape comma with a backslash (\) if
16183 you want to include a literal comma in the field.
16184 In other words, if you type a backslash followed by a comma it will
16185 be interpreted as a comma by Alpine, instead of as a separator between
16186 pattern values.
16187 All other backslashes are literal backslashes and should not be escaped.
16188 <P>
16189 Look "<A HREF="h_rule_patterns">here</A>"
16190 for more information on Patterns.
16191 <P>
16192 Look <A HREF="h_edit_nav_cmds">here</A>
16193 to see the available Editing and Navigation commands.
16194 <P>
16195 <End of help on this topic>
16196 </BODY>
16197 </HTML>
16198 ======= h_config_role_bodytextpat =======
16199 <HTML>
16200 <HEAD>
16201 <TITLE>BodyText Pattern Explained</TITLE>
16202 </HEAD>
16203 <BODY>
16204 <H1>BodyText Pattern Explained</H1>
16206 This is similar to the header patterns.
16207 Instead of comparing with text in a particular header field it
16208 is compared with all of the text in the message body.
16209 <P>
16210 It is possible to add a <EM>NOT</EM> to the BodyText Pattern meaning with the
16211 "!" "toggle NOT" command.
16212 This changes the meaning of the BodyText pattern so that it has the opposite meaning.
16213 It will be considered a match if there are no matches between the
16214 text of the body of the message and the list of BodyText patterns.
16215 <P>
16216 Don't make the mistake of putting the "!" in the data field for
16217 the pattern.
16218 For example, if you type the characters "!frizzle" into the BodyText
16219 pattern, the pattern will look like:
16220 <P>
16221 <PRE>
16222 BdyText pattern = !frizzle
16223 </PRE>
16224 <P>
16225 This means you want to match the 8 character sequence "!frizzle".
16226 In order to match messages that do not have "frizzle" in
16227 their BodyText, first type the characters "frizzle" followed
16228 by carriage return for the value of the BodyText pattern, then negate it
16229 by typing the "!" command.
16230 It should end up looking like
16231 <P>
16232 <PRE>
16233 ! BodyText pattern = frizzle
16234 </PRE>
16235 <P>
16236 It is possible that you may notice degraded performance when using
16237 BodyText Patterns.
16238 <P>
16239 A technicality: Since comma is the character used to separate multiple
16240 values in a pattern field, you have to escape comma with a backslash (\) if
16241 you want to include a literal comma in the field.
16242 In other words, if you type a backslash followed by a comma it will
16243 be interpreted as a comma by Alpine, instead of as a separator between
16244 pattern values.
16245 All other backslashes are literal backslashes and should not be escaped.
16246 <P>
16247 Look "<A HREF="h_rule_patterns">here</A>"
16248 for more information on Patterns.
16249 <P>
16250 Look <A HREF="h_edit_nav_cmds">here</A>
16251 to see the available Editing and Navigation commands.
16252 <P>
16253 <End of help on this topic>
16254 </BODY>
16255 </HTML>
16256 ======= h_config_role_charsetpat =======
16257 <HTML>
16258 <HEAD>
16259 <TITLE>Character Set Pattern Explained</TITLE>
16260 </HEAD>
16261 <BODY>
16262 <H1>Character Set Pattern Explained</H1>
16264 A message may use one or more character sets.
16265 This part of the Pattern matches messages that make use of
16266 certain specified character sets.
16267 It will be considered a match if a message uses any of the character
16268 sets in the list you give here.
16270 <P>
16271 When filling in a value for this field, you may use
16272 the "T" command, which presents you with a large list of
16273 possible character sets to choose from.
16274 You may also just type in the name of a character set, and it need not
16275 be one that Alpine knows about.
16277 <P>
16278 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
16279 GB2312) you may also use some shorthand names that Alpine provides.
16280 These names are more understandable shorthand names for sets of
16281 character set names.
16282 Two examples are "Cyrillic" and "Greek".
16283 Selecting one of these shorthand names is equivalent to selecting all of
16284 the character sets that make up the set.
16285 You can see all of these shorthand names and the lists of character sets
16286 they stand for by typing the "T" command.
16288 <P>
16289 For the purposes of this Pattern,
16290 Alpine will search through a message for all of the text parts and
16291 collect the character sets declared for each part.
16292 It will also look in the Subject line for a character set used there.
16293 Alpine does not actually look at the text of the message or the text
16294 of the Subject to determine if a declared character set is actually
16295 used, it looks only at the declarations themselves in the MIME part headers
16296 and in the Subject.
16298 <P>
16299 It is possible to add a <EM>NOT</EM> to the Character Set Pattern meaning with the
16300 "!" "toggle NOT" command.
16301 This changes the meaning of the Character Set pattern so that
16302 it has the opposite meaning.
16303 It will be considered a match if none of the character sets in the
16304 list are used in a message.
16305 <P>
16306 Don't make the mistake of putting the "!" in the data field for
16307 the pattern.
16308 For example, if you type the characters "!GB2312" into the
16309 Character Set pattern, the pattern will look like:
16310 <P>
16311 <PRE>
16312 Charset pattern = !GB2312
16313 </PRE>
16314 <P>
16315 This means you want to match the 7 character sequence "!GB2312".
16316 In order to match messages that do not have the
16317 character set "GB2312"
16318 set, first type the characters "GB2312" followed
16319 by carriage return for the value of the Character Set pattern, then negate it
16320 by typing the "!" command.
16321 It should end up looking like
16322 <P>
16323 <PRE>
16324 ! Charset pattern = GB2312
16325 </PRE>
16326 <P>
16327 A technicality: Since comma is the character used to separate multiple
16328 values in a pattern field, you have to escape comma with a backslash (\) if
16329 you want to include a literal comma in the field.
16330 In other words, if you type a backslash followed by a comma it will
16331 be interpreted as a comma by Alpine, instead of as a separator between
16332 pattern values.
16333 All other backslashes are literal backslashes and should not be escaped.
16334 <P>
16335 Look "<A HREF="h_rule_patterns">here</A>"
16336 for more information on Patterns.
16337 <P>
16338 Look <A HREF="h_edit_nav_cmds">here</A>
16339 to see the available Editing and Navigation commands.
16340 <P>
16341 <End of help on this topic>
16342 </BODY>
16343 </HTML>
16344 ======= h_config_role_keywordpat =======
16345 <HTML>
16346 <HEAD>
16347 <TITLE>Keyword Pattern Explained</TITLE>
16348 </HEAD>
16349 <BODY>
16350 <H1>Keyword Pattern Explained</H1>
16352 A folder may have user-defined keywords.
16353 These are similar to the Important flag, which the user may set using the
16354 Flag command.
16355 The difference is that the Important flag is always present for each folder.
16356 User-defined keywords are picked by the user.
16357 You may add new keywords by defining them in the
16358 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
16359 After you have added a potential keyword with the <!--#echo var="VAR_keywords"--> option,
16360 the Flag command may be used to set or clear the keyword on individual messages.
16361 If you have given a keyword a nickname when configuring it,
16362 that nickname may be used instead of the actual keyword.
16364 <P>
16365 When filling in a value for this field, it may be easiest to use
16366 the "T" command, which presents you with a list of the keywords
16367 you have defined to choose from.
16369 <P>
16370 This part of the Pattern matches messages with certain keywords set.
16371 It will be considered a match if a message has any of the keywords in the
16372 list set.
16373 A keyword that you have not defined using the
16374 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16375 will not be a match.
16377 <P>
16378 It is possible to add a <EM>NOT</EM> to the Keyword Pattern meaning with the
16379 "!" "toggle NOT" command.
16380 This changes the meaning of the Keyword pattern so that it has the opposite meaning.
16381 It will be considered a match if none of the keywords in the list are set
16382 for a message.
16383 A keyword that you have not defined using the
16384 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16385 will not be a match, so a <EM>NOT</EM> of that keyword does match.
16386 <P>
16387 Don't make the mistake of putting the "!" in the data field for
16388 the pattern.
16389 For example, if you type the characters "!frizzle" into the Keyword
16390 pattern, the pattern will look like:
16391 <P>
16392 <PRE>
16393 Keyword pattern = !frizzle
16394 </PRE>
16395 <P>
16396 This means you want to match the 8 character sequence "!frizzle".
16397 In order to match messages that do not have the keyword "frizzle"
16398 set, first type the characters "frizzle" followed
16399 by carriage return for the value of the Keyword pattern, then negate it
16400 by typing the "!" command.
16401 It should end up looking like
16402 <P>
16403 <PRE>
16404 ! Keyword pattern = frizzle
16405 </PRE>
16406 <P>
16407 A technicality: Since comma is the character used to separate multiple
16408 values in a pattern field, you have to escape comma with a backslash (\) if
16409 you want to include a literal comma in the field.
16410 In other words, if you type a backslash followed by a comma it will
16411 be interpreted as a comma by Alpine, instead of as a separator between
16412 pattern values.
16413 All other backslashes are literal backslashes and should not be escaped.
16414 <P>
16415 Look "<A HREF="h_rule_patterns">here</A>"
16416 for more information on Patterns.
16417 <P>
16418 Look <A HREF="h_edit_nav_cmds">here</A>
16419 to see the available Editing and Navigation commands.
16420 <P>
16421 <End of help on this topic>
16422 </BODY>
16423 </HTML>
16424 ======= h_config_role_arbpat =======
16425 <HTML>
16426 <HEAD>
16427 <TITLE>Extra Header Patterns Explained</TITLE>
16428 </HEAD>
16429 <BODY>
16430 <H1>Extra Header Patterns Explained</H1>
16432 The header patterns that come after the Participant pattern but before the
16433 AllText pattern are extra header patterns that you have added to a rule's
16434 Pattern. These are just like the other header patterns except that
16435 the contents of the particular header listed on the left hand side will
16436 be used for comparisons.
16437 <P>
16438 The "eXtraHdr" command may be used to add more of these
16439 header patterns to the rule you are editing.
16440 <P>
16441 The "RemoveHdr" command may be used to delete the highlighted
16442 extra header pattern from the rule you are editing.
16443 <P>
16444 It is possible to add a <EM>NOT</EM> to the Extra Header Pattern meaning with the
16445 "!" "toggle NOT" command.
16446 This changes the meaning of the pattern so that it has the opposite meaning.
16447 It will be considered a match if there are no matches between the
16448 text in the header line and the list of patterns.
16449 <P>
16450 Don't make the mistake of putting the "!" in the data field for
16451 the pattern.
16452 For example, if you type the characters "!frizzle" into the
16453 pattern, the pattern will look like:
16454 <P>
16455 <PRE>
16456 Xyz pattern = !frizzle
16457 </PRE>
16458 <P>
16459 This means you want to match the 8 character sequence "!frizzle".
16460 In order to match messages that do not have "frizzle" in
16461 their Xyz field, first type the characters "frizzle" followed
16462 by carriage return for the value of the pattern, then negate it
16463 by typing the "!" command.
16464 It should end up looking like
16465 <P>
16466 <PRE>
16467 ! Xyz pattern = frizzle
16468 </PRE>
16470 <P>
16471 A technicality: Since comma is the character used to separate multiple
16472 values in a pattern field, you have to escape comma with a backslash (\) if
16473 you want to include a literal comma in the field.
16474 In other words, if you type a backslash followed by a comma it will
16475 be interpreted as a comma by Alpine, instead of as a separator between
16476 pattern values.
16477 All other backslashes are literal backslashes and should not be escaped.
16478 <P>
16479 Look "<A HREF="h_rule_patterns">here</A>"
16480 for more information on Patterns.
16481 <P>
16482 Look <A HREF="h_edit_nav_cmds">here</A>
16483 to see the available Editing and Navigation commands.
16484 <P>
16485 <End of help on this topic>
16486 </BODY>
16487 </HTML>
16488 ======= h_config_role_cat_cmd =======
16489 <HTML>
16490 <HEAD>
16491 <TITLE>Categorizer Command Explained</TITLE>
16492 </HEAD>
16493 <BODY>
16494 <H1>Categorizer Command Explained</H1>
16496 This is a command that is run with its standard input set to the message
16497 being checked and its standard output discarded.
16498 The full directory path should be specified.
16499 The command will be run and then its exit status will be checked against
16500 the Exit Status Interval, which defaults to just the value zero.
16501 If the exit status of the command falls in the interval, it is considered
16502 a match, otherwise it is not a match.
16503 <P>
16505 This option may actually be a list of commands.
16506 The first one that exists and is executable is used.
16507 That makes it possible to use the same configuration with Unix Alpine and
16508 PC-Alpine.
16509 <P>
16511 If none of the commands in the list exists and is executable then the rule
16512 is <EM>not</EM> a match.
16513 If it is possible that the command may not exist, you should be careful
16514 to structure your rules so that nothing destructive
16515 happens when the command does not exist.
16516 For example, you might have a filter that filters away spam when there is
16517 a match but does nothing when there is not a match.
16518 That would cause no harm if the command didn't exist.
16519 However, if you have a filter that filters away spam when there is not
16520 a match and keeps it when there is a match, that would filter everything
16521 if the categorizer command didn't exist.
16522 <P>
16523 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
16524 setup for the bogofilter filter.
16526 <P>
16527 Look "<A HREF="h_rule_patterns">here</A>"
16528 for more information on Patterns.
16529 <P>
16530 Look <A HREF="h_edit_nav_cmds">here</A>
16531 to see the available Editing and Navigation commands.
16532 <P>
16533 <End of help on this topic>
16534 </BODY>
16535 </HTML>
16536 ======= h_config_role_cat_cmd_example =======
16537 <HTML>
16538 <HEAD>
16539 <TITLE>Categorizer Command Example</TITLE>
16540 </HEAD>
16541 <BODY>
16542 <H1>Categorizer Command Example</H1>
16544 Bogofilter
16545 (<A HREF="http://bogofilter.sourceforge.net/">http://bogofilter.sourceforge.net/</A>)
16546 is a mail filter that attempts to classify mail as spam or
16547 non-spam using statistical analysis of the message content.
16548 When run with no arguments and a message as standard input, it exits with
16549 exit status 0 if it thinks a message is spam and 1 if it thinks
16550 it is not spam.
16551 To use bogofilter as your Categorizer Command you would simply set Command to
16552 the pathname of the bogofilter program.
16553 For example,
16554 <P>
16555 <CENTER><SAMP>Command = /usr/local/bin/bogofilter</SAMP></CENTER>
16556 <P>
16557 Exit status of zero is what you are interested in, so you'd set the
16558 Exit Status Interval to
16559 <P>
16560 <CENTER><SAMP>Exit Status Interval = (0,0)</SAMP></CENTER>
16561 <P>
16563 In order to prevent downloading an entire huge message to check for spam, you
16564 might want to set the Character Limit to a few thousand characters (the
16565 assumption being that the spam will reveal itself in those characters)
16566 <P>
16567 <CENTER><SAMP>Character Limit = 50000</SAMP></CENTER>
16568 <P>
16570 You would probably use bogofilter in an Alpine Filter Rule, and have the action
16571 be to move the message to a spam folder.
16572 It would usually be wise to also check the "Message is Recent"
16573 part of the rule so that messages are only checked when they first arrive,
16574 and to restrict the Current Folder Type to just your INBOX.
16575 The reason for checking only Recent messages is to save the time it takes
16576 to run bogofilter on each message.
16577 As an experiment, you might start out by using this in an Indexcolor Rule
16578 instead of a Filter Rule.
16579 In that case, you probably wouldn't check the Recent checkbox.
16580 <P>
16581 The use described above assumes that you are somehow maintaining bogofilter's
16582 database of words associated with spam and non-spam messages.
16583 One way to start your database would be to select a bunch of spam messages
16584 in Alpine (you might Save spam messages to a special folder or use Alpine's
16585 Select command to select several) and then Apply
16586 (<A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>)
16587 a pipe command to the spam messages.
16588 For example, you could have a shell script or an alias
16589 called <EM>this_is_spam</EM>, which would simply be the command
16590 <P>
16591 <CENTER><SAMP>bogofilter -s</SAMP></CENTER>
16592 <P>
16594 It is probably best to use the pipe command's Raw Text, With Delimiter,
16595 and Free Output options,
16596 which are at the bottom of the screen when you type the pipe command.
16597 That's because bogofilter expects the raw message as input, and uses
16598 the Delimiters to tell when a new message starts.
16599 You would not need to use a separate pipe for each message, because
16600 bogofilter can handle multiple messages at once.
16601 <P>
16602 Similarly, you would select a group of non-spam messages
16603 and run them through a <EM>this_is_nonspam</EM> script
16604 that was something like
16605 <P>
16606 <CENTER><SAMP>bogofilter -n</SAMP></CENTER>
16607 <P>
16609 For the more adventurous, the next step might be to automate the upkeep of
16610 the bogofilter database.
16611 It might make more sense to have bogofilter be part of the delivery process,
16612 but it is also possible to do it entirely from within Alpine.
16613 Instead of using just plain "bogofilter" as the Categorizer Command,
16614 the "-u" argument will cause bogofilter to update the database.
16615 <P>
16616 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16617 <P>
16618 You'd want a couple more aliases or shell scripts called something like
16619 <EM>change_to_spam</EM>
16620 <P>
16621 <CENTER><SAMP>bogofilter -Ns</SAMP></CENTER>
16622 <P>
16623 and
16624 <EM>change_to_nonspam</EM>
16625 <P>
16626 <CENTER><SAMP>bogofilter -Sn</SAMP></CENTER>
16627 <P>
16628 When you run across a message in your INBOX that should have been
16629 classified as spam you would pipe it to the change_to_spam script, and
16630 when you run across a message in your spam folder that should have been
16631 left in your INBOX you would pipe it through change_to_nonspam.
16633 <P>
16634 There is a technical problem with this approach.
16635 Alpine may check your filters more than once.
16636 In particular, every time you start Alpine the filters will be checked for
16637 each message.
16638 Also, if you have any filters that depend on message state (New, Deleted, etc.)
16639 then Alpine will recheck for matches in messages that have changed state
16640 at the time you close the folder and before expunging.
16641 This is usually ok.
16642 However, in this case it is a problem because the command
16643 <P>
16644 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16645 <P>
16646 has the side effect of updating the database.
16647 So you run the risk of updating the database multiple times for a single
16648 message instead of updating it just once per message.
16649 There are some ways to work around this problem.
16650 What you need is a way to mark the message after you have run the filter.
16651 One way to mark messages is with the use of a keyword (say "Bogo").
16652 Besides having the filter move the message to a spam folder, also have it
16653 set the Bogo keyword.
16654 (Note that you will have to set up the "Bogo" keyword in the
16655 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in Setup/Config.)
16656 This rule can only set the Bogo keyword for the messages that it matches.
16657 You will also need to add a second rule right after this one that
16658 matches all the messages that don't have the Bogo keyword set
16659 (put the keyword in the Keyword pattern and toggle
16660 the Not with the ! command)
16661 and takes the action of setting it.
16662 Then change the "bogofilter -u" rule so that it won't be a match
16663 (and so it won't re-run the bogofilter command) if the keyword is already
16664 set.
16665 <P>
16666 What you will end up with is a rule that runs "bogofilter -u"
16667 on all messages that don't have the Bogo keyword set.
16668 This will have the side effect of inserting that message in the bogofilter
16669 database, match or not.
16670 If this rule matches (it is spam), the Bogo keyword will be set and
16671 the message will be moved to a spam folder.
16672 If it does not match, the
16673 following rule will mark the message by turning on the keyword.
16674 This second rule should be a non-terminating
16675 (<A HREF="h_config_filt_opts_nonterm">Dont-Stop-Even-if-Rule-Matches</A>)
16676 rule so that it doesn't stop the filtering process before the rest of
16677 your rules are consulted.
16679 <P>
16680 In summary, the first rule is something like
16681 <PRE>
16682 Nickname = bogofilter -u rule
16683 Current Folder Type =
16684 (*) Specific
16685 Folder = INBOX
16687 ! Keyword pattern = Bogo
16689 External Categorizer Commands =
16690 Command = /usr/local/bin/bogofilter -u
16691 Exit Status Interval = (0,0)
16692 Character Limit = <No Value Set: using "-1"> (optionally set this)
16694 Filter Action =
16695 (*) Move
16696 Folder = spam
16698 Set These Keywords = Bogo
16699 </PRE>
16700 <P>
16701 and the following rule is
16702 <PRE>
16703 Nickname = Set Bogo Keyword
16704 Current Folder Type =
16705 (*) Specific
16706 Folder = INBOX
16708 ! Keyword pattern = Bogo
16710 Filter Action =
16711 (*) Just Set Message Status
16713 Set These Keywords = Bogo
16715 Features =
16716 [X] dont-stop-even-if-rule-matches
16717 </PRE>
16718 <P>
16719 If it is possible for you to insert bogofilter in the delivery process instead
16720 of having it called from Alpine you could prevent having to wait
16721 for the bogofilter processing while you read your mail.
16722 You would have bogofilter add a header to the message at the time of delivery
16723 that identified it as spam or nonspam.
16724 With this method, you could avoid using a Categorizer Command while running Alpine,
16725 and just match on the header instead.
16726 You might still want to use the scripts mentioned above to initialize the
16727 database or to re-classify wrongly classified messages.
16729 <P>
16730 Finally, it isn't for the faint-hearted,
16731 but it is also possible to run bogofilter from PC-Alpine.
16732 You can install Cygwin from
16733 <A HREF="http://www.cygwin.com/">http://www.cygwin.com/</A> and
16734 then compile bogofilter in the cygwin environment, and run it from
16735 within PC-Alpine.
16736 You would end up with a Categorizer command that looked something like
16737 <P>
16738 <CENTER><SAMP>Command = C:\cygwin\bin\bogofilter.exe -u</SAMP></CENTER>
16739 <P>
16740 Note that the ".exe" extension is explicit,
16741 and that the bogofilter.exe executable should be in the same directory
16742 as cygwin1.dll.
16744 <P>
16745 <End of help on this topic>
16746 </BODY>
16747 </HTML>
16748 ======= h_config_role_cat_status =======
16749 <HTML>
16750 <HEAD>
16751 <TITLE>Exit Status Interval Explained</TITLE>
16752 </HEAD>
16753 <BODY>
16754 <H1>Exit Status Interval Explained</H1>
16756 The categorizer command is run and the result is the exit status of
16757 that command.
16758 If that exit status falls in the Exit Status Interval
16759 then it is considered a match, otherwise it is not a match.
16760 Of course for the entire rule to match, it must also be checked against
16761 the other defined parts of the Pattern.
16762 <P>
16763 The Exit Status Interval defaults to the single value 0 (zero).
16764 If you define it, it should be set to something like:
16765 <P>
16766 <CENTER><SAMP>(min_exit_value,max_exit_value)</SAMP></CENTER>
16767 <P>
16768 where "min_exit_value" and "max_exit_value" are integers.
16769 The special values "INF" and "-INF" may be used for large
16770 positive and negative integers.
16771 <P>
16772 Actually, a list of intervals may be used if you wish.
16773 A list would look like
16774 <P>
16775 <CENTER><SAMP>(min_exit_value1,max_exit_value1),(min_exit_value2,max_exit_value2),...</SAMP></CENTER>
16776 <P>
16777 When there is an Exit Status Interval defined, it is a match if the exit status
16778 of the categorizer command is contained in any of the intervals.
16779 The intervals include both endpoints.
16780 <P>
16781 The default interval is
16782 <P>
16783 <CENTER><SAMP>(0,0)</SAMP></CENTER>
16784 <P>
16785 and it matches only if the command exits with exit status equal to zero.
16787 <P>
16788 Look "<A HREF="h_rule_patterns">here</A>"
16789 for more information on Patterns.
16790 <P>
16791 Look <A HREF="h_edit_nav_cmds">here</A>
16792 to see the available Editing and Navigation commands.
16793 <P>
16794 <End of help on this topic>
16795 </BODY>
16796 </HTML>
16797 ======= h_config_role_cat_limit =======
16798 <HTML>
16799 <HEAD>
16800 <TITLE>Character Limit Explained</TITLE>
16801 </HEAD>
16802 <BODY>
16803 <H1>Character Limit Explained</H1>
16805 Setting this option makes it possible to limit how much of the message
16806 is made available to the categorizer command as input.
16807 The default value (-1) means that the entire message is fed to the
16808 command.
16809 A value of 0 (zero) means that only the headers of the message are
16810 made available.
16811 A positive integer means that the headers plus that many characters from
16812 the body of the message are passed to the categorizer.
16814 <P>
16815 Look "<A HREF="h_rule_patterns">here</A>"
16816 for more information on Patterns.
16817 <P>
16818 Look <A HREF="h_edit_nav_cmds">here</A>
16819 to see the available Editing and Navigation commands.
16820 <P>
16821 <End of help on this topic>
16822 </BODY>
16823 </HTML>
16824 ======= h_config_role_age =======
16825 <HTML>
16826 <HEAD>
16827 <TITLE>Age Interval Explained</TITLE>
16828 </HEAD>
16829 <BODY>
16830 <H1>Age Interval Explained</H1>
16832 The Age Interval, if defined, is part of the Pattern.
16833 If you use this, it should be set to something like:
16834 <P>
16835 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
16836 <P>
16837 where "min_age" and "max_age" are non-negative integers.
16838 The special value "INF" may be used for the max value.
16839 It represents infinity.
16840 <P>
16841 In rare cases it may be useful to use the more general form of the value,
16842 which is a comma-separated list of intervals.
16843 It would look something like:
16844 <P>
16845 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
16846 <P>
16847 When there is an Age Interval defined, it is a match if the age, in days, of
16848 the message is contained in the interval.
16849 The interval includes both endpoints.
16850 If the option is set to a list of intervals then it is a match if the
16851 age of the message is contained in any of the intervals.
16852 <P>
16853 Even though this option is called Age, it isn't actually
16854 the <EM>age</EM> of the message.
16855 Instead, it is how many days ago the message arrived in one of your folders.
16856 If the current time is a little past midnight, then a message that arrived
16857 just before midnight arrived yesterday, even though the message is only
16858 a few minutes old.
16859 By default, the date being used is not the date in the Date
16860 header of the message.
16861 It is the date that the message arrived in one of your folders.
16862 When you Save a message from one folder to another that arrival date
16863 is preserved.
16864 If you would like to use the date in the Date header that is possible.
16865 Turn on the option
16866 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
16867 near the bottom of the rule definition.
16868 <P>
16869 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
16870 The age interval
16871 <P>
16872 <CENTER><SAMP>(2,2)</SAMP></CENTER>
16873 <P>
16874 matches all messages that arrived on the day before yesterday.
16875 The interval
16876 <P>
16877 <CENTER><SAMP>(180,INF)</SAMP></CENTER>
16878 <P>
16879 matches all messages that arrived at least 180 days before today.
16880 The interval
16881 <P>
16882 <CENTER><SAMP>(0,1)</SAMP></CENTER>
16883 <P>
16884 matches all messages that arrived today or yesterday.
16886 <P>
16887 Look "<A HREF="h_rule_patterns">here</A>"
16888 for more information on Patterns.
16889 <P>
16890 Look <A HREF="h_edit_nav_cmds">here</A>
16891 to see the available Editing and Navigation commands.
16892 <P>
16893 <End of help on this topic>
16894 </BODY>
16895 </HTML>
16896 ======= h_config_role_size =======
16897 <HTML>
16898 <HEAD>
16899 <TITLE>Size Interval Explained</TITLE>
16900 </HEAD>
16901 <BODY>
16902 <H1>Size Interval Explained</H1>
16904 The Size Interval, if defined, is part of the Pattern.
16905 If you use this, it should be set to something like:
16906 <P>
16907 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
16908 <P>
16909 where "min_size" and "max_size" are non-negative integers.
16910 The special value "INF" may be used for the max value.
16911 It represents infinity.
16912 <P>
16913 In rare cases it may be useful to use the more general form of the value,
16914 which is a comma-separated list of intervals.
16915 It would look something like:
16916 <P>
16917 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
16918 <P>
16919 When there is a Size Interval defined, it is a match if the size of
16920 the message is contained in the interval.
16921 The interval includes both endpoints.
16922 If the option is set to a list of intervals then it is a match if the
16923 size of the message is contained in any of the intervals.
16924 <P>
16925 The size interval
16926 <P>
16927 <CENTER><SAMP>(10000,50000)</SAMP></CENTER>
16928 <P>
16929 matches all messages with sizes greater than or equal to 10000, and less
16930 than or equal to 50000.
16931 The interval
16932 <P>
16933 <CENTER><SAMP>(100000,INF)</SAMP></CENTER>
16934 <P>
16935 matches all messages with sizes greater than or equal to 100000.
16937 <P>
16938 Look "<A HREF="h_rule_patterns">here</A>"
16939 for more information on Patterns.
16940 <P>
16941 Look <A HREF="h_edit_nav_cmds">here</A>
16942 to see the available Editing and Navigation commands.
16943 <P>
16944 <End of help on this topic>
16945 </BODY>
16946 </HTML>
16947 ======= h_config_role_scorei =======
16948 <HTML>
16949 <HEAD>
16950 <TITLE>Score Interval Explained</TITLE>
16951 </HEAD>
16952 <BODY>
16953 <H1>Score Interval Explained</H1>
16955 The Score Interval, if defined, is part of the Pattern.
16956 If you use this, it should be set to something like:
16957 <P>
16958 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
16959 <P>
16960 where "min_score" and "max_score" are integers between
16961 -32000 and 32000.
16962 The special values "-INF" and "INF" may be used for
16963 the min and max values.
16964 These represent negative and positive infinity.
16965 <P>
16966 Actually, the value may be a list of intervals rather than just a
16967 single interval if that is useful.
16968 The elements of the list are separated by commas like:
16969 <P>
16970 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
16971 <P>
16972 When there is a Score Interval defined, it is a match if the score for
16973 the message is contained in any of the intervals.
16974 The intervals include both endpoints.
16975 The score for a message is calculated by looking at every scoring rule
16976 defined and adding up the Score Values for the rules that match the message.
16977 Scoring rules are created using the
16978 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
16980 <P>
16981 Look "<A HREF="h_rule_patterns">here</A>"
16982 for more information on Patterns.
16983 <P>
16984 Look <A HREF="h_edit_nav_cmds">here</A>
16985 to see the available Editing and Navigation commands.
16986 <P>
16987 <End of help on this topic>
16988 </BODY>
16989 </HTML>
16990 ======= h_config_role_fldr_type =======
16991 <HTML>
16992 <HEAD>
16993 <TITLE>Current Folder Type Explained</TITLE>
16994 </HEAD>
16995 <BODY>
16996 <H1>Current Folder Type Explained</H1>
16998 The Current Folder Type is part of the role's Pattern.
16999 It refers to the type of the currently open folder, which is the folder
17000 you were last looking at from the MESSAGE INDEX or MESSAGE TEXT screen.
17001 In order for a role to be considered a match, the current folder must
17002 be of the type you set here.
17003 The three types "Any", "News", and "Email" are
17004 all what you might think.
17005 <P>
17006 If the Current Folder Type for a role's Pattern is set to "News", for
17007 example, then
17008 that role will only be a match if the current folder is a newsgroup and
17009 the rest of the Pattern matches.
17010 The value "Specific" may be used when you want to limit the match
17011 to a specific folder (not just a specific type of folder), or to a list of
17012 specific folders.
17013 <P>
17014 In order to match a specific folder you Select the "Specific"
17015 button <EM>AND</EM> fill in
17016 the name (or list of names) of
17017 the folder in the "Folder List" field.
17018 If the current folder is any of the folders in the list, that is considered
17019 a match.
17020 The name of each folder in the list may be either "INBOX",
17021 the technical specification
17022 of the folder (like what appears in your configuration file) or, if the
17023 folder is one of your incoming folders, it may be the nickname you've given
17024 the folder.
17025 Here are a couple samples of specific folder names:
17026 <P>
17027 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17028 <P>
17029 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17030 <P>
17031 The easiest way to fill in the "Folder List" field is to use
17032 the "T" command that is available when the "Folder List" line is
17033 highlighted, or to use the "Take" command with the configuration
17034 feature
17035 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
17036 turned on.
17037 Note that you won't be able to edit the "Folder List" line unless the
17038 Current Folder Type is set to "Specific", and any value that
17039 "Folder List" has is ignored unless the type
17040 is set to "Specific".
17041 <P>
17042 When reading a newsgroup, there may be a performance penalty
17043 incurred when collecting the information necessary to check a Pattern.
17044 For this reason, the default Current Folder Type is set to "Email".
17045 <P>
17046 Look "<A HREF="h_rule_patterns">here</A>"
17047 for more information on Patterns.
17048 <P>
17049 Look <A HREF="h_edit_nav_cmds">here</A>
17050 to see the available Editing and Navigation commands.
17051 <P>
17052 <End of help on this topic>
17053 </BODY>
17054 </HTML>
17055 ======= h_config_filt_rule_type =======
17056 <HTML>
17057 <HEAD>
17058 <TITLE>Filter Action Explained</TITLE>
17059 </HEAD>
17060 <BODY>
17061 <H1>Filter Action Explained</H1>
17063 The Filter Action specifies the action to be taken when the Pattern is a
17064 match.
17065 It may be set to "Delete" "Move", or
17066 "Just Set Message Status".
17067 <P>
17068 If it is set to "Delete", then the message that matches the
17069 Pattern will be deleted from the open folder.
17070 <P>
17071 If it is set to "Move", then the name of the folder to which
17072 the matching message should be moved is given in the "Folder List" field on the
17073 next line of the screen.
17074 A list of folders separated by commas may be given, in which case the
17075 message will be copied to all of the folders in the list before it is
17076 deleted.
17077 <P>
17078 If it is set to neither of those two values (it is set to the value
17079 labeled "Just Set Message Status") then the message status
17080 setting will happen
17081 but the message will not be deleted or moved.
17082 <P>
17083 If you are Moving a message you may also set Message Status if you wish.
17084 <P>
17085 The easiest way to fill in the "Folder List" field is to use
17086 the T command that is available when the "Folder List" line is
17087 highlighted.
17088 Note that you won't be able to edit the "Folder List" line unless the
17089 Filter Action is set to "Move", and any value that
17090 "Folder List" has is ignored unless the type
17091 is set to "Move".
17092 <P>
17093 There are a few tokens that may be used in the names in the Folder List.
17094 They are all related to the date on which the filtering is taking place.
17095 The tokens are words surrounded by underscores.
17096 For example, if you want your filter to move messages to a folder named
17097 <P><CENTER><SAMP>abc-year-mon</SAMP></CENTER><P>
17098 you could specify the folder as
17099 <P><CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER><P>
17100 which would result in a file named something like
17101 <P><CENTER><SAMP>abc-2004-oct</SAMP></CENTER><P>
17102 or
17103 <P><CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER><P>
17104 which would result in a file named something like
17105 <P><CENTER><SAMP>abc-04-10</SAMP></CENTER><P>
17106 The available tokens are listed
17107 <A HREF="h_index_tokens">here</A>.
17108 <P>
17109 Look "<A HREF="h_rule_patterns">here</A>"
17110 for more information on Patterns.
17111 <P>
17112 Look <A HREF="h_edit_nav_cmds">here</A>
17113 to see the available Editing and Navigation commands.
17114 <P>
17115 <End of help on this topic>
17116 </BODY>
17117 </HTML>
17118 ======= h_config_score_fldr_type =======
17119 <HTML>
17120 <HEAD>
17121 <TITLE>Current Folder Type Explained</TITLE>
17122 </HEAD>
17123 <BODY>
17124 <H1>Current Folder Type Explained</H1>
17126 The Current Folder Type is part of the scoring rule's Pattern.
17127 It refers to the type of the folder that
17128 the message being scored is in.
17129 In order for a rule to be considered a match, the current folder must
17130 be of the type you set here.
17131 The three types "Any", "News", and "Email" are
17132 all what you might think.
17133 <P>
17134 If the Current Folder Type for a Pattern is set to "News", for
17135 example, then
17136 that Pattern will only match if the current folder is a newsgroup and
17137 the rest of the Pattern matches.
17138 The value "Specific" may be used when you want to limit the match
17139 to a specific folder (not just a specific type of folder), or to a list of
17140 specific folders.
17141 <P>
17142 In order to match a specific folder you Select the "Specific"
17143 button <EM>AND</EM> fill in
17144 the name (or list of names) of
17145 the folder in the "Folder List" field.
17146 If the current folder is any of the folders in the list, that is considered
17147 a match.
17148 The name of each folder in the list may be either "INBOX", the technical specification
17149 of the folder (like what appears in your configuration file) or, if the
17150 folder is one of your incoming folders, it may be the nickname you've given
17151 the folder.
17152 Here are a couple samples of specific folder names:
17153 <P>
17154 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17155 <P>
17156 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17157 <P>
17158 The easiest way to fill in the "Folder List" field is to use
17159 the T command that is available when the "Folder List" line is
17160 highlighted.
17161 Note that you won't be able to edit the "Folder List" line unless the
17162 Current Folder Type is set to "Specific", and any value that
17163 "Folder List" has is ignored unless the type
17164 is set to "Specific".
17165 <P>
17166 When reading a newsgroup, there may be a performance penalty
17167 incurred when collecting the information necessary to check a Pattern.
17168 For this reason, the default Current Folder Type is set to "Email".
17169 For example, if you have Index Line Coloring rules that have Score Intervals
17170 defined then the scores for all the visible messages will need to be calculated.
17171 If some of your Scoring rules have
17172 a Current Folder Type of
17173 "Any" or "News" this may cause the MESSAGE INDEX
17174 screen to draw more slowly when in a newsgroup.
17175 <P>
17176 Look "<A HREF="h_rule_patterns">here</A>"
17177 for more information on Patterns.
17178 <P>
17179 Look <A HREF="h_edit_nav_cmds">here</A>
17180 to see the available Editing and Navigation commands.
17181 <P>
17182 <End of help on this topic>
17183 </BODY>
17184 </HTML>
17185 ======= h_config_other_fldr_type =======
17186 <HTML>
17187 <HEAD>
17188 <TITLE>Current Folder Type Explained</TITLE>
17189 </HEAD>
17190 <BODY>
17191 <H1>Current Folder Type Explained</H1>
17193 The Current Folder Type is part of the rule's Pattern.
17194 It refers to the type of the folder being viewed.
17195 In order for a rule to be considered a match, the current folder must
17196 be of the type you set here.
17197 The three types "Any", "News", and "Email" are
17198 all what you might think.
17199 <P>
17200 If the Current Folder Type for a Pattern is set to "News", for
17201 example, then
17202 that Pattern will only match if the current folder is a newsgroup.
17203 The value "Specific" may be used when you want to limit the match
17204 to a specific folder (not just a specific type of folder), or to a list of
17205 specific folders.
17206 <P>
17207 In order to match a specific folder you Select the "Specific"
17208 button <EM>AND</EM> fill in
17209 the name (or list of names) of
17210 the folder in the "Folder List" field.
17211 If the current folder is any of the folders in the list, that is considered
17212 a match.
17213 The name of each folder in the list may be either "INBOX", the technical specification
17214 of the folder (like what appears in your configuration file) or, if the
17215 folder is one of your incoming folders, it may be the nickname you've given
17216 the folder.
17217 Here are a couple samples of specific folder names:
17218 <P>
17219 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17220 <P>
17221 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17222 <P>
17223 The easiest way to fill in the "Folder List" field is to use
17224 the T command that is available when the "Folder List" line is
17225 highlighted.
17226 Note that you won't be able to edit the "Folder List" line unless the
17227 Current Folder Type is set to "Specific", and any value that
17228 "Folder List" has is ignored unless the type
17229 is set to "Specific".
17230 <P>
17231 Look "<A HREF="h_rule_patterns">here</A>"
17232 for more information on Patterns.
17233 <P>
17234 Look <A HREF="h_edit_nav_cmds">here</A>
17235 to see the available Editing and Navigation commands.
17236 <P>
17237 <End of help on this topic>
17238 </BODY>
17239 </HTML>
17240 ======= h_config_incol_fldr_type =======
17241 <HTML>
17242 <HEAD>
17243 <TITLE>Current Folder Type Explained</TITLE>
17244 </HEAD>
17245 <BODY>
17246 <H1>Current Folder Type Explained</H1>
17248 The Current Folder Type is part of the Line Coloring rule's Pattern.
17249 It refers to the type of the folder for which the MESSAGE INDEX is
17250 being viewed.
17251 In order for a rule to be considered a match, the current folder must
17252 be of the type you set here.
17253 The three types "Any", "News", and "Email" are
17254 all what you might think.
17255 <P>
17256 If the Current Folder Type for a Pattern is set to "News", for
17257 example, then
17258 that Pattern will only match if the current folder is a newsgroup and
17259 the rest of the Pattern matches.
17260 The value "Specific" may be used when you want to limit the match
17261 to a specific folder (not just a specific type of folder), or to a list of
17262 specific folders.
17263 <P>
17264 In order to match a specific folder you Select the "Specific"
17265 button <EM>AND</EM> fill in
17266 the name (or list of names) of
17267 the folder in the "Folder List" field.
17268 If the current folder is any of the folders in the list, that is considered
17269 a match.
17270 The name of each folder in the list may be either "INBOX", the technical specification
17271 of the folder (like what appears in your configuration file) or, if the
17272 folder is one of your incoming folders, it may be the nickname you've given
17273 the folder.
17274 Here are a couple samples of specific folder names:
17275 <P>
17276 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17277 <P>
17278 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17279 <P>
17280 The easiest way to fill in the "Folder List" field is to use
17281 the T command that is available when the "Folder List" line is
17282 highlighted.
17283 Note that you won't be able to edit the "Folder List" line unless the
17284 Current Folder Type is set to "Specific", and any value that
17285 "Folder List" has is ignored unless the type
17286 is set to "Specific".
17287 <P>
17288 When reading a newsgroup, there may be a performance penalty
17289 incurred when collecting the information necessary to check a Pattern.
17290 For this reason, the default Current Folder Type is set to "Email".
17291 For example, a rule with a non-Normal Index Line Color
17292 and a Current Folder Type of
17293 "Any" or "News" may cause the MESSAGE INDEX
17294 screen to draw more slowly when in a newsgroup.
17295 <P>
17296 Look "<A HREF="h_rule_patterns">here</A>"
17297 for more information on Patterns.
17298 <P>
17299 Look <A HREF="h_edit_nav_cmds">here</A>
17300 to see the available Editing and Navigation commands.
17301 <P>
17302 <End of help on this topic>
17303 </BODY>
17304 </HTML>
17305 ======= h_config_filt_fldr_type =======
17306 <HTML>
17307 <HEAD>
17308 <TITLE>Current Folder Type Explained</TITLE>
17309 </HEAD>
17310 <BODY>
17311 <H1>Current Folder Type Explained</H1>
17313 The Current Folder Type is part of the Filtering rule's Pattern.
17314 It refers to the type of the folder for which the filtering is being done.
17315 In order for a rule to be considered a match, the current folder must
17316 be of the type you set here.
17317 The three types "Any", "News", and "Email" are
17318 all what you might think.
17319 <P>
17320 If the Current Folder Type for a Pattern is set to "News", for
17321 example, then
17322 that Pattern will only match if the current folder is a newsgroup and
17323 the rest of the Pattern matches.
17324 The value "Specific" may be used when you want to limit the match
17325 to a specific folder (not just a specific type of folder), or to a list of
17326 specific folders.
17327 <P>
17328 In order to match a specific folder you Select the "Specific"
17329 button <EM>AND</EM> fill in
17330 the name (or list of names) of
17331 the folder in the "Folder List" field.
17332 If the current folder is any of the folders in the list, that is considered
17333 a match.
17334 The name of each folder in the list may be either "INBOX", the technical specification
17335 of the folder (like what appears in your configuration file) or, if the
17336 folder is one of your incoming folders, it may be the nickname you've given
17337 the folder.
17338 Here are a couple samples of specific folder names:
17339 <P>
17340 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17341 <P>
17342 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17343 <P>
17344 The easiest way to fill in the "Folder List" field is to use
17345 the T command that is available when the "Folder List" line is
17346 highlighted.
17347 Note that you won't be able to edit the "Folder List" line unless the
17348 Current Folder Type is set to "Specific", and any value that
17349 "Folder List" has is ignored unless the type
17350 is set to "Specific".
17351 <P>
17352 When reading a newsgroup, there may be a performance penalty
17353 incurred when collecting the information necessary to check a Pattern.
17354 For this reason, the default Current Folder Type is set to "Email".
17355 For example, a rule with a Current Folder Type of either
17356 "Any" or "News" may cause the filtering to happen
17357 more slowly when opening a newsgroup.
17358 <P>
17359 Look "<A HREF="h_rule_patterns">here</A>"
17360 for more information on Patterns.
17361 <P>
17362 Look <A HREF="h_edit_nav_cmds">here</A>
17363 to see the available Editing and Navigation commands.
17364 <P>
17365 <End of help on this topic>
17366 </BODY>
17367 </HTML>
17368 ======= h_config_role_stat_imp =======
17369 <HTML>
17370 <HEAD>
17371 <TITLE>Message Important Status Explained</TITLE>
17372 </HEAD>
17373 <BODY>
17374 <H1>Message Important Status Explained</H1>
17376 This part of the Pattern may have one of three possible values.
17377 The default value is "Don't care", which matches any message.
17378 The other two values are "Yes", which means the message must be
17379 flagged "Important" in order to be a match; or "No", which
17380 means the message must <EM>not</EM> be flagged "Important" in order
17381 to be a match.
17382 <P>
17383 Look "<A HREF="h_rule_patterns">here</A>"
17384 for more information on Patterns.
17385 <P>
17386 Look <A HREF="h_edit_nav_cmds">here</A>
17387 to see the available Editing and Navigation commands.
17388 <P>
17389 <End of help on this topic>
17390 </BODY>
17391 </HTML>
17392 ======= h_config_role_stat_new =======
17393 <HTML>
17394 <HEAD>
17395 <TITLE>Message New Status Explained</TITLE>
17396 </HEAD>
17397 <BODY>
17398 <H1>Message New Status Explained</H1>
17400 This part of the Pattern may have one of three possible values.
17401 The default value is "Don't care", which matches any message.
17402 The other two values are "Yes", which means the message must be
17403 "New" in order to be a match; or "No", which
17404 means the message must <EM>not</EM> be "New" in order
17405 to be a match.
17406 "New" is the same as <EM>Unseen</EM> and not "New" is the
17407 same as <EM>Seen</EM>.
17408 <P>
17409 The nomenclature for New and Recent is a bit confusing:
17410 <P>
17411 New means that the message is Unseen.
17412 It could have been in your mailbox for a long time but if you haven't looked
17413 at it, it is still considered New.
17414 That matches the default Alpine index display that shows an N for such a
17415 message.
17416 <P>
17417 Recent means that the message was added to this folder since the last time
17418 you opened the folder.
17419 Alpine also shows an N by default for these types of messages.
17420 If you were to run two copies of Alpine that opened a folder one right after
17421 the other, a message would only show up as Recent in (at most) the first
17422 Alpine session.
17423 <P>
17424 Look "<A HREF="h_rule_patterns">here</A>"
17425 for more information on Patterns.
17426 <P>
17427 Look <A HREF="h_edit_nav_cmds">here</A>
17428 to see the available Editing and Navigation commands.
17429 <P>
17430 <End of help on this topic>
17431 </BODY>
17432 </HTML>
17433 ======= h_config_role_stat_recent =======
17434 <HTML>
17435 <HEAD>
17436 <TITLE>Message Recent Status Explained</TITLE>
17437 </HEAD>
17438 <BODY>
17439 <H1>Message Recent Status Explained</H1>
17441 This part of the Pattern may have one of three possible values.
17442 The default value is "Don't care", which matches any message.
17443 The other two values are "Yes", which means the message must be
17444 "Recent" in order to be a match; or "No", which
17445 means the message must <EM>not</EM> be "Recent" in order
17446 to be a match.
17447 "Recent" means that the message was added to the folder since
17448 the last time the folder was opened.
17449 If more than one mail client has the folder opened, the message will
17450 appear to be "Recent" to only one of the clients.
17451 <P>
17452 The nomenclature for New and Recent is a bit confusing:
17453 <P>
17454 New means that the message is Unseen.
17455 It could have been in your mailbox for a long time but if you haven't looked
17456 at it, it is still considered New.
17457 That matches the default Alpine index display that shows an N for such a
17458 message.
17459 <P>
17460 Recent means that the message was added to this folder since the last time
17461 you opened the folder.
17462 Alpine also shows an N by default for these types of messages.
17463 If you were to run two copies of Alpine that opened a folder one right after
17464 the other, a message would only show up as Recent in (at most) the first
17465 Alpine session.
17466 <P>
17467 Look "<A HREF="h_rule_patterns">here</A>"
17468 for more information on Patterns.
17469 <P>
17470 Look <A HREF="h_edit_nav_cmds">here</A>
17471 to see the available Editing and Navigation commands.
17472 <P>
17473 <End of help on this topic>
17474 </BODY>
17475 </HTML>
17476 ======= h_config_role_stat_del =======
17477 <HTML>
17478 <HEAD>
17479 <TITLE>Message Deleted Status Explained</TITLE>
17480 </HEAD>
17481 <BODY>
17482 <H1>Message Deleted Status Explained</H1>
17484 This part of the Pattern may have one of three possible values.
17485 The default value is "Don't care", which matches any message.
17486 The other two values are "Yes", which means the message must be
17487 marked "Deleted" in order to be a match; or "No", which
17488 means the message must <EM>not</EM> be marked "Deleted" in order
17489 to be a match.
17490 <P>
17491 If you are thinking of using this part of the Pattern as a way to prevent
17492 messages from being filtered more than once in a Filter Pattern,
17493 take a look at the Filter Option
17494 <A HREF="h_config_filt_opts_notdel">"Move-Only-if-Not-Deleted"</A>
17495 instead.
17496 It should work better than using this field since it will hide the filtered
17497 messages even if they are already Deleted.
17498 That option is at the bottom of the Filter configuration screen.
17499 <P>
17500 Look "<A HREF="h_rule_patterns">here</A>"
17501 for more information on Patterns.
17502 <P>
17503 Look <A HREF="h_edit_nav_cmds">here</A>
17504 to see the available Editing and Navigation commands.
17505 <P>
17506 <End of help on this topic>
17507 </BODY>
17508 </HTML>
17509 ======= h_config_role_stat_ans =======
17510 <HTML>
17511 <HEAD>
17512 <TITLE>Message Answered Status Explained</TITLE>
17513 </HEAD>
17514 <BODY>
17515 <H1>Message Answered Status Explained</H1>
17517 This part of the Pattern may have one of three possible values.
17518 The default value is "Don't care", which matches any message.
17519 The other two values are "Yes", which means the message must be
17520 marked "Answered" in order to be a match; or "No", which
17521 means the message must <EM>not</EM> be marked "Answered" in order
17522 to be a match.
17523 <P>
17524 Look "<A HREF="h_rule_patterns">here</A>"
17525 for more information on Patterns.
17526 <P>
17527 Look <A HREF="h_edit_nav_cmds">here</A>
17528 to see the available Editing and Navigation commands.
17529 <P>
17530 <End of help on this topic>
17531 </BODY>
17532 </HTML>
17533 ======= h_config_role_abookfrom =======
17534 <HTML>
17535 <HEAD>
17536 <TITLE>Address in Address Book Explained</TITLE>
17537 </HEAD>
17538 <BODY>
17539 <H1>Address in Address Book Explained</H1>
17541 This option gives you a way to match messages that contain an address
17542 that is in one of your address books.
17543 Only the simple entries in your address books are searched.
17544 Address book distribution lists are ignored!
17545 <P>
17546 This part of the Pattern may have one of five possible values.
17547 The default value is "Don't care", which matches any message.
17548 The value "Yes, in any address book" means at least one of the addresses
17549 from the message must be in at least one of your
17550 address books in order to be a match.
17551 The value "No, not in any address book"
17552 means none of the addresses may
17553 be in any of your address books in order to be a match.
17554 <P>
17555 The values "Yes, in specific address books" and
17556 "No, not in any of specific address books" are similar but instead
17557 of depending on all address books you are allowed to give a list of address
17558 books to look in.
17559 Usually this would be a single address book but it may be a
17560 list of address books as well.
17561 For each of these "specific" address book options you Select which
17562 of the Specific options you want (Yes or No) <EM>AND</EM> fill in the
17563 name (or list of names) of the address book in the
17564 "Abook List" field.
17565 The names to be used are those that appear in the ADDRESS BOOK LIST screen.
17566 The easiest way to fill in the Abook List field it to use
17567 the "T" command that is available when the "Abook List"
17568 line is highlighted.
17569 Note that you won't be able to edit the "Abook List" line unless the
17570 option is set to one of the two "Specific", values.
17571 <P>
17572 The addresses from the message that are checked for are determined by the
17573 setting you have for "Types of addresses to check for in address book".
17574 If you set this to "From" the From address from the message will
17575 be looked up in the address book.
17576 If you set it to "To" instead then the To addresses will be used.
17577 If any of the To addresses are in the address book then it is considered
17578 a match for "Yes" or not a match for "No".
17579 You could set it to both From and To, in which case all of the From and To
17580 addresses are used.
17581 The "Reply-To" and "Sender" cases are a little unusual.
17582 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
17583 exists or the From address if there is no Reply-To address.
17584 Same for the Sender address.
17585 <P>
17586 Look "<A HREF="h_rule_patterns">here</A>"
17587 for more information on Patterns.
17588 <P>
17589 Look <A HREF="h_edit_nav_cmds">here</A>
17590 to see the available Editing and Navigation commands.
17591 <P>
17592 <End of help on this topic>
17593 </BODY>
17594 </HTML>
17595 ======= h_config_inabook_from =======
17596 <HTML>
17597 <HEAD>
17598 <TITLE>From</TITLE>
17599 </HEAD>
17600 <BODY>
17601 <H1>From</H1>
17603 Setting the From line will cause the address from the From header line
17604 of the message to be checked for in the address book.
17605 <P>
17606 <End of help on this topic>
17607 </BODY>
17608 </HTML>
17609 ======= h_config_inabook_replyto =======
17610 <HTML>
17611 <HEAD>
17612 <TITLE>Reply-To</TITLE>
17613 </HEAD>
17614 <BODY>
17615 <H1>Reply-To</H1>
17617 Setting the Reply-To line will cause the address from the Reply-To header line
17618 of the message to be checked for in the address book.
17619 However, if there is no Reply-To header line in the message the From header
17620 line will be used instead.
17621 We understand this is dumb but we don't have an easy way around it.
17622 <P>
17623 <End of help on this topic>
17624 </BODY>
17625 </HTML>
17626 ======= h_config_inabook_sender =======
17627 <HTML>
17628 <HEAD>
17629 <TITLE>Sender</TITLE>
17630 </HEAD>
17631 <BODY>
17632 <H1>Sender</H1>
17634 Setting the Sender line will cause the address from the Sender header line
17635 of the message to be checked for in the address book.
17636 However, if there is no Sender header line in the message the From header
17637 line will be used instead.
17638 We understand this is dumb but we don't have an easy way around it.
17639 <P>
17640 <End of help on this topic>
17641 </BODY>
17642 </HTML>
17643 ======= h_config_inabook_to =======
17644 <HTML>
17645 <HEAD>
17646 <TITLE>To</TITLE>
17647 </HEAD>
17648 <BODY>
17649 <H1>To</H1>
17651 Setting the To line will cause the address from the To header line
17652 of the message to be checked for in the address book.
17653 <P>
17654 <End of help on this topic>
17655 </BODY>
17656 </HTML>
17657 ======= h_config_inabook_cc =======
17658 <HTML>
17659 <HEAD>
17660 <TITLE>CC</TITLE>
17661 </HEAD>
17662 <BODY>
17663 <H1>CC</H1>
17665 Setting the CC line will cause the address from the CC header line
17666 of the message to be checked for in the address book.
17667 <P>
17668 <End of help on this topic>
17669 </BODY>
17670 </HTML>
17671 ======= h_config_role_stat_8bitsubj =======
17672 <HTML>
17673 <HEAD>
17674 <TITLE>Raw 8-bit in Subject Explained</TITLE>
17675 </HEAD>
17676 <BODY>
17677 <H1>Raw 8-bit in Subject Explained</H1>
17679 It seems that lots of unwanted email contains unencoded 8-bit characters
17680 in the Subject.
17681 Normally, characters with the 8th bit set are not allowed in the Subject
17682 header unless they are MIME-encoded.
17683 This option gives you a way to match messages that have Subjects that
17684 contain unencoded 8-bit characters.
17685 <P>
17686 This part of the Pattern may have one of three possible values.
17687 The default value is "Don't care", which matches any message.
17688 The other two values are "Yes", which means the Subject of
17689 the message must contain unencoded 8-bit characters (characters with the
17690 most significant bit set)
17691 in order to be a match; or "No", which
17692 means the Subject must <EM>not</EM>
17693 contain unencoded 8-bit characters in order to be a match.
17694 <P>
17695 Look "<A HREF="h_rule_patterns">here</A>"
17696 for more information on Patterns.
17697 <P>
17698 Look <A HREF="h_edit_nav_cmds">here</A>
17699 to see the available Editing and Navigation commands.
17700 <P>
17701 <End of help on this topic>
17702 </BODY>
17703 </HTML>
17704 ======= h_config_role_bom =======
17705 <HTML>
17706 <HEAD>
17707 <TITLE>Beginning of Month</TITLE>
17708 </HEAD>
17709 <BODY>
17710 <H1>Beginning of Month</H1>
17712 This option gives you a limited ability to take different actions depending on whether
17713 this is the first time Alpine has been run this month or not.
17714 Though it would be nice to have such an option available, this is not the
17715 same as whether or not this is the first time a paricular folder has been
17716 opened this month.
17717 If you want some action (probably Filtering) to take place in a folder each
17718 month, then you will need to be sure that the folder is opened during the
17719 first Alpine session of the month in order for this option to be helpful.
17720 <P>
17721 This part of the Pattern may have one of three possible values.
17722 The default value is "Don't care", which matches any message.
17723 The other two values are "Yes", which means this is the first
17724 time Alpine has been run this month;
17725 or "No", which
17726 means this is not the first time Alpine has been run this month.
17727 <P>
17728 Look "<A HREF="h_rule_patterns">here</A>"
17729 for more information on Patterns.
17730 <P>
17731 Here are some technical details.
17732 The way that Alpine decides if it is the beginning of the month or not is
17733 to compare today's date with the date stored in the
17734 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
17735 variable in the config file.
17736 If the month of today's date is later than the month stored in the variable,
17737 then this is considered to be the first time you have run Alpine this month, and
17738 that turns the Beginning of the Month option on.
17739 <P>
17740 Look <A HREF="h_edit_nav_cmds">here</A>
17741 to see the available Editing and Navigation commands.
17742 <P>
17743 <End of help on this topic>
17744 </BODY>
17745 </HTML>
17746 ======= h_config_role_boy =======
17747 <HTML>
17748 <HEAD>
17749 <TITLE>Beginning of Year</TITLE>
17750 </HEAD>
17751 <BODY>
17752 <H1>Beginning of Year</H1>
17754 This option gives you a limited ability to take different actions depending on whether
17755 this is the first time Alpine has been run this year or not.
17756 Though it would be nice to have such an option available, this is not the
17757 same as whether or not this is the first time a paricular folder has been
17758 opened this year.
17759 If you want some action (probably Filtering) to take place in a folder each
17760 year, then you will need to be sure that the folder is opened during the
17761 first Alpine session of the year in order for this option to be helpful.
17762 <P>
17763 This part of the Pattern may have one of three possible values.
17764 The default value is "Don't care", which matches any message.
17765 The other two values are "Yes", which means this is the first
17766 time Alpine has been run this year;
17767 or "No", which
17768 means this is not the first time Alpine has been run this year.
17769 <P>
17770 Look "<A HREF="h_rule_patterns">here</A>"
17771 for more information on Patterns.
17772 <P>
17773 Here are some technical details.
17774 The way that Alpine decides if it is the beginning of the year or not is
17775 to compare today's date with the date stored in the
17776 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
17777 variable in the config file.
17778 If the year of today's date is later than the year stored in the variable,
17779 then this is considered to be the first time you have run Alpine this year, and
17780 that turns the Beginning of the Year option on.
17781 <P>
17782 Look <A HREF="h_edit_nav_cmds">here</A>
17783 to see the available Editing and Navigation commands.
17784 <P>
17785 <End of help on this topic>
17786 </BODY>
17787 </HTML>
17788 ======= h_config_role_inick =======
17789 <HTML>
17790 <HEAD>
17791 <TITLE>Initialize Values From Role Explained</TITLE>
17792 </HEAD>
17793 <BODY>
17794 <H1>Initialize Values From Role Explained</H1>
17796 This is a power user feature.
17797 You will usually want to leave this field empty.
17798 The value of this field is the nickname of another one of your roles.
17799 The Action values from that other role
17800 are used as the initial values of the Action items for this role.
17801 If you put something in any of the action fields for this role, that will
17802 override whatever was in the corresponding field of the initializer role.
17803 <P>
17804 You might use this field if the "Action" part of one of your roles
17805 is something you want to use in more than one role.
17806 Instead of filling in those action values again for each role, you
17807 may give the nickname of the role where the values are filled in.
17808 It's just a shortcut way to define Role Actions.
17809 <P>
17810 Here's an example to help explain how this works.
17811 Suppose you have a role with nickname "role1" and role1 has
17812 (among other things)
17813 <P>
17814 <CENTER><SAMP>Set Reply-To = The Pres <president@example.com></SAMP></CENTER>
17815 <P>
17816 set.
17817 If in "role2" you set "Initialize settings using role" to
17818 "role1", then role2 will inherit the Set Reply-To value
17819 from role1 by default (and any of the other inheritable action values
17820 that are set).
17821 So if role2 had
17822 <P>
17823 <CENTER><SAMP>Set Reply-To = <No Value Set></SAMP></CENTER>
17824 <P>
17825 defined, the Reply-To used with role2 would be "The Pres <president@example.com>"
17826 However, if role2 had
17827 <P>
17828 <CENTER><SAMP>Set Reply-To = VP <vicepresident@example.com></SAMP></CENTER>
17829 <P>
17830 defined, then the Reply-To used with role2 would be "VP <vicepresident@example.com>" instead.
17831 <P>
17832 If you wish,
17833 you may choose a nickname from your list of roles by using the
17834 "T" command.
17835 If the role you are using to initialize also has a role it initializes from,
17836 then that initialization happens first.
17837 That is, inheritance works as expected with the grandparent and
17838 great-grandparent (and so on) roles having the expected effect.
17839 <P>
17840 Look <A HREF="h_edit_nav_cmds">here</A>
17841 to see the available Editing and Navigation commands.
17842 <P>
17843 <End of help on this topic>
17844 </BODY>
17845 </HTML>
17846 ======= h_config_role_setfrom =======
17847 <HTML>
17848 <HEAD>
17849 <TITLE>Set From Explained</TITLE>
17850 </HEAD>
17851 <BODY>
17852 <H1>Set From Explained</H1>
17854 This describes part of the action to be taken if the Pattern for this
17855 role is a match.
17856 This field consists of a single address that will be used as the From
17857 address on the message you are sending.
17858 This should be a fully-qualified address like
17859 <P>
17860 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
17861 <P>
17862 or just
17863 <P>
17864 <CENTER><SAMP>user@domain</SAMP></CENTER>
17865 <P>
17866 If you wish,
17867 you may choose an address from your address book with the
17868 "T" command.
17869 <P>
17870 If this is left blank, then your normal From address will be used.
17871 <P>
17872 You may also find it useful to add the changed From address to the
17873 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
17874 configuration option.
17875 <P>
17876 Look <A HREF="h_edit_nav_cmds">here</A>
17877 to see the available Editing and Navigation commands.
17878 <P>
17879 <End of help on this topic>
17880 </BODY>
17881 </HTML>
17882 ======= h_config_role_setreplyto =======
17883 <HTML>
17884 <HEAD>
17885 <TITLE>Set Reply-To Explained</TITLE>
17886 </HEAD>
17887 <BODY>
17888 <H1>Set Reply-To Explained</H1>
17890 This describes part of the action to be taken if the Pattern for this
17891 role is a match.
17892 This field consists of a single address that will be used as the Reply-To
17893 address on the message you are sending.
17894 This may be a fully-qualified address like
17895 <P>
17896 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
17897 <P>
17898 or just
17899 <P>
17900 <CENTER><SAMP>user@domain</SAMP></CENTER>
17901 <P>
17902 If you wish,
17903 you may choose an address from your address book with the
17904 "T" command.
17905 <P>
17906 If this is left blank, then there won't be a Reply-To address unless
17907 you have configured one specially with the
17908 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>"
17909 configuration option.
17910 <P>
17911 Look <A HREF="h_edit_nav_cmds">here</A>
17912 to see the available Editing and Navigation commands.
17913 <P>
17914 <End of help on this topic>
17915 </BODY>
17916 </HTML>
17917 ======= h_config_role_setfcc =======
17918 <HTML>
17919 <HEAD>
17920 <TITLE>Set Fcc Explained</TITLE>
17921 </HEAD>
17922 <BODY>
17923 <H1>Set Fcc Explained</H1>
17925 This describes part of the action to be taken if the Pattern for this
17926 role is a match.
17927 This field consists of a single folder name that will be used in
17928 the Fcc field of the message you are sending.
17929 You may put anything here that you would normally type into the Fcc
17930 field from the composer.
17931 <P>
17932 In addition, an fcc of "" (two double quotation marks) means
17933 no Fcc.
17934 <P>
17935 A blank field here means that Alpine will use its normal rules for deciding
17936 the default value of the Fcc field.
17937 For many roles, perhaps most, it may make more sense for you to use the
17938 other Alpine facilities for setting the Fcc.
17939 In particular, if you want the Fcc to depend on who you are sending the
17940 message to then the <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
17941 is probably more useful.
17942 In that case, you would want to leave the Fcc field here blank.
17943 However, if you have a role that depends on who the message you are replying
17944 to was From, or what address that message was sent to;
17945 then it might make sense to set the Fcc for that role here.
17946 <P>
17947 If you wish,
17948 you may choose a folder from your folder collections by using the
17949 "T" command.
17950 <P>
17951 Look <A HREF="h_edit_nav_cmds">here</A>
17952 to see the available Editing and Navigation commands.
17953 <P>
17954 <End of help on this topic>
17955 </BODY>
17956 </HTML>
17957 ======= h_config_role_usesmtp =======
17958 <HTML>
17959 <HEAD>
17960 <TITLE>Use SMTP Server Explained</TITLE>
17961 </HEAD>
17962 <BODY>
17963 <H1>Use SMTP Server Explained</H1>
17965 This describes part of the action to be taken if the Pattern for this
17966 role is a match.
17967 If this field has a value, then it will be used as the SMTP server
17968 to send mail when this role is being used (unless the SMTP server variable
17969 is set in the system-wide fixed configuration file).
17970 It has the same semantics as the
17971 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
17972 variable in the Setup/Config screen.
17973 <P>
17974 If you are using this to post from home when you are at home and from
17975 work when you are at work you need to be careful about postponing messages.
17976 When you postpone a composition that was using a role with this variable
17977 set, the SMTP server list will be saved
17978 with the postponed composition.
17979 It cannot be changed later.
17980 Because of this, you may want to make this a list of SMTP servers
17981 with the preferred server at the front of the list and alternate servers
17982 later in the list.
17983 In your "Home" role you would put the home SMTP server first and
17984 the work SMTP server last.
17985 In your "Work" role you would put the work SMTP server first and
17986 the home SMTP server last.
17987 Then if you start a composition as "Work", postpone
17988 it, and then later resume it from home the work SMTP server will fail but
17989 the home SMTP server later in the list will succeed.
17990 <P>
17991 You may be able to simplify things by making the regular
17992 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
17993 variable in the Setup/Config screen a list instead of using roles
17994 to set the SMTP server.
17996 <P>
17997 Look <A HREF="h_edit_nav_cmds">here</A>
17998 to see the available Editing and Navigation commands.
17999 <P>
18000 <End of help on this topic>
18001 </BODY>
18002 </HTML>
18003 ======= h_config_role_usenntp =======
18004 <HTML>
18005 <HEAD>
18006 <TITLE>Use NNTP Server Explained</TITLE>
18007 </HEAD>
18008 <BODY>
18009 <H1>Use NNTP Server Explained</H1>
18011 This describes part of the action to be taken if the Pattern for this
18012 role is a match.
18013 If this field has a value, then it will be used as the NNTP server
18014 to post to newsgroups when this role is being used (unless the NNTP server
18015 variable
18016 is set in the system-wide fixed configuration file).
18017 It has the same semantics as the
18018 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
18019 variable in the Setup/Config screen.
18020 <P>
18021 This role setting can facilitate posting to the right nntp server for someone
18022 who reads news from various news sources. The feature
18023 <A HREF="h_config_predict_nntp_server">"<!--#echo var="FEAT_predict-nntp-server"-->"</A>
18024 allows for setting the correct <!--#echo var="VAR_nntp-server"--> without having to individually
18025 set a role for that <!--#echo var="VAR_nntp-server"-->, but for greater flexibility, setting
18026 nntp servers for roles may be more desirable for some people.
18027 <P>
18028 If you are using this to post from home when you are at home and from
18029 work when you are at work you need to be careful about postponing messages.
18030 When you postpone a composition that was using a role with this variable
18031 set, the NNTP server list will be saved
18032 with the postponed composition.
18033 It cannot be changed later.
18034 Because of this, you may want to make this a list of NNTP servers
18035 with the preferred server at the front of the list and alternate servers
18036 later in the list.
18037 In your "Home" role you would put the home NNTP server first and
18038 the work NNTP server last.
18039 In your "Work" role you would put the work NNTP server first and
18040 the home NNTP server last.
18041 Then if you start a composition as "Work", postpone
18042 it, and then later resume it from home the work NNTP server will fail but
18043 the home NNTP server later in the list will succeed.
18044 <P>
18045 You may be able to simplify things by making the regular
18046 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
18047 variable in the Setup/Config screen a list instead of using roles
18048 to set the NNTP server.
18050 <P>
18051 Look <A HREF="h_edit_nav_cmds">here</A>
18052 to see the available Editing and Navigation commands.
18053 <P>
18054 <End of help on this topic>
18055 </BODY>
18056 </HTML>
18057 ======= h_config_role_setotherhdr =======
18058 <HTML>
18059 <HEAD>
18060 <TITLE>Set Other Headers Explained</TITLE>
18061 </HEAD>
18062 <BODY>
18063 <H1>Set Other Headers Explained</H1>
18065 This describes part of the action to be taken if the Pattern for this
18066 role is a match.
18067 This field gives you a way to set values for headers besides
18068 "From" and "Reply-To".
18069 If you want to set either of those, use the specific
18070 "Set From" and "Set Reply-To" settings above.
18071 <P>
18072 This field is similar to the
18073 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" option.
18074 Each header you specify here must include the header tag
18075 ("To:", "Approved:", etc.)
18076 and may optionally include a value for that header.
18077 In order to see these headers when you compose using this role you
18078 must use the rich header
18079 <!--chtml if pinemode="function_key"-->(F5)
18080 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
18081 Here's an example that shows how you might set the To address.
18082 <P>
18083 <CENTER><SAMP>Set Other Hdrs = To: Full Name <user@domain></SAMP></CENTER>
18084 <P>
18085 Headers set in this way are different from headers set with the
18086 <!--#echo var="VAR_customized-hdrs"--> option in that the value you give for a header here
18087 will replace any value that already exists.
18088 For example, if you are Replying to a message there will already be at
18089 least one address in the To header (the address you are Replying to).
18090 However, if you Reply using a role that sets the To header, that role's
18091 To header value will be used instead.
18092 <P>
18093 Limitation: Because commas are used to separate the list of
18094 Other Headers, it is not possible to have the value of a
18095 header contain a comma;
18096 nor is there currently an "escape" mechanism provided
18097 to make this work.
18098 <P>
18099 Look <A HREF="h_edit_nav_cmds">here</A>
18100 to see the available Editing and Navigation commands.
18101 <P>
18102 <End of help on this topic>
18103 </BODY>
18104 </HTML>
18105 ======= h_config_role_setlitsig =======
18106 <HTML>
18107 <HEAD>
18108 <TITLE>Set Literal Signature Explained</TITLE>
18109 </HEAD>
18110 <BODY>
18111 <H1>Set Literal Signature Explained</H1>
18113 This describes part of the action to be taken if the Pattern for this
18114 role is a match.
18115 This field contains the actual text for your signature, as opposed to
18116 the name of a file containing your signature.
18117 If this is defined it takes precedence over any value set in the
18118 "Set Signature" field.
18119 <P>
18120 This is simply a different way to store the signature.
18121 The signature is stored inside your Alpine configuration file instead of in
18122 a separate file.
18123 Tokens work the same way they do with
18124 <A HREF="h_config_role_setsig">Set Signature</A>, so refer to the
18125 help text there for more information.
18126 <P>
18128 The two character sequence \n (backslash followed by
18129 the character n) will be used to signify a line-break in your signature.
18130 You don't have to enter the \n, but it will be visible in the
18131 CHANGE THIS ROLE RULE window after you are done editing the signature.
18132 <P>
18133 Look <A HREF="h_edit_nav_cmds">here</A>
18134 to see the available Editing and Navigation commands.
18135 <P>
18136 <End of help on this topic>
18137 </BODY>
18138 </HTML>
18139 ======= h_config_role_setsig =======
18140 <HTML>
18141 <HEAD>
18142 <TITLE>Set Signature Explained</TITLE>
18143 </HEAD>
18144 <BODY>
18145 <H1>Set Signature Explained</H1>
18147 This describes part of the action to be taken if the Pattern for this
18148 role is a match.
18149 <P>
18150 If either the default <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A>
18151 option from Setup/Config
18152 or the "Set LiteralSig" option for this role are defined,
18153 then this option will be ignored.
18154 You can tell that that is the case because the value of this
18155 option will show up as
18156 <P>
18157 <CENTER><SAMP><Ignored: using LiteralSig instead></SAMP></CENTER>
18158 <P>
18159 You may either use all Literal Signatures (signatures stored in your
18160 configuration file) throughout Alpine, or all signature files.
18161 You can't mix the two.
18162 <P>
18163 This field consists of a filename that will be used as the signature
18164 file when using this role.
18165 <P>
18166 If the filename is followed by a vertical bar (|) then instead
18167 of reading the contents of the file the file is assumed to be a
18168 program that will produce the text to be used on its standard output.
18169 The program can't have any arguments and doesn't receive any input from Alpine,
18170 but the rest of the processing works as if the contents came from a file.
18171 <P>
18172 Instead of storing the data in a local file, the
18173 signature data may be stored remotely in an IMAP folder.
18174 In order to do this,
18175 you must use a remote name for the signature.
18176 A remote signature name might look like:
18177 <P>
18178 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
18179 <P>
18181 The syntax used here is the same as the syntax used for a remote
18182 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
18183 Note that you may not access an existing signature file remotely,
18184 you have to create a new <EM>folder</EM> that contains the signature data.
18185 If the name you use here for the signature data is a remote name, then when
18186 you edit the file using the "F" command the data will
18187 be saved remotely in the folder.
18188 You aren't required to do anything special to create the folder, it
18189 gets created if you use a remote name.
18191 <P>
18192 If you type "F" you may edit the contents of the file (as opposed to
18193 the name of the file) you have specified.
18194 If you type "T" you may use a browser to choose an existing filename.
18195 <P>
18196 Besides containing regular text, a signature file may also
18197 contain (or a signature program may produce) tokens that are replaced with text
18198 that depends on the message you are replying to or forwarding.
18199 The tokens all look like _word_ (a word surrounded by underscores).
18200 For example, if the token
18201 <P>
18202 <CENTER><SAMP>_DATE_</SAMP></CENTER>
18203 <P>
18204 is included in the text of the signature file, then when you reply to
18205 or forward a message, the token will be replaced with the actual date
18206 the message you are replying to or forwarding was sent.
18207 <P>
18208 If you use a role that has a signature file for a plain composition
18209 (that is, not a reply or forward) then there is no original message, so
18210 any tokens that depend on the message will be replaced with nothing.
18211 So if you want a signature file to be useful for new compositions it
18212 shouldn't include any of the tokens that depend on the message being
18213 replied to or forwarded.
18214 <P>
18215 The list of available tokens is
18216 <A HREF="h_index_tokens">here</A>.
18217 <P>
18218 Actually, for the adventurous, there is a way to conditionally include text based
18219 on whether or not a token would result in specific replacement text.
18220 For example, you could include some text based on whether or not
18221 the _NEWS_ token would result in any newsgroups if it was used.
18222 It's explained in detail
18223 <A HREF="h_reply_token_conditionals">here</A>.
18224 <P>
18225 In the very unlikely event that you want to include a literal token in
18226 a signature file, you must precede it with a backslash character.
18227 For example, to include the literal text _DATE_ you must actually use
18228 \_DATE_.
18229 It is not possible to have a literal backslash followed by an expanded token.
18230 <P>
18231 A blank field here means that Alpine will use its normal rules for deciding
18232 which file (if any) to use for the signature file.
18233 <P>
18234 An alternate method for storing the signature is available in
18235 <A HREF="h_config_role_setlitsig">Set Literal Signature</A>.
18236 <P>
18237 Look <A HREF="h_edit_nav_cmds">here</A>
18238 to see the available Editing and Navigation commands.
18239 <P>
18240 <End of help on this topic>
18241 </BODY>
18242 </HTML>
18243 ======= h_config_role_settempl =======
18244 <HTML>
18245 <HEAD>
18246 <TITLE>Set Template Explained</TITLE>
18247 </HEAD>
18248 <BODY>
18249 <H1>Set Template Explained</H1>
18251 This describes part of the action to be taken if the Pattern for this
18252 role is a match.
18253 This field consists of a filename that will be used as the template
18254 file when using this role.
18255 The template file is a file that is included at the top of the message you
18256 are composing.
18257 <P>
18258 If the filename is followed by a vertical bar (|) then instead
18259 of reading the contents of the file the file is assumed to be a
18260 program that will produce the text to be used on its standard output.
18261 The program can't have any arguments and doesn't receive any input from Alpine,
18262 but the rest of the processing works as if the contents came from a file.
18263 <P>
18264 Instead of storing the data in a local file, the
18265 template may be stored remotely in an IMAP folder.
18266 In order to do this,
18267 you must use a remote name for the template.
18268 A remote template name might look like:
18269 <P>
18270 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/templ3</SAMP></CENTER>
18271 <P>
18273 The syntax used here is the same as the syntax used for a remote
18274 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
18275 Note that you may not access an existing template file remotely,
18276 you have to create a new <EM>folder</EM> that contains the template data.
18277 If the name you use here for the template is a remote name, then when
18278 you edit the file using the "F" command the data will
18279 be saved remotely in the folder.
18280 You aren't required to do anything special to create the folder, it
18281 gets created if you use a remote name.
18282 <P>
18283 If you type "F" you may edit the contents of the file (as opposed to
18284 the name of the file) you have specified.
18285 If you type "T" you may use a browser to choose an existing filename.
18286 <P>
18287 Besides containing regular text, the template file may also
18288 contain (or a template file program may produce) tokens that are replaced with text
18289 that depends on the message you are replying to or forwarding.
18290 The tokens all look like _word_ (a word surrounded by underscores).
18291 For example, if the token
18292 <P>
18293 <CENTER><SAMP>_DATE_</SAMP></CENTER>
18294 <P>
18295 is included in the text of the template file, then when you reply to
18296 or forward a message, the token will be replaced with the actual date
18297 the message you are replying to or forwarding was sent.
18298 <P>
18299 If you use a role that has a template file for a plain composition
18300 (that is, not a reply or forward) then there is no original message, so
18301 any tokens that depend on the message will be replaced with nothing.
18302 So if you want a template file to be useful for new compositions it
18303 shouldn't include any of the tokens that depend on the message being
18304 replied to or forwarded.
18305 <P>
18306 The list of available tokens is
18307 <A HREF="h_index_tokens">here</A>.
18308 <P>
18309 Actually, for the adventurous, there is a way to conditionally include text based
18310 on whether or not a token would result in specific replacement text.
18311 For example, you could include some text based on whether or not
18312 the _NEWS_ token would result in any newsgroups if it was used.
18313 It's explained in detail
18314 <A HREF="h_reply_token_conditionals">here</A>.
18315 <P>
18316 In the very unlikely event that you want to include a literal token in
18317 a template file, you must precede it with a backslash character.
18318 For example, to include the literal text _DATE_ you must actually use
18319 \_DATE_.
18320 It is not possible to have a literal backslash followed by an expanded token.
18321 <P>
18322 A blank template field means that Alpine will not use a template file when
18323 this role is being used.
18324 <P>
18325 Look <A HREF="h_edit_nav_cmds">here</A>
18326 to see the available Editing and Navigation commands.
18327 <P>
18328 <End of help on this topic>
18329 </BODY>
18330 </HTML>
18331 ======= h_config_filt_stat_imp =======
18332 <HTML>
18333 <HEAD>
18334 <TITLE>Set Important Status Explained</TITLE>
18335 </HEAD>
18336 <BODY>
18337 <H1>Set Important Status Explained</H1>
18339 This describes part of the action to be taken if the Pattern for this
18340 filter is a match.
18341 If set to "Don't change it" then this does nothing.
18342 If set to "Set this state" then the Important flag is set
18343 for the matching message.
18344 If set to "Clear this state" then the Important flag is cleared
18345 for the matching message.
18346 The important flag usually causes an asterisk to show up in the MESSAGE
18347 INDEX.
18348 It may also be useful when selecting a set of messages
18349 with the Select command.
18350 <P>
18351 Look <A HREF="h_edit_nav_cmds">here</A>
18352 to see the available Editing and Navigation commands.
18353 <P>
18354 <End of help on this topic>
18355 </BODY>
18356 </HTML>
18357 ======= h_config_filt_stat_new =======
18358 <HTML>
18359 <HEAD>
18360 <TITLE>Set New Status Explained</TITLE>
18361 </HEAD>
18362 <BODY>
18363 <H1>Set New Status Explained</H1>
18365 This describes part of the action to be taken if the Pattern for this
18366 filter is a match.
18367 If set to "Don't change it" then this does nothing.
18368 If set to "Set this state" then the
18369 matching message is marked New.
18370 If set to "Clear this state" then the
18371 matching message is marked Seen.
18372 <P>
18373 Look <A HREF="h_edit_nav_cmds">here</A>
18374 to see the available Editing and Navigation commands.
18375 <P>
18376 <End of help on this topic>
18377 </BODY>
18378 </HTML>
18379 ======= h_config_filt_stat_ans =======
18380 <HTML>
18381 <HEAD>
18382 <TITLE>Set Answered Status Explained</TITLE>
18383 </HEAD>
18384 <BODY>
18385 <H1>Set Answered Status Explained</H1>
18387 This describes part of the action to be taken if the Pattern for this
18388 filter is a match.
18389 If set to "Don't change it" then this does nothing.
18390 If set to "Set this state" then the Answered flag is set
18391 for the matching message.
18392 If set to "Clear this state" then the Answered flag is cleared
18393 for the matching message.
18394 <P>
18395 Look <A HREF="h_edit_nav_cmds">here</A>
18396 to see the available Editing and Navigation commands.
18397 <P>
18398 <End of help on this topic>
18399 </BODY>
18400 </HTML>
18401 ======= h_config_filt_stat_del =======
18402 <HTML>
18403 <HEAD>
18404 <TITLE>Set Deleted Status Explained</TITLE>
18405 </HEAD>
18406 <BODY>
18407 <H1>Set Deleted Status Explained</H1>
18409 This describes part of the action to be taken if the Pattern for this
18410 filter is a match.
18411 If set to "Don't change it" then this does nothing.
18412 If set to "Set this state" then the
18413 matching message is marked Deleted.
18414 If set to "Clear this state" then the
18415 matching message is marked UnDeleted.
18416 <P>
18417 You should not use this option unless you are prepared to have matching
18418 messages expunged from the folder permanently.
18419 For example, if you type the Expunge command, this filter is applied
18420 before the expunge, so matching messages will be marked Deleted and then
18421 will be permanently expunged from the folder.
18422 However, since the index isn't redrawn in between the time that the message
18423 is marked Deleted and the time that you are asked to expunge, the only
18424 indication that you are expunging the message comes in the number of messages
18425 being expunged.
18426 The same thing may happen when you close a folder.
18427 It is also possible that an expunge not initiated by you will
18428 delete matching messages.
18429 <P>
18430 Look <A HREF="h_edit_nav_cmds">here</A>
18431 to see the available Editing and Navigation commands.
18432 <P>
18433 <End of help on this topic>
18434 </BODY>
18435 </HTML>
18436 ======= h_config_role_scoreval =======
18437 <HTML>
18438 <HEAD>
18439 <TITLE>Score Value Explained</TITLE>
18440 </HEAD>
18441 <BODY>
18442 <H1>Score Value Explained</H1>
18444 A message's score is the sum of the Score Values from all of the Scoring rules
18445 with Patterns that match the message.
18446 The value you give here is the Score Value associated with this rule.
18447 A Score Value is an integer between -100 and 100, with the default
18448 value of zero.
18449 <P>
18450 Alternatively, if the
18451 <A HREF="h_config_role_scorehdrtok">"Score From Header"</A>
18452 field is defined
18453 (on the line right below the "Score Value" field)
18454 then the "Score Value" is ignored and
18455 the "Score From Header" field is used instead.
18456 <P>
18457 Look <A HREF="h_edit_nav_cmds">here</A>
18458 to see the available Editing and Navigation commands.
18459 <P>
18460 <End of help on this topic>
18461 </BODY>
18462 </HTML>
18463 ======= h_config_role_scorehdrtok =======
18464 <HTML>
18465 <HEAD>
18466 <TITLE>Score Value From Header Explained</TITLE>
18467 </HEAD>
18468 <BODY>
18469 <H1>Score Value From Header Explained</H1>
18471 This option provides a way to use a number that appears in the headers of your
18472 messages as the message's score, or as a component of that score.
18473 If this field is defined then it is used instead of the "Score Value".
18474 The idea behind this option is that there may be a score embedded in the
18475 headers of messages that has already been calculated outside of Alpine.
18476 For example, messages delivered to you may contain an "X-Spam" header and
18477 somewhere in that header there is a score.
18478 <P>
18479 The value for this option is the name of the header followed by parentheses
18480 with two arguments inside:
18481 <P>
18482 <CENTER><SAMP>HeaderName(field_number,field_separators)</SAMP></CENTER>
18483 <P>
18484 No space is allowed between the comma and the start of the field_separators.
18485 It would be interpreted as the first separator if it was there.
18486 Field 0 is the whole line, Field 1 is the data up to the first separator, Field 2
18487 starts after that and goes to the second separator, and so on.
18488 It's easier to explain with examples.
18489 <P>
18490 <CENTER><SAMP>X-Spam(2," ")</SAMP></CENTER>
18491 <P>
18492 In the above example the header that is used is the "X-Spam" header.
18493 The value of that header (the part after the colon and the space) is split
18494 into fields separated by spaces.
18495 <P>
18496 <CENTER><SAMP>Field1 <space> Field2 <space> Field3 ...</SAMP></CENTER>
18497 <P>
18498 The second field is selected and converted to an integer. It only makes sense
18499 if Field2 really is an integer.
18500 <P>
18501 Here's an example of a SpamAssassin header.
18502 The exact look of the header will vary, but if your incoming mail
18503 contains headers that look like the following
18504 <P>
18505 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
18506 <P>
18507 you might want to use the hits value as a score.
18508 Since the score is an integer value you can't make use of the decimal part of
18509 the number, but
18510 you might split off the hits=10 part as a score by using the characters "="
18511 and "." as your separators.
18512 <P>
18513 <CENTER><SAMP>X-Spam-Status(2,"=.")</SAMP></CENTER>
18514 <P>
18515 The first field starts with the Y in Yes and goes until the "=" after
18516 hits.
18517 The second field is "10" so the score value would be 10.
18518 <P>
18519 Another example we've seen has headers that look like
18520 <P>
18521 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
18522 <P>
18523 Because there are two equals before the 7% the value
18524 <P>
18525 <CENTER><SAMP>X-Spam(3,"=%")</SAMP></CENTER>
18526 <P>
18527 should capture the probability as the score.
18528 <P>
18529 The Score From Header scoring value actually works just like the
18530 regular Score Value in that the rest of the pattern has to match before
18531 it is used and the scores from all the different scoring rules that
18532 match for a particular message are added together.
18533 When using the Score From Header method it may (or may not) make sense to
18534 use only a single scoring rule with a pattern that matches every message.
18535 <P>
18536 Look <A HREF="h_edit_nav_cmds">here</A>
18537 to see the available Editing and Navigation commands.
18538 <P>
18539 <End of help on this topic>
18540 </BODY>
18541 </HTML>
18542 ======= h_config_role_replyuse =======
18543 <HTML>
18544 <HEAD>
18545 <TITLE>Reply Use Explained</TITLE>
18546 </HEAD>
18547 <BODY>
18548 <H1>Reply Use Explained</H1>
18550 This option determines how this particular role will be used when Replying
18551 to a message.
18552 There are three possible values for this option.
18553 The value "Never"
18554 means that this role will not be a candidate for use when Replying.
18555 The role's Pattern will not be checked for a match, however the role will
18556 be available to be manually switched to if there is a confirmation prompt.
18557 <P>
18559 The options "With confirmation" and "Without confirmation"
18560 mean that you do want to consider this role when Replying.
18561 For either of these settings, the role's Pattern will be compared with
18562 the message being replied to.
18563 If there is a match then this role will either be used without confirmation
18564 or will be the default when confirmation is asked for, depending on
18565 which of the two options is selected.
18566 If confirmation is requested, you will also have a chance to
18567 manually change the role to any one of your other roles.
18568 <P>
18570 You won't be prompted for confirmation if none of your role Patterns
18571 match the message being replied to.
18572 This is independent of the value of the current option.
18573 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18574 feature may be used to change this behavior.
18575 <P>
18576 <End of help on this topic>
18577 </BODY>
18578 </HTML>
18579 ======= h_config_role_forwarduse =======
18580 <HTML>
18581 <HEAD>
18582 <TITLE>Forward Use Explained</TITLE>
18583 </HEAD>
18584 <BODY>
18585 <H1>Forward Use Explained</H1>
18587 This option determines how this particular role will be used when Forwarding
18588 a message.
18589 There are three possible values for this option.
18590 The value "Never"
18591 means that this role will not be a candidate for use when Forwarding.
18592 The role's Pattern will not be checked for a match, however the role will
18593 be available to be manually switched to if there is a confirmation prompt.
18594 <P>
18596 The options "With confirmation" and "Without confirmation"
18597 mean that you do want to consider this role when Forwarding.
18598 For either of these settings, the role's Pattern will be compared with
18599 the message being forwarded.
18600 If there is a match then this role will either be used without confirmation
18601 or will be the default when confirmation is asked for, depending on
18602 which of the two options is selected.
18603 If confirmation is requested, you will also have a chance to
18604 manually change the role to any one of your other roles.
18605 <P>
18607 You won't be prompted for confirmation if none of your role Patterns
18608 match the message being forwarded.
18609 This is independent of the value of the current option.
18610 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18611 feature may be used to change this behavior.
18612 <P>
18613 <End of help on this topic>
18614 </BODY>
18615 </HTML>
18616 ======= h_config_role_composeuse =======
18617 <HTML>
18618 <HEAD>
18619 <TITLE>Compose Use Explained</TITLE>
18620 </HEAD>
18621 <BODY>
18622 <H1>Compose Use Explained</H1>
18624 This option determines how this particular role will be used when Composing
18625 a new message using the "Compose" command.
18626 This does not affect what happens when using the "Role" command
18627 to compose a new message.
18628 The "Role" command allows you to select a role from all of the
18629 roles you have defined, regardless of what Uses you've assigned to those
18630 roles.
18631 <P>
18633 There are three possible values for this option.
18634 The value "Never"
18635 means that this role will not be a candidate for use when Composing.
18636 The role's Current Folder Type will not be checked for a match, however the role
18637 will be available to be manually switched to if there is a confirmation prompt.
18638 <P>
18640 The options "With confirmation" and "Without confirmation"
18641 mean that you do want to consider this role when Composing.
18642 For either of these settings,
18643 the role's Current Folder Type will be checked (since there is no message
18644 to compare with, the rest of the Pattern is considered a match).
18645 If there is a match then this role will either be used without confirmation
18646 or will be the default when confirmation is asked for, depending on
18647 which of the two options is selected.
18648 If confirmation is requested, you will also have a chance to
18649 manually change the role to any one of your other roles.
18650 <P>
18652 When using the Compose command the role checking is a little different
18653 because there is no message being replied to or forwarded.
18654 Because of this the Current Folder Type is checked but the header pattern
18655 fields, the AllText pattern, the BodyText pattern, and the Score Interval are all ignored.
18656 A role is considered to be a match if it is a candidate for Compose Use and
18657 its Current Folder Type matches the currently open folder.
18658 This could be useful if you want to set a role based on the folder you
18659 are reading, or the type of folder you are reading.
18660 <P>
18662 You won't be prompted for confirmation if none of your role Patterns
18663 are a match.
18664 This is independent of the value of the current option.
18665 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18666 feature may be used to change this behavior.
18667 <P>
18668 <End of help on this topic>
18669 </BODY>
18670 </HTML>
18671 ======= h_config_filter_folder =======
18672 <HTML>
18673 <HEAD>
18674 <TITLE>Filter Folder Explained</TITLE>
18675 </HEAD>
18676 <BODY>
18677 <H1>Filter Folder Explained</H1>
18679 When the Filter Action is set to "Move",
18680 the folder or folders specified here will be used to store messages matching
18681 the provided pattern.
18683 <P>
18684 If you set the Filter Action to "Move" you must give a folder name
18685 here.
18687 <P>
18688 If you wish,
18689 you may choose a folder from your folder collections by using the
18690 "T" command.
18691 <P>
18692 Besides regular text, the folder name may also contain
18693 tokens that are replaced with text representing the current date
18694 when you run Alpine.
18695 For example, if the folder name you use is
18696 <P>
18697 <CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER>
18698 <P>
18699 that is replaced with something like
18700 <P>
18701 <CENTER><SAMP>abc-2004-oct</SAMP></CENTER>
18702 <P>
18703 Or,
18704 <P>
18705 <CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER>
18706 <P>
18707 becomes
18708 <P>
18709 <CENTER><SAMP>abc-04-10</SAMP></CENTER>
18710 <P>
18711 The token names must be surrounded by underscores in order to be recognized
18712 as tokens.
18713 The tokens that may be used are those that are derived from the current date.
18714 They're listed near the bottom of the list of tokens give
18715 <A HREF="h_index_tokens">here</A>.
18716 <P>
18717 Look "<A HREF="h_rule_patterns">here</A>"
18718 for more information on Patterns.
18719 <P>
18720 Look <A HREF="h_edit_nav_cmds">here</A>
18721 to see the available Editing and Navigation commands.
18722 <P>
18723 <End of help on this topic>
18724 </BODY>
18725 </HTML>
18726 ======= h_config_filter_kw_set =======
18727 <HTML>
18728 <HEAD>
18729 <TITLE>Set These Keywords Explained</TITLE>
18730 </HEAD>
18731 <BODY>
18732 <H1>Set These Keywords Explained</H1>
18734 This describes part of the action to be taken if the Pattern for this
18735 filter is a match.
18736 Read a little about keywords in the help text for the
18737 <A HREF="h_common_flag">Flag</A> command.
18738 This option is a list of keywords that will be Set when there is a match.
18739 If you wish, you may choose keywords from the list of keywords you have
18740 defined with the "T" command.
18741 You may add new keywords by defining them in the
18742 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
18743 If you have given a keyword a nickname when configuring it,
18744 that nickname may be used instead of the actual keyword.
18746 <P>
18747 Look <A HREF="h_edit_nav_cmds">here</A>
18748 to see the available Editing and Navigation commands.
18749 <P>
18750 <End of help on this topic>
18751 </BODY>
18752 </HTML>
18753 ======= h_config_filter_kw_clr =======
18754 <HTML>
18755 <HEAD>
18756 <TITLE>Clear These Keywords Explained</TITLE>
18757 </HEAD>
18758 <BODY>
18759 <H1>Clear These Keywords Explained</H1>
18761 This describes part of the action to be taken if the Pattern for this
18762 filter is a match.
18763 Read a little about keywords in the help text for the
18764 <A HREF="h_common_flag">Flag</A> command.
18765 This option is a list of keywords that will be Cleared when there is a match.
18766 If you wish, you may choose keywords from the list of keywords you have
18767 defined with the "T" command.
18768 You may add new keywords by defining them in the
18769 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
18770 If you have given a keyword a nickname when configuring it,
18771 that nickname may be used instead of the actual keyword.
18773 <P>
18774 Look <A HREF="h_edit_nav_cmds">here</A>
18775 to see the available Editing and Navigation commands.
18776 <P>
18777 <End of help on this topic>
18778 </BODY>
18779 </HTML>
18780 ======= h_index_tokens =======
18781 <HTML>
18782 <HEAD>
18783 <TITLE>Tokens for Index and Replying</TITLE>
18784 </HEAD>
18785 <BODY>
18787 This set of special tokens may be used in the
18788 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option,
18789 in the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
18790 in signature files,
18791 in template files used in
18792 <A HREF="h_rules_roles">"roles"</A>, and in the folder name
18793 that is the target of a Filter Rule.
18794 Some of them aren't available in all situations.
18795 <P>
18796 The tokens are used as they appear below for the "<!--#echo var="VAR_index-format"-->"
18797 option, but they must be surrounded by underscores for the
18798 "<!--#echo var="VAR_reply-leadin"-->" option, in signature and template files,
18799 and in the target of Filter Rules.
18800 <P>
18801 <P>
18803 <H1><EM>Tokens Available for all Cases (except Filter Rules)</EM></H1>
18805 <DL>
18806 <DT>SUBJECT</DT>
18807 <DD>
18808 This token represents the Subject the sender gave the message.
18809 Alternatives for use in the index screen are
18810 SUBJKEY, SUBJKEYINIT, SUBJECTTEXT, SUBJKEYTEXT, and SUBJKEYINITTEXT.
18811 You may color the subject text in the MESSAGE INDEX screen differently by using the
18812 <A HREF="h_config_index_subject_color">Index Subject Color</A> and the
18813 <A HREF="h_config_index_opening_color">Index Opening Color</A>
18814 options available from
18815 the <A HREF="h_color_setup">Setup Kolor</A> screen.
18816 </DD>
18818 <DT>FROM</DT>
18819 <DD>
18820 This token represents the personal name (or email address if the name
18821 is unavailable) of the person specified in the message's "From:"
18822 header field.
18823 You may color the from text in the MESSAGE INDEX screen differently by using the
18824 <A HREF="h_config_index_from_color">Index From Color</A>
18825 option available from
18826 the <A HREF="h_color_setup">Setup Kolor</A> screen.
18827 </DD>
18829 <DT>ADDRESS</DT>
18830 <DD>
18831 This is similar to the "FROM" token, only it is always the
18832 email address, never the personal name.
18833 For example, "mailbox@domain".
18834 </DD>
18836 <DT>MAILBOX</DT>
18837 <DD>
18838 This is the same as the "ADDRESS" except that the
18839 domain part of the address is left off.
18840 For example, "mailbox".
18841 </DD>
18843 <DT>SENDER</DT>
18844 <DD>
18845 This token represents the personal name (or email address) of the person
18846 listed in the message's "Sender:" header field.
18847 </DD>
18849 <DT>TO</DT>
18850 <DD>
18851 This token represents the personal names (or email addresses if the names
18852 are unavailable) of the persons specified in the
18853 message's "To:" header field.
18854 </DD>
18856 <DT>NEWSANDTO</DT>
18857 <DD>
18858 This token represents the newsgroups from the
18859 message's "Newsgroups:" header field <EM>and</EM>
18860 the personal names (or email addresses if the names
18861 are unavailable) of the persons specified in the
18862 message's "To:" header field.
18863 </DD>
18865 <DT>TOANDNEWS</DT>
18866 <DD>
18867 Same as "NEWSANDTO" except in the opposite order.
18868 </DD>
18870 <DT>NEWS</DT>
18871 <DD>
18872 This token represents the newsgroups from the
18873 message's "Newsgroups:" header field.
18874 </DD>
18876 <DT>CC</DT>
18877 <DD>
18878 This token represents the personal names (or email addresses if the names
18879 are unavailable) of the persons specified in the
18880 message's "Cc:" header field.
18881 </DD>
18883 <DT>RECIPS</DT>
18884 <DD>
18885 This token represents the personal names (or email addresses if the names
18886 are unavailable) of the persons specified in both the
18887 message's "To:" header field and
18888 the message's "Cc:" header field.
18889 </DD>
18891 <DT>NEWSANDRECIPS</DT>
18892 <DD>
18893 This token represents the newsgroups from the
18894 message's "Newsgroups:" header field <EM>and</EM>
18895 the personal names (or email addresses if the names
18896 are unavailable) of the persons specified in the
18897 message's "To:" and "Cc:" header fields.
18898 </DD>
18900 <DT>RECIPSANDNEWS</DT>
18901 <DD>
18902 Same as "NEWSANDRECIPS" except in the opposite order.
18903 </DD>
18905 <DT>INIT</DT>
18906 <DD>
18907 This token represents the initials from the personal name
18908 of the person specified in the message's "From:"
18909 header field.
18910 If there is no personal name, it is blank.
18911 </DD>
18913 <DT>DATE</DT>
18914 <DD>
18915 This token represents the date on which the message was sent, according
18916 to the "Date" header field.
18917 It has the format MMM DD. For example, "Oct 23".
18918 The feature
18919 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>,
18920 which adjusts for the timezone the message was sent from,
18921 may have an effect on the value of this token as well as the values of
18922 all of the other DATE or TIME tokens.
18923 Some of the DATE and TIME tokens are displayed in a locale-specific
18924 way unless the option
18925 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is set.
18926 </DD>
18928 <DT>SMARTDATE</DT>
18929 <DD>
18930 This token represents the date on which the message was sent, according
18931 to the "Date" header field.
18932 It is "Today" if the message was sent today,
18933 "Yesterday" for yesterday,
18934 "Wednesday" if it was last Wednesday, and so on. If the
18935 message is from last year and is more than six months old it includes the year, as well.
18936 See the SMARTDATE alternatives below, as well.
18937 </DD>
18939 <DT>SMARTTIME</DT>
18940 <DD>
18941 This token represents the most relevant elements of the date on which
18942 the message was sent (according to the "Date" header field),
18943 in a compact form. If the message was sent today, only the time is used
18944 (e.g. "9:22am", "10:07pm"); if it was sent during
18945 the past week, the day of the week and the hour are used
18946 (e.g. "Wed09am", "Thu10pm"); other dates are
18947 given as date, month, and year (e.g. "23Aug00",
18948 "9Apr98").
18949 </DD>
18951 <DT>SMARTDATETIME</DT>
18952 <DD>
18953 This is a combination of SMARTDATE and SMARTTIME.
18954 It is SMARTDATE unless the SMARTDATE value is "Today", in which
18955 case it is SMARTTIME.
18956 See the SMARTDATETIME alternatives below, as well.
18957 </DD>
18959 <DT>DATEISO</DT>
18960 <DD>
18961 This token represents the date on which the message was sent, according
18962 to the "Date" header field.
18963 It has the format YYYY-MM-DD. For example, "1998-10-23".
18964 </DD>
18966 <DT>SHORTDATEISO</DT>
18967 <DD>
18968 This token represents the date on which the message was sent, according
18969 to the "Date" header field.
18970 It has the format YY-MM-DD. For example, "98-10-23".
18971 </DD>
18973 <DT>SHORTDATE1</DT>
18974 <DD>
18975 This token represents the date on which the message was sent, according
18976 to the "Date" header field.
18977 It has the format MM/DD/YY. For example, "10/23/98".
18978 </DD>
18980 <DT>SHORTDATE2</DT>
18981 <DD>
18982 This token represents the date on which the message was sent, according
18983 to the "Date" header field.
18984 It has the format DD/MM/YY. For example, "23/10/98".
18985 </DD>
18987 <DT>SHORTDATE3</DT>
18988 <DD>
18989 This token represents the date on which the message was sent, according
18990 to the "Date" header field.
18991 It has the format DD.MM.YY. For example, "23.10.98".
18992 </DD>
18994 <DT>SHORTDATE4</DT>
18995 <DD>
18996 This token represents the date on which the message was sent, according
18997 to the "Date" header field.
18998 It has the format YY.MM.DD. For example, "98.10.23".
18999 </DD>
19001 <DT>LONGDATE</DT>
19002 <DD>
19003 This token represents the date on which the message was sent, according
19004 to the "Date" header field.
19005 It has the format MMM DD, YYYY. For example, "Oct 23, 1998".
19006 </DD>
19008 <DT>SMARTDATE alternatives</DT>
19009 <DD>
19010 There are several versions of SMARTDATE that are all the same except
19011 for the way they format dates far in the past.
19012 SMARTDATE formats the date using the information from your locale settings
19013 to format the date string. It may end up formatting dates so that they look
19014 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
19015 The feature
19016 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
19017 may have an affect on the values of these tokens.
19018 If you want more control you may use one of the following.
19019 <DL>
19020 <DT>SMARTDATE</DT> <DD>If the option
19021 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
19022 then this will be locale specific. Control this with the
19023 LC_TIME locale setting on a UNIX system. On Windows
19024 the Regional Options control panel may be used to set the Short date
19025 format. At the programming level, the strftime routine is what Alpine
19026 uses to print the date.
19027 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
19028 to SMARTDATES1.</DD>
19029 <DT>SMARTDATEISO</DT> <DD>DATEISO format. See text above.</DD>
19030 <DT>SMARTDATESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
19031 <DT>SMARTDATES1</DT> <DD>SHORTDATE1 format.</DD>
19032 <DT>SMARTDATES2</DT> <DD>SHORTDATE2 format.</DD>
19033 <DT>SMARTDATES3</DT> <DD>SHORTDATE3 format.</DD>
19034 <DT>SMARTDATES4</DT> <DD>SHORTDATE4 format.</DD>
19035 </DL>
19036 </DD>
19038 <DT>SMARTDATETIME alternatives</DT>
19039 <DD>
19040 There are several versions of SMARTDATETIME that are all very similar.
19041 The ones that end in 24 use a 24-hour clock for Today's messages instead
19042 of a 12-hour clock.
19043 The other variation is
19044 for the way they format dates far in the past.
19045 SMARTDATETIME and SMARTDATETIME24 format the date using the information from your locale settings
19046 to format the date string. It may end up formatting dates so that they look
19047 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
19048 The feature
19049 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
19050 may have an affect on the values of these tokens.
19051 The possible choices are:
19052 <DL>
19053 <DT>SMARTDATETIME</DT> <DD>If the option
19054 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
19055 then this will be locale specific. Control this with the
19056 LC_TIME locale setting on a UNIX system. On Windows
19057 the Regional Options control panel may be used to set the Short date
19058 format. At the programming level, the strftime routine is what Alpine
19059 uses to print the date.
19060 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
19061 to SMARTDATETIMES1.</DD>
19062 <DT>SMARTDATETIME24</DT> <DD>Use TIME24 for Today</DD>
19063 <DT>SMARTDATETIMEISO</DT> <DD>DATEISO format. See text above.</DD>
19064 <DT>SMARTDATETIMEISO24</DT> <DD>Use TIME24 for Today</DD>
19065 <DT>SMARTDATETIMESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
19066 <DT>SMARTDATETIMESHORTISO24</DT> <DD>Use TIME24 for Today</DD>
19067 <DT>SMARTDATETIMES1</DT> <DD>SHORTDATE1 format.</DD>
19068 <DT>SMARTDATETIMES124</DT> <DD>Use TIME24 for Today</DD>
19069 <DT>SMARTDATETIMES2</DT> <DD>SHORTDATE2 format.</DD>
19070 <DT>SMARTDATETIMES224</DT> <DD>Use TIME24 for Today</DD>
19071 <DT>SMARTDATETIMES3</DT> <DD>SHORTDATE3 format.</DD>
19072 <DT>SMARTDATETIMES324</DT> <DD>Use TIME24 for Today</DD>
19073 <DT>SMARTDATETIMES4</DT> <DD>SHORTDATE4 format.</DD>
19074 <DT>SMARTDATETIMES424</DT> <DD>Use TIME24 for Today</DD>
19075 </DL>
19076 </DD>
19078 <DT>DAYDATE</DT>
19079 <DD>
19080 This token represents the date on which the message was sent, according
19081 to the "Date" header field.
19082 It looks like "Sat, 23 Oct 1998".
19083 This token is never converted in any locale-specific way.
19084 </DD>
19086 <DT>PREFDATE</DT>
19087 <DD>
19088 This token represents the date on which the message was sent, according
19089 to the "Date" header field.
19090 It is your operating system's idea of the preferred date representation for the current locale.
19091 Internally it uses the %x version of the date from the strftime routine.
19092 </DD>
19094 <DT>PREFTIME</DT>
19095 <DD>
19096 This token represents the time at which the message was sent, according
19097 to the "Date" header field.
19098 It is the preferred time representation for the current locale.
19099 Internally it uses the %X version of the time from the strftime routine.
19100 </DD>
19102 <DT>PREFDATETIME</DT>
19103 <DD>
19104 This token represents the date and time at which the message was sent, according
19105 to the "Date" header field.
19106 It is the preferred date and time representation for the current locale.
19107 Internally it uses the %c version of the time from the strftime routine.
19108 </DD>
19110 <DT>DAY</DT>
19111 <DD>
19112 This token represents the day of the month on which the message was sent,
19113 according to the "Date" header field.
19114 For example, "23" or "9".
19115 </DD>
19117 <DT>DAY2DIGIT</DT>
19118 <DD>
19119 This token represents the day of the month on which the message was sent,
19120 according to the "Date" header field.
19121 For example, "23" or "09".
19122 It is always 2 digits.
19123 </DD>
19125 <DT>DAYORDINAL</DT>
19126 <DD>
19127 This token represents the ordinal number that is the day of
19128 the month on which the message was sent,
19129 according to the "Date" header field.
19130 For example, "23rd" or "9th".
19131 </DD>
19133 <DT>DAYOFWEEK</DT>
19134 <DD>
19135 This token represents the day of the week on which the message was sent,
19136 according to the "Date" header field.
19137 For example, "Sunday" or "Wednesday".
19138 </DD>
19140 <DT>DAYOFWEEKABBREV</DT>
19141 <DD>
19142 This token represents the day of the week on which the message was sent,
19143 according to the "Date" header field.
19144 For example, "Sun" or "Wed".
19145 </DD>
19147 <DT>MONTHABBREV</DT>
19148 <DD>
19149 This token represents the month the message was sent, according
19150 to the "Date" header field.
19151 For example, "Oct".
19152 </DD>
19154 <DT>MONTHLONG</DT>
19155 <DD>
19156 This token represents the month in which the message was sent, according
19157 to the "Date" header field.
19158 For example, "October".
19159 </DD>
19161 <DT>MONTH</DT>
19162 <DD>
19163 This token represents the month in which the message was sent, according
19164 to the "Date" header field.
19165 For example, "10" or "9".
19166 </DD>
19168 <DT>MONTH2DIGIT</DT>
19169 <DD>
19170 This token represents the month in which the message was sent, according
19171 to the "Date" header field.
19172 For example, "10" or "09".
19173 It is always 2 digits.
19174 </DD>
19176 <DT>YEAR</DT>
19177 <DD>
19178 This token represents the year the message was sent, according
19179 to the "Date" header field.
19180 For example, "1998" or "2001".
19181 </DD>
19183 <DT>YEAR2DIGIT</DT>
19184 <DD>
19185 This token represents the year the message was sent, according
19186 to the "Date" header field.
19187 For example, "98" or "01".
19188 It is always 2 digits.
19189 </DD>
19191 <DT>TIME24</DT>
19192 <DD>
19193 This token represents the time at which the message was sent, according
19194 to the "Date" header field.
19195 There is no adjustment made for different time zones, so you'll get
19196 the time the message was sent according to the time zone the sender
19197 was in.
19198 It has the format HH:MM. For example, "17:28".
19199 </DD>
19201 <DT>TIME12</DT>
19202 <DD>
19203 This token represents the time at which the message was sent, according
19204 to the "Date" header field.
19205 This time is for a 12 hour clock.
19206 It has the format HH:MMpm.
19207 For example, "5:28pm" or "11:13am".
19208 </DD>
19210 <DT>TIMEZONE</DT>
19211 <DD>
19212 This token represents the numeric timezone from
19213 the "Date" header field.
19214 It has the format [+-]HHMM. For example, "-0800".
19215 </DD>
19217 </DL>
19219 <P>
19220 <H1><EM>Tokens Available Only for <!--#echo var="VAR_index-format"--></EM></H1>
19222 <DL>
19223 <DT>MSGNO</DT>
19224 <DD>
19225 This token represents the message's current position in the folder that,
19226 of course, may change as the folder is sorted or new mail arrives.
19227 </DD>
19229 <DT>STATUS</DT>
19230 <DD>
19231 This token represents a three character wide field displaying various
19232 aspects of the message's state.
19233 The first character is either blank,
19234 a '*' for message marked Important, or a '+' indicating a message
19235 addressed directly to you (as opposed to your having received it via a
19236 mailing list, for example).
19237 When the feature
19238 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>"
19239 is set, if the first character would have been
19240 blank then it will instead be a '-' if the message is cc'd to you.
19241 The second character is typically blank,
19242 though the arrow cursor may occupy it if either the
19243 "<A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>"
19244 or the
19245 "<A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A>" feature
19246 is set (or you actually are on a slow link).
19247 The third character is either '<A HREF="h_flag_deleted">D</A>' (Deleted),
19248 '<A HREF="h_flag_answered">A</A>' (Answered),
19249 '<A HREF="h_flag_forwarded">F</A>' (Forwarded),
19250 '<A HREF="h_flag_new">N</A>' (New), or blank.
19251 <P>
19252 If you are using a threaded view of the index and this message is at the
19253 top of a collapsed portion of a thread,
19254 then this token refers to all of the messages in the collapsed portion of
19255 the thread instead of just the top message.
19256 The first character will be a '*' if <EM>any</EM> of the messages in the thread
19257 are marked Important, else a '+' if any of the messages are addressed
19258 to you, else a '-' if any of the messages are cc'd to you.
19259 The third character will be a 'D' if <EM>all</EM> of the messages
19260 in the collapsed thread are marked deleted,
19261 an 'A' if <EM>all</EM> of the messages
19262 in the collapsed thread are marked answered,
19263 it will be an 'N' if any of
19264 the messages are undeleted and unseen, and it will be blank otherwise.
19265 </DD>
19267 <DT>FULLSTATUS</DT>
19268 <DD>
19269 This token represents a less abbreviated alternative
19270 to the "STATUS" token.
19271 It is six characters wide.
19272 The first character is '+', '-', or blank, the
19273 second blank, the third either '*' or blank, the fourth
19274 '<A HREF="h_flag_new">N</A>' or blank,
19275 the fifth '<A HREF="h_flag_answered">A</A>'
19276 or blank, and the sixth character is
19277 either '<A HREF="h_flag_deleted">D</A>' or
19278 blank.
19279 <P>
19280 If you are using a threaded view of the index and this message is at the
19281 top of a collapsed portion of a thread,
19282 then this token refers to all of the messages in the collapsed portion of
19283 the thread instead of just the top message.
19284 The first character is '+', '-', or blank depending on whether <EM>any</EM>
19285 of the messages in the collapsed thread are addressed to you or cc'd to you.
19286 The third character will be '*' if any of the messages are marked
19287 Important.
19288 The fourth character will be 'N' if all of the messages in the thread
19289 are New, else 'n' if some of the messages in the thread are New, else blank.
19290 The fifth character will be 'A' or 'a' or blank, and the sixth character
19291 will be 'D' or 'd' or blank.
19292 </DD>
19294 <DT>IMAPSTATUS</DT>
19295 <DD>
19296 This token represents an even less abbreviated alternative to the
19297 "STATUS" token.
19298 It differs from "FULLSTATUS" in only the fourth character, which is
19299 an 'N' if the message is new to this folder since the last time
19300 it was opened <EM>and</EM> it has not been viewed, an 'R' (Recent) if the message
19301 is new to the folder and has been viewed, a 'U' (Unseen) if the message is not
19302 new to the folder since it was last opened <EM>but</EM> has not been
19303 viewed, or a blank if the message has been in the folder since it was
19304 last opened and has been viewed.
19305 <P>
19306 If you are using a threaded view of the index and this message is at the
19307 top of a collapsed portion of a thread,
19308 then the fourth character will be
19309 'N' if all of the messages in the thread are unseen and recent;
19310 else 'n' if some of the messages in the thread are unseen and recent;
19311 else 'U' if all of the messages in the thread are unseen and not recent;
19312 else 'u' if some of the messages in the thread are unseen and not recent;
19313 else 'R' if all of the messages in the thread are seen and recent;
19314 else 'r' if some of the messages in the thread are seen and recent;
19315 else blank.
19316 </DD>
19318 <DT>SHORTIMAPSTATUS</DT>
19319 <DD>
19320 This is the same as the last four of the six characters of IMAPSTATUS,
19321 so the '+' To Me information will be missing.
19322 </DD>
19324 <DT>SIZE</DT>
19325 <DD>
19326 This token represents the total size, in bytes, of the message.
19327 If a "K" (Kilobyte)
19328 follows the number, the size is approximately 1,000
19329 times that many bytes (rounded to the nearest 1,000).
19330 If an "M" (Megabyte) follows the number, the size is approximately
19331 1,000,000 times that many bytes.
19332 Commas are not used in this field.
19333 This field is seven characters wide, including the enclosing parentheses.
19334 Sizes are rounded when "K" or "M" is present.
19335 The progression of sizes used looks like:
19337 <P>
19338 <CENTER><SAMP>0 1 ... 9999 10K ... 999K 1.0M ... 99.9M 100M ... 2000M</SAMP></CENTER>
19339 <P>
19340 </DD>
19342 <DT>SIZECOMMA</DT>
19343 <DD>
19344 This token represents the total size, in bytes, of the message.
19345 If a "K" (Kilobyte)
19346 follows the number, the size is approximately 1,000
19347 times that many bytes (rounded to the nearest 1,000).
19348 If an "M" (Megabyte) follows the number, the size is approximately
19349 1,000,000 times that many bytes.
19350 Commas are used if the number shown is 1,000 or greater.
19351 The SIZECOMMA field is one character wider than the SIZE field.
19352 Sizes are rounded when "K" or "M" is present.
19353 The progression of sizes used looks like:
19355 <P>
19356 <CENTER><SAMP>0 1 ... 99,999 100K ... 9,999K 10.0M ... 999.9M 1,000M ... 2,000M</SAMP></CENTER>
19357 <P>
19358 </DD>
19360 <DT>KSIZE</DT>
19361 <DD>
19362 This token represents the total size of the message, expressed in
19363 kilobytes or megabytes, as most appropriate.
19364 These are 1,024 byte kilobytes and 1,024 x 1,024 byte megabytes.
19365 The progression of sizes used looks like:
19367 <P>
19368 <CENTER><SAMP>0K 1K ... 1023K 1.0M ... 99.9M 100M ... 2047M</SAMP></CENTER>
19369 <P>
19370 </DD>
19372 <DT>SIZENARROW</DT>
19373 <DD>
19374 This token represents the total size, in bytes, of the message.
19375 If a "K" (Kilobyte)
19376 follows the number, the size is approximately 1,000
19377 times that many bytes.
19378 If an "M" (Megabyte) follows the number, the size is approximately
19379 1,000,000 times that many bytes.
19380 If a "G" (Gigabyte) follows the number, the size is approximately
19381 1,000,000,000 times that many bytes.
19382 This field uses only five characters of screen width, including the enclosing
19383 parentheses.
19384 The progression of sizes used looks like:
19386 <P>
19387 <CENTER><SAMP>0 1 ... 999 1K ... 99K .1M ... .9M 1M ... 99M .1G ... .9G 1G 2G</SAMP></CENTER>
19388 <P>
19389 </DD>
19391 <DT>DESCRIPSIZE</DT>
19392 <DD>
19393 This token is intended to represent a more useful description of the
19394 message than just its size, but it isn't very useful at this point.
19395 The plus sign in this view means there are attachments.
19396 Note that including this token in
19397 the "<!--#echo var="VAR_index-format"-->" could slow down the
19398 display a little while Alpine collects the necessary information.
19399 </DD>
19401 <DT>SUBJKEY</DT>
19402 <DD>
19403 This token is the same as the SUBJECT token unless keywords are set for
19404 the message.
19405 In that case, a list of keywords enclosed in braces will be prepended to
19406 the subject of the message.
19407 Only those keywords that you have defined in your
19408 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19409 in Setup/Config are considered in the list.
19410 In other words, keywords that have been set by some other means, perhaps
19411 by another email program, won't show up unless included in
19412 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19413 Having this set in the <!--#echo var="VAR_index-format"--> will also cause the keywords to be
19414 prepended to the subject in the MESSAGE TEXT screen.
19415 If you have given a keyword a nickname
19416 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19417 instead of the actual keyword.
19418 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19419 option may be used to modify this token slightly.
19420 It is also possible to color keywords in the index using the
19421 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19422 </DD>
19424 <DT>SUBJKEYINIT</DT>
19425 <DD>
19426 This token is the same as the SUBJKEY token except that instead of
19427 prepending a list of keywords to the subject, a list of first initials
19428 of keywords will be prepended instead.
19429 For example, if a message has the keywords <EM>Work</EM> and <EM>Now</EM>
19430 set (or Work and Now are the Alpine nicknames of keywords that are set)
19431 then the SUBJKEY token would cause a result like
19432 <P>
19433 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
19434 <P>
19435 whereas the SUBJKEYINIT token would give
19436 <P>
19437 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
19438 <P>
19439 Only those keywords that you have defined in your
19440 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19441 in Setup/Config are considered in the list.
19442 In other words, keywords that have been set by some other means, perhaps
19443 by another email program, won't show up unless included in
19444 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19445 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19446 option may be used to modify this token slightly.
19447 It is also possible to color keywords in the index using the
19448 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19449 </DD>
19451 <DT>SUBJECTTEXT</DT>
19452 <DD>
19453 Same as SUBJECT but if there is room in the Subject field for more text,
19454 the opening part of the text of the message is displayed after the subject.
19455 The time needed to fetch the text may cause a performance problem
19456 which can, of course, be avoided by using the SUBJECT version of
19457 the Subject instead.
19458 You may color this opening text differently by using the
19459 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19460 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19461 You may adjust the characters that are displayed between the Subject and the
19462 opening text with the option
19463 <A HREF="h_config_opening_sep"><!--#echo var="VAR_opening-text-separator-chars"--></A>.
19464 </DD>
19466 <DT>SUBJKEYTEXT</DT>
19467 <DD>
19468 Same as SUBJKEY but with the opening message text.
19469 </DD>
19471 <DT>OPENINGTEXT</DT>
19472 <DD>
19473 This is similar to SUBJECTTEXT.
19474 Instead of combining the Subject and the opening text in a single
19475 field in the index screen this token allows you to allocate a
19476 separate column just for the opening text of the message.
19477 The time needed to fetch this text may cause a performance problem.
19478 You may color this opening text differently by using the
19479 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19480 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19481 </DD>
19483 <DT>OPENINGTEXTNQ</DT>
19484 <DD>
19485 This is very similar to OPENINGTEXT.
19486 The NQ stands for No Quotes.
19487 The only difference is that quoted text (lines beginning with >) is deleted.
19488 For some messages this may be confusing.
19489 For example, a message might have a line preceding some quoted
19490 text that reads something like "On May 8th person A said."
19491 That no longer makes sense after the quoted text is deleted and it
19492 will appear that person A said whatever the text after the quote
19493 is, even though that is really person B talking.
19494 </DD>
19496 <DT>SUBJKEYINITTEXT</DT>
19497 <DD>
19498 Same as SUBJKEYINIT but with the opening message text.
19499 </DD>
19501 <DT>KEY</DT>
19502 <DD>
19503 This is a space-delimited list of keywords that are set for the message.
19504 Only those keywords that you have defined in your
19505 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19506 in Setup/Config are considered in the list.
19507 In other words, keywords that have been set by some other means, perhaps
19508 by another email program, won't show up unless included in
19509 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19510 If you have given a keyword a nickname
19511 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19512 instead of the actual keyword.
19513 It is also possible to color keywords in the index using the
19514 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19515 This token defaults to an arbitrary width of 5.
19516 You should set it to whatever width suits you using something
19517 like KEY(17) in the <!--#echo var="VAR_index-format"-->.
19518 </DD>
19520 <DT>KEYINIT</DT>
19521 <DD>
19522 This is a list of keyword initials that are set for the message.
19523 If you have given a keyword a nickname
19524 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), the initial of that nickname
19525 is displayed instead of the initial of the actual keyword.
19526 It is also possible to color keyword initials in the index using the
19527 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19528 This token defaults to an arbitrary width of 2.
19529 You should set it to whatever width suits you using something
19530 like KEYINIT(3) in the <!--#echo var="VAR_index-format"-->.
19531 </DD>
19533 <DT>PRIORITY</DT>
19534 <DD>
19535 The X-Priority header is a non-standard header that is used in a
19536 somewhat standard way by many mail programs.
19537 Alpine expects the value of this header to be a digit with a value
19538 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
19539 Since this priority is something that the sender sets it is only an indication
19540 of the priority that the sender attaches to the mail and it is therefore almost
19541 totally unreliable for use as a filtering criterion.
19542 This token will display the numeric value of the priority if it is between
19543 1 and 5.
19544 It will be suppressed (blank) if the value is 3, which is normal priority.
19545 This token may be colored with the
19546 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19547 </DD>
19549 <DT>PRIORITYALPHA</DT>
19550 <DD>
19551 This is a more verbose interpretation of the X-Priority field.
19552 Once again nothing is displayed unless the value of the field
19553 is 1, 2, 4, or 5.
19554 The values displayed for those values are:
19555 <P>
19556 <TABLE>
19557 <TR> <TD>1</TD> <TD>Highest</TD> </TR>
19558 <TR> <TD>2</TD> <TD>High</TD> </TR>
19559 <TR> <TD>4</TD> <TD>Low</TD> </TR>
19560 <TR> <TD>5</TD> <TD>Lowest</TD> </TR>
19561 </TABLE>
19562 <P>
19563 This token may be colored with the
19564 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19565 </DD>
19567 <DT>PRIORITY!</DT>
19568 <DD>
19569 This is a one character, non-numeric version of the X-Priority field.
19570 If the value of the X-Priority header is 1 or 2 an exclamation
19571 point is displayed.
19572 If the value is 4 or 5 a "v" (think down arrow) is displayed.
19573 This token may be colored with the
19574 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19575 </DD>
19577 <DT>ATT</DT>
19578 <DD>
19579 This is a one column wide field that represents the number of attachments
19580 a message has. It will be blank if there are no attachments, a single
19581 digit for one to nine attachments, or an asterisk for more than nine.
19582 Note that including this token in
19583 the "<!--#echo var="VAR_index-format"-->" could slow down the
19584 display a little while Alpine collects the necessary information.
19585 </DD>
19587 <DT>FROMORTO</DT>
19588 <DD>
19589 This token represents <EM>either</EM> the personal name (or email address) of
19590 the person listed in the message's "From:" header
19591 field, <EM>or</EM>, if that address is yours or one of your
19592 <A HREF="h_config_alt_addresses">alternate addresses</A>,
19593 the first person specified in the
19594 message's "To:" header field
19595 with the prefix "To: " prepended.
19596 If the from address is yours and there is also no "To" address,
19597 Alpine will use the address on the "Cc" line.
19598 If there is no address there, either, Alpine will look for a newsgroup name
19599 from the "Newsgroups" header field and put
19600 that after the "To: " prefix.
19601 </DD>
19603 <DT>FROMORTONOTNEWS</DT>
19604 <DD>
19605 This is almost the same as <EM>FROMORTO</EM>.
19606 The difference is that newsgroups aren't considered.
19607 When a message is from you, doesn't have a To or Cc, and does have
19608 a Newsgroups header; this token will be your name instead of the name
19609 of the newsgroup (like it would be with FROMORTO).
19610 </DD>
19612 <DT>TEXT</DT>
19613 <DD>
19614 This is a different sort of token.
19615 It allows you to display a label within each index line.
19616 It will be the same fixed text for each line.
19617 It is different from all the other tokens in that there is no space column
19618 displayed after this token.
19619 Instead, it is butted up against the following field.
19620 It also has a different syntax.
19621 The text to display is given following a colon after the
19622 word "TEXT".
19623 For example,
19624 <P>
19625 <CENTER><SAMP>TEXT:abc=</SAMP></CENTER>
19626 <P>
19627 would insert the literal text "abc=" (without the quotes)
19628 into the index display line.
19629 You must quote the text if it includes space characters, like
19630 <P>
19631 <CENTER><SAMP>TEXT:"abc = "</SAMP></CENTER>
19632 <P>
19633 </DD>
19635 <DT>HEADER</DT>
19636 <DD>
19637 This allows you to display the text from a particular header line in the
19638 message.
19639 The syntax for this token is substantially different from all the others
19640 in order that you might be able to display a portion of the text following
19641 a particular header.
19642 The header name you are interested in is given following a colon
19643 after the word "HEADER".
19644 For example,
19645 <P>
19646 <CENTER><SAMP>HEADER:X-Spam</SAMP></CENTER>
19647 <P>
19648 would display the text of the X-Spam header, if any.
19649 Like for other index tokens a width field may (and probably should)
19650 follow this.
19651 <P>
19652 <CENTER><SAMP>HEADER:X-Spam(10)</SAMP></CENTER>
19653 <P>
19654 displays the first ten characters of the X-Spam header.
19655 Unlike other index tokens, the syntax for HEADER is more flexible.
19656 An optional second argument comes after a comma inside the parentheses.
19657 It specifies the "field" number.
19658 By default, the field separator is a space character.
19659 No extra space characters are allowed in the argument list.
19660 <P>
19661 <CENTER><SAMP>HEADER:X-Spam(10,2)</SAMP></CENTER>
19662 <P>
19663 would display the second field, left-justified, in a 10 character
19664 wide field.
19665 The second field would consist of all the text after the first space
19666 up to the next space or the end of the header.
19667 The default field number is zero, which stands for the entire line.
19668 There is also an optional third argument that is a list of field
19669 separators. It defaults to a space character.
19670 The example
19671 <P>
19672 <CENTER><SAMP>HEADER:X-Spam(10,2,:% )</SAMP></CENTER>
19673 <P>
19674 would cause the field separators to be any of colon, percent,
19675 or space (there is a space character between the percent and the
19676 right parenthesis).
19677 The first field runs from the start of the header value up to the first
19678 colon, percent, or space; the second goes from there to the next; and so on.
19679 In order to use a comma character as a field separator you must escape
19680 it by preceding it with a backslash (\).
19681 The same is true of the backslash character itself.
19682 There is one further optional argument.
19683 It is an R or an L to specify right or left adjustment of the text
19684 within the field.
19685 The default is to left justify, however if you are displaying numbers
19686 you might prefer to right justify.
19687 <P>
19688 Here's an example of a SpamAssassin header.
19689 The exact look of the header will vary, but if your incoming mail
19690 contains headers that look like the following
19691 <P>
19692 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
19693 <P>
19694 you might want to display the hits value.
19695 The first field starts with the Y in Yes.
19696 To get what you're interested in you might use "=" and
19697 space as the field separators and display the third field, like
19698 <P>
19699 <CENTER><SAMP>HEADER:X-Spam-Status(4,3,= )</SAMP></CENTER>
19700 <P>
19701 or maybe you would break at the dot instead
19702 <P>
19703 <CENTER><SAMP>HEADER:X-Spam-Status(2,2,=.,R)</SAMP></CENTER>
19704 <P>
19705 Another example we've seen has headers that look like
19706 <P>
19707 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
19708 <P>
19709 Because there are two equals and a comma before the 7% and a comma
19710 after it, the token
19711 <P>
19712 <CENTER><SAMP>HEADER:X-Spam(3,4,=\,,R)</SAMP></CENTER>
19713 <P>
19714 should display the probability (for example 7% or 83%) right justified
19715 in a 3-wide field.
19716 </DD>
19718 <DT>ARROW</DT>
19719 <DD>
19720 This gives an alternative way to display the current message in the
19721 MESSAGE INDEX screen.
19722 Usually the current message is indicated by the line being shown in
19723 reverse video.
19724 Instead, if the ARROW token is included in your <!--#echo var="VAR_index-format"-->,
19725 the current line will include an "arrow" that
19726 looks like
19727 <P>
19728 <CENTER><SAMP>-></SAMP></CENTER>
19729 <P>
19730 in the ARROW token's field.
19731 For all of the non-current messages, the ARROW field will be filled
19732 with blanks.
19733 If you use the fixed-field width feature the length of the "arrow"
19734 may be adjusted.
19735 The arrow will be drawn as width-1 dashes followed by a greater than sign.
19736 For example, if you use ARROW(3) you will get
19737 <P>
19738 <CENTER><SAMP>--></SAMP></CENTER>
19739 <P>
19740 and ARROW(1) will give you just
19741 <P>
19742 <CENTER><SAMP>></SAMP></CENTER>
19743 <P>
19744 It is also possible to set the color of the ARROW field.
19745 By default (and for non-current messages) the arrow is colored the same
19746 as the index line it is part of.
19747 You may set it to be another color with the
19748 <A HREF="h_config_index_arrow_color">Index Arrow Color</A> option available from
19749 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19750 </DD>
19752 <DT>SCORE</DT>
19753 <DD>
19754 This gives the
19755 <a href="h_rules_score">score</a>
19756 of each message.
19757 This will be six columns wide to accomodate the widest possible score.
19758 You will probably want to use the <!--#echo var="VAR_index-format"--> fixed-field width feature
19759 to limit the width of the field to the widest score that
19760 you use (e.g. SCORE(3) if your scores are always between 0 and 999).
19761 If you have not defined any score rules the scores will all be zero.
19762 If any of your score rules contain AllText or BodyText patterns
19763 then including SCORE in the <!--#echo var="VAR_index-format"-->
19764 may slow down the display of the MESSAGE INDEX screen.
19765 </DD>
19766 </DL>
19768 <P>
19769 <H1><EM>Tokens Available for all but <!--#echo var="VAR_index-format"--></EM></H1>
19771 <DL>
19772 <DT>CURNEWS</DT>
19773 <DD>
19774 This token represents the current newsgroup if there is one.
19775 For example, "comp.mail.pine".
19776 </DD>
19778 <DT>MSGID</DT>
19779 <DD>
19780 This token represents the message ID of the message.
19781 This token does not work with Filter Rule folder names.
19782 </DD>
19784 <DT>CURDATE</DT>
19785 <DD>
19786 This token represents the current date.
19787 It has the format MMM DD. For example, "Oct 23".
19788 </DD>
19790 <DT>CURDATEISO</DT>
19791 <DD>
19792 This token represents the current date.
19793 It has the format YYYY-MM-DD. For example, "1998-10-23".
19794 </DD>
19796 <DT>CURDATEISOS</DT>
19797 <DD>
19798 This token represents the current date.
19799 It has the format YY-MM-DD. For example, "98-10-23".
19800 </DD>
19802 <DT>CURPREFDATE</DT>
19803 <DD>
19804 This token represents the current date.
19805 It is your operating system's idea of the preferred date representation for the current locale.
19806 Internally it uses the %x version of the date from the strftime routine.
19807 </DD>
19809 <DT>CURPREFTIME</DT>
19810 <DD>
19811 This token represents the current time.
19812 It is the preferred time representation for the current locale.
19813 Internally it uses the %X version of the time from the strftime routine.
19814 </DD>
19816 <DT>CURPREFDATETIME</DT>
19817 <DD>
19818 This token represents the current date and time.
19819 It is the preferred date and time representation for the current locale.
19820 Internally it uses the %c version of the time from the strftime routine.
19821 </DD>
19823 <DT>CURTIME24</DT>
19824 <DD>
19825 This token represents the current time.
19826 It has the format HH:MM. For example, "17:28".
19827 </DD>
19829 <DT>CURTIME12</DT>
19830 <DD>
19831 This token represents the current time.
19832 This time is for a 12 hour clock.
19833 It has the format HH:MMpm.
19834 For example, "5:28pm" or "11:13am".
19835 </DD>
19837 <DT>CURDAY</DT>
19838 <DD>
19839 This token represents the current day of the month.
19840 For example, "23" or "9".
19841 </DD>
19843 <DT>CURDAY2DIGIT</DT>
19844 <DD>
19845 This token represents the current day of the month.
19846 For example, "23" or "09".
19847 It is always 2 digits.
19848 </DD>
19850 <DT>CURDAYOFWEEK</DT>
19851 <DD>
19852 This token represents the current day of the week.
19853 For example, "Sunday" or "Wednesday".
19854 </DD>
19856 <DT>CURDAYOFWEEKABBREV</DT>
19857 <DD>
19858 This token represents the current day of the week.
19859 For example, "Sun" or "Wed".
19860 </DD>
19862 <DT>CURMONTH</DT>
19863 <DD>
19864 This token represents the current month.
19865 For example, "10" or "9".
19866 </DD>
19868 <DT>CURMONTH2DIGIT</DT>
19869 <DD>
19870 This token represents the current month.
19871 For example, "10" or "09".
19872 It is always 2 digits.
19873 </DD>
19875 <DT>CURMONTHLONG</DT>
19876 <DD>
19877 This token represents the current month.
19878 For example, "October".
19879 </DD>
19881 <DT>CURMONTHABBREV</DT>
19882 <DD>
19883 This token represents the current month.
19884 For example, "Oct".
19885 </DD>
19887 <DT>CURYEAR</DT>
19888 <DD>
19889 This token represents the current year.
19890 For example, "1998" or "2001".
19891 </DD>
19893 <DT>CURYEAR2DIGIT</DT>
19894 <DD>
19895 This token represents the current year.
19896 For example, "98" or "01".
19897 It is always 2 digits.
19898 </DD>
19900 <DT>LASTMONTH</DT>
19901 <DD>
19902 This token represents last month.
19903 For example, if this is November (the 11th month),
19904 it is equal to "10" or if this is October (the 10th month),
19905 it is "9".
19906 It is possible that this and the other tokens beginning with LASTMONTH
19907 below could be useful when used with a Filtering Rule that
19908 has the "Beginning of Month" option set.
19909 </DD>
19911 <DT>LASTMONTH2DIGIT</DT>
19912 <DD>
19913 This token represents last month.
19914 For example, if this is November (the 11th month),
19915 it is equal to "10" or if this is October (the 10th month),
19916 it is "09".
19917 It is always 2 digits.
19918 </DD>
19920 <DT>LASTMONTHLONG</DT>
19921 <DD>
19922 This token represents last month.
19923 For example, if this is November the value is "October".
19924 </DD>
19926 <DT>LASTMONTHABBREV</DT>
19927 <DD>
19928 This token represents last month.
19929 For example, if this is November the value is "Oct".
19930 </DD>
19932 <DT>LASTMONTHYEAR</DT>
19933 <DD>
19934 This token represents what the year was a month ago.
19935 For example, if this is October, 1998, it is "1998".
19936 If this is January, 1998, it is "1997".
19937 </DD>
19939 <DT>LASTMONTHYEAR2DIGIT</DT>
19940 <DD>
19941 This token represents what the year was a month ago.
19942 For example, if this is October, 1998, it is "98".
19943 If this is January, 1998, it is "97".
19944 </DD>
19946 <DT>LASTYEAR</DT>
19947 <DD>
19948 This token represents last year.
19949 For example, if this is 1998, it equals "1997".
19950 It is possible that this
19951 could be useful when used with a Filtering Rule that
19952 has the "Beginning of Year" option set.
19953 </DD>
19955 <DT>LASTYEAR2DIGIT</DT>
19956 <DD>
19957 This token represents last year.
19958 For example, if this is 1998, it equals "97".
19959 It is always 2 digits.
19960 </DD>
19962 <DT>ROLENICK</DT>
19963 <DD>
19964 This token represents the nickname of the
19965 role currently being used. If no role is being used,
19966 then no text will be printed for this token.
19967 This token does not work with Filter Rule folder names.
19968 </DD>
19969 </DL>
19971 <P>
19972 <H1><EM>Token Available Only for <!--#echo var="VAR_reply-leadin"--></EM></H1>
19973 See the help for the
19974 <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option
19975 to see why you might want to use this.
19976 Since the <!--#echo var="VAR_reply-leadin"--> contains free text this token
19977 must be surrounded by underscores when used.
19979 <DL>
19980 <DT>NEWLINE</DT>
19981 <DD>
19982 This is an end of line marker.
19983 </DD>
19984 </DL>
19986 <P>
19987 <H1><EM>Token Available Only for Templates and Signatures</EM></H1>
19989 <DL>
19990 <DT>CURSORPOS</DT>
19991 <DD>
19992 This token is different from the others.
19993 When it is replaced it is replaced with nothing, but it sets an Alpine
19994 internal variable that tells the composer to start with the cursor
19995 positioned at the position where this token was.
19996 If both the template file and the signature file contain
19997 a "CURSORPOS" token, then the position in the template file
19998 is used.
19999 If there is a template file and neither it nor the signature file contains
20000 a "CURSORPOS" token, then the cursor is positioned
20001 after the end of the contents of the
20002 template file when the composer starts up.
20003 </DD>
20004 </DL>
20006 <P>
20007 <End of help on this topic>
20008 </BODY>
20009 </HTML>
20010 ======= h_reply_token_conditionals =======
20011 <HTML>
20012 <HEAD>
20013 <TITLE>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</TITLE>
20014 </HEAD>
20015 <BODY>
20016 <H1>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</H1>
20018 Conditional text inclusion may be used with
20019 the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
20020 in signature files, and in template files used in
20021 <A HREF="h_rules_roles">"roles"</A>.
20022 It may <EM>not</EM> be used with the
20023 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
20025 <P>
20026 There is a limited if-else capability for including text.
20027 The if-else condition is based
20028 on whether or not a given token would result in replacement text you
20029 specify.
20030 The syntax of this conditional inclusion is
20031 <P>
20032 <CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER>
20033 <P>
20034 The left parenthesis must follow the underscore immediately, with no
20035 intervening space.
20036 It means the token is expanded and the results of that expansion are
20037 compared against the "match_this" argument.
20038 If there is an exact match, then the "if_matched" text is used
20039 as the replacement text.
20040 Otherwise, the "if_not_matched" text is used.
20041 One of the most useful values for the "match_this" argument is
20042 the empty string, "".
20043 In that case the expansion is compared against the empty string.
20044 <P>
20045 Here's an example to make it clearer.
20046 This text could be included in one of your template files:
20047 <P>
20048 <CENTER><SAMP>_NEWS_("", "I'm replying to email", "I'm replying to news")</SAMP></CENTER>
20049 <P>
20050 If that is included in a template file that you are using while replying
20051 to a message (because you chose to use the role it was part of),
20052 and that message has a newsgroup header and a newsgroup in that header,
20053 then the text
20054 <P>
20055 <CENTER><SAMP>I'm replying to news</SAMP></CENTER>
20056 <P>
20057 will be included in the message you are about to compose.
20058 On the other hand, if the message you are replying to does not have
20059 a newsgroup, then the text
20060 <P>
20061 <CENTER><SAMP>I'm replying to email</SAMP></CENTER>
20062 <P>
20063 would be included instead.
20064 This would also work in signature files and in
20065 the "<!--#echo var="VAR_reply-leadin"-->" option.
20066 If the "match_this", "if_matched",
20067 or "if_not_matched" arguments contain
20068 spaces, parentheses, or commas;
20069 they have to be quoted with double quotation marks (like in the example
20070 above).
20071 If you want to include a literal quote (") in the text you must escape the
20072 quote by preceding it with a backslash (\) character.
20073 If you want to include a literal backslash character you must escape it
20074 by preceding it with another backslash.
20075 <P>
20076 The comma followed by "if_not_matched" is optional.
20077 If there is no "if_not_matched"
20078 present then no text is included if the not_matched case is true.
20079 Here's another example:
20080 <P>
20081 <CENTER><SAMP>_NEWS_("", "", "This msg was seen in group: _NEWS_.")</SAMP></CENTER>
20082 <P>
20083 Here you can see that tokens may appear in the arguments.
20084 The same is true for tokens with the conditional parentheses.
20085 They may appear in arguments,
20086 though you do have to be careful to get the quoting and escaping of
20087 nested double quotes correct.
20088 If this was in the signature file being used and you were replying to a message
20089 sent to comp.mail.pine the resulting text would be:
20090 <P>
20091 <CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER>
20092 <P>
20093 If you were replying to a message that wasn't sent to any newsgroup the
20094 resulting text would be a single blank line.
20095 The reason you'd get a blank line is because the end of the line is
20096 outside of the conditional, so is always included.
20097 If you wanted to get rid of that blank line you could do so by moving
20098 the end of line inside the conditional.
20099 In other words, it's ok to have multi-line
20100 "if_matched" or "if_not_matched" arguments in your
20101 template file.
20102 The text just continues until the next double quotation, even if it's not
20103 on the same line.
20104 <P>
20105 Here's an example for use in the "<!--#echo var="VAR_reply-leadin"-->":
20106 <P>
20107 <CENTER><SAMP>On _DAYDATE_, _FROM__CURNEWS_("", "", "seen in _CURNEWS_,") wrote</SAMP></CENTER>
20108 <P>
20109 If this was in your <!--#echo var="VAR_reply-leadin"--> and you were replying to a message
20110 while reading the newsgroup comp.mail.pine the resulting text would be:
20111 <P>
20112 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone, seen in comp.mail.pine, wrote:</SAMP></CENTER>
20113 <P>
20114 If you were replying to a message while reading an email folder instead
20115 of a newsgroup the resulting leadin text would be
20116 <P>
20117 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
20118 <P>
20119 Here's one more (contrived) example illustrating a matching argument
20120 that is not the empty string.
20121 <P>
20122 <CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER>
20123 <P>
20124 If this was the value of your "<!--#echo var="VAR_reply-leadin"-->" option and you
20125 were replying to
20126 a message that was sent today, then the value of the "<!--#echo var="VAR_reply-leadin"-->"
20127 would be
20128 <P>
20129 <CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER>
20130 <P>
20131 But if you were replying to a message sent on Oct. 27 (and that wasn't
20132 today) you would get
20133 <P>
20134 <CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER>
20135 <P>
20137 <End of help on this topic>
20138 </BODY>
20139 </HTML>
20140 ======= h_composer_cntxt_nick =======
20141 <HTML>
20142 <HEAD>
20143 <TITLE>Collection Nickname Explained</TITLE>
20144 </HEAD>
20145 <BODY>
20146 <H1>Collection Edit Help -- Nickname Field</H1>
20148 This field is provided so you can add a short nickname to use when
20149 referring to this collection within Alpine. Spaces are allowed, and
20150 you don't need to use double-quotes. However, the double-quote
20151 character is not allowed.
20152 <P>
20153 Look <A HREF="h_edit_nav_cmds">here</A>
20154 to see the available Editing and Navigation commands.
20155 <P>
20156 <End of help on this topic>
20157 </BODY>
20158 </HTML>
20159 ======= h_folder_server_syntax =======
20160 <HTML>
20161 <HEAD>
20162 <TITLE>Server Name Syntax</TITLE>
20163 </HEAD>
20164 <BODY>
20165 <H1>Server Name Syntax</H1>
20167 This help describes the syntax that may be used for server names
20168 that may be associated with remote folders or SMTP servers.
20170 <P>
20171 A server name is the hostname of the server.
20172 It's a good idea to use the host's fully-qualified network name.
20174 <P>
20175 <CENTER><SAMP>foo.example.com</SAMP></CENTER>
20176 <P>
20178 However, IP addresses are allowed if surrounded
20179 with square-brackets.
20181 <P>
20182 <CENTER><SAMP>[127.0.0.1]</SAMP></CENTER>
20183 <P>
20185 An optional network port number may be supplied by appending
20186 a colon (:) followed by the port number
20187 to the server name.
20188 By default, the IMAP port number, 143, is used.
20190 <P>
20191 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
20192 <P>
20194 Besides server name and optional port number, various other optional
20195 parameters may be supplied that alter Alpine's interaction with the server.
20196 A parameter is supplied by appending a slash (/) character followed by
20197 the parameter's name and,
20198 depending on the particular parameter, the value assigned to that
20199 name, to the server name (and optional port number).
20200 Parameter names are <EM>not</EM> case sensitive.
20201 Currently supported parameters include:
20203 <DL>
20205 <DT>User</DT>
20206 <DD>This parameter requires an associated value, and is intended to
20207 provide the username identifier with which to establish the server
20208 connection.
20209 If your SMTP server offers SMTP AUTH authentication, adding this
20210 parameter to the
20211 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
20212 option will cause Alpine to attempt to authenticate to the server using the
20213 supplied username.
20214 Similarly, if your NNTP server offers NNTP "AUTHINFO SASL"
20215 or "AUTHINFO USER" authentication, adding this parameter to the
20216 <A HREF="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></A>
20217 option (or to the server name for any folder collection using NNTP)
20218 will cause Alpine to attempt
20219 to authenticate to the server using the supplied username.
20220 An example might be:
20222 <P>
20223 <CENTER><SAMP>/user=katie</SAMP></CENTER>
20224 <P>
20226 </DD>
20228 <DT>TLS</DT>
20229 <DD>
20230 Normally, when a new connection is made an attempt is made to
20231 negotiate a secure (encrypted) session using Transport Layer Security (TLS).
20232 If that fails then a non-encrypted connection will be attempted instead.
20233 This is a unary parameter indicating communication with the server must
20234 take place over a TLS connection. If the attempt to use TLS fails then
20235 this parameter will cause the connection to fail instead of falling
20236 back to an unsecure connection.
20238 <P>
20239 <CENTER><SAMP>/tls</SAMP></CENTER>
20240 <P>
20242 </DD>
20244 <DT>SSL</DT>
20245 <DD>
20246 This is a unary parameter indicating communication with the server should
20247 take place over a Secure Socket Layer connection. The server must support
20248 this method, and be prepared to accept connections on the appropriate
20249 port (993 by default).
20250 Alpine must be linked with an SSL library for this option to be operational.
20252 <P>
20253 <CENTER><SAMP>/ssl</SAMP></CENTER>
20254 <P>
20256 </DD>
20258 <DT>TLS1</DT>
20259 <DD>
20260 This parameter indicates that the connection to the server will be made
20261 over the SSL port, but using the TLSv1 protocol, instead of the usual
20262 SSLv3 or SSLv2 protocols.
20263 Alpine must be linked with an SSL library for this option to be operational.
20265 <P>
20266 <CENTER><SAMP>/tls1</SAMP></CENTER>
20267 <P>
20269 </DD>
20271 <DT>DTLS1</DT>
20272 <DD>
20273 This parameter indicates that the connection to the server will be made
20274 over the SSL port, but using the DTLSv1 protocol, instead of the usual
20275 SSLv3 or SSLv2 protocols.
20276 Alpine must be linked with an SSL library for this option to be operational.
20278 <P>
20279 <CENTER><SAMP>/dtls1</SAMP></CENTER>
20280 <P>
20282 </DD>
20284 <DT>TLS1_1</DT>
20285 <DD>
20286 This parameter indicates that the connection to the server will be made
20287 over the SSL port, but using the TLSv1.1 protocol, instead of the usual
20288 SSLv3 or SSLv2 protocols.
20289 Alpine must be linked with an SSL library for this option to be operational.
20291 <P>
20292 <CENTER><SAMP>/tls1_1</SAMP></CENTER>
20293 <P>
20295 </DD>
20297 <DT>TLS1_2</DT>
20298 <DD>
20299 This parameter indicates that the connection to the server will be made
20300 over the SSL port, but using the TLSv1.2 protocol, instead of the usual
20301 SSLv3 or SSLv2 protocols.
20302 Alpine must be linked with an SSL library for this option to be operational.
20304 <P>
20305 <CENTER><SAMP>/tls1_2</SAMP></CENTER>
20306 <P>
20308 </DD>
20311 <DT>NoValidate-Cert</DT>
20312 <DD>Do not validate certificates (for TLS or SSL connections) from the server.
20313 This is needed if the server uses self-signed certificates or if Alpine
20314 cannot validate the certificate for some other known reason.
20315 <P>
20316 </DD>
20318 <DT>Anonymous</DT>
20319 <DD>This is a unary parameter (that means it does not have a value)
20320 indicating that the connection be logged in as
20321 "anonymous" rather than a specific user.
20322 Not all servers offer anonymous
20323 access; those which do generally only offer read-only access to certain
20324 "public" folders.
20326 <P>
20327 <CENTER><SAMP>/anonymous</SAMP></CENTER>
20328 <P>
20330 </DD>
20332 <DT>Secure</DT>
20333 <DD>This is a unary parameter indicating that the connection use the
20334 most secure authentication method mutually supported by Alpine and the
20335 server.
20336 Alpine is capable of authenticating connections to
20337 the server using several methods.
20338 By default, Alpine will attempt each
20339 method until either a connection is established or the
20340 list of methods is exhausted.
20341 This parameter causes Alpine to instead fail
20342 the connection if the first (generally most "secure") method fails.
20344 <P>
20345 <CENTER><SAMP>/secure</SAMP></CENTER>
20346 <P>
20348 </DD>
20350 <DT>Submit</DT>
20351 <DD>This is a unary parameter for use with the
20352 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> option.
20353 It indicates that the connection should be made to the Submit server
20354 (<A HREF="http://www.ietf.org/rfc/rfc2476.txt">RFC 3676</A>)
20355 (port 587) instead of the SMTP port (25).
20356 At the time this help was written the submit option was equivalent to
20357 specifying port 587.
20359 <P>
20360 <CENTER><SAMP>/submit</SAMP></CENTER>
20361 <P>
20362 or
20363 <P>
20364 <CENTER><SAMP>host:587</SAMP></CENTER>
20365 <P>
20367 </DD>
20369 <DT>Debug</DT>
20370 <DD>This is a unary parameter indicating that the connection be established
20371 in a verbose mode. Basically, it causes Alpine to log the communication with
20372 the server in Alpine's debug file.
20373 Normally, the pine -d command-line flag would be used instead.
20374 <P>
20375 </DD>
20377 <DT>NoRsh</DT>
20378 <DD>By default, Alpine attempts to login using "rsh",
20379 the UNIX remote shell program.
20380 Including "NoRsh" will cause connections to this server to skip
20381 the "rsh" attempt.
20382 This might be useful to avoid long timeouts caused by rsh firewalls, for
20383 example.
20384 <P>
20385 </DD>
20387 <DT>Loser</DT>
20388 <DD>This option makes sense only for IMAP servers that do not perform
20389 a SEARCH command correctly. If your filtering rules
20390 fail to filter some messages, that should have been filtered, then this
20391 option will make Alpine download all data necessary to perform that search.
20392 There is a performance penalty when using this option. Downloading the
20393 data to perfom the search will take longer than requesting the IMAP
20394 server to perform the filtering, but the filtering will be done correctly.
20395 <P>
20396 </DD>
20399 <DT>Service</DT>
20400 <DD>This parameter requires an associated value. The default value is
20401 "IMAP" which indicates communication with the server based
20402 on the IMAP4rev1 protocol (defined in RFC 3501 -- see
20403 <A HREF="http://www.imap.org/docs/rfc3501.html">http://www.imap.org/docs/rfc3501.html</A>).</DD>
20405 Other service values include:
20406 <DL>
20407 <DT>NNTP</DT>
20408 <DD>This value indicates communication with the server takes place via
20409 the Network News Transfer Protocol. Use this to define a collection
20410 of newsgroups on a remote news server. So
20412 <P>
20413 <CENTER><SAMP>/service=NNTP</SAMP></CENTER>
20414 <P>
20415 or just
20416 <P>
20417 <CENTER><SAMP>/NNTP</SAMP></CENTER>
20418 <P>
20420 is the way to specify NNTP access.
20421 <P>
20422 </DD>
20424 <DT>POP3</DT>
20425 <DD>This value indicates communication with the server takes place via the
20426 Post Office Protocol 3 protocol.
20428 <P>
20429 <CENTER><SAMP>/service=POP3</SAMP></CENTER>
20430 <P>
20431 or just
20432 <P>
20433 <CENTER><SAMP>/POP3</SAMP></CENTER>
20434 <P>
20436 Note that there are several important issues
20437 to consider when selecting this option:
20438 <OL>
20439 <LI> POP3 provides access to only your INBOX. In other words,
20440 secondary folders such as your "saved-messages" are inaccessible.
20441 <LI> Alpine's implementation of POP3 does not follow the traditional POP
20442 model and will leave your mail on the server. Refer to the
20443 <A HREF="h_maildrop">Mail Drop</A> functionality for a possible way around this problem.
20444 <LI> See the discussion about new-mail checking in <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
20445 </OL>
20446 </DD>
20447 </DL>
20448 </DL>
20450 <P>
20451 Note that it is possible to include more than one parameter in a server
20452 specification by concatenating the parameters. For example:
20454 <P>
20455 <CENTER><SAMP>foo.example.com:port/user=katie/novalidate-cert/debug</SAMP></CENTER>
20456 <P>
20458 <P>
20459 <End of help on this topic>
20460 </BODY>
20461 </HTML>
20462 ======= h_composer_cntxt_server =======
20463 <HTML>
20464 <HEAD>
20465 <TITLE>Collection Server: Explained</TITLE>
20466 </HEAD>
20467 <BODY>
20468 <H1>Collection Edit Help -- Server Field</H1>
20470 This collection's "Server:" definition indicates the
20471 hostname of the server providing access to the folders in this
20472 collection.
20473 The syntax of this server name is the same as for other server names used
20474 in remote folder names in
20475 Alpine and is described
20476 <A HREF="h_folder_server_syntax">here</A>.
20478 <P>
20479 <End of help on this topic>
20480 </BODY>
20481 </HTML>
20482 ======= h_composer_cntxt_path =======
20483 <HTML>
20484 <HEAD>
20485 <TITLE>Collection Path: Explained</TITLE>
20486 </HEAD>
20487 <BODY>
20488 <H1>Collection Edit Help -- Path Field</H1>
20490 The collection's "Path:" definition indicates the location
20491 of the folders in this collection. If the path or any of its components
20492 do not exist, Alpine will prompt you for their creation when exiting the
20493 Add/Change screen.
20495 <P>
20496 By default the path is interpreted as defining a section of your personal
20497 folder area. This area and how you specify it are defined by the
20498 server, if one is specified in the collection, or, typically, the home
20499 directory if no server is defined.
20501 <P>
20502 To define a collection outside the default "area", prefix
20503 the path with the "namespace" to use when interpreting the
20504 given path. If a namespace is specified, the Path begins with the
20505 sharp, "#", character followed by the name of the namespace
20506 and then the namespace's path-element-delimiter. Aside from the
20507 path's format, namespaces can also imply access rights, content
20508 policy, audience, location, and, occasionally, access methods.
20510 <P>
20511 Each server exports its own set (possibly of size one) of
20512 namespaces. Hence, it's likely communication with your server's
20513 administrator will be required for specific configurations. Some of
20514 the more common namespaces, however, include:
20516 <DL>
20517 <DT>#news.</DT>
20518 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
20519 names are hierarchically defined with each level delimited by a period.
20520 </DD>
20521 <DT>#public/</DT>
20522 <DD>This specifies a folder area that the server may export to the general
20523 public.
20524 </DD>
20525 <DT>#shared/</DT>
20526 <DD>This specifies a folder area that the folder may export to groups
20527 of users.
20528 </DD>
20529 <DT>#ftp/</DT>
20530 <DD>This specifies a folder area that is the same as that it may have
20531 exported via the "File Transfer Protocol".
20532 </DD>
20533 <DT>#mh/</DT>
20534 <DD>This specifies the personal folder area associated with folders
20535 and directories that were created using the MH message handling system.
20536 </DD>
20537 </DL>
20538 <P>
20540 In addition, the server may support access to other user's folders,
20541 provided you have suitable permissions. Common methods use a prefix
20542 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
20543 indicate the root of the other user's folder area.
20545 <P>
20546 No, nothing's simple.
20548 <P>
20549 <End of help on this topic>
20550 </BODY>
20551 </HTML>
20552 ======= h_composer_cntxt_view =======
20553 <HTML>
20554 <HEAD>
20555 <TITLE>Collection View: Explained</TITLE>
20556 </HEAD>
20557 <BODY>
20558 <H1>Collection Edit Help -- View Field</H1>
20560 The collection's "View:" definition provides a way to limit
20561 the displayed list of folders within a collection. By default, only
20562 folders that contain the specified characters anywhere in their name
20563 are shown in the collection's folder list.
20565 <P>
20566 Additionally, you can use a wildcard character to better control
20567 the list of folders selected for display. The wildcard specifier is
20568 the star, "*", character.
20570 <P>
20571 So, for example, to define a collection of all folders ending with
20572 "c", you'd specify a view of "*c" (without the
20573 quote characters!). Or, similarly, to define a collection of folders
20574 whose names start with "a" and end with "z", you'd
20575 specify a view of "a*z".
20577 <P>
20578 <End of help on this topic>
20579 </BODY>
20580 </HTML>
20581 ======= h_composer_abook_add_server =======
20582 <HTML>
20583 <HEAD>
20584 <TITLE>Addressbook Server Name Field Explained</TITLE>
20585 </HEAD>
20586 <BODY>
20587 This field should be left blank if the address book is stored in a regular
20588 file on this system. If it is a remote address book stored on an IMAP
20589 server then this is the name of that IMAP server.
20590 <P>
20591 Look <A HREF="h_edit_nav_cmds">here</A>
20592 to see the available Editing and Navigation commands.
20593 <P>
20594 <End of help on this topic>
20595 </BODY>
20596 </HTML>
20597 ======= h_composer_abook_add_folder =======
20598 <HTML>
20599 <HEAD>
20600 <TITLE>Addressbook Folder Name Field Explained</TITLE>
20601 </HEAD>
20602 <BODY>
20603 For a remote address book (one for which the Server Name is filled in)
20604 this is the name of a folder on the remote server. The address book data
20605 will be stored in this folder. This folder should be used only for
20606 storing this single address book, not for other address books or for
20607 other messages.
20608 <P>
20609 For a local address book (one for which the Server Name is not filled in)
20610 this is the name of a file in which the address book will be stored.
20611 The file is in the same directory as the Alpine configuration file if the
20612 configuration file is local.
20613 If the configuration file is remote, then this will be in the home directory
20614 for Unix Alpine and in the directory specified by the
20615 "-aux local_directory" command line argument.
20616 <P>
20617 Look <A HREF="h_edit_nav_cmds">here</A>
20618 to see the available Editing and Navigation commands.
20619 <P>
20620 <End of help on this topic>
20621 </BODY>
20622 </HTML>
20623 ======= h_composer_abook_add_nick =======
20624 <HTML>
20625 <HEAD>
20626 <TITLE>Addressbook NickName Field Explained</TITLE>
20627 </HEAD>
20628 <BODY>
20629 This is just an optional nickname for this address book. If present, it
20630 is used in some of the displays and error messages in the address book
20631 maintenance screens. It is for your convenience only and serves no
20632 other purpose.
20633 <P>
20634 Look <A HREF="h_edit_nav_cmds">here</A>
20635 to see the available Editing and Navigation commands.
20636 <P>
20637 <End of help on this topic>
20638 </BODY>
20639 </HTML>
20640 ======= h_composer_qserv_cn =======
20641 <HTML>
20642 <HEAD>
20643 <TITLE>Directory Query Form Explained</TITLE>
20644 </HEAD>
20645 <BODY>
20647 Fill in as many of these fields as you wish to narrow down your
20648 search. All the fields you fill in must match in order for an entry
20649 to be returned. You may use the wildcard character "*" in
20650 any of the fields, it matches any zero or more characters at that
20651 point in the string. There are no implicit wildcards, so the match is
20652 exact unless you include wildcards.
20653 <P>
20655 Note that if an attribute isn't present at all, then the match will fail.
20656 For example, if a server doesn't support the Locality attribute, then no
20657 matter what you put in the Locality field (other than leaving it empty)
20658 the search will fail.
20659 <P>
20661 This field, the Common Name field, is typically a person's full name.
20662 <P>
20664 <H1>EDITING and NAVIGATION COMMANDS</H1>
20665 <!--chtml if pinemode="function_key"-->
20666 <PRE>
20667 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
20668 ^B (Left Arrow) Back character | ^D Delete current character
20669 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
20670 ^P (Up Arrow) Previous line |
20671 ^N (Down Arrow) Next line | F9 Cut marked text or
20672 ^A Beginning of line | delete current line
20673 ^E End of line | F10 Undelete line(s)
20674 F7 Previous page |
20675 F8 Next page |-------------------------------------
20676 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
20677 ----------------------------------------|
20678 EXIT COMMANDS | GENERAL COMMANDS | F5 Restore previous search
20679 F2 Cancel | F1 Get help |
20680 F3 Search | ^Z Suspend | ^L Redraw Screen
20681 </PRE>
20682 <!--chtml else-->
20683 <PRE>
20684 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
20685 ^B (Left Arrow) Back character | ^D Delete current character
20686 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
20687 ^P (Up Arrow) Previous line |
20688 ^N (Down Arrow) Next line | ^K Cut marked text or
20689 ^A Beginning of line | delete current line
20690 ^E End of line | ^U Undelete line(s)
20691 ^Y Previous page |
20692 ^V Next page |-------------------------------------
20693 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
20694 ----------------------------------------|
20695 EXIT COMMANDS | GENERAL COMMANDS | ^R Restore previous search
20696 ^C Cancel | ^G Get help |
20697 ^X Search | ^Z Suspend | ^L Redraw Screen
20698 </PRE>
20699 <!--chtml endif-->
20700 <P><UL>
20701 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20702 </UL><P>
20703 <End of help on this topic>
20704 </BODY>
20705 </HTML>
20706 ======= h_composer_qserv_sn =======
20708 The Surname is usually the family name of a person.
20710 <End of help on this topic>
20711 ======= h_composer_qserv_gn =======
20713 This is the part of a person's name that isn't the surname or initials.
20715 <End of help on this topic>
20716 ======= h_composer_qserv_mail =======
20718 This is the email address of a person.
20720 <End of help on this topic>
20721 ======= h_composer_qserv_org =======
20723 This is the organization a person belongs to.
20725 <End of help on this topic>
20726 ======= h_composer_qserv_unit =======
20728 This is the organizational unit a person belongs to.
20730 <End of help on this topic>
20731 ======= h_composer_qserv_country =======
20733 This is the country a person belongs to.
20735 <End of help on this topic>
20736 ======= h_composer_qserv_state =======
20738 This is the state a person belongs to.
20740 <End of help on this topic>
20741 ======= h_composer_qserv_locality =======
20743 This is the locality a person belongs to.
20745 <End of help on this topic>
20746 ======= h_composer_qserv_custom =======
20748 This one is for advanced users only! If you put something in this field,
20749 then the rest of the fields are ignored.
20751 This field may be set to the string representation of an LDAP search
20752 filter (see RFC1960). Here are some examples:
20754 To search for an entry with a surname equal to "clinton" you could set
20755 the custom filter to:
20757 (sn=clinton)
20759 This is equivalent to putting "clinton" in the SurName field.
20760 To search for an entry that has a surname that begins with "clint" and
20761 has a givenname equal to "william" you could use:
20763 (&(sn=clint*)(givenname=william))
20765 This is equivalent to setting the SurName field to "clint*" and the
20766 GivenName field to "william".
20767 To search for an entry where either the common name OR the email address
20768 contains "abcde" you could use:
20770 (|(cn=*abcde*)(mail=*abcde*))
20772 That isn't equivalent to anything you can do by setting the other fields
20773 because of the OR.
20775 <End of help on this topic>
20776 ======= h_composer_qserv_qq =======
20778 This one is a little different from the rest of the categories. It causes
20779 a search to be formed from the configured search filter that you filled
20780 in when you added the directory server to your configuration. It can also
20781 be combined with the other fields if you'd like.
20783 <End of help on this topic>
20784 ======= h_address_format =======
20785 <HTML>
20786 <HEAD>
20787 <TITLE>INTERNET EMAIL ADDRESS FORMAT</TITLE>
20788 </HEAD>
20789 <BODY>
20790 <H1>INTERNET EMAIL ADDRESS FORMAT</H1>
20792 A valid email address on the Internet has a username, an "@" sign,
20793 and then a domain, with no spaces.
20794 For example, jsmith@art.example.com might be the email address
20795 of a person
20796 with the username "jsmith" who has an account in the domain
20797 "art.example.com". The number of dot-separated segments on the
20798 right of the "@" sign can vary - a shorter example would be
20799 isabelle@elsewhere.edu (the shortest possible form: here, only the
20800 organization's domain is specified after the "@" sign); a longer
20801 example would be
20802 jsingh@shakti.edutech.example.com
20803 (here, the name of the host "shakti" in the domain
20804 edutech.example.com is also specified).
20805 <P>
20806 If you do not know the exact email address of someone you want to write
20807 to, ask them what it is using other means of communication than email; or
20808 use the tools for
20809 finding people's addresses that are available on the Internet.
20810 <P>
20811 If you are sending to someone on the same system as you are, you can leave
20812 the "@" sign and all the information to its right off of the
20813 address, and Alpine will fill it in automatically,
20814 unless the feature
20815 <A HREF="h_config_compose_rejects_unqual">"<!--#echo var="FEAT_compose-rejects-unqualified-addrs"-->"</A> is set in SETUP CONFIGURATION.
20816 <P>
20818 When an email address you send a message to is not reachable -- either because
20819 it is simply an incorrect address, or because email can temporarily not be
20820 delivered to it due to a technical problem on the way to or at the recipient's
20821 end -- you will almost always get an error notification email message back.
20822 <P>
20823 If you encounter problems with, or have questions about, email delivery or
20824 email address syntax, contact your local network computing consultants.
20825 <P><UL>
20826 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20827 </UL>
20828 <P>
20829 <End of help on this topic>
20830 </BODY>
20831 </HTML>
20832 ======= h_flag_user_flag =======
20833 <HTML>
20834 <HEAD>
20835 <TITLE>STATUS FLAG: User Defined Keyword</TITLE>
20836 </HEAD>
20837 <BODY>
20838 <H1>STATUS FLAG: User Defined Keyword</h1>
20840 This is a keyword that is defined for this folder.
20841 It was most likely defined by the owner of the folder.
20842 Alpine will not set or clear this flag on its own.
20844 <P><UL>
20845 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20846 </UL><P>
20847 <End of help on this topic>
20848 </BODY>
20849 </HTML>
20850 ======= h_flag_important =======
20851 <html>
20852 <title>STATUS FLAG: Important</title>
20853 <body>
20854 <h1>STATUS FLAG: Important</h1>
20857 The <EM>Important</EM> flag, indicated by an asterisk in Alpine's
20858 MESSAGE INDEX
20859 screen, can only be set by the user, and is intended to be used in
20860 whatever fashion makes sense to you. You are the only one that can set or
20861 clear it.
20863 <P>
20864 <End of help on this topic>
20865 </BODY>
20866 </HTML>
20867 ======= h_flag_new =======
20868 <html>
20869 <title>STATUS FLAG: New</title>
20870 <body>
20871 <h1>STATUS FLAG: New</h1>
20874 The <EM>New</EM> flag, indicated by the letter 'N' in Alpine's
20875 MESSAGE INDEX screen,
20876 is automatically set when messages are delivered to your Inbox (or other
20877 folder specified outside of Alpine). Likewise, it is cleared automatically
20878 the first time you read the message it is associated with.
20880 <P>
20881 Sometimes it's helpful in prioritizing your mail. For example, perhaps
20882 a message isn't weighty enough to assign it an <A HREF="h_flag_important">Important</A> flag, but
20883 you'd like to be reminded of it next time you read mail. This can be done
20884 easily by <A HREF="h_common_flag">explicitly</A> resetting the <EM>New</EM> flag.
20887 <P>
20888 <End of help on this topic>
20889 </BODY>
20890 </HTML>
20891 ======= h_flag_answered =======
20892 <html>
20893 <title>STATUS FLAG: Answered</title>
20894 <body>
20895 <h1>STATUS FLAG: Answered</h1>
20897 The <EM>Answered</EM> flag, indicated by the letter 'A' in Alpine's
20898 MESSAGE INDEX
20899 screen, is automatically set when you reply to a message. This flag is not
20900 automatically cleared.
20902 <P>
20903 <End of help on this topic>
20904 </BODY>
20905 </HTML>
20906 ======= h_flag_forwarded =======
20907 <html>
20908 <title>STATUS FLAG: Forwarded</title>
20909 <body>
20910 <h1>STATUS FLAG: Forwarded</h1>
20912 The <EM>Forwarded</EM> flag, indicated by the letter 'F' in Alpine's
20913 MESSAGE INDEX
20914 screen, is automatically set when you forward a message. This flag is not
20915 automatically cleared.
20917 <P>
20918 <End of help on this topic>
20919 </BODY>
20920 </HTML>
20921 ======= h_flag_deleted =======
20922 <html>
20923 <title>STATUS FLAG: Deleted</title>
20924 <body>
20925 <h1>STATUS FLAG: Deleted</h1>
20927 The <EM>Deleted</EM> flag, indicated by the letter 'D' in Alpine's
20928 MESSAGE INDEX
20929 screen, is set when you use the ""D Delete" command.
20930 It is cleared
20931 when you use the "U Undelete" command.
20933 <P>
20934 Messages marked with this flag will be permanently removed from
20935 the folder when you issue the <A HREF="h_index_cmd_expunge">Expunge</A>
20936 command, or
20937 when you indicate acceptance of their removal upon leaving the folder.
20939 <P>
20940 Note, there can be other actions implicit in the
20941 "D Delete" command,
20942 such as advancing to the next message, that may be momentarily undesirable.
20943 For this reason, it's sometimes useful to set or clear the <EM>Deleted</EM>
20944 flag <A HREF="h_common_flag">explicitly</A>.
20946 <P>
20947 <End of help on this topic>
20948 </BODY>
20949 </HTML>
20950 ====== h_config_incoming_timeo ======
20951 <HTML>
20952 <HEAD>
20953 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></TITLE>
20954 </HEAD>
20955 <BODY>
20956 <H1>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></H1>
20958 This option has no effect unless the feature
20959 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
20960 is set, which in turn has no effect unless
20961 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
20962 is set.
20963 <P>
20964 Sets the time in seconds that Alpine will
20965 attempt to open a network connection used for monitoring for Unseen
20966 messages in Incoming Folders. The default is 5.
20967 If a connection has not completed within this many seconds Alpine will
20968 give up and consider it a failed connection.
20969 <P>
20970 <UL>
20971 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20972 </UL><P>
20973 <End of help on this topic>
20974 </BODY>
20975 </HTML>
20976 ====== h_config_psleep ======
20977 <HTML>
20978 <HEAD>
20979 <TITLE>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</TITLE>
20980 </HEAD>
20981 <BODY>
20982 <H1>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</H1>
20984 <P>
20985 In the good old days a mailcap viewer was used to examine an
20986 attachment before saving it, and after viewing the attachment control
20987 would return to the operating system when the viewer was closed. Therefore,
20988 when the mailcap viewer returned control to the operating system, it
20989 could be assumed that the user who opened the attachment was done
20990 examining it, and the copy of the attachment that was used, could be removed.
20992 <P>
20993 However, today this assumption is not longer valid. Some viewers return
20994 control to the operating system before they actually read the attachment
20995 to be examined. This causes Alpine to delete the attachment before it
20996 is read by the viewer, causing the viewer to fail opening the attachment.
20998 <P>
20999 In order to work around this problem, Alpine checks, after the viewer has
21000 returned control to the operating system, if there is any process that is
21001 using the attachment. This variable controls the number of seconds that
21002 must elapse between checks. Once it is found that no process is using the
21003 attachment, this is removed.
21005 <P>
21006 The minimum value for this variable is 60 (checks will be made once per
21007 minute), and the maximum value is 600 (checks will be made once every 10
21008 minutes). The default value is 60.
21010 <P>
21011 <UL>
21012 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21013 </UL><P>
21014 <End of help on this topic>
21015 </BODY>
21016 </HTML>
21017 ====== h_config_incoming_interv ======
21018 <HTML>
21019 <HEAD>
21020 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval"--></TITLE>
21021 </HEAD>
21022 <BODY>
21023 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval"--></H1>
21025 This option has no effect unless the feature
21026 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21027 is set, which in turn has no effect unless
21028 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21029 is set.
21030 <P>
21031 This option specifies, in seconds, how often Alpine will check
21032 for new mail and state changes in Incoming Folders when Incoming Folders
21033 Checking is turned on.
21034 The default is 3 minutes (180).
21035 This value applies only to folders that are local to the system that
21036 Alpine is running on or that are accessed using the IMAP protocol.
21037 The similar option
21038 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>
21039 applies to all other monitored folders.
21040 <P>
21041 <UL>
21042 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21043 </UL><P>
21044 <End of help on this topic>
21045 </BODY>
21046 </HTML>
21047 ====== h_config_incoming_second_interv ======
21048 <HTML>
21049 <HEAD>
21050 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></TITLE>
21051 </HEAD>
21052 <BODY>
21053 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></H1>
21055 This option has no effect unless the feature
21056 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21057 is set, which in turn has no effect unless
21058 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21059 is set.
21060 <P>
21061 This option together with the option
21062 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
21063 specifies, in seconds, how often Alpine will check
21064 for new mail and state changes in Incoming Folders when Incoming Folders
21065 Checking is turned on.
21066 The default for this option is 3 minutes (180).
21067 For folders that are local to this system or
21068 that are accessed using the IMAP protocol
21069 the value of the option
21070 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
21071 is used.
21072 For all other monitored folders, the value of this option is used.
21073 <P>
21074 The reason there are two separate options is because it is usually
21075 less expensive to check local and IMAP folders than it is to check
21076 other types, like POP or NNTP folders.
21077 You may want to set this secondary value to a higher number than
21078 the primary check interval.
21079 <P>
21080 <UL>
21081 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21082 </UL><P>
21083 <End of help on this topic>
21084 </BODY>
21085 </HTML>
21086 ====== h_config_incoming_list ======
21087 <HTML>
21088 <HEAD>
21089 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-list"--></TITLE>
21090 </HEAD>
21091 <BODY>
21092 <H1>OPTION: <!--#echo var="VAR_incoming-check-list"--></H1>
21094 This option has no effect unless the feature
21095 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21096 is set, which in turn has no effect unless
21097 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21098 is set.
21099 <P>
21100 When monitoring the Incoming Message Folders for Unseen messages Alpine will
21101 normally monitor all Incoming Folders.
21102 You may use this option to restrict the list of monitored folders to a
21103 subset of all Incoming Folders.
21104 <P>
21105 <UL>
21106 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21107 </UL><P>
21108 <End of help on this topic>
21109 </BODY>
21110 </HTML>
21111 ====== h_config_pers_name ======
21112 <HTML>
21113 <HEAD>
21114 <TITLE>OPTION: <!--#echo var="VAR_personal-name"--></TITLE>
21115 </HEAD>
21116 <BODY>
21117 <H1>OPTION: <!--#echo var="VAR_personal-name"--></H1>
21119 This value is used to determine the full name part of the "From" address
21120 on messages you send.
21121 <!--chtml if pinemode="os_windows"-->
21122 PC-Alpine requires that this be set in order to properly construct the "From" address.
21123 <!--chtml else-->
21124 If unset, Unix Alpine will obtain your full name from
21125 the system password file. PC-Alpine, on the other hand, requires that this be set.
21126 <!--chtml endif-->
21127 <P>
21128 If you want to change the value of what gets included in the From header
21129 in messages you send (other than just the Personal Name)
21130 look <A HREF="h_config_change_your_from">here</A> for a description.
21131 <P><UL>
21132 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21133 </UL><P>
21134 <End of help on this topic>
21135 </BODY>
21136 </HTML>
21137 ====== h_config_pruned_folders ======
21138 <html>
21139 <header>
21140 <title>OPTION: <!--#echo var="VAR_pruned-folders"--></title>
21141 </header>
21142 <body>
21143 <h1>OPTION: <!--#echo var="VAR_pruned-folders"--></h1>
21145 This variable allows you to define a list of one or more folders that
21146 Alpine will offer to prune for you in the same way it automatically offers
21147 to prune your "sent-mail" folder each month.
21148 Each folder in this list must be a folder in your default folder collection
21149 (the first folder collection if you have more than one), and it is just
21150 the relative name of the folder in the collection, not the fully-qualified name.
21151 It is similar to sent-mail.
21152 Instead of something like
21153 <P>
21154 <CENTER><SAMP><!--#echo var="VAR_pruned-folders"-->={servername}mail/folder</SAMP></CENTER>
21155 <P>
21156 the correct value to use would be
21157 <P>
21158 <CENTER><SAMP>folder</SAMP></CENTER>
21159 <P>
21160 There is an assumption here that your first collection is the folders in
21161 <P>
21162 <CENTER><SAMP>{servername}mail</SAMP></CENTER>
21163 <P>
21165 Once a month, for each folder listed, Alpine will offer to move
21166 the contents of the folder to a new folder of the same name but with
21167 the previous month's date appended. Alpine will then look for any such
21168 date-appended folder names created for a previous month, and offer each
21169 one it finds for deletion.
21170 <P>
21172 If you decline the first offer, no mail is moved and no new folder is
21173 created.
21174 <P>
21176 The new folders will be created
21177 in your default folder collection.
21178 <P>
21180 <UL>
21181 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21182 </UL><P>
21183 <End of help on this topic>
21184 </body>
21185 </html>
21186 ====== h_config_upload_cmd ======
21187 <HTML>
21188 <HEAD>
21189 <TITLE>OPTION: <!--#echo var="VAR_upload-command"--></TITLE>
21190 </HEAD>
21191 <BODY>
21192 <H1>OPTION: <!--#echo var="VAR_upload-command"--></H1>
21194 This option affects the behavior of the Composer's "Read File"
21195 (^R in the message body) and "Attach File" (^J in the header)
21196 commands. It specifies
21197 a Unix program name, and any necessary command line arguments, that Alpine can
21198 use to transfer files from your personal computer into messages that you are
21199 composing.<P>
21201 <B>Note:</B> this facility is intended for use with serial line transfer
21202 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
21203 to work with TCP/IP file transfer programs such as ftp.<P>
21205 If a program is specified, the commands listed above are modified to offer a
21206 subcommand (^Y) to activate the transfer. Obviously, the Unix program
21207 specified here must match the transfer program or protocol available on the
21208 personal computer.<P>
21210 Alpine expects to exchange uploaded data via a file on your Unix system. When
21211 the specified upload program finishes, Alpine expects the uploaded data to be
21212 contained in this file.<P>
21214 When upload is invoked via the "Read File" subcommand, Alpine
21215 generates a
21216 temporary file name that it will pass to the specified Unix program. Alpine
21217 will read the resulting uploaded text from this file and then delete it when
21218 the upload command is finished.<P>
21220 When upload is invoked via the "Attach File" subcommand, Alpine will
21221 prompt
21222 you for the name of the file that is to contain the uploaded information that
21223 it is to attach. Alpine will attach this file to the composition, but will
21224 <B>not</B> delete this file after the upload command is finished.<P>
21226 The special token "_FILE_" may be included among the Unix program's
21227 command
21228 line arguments. Alpine will replace this symbol with the name of the file
21229 being used to exchange the uploaded information. This token allows you to
21230 position the file name where it is required in the Unix program's command
21231 line arguments.<P>
21233 If the "_FILE_" token is not present in the specified command, the
21234 temporary file's name is automatically appended to the specified Unix
21235 program. In other words, you don't need to use "_FILE_" if it is the
21236 <B>last</B> command line argument.
21237 <P><UL>
21238 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21239 </UL><P>
21240 <End of help on this topic>
21241 </BODY>
21242 </HTML>
21243 ====== h_config_upload_prefix ======
21244 <HTML>
21245 <HEAD>
21246 <TITLE>OPTION: <!--#echo var="VAR_upload-command-prefix"--></TITLE>
21247 </HEAD>
21248 <BODY>
21249 <H1>OPTION: <!--#echo var="VAR_upload-command-prefix"--></H1>
21251 This option is used in conjunction with the <!--#echo var="VAR_upload-command"--> option.
21252 It defines text to be written to the terminal emulator (via standard output)
21253 immediately prior to starting upload command. This is useful for
21254 integrated serial line file transfer agents that permit command passing
21255 (e.g., Kermit's APC method).<P>
21257 The special token "_FILE_" may be included in the string specification.
21258 That symbol will be replaced with the (Alpine-created) name of the temporary
21259 file in which Alpine will expect to find the uploaded file.
21260 <P><UL>
21261 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21262 </UL><P>
21263 <End of help on this topic>
21264 </BODY>
21265 </HTML>
21266 ====== h_config_download_cmd ======
21267 <HTML>
21268 <HEAD>
21269 <TITLE>OPTION: <!--#echo var="VAR_download-command"--></TITLE>
21270 </HEAD>
21271 <BODY>
21272 <H1>OPTION: <!--#echo var="VAR_download-command"--></H1>
21274 This option affects the behavior of the Export command. It specifies a Unix
21275 program name, and any necessary command line arguments, that Alpine can use to
21276 transfer the exported message to your personal computer's disk.<P>
21277 Note: this facility is intended for use with serial line transfer
21278 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
21279 to work with TCP/IP file transfer programs such as ftp.<P>
21280 If a program is specified, the Export command is modified to offer a
21281 subcommand (^V) to activate the transfer (in lieu of saving it to
21282 the machine where Alpine is running). Obviously, the Unix program
21283 specified here must match the transfer program or protocol available on the
21284 personal computer.<P>
21286 When this subcommand is selected and before Alpine invokes the specified Unix
21287 program, Alpine will create a temporary file containing the text of the
21288 exported message. Alpine uses this file to pass the exported message text to
21289 the specified Unix program.<P>
21291 The special token "_FILE_" may be included among the Unix program's command
21292 line arguments. Alpine will replace this symbol with the temporary file's name
21293 before executing the Unix program. This token allows you to position the
21294 file name where it is required in the Unix program's command line arguments.
21295 <P>
21296 If the "_FILE_" token is not present in the specified command, the
21297 temporary file's name is automatically appended to the specified Unix
21298 program. In other words, you don't need to use "_FILE_" if it is the
21299 <B>last</B> command line argument.
21300 <P><UL>
21301 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21302 </UL><P>
21303 <End of help on this topic>
21304 </BODY>
21305 </HTML>
21306 ====== h_config_download_prefix ======
21307 <HTML>
21308 <HEAD>
21309 <TITLE>OPTION: <!--#echo var="VAR_download-command-prefix"--></TITLE>
21310 </HEAD>
21311 <BODY>
21312 <H1>OPTION: <!--#echo var="VAR_download-command-prefix"--></H1>
21314 This option is used in conjunction with the <!--#echo var="VAR_download-command"--> option.
21315 It defines text to be written to the terminal emulator (via standard output)
21316 immediately prior to starting the download command. This is useful for
21317 integrated serial line file transfer agents that permit command passing
21318 (e.g., Kermit's APC method).
21319 <P>
21320 The special token "_FILE_" may be included in the string
21321 specification.
21322 That symbol will be replaced with the (Alpine-created) name of the temporary
21323 file into which Alpine will place the message to be downloaded.
21324 <P><UL>
21325 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21326 </UL><P>
21327 <End of help on this topic>
21328 </BODY>
21329 </HTML>
21330 ====== h_config_mailcap_path ======
21331 <HTML>
21332 <HEAD>
21333 <TITLE>OPTION: <!--#echo var="VAR_mailcap-search-path"--></TITLE>
21334 </HEAD>
21335 <BODY>
21336 <H1>OPTION: <!--#echo var="VAR_mailcap-search-path"--></H1>
21337 This variable is used to replace Alpine's default mailcap file search path.
21338 It takes one or more file names (full paths must be specified) in which to
21339 look for mail capability data. The default search path can be found in this
21340 <A HREF="h_news_config">Alpine Configuration</A> help, near the bottom.
21341 If there is more than one file name listed, list members should be delimited
21342 by
21343 <!--chtml if pinemode="os_windows"-->
21344 a semi-colon (;) under Windows; for example:<PRE>
21345 C:\MYCONFIG\MAILCAP.TXT;H:\NETCONFIG\MAILCAP.TXT
21346 </PRE>
21347 <!--chtml else-->
21348 a colon (:) under UNIX; for example:<PRE>
21349 ~/.mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
21350 </PRE>
21351 <!--chtml endif-->
21352 <P><UL>
21353 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21354 </UL>
21355 <P>
21356 <End of help on this topic>
21357 </BODY>
21358 </HTML>
21359 ====== h_config_mimetype_path ======
21360 <HTML>
21361 <HEAD>
21362 <TITLE>OPTION: <!--#echo var="VAR_mimetype-search-path"--></TITLE>
21363 </HEAD>
21364 <BODY>
21365 <H1>OPTION: <!--#echo var="VAR_mimetype-search-path"--></H1>
21367 This variable is used to replace Alpine's default mime.types file search path.
21368 It takes one or more file names (full paths must be specified) in which to
21369 look for file-name-extension to MIME type mapping data. The default search
21370 path can be found in this
21371 <A HREF="h_news_config">Alpine Configuration</A> help.
21373 <P>
21375 If there is more than one file name listed, list members should be delimited
21376 by a colon (:) under UNIX and a semi-colon (;) under Windows.
21377 <P>
21378 <End of help on this topic>
21379 </BODY></HTML>
21380 ====== h_config_set_att_ansi ======
21381 <HTML><HEAD>
21382 <TITLE>OPTION: Set printer to attached ansi printer</TITLE>
21383 </HEAD>
21384 <BODY>
21385 <H1>OPTION: Set printer to attached ansi printer</H1>
21387 Type "S" to set your printer to "attached-to-ansi".<BR>
21388 It is OK to include "attached-to-ansi" in your personal list below.
21389 <P>
21390 <End of help on this topic>
21391 </BODY></HTML>
21392 ====== h_config_set_att_ansi2 ======
21393 <HTML><HEAD>
21394 <TITLE>OPTION: Set printer to attached ansi printer (no formfeed)</TITLE>
21395 </HEAD>
21396 <BODY>
21397 <H1>OPTION: Set printer to attached ansi printer (no formfeed)</H1>
21399 Type "S" to set your printer to "attached-to-ansi-no-formfeed".<BR>
21400 It is OK to include "attached-to-ansi-no-formfeed" in your personal
21401 list below.
21403 <P>
21405 This is the same as the "attached-to-ansi" option except that a
21406 formfeed character will not be appended to the end of the print job.
21407 If your printer already ejects the paper by itself at the end of the
21408 job, you may prefer the "no-formfeed" form of this printer so that you
21409 don't get an extra blank page between print jobs.
21410 <P>
21412 <End of help on this topic>
21413 </BODY></HTML>
21414 ====== h_config_set_att_wyse ======
21415 <HTML><HEAD>
21416 <TITLE>OPTION: Set printer to attached Wyse60 printer</TITLE>
21417 </HEAD>
21418 <BODY>
21419 <H1>OPTION: Set printer to attached Wyse60 printer</H1>
21421 Type "S" to set your printer to "attached-to-wyse".<BR>
21422 It is OK to include "attached-to-wyse" in your personal list below.
21423 <P>
21424 This is very similar to "attached-to-ansi".
21425 The only difference is in the control characters sent to turn the printer
21426 on and off.
21427 The ansi version of the printer uses ESC LEFT_BRACKET 5 i
21428 to turn on the printer and ESC LEFT_BRACKET 4 i
21429 to turn it off.
21430 The Wyse version uses Ctrl-R for on, and Ctrl-T for off.
21431 <End of help on this topic>
21432 </BODY></HTML>
21433 ====== h_config_set_att_wyse2 ======
21434 <HTML><HEAD>
21435 <TITLE>OPTION: Set printer to attached Wyse60 printer (no formfeed)</TITLE>
21436 </HEAD>
21437 <BODY>
21438 <H1>OPTION: Set printer to attached Wyse60 printer (no formfeed)</H1>
21440 Type "S" to set your printer to "attached-to-wyse-no-formfeed".<BR>
21441 It is OK to include "attached-to-wyse-no-formfeed" in your personal
21442 list below.
21444 <P>
21446 This is the same as the "attached-to-wyse" option except that a
21447 formfeed character will not be appended to the end of the print job.
21448 If your printer already ejects the paper by itself at the end of the
21449 job, you may prefer the "no-formfeed" form of this printer so that you
21450 don't get an extra blank page between print jobs.
21451 <P>
21453 <End of help on this topic>
21454 </BODY></HTML>
21455 ====== h_config_set_stand_print ======
21456 <HTML>
21457 <HEAD>
21458 <TITLE>OPTION: Set default printer</TITLE>
21459 </HEAD>
21460 <H1>OPTION: Set default printer</H1>
21461 <BODY>
21462 Move to the printer you want and type "S" to set it to be your
21463 default printer. This list is not modifiable by you and has been
21464 set up by the system administrators. If there is more than one printer
21465 listed in the Command List, you will be able to cycle through that
21466 whole list at the time you print, starting with your default.
21467 It is OK to include entries from this Standard list in your personal
21468 list below.
21469 <P>
21470 <End of help on this topic>
21471 </BODY>
21472 </HTML>
21473 ====== h_config_set_custom_print ======
21474 <HTML>
21475 <HEAD>
21476 <TITLE>OPTION: Set default printer</TITLE>
21477 </HEAD>
21478 <H1>OPTION: Set default printer</H1>
21479 <BODY>
21480 You may add as many print commands as you want to your personal list.
21481 Specify one of them as your default printer by moving to the printer
21482 you want and typing "S". If there is more than one printer listed
21483 in the Command List, you will be able to cycle through that list at
21484 the time you print, starting with your default. It is OK to include
21485 entries from the Standard list above or to include the command
21486 "attached-to-ansi", "attached-to-ansi-no-formfeed", "attached-to-wyse", or
21487 "attached-to-wyse-no-formfeed" as one of the entries here.
21488 <P>
21489 <End of help on this topic>
21490 </BODY>
21491 </HTML>
21492 ====== h_config_user_id =====
21493 <HTML>
21494 <HEAD>
21495 <TITLE>OPTION: <!--#echo var="VAR_user-id"--></TITLE>
21496 </HEAD>
21497 <BODY>
21498 <H1>OPTION: <!--#echo var="VAR_user-id"--></H1>
21500 This value is used as part of the "From" address on messages you send.
21501 It is also the default login name for remote IMAP server access. Set this
21502 to the username part you want to appear on outgoing email.
21503 <P>
21504 If you want to change the value of what gets included in the From header
21505 in messages you send (other than just the User ID)
21506 look <A HREF="h_config_change_your_from">here</A> for a description.
21508 <P><UL>
21509 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21510 </UL><P>
21511 <End of help on this topic>
21512 </BODY>
21513 </HTML>
21514 ====== h_config_user_dom =====
21515 <HTML>
21516 <HEAD>
21517 <TITLE>OPTION: <!--#echo var="VAR_user-domain"--></TITLE>
21518 </HEAD>
21519 <BODY>
21520 <H1>OPTION: <!--#echo var="VAR_user-domain"--></H1>
21522 This value specifies the domain part (right-hand side) of your return
21523 address on outgoing email and is also used as the default domain for email
21524 composed to a local user.
21525 <!--chtml if pinemode="os_windows"-->
21526 This value is required for PC-Alpine. If you are unsure as to what this should be,
21527 contact your local help desk, system administrator, or Internet Service Provider.
21528 <!--chtml else-->
21529 If unset, Unix Alpine will obtain the domain from
21530 the system. Often this value will be set for your whole site by the
21531 system administrator.<P>
21532 <!--chtml endif-->
21533 If you set this, see also the <A HREF="h_config_quell_local_lookup">
21534 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
21535 <P>
21536 If you want to change the value of what gets included in the From header
21537 in messages you send (other than just the User Domain)
21538 look <A HREF="h_config_change_your_from">here</A> for a description.
21539 <P><UL>
21540 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21541 </UL><P>
21542 <End of help on this topic>
21543 </BODY>
21544 </HTML>
21545 ====== h_config_smtp_server =====
21546 <HTML>
21547 <HEAD>
21548 <TITLE>OPTION: <!--#echo var="VAR_smtp-server"--></TITLE>
21549 </HEAD>
21550 <BODY>
21551 <H1>OPTION: <!--#echo var="VAR_smtp-server"--></H1>
21552 This value specifies the name of one or more SMTP
21553 (Simple Mail Transfer Protocol) servers for sending mail.
21554 <!--chtml if pinemode="os_windows"-->
21555 You must have an SMTP server for use with PC-Alpine.
21556 SMTP servers are
21557 normally set up by a system administrator for use by all members of a given
21558 campus or department.
21559 Contact your local help desk to ask what SMTP
21560 servers you should use.
21561 <!--chtml else-->
21562 Unix Alpine users may not need to set an SMTP server.
21563 Alpine will attempt to execute the program (usually sendmail) that is used
21564 to insert mail into the mail system.
21565 If this works for you, you may leave this option blank.
21566 If there is an SMTP server running on the Unix host you may be able to
21567 improve sending performance slightly by setting the SMTP server option
21568 to "localhost" or to the actual name of the Unix host.
21569 <P>
21570 If the Unix host doesn't work the way Alpine was expecting you will need to
21571 set the value of this option.
21572 SMTP servers are
21573 normally set up by a system administrator for use by all members of a given
21574 campus or department.
21575 Contact your local help desk to ask what SMTP
21576 servers you should use.
21577 <!--chtml endif-->
21578 <P>
21579 Your SMTP server may offer SMTP AUTH authentication.
21580 It may even require it.
21581 If your SMTP server offers SMTP AUTH authentication you may specify a
21582 "user" name parameter to cause Alpine to attempt to authenticate.
21583 This parameter requires an associated value,
21584 the username identifier with which to establish the server
21585 connection.
21586 An example might be:
21588 <P>
21589 <CENTER><SAMP>smtpserver.example.com/user=katie</SAMP></CENTER>
21590 <P>
21592 If AUTH authentication is offered by the server, this will cause Alpine to
21593 attempt to use it.
21594 If AUTH authentication is not offered by the server, this will cause Alpine
21595 to fail sending with an error similar to:
21597 <P>
21598 <CENTER><SAMP>Error: SMTP authentication not available</SAMP></CENTER>
21599 <P>
21601 Another type of authentication that is used by some ISPs is called
21602 "POP before SMTP" or "IMAP before SMTP",
21603 which means that you have to authenticate
21604 yourself to the POP or IMAP server by opening a mailbox before you
21605 can send mail.
21606 To do this, you usually only have to open your INBOX.
21608 <P>
21609 You may tell Alpine to use the
21610 <A HREF="http://www.ietf.org/rfc/rfc2476.txt">Message Submission</A>
21611 port (587) instead of the SMTP port (25) by including the "submit"
21612 parameter
21613 in this option.
21614 At this time "/submit" is simply equivalent to specifying
21615 port 587, though it may imply more than that at some point in the future.
21616 Some ISPs are blocking port 25 in order to reduce the amount of spam
21617 being sent to their users.
21618 You may find that the submit option allows you to get around such a block.
21620 <P>
21621 <CENTER><SAMP>smtpserver.example.com/submit</SAMP></CENTER>
21622 <P>
21624 To specify any non-standard port number on the SMTP server you may follow
21625 the hostname with a colon followed by the portnumber.
21627 <P>
21628 <CENTER><SAMP>smtpserver.example.com:12345</SAMP></CENTER>
21629 <P>
21631 Normally, when a connection is made to the Smtp-Server Alpine will attempt
21632 to negotiate a secure (encrypted) session using Transport Layer Security (TLS).
21633 If that fails then a non-encrypted connection will be attempted instead.
21634 You may specify that a TLS connection is required if you wish.
21635 If you append "/tls" to the name then the connection will fail
21636 instead of falling back to a non-secure connection.
21638 <P>
21639 <CENTER><SAMP>smtpserver.example.com/tls</SAMP></CENTER>
21640 <P>
21643 For more details about server name possibilities see
21644 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
21645 <P>
21647 <UL>
21648 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21649 </UL>
21650 <P>
21651 <End of help on this topic>
21652 </BODY>
21653 </HTML>
21654 ====== h_config_nntp_server =====
21655 <HTML>
21656 <HEAD>
21657 <TITLE>OPTION: <!--#echo var="VAR_nntp-server"--></TITLE></HEAD>
21658 <BODY>
21659 <H1>OPTION: <!--#echo var="VAR_nntp-server"--></H1>
21661 This value specifies the name of one or more NNTP
21662 (Network News Transfer Protocol)
21663 servers for reading and posting USENET news.
21664 NNTP servers are normally
21665 set up by a system administrator for use by all members of a given campus
21666 or department.
21667 Contact your local help desk to ask what NNTP servers you should use.
21668 <!--chtml if pinemode="os_windows"--><!--chtml else-->
21669 Often Unix Alpine users will find that this variable has been
21670 set for the whole system (and they don't have to worry about it).
21671 <!--chtml endif-->
21672 When you define an NNTP server here, Alpine implicitly defines a news
21673 collection for you, assuming that server as the news server and assuming
21674 that you will use the NNTP protocol and a local newsrc configuration file
21675 for reading news.
21676 For more about reading news with Alpine, see
21677 <A HREF="h_reading_news">how to use Alpine to read news</A>.
21678 <P>
21679 Your NNTP server may offer NNTP "AUTHINFO SASL"
21680 or "AUTHINFO USER" authentication.
21681 It may even require it.
21682 If your NNTP server does offer such authentication you may specify a user name
21683 parameter to cause Alpine to attempt to authenticate.
21684 The same is true for the server name in a folder collection that uses NNTP.
21685 This parameter requires an associated value,
21686 the username identifier with which to establish the server connection.
21687 An example might be:
21689 <P>
21690 <CENTER><SAMP>nntpserver.example.com/user=katie</SAMP></CENTER>
21691 <P>
21693 If authentication is offered by the server, this will cause Alpine to
21694 attempt to use it.
21695 If authentication is not offered by the server, this will cause Alpine
21696 to fail with an error similar to:
21698 <P>
21699 <CENTER><SAMP>Error: NNTP authentication not available</SAMP></CENTER>
21700 <P>
21701 For more details about the server name possibilities see
21702 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
21703 <P><UL>
21704 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21705 </UL><P>
21706 <End of help on this topic>
21707 </BODY>
21708 </HTML>
21709 ====== h_config_inbox_path =====
21710 <HTML>
21711 <HEAD>
21712 <TITLE>OPTION: <!--#echo var="VAR_inbox-path"--></TITLE>
21713 </HEAD>
21714 <BODY>
21715 <H1>OPTION: <!--#echo var="VAR_inbox-path"--></H1>
21717 This value overrides the default value of your INBOX name/path/location.
21718 <!--chtml if pinemode="os_windows"-->
21719 PC-Alpine users must specify an inbox path and it must be a folder on an
21720 IMAP server.
21721 <!--chtml else-->
21722 Unix and VMS Alpine users will often find that this variable
21723 has been pre-configured by your system administrator.
21724 <!--chtml endif-->
21725 You may be able to specify an alternate INBOX that is either a local folder
21726 or a folder on an IMAP server.
21727 <P>
21728 A typical remote <!--#echo var="VAR_inbox-path"--> entry would be: {monet.art.example.com}INBOX
21729 where "monet.art.example.com" is replaced by the name of your IMAP
21730 mail server.
21731 <P>
21732 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21733 details on the syntax of folder definitions.
21734 <P>
21735 See <A HREF="h_info_on_mbox">Missing mail and the mbox driver</A> if your
21736 mail is disappearing.
21737 <P><UL>
21738 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21739 </UL><P>
21740 <End of help on this topic>
21741 </BODY>
21742 </HTML>
21743 ====== h_config_change_your_from =====
21744 <HTML>
21745 <HEAD>
21746 <TITLE>How to Change your From Address</TITLE>
21747 </HEAD>
21748 <BODY>
21749 <H1>How to Change your From Address</H1>
21751 If the From address that Alpine includes in mail that you send is not correct,
21752 you may want to configure a different default value for the From address.
21753 You may follow these directions to change the default:
21755 <P>
21756 <UL>
21757 <LI> Go to the Main Alpine Menu
21758 <LI> From there type the Setup Command
21759 <LI> From there type the Config Command
21760 </UL>
21762 <P>
21763 You've probably already seen this SETUP CONFIGURATION screen.
21764 If not, there are many options you may want to set here.
21765 To set the value of the From header you may use the
21766 <A href="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> option.
21767 Find it by scrolling down a few pages or use the WhereIs command to
21768 search for "customized".
21769 You may want to read the help text associated with the option.
21770 <P>
21771 To add a custom From header, type the Add command and enter the
21772 full header line, including the leading "From: ".
21773 For example:
21774 <P>
21775 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
21776 <P>
21777 Now exit the Setup command and try sending mail to yourself to see
21778 what the From line looks like.
21779 <P>
21780 When you are in the composer you may edit the custom From line by typing
21781 Ctrl-R while your cursor is in the headers of the message and then moving
21782 to the From line and editing.
21783 If you want to leave the default value the same but add the possibility
21784 of being able to edit the header when you compose, add just the header
21785 name without a value.
21786 For example:
21787 <P>
21788 <CENTER><SAMP>From:</SAMP></CENTER>
21789 <P>
21790 If you change your From address you may also find it useful to add the
21791 changed From address to the
21792 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
21793 configuration option.
21794 <P>
21795 <UL>
21796 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21797 </UL><P>
21798 <End of help on this topic>
21799 </BODY>
21800 </HTML>
21801 ====== h_config_default_fcc =====
21802 <HTML>
21803 <HEAD>
21804 <TITLE>OPTION: <!--#echo var="VAR_default-fcc"--></TITLE>
21805 </HEAD>
21806 <BODY>
21807 <H1>OPTION: <!--#echo var="VAR_default-fcc"--></H1>
21809 This value specifies where a copy of outgoing mail should be saved. If
21810 this is not a path name, it will be in the default collection for saves.
21811 Any valid folder specification, local or IMAP, is allowed. This default
21812 folder carbon copy only applies when the
21813 <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
21814 is set to use the default folder.
21815 <!--chtml if pinemode="os_windows"-->
21816 PC-Alpine default is "SENTMAIL" (normally stored as SENTMAIL.MTX)
21817 <!--chtml else-->
21818 Unix Alpine default
21819 is normally "sent-mail" in the default folder collection.
21820 <!--chtml endif-->
21821 <P>
21822 If you access your email through an IMAP server, especially if you often switch between Unix Alpine
21823 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on your
21824 IMAP server (remember that in order to later access this remote folder through Alpine, it
21825 must be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
21826 for more information). An example:<p>
21827 <CENTER><SAMP>{monet.art.example.com}mail/sent-mail</SAMP></CENTER>
21828 <P>
21829 To suppress saving of outgoing mail, set: <!--#echo var="VAR_default-fcc"-->=""
21830 <P>
21831 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21832 details on the syntax of folder definitions.
21833 <P>
21834 <UL>
21835 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21836 </UL><P>
21837 <End of help on this topic>
21838 </BODY>
21839 </HTML>
21840 ====== h_config_def_save_folder =====
21841 <HTML>
21842 <HEAD>
21843 <TITLE>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></TITLE>
21844 </HEAD>
21845 <BODY>
21846 <H1>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></H1>
21848 This option determines the default folder name for save-message operations
21849 ("saves").
21850 <P>
21851 If this is not a path name, it will be in the default collection for saves.
21852 Any valid folder specification, local or IMAP, is allowed. This default
21853 folder only applies when the
21854 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
21855 doesn't override it.
21856 <!--chtml if pinemode="os_windows"-->
21857 PC-Alpine default is "SAVEMAIL" (normally stored as SAVEMAIL.MTX).
21858 <!--chtml else-->
21859 Unix Alpine default
21860 is normally "saved-messages" in the default folder collection.
21861 <!--chtml endif-->
21862 If you access your email through an IMAP server, especially if you often switch between Unix
21863 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on an
21864 IMAP server (remember that in order to later access this remote folder through Alpine, it
21865 should be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
21866 for more information). An example:<p>
21867 <CENTER><SAMP>{monet.art.example.com}mail/saved-messages</SAMP></CENTER>
21868 <P>
21869 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21870 details on the syntax of folder definitions.
21871 <P>
21872 <UL>
21873 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21874 </UL><P>
21875 <End of help on this topic>
21876 </BODY>
21877 </HTML>
21878 ====== h_config_postponed_folder =====
21879 <HTML>
21880 <HEAD>
21881 <TITLE>OPTION: <!--#echo var="VAR_postponed-folder"--></TITLE>
21882 </HEAD>
21883 <BODY>
21884 <H1>OPTION: <!--#echo var="VAR_postponed-folder"--></H1>
21886 This value overrides the default name for the folder where postponed
21887 messages are saved. If this is not a path name, it will be in the default
21888 collection for message Saves. Any valid folder specification, local or
21889 remote, is allowed.
21890 PC-Alpine default
21891 is "POSTPOND" (stored as POSTPOND.MTX).
21892 The Unix Alpine default is normally "postponed-msgs"
21893 in the default collection.
21894 <P>
21895 Tip: If you are using different installations of (PC-)Alpine -- for example, PC-Alpine on your personal
21896 computer at home, and Unix Alpine on campus -- you can postpone a composition begun with one Alpine and
21897 resume it later with the other if you set this option to the <B>same folder on the same IMAP host</B>
21898 in all Alpine copies you use.
21899 (Remember that in order to later access this remote folder through Alpine, it must be in a folder
21900 collection. See <A HREF="h_what_are_collections">Folder Collections Extensions Explained</a>
21901 for more information). An
21902 example:<p>
21903 <CENTER><SAMP>{monet.art.example.com}mail/postponed-msgs</SAMP></CENTER>
21904 <P>
21905 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21906 details on the syntax of folder definitions.
21907 <P>
21908 <UL>
21909 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21910 </UL><P>
21911 <End of help on this topic>
21912 </BODY>
21913 </HTML>
21914 ====== h_config_read_message_folder =====
21915 <HTML>
21916 <HEAD>
21917 <TITLE>OPTION: <!--#echo var="VAR_read-message-folder"--></TITLE>
21918 </HEAD>
21919 <BODY>
21920 <H1>OPTION: <!--#echo var="VAR_read-message-folder"--></H1>
21922 By virtue of specifying a folder name here, Alpine will be configured to
21923 save all messages that you have read during a session into the designated
21924 "read messages" folder. This allows you to more easily distinguish
21925 between your really new email (in your INBOX) and those that you have
21926 already read. Depending on how you define the
21927 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
21928 setting, you may or may not be asked when you quit
21929 Alpine if you want read messages to be moved to this folder. In either
21930 case, moving the messages means they will be deleted from your INBOX.
21931 <P>
21932 If this is not a path name, it will be in the default collection for
21933 saves. Any valid folder specification, local or remote (via IMAP), is
21934 allowed. There is no default for the name of the read message folder.
21935 <P>
21936 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21937 details on the syntax of folder definitions.
21938 <P>
21939 <UL>
21940 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21941 </UL><P>
21942 <End of help on this topic>
21943 </BODY>
21944 </HTML>
21945 ====== h_config_form_folder =====
21946 <HTML>
21947 <HEAD>
21948 <TITLE>OPTION: <!--#echo var="VAR_form-letter-folder"--></TITLE>
21949 </HEAD>
21950 <BODY>
21951 <H1>OPTION: <!--#echo var="VAR_form-letter-folder"--></H1>
21953 A "<!--#echo var="VAR_form-letter-folder"-->" is a mail folder that is intended to
21954 contain messages that you have composed and that are intended to be
21955 sent in their original form repeatedly.
21957 <P>
21958 Setting this variable will alter Alpine's usual behavior when you
21959 execute the Compose command. Normally, Alpine offers a chance to
21960 continue a postponed or interrupted message should one or the other
21961 exist. When this variable is set to a folder name that exists, Alpine
21962 will also offer the chance to select a message from the folder to
21963 insert into the composer (much like when continuing a postponed message).
21964 The difference, however, is that Alpine will not automatically delete
21965 the selected message from the Form Letter Folder.
21966 <P>
21967 Setting this variable will also affect Alpine's behavior when you
21968 Postpone a message from the composer. Normally, Alpine simply stashes
21969 the message away in your
21970 "<A HREF="h_config_postponed_folder"><!--#echo var="VAR_postponed-folder"--></A>".
21971 Regardless of the specified folder's existence, Alpine will ask which
21972 folder you intend the message to be stored in. Choose the
21973 "F" option to store the message in your Form Letter Folder.
21974 This is the most common way to add a message to the folder.
21976 <P>
21977 Another method of adding messages to the folder is via the Alpine
21978 composer's <SAMP>Fcc:</SAMP> field. If you are sending a message that
21979 you expect to send in the same form again, you can enter the Form
21980 Letter Folder's name in this field. Alpine, as usual, will copy the
21981 message as it's sent. Note, when you later select this message from
21982 your Form Letter Folder, it will have the same recipients as the original
21983 message.
21985 <P>
21986 To delete a message from the Form Letter Folder, you can either select
21987 the folder from a suitable FOLDER LIST screen, or use the Delete
21988 command in the MESSAGE INDEX offered when selecting from the folder as
21989 part of the Compose command. You can delete a Form Letter Folder just
21990 as any other folder from a suitable FOLDER LIST screen.
21992 <P>
21993 You may find that the <A HREF="h_rules_roles">"Roles"</A>
21994 facility can be used
21995 to replace the Form Letter Folder.
21997 <P>
21998 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21999 details on the syntax of folder definitions.
22001 <P>
22002 <UL>
22003 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22004 </UL><P>
22005 <End of help on this topic>
22006 </BODY>
22007 </HTML>
22008 ====== h_config_archived_folders =====
22009 <HTML>
22010 <HEAD>
22011 <TITLE>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></TITLE>
22012 </HEAD>
22013 <BODY>
22014 <H1>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></H1>
22016 This is like
22017 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>,
22018 only more general. You may archive
22019 any of the folders in your incoming collection. This is a list of folder
22020 pairs, with the first separated from the second in the pair by a space.
22021 The first folder in a pair is the folder you want to archive, and the
22022 second folder is the folder that read messages from the first should be
22023 moved to. Depending on how you define the
22024 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
22025 setting, you may or may not be asked when you
22026 leave the first folder if you want read messages to be moved to the
22027 second folder. In either case, moving the messages means they will be
22028 deleted from the first folder.
22029 <P>
22030 The name of the first folder in each pair can be either the technical
22031 specification of the folder (like what appears in your configuration file)
22032 or (much easier) the nickname that you gave the folder when you made it
22033 an incoming folder.
22034 <p>
22035 For example:<p>
22036 <CENTER><SAMP>{monet.art.example.com}inbox {monet.art.example.com}mail/inbox-archive</SAMP></CENTER>
22037 <p>or, using nicknames:<p>
22038 <CENTER><SAMP>inbox inbox-archive</SAMP></CENTER>
22039 <P>
22040 If these are not path names, they will be in the default collection for
22041 saves. Any valid folder specification, local or remote (via IMAP), is
22042 allowed. There is no default.
22043 <P>
22044 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22045 details on the syntax of folder definitions.
22046 <P>
22047 <UL>
22048 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22049 </UL><P>
22050 <End of help on this topic>
22051 </BODY>
22052 </HTML>
22053 ====== h_config_newsrc_path ======
22054 <HTML>
22055 <HEAD>
22056 <TITLE>OPTION: <!--#echo var="VAR_newsrc-path"--></TITLE>
22057 </HEAD>
22058 <BODY>
22059 <H1>OPTION: <!--#echo var="VAR_newsrc-path"--></H1>
22061 This option overrides the default name Alpine uses for your "newsrc" news
22062 status and subscription file. If set, Alpine will take this value as the
22063 full pathname for the desired newsrc file.<P>
22065 If this option is <B>not</B> set,
22066 <!--chtml if pinemode="os_windows"-->
22067 PC-Alpine looks first for $HOME\NEWSRC (where $HOME defaults to the root
22068 of the current drive, e.g. "C:\") and then it looks in the same
22069 directory as your pinerc file for NEWSRC.
22070 <!--chtml else-->
22071 Unix Alpine looks for the file ~/.newsrc (that is, the file named .newsrc in
22072 your account's home directory).
22073 <!--chtml endif-->
22074 <P><UL>
22075 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22076 </UL>
22077 <P>
22078 <End of help on this topic>
22079 </BODY>
22080 </HTML>
22081 ====== h_config_literal_sig =====
22082 <HTML>
22083 <HEAD>
22084 <TITLE>OPTION: <!--#echo var="VAR_literal-signature"--></TITLE>
22085 </HEAD>
22086 <BODY>
22087 <H1>OPTION: <!--#echo var="VAR_literal-signature"--></H1>
22089 With this option your actual signature, as opposed to
22090 the name of a file containing your signature,
22091 is stored in the Alpine configuration file.
22092 If this is defined it takes precedence over the <!--#echo var="VAR_signature-file"--> option.
22093 <P>
22095 This is simply a different way to store the signature.
22096 The signature is stored inside your Alpine configuration file instead of in
22097 a separate file.
22098 Tokens work the same way they do with the
22099 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A> so look there for
22100 help.
22101 <P>
22103 The Setup/Signature command on Alpine's MAIN MENU will edit
22104 the "<!--#echo var="VAR_literal-signature"-->" by default. However, if no
22105 "<!--#echo var="VAR_literal-signature"-->" is defined and the file named in the
22106 "<!--#echo var="VAR_signature-file"-->" option exists, then the latter will be used
22107 instead.
22108 <P>
22110 The two character sequence \n (backslash followed by
22111 the character n) will be used to signify a line-break in your signature.
22112 You don't have to enter the \n, but it will be visible in the
22113 SETUP CONFIGURATION window after you are done editing the signature.
22115 <P>
22116 <UL>
22117 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22118 </UL><P>
22119 <End of help on this topic>
22120 </BODY>
22121 </HTML>
22122 ====== h_config_signature_file =====
22123 <HTML>
22124 <HEAD>
22125 <TITLE>OPTION: <!--#echo var="VAR_signature-file"--></TITLE>
22126 </HEAD>
22127 <BODY>
22128 <H1>OPTION: <!--#echo var="VAR_signature-file"--></H1>
22130 If a <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined,
22131 then this "<!--#echo var="VAR_signature-file"-->" option will be ignored.
22132 You can tell that that is the case because the value of the
22133 "<!--#echo var="VAR_signature-file"-->" will show up as
22134 <P>
22135 <CENTER><SAMP><Ignored: using <!--#echo var="VAR_literal-signature"--> instead></SAMP></CENTER>
22136 <P>
22137 You may either use all Literal Signatures (signatures stored in your
22138 configuration file) throughout Alpine, or all signature files.
22139 You can't mix the two.
22140 <P>
22141 This is the name of a file that will be automatically inserted into
22142 outgoing messages.
22143 It typically contains information such as your
22144 name, email address and organizational affiliation.
22145 Alpine adds the
22146 signature into the message as soon as you enter the composer so you
22147 can choose to remove it or edit it on a message by message basis.
22148 Signature file placement in message replies is controlled by the
22149 "<A HREF="h_config_sig_at_bottom"><!--#echo var="FEAT_signature-at-bottom"--></A>"
22150 setting in the feature list.
22151 <P>
22153 The default file name is
22154 <!--chtml if pinemode="os_windows"-->
22155 "PINE.SIG" in the same directory as your PINERC file if your
22156 PINERC file is a local file.
22157 If your PINERC file is remote, then it will be in the directory specified
22158 by the "-aux local_directory" command line option.
22159 <!--chtml else-->
22160 ".signature".
22161 <!--chtml endif-->
22162 <P>
22164 To create or edit your signature file choose Setup from the MAIN MENU
22165 and then select S for Signature (Main/Setup/Signature). This puts you
22166 into the Signature Editor where you can enter a <EM>few</EM> lines of
22167 text containing your identity and affiliation.
22169 <P>
22170 If the filename is followed by a vertical bar (|) then instead
22171 of reading the contents of the file the file is assumed to be a
22172 program that will produce the text to be used on its standard output.
22173 The program can't have any arguments and doesn't receive any input from Alpine,
22174 but the rest of the processing works as if the contents came from a file.
22176 <P>
22177 Instead of storing the data in a local file, the
22178 signature data may be stored remotely in an IMAP folder.
22179 In order to do this,
22180 you must use a remote name for the file.
22181 A remote <!--#echo var="VAR_signature-file"--> name might look like:
22182 <P>
22183 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/signature</SAMP></CENTER>
22184 <P>
22186 The syntax used here is the same as the syntax used for remote configuration
22187 files from the command line.
22188 Note that you may not access an existing signature file remotely,
22189 you have to create a new <EM>folder</EM> that contains the signature data.
22190 If the name you use here for the signature file is a remote name, then when
22191 you edit the file from the Setup/Signature command the data will be stored
22192 remotely in the folder.
22193 You aren't required to do anything special to create the folder, it
22194 gets created automatically if you use a remote name.
22196 <P>
22197 Besides regular text, the signature file may also contain
22198 (or a signature program may produce) tokens that
22199 are replaced with text that usually depends on the message you are replying
22200 to or forwarding.
22201 For example, if the signature file contains the token
22202 <P>
22203 <CENTER><SAMP>_DATE_</SAMP></CENTER>
22204 <P>
22205 anywhere in the text, then that token is replaced by the date
22206 the message you are replying to or forwarding was sent.
22207 If it contains
22208 <P>
22209 <CENTER><SAMP>_CURDATE_</SAMP></CENTER>
22210 <P>
22211 that is replaced with the current date.
22212 The first is an example of a token that depends on the message you
22213 are replying to (or forwarding) and the second is an example which
22214 doesn't depend on anything other than the current date.
22215 You have to be a little careful with this facility since tokens that
22216 depend on the message you are replying to or forwarding will be replaced
22217 by nothing in the case where you are composing a new message from scratch.
22218 The use of <A HREF="h_rules_roles">"roles"</A> may help you
22219 in this respect.
22220 It allows you to use different signature files in different cases.
22221 <P>
22223 The list of tokens available for use in the signature file is
22224 <A HREF="h_index_tokens">here</A>.
22225 <P>
22227 Instead of, or along with the use of "roles" to give you
22228 different signature files in different situations, there is also
22229 a way to conditionally include text based
22230 on whether or not a token would result in specific replacement text.
22231 For example, you could include some text based on whether or not
22232 the _NEWS_ token would result in any newsgroups if it was used.
22233 This is explained in detail
22234 <A HREF="h_reply_token_conditionals">here</A>.
22235 This isn't for the faint of heart.
22236 <P>
22237 In the very unlikely event that you want to include a literal token
22238 in the signature you must precede it with a backslash character.
22239 For example,
22240 <P>
22241 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
22242 <P>
22243 would produce something like
22244 <P>
22245 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
22246 <P>
22247 It is not possible to have a literal backslash followed by an expanded token.
22248 <P>
22249 An alternate method for storing the signature data is available by using the
22250 <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> configuration option.
22251 This variable will be used by default.
22252 <P>
22253 <UL>
22254 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22255 </UL><P>
22256 <End of help on this topic>
22257 </BODY>
22258 </HTML>
22259 ====== h_config_init_cmd_list =====
22260 <HTML>
22261 <HEAD>
22262 <TITLE>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></TITLE>
22263 </HEAD>
22264 <BODY>
22265 <H1>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></H1>
22267 The initial keystroke--or command--list option lets you start Alpine at
22268 any place you like.
22269 Whatever keystrokes you specify here will be executed
22270 by Alpine upon startup as a macro.
22271 The words SPACE, TAB, DOWN, UP, LEFT, and
22272 RIGHT indicate the pressing of those keys.
22273 CR indicates the pressing of the RETURN key.
22274 F1 through F12 represent the function keys, and ^ followed
22275 by a character indicates that key pressed along with the control key (in
22276 other words, ^P means Ctrl-P).
22277 As a shortcut notation, an element of the list may be several characters
22278 surrounded by double-quotes (").
22279 That will be expanded into the individual keystrokes
22280 (excluding the double-quote characters).
22281 For example, the quoted-string
22283 <P><CENTER>"ABC"</CENTER>
22285 <P>
22286 is interpreted the same as the three separate list members
22288 <P><CENTER>A and B and C</CENTER>
22290 <P>
22291 which is also the same as
22293 <P><CENTER>A,B,C</CENTER>
22295 <P>
22296 An example: To view message 1 on startup,
22297 you could use an <!--#echo var="VAR_initial-keystroke-list"--> equal to
22299 <P><CENTER>I,J,1,CR,V</CENTER>
22301 <P>
22302 An equivalent version of this is
22304 <P><CENTER>"IJ1",CR,V</CENTER>
22306 <P>
22307 Restrictions: You cannot pre-type into the composer with the initial
22308 keystroke list, and you cannot mix function key commands with letter
22309 commands.
22311 <P><UL>
22312 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22313 </UL>
22314 <P>
22315 <End of help on this topic>
22316 </BODY>
22317 </HTML>
22318 ====== h_config_comp_hdrs =====
22319 <html>
22320 <header>
22321 <title>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></title>
22322 </header>
22323 <body>
22324 <h1>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></h1>
22326 You can control which headers you want visible when composing outgoing
22327 email using this option.
22328 You can specify any of the regular set, any
22329 <A HREF="h_compose_richhdr">Rich Header</A>,
22330 or any <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22331 that you have already defined.
22332 If you use this setting at all, you must specify all the
22333 headers you want to see, you can't just add to the regular header set.
22334 The default set is To:, Cc:, Attchmnt:, and Subject:.<p>
22336 Note that the "Newsgroups:" header will be abbreviated in the Composer
22337 display, but should be spelled out in full here.<p>
22338 <UL>
22339 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22340 </UL><P>
22341 <End of help on this topic>
22342 </body>
22343 </html>
22344 ====== h_config_custom_hdrs =====
22345 <HTML>
22346 <HEAD>
22347 <TITLE>OPTION: <!--#echo var="VAR_customized-hdrs"--></TITLE>
22348 </HEAD>
22349 <BODY>
22350 <H1>OPTION: <!--#echo var="VAR_customized-hdrs"--></H1>
22352 You may add your own custom headers to outgoing messages.
22353 Each header you specify here must include the header tag
22354 (<A HREF="h_composer_reply_to">Reply-To:</A>, Approved:, etc.)
22355 and may optionally include a value for that header.
22356 If you want to see these custom headers each time you compose a message,
22357 you must add them to your
22358 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> list,
22359 otherwise they become part
22360 of the rich header set that you only see when you press the
22361 <A HREF="h_compose_richhdr">Rich Header</A>
22362 <!--chtml if pinemode="function_key"-->(F5)
22363 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
22364 (If you are looking for a way to change which headers are <EM>displayed</EM>
22365 when you view a message, take a look at the
22366 <A HREF="h_config_viewer_headers"><!--#echo var="VAR_viewer-hdrs"--></A>
22367 option instead.)
22368 Here's an example that shows how you might set your From address
22369 <P>
22370 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
22371 <P>
22372 and another showing how you might set a Reply-To address
22373 <P>
22374 <CENTER><SAMP>Reply-To: user@example.com</SAMP></CENTER>
22375 <P>
22376 You may also set non-standard header values here.
22377 For example, you could add
22378 <P>
22379 <CENTER><SAMP>Organization: My Organization Name</SAMP></CENTER>
22380 <P>
22381 or even
22382 <P>
22383 <CENTER><SAMP>X-Favorite-Colors: Purple and Gold</SAMP></CENTER>
22384 <P>
22385 If you include a value after the colon then that header will be included
22386 in your outgoing messages unless you delete it before sending.
22387 If a header in the <!--#echo var="VAR_customized-hdrs"--> list has only a tag but no value, then
22388 it will not be included in outgoing messages unless you edit a value
22389 in manually.
22390 For example, if
22391 <P>
22392 <CENTER><SAMP>Reply-To:</SAMP></CENTER>
22393 <P>
22394 is in the list, then the Reply-To header will be available for editing
22395 but won't be included unless a value is added while in the composer.
22396 <P>
22397 It's actually a little more complicated than that.
22398 The values of headers that you set with the <!--#echo var="VAR_customized-hdrs"--> option are
22399 defaults.
22400 If the message you are about to compose already has a value for a header,
22401 that value is used instead of a value from your <!--#echo var="VAR_customized-hdrs"-->.
22402 For example, if you are Replying to a message the Subject field
22403 will already be filled in.
22404 In that case, if the <!--#echo var="VAR_customized-hdrs"--> list contains a Subject line, the
22405 custom subject will <EM>NOT</EM> be used.
22406 The subject derived from the subject of the message you are Replying
22407 to will be used instead.
22408 <P>
22409 It is also possible to make header setting even more complicated and more
22410 automatic by using
22411 <A HREF="h_rules_roles">Roles</A>,
22412 but if all you want to do is set a default value for a header, you don't
22413 need to think about Roles.
22414 <P>
22415 If you change your From address you may also find it useful to add the
22416 changed From address to the
22417 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
22418 configuration option.
22419 <P>
22420 Limitation: Because commas are used to separate the list of
22421 <!--#echo var="VAR_customized-hdrs"-->, it is not possible to have the value of a
22422 header contain a comma.
22423 Nor is there currently an "escape" mechanism provided
22424 to make this work.
22425 <P><UL>
22426 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22427 </UL>
22428 <P>
22429 <End of help on this topic>
22430 </BODY>
22431 </HTML>
22432 ====== h_config_viewer_headers =====
22433 <HTML>
22434 <HEAD>
22435 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdrs"--></TITLE>
22436 </HEAD>
22437 <BODY>
22438 <H1>OPTION: <!--#echo var="VAR_viewer-hdrs"--></H1>
22440 You may change the default list of headers that are viewed by listing
22441 the headers you want to view here. If the headers in your
22442 "<!--#echo var="VAR_viewer-hdrs"-->" list are present in the message, then they
22443 will be shown. The order of the headers you list will be honored. If
22444 the special value "all-except" is included as the first
22445 header in the "<!--#echo var="VAR_viewer-hdrs"-->" list, then all headers in the
22446 message except those in the list will be shown. The values are all
22447 case insensitive.
22449 <P>
22450 Note that once you put anything in the "<!--#echo var="VAR_viewer-hdrs"-->" list,
22451 then the original default headers are ignored. So, if you just wanted
22452 to add the header Organization to the list, you would have to list
22453 Organization plus all of the other headers originally in the default
22454 list. If you just included Organization and nothing else, then you
22455 would see only the Organization header, nothing else.
22457 <P>
22458 The default list of headers includes:
22459 <UL>
22460 <LI>From
22461 <LI>Resent-From
22462 <LI>To
22463 <LI>Resent-To
22464 <LI>Cc
22465 <LI>Resent-cc
22466 <LI>Bcc
22467 <LI>Newsgroups
22468 <LI>Followup-To
22469 <LI>Date
22470 <LI>Resent-Date
22471 <LI>Subject
22472 <LI>Resent-Subject
22473 <LI>Reply-To
22474 </UL>
22476 <P>
22477 If you are looking for a way to control which headers are included in
22478 outgoing mail and are visible or not in the composer, take a look at the
22479 options
22480 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22481 and <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> instead of
22482 this option.
22483 <P>
22484 <UL>
22485 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22486 </UL><P>
22487 <End of help on this topic>
22488 </BODY>
22489 </HTML>
22490 ====== h_config_viewer_margin_left =====
22491 <HTML>
22492 <HEAD>
22493 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-left"--></TITLE>
22494 </HEAD>
22495 <BODY>
22496 <H1>OPTION: <!--#echo var="VAR_viewer-margin-left"--></H1>
22498 This variable controls the left-hand vertical margin's width in
22499 Alpine's Message Viewing screen.
22500 Its value is the number of space characters preceding each displayed line.
22501 For consistency with
22502 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>,
22503 you may specify the column number to start in
22504 (column numbering begins with number 1)
22505 instead of the width of the margin by appending a lower case letter
22506 "c" to the number.
22507 For example, a value of "2c" means to start the text in column two,
22508 which is entirely equivalent to a value of "1", which means to
22509 leave a margin of 1 space.
22510 <P>
22511 The default is a left margin of 0 (zero).
22512 Misconfigurations (for example, negative values or values with starting
22513 left columns greater than the ending right column)
22514 are silently ignored.
22515 If the number of columns for text between the <!--#echo var="VAR_viewer-margin-left"--> and
22516 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22517 instead.
22519 <P>
22520 <End of help on this topic>
22521 </BODY>
22522 </HTML>
22523 ====== h_config_viewer_margin_right =====
22524 <HTML>
22525 <HEAD>
22526 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-right"--></TITLE>
22527 </HEAD>
22528 <BODY>
22529 <H1>OPTION: <!--#echo var="VAR_viewer-margin-right"--></H1>
22531 This variable controls the right-hand vertical margin's width in
22532 Alpine's Message Viewing screen.
22533 Its value is the number of space characters following each displayed line.
22534 You may specify the column number to end the text in
22535 (column numbering begins with number 1)
22536 instead of the width of the margin by appending a lower case letter
22537 "c" to the number.
22538 For example, a value of "76c" means to end the text in column 76.
22539 If the screen is 80 characters wide, this is equivalent to a value
22540 of "4", which means to leave a margin of 4 spaces.
22541 However, if you use different size screens at different times, then these
22542 two values are not equivalent.
22543 <P>
22544 The default right margin is 4.
22545 Misconfigurations (for example, negative values or values with starting
22546 left columns greater than the ending right column)
22547 are silently ignored.
22548 If the number of columns for text between the
22549 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
22550 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22551 instead.
22553 <P>
22554 <End of help on this topic>
22555 </BODY>
22556 </HTML>
22557 ====== h_config_quote_suppression =====
22558 <HTML>
22559 <HEAD>
22560 <TITLE>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></TITLE>
22561 </HEAD>
22562 <BODY>
22563 <H1>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></H1>
22565 This option should be used with care.
22566 It will cause some of the quoted text to be eliminated from the
22567 display when viewing a message in the MESSAGE TEXT screen.
22568 For example, if you set the <!--#echo var="VAR_quote-suppression-threshold"--> to the
22569 value "5",
22570 this will cause quoted text that is longer than five lines to be truncated.
22571 Quoted text of five or fewer consecutive lines will be displayed in its entirety.
22572 Quoted text of more than six lines will have the first five lines displayed
22573 followed by a line that looks something like
22574 <P>
22575 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
22576 <P>
22577 As a special case, if exactly one line of quoted text would be hidden, the
22578 entire quote will be shown instead.
22579 So for the above example, quoted text that is exactly six lines long will
22580 will be shown in its entirety.
22581 (In other words, instead of hiding a single line and adding a line
22582 that announces that one line was hidden, the line is just shown.)
22583 <P>
22584 If the sender of a message has carefully chosen the quotes that he or she
22585 includes, hiding those quotes may change the meaning of the message.
22586 For that reason, Alpine requires that when you want to set the value of this
22587 variable to something less than four lines, you actually have to set it
22588 to the negative of that number.
22589 So if you want to set this option to "3", you actually have to
22590 set it to "-3".
22591 The only purpose of this is to get you to think about whether or not you
22592 really want to do this!
22593 If you want to delete all quoted text you set the value of this option
22594 to the special value "-10".
22595 <P>
22596 The legal values for this option are
22597 <P>
22598 <TABLE>
22599 <TR>
22600 <TD> 0 </TD>
22601 <TD> Default, don't hide anything </TD>
22602 </TR>
22603 <TR>
22604 <TD> -1,-2,-3 </TD>
22605 <TD> Suppress quote lines past 1, 2, or 3 lines </TD>
22606 </TR>
22607 <TR>
22608 <TD> 4,5,6,... </TD>
22609 <TD> Suppress if more than that many lines </TD>
22610 </TR>
22611 <TR>
22612 <TD> -10 </TD>
22613 <TD> Suppress all quoted lines </TD>
22614 </TR>
22615 </TABLE>
22616 <P>
22617 If you set this option to a non-default value you may sometimes wish to
22618 view the quoted text that is not shown.
22619 When this is the case, the
22620 <A HREF="h_common_hdrmode">HdrMode Command</A>
22621 may be used to show the hidden text.
22622 Typing the "H" command once will show the hidden text.
22623 Typing a second "H" will also turn on Full Header mode.
22624 The presence or absence of the HdrMode command is determined by the
22625 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
22626 Feature-List option in your Alpine configuration, so you will want to
22627 be sure that is turned on if you use quote suppression.
22628 <P>
22629 For the purposes of this option, a quote is a line that begins with the
22630 character ">".
22631 <P>
22632 Quotes are only suppressed when displaying a message on the screen.
22633 The entire quote will be left intact when printing or forwarding or something
22634 similar.
22635 <P>
22636 <End of help on this topic>
22637 </BODY>
22638 </HTML>
22639 ====== h_config_saved_msg_name_rule =====
22640 <HTML>
22641 <HEAD>
22642 <TITLE>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></TITLE>
22643 </HEAD>
22644 <BODY>
22645 <H1>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></H1>
22647 This option determines the default folder name when saving
22648 a message.
22650 <P>
22651 The default option is "default-folder", which is the folder
22652 called "saved-messages" in Unix Alpine and
22653 "savemail" in PC-Alpine. To change the default folder, modify
22654 the Alpine option called
22655 <A HREF="h_config_def_save_folder">"<!--#echo var="VAR_default-saved-msg-folder"-->"</A>.
22657 <P>
22658 Choosing any of the "by-" options cause Alpine to attempt to
22659 get the chosen option's value for the message being saved (or for the
22660 first message being saved if using an aggregrate save).
22661 For example, if "by-from" is chosen, Alpine attempts to get the
22662 value of who the message came from (i.e. the from address).
22663 Alpine then attempts to save the message to a folder matching that value.
22664 If "by-from" is chosen and no value is obtained, Alpine uses
22665 "by-sender".
22666 The opposite is also true.
22667 If "by-recipient" is chosen and the message was posted to a
22668 newsgroup, Alpine will use the newsgroup name.
22669 If "by-replyto" is chosen and no value is obtained, Alpine uses
22670 "by-from".
22672 <P>
22673 If any of the "by-realname" options are chosen, Alpine will attempt
22674 to use the personal name part of the address instead of the mailbox part.
22675 If any of the "by-nick" options are chosen, the
22676 address is looked up in your address book and if found, the
22677 nickname for that entry is used.
22678 Only simple address book entries are checked, not distribution lists.
22679 Similarly, if any of the
22680 "by-fcc" options are chosen, the fcc from the corresponding
22681 address book entry is used.
22682 If by-realname, or the by-nick or by-fcc lookups result in no value,
22683 then if the chosen option ends with the "then-from",
22684 "then-sender", "then-replyto",
22685 or "then-recip" suffix, Alpine
22686 reverts to the same behavior as "by-from",
22687 "by-sender", "by-replyto", or "by-recip"
22688 depending on which option was specified.
22689 If the chosen option doesn't end with one of
22690 the "then-" suffixes, then Alpine reverts to the default
22691 folder when no match is found in the address book.
22693 <P>
22694 Choosing the option called "last-folder-used", causes Alpine
22695 to save to the folder that you saved to the last time you saved a
22696 message. The first time you save a message in an Alpine session, Alpine
22697 attempts to save the message to the default folder.
22699 <P>
22700 Here is an example to make some of the options clearer.
22701 If the message is From
22702 <P>
22703 <CENTER><SAMP>Fred Flintstone <flint@bedrock.org></SAMP></CENTER>
22704 <P>
22705 and this rule is set to "by-from", then the default folder offered
22706 in the save dialog would be "flint".
22707 <P>
22708 If this rule is set to "by-realname-of-from" then the default would
22709 be "Fred Flintstone".
22710 <P>
22711 If this rule is set to "by-nick-of-from" then Alpine will search
22712 for the address "flint@bedrock.org" in your address book.
22713 If an entry is found and it has a nickname associated with it, that nickname
22714 will be offered as the default folder.
22715 If not, the default saved message folder will be offered as the default.
22716 <P>
22717 If this rule is set to "by-fcc-of-from" then Alpine will search
22718 for the address "flint@bedrock.org" in your address book.
22719 If an entry is found and it has an Fcc associated with it, that Fcc
22720 will be offered as the default folder.
22721 If not, the default saved message folder will be offered as the default.
22722 <P>
22723 If this rule is set to "by-nick-of-from-then-from" then Alpine will search
22724 for the address "flint@bedrock.org" in your address book.
22725 If an entry is found and it has a nickname associated with it, that nickname
22726 will be offered as the default folder.
22727 If it is not found (or has no nickname) then the default offered will be
22728 the same as it would be for the "by-from" rule.
22729 That is, it would be "flint"
22730 <P>
22731 <UL>
22732 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22733 </UL><P>
22734 <End of help on this topic>
22735 </BODY>
22736 </HTML>
22737 ====== h_config_fcc_rule =====
22738 <HTML>
22739 <HEAD>
22740 <TITLE>OPTION: <!--#echo var="VAR_fcc-name-rule"--></TITLE>
22741 </HEAD>
22742 <BODY>
22743 <H1>OPTION: <!--#echo var="VAR_fcc-name-rule"--></H1>
22745 This option determines the default name for folder carbon copy. Choose
22746 one:
22748 <DL>
22749 <DT>default-fcc</DT>
22750 <DD>This is the normal default, the value of which is set in the
22751 "<!--#echo var="VAR_default-fcc"-->" variable as specified earlier in this
22752 configuration.
22753 </DD>
22755 <DT>last-fcc-used</DT>
22756 <DD> Causes Alpine to use the folder that was last
22757 used in the fcc field
22758 </DD>
22760 <DT>by-nickname</DT>
22761 <DD>Means that Alpine will use the nickname
22762 from your address book that matches the first address in the To line.
22763 If there is no match, it will use the value of the
22764 "<!--#echo var="VAR_default-fcc"-->" variable.
22765 </DD>
22767 <DT>by-recipient</DT>
22768 <DD>Means Alpine will form a folder name
22769 based on the left hand side of the first address in the To line.
22770 </DD>
22772 <DT>by-nick-then-recip</DT>
22773 <DD>Means that it will use the
22774 matching nickname from your address book if there is one, otherwise it
22775 will extract the recipient name from the address and use that (like
22776 by-recipient).
22777 </DD>
22779 <DT>current-folder</DT>
22780 <DD>Causes a copy to be written to
22781 the currently open folder, unless that is the INBOX. In the case
22782 where the current folder is the INBOX, the "<!--#echo var="VAR_default-fcc"-->" is
22783 used instead.
22784 </DD>
22785 </DL>
22787 <P>
22788 Note: Whatever the fcc specified by the rule here, it will be
22789 over-ridden by any fcc entries you have in your address book.
22791 <P>
22792 <UL>
22793 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22794 </UL><P>
22795 <End of help on this topic>
22796 </BODY>
22797 </HTML>
22798 ====== h_config_sort_key =====
22799 <HTML>
22800 <HEAD>
22801 <TITLE>OPTION: <!--#echo var="VAR_sort-key"--></TITLE>
22802 </HEAD>
22803 <BODY>
22804 <H1>OPTION: <!--#echo var="VAR_sort-key"--></H1>
22806 This option determines the order in which messages will be displayed in
22807 the MESSAGE INDEX screen. Choose from:
22808 <P>
22809 <UL>
22810 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
22811 <LI> <A HREF="h_index_sort_date">Date</A>
22812 <LI> <A HREF="h_index_sort_subj">Subject</A>
22813 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
22814 <LI> <A HREF="h_index_sort_thread">Thread</A>
22815 <LI> <A HREF="h_index_sort_from">From</A>
22816 <LI> <A HREF="h_index_sort_size">Size</A>
22817 <LI> <A HREF="h_index_sort_score">Score</A>
22818 <LI> <A HREF="h_index_sort_to">To</A>
22819 <LI> <A HREF="h_index_sort_cc">Cc</A>
22820 </UL>
22822 <P>
22823 Each type of sort may also be reversed.
22824 Normal default is by "Arrival".
22826 <P>
22827 A possible point of confusion arises when you change the configuration
22828 of the <!--#echo var="VAR_sort-key"-->.
22829 The folder will normally be re-sorted when you go back to viewing the
22830 index.
22831 However, if you have manually sorted the folder with the
22832 Sort
22833 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
22834 command, then it will not be re-sorted until the next time it is opened.
22836 <P>
22837 <UL>
22838 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22839 </UL><P>
22840 <End of help on this topic>
22841 </BODY>
22842 </HTML>
22843 ====== h_config_other_startup =====
22844 <HTML>
22845 <HEAD>
22846 <TITLE>OPTION: Set Startup Rule</TITLE>
22847 </HEAD>
22848 <BODY>
22849 <H1>OPTION: Set Startup Rule</H1>
22851 This option determines which message will be the <EM>current message</EM> when
22852 the folder is first opened.
22853 It works the same way that the option
22854 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
22855 works, so look there for help.
22856 It may be used for any folder, not just incoming folders.
22858 <P>
22859 <UL>
22860 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22861 </UL><P>
22862 <End of help on this topic>
22863 </BODY>
22864 </HTML>
22865 ====== h_config_perfolder_sort =====
22866 <HTML>
22867 <HEAD>
22868 <TITLE>Set Sort Order</TITLE>
22869 </HEAD>
22870 <BODY>
22871 <H1>Set Sort Order</H1>
22873 This option determines the order in which messages will be displayed in
22874 the MESSAGE INDEX screen when the Current Folder Type set in the
22875 Pattern is a match. Choose from:
22876 <P>
22877 <UL>
22878 <LI> <A HREF="h_index_sort_default">Default</A>
22879 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
22880 <LI> <A HREF="h_index_sort_date">Date</A>
22881 <LI> <A HREF="h_index_sort_subj">Subject</A>
22882 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
22883 <LI> <A HREF="h_index_sort_thread">Thread</A>
22884 <LI> <A HREF="h_index_sort_from">From</A>
22885 <LI> <A HREF="h_index_sort_size">Size</A>
22886 <LI> <A HREF="h_index_sort_score">Score</A>
22887 <LI> <A HREF="h_index_sort_to">To</A>
22888 <LI> <A HREF="h_index_sort_cc">Cc</A>
22889 </UL>
22891 <P>
22892 Each type of sort may also be reversed.
22893 Normal default is by "Arrival".
22895 <P>
22896 A possible point of confusion arises when you change the configuration
22897 of the Sort Order for the currently open folder.
22898 The folder will normally be re-sorted when you go back to viewing the
22899 index.
22900 However, if you have manually sorted the folder with the
22901 Sort
22902 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
22903 command, then it will not be re-sorted until the next time it is opened.
22905 <P>
22906 <UL>
22907 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22908 </UL><P>
22909 <End of help on this topic>
22910 </BODY>
22911 </HTML>
22912 ====== h_config_fld_sort_rule =====
22913 <HTML>
22914 <HEAD>
22915 <TITLE>OPTION: <!--#echo var="VAR_folder-sort-rule"--></TITLE>
22916 </HEAD>
22917 <BODY>
22918 <H1>OPTION: <!--#echo var="VAR_folder-sort-rule"--></H1>
22920 This option controls the order in which folder list entries will be
22921 presented in the FOLDER LIST screen. Choose one of the following:
22923 <DL>
22924 <DT>Alphabetical</DT>
22925 <DD>sort by alphabetical name independent of type
22926 </DD>
22928 <DT>Alpha-with-dirs-last</DT>
22929 <DD>sort by alphabetical name grouping directory entries
22930 to the end of the list
22931 </DD>
22933 <DT>Alpha-with-dirs-first</DT>
22934 <DD>sort by alphabetical name grouping directory entries
22935 to the start of the list
22936 </DD>
22937 </DL>
22939 The normal default is "Alphabetical".
22941 <P>
22942 <UL>
22943 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22944 </UL><P>
22945 <End of help on this topic>
22946 </BODY>
22947 </HTML>
22948 ====== h_config_ab_sort_rule =====
22949 <HTML>
22950 <HEAD>
22951 <TITLE>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></TITLE>
22952 </HEAD>
22953 <BODY>
22954 <H1>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></H1>
22956 This option controls the order in which address book entries will be
22957 presented. Choose one of the following:
22959 <DL>
22960 <DT>fullname</DT>
22961 <DD>use fullname field, lists mixed in
22962 </DD>
22964 <DT>fullname-with-lists-last</DT>
22965 <DD>use fullname field, but put lists at end
22966 </DD>
22968 <DT>nickname</DT>
22969 <DD>use nickname field, lists mixed in
22970 </DD>
22972 <DT>nickname-with-lists-last</DT>
22973 <DD>use nickname field, but put lists at end
22974 </DD>
22976 <DT>dont-sort</DT>
22977 <DD>don't change order of file
22978 </DD>
22979 </DL>
22981 <P>
22982 The normal default is "fullname-with-lists-last".
22983 If you use an address book from more than one computer and those
22984 computers sort the address book differently then the sort order
22985 will be the order where the last change to the address book was
22986 made.
22987 There are two reasons the sorting might be different on different
22988 systems.
22989 First, the <!--#echo var="VAR_addrbook-sort-rule"--></a> may be set differently in the two
22990 places.
22991 Second, the collation rules on the two computers may be different.
22992 For example, one system might ignore special characters while the other
22993 doesn't or one may sort upper and lower case letters together while
22994 the other doesn't.
22995 In any case, the order you see is the order on the system where the
22996 last change was made, for example by an address book edit or a
22997 Take Address command.
22999 <P>
23000 <UL>
23001 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23002 </UL><P>
23003 <End of help on this topic>
23004 </BODY>
23005 </HTML>
23006 ====== h_config_post_char_set =====
23007 <HTML>
23008 <HEAD>
23009 <TITLE>OPTION: <!--#echo var="VAR_posting-character-set"--></TITLE>
23010 </HEAD>
23011 <BODY>
23012 <H1>OPTION: <!--#echo var="VAR_posting-character-set"--></H1>
23014 The <!--#echo var="VAR_posting-character-set"--> configuration option is used
23015 when sending messages.
23017 <P>
23019 When sending a message the text typed in the composer is
23020 labeled with the character set specified by this option.
23021 If the composed text is not fully representable in the
23022 specified <!--#echo var="VAR_posting-character-set"-->, then it is labeled as "UTF-8."
23023 instead;
23025 <P>
23026 Attachments are labeled with your
23027 <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>.
23029 <P>
23030 Generally, there should be little need to set this option.
23031 If left unset, the
23032 default behavior is to label composed text as specifically as
23033 possible. That is, if the composed text has no non-ASCII characters,
23034 it is labeled as "US-ASCII." Similarly, if it is composed of
23035 only ISO-8859-15 characters, it is labeled as such. Alpine will
23036 attempt to automatically detect a number of character sets including ISO-8859-15,
23037 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
23038 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, and EUC-KR.
23039 If the message contains a mix of character sets,
23040 it is labeled as "UTF-8."
23042 <P>
23044 This setting is provided to allow you to force a particular character set that
23045 Alpine does not automatically detect. For example, if a message is representable
23046 in more than one character set then Alpine may choose a different default
23047 than you want.
23048 Lastly, by setting this option explicitly to
23049 "UTF-8" all non-ASCII messages you send will be labeled as
23050 "UTF-8" instead of something more specific.
23052 <P>
23053 In the Setup/Config screen you may choose from a list of all the
23054 character sets Alpine knows about by using the "T" ToCharsets command.
23056 <P>
23057 The options
23058 <A HREF="h_config_char_set">"Display Character Set"</A>
23059 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
23060 are closely related.
23061 Setting the feature
23062 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23063 should cause this option to be ignored.
23065 <P>
23066 <UL>
23067 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23068 </UL><P>
23069 <End of help on this topic>
23070 </BODY>
23071 </HTML>
23072 ====== h_config_unk_char_set =====
23073 <HTML>
23074 <HEAD>
23075 <TITLE>OPTION: <!--#echo var="VAR_unknown-character-set"--></TITLE>
23076 </HEAD>
23077 <BODY>
23078 <H1>OPTION: <!--#echo var="VAR_unknown-character-set"--></H1>
23080 The <!--#echo var="VAR_unknown-character-set"--> configuration option is used
23081 when reading or replying to messages.
23083 <P>
23085 A text message should either be made up of all US-ASCII characters
23086 or it should contain a charset label which tells the software which
23087 character set encoding to use to interpret the message.
23088 Sometimes a malformed message may be unlabeled but contain non-ascii text.
23089 This message is outside of the standards so any attempt to read it could fail.
23090 When Alpine attempts to read such a message it will try to interpret the
23091 text in the character set you specify here.
23092 For example, if you have correspondents who send you unlabeled messages that
23093 are usually made up of characters from the WINDOWS-1251 character set, setting
23094 this <!--#echo var="VAR_unknown-character-set"--> to <CODE>WINDOWS-1251</CODE> will
23095 allow you to read those messages.
23096 Of course, if the unlabeled message is actually in some other character set,
23097 then you may see garbage on your screen.
23098 <P>
23099 Instead of just unlabeled text, this option also affects text which is labeled
23100 with the charsets "X-Unknown", "MISSING_PARAMETER_VALUE"
23101 or "US-ASCII".
23103 <P>
23104 In the Setup/Config screen you may choose from a list of all the
23105 character sets Alpine knows about by using the "T" ToCharsets command.
23107 <P>
23108 <UL>
23109 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23110 </UL><P>
23111 <End of help on this topic>
23112 </BODY>
23113 </HTML>
23114 ====== h_config_char_set =====
23115 <HTML>
23116 <HEAD>
23117 <TITLE>OPTION: Display Character Set</TITLE>
23118 </HEAD>
23119 <BODY>
23120 <H1>OPTION: Display Character Set</H1>
23122 The Display Character Set configuration option is used when viewing messages.
23123 <P>
23124 Alpine uses Unicode characters internally and
23125 it is a goal for Alpine to handle email in many different languages.
23126 Alpine will properly display only left-to-right character sets
23127 in a fixed-width font. Specifically, Alpine assumes that a fixed-width
23128 font is in use, in the sense that
23129 characters are assumed to take up zero, one, or two character cell
23130 widths from left to right on the screen. This is true even in PC-Alpine.
23131 <P>
23133 Alpine recognizes some local character sets that are right-to-left
23134 (Arabic, Hebrew, and Thai) or not representable in a fixed-width font
23135 (Arabic) and properly converts texts in these character sets to/from
23136 Unicode; however, there are known display bugs with these character
23137 sets.
23138 <P>
23140 There are three possible configuration character settings and some
23141 environment variable settings that can affect how Alpine
23142 handles international characters.
23143 The first two of these are only available in UNIX Alpine.
23144 The three configuration options are
23145 Display Character Set,
23146 Keyboard Character Set, and
23147 <!--#echo var="VAR_posting-character-set"-->.
23148 The Keyboard Character Set defaults to being the same value
23149 as the Display Character Set, and that is usually correct, because
23150 the keyboard almost always produces characters in the same character set
23151 as the display displays.
23152 The Display Character Set is the character set that Alpine
23153 will attempt to use when sending characters to the display.
23154 <P>
23156 By default, the Display Character Set variable is not set and UNIX Alpine
23157 will attempt to get this information from the environment.
23158 In particular, the <CODE>nl_langinfo(CODESET)</CODE> call is used.
23159 This usually depends on the setting of the environment variables LANG or LC_CTYPE.
23160 An explicit configuration setting for Display Character Set will,
23161 of course, override any default setting.
23162 <P>
23163 For PC-Alpine the Display Character Set
23164 and the Keyboard Character Set
23165 are always equivalent to <CODE>UTF-8</CODE> and this is not settable.
23166 <P>
23168 It is probably best to use UNIX Alpine in a terminal emulator
23169 capable of displaying UTF-8 characters, since that will allow you to
23170 view just about any received text that is correctly formatted (note,
23171 however, the above comments about known index display bugs with certain
23172 character sets). You'll need to have an emulator that uses a UTF-8 font
23173 and you'll need to set up your environment to use a UTF-8 charmap. For
23174 example, on a Linux system you might include
23175 <P>
23176 <CENTER> <CODE>setenv LANG en_US.UTF-8</CODE> </CENTER>
23177 <P>
23179 or something similar in your UNIX startup files.
23180 You'd also have to select a UTF-8 font in your terminal emulator.
23181 <P>
23183 The types of values that the character set variables may be set to are
23184 <CODE>UTF-8</CODE>, <CODE>ISO-8859-1</CODE>, or <CODE>EUC-JP</CODE>.
23185 The <CODE>ISO-2022</CODE> character sets are not supported for input or
23186 for display, but as a special case, <CODE>ISO-2022-JP</CODE> is supported
23187 for use only as a <!--#echo var="VAR_posting-character-set"-->.
23188 In the Setup/Config screen you may choose from a list of all the
23189 character sets Alpine knows about by using the "T" ToCharsets command.
23190 Here is a list of many of the possible character sets:
23192 <P>
23193 <TABLE>
23194 <TR> <TD>UTF-8</TD> <TD>Unicode</TD> </TR>
23195 <TR> <TD>US-ASCII</TD> <TD>7 bit American English characters</TD> </TR>
23196 <TR> <TD>ISO-8859-1</TD> <TD>8 bit European "Latin 1" character set</TD> </TR>
23197 <TR> <TD>ISO-8859-2</TD> <TD>8 bit European "Latin 2" character set</TD> </TR>
23198 <TR> <TD>ISO-8859-3</TD> <TD>8 bit European "Latin 3" character set</TD> </TR>
23199 <TR> <TD>ISO-8859-4</TD> <TD>8 bit European "Latin 4" character set</TD> </TR>
23200 <TR> <TD>ISO-8859-5</TD> <TD>8 bit Latin and Cyrillic</TD> </TR>
23201 <TR> <TD>ISO-8859-6</TD> <TD>8 bit Latin and Arabic</TD> </TR>
23202 <TR> <TD>ISO-8859-7</TD> <TD>8 bit Latin and Greek</TD> </TR>
23203 <TR> <TD>ISO-8859-8</TD> <TD>8 bit Latin and Hebrew</TD> </TR>
23204 <TR> <TD>ISO-8859-9</TD> <TD>8 bit European "Latin 5" character set</TD> </TR>
23205 <TR> <TD>ISO-8859-10</TD> <TD>8 bit European "Latin 6" character set</TD> </TR>
23206 <TR> <TD>ISO-8859-11</TD> <TD>Latin and Thai</TD> </TR>
23207 <TR> <TD>ISO-8859-12</TD> <TD>Reserved</TD> </TR>
23208 <TR> <TD>ISO-8859-13</TD> <TD>8 bit European "Latin 7" character set</TD> </TR>
23209 <TR> <TD>ISO-8859-14</TD> <TD>8 bit European "Latin 8" character set</TD> </TR>
23210 <TR> <TD>ISO-8859-15</TD> <TD>8 bit European "Latin 9" character set</TD> </TR>
23211 <TR> <TD>ISO-8859-16</TD> <TD>8 bit European "Latin 10" character set</TD> </TR>
23212 <TR> <TD>KOI8-R</TD> <TD>8 bit Latin and Russian</TD> </TR>
23213 <TR> <TD>KOI8-U</TD> <TD>8 bit Latin and Ukranian</TD> </TR>
23214 <TR> <TD>WINDOWS-1251</TD> <TD>8 bit Latin and Russian</TD> </TR>
23215 <TR> <TD>TIS-620</TD> <TD>8 bit Latin and Thai</TD> </TR>
23216 <TR> <TD>VISCII</TD> <TD>8 bit Latin and Vietnamese</TD> </TR>
23217 <TR> <TD>GBK</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23218 <TR> <TD>GB2312</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23219 <TR> <TD>CN-GB</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23220 <TR> <TD>BIG5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
23221 <TR> <TD>BIG-5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
23222 <TR> <TD>EUC-JP</TD> <TD>Latin and Japanese</TD> </TR>
23223 <TR> <TD>SHIFT-JIS</TD> <TD>Latin and Japanese</TD> </TR>
23224 <TR> <TD>EUC-KR</TD> <TD>Latin and Korean</TD> </TR>
23225 <TR> <TD>KSC5601</TD> <TD>Latin and Korean</TD> </TR>
23226 </TABLE>
23227 <P>
23229 When reading incoming email, Alpine understands many different
23230 character sets and is able to convert the incoming mail into Unicode.
23231 The Unicode will be converted to the Display Character Set
23232 for display on your terminal.
23233 Characters typed at the keyboard will be converted from the
23234 Keyboard Character Set to Unicode for Alpine's internal
23235 use.
23236 You may find that you can read some malformed messages that do not
23237 contain a character set label by setting the option
23238 <A HREF="h_config_unk_char_set">"<!--#echo var="VAR_unknown-character-set"-->"</A>.
23239 <P>
23241 The <!--#echo var="VAR_posting-character-set"--> is used when sending messages.
23242 The default behavior obtained by leaving this variable unset is usually
23243 what is wanted. In that default case, Alpine will attempt
23244 to label the message with the most specific character set from the
23245 rather arbitrary set
23246 <P>
23247 US-ASCII, ISO-8859-15,
23248 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
23249 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, EUC-KR, and UTF-8.
23250 <P>
23252 For example, if the message is made up of only US-ASCII characters, it
23253 will be labeled US-ASCII. Otherwise, if it is all ISO-8859-15 characters,
23254 that will be the label. If that doesn't work the same is tried for the
23255 remaining members of the list.
23257 <P>
23258 It might make sense to set <!--#echo var="VAR_posting-character-set"--> to an
23259 explicit value instead.
23260 For example, if you usually send messages in Greek, setting this
23261 option to ISO-8859-7 will result in messages being labeled as
23262 US-ASCII if there are no non-ascii characters, ISO-8859-7 if there
23263 are only Greek characters, or UTF-8 if there are some characters
23264 that aren't representable in ISO-8859-7.
23265 Another possibility is to set this option explicitly to UTF-8.
23266 In that case
23267 Alpine labels only ascii messages as US-ASCII and all other
23268 messages as UTF-8.
23269 <P>
23271 The options
23272 <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
23273 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
23274 are closely related to this option.
23275 Setting the feature
23276 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23277 should cause this option to be ignored.
23279 <P>
23280 When displaying a message, Alpine compares this setting to the character
23281 set specified in the message. If not all of the
23282 characters in the message can be displayed using the Display Character Set
23283 then Alpine places an editorial
23284 comment in the displayed text (enclosed in square-brackets) indicating
23285 that some characters may not be displayed correctly.
23286 This comment may be eliminated by turning on the option
23287 <A HREF="h_config_quell_charset_warning"><!--#echo var="FEAT_quell-charset-warning"--></A>.
23289 <P>
23290 <UL>
23291 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23292 </UL><P>
23293 <End of help on this topic>
23294 </BODY>
23295 </HTML>
23296 ====== h_config_key_char_set =====
23297 <HTML>
23298 <HEAD>
23299 <TITLE>OPTION: Keyboard Character Set</TITLE>
23300 </HEAD>
23301 <BODY>
23302 <H1>OPTION: Keyboard Character Set</H1>
23304 UNIX Alpine only.
23305 <P>
23306 The Keyboard Character Set identifies the character set of the characters
23307 coming from your keyboard.
23308 It defaults to having the same value as your
23309 <A HREF="h_config_char_set">"Display Character Set"</A>,
23310 which in turn defaults to a value obtained from your environment.
23311 It is unlikely that you will need to use this option, because the keyboard
23312 almost always produces the same kind of characters as the display displays.
23314 <P>
23315 This character set is also used when accessing files in your local
23316 file system.
23317 The names of the files are assumed to be in the same character set as
23318 what the keyboard produces, as well as the contents of the files.
23320 <P>
23321 In the Setup/Config screen you may choose from a list of all the
23322 character sets Alpine knows about by using the "T" ToCharsets command.
23324 <P>
23325 The options
23326 <A HREF="h_config_char_set">"Display Character Set"</A>
23327 and <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
23328 are closely related.
23329 Setting the feature
23330 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23331 should cause this option to be ignored.
23333 <P>
23334 <UL>
23335 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23336 </UL><P>
23337 <End of help on this topic>
23338 </BODY>
23339 </HTML>
23340 ====== h_config_editor =====
23341 <HTML>
23342 <HEAD>
23343 <TITLE>OPTION: <!--#echo var="VAR_editor"--></TITLE>
23344 </HEAD>
23345 <BODY>
23346 <H1>OPTION: <!--#echo var="VAR_editor"--></H1>
23348 <!--#echo var="VAR_editor"--> specifies the program invoked by ^_ in the Composer. This is
23349 normally an alternative to Alpine's internal composer (Pico). You could use
23350 this setting to specify an alternate editor to use occasionally or if you
23351 have a favorite editor and want to use it all the time (see the
23352 <A HREF="h_config_alt_ed_now">"<!--#echo var="FEAT_enable-alternate-editor-implicitly"-->"</A> setting). <P>
23353 If you specify multiple editors for this option, ^_ will invoke the first one
23354 of those specified that exists and is executable. When specifying a program
23355 for use here, make sure that the format of the text it saves -- which, when
23356 you exit it, will become the message body in Alpine -- is appropriate
23357 for the body of an email message; avoid proprietary formats that may result in
23358 a message body that the recipient of your message will be unable to decipher.
23359 <P>
23360 <!--chtml if pinemode="os_windows"-->
23361 <!--chtml else-->
23362 If you are in doubt about what editors are available on your system, or which
23363 of them may be appropriate for specification here, ask your local computing
23364 support staff.
23365 <!--chtml endif-->
23366 <P>
23367 Note that if <a href="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></a> is
23368 unset, outgoing text will be set as flowed. In most cases this will be fine,
23369 but if the editor has a "flowed text" mode, it would be best to
23370 use that.
23372 <P><UL>
23373 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23374 </UL>
23375 <P>
23376 <End of help on this topic>
23377 </BODY>
23378 </HTML>
23379 ====== h_config_speller =====
23380 <HTML>
23381 <HEAD>
23382 <TITLE>OPTION: <!--#echo var="VAR_speller"--></TITLE>
23383 </HEAD>
23384 <BODY>
23385 <H1>OPTION: <!--#echo var="VAR_speller"--></H1>
23387 UNIX Alpine only.
23388 <P>
23389 For PC-Alpine, you must install the aspell library code that you
23390 may get from
23391 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
23392 <P>
23393 This option affects the behavior of the ^T (spell check) command in the
23394 Composer. It specifies the program invoked by ^T in the Composer.
23395 By default, Alpine uses
23396 <P>
23397 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
23398 <P>
23399 if it knows where to find "aspell".
23400 If there is no "aspell" command available but the command "ispell" is available
23401 then the command used is
23402 <P>
23403 <CENTER><SAMP>ispell -l</SAMP></CENTER>
23404 <P>
23405 Otherwise, the ancient "spell" command is used.
23406 <P>
23407 If you specify a value for this command (with full pathname) then that is what
23408 will be used instead of any of the defaults.
23409 When invoking this
23410 spell-checking program, Alpine appends a tempfile name (where the message is
23411 passed) to the command line. Alpine expects the speller to correct the
23412 spelling in that file. When you exit from that program Alpine will read the
23413 tempfile back into the composer.
23414 <P>
23415 Don't set this speller option to the standard Unix spell command.
23416 That won't work because spell works in a different way.
23418 <P>
23419 <UL>
23420 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23421 </UL><P>
23422 <End of help on this topic>
23423 </BODY>
23424 </HTML>
23425 ====== h_config_display_filters =====
23426 <HTML>
23427 <HEAD>
23428 <TITLE>OPTION: <!--#echo var="VAR_display-filters"--></TITLE>
23429 </HEAD>
23430 <BODY>
23431 <H1>OPTION: <!--#echo var="VAR_display-filters"--></H1>
23433 This option defines a list of text-filtering commands (programs or
23434 scripts) that may be used to filter text portions of received messages
23435 prior to their use (e.g., presentation in the "MESSAGE TEXT"
23436 display screen, exporting to a text file).
23437 For security reasons, the full path name of the
23438 filter command must be specified.
23440 <P>
23441 The command is executed and the message is piped into its standard input.
23442 The standard output of the command is read back by Alpine. The
23443 "_TMPFILE_" token (see below) overrides this default behavior.
23445 <P>
23446 The filter's use is based on the configured "trigger" string. The
23447 format of a filter definition is:
23449 <P>
23450 <CENTER><trigger> <command> <arguments></CENTER>
23452 <P>
23453 You can specify as many filters as you wish, separating them with a comma.
23454 Each filter can have only one trigger and command. Thus, two trigger
23455 strings that invoke the same command require separate filter
23456 specifications.
23458 <P>
23459 The "trigger" is simply text that, if found in the message,
23460 will invoke the associated command. If the trigger contains any space
23461 characters, it must be placed within quotes. Likewise, should you
23462 wish a filter to be invoked unconditionally, define the trigger as the
23463 null string, "" (two consecutive double-quote characters). If the
23464 trigger string is found anywhere in the text of the message the filter
23465 is invoked. Placing the trigger text within the tokens defined below
23466 changes where within the text the trigger must be before considering
23467 it a match.
23469 <P>
23470 Trigger Modifying Tokens:
23471 <DL>
23472 <DT>_CHARSET(<VAR>string</VAR>)_</DT>
23473 <DD>This token tells Alpine to invoke the supplied command
23474 if the text is in a character set matching <VAR>string</VAR>
23475 (e.g., ISO-8859-2 or ISO-2022-JP).
23476 </DD>
23479 <DT>_LEADING(<VAR>string</VAR>)_</DT>
23480 <DD>This token tells Alpine to invoke the supplied command
23481 if the enclosed <VAR>string</VAR> is found to be the first
23482 non-whitespace text.
23483 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23484 the space character.
23485 </DD>
23487 <DT>_BEGINNING(<VAR>string</VAR>)_</DT>
23488 <DD>This token tells Alpine to invoke the supplied command
23489 if the enclosed <VAR>string</VAR> is found at the beginning
23490 of any line in the text.
23491 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23492 the space character.
23493 </DD>
23494 </DL>
23496 <P>
23497 The "command" and "arguments" portion is simply
23498 the command line to be invoked if the trigger string is found. Below
23499 are tokens that Alpine will recognize and replace with special values
23500 when the command is actually invoked.
23502 <P>
23503 Command Modifying Tokens:
23505 <DL>
23506 <DT>_TMPFILE_</DT>
23507 <DD>When the command is executed, this token is
23508 replaced with the path and name of the temporary
23509 file containing the text to be filtered. Alpine
23510 expects the filter to replace this data with the
23511 filter's result.
23513 <P>
23514 NOTE: Use of this token implies that the text to
23515 be filtered is not piped into standard input of the
23516 executed command and its standard output is ignored.
23517 Alpine restores the tty modes before invoking the
23518 filter in case the filter interacts with the user
23519 via its own standard input and output.
23520 </DD>
23522 <DT>_RESULTFILE_</DT>
23523 <DD>When the command is executed, this token is
23524 replaced with the path and name of a temporary
23525 file intended to contain a status message from the
23526 filter. Alpine displays this in the message status
23527 field.
23528 </DD>
23530 <DT>_DATAFILE_</DT>
23531 <DD>When the command is executed, this token is
23532 replaced with the path and name of a temporary
23533 file that Alpine creates once per session and deletes
23534 upon exit. The file is intended to be used by the
23535 filter to store state information between instances
23536 of the filter.
23537 </DD>
23539 <DT>_PREPENDKEY_</DT>
23540 <DD>When the command is executed, this token indicates that a random
23541 number will be passed down the input stream before the message text.
23542 This number could be used as a session key. It is sent in this way to
23543 improve security. The number is unique to the current Alpine session
23544 and is only generated once per session.
23545 </DD>
23547 <DT>_SILENT_</DT>
23548 <DD>When the filter is executed, this token tells Alpine not to repaint
23549 the screen while the command is being executed. This can be used with
23550 filters that do not interact with the user, and therefore repainting
23551 the screen is not necessary.
23552 </DD>
23553 </DL>
23555 <P>
23556 The feature
23557 <A HREF="h_config_disable_reset_disp"><!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></A> is related.
23558 <P>
23559 Performance caveat/considerations:
23560 <BR>
23561 Testing for the trigger and invoking the filter doesn't come for free.
23562 There is overhead associated with searching for the trigger string, testing
23563 for the filter's existence and actually piping the text through the filter.
23564 The impact can be reduced if the Trigger Modifying Tokens above are
23565 employed.
23566 <P>
23567 <End of help on this topic>
23568 </BODY>
23569 </HTML>
23570 ====== h_config_sending_filter =====
23571 <HTML>
23572 <HEAD>
23573 <TITLE>OPTION: <!--#echo var="VAR_sending-filters"--></TITLE>
23574 </HEAD>
23575 <BODY>
23576 <H1>OPTION: <!--#echo var="VAR_sending-filters"--></H1>
23578 This option defines a list of text-filtering commands (programs and
23579 scripts) that may be selectively invoked to process a message just before
23580 it is sent. If set, the Composer's ^X (Send) command will allow you to
23581 select which filter (or none) to apply to the message before it is sent.
23582 For security reasons, the full path of the filter program must be
23583 specified.
23585 <P>
23586 Command Modifying Tokens:
23588 <DL>
23589 <DT>_RECIPIENTS_</DT>
23590 <DD>When the command is executed, this token is replaced
23591 with the space delimited list of recipients of the
23592 message being sent.
23593 </DD>
23595 <DT>_TMPFILE_</DT>
23596 <DD>
23597 When the command is executed, this token is
23598 replaced with the path and name of the temporary
23599 file containing the text to be filtered. Alpine
23600 expects the filter to replace this data with the
23601 filter's result.
23603 <P>
23604 NOTE: Use of this token implies that the text to
23605 be filtered is not piped into standard input of the
23606 executed command and its standard output is ignored.
23607 Alpine restores the tty modes before invoking the
23608 filter in case the filter interacts with the user
23609 via its own standard input and output.
23610 </DD>
23612 <DT>_RESULTFILE_</DT>
23613 <DD>When the command is executed, this token is
23614 replaced with the path and name of a temporary
23615 file intended to contain a status message from the
23616 filter. Alpine displays this in the message status
23617 field.
23618 </DD>
23620 <DT>_DATAFILE_</DT>
23621 <DD>When the command is executed, this token is replaced
23622 in the command line with the path and name of a
23623 temporary file that Alpine creates once per session
23624 and deletes upon exit. The file is intended to be
23625 used by the filter to store state information between
23626 instances of the filter.
23627 </DD>
23629 <DT>_PREPENDKEY_</DT>
23630 <DD>When the command is executed, this token indicates
23631 that a random number will be passed down the input
23632 stream before the message text. This number could
23633 be used as a session key. It is sent in this way
23634 to improve security. The number is unique to the
23635 current Alpine session and is only generated once per
23636 session.
23637 </DD>
23639 <DT>_INCLUDEALLHDRS_</DT>
23640 <DD>When the command is executed, this token indicates
23641 that the headers of the message will be passed down the input stream
23642 before the message text.
23643 </DD>
23645 <DT>_MIMETYPE_</DT>
23646 <DD>When the command is executed, this token is replaced in the
23647 command name with a temporary file name used to accept any new MIME
23648 Content-Type information necessitated by the output of the filter.
23649 Upon the filter's exit, if the file contains new MIME type
23650 information, Alpine verifies its format and replaces the outgoing
23651 message's MIME type information with that contained in the file. This
23652 is basically a cheap way of sending something other than Text/Plain.
23653 </DD>
23654 </DL>
23656 <P>
23657 NOTE: Only the body text, which is visible in the Composer, is piped
23658 through this filter. Attachments are not sent to the filter.
23659 <P>
23660 Sending filters are not used if the feature
23661 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set.
23662 <P>
23663 <UL>
23664 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23665 </UL><P>
23666 <End of help on this topic>
23667 </BODY>
23668 </HTML>
23669 ====== h_config_keywords =====
23670 <HTML>
23671 <HEAD>
23672 <TITLE>OPTION: <!--#echo var="VAR_keywords"--></TITLE>
23673 </HEAD>
23674 <BODY>
23675 <H1>OPTION: <!--#echo var="VAR_keywords"--></H1>
23677 You may define your own set of keywords and optionally set them on a
23678 message by message basis.
23679 These are similar to the "Important" flag which the user
23680 may set using the Flag command.
23681 The difference is that the Important flag is always present for each folder.
23682 User-defined keywords are chosen by the user.
23683 You may set up the list of possible keywords here, or you may add keywords
23684 from the Flag Details screen that you
23685 can get to after typing the
23686 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
23687 command.
23688 After the keywords have been defined,
23689 then you use the <A HREF="h_common_flag">Flag command</A>
23690 to set or clear the keywords in each message.
23691 The behavior of the flag command may be modified by using the
23692 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
23693 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
23695 <P>
23696 Keywords may be used when Selecting messages (Select Keyword).
23697 Keywords may also be used in the Patterns of Rules (Filters, Indexcolors, etc).
23698 Filter Rules may be used to set keywords automatically.
23699 Keywords may be displayed as part of the Subject of a message by using
23700 the SUBJKEY or SUBJKEYINIT tokens in the
23701 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
23702 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
23703 option may be used to modify the display of keywords using
23704 SUBJKEY and SUBJKEYINIT slightly.
23705 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
23706 screen by using the KEY or KEYINIT tokens.
23707 It is also possible to color keywords in the index using the
23708 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
23709 Keywords are not supported by all mail servers.
23711 <P>
23712 You may give keywords nicknames if you wish.
23713 If the keyword definition you type in contains a SPACE character, then the
23714 actual value of the keyword is everything after the last SPACE and the
23715 nickname for that keyword is everything before the last SPACE.
23716 For example, suppose you are trying to interoperate with another email program
23717 that uses a particular keyword with an unpleasant name.
23718 Maybe it uses a keyword called
23719 <P>
23720 <CENTER><SAMP>VendorName.SoftwareName.08</SAMP></CENTER>
23721 <P>
23722 but for you that keyword means that the message is work-related.
23723 You could define a keyword to have the value
23724 <P>
23725 <CENTER><SAMP>Work VendorName.SoftwareName.08</SAMP></CENTER>
23726 <P>
23727 and then you would use the name "Work" when dealing with
23728 that keyword in Alpine.
23729 If you defined it as
23730 <P>
23731 <CENTER><SAMP>My Work VendorName.SoftwareName.08</SAMP></CENTER>
23732 <P>
23733 the nickname would be everything before the last SPACE, that is the nickname
23734 would be "My Work".
23735 <P>
23736 Some commonly used keywords begin with dollar signs.
23737 This presents a slight complication, because the dollar sign is normally used
23738 to signify
23739 <A HREF="h_news_config">environment variable expansion</A>
23740 in the Alpine configuration.
23741 In order to specify a keyword that begins with a dollar sign you must
23742 precede the dollar sign with a second dollar sign to escape its special
23743 meaning.
23744 For example, if you want to include the keyword
23745 <P>
23746 <CENTER><SAMP>$Label1</SAMP></CENTER>
23747 <P>
23748 as one of your possible keywords, you must enter the text
23749 <P>
23750 <CENTER><SAMP>$$Label1</SAMP></CENTER>
23751 <P>
23753 instead.
23754 <P>
23755 There are a couple limitations.
23756 First, not all servers support keywords.
23757 Second, some servers (including the IMAP server included with Alpine)
23758 have a per folder limit on the number of keywords that may be defined.
23759 This count commonly includes every keyword you have ever used in the
23760 folder, even if it is no longer being used.
23761 In other words, you can add keywords but you cannot remove them easily.
23762 If you have changed keywords over the life of a folder and find that
23763 you have reached such a limit, one possible solution might be to copy
23764 all of the messages to a newly created folder (using Alpine) and then
23765 delete the original and rename the new folder.
23766 The reason this might work is that only the keywords currently set in
23767 any of the messages will be used in the new folder, hopefully putting you
23768 under the limit.
23770 <P>
23771 <UL>
23772 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23773 </UL><P>
23774 <End of help on this topic>
23775 </BODY>
23776 </HTML>
23777 ====== h_config_alt_addresses =====
23778 <HTML>
23779 <HEAD>
23780 <TITLE>OPTION: <!--#echo var="VAR_alt-addresses"--></TITLE>
23781 </HEAD>
23782 <BODY>
23783 <H1>OPTION: <!--#echo var="VAR_alt-addresses"--></H1>
23785 This option provides a place for you to list alternate email addresses
23786 you may have.
23787 Each address in the list should be the actual email address part of an
23788 address, without the full name field or the angle brackets.
23789 For example:
23791 <P>
23792 <CENTER><SAMP>user@example.com</SAMP></CENTER>
23793 <P>
23795 The matching is case-insensitive, so this would match any of
23796 <SAMP>User@example.com</SAMP>, <SAMP>user@Example.Com</SAMP>, or
23797 <SAMP>USER@EXAMPLE.COM</SAMP> as well.
23799 <P>
23800 If set, the option affects the behavior of the Reply
23801 command and the "+" symbol in the MESSAGE INDEX, which denotes that
23802 a message has been addressed specifically to you.
23804 <P>
23805 In the default INDEX display
23806 the personal name (or email address) of
23807 the person listed in the message's "From:" header
23808 field is usually displayed except when that address is yours or one of your
23809 alternate addresses.
23810 In that case you will usually see the name of
23811 the first person specified in the
23812 message's "To:" header field
23813 with the prefix "To: " prepended.
23815 <P>
23816 With respect to Reply, the reply-to-all option will exclude addresses
23817 listed here.
23819 <P>
23820 The feature
23821 <A HREF="h_config_copy_to_to_from"><!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></A>
23822 is somewhat related to this option.
23824 <P>
23825 In addition to a list of actual addresses,
23826 you may use regular expressions (as used with egrep with the ignore case flag)
23827 to describe the addresses you want to match.
23828 Alpine will somewhat arbitrarily interpret your entry as a regular
23829 expression if it contains any of the characters
23830 *, |, +, ?, {, [, ^, $, or \.
23831 Otherwise, it will be treated literally.
23832 The feature
23833 <a href="h_config_disable_regex"><!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
23834 may be used to turn off regular expression processing regardless of whether or not
23835 special characters appear in the entry.
23837 <P>
23838 A description of how regular expressions work is beyond the
23839 scope of this help text, but some examples follow.
23841 <P>
23842 The entry
23844 <P>
23845 <CENTER><SAMP>.*@example.com</SAMP></CENTER>
23846 <P>
23848 in the <!--#echo var="VAR_alt-addresses"--> list would mean that any
23849 address with a domain name of <SAMP>example.com</SAMP> (such as
23850 <SAMP>fred@example.com</SAMP> or <SAMP>wilma@example.com</SAMP>) will be considered
23851 one of your alternate addresses.
23852 Strictly speaking, the dot in <SAMP>example.com</SAMP> ought to be escaped with
23853 a backslash, as in <SAMP>example\.com</SAMP>, and a dollar sign anchor ought
23854 to come at the end of the expression to prevent a match of <SAMP>example.com.org</SAMP>.
23855 Complicating things further, the dollar sign
23856 is special in the Alpine configuration (it signifies environment variable expansion)
23857 so the dollar sign should be doubled or backslash escaped for Alpine's sake.
23858 Quotes around the whole expression will not escape the dollar sign successfully.
23859 So this example should look like
23861 <P>
23862 <CENTER><SAMP>.*@example\.com$$</SAMP></CENTER>
23863 <P>
23865 <P>
23866 The entry
23868 <P>
23869 <CENTER><SAMP>^fred[0-9]*@example.com$$</SAMP></CENTER>
23870 <P>
23872 would match
23873 <SAMP>fred3@example.com</SAMP> or <SAMP>fred17@example.com</SAMP> as well
23874 as <SAMP>fred@example.com</SAMP>.
23876 <P>
23877 You could match all addresses that look like
23878 <SAMP>fred+stuff@example.com</SAMP> for any value of <SAMP>stuff</SAMP> with the
23879 entry
23881 <P>
23882 <CENTER><SAMP>^fred\+.*@example.com$$</SAMP></CENTER>
23883 <P>
23885 Notice that you have to escape the plus sign with a backslash because plus
23886 is a special character in regular expressions.
23887 If you wanted to match plain <SAMP>fred</SAMP> as well as <SAMP>fred+stuff</SAMP>
23888 the expression
23890 <P>
23891 <CENTER><SAMP>^fred(()|\+.*)@example.com$$</SAMP></CENTER>
23892 <P>
23894 would do it, but it would be easier to just add fred@example.com as a
23895 separate entry.
23897 <P>
23898 One more example, a match of all first-level subdomains, is given by
23900 <P>
23901 <CENTER><SAMP>^fred@[[:alnum:]_-]*\.example\.com$$</SAMP></CENTER>
23902 <P>
23904 <P>
23905 Because the regular expression matching is based on an old library
23906 (<SAMP>hs_regex</SAMP>) the regular expressions might not work exactly as you expect,
23907 but they should be close.
23909 <P>
23910 <UL>
23911 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23912 </UL><P>
23913 <End of help on this topic>
23914 </BODY>
23915 </HTML>
23916 ====== h_config_abook_formats =====
23917 <HTML>
23918 <HEAD>
23919 <TITLE>OPTION: <!--#echo var="VAR_addressbook-formats"--></TITLE>
23920 </HEAD>
23921 <BODY>
23922 <H1>OPTION: <!--#echo var="VAR_addressbook-formats"--></H1>
23924 This option specifies the format that address books are displayed in.
23925 Normally, address books are displayed with the nicknames in the first
23926 column, the fullnames in the second column, and addresses in the third
23927 column. The system figures out reasonable defaults for the widths of
23928 the columns. An address book may be given a different format by
23929 listing special tokens in the order you want them to display. The
23930 possible tokens are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT.
23931 So, for example, to get the default behavior you could list
23933 <P>
23934 <CENTER><!--#echo var="VAR_addressbook-formats"-->=NICKNAME FULLNAME ADDRESS</CENTER>
23936 <P>
23937 (You can also use the token DEFAULT to get the default behavior for
23938 an address book format.)
23940 <P>
23941 The tokens are separated by spaces. "<!--#echo var="VAR_addressbook-formats"-->"
23942 is a list, so if you have more than one address book you may have a
23943 separate format for each by putting its format at the corresponding
23944 location in the "<!--#echo var="VAR_addressbook-formats"-->" list.
23946 <P>
23948 Listed first are the personal address books, then the global address
23949 books. So, if you have two personal address books and one global
23950 address book, you may have up to three formats in the
23951 "<!--#echo var="VAR_addressbook-formats"-->" list. If
23952 "<!--#echo var="VAR_addressbook-formats"-->" doesn't have as many elements as there
23953 are address books, the last element is used repeatedly.
23955 <P>
23957 Each of the tokens may also be optionally followed by parentheses with
23958 either a number or a percentage inside the parentheses. For example,
23959 <SAMP>FULLNAME(13)</SAMP> means to allocate 13 characters of space to
23960 the fullnames column, <SAMP>FULLNAME(20%)</SAMP> means to allocate 20%
23961 of the available space (the screen width minus the space for
23962 inter-column spaces) to the fullnames column, while plain
23963 <SAMP>FULLNAME</SAMP> means the system will attempt to figure out a
23964 reasonable number of columns.
23966 <P>
23967 There are always 2 spaces between every column, so if you use
23968 fixed column widths (like 13) you should remember to take that into
23969 account.
23971 <P>
23972 <UL>
23973 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23974 </UL><P>
23975 <End of help on this topic>
23976 </BODY>
23977 </HTML>
23978 ====== h_config_set_index_format =====
23979 <HTML>
23980 <HEAD>
23981 <TITLE>Set Index Format</TITLE>
23982 </HEAD>
23983 <BODY>
23984 <H1>Set Index Format</H1>
23986 This option is used to customize the content of lines in the
23987 <A HREF="h_mail_index">MESSAGE INDEX screen</A>.
23988 This action works exactly like the regular
23989 "<!--#echo var="VAR_index-format"-->" option in the Setup/Config screen,
23990 except that you can have a folder-specific value for it if you specify it here.
23991 Consult the help for
23992 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
23993 for more information.
23995 <P>
23996 <UL>
23997 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23998 </UL><P>
23999 <End of help on this topic>
24000 </BODY>
24001 </HTML>
24002 ====== h_config_index_format =====
24003 <HTML>
24004 <HEAD>
24005 <TITLE>OPTION: <!--#echo var="VAR_index-format"--></TITLE>
24006 </HEAD>
24007 <BODY>
24008 <H1>OPTION: <!--#echo var="VAR_index-format"--></H1>
24010 This option is used to customize the content of lines in the
24011 <A HREF="h_mail_index">MESSAGE INDEX screen</A>. Each line is intended
24012 to convey some amount of immediately relevant information about each
24013 message in the current folder.
24014 <P>
24016 Alpine provides a pre-defined set of informational fields with
24017 reasonable column widths automatically computed. You can, however,
24018 replace this default set by listing special tokens in the order you
24019 want them displayed.
24020 <P>
24022 The list of available tokens is
24023 <A HREF="h_index_tokens">here</A>.
24024 <P>
24026 Spaces are used to separate listed tokens. Additionally, you can
24027 specify how much of the screen's width the token's associated data
24028 should occupy on the index line by appending to the token a pair of
24029 parentheses enclosing either a number or percentage. For example,
24030 "SUBJECT(13)" means to allocate 13 characters of space to the subject
24031 column, and "SUBJECT(20%)" means to
24032 allocate 20% of the available space
24033 to the subjects column, while plain "SUBJECT" means the system will
24034 attempt to figure out a reasonable amount of space.
24035 <P>
24037 There is always one space between every pair of columns, so if you use fixed
24038 column widths (like 13) you should remember to take that into account.
24039 Several of the fields are virtually fixed-width, so it doesn't make
24040 much sense to specify the width for them. The fields STATUS,
24041 FULLSTATUS, IMAPSTATUS, MSGNO, the DATE fields, SIZE,
24042 and DESCRIPSIZE all fall into that category.
24043 You <EM>may</EM> specify widths for those if you wish, but
24044 you're probably better off letting the system pick those widths. <P>
24046 <P>
24047 The default is equivalent to:
24049 <P>
24050 <CENTER><SAMP>STATUS MSGNO SMARTDATETIME24 FROMORTO(33%) SIZENARROW SUBJKEY(67%)</SAMP></CENTER>
24052 <P>
24053 This means that the four fields without percentages will be allocated
24054 first, and then 33% and 67% of the <EM>remaining</EM> space will go to
24055 the from and subject fields. If one of those two fields is specified
24056 as a percentage and the other is left for the system to choose, then
24057 the percentage is taken as an absolute percentage of the screen, not
24058 of the space remaining after allocating the first four columns. It
24059 doesn't usually make sense to do it that way. If you leave off all
24060 the widths, then the subject and from fields (if both are present) are
24061 allocated space in a 2 to 1 ratio, which is almost exactly the same as
24062 the default.
24064 <P>
24065 What you are most likely to do with this configuration option is to
24066 specify which fields appear at all, which order they appear in, and the
24067 percentage of screen that is used for the from and subject fields if you
24068 don't like the 2 to 1 default.
24070 <P>
24071 If you want to retain the default format that Pine 4.64 had, use
24073 <P>
24074 <CENTER><SAMP><!--#echo var="VAR_index-format"-->=STATUS MSGNO DATE FROMORTO(33%) SIZE SUBJKEY(67%)</SAMP></CENTER>
24075 <P>
24076 <EM>and</EM> set the feature
24077 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>.
24078 <UL>
24079 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24080 </UL><P>
24081 <End of help on this topic>
24082 </BODY>
24083 </HTML>
24084 ====== h_config_reply_intro =====
24085 <HTML>
24086 <HEAD>
24087 <TITLE>OPTION: <!--#echo var="VAR_reply-leadin"--></TITLE>
24088 </HEAD>
24089 <BODY>
24090 <H1>OPTION: <!--#echo var="VAR_reply-leadin"--></H1>
24092 This option is used to customize the content of the introduction line
24093 that is included when replying to a message and including the original
24094 message in the reply.
24095 The normal default (what you will get if you delete this variable) looks
24096 something like:
24097 <P>
24098 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
24099 <P>
24100 where the day of the week is only included if it is available in the
24101 original message.
24102 You can replace this default with text of your own.
24103 The text may contain tokens that are replaced with text
24104 that depends on the message you are replying to.
24105 For example, the default is equivalent to:
24106 <P>
24107 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
24108 <P>
24110 Since this variable includes regular text mixed with special tokens
24111 the tokens have to be surrounded by underscore characters.
24112 For example, to use the token "<SAMP>PREFDATE</SAMP>"
24113 you would need to use "<SAMP>_PREFDATE_</SAMP>",
24114 not "<SAMP>PREFDATE</SAMP>".
24115 <P>
24116 The list of available tokens is
24117 <A HREF="h_index_tokens">here</A>.
24119 <P>
24120 By default, the text is all on a single line and is followed by a blank line.
24121 If your "<!--#echo var="VAR_reply-leadin"-->" turns out to be longer
24122 than 80 characters when replying to a particular message, it is shortened.
24123 However, if you use the token
24124 <P>
24125 <CENTER><SAMP>_NEWLINE_</SAMP></CENTER>
24126 <P>
24128 anywhere in the value, no end of line or blank line is appended, and no
24129 shortening is done.
24130 The _NEWLINE_ token may be used to get rid of the blank line following
24131 the text, to add more blank lines, or to form a multi-line
24132 "<!--#echo var="VAR_reply-leadin"-->".
24133 To clarify how _NEWLINE_ works recall that the default value is:
24134 <P>
24135 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
24136 <P>
24138 That is equivalent to
24139 <P>
24140 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE__NEWLINE_</SAMP></CENTER>
24141 <P>
24143 In the former case, two newlines are added automatically because
24144 no _NEWLINE_ token appears in the value of the option (for backwards
24145 compatibility). In the latter case, the newlines are explicit.
24146 If you want to remove the blank line that follows the
24147 "<!--#echo var="VAR_reply-leadin"-->" text use a single
24148 _NEWLINE_ token like
24149 <P>
24150 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE_</SAMP></CENTER>
24151 <P>
24153 Because of the backwards compatibility problem, it is not possible to
24154 remove all of the ends of lines, because then there will be no _NEWLINE_ tokens
24155 and that will cause the automatic adding of two newlines!
24156 If you want, you may embed newlines in the middle of the text, as well,
24157 producing a multi-line "<!--#echo var="VAR_reply-leadin"-->".
24159 <P>
24160 By default, no attempt is made to localize the date.
24161 If you prefer a localized form you may find that one of the tokens
24162 _PREFDATE_ or _PREFDATETIME_ is a satisfactory substitute.
24163 If you want more control one of the many other date tokens, such as _DATEISO_,
24164 might be better.
24166 <P>
24167 For the adventurous, there is a way to conditionally include text based
24168 on whether or not a token would result in specific replacement text.
24169 For example, you could include some text based on whether or not
24170 the _NEWS_ token would result in any newsgroups if it was used.
24171 It's explained in detail
24172 <A HREF="h_reply_token_conditionals">here</A>.
24174 <P>
24175 In the very unlikely event that you want to include a literal token
24176 in the introduction line you must precede it with a backslash character.
24177 For example,
24178 <P>
24179 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
24180 <P>
24181 would produce something like
24182 <P>
24183 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
24184 <P>
24185 It is not possible to have a literal backslash followed by an expanded token.
24186 <P>
24187 <UL>
24188 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24189 </UL><P>
24190 <End of help on this topic>
24191 </BODY>
24192 </HTML>
24193 ====== h_config_remote_abook_history =====
24194 <HTML>
24195 <HEAD>
24196 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-history"--></TITLE>
24197 </HEAD>
24198 <BODY>
24199 <H1>OPTION: <!--#echo var="VAR_remote-abook-history"--></H1>
24201 Sets how many extra copies of
24202 remote address book
24203 data will be kept in each remote address book folder.
24204 The default is three.
24205 These extra copies are simply old versions of the data. Each time a change
24206 is made a new copy of the address book data is appended to the folder. Old
24207 copies are trimmed, if possible, when Alpine exits.
24208 An old copy can be put back into use by
24209 deleting and expunging newer versions of the data from the folder.
24210 Don't delete the first message from the folder. It is a special header
24211 message for the remote address book and it must be there.
24212 This is to prevent regular folders from being used as remote address book
24213 folders and having their data destroyed.
24214 <P>
24215 This option is also used to determine how many extra copies of remote
24216 Alpine configuration files are kept.
24217 <P>
24218 <UL>
24219 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24220 </UL><P>
24221 <End of help on this topic>
24222 </BODY>
24223 </HTML>
24224 ====== h_config_remote_abook_validity =====
24225 <HTML>
24226 <HEAD>
24227 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-validity"--></TITLE>
24228 </HEAD>
24229 <BODY>
24230 <H1>OPTION: <!--#echo var="VAR_remote-abook-validity"--></H1>
24232 Sets the minimum number of minutes that a
24233 remote address book will be considered up to date.
24234 Whenever an entry contained in a remote address book is used,
24235 if more than this many minutes have
24236 passed since the last check the remote server will be queried to see if the
24237 address book has changed.
24238 If it has changed, the local copy is updated.
24239 The default value is five minutes.
24240 The special value of -1 means never check.
24241 The special value of zero means only check when the address book is first
24242 opened.
24243 <P>
24244 No matter what the value, the validity check is always done when the
24245 address book is about to be changed by the user.
24246 The check can be initiated manually by typing <EM>^L</EM> (Ctrl-L)
24247 while in the address book maintenance screen for the remote address book.
24248 <P>
24249 <UL>
24250 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24251 </UL><P>
24252 <End of help on this topic>
24253 </BODY>
24254 </HTML>
24255 ====== h_config_user_input_timeo =====
24256 <HTML>
24257 <HEAD>
24258 <TITLE>OPTION: <!--#echo var="VAR_user-input-timeout"--></TITLE>
24259 </HEAD>
24260 <BODY>
24261 <H1>OPTION: <!--#echo var="VAR_user-input-timeout"--></H1>
24263 If this is set to an integer greater than zero, then this is the number
24264 of <EM>hours</EM> to wait for user input before Alpine times out.
24265 If Alpine is
24266 in the midst of composing a message or is waiting for user response to
24267 a question, then it will not timeout.
24268 However, if Alpine is sitting idle waiting for
24269 the user to tell it what to do next and the user does not give any
24270 input for this many hours, Alpine will exit.
24271 No expunging or moving of read
24272 messages will take place.
24273 It will exit similarly to the way it would exit
24274 if it received a hangup signal.
24275 This may be useful for cleaning up unused Alpine sessions that have been
24276 forgotten by their owners.
24277 The Alpine developers envision system administrators
24278 setting this to a value of several hours (24?) so that it won't surprise
24279 a user who didn't want to be disconnected.
24280 <P>
24281 <UL>
24282 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24283 </UL><P>
24284 <End of help on this topic>
24285 </BODY>
24286 </HTML>
24287 ====== h_config_ssh_open_timeo =====
24288 <HTML>
24289 <HEAD>
24290 <TITLE>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></TITLE>
24291 </HEAD>
24292 <BODY>
24293 <H1>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></H1>
24295 Sets the time in seconds that Alpine will
24296 attempt to open a UNIX secure shell connection.
24297 The default is 15, the minimum non-zero value is 5,
24298 and the maximum is unlimited. If this is set to zero ssh connections
24299 will be completely disabled.
24300 <P>
24301 <UL>
24302 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24303 </UL><P>
24304 <End of help on this topic>
24305 </BODY>
24306 </HTML>
24307 ====== h_config_rsh_open_timeo =====
24308 <HTML>
24309 <HEAD>
24310 <TITLE>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></TITLE>
24311 </HEAD>
24312 <BODY>
24313 <H1>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></H1>
24315 Sets the time in seconds that Alpine will
24316 attempt to open a UNIX remote shell connection.
24317 The default is 15, the minimum non-zero value is 5,
24318 and the maximum is unlimited. If this is set to zero rsh connections
24319 will be completely disabled.
24320 This might be useful if rsh connections will never work in your environment
24321 but are causing delays due to firewalls or some other reason.
24322 <P>
24323 <UL>
24324 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24325 </UL><P>
24326 <End of help on this topic>
24327 </BODY>
24328 </HTML>
24329 ====== h_config_tcp_open_timeo =====
24330 <HTML>
24331 <HEAD>
24332 <TITLE>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></TITLE>
24333 </HEAD>
24334 <BODY>
24335 <H1>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></H1>
24337 Sets the time in seconds that Alpine will
24338 attempt to open a network connection. The default is 30, the minimum is 5,
24339 and the maximum is system defined (typically 75). If a connection has not
24340 completed within this many seconds Alpine will give up and consider it a
24341 failed connection.
24342 <P>
24343 <UL>
24344 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24345 </UL><P>
24346 <End of help on this topic>
24347 </BODY>
24348 </HTML>
24349 ====== h_config_tcp_readwarn_timeo =====
24350 <HTML>
24351 <HEAD>
24352 <TITLE>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></TITLE>
24353 </HEAD>
24354 <BODY>
24355 <H1>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></H1>
24357 Sets the time in seconds that Alpine will
24358 wait for a network read before warning you that things are moving slowly
24359 and possibly giving you the option to break the connection.
24360 The default is 15 seconds. The minimum is 5 seconds and the maximumn is
24361 1000 seconds.
24362 <P>
24363 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24364 <P>
24365 <UL>
24366 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24367 </UL><P>
24368 <End of help on this topic>
24369 </BODY>
24370 </HTML>
24371 ====== h_config_tcp_writewarn_timeo =====
24372 <HTML>
24373 <HEAD>
24374 <TITLE>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></TITLE>
24375 </HEAD>
24376 <BODY>
24377 <H1>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></H1>
24379 Sets the time in seconds that Alpine will
24380 wait for a network write before warning you that things are moving slowly
24381 and possibly giving you the option to break the connection.
24382 The default is 0 which means it is unset. If set to a non-zero value, the
24383 minimum is 5 and the maximum is 1000.
24384 <P>
24385 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24386 <P>
24387 <UL>
24388 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24389 </UL><P>
24390 <End of help on this topic>
24391 </BODY>
24392 </HTML>
24393 ====== h_config_tcp_query_timeo =====
24394 <HTML>
24395 <HEAD>
24396 <TITLE>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></TITLE>
24397 </HEAD>
24398 <BODY>
24399 <H1>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></H1>
24401 When Alpine times out a network read or write it will normally just display
24402 a message saying "Still waiting".
24403 However, if enough time has elapsed since it started waiting it will offer
24404 to let you break the connection.
24405 That amount of time is set by this option, which defaults to 60 seconds,
24406 has a minimum of 5 seconds, and a maximum of 1000 seconds.
24407 <P>
24408 <UL>
24409 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24410 </UL><P>
24411 <End of help on this topic>
24412 </BODY>
24413 </HTML>
24414 ====== h_config_incoming_folders =====
24415 <HTML>
24416 <HEAD>
24417 <TITLE>OPTION: <!--#echo var="VAR_incoming-folders"--></TITLE>
24418 </HEAD>
24419 <BODY>
24420 <H1>OPTION: <!--#echo var="VAR_incoming-folders"--></H1>
24422 This is a list of one or more folders other than <EM>INBOX</EM> that
24423 may receive new messages.
24424 It is related to the
24425 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
24426 feature.
24427 This variable is normally manipulated with the Add, Delete, and Rename
24428 commands in the FOLDER LIST for the Incoming Message Folders collection.
24429 <P>
24430 <UL>
24431 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24432 </UL><P>
24433 <End of help on this topic>
24434 </BODY>
24435 </HTML>
24436 ====== h_config_folder_spec =====
24437 <HTML>
24438 <HEAD>
24439 <TITLE>OPTION: <!--#echo var="VAR_folder-collections"--></TITLE>
24440 </HEAD>
24441 <BODY>
24442 <H1>OPTION: <!--#echo var="VAR_folder-collections"--></H1>
24444 This is a list of one or more collections where saved mail is stored.
24445 The first collection in this list is the default
24446 collection for <EM>Save</EM>s,
24447 including <A HREF="h_config_default_fcc"><!--#echo var="VAR_default-fcc"--></A>.
24448 <P>
24449 This variable is normally manipulated using the Setup/collectionList screen.
24450 <P>
24451 <UL>
24452 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24453 </UL><P>
24454 <End of help on this topic>
24455 </BODY>
24456 </HTML>
24457 ====== h_config_news_spec =====
24458 <HTML>
24459 <HEAD>
24460 <TITLE>OPTION: <!--#echo var="VAR_news-collections"--></TITLE>
24461 </HEAD>
24462 <BODY>
24463 <H1>OPTION: <!--#echo var="VAR_news-collections"--></H1>
24465 This is a list of collections where news folders are located.
24466 <P>
24467 This variable is normally manipulated using the Setup/collectionList screen.
24468 <P>
24469 <UL>
24470 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24471 </UL><P>
24472 <End of help on this topic>
24473 </BODY>
24474 </HTML>
24475 ====== h_config_address_book =====
24476 <HTML>
24477 <HEAD>
24478 <TITLE>OPTION: <!--#echo var="VAR_address-book"--></TITLE>
24479 </HEAD>
24480 <BODY>
24481 <H1>OPTION: <!--#echo var="VAR_address-book"--></H1>
24483 A list of personal address books.
24484 Each entry in the list is an
24485 optional nickname followed by a pathname or file name relative to the home
24486 directory.
24487 The nickname is separated from the rest of the line with whitespace.
24488 Instead of a local pathname or file name, a remote folder name can be given.
24489 This causes the address book to
24490 be a Remote address book.
24491 <P>
24492 Use the Setup/AddressBook screen to modify this variable.
24493 <P>
24494 <UL>
24495 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24496 </UL><P>
24497 <End of help on this topic>
24498 </BODY>
24499 </HTML>
24500 ====== h_config_glob_addrbook =====
24501 <HTML>
24502 <HEAD>
24503 <TITLE>OPTION: <!--#echo var="VAR_global-address-book"--></TITLE>
24504 </HEAD>
24505 <BODY>
24506 <H1>OPTION: <!--#echo var="VAR_global-address-book"--></H1>
24508 A list of shared address books. Each entry in the list is an
24509 optional nickname followed by a pathname or file name relative to the home
24510 directory.
24511 A SPACE character separates the nickname from the rest of the line.
24512 Instead of a local pathname or file name, a remote folder name can be given.
24513 This causes the address book to
24514 be a Remote address book.
24515 Global address books are
24516 defined to be ReadOnly.
24517 <P>
24518 Use the Setup/AddressBook screen to modify this variable.
24519 <P>
24520 <UL>
24521 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24522 </UL><P>
24523 <End of help on this topic>
24524 </BODY>
24525 </HTML>
24526 ====== h_config_last_vers =====
24527 <HTML>
24528 <HEAD>
24529 <TITLE>OPTION: <!--#echo var="VAR_last-version-used"--></TITLE>
24530 </HEAD>
24531 <BODY>
24532 <H1>OPTION: <!--#echo var="VAR_last-version-used"--></H1>
24534 This is set automatically by Alpine.
24535 It is used to keep track of the last version of Alpine that
24536 was run by the user.
24537 Whenever the version number increases, a new version message is printed out.
24538 This may not be set in the system-wide configuration files.
24539 <P>
24540 <UL>
24541 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24542 </UL><P>
24543 <End of help on this topic>
24544 </BODY>
24545 </HTML>
24546 ====== h_config_printer =====
24547 <HTML>
24548 <HEAD>
24549 <TITLE>OPTION: Printer</TITLE>
24550 </HEAD>
24551 <BODY>
24552 <H1>OPTION: Printer</H1>
24554 Your default printer selection.
24555 <P>
24556 Use the Setup/Printer screen to modify this variable.
24557 <P>
24558 <UL>
24559 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24560 </UL><P>
24561 <End of help on this topic>
24562 </BODY>
24563 </HTML>
24564 ====== h_config_print_cat =====
24565 <HTML>
24566 <HEAD>
24567 <TITLE>OPTION: <!--#echo var="VAR_personal-print-category"--></TITLE>
24568 </HEAD>
24569 <BODY>
24570 <H1>OPTION: <!--#echo var="VAR_personal-print-category"--></H1>
24572 This is an internal Alpine variable.
24573 It will be equal to 1, 2, or 3 depending on whether the default printer is
24574 attached, standard, or a personal print command.
24575 <P>
24576 Use the Setup/Printer screen to modify this variable.
24577 <P>
24578 <UL>
24579 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24580 </UL><P>
24581 <End of help on this topic>
24582 </BODY>
24583 </HTML>
24584 ====== h_config_print_command =====
24585 <HTML>
24586 <HEAD>
24587 <TITLE>OPTION: <!--#echo var="VAR_personal-print-command"--></TITLE>
24588 </HEAD>
24589 <BODY>
24590 <H1>OPTION: <!--#echo var="VAR_personal-print-command"--></H1>
24592 List of personal print commands.
24593 <P>
24594 Use the Setup/Printer screen to modify this variable.
24595 <P>
24596 <UL>
24597 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24598 </UL><P>
24599 <End of help on this topic>
24600 </BODY>
24601 </HTML>
24602 ====== h_config_pat_old =====
24603 <HTML>
24604 <HEAD>
24605 <TITLE>OPTION: Patterns</TITLE>
24606 </HEAD>
24607 <BODY>
24608 <H1>OPTION: Patterns</H1>
24610 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by the
24611 options Patterns-Roles, Patterns-Filters, Patterns-Scores, Patterns-Indexcolors,
24612 and Patterns-Other.
24613 Patterns-Scores and Patterns-Filters have been replaced since then by
24614 Patterns-Scores2 and Patterns-Filters2.
24615 <P>
24616 Use the Setup/Rules screens to modify these variable.
24617 <P>
24618 <UL>
24619 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24620 </UL><P>
24621 <End of help on this topic>
24622 </BODY>
24623 </HTML>
24624 ====== h_config_pat_roles =====
24625 <HTML>
24626 <HEAD>
24627 <TITLE>OPTION: <!--#echo var="VAR_patterns-roles"--></TITLE>
24628 </HEAD>
24629 <BODY>
24630 <H1>OPTION: <!--#echo var="VAR_patterns-roles"--></H1>
24632 List of rules used for roles.
24633 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by this and
24634 other options.
24635 <P>
24636 Use the Setup/Rules/Roles screen to modify this variable.
24637 <P>
24638 <UL>
24639 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24640 </UL><P>
24641 <End of help on this topic>
24642 </BODY>
24643 </HTML>
24644 ====== h_config_pat_filts =====
24645 <HTML>
24646 <HEAD>
24647 <TITLE>OPTION: <!--#echo var="VAR_patterns-filters2"--></TITLE>
24648 </HEAD>
24649 <BODY>
24650 <H1>OPTION: <!--#echo var="VAR_patterns-filters2"--></H1>
24652 List of rules used for filters.
24653 <P>
24654 Use the Setup/Rules/Filters screen to modify this variable.
24655 <P>
24656 <UL>
24657 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24658 </UL><P>
24659 <End of help on this topic>
24660 </BODY>
24661 </HTML>
24662 ====== h_config_pat_scores =====
24663 <HTML>
24664 <HEAD>
24665 <TITLE>OPTION: <!--#echo var="VAR_patterns-scores2"--></TITLE>
24666 </HEAD>
24667 <BODY>
24668 <H1>OPTION: <!--#echo var="VAR_patterns-scores2"--></H1>
24670 List of rules used for scoring.
24671 <P>
24672 Use the Setup/Rules/SetScores screen to modify this variable.
24673 <P>
24674 <UL>
24675 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24676 </UL><P>
24677 <End of help on this topic>
24678 </BODY>
24679 </HTML>
24680 ====== h_config_pat_other =====
24681 <HTML>
24682 <HEAD>
24683 <TITLE>OPTION: <!--#echo var="VAR_patterns-other"--></TITLE>
24684 </HEAD>
24685 <BODY>
24686 <H1>OPTION: <!--#echo var="VAR_patterns-other"--></H1>
24688 List of rules used for miscellaneous configuration.
24689 <P>
24690 Use the Setup/Rules/Other screen to modify this variable.
24691 <P>
24692 <UL>
24693 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24694 </UL><P>
24695 <End of help on this topic>
24696 </BODY>
24697 </HTML>
24698 ====== h_config_pat_incols =====
24699 <HTML>
24700 <HEAD>
24701 <TITLE>OPTION: patterns-indexcolors</TITLE>
24702 </HEAD>
24703 <BODY>
24704 <H1>OPTION: patterns-indexcolors</H1>
24706 List of rules used for coloring lines in the index.
24707 <P>
24708 Use the Setup/Rules/Indexcolor screen to modify this variable.
24709 <P>
24710 <UL>
24711 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24712 </UL><P>
24713 <End of help on this topic>
24714 </BODY>
24715 </HTML>
24716 ====== h_config_pat_srch =====
24717 <HTML>
24718 <HEAD>
24719 <TITLE>OPTION: patterns-search</TITLE>
24720 </HEAD>
24721 <BODY>
24722 <H1>OPTION: patterns-search</H1>
24724 List of rules used only for searching with the Select command in the MESSAGE INDEX.
24725 <P>
24726 Use the Setup/Rules/searCh screen to modify this variable.
24727 <P>
24728 <UL>
24729 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24730 </UL><P>
24731 <End of help on this topic>
24732 </BODY>
24733 </HTML>
24734 ====== h_config_font_name =====
24735 <HTML>
24736 <HEAD>
24737 <TITLE>OPTION: Font Name</TITLE>
24738 </HEAD>
24739 <BODY>
24740 <H1>OPTION: Font Name</H1>
24742 PC-Alpine only.
24743 <P>
24744 Name of normal font.
24745 <P>
24746 Use the pulldown Config menu to modify this variable.
24747 <P>
24748 <UL>
24749 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24750 </UL><P>
24751 <End of help on this topic>
24752 </BODY>
24753 </HTML>
24754 ====== h_config_font_size =====
24755 <HTML>
24756 <HEAD>
24757 <TITLE>OPTION: Font Size</TITLE>
24758 </HEAD>
24759 <BODY>
24760 <H1>OPTION: Font Size</H1>
24762 PC-Alpine only.
24763 <P>
24764 Size of normal font.
24765 <P>
24766 Use the pulldown Config menu to modify this variable.
24767 <P>
24768 <UL>
24769 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24770 </UL><P>
24771 <End of help on this topic>
24772 </BODY>
24773 </HTML>
24774 ====== h_config_font_style =====
24775 <HTML>
24776 <HEAD>
24777 <TITLE>OPTION: Font Style</TITLE>
24778 </HEAD>
24779 <BODY>
24780 <H1>OPTION: Font Style</H1>
24782 PC-Alpine only.
24783 <P>
24784 Style of normal font.
24785 <P>
24786 Use the pulldown Config menu to modify this variable.
24787 <P>
24788 <UL>
24789 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24790 </UL><P>
24791 <End of help on this topic>
24792 </BODY>
24793 </HTML>
24794 ====== h_config_font_char_set =====
24795 <HTML>
24796 <HEAD>
24797 <TITLE>OPTION: Font Character Set</TITLE>
24798 </HEAD>
24799 <BODY>
24800 <H1>OPTION: Font Character Set</H1>
24802 PC-Alpine only.
24803 <P>
24804 Character set of normal font.
24805 <P>
24806 Use the pulldown Config menu to modify this variable.
24807 <P>
24808 <UL>
24809 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24810 </UL><P>
24811 <End of help on this topic>
24812 </BODY>
24813 </HTML>
24814 ====== h_config_print_font_name =====
24815 <HTML>
24816 <HEAD>
24817 <TITLE>OPTION: Print-Font-Name</TITLE>
24818 </HEAD>
24819 <BODY>
24820 <H1>OPTION: Print-Font-Name</H1>
24822 PC-Alpine only.
24823 <P>
24824 Name of printer font.
24825 <P>
24826 Use the pulldown Config menu to modify this variable.
24827 <P>
24828 <UL>
24829 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24830 </UL><P>
24831 <End of help on this topic>
24832 </BODY>
24833 </HTML>
24834 ====== h_config_print_font_size =====
24835 <HTML>
24836 <HEAD>
24837 <TITLE>OPTION: Print-Font-Size</TITLE>
24838 </HEAD>
24839 <BODY>
24840 <H1>OPTION: Print-Font-Size</H1>
24842 PC-Alpine only.
24843 <P>
24844 Size of printer font.
24845 <P>
24846 Use the pulldown Config menu to modify this variable.
24847 <P>
24848 <UL>
24849 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24850 </UL><P>
24851 <End of help on this topic>
24852 </BODY>
24853 </HTML>
24854 ====== h_config_print_font_style =====
24855 <HTML>
24856 <HEAD>
24857 <TITLE>OPTION: Print-Font-Style</TITLE>
24858 </HEAD>
24859 <BODY>
24860 <H1>OPTION: Print-Font-Style</H1>
24862 PC-Alpine only.
24863 <P>
24864 Style of printer font.
24865 <P>
24866 Use the pulldown Config menu to modify this variable.
24867 <P>
24868 <UL>
24869 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24870 </UL><P>
24871 <End of help on this topic>
24872 </BODY>
24873 </HTML>
24874 ====== h_config_print_font_char_set =====
24875 <HTML>
24876 <HEAD>
24877 <TITLE>OPTION: Print-Font-Char-Set</TITLE>
24878 </HEAD>
24879 <BODY>
24880 <H1>OPTION: Print-Font-Char-Set</H1>
24882 PC-Alpine only.
24883 <P>
24884 Character set of printer font.
24885 <P>
24886 Use the pulldown Config menu to modify this variable.
24887 <P>
24888 <UL>
24889 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24890 </UL><P>
24891 <End of help on this topic>
24892 </BODY>
24893 </HTML>
24894 ====== h_config_window_position =====
24895 <HTML>
24896 <HEAD>
24897 <TITLE>OPTION: Window-Position</TITLE>
24898 </HEAD>
24899 <BODY>
24900 <H1>OPTION: Window-Position</H1>
24902 PC-Alpine only.
24903 <P>
24904 Position on the screen of the Alpine window.
24905 <P>
24906 Alpine normally maintains this variable itself, and it is set automatically.
24907 This variable is provided to those who wish to use the same window position
24908 across different machines from the same configuration.
24909 <A HREF="h_config_winpos_in_config"><!--#echo var="FEAT_store-window-position-in-config"--></A>
24910 must also be set for this setting to be used.
24911 <P>
24912 The format for this variable is of the form: <CODE>CxR+X+Y</CODE>, where
24913 C is the number of columns, R is the number of rows, and X and Y specify the
24914 top left corner of the window.
24915 <P>
24916 <UL>
24917 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24918 </UL><P>
24919 <End of help on this topic>
24920 </BODY>
24921 </HTML>
24922 ====== h_config_cursor_style =====
24923 <HTML>
24924 <HEAD>
24925 <TITLE>OPTION: Cursor Style</TITLE>
24926 </HEAD>
24927 <BODY>
24928 <H1>OPTION: Cursor Style</H1>
24930 PC-Alpine only.
24931 <P>
24932 Cursor style.
24933 <P>
24934 Use the pulldown Config menu to modify this variable.
24935 <P>
24936 <UL>
24937 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24938 </UL><P>
24939 <End of help on this topic>
24940 </BODY>
24941 </HTML>
24942 ====== h_config_ldap_servers =====
24943 <HTML>
24944 <HEAD>
24945 <TITLE>OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
24946 </HEAD>
24947 <BODY>
24948 <H1>OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
24950 List of LDAP servers and associated data.
24951 <P>
24952 Use the Setup/Directory screen to modify this variable.
24953 <P>
24954 <UL>
24955 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24956 </UL><P>
24957 <End of help on this topic>
24958 </BODY>
24959 </HTML>
24960 ====== h_config_sendmail_path =====
24961 <HTML>
24962 <HEAD>
24963 <TITLE>OPTION: <!--#echo var="VAR_sendmail-path"--></TITLE>
24964 </HEAD>
24965 <BODY>
24966 <H1>OPTION: <!--#echo var="VAR_sendmail-path"--></H1>
24968 This names the path to an
24969 alternative program, and any necessary arguments, to be used in posting
24970 mail messages. See the Technical notes for more information.
24971 <P>
24972 <UL>
24973 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24974 </UL><P>
24975 <End of help on this topic>
24976 </BODY>
24977 </HTML>
24978 ====== h_config_oper_dir =====
24979 <HTML>
24980 <HEAD>
24981 <TITLE>OPTION: <!--#echo var="VAR_operating-dir"--></TITLE>
24982 </HEAD>
24983 <BODY>
24984 <H1>OPTION: <!--#echo var="VAR_operating-dir"--></H1>
24986 This names the root of the
24987 tree to which you are restricted when reading and writing folders and
24988 files. It is usually used in the system-wide,
24989 <EM>fixed</EM> configuration file.
24990 <P>
24991 <UL>
24992 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24993 </UL><P>
24994 <End of help on this topic>
24995 </BODY>
24996 </HTML>
24997 ====== h_config_rshpath =====
24998 <HTML>
24999 <HEAD>
25000 <TITLE>OPTION: <!--#echo var="VAR_rsh-path"--></TITLE>
25001 </HEAD>
25002 <BODY>
25003 <H1>OPTION: <!--#echo var="VAR_rsh-path"--></H1>
25005 Sets the name of the command used to open a UNIX remote shell
25006 connection. The default is typically <CODE>/usr/ucb/rsh</CODE>.
25007 <P>
25008 <UL>
25009 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25010 </UL><P>
25011 <End of help on this topic>
25012 </BODY>
25013 </HTML>
25014 ====== h_config_rshcmd =====
25015 <HTML>
25016 <HEAD>
25017 <TITLE>OPTION: <!--#echo var="VAR_rsh-command"--></TITLE>
25018 </HEAD>
25019 <BODY>
25020 <H1>OPTION: <!--#echo var="VAR_rsh-command"--></H1>
25022 Sets the format of the command used to
25023 open a UNIX remote shell connection. The default is
25024 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
25025 provided command. The first is for the command's pathname, the second is
25026 for the host to connnect to, the third is for the user to connect as, and
25027 the fourth is for the connection method (typically <CODE>imap</CODE>).
25028 <P>
25029 <UL>
25030 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25031 </UL><P>
25032 <End of help on this topic>
25033 </BODY>
25034 </HTML>
25035 ====== h_config_sshpath =====
25036 <HTML>
25037 <HEAD>
25038 <TITLE>OPTION: <!--#echo var="VAR_ssh-path"--></TITLE>
25039 </HEAD>
25040 <BODY>
25041 <H1>OPTION: <!--#echo var="VAR_ssh-path"--></H1>
25043 Sets the name of the command used to open a UNIX secure shell
25044 connection. The default is typically <CODE>/usr/bin/ssh</CODE>.
25045 <P>
25046 <UL>
25047 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25048 </UL><P>
25049 <End of help on this topic>
25050 </BODY>
25051 </HTML>
25052 ====== h_config_sshcmd =====
25053 <HTML>
25054 <HEAD>
25055 <TITLE>OPTION: <!--#echo var="VAR_ssh-command"--></TITLE>
25056 </HEAD>
25057 <BODY>
25058 <H1>OPTION: <!--#echo var="VAR_ssh-command"--></H1>
25060 Sets the format of the command used to
25061 open a UNIX secure shell connection. The default is
25062 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
25063 provided command. The first is for the command's pathname, the second is
25064 for the host to connnect to, the third is for the user to connect as, and
25065 the fourth is for the connection method (typically <CODE>imap</CODE>).
25066 <P>
25067 <UL>
25068 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25069 </UL><P>
25070 <End of help on this topic>
25071 </BODY>
25072 </HTML>
25073 ====== h_config_new_ver_quell =====
25074 <HTML>
25075 <HEAD>
25076 <TITLE>OPTION: <!--#echo var="VAR_new-version-threshold"--></TITLE>
25077 </HEAD>
25078 <BODY>
25079 <H1>OPTION: <!--#echo var="VAR_new-version-threshold"--></H1>
25081 When a new version of Alpine is run for the first time it offers a
25082 special explanatory screen to the user upon startup. This option
25083 helps control when and if that special screen appears for users that
25084 have previously run Alpine. It takes as its value an Alpine version
25085 number. Alpine versions less than the specified value will supress this
25086 special screen while versions equal to or greater than that specified
25087 will behave normally.
25088 <P>
25089 <UL>
25090 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25091 </UL><P>
25092 <End of help on this topic>
25093 </BODY>
25094 </HTML>
25095 ====== h_config_disable_drivers =====
25096 <HTML>
25097 <HEAD>
25098 <TITLE>OPTION: <!--#echo var="VAR_disable-these-drivers"--></TITLE>
25099 </HEAD>
25100 <BODY>
25101 <H1>OPTION: <!--#echo var="VAR_disable-these-drivers"--></H1>
25103 This variable is a list of mail drivers that will be disabled.
25104 The candidates for disabling are listed below.
25105 There may be more in the future if you compile Alpine with
25106 a newer version of the c-client library.
25107 <P>
25109 <UL>
25110 <LI> mbox
25111 <LI> mbx
25112 <LI> mh
25113 <LI> mmdf
25114 <LI> mtx
25115 <LI> mx
25116 <LI> news
25117 <LI> phile
25118 <LI> tenex
25119 <LI> unix
25120 </UL>
25121 <P>
25123 The <EM>mbox</EM> driver enables the following behavior: if there is a
25124 file called <CODE>mbox</CODE>
25125 in your home directory, and if that file is either empty or in Unix mailbox
25126 format, then every time you open <EM>INBOX</EM> the <EM>mbox</EM> driver
25127 will automatically transfer mail from the system mail spool directory into the
25128 <CODE>mbox</CODE> file and
25129 delete it from the spool directory. If you disable the <EM>mbox</EM> driver,
25130 this will not happen.
25131 <P>
25133 It is not recommended to disable the driver that supports the system default
25134 mailbox format. On most non-SCO systems, that driver is the
25135 <EM>unix</EM> driver.
25136 On most SCO systems, it is the <EM>mmdf</EM> driver.
25137 The system default driver may be
25138 configured to something else on your system; check with your system manager
25139 for additional information.
25140 <P>
25142 It is most likely not very useful for you to disable any of the drivers other
25143 than possibly <EM>mbox</EM>.
25144 You could disable some of the others if you know for
25145 certain that you don't need them but the performance gain in doing so
25146 is very modest.
25147 <P>
25148 <UL>
25149 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25150 </UL><P>
25151 <End of help on this topic>
25152 </BODY>
25153 </HTML>
25154 ====== h_config_disable_auths =====
25155 <HTML>
25156 <HEAD>
25157 <TITLE>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></TITLE>
25158 </HEAD>
25159 <BODY>
25160 <H1>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></H1>
25162 This variable is a list of SASL (Simple Authentication and Security
25163 Layer) authenticators that will be disabled.
25164 SASL is a mechanism for
25165 authenticating to IMAP, POP3, SMTP, and other network servers.
25166 <P>
25168 Alpine matches its list of supported authenticators with the server to
25169 determine the most secure authenticator that is supported by both.
25170 If no matching authenticators are found, Alpine will revert to plaintext
25171 login (or, in the case of SMTP, will be unable to authenticate at all).
25172 <P>
25173 The candidates for disabling can be found <A HREF="X-Alpine-Config:">here</A>.
25174 <P>
25176 Normally, you will not disable any authenticators.
25177 There are two exceptions:
25178 <P>
25179 <OL>
25180 <LI> You use a broken server that advertises an authenticator,
25181 but does not actually implement it.
25182 <LI> You have a Kerberos-capable version of Alpine and the server is
25183 also Kerberos-capable, but you can not obtain Kerberos
25184 credentials on the server machine, thus you desire to disable
25185 GSSAPI (which in turn disables Alpine's Kerberos support).
25186 </OL>
25187 <P>
25188 It is never necessary to disable authenticators, since Alpine will try
25189 other authenticators before giving up.
25190 However, disabling the relevant authenticator avoids annoying error messages.
25191 <P>
25192 <UL>
25193 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25194 </UL><P>
25195 <End of help on this topic>
25196 </BODY>
25197 </HTML>
25198 ====== h_config_abook_metafile =====
25199 <HTML>
25200 <HEAD>
25201 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></TITLE>
25202 </HEAD>
25203 <BODY>
25204 <H1>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></H1>
25206 This is usually set by Alpine and is the name of a file
25207 that contains data about
25208 remote address books and remote configuration files.
25209 <P>
25210 <UL>
25211 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25212 </UL><P>
25213 <End of help on this topic>
25214 </BODY>
25215 </HTML>
25216 ====== h_config_composer_wrap_column =====
25217 <HTML>
25218 <HEAD>
25219 <TITLE>OPTION: <!--#echo var="VAR_composer-wrap-column"--></TITLE>
25220 </HEAD>
25221 <BODY>
25222 <H1>OPTION: <!--#echo var="VAR_composer-wrap-column"--></H1>
25225 This option specifies an aspect of Alpine's Composer. This gives the
25226 maximum width that auto-wrapped lines will have. It's also the maximum
25227 width of lines justified using the <A HREF="h_compose_justify">^J
25228 Justify</A> command. The normal default
25229 is "74". The largest allowed setting is normally "80"
25230 in order to
25231 prevent very long lines from being sent in outgoing mail. When the mail
25232 is actually sent, trailing spaces will be stripped off of each line.
25234 <P>
25235 <UL>
25236 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25237 </UL><P>
25238 <End of help on this topic>
25239 </BODY>
25240 </HTML>
25241 ====== h_config_deadlets =====
25242 <HTML>
25243 <HEAD>
25244 <TITLE>OPTION: <!--#echo var="VAR_dead-letter-files"--></TITLE>
25245 </HEAD>
25246 <BODY>
25247 <H1>OPTION: <!--#echo var="VAR_dead-letter-files"--></H1>
25250 This option affects Alpine's behavior when you cancel a message being
25251 composed. Alpine's usual behavior is to write the canceled message to
25252 a file named
25253 <!--chtml if pinemode="os_windows"-->
25254 "DEADLETR",
25255 <!--chtml else-->
25256 "dead.letter" in your home directory,
25257 <!--chtml endif-->
25258 overwriting any previous message.
25259 <P>
25260 If you set this option to a value higher than one, then that many copies
25261 of dead letter files will be saved.
25262 For example, if you set this option to "3" then you may have
25263 files named
25264 <!--chtml if pinemode="os_windows"-->
25265 "DEADLETR",
25266 "DEADLETR2", and
25267 "DEADLETR3".
25268 <!--chtml else-->
25269 "dead.letter",
25270 "dead.letter2", and
25271 "dead.letter3" in your home directory.
25272 <!--chtml endif-->
25273 In this example, the most recently cancelled message will be in
25274 <!--chtml if pinemode="os_windows"-->
25275 "DEADLETR",
25276 <!--chtml else-->
25277 "dead.letter",
25278 <!--chtml endif-->
25279 and the third most recently cancelled message will be in
25280 <!--chtml if pinemode="os_windows"-->
25281 "DEADLETR3".
25282 <!--chtml else-->
25283 "dead.letter3".
25284 <!--chtml endif-->
25285 The fourth most recently cancelled message will no longer be saved.
25287 <P>
25288 If you set this option to zero, then NO record of canceled messages is
25289 maintained.
25290 <P>
25291 If the feature
25292 <A HREF="h_config_quell_dead_letter"><!--#echo var="FEAT_quell-dead-letter-on-cancel"--></A>
25293 is set, that overrides whatever you set for this option.
25294 If this option had existed at the time, then the Quell feature would not
25295 have been added, but it is still there for backwards compatibility.
25296 So, in order for this option to have the desired effect, make sure the
25297 Quell feature is turned off.
25299 <P>
25300 <UL>
25301 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25302 </UL><P>
25303 <End of help on this topic>
25304 </BODY>
25305 </HTML>
25306 ====== h_config_maxremstream =====
25307 <HTML>
25308 <HEAD>
25309 <TITLE>OPTION: <!--#echo var="VAR_max-remote-connections"--></TITLE>
25310 </HEAD>
25311 <BODY>
25312 <H1>OPTION: <!--#echo var="VAR_max-remote-connections"--></H1>
25314 This option affects low-level behavior of Alpine.
25315 The default value for this option is <EM>3</EM>.
25316 If your INBOX is accessed using the IMAP protocol
25317 from an IMAP server, that connection is kept open throughout the
25318 duration of your Alpine session, independent of the value of this option.
25319 The same is true of any
25320 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
25321 you have defined.
25322 This option controls Alpine's behavior when connecting to remote IMAP folders
25323 other than your INBOX or your <!--#echo var="VAR_stay-open-folders"-->.
25324 It specifies the maximum number of remote IMAP connections (other than
25325 those mentioned above) that Alpine will use for accessing the rest of your
25326 folders.
25327 If you set this option to zero, you will turn off most remote connection
25328 re-use.
25329 It's difficult to understand exactly what this option does, and it is usually
25330 fine to leave it set to its default value.
25331 It is probably more likely that you will be interested in setting the
25332 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A> option
25333 instead of changing the value of this option.
25334 A slightly longer explanation of what is going on with this option
25335 is given in the next paragraphs.
25337 <P>
25338 There are some time costs involved in opening and closing remote IMAP
25339 folders, the main costs being the time you have to wait for the connection
25340 to the server and the time for the folder to open.
25341 Opening a folder may involve not only the time the server takes to do its
25342 processing but time that Alpine uses to do filtering.
25343 These times can vary widely.
25344 They depend on how loaded the server is, how large
25345 the folder being opened is, and how you set up filtering, among other things.
25346 Once Alpine has opened a connection to a particular folder, it will attempt
25347 to keep that connection open in case you use it again.
25348 In order to do this,
25349 Alpine will attempt to use the <!--#echo var="VAR_max-remote-connections"--> (the value of
25350 this option) IMAP connections you have alloted for this purpose.
25351 <P>
25352 For example, suppose the value of this option is set to "2".
25353 If your INBOX is accessed on a remote server using the IMAP protocol, that
25354 doesn't count as one of the remote connections but it is always kept open.
25355 If you then open another IMAP folder, that would be your first
25356 remote connection counted as one of the <!--#echo var="VAR_max-remote-connections"--> connections.
25357 If you open a third folder the second will be left open, in case you
25358 return to it.
25359 You won't be able to tell it has been left open.
25360 It will appear to be closed when you leave the folder but the connection
25361 will remain in the background.
25362 Now suppose you go back to the second folder (the first folder after the
25363 INBOX).
25364 A connection to that folder is still open so you won't have to wait
25365 for the startup time to open it.
25366 Meanwhile, the connection to the third folder will be left behind.
25367 Now, if you open a fourth folder, you will bump into the
25368 <!--#echo var="VAR_max-remote-connections"--> limit, because this will be the third folder other
25369 than INBOX and you have the option set to "2".
25370 The connection that is being used for
25371 the third folder will be re-used for this new fourth folder.
25372 If you go back to the third folder after this, it is no longer already
25373 connected when you get there.
25374 You'll still save some time since Alpine will re-use the connection to the
25375 fourth folder and you have already logged in on that connection,
25376 but the folder will have to be re-opened from scratch.
25377 <P>
25378 If a folder is large and the startup cost is dominated by the time it takes
25379 to open that folder or to run filters on it, then it will pay to make the
25380 value of this option large enough to keep it open.
25381 On the other hand, if you only revisit a handful of folders or if
25382 the folders are small, then it might
25383 make more sense to keep this number small so that the reconnect
25384 time (the time to start up a new connection and authenticate)
25385 is eliminated instead.
25386 <P>
25387 You may also need to consider the impact on the server.
25388 On the surface, a larger number here may cause a larger impact on the
25389 server, since you will have more connections open to the server.
25390 On the other hand, not only will <EM>you</EM> be avoiding the startup costs
25391 associated with reopening a folder, but the <EM>server</EM> will be
25392 avoiding those costs as well.
25393 <P>
25394 When twenty five minutes pass without any active use of an IMAP connection
25395 being saved for possible re-use, that connection will be shut down,
25397 <P>
25398 <UL>
25399 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25400 </UL><P>
25401 <End of help on this topic>
25402 </BODY>
25403 </HTML>
25404 ====== h_config_permlocked =====
25405 <HTML>
25406 <HEAD>
25407 <TITLE>OPTION: <!--#echo var="VAR_stay-open-folders"--></TITLE>
25408 </HEAD>
25409 <BODY>
25410 <H1>OPTION: <!--#echo var="VAR_stay-open-folders"--></H1>
25412 This option affects low-level behavior of Alpine.
25413 There is no default value for this option.
25414 It is related to the options
25415 <A HREF="h_config_preopen_stayopens">"<!--#echo var="FEAT_preopen-stayopen-folders"-->"</A>,
25416 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>,
25417 and <A HREF="h_config_expunge_stayopens">"<!--#echo var="FEAT_offer-expunge-of-stayopen-folders"-->"</A>.
25419 <P>
25420 Note: changes made to this list take effect the next time you open a
25421 folder in the list.
25423 <P>
25424 This is a list of folders that will be permanently kept open once they
25425 are first opened.
25426 The names in this list may be either the nickname of an Incoming folder
25427 or the full technical specification of a folder.
25428 The folders in this list need not be remote IMAP folders, they could usefully
25429 be local folders, as well.
25430 If a folder in the list is a newsgroup or is not accessed either locally
25431 or via IMAP, then the entry will be ignored.
25432 For example, folders accessed via NNTP or POP3 will not be kept open, since
25433 the way that new mail is found with those protocols involves closing and
25434 reopening the connection.
25435 <P>
25436 Once a Stay Open folder has been opened, new-mail checking will continue
25437 to happen on that folder for the rest of the Alpine session.
25438 Your INBOX is always implicitly included in this Stay-Open list and doesn't
25439 need to be added explicitly.
25440 <P>
25441 Another difference that you may notice between a Stay Open folder and a
25442 non-Stay Open folder is which message is selected as the current message
25443 when you enter the folder index.
25444 Normally, the starting position for an incoming folder (which most Stay Open
25445 folders will likely be) is controlled by the
25446 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
25447 However, if a folder is a Stay Open folder, when you re-enter the folder
25448 after the first time the current message will be the same as it was when
25449 you left the folder.
25450 An exception is made if you use the TAB command to get to the folder.
25451 In that case, the message number will be incremented by one from what it
25452 was when you left the folder.
25453 <P>
25454 The above special behavior is thought to be useful.
25455 However, it is special and different from what you might at first expect.
25456 The feature
25457 <A HREF="h_config_use_reg_start_for_stayopen"><!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></A>
25458 may be used to turn off this special treatment.
25459 <P>
25460 If the message that was current when you left the folder no longer exists,
25461 then the regular startup rule will be used instead.
25463 <P>
25464 <UL>
25465 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25466 </UL><P>
25467 <End of help on this topic>
25468 </BODY>
25469 </HTML>
25470 ====== h_config_viewer_overlap =====
25471 <html>
25472 <header>
25473 <title>OPTION: <!--#echo var="VAR_viewer-overlap"--></title>
25474 </header>
25475 <body>
25476 <h1>OPTION: <!--#echo var="VAR_viewer-overlap"--></h1>
25478 This option specifies an aspect of Alpine's Message Viewing screen. When
25479 the space bar is used to page forward in a message, the number of lines
25480 specified by the "<!--#echo var="VAR_viewer-overlap"-->" variable will be repeated from the
25481 bottom of the screen. That is, if this was set to two lines, then the
25482 bottom two lines of the screen would be repeated on the top of the next
25483 screen. The normal default value is "2".<p>
25484 <UL>
25485 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25486 </UL><P>
25487 <End of help on this topic>
25488 </body>
25489 </html>
25490 ====== h_config_scroll_margin =====
25491 <HTML>
25492 <HEAD>
25493 <TITLE>OPTION: <!--#echo var="VAR_scroll-margin"--></TITLE>
25494 </HEAD>
25495 <BODY>
25496 <H1>OPTION: <!--#echo var="VAR_scroll-margin"--></H1>
25498 This option controls when Alpine's line-by-line scrolling occurs.
25499 Typically, when a selected item is at the top or bottom screen edge
25500 and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are struck, the
25501 displayed items are scrolled down or up by a single line.
25503 <P>
25504 This option allows you to tell Alpine the number of lines from the top and
25505 bottom screen edge that line-by-line paging should occcur. For example,
25506 setting this value to one (1) will cause Alpine to scroll the display
25507 vertically when you move to select an item on the display's top or
25508 bottom edge.
25510 <P>
25511 By default, this variable is zero, indicating that scrolling happens
25512 when you move up or down to select an item immediately off the display's
25513 top or bottom edge.
25515 <P>
25516 <UL>
25517 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25518 </UL><P>
25519 <End of help on this topic>
25520 </BODY>
25521 </HTML>
25522 ====== h_config_wordseps =====
25523 <HTML>
25524 <HEAD>
25525 <TITLE>OPTION: <!--#echo var="VAR_composer-word-separators"--></TITLE>
25526 </HEAD>
25527 <BODY>
25528 <H1>OPTION: <!--#echo var="VAR_composer-word-separators"--></H1>
25530 This option affects how a "word" is defined in the composer.
25531 The definition of a word is used when using the Forward Word and Backward
25532 Word commands in the composer, as well as when using the spell checker.
25533 Whitespace is always considered a word separator.
25534 Punctuation (like question marks, periods, commas, and so on) is always
25535 a word separator if it comes at the end of a word.
25536 By default, a punctuation character that is in the middle of a word does
25537 not break up that word as long as the character before and the character
25538 after it are both alphanumeric.
25539 If you add a character to this option it will be considered a
25540 word separator even when it occurs in the middle of an alphanumeric word.
25541 For example, if you want to skip through each part of an address instead
25542 of skipping the whole address at once you might want to include "@"
25543 and "." in this list.
25544 If you want the word-skipper to stop on each part of a UNIX filename you
25545 could add "/" to the list.
25546 The equal sign and dash are other possibilities you might find helpful.
25547 <P>
25548 <UL>
25549 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25550 </UL><P>
25551 <End of help on this topic>
25552 </BODY>
25553 </HTML>
25554 ====== h_config_reply_indent_string =====
25555 <HTML>
25556 <HEAD>
25557 <TITLE>OPTION: <!--#echo var="VAR_reply-indent-string"--></TITLE>
25558 </HEAD>
25559 <BODY>
25560 <H1>OPTION: <!--#echo var="VAR_reply-indent-string"--></H1>
25562 This option specifies an aspect of Alpine's Reply command.
25563 When a message is replied to and the text of the message is included, the
25564 included text usually has the string "> " prepended
25565 to each line indicating it is quoted text.
25566 (In case you haven't seen this before, "string" is a technical term
25567 that means chunk of text.)
25569 <P>
25570 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
25571 in 1999 and its wide-spread adoption since then, you will usually be better off if you
25572 use one of the standard values,
25573 "> " or ">", for this option.
25575 <P>
25576 This option specifies a different value for that string.
25577 If you wish to use a string that begins or ends with a space,
25578 enclose the string in double quotes.
25580 <P>
25581 Besides simple text, the prepended string can be based
25582 on the message being replied to.
25583 The following tokens are substituted for the message's corresponding value:
25585 <DL>
25586 <DT>_FROM_</DT>
25587 <DD>This token gets replaced with the message sender's "username".
25588 If the name is longer than six characters, only the first six characters are
25589 used.
25590 </DD>
25592 <DT>_NICK_</DT>
25593 <DD>This token gets replaced with the nickname of the message sender's
25594 address as found in your addressbook.
25595 If no addressbook entry is found,
25596 Alpine replaces the characters "_NICK_" with nothing.
25597 If the nickname is longer than six characters, only the first six characters are
25598 used.
25599 </DD>
25601 <DT>_INIT_</DT>
25602 <DD>This token gets replaced with the initials of the sender of the message.
25603 </DD>
25605 </DL>
25607 NOTE: When the
25608 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
25609 feature is enabled, you are given the opportunity to edit the string, whether
25610 it is the default or one automatically generated using the above tokens.
25611 <P>
25612 If you change your <!--#echo var="VAR_reply-indent-string"-->
25613 so that it is not equal to the default value of "> ", then
25614 quoted text will not be flowed
25615 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
25616 when you reply.
25617 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
25618 set to the default value.
25619 <P>
25620 <UL>
25621 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25622 </UL><P>
25623 <End of help on this topic>
25624 </BODY>
25625 </HTML>
25626 ====== h_config_quote_replace_string =====
25627 <HTML>
25628 <HEAD>
25629 <TITLE>OPTION: <!--#echo var="VAR_quote-replace-string"--></TITLE>
25630 </HEAD>
25631 <BODY>
25632 <H1>OPTION: <!--#echo var="VAR_quote-replace-string"--></H1>
25634 This option specifies what string to use as a quote when <b>viewing</b> a
25635 message. The standard way of quoting messages when replying is the string
25636 "> " (quote space).
25637 With this variable set, viewing a message will
25638 replace occurrences of
25639 "> " and ">" with the replacement string.
25640 This setting works best when
25641 <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
25642 or the equivalent setting in your correspondents' mail programs
25643 is set to the default
25644 "> ", but it will also work fine with the
25645 <!--#echo var="VAR_reply-indent-string"--> set to ">".
25646 <P>
25647 By default, this setting will only work on messages that are flowed, which is
25648 the default way of sending messages for many mail clients including
25649 Alpine. Enable the feature
25650 <A HREF="h_config_quote_replace_noflow"><!--#echo var="FEAT_quote-replace-nonflowed"--></A>
25651 to also have quote-replacement performed on non-flowed messages.
25652 <P>
25654 Setting this option will replace ">" and
25655 "> " with the new setting. This string may include trailing
25656 spaces. To preserve those spaces enclose the full string in double quotes.
25657 <P>
25658 No padding to separate the text of the message from the quote string is
25659 added. This means that if you do not add trailing spaces to the value of
25660 this variable, text will be displayed right next to the quote string,
25661 which may be undesirable. This can be avoided by adding a new string
25662 separated by a space from your selection of quote string replacement. This
25663 last string will be used for padding. For example, setting this variable to
25664 <br>">" " " has the effect of setting
25665 ">" as the <!--#echo var="VAR_quote-replace-string"-->, with the text padded by
25666 a space from the last quote string to make it more readable.
25667 <P>
25668 One possible setting for this variable could be
25669 " " (four spaces wrapped in quotes), which
25670 would have the effect of indenting each level of quoting four spaces and
25671 removing the ">"'s. Different levels of quoting could be made
25672 more discernible by setting colors for quoted text.
25673 <P>
25674 Replying to or forwarding the viewed message will preserve the original
25675 formatting of the message, so quote-replacement will not be performed on
25676 messages that are being composed.
25677 <P>
25678 <UL>
25679 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25680 </UL><P>
25681 <End of help on this topic>
25682 </BODY>
25683 </HTML>
25684 ====== h_config_empty_hdr_msg =====
25685 <HTML>
25686 <HEAD>
25687 <TITLE>OPTION: <!--#echo var="VAR_empty-header-message"--></TITLE>
25688 </HEAD>
25689 <BODY>
25690 <H1>OPTION: <!--#echo var="VAR_empty-header-message"--></H1>
25692 When sending, if both the To and Cc fields are empty and you
25693 are sending the message to a Bcc,
25694 Alpine will put a special address in the To line. The default value is:
25696 <P>
25697 <CENTER><SAMP>undisclosed-recipients: ;</SAMP></CENTER>
25699 <P>
25700 The reason for this is to avoid embarrassment caused by some Internet
25701 mail transfer software that interprets a "missing"
25702 <SAMP>To:</SAMP> header as an error and replaces it with an
25703 <SAMP>Apparently-to:</SAMP> header that may contain the addresses you
25704 entered on the <SAMP>Bcc:</SAMP> line, defeating the purpose of the
25705 Bcc. You may change the part of this message that comes before the
25706 ": ;" by setting the "<!--#echo var="VAR_empty-header-message"-->"
25707 variable to something else.
25709 <P>
25710 The normal default is "undisclosed-recipients".
25712 <P>
25713 <UL>
25714 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25715 </UL><P>
25716 <End of help on this topic>
25717 </BODY>
25718 </HTML>
25719 ====== h_config_status_msg_delay =====
25720 <HTML>
25721 <HEAD>
25722 <TITLE>OPTION: <!--#echo var="VAR_status-message-delay"--></TITLE>
25723 </HEAD>
25724 <BODY>
25725 <H1>OPTION: <!--#echo var="VAR_status-message-delay"--></H1>
25727 This option has evolved over time, causing the possible values to be
25728 counter-intuitive.
25729 Read carefully before you set this option.
25730 First we explain what the option does, then there is a longer discussion
25731 following that.
25732 <P>
25733 If this is set to zero, the default value, it has <EM>no</EM> effect.
25734 Positive and negative values serve two similar, but different purposes.
25735 <P>
25736 If it is set to a positive number, it causes the cursor to move to the
25737 status line whenever a status message is printed and pause there for this
25738 many seconds.
25739 It will probably only be useful if the
25740 <A HREF="h_config_show_cursor">"<!--#echo var="FEAT_show-cursor"-->"</A> feature is
25741 also turned on.
25742 Setting this option to a positive number can only be used to
25743 <EM>increase</EM> the status message delay.
25744 This may be useful for Braille displays, or other non-traditional displays.
25745 <P>
25746 If it is set to a negative number the interpretation is a bit complicated.
25747 Negative numbers are used to <EM>decrease</EM> the amount of delay Alpine uses to
25748 allow you to read important status messages.
25749 Of course, this may cause you to miss some important messages.
25750 If you see a message flash by but miss what it says you can use the
25751 Journal command from the MAIN MENU to read it.
25752 If you set this option to a negative value, the delay will be
25753 no more than one second less than the absolute value
25754 of the value you set.
25755 So if you set it to -1, the delay will be no more than zero seconds, no
25756 delay at all.
25757 If you set it to -2, the delay will be no more than 1 second.
25758 And so on, -3 is 2 seconds, -4 is 3 seconds, ...
25759 If the delay that Alpine would have used by default is less than this delay,
25760 then the smaller delay set by Alpine will be used.
25761 Setting this option to a negative value can only reduce the amount of
25762 delay, never increase it.
25763 <P>
25764 Here is a more detailed explanation.
25765 Status messages are the messages that show up spontaneously in the
25766 status message line, usually the third line from the bottom of the screen.
25767 By default, Alpine assigns each status message it produces a minimum
25768 display time.
25769 Some status messages have a minimum display time of zero.
25770 You can see an example of such a message by paging up in this help text
25771 until you reach the top of the screen.
25772 If you try to page past the top you will see the message
25773 <P>
25774 <CENTER><SAMP>[Already at start of help text]</SAMP></CENTER>
25775 <P>
25776 in the status line.
25777 If there is another more important use of the status message line this message
25778 might be replaced quickly, or it even might not be shown at all.
25779 However, if there is no reason to get rid of the message, it might stay
25780 there for several seconds while you read the help.
25781 An example where it is replaced immediately happens when you page up in
25782 the help text past the top of the screen, but then type the "WhereIs"
25783 command right after paging up.
25784 The message will disappear immediately without causing a delay (unless you
25785 have set this option to a positive value) to allow you to type input for
25786 the "WhereIs" command.
25787 Since it isn't a very important message, Alpine has set its minimum display
25788 time to zero seconds.
25789 <P>
25790 Other messages have minimum display times of three or more seconds.
25791 These are usually error messages that Alpine thinks you ought to see.
25792 For example, it might be a message about a failed Save or a failed folder open.
25793 It is often the case that this minimum display time won't delay you in
25794 any way because the status message line is not needed for another reason.
25795 However, there are times when Alpine has to delay what it is doing in
25796 order to display a status message for the minimum display time.
25797 This happens when a message is being displayed and Alpine wants to ask
25798 for input from the keyboard.
25799 For example, when you Save a message you use the status message line.
25800 You get a prompt there asking for the name of the folder to save to.
25801 If there is a status message being displayed that has not
25802 yet displayed for its minimum
25803 time Alpine will display that status message surrounded with the characters
25804 > and < to show you that it is delaying.
25805 That might happen, for example, if you tried to save to a folder that
25806 caused an error, then followed that immediately with another Save command.
25807 You might find yourself waiting for a status message like
25808 <P>
25809 <CENTER><SAMP>[>Can't get write access to mailbox, access is readonly<]</SAMP></CENTER>
25810 <P>
25811 to finish displaying for three seconds.
25812 If that is something you find happening to you frequently, you may use
25813 negative values of this option to decrease or eliminate that delay, at
25814 the risk of missing the message.
25815 <P>
25816 <UL>
25817 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25818 </UL><P>
25819 <End of help on this topic>
25820 </BODY>
25821 </HTML>
25822 ====== h_config_active_msg_interval =====
25823 <HTML>
25824 <HEAD>
25825 <TITLE>OPTION: <!--#echo var="VAR_busy-cue-rate"--></TITLE>
25826 </HEAD>
25827 <BODY>
25828 <H1>OPTION: <!--#echo var="VAR_busy-cue-rate"--></H1>
25830 When Alpine is delayed for some reason it usually shows that
25831 something is happening with a small animated display in the status
25832 message line near the bottom of the screen.
25833 This option sets how frequently the characters (for example, a spinning bar)
25834 in the active status message lines are updated.
25835 At most, it can be set to be udpated 20 times per second.
25837 <P>
25838 Setting this value to zero will prevent display of the animations
25839 altogether.
25841 <P>
25842 The option <A HREF="h_config_use_boring_spinner"><!--#echo var="FEAT_busy-cue-spinner-only"--></A>
25843 can be used to remove the randomness from this animated display.
25845 <P>
25846 <UL>
25847 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25848 </UL><P>
25849 <End of help on this topic>
25850 </BODY>
25851 </HTML>
25852 ====== h_config_mailchecknoncurr =====
25853 <HTML>
25854 <HEADER>
25855 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></TITLE>
25856 </HEADER>
25857 <BODY>
25858 <H1>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></H1>
25860 This option is closely related to the
25861 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
25862 option, as well as the
25863 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A> and
25864 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> options.
25865 If the "<!--#echo var="VAR_mail-check-interval"-->" option is set to zero, then automatic
25866 new-mail checking is disabled and this option will have no effect.
25867 <P>
25868 Normally this option is set to zero, which means that the value used will be
25869 the same as the value for the "<!--#echo var="VAR_mail-check-interval"-->".
25870 If you set this option to a value different from zero
25871 (usually larger than the value for "<!--#echo var="VAR_mail-check-interval"-->")
25872 then that is the check interval that will be used
25873 for folders that are not the currently open folder or the INBOX.
25874 You may not even have any folders that are noncurrent and not the INBOX.
25875 If you do, it is likely that they are due to
25876 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
25877 you have configured.
25878 This option also affects the rate of mail checking done on cached
25879 connections to folders you previously had open but are no longer actively
25880 using.
25881 You aren't expected to understand that last sentence, but if you are interested
25882 take a look at
25883 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>
25884 and the related options.
25885 <P>
25886 <UL>
25887 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25888 </UL><P>
25889 <End of help on this topic>
25890 </BODY>
25891 </HTML>
25892 ====== h_config_fifopath =====
25893 <HTML>
25894 <HEADER>
25895 <TITLE>OPTION: NewMail FIFO Path</TITLE>
25896 </HEADER>
25897 <BODY>
25898 <H1>OPTION: NewMail FIFO Path</H1>
25900 This option is only available in UNIX Alpine.
25901 However, there is a very similar feature built in to PC-Alpine.
25902 In PC-Alpine's Config menu at the top of the screen
25903 is an option called "New Mail Window".
25904 <P>
25905 You may have Alpine create a FIFO special file (also called a named pipe) where
25906 it will send a one-line message each time a new message is received in
25907 the current folder, the INBOX, or any open
25908 <A HREF="h_config_permlocked"><!--#echo var="VAR_stay-open-folders"--></A>.
25909 To protect against two different Alpines both writing to the same FIFO, Alpine
25910 will only create the FIFO and write to it if it doesn't already exist.
25911 <P>
25912 A possible way to use this option would be to have a separate window
25913 on your screen running the command
25914 <P>
25915 <CENTER><SAMP>cat filename</SAMP></CENTER>
25916 <P>
25917 where "filename" is the name of the file given for this option.
25918 Because the file won't exist until after you start Alpine, you must <EM>first</EM>
25919 start Alpine and <EM>then</EM> run the "cat" command.
25920 You may be tempted to use "tail -f filename" to view the new
25921 mail log.
25922 However, the common implementations of the tail command will not do what you
25923 are hoping.
25924 <P>
25925 The width of the messages produced for the FIFO may be altered with the
25926 <A HREF="h_config_newmailwidth"><!--#echo var="VAR_newmail-window-width"--></A> option.
25927 <P>
25928 On some systems, fifos may only be created in a local filesystem.
25929 In other words, they may not be in NFS filesystems.
25930 This requirement is not universal.
25931 If the system you are using supports it, it should work.
25932 (It is often the case that your home directory is in an NFS filesystem.
25933 If that is the case, you might try using a file in the "/tmp"
25934 filesystem, which is usually a local filesytem.)
25935 Even when it is possible to use an NFS-mounted filesystem as a place to name
25936 the fifo (for example, your home directory), it will still be the case that
25937 the reader (probably the "cat" command) and the
25938 writer (Alpine) of the fifo must be running on the same system.
25939 <P>
25940 <UL>
25941 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25942 </UL><P>
25943 <End of help on this topic>
25944 </BODY>
25945 </HTML>
25946 ====== h_config_newmailwidth =====
25947 <HTML>
25948 <HEADER>
25949 <TITLE>OPTION: <!--#echo var="VAR_newmail-window-width"--></TITLE>
25950 </HEADER>
25951 <BODY>
25952 <H1>OPTION: <!--#echo var="VAR_newmail-window-width"--></H1>
25954 For UNIX Alpine, this option is only useful if you have turned on the
25955 <A HREF="h_config_fifopath">NewMail FIFO Path</A> option.
25956 That option causes new mail messages to be sent to a fifo file.
25957 Those messages will be 80 characters wide by default.
25958 You can change the width of those messages by changing this option.
25959 For example, if you are reading those messages in another window you might
25960 want to set this width to the width of that other window.
25961 <P>
25962 If you are using PC-Alpine, it has an option in the Config menu to turn
25963 on the "New Mail Window".
25964 This present option also controls the width of that window.
25965 <P>
25966 <UL>
25967 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25968 </UL><P>
25969 <End of help on this topic>
25970 </BODY>
25971 </HTML>
25972 ====== h_config_mailcheck =====
25973 <HTML>
25974 <HEADER>
25975 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval"--></TITLE>
25976 </HEADER>
25977 <BODY>
25978 <H1>OPTION: <!--#echo var="VAR_mail-check-interval"--></H1>
25980 This option specifies, in seconds,
25981 how often Alpine will check for new mail.
25982 If set to zero, new-mail checking is disabled.
25983 (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
25984 current message is the last message of the folder.)
25985 There is a minimum value for this option, normally 15 seconds.
25986 The default value is normally 150 seconds.
25987 The higher you set this option, the easier it is on the server.
25988 <P>
25989 There are some situations where automatic new-mail checking does not work.
25990 See the discussion about new-mail checking in
25991 <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
25992 <P>
25993 The new-mail checking will not happen exactly at the frequency that you specify.
25994 For example, Alpine may elect to defer a non-INBOX mail check if you
25995 are busy typing.
25996 Or, it may check more frequently than you have specified if that is
25997 thought to be necessary to keep the server from closing the connection
25998 to the folder due to inactivity.
25999 If Alpine checks for new mail as a side effect of another command, it will reset
26000 the timer, so that new-mail checking may seem to happen irregularly instead of
26001 every X seconds like clockwork.
26002 <P>
26003 If you are anxious to know about new mail as soon as possible, set the check
26004 interval low, and you'll know about the new mail by approximately
26005 that amount of time after it arrives.
26006 If you aren't so worried about knowing right away, set this option to a
26007 higher value.
26008 That will save the server some processing time and may save you some of
26009 the time you spend waiting for new-mail checks to happen if you are
26010 dealing with a slow server or slow network connection.
26011 <P>
26012 If you suspect that new-mail checking is causing slow downs for you,
26013 you may want to look into the options
26014 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>,
26015 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> and
26016 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A>,
26017 which refine when mail checking is done.
26018 <P>
26019 If the mailbox being checked uses a <A HREF="h_maildrop">Mail Drop</A> then
26020 there is a minimum time
26021 (<A HREF="h_config_maildropcheck">"<!--#echo var="VAR_maildrop-check-minimum"-->"</A>)
26022 between new-mail checks.
26023 Because of this minimum you may notice that new mail does not
26024 appear promptly when you expect it.
26025 The reason for this is to protect the server from over-zealous opening and
26026 closing of the Mail Drop folder, since that is a costly operation.
26027 <P>
26028 <UL>
26029 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26030 </UL><P>
26031 <End of help on this topic>
26032 </BODY>
26033 </HTML>
26034 ====== h_config_quell_checks_comp =====
26035 <HTML>
26036 <HEAD>
26037 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></TITLE>
26038 </HEAD>
26039 <BODY>
26040 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></H1>
26042 This option is closely related to the
26043 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26044 option, the
26045 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
26046 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A>.
26047 <P>
26048 If this option is set, then the normal new-mail checking that happens
26049 while you are composing will not happen for folders other than your
26050 INBOX (which depends on the setting
26051 of "<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->").
26052 <P>
26053 You might want to set this option if you are experiencing delays while
26054 composing that you think might be related to the speed of the new-mail
26055 checks.
26056 <P>
26057 Even with this option turned on, an occasional new-mail check may be done
26058 in order to keep the server from killing the connection to the folder.
26059 For example, IMAP servers may remove a connection to a folder if there
26060 has been no activity on the connection for 30 minutes or more.
26061 Instead of letting that happen, Alpine will check for new mail before the
26062 30 minutes is up even though you have turned on this feature to quell
26063 those checks.
26064 <P>
26065 Besides new-mail checks, checkpoint operations on the folders
26066 will also be quelled when you set this option.
26067 The purpose of checkpointing is to write the changes to a folder out to
26068 disk periodically in order to avoid losing those changes when system or
26069 software problems occur.
26070 New-mail checking and checkpointing while you are not composing are not
26071 affected by this option.
26073 <P>
26074 <End of help on this topic>
26075 </BODY>
26076 </HTML>
26077 ====== h_config_quell_checks_comp_inbox =====
26078 <HTML>
26079 <HEAD>
26080 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></TITLE>
26081 </HEAD>
26082 <BODY>
26083 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></H1>
26085 This option is closely related to the
26086 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26087 option, the
26088 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
26089 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>.
26090 <P>
26091 If this option is set, then the normal new-mail checking that happens
26092 while you are composing will not happen for your INBOX.
26093 Checking of other folders is controlled in a similar way with the
26094 "<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->" option.
26095 <P>
26096 You might want to set this option if you are experiencing delays while
26097 composing that you think might be related to the speed of the new-mail
26098 checks.
26099 <P>
26100 Even with this option turned on, an occasional new-mail check may be done
26101 in order to keep the server from killing the connection to the folder.
26102 For example, IMAP servers may remove a connection to a folder if there
26103 has been no activity on the connection for 30 minutes or more.
26104 Instead of letting that happen, Alpine will check for new mail before the
26105 30 minutes is up even though you have turned on this feature to quell
26106 those checks.
26107 <P>
26108 Besides new-mail checks, checkpoint operations on the INBOX
26109 will also be quelled when you set this option.
26110 The purpose of checkpointing is to write the changes to a folder out to
26111 disk periodically in order to avoid losing those changes when system or
26112 software problems occur.
26113 New-mail checking and checkpointing while you are not composing are not
26114 affected by this option.
26115 <P>
26116 <End of help on this topic>
26117 </BODY>
26118 </HTML>
26119 ====== h_config_maildropcheck =====
26120 <HTML>
26121 <HEADER>
26122 <TITLE>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></TITLE>
26123 </HEADER>
26124 <BODY>
26125 <H1>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></H1>
26127 New-mail checking for a
26128 <A HREF="h_maildrop">Mail Drop</A> is a little different from new
26129 mail checking for a regular folder.
26130 One of the differences is that the connection to the Mail Drop is not
26131 kept open and so the cost of checking
26132 (delay for you and additional load for the server) may be significant.
26133 Because of this additional cost we set a minimum time that
26134 must pass between checks.
26135 This minimum only applies to the automatic checking done by Alpine.
26136 If you force a check by typing ^L (Ctrl-L) or by typing the Next command when you are
26137 at the end of a folder index, then the check is done right away.
26138 <P>
26139 This option specifies, in seconds, the <EM>minimum</EM> time between Mail Drop
26140 new-mail checks.
26141 You may want to set this minimum high in order to avoid experiencing some
26142 of the delays associated with the checks.
26143 Note that the time between checks is still controlled by the regular
26144 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option.
26145 When Alpine is about to do an automatic check for new mail (because
26146 the <!--#echo var="VAR_mail-check-interval"--> has expired) then if the time since the last
26147 new-mail check
26148 of any open Mail Drops has been greater than the <!--#echo var="VAR_maildrop-check-minimum"-->,
26149 the Mail Drop is checked for new mail as well.
26150 Therefore, it is only useful to set this option to a value that is higher
26151 than the <!--#echo var="VAR_mail-check-interval"-->.
26152 <P>
26153 If this option is set to zero, automatic Mail Drop new-mail
26154 checking is disabled.
26155 There is a minimum value, normally 60 seconds.
26156 The default value is normally 60 seconds as well.
26157 This applies to the INBOX and to the currently open folder if that is
26158 different from the INBOX.
26160 <P>
26161 <UL>
26162 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26163 </UL><P>
26164 <End of help on this topic>
26165 </BODY>
26166 </HTML>
26167 ====== h_config_nntprange =====
26168 <HTML>
26169 <HEADER>
26170 <TITLE>OPTION: <!--#echo var="VAR_nntp-range"--></TITLE>
26171 </HEADER>
26172 <BODY>
26173 <H1>OPTION: <!--#echo var="VAR_nntp-range"--></H1>
26175 This option applies only to newsgroups accessed using the NNTP protocol.
26176 It does not, for example,
26177 apply to newsgroups accessed using an IMAP-to-NNTP proxy.
26179 <P>
26180 When you open a connection to a News server using the NNTP protocol, you
26181 normally have access to all of the articles in each newsgroup.
26182 If a server keeps a large backlog of messages it may speed performance
26183 some to restrict attention to only the newer messages in a group.
26184 This option allows you to set how many article numbers should be checked
26185 when opening a newsgroup.
26186 You can think of "<!--#echo var="VAR_nntp-range"-->" as specifying the maximum number
26187 of messages you ever want to see.
26188 For example, if you only ever wanted to look at the last 500 messages in each
26189 newsgroup you could set this option to 500.
26190 In actuality, it isn't quite that.
26191 Instead, for performance reasons, it specifies the range of article
26192 numbers to be checked, beginning
26193 with the highest numbered article and going backwards from there.
26194 If there are messages that have been canceled or deleted
26195 their article numbers are still counted as part of the range.
26196 <P>
26197 So, more precisely, setting the "<!--#echo var="VAR_nntp-range"-->" will cause article
26198 numbers
26199 <P><CENTER>last_article_number - <!--#echo var="VAR_nntp-range"--> + 1 through last_article_number</CENTER>
26200 <P>
26201 to be considered when reading a newsgroup.
26202 The number of messages that show up in your index will be less than or equal
26203 to the value of "<!--#echo var="VAR_nntp-range"-->".
26205 <P>
26206 The purpose of this option is simply to speed up access when reading news.
26207 The speedup comes because Alpine can ignore all but the last <!--#echo var="VAR_nntp-range"--> article
26208 numbers, and can avoid downloading any information about the ignored articles.
26209 There is a cost you pay for this speedup.
26210 That cost is that there is no way for you to see those ignored articles.
26211 The articles that come before the range you specify are invisible to you and
26212 to Alpine, as if they did not exist at all.
26213 There is no way to see those messages using, for example, an unexclude command
26214 or something similar.
26215 The only way to see those articles is to set this option high enough (or
26216 set it to zero) and then to reopen the newsgroup.
26218 <P>
26219 If this option is set to 0 (which is also the default),
26220 then the range is unlimited.
26221 This option applies globally to all NNTP servers and to all newsgroups
26222 on those servers.
26223 There is no way to set different values for different newsgroups or servers.
26225 <P>
26226 <UL>
26227 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26228 </UL><P>
26229 <End of help on this topic>
26230 </BODY>
26231 </HTML>
26232 ====== h_config_news_active =====
26233 <html>
26234 <header>
26235 <title>OPTION: <!--#echo var="VAR_news-active-file-path"--></title>
26236 </header>
26237 <body>
26238 <h1>OPTION: <!--#echo var="VAR_news-active-file-path"--></h1>
26240 This option tells Alpine where to look for the "active file" for newsgroups
26241 when accessing news locally, rather than via NNTP. The default path is
26242 usually "/usr/lib/news/active".<p>
26243 <UL>
26244 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26245 </UL><P>
26246 <End of help on this topic>
26247 </body>
26248 </html>
26249 ====== h_config_news_spool =====
26250 <html>
26251 <header>
26252 <title>OPTION: <!--#echo var="VAR_news-spool-directory"--></title>
26253 </header>
26254 <body>
26255 <h1>OPTION: <!--#echo var="VAR_news-spool-directory"--></h1>
26257 This option tells Alpine where to look for the "news spool" for newsgroups
26258 when accessing news locally, rather than via NNTP. The default path is
26259 usually "/var/spool/news".<p>
26260 <UL>
26261 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26262 </UL><P>
26263 <End of help on this topic>
26264 </body>
26265 </html>
26266 ====== h_config_image_viewer =====
26267 <html>
26268 <header>
26269 <title>OPTION: <!--#echo var="VAR_image-viewer"--></title>
26270 </header>
26271 <body>
26272 <h1>OPTION: <!--#echo var="VAR_image-viewer"--></h1>
26273 <body>
26274 This option specifies the program Alpine should call to view MIME
26275 attachments of type IMAGE (e.g. GIF or TIFF). The Image Viewer setting is
26276 no longer needed, but remains for backward compatibility. The more
26277 general method for associating external printing and viewing programs with
26278 specific MIME data types is to use the system's (or your personal)
26279 "mailcap" configuration file.<p>
26280 <UL>
26281 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26282 </UL><P>
26283 <End of help on this topic>
26284 </body>
26285 </html>
26286 ====== h_config_domain_name =====
26287 <HTML>
26288 <HEAD>
26289 <TITLE>OPTION: <!--#echo var="VAR_use-only-domain-name"--></TITLE>
26290 </HEAD>
26291 <BODY>
26292 <H1>OPTION: <!--#echo var="VAR_use-only-domain-name"--></H1>
26294 This option is used only if the
26295 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> option is <B>not</B>
26296 set. If set to "Yes" (and <!--#echo var="VAR_user-domain"--> is not used), then Alpine
26297 strips the hostname from your return ("From") address and when
26298 completing unqualified addresses that you enter into the composer.
26299 <P>
26300 If you set this, see also the <A HREF="h_config_quell_local_lookup">
26301 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
26304 <!--chtml if pinemode="os_windows"-->
26305 <P>This option is not applicable to PC-Alpine.
26306 <!--chtml else-->
26307 <P>
26308 <!--chtml endif-->
26309 <UL>
26310 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26311 </UL>
26312 <P>
26313 <End of help on this topic>
26314 </BODY>
26315 </HTML>
26316 ====== h_config_prune_date =====
26317 <HTML>
26318 <HEAD>
26319 <TITLE>OPTION: Last-Time-Prune Question</TITLE>
26320 </HEAD>
26321 <BODY>
26322 <H1>OPTION: Last-Time-Prune Question</H1>
26324 This value records the last time you were asked about deleting old
26325 sent-mail.
26326 It is set automatically by Alpine at the beginning of each month.
26327 In the past, if you wished to suppress the monthly sent-mail
26328 pruning feature, you could set this to a date in the future.
26329 This value is relative to the year 1900, so
26330 to set this, for example, to October 2005, use 105.10.
26331 <P>
26332 You can still do that if you wish, or you can use the
26333 <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option, which is probably
26334 a little more convenient to use.
26335 <P>
26336 <UL>
26337 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26338 </UL><P>
26339 <End of help on this topic>
26340 </BODY>
26341 </HTML>
26342 ====== h_config_goto_default =====
26343 <HTML>
26344 <HEAD>
26345 <TITLE>OPTION: <!--#echo var="VAR_goto-default-rule"--></TITLE>
26346 </HEAD>
26347 <BODY>
26348 <H1>OPTION: <!--#echo var="VAR_goto-default-rule"--></H1>
26350 This value affects Alpine's behavior when you use the Goto command.
26351 Alpine's usual behavior has two parts. If your current folder is
26352 "Inbox", Alpine will offer the last open folder as the
26353 default. If the current folder is other than "Inbox",
26354 "Inbox" is offered as the default.
26356 <P>
26357 The available options include:
26359 <DL>
26361 <DT>folder-in-first-collection</DT>
26363 <DD> Alpine will offer the most recently visited folder in the default
26364 collection found in the "Collection List" screen as the default.
26365 </DD>
26367 <DT> inbox-or-folder-in-first-collection</DT>
26369 <DD> If the current folder is "Inbox",
26370 Alpine will offer the most recently visited folder in the
26371 default collection found in the "Collection List" screen.
26372 If the current folder is other than "Inbox",
26373 "Inbox" is offered as the default.
26374 </DD>
26376 <DT> inbox-or-folder-in-recent-collection</DT>
26378 <DD> This is Alpine's default behavior.
26379 If the current folder is "Inbox",
26380 Alpine will offer the last open
26381 folder as the default.
26382 If the current folder is other than "Inbox",
26383 "Inbox" is offered as the default.
26384 </DD>
26386 <DT> first-collection-with-inbox-default</DT>
26388 <DD> Instead of offering the most recently visited folder in the default
26389 collection, the default collection is offered but with "Inbox" as
26390 the default folder.
26391 If you type in a folder name it will be in the default collection.
26392 If you simply accept the default, however, your "Inbox" will be opened.
26393 </DD>
26395 <DT> most-recent-folder</DT>
26397 <DD> The last accepted value simply causes the most recently opened
26398 folder to be offered as the default regardless of the currently opened
26399 folder.
26400 </DD>
26401 </DL>
26403 <P>
26404 NOTE: The default while a newsgroup is open remains the same; the last
26405 open newsgroup.
26407 <P>
26408 <UL>
26409 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26410 </UL><P>
26411 <End of help on this topic>
26412 </BODY>
26413 </HTML>
26414 ====== h_config_thread_lastreply_char =====
26415 <HTML>
26416 <HEAD>
26417 <TITLE>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></TITLE>
26418 </HEAD>
26419 <BODY>
26420 <H1>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></H1>
26422 The <!--#echo var="VAR_threading-lastreply-character"--> option has a small effect on the MESSAGE
26423 INDEX display when using a
26424 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
26425 of "show-thread-structure", "mutt-like", or
26426 "show-structure-in-from"; and sorting by Threads or OrderedSubject.
26427 The value of this option is a single character.
26428 This character is used instead of the vertical line character when there are
26429 no more replies directly to the parent of the current message.
26430 It can be used to "round-off" the bottom of the vertical line
26431 by setting it to a character such as a backslash (\) or
26432 a backquote (`).
26433 The default value of this option is the backslash character (\).
26434 This option may not be set to the Empty Value.
26435 In that case, the default will be used instead.
26437 <P>
26438 <UL>
26439 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26440 </UL><P>
26441 <End of help on this topic>
26442 </BODY>
26443 </HTML>
26444 ====== h_config_thread_indicator_char =====
26445 <HTML>
26446 <HEAD>
26447 <TITLE>OPTION: <!--#echo var="VAR_threading-indicator-character"--></TITLE>
26448 </HEAD>
26449 <BODY>
26450 <H1>OPTION: <!--#echo var="VAR_threading-indicator-character"--></H1>
26452 The <!--#echo var="VAR_threading-indicator-character"--> option has a small effect on the MESSAGE
26453 INDEX display when using a
26454 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26455 than "none" and sorting by Threads or OrderedSubject.
26456 The value of this option is a single character.
26457 This character is used to indicate that part of a thread (a conversation) is
26458 hidden beneath a message.
26459 The message could be expanded
26460 if desired with the "/" Collapse/Expand command.
26461 By default, the value of this option is the greater than sign (>).
26462 <P>
26463 If this option is set to the Empty Value, then the column (and the following
26464 blank column) will be deleted from the display.
26466 <P>
26467 This option is closely related to the
26468 <A HREF="h_config_thread_exp_char"><!--#echo var="VAR_threading-expanded-character"--></A> option.
26469 Another similar option that affects the thread display is the
26470 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26472 <P>
26473 <UL>
26474 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26475 </UL><P>
26476 <End of help on this topic>
26477 </BODY>
26478 </HTML>
26479 ====== h_config_thread_exp_char =====
26480 <HTML>
26481 <HEAD>
26482 <TITLE>OPTION: <!--#echo var="VAR_threading-expanded-character"--></TITLE>
26483 </HEAD>
26484 <BODY>
26485 <H1>OPTION: <!--#echo var="VAR_threading-expanded-character"--></H1>
26487 The <!--#echo var="VAR_threading-expanded-character"--> option has a small effect on the MESSAGE
26488 INDEX display when using a
26489 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26490 than "none".
26491 The value of this option is a single character.
26492 This character is used to indicate that part of a thread has been expanded
26493 and could be collapsed if desired with
26494 the "/" Collapse/Expand command.
26495 By default, the value of this option is a dot (.).
26496 <P>
26497 If this option is set to the Empty Value, then the column (and the following
26498 blank column) will be deleted from the display.
26500 <P>
26501 This option is closely related to the
26502 <A HREF="h_config_thread_indicator_char"><!--#echo var="VAR_threading-indicator-character"--></A> option.
26503 Another similar option that affects the thread display is the
26504 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26506 <P>
26507 <UL>
26508 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26509 </UL><P>
26510 <End of help on this topic>
26511 </BODY>
26512 </HTML>
26513 ====== h_config_thread_index_style =====
26514 <HTML>
26515 <HEAD>
26516 <TITLE>OPTION: <!--#echo var="VAR_threading-index-style"--></TITLE>
26517 </HEAD>
26518 <BODY>
26519 <H1>OPTION: <!--#echo var="VAR_threading-index-style"--></H1>
26521 When a folder is sorted by Threads or OrderedSubject,
26522 this option will affect the INDEX displays.
26523 <P>
26525 The possible values for this option are:
26527 <DL>
26528 <DT>regular-index-with-expanded-threads</DT>
26529 <DD>This is the default display.
26530 If the configuration option
26531 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26532 is set to something other than "none", then this setting
26533 will cause Alpine to start off with a MESSAGE INDEX with all of
26534 the threads expanded.
26535 That is, each message will have a line in the MESSAGE INDEX display.
26536 The Collapse/Expand command (/) may be used to manually collapse or
26537 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26538 <P>
26539 This setting affects the display when the folder is first threaded.
26540 The collapsed state may also be re-initialized by re-sorting the folder manually
26541 using the SortIndex command ($).
26542 After re-sorting the threads will once again all be expanded, even if you
26543 have previously collapsed some of them.
26544 <P>
26545 If "<!--#echo var="VAR_threading-display-style"-->" is set to "none", then
26546 the display will be the regular default Alpine MESSAGE INDEX, but sorted
26547 in a different order.
26548 </DD>
26550 <DT>regular-index-with-collapsed-threads</DT>
26551 <DD>If the configuration option
26552 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26553 is set to something other than "none", then this setting
26554 will cause Alpine to start out with all of the threads collapsed instead of
26555 starting out with all of the threads expanded.
26556 The Collapse/Expand command (/) may be used to manually collapse or
26557 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26558 <P>
26559 This setting affects the display when the folder is first threaded.
26560 The collapsed state may also be re-initialized by re-sorting the folder manually
26561 using the SortIndex command ($).
26562 After re-sorting the threads will once again all be collapsed, even if you
26563 have previously expanded some of them.
26564 </DD>
26566 <DT>separate-index-screen-always</DT>
26567 <DD>With this setting and the next, you will see an index of threads
26568 instead of an
26569 index of messages, provided you have sorted by Threads or OrderedSubject.
26570 <P>
26571 The THREAD INDEX contains a '*' in the first column if any message in the thread
26572 is marked Important.
26573 If not, it contains a '+' if any message in the thread is to you.
26574 The second column is blank. The third column contains a 'D' if all of the
26575 messages in the thread are deleted.
26576 Otherwise, it contains an 'N' if any of the messages in the thread are New.
26577 <P>
26578 When you view a particular thread from the THREAD INDEX you will be
26579 in the MESSAGE INDEX display
26580 but the index will only contain messages from the thread you are viewing.
26581 </DD>
26583 <DT>separate-index-screen-except-for-single-messages</DT>
26584 <DD>This is very similar to the option above.
26585 When you are in the THREAD INDEX, one of the available commands
26586 is "ViewThd".
26587 With the setting "separate-index-screen-always" (the option above)
26588 when you view a particular thread you will be in the
26589 MESSAGE INDEX display and the index will only contain messages from
26590 the thread you are viewing.
26591 If the thread you are viewing consists of a single message, the MESSAGE INDEX
26592 will be an index with only one message in it.
26593 If you use this "separate-index-screen-except-for-single-messages"
26594 setting instead, then that index that contains a single message
26595 will be skipped and you will go directly from the THREAD INDEX into the
26596 MESSAGE TEXT screen.
26597 </DD>
26599 </DL>
26601 <P>
26602 <UL>
26603 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26604 </UL><P>
26605 <End of help on this topic>
26606 </BODY>
26607 </HTML>
26608 ====== h_config_thread_disp_style =====
26609 <HTML>
26610 <HEAD>
26611 <TITLE>OPTION: <!--#echo var="VAR_threading-display-style"--></TITLE>
26612 </HEAD>
26613 <BODY>
26614 <H1>OPTION: <!--#echo var="VAR_threading-display-style"--></H1>
26616 When a folder is sorted by Threads or OrderedSubject,
26617 this option will affect the MESSAGE INDEX display.
26618 By default, Alpine will display the MESSAGE INDEX in the
26619 "show-thread-structure" style if a folder is sorted
26620 by Threads or OrderedSubject.
26621 <P>
26623 The possible values for this option are:
26625 <DL>
26626 <DT>none</DT>
26627 <DD>Regular index display.
26628 The same index line as would be displayed without threading is used.
26629 The only difference will be in the order of the messages.
26630 </DD>
26632 <DT>show-thread-structure</DT>
26633 <DD>Threaded Subjects will be indented and vertical bars and horizontal
26634 lines will be added to make it easier to see the relationships among
26635 the messages in a thread (a conversation).
26636 </DD>
26638 <DT>mutt-like</DT>
26639 <DD>This is the same as the option above except that the Subject
26640 is suppressed (is blank) if it matches the previous Subject in the thread.
26641 The name comes from the email client <A HREF="http://www.mutt.org/">Mutt</A>.
26642 Here is an example of what a mutt-like index might look like.
26643 In this example, the first column represents the message number, the
26644 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
26645 is set to "regular-index-with-expanded-threads", and the
26646 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A>
26647 is set to a backslash:
26648 <PRE>
26649 1 Some topic
26650 2 . Subject original message in thread
26651 3 |-> reply to 2
26652 4 . |-> another reply to 2
26653 5 . | \-> reply to 4
26654 6 . | \-> reply to 5
26655 7 | \-> reply to 6
26656 8 |-> another reply to 2
26657 9 . |->New subject another reply to 2 but with a New subject
26658 10 | |-> reply to 9
26659 11 | \-> another reply to 9
26660 12 | \-> reply to 11
26661 13 \-> final reply to 2
26662 14 Next topic
26663 </PRE>
26664 </DD>
26666 <DT>indent-subject-1</DT>
26667 <DD>Threaded Subjects will be indented one space per level of the conversation.
26668 The bars and lines that show up in the show-thread-structure display will
26669 not be there with this style.
26670 </DD>
26672 <DT>indent-subject-2</DT>
26673 <DD>Same as above but indent two spaces per level instead of one space.
26674 </DD>
26676 <DT>indent-from-1</DT>
26677 <DD>Similar to indent-subject-1, except that instead of indenting the
26678 Subject field one space the From field of a thread will be indented one
26679 space per level of the conversation.
26680 </DD>
26682 <DT>indent-from-2</DT>
26683 <DD>Same as above but indent two spaces per level instead of one space.
26684 </DD>
26686 <DT>show-structure-in-from</DT>
26687 <DD>The structure of the thread is illustrated with indenting, vertical bars,
26688 and horizontal lines just like with the show-thread-structure option, but
26689 the From field is used to show the relationships instead of the Subject field.
26690 </DD>
26692 </DL>
26694 <P>
26695 <UL>
26696 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26697 </UL><P>
26698 <End of help on this topic>
26699 </BODY>
26700 </HTML>
26701 ====== h_config_pruning_rule =====
26702 <HTML>
26703 <HEAD>
26704 <TITLE>OPTION: <!--#echo var="VAR_pruning-rule"--></TITLE>
26705 </HEAD>
26706 <BODY>
26707 <H1>OPTION: <!--#echo var="VAR_pruning-rule"--></H1>
26709 By default, Alpine will ask at the beginning of each month whether or not
26710 you want to rename your sent-mail folder to a name like sent-mail-month-year.
26711 (See the feature <A HREF="h_config_prune_uses_iso"><!--#echo var="FEAT_prune-uses-yyyy-mm"--></A> to
26712 change the format of the folder to sent-mail-yyyy-mm.)
26713 It will also ask whether you would like to delete old sent-mail folders.
26714 If you have defined
26715 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>
26716 or
26717 <A HREF="h_config_pruned_folders"><!--#echo var="VAR_pruned-folders"--></A>
26718 Alpine will also ask about pruning those folders.
26719 <P>
26721 With this option you may provide an automatic answer to these questions.
26722 The default value is to ask you what you'd like to do.
26723 <P>
26725 The six possible values for this option are:
26727 <DL>
26728 <DT>ask about rename, ask about deleting</DT>
26729 <DD>This is the default.
26730 Alpine will ask whether you want to rename the folders and whether you
26731 want to delete each of the old folders.
26732 </DD>
26734 <DT>ask about rename, don't delete</DT>
26735 <DD>Alpine will ask whether you want to rename the folders, but won't
26736 ask about or delete old folders.
26737 </DD>
26739 <DT>always rename, ask about deleting</DT>
26740 <DD>This means you want to always answer yes and have Alpine automatically
26741 rename the folder if possible.
26742 You will also be asked about deleting old folders.
26743 </DD>
26745 <DT>always rename, don't delete</DT>
26746 <DD>This means you want to always answer yes and have Alpine automatically
26747 rename the folder if possible.
26748 There will be no deleting of old folders.
26749 </DD>
26751 <DT>don't rename, ask about deleting</DT>
26752 <DD>This means you want to always answer no.
26753 Alpine will not rename the folder.
26754 You will be asked about deleting old folders.
26755 </DD>
26757 <DT>don't rename, don't delete</DT>
26758 <DD>This means you want to always answer no.
26759 Alpine will not rename the folder.
26760 There will be no deleting of old folders, either.
26761 </DD>
26762 </DL>
26764 <P>
26765 <UL>
26766 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26767 </UL><P>
26768 <End of help on this topic>
26769 </BODY>
26770 </HTML>
26771 ====== h_config_reopen_rule =====
26772 <HTML>
26773 <HEAD>
26774 <TITLE>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></TITLE>
26775 </HEAD>
26776 <BODY>
26777 <H1>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></H1>
26779 Alpine normally checks for new mail in the currently open folder
26780 and in the INBOX every few <A HREF="h_config_mailcheck">minutes</A>.
26782 <P>
26783 There are some situations where automatic new-mail checking does not work.
26784 For example, if a mail folder is opened using the POP protocol or a newsgroup
26785 is being read using the NNTP protocol, then new-mail checking is disabled.
26787 <P>
26788 It may be possible to check for new mail in these cases by reopening the
26789 folder.
26790 Alpine does not do this for you automatically, but you may do the commands
26791 manually to cause this to happen.
26792 You reopen by going back to the folder list screen from the message
26793 index screen with the "<" command,
26794 and then going back into the message index screen with
26795 the ">" command.
26796 (Actually, any method you would normally use to open a folder will work the
26797 same as the "<" followed by ">" method.
26798 For example, the GoTo Folder command will work, or you may use L to go to the
26799 Folder List screen and Carriage Return to reopen the folder.)
26801 <P>
26802 There are some cases where Alpine knows that reopening the folder should
26803 be useful as a way to discover new mail.
26804 At the time of this writing, connections made using the POP protocol,
26805 news reading using the NNTP protocol, local news reading, and local
26806 ReadOnly folders that are in the traditional UNIX or the MMDF format all
26807 fall into this category.
26808 There are other cases where it <EM>may</EM> be a way to discover new mail, but Alpine
26809 has no way of knowing, so it might also just be an exercise in futility.
26810 All remote, ReadOnly folders other than those listed just above fall into this
26811 category.
26812 The setting of this option together with the type of folder
26813 controls how Alpine will react to the apparent attempt to reopen a folder.
26815 <P>
26816 If you don't reopen, then you will just be back in
26817 the message index with no change.
26818 You left the index and came back, but the folder remained "open"
26819 the whole time.
26820 However, if you do reopen the folder, the folder is closed and then reopened.
26821 In this case, the current state of the open folder is lost.
26822 The New status, Important and Answered flags,
26823 selected state, Zoom state, collapsed or expanded state of threads,
26824 current message number,
26825 and any other temporary state is all lost when the reopen happens.
26826 For POP folders (but not NNTP newsgroups) the Deleted flags are also lost.
26828 <P>
26829 In the possibilities listed below, the text says "POP/NNTP" in
26830 several places.
26831 That really implies the case where Alpine knows it is a good way to discover
26832 new mail, which is more than just POP and NNTP, but POP and NNTP are
26833 the cases of most interest.
26834 This option probably has more possible values than it deserves. They are:
26836 <DL>
26837 <DT>Always reopen</DT>
26838 <DD>Alpine will not ask whether you want to reopen but will just do the reopen
26839 whenever you type a command that implies a reopen, regardless of the
26840 access method.
26841 In other words, it is assumed you would always answer Yes if asked
26842 about reopening.
26843 </DD>
26845 <DT>Yes for POP/NNTP, Ask about other remote [Yes]</DT>
26846 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
26847 will ask you whether to reopen other remote folders,
26848 with a default answer of Yes.
26849 </DD>
26851 <DT>Yes for POP/NNTP, Ask about other remote [No]</DT>
26852 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
26853 will ask you whether to reopen other remote folders,
26854 with a default answer of No.
26855 </DD>
26857 <DT>Yes for POP/NNTP, No for other remote</DT>
26858 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, and
26859 will assume a No answer for all other remote folders.
26860 </DD>
26862 <DT>Always ask [Yes]</DT>
26863 <DD>Alpine will not differentiate based on access method.
26864 It will always ask for all remote folders, with a default answer of Yes.
26865 </DD>
26867 <DT>Always ask [No]</DT>
26868 <DD>Alpine will not differentiate based on access method.
26869 It will always ask for all remote folders, with a default answer of No.
26870 </DD>
26872 <DT>Ask about POP/NNTP [Yes], No for other remote</DT>
26873 <DD>Alpine will ask if the access method is POP or NNTP, with a default answer
26874 of Yes.
26875 It will never attempt to reopen other remote folders.
26876 </DD>
26878 <DT>Ask about POP/NNTP [No], No for other remote</DT>
26879 <DD>This is the default.
26880 Alpine will ask if the access method is POP or NNTP, with a default answer
26881 of No.
26882 It will never attempt to reopen other remote folders.
26883 </DD>
26885 <DT>Never reopen</DT>
26886 <DD>Alpine will never attempt to reopen already open folders.
26887 </DD>
26888 </DL>
26890 <P>
26891 Remember, wherever it says POP or NNTP above it really means POP or NNTP or
26892 any of the other situations where it is likely that reopening is a good way
26893 to discover new mail.
26895 <P>
26896 There is an alternative that may be of useful in some situations.
26897 Instead of manually checking for new mail you can set up a
26898 <A HREF="h_maildrop">Mail Drop</A>
26899 and automatically check for new mail.
26901 <P>
26902 <UL>
26903 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26904 </UL><P>
26905 <End of help on this topic>
26906 </BODY>
26907 </HTML>
26908 ====== h_config_inc_startup =====
26909 <HTML>
26910 <HEAD>
26911 <TITLE>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></TITLE>
26912 </HEAD>
26913 <BODY>
26914 <H1>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></H1>
26916 This value affects Alpine's behavior when opening the "INBOX" or
26917 one of the "INCOMING MESSAGE FOLDERS".
26918 It determines which message will be the <EM>current message</EM> when
26919 the folder is first opened.
26920 The default value is "first-unseen".
26922 <P>
26923 The seven possible values for this option are:
26925 <DL>
26926 <DT>first-unseen</DT>
26927 <DD>The current message is set to the first
26928 unseen message that has not been marked deleted, or the last message if
26929 all of the messages have been seen previously.
26930 Messages which have not been seen or which have been seen but re-marked
26931 as New are considered unseen messages.
26932 See the note at the bottom of this help about newsgroups.
26933 </DD>
26935 <DT>first-recent</DT>
26936 <DD>Similar to the default, but rather than starting on the first
26937 unseen message Alpine starts on the first <EM>recent</EM> message.
26938 A message is recent if it arrived since the last time the folder was
26939 open. This value causes the current message to be set to the first
26940 recent message if there is one, otherwise to the last
26941 message in the folder.
26942 </DD>
26944 <DT>first-important</DT>
26945 <DD>This will result in the current message being set to the first
26946 message marked Important (but not Deleted).
26947 If no messages are marked Important, then it will be the last message.
26948 Messages are marked Important by <EM>you</EM>, not by the sender, using
26949 the
26950 <A HREF="h_common_flag">Flag command</A>.
26951 Or they may be marked Important by an Alpine
26952 <A HREF="h_mainhelp_filtering">Filter</A>
26953 that you have set up.
26954 </DD>
26956 <DT>first-important-or-unseen</DT>
26957 <DD>This selects the first of the first unseen and the first important
26958 messages.
26959 </DD>
26961 <DT>first-important-or-recent</DT>
26962 <DD>This selects the first of the first recent and the first important
26963 messages.
26964 </DD>
26966 <DT>first</DT>
26967 <DD>Simply starts you on the <EM>first</EM> undeleted message in the folder.
26968 If all messages are deleted you start on the last message.
26969 </DD>
26971 <DT>last</DT>
26972 <DD>Simply starts you on the <EM>last</EM> undeleted message in the folder
26973 If all messages are deleted you start on the last message.
26974 </DD>
26975 </DL>
26977 <P>
26978 NOTE: For newsgroups in the incoming collection, "first-unseen" and
26979 "first-recent" are the same and are affected by whether or not the
26980 feature
26981 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
26982 is turned on.
26983 Also, there is no permanent storage in news for an Important flag.
26984 This means that no messages will be marked Important when a newsgroup is
26985 first opened.
26987 <P>
26988 <UL>
26989 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26990 </UL><P>
26991 <End of help on this topic>
26992 </BODY>
26993 </HTML>
26994 ====== h_config_browser =====
26995 <HTML>
26996 <HEAD>
26997 <TITLE>OPTION: <!--#echo var="VAR_url-viewers"--></TITLE>
26998 </HEAD>
26999 <BODY>
27000 <H1>OPTION: <!--#echo var="VAR_url-viewers"--></H1>
27001 <!--chtml if pinemode="os_windows"-->
27002 PC-Alpine users do not need to enter anything here, unless:<UL>
27003 <LI> they want to override, for use with Alpine, the application defined
27004 in the Windows operating system for handling URLs; or
27005 <LI> they are (planning on) using the same configuration file with
27006 Unix Alpine.
27007 </UL>
27008 <P>
27009 Note that if using a viewer that has a space in its path, you should
27010 use the DOS name for that directory or file. Example:
27011 <PRE>
27012 url-viewer=C:\Progra~1\mozilla\mozilla.exe
27013 </PRE>
27014 <HR><P>
27015 <!--chtml endif-->
27016 This option affects Alpine's handling of URLs that are found in
27017 messages you read. Normally, only URLs Alpine can handle directly
27018 are automatically offered for selection in the "Message
27019 Text" screen. When one or more applications
27020 capable of deciphering URLs on their command line are added here, Alpine
27021 will choose the first available to display URLs it cannot handle directly.
27022 A viewer's availability is based on its being specified with a <B>full
27023 directory path</B> and the evaluation of any optionally supplied
27024 parameters described below.
27026 <P>
27027 Additionally, to support various connection methods and applications, each
27028 entry in this list can optionally begin with one or more of
27029 the following special tokens. The allowed tokens include:
27031 <P>
27032 <DL>
27033 <DT>_TEST(<VAR>test-string</VAR>)_</DT>
27034 <DD>
27035 The <VAR>test-string</VAR> is a shell command that Alpine will run to
27036 evaluate a viewer's availability. The command specified by the test
27037 string is run and if its resulting exit status is non-zero, Alpine will
27038 not consider the associated viewer for use.
27039 </DD>
27041 <DT>_SCHEME(<VAR>scheme-list</VAR>)_</DT>
27042 <DD>
27043 The <VAR>scheme-list</VAR> is a list of one or more (comma-delimited)
27044 URL schemes that are to be used with the associated viewer. This is
27045 the way to configure Alpine to recognize URLs other than the built-in set.
27046 <P>
27047 It can also be used to override Alpine's built-in handlers.
27048 For example, you could specify "news" in the <VAR>scheme-list</VAR>,
27049 and Alpine would use (provided it passed all other criteria) the associated
27050 viewer when it encounterd a URL of the form "news:comp.mail.pine".
27052 </DD>
27053 </DL>
27055 <P>
27056 By default, Alpine will simply append a space character followed by the
27057 selected URL prior to launching the command in your specified SHELL. You can
27058 optionally specify where in the command the selected URL should appear
27059 by using the "_URL_" token. All occurrences found in the command
27060 will be replaced with the selected URL before the command is handed
27061 to the shell. If such replacement occurs, the default appending of the
27062 selected URL does not take place.
27064 <P>
27065 NOTE: If the viewer you specify has any command-line arguments,
27066 including the "_URL_" token, you will need to add a
27067 double-quote character before the command path and after the last
27068 argument (see the "lynx" example below).
27070 <P>
27071 So, here are some example entries:
27072 <PRE>
27073 url-viewers = _TEST("test -n '${DISPLAY}'")_ /usr/local/bin/netscape
27074 "/usr/local/bin/lynx _URL_"
27075 C:\BIN\NETSCAPE.BAT
27076 </PRE>
27077 <P>
27078 This example shows that for the first viewer in the list to be used
27079 the environment variable "DISPLAY" must be defined. If it
27080 is, then the path and file "/usr/local/bin/netscape" must exist.
27081 If neither condition is met,
27082 then the path and file "/usr/local/bin/lynx" must exist.
27083 If it does, then the "_URL_" token is replaced by the selected URL.
27084 If the path to "lynx" is invalid,
27085 then the final path and file C:\BIN\NETSCAPE.BAT must exist.
27086 Note that the last
27087 entry is a DOS/Windows path. This is one way to support Alpine running
27088 on more than one architecture with the same configuration file.<P>
27089 <P>
27090 <!--chtml if pinemode="os_windows"-->
27091 <!--chtml else-->
27092 Note that depending on the type of browser used and the method of
27093 its invocation (such as whether it will open in a separate window) from
27094 the MESSAGE TEXT screen, the browser may "supplant"
27095 the MESSAGE TEXT screen, and you will have to quit the browser to return to
27096 it (for example, when using Lynx; to exit Lynx, use the "Q" command).
27097 In other words, launching the browser from Alpine may make Alpine
27098 "disappear" (although it is still "running")
27099 until you close the browser again.<P>
27100 <UL><LI><A HREF="h_config_browser_xterm">Defining <!--#echo var="VAR_url-viewers"--> in an X windows
27101 environment: for advanced users and systems administrators</A>
27102 </UL>
27103 <!--chtml endif-->
27104 <P>If you are unsure what browsers are available on your system or how to
27105 specify them in Alpine's <!--#echo var="VAR_url-viewers"--> option for best usability, contact your
27106 local computing support staff.
27107 <P><UL>
27108 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27109 </UL>
27110 <P>
27111 <End of help on this topic>
27112 </BODY>
27113 </HTML>
27114 ====== h_config_browser_xterm =====
27115 <HTML>
27116 <HEAD>
27117 <TITLE><!--#echo var="VAR_url-viewers"--> and X windows applications</TITLE>
27118 </HEAD>
27119 <BODY>
27120 <H1>Defining <!--#echo var="VAR_url-viewers"--> in an X windows
27121 environment: for advanced users and systems administrators</H1>
27122 If you are using Alpine with an X-terminal (emulator) and want to define an
27123 X windows-based application in <!--#echo var="VAR_url-viewers"-->,
27124 you may want to do so in a manner that causes any <B>already</B>
27125 invoked viewer application to be used for viewing URLs you select from Alpine
27126 messages, and a <B>new</B> URL-viewer process to be
27127 started <B>only</B> if the same application has <B>not already</B>
27128 been launched -- for one reason, to avoid file-locking contentions among
27129 multiple invocations of the same URL-viewer application.
27130 (The example entries set in the help screen for the "<!--#echo var="VAR_url-viewers"-->"
27131 option does not do this.) A method of doing that would be:<OL>
27132 <LI> use
27133 the _TEST(<VAR>test-string</VAR>)_ token in the <B>first</B> entry to
27134 check (using commands appropriate for your Unix shell
27135 in place of <VAR>test-string</VAR>) for the presence of a
27136 lockfile created by the URL-viewer application -- which implies that the
27137 application is already running, though this is not foolproof.
27138 Following that in the same <!--#echo var="VAR_url-viewers"--> entry, specify the
27139 application with its appropriate command line option(s) to
27140 show the URL selected from the Alpine message in an already open window of
27141 that application, or perhaps in a new window of that application.
27143 <LI> In the
27144 <B>second</B> entry for the <!--#echo var="VAR_url-viewers"--> option, specify the same
27145 application without those command line options, but this time using the
27146 _TEST(...)_ token to check whether the environment variable "DISPLAY"
27147 is defined.
27148 <LI> If you will be using Alpine (with the same .pinerc file) outside of the X
27149 windows environment (for instance, using VT-100 terminal emulation), you
27150 may wish to specify a non-X windows URL-viewer application such as Lynx
27151 as the last entry.
27152 </OL><BR>
27153 How exactly you define your <!--#echo var="VAR_url-viewers"--> entries to do this will depend on
27154 the command shell, the URL-viewer application(s), and possibly the specific
27155 version of the latter, you are using.
27156 <P>
27157 Relevant command
27158 line options for the Netscape browser for showing URLs (selected from Alpine)
27159 when Netscape is already running are discussed in the document
27160 "Remote Control of UNIX Netscape"
27161 found at the URL (as of 12 Aug. 1998):
27162 <P>
27164 <CENTER><A HREF="http://home.netscape.com/newsref/std/x-remote.html">http://home.netscape.com/newsref/std/x-remote.html</A></CENTER>
27166 <P>(If the URL-viewer application is
27167 <B>not</B> running on the same host as Alpine, but being launched from an
27168 applications server, you may not be able to use the command line options for
27169 using an existing invocation of the application in Alpine's <!--#echo var="VAR_url-viewers"--> entry.)
27170 <P>
27171 <!--chtml if this-method="shown-to-work"-->
27172 An example using the Korn shell and the Netscape browser (first entry wrapped
27173 because of its length, but should all appear on one line):
27174 <P>
27175 url-viewers = _TEST("test -L /myhomedir/.netscape/lock")_ "/usr/local/bin/netscape -remote 'openURL(_URL_, new-window)' &"<BR>
27177 _TEST("test -n '${DISPLAY}'")_ "/usr/local/bin/netscape &"<BR>
27178 "/usr/local/bin/lynx '_URL_'"
27179 <P>
27180 <!--chtml endif-->
27181 <P>
27182 <UL>
27183 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27184 </UL><P>
27185 <End of help on this topic>
27186 </BODY>
27187 </HTML>
27188 ====== h_config_enable_full_hdr =====
27189 <HTML>
27190 <HEAD>
27191 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></TITLE>
27192 </HEAD>
27193 <BODY>
27194 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></H1>
27196 This feature enables the "H Full Headers" command which toggles between
27197 the display of all headers in the message and the normal edited view of
27198 headers. The Full Header command also controls which headers are included
27199 for Export, Pipe, Print, Forward, and Reply functions. (For Reply, the
27200 Full Header mode will respect the
27201 <A HREF="h_config_include_header">"Include-Headers-in-Reply"</A>
27202 feature setting.)
27203 <P>
27204 If Full Header mode is turned on and you Forward a message, you will
27205 be asked if you'd like to forward the message as an attachment, as opposed
27206 to including the text of the message in the body of your new message.
27207 <P>
27208 If you have also turned on the
27209 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
27210 option then the Full Headers command actually rotates through three states
27211 instead of just two.
27212 The first is the normal view with long quotes suppressed.
27213 The second is the normal view but with the long quotes included.
27214 The last enables the display of all headers in the message.
27215 When using Export, Pipe, Print, Forward, or Reply the quotes are
27216 never suppressed, so the first two states are identical.
27217 <P>
27218 Normally, the Header Mode will reset
27219 to the default behavior when moving to a new message.
27220 The mode can be made to persist from message to message by setting the feature
27221 <A HREF="h_config_quell_full_hdr_reset"><!--#echo var="FEAT_quell-full-header-auto-reset"--></A>.
27222 <P>
27223 <UL>
27224 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27225 </UL><P>
27226 <End of help on this topic>
27227 </BODY>
27228 </HTML>
27229 ====== h_config_enable_full_hdr_and_text =====
27230 <HTML>
27231 <HEAD>
27232 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></TITLE>
27233 </HEAD>
27234 <BODY>
27235 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></H1>
27237 This feature affects how the "H Full Headers" command displays
27238 message text. If set, the raw message text will be displayed. This
27239 especially affects MIME formatted email, where the entire MIME format
27240 will be displayed. This feature similarly affects how messages are
27241 included for the Export, Pipe, Print, Forward, and Reply functions.
27242 <P>
27243 When viewing a raw message that has attachments with this feature set,
27244 you will not be able to view attachments without first leaving full
27245 headers mode. This is because MIME parsing is not done on the raw message.
27246 <P>
27247 <UL>
27248 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27249 </UL><P>
27250 <End of help on this topic>
27251 </BODY>
27252 </HTML>
27253 ====== h_config_enable_pipe =====
27254 <HTML>
27255 <HEAD>
27256 <TITLE>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></TITLE>
27257 </HEAD>
27258 <BODY>
27259 <H1>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></H1>
27261 This feature enables the "| Pipe" command that sends the current message
27262 to the specified command for external processing.
27263 <P>
27265 A short description of how the pipe command works is given
27266 <A HREF="h_pipe_command">here</A>.
27268 <P>
27269 <UL>
27270 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27271 </UL><P>
27272 <End of help on this topic>
27273 </BODY>
27274 </HTML>
27275 ====== h_config_quell_full_hdr_reset =====
27276 <HTML>
27277 <HEAD>
27278 <TITLE>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></TITLE>
27279 </HEAD>
27280 <BODY>
27281 <H1>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></H1>
27283 The <A HREF="h_common_hdrmode">HdrMode Command</A>
27284 normally resets to the default state when switching to a new message.
27285 For example, if you've used the "H" command to turn on Full
27286 Headers for a message you are viewing, and then you type the Next command
27287 to look at the next message, the full headers will no longer be shown.
27288 Setting this feature disables that reset.
27289 Instead, the Header Mode remains the same from message to message.
27291 <P>
27292 The presence or absence of the HdrMode command is determined by the
27293 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
27294 Feature-List option.
27295 <P>
27296 <UL>
27297 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27298 </UL><P>
27299 <End of help on this topic>
27300 </BODY>
27301 </HTML>
27302 ====== h_config_enable_tab_complete =====
27303 <HTML>
27304 <HEAD>
27305 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></TITLE>
27306 </HEAD>
27307 <BODY>
27308 <H1>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></H1>
27310 This feature enables the TAB key when at a prompt for a filename. In this
27311 case, TAB will cause the partial name already entered to be automatically
27312 completed, provided the partial name is unambiguous.
27313 This feature is on by default.
27314 <P>
27315 Similarly, this feature also enables TAB completion of address book
27316 nicknames when at a prompt for a nickname,
27317 or when typing in an address field in the composer.
27318 <P>
27319 <End of help on this topic>
27320 </BODY>
27321 </HTML>
27322 ====== h_config_quit_wo_confirm =====
27323 <HTML>
27324 <HEAD>
27325 <TITLE>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></TITLE>
27326 </HEAD>
27327 <BODY>
27328 <H1>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></H1>
27330 This feature controls whether or not Alpine will ask for confirmation when a
27331 Quit command is received.
27332 <P>
27333 <End of help on this topic>
27334 </BODY>
27335 </HTML>
27336 ====== h_config_quote_replace_noflow =====
27337 <HTML>
27338 <HEAD>
27339 <TITLE>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></TITLE>
27340 </HEAD>
27341 <BODY>
27342 <H1>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></H1>
27344 This feature, which is only active when
27345 <A HREF="h_config_quote_replace_string"><!--#echo var="VAR_quote-replace-string"--></A> is
27346 also set,
27347 enables quote-replacement on non-flowed messages. It is off
27348 by default because a non-flowed message is more dependent on its format,
27349 and thus quote-replacement may cause less-than-pleasing results.
27350 Setting this feature will cause quote-replacement similar to that of flowed
27351 messages, but with the added possibility of long lines being wrapped
27352 into new lines if the Quote-Replacement-String is longer than the string
27353 it is replacing, which is "> ".
27354 <P>
27355 <End of help on this topic>
27356 </BODY>
27357 </HTML>
27358 ====== h_config_enable_jump =====
27359 <HTML>
27360 <HEAD>
27361 <TITLE>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></TITLE>
27362 </HEAD>
27363 <BODY>
27364 <H1>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></H1>
27366 When this feature is set you may enter a number (followed by RETURN)
27367 and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT
27368 screens. In other words, it obviates the need for typing the "J" for the
27369 Jump command.
27370 <P>
27371 <End of help on this topic>
27372 </BODY>
27373 </HTML>
27374 ====== h_config_enable_alt_ed =====
27375 <HTML>
27376 <HEAD>
27377 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></TITLE>
27378 </HEAD>
27379 <BODY>
27380 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></H1>
27382 If this feature is set (the default), and the
27383 <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27384 <B>is not</B> set, entering
27385 the ^_ (Ctrl-underscore) key while composing a message will prompt you
27386 for the name of the editor you would like to use.
27387 <P>
27388 If the environment variable $EDITOR is set, its value will be offered as
27389 a default.
27390 <P>
27391 If the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27392 <B>is</B> set, the ^_ key will activate the specified
27393 editor without prompting, in which case it is not necessary to
27394 set the "<!--#echo var="FEAT_enable-alternate-editor-cmd"-->" feature.
27395 <P>
27396 <UL>
27397 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27398 </UL><P>
27399 <End of help on this topic>
27400 </BODY>
27401 </HTML>
27402 ====== h_config_alt_ed_now =====
27403 <HTML>
27404 <HEAD>
27405 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></TITLE>
27406 </HEAD>
27407 <BODY>
27408 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></H1>
27410 If this feature and the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A>
27411 variable are both set, Alpine will
27412 automatically activate the specified editor when the cursor is moved from
27413 the header of the message being composed into the message text. For
27414 replies, the alternate editor will be activated immediately. If this
27415 feature is set but the "<!--#echo var="VAR_editor"-->" variable is not set, then Alpine will
27416 automatically ask for the name of an alternate editor when the cursor
27417 is moved out of the header being composed, or if a reply is being done.
27419 <P><UL>
27420 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27421 </UL>
27422 <P>
27423 <End of help on this topic>
27424 </BODY>
27425 </HTML>
27426 ====== h_config_enable_bounce =====
27427 <HTML>
27428 <HEAD>
27429 <TITLE>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></TITLE>
27430 </HEAD>
27431 <H1>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></H1>
27432 <BODY>
27434 Setting this feature enables the "B Bounce" command, which will prompt
27435 for an address and *remail* the message to the new recipient. This command
27436 is used to re-direct messages that you have received in error, or need to
27437 be redirected for some other reason (e.g. list moderation). The final
27438 recipient will see a header indicating that you have Resent the msg, but
27439 the message's From: header will show the original author of the message,
27440 and replies to it will go back to that author, and not to you.
27441 <P>
27442 <End of help on this topic>
27443 </BODY>
27444 </HTML>
27445 ====== h_config_enable_agg_ops =====
27446 <HTML>
27447 <HEAD>
27448 <TITLE>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></TITLE>
27449 </HEAD>
27450 <BODY>
27451 <H1>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></H1>
27453 When this feature is set you may use the commands and subcommands that relate to
27454 performing operations on more than one message at a time. We call these
27455 "aggregate operations". In particular, the
27456 <!--chtml if pinemode="function_key"-->"F5
27457 <!--chtml else-->";
27458 <!--chtml endif--> Select",
27460 <!--chtml if pinemode="function_key"-->
27461 "F6
27462 <!--chtml else-->
27463 "A
27464 <!--chtml endif-->
27465 Apply", and
27466 <!--chtml if pinemode="function_key"-->
27467 "F4
27468 <!--chtml else-->
27469 "Z
27470 <!--chtml endif-->
27471 Zoom" commands are enabled by this feature. Select is used to
27472 "tag" one or more messages meeting the specified criteria. Apply can
27473 then be used to apply any message command to all of the selected/tagged
27474 messages. Further, the Zoom command allows you to toggle the MESSAGE INDEX
27475 view between just those Selected and all messages in the folder.
27476 <P>
27477 This feature also enables the
27478 <!--chtml if pinemode="function_key"-->
27479 "F7"
27480 <!--chtml else-->
27481 "^X"
27482 <!--chtml endif-->
27484 subcommand in the MESSAGE INDEX
27485 WhereIs command that causes all messages matching the WhereIs argument to
27486 become selected; and the Select, Select Current, and ZoomMode commands in the
27487 <A HREF="h_folder_maint">FOLDER LIST screen</A>.
27488 <P>
27489 Some related help topics are
27490 <UL>
27491 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
27492 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
27493 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
27494 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
27495 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
27496 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
27497 </UL>
27498 <P>
27499 <UL>
27500 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27501 </UL><P>
27502 <End of help on this topic>
27503 </BODY>
27504 </HTML>
27506 ====== h_config_enable_flag =====
27507 <HTML>
27508 <HEAD>
27509 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></TITLE>
27510 </HEAD>
27511 <BODY>
27512 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></H1>
27514 Setting this feature enables the
27515 <A HREF="h_common_flag">"* Flag"</A>
27516 command that allows you to
27517 manipulate the status flags associated with a message. By default, Flag
27518 will set the "Important" flag, which results in an asterisk being
27519 displayed in column one of the MESSAGE INDEX for such messages.
27520 <P>
27521 <End of help on this topic>
27522 </BODY>
27523 </HTML>
27524 ====== h_config_flag_screen_default =====
27525 <HTML>
27526 <HEAD>
27527 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></TITLE>
27528 </HEAD>
27529 <BODY>
27530 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></H1>
27532 The feature modifies the behavior of the
27533 <a href="h_common_flag">Flag</a>
27534 command (provided it too is
27535 <A HREF="h_config_enable_flag">enabled</A>).
27536 By default, when the "* Flag" command is selected,
27537 Alpine offers a prompt to set one of several flags and also offers the
27538 option of entering the detailed flag manipulation screen via the "^T"
27539 key. Enabling this feature causes Alpine to immediately enter the detailed
27540 flag screen rather than first offer the simple prompt.
27541 The
27542 <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.
27543 <P>
27544 <End of help on this topic>
27545 </BODY>
27546 </HTML>
27547 ====== h_config_flag_screen_kw_shortcut =====
27548 <HTML>
27549 <HEAD>
27550 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></TITLE>
27551 </HEAD>
27552 <BODY>
27553 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></H1>
27555 This feature modifies the behavior of the
27556 <a href="h_common_flag">Flag</a> command
27557 and the <A HREF="h_index_cmd_select">Select</A> command.
27558 This feature is set by default.
27559 When this feature is not set, when the "* Flag" command is selected,
27560 Alpine offers a prompt to set one of several flags and also offers the
27561 option of entering the detailed flag manipulation screen via the "^T"
27562 key.
27563 If you have
27564 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
27565 defined, then enabling this feature adds a shortcut way to set or unset
27566 keywords.
27567 You use "*" followed by the first letter of a keyword (or the nickname of
27568 a keyword if you've given it a nickname) and that will set the keyword.
27569 <P>
27570 An example is easier to understand than the explanation.
27571 The flag command can always be used to set the system flags.
27572 For example, to set the Answered flag you would type
27573 <P>
27574 <CENTER><SAMP>* A</SAMP></CENTER>
27575 <P>
27576 Now suppose you have defined a keyword "Work" using the <!--#echo var="VAR_keywords"-->
27577 option in the Config screen.
27578 By default, to set a keyword like "Work" you would usually
27579 have to go to the Flag Details screen using
27580 the "^T To Flag Details" command.
27581 Instead, if you have enabled this feature, you may type
27582 <P>
27583 <CENTER><SAMP>* W</SAMP></CENTER>
27584 <P>
27585 to set the Work flag, or
27586 <P>
27587 <CENTER><SAMP>* ! W</SAMP></CENTER>
27588 <P>
27589 to unset it.
27590 Just like for the other flag setting commands, the case of the letter does
27591 not matter, so "w" or "W" both set the "Work"
27592 keyword.
27593 <P>
27594 Notice that you can only use this trick for one keyword that begins
27595 with "W".
27596 If you happen to have a "Work" keyword and another keyword that is
27597 "WIFI" the "* W" command will set the first one in
27598 your list of keywords.
27599 Also, there are five letters that are reserved for system
27600 flags and the NOT command.
27601 If you type "* A" it will always set the Answered flag, not
27602 your "Aardvark" keyword.
27603 In order to set the "Aardvark" keyword you'll still have to use
27604 the Flag Details screen.
27605 <P>
27606 Because enabling the
27607 <A HREF="h_config_flag_screen_default"><!--#echo var="FEAT_enable-flag-screen-implicitly"--></A>
27608 option causes Alpine to skip directly to the Flag Details screen when the
27609 Flag command is used,
27610 setting it will cause this feature to have no effect at all.
27611 <P>
27612 Similarly, when Selecting by Keyword, setting this option will allow you
27613 to use Keyword initials instead of full keywords.
27614 <P>
27615 <End of help on this topic>
27616 </BODY>
27617 </HTML>
27618 ====== h_config_can_suspend =====
27619 <HTML>
27620 <HEAD>
27621 <TITLE>FEATURE: <!--#echo var="FEAT_enable-suspend"--></TITLE>
27622 </HEAD>
27623 <BODY>
27624 <H1>FEATURE: <!--#echo var="FEAT_enable-suspend"--></H1>
27626 Setting this feature will allow you to type ^Z (Control Z) to
27627 <!--chtml if pinemode="os_windows"-->
27628 minimize Alpine into its icon, bringing into focus whatever
27629 application is running behind the PC-Alpine window.
27630 <!--chtml else-->
27631 temporarily suspend Alpine.
27633 <P>
27634 This does not exit Alpine, but puts it in the background to watch
27635 for new mail and such. Normally, you type a command, such
27636 as "fg" at your system prompt to return to your Alpine session.
27638 <P>
27639 The <A HREF="h_config_suspend_spawns"><!--#echo var="FEAT_use-subshell-for-suspend"--></A> feature
27640 adjusts whether Alpine is placed into the background of the shell its
27641 running in or starts a news shell.
27642 <!--chtml endif-->
27644 <P>
27645 <UL>
27646 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27647 </UL><P>
27648 <End of help on this topic>
27649 </BODY>
27650 </HTML>
27651 ====== h_config_take_lastfirst ======
27652 <HTML>
27653 <HEAD>
27654 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></TITLE>
27655 </HEAD>
27656 <BODY>
27657 <H1>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></H1>
27659 Normally, when TakeAddr is used to copy an address from a message into
27660 an address book entry, Alpine will attempt to rewrite the full name of the
27661 address in the form
27662 <P>
27664 Last, First<P>
27666 instead of<P>
27668 First Last
27670 <P>
27671 It does this because many people find it useful to sort by Last name
27672 instead of First name. If this feature is set, then the TakeAddr command
27673 will not attempt to reverse the name in this manner.
27674 <P>
27675 <End of help on this topic>
27676 </BODY></HTML>
27677 ====== h_config_disable_regex ======
27678 <HTML>
27679 <HEAD>
27680 <TITLE>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></TITLE>
27681 </HEAD>
27682 <BODY>
27683 <H1>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></H1>
27685 Normally, the
27686 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
27687 option is interpreted as a regular expression.
27688 One type of address that might cause trouble is an address that
27689 contains a plus sign.
27690 If you want to have an address with a plus as one of your
27691 <!--#echo var="VAR_alt-addresses"-->
27692 and you don't want to use regular expressions, then setting this
27693 feature will cause Alpine to treat the addresses you list literally instead.
27694 <P>
27695 <End of help on this topic>
27696 </BODY></HTML>
27697 ====== h_config_take_fullname ======
27698 <HTML>
27699 <HEAD>
27700 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></TITLE>
27701 </HEAD>
27702 <BODY>
27703 <H1>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></H1>
27705 Normally, when TakeAddr is used to copy an address or addresses
27706 from a message into an address book entry, Alpine will try to preserve
27707 the full name associated with each address in the list of addresses.
27708 The reason for this is so that if the entry is a list or later becomes a
27709 list, then information about the individual addresses in the list
27710 is preserved.
27711 If you would rather just have the simple addresses in the list of addresses,
27712 set this feature. For example, with the default setting you might
27713 see something like this in the ADDRESS BOOK editor after you type TakeAddr
27714 <P>
27715 <PRE>
27716 Nickname : nick
27717 Fullname : Bedrock Elders
27718 Fcc :
27719 Comment :
27720 Addresses : Fred Flintstone <flint@bedrock.org>,
27721 Barney Rubble <rubble@bedrock.org>
27722 </PRE>
27723 <P>
27724 but with this feature set it would look like
27725 <P>
27726 <PRE>
27727 Nickname : nick
27728 Fullname : Bedrock Elders
27729 Fcc :
27730 Comment :
27731 Addresses : flint@bedrock.org,
27732 rubble@bedrock.org
27733 </PRE>
27734 <P>
27735 instead. Note the difference in the Addresses field.
27736 <P>
27737 <End of help on this topic>
27738 </BODY></HTML>
27739 ====== h_config_print_from ======
27740 <HTML>
27741 <HEAD>
27742 <TITLE>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></TITLE>
27743 </HEAD>
27744 <BODY>
27745 <H1>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></H1>
27747 If this feature is set, then the Berkeley-mail style From line is included
27748 at the start of each message that is printed. This line looks something
27749 like the following, with the address replaced by the address from the
27750 From line of the message being printed:
27751 <P>
27752 From user@domain.somewhere.com Mon May 13
27753 14:11:06 1998
27754 <P>
27755 <End of help on this topic>
27756 </BODY>
27757 </HTML>
27758 ====== h_config_expanded_distlists ======
27759 <HTML>
27760 <HEAD>
27761 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></TITLE>
27762 </HEAD>
27763 <BODY>
27764 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></H1>
27765 If this feature is set, then distribution lists in the address book
27766 screen will always be expanded automatically.
27767 <P>
27768 <End of help on this topic>
27769 </BODY>
27770 </HTML>
27771 ====== h_config_compose_news_wo_conf ======
27772 <HTML>
27773 <HEAD>
27774 <TITLE>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></TITLE>
27775 </HEAD>
27776 <BODY>
27777 <H1>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></H1>
27778 This feature controls one aspect of Alpine's Composer. If you enter the
27779 composer while reading a newsgroup, you will normally be prompted to
27780 determine whether you intend the new message to be posted to the current
27781 newsgroup or not. If this feature is set, Alpine will not prompt you
27782 in this situation, and will assume that you do indeed wish to post
27783 to the newsgroup you are reading.
27784 <P>
27785 <End of help on this topic>
27786 </BODY>
27787 </HTML>
27788 ====== h_config_compose_rejects_unqual ======
27789 <HTML>
27790 <HEAD>
27791 <TITLE>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></TITLE>
27792 </HEAD>
27793 <BODY>
27794 <H1>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></H1>
27796 This feature controls one aspect of the message composer; in particular,
27797 what happens when an unqualified name is entered into an address header.
27798 If set, unqualified names entered as addresses will be treated as errors
27799 unless they match an addressbook nickname. Alpine will not attempt to turn
27800 them into complete addresses by adding your local domain.<P>
27802 A complete (fully qualified) address is one containing a username followed
27803 by an "@" ("at") symbol, followed by a domain name (e.g.
27804 "jsmith@example.com"). An unqualified name is one <B>without</B>
27805 the "@" symbol and domain name (e.g. "jsmith").
27807 (See also <A HREF="h_address_format">Explanation of Address formats</A>.)
27809 <P>
27811 When you enter a fully qualified address, Alpine does not interpret or
27812 modify it, but simply passes it on to the mail-transport-agent (MTA) for
27813 your system. Alpine conforms to the Internet standards governing message
27814 headers and will not send an unqualifed name to the MTA. Therefore, when
27815 you enter an unqualified name, Alpine will normally attempt to turn it into
27816 a fully qualified address, first by checking to see if you have entered a
27817 matching nickname in your addressbook, or failing that, by simply adding
27818 your own domain to the name entered. So if your address is
27819 "jsmith@example.com" and you enter "fred", then (assuming
27820 "fred" is not a nickname in your addressbook), Alpine will turn
27821 that into "fred@example.com".<P>
27823 There are situations where it is not desirable for Alpine to interpret such
27824 unqualified names as valid (local) addresses. For example, if "fred"
27825 turned out to be a typo (intended to be an addressbook nickname), but
27826 there actually was a "fred" in your local domain, the message might
27827 be mis-delivered without your realizing it. In order to reduce the likelihood
27828 of such accidents, setting this feature will cause Alpine to treat such
27829 addresses as errors, and require that you explicitly enter the full local
27830 address (e.g. "fred@example.com") or correct the name so that it
27831 matches an address book nickname.<P>
27833 Consider this a safety feature against mis-directed mail.
27834 <P>
27835 <UL>
27836 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27837 </UL><P>
27838 <End of help on this topic>
27839 </BODY>
27840 </HTML>
27841 ====== h_config_quell_local_lookup ======
27842 <HTML>
27843 <HEAD>
27844 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></TITLE>
27845 </HEAD>
27846 <BODY>
27847 <H1>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></H1>
27849 This feature controls an aspect of Alpine's Composer, and if needed, will
27850 usually be set by your system manager in Alpine's system-wide configuration
27851 file. Specifically, if this feature is set, Alpine will not attempt to look
27852 in the system password file to find a Full Name for the entered address.
27853 <P>
27854 Normally, names you enter into address fields (e.g. To: or Cc:) are
27855 checked against your address book(s) to see if they match an address book
27856 nickname. Failing that, (in Unix Alpine) the name is then checked against
27857 the Unix password file. If the entered name matches a username in the
27858 system password file, Alpine extracts the corresponding Full Name information
27859 for that individual, and adds that to the address being entered.
27860 <P>
27861 However, password file matching can have surprising (incorrect) results if
27862 other users of the system do not receive mail at the domain you are using.
27863 That is, if either the
27864 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> or
27865 <A HREF="h_config_domain_name">"<!--#echo var="VAR_use-only-domain-name"-->"</A>
27866 option
27867 is set such that the administrative domain of other users on the system
27868 isn't accurately reflected, Alpine should be told that a passwd file match
27869 is coincidental, and Full Name info will be incorrect. For example, a
27870 personal name from the password file could get falsely paired with the
27871 entered name as it is turned into an address in the configured domain.
27872 <P>
27873 If you are seeing this behavior, enabling this feature will prevent Unix
27874 Alpine from looking up names in the password file to find the Full Name
27875 for incomplete addresses you enter.<P>
27876 <UL>
27877 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27878 </UL>
27879 <P>
27880 <End of help on this topic>
27881 </BODY>
27882 </HTML>
27883 ====== h_config_tab_checks_recent ======
27884 <HTML>
27885 <HEAD>
27886 <TITLE>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></TITLE>
27887 </HEAD>
27888 <BODY>
27889 <H1>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></H1>
27891 In a FOLDER LIST screen, the TAB key usually just changes which
27892 folder is highlighted.
27893 If this feature is set, then the TAB key will cause the number of
27894 recent messages and the total number of messages in the highlighted folder
27895 to be displayed instead.
27897 <P>
27898 <End of help on this topic>
27899 </BODY>
27900 </HTML>
27901 ====== h_config_maildrops_preserve_state ======
27902 <HTML>
27903 <HEAD>
27904 <TITLE>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></TITLE>
27905 </HEAD>
27906 <BODY>
27907 <H1>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></H1>
27909 This feature affects the way <A HREF="h_maildrop">Mail Drops</A> work.
27910 Normally, when mail is moved from a Mail Drop folder to a destination
27911 folder, it is delivered as new mail.
27912 Any Seen/New, Answered, Important/Flagged state that has changed will be
27913 ignored.
27914 All of the mail will be considered unSeen, unAnswered, and unImportant after
27915 it is moved.
27916 <P>
27917 If this feature is set, then the state changes that have been made
27918 to the messages in the Mail Drop folder will be preserved.
27919 <P>
27920 In any case, messages that are already marked Deleted when the
27921 mail is to be moved from the Mail Drop will be ignored.
27922 <P>
27923 <End of help on this topic>
27924 </BODY>
27925 </HTML>
27926 ====== h_config_preopen_stayopens ======
27927 <HTML>
27928 <HEAD>
27929 <TITLE>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></TITLE>
27930 </HEAD>
27931 <BODY>
27932 <H1>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></H1>
27934 This feature is related to the option
27935 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
27936 Normally, Stay Open folders are only opened on demand, when the user
27937 asks to open them.
27938 From then on they are kept open for the duration of the session.
27939 However, if this feature is set, then the Stay Open folders will all be
27940 opened at startup, at the same time that the INBOX is opened.
27942 <P>
27943 <End of help on this topic>
27944 </BODY>
27945 </HTML>
27946 ====== h_config_expunge_inbox ======
27947 <HTML>
27948 <HEAD>
27949 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></TITLE>
27950 </HEAD>
27951 <BODY>
27952 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></H1>
27954 The INBOX is normally treated differently from regular folders in several
27955 ways.
27956 One of the differences is that the normal "close" sequence of
27957 events is deferred until Alpine is exited, instead of happening when you
27958 leave the INBOX to view another folder.
27959 The "close" sequence normally includes the Expunging
27960 of deleted messages
27961 (either automatically or after a prompt, controlled by the features
27962 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
27963 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
27964 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
27965 handling of the
27966 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>.
27968 <P>
27969 If this feature is set the "close" sequence handling will take
27970 place every time you leave the INBOX.
27971 The INBOX will still be kept open, but the offer to Expunge and the archiving
27972 to the <!--#echo var="VAR_read-message-folder"-->
27973 will take place each time you leave the INBOX instead of only once at the
27974 end of the session.
27976 <P>
27977 <End of help on this topic>
27978 </BODY>
27979 </HTML>
27980 ====== h_config_expunge_stayopens ======
27981 <HTML>
27982 <HEAD>
27983 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></TITLE>
27984 </HEAD>
27985 <BODY>
27986 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></H1>
27988 This feature is related to the option
27989 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
27990 Stay Open folders are treated differently from regular folders in several
27991 ways.
27992 One of the differences is that the normal "close" sequence of
27993 events is deferred until Alpine is exited, instead of happening when you
27994 leave the folder to view another folder.
27995 The "close" sequence normally includes the Expunging
27996 of deleted messages
27997 (either automatically or after a prompt, controlled by the features
27998 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
27999 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
28000 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
28001 handling of
28002 <A HREF="h_config_archived_folders"><!--#echo var="VAR_incoming-archive-folders"--></A>.
28004 <P>
28005 If this feature is set the "close" sequence handling will take
28006 place when you leave the Stay Open folder.
28007 The folder will still be kept open, but the offer to Expunge and the archiving
28008 will take place each time you leave the folder instead of only once at the
28009 end of the session.
28010 This feature does not affect the INBOX, which will still only be processed
28011 when you exit Alpine.
28012 However, there is a similar feature that affects only the INBOX called
28013 <A HREF="h_config_expunge_inbox">"<!--#echo var="FEAT_offer-expunge-of-inbox"-->"</A>.
28015 <P>
28016 <End of help on this topic>
28017 </BODY>
28018 </HTML>
28019 ====== h_config_preserve_start_stop ======
28020 <HTML>
28021 <HEAD>
28022 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></TITLE>
28023 </HEAD>
28024 <BODY>
28025 <H1>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></H1>
28027 This feature controls how special control key characters, typically
28028 Ctrl-S and Ctrl-Q, are interpreted when input to Alpine. These characters
28029 are known as the "stop" and "start" characters and are sometimes used in
28030 communications paths to control data flow between devices that operate at
28031 different speeds.
28033 <P>
28035 By default, Alpine turns the system's handling of these special characters
28036 off except during printing. However, if you see Alpine reporting input errors
28037 such as:
28038 <P>
28039 [ Command "^Q" not defined for this screen.]
28040 <P>
28041 and, at the same time, see your display become garbled, then it is likely
28042 that setting this option will solve the problem. Be aware, though, that
28043 enabling this feature will also cause Alpine to ostensibly "hang"
28044 whenever the Ctrl-S key combination is entered as the system is now
28045 interpreting such input as a "stop output" command. To "start
28046 output" again, simply type Ctrl-Q.
28047 <P>
28048 <End of help on this topic>
28049 </BODY>
28050 </HTML>
28051 ====== h_config_enable_incoming ======
28052 <HTML>
28053 <HEAD>
28054 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></TITLE>
28055 </HEAD>
28056 <BODY>
28057 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></H1>
28059 Alpine's Incoming Message Folders collection
28060 provides a convenient way to access multiple incoming folders.
28061 It is also useful if you have accounts on multiple computers.
28062 <P>
28064 If set, this feature defines a pseudo-folder collection called
28065 "INCOMING MESSAGE FOLDERS". Initially, the only folder included
28066 in this collection will be your INBOX, which will no longer show up in
28067 your Default folder collection.
28068 <P>
28070 You may add more folders to the Incoming Message Folders collection by
28071 using the
28072 <!--chtml if pinemode="function_key"-->
28073 "F10
28074 <!--chtml else-->
28075 "A
28076 <!--chtml endif-->
28077 Add" command in the FOLDER LIST screen. You will be prompted for
28078 the host the folder is stored on (which defaults to the same host used
28079 for your INBOX), a nickname, and the actual folder name. Once a set
28080 of Incoming Message Folders are defined, the TAB key (in MESSAGE INDEX
28081 or MESSAGE TEXT screens) may be used to scan the folders for those
28082 with Recent messages. If you add more folders to
28083 your <!--#echo var="VAR_incoming-folders"--> collection, turning this feature back off will have
28084 no effect.
28085 <P>
28086 NOTE: Normally the software that actually delivers mail (the stuff that happens
28087 before Alpine is involved) is in a better position to do delivery filtering
28088 than is Alpine itself.
28089 If possible, you may want to look at programs such as
28090 "filter" or "procmail", which are examples of delivery
28091 filtering programs.
28092 If you'd prefer to have Alpine do the filtering for you, you may set that
28093 up.
28094 Look <A HREF="h_rules_filter">here</A> for help with Alpine filtering.
28095 <P>
28096 <UL>
28097 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28098 </UL><P>
28099 <End of help on this topic>
28100 </BODY>
28101 </HTML>
28102 ====== h_config_enable_incoming_checking ======
28103 <HTML>
28104 <HEAD>
28105 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></TITLE>
28106 </HEAD>
28107 <BODY>
28108 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></H1>
28110 This feature is only operational if you have enabled the optional
28111 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> collection.
28112 If you do have Incoming Message Folders and you also set this feature,
28113 then the number of Unseen messages in each folder will be displayed
28114 in the FOLDER LIST screen for the Incoming Message Folders.
28115 The number of Unseen messages in a folder will be displayed in parentheses
28116 to the right of the name of each folder.
28117 If there are no Unseen messages in a folder then only the name
28118 is displayed, not a set of parentheses with zero inside them.
28119 A redraw command, Ctrl-L, can be used in the FOLDER LIST screen for
28120 the Incoming Message Folders to cause an immediate update.
28121 <P>
28122 If a check for Unseen messages fails for a particular folder then Alpine
28123 will no longer attempt to check that folder for the duration of the
28124 session and this will be indicated by a question mark inside the
28125 parentheses.
28126 <P>
28127 The features
28128 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>,
28129 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>,
28130 <A HREF="h_config_incoming_list"><!--#echo var="VAR_incoming-check-list"--></A>,
28131 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>,
28132 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>, and
28133 <A HREF="h_config_incoming_timeo"><!--#echo var="VAR_incoming-check-timeout"--></A>
28134 all affect how this feature behaves.
28135 <P>
28136 <UL>
28137 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28138 </UL><P>
28139 <End of help on this topic>
28140 </BODY>
28141 </HTML>
28142 ====== h_config_incoming_checking_total ======
28143 <HTML>
28144 <HEAD>
28145 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></TITLE>
28146 </HEAD>
28147 <BODY>
28148 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></H1>
28150 This option has no effect unless the feature
28151 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
28152 is set, which in turn has no effect unless
28153 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28154 is set.
28155 <P>
28156 When incoming folder checking is turned on the default is to display
28157 the number of unseen messages in each folder.
28158 More precisely, it is the number of undeleted unseen messages.
28159 Using this option you may also display the total number of messages
28160 in each folder.
28161 Instead of a single number representing the number of unseen messages
28162 you will get two numbers separated by a slash character.
28163 The first is the number of unseen messages and the second is the
28164 total number of messages.
28165 <P>
28166 You may also use the recent message count instead of the unseen message
28167 count by turning on the feature
28168 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>.
28169 <P>
28170 <UL>
28171 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28172 </UL><P>
28173 <End of help on this topic>
28174 </BODY>
28175 </HTML>
28176 ====== h_config_incoming_checking_recent ======
28177 <HTML>
28178 <HEAD>
28179 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></TITLE>
28180 </HEAD>
28181 <BODY>
28182 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></H1>
28184 This option has no effect unless the feature
28185 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
28186 is set, which in turn has no effect unless
28187 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28188 is set.
28189 <P>
28190 When incoming folder checking is turned on the default is to display
28191 the number of unseen messages in each folder.
28192 More precisely, it is the number of undeleted unseen messages.
28193 Using this option you may display the number of recent messages instead
28194 of the number of unseen messages.
28195 A message is only counted as recent if this is the first session to
28196 see it, so the recent count might be less than the unseen count.
28197 The difference between the two would be accounted for by the unseen messages
28198 in the folder which were there previously but have not been looked at yet.
28199 <P>
28200 If you simultaneously run more than one email client at a time
28201 (for example, you run more than one Alpine in parallel) then turning
28202 this feature on can cause some confusion.
28203 The confusion stems from the fact that each message is only considered to be
28204 recent in one session.
28205 That means that the counts of new messages may be different in the two
28206 Alpines running side by side, because each incoming message will only be
28207 counted as recent in one of the two sessions.
28208 <P>
28209 You may also display the total number of messages
28210 in each folder by using the
28211 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
28212 option.
28213 <P>
28214 <UL>
28215 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28216 </UL><P>
28217 <End of help on this topic>
28218 </BODY>
28219 </HTML>
28220 ====== h_config_attach_in_reply ======
28221 <HTML>
28222 <HEAD>
28223 <TITLE>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></TITLE>
28224 </HEAD>
28225 <BODY>
28226 <H1>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></H1>
28228 This feature controls an aspect of Alpine's Reply command. If set, any MIME
28229 attachments that were part of the original message will automatically be
28230 included in the Reply.
28231 <P>
28232 <End of help on this topic>
28233 </BODY>
28234 </HTML>
28235 ====== h_config_include_header =====
28236 <HTML>
28237 <HEAD>
28238 <TITLE>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></TITLE>
28239 </HEAD>
28240 <BODY>
28241 <H1>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></H1>
28243 This feature controls an aspect of Alpine's Reply command. If set, and the
28244 original message is being included in the reply, then headers from that
28245 message will also be part of the reply.
28246 <P>
28247 <End of help on this topic>
28248 </HEAD>
28249 </HTML>
28250 ====== h_config_sig_at_bottom =====
28251 <HTML>
28252 <HEAD>
28253 <TITLE>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></TITLE>
28254 </HEAD>
28255 <BODY>
28256 <H1>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></H1>
28258 This feature controls an aspect of Alpine's Reply command. If this feature
28259 is set, and the original message is being included in the reply, then the
28260 contents of your signature file (if any) will be inserted after the included
28261 message.
28262 <P>
28263 This feature does not affect the results of a Forward command.
28264 <P>
28265 <End of help on this topic>
28266 </BODY>
28267 </HTML>
28268 ====== h_config_sigdashes =====
28269 <HTML>
28270 <HEAD>
28271 <TITLE>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></TITLE>
28272 </HEAD>
28273 <BODY>
28274 <H1>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></H1>
28276 This feature enables support for the common USENET news convention
28277 of preceding a message signature with the special line consisting of
28278 the three characters "-- " (i.e., dash, dash, and space).
28280 <P>
28281 When enabled and a
28282 "<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>" exists,
28283 Alpine will insert the special line before including the file's text (unless
28284 the special line already exists somewhere in the file's text).
28286 <P>
28287 In addition, when you Reply or Followup to a message containing one of
28288 these special lines and choose to include its text, Alpine will observe
28289 the convention of not including text beyond the special line in your
28290 reply.
28291 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
28292 mode is enabled and turned on, then Alpine <EM>will</EM>
28293 include the text beyond the special line regardless of the setting of
28294 this feature.
28296 <P>
28297 See also "<a href="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>"
28298 for a related feature.
28300 <P>
28301 <UL>
28302 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28303 </UL><P>
28304 <End of help on this topic>
28305 </BODY>
28306 </HTML>
28307 ====== h_config_new_thread_blank_subject =====
28308 <HTML>
28309 <HEAD>
28310 <TITLE>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></TITLE>
28311 </HEAD>
28312 <BODY>
28313 <H1>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></H1>
28315 When this feature is enabled (the default) Alpine will create a new thread
28316 every time that the subject line becomes empty at any time during composition.
28318 <P>
28319 This behavior is particularly useful in case you are replying to a message.
28320 Replying to a message causes the message to be in the same thread than the
28321 original message that is being replied to. However, many authors want to create
28322 a new message (in a different thread) while replying to a message, and they do
28323 this by changing the full subject, by first deleting the original subject and
28324 typing the new subject of the current message.
28326 <P>
28327 Enabling this feature causes that any time that the subject is deleted, the
28328 message being composed will be considered the first message of a new thread.
28330 <P>
28331 <UL>
28332 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28333 </UL><P>
28334 <End of help on this topic>
28335 </BODY>
28336 </HTML>
28337 ====== h_config_strip_sigdashes =====
28338 <HTML>
28339 <HEAD>
28340 <TITLE>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></TITLE>
28341 </HEAD>
28342 <BODY>
28343 <H1>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></H1>
28345 This feature doesn't do anything if the feature
28346 "<A HREF="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></A>" is turned on.
28347 However, if the "<!--#echo var="FEAT_enable-sigdashes"-->" feature is not turned on,
28348 then turning on this feature enables support for the convention
28349 of not including text beyond the sigdashes line when Replying or Following
28350 up to a message and including the text of that message.
28351 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
28352 mode is enabled and turned on, then Alpine <EM>will</EM>
28353 include the text beyond the special line regardless of the setting of
28354 this feature.
28355 <P>
28356 In other words, this is a way to turn on the signature stripping behavior
28357 without also turning on the dashes-adding behavior.
28358 <P>
28359 <UL>
28360 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28361 </UL><P>
28362 <End of help on this topic>
28363 </BODY>
28364 </HTML>
28365 ====== h_config_forward_as_attachment =====
28366 <HTML>
28367 <HEAD>
28368 <TITLE>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></TITLE>
28369 </HEAD>
28370 <BODY>
28371 <H1>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></H1>
28373 This feature affects the way forwarded message text is handled. When set, rather than
28374 include the text of the forwarded message below any additional text you provide in the
28375 composer, the forwarded message is attached in its entirety to the message you send.
28376 <P>
28377 This is useful in that it keeps the text you provide in the composer distinct from the
28378 text of the forwarded message. Similarly, it allows the recipient to
28379 conveniently operate on the forwarded message. For example, they might reply directly to
28380 the sender of the forwarded message, or process it as part of a spam report.
28381 <UL>
28382 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28383 </UL><P>
28384 <End of help on this topic>
28385 </BODY>
28386 </HTML>
28387 ====== h_config_preserve_field =====
28388 <HTML>
28389 <HEAD>
28390 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></TITLE>
28391 </HEAD>
28392 <BODY>
28393 <H1>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></H1>
28395 This feature affects Alpine's behavior when one replies to a message.
28396 When you receive a message, some or all of the recipients of the message
28397 have been added to the To: and Cc: fields. If you reply to such message,
28398 and this feature is disabled, then the original sender of the message is
28399 added to the To: field, and all other recipients are added to the Cc:
28400 field, while your address is added to the From: field.
28402 <P>
28403 However, if this feature is enabled, then Alpine will preserve the
28404 original fields as sent in the original message, so the Cc: and To:
28405 fields will be preserved. The sender's address will be added to the To:
28406 field, while your address is added to the From: field.
28408 <P>
28409 The behavior of this feature is that replies to all messages will behave
28410 in the way described above. If you only intend this to happen on a per
28411 message basis, then keep this feature disabled, and when replying to a
28412 message you will see a new option in the menu for the "Reply to all
28413 recipients?" question. In this case, pressing "p" will
28414 make Alpine toggle its question so you can preserve the To: and Cc:
28415 fields for that message only.
28417 <UL>
28418 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28419 </UL><P>
28420 <End of help on this topic>
28421 </BODY>
28422 </HTML>
28423 ====== h_config_sub_lists =====
28424 <HTML>
28425 <HEAD>
28426 <TITLE>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></TITLE>
28427 </HEAD>
28428 <BODY>
28429 <H1>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></H1>
28431 This feature affects the subcommands available when Saving,
28432 or when Opening a new folder. If set, the subcommand ^X ListMatches will be
28433 available. This command allows you to type in a substring of the folder
28434 you are looking for and when you type ^X it will display all folders
28435 that contain that substring in their names.
28436 This feature is set by default.
28438 <P>
28439 <End of help on this topic>
28440 </BODY>
28441 </HTML>
28442 ====== h_config_scramble_message_id =====
28443 <HTML>
28444 <HEAD>
28445 <TITLE>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></TITLE>
28446 </HEAD>
28447 <BODY>
28448 <H1>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></H1>
28450 Normally the Message-ID header that Alpine generates when sending a message
28451 contains the name of the computer from which the message is being sent.
28452 Some believe that this hostname could be used by spammers or could
28453 be used by others for nefarious purposes.
28454 If this feature is set, that name will be transformed with a simple
28455 Rot13 transformation.
28456 The result will still have the correct syntax for a Message-ID but the
28457 part of the MessageID that is often a domain name will not be an actual
28458 domain name because the letters will be scrambled.
28459 <P>
28460 In addition, other information such as the name program, version, and
28461 a code for operating system used to build Alpine, will be encoded using
28462 the Rot13 transformation, except for the version number which will be
28463 encoded using a Rot5 transformation.
28464 <P>
28465 It is possible (but unlikely?) that some spam detection
28466 software will use that as a reason to reject the mail as spam.
28467 It has also been reported that some spam detection software uses the
28468 fact that there are no dots after the "@" as a reason to reject
28469 messages.
28470 If your PC-Alpine Message-ID is using a name without a dot that is because
28471 that is what Windows thinks is your "Full computer name".
28472 The method used to set this varies from one type of Windows to another but
28473 check under Settings -> Control Panel -> System and
28474 look for Network Identification or Computer Name or something similar.
28475 How to set it is beyond the scope of Alpine.
28477 <P>
28478 <End of help on this topic>
28479 </BODY>
28480 </HTML>
28481 ====== h_downgrade_multipart_to_text =====
28482 <HTML>
28483 <HEAD>
28484 <TITLE>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></TITLE>
28485 </HEAD>
28486 <BODY>
28487 <H1>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></H1>
28489 <P>
28490 This feature affects Alpine's behavior when sending mail. Internet
28491 standards require Alpine to translate all non-ASCII characters in
28492 messages that it sends using MIME encoding. This encoding can be
28493 ostensibly broken for recipients if any agent between Alpine and the
28494 recipient, such as an email list expander, appends text to the
28495 message, such as list information or advertising. When sending such
28496 messages Alpine attempts to protect such encoding by placing extra
28497 MIME boundaries around the message text.
28498 <P>
28499 These extra boundaries are invisible to recipients that
28500 use MIME-aware email programs (the vast majority). However, if
28501 you correspond with users of email programs that are not MIME-aware,
28502 or do not handle the extra boundaries gracefully, you can
28503 use this feature to prevent Alpine from including the extra
28504 MIME information. Of course, it will increase the likelihood
28505 that non-ASCII text you send may appear corrupt to the recipient.
28506 <P>
28507 <End of help on this topic>
28508 </BODY>
28509 </HTML>
28510 ====== h_config_show_sort =====
28511 <HTML>
28512 <HEAD>
28513 <TITLE>FEATURE: <!--#echo var="FEAT_show-sort"--></TITLE>
28514 </HEAD>
28515 <BODY>
28516 <H1>FEATURE: <!--#echo var="FEAT_show-sort"--></H1>
28518 If this feature is set and there is sufficient space on the screen,
28519 a short indication of the current sort order will be
28520 added in the titlebar (the top line on the screen), before the name
28521 of the folder.
28522 For example, with the default Arrival sort in effect,
28523 the display would have the characters
28525 <P><CENTER>[A]</CENTER><P>
28527 added between the title of the screen and the folder name.
28528 The letters are the same as the letters you may type to manually
28529 sort a folder with the SortIndex command ($).
28530 The letters in the table below are the ones that may show
28531 up in the titlebar line.
28532 <P>
28533 <TABLE>
28534 <TR> <TD> A </TD> <TD> <EM>A</EM>rrival </TD> </TR>
28535 <TR> <TD> S </TD> <TD> <EM>S</EM>ubject </TD> </TR>
28536 <TR> <TD> F </TD> <TD> <EM>F</EM>rom </TD> </TR>
28537 <TR> <TD> T </TD> <TD> <EM>T</EM>o </TD> </TR>
28538 <TR> <TD> C </TD> <TD> <EM>C</EM>c </TD> </TR>
28539 <TR> <TD> D </TD> <TD> <EM>D</EM>ate </TD> </TR>
28540 <TR> <TD> Z </TD> <TD> si<EM>Z</EM>e </TD> </TR>
28541 <TR> <TD> O </TD> <TD> <EM>O</EM>rderedsubject </TD> </TR>
28542 <TR> <TD> E </TD> <TD> scor<EM>E</EM> </TD> </TR>
28543 <TR> <TD> H </TD> <TD> t<EM>H</EM>read </TD> </TR>
28544 </TABLE>
28545 <P>
28546 If the sort order is Reversed, the letter above will be preceded by the letter
28547 "R", for example
28549 <P><CENTER>[RS]</CENTER><P>
28551 means that a Reverse Subject sort is in effect.
28552 For the case where the sort is in Reverse Arrival order, the "A" is
28553 left out, and just an "R" is shown.
28555 <P><CENTER>[R]</CENTER>
28557 <P>
28558 <End of help on this topic>
28559 </BODY>
28560 </HTML>
28561 ====== h_config_disable_reset_disp =====
28562 <HTML>
28563 <HEAD>
28564 <TITLE>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></TITLE>
28565 </HEAD>
28566 <BODY>
28567 <H1>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></H1>
28569 UNIX Alpine only.
28570 <P>
28571 This feature affects Alpine's behavior when using
28572 <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>.
28573 Normally, before the display filter is run, the terminal mode is reset
28574 to what it was before you started Alpine.
28575 This may be necessary if the filter requires the use of the terminal.
28576 For example, it may need to interact with you.
28577 If you set this feature, then the terminal mode will not be reset.
28578 One thing that turning on this feature should fix is the coloring of
28579 <A HREF="h_config_quote_color">quoted text</A> in the message view, which
28580 breaks because the terminal reset resets the color state of the terminal.
28582 <P>
28583 <End of help on this topic>
28584 </BODY>
28585 </HTML>
28586 ====== h_config_disable_sender =====
28587 <HTML>
28588 <HEAD>
28589 <TITLE>FEATURE: <!--#echo var="FEAT_disable-sender"--></TITLE>
28590 </HEAD>
28591 <BODY>
28592 <H1>FEATURE: <!--#echo var="FEAT_disable-sender"--></H1>
28594 This feature affects Alpine's generation of the "Sender:" or
28595 <A HREF="h_config_use_sender_not_x">"X-X-Sender"</A>
28596 header fields.
28597 By default, Alpine will generate such a header in situations where the
28598 username or domain are not the same as
28599 the "From:" header on the message.
28600 With this feature set,
28601 no "Sender:" or "X-X-Sender" header will be generated.
28602 This may be desirable on a system that is virtually hosting many domains,
28603 and the sysadmin has other methods available for tracking a message to
28604 its originator.
28605 <P>
28606 See also <A HREF="h_config_allow_chg_from">"<!--#echo var="FEAT_allow-changing-from"-->"</A>.
28608 <P>
28609 <End of help on this topic>
28610 </BODY>
28611 </HTML>
28612 ====== h_config_use_sender_not_x =====
28613 <HTML>
28614 <HEAD>
28615 <TITLE>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></TITLE>
28616 </HEAD>
28617 <BODY>
28618 <H1>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></H1>
28620 Normally Alpine adds a header line
28621 labeled "X-X-Sender", if the sender is
28622 different from the From: line.
28623 The standard specifies that this header
28624 line should be labeled "Sender", not "X-X-Sender".
28625 Setting this feature causes
28626 "Sender" to be used instead of "X-X-Sender".
28627 <P>
28628 See also <A HREF="h_config_disable_sender">"<!--#echo var="FEAT_disable-sender"-->"</A>.
28630 <P>
28631 <End of help on this topic>
28632 </BODY>
28633 </HTML>
28634 ====== h_config_use_fk =====
28635 <HTML>
28636 <HEAD>
28637 <TITLE>FEATURE: <!--#echo var="FEAT_use-function-keys"--></TITLE>
28638 </HEAD>
28639 <BODY>
28640 <H1>FEATURE: <!--#echo var="FEAT_use-function-keys"--></H1>
28642 This feature specifies that Alpine will respond to function keys instead of
28643 the normal single-letter commands. In this mode, the key menus at the
28644 bottom of each screen will show function key designations instead of the
28645 normal mnemonic key.
28647 <P>
28648 <End of help on this topic>
28649 </BODY>
28650 </HTML>
28651 ====== h_config_cancel_confirm =====
28652 <HTML>
28653 <HEAD>
28654 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></TITLE>
28655 </HEAD>
28656 <BODY>
28657 <H1>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></H1>
28659 This feature affects what happens when you type ^C to cancel a composition.
28660 By default, if you attempt to cancel a composition by typing ^C, you will be
28661 asked to confirm the cancellation by typing a "C"
28662 for <EM>C</EM>onfirm.
28663 It logically ought to be a "Y" for <EM>Y</EM>es, but that is
28664 risky because the "^C Y" needed to cancel a message
28665 is close (on the keyboard) to the "^X Y" needed to send a message.
28666 <P>
28667 If this feature is set the confirmation asked for
28668 will be a "<EM>Y</EM>es"
28669 instead of a "<EM>C</EM>onfirm" response.
28671 <P>
28672 <End of help on this topic>
28673 </BODY>
28674 </HTML>
28675 ====== h_config_compose_maps_del =====
28676 <HTML>
28677 <HEAD>
28678 <TITLE>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></TITLE>
28679 </HEAD>
28680 <BODY>
28681 <H1>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></H1>
28683 This feature affects the behavior of the DELETE key.
28684 If set, Delete will be equivalent to ^D, and delete
28685 the current character. Normally Alpine defines the Delete key
28686 to be equivalent to ^H, which deletes the <EM>previous</EM>
28687 character.
28689 <P>
28690 <End of help on this topic>
28691 </BODY>
28692 </HTML>
28693 ====== h_config_compose_bg_post =====
28694 <HTML>
28695 <HEAD>
28696 <TITLE>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></TITLE>
28697 </HEAD>
28698 <BODY>
28699 <H1>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></H1>
28701 This feature affects the behavior of Alpine's mail sending. If set, this
28702 feature enables a subcommand in the composer's "Send?" confirmation
28703 prompt. The subcommand allows you to tell Alpine to handle the actual
28704 posting in the background. While this feature usually allows posting
28705 to appear to happen very fast, it has no affect on the actual delivery
28706 time it takes a message to arrive at its destination.
28708 <P>
28709 Please Note:
28710 <OL>
28711 <LI>This feature will have no effect if the feature
28712 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A>
28713 is set.
28714 <LI>This feature isn't supported on all systems. All DOS and Windows,
28715 as well as several Unix ports, do not recognize this feature.
28716 <LI>Error handling is significantly different when this feature is
28717 enabled. Any message posting failure results in the message
28718 being appended to your "Interrupted" mail folder. When you
28719 type the <A HREF="h_common_compose">C</A>ompose command,
28720 Alpine will notice this folder and
28721 offer to extract any messages contained. Upon continuing a
28722 failed message, Alpine will display the nature of the failure
28723 in the status message line.
28724 <LI> <EM>WARNING</EM>: Under extreme conditions, it is possible
28725 for message data to
28726 get lost. <EM>Do</EM> <EM>not</EM> enable this feature
28727 if you typically run close to any sort of disk-space limits or quotas.
28728 </OL>
28729 <P>
28730 <End of help on this topic>
28731 </BODY>
28732 </HTML>
28733 ====== h_config_compose_dsn =====
28734 <HTML>
28735 <HEAD>
28736 <TITLE>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></TITLE>
28737 </HEAD>
28738 <BODY>
28739 <H1>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></H1>
28741 This feature affects the behavior of Alpine's mail sending. If set, this
28742 feature enables a subcommand in the composer's "Send?" confirmation
28743 prompt. The subcommand allows you to tell Alpine to request the type of
28744 Delivery Status Notification (DSN) that you would like. Most users will
28745 be happy with the default, and need not enable this feature.
28746 <P>
28747 If the feature
28748 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
28749 then this feature has no effect and the type of DSN is not selectable.
28751 <P>
28752 Turning on this feature and then turning on the DSNOpts from the send
28753 prompt reveals four on-off toggles at the bottom of the screen.
28754 The "X" command toggles between NoErrRets and ErrRets. NoErrRets requests
28755 that no notification be returned to you, even if there is a delivery
28756 failure. The "D" key toggles between Delay and NoDelay. This tells the
28757 server that you are willing (or not) to receive delay notifications, which
28758 happen when there is an unusual delay at some mail server (in that mail
28759 server's opinion). The "S" key toggles between Success and NoSuccess.
28760 Success requests that you be sent a DSN message when the message is
28761 successfully delivered to the recipients mailbox. Setting NoErrRets will
28762 automatically turn off Delay and Success notification, and will flip the
28763 toggles to show that. Similarly, turning on Delay and/or Success will
28764 automatically toggle the "X" key to ErrRets. The fourth command, the
28765 "H" key, toggles between RetHdrs and RetFull. RetFull requests that
28766 the full message be returned in any failed DSN. RetHdrs requests that
28767 only the headers be returned in any failed DSN. Notice that this command
28768 applies only to failed delivery status reports. For delay or success
28769 reports, the full message is never returned, only the headers are returned.
28771 <P>
28772 If you don't enable the DSN feature or if you don't turn it on for a
28773 particular message, the default is that you will be notified about failures,
28774 you might be notified about delays, and you won't be notified about
28775 successes. You will usually receive the full message back when there is
28776 a failure.
28778 <P>
28779 If you turn on the DSNOpts the default is to return as much information as
28780 possible to you. That is, by default, the Success and Delay options are
28781 turned on and the full message will be returned on failure.
28783 <P>
28784 The sending prompt will display the current DSN request (if any) in a
28785 shorthand form. It will be:
28787 <P><CENTER>[Never]</CENTER>
28789 <P>
28790 if you have requested NoErrRets. Otherwise, it will look something like:
28792 <P><CENTER>[FDS-Hdrs]</CENTER>
28794 <P>
28795 The "F" will always be there, indicating that you will be notified
28796 of failures. (Alpine doesn't provide a way to request no failure notification
28797 and at the same time request either success or delay notification. The only
28798 way to request no failure notifications is to request no notifications at
28799 all with NoErrRets.) The "D" and/or "S" will be present if you have
28800 requested Delay and/or Success notification. If one of those is missing,
28801 that means you are requesting no notification of the corresponding type.
28802 After the dash it will say either Hdrs or Full. Hdrs means to return only
28803 the headers and Full means to return the full message (applies to
28804 failure notifications only).
28806 <P>
28807 NOTE: This feature relies on your system's mail transport agent or
28808 configured
28809 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
28810 having the negotiation mechanism introduced in
28811 "Extended SMTP" (ESMTP) and the specific extension called
28812 "Delivery Status Notification" (DSN). If the mail tranport agent you
28813 are using doesn't support DSN, a short warning will be shown to you on
28814 the message line at the bottom of the screen after you send your message,
28815 but your message will have been sent anyway.
28817 <P>
28818 Note that DSNs don't provide a mechanism to request read receipts. That
28819 is, if you request notification on success you are notified when the
28820 message is delivered to the mailbox, not when the message is read.
28822 <P>
28823 ESMTP allows for graceful migration to upgraded mail transfer agents, but
28824 it is possible that this feature might cause problems for some servers.
28826 <P>
28827 <End of help on this topic>
28828 </BODY>
28829 </HTML>
28830 ====== h_config_auto_zoom =====
28831 <HTML>
28832 <HEAD>
28833 <TITLE>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></TITLE>
28834 </HEAD>
28835 <BODY>
28836 <H1>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></H1>
28838 This feature affects the behavior of the Select command.
28839 If set, the select command will automatically perform a zoom
28840 after the select is complete.
28841 This feature is set by default.
28842 <P>
28843 Some related help topics are
28844 <UL>
28845 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28846 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28847 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28848 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
28849 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
28850 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28851 </UL>
28853 <P>
28854 <End of help on this topic>
28855 </BODY>
28856 </HTML>
28857 ====== h_config_auto_unzoom =====
28858 <HTML>
28859 <HEAD>
28860 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></TITLE>
28861 </HEAD>
28862 <BODY>
28863 <H1>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></H1>
28865 This feature affects the behavior of the Apply command. If set, and if
28866 you are currently looking at a Zoomed Index view of selected messages,
28867 the Apply command will do the operation you specify, but then will
28868 implicitly do an "UnZoom", so that you will automatically be back in
28869 the normal Index view after the Apply.
28870 This feature is set by default.
28872 <P>
28873 Some related help topics are
28874 <UL>
28875 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28876 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28877 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28878 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
28879 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
28880 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28881 </UL>
28882 <P>
28883 <End of help on this topic>
28884 </BODY>
28885 </HTML>
28886 ====== h_config_auto_unselect =====
28887 <HTML>
28888 <HEAD>
28889 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></TITLE>
28890 </HEAD>
28891 <BODY>
28892 <H1>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></H1>
28894 This feature affects the behavior of the Apply command. If set,
28895 the Apply command will do the operation you specify, but then will
28896 implicitly do an "UnSelect All", so that you will automatically be back in
28897 the normal Index view after the Apply.
28899 <P>
28900 Some related help topics are
28901 <UL>
28902 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28903 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28904 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28905 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
28906 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
28907 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28908 </UL>
28909 <P>
28910 <End of help on this topic>
28911 </BODY>
28912 </HTML>
28913 ====== h_config_fast_recent =====
28914 <HTML>
28915 <HEAD>
28916 <TITLE>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></TITLE>
28917 </HEAD>
28918 <BODY>
28919 <H1>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></H1>
28921 This feature controls the behavior of the TAB key when traversing folders
28922 in the optional
28923 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28924 collection or in optional <!--#echo var="VAR_news-collections"-->.
28926 <P>
28927 When the TAB
28928 (<A HREF="h_common_nextnew">NextNew</A>)
28929 key is pressed, the default behavior is to
28930 explicitly examine the status of the folder for the number of recent
28931 messages (messages delivered since the last time it was viewed).
28932 Depending on the size and number of messages in the folder, this test
28933 can be time consuming.
28935 <P>
28936 Enabling this feature will cause Alpine to only test for the existence of
28937 any recent messages rather than to obtain the count. This is much faster
28938 in many cases. The downside is that you're not given the number of recent
28939 messages when prompted to view the next folder.
28940 If the feature
28941 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
28942 is turned on, then the present feature will have no effect.
28944 <P>
28945 <UL>
28946 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28947 </UL><P>
28948 <End of help on this topic>
28949 </BODY>
28950 </HTML>
28951 ====== h_config_arrow_nav =====
28952 <HTML>
28953 <HEAD>
28954 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></TITLE>
28955 </HEAD>
28956 <BODY>
28957 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></H1>
28959 This feature controls the behavior of the left and right arrow keys.
28960 If set, the left and right arrow keys will operate like the usual
28961 navigation keys < and >.
28962 This feature is set by default.
28964 <P>
28965 If you set this feature, and do not like the changed behavior of the up/down
28966 arrow
28967 keys when navigating through the FOLDER LIST screen --
28968 <B>first</B> from column to column, if more than one folder is
28969 displayed per row,
28970 and <B>then</B> from row to row -- you may either also wish to set the feature
28971 "<A HREF="h_config_relaxed_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></A>",
28972 "<A HREF="h_config_single_list"><!--#echo var="FEAT_single-column-folder-list"--></A>", or
28973 use the ^P/^N (instead of up/down arrow) keys to move up/down the list of
28974 folders in each column.
28975 <P>
28976 <UL>
28977 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28978 </UL><P>
28979 <End of help on this topic>
28980 </BODY>
28981 </HTML>
28982 ====== h_config_relaxed_arrow_nav =====
28983 <HTML>
28984 <HEAD>
28985 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></TITLE>
28986 </HEAD>
28987 <BODY>
28988 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></H1>
28990 This feature controls the behavior of the left, right, up and down
28991 arrow keys in the FOLDER LIST screen when the "<A
28992 HREF="h_config_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation"--></A>" feature is
28993 set.
28994 This feature is set by default.
28996 <P>
28998 When this feature is set, the left and right
28999 arrow keys in the FOLDER LIST screen
29000 move the highlight bar to the left or right, and the up and
29001 down arrows move it up or down.
29003 <P>
29004 When the "<!--#echo var="FEAT_enable-arrow-navigation"-->" feature is set and this
29005 feature is not set;
29006 the left and right arrow keys in the Folder List screen strictly
29007 track the commands bound to the '<' and '>' keys, and the up
29008 and down arrow keys move the highlight bar to the previous and next
29009 folder or directory name.
29011 <P>
29012 <UL>
29013 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29014 </UL><P>
29015 <End of help on this topic>
29016 </BODY>
29017 </HTML>
29018 ====== h_config_alt_compose_menu =====
29019 <HTML>
29020 <HEAD>
29021 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></TITLE>
29022 </HEAD>
29023 <BODY>
29024 <H1>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></H1>
29026 This feature controls the menu that is displayed when Compose is selected.
29027 If set, a list of options will be presented, with each option representing
29028 the type of composition that could be used. This feature is most useful for
29029 users who want to avoid being prompted with each option separately, or who
29030 want to avoid the checking of remote postponed or form letter folders.
29031 The possible types of composition are:
29033 <P>
29034 New, for starting a new composition. Note that if New is selected and roles
29035 are set, roles are checked for matches and applied according to the setting
29036 of the matching role.
29038 <P>
29039 Interrupted, for continuing an interrupted composition. This option is only
29040 offered if an interrupted message folder is detected.
29042 <P>
29043 Postponed, for continuing postponed compositions. This option is offered
29044 if a <!--#echo var="VAR_postponed-folder"--> is set in the config REGARDLESS OF whether or not
29045 the postponed folder actually exists. This option is especially handy
29046 for avoiding having to check for the existence of a remote postponed folder.
29048 <P>
29049 Form, for using form letters. This option is offered if the <!--#echo var="VAR_form-letter-folder"-->
29050 is set in the config, and is not checked for existence for reasons similar
29051 to those explained by the postponed option.
29053 <P>
29054 setRole, for selecting a role to apply to a composition.
29056 <P>
29057 <End of help on this topic>
29058 </BODY>
29059 </HTML>
29060 ====== h_config_alt_role_menu =====
29061 <HTML>
29062 <HEAD>
29063 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></TITLE>
29064 </HEAD>
29065 <BODY>
29066 <H1>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></H1>
29068 Normally the <A HREF="h_common_role">Role Command</A> allows you to choose
29069 a role and compose a new message using that role.
29070 When this feature is set, the role command will first ask whether you want to
29071 Compose a new message, Forward the current message, Reply to the
29072 current message, or Bounce the current message.
29073 If you are not in the MESSAGE INDEX and are not viewing a message,
29074 then there is no current message and the question will be skipped.
29075 After you have chosen to Compose, Forward, Reply, or Bounce you will
29076 then choose the role to be used.
29077 <P>
29078 When Bouncing the "Set From" address is used for the
29079 Resent-From header, the "Set Fcc" value is used for the Fcc
29080 provided that the option
29081 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A> is turned on,
29082 and the "Use SMTP Server" value is used for the SMTP server, if
29083 set.
29084 Other actions of the role are ignored when Bouncing.
29086 <P>
29087 <End of help on this topic>
29088 </BODY>
29089 </HTML>
29090 ====== h_config_always_spell_check =====
29091 <HTML>
29092 <HEAD>
29093 <TITLE>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></TITLE>
29094 </HEAD>
29095 <BODY>
29096 <H1>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></H1>
29097 <P>
29098 When this feature is set, every composed message will be spell-checked before
29099 being sent.
29100 <P>
29101 <End of help on this topic>
29102 </BODY>
29103 </HTML>
29104 ====== h_config_quell_asterisks =====
29105 <HTML>
29106 <HEAD>
29107 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></TITLE>
29108 </HEAD>
29109 <BODY>
29110 <H1>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></H1>
29111 <P>
29112 When you are running Alpine you will sometimes be asked for a password
29113 in a prompt on the third line from the bottom of the screen.
29114 Normally each password character you type will cause an asterisk to echo
29115 on the screen. That gives you some feedback to know that your typing is
29116 being recognized.
29117 There is a very slight security risk in doing it this way because someone
29118 watching over your shoulder might be able to see how many characters there
29119 are in your password.
29120 If you'd like to suppress the echoing of the asterisks set this feature.
29121 <P>
29122 <End of help on this topic>
29123 </BODY>
29124 </HTML>
29125 ====== h_config_quell_flowed_text =====
29126 <HTML>
29127 <HEAD>
29128 <TITLE>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></TITLE>
29129 </HEAD>
29130 <BODY>
29131 <H1>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></H1>
29132 <P>
29133 Alpine generates flowed text where possible.
29134 The method for generating flowed text is defined by
29135 <A HREF="http://www.ietf.org/rfc/rfc3676.txt">RFC 3676</A>,
29136 the benefit of doing so is
29137 to send message text that can properly be viewed both on normal width displays
29138 and on displays with smaller or larger than normal screen widths.
29139 With flowed text, a space at the end of a line tells the receiving mail
29140 client that the following line belongs to the same paragraph.
29141 Quoted text will also be affected, with only the innermost
29142 level of ">" quoting being followed by a space.
29143 However, if you have changed the
29144 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29145 so that it is not equal to the default value of "> ", then
29146 quoted text will not be flowed.
29147 For this reason, we recommend that you leave your
29148 "<!--#echo var="VAR_reply-indent-string"-->" set to the default.
29149 <P>
29150 This feature turns off the generation of flowed text, as it might be
29151 desired to more tightly control how a message is displayed on the receiving end.
29152 <P>
29153 If this feature is <EM>not</EM> set, you can control on a message by message
29154 basis whether or not flowed text is generated.
29155 You do this by typing ^V at the Send confirmation prompt that you get
29156 after typing ^X to send a message.
29157 ^V is a toggle that turns flowing off and back on if typed again.
29158 If for some reason flowing cannot be done on a particular message, then the
29159 ^V command will not be available.
29160 This would be the case, for example, if this feature was set, or if your
29161 "<!--#echo var="VAR_reply-indent-string"-->" was set to a non-default value.
29162 If the feature
29163 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
29164 then the opportunity to control on a message by message basis
29165 whether or not flowed text is generated is lost.
29166 <P>
29167 When this feature is not set and you have typed ^V to turn off flowing,
29168 the Send confirmation prompt will change to look like
29169 <P>
29170 <CENTER><SAMP>Send message (not flowed)?</SAMP></CENTER>
29171 <P>
29172 <A HREF="h_config_strip_ws_before_send">"<!--#echo var="FEAT_strip-whitespace-before-send"-->"</A> will
29173 also turn off the sending of flowed text messages, but it differs in that
29174 it also trims all trailing white space from a message before sending it.
29175 <P>
29176 If alternate editors are used extensively, be aware that a message will still
29177 be sent flowed if this feature is unset. In most cases this will be fine,
29178 but if the editor has a "flowed text" mode, it would be best to
29179 use that.
29180 <P>
29181 <End of help on this topic>
29182 </BODY>
29183 </HTML>
29184 ====== h_config_strip_ws_before_send =====
29185 <HTML>
29186 <HEAD>
29187 <TITLE>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></TITLE>
29188 </HEAD>
29189 <BODY>
29190 <H1>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></H1>
29191 <P>
29192 By default, trailing whitespace is not stripped from
29193 a message before sending. Trailing whitespace should have no effect on an
29194 email message, and in flowed text can aid in delimiting paragraphs.
29195 However, the old behavior of stripping trailing whitespace was in place
29196 to better deal with older clients that couldn't handle certain types of
29197 text encodings. This feature restores the old behavior
29198 <P>
29199 Trailing whitespace is of aid to flowed-text-formatted messages, which are
29200 generated by default but can be turned off via the
29201 <A HREF="h_config_quell_flowed_text">"<!--#echo var="FEAT_quell-flowed-text"-->"</A> feature.
29202 <!--#echo var="FEAT_strip-whitespace-before-send"--> also has the effect of turning off sending
29203 of flowed text.
29204 <P>
29205 <End of help on this topic>
29206 </BODY>
29207 </HTML>
29208 ====== h_config_del_from_dot =====
29209 <HTML>
29210 <HEAD>
29211 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></TITLE>
29212 </HEAD>
29213 <BODY>
29214 <H1>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></H1>
29216 This feature controls the behavior of the Ctrl-K command in the composer.
29217 If set, ^K will cut from the current cursor position to the end of the line,
29218 rather than cutting the entire line.
29220 <P>
29221 <End of help on this topic>
29222 </BODY>
29223 </HTML>
29224 ====== h_config_print_index =====
29225 <HTML>
29226 <HEAD>
29227 <TITLE>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></TITLE>
29228 </HEAD>
29229 <BODY>
29230 <H1>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></H1>
29232 This feature controls the behavior of the Print command when in the
29233 MESSAGE INDEX screen. If set, the print command will give you a prompt
29234 asking if you wish to print the message index, or the currently highlighted
29235 message. If not set, the message will be printed.
29237 <P>
29238 <End of help on this topic>
29239 </BODY>
29240 </HTML>
29241 ====== h_config_allow_talk =====
29242 <HTML>
29243 <HEAD>
29244 <TITLE>FEATURE: <!--#echo var="FEAT_allow-talk"--></TITLE>
29245 </HEAD>
29246 <BODY>
29247 <H1>FEATURE: <!--#echo var="FEAT_allow-talk"--></H1>
29249 UNIX Alpine only.
29250 <P>
29251 By default, permission for others to "talk" to your terminal is turned
29252 off when you are running Alpine. When this feature is set, permission is
29253 instead turned on. If enabled, you may see unexpected messages in the
29254 middle of your Alpine screen from someone attempting to contact you via the
29255 "talk" program.
29257 <P>
29258 NOTE: The "talk" program has nothing to do with Alpine or email. The
29259 talk daemon on your system will attempt to print a message on your screen
29260 when someone else is trying to contact you. If you wish to see these
29261 messages while you are running Alpine, you should enable this feature.
29263 <P>
29264 If you do enable this feature and see a "talk" message, you must
29265 suspend or quit Alpine before you can respond.
29267 <P>
29268 <End of help on this topic>
29269 </BODY>
29270 </HTML>
29271 ====== h_config_send_filter_dflt =====
29272 <HTML>
29273 <HEAD>
29274 <TITLE>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></TITLE>
29275 </HEAD>
29276 <BODY>
29277 <H1>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></H1>
29278 If you have <A HREF="h_config_sending_filter">"<!--#echo var="VAR_sending-filters"-->"</A>
29279 configured, setting this feature will cause
29280 the first filter in the <!--#echo var="VAR_sending-filters"--> list to be offered as the default
29281 instead of unfiltered, the usual default.
29282 <P>
29283 <UL>
29284 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29285 </UL><P>
29286 <End of help on this topic>
29287 </BODY>
29288 </HTML>
29289 ====== h_config_custom_print =====
29290 <HTML>
29291 <HEAD>
29292 <TITLE>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></TITLE>
29293 </HEAD>
29294 <BODY>
29295 <H1>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></H1>
29297 When this feature is set, the print command will have an additional
29298 subcommand called "C CustomPrint". If selected, you will have
29299 the opportunity to enter any system print command --instead of being
29300 restricted to using those that have been previously configured in the
29301 printer setup menu.
29302 <P>
29304 <End of help on this topic>
29305 </BODY>
29306 </HTML>
29307 ====== h_config_enable_dot_files =====
29308 <HTML>
29309 <HEAD>
29310 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></TITLE>
29311 </HEAD>
29312 <BODY>
29313 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></H1>
29315 When this feature is set, files beginning with dot (".") will be
29316 visible in the file browser. For example, you'll be able to select them
29317 when using the browser to add an attachment to a message.
29318 <P>
29319 <End of help on this topic>
29320 </BODY>
29321 </HTML>
29322 ====== h_config_enable_dot_folders =====
29323 <HTML>
29324 <HEAD>
29325 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></TITLE>
29326 </HEAD>
29327 <BODY>
29328 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></H1>
29330 When this feature is set, folders beginning with dot (".") may be added
29331 and viewed.
29332 <P>
29333 <End of help on this topic>
29334 </BODY>
29335 </HTML>
29336 ====== h_config_ff_between_msgs =====
29337 <HTML>
29338 <HEAD>
29339 <TITLE>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></TITLE>
29340 </HEAD>
29341 <BODY>
29342 <H1>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></H1>
29344 Setting this feature causes a formfeed to be printed between messages when
29345 printing multiple messages (with Apply Print command).
29346 <P>
29347 <End of help on this topic>
29348 </BODY>
29349 </HTML>
29350 ====== h_config_blank_keymenu =====
29351 <HTML>
29352 <HEAD>
29353 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></TITLE>
29354 </HEAD>
29355 <BODY>
29356 <H1>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></H1>
29358 If this feature is set the command key menu that normally appears on the
29359 bottom two lines of the screen will not usually be there. Asking for
29360 help with ^G or ? will cause the key menu to appear instead of causing
29361 the help message to come up. If you want to actually see the help text,
29362 another ^G or ? will show it to you. After the key menu has popped
29363 up with the help key it will remain there for an O for Other command but
29364 disappear if any other command is typed.
29365 <P>
29366 <End of help on this topic>
29367 </BODY>
29368 </HTML>
29369 ====== h_config_enable_mouse =====
29370 <HTML>
29371 <HEAD>
29372 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></TITLE>
29373 </HEAD>
29374 <BODY>
29375 <H1>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></H1>
29377 This feature controls whether or not an X terminal mouse can be used with
29378 Alpine. If set, and the $DISPLAY variable indicates that an X terminal is
29379 being used, the left mouse button on the mouse can be used to select text
29380 or commands.
29381 Clicking on a command at the bottom of the screen will behave as if you had
29382 typed that command.
29383 Clicking on an index line will move the current message highlight to
29384 that line.
29385 Double-clicking on an index line will view the message.
29386 Double-clicking on a link will view the link.
29387 <P>
29388 This type of mouse support will also work in some terminal emulators which are
29389 not actually X terminals, but which have extra code to support the xterm
29390 style mouse.
29391 For those emulators you not only need to turn this feature on but you also
29392 have to set the $DISPLAY environment variable even though it isn't needed
29393 for your terminal.
29394 That will cause Alpine to think that it is an xterm and to properly interpret the
29395 escape sequences sent by the mouse.
29396 <P>
29397 Note: if this feature is set, the behavior of X terminal cut-and-paste is
29398 also modified. It is sometimes possible to hold the shift key down while clicking
29399 left or middle mouse buttons for the normal xterm cut/paste operations.
29400 There is also an Alpine command to toggle this mode on or off.
29401 The command is Ctrl-\ (Control-backslash).
29402 <P>
29403 <End of help on this topic>
29404 </BODY>
29405 </HTML>
29406 ====== h_config_enable_xterm_newmail =====
29407 <HTML>
29408 <HEAD>
29409 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></TITLE>
29410 </HEAD>
29411 <BODY>
29412 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></H1>
29414 This feature controls whether or not Alpine will attempt to announce new
29415 mail arrival when it is running in an X terminal window and that window
29416 is iconified. If set, and the $DISPLAY variable indicates that an X
29417 terminal is being used, Alpine will send appropriate escape sequences to
29418 the X terminal to modify the label on Alpine's icon to indicate that new
29419 mail has arrived. Alpine will also modify the Alpine window's title to
29420 indicate new mail.
29421 See also <a href="h_config_enable_newmail_short_text"><!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>.
29422 <P>
29423 <End of help on this topic>
29424 </BODY></HTML>
29425 ====== h_config_enable_newmail_short_text =====
29426 <HTML>
29427 <HEAD>
29428 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></TITLE>
29429 </HEAD>
29430 <BODY>
29431 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></H1>
29433 This feature controls the text to be displayed in an icon in the event
29434 of a new message arrival. Normally, the message will
29435 be the one that is displayed on the screen. This feature shortens the
29436 message to a count of the number of new messages in brackets. This may be
29437 more useful for those who use the window's title bar in the task bar as a
29438 new mail indicator. This feature is only useful if the
29439 <A HREF="h_config_enable_xterm_newmail"><!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></A>
29440 feature is also set. Like the <!--#echo var="FEAT_enable-newmail-in-xterm-icon"-->
29441 feature, this feature is only relevant when run in an xterm environment.
29442 <P>
29443 <End of help on this topic>
29444 </BODY></HTML>
29445 ====== h_config_copy_to_to_from =====
29446 <HTML>
29447 <HEAD>
29448 <TITLE>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></TITLE>
29449 </HEAD>
29450 <BODY>
29451 <H1>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></H1>
29453 This feature affects the From address used when Replying to a message.
29454 It is probably only useful if you have some
29455 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
29456 defined.
29457 When enabled, it checks to see if any of the addresses in the To or Cc
29458 fields of the message you are replying to is one of your addresses.
29459 If it is, and there is only one of them, then that address is used as
29460 the From address in the message you are composing.
29461 In other words, you will be using a From address that is the same
29462 as the To address that was used to get the mail to you in the first place.
29464 <P>
29465 If a role is being used and it has a From address defined, that From address will
29466 be used rather than the one derived from this feature.
29468 <P>
29469 <UL>
29470 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29471 </UL><P>
29472 <End of help on this topic>
29473 </BODY>
29474 </HTML>
29475 ====== h_config_prefix_editing =====
29476 <HTML>
29477 <HEAD>
29478 <TITLE>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></TITLE>
29479 </HEAD>
29480 <BODY>
29481 <H1>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></H1>
29483 This feature affects the Reply command's "Include original message
29484 in Reply?" prompt. When enabled, it causes the
29485 "Edit Indent String" sub-command to appear which allows
29486 you to edit the string Alpine would otherwise use to denote included
29487 text from the message being replied to.<P>
29489 Thus, you can change Alpine's default message quote character (usually
29490 an angle bracket) on a per message basis. So you could change your quoted message to
29491 look, for example, like this:<p>
29493 <pre>On Tues, 26 Jan 1999, John Q. Smith wrote:
29495 John: I just wanted to say hello and to congratulate you
29496 John: on a job well done!</pre><p>
29498 The configuration option
29499 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29500 may be used to change what appears as the default string to be edited.
29501 <P>
29502 NOTE: Edited <!--#echo var="VAR_reply-indent-string"--> only apply to the message
29503 currently being replied to.
29504 <P>
29505 If you change your <!--#echo var="VAR_reply-indent-string"-->
29506 so that it is not equal to the default value of "> ", then
29507 quoted text will not be flowed
29508 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
29509 when you reply.
29510 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
29511 set to the default value.
29512 <P>
29513 <UL>
29514 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29515 </UL><P>
29516 <End of help on this topic>
29517 </BODY>
29518 </HTML>
29519 ====== h_config_enable_search_and_repl =====
29520 <HTML>
29521 <HEAD>
29522 <TITLE>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></TITLE>
29523 </HEAD>
29524 <BODY>
29525 <H1>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></H1>
29527 This feature modifies the behavior of Alpine's composer. Setting this
29528 feature causes Alpine to offer the "^R Replace" subcommand, which
29529 allows you to search and replace text strings in a message you are composing,
29530 inside the "^W Where is" command.
29532 <P>
29534 To search and replace text, first enter the text to be replaced at the
29535 "Search: " prompt. Then, rather than pressing Enter to just search for that
29536 text, press ^R, which turns the prompt into
29538 <P>
29540 Search (to replace):
29542 <P>
29544 and then press Enter. The cursor will highlight the first occurrence
29545 of the text string you entered, and the prompt will show:
29547 <P>
29549 Replace "<your text string>" with :
29551 <P>
29553 where <your text string> is what you entered at the previous prompt;
29554 here, enter the replacement text. To only replace the highlighted
29555 occurrence, simply press Enter now; to replace all occurrences in the
29556 message, press ^X (Repl All), then Enter. You will then be asked to confirm
29557 each replacement.
29559 <P>
29561 The command ^R toggles between "Replace" and "Don't Replace"; its subcommand
29562 ^X toggles between "Replace All" and "Replace One."
29564 <P>
29566 If you previously searched for text in a message, it will be offered for
29567 re-use as part of the prompt, shown in [ ] brackets.
29569 <P>
29570 <End of help on this topic>
29571 </BODY>
29572 </HTML>
29573 ====== h_config_enable_view_attach =====
29574 <HTML>
29575 <HEAD>
29576 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></TITLE>
29577 </HEAD>
29578 <BODY>
29579 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></H1>
29581 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29582 Setting this feature causes Alpine to present attachments in boldface.
29583 The first available attachment is displayed in inverse. This is the
29584 "selected" attachment. Pressing RETURN will cause Alpine to display
29585 the selected attachment. Use the arrow keys to change which of the
29586 attachments displayed in boldface is the current selection.
29588 <P>
29590 Speaking of arrow keys, the Up and Down Arrows will select the next
29591 and previous attachments if one is available on the screen for selection.
29592 Otherwise, they will simply adjust the viewed text one line up or down.
29594 <P>
29596 Similarly, when selectable items are present in a message, the Ctrl-F key
29597 can be used to select the next item in the message independent of which
29598 portion of the viewed message is currently displayed. The Ctrl-B key can
29599 be used to select the previous item in the same way.
29600 <P>
29601 <End of help on this topic>
29602 </BODY>
29603 </HTML>
29604 ====== h_config_enable_y_print =====
29605 <HTML>
29606 <HEAD>
29607 <TITLE>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></TITLE>
29608 </HEAD>
29609 <BODY>
29610 <H1>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></H1>
29612 This feature modifies the behavior of Alpine's Print command.
29613 <P>
29614 By default, Alpine's print command is available by pressing the "%" key.
29615 (This command is a substantial change from Pine versions before 4.00 --
29616 where the print command was "Y" -- based on numerous complaints about
29617 printing being invoked inadvertently, since Y also means "Yes.")
29619 <P>
29621 This feature is supplied to mitigate any disruption or anxiety users
29622 might feel as a result of this change.
29624 <P>
29626 Enabling this feature will cause Alpine to recognize both the old
29627 command, "Y" for Prynt, as well the new "%" method for invoking
29628 printing. Note, key menu labels are not changed as a result of
29629 enabling this feature.
29631 <P>
29633 <End of help on this topic>
29634 </BODY>
29635 </HTML>
29636 ====== h_config_enable_lessthan_exit =====
29637 <HTML>
29638 <HEAD>
29639 <TITLE>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></TITLE>
29640 </HEAD>
29641 <BODY>
29642 <H1>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></H1>
29644 If this feature is set, then on screens where there is an Exit command
29645 but no < command, the < key will perform the same function as the Exit
29646 command.
29647 This feature is set by default.
29648 <P>
29649 <End of help on this topic>
29650 </BODY>
29651 </HTML>
29652 ====== h_config_enable_view_url =====
29653 <HTML>
29654 <HEAD>
29655 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></TITLE>
29656 </HEAD>
29657 <BODY>
29658 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></H1>
29659 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29660 When this feature is set (the default) Alpine will select possible URLs from the
29661 displayed text and display them in boldface for selection.
29662 <P>
29663 The first available URL is displayed in inverse. This is the
29664 "selected" URL. Pressing RETURN will cause Alpine to display
29665 the selected URL via either built-in means as with mailto:, imap:,
29666 news:, and nntp:, or via an external application as defined
29667 by the <A HREF="h_config_browser">"url-viewer"</A>
29668 variable.
29669 <P>
29670 Use the arrow keys to change which of the URLs displayed in boldface
29671 is the current selection.
29672 <P>
29673 Speaking of arrow keys, the Up and Down Arrows will select the next
29674 and previous URL if one is available on the screen for selection (unless
29675 you have set the feature
29676 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
29677 Otherwise, they will simply adjust the viewed text one line up or down.
29678 <P>
29679 Similarly, when selectable items are present in a message, the Ctrl-F
29680 key can be used to select the next item in the message independent
29681 of which portion of the viewed message is currently displayed. The
29682 Ctrl-B key can be used to select the previous item in the same way.
29683 <P>
29684 <UL>
29685 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29686 </UL><P>
29687 <End of help on this topic>
29688 </BODY>
29689 </HTML>
29690 ====== h_config_enable_view_web_host =====
29691 <HTML>
29692 <HEAD>
29693 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></TITLE>
29694 </HEAD>
29695 <BODY>
29696 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></H1>
29698 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29699 When this feature is set (the default) Alpine will select possible web hostnames
29700 from the displayed text and display them in boldface for selection.
29701 This can be useful when you receive messages referencing World Wide Web
29702 sites without the use of complete URLs; for example, specifying only
29703 "www.patches.freeiz.com/alpine/" (which will <B>not</B> become a
29704 selectable
29705 item by setting <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>)
29706 rather than explicitly
29707 "http://www.patches.freeiz.com/alpine/".
29708 <P>
29709 The first available hostname is displayed in inverse. This is the
29710 "selected" hostname. Pressing RETURN will cause Alpine to display
29711 the selected hostname via an external application as defined
29712 by the <A HREF="h_config_browser">"url-viewer"</A>
29713 variable.
29714 <P>
29715 Use the arrow keys (unless you have set the feature
29716 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
29717 to change which of the hostnames displayed in
29718 boldface is the current selection.
29719 <P>
29720 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
29721 key can be used to select the next web hostname in the message independent
29722 of which portion of the viewed message is currently displayed. The
29723 Ctrl-B key can be used to select the previous web hostnames in the same way.
29724 <P>
29725 <UL>
29726 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29727 </UL><P>
29728 <End of help on this topic>
29729 </BODY>
29730 </HTML>
29731 ====== h_config_enable_view_addresses =====
29732 <HTML>
29733 <HEAD>
29734 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></TITLE>
29735 </HEAD>
29736 <BODY>
29737 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></H1>
29739 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29740 Setting this feature causes Alpine to select possible email addresses
29741 from the displayed text and display them in boldface for selection.
29743 <P>
29744 The first available email address is displayed in inverse. This is the
29745 "selected" address. Pressing RETURN will cause Alpine to enter
29746 the message composition screen with the To: field filled in with the
29747 selected address.
29748 <P>
29749 Use the arrow keys (unless you have set the feature
29750 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
29751 to change which of the hostnames displayed in
29752 boldface is the current selection.
29753 <P>
29754 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
29755 key can be used to select the next web hostname in the message independent
29756 of which portion of the viewed message is currently displayed. The
29757 Ctrl-B key can be used to select the previous web hostnames in the same way.
29758 <P>
29759 <UL>
29760 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29761 </UL><P>
29762 <End of help on this topic>
29763 </BODY>
29764 </HTML>
29765 ====== h_config_enable_view_arrows =====
29766 <HTML>
29767 <HEAD>
29768 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></TITLE>
29769 </HEAD>
29770 <BODY>
29771 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></H1>
29773 This feature modifies Up and Down arrow key behavior in Alpine's
29774 MESSAGE TEXT screen when selectable Attachments, URL's, or
29775 web-hostnames are presented. Alpine's usual behavior is to move to
29776 the next or previous selectable item if currently displayed or
29777 simply to adjust the screen view by one line.
29779 <P>
29781 Setting this feature causes the UP and Down arrow key to behave as
29782 if no selectable items were present in the message.
29784 <P>
29786 Note, the Ctrl-F (next selectable item) and Ctrl-B (previous selectable
29787 item) functionality is unchanged.
29788 <P>
29790 <End of help on this topic>
29791 </BODY>
29792 <HTML>
29793 ====== h_config_quell_charset_warning =====
29794 <HTML>
29795 <HEAD>
29796 <TITLE>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></TITLE>
29797 </HEAD>
29798 <BODY>
29799 <H1>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></H1>
29801 By default, if the message you are viewing contains characters that are
29802 not representable in your
29803 <A HREF="h_config_char_set">"Display Character Set"</A>
29804 then Alpine will
29805 add a warning to the start of the displayed text.
29806 If this option is set, then that editorial message will be suppressed.
29807 <P>
29808 Setting this feature also suppresses the comment about the character set
29809 in header lines.
29810 For example, when viewing a message you might see
29811 <P>
29812 <CENTER><SAMP>From: "[ISO-8859-2] Name" <address></SAMP></CENTER>
29813 <P>
29814 in the From header if your Character-Set is something other than ISO-8859-2.
29815 If you set this feature, the comment about the character set will
29816 no longer be there.
29817 <P>
29818 <End of help on this topic>
29819 </BODY>
29820 </HTML>
29821 ====== h_config_quell_host_after_url =====
29822 <HTML>
29823 <HEAD>
29824 <TITLE>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></TITLE>
29825 </HEAD>
29826 <BODY>
29827 <H1>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></H1>
29829 By default, links in HTML text are displayed with the host the link
29830 references appended, within square brackets, to the link text. Alpine
29831 does this to help indicate where a link will take you, particularly when
29832 the link text might suggest a different destination.
29834 <P>
29835 Setting this feature will prevent the server name from being appended
29836 to the displayed text.
29838 <P>
29839 <End of help on this topic>
29840 </BODY>
29841 </HTML>
29842 ====== h_config_prefer_plain_text =====
29843 <HTML>
29844 <HEAD>
29845 <TITLE>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></TITLE>
29846 </HEAD>
29847 <BODY>
29848 <H1>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></H1>
29850 A message being viewed may contain alternate versions of the same content.
29851 Those alternate versions are supposed to be ordered by the sending software such that the
29852 first alternative is the least preferred and the last alternative is the
29853 most preferred. Alpine will normally display the most-preferred version that
29854 it knows how to display. This is most often encountered where the two
29855 alternate versions are a plain text version and an HTML version, with the
29856 HTML version listed last as the most preferred.
29857 <P>
29858 If this option is set, then any plain text version will be preferred to
29859 all other versions.
29860 <P>
29861 When viewing a message there is a command "A TogglePreferPlain",
29862 which will temporarily change the sense of this option.
29863 If this option is set you will first see the plain text version of a
29864 message.
29865 If you then type the "A" command, you will see the most preferred version,
29866 most likely HTML, instead.
29867 Typing the "A" command a second time will switch it back.
29868 Alternatively, if the present option is not set you will originally see
29869 the most preferred version of the message and typing "A" will switch to
29870 the plain text version.
29871 <P>
29872 <End of help on this topic>
29873 </BODY>
29874 </HTML>
29875 ====== h_config_pass_control =====
29876 <HTML>
29877 <HEAD>
29878 <TITLE>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></TITLE>
29879 </HEAD>
29880 <BODY>
29881 <H1>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></H1>
29883 It is probably not useful to set this option.
29884 This is a legacy option left behind "just in case".
29885 Multi-byte characters that have an octet that has the same
29886 value as a control character are permitted through whether or not
29887 this option is turned on.
29888 <P>
29889 This feature controls how certain characters contained in messages are
29890 displayed.
29891 If set, all characters in a message will be sent to the
29892 screen. Normally, control characters are displayed as shown below to
29893 avoid a garbled screen and to
29894 avoid inadvertently changing terminal setup parameters.
29895 Control characters are usually displayed as two character sequences like
29896 <P><CENTER><SAMP> ^C </SAMP></CENTER><P>
29897 for Control-C,
29898 <P><CENTER><SAMP> ^[ </SAMP></CENTER><P>
29899 for ESCAPE,
29900 <P><CENTER><SAMP> ^? </SAMP></CENTER><P>
29901 for DELETE, and
29902 <P><CENTER><SAMP> ~E </SAMP></CENTER><P>
29903 for the character with value 133 (0x85).
29904 (The DEL character is displayed as ^?, regular control characters are displayed
29905 as the character ^ followed by the character obtained by adding the
29906 five low-order bits of the character to 0x40, and the C1
29907 control characters 0x80 - 0x9F are displayed as the character ~ followed by the
29908 character obtained by adding the
29909 five low-order bits of the character to 0x40.)
29910 Sometimes, in cases where changing a single control character into a
29911 two-character sequence would confuse Alpine's display routines,
29912 a question mark is substituted for the control character.
29913 <P>
29914 If you wish to filter out regular control characters but pass the
29915 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
29916 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.
29917 <P>
29918 <End of help on this topic>
29919 </BODY>
29920 </HTML>
29921 ====== h_config_pass_c1_control =====
29922 <HTML>
29923 <HEAD>
29924 <TITLE>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></TITLE>
29925 </HEAD>
29926 <BODY>
29927 <H1>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></H1>
29929 It is probably not useful to set this option.
29930 This is a legacy option left behind "just in case".
29931 Multi-byte characters that have an octet that has the same
29932 value as a control character are permitted through whether or not
29933 this option is turned on.
29934 <P>
29935 If the feature <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
29936 is set, then this feature has no effect.
29937 However, if you wish to filter out regular control characters but pass the
29938 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
29939 you may leave <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
29940 unset and set this feature.
29941 <P>
29942 <End of help on this topic>
29943 </BODY>
29944 </HTML>
29945 ====== h_config_fcc_on_bounce =====
29946 <HTML>
29947 <HEAD>
29948 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></TITLE>
29949 </HEAD>
29950 <BODY>
29951 <H1>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></H1>
29953 This feature controls an aspect of Alpine's behavior when bouncing a
29954 message. If set, normal FCC ("File Carbon Copy") processing will be
29955 done, just as if you had composed a message to the address you are
29956 bouncing to. If not set, no FCC of the message will be saved.
29957 <P>
29958 <End of help on this topic>
29959 </BODY>
29960 </HTML>
29961 ====== h_config_show_cursor =====
29962 <HTML>
29963 <HEAD>
29964 <TITLE>FEATURE: <!--#echo var="FEAT_show-cursor"--></TITLE>
29965 </HEAD>
29966 <BODY>
29967 <H1>FEATURE: <!--#echo var="FEAT_show-cursor"--></H1>
29969 This feature controls an aspect of Alpine's displays. If set, the system
29970 cursor will move to convenient locations in the displays. For example,
29971 to the beginning of the status field of the highlighted index line, or
29972 to the highlighted word after a successful WhereIs command. It is intended
29973 to draw your attention to an "interesting" spot on the screen.
29974 <P>
29975 <End of help on this topic>
29976 </BODY>
29977 </HTML>
29978 ====== h_config_sort_fcc_alpha =====
29979 <HTML>
29980 <HEAD>
29981 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></TITLE>
29982 </HEAD>
29983 <BODY>
29984 <H1>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></H1>
29986 This feature controls an aspect of Alpine's FOLDER LIST screen.
29987 If set, the default Fcc folder will be sorted alphabetically with the other
29988 folders instead of appearing right after the INBOX.
29989 <P>
29990 <End of help on this topic>
29991 </BODY>
29992 </HTML>
29993 ====== h_config_sort_save_alpha =====
29994 <HTML>
29995 <HEAD>
29996 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></TITLE>
29997 </HEAD>
29998 <BODY>
29999 <H1>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></H1>
30001 This feature controls an aspect of Alpine's FOLDER LIST screen.
30002 If set, the default save folder will be sorted alphabetically with the other
30003 folders instead of appearing right after the INBOX (and default FCC folder).
30004 <P>
30005 <End of help on this topic>
30006 </BODY>
30007 </HTML>
30008 ====== h_config_single_list =====
30009 <HTML>
30010 <HEAD>
30011 <TITLE>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></TITLE>
30012 </HEAD>
30013 <BODY>
30014 <H1>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></H1>
30016 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
30017 the folders will be listed one per line instead of several per line
30018 in the FOLDER LIST display.
30019 <P>
30020 <End of help on this topic>
30021 </BODY>
30022 </HTML>
30023 ====== h_config_vertical_list =====
30024 <HTML>
30025 <HEAD>
30026 <TITLE>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></TITLE>
30027 </HEAD>
30028 <BODY>
30029 <H1>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></H1>
30031 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
30032 the folders will be listed alphabetically down the columns rather
30033 than across the columns as is the default.
30034 <P>
30035 <End of help on this topic>
30036 </BODY>
30037 </HTML>
30038 ====== h_config_verbose_post =====
30039 <HTML>
30040 <HEAD>
30041 <TITLE>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></TITLE>
30042 </HEAD>
30043 <BODY>
30044 <H1>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></H1>
30045 This feature controls an aspect of Alpine's message sending. When enabled,
30046 Alpine will send a VERB (i.e., VERBose) command early in the posting process
30047 intended to cause the SMTP server to provide a more detailed account of
30048 the transaction. This feature is typically only useful to system
30049 administrators and other support personel as an aid in troublshooting
30050 problems.
30051 <P>
30052 Note, this feature relies on a specific capability of the system's mail
30053 transport agent or configured
30054 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>.
30055 It is possible that this
30056 feature will cause problems for some tranport agents, and may result in
30057 sending failure. In addition, as the verbose output comes from the mail
30058 transport agent, it is likely to vary from one system to another.
30059 <P><UL>
30060 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30061 </UL><P>
30062 <End of help on this topic>
30063 </BODY>
30064 </HTML>
30065 ====== h_config_auto_reply_to =====
30066 <HTML>
30067 <HEAD>
30068 <TITLE>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></TITLE>
30069 </HEAD>
30070 <BODY>
30071 <H1>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></H1>
30073 This feature controls an aspect of Alpine's Reply command. If set, Alpine
30074 will not prompt when a message being replied to contains a "Reply-To:"
30075 header value, but will simply use its value (as opposed to using the
30076 "From:" field's value).
30078 <P>
30080 Note: Using the "Reply-To:" address is usually the preferred behavior,
30081 however, some mailing list managers choose to place the list's address in
30082 the "Reply-To:" field of any message sent out to the list. In such
30083 cases, this feature makes it all too easy for personal replies to be
30084 inadvertently sent to the entire mail list, so be careful!
30085 <P>
30086 <End of help on this topic>
30087 </BODY>
30088 </HTML>
30089 ====== h_config_del_skips_del =====
30090 <HTML>
30091 <HEAD>
30092 <TITLE>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></TITLE>
30093 </HEAD>
30094 <BODY>
30095 <H1>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></H1>
30097 This feature controls an aspect of Alpine's Delete command. If set, this
30098 feature will cause the Delete command to advance past following messages that
30099 are marked deleted. In other words, pressing "D" will both mark the
30100 current message deleted and advance to the next message that is not marked
30101 deleted.
30102 This feature is set by default.
30103 <P>
30104 <End of help on this topic>
30105 </BODY></HTML>
30106 ====== h_config_expunge_manually =====
30107 <HTML>
30108 <HEAD>
30109 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></TITLE>
30110 </HEAD>
30111 <BODY>
30112 <H1>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></H1>
30114 Normally, when you close a folder that contains deleted messages you are
30115 asked if you want to expunge those messages from the folder permanently.
30116 If this feature is set, you won't be asked and the deleted messages will
30117 remain in the folder.
30118 If you choose to set this feature you will have to expunge the
30119 messages manually using the eXpunge command, which you can use while
30120 in the MESSAGE INDEX screen.
30121 If you do not expunge deleted messages the size of your
30122 folder will continue to increase until you are out of disk space.
30123 <P>
30124 <UL>
30125 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30126 </UL><P>
30127 <End of help on this topic>
30128 </BODY>
30129 </HTML>
30130 ====== h_config_auto_expunge =====
30131 <HTML>
30132 <HEAD>
30133 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></TITLE>
30134 </HEAD>
30135 <BODY>
30136 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></H1>
30138 This features controls an aspect of Alpine's eXpunge command. If set, you
30139 will <B>not</B> be prompted to confirm your intent before the expunge takes
30140 place.
30141 Actually, this is only true for the INBOX folder and for folders in the
30142 Incoming Folders collection. See the feature
30143 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>.
30144 <P>
30145 <UL>
30146 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30147 </UL><P>
30148 <End of help on this topic>
30149 </BODY>
30150 </HTML>
30151 ====== h_config_full_auto_expunge =====
30152 <HTML>
30153 <HEAD>
30154 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></TITLE>
30155 </HEAD>
30156 <BODY>
30157 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></H1>
30159 This features controls an aspect of Alpine's eXpunge command. If set, you
30160 will <B>not</B> be prompted to confirm your intent before the expunge
30161 takes place. This feature sets this behavior for all folders, unlike the
30162 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
30163 feature that works only for incoming folders.
30164 <P>
30165 <UL>
30166 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30167 </UL><P>
30168 <End of help on this topic>
30169 </BODY>
30170 </HTML>
30171 ====== h_config_auto_read_msgs =====
30172 <HTML>
30173 <HEAD>
30174 <TITLE>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></TITLE>
30175 </HEAD>
30176 <BODY>
30177 <H1>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></H1>
30178 This feature controls an aspect of Alpine's behavior upon quitting. If set,
30179 and the
30180 <A HREF="h_config_read_message_folder">"<!--#echo var="VAR_read-message-folder"-->"</A>
30181 option is also set, then Alpine will
30182 automatically transfer all read messages to the designated folder and mark
30183 them as deleted in the INBOX. Messages in the INBOX marked with an
30184 "N" (meaning New, or unseen) are not affected.
30185 <P>
30186 <UL>
30187 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30188 </UL><P>
30189 <End of help on this topic>
30190 </BODY>
30191 </HTML>
30192 ====== h_config_auto_fcc_only =====
30193 <HTML>
30194 <HEAD>
30195 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></TITLE>
30196 </HEAD>
30197 <BODY>
30198 <H1>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></H1>
30199 This features controls an aspect of Alpine's composer.
30200 The only time this feature will be used is if you attempt to send mail
30201 that has no recipients but does have an Fcc.
30202 Normally, Alpine will ask if you really mean to copy the message only to
30203 the Fcc.
30204 That is, it asks if you really meant to have no recipients.
30205 If this feature is set, you
30206 will <B>not</B> be prompted to confirm your intent to make only a copy
30207 of a message with no recipients.
30208 <P>
30209 This feature is closely related to
30210 <A HREF="h_config_warn_if_no_to_or_cc"><!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></A>.
30211 The difference between this feature and that feature is that this feature
30212 considers a Bcc to be a recipient while that feature will ask for confirmation
30213 even if there is a Bcc when there is no To, Cc, or Newsgroup.
30214 The default values also differ. This feature defaults to asking the question
30215 and you have to turn it off.
30216 The <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--> feature defaults to not asking
30217 unless you turn it on.
30218 <P>
30220 <UL>
30221 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30222 </UL><P>
30223 <End of help on this topic>
30224 </BODY>
30225 </HTML>
30226 ====== h_config_mark_fcc_seen =====
30227 <HTML>
30228 <HEAD>
30229 <TITLE>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></TITLE>
30230 </HEAD>
30231 <BODY>
30232 <H1>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></H1>
30234 This features controls the way Fccs (File carbon copies) are
30235 made of the messages you send.
30237 <P>
30238 Normally, when Alpine saves a copy of a message you sent as an Fcc, that
30239 copy will be marked as Unseen.
30240 When you look at the folder it was saved in the message will appear to
30241 be a New message until you read it.
30242 When this feature is enabled, the message will be marked as having
30243 been Seen.
30245 <P>
30246 <UL>
30247 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30248 </UL><P>
30249 <End of help on this topic>
30250 </BODY>
30251 </HTML>
30252 ====== h_config_no_fcc_attach =====
30253 <HTML>
30254 <HEAD>
30255 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></TITLE>
30256 </HEAD>
30257 <BODY>
30258 <H1>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></H1>
30260 This features controls the way Fcc's (File carbon copies) are
30261 made of the messages you send.
30263 <P>
30264 Normally, Alpine saves an exact copy of your message as it was sent.
30265 When this feature is enabled, the "body" of the message
30266 you send (the text you type in the composer) is preserved in the
30267 copy as before, however all attachments are replaced with text
30268 explaining what had been sent rather than the attachments themselves.
30270 <P>
30271 This feature also affects Alpine's "Send ?" confirmation prompt
30272 in that a new "^F Fcc Attchmnts" option becomes available which
30273 allows you to interactively set whether or not attachments are saved
30274 to the Fcc'd copy.
30276 <P>
30277 <UL>
30278 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30279 </UL><P>
30280 <End of help on this topic>
30281 </BODY>
30282 </HTML>
30283 ====== h_config_read_in_newsrc_order =====
30284 <HTML>
30285 <HEAD>
30286 <TITLE>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></TITLE>
30287 </HEAD>
30288 <BODY>
30289 <H1>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></H1>
30291 This feature controls the order in which newsgroups will be presented. If
30292 set, they will be presented in the same order as they occur in your
30293 <!--chtml if pinemode="os_windows"-->
30294 "NEWSRC"
30295 <!--chtml else-->
30296 ".newsrc"
30297 <!--chtml endif-->
30298 file (the default location of which can be changed with the
30299 <A HREF="h_config_newsrc_path">"<!--#echo var="VAR_newsrc-path"-->"</A> option).
30300 <P>
30301 If not set, the newsgroups will be presented in alphabetical order.
30302 <P>
30303 <UL>
30304 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30305 </UL><P>
30306 <End of help on this topic>
30307 </BODY>
30308 </HTML>
30309 ====== h_config_quell_tz_comment =====
30310 <HTML>
30311 <HEAD>
30312 <TITLE>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></TITLE>
30313 </HEAD>
30314 <BODY>
30315 <H1>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></H1>
30317 Normally, when Alpine generates a Date header for outgoing mail,
30318 it will try to include the symbolic timezone at the end of the
30319 header inside parentheses.
30320 The symbolic timezone is often three characters long, but on
30321 some operating systems, it may be longer.
30322 Apparently there are some SMTP servers in the world that will reject an
30323 incoming message if it has a Date header longer than about 80 characters.
30324 If this feature is set, the symbolic timezone normally generated by
30325 Alpine will not be included.
30326 You probably don't need to worry about this feature unless you run into
30327 the problem described above.
30329 <P>
30330 <End of help on this topic>
30331 </BODY>
30332 </HTML>
30333 ====== h_config_post_wo_validation =====
30334 <HTML>
30335 <HEAD>
30336 <TITLE>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></TITLE>
30337 </HEAD>
30338 <BODY>
30339 <H1>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></H1>
30341 This feature controls whether the NNTP server is queried as newsgroups
30342 are entered for posting. Validation over slow links (e.g. dialup using
30343 SLIP or PPP) can cause delays. Set this feature to eliminate such delays.
30344 <P>
30345 <End of help on this topic>
30346 </BODY>
30347 </HTML>
30348 ====== h_config_send_wo_confirm =====
30349 <HTML>
30350 <HEAD>
30351 <TITLE>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></TITLE>
30352 </HEAD>
30353 <BODY>
30354 <H1>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></H1>
30356 By default, when you send or post a message you will be asked to confirm
30357 with a question that looks something like:
30359 <P>
30360 <CENTER><SAMP>Send message?</SAMP></CENTER>
30361 <P>
30363 If this feature is set, you
30364 will <B>not</B> be prompted to confirm your intent to send
30365 and your message will be sent.
30366 <P>
30367 If this feature is set it disables some possibilities and renders some
30368 other features meaningless.
30369 You will not be able to use
30370 <A HREF="h_config_sending_filter">Sending Filters</A>,
30371 Verbose sending mode,
30372 <A HREF="h_config_compose_bg_post">Background Sending</A>,
30373 <A HREF="h_config_compose_dsn">Delivery Status Notifications</A>,
30374 or ^V to turn off the generation of flowed text for this message.
30375 These options are normally available as suboptions in the Send prompt, but
30376 with no Send prompt the options are gone.
30378 <P>
30379 A somewhat related feature is
30380 <A HREF="h_config_quell_post_prompt">"<!--#echo var="FEAT_quell-extra-post-prompt"-->"</A>,
30381 which may be used to eliminate the extra confirmation
30382 question when posting to a newsgroup.
30383 <P>
30384 <UL>
30385 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30386 </UL><P>
30387 <End of help on this topic>
30388 </BODY>
30389 </HTML>
30390 ====== h_config_quell_filtering_done_message =====
30391 <HTML>
30392 <HEAD>
30393 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></TITLE>
30394 </HEAD>
30395 <BODY>
30396 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></H1>
30398 If you use Filter Rules that move messages or set status of messages
30399 you sometimes see a message from Alpine that looks like
30401 <P>
30402 <CENTER><SAMP>filtering done</SAMP></CENTER>
30403 <P>
30405 If this feature is set, this message will be suppressed.
30406 If the feature
30407 <A HREF="h_config_quell_filtering_messages"><!--#echo var="FEAT_quell-filtering-messages"--></A>
30408 is set then this message will be suppressed regardless.
30410 <P>
30411 <UL>
30412 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30413 </UL><P>
30414 <End of help on this topic>
30415 </BODY>
30416 </HTML>
30417 ====== h_config_quell_filtering_messages =====
30418 <HTML>
30419 <HEAD>
30420 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></TITLE>
30421 </HEAD>
30422 <BODY>
30423 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></H1>
30425 If you use Filter Rules that move messages or set status of messages
30426 you sometimes see messages from Alpine that look like
30428 <P>
30429 <CENTER><SAMP><filter name>: Moving 2 filtered messages to <folder name></SAMP></CENTER>
30430 <P>
30432 or
30434 <P>
30435 <CENTER><SAMP><filter name>: Setting flags in 5 messages</SAMP></CENTER>
30436 <P>
30438 or
30440 <P>
30441 <CENTER><SAMP>Processing filter <filter name></SAMP></CENTER>
30442 <P>
30444 If this feature is set, these messages will be suppressed.
30445 The feature
30446 <A HREF="h_config_quell_filtering_done_message"><!--#echo var="FEAT_quell-filtering-done-message"--></A>
30447 is related.
30449 <P>
30450 <UL>
30451 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30452 </UL><P>
30453 <End of help on this topic>
30454 </BODY>
30455 </HTML>
30456 ====== h_config_quell_post_prompt =====
30457 <HTML>
30458 <HEAD>
30459 <TITLE>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></TITLE>
30460 </HEAD>
30461 <BODY>
30462 <H1>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></H1>
30464 By default, when you post a message to a newsgroup you are asked to confirm
30465 that you want to post with the question
30467 <P>
30468 <CENTER><SAMP>Posted message may go to thousands of readers. Really post?</SAMP></CENTER>
30469 <P>
30471 If this feature is set, you
30472 will <B>not</B> be prompted to confirm your intent to post to a newsgroup
30473 and your message will be posted.
30475 <P>
30476 <UL>
30477 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30478 </UL><P>
30479 <End of help on this topic>
30480 </BODY>
30481 </HTML>
30482 ====== h_config_check_mail_onquit =====
30483 <HTML>
30484 <HEAD>
30485 <TITLE>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></TITLE>
30486 </HEAD>
30487 <BODY>
30488 <H1>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></H1>
30490 If this feature is set, Alpine will check for new mail after you give the
30491 Quit command.
30492 If new mail has arrived since the previous check, you will be notified
30493 and given the choice of quitting or not quitting.
30494 <P>
30495 <UL>
30496 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30497 </UL><P>
30498 <End of help on this topic>
30499 </BODY>
30500 </HTML>
30501 ====== h_config_inbox_no_confirm =====
30502 <HTML>
30503 <HEAD>
30504 <TITLE>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></TITLE>
30505 </HEAD>
30506 <BODY>
30507 <H1>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></H1>
30509 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
30510 command and there are no more folders or newsgroups to visit, you are asked
30511 if you want to return to the INBOX.
30512 If this feature is set you will not be asked.
30513 It will be assumed that you do want to return to the INBOX.
30514 <P>
30515 <UL>
30516 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30517 </UL><P>
30518 <End of help on this topic>
30519 </BODY>
30520 </HTML>
30521 ====== h_config_dates_to_local =====
30522 <HTML>
30523 <HEAD>
30524 <TITLE>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></TITLE>
30525 </HEAD>
30526 <BODY>
30527 <H1>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></H1>
30529 Normally, the message dates that you see in the
30530 MESSAGE INDEX and MESSAGE VIEW are displayed in the timezone they were sent from.
30531 For example, if a message was sent to you from a few timezones to the east
30532 it might appear that it was sent from the future;
30533 or if it was sent from somewhere to the west it might appear
30534 as if it is from yesterday even though it was sent only a few minutes ago.
30535 If this feature is set an attempt will be made to convert the dates
30536 to your local timezone to be displayed.
30537 <P>
30538 Note that this does not affect the results of Select by Date or of
30539 anything else other than these displayed dates.
30540 When viewing the message you may look at the original unconverted value of the Date
30541 header by using the <A HREF="h_common_hdrmode">HdrMode Command</A>.
30542 <P>
30543 <UL>
30544 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30545 </UL><P>
30546 <End of help on this topic>
30547 </BODY>
30548 </HTML>
30549 ====== h_config_tab_no_prompt =====
30550 <HTML>
30551 <HEAD>
30552 <TITLE>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></TITLE>
30553 </HEAD>
30554 <BODY>
30555 <H1>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></H1>
30557 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
30558 command and there is a problem checking a folder, you are asked
30559 whether you want to continue with the search in the following folder or not.
30560 This question gives you a chance to stop the NextNew processing.
30561 (The checking problem might be caused by the fact that the folder does not
30562 exist, or by an authentication problem, or by a server problem
30563 of some sort.)
30564 <P>
30566 If this feature is set you will not be asked.
30567 It will be assumed that you do want to continue.
30568 <P>
30569 <UL>
30570 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30571 </UL><P>
30572 <End of help on this topic>
30573 </BODY>
30574 </HTML>
30575 ====== h_config_input_history =====
30576 <HTML>
30577 <HEAD>
30578 <TITLE>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></TITLE>
30579 </HEAD>
30580 <BODY>
30581 <H1>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></H1>
30583 Many of the prompts that ask for input in the status line near the
30584 bottom of the screen will respond to Up Arrow and Down Arrow
30585 with the history of previous entries.
30586 For example, in the MESSAGE INDEX screen when you use the WhereIs
30587 command the text you entered will be remembered and can be recalled
30588 by using the Up Arrow key.
30589 Another example, when saving a message the folders saved to will
30590 be remembered and can be recalled using the arrow keys.
30591 <P>
30592 In the Save prompt, some users prefer that the Up and Down arrow keys
30593 be used for the Previous Collection and Next Collection commands
30594 instead of for a history of previous saves.
30595 If this option is set the Up and Down arrow keys will become synonyms for the
30596 Previous Collection and Next Collection (^P and ^N) commands in the
30597 prompt for the name of a folder to Save to or in the prompt for the
30598 name of a folder to GoTo.
30599 When this feature is not set (the default), ^P and ^N will change the
30600 collection and the arrow keys will show the history.
30601 <P>
30602 <UL>
30603 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30604 </UL><P>
30605 <End of help on this topic>
30606 </BODY>
30607 </HTML>
30608 ====== h_config_confirm_role =====
30609 <HTML>
30610 <HEAD>
30611 <TITLE>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></TITLE>
30612 </HEAD>
30613 <BODY>
30614 <H1>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></H1>
30616 If you have roles, when you Reply to or Forward a message, or Compose
30617 a new message, Alpine
30618 will search through your roles for one that matches.
30619 Normally, if no matches are found you will be placed into the composer
30620 with no opportunity to select a role.
30621 If this feature is set, then you will be asked to confirm that you don't
30622 want a role.
30623 This will give you the opportunity to select a role (with the ^T command).
30624 If you confirm no role with a Return, you will be placed in
30625 the composer with no role.
30626 You may also confirm with either an "N" or a "Y".
30627 These behave the same as if you pressed the Return.
30628 (The "N" and "Y" answers are available because they
30629 match what you might type if there was a role match.)
30630 <P>
30631 If you are using the alternate form of the Compose command called
30632 "Role", then all of your roles will be available to you,
30633 independent of the value of this feauture and of the values set for all of
30634 Reply Use, Forward Use, and Compose Use.
30635 <P>
30636 <UL>
30637 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30638 </UL><P>
30639 <End of help on this topic>
30640 </BODY>
30641 </HTML>
30642 ====== h_config_news_cross_deletes =====
30643 <HTML>
30644 <HEAD>
30645 <TITLE>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></TITLE>
30646 </HEAD>
30647 <BODY>
30648 <H1>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></H1>
30650 This feature controls what Alpine does when you delete a message in a
30651 newsgroup that appears in more than one newsgroup. Such a message
30652 is sometimes termed a "crossposting" in that it was posted
30653 across several newsgroups.
30655 <P>
30656 Alpine's default behavior when you delete such a message is to remove
30657 only the copy in the current newsgroup from view when you use the
30658 "Exclude" command or the next time you visit the newsgroup.
30660 <P>
30661 Enabling this feature causes Alpine to remove every occurrence of the
30662 message from all newsgroups it appears in and to which you are
30663 subscribed.
30665 <P>
30666 NOTE: As currently implemented, enabling this feature may increase the
30667 time it takes the Expunge command and newsgroup closing to complete.
30669 <P>
30670 <UL>
30671 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30672 </UL><P>
30673 <End of help on this topic>
30674 </BODY>
30675 </HTML>
30676 ====== h_config_news_catchup =====
30677 <HTML>
30678 <HEAD>
30679 <TITLE>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></TITLE>
30680 </HEAD>
30681 <BODY>
30682 <H1>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></H1>
30684 This feature controls what Alpine does as it closes a newsgroup.
30685 When set, Alpine will offer to delete all messages from the newsgroup
30686 as you are quitting Alpine or opening a new folder.
30688 <P>
30689 This feature is useful if you typically read all the interesting messages
30690 in a newsgroup each time you open it. This feature saves you from
30691 having to delete each message in a newsgroup as you read it or from
30692 selecting all the messages and doing an
30693 <A HREF="h_config_enable_agg_ops">aggregate delete</A> before you
30694 move on to the next folder or newsgroup.
30696 <P>
30697 <UL>
30698 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30699 </UL><P>
30700 <End of help on this topic>
30701 </BODY>
30702 </HTML>
30703 ====== h_config_next_thrd_wo_confirm =====
30704 <HTML>
30705 <HEAD>
30706 <TITLE>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></TITLE>
30707 </HEAD>
30708 <BODY>
30709 <H1>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></H1>
30711 This feature controls an aspect of Alpine's Next and Prev commands in
30712 the case where you are using one of the
30713 "separate-index-screen" styles for the configuration option
30714 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
30715 and currently have the folder sorted by a Threaded or OrderedSubject sort.
30716 When you are Viewing a particular thread you have a
30717 MESSAGE INDEX of only the messages in that thread.
30718 If you press the Next command with the last message in the thread highlighted
30719 you will normally be asked if you want to "View next thread?",
30720 assuming there is a next thread to view.
30721 If this feature is set it will be assumed that you always want to view the
30722 next thread and you won't be asked to confirm that.
30723 Similarly, if the first message of the thread is highlighted and you
30724 press the Prev command, this feature will prevent the question
30725 "View previous thread".
30726 <P>
30727 This feature only has an effect in the MESSAGE INDEX screen.
30728 If you then view a particular message from that screen and press the
30729 Next command, you will be sent to the next thread without being asked,
30730 independent of the setting of this feature.
30731 <P>
30732 The feature
30733 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A> also has some similar effects.
30734 <P>
30735 <End of help on this topic>
30736 </BODY>
30737 </HTML>
30738 ====== h_config_kw_braces =====
30739 <HTML>
30740 <HEAD>
30741 <TITLE>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></TITLE>
30742 </HEAD>
30743 <BODY>
30744 <H1>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></H1>
30746 This option controls a minor aspect of Alpine's MESSAGE INDEX and MESSAGE
30747 TEXT screens.
30748 If you have modified the
30749 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
30750 so that either the "SUBJKEY" or "SUBJKEYINIT" tokens
30751 are used to display keywords or their initials along with the Subject; then
30752 this option may be used to modify the resulting display slightly.
30753 By default, the keywords or initials displayed for these tokens will be
30754 surrounded with curly braces ({ and }) and a trailing space.
30755 For example, if keywords "Work" and "Now" are set for
30756 a message, the "SUBJKEY" token will normally look like
30757 <P>
30758 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
30759 <P>
30760 and the SUBJKEYINIT token would look like
30761 <P>
30762 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
30763 <P>
30764 The default character before the keywords is the left brace ({) and the
30765 default after the keywords is the right brace followed by a space (} ).
30766 <P>
30767 This option allows you to change that.
30768 You should set it to two values separated by a space.
30769 The values may be quoted if they include space characters.
30770 So, for example, the default value could be specified explicitly by setting this
30771 option to
30772 <P>
30773 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="{" "} "</SAMP></CENTER>
30774 <P>
30775 The first part wouldn't need to be quoted (but it doesn't hurt).
30776 The second part does need the quotes because it includes a space character.
30777 If you wanted to change the braces to brackets you could use
30778 <P>
30779 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="[" "] "</SAMP></CENTER>
30780 <P>
30781 Inside the quotes you can use backslash quote to mean quote, so
30782 <P>
30783 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="\"" "\" "</SAMP></CENTER>
30784 <P>
30785 would produce
30786 <P>
30787 <CENTER><SAMP>"Work Now" actual subject</SAMP></CENTER>
30788 <P>
30789 It is also possible to color keywords in the index using the
30790 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
30791 <P>
30792 It is not possible to change the fact that a space character is used to
30793 separate the keywords if more than one keyword is set for a message.
30794 It is also not possible to change the fact that there are no separators
30795 between the keyword initials if more than one keyword is set.
30796 <P>
30797 <End of help on this topic>
30798 </BODY>
30799 </HTML>
30800 ====== h_config_opening_sep =====
30801 <HTML>
30802 <HEAD>
30803 <TITLE>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></TITLE>
30804 </HEAD>
30805 <BODY>
30806 <H1>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></H1>
30808 This option controls a minor aspect of Alpine's MESSAGE INDEX screen.
30809 With some setups the text of the subject is followed
30810 by the opening text of the message if there is any room available in the index line.
30811 If you have configured your
30812 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
30813 to include one of the Subject tokens that causes this behavior
30814 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), then this option may be used
30815 to modify what is displayed slightly.
30816 By default, the Subject is separated from the opening text of the message by
30817 the three characters space dash space;
30818 <P>
30819 <CENTER><SAMP>" - "</SAMP></CENTER>
30820 <P>
30821 Use this option to set it to something different.
30822 The value must be quoted if it includes any space characters.
30823 For example, the default value could be specified explicitly by setting this
30824 option to
30825 <P>
30826 <CENTER><SAMP><!--#echo var="VAR_opening-text-separator-chars"-->=" - "</SAMP></CENTER>
30827 <P>
30828 <End of help on this topic>
30829 </BODY>
30830 </HTML>
30831 ====== h_config_select_wo_confirm =====
30832 <HTML>
30833 <HEAD>
30834 <TITLE>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></TITLE>
30835 </HEAD>
30836 <BODY>
30837 <H1>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></H1>
30839 This feature controls an aspect of Alpine's Save, Export, and Goto commands.
30840 These commands all take text input to specify the name of the folder or
30841 file to be used, but allow you to press ^T for a list of possible names.
30842 If set, the selected name will be used immediately, without further
30843 opportunity to confirm or edit the name.
30844 <P>
30845 Some related help topics are
30846 <UL>
30847 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
30848 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
30849 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
30850 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
30851 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
30852 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>.
30853 </UL>
30854 <P>
30855 <End of help on this topic>
30856 </BODY>
30857 </HTML>
30858 ====== h_config_save_part_wo_confirm =====
30859 <HTML>
30860 <HEAD>
30861 <TITLE>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></TITLE>
30862 </HEAD>
30863 <BODY>
30864 <H1>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></H1>
30866 This feature controls an aspect of Alpine's Save command.
30867 By default, when you Save a message that has some deleted parts, you will
30868 be asked to confirm that you want to Save with a prompt that looks like:
30869 <P>
30870 <CENTER><SAMP>Saved copy will NOT include entire message! Continue?</SAMP></CENTER>
30871 <P>
30872 If this feature is set, you will not be asked.
30873 <P>
30874 <End of help on this topic>
30875 </BODY>
30876 </HTML>
30877 ====== h_config_use_resentto =====
30878 <HTML>
30879 <HEAD>
30880 <TITLE>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></TITLE>
30881 </HEAD>
30882 <BODY>
30883 <H1>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></H1>
30885 This feature is turned off by default because turning it on causes problems
30886 with some deficient IMAP servers.
30887 In Alpine <A HREF="h_mainhelp_filtering">Filters</A> and other types of Rules, if the
30888 <A HREF="h_rule_patterns">Pattern</A>
30889 contains a To header pattern and this feature is turned on,
30890 then a check is made in the message to see
30891 if a Resent-To header is present, and that is used instead of the To header.
30892 If this feature is not turned on, then the regular To header will always
30893 be used.
30895 <P>
30896 <End of help on this topic>
30897 </BODY>
30898 </HTML>
30899 ====== h_config_use_reg_start_for_stayopen =====
30900 <HTML>
30901 <HEAD>
30902 <TITLE>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></TITLE>
30903 </HEAD>
30904 <BODY>
30905 <H1>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></H1>
30907 This feature affects which message is selected as the current message
30908 when you enter a
30909 <A HREF="h_config_permlocked">Stay Open</A> folder.
30910 <P>
30911 Normally, the starting position for an incoming folder (which most Stay Open
30912 folders will likely be) is controlled by the
30913 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
30914 However, if a folder is a Stay Open folder, when you re-enter the folder
30915 after the first time the current message will be the same as it was when
30916 you left the folder.
30917 An exception is made if you use the TAB command to get to the folder.
30918 In that case, the message number will be incremented by one from what it
30919 was when you left the folder.
30920 <P>
30921 The above special behavior is thought to be useful.
30922 However, it is special and different from what you might at first expect.
30923 If this feature is set, then Stay Open folders will not be treated specially
30924 as far as the startup rule is concerned.
30926 <P>
30927 <End of help on this topic>
30928 </BODY>
30929 </HTML>
30930 ====== h_config_use_current_dir =====
30931 <HTML>
30932 <HEAD>
30933 <TITLE>FEATURE: <!--#echo var="FEAT_use-current-dir"--></TITLE>
30934 </HEAD>
30935 <BODY>
30936 <H1>FEATURE: <!--#echo var="FEAT_use-current-dir"--></H1>
30938 This feature controls an aspect of several commands.
30939 If set, your "current working directory"
30940 <!--chtml if pinemode="running"-->
30941 (which, at least for your current Alpine "session,"
30942 is "<!--#echo var="CURRENT_DIR"-->")
30943 <!--chtml endif-->
30944 will be used instead of your home directory
30945 <!--chtml if pinemode="running"-->
30946 (which, in the present configuration of your system, is
30947 "<!--#echo var="HOME_DIR"-->")
30948 <!--chtml endif-->
30949 for all of the following operations:<UL>
30950 <LI> Export in the MESSAGE INDEX and MESSAGE TEXT screens
30951 <LI> Attachment Save in the MESSAGE TEXT and ATTACHMENT TEXT screens
30952 <LI> <!--chtml if pinemode="function_key"-->F4
30953 <!--chtml else-->Ctrl-R
30954 <!--chtml endif--> file inclusion in the COMPOSER
30955 <LI> <!--chtml if pinemode="function_key"-->F5
30956 <!--chtml else-->Ctrl-J
30957 <!--chtml endif--> file attachment in the COMPOSER
30958 </UL>
30959 <!--chtml if pinemode="os_windows"-->
30960 <P>
30961 If you are starting PC-Alpine from a desktop icon or the Start menu,
30962 you can set the "current drive"
30963 by specifying it in the "Start in:"
30964 box found in the Shortcut tab of the Properties.
30965 <!--chtml endif-->
30966 <P>
30967 <UL>
30968 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30969 </UL>
30971 <P>
30972 <End of help on this topic>
30973 </BODY>
30974 </HTML>
30975 ====== h_config_save_wont_delete =====
30976 <HTML>
30977 <HEAD>
30978 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></TITLE>
30979 </HEAD>
30980 <BODY>
30981 <H1>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></H1>
30983 This feature controls one aspect of the Save command. If set, Save will
30984 not mark the message "deleted" (its default behavior) after
30985 it has been copied to the designated folder.
30987 <P>
30988 <End of help on this topic>
30989 </BODY>
30990 </HTML>
30991 ====== h_config_use_boring_spinner =====
30992 <HTML>
30993 <HEAD>
30994 <TITLE>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></TITLE>
30995 </HEAD>
30996 <BODY>
30997 <H1>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></H1>
30999 When Alpine is delayed for some reason it usually shows that
31000 something is happening with a small animated display in the status
31001 message line near the bottom of the screen.
31002 Setting this feature will cause that animation to be the same
31003 each time instead of having Alpine choose a random animation.
31004 You may turn the animation off altogether by setting the
31005 <A HREF="h_config_active_msg_interval"><!--#echo var="VAR_busy-cue-rate"--></A>
31006 option to zero.
31008 <P>
31009 <End of help on this topic>
31010 </BODY>
31011 </HTML>
31012 ====== h_config_unsel_wont_advance =====
31013 <HTML>
31014 <HEAD>
31015 <TITLE>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></TITLE>
31016 </HEAD>
31017 <BODY>
31018 <H1>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></H1>
31020 This feature controls one aspect of the Unselect Current message command.
31021 Normally, when the Unselect current message command (:) is typed when the
31022 current message is selected, the message will be unselected and the next
31023 message will become the current message.
31024 If this feature is set, the cursor will not advance to the next message.
31025 Instead, the current message will remain the current message after
31026 unselecting.
31028 <P>
31029 <End of help on this topic>
31030 </BODY>
31031 </HTML>
31032 ====== h_config_prune_uses_iso =====
31033 <HTML>
31034 <HEAD>
31035 <TITLE>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></TITLE>
31036 </HEAD>
31037 <BODY>
31038 <H1>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></H1>
31040 By default, Alpine asks monthly whether or not you would like to rename
31041 some folders to a new name containing the date.
31042 It also asks whether or not you would like to delete some old folders.
31043 See the <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option for an
31044 explanation.
31046 <P>
31047 By default, the name used when renaming a folder looks like
31048 <P>
31049 <CENTER><SAMP><foldername>-<month>-<year></SAMP></CENTER>
31050 <P>
31051 For example, the first time you run Alpine in May of 2004,
31052 the folder "sent-mail" might be renamed to
31053 <P>
31054 <CENTER><SAMP>sent-mail-apr-2004</SAMP></CENTER>
31055 <P>
31056 If this feature is set, the name used will be of the form
31057 <P>
31058 <CENTER><SAMP><foldername>-<yyyy>-<mm></SAMP></CENTER>
31059 <P>
31060 where "yyyy" is the year and "mm" is the two-digit
31061 month (01, 02, ..., 12).
31062 For the April, 2004 example above, it would instead be
31063 <P>
31064 <CENTER><SAMP>sent-mail-2004-04</SAMP></CENTER>
31065 <P>
31066 because April is the 4th month of the year.
31067 A reason you might want to set this feature is so that the folders
31068 will sort in chronological order.
31070 <P>
31071 <End of help on this topic>
31072 </BODY>
31073 </HTML>
31074 ====== h_config_save_advances =====
31075 <HTML>
31076 <HEAD>
31077 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-advance"--></TITLE>
31078 </HEAD>
31079 <BODY>
31080 <H1>FEATURE: <!--#echo var="FEAT_save-will-advance"--></H1>
31082 This feature controls one aspect of the Save command. If set, Save will
31083 (in addition to copying the current message to the designated folder) also
31084 advance to the next message.
31086 <P>
31087 <End of help on this topic>
31088 </BODY>
31089 </HTML>
31090 ====== h_config_force_arrow =====
31091 <HTML>
31092 <HEAD>
31093 <TITLE>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></TITLE>
31094 </HEAD>
31095 <BODY>
31096 <H1>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></H1>
31098 This feature affects Alpine's MESSAGE INDEX display routine.
31099 If set, the normal inverse-video cursor will be
31100 replaced by a simple "arrow" cursor, which normally occupies the
31101 second column of the index display.
31102 <P>
31103 This is the same index cursor you get if you turn on
31104 <A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>, but the index
31105 line coloring will still be present if this feature is turned on and
31106 <!--#echo var="FEAT_assume-slow-link"--> is off.
31107 <P>
31108 An alternative version of the Arrow cursor is available by including the
31109 <A HREF="h_config_index_arrow_color">ARROW</A>
31110 token in the
31111 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
31112 <P>
31113 It ought to be the case that this feature also affects the ATTACHMENT INDEX,
31114 but that is not implemented.
31116 <P>
31117 <End of help on this topic>
31118 </BODY>
31119 </HTML>
31120 ====== h_config_force_low_speed =====
31121 <HTML>
31122 <HEAD>
31123 <TITLE>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></TITLE>
31124 </HEAD>
31125 <BODY>
31126 <H1>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></H1>
31128 UNIX Alpine only.
31129 <P>
31130 This feature affects Alpine's display routines. If set, the normal
31131 inverse-video cursor (used to highlight the current item in a list) will be
31132 replaced by an "arrow" cursor and other
31133 screen update optimizations for
31134 low-speed links (e.g. 2400 bps dialup connections) will be activated.
31135 One of the optimizations is that colored index lines (set up with Indexcolor
31136 Rules) will not be colored.
31137 If you are just turning this feature on because you like using
31138 the "arrow" cursor you may have an arrow cursor with index line
31139 coloring by turning this feature off and the
31140 <A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A> on.
31142 <P>
31143 <End of help on this topic>
31144 </BODY>
31145 </HTML>
31146 ====== h_config_show_delay_cue =====
31147 <HTML>
31148 <HEAD>
31149 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></TITLE>
31150 </HEAD>
31151 <BODY>
31152 <H1>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></H1>
31154 If set, this feature will cause an asterisk to appear in the upper
31155 left-hand corner of the screen whenever Alpine checks for new mail.
31156 Two asterisks whenever Alpine saves (checkpoints) the state of the current
31157 mailbox to disk.
31159 <!--chtml if pinemode="os_windows"-->
31160 <P>
31161 In addition, PC-Alpine will display a less-than symbol, '<', when
31162 it is trying to open a network connection (e.g, to open your INBOX
31163 on an IMAP
31164 server) or read from the network connection. A greater-than symbol,
31165 will be displayed when PC-Alpine is trying to write to the network
31166 connection (e.g, sending a command to your IMAP server).
31167 <!--chtml endif-->
31169 <P>
31170 <End of help on this topic>
31171 </BODY>
31172 </HTML>
31173 ====== h_config_color_style =====
31174 <HTML>
31175 <HEAD>
31176 <TITLE>OPTION: Color Style</TITLE>
31177 </HEAD>
31178 <BODY>
31179 <H1>OPTION: Color Style</H1>
31181 UNIX Alpine only.
31182 <P>
31183 If the terminal or terminal emulator you are using is capable of displaying
31184 colors, this option controls whether or not color will be used in Alpine.
31185 If you turn color on and things are set up correctly,
31186 you should see color appear on the screen immmediately.
31187 Modern terminal emulators are usually capable of displaying colors.
31188 <P>
31189 The available options include:
31190 <P>
31192 <DL>
31193 <DT>no-color</DT>
31194 <DD>Don't use color.
31195 </DD>
31197 <DT>use-termdef</DT>
31198 <DD>In order to decide if your terminal is capable of color, Alpine looks in
31199 the terminal capabilities database, TERMINFO or TERMCAP, depending on
31200 how Alpine was compiled.
31201 This is a good option to choose if you switch between a color and a non-color
31202 terminal with the same Alpine configuration.
31203 Alpine will know to use color on the color terminal because it is described
31204 in the termcap entry, and Alpine will know to use black and white on the
31205 non-color terminal.
31206 The Alpine Technical Notes
31207 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/tech-notes/">http://www.washington.edu/alpine/tech-notes/</A></SAMP></CENTER>
31208 have more information on configuring a TERMCAP or TERMINFO
31209 entry for color Alpine.
31210 This is usually something a system administrator does.
31211 </DD>
31213 <DT>force-ansi-8color</DT>
31214 <DD>This is probably the setting that most people should use.
31215 Because setting up a termcap entry is confusing and because the
31216 terminal capabilities database is often not correctly configured for color,
31217 this choice and the next may be easier for you to use.
31218 If your terminal emulator responds to ANSI color escape sequences, which
31219 many do, this option will cause Alpine to believe your terminal will respond
31220 to the escape sequences that produce eight different foreground and background
31221 colors.
31222 The escape sequences used to set the foreground colors are
31224 <P><CENTER>ESC [ 3 <color_number> m</CENTER><P>
31226 where the color_number is an ASCII digit between 0 and 7.
31227 The numbers 0 through 7 should correspond to the colors black, red, green,
31228 yellow, blue, magenta, cyan, and white.
31229 Some terminal emulators use a pre-ANSI scheme that swaps
31230 the colors blue and red and the colors yellow and cyan.
31231 This will cause the default colors to be different, but other than that
31232 things should work fine.
31233 There is also a 9th color available, the last one shown, which is the default
31234 color from the terminal emulator.
31235 When used as a background color some people refer to this color as
31236 "transparent", which is why the letters "TRAN" are
31237 shown in the color swatch of the SETUP COLOR screen.
31238 The foreground transparent color is shown as
31239 the color of the "TRAN" text.
31240 (The transparent color will not work correctly in a PC-Alpine configuration.)
31241 The escape sequences used to set the background colors are the same
31242 as for the foreground colors except a "4" replaces the "3".
31243 The escape sequences for foreground and background default colors (transparent)
31244 are 39m and 49m.
31245 <P>
31246 Note: With the Tera Term terminal emulator this setting works well.
31247 You should also have the Tera Term "Full color" option turned OFF.
31248 You may find the "Full color" option in Tera Term's "Setup"
31249 menu, in the "Window" submenu.
31250 </DD>
31252 <DT>force-ansi-16color</DT>
31253 <DD>Many terminal emulators know about the same eight colors above
31254 plus eight more.
31255 This option attempts to use all 16 colors.
31256 The same escape sequences as for the eight-color terminal are used
31257 for the first eight colors.
31258 The escape sequences used to set foreground colors 8-15 are the same as
31259 for 0-7 except the "3" is replaced with a "9".
31260 The background color sequences for colors 8-15 are the same as for 0-7
31261 except the "4" is replaced with "10".
31262 You can tell if the 16 colors are working by turning on this option
31263 and then going into one of the color configuration screens, for example,
31264 the configuration screen for Normal Color.
31265 If you see 16 different colors to select from (plus a 17th for
31266 the transparent color), it's working.
31267 </DD>
31269 <DT>force-xterm-256color</DT>
31270 <DD>Some versions of xterm (and some other terminal emulators)
31271 have support for 256 colors.
31272 The escape sequences used to set the foreground colors are
31274 <P><CENTER>ESC [ 38 ; 5 ; <color_number> m</CENTER><P>
31276 where the color_number is an ASCII digit between 0 and 255.
31277 Background colors are the same with the 38 replaced with a 48.
31278 The numbers 0 through 15 are probably similar to the 16 color version
31279 above, then comes a 6x6x6 color cube, followed by 24 colors of gray.
31280 The terminal default (transparent) color is the 257th color at the bottom.
31281 Some terminal emulators will misinterpret these escape sequences causing
31282 the terminal to blink or overstrike characters or to do something else
31283 undesirable.
31284 <P>
31285 The PuTTY terminal emulator has an option called "Allow terminal to
31286 use xterm 256-colour mode" which allows PuTTY to work well with
31287 this 256-color setting.
31289 </DD>
31290 </DL>
31292 <P>
31293 The normal default is "no-color".
31294 <P>
31296 Once you've turned on color you may set the
31297 colors of many objects on the screen individually.
31298 For example, you may add colors to the status letters on the MESSAGE
31299 INDEX page.
31300 Most categories of color that Alpine supports are configurable here.
31301 For example, "Normal Color"
31302 is the color used to display most of the text in Alpine, and
31303 "Reverse Color" is used to display highlighted text, such as the
31304 current message in the MESSAGE INDEX.
31305 <P>
31306 Lines in the MESSAGE INDEX may also be colored.
31307 Use Setup Rules to get to the Indexcolor configuration screen.
31308 <P>
31310 <UL>
31311 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31312 </UL><P>
31313 <End of help on this topic>
31314 </BODY>
31315 </HTML>
31316 ====== h_config_disable_index_locale_dates =====
31317 <HTML>
31318 <HEAD>
31319 <TITLE>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></TITLE>
31320 </HEAD>
31321 <BODY>
31322 <H1>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></H1>
31324 This feature affects the display of dates in the MESSAGE INDEX.
31325 Normally an attempt is made to localize the dates
31326 used in the MESSAGE INDEX display to your locale.
31327 This is controlled with the
31328 LC_TIME locale setting on a UNIX system.
31329 On Windows the Regional Options control panel may be used to set the date format.
31330 At the programming level, Alpine is using the strftime routine
31331 to print the parts of a date.
31332 <P>
31333 If this feature is set, dates are displayed in English and
31334 with the conventions of the United States.
31335 <P>
31337 <UL>
31338 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31339 </UL><P>
31340 <End of help on this topic>
31341 </BODY>
31342 </HTML>
31343 ====== h_config_auto_open_unread =====
31344 <HTML>
31345 <HEAD>
31346 <TITLE>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></TITLE>
31347 </HEAD>
31348 <BODY>
31349 <H1>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></H1>
31351 This feature controls the behavior of the TAB key when traversing folders
31352 in the optional
31353 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
31354 collection or in optional <!--#echo var="VAR_news-collections"-->.
31355 <P>
31356 When the TAB
31357 (<A HREF="h_common_nextnew">NextNew</A>)
31358 key is pressed, and there
31359 are no more unseen messages in the current (incoming message or news)
31360 folder, Alpine will search the list of folders in the current collection for
31361 one containing New or Recent (new since the last time the folder was
31362 opened) messages.
31363 This behavior may be modified slightly with the
31364 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
31365 feature that causes Alpine to look for Unseen messages instead of Recent
31366 messages.
31367 Normally, when such a folder is found, Alpine will ask
31368 whether you wish to open the folder. If this feature is set, Alpine will
31369 automatically open the folder without prompting.
31370 <P>
31371 This feature also affects some other similar situations.
31372 If you have a
31373 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
31374 that is equal to one of the "separate-" values, and you are
31375 viewing a thread; then when you type the NextNew command and are at the
31376 end of the current thread you will automatically go to the next thread
31377 if this feature is set.
31378 By default, you would be asked if you want to view the next thread.
31379 You will also be asked at times whether or not you want to view the next
31380 thread after you delete the last message in the thread.
31381 Setting this feature will also cause that question to be skipped.
31382 <P>
31384 <UL>
31385 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31386 </UL><P>
31387 <End of help on this topic>
31388 </BODY>
31389 </HTML>
31390 ====== h_config_auto_include_reply =====
31391 <HTML>
31392 <HEAD>
31393 <TITLE>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></TITLE>
31394 </HEAD>
31395 <BODY>
31396 <H1>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></H1>
31398 This feature controls an aspect of Alpine's Reply command. Normally, Alpine
31399 will ask whether you wish to include the original message in your reply.
31400 If this feature is set and the feature
31401 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
31402 is <EM>not</EM> set, then the original message will be included in the reply
31403 automatically, without prompting.
31404 <P>
31405 <End of help on this topic>
31406 </BODY>
31407 </HTML>
31408 ====== h_config_select_in_bold =====
31409 <HTML>
31410 <HEAD>
31411 <TITLE>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></TITLE>
31412 </HEAD>
31413 <BODY>
31414 <H1>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></H1>
31416 This feature controls an aspect of Alpine's
31417 <A HREF="h_config_enable_agg_ops">"aggregate operation"</A>
31418 commands; in
31419 particular, the Select and WhereIs commands. Select and WhereIs (with the
31420 ^X subcommand) will search the current folder for messages meeting a
31421 specified criteria, and "tag" the resulting messages with an
31422 "X" in the
31423 first column of the applicable lines in the MESSAGE INDEX. If this feature
31424 is set, instead of using the "X" to denote a selected message,
31425 Alpine will
31426 attempt to display those index lines in boldface. Whether this is
31427 preferable to the "X" will depend on personal taste and the type of
31428 terminal being used.
31429 <P>
31430 <UL>
31431 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31432 </UL><P>
31433 <End of help on this topic>
31434 </BODY>
31435 </HTML>
31436 ====== h_config_alt_auth =====
31437 <HTML>
31438 <HEAD>
31439 <TITLE>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></TITLE>
31440 </HEAD>
31441 <BODY>
31442 <H1>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></H1>
31444 This feature affects how Alpine connects to IMAP servers.
31445 It's utility has largely been overtaken by events,
31446 but it may still be useful in some circumstances.
31447 If you only connect to modern IMAP servers that support
31448 "TLS" you can ignore this feature.
31450 <P>
31451 Details:
31453 <P>
31454 By default, Alpine will attempt to connect to an IMAP server on the
31455 normal IMAP service port (143), and if the server offers "Transport Layer
31456 Security" (TLS) and Alpine has been compiled with encryption capability,
31457 then a secure (encrypted) session will be negotiated.
31459 <P>
31460 With this feature enabled, before connecting on the normal IMAP port, Alpine
31461 will first attempt to connect to an alternate IMAP service port (993) used
31462 specifically for encrypted IMAP sessions via the Secure Sockets Layer
31463 (SSL) method.
31464 If the SSL attempt fails, Alpine will then try the default
31465 behavior described in the previous paragraph.
31467 <P>
31468 TLS negotiation on the normal port is preferred, and supersedes the use of
31469 SSL on port 993, but older servers may not provide TLS support.
31470 This feature may be convenient when accessing IMAP servers that do not support
31471 TLS, but do support SSL connections on port 993.
31472 However, it is important to understand that with this feature enabled,
31473 Alpine will <EM>attempt</EM> to make a secure connection if that is possible,
31474 but it will proceed to make an insecure connection if that is the only
31475 option offered by the server, or if the Alpine in question has been built
31476 without encryption capability.
31478 <P>
31479 Note that this feature specifies a per-user (or system-wide) default
31480 behavior, but host/folder specification flags may be used to control the
31481 behavior of any specific connection.
31482 This feature interacts with some of
31483 the possible host/folder path specification flags as follows:
31485 <P>
31486 The <SAMP>/tls</SAMP> host flag, for example,
31488 <P>
31489 <CENTER><SAMP>{foo.example.com/tls}INBOX</SAMP></CENTER>
31490 <P>
31491 will over-ride this feature for the specified host by bypassing the
31492 SSL connection attempt.
31493 Moreover, with <SAMP>/tls</SAMP> specified,
31494 the connection attempt will fail if the
31495 service on port 143 does not offer TLS support.
31497 <P>
31498 The <SAMP>/ssl</SAMP> host flag, for example,
31500 <P>
31501 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
31502 <P>
31503 will insist on an SSL connection for the specified host,
31504 and will fail if the SSL service on port 993 is not available.
31505 Alpine will not subsequently retry a connection
31506 on port 143 if <SAMP>/ssl</SAMP> is specified.
31508 <P>
31509 <UL>
31510 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31511 </UL><P>
31512 <End of help on this topic>
31513 </BODY>
31514 </HTML>
31515 ====== h_config_file_dir ======
31516 <HTML>
31517 <HEAD>
31518 <TITLE>OPTION: File Directory</TITLE>
31519 </HEAD>
31520 <BODY>
31521 <H1>OPTION: File Directory</H1>
31523 PC-Alpine only.
31524 <P>
31525 This value affects the Composer's "^J Attach" command,
31526 the Attachment Index Screen's "S Save" command, and the
31527 Message Index's "E Export" command.
31529 <P>
31530 Normally, when a filename is supplied that lacks a leading "path"
31531 component, Alpine assumes the file exists in the user's home directory.
31532 Under Windows operating systems, this definition isn't always clear. This
31533 feature allows you to explictly set where Alpine should look for files
31534 without a leading path.
31536 <P>
31537 NOTE: this feature's value is ignored if either
31538 <A HREF="h_config_use_current_dir"><!--#echo var="FEAT_use-current-dir"--></A> feature
31539 is set or the PINERC has a value for the "<!--#echo var="VAR_operating-dir"-->" variable.
31541 <P>
31542 <UL>
31543 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31544 </UL><P>
31545 <End of help on this topic>
31546 </BODY>
31547 </HTML>
31548 ====== h_config_quote_all_froms =====
31549 <HTML>
31550 <HEAD>
31551 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></TITLE>
31552 </HEAD>
31553 <BODY>
31554 <H1>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></H1>
31556 This feature controls an aspect of the Save command (and also the way
31557 outgoing messages are saved to an FCC folder). If set, Alpine will add
31558 a leading ">" character in front of message lines beginning with "From"
31559 when they are saved to another folder, including lines syntactically
31560 distinguishable from the type of message separator line commonly used on
31561 Unix systems.
31563 <P>
31564 The default behavior is that a ">" will be prepended only to lines
31565 beginning with "From " that might otherwise be confused with a message
31566 separator line on Unix systems. If pine is the only mail program you use,
31567 this default is reasonable. If another program you use has trouble
31568 displaying a message with an unquoted "From " saved by Alpine, you should
31569 enable this feature. This feature only applies to the common Unix mailbox
31570 format that uses message separator lines beginning with "From ". If
31571 Alpine has been configured to use a different mailbox format (possibly
31572 incompatible with other mail programs), then this issue does not arise,
31573 and the feature is irrelevant.
31575 <P>
31576 <End of help on this topic>
31577 </BODY>
31578 </HTML>
31579 ====== h_config_normal_color =====
31580 <HTML>
31581 <HEAD>
31582 <TITLE>OPTION: Normal Color</TITLE>
31583 </HEAD>
31584 <BODY>
31585 <H1>OPTION: Normal Color</H1>
31587 Sets the color Alpine normally uses.
31588 The foreground color is the color of the actual character and the
31589 background color is the color of the area behind the character.
31590 By default this color is black characters on a white background.
31591 <P>
31592 <A HREF="h_color_setup">Descriptions of the available commands</A>
31593 <P>
31594 Look <A HREF="h_edit_nav_cmds">here</A>
31595 to see the available Editing and Navigation commands.
31596 <P>
31597 <End of help on this topic>
31598 </BODY>
31599 </HTML>
31600 ====== h_config_reverse_color =====
31601 <HTML>
31602 <HEAD>
31603 <TITLE>OPTION: Reverse Color</TITLE>
31604 </HEAD>
31605 <BODY>
31606 <H1>OPTION: Reverse Color</H1>
31608 Sets the color Alpine uses for reverse video characters.
31609 The foreground color is the color of the actual character and the
31610 background color is the color of the area behind the character.
31611 <P>
31612 <A HREF="h_color_setup">Descriptions of the available commands</A>
31613 <P>
31614 Look <A HREF="h_edit_nav_cmds">here</A>
31615 to see the available Editing and Navigation commands.
31616 <P>
31617 <End of help on this topic>
31618 </BODY>
31619 </HTML>
31620 ====== h_config_title_color =====
31621 <HTML>
31622 <HEAD>
31623 <TITLE>OPTION: Title Color</TITLE>
31624 </HEAD>
31625 <BODY>
31626 <H1>OPTION: Title Color</H1>
31628 Sets the color Alpine uses for the titlebar (the top line on the screen).
31629 The foreground color is the color of the actual character and the
31630 background color is the color of the area behind the character.
31631 By default, the Title Color is black characters on a yellow background.
31632 <P>
31633 The actual titlebar color may be different from the Title Color if
31634 the option
31635 <A HREF="h_config_titlebar_color_style">"<!--#echo var="VAR_titlebar-color-style"-->"</A>
31636 is set to some value other than the default.
31637 It may also be different if the current folder is closed and the
31638 <A HREF="h_config_titleclosed_color">Title Closed Color</A>
31639 color is set to something different from the Title Color.
31640 <P>
31641 <A HREF="h_color_setup">Descriptions of the available commands</A>
31642 <P>
31643 Look <A HREF="h_edit_nav_cmds">here</A>
31644 to see the available Editing and Navigation commands.
31645 <P>
31646 <End of help on this topic>
31647 </BODY>
31648 </HTML>
31649 ====== h_config_titleclosed_color =====
31650 <HTML>
31651 <HEAD>
31652 <TITLE>OPTION: Title Closed Color</TITLE>
31653 </HEAD>
31654 <BODY>
31655 <H1>OPTION: Title Closed Color</H1>
31657 Sets the color Alpine uses for the titlebar (the top line on the screen)
31658 when the current folder is closed.
31659 The foreground color is the color of the actual character and the
31660 background color is the color of the area behind the character.
31661 By default, the Title Color Closed Color is white characters on a red background.
31662 <P>
31663 By setting this color to something noticeable you will be alerted to the
31664 fact that the current folder is closed, perhaps unexpectedly.
31665 <P>
31666 <End of help on this topic>
31667 </BODY>
31668 </HTML>
31669 ====== h_config_status_color =====
31670 <HTML>
31671 <HEAD>
31672 <TITLE>OPTION: Status Color</TITLE>
31673 </HEAD>
31674 <BODY>
31675 <H1>OPTION: Status Color</H1>
31677 Sets the color Alpine uses for status messages written to the message
31678 line near the bottom of the screen.
31679 The foreground color is the color of the actual character and the
31680 background color is the color of the area behind the character.
31681 By default, the Status Color is the same as the Reverse Color.
31682 <P>
31683 <A HREF="h_color_setup">Descriptions of the available commands</A>
31684 <P>
31685 Look <A HREF="h_edit_nav_cmds">here</A>
31686 to see the available Editing and Navigation commands.
31687 <P>
31688 <End of help on this topic>
31689 </BODY>
31690 </HTML>
31691 ====== h_config_index_opening_color =====
31692 <HTML>
31693 <HEAD>
31694 <TITLE>OPTION: Index Opening Color</TITLE>
31695 </HEAD>
31696 <BODY>
31697 <H1>OPTION: Index Opening Color</H1>
31699 With some setups the text of the subject is followed
31700 by the opening text of the message if there is any room available in the index line.
31701 If you have configured your
31702 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
31703 to include one of the Subject tokens that causes this behavior
31704 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), you may set the color of
31705 this opening text with this option.
31706 This coloring takes place for all but the current index line, and the Opening
31707 Color appears to be in front of any color from an Index Color Rule.
31708 <P>
31709 By default the Index Opening Color is gray characters on a white background.
31711 <P>
31712 <A HREF="h_color_setup">Descriptions of the available commands</A>
31713 <P>
31714 Look <A HREF="h_edit_nav_cmds">here</A>
31715 to see the available Editing and Navigation commands.
31716 <P>
31717 <End of help on this topic>
31718 </BODY>
31719 </HTML>
31720 ====== h_config_index_pri_color =====
31721 <HTML>
31722 <HEAD>
31723 <TITLE>OPTION: Index Priority Symbol Colors</TITLE>
31724 </HEAD>
31725 <BODY>
31726 <H1>OPTION: Index Priority Symbol Colors</H1>
31728 The X-Priority header is a non-standard header that is used in a
31729 somewhat standard way by many mail programs.
31730 Alpine expects the value of this header to be a digit with a value
31731 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
31732 Alpine can be made to display an indication of this priority in
31733 messages by use of one of the tokens
31734 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
31735 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
31736 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
31738 <P>
31739 You may set the color used to draw these tokens by use of the colors
31740 Index High Priority Symbol Color and Index Low Priority Symbol Color.
31741 This coloring takes place for all but the current index line, and the Priority
31742 Color appears to be in front of any color from an Index Color Rule.
31743 If the priority has a value of 1 or 2 the High Priority color will be
31744 used,
31745 and if the value is 4 or 5 the Low Priority color will be used.
31746 <P>
31747 If you don't set these colors the index line will be colored in the same color as
31748 the bulk of the index line.
31750 <P>
31751 <A HREF="h_color_setup">Descriptions of the available commands</A>
31752 <P>
31753 Look <A HREF="h_edit_nav_cmds">here</A>
31754 to see the available Editing and Navigation commands.
31755 <P>
31756 <End of help on this topic>
31757 </BODY>
31758 </HTML>
31759 ====== h_config_index_subject_color =====
31760 <HTML>
31761 <HEAD>
31762 <TITLE>OPTION: Index Subject Color</TITLE>
31763 </HEAD>
31764 <BODY>
31765 <H1>OPTION: Index Subject Color</H1>
31767 You may set the color used to draw the Subject part of the index line.
31768 This coloring takes place for all but the current index line, and the Subject
31769 Color appears to be in front of any color from an Index Color Rule.
31770 <P>
31771 If you don't set this color it will be colored in the same color as
31772 the bulk of the index line.
31774 <P>
31775 <A HREF="h_color_setup">Descriptions of the available commands</A>
31776 <P>
31777 Look <A HREF="h_edit_nav_cmds">here</A>
31778 to see the available Editing and Navigation commands.
31779 <P>
31780 <End of help on this topic>
31781 </BODY>
31782 </HTML>
31783 ====== h_config_index_from_color =====
31784 <HTML>
31785 <HEAD>
31786 <TITLE>OPTION: Index From Color</TITLE>
31787 </HEAD>
31788 <BODY>
31789 <H1>OPTION: Index From Color</H1>
31791 You may set the color used to draw the From part of the index line.
31792 This coloring takes place for all but the current index line, and the From
31793 Color appears to be in front of any color from an Index Color Rule.
31794 <P>
31795 If you don't set this color it will be colored in the same color as
31796 the bulk of the index line.
31798 <P>
31799 <A HREF="h_color_setup">Descriptions of the available commands</A>
31800 <P>
31801 Look <A HREF="h_edit_nav_cmds">here</A>
31802 to see the available Editing and Navigation commands.
31803 <P>
31804 <End of help on this topic>
31805 </BODY>
31806 </HTML>
31807 ====== h_config_index_arrow_color =====
31808 <HTML>
31809 <HEAD>
31810 <TITLE>OPTION: Index Arrow Color</TITLE>
31811 </HEAD>
31812 <BODY>
31813 <H1>OPTION: Index Arrow Color</H1>
31815 If you have configured your
31816 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
31817 to include the "ARROW" token, you may set the color of
31818 the arrow displayed with this option.
31819 If you don't set the color it will be colored in the same color as
31820 the bulk of the index line.
31822 <P>
31823 <A HREF="h_color_setup">Descriptions of the available commands</A>
31824 <P>
31825 Look <A HREF="h_edit_nav_cmds">here</A>
31826 to see the available Editing and Navigation commands.
31827 <P>
31828 <End of help on this topic>
31829 </BODY>
31830 </HTML>
31831 ====== h_config_index_color =====
31832 <HTML>
31833 <HEAD>
31834 <TITLE>OPTION: Index Colors</TITLE>
31835 </HEAD>
31836 <BODY>
31837 <H1>OPTION: Index Colors</H1>
31839 You may add color to the single character symbols that give the status
31840 of each message in the MESSAGE INDEX.
31841 By default the characters "+", "*", "D",
31842 "A", and "N" show up near the left hand side of the
31843 screen depending on whether the message is addressed to you, and whether
31844 the message is marked Important, is Deleted, is Answered, or is New.
31845 The color for each of those characters may be specified by setting the
31846 "Index-to-me" Symbol Color,
31847 the "Index-important" Symbol Color,
31848 the "Index-deleted" Symbol Color,
31849 the "Index-answered" Symbol Color,
31850 and the "Index-new" Symbol Color.
31851 There are also two other symbol colors called "Index-recent"
31852 and "Index-unseen".
31853 These two colors will only be used if you have configured your
31854 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
31855 to include the "IMAPSTATUS" or "SHORTIMAPSTATUS" token.
31856 <P>
31857 The default colors for these symbols are:
31858 <TABLE>
31859 <TR> <TD> Index-to-me </TD> <TD> black on cyan </TD> </TR>
31860 <TR> <TD> Index-important </TD> <TD> white on bright red </TD> </TR>
31861 <TR> <TD> Index-deleted </TD> <TD> same as Normal Color </TD> </TR>
31862 <TR> <TD> Index-answered </TD> <TD> bright red on yellow </TD> </TR>
31863 <TR> <TD> Index-new </TD> <TD> white on magenta </TD> </TR>
31864 <TR> <TD> Index-recent </TD> <TD> same as Normal Color </TD> </TR>
31865 <TR> <TD> Index-unseen </TD> <TD> same as Normal Color </TD> </TR>
31866 </TABLE>
31867 <P>
31868 Besides coloring the message status symbols, you may also color the
31869 entire index line.
31870 This is done by using the
31871 <A HREF="h_rules_incols">SETUP INDEX LINE COLORS</A> screen, which you
31872 may get to with the commands <EM>S</EM>etup/<EM>R</EM>ules/<EM>I</EM>ndexcolor.
31873 When the entire line is colored that color will be "behind" the
31874 status symbol colors talked about in the paragraph above.
31875 <P>
31876 You may also color
31877 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
31878 in the index using the
31879 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>);
31880 the <A HREF="h_config_index_arrow_color">ARROW</A> cursor;
31881 the Subject using
31882 <A HREF="h_config_index_subject_color">Index Subject Color</A>;
31883 the From field using
31884 <A HREF="h_config_index_from_color">Index From Color</A>;
31885 and the
31886 <A HREF="h_config_index_opening_color">Index Opening</A> text.
31887 <P>
31888 <A HREF="h_color_setup">Descriptions of the available commands</A>
31889 <P>
31890 Look <A HREF="h_edit_nav_cmds">here</A>
31891 to see the available Editing and Navigation commands.
31892 <P>
31893 <End of help on this topic>
31894 </BODY>
31895 </HTML>
31896 ====== h_config_metamsg_color =====
31897 <HTML>
31898 <HEAD>
31899 <TITLE>OPTION: Meta-Message Color</TITLE>
31900 </HEAD>
31901 <BODY>
31902 <H1>OPTION: Meta-Message Color</H1>
31904 Sets the color Alpine uses in the MESSAGE TEXT screen for messages to you
31905 that aren't part of the message itself.
31906 For example, an attachment that isn't shown might produce a meta
31907 message something like:
31908 <P>
31909 <CENTER><SAMP> [ Part 2, "comment" Text/PLAIN (Name: "file") ]</SAMP></CENTER>
31910 <P>
31911 If you set the
31912 <A HREF="h_config_quote_suppression"><!--#echo var="VAR_quote-suppression-threshold"--></A>
31913 option you might see
31914 <P>
31915 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
31916 <P>
31917 Warnings about suspicious looking URLs in HTML will also be colored
31918 with this color.
31919 <P>
31920 The foreground color is the color of the actual character and the
31921 background color is the color of the area behind the character.
31922 By default, the Meta-Message Color is black characters on a yellow background.
31923 <P>
31924 <A HREF="h_color_setup">Descriptions of the available commands</A>
31925 <P>
31926 Look <A HREF="h_edit_nav_cmds">here</A>
31927 to see the available Editing and Navigation commands.
31928 <P>
31929 <End of help on this topic>
31930 </BODY>
31931 </HTML>
31932 ====== h_config_keylabel_color =====
31933 <HTML>
31934 <HEAD>
31935 <TITLE>OPTION: KeyLabel Color</TITLE>
31936 </HEAD>
31937 <BODY>
31938 <H1>OPTION: KeyLabel Color</H1>
31940 Sets the color Alpine uses for the labels of the keys in the two-line
31941 menu at the bottom of the screen.
31942 For example, some of the screens have a "P PrevMsg" command.
31943 This option sets the color used when displaying "PrevMsg".
31944 The foreground color is the color of the actual character and the
31945 background color is the color of the area behind the character.
31946 By default, the KeyLabel Color is the same as the Normal Color.
31947 <P>
31948 WARNING: Some terminal emulators have the property that the screen will scroll
31949 down one line whenever a character is written to the character cell in the
31950 lower right corner of the screen.
31951 Alpine can usually avoid writing a character in that corner of the screen.
31952 However, if you have defined a KeyLabel Color then Alpine does have to write
31953 a character in that cell in order to color the cell correctly.
31954 If you find that your display sometimes scrolls up a line this could be
31955 the problem.
31956 The most obvious symptom is probably that the titlebar at the top of the
31957 screen scrolls off the screen.
31958 Try setting KeyLabel Color to Default to see if that fixes the problem.
31959 <P>
31960 <A HREF="h_color_setup">Descriptions of the available commands</A>
31961 <P>
31962 Look <A HREF="h_edit_nav_cmds">here</A>
31963 to see the available Editing and Navigation commands.
31964 <P>
31965 <End of help on this topic>
31966 </BODY>
31967 </HTML>
31968 ====== h_config_keyname_color =====
31969 <HTML>
31970 <HEAD>
31971 <TITLE>OPTION: KeyName Color</TITLE>
31972 </HEAD>
31973 <BODY>
31974 <H1>OPTION: KeyName Color</H1>
31976 Sets the color Alpine uses for the names of the keys in the two-line
31977 menu at the bottom of the screen.
31978 For example, some of the screens have a "P PrevMsg" command.
31979 This option sets the color used when displaying the "P".
31980 The foreground color is the color of the actual character and the
31981 background color is the color of the area behind the character.
31982 By default, the KeyName Color is the same as the Reverse Color.
31983 <P>
31984 <A HREF="h_color_setup">Descriptions of the available commands</A>
31985 <P>
31986 Look <A HREF="h_edit_nav_cmds">here</A>
31987 to see the available Editing and Navigation commands.
31988 <P>
31989 <End of help on this topic>
31990 </BODY>
31991 </HTML>
31992 ====== h_config_slctbl_color =====
31993 <HTML>
31994 <HEAD>
31995 <TITLE>OPTION: Selectable Item Color</TITLE>
31996 </HEAD>
31997 <BODY>
31998 <H1>OPTION: Selectable Item Color</H1>
32000 Sets the color Alpine uses for selectable items, such as URLs.
32001 The foreground color is the color of the actual character and the
32002 background color is the color of the area behind the character.
32003 By default, the Selectable Item Color is the same as the Normal Color,
32004 except that it is bold.
32005 <P>
32006 <A HREF="h_color_setup">Descriptions of the available commands</A>
32007 <P>
32008 Look <A HREF="h_edit_nav_cmds">here</A>
32009 to see the available Editing and Navigation commands.
32010 <P>
32011 <End of help on this topic>
32012 </BODY>
32013 </HTML>
32014 ====== h_config_quote_color =====
32015 <HTML>
32016 <HEAD>
32017 <TITLE>OPTION: Quote Colors</TITLE>
32018 </HEAD>
32019 <BODY>
32020 <H1>OPTION: Quote Colors</H1>
32022 Sets the colors Alpine uses for coloring quoted text in the MESSAGE TEXT
32023 screen.
32024 If a line begins with a > character (or space followed by >)
32025 it is considered a quote.
32026 That line will be given the Quote1 Color (first level quote).
32027 If there is a second level of quoting then the Quote2 Color will be used.
32028 Alpine considers there to be a second level of quoting if that first > is
32029 followed by another > (or space followed by >).
32030 If there are characters other than whitespace and > signs, then it isn't
32031 considered another level of quoting.
32032 Similarly, if there is a third level of quoting the Quote3 Color will be
32033 used.
32034 If there are more levels after that the Quote Colors are re-used.
32035 If you define all three colors then it would repeat like Color1, Color2, Color3,
32036 Color1, Color2, Color3, ...
32037 If you only define the first two it would be
32038 Color1, Color2, Color1, Color2, ...
32039 If you define only the Quote1 Color, then the entire quote would be that
32040 color regardless of the quoting levels.
32041 By default, the Quote1 Color is black characters on a greenish-blue background;
32042 the Quote2 Color is black characters on a dull yellow background; and
32043 the Quote3 Color is black characters on a green background.
32044 <P>
32045 <A HREF="h_color_setup">Descriptions of the available commands</A>
32046 <P>
32047 Look <A HREF="h_edit_nav_cmds">here</A>
32048 to see the available Editing and Navigation commands.
32049 <P>
32050 <End of help on this topic>
32051 </BODY>
32052 </HTML>
32053 ====== h_config_folder_color =====
32054 <HTML>
32055 <HEAD>
32056 <TITLE>OPTION: Folder Color</TITLE>
32057 </HEAD>
32058 <BODY>
32059 <H1>OPTION: Folder Color</H1>
32061 Sets the colors Alpine uses for coloring a folder in the FOLDER LIST
32062 screen. By default, the Folder Color is the normal text color.
32064 <P>
32065 If you set a color for this feature, other than the normal color
32066 (the default), or a color for
32067 <A HREF="h_config_directory_color">Directory Color</A>, then directories
32068 will be colored according to the color specified in the
32069 <A HREF="h_config_directory_color">Directory Color</A> option. In this
32070 case, the color will be the only indication that the colored name
32071 refers to a directory. The normal behavior is that Alpine
32072 indicates that a name refers to a directory by appending a
32073 separator (like "/" or ".") to the name of
32074 the folder.
32076 <P>
32077 If a folder is a directory, then the folder name will be painted
32078 according to the color defined by this variable, and a separator
32079 indicator (like "/" or ".") will be added
32080 to the name. That
32081 indicator will be painted according to the color defined in the
32082 <A HREF="h_config_directory_color">Directory Color</A> option.
32084 <P>
32085 <End of help on this topic>
32086 </BODY>
32087 </HTML>
32088 ====== h_config_directory_color =====
32089 <HTML>
32090 <HEAD>
32091 <TITLE>OPTION: Directory Color</TITLE>
32092 </HEAD>
32093 <BODY>
32094 <H1>OPTION: Directory Color</H1>
32096 Sets the colors Alpine uses for coloring a directory in the FOLDER LIST
32097 screen. By default, the Folder Color is the normal text color.
32098 <P>
32099 If you set a color for this feature, other than the normal color
32100 (the default), or a color for
32101 <A HREF="h_config_folder_color">Folder Color</A>, then folders
32102 will be colored according to the color specified in the
32103 <A HREF="h_config_folder_color">Folder Color</A> option. In this
32104 case, the color will be the only indication that the colored name
32105 refers to a directory. The normal behavior is that Alpine
32106 indicates that a name refers to a directory by appending a
32107 separator (like "/" or ".") to the name of
32108 the folder.
32109 <P>
32110 If a folder is a directory, then the folder name will be painted
32111 according to the color defined by the option
32112 <A HREF="h_config_folder_color">Folder Color</A>, and the separator
32113 indicator (like "/" or ".") will be added
32114 after the name. That
32115 indicator will be painted according to the color defined in this
32116 option.
32117 <P>
32118 <End of help on this topic>
32119 </BODY>
32120 </HTML>
32121 ====== h_config_folder_list_color =====
32122 <HTML>
32123 <HEAD>
32124 <TITLE>OPTION: Folder-List Color</TITLE>
32125 </HEAD>
32126 <BODY>
32127 <H1>OPTION: Folder-List Color</H1>
32129 Sets the colors Alpine uses for coloring normal text in the FOLDER LIST
32130 screen. By default, the Folder-List Color is the normal text color.
32131 <P>
32132 This text refers to the informative text that Alpine displays so you
32133 can recognize each collection. The color of the content of each collection
32134 is determined by the options <A HREF="h_config_folder_color">Folder Color</A>
32135 and <A HREF="h_config_directory_color">Directory Color</A>.
32136 <P>
32137 Unlike the options
32138 <A HREF="h_config_folder_color">Folder Color</A>
32139 and <A HREF="h_config_directory_color">Directory Color</A>, configuring
32140 this option does not affect the way that Alpine reports folders,
32141 directories and folders that are directories.
32142 <P>
32143 <End of help on this topic>
32144 </BODY>
32145 </HTML>
32146 ====== h_config_incunseen_color =====
32147 <HTML>
32148 <HEAD>
32149 <TITLE>OPTION: Incoming Unseen Color</TITLE>
32150 </HEAD>
32151 <BODY>
32152 <H1>OPTION: Incoming Unseen Color</H1>
32154 If the option
32155 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
32156 is turned on it is possible to highlight the folders that contain
32157 unseen messages by coloring them with this color.
32158 By default, this is the same as the Normal Color and no highlighting is done.
32159 <P>
32160 Usually the "current" folder (the folder the cursor is on)
32161 is highlighted using reverse video.
32162 If the current folder is colored because it contains unseen messages then
32163 the color used to show that it is also the current folder is controlled
32164 by the
32165 <A HREF="h_config_index_color_style"><!--#echo var="VAR_current-indexline-style"--></A>
32166 feature at the top of the SETUP COLOR screen.
32167 <P>
32168 <A HREF="h_color_setup">Descriptions of the available commands</A>
32169 <P>
32170 Look <A HREF="h_edit_nav_cmds">here</A>
32171 to see the available Editing and Navigation commands.
32172 <P>
32173 <End of help on this topic>
32174 </BODY>
32175 </HTML>
32176 ====== h_config_signature_color =====
32177 <HTML>
32178 <HEAD>
32179 <TITLE>OPTION: Signature Color</TITLE>
32180 </HEAD>
32181 <BODY>
32182 <H1>OPTION: Signature Color</H1>
32184 Sets the color Alpine uses for coloring the signature in the MESSAGE TEXT
32185 screen. According to USENET conventions, the signature is defined as the
32186 paragraph following the "sigdashes", that is, the special line
32187 consisting of the three characters
32188 "-- " (i.e., dash, dash, and space). Alpine allows for one
32189 empty line right after the sigdashes to be considered as part of the
32190 signature.
32191 By default, the Signature Color is blue characters on a white background.
32192 <P>
32193 <A HREF="h_color_setup">Descriptions of the available commands</A>
32194 <P>
32195 Look <A HREF="h_edit_nav_cmds">here</A>
32196 to see the available Editing and Navigation commands.
32197 <P>
32198 <End of help on this topic>
32199 </BODY>
32200 </HTML>
32201 ====== h_config_prompt_color =====
32202 <HTML>
32203 <HEAD>
32204 <TITLE>OPTION: Prompt Color</TITLE>
32205 </HEAD>
32206 <BODY>
32207 <H1>OPTION: Prompt Color</H1>
32209 Sets the color Alpine uses for confirmation prompts and questions that
32210 appear in the status line near the bottom of the screen.
32211 The foreground color is the color of the actual character and the
32212 background color is the color of the area behind the character.
32213 By default, the Prompt Color is the same as the Reverse Color.
32214 <P>
32215 <A HREF="h_color_setup">Descriptions of the available commands</A>
32216 <P>
32217 Look <A HREF="h_edit_nav_cmds">here</A>
32218 to see the available Editing and Navigation commands.
32219 <P>
32220 <End of help on this topic>
32221 </BODY>
32222 </HTML>
32223 ====== h_config_header_general_color =====
32224 <HTML>
32225 <HEAD>
32226 <TITLE>OPTION: Header General Color</TITLE>
32227 </HEAD>
32228 <BODY>
32229 <H1>OPTION: Header General Color</H1>
32231 Sets the color Alpine uses for the headers of a message in the MESSAGE TEXT
32232 screen.
32233 The foreground color is the color of the actual character and the
32234 background color is the color of the area behind the character.
32235 By default, this is the same as the Normal Color.
32236 <P>
32237 It is also possible to set the colors for specific header fields, for
32238 example the Subject, using
32239 <A HREF="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></A>.
32240 If both a Header General Color and a specific Viewer Header Color are set
32241 the specific color will override the general color, as you would expect.
32242 <P>
32243 <A HREF="h_color_setup">Descriptions of the available commands</A>
32244 <P>
32245 Look <A HREF="h_edit_nav_cmds">here</A>
32246 to see the available Editing and Navigation commands.
32247 <P>
32248 <End of help on this topic>
32249 </BODY>
32250 </HTML>
32251 ====== h_config_incol =====
32252 <HTML>
32253 <HEAD>
32254 <TITLE>Index Line Color</TITLE>
32255 </HEAD>
32256 <BODY>
32257 <H1>Index Line Color</H1>
32259 This option is used to set the color of a line in the index when the
32260 message for that line matches the Pattern.
32261 This colors the whole index line, except possibly the status letters,
32262 which may be colored separately using the
32263 <A HREF="h_color_setup">Setup Kolor</A> screen.
32264 The foreground color is the color of the actual characters and the
32265 background color is the color of the area behind the characters.
32266 <P>
32267 <A HREF="h_color_setup">Descriptions of the available commands</A>
32268 <P>
32269 Look <A HREF="h_edit_nav_cmds">here</A>
32270 to see the available Editing and Navigation commands.
32271 <P>
32272 <End of help on this topic>
32273 </BODY>
32274 </HTML>
32275 ====== h_config_usetransparent_color =====
32276 <HTML>
32277 <HEAD>
32278 <TITLE>OPTION: Use Transparent Color</TITLE>
32279 </HEAD>
32280 <BODY>
32281 <H1>OPTION: Use Transparent Color</H1>
32283 This is a special color supported by some terminal emulators.
32284 It is intended to result in the default foreground or background color
32285 from the terminal emulator.
32286 This is the color the terminal was displaying characters in before you started Alpine.
32287 The reason it is called Transparent is because you could set the foreground color
32288 to some specific color, like Red, and then set the background color to the
32289 Transparent Color. If it works as expected, the background color from the terminal
32290 window in which Alpine is running will show through but with the Red characters
32291 in the foreground.
32292 <P>
32293 <A HREF="h_color_setup">Descriptions of the available commands</A>
32294 <P>
32295 Look <A HREF="h_edit_nav_cmds">here</A>
32296 to see the available Editing and Navigation commands.
32297 <P>
32298 <End of help on this topic>
32299 </BODY>
32300 </HTML>
32301 ====== h_config_usenormal_color =====
32302 <HTML>
32303 <HEAD>
32304 <TITLE>OPTION: Use Normal Color</TITLE>
32305 </HEAD>
32306 <BODY>
32307 <H1>OPTION: Use Normal Color</H1>
32309 When you use this color value, the actual color used will be the same
32310 as the corresponding Normal Color.
32311 For example if your Normal Color is black on white and you set both
32312 the foreground and background colors here to use the Normal Color, you'll
32313 get black on white. If you later change the Normal Color to red on blue
32314 this color will also change to red on blue.
32315 <P>
32316 <A HREF="h_color_setup">Descriptions of the available commands</A>
32317 <P>
32318 Look <A HREF="h_edit_nav_cmds">here</A>
32319 to see the available Editing and Navigation commands.
32320 <P>
32321 <End of help on this topic>
32322 </BODY>
32323 </HTML>
32324 ====== h_config_usenone_color =====
32325 <HTML>
32326 <HEAD>
32327 <TITLE>OPTION: Use None Color</TITLE>
32328 </HEAD>
32329 <BODY>
32330 <H1>OPTION: Use None Color</H1>
32332 This is a special color that simply means to leave the color alone.
32333 It is useful for Index symbols and for Keyword Colors used in the Subject
32334 field of an index line.
32335 The most likely use is to set an explicit foreground color and then set
32336 the background color to the None Color.
32337 That will cause the symbol or keyword to be drawn in the foreground color
32338 with a background equal to whatever color the rest of the index line is already
32339 drawn in.
32340 You will see no visible effect unless you have assigned Indexcolor Rules to
32341 color index lines or you have set an actual color for the Reverse Color.
32342 <P>
32343 <A HREF="h_color_setup">Descriptions of the available commands</A>
32344 <P>
32345 Look <A HREF="h_edit_nav_cmds">here</A>
32346 to see the available Editing and Navigation commands.
32347 <P>
32348 <End of help on this topic>
32349 </BODY>
32350 </HTML>
32351 ====== h_config_dflt_color =====
32352 <HTML>
32353 <HEAD>
32354 <TITLE>OPTION: Default Color</TITLE>
32355 </HEAD>
32356 <BODY>
32357 <H1>OPTION: Default Color</H1>
32359 Setting default will cause the color to be the default color.
32360 Unsetting default is normally done by choosing a color, but in some cases
32361 you may want to declare the current default color to be your non-default
32362 choice.
32363 For example, the default Keyname Color is the same as the Reverse Color.
32364 Whenever the Reverse Color changes the Keyname Color will also change, unless
32365 you've changed it or unset the default box.
32366 <P>
32367 <A HREF="h_color_setup">Descriptions of the available commands</A>
32368 <P>
32369 Look <A HREF="h_edit_nav_cmds">here</A>
32370 to see the available Editing and Navigation commands.
32371 <P>
32372 <End of help on this topic>
32373 </BODY>
32374 </HTML>
32375 ====== h_config_bold_slctbl =====
32376 <HTML>
32377 <HEAD>
32378 <TITLE>OPTION: Bold</TITLE>
32379 </HEAD>
32380 <BODY>
32381 <H1>OPTION: Bold</H1>
32383 The color for this particular section may have the Bold attribute turned
32384 on or off.
32385 Setting bold will cause the characters to be bold.
32386 <P>
32387 <A HREF="h_color_setup">Descriptions of the available commands</A>
32388 <P>
32389 Look <A HREF="h_edit_nav_cmds">here</A>
32390 to see the available Editing and Navigation commands.
32391 <P>
32392 <End of help on this topic>
32393 </BODY>
32394 </HTML>
32395 ====== h_config_kw_color =====
32396 <HTML>
32397 <HEAD>
32398 <TITLE>OPTION: Keyword Colors</TITLE>
32399 </HEAD>
32400 <BODY>
32401 <H1>OPTION: Keyword Colors</H1>
32403 Sets the colors Alpine uses for Keyword fields in the MESSAGE INDEX screen.
32404 Keywords are displayed as part of the Subject by default.
32405 They are also displayed as part of the Subject if the tokens
32406 "SUBJKEY", "SUBJKEYTEXT", "SUBJKEYINIT", or "SUBJKEYINITTEXT" are used in the
32407 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
32408 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
32409 screen by using the "KEY" or "KEYINIT" tokens.
32410 <P>
32411 For example, you might have set up a Keyword
32412 "Work" using the
32413 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
32414 You could cause that Keyword to show up as a special color
32415 by setting up the Keyword Color using this option, and then including it
32416 in the MESSAGE INDEX screen using one of the tokens listed above in the
32417 <!--#echo var="VAR_index-format"-->.
32418 <P>
32419 <A HREF="h_color_setup">Descriptions of the available commands</A>
32420 <P>
32421 Look <A HREF="h_edit_nav_cmds">here</A>
32422 to see the available Editing and Navigation commands.
32423 <P>
32424 <End of help on this topic>
32425 </BODY>
32426 </HTML>
32427 ====== h_config_customhdr_color =====
32428 <HTML>
32429 <HEAD>
32430 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></TITLE>
32431 </HEAD>
32432 <BODY>
32433 <H1>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></H1>
32435 Sets the colors Alpine uses for specific header fields in the MESSAGE TEXT screen.
32436 For example, you may set the color of the Subject header or the From header.
32437 The foreground color is the color of the actual character and the
32438 background color is the color of the area behind the character.
32439 <P>
32440 In addition to setting the colors for particular headers (like the Subject)
32441 you may also set a color to be used for all headers unless overridden by a
32442 more specific Viewer Header Color.
32443 To do this use the
32444 <A HREF="h_config_header_general_color">Header General Color</A>.
32445 <P>
32446 For Header Colors,
32447 there is an additional line on the
32448 screen labeled "Pattern to match".
32449 If you leave that blank, then the whole field for that header will
32450 be colored.
32451 However, if you give a pattern to match, the coloring will only take place
32452 if there is a match for that pattern in the value of the field.
32453 For example, if you are working on a color for the Subject header and
32454 you fill in a pattern of "important", then only Subjects that
32455 contain the word "important" will be colored.
32456 <P>
32457 If the pattern you enter is a comma-separated list of patterns, then coloring
32458 happens if any of those patterns matches.
32459 <P>
32460 <A HREF="h_color_setup">Descriptions of the available commands</A>
32461 <P>
32462 Look <A HREF="h_edit_nav_cmds">here</A>
32463 to see the available Editing and Navigation commands.
32464 <P>
32465 <End of help on this topic>
32466 </BODY>
32467 </HTML>
32468 ====== h_config_indextoken_color =====
32469 <HTML>
32470 <HEAD>
32471 <TITLE>OPTION: <!--#echo var="VAR_index-token-colors"--></TITLE>
32472 </HEAD>
32473 <BODY>
32474 <H1>OPTION: <!--#echo var="VAR_index-token-colors"--></H1>
32476 This option allows you to set up the color in which any token, not specified by the
32477 previous options, will be colored in the MESSAGE INDEX screen.
32478 <P>
32479 In order to use this option, you must press the "I" <B>IndxHdr</B> command, and add
32480 a token that can be used in the index format.
32481 The list of available tokens is <A HREF="h_index_tokens">here</A>.
32482 <P>
32483 If you fail to enter a valid token your entry will be ignored, and you will be asked to
32484 enter a new one. Once you have entered a valid token, a line will be added to the
32485 configuration screen that you can use to set up the colors in which that token will
32486 be painted. This is done in the same way that you configure colors for other
32487 variables.
32489 <A HREF="h_color_setup">Descriptions of the available commands</A>
32490 <P>
32491 Look <A HREF="h_edit_nav_cmds">here</A>
32492 to see the available Editing and Navigation commands.
32493 <P>
32494 <End of help on this topic>
32495 </BODY>
32496 </HTML>
32497 ====== h_config_customhdr_pattern =====
32498 <HTML>
32499 <HEAD>
32500 <TITLE>OPTION: Viewer Header Color Pattern</TITLE>
32501 </HEAD>
32502 <BODY>
32503 <H1>OPTION: Viewer Header Color Pattern</H1>
32505 If you leave this blank, then the whole field for the header will
32506 be colored.
32507 If you give a pattern to match, the coloring will only take place
32508 if there is a match for that pattern in the value of the field.
32509 For example, if you are working on a color for the Subject header and
32510 you fill in a pattern of "important", then only Subjects that
32511 contain the word "important" will be colored.
32512 <P>
32513 For address headers (like From and To) and for the Newsgroups header,
32514 a pattern match will cause only the matched addresses or newsgroups to be
32515 colored.
32516 If there is no pattern to match, then all of the addresses or newsgroups
32517 in the relevant header will be colored.
32518 <P>
32519 The matching pattern may be a comma-separated list of patterns to match
32520 instead of a single pattern.
32521 For example, you could use the pattern "important,urgent" which would
32522 cause a match if either the word "important" or the word
32523 "urgent" appeared in the value of the header.
32524 You could list several comma-separated email addresses in the Header
32525 From Color pattern so that those addresses will be colored when any of
32526 them appear in the From header.
32527 <P>
32528 To add a new matching pattern or change the existing pattern use the
32529 <!--chtml if pinemode="function_key"-->
32530 "F4"
32531 <!--chtml else-->
32532 "C"
32533 <!--chtml endif-->
32534 "Change" command that is available when the "Pattern to
32535 match" line is highlighted.
32536 The
32537 <!--chtml if pinemode="function_key"-->
32538 "F10"
32539 <!--chtml else-->
32540 "D"
32541 <!--chtml endif-->
32542 "Delete" command may be used to quickly remove all patterns
32543 for a particular header.
32544 <P>
32545 <End of help on this topic>
32546 </BODY>
32547 </HTML>
32548 ====== h_color_setup =====
32549 <HTML>
32550 <HEAD>
32551 <TITLE>SETUP COLOR COMMANDS</TITLE>
32552 </HEAD>
32553 <BODY>
32554 <H1>SETUP COLOR COMMANDS</H1>
32555 <!--chtml if pinemode="function_key"-->
32556 <PRE>
32557 Available Commands -- Group 1
32558 -------------------------------
32559 F1 Display this help text
32560 F2 Show other available commands
32561 F3 Exit to MAIN MENU
32562 F4 Select the highlighted foreground or background color
32563 F5 Move to previous line
32564 F6 Move to next line
32565 F7 Previous page
32566 F8 Next page
32567 F9 Add a config section for a header field
32568 F10 Restore all default colors (for all sections)
32569 F11 Print color configuration screen
32570 F12 Whereis (search for word)
32572 Available Commands -- Group 2
32573 -------------------------------
32574 F1 Display this help text
32575 F2 Show other available commands
32576 F5 Delete config section for highlighted header field
32577 F6 Shuffle the order of Header Color sections
32578 </PRE>
32579 <!--chtml else-->
32580 <PRE>
32581 General commands
32582 -------------------------------------------------
32583 ? Display this help text E Exit back to MAIN MENU
32584 P Previous Line N Next Line
32585 - Previous page Spc (space bar) Next page
32586 W WhereIs (search for word) % Print color configuration screen
32588 Color Setup Commands
32589 ------------------------------------------------
32590 * Select the highlighted foreground or background color
32591 A Add a config section for a header field
32592 D Delete config section for highlighted header field
32593 R Restore all default colors (for all sections)
32594 $ Shuffle the order of Header Color sections
32595 </PRE>
32596 <!--chtml endif-->
32598 <H2>Description of the Setup Color Screen</H2>
32600 From this screen you may turn on color and set the colors of
32601 various parts of the Alpine display.
32602 For help on turning on color move your cursor into the Color Style section
32603 at the top of the Setup Color screen and ask for help.
32605 <P>
32606 There are several sections in the Setup Color Screen.
32607 At the top are some settings that handle the style of color used
32608 with your terminal emulator (UNIX only), and some settings that
32609 control how the current indexline and the titlebar are colored.
32610 After that comes a long section called GENERAL COLORS that allows
32611 you to set the color of many elements in the Alpine screens.
32612 For example, the color of the titlebar, status messages,
32613 selectable links, quotes and signatures in messages, and so on.
32614 After that is a section called INDEX COLORS that allows you to
32615 set the colors of various pieces of the displayed index lines in
32616 the MESSAGE INDEX screen.
32617 The next section is HEADER COLORS. This is for coloring headers of
32618 messages in the MESSAGE TEXT screen in just about any way you would like.
32619 Finally, the KEYWORD COLORS section allows you to highlight
32620 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
32621 in the MESSAGE INDEX screen.
32623 <P>
32624 To change a color, highlight the color you want to change (for example,
32625 the Status Color) by moving
32626 the cursor into it.
32627 You may want to read the help text for the color to see a brief desription
32628 of what you are coloring.
32629 Then press "C" for Change to set the color to something new.
32630 That will put you into a screen with two columns of colors, one for
32631 the foreground color and one for the background color.
32632 The foreground color is just the color you want the actual characters
32633 to be and the background color is the color of the rest of the rectangle
32634 behind the characters.
32635 Select the foreground and background colors desired by using the Next and
32636 Prev keys to highlight the color, and the * command to select it.
32637 <P>
32638 To set a color to its default value, set the X in the Default line at
32639 the bottom of the list of colors.
32640 <P>
32642 The HEADER COLORS section is a little bit different from the others.
32643 Besides coloring the specific fields that Alpine knows about, you may also
32644 color specific header fields when viewing a message in the MESSAGE TEXT
32645 screen.
32646 For example, you may color the Subject header a particular color.
32647 There are a few commands for use with headers.
32648 The "AddHeader" command adds a section to the color
32649 configuration screen that allows you to set the color for that header.
32650 You'll be asked for the name of the header field you want to color.
32651 If you wanted to color the Subject, you would answer
32652 with the word "subject".
32653 Once you've added a header field, the color setting works just like the
32654 other color fields, except that there is an additional line on the
32655 configuration screen labeled "Pattern to match".
32656 If you leave that blank, then the whole field for that header will always
32657 be colored.
32658 However, if you give a pattern to match, the coloring will only take place
32659 if there is a match for that pattern in the value of the field.
32660 For example, if you are working on a color for the Subject header and
32661 you fill in a pattern of "important", then only Subjects that
32662 contain the word "important" will be colored.
32663 <P>
32664 The "DeleteHdr" command removes a header section from the
32665 configuration altogether.
32666 The "Shuffle" command changes the order of header sections.
32667 This is only necessary if you use header sections with pattern fields.
32668 For example, if you have two Subject sections, one with one pattern and
32669 another with another pattern, and the subject for a particular message
32670 happens to match both, then the color from the first match is used.
32671 <P>
32673 The command "RestoreDefs" will restore all of the default colors.
32674 Each section will change to the default value used for that section when
32675 color is first enabled.
32676 When you restore all default colors the color settings for the Header Colors
32677 will be unset (since that's the default), but the header fields you've
32678 added will remain so that you may easily reset them.
32679 In order to get rid of them completely you'd have to use
32680 the "DeleteHdr" command.
32682 <P>
32683 Remember that <A HREF="h_rules_incols">Index Line Colors</A>
32684 may be set with matching rules and that is configured separately from
32685 the rest of the color settings described here.
32686 It is configured in the Setup/Rules/Indexcolors section of the configuration screen
32687 instead of in the Setup/Kolor section.
32689 <P><UL>
32690 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32691 </UL><P>
32692 <End of help on this topic>
32693 </BODY>
32694 </HTML>
32695 ====== h_config_news_uses_recent ======
32696 <HTML>
32697 <HEAD>
32698 <TITLE>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></TITLE>
32699 </HEAD>
32700 <BODY>
32701 <H1>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></H1>
32703 This feature causes certain messages to be marked as "New" in the
32704 MESSAGE INDEX of newsgroups.
32705 This feature is set by default.
32707 <P>
32709 When opening a newsgroup, Alpine will consult your "newsrc" file and
32710 determine the last message you have previously disposed of via the "D"
32711 key. If this feature is set, any subsequent messages will be shown in the
32712 Index with an "N", and the first of these messages will be highlighted.
32713 Although this is only an approximation of true "New" or "Unseen"
32714 status, it provides a useful cue to distinguish more-or-less recent
32715 messages from those you have seen previously, but are not yet ready to
32716 mark deleted.
32718 <P>
32720 Background: your "newsrc" file (used to store message status information
32721 for newsgroups) is only capable of storing a single flag, and Alpine uses
32722 this to record whether or not you are "done with" a message, as
32723 indicated by marking the message as "Deleted". Unfortunately, this
32724 means that Alpine has no way to record exactly which messages you have
32725 previously seen, so it normally does not show the "N" status flag for
32726 any messages in a newsgroup. This feature enables a starting
32727 *approximation* of seen/unseen status that may be useful.
32728 <P>
32729 <End of help on this topic>
32730 </BODY>
32731 </HTML>
32732 ====== h_config_expose_hidden_config =====
32733 <HTML>
32734 <HEAD>
32735 <TITLE>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></TITLE>
32736 </HEAD>
32737 <BODY>
32738 <H1>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></H1>
32740 If set, this causes configuration options and features that are normally
32741 hidden from view to be editable in the Setup/Config screen.
32743 <P>
32744 The purpose of this feature is to allow you to change configuration
32745 features and variables that are normally hidden.
32746 This is particularly useful if you are using a remote configuration,
32747 where it is difficult to edit the contents manually, but it may also be used
32748 on a local pinerc configuration file.
32749 <P>
32750 If set, several configuration variables and features that are normally
32751 hidden from view will show up in the Setup/Configuration screen.
32752 They will be at the bottom of the configuration screen.
32753 You can find them by searching for the words "hidden configuration".
32754 <P>
32756 Note that this is an advanced feature that should be used with care.
32757 The reason that this part of the configuration is normally hidden is because
32758 there is a significant potential for causing problems if you change these
32759 variables.
32760 If something breaks after a change try changing it back to see if that is
32761 what is causing the problem.
32762 There are also some variables that are normally hidden because they are
32763 manipulated through Alpine in other ways.
32764 For example, colors are normally set using the Setup/Kolors screen and
32765 the "<!--#echo var="VAR_address-book"-->" variable is normally set using
32766 the Setup/AddressBooks screen, so there is little reason to edit these directly.
32767 The "<!--#echo var="VAR_incoming-folders"-->" variable is normally changed by using
32768 the Add, Delete, and Rename commands in the FOLDER LIST screen,
32769 and the "<!--#echo var="VAR_last-time-prune-questioned"-->" variable is normally used
32770 internally by Alpine and not set directly by the user.
32771 <P>
32772 <UL>
32773 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32774 </UL><P>
32775 <End of help on this topic>
32776 </BODY>
32777 </HTML>
32778 ====== h_config_disable_signature_edit =====
32779 <HTML>
32780 <HEAD>
32781 <TITLE>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></TITLE>
32782 </HEAD>
32783 <BODY>
32784 <H1>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></H1>
32786 If set, this disables the editing of signature files from within
32787 the Setup/Config screen.
32788 <P>
32789 <UL>
32790 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32791 </UL><P>
32792 <End of help on this topic>
32793 </BODY>
32794 </HTML>
32795 ====== h_config_disable_roles_templateedit =====
32796 <HTML>
32797 <HEAD>
32798 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></TITLE>
32799 </HEAD>
32800 <BODY>
32801 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></H1>
32803 If set, this disables the editing of template files within the
32804 Role setup screen.
32805 <P>
32806 <UL>
32807 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32808 </UL><P>
32809 <End of help on this topic>
32810 </BODY>
32811 </HTML>
32812 ====== h_config_disable_roles_sigedit =====
32813 <HTML>
32814 <HEAD>
32815 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></TITLE>
32816 </HEAD>
32817 <BODY>
32818 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></H1>
32820 If set, this disables the editing of signature files within the
32821 Role setup screen.
32822 <P>
32823 <UL>
32824 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32825 </UL><P>
32826 <End of help on this topic>
32827 </BODY>
32828 </HTML>
32829 ====== h_config_disable_roles_setup =====
32830 <HTML>
32831 <HEAD>
32832 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></TITLE>
32833 </HEAD>
32834 <BODY>
32835 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></H1>
32837 If set, this disables the Setup/Rules/Roles command.
32838 <P>
32839 <UL>
32840 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32841 </UL><P>
32842 <End of help on this topic>
32843 </BODY>
32844 </HTML>
32845 ====== h_config_disable_pipes_in_templates =====
32846 <HTML>
32847 <HEAD>
32848 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></TITLE>
32849 </HEAD>
32850 <BODY>
32851 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></H1>
32853 By default, if a template file name is followed by a vertical bar (|) then
32854 that causes the file to be executed to produce the text for the template.
32855 If this feature is set, then this is not allowed.
32856 <P>
32857 <UL>
32858 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32859 </UL><P>
32860 <End of help on this topic>
32861 </BODY>
32862 </HTML>
32863 ====== h_config_disable_pipes_in_sigs =====
32864 <HTML>
32865 <HEAD>
32866 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></TITLE>
32867 </HEAD>
32868 <BODY>
32869 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></H1>
32871 By default, if a signature file name is followed by a vertical bar (|) then
32872 that causes the file to be executed to produce the text for the signature.
32873 If this feature is set, then this is not allowed.
32874 <P>
32875 <UL>
32876 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32877 </UL><P>
32878 <End of help on this topic>
32879 </BODY>
32880 </HTML>
32881 ====== h_config_disable_password_cmd =====
32882 <HTML>
32883 <HEAD>
32884 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></TITLE>
32885 </HEAD>
32886 <BODY>
32887 <H1>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></H1>
32889 If set, then the Setup/Newpassword command is disabled.
32890 <P>
32891 <UL>
32892 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32893 </UL><P>
32894 <End of help on this topic>
32895 </BODY>
32896 </HTML>
32897 ====== h_config_disable_password_caching =====
32898 <HTML>
32899 <HEAD>
32900 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></TITLE>
32901 </HEAD>
32902 <BODY>
32903 <H1>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></H1>
32905 Normally, loginname/password combinations are cached in Alpine so that
32906 you do not have to enter the same password more than once in a session.
32907 A disadvantage to this approach is that the password must be stored in
32908 the memory image of the running Alpine in order that it can be re-used.
32909 In the event that Alpine crashes and produces a core dump, and that core
32910 dump is readable by others, the loginname and password could be read
32911 from the core dump.
32912 <P>
32913 If this feature is set, then the passwords will not be cached and you
32914 will have to retype the password whenever Alpine needs it.
32915 Even with this feature set there is still some chance that the core
32916 file will contain a password, so care should be taken to make the
32917 core files unreadable.
32918 <P>
32919 NOTE: If PASSFILE caching is enabled, this does not disable it.
32920 That is a separate and independent feature.
32921 <UL>
32922 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32923 </UL><P>
32924 <End of help on this topic>
32925 </BODY>
32926 </HTML>
32927 ====== h_config_disable_password_file_saving =====
32928 <HTML>
32929 <HEAD>
32930 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></TITLE>
32931 </HEAD>
32932 <BODY>
32933 <H1>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></H1>
32935 This feature changes the behavior of Alpine when a login name and password combination
32936 for a specific server is not found in the password file. The default behavior is that
32937 Alpine will ask the user if they wish to save this information in the password file for future
32938 use. It is assumed that if a user created a password file it is because they intend
32939 to use it, but in some instances a user might want to save some passwords and not others.
32940 In this case, enabling this feature will make Alpine not add any more passwords to the
32941 password file and will only use the passwords that it already saved. If you wish to allow
32942 Alpine to save more passwords in the password file, disable this feature.
32943 <P>
32944 <UL>
32945 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32946 </UL><P>
32947 <End of help on this topic>
32948 </BODY>
32949 </HTML>
32950 ====== h_config_disable_kb_lock =====
32951 <HTML>
32952 <HEAD>
32953 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></TITLE>
32954 </HEAD>
32955 <BODY>
32956 <H1>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></H1>
32958 If set, then the Keyboard Lock command is removed from the MAIN MENU.
32959 <P>
32960 <UL>
32961 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32962 </UL><P>
32963 <End of help on this topic>
32964 </BODY>
32965 </HTML>
32966 ====== h_config_disable_config_cmd =====
32967 <HTML>
32968 <HEAD>
32969 <TITLE>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></TITLE>
32970 </HEAD>
32971 <BODY>
32972 <H1>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></H1>
32974 If set, then the Setup/Config screen is disabled.
32975 <P>
32976 <UL>
32977 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32978 </UL><P>
32979 <End of help on this topic>
32980 </BODY>
32981 </HTML>
32982 ====== h_config_allow_chg_from =====
32983 <HTML>
32984 <HEAD>
32985 <TITLE>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></TITLE>
32986 </HEAD>
32987 <BODY>
32988 <H1>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></H1>
32990 This feature affects Alpine's handling of the "From:" header field
32991 in the "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" configuration
32992 option.
32993 <P>
32994 If this feature is set then the From line can be changed just like
32995 all the other header fields that can be changed.
32996 This feature defaults to <EM>ON</EM>.
32997 <P>
32998 Even with this feature turned ON (the default) you will not be able
32999 to change the From header unless you add it to your list of
33000 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>.
33001 You may also want to change the
33002 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
33003 if you want the From header to always show up in the composer without
33004 having to type the Rich Headers command first.
33005 <P>
33006 Note that many sites restrict the use of this feature in order to
33007 reduce the chance of falsified addresses and misdirected mail.
33008 If you want to change the value of what gets included in the From header
33009 in messages you send
33010 look <A HREF="h_config_change_your_from">here</A> for a description.
33011 <P>
33012 <UL>
33013 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33014 </UL><P>
33015 <End of help on this topic>
33016 </BODY>
33017 </HTML>
33018 ====== h_config_disable_collate =====
33019 <HTML>
33020 <HEAD>
33021 <TITLE>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></TITLE>
33022 </HEAD>
33023 <BODY>
33024 <H1>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></H1>
33026 This is a hard to understand feature that should only be used in rare cases.
33027 Normally, the C function call
33028 <P>
33029 <CENTER><SAMP>setlocale(LC_COLLATE, "")</SAMP></CENTER>
33030 <P>
33031 is used by Alpine.
33032 If you want to try turning it off,
33033 setting this feature will turn it off.
33034 This part of the locale has to do with the sort order
33035 of characters in your locale.
33036 <P>
33037 <UL>
33038 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33039 </UL><P>
33040 <End of help on this topic>
33041 </BODY>
33042 </HTML>
33043 ====== h_config_quell_attach_extra_prompt =====
33044 <HTML>
33045 <HEAD>
33046 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></TITLE>
33047 </HEAD>
33048 <BODY>
33049 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></H1>
33051 By default, when you attempt to view an attachment externally
33052 from the "Attachment View" screen, you are asked if you
33053 really want to view the selected attachment.
33055 <P>
33056 If this feature is set, you will <B>not</B> be prompted to confirm
33057 your selection. Prior to Alpine and to Pine 4.50, the default behavior was to not
33058 prompt. This feature was added for those wanting to preserve that
33059 behavior (along with
33060 <A HREF="h_config_quell_attach_ext_warn"><!--#echo var="FEAT_quell-attachment-extension-warn"--></A>).
33062 <P>
33063 <UL>
33064 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33065 </UL><P>
33066 <End of help on this topic>
33067 </BODY>
33068 </HTML>
33069 ====== h_config_quell_attach_ext_warn =====
33070 <HTML>
33071 <HEAD>
33072 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></TITLE>
33073 </HEAD>
33074 <BODY>
33075 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></H1>
33077 <P>
33078 This feature suppresses the extra warning you can get when trying
33079 to view an attachment for which there is no mime-type match. Turning
33080 on this feature will just run the program according to extension
33081 instead of first warning the user that it will run according to the
33082 file's extension.
33083 <P>
33084 This feature can be used along side
33085 <A HREF="h_config_quell_attach_extra_prompt"><!--#echo var="FEAT_quell-attachment-extra-prompt"--></A>
33086 to preserve the behavior exhibited in Pine versions prior to Pine 4.50.
33087 <P>
33088 <UL>
33089 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33090 </UL><P>
33091 <End of help on this topic>
33092 </BODY>
33093 </HTML>
33094 ====== h_config_mailcap_params =====
33095 <HTML>
33096 <HEAD>
33097 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></TITLE>
33098 </HEAD>
33099 <BODY>
33100 <H1>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></H1>
33102 If set, this will allow mailcap named parameter substitution to occur
33103 in mailcap entries.
33104 By default, this is turned off to prevent security problems that may occur
33105 with some incorrect mailcap configurations.
33106 For more information, see RFC1524 and look for "named parameters" in the
33107 text of the RFC.
33108 <P>
33109 <UL>
33110 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33111 </UL><P>
33112 <End of help on this topic>
33113 </BODY>
33114 </HTML>
33115 ====== h_config_disable_shared =====
33116 <HTML>
33117 <HEAD>
33118 <TITLE>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></TITLE>
33119 </HEAD>
33120 <BODY>
33121 <H1>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></H1>
33123 If this feature is set, the automatic search for namespaces "ftp",
33124 "imapshared", and "imappublic" by the underlying library
33125 will be disabled.
33126 The reason this feature exists is because there are some implementations
33127 of system password lookup routines that are very slow when presented with
33128 a long loginname that does not exist.
33129 This feature could be set to prevent the delay at startup time when the
33130 names above are searched for in the password file.
33131 <P>
33132 <UL>
33133 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33134 </UL><P>
33135 <End of help on this topic>
33136 </BODY>
33137 </HTML>
33138 ====== h_config_hide_nntp_path =====
33139 <HTML>
33140 <HEAD>
33141 <TITLE>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></TITLE>
33142 </HEAD>
33143 <BODY>
33144 <H1>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></H1>
33146 Normally the Path header that Alpine generates when posting to a newsgroup
33147 contains the name of the computer from which the message is being sent and
33148 the user name.
33149 Some believe that this information is used by spammers.
33150 If this feature is set, that information will be replaced with the text
33151 <P>
33152 <CENTER><SAMP>not-for-mail</SAMP></CENTER>
33153 <P>
33154 instead.
33155 <P>
33156 It should be noted that many servers being connected to will still reveal
33157 the information that this feature attempts to protect.
33158 <P>
33159 <UL>
33160 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33161 </UL><P>
33162 <End of help on this topic>
33163 </BODY>
33164 </HTML>
33165 ====== h_config_no_bezerk_zone =====
33166 <HTML>
33167 <HEAD>
33168 <TITLE>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></TITLE>
33169 </HEAD>
33170 <BODY>
33171 <H1>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></H1>
33173 POSIX mandates a timezone in UNIX mailbox format folder delimiters
33174 (the line that begins with From <SPACE>).
33175 Some versions of Berkeley mail have trouble with this, and don't recognize
33176 the line as a message delimiter.
33177 If this feature is set, the timezone will be left off the delimiter line.
33178 <P>
33179 <UL>
33180 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33181 </UL><P>
33182 <End of help on this topic>
33183 </BODY>
33184 </HTML>
33185 ====== h_config_quell_domain_warn =====
33186 <HTML>
33187 <HEAD>
33188 <TITLE>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></TITLE>
33189 </HEAD>
33190 <BODY>
33191 <H1>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></H1>
33193 When your configuration is set up so that your domain name contains no dots,
33194 it is usually a configuration error.
33195 By default, Alpine will warn you about this when you start it up.
33196 You will see a warning message that looks like
33198 <P>
33199 <CENTER><SAMP>Incomplete maildomain "<domain>".</SAMP></CENTER>
33201 <P>
33202 If this feature is set, the warning is turned off.
33203 <P>
33204 <UL>
33205 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33206 </UL><P>
33207 <End of help on this topic>
33208 </BODY>
33209 </HTML>
33210 ====== h_config_quell_imap_env =====
33211 <HTML>
33212 <HEAD>
33213 <TITLE>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></TITLE>
33214 </HEAD>
33215 <BODY>
33216 <H1>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></H1>
33218 In the MESSAGE INDEX screen, if the open folder is being accessed
33219 using IMAP, Alpine normally tries to paint the index lines on the screen
33220 as soon as the information arrives from the IMAP server.
33221 This means that the index information makes it onto the screen more quickly
33222 than it otherwise would.
33223 This sometimes results in behavior that bothers some users.
33224 For example, when paging to a new page of the index, it may be possible for
33225 the lines to be painted on the screen in a random order, rather than from
33226 top to bottom.
33227 <P>
33229 Setting this feature causes Alpine to wait for all of the information
33230 to be gathered before it paints the index screen.
33231 Once it collects all of the information, the screen will be painted quickly
33232 from top to bottom.
33233 <P>
33234 <UL>
33235 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33236 </UL><P>
33237 <End of help on this topic>
33238 </BODY>
33239 </HTML>
33240 ====== h_config_quell_news_env =====
33241 <HTML>
33242 <HEAD>
33243 <TITLE>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></TITLE>
33244 </HEAD>
33245 <BODY>
33246 <H1>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></H1>
33248 In the MESSAGE INDEX screen, if the open folder is being accessed
33249 using NNTP (News), Alpine normally tries to paint the index lines on the screen
33250 as soon as the information arrives from the NNTP server.
33251 This means that the index information makes it onto the screen more quickly
33252 than it otherwise would.
33253 This sometimes results in behavior that bothers some users.
33254 For example, when paging to a new page of the index, it may be possible for
33255 the lines to be painted on the screen in a random order, rather than from
33256 top to bottom.
33257 <P>
33259 Setting this feature causes Alpine to wait for all of the information
33260 to be gathered before it paints the index screen.
33261 Once it collects all of the information, the screen will be painted quickly
33262 from top to bottom.
33263 <P>
33264 <UL>
33265 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33266 </UL><P>
33267 <End of help on this topic>
33268 </BODY>
33269 </HTML>
33270 ====== h_config_quell_content_id =====
33271 <HTML>
33272 <HEAD>
33273 <TITLE>FEATURE: <!--#echo var="FEAT_quell-content-id"--></TITLE>
33274 </HEAD>
33275 <BODY>
33276 <H1>FEATURE: <!--#echo var="FEAT_quell-content-id"--></H1>
33278 This feature changes the behavior of Alpine when sending messages.
33279 It is intended to work around a bug in Microsoft's Outlook XP mail user
33280 agent.
33281 As of this writing, Microsoft has acknowledged the bug but
33282 has not added it to the Knowledge Base.
33283 We have been told that there will be a post-SP1 hotfix for Outlook XP.
33284 This particular bug has bug fix number OfficeQFE:4781.
33285 The nature of the bug is that messages with attachments that
33286 contain a Content-ID header (which standard Alpine attachments do)
33287 do not show the attachment indicator (a paperclip) when viewed with
33288 Outlook XP.
33289 So the user has no indication that the message contains an attachment.
33291 <P>
33292 If this feature is set then Alpine will remove most Content-ID headers
33293 before sending a message.
33294 If an attachment is of type MESSAGE, then the existing Content-ID headers
33295 inside the message will be left intact.
33296 This would only happen with Alpine if a message was forwarded as an attachment
33297 or if a message with a message attached was forwarded.
33298 Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded,
33299 the Content-ID headers of the alternative parts will not be removed.
33301 <P>
33302 Because the Content-ID header is a standard part of MIME it is possible
33303 that setting this feature will break something.
33304 For example, if an attachment has a Content-ID header that is necessary
33305 for the correct functioning of that attachment, it is possible that Alpine
33306 may remove that header when the attachment is forwarded.
33307 However, it seems fairly safe at this time.
33309 <P>
33310 <UL>
33311 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33312 </UL><P>
33313 <End of help on this topic>
33314 </BODY>
33315 </HTML>
33316 ====== h_config_winpos_in_config =====
33317 <HTML>
33318 <HEAD>
33319 <TITLE>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></TITLE>
33320 </HEAD>
33321 <BODY>
33322 <H1>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></H1>
33324 PC-Alpine only.
33325 <P>
33327 Normally, PC-Alpine will store its window size and position in the
33328 Windows Registry.
33329 This is convenient if you want to use the same remote
33330 configuration from more than one PC.
33331 If you use multiple configuration files to start PC-Alpine, you may want
33332 to store the window size and position in the configuration file instead
33333 of in the Registry.
33334 Setting this feature causes the value to be stored in
33335 <A HREF="h_config_window_position">Window-Position</A>.
33337 <P>
33338 <UL>
33339 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33340 </UL><P>
33341 <End of help on this topic>
33342 </BODY>
33343 </HTML>
33344 ====== h_config_quell_ssl_largeblocks =====
33345 <HTML>
33346 <HEAD>
33347 <TITLE>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></TITLE>
33348 </HEAD>
33349 <BODY>
33350 <H1>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></H1>
33352 PC-Alpine only.
33353 <P>
33354 This feature changes the behavior of fetching messages
33355 and attachments so that the message data is fetched in chunks no larger
33356 than 12K bytes.
33357 This works around a bug in Microsoft's SSL/TLS support.
33358 Some versions of Microsoft SSL are not able to read full-sized (16K)
33359 SSL/TLS packets.
33360 Some servers will send such packets and this will
33361 cause PC-Alpine to crash with the error
33363 <P>
33364 <CENTER><SAMP>incomplete SecBuffer exceeds maximum buffer size</SAMP></CENTER>
33366 <P>
33367 Microsoft is aware of the problem and has developed a hotfix for it, it is
33368 discussed in article 300562 in the Microsoft Knowledge Base.
33369 <P>
33370 <UL>
33371 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33372 </UL><P>
33373 <End of help on this topic>
33374 </BODY>
33375 </HTML>
33376 ====== h_config_quell_partial =====
33377 <HTML>
33378 <HEAD>
33379 <TITLE>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></TITLE>
33380 </HEAD>
33381 <BODY>
33382 <H1>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></H1>
33384 Partial fetching is a feature of the IMAP protocol.
33385 By default, Alpine
33386 will use partial fetching when copying the contents of a message or attachment
33387 from the IMAP server to Alpine.
33388 This means that the fetch will be done in many
33389 small chunks instead of one big chunk. The main benefit of this approach is
33390 that the fetch becomes interruptible. That is, the user can type <EM>^C</EM>
33391 to stop the fetch early. In some cases partial fetching may cause a performance
33392 problem so that the fetching of data takes significantly longer when partial
33393 fetching is used. Turning on this feature will turn off partial fetching.
33394 <P>
33395 <UL>
33396 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33397 </UL><P>
33398 <End of help on this topic>
33399 </BODY>
33400 </HTML>
33401 ====== h_config_quell_personal_name_prompt =====
33402 <HTML>
33403 <HEAD>
33404 <TITLE>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></TITLE>
33405 </HEAD>
33406 <BODY>
33407 <H1>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></H1>
33409 PC-Alpine only. This feature quells the prompting for a
33410 <A HREF="h_config_pers_name">personal name</A>. This
33411 prompt normally happens before composing a message, and only happens when
33412 there is no personal name already set.
33413 <P>
33414 <UL>
33415 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33416 </UL><P>
33417 <End of help on this topic>
33418 </BODY>
33419 </HTML>
33420 ====== h_config_quell_user_id_prompt =====
33421 <HTML>
33422 <HEAD>
33423 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></TITLE>
33424 </HEAD>
33425 <BODY>
33426 <H1>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></H1>
33428 PC-Alpine only. This feature quells the prompting for a
33429 <A HREF="h_config_user_id"><!--#echo var="VAR_user-id"--></A>
33430 if the information can be obtained from the login name used
33431 to open the INBOX. Normally, this prompt happens before composing
33432 a message, and only happens when there is no user-id already set
33433 in the configuration.
33434 <P>
33435 With this feature set, composing a message is only possible after
33436 establishing a connection to the INBOX.
33437 <P>
33438 <UL>
33439 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33440 </UL><P>
33441 <End of help on this topic>
33442 </BODY>
33443 </HTML>
33444 ====== h_config_save_aggregates =====
33445 <HTML>
33446 <HEAD>
33447 <TITLE>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></TITLE>
33448 </HEAD>
33449 <BODY>
33450 <H1>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></H1>
33452 This feature will optimize an aggregate copy operation, if
33453 possible, by issuing a single IMAP <EM>COPY</EM> command with a
33454 list of the messages to be copied.
33455 This feature is set by default.
33456 This may reduce network traffic and elapsed time for the Save.
33457 <EM>However, many IMAP servers (including the UW IMAP server) do
33458 not preserve the order of messages when this optimization is applied.</EM>
33459 If this feature is not set,
33460 Alpine will copy each message individually and the order of the messages
33461 will be preserved.
33462 <P>
33463 <UL>
33464 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33465 </UL><P>
33466 <End of help on this topic>
33467 </BODY>
33468 </HTML>
33469 ====== h_config_use_system_translation =====
33470 <HTML>
33471 <HEAD>
33472 <TITLE>FEATURE: Use System Translation</TITLE>
33473 </HEAD>
33474 <BODY>
33475 <H1>FEATURE: Use System Translation</H1>
33477 UNIX Alpine only.
33478 <P>
33479 Alpine normally uses its own internal software to convert between the multi-byte
33480 representation of characters and the Unicode representation of those
33481 same characters.
33482 It converts from the multi-byte characters your keyboard produces to Unicode,
33483 and from Unicode to the multi-byte characters your display expects.
33484 Alpine also uses its own internal software to decide how much space on
33485 the screen a particular Unicode character will occupy.
33487 <P>
33488 Setting this feature tells Alpine to use the system-supplied routines to
33489 perform these tasks instead.
33490 In particular there are three tasks and three system routines that will
33491 be used for these tasks.
33493 <P>
33494 To convert from multi-byte to Unicode the routine
33496 <P>
33497 <CENTER><SAMP>mbstowcs</SAMP></CENTER>
33498 <P>
33500 is used.
33501 To convert from Unicode to multi-byte the routine
33503 <P>
33504 <CENTER><SAMP>wcrtomb</SAMP></CENTER>
33505 <P>
33507 is used.
33508 And to find the screen width a particular Unicode character will
33509 occupy the routine used is
33511 <P>
33512 <CENTER><SAMP>wcwidth</SAMP></CENTER>
33513 <P>
33515 This feature has been only lightly tested.
33516 The internal routines should normally be used unless you run into
33517 a problem that you think may be solved by using the system routines.
33518 Note that your environment needs to be set up for these
33519 routines to work correctly.
33520 In particular, the LANG or LC_CTYPE variable in your environment will
33521 need to be set.
33523 <P>
33524 <UL>
33525 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33526 </UL><P>
33527 <End of help on this topic>
33528 </BODY>
33529 </HTML>
33530 ====== h_config_suspend_spawns =====
33531 <HTML>
33532 <HEAD>
33533 <TITLE>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></TITLE>
33534 </HEAD>
33535 <BODY>
33536 <H1>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></H1>
33538 This feature affects Alpine's behavior when process suspension is enabled
33539 and then activated via the Ctrl-Z key. Alpine suspension allows one to
33540 temporarily interact with the operating system command "shell"
33541 without
33542 quitting Alpine, and then subsequently resume the still-active Alpine session.
33543 <P>
33545 When the <A HREF="h_config_can_suspend">"<!--#echo var="FEAT_enable-suspend"-->"</A> feature
33546 is set and subsequently the Ctrl-Z key
33547 is pressed, Alpine will normally suspend itself and return temporary control
33548 to Alpine's parent shell process. However, if this feature is set, Alpine
33549 will instead create an inferior subshell process. This is useful when the
33550 parent process is not intended to be used interactively. Examples include
33551 invoking Alpine via the -e argument of the Unix "xterm" program,
33552 or via a menu system.<P>
33554 Note that one typically resumes a suspended Alpine by entering the Unix
33555 "fg" command, but if this feature is set, it will be necessary to
33556 enter the "exit" command instead.
33557 <P>
33558 <UL>
33559 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33560 </UL><P>
33561 <End of help on this topic>
33562 </BODY>
33563 </HTML>
33564 ====== h_config_8bit_smtp =====
33565 <HTML>
33566 <HEAD>
33567 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></TITLE>
33568 </HEAD>
33569 <BODY>
33570 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></H1>
33572 This feature affects Alpine's behavior when sending mail.
33573 By default, this feature is set.
33574 Internet standards
33575 require that all electronic mail messages traversing the global Internet
33576 consist of 7bit ASCII characters unless a pair of cooperating mail
33577 transfer agents explicitly agree to allow 8bit messages. In general,
33578 then, exchanging messages in non-ASCII characters requires MIME encoding.
33579 <P>
33580 However, there are now Internet standards that allow for unencoded 8bit
33581 exchange of messages between cooperating systems. When this feature is set
33582 Alpine will try to negotiate unencoded 8bit transmission during the
33583 sending process. Should the negotiation fail, Alpine will fall back to its
33584 ordinary encoding rules.
33585 <P>
33586 Note, this feature relies on your system's mail transport agent or
33587 configured <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
33588 having the negotiation mechanism introduced in
33589 "Extended SMTP" (ESMTP) and the specific extension called
33590 "8BITMIME".
33591 <P>
33592 ESMTP allows for graceful migration to upgraded mail transfer agents, but
33593 it is possible that this feature might cause problems for some servers.
33594 <P><UL>
33595 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33596 </UL>
33597 <P><End of help on this topic>
33598 </BODY>
33599 </HTML>
33600 ====== h_config_8bit_nntp =====
33601 <HTML>
33602 <HEAD>
33603 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></TITLE>
33604 </HEAD>
33605 <BODY>
33606 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></H1>
33608 This feature affects Alpine's behavior when posting news.
33610 <P>
33612 The Internet standard for exchanging USENET news messages (RFC-1036)
33613 specifies that USENET messages should conform to Internet mail standards
33614 and contain only 7bit characters, but much of the news transport software
33615 in use today is capable of successfully sending messages containing 8bit
33616 characters. Hence, many people believe that it is appropriate to send 8bit
33617 news messages without any MIME encoding.
33619 <P>
33621 Moreover, there is no Internet standard for explicitly negotiating 8bit
33622 transfer, as there is for Internet email. Therefore, Alpine provides the
33623 option of posting unencoded 8bit news messages, though not as the default.
33624 Setting this feature will turn OFF Alpine's MIME encoding of newsgroup
33625 postings that contain 8bit characters.
33627 <P>
33629 Note, articles may cross a path or pass through news transport software
33630 that is unsafe or even hostile to 8bit characters. At best this will only
33631 cause the posting to become garbled. The safest way to transmit 8bit
33632 characters is to leave Alpine's MIME encoding turned on, but recipients
33633 who lack MIME-aware tools are often annoyed when they receive MIME-encoded
33634 messages.
33635 <P>
33636 <End of help on this topic>
33637 </BODY>
33638 </HTML>
33639 ====== h_config_mark_for_cc =====
33640 <HTML>
33641 <HEAD>
33642 <TITLE>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></TITLE>
33643 </HEAD>
33644 <BODY>
33645 <H1>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></H1>
33647 This feature affects Alpine's MESSAGE INDEX display.
33648 By default, a '+' is displayed in the first column if the
33649 message is addressed directly to you.
33650 When this feature is set and the message is not addressed to you, then a
33651 '-' character is displayed if the message is instead Cc'd directly
33652 to you.
33654 <P>
33655 <UL>
33656 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33657 </UL><P>
33658 <End of help on this topic>
33659 </BODY>
33660 </HTML>
33661 ====== h_config_tab_uses_unseen =====
33662 <HTML>
33663 <HEAD>
33664 <TITLE>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></TITLE>
33665 </HEAD>
33666 <BODY>
33667 <H1>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></H1>
33669 This feature affects Alpine's behavior when using the TAB
33670 <A HREF="h_common_nextnew">NextNew Command</A>
33671 to move from one folder to the next.
33672 Alpine's usual behavior is to search for folders
33673 with <EM>Recent</EM> messages in them.
33674 Recent messages are messages that have arrived since the last time the
33675 folder was opened.
33677 <P>
33678 Setting this feature causes Alpine to search for <EM>Unseen</EM>
33679 messages instead of Recent messages.
33680 Unseen messages remain Unseen until you view them (or flag then as Seen with
33681 the <A HREF="h_common_flag">Flag Command</A>).
33682 Setting this feature allows you to locate messages you have not read
33683 instead of only recently received messages.
33684 When this feature is set, the feature
33685 <A HREF="h_config_fast_recent">"<!--#echo var="FEAT_enable-fast-recent-test"-->"</A>
33686 will have no effect, so the checking may be slower.
33688 <P>
33689 Another reason why you might want to use this feature is that Alpine sometimes
33690 opens folders implicitly behind the scenes, and this clears the
33691 Recent status of all messages in the folder.
33692 One example where this happens is when Saving or filtering a
33693 message to another folder.
33694 If that message has some <A HREF="h_config_keywords">keywords</A>
33695 set, then because of some shortcomings
33696 in the IMAP specification, the best way to ensure that those keywords are
33697 still set in the saved copy of the message is to open the folder and
33698 set the keywords explicitly.
33699 Because this clears the Recent status of all messages in that folder the
33700 folder will not be found by the NextNew command unless this feature is set.
33702 <P>
33703 <End of help on this topic>
33704 </BODY>
33705 </HTML>
33706 ====== h_config_tab_new_only =====
33707 <HTML>
33708 <HEAD>
33709 <TITLE>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></TITLE>
33710 </HEAD>
33711 <BODY>
33712 <H1>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></H1>
33714 This feature affects Alpine's behavior when using the TAB key to move from
33715 one message to the next. Alpine's usual behavior is to select the next
33716 unread message or message flagged as "Important".
33718 <P>
33720 Setting this feature causes Alpine to skip the messages flagged as important,
33721 and select unread messages exclusively. Tab behavior when there are no
33722 new messages left to select remains unchanged.
33723 <P>
33724 <End of help on this topic>
33725 </BODY>
33726 </HTML>
33727 ====== h_config_warn_if_subj_blank =====
33728 <HTML>
33729 <HEAD>
33730 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></TITLE>
33731 </HEAD>
33732 <BODY>
33733 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></H1>
33735 This feature affects Alpine's behavior when you send a message being
33736 composed.
33737 If this option is set, Alpine will check to see if the message about to be sent
33738 has a subject or not.
33739 If not, you will be asked if you want to send the message anyway.
33740 <P>
33742 <UL>
33743 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33744 </UL><P>
33745 <End of help on this topic>
33746 </BODY>
33747 </HTML>
33748 ====== h_config_warn_if_fcc_blank =====
33749 <HTML>
33750 <HEAD>
33751 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></TITLE>
33752 </HEAD>
33753 <BODY>
33754 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></H1>
33756 This feature affects Alpine's behavior when you send a message being
33757 composed.
33758 If this option is set, Alpine will check to see if the message about to be sent
33759 has an Fcc or not.
33760 If not, you will be asked if you want to send the message anyway.
33761 <P>
33763 <UL>
33764 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33765 </UL><P>
33766 <End of help on this topic>
33767 </BODY>
33768 </HTML>
33769 ====== h_config_warn_if_no_to_or_cc =====
33770 <HTML>
33771 <HEAD>
33772 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></TITLE>
33773 </HEAD>
33774 <BODY>
33775 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></H1>
33777 This feature affects Alpine's behavior when you send a message being
33778 composed.
33779 If this option is set, Alpine will check to see if the message about to be sent
33780 has either a To address, a Cc address, or a Newsgroup.
33781 If none of these is set,
33782 you will be asked if you want to send the message anyway.
33783 <P>
33785 This feature is closely related to
33786 <A HREF="h_config_auto_fcc_only"><!--#echo var="FEAT_fcc-only-without-confirm"--></A>.
33787 Alpine will normally ask if you want to copy a message only to the Fcc.
33788 This feature also applies to cases where there is a Bcc but still no To, Cc,
33789 or Newsgroup.
33790 If the <!--#echo var="FEAT_fcc-only-without-confirm"--> feature is set and you are sending a
33791 message with only an Fcc, then you won't be asked about sending with
33792 a blank To and Cc and Newsgroups header even if this feature is set.
33793 Similarly, if you have already been asked if you want to send to the Fcc
33794 only and you have answered Yes, then you won't be asked again about sending with
33795 blank To, Cc, and Newsgroups headers even if this feature is set.
33796 <P>
33798 <UL>
33799 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33800 </UL><P>
33801 <End of help on this topic>
33802 </BODY>
33803 </HTML>
33804 ====== h_config_quell_dead_letter =====
33805 <HTML>
33806 <HEAD>
33807 <TITLE>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></TITLE>
33808 </HEAD>
33809 <BODY>
33810 <H1>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></H1>
33812 This feature affects Alpine's behavior when you cancel a message being
33813 composed. Alpine's usual behavior is to write the canceled message to
33814 a file named
33815 <!--chtml if pinemode="os_windows"-->
33816 "DEADLETR",
33817 <!--chtml else-->
33818 "dead.letter" in your home directory,
33819 <!--chtml endif-->
33820 overwriting any previous message. Under
33821 some conditions (some routine), this can introduce a noticeable delay.
33822 Setting this feature will cause Alpine NOT to write canceled compositions
33823 into the file.
33824 <P>
33825 NOTE: Enabling this feature means NO record of canceled messages is
33826 maintained.
33827 <P>
33828 This feature affects the newer option
33829 <A HREF="h_config_deadlets"><!--#echo var="VAR_dead-letter-files"--></A>, which specifies the
33830 number of dead letter files to keep around.
33831 If this feature is set, then the <!--#echo var="VAR_dead-letter-files"--> option has no effect.
33832 <P>
33833 <UL>
33834 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33835 </UL><P>
33836 <End of help on this topic>
33837 </BODY>
33838 </HTML>
33839 ====== h_config_quell_beeps =====
33840 <HTML>
33841 <HEAD>
33842 <TITLE>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></TITLE>
33843 </HEAD>
33844 <BODY>
33845 <H1>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></H1>
33847 This feature affects Alpine's behavior when it displays status message
33848 (e.g., Error complaints, New mail warnings, etc). Setting this feature
33849 will not affect the display of such messages, but will cause those that
33850 emit a beep to become silent.
33852 <P>
33853 <UL>
33854 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33855 </UL><P>
33856 <End of help on this topic>
33857 </BODY>
33858 </HTML>
33859 ====== h_config_suppress_user_agent =====
33860 <HTML>
33861 <HEAD>
33862 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></TITLE>
33863 </HEAD>
33864 <BODY>
33865 <H1>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></H1>
33867 If this feature is set then Alpine will not generate a
33868 <CODE>User-Agent</CODE> header in outgoing messages.
33869 <P>
33870 <UL>
33871 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33872 </UL><P>
33873 <End of help on this topic>
33874 </BODY>
33875 </HTML>
33876 ====== h_config_quell_lock_failure_warnings =====
33877 <HTML>
33878 <HEAD>
33879 <TITLE>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></TITLE>
33880 </HEAD>
33881 <BODY>
33882 <H1>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></H1>
33884 This feature affects Alpine's behavior when it encounters a problem
33885 acquiring a mail folder lock. Typically, a secondary file associated
33886 with the mail folder being opened is created as part of the locking
33887 process. On some systems, such file creation has been administratively
33888 precluded by the system configuration.
33889 <P>
33890 Alpine issues a warning when such failures occur, which can become bothersome
33891 if the system is configured to disallow such actions. Setting this
33892 feature causes Alpine to remain silent when this part of lock creation fails.
33893 <P>
33894 WARNING: systems that have been configured in a way that precludes locking
33895 introduce some risk of mail folder corruption when more than one program
33896 attempts to modify the mail folder. This is most likely to occur to one's
33897 INBOX or other incoming message folder.
33898 <P>
33899 See also <A HREF="h_info_on_locking">"What Systems Managers Need to Know about Alpine File Locking"</A>.
33900 <P>
33901 <UL>
33902 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33903 </UL><P>
33904 <End of help on this topic>
33905 </BODY>
33906 </HTML>
33907 ====== h_config_enable_role_take ======
33908 <HTML>
33909 <HEAD>
33910 <TITLE>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></TITLE>
33911 </HEAD>
33912 <BODY>
33913 <H1>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></H1>
33915 Normally, the Take command takes addresses from a message and helps you
33916 put them into your Address Book.
33917 If you use Rules for Indexcolors, Roles, Filtering, or Scoring;
33918 you may find it useful
33919 to be able to Take information from a message's headers and put it into
33920 a new Rule.
33921 When this feature is set, you will be given an extra prompt that gives
33922 you the choice to Take into the Address Book or Take into a rule.
33923 <P><UL>
33924 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33925 </UL>
33926 <P>
33927 <End of help on this topic>
33928 </BODY>
33929 </HTML>
33930 ====== h_config_enable_take_export ======
33931 <HTML>
33932 <HEAD>
33933 <TITLE>FEATURE: <!--#echo var="FEAT_enable-take-export"--></TITLE>
33934 </HEAD>
33935 <BODY>
33936 <H1>FEATURE: <!--#echo var="FEAT_enable-take-export"--></H1>
33938 Normally, the Take command takes addresses from a message and helps you
33939 put them into your Address Book.
33940 When this feature is set, you will be given an extra prompt that gives you
33941 the choice to Take addresses into a file instead of your Address
33942 Book.
33943 Only the user@domain_name part of the address is put in the file.
33944 <P><UL>
33945 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33946 </UL>
33947 <P>
33948 <End of help on this topic>
33949 </BODY>
33950 </HTML>
33951 ====== h_config_quell_folder_internal_msg ======
33952 <HTML>
33953 <HEAD>
33954 <TITLE>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></TITLE>
33955 </HEAD>
33956 <BODY>
33957 <H1>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></H1>
33959 This feature determines whether or not Alpine will create
33960 "pseudo messages" in folders that are in standard Unix or
33961 MMDF format. <P>
33963 Alpine will normally create these pseudo messages when they are not already
33964 present in a standard Unix or MMDF folder. Their purpose is to record
33965 certain mailbox state data needed for correct IMAP and POP server
33966 operation, and also for Alpine to be able to mark messages as Answered when
33967 the Reply has been postponed.<P>
33969 Sites that do not use IMAP/POP for remote mail access, and that need to
33970 support mail tools that are adversely affected by the presence of the
33971 pseudo-messages (e.g. some mail notification tools) may enable this
33972 feature to tell Alpine not to create them. Note that Alpine's
33973 "Answered" flag
33974 capability will be adversely affected if this is done.<P>
33976 Note too that, even if this feature is enabled, Alpine will not remove
33977 pseudo-messages when it encounters them (e.g. those created by UW's imapd
33978 or ipopd servers.) This feature has no effect on folders that are not in
33979 standard Unix or MMDF format, as pseudo-messages are not needed in the
33980 other formats to record mailbox state information.
33981 <P><UL>
33982 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33983 </UL>
33984 <P>
33985 <End of help on this topic>
33986 </BODY>
33987 </HTML>
33988 ====== h_config_mulnews_as_typed ======
33989 <HTML>
33990 <HEAD>
33991 <TITLE>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></TITLE>
33992 </HEAD>
33993 <BODY>
33994 <H1>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></H1>
33996 This feature will be of little use to most users.
33997 It has no effect unless the feature
33998 <A HREF="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></A>
33999 is set.
34001 When the <!--#echo var="FEAT_enable-multiple-newsrcs"--> feature is set
34002 then the setting of this feature may have an effect on the names of the
34003 newsrc files used.
34004 Normally, the name of the news server will be canonicalized before it is
34005 used in the newsrc file name.
34006 For example, if you type the news server name
34008 <P>
34009 <CENTER><SAMP>servername</SAMP></CENTER>
34010 <P>
34012 it is likely that the canonical name will be something like
34014 <P>
34015 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
34016 <P>
34018 Or it may be the case that
34020 <P>
34021 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
34022 <P>
34024 is really an alias (a DNS CNAME) for
34026 <P>
34027 <CENTER><SAMP>othername.example.com</SAMP></CENTER>
34028 <P>
34030 If this feature is not set, then the canonicalized names will be used.
34031 If this feature is set, then the name you typed in (or put in your
34032 configuration) will be used.
34034 <P><UL>
34035 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34036 </UL>
34037 <P>
34038 <End of help on this topic>
34039 </BODY>
34040 </HTML>
34041 ====== h_config_quell_empty_dirs ======
34042 <HTML>
34043 <HEAD>
34044 <TITLE>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></TITLE>
34045 </HEAD>
34046 <BODY>
34047 <H1>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></H1>
34049 This feature causes Alpine to remove from the display any directories
34050 that do not contain at least one file or directory. This can be useful
34051 to prevent overly cluttered folder lists when a collection is stored on
34052 a server that treats all names as both a folder and a directory.
34054 <P>
34055 Note, enabling this feature can cause surprising behavior! For example,
34056 you can still use Add to create a directory, but unless you immediately
34057 enter that directory and create a folder, that newly created directory
34058 may not be displayed next time you enter the folder list.
34060 <P>
34061 The description above is not quite correct.
34062 Only directories which potentially may hold messages are hidden if empty.
34063 That is, a directory which is really just a directory and is not selectable
34064 as a folder will not be hidden.
34065 Such directories can occur on servers that treat most names as both a folder
34066 and a directory.
34067 These directories are typically created implicitly when a folder is created
34068 inside a directory that does not yet exist.
34070 <P>
34071 <UL>
34072 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34073 </UL><P>
34074 <End of help on this topic>
34075 </BODY>
34076 </HTML>
34077 ====== h_config_termcap_wins =====
34078 <HTML>
34079 <HEAD>
34080 <TITLE>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></TITLE>
34081 </HEAD>
34082 <BODY>
34083 <H1>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></H1>
34085 This feature may affect Alpine's low-level input routines. Termcap (or
34086 terminfo, depending on how your copy of Alpine was compiled and linked)
34087 is the name of the database that describes terminal capabilities. In
34088 particular, it describes the sequences of characters that various keys
34089 will emit.
34091 <P>
34092 An example would be the Up Arrow key on the keyboard. Up
34093 Arrow is not a distinct character on most Unix systems. When you press
34094 the Up Arrow key a short sequence of characters are produced. This
34095 sequence is supposed to be described in the termcap database by the
34096 "ku" capability (or by the "kcuu1" capability if you
34097 are using terminfo instead of termcap).
34099 <P>
34100 By default, Alpine defines some terminal
34101 escape sequences that are commonly used. For example, the sequence
34102 "ESC O A" is recognized as an Up Arrow key. The sequence
34103 "ESC [ A"
34104 is also recognized as an Up Arrow key. These are chosen because common
34105 terminals like VT100's or ANSI standard terminals produce these
34106 sequences when you press the Up Arrow key.
34108 <P>
34109 If your system's termcap
34110 (terminfo) database assigns some other function to the sequence
34111 "ESC O A"
34112 it is usually ignored by Alpine. Also, if your termcap (terminfo)
34113 database assigns a sequence that doesn't begin with an escape
34114 character (<SAMP>ESC</SAMP>) it is usually ignored by Alpine.
34115 This usually works fine
34116 because most terminals emit the escape sequences that Alpine has defined
34117 by default. We have also found that it is usually better to have these
34118 defaults take precedence over the definitions contained in the database
34119 because the defaults are more likely to be correct than the database.
34121 <P>
34122 There are some terminals where this breaks down. If you want Alpine to
34123 believe the definitions given in your termcap (terminfo) database in
34124 preference to the defaults the Alpine itself sets up, then you may turn
34125 this feature on. Then, sequences of characters that are defined in
34126 both termcap (terminfo) and in Alpine's set of defaults will be
34127 interpreted the way that termcap (terminfo) says they should be
34128 interpreted. Also, if your terminal capabilities database assigns a
34129 sequence that doesn't begin with escape, it will not be ignored.
34131 <P>
34132 <UL>
34133 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34134 </UL><P>
34135 <End of help on this topic>
34136 </BODY>
34137 </HTML>
34138 ====== h_config_cruise_mode =====
34139 <HTML>
34140 <HEAD>
34141 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></TITLE>
34142 </HEAD>
34143 <BODY>
34144 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></H1>
34146 This feature affects Alpine's behavior when you hit the
34147 "Space Bar" at
34148 the end of a displayed message. Typically, Alpine complains that the end
34149 of the text has already been reached. Setting this feature causes such
34150 keystrokes to be interpreted as if the "Tab" key had been hit, thus
34151 taking you to the next "interesting" message,
34152 or scanning ahead to the
34153 next incoming folder with "interesting" messages.
34155 <P>
34156 <UL>
34157 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34158 </UL><P>
34159 <End of help on this topic>
34160 </BODY>
34161 </HTML>
34162 ====== h_config_cruise_mode_delete =====
34163 <HTML>
34164 <HEAD>
34165 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></TITLE>
34166 </HEAD>
34167 <BODY>
34168 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></H1>
34170 This feature modifies the behavior of Alpine's
34171 <A HREF="h_config_cruise_mode">"<!--#echo var="FEAT_enable-cruise-mode"-->"</A> feature.
34172 Setting this feature causes Alpine to implicitly delete read
34173 messages when it moves on to display the next "interesting" message.
34174 <P>
34175 NOTE: Beware when enabling this feature AND the
34176 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
34177 feature.
34178 <P>
34179 <UL>
34180 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34181 </UL><P>
34182 <End of help on this topic>
34183 </BODY>
34184 </HTML>
34185 ====== h_config_slash_coll_entire =====
34186 <HTML>
34187 <HEAD>
34188 <TITLE>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></TITLE>
34189 </HEAD>
34190 <BODY>
34191 <H1>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></H1>
34193 The slash (/) command is available from the MESSAGE INDEX screen when
34194 the folder is sorted by either Threads or OrderedSubject, and the
34195 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
34196 is set to something other than "none".
34197 Normally, the slash command Collapses or Expands the subthread that
34198 starts at the currently highlighted message, if any.
34199 If this option is set, then the slash command Collapses or Expands the
34200 <EM>entire</EM> current thread instead of just the subthread.
34201 The current thread is simply the top-level thread that contains the
34202 current message.
34204 <P>
34205 <UL>
34206 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34207 </UL><P>
34208 <End of help on this topic>
34209 </BODY>
34210 </HTML>
34211 ====== h_config_color_thrd_import =====
34212 <HTML>
34213 <HEAD>
34214 <TITLE>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></TITLE>
34215 </HEAD>
34216 <BODY>
34217 <H1>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></H1>
34219 This option affects only the THREAD INDEX screen.
34220 Whether or not you ever see a THREAD INDEX screen depends on the setting
34221 of the configuration option
34222 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
34223 and on the sort order of the index.
34225 <P>
34226 If a message within a thread is flagged as Important
34227 and this option is set, then
34228 the entire line in the THREAD INDEX will be colored the color of the
34229 Index-important Symbol, which can be set using the
34230 <A HREF="h_color_setup">Setup Kolor</A> screen.
34232 <P>
34233 <UL>
34234 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34235 </UL><P>
34236 <End of help on this topic>
34237 </BODY>
34238 </HTML>
34239 ====== h_config_allow_goto =====
34240 <HTML>
34241 <HEAD>
34242 <TITLE>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></TITLE>
34243 </HEAD>
34244 <BODY>
34245 <H1>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></H1>
34247 This feature modifies the behavior of Alpine's file browser. Setting this
34248 feature causes Alpine to offer the "G Goto" command in the file browser.
34249 That is the default.
34251 <P>
34253 The Goto command allows you to explicitly type in the desired directory.
34254 <P>
34255 <End of help on this topic>
34256 </BODY></HTML>
34257 ====== h_config_add_ldap =====
34258 <HTML>
34259 <HEAD>
34260 <TITLE>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></TITLE>
34261 </HEAD>
34262 <BODY>
34263 <H1>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></H1>
34265 If both the Directory option
34266 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
34267 and this feature are set,
34268 then when an implicit directory lookup is done from the
34269 composer you will automatically be prompted to add the result of the
34270 directory lookup to your address book.
34271 <P>
34272 <UL>
34273 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34274 </UL><P>
34275 <End of help on this topic>
34276 </BODY>
34277 </HTML>
34278 ===== h_patterns_compat_behavior =====
34279 <HTML>
34280 <HEAD>
34281 <TITLE>Rules Behavior Changes in Pine 4.50</TITLE>
34282 </HEAD>
34283 <BODY>
34284 <H1>Rules Behavior Changes in Pine 4.50</H1>
34286 In Alpine, Rules that contain unrecognized elements
34287 are ignored.
34288 In most cases, the unrecognized elements will be something that was
34289 added as a new Rules feature in a later version of Alpine.
34290 In versions of Pine <EM>prior</EM> to 4.50, Pine did <EM>not</EM>
34291 ignore rules that contained unrecognized elements.
34292 For example, a new element of Rules that was added in Pine 4.50 is
34293 Age interval.
34294 Suppose you add an Indexcolor rule, using version Pine 4.50 or later, that colors
34295 all messages older than a week red.
34296 Now, if you run Pine 4.44 using that same configuration file, it will not
34297 recognize the Age interval and so will just ignore it.
34298 That means that all messages will match that rule so all messages will
34299 be colored red when using Pine version 4.44.
34301 <P>
34302 This behavior was considered a bug so it is fixed in Alpine and Pine 4.50 and later.
34303 However, since the behavior still exists in versions prior to Pine 4.50 and
34304 since Filtering is a potentially destructive operation, another measure
34305 was taken to attempt to avoid unintentional Filtering of messages.
34306 The first time that you run Alpine or a Pine that is version 4.50 or greater,
34307 the rules in your Filters configuration variable ("Patterns-Filters")
34308 will be copied to a new Filters configuration variable
34309 with a different name ("Patterns-Filters2").
34310 From then on, Alpine will continue to use the new
34311 variable.
34312 Of course, Pine version 4.44 or lower will continue to use the old
34313 variable.
34314 That means that if you are using Alpine
34315 and also using a version of Pine that is older than 4.50, they will not
34316 share the configuration information about Filters.
34317 If you make a change in one version you won't see it in the other version.
34319 <P>
34320 Since Scoring can be used to trigger Filtering, the same thing has been
34321 done for Score rules.
34322 The old configuration variable name is ("Patterns-Scores")
34323 and the new name is ("Patterns-Scores2").
34324 The same is not true of Role, Indexcolor, and Other rules that are
34325 thought to be less harmful when a mistake is made.
34327 <P>
34328 <End of help on this topic>
34329 </BODY>
34330 </HTML>
34331 ======= h_config_filt_opts_sentdate =======
34332 <HTML>
34333 <HEAD>
34334 <TITLE>PATTERN FEATURE: Use-Date-Header-For-Age</TITLE>
34335 </HEAD>
34336 <BODY>
34337 <H1>PATTERN FEATURE: Use-Date-Header-For-Age</H1>
34339 By default, the Age interval of a Pattern uses a message's time of
34340 arrival to compute the age of the message.
34341 If this feature is set, the date in the message's Date header will
34342 be used instead.
34343 <P>
34344 <End of help on this topic>
34345 </BODY>
34346 </HTML>
34347 ======= h_config_filt_opts_notdel =======
34348 <HTML>
34349 <HEAD>
34350 <TITLE>FILTER FEATURE: Move-Only-if-Not-Deleted</TITLE>
34351 </HEAD>
34352 <BODY>
34353 <H1>FILTER FEATURE: Move-Only-if-Not-Deleted</H1>
34355 If this option is set then a message will be moved into the
34356 specified folder only if it is not marked for deletion.
34357 This is useful if you have multiple Alpine sessions running
34358 simultaneously and you don't want messages to be filtered into a
34359 folder more than once.
34360 It is also useful if you want to filter
34361 only the "undeleted" messages in a newsgroup into a folder.
34362 This method is not foolproof.
34363 There may be cases where a message
34364 gets marked deleted and so it is never filtered into the folder.
34365 For example, if you deleted it in another Alpine session or another mail
34366 program that didn't use the filtering rule.
34367 <P>
34368 This option has no effect if the Filter Action is not set to Move.
34369 <P>
34370 <End of help on this topic>
34371 </BODY>
34372 </HTML>
34373 ======= h_config_filt_opts_nonterm =======
34374 <HTML>
34375 <HEAD>
34376 <TITLE>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</TITLE>
34377 </HEAD>
34378 <BODY>
34379 <H1>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</H1>
34381 If this option is set then this is a non-terminating rule.
34382 Usually, for each message, Alpine searches through the Filter Rules until
34383 a match is found and then it performs the action associated with that rule.
34384 Rules following the match are not considered.
34385 If this option is set then the search for matches will continue at the next
34386 rule.
34387 <P>
34388 If a non-terminating rule matches then the actions associated with
34389 that rule, except for any implied deletion of the message, are performed
34390 before the match for the next rule is checked.
34391 For example, if the non-terminating rule sets the Important status, then that
34392 status will be set when the next rule is considered.
34393 However, if the non-terminating rule Moves the message, the message will
34394 actually be copied instead of copied and deleted so that it is still there
34395 for the next rule.
34396 A moved message is deleted after all the relevant rules have been checked.
34397 The name of the "Move" action is confusing in this case because
34398 a single message can be moved to more than one folder.
34399 It turns the Move into a Copy instead, but it is still followed by a deletion
34400 at the end.
34401 <P>
34402 This option may be useful if you want to have a single message filtered to
34403 two different folders because it matches two different Patterns.
34404 For example, suppose you normally filter messages to a particular mailing
34405 list into one folder, and messages addressed directly to you into a second
34406 folder.
34407 If a message is sent to both you and the list (and you can tell that by
34408 looking at the headers of the message) this option may give you a convenient
34409 way to capture a copy to each folder.
34410 (It may also cause you to capture two copies to each folder,
34411 depending on whether your mail system delivers one or two copies of the
34412 message to you and on how the list works.)
34413 <P>
34414 <End of help on this topic>
34415 </BODY>
34416 </HTML>
34417 ===== h_mainhelp_smime ======
34418 <HTML>
34419 <HEAD>
34420 <TITLE>S/MIME Overview</TITLE>
34421 </HEAD>
34422 <BODY>
34423 <H1>S/MIME Overview</H1>
34425 S/MIME is a standard for the public key encryption and signing of email.
34426 UNIX Alpine contains a basic implementation of S/MIME based on
34427 the <A HREF="http://www.openssl.org/">OpenSSL</A> libraries.
34428 To check if this version of Alpine supports S/MIME look at
34429 <A HREF="X-Alpine-Config:">Supported Options in this Alpine</A> and look
34430 for "S/MIME" under the "Encryption" heading.
34431 <P>
34432 Some limitations:
34433 <UL>
34434 <LI> There is no PC-Alpine implementation.
34435 <LI> There is no provision for checking for CRLs
34436 (Certificate Revocation Lists) in Alpine.
34437 <LI> This built-in S/MIME implementation is not compatible with and does not help with PGP.
34438 <LI> There is no mechanism available for feeding either an entire incoming
34439 or an entire outgoing message to an external
34440 filter and using that external filter to do S/MIME or PGP processing.
34441 <LI> Because the implementation currently uses OpenSSL, there is only a very
34442 limited integration with the Mac OS Keychain (the storing and access of
34443 public certificates).
34444 </UL>
34445 <P>
34446 The S/MIME configuration screen is reached by going to the Main Menu and typing
34447 the "S Setup" command followed by "M S/MIME".
34448 <P>
34450 <H2>S/MIME BASICS</H2>
34452 In order to digitally sign messages you send you must have a public/private key-pair.
34453 This may be obtained from a public Certificate Authority (CA) such as Thawte, Verisign, Comodo,
34454 or GoDaddy; or from a smaller CA such as a university which provides certificates for its
34455 users or a company which provides certificates for its workers.
34456 These certificates are bound to an email address, so the identity being verified is the
34457 email address not a person's name.
34458 <P>
34459 Mail is signed by using the sender's private key, which only the owner of the private key
34460 has access to.
34461 The signature is verified using the signer's public key, which anyone can
34462 have access to.
34463 With Alpine, the first time you receive a signed message the public key of the
34464 sender will be stored for future use.
34466 <P>
34467 Mail is encrypted using the recipient's public key and decrypted by
34468 the recipient with their private key.
34470 <P>
34471 You need a key of your own in order to sign outgoing messages and to have others
34472 encrypt messages sent to you.
34473 You do not need a key of your own to verify signed messages sent by others or to
34474 encrypt messages sent to others.
34476 <H2>ALPINE S/MIME CERTIFICATE STORAGE</H2>
34478 By default UNIX Alpine stores the certificates it uses in a directory in your
34479 home directory.
34480 The directory name is
34481 <P>
34482 <CENTER><SAMP>.alpine-smime</SAMP></CENTER>
34483 <P>
34484 Within that directory are three subdirectories.
34485 Each of the three subdirectories contains files with PEM-encoded contents,
34486 the default format for OpenSSL.
34487 The "<SAMP>public</SAMP>" directory contains public certificates.
34488 The files within that directory have names that are email addresses with the
34489 suffix "<SAMP>.crt</SAMP>" appended.
34490 An example filename is
34491 <P>
34492 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
34493 <P>
34494 The "<SAMP>private</SAMP>" directory contains private keys, probably just one for
34495 your private key.
34496 These are also email addresses but with the suffix "<SAMP>.key</SAMP>" instead.
34497 The third directory is "<SAMP>ca</SAMP>" and it contains certificates for any Certificate
34498 Authorities that you want to trust but that aren't contained in the set of system CAs.
34499 Those files may have arbitrary names as long as they end with the
34500 suffix "<SAMP>.crt</SAMP>".
34502 <H2>HOW TO SIGN AND ENCRYPT</H2>
34504 If you have a certificate you may sign outgoing messages.
34505 After typing the Ctrl-X command to send a message you will see the prompt
34506 <P>
34507 <CENTER><SAMP>Send message?</SAMP></CENTER>
34508 <P>
34509 Available subcommands include "G Sign" and "E Encrypt".
34510 Typing the "G" command will change the prompt to
34511 <P>
34512 <CENTER><SAMP>Send message (Signed)?</SAMP></CENTER>
34513 <P>
34514 Typing the "E" command will change the prompt to
34515 <P>
34516 <CENTER><SAMP>Send message (Encrypted)?</SAMP></CENTER>
34517 <P>
34518 You may even type both to get
34519 <P>
34520 <CENTER><SAMP>Send message (Encrypted, Signed)?</SAMP></CENTER>
34521 <P>
34523 <H2>HOW TO READ SIGNED OR ENCRYPTED MESSAGES</H2>
34525 The reading of a signed message should not require any special action on
34526 your part.
34527 There should be an editorial addition at the start of the message which
34528 says either
34529 <P>
34530 <CENTER><SAMP>This message was cryptographically signed.</SAMP></CENTER>
34531 <P>
34532 or
34533 <P>
34534 <CENTER><SAMP>This message was cryptographically signed but the signature could not be verified.</SAMP></CENTER>
34535 <P>
34536 If an encrypted message is sent to you the encrypted text will not
34537 be shown.
34538 You will have to type the "Ctrl-D Decrypt" command (from the screen where
34539 you are viewing the message) and supply your passphrase when asked.
34540 <P>
34541 For a signed or encrypted message there is also a "Ctrl-E Security" command
34542 which gives you some information about the certificate used to sign or encrypt the message.
34544 <H2>MISCELLANEOUS</H2>
34546 If you have access to a private certificate in the PKCS12 format, which
34547 would sometimes be in a file with a ".p12" extension, then you can
34548 use the following commands to generate private keys, public and certificate
34549 authorities certificates. In the examples below, we assume that the
34550 certificate in the p12 format is called "certificate.p12", and
34551 that your email address is "your@address.com".
34553 <P>
34554 In order to create a private key use the command
34555 <P>
34556 <CENTER><SAMP>openssl pkcs12 -in certificate.p12 -out your@address.com.key</SAMP></CENTER>
34557 <P>
34558 In order to create a public certificate use the command
34559 <P>
34560 <CENTER><SAMP>
34561 openssl pkcs12 -in certificate.p12 -clcerts -nokeys -out your@address.com.crt
34562 </SAMP></CENTER>
34563 <P>
34564 In order to create a certificate authority certificate use the command
34565 <P>
34566 <CENTER><SAMP>
34567 openssl pkcs12 -in certificate.p12 -cacerts -nokeys -out certificate-ca.crt
34568 </SAMP></CENTER>
34570 <P> If the previous command produces an empty file, it means that the
34571 certificate authority was not included in the .p12 file, so you will have
34572 to get it from some other sources. You will need these certificates, so
34573 that you can validate correctly signatures.
34575 <P>
34576 After you have exported these certificates and keys, you can use the import
34577 command in Alpine, from the S/MIME configuration screen,
34578 to import these certificates into Alpine. They will be available for use
34579 as soon as you import them.
34580 <P>
34581 <End of help on this topic>
34582 </BODY>
34583 </HTML>
34584 ====== h_config_smime_pubcertdir =====
34585 <HTML>
34586 <HEAD>
34587 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></TITLE>
34588 </HEAD>
34589 <BODY>
34590 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></H1>
34592 UNIX Alpine only.
34593 <P>
34594 If the option
34595 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
34596 is set then this option will have no effect.
34597 <P>
34598 Normally, Public Certificates for use with S/MIME will be stored in the directory
34599 which is the value of this option.
34600 Those certificates will be stored in PEM format, one certificate per file.
34601 The name of the file for the certificate corresponding to
34602 <P>
34603 <CENTER><SAMP>emailaddress</SAMP></CENTER>
34604 <P>
34605 should be
34606 <P>
34607 <CENTER><SAMP>emailaddress.crt</SAMP></CENTER>
34608 <P>
34609 For example, a file for user@example.com would be in the file
34610 <P>
34611 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
34612 <P>
34613 in this directory.
34614 <P>
34615 Use the Setup/SMIME screen to modify this variable.
34616 <P>
34617 Typically, the public certificates that you have will come from S/MIME signed
34618 messages that are sent to you.
34619 Alpine will extract the public certificate from the signed message and store
34620 it in the certificates directory.
34621 These PEM format public certificates look something like:
34622 <PRE>
34623 -----BEGIN CERTIFICATE-----
34624 MIIFvTCCBKWgAwIBAgIQD4fYFHVI8T20yN4nus097DANBgkqhkiG9w0BAQUFADCB
34625 rjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2Ug
34626 Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExho
34627 ...
34628 2b9KGqDyMWW/rjNnmpjzjT2ObGM7lRA8lke4FLOLajhrz4ogO3b4DFfAAM1VSZH8
34629 D6sOwOLJZkLY8FRsfk63K+2EMzA2+qAzMKupgeTLqXIf
34630 -----END CERTIFICATE-----
34631 </PRE>
34632 <P>
34633 <UL>
34634 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34635 </UL><P>
34636 <P>
34637 <UL>
34638 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34639 </UL><P>
34640 <End of help on this topic>
34641 </BODY>
34642 </HTML>
34643 ====== h_config_smime_pubcertcon =====
34644 <HTML>
34645 <HEAD>
34646 <TITLE>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></TITLE>
34647 </HEAD>
34648 <BODY>
34649 <H1>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></H1>
34651 UNIX Alpine only.
34652 <P>
34653 If this option is set it will be used instead of
34654 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
34655 <P>
34656 This option gives you a way to store certificates remotely on an IMAP server
34657 instead of storing the certificates one per file locally.
34658 In order to do that you just give this option a remote folder name for a folder
34659 which does not yet exist.
34660 The name is similar to the name you might use for a remote configuration file.
34661 A remote folder name might look something like:
34662 <P>
34663 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/publiccerts</SAMP></CENTER>
34664 <P>
34665 See
34666 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34667 about the syntax of folder names.
34668 <P>
34669 Use the Setup/SMIME screen to modify this variable.
34670 <P>
34671 <UL>
34672 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34673 </UL><P>
34674 <P>
34675 <UL>
34676 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34677 </UL><P>
34678 <End of help on this topic>
34679 </BODY>
34680 </HTML>
34681 ====== h_config_smime_privkeydir =====
34682 <HTML>
34683 <HEAD>
34684 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></TITLE>
34685 </HEAD>
34686 <BODY>
34687 <H1>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></H1>
34689 UNIX Alpine only.
34690 <P>
34691 In order to sign outgoing S/MIME messages you will need a
34692 personal digital ID certificate.
34693 You will usually get such a certificate from a certificate authority such as
34694 Thawte or CAcert.
34695 (In order to encrypt outgoing messages you don't need a personal digital ID, you
34696 need the public certificate of the recipient instead.)
34697 If the option
34698 <A HREF="h_config_smime_privkeycon"><!--#echo var="VAR_smime-private-key-container"--></A>
34699 is set then this option will have no effect.
34700 <P>
34701 Normally, Private Keys for use with S/MIME will be stored in the directory
34702 which is the value of this option.
34703 Those certificates will be stored in PEM format, one certificate per file.
34704 The name of the file for the certificate corresponding to your
34705 <P>
34706 <CENTER><SAMP>emailaddress</SAMP></CENTER>
34707 <P>
34708 should be
34709 <P>
34710 <CENTER><SAMP>emailaddress.key</SAMP></CENTER>
34711 <P>
34712 For example, if your address is user@example.com the name of the file would be
34713 <P>
34714 <CENTER><SAMP>user@example.com.key</SAMP></CENTER>
34715 <P>
34716 in this directory.
34717 <P>
34718 Use the Setup/SMIME screen to modify this variable.
34719 <P>
34720 Typically, the private key that you have will come from a Certificate
34721 Authority.
34722 The private key should be stored in a PEM format file that
34723 looks something like:
34724 <PRE>
34725 -----BEGIN RSA PRIVATE KEY-----
34726 Proc-Type: 4,ENCRYPTED
34727 DEK-Info: DES-EDE3-CBC,2CBD328FD84CF5C6
34729 YBEXYLgLU9NJoc1V+vJ6UvcF08RX54S6jXsmgL0b5HGkudG6fhnmHkH7+UCvM5NI
34730 SXO/F8iuZDfs1VGG0NyitkFZ0Zn2vfaGovBvm15gx24b2xnZDLRB7/bNZkurnK5k
34731 VjAjZ2xXn2hFp2GJwqRdmxYNqsKGu52B99oti5HUWuZ2GFRaWjn5hYOqeApZE2uA
34732 ...
34733 oSRqfI51UdSRt0tmGhHeTvybUVrHm9eKft8TTGf+qSBqzSc55CsmoVbRzw4Nfhix
34734 m+4TJybNGNfAgOctSkEyY/OCb49fRRQTCBZVIhzLGGmpYmkO55HbIA==
34735 -----END RSA PRIVATE KEY-----
34736 </PRE>
34737 <P>
34738 <UL>
34739 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34740 </UL><P>
34741 <P>
34742 <UL>
34743 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34744 </UL><P>
34745 <End of help on this topic>
34746 </BODY>
34747 </HTML>
34748 ====== h_config_smime_privkeycon =====
34749 <HTML>
34750 <HEAD>
34751 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-container"--></TITLE>
34752 </HEAD>
34753 <BODY>
34754 <H1>OPTION: <!--#echo var="VAR_smime-private-key-container"--></H1>
34756 UNIX Alpine only.
34757 <P>
34758 If this option is set it will be used instead of
34759 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
34760 <P>
34761 This option gives you a way to store keys remotely on an IMAP server
34762 instead of storing the keys one per file locally.
34763 In order to do that you just give this option a remote folder name for a folder
34764 which does not yet exist.
34765 The name is similar to the name you might use for a remote configuration file.
34766 A remote folder name might look something like:
34767 <P>
34768 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/privatekeys</SAMP></CENTER>
34769 <P>
34770 See
34771 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34772 about the syntax of folder names.
34773 <P>
34774 Use the Setup/SMIME screen to modify this variable.
34775 <P>
34776 <UL>
34777 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34778 </UL><P>
34779 <P>
34780 <UL>
34781 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34782 </UL><P>
34783 <End of help on this topic>
34784 </BODY>
34785 </HTML>
34786 ====== h_config_smime_cacertdir =====
34787 <HTML>
34788 <HEAD>
34789 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></TITLE>
34790 </HEAD>
34791 <BODY>
34792 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></H1>
34794 UNIX Alpine only.
34795 <P>
34796 If the option
34797 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>
34798 is set then this option will have no effect.
34799 <P>
34800 CACert is a shorthand name for certification authority certificate.
34801 Normally Alpine will use the CACerts that are located in the standard system
34802 location for CACerts.
34803 It may be the case that one of your correspondents has a Digital ID which has
34804 been signed by a certificate authority that is not in the regular set of system certificate
34805 authorities.
34806 You may supplement the system list by adding further certificates of your own.
34807 These should be stored in the directory
34808 which is the value of this option.
34809 The certificates will be stored in PEM format, one certificate per file.
34810 The names of the files can be anything ending in ".crt".
34811 <P>
34812 Use the Setup/SMIME screen to modify this variable.
34813 <P>
34814 These PEM format CA certificates look very similar to your public
34815 certificates for particular email addresses
34816 (<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>).
34817 <P>
34818 <UL>
34819 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34820 </UL><P>
34821 <P>
34822 <UL>
34823 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34824 </UL><P>
34825 <End of help on this topic>
34826 </BODY>
34827 </HTML>
34828 ====== h_config_smime_cacertcon =====
34829 <HTML>
34830 <HEAD>
34831 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></TITLE>
34832 </HEAD>
34833 <BODY>
34834 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></H1>
34836 UNIX Alpine only.
34837 <P>
34838 If this option is set it will be used instead of
34839 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
34840 <P>
34841 This option gives you a way to store certificates remotely on an IMAP server
34842 instead of storing the certificates one per file locally.
34843 In order to do that you just give this option a remote folder name for a folder
34844 which does not yet exist.
34845 The name is similar to the name you might use for a remote configuration file.
34846 A remote folder name might look something like:
34847 <P>
34848 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/cacerts</SAMP></CENTER>
34849 <P>
34850 See
34851 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34852 about the syntax of folder names.
34853 <P>
34854 Use the Setup/SMIME screen to modify this variable.
34855 <P>
34856 <UL>
34857 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34858 </UL><P>
34859 <P>
34860 <UL>
34861 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34862 </UL><P>
34863 <End of help on this topic>
34864 </BODY>
34865 </HTML>
34866 ========== h_config_smime_sign_by_default ==========
34867 <HTML>
34868 <HEAD>
34869 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></TITLE>
34870 </HEAD>
34871 <BODY>
34872 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></H1>
34874 UNIX Alpine only.
34875 <P>
34876 This feature only has an effect if your version of Alpine includes
34877 support for S/MIME.
34878 It affects Alpine's behavior when you send a message.
34879 If this option is set, the "Sign" option will default to ON when sending messages.
34880 <P>
34881 Only the default value is affected.
34882 In any case, you may still toggle the Signing option on or off before sending
34883 with the "G Sign" command (provided you have a personal digital ID
34884 certificate).
34885 <P>
34886 <UL>
34887 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34888 </UL><P>
34889 <P>
34891 <UL>
34892 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34893 </UL><P>
34894 <End of help on this topic>
34895 </BODY>
34896 </HTML>
34897 ========== h_config_smime_use_cert_store ==========
34898 <HTML>
34899 <HEAD>
34900 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></TITLE>
34901 </HEAD>
34902 <BODY>
34903 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></H1>
34905 UNIX Alpine only.
34906 <P>
34907 This feature only has an effect if your version of Alpine includes
34908 support for S/MIME.
34909 It affects Alpine's behavior when you validate a message, and should
34910 not be disabled, unless you are performing a test.
34911 <P>
34912 There are two important aspects of validation: validation of the message
34913 (that is, the message was not modified after it was sent)
34914 as well as validation of the identity of the sender. This option has to
34915 do with the latter.
34916 <P>
34917 In order to validate that the message came from the sender in the message
34918 and not an impersonator, Alpine can
34919 either use the certificates that come in the message, or the ones that
34920 you have personally stored. If this feature is enabled (the default) then
34921 Alpine will use certificates that you have already saved in your store
34922 and not those that come in the message to validate the sender of the
34923 message. This behavior helps you prevent against impersonation, because
34924 it is assumed that you trust the certificates that you have saved, and
34925 might not trust those that came with the message that you are validating.
34926 <P>
34927 <UL>
34928 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34929 </UL><P>
34930 <P>
34932 <UL>
34933 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34934 </UL><P>
34935 <End of help on this topic>
34936 </BODY>
34937 </HTML>
34938 ========== h_config_smime_pubcerts_in_keychain ==========
34939 <HTML>
34940 <HEAD>
34941 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></TITLE>
34942 </HEAD>
34943 <BODY>
34944 <H1>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></H1>
34946 UNIX Alpine only.
34947 <P>
34948 If this feature is set the Mac OS X default keychain will be used as the place
34949 to store public certificates instead of a
34950 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
34951 or a
34952 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
34953 <P>
34954 <UL>
34955 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34956 </UL><P>
34957 <P>
34958 <UL>
34959 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34960 </UL><P>
34961 <End of help on this topic>
34962 </BODY>
34963 </HTML>
34964 ========== h_config_smime_dont_do_smime ==========
34965 <HTML>
34966 <HEAD>
34967 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></TITLE>
34968 </HEAD>
34969 <BODY>
34970 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></H1>
34972 UNIX Alpine only.
34973 <P>
34974 Setting this feature turns off all of Alpine's S/MIME support.
34975 You might want to set this if you are having trouble due to the S/MIME support.
34976 <P>
34977 <UL>
34978 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34979 </UL><P>
34980 <P>
34982 <UL>
34983 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34984 </UL><P>
34985 <End of help on this topic>
34986 </BODY>
34987 </HTML>
34988 ========== h_config_smime_encrypt_by_default ==========
34989 <HTML>
34990 <HEAD>
34991 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></TITLE>
34992 </HEAD>
34993 <BODY>
34994 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></H1>
34996 UNIX Alpine only.
34997 <P>
34998 This feature only has an effect if your version of Alpine includes
34999 support for S/MIME.
35000 It affects Alpine's behavior when you send a message.
35001 If this option is set, the "Encrypt" option will default to ON when sending messages.
35002 <P>
35003 Only the default value is affected.
35004 In any case, you may still toggle the Encrypt option on or off before sending
35005 with the "E Encrypt" command (provided you have a the public digital ID
35006 for the recipient).
35007 <P>
35008 <UL>
35009 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35010 </UL><P>
35011 <P>
35013 <UL>
35014 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35015 </UL><P>
35016 <End of help on this topic>
35017 </BODY>
35018 </HTML>
35019 ========== h_config_smime_remember_passphrase ==========
35020 <HTML>
35021 <HEAD>
35022 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></TITLE>
35023 </HEAD>
35024 <BODY>
35025 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></H1>
35027 UNIX Alpine only.
35028 <P>
35029 This feature only has an effect if your version of Alpine includes
35030 support for S/MIME.
35031 If this option is set, you will only have to enter your passphrase for your private key
35032 once during an Alpine session.
35033 <P>
35034 <UL>
35035 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35036 </UL><P>
35037 <P>
35039 <UL>
35040 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35041 </UL><P>
35042 <End of help on this topic>
35043 </BODY>
35044 </HTML>
35045 ====== h_config_smime_transfer_pub_to_con =====
35046 <HTML>
35047 <HEAD>
35048 <TITLE>S/MIME: Transfer Public Certs to Container</TITLE>
35049 </HEAD>
35050 <BODY>
35051 <H1>S/MIME: Transfer Public Certs to Container</H1>
35053 UNIX Alpine only.
35054 <P>
35055 The Transfer command will copy the public certificates in your configured
35056 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
35057 to the container in your configured
35058 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
35059 This might be useful if you decide to switch from using a cert directory to a cert
35060 container.
35061 <P>
35062 Warning: Any previous contents in the container will be lost.
35063 <P>
35064 <UL>
35065 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35066 </UL><P>
35067 <P>
35068 <UL>
35069 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35070 </UL><P>
35071 <End of help on this topic>
35072 </BODY>
35073 </HTML>
35074 ====== h_config_smime_transfer_pub_to_dir =====
35075 <HTML>
35076 <HEAD>
35077 <TITLE>S/MIME: Transfer Public Certs to Directory</TITLE>
35078 </HEAD>
35079 <BODY>
35080 <H1>S/MIME: Transfer Public Certs to Directory</H1>
35082 UNIX Alpine only.
35083 <P>
35084 The Transfer command will copy the public certificates in your configured
35085 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35086 to the directory in your configured
35087 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
35088 This might be useful if you decide to switch from using a cert container to a cert
35089 directory.
35090 <P>
35091 <UL>
35092 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35093 </UL><P>
35094 <P>
35095 <UL>
35096 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35097 </UL><P>
35098 <End of help on this topic>
35099 </BODY>
35100 </HTML>
35101 ====== h_config_smime_transfer_priv_to_con =====
35102 <HTML>
35103 <HEAD>
35104 <TITLE>S/MIME: Transfer Private Keys to Container</TITLE>
35105 </HEAD>
35106 <BODY>
35107 <H1>S/MIME: Transfer Private Keys to Container</H1>
35109 UNIX Alpine only.
35110 <P>
35111 The Transfer command will copy the private keys in your configured
35112 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35113 to the container in your configured
35114 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
35115 This might be useful if you decide to switch from using a key directory to a key
35116 container.
35117 <P>
35118 Warning: Any previous contents in the container will be lost.
35119 <P>
35120 <UL>
35121 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35122 </UL><P>
35123 <P>
35124 <UL>
35125 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35126 </UL><P>
35127 <End of help on this topic>
35128 </BODY>
35129 </HTML>
35130 ====== h_config_smime_transfer_priv_to_dir =====
35131 <HTML>
35132 <HEAD>
35133 <TITLE>S/MIME: Transfer Private Keys to Directory</TITLE>
35134 </HEAD>
35135 <BODY>
35136 <H1>S/MIME: Transfer Private Keys to Directory</H1>
35138 UNIX Alpine only.
35139 <P>
35140 The Transfer command will copy the private keys in your configured
35141 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
35142 to the directory in your configured
35143 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35144 This might be useful if you decide to switch from using a key container to a key
35145 directory.
35146 <P>
35147 <UL>
35148 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35149 </UL><P>
35150 <P>
35151 <UL>
35152 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35153 </UL><P>
35154 <End of help on this topic>
35155 </BODY>
35156 </HTML>
35157 ====== h_config_smime_transfer_cacert_to_con =====
35158 <HTML>
35159 <HEAD>
35160 <TITLE>S/MIME: Transfer CA Certs to Container</TITLE>
35161 </HEAD>
35162 <BODY>
35163 <H1>S/MIME: Transfer CA Certs to Container</H1>
35165 UNIX Alpine only.
35166 <P>
35167 The Transfer command will copy the CA certificates in your configured
35168 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>
35169 to the container in your configured
35170 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
35171 This might be useful if you decide to switch from using a CA cert directory to a CA cert
35172 container.
35173 <P>
35174 Warning: Any previous contents in the container will be lost.
35175 <P>
35176 <UL>
35177 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35178 </UL><P>
35179 <P>
35180 <UL>
35181 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35182 </UL><P>
35183 <End of help on this topic>
35184 </BODY>
35185 </HTML>
35186 ====== h_config_smime_transfer_cacert_to_dir =====
35187 <HTML>
35188 <HEAD>
35189 <TITLE>S/MIME: Transfer CA Certs to Directory</TITLE>
35190 </HEAD>
35191 <BODY>
35192 <H1>S/MIME: Transfer CA Certs to Directory</H1>
35194 UNIX Alpine only.
35195 <P>
35196 The Transfer command will copy the CA certificates in your configured
35197 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
35198 to the directory in your configured
35199 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
35200 This might be useful if you decide to switch from using a CA cert container to a CA cert
35201 directory.
35202 <P>
35203 <UL>
35204 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35205 </UL><P>
35206 <P>
35207 <UL>
35208 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35209 </UL><P>
35210 <End of help on this topic>
35211 </BODY>
35212 </HTML>
35213 ====== h_config_smime_transfer_pubcon_to_key =====
35214 <HTML>
35215 <HEAD>
35216 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
35217 </HEAD>
35218 <BODY>
35219 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
35221 Mac OS X Alpine only.
35222 <P>
35223 The Transfer command will copy the public certificates in your configured
35224 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35225 to your default Mac OS X Keychain.
35226 This might be useful if you decide to switch from using a cert container to using
35227 the Keychain to store your public certs, which you may do by using the
35228 feature
35229 <A HREF="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></A>.
35230 <P>
35231 <UL>
35232 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35233 </UL><P>
35234 <P>
35235 <UL>
35236 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35237 </UL><P>
35238 <End of help on this topic>
35239 </BODY>
35240 </HTML>
35241 ====== h_config_smime_transfer_pubkey_to_con =====
35242 <HTML>
35243 <HEAD>
35244 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
35245 </HEAD>
35246 <BODY>
35247 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
35249 UNIX Alpine only.
35250 <P>
35251 The Transfer command will copy the public certificates in your configured
35252 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35253 to your default Mac OS X Keychain.
35254 This might be useful if you decide to switch from using a cert container to using
35255 the Keychain to store your public certs.
35256 <P>
35257 <UL>
35258 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35259 </UL><P>
35260 <P>
35261 <UL>
35262 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35263 </UL><P>
35264 <End of help on this topic>
35265 </BODY>
35266 </HTML>
35267 ====== h_config_smime_public_certificates =====
35268 <HTML>
35269 <HEAD>
35270 <TITLE>S/MIME: Manage Public Certificates</TITLE>
35271 </HEAD>
35272 <BODY>
35273 <H1>S/MIME: Manage Public Certificates</H1>
35275 UNIX Alpine only.
35276 <P>
35277 This menu item allows you to manage your public certificates, this
35278 may include your own public certificate, but it normally includes
35279 certificates of people you correspond with. These certificates are
35280 saved by Alpine automatically when they are found in signed messages
35281 that you receive. This interface allows you to manage them, by
35282 giving you the option to delete them, or trust them (in the case
35283 of self-signed certificates).
35285 <P>
35286 Please note that Alpine will not validate a message that was sent to you
35287 using a self-signed certificate, unless you decide to trust that certificate.
35288 Internally, a certificate is trusted by copying it to the
35289 <A HREF="h_config_smime_certificate_authorities">Certificate Authorities</A>
35290 collection. If you decide that you want to stop trusting a self-signed
35291 certificate, you must delete such certificate from such collection.
35292 <P>
35293 The <B>I</B> Import command available in this screen allows you to
35294 import a command to this collection.
35295 <P>
35296 <UL>
35297 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35298 </UL><P>
35299 <P>
35300 <UL>
35301 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35302 </UL><P>
35303 <End of help on this topic>
35304 </BODY>
35305 </HTML>
35306 ====== h_config_smime_private_keys =====
35307 <HTML>
35308 <HEAD>
35309 <TITLE>S/MIME: Manage Private Keys</TITLE>
35310 </HEAD>
35311 <BODY>
35312 <H1>S/MIME: Manage Private Keys</H1>
35314 UNIX Alpine only.
35315 <P>
35316 This option allows you to manage your private key. Normally a person has only
35317 one key, in the same way that a person only has one valid passport, or ID card,
35318 at any given time. This option allows you to manage private keys. You can
35319 delete them or import them. Additionally, you can view information
35320 about your public certificate, such as the issuer and the dates of validity
35321 of such certificate, among others.
35323 <P>
35324 If you have more than one e-mail address for which you want to use the
35325 same private key, you must add all those addresses to the private key at
35326 the moment that the key is generated. When you receive a signed message using
35327 a key generated for several e-mail addresses, Alpine will save a
35328 certificate for each e-mail address included in such certificate.
35329 <P>
35330 The <B>I</B> Import command available in this screen allows you to
35331 import a command to this collection.
35332 <P>
35333 <UL>
35334 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35335 </UL><P>
35336 <P>
35337 <UL>
35338 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35339 </UL><P>
35340 <End of help on this topic>
35341 </BODY>
35342 </HTML>
35343 ====== h_config_smime_certificate_authorities =====
35344 <HTML>
35345 <HEAD>
35346 <TITLE>S/MIME: Manage Certificate Authorities</TITLE>
35347 </HEAD>
35348 <BODY>
35349 <H1>S/MIME: Manage Certificate Authorities</H1>
35351 UNIX Alpine only.
35352 <P>
35353 This collection contains certificates that are needed to validate the
35354 certificate of another person, and therefore contains certificates that
35355 you trust. Typically a certificate is signed by another entity, called a
35356 certificate authority. This option allows you to manage which certificates
35357 you trust, allowing you to import them and to delete them or view information
35358 about each certificate, such as the issuer and the dates of validity
35359 of such certificate.
35360 <P>
35361 The <B>I</B> Import command available in this screen allows you to
35362 import a command to this collection.
35363 <P>
35364 <UL>
35365 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35366 </UL><P>
35367 <P>
35368 <UL>
35369 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35370 </UL><P>
35371 <End of help on this topic>
35372 </BODY>
35373 </HTML>
35374 ====== h_certificate_information =====
35375 <HTML>
35376 <HEAD>
35377 <TITLE>S/MIME: Certificate Information Screen</TITLE>
35378 </HEAD>
35379 <BODY>
35380 <H1>S/MIME: Certificate Information Screen</H1>
35382 UNIX Alpine only.
35383 <P>
35384 The CERTIFICATE INFORMATION screen shows you information contained in a certificate
35385 such as its owner, e-mail address, issuer, and interval of validity,
35386 among others.
35387 <P>
35388 In the case of public certificates, this screen shows you if there was a
35389 failure when attempting to validate such message. If the certificate is
35390 self-signed, then the <B>T</B> Trust command will be available, which
35391 you can use to trust such certificate and make Alpine not fail validating
35392 signatures signed with such certificate.
35393 <P>
35394 You can also mark a certificate deleted, with the <B>D</B> command, or
35395 remove the deleted mark with the <B>U</B> undelete command.
35396 <P>
35397 In the case of your private key, Alpine shows you the information
35398 from your public key. Additionally, Alpine allows you to see public
35399 and private information about your key, with the <B>B</B> and
35400 <B>R</B> commands respectively.
35401 <UL>
35402 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35403 </UL><P>
35404 <P>
35405 <UL>
35406 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35407 </UL><P>
35408 <End of help on this topic>
35409 </BODY>
35410 </HTML>
35411 ====== h_config_smime_manage_public_menu =====
35412 <HTML>
35413 <HEAD>
35414 <TITLE>S/MIME: Menu of Commands to Manage Public Certificates</TITLE>
35415 </HEAD>
35416 <BODY>
35417 <H1>S/MIME: Commands that Manage Public Certificates</H1>
35419 UNIX Alpine only.
35420 <P>
35421 This screen allows you to manage your public certificates.
35422 <P>
35423 The format of this screen is as follows. There are five fields: The
35424 leftmost field is normally empty, but it could contain the letter
35425 "D" to indicate that that certificate has been marked for
35426 deletion. The next field is the e-mail address of the owner of the
35427 certificate, shown in its entirety. The third and fourth field are the
35428 first and last day validity for that certificate, respectively. The date
35429 is displayed in the user's locale unless the option
35430 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>
35431 is set. In this case, the month, day and year are represented by two
35432 digits, and the format used is mm/dd/yy. Finally, the fifth
35433 field is what can be displayed of the MD5 hash of the certificate. You can
35434 use any of the last three fields to distinguish between two certificates
35435 for the same owner.
35436 <P>
35437 Available commands in this screen and a short description of what they
35438 do follows.
35439 <UL>
35440 <LI> <B>I</B> Imports a public certificate to this collection.
35441 <LI> <B>V</B> View information about a certificate such as the name of the person the
35442 certificate was issued to, its dates of validity, and validity status.
35443 <LI> <B>D</B> Marks a certificate deleted.
35444 <LI> <B>U</B> Removes the deletion mark on a certificate.
35445 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
35446 <LI> <B>T</B> This command is only available for self-signed certificates, and allows you to
35447 trust a certificate by copying it to the collection of trusted certificates.
35448 </UL>
35449 <P>
35450 All commands provide feedback to let you know about their success or failure.
35451 <P>
35452 <UL>
35453 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35454 </UL><P>
35455 <P>
35456 <UL>
35457 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35458 </UL><P>
35459 <End of help on this topic>
35460 </BODY>
35461 </HTML>
35462 ====== h_config_smime_manage_private_menu =====
35463 <HTML>
35464 <HEAD>
35465 <TITLE>S/MIME: Menu of Commands to Manage Private Keys</TITLE>
35466 </HEAD>
35467 <BODY>
35468 <H1>S/MIME: Commands that Manage Private Keys</H1>
35470 UNIX Alpine only.
35471 <P>
35472 This screen allows you to manage your private key.
35473 <P>
35474 The format of this screen is as follows. There are five fields: The
35475 leftmost field is normally empty, but it could contain the letter
35476 "D" to indicate that that certificate has been marked for
35477 deletion. The next field is the e-mail address of the owner of the
35478 certificate, shown in its entirety. The third field is the first day of
35479 validity for that certificate; the fourth field in the last day that that
35480 certificate is valid, and the fifth field is what can be displayed of the
35481 MD5 hash of the public certificate corresponding to this private key. You
35482 can use any of the last three fields to distinguish between two
35483 certificates for the same owner.
35484 <P>
35485 Available commands and a short description of what they do follows.
35486 <UL>
35487 <LI> <B>I</B> Imports a new public key to this collection.
35488 <LI> <B>V</B> View information about the public certificate corresponding to this
35489 key.
35490 <LI> <B>D</B> Marks a key to be deleted.
35491 <LI> <B>U</B> Removes the deletion mark on a key.
35492 <LI> <B>X</B> Removes all keys marked deleted permanently (cannot be undone).
35493 Note that expunging a private key does not remove the public key, which must
35494 be removed separately.
35495 </UL>
35496 <P>
35497 All commands provide feedback to let you know about their success or failure.
35498 <P>
35499 <UL>
35500 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35501 </UL><P>
35502 <P>
35503 <UL>
35504 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35505 </UL><P>
35506 <End of help on this topic>
35507 </BODY>
35508 </HTML>
35509 ====== h_config_smime_manage_cacerts_menu =====
35510 <HTML>
35511 <HEAD>
35512 <TITLE>S/MIME: Menu of Commands to Manage Certificate Authorities</TITLE>
35513 </HEAD>
35514 <BODY>
35515 <H1>S/MIME: Commands that Manage Certificate Authorities</H1>
35517 UNIX Alpine only.
35518 <P>
35519 This screen allows you to manage your collection of certificates that you
35520 trust.
35521 <P>
35522 The format of this screen is as follows. There are five fields: The
35523 leftmost field is normally empty, but it could contain the letter
35524 "D" to indicate that that certificate has been marked for
35525 deletion. The next field is the e-mail address of the owner of the
35526 certificate, shown in its entirety. The third field is the first day of
35527 validity for that certificate; the fourth field in the last day that that
35528 certificate is valid, and the fifth field is what can be displayed of the
35529 MD5 hash of the certificate. You can use any of the last three fields to
35530 distinguish between two certificates for the same owner.
35531 <P>
35532 Available commands and a short description of what they do follows.
35533 <UL>
35534 <LI> <B>I</B> Imports a trusted certificate to this collection. This is
35535 done by reading the certificate and validating it. Once a certificate
35536 is found to be valid, it is saved, adding the extension ".crt"
35537 to the certificate, if necessary.
35538 <LI> <B>V</B> View information about this certificate, such as its issuer
35539 and validity dates.
35540 <LI> <B>D</B> Marks a certificate to be deleted.
35541 <LI> <B>U</B> Removes the deletion mark on a certificate.
35542 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
35543 </UL>
35544 <P>
35545 All commands provide feedback to let you know about their success or failure.
35546 <P>
35547 <UL>
35548 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35549 </UL><P>
35550 <P>
35551 <UL>
35552 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35553 </UL><P>
35554 <End of help on this topic>
35555 </BODY>
35556 </HTML>
35557 ====== h_config_lame_list_mode =====
35558 <HTML>
35559 <HEAD>
35560 <TITLE>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></TITLE>
35561 </HEAD>
35562 <BODY>
35563 <H1>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></H1>
35565 This feature modifies the method Alpine uses to ask your IMAP
35566 server for folder names to display in the FOLDER LIST screen.
35567 It is intended to compensate for a small set of IMAP servers that
35568 are programmed to ignore a part of the request, and thus respond
35569 to Alpine's query with nonsensical results.
35570 <P>
35572 If you find that Alpine is erroneously displaying blank folder lists,
35573 try enabling this feature.
35574 <P>
35576 NOTE: Enabling this feature has consequences for the Goto and Save
35577 commands. Many servers allow access to folders outside the area
35578 reserved for your personal folders via some reserved character,
35579 typically '#' (sharp), '~' (tilde) or '/' (slash). This mechanism
35580 allows, at the Goto and Save prompts, quick access to folders
35581 outside your personal folder collection without requiring a specific
35582 collection definition. This behavior will generally not be available
35583 when this feature is enabled.
35585 <P>
35586 <UL>
35587 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35588 </UL><P>
35589 <End of help on this topic>
35590 </BODY>
35591 </HTML>
35592 ====== h_config_enable_mulnewsrcs =====
35593 <HTML>
35594 <HEAD>
35595 <TITLE>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></TITLE>
35596 </HEAD>
35597 <BODY>
35598 <H1>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></H1>
35600 This feature makes it so Alpine can use multiple newsrcs based on
35601 the news server being connected to, which allows for separate lists
35602 of subscribed-to newsgroups. When this feature is not set, there is only
35603 one list of newsgroups.
35604 <P>
35605 Under this feature, the name of a newsrc is based on the news server.
35606 For example, if your <a href="h_config_newsrc_path"><!--#echo var="VAR_newsrc-path"--></a>
35607 is set to ".newsrc", and the news server you are connecting to is
35608 news.example.com, then the newsrc to be used is .newsrc-news.example.com.
35609 Setting this feature for the first time will allow for the option of using
35610 your old newsrc the next time you read news.
35611 <P>
35612 If this feature is set, then the feature
35613 <A HREF="h_config_mulnews_as_typed"><!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></A>
35614 also may affect the name of the newsrc file that is used.
35615 <P>
35616 <UL>
35617 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35618 </UL><P>
35619 <End of help on this topic>
35620 </BODY>
35621 </HTML>
35622 ======= h_ab_export_vcard =======
35623 <HTML>
35624 <HEAD>
35625 <TITLE>Address Book Export Format</TITLE>
35626 </HEAD>
35627 <BODY>
35628 <H1>Address Book Export Format</H1>
35630 You are exporting address book data from Alpine to a file outside of Alpine.
35631 You are being asked to choose the format of the export.
35632 Here are the choices:
35634 <DL>
35635 <DT><EM>A</EM>ddress List</DT>
35636 <DD>
35637 The addresses from the address book entries you are saving
35638 from will be saved one address per line.
35639 Address book lists (those with more than one address) will have
35640 all of their addresses saved separately.
35641 </DD>
35643 <DT><EM>V</EM>Card</DT>
35644 <DD>
35645 The entries will be saved in
35646 <A HREF="h_whatis_vcard">vCard</A> format.
35647 </DD>
35649 <DT><EM>T</EM>ab Separated</DT>
35650 <DD>
35651 The entries will be saved in tab-separated columns.
35652 There will be just 4 columns of data that correspond to Alpine's
35653 Nickname field, Full Name field, Address field, and Comment field.
35654 It might prove useful to Select only the Simple, non-List address book
35655 entries before Saving.
35656 </DD>
35658 <DT><EM>^C</EM> Cancel</DT>
35659 <DD>
35660 Cancel out of the Save.
35661 </DD>
35663 </DL>
35666 <P>
35667 <End of help on this topic>
35668 </BODY>
35669 </HTML>
35670 ====== h_config_predict_nntp_server =====
35671 <HTML>
35672 <HEAD>
35673 <TITLE>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></TITLE>
35674 </HEAD>
35675 <BODY>
35676 <H1>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></H1>
35678 This feature allows Alpine to assume that the open NNTP server at the
35679 time of composition is the NNTP server to which the message should be
35680 posted. This is especially recommended when there are multiple News
35681 collections. If this feature is not set, Alpine will try to post to the first server in
35682 the <a href="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></a> variable. Setting
35683 this feature also negates the need to add News collection servers to
35684 the <!--#echo var="VAR_nntp-server"--> variable.
35685 <P>
35686 This feature can be especially handy when used in conjunction with
35687 <a href="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></a>.
35688 <P>
35689 <UL>
35690 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35691 </UL><P>
35692 <End of help on this topic>
35693 </BODY>
35694 </HTML>
35695 ====== h_config_nntp_search_uses_overview =====
35696 <HTML>
35697 <HEAD>
35698 <TITLE>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></TITLE>
35699 </HEAD>
35700 <BODY>
35701 <H1>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></H1>
35703 This feature should probably be turned on unless it causes trouble.
35704 The results of the NNTP overview command (XOVER) may be used to help
35705 with some searches in news groups.
35706 It should result in quicker response time.
35707 Turning this feature on apparently causes search results which are
35708 different from what you would get with the feature turned off on some
35709 servers.
35710 <P>
35711 <UL>
35712 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35713 </UL><P>
35714 <End of help on this topic>
35715 </BODY>
35716 </HTML>
35717 ====== h_config_thread_sorts_by_arrival =====
35718 <HTML>
35719 <HEAD>
35720 <TITLE>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></TITLE>
35721 </HEAD>
35722 <BODY>
35723 <H1>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></H1>
35725 This feature affects how a threading sort arranges threads. The default way
35726 to arrange threads is by the date of the earliest message in the thread.
35727 This feature arranges threads by the last message to arrive in a thread.
35728 <P>
35729 This feature causes old threads that get recent messages to sort to the bottom,
35730 where previously a message arrival to a thread would not rearrange the order of
35731 that thread.
35732 <P>
35733 <UL>
35734 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35735 </UL><P>
35736 <End of help on this topic>
35737 </BODY>
35738 </HTML>
35739 ====== h_config_textplain_int =====
35740 <HTML>
35741 <HEAD>
35742 <TITLE>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></TITLE>
35743 </HEAD>
35744 <BODY>
35745 <H1>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></H1>
35747 This feature modifies the method Alpine uses to display Text/Plain
35748 MIME attachments from the Attachment Index screen. Normally, the
35749 "View" command searches for any externally defined (usually
35750 via the
35751 "<A HREF="h_config_mailcap_path">Mailcap</A>" file) viewer,
35752 and displays the selected text within that viewer.
35754 <P>
35755 Enabling this feature causes Alpine to ignore any external viewer
35756 settings and always display text with Alpine's internal viewer.
35758 <P>
35759 <UL>
35760 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35761 </UL><P>
35762 <End of help on this topic>
35763 </BODY>
35764 </HTML>
35765 ====== h_config_wp_columns =====
35766 <HTML>
35767 <HEAD>
35768 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></TITLE>
35769 </HEAD>
35770 <BODY>
35771 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></H1>
35773 Web Alpine only.
35774 <P>
35775 This configuration setting specifies the number of horizontal characters
35776 used to format various WebAlpine pages. Smaller values will tend to reduce
35777 the amount of horizontal scrolling required to view pages within narrow
35778 browsers, such as those found on PDAs, and larger values will tend to
35779 spread more information across the page.
35781 <P>
35782 The Message List page uses the width to determine how many characters
35783 to assign each field. Note, a smaller value may result in a disproportionate
35784 amount of blank space between fields on each line. Similarly, a large
35785 value may result in cramped fields or horizontal scrolling.
35787 <P>
35788 The Message View page uses this value to determine when to wrap lines
35789 in displayed message text. Note, a smaller value may result in jagged
35790 right margins or confusing quoting. A larger value may cause lines of text to
35791 run beyond the browser's right edge, requiring horizontal scrolling.
35793 <P>
35794 <UL>
35795 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35796 </UL><P>
35797 <End of help on this topic>
35798 </BODY>
35799 </HTML>
35800 ====== h_config_wp_state =====
35801 <HTML>
35802 <HEAD>
35803 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></TITLE>
35804 </HEAD>
35805 <BODY>
35806 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></H1>
35808 Web Alpine only.
35809 <P>
35810 Various aspects of cross-session state.
35812 <P>
35813 <UL>
35814 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35815 </UL><P>
35816 <End of help on this topic>
35817 </BODY>
35818 </HTML>
35819 ====== h_config_wp_aggstate =====
35820 <HTML>
35821 <HEAD>
35822 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></TITLE>
35823 </HEAD>
35824 <BODY>
35825 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></H1>
35827 Web Alpine only.
35828 <P>
35829 Aggregate operations tab state.
35831 <P>
35832 <UL>
35833 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35834 </UL><P>
35835 <End of help on this topic>
35836 </BODY>
35837 </HTML>
35838 ====== h_config_wp_indexlines =====
35839 <HTML>
35840 <HEAD>
35841 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></TITLE>
35842 </HEAD>
35843 <BODY>
35844 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></H1>
35846 Web Alpine only.
35847 <P>
35848 Number of index lines in table.
35850 <P>
35851 <UL>
35852 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35853 </UL><P>
35854 <End of help on this topic>
35855 </BODY>
35856 </HTML>
35857 ====== h_config_wp_indexheight =====
35858 <HTML>
35859 <HEAD>
35860 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></TITLE>
35861 </HEAD>
35862 <BODY>
35863 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></H1>
35865 Web Alpine only.
35866 <P>
35867 Index table row height.
35869 <P>
35870 <UL>
35871 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35872 </UL><P>
35873 <End of help on this topic>
35874 </BODY>
35875 </HTML>
35876 ====== h_config_rss_news =====
35877 <HTML>
35878 <HEAD>
35879 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss_news"--></TITLE>
35880 </HEAD>
35881 <BODY>
35882 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-news"--></H1>
35884 Web Alpine only.
35885 <P>
35886 RSS News feed.
35888 <P>
35889 <UL>
35890 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35891 </UL><P>
35892 <End of help on this topic>
35893 </BODY>
35894 </HTML>
35895 ====== h_config_rss_weather =====
35896 <HTML>
35897 <HEAD>
35898 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></TITLE>
35899 </HEAD>
35900 <BODY>
35901 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></H1>
35903 Web Alpine only.
35904 <P>
35905 RSS Weather feed.
35907 <P>
35908 <UL>
35909 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35910 </UL><P>
35911 <End of help on this topic>
35912 </BODY>
35913 </HTML>
35914 ====== h_config_send_confirms_only_expanded =====
35915 <HTML>
35916 <HEAD>
35917 <TITLE>FEATURE: send-confirms-only-expanded</TITLE>
35918 </HEAD>
35919 <BODY>
35920 <H1>FEATURE: send-confirms-only-expanded (Web Alpine Only)</H1>
35922 This Web Alpine option specifies whether or not a Send confirmations
35923 happens when a composed message is readied for sending or not. The
35924 default behavior is to not confirm that the nicknames were expanded to
35925 the intended addresses.
35927 <P>
35928 <UL>
35929 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35930 </UL><P>
35931 <End of help on this topic>
35932 </BODY>
35933 </HTML>
35934 ====== h_config_enable_jump_command =====
35935 <HTML>
35936 <HEAD>
35937 <TITLE>FEATURE: enable-jump-command</TITLE>
35938 </HEAD>
35939 <BODY>
35940 <H1>FEATURE: enable-jump-command (Web Alpine Only)</H1>
35942 This Web Alpine option specifies whether or not a Jump command is
35943 offered in the Message List and Message View pages. The command is
35944 implemented as an input field in the left column of the List and View
35945 screens.
35947 <P>
35948 When enabled and a number is entered in the input field while the
35949 Message List is displayed, the Message List is reframed with the
35950 specified message. While viewing a message, the message associated
35951 with the specified message number is displayed.
35953 <P>
35954 <UL>
35955 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35956 </UL><P>
35957 <End of help on this topic>
35958 </BODY>
35959 </HTML>
35960 ====== h_config_enable_newmail_sound =====
35961 <HTML>
35962 <HEAD>
35963 <TITLE>FEATURE: enable-newmail-sound</TITLE>
35964 </HEAD>
35965 <BODY>
35966 <H1>FEATURE: enable-newmail-sound (Web Alpine Only)</H1>
35968 This Web Alpine option specifies whether or not a sound file is sent
35969 to the web browser along with the newmail notification message.
35972 <P>
35973 <UL>
35974 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35975 </UL><P>
35976 <End of help on this topic>
35977 </BODY>
35978 </HTML>
35979 ====== h_config_render_html_internally =====
35980 <HTML>
35981 <HEAD>
35982 <TITLE>FEATURE: render-html-internally</TITLE>
35983 </HEAD>
35984 <BODY>
35985 <H1>FEATURE: render-html-internally (Web Alpine Only)</H1>
35987 By default, Web Alpine will pass cleansed HTML text you receive in messages
35988 to the browser for display (rendering). This feature causes Web Alpine to convert
35989 the HTML text into plain text in the same way Unix and PC-Alpine do.
35992 <P>
35993 <UL>
35994 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35995 </UL><P>
35996 <End of help on this topic>
35997 </BODY>
35998 </HTML>
35999 ====== h_config_role_undo =====
36000 Yes, remember changes and exit back to list of roles; No, discard changes
36001 made in this screen; ^C, cancel exit and stay in this config screen.
36002 ====== h_exit_editor =====
36003 S, save changes and exit from the editor; D, do not save changes but
36004 do exit from the editor; or ^C, cancel exit and stay in the editor.
36005 ====== h_config_undo =====
36006 Yes, save changes and exit; No, exit without saving any changes made since
36007 entering this CONFIGURATION screen; ^C, cancel exit and stay in config screen.
36008 ====== h_os_index_whereis =====
36009 Enter ^V or ^Y to go immediately to the last or first message in the index.
36010 Or, enter the match string followed by RETURN.
36011 ====== h_os_index_whereis_agg =====
36012 Enter ^V or ^Y to go immediately to the last or first message in the index,
36013 Or, enter the match string followed by RETURN (or ^X to select all matches).
36014 =========== h_oe_add_full ==================
36015 Type the full name of the person being added and press the RETURN key.
36016 Press ^C to cancel addition.
36017 =========== h_oe_add_nick ==================
36018 Type a short nickname and press RETURN. A nickname is a short easy-to-
36019 remember word, name or initials like "joe", or "wcfields." ^C to cancel.
36020 ========== h_oe_add_addr ================
36021 Type the e-mail address and press RETURN.
36022 Press ^C to cancel addition.
36023 ========== h_oe_crlst_full ==============
36024 Type a long name or description for the list that you are creating and
36025 press RETURN. Press ^C to cancel creation of list.
36026 =========== h_oe_crlst_nick =============
36027 Type a nickname (short, easy-to-remember name or single word) for the list
36028 you are creating and press RETURN. Press ^C to cancel.
36029 ========== h_oe_crlst_addr ==============
36030 Type an e-mail address, or a nickname already in the address book that you
36031 want to be part of this list and press RETURN.
36032 ========== h_oe_adlst_addr =============
36033 Type an e-mail address or a nickname already in the address book that you
36034 want to add to this list and press RETURN.
36035 ========== h_oe_editab_nick ============
36036 Change the nickname using the arrow keys and delete key. Press RETURN
36037 when done. Press ^C to cancel editing and leave the nickname as it was.
36038 ========== h_oe_editab_full ============
36039 Change the full name using the arrow keys and delete key. Press RETURN
36040 when done. Press ^C to cancel editing and leave the full name as it was.
36041 ========== h_oe_editab_addr ============
36042 Change the address using the arrow keys and delete key. Press RETURN
36043 when done. Press ^C to cancel editing and leave the address as it was.
36044 ========== h_oe_editab_fcc ============
36045 Change the fcc using the arrow keys and delete key. Press RETURN when
36046 done. Press ^C to cancel editing and leave the fcc as it was.
36047 ========== h_oe_editab_comment ============
36048 Change the comment field using the arrow keys and delete key. Press RETURN
36049 when done. Press ^C to cancel editing and leave the comment as it was.
36050 ====== h_ab_forward =====
36051 Yes, expand nicknames and qualify local names with your current domain name;
36052 No, leave nicknames and local names as is; ^C, cancel.
36053 ========== h_ab_export ==========
36054 Type the name of a file to write the addresses into and
36055 press RETURN. You may also specify an absolute path. Use ^C to cancel.
36056 ========== h_ab_edit_a_field ==========
36057 Edit any of the fields of the currently selected entry by typing one of the
36058 letters at the bottom of the screen. Press ^C to cancel edit.
36059 ====== h_ab_del_data_revert =====
36060 Press B to completely delete addrbook and revert to default, C to delete config
36061 and revert while leaving data, or D to only delete data (make it empty).
36062 ====== h_ab_del_data_modify =====
36063 Press B to completely delete addrbook, C to delete configuration while leaving
36064 data, or D to delete data (make it empty) but leave config. ^C to cancel.
36065 ====== h_ab_del_config_modify =====
36066 Yes, remove this address book from my configuration.
36067 No, make no changes now.
36068 ====== h_ab_del_config_revert =====
36069 Yes, remove this address book from my config and revert to default.
36070 No, make no changes now.
36071 ====== h_ab_del_default =====
36072 Yes, remove this default address book from my configuration.
36073 No, make no changes now.
36074 ====== h_ab_really_delete =====
36075 Yes, delete the actual contents of the address book, not just the
36076 configuration. No, don't delete the data after all, cancel and start over.
36077 ====== h_ab_del_ignore =====
36078 Press I to ignore all the default address books for this category. Press R to
36079 remove this one address book and add the others to your personal list.
36080 ====== h_ab_del_dir_ignore =====
36081 Press I to ignore all the default directory servers for this category.
36082 Press R to remove this one server and add the others to your personal list.
36083 ====== h_ab_copy_dups =====
36084 Yes, overwrite the existing entry.
36085 No, skip duplicates but save the rest. Press ^C to cancel.
36086 ====== h_confirm_cancel =====
36087 Type C to Confirm that you want to abandon the message you are composing.
36088 Type N or ^C to cancel out of the cancel and keep composing.
36089 ====== h_ab_text_or_vcard =====
36090 Text, start composer with displayed text already included.
36091 VCard, start composer with address book entry attached as a vCard. ^C cancels.
36092 ====== h_ab_backup_or_ldap =====
36093 Backup, copy email address from entry and allow editing of it.
36094 LDAP, copy LDAP search criteria, do not allow editing of it. ^C cancels.
36095 ====== h_ldap_text_or_vcard =====
36096 Text: export displayed text for selected entry. Address: export only the
36097 email address. VCard: export entry in vCard format. ^C cancels.
36098 ====== h_ab_save_exp =====
36099 Save, save entry or entries to an address book.
36100 Export, save to file outside of pine. ^C cancels save.
36101 ====== h_ab_add =====
36102 A, add a brand new entry to this address book.
36103 E, edit the entry that is currently highlighted. ^C to cancel.
36104 ====== h_ab_shuf =====
36105 U, swap order of highlighted address book and the one above it.
36106 D, swap order of highlighted address book and the one below it. ^C to cancel.
36107 ====== h_ab_shuf_up =====
36108 U, swap order of highlighted address book and the one above it.
36109 Press ^C to cancel.
36110 ====== h_ab_shuf_down =====
36111 D, swap order of highlighted address book and the one below it.
36112 Press ^C to cancel.
36113 ====== h_folder_prop =====
36114 Count is # of messages in the folder, Unseen means messages that have not
36115 been read, New means messages that were Recently added to the folder.
36116 ====== h_role_shuf =====
36117 U, swap order of highlighted rule and the one above it.
36118 D, swap order of highlighted rule and the one below it. ^C to cancel.
36119 ====== h_role_shuf_up =====
36120 U, swap order of highlighted rule and the one above it.
36121 Press ^C to cancel.
36122 ====== h_role_shuf_down =====
36123 D, swap order of highlighted rule and the one below it.
36124 Press ^C to cancel.
36125 ====== h_incoming_shuf =====
36126 B, swap order of highlighted directory and the one before it.
36127 F, swap order of highlighted directory and the one after it. ^C to cancel.
36128 ====== h_incoming_shuf_up =====
36129 B, swap order of highlighted directory and the one before it.
36130 Press ^C to cancel.
36131 ====== h_incoming_shuf_down =====
36132 F, swap order of highlighted directory and the one after it.
36133 Press ^C to cancel.
36134 ====== h_dir_shuf =====
36135 U, swap order of highlighted directory and the one above it.
36136 D, swap order of highlighted directory and the one below it. ^C to cancel.
36137 ====== h_dir_shuf_up =====
36138 U, swap order of highlighted directory and the one above it.
36139 Press ^C to cancel.
36140 ====== h_dir_shuf_down =====
36141 D, swap order of highlighted directory and the one below it.
36142 Press ^C to cancel.
36143 ====== h_hdrcolor_shuf =====
36144 U, swap order of highlighted Header Color and the one above it.
36145 D, swap order of highlighted Header Color and the one below it. ^C to cancel.
36146 ====== h_hdrcolor_shuf_up =====
36147 U, swap order of highlighted Header Color and the one above it.
36148 Press ^C to cancel.
36149 ====== h_hdrcolor_shuf_down =====
36150 D, swap order of highlighted Header Color and the one below it.
36151 Press ^C to cancel.
36152 ========== h_oe_editab_al ============
36153 Change the address using the arrow keys and delete key. Press RETURN
36154 when done. Press ^C to cancel editing and leave the address as it was.
36155 ========== h_dir_comp_search ===============
36156 Type a string to look for just like you would in the composer. Your configured
36157 rules for the servers with the implicit flag set will be used.
36158 ========== h_oe_searchab ===============
36159 Type the word or name you want to search for and press RETURN. If you press
36160 RETURN without entering anything the word in [] will be searched for.
36161 ========== h_oe_chooseabook ==========
36162 Choose the address book you want to save the new entry in.
36163 Use ^N or ^P to change address books. ^C to cancel.
36164 ========== h_oe_takeaddr ==========
36165 Edit the e-mail address using the arrow and delete keys. Press RETURN
36166 when done. Press ^C to cancel adding this entry to the address book.
36167 ========== h_oe_take_replace ==========
36168 Press R to replace the old entry with this new data. You will still have
36169 another chance to cancel. N to enter another nickname. ^C to cancel now.
36170 ========== h_oe_take_replace_or_add ==========
36171 Press R to replace the old entry. Press A to add the selected addresses to
36172 the old existing list. N to enter another nickname. ^C to cancel now.
36173 ========== h_oe_takename ==========
36174 Edit the full name to be correct using the arrow and delete keys. Press RETURN
36175 when done. Press ^C to cancel adding this entry to the address book.
36176 ========== h_oe_takenick ==========
36177 Type a nickname (short easy-to-remember name, initials or single word) for this
36178 entry in the address book and press RETURN. Press ^C to cancel addition.
36179 ========== h_oe_jump ==========
36180 Type the message number you want to jump to and press RETURN. The word "end"
36181 represents the last message. Press ^C to cancel jumping to another message.
36182 ========== h_oe_jump_thd ==========
36183 Type the thread number you want to jump to and press RETURN. The word "end"
36184 represents the last thread. Press ^C to cancel jumping to another thread.
36185 ========== h_oe_debuglevel ==========
36186 Higher number shows more debugging details.
36187 Press ^C if you want to cancel the change.
36188 ========== h_oe_broach ==========
36189 Type the name of the folder you want to open and press RETURN. Press ^P/^N
36190 to go to the previous/next collections in the list. Press ^C to cancel goto.
36191 ========== h_oe_foldsearch ==========
36192 Type the text you want to search for in foldernames and press RETURN. If you
36193 press RETURN without entering anything, any text in [] will be searched for.
36194 ========== h_oe_foldrename ==========
36195 Change the old name of the folder to the new name using the arrow and
36196 delete keys and press RETURN. Press ^C to cancel rename.
36197 ========== h_oe_login ==========
36198 Enter your login name for the host you are opening the mailbox on. Just press
36199 RETURN to use your login from this host as is, or edit it with delete key.
36200 ========== h_oe_passwd ==========
36201 Type your password for the host and login shown as part of the prompt.
36202 Press ^C to cancel opening folder.
36203 ========== h_oe_choosep ==========
36204 Enter the number associated with the printer you want to select. Press ^C to
36205 cancel the printer selection. The current selection is highlighted.
36206 ========== h_oe_customp ==========
36207 Type the name of the Unix print command and press RETURN. Press ^C to
36208 cancel the printer selection.
36209 ========== h_oe_searchview ==========
36210 Type the word or name you want to search for and press RETURN. If you press
36211 RETURN without entering anything the word in [] will be searched for.
36212 ========== h_oe_keylock ==========
36213 The keyboard is in use and locked by another user. Only that user can
36214 unlock this keyboard by typing the password.
36215 ========== h_wt_expire ==========
36216 At the beginning of each month Alpine offers to rename your current sent-mail
36217 folder to one named for the month so you have a sent-mail folder for each month
36218 ========== h_wt_delete_old ==========
36219 It is the beginning of the month, and we need to conserve disk
36220 space. Please delete any sent-mail that you do not need.
36221 ========== h_select_sort ==========
36222 Select the order for sorting the index by typing the capitalized letter.
36223 Arrival is by arrival in your mailbox; Date is by time/day message was sent.
36224 ========== h_no_F_arg ============
36225 Enter name of file to be opened.
36227 ========== h_sticky_personal_name ==========
36228 Type in your name as you want it to appear on outgoing email. This entry
36229 will be saved into your Alpine configuration file.
36230 ========== h_sticky_inbox ============
36231 INBOX syntax is usually {complete.machine.name}INBOX
36232 This entry will be saved in your Alpine configuration file.
36233 ========== h_sticky_smtp ============
36234 The name of the computer on your campus that relays your outgoing email
36235 to the Internet. This entry will be saved in your Alpine configuration file.
36236 ========== h_sticky_user_id ==========
36237 The username or login-id part of your email address. This entry will be
36238 saved in your Alpine configuration file.
36239 ========== h_sticky_domain ==========
36240 The domain part of your email address, NOT the name of your PC. This
36241 entry will be saved in your Alpine configuration file.
36242 ========== h_bounce =========
36243 Enter the address or nickname of the intended recipient. Alpine will resend
36244 the message, which will retain the original author's From: address.
36245 ========== h_incoming_add_folder_nickname =========
36246 Enter an (optional) nickname that will be used in lieu of the actual
36247 host and folder names in the FOLDER LIST display.
36248 ========== h_anon_forward ==========
36249 Enter the address of your intended recipient, or ^C to cancel.
36250 Example: jsmith@somewhere.edu
36251 ========== h_news_subscribe ==========
36252 Enter the name of the newsgroup to which you wish to subscribe,
36253 or ^C to cancel. Example: comp.mail.pine
36254 ========== h_pipe_msg ==========
36255 Enter the name of the Unix command to which you wish to send this
36256 message, or ^C to cancel.
36257 ========== h_pipe_attach ==========
36258 Enter the name of the Unix command to which you wish to send this
36259 attachment, or ^C to cancel.
36260 ========== h_select_by_num ==========
36261 Enter a list of message numbers (or number ranges), or ^C to cancel. The word
36262 "end" represents the last message. Example: 2-5,7-9,11,19,35-end
36263 ========== h_select_by_thrdnum ==========
36264 Enter a list of thread numbers (or number ranges), or ^C to cancel. The word
36265 "end" represents the last thread. Example: 2-5,7-9,11,19,35-end
36266 ========== h_select_txt_from ==========
36267 Messages with From: headers containing the entered string will be selected.
36268 ^C to cancel. ^G again to see original options.
36269 ========== h_select_txt_not_from ==========
36270 Messages without From: headers containing the entered string will be selected.
36271 ^C to cancel. ^G again to see original options.
36272 ========== h_select_txt_to ==========
36273 Messages with To: headers containing the entered string will be selected.
36274 ^C to cancel. ^G again to see original options.
36275 ========== h_select_txt_not_to ==========
36276 Messages without To: headers containing the entered string will be selected.
36277 ^C to cancel. ^G again to see original options.
36278 ========== h_select_txt_cc ==========
36279 Messages with Cc: headers containing the entered string will be selected.
36280 ^C to cancel. ^G again to see original options.
36281 ========== h_select_txt_not_cc ==========
36282 Messages without Cc: headers containing the entered string will be selected.
36283 ^C to cancel. ^G again to see original options.
36284 ========== h_select_txt_subj ==========
36285 Messages with Subject: headers containing the entered string will be selected.
36286 ^C to cancel. ^X enters Subject: line of current message.
36287 ========== h_select_txt_not_subj ==========
36288 Messages without Subject headers containing the entered string will be selected.
36289 ^C to cancel. ^X enters Subject: line of current message.
36290 ========== h_select_txt_all ==========
36291 All messages containing the entered string will be selected. Headers and body,
36292 but not encoded attachments, will be compared. Enter ^C to cancel.
36293 ========== h_select_txt_not_all ==========
36294 All messages that don't contain the entered string will be selected. Headers
36295 and body, but not encoded attachments, will be compared. Enter ^C to cancel.
36296 ========== h_select_txt_body ==========
36297 All messages containing the entered string will be selected. Body text, but
36298 not headers or encoded attachments, will be compared. ^C to cancel.
36299 ========== h_select_txt_not_body ==========
36300 All messages that don't contain the entered string will be selected. Body
36301 text, but not headers or encoded attachments, will be compared. ^C to cancel.
36302 ========== h_select_txt_recip ==========
36303 Messages with Cc: or To: headers containing the entered string will be selected.
36304 ^C to cancel. ^G again to see original options.
36305 ========== h_select_txt_not_recip ==========
36306 Messages without Cc: or To: headers containing the string will be selected.
36307 ^C to cancel. ^G again to see original options.
36308 ========== h_select_txt_partic ==========
36309 Messages with Cc, To, or From headers containing the string will be selected.
36310 ^C to cancel. ^G again to see original options.
36311 ========== h_select_txt_not_partic ==========
36312 Messages without Cc, To, or From headers containing the string will be selected.
36313 ^C to cancel. ^G again to see original options.
36314 ========== h_select_date ==========
36315 If typed, date may be in DD-MMM-YYYY format (04-Jul-2006) or in ISO format
36316 (2006-07-04). ^P/^N also changes default date. ^X enters date of current msg.
36317 ========== h_attach_index_whereis ==========
36318 Enter some text that appears in the Attachment Index entry for the desired
36319 attachment. The first attachment containing that text will be highlighted.
36320 ========== h_kb_lock ==========
36321 Keystrokes entered here (up to a RETURN) comprise a password that must
36322 be entered again later in order to unlock the keyboard.
36323 ========== h_compose_default ==========
36324 N, compose a new message. R, set a role.
36325 ^C to cancel.
36326 ========== h_untranslatable ==========
36327 Send using UTF-8 character set; Send but replace untranslatable characters
36328 with question marks; return to the composer; or cancel message altogether.
36329 ========== h_compose_intrptd ==========
36330 N, compose a new msg. I, continue interrupted msg. R, set a role.
36331 ^C to cancel.
36332 ========== h_compose_postponed ==========
36333 N, compose a new message. P, continue postponed msg. R, set a role.
36334 ^C to cancel.
36335 ========== h_compose_intrptd_postponed ==========
36336 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
36337 R, set a role. ^C to cancel.
36338 ========== h_compose_form ==========
36339 N, compose a new message. F, use form letter. R, set a role.
36340 ^C to cancel.
36341 ========== h_compose_intrptd_form ==========
36342 N, compose a new msg. I, continue interrupted msg. F, use form letter.
36343 R, set a role. ^C to cancel.
36344 ========== h_compose_postponed_form ==========
36345 N, compose a new message. P, continue postponed msg. F, use form letter.
36346 R, set a role. ^C to cancel.
36347 ========== h_compose_intrptd_postponed_form ==========
36348 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
36349 F, use form letter. R, set a role. ^C to cancel.
36350 ========== h_config_context_del_except ==========
36351 If you delete the last exceptional collection you can only add it back by
36352 manually editing the exceptions config file.
36353 ========== h_config_whereis ==========
36354 To move quickly to a particular line, enter a search string or
36355 ^C to cancel.
36356 ========== h_config_edit_scorei ==========
36357 Enter interval in the form (min,max). -INF and INF may be used to represent
36358 -infinity and infinity. ^C to cancel change. RETURN to accept change.
36359 ========== h_config_add ==========
36360 Enter desired value; use normal editing keys to modify (e.g. ^K, ^D). Just
36361 pressing RETURN sets the Empty Value (this turns off any global default).
36362 ========== h_config_add_custom_color ==========
36363 Enter a header fieldname. For example, "subject" or "from".
36365 ========== h_config_add_pat_hdr ==========
36366 Enter a header fieldname. For example, "reply-to" or "organization" or
36367 any fieldname you want that isn't included already.
36368 ========== h_config_print_opt_choice ==========
36369 You may edit either the initialization string (characters printed before
36370 printing starts) or the trailer string. Choose one or ^C to cancel.
36371 ========== h_config_print_init ==========
36372 Enter a C-style string for this. You may use common backslash escapes like
36373 \\n for newline, \\ooo for octal character, and \\xhh for hex character.
36374 ========== h_config_change ==========
36375 Edit the existing value using arrow keys, ^K to delete entire entry, ^D to
36376 delete current (highlighted) character, etc. Enter ^C to cancel change.
36377 ========== h_config_replace_add ==========
36378 Replace ignores the current default, Add places the current default in your
36379 editing buffer as if you had typed it in.
36380 ========== h_config_insert_after ==========
36381 Enter a nickname for this print command. (InsertBefore puts the new item
36382 before the current line, InsertAfter puts it after the current line.)
36383 ========== h_config_print_cmd ==========
36384 Enter command to be executed for the printer. Use normal editing keys
36385 to modify, ^C to cancel, carriage return to accept current value.
36386 ========== h_config_role_del ==========
36387 Answering Yes will remove this rule completely from your rules list.
36388 ========== h_config_role_addfile ==========
36389 Type the name of a file to add to your configuration. You don't need to
36390 use a file, you may add rules directly (with Add) without using a file.
36391 ========== h_config_role_delfile ==========
36392 Answering Yes will remove this rule file completely from your rules list.
36393 The rules data file itself will not be removed.
36394 ========== h_config_print_del ==========
36395 Answering Yes will remove this printer completely from your printer list.
36396 ========== h_config_print_name_cmd ==========
36397 You may edit the Nickname of this printer, the Command to be executed when
36398 printing, or change the Options associated with this printer.
36399 ========== h_send_check_fcc ==========
36400 Yes, send message without an Fcc.
36401 No, return to composer.
36402 ========== h_send_check_subj ==========
36403 Yes, send message without a Subject.
36404 No, return to composer.
36405 ========== h_send_check_to_cc ==========
36406 Yes, send message without a To address, or a Cc address, or a Newsgroup.
36407 No, return to composer.
36408 ========== h_send_fcc_only ==========
36409 Yes, copy message to Fcc only and send to NO recipients.
36410 No, return to composer.
36411 ========== h_send_prompt ==========
36412 Yes, send the message.
36413 No or ^C, return to composer.
36414 ========== h_send_prompt_flowed ==========
36415 Yes, send the message. No or ^C, return to composer.
36416 What's Flowed? See Do Not Send Flowed Text in config screen.
36417 ========== h_send_prompt_dsn ==========
36418 Yes, send the message. No or ^C, return to composer.
36419 What's DSNOpts? See Enable Delivery Status Notification in config screen.
36420 ========== h_send_prompt_dsn_flowed ==========
36421 Yes, send the message. No or ^C, return to composer. What's DSNOpts? See
36422 Enable Delivery Status Notification. What's Flowed? See Do Not Send Flowed Text.
36423 ========== h_role_confirm ==========
36424 Yes, use displayed role. No, compose without a role.
36425 ^C, cancel the message. ^T, select a role from your other eligible roles.
36426 ========== h_norole_confirm ==========
36427 Return, compose without a role.
36428 ^C, cancel the message. ^T, select a role from your eligible roles.
36429 ========== h_custom_print ==========
36430 Enter a Unix command that accepts its data on standard input.
36431 Alpine will display any information the command sends to standard output.
36432 ========== h_convert_abooks_and_sigs ==========
36433 You will be given the opportunity to convert address books and signature files
36434 to remote configurations.
36435 ========== h_convert_abooks ==========
36436 You will be given the opportunity to convert address books to remote
36437 configurations.
36438 ========== h_flag_keyword ==========
36439 Enter the name of the keyword you want to add for this folder.
36440 No spaces, parentheses, braces, percents or asterisks are allowed.
36441 ========== h_select_keyword ==========
36442 Enter the keyword you want to match, or use ^T to select a keyword from a list
36443 of possible keywords for this folder. Use ! to look for non-matches instead.
36444 ========== h_type_keyword ==========
36445 Enter the keyword you want to add. You may add a nickname in the next step.
36446 No spaces, parentheses, braces, percents or asterisks are allowed.
36447 ========== h_type_keyword_nickname ==========
36448 Enter an optional nickname for the keyword you want to add.
36449 Type Carriage return to use the keyword name instead of a nickname.
36450 ========== h_convert_sigs ==========
36451 You will be given the opportunity to convert signature files to remote
36452 configurations.
36453 ========== h_convert_abook ==========
36454 Yes is fairly safe. You will be ADDing a remote address book that is a copy
36455 of the current address book. The current abook won't be removed automatically.
36456 ========== h_convert_sig ==========
36457 Answering Yes copies the contents of the signature file into your Alpine
36458 configuration file. After that, the contents of the file will not be used.
36459 ========== h_save_addman ==========
36460 Enter the simple name of the folder you want to add. Carriage return to
36461 accept what you have typed so far. ^C to get back to SELECT FOLDER screen.
36462 ========== h_reopen_folder ==========
36463 Yes reopens the folder, as if you were starting over. This uncovers new mail.
36464 No leaves the folder index as it was without discovering new mail.
36465 ========== h_convert_pinerc_server ==========
36466 This is the name of the host (computer) where the remote Alpine configuration
36467 will be stored. This should be an IMAP server that you have permission to use.
36468 ========== h_convert_pinerc_folder ==========
36469 Enter the correct remote folder name. This folder is special and should
36470 contain only configuration data. It shouldn't contain other mail messages.
36471 ========== h_role_compose ==========
36472 Compose a New message, Reply to current message, Forward current message, or
36473 Bounce message. Then you will be asked to choose one of your Roles to be used.
36474 ========== h_save_size_changed ==========
36475 The reported size of a message is not the same as the actual size. Answer Yes
36476 to continue and hope for the best or No to Cancel the entire Save.
36477 ========== h_select_by_larger_size ==========
36478 Enter a number or ^C to cancel. All messages greater than this many characters
36479 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
36480 ========== h_select_by_smaller_size ==========
36481 Enter a number or ^C to cancel. All messages less than this many characters
36482 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
36483 ========== h_preserve_field ==========
36484 Use 'p' to toggle between preserving or not preserving the original To:
36485 and Cc: fields of the message. Enter ^C to cancel message.