| blob | acd3863b0218cfd3eb81da6d55b4ff00dc3d0de4 |
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 88 2015-08-07 17:43:07
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> HTML: Add support for decoding entities in hexadecimal notation.
200 Suggested by Tulipánt Gergely.
202 <LI> If the charset of a message can not be determined, use the value set
203 in the <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A> for its value.
205 <LI> Resizing setup screen will redraw screen.
207 <LI> Unix Alpine only. Experimental: If Alpine/Pico finds a UCS4 code
208 in the width ambiguous zone, it will use other means to determine
209 the width, such as call wcwidth.
211 <LI> Pico: Code reorganization in the search command to make it easier to
212 add subcommands of the search command.
214 <LI> Pico: Search command can do a case sensitive match. Use the Ctrl-^
215 subcommand of the search command to bring this choice into view.
217 <LI> Pico: Add the ability to search for strings in the beginning or end
218 of a line. Use the Ctrl-^ subcommand of the search command to bring
219 this choice into view.
221 <LI> For a multipart/alternative message, the Take Address command will
222 work on the part that is being read.
224 <LI> When sending a message, allow for 512 characters of consecutive
225 non-white space before folding the subject line.
227 <LI> Make sure titlebar (the line at the top of the screen) always
228 contains the name of the folder/newsgroup that is open, if this
229 fits in the title.
231 <LI> The feature <a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
232 will also scramble the name, version and operative system in the message-id header.
233 Based on a contribution by Dennis Davis, which is itself based on a contribution by
234 Mark Hills.
236 <LI> Change in logic in imap_set_password function to make Alpine ask if
237 a user wants to save a password before reading the password file.
239 <LI> Add the Control-R subcommand to the save command for attachments.
240 This subcommand toggles if the saving will be done in binary mode
241 for text attachments. When a user saves an attachment using binary
242 mode it will be saved as it was sent, otherwise the attachment will
243 be transformed to UTF-8 for further transformation through internal
244 and user defined filters for saving.
246 <LI> Add command line argument -smimedir, which allows to specify
247 the default path for a directory that contains the public, private,
248 and ca directories. This is useful in case a user has a backup of
249 old certificates that cannot be installed in the ~/.alpine-smime
250 dir.
251 </UL>
254 <P>
255 Bugs that have been addressed include:
256 <UL>
257 <LI> SMIME: Crash when a certificate has an invalid date of validity. Also
258 Alpine will use the function ASN1_TIME_print to determine the date
259 of validity. Reported by Ben Stienstra.
261 <LI> SMIME: Crash when atempting to unlock the password file and an
262 incorrect password is entered.
264 <LI> SMIME: Crash when checking the signature of a message that contains
265 a RFC822 attached message. Reported by Holger Trapp and Björn
266 Krellner.
268 <LI> SMIME: Cancelling entering password to unlock key will not reprompt.
270 <LI> Pico: Searching for a string that is too long causes Pico to crash
271 in the next search.
273 <LI> Fix vulnerability in regex library. This only affects those who use
274 this library, such as the windows version of Alpine. See
275 <A HREF="http://www.kb.cert.org/vuls/id/695940">http://www.kb.cert.org/vuls/id/695940</A>
276 for more details.
278 <LI> Alpine would not set include and lib paths for OpenSSL if this was
279 installed in /usr/local/ssl.
281 <LI> If the .pinerc file is a symbolic link, Alpine might not write its
282 contents when saving its configuration.
284 <LI> The _INIT_ token does not skip over non-alpha numeric characters in
285 the name. Reported by Andreas Fehr.
287 <LI> Mismatch in size of UCS and CELL caused a corruption in the
288 content of a pointer, which made the speller in PC-Alpine get the
289 content of a word incorrectly.
291 <LI> Skip testing openssl compatibility version when cross-compilation
292 is detected. Fix contributed by Antti Seppälä
294 <LI> Alpine fails to remove temporary files used during a display or sending
295 filter. Fix contributed by Phil Brooke.
297 </UL>
300 <P>
301 Version 2.20 addresses bugs found in previous releases and has several
302 additions as well.
304 <P>
305 Additions include:
306 <P>
308 <UL>
309 <LI> Upgrade UW-IMAP to Panda IMAP from
310 <A HREF="https://github.com/jonabbey/panda-imap">https://github.com/jonabbey/panda-imap</A>.
311 <LI> S/MIME: Add screen to manage certificates.
312 <LI> S/MIME: Signatures are validated using the user's certificates instead
313 of the ones included in the message. Behavior can be disabled by
314 disabling the option <A href="h_config_smime_use_cert_store">
315 <!--#echo var="FEAT_smime-use-storey-only"--></A>, which is enabled
316 by default.
317 <LI> S/MIME: sign messages using intermediate certificates when needed
318 and possible.
319 <LI> S/MIME: validation of certificates for servers that modify signed
320 content.
321 <LI> S/MIME: signed and encrypted messages will be signed first and
322 encrypted second, so that they can be decoded by other clients.
323 <LI> S/MIME: add the sender certificate to the list of certificates in
324 encrypted messages to make it possible for the sender to decrypt
325 the message they sent.
326 <LI> S/MIME: When transferring certificates to a local container, create
327 container with default names PublicContainer, PrivateContainer and
328 CAContainer, as appropriate for these files, unless the user has
329 provided some other names.
330 <LI> S/MIME: Forwarding a message will include the signed part as part
331 of the text and not as a multipart message, just as the reply
332 command does.
333 <LI> HTML: Style tag in body of html message causes Alpine to not write
334 its content until a new </style>
335 <LI> HTML: <BR>, <BR />, and <BR/> are considered
336 the same inline tag; the same is valid for the <HR> tag.
337 <LI> Add support to selective expunge through a subcommand of the
338 select-apply commands. Read more in the <A
339 HREF="h_index_cmd_expunge">help</A> for the expunge command.
340 <LI> Pico: New subcommand of the search command, allows to reverse the
341 direction of search.
342 <LI> Unix Alpine: If a password file is defined, and S/MIME is enabled,
343 the key and certificate used to encrypt the password file are saved
344 in the ~/.alpine-smime/.pwd directory, or in the directory specified
345 by the -pwdcertdir command line option.
346 <A HREF="h_password_file_support">Learn more</A>.
347 <LI> Add /tls1, /tls1_1, /tls1_2 and /dtls1 to the definition of a
348 server to use different ways to connect using ssl, for
349 example {server.com/tls1} will attempt to connect to
350 server.com at the ssl imap port (port 993) and establish a
351 connection using TLSv1. These flags can be used in
352 conjunction with the /ssl flag, the ssl flag is redundant.
353 Conversely, however, the /ssl flag does not imply any of
354 these flags; the /ssl flag means SSLv3 or, if not available,
355 SSLv2 in the SSL port.
356 <LI> Alpine does not attempt to automatically reopen a collection
357 that was not opened due to cancellation by the user.
358 Instead, the user must try to open it explicitly.
359 <LI> Alpine searches for a certificate that matches an email address in
360 all addresses in a certificate (instead of just the first
361 one) but when it tries to unlock the certificate, it asks
362 for the password for the first email address in that
363 certificate.
364 <LI> Style tag in body of html message causes Alpine to not write its content
365 until a new </style>
366 <LI> Experimental: Write the content-type of a message in
367 lowercase, as some non-compliant servers do not understand
368 uppercase content-type, such as those of GMX.de.
369 <LI> Experimental: Do not send the RSET command before attempting
370 to send a message, as this causes a delay in some evily managed
371 servers.
372 <LI> Opening a folder updates recent count in maildrops (this
373 already works for other types of folders)
374 <LI> Automatically redraw screen after opening an attachment
375 instead of simply clearing it.
376 <LI> Pico: Justification works without need of a predefined quote
377 string. This allows justification of blocks of text that are
378 indented with spaces.
379 <LI> Decode the name of attachment names, so they can be written as part
380 of the description of the part.
381 <LI> Check bounds and tie strings off to improve security. Contributed
382 by James Jerkins.
383 <LI> Replace tabs by spaces in From and Subject fields to control for
384 size in screen of these fields. Change only in index screen display.
385 <LI> Aggregate operations allows bouncing a list of messages using a role.
386 Suggested by Ulf-Dietrich Braumann.
387 <LI> Disable saving new passwords to the password file. Implemented
388 by Louis Raphael from dpslabs.com. <A HREF="h_config_disable_password_file_saving">Learn more.</A>
389 <LI> Makefile: Add $(LIBINTL) to the flags to link rpdump, rpload,
390 alpined and alpineldap because MAC OSX 10.8 x86_64 needs it. Reported by
391 Charles M. Register.
392 </UL>
395 <P>
396 Bugs that have been addressed include:
397 <UL>
398 <LI> Fix _INIT_ token for reply quote string to include support for 8-bit
399 in personal names. Reported by Lev Gorenstein.
400 <LI> When writing the .pinerc file, lines were truncated if they were longer
401 than 10,000 characters. This could cause data corruption, so now lines
402 are allowed to be of any length.
403 <LI> In Unix Alpine (but not in MAC OSX) fix a problem that made Alpine
404 remove attachments before they were open by a mailcap viewer. It
405 requires that the user has an equivalent to a command such as "ps
406 auxww" to list the list of processes, and check if there is any
407 program using the attachment. The default is "/bin/ps auxww", but
408 it can be changed at compile time with the option --with-ps-cmd.
409 See the help of the variable
410 <a href="h_config_psleep"><!--#echo var="VAR_mailcap-check-interval"--></a>
411 for more information.
412 <LI> S/MIME: signed messages that contained an attachment would not validate.
413 <LI> S/MIME: signed and encrypted messages from Thunderbird would not
414 validate. Thanks to Andreas Schamanek for testing, debugging and
415 advising during the process of fixing this problem.
416 <LI> S/MIME: Forwarding messages with multipart content-type failed to be signed
417 with "Error writing pipe" message. Reported by Andreas Schamanek
418 and Stefan Mueller.
419 <LI> S/MIME: Certificates are lost when using a pinerc file outside of the
420 home directory.
421 <LI> S/MIME: Accessing the S/MIME configuration screen would deinitialize
422 SMIME making it not possible to sign or encrypt messages.
423 <LI> S/MIME: Forwarding a signed message might make the body contain mime
424 information that is not part of the body, and hence making the body
425 of the message seem wrong.
426 <LI> S/MIME Alpine would compute incorrectly the signature of a message
427 that contains 8bit if the option "Enable 8bit ESMTP Negotiation" is
428 enabled, the message contains 8bit characters and the smtp server
429 supports 8bit sending.
430 <LI> When replying to several messages, subject will be decoded first,
431 and then stripped from re/fwd before they are compared to determine
432 the subject of the replied message.
433 <LI> Crash when tcp connection to NNTP server was lost after connection
434 had been established, but lost immediately afterwards.
435 <LI> Crash with message "lock when already locked", when painting
436 an index was based on scores that needed information from a remote
437 addressbook in the same server as the folder opened. Reported by
438 Peter Koellner.
439 <LI> Crash in message/rfc822 attachments encoded in base64.
440 <LI> Postponed messages whose content-type is text/html, text/enriched and
441 text/richtext are sent with that content-type, even though, after
442 resuming composition, Alpine had changed its type to text/plain.
443 <LI> Alpine cannot handle correctly some characters in the Windows-1256
444 character set, which might lead to a crash or a corruption in the
445 screen. Work was done to contain the bug. A more complete fix will
446 be done in a future release. Reported by Professor Robert Funnell.
447 <LI> WebAlpine: add _GNU_SOURCE to make pubcookie build.
448 <LI> WebAlpine: fail to build with debug disabled. Fix from Sam Hathaway.
449 <LI> Save command did not warn of existence of a message with a deleted
450 attachment in an aggregate save, unless cursor was positioned on a message
451 with a deleted attachment. Reported by Florian Herzig.
452 <LI> Transformation of UTF-8 to MUTF7 was not being done when creating a folder
453 in an IMAP server.
454 <LI> DATE tokens were not internally transformed to UTF-8, which made their
455 values not appear complete in the screen. Reported by Werner Scheinast.
456 <LI> Fixes to configure script so that it will not require PAM for every system.
457 <LI> Fix to configure script so that it will use CPPFLAGS instead of
458 CPPCFLAGS, and so the --with-ssl-include-dir option take effect
459 during the build. Fix by Ulf-Dietrich Braumann.
460 <LI> Fix in WebAlpine: do not use deprecated dereference in pointer,
461 needs to use tcl_getstringresult() instead. Reported by
462 Ulf-Dietrich Braumann.
463 <LI> Quoted string in URL Viewers configuration variable were not
464 unquoted before passing to viewer.
465 <LI> Fix in configure script to detect location of tcl library; add
466 /usr/local in FreeBSD and fix a bug in configure script that used
467 $alpine_TCLINC instead of $alpine_TCLINC/tcl.h. Reported and fixed
468 by Werner Scheinast.
469 <LI> Move SSL configurations from UW-IMAP to configure script, and
470 update OpenSSL configuration for Mac OS X.
471 <LI> Remove -lregex from linker flags when building --with-supplied-regex.
472 <LI> When the download of an attachment is interrumpted, Alpine stills
473 caches what was downloaded, making the download incomplete for
474 subsequent calls of Alpine attempting to open the attachment. In the
475 future, Alpine will not cache any downloaded part of the attachment
476 when it is interrupted.
477 </UL>
478 <P>
481 <P>
482 Version 2.11 addresses bugs found in previous releases and has a few
483 additions as well.
485 <P>
486 Additions include:
487 <P>
489 <UL>
490 <LI> Alpine requires version 1.0.0c of Openssl to build.
491 <LI> Increase encryption of S/MIME encrypted messages.
492 <LI> Pico: Improvements in justification of paragraphs: lines that begin
493 with a quote string, followed by a space were considered individual paragraphs,
494 now they are considered part of a paragraph. Based on earlier joint work
495 with Jeff Franklin.
496 <LI> Unix Alpine: Allow local .pinerc file to be a symbolic link.
497 <LI> Experimental extended support of recognition of UTF-8 in urls based on
498 information from <A HREF="http://url.spec.whatwg.org">http://url.spec.whatwg.org</A>.
499 <LI> Added recognition of ws and wss URIs.
500 <LI> Add ability to <A HREF="h_config_folder_color">color folder names</A>,
501 <A HREF="h_config_directory_color">directory names</A>,
502 and <A HREF="h_config_folder_list_color">text</A> in the FOLDER SCREEN.
503 <LI> Add the ability to <A HREF="h_config_indextoken_color">color any token</A>
504 used in the display of the INDEX SCREEN.
505 <LI> New option <A HREF="h_config_preserve_field"><!--#echo var="FEAT_preserve-original-fields"--></A>
506 that adds the ability to preserve To: and Cc: fields when replying to a
507 message, as specified by original sender.
508 <LI> Add a _SILENT_ token to the <A HREF="h_config_display_filters">list of tokens</A>
509 for a display filter, so that Alpine will not redraw the screen when it is unnecessary.
510 <LI> Quota command includes subcommands for printing, forwarding, etc.
511 </UL>
513 <P>
514 Bugs that have been addressed include:
515 <P>
516 <UL>
517 <LI> Crash when a non-compliant SMTP server closes a connection without a QUIT command.
518 <LI> Crash when resizing the screen in a configuration screen.
519 <LI> Do not bail out during a tcp timeout, instead close connection and avoid crash.
520 <LI> Do not use a shell to open a browser.
521 <LI> Configure script did not test for crypto or pam libraries.
522 <LI> Configure script attempted to build web component, even if header file tcl.h was not present.
523 <LI> Change Cygwin directory separator to "/".
524 <LI> Alpine could set List- headers, contrary to RFC 2369.
525 </UL>
527 <P>
528 Version 2.10 addresses bugs found in previous releases and has a few
529 additions as well.
531 <P>
532 Additions include:
533 <P>
535 <UL>
536 <LI> Quota report for IMAP folders that support it (press the "@" command in the index screen of such folder).
537 <LI> Search a folder for the content of any header with the ";" command.
538 <LI> Foreign characters are decoded correctly in IMAP folder names.
539 <LI> Question about breaking connection to slow servers includes their name.
540 <LI> Internal x-alpine-help: resource locator for sending links to internal help.
541 <LI> OpenSuse: Alpine find location of OpenSSL certificates.
542 <LI> Cygwin: Alpine builds without need of patch.
543 <LI> Recognition of proper mime type for docx, xlsx, and pptx files.
544 <LI> When composing a message, Alpine will create a new thread when the subject is erased.
545 <LI> Add support for strong encryption of password file when S/MIME is built in.
546 </UL>
548 <P>
549 Bugs that have been addressed include:
550 <P>
552 <UL>
553 <LI> Alpine will close a folder after confirming with user their intention and not reopen it.
554 <LI> Double allocation of memory in Pico.
555 <LI> Alpine does not give warning of message sent and posted upon receipt by email of message posted in newsgroup.
556 <LI> Handling of STYLE html parameter may make Alpine not display the content of a message.
557 <LI> Not recognition of environment variables in some options.
558 <LI> Not display of login prompt during initial keystrokes.
559 <LI> justification of long urls breaks them.
560 <LI> Incorrect New Mail message when envelope is not available.
561 <LI> Incorrect display of PREFDATE, PREFDATETIME and PREFTIME tokens.
562 <LI> Crash when resizing the screen after display of LDAP search.
563 <LI> Crash when redrawing screen while opening a remote folder collection.
564 <LI> Infinite loop in scrolltool function during notification of new mail.
565 <LI> No repaint of the screen after midnight was done when the SMARTDATE token is used in the index screen.
566 <LI> No display of signed and encrypted S/MIME messages.
567 <LI> Alpine will not build with OpenSSL.
568 <LI> Crash for double locking in calls to c-client.
569 <LI> Bad recognition of mime-encoded text may make Alpine not print the subject of a message.
570 <LI> Ignore the references header when threading messages
571 <LI> No update of colors in index screen after update to addressbook.
572 </UL>
574 <P>
575 Version 2.01 addresses bugs found in previous releases and has a few
576 additions as well.
578 <P>
579 Additions include:
580 <P>
582 <UL>
583 <LI> Fixed non-ASCII web alpine handling
584 <LI> Added web alpine help.
585 <LI> Allow web alpine inbox on second IMAP server.
586 <LI> Allow web alpine config reset after bad inbox-path gets set.
587 <LI> Added web alpine ability to create group contact from contact list members.
588 <LI> Backed out web alpine coercing of default sort-key of arrival to date/reverse.
589 <LI> Tidied up web alpine script layout.
590 <LI> Fixed web alpine status message ordering
591 <LI> Added web alpine Fcc setting via Contacts in Compose
592 <LI> Fixed web alpine autodraft attachment issues
593 <LI> Fixed web alpine problems with recent count maintenance
594 <LI> Fixed web alpine newmail arrival display in message list
595 <LI> Added web alpine confirmation to folder create for Move/Copy
596 <LI> Added web alpine user-domain support
597 <LI> Fixed web alpine to support INBOX-within-a-collection deletion
598 </UL>
600 <P>
601 Bugs that have been addressed include:
602 <P>
604 <UL>
605 <LI> In web alpine fixed delete all selected within a search result to reorient
606 correctly to whole-mailbox message list.
607 <LI> Fixed web alpine delete in view page to be sensitive to sort
608 <LI> Fixed web alpine open of folder within directory from folder manager page.
609 <LI> Fixed web alpine open of folder within directory from left column's recent cache.
610 <LI> Fixed web alpine problems with spaces in special folder names like Drafts
611 <LI> Fixed web alpine adding contacts from message list and view
612 <LI> Fixed web alpine create of non-existent fcc
613 <LI> Remove mistakenly left debugger statement in web alpine javascript.
614 <LI> Some UNIX alpine build problems fixed
615 <LI> Crash in pico and pilot when nl_langinfo returned something unrecognizable
616 or NULL. Add recognition of "646" to nl_langinfo wrapper. This is returned
617 by locale charmap call on some Solaris 8 systems.
618 <LI> MacOS Keychain logins were not working correctly with generic host names, like
619 imap.gmail.com, as opposed to specific instances like rx-in-209.google.com, causing
620 new password requests when not needed
621 <LI> Possible crash in WhereIs command while in FOLDER LIST when cursor is located on the
622 last folder in the list
623 <LI> Change to S/MIME get_x509_subject_email so that X509v3 alternative names are
624 looked for along with the email address
625 <LI> Changes to configure to get spellcheck options with work with arguments.
626 <LI> Add change from Mark Crispin of panda.com to at least minimally handle non-ascii hostname
627 returned by gethostname (iPhone can do this)
628 <LI> Fixed a bug that prevents a filter that moves a message into a local folder
629 from also setting the DELETE flag in that moved message. Fix from Eduardo Chappa.
630 <LI> Changed size of shellpath in open_system_pipe from 32 to MAXPATH. Fix from
631 Jake Scott of marganstanley.com.
632 <LI> Buffer overflow bug in c-client's tmail/dmail, fix from Mark Crispin. This
633 is not used in alpine.
634 <LI> Imapd server crash from unguarded fs_give in IDLE code, fix from Crispin.
635 Apparently this causes RIM Blackberry BIS service problems. This is not
636 used in alpine.
637 <LI> Tmail uninitialized pointer fix from Neil Hoggarth. Not used in alpine.
638 <LI> Buffer overflow possibility in RFC822BUFFER routines in c-client library.
639 Fix from Ludwig Nussel of SUSE and from Crispin.
640 <LI> Include whole filename in export filename history
641 <LI> Fix display bug in pico when Replace command is canceled. Fix from Eduardo Chappa.
642 </UL>
644 <P>
645 Version 2.00
646 addressed bugs found in previous releases and had a few additions as well.
647 <P>
648 Additions included:
649 <P>
651 <UL>
652 <LI> Redesigned Web Alpine interface
653 <LI> Experimental <A HREF="h_mainhelp_smime">S/MIME support</A> added
654 in UNIX versions of Alpine
655 <LI> Attempt to include the attachment filename as part of the name of the
656 temporary file used when viewing an attachment with an external program.
657 Add some randomness to that filename to make it hard to predict the filename.
658 Add a filename extension, usually derived from the type/subtype, to the
659 temporary filename. This was previously done only on Windows and MacOS X.
660 <LI> Enhance address completion in the composer (TAB command) so that it looks
661 through nicknames, fullnames, and addresses from the address book; addresses
662 from the message being viewed, if any; and the results from
663 <A HREF="h_direct_config">LDAP Directory Server</A>
664 lookups for all of the defined directory servers that have the
665 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
666 feature set.
667 <LI> Make the default character set setting more liberal in what it will accept
668 from the UNIX nl_langinfo call and the various values of LANG seen in the wild
669 <LI> Remove the Alpine revision number from the titlebar in released versions
670 while leaving it there in snapshot versions
671 <LI> Add a <A HREF="h_config_quell_asterisks">feature</A> to suppress the
672 display of asterisks when you type a password for Alpine
673 <LI> Add line wrapping when displaying <EM>PRE</EM> formatted sections of HTML
674 <LI> When the
675 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
676 feature is turned on convert not only the dates in the index screen but also
677 the dates in the MESSAGE VIEW
678 </UL>
680 <P>
681 Bugs addressed in the 2.00 release included:
682 <P>
684 <UL>
685 <LI> Crash when using tab-completion for selecting a Save filename
686 <LI> Make Web Alpine help text images relative for more portability
687 <LI> Fixed attach save of html parts in Web Alpine
688 <LI> Viewing, printing, exporting, replying, and bouncing of message
689 digests was broken. Replying and bouncing should not have been
690 allowed at all for digests. It would be nice to have a more standard
691 index-like view of a message digest but that has not been addressed
692 with this minor bug fix.
693 <LI> Adjust wrapping of HTML messages so that the margins specified by
694 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
695 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>
696 are observed correctly
697 <LI> Interrupt of WhereIs command in index was broken
698 <LI> The <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
699 option did not work correctly interpreting unknown characters in message headers
700 <LI> Long address lines could cause blank continuation lines
701 <LI> Save to a local default INBOX failed if the primary collection was also local,
702 which it is by default. The save went to ~/mail/inbox instead.
703 <LI> Make a default save folder of "inbox" always mean the real
704 inbox, not the inbox in the primary collection
705 <LI> Address book entries with lots of addresses would be truncated when
706 entered in the composer with a screen size wider than 270 or so charcters
707 <LI> Some fields in the index screen were truncated when the screen width was
708 wider than 256 characters
709 <LI> Crash when TABing to next folder, the next folder with new mail is a POP
710 folder, and there is a more than 10 minute pause between typing the TAB
711 and typing the Yes
712 </UL>
714 <P>
715 Version 1.10(962)
716 addressed bugs found in previous releases and had a few additions as well.
717 <P>
718 Additions included:
719 <P>
721 <UL>
722 <LI> Add the possibility of setting a default role
723 (see <A HREF="h_role_select">Roles Screen</A>)
724 which may be convenient if your work flow involves acting in one
725 role for a while then switching to another role and staying in the
726 new role for another period of time
727 <LI> When Saving and the IMAP server problem "Message to save shrank!"
728 is encountered, ask the user if he or she wants to continue with the
729 risky Save anyway instead of aborting. This may be helpful if your
730 IMAP server is broken in this way but be aware that it is possible there
731 was a real error instead of just a broken server implementation.
732 <LI> Some configure adjustments for Kerberos detection and
733 for SCO OpenServer 5 support
734 <LI> Hide INBOX in a collection if it also appears as an
735 <A HREF="h_config_enable_incoming">Incoming Folder</A>
736 <LI> Show asterisks for feedback when the user is typing a password
737 <LI> Performance improvement for threading of large folders
738 <LI> Previously, the search used to find
739 Pattern matches containing To patterns searched for both To
740 and Resent-To headers. The relatively complicated search this
741 produces causes problems when using some deficient IMAP servers.
742 Now the default is to look only for To headers and ignore the
743 presence of Resent-To. The previous behavior may be restored
744 with the <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> feature.
745 <LI> Add an
746 <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
747 to help with reading malformed unlabeled messages
748 <LI><A HREF="h_config_suppress_user_agent"><!--#echo var="FEAT_suppress-user-agent-when-sending"--></A> option added
749 <LI> Map some Shift-LeftArrow escape sequences to LeftArrow
750 <LI> Add feature <A HREF="h_config_warn_if_fcc_blank"><!--#echo var="FEAT_warn-if-blank-fcc"--></A>
751 </UL>
753 <P>
754 Bugs addressed in the 1.10(962) release included:
755 <P>
757 <UL>
758 <LI> Crash when encountering certain errors from an SMTP server
759 <LI> Crash in composer caused by overflow in replace_pat()
760 <LI> Hang when authenticating to an SMTP server that fails with a
761 "connection disconnected" error
762 <LI> Bug in handling of trailing tab character in flowed text
763 <LI> Security enhancement for mailcap parameter substitution
764 <LI> <A HREF="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></A>
765 did not work if the message being replied to was not flowed text
766 and <A HREF="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></A>
767 was not turned on
768 <LI> Don't allow printer to be changed through hidden config screen
769 if system administrator didn't want it to be allowed
770 <LI> Attempts are sometimes made to set the Forwarded flag when alpine
771 should know that it won't work, causing error messages to appear
772 <LI> A <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
773 of double-quote double-quote didn't work right
774 <LI> Quoting wasn't being done to protect special characters from the
775 MacOS X shell when
776 <A HREF="h_config_browser"><!--#echo var="VAR_url-viewers"--></A>
777 was not defined
778 <LI> On MacOS X message attachments should be shown internally instead of
779 being shown using the Mail application
780 <LI> When replying to a message with a charset of X-UNKNOWN Alpine would
781 sometimes set the outgoing charset to X-UNKNOWN, making the result
782 unreadable
783 <LI> When the sending of a message failed lines with leading spaces had one
784 additional space inserted in each of those lines when the user
785 was returned to the composer
786 <LI> The <A HREF="h_index_cmd_whereis">WhereIs</A> command missed some index lines
787 that contained non-ascii characters because it was truncating the
788 line being searched so that it was shorter than what was visible on
789 the screen
790 <LI> When composing, an attachment with a long name that causes wrapping in
791 just the wrong place would generate an error and cause the send
792 of the attachment to fail
793 <LI> After calling the file browser to attach a file in the composer, a resize
794 of the window when back in the composer would redraw the last screen that
795 had been shown in the browser instead of the current composer screen
796 <LI> Possible crash in index screen when encountering unparseable addresses
797 or when using one of the PRIORITY tokens or the HEADER token in the
798 <a href="h_config_index_format"><!--#echo var="VAR_index-format"--></a>
799 <LI> Problems with Header Color editing if the configuration option
800 <a href="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></a>
801 was inadvertently changed to the Empty Value in the hidden config screen
802 <LI> When resuming the final postponed message from an Exchange server the user
803 could get a certificate validation failure because alpine was trying
804 to validate the canonical name of the folder instead of the name the
805 user used
806 <LI> Windows line endings in a mimetypes file on a Unix system cause a
807 failure to find a match
808 <LI> Make matching of extension names case independent in mimetypes files
809 <LI> Windows dialog boxes for entering text were not working correctly
810 <LI> Replying to or Forwarding multipart/alternative messages which had a
811 single text/html part did not work well
812 <LI> Printing the print confirmation page caused a crash
813 <LI> A To line with a long, quoted personal name could display incorrectly
814 if it was close to the same width as the screen
815 <LI> When <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
816 and <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
817 are turned on hide (0/0) when the folder is empty
818 <LI> Folder completion while Saving didn't work if the collection being
819 saved to was the local home directory
820 </UL>
822 <P>
823 Version 1.00
824 was an evolutionary release based on
825 <A HREF="http://www.washington.edu/pine/">Pine</A>, which was also
826 developed at the University of Washington.
827 It is upwards-compatible for existing Pine users.
829 <P>
830 Changes included:
831 <P>
832 <UL>
833 <LI> Ground-up reorganization of source code around addition
834 of "pith/" core routine library.
835 <LI> Fundamental improvement in Alpine's internal text handling, which
836 is now based exclusively on Unicode. This allows displaying incoming
837 messages and producing outgoing messages in many different languages.
838 <LI> Ground-up reorganization of build and install procedures
839 based on GNU Build System's autotools. NOTE, the included IMAP library
840 build is not based on autotools, so some features will not work. However,
841 it should get built automatically during the Alpine build process.
842 <LI> Web-based version included built on TCL designed to run under
843 a suitable CGI-supporting web server such as Apache.
844 </UL>
846 <P>
848 Details on changes in previous (prerelease) versions of Alpine
849 may be found at the following URL:
850 <P>
851 <CENTER><SAMP><A HREF="http://patches.freeiz.com/alpine/release/">http://patches.freeiz.com/alpine/release/</A></SAMP></CENTER>
852 <P>
854 <HR WIDTH="75%"><P>
856 <H2>Getting Help</H2>
857 <DL>
858 <DT>Online Help</DT>
859 <DD>
860 Every Alpine screen and command has associated help text
861 accessible via the "?" key (or Ctrl-G in text-input contexts).
862 </DD>
864 <DT>Web Help</DT>
865 <DD>
866 The most current source of information about Alpine,
867 including new version availability, is the web page at
868 <P>
869 <CENTER><SAMP><A HREF="http://patches.freeiz.com/alpine/">http://patches.freeiz.com/alpine/</A></SAMP></CENTER>
870 </DD>
871 </DL>
873 Frequently Asked Questions (and answers) may be found at the following
874 URL:
875 <P>
876 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/faq/">http://www.washington.edu/alpine/faq/</A></SAMP></CENTER>
877 <P>
879 <HR WIDTH="75%"><P>
881 <H2>Additional Information</H2>
883 General Alpine configuration information can be found
884 <A HREF="h_news_config">here</A>.
885 <P>
886 This is revision (<!--#echo var="ALPINE_REVISION"-->) of the Alpine software.
887 Alpine mailbox and <A HREF="https://github.com/jonabbey/panda-imap/">IMAP</A> server
888 access is provided by the IMAP Toolkit Environment (c-client library)
889 version <!--#echo var="C_CLIENT_VERSION"-->.
890 <P>
891 Alpine was developed until 2009 by the Office of Computing
892 & Communications at the University of Washington in Seattle.
893 Since then, the effort of developing Alpine has been continued by
894 a community of volunteers who make good software even better!
896 <P>
897 Alpine Copyright 2013-2015 Eduardo Chappa,
898 <BR> Copyright 2006-2008 University of Washington.
900 <P>
901 Additional legal notices can be found <A HREF="h_news_legal">here</A>,
902 or instead you can find the Apache License, version 2.0 at the web URL:
904 <P>
905 <CENTER><A HREF="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</A></CENTER>
907 <P>
908 <End of Release Notes>
909 </BODY>
910 </HTML>
911 ====== h_password_file_support ======
912 <HTML>
913 <HEAD>
914 <TITLE>Encryption for Password File Support Explained</TITLE>
915 </HEAD>
916 <BODY>
917 <H1>Encryption for Password File Support Explained</H1>
919 Index<BR>
920 <OL>
921 <LI><A HREF="#content">Explanation</A>
922 <LI><A HREF="#example">Example</A>
923 </OL>
925 <P><A NAME="content">Unix Alpine Only.</A>
927 <P> If your version of Alpine has been built with password file support
928 then you can use a special file to save your passwords, and avoid typing
929 them every time you open a connection to a remote server.
931 <P> If your version of Alpine was built with SMIME support, and you have a
932 public certificate/private key pair, then Alpine will use such pair to
933 encrypt your password file. If you have more than one key/certificate
934 pair, Alpine will pick the first pair that it finds that works. You can also
935 select a pair, and the way to do this is explained below.
937 <P> Once a pair has been chosen, it will be copied to the directory
938 ~/.alpine-smime/.pwd, and from then on, Alpine will use the pair found in
939 that directory. The first time this process is done, this directory will
940 be created, a key/certificate pair will be copied to it, and this pair
941 will be used in the future to encrypt and decrypt your password file. You
942 can create this directory and copy any key/certificate pair there. You
943 can add a self-signed certificate there, if you like, and you can let
944 this certificate expire. This will not affect the encryption and decryption
945 of the password file.
947 <P> If you prefer not to use the directory ~/.alpine-smime/.pwd to save
948 your key/certificate pair, you can specify a different one with the
949 -pwdcertdir command line option in Alpine. If the directory specified by
950 this option is not found or there is no valid key/certificate pair there,
951 Alpine will fail to encrypt and decrypt your password file. In other words,
952 Alpine will not initialize this directory for you.
954 <P> Alpine does not care about the names of the key and certificates in
955 this directory, but the private key must have ".key" extension
956 and your public certificate must have the ".crt" extension. The
957 name of the private key will be used in the prompt when you are asked
958 to unlock your key to decrypt your password.
960 <P><A NAME="example">An example follows</A>
962 <P>Assume you have a private key called peter@address.com.key in your,
963 ~/.alpine-smime/private directory, and a public certificate called
964 peter@address.com.crt in your ~/.alpine-smime/public directory, and these
965 are your only key/certificate pair.
967 <P> When Alpine starts for the first time, without command line options,
968 it will check if the directory ~/.alpine-smime/.pwd exists, and if not,
969 it will create it. Then it will go through your keys and certificates and
970 find a pair that it can use, and copy the files peter@address.com.key,
971 and peter@address.com.crt to the ~/.alpine-smime/.pwd directory. Alternatively
972 you can do the same by copying these files by yourself. This can be done
973 with the sequence of commands
975 <PRE>
976 mkdir ~/.alpine-smime/.pwd
977 cp ~/.alpine-smime/private/peter@address.com.key ~/.alpine-smime/.pwd
978 cp ~/.alpine-smime/public/peter@address.com.crt ~/.alpine-smime/.pwd
979 </PRE>
981 <P> When Alpine starts, you will be asked the password to unlock your
982 private key with the prompt.
984 <PRE>
985 Enter password of key <peter@address.com> to unlock password file:
986 </PRE>
988 <P> If you prefer to use different names for your private and public keys
989 in the ~/.alpine-smime/.pwd directory, you can do so, but you must
990 preserve the extension of the files. For example, you can use the names
991 private_key.key and public_cert.crt instead. In this case, the prompt you
992 will see when you are asked to unlock your private key will read
994 <PRE>
995 Enter password of key <private_key> to unlock password file:
996 </PRE>
998 <P>Observe that you do not need to use an existing key/certificate pair,
999 and that you can create a new private key/public certificate pair to
1000 encrypt and decrypt your password. However, once one is used, Alpine does
1001 not provide a mechanism to switch the encryption and decryption files to
1002 another key/certificate pair. This will be implemented in a future
1003 release of Alpine.
1005 <P>
1006 <End of help>
1007 </BODY>
1008 </HTML>
1009 ====== h_tls_failure_details ======
1010 <HTML>
1011 <HEAD>
1012 <TITLE>Certificate Validation Details</TITLE>
1013 </HEAD>
1014 <BODY>
1015 <H1>Certificate Validation Details</H1>
1017 This screen gives details as to why the certificate validation failed: the
1018 name of the desired server system; the reason for failure; and the name on
1019 the certificate. This is primarily of interest to experts.
1021 <P>
1022 <End of help>
1023 </BODY>
1024 </HTML>
1025 ====== h_tls_failure ======
1026 <HTML>
1027 <HEAD>
1028 <TITLE>TLS or SSL Failure</TITLE>
1029 </HEAD>
1030 <BODY>
1031 <H1>TLS or SSL Failure</H1>
1033 An attempt was made to establish a secure, encrypted connection to the
1034 server system using either Transport Layer Security (TLS) or the older
1035 Secure Sockets Layer (SSL). This attempt failed.
1037 <P>
1038 You should contact your server system management for more assistance.
1039 The problem is probably at the server system and not in Alpine or your local
1040 system. The text in this screen may be helpful for the server system
1041 management in debugging the problem,
1043 <P>
1044 <End of help>
1045 </BODY>
1046 </HTML>
1047 ====== h_tls_validation_failure ======
1048 <HTML>
1049 <HEAD>
1050 <TITLE>TLS and SSL Certificate Validation Failures</TITLE>
1051 </HEAD>
1052 <BODY>
1053 <H1>TLS and SSL Certificate Validation Failures</H1>
1055 An attempt was made to establish a secure, encrypted connection to the
1056 server system using either Transport Layer Security (TLS) or the older
1057 Secure Sockets Layer (SSL).
1059 <P>
1060 An important part of this procedure is server certificate validation. A
1061 server certificate is an "electronic identification card" for the server
1062 system that is signed by a well-known certificate authority (CA). Alpine
1063 compares the server system identity in the server certificate with the
1064 name of the server system to which it is trying to connect. Alpine also
1065 verifies that the CA signature is authentic.
1067 <P>
1068 Some common failure conditions are:
1069 <P>
1071 <UL>
1072 <LI> [UNIX Alpine] Self signed certificate. This means that the server system
1073 signed its own certificate. This does not necessarily indicate anything
1074 bad; the server operators may simply have elected to not purchase a
1075 signed certificate from a certificate authority.
1077 <LI> [UNIX Alpine] Unable to get local issuer certificate. This means that
1078 the signature on the server system is from an unknown certificate authority.
1079 It can also mean that no certificate authority certificates have been
1080 installed on the local UNIX system.
1082 <LI> [PC Alpine] Self-signed certificate or untrusted authority. This is
1083 the same as either of the above two conditions in UNIX Alpine. Note that
1084 Windows systems typically have a full set of certificate authority
1085 certificates installed, so it is more likely to be a self-signed
1086 certificate than an unknown certificate authority.
1088 <LI> Server name does not match certificate. This means that the server
1089 presented a proper signed certificate for a name other than the desired
1090 name.
1091 </UL>
1093 <P>
1094 Any of these conditions can indicate that you are being attacked and have
1095 been directed to an imposter server that will record your password and
1096 your private mail messages. It can also mean something innocuous.
1098 <P>
1099 If you are certain that the problem is innocuous, you can append the
1100 option
1102 <P>
1103 <CENTER><SAMP>/novalidate-cert</SAMP></CENTER>
1104 <P>
1106 to the server system name where it appears in your configuration (e.g. the
1107 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>,
1108 a folder-collection, or a news or SMTP server). This will
1109 disable certificate validation. On the other hand, if you are attacked,
1110 you will get no warning if you do this.
1112 <P>
1113 <End of Cert Validation Failures help>
1114 </BODY>
1115 </HTML>
1116 ====== h_release_tlscerts ======
1117 <HTML>
1118 <HEAD>
1119 <TITLE>TLS and SSL usage note</TITLE>
1120 </HEAD>
1121 <BODY>
1122 <H1>TLS and SSL usage note</H1>
1124 <P>
1125 When using Alpine from Unix or Windows 2000,
1126 server certificates must be signed by a trusted certificate authority.
1127 You may relax this requirement (at the cost of some security) by using
1128 the
1129 <A HREF="h_folder_server_syntax">NoValidate-Cert</A>
1130 modifier in the mailbox name.
1132 <P>
1133 <CENTER><SAMP>{foo.example.com/novalidate-cert}INBOX</SAMP></CENTER>
1134 <P>
1136 The fully-qualified host name of the server should be used
1137 so that it matches the host name in the server certificate.
1138 <P>
1139 Here is an example of a host specification that directs Alpine to use
1140 the SSL port (993) and an encrypted data stream.
1141 <P>
1142 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
1143 <P>
1144 <End of TLS usage help>
1145 </BODY>
1146 </HTML>
1147 ====== h_news_config ======
1148 <HTML>
1149 <HEAD>
1150 <TITLE>Alpine Configuration</TITLE>
1151 </HEAD>
1152 <BODY>
1153 <H1>Alpine Configuration</H1>
1155 <H2>Using Environment Variables</H2>
1157 The values of Alpine configuration options may include environment variables
1158 that are replaced by the value of the variable at the time Alpine is run
1159 (and also at the time the config option is changed).
1160 The syntax to use environment variables is a subset of the common Unix
1161 shell dollar-syntax.
1162 For example, if
1164 <P><CENTER><SAMP>$VAR</SAMP></CENTER><P>
1166 appears in the value of an Alpine configuration option it is looked up in the
1167 environent (using getenv("VAR")) and its
1168 looked-up value replaces the <SAMP>$VAR</SAMP> part of the option value.
1169 To include a literal dollar sign you may precede the dollar sign with another
1170 dollar sign.
1171 In other words, if the text
1173 <P><CENTER><SAMP>$$text</SAMP></CENTER><P>
1175 is the value of a configuration option, it will be expanded to
1177 <P><CENTER><SAMP>$text</SAMP></CENTER><P>
1179 and no environment lookup will be done.
1180 For Unix Alpine it will also work to use a backslash character to
1181 escape the special meaning of the dollar sign, but $$ is preferable since
1182 it works for both PC-Alpine and Unix Alpine, allowing the configuration option
1183 to be in a shared configuration file.
1184 <P>
1186 This all sounds more complicated than it actually is.
1187 An example may make it clearer.
1188 Unfortunately, the way in which environment variables are set is OS-dependent
1189 and command shell-dependent.
1190 In some Unix command shells you may use
1192 <P><CENTER><SAMP>PERSNAME="Fred Flintstone"</SAMP></CENTER><P>
1193 <CENTER><SAMP>export PERSNAME</SAMP></CENTER><P>
1195 Now, if you use Alpine's Setup/Config screen to set
1197 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=$PERSNAME</SAMP></CENTER><P>
1199 the <SAMP>$PERSNAME</SAMP> would be replaced by <SAMP>Fred Flintstone</SAMP>
1200 so that this would be equivalent to
1202 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=Fred Flintstone</SAMP></CENTER><P>
1204 Note, environment variable substitution happens after configuration
1205 options that are lists are split into the separate elements of the list,
1206 so a single environment variable can't contain a list of values.
1208 <P>
1209 The environment variable doesn't have to be the only thing
1210 after the equal sign.
1211 However, if the name of the variable is not at the end of the line or
1212 followed by a space (so that you can tell where the variable name ends),
1213 it must be enclosed in curly braces like
1215 <P><CENTER><SAMP>${VAR}</SAMP></CENTER><P>
1217 It is always ok to use the braces even if you don't need to.
1218 <P>
1219 It is also possible to set a default value for an environment variable.
1220 This default value will be used if the environment variable is not
1221 set (that is, if getenv("VAR") returns NULL).
1222 The syntax used to set a default value is
1224 <P><CENTER><SAMP>${VAR:-default value}</SAMP></CENTER><P>
1226 If the config file contains
1228 <P><CENTER><SAMP>personal-name=${VAR:-Fred Flintstone}</SAMP></CENTER><P>
1230 then when Alpine is run <SAMP>VAR</SAMP> will be looked up in the environment.
1231 If <SAMP>VAR</SAMP> is found then <SAMP>personal-name</SAMP> will have
1232 the value that <SAMP>VAR</SAMP> was set to, otherwise,
1233 <SAMP>personal-name</SAMP> will be set to <SAMP>Fred Flintstone</SAMP>,
1234 the default value.
1235 (Note that the variable is called "personal-name" in the config
1236 file but is displayed in the config screen as
1237 "<!--#echo var="VAR_personal-name"-->".
1238 In general, the value that goes into a config file is never exactly the
1239 same as the value you see on the screen.)
1241 <P>
1242 An example where an environment variable might be useful is the
1243 variable <SAMP>Inbox-Path</SAMP> in the global configuration file.
1244 Suppose most users used the server
1246 <P><CENTER><SAMP>imapserver.example.com</SAMP></CENTER><P>
1248 but that there were some exceptions who used
1250 <P><CENTER><SAMP>altimapserver.example.com</SAMP></CENTER><P>
1252 In this case, the system manager might include the following line in
1253 the systemwide default Alpine configuration file
1255 <P><CENTER><SAMP>Inbox-Path=${IMAPSERVER:-imapserver.example.com}</SAMP></CENTER><P>
1257 For the exceptional users adding
1259 <P><CENTER><SAMP>IMAPSERVER=altimapserver.example.com</SAMP></CENTER><P>
1261 to their environment should work.
1262 <P>
1263 Another example might be the case where a user has to use a different
1264 SMTP server from work and from home.
1265 The setup might be something as simple as
1267 <P><CENTER><SAMP>smtp-server=$SMTP</SAMP></CENTER><P>
1269 or perhaps a default value could be given.
1270 Note that, as mentioned above, the variable <SAMP>SMTP</SAMP> cannot contain
1271 a list of SMTP servers.
1272 <P>
1274 <H2>Configuration precedence</H2>
1276 There are several levels of Alpine configuration. Configuration values at
1277 a given level override corresponding values at lower levels. In order of
1278 increasing precedence:
1279 <P>
1280 <UL>
1281 <LI> built-in defaults
1282 <LI> system-wide
1283 <!--chtml if pinemode="os_windows"-->
1284 config file from command line or provided
1285 by "PINECONF" environment variable
1286 <!--chtml else-->
1287 pine.conf file
1288 <!--chtml endif-->
1289 <LI> personal configuration file
1290 <LI> personal exceptions configuration file
1291 <LI> command-line options
1292 <!--chtml if pinemode="os_windows"--><!--chtml else-->
1293 <LI> system-wide pine.conf.fixed file<!--chtml endif-->
1294 </UL>
1295 <P>
1296 The values in both the personal configuration file and the
1297 <A HREF="h_config_exceptions">exceptions</A>
1298 configuration file may be set using the Setup command.
1299 Setup/Config is the command to change most of the personal configuration
1300 options.
1301 The other Setup subcommands are also used to change the configuration,
1302 for example, Setup/AddressBook, Setup/Rules, and so on.
1303 Changing the personal exceptions configuration is very similar.
1304 To change a value in the Config screen you would use the command
1305 Setup/eXceptions/Config.
1306 Likewise for the other Setup subcommands (Setup/eXceptions/Rules and so on).
1307 <P>
1308 There are a couple exceptions to the rule that configuration values are replaced
1309 by the value of the same option in a higher-precedence file.
1310 The Feature-List variable has values that are additive, but can be
1311 negated by prepending "no-" in front of an individual feature name.
1312 So for features, each individual feature's value is replaced by the value
1313 of the same feature in a higher-precedence file.
1314 Note that this is done automatically for you when you change these values via
1315 the Setup/Config command.
1316 The other exception to the <EM>replace</EM> semantics happens when you
1317 use <A HREF="h_config_inheritance">configuration inheritance</A>
1318 for option lists.
1319 <P>
1321 <H2>File name defaults</H2>
1323 Notes:<P>
1325 <BR> <exe dir> = directory where pine.exe found.
1326 <BR> <pinerc dir> = directory where pinerc found.
1327 <BR> # = default file name is overridable in pinerc.
1328 <BR> $HOME, if not explicitly set, defaults to root of the current drive.
1329 <BR> $MAILCAPS, if set, is used in lieu of the default mailcap search paths.
1330 <BR> + between the mailcap paths implies that the two files are combined.
1331 <BR> ; between other default paths implies that the first one found is used.
1332 </P>
1333 Alpine looks for most support files in the same directory it finds its
1334 personal configuration file (pinerc). The -p command-line flag may be
1335 used to specify a particular path name for the pinerc file. If a
1336 pinerc file does not exist, it will be created (if directory permissions
1337 allow). In PC-Alpine, if -p or $PINERC are not defined, Alpine will look
1338 in $HOME\PINE and the directory containing the PINE.EXE. If a PINERC
1339 file does not exist in either one, it will create one in the first of those
1340 two directories that is writable. In detail:
1341 <PRE>
1343 PC-Alpine:
1345 executable <DOS search path>\pine.exe
1346 help index <exe dir>\pine.ndx
1347 help text <exe dir>\pine.hlp
1349 pers config $PINERC ; $HOME\pine\PINERC ; <exe dir>\PINERC
1350 except config $PINERCEX ; $HOME\pine\PINERCEX ; <exe dir>\PINERCEX
1351 global cfg $PINECONF
1353 debug <pinerc dir>\pinedebg.txtN
1354 crash <pinerc dir>\pinecrsh.txt
1355 signature# <pinerc dir>\pine.sig
1356 addressbook# <pinerc dir>\addrbook
1357 mailcap# <pinerc dir>\mailcap + <exe dir>\mailcap
1358 mimetypes# <pinerc dir>\mimetype + <exe dir>\mimetype
1359 newsrc# $HOME\newsrc (if exists, else) <pinerc dir>\newsrc
1360 sentmail# $HOME\mail\sentmail.mtx
1361 postponed# $HOME\mail\postpond.mtx
1362 interrupted $HOME\mail\intruptd
1364 Unix Alpine:
1366 executable <Unix search path>/pine
1367 persnl cfg ~/.pinerc
1368 except cfg ~/.pinercex
1369 global cfg <!--#echo var="PINE_CONF_PATH"-->
1370 fixed cfg <!--#echo var="PINE_CONF_FIXED_PATH"-->
1371 local help <!--#echo var="PINE_INFO_PATH"-->
1373 interrupted ~/.pine-interrupted-mail
1374 debug ~/.pine-debugN
1375 crash ~/.pine-crash
1376 newsrc# ~/.newsrc
1377 signature# <pinerc dir>/.signature
1378 addressbook# <pinerc dir>/.addressbook
1379 postponed# ~/mail/postponed-msgs
1380 sentmail# ~/mail/sent-mail
1381 mailcap# ~/.mailcap + /etc/mailcap
1382 + /usr/etc/mailcap + /usr/local/etc/mailcap
1383 mimetypes# ~/.mime.types + /etc/mime.types + /usr/local/lib/mime.types
1385 news-spool varies across Unix flavors, e.g. /var/spool/news or /usr/spool/news
1386 active-news varies across Unix flavors, e.g. /usr/lib/news/active
1387 lock files /tmp/.<!--#echo var="MAIL_SPOOL_LOCK_PATH"-->
1388 inbox <!--#echo var="MAIL_SPOOL_PATH"-->
1389 password /etc/passwd
1391 Unix Alpine and PC-Alpine:
1393 .ab* remote addressbook support files
1394 a[1-9]* temporary (while Alpine is running) addressbook files
1396 </PRE>
1397 <P>
1399 <H2>Mailcap files</H2>
1401 Alpine honors the mailcap configuration system for specifying external
1402 programs for handling attachments. The mailcap file maps MIME attachment
1403 types to the external programs loaded on your system that can display
1404 and/or print the file. A sample mailcap file comes bundled with the Alpine
1405 distribution. It includes comments that explain the syntax you need to
1406 use for mailcap. With the mailcap file, any program (mail readers,
1407 newsreaders, WWW clients) can use the same configuration for handling
1408 MIME-encoded data.
1409 <P>
1411 <H2>MIME-Types files</H2>
1413 Alpine uses mime-types files (.mime.types or MIMETYPE) to determine
1414 what Content-Type to use for labeling an attached file, based on
1415 the file extension. That is, this file provides a mapping between
1416 filename extensions and MIME content-types.
1417 <P>
1419 <H2>Environment variables</H2>
1421 PC-Alpine uses the following environment variables:
1422 <DL>
1423 <DT>PINERC</DT>
1424 <DD>Optional path to pinerc file.</DD>
1425 <DT>PINERCEX</DT>
1426 <DD>Optional path to personal exceptions configuration file.</DD>
1427 <DT>PINECONF</DT>
1428 <DD>Optional path to global pine config file.</DD>
1429 <DT>HOME</DT>
1430 <DT>TMPDIR, TMP, or TEMP</DT>
1431 <DT>COMSPEC</DT>
1432 <DT>MAILCAPS</DT>
1433 <DD>A <B>semicolon</B> delimited list of path names to mailcap files.</DD>
1434 <DT>USER_DICTIONARY</DT>
1435 <DD>Used to specify the file to contain the user's spell check
1436 dictionary. The default is <SAMP>DICT.U</SAMP> in the same
1437 directory as the <SAMP>SPELL32.DLL</SAMP></DD>
1438 </DL>
1440 Unix Alpine uses the following environment variables:
1441 <DL>
1442 <DT>TERM</DT>
1443 <DD>Tells Alpine what kind of terminal is being used.</DD>
1444 <DT>DISPLAY</DT>
1445 <DD>Determines if Alpine will try to display IMAGE attachments.</DD>
1446 <DT>SHELL</DT>
1447 <DD>If not set, default is "/bin/sh".</DD>
1448 <DT>TMPDIR, TMP, or TEMP</DT>
1449 <DT>MAILCAPS</DT>
1450 <DD>A <B>colon</B> delimited list of path names to mailcap files.</DD>
1451 </DL>
1452 <!--chtml if pinemode="os_windows"-->
1453 <P>
1454 <H2>Common PC-Alpine Configuration Problems</H2>
1456 <H3>Configuration settings aren't being saved</H3>
1458 <P>This problem can happen if you run pine from one directory and
1459 then decide to move your pine directory to another location. PC-Alpine
1460 stores certain variables, including the configuration location, in the
1461 Windows Registry (which you shouldn't ever need to manually edit). There
1462 are a couple of ways to go about removing or resetting the values in the
1463 registry.
1465 <P>
1466 1) Run PC-Alpine's registry value deletion command. This can be done by
1467 running: "<your pine directory>\pine.exe -registry clear" from the DOS
1468 prompt. You could create a shortcut to pine.exe and change the "Target"
1469 value to the above command.
1471 <P>
1472 2) Tell PC-Alpine where to look for the configuration file. Configuration
1473 information is stored in a file called the PINERC. With the "-p PINERC"
1474 option, you can tell PC-Alpine the location of your pinerc. An example of
1475 this would be to run: "<your pine directory>\pine.exe -p C:\pine\mypinerc".
1476 Again, you can use the DOS prompt or the shortcut method explained in (1).
1478 <P>
1479 Additionally, there is the "-registry set" option, which will actively
1480 set registry values to the current setting, and is therefore useful with
1481 the "-p PINERC" option.
1483 <!--chtml endif-->
1484 <P>
1485 <End of Configuration Notes>
1486 </BODY>
1487 </HTML>
1488 ====== h_news_legal ======
1489 <html>
1490 <head>
1491 <TITLE>Alpine Legal Notices</TITLE>
1492 </head>
1493 <body>
1495 <H1>Alpine Legal Notices</H1>
1497 Alpine and its constituent programs are covered by the Apache License Version 2.0.
1500 <P>
1501 <End of Alpine Legal Notices>
1502 </BODY>
1503 </HTML>
1504 ===== h_info_on_mbox =====
1505 <HTML>
1506 <HEAD>
1507 <TITLE>Information on mbox driver</TITLE>
1508 </HEAD>
1509 <BODY>
1510 <H1>Information on "Missing Mail" and the "mbox" driver</H1>
1512 Beginning with Pine 4.00 (Pine came before Alpine)
1513 a new INBOX access method is
1514 available as part of the standard configuration. It is called the
1515 "mbox" driver and it works like this:<P>
1517 <P>
1518 <BLOCKQUOTE>
1519 If the file "mbox" exists in the user's home directory, and
1520 is in Unix mailbox format, then when INBOX is opened this file will be
1521 selected as INBOX instead of the mail spool file. Messages will be
1522 automatically transferred from the mail spool file into the mbox
1523 file.
1524 </BLOCKQUOTE>
1526 <P>
1527 The advantage of this method is that, after new mail has been copied
1528 from the system mail spool, all subsequent access is confined to the
1529 user's home directory, which is desirable on some systems. However, a
1530 possible disadvantage is that mail tools other than those from the
1531 University of Washington will not know to look for mail in the user's
1532 mbox file. For example, POP or IMAP servers other than those from the
1533 University of Washington, and many "new mail notification"
1534 programs may not work as expected with this driver enabled.<P>
1536 To disable this behavior, either remove/rename the "mbox"
1537 file or find the <A HREF="h_config_disable_drivers"><!--#echo var="VAR_disable-these-drivers"--></A>
1538 option in Setup/Config
1539 and add "mbox" to it:
1540 <P>
1541 <CENTER><SAMP><!--#echo var="VAR_disable-these-drivers"-->=mbox</SAMP></CENTER>
1542 <P>
1543 <End of help on this topic>
1544 </BODY>
1545 </HTML>
1546 ===== h_info_on_locking =====
1547 <HTML>
1548 <HEAD>
1549 <TITLE>FAQs on Alpine Locking</TITLE>
1550 </HEAD>
1551 <BODY>
1552 <H1>What Systems Managers Need to Know about Alpine File Locking</H1>
1554 There is an extensive section on locking in the Alpine technical notes;
1555 this information is intended to provide answers to some common questions:<P>
1556 <OL>
1557 <LI> Why did locking change in Pine 4.00?<BR>
1558 The actual locking mechanisms did not change in 4.00.
1559 What changed is that when one particular locking mechanism used by Alpine
1560 fails, Alpine now issues a warning message. Prior to Pine 4.00, the locking
1561 failure would occur, but no warning was issued.<P>
1563 <LI> Is this what the "Mailbox vulnerable" message is about?<BR>
1564 Yes. It means that Alpine was unable to create a lockfile in the
1565 spool directory, generally because of overly restrictive protections on the
1566 spool directory. The correct permissions on the spool directory for
1567 running Alpine are 1777, i.e. read-write-execute permission for everyone,
1568 with the sticky-bit set, so only owners of a file can delete them.<P>
1570 <LI> Why does Alpine require that the mail spool directory have 1777
1571 protections?<BR>
1572 Alpine was designed to run without special privileges. This means that in
1573 order to create a lockfile in the spool directory, it is necessary to have
1574 the spool directory permissions be world-writable.<P>
1576 <LI> Can't you create the lockfile somewhere else?<BR>
1577 No. The lockfile in question must be in the mail spool directory, because
1578 that's where the mail delivery program expects to find it, and the purpose
1579 of the file is to coordinate access between the mail client (Alpine) and the
1580 mail delivery program.<P>
1582 <LI> Isn't having the spool directory world-writable a big security risk?<BR>
1583 No. Remember that the individual mail files in the spool directory are
1584 NOT world-writable, only the containing directory. Setting the "sticky
1585 bit" -- indicated by the "1" before the "777" mode
1586 -- means that only the owner of the file (or root) can delete files in the
1587 directory. So the only bad behavior that is invited by the 1777 mode is that
1588 anyone could
1589 create a random file in the spool directory. If the spool directory is
1590 under quota control along with home directories, there is little incentive
1591 for anyone to do this, and even without quotas a periodic scan for
1592 non-mail files usually takes care of the problem. <P>
1594 <LI> Why not run Alpine as setgid mail?<BR>
1595 Alpine was never designed to run with privileges, and to do so introduces a
1596 significant security vulnerability. For example, if a user suspends Alpine,
1597 the resulting shell will have group privileges. This is one example of
1598 why we strongly recommend against running Alpine as a privileged program.
1599 In addition, a "privileged mailer " paradigm would mean that normal
1600 users
1601 could not test Alpine versions or other mailers that had not been installed
1602 by the system administrators.<P>
1605 <LI> Are there any alternatives to creating .lock files in the spool dir?<BR>
1606 There are, but they all have different sets of tradeoffs, and not all will
1607 work on all systems. Some examples:<UL>
1608 <LI> Use lock system calls. Works fine on a few systems, provided mail
1609 spool is local. Doesn't work reliably if NFS is used.
1610 Doesn't work unless <B>all</B> the mail programs accessing the spool dir
1611 use the same calls.
1612 <LI> Deliver mail to user's home directory. An excellent solution, highly
1613 recommended -- but one which is incompatible with some "legacy"
1614 mail tools that always look in the spool directory for the mail.
1615 </UL><P>
1617 <LI> Are these spool directory lock files the only kinds of locks used by
1618 Alpine?<BR>
1619 No. Alpine also creates lockfiles in the /tmp directory. For normal Unix
1620 mailbox format folders, these are used to coordinate access between
1621 multiple Alpine sessions. <P>
1623 <LI> What about the
1624 <A HREF="h_config_quell_lock_failure_warnings">"<!--#echo var="FEAT_quell-lock-failure-warnings"-->"</A> feature added in Pine 4.01?<BR>
1625 This is for people who are content to live dangerously, or who have
1626 specific knowledge that the spool directory lockfiles are superfluous on
1627 their system (because both Alpine and the mail delivery program are using
1628 system call file locking in a context that works reliably, e.g. not NFS.)<P>
1630 <LI> Where can I find more details on how Alpine locking works?<BR>
1631 See the Alpine Technical Notes.<P>
1633 </OL>
1634 <P>
1635 <End of help on this topic>
1636 </BODY>
1637 </HTML>
1638 ===== h_finding_help ====
1639 <HTML>
1640 <HEAD>
1641 <TITLE>Finding more information and requesting help</TITLE>
1642 </HEAD>
1643 <BODY>
1644 <H1>Places to Look for More Answers</H1>
1645 If you have questions about or problems with Alpine that you cannot resolve
1646 after consulting the program's internal, context-sensitive help screens, here
1647 are additional information resources that you may find helpful:
1648 <P>
1649 <UL>
1650 <LI> Alpine's top-level <A HREF="main_menu_tx">MAIN MENU HELP</A>.<P>
1652 <LI> Alpine's <A HREF="h_help_index">Help Index</A>.<P>
1654 <LI> Alpine's internal <A HREF="h_news">Release Notes</A>. They contain a
1655 listing of changes in Alpine <!--#echo var="ALPINE_VERSION"-->
1656 since the last version, which may be useful for you to be aware of,
1657 <B>especially</B> if a "problem" you are encountering is actually
1658 a change in the way an aspect of Alpine works. There, you will also find notes
1659 on Alpine configuration.<P>
1661 <LI> The main site for Alpine contains information on configuring and solving problems
1662 with Alpine, it can be found at
1664 <CENTER><A HREF="http://patches.freeiz.com/alpine/">http://patches.freeiz.com/alpine/</A></CENTER>
1666 <LI> The Alpine Information Center (maintained by the University of
1667 Washington) World Wide Web site contains, among other things
1668 <UL>
1669 <LI>a collection of Frequently Asked Questions (and answers!) about Alpine
1670 <LI>an overview of the basics for beginning Alpine users
1671 <LI>Technical Notes for systems administrators
1672 <LI>archives (including a searchable index) of the alpine-info
1673 mailing list, on which matters of interest to systems/email administrators,
1674 developers, trainers, user support personnel, and others involved with Alpine
1675 messaging on a "technical" level are discussed.
1676 </UL>
1677 The Alpine Information Center can be accessed with a WWW browser at:<P>
1678 <CENTER><A HREF="http://www.washington.edu/alpine/">http://www.washington.edu/alpine/</A></CENTER>
1679 </UL>
1680 <P><HR WIDTH="75%">
1681 <H1>Requesting help</H1>
1682 If the internal help, the Release Notes, the Alpine Information Center, and your
1683 local online and print resources do not help you resolve a problem, please
1684 start by contacting your local computer support staff and asking for help.
1685 <p>
1686 This is especially true if:
1687 <ul>
1688 <li>You suddenly have trouble sending or receiving mail.
1689 <li>You receive a "disk quota exceeded" message.
1690 <li>You have forgotten your password.
1691 <li>You think your account may have been compromised.
1692 <li>You need help viewing an attachment.
1693 <li>You need to know how to configure your:
1694 <A HREF="h_config_nntp_server">NNTP (news) server</A>,
1695 <A HREF="h_config_smtp_server">SMTP (sending mail) server</A>,
1696 <A HREF="h_config_ldap_server">LDAP (directory lookup) server</A>, or
1697 <A HREF="h_config_inbox_path">INBOX (incoming mail) path</A>.
1698 <li>You want to know what alternative editors or spellcheckers you may be able to use.
1699 <li>You want to block email from a particular person.
1700 <li>You're going on vacation and need to autorespond to incoming mail.
1701 <li>You want to automatically file or filter incoming messages.
1702 </ul>
1704 In all of these cases,
1705 you should contact <B>your</B> support staff, because <B>only they</B>
1706 will be able to assist you effectively. Your support staff may be, depending on who
1707 provides you with the email account you use Alpine with, for example:<UL>
1708 <LI> the computing help desk of (a department of) your university, school,
1709 employer, ... ; or
1710 <LI> the customer service center of your Internet Service Provider; or
1711 <LI> the friendly volunteer helpers of your Freenet; or
1712 <LI> the person who setup your computer and internet connection.
1713 </UL>
1715 Due to the large number of Alpine installations worldwide, and because we
1716 receive no funding for it, the University of Washington <B>cannot provide
1717 individual support services outside the University of Washington</B>.
1718 <P>
1719 If you have no local computing support to turn to, the worldwide <b>comp.mail.pine</b>
1720 newsgroup can be a valuable source of information and assistance for Alpine
1721 user issues.
1722 <P>
1723 For systems/email administrators, developers, trainers, user support
1724 personnel, and others involved with Alpine messaging on a "technical"
1725 level, the mailing list alpine-info is available; for information on
1726 subscribing and posting to it, see
1727 <P>
1728 <CENTER><A HREF="http://www.washington.edu/alpine/alpine-info/subscribing.html">http://www.washington.edu/alpine/alpine-info/subscribing.html</A></CENTER>
1729 <P>
1731 Regardless of whom you are asking for help with Alpine, remember
1732 to provide as much detail as you can about the
1733 nature of any problem you are encountering, such as
1734 <UL>
1735 <LI>when it first occurred;
1736 <LI>what, if anything, happened that might have brought it about;
1737 <LI>whether it still persists;
1738 <LI>whether it is reproducible, and if so, how;
1739 <LI>what, if anything, you already tried to solve it.
1740 </UL>
1741 It may also be helpful if you specify what version of Alpine you are using
1742 <!--chtml if pinemode="running"-->
1743 -- this is <!--#echo var="ALPINE_VERSION"--> --
1744 <!--chtml endif-->
1745 and on what system, and when the copy of Alpine you are using was created
1746 <!--chtml if pinemode="running"-->
1747 -- for this copy: <!--#echo var=ALPINE_COMPILE_DATE-->
1748 <!--chtml endif-->
1750 <!--chtml if pinemode="running"-->
1751 <P>
1752 When the Alpine program you are currently using was installed, a support
1753 contact email address may have been set up; in that case, you can simply select
1754 this link now to send a message to it:<BR>
1755 <A HREF="X-Alpine-Gripe:_LOCAL_ADDRESS_?local"><!--#echo var="_LOCAL_FULLNAME_"--></A><P>
1756 <!--chtml endif-->
1757 <!--chtml if [ -r PINE_INFO_PATH ]-->
1758 <HR WIDTH="75%">Local Support Contacts:<P>
1759 <!--#include file="PINE_INFO_PATH"-->
1760 <HR WIDTH="75%">
1761 <!--chtml endif-->
1762 <P>
1763 <End of help on this topic>
1764 </BODY>
1765 </HTML>
1766 ===== new_user_greeting ======
1767 <HTML>
1768 <HEAD>
1769 <TITLE>NEW USER GREETING</TITLE>
1770 </HEAD>
1771 <BODY>
1772 <CENTER><<<This message will appear only once>>></CENTER>
1773 <BR>
1774 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
1775 We hope you will explore Alpine's many capabilities. From the MAIN MENU,
1776 select Setup/Config to see many of the options available to you. Also note
1777 that all screens have context-sensitive help text available.<P>
1778 <!--chtml if pinemode="phone_home"-->
1779 SPECIAL REQUEST:
1780 This software was originally created and maintained as a public
1781 service by the University of Washington until 2009; updates are made
1782 available as a public service of the Alpine community. It is always
1783 helpful to have an idea of how many users are using Alpine. Are you
1784 willing to be counted as an Alpine user? Pressing
1785 <A HREF="X-Alpine-Phone-Home:">Return</A>
1786 will send an anonymous (meaning, your real email address will not be revealed)
1787 message to the Alpine developers for purposes of tallying.
1788 <P>
1789 <!--To Exit this screen and continue your Alpine session press "E".-->
1790 <!--chtml else-->
1791 To Exit this screen and continue your Alpine session press "Return".
1792 <!--chtml endif-->
1793 </BODY>
1794 </HTML>
1795 ===== new_alpine_user_greeting ======
1796 <HTML>
1797 <HEAD>
1798 <TITLE>NEW ALPINE USER GREETING</TITLE>
1799 </HEAD>
1800 <BODY>
1801 <CENTER><<<This message will appear only once>>></CENTER>
1802 <BR>
1803 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
1804 Your Alpine configuration file indicates that you may have used Pine before
1805 but not Alpine.
1806 If you are familiar with the way Pine works, you should be comfortable
1807 using Alpine.
1808 Your Pine configuration file is automatically used for Alpine.
1809 The Release Notes may be viewed by pressing
1810 "R" now or while in the MAIN MENU.
1811 <P>
1812 <!--chtml if pinemode="phone_home"-->
1813 SPECIAL REQUEST:
1814 This software was originally created and maintained as a public
1815 service by the University of Washington until 2009; updates are made
1816 available as a public service of the Alpine community. It is always
1817 helpful to have an idea of how many users are using Alpine. Are you
1818 willing to be counted as an Alpine user? Pressing
1819 <A HREF="X-Alpine-Phone-Home:">Return</A>
1820 will send an anonymous (meaning, your real email address will not be revealed)
1821 message to the Alpine developers for purposes of tallying.
1822 <P>
1823 <!--To Exit this screen and continue your Alpine session press "E".-->
1824 <!--chtml else-->
1825 To Exit this screen and continue your Alpine session press "Return".
1826 <!--chtml endif-->
1827 </BODY>
1828 </HTML>
1829 ===== new_version_greeting ======
1830 <HTML>
1831 <HEAD>
1832 <TITLE>NEW VERSION GREETING</TITLE>
1833 </HEAD>
1834 <BODY>
1835 <CENTER><<<This message will appear only once>>></CENTER>
1836 <BR>
1837 <H1>Welcome to Alpine version <!--#echo var="ALPINE_VERSION"-->!</H1>
1838 Your Alpine configuration file indicates that you may not have used
1839 this version of Alpine before. This version's significant changes are
1840 documented in the Release Notes, which may be viewed by pressing
1841 "R" now or while in the MAIN MENU.
1842 <P>
1843 <!--chtml if pinemode="phone_home"-->
1844 SPECIAL REQUEST:
1845 This software was originally created and maintained as a public
1846 service by the University of Washington until 2009; updates are made
1847 available as a public service of the Alpine community. It is always
1848 helpful to have an idea of how many users are using Alpine. Are you
1849 willing to be counted as an Alpine user? Pressing
1850 <A HREF="X-Alpine-Phone-Home:">Return</A>
1851 will send an anonymous (meaning, your real email address will not be revealed)
1852 message to the Alpine developers for purposes of tallying.
1853 <P>
1854 <!--To Exit this screen and continue your Alpine session press "E".-->
1855 <!--chtml else-->
1856 To Exit this screen and continue your Alpine session press "Return".
1857 <!--chtml endif-->
1858 </BODY>
1859 </HTML>
1861 ===== main_menu_tx ======
1862 <HTML>
1863 <HEAD>
1864 <TITLE>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</TITLE>
1865 </HEAD>
1866 <BODY>
1867 <H1>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</H1>
1868 <DIV ALIGN=CENTER>
1869 Version <!--#echo var="ALPINE_VERSION"-->
1870 <!--chtml if pinemode="running"-->
1871 <BR>(built <!--#echo var=ALPINE_COMPILE_DATE-->)
1872 <!--chtml endif-->
1873 </DIV>
1874 <CENTER>Copyright 2013-2015 Eduardo Chappa,
1875 <BR>Copyright 2006-2008 University of Washington.
1876 </CENTER>
1878 <P>
1879 When you are viewing a help screen, there may be links to
1880 other topics highlighted (in Reverse video) in the text.
1881 Here is an example.
1882 The word "Introduction" in the TABLE OF CONTENTS below should be
1883 highlighted.
1884 If you type carriage return (or V for View Link, see the commands at the
1885 bottom of the screen) you will be taken to a new help screen to view the
1886 Introduction.
1887 The commands at the bottom of the screen should then include
1888 "P Prev Help".
1889 If you type "P" you will end up back here.
1890 If you type "E" for Exit, you will be back out of help and returned
1891 to the place you were in Alpine when you entered Help.
1892 In this case, you would go back to the MAIN MENU.
1893 There are also other links that are highlighted in bold (or the color used
1894 by your terminal to display bold).
1895 The items after the Introduction in the TABLE OF CONTENTS are all examples
1896 of such links.
1897 In order to view those links, you first have to make the link you want
1898 to view the current link.
1899 The "NextLink" and "PrevLink" commands
1900 (see bottom of screen) can do that for you.
1901 <P>
1903 <H2>TABLE OF CONTENTS</H2>
1904 <OL>
1905 <LI> <A HREF="h_mainhelp_intro">Introduction</A>
1906 <LI> <A HREF="h_mainhelp_pinehelp">Alpine Help</A>
1907 <!--chtml if [ -r PINE_INFO_PATH ]-->
1908 <LI> <A HREF="h_mainhelp_localsupport">Local Support Contacts</A>
1909 <!--chtml endif-->
1910 <LI> <A HREF="h_mainhelp_cmds">Giving Commands in Alpine</A>
1911 <LI> <A HREF="h_mainhelp_config">Alpine Configuration</A>
1912 <LI> <A HREF="h_mainhelp_status">Titlebar Line</A>
1913 <LI> <A HREF="h_mainhelp_mainmenu">Main Menu</A>
1914 <LI> <A HREF="h_mainhelp_index">Index of Messages</A>
1915 <LI> <A HREF="h_mainhelp_reading">Reading Messages</A>
1916 <LI> <A HREF="h_mainhelp_composing">Composing Messages</A>
1917 <LI> <A HREF="h_mainhelp_readingnews">Reading News</A>
1918 <LI> <A HREF="h_mainhelp_abooks">Address Books</A>
1919 <LI> <A HREF="h_mainhelp_ldap">LDAP Directories</A>
1920 <LI> <A HREF="h_mainhelp_folders">Folders</A>
1921 <LI> <A HREF="h_mainhelp_collections">Collection Lists</A>
1922 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
1923 <LI> <A HREF="h_mainhelp_color">Color Setup</A>
1924 <LI> <A HREF="h_mainhelp_filtering">Filtering</A>
1925 <LI> <A HREF="h_mainhelp_roles">Roles</A>
1926 <LI> <A HREF="h_mainhelp_patterns">Patterns</A>
1927 <LI> <A HREF="h_mainhelp_keywords">Keywords (or Flags, or Labels)</A>
1928 <LI> <A HREF="h_mainhelp_mouse">Using a Mouse</A>
1929 <LI> <A HREF="h_mainhelp_cmdlineopts">Command Line Options</A>
1930 <LI> <A HREF="h_mainhelp_securing">Securing Your Alpine Session</A>
1931 <LI> <A HREF="h_mainhelp_smime">S/MIME</A>
1932 <LI> <A HREF="h_mainhelp_problems">Reporting Problems</A>
1933 <LI> <A HREF="X-Alpine-Config:">Show Supported Options in this Alpine</A>
1934 <LI> <A HREF="h_help_index">Index to Alpine's Online Help</A>
1935 </OL>
1937 <P>
1938 <End of help on this topic>
1939 </BODY>
1940 </HTML>
1941 ===== h_mainhelp_intro ======
1942 <HTML>
1943 <HEAD>
1944 <TITLE>Introduction</TITLE>
1945 </HEAD>
1946 <BODY>
1947 <H1>Introduction</H1>
1949 Alpine is an "Alternatively Licensed Program for Internet
1950 News and Email" produced until 2009 by the University of Washington.
1951 It is intended to be an easy-to-use program for
1952 sending, receiving, and filing Internet electronic mail messages and
1953 bulletin board (Netnews/Usenet) messages. Alpine supports the following
1954 Internet protocols and specifications: SMTP (Simple Mail Transport Protocol),
1955 NNTP (Network News Transport Protocol), MIME (Multipurpose Internet Mail
1956 Extensions), IMAP (Internet Message Access Protocol), and LDAP (Lightweight
1957 Directory Access Protocol).<p>
1959 Although originally designed for inexperienced email users, Alpine has
1960 evolved to support many advanced features. There are an ever-growing
1961 number of configuration and personal-preference options, though which of
1962 them are available to you is determined by your local system managers.
1964 <H2>WHAT ALPINE DOES...</H2>
1966 Alpine is a "mail user agent" (MUA), which is a program that
1967 allows you to
1968 compose and read messages using Internet mail standards. (Whether you
1969 can correspond with others on the Internet depends on whether or not your
1970 computer is connected to the Internet.) Alpine also allows reading and
1971 posting messages on the Internet "net news" system, provided
1972 that your site operates a suitable news server.
1974 <H2>WHAT ALPINE DOES NOT DO...</H2>
1976 A "mail user agent" such as Alpine is just one part of a
1977 messaging system. Here are some things that are <B>not</B> done by Alpine,
1978 but require other programs:<P>
1979 <UL>
1980 <LI> Actual relaying of email... which is done by "message transfer
1981 agents".
1982 <LI> Vacation messages... automatically responding to incoming messages
1983 <LI> Anything to do with "talk"... which has nothing to do with
1984 email.
1985 <LI> Anything to do with "irc"... which has nothing to do with email.
1986 <LI> List processing... resending one message to a list of recipients.
1987 </UL>
1989 <P>
1990 <End of help on this topic>
1991 </BODY>
1992 </HTML>
1994 ===== h_mainhelp_pinehelp ======
1995 <HTML>
1996 <HEAD>
1997 <TITLE>Alpine Help</TITLE>
1998 </HEAD>
1999 <BODY>
2000 <H1>Alpine Help</H1>
2002 Alpine help is generally context-sensitive. In other words, each Alpine screen you
2003 use will have its own help text, explaining the choices available for that
2004 screen. This general help section, on the other hand, attempts to give an
2005 overall picture of what Alpine is capable of doing, as well as pointers to
2006 additional help sections about specific topics.<p>
2008 Much of the help text contains links to further help topics, similar to
2009 how the World Wide Web works.
2010 You may choose a link to view using the "NextLink" and
2011 "PrevLink" commands to change the link that is highlighted.
2012 The "View Link" command will then show you the highlighted link.
2013 Similar to the Back button in a web browser, the "Prev Help" command
2014 will return you to where you were before viewing the link, and "Exit Help"
2015 will return you to the location in Alpine before you asked for help.
2016 For example, if you are reading this text in Alpine you may return to the
2017 help table of contents with the "Prev Help" command or you may view the
2018 Release notes link in the next paragraph and then return here with
2019 "Prev Help".
2020 <P>
2022 In addition to this general help on Alpine, <A HREF="h_news">Release Notes</A>
2023 on the current Alpine version are also available from the MAIN MENU: Press
2024 <!--chtml if pinemode="function_key"-->
2025 "F9"
2026 <!--chtml else-->
2027 "R"
2028 <!--chtml endif-->
2029 to browse the release notes. These include changes since the last release,
2030 configuration information, the history of the Alpine
2031 project, credits, and legal notices.
2033 Alpine releases are available via the world wide web at
2034 <P>
2035 <CENTER><SAMP><A
2036 HREF="http://patches.freeiz.com/alpine/release/">http://patches.freeiz.com/alpine/release/</A></SAMP
2037 ></CENTER>
2038 <P>
2040 If you would like to print <EM>all</EM> of Alpine's internal help text
2041 (not recommended) for a little light bedtime reading, then press
2042 <!--chtml if pinemode="function_key"-->
2043 "F12"
2044 <!--chtml else-->
2045 "Z"
2046 <!--chtml endif-->
2047 now. (This assumes that the
2048 copy of Alpine you are using has been properly configured for printing
2049 at your site.)
2050 <P>
2051 <End of help on this topic>
2052 </BODY>
2053 </HTML>
2054 ===== h_mainhelp_localsupport ======
2055 <HTML>
2056 <HEAD>
2057 <TITLE>Local Support Contacts</TITLE>
2058 </HEAD>
2059 <BODY>
2060 <H1>Local Support Contacts</H1>
2062 <!--chtml if [ -r PINE_INFO_PATH ]-->
2063 <!--#include file="PINE_INFO_PATH"-->
2064 <!--chtml else-->
2065 No Local Support Contacts configured.
2066 <!--chtml endif-->
2068 <P>
2069 <End of help on this topic>
2070 </BODY>
2071 </HTML>
2073 ===== h_mainhelp_cmds ======
2074 <HTML>
2075 <HEAD>
2076 <TITLE>Giving Commands in Alpine</TITLE>
2077 </HEAD>
2078 <BODY>
2079 <H1>Giving Commands in Alpine</H1>
2081 Unless configured otherwise
2082 (<A HREF="h_config_blank_keymenu"><!--#echo var="FEAT_disable-keymenu"--></A>)
2083 the bottom two lines of the screen are always used to list the
2084 commands you can give. You press the keys that are highlighted to give
2085 the command. The commands for getting help and going back to the main
2086 menu are always present (except when viewing help as you are now).
2087 <!--chtml if pinemode="function_key"-->
2088 <!--chtml else-->
2089 <p>
2090 Pressing O (meaning "Other Commands") changes the keys
2091 you see at the bottom of any screen. In some cases there are 3 or
2092 even 4 different
2093 sets of keys that can be seen by using the O key. <EM>All commands are
2094 active</EM>, even if they are not currently showing at the bottom of your
2095 screen. In other words, you <EM>never</EM> need to press the O key, except to
2096 remind yourself of the proper key to press to perform an operation.
2098 <H2>Control Key Commands</H2>
2099 When composing mail, and in a few other places, in Alpine you
2100 have to use Control keys. This means pressing the Control key (usually labeled
2101 "Ctrl") and the
2102 letter indicated at the same time. Usually, this is shown with a
2103 "^" in front of the letter. On some systems, certain control
2104 characters are intercepted before they get to Alpine. As a work-around,
2105 you can press the ESCAPE key twice followed by the desired key. For
2106 example, if Ctrl-O (^O) does not work on your system, try typing
2107 "ESC ESC O".
2108 <!--chtml endif-->
2109 <H2>Paging Up and Down</H2>
2110 The "+" and "-" keys are used for
2111 moving to the next or previous page. The space bar is a synonym for
2112 "+". You may also use Ctrl-V to page down and Ctrl-Y to page
2113 up as you do in the message composer. On screens with a WhereIs (search)
2114 command, W or Ctrl-W followed by Ctrl-V will move to the bottom of the
2115 message or list, and W or Ctrl-W followed by Ctrl-Y will move to the top
2116 of the message or list.
2118 <H2>Return Key</H2>
2119 The return key is usually a synonym for a frequently used
2120 command. When viewing a message, there is currently not a default
2121 command, so RETURN does nothing; when in the index, it is synonymous with
2122 "view msg". In the key menu at the bottom of the screen, whatever is
2123 enclosed in square brackets [] is the same as the return key.
2125 <H2>Control Keys Not Used By Alpine</H2>
2126 Most commands in Alpine are single letters, with -- we hope -- some mnemonic
2127 value, but in places where Alpine is expecting text input, e.g. in the composer or
2128 at prompts for file/folder names, control keys must be used for editing and
2129 navigation functions.
2130 <P>
2132 Alpine has used nearly all the control keys available. There are, however,
2133 certain control keys that are reserved by other programs or for technical
2134 reasons. Alpine does not use any of these keys:
2135 <DL>
2136 <DT>Ctrl-S</DT> <DD>Used by Unix as "stop output"</DD>
2137 <DT>Ctrl-Q</DT> <DD>Used by Unix as "resume output"</DD>
2138 <DT>Ctrl-]</DT> <DD>Often used by Telnet as escape key</DD>
2139 </DL>
2140 <P>
2141 Note: Ctrl-S and Ctrl-Q can be subject to
2142 <A HREF="h_special_xon_xoff">special handling</A>.
2143 <P>
2144 In addition, while the ESC key alone is not used for command input,
2145 Alpine will recognize two consecutive ESC key presses followed by a letter
2146 key as a substitute for control key input. For example, the control key
2147 <SAMP>Ctrl-X</SAMP> can alternatively be entered using the
2148 three keystrokes: <SAMP>ESC ESC x</SAMP>.
2149 This is useful if the communication program you are using
2150 (e.g. Telnet) has its own, conflicting, idea of what certain control
2151 characters mean.
2154 <H2>Repainting the Screen</H2>
2155 Sometimes what is displayed on the screen will be
2156 incorrect due to noise on the phone line or other causes and you will want
2157 to repaint the whole screen to make it correct. You can use the Ctrl-L
2158 command to do this. It never hurts to do it when in doubt.
2160 <P>
2161 <End of help on this topic>
2162 </BODY>
2163 </HTML>
2164 ===== h_mainhelp_status ======
2165 <HTML>
2166 <HEAD>
2167 <TITLE>Titlebar Line</TITLE>
2168 </HEAD>
2169 <BODY>
2170 <H1>Titlebar Line</H1>
2172 The top line of the screen is Alpine's titlebar line. It will always display
2173 the current version of Alpine and will also convey information about the
2174 status of the program. This is where you look to find out what
2175 collection, folder and message number is active and where you are in Alpine.
2176 <P>
2178 If the titlebar line says "READONLY" it means that the open folder
2179 (typically your INBOX) is "locked" by another mail session --
2180 most likely a more recent session of Alpine has taken the INBOX lock.
2181 <P>
2183 If the titlebar line says "CLOSED" it means that you are trying to
2184 access a
2185 folder on a remote mail server, and for some reason, communication with
2186 the mail server has either been lost, or never successfully established.
2187 This can be a result of trying to open a non-existent folder, or one
2188 stored on an invalid or non-operational server, or it can mean that Alpine
2189 has been suspended for more that 30 minutes while accessing a remote mail
2190 server.
2192 <P>
2193 <End of help on this topic>
2194 </BODY>
2195 </HTML>
2196 ===== h_mainhelp_mainmenu ======
2197 <HTML>
2198 <HEAD>
2199 <TITLE>Main Menu</TITLE>
2200 </HEAD>
2201 <BODY>
2202 <H1>Main Menu</H1>
2204 The Main Menu lists Alpine's main options.
2205 The key or keys you must type to enter your
2206 choice are to the left of each option or command name.
2207 You can type either uppercase or lowercase letters,
2208 and you should not press <Return> after typing the
2209 letter (unless you are specifically asking for the default,
2210 highlighted command).
2211 <P>
2213 From the Main Menu you can choose to read online help, write (compose) and
2214 send a message, look at an index of your mail messages, open or maintain
2215 your mail folders, update your address book, configure Alpine, and quit Alpine.
2216 There are additional options listed at
2217 the bottom of the screen as well.
2219 <P>
2220 The Help command usually returns context-sensitive help information.
2221 However, in the Main Menu you get the most general help, which includes
2222 a Table of Contents.
2223 The last entry in the Table of Contents is an Index of help topics,
2224 so this is a good place to go if you are having trouble finding how
2225 to do something.
2227 <H2>Main Menu Commands</H2>
2228 The Alpine main menu lists the most common Alpine functions. A <a
2229 href="h_main_menu_commands">full list of these
2230 commands</a> and what they do is available.
2231 <P>
2232 <End of help on this topic>
2233 </BODY>
2234 </HTML>
2235 ===== h_mainhelp_abooks ======
2236 <HTML>
2237 <HEAD>
2238 <TITLE>Address Books</TITLE>
2239 </HEAD>
2240 <BODY>
2241 <H1>Address Books</H1>
2244 As you use email, you can build a list of your regular email correspondents
2245 in your Alpine
2246 Address Book. At the Alpine MAIN MENU, press A to see the Address Book List
2247 screen. Your
2248 personal address book will be highlighted. Press <Return> to view it.
2249 You can use the address book to store email addresses for individuals or
2250 groups, to create easily
2251 remembered "nicknames" for these addresses, and to quickly retrieve an email
2252 address when you are composing a message.
2253 <P>
2254 There are two ways to add addresses to your address book: you can add them
2255 manually or take them from messages (by pressing T to access the Take command).
2256 With either method, you specify nicknames for your correspondents. A single
2257 address book entry (or nickname) can point to just one email address, or, it can
2258 point to more than one. When it points to more than one, it is called a
2259 distribution list. Each distribution list has a nickname, a full name, and a
2260 list of addresses. These
2261 addresses may be actual addresses, other nicknames in your address book, or
2262 other
2263 distribution lists.
2265 <P>
2266 Additional information is available in Alpine's online help:
2267 <ul>
2268 <li><a href="h_abook_opened">The Alpine Address Book</a></li>
2269 </ul>
2270 <P>
2271 <End of help on this topic>
2272 </BODY>
2273 </HTML>
2274 ===== h_mainhelp_ldap ======
2275 <HTML>
2276 <HEAD>
2277 <TITLE>LDAP</TITLE>
2278 </HEAD>
2279 <BODY>
2280 <H1>LDAP</H1>
2282 LDAP (Lightweight Directory Access Protocol) is a standard means of accessing
2283 an organization's shared
2284 directories. Essentially, using LDAP, Alpine is able to find email addresses in
2285 large address
2286 books, rather like the White Pages provided by the phone company. As an Alpine
2287 user, it is not
2288 necessary to know much about how this works, only how to use it and how to
2289 configure
2290 it.
2291 <P>
2292 More information on configuring LDAP is available in Alpine's online help:
2293 <ul>
2294 <li><a href="h_direct_config">Setup LDAP Directory Servers</a></li>
2295 </ul>
2296 <P>
2297 Additional help on using LDAP in Alpine is also available:
2298 <ul>
2299 <li><a href="h_ldap_view">LDAP Response View Explained</a></li>
2300 </ul>
2301 <P>
2302 <End of help on this topic>
2303 </BODY>
2304 </HTML>
2305 ===== h_mainhelp_index ======
2306 <HTML>
2307 <HEAD>
2308 <TITLE>Index of Messages</TITLE>
2309 </HEAD>
2310 <BODY>
2311 <H1>Index of Messages</H1>
2313 In Alpine's message index, the selected message is highlighted. The first
2314 column on the left is blank, shows a "+" if the message was
2315 sent directly to you (i.e., it is not a
2316 copy or from a list), or a "-" if you were explicitly Cc'd.
2317 <P>
2318 The second column may be blank, or it may contain:
2319 <ul>
2320 <li>"N" if the message is new (unread), </li>
2321 <li>"A" if you have answered the message (using the Reply command), </li>
2322 <li>"D" if you have marked the message for deletion.</li>
2323 </ul>
2325 <P>
2326 Note: If you answer a message as well as mark it deleted (in either order),
2327 you will only see the "D".
2329 <P>
2330 The rest of the columns in the message line show you the message
2331 number, date sent, sender, size, and subject. For details, press ? (Help).
2332 The behavior and appearance of the Index screen is highly configurable.
2333 In the Setup/Config screen search (with the WhereIs command) for options
2334 that contain the words "index" or "thread" to see
2335 many of the configuration possibilities.
2336 In particular, the
2337 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
2338 option may be used to configure the look of the standard MESSAGE INDEX lines
2339 in many different ways.
2340 Find <!--#echo var="VAR_index-format"--> in the Setup/Config screen and
2341 read the help text there for more information.
2342 <P>
2343 Most of the commands you need to handle your messages are visible at the
2344 bottom of the screen, and you can press O (OTHER CMDS) to see additional
2345 commands that are available.
2346 You do not need to see these "other commands"
2347 on the screen to use them. That is, you never need to press O as a prefix
2348 for any other command.
2350 <P>
2351 Additional information is available in Alpine's online help:
2352 <ul>
2353 <li><a href="h_mail_index">Message Index Commands</a></li>
2354 </ul>
2355 <P>
2356 <End of help on this topic>
2357 </BODY>
2358 </HTML>
2359 ===== h_mainhelp_reading ======
2360 <HTML>
2361 <HEAD>
2362 <TITLE>Reading Messages</TITLE>
2363 </HEAD>
2364 <BODY>
2365 <H1>Reading Messages</H1>
2367 The message text screen shows you the text of the message along with
2368 its header. If a message has attachments, those will be listed (but not
2369 displayed) also. The titlebar line displays information about the currently
2370 open message, folder and collection. You see the name of the collection
2371 (if there is one) in angle brackets, then the name of the folder, then the
2372 message number and finally the position within the current message (in
2373 percent). If the message is marked for deletion
2374 "DEL" will appear in the
2375 upper right as well.
2377 <P>
2378 As with every Alpine screen, the bottom two lines show you the commands
2379 available.
2381 <P>Additional information is available in Alpine's online help:
2382 <ul>
2383 <li><a href="h_mail_view">Message Text Screen</a></li>
2384 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a></li>
2385 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a></li>
2386 </ul>
2387 <P>
2388 <End of help on this topic>
2389 </BODY>
2390 </HTML>
2391 ===== h_mainhelp_composing ======
2392 <HTML>
2393 <HEAD>
2394 <TITLE>Composing Messages</TITLE>
2395 </HEAD>
2396 <BODY>
2397 <H1>Composing Messages</H1>
2399 To write a message, press C (Compose). You see the Compose Message
2400 screen, which is divided into two parts: the header area and the message
2401 text area. The header area is where information on the recipient (the To:
2402 field) and the subject line go, while the message text area contains the
2403 actual text of the email message. Different commands are available to you
2404 when your cursor is in different areas on this screen. To see additional
2405 help on commands in either the message text or header area, type
2406 <Control>G (Get help).
2408 <P>
2409 To move around, use the arrow keys or Ctrl-N (Next line) and Ctrl-P
2410 (Previous line); to correct typing errors, use <Backspace> or <Delete>.
2412 <P>The following information from Alpine's online help may prove useful:
2413 <ul>
2414 <li><a href="h_composer_to">Message Header Commands</a></li>
2415 <li><a href="h_compose_richhdr">Rich Header Command</a></li>
2416 <li><a href="h_composer">Composer Commands</a></li>
2417 <li><a href="h_edit_nav_cmds">Composer Editing Commands</a></li>
2418 <li><a href="h_config_change_your_from">Changing your From Address</a></li>
2419 <li><a href="h_compose_send">Send Command</a></li>
2420 <li><a href="h_compose_spell">Spell Check Command</a></li>
2421 </ul>
2422 <P>
2423 <End of help on this topic>
2424 </BODY>
2425 </HTML>
2426 ===== h_mainhelp_collections ======
2427 <HTML>
2428 <HEAD>
2429 <TITLE>Collection Lists</TITLE>
2430 </HEAD>
2431 <BODY>
2432 <H1>Collection Lists</H1>
2434 Collection lists are Alpine's way of organizing groups of folders. Each
2435 "collection" can reside on a different server, for example, and contain a
2436 different group of mail folders.
2438 <P>
2439 For more information on this, see:
2440 <ul>
2441 <li><a href="h_what_are_collections">Folder Collections Explained</a></li>
2442 </ul>
2443 <P>
2444 Additional information relating to collection lists is also available in
2445 Alpine's online
2446 help:
2447 <ul>
2448 <li><a href="h_collection_maint">Setup Collection List Screen</a></li>
2449 <li><a href="h_collection_screen">Collection List Screen</a></li>
2450 </ul>
2451 <P>
2452 <End of help on this topic>
2453 </BODY>
2454 </HTML>
2455 ===== h_mainhelp_folders ======
2456 <HTML>
2457 <HEAD>
2458 <TITLE>Folders</TITLE>
2459 </HEAD>
2460 <BODY>
2461 <H1>Folders</H1>
2463 Messages can quickly accumulate in your INBOX folder. If you use email
2464 often, you soon could have hundreds. You need to delete messages you do
2465 not want, and you can use folders to organize messages you wish to save. A
2466 folder is a collection of one or more messages that are stored (just like
2467 the messages in your INBOX) so you can access and manage them.
2469 <P>
2470 You can organize your email messages into different folders by topic,
2471 correspondent, date, or any other category that is meaningful to you. You
2472 can create your own folders, and Alpine automatically provides three:
2473 <ul>
2474 <li>The INBOX folder: messages sent to you are listed in this folder.
2475 When you first start Alpine and go to the Message Index screen, you are
2476 looking at the list of messages in your INBOX folder. Every incoming
2477 message remains in your INBOX until you delete it or save it in another
2478 folder. </li>
2479 <li>The sent-mail folder: copies of messages you send are stored in this
2480 folder. This is
2481 convenient if you cannot remember whether you actually sent a message and want
2482 to check, or
2483 if you want to send a message again.</li>
2484 <li>The saved-messages folder: copies of messages you save are stored in this
2485 folder
2486 unless you choose to save them to other folders you create yourself.</li>
2487 </ul>
2489 <P>
2490 More information about folders is available in Alpine's online help:
2491 <ul>
2492 <li><a href="h_folder_open">Explanation of Folder Selection</a></li>
2493 <li><a href="h_folder_maint">Help for Folder List</a></li>
2494 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a></li>
2495 <li><a href="h_folder_fcc">Folder Select for Fcc ("sent-mail")
2496 Explained</a></li>
2497 <li><a href="h_folder_save">Folder Select for Save Explained</a></li>
2498 </ul>
2499 <P>
2500 <End of help on this topic>
2501 </BODY>
2502 </HTML>
2503 ===== h_mainhelp_color ======
2504 <HTML>
2505 <HEAD>
2506 <TITLE>Color</TITLE>
2507 </HEAD>
2508 <BODY>
2509 <H1>Color</H1>
2511 If the terminal emulator you are using is capable of displaying color or if
2512 you are using PC-Alpine, then it is possible to set up Alpine so that various
2513 parts of the display will be shown in colors you configure. This is done
2514 using the Setup Color screen, available from the MAIN MENU by selecting
2515 the Setup command followed by "K" for Kolor (because "C"
2516 stands for Config in this context).
2518 <P>
2519 For example, you may color things like the titlebar, the current item,
2520 the keymenu, and the status messages.
2521 You may also color lines in the index, and headers and quoted text in the
2522 MESSAGE TEXT screen.
2523 You use the Color Setup screen for configuring most of this, but you must
2524 use the IndexColor setup for coloring whole index lines.
2525 These are available from the MAIN MENU under Setup/Kolor and Setup/Rules/IndexColor.
2527 <P>
2528 The following entries in Alpine's online help provide additional information
2529 about how to use color:
2530 <UL>
2531 <LI> <A HREF="h_color_setup">Color Setup screen</A>
2532 <LI> <A HREF="h_rules_incols">Index Line Color</A>
2533 <LI> <A HREF="h_config_quote_color">quoted text</A> in message view
2534 <LI> <A HREF="h_config_customhdr_pattern">text associated with user-defined headers</A> in message view
2535 </UL>
2536 <P>
2537 <End of help on this topic>
2538 </BODY>
2539 </HTML>
2540 ===== h_mainhelp_mouse ======
2541 <HTML>
2542 <HEAD>
2543 <TITLE>Using a Mouse</TITLE>
2544 </HEAD>
2545 <BODY>
2546 <H1>Using a Mouse</H1>
2548 If you are using PC-Alpine mouse support is turned on automatically.
2549 If you are using UNIX Alpine within an X terminal window or within
2550 a terminal emulator that supports an xterm-style mouse, then you may
2551 turn on support for the mouse with the feature
2552 <A HREF="h_config_enable_mouse"><!--#echo var="FEAT_enable-mouse-in-xterm"--></A>.
2553 For UNIX Alpine you will also need to set the $DISPLAY environment variable.
2554 <P>
2555 PC-Alpine offers considerable mouse support. You can view what is
2556 "clickable" by dragging your mouse over any screen; when the
2557 arrow cursor changes into a hand, you found something. Mouse-click
2558 possibilities include navigating between screens and folders and
2559 double-clicking on hyperlinks to open your Web browser.
2560 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
2561 screen. Examples of right-click options include "copy" after
2562 selecting text to copy and "View in New Window" when you click
2563 on a particular message in the Message Index. The menu choices available
2564 to you will vary based upon what screen is open, where on the screen your
2565 cursor is located, and even what action you have already taken.
2566 Within a folder, you may set the "Important" flag on any
2567 message.
2568 <P>
2569 X terminal mouse support is more limited but still quite powerful.
2570 As with PC-Alpine, clicking on any of the commands in the keymenu at
2571 the bottom of the screen will execute that command as if you typed it.
2572 Double-clicking on a link, for example the link to the
2573 <!--#echo var="FEAT_enable-mouse-in-xterm"--> feature in the paragraph above,
2574 will take you to that link.
2575 Double-clicking on an index line will view the message, and so on.
2576 <P>
2577 <End of help on this topic>
2578 </BODY>
2579 </HTML>
2580 ===== h_mainhelp_keywords ======
2581 <HTML>
2582 <HEAD>
2583 <TITLE>Keywords</TITLE>
2584 </HEAD>
2585 <BODY>
2586 <H1>Keywords</H1>
2588 Within a folder, you may set the "Important" flag on any
2589 message.
2590 This doesn't have any system-defined meaning and is only called
2591 the Important flag because many users use it to signify that a message
2592 is important to them in some way.
2593 <P>
2594 You may also define your own set of keywords.
2595 You might know these as user defined flags or as labels.
2596 These are similar to the Important flag but you choose the names for yourself.
2597 <P>
2598 Alpine will only display keywords that
2599 have been added by you in the Flag Details screen or
2600 that have been configured by you using the Setup/Config option
2601 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
2602 Keywords set by other means (for example, by another email client) will not
2603 show up in Alpine unless you configure Alpine to know about them.
2604 They will show up in the Flag Details screen, but will not show up, for example,
2605 in the index line.
2607 <P>
2608 The following entries in Alpine's online help provide additional information
2609 about how to use keywords:
2610 <ul>
2611 <li><A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--> config option</A></li>
2612 <li><A HREF="h_common_flag">Flag command to set keywords</A></li>
2613 </ul>
2614 <P>
2615 <End of help on this topic>
2616 </BODY>
2617 </HTML>
2618 ===== h_mainhelp_roles ======
2619 <HTML>
2620 <HEAD>
2621 <TITLE>Roles</TITLE>
2622 </HEAD>
2623 <BODY>
2624 <H1>Roles</H1>
2626 You may play different roles depending on who you are replying to. For
2627 example, if you are replying to a message addressed to help-desk you may
2628 be acting as a Help Desk Worker. That role may require that you use a
2629 different return address and/or a different signature.
2631 <P>
2632 To configure roles, go to the MAIN MENU and use the Setup command
2633 followed by "Rules" and then "Roles".
2634 The following entries in Alpine's online help provide additional information
2635 about how to
2636 use roles:
2637 <ul>
2638 <li><a href="h_rules_roles">Setup Roles Screen</a></li>
2639 <li><a href="h_role_select">Roles Screen</a></li>
2640 </ul>
2641 <P>
2642 <End of help on this topic>
2643 </BODY>
2644 </HTML>
2645 ===== h_mainhelp_filtering ======
2646 <HTML>
2647 <HEAD>
2648 <TITLE>Filtering</TITLE>
2649 </HEAD>
2650 <BODY>
2651 <H1>Filtering</H1>
2653 The software that actually delivers mail (the stuff that happens
2654 before Alpine is involved) for you is in a better position to do mail filtering
2655 than Alpine itself.
2656 If possible, you may want to look into using that sort of mail filtering to
2657 deliver mail to different folders, delete it, or forward it.
2658 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
2660 <P>
2661 Filtering is a way to automatically move certain messages from one folder
2662 to another or to automatically delete messages.
2663 You may also automatically set the state (Important, New, Deleted, Answered) of messages
2664 and set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
2665 Alpine doesn't have the ability to forward mail to another address or
2666 to deliver vacation messages.
2668 <P>
2669 To configure filtering, go to the MAIN MENU and use the Setup command
2670 followed by "Rules" and then "Filters".
2671 The following entries in Alpine's online help provide additional information
2672 about how to use filtering:
2673 <UL>
2674 <LI> <A HREF="h_rules_filter">Filtering Setup screen</A>
2675 </UL>
2676 <P>
2677 <End of help on this topic>
2678 </BODY>
2679 </HTML>
2680 ===== h_mainhelp_patterns ======
2681 <HTML>
2682 <HEAD>
2683 <TITLE>Patterns</TITLE>
2684 </HEAD>
2685 <BODY>
2686 <H1>Patterns</H1>
2688 Patterns are used with Roles, Filtering, Index Coloring,
2689 Scoring, Other Rules, and Search Rules, so it may help you to understand exactly how Patterns work.
2690 The following entries in Alpine's online help provide information
2691 about using Patterns:
2692 <UL>
2693 <LI> <A HREF="h_rule_patterns">Patterns</A>
2694 </UL>
2695 <P>
2696 <End of help on this topic>
2697 </BODY>
2698 </HTML>
2699 ===== h_mainhelp_cmdlineopts ======
2700 <HTML>
2701 <HEAD>
2702 <TITLE>Command Line Options</TITLE>
2703 </HEAD>
2704 <BODY>
2705 <H1>Command Line Options</H1>
2707 Alpine accepts a number of command line arguments, allowing you, for
2708 example, to start Alpine and immediately access a particular folder.
2709 Many of these arguments overlap with options in the Alpine configuration file.
2710 If there is a difference, then an option set on the command line takes
2711 precedence.
2712 Alpine expects command line arguments (other than addresses) to be
2713 preceded by a "-" (dash) as normally used by UNIX programs.
2714 A <a href="h_command_line_options">full list</a> of command line
2715 possibilities is available.
2716 <P>
2717 <End of help on this topic>
2718 </BODY>
2719 </HTML>
2720 ===== h_mainhelp_config ======
2721 <HTML>
2722 <HEAD>
2723 <TITLE>Alpine Configuration</TITLE>
2724 </HEAD>
2725 <BODY>
2726 <H1>Alpine Configuration</H1>
2728 Unless it has been administratively disabled, the Setup command on the
2729 MAIN MENU has several subcommands that allow you to modify Alpine's behavior.
2730 The possible subcommands are for general Configuration settings,
2731 Printer settings, Changing your Password, Signature setup,
2732 AddressBook setup, Collection Lists setup, Rules (including Roles, Filters,
2733 Scores, Search, Indexcolor, and Other rules), LDAP Directory setup,
2734 and Color configuration.
2735 In particular, the "Config" subcommand has many features you may
2736 set or unset and many other configuration variables that may be set to change
2737 the way Alpine works.
2738 Every one of the hundreds of options available in that configuration settings
2739 screen has help text associated with it.
2740 You may read that text by moving the cursor to highlight the option and then
2741 typing the Help command.
2742 <P>
2743 These settings are stored in your personal
2744 "pinerc" configuration file (or, optionally, they may be stored
2745 <A HREF="h_config_remote_config">remotely</A>),
2746 but on shared systems these settings
2747 may be over-ridden by a system-wide control file (due to local site
2748 security or support policies). A global pine configuration file can also
2749 be used to set default values for all Alpine users on a particular system.
2750 Power users may be interested in splitting their personal configuration
2751 data into two pieces, a generic piece and
2752 <A HREF="h_config_exceptions">exceptions</A> which apply to
2753 a particular platform.
2754 They may also be interested in <A HREF="h_config_inheritance">configuration inheritance</A>.
2755 General Alpine configuration information can be found
2756 <A HREF="h_news_config">here</A>.
2757 <P>
2758 <End of help on this topic>
2759 </BODY>
2760 </HTML>
2761 ===== h_mainhelp_aggops ======
2762 <HTML>
2763 <HEAD>
2764 <TITLE>Aggregate Operations</TITLE>
2765 </HEAD>
2766 <BODY>
2767 <H1>Aggregate Operations</H1>
2769 When you are in the MESSAGE INDEX, the available commands
2770 (for example, Delete, Undelete, Save, Reply, and so on)
2771 normally act on a single message.
2772 So, for example, if you press the Delete command, the currently highlighted
2773 message is marked Deleted.
2774 These commands that normally act on a single message may be applied to
2775 several messages at once instead.
2776 <P>
2777 By default this feature is turned on, but it could be administratively turned
2778 off to reduce complexity.
2779 The feature
2780 <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>
2781 in the Setup/Config screen is used to turn it off or on.
2782 When this feature is turned on, the four commands "Select",
2783 "SelectCur", "ZoomMode", and "Apply"
2784 are available.
2785 The two selection commands allow you to mark a set of
2786 messages as being "selected".
2787 The "ZoomMode" command will toggle between
2788 displaying only the selected messages and displaying all the messages.
2789 The "Apply" command allows you to
2790 apply one of the regular MESSAGE INDEX commands to all of the selected
2791 messages instead of to only the highlighted message.
2792 <P>
2793 An example aggregate operation would be to catch up when reading
2794 a news group.
2795 That is, get rid of all the messages in the news group so that you can
2796 start fresh.
2797 The easiest way to do this in Alpine is to use aggregate operations.
2798 You want to Delete all of the messages in the group.
2799 You could start at the top and type "D" once for every message.
2800 A much faster method is to first Select all of the messages in the group,
2801 and then Delete all of them.
2802 This would take four keystrokes:
2803 <P>
2804 <CENTER><SAMP>; a (to select all messages)</SAMP></CENTER>
2805 <BR>
2806 <CENTER><SAMP>a d (to delete all selected messages)</SAMP></CENTER>
2807 <P>
2808 Another use of Select is to use it for searching for a particular message
2809 or set of messages in a large folder.
2810 You may know that the message was From a certain user.
2811 You could select all messages from that user to start, and use Zoom to
2812 look at only those messages.
2813 If there were still too many messages to look at you could Narrow the
2814 set of messages further by selecting from all of those messages only
2815 the ones that were after a certain date, or contained a particular phrase
2816 in the Subject, or were too a particular address, and so on.
2817 That may be the end of what you are doing, or you may want to use Apply to
2818 Save or Forward or Print all of the selected messages.
2819 <P>
2820 Some related help topics are
2821 <UL>
2822 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
2823 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
2824 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
2825 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
2826 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
2827 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
2828 </UL>
2829 <P>
2830 <End of help on this topic>
2831 </BODY>
2832 </HTML>
2833 ===== h_mainhelp_readingnews ======
2834 <HTML>
2835 <HEAD>
2836 <TITLE>Reading News</TITLE>
2837 </HEAD>
2838 <BODY>
2839 <H1>Reading News</H1>
2841 <H2>Background</H2>
2842 Alpine can read and post to Internet (or USENET) newsgroups, using the same
2843 commands as for mail. Similar to mailing lists but existing on a larger scale,
2844 Usenet newsgroups allow groups of people with common interests to discuss
2845 particular topics. You might find newsgroups related to your career, or you
2846 might wish to check out the online discussion among the fans of your favorite
2847 television show.
2849 <H2>Configuring Alpine for Reading News</H2>
2850 Alpine often arrives
2851 pre-configured by your system administrator to automatically access the
2852 newsgroups offered by your organization, Internet Service Provider, or
2853 school. PC-Alpine users, and those attempting to customize Unix Alpine, will
2854 need additional details on <a href="h_configuring_news">how to
2855 configure Alpine to read news</a>.
2857 <H2>Accessing Newsgroups</H2>
2858 The first step in reading news is to access the newsgroups collections
2859 screen from Alpine. If everything is configured properly, you should be able
2860 to do this by first typing L (folder List), then selecting the folder
2861 collection listed as "News." The actual name of this collection may differ
2862 from system to system.
2864 <H2>Subscribing to Newsgroups</H2>
2866 Once you have accessed the news collection, you need to subscribe to a
2867 newsgroup that interests you. Subscribing to a newsgroup means that Alpine
2868 will keep a record of the newsgroups in which you are interested and which
2869 articles in those newsgroups have been read.
2871 <H2>Using Newsgroups</H2>
2872 Alpine uses the similar commands to read news as to read mail. For example,
2873 the D command marks messages as Deleted (or "Dismissed," if you prefer),
2874 and the R command Replies to a news posting. Basically, Alpine allows you to
2875 read news as if it were mail, so you don't need to change the way you
2876 interact with Alpine.
2877 <P>
2878 There is also additional Alpine help available on
2879 <A HREF="h_reading_news">how to use Alpine to read news</A>.
2880 <P>
2881 <End of help on this topic>
2882 </BODY>
2883 </HTML>
2884 ===== h_mainhelp_securing ======
2885 <HTML>
2886 <HEAD>
2887 <TITLE>Securing your Alpine Session</TITLE>
2888 </HEAD>
2889 <BODY>
2890 <H1>Securing your Alpine Session</H1>
2892 By default, Alpine will attempt to connect to an IMAP server on the normal
2893 IMAP service port (143).
2894 If the Alpine you are using has been built to
2895 support "Transport Layer Security" (TLS)
2896 and "Secure Sockets Layer" (SSL)
2897 (check by clicking <A HREF="X-Alpine-Config:">here</A>),
2898 and the server offers the STARTTLS capability, then a secure (encrypted)
2899 session will be established.
2900 <P>
2901 When you are connected to a remote folder the titlebar will contain a plus sign
2902 in the far right column if the connection is encrypted using TLS or SSL.
2903 Similarly, when you are being prompted for a password a plus sign will appear in the prompt
2904 if the connection is encrypted.
2906 <H2>More Information on Alpine with SSL and TLS</H2>
2907 <UL>
2908 <LI> <A HREF="h_release_tlscerts">TLS and SSL Usage Note</A> </LI>
2909 <LI> <A HREF="h_folder_server_syntax">/SSL</A> option for older servers which support port 993 SSL but not TLS </LI>
2910 <LI> <A HREF="h_config_alt_auth"><!--#echo var="FEAT_try-alternative-authentication-driver-first"--></A> feature </LI>
2911 <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>
2912 </UL>
2913 <H2>Here are some other security-related features and options</H2>
2914 <P>
2915 <UL>
2916 <LI> <A HREF="h_config_disable_password_caching"><!--#echo var="FEAT_disable-password-caching"--></A> feature to disable password caching </LI>
2917 <LI> <A HREF="h_config_disable_password_file_saving"><!--#echo var="FEAT_disable-password-file-saving"--></A> Disable password file saving</LI>
2918 <LI> <A HREF="h_config_mailcap_params"><!--#echo var="FEAT_enable-mailcap-param-substitution"--></A> feature </LI>
2919 <LI> <A HREF="h_config_disable_auths"><!--#echo var="VAR_disable-these-authenticators"--></A> option </LI>
2920 </UL>
2921 <P>
2922 <End of help on this topic>
2923 </BODY>
2924 </HTML>
2925 ===== h_mainhelp_problems ======
2926 <HTML>
2927 <HEAD>
2928 <TITLE>Reporting Problems</TITLE>
2929 </HEAD>
2930 <BODY>
2931 <H1>Reporting Problems</H1>
2933 We ask that you first read the relevant help screens and then seek
2934 assistance from your own local support staff. Once you are sure that your
2935 difficulty is not a local configuration problem, you might look at the
2936 help section explaining where to look for
2937 <A HREF="h_finding_help">more information</A> and where to
2938 get assistance.
2939 <P>
2941 <ADDRESS>
2942 Eduardo Chappa <chappa@gmx.com>
2943 </ADDRESS>
2945 <P>
2946 <End of help on this topic>
2947 </BODY>
2948 </HTML>
2949 ===== h_main_menu_commands ======
2950 <HTML>
2951 <HEAD>
2952 <TITLE>MAIN MENU COMMANDS</TITLE>
2953 </HEAD>
2954 <BODY>
2955 <H1>MAIN MENU COMMANDS</H1>
2957 <!--chtml if pinemode="function_key"-->
2958 Available Commands --
2959 Group 1 Available Commands -- Group 2<BR>
2960 ------------------------------
2961 --------------------
2962 ----------<BR>
2963 F1 Show this help text F1 Show this help text<BR>
2964 F2 Show all other available commands F2 Show other commands<BR>
2965 F3 Quit Alpine<BR>
2966 F4 Execute current MAIN MENU command F4 <A
2967 HREF="h_common_compose">Compose</A> a message<BR>
2968 F5 Select previous command up on menu F5 <A
2969 HREF="h_common_folders">FOLDER LIST</A> screen<BR>
2970 F6 Select next command down on menu F6 <A
2971 HREF="h_common_goto">Goto</A> a specified folder<BR>
2972
2973 F7 <A
2974 HREF="h_common_index">MESSAGE INDEX</A> screen<BR>
2975
2976 F8 <A
2977 HREF="h_main_journal">Journal</A> of status messages<BR>
2978 F9 Display <A
2979 HREF="h_main_release_notes">Release Notes</A> notes F9 <A
2980 HREF="h_main_setup">SETUP</A> menus<BR>
2981 F10 <A
2982 HREF="h_main_kblock">Lock Keyboard</A> F10 <A
2983 HREF="h_main_addrbook">ADDRESS BOOK</A> screen<BR>
2984
2985 F11 <A
2986 HREF="h_common_role">Compose message using a role</a><BR>
2987 <!--chtml else-->
2988 General Alpine Commands Main Menu Screen Commands<BR>
2989 --------------------- --------------------------<BR>
2990 ? Show Help Text O Show all Other available commands<BR>
2991 C <A
2992 HREF="h_common_compose">Compose</A> a message P Select Previous command up on menu<BR>
2993 I <A
2994 HREF="h_common_index">MESSAGE INDEX</A> screen N Select Next command down on menu<BR>
2995 L <A
2996 HREF="h_common_folders">FOLDER LIST</A> screen R Display Alpine <A HREF="h_main_release_notes">Release Notes</A><BR>
2997 A <A
2998 HREF="h_main_addrbook">ADDRESS BOOK</A> screen K <A
2999 HREF="h_main_kblock">Lock Keyboard</A><BR>
3000 S <A
3001 HREF="h_main_setup">SETUP</A> functions G <A
3002 HREF="h_common_goto">Goto</A> a specified folder<BR>
3003 Q Quit Alpine J <A HREF="h_main_journal">Journal</A> of status messages<BR>
3004 # <A
3005 HREF="h_common_role">Compose message using a role</a><BR>
3006 <!--chtml endif-->
3008 <P>
3009 NOTE:
3010 <OL>
3011 <LI>For help on a particular command, highlight the bold text associated
3012 with it above and hit Return.
3013 <LI> The availability of certain commands (e.g. some of the options under
3014 SETUP) is determined by Alpine configuration files and system capabilities.
3015 At some sites, certain commands may not be available due to security or
3016 support concerns.
3017 </OL>
3018 <P>
3019 <End of help on this topic>
3020 </BODY>
3021 </HTML>
3023 ===== h_command_line_options ======
3024 <HTML>
3025 <HEAD>
3026 <TITLE>COMMAND LINE OPTIONS</TITLE>
3027 </HEAD>
3028 <BODY>
3029 <H1>COMMAND LINE OPTIONS</H1>
3030 Possible starting arguments for Alpine:
3032 <DL COMPACT>
3034 <DT> <EM>[addresses]</EM>
3036 <DD> Send-to: If you give <EM>Alpine</EM> an argument or arguments which
3037 do not begin with a dash, <EM>Alpine</EM> treats them as email addresses.
3038 <EM>Alpine</EM> will startup in
3039 the composer with a message started to the addresses specified.
3040 Once the message is sent, the <EM>Alpine</EM> session closes.
3041 Standard input redirection is allowed.
3042 Separate multiple addresses with a space between them.
3043 Addresses are placed in the "To" field only.
3044 <P>
3046 <DT> < <EM>file</EM>
3048 <DD> <EM>Alpine</EM> will startup in the composer with <EM>file</EM> read
3049 into the body of the message.
3050 Once the message is sent, the <EM>Alpine</EM> session closes.
3051 <P>
3053 <DT> -attach <EM>file</EM>
3055 <DD> Go directly into composer with given file attached.
3056 <P>
3058 <DT> -attachlist <EM>file-list</EM>
3060 <DD> Go directly into composer with given files attached.
3061 This must be the last option on the command line.
3062 <P>
3064 <DT> -attach_and_delete <EM>file</EM>
3066 <DD> Go directly into composer with given file attached, delete when finished.
3067 <P>
3069 <DT> -aux <EM>local_directory</EM>
3071 <DD> <EM>PC-Alpine</EM> only.
3072 This tells <EM>PC-Alpine</EM> the local directory to use for storing auxiliary
3073 files, like debug files, address books, and signature files. The pinerc may
3074 be local or remote.
3075 <P>
3077 <DT> -bail
3079 <DD> If the personal configuration file doesn't already exist, exit.
3080 This might be useful if the configuration file is accessed using some
3081 remote filesystem protocol. If the remote mount is missing this will cause
3082 <EM>Alpine</EM> to quit instead of creating a new pinerc.
3083 <P>
3085 <DT> -c <EM>n</EM>
3087 <DD> When used with the <CODE>-f</CODE> option, apply the <EM>n</EM>th context.
3088 This is used when there are multiple folder collections (contexts) and you
3089 want to open a folder not in the primary collection.
3090 <P>
3092 <DT> -conf
3094 <DD> Configuration: Prints a sample system configuration file to the
3095 screen or standard output. To generate an initial system configuration
3096 file, execute
3098 <PRE><CODE>
3099 pine -conf > <!--#echo var="PINE_CONF_PATH"-->
3100 </CODE></PRE>
3101 <P>
3103 To generate a system configuration file using settings from an old
3104 system configuration file, execute
3106 <PRE><CODE>
3107 pine -P old-pine.conf -conf > <!--#echo var="PINE_CONF_PATH"-->
3108 </CODE></PRE>
3109 <P>
3110 A system configuration file is not required.
3111 <P>
3113 <DT> -copy_abook <<EM>local_abook_file</EM>> <<EM>remote_abook_folder</EM>>
3115 <DD> Copy an address book file to a remote address book folder.
3116 If the remote folder doesn't exist, it will be created.
3117 If it exists but the first message in the folder isn't a remote address
3118 book header message, the copy will be aborted.
3119 This flag will not usually be used by a user.
3120 Instead, the user will create a remote address book from within <EM>Alpine</EM>
3121 and copy entries from the local address book by using aggregate Save in
3122 the address book screen.
3123 <P>
3125 <DT> -copy_pinerc <<EM>local_pinerc_file</EM>> <<EM>remote_pinerc_folder</EM>>
3127 <DD> Copy a pinerc configuration file to a remote pinerc folder.
3128 If the remote folder doesn't exist, it will be created.
3129 If it exists but the first message in the folder isn't a remote pinerc
3130 header message, the copy will be aborted.
3131 This flag may be useful to users who already have a local pinerc file and
3132 would like to convert it to a remote pinerc folder and use that instead.
3133 This gives a way to bootstrap that conversion without having to manually
3134 reset all of the variables in the remote pinerc folder.
3135 <P>
3137 <DT> -d <EM>debug-level</EM>
3139 <DD> Debug Level: Sets the level of debugging information written by
3140 <EM>Alpine</EM>.
3141 <EM>debug-level</EM> can be set to any integer 0-9.
3142 A debug level of 0 turns off debugging for the session.
3143 (Actually there are some levels higher than 9, but you probably don't
3144 want to see them.)
3145 <P>
3147 <DT> -d <EM>keywords</EM>
3149 <DD> You may use a more detailed version of the debugging flag to set
3150 the debug level in separate parts of <EM>Alpine</EM>.
3151 The possibilities are flush, timestamp, imap=0..4, tcp, numfiles=0..31, and
3152 verbose=0..9.
3153 <EM>Flush</EM> causes debugging information to be flushed immediately to
3154 the debug file as it is written.
3155 <EM>Verbose</EM> is the general debugging verbosity level.
3156 <EM>Timestamp</EM> causes timestamps to be added to the debug file, which
3157 is useful when you are trying to figure out what is responsible for delays.
3158 <EM>Numfiles</EM> sets the number of debug files saved.
3159 <EM>Imap</EM> sets the debug level for the debugging statements related
3160 to the conversation with the IMAP server, and more generally, for the
3161 debugging related to <EM>Alpine</EM>'s interaction with the C-Client library.
3162 <EM>Tcp</EM> turns on some TCP/IP debugging.
3163 <P>
3165 <DT> -f <EM>folder</EM>
3167 <DD> Startup folder: <EM>Alpine</EM> will open this folder in place
3168 of the standard INBOX.
3169 <P>
3171 <DT> -F <EM>file</EM>
3173 <DD> Open named text file for viewing and forwarding.
3174 <P>
3176 <DT> -h
3178 <DD> Help: Prints the list of available command-line arguments to the
3179 screen.
3180 <P>
3182 <DT> -i
3184 <DD> <EM>Alpine</EM> will start up in the FOLDER INDEX
3185 screen instead of the MAIN MENU.
3186 <P>
3188 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"-->=i</EM>.
3189 <P>
3191 <DT> -I <EM>a,b,c,...</EM>
3193 <DD> Initial Keystrokes: <EM>Alpine</EM> will execute this comma-separated
3194 sequence of commands upon startup.
3195 This allows users to get <EM>Alpine</EM> to start in any
3196 of its menus/screens.
3197 You cannot include any input to the composer in the initial keystrokes.
3198 The key <Return> is represented by a ``CR'' in
3199 the keystroke list; the spacebar is designated by the letters ``SPACE''.
3200 Control keys are two character sequences beginning with ``^'', such as
3201 ``^I''.
3202 A tab character is ``TAB''.
3203 Function keys are ``F1'' - ``F12'' and the arrow keys are ``UP'',
3204 ``DOWN'', ``LEFT'', and ``RIGHT''.
3205 A restriction is that you can't mix function keys and character keys in this
3206 list even though you can, in some cases, mix them when running <EM>Alpine</EM>.
3207 A user can always use only <EM>character</EM> keys in the startup list even
3208 if he or she is using <EM>function</EM> keys normally, or vice versa.
3209 If an element in this list is a string of characters surrounded by double
3210 quotes (") then it will be expanded into the individual characters in
3211 the string, excluding the double quotes.
3212 <P>
3214 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"--></EM>
3215 <P>
3217 <DT> -install
3219 <DD> For <EM>PC-Alpine</EM> only, this option prompts the user for
3220 some basic information to help with getting properly set up.
3221 <P>
3223 <DT> -k
3225 <DD> Function-Key Mode: When invoked in this way, <EM>Alpine</EM> expects
3226 the input of commands to be function-keys.
3227 Otherwise, commands are linked to the regular character keys.
3228 <P>
3230 Configuration equivalent: <EM><!--#echo var="FEAT_use-function-keys"--></EM> included in
3231 <EM>Feature-List</EM>.
3232 <P>
3234 <DT> -n <EM>n</EM>
3236 <DD> Message-Number: When specified, <EM>Alpine</EM> starts up in the
3237 FOLDER INDEX screen with the current message being the specified
3238 message number.
3239 <P>
3241 <DT> -nosplash
3243 <DD> <EM>PC-Alpine</EM> only.
3244 This tells <EM>PC-Alpine</EM> not to display the splash screen upon startup.
3245 This may be helpful for certain troubleshooting or terminal server scenarios.
3246 <P>
3248 <DT> -o <EM>folder</EM>
3250 <DD> Opens the INBOX (or a folder specified via the -f argument) ReadOnly.
3251 <P>
3253 <DT> -p <EM>pinerc</EM>
3255 <DD> Uses the named file as the personal configuration file instead of
3256 <EM>~/.pinerc</EM> or the default PINERC search sequence <EM>PC-Alpine</EM> uses.
3257 Alpinerc may be either a local file or a remote configuration folder.
3258 <P>
3260 <DT> -P <EM>pinerc</EM>
3262 <DD> Uses the named file as the system wide configuration file instead of
3263 <EM><!--#echo var="PINE_CONF_PATH"--></EM> on UNIX, or nothing on <EM>PC-Alpine</EM>.
3264 Alpinerc may be either a local file or a remote configuration folder.
3265 <P>
3267 <DT> -passfile <EM>passfile</EM>
3269 <DD> This tells <EM>Alpine</EM> what file should be used as the password file.
3270 This should be a fully-qualified filename.
3271 <P>
3273 <DT> -pinerc <EM>file</EM>
3275 <DD> Output fresh pinerc configuration to <EM>file</EM>, preserving the
3276 settings of variables that the user has made.
3277 Use <EM>file</EM> set to ``-'' to make output go to standard out.
3278 <P>
3280 <DT> -r
3282 <DD> Restricted Mode: For UNIX <EM>Alpine</EM> only.
3283 <EM>Alpine</EM> in restricted mode can only send email to itself.
3284 Save and export are limited.
3285 <P>
3287 <DT> -registry <EM>cmd</EM>
3289 <DD> For <EM>PC-Alpine</EM> only, this option affects the values of
3290 <EM>Alpine</EM>'s registry entries.
3291 Possible values for <EM>cmd</EM> are set, clear, and dump.
3292 <EM>Set</EM> will always reset <EM>Alpine</EM>'s registry
3293 entries according to its current settings.
3294 <EM>Clear</EM> will clear the registry values.
3295 <EM>Clearsilent</EM> will clear the registry values without any dialogs.
3296 <EM>Dump</EM> will display the values of current registry settings.
3297 Note that the dump command is currently disabled.
3298 Without the -registry option, <EM>PC-Alpine</EM> will write values into
3299 the registry only if there currently aren't any values set.
3300 <P>
3302 <DT> -sort <EM>key</EM>
3304 <DD> Sort-Key: Specifies the order messages will be displayed in for the
3305 FOLDER INDEX screen.
3306 <EM>Key</EM> can have the following values:
3307 arrival, date, subject, orderedsubj, thread, from, size, score, to, cc,
3308 arrival/reverse, date/reverse, subject/reverse, orderedsubj/reverse, thread/reverse,
3309 from/reverse, size/reverse, score/reverse, to/reverse, and cc/reverse.
3310 The default value is "arrival".
3311 The <EM>key</EM> value reverse is equivalent to arrival/reverse.
3312 <P>
3314 Configuration equivalent: <EM><!--#echo var="VAR_sort-key"--></EM>.
3315 <P>
3317 <DT> -uninstall
3319 <DD> For <EM>PC-Alpine</EM> only, this option removes references to Alpine
3320 in Windows settings. The registry settings are removed and
3321 the password cache is cleared.
3322 <P>
3324 <DT> -url <EM>url</EM>
3326 <DD> Open the given URL.
3327 <P>
3329 <DT> -v
3331 <DD> Version: Print version information to the screen.
3332 <P>
3334 <DT> -x <EM>exceptions_config</EM>
3336 <DD> Configuration settings in the exceptions configuration override your normal
3337 default settings.
3338 <EM>Exceptions_config</EM> may be either a local file or a remote Alpine configuration folder.
3339 <P>
3341 <DT> -z
3343 <DD> Enable Suspend: When run with this flag, the key sequence ctrl-z
3344 will suspend the <EM>Alpine</EM> session.
3345 <P>
3347 Configuration equivalent: <EM><!--#echo var="FEAT_enable-suspend"--></EM> included in
3348 <EM>Feature-List</EM>.
3349 <P>
3351 <DT> -<EM>option</EM>=<EM>value</EM>
3353 <DD> Assign <EM>value</EM> to the config option <EM>option</EM>.
3354 For example, <EM>-signature-file=sig1</EM> or
3355 <EM>-Feature-List=signature-at-bottom</EM>.
3356 Note: Feature-List values are
3357 additive and features may be preceded with no- to turn them off.
3358 Also, as a special case, the "Feature-List=" part of that may be
3359 omitted. For example, <EM>-signature-at-bottom</EM> is equivalent to
3360 <EM>-Feature-List=signature-at-bottom</EM>.
3361 <P>
3363 </DL>
3364 <P>
3365 <End of help on this topic>
3366 </BODY>
3367 </HTML>
3368 ===== h_configuring_news ======
3369 <HTML>
3370 <HEAD>
3371 <TITLE>CONFIGURING NEWS</TITLE>
3372 </HEAD>
3373 <BODY>
3374 <H1>CONFIGURING NEWS</H1>
3375 Alpine can access news folders in any one of three different ways:
3376 <DL>
3377 <DT>REMOTE NNTP</DT>
3378 <DD>Using the Network News Transport Protocol (NNTP) to
3379 access news on a remote news server. In this case the newsrc file is
3380 stored on the machine where Alpine is running.
3382 <P>
3383 To specify a remote news-collection accessed via NNTP use the
3384 SETUP/collectionList screen's "Add" command. Set the
3385 Server: value to the NNTP server's hostname appended with the
3386 communication method "/service=NNTP", and set the Path:
3387 value to the "#news." namespace (without the quotes). See
3388 the "<A HREF="h_composer_cntxt_server">Server:</A>" field's
3389 help text for a more complete explanation of access method, and the
3390 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3391 text for a more complete explanation of "namespace".
3392 <P>
3393 Instead of specifying a news-collection, you may simply set the
3394 <A HREF="h_config_nntp_server">NNTP Server</A>
3395 option, which will cause Alpine to create a default news-collection for you.
3396 Another NNTP option that may be of interest is
3397 <A HREF="h_config_nntprange"><!--#echo var="VAR_nntp-range"--></A>.
3399 <DT>REMOTE IMAP</DT>
3400 <DD>Using the Internet Message Access Protocol (IMAP) to
3401 access news on a remote news server. In this case, your newsrc file is
3402 stored on the news server, in your home directory, so you must have an
3403 account on the news server, but you would be running Alpine on a different
3404 machine. The news server must be running an IMAPd server process.
3406 <P>
3407 To specify a remote news-collection accessed via IMAP use the
3408 SETUP/collectionList screen's "Add" command. Set the
3409 Server: value to the IMAP server's hostname, and set the Path: value
3410 to the "#news." namespace (without the quotes). See the
3411 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3412 text for a more complete explanation of "namespace".
3414 </DD>
3416 <DT>LOCAL</DT>
3417 <DD>Using local file access to the news database. In this
3418 case, your newsrc file is stored on the news server, in your home
3419 directory, so you must have an account on the news server, and you would
3420 be running Alpine on the same machine.
3422 <P>
3423 To specify a local news-collection use the SETUP/collectionList
3424 screen's "Add" command. Leave the Server: value blank, and
3425 set the Path: value to the "#news." namespace (without the
3426 quotes). See the "<A HREF="h_composer_cntxt_path">Path:</A>"
3427 field's help text for a more complete explanation of "namespace".
3429 </DD>
3430 </DL>
3432 <P>
3434 NOTE: Should no news-collection be defined as above, Alpine will
3435 automatically create one using the Setup/Config screen's
3436 "<!--#echo var="VAR_nntp-server"-->" variable's value if defined. The collection
3437 will be created as a "Remote NNTP" as described above.
3439 <P>
3441 If you are a PC-Alpine user, either option 1 (NNTP) or option 2 (IMAP) is
3442 possible. If you don't have an account on the news server, or if the news
3443 server is not running an IMAP daemon, then you must use NNTP. (If you are not
3444 sure, ask your service provider, university, or company for help.) In
3445 this case, your Unix .newsrc file can be transferred to your PC. A good
3446 place to put it would be in the same directory as your PINERC file, under
3447 the name NEWSRC, but you can
3448 <A HREF="h_config_newsrc_path">specify a different location</A>
3449 via Alpine's Setup/Config screen.
3451 <P>
3452 Other configuration features related to news are
3453 <A HREF="h_config_8bit_nntp"><!--#echo var="FEAT_enable-8bit-nntp-posting"--></A>.
3454 <A HREF="h_config_compose_news_wo_conf"><!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></A>,
3455 <A HREF="h_config_news_uses_recent"><!--#echo var="FEAT_news-approximates-new-status"--></A>,
3456 <A HREF="h_config_news_cross_deletes"><!--#echo var="FEAT_news-deletes-across-groups"--></A>,
3457 <A HREF="h_config_news_catchup"><!--#echo var="FEAT_news-offers-catchup-on-close"--></A>,
3458 <A HREF="h_config_post_wo_validation"><!--#echo var="FEAT_news-post-without-validation"--></A>,
3459 <A HREF="h_config_read_in_newsrc_order"><!--#echo var="FEAT_news-read-in-newsrc-order"--></A>, and
3460 <A HREF="h_config_quell_post_prompt"><!--#echo var="FEAT_quell-extra-post-prompt"--></A>.
3462 <P>
3463 <End of help on this topic>
3464 </BODY>
3465 </HTML>
3466 ===== h_reading_news ======
3467 <HTML>
3468 <HEAD>
3469 <TITLE>READING NEWS</TITLE>
3470 </HEAD>
3471 <BODY>
3472 <H1>READING NEWS</H1>
3474 Alpine uses almost the same commands for manipulating news folders as for
3475 mail folders. This means, for example, that when you are done with a
3476 message, you would use "D" to mark it as Deleted (or Dismissed,
3477 if you prefer.) This "mail-like" behavior differs from that of
3478 most newsreaders, wherein a message is implicitly dismissed after you have
3479 looked at it once. We strongly believe that Alpine should offer as much
3480 consistency as possible between mail and news, so the mail paradigm --
3481 wherein a message does not magically disappear without explicit action by
3482 the user -- is used for news as well. <P>
3484 If you answer a message in a news folder, the index view will show the
3485 "A" flag as usual; but the industry standard file Alpine uses to
3486 keep track of what news as been read has no way of storing this flag, so
3487 it will not be preserved across sessions. The Deleted flag is the only
3488 one that is preserved when you leave and then return to a newsgroup. As an
3489 additional note on replies, when you Reply to a newsgroup message and say
3490 you want to reply to all recipients, Alpine will ask if you want to post the
3491 message to all the newsgroups listed in the original message. <P>
3493 If you would like Alpine to mark more-or-less recent news messages as
3494 "New", then set the
3495 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
3496 feature (which is set by default). This will cause messages after the last one you have marked as
3497 Deleted to appear with "N" status in the MESSAGE INDEX. The
3498 "N" status often makes it easier to distinguish later news
3499 articles from those you've previously seen, but not yet disposed of via
3500 the "D" key. Note that this is an approximation, not an exact
3501 record of which messages you have not seen.
3502 <P>
3504 A frequent operation in news-reading is "catching up" -- that
3505 is, getting rid of all the messages in the newsgroup so that you can
3506 "start fresh." The easiest way to do this in Alpine is via the
3507 Select command. You would enter the following four keystrokes:
3508 <tt>;aad</tt> to select all messaged, and then apply the delete (or
3509 dismiss) command to all of them.
3511 <P>
3512 There are also additional details on
3513 <A HREF="h_configuring_news">configuring news</a>.
3515 <P>
3516 <End of help on this topic>
3517 </BODY>
3518 </HTML>
3519 ====== h_help_index ======
3520 <HTML>
3521 <HEAD>
3522 <TITLE>Help Index</TITLE>
3523 </HEAD>
3524 <BODY>
3525 <H1>Help Index</H1>
3526 <ul>
3527 <li><a href="h_mainhelp_abooks">Address Books</a></li>
3528 <li><a href="h_abook_top">ADDRESS BOOK LIST COMMANDS</a>
3529 <li><a href="h_main_addrbook">Address Book Command</a>
3530 <li><a href="h_abook_view">Address Book View Explained</a>
3531 <li><a href="h_compose_addrcomplete">Address Completion</a>
3532 <li><a href="h_abook_select_listmode">Address Listmode Selection from Composer Explained</a>
3533 <li><a href="h_abook_select_checks">Address Selection from Composer Explained</a>
3534 <li><a href="h_composer_abook_comment">Addressbook Comment Explained</a>
3535 <li><a href="h_composer_abook_fcc">Addressbook Fcc Explained</a>
3536 <li><a href="h_composer_abook_add_folder">Addressbook Folder Name Field Explained</a>
3537 <li><a href="h_composer_abook_full">Addressbook Fullname Explained</a>
3538 <li><a href="h_composer_abook_add_nick">Addressbook NickName Field Explained</a>
3539 <li><a href="h_composer_abook_nick">Addressbook Nickname Explained</a>
3540 <li><a href="h_abook_select_addr">Addressbook Selection Explained</a>
3541 <li><a href="h_abook_select_top">Addressbook Selection Navigation Explained</a>
3542 <li><a href="h_composer_abook_add_server">Addressbook Server Name Field Explained</a>
3543 <li><a href="h_mainhelp_aggops">Aggregate Operations</a>
3544 <li><a href="h_mainhelp_config">Alpine Configuration</a>
3545 <li><a href="h_mainhelp_pinehelp">Alpine Help</a>
3546 <li><a href="h_news_legal">Alpine Legal Notices</a>
3547 <li><a href="h_compose_alted">Alt Editor Command</a>
3548 <li><a href="h_index_cmd_apply">Apply Command</a>
3549 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a>
3550 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a>
3551 <li><a href="h_mainhelp_filtering">Blocking Messages</a>
3552 <li><a href="h_composer_browse">BROWSER</a>
3553 <li><a href="h_common_bounce">Bounce Command</a>
3554 <li><a href="h_compose_cancel">Cancel Command</a>
3555 <li><a href="h_config_change_your_from">Changing your From Address</a>
3556 <li><a href="h_collection_screen">COLLECTION LIST screen</a>
3557 <li><a href="h_mainhelp_color">Color</a>
3558 <li><a href="h_composer_ctrl_j">COMPOSER ATTACH</a>
3559 <li><a href="h_composer">COMPOSER COMMANDS</a>
3560 <li><a href="h_mainhelp_composing">Composing Messages</a>
3561 <li><a href="h_mainhelp_collections">Collection Lists</a>
3562 <li><a href="h_composer_cntxt_nick">Collection Nickname Explained</a>
3563 <li><a href="h_composer_cntxt_path">Collection Path: Explained</a>
3564 <li><a href="h_composer_cntxt_server">Collection Server: Explained</a>
3565 <li><a href="h_composer_cntxt_view">Collection View: Explained</a>
3566 <li><a href="h_mainhelp_cmdlineopts">Command Line Options</a>
3567 <li><a href="h_common_compose">Compose Command</a>
3568 <li><a href="h_edit_nav_cmds">Composer Editing Commands Explained</a>
3569 <li><a href="h_common_conditional_cmds">Conditional Commands</a>
3570 <li><a href="h_reply_token_conditionals">Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</a>
3571 <li><a href="h_mainhelp_config">Configuration</a>
3572 <li><a href="h_composer_custom_free">CUSTOMIZED HEADER FIELD</a>
3573 <li><a href="h_config_dflt_color">Default Color</a>
3574 <li><a href="h_common_delete">Delete and Undelete Commands</a>
3575 <li><a href="h_composer_qserv_cn">Directory Query Form Explained</a>
3576 <li><a href="h_special_list_commands">Email List Commands Explained</a>
3577 <li><a href="h_composer_search">Explanation of Composer Whereis Command </a>
3578 <li><a href="h_folder_open">Explanation of Folder Selection</a>
3579 <li><a href="h_special_xon_xoff">Explanation of Alpine's XOFF/XON Handling</a>
3580 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a>
3581 <li><a href="h_ge_export">Export File Selection</a>
3582 <li><a href="h_ge_allparts">Export Message File Selection</a>
3583 <li><a href="h_index_cmd_expunge">Expunge/Exclude Command</a>
3584 <li><a href="h_info_on_locking">FAQs on Alpine Locking</a>
3585 <li><a href="h_config_allow_chg_from">FEATURE: <!--#echo var="FEAT_allow-changing-from"--></a>
3586 <li><a href="h_config_allow_talk">FEATURE: <!--#echo var="FEAT_allow-talk"--></a>
3587 <li><a href="h_config_alt_compose_menu">FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></a>
3588 <li><a href="h_config_alt_role_menu">FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></a>
3589 <li><a href="h_config_force_low_speed">FEATURE: <!--#echo var="FEAT_assume-slow-link"--></a>
3590 <li><a href="h_config_auto_read_msgs">FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></a>
3591 <li><a href="h_config_auto_open_unread">FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></a>
3592 <li><a href="h_config_auto_unselect">FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></a>
3593 <li><a href="h_config_auto_unzoom">FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></a>
3594 <li><a href="h_config_auto_zoom">FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></a>
3595 <li><a href="h_config_use_boring_spinner">FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></a>
3596 <li><a href="h_config_check_mail_onquit">FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></a>
3597 <li><a href="h_config_combined_abook_display">FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></a>
3598 <li><a href="h_config_combined_folder_display">FEATURE: <!--#echo var="FEAT_combined-folder-display"--></a>
3599 <li><a href="h_config_combined_subdir_display">FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></a>
3600 <li><a href="h_config_cancel_confirm">FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></a>
3601 <li><a href="h_config_lame_list_mode">FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></a>
3602 <li><a href="h_config_compose_rejects_unqual">FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></a>
3603 <li><a href="h_config_send_filter_dflt">FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></a>
3604 <li><a href="h_config_compose_news_wo_conf">FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></a>
3605 <li><a href="h_config_del_from_dot">FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></a>
3606 <li><a href="h_config_compose_maps_del">FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></a>
3607 <li><a href="h_config_confirm_role">FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></a>
3608 <li><a href="h_config_tab_no_prompt">FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></a>
3609 <li><a href="h_config_dates_to_local">FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></a>
3610 <li><a href="h_config_copy_to_to_from">FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></a>
3611 <li><a href="h_config_del_skips_del">FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></a>
3612 <li><a href="h_config_disable_config_cmd">FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></a>
3613 <li><a href="h_config_disable_index_locale_dates">FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></a>
3614 <li><a href="h_config_disable_kb_lock">FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></a>
3615 <li><a href="h_config_blank_keymenu">FEATURE: <!--#echo var="FEAT_disable-keymenu"--></a>
3616 <li><a href="h_config_disable_password_caching">FEATURE: <!--#echo var="FEAT_disable-password-caching"--></a>
3617 <li><a href="h_config_disable_password_cmd">FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></a>
3618 <li><a href="h_config_disable_pipes_in_sigs">FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></a>
3619 <li><a href="h_config_disable_pipes_in_templates">FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></a>
3620 <li><a href="h_config_disable_regex">FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
3621 <li><a href="h_config_disable_roles_setup">FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></a>
3622 <li><a href="h_config_disable_roles_sigedit">FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></a>
3623 <li><a href="h_config_disable_roles_templateedit">FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></a>
3624 <li><a href="h_config_input_history">FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></a>
3625 <li><a href="h_config_disable_collate">FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></a>
3626 <li><a href="h_config_disable_shared">FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></a>
3627 <li><a href="h_config_disable_signature_edit">FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></a>
3628 <li><a href="h_config_take_fullname">FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></a>
3629 <li><a href="h_config_take_lastfirst">FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></a>
3630 <li><a href="h_config_disable_reset_disp">FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></a>
3631 <li><a href="h_config_disable_sender">FEATURE: <!--#echo var="FEAT_disable-sender"--></a>
3632 <li><a href="h_config_quell_dead_letter">FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></a>
3633 <li><a href="h_config_quell_flowed_text">FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></a>
3634 <li><a href="h_downgrade_multipart_to_text">FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></a>
3635 <li><a href="h_config_8bit_smtp">FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></a>
3636 <li><a href="h_config_8bit_nntp">FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></a>
3637 <li><a href="h_config_enable_agg_ops">FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></a>
3638 <li><a href="h_config_enable_alt_ed">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></a>
3639 <li><a href="h_config_alt_ed_now">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></a>
3640 <li><a href="h_config_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></a>
3641 <li><a href="h_config_relaxed_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></a>
3642 <li><a href="h_config_compose_bg_post">FEATURE: <!--#echo var="FEAT_enable-background-sending"--></a>
3643 <li><a href="h_config_enable_bounce">FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></a>
3644 <li><a href="h_config_cruise_mode">FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></a>
3645 <li><a href="h_config_cruise_mode_delete">FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></a>
3646 <li><a href="h_config_compose_dsn">FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></a>
3647 <li><a href="h_config_enable_dot_files">FEATURE: <!--#echo var="FEAT_enable-dot-files"--></a>
3648 <li><a href="h_config_enable_lessthan_exit">FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></a>
3649 <li><a href="h_config_fast_recent">FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></a>
3650 <li><a href="h_config_enable_flag">FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></a>
3651 <li><a href="h_config_flag_screen_default">FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></a>
3652 <li><a href="h_config_flag_screen_kw_shortcut">FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></a>
3653 <li><a href="h_config_enable_full_hdr_and_text">FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></a>
3654 <li><a href="h_config_enable_full_hdr">FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></a>
3655 <li><a href="h_config_allow_goto">FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></a>
3656 <li><a href="h_config_enable_dot_folders">FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></a>
3657 <li><a href="h_config_enable_incoming">FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></a>
3658 <li><a href="h_config_enable_incoming_checking">FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></a>
3659 <li><a href="h_config_enable_jump">FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></a>
3660 <li><a href="h_config_show_delay_cue">FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></a>
3661 <li><a href="h_config_mailcap_params">FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></a>
3662 <li><a href="h_config_enable_mouse">FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></a>
3663 <li><a href="h_config_enable_view_addresses">FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></a>
3664 <li><a href="h_config_enable_view_attach">FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></a>
3665 <li><a href="h_config_enable_view_arrows">FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></a>
3666 <li><a href="h_config_enable_view_url">FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></a>
3667 <li><a href="h_config_enable_view_web_host">FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></a>
3668 <li><a href="h_config_enable_mulnewsrcs">FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></a>
3669 <li><a href="h_config_enable_xterm_newmail">FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></a>
3670 <li><a href="h_config_enable_newmail_short_text">FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>
3671 <li><a href="h_config_sub_lists">FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></a>
3672 <li><a href="h_config_enable_y_print">FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></a>
3673 <li><a href="h_config_prefix_editing">FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></a>
3674 <li><a href="h_config_enable_search_and_repl">FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></a>
3675 <li><a href="h_config_sigdashes">FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></a>
3676 <li><a href="h_config_new_thread_blank_subject">FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></a>
3677 <li><a href="h_config_can_suspend">FEATURE: <!--#echo var="FEAT_enable-suspend"--></a>
3678 <li><a href="h_config_enable_tab_complete">FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></a>
3679 <li><a href="h_config_enable_take_export">FEATURE: <!--#echo var="FEAT_enable-take-export"--></a>
3680 <li><a href="h_config_enable_role_take">FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></a>
3681 <li><a href="h_config_tray_icon">FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></a>
3682 <li><a href="h_config_enable_pipe">FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></a>
3683 <li><a href="h_config_verbose_post">FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></a>
3684 <li><a href="h_config_expanded_addrbooks">FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></a>
3685 <li><a href="h_config_expanded_distlists">FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></a>
3686 <li><a href="h_config_expanded_folders">FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></a>
3687 <li><a href="h_config_expose_hidden_config">FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></a>
3688 <li><a href="h_config_expunge_manually">FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></a>
3689 <li><a href="h_config_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></a>
3690 <li><a href="h_config_full_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></a>
3691 <li><a href="h_config_no_fcc_attach">FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></a>
3692 <li><a href="h_config_force_arrow">FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></a>
3693 <li><a href="h_config_forward_as_attachment">FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></a>
3694 <li><a href="h_config_preserve_field">FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></a>
3695 <li><a href="h_config_quell_empty_dirs">FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></a>
3696 <li><a href="h_config_hide_nntp_path">FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></a>
3697 <li><a href="h_config_attach_in_reply">FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></a>
3698 <li><a href="h_config_fcc_on_bounce">FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></a>
3699 <li><a href="h_config_include_header">FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></a>
3700 <li><a href="h_config_auto_include_reply">FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></a>
3701 <li><a href="h_config_incoming_checking_total">FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></a>
3702 <li><a href="h_config_incoming_checking_recent">FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></a>
3703 <li><a href="h_config_add_ldap">FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></a>
3704 <li><a href="h_config_maildrops_preserve_state">FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></a>
3705 <li><a href="h_config_mark_fcc_seen">FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></a>
3706 <li><a href="h_config_mark_for_cc">FEATURE: <!--#echo var="FEAT_mark-for-cc"--></a>
3707 <li><a href="h_config_mulnews_as_typed">FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></a>
3708 <li><a href="h_config_news_uses_recent">FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></a>
3709 <li><a href="h_config_news_cross_deletes">FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></a>
3710 <li><a href="h_config_news_catchup">FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></a>
3711 <li><a href="h_config_post_wo_validation">FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></a>
3712 <li><a href="h_config_read_in_newsrc_order">FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></a>
3713 <li><a href="h_config_nntp_search_uses_overview">FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></a>
3714 <li><a href="h_config_thread_sorts_by_arrival">FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></a>
3715 <li><a href="h_config_expunge_inbox">FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></a>
3716 <li><a href="h_config_expunge_stayopens">FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></a>
3717 <li><a href="h_config_pass_c1_control">FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></a>
3718 <li><a href="h_config_pass_control">FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></a>
3719 <li><a href="h_config_predict_nntp_server">FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></a>
3720 <li><a href="h_config_prefer_plain_text">FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></a>
3721 <li><a href="h_config_preopen_stayopens">FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></a>
3722 <li><a href="h_config_preserve_start_stop">FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></a>
3723 <li><a href="h_config_quell_folder_internal_msg">FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></a>
3724 <li><a href="h_config_quell_checks_comp">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></a>
3725 <li><a href="h_config_quell_checks_comp_inbox">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></a>
3726 <li><a href="h_config_quell_partial">FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></a>
3727 <li><a href="h_config_quell_local_lookup">FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></a>
3728 <li><a href="h_config_ff_between_msgs">FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></a>
3729 <li><a href="h_config_print_from">FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></a>
3730 <li><a href="h_config_print_index">FEATURE: <!--#echo var="FEAT_print-index-enabled"--></a>
3731 <li><a href="h_config_custom_print">FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></a>
3732 <li><a href="h_config_prune_uses_iso">FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></a>
3733 <li><a href="h_config_quell_personal_name_prompt">FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></a>
3734 <li><a href="h_config_quell_ssl_largeblocks">FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></a>
3735 <li><a href="h_config_quell_user_id_prompt">FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></a>
3736 <li><a href="h_config_quit_wo_confirm">FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></a>
3737 <li><a href="h_config_quote_replace_noflow">FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></a>
3738 <li><a href="h_config_next_thrd_wo_confirm">FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></a>
3739 <li><a href="h_config_auto_reply_to">FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></a>
3740 <li><a href="h_config_inbox_no_confirm">FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></a>
3741 <li><a href="h_config_save_aggregates">FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></a>
3742 <li><a href="h_config_save_part_wo_confirm">FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></a>
3743 <li><a href="h_config_save_advances">FEATURE: <!--#echo var="FEAT_save-will-advance"--></a>
3744 <li><a href="h_config_save_wont_delete">FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></a>
3745 <li><a href="h_config_quote_all_froms">FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></a>
3746 <li><a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
3747 <li><a href="h_config_select_wo_confirm">FEATURE: <!--#echo var="FEAT_select-without-confirm"--></a>
3748 <li><a href="h_config_auto_fcc_only">FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></a>
3749 <li><a href="h_config_send_wo_confirm">FEATURE: <!--#echo var="FEAT_send-without-confirm"--></a>
3750 <li><a href="h_config_separate_fold_dir_view">FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></a>
3751 <li><a href="h_config_show_cursor">FEATURE: <!--#echo var="FEAT_show-cursor"--></a>
3752 <li><a href="h_config_textplain_int">FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></a>
3753 <li><a href="h_config_select_in_bold">FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></a>
3754 <li><a href="h_config_show_sort">FEATURE: <!--#echo var="FEAT_show-sort"--></a>
3755 <li><a href="h_config_single_list">FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></a>
3756 <li><a href="h_config_sig_at_bottom">FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></a>
3757 <li><a href="h_config_slash_coll_entire">FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></a>
3758 <li><a href="h_config_sort_fcc_alpha">FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></a>
3759 <li><a href="h_config_sort_save_alpha">FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></a>
3760 <li><a href="h_config_always_spell_check">FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></a>
3761 <li><a href="h_config_winpos_in_config">FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></a>
3762 <li><a href="h_config_strip_sigdashes">FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>
3763 <li><a href="h_config_strip_ws_before_send">FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></a>
3764 <li><a href="h_config_quells_asterisks">FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></a>
3765 <li><a href="h_config_quell_attach_ext_warn">FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></a>
3766 <li><a href="h_config_quell_attach_extra_prompt">FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></a>
3767 <li><a href="h_config_no_bezerk_zone">FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></a>
3768 <li><a href="h_config_quell_charset_warning">FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></a>
3769 <li><a href="h_config_quell_content_id">FEATURE: <!--#echo var="FEAT_quell-content-id"--></a>
3770 <li><a href="h_config_quell_post_prompt">FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></a>
3771 <li><a href="h_config_quell_filtering_done_message">FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></a>
3772 <li><a href="h_config_quell_filtering_messages">FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></a>
3773 <li><a href="h_config_quell_full_hdr_reset">FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></a>
3774 <li><a href="h_config_quell_imap_env">FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></a>
3775 <li><a href="h_config_quell_lock_failure_warnings">FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></a>
3776 <li><a href="h_config_quell_domain_warn">FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></a>
3777 <li><a href="h_config_quell_news_env">FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></a>
3778 <li><a href="h_config_quell_host_after_url">FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></a>
3779 <li><a href="h_config_quell_beeps">FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></a>
3780 <li><a href="h_config_quell_tz_comment">FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></a>
3781 <li><a href="h_config_suppress_user_agent">FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></a>
3782 <li><a href="h_config_tab_checks_recent">FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></a>
3783 <li><a href="h_config_tab_uses_unseen">FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></a>
3784 <li><a href="h_config_tab_new_only">FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></a>
3785 <li><a href="h_config_termcap_wins">FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></a>
3786 <li><a href="h_config_color_thrd_import">FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></a>
3787 <li><a href="h_config_alt_auth">FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></a>
3788 <li><a href="h_config_unsel_wont_advance">FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></a>
3789 <li><a href="h_config_use_current_dir">FEATURE: <!--#echo var="FEAT_use-current-dir"--></a>
3790 <li><a href="h_config_use_fk">FEATURE: <!--#echo var="FEAT_use-function-keys"--></a>
3791 <li><a href="h_config_use_reg_start_for_stayopen">FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></a>
3792 <li><a href="h_config_use_resentto">FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></a>
3793 <li><a href="h_config_use_sender_not_x">FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></a>
3794 <li><a href="h_config_suspend_spawns">FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></a>
3795 <li><a href="h_config_use_system_translation">FEATURE: Use System Translation</a>
3796 <li><a href="h_config_vertical_list">FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></a>
3797 <li><a href="h_config_warn_if_fcc_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></a>
3798 <li><a href="h_config_warn_if_subj_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></a>
3799 <li><a href="h_config_warn_if_no_to_or_cc">FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></a>
3800 <li><a href="h_mainhelp_filtering">Filtering</a>
3801 <li><a href="h_finding_help">Finding more information and requesting help</a>
3802 <li><a href="h_common_flag">Flag Command</a>
3803 <li><a href="h_config_quell_flowed_text">Flowed Text</a>
3804 <li><a href="h_mainhelp_folders">Folders</a>
3805 <li><a href="h_what_are_collections">Folder Collections Explained</a>
3806 <li><a href="h_common_folders">Folder List Command</a>
3807 <li><a href="h_folder_fcc">Folder Select for Fcc Explained</a>
3808 <li><a href="h_folder_save">Folder Select for Save Explained</a>
3809 <li><a href="h_folder_server_syntax">Folder Server Name Syntax</a>
3810 <li><a href="h_config_change_your_from">From Address, Changing</a>
3811 <li><a href="main_menu_tx">GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</a>
3812 <li><a href="h_pine_for_windows">GETTING HELP IN ALPINE</a>
3813 <li><a href="h_common_goto">Goto Command</a>
3814 <li><a href="h_common_hdrmode">HdrMode Command</a>
3815 <li><a href="h_mainhelp_pinehelp">Help</a>
3816 <li><a href="h_special_help_nav">Help Text Navigation Explained</a>
3817 <li><a href="h_folder_maint">Help for Folder List</a>
3818 <li><a href="h_valid_folder_names">IMAP</a>
3819 <li><a href="h_ge_import">Import File Selection</a>
3820 <li><a href="h_mainhelp_index">Index of Messages</a>
3821 <li><a href="h_composer_ins_m">INSERT MESSAGE</a>
3822 <li><a href="h_composer_ins">INSERT TEXT FILE</a>
3823 <li><a href="h_address_format">INTERNET EMAIL ADDRESS FORMAT</a>
3824 <li><a href="h_info_on_mbox">Information on mbox driver</a>
3825 <li><a href="h_mainhelp_intro">Introduction</a>
3826 <li><a href="h_main_journal">Journal Command</a>
3827 <li><a href="h_common_jump">Jump Command</a>
3828 <li><a href="h_compose_justify">Justify Command</a>
3829 <li><a href="h_main_kblock">Keyboard Lock Command</a>
3830 <li><a href="h_mainhelp_keywords">Keywords (or Flags, or Labels)</a>
3831 <li><a href="h_mainhelp_ldap">LDAP</a>
3832 <li><a href="h_config_ldap_opts_tls">LDAP FEATURE: Attempt-TLS-On-Connection</a>
3833 <li><a href="h_config_ldap_opts_nosub">LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</a>
3834 <li><a href="h_config_ldap_opts_rhs">LDAP FEATURE: Lookup-Addrbook-Contents</a>
3835 <li><a href="h_config_ldap_opts_tlsmust">LDAP FEATURE: Require-TLS-On-Connection</a>
3836 <li><a href="h_config_ldap_opts_ref">LDAP FEATURE: Save-Search-Criteria-Not-Result</a>
3837 <li><a href="h_config_ldap_opts_impl">LDAP FEATURE: Use-Implicitly-From-Composer</a>
3838 <li><a href="h_config_ldap_binddn">LDAP OPTION: Bind-DN</a>
3839 <li><a href="h_config_ldap_cust">LDAP OPTION: Custom-Search-Filter</a>
3840 <li><a href="h_config_ldap_email_attr">LDAP OPTION: EmailAttribute</a>
3841 <li><a href="h_config_ldap_gn_attr">LDAP OPTION: GivennameAttribute</a>
3842 <li><a href="h_config_ldap_server">LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></a>
3843 <li><a href="h_config_ldap_cn_attr">LDAP OPTION: NameAttribute</a>
3844 <li><a href="h_config_ldap_nick">LDAP OPTION: Nickname</a>
3845 <li><a href="h_config_ldap_port">LDAP OPTION: Port</a>
3846 <li><a href="h_config_ldap_base">LDAP OPTION: Search-Base</a>
3847 <li><a href="h_config_ldap_searchrules">LDAP OPTION: Search-Rule</a>
3848 <li><a href="h_config_ldap_searchtypes">LDAP OPTION: Search-Type</a>
3849 <li><a href="h_config_ldap_size">LDAP OPTION: Sizelimit</a>
3850 <li><a href="h_config_ldap_sn_attr">LDAP OPTION: SurnameAttribute</a>
3851 <li><a href="h_config_ldap_time">LDAP OPTION: Timelimit</a>
3852 <li><a href="h_ldap_view">LDAP Response View Explained</a>
3853 <li><a href="h_maildrop">Mail Drop: What is it?</a>
3854 <li><a href="h_mainhelp_mainmenu">MAIN MENU</a>
3855 <li><a href="h_mail_index">MESSAGE INDEX COMMANDS</a>
3856 <li><a href="h_mail_view">MESSAGE TEXT SCREEN</a>
3857 <li><a href="h_compose_markcutpaste">Mark, Cut and Paste Commands</a>
3858 <li><a href="h_common_index">Message Index Command</a>
3859 <li><a href="h_mainhelp_mouse">Mouse</a>
3860 <li><a href="h_mainhelp_aggops">Multiple Message Operations</a>
3861 <li><a href="new_user_greeting">NEW USER GREETING</a>
3862 <li><a href="new_version_greeting">NEW VERSION GREETING</a>
3863 <li><a href="h_mainhelp_readingnews">News Reading</a>
3864 <li><a href="h_folder_subscribe">Newsgroup Subcribe Screen explained</a>
3865 <li><a href="h_folder_postnews">Newsgroup selecting for Posting explained</a>
3866 <li><a href="h_common_nextnew">NextNew Command</a>
3867 <li><a href="h_abook_select_nick">Nickname Selection Explained</a>
3868 <li><a href="h_mainhelp_readingnews">NNTP</a>
3869 <li><a href="h_config_address_book">OPTION: <!--#echo var="VAR_address-book"--></a>
3870 <li><a href="h_config_abook_formats">OPTION: <!--#echo var="VAR_addressbook-formats"--></a>
3871 <li><a href="h_config_ab_sort_rule">OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></a>
3872 <li><a href="h_config_alt_addresses">OPTION: <!--#echo var="VAR_alt-addresses"--></a>
3873 <li><a href="h_config_active_msg_interval">OPTION: <!--#echo var="VAR_busy-cue-rate"--></a>
3874 <li><a href="h_config_color_style">OPTION: Color Style</a>
3875 <li><a href="h_config_wordseps">OPTION: <!--#echo var="VAR_composer-word-separators"--></a>
3876 <li><a href="h_config_composer_wrap_column">OPTION: <!--#echo var="VAR_composer-wrap-column"--></a>
3877 <li><a href="h_config_index_color_style">OPTION: <!--#echo var="VAR_current-indexline-style"--></a>
3878 <li><a href="h_config_cursor_style">OPTION: Cursor Style</a>
3879 <li><a href="h_config_custom_hdrs">OPTION: <!--#echo var="VAR_customized-hdrs"--></a>
3880 <li><a href="h_config_deadlets">OPTION: <!--#echo var="VAR_dead-letter-files"--></a>
3881 <li><a href="h_config_comp_hdrs">OPTION: <!--#echo var="VAR_default-composer-hdrs"--></a>
3882 <li><a href="h_config_default_fcc">OPTION: <!--#echo var="VAR_default-fcc"--></a>
3883 <li><a href="h_config_def_save_folder">OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></a>
3884 <li><a href="h_config_disable_auths">OPTION: <!--#echo var="VAR_disable-these-authenticators"--></a>
3885 <li><a href="h_config_disable_drivers">OPTION: <!--#echo var="VAR_disable-these-drivers"--></a>
3886 <li><a href="h_config_char_set">OPTION: Display Character Set</a>
3887 <li><a href="h_config_display_filters">OPTION: <!--#echo var="VAR_display-filters"--></a>
3888 <li><a href="h_config_download_cmd">OPTION: <!--#echo var="VAR_download-command"--></a>
3889 <li><a href="h_config_download_prefix">OPTION: <!--#echo var="VAR_download-command-prefix"--></a>
3890 <li><a href="h_config_editor">OPTION: <!--#echo var="VAR_editor"--></a>
3891 <li><a href="h_config_empty_hdr_msg">OPTION: <!--#echo var="VAR_empty-header-message"--></a>
3892 <li><a href="h_config_fcc_rule">OPTION: <!--#echo var="VAR_fcc-name-rule"--></a>
3893 <li><a href="h_config_file_dir">OPTION: File Directory</a>
3894 <li><a href="h_config_folder_spec">OPTION: <!--#echo var="VAR_folder-collections"--></a>
3895 <li><a href="h_config_reopen_rule">OPTION: <!--#echo var="VAR_folder-reopen-rule"--></a>
3896 <li><a href="h_config_fld_sort_rule">OPTION: <!--#echo var="VAR_folder-sort-rule"--></a>
3897 <li><a href="h_config_font_char_set">OPTION: Font Character Set</a>
3898 <li><a href="h_config_font_name">OPTION: Font Name</a>
3899 <li><a href="h_config_font_size">OPTION: Font Size</a>
3900 <li><a href="h_config_font_style">OPTION: Font Style</a>
3901 <li><a href="h_config_form_folder">OPTION: <!--#echo var="VAR_form-letter-folder"--></a>
3902 <li><a href="h_config_glob_addrbook">OPTION: <!--#echo var="VAR_global-address-book"--></a>
3903 <li><a href="h_config_goto_default">OPTION: <!--#echo var="VAR_goto-default-rule"--></a>
3904 <li><a href="h_config_header_general_color">OPTION: Header General Color</a>
3905 <li><a href="h_config_image_viewer">OPTION: <!--#echo var="VAR_image-viewer"--></a>
3906 <li><a href="h_config_inbox_path">OPTION: <!--#echo var="VAR_inbox-path"--></a>
3907 <li><a href="h_config_archived_folders">OPTION: <!--#echo var="VAR_incoming-archive-folders"--></a>
3908 <li><a href="h_config_psleep">OPTION: <!--#echo var="VAR_mailcap-check-interval"--></a>
3909 <li><a href="h_config_incoming_interv">OPTION: <!--#echo var="VAR_incoming-check-interval"--></a>
3910 <li><a href="h_config_incoming_second_interv">OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></a>
3911 <li><a href="h_config_incoming_list">OPTION: <!--#echo var="VAR_incoming-check-list"--></a>
3912 <li><a href="h_config_incoming_timeo">OPTION: <!--#echo var="VAR_incoming-check-timeout"--></a>
3913 <li><a href="h_config_incoming_folders">OPTION: <!--#echo var="VAR_incoming-folders"--></a>
3914 <li><a href="h_config_inc_startup">OPTION: <!--#echo var="VAR_incoming-startup-rule"--></a>
3915 <li><a href="h_config_incunseen_color">OPTION: Incoming Unseen Color</a>
3916 <li><a href="h_config_index_arrow_color">OPTION: Index Arrow Color</a>
3917 <li><a href="h_config_index_color">OPTION: Index Colors</a>
3918 <li><a href="h_config_index_format">OPTION: <!--#echo var="VAR_index-format"--></a>
3919 <li><a href="h_config_index_from_color">OPTION: Index From Color</a>
3920 <li><a href="h_config_index_opening_color">OPTION: Index Opening Color</a>
3921 <li><a href="h_config_index_pri_color">OPTION: Index Priority Symbol Colors</a>
3922 <li><a href="h_config_index_subject_color">OPTION: Index Subject Color</a>
3923 <li><a href="h_config_init_cmd_list">OPTION: <!--#echo var="VAR_initial-keystroke-list"--></a>
3924 <li><a href="h_config_key_char_set">OPTION: Keyboard Character Set</a>
3925 <li><a href="h_config_keylabel_color">OPTION: KeyLabel Color</a>
3926 <li><a href="h_config_keyname_color">OPTION: KeyName Color</a>
3927 <li><a href="h_config_keywords">OPTION: <!--#echo var="VAR_keywords"--></a>
3928 <li><a href="h_config_kw_color">OPTION: Keyword Colors</a>
3929 <li><a href="h_config_kw_braces">OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></a>
3930 <li><a href="h_config_prune_date">OPTION: <!--#echo var="VAR_last-time-prune-questioned"--></a>
3931 <li><a href="h_config_last_vers">OPTION: <!--#echo var="VAR_last-version-used"--></a>
3932 <li><a href="h_config_literal_sig">OPTION: <!--#echo var="VAR_literal-signature"--></a>
3933 <li><a href="h_config_mailcheck">OPTION: <!--#echo var="VAR_mail-check-interval"--></a>
3934 <li><a href="h_config_mailchecknoncurr">OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></a>
3935 <li><a href="h_config_mailcap_path">OPTION: <!--#echo var="VAR_mailcap-search-path"--></a>
3936 <li><a href="h_config_maildropcheck">OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></a>
3937 <li><a href="h_config_maxremstream">OPTION: <!--#echo var="VAR_max-remote-connections"--></a>
3938 <li><a href="h_config_metamsg_color">OPTION: Meta-Message Color</a>
3939 <li><a href="h_config_mimetype_path">OPTION: <!--#echo var="VAR_mimetype-search-path"--></a>
3940 <li><a href="h_config_new_ver_quell">OPTION: <!--#echo var="VAR_new-version-threshold"--></a>
3941 <li><a href="h_config_fifopath">OPTION: NewMail FIFO Path</a>
3942 <li><a href="h_config_newmailwidth">OPTION: <!--#echo var="VAR_newmail-window-width"--></a>
3943 <li><a href="h_config_news_active">OPTION: <!--#echo var="VAR_news-active-file-path"--></a>
3944 <li><a href="h_config_news_spec">OPTION: <!--#echo var="VAR_news-collections"--></a>
3945 <li><a href="h_config_news_spool">OPTION: <!--#echo var="VAR_news-spool-directory"--></a>
3946 <li><a href="h_config_newsrc_path">OPTION: <!--#echo var="VAR_newsrc-path"--></a>
3947 <li><a href="h_config_nntprange">OPTION: <!--#echo var="VAR_nntp-range"--></a>
3948 <li><a href="h_config_nntp_server">OPTION: <!--#echo var="VAR_nntp-server"--></HEAD></a>
3949 <li><a href="h_config_normal_color">OPTION: Normal Color</a>
3950 <li><a href="h_config_opening_sep">OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></a>
3951 <li><a href="h_config_oper_dir">OPTION: <!--#echo var="VAR_operating-dir"--></a>
3952 <li><a href="h_config_pat_old">OPTION: Patterns</a>
3953 <li><a href="h_config_pat_filts">OPTION: <!--#echo var="VAR_patterns-filters2"--></a>
3954 <li><a href="h_config_pat_other">OPTION: <!--#echo var="VAR_patterns-other"--></a>
3955 <li><a href="h_config_pat_roles">OPTION: <!--#echo var="VAR_patterns-roles"--></a>
3956 <li><a href="h_config_pat_scores">OPTION: <!--#echo var="VAR_patterns-scores2"--></a>
3957 <li><a href="h_config_pers_name">OPTION: <!--#echo var="VAR_personal-name"--></a>
3958 <li><a href="h_config_print_cat">OPTION: <!--#echo var="VAR_personal-print-category"--></a>
3959 <li><a href="h_config_print_command">OPTION: <!--#echo var="VAR_personal-print-command"--></a>
3960 <li><a href="h_config_post_char_set">OPTION: <!--#echo var="VAR_posting-character-set"--></a>
3961 <li><a href="h_config_postponed_folder">OPTION: <!--#echo var="VAR_postponed-folder"--></a>
3962 <li><a href="h_config_print_font_char_set">OPTION: Print-Font-Char-Set</a>
3963 <li><a href="h_config_print_font_name">OPTION: Print-Font-Name</a>
3964 <li><a href="h_config_print_font_size">OPTION: Print-Font-Size</a>
3965 <li><a href="h_config_print_font_style">OPTION: Print-Font-Style</a>
3966 <li><a href="h_config_printer">OPTION: Printer</a>
3967 <li><a href="h_config_prompt_color">OPTION: Prompt Color</a>
3968 <li><a href="h_config_pruned_folders">OPTION: <!--#echo var="VAR_pruned-folders"--></a>
3969 <li><a href="h_config_pruning_rule">OPTION: <!--#echo var="VAR_pruning-rule"--></a>
3970 <li><a href="h_config_quote_color">OPTION: Quote Colors</a>
3971 <li><a href="h_config_quote_replace_string">OPTION: <!--#echo var="VAR_quote-replace-string"--></a>
3972 <li><a href="h_config_quote_suppression">OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></a>
3973 <li><a href="h_config_read_message_folder">OPTION: <!--#echo var="VAR_read-message-folder"--></a>
3974 <li><a href="h_config_remote_abook_history">OPTION: <!--#echo var="VAR_remote-abook-history"--></a>
3975 <li><a href="h_config_abook_metafile">OPTION: <!--#echo var="VAR_remote-abook-metafile"--></a>
3976 <li><a href="h_config_remote_abook_validity">OPTION: <!--#echo var="VAR_remote-abook-validity"--></a>
3977 <li><a href="h_config_reply_indent_string">OPTION: <!--#echo var="VAR_reply-indent-string"--></a>
3978 <li><a href="h_config_reply_intro">OPTION: <!--#echo var="VAR_reply-leadin"--></a>
3979 <li><a href="h_config_reverse_color">OPTION: Reverse Color</a>
3980 <li><a href="h_config_rshcmd">OPTION: <!--#echo var="VAR_rsh-command"--></a>
3981 <li><a href="h_config_rsh_open_timeo">OPTION: <!--#echo var="VAR_rsh-open-timeout"--></a>
3982 <li><a href="h_config_rshpath">OPTION: <!--#echo var="VAR_rsh-path"--></a>
3983 <li><a href="h_config_saved_msg_name_rule">OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></a>
3984 <li><a href="h_config_scroll_margin">OPTION: <!--#echo var="VAR_scroll-margin"--></a>
3985 <li><a href="h_config_slctbl_color">OPTION: Selectable Item Color</a>
3986 <li><a href="h_config_sending_filter">OPTION: <!--#echo var="VAR_sending-filters"--></a>
3987 <li><a href="h_config_sendmail_path">OPTION: <!--#echo var="VAR_sendmail-path"--></a>
3988 <li><a href="h_config_signature_color">OPTION: Signature Color</a>
3989 <li><a href="h_config_signature_file">OPTION: <!--#echo var="VAR_signature-file"--></a>
3990 <li><a href="h_config_smtp_server">OPTION: <!--#echo var="VAR_smtp-server"--></a>
3991 <li><a href="h_config_sort_key">OPTION: <!--#echo var="VAR_sort-key"--></a>
3992 <li><a href="h_config_speller">OPTION: <!--#echo var="VAR_speller"--></a>
3993 <li><a href="h_config_sshcmd">OPTION: <!--#echo var="VAR_ssh-command"--></a>
3994 <li><a href="h_config_ssh_open_timeo">OPTION: <!--#echo var="VAR_ssh-open-timeout"--></a>
3995 <li><a href="h_config_sshpath">OPTION: <!--#echo var="VAR_ssh-path"--></a>
3996 <li><a href="h_config_status_color">OPTION: Status Color</a>
3997 <li><a href="h_config_status_msg_delay">OPTION: <!--#echo var="VAR_status-message-delay"--></a>
3998 <li><a href="h_config_permlocked">OPTION: <!--#echo var="VAR_stay-open-folders"--></a>
3999 <li><a href="h_config_tcp_open_timeo">OPTION: <!--#echo var="VAR_tcp-open-timeout"--></a>
4000 <li><a href="h_config_tcp_query_timeo">OPTION: <!--#echo var="VAR_tcp-query-timeout"--></a>
4001 <li><a href="h_config_tcp_readwarn_timeo">OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></a>
4002 <li><a href="h_config_tcp_writewarn_timeo">OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></a>
4003 <li><a href="h_config_thread_disp_style">OPTION: <!--#echo var="VAR_threading-display-style"--></a>
4004 <li><a href="h_config_thread_exp_char">OPTION: <!--#echo var="VAR_threading-expanded-character"--></a>
4005 <li><a href="h_config_thread_index_style">OPTION: <!--#echo var="VAR_threading-index-style"--></a>
4006 <li><a href="h_config_thread_indicator_char">OPTION: <!--#echo var="VAR_threading-indicator-character"--></a>
4007 <li><a href="h_config_thread_lastreply_char">OPTION: <!--#echo var="VAR_threading-lastreply-character"--></a>
4008 <li><a href="h_config_title_color">OPTION: Title Color</a>
4009 <li><a href="h_config_titleclosed_color">OPTION: Title Closed Color</a>
4010 <li><a href="h_config_titlebar_color_style">OPTION: <!--#echo var="VAR_titlebar-color-style"--></a>
4011 <li><a href="h_config_unk_char_set">OPTION: <!--#echo var="VAR_unknown-character-set"--></a>
4012 <li><a href="h_config_upload_cmd">OPTION: <!--#echo var="VAR_upload-command"--></a>
4013 <li><a href="h_config_upload_prefix">OPTION: <!--#echo var="VAR_upload-command-prefix"--></a>
4014 <li><a href="h_config_browser">OPTION: <!--#echo var="VAR_url-viewers"--></a>
4015 <li><a href="h_config_domain_name">OPTION: <!--#echo var="VAR_use-only-domain-name"--></a>
4016 <li><a href="h_config_user_dom">OPTION: <!--#echo var="VAR_user-domain"--></a>
4017 <li><a href="h_config_user_id">OPTION: <!--#echo var="VAR_user-id"--></a>
4018 <li><a href="h_config_user_input_timeo">OPTION: <!--#echo var="VAR_user-input-timeout"--></a>
4019 <li><a href="h_config_viewer_headers">OPTION: <!--#echo var="VAR_viewer-hdrs"--></a>
4020 <li><a href="h_config_customhdr_pattern">OPTION: Viewer Header Color Pattern</a>
4021 <li><a href="h_config_customhdr_color">OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></a>
4022 <li><a href="h_config_viewer_margin_left">OPTION: <!--#echo var="VAR_viewer-margin-left"--></a>
4023 <li><a href="h_config_viewer_margin_right">OPTION: <!--#echo var="VAR_viewer-margin-right"--></a>
4024 <li><a href="h_config_viewer_overlap">OPTION: <!--#echo var="VAR_viewer-overlap"--></a>
4025 <li><a href="h_config_window_position">OPTION: Window-Position</a>
4026 <li><a href="h_mainhelp_patterns">Patterns</a>
4027 <li><a href="h_config_role_abookfrom">PATTERNS: Address in Address Book</a>
4028 <li><a href="h_config_role_age">PATTERNS: Age Interval</a>
4029 <li><a href="h_config_role_alltextpat">PATTERNS: AllText Pattern</a>
4030 <li><a href="h_config_role_bom">PATTERNS: Beginning of Month</a>
4031 <li><a href="h_config_role_boy">PATTERNS: Beginning of Year</a>
4032 <li><a href="h_config_role_bodytextpat">PATTERNS: BodyText Pattern</a>
4033 <li><a href="h_config_role_cat_cmd">PATTERNS: Categorizer Command</a>
4034 <li><a href="h_config_role_cat_cmd_example">PATTERNS: Categorizer Command Example</a>
4035 <li><a href="h_config_role_ccpat">PATTERNS: Cc Pattern</a>
4036 <li><a href="h_config_role_cat_limit">PATTERNS: Character Limit</a>
4037 <li><a href="h_config_role_charsetpat">PATTERNS: Character Set Pattern</a>
4038 <li><a href="h_config_role_comment">PATTERNS: Comment</a>
4039 <li><a href="h_config_role_fldr_type">PATTERNS: Current Folder Type</a>
4040 <li><a href="h_config_role_cat_status">PATTERNS: Exit Status Interval</a>
4041 <li><a href="h_config_role_arbpat">PATTERNS: Extra Headers Pattern</a>
4042 <li><a href="h_config_role_frompat">PATTERNS: From Pattern</a>
4043 <li><a href="h_config_role_keywordpat">PATTERNS: Keyword Pattern</a>
4044 <li><a href="h_config_role_stat_ans">PATTERNS: Message Answered Status</a>
4045 <li><a href="h_config_role_stat_del">PATTERNS: Message Deleted Status</a>
4046 <li><a href="h_config_role_stat_imp">PATTERNS: Message Important Status</a>
4047 <li><a href="h_config_role_stat_new">PATTERNS: Message New Status</a>
4048 <li><a href="h_config_role_stat_recent">PATTERNS: Message Recent Status</a>
4049 <li><a href="h_config_role_newspat">PATTERNS: News Pattern</a>
4050 <li><a href="h_config_role_nick">PATTERNS: Nickname</a>
4051 <li><a href="h_config_role_particpat">PATTERNS: Participant Pattern</a>
4052 <li><a href="h_config_role_stat_8bitsubj">PATTERNS: Raw 8-bit in Subject</a>
4053 <li><a href="h_config_role_recippat">PATTERNS: Recipient Pattern</a>
4054 <li><a href="h_config_role_scorei">PATTERNS: Score Interval</a>
4055 <li><a href="h_config_role_senderpat">PATTERNS: Sender Pattern</a>
4056 <li><a href="h_config_role_size">PATTERNS: Size Interval</a>
4057 <li><a href="h_config_role_subjpat">PATTERNS: Subject Pattern</a>
4058 <li><a href="h_config_role_topat">PATTERNS: To Pattern</a>
4059 <li><a href="h_config_filt_opts_nonterm">PATTERNS FEATURE: Dont-Stop-Even-if-Rule-Matches</a>
4060 <li><a href="h_config_filt_opts_notdel">PATTERNS FEATURE: Move-Only-if-Not-Deleted</a>
4061 <li><a href="h_config_filt_opts_sentdate">PATTERNS FEATURE: Use-Date-Header-For-Age</a>
4062 <li><a href="h_config_filt_rule_type">PATTERNS FILTER ACTION: Filter Action</a>
4063 <li><a href="h_config_filter_kw_clr">PATTERNS FILTER ACTION: Clear These Keywords</a>
4064 <li><a href="h_config_filt_stat_ans">PATTERNS FILTER ACTION: Set Answered Status</a>
4065 <li><a href="h_config_filt_stat_del">PATTERNS FILTER ACTION: Set Deleted Status</a>
4066 <li><a href="h_config_filt_stat_imp">PATTERNS FILTER ACTION: Set Important Status</a>
4067 <li><a href="h_config_filt_stat_new">PATTERNS FILTER ACTION: Set New Status</a>
4068 <li><a href="h_config_filter_kw_set">PATTERNS FILTER ACTION: Set These Keywords</a>
4069 <li><a href="h_config_incol">PATTERNS INDEXCOLOR ACTION: Index Line Color</a>
4070 <li><a href="h_config_set_index_format">PATTERNS OTHER ACTION: Set Index Format</a>
4071 <li><a href="h_config_perfolder_sort">PATTERNS OTHER ACTION: Set Sort Order</a>
4072 <li><a href="h_config_other_startup">PATTERNS OTHER ACTION: Set Startup Rule</a>
4073 <li><a href="h_config_role_inick">PATTERNS ROLE ACTION: Initialize Values From Role</a>
4074 <li><a href="h_config_role_setfcc">PATTERNS ROLE ACTION: Set Fcc</a>
4075 <li><a href="h_config_role_setfrom">PATTERNS ROLE ACTION: Set From</a>
4076 <li><a href="h_config_role_setlitsig">PATTERNS ROLE ACTION: Set Literal Signature</a>
4077 <li><a href="h_config_role_setotherhdr">PATTERNS ROLE ACTION: Set Other Headers</a>
4078 <li><a href="h_config_role_setreplyto">PATTERNS ROLE ACTION: Set Reply-To</a>
4079 <li><a href="h_config_role_setsig">PATTERNS ROLE ACTION: Set Signature</a>
4080 <li><a href="h_config_role_settempl">PATTERNS ROLE ACTION: Set Template</a>
4081 <li><a href="h_config_role_usenntp">PATTERNS ROLE ACTION: Use NNTP Server</a>
4082 <li><a href="h_config_role_usesmtp">PATTERNS ROLE ACTION: Use SMTP Server</a>
4083 <li><a href="h_config_role_scoreval">PATTERNS SCORE ACTION: Score Value</a>
4084 <li><a href="h_config_role_scorehdrtok">PATTERNS SCORE ACTION: Score Value From Header</a>
4085 <li><a href="h_config_role_composeuse">PATTERNS USE: Compose Use</a>
4086 <li><a href="h_config_role_forwarduse">PATTERNS USE: Forward Use</a>
4087 <li><a href="h_config_role_replyuse">PATTERNS USE: Reply Use</a>
4088 <li><a href="h_pipe_command">Pipe Command SubOptions</a>
4089 <li><a href="h_common_pipe">Pipe Command</a>
4090 <li><a href="h_valid_folder_names">POP</a>
4091 <li><a href="h_common_postpone">Postpone Command</a>
4092 <li><a href="h_common_print">Print Command</a>
4093 <li><a href="h_mainhelp_readingnews">Reading News</a>
4094 <li><a href="h_news">RELEASE NOTES for Alpine</a>
4095 <li><a href="h_mainhelp_roles">Roles</a>
4096 <li><a href="h_role_select">ROLES SCREEN</a>
4097 <li><a href="h_compose_readfile">Read File Command</a>
4098 <li><a href="h_mainhelp_reading">Reading Messages</a>
4099 <li><a href="h_main_release_notes">Release Notes Command</a>
4100 <li><a href="h_common_reply">Reply and Forward Commands</a>
4101 <li><a href="h_compose_richhdr">Rich Header Command</a>
4102 <li><a href="h_common_role">Role Command</a>
4103 <li><a href="h_mainhelp_smime">S/MIME</a>
4104 <li><a href="h_index_cmd_select">Searching for Messages</a>
4105 <li><a href="h_address_display">SEARCH RESULTS INDEX</a>
4106 <li><a href="h_address_select">SEARCH RESULTS INDEX</a>
4107 <li><a href="h_simple_index">SELECT POSTPONED MESSAGE</a>
4108 <li><a href="h_abook_config">SETUP ADDRESS BOOKS SCREEN</a>
4109 <li><a href="h_collection_maint">SETUP COLLECTION LIST screen</a>
4110 <li><a href="h_color_setup">SETUP COLOR COMMANDS</a>
4111 <li><a href="h_direct_config">SETUP LDAP DIRECTORY SERVERS SCREEN</a>
4112 <li><a href="h_rules_roles">SETUP ROLES SCREEN</a>
4113 <li><a href="h_rules_incols">SETUP INDEX COLORS SCREEN</a>
4114 <li><a href="h_rules_filter">SETUP FILTERING SCREEN</a>
4115 <li><a href="h_rules_score">SETUP SCORING SCREEN</a>
4116 <li><a href="h_common_save">Save and Export Commands</a>
4117 <li><a href="h_mainhelp_securing">Securing Your Alpine Session</a>
4118 <li><a href="h_index_cmd_select">Selecting: Select and WhereIs/Select</a>
4119 <li><a href="h_compose_send">Send Command</a>
4120 <li><a href="h_folder_server_syntax">Server Name Syntax</a>
4121 <li><a href="h_main_setup">Setup Command</a>
4122 <li><a href="X-Alpine-Config:">Show Supported Options in this Alpine</a>
4123 <li><a href="h_composer_sigedit">Signature Editor Commands Explained</a>
4124 <li><a href="h_simple_text_view">Simple Text View Screen Explained</a>
4125 <li><a href="h_mainhelp_smime">S/MIME</a>
4126 <li><a href="h_config_smime_dont_do_smime">S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></a>
4127 <li><a href="h_config_smime_encrypt_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></a>
4128 <li><a href="h_config_smime_remember_passphrase">S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></a>
4129 <li><a href="h_config_smime_sign_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></a>
4130 <li><a href="h_config_smime_use_cert_store">S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></a>
4131 <li><a href="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></a>
4132 <li><a href="h_config_smime_cacertcon">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></a>
4133 <li><a href="h_config_smime_cacertdir">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></a>
4134 <li><a href="h_config_smime_privkeycon">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-container"--></a>
4135 <li><a href="h_config_smime_privkeydir">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-directory"--></a>
4136 <li><a href="h_config_smime_pubcertcon">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-container"--></a>
4137 <li><a href="h_config_smime_pubcertdir">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></a>
4138 <li><a href="h_config_smime_transfer_cacert_to_con">S/MIME: Transfer CA Certs to Container</a>
4139 <li><a href="h_config_smime_transfer_cacert_to_dir">S/MIME: Transfer CA Certs to Directory</a>
4140 <li><a href="h_config_smime_transfer_priv_to_con">S/MIME: Transfer Private Keys to Container</a>
4141 <li><a href="h_config_smime_transfer_priv_to_dir">S/MIME: Transfer Private Keys to Directory</a>
4142 <li><a href="h_config_smime_transfer_pub_to_con">S/MIME: Transfer Public Certs to Container</a>
4143 <li><a href="h_config_smime_transfer_pub_to_dir">S/MIME: Transfer Public Certs to Directory</a>
4144 <li><a href="h_config_smime_public_certificates">S/MIME: Manage Public Certificates</a>
4145 <li><a href="h_config_smime_private_keys">S/MIME: Manage Private Keys</a>
4146 <li><a href="h_config_smime_certificate_authorities">S/MIME: Manage Certificate Authorities</a>
4147 <li><a href="h_index_cmd_sort">Sort Command</a>
4148 <li><a href="h_compose_spell">Spell Check Command</a>
4149 <li><a href="h_common_suspend">Suspend Command</a>
4150 <li><a href="h_compose_addrcomplete">THE MESSAGE COMPOSER'S ADDRESS COMPLETION</a>
4151 <li><a href="h_composer_attachment">THE MESSAGE COMPOSER'S ATTCHMNT FIELD</a>
4152 <li><a href="h_composer_bcc">THE MESSAGE COMPOSER'S BCC FIELD</a>
4153 <li><a href="h_composer_cc">THE MESSAGE COMPOSER'S CC FIELD</a>
4154 <li><a href="h_composer_from">THE MESSAGE COMPOSER'S FROM FIELD</a>
4155 <li><a href="h_composer_lcc">THE MESSAGE COMPOSER'S LCC FIELD</a>
4156 <li><a href="h_composer_news">THE MESSAGE COMPOSER'S NEWSGRPS LINE</a>
4157 <li><a href="h_composer_reply_to">THE MESSAGE COMPOSER'S REPLY-TO FIELD</a>
4158 <li><a href="h_composer_to">THE MESSAGE COMPOSER'S TO FIELD</a>
4159 <li><a href="h_abook_opened">THE ALPINE ADDRESS BOOK</a>
4160 <li><a href="h_abook_select_nicks_take">Take Address Nickname Selection Explained</a>
4161 <li><a href="h_takeaddr_screen">Take Address Screen Explained</a>
4162 <li><a href="h_common_take">TakeAddr Command</a>
4163 <li><a href="h_mainhelp_status">Titlebar Line</a>
4164 <li><a href="h_index_tokens">Tokens for Index and Replying</a>
4165 <li><a href="h_config_usenone_color">Use None Color</a>
4166 <li><a href="h_config_usenormal_color">Use Normal Color</a>
4167 <li><a href="h_config_usetransparent_color">Use Transparent Color</a>
4168 <li><a href="h_whatis_vcard">VCARD EXPLAINED</a>
4169 <li><a href="h_view_cmd_hilite">View Hilite and Next item/Previous item</a>
4170 <li><a href="h_view_cmd_viewattch">ViewAttch Command</a>
4171 <li><a href="h_index_cmd_whereis">WhereIs Command</a>
4172 <li><a href="h_view_cmd_whereis">WhereIs Command</a>
4173 <li><a href="h_index_cmd_zoom">ZoomMode Command</a>
4174 <li><a href="h_config_browser_xterm"><!--#echo var="VAR_url-viewers"--> and X windows applications</a>
4175 </UL>
4177 <P>
4178 <End of Help Index>
4179 </BODY>
4180 </HTML>
4183 ============== h_config_remote_config =============
4184 <HTML>
4185 <HEAD>
4186 <TITLE>Remote Configuration</TITLE>
4187 </HEAD>
4188 <BODY>
4189 <H1>Remote Configuration</H1>
4191 You may use the command line argument "-p pinerc" to tell
4192 Alpine to use a non-default configuration file.
4193 There are two types of storage for configuration information.
4194 <EM>Local</EM> configuration files are used by default.
4195 These are just regular files on the UNIX system or on the PC.
4196 The file "<CODE>.pinerc</CODE>" is the default for Unix Alpine and the
4197 file "<CODE>PINERC</CODE>" is the default for PC-Alpine.
4198 <EM>Remote</EM> configuration folders are stored on an IMAP server.
4199 The advantage of using a remote configuration is that the same information
4200 may be accessed from multiple platforms.
4201 For example, if you use one computer at work and another at home, the same
4202 configuration could be used from both places.
4203 A configuration change from one place would be seen in both places.
4204 To use a remote configuration you simply give a
4205 <A HREF="h_valid_folder_names">remote folder name</A>
4206 as the argument to the "-p" command line option.
4207 The command line might look something like:
4208 <P>
4209 <CENTER><SAMP>pine -p {my.imap.server}remote_pinerc</SAMP></CENTER>
4210 <P>
4211 If there are special characters in the command shell you use, you may need to
4212 quote the last argument (to protect the curly braces from the shell).
4213 The command might look like:
4214 <P>
4215 <CENTER><SAMP>pine -p "{my.imap.server}remote_pinerc"</SAMP></CENTER>
4216 <P>
4217 You should choose a folder name for a folder that does not yet exist.
4218 It will be created containing an empty configuration.
4219 Do not use a folder that you wish to store regular mail messages in.
4220 <P>
4221 The Setup/RemoteConfigSetup command will help you convert from a local
4222 configuration to a remote configuration.
4223 It will create a remote configuration for you and copy your current local
4224 configuration to it.
4225 It will also help you convert local address books into remote address books
4226 and local signature files into literal signatures contained in the
4227 remote configuration file.
4228 <P>
4229 If the Setup/RemoteConfigSetup command doesn't do what you want, you
4230 may copy a local pinerc file to a remote configuration folder by hand
4231 by using the command line option "-copy_pinerc".
4232 <P>
4233 Another command line option, which is somewhat related to remote
4234 configuration, is the option "-x exceptions_config".
4235 The configuration settings in the exceptions configuration override
4236 your default settings.
4237 It may be useful to store the default configuration (the -p argument) remotely
4238 and to have the exceptions configuration stored in a local file.
4239 You might put generic configuration information in the remote configuration
4240 and platform-specific configuration on each platform in the exceptions
4241 configuration.
4242 The arguments to the "-p" and "-x" options
4243 can be either remote folders or local files.
4244 <P>
4245 There is another command line argument that works only with PC-Alpine and
4246 which may prove useful when using a remote configuration.
4247 The option "-aux local_directory" allows you to tell PC-Alpine where
4248 to store your local auxiliary files.
4249 This only has an effect if your configuration file is remote.
4250 Some examples of auxiliary files are debug files, address book files, and
4251 signature files.
4252 <P>
4253 <End of help on this topic>
4254 </BODY>
4255 </HTML>
4256 ============== h_config_exceptions =============
4257 <HTML>
4258 <HEAD>
4259 <TITLE>Generic and Exceptional Configuration</TITLE>
4260 </HEAD>
4261 <BODY>
4262 <H1>Generic and Exceptional Configuration</H1>
4264 If you use Alpine from more than one platform it may be convenient
4265 to split your configuration information into two pieces, a generic piece
4266 and exceptions that apply to a particular platform.
4267 For example, suppose you use Alpine from home and from work.
4268 Most of your configuration settings are probably the
4269 same in both locations, so those settings belong in the generic settings
4270 configuration.
4271 However, you may use a different SMTP server and INBOX
4272 from home than you do from work.
4273 The
4274 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
4275 and
4276 <A HREF="h_config_inbox_path">"<!--#echo var="VAR_inbox-path"-->"</A>
4277 options could be
4278 part of your exceptional configuration so that they could be different in the
4279 two places.
4280 <P>
4281 The command line option "-x exceptions_config"
4282 may be used to split your configuration into generic and exceptional pieces.
4283 "Exceptions_config" may be either local or remote.
4284 The regular Alpine configuration file will contain the generic data, and
4285 "exceptions_config" will contain the exceptional data.
4286 <P>
4287 For Unix Alpine, if you don't have a "-x" command line option,
4288 Alpine will look for the file "<CODE>.pinercex</CODE>"
4289 in the same local directory that the regular config file is located in (usually
4290 the Unix home directory).
4291 If the regular config file is remote (because the command line option
4292 "-p remote_config" was used) then Unix Alpine looks in the Unix home
4293 directory for "<CODE>.pinercex</CODE>".
4294 If the file does not already exist then no exceptions will be used.
4295 You can force exceptions to be used by using the "-x" option or
4296 by creating an empty "<CODE>.pinercex</CODE>" file.
4297 <P>
4298 For PC-Alpine, if you don't have a "-x" command line option,
4299 PC-Alpine will use the value of the
4300 environment variable <CODE>$PINERCEX</CODE>.
4301 If that is not set, PC-Alpine will look for
4302 the local file "<CODE>PINERCEX</CODE>"
4303 in the same local directory that the regular config file is located in.
4304 If the regular config file is remote (because the command line option
4305 "-p remote_config" was used) then PC-Alpine looks in the
4306 local directory specified by the "-aux local_directory" command
4307 line argument, or the directory <CODE>$HOME\PINE</CODE>, or
4308 in the <CODE><PINE.EXE </CODE>directory<CODE>></CODE>.
4309 <P>
4310 When you have an exception configuration there is a new command
4311 in the Alpine Setup screen, Setup/eXceptions.
4312 It toggles between exceptions and the regular configuration.
4313 This is the usual way to make changes in your exceptional configuration data.
4314 For example, you would type "S" for Setup, "X" for
4315 eXception, then follow that with one of the Setup commands, like "C"
4316 for Config or "K" for Kolor.
4317 <P>
4318 For most people, splitting the configuration information into two pieces is
4319 going to be most useful if the generic information is accessed
4320 <A HREF="h_config_remote_config">remotely</A>).
4321 That data will be the same no matter where you access it from and if you
4322 change it that change will show up everywhere.
4323 The exceptional data will most commonly be in a local file, so that the
4324 contents may easily be different on each computing platform used.
4325 <P>
4326 If you already have a local configuration file with settings you like
4327 you may find that the command Setup/RemoteConfigSetup is useful
4328 in helping you convert to a remote configuration.
4329 The command line flag "-copy_pinerc"
4330 may also be useful.
4331 <P>
4332 <End of help on this topic>
4333 </BODY>
4334 </HTML>
4335 ============== h_config_inheritance =============
4336 <HTML>
4337 <HEAD>
4338 <TITLE>Configuration Inheritance</TITLE>
4339 </HEAD>
4340 <BODY>
4341 <H1>Configuration Inheritance</H1>
4343 Configuration inheritance is a power user feature.
4344 It is confusing and not completely supported by the configuration
4345 user interface.
4346 We start with an explanation of how configuration works in hopes of making
4347 it easier to describe how inheritance works.
4348 <P>
4349 Alpine uses a hierarchy of configuration values from different locations.
4350 There are five ways in which each configuration option (configuration
4351 variable) can be set.
4352 In increasing order of precedence they are:
4353 <P>
4354 <OL>
4355 <LI> the system-wide configuration file.
4357 <LI> the personal configuration file
4359 <LI> the personal exceptions file
4361 <LI> a command line argument
4363 <LI> the system-wide <EM>fixed</EM> configuration file (Unix Alpine only)
4364 </OL>
4365 <P>
4366 The fixed configuration file is normally
4367 <CODE><!--#echo var="PINE_CONF_FIXED_PATH"--></CODE>.
4368 <P>
4369 The system-wide configuration file is normally
4370 <CODE><!--#echo var="PINE_CONF_PATH"--></CODE> for Unix Alpine and is normally not
4371 set for PC-Alpine.
4372 For PC-Alpine, if the environment variable <EM>$PINECONF</EM> is set, that
4373 is used for the system-wide configuration.
4374 This location can be set or changed on the command line with the -P flag.
4375 The system-wide configuration file can be either a local file or a
4376 remote configuration folder.
4377 <P>
4378 For Unix Alpine, the personal configuration file is normally the file
4379 <CODE>.pinerc</CODE> in the user's home directory.
4380 This can be changed with the -p command line flag.
4381 For PC-Alpine, the personal configuration file is in
4382 <CODE>$PINERC</CODE> or <CODE><AlpineRC registry value></CODE> or
4383 <CODE>$HOME\PINE\PINERC</CODE> or
4384 <CODE><PINE.EXE </CODE>dir<CODE>>\PINERC</CODE>.
4385 This can be changed with the -p command line flag.
4386 If -p is used, the configuration data may be in a local file or a remote config
4387 folder.
4388 <P>
4389 For Unix Alpine, the personal exceptions configuration file is named
4390 <CODE>.pinercex</CODE> and is in the same directory as the personal
4391 configuration file, if that configuration file is not remote, and is in
4392 the home directory if the personal configuration file is remote.
4393 If the file exists, then exceptions are turned on.
4394 If it doesn't, then you are not using exceptions.
4395 Alternatively, you may change the location of the exceptions configuration
4396 by using the command line argument "-x <exceptions_config>".
4397 Like the personal configuration data, exceptions_config may be
4398 either local or remote.
4399 <P>
4400 For PC-Alpine, the personal exceptions configuration file is named
4401 <CODE>PINERCEX</CODE> and is in the same directory as the personal
4402 configuration file unless the personal configuration file is remote.
4403 In that case, it is in the local directory specfied by the
4404 "-aux local_directory" command line argument.
4405 (In the case that the personal configuration is remote and there is no
4406 "-aux" command line argument, Alpine searches for
4407 a PINERCEX file in the directory <CODE>$HOME\PINE</CODE> and
4408 the directory <CODE><PINE.EXE </CODE>dir<CODE>></CODE>.)
4409 If the file exists, then exceptions are turned on.
4410 If it doesn't, then you are not using exceptions.
4411 You may change the location of the exceptions configuration
4412 by using the command line argument "-x <exceptions_config>".
4413 or with the
4414 environment variable <CODE>$PINERCEX</CODE> (if there is no "-x"
4415 option).
4416 <P>
4417 To reiterate, the value of a configuration option is taken from the
4418 last location in the list above in which it is set.
4419 Or, thinking about it slightly differently, a default value for an option
4420 is established in the system-wide configuration file (or internally by Alpine
4421 if there is no value in the system-wide file).
4422 That default remains in effect until and unless it is overridden by a value in a
4423 location further down the list, in which case a new "default"
4424 value is established.
4425 As we continue down the list of locations we either retain the
4426 value at each step or establish a new value.
4427 The value that is still set after going through the whole list of
4428 configuration locations is the one that is used.
4429 <P>
4430 So, for example, if an option is set in the system-wide configuration
4431 file and in the personal configuration file, but is not set in the
4432 exceptions, on the command line, or in the fixed file; then the value
4433 from the personal configuration file is the one that is used.
4434 Or, if it is set in the system-wide config, in the personal config, not
4435 in the exceptions, but is set on the command line; then the value
4436 on the command line is used.
4437 <P>
4438 Finally we get to inheritance.
4439 For configuration options that are lists, like "<!--#echo var="VAR_smtp-server"-->" or
4440 "<!--#echo var="VAR_incoming-folders"-->",
4441 the inheritance mechanism makes it possible to <EM>combine</EM>
4442 the values from different locations instead of <EM>replacing</EM> the value.
4443 This is true of all configuration lists other than the "Feature-List",
4444 for which you may already set whatever you want at
4445 any configuration location (by using the "no-" prefix if
4446 necessary).
4447 <P>
4448 To use inheritance, set the first item in a configuration list to the
4449 token "INHERIT", without the quotes.
4450 If the first item is "INHERIT",
4451 then instead of replacing the default value established so far, the rest of
4452 the list is appended to the default value established so far and that is
4453 the new value.
4454 <P>
4455 Here is an example which may make it clearer. Suppose we have:
4456 <P>
4457 <PRE>
4458 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4459 Personal config : smtp-server = INHERIT, mysmtp.home
4460 Exceptions config : smtp-server = <No Value Set>
4461 Command line : smtp-server = <No Value Set>
4462 Fixed config : smtp-server = <No Value Set>
4463 </PRE>
4464 <P>
4466 This would result in an effective smtp-server option of
4467 <P>
4468 <PRE>
4469 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home
4470 </PRE>
4471 <P>
4472 The "INHERIT" token can be used in any of the configuration files
4473 and the effect cascades.
4474 For example, if we change the above example to:
4475 <P>
4476 <PRE>
4477 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4478 Personal config : smtp-server = INHERIT, mysmtp.home
4479 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4480 Command line : smtp-server = <No Value Set>
4481 Fixed config : smtp-server = <No Value Set>
4482 </PRE>
4483 <P>
4485 This would result in:
4486 <P>
4487 <PRE>
4488 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home, yoursmtp.org
4489 </PRE>
4490 <P>
4491 Unset variables are skipped over (the default value is carried forward) so
4492 that, for example:
4493 <P>
4494 <PRE>
4495 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4496 Personal config : smtp-server = <No Value Set>
4497 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4498 Command line : smtp-server = <No Value Set>
4499 Fixed config : smtp-server = <No Value Set>
4500 </PRE>
4501 <P>
4503 produces:
4504 <P>
4505 <PRE>
4506 smtp-server = smtp1.corp.com, smtp2.corp.com, yoursmtp.org
4507 </PRE>
4508 <P>
4510 If any later configuration location has a value set (for a particular list
4511 option) which does <EM>not</EM> begin with "INHERIT",
4512 then that value replaces whatever value has been defined up to that point.
4513 In other words, that cancels out any previous inheritance.
4514 <P>
4515 <PRE>
4516 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4517 Personal config : smtp-server = INHERIT, mysmtp.org
4518 Exceptions config : smtp-server = yoursmtp.org
4519 Command line : smtp-server = <No Value Set>
4520 Fixed config : smtp-server = <No Value Set>
4521 </PRE>
4522 <P>
4524 results in:
4525 <P>
4526 <PRE>
4527 smtp-server = yoursmtp.org
4528 </PRE>
4529 <P>
4531 For some configuration options, like "<!--#echo var="VAR_viewer-hdr-colors"-->" or
4532 "<!--#echo var="VAR_patterns-roles"-->", it is
4533 difficult to insert the value "INHERIT" into the list of values
4534 for the option using the normal Setup tools.
4535 In other words, the color setting screen (for example) does not
4536 provide a way to input the text "INHERIT" as the first
4537 item in the <!--#echo var="VAR_viewer-hdr-colors"--> option.
4538 The way to do this is to either edit the pinerc file directly and manually
4539 insert it, or turn
4540 on the <A HREF="h_config_expose_hidden_config"><!--#echo var="FEAT_expose-hidden-config"--></A>
4541 feature and insert it using the Setup/Config screen.
4542 <P>
4543 <End of help on this topic>
4544 </BODY>
4545 </HTML>
4546 ============== h_special_xon_xoff =============
4547 <HTML>
4548 <HEAD>
4549 <TITLE>Explanation of Alpine's XOFF/XON Handling</TITLE>
4550 </HEAD>
4551 <BODY>
4552 <H1>XOFF/XON Handling within Alpine</H1>
4554 By default, Alpine treats Ctrl-S or Ctrl-Q (sometimes known as XOFF
4555 and XON) as normal characters, even though Alpine does not use them.
4556 However, the printer, modem, or communication software you are using may
4557 be configured for "software flow control," which means that
4558 XON/XOFF must be treated as special characters by the operating system.
4559 If you see messages such as "^S not defined for this screen",
4560 then your system is probably using software flow control. In this case
4561 you will need to set the
4562 <A HREF="h_config_preserve_start_stop">"<!--#echo var="FEAT_preserve-start-stop-characters"-->"</A>
4563 feature.
4564 <P>
4565 If you <EM>do</EM> set this
4566 feature, be advised that if you accidentally hit a Ctrl-S, Alpine will
4567 mysteriously freeze up with no warning. In this case, try typing a Ctrl-Q
4568 and see if that puts things right. Printing via the
4569 "attached-to-ansi" or
4570 "attached-to-wyse"
4571 option will automatically enable software
4572 flow-control handling for the duration of the printing.
4573 <P>
4574 <End of help on this topic>
4575 </BODY>
4576 </HTML>
4577 ============= h_special_help_nav =============
4578 <HTML>
4579 <HEAD>
4580 <TITLE>Help Text Navigation Explained</TITLE>
4581 </HEAD>
4582 <BODY>
4583 <H1>Help Text Navigation Explained</H1>
4585 Alpine contains extensive context-sensitive help text. At any point,
4586 pressing the "?" key will bring up a page of help text
4587 explaining the options available to you. You can leave the help
4588 text screen and return to normal Alpine operation by pressing
4589 the
4590 <!--chtml if pinemode="function_key"-->
4591 F3 function
4592 <!--chtml else-->
4593 "E"
4594 <!--chtml endif-->
4595 key to Exit Help at any time.
4597 <P>
4598 Within the help screen you might find a word or phrase displayed in
4599 inverse text and others displayed in bold typeface. Such words and
4600 phrases are used to tell you Alpine has more information available on
4601 the topic they describe.
4602 The inverted text is the "selected" topic.
4603 Use the arrow keys, Ctrl-F, and Ctrl-B to change which of the phrases
4604 displayed in bold type
4605 is "selected".
4606 Hit the Return key to display the information Alpine has available on that
4607 topic. While viewing such additional information, the
4608 <!--chtml if pinemode="function_key"-->
4609 F3 function
4610 <!--chtml else-->
4611 "P"
4612 <!--chtml endif-->
4613 key will return you to the previous help screen, and the
4614 <!--chtml if pinemode="function_key"-->
4615 F2 function
4616 <!--chtml else-->
4617 "E"
4618 <!--chtml endif-->
4619 key will Exit the Help system altogether.
4621 <P>
4622 The "N" command will tell you the internal name of the help text you are
4623 reading each time, so that you can send this name in the text of a message
4624 and create a direct link to that internal help using the x-pine-help URL
4625 scheme. For example, the direct link to this item is
4626 x-pine-help:h_special_help_nav. If you add this text to a message, then
4627 a person using Pine to read such message would have a direct link to this
4628 help text.
4630 <P>
4631 When you are finished reading this help text, you can press the
4632 <!--chtml if pinemode="function_key"-->
4633 F3 function
4634 <!--chtml else-->
4635 "P"
4636 <!--chtml endif-->
4637 key to return to the previously displayed help text.
4639 <P>
4640 <End of help on this topic>
4641 </BODY>
4642 </HTML>
4643 ============= h_special_list_commands =============
4644 <HTML>
4645 <HEAD>
4646 <TITLE>Email List Commands Explained</TITLE>
4647 </HEAD>
4648 <BODY>
4649 <H1>Email List Commands Explained</H1>
4651 Electonic mail lists provide a way for like-minded users to join in
4652 discussions on topics of interest. The email list itself is
4653 represented by a
4654 single address that participants send messages to when they have
4655 something of interest to share with other members of the list. The
4656 receiving computer then, either automatically or after review by the
4657 list's owner (or moderator), sends a copy of that message to each
4658 member of the list.
4660 <P>
4661 Usually, subscribing and unsubscribing is done by sending requests in
4662 an email message to a special address setup to handle managing list
4663 membership. Often this is the name of the list followed by
4664 <I>-request</I>. This address is almost <EM>never</EM> the same as
4665 the address used to send messages to the list.
4667 <P>
4668 Unfortunately, email list participation commands are more a matter
4669 of convention than standard, and thus may vary from list to list.
4670 Increasingly, list management software is adding information to
4671 the copy of the postings as they're copied to the list members that
4672 explains how to do the various list management functions.
4674 <P>
4675 Alpine will recognize this information and offer the management commands
4676 they represent in a simple display. One or more of the following
4677 operations will be made available:
4679 <DL>
4680 <DT>Help</DT>
4681 <DD>
4682 A method to get help on subscribing, unsubscribing,
4683 an explanation of what the list is about, or special instructions
4684 for participation. This may be in the form of a reply in response
4685 to an email message, or instructions on how to connect to a Web site.
4686 </DD>
4688 <DT>Unsubscribe</DT>
4689 <DD>
4690 A method to get your email addressed removed from the list of
4691 recipients of the email list.
4692 </DD>
4694 <DT>Subscribe</DT>
4695 <DD>
4696 A method to get your email address added to the list of recipients
4697 of the email list. It may be in the form of a message sent to
4698 a special address or you may be connected to a web site.
4699 <DD>
4700 </DD>
4702 <DT>Post</DT>
4703 <DD>
4704 A method used to post to the email list. However, it might also
4705 indicate that no posting is allowed directly to the list.
4706 </DD>
4708 <DT>Owner</DT>
4709 <DD>
4710 A method to contact the list owner for special questions you might
4711 have regarding the list.
4712 </DD>
4714 <DT>Archive</DT>
4715 <DD>
4716 A method to view an archive of previous messages posted to the list.
4717 This may be in the form of a mail folder on a remote computer, an
4718 IMAP mailbox or even a Web site.
4719 </DD>
4720 </DL>
4722 <P>
4723 <End of help on this topic>
4724 </BODY>
4725 </HTML>
4726 ============= h_quota_command =============
4727 <HTML>
4728 <HEAD>
4729 <TITLE>Quota Screen Explained</TITLE>
4730 </HEAD>
4731 <BODY>
4732 <H1>Quota Screen Explained</H1>
4734 <P> This screen summarizes the quota report for this mailbox in the
4735 IMAP server. For each resource that you have a quota, this reports summarizes
4736 its use and limit.
4738 <P> Your IMAP server administrator may have set a quota based either on
4739 the total size of your mailbox (STORAGE), or the number of messages in
4740 your mailbox (MESSAGES), or some other criteria. This will be reported
4741 to you indicating the type of quota, its total use and its limit.
4743 <P> The report for STORAGE is reported in kibibytes (KiB). One kibibyte is
4744 1024 bytes. Each of the characters that you see in this help text is one
4745 byte, and this help text is about 1 kibibyte in size. Small messages sent
4746 by Alpine are normally less than 4 kibibytes in size (which includes
4747 headers and text). Other email programs may send messages with bigger
4748 sizes when they send messages, since they send plain text and an
4749 alternative part in HTML.
4751 <P> A convenient way to save space for the STORAGE type of quota is by
4752 deleting attachments. This is done on each individual message by pressing
4753 the "V" command while reading the message text, then moving the cursor
4754 to the position of the attachment that is to be deleted, then pressing
4755 "D" to delete such attachment, going back to reading the
4756 message with the "<" command and pressing "S" to
4757 save the message in the same folder you are reading from. The saved
4758 message will not have the attachment that was marked deleted. Now you
4759 can delete and expunge the message with the unwanted attachment.
4761 <P>
4762 <End of help on this topic>
4763 </BODY>
4764 </HTML>
4765 ============= h_mail_thread_index =============
4766 <HTML>
4767 <HEAD>
4768 <TITLE>THREAD INDEX COMMANDS</TITLE>
4769 </HEAD>
4770 <BODY>
4771 <H1>THREAD INDEX COMMANDS</H1>
4772 <!--chtml if pinemode="function_key"-->
4773 Available Commands -- Group 1 Available Commands -- Group 2<BR>
4774 ------------------------------- -----------------------------<BR>
4775 F1 Show Help Text F1 Show Help Text<BR>
4776 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
4777 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
4778 F4 View current thread F4 Quit Alpine<BR>
4779 F5 Move to previous thread F5 <A HREF="h_common_compose">Compose</A> a message<BR>
4780 F6 Move to next thread F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
4781 F7 Show previous screen F7 <A HREF="h_common_nextnew">Next new</A> thread<BR>
4782 F8 Show next screen F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
4783 F9 <A HREF="h_common_delete">Mark thread for deletion</A> F9 <A HREF="h_common_print">Print</A> index<BR>
4784 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
4785 F11 <A HREF="h_common_reply">Reply</A> to thread F11 <A HREF="h_common_save">Save</A> messages into an email folder<BR>
4786 F12 <A HREF="h_common_reply">Forward</A> messages F12 <A HREF="h_common_save">Export</A> messages into a plain file<BR>
4787 <BR>
4788 Available Commands -- Group 3<BR>
4789 -----------------------------<BR>
4790 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>
4791 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>
4792 F6 F9 <A HREF="h_common_hdrmode">Full Header Mode</A> F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
4793 <BR>
4794 Available Commands -- Group 4<BR>
4795 -----------------------------<BR>
4796 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
4797 F6 <A HREF="h_common_role">Compose using a role</A><BR>
4798 <BR>
4799 <!--chtml else-->
4800 Navigating the List of Threads Operations on the Current Thread<BR>
4801 ------------------------------- ---------------------------------<BR>
4802 P Move to the previous thread > View Thread % <A HREF="h_common_print">Print</A><BR>
4803 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>
4804 - Show previous screen D <A HREF="h_common_delete">Mark thread for deletion</A><BR>
4805 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
4806 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>
4807 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>
4808 specific thread E <A HREF="h_common_save">Export</A> as a plain text file<BR>
4809 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>
4810 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
4811 <BR>
4812 Miscellaneous Operations General Alpine Commands<BR>
4813 ------------------------ ---------------------<BR>
4814 G <A HREF="h_common_goto">Goto</A> a specified folder O Show all other available commands<BR>
4815 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ? Show Helptext Q Quit Alpine<BR>
4816 H <A HREF="h_common_hdrmode">Full header mode</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
4817 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> C <A HREF="h_common_compose">Compose</A> a new message<BR>
4818 Z <A HREF="h_index_cmd_zoom">Zoom</A> # <A HREF="h_common_role">Compose using a role</A><BR>
4819 ; <A HREF="h_index_cmd_select">Select</A> A <A HREF="h_index_cmd_apply">Apply</A> L COLLECTION LIST Screen<BR>
4820 : Select Messages in Current Thread<BR>
4821 <!--chtml endif-->
4822 <P>
4824 NOTE:
4825 <OL>
4826 <LI>For help on a particular command, highlight the bold text associated
4827 with it above and hit Return.
4828 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
4829 </OL>
4831 <H2>Description of the THREAD INDEX Screen</H2>
4833 The THREAD INDEX displays summary information from each
4834 thread (conversation) in the current folder.
4835 This is useful if you want to quickly
4836 scan new threads, or find a particular thread without having to go
4837 through the text of each message, or to quickly get rid of junk
4838 threads, etc.
4839 The current thread is always highlighted.
4840 Each line of the THREAD INDEX contains the following columns: <P>
4841 <DL>
4842 <DT>STATUS:</DT>
4843 <DD> The markings on the left side of the thread tell you about its
4844 status. You may see one or more of the following codes on any given
4845 thread:
4846 <UL>
4847 <LI> "D" for Deleted. All of the messages in this thread are marked for deletion but not yet eXpunged from the folder.
4848 <LI> "A" for Answered. All of the messages in this thread are marked answered.
4849 <LI> "N" for New. At least one message in the thread is New (you haven't looked at it yet).
4850 <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.
4851 <LI> "-" for cc-to-you. The "-" indicates that a
4852 message in the thread was sent to you as a cc:. This symbol will only show up if
4853 the feature
4854 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
4855 <LI> "X" for selected. You have selected at least one message in the thread by using the
4856 "select" command. (Some systems may optionally allow selected
4857 messages to be denoted by the index line being displayed in bold
4858 type instead.)
4859 <LI> "*" for Important. You have previously used the "Flag" command
4860 to mark at least one message in this thread as "important".
4861 </UL></DD><P>
4863 <DT>THREAD NUMBER:</DT>
4864 <DD>Threads in a folder are numbered, from one through the number
4865 of threads in the folder, to help you know where you are in the folder.
4866 </DD><P>
4868 <DT>DATE STARTED:</DT>
4869 <DD>The date the thread was started. This is actually from the Date header
4870 of the first message in the thread. It doesn't take different time zones
4871 into account.</DD><P>
4873 <DT>WHO STARTED THE THREAD:</DT>
4874 <DD>This is usually the name of the sender of the first message in the thread, taken from
4875 the From header of the message.
4876 If there is no personal name given in that
4877 address, then the email address is used instead.
4878 If the message is from you (or from one of your
4879 <A HREF="h_config_alt_addresses">alternate addresses</A>),
4880 then the recipient's name is shown here instead, with the characters
4881 "To: " inserted before the name.
4882 (The idea of this is that if you started the thread you would rather see who
4883 the mail was sent to instead of that the mail was from you.)
4884 In Newsgroups, if you are
4885 the sender and there are no email recipients, the newsgroup name will be
4886 listed after the "To: ".
4887 </DD><P>
4889 <DT>SIZE:</DT>
4890 <DD>The number in parentheses is the number of messages in the thread.</DD><P>
4892 <DT>SUBJECT:</DT>
4893 <DD>As much of the thread's subject line as will fit on the screen.
4894 This is the subject of the first message in the thread.</DD>
4895 </DL>
4897 <P><UL>
4898 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
4899 </UL>
4900 <P>
4901 <End of help on this topic>
4902 </BODY>
4903 </HTML>
4904 ============= h_mail_index =============
4905 <HTML>
4906 <HEAD>
4907 <TITLE>MESSAGE INDEX COMMANDS</TITLE>
4908 </HEAD>
4909 <BODY>
4910 <H1>MESSAGE INDEX COMMANDS</H1>
4911 <!--chtml if pinemode="function_key"-->
4912 Available Commands -- Group 1 Available Commands -- Group 2<BR>
4913 ------------------------------- -----------------------------<BR>
4914 F1 Show Help Text F1 Show Help Text<BR>
4915 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
4916 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
4917 F4 View current message F4 Quit Alpine<BR>
4918 F5 Move to previous message F5 <A HREF="h_common_compose">Compose</A> a message<BR>
4919 F6 Move to next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
4920 F7 Show previous screen of messages F7 <A HREF="h_common_nextnew">Next new</A> message<BR>
4921 F8 Show next screen of messages F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
4922 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
4923 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
4924 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
4925 F12 <A HREF="h_common_reply">Forward</A> message F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
4926 <BR>
4927 Available Commands -- Group 3<BR>
4928 -----------------------------<BR>
4929 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>
4930 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>
4931 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>
4932 <BR>
4933 Available Commands -- Group 4<BR>
4934 -----------------------------<BR>
4935 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
4936 F6 <A HREF="h_common_role">Compose using a role</A> F10 <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread<BR>
4937 <BR>
4938 <!--chtml else-->
4939 Navigating the List of Messages Operations on the Current Message<BR>
4940 ------------------------------- ---------------------------------<BR>
4941 P Move to the previous message > View % <A HREF="h_common_print">Print</A><BR>
4942 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>
4943 - Show previous screen of messages D <A HREF="h_common_delete">Mark for deletion</A><BR>
4944 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
4945 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>
4946 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>
4947 specific message E <A HREF="h_common_save">Export</A> as a plain text file<BR>
4948 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>
4949 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
4950 Miscellaneous Operations<BR>
4951 ------------------------<BR>
4952 G <A HREF="h_common_goto">Goto</A> a specified folder General Alpine Commands<BR>
4953 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ---------------------<BR>
4954 H <A HREF="h_common_hdrmode">Full header mode</A> O Show all other available commands<BR>
4955 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> ? Show Help text Q Quit Alpine<BR>
4956 Z <A HREF="h_index_cmd_zoom">Zoom</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
4957 ; <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>
4958 : Select Current message # <A HREF="h_common_role">Compose using a role</A><BR>
4959 / <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread L COLLECTION LIST Screen<BR>
4960 <!--chtml endif-->
4961 <P>
4963 NOTE:
4964 <OL>
4965 <LI>For help on a particular command, highlight the bold text associated
4966 with it above and hit Return.
4967 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
4968 </OL>
4970 <H2>Description of the MESSAGE INDEX Screen</H2>
4972 The MESSAGE INDEX displays summary information from each
4973 message in the current folder.
4974 This is useful if you want to quickly
4975 scan new messages, or find a particular message without having to go
4976 through the text of each message, or to quickly get rid of junk
4977 messages, etc.
4978 <P>
4979 The current message is always highlighted
4980 and many commands operate on the current message.
4981 For example, the Delete command will delete the current message.
4982 If the folder is sorted by either Threads or OrderedSubject, then, depending
4983 on some of your configuration settings, a single line in the index may
4984 refer to an entire thread or to a subthread.
4985 If that is the case, then the commands that normally operate on the current
4986 message will operate on the thread or subthread instead.
4987 For example, the Delete command will delete the whole collapsed thread
4988 instead of just a single message.
4989 <P>
4990 Each line of the MESSAGE INDEX contains the following columns (by default --
4991 you can change this with the
4992 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
4993 in the SETUP CONFIGURATION screen): <P>
4994 <DL>
4995 <DT>STATUS:</DT>
4996 <DD> The markings on the left side of the message tell you about its
4997 status. You may see one or more of the following codes on any given
4998 message:
4999 <UL>
5000 <LI> "D" for Deleted. You have marked this message for deletion but not
5001 yet eXpunged the folder.
5002 <LI> "N" for New. You have not looked at the text of the message yet.
5003 <LI> "A" for Answered. Any time you reply to a message it is considered
5004 to be answered.
5005 <LI> "F" for Forwarded. Similar to Answered, this is set whenever you
5006 forward a message.
5007 <LI> "+" for direct-to-you. The "+" indicates that a message was sent
5008 directly to your account, your copy is not part of a cc: or a
5009 mailing list.
5010 <LI> "-" for cc-to-you. The "-" indicates that a
5011 message was sent to you as a cc:. This symbol will only show up if
5012 the feature
5013 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
5014 <LI> "X" for selected. You have selected the message by using the
5015 "select" command. (Some systems may optionally allow selected
5016 messages to be denoted by the index line being displayed in bold
5017 type.)
5018 <LI> "*" for Important. You have previously used the "Flag" command
5019 to mark this message as "important".
5020 </UL></DD><P>
5022 <DT>MESSAGE NUMBER:</DT>
5023 <DD>Messages in a folder are numbered, from one through the number
5024 of messages in the folder, to help you know where you are in the folder.
5025 These numbers are always in increasing order, even if you sort the folder
5026 in a different way.</DD><P>
5028 <DT>DATE SENT:</DT>
5029 <DD>The date the message was sent. By default, messages are
5030 ordered by arrival time, not by date sent. Most of the time, arrival time
5031 and date sent (effectively departure time) are similar. Sometimes,
5032 however, the index will appear to be out of order because a message took a
5033 long time in delivery or because the sender is in a different time
5034 zone than you are. This date is just the date from the Date header
5035 field in the message.</DD><P>
5037 <DT>WHO SENT THE MESSAGE:</DT>
5038 <DD>This is usually the name of the sender of the message, taken from
5039 the From header of the message.
5040 If there is no personal name given in that
5041 address, then the email address is used instead.
5042 If the message is from you (or from one of your
5043 <A HREF="h_config_alt_addresses">alternate addresses</A>),
5044 then the recipient's name is shown here instead, with the characters
5045 "To: " inserted before the name.
5046 (The idea of this is that if you sent the mail you would rather see who
5047 the mail was sent to instead of that the mail was from you.
5048 This behavior may be changed by modifying the <!--#echo var="VAR_index-format"--> option mentioned
5049 above.
5050 In particular, use the FROM token or the FROMORTONOTNEWS token
5051 in place of the FROMORTO token.)
5052 In Newsgroups, if you are
5053 the sender and there are no email recipients, the newsgroup name will be
5054 listed after the "To: ". </DD><P>
5056 <DT>SIZE:</DT>
5057 <DD>The number in parentheses is the number of characters in the message.
5058 It may have a suffix of K, M, or G which means the number should be
5059 multiplied by one thousand, one million, or one billion to get the
5060 size of the message.</DD><P>
5062 <DT>SUBJECT:</DT>
5063 <DD>As much of the message's subject line as will fit on the screen.</DD>
5064 </DL>
5066 <P><UL>
5067 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5068 </UL>
5069 <P>
5070 <End of help on this topic>
5071 </BODY>
5072 </HTML>
5073 ============= h_mail_view ========================
5074 <HTML>
5075 <HEAD>
5076 <TITLE>MESSAGE TEXT SCREEN</TITLE>
5077 </HEAD>
5078 <BODY>
5079 <H1>MESSAGE TEXT SCREEN</H1>
5080 <!--chtml if pinemode="function_key"-->
5081 Available Commands -- Group 1 Available Commands -- Group 2<BR>
5082 ------------------------------- ------------------------------<BR>
5083 F1 Show Help Text F1 Show Help Text<BR>
5084 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
5085 F3 <A HREF="h_common_index">MESSAGE INDEX</A> Screen F3 MAIN MENU Screen<BR>
5086 F4 <A HREF="h_view_cmd_viewattch">View attachment</A> F4 Quit Alpine<BR>
5087 F5 Display previous message F5 <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5088 F6 Display next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5089 F7 Previous screen of this message F7 <A HREF="h_common_compose">Compose</A> message<BR>
5090 F8 Next screen of this message F8 <A HREF="h_view_cmd_whereis">Whereis</A><BR>
5091 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
5092 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
5093 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
5094 F12 <A HREF="h_common_reply">Forward</A> F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
5095 <BR>
5096 Available Commands -- Group 3<BR>
5097 ------------------------------<BR>
5098 F1 Show Help Text<BR>
5099 F2 Toggle to see more commands<BR>
5100 F3 <A HREF="h_view_cmd_hilite">View hilited</A><BR>
5101 F4 Select current message<BR>
5102 F5 Previous selectable item<BR>
5103 F6 Next selectable item<BR>
5104 F7 <A HREF="h_common_jump">Jump</A> to message number<BR>
5105 F8 <A HREF="h_common_nextnew">Next new</A> message<BR>
5106 F9 <A HREF="h_common_hdrmode">Display full headers</A><BR>
5107 F10 <A HREF="h_common_bounce">Bounce</A> message<BR>
5108 F11 <A HREF="h_common_flag">Flag</A> message<BR>
5109 F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
5110 Available Commands -- Group 4<BR>
5111 F5 <A HREF="h_common_role">Compose using a role</A><BR>
5112 <!--chtml else-->
5113 Operations on the Current Message<BR>
5114 ---------------------------------<BR>
5115 <BR>
5116 - Show previous page of this msg S <A HREF="h_common_save">Save</A> into an email folder<BR>
5117 Spc (space bar) Show next page E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5118 > <A HREF="h_view_cmd_viewattch">View attachment</A> B <A HREF="h_common_bounce">Bounce</A><BR>
5119 R <A HREF="h_common_reply">Reply</A> to message F <A HREF="h_common_reply">Forward</A> message<BR>
5120 D <A HREF="h_common_delete">Mark for deletion</A> Ret View <A HREF="h_view_cmd_hilite">hilited</A> item<BR>
5121 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>
5122 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>
5123 % <A HREF="h_common_print">Print</A> * <A HREF="h_common_flag">Flag</A> message<BR>
5124 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>
5125 <BR>
5126 Navigating the List of Messages Other Commands<BR>
5127 ------------------------------- ----------------------------<BR>
5128 P Display previous message G <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5129 N Display next message H <A HREF="h_common_hdrmode">Full header mode</A> on/off<BR>
5130 J <A HREF="h_common_jump">Jump</A> to a specific message : Select Current message<BR>
5131 Tab <A HREF="h_common_nextnew">Next new</A> message A <A HREF="h_config_prefer_plain_text">Toggle Prefer Plain Text</A><BR>
5132 <BR>
5133 General Alpine Commands<BR>
5134 ---------------------<BR>
5135 O Show all other available commands<BR>
5136 ? Show Help text Q Quit Alpine<BR>
5137 M MAIN MENU Screen L <A HREF="h_common_folders">FOLDER LIST</A> Screen (or COLLECTION LIST Screen)<BR>
5138 < <A HREF="h_common_index">MESSAGE INDEX</A> Screen C <A HREF="h_common_compose">Compose</A> a new message<BR>
5139 # <A HREF="h_common_role">Compose using a role</A><BR>
5140 <!--chtml endif-->
5141 <P>
5143 NOTE:
5144 <OL>
5145 <LI>For help on a particular command, highlight the bold text associated
5146 with it above and hit Return.
5147 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5148 </OL>
5150 <H2>Description of the MESSAGE TEXT Screen</H2>
5152 The top line of the view message screen displays status
5153 information about the currently open collection and folder and about the
5154 current message. It shows the name of the collection in angle brackets
5155 and then the name of the folder. The line also displays the number
5156 of messages in the folder, the number of the current message and the
5157 percentage of the current message that has been displayed on the screen.
5158 If the message is marked for deletion "DEL" will appear in the upper
5159 right corner.
5160 If the message has been answered (but not deleted) "ANS" will show
5161 in the corner.
5162 <P>
5164 NOTE: to rapidly move to the end of a message, hit the
5165 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5166 (or Ctrl-W) key followed
5167 by Ctrl-V. Similarly,
5168 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5169 followed by Ctrl-Y will take you to the beginning of
5170 a message.
5172 <H2>Explanation of Alternate Character Sets</H2>
5174 Alpine attempts to stay out of the way so that it won't prevent you from
5175 viewing mail in any character set. It will simply send the message to
5176 your display device. If the device is capable of displaying the
5177 message as it was written it will do so. If not, the display may be
5178 partially or totally incorrect.
5179 If the message contains characters that are not representable in your
5180 <A HREF="h_config_char_set">"Display Character Set"</A>
5181 variable in your configuration, then a warning message will be printed
5182 to your screen at the beginning of the message display.
5183 It is probably best to use UNIX Alpine in a terminal emulator
5184 capable of displaying UTF-8 characters.
5185 See <A HREF="h_config_char_set">Display Character Set</A> for a little
5186 more information about character set settings.
5188 <P><UL>
5189 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5190 </UL>
5191 <P>
5192 <End of help on this topic>
5193 </BODY>
5194 </HTML>
5195 ======= h_index_cmd_select =======
5196 <HTML>
5197 <HEAD>
5198 <TITLE>Selecting: Select and WhereIs/Select</TITLE>
5199 </HEAD>
5200 <BODY>
5201 <H1>Selecting: Select and WhereIs/Select</H1>
5203 Aggregate operations give you the ability to process a group of messages
5204 at once. Acting on multiple messages requires two steps: (1) selecting a
5205 set of messages and then; (2) applying a command to that set. The first
5206 part is handled by the select command. Select allows you to
5207 select messages based on their status (read, answered, etc.), contents,
5208 date, size, or keywords.
5209 You may also select based on one of your Rules or based on threads,
5210 and there are quick options to select a specific message or range of messages,
5211 to select the current message, or to select all messages.
5212 <P>
5214 We describe the various selection criteria briefly:
5215 <P>
5217 <DL>
5218 <DT>select All</DT>
5219 <DD> Marks all the messages in the folder as selected.
5220 </DD>
5222 <DT>select Cur</DT>
5223 <DD> Selects the currently highlighted message or currently highlighted
5224 set of messages if in a threaded view.
5225 </DD>
5227 <DT>select by Number</DT>
5228 <DD> Select by message number. This may be a comma-separated list instead or
5229 a single entry.
5230 Each element in the list may be either a single message number or a range
5231 of numbers with a dash between the lowest and highest member of the range.
5232 Some examples are 7 to select only message number 7; 2-5 to select messages
5233 2 through 5; and 2-5,7-9,11 to select messages 2, 3, 4, 5, 7, 8, 9, and 11.
5234 The word "end" may be used as a substitute for the highest numbered
5235 message in the folder.
5236 If in a separate thread index where the numbers refer to threads instead of
5237 to messages, then you will be selecting all of the messages in the
5238 referenced threads instead of selecting by message number.
5239 </DD>
5241 <DT>select by Date</DT>
5242 <DD> Select by either the date stored in the Date headers of each message,
5243 or by the date when the messages arrived.
5244 This does not adjust for different time zones, but just checks to see what
5245 day the message was sent on.
5246 You may type in a date. If you do, the date should be in the form
5247 <P><SAMP><CENTER>DD-Mon-YYYY</CENTER></SAMP><P>
5248 For example,
5249 <P><SAMP><CENTER>24-Nov-2004</CENTER></SAMP><P>
5250 or
5251 <P><SAMP><CENTER>09-Nov-2004</CENTER></SAMP><P>
5252 If the date you want is close to the current date, it is probably
5253 easier to use the "^P Prev Day" or "^N Next Day" commands to change the default date that
5254 is displayed, instead of typing in the date yourself.
5255 Or, the "^X Cur Msg" command may be used to fill in
5256 the date of the currently highlighted message.
5257 <P>
5258 There are six possible settings that are selected using the
5259 "^W Toggle When" command.
5260 Three of them select messages based on the Date headers.
5261 They are "SENT SINCE", "SENT BEFORE",
5262 and "SENT ON".
5263 SINCE is all messages with the selected date or later.
5264 BEFORE is all messages earlier than the selected date (not including the day
5265 itself).
5266 ON is all messages sent on the selected date.
5267 The other three select messages in the same way but they use the arrival
5268 times of the messages instead of the Date headers included in the messages.
5269 Those three are "ARRIVED SINCE", "ARRIVED BEFORE",
5270 and "ARRIVED ON".
5271 When you save a message from one folder to another the arrival time is
5272 preserved.
5273 </DD>
5275 <DT>select by Text</DT>
5276 <DD> Selects messages based on the message contents.
5277 This allows you to select a set of messages based on whether or not the
5278 message headers or message body contain specified text.
5279 You may look for text in the Subject, the From header,
5280 the To header, or the Cc header.
5281 You may also choose Recipient, which searches for the text in
5282 either the To or the Cc header;
5283 or Participant, which means To or Cc or From.
5284 Besides those specific header searches, you may also search the entire
5285 header and text of the message with "All Text", or just the
5286 body of the message.
5287 <P>
5288 To search for the absence of text, first type the "! Not" command
5289 before typing the specific type of text search.
5290 For example, you could type "!" followed by "S" to
5291 search for all messages that do not contain a particular word in their
5292 Subjects.
5293 <P>
5294 If you choose a Subject search, you may use the subject from the current
5295 message by typing the "^X Cur Subject" command.
5296 You may then edit it further if you wish.
5297 For example, you might select the subject of a reply and edit the
5298 "Re: " off of the front of it in order to search for
5299 the original message being replied to.
5300 All of the other header searches allow you to use addresses from the
5301 headers of the current message if you want to.
5302 You may use the "^T Cur To", "^R Cur From", or
5303 "^W Cur Cc".
5304 In each case, if there is more than one address, only the first is offered.
5305 </DD>
5307 <DT>select by Status</DT>
5308 <DD> Selects messages based on their status.
5309 You may select all New, Important, Deleted, Answered, Recent, or Unseen
5310 messages.
5311 Or, if you first type the "! Not" command, you get not New,
5312 or not Important, and so on.
5313 If you select Deleted messages, you will get all messages with their
5314 Deleted flag set.
5315 Likewise for Important messages, all messages that you have flagged as
5316 being Important with the
5317 <A HREF="h_common_flag">Flag</A> command.
5318 The "New" and "Answered" choices are a little bit odd
5319 because they try to match what you see on the screen by default.
5320 "New" is a shorthand for messages that are Unseen, Undeleted,
5321 and Unanswered.
5322 If you have looked at the message, or deleted it, or answered it; then it
5323 is not considered "New ".
5324 "! New" is the opposite of "New".
5325 <P>
5326 "Answered" is another one that is a little different.
5327 It means that the message has been Answered <EM>and</EM> is not deleted.
5328 And to make it even more confusing, "! Answered" is not
5329 the opposite of "Answered"!
5330 Instead, "! Answered" stands for messages that are
5331 both Unanswered <EM>and</EM> not deleted.
5332 <P>
5333 The other two types were added later because the special nature of the
5334 New flag was not what was wanted by all users.
5335 New does match what you see in the index by default, but if you use
5336 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5337 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5338 be exactly what you want.
5339 "Unseen" simply selects all unseen messages, whether or not
5340 they are deleted or answered, and
5341 "Recent" selects all of the messages that have been added to
5342 the folder since you started this Alpine session.
5343 (That's not technically quite true. If there are multiple mail clients
5344 reading an IMAP mailbox, each message will be marked as Recent in only
5345 one of the client's sessions.)
5346 </DD>
5348 <DT>select by siZe</DT>
5349 <DD> Selects messages based on their size being smaller than or larger
5350 than the size you specify.
5351 The size is the number of bytes.
5352 You may use the suffix "K" or "k" to mean 1,000 times
5353 the number.
5354 For example, 7K is the same as 7000.
5355 The suffix "M" or "m" means 1,000,000 times the number,
5356 and the suffix "G" or "g" means 1,000,000,000 times.
5357 Use the "^W" command to toggle back and forth between Smaller
5358 and Larger.
5359 </DD>
5361 <DT>select by Keyword</DT>
5362 <DD> Selects messages that either have or do not have
5363 (using the "! Not" command)
5364 a particular <A HREF="h_config_keywords">Keyword</A> set.
5365 One way to select a keyword is to use the "^T To List"
5366 command to select one from your list of keywords.
5367 The
5368 <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.
5369 </DD>
5371 <DT>select by Rule</DT>
5372 <DD> Selects messages that either match or don't match
5373 (using the "! Not" command)
5374 one of the Rules you have defined.
5375 The most likely method of filling in the Rule is to use the
5376 "^T To List"
5377 command to select one of your Rules.
5378 All of the Rules you have defined will be in the list, including
5379 Rules for Searching, Indexcolors, Filtering, Roles, Score setting, and Other.
5380 They may not all make sense for this purpose, but they are all there for
5381 flexibility.
5382 You might find it useful to define some rules solely for the purpose
5383 of being used by the Select command.
5384 There is a special category for such Rules. They are called Search Rules.
5385 <P>
5386 Unfortunately, Alpine does not allow all possible Rules to be defined.
5387 For example, there is no logical OR operation.
5388 OR is accomplished in the Filter Rules or the other types of Rules by
5389 simply defining two rules, one that matches the first part of the OR
5390 and another that matches the second part.
5391 But you can't do that here, since you only have a single Rule to work with.
5392 Likewise, the order of Rules is usually important.
5393 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5394 a message, then that stops the search for a further match.
5395 This means that you may be confused if you try to use Select by Rule to
5396 check your Filter rules because the order is important when filtering but
5397 is not considered here.
5398 </DD>
5400 <DT>select by tHread</DT>
5401 <DD> Selects all of the messages in the current thread.
5402 </DD>
5403 </DL>
5405 After you have an initial selection, the next and subsequent selection
5406 commands modify the selection.
5407 The select command changes. It first gives
5408 you selection "alteration" options: "unselect All",
5409 "unselect Current",
5410 "Broaden selection" (implements a logical OR), and
5411 "Narrow selection" (implements a logical AND).
5412 After you choose either Broaden or Narrow, you then choose one of the
5413 selection criteria listed above (by Text or Number or ...).
5414 You may use select as many times as you wish to get the selected set right.
5415 <P>
5417 The WhereIs command has a feature (Ctrl-X) to
5418 select all the messages that match the WhereIs search. WhereIs searches
5419 through just the text that appears on the MESSAGE INDEX screen.
5420 This method is often slower than using the select command itself, unless the
5421 line you are looking for is not too far away in the index.
5422 <P>
5424 The availability of the aggregate operations commands is determined by the
5425 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
5426 Feature-List option in your Alpine
5427 configuration, which defaults to set.
5428 The features
5429 <A HREF="h_config_auto_zoom">"<!--#echo var="FEAT_auto-zoom-after-select"-->"</A>
5430 and
5431 <A HREF="h_config_select_wo_confirm">"<!--#echo var="FEAT_select-without-confirm"-->"</A>
5432 affect the behavior of the Select command.
5434 <P>
5435 <End of help on this topic>
5436 </BODY>
5437 </HTML>
5438 ======= h_select_rule =======
5439 <HTML>
5440 <HEAD>
5441 <TITLE>Select: Rule</TITLE>
5442 </HEAD>
5443 <BODY>
5444 <H1>Select: Rule</H1>
5446 You are selecting messages that either match or don't match
5447 one of the Rules you have defined.
5448 You may either type the nickname of the Rule at the prompt, or use the
5449 "^T To List"
5450 command to select one of your Rules.
5451 All of the Rules you have defined will be in the list, including
5452 Rules for Indexcolors, Filtering, Roles, Score setting, and Other.
5453 They may not all make sense for this purpose, but they are all there for
5454 flexibility.
5455 Rules may be added by using the Setup/Rules screen off of the main Alpine
5456 menu.
5457 <P>
5458 Unfortunately, Alpine does not allow all possible Rules to be defined.
5459 For example, there is no logical OR operation.
5460 OR is accomplished in the Filter Rules or the other types of Rules by
5461 simply defining two rules, one that matches the first part of the OR
5462 and another that matches the second part.
5463 But you can't do that here, since you only have a single Rule to work with.
5464 Likewise, the order of Rules is usually important.
5465 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5466 a message, then that stops the search for a further match.
5467 This means that you may be confused if you try to use Select by Rule to
5468 check your Filter rules because the order is important when filtering but
5469 is not considered here.
5471 <P>
5472 <End of help on this topic>
5473 </BODY>
5474 </HTML>
5475 ======= h_select_text =======
5476 <HTML>
5477 <HEAD>
5478 <TITLE>Select: Text</TITLE>
5479 </HEAD>
5480 <BODY>
5481 <H1>Select: Text</H1>
5483 You are selecting messages based on the contents of the message.
5484 This allows you to select a set of messages based on whether or not the
5485 message headers or message body contain specified text.
5486 You may look for text in the Subject, the From header,
5487 the To header, or the Cc header.
5488 You may also choose Recipient, which searches for the text in
5489 either the To or the Cc header;
5490 or Participant, which means either the To header, or the Cc header,
5491 or the From header.
5492 Besides those specific header searches, you may also search the entire
5493 header and text of the message with "All Text", or just the
5494 body of the message with "Body".
5495 <P>
5496 To search for the absence of text, first type the "! Not" command
5497 before typing the specific type of text search.
5498 For example, you could type "!" followed by "S" to
5499 search for all messages that do not contain a particular word in their
5500 Subjects.
5501 <P>
5502 If you choose a Subject search, you may use the subject from the current
5503 message by typing the "^X Cur Subject" command.
5504 You may then edit it further if you wish.
5505 For example, you might select the subject of a reply and edit the
5506 "Re: " off of the front of it in order to search for
5507 the original message being replied to.
5508 All of the other header searches allow you to use addresses from the
5509 headers of the current message if you want to.
5510 You may use the "^T Cur To", "^R Cur From", or
5511 "^W Cur Cc".
5512 In each case, if there is more than one address, only the first is offered.
5514 <P>
5515 <End of help on this topic>
5516 </BODY>
5517 </HTML>
5518 ======= h_select_status =======
5519 <HTML>
5520 <HEAD>
5521 <TITLE>Select: Status</TITLE>
5522 </HEAD>
5523 <BODY>
5524 <H1>Select: Status</H1>
5526 You are selecting messages based on the status of the message.
5527 For example, whether or not the message has been marked Deleted or Important,
5528 or whether or not it has been Answered or is New.
5529 If you first type the "! Not" command, you will get the
5530 opposite: not Deleted, not Important, and so on.
5531 <P>
5532 If you select Deleted messages, you will get all messages with their
5533 Deleted flag set.
5534 Likewise for Important messages, all messages that you have flagged as
5535 being Important with the
5536 <A HREF="h_common_flag">Flag</A> command.
5537 The "New" and "Answered" choices are a little bit odd
5538 because they try to match what you see on the screen by default.
5539 "New" is a shorthand for messages that are Unseen, Undeleted,
5540 and Unanswered.
5541 If you have looked at the message, or deleted it, or answered it; then it
5542 is not considered "New ".
5543 "! New" is the opposite of "New".
5544 <P>
5545 "Answered" is another one that is a little different.
5546 It means that the message has been Answered <EM>and</EM> is not deleted.
5547 And to make it even more confusing, "! Answered" is not
5548 the opposite of "Answered"!
5549 Instead, "! Answered" stands for messages that are
5550 both Unanswered <EM>and</EM> not deleted.
5551 <P>
5552 (The New and Answered options may seem counter-intuitive.
5553 The reason it is done this way is
5554 because, by default, a Deleted message will show up with the "D"
5555 symbol in the MAIL INDEX screen even if it is New or Answered.
5556 The Delete symbol overrides the New and Answered symbols, because you
5557 usually don't care about the message anymore once you've deleted it.
5558 Similarly, you usually only care about whether a message is Answered or
5559 not if it is not Deleted.
5560 Once it is Deleted you've put it out of your mind.)
5561 <P>
5562 The other two options were added later because the special nature of the
5563 New flag was not what was wanted by all users.
5564 New does match what you see in the index by default, but if you use
5565 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5566 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5567 be exactly what you expect.
5568 "Unseen" simply selects all unseen messages, whether or not
5569 they are deleted or answered, and
5570 "Recent" selects all of the messages that have been added to
5571 the folder since you started this Alpine session.
5572 (That's not technically quite true. If there are multiple mail clients
5573 reading an IMAP mailbox, each message will be marked as Recent in only
5574 one of the client's sessions.
5575 That behavior can be convenienent for some purposes, like filtering, but
5576 it isn't usually what you expect when selecting.)
5578 <P>
5579 <End of help on this topic>
5580 </BODY>
5581 </HTML>
5582 ======= h_index_cmd_apply =======
5583 <HTML>
5584 <HEAD>
5585 <TITLE>Apply Command</TITLE>
5586 </HEAD>
5587 <BODY>
5588 <H1>Apply Command</H1>
5590 Apply
5591 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->A<!--chtml endif-->)
5592 is the second step of most aggregate operations. Apply
5593 becomes active any time there is a defined set of selected messages. The
5594 following commands can be applied to a selected message set: delete,
5595 undelete, reply, forward,
5596 <!--chtml if pinemode="os_windows"-->
5597 <!--chtml else-->
5598 pipe,
5599 <!--chtml endif-->
5600 print, take address, save, export, bounce, and flag.
5601 <P>
5603 The behavior of some of these commands in an aggregate sense is not easy to
5604 explain. Try them out to see what they do.
5605 The feature
5606 <A HREF="h_config_auto_unzoom">"<!--#echo var="FEAT_auto-unzoom-after-apply"-->"</A>
5607 affects the behavior of the Apply command, as does the feature
5608 <A HREF="h_config_auto_unselect">"<!--#echo var="FEAT_auto-unselect-after-apply"-->"</A>.
5610 <P>
5611 <End of help on this topic>
5612 </BODY>
5613 </HTML>
5614 ======= h_index_cmd_zoom =======
5615 <HTML>
5616 <HEAD>
5617 <TITLE>ZoomMode Command</TITLE>
5618 </HEAD>
5619 <BODY>
5620 <H1>ZoomMode Command</H1>
5622 Another action you might want to take on a set of selected messages is to
5623 zoom in on them. Like apply, zoom only becomes active when messages have
5624 been selected.
5625 ZoomMode
5626 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->Z<!--chtml endif-->)
5627 is a toggle command that allows you to
5628 zoom-in (and only see the selected messages) and zoom-out (to see all
5629 messages in the folder). Neither apply nor zoom removes the markings that
5630 define the selected set; you need to use a select command in order
5631 to do that.
5633 <P>
5634 <End of help on this topic>
5635 </BODY>
5636 </HTML>
5637 ======= h_index_collapse_expand =======
5638 <HTML>
5639 <HEAD>
5640 <TITLE>Collapse/Expand Command</TITLE>
5641 </HEAD>
5642 <BODY>
5643 <H1>Collapse/Expand Command</H1>
5645 The Collapse/Expand command is only available from the MESSAGE INDEX screen when
5646 the folder is sorted by either Threads or OrderedSubject, and the
5647 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
5648 is set to something other than "none".
5649 By default, this command collapses or expands the subthread that starts at
5650 the currently highlighted message, if any.
5651 If the subthread is already collapsed, then this command expands it.
5652 If the subthread is expanded, then this command collapses it.
5653 If there are no more messages below the current message in the
5654 thread tree (that is, there are no replies to the current message) then
5655 this command does nothing.
5657 <P>
5658 The behavior of this command is affected by the option
5659 <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>.
5660 Normally, this command Collapses or Expands the subthread that
5661 starts at the currently highlighted message.
5662 If the above option is set, then this command Collapses or Expands the
5663 entire current thread instead of just the subthread.
5664 The current thread is simply the top-level thread that contains the
5665 current message.
5667 <P>
5668 <End of help on this topic>
5669 </BODY>
5670 </HTML>
5671 ======= h_index_cmd_sort =======
5672 <HTML>
5673 <HEAD>
5674 <TITLE>Sort Command</TITLE>
5675 </HEAD>
5676 <BODY>
5677 <H1>Sort Command</H1>
5679 In Alpine's generic configuration, messages are presented in the order in
5680 which they arrive. This default can be changed in the SETUP CONFIGURATION
5681 with the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
5682 You can also re-sort the folder on demand with the sort
5683 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
5684 command.
5685 Your sorting options are:
5686 <P>
5687 <UL>
5688 <LI> <A HREF="h_index_sort_arrival">A</A>rrival
5689 <LI> <A HREF="h_index_sort_date">D</A>ate
5690 <LI> <A HREF="h_index_sort_subj">S</A>ubject
5691 <LI> <A HREF="h_index_sort_ordsubj">O</A>rderedSubject
5692 <LI> t<A HREF="h_index_sort_thread">H</A>read
5693 <LI> <A HREF="h_index_sort_from">F</A>rom
5694 <LI> si<A HREF="h_index_sort_size">Z</A>e
5695 <LI> scor<A HREF="h_index_sort_score">E</A>,
5696 <LI> <A HREF="h_index_sort_to">T</A>o
5697 <LI> <A HREF="h_index_sort_cc">C</A>c
5698 </UL>
5700 <P>
5701 The Reverse option will toggle the order the index is currently
5702 sorted by, but will not change the relative sort order.
5704 <P>
5705 Sorting a folder does not actually rearrange the way the folder is saved,
5706 it just re-arranges how the messages are presented to you. This means
5707 that Alpine has to do the work of sorting every time you change sort order.
5708 Sometimes, especially with PC-Alpine or with large folders, this could take
5709 a while.
5711 <P>
5712 <End of help on this topic>
5713 </BODY>
5714 </HTML>
5715 ======= h_index_sort_default =======
5716 <HTML>
5717 <HEAD>
5718 <TITLE>SORT OPTION: Default</TITLE>
5719 </HEAD>
5720 <BODY>
5721 <H1>SORT OPTION: Default</H1>
5723 The <EM>Default</EM> sort option just means to use the default sort order
5724 set in the
5725 <li><a href="h_config_sort_key"><!--#echo var="VAR_sort-key"--></a>
5726 option in Setup/Config.
5728 <P>
5729 <End of help on this topic>
5730 </BODY>
5731 </HTML>
5732 ======= h_index_sort_arrival =======
5733 <HTML>
5734 <HEAD>
5735 <TITLE>SORT OPTION: Arrival</TITLE>
5736 </HEAD>
5737 <BODY>
5738 <H1>SORT OPTION: Arrival</H1>
5740 The <EM>Arrival</EM> sort option arranges messages in the MESSAGE INDEX
5741 in the order that they exist in the folder. This is usually the same as the
5742 order in which they arrived. This option is comparable to not sorting
5743 the messages at all.
5745 <P>
5746 <End of help on this topic>
5747 </BODY>
5748 </HTML>
5749 ======= h_index_sort_date =======
5750 <HTML>
5751 <HEAD>
5752 <TITLE>SORT OPTION: Date</TITLE>
5753 </HEAD>
5754 <BODY>
5755 <H1>SORT OPTION: Date</H1>
5757 The <EM>Date</EM> sort option arranges messages in the MESSAGE INDEX
5758 according to the date and time they were
5759 sent.
5761 <P>
5762 On a folder like INBOX, sorting by "Date" should be almost
5763 identical to sorting by "Arrival".
5765 <P>
5766 <End of help on this topic>
5767 </BODY>
5768 </HTML>
5769 ======= h_index_sort_subj =======
5770 <HTML>
5771 <HEAD>
5772 <TITLE>SORT OPTION: Subject</TITLE>
5773 </HEAD>
5774 <BODY>
5775 <H1>SORT OPTION: Subject</H1>
5777 The <EM>Subject</EM> sort option arranges messages in the MESSAGE INDEX
5778 by subject.
5780 <P>
5781 Messages with the same subject are
5782 first grouped together, and then the groups of like-subject messages
5783 are arranged alphabetically.
5785 <P>
5786 Alpine ignores leading "Re:" and
5787 "re:" and trailing "(fwd)" when determining the
5788 likeness and alphabetical order of subject lines.
5790 <P>
5791 <End of help on this topic>
5792 </BODY>
5793 </HTML>
5794 ======= h_index_sort_ordsubj =======
5795 <HTML>
5796 <HEAD>
5797 <TITLE>SORT OPTION: OrderedSubject</TITLE>
5798 </HEAD>
5799 <BODY>
5800 <H1>SORT OPTION: OrderedSubject</H1>
5802 The <EM>OrderedSubject</EM> sort option arranges messages in the
5803 MESSAGE INDEX by grouping all messages with the same subject
5804 together, similar to sort by <A HREF="h_index_sort_subj">S</A>ubject.
5806 <P>
5807 However, <EM>OrderedSubj</EM> then arranges the groups of like-subject
5808 messages by the date of the oldest message in the group.
5810 <P>
5811 This sort method provides for pseudo threading of conversations within
5812 a folder.
5813 You may want to try sorting by Thread instead.
5815 <P>
5816 <End of help on this topic>
5817 </BODY>
5818 </HTML>
5819 ======= h_index_sort_thread =======
5820 <HTML>
5821 <HEAD>
5822 <TITLE>SORT OPTION: Thread</TITLE>
5823 </HEAD>
5824 <BODY>
5825 <H1>SORT OPTION: Thread</H1>
5827 The <EM>Thread</EM> sort option arranges messages in the
5828 MESSAGE INDEX by grouping all messages that indicate
5829 they are part of a conversation (discussion thread) taking
5830 place within a mailbox or newsgroup. This indication is
5831 based on information in the message's header -- specifically
5832 its <tt>References:</tt>, <tt>Message-ID:</tt>, and <tt>Subject:</tt> fields.
5834 <P>
5835 <End of help on this topic>
5836 </BODY>
5837 </HTML>
5838 ======= h_index_sort_from =======
5839 <HTML>
5840 <HEAD>
5841 <TITLE>SORT OPTION: From</TITLE>
5842 </HEAD>
5843 <BODY>
5844 <H1>SORT OPTION: From</H1>
5846 The <EM>From</EM> sort option arranges messages in the MESSAGE INDEX
5847 by the name of the author of the message.
5849 <P>
5850 Messages with the same author are grouped together. Groups of
5851 messages are then put into alphabetical order according to message
5852 author.
5854 <P>
5855 <End of help on this topic>
5856 </BODY>
5857 </HTML>
5858 ======= h_index_sort_size =======
5859 <HTML>
5860 <HEAD>
5861 <TITLE>SORT OPTION: Size</TITLE>
5862 </HEAD>
5863 <BODY>
5864 <H1>SORT OPTION: Size</H1>
5866 The <EM>Size</EM> sort option arranges messages in the MESSAGE INDEX
5867 by their relative sizes.
5869 <P>
5870 <End of help on this topic>
5871 </BODY>
5872 </HTML>
5873 ======= h_index_sort_score =======
5874 <HTML>
5875 <HEAD>
5876 <TITLE>SORT OPTION: Score</TITLE>
5877 </HEAD>
5878 <BODY>
5879 <H1>SORT OPTION: Score</H1>
5881 The <EM>Score</EM> sort option arranges messages in the MESSAGE INDEX
5882 by their scores.
5884 <P>
5885 Messages with the same score are sorted in arrival order.
5886 Scores are something you create using the
5887 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
5889 <P>
5890 <End of help on this topic>
5891 </BODY>
5892 </HTML>
5893 ======= h_index_sort_to =======
5894 <HTML>
5895 <HEAD>
5896 <TITLE>SORT OPTION: To</TITLE>
5897 </HEAD>
5898 <BODY>
5899 <H1>SORT OPTION: To</H1>
5901 The <EM>To</EM> sort option arranges messages in the MESSAGE INDEX
5902 by the names of the recipients of the message.
5904 <P>
5905 Messages with the same recipients are grouped together. Groups of
5906 messages are then put into alphabetical order according to message
5907 recipients.
5909 <P>
5910 <End of help on this topic>
5911 </BODY>
5912 </HTML>
5913 ======= h_index_sort_cc =======
5914 <HTML>
5915 <HEAD>
5916 <TITLE>SORT OPTION: Cc</TITLE>
5917 </HEAD>
5918 <BODY>
5919 <H1>SORT OPTION: Cc</H1>
5921 The <EM>Cc</EM> sort option arranges messages in the MESSAGE INDEX by
5922 the names of the carbon copy addresses of the message.
5924 <P>
5925 <End of help on this topic>
5926 </BODY>
5927 </HTML>
5928 ======= h_index_cmd_whereis =======
5929 <HTML>
5930 <HEAD>
5931 <TITLE>WhereIs Command</TITLE>
5932 </HEAD>
5933 <BODY>
5934 <H1>WhereIs Command</H1>
5936 The WhereIs
5937 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
5938 command lets you search the MESSAGE INDEX for a word.
5939 It scans through whatever you see, usually the name of the author
5940 and the Subject line.
5941 WhereIs has special subcommands to let you find the beginning of the
5942 index (Ctrl-Y -- first message)
5943 or the end of the index (Ctrl-V -- last message).
5944 <P>
5945 Note that WhereIs only searches through the visible text on the screen.
5946 For example, if only part of the Subject of a message is shown because it
5947 is long, then only the visible portion of the Subject is searched.
5948 Also note that WhereIs does not "see" the
5949 "X" in column one of Index entries for selected messages
5950 so it can't be used to search for
5951 selected messages (use "Zoom" instead).
5952 <P>
5953 If the feature
5954 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
5955 is turned on,
5956 WhereIs can also be used as a quick way to select messages that match the
5957 string being searched for.
5958 Instead of typing carriage return to search for the next match, type
5959 Ctrl-X to select all matches.
5960 Once again, this only selects matches that are (or would be if the right
5961 index line was on the screen) visible.
5962 Truncated From lines or Subjects will cause matches to be missed.
5963 Although WhereIs is sometimes convenient for quick matching, the Select
5964 command is usually more powerful and usually faster.
5966 <P>
5967 <End of help on this topic>
5968 </BODY>
5969 </HTML>
5970 ======= h_view_cmd_whereis =======
5971 <HTML>
5972 <HEAD>
5973 <TITLE>WhereIs Command</TITLE>
5974 </HEAD>
5975 <BODY>
5976 <H1>WhereIs Command</H1>
5978 The WhereIs
5979 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
5980 command does a "find in current message" operation. You
5981 type in text and Alpine will try to find it in the message you are
5982 reading. WhereIs also has subcommands to jump to the beginning (Ctrl-Y)
5983 or end (Ctrl-V) of the message.
5984 That is, to rapidly move to the end of a message, hit the
5985 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5986 (or Ctrl-W) key followed
5987 by Ctrl-V. Similarly,
5988 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5989 followed by Ctrl-Y will take you to the beginning of a message.
5991 <P>
5992 <End of help on this topic>
5993 </BODY>
5994 </HTML>
5995 ======= h_view_cmd_hilite =======
5996 <HTML>
5997 <HEAD>
5998 <TITLE>View Hilite and Next item/Previous item</TITLE>
5999 </HEAD>
6000 <BODY>
6001 <H1>View Hilite and Next item/Previous item</H1>
6003 Sometimes messages may be in the form of formatted HTML text
6004 or they may contain URLs or Web server hostnames.
6005 When any of the features
6006 <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>,
6007 <A HREF="h_config_enable_view_web_host">"<!--#echo var="FEAT_enable-msg-view-web-hostnames"-->"</A>,
6008 <A HREF="h_config_enable_view_attach">"<!--#echo var="FEAT_enable-msg-view-attachments"-->"</A>,
6009 or
6010 <A HREF="h_config_enable_view_addresses">"<!--#echo var="FEAT_enable-msg-view-addresses"-->"</A>
6011 are enabled, Alpine will represent such selectable items in the text
6012 in bold typeface. One of the selectable items will be displayed in
6013 inverse video (highlighted). This is the "currently selected" item.
6014 Press the Return key to view the currently selected item.
6015 <P>
6017 The Up and Down Arrows keys can be used to change the selected item
6018 (also see the feature
6019 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
6020 If there are no selectable items in the direction of the arrow you
6021 pressed, Alpine will scroll the display in that direction until one
6022 becomes visible. To "jump" forwards/backwards among selectable
6023 items in the message text, use the Previous and Next item commands,
6024 <!--chtml if pinemode="function_key"-->F5 and F6
6025 <!--chtml else-->^B and ^F<!--chtml endif-->.
6027 <P>
6028 <End of help on this topic>
6029 </BODY>
6030 </HTML>
6031 ======= h_view_cmd_viewattch =======
6032 <HTML>
6033 <HEAD>
6034 <TITLE>ViewAttch Command</TITLE>
6035 </HEAD>
6036 <BODY>
6037 <H1>ViewAttch Command</H1>
6040 The View/Save Attachment
6041 (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->V<!--chtml endif-->)
6042 command allows you to handle MIME attachments to a message you have
6043 received. Alpine shows you a list of the message attachments -- you just
6044 choose the attachment you want. You may either view or save the
6045 selected attachment.
6047 <P>
6048 Because many attachments require external programs for display, there
6049 is some system configuration that has to happen before you can
6050 actually display attachments. Hopefully much of that will have been
6051 done already by your system administrator. MIME configuration is
6052 handled with the "mailcap" configuration file. (See the section
6053 on configuration in the
6054 <A HREF="h_news">release notes</A> for more information.)
6056 <P>
6057 <End of help on this topic>
6058 </BODY>
6059 </HTML>
6060 ======= h_index_cmd_expunge =======
6061 <HTML>
6062 <HEAD>
6063 <TITLE>Expunge/Exclude Command</TITLE>
6064 </HEAD>
6065 <BODY>
6066 <H1>Expunge/Exclude Command</H1>
6068 Expunge/Exclude
6069 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->X<!--chtml endif-->)
6070 is the command Alpine uses to actually remove all messages
6071 marked for deletion. With regular email files, expunge literally deletes
6072 the text from the current folder. With newsgroups or shared mailboxes,
6073 you don't have permission to actually remove the message, so it is an
6074 exclude -- Alpine removes the message from your view of the folder even
6075 though it is not technically gone.
6077 <P> A selective expunge command is available in IMAP folders that support
6078 the UID EXPUNGE extension in <A
6079 HREF="http://tools.ietf.org/html/rfc4315">RFC 4315</A> as well as for all
6080 other folders (local folders in all formats, POP3 inbox, and newsgroups)
6081 as a subcommand of the apply command. If some selected messages are marked
6082 deleted, then the apply command will offer the eXpunge command, which when
6083 executed will only expunge those messages that are selected and deleted.
6085 <P>
6086 Observe that the expunge command (when not used from the apply command)
6087 will expunge/exclude all deleted messages from the folder, and so all
6088 messages marked deleted will be expunged, regardless of if they are
6089 selected or not. In other words, there is no protection against
6090 potentially expunging more messages than only those that have been
6091 selected and deleted.
6092 <P>
6094 The configuration features
6095 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
6096 and
6097 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>
6098 affect the behavior of the Expunge command.
6100 <P>
6101 <End of help on this topic>
6102 </BODY>
6103 </HTML>
6104 ======= h_common_compose =======
6105 <HTML>
6106 <HEAD>
6107 <TITLE>Compose Command</TITLE>
6108 </HEAD>
6109 <BODY>
6110 <H1>Compose Command</H1>
6112 The Compose command takes you into the Alpine message composer where you
6113 can start a new message for sending. This is where you type in the
6114 message's text and specify its recipient list (the "To:"
6115 address), where copies should be directed (e.g., "Fcc",
6116 "Cc:" or "Bcc:"), and which files, if any, should
6117 be attached to the message.
6119 <P>
6120 When you type this command, Alpine will also automatically check for any
6121 interrupted (i.e., a message that was being composed when your modem
6122 or network connection was broken) or previously postponed messages and
6123 offer you a chance to continue working on those.
6125 <P>
6126 <UL>
6127 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6128 </UL><P>
6129 <End of help on this topic>
6130 </BODY>
6131 </HTML>
6132 ======= h_common_index =======
6133 <HTML>
6134 <HEAD>
6135 <TITLE>Message Index Command</TITLE>
6136 </HEAD>
6137 <BODY>
6138 <H1>Message Index Command</H1>
6140 The Index command takes you to the MESSAGE INDEX screen that displays a
6141 summary caption for each message in the currently-open folder. One
6142 message will be highlighted; this is the "Current" message.
6143 The message commands available from this screen (e.g. View, Reply,
6144 Forward, Delete, Print, Save, etc) apply to the current message.
6146 <P>
6147 <End of help on this topic>
6148 </BODY>
6149 </HTML>
6150 ======= h_common_folders =======
6151 <HTML>
6152 <HEAD>
6153 <TITLE>Folder List Command</TITLE>
6154 </HEAD>
6155 <BODY>
6156 <H1>Folder List Command</H1>
6158 This Folder List command takes you to the FOLDER LIST screen that displays
6159 the names of all your message folders and allows you to view, rename,
6160 delete, and add folders. You can open (view) a different folder than the
6161 one currently open by highlighting the desired one (using the arrow keys
6162 or their control-key equivalents) and pressing RETURN.
6164 <P>
6165 If you have multiple folder collections defined (see the Help text for
6166 the FOLDER LIST screen to learn more about Collections), you may need
6167 to press Return to expand the collection and display all of the
6168 folders in it.
6170 <P>
6171 <End of help on this topic>
6172 </BODY>
6173 </HTML>
6174 ======= h_main_addrbook =======
6175 <HTML>
6176 <HEAD>
6177 <TITLE>Address Book Command</TITLE>
6178 </HEAD>
6179 <BODY>
6180 <H1>Address Book Command</H1>
6182 This command, available only from the MAIN MENU, takes you
6183 to the ADDRESS BOOK management screen. From here, your personal address
6184 book(s) may be updated.
6186 <P>
6187 <End of help on this topic>
6188 </BODY>
6189 </HTML>
6190 ======= h_main_setup =======
6191 <HTML>
6192 <HEAD>
6193 <TITLE>Setup Command</TITLE>
6194 </HEAD>
6195 <BODY>
6196 <H1>Setup Command</H1>
6198 The Setup command, available only from the MAIN MENU, prompts you for
6199 one of several configuration screens, including the SETUP CONFIGURATION
6200 screen, by which you may activate optional Alpine features.
6202 <P>
6203 <End of help on this topic>
6204 </BODY>
6205 </HTML>
6206 ======= h_main_release_notes =======
6207 <HTML>
6208 <HEAD>
6209 <TITLE>Release Notes Command</TITLE>
6210 </HEAD>
6211 <BODY>
6212 <H1>Release Notes Command</H1>
6214 This command displays information about Alpine <!--#echo var="ALPINE_VERSION"-->,
6215 as well as pointers to further information such as history and legal notes.
6217 <P>
6218 <End of help on this topic>
6219 </BODY>
6220 </HTML>
6221 ======= h_main_kblock =======
6222 <HTML>
6223 <HEAD>
6224 <TITLE>Keyboard Lock Command</TITLE>
6225 </HEAD>
6226 <BODY>
6227 <H1>Keyboard Lock Command</H1>
6229 This command allows your Alpine session to be protected
6230 during a temporary absence from your terminal.
6232 <P>
6233 <End of help on this topic>
6234 </BODY>
6235 </HTML>
6236 ======= h_main_journal =======
6237 <HTML>
6238 <HEAD>
6239 <TITLE>Journal Command</TITLE>
6240 </HEAD>
6241 <BODY>
6242 <H1>Journal Command</H1>
6244 This command displays a list of all the status messages Alpine has
6245 displayed (on the third line from the bottom of the screen). This may
6246 be useful if a message disappeared before you had a chance to read it.
6248 <P>
6249 <End of help on this topic>
6250 </BODY>
6251 </HTML>
6252 ======= h_common_role =======
6253 <HTML>
6254 <HEAD>
6255 <TITLE>Role Command</TITLE>
6256 </HEAD>
6257 <BODY>
6258 <H1>Role Command</H1>
6260 The Role command is similar to the Compose command except that it starts
6261 off by letting you select a <A HREF="h_rules_roles">role</A>
6262 to be used for the composition.
6263 You may set up alternate roles by using Setup/Rules/Roles.
6265 <P>
6266 <End of help on this topic>
6267 </BODY>
6268 </HTML>
6269 ======= h_common_conditional_cmds =======
6270 <HTML>
6271 <HEAD>
6272 <TITLE>Conditional Commands</TITLE>
6273 </HEAD>
6274 <BODY>
6275 <H1>Conditional Commands</H1>
6277 The presence or absence of certain commands, particularly in the
6278 MESSAGE INDEX and MESSAGE TEXT screens, is determined by
6279 whether or not specific features are set in your Alpine configuration.
6280 (You can access the SETUP CONFIGURATION screen, where they are found, from
6281 Alpine's MAIN MENU.) To see if a desired command's availability is
6282 conditioned on a feature setting, see the command's help text (highlight
6283 the phrase associated with the command and hit Return).
6285 <P>
6286 Also note that some
6287 commands may be administratively disabled by your system manager;
6288 if they don't work, please check with your local help desk.
6290 <P>
6291 <UL>
6292 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6293 </UL><P>
6294 <End of help on this topic>
6295 </BODY>
6296 </HTML>
6297 ======= h_common_pipe =======
6298 <HTML>
6299 <HEAD>
6300 <TITLE>Pipe Command</TITLE>
6301 </HEAD>
6302 <BODY>
6303 <H1>Pipe Command</H1>
6305 Pipe
6306 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->|<!--chtml endif-->)
6307 allows you to send a message to a specified Unix command for external
6308 processing.
6309 This command's availability is controlled by the
6310 <A HREF="h_config_enable_pipe">"<!--#echo var="FEAT_enable-unix-pipe-cmd"-->"</A>
6311 feature.
6312 By default, the processed text of the message is sent to the command
6313 you specify and the output is captured by Alpine and shown to you.
6314 When you run the pipe command, there are some sub-commands which may be
6315 used to alter this behavior.
6316 These sub-commands are described <A HREF="h_pipe_command">here</A>.
6318 <P>
6319 <End of help on this topic>
6320 </BODY>
6321 </HTML>
6322 ======= h_common_goto =======
6323 <HTML>
6324 <HEAD>
6325 <TITLE>Goto Command</TITLE>
6326 </HEAD>
6327 <BODY>
6328 <H1>Goto Command</H1>
6330 Goto
6331 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->G<!--chtml endif-->)
6332 is the command that lets you bypass Alpine's folder selection screens
6333 and jump directly to a new folder. You can select any folder in the
6334 world: one in your current collection, one in a different collection or
6335 one in a collection you've never even used before.
6336 <P>
6338 Alpine will help you as much as possible to narrow in on the folder you want.
6339 However, if the folder is outside of your defined collections, you are
6340 going to have to enter the exact folder location using the correct
6341 <A HREF="h_valid_folder_names">syntax</A>
6342 for a remote folder and/or fully-qualified path name.
6344 <P>
6345 <End of help on this topic>
6346 </BODY>
6347 </HTML>
6348 ======= h_common_nextnew =======
6349 <HTML>
6350 <HEAD>
6351 <TITLE>NextNew Command</TITLE>
6352 </HEAD>
6353 <BODY>
6354 <H1>NextNew Command</H1>
6356 When you press the TAB key, Alpine advances to the next
6357 "interesting" message.
6358 This will be the next message you have not seen before, or the next message
6359 you have flagged Important, whichever comes first.
6360 Unread messages that have been deleted are not considered interesting.
6361 (A note about reading news. Alpine expects you to "Delete" news
6362 articles after you have read them if you want to remove them from future
6363 consideration. See <A HREF="h_mainhelp_readingnews">Reading News</A> for
6364 more information.)
6366 <P>
6367 The NextNew command is affected by the feature
6368 <A HREF="h_config_tab_new_only">"<!--#echo var="FEAT_tab-visits-next-new-message-only"-->"</A>,
6369 which causes Alpine to only consider Unread messages interesting, not messages
6370 flagged Important.
6372 <P>
6373 This command behaves a little differently when it finds there are no more
6374 interesting messages left in the current folder.
6375 If the current folder is one of your Incoming Message Folders
6376 (<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>)
6377 or it is a newsgroup, then Alpine will try to find the next folder or
6378 newsgroup that contains <EM>Recent</EM> messages and will ask you
6379 if you want to open that folder.
6380 This behavior may be modified by using the
6381 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
6382 feature that causes Alpine to look for Unseen messages instead of Recent
6383 messages.
6384 The NextNew command's behavior is also affected by the configuration features
6385 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A>,
6386 and
6387 <A HREF="h_config_tab_no_prompt">"<!--#echo var="FEAT_continue-tab-without-confirm"-->"</A>.
6389 <P>
6390 <End of help on this topic>
6391 </BODY>
6392 </HTML>
6393 ======= h_common_jump =======
6394 <HTML>
6395 <HEAD>
6396 <TITLE>Jump Command</TITLE>
6397 </HEAD>
6398 <BODY>
6399 <H1>Jump Command</H1>
6401 This is Alpine's way of allowing you to go straight to a specific message.
6402 Just press "J" and then enter the message number. By default, Alpine is also
6403 configured such that typing in any number automatically jumps you to that
6404 message
6405 (<A HREF="h_config_enable_jump">"<!--#echo var="FEAT_enable-jump-shortcut"-->"</A>
6406 in the SETUP CONFIGURATION).
6408 <P>
6409 <End of help on this topic>
6410 </BODY>
6411 </HTML>
6412 ======= h_common_flag =======
6413 <HTML>
6414 <HEAD>
6415 <TITLE>Flag Command</TITLE>
6416 </HEAD>
6417 <BODY>
6418 <H1>Flag Command</H1>
6420 Flag
6421 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6422 is the command that allows users to manipulate the status flags that
6423 appear on the left side of the MESSAGE INDEX screen. The most common
6424 use of this is to mark a message as important. This is something of a
6425 note to yourself to get back to that message. You may also use the
6426 flag command to set (or unset) the flags that indicate that a message
6427 is new, answered, deleted, or forwarded.<P>
6429 Provided the mail server supports it,
6430 you may also manipulate user-defined keywords
6431 for a message using the flag command.
6432 These keywords will be available if you use the Flag Details screen that you
6433 can get to after typing the
6434 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6435 command.
6436 They will be listed after the Important, New, Answered, Deleted , and Forwarded flags,
6437 which are always present.
6438 You may add new keywords by using the Add KW command from the Flag Details screen
6439 or by defining them in the <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
6441 The availability of the flag command is determined by the
6442 <A HREF="h_config_enable_flag">"<!--#echo var="FEAT_enable-flag-cmd"-->"</A>
6443 feature in your Alpine configuration. Also, it is possible that Flag could be
6444 administratively disabled by your system manager; if it doesn't work,
6445 please check with your local help desk before reporting a bug.
6446 The behavior of the flag command may be modified by the
6447 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
6448 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
6450 <P>
6451 <End of help on this topic>
6452 </BODY>
6453 </HTML>
6454 ======= h_common_hdrmode =======
6455 <HTML>
6456 <HEAD>
6457 <TITLE>HdrMode Command</TITLE>
6458 </HEAD>
6459 <BODY>
6460 <H1>HdrMode Command</H1>
6462 Every email message comes with some header lines that you normally
6463 don't see (and don't want to see).
6464 These include anywhere from 3-20 lines (or more) added by the
6465 Internet mail transport system to record the route your message took,
6466 for diagnostic purposes.
6467 These are normally of no import and simply
6468 add clutter, so Alpine suppresses them in the MESSAGE TEXT display.
6469 This also includes other non-standard headers the message may contain.
6470 If you want to see these headers, there is a way to reveal them.
6471 <P>
6473 The Header Mode
6474 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6475 command is a toggle that controls Alpine's handling of these header
6476 lines. Normally, full headers is "off" and you only see a
6477 few lines about who a message is to and who it is from. When you
6478 press
6479 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6480 to turn full headers on, Alpine will show you
6481 the normal header lines as well as delivery headers, comment headers,
6482 MIME headers, and any other headers present.
6483 <P>
6485 Several different Alpine commands honor the header mode -- it affects how
6486 messages are displayed, how they appear in forward and reply email, how
6487 they are printed, how they are saved, and how they are exported.
6488 <!--chtml if pinemode="os_windows"-->
6489 <!--chtml else-->
6490 The pipe command is also affected.
6491 <!--chtml endif-->
6492 <P>
6494 The presence or absence of the Header Mode command is determined by the
6495 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
6496 Feature-List option in your Alpine configuration.
6498 <P>
6499 If you have also turned on the
6500 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
6501 option then the HdrMode command actually rotates through three states
6502 instead of just two.
6503 The first is the normal view with long quotes suppressed.
6504 The second is the normal view but with the long quotes included.
6505 The last enables the display of all headers in the message.
6506 When using Export, Pipe, Print, Forward, or Reply the quotes are
6507 never suppressed, so the first two states are identical.
6509 <P>
6510 The behavior of the Header Mode command may be altered slightly by
6511 turning on the
6512 <A HREF="h_config_quell_full_hdr_reset">"<!--#echo var="FEAT_quell-full-header-auto-reset"-->"</A>
6513 Feature-List option in your Alpine configuration.
6514 In particular, it will cause the Header Mode to be persistent when moving
6515 from message to message instead of resetting to the default for each message.
6517 <P>
6518 <UL>
6519 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6520 </UL><P>
6521 <End of help on this topic>
6522 </BODY>
6523 </HTML>
6524 ======= h_common_print =======
6525 <HTML>
6526 <HEAD>
6527 <TITLE>Print Command</TITLE>
6528 </HEAD>
6529 <BODY>
6530 <H1>Print Command</H1>
6532 The Print
6533 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->%<!--chtml endif-->)
6534 command allows you to print a copy of a message.
6535 There are many SETUP CONFIGURATION features that affect the
6536 Print command, including
6537 <A HREF="h_config_enable_y_print">"<!--#echo var="FEAT_enable-print-via-y-command"-->"</A>,
6538 <A HREF="h_config_print_index">"<!--#echo var="FEAT_print-index-enabled"-->"</A>,
6539 <A HREF="h_config_custom_print">"<!--#echo var="FEAT_print-offers-custom-cmd-prompt"-->"</A>,
6540 <A HREF="h_config_print_from">"<!--#echo var="FEAT_print-includes-from-line"-->"</A>, and
6541 <A HREF="h_config_ff_between_msgs">"<!--#echo var="FEAT_print-formfeed-between-messages"-->"</A>.
6542 You set up for printing by using the Printer option of the Setup command
6543 on the MAIN MENU.
6544 <P>
6546 <P>
6547 <End of help on this topic>
6548 </BODY>
6549 </HTML>
6550 ======= h_common_take =======
6551 <HTML>
6552 <HEAD>
6553 <TITLE>TakeAddr Command</TITLE>
6554 </HEAD>
6555 <BODY>
6556 <H1>TakeAddr Command</H1>
6559 With the Take Address
6560 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->T<!--chtml endif-->)
6561 command, you can extract email addresses from an
6562 incoming message and save them in an address book. This is an easy way
6563 to add to your address book and avoid having to remember the email
6564 addresses of the people who write to you.
6565 <P>
6567 If the message is just to you individually, then you will only need to
6568 provide a nickname. If the message contains more than one email address,
6569 then you will see an address
6570 selection screen that lets you choose the address you want to save into
6571 your address book, or lets you choose several of them add to a
6572 personal distribution list.
6573 <P>
6575 Once you've added an entry to your address book, you can use it from the
6576 message composer by typing the nickname of the entry into one of the
6577 header fields (for example, into the To: field), or you can use ^T from
6578 the header field to select the entry from your address book.
6579 <P>
6581 If the configuration feature
6582 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
6583 is set, the behavior of the Take command is altered slightly.
6585 <P>
6586 <End of help on this topic>
6587 </BODY>
6588 </HTML>
6589 ======= h_ge_import =======
6590 <HTML>
6591 <HEAD>
6592 <TITLE>Import File Selection</TITLE>
6593 </HEAD>
6594 <BODY>
6595 <H1>Import File Selection</H1>
6597 You are importing a file that you previously
6598 exported from Alpine.
6599 You are now being asked for the name of that file.
6600 The easiest way to select a file is probably with the "^T"
6601 "To Files" command.
6602 Alternatively, you may type in a file name.
6603 It may be an absolute pathname.
6604 Otherwise, it is a file located in your home directory
6605 or current working directory
6606 <!--chtml if pinemode="running"-->
6607 (which, at least for your current Alpine "session,"
6608 is "<!--#echo var="CURRENT_DIR"-->")
6609 <!--chtml endif-->, depending on the
6610 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6611 In any case, you finish by typing a carriage return to accept the
6612 file name that is displayed.
6613 When the feature
6614 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6615 is turned on you may use TAB to complete partially typed in names.
6616 <P>
6617 You may cancel the import operation by typing "^C" after exiting
6618 this help.
6619 <P>
6620 <End of help on this topic>
6621 </BODY>
6622 </HTML>
6623 ======= h_ge_allparts =======
6624 <HTML>
6625 <HEAD>
6626 <TITLE>Export Message File Selection</TITLE>
6627 </HEAD>
6628 <BODY>
6629 <H1>Export Message File Selection</H1>
6631 You are Exporting a message from an Alpine mail folder
6632 to a plain text file.
6633 You also have the option of exporting all of the attachments associated
6634 with the message.
6635 You are now being asked for the name of the file to export <EM>to</EM>.
6636 The easiest way to select a file is probably with the "^T"
6637 "To Files" subcommand.
6638 After returning from that subcommand you will still be allowed to
6639 edit the name you have selected.
6640 Alternatively, you may type in a file name.
6641 It may be an absolute pathname.
6642 Otherwise, it is a file located in your home directory
6643 or current working directory
6644 <!--chtml if pinemode="running"-->
6645 (which, at least for your current Alpine "session,"
6646 is "<!--#echo var="CURRENT_DIR"-->")
6647 <!--chtml endif-->, depending on the
6648 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6649 In any case, you finish by typing a carriage return to accept the
6650 file name that is displayed.
6651 When the feature
6652 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6653 is turned on you may use TAB to complete partially typed in names.
6654 <P>
6655 The message you are exporting appears to have some attachments.
6656 If you wish to save <EM>all</EM> of the attachments at once,
6657 type the "^P" "AllParts" command to turn on
6658 saving of the attachments.
6659 You may turn it back off by typing "^P" again, which will now
6660 be labeled "NoAllParts" instead.
6661 If you want to save the parts the command displayed should be
6662 "NoAllParts"!
6663 When you choose to save attachments like this, the attachments will be saved
6664 in a newly created directory.
6665 That directory will have the same name as the file name you choose here,
6666 with the letters ".d" appended.
6667 If that directory already exists, then the letters ".d_1" will
6668 be tried, then ".d_2" and so on until a name that doesn't exist
6669 is found.
6670 For example, if you select the file name
6671 <P>
6672 <CENTER><SAMP>filename</SAMP></CENTER>
6673 <P>
6674 to export the message to, then the directory used for the attachments will be
6675 <P>
6676 <CENTER><SAMP>filename.d</SAMP></CENTER>
6677 <P>
6678 or perhaps
6679 <P>
6680 <CENTER><SAMP>filename.d_<n></SAMP></CENTER>
6681 <P>
6682 The attachments will then be put into files inside that directory.
6683 The names for the attachment files will be derived from the attachments
6684 if possible.
6685 This is done in the same way as the default values are derived if you
6686 save them one at a time.
6687 (The "filename" parameter from the Content-Disposition header
6688 is the first choice. If that doesn't exist, the "name"
6689 parameter from the Content-Type header is used.)
6690 If a name for a particular attachment is not available, then the
6691 part number of the attachment is used, with the characters "part_"
6692 prepended.
6693 An example of that would be
6694 <P>
6695 <CENTER><SAMP>part_2.1</SAMP></CENTER>
6696 <P>
6697 If you want to save only some of the attachments or if you want more control
6698 over the directory and filename where an attachment is saved you may
6699 cancel out of this command and View the attachment list.
6700 From there you can save each attachment individually.
6701 <P>
6702 You may cancel the Export operation by typing "^C" after exiting
6703 this help.
6704 <P>
6705 <End of help on this topic>
6706 </BODY>
6707 </HTML>
6708 ======= h_ge_export =======
6709 <HTML>
6710 <HEAD>
6711 <TITLE>Export File Selection</TITLE>
6712 </HEAD>
6713 <BODY>
6714 <H1>Export File Selection</H1>
6716 You are Exporting or Saving something from within the Alpine world
6717 (a message, an attachment, etc.)
6718 to a plain text file.
6719 You are now being asked for the name of the file to export <EM>to</EM>.
6720 The easiest way to select a file is probably with the "^T"
6721 "To Files" subcommand.
6722 After returning from that subcommand you will still be allowed to
6723 edit the name you have selected.
6724 Alternatively, you may type in a file name.
6725 It may be an absolute pathname.
6726 Otherwise, it is a file located in your home directory
6727 or current working directory
6728 <!--chtml if pinemode="running"-->
6729 (which, at least for your current Alpine "session,"
6730 is "<!--#echo var="CURRENT_DIR"-->")
6731 <!--chtml endif-->, depending on the
6732 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6733 In any case, you finish by typing a carriage return to accept the
6734 file name that is displayed.
6735 When the feature
6736 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6737 is turned on you may use TAB to complete partially typed in names.
6738 <P>
6739 If the object you are exporting is a message with some attachments,
6740 you may wish to save all of the attachments by typing the "^P"
6741 "AllParts" command to turn on saving of the attachments.
6742 This subcommand will only be visible if the message actually has attachments.
6743 You may also View the attachment list and save individual attachments from
6744 there.
6745 <P>
6746 If you are SAVING a text part (text/plain, text/html, etc.) you can use
6747 the Control-R subcommand to toggle if saving will be done in binary mode,
6748 meaning that the attachment will be decoded, but will not be transformed
6749 to UTF-8 for further processing (either in internal filters, or user
6750 supplied filters.) This is useful in case you either want to preserve
6751 the text as it was encoded originally to you, or the attachment was
6752 incorrectly attached (the attachment is not of text type) and you need
6753 the original text to process the attachment.
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_common_save =======
6762 <HTML>
6763 <HEAD>
6764 <TITLE>Save and Export Commands</TITLE>
6765 </HEAD>
6766 <BODY>
6767 <H1>Save and Export Commands</H1>
6769 Save
6770 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->S<!--chtml endif-->)
6771 and Export
6772 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->E<!--chtml endif-->)
6773 are the two alternatives Alpine gives you to keep a copy of the message
6774 you are reading. If you want to keep the message within Alpine's email
6775 world, use "Save"; if you want to use the message in another
6776 program, use "Export".
6777 <P>
6779 When you Save a message, it is put into an existing folder or into a new
6780 folder in one of your existing folder collections. The message stays in
6781 email format and can be read by Alpine again. Alpine may use a special format
6782 for its mail folders -- never edit an Alpine folder by hand or with any
6783 program other than Alpine. The exact behavior of the Save command can be
6784 configured with the
6785 <A HREF="h_config_quote_all_froms">"<!--#echo var="FEAT_save-will-quote-leading-froms"-->"</A>,
6786 <A HREF="h_config_save_wont_delete">"<!--#echo var="FEAT_save-will-not-delete"-->"</A>,
6787 and
6788 <A HREF="h_config_save_advances">"<!--#echo var="FEAT_save-will-advance"-->"</A>
6789 feature list settings.
6790 The name of the folder offered as a default is controlled by the option
6791 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>.
6792 <P>
6794 When you use Export, the message is placed in a plain text file in your
6795 home directory
6796 <!--chtml if pinemode="running"-->
6797 (which, in the present configuration of your system, is
6798 "<!--#echo var="HOME_DIR"-->")
6799 <!--chtml endif-->
6800 or current working directory
6801 <!--chtml if pinemode="running"-->
6802 (which, at least for your current Alpine "session,"
6803 is "<!--#echo var="CURRENT_DIR"-->")
6804 <!--chtml endif-->, depending on the
6805 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
6806 configuration setting. In the normal case, only minimal
6807 headers are exported with the message; however, if the full header mode
6808 (whose availability may be disabled by setting the feature
6809 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
6810 in SETUP CONFIGURATION) is
6811 toggled on, then complete headers are exported along with the message
6812 text. (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
6813 defined, they may affect the contents of the exported file.)
6815 <P>
6816 <End of help on this topic>
6817 </BODY>
6818 </HTML>
6819 ======= h_common_bounce =======
6820 <HTML>
6821 <HEAD>
6822 <TITLE>Bounce Command</TITLE>
6823 </HEAD>
6824 <BODY>
6825 <H1>Bounce Command</H1>
6827 The Bounce
6828 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->B<!--chtml endif-->)
6829 command allows you to re-send, or "remail", a
6830 message, as if you were never in the loop. It is analogous to crossing
6831 out your address on a postal letter, writing a different address on the
6832 envelope, and putting it into the mailbox. Bounce is used primarily to
6833 redirect email that was sent to you in error.
6834 Also, some owners of email
6835 lists need the bounce command to handle list traffic.
6836 Bounce is not anonymous.
6837 A ReSent-From header is added to the message so that the recipient may
6838 tell that you Bounced it to them.
6839 <P>
6841 The presence or absence of the Bounce command is determined by the
6842 <A HREF="h_config_enable_bounce">"<!--#echo var="FEAT_enable-bounce-cmd"-->"</A>
6843 feature in your Alpine configuration.
6844 The feature
6845 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A>
6846 affects the behavior of the Bounce command.
6847 Also, it is possible that Bounce could be
6848 administratively disabled by your system manager; if it doesn't work,
6849 please check with your local help desk before reporting a bug.
6851 <P>
6852 <End of help on this topic>
6853 </BODY>
6854 </HTML>
6855 ======= h_common_reply =======
6856 <HTML>
6857 <HEAD>
6858 <TITLE>Reply and Forward Commands</TITLE>
6859 </HEAD>
6860 <BODY>
6862 <H1>Reply and Forward Commands</H1>
6864 Replying
6865 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->R<!--chtml endif-->)
6866 and Forwarding
6867 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->F<!--chtml endif-->)
6868 are your two alternatives for following up on the
6869 message you are reading. You would use reply if you want to get email
6870 back to the author of the message and/or the other people who have
6871 already seen it. You use forward if you want somebody new to see the
6872 message.
6873 <P>
6875 In the normal case, the only thing that you must supply when forwarding a
6876 message is the name/email address of the new recipient.
6877 Alpine will include the text of the forwarded message.
6878 Alpine will also include any attachments to the message.
6879 There is space above the forwarded text for you to include additional comments.
6880 <P>
6882 When replying, you usually have to answer some questions.
6883 If the message is to multiple people and/or specified with a Reply-To: header,
6884 then you will have to decide who should get the reply.
6885 You also need to decide whether or not to include the previous
6886 message in your reply.
6887 Some of this is configurable.
6888 Specifically, see the
6889 <A HREF="h_config_include_header">"<!--#echo var="FEAT_include-header-in-reply"-->"</A>,
6890 <A HREF="h_config_auto_include_reply">"<!--#echo var="FEAT_include-text-in-reply"-->"</A>,
6891 <A HREF="h_config_attach_in_reply">"<!--#echo var="FEAT_include-attachments-in-reply"-->"</A>,
6892 and
6893 <A HREF="h_config_auto_reply_to">"<!--#echo var="FEAT_reply-always-uses-reply-to"-->"</A>
6894 configuration features.
6895 <P>
6897 Both the Reply and Forward commands react to the full header mode toggle.
6898 If the full header mode is on, then all the header and delivery lines are
6899 included with the text of the message in your reply/forward.
6900 <P>
6902 Other configuration features that affect the Reply command are
6903 <A HREF="h_config_sig_at_bottom">"<!--#echo var="FEAT_signature-at-bottom"-->"</A>,
6904 <A HREF="h_config_sigdashes">"<!--#echo var="FEAT_enable-sigdashes"-->"</A>, and
6905 <A HREF="h_config_strip_sigdashes">"<!--#echo var="FEAT_strip-from-sigdashes-on-reply"-->"</A>.
6907 <P>
6908 <End of help on this topic>
6909 </BODY>
6910 </HTML>
6911 ======= h_common_delete =======
6912 <HTML>
6913 <HEAD>
6914 <TITLE>Delete and Undelete Commands</TITLE>
6915 </HEAD>
6916 <BODY>
6917 <H1>Delete and Undelete Commands</H1>
6919 Delete
6920 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->D<!--chtml endif-->)
6921 and Undelete
6922 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->U<!--chtml endif-->)
6923 allow you to change the Deleted flag for the current message.
6924 Delete marks a message Deleted (turns on the Deleted flag) and Undelete
6925 removes the mark.
6926 In the MESSAGE INDEX, deleted messages have a "D" in the status field
6927 at the left hand edge of the index line.
6928 When viewing a deleted message, the letters "DEL" will be present
6929 in the upper right hand corner of the screen.
6930 Delete simply <EM>marks</EM> a message Deleted, it does not actually
6931 get rid of the message.
6932 The eXpunge command (available from the MESSAGE INDEX screen) actually
6933 removes all of the deleted messages in a folder.
6934 Once a message is eXpunged, it can't be retrieved.
6935 <P>
6937 The Delete command is affected by the setting of the configuration feature
6938 <A HREF="h_config_del_skips_del">"<!--#echo var="FEAT_delete-skips-deleted"-->"</A>.
6940 <P>
6941 <End of help on this topic>
6942 </BODY>
6943 </HTML>
6944 ======= h_common_postpone =======
6945 <HTML>
6946 <HEAD>
6947 <TITLE>Postpone Command</TITLE>
6948 </HEAD>
6949 <BODY>
6950 <H1>Postpone Command</H1>
6952 The postpone
6953 <!--chtml if pinemode="function_key"-->(F11)<!--chtml else-->(^O)<!--chtml endif-->
6954 command allows you to temporarily stop working on the current
6955 message so you may read
6956 other messages or compose another message. When you want to resume a
6957 message later, start to compose and answer "yes" to the
6958 "Continue postponed composition?" question. You may
6959 postpone as many messages as you like.
6961 <P>
6962 Note: If a <A HREF="h_config_form_folder"><!--#echo var="VAR_form-letter-folder"--></A> is defined
6963 in the Setup/Config screen, then the Postpone command will prompt you for
6964 the folder in which to store your outgoing message.
6966 <P>
6967 <End of help on this topic>
6968 </BODY>
6969 </HTML>
6970 ======= h_compose_cancel =======
6971 <HTML>
6972 <HEAD>
6973 <TITLE>Cancel Command</TITLE>
6974 </HEAD>
6975 <BODY>
6976 <H1>Cancel Command</H1>
6978 Cancel
6979 <!--chtml if pinemode="function_key"-->
6980 (F2)
6981 <!--chtml else-->
6982 (^C)
6983 <!--chtml endif-->
6985 The Cancel command returns you to Alpine's normal mail processing and
6986 causes the message currently under composition to be thrown out.
6987 The message text <EM>will be lost</EM>.
6989 <P>
6990 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
6991 will be preserved in the file named
6992 <!--chtml if pinemode="os_windows"-->
6993 "DEADLETR".
6994 <!--chtml else-->
6995 "dead.letter" in your home directory.
6996 <!--chtml endif-->
6997 If you unintentionally cancel a message, look there for its text.
6999 <P>
7000 <End of help on this topic>
7001 </BODY>
7002 </HTML>
7003 ======= h_compose_addrcomplete =======
7004 <HTML>
7005 <HEAD>
7006 <TITLE>Address Completion</TITLE>
7007 </HEAD>
7008 <BODY>
7009 <H1>Address Completion</H1>
7011 When entering addresses in the address fields of the composer (To, Cc, etc.)
7012 the TAB key may be used to help complete the address.
7013 Type a partial nickname and tap the TAB key to complete the typing.
7014 The unambiguous part of the name will be filled in automatically.
7015 Typing TAB twice in succession will bring up a selection list of possibilities,
7016 making it easy to find and choose the correct address.
7018 <P>
7019 The matching algorithm is rather ad hoc.
7020 The search starts with a search of your address book.
7021 It counts as a match if the nickname, address, or fullname field of an
7022 entry begins with the text typed in so far. It is also a match if
7023 a later word in the fullname (for example, the middle name or last name)
7024 begins with the entered text.
7025 <P>
7026 Next comes an LDAP search.
7027 The search will happen for any servers that have the
7028 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
7029 feature set. You can set or unset the feature for each server independently
7030 in the Setup/Directory screen.
7031 <P>
7032 Finally, if you are replying to or forwarding a message, that message is
7033 searched for likely candidate addresses that match the typed-in text.
7035 <P>
7036 <End of help on this topic>
7037 </BODY>
7038 </HTML>
7039 ======= h_compose_richhdr =======
7040 <HTML>
7041 <HEAD>
7042 <TITLE>Rich Header Command</TITLE>
7043 </HEAD>
7044 <BODY>
7045 <H1>Rich Header Command</H1>
7047 The Rich Header command allows you to toggle between the list of
7048 all message headers available for editing and those that are most
7049 common.
7051 <P>
7052 Use this toggle to expose headers that are not normally visible by
7053 default.
7054 This set usually includes the
7055 "Bcc:",
7056 "Fcc:",
7057 "Lcc:",
7058 and "Newsgroups"
7059 headers.
7060 If you are posting to a newsgroup the set of defaults is a little different.
7061 Obviously, in that case, the Newsgroups header is of interest so is not
7062 hidden.
7063 For news posting the hidden set includes the
7064 "To:",
7065 "Cc:",
7066 "Bcc:",
7067 "Fcc:",
7068 and "Lcc:"
7069 headers.
7070 You won't normally want to edit these, which is why they are hidden,
7071 but it is sometimes useful to be able to set them manually.
7073 <P>
7074 The default sets of headers listed above can be altered.
7075 Any header that you have added to the
7076 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
7077 option, but not to the
7078 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
7079 option will appear when you use the Rich Headers command to
7080 make the Rich Headers visible.
7081 (Headers listed in the <!--#echo var="VAR_default-composer-hdrs"--> list will be visible
7082 even without toggling the Rich Headers command.)
7084 <P>
7085 <End of help on this topic>
7086 </BODY>
7087 </HTML>
7088 ======= h_compose_send =======
7089 <HTML>
7090 <HEAD>
7091 <TITLE>Send Command</TITLE>
7092 </HEAD>
7093 <BODY>
7094 <H1>Send Command</H1>
7096 The Send command
7097 <!--chtml if pinemode="function_key"-->
7098 (F3)
7099 <!--chtml else-->
7100 (^X)
7101 <!--chtml endif-->
7102 tells Alpine you are finished composing.
7103 Before actually sending it, though, Alpine will ask you to confirm
7104 your intention, and, at the same time, redisplayed the message text
7105 with the recipients at the top of the screen to give you the opportunity
7106 to review and verify that the message is addressed to the people
7107 you intended.
7108 <P>
7109 If the feature
7110 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
7111 then this confirmation prompt and any options it allows are skipped.
7113 <P>
7114 This confirmation prompt may also offer, depending
7115 on your particular Setup/Config, options allowing you to set
7116 <A HREF="h_config_compose_dsn">delivery status notifications</A>,
7117 include attachments in the "Fcc" (if you had previously
7118 specified that they <A HREF="h_config_no_fcc_attach">exclude attachments</A>,
7119 observe details of the
7120 <A HREF="h_config_verbose_post">message submission process</A>,
7121 choose the filter through which the
7122 <A HREF="h_config_sending_filter">outgoing text should first pass</A>,
7123 or turn of flowed text generation.
7125 <P>
7126 <End of help on this topic>
7127 </BODY>
7128 </HTML>
7129 ======= h_compose_markcutpaste =======
7130 <HTML>
7131 <HEAD>
7132 <TITLE>Mark, Cut and Paste Commands</TITLE>
7133 </HEAD>
7134 <BODY>
7135 <H1>Mark, Cut and Paste Commands</H1>
7137 You can define a "block" of text, which can subsequently
7138 be deleted or
7139 copied as a unit, by setting a mark at the start of the block (Ctrl-^) and
7140 then moving the cursor to the end of the desired text block. You can then
7141 "cut" the block out
7142 <!--chtml if pinemode="function_key"-->
7143 "F9",
7144 <!--chtml else-->
7145 "Ctrl-K",
7146 <!--chtml endif-->
7147 move the cursor, and "paste" it
7148 <!--chtml if pinemode="function_key"-->
7149 "F10",
7150 <!--chtml else-->
7151 "Ctrl-U",
7152 <!--chtml endif-->
7153 in the new location. Also, you can paste more than once, allowing you
7154 to use this feature to copy a block of text.<P>
7156 If you press
7157 <!--chtml if pinemode="function_key"-->
7158 "F9"
7159 <!--chtml else-->
7160 "^K"
7161 <!--chtml endif-->
7162 without having marked anything, Alpine will delete
7163 a single line. If you delete a group of lines together, Alpine keeps them
7164 in the same buffer, so
7165 <!--chtml if pinemode="function_key"-->
7166 F10
7167 <!--chtml else-->
7168 ^U
7169 <!--chtml endif-->
7170 will restore them as a block. About
7171 terminology: Mark is shown as "^^". The first "^" means you should
7172 hold down the "Control" key on your keyboard. The second "^" means
7173 "type the character ^".
7175 <P>
7176 <End of help on this topic>
7177 </BODY>
7178 </HTML>
7179 ======= h_compose_justify =======
7180 <HTML>
7181 <HEAD>
7182 <TITLE>Justify Command</TITLE>
7183 </HEAD>
7184 <BODY>
7185 <H1>Justify Command</H1>
7187 The Justify
7188 <!--chtml if pinemode="function_key"-->
7189 (F4)
7190 <!--chtml else-->
7191 (^J)
7192 <!--chtml endif-->
7193 command reformats the text in the paragraph the cursor is in.
7194 Paragraphs are separated by one blank line or a line beginning with a space.
7195 This is useful when you have been editing a paragraph and the lines become
7196 uneven. The text is left aligned or justified and the right is ragged. If
7197 the text is already justified as typed with auto-wrap, no justification will
7198 be done.
7200 <P>
7201 If you have set a <A HREF="h_compose_markcutpaste">mark</A> to select a
7202 block of text, the Justify command is modified.
7203 Instead of automatically justifying the current paragraph you will be
7204 asked if you want to justify the paragraph, justify the selected region,
7205 or adjust the quote level of the selected region.
7206 Adjusting the quote level only works if you are using standard
7207 "> " or ">" quotes, which is the default if you haven't
7208 changed "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>".
7210 <P>
7211 When composing a reply containing included text, the justify command
7212 will reformat text to the right of the
7213 "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>",
7214 adding or removing indented lines as needed. Paragraphs are separated
7215 by a blank line, a line containing only the <!--#echo var="VAR_reply-indent-string"-->, or a
7216 line containing the indent string and one or more blank spaces.
7217 Included text that was previously indented (or "quoted") is
7218 not preserved.
7220 <P>
7221 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
7222 in 1999 and its wide-spread adoption since then, you will usually be better off if you
7223 use the standard
7224 "> " or ">" quotes.
7226 <P>
7227 <End of help on this topic>
7228 </BODY>
7229 </HTML>
7230 ======= h_compose_spell =======
7231 <HTML>
7232 <HEAD>
7233 <TITLE>Spell Check Command</TITLE>
7234 </HEAD>
7235 <BODY>
7236 <H1>Spell Check Command</H1>
7238 The "To Spell"
7239 <!--chtml if pinemode="function_key"-->
7240 (F12)
7241 <!--chtml else-->
7242 (^T)
7243 <!--chtml endif-->
7244 command calls an external spell checking program to look over the
7245 message you are composing. By default, Alpine uses
7246 <P>
7247 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
7248 <P>
7249 if it knows where to find "aspell".
7250 If there is no "aspell" command available but the command "ispell" is available
7251 then the command used is
7252 <P>
7253 <CENTER><SAMP>ispell -l</SAMP></CENTER>
7254 <P>
7255 Otherwise, the ancient "spell" command is used.
7256 <P>
7257 For PC-Alpine, you must install the aspell library code that you
7258 may get from
7259 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
7261 <P>
7262 <End of help on this topic>
7263 </BODY>
7264 </HTML>
7265 ======= h_compose_alted =======
7266 <HTML>
7267 <HEAD>
7268 <TITLE>Alt Editor Command</TITLE>
7269 </HEAD>
7270 <BODY>
7271 <H1>Alt Editor Command</H1>
7273 The "Alt Editor" command's availability depends on the
7274 Setup/Config variable "<A HREF="h_config_editor"><!--#echo var="VAR_editor"--></A>".
7276 <P>
7277 When the variable specifies a valid editor on your system, this
7278 command will launch it with the current text of your message
7279 already filled in.
7281 <P>
7282 <End of help on this topic>
7283 </BODY>
7284 </HTML>
7285 ======= h_compose_readfile =======
7286 <HTML>
7287 <HEAD>
7288 <TITLE>Read File Command</TITLE>
7289 </HEAD>
7290 <BODY>
7291 <H1>Read File Command</H1>
7293 The "Read File"
7294 <!--chtml if pinemode="function_key"-->
7295 (F5)
7296 <!--chtml else-->
7297 (^R)
7298 <!--chtml endif-->
7299 command allows you to copy in text from an existing file. You will be
7300 prompted for the name of a file to be inserted into the message. The file
7301 name is relative to your home directory
7302 <!--chtml if pinemode="running"-->
7303 (which, in the present configuration of your system, is
7304 "<!--#echo var="HOME_DIR"-->")
7305 <!--chtml endif-->
7306 or current working directory
7307 <!--chtml if pinemode="running"-->
7308 (which, at least for your current Alpine "session,"
7309 is "<!--#echo var="CURRENT_DIR"-->")
7310 <!--chtml endif-->, depending on the
7311 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
7312 configuration setting; or, the file name must be specified as a full path name
7313 <!--chtml if pinemode="os_windows"-->
7314 -- for example: "A:\PAPER.TXT"
7315 <!--chtml else-->
7316 -- for example: "/tmp/wisdom-of-the-day"
7317 <!--chtml endif-->
7318 (without the quotation marks).
7320 <P>
7321 The file will be inserted where the cursor is located. <B>The
7322 file to be read must be on the same system as Alpine.</B> If you use Alpine on a
7323 Unix machine but have files on a PC or Mac, the files must be transferred
7324 to the system Alpine is running on before they can be read. Please ask your
7325 local computer support people about the correct way to transfer a file to
7326 your Alpine system.
7328 <P>
7329 <End of help on this topic>
7330 </BODY>
7331 </HTML>
7332 ======= h_config_tray_icon =======
7333 <HTML>
7334 <HEAD>
7335 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></TITLE>
7336 </HEAD>
7337 <BODY>
7338 <H1>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></H1>
7340 PC-Alpine only.
7341 <P>
7342 This option restores a behavior of previous versions of PC-Alpine.
7343 These
7344 versions, when started, installed a PC-Alpine icon in the notification
7345 tray of Window's Taskbar. The primary use of this icon was to indicate
7346 new mail arrival by turning red (while the Taskbar icon remained green).
7347 Additionally, the icon now changes to yellow to signify that a mail folder
7348 has been closed unexpectedly.
7350 <P>
7351 Rather than add another icon to the Taskbar, this version of PC-Alpine will
7352 color its Taskbar entry's icon red (as well as the icon in the Window
7353 Title). This feature is only provided for backwards compatibility.
7355 <P>
7356 <End of help on this topic>
7357 </BODY>
7358 </HTML>
7359 ======= h_common_suspend =======
7360 <HTML>
7361 <HEAD>
7362 <TITLE>Suspend Command</TITLE>
7363 </HEAD>
7364 <BODY>
7365 <H1>Suspend Command</H1>
7367 With the <A HREF="h_config_can_suspend"><!--#echo var="FEAT_enable-suspend"--></A> feature
7368 enabled, you can, at almost any time, temporarily halt your Alpine session,
7369 <!--chtml if pinemode="os_windows"-->
7370 minimizing it into an icon.
7371 <!--chtml else-->
7372 and return to your system prompt.
7373 <!--chtml endif-->
7375 <P>
7376 <End of help on this topic>
7377 </BODY>
7378 </HTML>
7379 ======= h_pipe_command =======
7380 <HTML>
7381 <HEAD>
7382 <TITLE>Pipe Command SubOptions</TITLE>
7383 </HEAD>
7384 <BODY>
7385 <H1>Pipe Command SubOptions</H1>
7387 By default, when you use the Pipe command, the processed text of the
7388 message is sent to the Unix command
7389 you specify and the output is captured by Alpine and shown to you.
7390 (This command is available in PC-Alpine, as well, but there aren't many
7391 Windows commands that work well with piping.)
7392 There are some sub-commands that may be used to alter this behavior.
7393 These are toggles that switch the behavior between two possibilities.
7394 They can be combined in any way you wish.
7395 <P>
7396 By default, the prompt at the bottom of the screen looks like
7397 <P>
7398 <CENTER><SAMP>Pipe message 37 to :</SAMP></CENTER>
7399 <P>
7400 or
7401 <P>
7402 <CENTER><SAMP>Pipe messages to :</SAMP></CENTER>
7403 <P>
7404 if you are piping more than one message.
7405 <P>
7406 The sub-command options are:
7407 <DL>
7408 <DT>Shown Text or Raw Text</DT>
7409 <DD>This option toggles between sending the shown (processed) text
7410 of the message to the Unix command, and sending the
7411 raw (unprocessed) text of the message to the Unix command.
7412 The default is to send the shown text.
7413 The raw version of the message will contain all of the headers and any
7414 MIME encoding that the message contains.
7415 If you've selected the Raw Text then the prompt will have the additional word
7416 "RAW" in it, like
7417 <P>
7418 <CENTER><SAMP>Pipe RAW messages to :</SAMP></CENTER>
7419 <P>
7420 You can experiment with this option by piping to something simple like the
7421 Unix "cat" command.
7422 </DD>
7423 <DT>Captured Output or Free Output</DT>
7424 <DD>This option toggles between having Alpine capture the output of
7425 the Unix pipe command for display, and not capturing it.
7426 If the command you are piping to is a filter that will produce output
7427 you want to view, then you want to capture that output
7428 for display (the default).
7429 If the Unix command doesn't produce output or handles the display itself,
7430 then you want free output.
7431 When you've selected the Free Output option the prompt will change to
7432 <P>
7433 <CENTER><SAMP>Pipe messages to (uncaptured) :</SAMP></CENTER>
7434 <P>
7435 </DD>
7436 <DT>No Delimiter or With Delimiter</DT>
7437 <DD>This option controls whether or not a Unix mailbox style delimiter
7438 will come before the text of the message.
7439 This is the delimiter used in the common Unix mailbox format.
7440 It's the single line that begins with the five characters
7441 "From" followed by a <SPACE> character.
7442 You'll usually only want to include this if the Unix command requires
7443 input in the format of a traditional Unix mailbox file.
7444 When you've selected the With Delimiter option the prompt will change to
7445 <P>
7446 <CENTER><SAMP>Pipe messages to (delimited) :</SAMP></CENTER>
7447 <P>
7448 </DD>
7449 <DT>To Same Pipe or To Individual Pipes</DT>
7450 <DD>This option only shows up if you are running an aggregate
7451 pipe command.
7452 That is, the command was Apply Pipe, not just Pipe.
7453 You have the option of piping all of the selected messages through a
7454 single pipe to a single instance of the Unix command,
7455 or piping each individual message through a separate pipe to separate
7456 instances of the Unix command.
7457 The default is that all of the output will go through a single pipe
7458 to a single instance of the command.
7459 You can try this option with a command like "less", with Free
7460 Output enabled.
7461 When you've selected the Individual Pipes option the prompt will change to
7462 <P>
7463 <CENTER><SAMP>Pipe messages to (new pipe) :</SAMP></CENTER>
7464 <P>
7465 </DD>
7466 </DL>
7468 <P>
7469 As mentioned earlier, the options can be combined in any way you wish.
7470 You may leave them all off, turn them all on, or turn some of them on
7471 and some of them off.
7472 If you use the pipe command a second time in the same session the default
7473 options will be what you used the last time.
7475 <P>
7476 <End of help on this topic>
7477 </BODY>
7478 </HTML>
7479 ========== h_emptydir_subfolder_name =========
7480 <HTML>
7481 <HEAD>
7482 <TITLE>ENTER SUBFOLDER NAME</TITLE>
7483 </HEAD>
7484 <BODY>
7485 <H1>Enter Subfolder Name</H1>
7487 <P>
7488 This is the name of a new subfolder in the directory you are creating.
7489 Because empty directories are hidden and therefore not useful, you must also
7490 create a subfolder in the directory you are creating in order that the
7491 directory remains visible.
7492 <P>
7493 Alternatively, you may turn off the configuration feature
7494 <A HREF="h_config_quell_empty_dirs"><!--#echo var="FEAT_quell-empty-directories"--></A>
7495 so that empty directories remain visible.
7496 If you do that, you will not be required to create the subfolder when you
7497 create a directory.
7499 <P>
7500 <End of help on this topic>
7501 </BODY>
7502 </HTML>
7503 ========== h_incoming_add_folder_name =========
7504 <HTML>
7505 <HEAD>
7506 <TITLE>ENTER FOLDER NAME</TITLE>
7507 </HEAD>
7508 <BODY>
7509 <H1>Enter Folder Name</H1>
7511 <P>
7512 This is the name of the folder on the previously specified server.
7513 By default the folder name is interpreted as defining a section of your personal
7514 folder area. This area and how you specify it are defined by the
7515 server, if one is specified.
7517 <P>
7518 To define a folder outside the default area, prefix
7519 the path with the namespace to use when interpreting the
7520 given path. If a namespace is specified, the folder name begins with the
7521 sharp (#) character followed by the name of the namespace
7522 and then the namespace's path-element-delimiter. Aside from the
7523 name's format, namespaces can also imply access rights, content
7524 policy, audience, location, and, occasionally, access methods.
7526 <P>
7527 Each server exports its own set (possibly of size one) of
7528 namespaces.
7529 For a more detailed explanation read about
7530 <A HREF="h_folder_name_namespaces">Namespaces</A>.
7532 <P>
7533 To specify the default for INBOX on the server you can usually just enter
7534 "INBOX", and the server will understand the special meaning of
7535 that word.
7537 <P>
7538 <End of help on this topic>
7539 </BODY>
7540 </HTML>
7541 ========== h_incoming_add_folder_host =========
7542 <HTML>
7543 <HEAD>
7544 <TITLE>ENTER INCOMING FOLDER SERVER</TITLE>
7545 </HEAD>
7546 <BODY>
7547 <H1>Enter Incoming Folder Server</H1>
7549 You are being asked for the name of the server for use with this incoming
7550 folder.
7551 If the folder is on the machine where Alpine is running, then just enter
7552 RETURN without typing a server name.
7554 <P>
7555 If the folder is on an IMAP server then type the server's name followed
7556 by RETURN.
7557 You may use the ^X command if the server is the same as the server that
7558 the INBOX is on.
7560 <P>
7561 You may have to add optional extra information to the server name.
7562 For example, if the IMAP server is using a non-standard port number you
7563 would specify that by appending a colon (:) followed by the port number
7564 to the server name
7566 <P>
7567 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7568 <P>
7570 or you may need to specify a different protocol if the server is not an
7571 IMAP server. For example:
7573 <P>
7574 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7575 <P>
7577 for a POP server or
7579 <P>
7580 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7581 <P>
7583 for an NNTP news server.
7584 For an explanation of all of the possibilities, see
7585 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7586 for folders.
7588 <P>
7589 There is a special command (^W) if you want to set up a folder that gets its
7590 mail from a
7591 <A HREF="h_maildrop">Mail Drop</A>.
7592 If you type that command, you will be prompted for the information for
7593 both the Mail Drop folder and the destination folder.
7595 <P>
7596 <End of help on this topic>
7597 </BODY>
7598 </HTML>
7599 ========== h_incoming_add_inbox =========
7600 <HTML>
7601 <HEAD>
7602 <TITLE>ENTER INBOX SERVER</TITLE>
7603 </HEAD>
7604 <BODY>
7605 <H1>Enter INBOX Server</H1>
7607 You are being asked for the name of the server for use with
7608 the INBOX folder.
7609 Type the server's name followed by RETURN.
7611 <P>
7612 You may have to add optional extra information to the server name.
7613 For example, if the server is using a non-standard port number you
7614 would specify that by appending a colon (:) followed by the port number
7615 to the server name
7617 <P>
7618 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7619 <P>
7621 or you may need to specify a different protocol if the server is not an
7622 IMAP server. For example:
7624 <P>
7625 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7626 <P>
7628 for a POP server.
7629 <P>
7631 For an explanation of all of the possibilities, see
7632 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7633 for folders.
7635 <P>
7636 If the INBOX folder is on the machine where Alpine is running, then just enter
7637 RETURN without typing a server name.
7639 <P>
7640 There is a special command (^W) if you want to set up a folder that gets its
7641 mail from a
7642 <A HREF="h_maildrop">Mail Drop</A>.
7643 If you type that command, you will be prompted for the information for
7644 both the Mail Drop folder and the destination folder, which will be used
7645 as your INBOX folder.
7647 <P>
7648 <End of help on this topic>
7649 </BODY>
7650 </HTML>
7651 ========== h_incoming_add_maildrop_destn =========
7652 <HTML>
7653 <HEAD>
7654 <TITLE>ENTER DESTINATION SERVER</TITLE>
7655 </HEAD>
7656 <BODY>
7657 <H1>Enter Destination Server</H1>
7659 You are being asked for the name of the server where the destination
7660 folder is for use with this Mail Drop incoming folder.
7661 That is, you are using a Mail Drop for this incoming folder and
7662 you've already entered
7663 the server and folder name for the Mail Drop.
7664 Now you need to enter the server for the destination folder
7665 where the mail should be copied to.
7666 Mail will come from the Mail Drop and be copied to the destination folder.
7668 <P>
7669 Type the server's name followed by RETURN.
7670 If the folder is local to this computer, just type RETURN without entering
7671 a server name.
7673 <P>
7674 You may have to add optional extra information to the server name.
7675 For example, if the server is using a non-standard port number you
7676 would specify that by appending a colon (:) followed by the port number
7677 to the server name
7679 <P>
7680 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7681 <P>
7683 For an explanation of all of the possibilities, see
7684 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7685 for folders.
7687 <P>
7688 <End of help on this topic>
7689 </BODY>
7690 </HTML>
7691 ========== h_inbox_add_maildrop_destn =========
7692 <HTML>
7693 <HEAD>
7694 <TITLE>ENTER DESTINATION SERVER</TITLE>
7695 </HEAD>
7696 <BODY>
7697 <H1>Enter Destination Server</H1>
7699 You are being asked for the name of the server where the destination
7700 folder is for use with your Mail Drop INBOX.
7701 That is, you are using a Mail Drop for your INBOX and you've already entered
7702 the server and folder name for the Mail Drop.
7703 Now you need to enter the server for the destination folder
7704 where the mail should be copied to.
7705 Mail will come from the Mail Drop and be copied to the destination folder.
7707 <P>
7708 Type the server's name followed by RETURN.
7709 If the folder is local to this computer, just type RETURN without entering
7710 a server name.
7712 <P>
7713 You may have to add optional extra information to the server name.
7714 For example, if the server is using a non-standard port number you
7715 would specify that by appending a colon (:) followed by the port number
7716 to the server name
7718 <P>
7719 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7720 <P>
7722 For an explanation of all of the possibilities, see
7723 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7724 for folders.
7726 <P>
7727 <End of help on this topic>
7728 </BODY>
7729 </HTML>
7730 ========== h_inbox_add_maildrop =========
7731 <HTML>
7732 <HEAD>
7733 <TITLE>ENTER MAILDROP SERVER</TITLE>
7734 </HEAD>
7735 <BODY>
7736 <H1>Enter Mail Drop Server</H1>
7738 You are being asked for the name of the Mail Drop server for use with
7739 your INBOX.
7741 <P>
7742 Type the server's name followed by RETURN.
7744 <P>
7745 You may have to add optional extra information to the server name.
7746 For example, if the server is using a non-standard port number you
7747 would specify that by appending a colon (:) followed by the port number
7748 to the server name
7750 <P>
7751 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7752 <P>
7754 or you may need to specify a different protocol if the server is not an
7755 IMAP server. For example:
7757 <P>
7758 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7759 <P>
7761 for a POP server or
7763 <P>
7764 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7765 <P>
7767 for an NNTP news server.
7768 For an explanation of all of the possibilities, see
7769 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7770 for folders.
7772 <P>
7773 <End of help on this topic>
7774 </BODY>
7775 </HTML>
7776 ========== h_incoming_add_maildrop =========
7777 <HTML>
7778 <HEAD>
7779 <TITLE>ENTER MAILDROP SERVER</TITLE>
7780 </HEAD>
7781 <BODY>
7782 <H1>Enter Mail Drop Server</H1>
7784 You are being asked for the name of the Mail Drop server for use with
7785 this incoming folder.
7787 <P>
7788 Type the server's name followed by RETURN.
7789 You may use the ^X command if the server is the same as the server that
7790 the INBOX is on.
7792 <P>
7793 You may have to add optional extra information to the server name.
7794 For example, if the server is using a non-standard port number you
7795 would specify that by appending a colon (:) followed by the port number
7796 to the server name
7798 <P>
7799 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7800 <P>
7802 or you may need to specify a different protocol if the server is not an
7803 IMAP server. For example:
7805 <P>
7806 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7807 <P>
7809 for a POP server or
7811 <P>
7812 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7813 <P>
7815 for an NNTP news server.
7816 For an explanation of all of the possibilities, see
7817 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7818 for folders.
7820 <P>
7821 If the Mail Drop folder is on the machine where Alpine is running, then just enter
7822 RETURN without typing a server name.
7824 <P>
7825 <End of help on this topic>
7826 </BODY>
7827 </HTML>
7828 ========== h_maildrop =========
7829 <HTML>
7830 <HEAD>
7831 <TITLE>WHAT IS A MAIL DROP?</TITLE>
7832 </HEAD>
7833 <BODY>
7834 <H1>What is a Mail Drop?</H1>
7836 In some situaions it may make sense to have your mail delivered to one
7837 folder (the Mail Drop) and then when you want to read mail that has been
7838 delivered to the Mail Drop folder Alpine will move it to another
7839 destination folder.
7840 Often the Mail Drop will be a remote folder and messages will be moved from
7841 there to a local destination folder.
7843 <P>
7844 One example where this might make sense is if the Mail Drop folder is accessible
7845 only with the POP protocol.
7846 You could designate your POP inbox as the Mail Drop folder and have Alpine move
7847 mail from there to a local (on the same machine Alpine is running on)
7848 destination folder, where you'll read it.
7850 <P>
7851 A Mail Drop may only be used as your Inbox or as an
7852 <A HREF="h_config_enable_incoming">"Incoming folder"</A>.
7854 <P>
7855 There is no attempt to synchronize the contents of the destination folder
7856 with the contents of the Mail Drop folder.
7857 All that happens is that all of the messages in the Mail Drop folder are
7858 copied to the destination folder and then they are deleted and expunged (if possible)
7859 from the Mail Drop folder.
7860 The next time a check for new mail is made, any messages in the Mail
7861 Drop folder are once again copied to the destination folder and deleted
7862 and expunged from the Mail Drop folder.
7863 (If the Mail Drop folder is a news group, then the messages can't be
7864 expunged from the newsgroup. Instead, only Recent messages are copied from
7865 the newsgroup to the destination folder.)
7867 <P>
7868 Configuration of a Mail Drop is a little different from configuration of
7869 a folder that does not use a Mail Drop because you have to specify two
7870 folder names instead of one.
7871 The two folders may be any types of folders that Alpine can normally use.
7872 They don't have to be a remote folder and a local folder, that is
7873 simply the most common usage.
7874 When you use a Mail Drop folder Alpine will periodically re-open the Mail
7875 Drop to check for new mail.
7876 The new-mail checks will happen at the frequency set with the
7877 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option,
7878 but with a minimum time
7879 (<A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>)
7880 between checks.
7881 Because of this minimum you may notice that new mail does not
7882 appear promptly when you expect it.
7883 The reason for this is to protect the server from over-zealous opening and
7884 closing of the Mail Drop folder.
7885 If the user initiates the check by typing ^L (Ctrl-L) or the Next command when at
7886 the end of the folder index, then the check will happen, regardless of how
7887 long it has been since the previous check.
7888 <P>
7889 If there is new mail, that mail will be copied to the destination folder
7890 and then will be deleted from the Mail Drop.
7891 Note that using a Mail Drop with a local destination folder does not make
7892 sense if you read mail from more than one machine, because the mail is
7893 downloaded to the destination folder (which is accessible from only one
7894 machine) and deleted from the Mail Drop.
7895 <P>
7896 The feature <A HREF="h_config_maildrops_preserve_state"><!--#echo var="FEAT_maildrops-preserve-state"--></A> modifies the operation of Mail Drops.
7898 <P>
7899 The actual syntax used by Alpine for a folder that uses a Mail Drop is:
7901 <P>
7902 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
7903 <P>
7904 The brackets are not literal.
7905 <P>
7906 <CENTER><SAMP><DELIM></SAMP></CENTER>
7907 <P>
7908 is a single character that does not appear in the MailDropFolder name.
7909 If the name doesn't contain spaces then it can be a space character.
7910 The two folder names are full technical
7911 <A HREF="h_valid_folder_names">folder names</A>
7912 as used by Alpine.
7913 Here are a couple examples to give you an idea what is being talked about:
7915 <P>
7916 <CENTER><SAMP>#move {popserver.example.com/pop3}inbox localfolder</SAMP></CENTER>
7917 <P>
7918 <CENTER><SAMP>#move+{nntpserver.example.com/nntp}#news.comp.mail.pine+local folder</SAMP></CENTER>
7919 <P>
7921 A #move folder may only be used as an
7922 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
7923 an Inbox.
7924 When you are in the FOLDER LIST of Incoming Message Folders (after turning
7925 on the
7926 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
7927 option)
7928 the Add command has a subcommand "Use Mail Drop"
7929 which may be helpful for defining the folder in your Alpine configuration.
7930 The same is true when you edit the
7931 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
7932 option in Setup/Config.
7933 Each of these configuration methods will also create the DestinationFolder
7934 if it doesn't already exist.
7935 If you are having problems, make sure the DestinationFolder exists.
7937 <P>
7938 <End of help on this topic>
7939 </BODY>
7940 </HTML>
7941 ========== h_save =========
7942 <HTML>
7943 <HEAD>
7944 <TITLE>CHOOSE A FOLDER TO SAVE INTO</TITLE>
7945 </HEAD>
7946 <BODY>
7947 <H1>Choose a Folder to Save Into</H1>
7949 After Exiting from this help text,
7950 type the name of the folder you want to save into and press RETURN.
7951 <P>
7952 Press ^T to get a list of your folders to choose from.
7953 Press ^C to cancel the Save.
7954 <P>
7955 If you have Folder Collections defined you may use
7956 Ctrl-P (Previous collection) and Ctrl-N (Next collection) to switch
7957 the collection being saved to.
7958 <P>
7959 If Tab Completion is enabled (it is enabled by default)
7960 you may type a Tab character to have Alpine complete the folder name for you.
7961 <P>
7962 If Partial Match Lists is enabled (it is enabled by default) you may type
7963 Ctrl-X to get a list of matches to the prefix you've typed in so far.
7964 <P>
7965 If the Ctrl-R subcommand is present that means you can decide to Delete or
7966 not Delete the message you are saving after you save it.
7967 The label on that key gives the action to switch to.
7968 If it says Delete and you type Ctrl-R the label displayed will change to
7969 No Delete and the source message will be deleted after the save. If it
7970 says No Delete and you type Ctrl-R the label displayed will change to
7971 Delete and the message will not be deleted.
7972 You can control the default for the Delete parameter with the
7973 configuration feature <!--#echo var="FEAT_save-will-not-delete"-->.
7974 <P>
7975 Similarly, if the Ctrl-W subcommand is present that means you can decide
7976 to Preserve the order of the messages being saved or not.
7977 If it is labeled Preserve Order and you type Ctrl-W, the resulting Saved messages
7978 will be in the same order as you see them in the source folder now.
7979 The opposite action (which is usually the default) is that you don't care
7980 about the order.
7981 The Saved messages may or may not be in the same order in the destination folder.
7982 There may be a performance penalty for choosing to save the messages in order.
7983 You can control the default for the Preserve Order parameter with the
7984 configuration feature
7985 <!--#echo var="FEAT_save-aggregates-copy-sequence"-->.
7987 <P>
7988 If you haven't disabled the Save Input History and you've already done a
7989 Save earlier in this session then you may use the Up and Down arrows to retrieve
7990 a folder name used in a previous Save.
7992 <P>
7993 <End of help on this topic>
7994 </BODY>
7995 </HTML>
7996 ============= h_simple_index ========================
7997 <HTML>
7998 <HEAD>
7999 <TITLE>SELECT POSTPONED MESSAGE</TITLE>
8000 </HEAD>
8001 <BODY>
8002 <H1>POSTPONED MESSAGE SELECTION COMMANDS</H1>
8003 <!--chtml if pinemode="function_key"-->
8004 <PRE>
8005 Navigating the List of Messages General Alpine Commands
8006 ------------------------------- -----------------------
8007 F5 Move to previous message F1 Show this help text
8008 F6 Move to next message
8009 F7 Show previous screen of messages
8010 F8 Show next screen of messages
8012 Message Selection Commands
8013 --------------------------
8014 F3 Exit the Message Select menu (canceling Send command)
8015 F4 Select the currently highlighted message
8016 F9 Mark the currently highlighted message as deleted
8017 F10 Undelete (remove deletion mark from) the highlighted message
8018 </PRE>
8019 <!--chtml else-->
8020 <PRE>
8021 Navigating the List of Messages General Alpine Commands
8022 ------------------------------- -----------------------
8023 P Move to previous message ? Show this help text
8024 N Move to next message
8025 - Show previous screen of messages
8026 Spc (space bar) Show next screen of messages
8028 Message Selection Commands
8029 --------------------------
8030 E Exit the Message Select menu (canceling Send command)
8031 S Select the currently highlighted message
8032 D Mark the currently highlighted message as deleted
8033 U Undelete (remove deletion mark from) the highlighted message
8034 </PRE>
8035 <!--chtml endif-->
8036 <P>
8037 <H2>Description of the Select Postponed Message Screen</H2>
8039 This screen allows you to select one of several previously postponed
8040 messages in order to continue composition. Your options are very limited
8041 -- the screen is not meant to let you manipulate these messages. However,
8042 you may now delete messages from this list. Once you choose a message,
8043 Alpine reads it in and puts you into the regular message composer.
8044 <P>
8046 Messages do not stay in this postponed state automatically. If you select
8047 a message and then want to postpone it again, use the normal postpone
8048 (Ctrl-O) command in the composer.
8049 <P>
8051 If you exit this screen without selecting a message, the Compose command
8052 that got you here is canceled. Other than messages explicitly marked
8053 "Deleted", no messages will be removed.
8055 <P>
8056 <End of help on this topic>
8057 </BODY>
8058 </HTML>
8059 ============= h_collection_screen ========================
8060 <HTML>
8061 <HEAD>
8062 <TITLE>COLLECTION LIST screen</TITLE>
8063 </HEAD>
8064 <BODY>
8065 <H1>COLLECTION LIST screen</H1>
8067 The COLLECTION LIST screen is used to select one of your
8068 collection definitions to display the folders they contain. See
8069 <A HREF="h_what_are_collections">Folder Collections Explained</A> for
8070 detailed explanation of collections.<P>
8072 To manage your collection definitions (Add, Change, Delete, etc.), use
8073 the <A HREF="h_collection_maint">Setup/collectionList</A> command on Alpine's
8074 MAIN MENU.
8076 <P>
8077 <End of help on this topic>
8078 </BODY>
8079 </HTML>
8080 ============= h_collection_maint ========================
8081 <HTML>
8082 <HEAD>
8083 <TITLE>SETUP COLLECTION LIST screen</TITLE>
8084 </HEAD>
8085 <BODY>
8086 <H1>SETUP COLLECTION LIST screen</H1>
8088 The SETUP COLLECTION LIST screen lets you manage your collection
8089 definitions. See
8090 <A HREF="h_what_are_collections">Folder Collections Explained</A>
8091 for detailed explanation of collections.<P>
8093 Maintenance commands include:
8094 <DL>
8095 <DT>Change
8096 <!--chtml if pinemode="function_key"-->
8097 (F4)
8098 <!--chtml else-->
8099 (C)
8100 <!--chtml endif-->
8101 </DT>
8103 <DD>Modify attributes of the selected collection definition.
8105 <DT>Add Cltn
8106 <!--chtml if pinemode="function_key"-->
8107 (F9)
8108 <!--chtml else-->
8109 (A)
8110 <!--chtml endif-->
8111 </DT>
8113 <DD>Create a new collection definition.
8114 </DD>
8116 <DT>Del Cltn
8117 <!--chtml if pinemode="function_key"-->
8118 (F10)
8119 <!--chtml else-->
8120 (D)
8121 <!--chtml endif-->
8122 </DT>
8124 <DD>Delete the selected collection definition.<BR>
8125 NOTE: The folders and directories referred to by the
8126 collection definition are <EM>NOT</EM> deleted. Folders must
8127 be deleted, if that's what you wish to do, from the
8128 <A HREF="h_folder_maint">FOLDER LIST screen</A>, which shows the
8129 individual folders in a collection.
8130 </DD>
8132 <DT>Shuffle
8133 <!--chtml if pinemode="function_key"-->
8134 (F11)
8135 <!--chtml else-->
8136 ($)
8137 <!--chtml endif-->
8138 </DT>
8140 <DD>Change the order of the displayed collections. Alpine will offer
8141 to move the currently selected collection one position UP
8142 or DOWN.
8143 </DD>
8144 </DL>
8146 <P>
8147 <End of help on this topic>
8148 </BODY>
8149 </HTML>
8150 ============ h_what_are_collections ==========
8151 <HTML>
8152 <HEAD>
8153 <TITLE>Folder Collections Explained</TITLE>
8154 </HEAD>
8155 <BODY>
8156 <H1>Folder Collections Explained</H1>
8159 Those of you with simple mail configurations will just see a list of all the
8160 folders you have when choosing FOLDER LIST from Alpine's MAIN MENU.
8161 The special folders for INBOX, sent mail and saved messages
8162 will appear at the top of the list. All others are in alphabetical order.
8163 <P>
8164 If you
8165 or your system administrator have defined more than one collection or if
8166 you have a collection (for newsgroups or email folders) defined on your
8167 system, then you will see the COLLECTION LIST screen first when choosing
8168 FOLDER LIST from Alpine's MAIN MENU.
8169 <P>
8170 <H2>Why have multiple folder collections?</H2>
8171 <P>
8172 For Alpine users who only maintain email folders (and not too many) on one host,
8173 a single folder collection is probably sufficient.<P>
8175 However, people who have more than one email account - for example, one
8176 at their university, and one with their personal Internet Service Provider -
8177 will have different sets of folders on different hosts, and they may want to
8178 access them all from the same installation of Alpine, rather than use different
8179 software and/or log into other hosts to manipulate messages in different
8180 accounts. (If in doubt whether one of your email accounts can be accessed
8181 with Alpine, contact the technical support people for that account.) Even people
8182 who have only one email account on one host, but have dozens or
8183 hundreds of email folders, may want to arrange these folders together in a
8184 meaningful way.<BR>
8185 That is where multiple collections come in.
8187 <H2>Types of Collections</H2>
8188 <DL>
8189 <DT>INCOMING FOLDERS</DT>
8190 <DD>"Incoming Message Folders"
8191 is a special collection typically used to supplement your single INBOX.
8192 All the folders here are meant to be ones that receive incoming messages,
8193 which you intend to check more or less frequently.
8194 You may have multiple folders like this because you or your systems
8195 administrator have set up an external program or you may have set up
8196 Alpine to filter incoming
8197 messages into different folders, based on certain criteria such as
8198 sender, recipient, or subject; or because you have multiple accounts and
8199 wish to check their INBOXes easily. This collection is established by
8200 setting the
8201 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
8202 feature in the SETUP CONFIGURATION screen, which is accessed from the
8203 MAIN MENU.
8204 </DD>
8206 <DT>NEWS</DT>
8207 <DD>You can also define a collection specifically for
8208 newsgroups. Alpine does this for you implicitly when you
8209 <A HREF="h_config_nntp_server">define an NNTP Server</A>
8210 in your Alpine configuration. The news collection appears last in the
8211 COLLECTION LIST (though you can shuffle it up in the order of presentation),
8212 and Alpine knows not to save messages there.
8213 </DD>
8215 <DT>DEFAULT COLLECTION</DT>
8216 <DD>This is the default collection for your saved and sent messages folders.
8217 </DD>
8218 </DL>
8220 <P>
8222 <H2>Defining Collections</H2>
8223 <P>
8224 In the absence of any folder-collection definitions, Alpine will assume a
8225 single default folder collection.
8226 <!--chtml if pinemode="os_windows"-->
8227 <!--chtml else-->
8228 If necessary, Alpine will create the directory
8229 "mail" in your Unix home directory
8230 to hold your folders.
8231 <!--chtml endif-->
8232 <P>
8233 You can use the
8234 <A HREF="h_collection_maint">Setup/collectionList screen</A>, called up from
8235 the MAIN MENU, to manage your collection list.
8236 <P>
8237 <End of help on this topic>
8238 </BODY>
8239 </HTML>
8240 ===== h_select_address_screen =====
8241 <HTML>
8242 <HEAD>
8243 <TITLE>SELECT AN ADDRESS SCREEN</TITLE>
8244 </HEAD>
8245 <BODY>
8246 <H1>SELECT AN ADDRESS SCREEN</H1>
8247 <H2>COMMANDS</H2>
8248 <!--chtml if pinemode="function_key"-->
8249 <PRE>
8250 Available Commands
8251 -------------------------------
8252 F1 Show Help Text
8253 F3 Exit without selecting anything
8254 F4 Select the highlighted address
8255 F5 Move highlight to previous address
8256 F6 Move highlight to next address
8257 F7 Previous page of addresses
8258 F8 Next page of addresses
8259 F11 Print
8260 F12 WhereIs
8261 </PRE>
8262 <!--chtml else-->
8263 <PRE>
8264 Navigation General Alpine Commands
8265 ------------------------- -----------------------
8266 P Prev Address ? Display this help text
8267 N Next Address E Exit without selecting anything
8268 - Previous page % Print
8269 Spc (space bar) Next page
8270 W WhereIs
8272 Select Command
8273 ------------------------------------------------
8274 S Select the highlighted address
8275 </PRE>
8276 <!--chtml endif-->
8278 <H2>Description of the Select Address Screen</H2>
8280 This screen gives you an easy way to select an address from all of
8281 the address book entries that match the prefix typed so far.
8283 <P><UL>
8284 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8285 </UL>
8286 <P>
8287 <End of help on this topic>
8288 </BODY>
8289 </HTML>
8290 ===== h_select_rule_screen =====
8291 <HTML>
8292 <HEAD>
8293 <TITLE>SELECT A RULE SCREEN</TITLE>
8294 </HEAD>
8295 <BODY>
8296 <H1>SELECT A RULE SCREEN</H1>
8297 <H2>COMMANDS</H2>
8298 <!--chtml if pinemode="function_key"-->
8299 <PRE>
8300 Available Commands
8301 -------------------------------
8302 F1 Show Help Text
8303 F3 Exit without selecting anything
8304 F4 Select the highlighted rule
8305 F5 Move highlight to previous rule
8306 F6 Move highlight to next rule
8307 F7 Previous page of rules
8308 F8 Next page of rules
8309 F11 Print
8310 F12 WhereIs
8311 </PRE>
8312 <!--chtml else-->
8313 <PRE>
8314 Navigation General Alpine Commands
8315 ------------------------- -----------------------
8316 P Prev Rule ? Display this help text
8317 N Next Rule E Exit without selecting anything
8318 - Previous page % Print
8319 Spc (space bar) Next page
8320 W WhereIs
8322 Select Command
8323 ------------------------------------------------
8324 S Select the highlighted rule
8325 </PRE>
8326 <!--chtml endif-->
8328 <H2>Description of the Select Rule Screen</H2>
8330 This screen just gives you an easy way to select a rule from all of your
8331 defined rules.
8332 The list of rules presented is the list of nicknames of all of the rules
8333 defined using Setup/Rules.
8334 For selecting messages, it is likely that the Indexcolor rules and possibly
8335 the Roles rules will be most useful.
8336 The others are there also, in case you find a use for them.
8337 <P>
8338 In order for this to be useful for selecting messages, the nicknames of
8339 the rules have to be different.
8340 Alpine actually just gets the nickname of the rule that you select and then
8341 looks up that rule using the nickname.
8342 So if there are duplicate nicknames, the first rule that has that
8343 nickname will be used.
8345 <P><UL>
8346 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8347 </UL>
8348 <P>
8349 <End of help on this topic>
8350 </BODY>
8351 </HTML>
8352 ===== h_select_priority_screen =====
8353 <HTML>
8354 <HEAD>
8355 <TITLE>SELECT A PRIORITY SCREEN</TITLE>
8356 </HEAD>
8357 <BODY>
8358 <H1>SELECT A PRIORITY SCREEN</H1>
8359 <H2>COMMANDS</H2>
8360 <!--chtml if pinemode="function_key"-->
8361 <PRE>
8362 Available Commands
8363 -------------------------------
8364 F1 Show Help Text
8365 F3 Exit without selecting anything
8366 F4 Select the highlighted priority
8367 F5 Move highlight to previous priority
8368 F6 Move highlight to next priority
8369 F7 Previous page of priorities
8370 F8 Next page of priorities
8371 F11 Print
8372 F12 WhereIs
8373 </PRE>
8374 <!--chtml else-->
8375 <PRE>
8376 Navigation General Alpine Commands
8377 ------------------------- -----------------------
8378 P Prev Priority ? Display this help text
8379 N Next Priority E Exit without selecting anything
8380 - Previous page % Print
8381 Spc (space bar) Next page
8382 W WhereIs
8384 Select Command
8385 ------------------------------------------------
8386 S Select the highlighted priority
8387 </PRE>
8388 <!--chtml endif-->
8390 <H2>Description of the Select Priority Screen</H2>
8392 This screen gives you a way to select a priority for the message you are sending.
8393 This priority will be placed in the non-standard X-Priority header of your outgoing mail.
8394 Some mail programs will display an indication of the priority level to
8395 the recipient of the message, some will ignore it.
8396 Even in cases where the mail programs of both the sender and the recipient
8397 agree on the meaning of this header, keep in mind that it is
8398 something that the sender sets so it is only an indication
8399 of the priority that the sender attaches to the mail.
8400 Alpine can be made to display an indication of this priority in incoming
8401 messages by use of one of the tokens
8402 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
8403 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
8404 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
8406 <P><UL>
8407 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8408 </UL>
8409 <P>
8410 <End of help on this topic>
8411 </BODY>
8412 </HTML>
8413 ===== h_select_keyword_screen =====
8414 <HTML>
8415 <HEAD>
8416 <TITLE>SELECT A KEYWORD SCREEN</TITLE>
8417 </HEAD>
8418 <BODY>
8419 <H1>SELECT A KEYWORD SCREEN</H1>
8420 <H2>COMMANDS</H2>
8421 <!--chtml if pinemode="function_key"-->
8422 <PRE>
8423 Available Commands
8424 -------------------------------
8425 F1 Show Help Text
8426 F3 Exit without selecting anything
8427 F4 Select the highlighted keyword
8428 F5 Move highlight to previous keyword
8429 F6 Move highlight to next keyword
8430 F7 Previous page of keywords
8431 F8 Next page of keywords
8432 F11 Print
8433 F12 WhereIs
8434 </PRE>
8435 <!--chtml else-->
8436 <PRE>
8437 Navigation General Alpine Commands
8438 ------------------------- -----------------------
8439 P Prev Keyword ? Display this help text
8440 N Next Keyword E Exit without selecting anything
8441 - Previous page % Print
8442 Spc (space bar) Next page
8443 W WhereIs
8445 Select Command
8446 ------------------------------------------------
8447 S Select the highlighted keyword
8448 </PRE>
8449 <!--chtml endif-->
8451 <H2>Description of the Select Keyword Screen</H2>
8453 This screen just gives you an easy way to select a keyword.
8454 The list of keywords presented is the list of all keywords defined in your
8455 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8456 If you have given a keyword a nickname, that nickname is displayed
8457 instead of the actual keyword.
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_charset_screen =====
8467 <HTML>
8468 <HEAD>
8469 <TITLE>SELECT A CHARACTER SET SCREEN</TITLE>
8470 </HEAD>
8471 <BODY>
8472 <H1>SELECT A CHARACTER SET 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 character set
8481 F5 Move highlight to previous character set
8482 F6 Move highlight to next character set
8483 F7 Previous page of character sets
8484 F8 Next page of character sets
8485 F11 Print
8486 F12 WhereIs
8487 </PRE>
8488 <!--chtml else-->
8489 <PRE>
8490 Navigation General Alpine Commands
8491 ------------------------- -----------------------
8492 P Prev Character Set ? Display this help text
8493 N Next Character Set 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 character set
8501 </PRE>
8502 <!--chtml endif-->
8504 <H2>Description of the Select A Character Set Screen</H2>
8506 This screen just gives you an easy way to select a character set from the
8507 set of character sets Alpine knows about.
8508 The list presented will vary slightly depending on what option you are
8509 selecting the character set for.
8511 <P><UL>
8512 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8513 </UL>
8514 <P>
8515 <End of help on this topic>
8516 </BODY>
8517 </HTML>
8518 ===== h_select_multcharsets_screen =====
8519 <HTML>
8520 <HEAD>
8521 <TITLE>SELECT CHARACTER SETS SCREEN</TITLE>
8522 </HEAD>
8523 <BODY>
8524 <H1>SELECT CHARACTER SETS SCREEN</H1>
8525 <H2>COMMANDS</H2>
8526 <!--chtml if pinemode="function_key"-->
8527 <PRE>
8528 Available Commands
8529 -------------------------------
8530 F1 Show Help Text
8531 F3 Exit without selecting anything
8532 F4 Select the highlighted charset (or chosen charsets in ListMode)
8533 F5 Move highlight to previous charset
8534 F6 Move highlight to next charset
8535 F7 Previous page of charsets
8536 F8 Next page of charsets
8537 F9 Toggle choices when using ListMode
8538 F10 Turn on/off ListMode (makes it easy to choose multiple charsets)
8539 F11 Print
8540 F12 WhereIs
8541 </PRE>
8542 <!--chtml else-->
8543 <PRE>
8544 Navigation General Alpine Commands
8545 ------------------------- -----------------------
8546 P Prev Charset ? Display this help text
8547 N Next Charset E Exit without selecting anything
8548 - Previous page % Print
8549 Spc (space bar) Next page
8550 W WhereIs
8552 Select Command
8553 ------------------------------------------------
8554 S Select the highlighted charset (or chosen charsets in ListMode)
8555 L Turn on ListMode (makes it easy to choose multiple charsets)
8556 1 Turn off ListMode
8557 X Toggle choices when using ListMode
8558 </PRE>
8559 <!--chtml endif-->
8561 <H2>Description of the Select Character Set Screen</H2>
8563 This screen just gives you an easy way to select a character set or a list of
8564 character sets.
8565 The list of character sets presented is the list of all character sets known to
8566 Alpine.
8567 You may select other character sets by typing them in directly.
8569 <P><UL>
8570 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8571 </UL>
8572 <P>
8573 <End of help on this topic>
8574 </BODY>
8575 </HTML>
8576 ===== h_select_multkeyword_screen =====
8577 <HTML>
8578 <HEAD>
8579 <TITLE>SELECT KEYWORDS SCREEN</TITLE>
8580 </HEAD>
8581 <BODY>
8582 <H1>SELECT KEYWORDS SCREEN</H1>
8583 <H2>COMMANDS</H2>
8584 <!--chtml if pinemode="function_key"-->
8585 <PRE>
8586 Available Commands
8587 -------------------------------
8588 F1 Show Help Text
8589 F3 Exit without selecting anything
8590 F4 Select the highlighted keyword (or chosen keywords in ListMode)
8591 F5 Move highlight to previous keyword
8592 F6 Move highlight to next keyword
8593 F7 Previous page of keywords
8594 F8 Next page of keywords
8595 F9 Toggle choices when using ListMode
8596 F10 Turn on/off ListMode (makes it easy to choose multiple keywords)
8597 F11 Print
8598 F12 WhereIs
8599 </PRE>
8600 <!--chtml else-->
8601 <PRE>
8602 Navigation General Alpine Commands
8603 ------------------------- -----------------------
8604 P Prev Keyword ? Display this help text
8605 N Next Keyword E Exit without selecting anything
8606 - Previous page % Print
8607 Spc (space bar) Next page
8608 W WhereIs
8610 Select Command
8611 ------------------------------------------------
8612 S Select the highlighted keyword (or chosen keywords in ListMode)
8613 L Turn on ListMode (makes it easy to choose multiple keywords)
8614 1 Turn off ListMode
8615 X Toggle choices when using ListMode
8616 </PRE>
8617 <!--chtml endif-->
8619 <H2>Description of the Select Keyword Screen</H2>
8621 This screen just gives you an easy way to select a keyword or a list of
8622 keywords.
8623 The list of keywords presented is the list of all keywords defined in your
8624 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8625 If you have given a keyword a nickname, that nickname is displayed
8626 instead of the actual keyword.
8628 <P><UL>
8629 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8630 </UL>
8631 <P>
8632 <End of help on this topic>
8633 </BODY>
8634 </HTML>
8635 ===== h_select_incoming_to_monitor =====
8636 <HTML>
8637 <HEAD>
8638 <TITLE>SELECT FOLDERS TO CHECK SCREEN</TITLE>
8639 </HEAD>
8640 <BODY>
8641 <H1>SELECT FOLDERS TO CHECK SCREEN</H1>
8642 <H2>COMMANDS</H2>
8643 <!--chtml if pinemode="function_key"-->
8644 <PRE>
8645 Available Commands
8646 -------------------------------
8647 F1 Show Help Text
8648 F3 Exit without selecting anything
8649 F4 Select the marked folders
8650 F5 Move highlight to previous folder
8651 F6 Move highlight to next folder
8652 F7 Previous page of folders
8653 F8 Next page of folders
8654 F9 Toggle choices on or off
8655 F11 Print
8656 F12 WhereIs
8657 </PRE>
8658 <!--chtml else-->
8659 <PRE>
8660 Navigation General Alpine Commands
8661 ------------------------- -----------------------
8662 P Prev Folder ? Display this help text
8663 N Next Folder ^C exit without changing anything
8664 - Previous page % Print
8665 Spc (space bar) Next page
8666 W WhereIs
8668 Select Command
8669 ------------------------------------------------
8670 S Select the marked folders
8671 X Toggle choices on or off
8672 </PRE>
8673 <!--chtml endif-->
8675 <H2>Description of the Select Folders to Check Screen</H2>
8677 This screen is only useful if the feature
8678 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
8679 is set.
8680 By default, when you set that feature all of your incoming folders
8681 will be checked periodically for Unseen messages.
8682 By using this screen, you may restrict the set of monitored folders to
8683 a subset of all of the incoming folders.
8684 <P>
8685 Mark the folders you want to monitor for Unseen messages with
8686 an "X".
8687 When you've finished marking all your selections use the Select
8688 command to register your choices.
8689 To return to the default of checking all incoming folders
8690 delete all folders or unmark all folders.
8692 <P><UL>
8693 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8694 </UL>
8695 <P>
8696 <End of help on this topic>
8697 </BODY>
8698 </HTML>
8699 ===== h_role_select =====
8700 <HTML>
8701 <HEAD>
8702 <TITLE>ROLES SCREEN</TITLE>
8703 </HEAD>
8704 <BODY>
8705 <H1>ROLES SCREEN</H1>
8706 <H2>ROLES COMMANDS</H2>
8707 <!--chtml if pinemode="function_key"-->
8708 <PRE>
8709 Available Commands
8710 -------------------------------
8711 F1 Show Help Text
8712 F3 Exit without a selection
8713 F4 Select a role to use in composition
8714 F5 Move to previous role
8715 F6 Move to next role
8716 F7 Previous page of roles
8717 F8 Next page of roles
8718 F11 Change Default Role
8719 F12 Whereis (search role nicknames)
8720 </PRE>
8721 <!--chtml else-->
8722 <PRE>
8723 Navigation General Alpine Commands
8724 ------------------------- -----------------------
8725 P Prev Role ? Display this help text
8726 N Next Role E Exit without a selection
8727 - Previous page
8728 Spc (space bar) Next page
8729 W WhereIs (search for word in role nicknames)
8731 Select Role Commands
8732 ------------------------------------------------
8733 [Return] Select highlighted role
8734 D Change Default Role
8735 </PRE>
8736 <!--chtml endif-->
8738 <H2>Description of the Roles Screen</H2>
8740 With this screen you select a role to be used in the composition of a
8741 message.
8742 Use the Previous and Next commands to highlight the role you wish to
8743 use.
8744 When you type carriage return you will be placed in the composer using the highlighted role.
8745 <P>
8746 You don't have any non-default <A HREF="h_rules_roles">roles</A>
8747 available unless you set them up.
8748 You may do so by using the Setup/Rules command on the MAIN MENU.
8749 <P>
8750 By using the D command, you may set a default role that will persist until
8751 you change it or until you exit Alpine.
8752 The D command toggles through three states: set the default role, unset the
8753 default role, and leave the default role as it is.
8754 <P><UL>
8755 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8756 </UL>
8757 <P>
8758 <End of help on this topic>
8759 </BODY>
8760 </HTML>
8761 ===== h_role_abook_select =====
8762 <HTML>
8763 <HEAD>
8764 <TITLE>SELECT ADDRESS BOOK SCREEN</TITLE>
8765 </HEAD>
8766 <BODY>
8767 <H1>SELECT ADDRESS BOOK SCREEN</H1>
8768 <H2>COMMANDS</H2>
8769 <!--chtml if pinemode="function_key"-->
8770 <PRE>
8771 Available Commands
8772 -------------------------------
8773 F1 Show Help Text
8774 F3 Exit screen without selecting anything
8775 F4 Select highlighted address book
8776 F5 Move to previous address book
8777 F6 Move to next address book
8778 F7 Previous page of address books
8779 F8 Next page of address books
8780 F12 Whereis
8781 </PRE>
8782 <!--chtml else-->
8783 <PRE>
8784 Navigation General Alpine Commands
8785 ------------------------- -----------------------
8786 P Previous addrbook ? Display this help text
8787 N Next addrbook
8788 - Previous page
8789 Spc (space bar) Next page
8790 W WhereIs
8792 Select Role Commands
8793 ------------------------------------------------
8794 S Select highlighted address book
8795 E Exit screen without selecting anything
8796 </PRE>
8797 <!--chtml endif-->
8799 <H2>Description of the Select Address Book Screen</H2>
8801 This screen helps you select one of your address books.
8802 Use the Previous and Next commands to highlight the address book you wish to
8803 select.
8804 <P><UL>
8805 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8806 </UL>
8807 <P>
8808 <End of help on this topic>
8809 </BODY>
8810 </HTML>
8811 ======== h_rule_patterns =============
8812 <HTML>
8813 <HEAD>
8814 <TITLE>PATTERNS</TITLE>
8815 </HEAD>
8816 <BODY>
8817 <H1>PATTERNS</H1>
8818 Patterns are used with Roles, Filtering, Index Coloring,
8819 Scoring, Other Rules, and Search Rules.
8820 Patterns are compared with a message to see if there is a match.
8821 For Filtering, the messages being checked are all the messages in the
8822 folder, one at a time.
8823 For Index Line Coloring, each message that is visible on the screen is
8824 checked for matches with the Index Coloring Patterns.
8825 Roles are used with the Reply, Forward, and Compose commands.
8826 For Reply, the message used to compare the Pattern with is the message
8827 being replied to;
8828 for Forward, the message used to compare the Pattern with is the message
8829 being forwarded;
8830 and for Compose, there is no message, so the parts of the Pattern that depend
8831 on a message (everything other than Current Folder Type and the
8832 Beginning of Month and Year)
8833 are not used.
8834 Only the Current Folder Type matters for Compose (plus the Beginning of
8835 Month or Year, which you wouldn't usually use for a Role).
8836 For Scoring, the message being scored is compared with all of the Score
8837 Patterns, and the Score Values from the ones that match are added together to
8838 get the message's score.
8839 For Other Rules, there is no message. Only the Current Folder Type is checked
8840 for Other Rules.
8841 <P>
8842 Each Pattern has several possible parts, all of which are optional.
8843 In order for there to be a match, <EM>ALL</EM> of the
8844 <EM>defined</EM> parts of the Pattern must match the message.
8845 If a part is not defined it is considered a match, but note that a filtering
8846 Pattern must have at least one defined part or it will be ignored.
8847 For example, if the To pattern is not defined it will be
8848 displayed as
8849 <P>
8850 <CENTER>To pattern = <No Value Set></CENTER>
8851 <P>
8852 That is considered a match because it is not defined.
8853 This means that the Pattern with nothing defined is a match if the
8854 Current Folder Type matches, but there is an exception that was mentioned
8855 in the previous paragraph.
8856 Because filtering is a potentially destructive action, filtering Patterns
8857 with nothing other than Current Folder Type defined are ignored.
8858 If you really want a filtering Pattern to match all messages (subject to
8859 Current Folder Type) the best way to do it is to define a Score interval
8860 that includes all possible scores.
8861 This would be the score interval <SAMP>(-INF,INF)</SAMP>.
8862 This can be used even if you haven't defined any rules to Set Scores.
8863 <P>
8864 There are six predefined header patterns called the To, From, Sender, Cc, News,
8865 and Subject patterns.
8866 Besides those six predefined header patterns, you may add
8867 additional header patterns with header fieldnames of your choosing.
8868 You add an extra header pattern by placing the cursor on one of the
8869 patterns while in the role editor and using the "eXtraHdr" command.
8870 The Recip pattern is a header pattern that stands for Recipient (To OR Cc)
8871 and the Partic pattern is a header pattern that stands for
8872 Participant (From OR To OR Cc).
8873 (Defining the Recip pattern does not have the same effect as defining both
8874 the To and Cc patterns. Recip is To <EM>OR</EM> Cc, not To <EM>AND</EM> Cc.)
8875 Similar to the header patterns are the AllText pattern and the BodyText pattern.
8876 Instead of comparing this pattern's text against only the contents of
8877 a particular header field, the text for the AllText pattern is compared
8878 with text anywhere in the message's header or body, and the text for the
8879 BodyText pattern is compared with text anywhere in the message's body.
8880 <P>
8881 Any of the header patterns, the AllText pattern, or the BodyText pattern may be negated with the
8882 "!" "toggle NOT" command.
8883 You can tell that <EM>NOT</EM> has been turned on by looking for the character
8884 "!" at the beginning of the pattern line.
8885 When the "!" is present, it reverses the meaning of the match.
8886 That is, if the pattern matches then it is considered to NOT be a match, and
8887 if it does not match it is considered to be a match.
8888 <P>
8889 Don't make the mistake of putting the "!" in the data field for
8890 a pattern.
8891 For example, if you type the characters "!urgent" into the Subject
8892 pattern, the pattern will look like:
8893 <P>
8894 <PRE>
8895 Subject pattern = !urgent
8896 </PRE>
8897 <P>
8898 This means you want to match the 7 character sequence "!urgent".
8899 In order to match messages that do not have "urgent" in
8900 their Subject field, first type the characters "urgent" followed
8901 by carriage return for the value of the Subject pattern, then negate it
8902 by typing the "!" command.
8903 It should look like
8904 <P>
8905 <PRE>
8906 ! Subject pattern = urgent
8907 </PRE>
8908 <P>
8909 The contents of each of these header patterns (or the AllText or BodyText patterns) may
8910 be a complete email address, part of an address, or a random set of
8911 characters to match against.
8912 It may also be a list of such patterns, which means you
8913 are looking for a match against the first pattern in the list <EM>OR</EM>
8914 the second pattern <EM>OR</EM> the third and so on.
8915 For example, a Subject pattern equal to
8916 <P>
8917 <PRE>
8918 Subject pattern = urgent
8919 emergency
8920 alert
8921 </PRE>
8922 <P>
8923 would match all messages with a subject that contained at least one
8924 of those words.
8925 It would also match subjects containing the words "alerts" or
8926 "Urgently".
8927 <P>
8928 The same example with "NOT" turned on would be
8929 <P>
8930 <PRE>
8931 ! Subject pattern = urgent
8932 emergency
8933 alert
8934 </PRE>
8935 <P>
8936 which would match all messages with a subject that did <EM>NOT</EM> contain any of
8937 those words.
8938 You can use the "Add Value" command to add new words to the list,
8939 or you can enter them as a comma-separated list.
8940 <P>
8941 (It is not possible to specify two patterns that must <EM>BOTH</EM> be
8942 present for a match.
8943 It is only possible to specify that <EM>EITHER</EM> pattern1 <EM>OR</EM>
8944 pattern2 must be present,
8945 and that is exactly what using a list does.)
8946 <P>
8947 The "Current Folder Type" and the "Score Interval" are
8948 also part of the Pattern, although the "Score Interval" is not used
8949 when checking for matches for Scoring.
8950 There are five similar settings that relate to the status of the message.
8951 These settings rely on the message being New or not, Deleted or not,
8952 Answered or not, Important or not, and Recent or not.
8953 There are also some other miscellaneous settings.
8954 The first is the Age of the message in days.
8955 Another is the Size of the message, in bytes.
8956 The third is a setting that detects whether or not the Subject of a
8957 message contains raw 8-bit characters (unencoded characters with the most
8958 significant bit set).
8959 There is a setting that detects whether or not this is the first time
8960 Alpine has been run this month (doesn't depend on individual messages),
8961 and another that detects whether or not this is the first time Alpine has
8962 been run this year.
8963 Other parts of the Pattern detect whether or not the From address of a
8964 message appears in your address book, whether or not certain keywords
8965 are set for a message, and whether or not certain character sets are
8966 used in a message.
8968 <H2>Parts of a Pattern</H2>
8970 <H3>Header patterns</H3>
8972 A header pattern is simply text that is searched for in the corresponding
8973 header field.
8974 For example, if a Pattern has a From header pattern with the value
8975 "@company.com", then only messages that have a From header
8976 that contains the text "@company.com" will be possible
8977 matches.
8978 Matches don't have to be exact.
8979 For example, if the relevant field of a message contains the text
8980 "mailbox@domain" somewhere
8981 in it, then header patterns of "box", or "x@d", or
8982 "mailbox@domain" are all matches.
8983 <P>
8984 All parts of the Pattern must match so, for example,
8985 if a message matches a defined
8986 From pattern, it still must be checked against the other parts of the
8987 Pattern that have been defined.
8988 The To header pattern is a slightly special case.
8989 If the message being checked has a Resent-To header
8990 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, the addresses
8991 there are used in place of the addresses in the To header.
8992 This is only true for the To header.
8993 Resent-cc and Resent-From headers are never used unless you add them
8994 with the eXtraHdrs command.
8995 <P>
8996 The meaning of a header pattern may be negated with the
8997 "!" "toggle NOT" command.
8998 You can tell that <EM>NOT</EM> has been turned on by looking for the character
8999 "!" at the beginning of the pattern line.
9000 It would look something like
9001 <P>
9002 <PRE>
9003 ! From pattern = susan@example.com
9004 </PRE>
9005 <P>
9006 When the "!" is present, it reverses the meaning of the match.
9007 <P>
9008 If you want to check for the presence of a header field but don't care
9009 about its value, then
9010 the empty pattern that you get by entering a pair of
9011 double quotes ("") should match any message that
9012 has the corresponding header field.
9014 <H3><A NAME="pattern_alltext">AllText patterns</A></H3>
9016 AllText patterns are just like header patterns except that the text is
9017 searched for anywhere in the message's headers or body, not just in the
9018 contents of a particular header field.
9019 <P>
9021 <H3><A NAME="pattern_bodytext">BodyText patterns</A></H3>
9023 BodyText patterns are just like header patterns except that the text is
9024 searched for anywhere in the message's body, not just in the
9025 contents of a particular header field.
9026 <P>
9028 If there is more than one header pattern or AllText pattern or BodyText pattern
9029 for which you want to take the
9030 same action there is a shorthand notation that may be used.
9031 Any of these patterns may be a list of patterns instead of
9032 just a single pattern.
9033 If any one of the patterns in the list matches the message
9034 then it is considered a match.
9035 For example, if "company1" and "company2" both required
9036 you to use the same role when replying to messages, you might have
9037 a To pattern that looks like
9038 <P>
9039 <PRE>
9040 To pattern = company1.com
9041 company2.com
9042 </PRE>
9043 <P>
9044 This means that if the mail you are replying to was addressed to
9045 either "anything@company1.com" or "anything@company2.com",
9046 then this Pattern is a match and the same actions will be taken.
9047 <P>
9048 The meaning of an AllText or BodyText pattern may be negated with the
9049 "!" "toggle NOT" command.
9050 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9051 "!" at the beginning of the pattern line.
9052 When the "!" is present, it reverses the meaning of the match.
9053 <P>
9054 A technicality: Since comma is the character used to separate multiple values
9055 in any of the fields that may have multiple values (such as header patterns,
9056 AllText patterns, BodyText patterns, keywords, folder lists, and so on),
9057 you must escape comma with a
9058 backslash (\) if you want to include a literal comma in one of those fields.
9059 In other words, if you type a backslash followed by a comma it will
9060 be interpreted as a comma by Alpine, instead of as a separator between
9061 pattern values.
9062 All other backslashes (those not followed by a comma) are literal
9063 backslashes and should not be escaped.
9064 It's unlikely you'll ever need to enter a literal comma or backslash in
9065 any of the patterns.
9067 <H3><A NAME="pattern_current_folder">Current Folder Type</A></H3>
9069 The "Current Folder Type" may be set to one of four different
9070 values: "Any", "News", "Email", or
9071 "Specific".
9072 If the value is set to "News", then the
9073 Pattern will only match if the currently open folder is a newsgroup.
9074 The value "Email" only matches if the current folder is not news and
9075 the value "Any" causes any folder to match.
9076 If the value of "Current Folder Type" is set to "Specific",
9077 then you must fill in a value for "Folder", which is on the line
9078 below the "Specific" line.
9079 In this case you will only get a match if the currently open folder is
9080 the specific folder you list.
9081 You may give a list of folders instead of just a single
9082 folder name, in which case the Pattern will match if the open folder is
9083 any one of the folders in the list.
9084 The name of each folder in the list may be either "INBOX",
9085 the technical specification
9086 of the folder (like what appears in your configuration file) or, if the
9087 folder is one of your incoming folders, it may be the nickname you've given
9088 the folder.
9089 Here are some samples of specific folder names:
9090 <P>
9091 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
9092 <P>
9093 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
9094 <P>
9095 <CENTER><SAMP>mail/local-folder</SAMP></CENTER>
9096 <P>
9097 The easiest way to fill in the "Folder" field is to use
9098 the "T" command that is available when the "Folder" line is
9099 highlighted, or to use the "Take" command with the configuration
9100 feature
9101 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
9102 turned on.
9103 <P>
9104 When reading a newsgroup, there may be a performance penalty
9105 incurred when collecting the information necessary to check whether
9106 or not a Pattern matches a message.
9107 For this reason, the default Current Folder Type is set to "Email".
9108 If you have Patterns with a Current Folder Type of either
9109 "Any" or "News" and those Patterns are used for
9110 Index Line Coloring or Scoring, you may experience
9111 slower screen redrawing in the MESSAGE INDEX screen when in a newsgroup.
9113 <H3><A NAME="pattern_age_interval">Age Interval</A></H3>
9115 The "Age Interval" may be set to an interval of message
9116 ages that should be considered a match.
9117 Like the other parts of the Pattern, if it is unset it will be ignored.
9118 The Age Interval looks like
9119 <P>
9120 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
9121 <P>
9122 where "min_age" and "max_age" are integers greater
9123 than or equal to zero.
9124 The special value "INF" may be used for
9125 the max value. It represents infinity.
9126 <P>
9127 Actually, this option may be defined as a list of intervals instead
9128 of just a single interval.
9129 The list is separated by commas.
9130 It can look like
9131 <P>
9132 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
9133 <P>
9134 When there is an Age Interval defined, it is a match if the age, in days, of
9135 the message is contained in any of the intervals.
9136 The intervals include both endpoints.
9137 <P>
9138 Even though this option is called Age, it isn't actually
9139 the <EM>age</EM> of the message.
9140 Instead, it is how many days ago the message arrived in one of your folders.
9141 If the current time is a little past midnight, then a message that arrived
9142 just before midnight arrived yesterday, even though the message is only
9143 a few minutes old.
9144 By default, the date being used is not the date in the Date
9145 header of the message.
9146 It is the date that the message arrived in one of your folders.
9147 When you Save a message from one folder to another that arrival date
9148 is preserved.
9149 If you would like to use the date in the Date header that is possible.
9150 Turn on the option
9151 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
9152 near the bottom of the rule definition.
9153 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
9155 <H3><A NAME="pattern_size_interval">Size Interval</A></H3>
9157 The "Size Interval" may be set to an interval of message
9158 sizes that should be considered a match.
9159 Like the other parts of the Pattern, if it is unset it will be ignored.
9160 The Size Interval looks like
9161 <P>
9162 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
9163 <P>
9164 where "min_size" and "max_size" are integers greater
9165 than or equal to zero.
9166 The special value "INF" may be used for
9167 the max value. It represents infinity.
9168 <P>
9169 Actually, this option may be defined as a list of intervals instead
9170 of just a single interval.
9171 The list is separated by commas.
9172 It can look like
9173 <P>
9174 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
9175 <P>
9176 When there is a Size Interval defined, it is a match if the size, in bytes, of
9177 the message is contained in any of the intervals.
9178 The intervals include both endpoints.
9180 <H3><A NAME="pattern_score_interval">Score Interval</A></H3>
9182 The "Score Interval" may be set to an interval of message
9183 scores that should be considered a match.
9184 Like the other parts of the Pattern, if it is unset it will be ignored.
9185 The Score Interval looks like
9186 <P>
9187 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
9188 <P>
9189 where "min_score" and "max_score" are positive or
9190 negative integers, with min_score less than or equal to max_score.
9191 The special values "-INF" and "INF" may be used for
9192 the min and max values to represent negative and positive infinity.
9193 <P>
9194 Actually, a list of intervals may be used if you wish.
9195 A list would look like
9196 <P>
9197 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
9198 <P>
9199 When there is a Score Interval defined, it is a match if the score for
9200 the message is contained in any of the intervals in the list.
9201 The intervals include the endpoints.
9202 The score for a message is calculated by looking at every Score rule defined and
9203 adding up the Score Values for the ones that match the message.
9204 When deciding whether or not a Pattern matches a message for purposes of
9205 calculating the score, the Score Interval is ignored.
9207 <H3><A NAME="pattern_message_status">Message Status</A></H3>
9209 There are five separate message status settings.
9210 By default, all five are set to the value "Don't care", which
9211 will match any message.
9212 The value "Yes" means that the particular status must be true
9213 for a match, and the value "No" means that the particular
9214 status must not be true for a match.
9215 For example, one of the five Message Status settings is whether a message
9216 is marked Important or not.
9217 A "Yes" means that the message must be Important to be
9218 considered a match and "No" means that the message must not be
9219 Important to be considered a match.
9220 The same is true of the other four message status settings that depend
9221 on whether or not the message is New; whether the message has
9222 been Answered or not; whether the message has been Deleted or not, and
9223 whether the message is Recent or not.
9224 <P>
9225 The nomenclature for New and Recent is a bit confusing:
9226 <P>
9227 New means that the message is Unseen.
9228 It could have been in your mailbox for a long time but if you haven't looked
9229 at it, it is still considered New.
9230 That matches the default Alpine index display that shows an N for such a
9231 message.
9232 <P>
9233 Recent means that the message was added to this folder since the last time
9234 you opened the folder.
9235 Alpine also shows an N by default for these types of messages.
9236 If you were to run two copies of Alpine that opened a folder one right after
9237 the other, a message would only show up as Recent in (at most) the first
9238 Alpine session.
9240 <H3><A NAME="pattern_message_keywords">Message Keywords</A></H3>
9242 Keywords are similar to Message Status, but they are chosen by the user.
9243 Provided the mail server allows for it, you may add a set of possible keywords
9244 to a folder and then you may set those keywords or not for each message
9245 in the folder (see <A HREF="h_common_flag">Flag Command</A>).
9246 The syntax of this part of the Pattern is similar to the header patterns.
9247 It is a list of keywords.
9248 The Keyword part of the Pattern is a match if the message has any of
9249 the keywords in the list set.
9250 Like other parts of the Pattern, if this is unset it will be ignored.
9252 <H3><A NAME="pattern_message_charsets">Message Character Sets</A></H3>
9254 A message may use one or more character sets.
9255 This part of the Pattern matches messages that make use of one or more of
9256 the character sets specified in the pattern.
9257 It will be considered a match if a message uses any of the character
9258 sets in the list you give here.
9260 <P>
9261 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
9262 GB2312) you may also use some shorthand names that Alpine provides.
9263 These names are more understandable shorthand names for sets of
9264 character set names.
9265 Two examples are "Cyrillic" and "Greek".
9266 Selecting one of these shorthand names is equivalent to selecting all of
9267 the character sets that make up the set.
9268 You can see all of these shorthand names and the lists of character sets
9269 they stand for by typing the "T" command with the Character
9270 Set pattern highlighted.
9271 The syntax of this part of the Pattern is similar to the header patterns
9272 and the Message Keywords pattern.
9273 It is a list of character sets (or shorthand names).
9274 The Character Set part of the Pattern is a match if the message uses any
9275 of the character sets in the list.
9276 Like other parts of the Pattern, if this is unset it will be ignored.
9278 <H3><A NAME="pattern_8bit_subject">Raw 8-bit in Subject</A></H3>
9280 It seems that lots of unwanted email contains unencoded 8-bit characters
9281 in the Subject.
9282 Normally, characters with the 8th bit set are not allowed in the Subject
9283 header unless they are MIME-encoded.
9284 This option gives you a way to match messages that have Subjects that
9285 contain unencoded 8-bit characters.
9286 By default, the value of this option is "Don't care", which
9287 will match any message.
9288 The value "Yes" means that there must be raw 8-bit characters in
9289 the Subject of the message in order for there to be a match,
9290 and the value "No" is the opposite.
9291 Setting this option will affect performance in large folders because the
9292 subject of each message in the folder has to be checked.
9294 <H3><A NAME="pattern_bom">Beginning of Month</A></H3>
9296 This option gives you a way to take some action once per month.
9297 By default, the value of this option is "Don't care", which
9298 will always match.
9299 The value "Yes" means that this must be the first time Alpine has
9300 been run this month in order to count as a match,
9301 and the value "No" is the opposite.
9303 <H3><A NAME="pattern_boy">Beginning of Year</A></H3>
9305 This option gives you a way to take some action once per year.
9306 By default, the value of this option is "Don't care", which
9307 will always match.
9308 The value "Yes" means that this must be the first time Alpine has
9309 been run this year in order to count as a match,
9310 and the value "No" is the opposite.
9312 <H3><A NAME="pattern_abookfrom">Address in Address Books</A></H3>
9314 This option gives you a way to match messages that have an address
9315 that is in one of your address books.
9316 Only the simple entries in your address books are searched.
9317 Address book distribution lists are ignored!
9318 By default, the value of this option is "Don't care", which
9319 will match any message.
9320 The value "Yes, in any address book" means the address
9321 from the message must be in at least one of your
9322 address books in order to be a match.
9323 The value "No, not in any address book"
9324 means none of the addresses may
9325 be in any of your address books in order to be a match.
9326 The values "Yes, in specific address books" and
9327 "No, not in any of specific address books" are similar but instead
9328 of depending on all address books you are allowed to give a list of address
9329 books to look in.
9330 The addresses from the message that are checked for are determined by the
9331 setting you have for "Types of addresses to check for in address book".
9332 If you set this to "From" the From address from the message will
9333 be looked up in the address book.
9334 If you set it to only "To" then the To addresses will be used.
9335 If any of the To addresses are in the address book then it is considered
9336 a match for "Yes" or not a match for "No".
9337 You could set it to both From and To, in which case all of the From and To
9338 addresses are used.
9339 The "Reply-To" and "Sender" cases are a little unusual.
9340 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
9341 exists or the From address if there is no Reply-To address.
9342 Same for the Sender address.
9343 Setting this option may affect performance in large folders because the
9344 From and Reply-To of each message in the folder have to be checked.
9346 <H3><A NAME="pattern_categorizer">Categorizer Command</A></H3>
9348 This is a command that is run with its standard input set to the message
9349 being checked and its standard output discarded.
9350 The full directory path should be specified.
9351 The command will be run and then its exit status will be checked against
9352 the Exit Status Interval, which defaults to just the value zero.
9353 If the exit status of the command falls in the interval, it is considered
9354 a match, otherwise it is not a match.
9355 <P>
9357 This option may actually be a list of commands.
9358 The first one that exists and is executable is used.
9359 That makes it possible to use the same configuration with Unix Alpine and
9360 PC-Alpine.
9361 <P>
9363 If none of the commands in the list exists and is executable then the rule
9364 is <EM>not</EM> a match.
9365 If it is possible that the command may not exist, you should be careful
9366 to structure your rules so that nothing destructive
9367 happens when the command does not exist.
9368 For example, you might have a filter that filters away spam when there is
9369 a match but does nothing when there is not a match.
9370 That would continue to work correctly if the command didn't exist.
9371 However, if you have a filter that filters away spam when there is not
9372 a match and keeps it when there is a match, that would filter everything
9373 if the categorizer command didn't exist.
9374 <P>
9375 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
9376 setup for the bogofilter filter.
9378 <P>
9379 <End of help on this topic>
9380 </BODY>
9381 </HTML>
9382 ===== h_rules_roles =====
9383 <HTML>
9384 <HEAD>
9385 <TITLE>SETUP ROLES SCREEN</TITLE>
9386 </HEAD>
9387 <BODY>
9388 <H1>SETUP ROLES SCREEN</H1>
9389 <H2>SETUP ROLES COMMANDS</H2>
9390 <!--chtml if pinemode="function_key"-->
9391 <PRE>
9392 Available Commands -- Group 1 Available Commands -- Group 2
9393 ------------------------------- ------------------------------
9394 F1 Show Help Text F1 Show Help Text
9395 F2 See commands in next group F2 See commands in next group
9396 F3 Back to MAIN Alpine menu
9397 F4 Change configuration for role
9398 F5 Move to previous role F5 Include file in role config
9399 F6 Move to next role F6 Exclude file from config
9400 F7 Previous page of roles
9401 F8 Next page of roles
9402 F9 Add new role F9 Replicate existing role
9403 F10 Delete existing role
9404 F11 Shuffle the order of roles
9405 F12 Whereis (search role nicknames)
9406 </PRE>
9407 <!--chtml else-->
9408 <PRE>
9409 Navigation General Alpine Commands
9410 ------------------------- -----------------------
9411 P Prev Role ? Display this help text
9412 N Next Role E Back to MAIN Alpine menu
9413 - Previous page
9414 Spc (space bar) Next page
9415 W WhereIs (search for word in role nicknames)
9417 Setup Roles Commands
9418 ------------------------------------------------
9419 A Add new role $ Shuffle the order of roles
9420 D Delete existing role C Change configuration for highlighted role
9421 R Replicate existing role
9422 I Include file in role config X Exclude file from role config
9423 </PRE>
9424 <!--chtml endif-->
9426 <H2>Description of the Setup Roles Screen</H2>
9428 This screen lets you add, delete, modify, or change the order of the rules
9429 that determine the role you are playing when composing a message.
9430 <P>
9431 You may play different roles depending on who you are replying to.
9432 For example, if you are replying to a message addressed to help-desk you
9433 may be acting as a Help Desk Worker.
9434 That role may require that you use a different return address and/or
9435 a different signature.
9436 <P>
9437 Roles are optional.
9438 If you set up roles they work like this: Each role has a set of
9439 "Uses", which indicate whether or not a role is eligible to be
9440 considered for a particular use; a "Pattern",
9441 which is used to decide which of the eligible roles is used; and a set
9442 of "Actions", which are taken when that role is used.
9443 When you reply to a message, the message you are replying to is compared
9444 with the Patterns of the roles marked as eligible for use when replying.
9445 The comparisons start with the first eligible role and keep going until there
9446 is a match.
9447 If a match is found, the matching role's Actions are taken.
9448 <P>
9449 It is also possible to set a default role and to change that role during
9450 your Alpine session.
9451 When you start Alpine no default role will be set.
9452 You may set or change the current default role by using the "D"
9453 command in the role selection screen.
9454 You'll see that screen while composing a message and being asked to select
9455 a role.
9456 An easy way to get to that screen is to use the <A HREF="h_common_role">Role Command</A> to
9457 compose a message.
9458 You may find a default role useful if you normally perform the duties of one
9459 of your roles for a while, then you switch to another role and stay in the
9460 new role for another period of time.
9461 It may be easier than using the Role Command to select the role each time you
9462 compose a message.
9464 <H2>Role Uses</H2>
9466 There are three types of use to be configured;
9467 one for Replying, one for Forwarding, and one for Composing.
9468 These indicate whether or not you want a role to be considered when you
9469 type the Reply, Forward, or Compose commands.
9470 (The Role command is an alternate form of the Compose command, and it is
9471 not affected by these settings.)
9472 Each of these Use types has three possible values.
9473 The value "Never"
9474 means that the role will never be considered as a candidate for use with
9475 the corresponding command.
9476 For example, if you set a role's Reply Use to Never, then when you Reply to
9477 a message, that role won't even be considered.
9478 (That isn't quite true. If the message you are replying to matches some other
9479 role that requires confirmation,
9480 then there will be a ^T command available which allows you to select a role
9481 from all of your roles, not just the reply-eligible roles.)
9482 <P>
9484 The options "With confirmation" and "Without confirmation"
9485 both mean that you do want to consider this role when using the corresponding
9486 command.
9487 For either of these settings the role's Pattern will
9488 be checked to see if it matches the message.
9489 For Reply Use, the message used to compare the Pattern with is the message
9490 being replied to.
9491 For Forward Use, the message used to compare the Pattern with is the message
9492 being forwarded.
9493 For Compose Use, there is no message, so the parts of the Pattern that depend
9494 on a message (everything other than Current Folder Type) are ignored.
9495 In all cases, the Current Folder Type is checked if defined.
9496 If there is a match then this role will either be used without confirmation
9497 or will be the default when confirmation is asked for, depending on
9498 which of the two options is selected.
9499 If confirmation is requested, you will have a chance to
9500 choose No Role instead of the offered role, or to
9501 change the role to any one of your other roles (with the ^T command).
9503 <H2>Role Patterns</H2>
9505 In order to determine whether or not a message matches a role the message is
9506 compared with the Role's Pattern.
9507 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9508 Scoring, Other Rules, and Search Rules, so are described in only one place,
9509 "<A HREF="h_rule_patterns">here</A>".
9510 <P>
9511 Since header patterns, AllText patterns, and BodyText patterns that are unset are ignored,
9512 a role that has all header patterns unset, the AllText pattern unset,
9513 the BodyText pattern unset,
9514 the Score Interval unset, and the Current Folder Type set to
9515 "Any" may be used as a default role.
9516 It should be put last in the list of roles since the matching
9517 starts at the beginning and proceeds until one of the roles is a match.
9518 If no roles at all match, then Alpine will
9519 use its regular methods of defining the role.
9520 If you wanted to, you could define a different "default" role
9521 for Replying, Forwarding, and Composing by setting the
9522 "Use" fields appropriately.
9524 <H2>Role Actions</H2>
9526 Once a role match is found, the role's Actions are taken.
9527 For each role there are several possible actions that may be defined.
9528 They are actions to set the From address, the Reply-To address,
9529 the Fcc, the Signature, the Template file, and Other Headers.
9531 <H3>Set From</H3>
9533 The From address is the address used on the From line of the message
9534 you are sending.
9536 <H3>Set Reply-To</H3>
9538 The Reply-To address is the address used on the Reply-To line of the message
9539 you are sending.
9540 You don't need a Reply-To address unless it is different from the From address.
9542 <H3>Set Other Headers</H3>
9544 If you want to set the value of the From or Reply-To headers, use
9545 the specific fields "Set From" or "Set Reply-To".
9546 If you want to set the values of other headers, use this field.
9547 This field is similar to the
9548 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> configuration option.
9549 Each header you specify here must include the header tag
9550 ("To:", "Approved:", etc.)
9551 and may optionally include a value for that header.
9552 It is different from the <!--#echo var="VAR_customized-hdrs"--> in that the value you give
9553 for a header here will replace any value that already exists.
9554 For example, if you are Replying to a message there will be at least one
9555 address in the To header (the address you are Replying to).
9556 However, if you Reply using a role that sets the To header, that role's
9557 To header value will be used instead.
9559 <H3>Set Fcc</H3>
9561 The Fcc is used as the Fcc for the message you are sending.
9563 <H3>Set Signature or Set LiteralSig</H3>
9565 The Signature is the name of a file to be used as the signature file when
9566 this role is being used.
9567 If the name of the file has a vertical bar following it (|)
9568 then it is assumed that the file is a program that should be run to
9569 produce the signature.
9570 If the LiteralSig is set, then it is used instead of the signature file.
9571 LiteralSig is just a different way to store the signature.
9572 It is stored in the pine configuration file instead of in a separate
9573 signature file.
9574 If the <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined
9575 either in the role or as the default signature in the Setup/Config screen,
9576 then the signature file is ignored.
9578 <H3>Set Template</H3>
9580 A Template is the name of a file to be included in the message when this
9581 role is being used.
9582 If the name of the file has a vertical bar following it (|)
9583 then it is assumed that the file is a program that should be run to
9584 produce the template.
9586 <P>
9587 Both signature files and template files may be stored remotely on an IMAP
9588 server.
9589 In order to do that you just give the file a remote name.
9590 This works just like the regular
9591 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>
9592 option that is configured from the Setup/Configuration screen.
9593 A remote signature file name might look like:
9594 <P>
9595 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
9596 <P>
9597 Once you have named the remote signature or template file you create its
9598 contents by using the "F" "editFile" command when the
9599 cursor is on the "Set Signature" or "Set Template"
9600 line of the role editor.
9602 <P>
9603 Both signature files and template files (or the output of signature programs
9604 and template file programs) may contain special tokens
9605 that are replaced with contents
9606 that depend on the message being replied to or forwarded.
9607 See the help for the individual fields inside the role editor for more
9608 information on tokens.
9610 <H3>Use SMTP Server</H3>
9612 If this field has a value, then it will be used as the SMTP server
9613 to send mail when this role is being used (unless the SMTP server variable
9614 is set in the system-wide fixed configuration file).
9615 It has the same semantics as the
9616 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
9617 variable in the Setup/Config screen.
9618 When you postpone the composition this SMTP server list will be saved
9619 with the postponed composition and it cannot be changed later.
9620 Because of that, you may want to make this a list of SMTP servers
9621 with the preferred server at the front of the list and alternate servers
9622 later in the list.
9624 <P>
9625 If any of the actions are left unset, then the action depends on what
9626 is present in the "Initialize settings using role" field.
9627 If you've listed the nickname of another one of your roles there, then the
9628 corresponding action from that role will be used here.
9629 If that action is also blank, or if there is no nickname specified,
9630 then Alpine will do whatever it normally does to set these actions.
9631 This depends on other configuration options and features you've set.
9633 <H2>Command Descriptions</H2>
9635 <H3>Add</H3>
9637 The Add command is used to add a new role definition to your set of
9638 roles.
9639 The new role will be added after the highlighted role.
9641 <H3>Delete</H3>
9643 The Delete command deletes the currently highlighted role.
9645 <H3>Change</H3>
9647 The Change command lets you edit the nickname, Uses, Pattern,
9648 and Actions of the currently highlighted role.
9650 <H3>Shuffle</H3>
9652 The Shuffle command allows you to change the order of the roles.
9653 You may move the currently highlighted role up or down in the list.
9654 The order of the roles is important since the roles are tested for a
9655 match starting with the first role and continuing until a match is found.
9656 You should place the roles with more specific Patterns near the beginning
9657 of the list, and those with more general Patterns near the end so that
9658 the more specific matches will happen when appropriate.
9660 <H3>Replicate</H3>
9662 The Replicate command is used to copy an existing role and modify it.
9663 The new role will be added after the highlighted role.
9665 <H3>IncludeFile</H3>
9667 The IncludeFile command allows you to add a roles file to your configuration.
9668 Usually, your roles will be contained in your Alpine configuration file.
9669 If you wish, some or all of your roles may be stored in a separate file.
9670 If a roles file already exists (maybe it was made by somebody else using
9671 Alpine), you may insert it before the currently highlighted role.
9672 You may also insert an empty file or a file that does not yet exist.
9673 Once you have an empty roles file in your configuration, you may use
9674 the Shuffle command to move roles into it.
9675 In fact, that's the only way to get the initial role into the file.
9677 <H3>eXcludeFile</H3>
9679 The eXcludeFile command removes a roles file from your roles configuration.
9680 A limitation of the program is that in order to exclude a roles file
9681 that file must have at least one role
9682 in it, otherwise you won't be able to highlight a line in the file.
9683 So you may have to add a dummy role to the file in order to exclude the file.
9684 <P><UL>
9685 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9686 </UL>
9687 <P>
9688 <End of help on this topic>
9689 </BODY>
9690 </HTML>
9691 ===== h_rules_other =====
9692 <HTML>
9693 <HEAD>
9694 <TITLE>SETUP OTHER RULES SCREEN</TITLE>
9695 </HEAD>
9696 <BODY>
9697 <H1>SETUP OTHER RULES SCREEN</H1>
9698 <H2>SETUP OTHER RULES COMMANDS</H2>
9699 <!--chtml if pinemode="function_key"-->
9700 <PRE>
9701 Available Commands -- Group 1 Available Commands -- Group 2
9702 ------------------------------- ------------------------------
9703 F1 Show Help Text F1 Show Help Text
9704 F2 See commands in next group F2 See commands in next group
9705 F3 Back to MAIN Alpine menu
9706 F4 Change configuration for rule
9707 F5 Move to previous rule F5 Include file in rule config
9708 F6 Move to next rule F6 Exclude file from config
9709 F7 Previous page of rules
9710 F8 Next page of rules
9711 F9 Add new rule F9 Replicate existing rule
9712 F10 Delete existing rule
9713 F11 Shuffle the order of rules
9714 F12 Whereis (search rule nicknames)
9715 </PRE>
9716 <!--chtml else-->
9717 <PRE>
9718 Navigation General Alpine Commands
9719 ------------------------- -----------------------
9720 P Prev rule ? Display this help text
9721 N Next rule E Back to MAIN Alpine menu
9722 - Previous page
9723 Spc (space bar) Next page
9724 W WhereIs (search for word in rule nicknames)
9726 Setup Other Rules Commands
9727 ------------------------------------------------
9728 A Add new rule $ Shuffle the order of rules
9729 D Delete existing rule C Change configuration for highlighted rule
9730 R Replicate existing rule
9731 I Include file in rule config X Exclude file from rule config
9732 </PRE>
9733 <!--chtml endif-->
9735 <H2>Description of the Setup Other Rules Screen</H2>
9737 This is where you may set various actions that do not fit well into the
9738 other Rules categories.
9740 <H2>Patterns</H2>
9742 Other Rules are a little different from the rest of the Rules because
9743 they depend only on the current folder, and not on a particular message.
9744 In order to determine whether or not a rule's actions should be applied
9745 the current folder is compared with the rule's Pattern, which consists
9746 of only the Current Folder Type.
9747 Current Folder Type works the same for Other Rules as it does for Roles,
9748 Filtering, Index Coloring, and Scoring.
9749 Keep in mind that the only part of the Pattern that applies to Other
9750 Rules is the Current Folder Type when looking at the description of
9751 Patterns given
9752 "<A HREF="h_rule_patterns">here</A>".
9754 <H2>The Actions</H2>
9756 <H3>Set Sort Order</H3>
9758 When you enter a new folder, these rules will be checked to see if you
9759 have set a sort order that is different from your default sort order.
9760 The default is set in the Setup/Config screen with
9761 the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
9762 If the Sort Order action is set, then the folder will be displayed sorted in
9763 that sort order instead of in the default order.
9764 <P>
9765 A possible point of confusion arises when you change the configuration
9766 of the Sort Order for the currently open folder.
9767 The folder will normally be re-sorted when you go back to viewing the
9768 index.
9769 However, if you have manually sorted the folder with the
9770 Sort
9771 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
9772 command, then it will not be re-sorted until the next time it is opened.
9774 <H3>Set Index Format</H3>
9776 When you enter a new folder, these rules will be checked to see if you
9777 have set an Index Format that is different from your default Index Format,
9778 which is set with the
9779 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
9780 If so, the index will be displayed with this format instead of the default.
9782 <H3>Set Startup Rule</H3>
9784 When you enter a new folder, these rules will be checked to see if you
9785 have set a startup rule that is different from the default startup rule.
9786 The default for incoming folders is set in the Setup/Config screen with
9787 the "<!--#echo var="VAR_incoming-startup-rule"-->" option.
9788 The default for folders other than INBOX that are not part of your
9789 incoming collection
9790 (see <A HREF="h_config_enable_incoming"><!--#echo var="FEAT_enable-incoming-folders"--></A> feature)
9791 is to start with the last message in the folder.
9792 If the Startup Rule is set to something other than "default",
9793 then the rule will determine which message will be the current message when
9794 the folder is first opened.
9795 <P>
9796 The various startup rule possibilities work the same here as they do in
9797 the incoming collection, so check
9798 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
9799 for more help.
9801 <H2>Command Descriptions</H2>
9803 <H3>Add</H3>
9805 The Add command is used to add a new rule definition to your set of
9806 rules.
9807 The new rule will be added after the highlighted rule.
9809 <H3>Delete</H3>
9811 The Delete command deletes the currently highlighted rule.
9813 <H3>Change</H3>
9815 The Change command lets you edit the nickname, Pattern,
9816 and Action of the currently highlighted rule.
9818 <H3>Shuffle</H3>
9820 The Shuffle command allows you to change the order of the rules.
9821 You may move the currently highlighted rule up or down in the list.
9822 The order of the rules is important since the rules are tested for a
9823 match starting with the first rule and continuing until a match is found.
9824 You should place the rules with more specific Patterns near the beginning
9825 of the list, and those with more general Patterns near the end so that
9826 the more specific matches will happen when appropriate.
9828 <H3>Replicate</H3>
9830 The Replicate command is used to copy an existing rule definition and modify it.
9831 The new rule will be added after the highlighted rule.
9833 <H3>IncludeFile</H3>
9835 The IncludeFile command allows you to add a rules file to your configuration.
9836 Usually, your rules will be contained in your Alpine configuration file.
9837 If you wish, some or all of your rules may be stored in a separate file.
9838 If a rules file already exists (maybe it was made by somebody else using
9839 Alpine), you may insert it before the currently highlighted rule.
9840 You may also insert an empty file or a file that does not yet exist.
9841 Once you have an empty rules file in your configuration, you may use
9842 the Shuffle command to move rules into it.
9843 In fact, that's the only way to get the initial rule into the file.
9845 <H3>eXcludeFile</H3>
9847 The eXcludeFile command removes a rules file from your rules configuration.
9848 A limitation of the program is that in order to exclude a rules file
9849 that file must have at least one rule
9850 in it, otherwise you won't be able to highlight a line in the file.
9851 So you may have to add a dummy rule to the file in order to exclude the file.
9852 <P><UL>
9853 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9854 </UL>
9855 <P>
9856 <End of help on this topic>
9857 </BODY>
9858 </HTML>
9859 ===== h_rules_srch =====
9860 <HTML>
9861 <HEAD>
9862 <TITLE>SETUP SEARCH RULES SCREEN</TITLE>
9863 </HEAD>
9864 <BODY>
9865 <H1>SETUP SEARCH RULES SCREEN</H1>
9866 <H2>SETUP SEARCH RULES COMMANDS</H2>
9867 <!--chtml if pinemode="function_key"-->
9868 <PRE>
9869 Available Commands -- Group 1 Available Commands -- Group 2
9870 ------------------------------- ------------------------------
9871 F1 Show Help Text F1 Show Help Text
9872 F2 See commands in next group F2 See commands in next group
9873 F3 Back to MAIN Alpine menu
9874 F4 Change configuration for rule
9875 F5 Move to previous rule F5 Include file in rule config
9876 F6 Move to next rule F6 Exclude file from config
9877 F7 Previous page of rules
9878 F8 Next page of rules
9879 F9 Add new rule F9 Replicate existing rule
9880 F10 Delete existing rule
9881 F11 Shuffle the order of rules
9882 F12 Whereis (search rule nicknames)
9883 </PRE>
9884 <!--chtml else-->
9885 <PRE>
9886 Navigation General Alpine Commands
9887 ------------------------- -----------------------
9888 P Prev rule ? Display this help text
9889 N Next rule E Back to MAIN Alpine menu
9890 - Previous page
9891 Spc (space bar) Next page
9892 W WhereIs (search for word in rule nicknames)
9894 Setup Search Rules Commands
9895 ------------------------------------------------
9896 A Add new rule $ Shuffle the order of rules
9897 D Delete existing rule C Change configuration for highlighted rule
9898 R Replicate existing rule
9899 I Include file in rule config X Exclude file from rule config
9900 </PRE>
9901 <!--chtml endif-->
9903 <H2>Description of the Setup Search Rules Screen</H2>
9905 One of the commands that becomes available when that feature is turned on
9906 is the "; Select" command, which is used in the MESSAGE INDEX
9907 screen to select a set of messages.
9908 One way of selecting messages is to use a Rule.
9909 All of the messages that match (or don't match if you wish)
9910 a Rule's Pattern will be selected.
9911 <P>
9912 Any of your Rules may be used for this purpose.
9913 You might already have Rules set up for filtering, index line color, scores, or roles;
9914 and you may use any of those Rules with the Select command.
9915 However, you might find it more convenient to set up a separate set of Rules
9916 just for this purpose without having to worry about what other effects
9917 they may cause.
9918 That is the purpose of these Select Rules.
9920 <P>
9921 Each rule has a "Pattern"
9922 that is used to decide which messages are selected when you use it with
9923 the Select command.
9925 <H2>Patterns</H2>
9927 In order to determine whether or not a message should be selected
9928 the message is compared with the rule's Pattern.
9929 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9930 Scoring, Other Rules, and Search Rules, so are described in only one place,
9931 "<A HREF="h_rule_patterns">here</A>".
9933 <H2>Command Descriptions</H2>
9935 <H3>Add</H3>
9937 The Add command is used to add a new rule definition to your set of
9938 rules.
9939 The new rule will be added after the highlighted rule.
9941 <H3>Delete</H3>
9943 The Delete command deletes the currently highlighted rule.
9945 <H3>Change</H3>
9947 The Change command lets you edit the nickname and Pattern
9948 of the currently highlighted rule.
9950 <H3>Shuffle</H3>
9952 The Shuffle command allows you to change the order of the rules.
9953 This affects only the order they are presented in when you use the
9954 ^T subcommand of the Select by Rule command.
9955 You may move the currently highlighted rule up or down in the list.
9957 <H3>Replicate</H3>
9959 The Replicate command is used to copy an existing rule definition and modify it.
9960 The new rule will be added after the highlighted rule.
9962 <H3>IncludeFile</H3>
9964 The IncludeFile command allows you to add a rules file to your configuration.
9965 Usually, your rules will be contained in your Alpine configuration file.
9966 If you wish, some or all of your rules may be stored in a separate file.
9967 If a rules file already exists (maybe it was made by somebody else using
9968 Alpine), you may insert it before the currently highlighted rule.
9969 You may also insert an empty file or a file that does not yet exist.
9970 Once you have an empty rules file in your configuration, you may use
9971 the Shuffle command to move rules into it.
9972 In fact, that's the only way to get the initial rule into the file.
9974 <H3>eXcludeFile</H3>
9976 The eXcludeFile command removes a rules file from your rules configuration.
9977 A limitation of the program is that in order to exclude a rules file
9978 that file must have at least one rule
9979 in it, otherwise you won't be able to highlight a line in the file.
9980 So you may have to add a dummy rule to the file in order to exclude the file.
9981 <P><UL>
9982 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9983 </UL>
9984 <P>
9985 <End of help on this topic>
9986 </BODY>
9987 </HTML>
9988 ===== h_rules_incols =====
9989 <HTML>
9990 <HEAD>
9991 <TITLE>SETUP INDEX LINE COLORS SCREEN</TITLE>
9992 </HEAD>
9993 <BODY>
9994 <H1>SETUP INDEX LINE COLORS SCREEN</H1>
9995 <H2>SETUP INDEX LINE COLORS COMMANDS</H2>
9996 <!--chtml if pinemode="function_key"-->
9997 <PRE>
9998 Available Commands -- Group 1 Available Commands -- Group 2
9999 ------------------------------- ------------------------------
10000 F1 Show Help Text F1 Show Help Text
10001 F2 See commands in next group F2 See commands in next group
10002 F3 Back to MAIN Alpine menu
10003 F4 Change configuration for rule
10004 F5 Move to previous rule F5 Include file in rule config
10005 F6 Move to next rule F6 Exclude file from config
10006 F7 Previous page of rules
10007 F8 Next page of rules
10008 F9 Add new rule F9 Replicate existing rule
10009 F10 Delete existing rule
10010 F11 Shuffle the order of rules
10011 F12 Whereis (search rule nicknames)
10012 </PRE>
10013 <!--chtml else-->
10014 <PRE>
10015 Navigation General Alpine Commands
10016 ------------------------- -----------------------
10017 P Prev rule ? Display this help text
10018 N Next rule E Back to MAIN Alpine menu
10019 - Previous page
10020 Spc (space bar) Next page
10021 W WhereIs (search for word in rule nicknames)
10023 Setup Index Color Commands
10024 ------------------------------------------------
10025 A Add new rule $ Shuffle the order of rules
10026 D Delete existing rule C Change configuration for highlighted rule
10027 R Replicate existing rule
10028 I Include file in rule config X Exclude file from rule config
10029 </PRE>
10030 <!--chtml endif-->
10032 <H2>Description of the Setup Index Line Colors Screen</H2>
10034 Index Line Color causes lines in the MESSAGE INDEX screen to be colored.
10035 This action is only available if your terminal is capable of displaying
10036 color and color display has been enabled with the
10037 <A HREF="h_config_color_style">Color Style</A> option within the
10038 Setup Color screen.
10039 (In PC-Alpine, color is always enabled so there is no option to turn on.)
10040 This screen lets you add, delete, modify, or change the order of the rules
10041 that cause the lines in the MESSAGE INDEX to be displayed in different
10042 colors.
10043 <P>
10044 Each rule has a "Pattern",
10045 which is used to decide which of the rules is used; and the color that
10046 is used if the Pattern matches a particular message.
10048 <H2>Index Color Patterns</H2>
10050 In order to determine whether or not a message matches an Index Color Rule
10051 the message is compared with the rule's Pattern.
10052 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10053 Scoring, Other Rules, and Search Rules, so are described in only one place,
10054 "<A HREF="h_rule_patterns">here</A>".
10056 <P>
10057 If none of the Index Color rules is a match for a particular index line,
10058 then the color used is set using
10059 the <A HREF="h_color_setup">Setup Kolor</A> screen.
10061 <H2>Index Line Color</H2>
10063 This is the color that index lines are colored when there is a matching
10064 Pattern.
10065 This colors the whole index line, except possibly the status letters,
10066 which may be colored separately using
10067 the <A HREF="h_color_setup">Setup Kolor</A> screen.
10069 <H2>Command Descriptions</H2>
10071 <H3>Add</H3>
10073 The Add command is used to add a new rule definition to your set of
10074 rules.
10075 The new rule will be added after the highlighted rule.
10077 <H3>Delete</H3>
10079 The Delete command deletes the currently highlighted rule.
10081 <H3>Change</H3>
10083 The Change command lets you edit the nickname, Pattern,
10084 and Index Line Color of the currently highlighted rule.
10086 <H3>Shuffle</H3>
10088 The Shuffle command allows you to change the order of the rules.
10089 You may move the currently highlighted rule up or down in the list.
10090 The order of the rules is important since the rules are tested for a
10091 match starting with the first rule and continuing until a match is found.
10092 You should place the rules with more specific Patterns near the beginning
10093 of the list, and those with more general Patterns near the end so that
10094 the more specific matches will happen when appropriate.
10096 <H3>Replicate</H3>
10098 The Replicate command is used to copy an existing rule definition and modify it.
10099 The new rule will be added after the highlighted rule.
10101 <H3>IncludeFile</H3>
10103 The IncludeFile command allows you to add a rules file to your configuration.
10104 Usually, your rules will be contained in your Alpine configuration file.
10105 If you wish, some or all of your rules may be stored in a separate file.
10106 If a rules file already exists (maybe it was made by somebody else using
10107 Alpine), you may insert it before the currently highlighted rule.
10108 You may also insert an empty file or a file that does not yet exist.
10109 Once you have an empty rules file in your configuration, you may use
10110 the Shuffle command to move rules into it.
10111 In fact, that's the only way to get the initial rule into the file.
10113 <H3>eXcludeFile</H3>
10115 The eXcludeFile command removes a rules file from your rules configuration.
10116 A limitation of the program is that in order to exclude a rules file
10117 that file must have at least one rule
10118 in it, otherwise you won't be able to highlight a line in the file.
10119 So you may have to add a dummy rule to the file in order to exclude the file.
10120 <P><UL>
10121 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10122 </UL>
10123 <P>
10124 <End of help on this topic>
10125 </BODY>
10126 </HTML>
10127 ===== h_rules_filter =====
10128 <HTML>
10129 <HEAD>
10130 <TITLE>SETUP FILTERING SCREEN</TITLE>
10131 </HEAD>
10132 <BODY>
10133 <H1>SETUP FILTERING SCREEN</H1>
10134 <H2>SETUP FILTERING COMMANDS</H2>
10135 <!--chtml if pinemode="function_key"-->
10136 <PRE>
10137 Available Commands -- Group 1 Available Commands -- Group 2
10138 ------------------------------- ------------------------------
10139 F1 Show Help Text F1 Show Help Text
10140 F2 See commands in next group F2 See commands in next group
10141 F3 Back to MAIN Alpine menu
10142 F4 Change configuration for filter
10143 F5 Move to previous filter F5 Include file in filter config
10144 F6 Move to next filter F6 Exclude file from config
10145 F7 Previous page of filters
10146 F8 Next page of filters
10147 F9 Add new filter F9 Replicate existing filter
10148 F10 Delete existing filter
10149 F11 Shuffle the order of filters
10150 F12 Whereis (search filter nicknames)
10151 </PRE>
10152 <!--chtml else-->
10153 <PRE>
10154 Navigation General Alpine Commands
10155 ------------------------- -----------------------
10156 P Prev Filter ? Display this help text
10157 N Next Filter E Back to MAIN Alpine menu
10158 - Previous page
10159 Spc (space bar) Next page
10160 W WhereIs (search for word in filter nicknames)
10162 Setup Filters Commands
10163 ------------------------------------------------
10164 A Add new filter $ Shuffle the order of filters
10165 D Delete existing filter C Change configuration for highlighted filter
10166 R Replicate existing filter
10167 I Include file in filter config X Exclude file from filter config
10168 </PRE>
10169 <!--chtml endif-->
10171 <H2>Description of the Setup Filtering Screen</H2>
10173 This screen lets you add, delete, modify, or change the order of the rules
10174 that determine the filtering Alpine does on folders you view.
10175 <P>
10176 The software that actually delivers mail (the stuff that happens
10177 before Alpine is involved) for you is in a better position to do mail filtering
10178 than Alpine itself.
10179 If possible, you may want to look into using that sort of mail filtering to
10180 deliver mail to different folders, delete it, or forward it.
10181 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
10182 <P>
10183 Filtering is a way to automatically move certain messages from one folder
10184 to another or to delete messages.
10185 It can also be used to set message status (Important, Deleted, New,
10186 Answered) and to set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
10187 Alpine doesn't have the ability to forward mail to another address or
10188 to deliver vacation messages.
10189 <P>
10190 Each filtering rule has a "Pattern" and a "Filter Action".
10191 When a folder is opened, when new mail arrives in an open folder, or
10192 when mail is Expunged from a folder; each
10193 message is compared with the Patterns of your filtering rules.
10194 The comparisons start with the first rule and keep going until there
10195 is a match.
10196 If a match is found, the message may be deleted or moved, depending on
10197 the setting of the Filter Action.
10198 If the message is not deleted, it may have its status altered.
10200 <P>
10201 <EM>NOTE:</EM>
10202 When setting up a Pattern used to delete messages,
10203 it is recommended that you test the Pattern first with a "Move"
10204 folder specified in
10205 case unintended matches occur. Messages that are deleted will be removed
10206 from the folder and <EM>unrecoverable</EM> from within Alpine after the
10207 next Expunge command or once the folder being filtered has been closed.
10209 <H2>Filter Patterns</H2>
10211 In order to determine whether or not a message matches a filter the message is
10212 compared with the Filter's Pattern.
10213 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10214 Scoring, Other Rules, and Search Rules, so are described in only one place,
10215 "<A HREF="h_rule_patterns">here</A>".
10216 <P>
10217 Since filtering is a potentially destructive action, if you have a filtering
10218 Pattern with nothing other than Current Folder Type set, that filtering
10219 rule is ignored.
10221 <H2>Filter Actions</H2>
10223 Once a filter match is found for a particular message, there are some actions
10224 that may be taken.
10225 First, the message may have its status changed.
10226 This is the same message status that you can manipulate manually using the
10227 <a href="h_common_flag">Flag Command</a>.
10228 There are always four elements of message status that you can control.
10229 You can set or clear the Important status, the New status, the Deleted
10230 status, and the Answered status.
10231 Of course, if the filter is going to delete the message,
10232 then there is no point in setting message status.
10233 You may also be able to set user-defined keywords for a message.
10234 Read a little about keywords in the help text for the
10235 <A HREF="h_common_flag">Flag</A> command.
10236 <P>
10237 Second, the filter may delete or move the message.
10238 Deleting the message marks it Deleted and removes it from view.
10239 It is effectively gone forever (though it technically is still there until
10240 the next expunge command, which may happen implicitly).
10241 Moving the message moves it from the open folder into the folder
10242 listed on the "Folder List" line of the filter configuration.
10243 If you list more than one folder name (separated by commas) then the message
10244 will be copied to each of those folders.
10245 In any case, if "Delete" or "Move" is set then the
10246 message is removed from the current folder.
10247 If you just want to set the messages status without deleting it from
10248 the folder, then set the filter action to
10249 "Just Set Message Status".
10250 <P>
10251 (There is no way to do a Copy instead of a Move, due to the difficulties
10252 involved in keeping track of whether or not a message has
10253 already been copied.)
10255 <H2>Command Descriptions</H2>
10257 <H3>Add</H3>
10259 The Add command is used to add a new filter definition to your set of
10260 filters.
10261 The new filter will be added after the highlighted filter.
10263 <H3>Delete</H3>
10265 The Delete command deletes the currently highlighted filter.
10267 <H3>Change</H3>
10269 The Change command lets you edit the nickname, Pattern,
10270 and Folder of the currently highlighted filter.
10272 <H3>Shuffle</H3>
10274 The Shuffle command allows you to change the order of the filters.
10275 You may move the currently highlighted filter up or down in the list.
10276 The order of the filters is important since the filters are tested for a
10277 match starting with the first filter and continuing until a match is found.
10278 You should place the filters with more specific Patterns near the beginning
10279 of the list, and those with more general Patterns near the end so that
10280 the more specific matches will happen when appropriate.
10282 <H3>Replicate</H3>
10284 The Replicate command is used to copy an existing filter and modify it.
10285 The new filter will be added after the highlighted filter.
10287 <H3>IncludeFile</H3>
10289 The IncludeFile command allows you to add a filters file to your configuration.
10290 Usually, your filters will be contained in your Alpine configuration file.
10291 If you wish, some or all of your filters may be stored in a separate file.
10292 If a filters file already exists (maybe it was made by somebody else using
10293 Alpine), you may insert it before the currently highlighted filter.
10294 You may also insert an empty file or a file that does not yet exist.
10295 Once you have an empty filters file in your configuration, you may use
10296 the Shuffle command to move filters into it.
10297 In fact, that's the only way to get the initial filter into the file.
10299 <H3>eXcludeFile</H3>
10301 The eXcludeFile command removes a filters file from your filters configuration.
10302 A limitation of the program is that in order to exclude a filters file
10303 that file must have at least one filter
10304 in it, otherwise you won't be able to highlight a line in the file.
10305 So you may have to add a dummy filter to the file in order to exclude the file.
10306 <P><UL>
10307 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10308 </UL>
10309 <P>
10310 <H3>Performance Considerations</H3>
10311 The number and type of patterns being tested can
10312 adversely effect performance. Issues to be aware
10313 of include:
10314 <P>
10315 <UL>
10316 <LI> The more filters you have defined the longer it will take to run down
10317 the list. Deleting unused filters is a good idea.
10318 <LI> Filtering in newsgroups served by an NNTP server will be slow
10319 if your patterns include tests other than "From:"
10320 or "Subject:".
10321 </UL>
10322 <P>
10323 <End of help on this topic>
10324 </BODY>
10325 </HTML>
10326 ===== h_rules_score =====
10327 <HTML>
10328 <HEAD>
10329 <TITLE>SETUP SCORING SCREEN</TITLE>
10330 </HEAD>
10331 <BODY>
10332 <H1>SETUP SCORING SCREEN</H1>
10333 <H2>SETUP SCORING COMMANDS</H2>
10334 <!--chtml if pinemode="function_key"-->
10335 <PRE>
10336 Available Commands -- Group 1 Available Commands -- Group 2
10337 ------------------------------- ------------------------------
10338 F1 Show Help Text F1 Show Help Text
10339 F2 See commands in next group F2 See commands in next group
10340 F3 Back to MAIN Alpine menu
10341 F4 Change configuration for rule
10342 F5 Move to previous rule F5 Include file in rule config
10343 F6 Move to next rule F6 Exclude file from config
10344 F7 Previous page of rules
10345 F8 Next page of rules
10346 F9 Add new rule F9 Replicate existing rule
10347 F10 Delete existing rule
10348 F11 Shuffle the order of rules
10349 F12 Whereis (search rule nicknames)
10350 </PRE>
10351 <!--chtml else-->
10352 <PRE>
10353 Navigation General Alpine Commands
10354 ------------------------- -----------------------
10355 P Prev rule ? Display this help text
10356 N Next rule E Back to MAIN Alpine menu
10357 - Previous page
10358 Spc (space bar) Next page
10359 W WhereIs (search for word in rule nicknames)
10361 Setup Scoring Commands
10362 ------------------------------------------------
10363 A Add new rule $ Shuffle the order of rules
10364 D Delete existing rule C Change configuration for highlighted rule
10365 R Replicate existing rule
10366 I Include file in rule config X Exclude file from rule config
10367 </PRE>
10368 <!--chtml endif-->
10370 <H2>Description of the Setup Scoring Screen</H2>
10372 Most people will not use scores at all, but if you do use them, here's how
10373 they work in Alpine.
10374 Using this screen, you may define Scoring rules.
10375 The score for a message is calculated by looking at every Score rule defined
10376 and adding up the Score Values for the ones that match the message.
10377 If there are no matches for a message, it has a score of zero.
10378 Message scores may be used a couple of ways in Alpine.
10380 <H3>Sorting by Score</H3>
10382 One of the methods you may use to sort message indexes is to sort by
10383 score.
10384 The scores of all the messages in a folder will be calculated and then
10385 the index will be ordered by placing the messages in order of ascending or
10386 descending score.
10388 <H3>Scores for use in Patterns</H3>
10390 The Patterns used for Roles, Index Line Coloring, and Filtering have a
10391 category labeled "Score Interval".
10392 When a message is being compared with a Pattern to check for a match, if
10393 the Score Interval is set only messages that have a score somewhere in
10394 the interval are a match.
10396 <H2>Scoring Rule Patterns</H2>
10398 In order to determine whether or not a message matches a scoring rule
10399 the message is compared with the rule's Pattern.
10400 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10401 Scoring, Other Rules, and Search Rules, so are described in only one place,
10402 "<A HREF="h_rule_patterns">here</A>".
10404 <P>
10405 Actually, Scoring rule Patterns are slightly different from the other types of
10406 Patterns because Scoring rule Patterns don't contain a Score Interval.
10407 In other words, when calculating the score for a message, which is done
10408 by looking at the Scoring rule Patterns, scores aren't used.
10410 <H2>Score Value</H2>
10412 This is the value that will be added to the score for a message if the
10413 rule's Pattern is a match.
10414 Each individual Score Value is an integer between -100 and 100, and the
10415 values from matching rules are added together to get a message's score.
10416 There is also a way to extract the value from a particular header of each
10417 message. See the help text for Score Value for further information.
10419 <H2>Command Descriptions</H2>
10421 <H3>Add</H3>
10423 The Add command is used to add a new scoring rule definition.
10424 The new rule will be added after the highlighted rule.
10426 <H3>Delete</H3>
10428 The Delete command deletes the currently highlighted scoring rule.
10430 <H3>Change</H3>
10432 The Change command lets you edit the nickname, Pattern,
10433 and Score Value of the currently highlighted scoring rule.
10435 <H3>Shuffle</H3>
10437 The Shuffle command allows you to change the order of the scoring rules.
10438 You may move the currently highlighted rule up or down in the list.
10439 The order of the rules is important since the rules are tested for a
10440 match starting with the first rule and continuing until a match is found.
10441 You should place the rules with more specific Patterns near the beginning
10442 of the list, and those with more general Patterns near the end so that
10443 the more specific matches will happen when appropriate.
10445 <H3>Replicate</H3>
10447 The Replicate command is used to copy an existing rule and modify it.
10448 The new rule will be added after the highlighted rule.
10450 <H3>IncludeFile</H3>
10452 The IncludeFile command allows you to add a rules file to your configuration.
10453 Usually, your rules will be contained in your Alpine configuration file.
10454 If you wish, some or all of your rules may be stored in a separate file.
10455 If a rules file already exists (maybe it was made by somebody else using
10456 Alpine), you may insert it before the currently highlighted rule.
10457 You may also insert an empty file or a file that does not yet exist.
10458 Once you have an empty rules file in your configuration, you may use
10459 the Shuffle command to move rules into it.
10460 In fact, that's the only way to get the initial rule into the file.
10462 <H3>eXcludeFile</H3>
10464 The eXcludeFile command removes a rules file from your rules configuration.
10465 A limitation of the program is that in order to exclude a rules file
10466 that file must have at least one rule
10467 in it, otherwise you won't be able to highlight a line in the file.
10468 So you may have to add a dummy rule to the file in order to exclude the file.
10469 <P><UL>
10470 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10471 </UL>
10472 <P>
10473 <End of help on this topic>
10474 </BODY>
10475 </HTML>
10476 ===== h_direct_config =====
10477 <HTML>
10478 <HEAD>
10479 <TITLE>SETUP LDAP DIRECTORY SERVERS SCREEN</TITLE>
10480 </HEAD>
10481 <BODY>
10482 <H1>SETUP LDAP DIRECTORY SERVERS SCREEN</H1>
10483 <H2>SETUP LDAP DIRECTORY SERVERS COMMANDS</H2>
10484 <!--chtml if pinemode="function_key"-->
10485 <PRE>
10486 Available Commands
10487 -------------------------------
10488 F1 Show Help Text
10489 F3 Back to MAIN Alpine menu
10490 F4 Change configuration for directory server
10491 F5 Move to previous directory server
10492 F6 Move to next directory server
10493 F7 Previous page of directory servers
10494 F8 Next page of directory servers
10495 F9 Add new directory server
10496 F10 Delete existing directory server
10497 F11 Shuffle the order of directory servers
10498 F12 Whereis (search directory server titles)
10499 </PRE>
10500 <!--chtml else-->
10501 <PRE>
10502 Navigation General Alpine Commands
10503 ------------------------- -----------------------
10504 P Prev Directory Server ? Display this help text
10505 N Next Directory Server E Back to MAIN Alpine menu
10506 - Previous page
10507 Spc (space bar) Next page
10508 W WhereIs (search for word in directory server titles)
10510 Setup LDAP Directory Server Commands
10511 ------------------------------------------------
10512 A Add new directory server $ Shuffle the order of directory servers
10513 D Delete existing dir server C Change configuration for highlighted server
10514 </PRE>
10515 <!--chtml endif-->
10517 <H2>Description of the Setup LDAP Directory Servers Screen</H2>
10519 This screen lets you add, delete, modify, or change the order of your
10520 directory servers. You may also set some optional behavior for each server.
10521 The "Add Dir" command brings up a blank form to
10522 fill in. You will have to supply at least the name of the LDAP server.
10523 You will often have to supply a search base to be used with that server,
10524 as well. Once the form has been brought up on your screen, there is help
10525 available for each of the options you may set.
10526 <P>
10527 The "Del Dir" command allows you to remove a directory server
10528 from your configuration.
10529 <P>
10530 The "Change" command is similar to the "Add Dir" command.
10531 The difference is that instead of bringing up a form for a new server
10532 configuration, you are changing the configuration of an existing entry.
10533 For example, you might want to correct a typing error, change a
10534 nickname, or change one of the options set for that server.
10535 <P>
10536 The "Shuffle" command is used to change the order of directory
10537 servers.
10538 <P><UL>
10539 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10540 </UL>
10541 <P>
10542 <End of help on this topic>
10543 </BODY>
10544 </HTML>
10545 ============= h_address_display ========================
10546 <HTML>
10547 <HEAD>
10548 <TITLE>SEARCH RESULTS INDEX</TITLE>
10549 </HEAD>
10550 <BODY>
10551 <H1>SEARCH RESULTS INDEX</H1>
10552 This screen shows the results, if any, of your Directory Server search.
10553 Commands (besides those for screen navigation) are:
10554 <DL>
10555 <DT>View
10556 <!--chtml if pinemode="function_key"-->
10557 (F4)
10558 <!--chtml else-->
10559 (V)
10560 <!--chtml endif-->
10561 </DT>
10562 <DD>See the full information for the selected entry.
10564 <DT>Compose
10565 <!--chtml if pinemode="function_key"-->
10566 (F9)
10567 <!--chtml else-->
10568 (C)
10569 <!--chtml endif--></DT>
10570 <DD>Compose a message with the selected entry as the recipient.
10572 <DT>Role
10573 <!--chtml if pinemode="function_key"-->
10574 (F2)
10575 <!--chtml else-->
10576 (#)
10577 <!--chtml endif--></DT>
10578 <DD>Compose a message with the selected entry as the recipient. This differs
10579 from Compose in that you may select a role before beginning your composition.
10581 <DT>Forward
10582 <!--chtml if pinemode="function_key"-->
10583 (F10)
10584 <!--chtml else-->
10585 (F)
10586 <!--chtml endif--></DT>
10587 <DD>Send the full information for the selected entry as an
10588 email message to someone else.
10590 <DT>Save
10591 <!--chtml if pinemode="function_key"-->
10592 (F11)
10593 <!--chtml else-->
10594 (S)
10595 <!--chtml endif-->
10596 </DT>
10597 <DD>Save to your address book:
10598 <UL>
10599 <LI>the result of the search (as just found through your query) for the
10600 selected entry; or
10601 <LI>the selected entry for repeated Directory Server searching when used
10602 in the future.
10603 </UL>
10604 or<BR>
10605 Export to a file (external to Alpine):
10606 <UL>
10607 <LI>the full information for the selected entry; or
10608 <LI>the email address from the selected entry; or
10609 <LI>the selected entry in <A HREF="h_whatis_vcard">vCard</A> format.
10610 </UL>
10611 <DT>WhereIs
10612 <!--chtml if pinemode="function_key"-->
10613 (F12)
10614 <!--chtml else-->
10615 (W)
10616 <!--chtml endif-->
10617 </DT>
10618 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10619 displayed text, not the full records for each entry.)
10620 </DL>
10621 <End of help on this topic>
10622 </BODY>
10623 </HTML>
10624 ============= h_address_select ========================
10625 <HTML>
10626 <HEAD>
10627 <TITLE>SEARCH RESULTS INDEX</TITLE>
10628 </HEAD>
10629 <BODY>
10630 <H1>SEARCH RESULTS INDEX</H1>
10631 This screen shows the results, if any, of your Directory Server search.
10632 Commands (besides those for screen navigation) are:
10633 <DL>
10634 <DT>Select
10635 </DT>
10636 <DD>Select this entry for use.
10638 <DT>ExitSelect
10639 <DD>Exit without selecting any of the entries.
10641 <DT>WhereIs
10642 </DT>
10643 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10644 displayed text, not the full records for each entry.)
10645 </DL>
10646 <End of help on this topic>
10647 </BODY>
10648 </HTML>
10649 ===== h_folder_maint =====
10650 <HTML>
10651 <HEAD>
10652 <TITLE>Help for Folder List</TITLE>
10653 </HEAD>
10654 <BODY>
10655 <H1>FOLDER LIST COMMANDS</H1>
10656 <!--chtml if pinemode="function_key"-->
10657 <PRE>
10658 Available Commands -- Group 1 Available Commands -- Group 2
10659 ------------------------------- ------------------------------
10660 F1 Show Help Text F1 Show Help Text
10661 F2 See commands in next group F2 See commands in next group
10662 F3 MAIN MENU Screen F3 Quit Alpine
10663 F4 Select folder and view it F4 MAIN MENU Screen
10664 F5 Move to previous folder
10665 F6 Move to next folder F6 Specify a folder to go to
10666 F7 Show previous screen of listing F7 Show MESSAGE INDEX of current folder
10667 F8 Show next screen of listing F8 Compose a message
10668 F9 Add a new folder F9 Print folder listing
10669 F10 Delete selected folder
10670 F11 Rename selected folder
10671 F12 Whereis (search folder names)
10673 Available Commands -- Group 3
10674 F1 Show Help Text
10675 F2 See commands in next group
10676 F5 Go to next new message
10677 (or count recent messages if <A HREF="h_config_tab_checks_recent"><!--#echo var="FEAT_tab-checks-recent"--></A> is set)
10678 F8 Compose a message using roles
10679 F9 Export folder to a file
10680 F10 Import the file back to a folder
10681 </PRE>
10682 <!--chtml else-->
10683 <PRE>
10684 Navigating the Folder Screen Operations on the Selected Folder
10685 ---------------------------- ---------------------------------
10686 P Move to previous folder V View Index of selected folder
10687 N Move to next folder D Delete
10688 - Show previous page of listing R Rename
10689 Spc (space bar) Show next page E Export to file
10690 U Import from file to folder
10692 FOLDER LIST Screen Commands General Alpine Command
10693 --------------------------- -----------------------
10694 A Add a folder O Show all other available commands
10695 G Specify a folder to go to ? Show Help text
10696 I Show MESSAGE INDEX of current folder M MAIN MENU Screen
10697 W Whereis (search folder names) Q Quit Alpine
10698 % Print folder listing C Compose a message
10699 # Compose a message using roles
10700 </PRE>
10701 <!--chtml endif-->
10702 <P>
10703 These commands are only available in the FOLDER LIST screen when the
10704 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"
10705 feature</A> is set in the SETUP CONFIGURATION screen:<DL>
10706 <DT>Select:</DT>
10707 <DD>Select folders by certain criteria:<UL>
10708 <LI>All: of limited use, since there is no Apply command.
10709 <LI>by Property: <UL>
10710 <LI>folder contains messages not yet seen
10711 <LI>folder contains new messages
10712 <LI>folder contains exactly as many, more, or fewer messages
10713 than a given number
10714 </UL>
10715 <LI>by Text: <UL>
10716 <LI>contained in name of folder (Name Select)
10717 <LI>contained in messages in folder (Content Select)
10718 </UL>
10719 </UL></DD>
10721 <DT>Select current:</DT>
10722 <DD>Select the folder the cursor is on. (Can be used to "manually"
10723 add one or more folders to a set created with the Select command described
10724 above.)</DD>
10725 <DT>Zoom mode:</DT>
10726 <DD>Toggles display of only selected folders or all folders on and off.</DD>
10727 </DL>
10728 <P>
10729 If the feature
10730 <A HREF="h_config_tab_checks_recent">"<!--#echo var="FEAT_tab-checks-recent"-->"</A>
10731 is set then the TAB key will display the number of recent messages and
10732 the total number of messages in the highlighted folder.
10733 <P>
10734 The "Export" command causes the lowest common denominator style
10735 mailbox to be written to a file.
10736 If the file already exists, you are asked if you want to delete it.
10737 If you say No, then the operation is aborted.
10738 Export might be a reasonable way to store a backup or an archival copy of
10739 a folder.
10740 The exported-to file is a local file on the system where you are running Alpine.
10741 The "Import" command is the opposite of the Export command.
10742 It reads a file created by Export and asks where it should save it in your
10743 folders.
10744 This could be a new folder or an existing folder.
10745 If the folder already exists, the messages from the exported file will be
10746 appended to the folder.
10747 <P>
10748 <CENTER>Description of the FOLDER LIST Screen</CENTER>
10750 The purpose of the FOLDER LIST screen is to help you browse and manage
10751 the folders and directories (also known as "hierarchy")
10752 contained within a collection.
10754 <P>
10755 Folders and directories are arranged alphabetically across lines of
10756 the screen. Directories, if present, are denoted by a special
10757 character at the end of the name known as the hierarchy delimiter
10758 (typically, "/"). By default, folders and directories are
10759 mixed together. The
10760 "<A HREF="h_config_fld_sort_rule"><!--#echo var="VAR_folder-sort-rule"--></A>"
10761 configuration option can be used to group directories toward the
10762 beginning or end of the list.
10764 <P>
10765 The Next/Prev Page commands help browse the list, the Next/Prev Fldr
10766 commands change the "selected" (i.e., highlighted) folder or
10767 directory, and the View Fldr/Dir commands will "open" the
10768 selected item. Folder and directory management is provided via the
10769 Rename, Delete and Add commands.
10771 <P><CENTER>About Folders</CENTER>
10772 What are Folders?<P>
10774 Folders are simply files where messages are kept. Every message has to be
10775 in a folder. Most every Alpine user starts out with 3 folders: an INBOX, a
10776 folder for sent mail and a folder for saved messages.<P>
10778 You may create as many other folders as you wish. They must be given
10779 names that can be filenames on the filesystem.
10780 <P>
10782 You can move messages from one folder to another by opening the original
10783 folder and saving messages into the other folder just as you can save
10784 message from your INBOX to any other folder.<P>
10786 Folders are typically just files in the filesystem. However, the files
10787 that are
10788 folders have some special formatting in them (so that Alpine knows where one
10789 message ends and another begins) and should <EM>not</EM> be edited outside of
10790 Alpine. If you want copies of your messages in text files that you can edit
10791 or otherwise manipulate, use the Export command to copy them from Alpine into
10792 your regular file area.
10794 <P>
10795 FOR MORE INFORMATION: See the section on
10796 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
10797 <P>
10798 <CENTER>About Directories</CENTER>
10799 <P>
10800 A directory is simply a container used to group folders within a
10801 folder list. You can create as many directories as you like. And
10802 directories can even contain directories themselves.
10804 <P>
10805 SPECIAL NOTES: When accessing folders on an IMAP server, it is important
10806 to note that not all IMAP servers support directories. If you find that
10807 the Add command fails to offer the "Create Directory" subcommand,
10808 then it's likely that directories are not supported by the server serving
10809 in that collection.
10811 <P>
10812 Similarly, servers that do provide for directories may not do so in
10813 the same way. On some servers, for example, each folder name you
10814 create is at the same time capable of being a directory. When this
10815 happens, Alpine will display both the folder name and the name of the
10816 directory (with trailing hierarchy delimiter) in the folder list.
10818 <P>
10819 Another issue with IMAP access, though with a much smaller set of servers,
10820 is that not all servers accept the request to list out the available
10821 folders and directories in the same way. If you find yourself having
10822 trouble viewing folders on your server, you might investigate the
10823 "<A HREF="h_config_lame_list_mode"><!--#echo var="FEAT_enable-lame-list-mode"--></A>"
10824 feature.
10825 <P>
10826 <UL>
10827 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10828 </UL>
10829 <P>
10830 <End of help on this topic>
10831 </BODY>
10832 </HTML>
10833 ========= h_valid_folder_names ========
10834 <HTML>
10835 <HEAD>
10836 <TITLE>Explanation of Valid Folder Names</TITLE>
10837 </HEAD>
10838 <BODY>
10839 <H1>Folder Name Syntax Explained</H1>
10841 Once your folder collections are defined, you can usually refer to
10842 folders by their simple (unqualified) name, or pick from a FOLDER LIST
10843 display. However, understanding the complete syntax for folder names,
10844 both local and remote, is handy when using the Goto command and when
10845 you are adding new folder collections via the Setups/collectionList screen.
10846 <P>
10847 An Alpine folder name looks like
10849 <P>
10850 <CENTER><SAMP>[{<remote-specification>}][#<namespace>]<namespace-specific-part></SAMP></CENTER>
10851 <P>
10853 The square brackets ([]) mean that the part is optional.
10855 <P>
10856 If there is no remote-specification, then the folder name is interpreted
10857 locally on the computer running Alpine.
10858 Local folder names depend on the operating system used by the computer
10859 running Alpine, as well as the configuration of that system. For example,
10860 "C:\PINE\FOLDERS\OCT-94" might exist on a PC, and
10861 "~/mail/september-1994" might be a reasonable folder name on a
10862 system running Unix.
10864 <P>
10865 Alpine users have the option of using folders that are stored on some other
10866 computer. Alpine accesses remote folders via IMAP (the Internet Message
10867 Access Protocol), or in the case of news, via NNTP (the Network News
10868 Transport Protocol). To be able to access remote folders in Alpine, the
10869 remote host must be running the appropriate server software (imapd or
10870 nntpd) and you must correctly specify the name of the folder to Alpine,
10871 including the domain name of the remote machine. For example,
10872 <P>
10873 <CENTER><SAMP>{monet.art.example.com}INBOX</SAMP></CENTER>
10874 <P>
10875 could be a remote folder specification, and so could
10876 <P>
10877 <CENTER><SAMP>{unixhost.art.example.com}~/mail/september-1994</SAMP></CENTER>
10878 and
10879 <P>
10880 <CENTER><SAMP>{winhost.art.example.com}\mymail\SEP-94</SAMP></CENTER>
10881 <P>
10882 Note that in the case of remote folders, the directory/file path in the specification is
10883 determined by the operating system of the remote computer, <B>not</B> by
10884 the operating system of the computer on which you are running Alpine.
10885 <P>
10886 As you can tell, the name of the computer is in {} brackets
10887 followed immediately by the name of the folder. (In each of these cases the
10888 optional namespace is missing.) If, as in these
10889 examples, there is no remote access protocol specified, then IMAP is
10890 assumed. Check
10891 <A HREF="h_folder_server_syntax">here</A>
10892 for a more detailed look at what options can be placed between the brackets.
10893 If there are no brackets at all, then the folder name is interpreted locally
10894 on the computer on which you are running Alpine.
10896 <P>
10897 To the right of the brackets when a server name is present, or at the
10898 start of the foldername if no server is present, the sharp sign,
10899 "#", holds special meaning. It indicates a folder name
10900 outside the area reserved for your personal folders. In fact, it's
10901 used to indicate both the name of the folder, and a special phrase
10902 telling Alpine how to interpret the name that follows.
10904 <P>
10905 So, for example, Alpine can be used to access a newsgroup that might be
10906 available on your computer using:
10907 <P>
10908 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
10909 <P>
10910 The sharp sign indicates the folder name is outside your personal
10911 folder area. The "news." phrase after it tells Alpine to
10912 interpret the remainder of the name as a newsgroup.
10914 <P>
10915 Similarly, to access a newsgroup on your IMAP server, you might
10916 use something like:
10917 <P>
10918 <CENTER><SAMP>{wharhol.art.example.com}#news.comp.mail.misc</SAMP></CENTER>
10920 <P>
10921 There are a number of such special phrases (or "namespaces")
10922 available. For a more detailed explanation read about
10923 <A HREF="h_folder_name_namespaces">Namespaces</A>.
10925 <P>
10926 Note that "INBOX" has special meaning in both local and remote folder
10927 names. The name INBOX refers to your "principal incoming
10928 message folder" and will be mapped to the actual file name used for your
10929 INBOX on any given host. Therefore, a name like
10930 "{xxx.art.example.com}INBOX" refers to whatever file is used to
10931 store incoming mail for you on that particular host.
10933 <P>
10934 <End of help on this topic>
10935 </BODY>
10936 </HTML>
10937 ======= h_folder_name_namespaces =======
10938 <HTML>
10939 <HEAD>
10940 <TITLE>FOLDER NAME NAMESPACES EXPLAINED</TITLE>
10941 </HEAD>
10942 <BODY>
10943 <H1>Folder Name Namespaces Explained</H1>
10945 An Alpine folder name looks like
10947 <P>
10948 <CENTER><SAMP>[{<remote-specification>}][#<namespace>][<namespace-specific-part>]</SAMP></CENTER>
10949 <P>
10951 The local part of a folder name has an optional "Namespace" which
10952 tells Alpine how to interpret the rest of the name.
10954 <P>
10955 By default the folder name is interpreted as defining a section of your personal
10956 folder area. This area and how you specify it are defined by the
10957 server, if one is specified, or, typically, the home
10958 directory, if no server is defined.
10960 <P>
10961 If a namespace is specified, it begins with the
10962 sharp, "#", character followed by the name of the namespace
10963 and then the namespace's path-element-delimiter. Aside from the
10964 path's format, namespaces can also imply access rights, content
10965 policy, audience, location, and, occasionally, access methods.
10967 <P>
10968 Each server exports its own set (possibly of size one) of
10969 namespaces. Hence, it's likely communication with your server's
10970 administrator will be required for specific configurations. Some of
10971 the more common namespaces, however, include:
10973 <DL>
10974 <DT>#news.</DT>
10975 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
10976 names are hierarchically defined with each level delimited by a period.
10977 <P>
10978 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
10979 <P>
10980 </DD>
10981 <DT>#public/</DT>
10982 <DD>This specifies a folder area that the server may export to the general
10983 public.
10984 </DD>
10985 <DT>#shared/</DT>
10986 <DD>This specifies a folder area that the server may export to groups
10987 of users.
10988 </DD>
10989 <DT>#ftp/</DT>
10990 <DD>This specifies a folder area that is the same as that it may have
10991 exported via the "File Transfer Protocol".
10992 </DD>
10993 <DT>#mh/</DT>
10994 <DD>This specifies the personal folder area associated with folders
10995 and directories that were created using the MH message handling system.
10996 </DD>
10997 <DT>#move/</DT>
10998 <DD>This namespace is interpreted locally by Alpine. It has an unusual interpretation and format.
10999 <P>
11000 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
11001 <P>
11002 The #move namespace is followed by two folder names separated by a delimiter
11003 character.
11004 The delimiter character may be any character that does not appear in
11005 the MailDropFolder name.
11006 The meaning of #move is that mail will be copied from the MailDropFolder to
11007 the DestinationFolder and then deleted (if possible) from the MailDropFolder.
11008 Periodic checks at frequency
11009 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A>, but with a minimum
11010 time between checks set by
11011 <A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>,
11012 are made for new mail arriving in the MailDropFolder.
11013 An example that copies mail from a POP inbox to a local folder follows
11014 <P>
11015 <CENTER><SAMP>#move+{popserver.example.com/pop3/ssl}inbox+local folder</SAMP></CENTER>
11016 <P>
11017 To you it appears that mail is being delivered to the local folder when it
11018 is copied from the MailDropFolder, and you read mail from the local folder.
11019 <P>
11020 Note that if the DestinationFolder does not exist then the messages are not
11021 copied from the MailDropFolder.
11022 A #move folder may only be used as an
11023 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
11024 an Inbox.
11025 When you are in the FOLDER LIST of Incoming Message Folders (after turning
11026 on the
11027 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
11028 option)
11029 the Add command has a subcommand "Use Mail Drop"
11030 which may be helpful for defining the folder in your Alpine configuration.
11031 The same is true when you edit the
11032 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
11033 option in Setup/Config.
11034 Each of these configuration methods will also create the DestinationFolder
11035 if it doesn't already exist.
11036 If you are having problems, make sure the DestinationFolder exists.
11037 You may find some more useful information about Mail Drops at
11038 <A HREF="h_maildrop">What is a Mail Drop?</A>.
11039 </DD>
11040 </DL>
11041 <P>
11043 In addition, the server may support access to other user's folders,
11044 provided you have suitable permissions. Common methods use a prefix
11045 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
11046 indicate the root of the other user's folder area.
11048 <P>
11049 No, nothing's simple.
11051 <P>
11052 <End of help on this topic>
11053 </BODY>
11054 </HTML>
11055 ============= h_whatis_vcard ========================
11056 <HTML>
11057 <HEAD>
11058 <TITLE>VCARD EXPLAINED</TITLE>
11059 </HEAD>
11060 <BODY>
11061 <H1>What is the vCard format?</H1>
11062 A "vCard" is a sort of electronic business card, for exchanging
11063 information about and among people and organizations electronically.
11064 More information about vCard can be found (as of May 1998) on the WWW site
11065 of the Internet Mail Consortium at the URL:
11066 <P>
11067 <CENTER><A HREF="http://www.imc.org/pdi/">http://www.imc.org/pdi/</A></CENTER>
11068 <P>
11069 <End of help on this topic>
11070 </BODY>
11071 </HTML>
11072 ===== h_folder_open =====
11073 <HTML>
11074 <HEAD>
11075 <TITLE>Explanation of Folder Selection</TITLE>
11076 </HEAD>
11077 <BODY>
11078 <BR>
11079 <BR>
11080 This screen is designed to allow you to quickly and easily survey your
11081 folders and select one to open.
11082 <!--chtml if pinemode="function_key"-->
11083 <PRE>
11084 Navigating the List of Folders General Alpine Commands
11085 ------------------------------ -----------------------
11086 P Move to previous folder ? Show this help text
11087 N Move to next folder
11088 - Show previous screen of folders
11089 Spc (space bar) Show next screen
11090 W WhereIs (search folder names)
11092 Folder Selection Commands
11093 -------------------------
11094 E Exit the Folder Select menu (without selecting a folder)
11095 S Select the currently highlighted folder
11096 </PRE>
11097 <!--chtml else-->
11098 <PRE>
11099 Navigating the List of Folders General Alpine Commands
11100 ------------------------------ -----------------------
11101 F5 Move to previous folder F1 Show this help text
11102 F6 Move to next folder
11103 F7 Show previous screen of folders
11104 F8 Show next screen of folders
11105 F12 WhereIs (search folder names)
11107 Folder Selection Commands
11108 -------------------------
11109 F3 Exit the Folder Select menu (without selecting a folder)
11110 F4 Select the currently highlighted folder
11111 </PRE>
11112 <!--chtml endif-->
11113 <P>
11114 FOR MORE INFORMATION: See the section on
11115 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11116 <P>
11117 <End of help on this topic>
11118 </BODY>
11119 </HTML>
11120 ===== h_folder_subscribe =====
11121 <HTML>
11122 <HEAD>
11123 <TITLE>Newsgroup Subcribe Screen explained</TITLE>
11124 </HEAD>
11125 <BODY>
11126 <H1>FOLDER SUBSCRIBE HELP</H1>
11128 This screen is designed to help you subscribe to newsgroups you are
11129 not currently subscribed to. The screen display is a list of all
11130 available newsgroups (or possibly a partial list if you specified a
11131 partial name when entering the screen). Groups you have already
11132 subscribed to have the letters "SUB" next to them. You may
11133 select a single new group to subscribe to by moving the cursor to that
11134 group and pressing "S" or carriage return. Alternatively,
11135 you may change into ListMode with the "ListMode" command.
11136 The display will change slightly so that each group has a checkbox in
11137 front of it. Use the cursor and the Set/Unset command to place an
11138 "X" in front of each newsgroup you wish to subscribe to.
11139 <P>
11141 When you are finished marking groups, the "Subscribe"
11142 command will subscribe you to those groups you have marked. Note, you
11143 may not unsubscribe to groups with this command. Instead of the
11144 "A" "Subscribe" command, use the "D"
11145 UnSbscrbe command.
11146 <P>
11148 <!--chtml if pinemode="function_key"-->
11149 <PRE>
11150 Navigating the List of Newsgroups General Alpine Commands
11151 --------------------------------- -----------------------
11152 F5 Move to previous group F1 Show this help text
11153 F6 Move to next group
11154 F7 Show previous screen of groups
11155 F8 Show next screen of groups
11156 F12 WhereIs (search group names)
11157 F9 Use ListMode
11159 Group Selection Commands
11160 -------------------------
11161 F3 Exit the News Subscribe menu (without selecting any groups)
11162 F4 Subscribe to the currently highlighted newsgroup
11163 </PRE>
11164 <!--chtml else-->
11165 <PRE>
11166 Navigating the List of Newsgroups General Alpine Commands
11167 --------------------------------- -----------------------
11168 P Move to previous group ? Show this help text
11169 N Move to next group
11170 - Show previous screen of groups
11171 Spc (space bar) Show next screen
11172 W WhereIs (search group names)
11173 L Use ListMode
11175 Group Selection Commands
11176 -------------------------
11177 E Exit the News Subscribe menu (without selecting any groups)
11178 S Subscribe to the currently highlighted newsgroup
11179 </PRE>
11180 <!--chtml endif-->
11181 <P>
11182 When in ListMode, there is an additional command for marking groups to
11183 subscribe to:
11184 <P>
11185 <!--chtml if pinemode="function_key"-->
11186 <PRE>
11187 ListMode Commands
11188 -------------------------
11189 F9 Set or unset the highlighted group
11190 </PRE>
11191 <!--chtml else-->
11192 <PRE>
11193 ListMode Commands
11194 -------------------------
11195 X Set or unset the highlighted group
11196 </PRE>
11197 <!--chtml endif-->
11198 <P>
11199 <End of help on this topic>
11200 </BODY>
11201 </HTML>
11202 ===== h_folder_postnews =====
11203 <HTML>
11204 <HEAD>
11205 <TITLE>Newsgroup selecting for Posting explained</TITLE>
11206 </HEAD>
11207 <BODY>
11208 This screen is designed to allow you to quickly and easily survey
11209 the available newsgroups and select one to post news to.
11210 <P>
11211 <!--chtml if pinemode="function_key"-->
11212 <PRE>
11213 Navigating the List of Newsgroups General Alpine Commands
11214 --------------------------------- -----------------------
11215 F5 Move to previous group F1 Show this help text
11216 F6 Move to next group
11217 F7 Show previous screen of groups
11218 F8 Show next screen of groups
11219 F12 WhereIs (search group names)
11221 Group Selection Commands
11222 -------------------------
11223 F3 Exit the Selection menu (without selecting a group)
11224 F4 Select the currently highlighted newsgroup
11225 </PRE>
11226 <!--chtml else-->
11227 <PRE>
11228 Navigating the List of Newsgroups General Alpine Commands
11229 --------------------------------- -----------------------
11230 P Move to previous group ? Show this help text
11231 N Move to next group
11232 - Show previous screen of groups
11233 Spc (space bar) Show next screen of groups
11234 W WhereIs (search group names)
11236 Group Selection Commands
11237 -------------------------
11238 E Exit the Selection menu (without selecting a group)
11239 S Select the currently highlighted newsgroup
11240 </PRE>
11241 <!--chtml endif-->
11242 <P>
11243 <End of help on this topic>
11244 </BODY>
11245 </HTML>
11246 ===== h_folder_save =====
11247 <HTML>
11248 <HEAD>
11249 <TITLE>Folder Select for Save Explained</TITLE>
11250 </HEAD>
11251 <BODY>
11252 This screen is designed to allow you to quickly and easily survey your
11253 folders and select one to use for saving the current message.
11254 <P>
11256 <!--chtml if pinemode="function_key"-->
11257 <PRE>
11258 Navigating the List of Folders General Alpine Commands
11259 ------------------------------ -----------------------
11260 F5 Move to previous folder F1 Show this help text
11261 F6 Move to next folder
11262 F7 Show previous screen of folders
11263 F8 Show next screen of folders
11264 F12 WhereIs (search folder names)
11266 Folder Selection Commands
11267 -------------------------
11268 F3 Exit the Folder Select menu (without selecting a folder)
11269 F4 Select the currently highlighted folder
11270 F11 AddNew folder (just like Select, but you type in a new folder name)
11271 </PRE>
11272 <!--chtml else-->
11273 <PRE>
11274 Navigating the List of Folders General Alpine Commands
11275 ------------------------------ -----------------------
11276 P Move to previous folder ? Show this help text
11277 N Move to next folder
11278 - Show previous screen of folders
11279 Spc (space bar) Show next screen of folders
11280 W WhereIs (search folder names)
11282 Folder Selection Commands
11283 -------------------------
11284 E Exit the Folder Select menu (without selecting a folder)
11285 S Select the currently highlighted folder
11286 A AddNew folder (just like Select, but you type in a new folder name)
11287 </PRE>
11288 <!--chtml endif-->
11289 <P>
11290 FOR MORE INFORMATION: See the section on
11291 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11292 <P>
11293 <End of help on this topic>
11294 </BODY>
11295 </HTML>
11296 ===== h_folder_fcc =====
11297 <HTML>
11298 <HEAD>
11299 <TITLE>Folder Select for Fcc Explained</TITLE>
11300 </HEAD>
11301 <BODY>
11302 This screen is designed to allow you to quickly and easily survey your
11303 folders and select one to use as the file carbon copy (fcc) for the
11304 current message.
11305 <P>
11307 <!--chtml if pinemode="function_key"-->
11308 <PRE>
11309 Navigating the List of Folders General Alpine Commands
11310 ------------------------------ -----------------------
11311 F5 Move to previous folder F1 Show this help text
11312 F6 Move to next folder
11313 F7 Show previous screen of folders
11314 F8 Show next screen of folders
11315 F12 WhereIs (search folder names)
11317 Folder Selection Commands
11318 -------------------------
11319 F3 Exit the Folder Select menu (without selecting a folder)
11320 F4 Select the currently highlighted folder
11321 F11 AddNew folder (just like Select, but you type in a new folder name)
11322 </PRE>
11323 <!--chtml else-->
11324 <PRE>
11325 Navigating the List of Folders General Alpine Commands
11326 ------------------------------ -----------------------
11327 P Move to previous folder ? Show this help text
11328 N Move to next folder
11329 - Show previous screen of folders
11330 Spc (space bar) Show next screen of folders
11331 W WhereIs (search folder names)
11333 Folder Selection Commands
11334 -------------------------
11335 E Exit the Folder Select menu (without selecting a folder)
11336 S Select the currently highlighted folder
11337 A AddNew folder (just like Select, but you type in a new folder name)
11338 </PRE>
11339 <!--chtml endif-->
11340 <P>
11341 FOR MORE INFORMATION: See the section on
11342 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11343 <P>
11344 <End of help on this topic>
11345 </BODY>
11346 </HTML>
11347 ===== h_folder_pattern_roles =====
11348 <HTML>
11349 <HEAD>
11350 <TITLE>Folder Select for Current Folder Explained</TITLE>
11351 </HEAD>
11352 <BODY>
11353 This screen is designed to allow you to quickly and easily survey your
11354 folders and select one to use as the specific Current Folder
11355 in a Pattern.
11356 <P>
11358 <!--chtml if pinemode="function_key"-->
11359 <PRE>
11360 Navigating the List of Folders General Alpine Commands
11361 ------------------------------ -----------------------
11362 F5 Move to previous folder F1 Show this help text
11363 F6 Move to next folder
11364 F7 Show previous screen of folders
11365 F8 Show next screen of folders
11366 F12 WhereIs (search folder names)
11368 Folder Selection Commands
11369 -------------------------
11370 F3 Exit the Folder Select menu (without selecting a folder)
11371 F4 Select the currently highlighted folder
11372 F11 AddNew folder (just like Select, but you type in a new folder name)
11373 </PRE>
11374 <!--chtml else-->
11375 <PRE>
11376 Navigating the List of Folders General Alpine Commands
11377 ------------------------------ -----------------------
11378 P Move to previous folder ? Show this help text
11379 N Move to next folder
11380 - Show previous screen of folders
11381 Spc (space bar) Show next screen of folders
11382 W WhereIs (search folder names)
11384 Folder Selection Commands
11385 -------------------------
11386 E Exit the Folder Select menu (without selecting a folder)
11387 S Select the currently highlighted folder
11388 A AddNew folder (just like Select, but you type in a new folder name)
11389 </PRE>
11390 <!--chtml endif-->
11391 <P>
11392 FOR MORE INFORMATION: See the section on
11393 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11394 <P>
11395 <End of help on this topic>
11396 </BODY>
11397 </HTML>
11398 ===== h_folder_stayopen_folders =====
11399 <HTML>
11400 <HEAD>
11401 <TITLE>Folder Select Explained</TITLE>
11402 </HEAD>
11403 <BODY>
11404 This screen is designed to allow you to quickly and easily survey your
11405 folders and select one to use as a Stay-Open folder.
11406 <P>
11408 <!--chtml if pinemode="function_key"-->
11409 <PRE>
11410 Navigating the List of Folders General Alpine Commands
11411 ------------------------------ -----------------------
11412 F5 Move to previous folder F1 Show this help text
11413 F6 Move to next folder
11414 F7 Show previous screen of folders
11415 F8 Show next screen of folders
11416 F12 WhereIs (search folder names)
11418 Folder Selection Commands
11419 -------------------------
11420 F3 Exit the Folder Select menu (without selecting a folder)
11421 F4 Select the currently highlighted folder
11422 F11 AddNew folder (just like Select, but you type in a new folder name)
11423 </PRE>
11424 <!--chtml else-->
11425 <PRE>
11426 Navigating the List of Folders General Alpine Commands
11427 ------------------------------ -----------------------
11428 P Move to previous folder ? Show this help text
11429 N Move to next folder
11430 - Show previous screen of folders
11431 Spc (space bar) Show next screen of folders
11432 W WhereIs (search folder names)
11434 Folder Selection Commands
11435 -------------------------
11436 E Exit the Folder Select menu (without selecting a folder)
11437 S Select the currently highlighted folder
11438 A AddNew folder (just like Select, but you type in a new folder name)
11439 </PRE>
11440 <!--chtml endif-->
11441 <P>
11442 FOR MORE INFORMATION: See the section on
11443 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11444 <P>
11445 <End of help on this topic>
11446 </BODY>
11447 </HTML>
11448 ===== h_folder_action_roles =====
11449 <HTML>
11450 <HEAD>
11451 <TITLE>Folder Select Explained</TITLE>
11452 </HEAD>
11453 <BODY>
11454 This screen is designed to allow you to quickly and easily survey your
11455 folders and select one to use as the folder into which messages
11456 matching this filter will be moved.
11457 <P>
11459 <!--chtml if pinemode="function_key"-->
11460 <PRE>
11461 Navigating the List of Folders General Alpine Commands
11462 ------------------------------ -----------------------
11463 F5 Move to previous folder F1 Show this help text
11464 F6 Move to next folder
11465 F7 Show previous screen of folders
11466 F8 Show next screen of folders
11467 F12 WhereIs (search folder names)
11469 Folder Selection Commands
11470 -------------------------
11471 F3 Exit the Folder Select menu (without selecting a folder)
11472 F4 Select the currently highlighted folder
11473 F11 AddNew folder (just like Select, but you type in a new folder name)
11474 </PRE>
11475 <!--chtml else-->
11476 <PRE>
11477 Navigating the List of Folders General Alpine Commands
11478 ------------------------------ -----------------------
11479 P Move to previous folder ? Show this help text
11480 N Move to next folder
11481 - Show previous screen of folders
11482 Spc (space bar) Show next screen of folders
11483 W WhereIs (search folder names)
11485 Folder Selection Commands
11486 -------------------------
11487 E Exit the Folder Select menu (without selecting a folder)
11488 S Select the currently highlighted folder
11489 A AddNew folder (just like Select, but you type in a new folder name)
11490 </PRE>
11491 <!--chtml endif-->
11492 <P>
11493 FOR MORE INFORMATION: See the section on
11494 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11495 <P>
11496 <End of help on this topic>
11497 </BODY>
11498 </HTML>
11499 ===== h_abook_config =====
11500 <HTML>
11501 <HEAD>
11502 <TITLE>SETUP ADDRESS BOOKS SCREEN</TITLE>
11503 </HEAD>
11504 <BODY>
11505 <H1>SETUP ADDRESS BOOKS SCREEN</H1>
11506 <H2>SETUP ADDRESS BOOKS COMMANDS</H2>
11507 <!--chtml if pinemode="function_key"-->
11508 <PRE>
11509 Available Commands
11510 -------------------------------
11511 F1 Show Help Text
11512 F3 Back to MAIN Alpine menu
11513 F4 Change configuration for address book
11514 F5 Move to previous address book
11515 F6 Move to next address book
11516 F7 Previous page of address books
11517 F8 Next page of address books
11518 F9 Add new address book
11519 F10 Delete existing address book
11520 F11 Shuffle the order of address books
11521 F12 Whereis (search address book titles)
11522 </PRE>
11523 <!--chtml else-->
11524 <PRE>
11525 Navigation General Alpine Commands
11526 ----------------------- -----------------------
11527 P Prev Address Book ? Display this help text
11528 N Next Address Book E Back to MAIN Alpine menu
11529 - Previous page
11530 Spc (space bar) Next page
11531 W WhereIs (search for word in address book titles)
11533 Setup Address Books Commands
11534 ------------------------------------------------
11535 A Add new address book $ Shuffle the order of address books
11536 D Delete existing address book C Change configuration for address book
11537 </PRE>
11538 <!--chtml endif-->
11540 <H2>Description of the Setup Address Books Screen</H2>
11542 This screen lets you add, delete, modify, or change the order of your
11543 address books. The "Add Abook" command brings up a blank form to
11544 fill in. If you are adding a remote address book on an IMAP server
11545 you should fill in the name of the IMAP server. Otherwise, leave
11546 that field blank. (Note that remote IMAP address books are an Alpine
11547 concept and are unlikely to interoperate with other mail clients.)
11548 For a remote address book, fill in the name of the remote folder
11549 in the Folder field. This should be a folder that is used only for
11550 this one purpose, not a general purpose folder you expect to store
11551 messages in.
11552 <P>If you are adding a local address book, fill in the
11553 Folder Name field with a local file name (e.g., .addressbook).
11554 <P>
11555 <B>Please note:</B> Remote address books stored on an IMAP server are
11556 of an entirely different format (namely, a special-purpose
11557 "mail folder") than that of the local addressbook familiar
11558 to Alpine users. Therefore,
11559 you cannot use "add a remote address book" to make an existing
11560 Alpine .addressbook file you may have on a remote IMAP server accessible to
11561 Alpine running on a different host.
11562 <P>
11564 The "Del Abook" command allows you to remove an address book
11565 from your configuration. It will also ask you if you wish to remove
11566 the data for that address book, which would erase all traces of the
11567 address book if you answer Yes.
11568 <P>
11570 The "Change" command is similar to the "Add Abook" command.
11571 The difference is that instead of adding a new address book to your
11572 configuration, you are changing the configuration of an existing entry.
11573 For example, you might want to correct a typing error or change a
11574 nickname. The "Change" command is not a move command. If you
11575 change the folder name or server name the data will not be moved for you.
11576 <P>
11578 The "Shuffle" command is used for two purposes. If you shuffle
11579 an address book toward another address book in the same group then
11580 the order of those two address books will be swapped. If you shuffle
11581 the last Personal address book down towards the Global address book
11582 section, it will become a Global address book. If you shuffle
11583 the first Global address book up it will become a Personal address
11584 book. The main difference between Personal and Global address
11585 books is that Global address books are forced read-only.
11586 <P><UL>
11587 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11588 </UL>
11589 <P>
11590 <End of help on this topic>
11591 </BODY>
11592 </HTML>
11593 ===== h_abook_top =====
11594 <HTML>
11595 <HEAD>
11596 <TITLE>ADDRESS BOOK LIST COMMANDS</TITLE>
11597 </HEAD>
11598 <BODY>
11599 <H1>ADDRESS BOOK LIST COMMANDS</H1>
11600 <!--chtml if pinemode="function_key"-->
11601 <PRE>
11602 Available Commands -- Group 1 Available Commands -- Group 2
11603 ------------------------------- ------------------------------
11604 F1 Show Help Text F1 Show Help Text
11605 F2 See commands in next group F2 See commands in next group
11606 F3 Exit to MAIN MENU F3 Quit Alpine
11607 F4 View/Edit selected address book
11608 F5 Move to previous address book F5 FOLDER LIST screen
11609 F6 Move to next address book F6 Specify a folder to go to
11610 F7 Previous page F7 MESSAGE INDEX screen
11611 F8 Next page F9 Print list of address books
11612 F12 Whereis (search for word)
11613 </PRE>
11614 <!--chtml else-->
11615 <PRE>
11616 Navigation General Alpine Commands
11617 ----------------------- -----------------------
11618 P Previous Entry ? Display this help text
11619 N Next Entry O Show all other available commands
11620 - Previous page < Back to MAIN Alpine menu
11621 Spc (space bar) Next page Q Quit Alpine
11622 W WhereIs (search for word) L FOLDER LIST screen
11623 G Specify a folder to go to
11624 Address Book Commands I MESSAGE INDEX screen
11625 ------------------------------------------------
11626 > View/Edit selected address book
11627 or
11628 > Search on selected directory server
11630 % Print list of address books and directory servers
11631 </PRE>
11632 <!--chtml endif-->
11634 <H2>Description of the Address Book List Screen</H2>
11636 From this screen you may choose which address book you wish to view
11637 or edit. For more information on address books, view one of your
11638 address books (with
11639 <!--chtml if pinemode="function_key"-->
11640 F4
11641 <!--chtml else-->
11642 ">"
11643 <!--chtml endif-->)
11644 and see the Help Text there.<P>
11646 You may also choose a directory server on which to search for entries.
11647 You do that by highlighting the directory server line and using
11648 <!--chtml if pinemode="function_key"-->
11649 F4
11650 <!--chtml else-->
11651 ">"
11652 <!--chtml endif-->.<P>
11654 If you wish to define new address books or directory servers go to the Main
11655 menu and choose Setup. You may then either choose to setup AddressBooks or
11656 Directory (among other things). It's possible that the Directory option
11657 will not be there if the Alpine you are using does not contain LDAP directory
11658 lookup functionality.
11660 <P><UL>
11661 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11662 </UL><P>
11663 <End of help on this topic>
11664 </BODY>
11665 </HTML>
11666 ===== h_abook_opened =====
11667 <HTML>
11668 <HEAD>
11669 <TITLE>THE ALPINE ADDRESS BOOK</TITLE>
11670 </HEAD>
11671 <BODY>
11672 <H1>THE ALPINE ADDRESS BOOK</H1>
11673 <H2>ADDRESS BOOK COMMANDS</H2>
11674 <PRE>
11675 <!--chtml if pinemode="function_key"-->
11676 Available Commands -- Group 1 Available Commands -- Group 2
11677 ------------------------------- ------------------------------
11678 F1 Show Help Text F1 Show Help Text
11679 F2 See commands in next group F2 See commands in next group
11680 F3 Exit this screen F3 Quit Alpine
11681 F4 View/Edit selected entry F4 Go to MAIN MENU screen
11682 F5 Move to previous entry F5 FOLDER LIST screen
11683 F6 Move to next entry F6 Specify a folder to go to
11684 F7 Previous page of address book F7 MESSAGE INDEX screen
11685 F8 Next page of address book F8 Compose to entry using roles
11686 F9 Add new entry to address book F9 Print address book
11687 F10 Delete selected entry F10 TakeAddr to another addrbook
11688 F11 Compose to selected entry F11 Save or Export addrbook selections
11689 F12 Whereis (search address book) F12 Forward entry by mail
11691 Available Commands -- Group 3
11692 ------------------------------
11693 F3 Select F6 Zoom (or unZoom)
11694 F5 Select Current F7 Apply Command to Selection
11695 <!--chtml else-->
11696 Address Book Navigation General Alpine Commands
11697 ----------------------- -----------------------
11698 P Prev Address ? Display this help text
11699 N Next Address O Show all other available commands
11700 - Previous page of address book M Back to MAIN MENU
11701 Spc (space bar) Next page Q Quit Alpine
11702 W WhereIs (search for word C Compose message to selected addr
11703 or name in address book) # Compose to addr using roles
11704 < To List of Address Books if L FOLDER LIST screen
11705 more than one, else to MAIN G Specify a folder to go to
11706 I MESSAGE INDEX screen
11708 Address Book Commands
11709 ----------------------------------------------------
11710 > View/Update selected entry D Delete selected entries
11711 % Print address book S Save or Export address book selections
11712 F Forward entries by mail @ Add new entry to address book
11714 ; Select command Z Toggle Zoom Mode
11715 : Select highlighted entry A Apply command to selected entries
11717 <!--chtml endif-->
11718 </PRE>
11719 Note: The presence or absence of the final four commands above is
11720 controlled by the option
11721 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>.
11722 <P>
11724 <H2>Description of the Address Book Screen</H2>
11726 This screen lets you edit and manage entries in your address book. It
11727 also acts as a short-cut for composing messages to people in the address
11728 book. When, from this screen, you press <!--chtml if pinemode="function_key"-->F11<!--chtml else-->"C"<!--chtml endif--> for ComposeTo, the
11729 message starts "pre-addressed" to whatever address book entry is
11730 currently selected. If you use the <!--chtml if pinemode="function_key"-->F8<!--chtml else-->"#"<!--chtml endif--> for Role, you may first select a
11731 role to use in your composition.
11732 <P>
11733 Alpine's address book helps you keep a list of addresses you send email to so
11734 you do not have to remember addresses that are often complex. Each entry
11735 in the address book has five fields, all of them optional. The three
11736 elements that are usually visible on the ADDRESS BOOK display, are: <DL>
11738 <P><DT>NICKNAME: <DD>A short easy-to-remember label to identify the entry.
11739 This is what you type in as you are addressing the message in the
11740 composer. If there is a matching entry in your address book(s),
11741 Alpine will extract the corresponding FullName and Address fields to
11742 generate the actual address for your message.
11744 <P><DT>FULLNAME: <DD>A longer field where you can put the full name
11745 of the
11746 person or organization. Usually the full names are put in last
11747 name first so they sort nicely in alphabetical order. Whatever
11748 you put as the name here will appear on the message when it is
11749 finally delivered. Examples:<PRE>
11750 Garcia Marquez, Gabriel
11751 Henscheid, Eckhard
11752 Alpine-Info mailing list
11753 Library materials renewal requests
11754 Kim An-guk
11755 "George III, King of Great Britain, 1738-1820"
11756 </PRE>
11757 (In the second-to-last example, no comma is used in the name so that
11758 the family name appears first in the address book and when the entry is
11759 used in the composer.
11760 In the last example, retaining the commas is intended;
11761 double-quotation marks surround the name to
11762 prevent the transposition of its parts when the entry is used in
11763 the composer.)
11765 <P><DT>ADDRESS: <DD>This is the actual email address itself. This must be
11766 a valid Internet address that conforms to the Internet message
11767 header standard, RFC-822. (See also <A HREF="h_address_format">Explanation of Address formats</A>.)</DL>
11769 The two fields that aren't usually visible are:<DL>
11771 <P><DT>FCC: <DD>The name of the folder you would like a copy of any outgoing
11772 message to this address to be saved in. If this field is set, and
11773 this address is the first one in the message's To: header, then
11774 Alpine will use this folder name for the FCC in lieu of the normal
11775 FCC folder name.
11777 <P><DT>COMMENTS: <DD>This field contains arbitrary text for your convenience.
11778 </DL>
11779 <P>
11780 Due to screen width limitations, these last two fields do not show up in
11781 the normal ADDRESS BOOK display. You may select the
11782 "View/Update" command to
11783 view or modify them. You may use the configuration variable
11784 <A HREF="h_config_abook_formats">"<!--#echo var="VAR_addressbook-formats"-->"</A>
11785 to add these fields to your ADDRESS BOOK
11786 display, or to modify the format of the display.
11788 <H2>Sorting the Address book</H2>
11790 By default, address book entries are sorted alphabetically on the full
11791 name with distribution lists sorted to the end. Sorting can be changed by
11792 resetting the address book sort rule in the Alpine SETUP CONFIGURATION screen
11793 --assuming you have "write" permission for the address book file.
11794 <P>
11795 Unlike the sorting of folders (which only changes presentation), sorting an
11796 address book actually changes the file as it is kept on the computer. For
11797 this reason you won't be able to sort a shared or system-wide address
11798 book.
11800 <H2>Adding New Entries</H2>
11802 The easiest way to add new entries to your address book is to use the
11803 "TakeAddr" command when viewing a message.
11804 This command allows you to take addresses from the header and body of the
11805 message and put them into your address book, without having to type
11806 them in.
11807 <P>
11809 To manually add a new entry from within the address book screen, use the AddNew
11810 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->"@"<!--chtml endif-->) command.
11811 Use this command both for adding a simple alias and for adding a
11812 distribution list.
11814 <H2>Distribution Lists</H2>
11816 Address book entries can be simple cases of aliases (a single nickname is linked
11817 to a single email address) or distribution lists (a single nickname
11818 pointing at more than one email address). Each distribution list has a
11819 nickname, a full name and a list of addresses. The addresses may be
11820 actual addresses or they may be other nicknames in your address book.
11821 They may even refer to other distribution lists.
11822 There's really no difference between a simple alias and a distribution list,
11823 other than the number of addresses.
11824 Therefore, you can turn a simple alias with one address into a distribution
11825 list simply by adding more addresses.
11826 To add entries to an existing list or alias
11827 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
11828 a single address from the list if the cursor is placed on the address;
11829 it will delete the entire distribution list if the cursor is on the
11830 nickname/fullname line. View/Update may also be used to delete addresses
11831 from a list.
11832 <P>
11833 Address field entries in distribution lists may take any one of three
11834 forms: a nickname existing in any of the defined address books, a normal
11835 address of the form "jsmith@art.example.com", or a complete
11836 fullname/address combination, e.g. "John Smith
11837 <jsmith@art.example.com>".
11838 <P>
11839 Distribution lists in Alpine address books can only be used by the person or
11840 people who have access to that address book. They are not usually used to
11841 implement discussion groups, but can be used to facilitate small
11842 discussion groups if all the participants have access to the same shared
11843 address book.
11845 <H2>FCC and Comments</H2>
11847 As mentioned above, each entry in the address book also has two other optional
11848 fields, Fcc and Comments. The command to look at or change either of these
11849 is the same View/Update command used for all of the fields (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->">"<!--chtml endif-->). The
11850 Comments field is just for your own use. The Fcc field overrides the
11851 default Fcc if this address is the first one on the To line. The WhereIs
11852 command may be used to search for particular strings in the address book,
11853 including fields that are not visible (like Comment and Fcc by default).
11855 <H2>Aggregate Operations</H2>
11857 If the feature
11858 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
11859 is turned on (the default), then the four commands "Select",
11860 "Select Current", "Zoom", and "Apply"
11861 are available. The two selection commands allow you to mark a set of
11862 address book entries as being selected. If you have more than one address
11863 book, the selections may be in more than one of those address books.
11864 The "Zoom" command will toggle between displaying only the selected
11865 entries and all of the entries. The "Apply" command allows you to
11866 apply one of the regular address book commands to all of the selected
11867 entries. Usually the address book commands apply to only the entry
11868 highlighted by the cursor. The "Apply" command works with the
11869 commands "ComposeTo", "Delete", "Print",
11870 "Save", "Forward", and "Role".
11872 <H2>Exporting and Forwarding Address book entries</H2>
11874 Under the save option, when you use the Export (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->"X"<!--chtml endif-->) command, the currently highlighted
11875 address book entry is placed in a plain text file in your home directory
11876 <!--chtml if pinemode="running"-->
11877 (which, in the present configuration of your system, is
11878 "<!--#echo var="HOME_DIR"-->")
11879 <!--chtml endif-->
11880 or current working directory
11881 <!--chtml if pinemode="running"-->
11882 (which, at least for your current Alpine "session,"
11883 is "<!--#echo var="CURRENT_DIR"-->")
11884 <!--chtml endif-->, depending on the
11885 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
11886 configuration setting. If you have some entries selected and use the
11887 Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Export command, all of the selected addresses will be
11888 placed in the text file.
11889 <P>
11890 When you use the Forward (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->"F"<!--chtml endif-->) command, the currently highlighted
11891 address book entry is placed in a special attachment and you are put into
11892 the composer. You can fill in some comments in the body of the message,
11893 if you'd like, and send it to somebody else who uses Alpine. The recipient
11894 may use the TakeAddr command on that message to insert the address book
11895 entry you sent in their own address book. If you have some entries
11896 selected and use the Apply Forward command all of the selected entries
11897 will be forwarded in a single message. You may
11898 use Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Forward to forward a copy of an entire address book.
11899 The recipient must be using Alpine in order to receive this correctly.
11900 One way for the recipient to handle this might be to create an empty
11901 address book and then "Take" your forwarded address book entries into
11902 that empty address book.
11904 <H2>Multiple and/or Site-Wide Address books</H2>
11906 You may have more than one personal address book. In addition, there may
11907 be one or more global address books. This capability allows you to have
11908 multiple personal address books (some of which may be shared) and it also
11909 allows system administrators to implement site-wide address books that
11910 contain entries for users on multiple machines within the organization.
11911 <P><DL>
11912 <DT>Searching
11913 <DD> If you enter a nickname when composing a message, your
11914 personal address books will be searched through in order, and then the
11915 global address book(s) searched. If more than one address book has an entry
11916 for the nickname, Alpine uses the first one that it finds, so an entry in
11917 your personal address book would override a global address book entry. If
11918 after searching all the address books there is still no match, (Unix) Alpine
11919 then searches the local host password file on the assumption that you have
11920 entered a local user name rather than an address book nickname.
11921 You may change the search order of your address books with the <!--chtml if pinemode="function_key"-->F3<!--chtml else-->$<!--chtml endif--> Shuffle
11922 command, but global address books are always searched after personal
11923 address books.
11925 <P><DT>Tab completion
11926 <DD> If the
11927 <A HREF="h_config_enable_tab_complete"><!--#echo var="FEAT_enable-tab-completion"--></A>
11928 feature is turned on (the default) then the Tab key may be used
11929 in the composer to complete partially typed nicknames in the To
11930 or Cc lines. You type the first few letters of a nickname and then
11931 press the Tab key. It there is only one nickname that matches it will
11932 be filled in by Alpine. If there is more than one the unambiguous part
11933 of the nicknames will be filled in. For example, if your address book or
11934 books contains only the two entries "barley" and "barbecue"
11935 beginning with the letters "ba", then if you type "ba"
11936 followed by a Tab character Alpine will fill in "bar" and stop.
11937 If you then type a second Tab character you will be presented with a list
11938 of matching nicknames to select from. Alternatively, you could type another
11939 "b" resulting in "barb" and then a Tab would fill
11940 in the entire "barbecue" entry.
11942 <P><DT>Defining
11943 <DD> You define multiple personal address books in the
11944 <A HREF="h_abook_config">SETUP AddressBooks</A> screen, which you may reach
11945 from the MAIN MENU.
11946 You may add as many as you like. Global address books are usually
11947 site-wide address books defined by the System administrator, but
11948 you may define global address books of your own just like you define
11949 personal address books.
11951 <P><DT>Creating and updating
11952 <DD> Personal address books are normally created empty
11953 and populated by explicit additions from within Alpine, e.g. via the
11954 TakeAddr command. Unlike personal address books, global address books may
11955 not be modified/updated from within Alpine; that is, they are Read-Only.
11956 Thus, global address books are created, populated and updated outside of
11957 Alpine. They might be hand-edited, generated by a program from another
11958 database, or by copying an existing address book. They might also be
11959 some other user's personal address book, and so be modified normally by
11960 that user but accessed Read-Only by you. See the Alpine Technical
11961 Notes document (included in the Alpine distribution) for more information on
11962 this.
11964 <P><DT>Accessing
11965 <DD>There are two different types of address books in Alpine.
11966 A local address book is stored in a regular file and the normal file
11967 access permissions apply. A remote address book is stored on an IMAP
11968 server in a special folder that contains only messages pertaining to
11969 that address book. The last message in the remote folder contains a
11970 copy of the address book data, and that data is copied to a local cache
11971 file in your home directory. From there it is accessed just like a local
11972 address book. The name of the cache file is kept track of in a special
11973 file called the
11974 <A HREF="h_config_abook_metafile"><!--#echo var="VAR_remote-abook-metafile"--></A>,
11975 the name of which is stored in
11976 your Alpine configuration file the first time you use a remote address book.
11977 Just as local Alpine address books use a format that only Alpine understands,
11978 remote Alpine address books do the same and other mail reading programs
11979 are unlikely to be able to understand them.<P>
11980 While global address books are explicitly intended to be shared, there is
11981 nothing to prevent you from sharing a personal address book with other
11982 Alpine users. This might be useful in the case of a small workgroup.
11983 However, it is recommended that updates to shared personal address books
11984 be done when other Alpine users are not accessing the address book. Alpine
11985 does not do any file-locking to manage concurrent updates to the
11986 addressbook, but it does check to see if the file has been modified before
11987 making any changes. Consequently, inadvertent concurrent updates will
11988 only cause other Alpine users to have to restart their address book
11989 operation, which will cause Alpine to reopen the updated file.
11991 <P><DT>Converting to Remote
11992 <DD>The easiest way to convert an existing local
11993 address book into a remote address book is to create an empty new remote
11994 personal address book by typing "A" to execute the
11995 "Add Pers Abook" command in the SETUP Addressbook screen.
11996 Make sure you add a <EM>personal</EM> address book, not a <EM>global</EM>
11997 address book.
11998 After you have added the empty
11999 remote address book, go into the screen for the address book you wish
12000 to copy and "Select" "All".
12001 This selects every entry in that
12002 address book. Then type the command "Apply Save".
12003 You will be asked for the address book to save to. You may use ^P and ^N
12004 to get to the new empty address book, then hit RETURN and the addresses
12005 will be copied.
12006 At this point you'll probably want to unselect all the entries in the local
12007 address book before proceeding. You do that with
12008 "Select" "unselect All".
12010 </DL>
12011 <UL>
12012 <LI><A HREF="h_address_format">Explanation of Address formats</A>
12013 </UL>
12014 <P><UL>
12015 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
12016 </UL>
12017 <P>
12018 <End of help on this topic>
12019 </BODY>
12020 </HTML>
12021 ===== h_abook_select_addr =====
12022 <HTML>
12023 <HEAD>
12024 <TITLE>Addressbook Selection Explained</TITLE>
12025 </HEAD>
12026 <BODY>
12027 <H1>SELECT ADDRESS</H1>
12028 <!--chtml if pinemode="function_key"-->
12029 <PRE>
12030 Navigating the List of Messages General Alpine Commands
12031 ------------------------------- -----------------------
12032 F5 Move to previous entry F1 Show this help text
12033 F6 Move to next entry
12034 F7 Show previous screen of address book
12035 F8 Show next screen of address book
12036 F12 WhereIs (search through address book)
12038 Address Selection Commands
12039 --------------------------
12040 F3 Exit the Address Select screen (without selecting an address)
12041 F4 Select the currently highlighted entry
12042 </PRE>
12043 <!--chtml else-->
12044 <PRE>
12045 Navigating the List of Messages General Alpine Commands
12046 ------------------------------- -----------------------
12047 P Move to previous entry ? Show this help text
12048 N Move to next entry
12049 - Show previous screen of address book
12050 Spc (space bar) Show next screen of address book
12051 W WhereIs (search through address book)
12053 Address Selection Commands
12054 --------------------------
12055 E Exit the Address Select screen (without selecting an address)
12056 S Select the currently highlighted entry
12057 </PRE>
12058 <!--chtml endif-->
12059 <P>
12061 This screen is designed to let you easily scan your address book(s) in
12062 order to select an entry for the message you are composing. You cannot
12063 edit your address book in any way at this time, for address book
12064 maintenance, select the address book command when not composing a message.
12065 <P>
12067 If you are composing a message and know the nickname of the person/list you
12068 want, you can bypass this screen by simply typing in the nickname on the
12069 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12070 selecting an entry does not cancel your message.
12071 <P>
12073 FOR MORE INFORMATION on addressing see
12074 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12075 <A HREF="h_abook_opened">Address Book Screen's</A>
12076 help text.
12077 <P>
12078 <End of help on this topic>
12079 </BODY>
12080 </HTML>
12081 ===== h_abook_select_top =====
12082 <HTML>
12083 <HEAD>
12084 <TITLE>Addressbook Selection Navigation Explained</TITLE>
12085 </HEAD>
12086 <BODY>
12087 <H1>NAVIGATING WHILE SELECTING ADDRESSES</H1>
12088 <!--chtml if pinemode="function_key"-->
12089 <PRE>
12090 Navigating the List of Address Books General Alpine Commands
12091 ------------------------------------ -----------------------
12092 F4 View the highlighted address book
12093 F5 Move to previous address book F1 Show this help text
12094 F6 Move to next address book
12095 F7 Show previous screen of address books
12096 F8 Show next screen of address books
12097 F12 WhereIs (search through address books)
12099 Address Selection Commands
12100 --------------------------
12101 F3 Exit the Address Select screen (without selecting an address)
12102 F4 Select the currently selected entries (if using ListMode)
12103 F9 Change to ListMode
12104 </PRE>
12105 <!--chtml else-->
12106 <PRE>
12107 Navigating the List of Address Books General Alpine Commands
12108 ------------------------------------ -----------------------
12109 > View the highlighted address book
12110 P Move to previous address book ? Show this help text
12111 N Move to next address book
12112 - Show previous screen of address books
12113 Spc (space bar) Show next screen of address books
12114 W WhereIs (search through address books)
12116 Address Selection Commands
12117 --------------------------
12118 E Exit the Address Select screen (without selecting an address)
12119 S Select the currently selected entries (if using ListMode)
12120 L Change to ListMode
12121 </PRE>
12122 <!--chtml endif-->
12123 <P>
12125 This screen is designed to let you easily scan your address book(s) in
12126 order to select entries for the message you are composing. You cannot
12127 edit your address book in any way at this time. For address book
12128 maintenance, select the address book command when not composing a message.
12129 <P>
12131 If you are composing a message and know the nickname of the person/list you
12132 want, you can bypass this screen by simply typing in the nickname on the
12133 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12134 selecting an entry does not cancel your message.
12135 <P>
12137 The ListMode command will add a column at the left edge of the screen.
12138 You mark the entries that you wish to select with the "X" command.
12139 This allows you to choose more than one entry at a time.
12140 <P>
12142 An alternative method of composing a message to entries in your
12143 address book(s) is to first use the "Select" command from
12144 the address book maintenance screen and then the "Apply"
12145 "ComposeTo" command to start the composer composing to the
12146 selected entries.
12147 <P>
12149 FOR MORE INFORMATION on addressing see
12150 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12151 <A HREF="h_abook_opened">Address Book Screen's</A>
12152 help text.
12153 <P>
12154 <End of help on this topic>
12155 </BODY>
12156 </HTML>
12157 ===== h_abook_select_listmode =====
12158 <HTML>
12159 <HEAD>
12160 <TITLE>Address Listmode Selection from Composer Explained</TITLE>
12161 </HEAD>
12162 <BODY>
12163 <H1>COMPOSER: SELECT ADDRESSES</H1>
12164 <!--chtml if pinemode="function_key"-->
12165 <PRE>
12166 Navigating the List of Messages General Alpine Commands
12167 ------------------------------- -----------------------
12168 F5 Move to previous entry F1 Show this help text
12169 F6 Move to next entry
12170 F7 Show previous screen of address book
12171 F8 Show next screen of address book
12172 F12 WhereIs (search through address book)
12174 Address Selection Commands
12175 --------------------------
12176 F3 Exit the Address Select screen (without selecting an address)
12177 F4 Select the currently highlighted entry
12178 F9 Change to ListMode
12179 </PRE>
12180 <!--chtml else-->
12181 <PRE>
12182 Navigating the List of Messages General Alpine Commands
12183 ------------------------------- -----------------------
12184 P Move to previous entry ? Show this help text
12185 N Move to next entry
12186 - Show previous screen of address book
12187 Spc (space bar) Show next screen of address book
12188 W WhereIs (search through address book)
12190 Address Selection Commands
12191 --------------------------
12192 E Exit the Address Select screen (without selecting an address)
12193 S Select the currently highlighted entry
12194 L Change to ListMode
12195 </PRE>
12196 <!--chtml endif-->
12197 <P>
12199 This screen is designed to let you easily scan your address book(s) in
12200 order to select entries for the message you are composing. You cannot
12201 edit your address book in any way at this time, for address book
12202 maintenance, select the address book command when not composing a message.
12203 <P>
12205 If you are composing a message and know the nickname of the person/list you
12206 want, you can bypass this screen by simply typing in the nickname on the
12207 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12208 selecting an entry does not cancel your message.
12209 <P>
12211 The ListMode command will add a column at the left edge of the screen.
12212 You mark the entries that you wish to select with the "X" command.
12213 This allows you to choose more than one entry at a time.
12214 <P>
12216 An alternative method of composing a message to entries in your
12217 address book(s) is to first use the "Select" command from
12218 the address book maintenance screen and then the "Apply"
12219 "ComposeTo" command to start the composer composing to the
12220 selected entries.
12221 <P>
12223 FOR MORE INFORMATION on addressing see
12224 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12225 <A HREF="h_abook_opened">Address Book Screen's</A>
12226 help text.
12227 <P>
12228 <End of help on this topic>
12229 </BODY>
12230 </HTML>
12231 ===== h_abook_select_checks =====
12232 <HTML>
12233 <HEAD>
12234 <TITLE>Address Selection from Composer Explained</TITLE>
12235 </HEAD>
12236 <BODY>
12237 <H1>COMPOSER: SELECT ADDRESSES</H1>
12238 <!--chtml if pinemode="function_key"-->
12239 <PRE>
12240 Navigating the List of Messages General Alpine Commands
12241 ------------------------------- -----------------------
12242 F5 Move to previous entry F1 Show this help text
12243 F6 Move to next entry
12244 F7 Show previous screen of address book
12245 F8 Show next screen of address book
12246 F12 WhereIs (search through address book)
12248 Address Selection Commands
12249 --------------------------
12250 F3 Exit the Address Select screen (without selecting an address)
12251 F4 Select the currently highlighted entry
12252 F8 Either Sets or Unsets all entries in this address book
12253 F9 Set or Unset the highlighted entry
12254 </PRE>
12255 <!--chtml else-->
12256 <PRE>
12257 Navigating the List of Messages General Alpine Commands
12258 ------------------------------- -----------------------
12259 P Move to previous entry ? Show this help text
12260 N Move to next entry
12261 - Show previous screen of address book
12262 Spc (space bar) Show next screen of address book
12263 W WhereIs (search through address book)
12265 Address Selection Commands
12266 --------------------------
12267 E Exit the Address Select screen (without selecting an address)
12268 S Select the currently highlighted entry
12269 X Set or Unset the highlighted entry
12270 A Either Sets or Unsets all entries in this address book
12271 </PRE>
12272 <!--chtml endif-->
12273 <P>
12275 Mark the entries you wish to select with the "X Set/Unset"
12276 command. Type "S Select" to select all of the entries you
12277 have marked, just as if you had typed them in by hand.
12278 <P>
12280 An alternative method of composing a message to entries in your
12281 address book(s) is to first use the "Select" command from
12282 the address book maintenance screen and then the "Apply"
12283 "ComposeTo" command to start the composer composing to the
12284 selected entries.
12285 <P>
12287 FOR MORE INFORMATION on addressing see
12288 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12289 <A HREF="h_abook_opened">Address Book Screen's</A>
12290 help text.
12291 <P>
12292 <End of help on this topic>
12293 </BODY>
12294 </HTML>
12295 ===== h_abook_select_nicks_take =====
12296 <HTML>
12297 <HEAD>
12298 <TITLE>Take Address Nickname Selection Explained</TITLE>
12299 </HEAD>
12300 <BODY>
12301 <H1>TAKEADDR: SELECT NICKNAME</H1>
12302 <!--chtml if pinemode="function_key"-->
12303 <PRE>
12304 Navigating the List of Messages General Alpine Commands
12305 ------------------------------- -----------------------
12306 F5 Move to previous entry F1 Show this help text
12307 F6 Move to next entry
12308 F7 Show previous screen of address book
12309 F8 Show next screen of address book
12310 F12 WhereIs (search through address book)
12312 Message Selection Commands
12313 --------------------------
12314 F3 Exit the Nickname Select screen (without selecting an address)
12315 F4 Select the currently highlighted entry
12316 </PRE>
12317 <!--chtml else-->
12318 <PRE>
12319 Navigating the List of Messages General Alpine Commands
12320 ------------------------------- -----------------------
12321 P Move to previous entry ? Show this help text
12322 N Move to next entry
12323 - Show previous screen of address book
12324 Spc (space bar) Show next screen of address book
12325 W WhereIs (search through address book)
12327 Message Selection Commands
12328 --------------------------
12329 E Exit the Nickname Select screen (without selecting an address)
12330 S Select the currently highlighted entry
12331 </PRE>
12332 <!--chtml endif-->
12333 <P>
12335 This screen is designed to let you modify or add to an existing
12336 address book entry. You have already selected the name(s) and
12337 address(es) through "Take Address". This screen simply lets
12338 you scan your address books and select the nickname to be
12339 changed/augmented. If you want to add a new entry, then you are in
12340 the wrong place-- Select "Exit" command.
12341 <P>
12343 FOR MORE INFORMATION on addressing see
12344 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12345 <A HREF="h_abook_opened">Address Book Screen's</A>
12346 help text.
12347 <P>
12348 <End of help on this topic>
12349 </BODY>
12350 </HTML>
12351 ===== h_abook_select_nick =====
12352 <HTML>
12353 <HEAD>
12354 <TITLE>Nickname Selection Explained</TITLE>
12355 </HEAD>
12356 <BODY>
12357 <H1>SELECT NICKNAME</H1>
12358 <!--chtml if pinemode="function_key"-->
12359 <PRE>
12360 Navigating the List of Messages General Alpine Commands
12361 ------------------------------- -----------------------
12362 F5 Move to previous entry F1 Show this help text
12363 F6 Move to next entry
12364 F7 Show previous screen of address book
12365 F8 Show next screen of address book
12366 F12 WhereIs (search through address book)
12368 Message Selection Commands
12369 --------------------------
12370 F3 Exit the Nickname Select screen (without selecting an address)
12371 F4 Select the currently highlighted entry
12372 </PRE>
12373 <!--chtml else-->
12374 <PRE>
12375 Navigating the List of Messages General Alpine Commands
12376 ------------------------------- -----------------------
12377 P Move to previous entry ? Show this help text
12378 N Move to next entry
12379 - Show previous screen of address book
12380 Spc (space bar) Show next screen of address book
12381 W WhereIs (search through address book)
12383 Message Selection Commands
12384 --------------------------
12385 E Exit the Nickname Select screen (without selecting an address)
12386 S Select the currently highlighted entry
12387 </PRE>
12388 <!--chtml endif-->
12389 <P>
12391 This screen is designed to let you look at the nicknames in your address
12392 books before choosing a new one.
12393 <P>
12395 FOR MORE INFORMATION on addressing see
12396 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12397 <A HREF="h_abook_opened">Address Book Screen's</A>
12398 help text.
12399 <P>
12400 <End of help on this topic>
12401 </BODY>
12402 </HTML>
12403 ===== h_takeaddr_screen =====
12404 <HTML>
12405 <HEAD>
12406 <TITLE>Take Address Screen Explained</TITLE>
12407 </HEAD>
12408 <BODY>
12409 <H1>TAKE ADDRESS COMMANDS</H1>
12410 <!--chtml if pinemode="function_key"-->
12411 <PRE>
12412 Navigating the List of Addresses Address Selection Commands
12413 -------------------------------- --------------------------
12414 F5 Move to previous entry F3 Exit without taking address
12415 F6 Move to next entry F4 Take current address(es)
12416 F7 Show previous page of address list
12417 F8 Show next page of address list
12418 F2 WhereIs (search list)
12419 --------------
12420 Mode Toggle F9 Set/Unset current address
12421 ----------- F10 Set all
12422 F12 Toggle between List and single mode F11 Unset all
12423 </PRE>
12424 <!--chtml else-->
12425 <PRE>
12426 Navigating the List of Addresses Address Selection Commands
12427 -------------------------------- --------------------------
12428 P Move to previous entry < Exit without taking address
12429 N Move to next entry T Take address
12430 - Show previous page of address list
12431 Spc (space bar) Show next page of address list
12432 W WhereIs (search list) List Mode
12433 ---------
12434 Single Mode X Set/Unset current address
12435 ----------- A Set all addresses
12436 L Switch to list mode U Unset all addresses
12437 S Switch to single mode
12438 </PRE>
12439 <!--chtml endif-->
12441 <H2>Description of the Take Address Screen</H2>
12443 This screen is designed to let you select one or more address/name
12444 combinations from the current message and put them into your address book.
12445 The cursor is initially placed on the line with the message author.
12446 Other lines include the names of people and/or mailing lists who also
12447 received the message. Other people "involved" in the
12448 message (e.g. the person named as Reply-To:) are also listed here.
12449 <P>
12451 The simple case is adding a new, single entry into your address book. To
12452 do this, simply highlight the correct line and press
12453 <!--chtml if pinemode="function_key"-->
12454 F4.
12455 <!--chtml else-->
12456 "T".
12457 <!--chtml endif-->
12458 To create a new list or add to an existing list, switch the screen display
12459 into List Mode by pressing
12460 <!--chtml if pinemode="function_key"-->
12461 F12.
12462 <!--chtml else-->
12463 "L".
12464 <!--chtml endif-->
12465 In List Mode, you select the
12466 group of addresses you wish to manipulate by marking them with an
12467 "X".
12468 The Set/Unset
12469 <!--chtml if pinemode="function_key"-->
12470 (F9)
12471 <!--chtml else-->
12472 ("X")
12473 <!--chtml endif-->
12474 command will turn the "X" on for the
12475 highlighted address if it was off or turn it off if it was previously on.
12476 The SetAll command will select all of the addresses, and the UnSetAll
12477 command will turn off all the selections. Once you've gotten the
12478 selection the way you want it, you may create a new list by pressing
12479 <!--chtml if pinemode="function_key"-->
12480 F4.
12481 <!--chtml else-->
12482 "T".
12483 <!--chtml endif-->
12484 <P>
12486 In both the simple and list cases, after choosing to take the address,
12487 you will be asked for the nickname of the entry. Typing in a new name
12488 creates the new entry/list. Entering an existing nickname will replace
12489 the entry (simple case) or add to the list (list case). Alternatively,
12490 you can press Ctrl-T at the nickname prompt and select an existing
12491 nickname from your address book.
12492 <P>
12494 You will normally start in Single Mode, unless you used the Apply command
12495 to startup the TakeAddr screen, in which case you will start in List Mode.
12496 You may switch between the two modes at any time. If you've already
12497 selected several addresses in List Mode, those will be remembered when you
12498 switch to Single Mode and then back to List Mode. The set of addresses
12499 that are pre-selected when you start in List Mode are the From addresses
12500 of all of the messages you are operating on. You may, of course, easily
12501 erase those selections with the UnSetAll command.
12502 <P>
12504 If you have more than one writable address book, you will be prompted for
12505 the name of the address book you wish to add the new entry to before
12506 anything else. You can use ^N and ^P to choose among the defined address
12507 books, or type in the address book name.
12508 <P>
12510 FOR MORE INFORMATION on addressing see
12511 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12512 <A HREF="h_abook_opened">Address Book Screen's</A>
12513 help text.
12514 <P>
12515 <End of help on this topic>
12516 </BODY>
12517 </HTML>
12518 ===== h_takeexport_screen =====
12519 <HTML>
12520 <HEAD>
12521 <TITLE>Take Export Screen Explained</TITLE>
12522 </HEAD>
12523 <BODY>
12524 <H1>TAKE EXPORT COMMANDS</H1>
12525 <!--chtml if pinemode="function_key"-->
12526 <PRE>
12527 Navigating the List of Addresses Address Selection Commands
12528 -------------------------------- --------------------------
12529 F5 Move to previous entry F3 Exit without taking address
12530 F6 Move to next entry F4 Take current address(es)
12531 F7 Show previous page of address list
12532 F8 Show next page of address list
12533 F2 WhereIs (search list)
12534 --------------
12535 Mode Toggle F9 Set/Unset current address
12536 ----------- F10 Set all
12537 F12 Toggle between List and single mode F11 Unset all
12538 </PRE>
12539 <!--chtml else-->
12540 <PRE>
12541 Navigating the List of Addresses Address Selection Commands
12542 -------------------------------- --------------------------
12543 P Move to previous entry < Exit without taking address
12544 N Move to next entry T Take address
12545 - Show previous page of address list
12546 Spc (space bar) Show next page of address list
12547 W WhereIs (search list) List Mode
12548 ---------
12549 Single Mode X Set/Unset current address
12550 ----------- A Set all addresses
12551 L Switch to list mode U Unset all addresses
12552 S Switch to single mode
12553 </PRE>
12554 <!--chtml endif-->
12556 <H2>Description of the Take Export Screen</H2>
12558 This screen is designed to let you select one or more addresses
12559 from the current message and put them into a file.
12560 Only the user@domain_name part of each address is put into the file.
12561 <P>
12563 To put a single entry into a file simply highlight the correct line and press
12564 <!--chtml if pinemode="function_key"-->
12565 F4.
12566 <!--chtml else-->
12567 "T".
12568 <!--chtml endif-->
12569 To put more than one entry into a file
12570 switch the screen display
12571 into List Mode by pressing
12572 <!--chtml if pinemode="function_key"-->
12573 F12.
12574 <!--chtml else-->
12575 "L".
12576 <!--chtml endif-->
12577 In List Mode, you select the
12578 group of addresses you wish to manipulate by marking them with an
12579 "X".
12580 The Set/Unset
12581 <!--chtml if pinemode="function_key"-->
12582 (F9)
12583 <!--chtml else-->
12584 ("X")
12585 <!--chtml endif-->
12586 command will turn the "X" on for the
12587 highlighted address if it was off or turn it off if it was previously on.
12588 The SetAll command will select all of the addresses, and the UnSetAll
12589 command will turn off all the selections. Once you've gotten the
12590 selection the way you want it, you may put the addresses in a file by typing
12591 <!--chtml if pinemode="function_key"-->
12592 F4.
12593 <!--chtml else-->
12594 "T".
12595 <!--chtml endif-->
12596 <P>
12598 You will be asked for the name of a file to put the addresses in.
12599 If the file already exists, you will be asked whether you want to Overwrite
12600 (replace) the contents of the file or Append to the contents of the file.
12601 <P>
12603 <End of help on this topic>
12604 </BODY>
12605 </HTML>
12606 ============= h_abook_view ========================
12607 <HTML>
12608 <HEAD>
12609 <TITLE>Address Book View Explained</TITLE>
12610 </HEAD>
12611 <BODY>
12612 This function allows you to view the contents of an address book entry. You
12613 can only view one entry at a time.
12614 <P>
12615 <DL>
12616 <DT>Help
12617 <!--chtml if pinemode="function_key"-->
12618 (F1)
12619 <!--chtml else-->
12620 (?)
12621 <!--chtml endif-->
12622 </DT>
12623 <DD>
12624 Display this help text.
12626 <DT>Abook
12627 <!--chtml if pinemode="function_key"-->
12628 (F3)
12629 <!--chtml else-->
12630 (<)
12631 <!--chtml endif-->
12632 </DT>
12633 <DD>
12634 Go back to index of address book entries.
12636 <DT>Update
12637 <!--chtml if pinemode="function_key"-->
12638 (F4)
12639 <!--chtml else-->
12640 (U)
12641 <!--chtml endif-->
12642 </DT>
12643 <DD>
12644 Update (modify) this entry.
12646 <DT>ComposeTo
12647 <!--chtml if pinemode="function_key"-->
12648 (F5)
12649 <!--chtml else-->
12650 (C)
12651 <!--chtml endif-->
12652 </DT>
12653 <DD>Compose a message to the address(es) in this entry.
12655 <DT>Role
12656 <!--chtml if pinemode="function_key"-->
12657 (F6)
12658 <!--chtml else-->
12659 (#)
12660 <!--chtml endif-->
12661 </DT>
12662 <DD>Compose a message to the address(es) in this entry using roles.
12664 <DT>Prev Page
12665 <!--chtml if pinemode="function_key"-->
12666 (F7)
12667 <!--chtml else-->
12668 (-)
12669 <!--chtml endif-->
12670 </DT>
12671 <DD>
12672 Show the previous page of the current entry.
12674 <DT>Next Page
12675 <!--chtml if pinemode="function_key"-->
12676 (F8)
12677 <!--chtml else-->
12678 (Space)
12679 <!--chtml endif-->
12680 </DT>
12681 <DD>
12682 Show the next page of the current entry.
12684 <DT>Print
12685 <!--chtml if pinemode="function_key"-->
12686 (F9)
12687 <!--chtml else-->
12688 (%)
12689 <!--chtml endif-->
12690 </DT>
12691 <DD>Print the current entry. You can select the
12692 printer or the print command via the "Setup" command
12693 on the MAIN MENU.
12695 <DT>WhereIs
12696 <!--chtml if pinemode="function_key"-->
12697 (F10)
12698 <!--chtml else-->
12699 (W)
12700 <!--chtml endif-->
12701 </DT>
12702 <DD>Search the entry for a string of letters. If it is
12703 found, move to it. The string can be one word or a phrase.
12704 If there are multiple occurrences, the cursor moves to the
12705 first occurrence beyond the current cursor position.
12707 <DT>Fwd Email
12708 <!--chtml if pinemode="function_key"-->
12709 (F11)
12710 <!--chtml else-->
12711 (F)
12712 <!--chtml endif-->
12713 </DT>
12714 <DD>Begin composition of a new mail message with the displayed
12715 text already inserted in the message body.
12717 </DL>
12718 <P>
12719 <End of help on this topic>
12720 </BODY>
12721 </HTML>
12722 ============= h_ldap_view ========================
12723 <HTML>
12724 <HEAD>
12725 <TITLE>LDAP Response View Explained</TITLE>
12726 </HEAD>
12727 <BODY>
12728 This function allows you to view the contents of a directory entry. You
12729 can only view one entry at a time.
12730 <P>
12731 <DL>
12732 <DT>Help
12733 <!--chtml if pinemode="function_key"-->
12734 (F1)
12735 <!--chtml else-->
12736 (?)
12737 <!--chtml endif-->
12738 </DT>
12739 <DD>
12740 Display this help text.
12742 <DT>Results Index
12743 <!--chtml if pinemode="function_key"-->
12744 (F3)
12745 <!--chtml else-->
12746 (<)
12747 <!--chtml endif-->
12748 </DT>
12749 <DD>Go back to index of search results.
12751 <DT>ComposeTo
12752 <!--chtml if pinemode="function_key"-->
12753 (F5)
12754 <!--chtml else-->
12755 (C)
12756 <!--chtml endif-->
12757 </DT>
12758 <DD>Compose a message to the address(es) in this entry.
12760 <DT>Role
12761 <!--chtml if pinemode="function_key"-->
12762 (F6)
12763 <!--chtml else-->
12764 (#)
12765 <!--chtml endif-->
12766 </DT>
12767 <DD>Compose a message to the address(es) in this entry using roles.
12769 <DT>Prev Page
12770 <!--chtml if pinemode="function_key"-->
12771 (F7)
12772 <!--chtml else-->
12773 (-)
12774 <!--chtml endif-->
12775 </DT>
12776 <DD>
12777 Show the previous page of the current entry.
12779 <DT>Next Page
12780 <!--chtml if pinemode="function_key"-->
12781 (F8)
12782 <!--chtml else-->
12783 (Space)
12784 <!--chtml endif-->
12785 </DT>
12786 <DD>
12787 Show the next page of the current entry.
12789 <DT>Print
12790 <!--chtml if pinemode="function_key"-->
12791 (F9)
12792 <!--chtml else-->
12793 (%)
12794 <!--chtml endif-->
12795 </DT>
12796 <DD>Print the current entry on paper. You can select the
12797 printer or the print command via the "Setup" command
12798 on the MAIN MENU.
12800 <DT>WhereIs
12801 <!--chtml if pinemode="function_key"-->
12802 (F10)
12803 <!--chtml else-->
12804 (W)
12805 <!--chtml endif-->
12806 </DT>
12807 <DD>Search the entry for a string of letters. If it is
12808 found, move to it. The string can be one word or a phrase.
12809 If there are multiple occurrences, the cursor moves to the
12810 first occurrence beyond the current cursor position.
12812 <DT>Fwd Email
12813 <!--chtml if pinemode="function_key"-->
12814 (F11)
12815 <!--chtml else-->
12816 (F)
12817 <!--chtml endif-->
12818 </DT>
12819 <DD>Begin composition of a new mail message with the displayed
12820 text already inserted in the message body.
12822 <DT>Save
12823 <!--chtml if pinemode="function_key"-->
12824 (F12)
12825 <!--chtml else-->
12826 (S)
12827 <!--chtml endif-->
12828 </DT>
12829 <DD>Save the displayed entry to one of your address books or export
12830 it to a file.
12831 </DL>
12832 <P>
12833 <End of help on this topic>
12834 </BODY>
12835 </HTML>
12836 ===== h_attachment_screen =====
12837 <HTML>
12838 <HEAD>
12839 <TITLE>Attachment Index Screen Explained</TITLE>
12840 </HEAD>
12841 <BODY>
12842 The "ATTACHMENT INDEX" displays a list of the current
12843 message's attachments, and allows various operations on them. The
12844 first attachment is usually the message text, but does not include the
12845 header portion of the message.
12846 <P>
12847 Available commands include:
12848 <P>
12849 <DL>
12851 <DT>Help</DT>
12852 <DD>Show this help text.
12854 <DT>Msg #<I>num</I></DT>
12855 <DD>Leave this screen without displaying or saving any attachments.
12857 <DT>View</DT>
12858 <DD>View the currently selected attachment.
12860 <DT>Prev Attach</DT>
12861 <DD>Move to previous attachment.
12863 <DT>Next Attach</DT>
12864 <DD>Move to next attachment.
12866 <DT>Prev Page</DT>
12867 <DD>Previous page of the listed attachments.
12869 <DT>Next Page</DT>
12870 <DD>Next page of the listed attachments.
12872 <DT>Delete</DT>
12873 <DD>Mark the currently selected attachment for Deletion.
12874 This does not modify the current message by deleting the attachment from
12875 it, but instead the delete flag <EM>only</EM> has an effect when saving
12876 the message to a folder.
12877 Attachments marked for deletion are not copied to the destination folder
12878 along with the rest of the message when it is saved.
12879 It is ok for the destination folder to be the same as the current folder.
12880 In addition, the delete mark <EM>only</EM> applies to this Alpine session.
12882 <DT>Undelete</DT>
12883 <DD>Turn off the Delete flag for the selected attachment.
12885 <DT>Save</DT>
12886 <DD>Save the selected attachment to a file. If the attachment is of
12887 type "RFC822/Message", then the attachment will be saved to
12888 the specified mail folder.
12890 <DT>Export</DT>
12891 <DD>If the attachment is of
12892 type "RFC822/Message", then "Export" is used to
12893 copy the message to a file in the same way this command works on
12894 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
12896 <DT>Pipe</DT>
12897 <DD>Pipe the attachment contents into a UNIX command (if enabled).
12898 A description of the Pipe sub-commands is <A HREF="h_pipe_command">here</A>.
12900 <DT>WhereIs</DT>
12901 <DD>Find a matching string in the attachment list.
12903 <DT>AboutAttch</DT>
12904 <DD>Examine various aspects of the selected attachment.
12906 <DT>Print</DT>
12907 <DD>Print the selected attachment.
12909 <DT>Forward</DT>
12910 <DD>Forward the selected attachment as an attachment.
12911 </DL>
12913 <P>
12915 All attachments can be saved or piped into a UNIX command, but some may
12916 not be readily displayed by either Alpine or an external tool. In such
12917 cases, the reason why the message cannot be displayed is displayed on
12918 Alpine's message line.
12919 <P>
12920 <End of help on this topic>
12921 </BODY>
12922 </HTML>
12923 ============= h_mail_text_att_view ========================
12924 <HTML>
12925 <HEAD>
12926 <TITLE>Attachment View Screen Explained</TITLE>
12927 </HEAD>
12928 <BODY>
12929 This function allows you to view the contents of a text attachment. You
12930 can only view one attachment at a time.
12931 <P>
12932 Available commands include:
12933 <P>
12934 <DL>
12936 <DT>Help</DT>
12937 <DD>Display this help text
12939 <DT>AttchIndex</DT>
12940 <DD>Leave viewer and return to the "ATTACHMENT INDEX" screen
12942 <DT>Prev Page</DT>
12943 <DD>Show the previous page of the current attachment.
12945 <DT>Next Page</DT>
12946 <DD>Show the next page of the current attachment by pressing the space bar.
12948 <DT>Delete</DT>
12949 <DD>Mark the viewed attachment for Deletion. The delete
12950 flag <EM>only</EM> has affect when saving the message to a folder.
12951 Attachments marked for deletion are exluded from the messsage when
12952 it is saved. In addition, the delete mark <EM>only</EM> applies to
12953 this Alpine session.
12955 <DT>Undelete</DT>
12956 <DD>Turn off the Delete flag for the selected attachment.
12958 <DT>Save</DT>
12959 <DD>Copy the current attachment to a file. If you just enter
12960 a filename, the attachment will be saved with that name in
12961 your home directory
12962 <!--chtml if pinemode="running"-->
12963 (which, in the present configuration of your system, is
12964 "<!--#echo var="HOME_DIR"-->")
12965 <!--chtml endif-->
12966 or current working directory
12967 <!--chtml if pinemode="running"-->
12968 (which, at least for your current Alpine "session,"
12969 is "<!--#echo var="CURRENT_DIR"-->")
12970 <!--chtml endif-->, depending on the
12971 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
12972 configuration setting. You may enter the full
12973 path and filename to save it in another directory instead.
12975 <DT>Export</DT>
12976 <DD>If the attachment is of
12977 type "RFC822/Message", then "Export" is used to
12978 copy the message to a file in the same way this command works on
12979 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
12980 (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
12981 defined, they may affect the contents of the exported file.)
12983 <DT>Pipe</DT>
12984 <DD>Pipe the attachment contents into a UNIX command (if enabled)
12986 <DT>WhereIs</DT>
12987 <DD>Search the attachment for a string of letters. If it is
12988 found, move to it. The string can be one word or a phrase.
12989 If there are multiple occurrences, the cursor moves to the
12990 first occurrence beyond the current cursor position.
12992 <DT>Print</DT>
12993 <DD>Print the current attachment on paper. You can select the
12994 printer or the print command via the "Setup" command
12995 on the MAIN MENU.
12997 <DT>Forward</DT>
12998 <DD>Forward the selected attachment as an attachment.
12999 </DL>
13000 <P>
13001 <End of help on this topic>
13002 </BODY>
13003 </HTML>
13004 ============= h_journal ==============
13005 <HTML>
13006 <HEAD>
13007 <TITLE>Recent Message Journal Explained</TITLE>
13008 </HEAD>
13009 <BODY>
13011 The following commands are available on this screen:
13012 <P>
13013 <DL>
13014 <DT>Help</DT>
13015 <DD>Show this help text
13017 <DT>Exit</DT>
13018 <DD>Exit Viewer, and go back to mail processing
13020 <DT>Prev Page</DT>
13021 <DD>Show the previous page text
13023 <DT>Next Page</DT>
13024 <DD>Show the next page of text by pressing the space bar
13026 <DT>Print</DT>
13027 <DD>Print the displayed text on paper. You can select the
13028 printer or the print command via the "Setup" command
13029 on the MAIN MENU.
13031 <DT>Fwd Email</DT>
13032 <DD>Begin composition of a new mail message with the displayed
13033 text already inserted in the message body.
13035 <DT>Save</DT>
13036 <DD>Copy the displayed text to a file. If you just enter
13037 a filename, the text will be saved with that name in
13038 your
13039 home directory
13040 <!--chtml if pinemode="running"-->
13041 (which, in the present configuration of your system, is
13042 "<!--#echo var="HOME_DIR"-->")
13043 <!--chtml endif-->
13044 or current working directory
13045 <!--chtml if pinemode="running"-->
13046 (which, at least for your current Alpine "session,"
13047 is "<!--#echo var="CURRENT_DIR"-->")
13048 <!--chtml endif-->, depending on the
13049 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13050 configuration setting. You may enter the full
13051 path and filename to save it in another directory instead.
13053 <DT>WhereIs</DT>
13054 <DD>Search the text for a string of letters. If it is
13055 found, move to it. The string can be one word or a phrase.
13056 If there are multiple occurrences, the cursor moves to the
13057 first occurrence beyond the current cursor position.
13058 </DL>
13059 <P>
13060 <End of help on this topic>
13061 </BODY>
13062 </HTML>
13063 ============= h_debugjournal ==============
13064 <HTML>
13065 <HEAD>
13066 <TITLE>Debug Journal Explained</TITLE>
13067 </HEAD>
13068 <BODY>
13070 The following commands are available on this screen:
13071 <P>
13072 <DL>
13073 <DT>Help</DT>
13074 <DD>Show this help text
13076 <DT>Exit</DT>
13077 <DD>Exit Viewer, and go back to mail processing
13079 <DT>Timestamps</DT>
13080 <DD>Turn on or off timestamps.
13082 <DT>DebugView</DT>
13083 <DD>Set the level of debugging you want to see. The level may be any number
13084 in the range 0-9. Higher numbers show more debugging detail. Note that the
13085 debugging information has already been captured. This setting just causes the
13086 debugging information that you see to be filtered. If you set this to
13087 the number "5" then you will be shown all of the debugging information
13088 at levels 5 and below.
13089 It's actually a bit more complicated than that. A fixed amount of memory
13090 is used to store the debug information.
13091 Since the amount of memory used is limited the debugging information
13092 has to be trimmed back when it gets too large.
13094 <DT>Prev Page</DT>
13095 <DD>Show the previous page text
13097 <DT>Next Page</DT>
13098 <DD>Show the next page of text by pressing the space bar
13100 <DT>Print</DT>
13101 <DD>Print the displayed text on paper. You can select the
13102 printer or the print command via the "Setup" command
13103 on the MAIN MENU.
13105 <DT>Fwd Email</DT>
13106 <DD>Begin composition of a new mail message with the displayed
13107 text already inserted in the message body.
13109 <DT>Save</DT>
13110 <DD>Copy the displayed text to a file. If you just enter
13111 a filename, the text will be saved with that name in
13112 your
13113 home directory
13114 <!--chtml if pinemode="running"-->
13115 (which, in the present configuration of your system, is
13116 "<!--#echo var="HOME_DIR"-->")
13117 <!--chtml endif-->
13118 or current working directory
13119 <!--chtml if pinemode="running"-->
13120 (which, at least for your current Alpine "session,"
13121 is "<!--#echo var="CURRENT_DIR"-->")
13122 <!--chtml endif-->, depending on the
13123 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13124 configuration setting. You may enter the full
13125 path and filename to save it in another directory instead.
13127 <DT>WhereIs</DT>
13128 <DD>Search the text for a string of letters. If it is
13129 found, move to it. The string can be one word or a phrase.
13130 If there are multiple occurrences, the cursor moves to the
13131 first occurrence beyond the current cursor position.
13132 </DL>
13133 <P>
13134 <End of help on this topic>
13135 </BODY>
13136 </HTML>
13137 ============= h_simple_text_view ==============
13138 <HTML>
13139 <HEAD>
13140 <TITLE>Simple Text View Screen Explained</TITLE>
13141 </HEAD>
13142 <BODY>
13144 The following commands are available on this screen:
13145 <P>
13146 <DL>
13147 <DT>Help</DT>
13148 <DD>Show this help text
13150 <DT>Exit</DT>
13151 <DD>Exit Viewer, and go back to mail processing
13153 <DT>Prev Page</DT>
13154 <DD>Show the previous page text
13156 <DT>Next Page</DT>
13157 <DD>Show the next page of text by pressing the space bar
13159 <DT>Print</DT>
13160 <DD>Print the displayed text on paper. You can select the
13161 printer or the print command via the "Setup" command
13162 on the MAIN MENU.
13164 <DT>Fwd Email</DT>
13165 <DD>Begin composition of a new mail message with the displayed
13166 text already inserted in the message body.
13168 <DT>Save</DT>
13169 <DD>Copy the displayed text to a file. If you just enter
13170 a filename, the attachment will be saved with that name in
13171 your
13172 home directory
13173 <!--chtml if pinemode="running"-->
13174 (which, in the present configuration of your system, is
13175 "<!--#echo var="HOME_DIR"-->")
13176 <!--chtml endif-->
13177 or current working directory
13178 <!--chtml if pinemode="running"-->
13179 (which, at least for your current Alpine "session,"
13180 is "<!--#echo var="CURRENT_DIR"-->")
13181 <!--chtml endif-->, depending on the
13182 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13183 configuration setting. You may enter the full
13184 path and filename to save it in another directory instead.
13186 <DT>WhereIs</DT>
13187 <DD>Search the attachment for a string of letters. If it is
13188 found, move to it. The string can be one word or a phrase.
13189 If there are multiple occurrences, the cursor moves to the
13190 first occurrence beyond the current cursor position.
13191 </DL>
13192 <P>
13193 <End of help on this topic>
13194 </BODY>
13195 </HTML>
13196 ======= h_pine_for_windows ========
13197 <HTML>
13198 <HEAD>
13199 <TITLE>GETTING HELP IN PC-ALPINE</TITLE>
13200 </HEAD>
13201 <BODY>
13202 <H1>Getting Help In PC-Alpine</H1>
13204 <P>
13205 PC-Alpine offers general and specific help text. From the <A
13206 HREF="main_menu_tx">MAIN MENU</A>, you will find an overview in the MAIN
13207 MENU HELP and the <A HREF="h_news">Release Notes</A>. On all screens,
13208 specific help for that screen is available from the toolbar Help menu or
13209 with the
13210 <!--chtml if pinemode="function_key"-->
13211 "F1" key.
13212 <!--chtml else-->
13213 "?" or "Ctrl-G" keys. "Ctrl-G" is used where
13214 typing "?" would be mistaken as entering text.
13215 <!--chtml endif-->
13217 <P>
13218 Although this version of Alpine is for Microsoft Windows, it is not
13219 considered a full "Graphical User Interface" application.
13220 Yet, many of the controls that Windows users are accustomed to seeing,
13221 such as scrollbars and toolbars, are available.
13223 <P>
13224 PC-Alpine offers considerable mouse support. You can view what is
13225 "click-able" by dragging your mouse over any screen; when the
13226 arrow cursor changes into a hand, you found something. Mouse-click
13227 possibilities include navigating between screens and folders and
13228 double-clicking on hyperlinks to open your Web browser.
13229 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
13230 screen. Examples of right-click options include "copy" after
13231 selecting text to copy and "View in New Window" when you click
13232 on a particular message in the Message Index. The menu choices available
13233 to you will vary based upon what screen is open, where on the screen your
13234 cursor is located, and even what action you have already taken.
13236 <P>
13237 <End of help on this topic>
13238 </BODY>
13239 </HTML>
13240 ===== h_composer =====
13241 <HTML>
13242 <HEAD>
13243 <TITLE>COMPOSER COMMANDS</TITLE>
13244 </HEAD>
13245 <BODY>
13246 <H1>COMPOSER COMMANDS</H1>
13248 CURSOR MOTION KEYS |EDITING KEYS<BR>
13249 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13250 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13251 ^P (Up Arrow) Previous line | ^^ Set a <A HREF="h_compose_markcutpaste">mark</A><BR>
13252 ^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>
13253 ^A Beginning of line | delete current line<BR>
13254 ^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>
13255 ^Y Previous page | cut with ^K, or unjustify<BR>
13256 ^V Next page |-------------------------------------<BR>
13257 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13258 ---------------------------------------| <!--chtml if pinemode="function_key"-->F6<!--chtml else-->^W<!--chtml endif--> <A HREF="h_composer_search">Whereis</A> (search for string)<BR>
13259 MESSAGE COMMANDS | GENERAL COMMANDS | <!--chtml if pinemode="function_key"-->F12<!--chtml else-->^T <!--chtml endif--> <A HREF="h_compose_spell">Spell checker</A><BR>
13260 <!--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>
13261 <!--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>
13262 <!--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>
13264 <P>
13265 NOTE:
13266 <OL>
13267 <LI>For help on a particular command, highlight the bold text associated
13268 with it above and hit Return.
13269 <LI> The availability of certain commands
13270 is determined by Alpine configuration files and system capabilities.
13271 At some sites, certain commands may not be available due to security or
13272 support concerns.
13273 <LI>Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
13274 Ctrl-\, ESC.
13275 <LI>For special handling of Ctrl-S and Ctrl-Q see special comments regarding
13276 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
13277 </OL>
13279 <P>
13280 HINT: To move rapidly to the bottom of a message you are composing,
13281 enter ^W^V. To go to the top, ^W^Y. These can be used in conjunction
13282 with the Mark and Cut commands to eliminate large amounts of unwanted
13283 text in a Reply.
13285 <H2>Description of Composer</H2>
13287 Alpine has a built-in editing program that allows you to compose messages
13288 without having to leave Alpine. The editor is designed to be very simple to
13289 use so that you can get started writing email right away.
13291 <P>
13292 Messages are usually just text, about 80 columns wide. Using upper and
13293 lower case is encouraged. On some systems the size limit of the message
13294 is about 100,000 characters, which is about 2,000 lines. You can include
13295 punctuation and special characters found on most keyboards, but you can't
13296 include characters with diacritical marks and certain special symbols.
13298 <P>
13299 Text automatically wraps as you type past the end of a line so you do not
13300 have to hit return. Using the
13301 "<A HREF="h_compose_justify">Justify</A>" command,
13302 you can also reformat text explicitly, perhaps after you have
13303 deleted some text.
13305 <P>
13306 You can include other text files with the
13307 "<A HREF="h_compose_readfile">Read File</A>" command,
13308 which will prompt you for the name of the file to insert at the
13309 current cursor postion.
13311 <P>
13312 <UL>
13313 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13314 </UL>
13315 <P>
13316 <End of help on this topic>
13317 </BODY>
13318 </HTML>
13319 ====== h_composer_browse =====
13320 <HTML>
13321 <HEAD>
13322 <TITLE>BROWSER</TITLE>
13323 </HEAD>
13324 <BODY>
13325 <H1>BROWSER</H1>
13326 This screen lets you browse your files and directories. To go to another
13327 directory (identified by "(dir)"), move the cursor to it and
13328 choose "Select" (the default choice on the menu);
13329 or choose "Goto" and enter the name of the directory.
13330 <!--chtml if pinemode="os_windows"-->
13331 <!--chtml else-->
13332 In Unix Alpine, you may use
13333 "~" to refer to your home directory or "~user" to refer
13334 to another's home directory.
13335 <!--chtml endif--><P>
13336 To select a file, move the cursor to it and
13337 choose "Select" (the default choice on the menu).
13338 <P>
13339 <UL>
13340 <LI>Note <B>if</B> you are currently using the BROWSER for choosing a file for
13341 inclusion in the
13342 message body (that is, you chose "Read File" with the cursor under
13343 the
13344 "----- Message Text -----" line
13345 while composing, then "To Files"): Since the file
13346 selected will become part of the message text, it must be in a format
13347 suitable for that (Alpine does not check!), such as a plain text file.
13348 Files of other formats (for example, graphics, databases, software
13349 programs) should be
13350 <B>attached</B> to the message instead --
13351 by moving the cursor in the COMPOSE MESSAGE screen into the
13352 message header area and pressing
13353 <!--chtml if pinemode="function_key"-->
13354 F6.
13355 <!--chtml else-->
13356 Ctrl-J.
13357 <!--chtml endif-->
13359 <P><LI>
13360 Note <B>if</B> you are currently using the BROWSER for saving a message
13361 attachment, or exporting a message, to a file: You can use the Add command to
13362 provide the name for a new file to save/export to, and then select that name
13363 to use it for the save/export operation. Back at the prompt
13364 "EXPORT: Copy message to file in ..." hit Enter, then choose
13365 either Overwrite or Append (it doesn't make a difference, since the file is
13366 so far empty). Note: If you cancel the
13367 operation at that point, the file created with the Add command will remain
13368 0 bytes in size.
13370 </UL>
13371 <P><UL>
13372 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13373 </UL>
13374 <P>
13375 <End of help on this topic>
13376 </BODY>
13377 </HTML>
13378 ====== h_composer_ins =====
13379 <HTML>
13380 <HEAD>
13381 <TITLE>INSERT TEXT FILE</TITLE>
13382 </HEAD>
13383 <BODY>
13384 <H1>INSERT TEXT FILE</H1>
13386 Use this function to insert a text file. The file name
13387 given can be an absolute file path name for your system
13388 <!--chtml if pinemode="os_windows"-->
13389 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
13390 with a relative pathname, or simply a file name without
13391 drive or directory specification.
13392 <!--chtml else-->
13393 (for example, "/tmp/exported.earlier" on Unix hosts),
13394 a file in your home directory, or a file path relative to your
13395 home directory. In Unix Alpine, you may use "~" to refer to
13396 your home directory or "~user" to refer to another
13397 account's home directory.
13398 <!--chtml endif-->
13399 <P>
13400 No wild card characters may be used.
13401 The file must reside on the system running Alpine.
13402 <P>
13403 If the
13404 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13405 feature is set, names are relative to your current working directory
13406 <!--chtml if pinemode="running"-->
13407 (which, at least for your current Alpine "session,"
13408 is "<!--#echo var="CURRENT_DIR"-->")
13409 <!--chtml endif-->
13410 rather than your home directory
13411 <!--chtml if pinemode="running"-->
13412 (which, in the present configuration of your system, is
13413 "<!--#echo var="HOME_DIR"-->")
13414 <!--chtml endif-->
13415 .
13416 <P><UL>
13417 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13418 </UL>
13419 <P>
13420 <End of help on this topic>
13421 </BODY>
13422 </HTML>
13423 ====== h_composer_ins_m =====
13424 <HTML>
13425 <HEAD>
13426 <TITLE>INSERT MESSAGE</TITLE>
13427 </HEAD>
13428 <BODY>
13429 <H1>INSERT MESSAGE</H1>
13431 Type in the number of a message in the currently open folder to insert it
13432 into your message.
13433 <P><UL>
13434 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13435 </UL>
13436 <P>
13437 <End of help on this topic>
13438 </BODY>
13439 </HTML>
13440 ====== h_composer_search =====
13441 <HTML>
13442 <HEAD>
13443 <TITLE>Explanation of Composer Whereis Command </TITLE>
13444 </HEAD>
13445 <BODY>
13446 <H1>Help For Whereis Command</H1>
13448 Whereis is used to search the message for a word or part of a word.
13449 When searching in the composer, only the message part of your mail is
13450 searched, and the cursor is put on the first occurrence appearing
13451 after the location of the cursor. The search will wrap to the
13452 beginning of the message when it no longer finds matches in the
13453 remainder of the message.
13455 To search for the same string a second time, press
13456 <!--chtml if pinemode="function_key"-->
13457 "F6"
13458 <!--chtml else-->
13459 "^W"
13460 <!--chtml endif-->
13461 to begin search and then just press RETURN to accept the previous
13462 search string shown in square brackets rather than entering a new
13463 search string.<P>
13465 The "Search" prompt has several sub-command available:
13467 <DL>
13468 <DT>Get Help</DT>
13469 <DD> Takes you to this help page.
13471 <DT>Cancel</DT>
13472 <DD> Cancels the prompt. No search takes place.
13474 <DT>First Line</DT>
13475 <DD> Takes you back to the composer with the cursor on the first character
13476 of the first line of text.
13478 <DT>Last Line</DT>
13479 <DD> Takes you back to the composer with the cursor on the last character
13480 of the last line of text.
13482 <DT>Replace (Optional)</DT>
13483 <DD> This sub-command is enabled by the
13484 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13485 feature (which is on by default); see its help screen for details on how replacing works.
13487 </DL>
13489 <End of help on this topic>
13490 </BODY>
13491 </HTML>
13492 ====== h_sigedit_search =====
13493 <HTML>
13494 <HEAD>
13495 <TITLE>Explanation of Whereis Command </TITLE>
13496 </HEAD>
13497 <BODY>
13498 <H1>Help For Whereis Command</H1>
13500 Whereis is used to search for a word or part of a word.
13501 When searching the cursor is put on the first occurrence appearing
13502 after the location of the cursor. The search will wrap to the
13503 beginning of the signature when it no longer finds matches in the
13504 remainder of the signature.
13506 To search for the same string a second time, press
13507 <!--chtml if pinemode="function_key"-->
13508 "F6"
13509 <!--chtml else-->
13510 "^W"
13511 <!--chtml endif-->
13512 to begin search and then just press RETURN to accept the previous
13513 search string shown in square brackets rather than entering a new
13514 search string.<P>
13516 The "Search" prompt has several sub-command available:
13518 <DL>
13519 <DT>Get Help</DT>
13520 <DD> Takes you to this help page.
13522 <DT>Cancel</DT>
13523 <DD> Cancels the prompt. No search takes place.
13525 <DT>First Line</DT>
13526 <DD> Takes you back to the composer with the cursor on the first character
13527 of the first line of text.
13529 <DT>Last Line</DT>
13530 <DD> Takes you back to the composer with the cursor on the last character
13531 of the last line of text.
13533 <DT>Replace (Optional)</DT>
13534 <DD> This sub-command is enabled by the
13535 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13536 feature (which is on by default); see its help screen for details on how replacing works.
13538 </DL>
13540 <End of help on this topic>
13541 </BODY>
13542 </HTML>
13543 ======= h_composer_to ====
13544 <HTML>
13545 <HEAD>
13546 <TITLE>THE MESSAGE COMPOSER'S TO FIELD</TITLE>
13547 </HEAD>
13548 <BODY>
13549 <H1>THE MESSAGE COMPOSER'S TO FIELD</H1>
13551 <H2>The "To:" field</H2>
13552 The address you enter here must be a valid email address that is reachable
13553 from your site.
13555 <H2>Email Address Format</H2>
13556 You may enter a full name and email address,
13557 <!--chtml if pinemode="os_windows"-->
13558 <!--chtml else-->
13559 a local (meaning, on the same
13560 host as the one you are running Alpine on) username that Alpine will
13561 complete for you,
13562 <!--chtml endif-->
13563 the nickname of someone in a
13564 <A HREF="h_abook_opened">Alpine Address Book</A>, or a local
13565 mail alias defined by your system administrator. When you move the cursor
13566 out of this field, the nicknames will be expanded to the addresses in your
13567 address book, and the local usernames will be expanded to include the
13568 persons' actual names. You may enter as many addresses as you wish, but they
13569 must be separated by commas. You can move around this and other header fields
13570 with the arrow keys and use many of the usual composer editing keys.
13571 <P>
13572 <UL>
13573 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13574 </UL>
13576 <P>
13577 <H2>MESSAGE HEADER COMMANDS</H2>
13578 <!--chtml if pinemode="function_key"-->
13579 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13580 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13581 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13582 ^P (Up Arrow) Previous line |<BR>
13583 ^N (Down Arrow) Next line | F9 Cut marked text or<BR>
13584 ^A Beginning of line | delete current line<BR>
13585 ^E End of line | F10 Undelete line(s)<BR>
13586 F7 Previous page | ^W <A HREF="h_composer_search">Whereis</A> (search text)<BR>
13587 F8 Next page |-------------------------------------<BR>
13588 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13589 ----------------------------------------|<BR>
13590 MESSAGE COMMANDS | GENERAL COMMANDS | F12 To Addressbook/Browser<BR>
13591 F3 <A HREF="h_compose_cancel">Cancel</A> | F1 Get help | F4 Attach File<BR>
13592 F11 <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13593 F2 <A HREF="h_compose_send">Send</A> | | F5 <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13594 <!--chtml else-->
13595 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13596 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13597 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13598 ^P (Up Arrow) Previous line | <BR>
13599 ^N (Down Arrow) Next line | ^K Cut marked text or<BR>
13600 ^A Beginning of line | delete current line<BR>
13601 ^E End of line | ^U Undelete line(s)<BR>
13602 ^Y Previous page |<BR>
13603 ^V Next page |-------------------------------------<BR>
13604 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13605 ----------------------------------------| ^R <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13606 MESSAGE COMMANDS | GENERAL COMMANDS | ^T To Addressbook/Browser<BR>
13607 ^C <A HREF="h_compose_cancel">Cancel</A> | ^G Get help | ^J Attach File<BR>
13608 ^O <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13609 ^X <A HREF="h_compose_send">Send</A> | | TAB <A HREF="h_compose_addrcomplete">Address Completion</A><BR>
13610 <!--chtml endif-->
13612 <P>
13613 NOTE:
13614 <OL>
13615 <LI>For help on a particular command, highlight the bold text associated
13616 with it above and hit Return.
13617 <LI> The availability of certain commands
13618 is determined by Alpine configuration files and system capabilities.
13619 At some sites, certain commands may not be available due to security or
13620 support concerns.
13621 </OL>
13623 <P>
13624 <UL>
13625 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13626 </UL><P>
13627 <End of help on this topic>
13628 </BODY>
13629 </HTML>
13630 ======= h_composer_cc ====
13631 <HTML>
13632 <HEAD>
13633 <TITLE>THE MESSAGE COMPOSER'S CC FIELD</TITLE>
13634 </HEAD>
13635 <BODY>
13636 <H1>THE MESSAGE COMPOSER'S CC FIELD</H1>
13637 The Cc: field is just like the To: field, except it is used for addressees
13638 that you wish to send a "carbon" copy to. That is, the message is
13639 not directly meant directly "for" these recipients, but you wanted
13640 them to see the message. The only difference the recipients see is that their
13641 name is in the Cc: field, rather than the To: field.
13642 <P>
13643 For help with Cc: field editing
13644 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13645 <P>
13646 <UL>
13647 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13648 </UL>
13649 <P>
13650 <UL>
13651 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13652 </UL><P>
13653 <End of help on this topic>
13654 </BODY>
13655 </HTML>
13656 ======= h_composer_bcc ====
13657 <HTML>
13658 <HEAD>
13659 <TITLE>THE MESSAGE COMPOSER'S BCC FIELD</TITLE>
13660 </HEAD>
13661 <BODY>
13662 <H1>THE MESSAGE COMPOSER'S BCC FIELD</H1>
13663 The "Bcc:" (Blind carbon copy) header is used when you wish to send
13664 a copy of the message to one or more people whose addresses you do not
13665 wish disclosed, either to reduce clutter or for confidentiality.
13666 <P>
13667 The format of the Bcc: field is just the same as the To: and Cc: fields in
13668 the way the addresses are entered. The recipients listed here will
13669 receive a copy of the message, but --assuming your site's mail transport
13670 software is properly configured-- their addresses will not show up in the
13671 headers of the message, as delivered to all of the recipients. The To:
13672 and Cc: recipients will not know a copy was sent to the Bcc: recipients.
13673 <P>
13674 Note: if there is no To: or Cc: or Lcc: address in the message, Alpine
13675 will automatically generate and place in the To: field a pseudo-address of
13676 "undisclosed-recipients: ;"
13677 or whatever string has been specified in the
13678 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
13679 variable.
13680 <P>
13681 The reason for this is to avoid embarrassment caused by some Internet
13682 mail transfer software that interprets a "missing" To: header as
13683 an error and replaces it with an Apparently-to: header that may contain
13684 the addresses you entered on the Bcc: line. In addition, it may be
13685 less disconcerting to Bcc: recipients to see <B>something</B> in the To: field.
13686 <P>
13687 You can manipulate what text ends up on the (originally) empty To:
13688 field. Just remember to put a colon and semicolon at the end of the
13689 field, which is a special notation denoting that it is not a real address.
13690 <P>
13691 For information on message header editing
13692 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13693 <P>
13694 <UL>
13695 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13696 </UL>
13697 <P>
13698 <UL>
13699 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13700 </UL><P>
13701 <End of help on this topic>
13702 </BODY>
13703 </HTML>
13704 ======= h_composer_lcc ====
13705 <HTML>
13706 <HEAD>
13707 <TITLE>THE MESSAGE COMPOSER'S LCC FIELD</TITLE>
13708 </HEAD>
13709 <BODY>
13710 <H1>THE MESSAGE COMPOSER'S LCC FIELD</H1>
13711 The "Lcc:" (List carbon copy) header is intended to be used when
13712 you wish to send a message to a list of people but avoid having all
13713 of their addresses visible, in order to reduce clutter when the
13714 message is received.
13715 <P>
13716 It is similar to the
13717 <A HREF="h_composer_bcc">"Bcc" (Blind carbon copy) header</A>
13718 in that individual
13719 addressees are hidden, but Lcc is designed to work specifically with
13720 distribution lists you have created in your
13721 <A HREF="h_abook_opened">Alpine Address Book</A>. Placing
13722 the nickname of the list on the Lcc line will result in the full name of
13723 your Alpine Address Book list being placed on the To: line of the message,
13724 using a special notation that distinguishes it from a real address. You
13725 must leave the To: line blank for your list name to appear there.
13726 <P>
13727 For example, if you have this list entered in your Address Book:<PRE>
13729 largo Key Largo List DISTRIBUTION LIST:
13730 bogie@mgm.com
13731 lauren@mgm.com
13732 walter@mgm.com</PRE>
13735 and you enter "largo" on the Lcc: line while composing a message,
13736 the result is:<PRE>
13738 To : Key Largo List: ;
13739 Cc :
13740 Bcc :
13741 Fcc : sent-mail
13742 Lcc : Key Largo List <bogie@mgm.com>,
13743 lauren@mgm.com,
13744 walter@mgm.com
13745 Subject :</PRE>
13747 Each recipient listed on the Lcc: line receives a copy of the message
13748 without their address being visible (as though they were listed on the
13749 Bcc: line). The colon-semicolon notation used to put the full-name of the
13750 list on the To: line is a special address format that doesn't specify any
13751 actual addressees, but does give some information to the recipients of the
13752 message.
13753 <P>
13754 Note: if after entering an LCC, you delete the list name that is placed
13755 on the To: line, then recipients will see <PRE>
13756 To: undisclosed-recipients: ;</PRE>
13758 (or whatever string is defined in the
13759 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
13760 variable) just as in the BCC case.
13761 <P>
13762 For help with Lcc: field editing
13763 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13764 <P>
13765 <UL>
13766 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13767 </UL>
13768 <P>
13769 <UL>
13770 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13771 </UL><P>
13772 <End of help on this topic>
13773 </BODY>
13774 </HTML>
13775 ======= h_composer_from =======
13776 <HTML>
13777 <HEAD>
13778 <TITLE>THE MESSAGE COMPOSER'S FROM FIELD</TITLE>
13779 </HEAD>
13780 <BODY>
13781 <H1>THE MESSAGE COMPOSER'S FROM FIELD</H1>
13783 This header carries your return address. It is the address toward which
13784 replies (and often, future unrelated correspondence) will be directed,
13785 unless you have <A HREF="h_config_custom_hdrs">defined an optional
13786 "Reply-To:" header</A> in the SETUP CONFIGURATION screen. Make
13787 sure this address is correct.
13788 <P>
13789 For help with message header editing
13790 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13791 <P>
13792 <UL>
13793 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13794 </UL>
13795 <P>
13796 <UL>
13797 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13798 </UL><P>
13799 <End of help on this topic>
13800 </BODY>
13801 </HTML>
13802 ======= h_composer_reply_to =======
13803 <HTML>
13804 <HEAD>
13805 <TITLE>THE MESSAGE COMPOSER'S REPLY-TO FIELD</TITLE>
13806 </HEAD>
13807 <BODY>
13808 <H1>THE MESSAGE COMPOSER'S REPLY-TO FIELD</H1>
13810 Most people should not need this header. The Reply-To: header is used in
13811 cases where you would like replies to your messages to be directed to an
13812 address other than your normal "From:" address. This is atypical,
13813 but can happen when you use multiple machines and do not have the same account
13814 name on each one, or when you wish to direct certain replies to accounts
13815 or folders designated for specific classes of correspondence.
13816 <P>
13817 For help with message header editing
13818 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13819 <P>
13820 <UL>
13821 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13822 </UL>
13824 <P>
13825 <UL>
13826 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13827 </UL><P>
13828 <End of help on this topic>
13829 </BODY>
13830 </HTML>
13831 ======= h_composer_custom_addr ====
13832 <HTML>
13833 <HEAD>
13834 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
13835 </HEAD>
13836 <BODY>
13837 <H1>CUSTOMIZED HEADER FIELD</H1>
13838 This is a customized header, i.e. not one that is part of Alpine's normal
13839 set of Compose headers.
13840 <P>
13841 For help with message header editing
13842 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13843 <P>
13844 <UL>
13845 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13846 </UL>
13847 <P>
13848 <UL>
13849 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13850 </UL><P>
13851 <End of help on this topic>
13852 </BODY>
13853 </HTML>
13854 ======= h_composer_custom_free ====
13855 <HTML>
13856 <HEAD>
13857 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
13858 </HEAD>
13859 <BODY>
13860 <H1>CUSTOMIZED HEADER FIELD</H1>
13861 This is a customized header, i.e. not one that is part of Alpine's normal
13862 set of Compose headers.
13863 <P>
13864 This field consists of arbitrary text.
13865 <P>
13866 For help with message header editing
13867 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13868 <P>
13869 <UL>
13870 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13871 </UL><P>
13872 <End of help on this topic>
13873 </BODY>
13874 </HTML>
13875 ====== h_composer_news =====
13876 <HTML>
13877 <HEAD>
13878 <TITLE>THE MESSAGE COMPOSER'S NEWSGRPS LINE</TITLE>
13879 </HEAD>
13880 <BODY>
13881 <h1>THE MESSAGE COMPOSER'S NEWSGRPS LINE</h1>
13882 Use the newsgroups line to specify any and all USENET newsgroups to which
13883 your message should be posted. When composing a message from scratch, this
13884 line may be hidden. If so, just press the rich headers command
13885 (<!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif-->)
13886 to make it visible.
13887 <P>
13888 <EM>Be aware</EM> that when you post to a newsgroup thousands of
13889 people will be reading your message. Also, you or your system manager
13890 must have defined an "<!--#echo var="VAR_nntp-server"-->" in your Alpine configuration
13891 in order for you to be able to post.
13892 <P>
13893 For help with message header editing
13894 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13895 <P><UL>
13896 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13897 </UL>
13898 <P>
13899 <End of help on this topic>
13900 </BODY>
13901 </HTML>
13902 ======= h_composer_fcc ====
13903 <HTML>
13904 <HEADER>
13905 <TITLE>THE MESSAGE COMPOSER'S FCC FIELD</TITLE>
13906 </HEADER>
13907 <BODY>
13908 <H1>THE MESSAGE COMPOSER'S FCC FIELD</H1>
13909 The FCC (File Carbon Copy) specifies the folder used to keep a copy of
13910 each outgoing message. The default value can be configured with the
13911 "<!--#echo var="VAR_default-fcc"-->" and "<!--#echo var="VAR_fcc-name-rule"-->" options. You can change or remove
13912 the file carbon copy on any message you send by editing the FCC header.<p>
13914 You may type ^T to get a list of all your folders and select one to use as
13915 the FCC for this message.<P>
13917 For help with message header editing
13918 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13919 <P>
13920 <UL>
13921 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13922 </UL><P>
13923 <End of help on this topic>
13924 </BODY>
13925 </HTML>
13926 ======= h_composer_subject ====
13927 <HTML>
13928 <HEADER>
13929 <TITLE>THE MESSAGE COMPOSER'S SUBJECT FIELD</TITLE>
13930 </HEADER>
13931 <BODY>
13932 <H1>THE MESSAGE COMPOSER'S SUBJECT FIELD</H1>
13934 The subject header provides a place to enter a few words that summarize
13935 the topic of the message you are sending. You may leave this line blank,
13936 but it is considered a courtesy to use a meaningful subject.<p>
13938 For help with message header editing
13939 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13940 <P>
13941 <UL>
13942 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13943 </UL><P>
13944 <End of help on this topic>
13945 </BODY>
13946 </HTML>
13947 ======= h_composer_attachment ====
13948 <HTML>
13949 <HEAD>
13950 <TITLE>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</TITLE>
13951 </HEAD>
13952 <BODY>
13953 <H1>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</H1>
13955 The "Attchmnt:" field is where you specify what file or
13956 files you'd like attached to
13957 the message you are composing. Those files must reside on the machine
13958 running Alpine. If your file is on a PC or Mac and you run Alpine with an
13959 account on a Unix machine, you'll have to transfer it before attaching it.
13960 Contact local computer support people for assistance with transferring.
13962 <P>
13963 The file name
13964 given can be an absolute file path name for your system
13965 <!--chtml if pinemode="os_windows"-->
13966 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
13967 with a relative pathname, or simply a file name without
13968 drive or directory specification.
13969 <!--chtml else-->
13970 (for example, "/tmp/exported.earlier" on Unix hosts),
13971 a file in your home directory, or a file path relative to your
13972 home directory. In Unix Alpine, you may use "~" to refer to
13973 your home directory or "~user" to refer to another
13974 account's home directory.
13975 <!--chtml endif--><P>
13976 No wild card characters may be used.
13977 <P>If the
13978 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13979 feature is set, names are relative to your current working directory
13980 <!--chtml if pinemode="running"-->
13981 (which, at least for your current Alpine "session,"
13982 is "<!--#echo var="CURRENT_DIR"-->")
13983 <!--chtml endif-->
13984 rather than your home directory
13985 <!--chtml if pinemode="running"-->
13986 (which, in the present configuration of your system, is
13987 "<!--#echo var="HOME_DIR"-->")
13988 <!--chtml endif-->
13989 .
13990 <P>
13991 Alpine uses MIME encoding for attachments, so binaries and files of any
13992 length can safely be delivered to any MIME-capable mail reading program.
13993 If you send an attachment to someone who does not have a MIME-capable mail
13994 reading program yet, then the main message text will be readable, but
13995 attachments (even attachments that are just plain text) are not.
13996 <P>
13998 Typing the filename on the Attchmnt: line achieves the same
13999 result as using the
14000 <!--chtml if pinemode="function_key"-->
14001 F6
14002 <!--chtml else-->
14003 Ctrl-J
14004 <!--chtml endif--> command.
14005 <P>
14007 If you Forward a message with attachments, you may delete them from your
14008 Forwarded message by editing the Attchmnt header line.
14009 <P>
14011 For help with message header editing
14012 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14013 <P>
14014 <UL>
14015 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14016 </UL><P>
14017 <End of help on this topic>
14018 </BODY>
14019 </HTML>
14020 ======= h_composer_ctrl_j ====
14021 <HTML>
14022 <HEAD>
14023 <TITLE>COMPOSER ATTACH</TITLE>
14024 </HEAD>
14025 <BODY>
14026 After the
14027 <!--chtml if pinemode="function_key"-->
14028 F6
14029 <!--chtml else-->
14030 Ctrl-J
14031 <!--chtml endif--> command:
14032 At the "File to attach:" prompt, enter the name of the
14033 existing file to attach to your message.
14034 When the feature
14035 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
14036 is set
14037 you need only enter the beginning of the filename (enough of it to uniquely
14038 identify the file) and press TAB to complete it.
14040 Or, press ^T to use the BROWSER screen for
14041 selecting the file. <P>
14042 For more information on attaching files, see the help screen for the
14043 composer's
14044 <A HREF="h_composer_attachment">Attchmnt: field</A>, which is normally hidden,
14045 but can be revealed using the
14046 <!--chtml if pinemode="function_key"-->
14047 F5
14048 <!--chtml else-->
14049 Ctrl-R
14050 <!--chtml endif-->
14051 command with the cursor positioned above the
14052 "----- Message Text -----" line in the COMPOSE MESSAGE screen.
14053 <P>
14054 <End of help on this topic>
14055 </BODY>
14056 </HTML>
14057 ======= h_edit_nav_cmds =========
14058 <HTML>
14059 <HEAD>
14060 <TITLE>Composer Editing Commands Explained</TITLE>
14061 </HEAD>
14062 <BODY>
14063 <H1>EDITING and NAVIGATION COMMANDS</H1>
14064 <!--chtml if pinemode="function_key"-->
14065 <PRE>
14066 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
14067 ^B (Left Arrow) Back character | ^D Delete current character
14068 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14069 ^P (Up Arrow) Previous line |
14070 ^N (Down Arrow) Next line | F9 Cut marked text or
14071 ^A Beginning of line | delete current line
14072 ^E End of line | F10 Undelete line(s)
14073 F7 Previous page |
14074 F8 Next page |-------------------------------------
14075 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
14076 ----------------------------------------|
14077 EXIT COMMANDS | GENERAL COMMANDS | F12 To Addressbook
14078 F3 Cancel | F1 Get help | F12 RichView (expand lists)
14079 F2 eXit/save | ^Z Suspend | ^L Redraw Screen
14080 </PRE>
14081 <!--chtml else-->
14082 <PRE>
14083 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
14084 ^B (Left Arrow) Back character | ^D Delete current character
14085 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14086 ^P (Up Arrow) Previous line |
14087 ^N (Down Arrow) Next line | ^K Cut marked text or
14088 ^A Beginning of line | delete current line
14089 ^E End of line | ^U Undelete line(s)
14090 ^Y Previous page |
14091 ^V Next page |-------------------------------------
14092 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
14093 ----------------------------------------|
14094 EXIT COMMANDS | GENERAL COMMANDS | ^T To Addressbook
14095 ^C Cancel | ^G Get help | ^R RichView (expand lists)
14096 ^X eXit/save | ^Z Suspend | ^L Redraw Screen
14097 </PRE>
14098 <!--chtml endif-->
14099 <End of help on this topic>
14100 </BODY>
14101 </HTML>
14102 ===== h_composer_sigedit =====
14103 <HTML>
14104 <HEAD>
14105 <TITLE>Signature Editor Commands Explained</TITLE>
14106 </HEAD>
14107 <BODY>
14108 <H1>SIGNATURE EDITOR COMMANDS</H1>
14109 <!--chtml if pinemode="function_key"-->
14110 <PRE>
14111 CURSOR MOTION KEYS |EDITING KEYS
14112 ^B (Left Arrow) Back character | ^D Delete current character
14113 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14114 ^P (Up Arrow) Previous line | ^^ Set a mark
14115 ^N (Down Arrow) Next line | F9 Cut marked text or
14116 ^A Beginning of line | delete current line
14117 ^E End of line | F10 Paste text, undelete lines
14118 F7 Previous page | cut with ^K, or unjustify
14119 F8 Next page |-------------------------------------
14120 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14121 ---------------------------------------| F6 Whereis (search for string)
14122 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
14123 F3 Cancel | F1 Get help | F4 Justify paragraph
14124 | ^Z Suspend | ^L Redraw Screen
14125 F2 Send | F6 Alt. editor | F5 Read in a file
14126 </PRE>
14127 <!--chtml else-->
14128 <PRE>
14129 CURSOR MOTION KEYS |EDITING KEYS
14130 ^B (Left Arrow) Back character | ^D Delete current character
14131 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14132 ^P (Up Arrow) Previous line | ^^ Set a mark
14133 ^N (Down Arrow) Next line | ^K Cut marked text or
14134 ^A Beginning of line | delete current line
14135 ^E End of line | ^U Paste text, undelete lines
14136 ^Y Previous page | cut with ^K, or unjustify
14137 ^V Next page |-------------------------------------
14138 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14139 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
14140 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
14141 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
14142 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
14143 ^X Send | ^_ Alt. editor | ^R Read in a file
14144 </PRE>
14145 <!--chtml endif-->
14147 NOTE: The presence or absence of the following commands is determined
14148 by "Feature-List" options in your Alpine configuration. Also,
14149 some of these commands may be administratively disabled by your system
14150 manager; if they don't work, please check with your local help desk
14151 before reporting a bug.
14152 <P>
14153 <UL>
14154 <LI>Suspend (suspends Alpine and gives a system prompt)
14155 <LI>Alternate editor (allows you to compose with your own editor)
14156 </UL>
14157 <P>
14159 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
14160 Ctrl-\, ESC
14161 <P>
14163 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
14164 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
14165 <P>
14166 <End of help on this topic>
14167 </BODY>
14168 </HTML>
14169 ===== h_composer_commentedit =====
14170 <HTML>
14171 <HEAD>
14172 <TITLE>Comment Editor Commands Explained</TITLE>
14173 </HEAD>
14174 <BODY>
14175 <H1>COMMENT EDITOR COMMANDS</H1>
14176 <!--chtml if pinemode="function_key"-->
14177 <PRE>
14178 CURSOR MOTION KEYS |EDITING KEYS
14179 ^B (Left Arrow) Back character | ^D Delete current character
14180 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14181 ^P (Up Arrow) Previous line | ^^ Set a mark
14182 ^N (Down Arrow) Next line | F9 Cut marked text or
14183 ^A Beginning of line | delete current line
14184 ^E End of line | F10 Paste text, undelete lines
14185 F7 Previous page | cut with ^K, or unjustify
14186 F8 Next page |-------------------------------------
14187 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14188 ---------------------------------------| F6 Whereis (search for string)
14189 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
14190 F3 Cancel | F1 Get help | F4 Justify paragraph
14191 | ^Z Suspend | ^L Redraw Screen
14192 F2 Send | F6 Alt. editor | F5 Read in a file
14193 </PRE>
14194 <!--chtml else-->
14195 <PRE>
14196 CURSOR MOTION KEYS |EDITING KEYS
14197 ^B (Left Arrow) Back character | ^D Delete current character
14198 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14199 ^P (Up Arrow) Previous line | ^^ Set a mark
14200 ^N (Down Arrow) Next line | ^K Cut marked text or
14201 ^A Beginning of line | delete current line
14202 ^E End of line | ^U Paste text, undelete lines
14203 ^Y Previous page | cut with ^K, or unjustify
14204 ^V Next page |-------------------------------------
14205 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14206 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
14207 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
14208 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
14209 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
14210 ^X Send | ^_ Alt. editor | ^R Read in a file
14211 </PRE>
14212 <!--chtml endif-->
14214 NOTE: The presence or absence of the following commands is determined
14215 by "Feature-List" options in your Alpine configuration. Also,
14216 some of these commands may be administratively disabled by your system
14217 manager; if they don't work, please check with your local help desk
14218 before reporting a bug.
14219 <P>
14220 <UL>
14221 <LI>Suspend (suspends Alpine and gives a system prompt)
14222 <LI>Alternate editor (allows you to compose with your own editor)
14223 </UL>
14224 <P>
14226 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
14227 Ctrl-\, ESC
14228 <P>
14230 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
14231 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
14232 <P>
14233 <End of help on this topic>
14234 </BODY>
14235 </HTML>
14236 ======= h_composer_abook_nick =======
14237 <HTML>
14238 <HEAD>
14239 <TITLE>Addressbook Nickname Explained</TITLE>
14240 </HEAD>
14241 <BODY>
14242 This is a short nickname for this address book entry. If it is used in
14243 place of an address from the composer, the composer will fill in the
14244 address(es) for the entry that matches the nickname.
14245 <P>
14247 Look <A HREF="h_edit_nav_cmds">here</A>
14248 to see the available Editing and Navigation commands.
14249 <P>
14250 <End of help on this topic>
14251 </BODY>
14252 </HTML>
14253 ======= h_composer_abook_full =======
14254 <HTML>
14255 <HEAD>
14256 <TITLE>Addressbook Fullname Explained</TITLE>
14257 </HEAD>
14258 <BODY>
14259 This is the full name field for this entry. If this is going to be a
14260 distribution list (more than one address), it should be a descriptive
14261 phrase describing the list. It will be included in the mail header if you
14262 put the list in the To: or CC: field, or in the To: line if you put the
14263 list in the Lcc: field. It's OK to leave this field blank (and OK to
14264 leave any of the other fields blank, too). If this address book entry is
14265 going to be a simple entry with just one address, then this field is the
14266 person's name. When you send mail to this entry, this is the field to the
14267 left of the brackets. That is, it is the most readable part of the
14268 address. For example, in the sample address:
14269 <PRE>
14270 John Doe <jdoe@some.domain>
14271 </PRE>
14272 "John Doe" is the full name field. If you are sorting your address book
14273 with one of the options that uses full names, then it might be useful to
14274 enter the full name as "Last, First", for example:
14275 <PRE>
14276 Doe, John
14277 </PRE>
14278 so that it will be sorted using Doe instead of John. This will be changed
14279 back into John Doe when you use it.
14280 <P>
14281 Look <A HREF="h_edit_nav_cmds">here</A>
14282 to see the available Editing and Navigation commands.
14283 <P>
14284 <End of help on this topic>
14285 </BODY>
14286 </HTML>
14287 ======= h_composer_abook_fcc =======
14288 <HTML>
14289 <HEAD>
14290 <TITLE>Addressbook Fcc Explained</TITLE>
14291 </HEAD>
14292 <BODY>
14293 If this entry is the first one in the To: line of an outgoing message,
14294 this field will be used for the Fcc (File Carbon Copy) instead of whatever
14295 you would normally get (which depends on which
14296 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
14297 you've chosen).
14298 <P>
14299 If this field consists of two double quotes ("") that tells Alpine
14300 that you don't want any Fcc associated with this entry.
14301 <P>
14302 Look <A HREF="h_edit_nav_cmds">here</A>
14303 to see the available Editing and Navigation commands.
14304 <P>
14305 <End of help on this topic>
14306 </BODY>
14307 </HTML>
14308 ====== h_config_combined_abook_display =====
14309 <HTML>
14310 <HEAD>
14311 <TITLE>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></TITLE>
14312 </HEAD>
14313 <BODY>
14314 <H1>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></H1>
14316 This feature affects the address book display screens.
14317 Normally, expanding an address book from the ADDRESS BOOK LIST screen
14318 will cause the remaining address books and directory servers to disappear
14319 from the screen, leaving only the entries of the expanded address book.
14320 If this feature is set, then the other address books will remain on the screen,
14321 so that all of the address books can be present at once.
14323 <P>
14324 The way that commands work won't be changed.
14325 For example, the Select All command will select all of the entries in the
14326 current address book, not all of the entries in all of the address books.
14327 The WhereIs command will change a little.
14328 It will search through all of the text on the screen plus all of the entries
14329 from expanded address books.
14331 <P>
14332 When this feature is set, the setting of the feature
14333 <A HREF="h_config_expanded_addrbooks">"<!--#echo var="FEAT_expanded-view-of-addressbooks"-->"</A>
14334 has an effect.
14335 <P>
14336 <End of help on this topic>
14337 </BODY>
14338 </HTML>
14339 ====== h_config_titlebar_color_style =====
14340 <HTML>
14341 <HEAD>
14342 <TITLE>OPTION: <!--#echo var="VAR_titlebar-color-style"--></TITLE>
14343 </HEAD>
14344 <BODY>
14345 <H1>OPTION: <!--#echo var="VAR_titlebar-color-style"--></H1>
14347 This option affects the colors used to display the titlebar (the top
14348 line on the screen) when viewing a message.
14350 <P>
14351 The available options include:
14352 <P>
14354 <DL>
14355 <DT>default</DT>
14356 <DD>The color of the titlebar will be the color you set for the
14357 <A HREF="h_config_title_color">Title Color</A>.
14358 The Title Color may be set by using the
14359 <A HREF="h_color_setup">Setup Kolor</A> screen.
14360 </DD>
14362 <DT>indexline</DT>
14363 <DD>The color of the titlebar will be the same as the color of the
14364 index line corresponding to the message being viewed.
14365 The rules that determine what color the index line will be may be set
14366 up by going to the Setup/Rules/Indexcolor screen.
14367 If the index line for a message is not colored explicitly by the
14368 Indexcolor rules, then the titlebar will be colored the same as for
14369 the "default" option above (which is not the same color that
14370 the index line itself will have).
14371 </DD>
14373 <DT>reverse-indexline</DT>
14374 <DD>This is similar to the "indexline" option except the
14375 foreground and background colors from the corresponding index line will
14376 be reversed.
14377 For example, if the index line color is red letters on a white background,
14378 then the titlebar will be white letters on a red background.
14379 If the index line for a message is not colored explicitly by the
14380 Indexcolor rules, then the titlebar will be colored the same as for
14381 the "default" option above (which is not the same color that
14382 the index line itself will have).
14383 </DD>
14384 </DL>
14386 <P>
14388 <UL>
14389 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14390 </UL><P>
14391 <End of help on this topic>
14392 </BODY>
14393 </HTML>
14394 ====== h_config_index_color_style =====
14395 <HTML>
14396 <HEAD>
14397 <TITLE>OPTION: <!--#echo var="VAR_current-indexline-style"--></TITLE>
14398 </HEAD>
14399 <BODY>
14400 <H1>OPTION: <!--#echo var="VAR_current-indexline-style"--></H1>
14402 This option affects the colors used to display the current line in the
14403 MESSAGE INDEX screen.
14404 If you do not have Index Color Rules defined, then this option will
14405 have no effect in the index.
14406 Those Rules may be defined by going to the Setup/Rules/Indexcolor screen.
14407 <P>
14408 If the option
14409 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
14410 is turned on and the
14411 <A HREF="h_config_incunseen_color">Incoming Unseen Color</A>
14412 is set to something other than the default, then
14413 this option also affects the color used to display the current folder
14414 in the Incoming FOLDER LIST screen.
14416 <P>
14417 The available options include:
14418 <P>
14420 <DL>
14421 <DT>flip-colors</DT>
14422 <DD>This is the default.
14423 If an index line is colored because it matches one of your
14424 Index Color Rules, then its colors will be reversed when it is the currently
14425 highlighted line.
14426 For example, if the line is normally red text on a blue background, then
14427 when it is the current line it will be drawn as blue text on a red background.
14428 <P>
14429 The rest of the option values all revert to this flip-colors behavior if
14430 there is no Reverse Color defined.
14431 </DD>
14433 <DT>reverse</DT>
14434 <DD>With this option the Reverse color is always used to highlight the
14435 current line.
14436 </DD>
14438 <DT>reverse-fg</DT>
14439 <DD>The foreground part of the Reverse Color is used to highlight
14440 the current line.
14441 If this would cause the text to be unreadable (because the foreground and
14442 background colors are the same) or if it would cause no change in the
14443 color of the index line, then the colors are flipped instead.
14444 <P>
14445 Some people think this works particularly well if you use different
14446 background colors to emphasize "interesting" lines,
14447 but always with the same Normal foreground color,
14448 and you use a different foreground color for the Reverse Color.
14449 </DD>
14451 <DT>reverse-fg-no-ambiguity</DT>
14452 <DD>With the "reverse-fg" rule above, it is possible that
14453 the resulting color will be exactly the same as the regular Reverse
14454 Color.
14455 That can lead to some possible confusion because an
14456 "interesting"
14457 line that is the current line will be displayed exactly the same as a
14458 non-interesting line that is current.
14459 You can't tell whether the line is just a regular current line or if it is
14460 an "interesting" current line by looking at the color.
14461 Setting the option to this value removes that ambiguity.
14462 It is the same as the "reverse-fg" setting unless the resulting
14463 interesting current line would look just like a non-interesting current line.
14464 In that case, the interesting line's colors are simply flipped (like in the
14465 default behavior).
14466 <P>
14467 As an alternative way to preserve the line's interestingness in this case,
14468 you may find that using both a different foreground and a different
14469 background color for the interesting line will help.
14470 </DD>
14472 <DT>reverse-bg</DT>
14473 <DD>The background part of the Reverse Color is used to highlight
14474 the current line.
14475 If this would cause the text to be unreadable (because the foreground and
14476 background colors are the same) or if it would cause no change in the
14477 color of the index line, then the colors are flipped instead.
14478 <P>
14479 Some people think this works particularly well if you use different
14480 foreground colors to emphasize "interesting" lines,
14481 but always with the same Normal background color,
14482 and you use a different background color for the Reverse Color.
14483 </DD>
14485 <DT>reverse-bg-no-ambiguity</DT>
14486 <DD>As with the "reverse-fg" case, the "reverse-bg"
14487 rule may also result in a color that is exactly the same as the regular
14488 Reverse Color.
14489 Setting the option to this value removes that ambiguity.
14490 It is the same as the "reverse-bg" setting unless the resulting
14491 current line has the same color as the Reverse Color.
14492 In that case, the interesting line's colors are simply flipped (like in the
14493 default behavior).
14494 </DD>
14495 </DL>
14497 <P>
14499 <UL>
14500 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14501 </UL><P>
14502 <End of help on this topic>
14503 </BODY>
14504 </HTML>
14505 ====== h_config_expanded_addrbooks =====
14506 <HTML>
14507 <HEAD>
14508 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></TITLE>
14509 </HEAD>
14510 <BODY>
14511 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></H1>
14513 If multiple address books (either personal or global) are defined, and you
14514 wish to have them all expanded implicitly upon entering the ADDRESS BOOK
14515 screen, then set this feature. This feature will have no effect unless the
14516 feature
14517 <A HREF="h_config_combined_abook_display">"<!--#echo var="FEAT_combined-addrbook-display"-->"</A>
14518 is also set.
14519 <P>
14520 <End of help on this topic>
14521 </BODY>
14522 </HTML>
14523 ====== h_config_combined_folder_display =====
14524 <HTML>
14525 <HEAD>
14526 <TITLE>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></TITLE>
14527 </HEAD>
14528 <BODY>
14529 <H1>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></H1>
14531 This feature affects the folder list display screens.
14532 Normally, each folder list is viewed within its collection only. This
14533 command allows folder lists to be viewed within a single screen that
14534 combines the contents of all collections.
14536 <P>
14537 The way that commands work won't be changed.
14538 For example, the Select All command will select all of the folders in the
14539 current collection, not all of the entries in all of the collections.
14540 The WhereIs command will change a little.
14541 It will search through all of the folders in the current collection as well
14542 as all the folder in any other expanded collection.
14544 <P>
14545 When this feature is set, the setting of the feature
14546 <A HREF="h_config_expanded_folders">"<!--#echo var="FEAT_expanded-view-of-folders"-->"</A>
14547 has an effect.
14548 <P>
14549 <End of help on this topic>
14550 </BODY>
14551 </HTML>
14552 ====== h_config_combined_subdir_display =====
14553 <HTML>
14554 <HEAD>
14555 <TITLE>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></TITLE>
14556 </HEAD>
14557 <BODY>
14558 <H1>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></H1>
14560 This feature affects the Folder List screen when
14561 the
14562 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14563 feature is enabled. Normally, selecting a directory from the Folder
14564 List takes you into a new screen displaying only the contents of
14565 that directory.
14567 <P>
14568 Enabling this feature will cause the contents of the selected
14569 directory to be
14570 displayed within the boundaries of the "Collection" it
14571 is a part of. All previously displayed collections will remain
14572 in the screen.
14574 <P>
14575 The way that commands work won't be changed.
14576 For example, the Select All command will select all of the folders in the
14577 directory, as opposed to all of the entries in all of the collections.
14578 The WhereIs command will change a little.
14579 It will search through all of the folders in the current collection as well
14580 as all the folder in any other expanded collection.
14582 <P>
14583 <End of help on this topic>
14584 </BODY>
14585 </HTML>
14586 ====== h_config_separate_fold_dir_view =====
14587 <HTML>
14588 <HEAD>
14589 <TITLE>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></TITLE>
14590 </HEAD>
14591 <BODY>
14592 <H1>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></H1>
14594 This feature affects folder collections wherein a folder
14595 and directory can have the same name. By default, Alpine displays them
14596 only once, denoting that it is both a folder and directory by appending
14597 the folder name with the hierarchy character enclosed
14598 in square brackets.
14601 <P>
14602 Enabling this feature will cause Alpine to display such names
14603 separately marking the name representing a directory with a trailing
14604 hierarchy delimiter (typically the slash, "/", character).
14606 <P>
14607 The feature also alters the command set slightly. By default, the
14608 right-arrow descends into the directory, while hitting the Return key will
14609 cause the folder by that name to be opened.
14611 <P>
14612 With this feature set, the Return key will open the highlighted folder, or
14613 enter the highlighted directory.
14615 <P>
14616 <End of help on this topic>
14617 </BODY>
14618 </HTML>
14619 ====== h_config_expanded_folders =====
14620 <HTML>
14621 <HEAD>
14622 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></TITLE>
14623 </HEAD>
14624 <BODY>
14625 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></H1>
14627 If multiple folder collections are defined, and you
14628 wish to have them all expanded implicitly upon entering the FOLDER LIST
14629 screen, then set this feature. This feature will have no effect unless the
14630 feature
14631 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14632 is also set.
14633 <P>
14634 <End of help on this topic>
14635 </BODY>
14636 </HTML>
14637 ======= h_config_ldap_server =======
14638 <HTML>
14639 <HEAD>
14640 <TITLE>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
14641 </HEAD>
14642 <BODY>
14643 <H1>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
14644 This is the name of the host where an LDAP server is running.
14645 For redundancy, this may be a space-delimited set of server names, in which
14646 case the first server that answers is used.
14647 Each of the server names may be optionally followed by
14648 a colon and a port number.
14649 If this form is used then the port number configured below in the
14650 <EM>port</EM> field is not used.
14651 <P>
14652 To find out whether your organization has its own LDAP server,
14653 contact its computing support staff.
14654 <P><UL>
14655 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14656 </UL>
14657 <P>
14658 <End of help on this topic>
14659 </BODY>
14660 </HTML>
14661 ======= h_config_ldap_base =======
14662 <HTML>
14663 <HEAD>
14664 <TITLE>LDAP OPTION: Search-Base</TITLE>
14665 </HEAD>
14666 <BODY>
14667 <H1>LDAP OPTION: Search-Base</H1>
14669 This is the search base to be used on this server. It functions as a filter
14670 by restricting your searches in the LDAP server database
14671 to the specified contents of the specified fields. Without it, searches
14672 submitted to this directory server may fail. It might be something
14673 like:
14675 <PRE>
14676 O = <Your Organization Name>, C = US
14677 </PRE>
14678 or it might be blank.
14679 (Some LDAP servers actually ignore anything specified here.)
14680 <P>
14681 If in doubt what parameters you should specify here,
14682 contact the maintainers of the LDAP server.
14683 <P><UL>
14684 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14685 </UL>
14686 <P>
14687 <End of help on this topic>
14688 </BODY>
14689 </HTML>
14690 ======= h_config_ldap_port =======
14691 <HTML>
14692 <HEAD>
14693 <TITLE>LDAP OPTION: Port</TITLE>
14694 </HEAD>
14695 <BODY>
14696 <H1>LDAP OPTION: Port</H1>
14698 This is the TCP port number to be used with this LDAP server. If you leave
14699 this blank port 389 will be used.
14700 <P>
14701 <End of help on this topic>
14702 </BODY>
14703 </HTML>
14704 ======= h_config_ldap_nick =======
14705 <HTML>
14706 <HEAD>
14707 <TITLE>LDAP OPTION: Nickname</TITLE>
14708 </HEAD>
14709 <BODY>
14710 <H1>LDAP OPTION: Nickname</H1>
14712 This is a nickname to be used in displays. If you don't supply a
14713 nickname the server name
14714 (<A HREF="h_config_ldap_server">"<!--#echo var="VAR_ldap-servers"-->"</A>)
14715 will be used instead. This option is strictly for your convenience.
14716 <P>
14717 <End of help on this topic>
14718 </BODY>
14719 </HTML>
14720 ======= h_config_ldap_binddn =======
14721 <HTML>
14722 <HEAD>
14723 <TITLE>LDAP OPTION: Bind-DN</TITLE>
14724 </HEAD>
14725 <BODY>
14726 <H1>LDAP OPTION: Bind-DN</H1>
14728 You may need to authenticate to the LDAP server before you are able to use it.
14729 This is the Distinguished Name to bind to when authenticating to this server.
14730 Try leaving this blank until you know you need it.
14731 <P>
14732 Alpine only knows about LDAP Simple authentication.
14733 It does not attempt LDAP SASL authentication.
14734 The DN and password will be sent in the clear unless TLS encryption is
14735 being used on this connection.
14736 Because of this, you may want to set the LDAP feature
14737 <A HREF="h_config_ldap_opts_tls">"Attempt-TLS-On-Connection"</A>
14738 or the feature
14739 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
14740 if you are going to be providing a password.
14741 <P><UL>
14742 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14743 </UL>
14744 <P>
14745 <End of help on this topic>
14746 </BODY>
14747 </HTML>
14748 ======= h_config_ldap_opts_impl =======
14749 <HTML>
14750 <HEAD>
14751 <TITLE>LDAP FEATURE: Use-Implicitly-From-Composer</TITLE>
14752 </HEAD>
14753 <BODY>
14754 <H1>LDAP FEATURE: Use-Implicitly-From-Composer</H1>
14756 Set this to have lookups done to this server implicitly from the composer.
14757 If an address doesn't look like a fully-qualified address, it will be looked
14758 up in your address books, and if it doesn't match a nickname there, then it
14759 will be looked up on the LDAP servers that have this feature set.
14760 The lookups will also be done when using the address completion feature
14761 (TAB command) in the composer if any of the serves have this feature set.
14762 Also see the LDAP feature
14763 <A HREF="h_config_ldap_opts_rhs">"Lookup-Addrbook-Contents"</A>
14764 and the Setup/Config feature
14765 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
14766 <P>
14767 <End of help on this topic>
14768 </BODY>
14769 </HTML>
14770 ======= h_config_ldap_opts_tls =======
14771 <HTML>
14772 <HEAD>
14773 <TITLE>LDAP FEATURE: Attempt-TLS-On-Connection</TITLE>
14774 </HEAD>
14775 <BODY>
14776 <H1>LDAP FEATURE: Attempt-TLS-On-Connection</H1>
14778 When connecting to this server Alpine will attempt to use TLS encryption
14779 on the connection.
14780 Also see the closely related feature
14781 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
14782 <P>
14783 <End of help on this topic>
14784 </BODY>
14785 </HTML>
14786 ======= h_config_ldap_opts_tlsmust =======
14787 <HTML>
14788 <HEAD>
14789 <TITLE>LDAP FEATURE: Require-TLS-On-Connection</TITLE>
14790 </HEAD>
14791 <BODY>
14792 <H1>LDAP FEATURE: Require-TLS-On-Connection</H1>
14794 When connecting to this server Alpine will attempt to use TLS encryption
14795 on the connection.
14796 If the StartTLS operation fails then the connection will not be used.
14797 <P>
14798 <End of help on this topic>
14799 </BODY>
14800 </HTML>
14801 ====== h_config_ldap_opts_rhs =====
14802 <HTML>
14803 <HEAD>
14804 <TITLE>LDAP FEATURE: Lookup-Addrbook-Contents</TITLE>
14805 </HEAD>
14806 <BODY>
14807 <H1>LDAP FEATURE: Lookup-Addrbook-Contents</H1>
14809 Normally implicit LDAP lookups from the composer are done only for the
14810 strings you type in from the composer screen. In other words, you type in
14811 something in the To or CC field and press return, then the string is looked up.
14812 First that string is looked up in your address books. If a match is found
14813 there, then the results of that match are looked up again. If you place
14814 a string in your address book that you want to have looked up on the LDAP
14815 directory server, you need to turn on this feature. If you set this feature
14816 for a server, you almost always will also want to set the
14817 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
14818 feature. An example might serve to best illustrate this feature.
14819 <P>
14820 If an LDAP lookup of "William Clinton" normally returns an
14821 entry with an
14822 address of pres@whitehouse.gov, then you might put an entry in your address
14823 book that looks like:
14824 <P>
14825 <CENTER><SAMP>Nickname = bill</SAMP></CENTER><BR>
14826 <CENTER><SAMP>Address = "William Clinton"</SAMP></CENTER>
14827 <P>
14828 Now, when you type "bill" into an
14829 address field in the composer Alpine will
14830 find the "bill" entry in your address book.
14831 It will replace "bill" with
14832 "William Clinton".
14833 It will then search for an entry with that nickname
14834 in your address book and not find one. If this feature
14835 is set, Alpine will then attempt to lookup
14836 "William Clinton" on the LDAP server and find the entry with address
14837 pres@whitehouse.gov.
14838 <P>
14839 A better way to accomplish the same thing is probably to use the feature
14840 <A HREF="h_config_ldap_opts_ref">"Save-Search-Criteria-Not-Result"</A>.
14841 <P>
14842 <End of help on this topic>
14843 </BODY>
14844 </HTML>
14845 ====== h_config_ldap_opts_ref =====
14846 <HTML>
14847 <HEAD>
14848 <TITLE>LDAP FEATURE: Save-Search-Criteria-Not-Result</TITLE>
14849 </HEAD>
14850 <BODY>
14851 <H1>LDAP FEATURE: Save-Search-Criteria-Not-Result</H1>
14853 Normally when you save the results of an LDAP directory lookup to your
14854 address book the results of the lookup are saved. If this feature is set
14855 and the entry being saved was found on this directory server, then the
14856 search criteria is saved instead of the results of the search. When this
14857 address book entry is used in the future, instead of copying the results
14858 from the address book the directory lookup will be done again. This could
14859 be useful if the copied result might become stale because the data on
14860 the directory server changes (for example, the entry's email address changes).
14861 You probably don't want to set this feature if the server is at all slow or
14862 unreliable.
14863 <P>
14864 The way this actually works is that instead of saving the email address
14865 in your address book, Alpine saves enough information to look up the same
14866 directory entry again. In particular, it saves the server name and the
14867 distinguished name of the entry. It's possible that the server administrators
14868 might change the format of distinguished names on the server, or that the
14869 entry might be removed from the server. If Alpine notices this, you will be warned
14870 and a backup copy of the email address will be used. You may want to create
14871 a new entry in this case, since you will get the annoying warning every
14872 time you use the old entry. You may do that by Saving the entry to a new
14873 nickname in the same address book. You will be asked whether or not you
14874 want to use the backup email address.
14875 <P>
14876 A related feature in the Setup/Config screen is
14877 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
14878 <P>
14879 <End of help on this topic>
14880 </BODY>
14881 </HTML>
14882 ======= h_config_ldap_opts_nosub =======
14883 <HTML>
14884 <HEAD>
14885 <TITLE>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</TITLE>
14886 </HEAD>
14887 <BODY>
14888 <H1>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</H1>
14890 Spaces in your input are normally handled specially.
14891 Each space character is replaced
14892 by
14893 <P>
14894 <CENTER><SAMP>* <SPACE></SAMP></CENTER>
14895 <P>
14896 in the search query (but not by "* <SPACE> *").
14897 The reason this is done is so the input string
14898 <P>
14899 <CENTER><SAMP>Greg Donald</SAMP></CENTER>
14900 <P>
14901 (which is converted to "Greg* Donald") will match
14902 the names "Greg Donald",
14903 "Gregory Donald", "Greg F. Donald", and
14904 "Gregory F Donald"; but it won't match "Greg McDonald".
14905 If the "Search-Rule" you were using was "begins-with",
14906 then it would also match the name "Greg Donaldson".
14907 <P>
14908 Turning on this feature will disable this substitution.
14909 <P>
14910 <End of help on this topic>
14911 </BODY>
14912 </HTML>
14913 ====== h_config_ldap_searchtypes =======
14914 <HTML>
14915 <HEAD>
14916 <TITLE>LDAP OPTION: Search-Type</TITLE>
14917 </HEAD>
14918 <BODY>
14919 <H1>LDAP OPTION: Search-Type</H1>
14921 This affects the way that LDAP searches are done.
14922 In particular, this tells the server where to look for the string to be matched.
14923 If set to "name" then the string that is being searched for will
14924 be compared with the string in the
14925 "Name" field on the server
14926 (technically, it is the "commonname" field on the server).
14927 "Surname" means we're looking for a
14928 match in the "Surname" field on the
14929 server (actually the "sn" field).
14930 "Givenname" really is "givenname"
14931 and "email" is the electronic mail address (this is actually the field
14932 called "mail" or "electronicmail" on the server).
14933 The other three types are combinations of
14934 the types listed so far. "Name-or-email"
14935 means the string should appear
14936 in either the "name" field OR the "email" field.
14937 Likewise, "surname-or-givenname"
14938 means "surname" OR "givenname"
14939 and "sur-or-given-or-name-or-email" means the obvious thing.
14940 <P>
14941 This search TYPE is combined with the
14942 search <A HREF="h_config_ldap_searchrules">RULE</A>
14943 to form the actual search query.
14944 <P>
14945 The usual default value for this
14946 option is "sur-or-given-or-name-or-email".
14947 This type of search may be slow on some servers.
14948 Try "name-or-email", which is often
14949 faster, or just "name" if the performance seems to be a problem.
14950 <P>
14951 Some servers have been configured with different attribute names for
14952 these four fields.
14953 In other words, instead of using the attribute name "mail"
14954 for the email address field, the server might be configured to use something
14955 else, for example, "rfc822mail" or "internetemailaddress".
14956 Alpine can be configured to use these different attribute names by using
14957 the four configuration options:
14958 <P><UL>
14959 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
14960 </UL>
14961 <P><UL>
14962 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
14963 </UL>
14964 <P><UL>
14965 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
14966 </UL>
14967 <P><UL>
14968 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
14969 </UL>
14970 <P>
14971 <End of help on this topic>
14972 </BODY>
14973 </HTML>
14974 ====== h_config_ldap_searchrules =======
14975 <HTML>
14976 <HEAD>
14977 <TITLE>LDAP OPTION: Search-Rule</TITLE>
14978 </HEAD>
14979 <BODY>
14980 <H1>LDAP OPTION: Search-Rule</H1>
14982 This affects the way that LDAP searches are done.
14983 If set to "equals" then
14984 only exact matches count.
14985 "Contains" means that the string you type in
14986 is a substring of what you are matching against.
14987 "Begins-with" and "ends-with"
14988 mean that the string starts or ends with the string you type in.
14989 <P>
14990 Spaces in your input are normally handled specially, but you can turn that
14991 special handling off with the
14992 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
14993 feature.
14994 <P>
14995 The usual default value for this option is "begins-with".
14996 <P>
14997 <End of help on this topic>
14998 </BODY>
14999 </HTML>
15000 ======= h_config_ldap_email_attr =======
15001 <HTML>
15002 <HEAD>
15003 <TITLE>LDAP OPTION: EmailAttribute</TITLE>
15004 </HEAD>
15005 <BODY>
15006 <H1>LDAP OPTION: EmailAttribute</H1>
15008 This is the name of the attribute that is searched for when looking for
15009 an email address. The default value for this option is "mail" or
15010 "electronicmail".
15011 If the server you are using uses a different attribute name for the email
15012 address, put that attribute name here.
15013 <P>
15014 This will affect the search filter used if your Search-Type is one that
15015 contains a search for "email".
15016 It will also cause the attribute value matching this attribute name to be used
15017 as the email address when you look up an entry from the composer.
15018 <P>
15019 <End of help on this topic>
15020 </BODY>
15021 </HTML>
15022 ======= h_config_ldap_sn_attr =======
15023 <HTML>
15024 <HEAD>
15025 <TITLE>LDAP OPTION: SurnameAttribute</TITLE>
15026 </HEAD>
15027 <BODY>
15028 <H1>LDAP OPTION: SurnameAttribute</H1>
15030 This is the name of the attribute that is searched for when looking for
15031 the surname of the entry. The default value for this option is "sn".
15032 If the server you are using uses a different attribute name for the surname,
15033 put that attribute name here.
15034 This will affect the search filter used if your Search-Type is one that
15035 contains a search for "surname".
15036 <P>
15037 <End of help on this topic>
15038 </BODY>
15039 </HTML>
15040 ======= h_config_ldap_gn_attr =======
15041 <HTML>
15042 <HEAD>
15043 <TITLE>LDAP OPTION: GivennameAttribute</TITLE>
15044 </HEAD>
15045 <BODY>
15046 <H1>LDAP OPTION: GivennameAttribute</H1>
15048 This is the name of the attribute that is searched for when looking for
15049 the given name of the entry. The default value for this option is "givenname".
15050 If the server you are using uses a different attribute name for the given name,
15051 put that attribute name here.
15052 This will affect the search filter used if your Search-Type is one that
15053 contains a search for "givenname".
15054 <P>
15055 <End of help on this topic>
15056 </BODY>
15057 </HTML>
15058 ======= h_config_ldap_cn_attr =======
15059 <HTML>
15060 <HEAD>
15061 <TITLE>LDAP OPTION: NameAttribute</TITLE>
15062 </HEAD>
15063 <BODY>
15064 <H1>LDAP OPTION: NameAttribute</H1>
15066 This is the name of the attribute that is searched for when looking for
15067 the name of the entry. The default value for this option is "cn", which
15068 stands for common name.
15069 If the server you are using uses a different attribute name for the name,
15070 put that attribute name here.
15071 This will affect the search filter used if your Search-Type is one that
15072 contains a search for "name".
15073 <P>
15074 <End of help on this topic>
15075 </BODY>
15076 </HTML>
15077 ======= h_config_ldap_time =======
15078 <HTML>
15079 <HEAD>
15080 <TITLE>LDAP OPTION: Timelimit</TITLE>
15081 </HEAD>
15082 <BODY>
15083 <H1>LDAP OPTION: Timelimit</H1>
15085 This places a limit on the number of seconds the LDAP search will continue.
15086 The default is 30 seconds. A value of 0 means no limit. Note that some servers
15087 may place limits of their own on searches.
15088 <P>
15089 <End of help on this topic>
15090 </BODY>
15091 </HTML>
15092 ======= h_config_ldap_size =======
15093 <HTML>
15094 <HEAD>
15095 <TITLE>LDAP OPTION: Sizelimit</TITLE>
15096 </HEAD>
15097 <BODY>
15098 <H1>LDAP OPTION: Sizelimit</H1>
15100 This places a limit on the number of entries returned by the LDAP server.
15101 A value of 0 means no limit. The default is 0. Note that some servers
15102 may place limits of their own on searches.
15103 <P>
15104 <End of help on this topic>
15105 </BODY>
15106 </HTML>
15107 ======= h_config_ldap_cust =======
15108 <HTML>
15109 <HEAD>
15110 <TITLE>LDAP OPTION: Custom-Search-Filter</TITLE>
15111 </HEAD>
15112 <BODY>
15113 <H1>LDAP OPTION: Custom-Search-Filter</H1>
15115 This one is for advanced users only! If you define this, then the
15116 "Search-Type" and "Search-Rule" defined are both ignored.
15117 However, the feature
15118 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
15119 is still in effect.
15120 That is, the space substitution will take place even in a custom filter unless
15121 you disable it.
15122 <P>
15123 If your LDAP service stops working and you suspect it might be because
15124 of your custom filter, just delete this filter and try using the
15125 "Search-Type" and "Search-Rule" instead.
15126 Another option that sometimes causes trouble is the
15127 <A HREF="h_config_ldap_base">"Search-Base"</A> option.
15128 <P>
15129 This variable may be set to the string representation of an LDAP search
15130 filter (see RFC1960). In the places where you want the address string to be
15131 substituted in, put a '%s' in this filter string. Here are some examples:
15132 <P>
15133 A "Search-Type" of "name" with "Search-Rule" of "begins-with"
15134 is equivalent to the "Custom-Search-Filter"
15135 <PRE>
15136 (cn=%s*)
15137 </PRE>
15138 When you try to match against the string "string" the program replaces
15139 the "%s" with "string" (without the quotes). You may have multiple "%s"'s and
15140 they will all be replaced with the string. There is a limit of 10 "%s"'s.
15141 <P>
15142 A "Search-Type" of "name-or-email" with "Search-Rule"
15143 of "contains" is equivalent to
15144 <PRE>
15145 (|(cn=*%s*)(mail=*%s*))
15146 </PRE>
15147 <P>
15148 If your server uses a different attribute <EM>name</EM> than
15149 Alpine uses by default,
15150 (for example, it uses "rfc822mail" instead of "mail"),
15151 then you may be able to use one or more of the four attribute configuration
15152 options instead of defining a custom filter:
15153 <P><UL>
15154 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
15155 </UL>
15156 <P><UL>
15157 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
15158 </UL>
15159 <P><UL>
15160 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
15161 </UL>
15162 <P><UL>
15163 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
15164 </UL>
15165 <P>
15166 <End of help on this topic>
15167 </BODY>
15168 </HTML>
15169 ======= h_composer_abook_comment =======
15170 <HTML>
15171 <HEAD>
15172 <TITLE>Addressbook Comment Explained</TITLE>
15173 </HEAD>
15174 <BODY>
15175 This is a comment to help you remember what this entry is. The WhereIs
15176 command searches comments so that it is easier to find an entry with a comment
15177 you know about attached to it. This field is not used in the outgoing message.
15178 <P>
15179 Look <A HREF="h_edit_nav_cmds">here</A>
15180 to see the available Editing and Navigation commands.
15181 <P>
15182 <End of help on this topic>
15183 </BODY>
15184 </HTML>
15185 ======= h_composer_abook_addrs =======
15186 <HTML>
15187 <HEAD>
15188 <TITLE>Addressbook Lists</TITLE>
15189 </HEAD>
15190 <BODY>
15191 <H1>Addressbook Lists</H1>
15193 This is a list of addresses to send to when sending to this address book
15194 entry. Each member of the list may be an address or another nickname from
15195 any of your address books. If it is an address, it is OK to include the
15196 full name field as well as the electronic address portion of that address.
15197 For example, the following are all legitimate entries in this field:
15199 <DL><DT> </DT>
15200 <DD>john (a nickname in your address book)
15201 <DD>jdoe@some.domain
15202 <DD>John Doe <jdoe@some.domain>
15203 </DL>
15205 The addresses should be listed separated by commas, just like you would
15206 enter them from the composer.
15208 <P>
15210 The only difference between a distribution list and a simple entry with a
15211 single address, is that a distribution list has more than one address
15212 listed in the Addresses: field, whereas a simple personal entry has just
15213 one address.
15215 <P>
15217 For individual address book entries, if there is a full name in the
15218 Fullname: field (filling in the Fullname: field is not required), it is
15219 used. If the full name is specified in the Address: field and not in the
15220 Fullname: field, then the full name from the Address: field is used.
15222 <P>
15224 If you type the nickname of a distribution list from one of your address
15225 books in the Lcc: field, then the full name of that list is used in the
15226 To: field. If you put a list in the To: or Cc: fields, that list will be
15227 expanded into all of its addresses. If the list has a full name, then
15228 that will appear at the beginning of the addresses.
15230 <DL><DT> </DT>
15231 <DD>Sewing Club <john@somewhere>, nancy@something.else, Sal
15232 <sal@here.there>
15233 </DL>
15235 If the first address in the distribution list also has a full name, then
15236 the list full name and that full name are combined into something like the
15237 following:
15239 <DL><DT> </DT>
15240 <DD>Sewing Club -- John Smith <john@somewhere>
15241 </DL>
15244 If you specify a list via Lcc, the full name is used in the To: line. If
15245 you specify a list in the To: or Cc: fields, then it uses the same method
15246 as for individual entries for filling in the full name.
15248 <P>
15250 For help with editing and navigation commands, check the Help for the
15251 Nickname: field.
15253 <P>
15254 <End of help on this topic>
15255 </BODY>
15256 </HTML>
15257 ======= h_config_role_nick =======
15258 <HTML>
15259 <HEAD>
15260 <TITLE>Nickname Explained</TITLE>
15261 </HEAD>
15262 <BODY>
15263 <H1>Nickname Explained</H1>
15265 This is a nickname to help you.
15266 You should have a different nickname for each role you define.
15267 The nickname will be used in the SETUP ROLE RULES screen to allow you to
15268 pick a role to edit.
15269 It will also be used when you send a message to let you know you are
15270 sending with a different role than you use by default, and
15271 it will be useful for choosing a role when composing with the Role command
15272 or when composing with one of the Role Uses set to With Confirmation.
15273 This field is not used in the outgoing message.
15274 <P>
15275 Look <A HREF="h_edit_nav_cmds">here</A>
15276 to see the available Editing and Navigation commands.
15277 <P>
15278 <End of help on this topic>
15279 </BODY>
15280 </HTML>
15281 ======= h_config_role_comment =======
15282 <HTML>
15283 <HEAD>
15284 <TITLE>Comment Explained</TITLE>
15285 </HEAD>
15286 <BODY>
15287 <H1>Comment Explained</H1>
15289 This is a comment to help you.
15290 This comment does not play any functional role, it is simply an optional
15291 comment to help you remember what the rule is for.
15292 <P>
15293 Look <A HREF="h_edit_nav_cmds">here</A>
15294 to see the available Editing and Navigation commands.
15295 <P>
15296 <End of help on this topic>
15297 </BODY>
15298 </HTML>
15299 ======= h_config_other_nick =======
15300 <HTML>
15301 <HEAD>
15302 <TITLE>Nickname Explained</TITLE>
15303 </HEAD>
15304 <BODY>
15305 <H1>Nickname Explained</H1>
15307 This is a nickname to help you.
15308 You should have a different nickname for each rule you define.
15309 The nickname will be used in the SETUP OTHER RULES screen to allow you to
15310 pick a rule to edit.
15311 <P>
15312 Look <A HREF="h_edit_nav_cmds">here</A>
15313 to see the available Editing and Navigation commands.
15314 <P>
15315 <End of help on this topic>
15316 </BODY>
15317 </HTML>
15318 ======= h_config_score_nick =======
15319 <HTML>
15320 <HEAD>
15321 <TITLE>Nickname Explained</TITLE>
15322 </HEAD>
15323 <BODY>
15324 <H1>Nickname Explained</H1>
15326 This is a nickname to help you.
15327 You should have a different nickname for each scoring rule you define.
15328 The nickname will be used in the SETUP SCORING RULES screen to allow you to
15329 pick a rule to edit.
15330 <P>
15331 Look <A HREF="h_edit_nav_cmds">here</A>
15332 to see the available Editing and Navigation commands.
15333 <P>
15334 <End of help on this topic>
15335 </BODY>
15336 </HTML>
15337 ======= h_config_incol_nick =======
15338 <HTML>
15339 <HEAD>
15340 <TITLE>Nickname Explained</TITLE>
15341 </HEAD>
15342 <BODY>
15343 <H1>Nickname Explained</H1>
15345 This is a nickname to help you.
15346 You should have a different nickname for each color rule you define.
15347 The nickname will be used in the SETUP INDEX COLOR RULES screen to allow you to
15348 pick a rule to edit.
15349 <P>
15350 Look <A HREF="h_edit_nav_cmds">here</A>
15351 to see the available Editing and Navigation commands.
15352 <P>
15353 <End of help on this topic>
15354 </BODY>
15355 </HTML>
15356 ======= h_config_filt_nick =======
15357 <HTML>
15358 <HEAD>
15359 <TITLE>Nickname Explained</TITLE>
15360 </HEAD>
15361 <BODY>
15362 <H1>Nickname Explained</H1>
15364 This is a nickname to help you.
15365 You should have a different nickname for each filtering rule you define.
15366 The nickname will be used in the SETUP FILTERING RULES screen to allow you to
15367 pick a rule to edit.
15368 <P>
15369 Look <A HREF="h_edit_nav_cmds">here</A>
15370 to see the available Editing and Navigation commands.
15371 <P>
15372 <End of help on this topic>
15373 </BODY>
15374 </HTML>
15375 ======= h_config_score_topat =======
15376 <HTML>
15377 <HEAD>
15378 <TITLE>"To:" Pattern Explained</TITLE>
15379 </HEAD>
15380 <BODY>
15381 <H1>"To:" Pattern Explained</H1>
15383 Any text you enter as the "To pattern"
15384 will be compared to the recipients from the To: line of
15385 the message being scored.
15386 When the text you entered matches
15387 all or part of the To: line of a message, then the Score Value
15388 you have specified will be added to the score for the message.
15389 (Any other non-blank parts of the Pattern must match, too.)
15390 <P>
15392 You may enter a complete email address, part of an address, or a
15393 list of addresses or partial addresses.
15394 For example:
15395 <P>
15397 <PRE>
15398 To pattern = friend@public.com
15400 To pattern = rated.net
15402 To pattern = xxx@adults.com
15403 admin@msn.com
15404 fool@motleyfool.com
15405 </PRE>
15407 <P>
15408 Each of those are valid To patterns.
15409 <P>
15411 Messages match those patterns if any of the
15412 addresses in the To: line of the message contains the pattern.
15413 If the pattern is a list of patterns
15414 (like the last example above) then it is a match if any of the patterns in
15415 the list match any of the addresses in the To: line.
15416 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15417 present for a match.
15418 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15419 address2 must be present.
15420 That is exactly what using a list does.)
15421 <P>
15423 Some messages may be "bounced" to you, and will
15424 have a "Resent-To:" header line.
15425 If the message contains a Resent-To: line
15426 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15427 Alpine will look for
15428 matches to your "To patterns" there, and <EM>NOT</EM> in
15429 the original To: line.
15430 <P>
15432 When entering a pattern, you may choose an address from your address book
15433 with the "T" command.
15434 <P>
15436 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15437 "!" "toggle NOT" command.
15438 This changes the meaning of the To pattern so that it has the opposite meaning.
15439 It will be considered a match if there are no matches between the
15440 addresses in the To: line and the list of To patterns.
15441 <P>
15442 Don't make the mistake of putting the "!" in the data field for
15443 the pattern.
15444 For example, if you type the characters "!frizzle" into the To
15445 pattern, the pattern will look like:
15446 <P>
15447 <PRE>
15448 To pattern = !frizzle
15449 </PRE>
15450 <P>
15451 This means you want to match the 8 character sequence "!frizzle".
15452 In order to match messages that do not have "frizzle" in
15453 their To field, first type the characters "frizzle" followed
15454 by carriage return for the value of the To pattern, then negate it
15455 by typing the "!" command.
15456 It should end up looking like
15457 <P>
15458 <PRE>
15459 ! To pattern = frizzle
15460 </PRE>
15461 <P>
15462 You are not limited to using the six standard header patterns that are
15463 normally shown (To, From, Sender, Cc, News, and Subject).
15464 You may add any other header to a Pattern by
15465 using the "eXtraHdr" command to specify a different
15466 message header line; and then the Add or Change command to fill in
15467 a pattern for the new header line, just like you would for a standard header.
15468 <P>
15469 A technicality: Since comma is the character used to separate multiple
15470 values in a pattern field, you have to escape comma with a backslash (\) if
15471 you want to include a literal comma in the field.
15472 In other words, if you type a backslash followed by a comma it will
15473 be interpreted as a comma by Alpine, instead of as a separator between
15474 pattern values.
15475 All other backslashes are literal backslashes and should not be escaped.
15476 <P>
15477 Look "<A HREF="h_rule_patterns">here</A>"
15478 for more information on Patterns.
15479 <P>
15480 Look <A HREF="h_edit_nav_cmds">here</A>
15481 to see the available Editing and Navigation commands.
15482 <P>
15483 <End of help on this topic>
15484 </BODY>
15485 </HTML>
15486 ======= h_config_incol_topat =======
15487 <HTML>
15488 <HEAD>
15489 <TITLE>"To:" Pattern Explained</TITLE>
15490 </HEAD>
15491 <BODY>
15492 <H1>"To:" Pattern Explained</H1>
15494 Any text you enter as the "To pattern"
15495 will be compared to the recipients from the To: lines of
15496 the messages in the index.
15497 When the text you entered matches
15498 all or part of the To: line of a message, then the Index Line Color you have
15499 specified will be used for that line in the index.
15500 (Any other non-blank parts of the Pattern must match, too.)
15501 <P>
15503 You may enter a complete email address, part of an address, or a
15504 list of addresses or partial addresses.
15505 For example:
15506 <P>
15508 <PRE>
15509 To pattern = friend@public.com
15510 To pattern = rated.net
15511 To pattern = xxx@adults.com
15512 admin@msn.com
15513 fool@motleyfool.com
15514 </PRE>
15516 <P>
15517 Each of those are valid To patterns.
15518 <P>
15520 Messages match those patterns if any of the
15521 addresses in the To: line of the message contains the pattern.
15522 If the pattern is a list of patterns
15523 (like the last example above) then it is a match if any of the patterns in
15524 the list match any of the addresses in the To: line.
15525 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15526 present for a match.
15527 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15528 address2 must be present.
15529 That is exactly what using a list does.)
15530 <P>
15532 Some messages may be "bounced" to you, and will
15533 have a "Resent-To:" header line.
15534 If the message contains a Resent-To: line
15535 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15536 Alpine will look for
15537 matches to your "To patterns" there, and <EM>NOT</EM> in
15538 the original To: line.
15539 <P>
15541 When entering a pattern, you may choose an address from your address book
15542 with the "T" command.
15543 <P>
15545 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15546 "!" "toggle NOT" command.
15547 This changes the meaning of the To pattern so that it has the opposite meaning.
15548 It will be considered a match if there are no matches between the
15549 addresses in the To: line and the list of To patterns.
15550 <P>
15551 Don't make the mistake of putting the "!" in the data field for
15552 the pattern.
15553 For example, if you type the characters "!frizzle" into the To
15554 pattern, the pattern will look like:
15555 <P>
15556 <PRE>
15557 To pattern = !frizzle
15558 </PRE>
15559 <P>
15560 This means you want to match the 8 character sequence "!frizzle".
15561 In order to match messages that do not have "frizzle" in
15562 their To field, first type the characters "frizzle" followed
15563 by carriage return for the value of the To pattern, then negate it
15564 by typing the "!" command.
15565 It should end up looking like
15566 <P>
15567 <PRE>
15568 ! To pattern = frizzle
15569 </PRE>
15570 <P>
15572 You are not limited to using the six standard header patterns that are
15573 normally shown (To, From, Sender, Cc, News, and Subject).
15574 You may add any other header to a Pattern by
15575 using the "eXtraHdr" command to specify a different
15576 message header line; and then the Add or Change command to fill in
15577 a pattern for the new header line, just like you would for a standard header.
15578 <P>
15579 A technicality: Since comma is the character used to separate multiple
15580 values in a pattern field, you have to escape comma with a backslash (\) if
15581 you want to include a literal comma in the field.
15582 In other words, if you type a backslash followed by a comma it will
15583 be interpreted as a comma by Alpine, instead of as a separator between
15584 pattern values.
15585 All other backslashes are literal backslashes and should not be escaped.
15586 <P>
15587 Look "<A HREF="h_rule_patterns">here</A>"
15588 for more information on Patterns.
15589 <P>
15590 Look <A HREF="h_edit_nav_cmds">here</A>
15591 to see the available Editing and Navigation commands.
15592 <P>
15593 <End of help on this topic>
15594 </BODY>
15595 </HTML>
15596 ======= h_config_other_topat =======
15597 <HTML>
15598 <HEAD>
15599 <TITLE>"To:" Pattern Explained</TITLE>
15600 </HEAD>
15601 <BODY>
15602 <H1>"To:" Pattern Explained</H1>
15604 For some of the OTHER RULES actions, there is no message that is being
15605 compared against.
15606 If that is the case, then only the Current Folder Type is checked.
15607 In particular, this To pattern is ignored.
15608 Actions that fall into this category include both
15609 Sort Order and Index Format.
15610 <P>
15611 A technicality: Since comma is the character used to separate multiple
15612 values in a pattern field, you have to escape comma with a backslash (\) if
15613 you want to include a literal comma in the field.
15614 In other words, if you type a backslash followed by a comma it will
15615 be interpreted as a comma by Alpine, instead of as a separator between
15616 pattern values.
15617 All other backslashes are literal backslashes and should not be escaped.
15618 <P>
15619 Look "<A HREF="h_rule_patterns">here</A>"
15620 for more information on Patterns.
15621 <P>
15622 Look <A HREF="h_edit_nav_cmds">here</A>
15623 to see the available Editing and Navigation commands.
15624 <P>
15625 <End of help on this topic>
15626 </BODY>
15627 </HTML>
15628 ======= h_config_filt_topat =======
15629 <HTML>
15630 <HEAD>
15631 <TITLE>"To:" Pattern Explained</TITLE>
15632 </HEAD>
15633 <BODY>
15634 <H1>"To:" Pattern Explained</H1>
15636 Any text you enter as the "To pattern"
15637 will be compared to the recipients from the To: line of
15638 messages when Alpine opens folders.
15639 When the text you entered matches
15640 all or part of the To: line of a message, then the Filter Action you have
15641 specified will be carried out.
15642 (Any other non-blank parts of the Pattern must match, too.)
15643 <P>
15645 You may enter a complete email address, part of an address, or a
15646 list of addresses or partial addresses.
15647 For example:
15648 <P>
15650 <PRE>
15651 To pattern = friend@public.com
15652 To pattern = rated.net
15653 To pattern = xxx@adults.com
15654 admin@msn.com
15655 fool@motleyfool.com
15656 </PRE>
15658 <P>
15659 Each of those are valid To patterns.
15660 <P>
15662 Messages match those patterns if any of the
15663 addresses in the To: line of the message contains the pattern.
15664 If the pattern is a list of patterns
15665 (like the last example above) then it is a match if any of the patterns in
15666 the list match any of the addresses in the To: line.
15667 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15668 present for a match.
15669 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15670 address2 must be present.
15671 That is exactly what using a list does.)
15672 <P>
15674 Some messages may be "bounced" to you, and will
15675 have a "Resent-To:" header line.
15676 If the message contains a Resent-To: line
15677 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15678 Alpine will look for
15679 matches to your "To patterns" there, and <EM>NOT</EM> in
15680 the original To: line.
15681 <P>
15683 When entering a pattern, you may choose an address from your address book
15684 with the "T" command.
15685 <P>
15687 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15688 "!" "toggle NOT" command.
15689 This changes the meaning of the To pattern so that it has the opposite meaning.
15690 It will be considered a match if there are no matches between the
15691 addresses in the To: line and the list of To patterns.
15692 <P>
15693 Don't make the mistake of putting the "!" in the data field for
15694 the pattern.
15695 For example, if you type the characters "!frizzle" into the To
15696 pattern, the pattern will look like:
15697 <P>
15698 <PRE>
15699 To pattern = !frizzle
15700 </PRE>
15701 <P>
15702 This means you want to match the 8 character sequence "!frizzle".
15703 In order to match messages that do not have "frizzle" in
15704 their To field, first type the characters "frizzle" followed
15705 by carriage return for the value of the To pattern, then negate it
15706 by typing the "!" command.
15707 It should end up looking like
15708 <P>
15709 <PRE>
15710 ! To pattern = frizzle
15711 </PRE>
15712 <P>
15714 You are not limited to using the six standard header patterns that are
15715 normally shown (To, From, Sender, Cc, News, and Subject).
15716 You may add any other header to a Pattern by
15717 using the "eXtraHdr" command to specify a different
15718 message header line; and then the Add or Change command to fill in
15719 a pattern for the new header line, just like you would for a standard header.
15720 <P>
15721 A technicality: Since comma is the character used to separate multiple
15722 values in a pattern field, you have to escape comma with a backslash (\) if
15723 you want to include a literal comma in the field.
15724 In other words, if you type a backslash followed by a comma it will
15725 be interpreted as a comma by Alpine, instead of as a separator between
15726 pattern values.
15727 All other backslashes are literal backslashes and should not be escaped.
15728 <P>
15729 Look "<A HREF="h_rule_patterns">here</A>"
15730 for more information on Patterns.
15731 <P>
15732 Look <A HREF="h_edit_nav_cmds">here</A>
15733 to see the available Editing and Navigation commands.
15734 <P>
15735 <End of help on this topic>
15736 </BODY>
15737 </HTML>
15738 ======= h_config_role_topat =======
15739 <HTML>
15740 <HEAD>
15741 <TITLE>"To:" Pattern Explained</TITLE>
15742 </HEAD>
15743 <BODY>
15744 <H1>"To:" Pattern Explained</H1>
15746 Any text you enter as the "To pattern"
15747 will be compared to the recipients from the To: line of
15748 the message being replied to or forwarded.
15749 (Any other non-blank parts of the Pattern must match, too.)
15750 In the case of the Compose command, this pattern and the other header
15751 patterns are ignored.
15752 <P>
15754 You may enter a complete email address, part of an address, or a
15755 list of addresses or partial addresses.
15756 For example:
15757 <P>
15759 <PRE>
15760 To pattern = friend@public.com
15761 To pattern = rated.net
15762 To pattern = xxx@adults.com
15763 admin@msn.com
15764 fool@motleyfool.com
15765 </PRE>
15767 <P>
15768 Each of those are valid To patterns.
15769 <P>
15771 Messages match those patterns if any of the
15772 addresses in the To: line of the message contains the pattern.
15773 If the pattern is a list of patterns
15774 (like the last example above) then it is a match if any of the patterns in
15775 the list match any of the addresses in the To: line.
15776 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15777 present for a match.
15778 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15779 address2 must be present.
15780 That is exactly what using a list does.)
15781 <P>
15783 Some messages may be "bounced" to you, and will
15784 have a "Resent-To:" header line.
15785 If the message contains a Resent-To: line
15786 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15787 Alpine will look for
15788 matches to your "To patterns" there, and <EM>NOT</EM> in
15789 the original To: line.
15790 <P>
15792 When entering a pattern, you may choose an address from your address book
15793 with the "T" command.
15794 <P>
15796 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15797 "!" "toggle NOT" command.
15798 This changes the meaning of the To pattern so that it has the opposite meaning.
15799 It will be considered a match if there are no matches between the
15800 addresses in the To: line and the list of To patterns.
15801 <P>
15802 Don't make the mistake of putting the "!" in the data field for
15803 the pattern.
15804 For example, if you type the characters "!frizzle" into the To
15805 pattern, the pattern will look like:
15806 <P>
15807 <PRE>
15808 To pattern = !frizzle
15809 </PRE>
15810 <P>
15811 This means you want to match the 8 character sequence "!frizzle".
15812 In order to match messages that do not have "frizzle" in
15813 their To field, first type the characters "frizzle" followed
15814 by carriage return for the value of the To pattern, then negate it
15815 by typing the "!" command.
15816 It should end up looking like
15817 <P>
15818 <PRE>
15819 ! To pattern = frizzle
15820 </PRE>
15821 <P>
15823 You are not limited to using the six standard header patterns that are
15824 normally shown (To, From, Sender, Cc, News, and Subject).
15825 You may add any other header to a Pattern by
15826 using the "eXtraHdr" command to specify a different
15827 message header line; and then the Add or Change command to fill in
15828 a pattern for the new header line, just like you would for a standard header.
15829 <P>
15830 A technicality: Since comma is the character used to separate multiple
15831 values in a pattern field, you have to escape comma with a backslash (\) if
15832 you want to include a literal comma in the field.
15833 In other words, if you type a backslash followed by a comma it will
15834 be interpreted as a comma by Alpine, instead of as a separator between
15835 pattern values.
15836 All other backslashes are literal backslashes and should not be escaped.
15837 <P>
15838 Look "<A HREF="h_rule_patterns">here</A>"
15839 for more information on Patterns.
15840 <P>
15841 Look <A HREF="h_edit_nav_cmds">here</A>
15842 to see the available Editing and Navigation commands.
15843 <P>
15844 <End of help on this topic>
15845 </BODY>
15846 </HTML>
15847 ======= h_config_role_frompat =======
15848 <HTML>
15849 <HEAD>
15850 <TITLE>"From:" Pattern Explained</TITLE>
15851 </HEAD>
15852 <BODY>
15853 <H1>"From:" Pattern Explained</H1>
15855 This is just like the "To pattern" except that it is compared with
15856 the address in the From: line of the message
15857 instead of the addresses from the To: line.
15858 See the help for the To pattern for more information on header patterns.
15859 <P>
15860 Look "<A HREF="h_rule_patterns">here</A>"
15861 for more information on Patterns.
15862 <P>
15863 Look <A HREF="h_edit_nav_cmds">here</A>
15864 to see the available Editing and Navigation commands.
15865 <P>
15866 <End of help on this topic>
15867 </BODY>
15868 </HTML>
15869 ======= h_config_role_senderpat =======
15870 <HTML>
15871 <HEAD>
15872 <TITLE>"Sender:" Pattern Explained</TITLE>
15873 </HEAD>
15874 <BODY>
15875 <H1>"Sender:" Pattern Explained</H1>
15877 This is just like the "To pattern" except that it is compared with
15878 the address from the Sender: line of the message
15879 instead of the addresses from the To: line.
15880 See the help for the To pattern for more information on header patterns.
15881 <P>
15882 Look "<A HREF="h_rule_patterns">here</A>"
15883 for more information on Patterns.
15884 <P>
15885 Look <A HREF="h_edit_nav_cmds">here</A>
15886 to see the available Editing and Navigation commands.
15887 <P>
15888 <End of help on this topic>
15889 </BODY>
15890 </HTML>
15891 ======= h_config_role_ccpat =======
15892 <HTML>
15893 <HEAD>
15894 <TITLE>"Cc:" Pattern Explained</TITLE>
15895 </HEAD>
15896 <BODY>
15897 <H1>"Cc:" Pattern Explained</H1>
15899 This is just like the "To pattern" except that it is compared with
15900 the addresses from the Cc: line of the message
15901 instead of the addresses from the To: line.
15902 See the help for the To pattern for more information on header patterns.
15903 <P>
15904 Look "<A HREF="h_rule_patterns">here</A>"
15905 for more information on Patterns.
15906 <P>
15907 Look <A HREF="h_edit_nav_cmds">here</A>
15908 to see the available Editing and Navigation commands.
15909 <P>
15910 <End of help on this topic>
15911 </BODY>
15912 </HTML>
15913 ======= h_config_role_recippat =======
15914 <HTML>
15915 <HEAD>
15916 <TITLE>Recipient Pattern Explained</TITLE>
15917 </HEAD>
15918 <BODY>
15919 <H1>Recipient Pattern Explained</H1>
15921 This is just like the "To pattern" except that it is compared with
15922 the addresses from both the To: line and the Cc: line of the
15923 message instead of just the addresses from the To: line.
15924 In other words, it is considered a match if the pattern matches
15925 <EM>EITHER</EM> an address in the To: line <EM>OR</EM> an address
15926 in the Cc: line.
15927 (Notice that defining the Recipient pattern does not have the same
15928 effect as defining both the To and Cc patterns.
15929 Recipient is To <EM>OR</EM> Cc; not To <EM>AND</EM> Cc.
15930 It is equivalent to having two different rules;
15931 one with a To pattern and the other with the same Cc pattern.)
15932 <P>
15933 A technicality: Since comma is the character used to separate multiple
15934 values in a pattern field, you have to escape comma with a backslash (\) if
15935 you want to include a literal comma in the field.
15936 In other words, if you type a backslash followed by a comma it will
15937 be interpreted as a comma by Alpine, instead of as a separator between
15938 pattern values.
15939 All other backslashes are literal backslashes and should not be escaped.
15940 <P>
15941 Look "<A HREF="h_rule_patterns">here</A>"
15942 for more information on Patterns.
15943 <P>
15944 Look <A HREF="h_edit_nav_cmds">here</A>
15945 to see the available Editing and Navigation commands.
15946 <P>
15947 <End of help on this topic>
15948 </BODY>
15949 </HTML>
15950 ======= h_config_role_particpat =======
15951 <HTML>
15952 <HEAD>
15953 <TITLE>Participant Pattern Explained</TITLE>
15954 </HEAD>
15955 <BODY>
15956 <H1>Participant Pattern Explained</H1>
15958 This is just like the "To pattern" except that it is compared with
15959 the addresses from the From: line, the To: line, and the Cc: line of the
15960 message instead of just the addresses from the To: line.
15961 In other words, it is considered a match if the pattern matches
15962 <EM>EITHER</EM> an address in the From: line, <EM>OR</EM> an address
15963 in the To: line, <EM>OR</EM> an address in the Cc: line.
15964 (Notice that defining the Participant pattern does not have the same
15965 effect as defining all of the From, To, and Cc patterns.
15966 Participant is From <EM>OR</EM> To <EM>OR</EM> Cc; not
15967 From <EM>AND</EM> To <EM>AND</EM> Cc.
15968 It is equivalent to having three different rules;
15969 one with a From pattern, another with the same To pattern, and a third with
15970 the same Cc pattern.)
15971 <P>
15972 A technicality: Since comma is the character used to separate multiple
15973 values in a pattern field, you have to escape comma with a backslash (\) if
15974 you want to include a literal comma in the field.
15975 In other words, if you type a backslash followed by a comma it will
15976 be interpreted as a comma by Alpine, instead of as a separator between
15977 pattern values.
15978 All other backslashes are literal backslashes and should not be escaped.
15979 <P>
15980 Look "<A HREF="h_rule_patterns">here</A>"
15981 for more information on Patterns.
15982 <P>
15983 Look <A HREF="h_edit_nav_cmds">here</A>
15984 to see the available Editing and Navigation commands.
15985 <P>
15986 <End of help on this topic>
15987 </BODY>
15988 </HTML>
15989 ======= h_config_role_newspat =======
15990 <HTML>
15991 <HEAD>
15992 <TITLE>News Pattern Explained</TITLE>
15993 </HEAD>
15994 <BODY>
15995 <H1>News Pattern Explained</H1>
15997 If this pattern is non-blank, then for this rule to be considered a
15998 match, at least one of the newsgroups from
15999 the Newsgroups line of the message must match this pattern.
16000 If this pattern is a list of patterns, then at least one of the
16001 newsgroups must match at least one of the patterns.
16002 (Any other non-blank parts of the Pattern must match, too.)
16003 <P>
16004 It is possible to add a <EM>NOT</EM> to the News Pattern meaning with the
16005 "!" "toggle NOT" command.
16006 This changes the meaning of the News pattern so that it has the opposite meaning.
16007 It will be considered a match if there are no matches between the
16008 addresses in the Newsgroups: line and the list of News patterns.
16009 <P>
16010 Don't make the mistake of putting the "!" in the data field for
16011 the pattern.
16012 For example, if you type the characters "!frizzle" into the News
16013 pattern, the pattern will look like:
16014 <P>
16015 <PRE>
16016 News pattern = !frizzle
16017 </PRE>
16018 <P>
16019 This means you want to match the 8 character sequence "!frizzle".
16020 In order to match messages that do not have "frizzle" in
16021 their Newsgroups header, first type the characters "frizzle" followed
16022 by carriage return for the value of the News pattern, then negate it
16023 by typing the "!" command.
16024 It should end up looking like
16025 <P>
16026 <PRE>
16027 ! News pattern = frizzle
16028 </PRE>
16029 <P>
16030 A technicality: Since comma is the character used to separate multiple
16031 values in a pattern field, you have to escape comma with a backslash (\) if
16032 you want to include a literal comma in the field.
16033 In other words, if you type a backslash followed by a comma it will
16034 be interpreted as a comma by Alpine, instead of as a separator between
16035 pattern values.
16036 All other backslashes are literal backslashes and should not be escaped.
16037 <P>
16039 Look "<A HREF="h_rule_patterns">here</A>"
16040 for more information on Patterns.
16041 <P>
16042 Look <A HREF="h_edit_nav_cmds">here</A>
16043 to see the available Editing and Navigation commands.
16044 <P>
16045 <End of help on this topic>
16046 </BODY>
16047 </HTML>
16048 ======= h_config_role_subjpat =======
16049 <HTML>
16050 <HEAD>
16051 <TITLE>"Subject:" Pattern Explained</TITLE>
16052 </HEAD>
16053 <BODY>
16054 <H1>"Subject:" Pattern Explained</H1>
16056 This is similar to the other parts of the Pattern.
16057 It is compared with
16058 the contents from the Subject of the message.
16059 <P>
16060 Look "<A HREF="h_rule_patterns">here</A>"
16061 for more information on Patterns.
16062 <P>
16063 It is possible to add a <EM>NOT</EM> to the Subject Pattern meaning with the
16064 "!" "toggle NOT" command.
16065 This changes the meaning of the Subject pattern so that it has the opposite meaning.
16066 It will be considered a match if there are no matches between the
16067 text in the Subject: line and the list of Subject patterns.
16068 <P>
16070 If you wish to have a header pattern that is not one of the six standard
16071 header patterns, you may add it with the "eXtraHdr" command.
16072 <P>
16073 A technicality: Since comma is the character used to separate multiple
16074 values in a pattern field, you have to escape comma with a backslash (\) if
16075 you want to include a literal comma in the field.
16076 In other words, if you type a backslash followed by a comma it will
16077 be interpreted as a comma by Alpine, instead of as a separator between
16078 pattern values.
16079 All other backslashes are literal backslashes and should not be escaped.
16080 <P>
16081 Look <A HREF="h_edit_nav_cmds">here</A>
16082 to see the available Editing and Navigation commands.
16083 <P>
16084 <End of help on this topic>
16085 </BODY>
16086 </HTML>
16087 ======= h_config_role_alltextpat =======
16088 <HTML>
16089 <HEAD>
16090 <TITLE>AllText Pattern Explained</TITLE>
16091 </HEAD>
16092 <BODY>
16093 <H1>AllText Pattern Explained</H1>
16095 This is similar to the header patterns.
16096 Instead of comparing with text in a particular header field it
16097 is compared with all of the text in the message header and body.
16098 <P>
16099 It is possible to add a <EM>NOT</EM> to the AllText Pattern meaning with the
16100 "!" "toggle NOT" command.
16101 This changes the meaning of the AllText pattern so that it has the opposite meaning.
16102 It will be considered a match if there are no matches between the
16103 text of the message and the list of AllText patterns.
16104 <P>
16105 Don't make the mistake of putting the "!" in the data field for
16106 the pattern.
16107 For example, if you type the characters "!frizzle" into the AllText
16108 pattern, the pattern will look like:
16109 <P>
16110 <PRE>
16111 AllText pattern = !frizzle
16112 </PRE>
16113 <P>
16114 This means you want to match the 8 character sequence "!frizzle".
16115 In order to match messages that do not have "frizzle" in
16116 the text of the message, first type the characters "frizzle" followed
16117 by carriage return for the value of the AllText pattern, then negate it
16118 by typing the "!" command.
16119 It should end up looking like
16120 <P>
16121 <PRE>
16122 ! AllText pattern = frizzle
16123 </PRE>
16124 <P>
16125 It is possible that you may notice degraded performance when using
16126 AllText Patterns.
16127 <P>
16128 A technicality: Since comma is the character used to separate multiple
16129 values in a pattern field, you have to escape comma with a backslash (\) if
16130 you want to include a literal comma in the field.
16131 In other words, if you type a backslash followed by a comma it will
16132 be interpreted as a comma by Alpine, instead of as a separator between
16133 pattern values.
16134 All other backslashes are literal backslashes and should not be escaped.
16135 <P>
16136 Look "<A HREF="h_rule_patterns">here</A>"
16137 for more information on Patterns.
16138 <P>
16139 Look <A HREF="h_edit_nav_cmds">here</A>
16140 to see the available Editing and Navigation commands.
16141 <P>
16142 <End of help on this topic>
16143 </BODY>
16144 </HTML>
16145 ======= h_config_role_bodytextpat =======
16146 <HTML>
16147 <HEAD>
16148 <TITLE>BodyText Pattern Explained</TITLE>
16149 </HEAD>
16150 <BODY>
16151 <H1>BodyText Pattern Explained</H1>
16153 This is similar to the header patterns.
16154 Instead of comparing with text in a particular header field it
16155 is compared with all of the text in the message body.
16156 <P>
16157 It is possible to add a <EM>NOT</EM> to the BodyText Pattern meaning with the
16158 "!" "toggle NOT" command.
16159 This changes the meaning of the BodyText pattern so that it has the opposite meaning.
16160 It will be considered a match if there are no matches between the
16161 text of the body of the message and the list of BodyText patterns.
16162 <P>
16163 Don't make the mistake of putting the "!" in the data field for
16164 the pattern.
16165 For example, if you type the characters "!frizzle" into the BodyText
16166 pattern, the pattern will look like:
16167 <P>
16168 <PRE>
16169 BdyText pattern = !frizzle
16170 </PRE>
16171 <P>
16172 This means you want to match the 8 character sequence "!frizzle".
16173 In order to match messages that do not have "frizzle" in
16174 their BodyText, first type the characters "frizzle" followed
16175 by carriage return for the value of the BodyText pattern, then negate it
16176 by typing the "!" command.
16177 It should end up looking like
16178 <P>
16179 <PRE>
16180 ! BodyText pattern = frizzle
16181 </PRE>
16182 <P>
16183 It is possible that you may notice degraded performance when using
16184 BodyText Patterns.
16185 <P>
16186 A technicality: Since comma is the character used to separate multiple
16187 values in a pattern field, you have to escape comma with a backslash (\) if
16188 you want to include a literal comma in the field.
16189 In other words, if you type a backslash followed by a comma it will
16190 be interpreted as a comma by Alpine, instead of as a separator between
16191 pattern values.
16192 All other backslashes are literal backslashes and should not be escaped.
16193 <P>
16194 Look "<A HREF="h_rule_patterns">here</A>"
16195 for more information on Patterns.
16196 <P>
16197 Look <A HREF="h_edit_nav_cmds">here</A>
16198 to see the available Editing and Navigation commands.
16199 <P>
16200 <End of help on this topic>
16201 </BODY>
16202 </HTML>
16203 ======= h_config_role_charsetpat =======
16204 <HTML>
16205 <HEAD>
16206 <TITLE>Character Set Pattern Explained</TITLE>
16207 </HEAD>
16208 <BODY>
16209 <H1>Character Set Pattern Explained</H1>
16211 A message may use one or more character sets.
16212 This part of the Pattern matches messages that make use of
16213 certain specified character sets.
16214 It will be considered a match if a message uses any of the character
16215 sets in the list you give here.
16217 <P>
16218 When filling in a value for this field, you may use
16219 the "T" command, which presents you with a large list of
16220 possible character sets to choose from.
16221 You may also just type in the name of a character set, and it need not
16222 be one that Alpine knows about.
16224 <P>
16225 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
16226 GB2312) you may also use some shorthand names that Alpine provides.
16227 These names are more understandable shorthand names for sets of
16228 character set names.
16229 Two examples are "Cyrillic" and "Greek".
16230 Selecting one of these shorthand names is equivalent to selecting all of
16231 the character sets that make up the set.
16232 You can see all of these shorthand names and the lists of character sets
16233 they stand for by typing the "T" command.
16235 <P>
16236 For the purposes of this Pattern,
16237 Alpine will search through a message for all of the text parts and
16238 collect the character sets declared for each part.
16239 It will also look in the Subject line for a character set used there.
16240 Alpine does not actually look at the text of the message or the text
16241 of the Subject to determine if a declared character set is actually
16242 used, it looks only at the declarations themselves in the MIME part headers
16243 and in the Subject.
16245 <P>
16246 It is possible to add a <EM>NOT</EM> to the Character Set Pattern meaning with the
16247 "!" "toggle NOT" command.
16248 This changes the meaning of the Character Set pattern so that
16249 it has the opposite meaning.
16250 It will be considered a match if none of the character sets in the
16251 list are used in a message.
16252 <P>
16253 Don't make the mistake of putting the "!" in the data field for
16254 the pattern.
16255 For example, if you type the characters "!GB2312" into the
16256 Character Set pattern, the pattern will look like:
16257 <P>
16258 <PRE>
16259 Charset pattern = !GB2312
16260 </PRE>
16261 <P>
16262 This means you want to match the 7 character sequence "!GB2312".
16263 In order to match messages that do not have the
16264 character set "GB2312"
16265 set, first type the characters "GB2312" followed
16266 by carriage return for the value of the Character Set pattern, then negate it
16267 by typing the "!" command.
16268 It should end up looking like
16269 <P>
16270 <PRE>
16271 ! Charset pattern = GB2312
16272 </PRE>
16273 <P>
16274 A technicality: Since comma is the character used to separate multiple
16275 values in a pattern field, you have to escape comma with a backslash (\) if
16276 you want to include a literal comma in the field.
16277 In other words, if you type a backslash followed by a comma it will
16278 be interpreted as a comma by Alpine, instead of as a separator between
16279 pattern values.
16280 All other backslashes are literal backslashes and should not be escaped.
16281 <P>
16282 Look "<A HREF="h_rule_patterns">here</A>"
16283 for more information on Patterns.
16284 <P>
16285 Look <A HREF="h_edit_nav_cmds">here</A>
16286 to see the available Editing and Navigation commands.
16287 <P>
16288 <End of help on this topic>
16289 </BODY>
16290 </HTML>
16291 ======= h_config_role_keywordpat =======
16292 <HTML>
16293 <HEAD>
16294 <TITLE>Keyword Pattern Explained</TITLE>
16295 </HEAD>
16296 <BODY>
16297 <H1>Keyword Pattern Explained</H1>
16299 A folder may have user-defined keywords.
16300 These are similar to the Important flag, which the user may set using the
16301 Flag command.
16302 The difference is that the Important flag is always present for each folder.
16303 User-defined keywords are picked by the user.
16304 You may add new keywords by defining them in the
16305 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
16306 After you have added a potential keyword with the <!--#echo var="VAR_keywords"--> option,
16307 the Flag command may be used to set or clear the keyword on individual messages.
16308 If you have given a keyword a nickname when configuring it,
16309 that nickname may be used instead of the actual keyword.
16311 <P>
16312 When filling in a value for this field, it may be easiest to use
16313 the "T" command, which presents you with a list of the keywords
16314 you have defined to choose from.
16316 <P>
16317 This part of the Pattern matches messages with certain keywords set.
16318 It will be considered a match if a message has any of the keywords in the
16319 list set.
16320 A keyword that you have not defined using the
16321 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16322 will not be a match.
16324 <P>
16325 It is possible to add a <EM>NOT</EM> to the Keyword Pattern meaning with the
16326 "!" "toggle NOT" command.
16327 This changes the meaning of the Keyword pattern so that it has the opposite meaning.
16328 It will be considered a match if none of the keywords in the list are set
16329 for a message.
16330 A keyword that you have not defined using the
16331 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16332 will not be a match, so a <EM>NOT</EM> of that keyword does match.
16333 <P>
16334 Don't make the mistake of putting the "!" in the data field for
16335 the pattern.
16336 For example, if you type the characters "!frizzle" into the Keyword
16337 pattern, the pattern will look like:
16338 <P>
16339 <PRE>
16340 Keyword pattern = !frizzle
16341 </PRE>
16342 <P>
16343 This means you want to match the 8 character sequence "!frizzle".
16344 In order to match messages that do not have the keyword "frizzle"
16345 set, first type the characters "frizzle" followed
16346 by carriage return for the value of the Keyword pattern, then negate it
16347 by typing the "!" command.
16348 It should end up looking like
16349 <P>
16350 <PRE>
16351 ! Keyword pattern = frizzle
16352 </PRE>
16353 <P>
16354 A technicality: Since comma is the character used to separate multiple
16355 values in a pattern field, you have to escape comma with a backslash (\) if
16356 you want to include a literal comma in the field.
16357 In other words, if you type a backslash followed by a comma it will
16358 be interpreted as a comma by Alpine, instead of as a separator between
16359 pattern values.
16360 All other backslashes are literal backslashes and should not be escaped.
16361 <P>
16362 Look "<A HREF="h_rule_patterns">here</A>"
16363 for more information on Patterns.
16364 <P>
16365 Look <A HREF="h_edit_nav_cmds">here</A>
16366 to see the available Editing and Navigation commands.
16367 <P>
16368 <End of help on this topic>
16369 </BODY>
16370 </HTML>
16371 ======= h_config_role_arbpat =======
16372 <HTML>
16373 <HEAD>
16374 <TITLE>Extra Header Patterns Explained</TITLE>
16375 </HEAD>
16376 <BODY>
16377 <H1>Extra Header Patterns Explained</H1>
16379 The header patterns that come after the Participant pattern but before the
16380 AllText pattern are extra header patterns that you have added to a rule's
16381 Pattern. These are just like the other header patterns except that
16382 the contents of the particular header listed on the left hand side will
16383 be used for comparisons.
16384 <P>
16385 The "eXtraHdr" command may be used to add more of these
16386 header patterns to the rule you are editing.
16387 <P>
16388 The "RemoveHdr" command may be used to delete the highlighted
16389 extra header pattern from the rule you are editing.
16390 <P>
16391 It is possible to add a <EM>NOT</EM> to the Extra Header Pattern meaning with the
16392 "!" "toggle NOT" command.
16393 This changes the meaning of the pattern so that it has the opposite meaning.
16394 It will be considered a match if there are no matches between the
16395 text in the header line and the list of patterns.
16396 <P>
16397 Don't make the mistake of putting the "!" in the data field for
16398 the pattern.
16399 For example, if you type the characters "!frizzle" into the
16400 pattern, the pattern will look like:
16401 <P>
16402 <PRE>
16403 Xyz pattern = !frizzle
16404 </PRE>
16405 <P>
16406 This means you want to match the 8 character sequence "!frizzle".
16407 In order to match messages that do not have "frizzle" in
16408 their Xyz field, first type the characters "frizzle" followed
16409 by carriage return for the value of the pattern, then negate it
16410 by typing the "!" command.
16411 It should end up looking like
16412 <P>
16413 <PRE>
16414 ! Xyz pattern = frizzle
16415 </PRE>
16417 <P>
16418 A technicality: Since comma is the character used to separate multiple
16419 values in a pattern field, you have to escape comma with a backslash (\) if
16420 you want to include a literal comma in the field.
16421 In other words, if you type a backslash followed by a comma it will
16422 be interpreted as a comma by Alpine, instead of as a separator between
16423 pattern values.
16424 All other backslashes are literal backslashes and should not be escaped.
16425 <P>
16426 Look "<A HREF="h_rule_patterns">here</A>"
16427 for more information on Patterns.
16428 <P>
16429 Look <A HREF="h_edit_nav_cmds">here</A>
16430 to see the available Editing and Navigation commands.
16431 <P>
16432 <End of help on this topic>
16433 </BODY>
16434 </HTML>
16435 ======= h_config_role_cat_cmd =======
16436 <HTML>
16437 <HEAD>
16438 <TITLE>Categorizer Command Explained</TITLE>
16439 </HEAD>
16440 <BODY>
16441 <H1>Categorizer Command Explained</H1>
16443 This is a command that is run with its standard input set to the message
16444 being checked and its standard output discarded.
16445 The full directory path should be specified.
16446 The command will be run and then its exit status will be checked against
16447 the Exit Status Interval, which defaults to just the value zero.
16448 If the exit status of the command falls in the interval, it is considered
16449 a match, otherwise it is not a match.
16450 <P>
16452 This option may actually be a list of commands.
16453 The first one that exists and is executable is used.
16454 That makes it possible to use the same configuration with Unix Alpine and
16455 PC-Alpine.
16456 <P>
16458 If none of the commands in the list exists and is executable then the rule
16459 is <EM>not</EM> a match.
16460 If it is possible that the command may not exist, you should be careful
16461 to structure your rules so that nothing destructive
16462 happens when the command does not exist.
16463 For example, you might have a filter that filters away spam when there is
16464 a match but does nothing when there is not a match.
16465 That would cause no harm if the command didn't exist.
16466 However, if you have a filter that filters away spam when there is not
16467 a match and keeps it when there is a match, that would filter everything
16468 if the categorizer command didn't exist.
16469 <P>
16470 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
16471 setup for the bogofilter filter.
16473 <P>
16474 Look "<A HREF="h_rule_patterns">here</A>"
16475 for more information on Patterns.
16476 <P>
16477 Look <A HREF="h_edit_nav_cmds">here</A>
16478 to see the available Editing and Navigation commands.
16479 <P>
16480 <End of help on this topic>
16481 </BODY>
16482 </HTML>
16483 ======= h_config_role_cat_cmd_example =======
16484 <HTML>
16485 <HEAD>
16486 <TITLE>Categorizer Command Example</TITLE>
16487 </HEAD>
16488 <BODY>
16489 <H1>Categorizer Command Example</H1>
16491 Bogofilter
16492 (<A HREF="http://bogofilter.sourceforge.net/">http://bogofilter.sourceforge.net/</A>)
16493 is a mail filter that attempts to classify mail as spam or
16494 non-spam using statistical analysis of the message content.
16495 When run with no arguments and a message as standard input, it exits with
16496 exit status 0 if it thinks a message is spam and 1 if it thinks
16497 it is not spam.
16498 To use bogofilter as your Categorizer Command you would simply set Command to
16499 the pathname of the bogofilter program.
16500 For example,
16501 <P>
16502 <CENTER><SAMP>Command = /usr/local/bin/bogofilter</SAMP></CENTER>
16503 <P>
16504 Exit status of zero is what you are interested in, so you'd set the
16505 Exit Status Interval to
16506 <P>
16507 <CENTER><SAMP>Exit Status Interval = (0,0)</SAMP></CENTER>
16508 <P>
16510 In order to prevent downloading an entire huge message to check for spam, you
16511 might want to set the Character Limit to a few thousand characters (the
16512 assumption being that the spam will reveal itself in those characters)
16513 <P>
16514 <CENTER><SAMP>Character Limit = 50000</SAMP></CENTER>
16515 <P>
16517 You would probably use bogofilter in an Alpine Filter Rule, and have the action
16518 be to move the message to a spam folder.
16519 It would usually be wise to also check the "Message is Recent"
16520 part of the rule so that messages are only checked when they first arrive,
16521 and to restrict the Current Folder Type to just your INBOX.
16522 The reason for checking only Recent messages is to save the time it takes
16523 to run bogofilter on each message.
16524 As an experiment, you might start out by using this in an Indexcolor Rule
16525 instead of a Filter Rule.
16526 In that case, you probably wouldn't check the Recent checkbox.
16527 <P>
16528 The use described above assumes that you are somehow maintaining bogofilter's
16529 database of words associated with spam and non-spam messages.
16530 One way to start your database would be to select a bunch of spam messages
16531 in Alpine (you might Save spam messages to a special folder or use Alpine's
16532 Select command to select several) and then Apply
16533 (<A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>)
16534 a pipe command to the spam messages.
16535 For example, you could have a shell script or an alias
16536 called <EM>this_is_spam</EM>, which would simply be the command
16537 <P>
16538 <CENTER><SAMP>bogofilter -s</SAMP></CENTER>
16539 <P>
16541 It is probably best to use the pipe command's Raw Text, With Delimiter,
16542 and Free Output options,
16543 which are at the bottom of the screen when you type the pipe command.
16544 That's because bogofilter expects the raw message as input, and uses
16545 the Delimiters to tell when a new message starts.
16546 You would not need to use a separate pipe for each message, because
16547 bogofilter can handle multiple messages at once.
16548 <P>
16549 Similarly, you would select a group of non-spam messages
16550 and run them through a <EM>this_is_nonspam</EM> script
16551 that was something like
16552 <P>
16553 <CENTER><SAMP>bogofilter -n</SAMP></CENTER>
16554 <P>
16556 For the more adventurous, the next step might be to automate the upkeep of
16557 the bogofilter database.
16558 It might make more sense to have bogofilter be part of the delivery process,
16559 but it is also possible to do it entirely from within Alpine.
16560 Instead of using just plain "bogofilter" as the Categorizer Command,
16561 the "-u" argument will cause bogofilter to update the database.
16562 <P>
16563 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16564 <P>
16565 You'd want a couple more aliases or shell scripts called something like
16566 <EM>change_to_spam</EM>
16567 <P>
16568 <CENTER><SAMP>bogofilter -Ns</SAMP></CENTER>
16569 <P>
16570 and
16571 <EM>change_to_nonspam</EM>
16572 <P>
16573 <CENTER><SAMP>bogofilter -Sn</SAMP></CENTER>
16574 <P>
16575 When you run across a message in your INBOX that should have been
16576 classified as spam you would pipe it to the change_to_spam script, and
16577 when you run across a message in your spam folder that should have been
16578 left in your INBOX you would pipe it through change_to_nonspam.
16580 <P>
16581 There is a technical problem with this approach.
16582 Alpine may check your filters more than once.
16583 In particular, every time you start Alpine the filters will be checked for
16584 each message.
16585 Also, if you have any filters that depend on message state (New, Deleted, etc.)
16586 then Alpine will recheck for matches in messages that have changed state
16587 at the time you close the folder and before expunging.
16588 This is usually ok.
16589 However, in this case it is a problem because the command
16590 <P>
16591 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16592 <P>
16593 has the side effect of updating the database.
16594 So you run the risk of updating the database multiple times for a single
16595 message instead of updating it just once per message.
16596 There are some ways to work around this problem.
16597 What you need is a way to mark the message after you have run the filter.
16598 One way to mark messages is with the use of a keyword (say "Bogo").
16599 Besides having the filter move the message to a spam folder, also have it
16600 set the Bogo keyword.
16601 (Note that you will have to set up the "Bogo" keyword in the
16602 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in Setup/Config.)
16603 This rule can only set the Bogo keyword for the messages that it matches.
16604 You will also need to add a second rule right after this one that
16605 matches all the messages that don't have the Bogo keyword set
16606 (put the keyword in the Keyword pattern and toggle
16607 the Not with the ! command)
16608 and takes the action of setting it.
16609 Then change the "bogofilter -u" rule so that it won't be a match
16610 (and so it won't re-run the bogofilter command) if the keyword is already
16611 set.
16612 <P>
16613 What you will end up with is a rule that runs "bogofilter -u"
16614 on all messages that don't have the Bogo keyword set.
16615 This will have the side effect of inserting that message in the bogofilter
16616 database, match or not.
16617 If this rule matches (it is spam), the Bogo keyword will be set and
16618 the message will be moved to a spam folder.
16619 If it does not match, the
16620 following rule will mark the message by turning on the keyword.
16621 This second rule should be a non-terminating
16622 (<A HREF="h_config_filt_opts_nonterm">Dont-Stop-Even-if-Rule-Matches</A>)
16623 rule so that it doesn't stop the filtering process before the rest of
16624 your rules are consulted.
16626 <P>
16627 In summary, the first rule is something like
16628 <PRE>
16629 Nickname = bogofilter -u rule
16630 Current Folder Type =
16631 (*) Specific
16632 Folder = INBOX
16634 ! Keyword pattern = Bogo
16636 External Categorizer Commands =
16637 Command = /usr/local/bin/bogofilter -u
16638 Exit Status Interval = (0,0)
16639 Character Limit = <No Value Set: using "-1"> (optionally set this)
16641 Filter Action =
16642 (*) Move
16643 Folder = spam
16645 Set These Keywords = Bogo
16646 </PRE>
16647 <P>
16648 and the following rule is
16649 <PRE>
16650 Nickname = Set Bogo Keyword
16651 Current Folder Type =
16652 (*) Specific
16653 Folder = INBOX
16655 ! Keyword pattern = Bogo
16657 Filter Action =
16658 (*) Just Set Message Status
16660 Set These Keywords = Bogo
16662 Features =
16663 [X] dont-stop-even-if-rule-matches
16664 </PRE>
16665 <P>
16666 If it is possible for you to insert bogofilter in the delivery process instead
16667 of having it called from Alpine you could prevent having to wait
16668 for the bogofilter processing while you read your mail.
16669 You would have bogofilter add a header to the message at the time of delivery
16670 that identified it as spam or nonspam.
16671 With this method, you could avoid using a Categorizer Command while running Alpine,
16672 and just match on the header instead.
16673 You might still want to use the scripts mentioned above to initialize the
16674 database or to re-classify wrongly classified messages.
16676 <P>
16677 Finally, it isn't for the faint-hearted,
16678 but it is also possible to run bogofilter from PC-Alpine.
16679 You can install Cygwin from
16680 <A HREF="http://www.cygwin.com/">http://www.cygwin.com/</A> and
16681 then compile bogofilter in the cygwin environment, and run it from
16682 within PC-Alpine.
16683 You would end up with a Categorizer command that looked something like
16684 <P>
16685 <CENTER><SAMP>Command = C:\cygwin\bin\bogofilter.exe -u</SAMP></CENTER>
16686 <P>
16687 Note that the ".exe" extension is explicit,
16688 and that the bogofilter.exe executable should be in the same directory
16689 as cygwin1.dll.
16691 <P>
16692 <End of help on this topic>
16693 </BODY>
16694 </HTML>
16695 ======= h_config_role_cat_status =======
16696 <HTML>
16697 <HEAD>
16698 <TITLE>Exit Status Interval Explained</TITLE>
16699 </HEAD>
16700 <BODY>
16701 <H1>Exit Status Interval Explained</H1>
16703 The categorizer command is run and the result is the exit status of
16704 that command.
16705 If that exit status falls in the Exit Status Interval
16706 then it is considered a match, otherwise it is not a match.
16707 Of course for the entire rule to match, it must also be checked against
16708 the other defined parts of the Pattern.
16709 <P>
16710 The Exit Status Interval defaults to the single value 0 (zero).
16711 If you define it, it should be set to something like:
16712 <P>
16713 <CENTER><SAMP>(min_exit_value,max_exit_value)</SAMP></CENTER>
16714 <P>
16715 where "min_exit_value" and "max_exit_value" are integers.
16716 The special values "INF" and "-INF" may be used for large
16717 positive and negative integers.
16718 <P>
16719 Actually, a list of intervals may be used if you wish.
16720 A list would look like
16721 <P>
16722 <CENTER><SAMP>(min_exit_value1,max_exit_value1),(min_exit_value2,max_exit_value2),...</SAMP></CENTER>
16723 <P>
16724 When there is an Exit Status Interval defined, it is a match if the exit status
16725 of the categorizer command is contained in any of the intervals.
16726 The intervals include both endpoints.
16727 <P>
16728 The default interval is
16729 <P>
16730 <CENTER><SAMP>(0,0)</SAMP></CENTER>
16731 <P>
16732 and it matches only if the command exits with exit status equal to zero.
16734 <P>
16735 Look "<A HREF="h_rule_patterns">here</A>"
16736 for more information on Patterns.
16737 <P>
16738 Look <A HREF="h_edit_nav_cmds">here</A>
16739 to see the available Editing and Navigation commands.
16740 <P>
16741 <End of help on this topic>
16742 </BODY>
16743 </HTML>
16744 ======= h_config_role_cat_limit =======
16745 <HTML>
16746 <HEAD>
16747 <TITLE>Character Limit Explained</TITLE>
16748 </HEAD>
16749 <BODY>
16750 <H1>Character Limit Explained</H1>
16752 Setting this option makes it possible to limit how much of the message
16753 is made available to the categorizer command as input.
16754 The default value (-1) means that the entire message is fed to the
16755 command.
16756 A value of 0 (zero) means that only the headers of the message are
16757 made available.
16758 A positive integer means that the headers plus that many characters from
16759 the body of the message are passed to the categorizer.
16761 <P>
16762 Look "<A HREF="h_rule_patterns">here</A>"
16763 for more information on Patterns.
16764 <P>
16765 Look <A HREF="h_edit_nav_cmds">here</A>
16766 to see the available Editing and Navigation commands.
16767 <P>
16768 <End of help on this topic>
16769 </BODY>
16770 </HTML>
16771 ======= h_config_role_age =======
16772 <HTML>
16773 <HEAD>
16774 <TITLE>Age Interval Explained</TITLE>
16775 </HEAD>
16776 <BODY>
16777 <H1>Age Interval Explained</H1>
16779 The Age Interval, if defined, is part of the Pattern.
16780 If you use this, it should be set to something like:
16781 <P>
16782 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
16783 <P>
16784 where "min_age" and "max_age" are non-negative integers.
16785 The special value "INF" may be used for the max value.
16786 It represents infinity.
16787 <P>
16788 In rare cases it may be useful to use the more general form of the value,
16789 which is a comma-separated list of intervals.
16790 It would look something like:
16791 <P>
16792 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
16793 <P>
16794 When there is an Age Interval defined, it is a match if the age, in days, of
16795 the message is contained in the interval.
16796 The interval includes both endpoints.
16797 If the option is set to a list of intervals then it is a match if the
16798 age of the message is contained in any of the intervals.
16799 <P>
16800 Even though this option is called Age, it isn't actually
16801 the <EM>age</EM> of the message.
16802 Instead, it is how many days ago the message arrived in one of your folders.
16803 If the current time is a little past midnight, then a message that arrived
16804 just before midnight arrived yesterday, even though the message is only
16805 a few minutes old.
16806 By default, the date being used is not the date in the Date
16807 header of the message.
16808 It is the date that the message arrived in one of your folders.
16809 When you Save a message from one folder to another that arrival date
16810 is preserved.
16811 If you would like to use the date in the Date header that is possible.
16812 Turn on the option
16813 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
16814 near the bottom of the rule definition.
16815 <P>
16816 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
16817 The age interval
16818 <P>
16819 <CENTER><SAMP>(2,2)</SAMP></CENTER>
16820 <P>
16821 matches all messages that arrived on the day before yesterday.
16822 The interval
16823 <P>
16824 <CENTER><SAMP>(180,INF)</SAMP></CENTER>
16825 <P>
16826 matches all messages that arrived at least 180 days before today.
16827 The interval
16828 <P>
16829 <CENTER><SAMP>(0,1)</SAMP></CENTER>
16830 <P>
16831 matches all messages that arrived today or yesterday.
16833 <P>
16834 Look "<A HREF="h_rule_patterns">here</A>"
16835 for more information on Patterns.
16836 <P>
16837 Look <A HREF="h_edit_nav_cmds">here</A>
16838 to see the available Editing and Navigation commands.
16839 <P>
16840 <End of help on this topic>
16841 </BODY>
16842 </HTML>
16843 ======= h_config_role_size =======
16844 <HTML>
16845 <HEAD>
16846 <TITLE>Size Interval Explained</TITLE>
16847 </HEAD>
16848 <BODY>
16849 <H1>Size Interval Explained</H1>
16851 The Size Interval, if defined, is part of the Pattern.
16852 If you use this, it should be set to something like:
16853 <P>
16854 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
16855 <P>
16856 where "min_size" and "max_size" are non-negative integers.
16857 The special value "INF" may be used for the max value.
16858 It represents infinity.
16859 <P>
16860 In rare cases it may be useful to use the more general form of the value,
16861 which is a comma-separated list of intervals.
16862 It would look something like:
16863 <P>
16864 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
16865 <P>
16866 When there is a Size Interval defined, it is a match if the size of
16867 the message is contained in the interval.
16868 The interval includes both endpoints.
16869 If the option is set to a list of intervals then it is a match if the
16870 size of the message is contained in any of the intervals.
16871 <P>
16872 The size interval
16873 <P>
16874 <CENTER><SAMP>(10000,50000)</SAMP></CENTER>
16875 <P>
16876 matches all messages with sizes greater than or equal to 10000, and less
16877 than or equal to 50000.
16878 The interval
16879 <P>
16880 <CENTER><SAMP>(100000,INF)</SAMP></CENTER>
16881 <P>
16882 matches all messages with sizes greater than or equal to 100000.
16884 <P>
16885 Look "<A HREF="h_rule_patterns">here</A>"
16886 for more information on Patterns.
16887 <P>
16888 Look <A HREF="h_edit_nav_cmds">here</A>
16889 to see the available Editing and Navigation commands.
16890 <P>
16891 <End of help on this topic>
16892 </BODY>
16893 </HTML>
16894 ======= h_config_role_scorei =======
16895 <HTML>
16896 <HEAD>
16897 <TITLE>Score Interval Explained</TITLE>
16898 </HEAD>
16899 <BODY>
16900 <H1>Score Interval Explained</H1>
16902 The Score Interval, if defined, is part of the Pattern.
16903 If you use this, it should be set to something like:
16904 <P>
16905 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
16906 <P>
16907 where "min_score" and "max_score" are integers between
16908 -32000 and 32000.
16909 The special values "-INF" and "INF" may be used for
16910 the min and max values.
16911 These represent negative and positive infinity.
16912 <P>
16913 Actually, the value may be a list of intervals rather than just a
16914 single interval if that is useful.
16915 The elements of the list are separated by commas like:
16916 <P>
16917 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
16918 <P>
16919 When there is a Score Interval defined, it is a match if the score for
16920 the message is contained in any of the intervals.
16921 The intervals include both endpoints.
16922 The score for a message is calculated by looking at every scoring rule
16923 defined and adding up the Score Values for the rules that match the message.
16924 Scoring rules are created using the
16925 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
16927 <P>
16928 Look "<A HREF="h_rule_patterns">here</A>"
16929 for more information on Patterns.
16930 <P>
16931 Look <A HREF="h_edit_nav_cmds">here</A>
16932 to see the available Editing and Navigation commands.
16933 <P>
16934 <End of help on this topic>
16935 </BODY>
16936 </HTML>
16937 ======= h_config_role_fldr_type =======
16938 <HTML>
16939 <HEAD>
16940 <TITLE>Current Folder Type Explained</TITLE>
16941 </HEAD>
16942 <BODY>
16943 <H1>Current Folder Type Explained</H1>
16945 The Current Folder Type is part of the role's Pattern.
16946 It refers to the type of the currently open folder, which is the folder
16947 you were last looking at from the MESSAGE INDEX or MESSAGE TEXT screen.
16948 In order for a role to be considered a match, the current folder must
16949 be of the type you set here.
16950 The three types "Any", "News", and "Email" are
16951 all what you might think.
16952 <P>
16953 If the Current Folder Type for a role's Pattern is set to "News", for
16954 example, then
16955 that role will only be a match if the current folder is a newsgroup and
16956 the rest of the Pattern matches.
16957 The value "Specific" may be used when you want to limit the match
16958 to a specific folder (not just a specific type of folder), or to a list of
16959 specific folders.
16960 <P>
16961 In order to match a specific folder you Select the "Specific"
16962 button <EM>AND</EM> fill in
16963 the name (or list of names) of
16964 the folder in the "Folder List" field.
16965 If the current folder is any of the folders in the list, that is considered
16966 a match.
16967 The name of each folder in the list may be either "INBOX",
16968 the technical specification
16969 of the folder (like what appears in your configuration file) or, if the
16970 folder is one of your incoming folders, it may be the nickname you've given
16971 the folder.
16972 Here are a couple samples of specific folder names:
16973 <P>
16974 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
16975 <P>
16976 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
16977 <P>
16978 The easiest way to fill in the "Folder List" field is to use
16979 the "T" command that is available when the "Folder List" line is
16980 highlighted, or to use the "Take" command with the configuration
16981 feature
16982 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
16983 turned on.
16984 Note that you won't be able to edit the "Folder List" line unless the
16985 Current Folder Type is set to "Specific", and any value that
16986 "Folder List" has is ignored unless the type
16987 is set to "Specific".
16988 <P>
16989 When reading a newsgroup, there may be a performance penalty
16990 incurred when collecting the information necessary to check a Pattern.
16991 For this reason, the default Current Folder Type is set to "Email".
16992 <P>
16993 Look "<A HREF="h_rule_patterns">here</A>"
16994 for more information on Patterns.
16995 <P>
16996 Look <A HREF="h_edit_nav_cmds">here</A>
16997 to see the available Editing and Navigation commands.
16998 <P>
16999 <End of help on this topic>
17000 </BODY>
17001 </HTML>
17002 ======= h_config_filt_rule_type =======
17003 <HTML>
17004 <HEAD>
17005 <TITLE>Filter Action Explained</TITLE>
17006 </HEAD>
17007 <BODY>
17008 <H1>Filter Action Explained</H1>
17010 The Filter Action specifies the action to be taken when the Pattern is a
17011 match.
17012 It may be set to "Delete" "Move", or
17013 "Just Set Message Status".
17014 <P>
17015 If it is set to "Delete", then the message that matches the
17016 Pattern will be deleted from the open folder.
17017 <P>
17018 If it is set to "Move", then the name of the folder to which
17019 the matching message should be moved is given in the "Folder List" field on the
17020 next line of the screen.
17021 A list of folders separated by commas may be given, in which case the
17022 message will be copied to all of the folders in the list before it is
17023 deleted.
17024 <P>
17025 If it is set to neither of those two values (it is set to the value
17026 labeled "Just Set Message Status") then the message status
17027 setting will happen
17028 but the message will not be deleted or moved.
17029 <P>
17030 If you are Moving a message you may also set Message Status if you wish.
17031 <P>
17032 The easiest way to fill in the "Folder List" field is to use
17033 the T command that is available when the "Folder List" line is
17034 highlighted.
17035 Note that you won't be able to edit the "Folder List" line unless the
17036 Filter Action is set to "Move", and any value that
17037 "Folder List" has is ignored unless the type
17038 is set to "Move".
17039 <P>
17040 There are a few tokens that may be used in the names in the Folder List.
17041 They are all related to the date on which the filtering is taking place.
17042 The tokens are words surrounded by underscores.
17043 For example, if you want your filter to move messages to a folder named
17044 <P><CENTER><SAMP>abc-year-mon</SAMP></CENTER><P>
17045 you could specify the folder as
17046 <P><CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER><P>
17047 which would result in a file named something like
17048 <P><CENTER><SAMP>abc-2004-oct</SAMP></CENTER><P>
17049 or
17050 <P><CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER><P>
17051 which would result in a file named something like
17052 <P><CENTER><SAMP>abc-04-10</SAMP></CENTER><P>
17053 The available tokens are listed
17054 <A HREF="h_index_tokens">here</A>.
17055 <P>
17056 Look "<A HREF="h_rule_patterns">here</A>"
17057 for more information on Patterns.
17058 <P>
17059 Look <A HREF="h_edit_nav_cmds">here</A>
17060 to see the available Editing and Navigation commands.
17061 <P>
17062 <End of help on this topic>
17063 </BODY>
17064 </HTML>
17065 ======= h_config_score_fldr_type =======
17066 <HTML>
17067 <HEAD>
17068 <TITLE>Current Folder Type Explained</TITLE>
17069 </HEAD>
17070 <BODY>
17071 <H1>Current Folder Type Explained</H1>
17073 The Current Folder Type is part of the scoring rule's Pattern.
17074 It refers to the type of the folder that
17075 the message being scored is in.
17076 In order for a rule to be considered a match, the current folder must
17077 be of the type you set here.
17078 The three types "Any", "News", and "Email" are
17079 all what you might think.
17080 <P>
17081 If the Current Folder Type for a Pattern is set to "News", for
17082 example, then
17083 that Pattern will only match if the current folder is a newsgroup and
17084 the rest of the Pattern matches.
17085 The value "Specific" may be used when you want to limit the match
17086 to a specific folder (not just a specific type of folder), or to a list of
17087 specific folders.
17088 <P>
17089 In order to match a specific folder you Select the "Specific"
17090 button <EM>AND</EM> fill in
17091 the name (or list of names) of
17092 the folder in the "Folder List" field.
17093 If the current folder is any of the folders in the list, that is considered
17094 a match.
17095 The name of each folder in the list may be either "INBOX", the technical specification
17096 of the folder (like what appears in your configuration file) or, if the
17097 folder is one of your incoming folders, it may be the nickname you've given
17098 the folder.
17099 Here are a couple samples of specific folder names:
17100 <P>
17101 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17102 <P>
17103 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17104 <P>
17105 The easiest way to fill in the "Folder List" field is to use
17106 the T command that is available when the "Folder List" line is
17107 highlighted.
17108 Note that you won't be able to edit the "Folder List" line unless the
17109 Current Folder Type is set to "Specific", and any value that
17110 "Folder List" has is ignored unless the type
17111 is set to "Specific".
17112 <P>
17113 When reading a newsgroup, there may be a performance penalty
17114 incurred when collecting the information necessary to check a Pattern.
17115 For this reason, the default Current Folder Type is set to "Email".
17116 For example, if you have Index Line Coloring rules that have Score Intervals
17117 defined then the scores for all the visible messages will need to be calculated.
17118 If some of your Scoring rules have
17119 a Current Folder Type of
17120 "Any" or "News" this may cause the MESSAGE INDEX
17121 screen to draw more slowly when in a newsgroup.
17122 <P>
17123 Look "<A HREF="h_rule_patterns">here</A>"
17124 for more information on Patterns.
17125 <P>
17126 Look <A HREF="h_edit_nav_cmds">here</A>
17127 to see the available Editing and Navigation commands.
17128 <P>
17129 <End of help on this topic>
17130 </BODY>
17131 </HTML>
17132 ======= h_config_other_fldr_type =======
17133 <HTML>
17134 <HEAD>
17135 <TITLE>Current Folder Type Explained</TITLE>
17136 </HEAD>
17137 <BODY>
17138 <H1>Current Folder Type Explained</H1>
17140 The Current Folder Type is part of the rule's Pattern.
17141 It refers to the type of the folder being viewed.
17142 In order for a rule to be considered a match, the current folder must
17143 be of the type you set here.
17144 The three types "Any", "News", and "Email" are
17145 all what you might think.
17146 <P>
17147 If the Current Folder Type for a Pattern is set to "News", for
17148 example, then
17149 that Pattern will only match if the current folder is a newsgroup.
17150 The value "Specific" may be used when you want to limit the match
17151 to a specific folder (not just a specific type of folder), or to a list of
17152 specific folders.
17153 <P>
17154 In order to match a specific folder you Select the "Specific"
17155 button <EM>AND</EM> fill in
17156 the name (or list of names) of
17157 the folder in the "Folder List" field.
17158 If the current folder is any of the folders in the list, that is considered
17159 a match.
17160 The name of each folder in the list may be either "INBOX", the technical specification
17161 of the folder (like what appears in your configuration file) or, if the
17162 folder is one of your incoming folders, it may be the nickname you've given
17163 the folder.
17164 Here are a couple samples of specific folder names:
17165 <P>
17166 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17167 <P>
17168 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17169 <P>
17170 The easiest way to fill in the "Folder List" field is to use
17171 the T command that is available when the "Folder List" line is
17172 highlighted.
17173 Note that you won't be able to edit the "Folder List" line unless the
17174 Current Folder Type is set to "Specific", and any value that
17175 "Folder List" has is ignored unless the type
17176 is set to "Specific".
17177 <P>
17178 Look "<A HREF="h_rule_patterns">here</A>"
17179 for more information on Patterns.
17180 <P>
17181 Look <A HREF="h_edit_nav_cmds">here</A>
17182 to see the available Editing and Navigation commands.
17183 <P>
17184 <End of help on this topic>
17185 </BODY>
17186 </HTML>
17187 ======= h_config_incol_fldr_type =======
17188 <HTML>
17189 <HEAD>
17190 <TITLE>Current Folder Type Explained</TITLE>
17191 </HEAD>
17192 <BODY>
17193 <H1>Current Folder Type Explained</H1>
17195 The Current Folder Type is part of the Line Coloring rule's Pattern.
17196 It refers to the type of the folder for which the MESSAGE INDEX is
17197 being viewed.
17198 In order for a rule to be considered a match, the current folder must
17199 be of the type you set here.
17200 The three types "Any", "News", and "Email" are
17201 all what you might think.
17202 <P>
17203 If the Current Folder Type for a Pattern is set to "News", for
17204 example, then
17205 that Pattern will only match if the current folder is a newsgroup and
17206 the rest of the Pattern matches.
17207 The value "Specific" may be used when you want to limit the match
17208 to a specific folder (not just a specific type of folder), or to a list of
17209 specific folders.
17210 <P>
17211 In order to match a specific folder you Select the "Specific"
17212 button <EM>AND</EM> fill in
17213 the name (or list of names) of
17214 the folder in the "Folder List" field.
17215 If the current folder is any of the folders in the list, that is considered
17216 a match.
17217 The name of each folder in the list may be either "INBOX", the technical specification
17218 of the folder (like what appears in your configuration file) or, if the
17219 folder is one of your incoming folders, it may be the nickname you've given
17220 the folder.
17221 Here are a couple samples of specific folder names:
17222 <P>
17223 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17224 <P>
17225 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17226 <P>
17227 The easiest way to fill in the "Folder List" field is to use
17228 the T command that is available when the "Folder List" line is
17229 highlighted.
17230 Note that you won't be able to edit the "Folder List" line unless the
17231 Current Folder Type is set to "Specific", and any value that
17232 "Folder List" has is ignored unless the type
17233 is set to "Specific".
17234 <P>
17235 When reading a newsgroup, there may be a performance penalty
17236 incurred when collecting the information necessary to check a Pattern.
17237 For this reason, the default Current Folder Type is set to "Email".
17238 For example, a rule with a non-Normal Index Line Color
17239 and a Current Folder Type of
17240 "Any" or "News" may cause the MESSAGE INDEX
17241 screen to draw more slowly when in a newsgroup.
17242 <P>
17243 Look "<A HREF="h_rule_patterns">here</A>"
17244 for more information on Patterns.
17245 <P>
17246 Look <A HREF="h_edit_nav_cmds">here</A>
17247 to see the available Editing and Navigation commands.
17248 <P>
17249 <End of help on this topic>
17250 </BODY>
17251 </HTML>
17252 ======= h_config_filt_fldr_type =======
17253 <HTML>
17254 <HEAD>
17255 <TITLE>Current Folder Type Explained</TITLE>
17256 </HEAD>
17257 <BODY>
17258 <H1>Current Folder Type Explained</H1>
17260 The Current Folder Type is part of the Filtering rule's Pattern.
17261 It refers to the type of the folder for which the filtering is being done.
17262 In order for a rule to be considered a match, the current folder must
17263 be of the type you set here.
17264 The three types "Any", "News", and "Email" are
17265 all what you might think.
17266 <P>
17267 If the Current Folder Type for a Pattern is set to "News", for
17268 example, then
17269 that Pattern will only match if the current folder is a newsgroup and
17270 the rest of the Pattern matches.
17271 The value "Specific" may be used when you want to limit the match
17272 to a specific folder (not just a specific type of folder), or to a list of
17273 specific folders.
17274 <P>
17275 In order to match a specific folder you Select the "Specific"
17276 button <EM>AND</EM> fill in
17277 the name (or list of names) of
17278 the folder in the "Folder List" field.
17279 If the current folder is any of the folders in the list, that is considered
17280 a match.
17281 The name of each folder in the list may be either "INBOX", the technical specification
17282 of the folder (like what appears in your configuration file) or, if the
17283 folder is one of your incoming folders, it may be the nickname you've given
17284 the folder.
17285 Here are a couple samples of specific folder names:
17286 <P>
17287 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17288 <P>
17289 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17290 <P>
17291 The easiest way to fill in the "Folder List" field is to use
17292 the T command that is available when the "Folder List" line is
17293 highlighted.
17294 Note that you won't be able to edit the "Folder List" line unless the
17295 Current Folder Type is set to "Specific", and any value that
17296 "Folder List" has is ignored unless the type
17297 is set to "Specific".
17298 <P>
17299 When reading a newsgroup, there may be a performance penalty
17300 incurred when collecting the information necessary to check a Pattern.
17301 For this reason, the default Current Folder Type is set to "Email".
17302 For example, a rule with a Current Folder Type of either
17303 "Any" or "News" may cause the filtering to happen
17304 more slowly when opening a newsgroup.
17305 <P>
17306 Look "<A HREF="h_rule_patterns">here</A>"
17307 for more information on Patterns.
17308 <P>
17309 Look <A HREF="h_edit_nav_cmds">here</A>
17310 to see the available Editing and Navigation commands.
17311 <P>
17312 <End of help on this topic>
17313 </BODY>
17314 </HTML>
17315 ======= h_config_role_stat_imp =======
17316 <HTML>
17317 <HEAD>
17318 <TITLE>Message Important Status Explained</TITLE>
17319 </HEAD>
17320 <BODY>
17321 <H1>Message Important Status Explained</H1>
17323 This part of the Pattern may have one of three possible values.
17324 The default value is "Don't care", which matches any message.
17325 The other two values are "Yes", which means the message must be
17326 flagged "Important" in order to be a match; or "No", which
17327 means the message must <EM>not</EM> be flagged "Important" in order
17328 to be a match.
17329 <P>
17330 Look "<A HREF="h_rule_patterns">here</A>"
17331 for more information on Patterns.
17332 <P>
17333 Look <A HREF="h_edit_nav_cmds">here</A>
17334 to see the available Editing and Navigation commands.
17335 <P>
17336 <End of help on this topic>
17337 </BODY>
17338 </HTML>
17339 ======= h_config_role_stat_new =======
17340 <HTML>
17341 <HEAD>
17342 <TITLE>Message New Status Explained</TITLE>
17343 </HEAD>
17344 <BODY>
17345 <H1>Message New Status Explained</H1>
17347 This part of the Pattern may have one of three possible values.
17348 The default value is "Don't care", which matches any message.
17349 The other two values are "Yes", which means the message must be
17350 "New" in order to be a match; or "No", which
17351 means the message must <EM>not</EM> be "New" in order
17352 to be a match.
17353 "New" is the same as <EM>Unseen</EM> and not "New" is the
17354 same as <EM>Seen</EM>.
17355 <P>
17356 The nomenclature for New and Recent is a bit confusing:
17357 <P>
17358 New means that the message is Unseen.
17359 It could have been in your mailbox for a long time but if you haven't looked
17360 at it, it is still considered New.
17361 That matches the default Alpine index display that shows an N for such a
17362 message.
17363 <P>
17364 Recent means that the message was added to this folder since the last time
17365 you opened the folder.
17366 Alpine also shows an N by default for these types of messages.
17367 If you were to run two copies of Alpine that opened a folder one right after
17368 the other, a message would only show up as Recent in (at most) the first
17369 Alpine session.
17370 <P>
17371 Look "<A HREF="h_rule_patterns">here</A>"
17372 for more information on Patterns.
17373 <P>
17374 Look <A HREF="h_edit_nav_cmds">here</A>
17375 to see the available Editing and Navigation commands.
17376 <P>
17377 <End of help on this topic>
17378 </BODY>
17379 </HTML>
17380 ======= h_config_role_stat_recent =======
17381 <HTML>
17382 <HEAD>
17383 <TITLE>Message Recent Status Explained</TITLE>
17384 </HEAD>
17385 <BODY>
17386 <H1>Message Recent Status Explained</H1>
17388 This part of the Pattern may have one of three possible values.
17389 The default value is "Don't care", which matches any message.
17390 The other two values are "Yes", which means the message must be
17391 "Recent" in order to be a match; or "No", which
17392 means the message must <EM>not</EM> be "Recent" in order
17393 to be a match.
17394 "Recent" means that the message was added to the folder since
17395 the last time the folder was opened.
17396 If more than one mail client has the folder opened, the message will
17397 appear to be "Recent" to only one of the clients.
17398 <P>
17399 The nomenclature for New and Recent is a bit confusing:
17400 <P>
17401 New means that the message is Unseen.
17402 It could have been in your mailbox for a long time but if you haven't looked
17403 at it, it is still considered New.
17404 That matches the default Alpine index display that shows an N for such a
17405 message.
17406 <P>
17407 Recent means that the message was added to this folder since the last time
17408 you opened the folder.
17409 Alpine also shows an N by default for these types of messages.
17410 If you were to run two copies of Alpine that opened a folder one right after
17411 the other, a message would only show up as Recent in (at most) the first
17412 Alpine session.
17413 <P>
17414 Look "<A HREF="h_rule_patterns">here</A>"
17415 for more information on Patterns.
17416 <P>
17417 Look <A HREF="h_edit_nav_cmds">here</A>
17418 to see the available Editing and Navigation commands.
17419 <P>
17420 <End of help on this topic>
17421 </BODY>
17422 </HTML>
17423 ======= h_config_role_stat_del =======
17424 <HTML>
17425 <HEAD>
17426 <TITLE>Message Deleted Status Explained</TITLE>
17427 </HEAD>
17428 <BODY>
17429 <H1>Message Deleted Status Explained</H1>
17431 This part of the Pattern may have one of three possible values.
17432 The default value is "Don't care", which matches any message.
17433 The other two values are "Yes", which means the message must be
17434 marked "Deleted" in order to be a match; or "No", which
17435 means the message must <EM>not</EM> be marked "Deleted" in order
17436 to be a match.
17437 <P>
17438 If you are thinking of using this part of the Pattern as a way to prevent
17439 messages from being filtered more than once in a Filter Pattern,
17440 take a look at the Filter Option
17441 <A HREF="h_config_filt_opts_notdel">"Move-Only-if-Not-Deleted"</A>
17442 instead.
17443 It should work better than using this field since it will hide the filtered
17444 messages even if they are already Deleted.
17445 That option is at the bottom of the Filter configuration screen.
17446 <P>
17447 Look "<A HREF="h_rule_patterns">here</A>"
17448 for more information on Patterns.
17449 <P>
17450 Look <A HREF="h_edit_nav_cmds">here</A>
17451 to see the available Editing and Navigation commands.
17452 <P>
17453 <End of help on this topic>
17454 </BODY>
17455 </HTML>
17456 ======= h_config_role_stat_ans =======
17457 <HTML>
17458 <HEAD>
17459 <TITLE>Message Answered Status Explained</TITLE>
17460 </HEAD>
17461 <BODY>
17462 <H1>Message Answered Status Explained</H1>
17464 This part of the Pattern may have one of three possible values.
17465 The default value is "Don't care", which matches any message.
17466 The other two values are "Yes", which means the message must be
17467 marked "Answered" in order to be a match; or "No", which
17468 means the message must <EM>not</EM> be marked "Answered" in order
17469 to be a match.
17470 <P>
17471 Look "<A HREF="h_rule_patterns">here</A>"
17472 for more information on Patterns.
17473 <P>
17474 Look <A HREF="h_edit_nav_cmds">here</A>
17475 to see the available Editing and Navigation commands.
17476 <P>
17477 <End of help on this topic>
17478 </BODY>
17479 </HTML>
17480 ======= h_config_role_abookfrom =======
17481 <HTML>
17482 <HEAD>
17483 <TITLE>Address in Address Book Explained</TITLE>
17484 </HEAD>
17485 <BODY>
17486 <H1>Address in Address Book Explained</H1>
17488 This option gives you a way to match messages that contain an address
17489 that is in one of your address books.
17490 Only the simple entries in your address books are searched.
17491 Address book distribution lists are ignored!
17492 <P>
17493 This part of the Pattern may have one of five possible values.
17494 The default value is "Don't care", which matches any message.
17495 The value "Yes, in any address book" means at least one of the addresses
17496 from the message must be in at least one of your
17497 address books in order to be a match.
17498 The value "No, not in any address book"
17499 means none of the addresses may
17500 be in any of your address books in order to be a match.
17501 <P>
17502 The values "Yes, in specific address books" and
17503 "No, not in any of specific address books" are similar but instead
17504 of depending on all address books you are allowed to give a list of address
17505 books to look in.
17506 Usually this would be a single address book but it may be a
17507 list of address books as well.
17508 For each of these "specific" address book options you Select which
17509 of the Specific options you want (Yes or No) <EM>AND</EM> fill in the
17510 name (or list of names) of the address book in the
17511 "Abook List" field.
17512 The names to be used are those that appear in the ADDRESS BOOK LIST screen.
17513 The easiest way to fill in the Abook List field it to use
17514 the "T" command that is available when the "Abook List"
17515 line is highlighted.
17516 Note that you won't be able to edit the "Abook List" line unless the
17517 option is set to one of the two "Specific", values.
17518 <P>
17519 The addresses from the message that are checked for are determined by the
17520 setting you have for "Types of addresses to check for in address book".
17521 If you set this to "From" the From address from the message will
17522 be looked up in the address book.
17523 If you set it to "To" instead then the To addresses will be used.
17524 If any of the To addresses are in the address book then it is considered
17525 a match for "Yes" or not a match for "No".
17526 You could set it to both From and To, in which case all of the From and To
17527 addresses are used.
17528 The "Reply-To" and "Sender" cases are a little unusual.
17529 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
17530 exists or the From address if there is no Reply-To address.
17531 Same for the Sender address.
17532 <P>
17533 Look "<A HREF="h_rule_patterns">here</A>"
17534 for more information on Patterns.
17535 <P>
17536 Look <A HREF="h_edit_nav_cmds">here</A>
17537 to see the available Editing and Navigation commands.
17538 <P>
17539 <End of help on this topic>
17540 </BODY>
17541 </HTML>
17542 ======= h_config_inabook_from =======
17543 <HTML>
17544 <HEAD>
17545 <TITLE>From</TITLE>
17546 </HEAD>
17547 <BODY>
17548 <H1>From</H1>
17550 Setting the From line will cause the address from the From header line
17551 of the message to be checked for in the address book.
17552 <P>
17553 <End of help on this topic>
17554 </BODY>
17555 </HTML>
17556 ======= h_config_inabook_replyto =======
17557 <HTML>
17558 <HEAD>
17559 <TITLE>Reply-To</TITLE>
17560 </HEAD>
17561 <BODY>
17562 <H1>Reply-To</H1>
17564 Setting the Reply-To line will cause the address from the Reply-To header line
17565 of the message to be checked for in the address book.
17566 However, if there is no Reply-To header line in the message the From header
17567 line will be used instead.
17568 We understand this is dumb but we don't have an easy way around it.
17569 <P>
17570 <End of help on this topic>
17571 </BODY>
17572 </HTML>
17573 ======= h_config_inabook_sender =======
17574 <HTML>
17575 <HEAD>
17576 <TITLE>Sender</TITLE>
17577 </HEAD>
17578 <BODY>
17579 <H1>Sender</H1>
17581 Setting the Sender line will cause the address from the Sender header line
17582 of the message to be checked for in the address book.
17583 However, if there is no Sender header line in the message the From header
17584 line will be used instead.
17585 We understand this is dumb but we don't have an easy way around it.
17586 <P>
17587 <End of help on this topic>
17588 </BODY>
17589 </HTML>
17590 ======= h_config_inabook_to =======
17591 <HTML>
17592 <HEAD>
17593 <TITLE>To</TITLE>
17594 </HEAD>
17595 <BODY>
17596 <H1>To</H1>
17598 Setting the To line will cause the address from the To header line
17599 of the message to be checked for in the address book.
17600 <P>
17601 <End of help on this topic>
17602 </BODY>
17603 </HTML>
17604 ======= h_config_inabook_cc =======
17605 <HTML>
17606 <HEAD>
17607 <TITLE>CC</TITLE>
17608 </HEAD>
17609 <BODY>
17610 <H1>CC</H1>
17612 Setting the CC line will cause the address from the CC header line
17613 of the message to be checked for in the address book.
17614 <P>
17615 <End of help on this topic>
17616 </BODY>
17617 </HTML>
17618 ======= h_config_role_stat_8bitsubj =======
17619 <HTML>
17620 <HEAD>
17621 <TITLE>Raw 8-bit in Subject Explained</TITLE>
17622 </HEAD>
17623 <BODY>
17624 <H1>Raw 8-bit in Subject Explained</H1>
17626 It seems that lots of unwanted email contains unencoded 8-bit characters
17627 in the Subject.
17628 Normally, characters with the 8th bit set are not allowed in the Subject
17629 header unless they are MIME-encoded.
17630 This option gives you a way to match messages that have Subjects that
17631 contain unencoded 8-bit characters.
17632 <P>
17633 This part of the Pattern may have one of three possible values.
17634 The default value is "Don't care", which matches any message.
17635 The other two values are "Yes", which means the Subject of
17636 the message must contain unencoded 8-bit characters (characters with the
17637 most significant bit set)
17638 in order to be a match; or "No", which
17639 means the Subject must <EM>not</EM>
17640 contain unencoded 8-bit characters in order to be a match.
17641 <P>
17642 Look "<A HREF="h_rule_patterns">here</A>"
17643 for more information on Patterns.
17644 <P>
17645 Look <A HREF="h_edit_nav_cmds">here</A>
17646 to see the available Editing and Navigation commands.
17647 <P>
17648 <End of help on this topic>
17649 </BODY>
17650 </HTML>
17651 ======= h_config_role_bom =======
17652 <HTML>
17653 <HEAD>
17654 <TITLE>Beginning of Month</TITLE>
17655 </HEAD>
17656 <BODY>
17657 <H1>Beginning of Month</H1>
17659 This option gives you a limited ability to take different actions depending on whether
17660 this is the first time Alpine has been run this month or not.
17661 Though it would be nice to have such an option available, this is not the
17662 same as whether or not this is the first time a paricular folder has been
17663 opened this month.
17664 If you want some action (probably Filtering) to take place in a folder each
17665 month, then you will need to be sure that the folder is opened during the
17666 first Alpine session of the month in order for this option to be helpful.
17667 <P>
17668 This part of the Pattern may have one of three possible values.
17669 The default value is "Don't care", which matches any message.
17670 The other two values are "Yes", which means this is the first
17671 time Alpine has been run this month;
17672 or "No", which
17673 means this is not the first time Alpine has been run this month.
17674 <P>
17675 Look "<A HREF="h_rule_patterns">here</A>"
17676 for more information on Patterns.
17677 <P>
17678 Here are some technical details.
17679 The way that Alpine decides if it is the beginning of the month or not is
17680 to compare today's date with the date stored in the
17681 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
17682 variable in the config file.
17683 If the month of today's date is later than the month stored in the variable,
17684 then this is considered to be the first time you have run Alpine this month, and
17685 that turns the Beginning of the Month option on.
17686 <P>
17687 Look <A HREF="h_edit_nav_cmds">here</A>
17688 to see the available Editing and Navigation commands.
17689 <P>
17690 <End of help on this topic>
17691 </BODY>
17692 </HTML>
17693 ======= h_config_role_boy =======
17694 <HTML>
17695 <HEAD>
17696 <TITLE>Beginning of Year</TITLE>
17697 </HEAD>
17698 <BODY>
17699 <H1>Beginning of Year</H1>
17701 This option gives you a limited ability to take different actions depending on whether
17702 this is the first time Alpine has been run this year or not.
17703 Though it would be nice to have such an option available, this is not the
17704 same as whether or not this is the first time a paricular folder has been
17705 opened this year.
17706 If you want some action (probably Filtering) to take place in a folder each
17707 year, then you will need to be sure that the folder is opened during the
17708 first Alpine session of the year in order for this option to be helpful.
17709 <P>
17710 This part of the Pattern may have one of three possible values.
17711 The default value is "Don't care", which matches any message.
17712 The other two values are "Yes", which means this is the first
17713 time Alpine has been run this year;
17714 or "No", which
17715 means this is not the first time Alpine has been run this year.
17716 <P>
17717 Look "<A HREF="h_rule_patterns">here</A>"
17718 for more information on Patterns.
17719 <P>
17720 Here are some technical details.
17721 The way that Alpine decides if it is the beginning of the year or not is
17722 to compare today's date with the date stored in the
17723 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
17724 variable in the config file.
17725 If the year of today's date is later than the year stored in the variable,
17726 then this is considered to be the first time you have run Alpine this year, and
17727 that turns the Beginning of the Year option on.
17728 <P>
17729 Look <A HREF="h_edit_nav_cmds">here</A>
17730 to see the available Editing and Navigation commands.
17731 <P>
17732 <End of help on this topic>
17733 </BODY>
17734 </HTML>
17735 ======= h_config_role_inick =======
17736 <HTML>
17737 <HEAD>
17738 <TITLE>Initialize Values From Role Explained</TITLE>
17739 </HEAD>
17740 <BODY>
17741 <H1>Initialize Values From Role Explained</H1>
17743 This is a power user feature.
17744 You will usually want to leave this field empty.
17745 The value of this field is the nickname of another one of your roles.
17746 The Action values from that other role
17747 are used as the initial values of the Action items for this role.
17748 If you put something in any of the action fields for this role, that will
17749 override whatever was in the corresponding field of the initializer role.
17750 <P>
17751 You might use this field if the "Action" part of one of your roles
17752 is something you want to use in more than one role.
17753 Instead of filling in those action values again for each role, you
17754 may give the nickname of the role where the values are filled in.
17755 It's just a shortcut way to define Role Actions.
17756 <P>
17757 Here's an example to help explain how this works.
17758 Suppose you have a role with nickname "role1" and role1 has
17759 (among other things)
17760 <P>
17761 <CENTER><SAMP>Set Reply-To = The Pres <president@example.com></SAMP></CENTER>
17762 <P>
17763 set.
17764 If in "role2" you set "Initialize settings using role" to
17765 "role1", then role2 will inherit the Set Reply-To value
17766 from role1 by default (and any of the other inheritable action values
17767 that are set).
17768 So if role2 had
17769 <P>
17770 <CENTER><SAMP>Set Reply-To = <No Value Set></SAMP></CENTER>
17771 <P>
17772 defined, the Reply-To used with role2 would be "The Pres <president@example.com>"
17773 However, if role2 had
17774 <P>
17775 <CENTER><SAMP>Set Reply-To = VP <vicepresident@example.com></SAMP></CENTER>
17776 <P>
17777 defined, then the Reply-To used with role2 would be "VP <vicepresident@example.com>" instead.
17778 <P>
17779 If you wish,
17780 you may choose a nickname from your list of roles by using the
17781 "T" command.
17782 If the role you are using to initialize also has a role it initializes from,
17783 then that initialization happens first.
17784 That is, inheritance works as expected with the grandparent and
17785 great-grandparent (and so on) roles having the expected effect.
17786 <P>
17787 Look <A HREF="h_edit_nav_cmds">here</A>
17788 to see the available Editing and Navigation commands.
17789 <P>
17790 <End of help on this topic>
17791 </BODY>
17792 </HTML>
17793 ======= h_config_role_setfrom =======
17794 <HTML>
17795 <HEAD>
17796 <TITLE>Set From Explained</TITLE>
17797 </HEAD>
17798 <BODY>
17799 <H1>Set From Explained</H1>
17801 This describes part of the action to be taken if the Pattern for this
17802 role is a match.
17803 This field consists of a single address that will be used as the From
17804 address on the message you are sending.
17805 This should be a fully-qualified address like
17806 <P>
17807 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
17808 <P>
17809 or just
17810 <P>
17811 <CENTER><SAMP>user@domain</SAMP></CENTER>
17812 <P>
17813 If you wish,
17814 you may choose an address from your address book with the
17815 "T" command.
17816 <P>
17817 If this is left blank, then your normal From address will be used.
17818 <P>
17819 You may also find it useful to add the changed From address to the
17820 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
17821 configuration option.
17822 <P>
17823 Look <A HREF="h_edit_nav_cmds">here</A>
17824 to see the available Editing and Navigation commands.
17825 <P>
17826 <End of help on this topic>
17827 </BODY>
17828 </HTML>
17829 ======= h_config_role_setreplyto =======
17830 <HTML>
17831 <HEAD>
17832 <TITLE>Set Reply-To Explained</TITLE>
17833 </HEAD>
17834 <BODY>
17835 <H1>Set Reply-To Explained</H1>
17837 This describes part of the action to be taken if the Pattern for this
17838 role is a match.
17839 This field consists of a single address that will be used as the Reply-To
17840 address on the message you are sending.
17841 This may be a fully-qualified address like
17842 <P>
17843 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
17844 <P>
17845 or just
17846 <P>
17847 <CENTER><SAMP>user@domain</SAMP></CENTER>
17848 <P>
17849 If you wish,
17850 you may choose an address from your address book with the
17851 "T" command.
17852 <P>
17853 If this is left blank, then there won't be a Reply-To address unless
17854 you have configured one specially with the
17855 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>"
17856 configuration option.
17857 <P>
17858 Look <A HREF="h_edit_nav_cmds">here</A>
17859 to see the available Editing and Navigation commands.
17860 <P>
17861 <End of help on this topic>
17862 </BODY>
17863 </HTML>
17864 ======= h_config_role_setfcc =======
17865 <HTML>
17866 <HEAD>
17867 <TITLE>Set Fcc Explained</TITLE>
17868 </HEAD>
17869 <BODY>
17870 <H1>Set Fcc Explained</H1>
17872 This describes part of the action to be taken if the Pattern for this
17873 role is a match.
17874 This field consists of a single folder name that will be used in
17875 the Fcc field of the message you are sending.
17876 You may put anything here that you would normally type into the Fcc
17877 field from the composer.
17878 <P>
17879 In addition, an fcc of "" (two double quotation marks) means
17880 no Fcc.
17881 <P>
17882 A blank field here means that Alpine will use its normal rules for deciding
17883 the default value of the Fcc field.
17884 For many roles, perhaps most, it may make more sense for you to use the
17885 other Alpine facilities for setting the Fcc.
17886 In particular, if you want the Fcc to depend on who you are sending the
17887 message to then the <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
17888 is probably more useful.
17889 In that case, you would want to leave the Fcc field here blank.
17890 However, if you have a role that depends on who the message you are replying
17891 to was From, or what address that message was sent to;
17892 then it might make sense to set the Fcc for that role here.
17893 <P>
17894 If you wish,
17895 you may choose a folder from your folder collections by using the
17896 "T" command.
17897 <P>
17898 Look <A HREF="h_edit_nav_cmds">here</A>
17899 to see the available Editing and Navigation commands.
17900 <P>
17901 <End of help on this topic>
17902 </BODY>
17903 </HTML>
17904 ======= h_config_role_usesmtp =======
17905 <HTML>
17906 <HEAD>
17907 <TITLE>Use SMTP Server Explained</TITLE>
17908 </HEAD>
17909 <BODY>
17910 <H1>Use SMTP Server Explained</H1>
17912 This describes part of the action to be taken if the Pattern for this
17913 role is a match.
17914 If this field has a value, then it will be used as the SMTP server
17915 to send mail when this role is being used (unless the SMTP server variable
17916 is set in the system-wide fixed configuration file).
17917 It has the same semantics as the
17918 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
17919 variable in the Setup/Config screen.
17920 <P>
17921 If you are using this to post from home when you are at home and from
17922 work when you are at work you need to be careful about postponing messages.
17923 When you postpone a composition that was using a role with this variable
17924 set, the SMTP server list will be saved
17925 with the postponed composition.
17926 It cannot be changed later.
17927 Because of this, you may want to make this a list of SMTP servers
17928 with the preferred server at the front of the list and alternate servers
17929 later in the list.
17930 In your "Home" role you would put the home SMTP server first and
17931 the work SMTP server last.
17932 In your "Work" role you would put the work SMTP server first and
17933 the home SMTP server last.
17934 Then if you start a composition as "Work", postpone
17935 it, and then later resume it from home the work SMTP server will fail but
17936 the home SMTP server later in the list will succeed.
17937 <P>
17938 You may be able to simplify things by making the regular
17939 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
17940 variable in the Setup/Config screen a list instead of using roles
17941 to set the SMTP server.
17943 <P>
17944 Look <A HREF="h_edit_nav_cmds">here</A>
17945 to see the available Editing and Navigation commands.
17946 <P>
17947 <End of help on this topic>
17948 </BODY>
17949 </HTML>
17950 ======= h_config_role_usenntp =======
17951 <HTML>
17952 <HEAD>
17953 <TITLE>Use NNTP Server Explained</TITLE>
17954 </HEAD>
17955 <BODY>
17956 <H1>Use NNTP Server Explained</H1>
17958 This describes part of the action to be taken if the Pattern for this
17959 role is a match.
17960 If this field has a value, then it will be used as the NNTP server
17961 to post to newsgroups when this role is being used (unless the NNTP server
17962 variable
17963 is set in the system-wide fixed configuration file).
17964 It has the same semantics as the
17965 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
17966 variable in the Setup/Config screen.
17967 <P>
17968 This role setting can facilitate posting to the right nntp server for someone
17969 who reads news from various news sources. The feature
17970 <A HREF="h_config_predict_nntp_server">"<!--#echo var="FEAT_predict-nntp-server"-->"</A>
17971 allows for setting the correct <!--#echo var="VAR_nntp-server"--> without having to individually
17972 set a role for that <!--#echo var="VAR_nntp-server"-->, but for greater flexibility, setting
17973 nntp servers for roles may be more desirable for some people.
17974 <P>
17975 If you are using this to post from home when you are at home and from
17976 work when you are at work you need to be careful about postponing messages.
17977 When you postpone a composition that was using a role with this variable
17978 set, the NNTP server list will be saved
17979 with the postponed composition.
17980 It cannot be changed later.
17981 Because of this, you may want to make this a list of NNTP servers
17982 with the preferred server at the front of the list and alternate servers
17983 later in the list.
17984 In your "Home" role you would put the home NNTP server first and
17985 the work NNTP server last.
17986 In your "Work" role you would put the work NNTP server first and
17987 the home NNTP server last.
17988 Then if you start a composition as "Work", postpone
17989 it, and then later resume it from home the work NNTP server will fail but
17990 the home NNTP server later in the list will succeed.
17991 <P>
17992 You may be able to simplify things by making the regular
17993 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
17994 variable in the Setup/Config screen a list instead of using roles
17995 to set the NNTP server.
17997 <P>
17998 Look <A HREF="h_edit_nav_cmds">here</A>
17999 to see the available Editing and Navigation commands.
18000 <P>
18001 <End of help on this topic>
18002 </BODY>
18003 </HTML>
18004 ======= h_config_role_setotherhdr =======
18005 <HTML>
18006 <HEAD>
18007 <TITLE>Set Other Headers Explained</TITLE>
18008 </HEAD>
18009 <BODY>
18010 <H1>Set Other Headers Explained</H1>
18012 This describes part of the action to be taken if the Pattern for this
18013 role is a match.
18014 This field gives you a way to set values for headers besides
18015 "From" and "Reply-To".
18016 If you want to set either of those, use the specific
18017 "Set From" and "Set Reply-To" settings above.
18018 <P>
18019 This field is similar to the
18020 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" option.
18021 Each header you specify here must include the header tag
18022 ("To:", "Approved:", etc.)
18023 and may optionally include a value for that header.
18024 In order to see these headers when you compose using this role you
18025 must use the rich header
18026 <!--chtml if pinemode="function_key"-->(F5)
18027 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
18028 Here's an example that shows how you might set the To address.
18029 <P>
18030 <CENTER><SAMP>Set Other Hdrs = To: Full Name <user@domain></SAMP></CENTER>
18031 <P>
18032 Headers set in this way are different from headers set with the
18033 <!--#echo var="VAR_customized-hdrs"--> option in that the value you give for a header here
18034 will replace any value that already exists.
18035 For example, if you are Replying to a message there will already be at
18036 least one address in the To header (the address you are Replying to).
18037 However, if you Reply using a role that sets the To header, that role's
18038 To header value will be used instead.
18039 <P>
18040 Limitation: Because commas are used to separate the list of
18041 Other Headers, it is not possible to have the value of a
18042 header contain a comma;
18043 nor is there currently an "escape" mechanism provided
18044 to make this work.
18045 <P>
18046 Look <A HREF="h_edit_nav_cmds">here</A>
18047 to see the available Editing and Navigation commands.
18048 <P>
18049 <End of help on this topic>
18050 </BODY>
18051 </HTML>
18052 ======= h_config_role_setlitsig =======
18053 <HTML>
18054 <HEAD>
18055 <TITLE>Set Literal Signature Explained</TITLE>
18056 </HEAD>
18057 <BODY>
18058 <H1>Set Literal Signature Explained</H1>
18060 This describes part of the action to be taken if the Pattern for this
18061 role is a match.
18062 This field contains the actual text for your signature, as opposed to
18063 the name of a file containing your signature.
18064 If this is defined it takes precedence over any value set in the
18065 "Set Signature" field.
18066 <P>
18067 This is simply a different way to store the signature.
18068 The signature is stored inside your Alpine configuration file instead of in
18069 a separate file.
18070 Tokens work the same way they do with
18071 <A HREF="h_config_role_setsig">Set Signature</A>, so refer to the
18072 help text there for more information.
18073 <P>
18075 The two character sequence \n (backslash followed by
18076 the character n) will be used to signify a line-break in your signature.
18077 You don't have to enter the \n, but it will be visible in the
18078 CHANGE THIS ROLE RULE window after you are done editing the signature.
18079 <P>
18080 Look <A HREF="h_edit_nav_cmds">here</A>
18081 to see the available Editing and Navigation commands.
18082 <P>
18083 <End of help on this topic>
18084 </BODY>
18085 </HTML>
18086 ======= h_config_role_setsig =======
18087 <HTML>
18088 <HEAD>
18089 <TITLE>Set Signature Explained</TITLE>
18090 </HEAD>
18091 <BODY>
18092 <H1>Set Signature Explained</H1>
18094 This describes part of the action to be taken if the Pattern for this
18095 role is a match.
18096 <P>
18097 If either the default <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A>
18098 option from Setup/Config
18099 or the "Set LiteralSig" option for this role are defined,
18100 then this option will be ignored.
18101 You can tell that that is the case because the value of this
18102 option will show up as
18103 <P>
18104 <CENTER><SAMP><Ignored: using LiteralSig instead></SAMP></CENTER>
18105 <P>
18106 You may either use all Literal Signatures (signatures stored in your
18107 configuration file) throughout Alpine, or all signature files.
18108 You can't mix the two.
18109 <P>
18110 This field consists of a filename that will be used as the signature
18111 file when using this role.
18112 <P>
18113 If the filename is followed by a vertical bar (|) then instead
18114 of reading the contents of the file the file is assumed to be a
18115 program that will produce the text to be used on its standard output.
18116 The program can't have any arguments and doesn't receive any input from Alpine,
18117 but the rest of the processing works as if the contents came from a file.
18118 <P>
18119 Instead of storing the data in a local file, the
18120 signature data may be stored remotely in an IMAP folder.
18121 In order to do this,
18122 you must use a remote name for the signature.
18123 A remote signature name might look like:
18124 <P>
18125 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
18126 <P>
18128 The syntax used here is the same as the syntax used for a remote
18129 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
18130 Note that you may not access an existing signature file remotely,
18131 you have to create a new <EM>folder</EM> that contains the signature data.
18132 If the name you use here for the signature data is a remote name, then when
18133 you edit the file using the "F" command the data will
18134 be saved remotely in the folder.
18135 You aren't required to do anything special to create the folder, it
18136 gets created if you use a remote name.
18138 <P>
18139 If you type "F" you may edit the contents of the file (as opposed to
18140 the name of the file) you have specified.
18141 If you type "T" you may use a browser to choose an existing filename.
18142 <P>
18143 Besides containing regular text, a signature file may also
18144 contain (or a signature program may produce) tokens that are replaced with text
18145 that depends on the message you are replying to or forwarding.
18146 The tokens all look like _word_ (a word surrounded by underscores).
18147 For example, if the token
18148 <P>
18149 <CENTER><SAMP>_DATE_</SAMP></CENTER>
18150 <P>
18151 is included in the text of the signature file, then when you reply to
18152 or forward a message, the token will be replaced with the actual date
18153 the message you are replying to or forwarding was sent.
18154 <P>
18155 If you use a role that has a signature file for a plain composition
18156 (that is, not a reply or forward) then there is no original message, so
18157 any tokens that depend on the message will be replaced with nothing.
18158 So if you want a signature file to be useful for new compositions it
18159 shouldn't include any of the tokens that depend on the message being
18160 replied to or forwarded.
18161 <P>
18162 The list of available tokens is
18163 <A HREF="h_index_tokens">here</A>.
18164 <P>
18165 Actually, for the adventurous, there is a way to conditionally include text based
18166 on whether or not a token would result in specific replacement text.
18167 For example, you could include some text based on whether or not
18168 the _NEWS_ token would result in any newsgroups if it was used.
18169 It's explained in detail
18170 <A HREF="h_reply_token_conditionals">here</A>.
18171 <P>
18172 In the very unlikely event that you want to include a literal token in
18173 a signature file, you must precede it with a backslash character.
18174 For example, to include the literal text _DATE_ you must actually use
18175 \_DATE_.
18176 It is not possible to have a literal backslash followed by an expanded token.
18177 <P>
18178 A blank field here means that Alpine will use its normal rules for deciding
18179 which file (if any) to use for the signature file.
18180 <P>
18181 An alternate method for storing the signature is available in
18182 <A HREF="h_config_role_setlitsig">Set Literal Signature</A>.
18183 <P>
18184 Look <A HREF="h_edit_nav_cmds">here</A>
18185 to see the available Editing and Navigation commands.
18186 <P>
18187 <End of help on this topic>
18188 </BODY>
18189 </HTML>
18190 ======= h_config_role_settempl =======
18191 <HTML>
18192 <HEAD>
18193 <TITLE>Set Template Explained</TITLE>
18194 </HEAD>
18195 <BODY>
18196 <H1>Set Template Explained</H1>
18198 This describes part of the action to be taken if the Pattern for this
18199 role is a match.
18200 This field consists of a filename that will be used as the template
18201 file when using this role.
18202 The template file is a file that is included at the top of the message you
18203 are composing.
18204 <P>
18205 If the filename is followed by a vertical bar (|) then instead
18206 of reading the contents of the file the file is assumed to be a
18207 program that will produce the text to be used on its standard output.
18208 The program can't have any arguments and doesn't receive any input from Alpine,
18209 but the rest of the processing works as if the contents came from a file.
18210 <P>
18211 Instead of storing the data in a local file, the
18212 template may be stored remotely in an IMAP folder.
18213 In order to do this,
18214 you must use a remote name for the template.
18215 A remote template name might look like:
18216 <P>
18217 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/templ3</SAMP></CENTER>
18218 <P>
18220 The syntax used here is the same as the syntax used for a remote
18221 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
18222 Note that you may not access an existing template file remotely,
18223 you have to create a new <EM>folder</EM> that contains the template data.
18224 If the name you use here for the template is a remote name, then when
18225 you edit the file using the "F" command the data will
18226 be saved remotely in the folder.
18227 You aren't required to do anything special to create the folder, it
18228 gets created if you use a remote name.
18229 <P>
18230 If you type "F" you may edit the contents of the file (as opposed to
18231 the name of the file) you have specified.
18232 If you type "T" you may use a browser to choose an existing filename.
18233 <P>
18234 Besides containing regular text, the template file may also
18235 contain (or a template file program may produce) tokens that are replaced with text
18236 that depends on the message you are replying to or forwarding.
18237 The tokens all look like _word_ (a word surrounded by underscores).
18238 For example, if the token
18239 <P>
18240 <CENTER><SAMP>_DATE_</SAMP></CENTER>
18241 <P>
18242 is included in the text of the template file, then when you reply to
18243 or forward a message, the token will be replaced with the actual date
18244 the message you are replying to or forwarding was sent.
18245 <P>
18246 If you use a role that has a template file for a plain composition
18247 (that is, not a reply or forward) then there is no original message, so
18248 any tokens that depend on the message will be replaced with nothing.
18249 So if you want a template file to be useful for new compositions it
18250 shouldn't include any of the tokens that depend on the message being
18251 replied to or forwarded.
18252 <P>
18253 The list of available tokens is
18254 <A HREF="h_index_tokens">here</A>.
18255 <P>
18256 Actually, for the adventurous, there is a way to conditionally include text based
18257 on whether or not a token would result in specific replacement text.
18258 For example, you could include some text based on whether or not
18259 the _NEWS_ token would result in any newsgroups if it was used.
18260 It's explained in detail
18261 <A HREF="h_reply_token_conditionals">here</A>.
18262 <P>
18263 In the very unlikely event that you want to include a literal token in
18264 a template file, you must precede it with a backslash character.
18265 For example, to include the literal text _DATE_ you must actually use
18266 \_DATE_.
18267 It is not possible to have a literal backslash followed by an expanded token.
18268 <P>
18269 A blank template field means that Alpine will not use a template file when
18270 this role is being used.
18271 <P>
18272 Look <A HREF="h_edit_nav_cmds">here</A>
18273 to see the available Editing and Navigation commands.
18274 <P>
18275 <End of help on this topic>
18276 </BODY>
18277 </HTML>
18278 ======= h_config_filt_stat_imp =======
18279 <HTML>
18280 <HEAD>
18281 <TITLE>Set Important Status Explained</TITLE>
18282 </HEAD>
18283 <BODY>
18284 <H1>Set Important Status Explained</H1>
18286 This describes part of the action to be taken if the Pattern for this
18287 filter is a match.
18288 If set to "Don't change it" then this does nothing.
18289 If set to "Set this state" then the Important flag is set
18290 for the matching message.
18291 If set to "Clear this state" then the Important flag is cleared
18292 for the matching message.
18293 The important flag usually causes an asterisk to show up in the MESSAGE
18294 INDEX.
18295 It may also be useful when selecting a set of messages
18296 with the Select command.
18297 <P>
18298 Look <A HREF="h_edit_nav_cmds">here</A>
18299 to see the available Editing and Navigation commands.
18300 <P>
18301 <End of help on this topic>
18302 </BODY>
18303 </HTML>
18304 ======= h_config_filt_stat_new =======
18305 <HTML>
18306 <HEAD>
18307 <TITLE>Set New Status Explained</TITLE>
18308 </HEAD>
18309 <BODY>
18310 <H1>Set New Status Explained</H1>
18312 This describes part of the action to be taken if the Pattern for this
18313 filter is a match.
18314 If set to "Don't change it" then this does nothing.
18315 If set to "Set this state" then the
18316 matching message is marked New.
18317 If set to "Clear this state" then the
18318 matching message is marked Seen.
18319 <P>
18320 Look <A HREF="h_edit_nav_cmds">here</A>
18321 to see the available Editing and Navigation commands.
18322 <P>
18323 <End of help on this topic>
18324 </BODY>
18325 </HTML>
18326 ======= h_config_filt_stat_ans =======
18327 <HTML>
18328 <HEAD>
18329 <TITLE>Set Answered Status Explained</TITLE>
18330 </HEAD>
18331 <BODY>
18332 <H1>Set Answered Status Explained</H1>
18334 This describes part of the action to be taken if the Pattern for this
18335 filter is a match.
18336 If set to "Don't change it" then this does nothing.
18337 If set to "Set this state" then the Answered flag is set
18338 for the matching message.
18339 If set to "Clear this state" then the Answered flag is cleared
18340 for the matching message.
18341 <P>
18342 Look <A HREF="h_edit_nav_cmds">here</A>
18343 to see the available Editing and Navigation commands.
18344 <P>
18345 <End of help on this topic>
18346 </BODY>
18347 </HTML>
18348 ======= h_config_filt_stat_del =======
18349 <HTML>
18350 <HEAD>
18351 <TITLE>Set Deleted Status Explained</TITLE>
18352 </HEAD>
18353 <BODY>
18354 <H1>Set Deleted Status Explained</H1>
18356 This describes part of the action to be taken if the Pattern for this
18357 filter is a match.
18358 If set to "Don't change it" then this does nothing.
18359 If set to "Set this state" then the
18360 matching message is marked Deleted.
18361 If set to "Clear this state" then the
18362 matching message is marked UnDeleted.
18363 <P>
18364 You should not use this option unless you are prepared to have matching
18365 messages expunged from the folder permanently.
18366 For example, if you type the Expunge command, this filter is applied
18367 before the expunge, so matching messages will be marked Deleted and then
18368 will be permanently expunged from the folder.
18369 However, since the index isn't redrawn in between the time that the message
18370 is marked Deleted and the time that you are asked to expunge, the only
18371 indication that you are expunging the message comes in the number of messages
18372 being expunged.
18373 The same thing may happen when you close a folder.
18374 It is also possible that an expunge not initiated by you will
18375 delete matching messages.
18376 <P>
18377 Look <A HREF="h_edit_nav_cmds">here</A>
18378 to see the available Editing and Navigation commands.
18379 <P>
18380 <End of help on this topic>
18381 </BODY>
18382 </HTML>
18383 ======= h_config_role_scoreval =======
18384 <HTML>
18385 <HEAD>
18386 <TITLE>Score Value Explained</TITLE>
18387 </HEAD>
18388 <BODY>
18389 <H1>Score Value Explained</H1>
18391 A message's score is the sum of the Score Values from all of the Scoring rules
18392 with Patterns that match the message.
18393 The value you give here is the Score Value associated with this rule.
18394 A Score Value is an integer between -100 and 100, with the default
18395 value of zero.
18396 <P>
18397 Alternatively, if the
18398 <A HREF="h_config_role_scorehdrtok">"Score From Header"</A>
18399 field is defined
18400 (on the line right below the "Score Value" field)
18401 then the "Score Value" is ignored and
18402 the "Score From Header" field is used instead.
18403 <P>
18404 Look <A HREF="h_edit_nav_cmds">here</A>
18405 to see the available Editing and Navigation commands.
18406 <P>
18407 <End of help on this topic>
18408 </BODY>
18409 </HTML>
18410 ======= h_config_role_scorehdrtok =======
18411 <HTML>
18412 <HEAD>
18413 <TITLE>Score Value From Header Explained</TITLE>
18414 </HEAD>
18415 <BODY>
18416 <H1>Score Value From Header Explained</H1>
18418 This option provides a way to use a number that appears in the headers of your
18419 messages as the message's score, or as a component of that score.
18420 If this field is defined then it is used instead of the "Score Value".
18421 The idea behind this option is that there may be a score embedded in the
18422 headers of messages that has already been calculated outside of Alpine.
18423 For example, messages delivered to you may contain an "X-Spam" header and
18424 somewhere in that header there is a score.
18425 <P>
18426 The value for this option is the name of the header followed by parentheses
18427 with two arguments inside:
18428 <P>
18429 <CENTER><SAMP>HeaderName(field_number,field_separators)</SAMP></CENTER>
18430 <P>
18431 No space is allowed between the comma and the start of the field_separators.
18432 It would be interpreted as the first separator if it was there.
18433 Field 0 is the whole line, Field 1 is the data up to the first separator, Field 2
18434 starts after that and goes to the second separator, and so on.
18435 It's easier to explain with examples.
18436 <P>
18437 <CENTER><SAMP>X-Spam(2," ")</SAMP></CENTER>
18438 <P>
18439 In the above example the header that is used is the "X-Spam" header.
18440 The value of that header (the part after the colon and the space) is split
18441 into fields separated by spaces.
18442 <P>
18443 <CENTER><SAMP>Field1 <space> Field2 <space> Field3 ...</SAMP></CENTER>
18444 <P>
18445 The second field is selected and converted to an integer. It only makes sense
18446 if Field2 really is an integer.
18447 <P>
18448 Here's an example of a SpamAssassin header.
18449 The exact look of the header will vary, but if your incoming mail
18450 contains headers that look like the following
18451 <P>
18452 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
18453 <P>
18454 you might want to use the hits value as a score.
18455 Since the score is an integer value you can't make use of the decimal part of
18456 the number, but
18457 you might split off the hits=10 part as a score by using the characters "="
18458 and "." as your separators.
18459 <P>
18460 <CENTER><SAMP>X-Spam-Status(2,"=.")</SAMP></CENTER>
18461 <P>
18462 The first field starts with the Y in Yes and goes until the "=" after
18463 hits.
18464 The second field is "10" so the score value would be 10.
18465 <P>
18466 Another example we've seen has headers that look like
18467 <P>
18468 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
18469 <P>
18470 Because there are two equals before the 7% the value
18471 <P>
18472 <CENTER><SAMP>X-Spam(3,"=%")</SAMP></CENTER>
18473 <P>
18474 should capture the probability as the score.
18475 <P>
18476 The Score From Header scoring value actually works just like the
18477 regular Score Value in that the rest of the pattern has to match before
18478 it is used and the scores from all the different scoring rules that
18479 match for a particular message are added together.
18480 When using the Score From Header method it may (or may not) make sense to
18481 use only a single scoring rule with a pattern that matches every message.
18482 <P>
18483 Look <A HREF="h_edit_nav_cmds">here</A>
18484 to see the available Editing and Navigation commands.
18485 <P>
18486 <End of help on this topic>
18487 </BODY>
18488 </HTML>
18489 ======= h_config_role_replyuse =======
18490 <HTML>
18491 <HEAD>
18492 <TITLE>Reply Use Explained</TITLE>
18493 </HEAD>
18494 <BODY>
18495 <H1>Reply Use Explained</H1>
18497 This option determines how this particular role will be used when Replying
18498 to a message.
18499 There are three possible values for this option.
18500 The value "Never"
18501 means that this role will not be a candidate for use when Replying.
18502 The role's Pattern will not be checked for a match, however the role will
18503 be available to be manually switched to if there is a confirmation prompt.
18504 <P>
18506 The options "With confirmation" and "Without confirmation"
18507 mean that you do want to consider this role when Replying.
18508 For either of these settings, the role's Pattern will be compared with
18509 the message being replied to.
18510 If there is a match then this role will either be used without confirmation
18511 or will be the default when confirmation is asked for, depending on
18512 which of the two options is selected.
18513 If confirmation is requested, you will also have a chance to
18514 manually change the role to any one of your other roles.
18515 <P>
18517 You won't be prompted for confirmation if none of your role Patterns
18518 match the message being replied to.
18519 This is independent of the value of the current option.
18520 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18521 feature may be used to change this behavior.
18522 <P>
18523 <End of help on this topic>
18524 </BODY>
18525 </HTML>
18526 ======= h_config_role_forwarduse =======
18527 <HTML>
18528 <HEAD>
18529 <TITLE>Forward Use Explained</TITLE>
18530 </HEAD>
18531 <BODY>
18532 <H1>Forward Use Explained</H1>
18534 This option determines how this particular role will be used when Forwarding
18535 a message.
18536 There are three possible values for this option.
18537 The value "Never"
18538 means that this role will not be a candidate for use when Forwarding.
18539 The role's Pattern will not be checked for a match, however the role will
18540 be available to be manually switched to if there is a confirmation prompt.
18541 <P>
18543 The options "With confirmation" and "Without confirmation"
18544 mean that you do want to consider this role when Forwarding.
18545 For either of these settings, the role's Pattern will be compared with
18546 the message being forwarded.
18547 If there is a match then this role will either be used without confirmation
18548 or will be the default when confirmation is asked for, depending on
18549 which of the two options is selected.
18550 If confirmation is requested, you will also have a chance to
18551 manually change the role to any one of your other roles.
18552 <P>
18554 You won't be prompted for confirmation if none of your role Patterns
18555 match the message being forwarded.
18556 This is independent of the value of the current option.
18557 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18558 feature may be used to change this behavior.
18559 <P>
18560 <End of help on this topic>
18561 </BODY>
18562 </HTML>
18563 ======= h_config_role_composeuse =======
18564 <HTML>
18565 <HEAD>
18566 <TITLE>Compose Use Explained</TITLE>
18567 </HEAD>
18568 <BODY>
18569 <H1>Compose Use Explained</H1>
18571 This option determines how this particular role will be used when Composing
18572 a new message using the "Compose" command.
18573 This does not affect what happens when using the "Role" command
18574 to compose a new message.
18575 The "Role" command allows you to select a role from all of the
18576 roles you have defined, regardless of what Uses you've assigned to those
18577 roles.
18578 <P>
18580 There are three possible values for this option.
18581 The value "Never"
18582 means that this role will not be a candidate for use when Composing.
18583 The role's Current Folder Type will not be checked for a match, however the role
18584 will be available to be manually switched to if there is a confirmation prompt.
18585 <P>
18587 The options "With confirmation" and "Without confirmation"
18588 mean that you do want to consider this role when Composing.
18589 For either of these settings,
18590 the role's Current Folder Type will be checked (since there is no message
18591 to compare with, the rest of the Pattern is considered a match).
18592 If there is a match then this role will either be used without confirmation
18593 or will be the default when confirmation is asked for, depending on
18594 which of the two options is selected.
18595 If confirmation is requested, you will also have a chance to
18596 manually change the role to any one of your other roles.
18597 <P>
18599 When using the Compose command the role checking is a little different
18600 because there is no message being replied to or forwarded.
18601 Because of this the Current Folder Type is checked but the header pattern
18602 fields, the AllText pattern, the BodyText pattern, and the Score Interval are all ignored.
18603 A role is considered to be a match if it is a candidate for Compose Use and
18604 its Current Folder Type matches the currently open folder.
18605 This could be useful if you want to set a role based on the folder you
18606 are reading, or the type of folder you are reading.
18607 <P>
18609 You won't be prompted for confirmation if none of your role Patterns
18610 are a match.
18611 This is independent of the value of the current option.
18612 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18613 feature may be used to change this behavior.
18614 <P>
18615 <End of help on this topic>
18616 </BODY>
18617 </HTML>
18618 ======= h_config_filter_folder =======
18619 <HTML>
18620 <HEAD>
18621 <TITLE>Filter Folder Explained</TITLE>
18622 </HEAD>
18623 <BODY>
18624 <H1>Filter Folder Explained</H1>
18626 When the Filter Action is set to "Move",
18627 the folder or folders specified here will be used to store messages matching
18628 the provided pattern.
18630 <P>
18631 If you set the Filter Action to "Move" you must give a folder name
18632 here.
18634 <P>
18635 If you wish,
18636 you may choose a folder from your folder collections by using the
18637 "T" command.
18638 <P>
18639 Besides regular text, the folder name may also contain
18640 tokens that are replaced with text representing the current date
18641 when you run Alpine.
18642 For example, if the folder name you use is
18643 <P>
18644 <CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER>
18645 <P>
18646 that is replaced with something like
18647 <P>
18648 <CENTER><SAMP>abc-2004-oct</SAMP></CENTER>
18649 <P>
18650 Or,
18651 <P>
18652 <CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER>
18653 <P>
18654 becomes
18655 <P>
18656 <CENTER><SAMP>abc-04-10</SAMP></CENTER>
18657 <P>
18658 The token names must be surrounded by underscores in order to be recognized
18659 as tokens.
18660 The tokens that may be used are those that are derived from the current date.
18661 They're listed near the bottom of the list of tokens give
18662 <A HREF="h_index_tokens">here</A>.
18663 <P>
18664 Look "<A HREF="h_rule_patterns">here</A>"
18665 for more information on Patterns.
18666 <P>
18667 Look <A HREF="h_edit_nav_cmds">here</A>
18668 to see the available Editing and Navigation commands.
18669 <P>
18670 <End of help on this topic>
18671 </BODY>
18672 </HTML>
18673 ======= h_config_filter_kw_set =======
18674 <HTML>
18675 <HEAD>
18676 <TITLE>Set These Keywords Explained</TITLE>
18677 </HEAD>
18678 <BODY>
18679 <H1>Set These Keywords Explained</H1>
18681 This describes part of the action to be taken if the Pattern for this
18682 filter is a match.
18683 Read a little about keywords in the help text for the
18684 <A HREF="h_common_flag">Flag</A> command.
18685 This option is a list of keywords that will be Set when there is a match.
18686 If you wish, you may choose keywords from the list of keywords you have
18687 defined with the "T" command.
18688 You may add new keywords by defining them in the
18689 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
18690 If you have given a keyword a nickname when configuring it,
18691 that nickname may be used instead of the actual keyword.
18693 <P>
18694 Look <A HREF="h_edit_nav_cmds">here</A>
18695 to see the available Editing and Navigation commands.
18696 <P>
18697 <End of help on this topic>
18698 </BODY>
18699 </HTML>
18700 ======= h_config_filter_kw_clr =======
18701 <HTML>
18702 <HEAD>
18703 <TITLE>Clear These Keywords Explained</TITLE>
18704 </HEAD>
18705 <BODY>
18706 <H1>Clear These Keywords Explained</H1>
18708 This describes part of the action to be taken if the Pattern for this
18709 filter is a match.
18710 Read a little about keywords in the help text for the
18711 <A HREF="h_common_flag">Flag</A> command.
18712 This option is a list of keywords that will be Cleared when there is a match.
18713 If you wish, you may choose keywords from the list of keywords you have
18714 defined with the "T" command.
18715 You may add new keywords by defining them in the
18716 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
18717 If you have given a keyword a nickname when configuring it,
18718 that nickname may be used instead of the actual keyword.
18720 <P>
18721 Look <A HREF="h_edit_nav_cmds">here</A>
18722 to see the available Editing and Navigation commands.
18723 <P>
18724 <End of help on this topic>
18725 </BODY>
18726 </HTML>
18727 ======= h_index_tokens =======
18728 <HTML>
18729 <HEAD>
18730 <TITLE>Tokens for Index and Replying</TITLE>
18731 </HEAD>
18732 <BODY>
18734 This set of special tokens may be used in the
18735 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option,
18736 in the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
18737 in signature files,
18738 in template files used in
18739 <A HREF="h_rules_roles">"roles"</A>, and in the folder name
18740 that is the target of a Filter Rule.
18741 Some of them aren't available in all situations.
18742 <P>
18743 The tokens are used as they appear below for the "<!--#echo var="VAR_index-format"-->"
18744 option, but they must be surrounded by underscores for the
18745 "<!--#echo var="VAR_reply-leadin"-->" option, in signature and template files,
18746 and in the target of Filter Rules.
18747 <P>
18748 <P>
18750 <H1><EM>Tokens Available for all Cases (except Filter Rules)</EM></H1>
18752 <DL>
18753 <DT>SUBJECT</DT>
18754 <DD>
18755 This token represents the Subject the sender gave the message.
18756 Alternatives for use in the index screen are
18757 SUBJKEY, SUBJKEYINIT, SUBJECTTEXT, SUBJKEYTEXT, and SUBJKEYINITTEXT.
18758 You may color the subject text in the MESSAGE INDEX screen differently by using the
18759 <A HREF="h_config_index_subject_color">Index Subject Color</A> and the
18760 <A HREF="h_config_index_opening_color">Index Opening Color</A>
18761 options available from
18762 the <A HREF="h_color_setup">Setup Kolor</A> screen.
18763 </DD>
18765 <DT>FROM</DT>
18766 <DD>
18767 This token represents the personal name (or email address if the name
18768 is unavailable) of the person specified in the message's "From:"
18769 header field.
18770 You may color the from text in the MESSAGE INDEX screen differently by using the
18771 <A HREF="h_config_index_from_color">Index From Color</A>
18772 option available from
18773 the <A HREF="h_color_setup">Setup Kolor</A> screen.
18774 </DD>
18776 <DT>ADDRESS</DT>
18777 <DD>
18778 This is similar to the "FROM" token, only it is always the
18779 email address, never the personal name.
18780 For example, "mailbox@domain".
18781 </DD>
18783 <DT>MAILBOX</DT>
18784 <DD>
18785 This is the same as the "ADDRESS" except that the
18786 domain part of the address is left off.
18787 For example, "mailbox".
18788 </DD>
18790 <DT>SENDER</DT>
18791 <DD>
18792 This token represents the personal name (or email address) of the person
18793 listed in the message's "Sender:" header field.
18794 </DD>
18796 <DT>TO</DT>
18797 <DD>
18798 This token represents the personal names (or email addresses if the names
18799 are unavailable) of the persons specified in the
18800 message's "To:" header field.
18801 </DD>
18803 <DT>NEWSANDTO</DT>
18804 <DD>
18805 This token represents the newsgroups from the
18806 message's "Newsgroups:" header field <EM>and</EM>
18807 the personal names (or email addresses if the names
18808 are unavailable) of the persons specified in the
18809 message's "To:" header field.
18810 </DD>
18812 <DT>TOANDNEWS</DT>
18813 <DD>
18814 Same as "NEWSANDTO" except in the opposite order.
18815 </DD>
18817 <DT>NEWS</DT>
18818 <DD>
18819 This token represents the newsgroups from the
18820 message's "Newsgroups:" header field.
18821 </DD>
18823 <DT>CC</DT>
18824 <DD>
18825 This token represents the personal names (or email addresses if the names
18826 are unavailable) of the persons specified in the
18827 message's "Cc:" header field.
18828 </DD>
18830 <DT>RECIPS</DT>
18831 <DD>
18832 This token represents the personal names (or email addresses if the names
18833 are unavailable) of the persons specified in both the
18834 message's "To:" header field and
18835 the message's "Cc:" header field.
18836 </DD>
18838 <DT>NEWSANDRECIPS</DT>
18839 <DD>
18840 This token represents the newsgroups from the
18841 message's "Newsgroups:" header field <EM>and</EM>
18842 the personal names (or email addresses if the names
18843 are unavailable) of the persons specified in the
18844 message's "To:" and "Cc:" header fields.
18845 </DD>
18847 <DT>RECIPSANDNEWS</DT>
18848 <DD>
18849 Same as "NEWSANDRECIPS" except in the opposite order.
18850 </DD>
18852 <DT>INIT</DT>
18853 <DD>
18854 This token represents the initials from the personal name
18855 of the person specified in the message's "From:"
18856 header field.
18857 If there is no personal name, it is blank.
18858 </DD>
18860 <DT>DATE</DT>
18861 <DD>
18862 This token represents the date on which the message was sent, according
18863 to the "Date" header field.
18864 It has the format MMM DD. For example, "Oct 23".
18865 The feature
18866 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>,
18867 which adjusts for the timezone the message was sent from,
18868 may have an effect on the value of this token as well as the values of
18869 all of the other DATE or TIME tokens.
18870 Some of the DATE and TIME tokens are displayed in a locale-specific
18871 way unless the option
18872 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is set.
18873 </DD>
18875 <DT>SMARTDATE</DT>
18876 <DD>
18877 This token represents the date on which the message was sent, according
18878 to the "Date" header field.
18879 It is "Today" if the message was sent today,
18880 "Yesterday" for yesterday,
18881 "Wednesday" if it was last Wednesday, and so on. If the
18882 message is from last year and is more than six months old it includes the year, as well.
18883 See the SMARTDATE alternatives below, as well.
18884 </DD>
18886 <DT>SMARTTIME</DT>
18887 <DD>
18888 This token represents the most relevant elements of the date on which
18889 the message was sent (according to the "Date" header field),
18890 in a compact form. If the message was sent today, only the time is used
18891 (e.g. "9:22am", "10:07pm"); if it was sent during
18892 the past week, the day of the week and the hour are used
18893 (e.g. "Wed09am", "Thu10pm"); other dates are
18894 given as date, month, and year (e.g. "23Aug00",
18895 "9Apr98").
18896 </DD>
18898 <DT>SMARTDATETIME</DT>
18899 <DD>
18900 This is a combination of SMARTDATE and SMARTTIME.
18901 It is SMARTDATE unless the SMARTDATE value is "Today", in which
18902 case it is SMARTTIME.
18903 See the SMARTDATETIME alternatives below, as well.
18904 </DD>
18906 <DT>DATEISO</DT>
18907 <DD>
18908 This token represents the date on which the message was sent, according
18909 to the "Date" header field.
18910 It has the format YYYY-MM-DD. For example, "1998-10-23".
18911 </DD>
18913 <DT>SHORTDATEISO</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 YY-MM-DD. For example, "98-10-23".
18918 </DD>
18920 <DT>SHORTDATE1</DT>
18921 <DD>
18922 This token represents the date on which the message was sent, according
18923 to the "Date" header field.
18924 It has the format MM/DD/YY. For example, "10/23/98".
18925 </DD>
18927 <DT>SHORTDATE2</DT>
18928 <DD>
18929 This token represents the date on which the message was sent, according
18930 to the "Date" header field.
18931 It has the format DD/MM/YY. For example, "23/10/98".
18932 </DD>
18934 <DT>SHORTDATE3</DT>
18935 <DD>
18936 This token represents the date on which the message was sent, according
18937 to the "Date" header field.
18938 It has the format DD.MM.YY. For example, "23.10.98".
18939 </DD>
18941 <DT>SHORTDATE4</DT>
18942 <DD>
18943 This token represents the date on which the message was sent, according
18944 to the "Date" header field.
18945 It has the format YY.MM.DD. For example, "98.10.23".
18946 </DD>
18948 <DT>LONGDATE</DT>
18949 <DD>
18950 This token represents the date on which the message was sent, according
18951 to the "Date" header field.
18952 It has the format MMM DD, YYYY. For example, "Oct 23, 1998".
18953 </DD>
18955 <DT>SMARTDATE alternatives</DT>
18956 <DD>
18957 There are several versions of SMARTDATE that are all the same except
18958 for the way they format dates far in the past.
18959 SMARTDATE formats the date using the information from your locale settings
18960 to format the date string. It may end up formatting dates so that they look
18961 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
18962 The feature
18963 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
18964 may have an affect on the values of these tokens.
18965 If you want more control you may use one of the following.
18966 <DL>
18967 <DT>SMARTDATE</DT> <DD>If the option
18968 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
18969 then this will be locale specific. Control this with the
18970 LC_TIME locale setting on a UNIX system. On Windows
18971 the Regional Options control panel may be used to set the Short date
18972 format. At the programming level, the strftime routine is what Alpine
18973 uses to print the date.
18974 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
18975 to SMARTDATES1.</DD>
18976 <DT>SMARTDATEISO</DT> <DD>DATEISO format. See text above.</DD>
18977 <DT>SMARTDATESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
18978 <DT>SMARTDATES1</DT> <DD>SHORTDATE1 format.</DD>
18979 <DT>SMARTDATES2</DT> <DD>SHORTDATE2 format.</DD>
18980 <DT>SMARTDATES3</DT> <DD>SHORTDATE3 format.</DD>
18981 <DT>SMARTDATES4</DT> <DD>SHORTDATE4 format.</DD>
18982 </DL>
18983 </DD>
18985 <DT>SMARTDATETIME alternatives</DT>
18986 <DD>
18987 There are several versions of SMARTDATETIME that are all very similar.
18988 The ones that end in 24 use a 24-hour clock for Today's messages instead
18989 of a 12-hour clock.
18990 The other variation is
18991 for the way they format dates far in the past.
18992 SMARTDATETIME and SMARTDATETIME24 format the date using the information from your locale settings
18993 to format the date string. It may end up formatting dates so that they look
18994 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
18995 The feature
18996 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
18997 may have an affect on the values of these tokens.
18998 The possible choices are:
18999 <DL>
19000 <DT>SMARTDATETIME</DT> <DD>If the option
19001 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
19002 then this will be locale specific. Control this with the
19003 LC_TIME locale setting on a UNIX system. On Windows
19004 the Regional Options control panel may be used to set the Short date
19005 format. At the programming level, the strftime routine is what Alpine
19006 uses to print the date.
19007 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
19008 to SMARTDATETIMES1.</DD>
19009 <DT>SMARTDATETIME24</DT> <DD>Use TIME24 for Today</DD>
19010 <DT>SMARTDATETIMEISO</DT> <DD>DATEISO format. See text above.</DD>
19011 <DT>SMARTDATETIMEISO24</DT> <DD>Use TIME24 for Today</DD>
19012 <DT>SMARTDATETIMESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
19013 <DT>SMARTDATETIMESHORTISO24</DT> <DD>Use TIME24 for Today</DD>
19014 <DT>SMARTDATETIMES1</DT> <DD>SHORTDATE1 format.</DD>
19015 <DT>SMARTDATETIMES124</DT> <DD>Use TIME24 for Today</DD>
19016 <DT>SMARTDATETIMES2</DT> <DD>SHORTDATE2 format.</DD>
19017 <DT>SMARTDATETIMES224</DT> <DD>Use TIME24 for Today</DD>
19018 <DT>SMARTDATETIMES3</DT> <DD>SHORTDATE3 format.</DD>
19019 <DT>SMARTDATETIMES324</DT> <DD>Use TIME24 for Today</DD>
19020 <DT>SMARTDATETIMES4</DT> <DD>SHORTDATE4 format.</DD>
19021 <DT>SMARTDATETIMES424</DT> <DD>Use TIME24 for Today</DD>
19022 </DL>
19023 </DD>
19025 <DT>DAYDATE</DT>
19026 <DD>
19027 This token represents the date on which the message was sent, according
19028 to the "Date" header field.
19029 It looks like "Sat, 23 Oct 1998".
19030 This token is never converted in any locale-specific way.
19031 </DD>
19033 <DT>PREFDATE</DT>
19034 <DD>
19035 This token represents the date on which the message was sent, according
19036 to the "Date" header field.
19037 It is your operating system's idea of the preferred date representation for the current locale.
19038 Internally it uses the %x version of the date from the strftime routine.
19039 </DD>
19041 <DT>PREFTIME</DT>
19042 <DD>
19043 This token represents the time at which the message was sent, according
19044 to the "Date" header field.
19045 It is the preferred time representation for the current locale.
19046 Internally it uses the %X version of the time from the strftime routine.
19047 </DD>
19049 <DT>PREFDATETIME</DT>
19050 <DD>
19051 This token represents the date and time at which the message was sent, according
19052 to the "Date" header field.
19053 It is the preferred date and time representation for the current locale.
19054 Internally it uses the %c version of the time from the strftime routine.
19055 </DD>
19057 <DT>DAY</DT>
19058 <DD>
19059 This token represents the day of the month on which the message was sent,
19060 according to the "Date" header field.
19061 For example, "23" or "9".
19062 </DD>
19064 <DT>DAY2DIGIT</DT>
19065 <DD>
19066 This token represents the day of the month on which the message was sent,
19067 according to the "Date" header field.
19068 For example, "23" or "09".
19069 It is always 2 digits.
19070 </DD>
19072 <DT>DAYORDINAL</DT>
19073 <DD>
19074 This token represents the ordinal number that is the day of
19075 the month on which the message was sent,
19076 according to the "Date" header field.
19077 For example, "23rd" or "9th".
19078 </DD>
19080 <DT>DAYOFWEEK</DT>
19081 <DD>
19082 This token represents the day of the week on which the message was sent,
19083 according to the "Date" header field.
19084 For example, "Sunday" or "Wednesday".
19085 </DD>
19087 <DT>DAYOFWEEKABBREV</DT>
19088 <DD>
19089 This token represents the day of the week on which the message was sent,
19090 according to the "Date" header field.
19091 For example, "Sun" or "Wed".
19092 </DD>
19094 <DT>MONTHABBREV</DT>
19095 <DD>
19096 This token represents the month the message was sent, according
19097 to the "Date" header field.
19098 For example, "Oct".
19099 </DD>
19101 <DT>MONTHLONG</DT>
19102 <DD>
19103 This token represents the month in which the message was sent, according
19104 to the "Date" header field.
19105 For example, "October".
19106 </DD>
19108 <DT>MONTH</DT>
19109 <DD>
19110 This token represents the month in which the message was sent, according
19111 to the "Date" header field.
19112 For example, "10" or "9".
19113 </DD>
19115 <DT>MONTH2DIGIT</DT>
19116 <DD>
19117 This token represents the month in which the message was sent, according
19118 to the "Date" header field.
19119 For example, "10" or "09".
19120 It is always 2 digits.
19121 </DD>
19123 <DT>YEAR</DT>
19124 <DD>
19125 This token represents the year the message was sent, according
19126 to the "Date" header field.
19127 For example, "1998" or "2001".
19128 </DD>
19130 <DT>YEAR2DIGIT</DT>
19131 <DD>
19132 This token represents the year the message was sent, according
19133 to the "Date" header field.
19134 For example, "98" or "01".
19135 It is always 2 digits.
19136 </DD>
19138 <DT>TIME24</DT>
19139 <DD>
19140 This token represents the time at which the message was sent, according
19141 to the "Date" header field.
19142 There is no adjustment made for different time zones, so you'll get
19143 the time the message was sent according to the time zone the sender
19144 was in.
19145 It has the format HH:MM. For example, "17:28".
19146 </DD>
19148 <DT>TIME12</DT>
19149 <DD>
19150 This token represents the time at which the message was sent, according
19151 to the "Date" header field.
19152 This time is for a 12 hour clock.
19153 It has the format HH:MMpm.
19154 For example, "5:28pm" or "11:13am".
19155 </DD>
19157 <DT>TIMEZONE</DT>
19158 <DD>
19159 This token represents the numeric timezone from
19160 the "Date" header field.
19161 It has the format [+-]HHMM. For example, "-0800".
19162 </DD>
19164 </DL>
19166 <P>
19167 <H1><EM>Tokens Available Only for <!--#echo var="VAR_index-format"--></EM></H1>
19169 <DL>
19170 <DT>MSGNO</DT>
19171 <DD>
19172 This token represents the message's current position in the folder that,
19173 of course, may change as the folder is sorted or new mail arrives.
19174 </DD>
19176 <DT>STATUS</DT>
19177 <DD>
19178 This token represents a three character wide field displaying various
19179 aspects of the message's state.
19180 The first character is either blank,
19181 a '*' for message marked Important, or a '+' indicating a message
19182 addressed directly to you (as opposed to your having received it via a
19183 mailing list, for example).
19184 When the feature
19185 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>"
19186 is set, if the first character would have been
19187 blank then it will instead be a '-' if the message is cc'd to you.
19188 The second character is typically blank,
19189 though the arrow cursor may occupy it if either the
19190 "<A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>"
19191 or the
19192 "<A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A>" feature
19193 is set (or you actually are on a slow link).
19194 The third character is either '<A HREF="h_flag_deleted">D</A>' (Deleted),
19195 '<A HREF="h_flag_answered">A</A>' (Answered),
19196 '<A HREF="h_flag_forwarded">F</A>' (Forwarded),
19197 '<A HREF="h_flag_new">N</A>' (New), or blank.
19198 <P>
19199 If you are using a threaded view of the index and this message is at the
19200 top of a collapsed portion of a thread,
19201 then this token refers to all of the messages in the collapsed portion of
19202 the thread instead of just the top message.
19203 The first character will be a '*' if <EM>any</EM> of the messages in the thread
19204 are marked Important, else a '+' if any of the messages are addressed
19205 to you, else a '-' if any of the messages are cc'd to you.
19206 The third character will be a 'D' if <EM>all</EM> of the messages
19207 in the collapsed thread are marked deleted,
19208 an 'A' if <EM>all</EM> of the messages
19209 in the collapsed thread are marked answered,
19210 it will be an 'N' if any of
19211 the messages are undeleted and unseen, and it will be blank otherwise.
19212 </DD>
19214 <DT>FULLSTATUS</DT>
19215 <DD>
19216 This token represents a less abbreviated alternative
19217 to the "STATUS" token.
19218 It is six characters wide.
19219 The first character is '+', '-', or blank, the
19220 second blank, the third either '*' or blank, the fourth
19221 '<A HREF="h_flag_new">N</A>' or blank,
19222 the fifth '<A HREF="h_flag_answered">A</A>'
19223 or blank, and the sixth character is
19224 either '<A HREF="h_flag_deleted">D</A>' or
19225 blank.
19226 <P>
19227 If you are using a threaded view of the index and this message is at the
19228 top of a collapsed portion of a thread,
19229 then this token refers to all of the messages in the collapsed portion of
19230 the thread instead of just the top message.
19231 The first character is '+', '-', or blank depending on whether <EM>any</EM>
19232 of the messages in the collapsed thread are addressed to you or cc'd to you.
19233 The third character will be '*' if any of the messages are marked
19234 Important.
19235 The fourth character will be 'N' if all of the messages in the thread
19236 are New, else 'n' if some of the messages in the thread are New, else blank.
19237 The fifth character will be 'A' or 'a' or blank, and the sixth character
19238 will be 'D' or 'd' or blank.
19239 </DD>
19241 <DT>IMAPSTATUS</DT>
19242 <DD>
19243 This token represents an even less abbreviated alternative to the
19244 "STATUS" token.
19245 It differs from "FULLSTATUS" in only the fourth character, which is
19246 an 'N' if the message is new to this folder since the last time
19247 it was opened <EM>and</EM> it has not been viewed, an 'R' (Recent) if the message
19248 is new to the folder and has been viewed, a 'U' (Unseen) if the message is not
19249 new to the folder since it was last opened <EM>but</EM> has not been
19250 viewed, or a blank if the message has been in the folder since it was
19251 last opened and has been viewed.
19252 <P>
19253 If you are using a threaded view of the index and this message is at the
19254 top of a collapsed portion of a thread,
19255 then the fourth character will be
19256 'N' if all of the messages in the thread are unseen and recent;
19257 else 'n' if some of the messages in the thread are unseen and recent;
19258 else 'U' if all of the messages in the thread are unseen and not recent;
19259 else 'u' if some of the messages in the thread are unseen and not recent;
19260 else 'R' if all of the messages in the thread are seen and recent;
19261 else 'r' if some of the messages in the thread are seen and recent;
19262 else blank.
19263 </DD>
19265 <DT>SHORTIMAPSTATUS</DT>
19266 <DD>
19267 This is the same as the last four of the six characters of IMAPSTATUS,
19268 so the '+' To Me information will be missing.
19269 </DD>
19271 <DT>SIZE</DT>
19272 <DD>
19273 This token represents the total size, in bytes, of the message.
19274 If a "K" (Kilobyte)
19275 follows the number, the size is approximately 1,000
19276 times that many bytes (rounded to the nearest 1,000).
19277 If an "M" (Megabyte) follows the number, the size is approximately
19278 1,000,000 times that many bytes.
19279 Commas are not used in this field.
19280 This field is seven characters wide, including the enclosing parentheses.
19281 Sizes are rounded when "K" or "M" is present.
19282 The progression of sizes used looks like:
19284 <P>
19285 <CENTER><SAMP>0 1 ... 9999 10K ... 999K 1.0M ... 99.9M 100M ... 2000M</SAMP></CENTER>
19286 <P>
19287 </DD>
19289 <DT>SIZECOMMA</DT>
19290 <DD>
19291 This token represents the total size, in bytes, of the message.
19292 If a "K" (Kilobyte)
19293 follows the number, the size is approximately 1,000
19294 times that many bytes (rounded to the nearest 1,000).
19295 If an "M" (Megabyte) follows the number, the size is approximately
19296 1,000,000 times that many bytes.
19297 Commas are used if the number shown is 1,000 or greater.
19298 The SIZECOMMA field is one character wider than the SIZE field.
19299 Sizes are rounded when "K" or "M" is present.
19300 The progression of sizes used looks like:
19302 <P>
19303 <CENTER><SAMP>0 1 ... 99,999 100K ... 9,999K 10.0M ... 999.9M 1,000M ... 2,000M</SAMP></CENTER>
19304 <P>
19305 </DD>
19307 <DT>KSIZE</DT>
19308 <DD>
19309 This token represents the total size of the message, expressed in
19310 kilobytes or megabytes, as most appropriate.
19311 These are 1,024 byte kilobytes and 1,024 x 1,024 byte megabytes.
19312 The progression of sizes used looks like:
19314 <P>
19315 <CENTER><SAMP>0K 1K ... 1023K 1.0M ... 99.9M 100M ... 2047M</SAMP></CENTER>
19316 <P>
19317 </DD>
19319 <DT>SIZENARROW</DT>
19320 <DD>
19321 This token represents the total size, in bytes, of the message.
19322 If a "K" (Kilobyte)
19323 follows the number, the size is approximately 1,000
19324 times that many bytes.
19325 If an "M" (Megabyte) follows the number, the size is approximately
19326 1,000,000 times that many bytes.
19327 If a "G" (Gigabyte) follows the number, the size is approximately
19328 1,000,000,000 times that many bytes.
19329 This field uses only five characters of screen width, including the enclosing
19330 parentheses.
19331 The progression of sizes used looks like:
19333 <P>
19334 <CENTER><SAMP>0 1 ... 999 1K ... 99K .1M ... .9M 1M ... 99M .1G ... .9G 1G 2G</SAMP></CENTER>
19335 <P>
19336 </DD>
19338 <DT>DESCRIPSIZE</DT>
19339 <DD>
19340 This token is intended to represent a more useful description of the
19341 message than just its size, but it isn't very useful at this point.
19342 The plus sign in this view means there are attachments.
19343 Note that including this token in
19344 the "<!--#echo var="VAR_index-format"-->" could slow down the
19345 display a little while Alpine collects the necessary information.
19346 </DD>
19348 <DT>SUBJKEY</DT>
19349 <DD>
19350 This token is the same as the SUBJECT token unless keywords are set for
19351 the message.
19352 In that case, a list of keywords enclosed in braces will be prepended to
19353 the subject of the message.
19354 Only those keywords that you have defined in your
19355 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19356 in Setup/Config are considered in the list.
19357 In other words, keywords that have been set by some other means, perhaps
19358 by another email program, won't show up unless included in
19359 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19360 Having this set in the <!--#echo var="VAR_index-format"--> will also cause the keywords to be
19361 prepended to the subject in the MESSAGE TEXT screen.
19362 If you have given a keyword a nickname
19363 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19364 instead of the actual keyword.
19365 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19366 option may be used to modify this token slightly.
19367 It is also possible to color keywords in the index using the
19368 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19369 </DD>
19371 <DT>SUBJKEYINIT</DT>
19372 <DD>
19373 This token is the same as the SUBJKEY token except that instead of
19374 prepending a list of keywords to the subject, a list of first initials
19375 of keywords will be prepended instead.
19376 For example, if a message has the keywords <EM>Work</EM> and <EM>Now</EM>
19377 set (or Work and Now are the Alpine nicknames of keywords that are set)
19378 then the SUBJKEY token would cause a result like
19379 <P>
19380 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
19381 <P>
19382 whereas the SUBJKEYINIT token would give
19383 <P>
19384 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
19385 <P>
19386 Only those keywords that you have defined in your
19387 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19388 in Setup/Config are considered in the list.
19389 In other words, keywords that have been set by some other means, perhaps
19390 by another email program, won't show up unless included in
19391 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19392 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19393 option may be used to modify this token slightly.
19394 It is also possible to color keywords in the index using the
19395 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19396 </DD>
19398 <DT>SUBJECTTEXT</DT>
19399 <DD>
19400 Same as SUBJECT but if there is room in the Subject field for more text,
19401 the opening part of the text of the message is displayed after the subject.
19402 The time needed to fetch the text may cause a performance problem
19403 which can, of course, be avoided by using the SUBJECT version of
19404 the Subject instead.
19405 You may color this opening text differently by using the
19406 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19407 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19408 You may adjust the characters that are displayed between the Subject and the
19409 opening text with the option
19410 <A HREF="h_config_opening_sep"><!--#echo var="VAR_opening-text-separator-chars"--></A>.
19411 </DD>
19413 <DT>SUBJKEYTEXT</DT>
19414 <DD>
19415 Same as SUBJKEY but with the opening message text.
19416 </DD>
19418 <DT>OPENINGTEXT</DT>
19419 <DD>
19420 This is similar to SUBJECTTEXT.
19421 Instead of combining the Subject and the opening text in a single
19422 field in the index screen this token allows you to allocate a
19423 separate column just for the opening text of the message.
19424 The time needed to fetch this text may cause a performance problem.
19425 You may color this opening text differently by using the
19426 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19427 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19428 </DD>
19430 <DT>OPENINGTEXTNQ</DT>
19431 <DD>
19432 This is very similar to OPENINGTEXT.
19433 The NQ stands for No Quotes.
19434 The only difference is that quoted text (lines beginning with >) is deleted.
19435 For some messages this may be confusing.
19436 For example, a message might have a line preceding some quoted
19437 text that reads something like "On May 8th person A said."
19438 That no longer makes sense after the quoted text is deleted and it
19439 will appear that person A said whatever the text after the quote
19440 is, even though that is really person B talking.
19441 </DD>
19443 <DT>SUBJKEYINITTEXT</DT>
19444 <DD>
19445 Same as SUBJKEYINIT but with the opening message text.
19446 </DD>
19448 <DT>KEY</DT>
19449 <DD>
19450 This is a space-delimited list of keywords that are set for the message.
19451 Only those keywords that you have defined in your
19452 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19453 in Setup/Config are considered in the list.
19454 In other words, keywords that have been set by some other means, perhaps
19455 by another email program, won't show up unless included in
19456 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19457 If you have given a keyword a nickname
19458 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19459 instead of the actual keyword.
19460 It is also possible to color keywords in the index using the
19461 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19462 This token defaults to an arbitrary width of 5.
19463 You should set it to whatever width suits you using something
19464 like KEY(17) in the <!--#echo var="VAR_index-format"-->.
19465 </DD>
19467 <DT>KEYINIT</DT>
19468 <DD>
19469 This is a list of keyword initials that are set for the message.
19470 If you have given a keyword a nickname
19471 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), the initial of that nickname
19472 is displayed instead of the initial of the actual keyword.
19473 It is also possible to color keyword initials in the index using the
19474 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19475 This token defaults to an arbitrary width of 2.
19476 You should set it to whatever width suits you using something
19477 like KEYINIT(3) in the <!--#echo var="VAR_index-format"-->.
19478 </DD>
19480 <DT>PRIORITY</DT>
19481 <DD>
19482 The X-Priority header is a non-standard header that is used in a
19483 somewhat standard way by many mail programs.
19484 Alpine expects the value of this header to be a digit with a value
19485 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
19486 Since this priority is something that the sender sets it is only an indication
19487 of the priority that the sender attaches to the mail and it is therefore almost
19488 totally unreliable for use as a filtering criterion.
19489 This token will display the numeric value of the priority if it is between
19490 1 and 5.
19491 It will be suppressed (blank) if the value is 3, which is normal priority.
19492 This token may be colored with the
19493 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19494 </DD>
19496 <DT>PRIORITYALPHA</DT>
19497 <DD>
19498 This is a more verbose interpretation of the X-Priority field.
19499 Once again nothing is displayed unless the value of the field
19500 is 1, 2, 4, or 5.
19501 The values displayed for those values are:
19502 <P>
19503 <TABLE>
19504 <TR> <TD>1</TD> <TD>Highest</TD> </TR>
19505 <TR> <TD>2</TD> <TD>High</TD> </TR>
19506 <TR> <TD>4</TD> <TD>Low</TD> </TR>
19507 <TR> <TD>5</TD> <TD>Lowest</TD> </TR>
19508 </TABLE>
19509 <P>
19510 This token may be colored with the
19511 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19512 </DD>
19514 <DT>PRIORITY!</DT>
19515 <DD>
19516 This is a one character, non-numeric version of the X-Priority field.
19517 If the value of the X-Priority header is 1 or 2 an exclamation
19518 point is displayed.
19519 If the value is 4 or 5 a "v" (think down arrow) is displayed.
19520 This token may be colored with the
19521 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19522 </DD>
19524 <DT>ATT</DT>
19525 <DD>
19526 This is a one column wide field that represents the number of attachments
19527 a message has. It will be blank if there are no attachments, a single
19528 digit for one to nine attachments, or an asterisk for more than nine.
19529 Note that including this token in
19530 the "<!--#echo var="VAR_index-format"-->" could slow down the
19531 display a little while Alpine collects the necessary information.
19532 </DD>
19534 <DT>FROMORTO</DT>
19535 <DD>
19536 This token represents <EM>either</EM> the personal name (or email address) of
19537 the person listed in the message's "From:" header
19538 field, <EM>or</EM>, if that address is yours or one of your
19539 <A HREF="h_config_alt_addresses">alternate addresses</A>,
19540 the first person specified in the
19541 message's "To:" header field
19542 with the prefix "To: " prepended.
19543 If the from address is yours and there is also no "To" address,
19544 Alpine will use the address on the "Cc" line.
19545 If there is no address there, either, Alpine will look for a newsgroup name
19546 from the "Newsgroups" header field and put
19547 that after the "To: " prefix.
19548 </DD>
19550 <DT>FROMORTONOTNEWS</DT>
19551 <DD>
19552 This is almost the same as <EM>FROMORTO</EM>.
19553 The difference is that newsgroups aren't considered.
19554 When a message is from you, doesn't have a To or Cc, and does have
19555 a Newsgroups header; this token will be your name instead of the name
19556 of the newsgroup (like it would be with FROMORTO).
19557 </DD>
19559 <DT>TEXT</DT>
19560 <DD>
19561 This is a different sort of token.
19562 It allows you to display a label within each index line.
19563 It will be the same fixed text for each line.
19564 It is different from all the other tokens in that there is no space column
19565 displayed after this token.
19566 Instead, it is butted up against the following field.
19567 It also has a different syntax.
19568 The text to display is given following a colon after the
19569 word "TEXT".
19570 For example,
19571 <P>
19572 <CENTER><SAMP>TEXT:abc=</SAMP></CENTER>
19573 <P>
19574 would insert the literal text "abc=" (without the quotes)
19575 into the index display line.
19576 You must quote the text if it includes space characters, like
19577 <P>
19578 <CENTER><SAMP>TEXT:"abc = "</SAMP></CENTER>
19579 <P>
19580 </DD>
19582 <DT>HEADER</DT>
19583 <DD>
19584 This allows you to display the text from a particular header line in the
19585 message.
19586 The syntax for this token is substantially different from all the others
19587 in order that you might be able to display a portion of the text following
19588 a particular header.
19589 The header name you are interested in is given following a colon
19590 after the word "HEADER".
19591 For example,
19592 <P>
19593 <CENTER><SAMP>HEADER:X-Spam</SAMP></CENTER>
19594 <P>
19595 would display the text of the X-Spam header, if any.
19596 Like for other index tokens a width field may (and probably should)
19597 follow this.
19598 <P>
19599 <CENTER><SAMP>HEADER:X-Spam(10)</SAMP></CENTER>
19600 <P>
19601 displays the first ten characters of the X-Spam header.
19602 Unlike other index tokens, the syntax for HEADER is more flexible.
19603 An optional second argument comes after a comma inside the parentheses.
19604 It specifies the "field" number.
19605 By default, the field separator is a space character.
19606 No extra space characters are allowed in the argument list.
19607 <P>
19608 <CENTER><SAMP>HEADER:X-Spam(10,2)</SAMP></CENTER>
19609 <P>
19610 would display the second field, left-justified, in a 10 character
19611 wide field.
19612 The second field would consist of all the text after the first space
19613 up to the next space or the end of the header.
19614 The default field number is zero, which stands for the entire line.
19615 There is also an optional third argument that is a list of field
19616 separators. It defaults to a space character.
19617 The example
19618 <P>
19619 <CENTER><SAMP>HEADER:X-Spam(10,2,:% )</SAMP></CENTER>
19620 <P>
19621 would cause the field separators to be any of colon, percent,
19622 or space (there is a space character between the percent and the
19623 right parenthesis).
19624 The first field runs from the start of the header value up to the first
19625 colon, percent, or space; the second goes from there to the next; and so on.
19626 In order to use a comma character as a field separator you must escape
19627 it by preceding it with a backslash (\).
19628 The same is true of the backslash character itself.
19629 There is one further optional argument.
19630 It is an R or an L to specify right or left adjustment of the text
19631 within the field.
19632 The default is to left justify, however if you are displaying numbers
19633 you might prefer to right justify.
19634 <P>
19635 Here's an example of a SpamAssassin header.
19636 The exact look of the header will vary, but if your incoming mail
19637 contains headers that look like the following
19638 <P>
19639 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
19640 <P>
19641 you might want to display the hits value.
19642 The first field starts with the Y in Yes.
19643 To get what you're interested in you might use "=" and
19644 space as the field separators and display the third field, like
19645 <P>
19646 <CENTER><SAMP>HEADER:X-Spam-Status(4,3,= )</SAMP></CENTER>
19647 <P>
19648 or maybe you would break at the dot instead
19649 <P>
19650 <CENTER><SAMP>HEADER:X-Spam-Status(2,2,=.,R)</SAMP></CENTER>
19651 <P>
19652 Another example we've seen has headers that look like
19653 <P>
19654 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
19655 <P>
19656 Because there are two equals and a comma before the 7% and a comma
19657 after it, the token
19658 <P>
19659 <CENTER><SAMP>HEADER:X-Spam(3,4,=\,,R)</SAMP></CENTER>
19660 <P>
19661 should display the probability (for example 7% or 83%) right justified
19662 in a 3-wide field.
19663 </DD>
19665 <DT>ARROW</DT>
19666 <DD>
19667 This gives an alternative way to display the current message in the
19668 MESSAGE INDEX screen.
19669 Usually the current message is indicated by the line being shown in
19670 reverse video.
19671 Instead, if the ARROW token is included in your <!--#echo var="VAR_index-format"-->,
19672 the current line will include an "arrow" that
19673 looks like
19674 <P>
19675 <CENTER><SAMP>-></SAMP></CENTER>
19676 <P>
19677 in the ARROW token's field.
19678 For all of the non-current messages, the ARROW field will be filled
19679 with blanks.
19680 If you use the fixed-field width feature the length of the "arrow"
19681 may be adjusted.
19682 The arrow will be drawn as width-1 dashes followed by a greater than sign.
19683 For example, if you use ARROW(3) you will get
19684 <P>
19685 <CENTER><SAMP>--></SAMP></CENTER>
19686 <P>
19687 and ARROW(1) will give you just
19688 <P>
19689 <CENTER><SAMP>></SAMP></CENTER>
19690 <P>
19691 It is also possible to set the color of the ARROW field.
19692 By default (and for non-current messages) the arrow is colored the same
19693 as the index line it is part of.
19694 You may set it to be another color with the
19695 <A HREF="h_config_index_arrow_color">Index Arrow Color</A> option available from
19696 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19697 </DD>
19699 <DT>SCORE</DT>
19700 <DD>
19701 This gives the
19702 <a href="h_rules_score">score</a>
19703 of each message.
19704 This will be six columns wide to accomodate the widest possible score.
19705 You will probably want to use the <!--#echo var="VAR_index-format"--> fixed-field width feature
19706 to limit the width of the field to the widest score that
19707 you use (e.g. SCORE(3) if your scores are always between 0 and 999).
19708 If you have not defined any score rules the scores will all be zero.
19709 If any of your score rules contain AllText or BodyText patterns
19710 then including SCORE in the <!--#echo var="VAR_index-format"-->
19711 may slow down the display of the MESSAGE INDEX screen.
19712 </DD>
19713 </DL>
19715 <P>
19716 <H1><EM>Tokens Available for all but <!--#echo var="VAR_index-format"--></EM></H1>
19718 <DL>
19719 <DT>CURNEWS</DT>
19720 <DD>
19721 This token represents the current newsgroup if there is one.
19722 For example, "comp.mail.pine".
19723 </DD>
19725 <DT>MSGID</DT>
19726 <DD>
19727 This token represents the message ID of the message.
19728 This token does not work with Filter Rule folder names.
19729 </DD>
19731 <DT>CURDATE</DT>
19732 <DD>
19733 This token represents the current date.
19734 It has the format MMM DD. For example, "Oct 23".
19735 </DD>
19737 <DT>CURDATEISO</DT>
19738 <DD>
19739 This token represents the current date.
19740 It has the format YYYY-MM-DD. For example, "1998-10-23".
19741 </DD>
19743 <DT>CURDATEISOS</DT>
19744 <DD>
19745 This token represents the current date.
19746 It has the format YY-MM-DD. For example, "98-10-23".
19747 </DD>
19749 <DT>CURPREFDATE</DT>
19750 <DD>
19751 This token represents the current date.
19752 It is your operating system's idea of the preferred date representation for the current locale.
19753 Internally it uses the %x version of the date from the strftime routine.
19754 </DD>
19756 <DT>CURPREFTIME</DT>
19757 <DD>
19758 This token represents the current time.
19759 It is the preferred time representation for the current locale.
19760 Internally it uses the %X version of the time from the strftime routine.
19761 </DD>
19763 <DT>CURPREFDATETIME</DT>
19764 <DD>
19765 This token represents the current date and time.
19766 It is the preferred date and time representation for the current locale.
19767 Internally it uses the %c version of the time from the strftime routine.
19768 </DD>
19770 <DT>CURTIME24</DT>
19771 <DD>
19772 This token represents the current time.
19773 It has the format HH:MM. For example, "17:28".
19774 </DD>
19776 <DT>CURTIME12</DT>
19777 <DD>
19778 This token represents the current time.
19779 This time is for a 12 hour clock.
19780 It has the format HH:MMpm.
19781 For example, "5:28pm" or "11:13am".
19782 </DD>
19784 <DT>CURDAY</DT>
19785 <DD>
19786 This token represents the current day of the month.
19787 For example, "23" or "9".
19788 </DD>
19790 <DT>CURDAY2DIGIT</DT>
19791 <DD>
19792 This token represents the current day of the month.
19793 For example, "23" or "09".
19794 It is always 2 digits.
19795 </DD>
19797 <DT>CURDAYOFWEEK</DT>
19798 <DD>
19799 This token represents the current day of the week.
19800 For example, "Sunday" or "Wednesday".
19801 </DD>
19803 <DT>CURDAYOFWEEKABBREV</DT>
19804 <DD>
19805 This token represents the current day of the week.
19806 For example, "Sun" or "Wed".
19807 </DD>
19809 <DT>CURMONTH</DT>
19810 <DD>
19811 This token represents the current month.
19812 For example, "10" or "9".
19813 </DD>
19815 <DT>CURMONTH2DIGIT</DT>
19816 <DD>
19817 This token represents the current month.
19818 For example, "10" or "09".
19819 It is always 2 digits.
19820 </DD>
19822 <DT>CURMONTHLONG</DT>
19823 <DD>
19824 This token represents the current month.
19825 For example, "October".
19826 </DD>
19828 <DT>CURMONTHABBREV</DT>
19829 <DD>
19830 This token represents the current month.
19831 For example, "Oct".
19832 </DD>
19834 <DT>CURYEAR</DT>
19835 <DD>
19836 This token represents the current year.
19837 For example, "1998" or "2001".
19838 </DD>
19840 <DT>CURYEAR2DIGIT</DT>
19841 <DD>
19842 This token represents the current year.
19843 For example, "98" or "01".
19844 It is always 2 digits.
19845 </DD>
19847 <DT>LASTMONTH</DT>
19848 <DD>
19849 This token represents last month.
19850 For example, if this is November (the 11th month),
19851 it is equal to "10" or if this is October (the 10th month),
19852 it is "9".
19853 It is possible that this and the other tokens beginning with LASTMONTH
19854 below could be useful when used with a Filtering Rule that
19855 has the "Beginning of Month" option set.
19856 </DD>
19858 <DT>LASTMONTH2DIGIT</DT>
19859 <DD>
19860 This token represents last month.
19861 For example, if this is November (the 11th month),
19862 it is equal to "10" or if this is October (the 10th month),
19863 it is "09".
19864 It is always 2 digits.
19865 </DD>
19867 <DT>LASTMONTHLONG</DT>
19868 <DD>
19869 This token represents last month.
19870 For example, if this is November the value is "October".
19871 </DD>
19873 <DT>LASTMONTHABBREV</DT>
19874 <DD>
19875 This token represents last month.
19876 For example, if this is November the value is "Oct".
19877 </DD>
19879 <DT>LASTMONTHYEAR</DT>
19880 <DD>
19881 This token represents what the year was a month ago.
19882 For example, if this is October, 1998, it is "1998".
19883 If this is January, 1998, it is "1997".
19884 </DD>
19886 <DT>LASTMONTHYEAR2DIGIT</DT>
19887 <DD>
19888 This token represents what the year was a month ago.
19889 For example, if this is October, 1998, it is "98".
19890 If this is January, 1998, it is "97".
19891 </DD>
19893 <DT>LASTYEAR</DT>
19894 <DD>
19895 This token represents last year.
19896 For example, if this is 1998, it equals "1997".
19897 It is possible that this
19898 could be useful when used with a Filtering Rule that
19899 has the "Beginning of Year" option set.
19900 </DD>
19902 <DT>LASTYEAR2DIGIT</DT>
19903 <DD>
19904 This token represents last year.
19905 For example, if this is 1998, it equals "97".
19906 It is always 2 digits.
19907 </DD>
19909 <DT>ROLENICK</DT>
19910 <DD>
19911 This token represents the nickname of the
19912 role currently being used. If no role is being used,
19913 then no text will be printed for this token.
19914 This token does not work with Filter Rule folder names.
19915 </DD>
19916 </DL>
19918 <P>
19919 <H1><EM>Token Available Only for <!--#echo var="VAR_reply-leadin"--></EM></H1>
19920 See the help for the
19921 <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option
19922 to see why you might want to use this.
19923 Since the <!--#echo var="VAR_reply-leadin"--> contains free text this token
19924 must be surrounded by underscores when used.
19926 <DL>
19927 <DT>NEWLINE</DT>
19928 <DD>
19929 This is an end of line marker.
19930 </DD>
19931 </DL>
19933 <P>
19934 <H1><EM>Token Available Only for Templates and Signatures</EM></H1>
19936 <DL>
19937 <DT>CURSORPOS</DT>
19938 <DD>
19939 This token is different from the others.
19940 When it is replaced it is replaced with nothing, but it sets an Alpine
19941 internal variable that tells the composer to start with the cursor
19942 positioned at the position where this token was.
19943 If both the template file and the signature file contain
19944 a "CURSORPOS" token, then the position in the template file
19945 is used.
19946 If there is a template file and neither it nor the signature file contains
19947 a "CURSORPOS" token, then the cursor is positioned
19948 after the end of the contents of the
19949 template file when the composer starts up.
19950 </DD>
19951 </DL>
19953 <P>
19954 <End of help on this topic>
19955 </BODY>
19956 </HTML>
19957 ======= h_reply_token_conditionals =======
19958 <HTML>
19959 <HEAD>
19960 <TITLE>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</TITLE>
19961 </HEAD>
19962 <BODY>
19963 <H1>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</H1>
19965 Conditional text inclusion may be used with
19966 the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
19967 in signature files, and in template files used in
19968 <A HREF="h_rules_roles">"roles"</A>.
19969 It may <EM>not</EM> be used with the
19970 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
19972 <P>
19973 There is a limited if-else capability for including text.
19974 The if-else condition is based
19975 on whether or not a given token would result in replacement text you
19976 specify.
19977 The syntax of this conditional inclusion is
19978 <P>
19979 <CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER>
19980 <P>
19981 The left parenthesis must follow the underscore immediately, with no
19982 intervening space.
19983 It means the token is expanded and the results of that expansion are
19984 compared against the "match_this" argument.
19985 If there is an exact match, then the "if_matched" text is used
19986 as the replacement text.
19987 Otherwise, the "if_not_matched" text is used.
19988 One of the most useful values for the "match_this" argument is
19989 the empty string, "".
19990 In that case the expansion is compared against the empty string.
19991 <P>
19992 Here's an example to make it clearer.
19993 This text could be included in one of your template files:
19994 <P>
19995 <CENTER><SAMP>_NEWS_("", "I'm replying to email", "I'm replying to news")</SAMP></CENTER>
19996 <P>
19997 If that is included in a template file that you are using while replying
19998 to a message (because you chose to use the role it was part of),
19999 and that message has a newsgroup header and a newsgroup in that header,
20000 then the text
20001 <P>
20002 <CENTER><SAMP>I'm replying to news</SAMP></CENTER>
20003 <P>
20004 will be included in the message you are about to compose.
20005 On the other hand, if the message you are replying to does not have
20006 a newsgroup, then the text
20007 <P>
20008 <CENTER><SAMP>I'm replying to email</SAMP></CENTER>
20009 <P>
20010 would be included instead.
20011 This would also work in signature files and in
20012 the "<!--#echo var="VAR_reply-leadin"-->" option.
20013 If the "match_this", "if_matched",
20014 or "if_not_matched" arguments contain
20015 spaces, parentheses, or commas;
20016 they have to be quoted with double quotation marks (like in the example
20017 above).
20018 If you want to include a literal quote (") in the text you must escape the
20019 quote by preceding it with a backslash (\) character.
20020 If you want to include a literal backslash character you must escape it
20021 by preceding it with another backslash.
20022 <P>
20023 The comma followed by "if_not_matched" is optional.
20024 If there is no "if_not_matched"
20025 present then no text is included if the not_matched case is true.
20026 Here's another example:
20027 <P>
20028 <CENTER><SAMP>_NEWS_("", "", "This msg was seen in group: _NEWS_.")</SAMP></CENTER>
20029 <P>
20030 Here you can see that tokens may appear in the arguments.
20031 The same is true for tokens with the conditional parentheses.
20032 They may appear in arguments,
20033 though you do have to be careful to get the quoting and escaping of
20034 nested double quotes correct.
20035 If this was in the signature file being used and you were replying to a message
20036 sent to comp.mail.pine the resulting text would be:
20037 <P>
20038 <CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER>
20039 <P>
20040 If you were replying to a message that wasn't sent to any newsgroup the
20041 resulting text would be a single blank line.
20042 The reason you'd get a blank line is because the end of the line is
20043 outside of the conditional, so is always included.
20044 If you wanted to get rid of that blank line you could do so by moving
20045 the end of line inside the conditional.
20046 In other words, it's ok to have multi-line
20047 "if_matched" or "if_not_matched" arguments in your
20048 template file.
20049 The text just continues until the next double quotation, even if it's not
20050 on the same line.
20051 <P>
20052 Here's an example for use in the "<!--#echo var="VAR_reply-leadin"-->":
20053 <P>
20054 <CENTER><SAMP>On _DAYDATE_, _FROM__CURNEWS_("", "", "seen in _CURNEWS_,") wrote</SAMP></CENTER>
20055 <P>
20056 If this was in your <!--#echo var="VAR_reply-leadin"--> and you were replying to a message
20057 while reading the newsgroup comp.mail.pine the resulting text would be:
20058 <P>
20059 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone, seen in comp.mail.pine, wrote:</SAMP></CENTER>
20060 <P>
20061 If you were replying to a message while reading an email folder instead
20062 of a newsgroup the resulting leadin text would be
20063 <P>
20064 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
20065 <P>
20066 Here's one more (contrived) example illustrating a matching argument
20067 that is not the empty string.
20068 <P>
20069 <CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER>
20070 <P>
20071 If this was the value of your "<!--#echo var="VAR_reply-leadin"-->" option and you
20072 were replying to
20073 a message that was sent today, then the value of the "<!--#echo var="VAR_reply-leadin"-->"
20074 would be
20075 <P>
20076 <CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER>
20077 <P>
20078 But if you were replying to a message sent on Oct. 27 (and that wasn't
20079 today) you would get
20080 <P>
20081 <CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER>
20082 <P>
20084 <End of help on this topic>
20085 </BODY>
20086 </HTML>
20087 ======= h_composer_cntxt_nick =======
20088 <HTML>
20089 <HEAD>
20090 <TITLE>Collection Nickname Explained</TITLE>
20091 </HEAD>
20092 <BODY>
20093 <H1>Collection Edit Help -- Nickname Field</H1>
20095 This field is provided so you can add a short nickname to use when
20096 referring to this collection within Alpine. Spaces are allowed, and
20097 you don't need to use double-quotes. However, the double-quote
20098 character is not allowed.
20099 <P>
20100 Look <A HREF="h_edit_nav_cmds">here</A>
20101 to see the available Editing and Navigation commands.
20102 <P>
20103 <End of help on this topic>
20104 </BODY>
20105 </HTML>
20106 ======= h_folder_server_syntax =======
20107 <HTML>
20108 <HEAD>
20109 <TITLE>Server Name Syntax</TITLE>
20110 </HEAD>
20111 <BODY>
20112 <H1>Server Name Syntax</H1>
20114 This help describes the syntax that may be used for server names
20115 that may be associated with remote folders or SMTP servers.
20117 <P>
20118 A server name is the hostname of the server.
20119 It's a good idea to use the host's fully-qualified network name.
20121 <P>
20122 <CENTER><SAMP>foo.example.com</SAMP></CENTER>
20123 <P>
20125 However, IP addresses are allowed if surrounded
20126 with square-brackets.
20128 <P>
20129 <CENTER><SAMP>[127.0.0.1]</SAMP></CENTER>
20130 <P>
20132 An optional network port number may be supplied by appending
20133 a colon (:) followed by the port number
20134 to the server name.
20135 By default, the IMAP port number, 143, is used.
20137 <P>
20138 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
20139 <P>
20141 Besides server name and optional port number, various other optional
20142 parameters may be supplied that alter Alpine's interaction with the server.
20143 A parameter is supplied by appending a slash (/) character followed by
20144 the parameter's name and,
20145 depending on the particular parameter, the value assigned to that
20146 name, to the server name (and optional port number).
20147 Parameter names are <EM>not</EM> case sensitive.
20148 Currently supported parameters include:
20150 <DL>
20152 <DT>User</DT>
20153 <DD>This parameter requires an associated value, and is intended to
20154 provide the username identifier with which to establish the server
20155 connection.
20156 If your SMTP server offers SMTP AUTH authentication, adding this
20157 parameter to the
20158 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
20159 option will cause Alpine to attempt to authenticate to the server using the
20160 supplied username.
20161 Similarly, if your NNTP server offers NNTP "AUTHINFO SASL"
20162 or "AUTHINFO USER" authentication, adding this parameter to the
20163 <A HREF="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></A>
20164 option (or to the server name for any folder collection using NNTP)
20165 will cause Alpine to attempt
20166 to authenticate to the server using the supplied username.
20167 An example might be:
20169 <P>
20170 <CENTER><SAMP>/user=katie</SAMP></CENTER>
20171 <P>
20173 </DD>
20175 <DT>TLS</DT>
20176 <DD>
20177 Normally, when a new connection is made an attempt is made to
20178 negotiate a secure (encrypted) session using Transport Layer Security (TLS).
20179 If that fails then a non-encrypted connection will be attempted instead.
20180 This is a unary parameter indicating communication with the server must
20181 take place over a TLS connection. If the attempt to use TLS fails then
20182 this parameter will cause the connection to fail instead of falling
20183 back to an unsecure connection.
20185 <P>
20186 <CENTER><SAMP>/tls</SAMP></CENTER>
20187 <P>
20189 </DD>
20191 <DT>SSL</DT>
20192 <DD>
20193 This is a unary parameter indicating communication with the server should
20194 take place over a Secure Socket Layer connection. The server must support
20195 this method, and be prepared to accept connections on the appropriate
20196 port (993 by default).
20197 Alpine must be linked with an SSL library for this option to be operational.
20199 <P>
20200 <CENTER><SAMP>/ssl</SAMP></CENTER>
20201 <P>
20203 </DD>
20205 <DT>TLS1</DT>
20206 <DD>
20207 This parameter indicates that the connection to the server will be made
20208 over the SSL port, but using the TLSv1 protocol, instead of the usual
20209 SSLv3 or SSLv2 protocols.
20210 Alpine must be linked with an SSL library for this option to be operational.
20212 <P>
20213 <CENTER><SAMP>/tls1</SAMP></CENTER>
20214 <P>
20216 </DD>
20218 <DT>DTLS1</DT>
20219 <DD>
20220 This parameter indicates that the connection to the server will be made
20221 over the SSL port, but using the DTLSv1 protocol, instead of the usual
20222 SSLv3 or SSLv2 protocols.
20223 Alpine must be linked with an SSL library for this option to be operational.
20225 <P>
20226 <CENTER><SAMP>/dtls1</SAMP></CENTER>
20227 <P>
20229 </DD>
20231 <DT>TLS1_1</DT>
20232 <DD>
20233 This parameter indicates that the connection to the server will be made
20234 over the SSL port, but using the TLSv1.1 protocol, instead of the usual
20235 SSLv3 or SSLv2 protocols.
20236 Alpine must be linked with an SSL library for this option to be operational.
20238 <P>
20239 <CENTER><SAMP>/tls1_1</SAMP></CENTER>
20240 <P>
20242 </DD>
20244 <DT>TLS1_2</DT>
20245 <DD>
20246 This parameter indicates that the connection to the server will be made
20247 over the SSL port, but using the TLSv1.2 protocol, instead of the usual
20248 SSLv3 or SSLv2 protocols.
20249 Alpine must be linked with an SSL library for this option to be operational.
20251 <P>
20252 <CENTER><SAMP>/tls1_2</SAMP></CENTER>
20253 <P>
20255 </DD>
20258 <DT>NoValidate-Cert</DT>
20259 <DD>Do not validate certificates (for TLS or SSL connections) from the server.
20260 This is needed if the server uses self-signed certificates or if Alpine
20261 cannot validate the certificate for some other known reason.
20262 <P>
20263 </DD>
20265 <DT>Anonymous</DT>
20266 <DD>This is a unary parameter (that means it does not have a value)
20267 indicating that the connection be logged in as
20268 "anonymous" rather than a specific user.
20269 Not all servers offer anonymous
20270 access; those which do generally only offer read-only access to certain
20271 "public" folders.
20273 <P>
20274 <CENTER><SAMP>/anonymous</SAMP></CENTER>
20275 <P>
20277 </DD>
20279 <DT>Secure</DT>
20280 <DD>This is a unary parameter indicating that the connection use the
20281 most secure authentication method mutually supported by Alpine and the
20282 server.
20283 Alpine is capable of authenticating connections to
20284 the server using several methods.
20285 By default, Alpine will attempt each
20286 method until either a connection is established or the
20287 list of methods is exhausted.
20288 This parameter causes Alpine to instead fail
20289 the connection if the first (generally most "secure") method fails.
20291 <P>
20292 <CENTER><SAMP>/secure</SAMP></CENTER>
20293 <P>
20295 </DD>
20297 <DT>Submit</DT>
20298 <DD>This is a unary parameter for use with the
20299 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> option.
20300 It indicates that the connection should be made to the Submit server
20301 (<A HREF="http://www.ietf.org/rfc/rfc2476.txt">RFC 3676</A>)
20302 (port 587) instead of the SMTP port (25).
20303 At the time this help was written the submit option was equivalent to
20304 specifying port 587.
20306 <P>
20307 <CENTER><SAMP>/submit</SAMP></CENTER>
20308 <P>
20309 or
20310 <P>
20311 <CENTER><SAMP>host:587</SAMP></CENTER>
20312 <P>
20314 </DD>
20316 <DT>Debug</DT>
20317 <DD>This is a unary parameter indicating that the connection be established
20318 in a verbose mode. Basically, it causes Alpine to log the communication with
20319 the server in Alpine's debug file.
20320 Normally, the pine -d command-line flag would be used instead.
20321 <P>
20322 </DD>
20324 <DT>NoRsh</DT>
20325 <DD>By default, Alpine attempts to login using "rsh",
20326 the UNIX remote shell program.
20327 Including "NoRsh" will cause connections to this server to skip
20328 the "rsh" attempt.
20329 This might be useful to avoid long timeouts caused by rsh firewalls, for
20330 example.
20331 <P>
20332 </DD>
20334 <DT>Loser</DT>
20335 <DD>This option makes sense only for IMAP servers that do not perform
20336 a SEARCH command correctly. If your filtering rules
20337 fail to filter some messages, that should have been filtered, then this
20338 option will make Alpine download all data necessary to perform that search.
20339 There is a performance penalty when using this option. Downloading the
20340 data to perfom the search will take longer than requesting the IMAP
20341 server to perform the filtering, but the filtering will be done correctly.
20342 <P>
20343 </DD>
20346 <DT>Service</DT>
20347 <DD>This parameter requires an associated value. The default value is
20348 "IMAP" which indicates communication with the server based
20349 on the IMAP4rev1 protocol (defined in RFC 3501 -- see
20350 <A HREF="http://www.imap.org/docs/rfc3501.html">http://www.imap.org/docs/rfc3501.html</A>).</DD>
20352 Other service values include:
20353 <DL>
20354 <DT>NNTP</DT>
20355 <DD>This value indicates communication with the server takes place via
20356 the Network News Transfer Protocol. Use this to define a collection
20357 of newsgroups on a remote news server. So
20359 <P>
20360 <CENTER><SAMP>/service=NNTP</SAMP></CENTER>
20361 <P>
20362 or just
20363 <P>
20364 <CENTER><SAMP>/NNTP</SAMP></CENTER>
20365 <P>
20367 is the way to specify NNTP access.
20368 <P>
20369 </DD>
20371 <DT>POP3</DT>
20372 <DD>This value indicates communication with the server takes place via the
20373 Post Office Protocol 3 protocol.
20375 <P>
20376 <CENTER><SAMP>/service=POP3</SAMP></CENTER>
20377 <P>
20378 or just
20379 <P>
20380 <CENTER><SAMP>/POP3</SAMP></CENTER>
20381 <P>
20383 Note that there are several important issues
20384 to consider when selecting this option:
20385 <OL>
20386 <LI> POP3 provides access to only your INBOX. In other words,
20387 secondary folders such as your "saved-messages" are inaccessible.
20388 <LI> Alpine's implementation of POP3 does not follow the traditional POP
20389 model and will leave your mail on the server. Refer to the
20390 <A HREF="h_maildrop">Mail Drop</A> functionality for a possible way around this problem.
20391 <LI> See the discussion about new-mail checking in <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
20392 </OL>
20393 </DD>
20394 </DL>
20395 </DL>
20397 <P>
20398 Note that it is possible to include more than one parameter in a server
20399 specification by concatenating the parameters. For example:
20401 <P>
20402 <CENTER><SAMP>foo.example.com:port/user=katie/novalidate-cert/debug</SAMP></CENTER>
20403 <P>
20405 <P>
20406 <End of help on this topic>
20407 </BODY>
20408 </HTML>
20409 ======= h_composer_cntxt_server =======
20410 <HTML>
20411 <HEAD>
20412 <TITLE>Collection Server: Explained</TITLE>
20413 </HEAD>
20414 <BODY>
20415 <H1>Collection Edit Help -- Server Field</H1>
20417 This collection's "Server:" definition indicates the
20418 hostname of the server providing access to the folders in this
20419 collection.
20420 The syntax of this server name is the same as for other server names used
20421 in remote folder names in
20422 Alpine and is described
20423 <A HREF="h_folder_server_syntax">here</A>.
20425 <P>
20426 <End of help on this topic>
20427 </BODY>
20428 </HTML>
20429 ======= h_composer_cntxt_path =======
20430 <HTML>
20431 <HEAD>
20432 <TITLE>Collection Path: Explained</TITLE>
20433 </HEAD>
20434 <BODY>
20435 <H1>Collection Edit Help -- Path Field</H1>
20437 The collection's "Path:" definition indicates the location
20438 of the folders in this collection. If the path or any of its components
20439 do not exist, Alpine will prompt you for their creation when exiting the
20440 Add/Change screen.
20442 <P>
20443 By default the path is interpreted as defining a section of your personal
20444 folder area. This area and how you specify it are defined by the
20445 server, if one is specified in the collection, or, typically, the home
20446 directory if no server is defined.
20448 <P>
20449 To define a collection outside the default "area", prefix
20450 the path with the "namespace" to use when interpreting the
20451 given path. If a namespace is specified, the Path begins with the
20452 sharp, "#", character followed by the name of the namespace
20453 and then the namespace's path-element-delimiter. Aside from the
20454 path's format, namespaces can also imply access rights, content
20455 policy, audience, location, and, occasionally, access methods.
20457 <P>
20458 Each server exports its own set (possibly of size one) of
20459 namespaces. Hence, it's likely communication with your server's
20460 administrator will be required for specific configurations. Some of
20461 the more common namespaces, however, include:
20463 <DL>
20464 <DT>#news.</DT>
20465 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
20466 names are hierarchically defined with each level delimited by a period.
20467 </DD>
20468 <DT>#public/</DT>
20469 <DD>This specifies a folder area that the server may export to the general
20470 public.
20471 </DD>
20472 <DT>#shared/</DT>
20473 <DD>This specifies a folder area that the folder may export to groups
20474 of users.
20475 </DD>
20476 <DT>#ftp/</DT>
20477 <DD>This specifies a folder area that is the same as that it may have
20478 exported via the "File Transfer Protocol".
20479 </DD>
20480 <DT>#mh/</DT>
20481 <DD>This specifies the personal folder area associated with folders
20482 and directories that were created using the MH message handling system.
20483 </DD>
20484 </DL>
20485 <P>
20487 In addition, the server may support access to other user's folders,
20488 provided you have suitable permissions. Common methods use a prefix
20489 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
20490 indicate the root of the other user's folder area.
20492 <P>
20493 No, nothing's simple.
20495 <P>
20496 <End of help on this topic>
20497 </BODY>
20498 </HTML>
20499 ======= h_composer_cntxt_view =======
20500 <HTML>
20501 <HEAD>
20502 <TITLE>Collection View: Explained</TITLE>
20503 </HEAD>
20504 <BODY>
20505 <H1>Collection Edit Help -- View Field</H1>
20507 The collection's "View:" definition provides a way to limit
20508 the displayed list of folders within a collection. By default, only
20509 folders that contain the specified characters anywhere in their name
20510 are shown in the collection's folder list.
20512 <P>
20513 Additionally, you can use a wildcard character to better control
20514 the list of folders selected for display. The wildcard specifier is
20515 the star, "*", character.
20517 <P>
20518 So, for example, to define a collection of all folders ending with
20519 "c", you'd specify a view of "*c" (without the
20520 quote characters!). Or, similarly, to define a collection of folders
20521 whose names start with "a" and end with "z", you'd
20522 specify a view of "a*z".
20524 <P>
20525 <End of help on this topic>
20526 </BODY>
20527 </HTML>
20528 ======= h_composer_abook_add_server =======
20529 <HTML>
20530 <HEAD>
20531 <TITLE>Addressbook Server Name Field Explained</TITLE>
20532 </HEAD>
20533 <BODY>
20534 This field should be left blank if the address book is stored in a regular
20535 file on this system. If it is a remote address book stored on an IMAP
20536 server then this is the name of that IMAP server.
20537 <P>
20538 Look <A HREF="h_edit_nav_cmds">here</A>
20539 to see the available Editing and Navigation commands.
20540 <P>
20541 <End of help on this topic>
20542 </BODY>
20543 </HTML>
20544 ======= h_composer_abook_add_folder =======
20545 <HTML>
20546 <HEAD>
20547 <TITLE>Addressbook Folder Name Field Explained</TITLE>
20548 </HEAD>
20549 <BODY>
20550 For a remote address book (one for which the Server Name is filled in)
20551 this is the name of a folder on the remote server. The address book data
20552 will be stored in this folder. This folder should be used only for
20553 storing this single address book, not for other address books or for
20554 other messages.
20555 <P>
20556 For a local address book (one for which the Server Name is not filled in)
20557 this is the name of a file in which the address book will be stored.
20558 The file is in the same directory as the Alpine configuration file if the
20559 configuration file is local.
20560 If the configuration file is remote, then this will be in the home directory
20561 for Unix Alpine and in the directory specified by the
20562 "-aux local_directory" command line argument.
20563 <P>
20564 Look <A HREF="h_edit_nav_cmds">here</A>
20565 to see the available Editing and Navigation commands.
20566 <P>
20567 <End of help on this topic>
20568 </BODY>
20569 </HTML>
20570 ======= h_composer_abook_add_nick =======
20571 <HTML>
20572 <HEAD>
20573 <TITLE>Addressbook NickName Field Explained</TITLE>
20574 </HEAD>
20575 <BODY>
20576 This is just an optional nickname for this address book. If present, it
20577 is used in some of the displays and error messages in the address book
20578 maintenance screens. It is for your convenience only and serves no
20579 other purpose.
20580 <P>
20581 Look <A HREF="h_edit_nav_cmds">here</A>
20582 to see the available Editing and Navigation commands.
20583 <P>
20584 <End of help on this topic>
20585 </BODY>
20586 </HTML>
20587 ======= h_composer_qserv_cn =======
20588 <HTML>
20589 <HEAD>
20590 <TITLE>Directory Query Form Explained</TITLE>
20591 </HEAD>
20592 <BODY>
20594 Fill in as many of these fields as you wish to narrow down your
20595 search. All the fields you fill in must match in order for an entry
20596 to be returned. You may use the wildcard character "*" in
20597 any of the fields, it matches any zero or more characters at that
20598 point in the string. There are no implicit wildcards, so the match is
20599 exact unless you include wildcards.
20600 <P>
20602 Note that if an attribute isn't present at all, then the match will fail.
20603 For example, if a server doesn't support the Locality attribute, then no
20604 matter what you put in the Locality field (other than leaving it empty)
20605 the search will fail.
20606 <P>
20608 This field, the Common Name field, is typically a person's full name.
20609 <P>
20611 <H1>EDITING and NAVIGATION COMMANDS</H1>
20612 <!--chtml if pinemode="function_key"-->
20613 <PRE>
20614 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
20615 ^B (Left Arrow) Back character | ^D Delete current character
20616 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
20617 ^P (Up Arrow) Previous line |
20618 ^N (Down Arrow) Next line | F9 Cut marked text or
20619 ^A Beginning of line | delete current line
20620 ^E End of line | F10 Undelete line(s)
20621 F7 Previous page |
20622 F8 Next page |-------------------------------------
20623 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
20624 ----------------------------------------|
20625 EXIT COMMANDS | GENERAL COMMANDS | F5 Restore previous search
20626 F2 Cancel | F1 Get help |
20627 F3 Search | ^Z Suspend | ^L Redraw Screen
20628 </PRE>
20629 <!--chtml else-->
20630 <PRE>
20631 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
20632 ^B (Left Arrow) Back character | ^D Delete current character
20633 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
20634 ^P (Up Arrow) Previous line |
20635 ^N (Down Arrow) Next line | ^K Cut marked text or
20636 ^A Beginning of line | delete current line
20637 ^E End of line | ^U Undelete line(s)
20638 ^Y Previous page |
20639 ^V Next page |-------------------------------------
20640 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
20641 ----------------------------------------|
20642 EXIT COMMANDS | GENERAL COMMANDS | ^R Restore previous search
20643 ^C Cancel | ^G Get help |
20644 ^X Search | ^Z Suspend | ^L Redraw Screen
20645 </PRE>
20646 <!--chtml endif-->
20647 <P><UL>
20648 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20649 </UL><P>
20650 <End of help on this topic>
20651 </BODY>
20652 </HTML>
20653 ======= h_composer_qserv_sn =======
20655 The Surname is usually the family name of a person.
20657 <End of help on this topic>
20658 ======= h_composer_qserv_gn =======
20660 This is the part of a person's name that isn't the surname or initials.
20662 <End of help on this topic>
20663 ======= h_composer_qserv_mail =======
20665 This is the email address of a person.
20667 <End of help on this topic>
20668 ======= h_composer_qserv_org =======
20670 This is the organization a person belongs to.
20672 <End of help on this topic>
20673 ======= h_composer_qserv_unit =======
20675 This is the organizational unit a person belongs to.
20677 <End of help on this topic>
20678 ======= h_composer_qserv_country =======
20680 This is the country a person belongs to.
20682 <End of help on this topic>
20683 ======= h_composer_qserv_state =======
20685 This is the state a person belongs to.
20687 <End of help on this topic>
20688 ======= h_composer_qserv_locality =======
20690 This is the locality a person belongs to.
20692 <End of help on this topic>
20693 ======= h_composer_qserv_custom =======
20695 This one is for advanced users only! If you put something in this field,
20696 then the rest of the fields are ignored.
20698 This field may be set to the string representation of an LDAP search
20699 filter (see RFC1960). Here are some examples:
20701 To search for an entry with a surname equal to "clinton" you could set
20702 the custom filter to:
20704 (sn=clinton)
20706 This is equivalent to putting "clinton" in the SurName field.
20707 To search for an entry that has a surname that begins with "clint" and
20708 has a givenname equal to "william" you could use:
20710 (&(sn=clint*)(givenname=william))
20712 This is equivalent to setting the SurName field to "clint*" and the
20713 GivenName field to "william".
20714 To search for an entry where either the common name OR the email address
20715 contains "abcde" you could use:
20717 (|(cn=*abcde*)(mail=*abcde*))
20719 That isn't equivalent to anything you can do by setting the other fields
20720 because of the OR.
20722 <End of help on this topic>
20723 ======= h_composer_qserv_qq =======
20725 This one is a little different from the rest of the categories. It causes
20726 a search to be formed from the configured search filter that you filled
20727 in when you added the directory server to your configuration. It can also
20728 be combined with the other fields if you'd like.
20730 <End of help on this topic>
20731 ======= h_address_format =======
20732 <HTML>
20733 <HEAD>
20734 <TITLE>INTERNET EMAIL ADDRESS FORMAT</TITLE>
20735 </HEAD>
20736 <BODY>
20737 <H1>INTERNET EMAIL ADDRESS FORMAT</H1>
20739 A valid email address on the Internet has a username, an "@" sign,
20740 and then a domain, with no spaces.
20741 For example, jsmith@art.example.com might be the email address
20742 of a person
20743 with the username "jsmith" who has an account in the domain
20744 "art.example.com". The number of dot-separated segments on the
20745 right of the "@" sign can vary - a shorter example would be
20746 isabelle@elsewhere.edu (the shortest possible form: here, only the
20747 organization's domain is specified after the "@" sign); a longer
20748 example would be
20749 jsingh@shakti.edutech.example.com
20750 (here, the name of the host "shakti" in the domain
20751 edutech.example.com is also specified).
20752 <P>
20753 If you do not know the exact email address of someone you want to write
20754 to, ask them what it is using other means of communication than email; or
20755 use the tools for
20756 finding people's addresses that are available on the Internet.
20757 <P>
20758 If you are sending to someone on the same system as you are, you can leave
20759 the "@" sign and all the information to its right off of the
20760 address, and Alpine will fill it in automatically,
20761 unless the feature
20762 <A HREF="h_config_compose_rejects_unqual">"<!--#echo var="FEAT_compose-rejects-unqualified-addrs"-->"</A> is set in SETUP CONFIGURATION.
20763 <P>
20765 When an email address you send a message to is not reachable -- either because
20766 it is simply an incorrect address, or because email can temporarily not be
20767 delivered to it due to a technical problem on the way to or at the recipient's
20768 end -- you will almost always get an error notification email message back.
20769 <P>
20770 If you encounter problems with, or have questions about, email delivery or
20771 email address syntax, contact your local network computing consultants.
20772 <P><UL>
20773 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20774 </UL>
20775 <P>
20776 <End of help on this topic>
20777 </BODY>
20778 </HTML>
20779 ======= h_flag_user_flag =======
20780 <HTML>
20781 <HEAD>
20782 <TITLE>STATUS FLAG: User Defined Keyword</TITLE>
20783 </HEAD>
20784 <BODY>
20785 <H1>STATUS FLAG: User Defined Keyword</h1>
20787 This is a keyword that is defined for this folder.
20788 It was most likely defined by the owner of the folder.
20789 Alpine will not set or clear this flag on its own.
20791 <P><UL>
20792 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20793 </UL><P>
20794 <End of help on this topic>
20795 </BODY>
20796 </HTML>
20797 ======= h_flag_important =======
20798 <html>
20799 <title>STATUS FLAG: Important</title>
20800 <body>
20801 <h1>STATUS FLAG: Important</h1>
20804 The <EM>Important</EM> flag, indicated by an asterisk in Alpine's
20805 MESSAGE INDEX
20806 screen, can only be set by the user, and is intended to be used in
20807 whatever fashion makes sense to you. You are the only one that can set or
20808 clear it.
20810 <P>
20811 <End of help on this topic>
20812 </BODY>
20813 </HTML>
20814 ======= h_flag_new =======
20815 <html>
20816 <title>STATUS FLAG: New</title>
20817 <body>
20818 <h1>STATUS FLAG: New</h1>
20821 The <EM>New</EM> flag, indicated by the letter 'N' in Alpine's
20822 MESSAGE INDEX screen,
20823 is automatically set when messages are delivered to your Inbox (or other
20824 folder specified outside of Alpine). Likewise, it is cleared automatically
20825 the first time you read the message it is associated with.
20827 <P>
20828 Sometimes it's helpful in prioritizing your mail. For example, perhaps
20829 a message isn't weighty enough to assign it an <A HREF="h_flag_important">Important</A> flag, but
20830 you'd like to be reminded of it next time you read mail. This can be done
20831 easily by <A HREF="h_common_flag">explicitly</A> resetting the <EM>New</EM> flag.
20834 <P>
20835 <End of help on this topic>
20836 </BODY>
20837 </HTML>
20838 ======= h_flag_answered =======
20839 <html>
20840 <title>STATUS FLAG: Answered</title>
20841 <body>
20842 <h1>STATUS FLAG: Answered</h1>
20844 The <EM>Answered</EM> flag, indicated by the letter 'A' in Alpine's
20845 MESSAGE INDEX
20846 screen, is automatically set when you reply to a message. This flag is not
20847 automatically cleared.
20849 <P>
20850 <End of help on this topic>
20851 </BODY>
20852 </HTML>
20853 ======= h_flag_forwarded =======
20854 <html>
20855 <title>STATUS FLAG: Forwarded</title>
20856 <body>
20857 <h1>STATUS FLAG: Forwarded</h1>
20859 The <EM>Forwarded</EM> flag, indicated by the letter 'F' in Alpine's
20860 MESSAGE INDEX
20861 screen, is automatically set when you forward a message. This flag is not
20862 automatically cleared.
20864 <P>
20865 <End of help on this topic>
20866 </BODY>
20867 </HTML>
20868 ======= h_flag_deleted =======
20869 <html>
20870 <title>STATUS FLAG: Deleted</title>
20871 <body>
20872 <h1>STATUS FLAG: Deleted</h1>
20874 The <EM>Deleted</EM> flag, indicated by the letter 'D' in Alpine's
20875 MESSAGE INDEX
20876 screen, is set when you use the ""D Delete" command.
20877 It is cleared
20878 when you use the "U Undelete" command.
20880 <P>
20881 Messages marked with this flag will be permanently removed from
20882 the folder when you issue the <A HREF="h_index_cmd_expunge">Expunge</A>
20883 command, or
20884 when you indicate acceptance of their removal upon leaving the folder.
20886 <P>
20887 Note, there can be other actions implicit in the
20888 "D Delete" command,
20889 such as advancing to the next message, that may be momentarily undesirable.
20890 For this reason, it's sometimes useful to set or clear the <EM>Deleted</EM>
20891 flag <A HREF="h_common_flag">explicitly</A>.
20893 <P>
20894 <End of help on this topic>
20895 </BODY>
20896 </HTML>
20897 ====== h_config_incoming_timeo ======
20898 <HTML>
20899 <HEAD>
20900 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></TITLE>
20901 </HEAD>
20902 <BODY>
20903 <H1>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></H1>
20905 This option has no effect unless the feature
20906 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
20907 is set, which in turn has no effect unless
20908 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
20909 is set.
20910 <P>
20911 Sets the time in seconds that Alpine will
20912 attempt to open a network connection used for monitoring for Unseen
20913 messages in Incoming Folders. The default is 5.
20914 If a connection has not completed within this many seconds Alpine will
20915 give up and consider it a failed connection.
20916 <P>
20917 <UL>
20918 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20919 </UL><P>
20920 <End of help on this topic>
20921 </BODY>
20922 </HTML>
20923 ====== h_config_psleep ======
20924 <HTML>
20925 <HEAD>
20926 <TITLE>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</TITLE>
20927 </HEAD>
20928 <BODY>
20929 <H1>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</H1>
20931 <P>
20932 In the good old days a mailcap viewer was used to examine an
20933 attachment before saving it, and after viewing the attachment control
20934 would return to the operating system when the viewer was closed. Therefore,
20935 when the mailcap viewer returned control to the operating system, it
20936 could be assumed that the user who opened the attachment was done
20937 examining it, and the copy of the attachment that was used, could be removed.
20939 <P>
20940 However, today this assumption is not longer valid. Some viewers return
20941 control to the operating system before they actually read the attachment
20942 to be examined. This causes Alpine to delete the attachment before it
20943 is read by the viewer, causing the viewer to fail opening the attachment.
20945 <P>
20946 In order to work around this problem, Alpine checks, after the viewer has
20947 returned control to the operating system, if there is any process that is
20948 using the attachment. This variable controls the number of seconds that
20949 must elapse between checks. Once it is found that no process is using the
20950 attachment, this is removed.
20952 <P>
20953 The minimum value for this variable is 60 (checks will be made once per
20954 minute), and the maximum value is 600 (checks will be made once every 10
20955 minutes). The default value is 60.
20957 <P>
20958 <UL>
20959 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20960 </UL><P>
20961 <End of help on this topic>
20962 </BODY>
20963 </HTML>
20964 ====== h_config_incoming_interv ======
20965 <HTML>
20966 <HEAD>
20967 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval"--></TITLE>
20968 </HEAD>
20969 <BODY>
20970 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval"--></H1>
20972 This option has no effect unless the feature
20973 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
20974 is set, which in turn has no effect unless
20975 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
20976 is set.
20977 <P>
20978 This option specifies, in seconds, how often Alpine will check
20979 for new mail and state changes in Incoming Folders when Incoming Folders
20980 Checking is turned on.
20981 The default is 3 minutes (180).
20982 This value applies only to folders that are local to the system that
20983 Alpine is running on or that are accessed using the IMAP protocol.
20984 The similar option
20985 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>
20986 applies to all other monitored folders.
20987 <P>
20988 <UL>
20989 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20990 </UL><P>
20991 <End of help on this topic>
20992 </BODY>
20993 </HTML>
20994 ====== h_config_incoming_second_interv ======
20995 <HTML>
20996 <HEAD>
20997 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></TITLE>
20998 </HEAD>
20999 <BODY>
21000 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></H1>
21002 This option has no effect unless the feature
21003 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21004 is set, which in turn has no effect unless
21005 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21006 is set.
21007 <P>
21008 This option together with the option
21009 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
21010 specifies, in seconds, how often Alpine will check
21011 for new mail and state changes in Incoming Folders when Incoming Folders
21012 Checking is turned on.
21013 The default for this option is 3 minutes (180).
21014 For folders that are local to this system or
21015 that are accessed using the IMAP protocol
21016 the value of the option
21017 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
21018 is used.
21019 For all other monitored folders, the value of this option is used.
21020 <P>
21021 The reason there are two separate options is because it is usually
21022 less expensive to check local and IMAP folders than it is to check
21023 other types, like POP or NNTP folders.
21024 You may want to set this secondary value to a higher number than
21025 the primary check interval.
21026 <P>
21027 <UL>
21028 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21029 </UL><P>
21030 <End of help on this topic>
21031 </BODY>
21032 </HTML>
21033 ====== h_config_incoming_list ======
21034 <HTML>
21035 <HEAD>
21036 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-list"--></TITLE>
21037 </HEAD>
21038 <BODY>
21039 <H1>OPTION: <!--#echo var="VAR_incoming-check-list"--></H1>
21041 This option has no effect unless the feature
21042 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21043 is set, which in turn has no effect unless
21044 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21045 is set.
21046 <P>
21047 When monitoring the Incoming Message Folders for Unseen messages Alpine will
21048 normally monitor all Incoming Folders.
21049 You may use this option to restrict the list of monitored folders to a
21050 subset of all Incoming Folders.
21051 <P>
21052 <UL>
21053 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21054 </UL><P>
21055 <End of help on this topic>
21056 </BODY>
21057 </HTML>
21058 ====== h_config_pers_name ======
21059 <HTML>
21060 <HEAD>
21061 <TITLE>OPTION: <!--#echo var="VAR_personal-name"--></TITLE>
21062 </HEAD>
21063 <BODY>
21064 <H1>OPTION: <!--#echo var="VAR_personal-name"--></H1>
21066 This value is used to determine the full name part of the "From" address
21067 on messages you send.
21068 <!--chtml if pinemode="os_windows"-->
21069 PC-Alpine requires that this be set in order to properly construct the "From" address.
21070 <!--chtml else-->
21071 If unset, Unix Alpine will obtain your full name from
21072 the system password file. PC-Alpine, on the other hand, requires that this be set.
21073 <!--chtml endif-->
21074 <P>
21075 If you want to change the value of what gets included in the From header
21076 in messages you send (other than just the Personal Name)
21077 look <A HREF="h_config_change_your_from">here</A> for a description.
21078 <P><UL>
21079 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21080 </UL><P>
21081 <End of help on this topic>
21082 </BODY>
21083 </HTML>
21084 ====== h_config_pruned_folders ======
21085 <html>
21086 <header>
21087 <title>OPTION: <!--#echo var="VAR_pruned-folders"--></title>
21088 </header>
21089 <body>
21090 <h1>OPTION: <!--#echo var="VAR_pruned-folders"--></h1>
21092 This variable allows you to define a list of one or more folders that
21093 Alpine will offer to prune for you in the same way it automatically offers
21094 to prune your "sent-mail" folder each month.
21095 Each folder in this list must be a folder in your default folder collection
21096 (the first folder collection if you have more than one), and it is just
21097 the relative name of the folder in the collection, not the fully-qualified name.
21098 It is similar to sent-mail.
21099 Instead of something like
21100 <P>
21101 <CENTER><SAMP><!--#echo var="VAR_pruned-folders"-->={servername}mail/folder</SAMP></CENTER>
21102 <P>
21103 the correct value to use would be
21104 <P>
21105 <CENTER><SAMP>folder</SAMP></CENTER>
21106 <P>
21107 There is an assumption here that your first collection is the folders in
21108 <P>
21109 <CENTER><SAMP>{servername}mail</SAMP></CENTER>
21110 <P>
21112 Once a month, for each folder listed, Alpine will offer to move
21113 the contents of the folder to a new folder of the same name but with
21114 the previous month's date appended. Alpine will then look for any such
21115 date-appended folder names created for a previous month, and offer each
21116 one it finds for deletion.
21117 <P>
21119 If you decline the first offer, no mail is moved and no new folder is
21120 created.
21121 <P>
21123 The new folders will be created
21124 in your default folder collection.
21125 <P>
21127 <UL>
21128 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21129 </UL><P>
21130 <End of help on this topic>
21131 </body>
21132 </html>
21133 ====== h_config_upload_cmd ======
21134 <HTML>
21135 <HEAD>
21136 <TITLE>OPTION: <!--#echo var="VAR_upload-command"--></TITLE>
21137 </HEAD>
21138 <BODY>
21139 <H1>OPTION: <!--#echo var="VAR_upload-command"--></H1>
21141 This option affects the behavior of the Composer's "Read File"
21142 (^R in the message body) and "Attach File" (^J in the header)
21143 commands. It specifies
21144 a Unix program name, and any necessary command line arguments, that Alpine can
21145 use to transfer files from your personal computer into messages that you are
21146 composing.<P>
21148 <B>Note:</B> this facility is intended for use with serial line transfer
21149 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
21150 to work with TCP/IP file transfer programs such as ftp.<P>
21152 If a program is specified, the commands listed above are modified to offer a
21153 subcommand (^Y) to activate the transfer. Obviously, the Unix program
21154 specified here must match the transfer program or protocol available on the
21155 personal computer.<P>
21157 Alpine expects to exchange uploaded data via a file on your Unix system. When
21158 the specified upload program finishes, Alpine expects the uploaded data to be
21159 contained in this file.<P>
21161 When upload is invoked via the "Read File" subcommand, Alpine
21162 generates a
21163 temporary file name that it will pass to the specified Unix program. Alpine
21164 will read the resulting uploaded text from this file and then delete it when
21165 the upload command is finished.<P>
21167 When upload is invoked via the "Attach File" subcommand, Alpine will
21168 prompt
21169 you for the name of the file that is to contain the uploaded information that
21170 it is to attach. Alpine will attach this file to the composition, but will
21171 <B>not</B> delete this file after the upload command is finished.<P>
21173 The special token "_FILE_" may be included among the Unix program's
21174 command
21175 line arguments. Alpine will replace this symbol with the name of the file
21176 being used to exchange the uploaded information. This token allows you to
21177 position the file name where it is required in the Unix program's command
21178 line arguments.<P>
21180 If the "_FILE_" token is not present in the specified command, the
21181 temporary file's name is automatically appended to the specified Unix
21182 program. In other words, you don't need to use "_FILE_" if it is the
21183 <B>last</B> command line argument.
21184 <P><UL>
21185 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21186 </UL><P>
21187 <End of help on this topic>
21188 </BODY>
21189 </HTML>
21190 ====== h_config_upload_prefix ======
21191 <HTML>
21192 <HEAD>
21193 <TITLE>OPTION: <!--#echo var="VAR_upload-command-prefix"--></TITLE>
21194 </HEAD>
21195 <BODY>
21196 <H1>OPTION: <!--#echo var="VAR_upload-command-prefix"--></H1>
21198 This option is used in conjunction with the <!--#echo var="VAR_upload-command"--> option.
21199 It defines text to be written to the terminal emulator (via standard output)
21200 immediately prior to starting upload command. This is useful for
21201 integrated serial line file transfer agents that permit command passing
21202 (e.g., Kermit's APC method).<P>
21204 The special token "_FILE_" may be included in the string specification.
21205 That symbol will be replaced with the (Alpine-created) name of the temporary
21206 file in which Alpine will expect to find the uploaded file.
21207 <P><UL>
21208 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21209 </UL><P>
21210 <End of help on this topic>
21211 </BODY>
21212 </HTML>
21213 ====== h_config_download_cmd ======
21214 <HTML>
21215 <HEAD>
21216 <TITLE>OPTION: <!--#echo var="VAR_download-command"--></TITLE>
21217 </HEAD>
21218 <BODY>
21219 <H1>OPTION: <!--#echo var="VAR_download-command"--></H1>
21221 This option affects the behavior of the Export command. It specifies a Unix
21222 program name, and any necessary command line arguments, that Alpine can use to
21223 transfer the exported message to your personal computer's disk.<P>
21224 Note: this facility is intended for use with serial line transfer
21225 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
21226 to work with TCP/IP file transfer programs such as ftp.<P>
21227 If a program is specified, the Export command is modified to offer a
21228 subcommand (^V) to activate the transfer (in lieu of saving it to
21229 the machine where Alpine is running). Obviously, the Unix program
21230 specified here must match the transfer program or protocol available on the
21231 personal computer.<P>
21233 When this subcommand is selected and before Alpine invokes the specified Unix
21234 program, Alpine will create a temporary file containing the text of the
21235 exported message. Alpine uses this file to pass the exported message text to
21236 the specified Unix program.<P>
21238 The special token "_FILE_" may be included among the Unix program's command
21239 line arguments. Alpine will replace this symbol with the temporary file's name
21240 before executing the Unix program. This token allows you to position the
21241 file name where it is required in the Unix program's command line arguments.
21242 <P>
21243 If the "_FILE_" token is not present in the specified command, the
21244 temporary file's name is automatically appended to the specified Unix
21245 program. In other words, you don't need to use "_FILE_" if it is the
21246 <B>last</B> command line argument.
21247 <P><UL>
21248 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21249 </UL><P>
21250 <End of help on this topic>
21251 </BODY>
21252 </HTML>
21253 ====== h_config_download_prefix ======
21254 <HTML>
21255 <HEAD>
21256 <TITLE>OPTION: <!--#echo var="VAR_download-command-prefix"--></TITLE>
21257 </HEAD>
21258 <BODY>
21259 <H1>OPTION: <!--#echo var="VAR_download-command-prefix"--></H1>
21261 This option is used in conjunction with the <!--#echo var="VAR_download-command"--> option.
21262 It defines text to be written to the terminal emulator (via standard output)
21263 immediately prior to starting the download command. This is useful for
21264 integrated serial line file transfer agents that permit command passing
21265 (e.g., Kermit's APC method).
21266 <P>
21267 The special token "_FILE_" may be included in the string
21268 specification.
21269 That symbol will be replaced with the (Alpine-created) name of the temporary
21270 file into which Alpine will place the message to be downloaded.
21271 <P><UL>
21272 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21273 </UL><P>
21274 <End of help on this topic>
21275 </BODY>
21276 </HTML>
21277 ====== h_config_mailcap_path ======
21278 <HTML>
21279 <HEAD>
21280 <TITLE>OPTION: <!--#echo var="VAR_mailcap-search-path"--></TITLE>
21281 </HEAD>
21282 <BODY>
21283 <H1>OPTION: <!--#echo var="VAR_mailcap-search-path"--></H1>
21284 This variable is used to replace Alpine's default mailcap file search path.
21285 It takes one or more file names (full paths must be specified) in which to
21286 look for mail capability data. The default search path can be found in this
21287 <A HREF="h_news_config">Alpine Configuration</A> help, near the bottom.
21288 If there is more than one file name listed, list members should be delimited
21289 by
21290 <!--chtml if pinemode="os_windows"-->
21291 a semi-colon (;) under Windows; for example:<PRE>
21292 C:\MYCONFIG\MAILCAP.TXT;H:\NETCONFIG\MAILCAP.TXT
21293 </PRE>
21294 <!--chtml else-->
21295 a colon (:) under UNIX; for example:<PRE>
21296 ~/.mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
21297 </PRE>
21298 <!--chtml endif-->
21299 <P><UL>
21300 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21301 </UL>
21302 <P>
21303 <End of help on this topic>
21304 </BODY>
21305 </HTML>
21306 ====== h_config_mimetype_path ======
21307 <HTML>
21308 <HEAD>
21309 <TITLE>OPTION: <!--#echo var="VAR_mimetype-search-path"--></TITLE>
21310 </HEAD>
21311 <BODY>
21312 <H1>OPTION: <!--#echo var="VAR_mimetype-search-path"--></H1>
21314 This variable is used to replace Alpine's default mime.types file search path.
21315 It takes one or more file names (full paths must be specified) in which to
21316 look for file-name-extension to MIME type mapping data. The default search
21317 path can be found in this
21318 <A HREF="h_news_config">Alpine Configuration</A> help.
21320 <P>
21322 If there is more than one file name listed, list members should be delimited
21323 by a colon (:) under UNIX and a semi-colon (;) under Windows.
21324 <P>
21325 <End of help on this topic>
21326 </BODY></HTML>
21327 ====== h_config_set_att_ansi ======
21328 <HTML><HEAD>
21329 <TITLE>OPTION: Set printer to attached ansi printer</TITLE>
21330 </HEAD>
21331 <BODY>
21332 <H1>OPTION: Set printer to attached ansi printer</H1>
21334 Type "S" to set your printer to "attached-to-ansi".<BR>
21335 It is OK to include "attached-to-ansi" in your personal list below.
21336 <P>
21337 <End of help on this topic>
21338 </BODY></HTML>
21339 ====== h_config_set_att_ansi2 ======
21340 <HTML><HEAD>
21341 <TITLE>OPTION: Set printer to attached ansi printer (no formfeed)</TITLE>
21342 </HEAD>
21343 <BODY>
21344 <H1>OPTION: Set printer to attached ansi printer (no formfeed)</H1>
21346 Type "S" to set your printer to "attached-to-ansi-no-formfeed".<BR>
21347 It is OK to include "attached-to-ansi-no-formfeed" in your personal
21348 list below.
21350 <P>
21352 This is the same as the "attached-to-ansi" option except that a
21353 formfeed character will not be appended to the end of the print job.
21354 If your printer already ejects the paper by itself at the end of the
21355 job, you may prefer the "no-formfeed" form of this printer so that you
21356 don't get an extra blank page between print jobs.
21357 <P>
21359 <End of help on this topic>
21360 </BODY></HTML>
21361 ====== h_config_set_att_wyse ======
21362 <HTML><HEAD>
21363 <TITLE>OPTION: Set printer to attached Wyse60 printer</TITLE>
21364 </HEAD>
21365 <BODY>
21366 <H1>OPTION: Set printer to attached Wyse60 printer</H1>
21368 Type "S" to set your printer to "attached-to-wyse".<BR>
21369 It is OK to include "attached-to-wyse" in your personal list below.
21370 <P>
21371 This is very similar to "attached-to-ansi".
21372 The only difference is in the control characters sent to turn the printer
21373 on and off.
21374 The ansi version of the printer uses ESC LEFT_BRACKET 5 i
21375 to turn on the printer and ESC LEFT_BRACKET 4 i
21376 to turn it off.
21377 The Wyse version uses Ctrl-R for on, and Ctrl-T for off.
21378 <End of help on this topic>
21379 </BODY></HTML>
21380 ====== h_config_set_att_wyse2 ======
21381 <HTML><HEAD>
21382 <TITLE>OPTION: Set printer to attached Wyse60 printer (no formfeed)</TITLE>
21383 </HEAD>
21384 <BODY>
21385 <H1>OPTION: Set printer to attached Wyse60 printer (no formfeed)</H1>
21387 Type "S" to set your printer to "attached-to-wyse-no-formfeed".<BR>
21388 It is OK to include "attached-to-wyse-no-formfeed" in your personal
21389 list below.
21391 <P>
21393 This is the same as the "attached-to-wyse" option except that a
21394 formfeed character will not be appended to the end of the print job.
21395 If your printer already ejects the paper by itself at the end of the
21396 job, you may prefer the "no-formfeed" form of this printer so that you
21397 don't get an extra blank page between print jobs.
21398 <P>
21400 <End of help on this topic>
21401 </BODY></HTML>
21402 ====== h_config_set_stand_print ======
21403 <HTML>
21404 <HEAD>
21405 <TITLE>OPTION: Set default printer</TITLE>
21406 </HEAD>
21407 <H1>OPTION: Set default printer</H1>
21408 <BODY>
21409 Move to the printer you want and type "S" to set it to be your
21410 default printer. This list is not modifiable by you and has been
21411 set up by the system administrators. If there is more than one printer
21412 listed in the Command List, you will be able to cycle through that
21413 whole list at the time you print, starting with your default.
21414 It is OK to include entries from this Standard list in your personal
21415 list below.
21416 <P>
21417 <End of help on this topic>
21418 </BODY>
21419 </HTML>
21420 ====== h_config_set_custom_print ======
21421 <HTML>
21422 <HEAD>
21423 <TITLE>OPTION: Set default printer</TITLE>
21424 </HEAD>
21425 <H1>OPTION: Set default printer</H1>
21426 <BODY>
21427 You may add as many print commands as you want to your personal list.
21428 Specify one of them as your default printer by moving to the printer
21429 you want and typing "S". If there is more than one printer listed
21430 in the Command List, you will be able to cycle through that list at
21431 the time you print, starting with your default. It is OK to include
21432 entries from the Standard list above or to include the command
21433 "attached-to-ansi", "attached-to-ansi-no-formfeed", "attached-to-wyse", or
21434 "attached-to-wyse-no-formfeed" as one of the entries here.
21435 <P>
21436 <End of help on this topic>
21437 </BODY>
21438 </HTML>
21439 ====== h_config_user_id =====
21440 <HTML>
21441 <HEAD>
21442 <TITLE>OPTION: <!--#echo var="VAR_user-id"--></TITLE>
21443 </HEAD>
21444 <BODY>
21445 <H1>OPTION: <!--#echo var="VAR_user-id"--></H1>
21447 This value is used as part of the "From" address on messages you send.
21448 It is also the default login name for remote IMAP server access. Set this
21449 to the username part you want to appear on outgoing email.
21450 <P>
21451 If you want to change the value of what gets included in the From header
21452 in messages you send (other than just the User ID)
21453 look <A HREF="h_config_change_your_from">here</A> for a description.
21455 <P><UL>
21456 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21457 </UL><P>
21458 <End of help on this topic>
21459 </BODY>
21460 </HTML>
21461 ====== h_config_user_dom =====
21462 <HTML>
21463 <HEAD>
21464 <TITLE>OPTION: <!--#echo var="VAR_user-domain"--></TITLE>
21465 </HEAD>
21466 <BODY>
21467 <H1>OPTION: <!--#echo var="VAR_user-domain"--></H1>
21469 This value specifies the domain part (right-hand side) of your return
21470 address on outgoing email and is also used as the default domain for email
21471 composed to a local user.
21472 <!--chtml if pinemode="os_windows"-->
21473 This value is required for PC-Alpine. If you are unsure as to what this should be,
21474 contact your local help desk, system administrator, or Internet Service Provider.
21475 <!--chtml else-->
21476 If unset, Unix Alpine will obtain the domain from
21477 the system. Often this value will be set for your whole site by the
21478 system administrator.<P>
21479 <!--chtml endif-->
21480 If you set this, see also the <A HREF="h_config_quell_local_lookup">
21481 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
21482 <P>
21483 If you want to change the value of what gets included in the From header
21484 in messages you send (other than just the User Domain)
21485 look <A HREF="h_config_change_your_from">here</A> for a description.
21486 <P><UL>
21487 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21488 </UL><P>
21489 <End of help on this topic>
21490 </BODY>
21491 </HTML>
21492 ====== h_config_smtp_server =====
21493 <HTML>
21494 <HEAD>
21495 <TITLE>OPTION: <!--#echo var="VAR_smtp-server"--></TITLE>
21496 </HEAD>
21497 <BODY>
21498 <H1>OPTION: <!--#echo var="VAR_smtp-server"--></H1>
21499 This value specifies the name of one or more SMTP
21500 (Simple Mail Transfer Protocol) servers for sending mail.
21501 <!--chtml if pinemode="os_windows"-->
21502 You must have an SMTP server for use with PC-Alpine.
21503 SMTP servers are
21504 normally set up by a system administrator for use by all members of a given
21505 campus or department.
21506 Contact your local help desk to ask what SMTP
21507 servers you should use.
21508 <!--chtml else-->
21509 Unix Alpine users may not need to set an SMTP server.
21510 Alpine will attempt to execute the program (usually sendmail) that is used
21511 to insert mail into the mail system.
21512 If this works for you, you may leave this option blank.
21513 If there is an SMTP server running on the Unix host you may be able to
21514 improve sending performance slightly by setting the SMTP server option
21515 to "localhost" or to the actual name of the Unix host.
21516 <P>
21517 If the Unix host doesn't work the way Alpine was expecting you will need to
21518 set the value of this option.
21519 SMTP servers are
21520 normally set up by a system administrator for use by all members of a given
21521 campus or department.
21522 Contact your local help desk to ask what SMTP
21523 servers you should use.
21524 <!--chtml endif-->
21525 <P>
21526 Your SMTP server may offer SMTP AUTH authentication.
21527 It may even require it.
21528 If your SMTP server offers SMTP AUTH authentication you may specify a
21529 "user" name parameter to cause Alpine to attempt to authenticate.
21530 This parameter requires an associated value,
21531 the username identifier with which to establish the server
21532 connection.
21533 An example might be:
21535 <P>
21536 <CENTER><SAMP>smtpserver.example.com/user=katie</SAMP></CENTER>
21537 <P>
21539 If AUTH authentication is offered by the server, this will cause Alpine to
21540 attempt to use it.
21541 If AUTH authentication is not offered by the server, this will cause Alpine
21542 to fail sending with an error similar to:
21544 <P>
21545 <CENTER><SAMP>Error: SMTP authentication not available</SAMP></CENTER>
21546 <P>
21548 Another type of authentication that is used by some ISPs is called
21549 "POP before SMTP" or "IMAP before SMTP",
21550 which means that you have to authenticate
21551 yourself to the POP or IMAP server by opening a mailbox before you
21552 can send mail.
21553 To do this, you usually only have to open your INBOX.
21555 <P>
21556 You may tell Alpine to use the
21557 <A HREF="http://www.ietf.org/rfc/rfc2476.txt">Message Submission</A>
21558 port (587) instead of the SMTP port (25) by including the "submit"
21559 parameter
21560 in this option.
21561 At this time "/submit" is simply equivalent to specifying
21562 port 587, though it may imply more than that at some point in the future.
21563 Some ISPs are blocking port 25 in order to reduce the amount of spam
21564 being sent to their users.
21565 You may find that the submit option allows you to get around such a block.
21567 <P>
21568 <CENTER><SAMP>smtpserver.example.com/submit</SAMP></CENTER>
21569 <P>
21571 To specify any non-standard port number on the SMTP server you may follow
21572 the hostname with a colon followed by the portnumber.
21574 <P>
21575 <CENTER><SAMP>smtpserver.example.com:12345</SAMP></CENTER>
21576 <P>
21578 Normally, when a connection is made to the Smtp-Server Alpine will attempt
21579 to negotiate a secure (encrypted) session using Transport Layer Security (TLS).
21580 If that fails then a non-encrypted connection will be attempted instead.
21581 You may specify that a TLS connection is required if you wish.
21582 If you append "/tls" to the name then the connection will fail
21583 instead of falling back to a non-secure connection.
21585 <P>
21586 <CENTER><SAMP>smtpserver.example.com/tls</SAMP></CENTER>
21587 <P>
21590 For more details about server name possibilities see
21591 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
21592 <P>
21594 <UL>
21595 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21596 </UL>
21597 <P>
21598 <End of help on this topic>
21599 </BODY>
21600 </HTML>
21601 ====== h_config_nntp_server =====
21602 <HTML>
21603 <HEAD>
21604 <TITLE>OPTION: <!--#echo var="VAR_nntp-server"--></TITLE></HEAD>
21605 <BODY>
21606 <H1>OPTION: <!--#echo var="VAR_nntp-server"--></H1>
21608 This value specifies the name of one or more NNTP
21609 (Network News Transfer Protocol)
21610 servers for reading and posting USENET news.
21611 NNTP servers are normally
21612 set up by a system administrator for use by all members of a given campus
21613 or department.
21614 Contact your local help desk to ask what NNTP servers you should use.
21615 <!--chtml if pinemode="os_windows"--><!--chtml else-->
21616 Often Unix Alpine users will find that this variable has been
21617 set for the whole system (and they don't have to worry about it).
21618 <!--chtml endif-->
21619 When you define an NNTP server here, Alpine implicitly defines a news
21620 collection for you, assuming that server as the news server and assuming
21621 that you will use the NNTP protocol and a local newsrc configuration file
21622 for reading news.
21623 For more about reading news with Alpine, see
21624 <A HREF="h_reading_news">how to use Alpine to read news</A>.
21625 <P>
21626 Your NNTP server may offer NNTP "AUTHINFO SASL"
21627 or "AUTHINFO USER" authentication.
21628 It may even require it.
21629 If your NNTP server does offer such authentication you may specify a user name
21630 parameter to cause Alpine to attempt to authenticate.
21631 The same is true for the server name in a folder collection that uses NNTP.
21632 This parameter requires an associated value,
21633 the username identifier with which to establish the server connection.
21634 An example might be:
21636 <P>
21637 <CENTER><SAMP>nntpserver.example.com/user=katie</SAMP></CENTER>
21638 <P>
21640 If authentication is offered by the server, this will cause Alpine to
21641 attempt to use it.
21642 If authentication is not offered by the server, this will cause Alpine
21643 to fail with an error similar to:
21645 <P>
21646 <CENTER><SAMP>Error: NNTP authentication not available</SAMP></CENTER>
21647 <P>
21648 For more details about the server name possibilities see
21649 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
21650 <P><UL>
21651 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21652 </UL><P>
21653 <End of help on this topic>
21654 </BODY>
21655 </HTML>
21656 ====== h_config_inbox_path =====
21657 <HTML>
21658 <HEAD>
21659 <TITLE>OPTION: <!--#echo var="VAR_inbox-path"--></TITLE>
21660 </HEAD>
21661 <BODY>
21662 <H1>OPTION: <!--#echo var="VAR_inbox-path"--></H1>
21664 This value overrides the default value of your INBOX name/path/location.
21665 <!--chtml if pinemode="os_windows"-->
21666 PC-Alpine users must specify an inbox path and it must be a folder on an
21667 IMAP server.
21668 <!--chtml else-->
21669 Unix and VMS Alpine users will often find that this variable
21670 has been pre-configured by your system administrator.
21671 <!--chtml endif-->
21672 You may be able to specify an alternate INBOX that is either a local folder
21673 or a folder on an IMAP server.
21674 <P>
21675 A typical remote <!--#echo var="VAR_inbox-path"--> entry would be: {monet.art.example.com}INBOX
21676 where "monet.art.example.com" is replaced by the name of your IMAP
21677 mail server.
21678 <P>
21679 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21680 details on the syntax of folder definitions.
21681 <P>
21682 See <A HREF="h_info_on_mbox">Missing mail and the mbox driver</A> if your
21683 mail is disappearing.
21684 <P><UL>
21685 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21686 </UL><P>
21687 <End of help on this topic>
21688 </BODY>
21689 </HTML>
21690 ====== h_config_change_your_from =====
21691 <HTML>
21692 <HEAD>
21693 <TITLE>How to Change your From Address</TITLE>
21694 </HEAD>
21695 <BODY>
21696 <H1>How to Change your From Address</H1>
21698 If the From address that Alpine includes in mail that you send is not correct,
21699 you may want to configure a different default value for the From address.
21700 You may follow these directions to change the default:
21702 <P>
21703 <UL>
21704 <LI> Go to the Main Alpine Menu
21705 <LI> From there type the Setup Command
21706 <LI> From there type the Config Command
21707 </UL>
21709 <P>
21710 You've probably already seen this SETUP CONFIGURATION screen.
21711 If not, there are many options you may want to set here.
21712 To set the value of the From header you may use the
21713 <A href="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> option.
21714 Find it by scrolling down a few pages or use the WhereIs command to
21715 search for "customized".
21716 You may want to read the help text associated with the option.
21717 <P>
21718 To add a custom From header, type the Add command and enter the
21719 full header line, including the leading "From: ".
21720 For example:
21721 <P>
21722 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
21723 <P>
21724 Now exit the Setup command and try sending mail to yourself to see
21725 what the From line looks like.
21726 <P>
21727 When you are in the composer you may edit the custom From line by typing
21728 Ctrl-R while your cursor is in the headers of the message and then moving
21729 to the From line and editing.
21730 If you want to leave the default value the same but add the possibility
21731 of being able to edit the header when you compose, add just the header
21732 name without a value.
21733 For example:
21734 <P>
21735 <CENTER><SAMP>From:</SAMP></CENTER>
21736 <P>
21737 If you change your From address you may also find it useful to add the
21738 changed From address to the
21739 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
21740 configuration option.
21741 <P>
21742 <UL>
21743 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21744 </UL><P>
21745 <End of help on this topic>
21746 </BODY>
21747 </HTML>
21748 ====== h_config_default_fcc =====
21749 <HTML>
21750 <HEAD>
21751 <TITLE>OPTION: <!--#echo var="VAR_default-fcc"--></TITLE>
21752 </HEAD>
21753 <BODY>
21754 <H1>OPTION: <!--#echo var="VAR_default-fcc"--></H1>
21756 This value specifies where a copy of outgoing mail should be saved. If
21757 this is not a path name, it will be in the default collection for saves.
21758 Any valid folder specification, local or IMAP, is allowed. This default
21759 folder carbon copy only applies when the
21760 <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
21761 is set to use the default folder.
21762 <!--chtml if pinemode="os_windows"-->
21763 PC-Alpine default is "SENTMAIL" (normally stored as SENTMAIL.MTX)
21764 <!--chtml else-->
21765 Unix Alpine default
21766 is normally "sent-mail" in the default folder collection.
21767 <!--chtml endif-->
21768 <P>
21769 If you access your email through an IMAP server, especially if you often switch between Unix Alpine
21770 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on your
21771 IMAP server (remember that in order to later access this remote folder through Alpine, it
21772 must be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
21773 for more information). An example:<p>
21774 <CENTER><SAMP>{monet.art.example.com}mail/sent-mail</SAMP></CENTER>
21775 <P>
21776 To suppress saving of outgoing mail, set: <!--#echo var="VAR_default-fcc"-->=""
21777 <P>
21778 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21779 details on the syntax of folder definitions.
21780 <P>
21781 <UL>
21782 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21783 </UL><P>
21784 <End of help on this topic>
21785 </BODY>
21786 </HTML>
21787 ====== h_config_def_save_folder =====
21788 <HTML>
21789 <HEAD>
21790 <TITLE>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></TITLE>
21791 </HEAD>
21792 <BODY>
21793 <H1>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></H1>
21795 This option determines the default folder name for save-message operations
21796 ("saves").
21797 <P>
21798 If this is not a path name, it will be in the default collection for saves.
21799 Any valid folder specification, local or IMAP, is allowed. This default
21800 folder only applies when the
21801 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
21802 doesn't override it.
21803 <!--chtml if pinemode="os_windows"-->
21804 PC-Alpine default is "SAVEMAIL" (normally stored as SAVEMAIL.MTX).
21805 <!--chtml else-->
21806 Unix Alpine default
21807 is normally "saved-messages" in the default folder collection.
21808 <!--chtml endif-->
21809 If you access your email through an IMAP server, especially if you often switch between Unix
21810 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on an
21811 IMAP server (remember that in order to later access this remote folder through Alpine, it
21812 should be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
21813 for more information). An example:<p>
21814 <CENTER><SAMP>{monet.art.example.com}mail/saved-messages</SAMP></CENTER>
21815 <P>
21816 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21817 details on the syntax of folder definitions.
21818 <P>
21819 <UL>
21820 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21821 </UL><P>
21822 <End of help on this topic>
21823 </BODY>
21824 </HTML>
21825 ====== h_config_postponed_folder =====
21826 <HTML>
21827 <HEAD>
21828 <TITLE>OPTION: <!--#echo var="VAR_postponed-folder"--></TITLE>
21829 </HEAD>
21830 <BODY>
21831 <H1>OPTION: <!--#echo var="VAR_postponed-folder"--></H1>
21833 This value overrides the default name for the folder where postponed
21834 messages are saved. If this is not a path name, it will be in the default
21835 collection for message Saves. Any valid folder specification, local or
21836 remote, is allowed.
21837 PC-Alpine default
21838 is "POSTPOND" (stored as POSTPOND.MTX).
21839 The Unix Alpine default is normally "postponed-msgs"
21840 in the default collection.
21841 <P>
21842 Tip: If you are using different installations of (PC-)Alpine -- for example, PC-Alpine on your personal
21843 computer at home, and Unix Alpine on campus -- you can postpone a composition begun with one Alpine and
21844 resume it later with the other if you set this option to the <B>same folder on the same IMAP host</B>
21845 in all Alpine copies you use.
21846 (Remember that in order to later access this remote folder through Alpine, it must be in a folder
21847 collection. See <A HREF="h_what_are_collections">Folder Collections Extensions Explained</a>
21848 for more information). An
21849 example:<p>
21850 <CENTER><SAMP>{monet.art.example.com}mail/postponed-msgs</SAMP></CENTER>
21851 <P>
21852 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21853 details on the syntax of folder definitions.
21854 <P>
21855 <UL>
21856 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21857 </UL><P>
21858 <End of help on this topic>
21859 </BODY>
21860 </HTML>
21861 ====== h_config_read_message_folder =====
21862 <HTML>
21863 <HEAD>
21864 <TITLE>OPTION: <!--#echo var="VAR_read-message-folder"--></TITLE>
21865 </HEAD>
21866 <BODY>
21867 <H1>OPTION: <!--#echo var="VAR_read-message-folder"--></H1>
21869 By virtue of specifying a folder name here, Alpine will be configured to
21870 save all messages that you have read during a session into the designated
21871 "read messages" folder. This allows you to more easily distinguish
21872 between your really new email (in your INBOX) and those that you have
21873 already read. Depending on how you define the
21874 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
21875 setting, you may or may not be asked when you quit
21876 Alpine if you want read messages to be moved to this folder. In either
21877 case, moving the messages means they will be deleted from your INBOX.
21878 <P>
21879 If this is not a path name, it will be in the default collection for
21880 saves. Any valid folder specification, local or remote (via IMAP), is
21881 allowed. There is no default for the name of the read message folder.
21882 <P>
21883 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21884 details on the syntax of folder definitions.
21885 <P>
21886 <UL>
21887 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21888 </UL><P>
21889 <End of help on this topic>
21890 </BODY>
21891 </HTML>
21892 ====== h_config_form_folder =====
21893 <HTML>
21894 <HEAD>
21895 <TITLE>OPTION: <!--#echo var="VAR_form-letter-folder"--></TITLE>
21896 </HEAD>
21897 <BODY>
21898 <H1>OPTION: <!--#echo var="VAR_form-letter-folder"--></H1>
21900 A "<!--#echo var="VAR_form-letter-folder"-->" is a mail folder that is intended to
21901 contain messages that you have composed and that are intended to be
21902 sent in their original form repeatedly.
21904 <P>
21905 Setting this variable will alter Alpine's usual behavior when you
21906 execute the Compose command. Normally, Alpine offers a chance to
21907 continue a postponed or interrupted message should one or the other
21908 exist. When this variable is set to a folder name that exists, Alpine
21909 will also offer the chance to select a message from the folder to
21910 insert into the composer (much like when continuing a postponed message).
21911 The difference, however, is that Alpine will not automatically delete
21912 the selected message from the Form Letter Folder.
21913 <P>
21914 Setting this variable will also affect Alpine's behavior when you
21915 Postpone a message from the composer. Normally, Alpine simply stashes
21916 the message away in your
21917 "<A HREF="h_config_postponed_folder"><!--#echo var="VAR_postponed-folder"--></A>".
21918 Regardless of the specified folder's existence, Alpine will ask which
21919 folder you intend the message to be stored in. Choose the
21920 "F" option to store the message in your Form Letter Folder.
21921 This is the most common way to add a message to the folder.
21923 <P>
21924 Another method of adding messages to the folder is via the Alpine
21925 composer's <SAMP>Fcc:</SAMP> field. If you are sending a message that
21926 you expect to send in the same form again, you can enter the Form
21927 Letter Folder's name in this field. Alpine, as usual, will copy the
21928 message as it's sent. Note, when you later select this message from
21929 your Form Letter Folder, it will have the same recipients as the original
21930 message.
21932 <P>
21933 To delete a message from the Form Letter Folder, you can either select
21934 the folder from a suitable FOLDER LIST screen, or use the Delete
21935 command in the MESSAGE INDEX offered when selecting from the folder as
21936 part of the Compose command. You can delete a Form Letter Folder just
21937 as any other folder from a suitable FOLDER LIST screen.
21939 <P>
21940 You may find that the <A HREF="h_rules_roles">"Roles"</A>
21941 facility can be used
21942 to replace the Form Letter Folder.
21944 <P>
21945 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21946 details on the syntax of folder definitions.
21948 <P>
21949 <UL>
21950 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21951 </UL><P>
21952 <End of help on this topic>
21953 </BODY>
21954 </HTML>
21955 ====== h_config_archived_folders =====
21956 <HTML>
21957 <HEAD>
21958 <TITLE>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></TITLE>
21959 </HEAD>
21960 <BODY>
21961 <H1>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></H1>
21963 This is like
21964 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>,
21965 only more general. You may archive
21966 any of the folders in your incoming collection. This is a list of folder
21967 pairs, with the first separated from the second in the pair by a space.
21968 The first folder in a pair is the folder you want to archive, and the
21969 second folder is the folder that read messages from the first should be
21970 moved to. Depending on how you define the
21971 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
21972 setting, you may or may not be asked when you
21973 leave the first folder if you want read messages to be moved to the
21974 second folder. In either case, moving the messages means they will be
21975 deleted from the first folder.
21976 <P>
21977 The name of the first folder in each pair can be either the technical
21978 specification of the folder (like what appears in your configuration file)
21979 or (much easier) the nickname that you gave the folder when you made it
21980 an incoming folder.
21981 <p>
21982 For example:<p>
21983 <CENTER><SAMP>{monet.art.example.com}inbox {monet.art.example.com}mail/inbox-archive</SAMP></CENTER>
21984 <p>or, using nicknames:<p>
21985 <CENTER><SAMP>inbox inbox-archive</SAMP></CENTER>
21986 <P>
21987 If these are not path names, they will be in the default collection for
21988 saves. Any valid folder specification, local or remote (via IMAP), is
21989 allowed. There is no default.
21990 <P>
21991 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21992 details on the syntax of folder definitions.
21993 <P>
21994 <UL>
21995 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21996 </UL><P>
21997 <End of help on this topic>
21998 </BODY>
21999 </HTML>
22000 ====== h_config_newsrc_path ======
22001 <HTML>
22002 <HEAD>
22003 <TITLE>OPTION: <!--#echo var="VAR_newsrc-path"--></TITLE>
22004 </HEAD>
22005 <BODY>
22006 <H1>OPTION: <!--#echo var="VAR_newsrc-path"--></H1>
22008 This option overrides the default name Alpine uses for your "newsrc" news
22009 status and subscription file. If set, Alpine will take this value as the
22010 full pathname for the desired newsrc file.<P>
22012 If this option is <B>not</B> set,
22013 <!--chtml if pinemode="os_windows"-->
22014 PC-Alpine looks first for $HOME\NEWSRC (where $HOME defaults to the root
22015 of the current drive, e.g. "C:\") and then it looks in the same
22016 directory as your pinerc file for NEWSRC.
22017 <!--chtml else-->
22018 Unix Alpine looks for the file ~/.newsrc (that is, the file named .newsrc in
22019 your account's home directory).
22020 <!--chtml endif-->
22021 <P><UL>
22022 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22023 </UL>
22024 <P>
22025 <End of help on this topic>
22026 </BODY>
22027 </HTML>
22028 ====== h_config_literal_sig =====
22029 <HTML>
22030 <HEAD>
22031 <TITLE>OPTION: <!--#echo var="VAR_literal-signature"--></TITLE>
22032 </HEAD>
22033 <BODY>
22034 <H1>OPTION: <!--#echo var="VAR_literal-signature"--></H1>
22036 With this option your actual signature, as opposed to
22037 the name of a file containing your signature,
22038 is stored in the Alpine configuration file.
22039 If this is defined it takes precedence over the <!--#echo var="VAR_signature-file"--> option.
22040 <P>
22042 This is simply a different way to store the signature.
22043 The signature is stored inside your Alpine configuration file instead of in
22044 a separate file.
22045 Tokens work the same way they do with the
22046 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A> so look there for
22047 help.
22048 <P>
22050 The Setup/Signature command on Alpine's MAIN MENU will edit
22051 the "<!--#echo var="VAR_literal-signature"-->" by default. However, if no
22052 "<!--#echo var="VAR_literal-signature"-->" is defined and the file named in the
22053 "<!--#echo var="VAR_signature-file"-->" option exists, then the latter will be used
22054 instead.
22055 <P>
22057 The two character sequence \n (backslash followed by
22058 the character n) will be used to signify a line-break in your signature.
22059 You don't have to enter the \n, but it will be visible in the
22060 SETUP CONFIGURATION window after you are done editing the signature.
22062 <P>
22063 <UL>
22064 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22065 </UL><P>
22066 <End of help on this topic>
22067 </BODY>
22068 </HTML>
22069 ====== h_config_signature_file =====
22070 <HTML>
22071 <HEAD>
22072 <TITLE>OPTION: <!--#echo var="VAR_signature-file"--></TITLE>
22073 </HEAD>
22074 <BODY>
22075 <H1>OPTION: <!--#echo var="VAR_signature-file"--></H1>
22077 If a <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined,
22078 then this "<!--#echo var="VAR_signature-file"-->" option will be ignored.
22079 You can tell that that is the case because the value of the
22080 "<!--#echo var="VAR_signature-file"-->" will show up as
22081 <P>
22082 <CENTER><SAMP><Ignored: using <!--#echo var="VAR_literal-signature"--> instead></SAMP></CENTER>
22083 <P>
22084 You may either use all Literal Signatures (signatures stored in your
22085 configuration file) throughout Alpine, or all signature files.
22086 You can't mix the two.
22087 <P>
22088 This is the name of a file that will be automatically inserted into
22089 outgoing messages.
22090 It typically contains information such as your
22091 name, email address and organizational affiliation.
22092 Alpine adds the
22093 signature into the message as soon as you enter the composer so you
22094 can choose to remove it or edit it on a message by message basis.
22095 Signature file placement in message replies is controlled by the
22096 "<A HREF="h_config_sig_at_bottom"><!--#echo var="FEAT_signature-at-bottom"--></A>"
22097 setting in the feature list.
22098 <P>
22100 The default file name is
22101 <!--chtml if pinemode="os_windows"-->
22102 "PINE.SIG" in the same directory as your PINERC file if your
22103 PINERC file is a local file.
22104 If your PINERC file is remote, then it will be in the directory specified
22105 by the "-aux local_directory" command line option.
22106 <!--chtml else-->
22107 ".signature".
22108 <!--chtml endif-->
22109 <P>
22111 To create or edit your signature file choose Setup from the MAIN MENU
22112 and then select S for Signature (Main/Setup/Signature). This puts you
22113 into the Signature Editor where you can enter a <EM>few</EM> lines of
22114 text containing your identity and affiliation.
22116 <P>
22117 If the filename is followed by a vertical bar (|) then instead
22118 of reading the contents of the file the file is assumed to be a
22119 program that will produce the text to be used on its standard output.
22120 The program can't have any arguments and doesn't receive any input from Alpine,
22121 but the rest of the processing works as if the contents came from a file.
22123 <P>
22124 Instead of storing the data in a local file, the
22125 signature data may be stored remotely in an IMAP folder.
22126 In order to do this,
22127 you must use a remote name for the file.
22128 A remote <!--#echo var="VAR_signature-file"--> name might look like:
22129 <P>
22130 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/signature</SAMP></CENTER>
22131 <P>
22133 The syntax used here is the same as the syntax used for remote configuration
22134 files from the command line.
22135 Note that you may not access an existing signature file remotely,
22136 you have to create a new <EM>folder</EM> that contains the signature data.
22137 If the name you use here for the signature file is a remote name, then when
22138 you edit the file from the Setup/Signature command the data will be stored
22139 remotely in the folder.
22140 You aren't required to do anything special to create the folder, it
22141 gets created automatically if you use a remote name.
22143 <P>
22144 Besides regular text, the signature file may also contain
22145 (or a signature program may produce) tokens that
22146 are replaced with text that usually depends on the message you are replying
22147 to or forwarding.
22148 For example, if the signature file contains the token
22149 <P>
22150 <CENTER><SAMP>_DATE_</SAMP></CENTER>
22151 <P>
22152 anywhere in the text, then that token is replaced by the date
22153 the message you are replying to or forwarding was sent.
22154 If it contains
22155 <P>
22156 <CENTER><SAMP>_CURDATE_</SAMP></CENTER>
22157 <P>
22158 that is replaced with the current date.
22159 The first is an example of a token that depends on the message you
22160 are replying to (or forwarding) and the second is an example which
22161 doesn't depend on anything other than the current date.
22162 You have to be a little careful with this facility since tokens that
22163 depend on the message you are replying to or forwarding will be replaced
22164 by nothing in the case where you are composing a new message from scratch.
22165 The use of <A HREF="h_rules_roles">"roles"</A> may help you
22166 in this respect.
22167 It allows you to use different signature files in different cases.
22168 <P>
22170 The list of tokens available for use in the signature file is
22171 <A HREF="h_index_tokens">here</A>.
22172 <P>
22174 Instead of, or along with the use of "roles" to give you
22175 different signature files in different situations, there is also
22176 a way to conditionally include text based
22177 on whether or not a token would result in specific replacement text.
22178 For example, you could include some text based on whether or not
22179 the _NEWS_ token would result in any newsgroups if it was used.
22180 This is explained in detail
22181 <A HREF="h_reply_token_conditionals">here</A>.
22182 This isn't for the faint of heart.
22183 <P>
22184 In the very unlikely event that you want to include a literal token
22185 in the signature you must precede it with a backslash character.
22186 For example,
22187 <P>
22188 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
22189 <P>
22190 would produce something like
22191 <P>
22192 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
22193 <P>
22194 It is not possible to have a literal backslash followed by an expanded token.
22195 <P>
22196 An alternate method for storing the signature data is available by using the
22197 <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> configuration option.
22198 This variable will be used by default.
22199 <P>
22200 <UL>
22201 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22202 </UL><P>
22203 <End of help on this topic>
22204 </BODY>
22205 </HTML>
22206 ====== h_config_init_cmd_list =====
22207 <HTML>
22208 <HEAD>
22209 <TITLE>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></TITLE>
22210 </HEAD>
22211 <BODY>
22212 <H1>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></H1>
22214 The initial keystroke--or command--list option lets you start Alpine at
22215 any place you like.
22216 Whatever keystrokes you specify here will be executed
22217 by Alpine upon startup as a macro.
22218 The words SPACE, TAB, DOWN, UP, LEFT, and
22219 RIGHT indicate the pressing of those keys.
22220 CR indicates the pressing of the RETURN key.
22221 F1 through F12 represent the function keys, and ^ followed
22222 by a character indicates that key pressed along with the control key (in
22223 other words, ^P means Ctrl-P).
22224 As a shortcut notation, an element of the list may be several characters
22225 surrounded by double-quotes (").
22226 That will be expanded into the individual keystrokes
22227 (excluding the double-quote characters).
22228 For example, the quoted-string
22230 <P><CENTER>"ABC"</CENTER>
22232 <P>
22233 is interpreted the same as the three separate list members
22235 <P><CENTER>A and B and C</CENTER>
22237 <P>
22238 which is also the same as
22240 <P><CENTER>A,B,C</CENTER>
22242 <P>
22243 An example: To view message 1 on startup,
22244 you could use an <!--#echo var="VAR_initial-keystroke-list"--> equal to
22246 <P><CENTER>I,J,1,CR,V</CENTER>
22248 <P>
22249 An equivalent version of this is
22251 <P><CENTER>"IJ1",CR,V</CENTER>
22253 <P>
22254 Restrictions: You cannot pre-type into the composer with the initial
22255 keystroke list, and you cannot mix function key commands with letter
22256 commands.
22258 <P><UL>
22259 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22260 </UL>
22261 <P>
22262 <End of help on this topic>
22263 </BODY>
22264 </HTML>
22265 ====== h_config_comp_hdrs =====
22266 <html>
22267 <header>
22268 <title>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></title>
22269 </header>
22270 <body>
22271 <h1>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></h1>
22273 You can control which headers you want visible when composing outgoing
22274 email using this option.
22275 You can specify any of the regular set, any
22276 <A HREF="h_compose_richhdr">Rich Header</A>,
22277 or any <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22278 that you have already defined.
22279 If you use this setting at all, you must specify all the
22280 headers you want to see, you can't just add to the regular header set.
22281 The default set is To:, Cc:, Attchmnt:, and Subject:.<p>
22283 Note that the "Newsgroups:" header will be abbreviated in the Composer
22284 display, but should be spelled out in full here.<p>
22285 <UL>
22286 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22287 </UL><P>
22288 <End of help on this topic>
22289 </body>
22290 </html>
22291 ====== h_config_custom_hdrs =====
22292 <HTML>
22293 <HEAD>
22294 <TITLE>OPTION: <!--#echo var="VAR_customized-hdrs"--></TITLE>
22295 </HEAD>
22296 <BODY>
22297 <H1>OPTION: <!--#echo var="VAR_customized-hdrs"--></H1>
22299 You may add your own custom headers to outgoing messages.
22300 Each header you specify here must include the header tag
22301 (<A HREF="h_composer_reply_to">Reply-To:</A>, Approved:, etc.)
22302 and may optionally include a value for that header.
22303 If you want to see these custom headers each time you compose a message,
22304 you must add them to your
22305 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> list,
22306 otherwise they become part
22307 of the rich header set that you only see when you press the
22308 <A HREF="h_compose_richhdr">Rich Header</A>
22309 <!--chtml if pinemode="function_key"-->(F5)
22310 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
22311 (If you are looking for a way to change which headers are <EM>displayed</EM>
22312 when you view a message, take a look at the
22313 <A HREF="h_config_viewer_headers"><!--#echo var="VAR_viewer-hdrs"--></A>
22314 option instead.)
22315 Here's an example that shows how you might set your From address
22316 <P>
22317 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
22318 <P>
22319 and another showing how you might set a Reply-To address
22320 <P>
22321 <CENTER><SAMP>Reply-To: user@example.com</SAMP></CENTER>
22322 <P>
22323 You may also set non-standard header values here.
22324 For example, you could add
22325 <P>
22326 <CENTER><SAMP>Organization: My Organization Name</SAMP></CENTER>
22327 <P>
22328 or even
22329 <P>
22330 <CENTER><SAMP>X-Favorite-Colors: Purple and Gold</SAMP></CENTER>
22331 <P>
22332 If you include a value after the colon then that header will be included
22333 in your outgoing messages unless you delete it before sending.
22334 If a header in the <!--#echo var="VAR_customized-hdrs"--> list has only a tag but no value, then
22335 it will not be included in outgoing messages unless you edit a value
22336 in manually.
22337 For example, if
22338 <P>
22339 <CENTER><SAMP>Reply-To:</SAMP></CENTER>
22340 <P>
22341 is in the list, then the Reply-To header will be available for editing
22342 but won't be included unless a value is added while in the composer.
22343 <P>
22344 It's actually a little more complicated than that.
22345 The values of headers that you set with the <!--#echo var="VAR_customized-hdrs"--> option are
22346 defaults.
22347 If the message you are about to compose already has a value for a header,
22348 that value is used instead of a value from your <!--#echo var="VAR_customized-hdrs"-->.
22349 For example, if you are Replying to a message the Subject field
22350 will already be filled in.
22351 In that case, if the <!--#echo var="VAR_customized-hdrs"--> list contains a Subject line, the
22352 custom subject will <EM>NOT</EM> be used.
22353 The subject derived from the subject of the message you are Replying
22354 to will be used instead.
22355 <P>
22356 It is also possible to make header setting even more complicated and more
22357 automatic by using
22358 <A HREF="h_rules_roles">Roles</A>,
22359 but if all you want to do is set a default value for a header, you don't
22360 need to think about Roles.
22361 <P>
22362 If you change your From address you may also find it useful to add the
22363 changed From address to the
22364 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
22365 configuration option.
22366 <P>
22367 Limitation: Because commas are used to separate the list of
22368 <!--#echo var="VAR_customized-hdrs"-->, it is not possible to have the value of a
22369 header contain a comma.
22370 Nor is there currently an "escape" mechanism provided
22371 to make this work.
22372 <P><UL>
22373 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22374 </UL>
22375 <P>
22376 <End of help on this topic>
22377 </BODY>
22378 </HTML>
22379 ====== h_config_viewer_headers =====
22380 <HTML>
22381 <HEAD>
22382 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdrs"--></TITLE>
22383 </HEAD>
22384 <BODY>
22385 <H1>OPTION: <!--#echo var="VAR_viewer-hdrs"--></H1>
22387 You may change the default list of headers that are viewed by listing
22388 the headers you want to view here. If the headers in your
22389 "<!--#echo var="VAR_viewer-hdrs"-->" list are present in the message, then they
22390 will be shown. The order of the headers you list will be honored. If
22391 the special value "all-except" is included as the first
22392 header in the "<!--#echo var="VAR_viewer-hdrs"-->" list, then all headers in the
22393 message except those in the list will be shown. The values are all
22394 case insensitive.
22396 <P>
22397 Note that once you put anything in the "<!--#echo var="VAR_viewer-hdrs"-->" list,
22398 then the original default headers are ignored. So, if you just wanted
22399 to add the header Organization to the list, you would have to list
22400 Organization plus all of the other headers originally in the default
22401 list. If you just included Organization and nothing else, then you
22402 would see only the Organization header, nothing else.
22404 <P>
22405 The default list of headers includes:
22406 <UL>
22407 <LI>From
22408 <LI>Resent-From
22409 <LI>To
22410 <LI>Resent-To
22411 <LI>Cc
22412 <LI>Resent-cc
22413 <LI>Bcc
22414 <LI>Newsgroups
22415 <LI>Followup-To
22416 <LI>Date
22417 <LI>Resent-Date
22418 <LI>Subject
22419 <LI>Resent-Subject
22420 <LI>Reply-To
22421 </UL>
22423 <P>
22424 If you are looking for a way to control which headers are included in
22425 outgoing mail and are visible or not in the composer, take a look at the
22426 options
22427 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22428 and <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> instead of
22429 this option.
22430 <P>
22431 <UL>
22432 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22433 </UL><P>
22434 <End of help on this topic>
22435 </BODY>
22436 </HTML>
22437 ====== h_config_viewer_margin_left =====
22438 <HTML>
22439 <HEAD>
22440 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-left"--></TITLE>
22441 </HEAD>
22442 <BODY>
22443 <H1>OPTION: <!--#echo var="VAR_viewer-margin-left"--></H1>
22445 This variable controls the left-hand vertical margin's width in
22446 Alpine's Message Viewing screen.
22447 Its value is the number of space characters preceding each displayed line.
22448 For consistency with
22449 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>,
22450 you may specify the column number to start in
22451 (column numbering begins with number 1)
22452 instead of the width of the margin by appending a lower case letter
22453 "c" to the number.
22454 For example, a value of "2c" means to start the text in column two,
22455 which is entirely equivalent to a value of "1", which means to
22456 leave a margin of 1 space.
22457 <P>
22458 The default is a left margin of 0 (zero).
22459 Misconfigurations (for example, negative values or values with starting
22460 left columns greater than the ending right column)
22461 are silently ignored.
22462 If the number of columns for text between the <!--#echo var="VAR_viewer-margin-left"--> and
22463 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22464 instead.
22466 <P>
22467 <End of help on this topic>
22468 </BODY>
22469 </HTML>
22470 ====== h_config_viewer_margin_right =====
22471 <HTML>
22472 <HEAD>
22473 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-right"--></TITLE>
22474 </HEAD>
22475 <BODY>
22476 <H1>OPTION: <!--#echo var="VAR_viewer-margin-right"--></H1>
22478 This variable controls the right-hand vertical margin's width in
22479 Alpine's Message Viewing screen.
22480 Its value is the number of space characters following each displayed line.
22481 You may specify the column number to end the text in
22482 (column numbering begins with number 1)
22483 instead of the width of the margin by appending a lower case letter
22484 "c" to the number.
22485 For example, a value of "76c" means to end the text in column 76.
22486 If the screen is 80 characters wide, this is equivalent to a value
22487 of "4", which means to leave a margin of 4 spaces.
22488 However, if you use different size screens at different times, then these
22489 two values are not equivalent.
22490 <P>
22491 The default right margin is 4.
22492 Misconfigurations (for example, negative values or values with starting
22493 left columns greater than the ending right column)
22494 are silently ignored.
22495 If the number of columns for text between the
22496 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
22497 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22498 instead.
22500 <P>
22501 <End of help on this topic>
22502 </BODY>
22503 </HTML>
22504 ====== h_config_quote_suppression =====
22505 <HTML>
22506 <HEAD>
22507 <TITLE>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></TITLE>
22508 </HEAD>
22509 <BODY>
22510 <H1>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></H1>
22512 This option should be used with care.
22513 It will cause some of the quoted text to be eliminated from the
22514 display when viewing a message in the MESSAGE TEXT screen.
22515 For example, if you set the <!--#echo var="VAR_quote-suppression-threshold"--> to the
22516 value "5",
22517 this will cause quoted text that is longer than five lines to be truncated.
22518 Quoted text of five or fewer consecutive lines will be displayed in its entirety.
22519 Quoted text of more than six lines will have the first five lines displayed
22520 followed by a line that looks something like
22521 <P>
22522 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
22523 <P>
22524 As a special case, if exactly one line of quoted text would be hidden, the
22525 entire quote will be shown instead.
22526 So for the above example, quoted text that is exactly six lines long will
22527 will be shown in its entirety.
22528 (In other words, instead of hiding a single line and adding a line
22529 that announces that one line was hidden, the line is just shown.)
22530 <P>
22531 If the sender of a message has carefully chosen the quotes that he or she
22532 includes, hiding those quotes may change the meaning of the message.
22533 For that reason, Alpine requires that when you want to set the value of this
22534 variable to something less than four lines, you actually have to set it
22535 to the negative of that number.
22536 So if you want to set this option to "3", you actually have to
22537 set it to "-3".
22538 The only purpose of this is to get you to think about whether or not you
22539 really want to do this!
22540 If you want to delete all quoted text you set the value of this option
22541 to the special value "-10".
22542 <P>
22543 The legal values for this option are
22544 <P>
22545 <TABLE>
22546 <TR>
22547 <TD> 0 </TD>
22548 <TD> Default, don't hide anything </TD>
22549 </TR>
22550 <TR>
22551 <TD> -1,-2,-3 </TD>
22552 <TD> Suppress quote lines past 1, 2, or 3 lines </TD>
22553 </TR>
22554 <TR>
22555 <TD> 4,5,6,... </TD>
22556 <TD> Suppress if more than that many lines </TD>
22557 </TR>
22558 <TR>
22559 <TD> -10 </TD>
22560 <TD> Suppress all quoted lines </TD>
22561 </TR>
22562 </TABLE>
22563 <P>
22564 If you set this option to a non-default value you may sometimes wish to
22565 view the quoted text that is not shown.
22566 When this is the case, the
22567 <A HREF="h_common_hdrmode">HdrMode Command</A>
22568 may be used to show the hidden text.
22569 Typing the "H" command once will show the hidden text.
22570 Typing a second "H" will also turn on Full Header mode.
22571 The presence or absence of the HdrMode command is determined by the
22572 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
22573 Feature-List option in your Alpine configuration, so you will want to
22574 be sure that is turned on if you use quote suppression.
22575 <P>
22576 For the purposes of this option, a quote is a line that begins with the
22577 character ">".
22578 <P>
22579 Quotes are only suppressed when displaying a message on the screen.
22580 The entire quote will be left intact when printing or forwarding or something
22581 similar.
22582 <P>
22583 <End of help on this topic>
22584 </BODY>
22585 </HTML>
22586 ====== h_config_saved_msg_name_rule =====
22587 <HTML>
22588 <HEAD>
22589 <TITLE>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></TITLE>
22590 </HEAD>
22591 <BODY>
22592 <H1>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></H1>
22594 This option determines the default folder name when saving
22595 a message.
22597 <P>
22598 The default option is "default-folder", which is the folder
22599 called "saved-messages" in Unix Alpine and
22600 "savemail" in PC-Alpine. To change the default folder, modify
22601 the Alpine option called
22602 <A HREF="h_config_def_save_folder">"<!--#echo var="VAR_default-saved-msg-folder"-->"</A>.
22604 <P>
22605 Choosing any of the "by-" options cause Alpine to attempt to
22606 get the chosen option's value for the message being saved (or for the
22607 first message being saved if using an aggregrate save).
22608 For example, if "by-from" is chosen, Alpine attempts to get the
22609 value of who the message came from (i.e. the from address).
22610 Alpine then attempts to save the message to a folder matching that value.
22611 If "by-from" is chosen and no value is obtained, Alpine uses
22612 "by-sender".
22613 The opposite is also true.
22614 If "by-recipient" is chosen and the message was posted to a
22615 newsgroup, Alpine will use the newsgroup name.
22616 If "by-replyto" is chosen and no value is obtained, Alpine uses
22617 "by-from".
22619 <P>
22620 If any of the "by-realname" options are chosen, Alpine will attempt
22621 to use the personal name part of the address instead of the mailbox part.
22622 If any of the "by-nick" options are chosen, the
22623 address is looked up in your address book and if found, the
22624 nickname for that entry is used.
22625 Only simple address book entries are checked, not distribution lists.
22626 Similarly, if any of the
22627 "by-fcc" options are chosen, the fcc from the corresponding
22628 address book entry is used.
22629 If by-realname, or the by-nick or by-fcc lookups result in no value,
22630 then if the chosen option ends with the "then-from",
22631 "then-sender", "then-replyto",
22632 or "then-recip" suffix, Alpine
22633 reverts to the same behavior as "by-from",
22634 "by-sender", "by-replyto", or "by-recip"
22635 depending on which option was specified.
22636 If the chosen option doesn't end with one of
22637 the "then-" suffixes, then Alpine reverts to the default
22638 folder when no match is found in the address book.
22640 <P>
22641 Choosing the option called "last-folder-used", causes Alpine
22642 to save to the folder that you saved to the last time you saved a
22643 message. The first time you save a message in an Alpine session, Alpine
22644 attempts to save the message to the default folder.
22646 <P>
22647 Here is an example to make some of the options clearer.
22648 If the message is From
22649 <P>
22650 <CENTER><SAMP>Fred Flintstone <flint@bedrock.org></SAMP></CENTER>
22651 <P>
22652 and this rule is set to "by-from", then the default folder offered
22653 in the save dialog would be "flint".
22654 <P>
22655 If this rule is set to "by-realname-of-from" then the default would
22656 be "Fred Flintstone".
22657 <P>
22658 If this rule is set to "by-nick-of-from" then Alpine will search
22659 for the address "flint@bedrock.org" in your address book.
22660 If an entry is found and it has a nickname associated with it, that nickname
22661 will be offered as the default folder.
22662 If not, the default saved message folder will be offered as the default.
22663 <P>
22664 If this rule is set to "by-fcc-of-from" then Alpine will search
22665 for the address "flint@bedrock.org" in your address book.
22666 If an entry is found and it has an Fcc associated with it, that Fcc
22667 will be offered as the default folder.
22668 If not, the default saved message folder will be offered as the default.
22669 <P>
22670 If this rule is set to "by-nick-of-from-then-from" then Alpine will search
22671 for the address "flint@bedrock.org" in your address book.
22672 If an entry is found and it has a nickname associated with it, that nickname
22673 will be offered as the default folder.
22674 If it is not found (or has no nickname) then the default offered will be
22675 the same as it would be for the "by-from" rule.
22676 That is, it would be "flint"
22677 <P>
22678 <UL>
22679 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22680 </UL><P>
22681 <End of help on this topic>
22682 </BODY>
22683 </HTML>
22684 ====== h_config_fcc_rule =====
22685 <HTML>
22686 <HEAD>
22687 <TITLE>OPTION: <!--#echo var="VAR_fcc-name-rule"--></TITLE>
22688 </HEAD>
22689 <BODY>
22690 <H1>OPTION: <!--#echo var="VAR_fcc-name-rule"--></H1>
22692 This option determines the default name for folder carbon copy. Choose
22693 one:
22695 <DL>
22696 <DT>default-fcc</DT>
22697 <DD>This is the normal default, the value of which is set in the
22698 "<!--#echo var="VAR_default-fcc"-->" variable as specified earlier in this
22699 configuration.
22700 </DD>
22702 <DT>last-fcc-used</DT>
22703 <DD> Causes Alpine to use the folder that was last
22704 used in the fcc field
22705 </DD>
22707 <DT>by-nickname</DT>
22708 <DD>Means that Alpine will use the nickname
22709 from your address book that matches the first address in the To line.
22710 If there is no match, it will use the value of the
22711 "<!--#echo var="VAR_default-fcc"-->" variable.
22712 </DD>
22714 <DT>by-recipient</DT>
22715 <DD>Means Alpine will form a folder name
22716 based on the left hand side of the first address in the To line.
22717 </DD>
22719 <DT>by-nick-then-recip</DT>
22720 <DD>Means that it will use the
22721 matching nickname from your address book if there is one, otherwise it
22722 will extract the recipient name from the address and use that (like
22723 by-recipient).
22724 </DD>
22726 <DT>current-folder</DT>
22727 <DD>Causes a copy to be written to
22728 the currently open folder, unless that is the INBOX. In the case
22729 where the current folder is the INBOX, the "<!--#echo var="VAR_default-fcc"-->" is
22730 used instead.
22731 </DD>
22732 </DL>
22734 <P>
22735 Note: Whatever the fcc specified by the rule here, it will be
22736 over-ridden by any fcc entries you have in your address book.
22738 <P>
22739 <UL>
22740 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22741 </UL><P>
22742 <End of help on this topic>
22743 </BODY>
22744 </HTML>
22745 ====== h_config_sort_key =====
22746 <HTML>
22747 <HEAD>
22748 <TITLE>OPTION: <!--#echo var="VAR_sort-key"--></TITLE>
22749 </HEAD>
22750 <BODY>
22751 <H1>OPTION: <!--#echo var="VAR_sort-key"--></H1>
22753 This option determines the order in which messages will be displayed in
22754 the MESSAGE INDEX screen. Choose from:
22755 <P>
22756 <UL>
22757 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
22758 <LI> <A HREF="h_index_sort_date">Date</A>
22759 <LI> <A HREF="h_index_sort_subj">Subject</A>
22760 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
22761 <LI> <A HREF="h_index_sort_thread">Thread</A>
22762 <LI> <A HREF="h_index_sort_from">From</A>
22763 <LI> <A HREF="h_index_sort_size">Size</A>
22764 <LI> <A HREF="h_index_sort_score">Score</A>
22765 <LI> <A HREF="h_index_sort_to">To</A>
22766 <LI> <A HREF="h_index_sort_cc">Cc</A>
22767 </UL>
22769 <P>
22770 Each type of sort may also be reversed.
22771 Normal default is by "Arrival".
22773 <P>
22774 A possible point of confusion arises when you change the configuration
22775 of the <!--#echo var="VAR_sort-key"-->.
22776 The folder will normally be re-sorted when you go back to viewing the
22777 index.
22778 However, if you have manually sorted the folder with the
22779 Sort
22780 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
22781 command, then it will not be re-sorted until the next time it is opened.
22783 <P>
22784 <UL>
22785 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22786 </UL><P>
22787 <End of help on this topic>
22788 </BODY>
22789 </HTML>
22790 ====== h_config_other_startup =====
22791 <HTML>
22792 <HEAD>
22793 <TITLE>OPTION: Set Startup Rule</TITLE>
22794 </HEAD>
22795 <BODY>
22796 <H1>OPTION: Set Startup Rule</H1>
22798 This option determines which message will be the <EM>current message</EM> when
22799 the folder is first opened.
22800 It works the same way that the option
22801 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
22802 works, so look there for help.
22803 It may be used for any folder, not just incoming folders.
22805 <P>
22806 <UL>
22807 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22808 </UL><P>
22809 <End of help on this topic>
22810 </BODY>
22811 </HTML>
22812 ====== h_config_perfolder_sort =====
22813 <HTML>
22814 <HEAD>
22815 <TITLE>Set Sort Order</TITLE>
22816 </HEAD>
22817 <BODY>
22818 <H1>Set Sort Order</H1>
22820 This option determines the order in which messages will be displayed in
22821 the MESSAGE INDEX screen when the Current Folder Type set in the
22822 Pattern is a match. Choose from:
22823 <P>
22824 <UL>
22825 <LI> <A HREF="h_index_sort_default">Default</A>
22826 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
22827 <LI> <A HREF="h_index_sort_date">Date</A>
22828 <LI> <A HREF="h_index_sort_subj">Subject</A>
22829 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
22830 <LI> <A HREF="h_index_sort_thread">Thread</A>
22831 <LI> <A HREF="h_index_sort_from">From</A>
22832 <LI> <A HREF="h_index_sort_size">Size</A>
22833 <LI> <A HREF="h_index_sort_score">Score</A>
22834 <LI> <A HREF="h_index_sort_to">To</A>
22835 <LI> <A HREF="h_index_sort_cc">Cc</A>
22836 </UL>
22838 <P>
22839 Each type of sort may also be reversed.
22840 Normal default is by "Arrival".
22842 <P>
22843 A possible point of confusion arises when you change the configuration
22844 of the Sort Order for the currently open folder.
22845 The folder will normally be re-sorted when you go back to viewing the
22846 index.
22847 However, if you have manually sorted the folder with the
22848 Sort
22849 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
22850 command, then it will not be re-sorted until the next time it is opened.
22852 <P>
22853 <UL>
22854 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22855 </UL><P>
22856 <End of help on this topic>
22857 </BODY>
22858 </HTML>
22859 ====== h_config_fld_sort_rule =====
22860 <HTML>
22861 <HEAD>
22862 <TITLE>OPTION: <!--#echo var="VAR_folder-sort-rule"--></TITLE>
22863 </HEAD>
22864 <BODY>
22865 <H1>OPTION: <!--#echo var="VAR_folder-sort-rule"--></H1>
22867 This option controls the order in which folder list entries will be
22868 presented in the FOLDER LIST screen. Choose one of the following:
22870 <DL>
22871 <DT>Alphabetical</DT>
22872 <DD>sort by alphabetical name independent of type
22873 </DD>
22875 <DT>Alpha-with-dirs-last</DT>
22876 <DD>sort by alphabetical name grouping directory entries
22877 to the end of the list
22878 </DD>
22880 <DT>Alpha-with-dirs-first</DT>
22881 <DD>sort by alphabetical name grouping directory entries
22882 to the start of the list
22883 </DD>
22884 </DL>
22886 The normal default is "Alphabetical".
22888 <P>
22889 <UL>
22890 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22891 </UL><P>
22892 <End of help on this topic>
22893 </BODY>
22894 </HTML>
22895 ====== h_config_ab_sort_rule =====
22896 <HTML>
22897 <HEAD>
22898 <TITLE>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></TITLE>
22899 </HEAD>
22900 <BODY>
22901 <H1>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></H1>
22903 This option controls the order in which address book entries will be
22904 presented. Choose one of the following:
22906 <DL>
22907 <DT>fullname</DT>
22908 <DD>use fullname field, lists mixed in
22909 </DD>
22911 <DT>fullname-with-lists-last</DT>
22912 <DD>use fullname field, but put lists at end
22913 </DD>
22915 <DT>nickname</DT>
22916 <DD>use nickname field, lists mixed in
22917 </DD>
22919 <DT>nickname-with-lists-last</DT>
22920 <DD>use nickname field, but put lists at end
22921 </DD>
22923 <DT>dont-sort</DT>
22924 <DD>don't change order of file
22925 </DD>
22926 </DL>
22928 <P>
22929 The normal default is "fullname-with-lists-last".
22930 If you use an address book from more than one computer and those
22931 computers sort the address book differently then the sort order
22932 will be the order where the last change to the address book was
22933 made.
22934 There are two reasons the sorting might be different on different
22935 systems.
22936 First, the <!--#echo var="VAR_addrbook-sort-rule"--></a> may be set differently in the two
22937 places.
22938 Second, the collation rules on the two computers may be different.
22939 For example, one system might ignore special characters while the other
22940 doesn't or one may sort upper and lower case letters together while
22941 the other doesn't.
22942 In any case, the order you see is the order on the system where the
22943 last change was made, for example by an address book edit or a
22944 Take Address command.
22946 <P>
22947 <UL>
22948 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22949 </UL><P>
22950 <End of help on this topic>
22951 </BODY>
22952 </HTML>
22953 ====== h_config_post_char_set =====
22954 <HTML>
22955 <HEAD>
22956 <TITLE>OPTION: <!--#echo var="VAR_posting-character-set"--></TITLE>
22957 </HEAD>
22958 <BODY>
22959 <H1>OPTION: <!--#echo var="VAR_posting-character-set"--></H1>
22961 The <!--#echo var="VAR_posting-character-set"--> configuration option is used
22962 when sending messages.
22964 <P>
22966 When sending a message the text typed in the composer is
22967 labeled with the character set specified by this option.
22968 If the composed text is not fully representable in the
22969 specified <!--#echo var="VAR_posting-character-set"-->, then it is labeled as "UTF-8."
22970 instead;
22972 <P>
22973 Attachments are labeled with your
22974 <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>.
22976 <P>
22977 Generally, there should be little need to set this option.
22978 If left unset, the
22979 default behavior is to label composed text as specifically as
22980 possible. That is, if the composed text has no non-ASCII characters,
22981 it is labeled as "US-ASCII." Similarly, if it is composed of
22982 only ISO-8859-15 characters, it is labeled as such. Alpine will
22983 attempt to automatically detect a number of character sets including ISO-8859-15,
22984 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
22985 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, and EUC-KR.
22986 If the message contains a mix of character sets,
22987 it is labeled as "UTF-8."
22989 <P>
22991 This setting is provided to allow you to force a particular character set that
22992 Alpine does not automatically detect. For example, if a message is representable
22993 in more than one character set then Alpine may choose a different default
22994 than you want.
22995 Lastly, by setting this option explicitly to
22996 "UTF-8" all non-ASCII messages you send will be labeled as
22997 "UTF-8" instead of something more specific.
22999 <P>
23000 In the Setup/Config screen you may choose from a list of all the
23001 character sets Alpine knows about by using the "T" ToCharsets command.
23003 <P>
23004 The options
23005 <A HREF="h_config_char_set">"Display Character Set"</A>
23006 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
23007 are closely related.
23008 Setting the feature
23009 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23010 should cause this option to be ignored.
23012 <P>
23013 <UL>
23014 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23015 </UL><P>
23016 <End of help on this topic>
23017 </BODY>
23018 </HTML>
23019 ====== h_config_unk_char_set =====
23020 <HTML>
23021 <HEAD>
23022 <TITLE>OPTION: <!--#echo var="VAR_unknown-character-set"--></TITLE>
23023 </HEAD>
23024 <BODY>
23025 <H1>OPTION: <!--#echo var="VAR_unknown-character-set"--></H1>
23027 The <!--#echo var="VAR_unknown-character-set"--> configuration option is used
23028 when reading or replying to messages.
23030 <P>
23032 A text message should either be made up of all US-ASCII characters
23033 or it should contain a charset label which tells the software which
23034 character set encoding to use to interpret the message.
23035 Sometimes a malformed message may be unlabeled but contain non-ascii text.
23036 This message is outside of the standards so any attempt to read it could fail.
23037 When Alpine attempts to read such a message it will try to interpret the
23038 text in the character set you specify here.
23039 For example, if you have correspondents who send you unlabeled messages that
23040 are usually made up of characters from the WINDOWS-1251 character set, setting
23041 this <!--#echo var="VAR_unknown-character-set"--> to <CODE>WINDOWS-1251</CODE> will
23042 allow you to read those messages.
23043 Of course, if the unlabeled message is actually in some other character set,
23044 then you may see garbage on your screen.
23045 <P>
23046 Instead of just unlabeled text, this option also affects text which is labeled
23047 with the charsets "X-Unknown", "MISSING_PARAMETER_VALUE"
23048 or "US-ASCII".
23050 <P>
23051 In the Setup/Config screen you may choose from a list of all the
23052 character sets Alpine knows about by using the "T" ToCharsets command.
23054 <P>
23055 <UL>
23056 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23057 </UL><P>
23058 <End of help on this topic>
23059 </BODY>
23060 </HTML>
23061 ====== h_config_char_set =====
23062 <HTML>
23063 <HEAD>
23064 <TITLE>OPTION: Display Character Set</TITLE>
23065 </HEAD>
23066 <BODY>
23067 <H1>OPTION: Display Character Set</H1>
23069 The Display Character Set configuration option is used when viewing messages.
23070 <P>
23071 Alpine uses Unicode characters internally and
23072 it is a goal for Alpine to handle email in many different languages.
23073 Alpine will properly display only left-to-right character sets
23074 in a fixed-width font. Specifically, Alpine assumes that a fixed-width
23075 font is in use, in the sense that
23076 characters are assumed to take up zero, one, or two character cell
23077 widths from left to right on the screen. This is true even in PC-Alpine.
23078 <P>
23080 Alpine recognizes some local character sets that are right-to-left
23081 (Arabic, Hebrew, and Thai) or not representable in a fixed-width font
23082 (Arabic) and properly converts texts in these character sets to/from
23083 Unicode; however, there are known display bugs with these character
23084 sets.
23085 <P>
23087 There are three possible configuration character settings and some
23088 environment variable settings that can affect how Alpine
23089 handles international characters.
23090 The first two of these are only available in UNIX Alpine.
23091 The three configuration options are
23092 Display Character Set,
23093 Keyboard Character Set, and
23094 <!--#echo var="VAR_posting-character-set"-->.
23095 The Keyboard Character Set defaults to being the same value
23096 as the Display Character Set, and that is usually correct, because
23097 the keyboard almost always produces characters in the same character set
23098 as the display displays.
23099 The Display Character Set is the character set that Alpine
23100 will attempt to use when sending characters to the display.
23101 <P>
23103 By default, the Display Character Set variable is not set and UNIX Alpine
23104 will attempt to get this information from the environment.
23105 In particular, the <CODE>nl_langinfo(CODESET)</CODE> call is used.
23106 This usually depends on the setting of the environment variables LANG or LC_CTYPE.
23107 An explicit configuration setting for Display Character Set will,
23108 of course, override any default setting.
23109 <P>
23110 For PC-Alpine the Display Character Set
23111 and the Keyboard Character Set
23112 are always equivalent to <CODE>UTF-8</CODE> and this is not settable.
23113 <P>
23115 It is probably best to use UNIX Alpine in a terminal emulator
23116 capable of displaying UTF-8 characters, since that will allow you to
23117 view just about any received text that is correctly formatted (note,
23118 however, the above comments about known index display bugs with certain
23119 character sets). You'll need to have an emulator that uses a UTF-8 font
23120 and you'll need to set up your environment to use a UTF-8 charmap. For
23121 example, on a Linux system you might include
23122 <P>
23123 <CENTER> <CODE>setenv LANG en_US.UTF-8</CODE> </CENTER>
23124 <P>
23126 or something similar in your UNIX startup files.
23127 You'd also have to select a UTF-8 font in your terminal emulator.
23128 <P>
23130 The types of values that the character set variables may be set to are
23131 <CODE>UTF-8</CODE>, <CODE>ISO-8859-1</CODE>, or <CODE>EUC-JP</CODE>.
23132 The <CODE>ISO-2022</CODE> character sets are not supported for input or
23133 for display, but as a special case, <CODE>ISO-2022-JP</CODE> is supported
23134 for use only as a <!--#echo var="VAR_posting-character-set"-->.
23135 In the Setup/Config screen you may choose from a list of all the
23136 character sets Alpine knows about by using the "T" ToCharsets command.
23137 Here is a list of many of the possible character sets:
23139 <P>
23140 <TABLE>
23141 <TR> <TD>UTF-8</TD> <TD>Unicode</TD> </TR>
23142 <TR> <TD>US-ASCII</TD> <TD>7 bit American English characters</TD> </TR>
23143 <TR> <TD>ISO-8859-1</TD> <TD>8 bit European "Latin 1" character set</TD> </TR>
23144 <TR> <TD>ISO-8859-2</TD> <TD>8 bit European "Latin 2" character set</TD> </TR>
23145 <TR> <TD>ISO-8859-3</TD> <TD>8 bit European "Latin 3" character set</TD> </TR>
23146 <TR> <TD>ISO-8859-4</TD> <TD>8 bit European "Latin 4" character set</TD> </TR>
23147 <TR> <TD>ISO-8859-5</TD> <TD>8 bit Latin and Cyrillic</TD> </TR>
23148 <TR> <TD>ISO-8859-6</TD> <TD>8 bit Latin and Arabic</TD> </TR>
23149 <TR> <TD>ISO-8859-7</TD> <TD>8 bit Latin and Greek</TD> </TR>
23150 <TR> <TD>ISO-8859-8</TD> <TD>8 bit Latin and Hebrew</TD> </TR>
23151 <TR> <TD>ISO-8859-9</TD> <TD>8 bit European "Latin 5" character set</TD> </TR>
23152 <TR> <TD>ISO-8859-10</TD> <TD>8 bit European "Latin 6" character set</TD> </TR>
23153 <TR> <TD>ISO-8859-11</TD> <TD>Latin and Thai</TD> </TR>
23154 <TR> <TD>ISO-8859-12</TD> <TD>Reserved</TD> </TR>
23155 <TR> <TD>ISO-8859-13</TD> <TD>8 bit European "Latin 7" character set</TD> </TR>
23156 <TR> <TD>ISO-8859-14</TD> <TD>8 bit European "Latin 8" character set</TD> </TR>
23157 <TR> <TD>ISO-8859-15</TD> <TD>8 bit European "Latin 9" character set</TD> </TR>
23158 <TR> <TD>ISO-8859-16</TD> <TD>8 bit European "Latin 10" character set</TD> </TR>
23159 <TR> <TD>KOI8-R</TD> <TD>8 bit Latin and Russian</TD> </TR>
23160 <TR> <TD>KOI8-U</TD> <TD>8 bit Latin and Ukranian</TD> </TR>
23161 <TR> <TD>WINDOWS-1251</TD> <TD>8 bit Latin and Russian</TD> </TR>
23162 <TR> <TD>TIS-620</TD> <TD>8 bit Latin and Thai</TD> </TR>
23163 <TR> <TD>VISCII</TD> <TD>8 bit Latin and Vietnamese</TD> </TR>
23164 <TR> <TD>GBK</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23165 <TR> <TD>GB2312</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23166 <TR> <TD>CN-GB</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23167 <TR> <TD>BIG5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
23168 <TR> <TD>BIG-5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
23169 <TR> <TD>EUC-JP</TD> <TD>Latin and Japanese</TD> </TR>
23170 <TR> <TD>SHIFT-JIS</TD> <TD>Latin and Japanese</TD> </TR>
23171 <TR> <TD>EUC-KR</TD> <TD>Latin and Korean</TD> </TR>
23172 <TR> <TD>KSC5601</TD> <TD>Latin and Korean</TD> </TR>
23173 </TABLE>
23174 <P>
23176 When reading incoming email, Alpine understands many different
23177 character sets and is able to convert the incoming mail into Unicode.
23178 The Unicode will be converted to the Display Character Set
23179 for display on your terminal.
23180 Characters typed at the keyboard will be converted from the
23181 Keyboard Character Set to Unicode for Alpine's internal
23182 use.
23183 You may find that you can read some malformed messages that do not
23184 contain a character set label by setting the option
23185 <A HREF="h_config_unk_char_set">"<!--#echo var="VAR_unknown-character-set"-->"</A>.
23186 <P>
23188 The <!--#echo var="VAR_posting-character-set"--> is used when sending messages.
23189 The default behavior obtained by leaving this variable unset is usually
23190 what is wanted. In that default case, Alpine will attempt
23191 to label the message with the most specific character set from the
23192 rather arbitrary set
23193 <P>
23194 US-ASCII, ISO-8859-15,
23195 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
23196 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, EUC-KR, and UTF-8.
23197 <P>
23199 For example, if the message is made up of only US-ASCII characters, it
23200 will be labeled US-ASCII. Otherwise, if it is all ISO-8859-15 characters,
23201 that will be the label. If that doesn't work the same is tried for the
23202 remaining members of the list.
23204 <P>
23205 It might make sense to set <!--#echo var="VAR_posting-character-set"--> to an
23206 explicit value instead.
23207 For example, if you usually send messages in Greek, setting this
23208 option to ISO-8859-7 will result in messages being labeled as
23209 US-ASCII if there are no non-ascii characters, ISO-8859-7 if there
23210 are only Greek characters, or UTF-8 if there are some characters
23211 that aren't representable in ISO-8859-7.
23212 Another possibility is to set this option explicitly to UTF-8.
23213 In that case
23214 Alpine labels only ascii messages as US-ASCII and all other
23215 messages as UTF-8.
23216 <P>
23218 The options
23219 <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
23220 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
23221 are closely related to this option.
23222 Setting the feature
23223 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23224 should cause this option to be ignored.
23226 <P>
23227 When displaying a message, Alpine compares this setting to the character
23228 set specified in the message. If not all of the
23229 characters in the message can be displayed using the Display Character Set
23230 then Alpine places an editorial
23231 comment in the displayed text (enclosed in square-brackets) indicating
23232 that some characters may not be displayed correctly.
23233 This comment may be eliminated by turning on the option
23234 <A HREF="h_config_quell_charset_warning"><!--#echo var="FEAT_quell-charset-warning"--></A>.
23236 <P>
23237 <UL>
23238 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23239 </UL><P>
23240 <End of help on this topic>
23241 </BODY>
23242 </HTML>
23243 ====== h_config_key_char_set =====
23244 <HTML>
23245 <HEAD>
23246 <TITLE>OPTION: Keyboard Character Set</TITLE>
23247 </HEAD>
23248 <BODY>
23249 <H1>OPTION: Keyboard Character Set</H1>
23251 UNIX Alpine only.
23252 <P>
23253 The Keyboard Character Set identifies the character set of the characters
23254 coming from your keyboard.
23255 It defaults to having the same value as your
23256 <A HREF="h_config_char_set">"Display Character Set"</A>,
23257 which in turn defaults to a value obtained from your environment.
23258 It is unlikely that you will need to use this option, because the keyboard
23259 almost always produces the same kind of characters as the display displays.
23261 <P>
23262 This character set is also used when accessing files in your local
23263 file system.
23264 The names of the files are assumed to be in the same character set as
23265 what the keyboard produces, as well as the contents of the files.
23267 <P>
23268 In the Setup/Config screen you may choose from a list of all the
23269 character sets Alpine knows about by using the "T" ToCharsets command.
23271 <P>
23272 The options
23273 <A HREF="h_config_char_set">"Display Character Set"</A>
23274 and <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
23275 are closely related.
23276 Setting the feature
23277 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23278 should cause this option to be ignored.
23280 <P>
23281 <UL>
23282 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23283 </UL><P>
23284 <End of help on this topic>
23285 </BODY>
23286 </HTML>
23287 ====== h_config_editor =====
23288 <HTML>
23289 <HEAD>
23290 <TITLE>OPTION: <!--#echo var="VAR_editor"--></TITLE>
23291 </HEAD>
23292 <BODY>
23293 <H1>OPTION: <!--#echo var="VAR_editor"--></H1>
23295 <!--#echo var="VAR_editor"--> specifies the program invoked by ^_ in the Composer. This is
23296 normally an alternative to Alpine's internal composer (Pico). You could use
23297 this setting to specify an alternate editor to use occasionally or if you
23298 have a favorite editor and want to use it all the time (see the
23299 <A HREF="h_config_alt_ed_now">"<!--#echo var="FEAT_enable-alternate-editor-implicitly"-->"</A> setting). <P>
23300 If you specify multiple editors for this option, ^_ will invoke the first one
23301 of those specified that exists and is executable. When specifying a program
23302 for use here, make sure that the format of the text it saves -- which, when
23303 you exit it, will become the message body in Alpine -- is appropriate
23304 for the body of an email message; avoid proprietary formats that may result in
23305 a message body that the recipient of your message will be unable to decipher.
23306 <P>
23307 <!--chtml if pinemode="os_windows"-->
23308 <!--chtml else-->
23309 If you are in doubt about what editors are available on your system, or which
23310 of them may be appropriate for specification here, ask your local computing
23311 support staff.
23312 <!--chtml endif-->
23313 <P>
23314 Note that if <a href="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></a> is
23315 unset, outgoing text will be set as flowed. In most cases this will be fine,
23316 but if the editor has a "flowed text" mode, it would be best to
23317 use that.
23319 <P><UL>
23320 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23321 </UL>
23322 <P>
23323 <End of help on this topic>
23324 </BODY>
23325 </HTML>
23326 ====== h_config_speller =====
23327 <HTML>
23328 <HEAD>
23329 <TITLE>OPTION: <!--#echo var="VAR_speller"--></TITLE>
23330 </HEAD>
23331 <BODY>
23332 <H1>OPTION: <!--#echo var="VAR_speller"--></H1>
23334 UNIX Alpine only.
23335 <P>
23336 For PC-Alpine, you must install the aspell library code that you
23337 may get from
23338 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
23339 <P>
23340 This option affects the behavior of the ^T (spell check) command in the
23341 Composer. It specifies the program invoked by ^T in the Composer.
23342 By default, Alpine uses
23343 <P>
23344 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
23345 <P>
23346 if it knows where to find "aspell".
23347 If there is no "aspell" command available but the command "ispell" is available
23348 then the command used is
23349 <P>
23350 <CENTER><SAMP>ispell -l</SAMP></CENTER>
23351 <P>
23352 Otherwise, the ancient "spell" command is used.
23353 <P>
23354 If you specify a value for this command (with full pathname) then that is what
23355 will be used instead of any of the defaults.
23356 When invoking this
23357 spell-checking program, Alpine appends a tempfile name (where the message is
23358 passed) to the command line. Alpine expects the speller to correct the
23359 spelling in that file. When you exit from that program Alpine will read the
23360 tempfile back into the composer.
23361 <P>
23362 Don't set this speller option to the standard Unix spell command.
23363 That won't work because spell works in a different way.
23365 <P>
23366 <UL>
23367 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23368 </UL><P>
23369 <End of help on this topic>
23370 </BODY>
23371 </HTML>
23372 ====== h_config_display_filters =====
23373 <HTML>
23374 <HEAD>
23375 <TITLE>OPTION: <!--#echo var="VAR_display-filters"--></TITLE>
23376 </HEAD>
23377 <BODY>
23378 <H1>OPTION: <!--#echo var="VAR_display-filters"--></H1>
23380 This option defines a list of text-filtering commands (programs or
23381 scripts) that may be used to filter text portions of received messages
23382 prior to their use (e.g., presentation in the "MESSAGE TEXT"
23383 display screen, exporting to a text file).
23384 For security reasons, the full path name of the
23385 filter command must be specified.
23387 <P>
23388 The command is executed and the message is piped into its standard input.
23389 The standard output of the command is read back by Alpine. The
23390 "_TMPFILE_" token (see below) overrides this default behavior.
23392 <P>
23393 The filter's use is based on the configured "trigger" string. The
23394 format of a filter definition is:
23396 <P>
23397 <CENTER><trigger> <command> <arguments></CENTER>
23399 <P>
23400 You can specify as many filters as you wish, separating them with a comma.
23401 Each filter can have only one trigger and command. Thus, two trigger
23402 strings that invoke the same command require separate filter
23403 specifications.
23405 <P>
23406 The "trigger" is simply text that, if found in the message,
23407 will invoke the associated command. If the trigger contains any space
23408 characters, it must be placed within quotes. Likewise, should you
23409 wish a filter to be invoked unconditionally, define the trigger as the
23410 null string, "" (two consecutive double-quote characters). If the
23411 trigger string is found anywhere in the text of the message the filter
23412 is invoked. Placing the trigger text within the tokens defined below
23413 changes where within the text the trigger must be before considering
23414 it a match.
23416 <P>
23417 Trigger Modifying Tokens:
23418 <DL>
23419 <DT>_CHARSET(<VAR>string</VAR>)_</DT>
23420 <DD>This token tells Alpine to invoke the supplied command
23421 if the text is in a character set matching <VAR>string</VAR>
23422 (e.g., ISO-8859-2 or ISO-2022-JP).
23423 </DD>
23426 <DT>_LEADING(<VAR>string</VAR>)_</DT>
23427 <DD>This token tells Alpine to invoke the supplied command
23428 if the enclosed <VAR>string</VAR> is found to be the first
23429 non-whitespace text.
23430 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23431 the space character.
23432 </DD>
23434 <DT>_BEGINNING(<VAR>string</VAR>)_</DT>
23435 <DD>This token tells Alpine to invoke the supplied command
23436 if the enclosed <VAR>string</VAR> is found at the beginning
23437 of any line in the text.
23438 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23439 the space character.
23440 </DD>
23441 </DL>
23443 <P>
23444 The "command" and "arguments" portion is simply
23445 the command line to be invoked if the trigger string is found. Below
23446 are tokens that Alpine will recognize and replace with special values
23447 when the command is actually invoked.
23449 <P>
23450 Command Modifying Tokens:
23452 <DL>
23453 <DT>_TMPFILE_</DT>
23454 <DD>When the command is executed, this token is
23455 replaced with the path and name of the temporary
23456 file containing the text to be filtered. Alpine
23457 expects the filter to replace this data with the
23458 filter's result.
23460 <P>
23461 NOTE: Use of this token implies that the text to
23462 be filtered is not piped into standard input of the
23463 executed command and its standard output is ignored.
23464 Alpine restores the tty modes before invoking the
23465 filter in case the filter interacts with the user
23466 via its own standard input and output.
23467 </DD>
23469 <DT>_RESULTFILE_</DT>
23470 <DD>When the command is executed, this token is
23471 replaced with the path and name of a temporary
23472 file intended to contain a status message from the
23473 filter. Alpine displays this in the message status
23474 field.
23475 </DD>
23477 <DT>_DATAFILE_</DT>
23478 <DD>When the command is executed, this token is
23479 replaced with the path and name of a temporary
23480 file that Alpine creates once per session and deletes
23481 upon exit. The file is intended to be used by the
23482 filter to store state information between instances
23483 of the filter.
23484 </DD>
23486 <DT>_PREPENDKEY_</DT>
23487 <DD>When the command is executed, this token indicates that a random
23488 number will be passed down the input stream before the message text.
23489 This number could be used as a session key. It is sent in this way to
23490 improve security. The number is unique to the current Alpine session
23491 and is only generated once per session.
23492 </DD>
23494 <DT>_SILENT_</DT>
23495 <DD>When the filter is executed, this token tells Alpine not to repaint
23496 the screen while the command is being executed. This can be used with
23497 filters that do not interact with the user, and therefore repainting
23498 the screen is not necessary.
23499 </DD>
23500 </DL>
23502 <P>
23503 The feature
23504 <A HREF="h_config_disable_reset_disp"><!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></A> is related.
23505 <P>
23506 Performance caveat/considerations:
23507 <BR>
23508 Testing for the trigger and invoking the filter doesn't come for free.
23509 There is overhead associated with searching for the trigger string, testing
23510 for the filter's existence and actually piping the text through the filter.
23511 The impact can be reduced if the Trigger Modifying Tokens above are
23512 employed.
23513 <P>
23514 <End of help on this topic>
23515 </BODY>
23516 </HTML>
23517 ====== h_config_sending_filter =====
23518 <HTML>
23519 <HEAD>
23520 <TITLE>OPTION: <!--#echo var="VAR_sending-filters"--></TITLE>
23521 </HEAD>
23522 <BODY>
23523 <H1>OPTION: <!--#echo var="VAR_sending-filters"--></H1>
23525 This option defines a list of text-filtering commands (programs and
23526 scripts) that may be selectively invoked to process a message just before
23527 it is sent. If set, the Composer's ^X (Send) command will allow you to
23528 select which filter (or none) to apply to the message before it is sent.
23529 For security reasons, the full path of the filter program must be
23530 specified.
23532 <P>
23533 Command Modifying Tokens:
23535 <DL>
23536 <DT>_RECIPIENTS_</DT>
23537 <DD>When the command is executed, this token is replaced
23538 with the space delimited list of recipients of the
23539 message being sent.
23540 </DD>
23542 <DT>_TMPFILE_</DT>
23543 <DD>
23544 When the command is executed, this token is
23545 replaced with the path and name of the temporary
23546 file containing the text to be filtered. Alpine
23547 expects the filter to replace this data with the
23548 filter's result.
23550 <P>
23551 NOTE: Use of this token implies that the text to
23552 be filtered is not piped into standard input of the
23553 executed command and its standard output is ignored.
23554 Alpine restores the tty modes before invoking the
23555 filter in case the filter interacts with the user
23556 via its own standard input and output.
23557 </DD>
23559 <DT>_RESULTFILE_</DT>
23560 <DD>When the command is executed, this token is
23561 replaced with the path and name of a temporary
23562 file intended to contain a status message from the
23563 filter. Alpine displays this in the message status
23564 field.
23565 </DD>
23567 <DT>_DATAFILE_</DT>
23568 <DD>When the command is executed, this token is replaced
23569 in the command line with the path and name of a
23570 temporary file that Alpine creates once per session
23571 and deletes upon exit. The file is intended to be
23572 used by the filter to store state information between
23573 instances of the filter.
23574 </DD>
23576 <DT>_PREPENDKEY_</DT>
23577 <DD>When the command is executed, this token indicates
23578 that a random number will be passed down the input
23579 stream before the message text. This number could
23580 be used as a session key. It is sent in this way
23581 to improve security. The number is unique to the
23582 current Alpine session and is only generated once per
23583 session.
23584 </DD>
23586 <DT>_INCLUDEALLHDRS_</DT>
23587 <DD>When the command is executed, this token indicates
23588 that the headers of the message will be passed down the input stream
23589 before the message text.
23590 </DD>
23592 <DT>_MIMETYPE_</DT>
23593 <DD>When the command is executed, this token is replaced in the
23594 command name with a temporary file name used to accept any new MIME
23595 Content-Type information necessitated by the output of the filter.
23596 Upon the filter's exit, if the file contains new MIME type
23597 information, Alpine verifies its format and replaces the outgoing
23598 message's MIME type information with that contained in the file. This
23599 is basically a cheap way of sending something other than Text/Plain.
23600 </DD>
23601 </DL>
23603 <P>
23604 NOTE: Only the body text, which is visible in the Composer, is piped
23605 through this filter. Attachments are not sent to the filter.
23606 <P>
23607 Sending filters are not used if the feature
23608 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set.
23609 <P>
23610 <UL>
23611 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23612 </UL><P>
23613 <End of help on this topic>
23614 </BODY>
23615 </HTML>
23616 ====== h_config_keywords =====
23617 <HTML>
23618 <HEAD>
23619 <TITLE>OPTION: <!--#echo var="VAR_keywords"--></TITLE>
23620 </HEAD>
23621 <BODY>
23622 <H1>OPTION: <!--#echo var="VAR_keywords"--></H1>
23624 You may define your own set of keywords and optionally set them on a
23625 message by message basis.
23626 These are similar to the "Important" flag which the user
23627 may set using the Flag command.
23628 The difference is that the Important flag is always present for each folder.
23629 User-defined keywords are chosen by the user.
23630 You may set up the list of possible keywords here, or you may add keywords
23631 from the Flag Details screen that you
23632 can get to after typing the
23633 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
23634 command.
23635 After the keywords have been defined,
23636 then you use the <A HREF="h_common_flag">Flag command</A>
23637 to set or clear the keywords in each message.
23638 The behavior of the flag command may be modified by using the
23639 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
23640 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
23642 <P>
23643 Keywords may be used when Selecting messages (Select Keyword).
23644 Keywords may also be used in the Patterns of Rules (Filters, Indexcolors, etc).
23645 Filter Rules may be used to set keywords automatically.
23646 Keywords may be displayed as part of the Subject of a message by using
23647 the SUBJKEY or SUBJKEYINIT tokens in the
23648 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
23649 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
23650 option may be used to modify the display of keywords using
23651 SUBJKEY and SUBJKEYINIT slightly.
23652 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
23653 screen by using the KEY or KEYINIT tokens.
23654 It is also possible to color keywords in the index using the
23655 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
23656 Keywords are not supported by all mail servers.
23658 <P>
23659 You may give keywords nicknames if you wish.
23660 If the keyword definition you type in contains a SPACE character, then the
23661 actual value of the keyword is everything after the last SPACE and the
23662 nickname for that keyword is everything before the last SPACE.
23663 For example, suppose you are trying to interoperate with another email program
23664 that uses a particular keyword with an unpleasant name.
23665 Maybe it uses a keyword called
23666 <P>
23667 <CENTER><SAMP>VendorName.SoftwareName.08</SAMP></CENTER>
23668 <P>
23669 but for you that keyword means that the message is work-related.
23670 You could define a keyword to have the value
23671 <P>
23672 <CENTER><SAMP>Work VendorName.SoftwareName.08</SAMP></CENTER>
23673 <P>
23674 and then you would use the name "Work" when dealing with
23675 that keyword in Alpine.
23676 If you defined it as
23677 <P>
23678 <CENTER><SAMP>My Work VendorName.SoftwareName.08</SAMP></CENTER>
23679 <P>
23680 the nickname would be everything before the last SPACE, that is the nickname
23681 would be "My Work".
23682 <P>
23683 Some commonly used keywords begin with dollar signs.
23684 This presents a slight complication, because the dollar sign is normally used
23685 to signify
23686 <A HREF="h_news_config">environment variable expansion</A>
23687 in the Alpine configuration.
23688 In order to specify a keyword that begins with a dollar sign you must
23689 precede the dollar sign with a second dollar sign to escape its special
23690 meaning.
23691 For example, if you want to include the keyword
23692 <P>
23693 <CENTER><SAMP>$Label1</SAMP></CENTER>
23694 <P>
23695 as one of your possible keywords, you must enter the text
23696 <P>
23697 <CENTER><SAMP>$$Label1</SAMP></CENTER>
23698 <P>
23700 instead.
23701 <P>
23702 There are a couple limitations.
23703 First, not all servers support keywords.
23704 Second, some servers (including the IMAP server included with Alpine)
23705 have a per folder limit on the number of keywords that may be defined.
23706 This count commonly includes every keyword you have ever used in the
23707 folder, even if it is no longer being used.
23708 In other words, you can add keywords but you cannot remove them easily.
23709 If you have changed keywords over the life of a folder and find that
23710 you have reached such a limit, one possible solution might be to copy
23711 all of the messages to a newly created folder (using Alpine) and then
23712 delete the original and rename the new folder.
23713 The reason this might work is that only the keywords currently set in
23714 any of the messages will be used in the new folder, hopefully putting you
23715 under the limit.
23717 <P>
23718 <UL>
23719 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23720 </UL><P>
23721 <End of help on this topic>
23722 </BODY>
23723 </HTML>
23724 ====== h_config_alt_addresses =====
23725 <HTML>
23726 <HEAD>
23727 <TITLE>OPTION: <!--#echo var="VAR_alt-addresses"--></TITLE>
23728 </HEAD>
23729 <BODY>
23730 <H1>OPTION: <!--#echo var="VAR_alt-addresses"--></H1>
23732 This option provides a place for you to list alternate email addresses
23733 you may have.
23734 Each address in the list should be the actual email address part of an
23735 address, without the full name field or the angle brackets.
23736 For example:
23738 <P>
23739 <CENTER><SAMP>user@example.com</SAMP></CENTER>
23740 <P>
23742 The matching is case-insensitive, so this would match any of
23743 <SAMP>User@example.com</SAMP>, <SAMP>user@Example.Com</SAMP>, or
23744 <SAMP>USER@EXAMPLE.COM</SAMP> as well.
23746 <P>
23747 If set, the option affects the behavior of the Reply
23748 command and the "+" symbol in the MESSAGE INDEX, which denotes that
23749 a message has been addressed specifically to you.
23751 <P>
23752 In the default INDEX display
23753 the personal name (or email address) of
23754 the person listed in the message's "From:" header
23755 field is usually displayed except when that address is yours or one of your
23756 alternate addresses.
23757 In that case you will usually see the name of
23758 the first person specified in the
23759 message's "To:" header field
23760 with the prefix "To: " prepended.
23762 <P>
23763 With respect to Reply, the reply-to-all option will exclude addresses
23764 listed here.
23766 <P>
23767 The feature
23768 <A HREF="h_config_copy_to_to_from"><!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></A>
23769 is somewhat related to this option.
23771 <P>
23772 In addition to a list of actual addresses,
23773 you may use regular expressions (as used with egrep with the ignore case flag)
23774 to describe the addresses you want to match.
23775 Alpine will somewhat arbitrarily interpret your entry as a regular
23776 expression if it contains any of the characters
23777 *, |, +, ?, {, [, ^, $, or \.
23778 Otherwise, it will be treated literally.
23779 The feature
23780 <a href="h_config_disable_regex"><!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
23781 may be used to turn off regular expression processing regardless of whether or not
23782 special characters appear in the entry.
23784 <P>
23785 A description of how regular expressions work is beyond the
23786 scope of this help text, but some examples follow.
23788 <P>
23789 The entry
23791 <P>
23792 <CENTER><SAMP>.*@example.com</SAMP></CENTER>
23793 <P>
23795 in the <!--#echo var="VAR_alt-addresses"--> list would mean that any
23796 address with a domain name of <SAMP>example.com</SAMP> (such as
23797 <SAMP>fred@example.com</SAMP> or <SAMP>wilma@example.com</SAMP>) will be considered
23798 one of your alternate addresses.
23799 Strictly speaking, the dot in <SAMP>example.com</SAMP> ought to be escaped with
23800 a backslash, as in <SAMP>example\.com</SAMP>, and a dollar sign anchor ought
23801 to come at the end of the expression to prevent a match of <SAMP>example.com.org</SAMP>.
23802 Complicating things further, the dollar sign
23803 is special in the Alpine configuration (it signifies environment variable expansion)
23804 so the dollar sign should be doubled or backslash escaped for Alpine's sake.
23805 Quotes around the whole expression will not escape the dollar sign successfully.
23806 So this example should look like
23808 <P>
23809 <CENTER><SAMP>.*@example\.com$$</SAMP></CENTER>
23810 <P>
23812 <P>
23813 The entry
23815 <P>
23816 <CENTER><SAMP>^fred[0-9]*@example.com$$</SAMP></CENTER>
23817 <P>
23819 would match
23820 <SAMP>fred3@example.com</SAMP> or <SAMP>fred17@example.com</SAMP> as well
23821 as <SAMP>fred@example.com</SAMP>.
23823 <P>
23824 You could match all addresses that look like
23825 <SAMP>fred+stuff@example.com</SAMP> for any value of <SAMP>stuff</SAMP> with the
23826 entry
23828 <P>
23829 <CENTER><SAMP>^fred\+.*@example.com$$</SAMP></CENTER>
23830 <P>
23832 Notice that you have to escape the plus sign with a backslash because plus
23833 is a special character in regular expressions.
23834 If you wanted to match plain <SAMP>fred</SAMP> as well as <SAMP>fred+stuff</SAMP>
23835 the expression
23837 <P>
23838 <CENTER><SAMP>^fred(()|\+.*)@example.com$$</SAMP></CENTER>
23839 <P>
23841 would do it, but it would be easier to just add fred@example.com as a
23842 separate entry.
23844 <P>
23845 One more example, a match of all first-level subdomains, is given by
23847 <P>
23848 <CENTER><SAMP>^fred@[[:alnum:]_-]*\.example\.com$$</SAMP></CENTER>
23849 <P>
23851 <P>
23852 Because the regular expression matching is based on an old library
23853 (<SAMP>hs_regex</SAMP>) the regular expressions might not work exactly as you expect,
23854 but they should be close.
23856 <P>
23857 <UL>
23858 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23859 </UL><P>
23860 <End of help on this topic>
23861 </BODY>
23862 </HTML>
23863 ====== h_config_abook_formats =====
23864 <HTML>
23865 <HEAD>
23866 <TITLE>OPTION: <!--#echo var="VAR_addressbook-formats"--></TITLE>
23867 </HEAD>
23868 <BODY>
23869 <H1>OPTION: <!--#echo var="VAR_addressbook-formats"--></H1>
23871 This option specifies the format that address books are displayed in.
23872 Normally, address books are displayed with the nicknames in the first
23873 column, the fullnames in the second column, and addresses in the third
23874 column. The system figures out reasonable defaults for the widths of
23875 the columns. An address book may be given a different format by
23876 listing special tokens in the order you want them to display. The
23877 possible tokens are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT.
23878 So, for example, to get the default behavior you could list
23880 <P>
23881 <CENTER><!--#echo var="VAR_addressbook-formats"-->=NICKNAME FULLNAME ADDRESS</CENTER>
23883 <P>
23884 (You can also use the token DEFAULT to get the default behavior for
23885 an address book format.)
23887 <P>
23888 The tokens are separated by spaces. "<!--#echo var="VAR_addressbook-formats"-->"
23889 is a list, so if you have more than one address book you may have a
23890 separate format for each by putting its format at the corresponding
23891 location in the "<!--#echo var="VAR_addressbook-formats"-->" list.
23893 <P>
23895 Listed first are the personal address books, then the global address
23896 books. So, if you have two personal address books and one global
23897 address book, you may have up to three formats in the
23898 "<!--#echo var="VAR_addressbook-formats"-->" list. If
23899 "<!--#echo var="VAR_addressbook-formats"-->" doesn't have as many elements as there
23900 are address books, the last element is used repeatedly.
23902 <P>
23904 Each of the tokens may also be optionally followed by parentheses with
23905 either a number or a percentage inside the parentheses. For example,
23906 <SAMP>FULLNAME(13)</SAMP> means to allocate 13 characters of space to
23907 the fullnames column, <SAMP>FULLNAME(20%)</SAMP> means to allocate 20%
23908 of the available space (the screen width minus the space for
23909 inter-column spaces) to the fullnames column, while plain
23910 <SAMP>FULLNAME</SAMP> means the system will attempt to figure out a
23911 reasonable number of columns.
23913 <P>
23914 There are always 2 spaces between every column, so if you use
23915 fixed column widths (like 13) you should remember to take that into
23916 account.
23918 <P>
23919 <UL>
23920 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23921 </UL><P>
23922 <End of help on this topic>
23923 </BODY>
23924 </HTML>
23925 ====== h_config_set_index_format =====
23926 <HTML>
23927 <HEAD>
23928 <TITLE>Set Index Format</TITLE>
23929 </HEAD>
23930 <BODY>
23931 <H1>Set Index Format</H1>
23933 This option is used to customize the content of lines in the
23934 <A HREF="h_mail_index">MESSAGE INDEX screen</A>.
23935 This action works exactly like the regular
23936 "<!--#echo var="VAR_index-format"-->" option in the Setup/Config screen,
23937 except that you can have a folder-specific value for it if you specify it here.
23938 Consult the help for
23939 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
23940 for more information.
23942 <P>
23943 <UL>
23944 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23945 </UL><P>
23946 <End of help on this topic>
23947 </BODY>
23948 </HTML>
23949 ====== h_config_index_format =====
23950 <HTML>
23951 <HEAD>
23952 <TITLE>OPTION: <!--#echo var="VAR_index-format"--></TITLE>
23953 </HEAD>
23954 <BODY>
23955 <H1>OPTION: <!--#echo var="VAR_index-format"--></H1>
23957 This option is used to customize the content of lines in the
23958 <A HREF="h_mail_index">MESSAGE INDEX screen</A>. Each line is intended
23959 to convey some amount of immediately relevant information about each
23960 message in the current folder.
23961 <P>
23963 Alpine provides a pre-defined set of informational fields with
23964 reasonable column widths automatically computed. You can, however,
23965 replace this default set by listing special tokens in the order you
23966 want them displayed.
23967 <P>
23969 The list of available tokens is
23970 <A HREF="h_index_tokens">here</A>.
23971 <P>
23973 Spaces are used to separate listed tokens. Additionally, you can
23974 specify how much of the screen's width the token's associated data
23975 should occupy on the index line by appending to the token a pair of
23976 parentheses enclosing either a number or percentage. For example,
23977 "SUBJECT(13)" means to allocate 13 characters of space to the subject
23978 column, and "SUBJECT(20%)" means to
23979 allocate 20% of the available space
23980 to the subjects column, while plain "SUBJECT" means the system will
23981 attempt to figure out a reasonable amount of space.
23982 <P>
23984 There is always one space between every pair of columns, so if you use fixed
23985 column widths (like 13) you should remember to take that into account.
23986 Several of the fields are virtually fixed-width, so it doesn't make
23987 much sense to specify the width for them. The fields STATUS,
23988 FULLSTATUS, IMAPSTATUS, MSGNO, the DATE fields, SIZE,
23989 and DESCRIPSIZE all fall into that category.
23990 You <EM>may</EM> specify widths for those if you wish, but
23991 you're probably better off letting the system pick those widths. <P>
23993 <P>
23994 The default is equivalent to:
23996 <P>
23997 <CENTER><SAMP>STATUS MSGNO SMARTDATETIME24 FROMORTO(33%) SIZENARROW SUBJKEY(67%)</SAMP></CENTER>
23999 <P>
24000 This means that the four fields without percentages will be allocated
24001 first, and then 33% and 67% of the <EM>remaining</EM> space will go to
24002 the from and subject fields. If one of those two fields is specified
24003 as a percentage and the other is left for the system to choose, then
24004 the percentage is taken as an absolute percentage of the screen, not
24005 of the space remaining after allocating the first four columns. It
24006 doesn't usually make sense to do it that way. If you leave off all
24007 the widths, then the subject and from fields (if both are present) are
24008 allocated space in a 2 to 1 ratio, which is almost exactly the same as
24009 the default.
24011 <P>
24012 What you are most likely to do with this configuration option is to
24013 specify which fields appear at all, which order they appear in, and the
24014 percentage of screen that is used for the from and subject fields if you
24015 don't like the 2 to 1 default.
24017 <P>
24018 If you want to retain the default format that Pine 4.64 had, use
24020 <P>
24021 <CENTER><SAMP><!--#echo var="VAR_index-format"-->=STATUS MSGNO DATE FROMORTO(33%) SIZE SUBJKEY(67%)</SAMP></CENTER>
24022 <P>
24023 <EM>and</EM> set the feature
24024 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>.
24025 <UL>
24026 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24027 </UL><P>
24028 <End of help on this topic>
24029 </BODY>
24030 </HTML>
24031 ====== h_config_reply_intro =====
24032 <HTML>
24033 <HEAD>
24034 <TITLE>OPTION: <!--#echo var="VAR_reply-leadin"--></TITLE>
24035 </HEAD>
24036 <BODY>
24037 <H1>OPTION: <!--#echo var="VAR_reply-leadin"--></H1>
24039 This option is used to customize the content of the introduction line
24040 that is included when replying to a message and including the original
24041 message in the reply.
24042 The normal default (what you will get if you delete this variable) looks
24043 something like:
24044 <P>
24045 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
24046 <P>
24047 where the day of the week is only included if it is available in the
24048 original message.
24049 You can replace this default with text of your own.
24050 The text may contain tokens that are replaced with text
24051 that depends on the message you are replying to.
24052 For example, the default is equivalent to:
24053 <P>
24054 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
24055 <P>
24057 Since this variable includes regular text mixed with special tokens
24058 the tokens have to be surrounded by underscore characters.
24059 For example, to use the token "<SAMP>PREFDATE</SAMP>"
24060 you would need to use "<SAMP>_PREFDATE_</SAMP>",
24061 not "<SAMP>PREFDATE</SAMP>".
24062 <P>
24063 The list of available tokens is
24064 <A HREF="h_index_tokens">here</A>.
24066 <P>
24067 By default, the text is all on a single line and is followed by a blank line.
24068 If your "<!--#echo var="VAR_reply-leadin"-->" turns out to be longer
24069 than 80 characters when replying to a particular message, it is shortened.
24070 However, if you use the token
24071 <P>
24072 <CENTER><SAMP>_NEWLINE_</SAMP></CENTER>
24073 <P>
24075 anywhere in the value, no end of line or blank line is appended, and no
24076 shortening is done.
24077 The _NEWLINE_ token may be used to get rid of the blank line following
24078 the text, to add more blank lines, or to form a multi-line
24079 "<!--#echo var="VAR_reply-leadin"-->".
24080 To clarify how _NEWLINE_ works recall that the default value is:
24081 <P>
24082 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
24083 <P>
24085 That is equivalent to
24086 <P>
24087 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE__NEWLINE_</SAMP></CENTER>
24088 <P>
24090 In the former case, two newlines are added automatically because
24091 no _NEWLINE_ token appears in the value of the option (for backwards
24092 compatibility). In the latter case, the newlines are explicit.
24093 If you want to remove the blank line that follows the
24094 "<!--#echo var="VAR_reply-leadin"-->" text use a single
24095 _NEWLINE_ token like
24096 <P>
24097 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE_</SAMP></CENTER>
24098 <P>
24100 Because of the backwards compatibility problem, it is not possible to
24101 remove all of the ends of lines, because then there will be no _NEWLINE_ tokens
24102 and that will cause the automatic adding of two newlines!
24103 If you want, you may embed newlines in the middle of the text, as well,
24104 producing a multi-line "<!--#echo var="VAR_reply-leadin"-->".
24106 <P>
24107 By default, no attempt is made to localize the date.
24108 If you prefer a localized form you may find that one of the tokens
24109 _PREFDATE_ or _PREFDATETIME_ is a satisfactory substitute.
24110 If you want more control one of the many other date tokens, such as _DATEISO_,
24111 might be better.
24113 <P>
24114 For the adventurous, there is a way to conditionally include text based
24115 on whether or not a token would result in specific replacement text.
24116 For example, you could include some text based on whether or not
24117 the _NEWS_ token would result in any newsgroups if it was used.
24118 It's explained in detail
24119 <A HREF="h_reply_token_conditionals">here</A>.
24121 <P>
24122 In the very unlikely event that you want to include a literal token
24123 in the introduction line you must precede it with a backslash character.
24124 For example,
24125 <P>
24126 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
24127 <P>
24128 would produce something like
24129 <P>
24130 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
24131 <P>
24132 It is not possible to have a literal backslash followed by an expanded token.
24133 <P>
24134 <UL>
24135 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24136 </UL><P>
24137 <End of help on this topic>
24138 </BODY>
24139 </HTML>
24140 ====== h_config_remote_abook_history =====
24141 <HTML>
24142 <HEAD>
24143 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-history"--></TITLE>
24144 </HEAD>
24145 <BODY>
24146 <H1>OPTION: <!--#echo var="VAR_remote-abook-history"--></H1>
24148 Sets how many extra copies of
24149 remote address book
24150 data will be kept in each remote address book folder.
24151 The default is three.
24152 These extra copies are simply old versions of the data. Each time a change
24153 is made a new copy of the address book data is appended to the folder. Old
24154 copies are trimmed, if possible, when Alpine exits.
24155 An old copy can be put back into use by
24156 deleting and expunging newer versions of the data from the folder.
24157 Don't delete the first message from the folder. It is a special header
24158 message for the remote address book and it must be there.
24159 This is to prevent regular folders from being used as remote address book
24160 folders and having their data destroyed.
24161 <P>
24162 This option is also used to determine how many extra copies of remote
24163 Alpine configuration files are kept.
24164 <P>
24165 <UL>
24166 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24167 </UL><P>
24168 <End of help on this topic>
24169 </BODY>
24170 </HTML>
24171 ====== h_config_remote_abook_validity =====
24172 <HTML>
24173 <HEAD>
24174 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-validity"--></TITLE>
24175 </HEAD>
24176 <BODY>
24177 <H1>OPTION: <!--#echo var="VAR_remote-abook-validity"--></H1>
24179 Sets the minimum number of minutes that a
24180 remote address book will be considered up to date.
24181 Whenever an entry contained in a remote address book is used,
24182 if more than this many minutes have
24183 passed since the last check the remote server will be queried to see if the
24184 address book has changed.
24185 If it has changed, the local copy is updated.
24186 The default value is five minutes.
24187 The special value of -1 means never check.
24188 The special value of zero means only check when the address book is first
24189 opened.
24190 <P>
24191 No matter what the value, the validity check is always done when the
24192 address book is about to be changed by the user.
24193 The check can be initiated manually by typing <EM>^L</EM> (Ctrl-L)
24194 while in the address book maintenance screen for the remote address book.
24195 <P>
24196 <UL>
24197 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24198 </UL><P>
24199 <End of help on this topic>
24200 </BODY>
24201 </HTML>
24202 ====== h_config_user_input_timeo =====
24203 <HTML>
24204 <HEAD>
24205 <TITLE>OPTION: <!--#echo var="VAR_user-input-timeout"--></TITLE>
24206 </HEAD>
24207 <BODY>
24208 <H1>OPTION: <!--#echo var="VAR_user-input-timeout"--></H1>
24210 If this is set to an integer greater than zero, then this is the number
24211 of <EM>hours</EM> to wait for user input before Alpine times out.
24212 If Alpine is
24213 in the midst of composing a message or is waiting for user response to
24214 a question, then it will not timeout.
24215 However, if Alpine is sitting idle waiting for
24216 the user to tell it what to do next and the user does not give any
24217 input for this many hours, Alpine will exit.
24218 No expunging or moving of read
24219 messages will take place.
24220 It will exit similarly to the way it would exit
24221 if it received a hangup signal.
24222 This may be useful for cleaning up unused Alpine sessions that have been
24223 forgotten by their owners.
24224 The Alpine developers envision system administrators
24225 setting this to a value of several hours (24?) so that it won't surprise
24226 a user who didn't want to be disconnected.
24227 <P>
24228 <UL>
24229 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24230 </UL><P>
24231 <End of help on this topic>
24232 </BODY>
24233 </HTML>
24234 ====== h_config_ssh_open_timeo =====
24235 <HTML>
24236 <HEAD>
24237 <TITLE>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></TITLE>
24238 </HEAD>
24239 <BODY>
24240 <H1>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></H1>
24242 Sets the time in seconds that Alpine will
24243 attempt to open a UNIX secure shell connection.
24244 The default is 15, the minimum non-zero value is 5,
24245 and the maximum is unlimited. If this is set to zero ssh connections
24246 will be completely disabled.
24247 <P>
24248 <UL>
24249 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24250 </UL><P>
24251 <End of help on this topic>
24252 </BODY>
24253 </HTML>
24254 ====== h_config_rsh_open_timeo =====
24255 <HTML>
24256 <HEAD>
24257 <TITLE>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></TITLE>
24258 </HEAD>
24259 <BODY>
24260 <H1>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></H1>
24262 Sets the time in seconds that Alpine will
24263 attempt to open a UNIX remote shell connection.
24264 The default is 15, the minimum non-zero value is 5,
24265 and the maximum is unlimited. If this is set to zero rsh connections
24266 will be completely disabled.
24267 This might be useful if rsh connections will never work in your environment
24268 but are causing delays due to firewalls or some other reason.
24269 <P>
24270 <UL>
24271 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24272 </UL><P>
24273 <End of help on this topic>
24274 </BODY>
24275 </HTML>
24276 ====== h_config_tcp_open_timeo =====
24277 <HTML>
24278 <HEAD>
24279 <TITLE>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></TITLE>
24280 </HEAD>
24281 <BODY>
24282 <H1>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></H1>
24284 Sets the time in seconds that Alpine will
24285 attempt to open a network connection. The default is 30, the minimum is 5,
24286 and the maximum is system defined (typically 75). If a connection has not
24287 completed within this many seconds Alpine will give up and consider it a
24288 failed connection.
24289 <P>
24290 <UL>
24291 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24292 </UL><P>
24293 <End of help on this topic>
24294 </BODY>
24295 </HTML>
24296 ====== h_config_tcp_readwarn_timeo =====
24297 <HTML>
24298 <HEAD>
24299 <TITLE>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></TITLE>
24300 </HEAD>
24301 <BODY>
24302 <H1>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></H1>
24304 Sets the time in seconds that Alpine will
24305 wait for a network read before warning you that things are moving slowly
24306 and possibly giving you the option to break the connection.
24307 The default is 15 seconds. The minimum is 5 seconds and the maximumn is
24308 1000 seconds.
24309 <P>
24310 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24311 <P>
24312 <UL>
24313 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24314 </UL><P>
24315 <End of help on this topic>
24316 </BODY>
24317 </HTML>
24318 ====== h_config_tcp_writewarn_timeo =====
24319 <HTML>
24320 <HEAD>
24321 <TITLE>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></TITLE>
24322 </HEAD>
24323 <BODY>
24324 <H1>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></H1>
24326 Sets the time in seconds that Alpine will
24327 wait for a network write before warning you that things are moving slowly
24328 and possibly giving you the option to break the connection.
24329 The default is 0 which means it is unset. If set to a non-zero value, the
24330 minimum is 5 and the maximum is 1000.
24331 <P>
24332 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24333 <P>
24334 <UL>
24335 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24336 </UL><P>
24337 <End of help on this topic>
24338 </BODY>
24339 </HTML>
24340 ====== h_config_tcp_query_timeo =====
24341 <HTML>
24342 <HEAD>
24343 <TITLE>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></TITLE>
24344 </HEAD>
24345 <BODY>
24346 <H1>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></H1>
24348 When Alpine times out a network read or write it will normally just display
24349 a message saying "Still waiting".
24350 However, if enough time has elapsed since it started waiting it will offer
24351 to let you break the connection.
24352 That amount of time is set by this option, which defaults to 60 seconds,
24353 has a minimum of 5 seconds, and a maximum of 1000 seconds.
24354 <P>
24355 <UL>
24356 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24357 </UL><P>
24358 <End of help on this topic>
24359 </BODY>
24360 </HTML>
24361 ====== h_config_incoming_folders =====
24362 <HTML>
24363 <HEAD>
24364 <TITLE>OPTION: <!--#echo var="VAR_incoming-folders"--></TITLE>
24365 </HEAD>
24366 <BODY>
24367 <H1>OPTION: <!--#echo var="VAR_incoming-folders"--></H1>
24369 This is a list of one or more folders other than <EM>INBOX</EM> that
24370 may receive new messages.
24371 It is related to the
24372 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
24373 feature.
24374 This variable is normally manipulated with the Add, Delete, and Rename
24375 commands in the FOLDER LIST for the Incoming Message Folders collection.
24376 <P>
24377 <UL>
24378 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24379 </UL><P>
24380 <End of help on this topic>
24381 </BODY>
24382 </HTML>
24383 ====== h_config_folder_spec =====
24384 <HTML>
24385 <HEAD>
24386 <TITLE>OPTION: <!--#echo var="VAR_folder-collections"--></TITLE>
24387 </HEAD>
24388 <BODY>
24389 <H1>OPTION: <!--#echo var="VAR_folder-collections"--></H1>
24391 This is a list of one or more collections where saved mail is stored.
24392 The first collection in this list is the default
24393 collection for <EM>Save</EM>s,
24394 including <A HREF="h_config_default_fcc"><!--#echo var="VAR_default-fcc"--></A>.
24395 <P>
24396 This variable is normally manipulated using the Setup/collectionList screen.
24397 <P>
24398 <UL>
24399 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24400 </UL><P>
24401 <End of help on this topic>
24402 </BODY>
24403 </HTML>
24404 ====== h_config_news_spec =====
24405 <HTML>
24406 <HEAD>
24407 <TITLE>OPTION: <!--#echo var="VAR_news-collections"--></TITLE>
24408 </HEAD>
24409 <BODY>
24410 <H1>OPTION: <!--#echo var="VAR_news-collections"--></H1>
24412 This is a list of collections where news folders are located.
24413 <P>
24414 This variable is normally manipulated using the Setup/collectionList screen.
24415 <P>
24416 <UL>
24417 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24418 </UL><P>
24419 <End of help on this topic>
24420 </BODY>
24421 </HTML>
24422 ====== h_config_address_book =====
24423 <HTML>
24424 <HEAD>
24425 <TITLE>OPTION: <!--#echo var="VAR_address-book"--></TITLE>
24426 </HEAD>
24427 <BODY>
24428 <H1>OPTION: <!--#echo var="VAR_address-book"--></H1>
24430 A list of personal address books.
24431 Each entry in the list is an
24432 optional nickname followed by a pathname or file name relative to the home
24433 directory.
24434 The nickname is separated from the rest of the line with whitespace.
24435 Instead of a local pathname or file name, a remote folder name can be given.
24436 This causes the address book to
24437 be a Remote address book.
24438 <P>
24439 Use the Setup/AddressBook screen to modify this variable.
24440 <P>
24441 <UL>
24442 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24443 </UL><P>
24444 <End of help on this topic>
24445 </BODY>
24446 </HTML>
24447 ====== h_config_glob_addrbook =====
24448 <HTML>
24449 <HEAD>
24450 <TITLE>OPTION: <!--#echo var="VAR_global-address-book"--></TITLE>
24451 </HEAD>
24452 <BODY>
24453 <H1>OPTION: <!--#echo var="VAR_global-address-book"--></H1>
24455 A list of shared address books. Each entry in the list is an
24456 optional nickname followed by a pathname or file name relative to the home
24457 directory.
24458 A SPACE character separates the nickname from the rest of the line.
24459 Instead of a local pathname or file name, a remote folder name can be given.
24460 This causes the address book to
24461 be a Remote address book.
24462 Global address books are
24463 defined to be ReadOnly.
24464 <P>
24465 Use the Setup/AddressBook screen to modify this variable.
24466 <P>
24467 <UL>
24468 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24469 </UL><P>
24470 <End of help on this topic>
24471 </BODY>
24472 </HTML>
24473 ====== h_config_last_vers =====
24474 <HTML>
24475 <HEAD>
24476 <TITLE>OPTION: <!--#echo var="VAR_last-version-used"--></TITLE>
24477 </HEAD>
24478 <BODY>
24479 <H1>OPTION: <!--#echo var="VAR_last-version-used"--></H1>
24481 This is set automatically by Alpine.
24482 It is used to keep track of the last version of Alpine that
24483 was run by the user.
24484 Whenever the version number increases, a new version message is printed out.
24485 This may not be set in the system-wide configuration files.
24486 <P>
24487 <UL>
24488 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24489 </UL><P>
24490 <End of help on this topic>
24491 </BODY>
24492 </HTML>
24493 ====== h_config_printer =====
24494 <HTML>
24495 <HEAD>
24496 <TITLE>OPTION: Printer</TITLE>
24497 </HEAD>
24498 <BODY>
24499 <H1>OPTION: Printer</H1>
24501 Your default printer selection.
24502 <P>
24503 Use the Setup/Printer screen to modify this variable.
24504 <P>
24505 <UL>
24506 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24507 </UL><P>
24508 <End of help on this topic>
24509 </BODY>
24510 </HTML>
24511 ====== h_config_print_cat =====
24512 <HTML>
24513 <HEAD>
24514 <TITLE>OPTION: <!--#echo var="VAR_personal-print-category"--></TITLE>
24515 </HEAD>
24516 <BODY>
24517 <H1>OPTION: <!--#echo var="VAR_personal-print-category"--></H1>
24519 This is an internal Alpine variable.
24520 It will be equal to 1, 2, or 3 depending on whether the default printer is
24521 attached, standard, or a personal print command.
24522 <P>
24523 Use the Setup/Printer screen to modify this variable.
24524 <P>
24525 <UL>
24526 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24527 </UL><P>
24528 <End of help on this topic>
24529 </BODY>
24530 </HTML>
24531 ====== h_config_print_command =====
24532 <HTML>
24533 <HEAD>
24534 <TITLE>OPTION: <!--#echo var="VAR_personal-print-command"--></TITLE>
24535 </HEAD>
24536 <BODY>
24537 <H1>OPTION: <!--#echo var="VAR_personal-print-command"--></H1>
24539 List of personal print commands.
24540 <P>
24541 Use the Setup/Printer screen to modify this variable.
24542 <P>
24543 <UL>
24544 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24545 </UL><P>
24546 <End of help on this topic>
24547 </BODY>
24548 </HTML>
24549 ====== h_config_pat_old =====
24550 <HTML>
24551 <HEAD>
24552 <TITLE>OPTION: Patterns</TITLE>
24553 </HEAD>
24554 <BODY>
24555 <H1>OPTION: Patterns</H1>
24557 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by the
24558 options Patterns-Roles, Patterns-Filters, Patterns-Scores, Patterns-Indexcolors,
24559 and Patterns-Other.
24560 Patterns-Scores and Patterns-Filters have been replaced since then by
24561 Patterns-Scores2 and Patterns-Filters2.
24562 <P>
24563 Use the Setup/Rules screens to modify these variable.
24564 <P>
24565 <UL>
24566 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24567 </UL><P>
24568 <End of help on this topic>
24569 </BODY>
24570 </HTML>
24571 ====== h_config_pat_roles =====
24572 <HTML>
24573 <HEAD>
24574 <TITLE>OPTION: <!--#echo var="VAR_patterns-roles"--></TITLE>
24575 </HEAD>
24576 <BODY>
24577 <H1>OPTION: <!--#echo var="VAR_patterns-roles"--></H1>
24579 List of rules used for roles.
24580 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by this and
24581 other options.
24582 <P>
24583 Use the Setup/Rules/Roles screen to modify this variable.
24584 <P>
24585 <UL>
24586 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24587 </UL><P>
24588 <End of help on this topic>
24589 </BODY>
24590 </HTML>
24591 ====== h_config_pat_filts =====
24592 <HTML>
24593 <HEAD>
24594 <TITLE>OPTION: <!--#echo var="VAR_patterns-filters2"--></TITLE>
24595 </HEAD>
24596 <BODY>
24597 <H1>OPTION: <!--#echo var="VAR_patterns-filters2"--></H1>
24599 List of rules used for filters.
24600 <P>
24601 Use the Setup/Rules/Filters screen to modify this variable.
24602 <P>
24603 <UL>
24604 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24605 </UL><P>
24606 <End of help on this topic>
24607 </BODY>
24608 </HTML>
24609 ====== h_config_pat_scores =====
24610 <HTML>
24611 <HEAD>
24612 <TITLE>OPTION: <!--#echo var="VAR_patterns-scores2"--></TITLE>
24613 </HEAD>
24614 <BODY>
24615 <H1>OPTION: <!--#echo var="VAR_patterns-scores2"--></H1>
24617 List of rules used for scoring.
24618 <P>
24619 Use the Setup/Rules/SetScores screen to modify this variable.
24620 <P>
24621 <UL>
24622 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24623 </UL><P>
24624 <End of help on this topic>
24625 </BODY>
24626 </HTML>
24627 ====== h_config_pat_other =====
24628 <HTML>
24629 <HEAD>
24630 <TITLE>OPTION: <!--#echo var="VAR_patterns-other"--></TITLE>
24631 </HEAD>
24632 <BODY>
24633 <H1>OPTION: <!--#echo var="VAR_patterns-other"--></H1>
24635 List of rules used for miscellaneous configuration.
24636 <P>
24637 Use the Setup/Rules/Other screen to modify this variable.
24638 <P>
24639 <UL>
24640 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24641 </UL><P>
24642 <End of help on this topic>
24643 </BODY>
24644 </HTML>
24645 ====== h_config_pat_incols =====
24646 <HTML>
24647 <HEAD>
24648 <TITLE>OPTION: patterns-indexcolors</TITLE>
24649 </HEAD>
24650 <BODY>
24651 <H1>OPTION: patterns-indexcolors</H1>
24653 List of rules used for coloring lines in the index.
24654 <P>
24655 Use the Setup/Rules/Indexcolor screen to modify this variable.
24656 <P>
24657 <UL>
24658 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24659 </UL><P>
24660 <End of help on this topic>
24661 </BODY>
24662 </HTML>
24663 ====== h_config_pat_srch =====
24664 <HTML>
24665 <HEAD>
24666 <TITLE>OPTION: patterns-search</TITLE>
24667 </HEAD>
24668 <BODY>
24669 <H1>OPTION: patterns-search</H1>
24671 List of rules used only for searching with the Select command in the MESSAGE INDEX.
24672 <P>
24673 Use the Setup/Rules/searCh screen to modify this variable.
24674 <P>
24675 <UL>
24676 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24677 </UL><P>
24678 <End of help on this topic>
24679 </BODY>
24680 </HTML>
24681 ====== h_config_font_name =====
24682 <HTML>
24683 <HEAD>
24684 <TITLE>OPTION: Font Name</TITLE>
24685 </HEAD>
24686 <BODY>
24687 <H1>OPTION: Font Name</H1>
24689 PC-Alpine only.
24690 <P>
24691 Name of normal font.
24692 <P>
24693 Use the pulldown Config menu to modify this variable.
24694 <P>
24695 <UL>
24696 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24697 </UL><P>
24698 <End of help on this topic>
24699 </BODY>
24700 </HTML>
24701 ====== h_config_font_size =====
24702 <HTML>
24703 <HEAD>
24704 <TITLE>OPTION: Font Size</TITLE>
24705 </HEAD>
24706 <BODY>
24707 <H1>OPTION: Font Size</H1>
24709 PC-Alpine only.
24710 <P>
24711 Size of normal font.
24712 <P>
24713 Use the pulldown Config menu to modify this variable.
24714 <P>
24715 <UL>
24716 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24717 </UL><P>
24718 <End of help on this topic>
24719 </BODY>
24720 </HTML>
24721 ====== h_config_font_style =====
24722 <HTML>
24723 <HEAD>
24724 <TITLE>OPTION: Font Style</TITLE>
24725 </HEAD>
24726 <BODY>
24727 <H1>OPTION: Font Style</H1>
24729 PC-Alpine only.
24730 <P>
24731 Style of normal font.
24732 <P>
24733 Use the pulldown Config menu to modify this variable.
24734 <P>
24735 <UL>
24736 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24737 </UL><P>
24738 <End of help on this topic>
24739 </BODY>
24740 </HTML>
24741 ====== h_config_font_char_set =====
24742 <HTML>
24743 <HEAD>
24744 <TITLE>OPTION: Font Character Set</TITLE>
24745 </HEAD>
24746 <BODY>
24747 <H1>OPTION: Font Character Set</H1>
24749 PC-Alpine only.
24750 <P>
24751 Character set of normal font.
24752 <P>
24753 Use the pulldown Config menu to modify this variable.
24754 <P>
24755 <UL>
24756 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24757 </UL><P>
24758 <End of help on this topic>
24759 </BODY>
24760 </HTML>
24761 ====== h_config_print_font_name =====
24762 <HTML>
24763 <HEAD>
24764 <TITLE>OPTION: Print-Font-Name</TITLE>
24765 </HEAD>
24766 <BODY>
24767 <H1>OPTION: Print-Font-Name</H1>
24769 PC-Alpine only.
24770 <P>
24771 Name of printer font.
24772 <P>
24773 Use the pulldown Config menu to modify this variable.
24774 <P>
24775 <UL>
24776 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24777 </UL><P>
24778 <End of help on this topic>
24779 </BODY>
24780 </HTML>
24781 ====== h_config_print_font_size =====
24782 <HTML>
24783 <HEAD>
24784 <TITLE>OPTION: Print-Font-Size</TITLE>
24785 </HEAD>
24786 <BODY>
24787 <H1>OPTION: Print-Font-Size</H1>
24789 PC-Alpine only.
24790 <P>
24791 Size of printer font.
24792 <P>
24793 Use the pulldown Config menu to modify this variable.
24794 <P>
24795 <UL>
24796 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24797 </UL><P>
24798 <End of help on this topic>
24799 </BODY>
24800 </HTML>
24801 ====== h_config_print_font_style =====
24802 <HTML>
24803 <HEAD>
24804 <TITLE>OPTION: Print-Font-Style</TITLE>
24805 </HEAD>
24806 <BODY>
24807 <H1>OPTION: Print-Font-Style</H1>
24809 PC-Alpine only.
24810 <P>
24811 Style of printer font.
24812 <P>
24813 Use the pulldown Config menu to modify this variable.
24814 <P>
24815 <UL>
24816 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24817 </UL><P>
24818 <End of help on this topic>
24819 </BODY>
24820 </HTML>
24821 ====== h_config_print_font_char_set =====
24822 <HTML>
24823 <HEAD>
24824 <TITLE>OPTION: Print-Font-Char-Set</TITLE>
24825 </HEAD>
24826 <BODY>
24827 <H1>OPTION: Print-Font-Char-Set</H1>
24829 PC-Alpine only.
24830 <P>
24831 Character set of printer font.
24832 <P>
24833 Use the pulldown Config menu to modify this variable.
24834 <P>
24835 <UL>
24836 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24837 </UL><P>
24838 <End of help on this topic>
24839 </BODY>
24840 </HTML>
24841 ====== h_config_window_position =====
24842 <HTML>
24843 <HEAD>
24844 <TITLE>OPTION: Window-Position</TITLE>
24845 </HEAD>
24846 <BODY>
24847 <H1>OPTION: Window-Position</H1>
24849 PC-Alpine only.
24850 <P>
24851 Position on the screen of the Alpine window.
24852 <P>
24853 Alpine normally maintains this variable itself, and it is set automatically.
24854 This variable is provided to those who wish to use the same window position
24855 across different machines from the same configuration.
24856 <A HREF="h_config_winpos_in_config"><!--#echo var="FEAT_store-window-position-in-config"--></A>
24857 must also be set for this setting to be used.
24858 <P>
24859 The format for this variable is of the form: <CODE>CxR+X+Y</CODE>, where
24860 C is the number of columns, R is the number of rows, and X and Y specify the
24861 top left corner of the window.
24862 <P>
24863 <UL>
24864 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24865 </UL><P>
24866 <End of help on this topic>
24867 </BODY>
24868 </HTML>
24869 ====== h_config_cursor_style =====
24870 <HTML>
24871 <HEAD>
24872 <TITLE>OPTION: Cursor Style</TITLE>
24873 </HEAD>
24874 <BODY>
24875 <H1>OPTION: Cursor Style</H1>
24877 PC-Alpine only.
24878 <P>
24879 Cursor style.
24880 <P>
24881 Use the pulldown Config menu to modify this variable.
24882 <P>
24883 <UL>
24884 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24885 </UL><P>
24886 <End of help on this topic>
24887 </BODY>
24888 </HTML>
24889 ====== h_config_ldap_servers =====
24890 <HTML>
24891 <HEAD>
24892 <TITLE>OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
24893 </HEAD>
24894 <BODY>
24895 <H1>OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
24897 List of LDAP servers and associated data.
24898 <P>
24899 Use the Setup/Directory screen to modify this variable.
24900 <P>
24901 <UL>
24902 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24903 </UL><P>
24904 <End of help on this topic>
24905 </BODY>
24906 </HTML>
24907 ====== h_config_sendmail_path =====
24908 <HTML>
24909 <HEAD>
24910 <TITLE>OPTION: <!--#echo var="VAR_sendmail-path"--></TITLE>
24911 </HEAD>
24912 <BODY>
24913 <H1>OPTION: <!--#echo var="VAR_sendmail-path"--></H1>
24915 This names the path to an
24916 alternative program, and any necessary arguments, to be used in posting
24917 mail messages. See the Technical notes for more information.
24918 <P>
24919 <UL>
24920 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24921 </UL><P>
24922 <End of help on this topic>
24923 </BODY>
24924 </HTML>
24925 ====== h_config_oper_dir =====
24926 <HTML>
24927 <HEAD>
24928 <TITLE>OPTION: <!--#echo var="VAR_operating-dir"--></TITLE>
24929 </HEAD>
24930 <BODY>
24931 <H1>OPTION: <!--#echo var="VAR_operating-dir"--></H1>
24933 This names the root of the
24934 tree to which you are restricted when reading and writing folders and
24935 files. It is usually used in the system-wide,
24936 <EM>fixed</EM> configuration file.
24937 <P>
24938 <UL>
24939 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24940 </UL><P>
24941 <End of help on this topic>
24942 </BODY>
24943 </HTML>
24944 ====== h_config_rshpath =====
24945 <HTML>
24946 <HEAD>
24947 <TITLE>OPTION: <!--#echo var="VAR_rsh-path"--></TITLE>
24948 </HEAD>
24949 <BODY>
24950 <H1>OPTION: <!--#echo var="VAR_rsh-path"--></H1>
24952 Sets the name of the command used to open a UNIX remote shell
24953 connection. The default is typically <CODE>/usr/ucb/rsh</CODE>.
24954 <P>
24955 <UL>
24956 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24957 </UL><P>
24958 <End of help on this topic>
24959 </BODY>
24960 </HTML>
24961 ====== h_config_rshcmd =====
24962 <HTML>
24963 <HEAD>
24964 <TITLE>OPTION: <!--#echo var="VAR_rsh-command"--></TITLE>
24965 </HEAD>
24966 <BODY>
24967 <H1>OPTION: <!--#echo var="VAR_rsh-command"--></H1>
24969 Sets the format of the command used to
24970 open a UNIX remote shell connection. The default is
24971 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
24972 provided command. The first is for the command's pathname, the second is
24973 for the host to connnect to, the third is for the user to connect as, and
24974 the fourth is for the connection method (typically <CODE>imap</CODE>).
24975 <P>
24976 <UL>
24977 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24978 </UL><P>
24979 <End of help on this topic>
24980 </BODY>
24981 </HTML>
24982 ====== h_config_sshpath =====
24983 <HTML>
24984 <HEAD>
24985 <TITLE>OPTION: <!--#echo var="VAR_ssh-path"--></TITLE>
24986 </HEAD>
24987 <BODY>
24988 <H1>OPTION: <!--#echo var="VAR_ssh-path"--></H1>
24990 Sets the name of the command used to open a UNIX secure shell
24991 connection. The default is typically <CODE>/usr/bin/ssh</CODE>.
24992 <P>
24993 <UL>
24994 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24995 </UL><P>
24996 <End of help on this topic>
24997 </BODY>
24998 </HTML>
24999 ====== h_config_sshcmd =====
25000 <HTML>
25001 <HEAD>
25002 <TITLE>OPTION: <!--#echo var="VAR_ssh-command"--></TITLE>
25003 </HEAD>
25004 <BODY>
25005 <H1>OPTION: <!--#echo var="VAR_ssh-command"--></H1>
25007 Sets the format of the command used to
25008 open a UNIX secure shell connection. The default is
25009 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
25010 provided command. The first is for the command's pathname, the second is
25011 for the host to connnect to, the third is for the user to connect as, and
25012 the fourth is for the connection method (typically <CODE>imap</CODE>).
25013 <P>
25014 <UL>
25015 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25016 </UL><P>
25017 <End of help on this topic>
25018 </BODY>
25019 </HTML>
25020 ====== h_config_new_ver_quell =====
25021 <HTML>
25022 <HEAD>
25023 <TITLE>OPTION: <!--#echo var="VAR_new-version-threshold"--></TITLE>
25024 </HEAD>
25025 <BODY>
25026 <H1>OPTION: <!--#echo var="VAR_new-version-threshold"--></H1>
25028 When a new version of Alpine is run for the first time it offers a
25029 special explanatory screen to the user upon startup. This option
25030 helps control when and if that special screen appears for users that
25031 have previously run Alpine. It takes as its value an Alpine version
25032 number. Alpine versions less than the specified value will supress this
25033 special screen while versions equal to or greater than that specified
25034 will behave normally.
25035 <P>
25036 <UL>
25037 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25038 </UL><P>
25039 <End of help on this topic>
25040 </BODY>
25041 </HTML>
25042 ====== h_config_disable_drivers =====
25043 <HTML>
25044 <HEAD>
25045 <TITLE>OPTION: <!--#echo var="VAR_disable-these-drivers"--></TITLE>
25046 </HEAD>
25047 <BODY>
25048 <H1>OPTION: <!--#echo var="VAR_disable-these-drivers"--></H1>
25050 This variable is a list of mail drivers that will be disabled.
25051 The candidates for disabling are listed below.
25052 There may be more in the future if you compile Alpine with
25053 a newer version of the c-client library.
25054 <P>
25056 <UL>
25057 <LI> mbox
25058 <LI> mbx
25059 <LI> mh
25060 <LI> mmdf
25061 <LI> mtx
25062 <LI> mx
25063 <LI> news
25064 <LI> phile
25065 <LI> tenex
25066 <LI> unix
25067 </UL>
25068 <P>
25070 The <EM>mbox</EM> driver enables the following behavior: if there is a
25071 file called <CODE>mbox</CODE>
25072 in your home directory, and if that file is either empty or in Unix mailbox
25073 format, then every time you open <EM>INBOX</EM> the <EM>mbox</EM> driver
25074 will automatically transfer mail from the system mail spool directory into the
25075 <CODE>mbox</CODE> file and
25076 delete it from the spool directory. If you disable the <EM>mbox</EM> driver,
25077 this will not happen.
25078 <P>
25080 It is not recommended to disable the driver that supports the system default
25081 mailbox format. On most non-SCO systems, that driver is the
25082 <EM>unix</EM> driver.
25083 On most SCO systems, it is the <EM>mmdf</EM> driver.
25084 The system default driver may be
25085 configured to something else on your system; check with your system manager
25086 for additional information.
25087 <P>
25089 It is most likely not very useful for you to disable any of the drivers other
25090 than possibly <EM>mbox</EM>.
25091 You could disable some of the others if you know for
25092 certain that you don't need them but the performance gain in doing so
25093 is very modest.
25094 <P>
25095 <UL>
25096 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25097 </UL><P>
25098 <End of help on this topic>
25099 </BODY>
25100 </HTML>
25101 ====== h_config_disable_auths =====
25102 <HTML>
25103 <HEAD>
25104 <TITLE>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></TITLE>
25105 </HEAD>
25106 <BODY>
25107 <H1>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></H1>
25109 This variable is a list of SASL (Simple Authentication and Security
25110 Layer) authenticators that will be disabled.
25111 SASL is a mechanism for
25112 authenticating to IMAP, POP3, SMTP, and other network servers.
25113 <P>
25115 Alpine matches its list of supported authenticators with the server to
25116 determine the most secure authenticator that is supported by both.
25117 If no matching authenticators are found, Alpine will revert to plaintext
25118 login (or, in the case of SMTP, will be unable to authenticate at all).
25119 <P>
25120 The candidates for disabling can be found <A HREF="X-Alpine-Config:">here</A>.
25121 <P>
25123 Normally, you will not disable any authenticators.
25124 There are two exceptions:
25125 <P>
25126 <OL>
25127 <LI> You use a broken server that advertises an authenticator,
25128 but does not actually implement it.
25129 <LI> You have a Kerberos-capable version of Alpine and the server is
25130 also Kerberos-capable, but you can not obtain Kerberos
25131 credentials on the server machine, thus you desire to disable
25132 GSSAPI (which in turn disables Alpine's Kerberos support).
25133 </OL>
25134 <P>
25135 It is never necessary to disable authenticators, since Alpine will try
25136 other authenticators before giving up.
25137 However, disabling the relevant authenticator avoids annoying error messages.
25138 <P>
25139 <UL>
25140 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25141 </UL><P>
25142 <End of help on this topic>
25143 </BODY>
25144 </HTML>
25145 ====== h_config_abook_metafile =====
25146 <HTML>
25147 <HEAD>
25148 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></TITLE>
25149 </HEAD>
25150 <BODY>
25151 <H1>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></H1>
25153 This is usually set by Alpine and is the name of a file
25154 that contains data about
25155 remote address books and remote configuration files.
25156 <P>
25157 <UL>
25158 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25159 </UL><P>
25160 <End of help on this topic>
25161 </BODY>
25162 </HTML>
25163 ====== h_config_composer_wrap_column =====
25164 <HTML>
25165 <HEAD>
25166 <TITLE>OPTION: <!--#echo var="VAR_composer-wrap-column"--></TITLE>
25167 </HEAD>
25168 <BODY>
25169 <H1>OPTION: <!--#echo var="VAR_composer-wrap-column"--></H1>
25172 This option specifies an aspect of Alpine's Composer. This gives the
25173 maximum width that auto-wrapped lines will have. It's also the maximum
25174 width of lines justified using the <A HREF="h_compose_justify">^J
25175 Justify</A> command. The normal default
25176 is "74". The largest allowed setting is normally "80"
25177 in order to
25178 prevent very long lines from being sent in outgoing mail. When the mail
25179 is actually sent, trailing spaces will be stripped off of each line.
25181 <P>
25182 <UL>
25183 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25184 </UL><P>
25185 <End of help on this topic>
25186 </BODY>
25187 </HTML>
25188 ====== h_config_deadlets =====
25189 <HTML>
25190 <HEAD>
25191 <TITLE>OPTION: <!--#echo var="VAR_dead-letter-files"--></TITLE>
25192 </HEAD>
25193 <BODY>
25194 <H1>OPTION: <!--#echo var="VAR_dead-letter-files"--></H1>
25197 This option affects Alpine's behavior when you cancel a message being
25198 composed. Alpine's usual behavior is to write the canceled message to
25199 a file named
25200 <!--chtml if pinemode="os_windows"-->
25201 "DEADLETR",
25202 <!--chtml else-->
25203 "dead.letter" in your home directory,
25204 <!--chtml endif-->
25205 overwriting any previous message.
25206 <P>
25207 If you set this option to a value higher than one, then that many copies
25208 of dead letter files will be saved.
25209 For example, if you set this option to "3" then you may have
25210 files named
25211 <!--chtml if pinemode="os_windows"-->
25212 "DEADLETR",
25213 "DEADLETR2", and
25214 "DEADLETR3".
25215 <!--chtml else-->
25216 "dead.letter",
25217 "dead.letter2", and
25218 "dead.letter3" in your home directory.
25219 <!--chtml endif-->
25220 In this example, the most recently cancelled message will be in
25221 <!--chtml if pinemode="os_windows"-->
25222 "DEADLETR",
25223 <!--chtml else-->
25224 "dead.letter",
25225 <!--chtml endif-->
25226 and the third most recently cancelled message will be in
25227 <!--chtml if pinemode="os_windows"-->
25228 "DEADLETR3".
25229 <!--chtml else-->
25230 "dead.letter3".
25231 <!--chtml endif-->
25232 The fourth most recently cancelled message will no longer be saved.
25234 <P>
25235 If you set this option to zero, then NO record of canceled messages is
25236 maintained.
25237 <P>
25238 If the feature
25239 <A HREF="h_config_quell_dead_letter"><!--#echo var="FEAT_quell-dead-letter-on-cancel"--></A>
25240 is set, that overrides whatever you set for this option.
25241 If this option had existed at the time, then the Quell feature would not
25242 have been added, but it is still there for backwards compatibility.
25243 So, in order for this option to have the desired effect, make sure the
25244 Quell feature is turned off.
25246 <P>
25247 <UL>
25248 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25249 </UL><P>
25250 <End of help on this topic>
25251 </BODY>
25252 </HTML>
25253 ====== h_config_maxremstream =====
25254 <HTML>
25255 <HEAD>
25256 <TITLE>OPTION: <!--#echo var="VAR_max-remote-connections"--></TITLE>
25257 </HEAD>
25258 <BODY>
25259 <H1>OPTION: <!--#echo var="VAR_max-remote-connections"--></H1>
25261 This option affects low-level behavior of Alpine.
25262 The default value for this option is <EM>3</EM>.
25263 If your INBOX is accessed using the IMAP protocol
25264 from an IMAP server, that connection is kept open throughout the
25265 duration of your Alpine session, independent of the value of this option.
25266 The same is true of any
25267 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
25268 you have defined.
25269 This option controls Alpine's behavior when connecting to remote IMAP folders
25270 other than your INBOX or your <!--#echo var="VAR_stay-open-folders"-->.
25271 It specifies the maximum number of remote IMAP connections (other than
25272 those mentioned above) that Alpine will use for accessing the rest of your
25273 folders.
25274 If you set this option to zero, you will turn off most remote connection
25275 re-use.
25276 It's difficult to understand exactly what this option does, and it is usually
25277 fine to leave it set to its default value.
25278 It is probably more likely that you will be interested in setting the
25279 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A> option
25280 instead of changing the value of this option.
25281 A slightly longer explanation of what is going on with this option
25282 is given in the next paragraphs.
25284 <P>
25285 There are some time costs involved in opening and closing remote IMAP
25286 folders, the main costs being the time you have to wait for the connection
25287 to the server and the time for the folder to open.
25288 Opening a folder may involve not only the time the server takes to do its
25289 processing but time that Alpine uses to do filtering.
25290 These times can vary widely.
25291 They depend on how loaded the server is, how large
25292 the folder being opened is, and how you set up filtering, among other things.
25293 Once Alpine has opened a connection to a particular folder, it will attempt
25294 to keep that connection open in case you use it again.
25295 In order to do this,
25296 Alpine will attempt to use the <!--#echo var="VAR_max-remote-connections"--> (the value of
25297 this option) IMAP connections you have alloted for this purpose.
25298 <P>
25299 For example, suppose the value of this option is set to "2".
25300 If your INBOX is accessed on a remote server using the IMAP protocol, that
25301 doesn't count as one of the remote connections but it is always kept open.
25302 If you then open another IMAP folder, that would be your first
25303 remote connection counted as one of the <!--#echo var="VAR_max-remote-connections"--> connections.
25304 If you open a third folder the second will be left open, in case you
25305 return to it.
25306 You won't be able to tell it has been left open.
25307 It will appear to be closed when you leave the folder but the connection
25308 will remain in the background.
25309 Now suppose you go back to the second folder (the first folder after the
25310 INBOX).
25311 A connection to that folder is still open so you won't have to wait
25312 for the startup time to open it.
25313 Meanwhile, the connection to the third folder will be left behind.
25314 Now, if you open a fourth folder, you will bump into the
25315 <!--#echo var="VAR_max-remote-connections"--> limit, because this will be the third folder other
25316 than INBOX and you have the option set to "2".
25317 The connection that is being used for
25318 the third folder will be re-used for this new fourth folder.
25319 If you go back to the third folder after this, it is no longer already
25320 connected when you get there.
25321 You'll still save some time since Alpine will re-use the connection to the
25322 fourth folder and you have already logged in on that connection,
25323 but the folder will have to be re-opened from scratch.
25324 <P>
25325 If a folder is large and the startup cost is dominated by the time it takes
25326 to open that folder or to run filters on it, then it will pay to make the
25327 value of this option large enough to keep it open.
25328 On the other hand, if you only revisit a handful of folders or if
25329 the folders are small, then it might
25330 make more sense to keep this number small so that the reconnect
25331 time (the time to start up a new connection and authenticate)
25332 is eliminated instead.
25333 <P>
25334 You may also need to consider the impact on the server.
25335 On the surface, a larger number here may cause a larger impact on the
25336 server, since you will have more connections open to the server.
25337 On the other hand, not only will <EM>you</EM> be avoiding the startup costs
25338 associated with reopening a folder, but the <EM>server</EM> will be
25339 avoiding those costs as well.
25340 <P>
25341 When twenty five minutes pass without any active use of an IMAP connection
25342 being saved for possible re-use, that connection will be shut down,
25344 <P>
25345 <UL>
25346 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25347 </UL><P>
25348 <End of help on this topic>
25349 </BODY>
25350 </HTML>
25351 ====== h_config_permlocked =====
25352 <HTML>
25353 <HEAD>
25354 <TITLE>OPTION: <!--#echo var="VAR_stay-open-folders"--></TITLE>
25355 </HEAD>
25356 <BODY>
25357 <H1>OPTION: <!--#echo var="VAR_stay-open-folders"--></H1>
25359 This option affects low-level behavior of Alpine.
25360 There is no default value for this option.
25361 It is related to the options
25362 <A HREF="h_config_preopen_stayopens">"<!--#echo var="FEAT_preopen-stayopen-folders"-->"</A>,
25363 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>,
25364 and <A HREF="h_config_expunge_stayopens">"<!--#echo var="FEAT_offer-expunge-of-stayopen-folders"-->"</A>.
25366 <P>
25367 Note: changes made to this list take effect the next time you open a
25368 folder in the list.
25370 <P>
25371 This is a list of folders that will be permanently kept open once they
25372 are first opened.
25373 The names in this list may be either the nickname of an Incoming folder
25374 or the full technical specification of a folder.
25375 The folders in this list need not be remote IMAP folders, they could usefully
25376 be local folders, as well.
25377 If a folder in the list is a newsgroup or is not accessed either locally
25378 or via IMAP, then the entry will be ignored.
25379 For example, folders accessed via NNTP or POP3 will not be kept open, since
25380 the way that new mail is found with those protocols involves closing and
25381 reopening the connection.
25382 <P>
25383 Once a Stay Open folder has been opened, new-mail checking will continue
25384 to happen on that folder for the rest of the Alpine session.
25385 Your INBOX is always implicitly included in this Stay-Open list and doesn't
25386 need to be added explicitly.
25387 <P>
25388 Another difference that you may notice between a Stay Open folder and a
25389 non-Stay Open folder is which message is selected as the current message
25390 when you enter the folder index.
25391 Normally, the starting position for an incoming folder (which most Stay Open
25392 folders will likely be) is controlled by the
25393 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
25394 However, if a folder is a Stay Open folder, when you re-enter the folder
25395 after the first time the current message will be the same as it was when
25396 you left the folder.
25397 An exception is made if you use the TAB command to get to the folder.
25398 In that case, the message number will be incremented by one from what it
25399 was when you left the folder.
25400 <P>
25401 The above special behavior is thought to be useful.
25402 However, it is special and different from what you might at first expect.
25403 The feature
25404 <A HREF="h_config_use_reg_start_for_stayopen"><!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></A>
25405 may be used to turn off this special treatment.
25406 <P>
25407 If the message that was current when you left the folder no longer exists,
25408 then the regular startup rule will be used instead.
25410 <P>
25411 <UL>
25412 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25413 </UL><P>
25414 <End of help on this topic>
25415 </BODY>
25416 </HTML>
25417 ====== h_config_viewer_overlap =====
25418 <html>
25419 <header>
25420 <title>OPTION: <!--#echo var="VAR_viewer-overlap"--></title>
25421 </header>
25422 <body>
25423 <h1>OPTION: <!--#echo var="VAR_viewer-overlap"--></h1>
25425 This option specifies an aspect of Alpine's Message Viewing screen. When
25426 the space bar is used to page forward in a message, the number of lines
25427 specified by the "<!--#echo var="VAR_viewer-overlap"-->" variable will be repeated from the
25428 bottom of the screen. That is, if this was set to two lines, then the
25429 bottom two lines of the screen would be repeated on the top of the next
25430 screen. The normal default value is "2".<p>
25431 <UL>
25432 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25433 </UL><P>
25434 <End of help on this topic>
25435 </body>
25436 </html>
25437 ====== h_config_scroll_margin =====
25438 <HTML>
25439 <HEAD>
25440 <TITLE>OPTION: <!--#echo var="VAR_scroll-margin"--></TITLE>
25441 </HEAD>
25442 <BODY>
25443 <H1>OPTION: <!--#echo var="VAR_scroll-margin"--></H1>
25445 This option controls when Alpine's line-by-line scrolling occurs.
25446 Typically, when a selected item is at the top or bottom screen edge
25447 and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are struck, the
25448 displayed items are scrolled down or up by a single line.
25450 <P>
25451 This option allows you to tell Alpine the number of lines from the top and
25452 bottom screen edge that line-by-line paging should occcur. For example,
25453 setting this value to one (1) will cause Alpine to scroll the display
25454 vertically when you move to select an item on the display's top or
25455 bottom edge.
25457 <P>
25458 By default, this variable is zero, indicating that scrolling happens
25459 when you move up or down to select an item immediately off the display's
25460 top or bottom edge.
25462 <P>
25463 <UL>
25464 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25465 </UL><P>
25466 <End of help on this topic>
25467 </BODY>
25468 </HTML>
25469 ====== h_config_wordseps =====
25470 <HTML>
25471 <HEAD>
25472 <TITLE>OPTION: <!--#echo var="VAR_composer-word-separators"--></TITLE>
25473 </HEAD>
25474 <BODY>
25475 <H1>OPTION: <!--#echo var="VAR_composer-word-separators"--></H1>
25477 This option affects how a "word" is defined in the composer.
25478 The definition of a word is used when using the Forward Word and Backward
25479 Word commands in the composer, as well as when using the spell checker.
25480 Whitespace is always considered a word separator.
25481 Punctuation (like question marks, periods, commas, and so on) is always
25482 a word separator if it comes at the end of a word.
25483 By default, a punctuation character that is in the middle of a word does
25484 not break up that word as long as the character before and the character
25485 after it are both alphanumeric.
25486 If you add a character to this option it will be considered a
25487 word separator even when it occurs in the middle of an alphanumeric word.
25488 For example, if you want to skip through each part of an address instead
25489 of skipping the whole address at once you might want to include "@"
25490 and "." in this list.
25491 If you want the word-skipper to stop on each part of a UNIX filename you
25492 could add "/" to the list.
25493 The equal sign and dash are other possibilities you might find helpful.
25494 <P>
25495 <UL>
25496 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25497 </UL><P>
25498 <End of help on this topic>
25499 </BODY>
25500 </HTML>
25501 ====== h_config_reply_indent_string =====
25502 <HTML>
25503 <HEAD>
25504 <TITLE>OPTION: <!--#echo var="VAR_reply-indent-string"--></TITLE>
25505 </HEAD>
25506 <BODY>
25507 <H1>OPTION: <!--#echo var="VAR_reply-indent-string"--></H1>
25509 This option specifies an aspect of Alpine's Reply command.
25510 When a message is replied to and the text of the message is included, the
25511 included text usually has the string "> " prepended
25512 to each line indicating it is quoted text.
25513 (In case you haven't seen this before, "string" is a technical term
25514 that means chunk of text.)
25516 <P>
25517 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
25518 in 1999 and its wide-spread adoption since then, you will usually be better off if you
25519 use one of the standard values,
25520 "> " or ">", for this option.
25522 <P>
25523 This option specifies a different value for that string.
25524 If you wish to use a string that begins or ends with a space,
25525 enclose the string in double quotes.
25527 <P>
25528 Besides simple text, the prepended string can be based
25529 on the message being replied to.
25530 The following tokens are substituted for the message's corresponding value:
25532 <DL>
25533 <DT>_FROM_</DT>
25534 <DD>This token gets replaced with the message sender's "username".
25535 If the name is longer than six characters, only the first six characters are
25536 used.
25537 </DD>
25539 <DT>_NICK_</DT>
25540 <DD>This token gets replaced with the nickname of the message sender's
25541 address as found in your addressbook.
25542 If no addressbook entry is found,
25543 Alpine replaces the characters "_NICK_" with nothing.
25544 If the nickname is longer than six characters, only the first six characters are
25545 used.
25546 </DD>
25548 <DT>_INIT_</DT>
25549 <DD>This token gets replaced with the initials of the sender of the message.
25550 </DD>
25552 </DL>
25554 NOTE: When the
25555 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
25556 feature is enabled, you are given the opportunity to edit the string, whether
25557 it is the default or one automatically generated using the above tokens.
25558 <P>
25559 If you change your <!--#echo var="VAR_reply-indent-string"-->
25560 so that it is not equal to the default value of "> ", then
25561 quoted text will not be flowed
25562 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
25563 when you reply.
25564 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
25565 set to the default value.
25566 <P>
25567 <UL>
25568 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25569 </UL><P>
25570 <End of help on this topic>
25571 </BODY>
25572 </HTML>
25573 ====== h_config_quote_replace_string =====
25574 <HTML>
25575 <HEAD>
25576 <TITLE>OPTION: <!--#echo var="VAR_quote-replace-string"--></TITLE>
25577 </HEAD>
25578 <BODY>
25579 <H1>OPTION: <!--#echo var="VAR_quote-replace-string"--></H1>
25581 This option specifies what string to use as a quote when <b>viewing</b> a
25582 message. The standard way of quoting messages when replying is the string
25583 "> " (quote space).
25584 With this variable set, viewing a message will
25585 replace occurrences of
25586 "> " and ">" with the replacement string.
25587 This setting works best when
25588 <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
25589 or the equivalent setting in your correspondents' mail programs
25590 is set to the default
25591 "> ", but it will also work fine with the
25592 <!--#echo var="VAR_reply-indent-string"--> set to ">".
25593 <P>
25594 By default, this setting will only work on messages that are flowed, which is
25595 the default way of sending messages for many mail clients including
25596 Alpine. Enable the feature
25597 <A HREF="h_config_quote_replace_noflow"><!--#echo var="FEAT_quote-replace-nonflowed"--></A>
25598 to also have quote-replacement performed on non-flowed messages.
25599 <P>
25601 Setting this option will replace ">" and
25602 "> " with the new setting. This string may include trailing
25603 spaces. To preserve those spaces enclose the full string in double quotes.
25604 <P>
25605 No padding to separate the text of the message from the quote string is
25606 added. This means that if you do not add trailing spaces to the value of
25607 this variable, text will be displayed right next to the quote string,
25608 which may be undesirable. This can be avoided by adding a new string
25609 separated by a space from your selection of quote string replacement. This
25610 last string will be used for padding. For example, setting this variable to
25611 <br>">" " " has the effect of setting
25612 ">" as the <!--#echo var="VAR_quote-replace-string"-->, with the text padded by
25613 a space from the last quote string to make it more readable.
25614 <P>
25615 One possible setting for this variable could be
25616 " " (four spaces wrapped in quotes), which
25617 would have the effect of indenting each level of quoting four spaces and
25618 removing the ">"'s. Different levels of quoting could be made
25619 more discernible by setting colors for quoted text.
25620 <P>
25621 Replying to or forwarding the viewed message will preserve the original
25622 formatting of the message, so quote-replacement will not be performed on
25623 messages that are being composed.
25624 <P>
25625 <UL>
25626 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25627 </UL><P>
25628 <End of help on this topic>
25629 </BODY>
25630 </HTML>
25631 ====== h_config_empty_hdr_msg =====
25632 <HTML>
25633 <HEAD>
25634 <TITLE>OPTION: <!--#echo var="VAR_empty-header-message"--></TITLE>
25635 </HEAD>
25636 <BODY>
25637 <H1>OPTION: <!--#echo var="VAR_empty-header-message"--></H1>
25639 When sending, if both the To and Cc fields are empty and you
25640 are sending the message to a Bcc,
25641 Alpine will put a special address in the To line. The default value is:
25643 <P>
25644 <CENTER><SAMP>undisclosed-recipients: ;</SAMP></CENTER>
25646 <P>
25647 The reason for this is to avoid embarrassment caused by some Internet
25648 mail transfer software that interprets a "missing"
25649 <SAMP>To:</SAMP> header as an error and replaces it with an
25650 <SAMP>Apparently-to:</SAMP> header that may contain the addresses you
25651 entered on the <SAMP>Bcc:</SAMP> line, defeating the purpose of the
25652 Bcc. You may change the part of this message that comes before the
25653 ": ;" by setting the "<!--#echo var="VAR_empty-header-message"-->"
25654 variable to something else.
25656 <P>
25657 The normal default is "undisclosed-recipients".
25659 <P>
25660 <UL>
25661 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25662 </UL><P>
25663 <End of help on this topic>
25664 </BODY>
25665 </HTML>
25666 ====== h_config_status_msg_delay =====
25667 <HTML>
25668 <HEAD>
25669 <TITLE>OPTION: <!--#echo var="VAR_status-message-delay"--></TITLE>
25670 </HEAD>
25671 <BODY>
25672 <H1>OPTION: <!--#echo var="VAR_status-message-delay"--></H1>
25674 This option has evolved over time, causing the possible values to be
25675 counter-intuitive.
25676 Read carefully before you set this option.
25677 First we explain what the option does, then there is a longer discussion
25678 following that.
25679 <P>
25680 If this is set to zero, the default value, it has <EM>no</EM> effect.
25681 Positive and negative values serve two similar, but different purposes.
25682 <P>
25683 If it is set to a positive number, it causes the cursor to move to the
25684 status line whenever a status message is printed and pause there for this
25685 many seconds.
25686 It will probably only be useful if the
25687 <A HREF="h_config_show_cursor">"<!--#echo var="FEAT_show-cursor"-->"</A> feature is
25688 also turned on.
25689 Setting this option to a positive number can only be used to
25690 <EM>increase</EM> the status message delay.
25691 This may be useful for Braille displays, or other non-traditional displays.
25692 <P>
25693 If it is set to a negative number the interpretation is a bit complicated.
25694 Negative numbers are used to <EM>decrease</EM> the amount of delay Alpine uses to
25695 allow you to read important status messages.
25696 Of course, this may cause you to miss some important messages.
25697 If you see a message flash by but miss what it says you can use the
25698 Journal command from the MAIN MENU to read it.
25699 If you set this option to a negative value, the delay will be
25700 no more than one second less than the absolute value
25701 of the value you set.
25702 So if you set it to -1, the delay will be no more than zero seconds, no
25703 delay at all.
25704 If you set it to -2, the delay will be no more than 1 second.
25705 And so on, -3 is 2 seconds, -4 is 3 seconds, ...
25706 If the delay that Alpine would have used by default is less than this delay,
25707 then the smaller delay set by Alpine will be used.
25708 Setting this option to a negative value can only reduce the amount of
25709 delay, never increase it.
25710 <P>
25711 Here is a more detailed explanation.
25712 Status messages are the messages that show up spontaneously in the
25713 status message line, usually the third line from the bottom of the screen.
25714 By default, Alpine assigns each status message it produces a minimum
25715 display time.
25716 Some status messages have a minimum display time of zero.
25717 You can see an example of such a message by paging up in this help text
25718 until you reach the top of the screen.
25719 If you try to page past the top you will see the message
25720 <P>
25721 <CENTER><SAMP>[Already at start of help text]</SAMP></CENTER>
25722 <P>
25723 in the status line.
25724 If there is another more important use of the status message line this message
25725 might be replaced quickly, or it even might not be shown at all.
25726 However, if there is no reason to get rid of the message, it might stay
25727 there for several seconds while you read the help.
25728 An example where it is replaced immediately happens when you page up in
25729 the help text past the top of the screen, but then type the "WhereIs"
25730 command right after paging up.
25731 The message will disappear immediately without causing a delay (unless you
25732 have set this option to a positive value) to allow you to type input for
25733 the "WhereIs" command.
25734 Since it isn't a very important message, Alpine has set its minimum display
25735 time to zero seconds.
25736 <P>
25737 Other messages have minimum display times of three or more seconds.
25738 These are usually error messages that Alpine thinks you ought to see.
25739 For example, it might be a message about a failed Save or a failed folder open.
25740 It is often the case that this minimum display time won't delay you in
25741 any way because the status message line is not needed for another reason.
25742 However, there are times when Alpine has to delay what it is doing in
25743 order to display a status message for the minimum display time.
25744 This happens when a message is being displayed and Alpine wants to ask
25745 for input from the keyboard.
25746 For example, when you Save a message you use the status message line.
25747 You get a prompt there asking for the name of the folder to save to.
25748 If there is a status message being displayed that has not
25749 yet displayed for its minimum
25750 time Alpine will display that status message surrounded with the characters
25751 > and < to show you that it is delaying.
25752 That might happen, for example, if you tried to save to a folder that
25753 caused an error, then followed that immediately with another Save command.
25754 You might find yourself waiting for a status message like
25755 <P>
25756 <CENTER><SAMP>[>Can't get write access to mailbox, access is readonly<]</SAMP></CENTER>
25757 <P>
25758 to finish displaying for three seconds.
25759 If that is something you find happening to you frequently, you may use
25760 negative values of this option to decrease or eliminate that delay, at
25761 the risk of missing the message.
25762 <P>
25763 <UL>
25764 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25765 </UL><P>
25766 <End of help on this topic>
25767 </BODY>
25768 </HTML>
25769 ====== h_config_active_msg_interval =====
25770 <HTML>
25771 <HEAD>
25772 <TITLE>OPTION: <!--#echo var="VAR_busy-cue-rate"--></TITLE>
25773 </HEAD>
25774 <BODY>
25775 <H1>OPTION: <!--#echo var="VAR_busy-cue-rate"--></H1>
25777 When Alpine is delayed for some reason it usually shows that
25778 something is happening with a small animated display in the status
25779 message line near the bottom of the screen.
25780 This option sets how frequently the characters (for example, a spinning bar)
25781 in the active status message lines are updated.
25782 At most, it can be set to be udpated 20 times per second.
25784 <P>
25785 Setting this value to zero will prevent display of the animations
25786 altogether.
25788 <P>
25789 The option <A HREF="h_config_use_boring_spinner"><!--#echo var="FEAT_busy-cue-spinner-only"--></A>
25790 can be used to remove the randomness from this animated display.
25792 <P>
25793 <UL>
25794 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25795 </UL><P>
25796 <End of help on this topic>
25797 </BODY>
25798 </HTML>
25799 ====== h_config_mailchecknoncurr =====
25800 <HTML>
25801 <HEADER>
25802 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></TITLE>
25803 </HEADER>
25804 <BODY>
25805 <H1>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></H1>
25807 This option is closely related to the
25808 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
25809 option, as well as the
25810 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A> and
25811 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> options.
25812 If the "<!--#echo var="VAR_mail-check-interval"-->" option is set to zero, then automatic
25813 new-mail checking is disabled and this option will have no effect.
25814 <P>
25815 Normally this option is set to zero, which means that the value used will be
25816 the same as the value for the "<!--#echo var="VAR_mail-check-interval"-->".
25817 If you set this option to a value different from zero
25818 (usually larger than the value for "<!--#echo var="VAR_mail-check-interval"-->")
25819 then that is the check interval that will be used
25820 for folders that are not the currently open folder or the INBOX.
25821 You may not even have any folders that are noncurrent and not the INBOX.
25822 If you do, it is likely that they are due to
25823 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
25824 you have configured.
25825 This option also affects the rate of mail checking done on cached
25826 connections to folders you previously had open but are no longer actively
25827 using.
25828 You aren't expected to understand that last sentence, but if you are interested
25829 take a look at
25830 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>
25831 and the related options.
25832 <P>
25833 <UL>
25834 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25835 </UL><P>
25836 <End of help on this topic>
25837 </BODY>
25838 </HTML>
25839 ====== h_config_fifopath =====
25840 <HTML>
25841 <HEADER>
25842 <TITLE>OPTION: NewMail FIFO Path</TITLE>
25843 </HEADER>
25844 <BODY>
25845 <H1>OPTION: NewMail FIFO Path</H1>
25847 This option is only available in UNIX Alpine.
25848 However, there is a very similar feature built in to PC-Alpine.
25849 In PC-Alpine's Config menu at the top of the screen
25850 is an option called "New Mail Window".
25851 <P>
25852 You may have Alpine create a FIFO special file (also called a named pipe) where
25853 it will send a one-line message each time a new message is received in
25854 the current folder, the INBOX, or any open
25855 <A HREF="h_config_permlocked"><!--#echo var="VAR_stay-open-folders"--></A>.
25856 To protect against two different Alpines both writing to the same FIFO, Alpine
25857 will only create the FIFO and write to it if it doesn't already exist.
25858 <P>
25859 A possible way to use this option would be to have a separate window
25860 on your screen running the command
25861 <P>
25862 <CENTER><SAMP>cat filename</SAMP></CENTER>
25863 <P>
25864 where "filename" is the name of the file given for this option.
25865 Because the file won't exist until after you start Alpine, you must <EM>first</EM>
25866 start Alpine and <EM>then</EM> run the "cat" command.
25867 You may be tempted to use "tail -f filename" to view the new
25868 mail log.
25869 However, the common implementations of the tail command will not do what you
25870 are hoping.
25871 <P>
25872 The width of the messages produced for the FIFO may be altered with the
25873 <A HREF="h_config_newmailwidth"><!--#echo var="VAR_newmail-window-width"--></A> option.
25874 <P>
25875 On some systems, fifos may only be created in a local filesystem.
25876 In other words, they may not be in NFS filesystems.
25877 This requirement is not universal.
25878 If the system you are using supports it, it should work.
25879 (It is often the case that your home directory is in an NFS filesystem.
25880 If that is the case, you might try using a file in the "/tmp"
25881 filesystem, which is usually a local filesytem.)
25882 Even when it is possible to use an NFS-mounted filesystem as a place to name
25883 the fifo (for example, your home directory), it will still be the case that
25884 the reader (probably the "cat" command) and the
25885 writer (Alpine) of the fifo must be running on the same system.
25886 <P>
25887 <UL>
25888 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25889 </UL><P>
25890 <End of help on this topic>
25891 </BODY>
25892 </HTML>
25893 ====== h_config_newmailwidth =====
25894 <HTML>
25895 <HEADER>
25896 <TITLE>OPTION: <!--#echo var="VAR_newmail-window-width"--></TITLE>
25897 </HEADER>
25898 <BODY>
25899 <H1>OPTION: <!--#echo var="VAR_newmail-window-width"--></H1>
25901 For UNIX Alpine, this option is only useful if you have turned on the
25902 <A HREF="h_config_fifopath">NewMail FIFO Path</A> option.
25903 That option causes new mail messages to be sent to a fifo file.
25904 Those messages will be 80 characters wide by default.
25905 You can change the width of those messages by changing this option.
25906 For example, if you are reading those messages in another window you might
25907 want to set this width to the width of that other window.
25908 <P>
25909 If you are using PC-Alpine, it has an option in the Config menu to turn
25910 on the "New Mail Window".
25911 This present option also controls the width of that window.
25912 <P>
25913 <UL>
25914 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25915 </UL><P>
25916 <End of help on this topic>
25917 </BODY>
25918 </HTML>
25919 ====== h_config_mailcheck =====
25920 <HTML>
25921 <HEADER>
25922 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval"--></TITLE>
25923 </HEADER>
25924 <BODY>
25925 <H1>OPTION: <!--#echo var="VAR_mail-check-interval"--></H1>
25927 This option specifies, in seconds,
25928 how often Alpine will check for new mail.
25929 If set to zero, new-mail checking is disabled.
25930 (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
25931 current message is the last message of the folder.)
25932 There is a minimum value for this option, normally 15 seconds.
25933 The default value is normally 150 seconds.
25934 The higher you set this option, the easier it is on the server.
25935 <P>
25936 There are some situations where automatic new-mail checking does not work.
25937 See the discussion about new-mail checking in
25938 <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
25939 <P>
25940 The new-mail checking will not happen exactly at the frequency that you specify.
25941 For example, Alpine may elect to defer a non-INBOX mail check if you
25942 are busy typing.
25943 Or, it may check more frequently than you have specified if that is
25944 thought to be necessary to keep the server from closing the connection
25945 to the folder due to inactivity.
25946 If Alpine checks for new mail as a side effect of another command, it will reset
25947 the timer, so that new-mail checking may seem to happen irregularly instead of
25948 every X seconds like clockwork.
25949 <P>
25950 If you are anxious to know about new mail as soon as possible, set the check
25951 interval low, and you'll know about the new mail by approximately
25952 that amount of time after it arrives.
25953 If you aren't so worried about knowing right away, set this option to a
25954 higher value.
25955 That will save the server some processing time and may save you some of
25956 the time you spend waiting for new-mail checks to happen if you are
25957 dealing with a slow server or slow network connection.
25958 <P>
25959 If you suspect that new-mail checking is causing slow downs for you,
25960 you may want to look into the options
25961 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>,
25962 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> and
25963 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A>,
25964 which refine when mail checking is done.
25965 <P>
25966 If the mailbox being checked uses a <A HREF="h_maildrop">Mail Drop</A> then
25967 there is a minimum time
25968 (<A HREF="h_config_maildropcheck">"<!--#echo var="VAR_maildrop-check-minimum"-->"</A>)
25969 between new-mail checks.
25970 Because of this minimum you may notice that new mail does not
25971 appear promptly when you expect it.
25972 The reason for this is to protect the server from over-zealous opening and
25973 closing of the Mail Drop folder, since that is a costly operation.
25974 <P>
25975 <UL>
25976 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25977 </UL><P>
25978 <End of help on this topic>
25979 </BODY>
25980 </HTML>
25981 ====== h_config_quell_checks_comp =====
25982 <HTML>
25983 <HEAD>
25984 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></TITLE>
25985 </HEAD>
25986 <BODY>
25987 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></H1>
25989 This option is closely related to the
25990 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
25991 option, the
25992 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
25993 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A>.
25994 <P>
25995 If this option is set, then the normal new-mail checking that happens
25996 while you are composing will not happen for folders other than your
25997 INBOX (which depends on the setting
25998 of "<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->").
25999 <P>
26000 You might want to set this option if you are experiencing delays while
26001 composing that you think might be related to the speed of the new-mail
26002 checks.
26003 <P>
26004 Even with this option turned on, an occasional new-mail check may be done
26005 in order to keep the server from killing the connection to the folder.
26006 For example, IMAP servers may remove a connection to a folder if there
26007 has been no activity on the connection for 30 minutes or more.
26008 Instead of letting that happen, Alpine will check for new mail before the
26009 30 minutes is up even though you have turned on this feature to quell
26010 those checks.
26011 <P>
26012 Besides new-mail checks, checkpoint operations on the folders
26013 will also be quelled when you set this option.
26014 The purpose of checkpointing is to write the changes to a folder out to
26015 disk periodically in order to avoid losing those changes when system or
26016 software problems occur.
26017 New-mail checking and checkpointing while you are not composing are not
26018 affected by this option.
26020 <P>
26021 <End of help on this topic>
26022 </BODY>
26023 </HTML>
26024 ====== h_config_quell_checks_comp_inbox =====
26025 <HTML>
26026 <HEAD>
26027 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></TITLE>
26028 </HEAD>
26029 <BODY>
26030 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></H1>
26032 This option is closely related to the
26033 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26034 option, the
26035 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
26036 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>.
26037 <P>
26038 If this option is set, then the normal new-mail checking that happens
26039 while you are composing will not happen for your INBOX.
26040 Checking of other folders is controlled in a similar way with the
26041 "<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->" option.
26042 <P>
26043 You might want to set this option if you are experiencing delays while
26044 composing that you think might be related to the speed of the new-mail
26045 checks.
26046 <P>
26047 Even with this option turned on, an occasional new-mail check may be done
26048 in order to keep the server from killing the connection to the folder.
26049 For example, IMAP servers may remove a connection to a folder if there
26050 has been no activity on the connection for 30 minutes or more.
26051 Instead of letting that happen, Alpine will check for new mail before the
26052 30 minutes is up even though you have turned on this feature to quell
26053 those checks.
26054 <P>
26055 Besides new-mail checks, checkpoint operations on the INBOX
26056 will also be quelled when you set this option.
26057 The purpose of checkpointing is to write the changes to a folder out to
26058 disk periodically in order to avoid losing those changes when system or
26059 software problems occur.
26060 New-mail checking and checkpointing while you are not composing are not
26061 affected by this option.
26062 <P>
26063 <End of help on this topic>
26064 </BODY>
26065 </HTML>
26066 ====== h_config_maildropcheck =====
26067 <HTML>
26068 <HEADER>
26069 <TITLE>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></TITLE>
26070 </HEADER>
26071 <BODY>
26072 <H1>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></H1>
26074 New-mail checking for a
26075 <A HREF="h_maildrop">Mail Drop</A> is a little different from new
26076 mail checking for a regular folder.
26077 One of the differences is that the connection to the Mail Drop is not
26078 kept open and so the cost of checking
26079 (delay for you and additional load for the server) may be significant.
26080 Because of this additional cost we set a minimum time that
26081 must pass between checks.
26082 This minimum only applies to the automatic checking done by Alpine.
26083 If you force a check by typing ^L (Ctrl-L) or by typing the Next command when you are
26084 at the end of a folder index, then the check is done right away.
26085 <P>
26086 This option specifies, in seconds, the <EM>minimum</EM> time between Mail Drop
26087 new-mail checks.
26088 You may want to set this minimum high in order to avoid experiencing some
26089 of the delays associated with the checks.
26090 Note that the time between checks is still controlled by the regular
26091 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option.
26092 When Alpine is about to do an automatic check for new mail (because
26093 the <!--#echo var="VAR_mail-check-interval"--> has expired) then if the time since the last
26094 new-mail check
26095 of any open Mail Drops has been greater than the <!--#echo var="VAR_maildrop-check-minimum"-->,
26096 the Mail Drop is checked for new mail as well.
26097 Therefore, it is only useful to set this option to a value that is higher
26098 than the <!--#echo var="VAR_mail-check-interval"-->.
26099 <P>
26100 If this option is set to zero, automatic Mail Drop new-mail
26101 checking is disabled.
26102 There is a minimum value, normally 60 seconds.
26103 The default value is normally 60 seconds as well.
26104 This applies to the INBOX and to the currently open folder if that is
26105 different from the INBOX.
26107 <P>
26108 <UL>
26109 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26110 </UL><P>
26111 <End of help on this topic>
26112 </BODY>
26113 </HTML>
26114 ====== h_config_nntprange =====
26115 <HTML>
26116 <HEADER>
26117 <TITLE>OPTION: <!--#echo var="VAR_nntp-range"--></TITLE>
26118 </HEADER>
26119 <BODY>
26120 <H1>OPTION: <!--#echo var="VAR_nntp-range"--></H1>
26122 This option applies only to newsgroups accessed using the NNTP protocol.
26123 It does not, for example,
26124 apply to newsgroups accessed using an IMAP-to-NNTP proxy.
26126 <P>
26127 When you open a connection to a News server using the NNTP protocol, you
26128 normally have access to all of the articles in each newsgroup.
26129 If a server keeps a large backlog of messages it may speed performance
26130 some to restrict attention to only the newer messages in a group.
26131 This option allows you to set how many article numbers should be checked
26132 when opening a newsgroup.
26133 You can think of "<!--#echo var="VAR_nntp-range"-->" as specifying the maximum number
26134 of messages you ever want to see.
26135 For example, if you only ever wanted to look at the last 500 messages in each
26136 newsgroup you could set this option to 500.
26137 In actuality, it isn't quite that.
26138 Instead, for performance reasons, it specifies the range of article
26139 numbers to be checked, beginning
26140 with the highest numbered article and going backwards from there.
26141 If there are messages that have been canceled or deleted
26142 their article numbers are still counted as part of the range.
26143 <P>
26144 So, more precisely, setting the "<!--#echo var="VAR_nntp-range"-->" will cause article
26145 numbers
26146 <P><CENTER>last_article_number - <!--#echo var="VAR_nntp-range"--> + 1 through last_article_number</CENTER>
26147 <P>
26148 to be considered when reading a newsgroup.
26149 The number of messages that show up in your index will be less than or equal
26150 to the value of "<!--#echo var="VAR_nntp-range"-->".
26152 <P>
26153 The purpose of this option is simply to speed up access when reading news.
26154 The speedup comes because Alpine can ignore all but the last <!--#echo var="VAR_nntp-range"--> article
26155 numbers, and can avoid downloading any information about the ignored articles.
26156 There is a cost you pay for this speedup.
26157 That cost is that there is no way for you to see those ignored articles.
26158 The articles that come before the range you specify are invisible to you and
26159 to Alpine, as if they did not exist at all.
26160 There is no way to see those messages using, for example, an unexclude command
26161 or something similar.
26162 The only way to see those articles is to set this option high enough (or
26163 set it to zero) and then to reopen the newsgroup.
26165 <P>
26166 If this option is set to 0 (which is also the default),
26167 then the range is unlimited.
26168 This option applies globally to all NNTP servers and to all newsgroups
26169 on those servers.
26170 There is no way to set different values for different newsgroups or servers.
26172 <P>
26173 <UL>
26174 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26175 </UL><P>
26176 <End of help on this topic>
26177 </BODY>
26178 </HTML>
26179 ====== h_config_news_active =====
26180 <html>
26181 <header>
26182 <title>OPTION: <!--#echo var="VAR_news-active-file-path"--></title>
26183 </header>
26184 <body>
26185 <h1>OPTION: <!--#echo var="VAR_news-active-file-path"--></h1>
26187 This option tells Alpine where to look for the "active file" for newsgroups
26188 when accessing news locally, rather than via NNTP. The default path is
26189 usually "/usr/lib/news/active".<p>
26190 <UL>
26191 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26192 </UL><P>
26193 <End of help on this topic>
26194 </body>
26195 </html>
26196 ====== h_config_news_spool =====
26197 <html>
26198 <header>
26199 <title>OPTION: <!--#echo var="VAR_news-spool-directory"--></title>
26200 </header>
26201 <body>
26202 <h1>OPTION: <!--#echo var="VAR_news-spool-directory"--></h1>
26204 This option tells Alpine where to look for the "news spool" for newsgroups
26205 when accessing news locally, rather than via NNTP. The default path is
26206 usually "/var/spool/news".<p>
26207 <UL>
26208 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26209 </UL><P>
26210 <End of help on this topic>
26211 </body>
26212 </html>
26213 ====== h_config_image_viewer =====
26214 <html>
26215 <header>
26216 <title>OPTION: <!--#echo var="VAR_image-viewer"--></title>
26217 </header>
26218 <body>
26219 <h1>OPTION: <!--#echo var="VAR_image-viewer"--></h1>
26220 <body>
26221 This option specifies the program Alpine should call to view MIME
26222 attachments of type IMAGE (e.g. GIF or TIFF). The Image Viewer setting is
26223 no longer needed, but remains for backward compatibility. The more
26224 general method for associating external printing and viewing programs with
26225 specific MIME data types is to use the system's (or your personal)
26226 "mailcap" configuration file.<p>
26227 <UL>
26228 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26229 </UL><P>
26230 <End of help on this topic>
26231 </body>
26232 </html>
26233 ====== h_config_domain_name =====
26234 <HTML>
26235 <HEAD>
26236 <TITLE>OPTION: <!--#echo var="VAR_use-only-domain-name"--></TITLE>
26237 </HEAD>
26238 <BODY>
26239 <H1>OPTION: <!--#echo var="VAR_use-only-domain-name"--></H1>
26241 This option is used only if the
26242 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> option is <B>not</B>
26243 set. If set to "Yes" (and <!--#echo var="VAR_user-domain"--> is not used), then Alpine
26244 strips the hostname from your return ("From") address and when
26245 completing unqualified addresses that you enter into the composer.
26246 <P>
26247 If you set this, see also the <A HREF="h_config_quell_local_lookup">
26248 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
26251 <!--chtml if pinemode="os_windows"-->
26252 <P>This option is not applicable to PC-Alpine.
26253 <!--chtml else-->
26254 <P>
26255 <!--chtml endif-->
26256 <UL>
26257 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26258 </UL>
26259 <P>
26260 <End of help on this topic>
26261 </BODY>
26262 </HTML>
26263 ====== h_config_prune_date =====
26264 <HTML>
26265 <HEAD>
26266 <TITLE>OPTION: Last-Time-Prune Question</TITLE>
26267 </HEAD>
26268 <BODY>
26269 <H1>OPTION: Last-Time-Prune Question</H1>
26271 This value records the last time you were asked about deleting old
26272 sent-mail.
26273 It is set automatically by Alpine at the beginning of each month.
26274 In the past, if you wished to suppress the monthly sent-mail
26275 pruning feature, you could set this to a date in the future.
26276 This value is relative to the year 1900, so
26277 to set this, for example, to October 2005, use 105.10.
26278 <P>
26279 You can still do that if you wish, or you can use the
26280 <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option, which is probably
26281 a little more convenient to use.
26282 <P>
26283 <UL>
26284 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26285 </UL><P>
26286 <End of help on this topic>
26287 </BODY>
26288 </HTML>
26289 ====== h_config_goto_default =====
26290 <HTML>
26291 <HEAD>
26292 <TITLE>OPTION: <!--#echo var="VAR_goto-default-rule"--></TITLE>
26293 </HEAD>
26294 <BODY>
26295 <H1>OPTION: <!--#echo var="VAR_goto-default-rule"--></H1>
26297 This value affects Alpine's behavior when you use the Goto command.
26298 Alpine's usual behavior has two parts. If your current folder is
26299 "Inbox", Alpine will offer the last open folder as the
26300 default. If the current folder is other than "Inbox",
26301 "Inbox" is offered as the default.
26303 <P>
26304 The available options include:
26306 <DL>
26308 <DT>folder-in-first-collection</DT>
26310 <DD> Alpine will offer the most recently visited folder in the default
26311 collection found in the "Collection List" screen as the default.
26312 </DD>
26314 <DT> inbox-or-folder-in-first-collection</DT>
26316 <DD> If the current folder is "Inbox",
26317 Alpine will offer the most recently visited folder in the
26318 default collection found in the "Collection List" screen.
26319 If the current folder is other than "Inbox",
26320 "Inbox" is offered as the default.
26321 </DD>
26323 <DT> inbox-or-folder-in-recent-collection</DT>
26325 <DD> This is Alpine's default behavior.
26326 If the current folder is "Inbox",
26327 Alpine will offer the last open
26328 folder as the default.
26329 If the current folder is other than "Inbox",
26330 "Inbox" is offered as the default.
26331 </DD>
26333 <DT> first-collection-with-inbox-default</DT>
26335 <DD> Instead of offering the most recently visited folder in the default
26336 collection, the default collection is offered but with "Inbox" as
26337 the default folder.
26338 If you type in a folder name it will be in the default collection.
26339 If you simply accept the default, however, your "Inbox" will be opened.
26340 </DD>
26342 <DT> most-recent-folder</DT>
26344 <DD> The last accepted value simply causes the most recently opened
26345 folder to be offered as the default regardless of the currently opened
26346 folder.
26347 </DD>
26348 </DL>
26350 <P>
26351 NOTE: The default while a newsgroup is open remains the same; the last
26352 open newsgroup.
26354 <P>
26355 <UL>
26356 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26357 </UL><P>
26358 <End of help on this topic>
26359 </BODY>
26360 </HTML>
26361 ====== h_config_thread_lastreply_char =====
26362 <HTML>
26363 <HEAD>
26364 <TITLE>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></TITLE>
26365 </HEAD>
26366 <BODY>
26367 <H1>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></H1>
26369 The <!--#echo var="VAR_threading-lastreply-character"--> option has a small effect on the MESSAGE
26370 INDEX display when using a
26371 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
26372 of "show-thread-structure", "mutt-like", or
26373 "show-structure-in-from"; and sorting by Threads or OrderedSubject.
26374 The value of this option is a single character.
26375 This character is used instead of the vertical line character when there are
26376 no more replies directly to the parent of the current message.
26377 It can be used to "round-off" the bottom of the vertical line
26378 by setting it to a character such as a backslash (\) or
26379 a backquote (`).
26380 The default value of this option is the backslash character (\).
26381 This option may not be set to the Empty Value.
26382 In that case, the default will be used instead.
26384 <P>
26385 <UL>
26386 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26387 </UL><P>
26388 <End of help on this topic>
26389 </BODY>
26390 </HTML>
26391 ====== h_config_thread_indicator_char =====
26392 <HTML>
26393 <HEAD>
26394 <TITLE>OPTION: <!--#echo var="VAR_threading-indicator-character"--></TITLE>
26395 </HEAD>
26396 <BODY>
26397 <H1>OPTION: <!--#echo var="VAR_threading-indicator-character"--></H1>
26399 The <!--#echo var="VAR_threading-indicator-character"--> option has a small effect on the MESSAGE
26400 INDEX display when using a
26401 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26402 than "none" and sorting by Threads or OrderedSubject.
26403 The value of this option is a single character.
26404 This character is used to indicate that part of a thread (a conversation) is
26405 hidden beneath a message.
26406 The message could be expanded
26407 if desired with the "/" Collapse/Expand command.
26408 By default, the value of this option is the greater than sign (>).
26409 <P>
26410 If this option is set to the Empty Value, then the column (and the following
26411 blank column) will be deleted from the display.
26413 <P>
26414 This option is closely related to the
26415 <A HREF="h_config_thread_exp_char"><!--#echo var="VAR_threading-expanded-character"--></A> option.
26416 Another similar option that affects the thread display is the
26417 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26419 <P>
26420 <UL>
26421 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26422 </UL><P>
26423 <End of help on this topic>
26424 </BODY>
26425 </HTML>
26426 ====== h_config_thread_exp_char =====
26427 <HTML>
26428 <HEAD>
26429 <TITLE>OPTION: <!--#echo var="VAR_threading-expanded-character"--></TITLE>
26430 </HEAD>
26431 <BODY>
26432 <H1>OPTION: <!--#echo var="VAR_threading-expanded-character"--></H1>
26434 The <!--#echo var="VAR_threading-expanded-character"--> option has a small effect on the MESSAGE
26435 INDEX display when using a
26436 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26437 than "none".
26438 The value of this option is a single character.
26439 This character is used to indicate that part of a thread has been expanded
26440 and could be collapsed if desired with
26441 the "/" Collapse/Expand command.
26442 By default, the value of this option is a dot (.).
26443 <P>
26444 If this option is set to the Empty Value, then the column (and the following
26445 blank column) will be deleted from the display.
26447 <P>
26448 This option is closely related to the
26449 <A HREF="h_config_thread_indicator_char"><!--#echo var="VAR_threading-indicator-character"--></A> option.
26450 Another similar option that affects the thread display is the
26451 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26453 <P>
26454 <UL>
26455 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26456 </UL><P>
26457 <End of help on this topic>
26458 </BODY>
26459 </HTML>
26460 ====== h_config_thread_index_style =====
26461 <HTML>
26462 <HEAD>
26463 <TITLE>OPTION: <!--#echo var="VAR_threading-index-style"--></TITLE>
26464 </HEAD>
26465 <BODY>
26466 <H1>OPTION: <!--#echo var="VAR_threading-index-style"--></H1>
26468 When a folder is sorted by Threads or OrderedSubject,
26469 this option will affect the INDEX displays.
26470 <P>
26472 The possible values for this option are:
26474 <DL>
26475 <DT>regular-index-with-expanded-threads</DT>
26476 <DD>This is the default display.
26477 If the configuration option
26478 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26479 is set to something other than "none", then this setting
26480 will cause Alpine to start off with a MESSAGE INDEX with all of
26481 the threads expanded.
26482 That is, each message will have a line in the MESSAGE INDEX display.
26483 The Collapse/Expand command (/) may be used to manually collapse or
26484 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26485 <P>
26486 This setting affects the display when the folder is first threaded.
26487 The collapsed state may also be re-initialized by re-sorting the folder manually
26488 using the SortIndex command ($).
26489 After re-sorting the threads will once again all be expanded, even if you
26490 have previously collapsed some of them.
26491 <P>
26492 If "<!--#echo var="VAR_threading-display-style"-->" is set to "none", then
26493 the display will be the regular default Alpine MESSAGE INDEX, but sorted
26494 in a different order.
26495 </DD>
26497 <DT>regular-index-with-collapsed-threads</DT>
26498 <DD>If the configuration option
26499 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26500 is set to something other than "none", then this setting
26501 will cause Alpine to start out with all of the threads collapsed instead of
26502 starting out with all of the threads expanded.
26503 The Collapse/Expand command (/) may be used to manually collapse or
26504 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26505 <P>
26506 This setting affects the display when the folder is first threaded.
26507 The collapsed state may also be re-initialized by re-sorting the folder manually
26508 using the SortIndex command ($).
26509 After re-sorting the threads will once again all be collapsed, even if you
26510 have previously expanded some of them.
26511 </DD>
26513 <DT>separate-index-screen-always</DT>
26514 <DD>With this setting and the next, you will see an index of threads
26515 instead of an
26516 index of messages, provided you have sorted by Threads or OrderedSubject.
26517 <P>
26518 The THREAD INDEX contains a '*' in the first column if any message in the thread
26519 is marked Important.
26520 If not, it contains a '+' if any message in the thread is to you.
26521 The second column is blank. The third column contains a 'D' if all of the
26522 messages in the thread are deleted.
26523 Otherwise, it contains an 'N' if any of the messages in the thread are New.
26524 <P>
26525 When you view a particular thread from the THREAD INDEX you will be
26526 in the MESSAGE INDEX display
26527 but the index will only contain messages from the thread you are viewing.
26528 </DD>
26530 <DT>separate-index-screen-except-for-single-messages</DT>
26531 <DD>This is very similar to the option above.
26532 When you are in the THREAD INDEX, one of the available commands
26533 is "ViewThd".
26534 With the setting "separate-index-screen-always" (the option above)
26535 when you view a particular thread you will be in the
26536 MESSAGE INDEX display and the index will only contain messages from
26537 the thread you are viewing.
26538 If the thread you are viewing consists of a single message, the MESSAGE INDEX
26539 will be an index with only one message in it.
26540 If you use this "separate-index-screen-except-for-single-messages"
26541 setting instead, then that index that contains a single message
26542 will be skipped and you will go directly from the THREAD INDEX into the
26543 MESSAGE TEXT screen.
26544 </DD>
26546 </DL>
26548 <P>
26549 <UL>
26550 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26551 </UL><P>
26552 <End of help on this topic>
26553 </BODY>
26554 </HTML>
26555 ====== h_config_thread_disp_style =====
26556 <HTML>
26557 <HEAD>
26558 <TITLE>OPTION: <!--#echo var="VAR_threading-display-style"--></TITLE>
26559 </HEAD>
26560 <BODY>
26561 <H1>OPTION: <!--#echo var="VAR_threading-display-style"--></H1>
26563 When a folder is sorted by Threads or OrderedSubject,
26564 this option will affect the MESSAGE INDEX display.
26565 By default, Alpine will display the MESSAGE INDEX in the
26566 "show-thread-structure" style if a folder is sorted
26567 by Threads or OrderedSubject.
26568 <P>
26570 The possible values for this option are:
26572 <DL>
26573 <DT>none</DT>
26574 <DD>Regular index display.
26575 The same index line as would be displayed without threading is used.
26576 The only difference will be in the order of the messages.
26577 </DD>
26579 <DT>show-thread-structure</DT>
26580 <DD>Threaded Subjects will be indented and vertical bars and horizontal
26581 lines will be added to make it easier to see the relationships among
26582 the messages in a thread (a conversation).
26583 </DD>
26585 <DT>mutt-like</DT>
26586 <DD>This is the same as the option above except that the Subject
26587 is suppressed (is blank) if it matches the previous Subject in the thread.
26588 The name comes from the email client <A HREF="http://www.mutt.org/">Mutt</A>.
26589 Here is an example of what a mutt-like index might look like.
26590 In this example, the first column represents the message number, the
26591 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
26592 is set to "regular-index-with-expanded-threads", and the
26593 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A>
26594 is set to a backslash:
26595 <PRE>
26596 1 Some topic
26597 2 . Subject original message in thread
26598 3 |-> reply to 2
26599 4 . |-> another reply to 2
26600 5 . | \-> reply to 4
26601 6 . | \-> reply to 5
26602 7 | \-> reply to 6
26603 8 |-> another reply to 2
26604 9 . |->New subject another reply to 2 but with a New subject
26605 10 | |-> reply to 9
26606 11 | \-> another reply to 9
26607 12 | \-> reply to 11
26608 13 \-> final reply to 2
26609 14 Next topic
26610 </PRE>
26611 </DD>
26613 <DT>indent-subject-1</DT>
26614 <DD>Threaded Subjects will be indented one space per level of the conversation.
26615 The bars and lines that show up in the show-thread-structure display will
26616 not be there with this style.
26617 </DD>
26619 <DT>indent-subject-2</DT>
26620 <DD>Same as above but indent two spaces per level instead of one space.
26621 </DD>
26623 <DT>indent-from-1</DT>
26624 <DD>Similar to indent-subject-1, except that instead of indenting the
26625 Subject field one space the From field of a thread will be indented one
26626 space per level of the conversation.
26627 </DD>
26629 <DT>indent-from-2</DT>
26630 <DD>Same as above but indent two spaces per level instead of one space.
26631 </DD>
26633 <DT>show-structure-in-from</DT>
26634 <DD>The structure of the thread is illustrated with indenting, vertical bars,
26635 and horizontal lines just like with the show-thread-structure option, but
26636 the From field is used to show the relationships instead of the Subject field.
26637 </DD>
26639 </DL>
26641 <P>
26642 <UL>
26643 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26644 </UL><P>
26645 <End of help on this topic>
26646 </BODY>
26647 </HTML>
26648 ====== h_config_pruning_rule =====
26649 <HTML>
26650 <HEAD>
26651 <TITLE>OPTION: <!--#echo var="VAR_pruning-rule"--></TITLE>
26652 </HEAD>
26653 <BODY>
26654 <H1>OPTION: <!--#echo var="VAR_pruning-rule"--></H1>
26656 By default, Alpine will ask at the beginning of each month whether or not
26657 you want to rename your sent-mail folder to a name like sent-mail-month-year.
26658 (See the feature <A HREF="h_config_prune_uses_iso"><!--#echo var="FEAT_prune-uses-yyyy-mm"--></A> to
26659 change the format of the folder to sent-mail-yyyy-mm.)
26660 It will also ask whether you would like to delete old sent-mail folders.
26661 If you have defined
26662 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>
26663 or
26664 <A HREF="h_config_pruned_folders"><!--#echo var="VAR_pruned-folders"--></A>
26665 Alpine will also ask about pruning those folders.
26666 <P>
26668 With this option you may provide an automatic answer to these questions.
26669 The default value is to ask you what you'd like to do.
26670 <P>
26672 The six possible values for this option are:
26674 <DL>
26675 <DT>ask about rename, ask about deleting</DT>
26676 <DD>This is the default.
26677 Alpine will ask whether you want to rename the folders and whether you
26678 want to delete each of the old folders.
26679 </DD>
26681 <DT>ask about rename, don't delete</DT>
26682 <DD>Alpine will ask whether you want to rename the folders, but won't
26683 ask about or delete old folders.
26684 </DD>
26686 <DT>always rename, ask about deleting</DT>
26687 <DD>This means you want to always answer yes and have Alpine automatically
26688 rename the folder if possible.
26689 You will also be asked about deleting old folders.
26690 </DD>
26692 <DT>always rename, don't delete</DT>
26693 <DD>This means you want to always answer yes and have Alpine automatically
26694 rename the folder if possible.
26695 There will be no deleting of old folders.
26696 </DD>
26698 <DT>don't rename, ask about deleting</DT>
26699 <DD>This means you want to always answer no.
26700 Alpine will not rename the folder.
26701 You will be asked about deleting old folders.
26702 </DD>
26704 <DT>don't rename, don't delete</DT>
26705 <DD>This means you want to always answer no.
26706 Alpine will not rename the folder.
26707 There will be no deleting of old folders, either.
26708 </DD>
26709 </DL>
26711 <P>
26712 <UL>
26713 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26714 </UL><P>
26715 <End of help on this topic>
26716 </BODY>
26717 </HTML>
26718 ====== h_config_reopen_rule =====
26719 <HTML>
26720 <HEAD>
26721 <TITLE>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></TITLE>
26722 </HEAD>
26723 <BODY>
26724 <H1>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></H1>
26726 Alpine normally checks for new mail in the currently open folder
26727 and in the INBOX every few <A HREF="h_config_mailcheck">minutes</A>.
26729 <P>
26730 There are some situations where automatic new-mail checking does not work.
26731 For example, if a mail folder is opened using the POP protocol or a newsgroup
26732 is being read using the NNTP protocol, then new-mail checking is disabled.
26734 <P>
26735 It may be possible to check for new mail in these cases by reopening the
26736 folder.
26737 Alpine does not do this for you automatically, but you may do the commands
26738 manually to cause this to happen.
26739 You reopen by going back to the folder list screen from the message
26740 index screen with the "<" command,
26741 and then going back into the message index screen with
26742 the ">" command.
26743 (Actually, any method you would normally use to open a folder will work the
26744 same as the "<" followed by ">" method.
26745 For example, the GoTo Folder command will work, or you may use L to go to the
26746 Folder List screen and Carriage Return to reopen the folder.)
26748 <P>
26749 There are some cases where Alpine knows that reopening the folder should
26750 be useful as a way to discover new mail.
26751 At the time of this writing, connections made using the POP protocol,
26752 news reading using the NNTP protocol, local news reading, and local
26753 ReadOnly folders that are in the traditional UNIX or the MMDF format all
26754 fall into this category.
26755 There are other cases where it <EM>may</EM> be a way to discover new mail, but Alpine
26756 has no way of knowing, so it might also just be an exercise in futility.
26757 All remote, ReadOnly folders other than those listed just above fall into this
26758 category.
26759 The setting of this option together with the type of folder
26760 controls how Alpine will react to the apparent attempt to reopen a folder.
26762 <P>
26763 If you don't reopen, then you will just be back in
26764 the message index with no change.
26765 You left the index and came back, but the folder remained "open"
26766 the whole time.
26767 However, if you do reopen the folder, the folder is closed and then reopened.
26768 In this case, the current state of the open folder is lost.
26769 The New status, Important and Answered flags,
26770 selected state, Zoom state, collapsed or expanded state of threads,
26771 current message number,
26772 and any other temporary state is all lost when the reopen happens.
26773 For POP folders (but not NNTP newsgroups) the Deleted flags are also lost.
26775 <P>
26776 In the possibilities listed below, the text says "POP/NNTP" in
26777 several places.
26778 That really implies the case where Alpine knows it is a good way to discover
26779 new mail, which is more than just POP and NNTP, but POP and NNTP are
26780 the cases of most interest.
26781 This option probably has more possible values than it deserves. They are:
26783 <DL>
26784 <DT>Always reopen</DT>
26785 <DD>Alpine will not ask whether you want to reopen but will just do the reopen
26786 whenever you type a command that implies a reopen, regardless of the
26787 access method.
26788 In other words, it is assumed you would always answer Yes if asked
26789 about reopening.
26790 </DD>
26792 <DT>Yes for POP/NNTP, Ask about other remote [Yes]</DT>
26793 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
26794 will ask you whether to reopen other remote folders,
26795 with a default answer of Yes.
26796 </DD>
26798 <DT>Yes for POP/NNTP, Ask about other remote [No]</DT>
26799 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
26800 will ask you whether to reopen other remote folders,
26801 with a default answer of No.
26802 </DD>
26804 <DT>Yes for POP/NNTP, No for other remote</DT>
26805 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, and
26806 will assume a No answer for all other remote folders.
26807 </DD>
26809 <DT>Always ask [Yes]</DT>
26810 <DD>Alpine will not differentiate based on access method.
26811 It will always ask for all remote folders, with a default answer of Yes.
26812 </DD>
26814 <DT>Always ask [No]</DT>
26815 <DD>Alpine will not differentiate based on access method.
26816 It will always ask for all remote folders, with a default answer of No.
26817 </DD>
26819 <DT>Ask about POP/NNTP [Yes], No for other remote</DT>
26820 <DD>Alpine will ask if the access method is POP or NNTP, with a default answer
26821 of Yes.
26822 It will never attempt to reopen other remote folders.
26823 </DD>
26825 <DT>Ask about POP/NNTP [No], No for other remote</DT>
26826 <DD>This is the default.
26827 Alpine will ask if the access method is POP or NNTP, with a default answer
26828 of No.
26829 It will never attempt to reopen other remote folders.
26830 </DD>
26832 <DT>Never reopen</DT>
26833 <DD>Alpine will never attempt to reopen already open folders.
26834 </DD>
26835 </DL>
26837 <P>
26838 Remember, wherever it says POP or NNTP above it really means POP or NNTP or
26839 any of the other situations where it is likely that reopening is a good way
26840 to discover new mail.
26842 <P>
26843 There is an alternative that may be of useful in some situations.
26844 Instead of manually checking for new mail you can set up a
26845 <A HREF="h_maildrop">Mail Drop</A>
26846 and automatically check for new mail.
26848 <P>
26849 <UL>
26850 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26851 </UL><P>
26852 <End of help on this topic>
26853 </BODY>
26854 </HTML>
26855 ====== h_config_inc_startup =====
26856 <HTML>
26857 <HEAD>
26858 <TITLE>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></TITLE>
26859 </HEAD>
26860 <BODY>
26861 <H1>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></H1>
26863 This value affects Alpine's behavior when opening the "INBOX" or
26864 one of the "INCOMING MESSAGE FOLDERS".
26865 It determines which message will be the <EM>current message</EM> when
26866 the folder is first opened.
26867 The default value is "first-unseen".
26869 <P>
26870 The seven possible values for this option are:
26872 <DL>
26873 <DT>first-unseen</DT>
26874 <DD>The current message is set to the first
26875 unseen message that has not been marked deleted, or the last message if
26876 all of the messages have been seen previously.
26877 Messages which have not been seen or which have been seen but re-marked
26878 as New are considered unseen messages.
26879 See the note at the bottom of this help about newsgroups.
26880 </DD>
26882 <DT>first-recent</DT>
26883 <DD>Similar to the default, but rather than starting on the first
26884 unseen message Alpine starts on the first <EM>recent</EM> message.
26885 A message is recent if it arrived since the last time the folder was
26886 open. This value causes the current message to be set to the first
26887 recent message if there is one, otherwise to the last
26888 message in the folder.
26889 </DD>
26891 <DT>first-important</DT>
26892 <DD>This will result in the current message being set to the first
26893 message marked Important (but not Deleted).
26894 If no messages are marked Important, then it will be the last message.
26895 Messages are marked Important by <EM>you</EM>, not by the sender, using
26896 the
26897 <A HREF="h_common_flag">Flag command</A>.
26898 Or they may be marked Important by an Alpine
26899 <A HREF="h_mainhelp_filtering">Filter</A>
26900 that you have set up.
26901 </DD>
26903 <DT>first-important-or-unseen</DT>
26904 <DD>This selects the first of the first unseen and the first important
26905 messages.
26906 </DD>
26908 <DT>first-important-or-recent</DT>
26909 <DD>This selects the first of the first recent and the first important
26910 messages.
26911 </DD>
26913 <DT>first</DT>
26914 <DD>Simply starts you on the <EM>first</EM> undeleted message in the folder.
26915 If all messages are deleted you start on the last message.
26916 </DD>
26918 <DT>last</DT>
26919 <DD>Simply starts you on the <EM>last</EM> undeleted message in the folder
26920 If all messages are deleted you start on the last message.
26921 </DD>
26922 </DL>
26924 <P>
26925 NOTE: For newsgroups in the incoming collection, "first-unseen" and
26926 "first-recent" are the same and are affected by whether or not the
26927 feature
26928 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
26929 is turned on.
26930 Also, there is no permanent storage in news for an Important flag.
26931 This means that no messages will be marked Important when a newsgroup is
26932 first opened.
26934 <P>
26935 <UL>
26936 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26937 </UL><P>
26938 <End of help on this topic>
26939 </BODY>
26940 </HTML>
26941 ====== h_config_browser =====
26942 <HTML>
26943 <HEAD>
26944 <TITLE>OPTION: <!--#echo var="VAR_url-viewers"--></TITLE>
26945 </HEAD>
26946 <BODY>
26947 <H1>OPTION: <!--#echo var="VAR_url-viewers"--></H1>
26948 <!--chtml if pinemode="os_windows"-->
26949 PC-Alpine users do not need to enter anything here, unless:<UL>
26950 <LI> they want to override, for use with Alpine, the application defined
26951 in the Windows operating system for handling URLs; or
26952 <LI> they are (planning on) using the same configuration file with
26953 Unix Alpine.
26954 </UL>
26955 <P>
26956 Note that if using a viewer that has a space in its path, you should
26957 use the DOS name for that directory or file. Example:
26958 <PRE>
26959 url-viewer=C:\Progra~1\mozilla\mozilla.exe
26960 </PRE>
26961 <HR><P>
26962 <!--chtml endif-->
26963 This option affects Alpine's handling of URLs that are found in
26964 messages you read. Normally, only URLs Alpine can handle directly
26965 are automatically offered for selection in the "Message
26966 Text" screen. When one or more applications
26967 capable of deciphering URLs on their command line are added here, Alpine
26968 will choose the first available to display URLs it cannot handle directly.
26969 A viewer's availability is based on its being specified with a <B>full
26970 directory path</B> and the evaluation of any optionally supplied
26971 parameters described below.
26973 <P>
26974 Additionally, to support various connection methods and applications, each
26975 entry in this list can optionally begin with one or more of
26976 the following special tokens. The allowed tokens include:
26978 <P>
26979 <DL>
26980 <DT>_TEST(<VAR>test-string</VAR>)_</DT>
26981 <DD>
26982 The <VAR>test-string</VAR> is a shell command that Alpine will run to
26983 evaluate a viewer's availability. The command specified by the test
26984 string is run and if its resulting exit status is non-zero, Alpine will
26985 not consider the associated viewer for use.
26986 </DD>
26988 <DT>_SCHEME(<VAR>scheme-list</VAR>)_</DT>
26989 <DD>
26990 The <VAR>scheme-list</VAR> is a list of one or more (comma-delimited)
26991 URL schemes that are to be used with the associated viewer. This is
26992 the way to configure Alpine to recognize URLs other than the built-in set.
26993 <P>
26994 It can also be used to override Alpine's built-in handlers.
26995 For example, you could specify "news" in the <VAR>scheme-list</VAR>,
26996 and Alpine would use (provided it passed all other criteria) the associated
26997 viewer when it encounterd a URL of the form "news:comp.mail.pine".
26999 </DD>
27000 </DL>
27002 <P>
27003 By default, Alpine will simply append a space character followed by the
27004 selected URL prior to launching the command in your specified SHELL. You can
27005 optionally specify where in the command the selected URL should appear
27006 by using the "_URL_" token. All occurrences found in the command
27007 will be replaced with the selected URL before the command is handed
27008 to the shell. If such replacement occurs, the default appending of the
27009 selected URL does not take place.
27011 <P>
27012 NOTE: If the viewer you specify has any command-line arguments,
27013 including the "_URL_" token, you will need to add a
27014 double-quote character before the command path and after the last
27015 argument (see the "lynx" example below).
27017 <P>
27018 So, here are some example entries:
27019 <PRE>
27020 url-viewers = _TEST("test -n '${DISPLAY}'")_ /usr/local/bin/netscape
27021 "/usr/local/bin/lynx _URL_"
27022 C:\BIN\NETSCAPE.BAT
27023 </PRE>
27024 <P>
27025 This example shows that for the first viewer in the list to be used
27026 the environment variable "DISPLAY" must be defined. If it
27027 is, then the path and file "/usr/local/bin/netscape" must exist.
27028 If neither condition is met,
27029 then the path and file "/usr/local/bin/lynx" must exist.
27030 If it does, then the "_URL_" token is replaced by the selected URL.
27031 If the path to "lynx" is invalid,
27032 then the final path and file C:\BIN\NETSCAPE.BAT must exist.
27033 Note that the last
27034 entry is a DOS/Windows path. This is one way to support Alpine running
27035 on more than one architecture with the same configuration file.<P>
27036 <P>
27037 <!--chtml if pinemode="os_windows"-->
27038 <!--chtml else-->
27039 Note that depending on the type of browser used and the method of
27040 its invocation (such as whether it will open in a separate window) from
27041 the MESSAGE TEXT screen, the browser may "supplant"
27042 the MESSAGE TEXT screen, and you will have to quit the browser to return to
27043 it (for example, when using Lynx; to exit Lynx, use the "Q" command).
27044 In other words, launching the browser from Alpine may make Alpine
27045 "disappear" (although it is still "running")
27046 until you close the browser again.<P>
27047 <UL><LI><A HREF="h_config_browser_xterm">Defining <!--#echo var="VAR_url-viewers"--> in an X windows
27048 environment: for advanced users and systems administrators</A>
27049 </UL>
27050 <!--chtml endif-->
27051 <P>If you are unsure what browsers are available on your system or how to
27052 specify them in Alpine's <!--#echo var="VAR_url-viewers"--> option for best usability, contact your
27053 local computing support staff.
27054 <P><UL>
27055 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27056 </UL>
27057 <P>
27058 <End of help on this topic>
27059 </BODY>
27060 </HTML>
27061 ====== h_config_browser_xterm =====
27062 <HTML>
27063 <HEAD>
27064 <TITLE><!--#echo var="VAR_url-viewers"--> and X windows applications</TITLE>
27065 </HEAD>
27066 <BODY>
27067 <H1>Defining <!--#echo var="VAR_url-viewers"--> in an X windows
27068 environment: for advanced users and systems administrators</H1>
27069 If you are using Alpine with an X-terminal (emulator) and want to define an
27070 X windows-based application in <!--#echo var="VAR_url-viewers"-->,
27071 you may want to do so in a manner that causes any <B>already</B>
27072 invoked viewer application to be used for viewing URLs you select from Alpine
27073 messages, and a <B>new</B> URL-viewer process to be
27074 started <B>only</B> if the same application has <B>not already</B>
27075 been launched -- for one reason, to avoid file-locking contentions among
27076 multiple invocations of the same URL-viewer application.
27077 (The example entries set in the help screen for the "<!--#echo var="VAR_url-viewers"-->"
27078 option does not do this.) A method of doing that would be:<OL>
27079 <LI> use
27080 the _TEST(<VAR>test-string</VAR>)_ token in the <B>first</B> entry to
27081 check (using commands appropriate for your Unix shell
27082 in place of <VAR>test-string</VAR>) for the presence of a
27083 lockfile created by the URL-viewer application -- which implies that the
27084 application is already running, though this is not foolproof.
27085 Following that in the same <!--#echo var="VAR_url-viewers"--> entry, specify the
27086 application with its appropriate command line option(s) to
27087 show the URL selected from the Alpine message in an already open window of
27088 that application, or perhaps in a new window of that application.
27090 <LI> In the
27091 <B>second</B> entry for the <!--#echo var="VAR_url-viewers"--> option, specify the same
27092 application without those command line options, but this time using the
27093 _TEST(...)_ token to check whether the environment variable "DISPLAY"
27094 is defined.
27095 <LI> If you will be using Alpine (with the same .pinerc file) outside of the X
27096 windows environment (for instance, using VT-100 terminal emulation), you
27097 may wish to specify a non-X windows URL-viewer application such as Lynx
27098 as the last entry.
27099 </OL><BR>
27100 How exactly you define your <!--#echo var="VAR_url-viewers"--> entries to do this will depend on
27101 the command shell, the URL-viewer application(s), and possibly the specific
27102 version of the latter, you are using.
27103 <P>
27104 Relevant command
27105 line options for the Netscape browser for showing URLs (selected from Alpine)
27106 when Netscape is already running are discussed in the document
27107 "Remote Control of UNIX Netscape"
27108 found at the URL (as of 12 Aug. 1998):
27109 <P>
27111 <CENTER><A HREF="http://home.netscape.com/newsref/std/x-remote.html">http://home.netscape.com/newsref/std/x-remote.html</A></CENTER>
27113 <P>(If the URL-viewer application is
27114 <B>not</B> running on the same host as Alpine, but being launched from an
27115 applications server, you may not be able to use the command line options for
27116 using an existing invocation of the application in Alpine's <!--#echo var="VAR_url-viewers"--> entry.)
27117 <P>
27118 <!--chtml if this-method="shown-to-work"-->
27119 An example using the Korn shell and the Netscape browser (first entry wrapped
27120 because of its length, but should all appear on one line):
27121 <P>
27122 url-viewers = _TEST("test -L /myhomedir/.netscape/lock")_ "/usr/local/bin/netscape -remote 'openURL(_URL_, new-window)' &"<BR>
27124 _TEST("test -n '${DISPLAY}'")_ "/usr/local/bin/netscape &"<BR>
27125 "/usr/local/bin/lynx '_URL_'"
27126 <P>
27127 <!--chtml endif-->
27128 <P>
27129 <UL>
27130 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27131 </UL><P>
27132 <End of help on this topic>
27133 </BODY>
27134 </HTML>
27135 ====== h_config_enable_full_hdr =====
27136 <HTML>
27137 <HEAD>
27138 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></TITLE>
27139 </HEAD>
27140 <BODY>
27141 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></H1>
27143 This feature enables the "H Full Headers" command which toggles between
27144 the display of all headers in the message and the normal edited view of
27145 headers. The Full Header command also controls which headers are included
27146 for Export, Pipe, Print, Forward, and Reply functions. (For Reply, the
27147 Full Header mode will respect the
27148 <A HREF="h_config_include_header">"Include-Headers-in-Reply"</A>
27149 feature setting.)
27150 <P>
27151 If Full Header mode is turned on and you Forward a message, you will
27152 be asked if you'd like to forward the message as an attachment, as opposed
27153 to including the text of the message in the body of your new message.
27154 <P>
27155 If you have also turned on the
27156 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
27157 option then the Full Headers command actually rotates through three states
27158 instead of just two.
27159 The first is the normal view with long quotes suppressed.
27160 The second is the normal view but with the long quotes included.
27161 The last enables the display of all headers in the message.
27162 When using Export, Pipe, Print, Forward, or Reply the quotes are
27163 never suppressed, so the first two states are identical.
27164 <P>
27165 Normally, the Header Mode will reset
27166 to the default behavior when moving to a new message.
27167 The mode can be made to persist from message to message by setting the feature
27168 <A HREF="h_config_quell_full_hdr_reset"><!--#echo var="FEAT_quell-full-header-auto-reset"--></A>.
27169 <P>
27170 <UL>
27171 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27172 </UL><P>
27173 <End of help on this topic>
27174 </BODY>
27175 </HTML>
27176 ====== h_config_enable_full_hdr_and_text =====
27177 <HTML>
27178 <HEAD>
27179 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></TITLE>
27180 </HEAD>
27181 <BODY>
27182 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></H1>
27184 This feature affects how the "H Full Headers" command displays
27185 message text. If set, the raw message text will be displayed. This
27186 especially affects MIME formatted email, where the entire MIME format
27187 will be displayed. This feature similarly affects how messages are
27188 included for the Export, Pipe, Print, Forward, and Reply functions.
27189 <P>
27190 When viewing a raw message that has attachments with this feature set,
27191 you will not be able to view attachments without first leaving full
27192 headers mode. This is because MIME parsing is not done on the raw message.
27193 <P>
27194 <UL>
27195 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27196 </UL><P>
27197 <End of help on this topic>
27198 </BODY>
27199 </HTML>
27200 ====== h_config_enable_pipe =====
27201 <HTML>
27202 <HEAD>
27203 <TITLE>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></TITLE>
27204 </HEAD>
27205 <BODY>
27206 <H1>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></H1>
27208 This feature enables the "| Pipe" command that sends the current message
27209 to the specified command for external processing.
27210 <P>
27212 A short description of how the pipe command works is given
27213 <A HREF="h_pipe_command">here</A>.
27215 <P>
27216 <UL>
27217 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27218 </UL><P>
27219 <End of help on this topic>
27220 </BODY>
27221 </HTML>
27222 ====== h_config_quell_full_hdr_reset =====
27223 <HTML>
27224 <HEAD>
27225 <TITLE>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></TITLE>
27226 </HEAD>
27227 <BODY>
27228 <H1>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></H1>
27230 The <A HREF="h_common_hdrmode">HdrMode Command</A>
27231 normally resets to the default state when switching to a new message.
27232 For example, if you've used the "H" command to turn on Full
27233 Headers for a message you are viewing, and then you type the Next command
27234 to look at the next message, the full headers will no longer be shown.
27235 Setting this feature disables that reset.
27236 Instead, the Header Mode remains the same from message to message.
27238 <P>
27239 The presence or absence of the HdrMode command is determined by the
27240 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
27241 Feature-List option.
27242 <P>
27243 <UL>
27244 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27245 </UL><P>
27246 <End of help on this topic>
27247 </BODY>
27248 </HTML>
27249 ====== h_config_enable_tab_complete =====
27250 <HTML>
27251 <HEAD>
27252 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></TITLE>
27253 </HEAD>
27254 <BODY>
27255 <H1>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></H1>
27257 This feature enables the TAB key when at a prompt for a filename. In this
27258 case, TAB will cause the partial name already entered to be automatically
27259 completed, provided the partial name is unambiguous.
27260 This feature is on by default.
27261 <P>
27262 Similarly, this feature also enables TAB completion of address book
27263 nicknames when at a prompt for a nickname,
27264 or when typing in an address field in the composer.
27265 <P>
27266 <End of help on this topic>
27267 </BODY>
27268 </HTML>
27269 ====== h_config_quit_wo_confirm =====
27270 <HTML>
27271 <HEAD>
27272 <TITLE>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></TITLE>
27273 </HEAD>
27274 <BODY>
27275 <H1>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></H1>
27277 This feature controls whether or not Alpine will ask for confirmation when a
27278 Quit command is received.
27279 <P>
27280 <End of help on this topic>
27281 </BODY>
27282 </HTML>
27283 ====== h_config_quote_replace_noflow =====
27284 <HTML>
27285 <HEAD>
27286 <TITLE>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></TITLE>
27287 </HEAD>
27288 <BODY>
27289 <H1>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></H1>
27291 This feature, which is only active when
27292 <A HREF="h_config_quote_replace_string"><!--#echo var="VAR_quote-replace-string"--></A> is
27293 also set,
27294 enables quote-replacement on non-flowed messages. It is off
27295 by default because a non-flowed message is more dependent on its format,
27296 and thus quote-replacement may cause less-than-pleasing results.
27297 Setting this feature will cause quote-replacement similar to that of flowed
27298 messages, but with the added possibility of long lines being wrapped
27299 into new lines if the Quote-Replacement-String is longer than the string
27300 it is replacing, which is "> ".
27301 <P>
27302 <End of help on this topic>
27303 </BODY>
27304 </HTML>
27305 ====== h_config_enable_jump =====
27306 <HTML>
27307 <HEAD>
27308 <TITLE>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></TITLE>
27309 </HEAD>
27310 <BODY>
27311 <H1>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></H1>
27313 When this feature is set you may enter a number (followed by RETURN)
27314 and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT
27315 screens. In other words, it obviates the need for typing the "J" for the
27316 Jump command.
27317 <P>
27318 <End of help on this topic>
27319 </BODY>
27320 </HTML>
27321 ====== h_config_enable_alt_ed =====
27322 <HTML>
27323 <HEAD>
27324 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></TITLE>
27325 </HEAD>
27326 <BODY>
27327 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></H1>
27329 If this feature is set (the default), and the
27330 <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27331 <B>is not</B> set, entering
27332 the ^_ (Ctrl-underscore) key while composing a message will prompt you
27333 for the name of the editor you would like to use.
27334 <P>
27335 If the environment variable $EDITOR is set, its value will be offered as
27336 a default.
27337 <P>
27338 If the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27339 <B>is</B> set, the ^_ key will activate the specified
27340 editor without prompting, in which case it is not necessary to
27341 set the "<!--#echo var="FEAT_enable-alternate-editor-cmd"-->" feature.
27342 <P>
27343 <UL>
27344 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27345 </UL><P>
27346 <End of help on this topic>
27347 </BODY>
27348 </HTML>
27349 ====== h_config_alt_ed_now =====
27350 <HTML>
27351 <HEAD>
27352 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></TITLE>
27353 </HEAD>
27354 <BODY>
27355 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></H1>
27357 If this feature and the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A>
27358 variable are both set, Alpine will
27359 automatically activate the specified editor when the cursor is moved from
27360 the header of the message being composed into the message text. For
27361 replies, the alternate editor will be activated immediately. If this
27362 feature is set but the "<!--#echo var="VAR_editor"-->" variable is not set, then Alpine will
27363 automatically ask for the name of an alternate editor when the cursor
27364 is moved out of the header being composed, or if a reply is being done.
27366 <P><UL>
27367 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27368 </UL>
27369 <P>
27370 <End of help on this topic>
27371 </BODY>
27372 </HTML>
27373 ====== h_config_enable_bounce =====
27374 <HTML>
27375 <HEAD>
27376 <TITLE>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></TITLE>
27377 </HEAD>
27378 <H1>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></H1>
27379 <BODY>
27381 Setting this feature enables the "B Bounce" command, which will prompt
27382 for an address and *remail* the message to the new recipient. This command
27383 is used to re-direct messages that you have received in error, or need to
27384 be redirected for some other reason (e.g. list moderation). The final
27385 recipient will see a header indicating that you have Resent the msg, but
27386 the message's From: header will show the original author of the message,
27387 and replies to it will go back to that author, and not to you.
27388 <P>
27389 <End of help on this topic>
27390 </BODY>
27391 </HTML>
27392 ====== h_config_enable_agg_ops =====
27393 <HTML>
27394 <HEAD>
27395 <TITLE>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></TITLE>
27396 </HEAD>
27397 <BODY>
27398 <H1>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></H1>
27400 When this feature is set you may use the commands and subcommands that relate to
27401 performing operations on more than one message at a time. We call these
27402 "aggregate operations". In particular, the
27403 <!--chtml if pinemode="function_key"-->"F5
27404 <!--chtml else-->";
27405 <!--chtml endif--> Select",
27407 <!--chtml if pinemode="function_key"-->
27408 "F6
27409 <!--chtml else-->
27410 "A
27411 <!--chtml endif-->
27412 Apply", and
27413 <!--chtml if pinemode="function_key"-->
27414 "F4
27415 <!--chtml else-->
27416 "Z
27417 <!--chtml endif-->
27418 Zoom" commands are enabled by this feature. Select is used to
27419 "tag" one or more messages meeting the specified criteria. Apply can
27420 then be used to apply any message command to all of the selected/tagged
27421 messages. Further, the Zoom command allows you to toggle the MESSAGE INDEX
27422 view between just those Selected and all messages in the folder.
27423 <P>
27424 This feature also enables the
27425 <!--chtml if pinemode="function_key"-->
27426 "F7"
27427 <!--chtml else-->
27428 "^X"
27429 <!--chtml endif-->
27431 subcommand in the MESSAGE INDEX
27432 WhereIs command that causes all messages matching the WhereIs argument to
27433 become selected; and the Select, Select Current, and ZoomMode commands in the
27434 <A HREF="h_folder_maint">FOLDER LIST screen</A>.
27435 <P>
27436 Some related help topics are
27437 <UL>
27438 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
27439 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
27440 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
27441 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
27442 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
27443 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
27444 </UL>
27445 <P>
27446 <UL>
27447 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27448 </UL><P>
27449 <End of help on this topic>
27450 </BODY>
27451 </HTML>
27453 ====== h_config_enable_flag =====
27454 <HTML>
27455 <HEAD>
27456 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></TITLE>
27457 </HEAD>
27458 <BODY>
27459 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></H1>
27461 Setting this feature enables the
27462 <A HREF="h_common_flag">"* Flag"</A>
27463 command that allows you to
27464 manipulate the status flags associated with a message. By default, Flag
27465 will set the "Important" flag, which results in an asterisk being
27466 displayed in column one of the MESSAGE INDEX for such messages.
27467 <P>
27468 <End of help on this topic>
27469 </BODY>
27470 </HTML>
27471 ====== h_config_flag_screen_default =====
27472 <HTML>
27473 <HEAD>
27474 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></TITLE>
27475 </HEAD>
27476 <BODY>
27477 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></H1>
27479 The feature modifies the behavior of the
27480 <a href="h_common_flag">Flag</a>
27481 command (provided it too is
27482 <A HREF="h_config_enable_flag">enabled</A>).
27483 By default, when the "* Flag" command is selected,
27484 Alpine offers a prompt to set one of several flags and also offers the
27485 option of entering the detailed flag manipulation screen via the "^T"
27486 key. Enabling this feature causes Alpine to immediately enter the detailed
27487 flag screen rather than first offer the simple prompt.
27488 The
27489 <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.
27490 <P>
27491 <End of help on this topic>
27492 </BODY>
27493 </HTML>
27494 ====== h_config_flag_screen_kw_shortcut =====
27495 <HTML>
27496 <HEAD>
27497 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></TITLE>
27498 </HEAD>
27499 <BODY>
27500 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></H1>
27502 This feature modifies the behavior of the
27503 <a href="h_common_flag">Flag</a> command
27504 and the <A HREF="h_index_cmd_select">Select</A> command.
27505 This feature is set by default.
27506 When this feature is not set, when the "* Flag" command is selected,
27507 Alpine offers a prompt to set one of several flags and also offers the
27508 option of entering the detailed flag manipulation screen via the "^T"
27509 key.
27510 If you have
27511 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
27512 defined, then enabling this feature adds a shortcut way to set or unset
27513 keywords.
27514 You use "*" followed by the first letter of a keyword (or the nickname of
27515 a keyword if you've given it a nickname) and that will set the keyword.
27516 <P>
27517 An example is easier to understand than the explanation.
27518 The flag command can always be used to set the system flags.
27519 For example, to set the Answered flag you would type
27520 <P>
27521 <CENTER><SAMP>* A</SAMP></CENTER>
27522 <P>
27523 Now suppose you have defined a keyword "Work" using the <!--#echo var="VAR_keywords"-->
27524 option in the Config screen.
27525 By default, to set a keyword like "Work" you would usually
27526 have to go to the Flag Details screen using
27527 the "^T To Flag Details" command.
27528 Instead, if you have enabled this feature, you may type
27529 <P>
27530 <CENTER><SAMP>* W</SAMP></CENTER>
27531 <P>
27532 to set the Work flag, or
27533 <P>
27534 <CENTER><SAMP>* ! W</SAMP></CENTER>
27535 <P>
27536 to unset it.
27537 Just like for the other flag setting commands, the case of the letter does
27538 not matter, so "w" or "W" both set the "Work"
27539 keyword.
27540 <P>
27541 Notice that you can only use this trick for one keyword that begins
27542 with "W".
27543 If you happen to have a "Work" keyword and another keyword that is
27544 "WIFI" the "* W" command will set the first one in
27545 your list of keywords.
27546 Also, there are five letters that are reserved for system
27547 flags and the NOT command.
27548 If you type "* A" it will always set the Answered flag, not
27549 your "Aardvark" keyword.
27550 In order to set the "Aardvark" keyword you'll still have to use
27551 the Flag Details screen.
27552 <P>
27553 Because enabling the
27554 <A HREF="h_config_flag_screen_default"><!--#echo var="FEAT_enable-flag-screen-implicitly"--></A>
27555 option causes Alpine to skip directly to the Flag Details screen when the
27556 Flag command is used,
27557 setting it will cause this feature to have no effect at all.
27558 <P>
27559 Similarly, when Selecting by Keyword, setting this option will allow you
27560 to use Keyword initials instead of full keywords.
27561 <P>
27562 <End of help on this topic>
27563 </BODY>
27564 </HTML>
27565 ====== h_config_can_suspend =====
27566 <HTML>
27567 <HEAD>
27568 <TITLE>FEATURE: <!--#echo var="FEAT_enable-suspend"--></TITLE>
27569 </HEAD>
27570 <BODY>
27571 <H1>FEATURE: <!--#echo var="FEAT_enable-suspend"--></H1>
27573 Setting this feature will allow you to type ^Z (Control Z) to
27574 <!--chtml if pinemode="os_windows"-->
27575 minimize Alpine into its icon, bringing into focus whatever
27576 application is running behind the PC-Alpine window.
27577 <!--chtml else-->
27578 temporarily suspend Alpine.
27580 <P>
27581 This does not exit Alpine, but puts it in the background to watch
27582 for new mail and such. Normally, you type a command, such
27583 as "fg" at your system prompt to return to your Alpine session.
27585 <P>
27586 The <A HREF="h_config_suspend_spawns"><!--#echo var="FEAT_use-subshell-for-suspend"--></A> feature
27587 adjusts whether Alpine is placed into the background of the shell its
27588 running in or starts a news shell.
27589 <!--chtml endif-->
27591 <P>
27592 <UL>
27593 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27594 </UL><P>
27595 <End of help on this topic>
27596 </BODY>
27597 </HTML>
27598 ====== h_config_take_lastfirst ======
27599 <HTML>
27600 <HEAD>
27601 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></TITLE>
27602 </HEAD>
27603 <BODY>
27604 <H1>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></H1>
27606 Normally, when TakeAddr is used to copy an address from a message into
27607 an address book entry, Alpine will attempt to rewrite the full name of the
27608 address in the form
27609 <P>
27611 Last, First<P>
27613 instead of<P>
27615 First Last
27617 <P>
27618 It does this because many people find it useful to sort by Last name
27619 instead of First name. If this feature is set, then the TakeAddr command
27620 will not attempt to reverse the name in this manner.
27621 <P>
27622 <End of help on this topic>
27623 </BODY></HTML>
27624 ====== h_config_disable_regex ======
27625 <HTML>
27626 <HEAD>
27627 <TITLE>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></TITLE>
27628 </HEAD>
27629 <BODY>
27630 <H1>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></H1>
27632 Normally, the
27633 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
27634 option is interpreted as a regular expression.
27635 One type of address that might cause trouble is an address that
27636 contains a plus sign.
27637 If you want to have an address with a plus as one of your
27638 <!--#echo var="VAR_alt-addresses"-->
27639 and you don't want to use regular expressions, then setting this
27640 feature will cause Alpine to treat the addresses you list literally instead.
27641 <P>
27642 <End of help on this topic>
27643 </BODY></HTML>
27644 ====== h_config_take_fullname ======
27645 <HTML>
27646 <HEAD>
27647 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></TITLE>
27648 </HEAD>
27649 <BODY>
27650 <H1>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></H1>
27652 Normally, when TakeAddr is used to copy an address or addresses
27653 from a message into an address book entry, Alpine will try to preserve
27654 the full name associated with each address in the list of addresses.
27655 The reason for this is so that if the entry is a list or later becomes a
27656 list, then information about the individual addresses in the list
27657 is preserved.
27658 If you would rather just have the simple addresses in the list of addresses,
27659 set this feature. For example, with the default setting you might
27660 see something like this in the ADDRESS BOOK editor after you type TakeAddr
27661 <P>
27662 <PRE>
27663 Nickname : nick
27664 Fullname : Bedrock Elders
27665 Fcc :
27666 Comment :
27667 Addresses : Fred Flintstone <flint@bedrock.org>,
27668 Barney Rubble <rubble@bedrock.org>
27669 </PRE>
27670 <P>
27671 but with this feature set it would look like
27672 <P>
27673 <PRE>
27674 Nickname : nick
27675 Fullname : Bedrock Elders
27676 Fcc :
27677 Comment :
27678 Addresses : flint@bedrock.org,
27679 rubble@bedrock.org
27680 </PRE>
27681 <P>
27682 instead. Note the difference in the Addresses field.
27683 <P>
27684 <End of help on this topic>
27685 </BODY></HTML>
27686 ====== h_config_print_from ======
27687 <HTML>
27688 <HEAD>
27689 <TITLE>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></TITLE>
27690 </HEAD>
27691 <BODY>
27692 <H1>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></H1>
27694 If this feature is set, then the Berkeley-mail style From line is included
27695 at the start of each message that is printed. This line looks something
27696 like the following, with the address replaced by the address from the
27697 From line of the message being printed:
27698 <P>
27699 From user@domain.somewhere.com Mon May 13
27700 14:11:06 1998
27701 <P>
27702 <End of help on this topic>
27703 </BODY>
27704 </HTML>
27705 ====== h_config_expanded_distlists ======
27706 <HTML>
27707 <HEAD>
27708 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></TITLE>
27709 </HEAD>
27710 <BODY>
27711 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></H1>
27712 If this feature is set, then distribution lists in the address book
27713 screen will always be expanded automatically.
27714 <P>
27715 <End of help on this topic>
27716 </BODY>
27717 </HTML>
27718 ====== h_config_compose_news_wo_conf ======
27719 <HTML>
27720 <HEAD>
27721 <TITLE>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></TITLE>
27722 </HEAD>
27723 <BODY>
27724 <H1>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></H1>
27725 This feature controls one aspect of Alpine's Composer. If you enter the
27726 composer while reading a newsgroup, you will normally be prompted to
27727 determine whether you intend the new message to be posted to the current
27728 newsgroup or not. If this feature is set, Alpine will not prompt you
27729 in this situation, and will assume that you do indeed wish to post
27730 to the newsgroup you are reading.
27731 <P>
27732 <End of help on this topic>
27733 </BODY>
27734 </HTML>
27735 ====== h_config_compose_rejects_unqual ======
27736 <HTML>
27737 <HEAD>
27738 <TITLE>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></TITLE>
27739 </HEAD>
27740 <BODY>
27741 <H1>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></H1>
27743 This feature controls one aspect of the message composer; in particular,
27744 what happens when an unqualified name is entered into an address header.
27745 If set, unqualified names entered as addresses will be treated as errors
27746 unless they match an addressbook nickname. Alpine will not attempt to turn
27747 them into complete addresses by adding your local domain.<P>
27749 A complete (fully qualified) address is one containing a username followed
27750 by an "@" ("at") symbol, followed by a domain name (e.g.
27751 "jsmith@example.com"). An unqualified name is one <B>without</B>
27752 the "@" symbol and domain name (e.g. "jsmith").
27754 (See also <A HREF="h_address_format">Explanation of Address formats</A>.)
27756 <P>
27758 When you enter a fully qualified address, Alpine does not interpret or
27759 modify it, but simply passes it on to the mail-transport-agent (MTA) for
27760 your system. Alpine conforms to the Internet standards governing message
27761 headers and will not send an unqualifed name to the MTA. Therefore, when
27762 you enter an unqualified name, Alpine will normally attempt to turn it into
27763 a fully qualified address, first by checking to see if you have entered a
27764 matching nickname in your addressbook, or failing that, by simply adding
27765 your own domain to the name entered. So if your address is
27766 "jsmith@example.com" and you enter "fred", then (assuming
27767 "fred" is not a nickname in your addressbook), Alpine will turn
27768 that into "fred@example.com".<P>
27770 There are situations where it is not desirable for Alpine to interpret such
27771 unqualified names as valid (local) addresses. For example, if "fred"
27772 turned out to be a typo (intended to be an addressbook nickname), but
27773 there actually was a "fred" in your local domain, the message might
27774 be mis-delivered without your realizing it. In order to reduce the likelihood
27775 of such accidents, setting this feature will cause Alpine to treat such
27776 addresses as errors, and require that you explicitly enter the full local
27777 address (e.g. "fred@example.com") or correct the name so that it
27778 matches an address book nickname.<P>
27780 Consider this a safety feature against mis-directed mail.
27781 <P>
27782 <UL>
27783 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27784 </UL><P>
27785 <End of help on this topic>
27786 </BODY>
27787 </HTML>
27788 ====== h_config_quell_local_lookup ======
27789 <HTML>
27790 <HEAD>
27791 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></TITLE>
27792 </HEAD>
27793 <BODY>
27794 <H1>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></H1>
27796 This feature controls an aspect of Alpine's Composer, and if needed, will
27797 usually be set by your system manager in Alpine's system-wide configuration
27798 file. Specifically, if this feature is set, Alpine will not attempt to look
27799 in the system password file to find a Full Name for the entered address.
27800 <P>
27801 Normally, names you enter into address fields (e.g. To: or Cc:) are
27802 checked against your address book(s) to see if they match an address book
27803 nickname. Failing that, (in Unix Alpine) the name is then checked against
27804 the Unix password file. If the entered name matches a username in the
27805 system password file, Alpine extracts the corresponding Full Name information
27806 for that individual, and adds that to the address being entered.
27807 <P>
27808 However, password file matching can have surprising (incorrect) results if
27809 other users of the system do not receive mail at the domain you are using.
27810 That is, if either the
27811 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> or
27812 <A HREF="h_config_domain_name">"<!--#echo var="VAR_use-only-domain-name"-->"</A>
27813 option
27814 is set such that the administrative domain of other users on the system
27815 isn't accurately reflected, Alpine should be told that a passwd file match
27816 is coincidental, and Full Name info will be incorrect. For example, a
27817 personal name from the password file could get falsely paired with the
27818 entered name as it is turned into an address in the configured domain.
27819 <P>
27820 If you are seeing this behavior, enabling this feature will prevent Unix
27821 Alpine from looking up names in the password file to find the Full Name
27822 for incomplete addresses you enter.<P>
27823 <UL>
27824 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27825 </UL>
27826 <P>
27827 <End of help on this topic>
27828 </BODY>
27829 </HTML>
27830 ====== h_config_tab_checks_recent ======
27831 <HTML>
27832 <HEAD>
27833 <TITLE>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></TITLE>
27834 </HEAD>
27835 <BODY>
27836 <H1>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></H1>
27838 In a FOLDER LIST screen, the TAB key usually just changes which
27839 folder is highlighted.
27840 If this feature is set, then the TAB key will cause the number of
27841 recent messages and the total number of messages in the highlighted folder
27842 to be displayed instead.
27844 <P>
27845 <End of help on this topic>
27846 </BODY>
27847 </HTML>
27848 ====== h_config_maildrops_preserve_state ======
27849 <HTML>
27850 <HEAD>
27851 <TITLE>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></TITLE>
27852 </HEAD>
27853 <BODY>
27854 <H1>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></H1>
27856 This feature affects the way <A HREF="h_maildrop">Mail Drops</A> work.
27857 Normally, when mail is moved from a Mail Drop folder to a destination
27858 folder, it is delivered as new mail.
27859 Any Seen/New, Answered, Important/Flagged state that has changed will be
27860 ignored.
27861 All of the mail will be considered unSeen, unAnswered, and unImportant after
27862 it is moved.
27863 <P>
27864 If this feature is set, then the state changes that have been made
27865 to the messages in the Mail Drop folder will be preserved.
27866 <P>
27867 In any case, messages that are already marked Deleted when the
27868 mail is to be moved from the Mail Drop will be ignored.
27869 <P>
27870 <End of help on this topic>
27871 </BODY>
27872 </HTML>
27873 ====== h_config_preopen_stayopens ======
27874 <HTML>
27875 <HEAD>
27876 <TITLE>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></TITLE>
27877 </HEAD>
27878 <BODY>
27879 <H1>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></H1>
27881 This feature is related to the option
27882 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
27883 Normally, Stay Open folders are only opened on demand, when the user
27884 asks to open them.
27885 From then on they are kept open for the duration of the session.
27886 However, if this feature is set, then the Stay Open folders will all be
27887 opened at startup, at the same time that the INBOX is opened.
27889 <P>
27890 <End of help on this topic>
27891 </BODY>
27892 </HTML>
27893 ====== h_config_expunge_inbox ======
27894 <HTML>
27895 <HEAD>
27896 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></TITLE>
27897 </HEAD>
27898 <BODY>
27899 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></H1>
27901 The INBOX is normally treated differently from regular folders in several
27902 ways.
27903 One of the differences is that the normal "close" sequence of
27904 events is deferred until Alpine is exited, instead of happening when you
27905 leave the INBOX to view another folder.
27906 The "close" sequence normally includes the Expunging
27907 of deleted messages
27908 (either automatically or after a prompt, controlled by the features
27909 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
27910 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
27911 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
27912 handling of the
27913 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>.
27915 <P>
27916 If this feature is set the "close" sequence handling will take
27917 place every time you leave the INBOX.
27918 The INBOX will still be kept open, but the offer to Expunge and the archiving
27919 to the <!--#echo var="VAR_read-message-folder"-->
27920 will take place each time you leave the INBOX instead of only once at the
27921 end of the session.
27923 <P>
27924 <End of help on this topic>
27925 </BODY>
27926 </HTML>
27927 ====== h_config_expunge_stayopens ======
27928 <HTML>
27929 <HEAD>
27930 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></TITLE>
27931 </HEAD>
27932 <BODY>
27933 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></H1>
27935 This feature is related to the option
27936 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
27937 Stay Open folders are treated differently from regular folders in several
27938 ways.
27939 One of the differences is that the normal "close" sequence of
27940 events is deferred until Alpine is exited, instead of happening when you
27941 leave the folder to view another folder.
27942 The "close" sequence normally includes the Expunging
27943 of deleted messages
27944 (either automatically or after a prompt, controlled by the features
27945 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
27946 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
27947 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
27948 handling of
27949 <A HREF="h_config_archived_folders"><!--#echo var="VAR_incoming-archive-folders"--></A>.
27951 <P>
27952 If this feature is set the "close" sequence handling will take
27953 place when you leave the Stay Open folder.
27954 The folder will still be kept open, but the offer to Expunge and the archiving
27955 will take place each time you leave the folder instead of only once at the
27956 end of the session.
27957 This feature does not affect the INBOX, which will still only be processed
27958 when you exit Alpine.
27959 However, there is a similar feature that affects only the INBOX called
27960 <A HREF="h_config_expunge_inbox">"<!--#echo var="FEAT_offer-expunge-of-inbox"-->"</A>.
27962 <P>
27963 <End of help on this topic>
27964 </BODY>
27965 </HTML>
27966 ====== h_config_preserve_start_stop ======
27967 <HTML>
27968 <HEAD>
27969 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></TITLE>
27970 </HEAD>
27971 <BODY>
27972 <H1>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></H1>
27974 This feature controls how special control key characters, typically
27975 Ctrl-S and Ctrl-Q, are interpreted when input to Alpine. These characters
27976 are known as the "stop" and "start" characters and are sometimes used in
27977 communications paths to control data flow between devices that operate at
27978 different speeds.
27980 <P>
27982 By default, Alpine turns the system's handling of these special characters
27983 off except during printing. However, if you see Alpine reporting input errors
27984 such as:
27985 <P>
27986 [ Command "^Q" not defined for this screen.]
27987 <P>
27988 and, at the same time, see your display become garbled, then it is likely
27989 that setting this option will solve the problem. Be aware, though, that
27990 enabling this feature will also cause Alpine to ostensibly "hang"
27991 whenever the Ctrl-S key combination is entered as the system is now
27992 interpreting such input as a "stop output" command. To "start
27993 output" again, simply type Ctrl-Q.
27994 <P>
27995 <End of help on this topic>
27996 </BODY>
27997 </HTML>
27998 ====== h_config_enable_incoming ======
27999 <HTML>
28000 <HEAD>
28001 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></TITLE>
28002 </HEAD>
28003 <BODY>
28004 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></H1>
28006 Alpine's Incoming Message Folders collection
28007 provides a convenient way to access multiple incoming folders.
28008 It is also useful if you have accounts on multiple computers.
28009 <P>
28011 If set, this feature defines a pseudo-folder collection called
28012 "INCOMING MESSAGE FOLDERS". Initially, the only folder included
28013 in this collection will be your INBOX, which will no longer show up in
28014 your Default folder collection.
28015 <P>
28017 You may add more folders to the Incoming Message Folders collection by
28018 using the
28019 <!--chtml if pinemode="function_key"-->
28020 "F10
28021 <!--chtml else-->
28022 "A
28023 <!--chtml endif-->
28024 Add" command in the FOLDER LIST screen. You will be prompted for
28025 the host the folder is stored on (which defaults to the same host used
28026 for your INBOX), a nickname, and the actual folder name. Once a set
28027 of Incoming Message Folders are defined, the TAB key (in MESSAGE INDEX
28028 or MESSAGE TEXT screens) may be used to scan the folders for those
28029 with Recent messages. If you add more folders to
28030 your <!--#echo var="VAR_incoming-folders"--> collection, turning this feature back off will have
28031 no effect.
28032 <P>
28033 NOTE: Normally the software that actually delivers mail (the stuff that happens
28034 before Alpine is involved) is in a better position to do delivery filtering
28035 than is Alpine itself.
28036 If possible, you may want to look at programs such as
28037 "filter" or "procmail", which are examples of delivery
28038 filtering programs.
28039 If you'd prefer to have Alpine do the filtering for you, you may set that
28040 up.
28041 Look <A HREF="h_rules_filter">here</A> for help with Alpine filtering.
28042 <P>
28043 <UL>
28044 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28045 </UL><P>
28046 <End of help on this topic>
28047 </BODY>
28048 </HTML>
28049 ====== h_config_enable_incoming_checking ======
28050 <HTML>
28051 <HEAD>
28052 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></TITLE>
28053 </HEAD>
28054 <BODY>
28055 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></H1>
28057 This feature is only operational if you have enabled the optional
28058 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> collection.
28059 If you do have Incoming Message Folders and you also set this feature,
28060 then the number of Unseen messages in each folder will be displayed
28061 in the FOLDER LIST screen for the Incoming Message Folders.
28062 The number of Unseen messages in a folder will be displayed in parentheses
28063 to the right of the name of each folder.
28064 If there are no Unseen messages in a folder then only the name
28065 is displayed, not a set of parentheses with zero inside them.
28066 A redraw command, Ctrl-L, can be used in the FOLDER LIST screen for
28067 the Incoming Message Folders to cause an immediate update.
28068 <P>
28069 If a check for Unseen messages fails for a particular folder then Alpine
28070 will no longer attempt to check that folder for the duration of the
28071 session and this will be indicated by a question mark inside the
28072 parentheses.
28073 <P>
28074 The features
28075 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>,
28076 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>,
28077 <A HREF="h_config_incoming_list"><!--#echo var="VAR_incoming-check-list"--></A>,
28078 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>,
28079 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>, and
28080 <A HREF="h_config_incoming_timeo"><!--#echo var="VAR_incoming-check-timeout"--></A>
28081 all affect how this feature behaves.
28082 <P>
28083 <UL>
28084 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28085 </UL><P>
28086 <End of help on this topic>
28087 </BODY>
28088 </HTML>
28089 ====== h_config_incoming_checking_total ======
28090 <HTML>
28091 <HEAD>
28092 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></TITLE>
28093 </HEAD>
28094 <BODY>
28095 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></H1>
28097 This option has no effect unless the feature
28098 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
28099 is set, which in turn has no effect unless
28100 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28101 is set.
28102 <P>
28103 When incoming folder checking is turned on the default is to display
28104 the number of unseen messages in each folder.
28105 More precisely, it is the number of undeleted unseen messages.
28106 Using this option you may also display the total number of messages
28107 in each folder.
28108 Instead of a single number representing the number of unseen messages
28109 you will get two numbers separated by a slash character.
28110 The first is the number of unseen messages and the second is the
28111 total number of messages.
28112 <P>
28113 You may also use the recent message count instead of the unseen message
28114 count by turning on the feature
28115 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>.
28116 <P>
28117 <UL>
28118 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28119 </UL><P>
28120 <End of help on this topic>
28121 </BODY>
28122 </HTML>
28123 ====== h_config_incoming_checking_recent ======
28124 <HTML>
28125 <HEAD>
28126 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></TITLE>
28127 </HEAD>
28128 <BODY>
28129 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></H1>
28131 This option has no effect unless the feature
28132 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
28133 is set, which in turn has no effect unless
28134 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28135 is set.
28136 <P>
28137 When incoming folder checking is turned on the default is to display
28138 the number of unseen messages in each folder.
28139 More precisely, it is the number of undeleted unseen messages.
28140 Using this option you may display the number of recent messages instead
28141 of the number of unseen messages.
28142 A message is only counted as recent if this is the first session to
28143 see it, so the recent count might be less than the unseen count.
28144 The difference between the two would be accounted for by the unseen messages
28145 in the folder which were there previously but have not been looked at yet.
28146 <P>
28147 If you simultaneously run more than one email client at a time
28148 (for example, you run more than one Alpine in parallel) then turning
28149 this feature on can cause some confusion.
28150 The confusion stems from the fact that each message is only considered to be
28151 recent in one session.
28152 That means that the counts of new messages may be different in the two
28153 Alpines running side by side, because each incoming message will only be
28154 counted as recent in one of the two sessions.
28155 <P>
28156 You may also display the total number of messages
28157 in each folder by using the
28158 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
28159 option.
28160 <P>
28161 <UL>
28162 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28163 </UL><P>
28164 <End of help on this topic>
28165 </BODY>
28166 </HTML>
28167 ====== h_config_attach_in_reply ======
28168 <HTML>
28169 <HEAD>
28170 <TITLE>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></TITLE>
28171 </HEAD>
28172 <BODY>
28173 <H1>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></H1>
28175 This feature controls an aspect of Alpine's Reply command. If set, any MIME
28176 attachments that were part of the original message will automatically be
28177 included in the Reply.
28178 <P>
28179 <End of help on this topic>
28180 </BODY>
28181 </HTML>
28182 ====== h_config_include_header =====
28183 <HTML>
28184 <HEAD>
28185 <TITLE>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></TITLE>
28186 </HEAD>
28187 <BODY>
28188 <H1>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></H1>
28190 This feature controls an aspect of Alpine's Reply command. If set, and the
28191 original message is being included in the reply, then headers from that
28192 message will also be part of the reply.
28193 <P>
28194 <End of help on this topic>
28195 </HEAD>
28196 </HTML>
28197 ====== h_config_sig_at_bottom =====
28198 <HTML>
28199 <HEAD>
28200 <TITLE>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></TITLE>
28201 </HEAD>
28202 <BODY>
28203 <H1>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></H1>
28205 This feature controls an aspect of Alpine's Reply command. If this feature
28206 is set, and the original message is being included in the reply, then the
28207 contents of your signature file (if any) will be inserted after the included
28208 message.
28209 <P>
28210 This feature does not affect the results of a Forward command.
28211 <P>
28212 <End of help on this topic>
28213 </BODY>
28214 </HTML>
28215 ====== h_config_sigdashes =====
28216 <HTML>
28217 <HEAD>
28218 <TITLE>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></TITLE>
28219 </HEAD>
28220 <BODY>
28221 <H1>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></H1>
28223 This feature enables support for the common USENET news convention
28224 of preceding a message signature with the special line consisting of
28225 the three characters "-- " (i.e., dash, dash, and space).
28227 <P>
28228 When enabled and a
28229 "<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>" exists,
28230 Alpine will insert the special line before including the file's text (unless
28231 the special line already exists somewhere in the file's text).
28233 <P>
28234 In addition, when you Reply or Followup to a message containing one of
28235 these special lines and choose to include its text, Alpine will observe
28236 the convention of not including text beyond the special line in your
28237 reply.
28238 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
28239 mode is enabled and turned on, then Alpine <EM>will</EM>
28240 include the text beyond the special line regardless of the setting of
28241 this feature.
28243 <P>
28244 See also "<a href="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>"
28245 for a related feature.
28247 <P>
28248 <UL>
28249 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28250 </UL><P>
28251 <End of help on this topic>
28252 </BODY>
28253 </HTML>
28254 ====== h_config_new_thread_blank_subject =====
28255 <HTML>
28256 <HEAD>
28257 <TITLE>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></TITLE>
28258 </HEAD>
28259 <BODY>
28260 <H1>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></H1>
28262 When this feature is enabled (the default) Alpine will create a new thread
28263 every time that the subject line becomes empty at any time during composition.
28265 <P>
28266 This behavior is particularly useful in case you are replying to a message.
28267 Replying to a message causes the message to be in the same thread than the
28268 original message that is being replied to. However, many authors want to create
28269 a new message (in a different thread) while replying to a message, and they do
28270 this by changing the full subject, by first deleting the original subject and
28271 typing the new subject of the current message.
28273 <P>
28274 Enabling this feature causes that any time that the subject is deleted, the
28275 message being composed will be considered the first message of a new thread.
28277 <P>
28278 <UL>
28279 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28280 </UL><P>
28281 <End of help on this topic>
28282 </BODY>
28283 </HTML>
28284 ====== h_config_strip_sigdashes =====
28285 <HTML>
28286 <HEAD>
28287 <TITLE>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></TITLE>
28288 </HEAD>
28289 <BODY>
28290 <H1>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></H1>
28292 This feature doesn't do anything if the feature
28293 "<A HREF="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></A>" is turned on.
28294 However, if the "<!--#echo var="FEAT_enable-sigdashes"-->" feature is not turned on,
28295 then turning on this feature enables support for the convention
28296 of not including text beyond the sigdashes line when Replying or Following
28297 up to a message and including the text of that message.
28298 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
28299 mode is enabled and turned on, then Alpine <EM>will</EM>
28300 include the text beyond the special line regardless of the setting of
28301 this feature.
28302 <P>
28303 In other words, this is a way to turn on the signature stripping behavior
28304 without also turning on the dashes-adding behavior.
28305 <P>
28306 <UL>
28307 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28308 </UL><P>
28309 <End of help on this topic>
28310 </BODY>
28311 </HTML>
28312 ====== h_config_forward_as_attachment =====
28313 <HTML>
28314 <HEAD>
28315 <TITLE>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></TITLE>
28316 </HEAD>
28317 <BODY>
28318 <H1>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></H1>
28320 This feature affects the way forwarded message text is handled. When set, rather than
28321 include the text of the forwarded message below any additional text you provide in the
28322 composer, the forwarded message is attached in its entirety to the message you send.
28323 <P>
28324 This is useful in that it keeps the text you provide in the composer distinct from the
28325 text of the forwarded message. Similarly, it allows the recipient to
28326 conveniently operate on the forwarded message. For example, they might reply directly to
28327 the sender of the forwarded message, or process it as part of a spam report.
28328 <UL>
28329 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28330 </UL><P>
28331 <End of help on this topic>
28332 </BODY>
28333 </HTML>
28334 ====== h_config_preserve_field =====
28335 <HTML>
28336 <HEAD>
28337 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></TITLE>
28338 </HEAD>
28339 <BODY>
28340 <H1>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></H1>
28342 This feature affects Alpine's behavior when one replies to a message.
28343 When you receive a message, some or all of the recipients of the message
28344 have been added to the To: and Cc: fields. If you reply to such message,
28345 and this feature is disabled, then the original sender of the message is
28346 added to the To: field, and all other recipients are added to the Cc:
28347 field, while your address is added to the From: field.
28349 <P>
28350 However, if this feature is enabled, then Alpine will preserve the
28351 original fields as sent in the original message, so the Cc: and To:
28352 fields will be preserved. The sender's address will be added to the To:
28353 field, while your address is added to the From: field.
28355 <P>
28356 The behavior of this feature is that replies to all messages will behave
28357 in the way described above. If you only intend this to happen on a per
28358 message basis, then keep this feature disabled, and when replying to a
28359 message you will see a new option in the menu for the "Reply to all
28360 recipients?" question. In this case, pressing "p" will
28361 make Alpine toggle its question so you can preserve the To: and Cc:
28362 fields for that message only.
28364 <UL>
28365 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28366 </UL><P>
28367 <End of help on this topic>
28368 </BODY>
28369 </HTML>
28370 ====== h_config_sub_lists =====
28371 <HTML>
28372 <HEAD>
28373 <TITLE>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></TITLE>
28374 </HEAD>
28375 <BODY>
28376 <H1>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></H1>
28378 This feature affects the subcommands available when Saving,
28379 or when Opening a new folder. If set, the subcommand ^X ListMatches will be
28380 available. This command allows you to type in a substring of the folder
28381 you are looking for and when you type ^X it will display all folders
28382 that contain that substring in their names.
28383 This feature is set by default.
28385 <P>
28386 <End of help on this topic>
28387 </BODY>
28388 </HTML>
28389 ====== h_config_scramble_message_id =====
28390 <HTML>
28391 <HEAD>
28392 <TITLE>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></TITLE>
28393 </HEAD>
28394 <BODY>
28395 <H1>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></H1>
28397 Normally the Message-ID header that Alpine generates when sending a message
28398 contains the name of the computer from which the message is being sent.
28399 Some believe that this hostname could be used by spammers or could
28400 be used by others for nefarious purposes.
28401 If this feature is set, that name will be transformed with a simple
28402 Rot13 transformation.
28403 The result will still have the correct syntax for a Message-ID but the
28404 part of the MessageID that is often a domain name will not be an actual
28405 domain name because the letters will be scrambled.
28406 <P>
28407 In addition, other information such as the name program, version, and
28408 a code for operating system used to build Alpine, will be encoded using
28409 the Rot13 transformation, except for the version number which will be
28410 encoded using a Rot5 transformation.
28411 <P>
28412 It is possible (but unlikely?) that some spam detection
28413 software will use that as a reason to reject the mail as spam.
28414 It has also been reported that some spam detection software uses the
28415 fact that there are no dots after the "@" as a reason to reject
28416 messages.
28417 If your PC-Alpine Message-ID is using a name without a dot that is because
28418 that is what Windows thinks is your "Full computer name".
28419 The method used to set this varies from one type of Windows to another but
28420 check under Settings -> Control Panel -> System and
28421 look for Network Identification or Computer Name or something similar.
28422 How to set it is beyond the scope of Alpine.
28424 <P>
28425 <End of help on this topic>
28426 </BODY>
28427 </HTML>
28428 ====== h_downgrade_multipart_to_text =====
28429 <HTML>
28430 <HEAD>
28431 <TITLE>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></TITLE>
28432 </HEAD>
28433 <BODY>
28434 <H1>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></H1>
28436 <P>
28437 This feature affects Alpine's behavior when sending mail. Internet
28438 standards require Alpine to translate all non-ASCII characters in
28439 messages that it sends using MIME encoding. This encoding can be
28440 ostensibly broken for recipients if any agent between Alpine and the
28441 recipient, such as an email list expander, appends text to the
28442 message, such as list information or advertising. When sending such
28443 messages Alpine attempts to protect such encoding by placing extra
28444 MIME boundaries around the message text.
28445 <P>
28446 These extra boundaries are invisible to recipients that
28447 use MIME-aware email programs (the vast majority). However, if
28448 you correspond with users of email programs that are not MIME-aware,
28449 or do not handle the extra boundaries gracefully, you can
28450 use this feature to prevent Alpine from including the extra
28451 MIME information. Of course, it will increase the likelihood
28452 that non-ASCII text you send may appear corrupt to the recipient.
28453 <P>
28454 <End of help on this topic>
28455 </BODY>
28456 </HTML>
28457 ====== h_config_show_sort =====
28458 <HTML>
28459 <HEAD>
28460 <TITLE>FEATURE: <!--#echo var="FEAT_show-sort"--></TITLE>
28461 </HEAD>
28462 <BODY>
28463 <H1>FEATURE: <!--#echo var="FEAT_show-sort"--></H1>
28465 If this feature is set and there is sufficient space on the screen,
28466 a short indication of the current sort order will be
28467 added in the titlebar (the top line on the screen), before the name
28468 of the folder.
28469 For example, with the default Arrival sort in effect,
28470 the display would have the characters
28472 <P><CENTER>[A]</CENTER><P>
28474 added between the title of the screen and the folder name.
28475 The letters are the same as the letters you may type to manually
28476 sort a folder with the SortIndex command ($).
28477 The letters in the table below are the ones that may show
28478 up in the titlebar line.
28479 <P>
28480 <TABLE>
28481 <TR> <TD> A </TD> <TD> <EM>A</EM>rrival </TD> </TR>
28482 <TR> <TD> S </TD> <TD> <EM>S</EM>ubject </TD> </TR>
28483 <TR> <TD> F </TD> <TD> <EM>F</EM>rom </TD> </TR>
28484 <TR> <TD> T </TD> <TD> <EM>T</EM>o </TD> </TR>
28485 <TR> <TD> C </TD> <TD> <EM>C</EM>c </TD> </TR>
28486 <TR> <TD> D </TD> <TD> <EM>D</EM>ate </TD> </TR>
28487 <TR> <TD> Z </TD> <TD> si<EM>Z</EM>e </TD> </TR>
28488 <TR> <TD> O </TD> <TD> <EM>O</EM>rderedsubject </TD> </TR>
28489 <TR> <TD> E </TD> <TD> scor<EM>E</EM> </TD> </TR>
28490 <TR> <TD> H </TD> <TD> t<EM>H</EM>read </TD> </TR>
28491 </TABLE>
28492 <P>
28493 If the sort order is Reversed, the letter above will be preceded by the letter
28494 "R", for example
28496 <P><CENTER>[RS]</CENTER><P>
28498 means that a Reverse Subject sort is in effect.
28499 For the case where the sort is in Reverse Arrival order, the "A" is
28500 left out, and just an "R" is shown.
28502 <P><CENTER>[R]</CENTER>
28504 <P>
28505 <End of help on this topic>
28506 </BODY>
28507 </HTML>
28508 ====== h_config_disable_reset_disp =====
28509 <HTML>
28510 <HEAD>
28511 <TITLE>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></TITLE>
28512 </HEAD>
28513 <BODY>
28514 <H1>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></H1>
28516 UNIX Alpine only.
28517 <P>
28518 This feature affects Alpine's behavior when using
28519 <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>.
28520 Normally, before the display filter is run, the terminal mode is reset
28521 to what it was before you started Alpine.
28522 This may be necessary if the filter requires the use of the terminal.
28523 For example, it may need to interact with you.
28524 If you set this feature, then the terminal mode will not be reset.
28525 One thing that turning on this feature should fix is the coloring of
28526 <A HREF="h_config_quote_color">quoted text</A> in the message view, which
28527 breaks because the terminal reset resets the color state of the terminal.
28529 <P>
28530 <End of help on this topic>
28531 </BODY>
28532 </HTML>
28533 ====== h_config_disable_sender =====
28534 <HTML>
28535 <HEAD>
28536 <TITLE>FEATURE: <!--#echo var="FEAT_disable-sender"--></TITLE>
28537 </HEAD>
28538 <BODY>
28539 <H1>FEATURE: <!--#echo var="FEAT_disable-sender"--></H1>
28541 This feature affects Alpine's generation of the "Sender:" or
28542 <A HREF="h_config_use_sender_not_x">"X-X-Sender"</A>
28543 header fields.
28544 By default, Alpine will generate such a header in situations where the
28545 username or domain are not the same as
28546 the "From:" header on the message.
28547 With this feature set,
28548 no "Sender:" or "X-X-Sender" header will be generated.
28549 This may be desirable on a system that is virtually hosting many domains,
28550 and the sysadmin has other methods available for tracking a message to
28551 its originator.
28552 <P>
28553 See also <A HREF="h_config_allow_chg_from">"<!--#echo var="FEAT_allow-changing-from"-->"</A>.
28555 <P>
28556 <End of help on this topic>
28557 </BODY>
28558 </HTML>
28559 ====== h_config_use_sender_not_x =====
28560 <HTML>
28561 <HEAD>
28562 <TITLE>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></TITLE>
28563 </HEAD>
28564 <BODY>
28565 <H1>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></H1>
28567 Normally Alpine adds a header line
28568 labeled "X-X-Sender", if the sender is
28569 different from the From: line.
28570 The standard specifies that this header
28571 line should be labeled "Sender", not "X-X-Sender".
28572 Setting this feature causes
28573 "Sender" to be used instead of "X-X-Sender".
28574 <P>
28575 See also <A HREF="h_config_disable_sender">"<!--#echo var="FEAT_disable-sender"-->"</A>.
28577 <P>
28578 <End of help on this topic>
28579 </BODY>
28580 </HTML>
28581 ====== h_config_use_fk =====
28582 <HTML>
28583 <HEAD>
28584 <TITLE>FEATURE: <!--#echo var="FEAT_use-function-keys"--></TITLE>
28585 </HEAD>
28586 <BODY>
28587 <H1>FEATURE: <!--#echo var="FEAT_use-function-keys"--></H1>
28589 This feature specifies that Alpine will respond to function keys instead of
28590 the normal single-letter commands. In this mode, the key menus at the
28591 bottom of each screen will show function key designations instead of the
28592 normal mnemonic key.
28594 <P>
28595 <End of help on this topic>
28596 </BODY>
28597 </HTML>
28598 ====== h_config_cancel_confirm =====
28599 <HTML>
28600 <HEAD>
28601 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></TITLE>
28602 </HEAD>
28603 <BODY>
28604 <H1>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></H1>
28606 This feature affects what happens when you type ^C to cancel a composition.
28607 By default, if you attempt to cancel a composition by typing ^C, you will be
28608 asked to confirm the cancellation by typing a "C"
28609 for <EM>C</EM>onfirm.
28610 It logically ought to be a "Y" for <EM>Y</EM>es, but that is
28611 risky because the "^C Y" needed to cancel a message
28612 is close (on the keyboard) to the "^X Y" needed to send a message.
28613 <P>
28614 If this feature is set the confirmation asked for
28615 will be a "<EM>Y</EM>es"
28616 instead of a "<EM>C</EM>onfirm" response.
28618 <P>
28619 <End of help on this topic>
28620 </BODY>
28621 </HTML>
28622 ====== h_config_compose_maps_del =====
28623 <HTML>
28624 <HEAD>
28625 <TITLE>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></TITLE>
28626 </HEAD>
28627 <BODY>
28628 <H1>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></H1>
28630 This feature affects the behavior of the DELETE key.
28631 If set, Delete will be equivalent to ^D, and delete
28632 the current character. Normally Alpine defines the Delete key
28633 to be equivalent to ^H, which deletes the <EM>previous</EM>
28634 character.
28636 <P>
28637 <End of help on this topic>
28638 </BODY>
28639 </HTML>
28640 ====== h_config_compose_bg_post =====
28641 <HTML>
28642 <HEAD>
28643 <TITLE>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></TITLE>
28644 </HEAD>
28645 <BODY>
28646 <H1>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></H1>
28648 This feature affects the behavior of Alpine's mail sending. If set, this
28649 feature enables a subcommand in the composer's "Send?" confirmation
28650 prompt. The subcommand allows you to tell Alpine to handle the actual
28651 posting in the background. While this feature usually allows posting
28652 to appear to happen very fast, it has no affect on the actual delivery
28653 time it takes a message to arrive at its destination.
28655 <P>
28656 Please Note:
28657 <OL>
28658 <LI>This feature will have no effect if the feature
28659 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A>
28660 is set.
28661 <LI>This feature isn't supported on all systems. All DOS and Windows,
28662 as well as several Unix ports, do not recognize this feature.
28663 <LI>Error handling is significantly different when this feature is
28664 enabled. Any message posting failure results in the message
28665 being appended to your "Interrupted" mail folder. When you
28666 type the <A HREF="h_common_compose">C</A>ompose command,
28667 Alpine will notice this folder and
28668 offer to extract any messages contained. Upon continuing a
28669 failed message, Alpine will display the nature of the failure
28670 in the status message line.
28671 <LI> <EM>WARNING</EM>: Under extreme conditions, it is possible
28672 for message data to
28673 get lost. <EM>Do</EM> <EM>not</EM> enable this feature
28674 if you typically run close to any sort of disk-space limits or quotas.
28675 </OL>
28676 <P>
28677 <End of help on this topic>
28678 </BODY>
28679 </HTML>
28680 ====== h_config_compose_dsn =====
28681 <HTML>
28682 <HEAD>
28683 <TITLE>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></TITLE>
28684 </HEAD>
28685 <BODY>
28686 <H1>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></H1>
28688 This feature affects the behavior of Alpine's mail sending. If set, this
28689 feature enables a subcommand in the composer's "Send?" confirmation
28690 prompt. The subcommand allows you to tell Alpine to request the type of
28691 Delivery Status Notification (DSN) that you would like. Most users will
28692 be happy with the default, and need not enable this feature.
28693 <P>
28694 If the feature
28695 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
28696 then this feature has no effect and the type of DSN is not selectable.
28698 <P>
28699 Turning on this feature and then turning on the DSNOpts from the send
28700 prompt reveals four on-off toggles at the bottom of the screen.
28701 The "X" command toggles between NoErrRets and ErrRets. NoErrRets requests
28702 that no notification be returned to you, even if there is a delivery
28703 failure. The "D" key toggles between Delay and NoDelay. This tells the
28704 server that you are willing (or not) to receive delay notifications, which
28705 happen when there is an unusual delay at some mail server (in that mail
28706 server's opinion). The "S" key toggles between Success and NoSuccess.
28707 Success requests that you be sent a DSN message when the message is
28708 successfully delivered to the recipients mailbox. Setting NoErrRets will
28709 automatically turn off Delay and Success notification, and will flip the
28710 toggles to show that. Similarly, turning on Delay and/or Success will
28711 automatically toggle the "X" key to ErrRets. The fourth command, the
28712 "H" key, toggles between RetHdrs and RetFull. RetFull requests that
28713 the full message be returned in any failed DSN. RetHdrs requests that
28714 only the headers be returned in any failed DSN. Notice that this command
28715 applies only to failed delivery status reports. For delay or success
28716 reports, the full message is never returned, only the headers are returned.
28718 <P>
28719 If you don't enable the DSN feature or if you don't turn it on for a
28720 particular message, the default is that you will be notified about failures,
28721 you might be notified about delays, and you won't be notified about
28722 successes. You will usually receive the full message back when there is
28723 a failure.
28725 <P>
28726 If you turn on the DSNOpts the default is to return as much information as
28727 possible to you. That is, by default, the Success and Delay options are
28728 turned on and the full message will be returned on failure.
28730 <P>
28731 The sending prompt will display the current DSN request (if any) in a
28732 shorthand form. It will be:
28734 <P><CENTER>[Never]</CENTER>
28736 <P>
28737 if you have requested NoErrRets. Otherwise, it will look something like:
28739 <P><CENTER>[FDS-Hdrs]</CENTER>
28741 <P>
28742 The "F" will always be there, indicating that you will be notified
28743 of failures. (Alpine doesn't provide a way to request no failure notification
28744 and at the same time request either success or delay notification. The only
28745 way to request no failure notifications is to request no notifications at
28746 all with NoErrRets.) The "D" and/or "S" will be present if you have
28747 requested Delay and/or Success notification. If one of those is missing,
28748 that means you are requesting no notification of the corresponding type.
28749 After the dash it will say either Hdrs or Full. Hdrs means to return only
28750 the headers and Full means to return the full message (applies to
28751 failure notifications only).
28753 <P>
28754 NOTE: This feature relies on your system's mail transport agent or
28755 configured
28756 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
28757 having the negotiation mechanism introduced in
28758 "Extended SMTP" (ESMTP) and the specific extension called
28759 "Delivery Status Notification" (DSN). If the mail tranport agent you
28760 are using doesn't support DSN, a short warning will be shown to you on
28761 the message line at the bottom of the screen after you send your message,
28762 but your message will have been sent anyway.
28764 <P>
28765 Note that DSNs don't provide a mechanism to request read receipts. That
28766 is, if you request notification on success you are notified when the
28767 message is delivered to the mailbox, not when the message is read.
28769 <P>
28770 ESMTP allows for graceful migration to upgraded mail transfer agents, but
28771 it is possible that this feature might cause problems for some servers.
28773 <P>
28774 <End of help on this topic>
28775 </BODY>
28776 </HTML>
28777 ====== h_config_auto_zoom =====
28778 <HTML>
28779 <HEAD>
28780 <TITLE>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></TITLE>
28781 </HEAD>
28782 <BODY>
28783 <H1>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></H1>
28785 This feature affects the behavior of the Select command.
28786 If set, the select command will automatically perform a zoom
28787 after the select is complete.
28788 This feature is set by default.
28789 <P>
28790 Some related help topics are
28791 <UL>
28792 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28793 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28794 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28795 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
28796 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
28797 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28798 </UL>
28800 <P>
28801 <End of help on this topic>
28802 </BODY>
28803 </HTML>
28804 ====== h_config_auto_unzoom =====
28805 <HTML>
28806 <HEAD>
28807 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></TITLE>
28808 </HEAD>
28809 <BODY>
28810 <H1>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></H1>
28812 This feature affects the behavior of the Apply command. If set, and if
28813 you are currently looking at a Zoomed Index view of selected messages,
28814 the Apply command will do the operation you specify, but then will
28815 implicitly do an "UnZoom", so that you will automatically be back in
28816 the normal Index view after the Apply.
28817 This feature is set by default.
28819 <P>
28820 Some related help topics are
28821 <UL>
28822 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28823 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28824 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28825 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
28826 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
28827 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28828 </UL>
28829 <P>
28830 <End of help on this topic>
28831 </BODY>
28832 </HTML>
28833 ====== h_config_auto_unselect =====
28834 <HTML>
28835 <HEAD>
28836 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></TITLE>
28837 </HEAD>
28838 <BODY>
28839 <H1>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></H1>
28841 This feature affects the behavior of the Apply command. If set,
28842 the Apply command will do the operation you specify, but then will
28843 implicitly do an "UnSelect All", so that you will automatically be back in
28844 the normal Index view after the Apply.
28846 <P>
28847 Some related help topics are
28848 <UL>
28849 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28850 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28851 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28852 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
28853 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
28854 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28855 </UL>
28856 <P>
28857 <End of help on this topic>
28858 </BODY>
28859 </HTML>
28860 ====== h_config_fast_recent =====
28861 <HTML>
28862 <HEAD>
28863 <TITLE>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></TITLE>
28864 </HEAD>
28865 <BODY>
28866 <H1>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></H1>
28868 This feature controls the behavior of the TAB key when traversing folders
28869 in the optional
28870 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28871 collection or in optional <!--#echo var="VAR_news-collections"-->.
28873 <P>
28874 When the TAB
28875 (<A HREF="h_common_nextnew">NextNew</A>)
28876 key is pressed, the default behavior is to
28877 explicitly examine the status of the folder for the number of recent
28878 messages (messages delivered since the last time it was viewed).
28879 Depending on the size and number of messages in the folder, this test
28880 can be time consuming.
28882 <P>
28883 Enabling this feature will cause Alpine to only test for the existence of
28884 any recent messages rather than to obtain the count. This is much faster
28885 in many cases. The downside is that you're not given the number of recent
28886 messages when prompted to view the next folder.
28887 If the feature
28888 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
28889 is turned on, then the present feature will have no effect.
28891 <P>
28892 <UL>
28893 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28894 </UL><P>
28895 <End of help on this topic>
28896 </BODY>
28897 </HTML>
28898 ====== h_config_arrow_nav =====
28899 <HTML>
28900 <HEAD>
28901 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></TITLE>
28902 </HEAD>
28903 <BODY>
28904 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></H1>
28906 This feature controls the behavior of the left and right arrow keys.
28907 If set, the left and right arrow keys will operate like the usual
28908 navigation keys < and >.
28909 This feature is set by default.
28911 <P>
28912 If you set this feature, and do not like the changed behavior of the up/down
28913 arrow
28914 keys when navigating through the FOLDER LIST screen --
28915 <B>first</B> from column to column, if more than one folder is
28916 displayed per row,
28917 and <B>then</B> from row to row -- you may either also wish to set the feature
28918 "<A HREF="h_config_relaxed_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></A>",
28919 "<A HREF="h_config_single_list"><!--#echo var="FEAT_single-column-folder-list"--></A>", or
28920 use the ^P/^N (instead of up/down arrow) keys to move up/down the list of
28921 folders in each column.
28922 <P>
28923 <UL>
28924 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28925 </UL><P>
28926 <End of help on this topic>
28927 </BODY>
28928 </HTML>
28929 ====== h_config_relaxed_arrow_nav =====
28930 <HTML>
28931 <HEAD>
28932 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></TITLE>
28933 </HEAD>
28934 <BODY>
28935 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></H1>
28937 This feature controls the behavior of the left, right, up and down
28938 arrow keys in the FOLDER LIST screen when the "<A
28939 HREF="h_config_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation"--></A>" feature is
28940 set.
28941 This feature is set by default.
28943 <P>
28945 When this feature is set, the left and right
28946 arrow keys in the FOLDER LIST screen
28947 move the highlight bar to the left or right, and the up and
28948 down arrows move it up or down.
28950 <P>
28951 When the "<!--#echo var="FEAT_enable-arrow-navigation"-->" feature is set and this
28952 feature is not set;
28953 the left and right arrow keys in the Folder List screen strictly
28954 track the commands bound to the '<' and '>' keys, and the up
28955 and down arrow keys move the highlight bar to the previous and next
28956 folder or directory name.
28958 <P>
28959 <UL>
28960 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28961 </UL><P>
28962 <End of help on this topic>
28963 </BODY>
28964 </HTML>
28965 ====== h_config_alt_compose_menu =====
28966 <HTML>
28967 <HEAD>
28968 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></TITLE>
28969 </HEAD>
28970 <BODY>
28971 <H1>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></H1>
28973 This feature controls the menu that is displayed when Compose is selected.
28974 If set, a list of options will be presented, with each option representing
28975 the type of composition that could be used. This feature is most useful for
28976 users who want to avoid being prompted with each option separately, or who
28977 want to avoid the checking of remote postponed or form letter folders.
28978 The possible types of composition are:
28980 <P>
28981 New, for starting a new composition. Note that if New is selected and roles
28982 are set, roles are checked for matches and applied according to the setting
28983 of the matching role.
28985 <P>
28986 Interrupted, for continuing an interrupted composition. This option is only
28987 offered if an interrupted message folder is detected.
28989 <P>
28990 Postponed, for continuing postponed compositions. This option is offered
28991 if a <!--#echo var="VAR_postponed-folder"--> is set in the config REGARDLESS OF whether or not
28992 the postponed folder actually exists. This option is especially handy
28993 for avoiding having to check for the existence of a remote postponed folder.
28995 <P>
28996 Form, for using form letters. This option is offered if the <!--#echo var="VAR_form-letter-folder"-->
28997 is set in the config, and is not checked for existence for reasons similar
28998 to those explained by the postponed option.
29000 <P>
29001 setRole, for selecting a role to apply to a composition.
29003 <P>
29004 <End of help on this topic>
29005 </BODY>
29006 </HTML>
29007 ====== h_config_alt_role_menu =====
29008 <HTML>
29009 <HEAD>
29010 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></TITLE>
29011 </HEAD>
29012 <BODY>
29013 <H1>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></H1>
29015 Normally the <A HREF="h_common_role">Role Command</A> allows you to choose
29016 a role and compose a new message using that role.
29017 When this feature is set, the role command will first ask whether you want to
29018 Compose a new message, Forward the current message, Reply to the
29019 current message, or Bounce the current message.
29020 If you are not in the MESSAGE INDEX and are not viewing a message,
29021 then there is no current message and the question will be skipped.
29022 After you have chosen to Compose, Forward, Reply, or Bounce you will
29023 then choose the role to be used.
29024 <P>
29025 When Bouncing the "Set From" address is used for the
29026 Resent-From header, the "Set Fcc" value is used for the Fcc
29027 provided that the option
29028 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A> is turned on,
29029 and the "Use SMTP Server" value is used for the SMTP server, if
29030 set.
29031 Other actions of the role are ignored when Bouncing.
29033 <P>
29034 <End of help on this topic>
29035 </BODY>
29036 </HTML>
29037 ====== h_config_always_spell_check =====
29038 <HTML>
29039 <HEAD>
29040 <TITLE>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></TITLE>
29041 </HEAD>
29042 <BODY>
29043 <H1>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></H1>
29044 <P>
29045 When this feature is set, every composed message will be spell-checked before
29046 being sent.
29047 <P>
29048 <End of help on this topic>
29049 </BODY>
29050 </HTML>
29051 ====== h_config_quell_asterisks =====
29052 <HTML>
29053 <HEAD>
29054 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></TITLE>
29055 </HEAD>
29056 <BODY>
29057 <H1>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></H1>
29058 <P>
29059 When you are running Alpine you will sometimes be asked for a password
29060 in a prompt on the third line from the bottom of the screen.
29061 Normally each password character you type will cause an asterisk to echo
29062 on the screen. That gives you some feedback to know that your typing is
29063 being recognized.
29064 There is a very slight security risk in doing it this way because someone
29065 watching over your shoulder might be able to see how many characters there
29066 are in your password.
29067 If you'd like to suppress the echoing of the asterisks set this feature.
29068 <P>
29069 <End of help on this topic>
29070 </BODY>
29071 </HTML>
29072 ====== h_config_quell_flowed_text =====
29073 <HTML>
29074 <HEAD>
29075 <TITLE>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></TITLE>
29076 </HEAD>
29077 <BODY>
29078 <H1>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></H1>
29079 <P>
29080 Alpine generates flowed text where possible.
29081 The method for generating flowed text is defined by
29082 <A HREF="http://www.ietf.org/rfc/rfc3676.txt">RFC 3676</A>,
29083 the benefit of doing so is
29084 to send message text that can properly be viewed both on normal width displays
29085 and on displays with smaller or larger than normal screen widths.
29086 With flowed text, a space at the end of a line tells the receiving mail
29087 client that the following line belongs to the same paragraph.
29088 Quoted text will also be affected, with only the innermost
29089 level of ">" quoting being followed by a space.
29090 However, if you have changed the
29091 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29092 so that it is not equal to the default value of "> ", then
29093 quoted text will not be flowed.
29094 For this reason, we recommend that you leave your
29095 "<!--#echo var="VAR_reply-indent-string"-->" set to the default.
29096 <P>
29097 This feature turns off the generation of flowed text, as it might be
29098 desired to more tightly control how a message is displayed on the receiving end.
29099 <P>
29100 If this feature is <EM>not</EM> set, you can control on a message by message
29101 basis whether or not flowed text is generated.
29102 You do this by typing ^V at the Send confirmation prompt that you get
29103 after typing ^X to send a message.
29104 ^V is a toggle that turns flowing off and back on if typed again.
29105 If for some reason flowing cannot be done on a particular message, then the
29106 ^V command will not be available.
29107 This would be the case, for example, if this feature was set, or if your
29108 "<!--#echo var="VAR_reply-indent-string"-->" was set to a non-default value.
29109 If the feature
29110 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
29111 then the opportunity to control on a message by message basis
29112 whether or not flowed text is generated is lost.
29113 <P>
29114 When this feature is not set and you have typed ^V to turn off flowing,
29115 the Send confirmation prompt will change to look like
29116 <P>
29117 <CENTER><SAMP>Send message (not flowed)?</SAMP></CENTER>
29118 <P>
29119 <A HREF="h_config_strip_ws_before_send">"<!--#echo var="FEAT_strip-whitespace-before-send"-->"</A> will
29120 also turn off the sending of flowed text messages, but it differs in that
29121 it also trims all trailing white space from a message before sending it.
29122 <P>
29123 If alternate editors are used extensively, be aware that a message will still
29124 be sent flowed if this feature is unset. In most cases this will be fine,
29125 but if the editor has a "flowed text" mode, it would be best to
29126 use that.
29127 <P>
29128 <End of help on this topic>
29129 </BODY>
29130 </HTML>
29131 ====== h_config_strip_ws_before_send =====
29132 <HTML>
29133 <HEAD>
29134 <TITLE>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></TITLE>
29135 </HEAD>
29136 <BODY>
29137 <H1>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></H1>
29138 <P>
29139 By default, trailing whitespace is not stripped from
29140 a message before sending. Trailing whitespace should have no effect on an
29141 email message, and in flowed text can aid in delimiting paragraphs.
29142 However, the old behavior of stripping trailing whitespace was in place
29143 to better deal with older clients that couldn't handle certain types of
29144 text encodings. This feature restores the old behavior
29145 <P>
29146 Trailing whitespace is of aid to flowed-text-formatted messages, which are
29147 generated by default but can be turned off via the
29148 <A HREF="h_config_quell_flowed_text">"<!--#echo var="FEAT_quell-flowed-text"-->"</A> feature.
29149 <!--#echo var="FEAT_strip-whitespace-before-send"--> also has the effect of turning off sending
29150 of flowed text.
29151 <P>
29152 <End of help on this topic>
29153 </BODY>
29154 </HTML>
29155 ====== h_config_del_from_dot =====
29156 <HTML>
29157 <HEAD>
29158 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></TITLE>
29159 </HEAD>
29160 <BODY>
29161 <H1>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></H1>
29163 This feature controls the behavior of the Ctrl-K command in the composer.
29164 If set, ^K will cut from the current cursor position to the end of the line,
29165 rather than cutting the entire line.
29167 <P>
29168 <End of help on this topic>
29169 </BODY>
29170 </HTML>
29171 ====== h_config_print_index =====
29172 <HTML>
29173 <HEAD>
29174 <TITLE>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></TITLE>
29175 </HEAD>
29176 <BODY>
29177 <H1>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></H1>
29179 This feature controls the behavior of the Print command when in the
29180 MESSAGE INDEX screen. If set, the print command will give you a prompt
29181 asking if you wish to print the message index, or the currently highlighted
29182 message. If not set, the message will be printed.
29184 <P>
29185 <End of help on this topic>
29186 </BODY>
29187 </HTML>
29188 ====== h_config_allow_talk =====
29189 <HTML>
29190 <HEAD>
29191 <TITLE>FEATURE: <!--#echo var="FEAT_allow-talk"--></TITLE>
29192 </HEAD>
29193 <BODY>
29194 <H1>FEATURE: <!--#echo var="FEAT_allow-talk"--></H1>
29196 UNIX Alpine only.
29197 <P>
29198 By default, permission for others to "talk" to your terminal is turned
29199 off when you are running Alpine. When this feature is set, permission is
29200 instead turned on. If enabled, you may see unexpected messages in the
29201 middle of your Alpine screen from someone attempting to contact you via the
29202 "talk" program.
29204 <P>
29205 NOTE: The "talk" program has nothing to do with Alpine or email. The
29206 talk daemon on your system will attempt to print a message on your screen
29207 when someone else is trying to contact you. If you wish to see these
29208 messages while you are running Alpine, you should enable this feature.
29210 <P>
29211 If you do enable this feature and see a "talk" message, you must
29212 suspend or quit Alpine before you can respond.
29214 <P>
29215 <End of help on this topic>
29216 </BODY>
29217 </HTML>
29218 ====== h_config_send_filter_dflt =====
29219 <HTML>
29220 <HEAD>
29221 <TITLE>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></TITLE>
29222 </HEAD>
29223 <BODY>
29224 <H1>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></H1>
29225 If you have <A HREF="h_config_sending_filter">"<!--#echo var="VAR_sending-filters"-->"</A>
29226 configured, setting this feature will cause
29227 the first filter in the <!--#echo var="VAR_sending-filters"--> list to be offered as the default
29228 instead of unfiltered, the usual default.
29229 <P>
29230 <UL>
29231 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29232 </UL><P>
29233 <End of help on this topic>
29234 </BODY>
29235 </HTML>
29236 ====== h_config_custom_print =====
29237 <HTML>
29238 <HEAD>
29239 <TITLE>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></TITLE>
29240 </HEAD>
29241 <BODY>
29242 <H1>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></H1>
29244 When this feature is set, the print command will have an additional
29245 subcommand called "C CustomPrint". If selected, you will have
29246 the opportunity to enter any system print command --instead of being
29247 restricted to using those that have been previously configured in the
29248 printer setup menu.
29249 <P>
29251 <End of help on this topic>
29252 </BODY>
29253 </HTML>
29254 ====== h_config_enable_dot_files =====
29255 <HTML>
29256 <HEAD>
29257 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></TITLE>
29258 </HEAD>
29259 <BODY>
29260 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></H1>
29262 When this feature is set, files beginning with dot (".") will be
29263 visible in the file browser. For example, you'll be able to select them
29264 when using the browser to add an attachment to a message.
29265 <P>
29266 <End of help on this topic>
29267 </BODY>
29268 </HTML>
29269 ====== h_config_enable_dot_folders =====
29270 <HTML>
29271 <HEAD>
29272 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></TITLE>
29273 </HEAD>
29274 <BODY>
29275 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></H1>
29277 When this feature is set, folders beginning with dot (".") may be added
29278 and viewed.
29279 <P>
29280 <End of help on this topic>
29281 </BODY>
29282 </HTML>
29283 ====== h_config_ff_between_msgs =====
29284 <HTML>
29285 <HEAD>
29286 <TITLE>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></TITLE>
29287 </HEAD>
29288 <BODY>
29289 <H1>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></H1>
29291 Setting this feature causes a formfeed to be printed between messages when
29292 printing multiple messages (with Apply Print command).
29293 <P>
29294 <End of help on this topic>
29295 </BODY>
29296 </HTML>
29297 ====== h_config_blank_keymenu =====
29298 <HTML>
29299 <HEAD>
29300 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></TITLE>
29301 </HEAD>
29302 <BODY>
29303 <H1>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></H1>
29305 If this feature is set the command key menu that normally appears on the
29306 bottom two lines of the screen will not usually be there. Asking for
29307 help with ^G or ? will cause the key menu to appear instead of causing
29308 the help message to come up. If you want to actually see the help text,
29309 another ^G or ? will show it to you. After the key menu has popped
29310 up with the help key it will remain there for an O for Other command but
29311 disappear if any other command is typed.
29312 <P>
29313 <End of help on this topic>
29314 </BODY>
29315 </HTML>
29316 ====== h_config_enable_mouse =====
29317 <HTML>
29318 <HEAD>
29319 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></TITLE>
29320 </HEAD>
29321 <BODY>
29322 <H1>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></H1>
29324 This feature controls whether or not an X terminal mouse can be used with
29325 Alpine. If set, and the $DISPLAY variable indicates that an X terminal is
29326 being used, the left mouse button on the mouse can be used to select text
29327 or commands.
29328 Clicking on a command at the bottom of the screen will behave as if you had
29329 typed that command.
29330 Clicking on an index line will move the current message highlight to
29331 that line.
29332 Double-clicking on an index line will view the message.
29333 Double-clicking on a link will view the link.
29334 <P>
29335 This type of mouse support will also work in some terminal emulators which are
29336 not actually X terminals, but which have extra code to support the xterm
29337 style mouse.
29338 For those emulators you not only need to turn this feature on but you also
29339 have to set the $DISPLAY environment variable even though it isn't needed
29340 for your terminal.
29341 That will cause Alpine to think that it is an xterm and to properly interpret the
29342 escape sequences sent by the mouse.
29343 <P>
29344 Note: if this feature is set, the behavior of X terminal cut-and-paste is
29345 also modified. It is sometimes possible to hold the shift key down while clicking
29346 left or middle mouse buttons for the normal xterm cut/paste operations.
29347 There is also an Alpine command to toggle this mode on or off.
29348 The command is Ctrl-\ (Control-backslash).
29349 <P>
29350 <End of help on this topic>
29351 </BODY>
29352 </HTML>
29353 ====== h_config_enable_xterm_newmail =====
29354 <HTML>
29355 <HEAD>
29356 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></TITLE>
29357 </HEAD>
29358 <BODY>
29359 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></H1>
29361 This feature controls whether or not Alpine will attempt to announce new
29362 mail arrival when it is running in an X terminal window and that window
29363 is iconified. If set, and the $DISPLAY variable indicates that an X
29364 terminal is being used, Alpine will send appropriate escape sequences to
29365 the X terminal to modify the label on Alpine's icon to indicate that new
29366 mail has arrived. Alpine will also modify the Alpine window's title to
29367 indicate new mail.
29368 See also <a href="h_config_enable_newmail_short_text"><!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>.
29369 <P>
29370 <End of help on this topic>
29371 </BODY></HTML>
29372 ====== h_config_enable_newmail_short_text =====
29373 <HTML>
29374 <HEAD>
29375 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></TITLE>
29376 </HEAD>
29377 <BODY>
29378 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></H1>
29380 This feature controls the text to be displayed in an icon in the event
29381 of a new message arrival. Normally, the message will
29382 be the one that is displayed on the screen. This feature shortens the
29383 message to a count of the number of new messages in brackets. This may be
29384 more useful for those who use the window's title bar in the task bar as a
29385 new mail indicator. This feature is only useful if the
29386 <A HREF="h_config_enable_xterm_newmail"><!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></A>
29387 feature is also set. Like the <!--#echo var="FEAT_enable-newmail-in-xterm-icon"-->
29388 feature, this feature is only relevant when run in an xterm environment.
29389 <P>
29390 <End of help on this topic>
29391 </BODY></HTML>
29392 ====== h_config_copy_to_to_from =====
29393 <HTML>
29394 <HEAD>
29395 <TITLE>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></TITLE>
29396 </HEAD>
29397 <BODY>
29398 <H1>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></H1>
29400 This feature affects the From address used when Replying to a message.
29401 It is probably only useful if you have some
29402 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
29403 defined.
29404 When enabled, it checks to see if any of the addresses in the To or Cc
29405 fields of the message you are replying to is one of your addresses.
29406 If it is, and there is only one of them, then that address is used as
29407 the From address in the message you are composing.
29408 In other words, you will be using a From address that is the same
29409 as the To address that was used to get the mail to you in the first place.
29411 <P>
29412 If a role is being used and it has a From address defined, that From address will
29413 be used rather than the one derived from this feature.
29415 <P>
29416 <UL>
29417 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29418 </UL><P>
29419 <End of help on this topic>
29420 </BODY>
29421 </HTML>
29422 ====== h_config_prefix_editing =====
29423 <HTML>
29424 <HEAD>
29425 <TITLE>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></TITLE>
29426 </HEAD>
29427 <BODY>
29428 <H1>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></H1>
29430 This feature affects the Reply command's "Include original message
29431 in Reply?" prompt. When enabled, it causes the
29432 "Edit Indent String" sub-command to appear which allows
29433 you to edit the string Alpine would otherwise use to denote included
29434 text from the message being replied to.<P>
29436 Thus, you can change Alpine's default message quote character (usually
29437 an angle bracket) on a per message basis. So you could change your quoted message to
29438 look, for example, like this:<p>
29440 <pre>On Tues, 26 Jan 1999, John Q. Smith wrote:
29442 John: I just wanted to say hello and to congratulate you
29443 John: on a job well done!</pre><p>
29445 The configuration option
29446 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29447 may be used to change what appears as the default string to be edited.
29448 <P>
29449 NOTE: Edited <!--#echo var="VAR_reply-indent-string"--> only apply to the message
29450 currently being replied to.
29451 <P>
29452 If you change your <!--#echo var="VAR_reply-indent-string"-->
29453 so that it is not equal to the default value of "> ", then
29454 quoted text will not be flowed
29455 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
29456 when you reply.
29457 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
29458 set to the default value.
29459 <P>
29460 <UL>
29461 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29462 </UL><P>
29463 <End of help on this topic>
29464 </BODY>
29465 </HTML>
29466 ====== h_config_enable_search_and_repl =====
29467 <HTML>
29468 <HEAD>
29469 <TITLE>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></TITLE>
29470 </HEAD>
29471 <BODY>
29472 <H1>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></H1>
29474 This feature modifies the behavior of Alpine's composer. Setting this
29475 feature causes Alpine to offer the "^R Replace" subcommand, which
29476 allows you to search and replace text strings in a message you are composing,
29477 inside the "^W Where is" command.
29479 <P>
29481 To search and replace text, first enter the text to be replaced at the
29482 "Search: " prompt. Then, rather than pressing Enter to just search for that
29483 text, press ^R, which turns the prompt into
29485 <P>
29487 Search (to replace):
29489 <P>
29491 and then press Enter. The cursor will highlight the first occurrence
29492 of the text string you entered, and the prompt will show:
29494 <P>
29496 Replace "<your text string>" with :
29498 <P>
29500 where <your text string> is what you entered at the previous prompt;
29501 here, enter the replacement text. To only replace the highlighted
29502 occurrence, simply press Enter now; to replace all occurrences in the
29503 message, press ^X (Repl All), then Enter. You will then be asked to confirm
29504 each replacement.
29506 <P>
29508 The command ^R toggles between "Replace" and "Don't Replace"; its subcommand
29509 ^X toggles between "Replace All" and "Replace One."
29511 <P>
29513 If you previously searched for text in a message, it will be offered for
29514 re-use as part of the prompt, shown in [ ] brackets.
29516 <P>
29517 <End of help on this topic>
29518 </BODY>
29519 </HTML>
29520 ====== h_config_enable_view_attach =====
29521 <HTML>
29522 <HEAD>
29523 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></TITLE>
29524 </HEAD>
29525 <BODY>
29526 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></H1>
29528 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29529 Setting this feature causes Alpine to present attachments in boldface.
29530 The first available attachment is displayed in inverse. This is the
29531 "selected" attachment. Pressing RETURN will cause Alpine to display
29532 the selected attachment. Use the arrow keys to change which of the
29533 attachments displayed in boldface is the current selection.
29535 <P>
29537 Speaking of arrow keys, the Up and Down Arrows will select the next
29538 and previous attachments if one is available on the screen for selection.
29539 Otherwise, they will simply adjust the viewed text one line up or down.
29541 <P>
29543 Similarly, when selectable items are present in a message, the Ctrl-F key
29544 can be used to select the next item in the message independent of which
29545 portion of the viewed message is currently displayed. The Ctrl-B key can
29546 be used to select the previous item in the same way.
29547 <P>
29548 <End of help on this topic>
29549 </BODY>
29550 </HTML>
29551 ====== h_config_enable_y_print =====
29552 <HTML>
29553 <HEAD>
29554 <TITLE>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></TITLE>
29555 </HEAD>
29556 <BODY>
29557 <H1>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></H1>
29559 This feature modifies the behavior of Alpine's Print command.
29560 <P>
29561 By default, Alpine's print command is available by pressing the "%" key.
29562 (This command is a substantial change from Pine versions before 4.00 --
29563 where the print command was "Y" -- based on numerous complaints about
29564 printing being invoked inadvertently, since Y also means "Yes.")
29566 <P>
29568 This feature is supplied to mitigate any disruption or anxiety users
29569 might feel as a result of this change.
29571 <P>
29573 Enabling this feature will cause Alpine to recognize both the old
29574 command, "Y" for Prynt, as well the new "%" method for invoking
29575 printing. Note, key menu labels are not changed as a result of
29576 enabling this feature.
29578 <P>
29580 <End of help on this topic>
29581 </BODY>
29582 </HTML>
29583 ====== h_config_enable_lessthan_exit =====
29584 <HTML>
29585 <HEAD>
29586 <TITLE>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></TITLE>
29587 </HEAD>
29588 <BODY>
29589 <H1>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></H1>
29591 If this feature is set, then on screens where there is an Exit command
29592 but no < command, the < key will perform the same function as the Exit
29593 command.
29594 This feature is set by default.
29595 <P>
29596 <End of help on this topic>
29597 </BODY>
29598 </HTML>
29599 ====== h_config_enable_view_url =====
29600 <HTML>
29601 <HEAD>
29602 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></TITLE>
29603 </HEAD>
29604 <BODY>
29605 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></H1>
29606 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29607 When this feature is set (the default) Alpine will select possible URLs from the
29608 displayed text and display them in boldface for selection.
29609 <P>
29610 The first available URL is displayed in inverse. This is the
29611 "selected" URL. Pressing RETURN will cause Alpine to display
29612 the selected URL via either built-in means as with mailto:, imap:,
29613 news:, and nntp:, or via an external application as defined
29614 by the <A HREF="h_config_browser">"url-viewer"</A>
29615 variable.
29616 <P>
29617 Use the arrow keys to change which of the URLs displayed in boldface
29618 is the current selection.
29619 <P>
29620 Speaking of arrow keys, the Up and Down Arrows will select the next
29621 and previous URL if one is available on the screen for selection (unless
29622 you have set the feature
29623 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
29624 Otherwise, they will simply adjust the viewed text one line up or down.
29625 <P>
29626 Similarly, when selectable items are present in a message, the Ctrl-F
29627 key can be used to select the next item in the message independent
29628 of which portion of the viewed message is currently displayed. The
29629 Ctrl-B key can be used to select the previous item in the same way.
29630 <P>
29631 <UL>
29632 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29633 </UL><P>
29634 <End of help on this topic>
29635 </BODY>
29636 </HTML>
29637 ====== h_config_enable_view_web_host =====
29638 <HTML>
29639 <HEAD>
29640 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></TITLE>
29641 </HEAD>
29642 <BODY>
29643 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></H1>
29645 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29646 When this feature is set (the default) Alpine will select possible web hostnames
29647 from the displayed text and display them in boldface for selection.
29648 This can be useful when you receive messages referencing World Wide Web
29649 sites without the use of complete URLs; for example, specifying only
29650 "www.patches.freeiz.com/alpine/" (which will <B>not</B> become a
29651 selectable
29652 item by setting <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>)
29653 rather than explicitly
29654 "http://www.patches.freeiz.com/alpine/".
29655 <P>
29656 The first available hostname is displayed in inverse. This is the
29657 "selected" hostname. Pressing RETURN will cause Alpine to display
29658 the selected hostname via an external application as defined
29659 by the <A HREF="h_config_browser">"url-viewer"</A>
29660 variable.
29661 <P>
29662 Use the arrow keys (unless you have set the feature
29663 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
29664 to change which of the hostnames displayed in
29665 boldface is the current selection.
29666 <P>
29667 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
29668 key can be used to select the next web hostname in the message independent
29669 of which portion of the viewed message is currently displayed. The
29670 Ctrl-B key can be used to select the previous web hostnames in the same way.
29671 <P>
29672 <UL>
29673 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29674 </UL><P>
29675 <End of help on this topic>
29676 </BODY>
29677 </HTML>
29678 ====== h_config_enable_view_addresses =====
29679 <HTML>
29680 <HEAD>
29681 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></TITLE>
29682 </HEAD>
29683 <BODY>
29684 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></H1>
29686 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29687 Setting this feature causes Alpine to select possible email addresses
29688 from the displayed text and display them in boldface for selection.
29690 <P>
29691 The first available email address is displayed in inverse. This is the
29692 "selected" address. Pressing RETURN will cause Alpine to enter
29693 the message composition screen with the To: field filled in with the
29694 selected address.
29695 <P>
29696 Use the arrow keys (unless you have set the feature
29697 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
29698 to change which of the hostnames displayed in
29699 boldface is the current selection.
29700 <P>
29701 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
29702 key can be used to select the next web hostname in the message independent
29703 of which portion of the viewed message is currently displayed. The
29704 Ctrl-B key can be used to select the previous web hostnames in the same way.
29705 <P>
29706 <UL>
29707 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29708 </UL><P>
29709 <End of help on this topic>
29710 </BODY>
29711 </HTML>
29712 ====== h_config_enable_view_arrows =====
29713 <HTML>
29714 <HEAD>
29715 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></TITLE>
29716 </HEAD>
29717 <BODY>
29718 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></H1>
29720 This feature modifies Up and Down arrow key behavior in Alpine's
29721 MESSAGE TEXT screen when selectable Attachments, URL's, or
29722 web-hostnames are presented. Alpine's usual behavior is to move to
29723 the next or previous selectable item if currently displayed or
29724 simply to adjust the screen view by one line.
29726 <P>
29728 Setting this feature causes the UP and Down arrow key to behave as
29729 if no selectable items were present in the message.
29731 <P>
29733 Note, the Ctrl-F (next selectable item) and Ctrl-B (previous selectable
29734 item) functionality is unchanged.
29735 <P>
29737 <End of help on this topic>
29738 </BODY>
29739 <HTML>
29740 ====== h_config_quell_charset_warning =====
29741 <HTML>
29742 <HEAD>
29743 <TITLE>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></TITLE>
29744 </HEAD>
29745 <BODY>
29746 <H1>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></H1>
29748 By default, if the message you are viewing contains characters that are
29749 not representable in your
29750 <A HREF="h_config_char_set">"Display Character Set"</A>
29751 then Alpine will
29752 add a warning to the start of the displayed text.
29753 If this option is set, then that editorial message will be suppressed.
29754 <P>
29755 Setting this feature also suppresses the comment about the character set
29756 in header lines.
29757 For example, when viewing a message you might see
29758 <P>
29759 <CENTER><SAMP>From: "[ISO-8859-2] Name" <address></SAMP></CENTER>
29760 <P>
29761 in the From header if your Character-Set is something other than ISO-8859-2.
29762 If you set this feature, the comment about the character set will
29763 no longer be there.
29764 <P>
29765 <End of help on this topic>
29766 </BODY>
29767 </HTML>
29768 ====== h_config_quell_host_after_url =====
29769 <HTML>
29770 <HEAD>
29771 <TITLE>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></TITLE>
29772 </HEAD>
29773 <BODY>
29774 <H1>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></H1>
29776 By default, links in HTML text are displayed with the host the link
29777 references appended, within square brackets, to the link text. Alpine
29778 does this to help indicate where a link will take you, particularly when
29779 the link text might suggest a different destination.
29781 <P>
29782 Setting this feature will prevent the server name from being appended
29783 to the displayed text.
29785 <P>
29786 <End of help on this topic>
29787 </BODY>
29788 </HTML>
29789 ====== h_config_prefer_plain_text =====
29790 <HTML>
29791 <HEAD>
29792 <TITLE>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></TITLE>
29793 </HEAD>
29794 <BODY>
29795 <H1>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></H1>
29797 A message being viewed may contain alternate versions of the same content.
29798 Those alternate versions are supposed to be ordered by the sending software such that the
29799 first alternative is the least preferred and the last alternative is the
29800 most preferred. Alpine will normally display the most-preferred version that
29801 it knows how to display. This is most often encountered where the two
29802 alternate versions are a plain text version and an HTML version, with the
29803 HTML version listed last as the most preferred.
29804 <P>
29805 If this option is set, then any plain text version will be preferred to
29806 all other versions.
29807 <P>
29808 When viewing a message there is a command "A TogglePreferPlain",
29809 which will temporarily change the sense of this option.
29810 If this option is set you will first see the plain text version of a
29811 message.
29812 If you then type the "A" command, you will see the most preferred version,
29813 most likely HTML, instead.
29814 Typing the "A" command a second time will switch it back.
29815 Alternatively, if the present option is not set you will originally see
29816 the most preferred version of the message and typing "A" will switch to
29817 the plain text version.
29818 <P>
29819 <End of help on this topic>
29820 </BODY>
29821 </HTML>
29822 ====== h_config_pass_control =====
29823 <HTML>
29824 <HEAD>
29825 <TITLE>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></TITLE>
29826 </HEAD>
29827 <BODY>
29828 <H1>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></H1>
29830 It is probably not useful to set this option.
29831 This is a legacy option left behind "just in case".
29832 Multi-byte characters that have an octet that has the same
29833 value as a control character are permitted through whether or not
29834 this option is turned on.
29835 <P>
29836 This feature controls how certain characters contained in messages are
29837 displayed.
29838 If set, all characters in a message will be sent to the
29839 screen. Normally, control characters are displayed as shown below to
29840 avoid a garbled screen and to
29841 avoid inadvertently changing terminal setup parameters.
29842 Control characters are usually displayed as two character sequences like
29843 <P><CENTER><SAMP> ^C </SAMP></CENTER><P>
29844 for Control-C,
29845 <P><CENTER><SAMP> ^[ </SAMP></CENTER><P>
29846 for ESCAPE,
29847 <P><CENTER><SAMP> ^? </SAMP></CENTER><P>
29848 for DELETE, and
29849 <P><CENTER><SAMP> ~E </SAMP></CENTER><P>
29850 for the character with value 133 (0x85).
29851 (The DEL character is displayed as ^?, regular control characters are displayed
29852 as the character ^ followed by the character obtained by adding the
29853 five low-order bits of the character to 0x40, and the C1
29854 control characters 0x80 - 0x9F are displayed as the character ~ followed by the
29855 character obtained by adding the
29856 five low-order bits of the character to 0x40.)
29857 Sometimes, in cases where changing a single control character into a
29858 two-character sequence would confuse Alpine's display routines,
29859 a question mark is substituted for the control character.
29860 <P>
29861 If you wish to filter out regular control characters but pass the
29862 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
29863 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.
29864 <P>
29865 <End of help on this topic>
29866 </BODY>
29867 </HTML>
29868 ====== h_config_pass_c1_control =====
29869 <HTML>
29870 <HEAD>
29871 <TITLE>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></TITLE>
29872 </HEAD>
29873 <BODY>
29874 <H1>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></H1>
29876 It is probably not useful to set this option.
29877 This is a legacy option left behind "just in case".
29878 Multi-byte characters that have an octet that has the same
29879 value as a control character are permitted through whether or not
29880 this option is turned on.
29881 <P>
29882 If the feature <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
29883 is set, then this feature has no effect.
29884 However, if you wish to filter out regular control characters but pass the
29885 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
29886 you may leave <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
29887 unset and set this feature.
29888 <P>
29889 <End of help on this topic>
29890 </BODY>
29891 </HTML>
29892 ====== h_config_fcc_on_bounce =====
29893 <HTML>
29894 <HEAD>
29895 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></TITLE>
29896 </HEAD>
29897 <BODY>
29898 <H1>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></H1>
29900 This feature controls an aspect of Alpine's behavior when bouncing a
29901 message. If set, normal FCC ("File Carbon Copy") processing will be
29902 done, just as if you had composed a message to the address you are
29903 bouncing to. If not set, no FCC of the message will be saved.
29904 <P>
29905 <End of help on this topic>
29906 </BODY>
29907 </HTML>
29908 ====== h_config_show_cursor =====
29909 <HTML>
29910 <HEAD>
29911 <TITLE>FEATURE: <!--#echo var="FEAT_show-cursor"--></TITLE>
29912 </HEAD>
29913 <BODY>
29914 <H1>FEATURE: <!--#echo var="FEAT_show-cursor"--></H1>
29916 This feature controls an aspect of Alpine's displays. If set, the system
29917 cursor will move to convenient locations in the displays. For example,
29918 to the beginning of the status field of the highlighted index line, or
29919 to the highlighted word after a successful WhereIs command. It is intended
29920 to draw your attention to an "interesting" spot on the screen.
29921 <P>
29922 <End of help on this topic>
29923 </BODY>
29924 </HTML>
29925 ====== h_config_sort_fcc_alpha =====
29926 <HTML>
29927 <HEAD>
29928 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></TITLE>
29929 </HEAD>
29930 <BODY>
29931 <H1>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></H1>
29933 This feature controls an aspect of Alpine's FOLDER LIST screen.
29934 If set, the default Fcc folder will be sorted alphabetically with the other
29935 folders instead of appearing right after the INBOX.
29936 <P>
29937 <End of help on this topic>
29938 </BODY>
29939 </HTML>
29940 ====== h_config_sort_save_alpha =====
29941 <HTML>
29942 <HEAD>
29943 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></TITLE>
29944 </HEAD>
29945 <BODY>
29946 <H1>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></H1>
29948 This feature controls an aspect of Alpine's FOLDER LIST screen.
29949 If set, the default save folder will be sorted alphabetically with the other
29950 folders instead of appearing right after the INBOX (and default FCC folder).
29951 <P>
29952 <End of help on this topic>
29953 </BODY>
29954 </HTML>
29955 ====== h_config_single_list =====
29956 <HTML>
29957 <HEAD>
29958 <TITLE>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></TITLE>
29959 </HEAD>
29960 <BODY>
29961 <H1>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></H1>
29963 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
29964 the folders will be listed one per line instead of several per line
29965 in the FOLDER LIST display.
29966 <P>
29967 <End of help on this topic>
29968 </BODY>
29969 </HTML>
29970 ====== h_config_vertical_list =====
29971 <HTML>
29972 <HEAD>
29973 <TITLE>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></TITLE>
29974 </HEAD>
29975 <BODY>
29976 <H1>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></H1>
29978 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
29979 the folders will be listed alphabetically down the columns rather
29980 than across the columns as is the default.
29981 <P>
29982 <End of help on this topic>
29983 </BODY>
29984 </HTML>
29985 ====== h_config_verbose_post =====
29986 <HTML>
29987 <HEAD>
29988 <TITLE>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></TITLE>
29989 </HEAD>
29990 <BODY>
29991 <H1>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></H1>
29992 This feature controls an aspect of Alpine's message sending. When enabled,
29993 Alpine will send a VERB (i.e., VERBose) command early in the posting process
29994 intended to cause the SMTP server to provide a more detailed account of
29995 the transaction. This feature is typically only useful to system
29996 administrators and other support personel as an aid in troublshooting
29997 problems.
29998 <P>
29999 Note, this feature relies on a specific capability of the system's mail
30000 transport agent or configured
30001 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>.
30002 It is possible that this
30003 feature will cause problems for some tranport agents, and may result in
30004 sending failure. In addition, as the verbose output comes from the mail
30005 transport agent, it is likely to vary from one system to another.
30006 <P><UL>
30007 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30008 </UL><P>
30009 <End of help on this topic>
30010 </BODY>
30011 </HTML>
30012 ====== h_config_auto_reply_to =====
30013 <HTML>
30014 <HEAD>
30015 <TITLE>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></TITLE>
30016 </HEAD>
30017 <BODY>
30018 <H1>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></H1>
30020 This feature controls an aspect of Alpine's Reply command. If set, Alpine
30021 will not prompt when a message being replied to contains a "Reply-To:"
30022 header value, but will simply use its value (as opposed to using the
30023 "From:" field's value).
30025 <P>
30027 Note: Using the "Reply-To:" address is usually the preferred behavior,
30028 however, some mailing list managers choose to place the list's address in
30029 the "Reply-To:" field of any message sent out to the list. In such
30030 cases, this feature makes it all too easy for personal replies to be
30031 inadvertently sent to the entire mail list, so be careful!
30032 <P>
30033 <End of help on this topic>
30034 </BODY>
30035 </HTML>
30036 ====== h_config_del_skips_del =====
30037 <HTML>
30038 <HEAD>
30039 <TITLE>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></TITLE>
30040 </HEAD>
30041 <BODY>
30042 <H1>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></H1>
30044 This feature controls an aspect of Alpine's Delete command. If set, this
30045 feature will cause the Delete command to advance past following messages that
30046 are marked deleted. In other words, pressing "D" will both mark the
30047 current message deleted and advance to the next message that is not marked
30048 deleted.
30049 This feature is set by default.
30050 <P>
30051 <End of help on this topic>
30052 </BODY></HTML>
30053 ====== h_config_expunge_manually =====
30054 <HTML>
30055 <HEAD>
30056 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></TITLE>
30057 </HEAD>
30058 <BODY>
30059 <H1>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></H1>
30061 Normally, when you close a folder that contains deleted messages you are
30062 asked if you want to expunge those messages from the folder permanently.
30063 If this feature is set, you won't be asked and the deleted messages will
30064 remain in the folder.
30065 If you choose to set this feature you will have to expunge the
30066 messages manually using the eXpunge command, which you can use while
30067 in the MESSAGE INDEX screen.
30068 If you do not expunge deleted messages the size of your
30069 folder will continue to increase until you are out of disk space.
30070 <P>
30071 <UL>
30072 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30073 </UL><P>
30074 <End of help on this topic>
30075 </BODY>
30076 </HTML>
30077 ====== h_config_auto_expunge =====
30078 <HTML>
30079 <HEAD>
30080 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></TITLE>
30081 </HEAD>
30082 <BODY>
30083 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></H1>
30085 This features controls an aspect of Alpine's eXpunge command. If set, you
30086 will <B>not</B> be prompted to confirm your intent before the expunge takes
30087 place.
30088 Actually, this is only true for the INBOX folder and for folders in the
30089 Incoming Folders collection. See the feature
30090 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>.
30091 <P>
30092 <UL>
30093 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30094 </UL><P>
30095 <End of help on this topic>
30096 </BODY>
30097 </HTML>
30098 ====== h_config_full_auto_expunge =====
30099 <HTML>
30100 <HEAD>
30101 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></TITLE>
30102 </HEAD>
30103 <BODY>
30104 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></H1>
30106 This features controls an aspect of Alpine's eXpunge command. If set, you
30107 will <B>not</B> be prompted to confirm your intent before the expunge
30108 takes place. This feature sets this behavior for all folders, unlike the
30109 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
30110 feature that works only for incoming folders.
30111 <P>
30112 <UL>
30113 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30114 </UL><P>
30115 <End of help on this topic>
30116 </BODY>
30117 </HTML>
30118 ====== h_config_auto_read_msgs =====
30119 <HTML>
30120 <HEAD>
30121 <TITLE>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></TITLE>
30122 </HEAD>
30123 <BODY>
30124 <H1>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></H1>
30125 This feature controls an aspect of Alpine's behavior upon quitting. If set,
30126 and the
30127 <A HREF="h_config_read_message_folder">"<!--#echo var="VAR_read-message-folder"-->"</A>
30128 option is also set, then Alpine will
30129 automatically transfer all read messages to the designated folder and mark
30130 them as deleted in the INBOX. Messages in the INBOX marked with an
30131 "N" (meaning New, or unseen) are not affected.
30132 <P>
30133 <UL>
30134 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30135 </UL><P>
30136 <End of help on this topic>
30137 </BODY>
30138 </HTML>
30139 ====== h_config_auto_fcc_only =====
30140 <HTML>
30141 <HEAD>
30142 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></TITLE>
30143 </HEAD>
30144 <BODY>
30145 <H1>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></H1>
30146 This features controls an aspect of Alpine's composer.
30147 The only time this feature will be used is if you attempt to send mail
30148 that has no recipients but does have an Fcc.
30149 Normally, Alpine will ask if you really mean to copy the message only to
30150 the Fcc.
30151 That is, it asks if you really meant to have no recipients.
30152 If this feature is set, you
30153 will <B>not</B> be prompted to confirm your intent to make only a copy
30154 of a message with no recipients.
30155 <P>
30156 This feature is closely related to
30157 <A HREF="h_config_warn_if_no_to_or_cc"><!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></A>.
30158 The difference between this feature and that feature is that this feature
30159 considers a Bcc to be a recipient while that feature will ask for confirmation
30160 even if there is a Bcc when there is no To, Cc, or Newsgroup.
30161 The default values also differ. This feature defaults to asking the question
30162 and you have to turn it off.
30163 The <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--> feature defaults to not asking
30164 unless you turn it on.
30165 <P>
30167 <UL>
30168 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30169 </UL><P>
30170 <End of help on this topic>
30171 </BODY>
30172 </HTML>
30173 ====== h_config_mark_fcc_seen =====
30174 <HTML>
30175 <HEAD>
30176 <TITLE>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></TITLE>
30177 </HEAD>
30178 <BODY>
30179 <H1>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></H1>
30181 This features controls the way Fccs (File carbon copies) are
30182 made of the messages you send.
30184 <P>
30185 Normally, when Alpine saves a copy of a message you sent as an Fcc, that
30186 copy will be marked as Unseen.
30187 When you look at the folder it was saved in the message will appear to
30188 be a New message until you read it.
30189 When this feature is enabled, the message will be marked as having
30190 been Seen.
30192 <P>
30193 <UL>
30194 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30195 </UL><P>
30196 <End of help on this topic>
30197 </BODY>
30198 </HTML>
30199 ====== h_config_no_fcc_attach =====
30200 <HTML>
30201 <HEAD>
30202 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></TITLE>
30203 </HEAD>
30204 <BODY>
30205 <H1>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></H1>
30207 This features controls the way Fcc's (File carbon copies) are
30208 made of the messages you send.
30210 <P>
30211 Normally, Alpine saves an exact copy of your message as it was sent.
30212 When this feature is enabled, the "body" of the message
30213 you send (the text you type in the composer) is preserved in the
30214 copy as before, however all attachments are replaced with text
30215 explaining what had been sent rather than the attachments themselves.
30217 <P>
30218 This feature also affects Alpine's "Send ?" confirmation prompt
30219 in that a new "^F Fcc Attchmnts" option becomes available which
30220 allows you to interactively set whether or not attachments are saved
30221 to the Fcc'd copy.
30223 <P>
30224 <UL>
30225 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30226 </UL><P>
30227 <End of help on this topic>
30228 </BODY>
30229 </HTML>
30230 ====== h_config_read_in_newsrc_order =====
30231 <HTML>
30232 <HEAD>
30233 <TITLE>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></TITLE>
30234 </HEAD>
30235 <BODY>
30236 <H1>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></H1>
30238 This feature controls the order in which newsgroups will be presented. If
30239 set, they will be presented in the same order as they occur in your
30240 <!--chtml if pinemode="os_windows"-->
30241 "NEWSRC"
30242 <!--chtml else-->
30243 ".newsrc"
30244 <!--chtml endif-->
30245 file (the default location of which can be changed with the
30246 <A HREF="h_config_newsrc_path">"<!--#echo var="VAR_newsrc-path"-->"</A> option).
30247 <P>
30248 If not set, the newsgroups will be presented in alphabetical order.
30249 <P>
30250 <UL>
30251 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30252 </UL><P>
30253 <End of help on this topic>
30254 </BODY>
30255 </HTML>
30256 ====== h_config_quell_tz_comment =====
30257 <HTML>
30258 <HEAD>
30259 <TITLE>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></TITLE>
30260 </HEAD>
30261 <BODY>
30262 <H1>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></H1>
30264 Normally, when Alpine generates a Date header for outgoing mail,
30265 it will try to include the symbolic timezone at the end of the
30266 header inside parentheses.
30267 The symbolic timezone is often three characters long, but on
30268 some operating systems, it may be longer.
30269 Apparently there are some SMTP servers in the world that will reject an
30270 incoming message if it has a Date header longer than about 80 characters.
30271 If this feature is set, the symbolic timezone normally generated by
30272 Alpine will not be included.
30273 You probably don't need to worry about this feature unless you run into
30274 the problem described above.
30276 <P>
30277 <End of help on this topic>
30278 </BODY>
30279 </HTML>
30280 ====== h_config_post_wo_validation =====
30281 <HTML>
30282 <HEAD>
30283 <TITLE>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></TITLE>
30284 </HEAD>
30285 <BODY>
30286 <H1>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></H1>
30288 This feature controls whether the NNTP server is queried as newsgroups
30289 are entered for posting. Validation over slow links (e.g. dialup using
30290 SLIP or PPP) can cause delays. Set this feature to eliminate such delays.
30291 <P>
30292 <End of help on this topic>
30293 </BODY>
30294 </HTML>
30295 ====== h_config_send_wo_confirm =====
30296 <HTML>
30297 <HEAD>
30298 <TITLE>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></TITLE>
30299 </HEAD>
30300 <BODY>
30301 <H1>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></H1>
30303 By default, when you send or post a message you will be asked to confirm
30304 with a question that looks something like:
30306 <P>
30307 <CENTER><SAMP>Send message?</SAMP></CENTER>
30308 <P>
30310 If this feature is set, you
30311 will <B>not</B> be prompted to confirm your intent to send
30312 and your message will be sent.
30313 <P>
30314 If this feature is set it disables some possibilities and renders some
30315 other features meaningless.
30316 You will not be able to use
30317 <A HREF="h_config_sending_filter">Sending Filters</A>,
30318 Verbose sending mode,
30319 <A HREF="h_config_compose_bg_post">Background Sending</A>,
30320 <A HREF="h_config_compose_dsn">Delivery Status Notifications</A>,
30321 or ^V to turn off the generation of flowed text for this message.
30322 These options are normally available as suboptions in the Send prompt, but
30323 with no Send prompt the options are gone.
30325 <P>
30326 A somewhat related feature is
30327 <A HREF="h_config_quell_post_prompt">"<!--#echo var="FEAT_quell-extra-post-prompt"-->"</A>,
30328 which may be used to eliminate the extra confirmation
30329 question when posting to a newsgroup.
30330 <P>
30331 <UL>
30332 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30333 </UL><P>
30334 <End of help on this topic>
30335 </BODY>
30336 </HTML>
30337 ====== h_config_quell_filtering_done_message =====
30338 <HTML>
30339 <HEAD>
30340 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></TITLE>
30341 </HEAD>
30342 <BODY>
30343 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></H1>
30345 If you use Filter Rules that move messages or set status of messages
30346 you sometimes see a message from Alpine that looks like
30348 <P>
30349 <CENTER><SAMP>filtering done</SAMP></CENTER>
30350 <P>
30352 If this feature is set, this message will be suppressed.
30353 If the feature
30354 <A HREF="h_config_quell_filtering_messages"><!--#echo var="FEAT_quell-filtering-messages"--></A>
30355 is set then this message will be suppressed regardless.
30357 <P>
30358 <UL>
30359 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30360 </UL><P>
30361 <End of help on this topic>
30362 </BODY>
30363 </HTML>
30364 ====== h_config_quell_filtering_messages =====
30365 <HTML>
30366 <HEAD>
30367 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></TITLE>
30368 </HEAD>
30369 <BODY>
30370 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></H1>
30372 If you use Filter Rules that move messages or set status of messages
30373 you sometimes see messages from Alpine that look like
30375 <P>
30376 <CENTER><SAMP><filter name>: Moving 2 filtered messages to <folder name></SAMP></CENTER>
30377 <P>
30379 or
30381 <P>
30382 <CENTER><SAMP><filter name>: Setting flags in 5 messages</SAMP></CENTER>
30383 <P>
30385 or
30387 <P>
30388 <CENTER><SAMP>Processing filter <filter name></SAMP></CENTER>
30389 <P>
30391 If this feature is set, these messages will be suppressed.
30392 The feature
30393 <A HREF="h_config_quell_filtering_done_message"><!--#echo var="FEAT_quell-filtering-done-message"--></A>
30394 is related.
30396 <P>
30397 <UL>
30398 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30399 </UL><P>
30400 <End of help on this topic>
30401 </BODY>
30402 </HTML>
30403 ====== h_config_quell_post_prompt =====
30404 <HTML>
30405 <HEAD>
30406 <TITLE>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></TITLE>
30407 </HEAD>
30408 <BODY>
30409 <H1>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></H1>
30411 By default, when you post a message to a newsgroup you are asked to confirm
30412 that you want to post with the question
30414 <P>
30415 <CENTER><SAMP>Posted message may go to thousands of readers. Really post?</SAMP></CENTER>
30416 <P>
30418 If this feature is set, you
30419 will <B>not</B> be prompted to confirm your intent to post to a newsgroup
30420 and your message will be posted.
30422 <P>
30423 <UL>
30424 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30425 </UL><P>
30426 <End of help on this topic>
30427 </BODY>
30428 </HTML>
30429 ====== h_config_check_mail_onquit =====
30430 <HTML>
30431 <HEAD>
30432 <TITLE>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></TITLE>
30433 </HEAD>
30434 <BODY>
30435 <H1>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></H1>
30437 If this feature is set, Alpine will check for new mail after you give the
30438 Quit command.
30439 If new mail has arrived since the previous check, you will be notified
30440 and given the choice of quitting or not quitting.
30441 <P>
30442 <UL>
30443 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30444 </UL><P>
30445 <End of help on this topic>
30446 </BODY>
30447 </HTML>
30448 ====== h_config_inbox_no_confirm =====
30449 <HTML>
30450 <HEAD>
30451 <TITLE>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></TITLE>
30452 </HEAD>
30453 <BODY>
30454 <H1>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></H1>
30456 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
30457 command and there are no more folders or newsgroups to visit, you are asked
30458 if you want to return to the INBOX.
30459 If this feature is set you will not be asked.
30460 It will be assumed that you do want to return to the INBOX.
30461 <P>
30462 <UL>
30463 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30464 </UL><P>
30465 <End of help on this topic>
30466 </BODY>
30467 </HTML>
30468 ====== h_config_dates_to_local =====
30469 <HTML>
30470 <HEAD>
30471 <TITLE>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></TITLE>
30472 </HEAD>
30473 <BODY>
30474 <H1>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></H1>
30476 Normally, the message dates that you see in the
30477 MESSAGE INDEX and MESSAGE VIEW are displayed in the timezone they were sent from.
30478 For example, if a message was sent to you from a few timezones to the east
30479 it might appear that it was sent from the future;
30480 or if it was sent from somewhere to the west it might appear
30481 as if it is from yesterday even though it was sent only a few minutes ago.
30482 If this feature is set an attempt will be made to convert the dates
30483 to your local timezone to be displayed.
30484 <P>
30485 Note that this does not affect the results of Select by Date or of
30486 anything else other than these displayed dates.
30487 When viewing the message you may look at the original unconverted value of the Date
30488 header by using the <A HREF="h_common_hdrmode">HdrMode Command</A>.
30489 <P>
30490 <UL>
30491 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30492 </UL><P>
30493 <End of help on this topic>
30494 </BODY>
30495 </HTML>
30496 ====== h_config_tab_no_prompt =====
30497 <HTML>
30498 <HEAD>
30499 <TITLE>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></TITLE>
30500 </HEAD>
30501 <BODY>
30502 <H1>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></H1>
30504 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
30505 command and there is a problem checking a folder, you are asked
30506 whether you want to continue with the search in the following folder or not.
30507 This question gives you a chance to stop the NextNew processing.
30508 (The checking problem might be caused by the fact that the folder does not
30509 exist, or by an authentication problem, or by a server problem
30510 of some sort.)
30511 <P>
30513 If this feature is set you will not be asked.
30514 It will be assumed that you do want to continue.
30515 <P>
30516 <UL>
30517 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30518 </UL><P>
30519 <End of help on this topic>
30520 </BODY>
30521 </HTML>
30522 ====== h_config_input_history =====
30523 <HTML>
30524 <HEAD>
30525 <TITLE>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></TITLE>
30526 </HEAD>
30527 <BODY>
30528 <H1>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></H1>
30530 Many of the prompts that ask for input in the status line near the
30531 bottom of the screen will respond to Up Arrow and Down Arrow
30532 with the history of previous entries.
30533 For example, in the MESSAGE INDEX screen when you use the WhereIs
30534 command the text you entered will be remembered and can be recalled
30535 by using the Up Arrow key.
30536 Another example, when saving a message the folders saved to will
30537 be remembered and can be recalled using the arrow keys.
30538 <P>
30539 In the Save prompt, some users prefer that the Up and Down arrow keys
30540 be used for the Previous Collection and Next Collection commands
30541 instead of for a history of previous saves.
30542 If this option is set the Up and Down arrow keys will become synonyms for the
30543 Previous Collection and Next Collection (^P and ^N) commands in the
30544 prompt for the name of a folder to Save to or in the prompt for the
30545 name of a folder to GoTo.
30546 When this feature is not set (the default), ^P and ^N will change the
30547 collection and the arrow keys will show the history.
30548 <P>
30549 <UL>
30550 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30551 </UL><P>
30552 <End of help on this topic>
30553 </BODY>
30554 </HTML>
30555 ====== h_config_confirm_role =====
30556 <HTML>
30557 <HEAD>
30558 <TITLE>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></TITLE>
30559 </HEAD>
30560 <BODY>
30561 <H1>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></H1>
30563 If you have roles, when you Reply to or Forward a message, or Compose
30564 a new message, Alpine
30565 will search through your roles for one that matches.
30566 Normally, if no matches are found you will be placed into the composer
30567 with no opportunity to select a role.
30568 If this feature is set, then you will be asked to confirm that you don't
30569 want a role.
30570 This will give you the opportunity to select a role (with the ^T command).
30571 If you confirm no role with a Return, you will be placed in
30572 the composer with no role.
30573 You may also confirm with either an "N" or a "Y".
30574 These behave the same as if you pressed the Return.
30575 (The "N" and "Y" answers are available because they
30576 match what you might type if there was a role match.)
30577 <P>
30578 If you are using the alternate form of the Compose command called
30579 "Role", then all of your roles will be available to you,
30580 independent of the value of this feauture and of the values set for all of
30581 Reply Use, Forward Use, and Compose Use.
30582 <P>
30583 <UL>
30584 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30585 </UL><P>
30586 <End of help on this topic>
30587 </BODY>
30588 </HTML>
30589 ====== h_config_news_cross_deletes =====
30590 <HTML>
30591 <HEAD>
30592 <TITLE>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></TITLE>
30593 </HEAD>
30594 <BODY>
30595 <H1>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></H1>
30597 This feature controls what Alpine does when you delete a message in a
30598 newsgroup that appears in more than one newsgroup. Such a message
30599 is sometimes termed a "crossposting" in that it was posted
30600 across several newsgroups.
30602 <P>
30603 Alpine's default behavior when you delete such a message is to remove
30604 only the copy in the current newsgroup from view when you use the
30605 "Exclude" command or the next time you visit the newsgroup.
30607 <P>
30608 Enabling this feature causes Alpine to remove every occurrence of the
30609 message from all newsgroups it appears in and to which you are
30610 subscribed.
30612 <P>
30613 NOTE: As currently implemented, enabling this feature may increase the
30614 time it takes the Expunge command and newsgroup closing to complete.
30616 <P>
30617 <UL>
30618 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30619 </UL><P>
30620 <End of help on this topic>
30621 </BODY>
30622 </HTML>
30623 ====== h_config_news_catchup =====
30624 <HTML>
30625 <HEAD>
30626 <TITLE>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></TITLE>
30627 </HEAD>
30628 <BODY>
30629 <H1>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></H1>
30631 This feature controls what Alpine does as it closes a newsgroup.
30632 When set, Alpine will offer to delete all messages from the newsgroup
30633 as you are quitting Alpine or opening a new folder.
30635 <P>
30636 This feature is useful if you typically read all the interesting messages
30637 in a newsgroup each time you open it. This feature saves you from
30638 having to delete each message in a newsgroup as you read it or from
30639 selecting all the messages and doing an
30640 <A HREF="h_config_enable_agg_ops">aggregate delete</A> before you
30641 move on to the next folder or newsgroup.
30643 <P>
30644 <UL>
30645 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30646 </UL><P>
30647 <End of help on this topic>
30648 </BODY>
30649 </HTML>
30650 ====== h_config_next_thrd_wo_confirm =====
30651 <HTML>
30652 <HEAD>
30653 <TITLE>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></TITLE>
30654 </HEAD>
30655 <BODY>
30656 <H1>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></H1>
30658 This feature controls an aspect of Alpine's Next and Prev commands in
30659 the case where you are using one of the
30660 "separate-index-screen" styles for the configuration option
30661 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
30662 and currently have the folder sorted by a Threaded or OrderedSubject sort.
30663 When you are Viewing a particular thread you have a
30664 MESSAGE INDEX of only the messages in that thread.
30665 If you press the Next command with the last message in the thread highlighted
30666 you will normally be asked if you want to "View next thread?",
30667 assuming there is a next thread to view.
30668 If this feature is set it will be assumed that you always want to view the
30669 next thread and you won't be asked to confirm that.
30670 Similarly, if the first message of the thread is highlighted and you
30671 press the Prev command, this feature will prevent the question
30672 "View previous thread".
30673 <P>
30674 This feature only has an effect in the MESSAGE INDEX screen.
30675 If you then view a particular message from that screen and press the
30676 Next command, you will be sent to the next thread without being asked,
30677 independent of the setting of this feature.
30678 <P>
30679 The feature
30680 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A> also has some similar effects.
30681 <P>
30682 <End of help on this topic>
30683 </BODY>
30684 </HTML>
30685 ====== h_config_kw_braces =====
30686 <HTML>
30687 <HEAD>
30688 <TITLE>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></TITLE>
30689 </HEAD>
30690 <BODY>
30691 <H1>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></H1>
30693 This option controls a minor aspect of Alpine's MESSAGE INDEX and MESSAGE
30694 TEXT screens.
30695 If you have modified the
30696 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
30697 so that either the "SUBJKEY" or "SUBJKEYINIT" tokens
30698 are used to display keywords or their initials along with the Subject; then
30699 this option may be used to modify the resulting display slightly.
30700 By default, the keywords or initials displayed for these tokens will be
30701 surrounded with curly braces ({ and }) and a trailing space.
30702 For example, if keywords "Work" and "Now" are set for
30703 a message, the "SUBJKEY" token will normally look like
30704 <P>
30705 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
30706 <P>
30707 and the SUBJKEYINIT token would look like
30708 <P>
30709 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
30710 <P>
30711 The default character before the keywords is the left brace ({) and the
30712 default after the keywords is the right brace followed by a space (} ).
30713 <P>
30714 This option allows you to change that.
30715 You should set it to two values separated by a space.
30716 The values may be quoted if they include space characters.
30717 So, for example, the default value could be specified explicitly by setting this
30718 option to
30719 <P>
30720 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="{" "} "</SAMP></CENTER>
30721 <P>
30722 The first part wouldn't need to be quoted (but it doesn't hurt).
30723 The second part does need the quotes because it includes a space character.
30724 If you wanted to change the braces to brackets you could use
30725 <P>
30726 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="[" "] "</SAMP></CENTER>
30727 <P>
30728 Inside the quotes you can use backslash quote to mean quote, so
30729 <P>
30730 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="\"" "\" "</SAMP></CENTER>
30731 <P>
30732 would produce
30733 <P>
30734 <CENTER><SAMP>"Work Now" actual subject</SAMP></CENTER>
30735 <P>
30736 It is also possible to color keywords in the index using the
30737 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
30738 <P>
30739 It is not possible to change the fact that a space character is used to
30740 separate the keywords if more than one keyword is set for a message.
30741 It is also not possible to change the fact that there are no separators
30742 between the keyword initials if more than one keyword is set.
30743 <P>
30744 <End of help on this topic>
30745 </BODY>
30746 </HTML>
30747 ====== h_config_opening_sep =====
30748 <HTML>
30749 <HEAD>
30750 <TITLE>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></TITLE>
30751 </HEAD>
30752 <BODY>
30753 <H1>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></H1>
30755 This option controls a minor aspect of Alpine's MESSAGE INDEX screen.
30756 With some setups the text of the subject is followed
30757 by the opening text of the message if there is any room available in the index line.
30758 If you have configured your
30759 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
30760 to include one of the Subject tokens that causes this behavior
30761 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), then this option may be used
30762 to modify what is displayed slightly.
30763 By default, the Subject is separated from the opening text of the message by
30764 the three characters space dash space;
30765 <P>
30766 <CENTER><SAMP>" - "</SAMP></CENTER>
30767 <P>
30768 Use this option to set it to something different.
30769 The value must be quoted if it includes any space characters.
30770 For example, the default value could be specified explicitly by setting this
30771 option to
30772 <P>
30773 <CENTER><SAMP><!--#echo var="VAR_opening-text-separator-chars"-->=" - "</SAMP></CENTER>
30774 <P>
30775 <End of help on this topic>
30776 </BODY>
30777 </HTML>
30778 ====== h_config_select_wo_confirm =====
30779 <HTML>
30780 <HEAD>
30781 <TITLE>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></TITLE>
30782 </HEAD>
30783 <BODY>
30784 <H1>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></H1>
30786 This feature controls an aspect of Alpine's Save, Export, and Goto commands.
30787 These commands all take text input to specify the name of the folder or
30788 file to be used, but allow you to press ^T for a list of possible names.
30789 If set, the selected name will be used immediately, without further
30790 opportunity to confirm or edit the name.
30791 <P>
30792 Some related help topics are
30793 <UL>
30794 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
30795 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
30796 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
30797 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
30798 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
30799 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>.
30800 </UL>
30801 <P>
30802 <End of help on this topic>
30803 </BODY>
30804 </HTML>
30805 ====== h_config_save_part_wo_confirm =====
30806 <HTML>
30807 <HEAD>
30808 <TITLE>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></TITLE>
30809 </HEAD>
30810 <BODY>
30811 <H1>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></H1>
30813 This feature controls an aspect of Alpine's Save command.
30814 By default, when you Save a message that has some deleted parts, you will
30815 be asked to confirm that you want to Save with a prompt that looks like:
30816 <P>
30817 <CENTER><SAMP>Saved copy will NOT include entire message! Continue?</SAMP></CENTER>
30818 <P>
30819 If this feature is set, you will not be asked.
30820 <P>
30821 <End of help on this topic>
30822 </BODY>
30823 </HTML>
30824 ====== h_config_use_resentto =====
30825 <HTML>
30826 <HEAD>
30827 <TITLE>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></TITLE>
30828 </HEAD>
30829 <BODY>
30830 <H1>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></H1>
30832 This feature is turned off by default because turning it on causes problems
30833 with some deficient IMAP servers.
30834 In Alpine <A HREF="h_mainhelp_filtering">Filters</A> and other types of Rules, if the
30835 <A HREF="h_rule_patterns">Pattern</A>
30836 contains a To header pattern and this feature is turned on,
30837 then a check is made in the message to see
30838 if a Resent-To header is present, and that is used instead of the To header.
30839 If this feature is not turned on, then the regular To header will always
30840 be used.
30842 <P>
30843 <End of help on this topic>
30844 </BODY>
30845 </HTML>
30846 ====== h_config_use_reg_start_for_stayopen =====
30847 <HTML>
30848 <HEAD>
30849 <TITLE>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></TITLE>
30850 </HEAD>
30851 <BODY>
30852 <H1>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></H1>
30854 This feature affects which message is selected as the current message
30855 when you enter a
30856 <A HREF="h_config_permlocked">Stay Open</A> folder.
30857 <P>
30858 Normally, the starting position for an incoming folder (which most Stay Open
30859 folders will likely be) is controlled by the
30860 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
30861 However, if a folder is a Stay Open folder, when you re-enter the folder
30862 after the first time the current message will be the same as it was when
30863 you left the folder.
30864 An exception is made if you use the TAB command to get to the folder.
30865 In that case, the message number will be incremented by one from what it
30866 was when you left the folder.
30867 <P>
30868 The above special behavior is thought to be useful.
30869 However, it is special and different from what you might at first expect.
30870 If this feature is set, then Stay Open folders will not be treated specially
30871 as far as the startup rule is concerned.
30873 <P>
30874 <End of help on this topic>
30875 </BODY>
30876 </HTML>
30877 ====== h_config_use_current_dir =====
30878 <HTML>
30879 <HEAD>
30880 <TITLE>FEATURE: <!--#echo var="FEAT_use-current-dir"--></TITLE>
30881 </HEAD>
30882 <BODY>
30883 <H1>FEATURE: <!--#echo var="FEAT_use-current-dir"--></H1>
30885 This feature controls an aspect of several commands.
30886 If set, your "current working directory"
30887 <!--chtml if pinemode="running"-->
30888 (which, at least for your current Alpine "session,"
30889 is "<!--#echo var="CURRENT_DIR"-->")
30890 <!--chtml endif-->
30891 will be used instead of your home directory
30892 <!--chtml if pinemode="running"-->
30893 (which, in the present configuration of your system, is
30894 "<!--#echo var="HOME_DIR"-->")
30895 <!--chtml endif-->
30896 for all of the following operations:<UL>
30897 <LI> Export in the MESSAGE INDEX and MESSAGE TEXT screens
30898 <LI> Attachment Save in the MESSAGE TEXT and ATTACHMENT TEXT screens
30899 <LI> <!--chtml if pinemode="function_key"-->F4
30900 <!--chtml else-->Ctrl-R
30901 <!--chtml endif--> file inclusion in the COMPOSER
30902 <LI> <!--chtml if pinemode="function_key"-->F5
30903 <!--chtml else-->Ctrl-J
30904 <!--chtml endif--> file attachment in the COMPOSER
30905 </UL>
30906 <!--chtml if pinemode="os_windows"-->
30907 <P>
30908 If you are starting PC-Alpine from a desktop icon or the Start menu,
30909 you can set the "current drive"
30910 by specifying it in the "Start in:"
30911 box found in the Shortcut tab of the Properties.
30912 <!--chtml endif-->
30913 <P>
30914 <UL>
30915 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30916 </UL>
30918 <P>
30919 <End of help on this topic>
30920 </BODY>
30921 </HTML>
30922 ====== h_config_save_wont_delete =====
30923 <HTML>
30924 <HEAD>
30925 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></TITLE>
30926 </HEAD>
30927 <BODY>
30928 <H1>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></H1>
30930 This feature controls one aspect of the Save command. If set, Save will
30931 not mark the message "deleted" (its default behavior) after
30932 it has been copied to the designated folder.
30934 <P>
30935 <End of help on this topic>
30936 </BODY>
30937 </HTML>
30938 ====== h_config_use_boring_spinner =====
30939 <HTML>
30940 <HEAD>
30941 <TITLE>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></TITLE>
30942 </HEAD>
30943 <BODY>
30944 <H1>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></H1>
30946 When Alpine is delayed for some reason it usually shows that
30947 something is happening with a small animated display in the status
30948 message line near the bottom of the screen.
30949 Setting this feature will cause that animation to be the same
30950 each time instead of having Alpine choose a random animation.
30951 You may turn the animation off altogether by setting the
30952 <A HREF="h_config_active_msg_interval"><!--#echo var="VAR_busy-cue-rate"--></A>
30953 option to zero.
30955 <P>
30956 <End of help on this topic>
30957 </BODY>
30958 </HTML>
30959 ====== h_config_unsel_wont_advance =====
30960 <HTML>
30961 <HEAD>
30962 <TITLE>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></TITLE>
30963 </HEAD>
30964 <BODY>
30965 <H1>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></H1>
30967 This feature controls one aspect of the Unselect Current message command.
30968 Normally, when the Unselect current message command (:) is typed when the
30969 current message is selected, the message will be unselected and the next
30970 message will become the current message.
30971 If this feature is set, the cursor will not advance to the next message.
30972 Instead, the current message will remain the current message after
30973 unselecting.
30975 <P>
30976 <End of help on this topic>
30977 </BODY>
30978 </HTML>
30979 ====== h_config_prune_uses_iso =====
30980 <HTML>
30981 <HEAD>
30982 <TITLE>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></TITLE>
30983 </HEAD>
30984 <BODY>
30985 <H1>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></H1>
30987 By default, Alpine asks monthly whether or not you would like to rename
30988 some folders to a new name containing the date.
30989 It also asks whether or not you would like to delete some old folders.
30990 See the <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option for an
30991 explanation.
30993 <P>
30994 By default, the name used when renaming a folder looks like
30995 <P>
30996 <CENTER><SAMP><foldername>-<month>-<year></SAMP></CENTER>
30997 <P>
30998 For example, the first time you run Alpine in May of 2004,
30999 the folder "sent-mail" might be renamed to
31000 <P>
31001 <CENTER><SAMP>sent-mail-apr-2004</SAMP></CENTER>
31002 <P>
31003 If this feature is set, the name used will be of the form
31004 <P>
31005 <CENTER><SAMP><foldername>-<yyyy>-<mm></SAMP></CENTER>
31006 <P>
31007 where "yyyy" is the year and "mm" is the two-digit
31008 month (01, 02, ..., 12).
31009 For the April, 2004 example above, it would instead be
31010 <P>
31011 <CENTER><SAMP>sent-mail-2004-04</SAMP></CENTER>
31012 <P>
31013 because April is the 4th month of the year.
31014 A reason you might want to set this feature is so that the folders
31015 will sort in chronological order.
31017 <P>
31018 <End of help on this topic>
31019 </BODY>
31020 </HTML>
31021 ====== h_config_save_advances =====
31022 <HTML>
31023 <HEAD>
31024 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-advance"--></TITLE>
31025 </HEAD>
31026 <BODY>
31027 <H1>FEATURE: <!--#echo var="FEAT_save-will-advance"--></H1>
31029 This feature controls one aspect of the Save command. If set, Save will
31030 (in addition to copying the current message to the designated folder) also
31031 advance to the next message.
31033 <P>
31034 <End of help on this topic>
31035 </BODY>
31036 </HTML>
31037 ====== h_config_force_arrow =====
31038 <HTML>
31039 <HEAD>
31040 <TITLE>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></TITLE>
31041 </HEAD>
31042 <BODY>
31043 <H1>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></H1>
31045 This feature affects Alpine's MESSAGE INDEX display routine.
31046 If set, the normal inverse-video cursor will be
31047 replaced by a simple "arrow" cursor, which normally occupies the
31048 second column of the index display.
31049 <P>
31050 This is the same index cursor you get if you turn on
31051 <A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>, but the index
31052 line coloring will still be present if this feature is turned on and
31053 <!--#echo var="FEAT_assume-slow-link"--> is off.
31054 <P>
31055 An alternative version of the Arrow cursor is available by including the
31056 <A HREF="h_config_index_arrow_color">ARROW</A>
31057 token in the
31058 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
31059 <P>
31060 It ought to be the case that this feature also affects the ATTACHMENT INDEX,
31061 but that is not implemented.
31063 <P>
31064 <End of help on this topic>
31065 </BODY>
31066 </HTML>
31067 ====== h_config_force_low_speed =====
31068 <HTML>
31069 <HEAD>
31070 <TITLE>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></TITLE>
31071 </HEAD>
31072 <BODY>
31073 <H1>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></H1>
31075 UNIX Alpine only.
31076 <P>
31077 This feature affects Alpine's display routines. If set, the normal
31078 inverse-video cursor (used to highlight the current item in a list) will be
31079 replaced by an "arrow" cursor and other
31080 screen update optimizations for
31081 low-speed links (e.g. 2400 bps dialup connections) will be activated.
31082 One of the optimizations is that colored index lines (set up with Indexcolor
31083 Rules) will not be colored.
31084 If you are just turning this feature on because you like using
31085 the "arrow" cursor you may have an arrow cursor with index line
31086 coloring by turning this feature off and the
31087 <A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A> on.
31089 <P>
31090 <End of help on this topic>
31091 </BODY>
31092 </HTML>
31093 ====== h_config_show_delay_cue =====
31094 <HTML>
31095 <HEAD>
31096 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></TITLE>
31097 </HEAD>
31098 <BODY>
31099 <H1>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></H1>
31101 If set, this feature will cause an asterisk to appear in the upper
31102 left-hand corner of the screen whenever Alpine checks for new mail.
31103 Two asterisks whenever Alpine saves (checkpoints) the state of the current
31104 mailbox to disk.
31106 <!--chtml if pinemode="os_windows"-->
31107 <P>
31108 In addition, PC-Alpine will display a less-than symbol, '<', when
31109 it is trying to open a network connection (e.g, to open your INBOX
31110 on an IMAP
31111 server) or read from the network connection. A greater-than symbol,
31112 will be displayed when PC-Alpine is trying to write to the network
31113 connection (e.g, sending a command to your IMAP server).
31114 <!--chtml endif-->
31116 <P>
31117 <End of help on this topic>
31118 </BODY>
31119 </HTML>
31120 ====== h_config_color_style =====
31121 <HTML>
31122 <HEAD>
31123 <TITLE>OPTION: Color Style</TITLE>
31124 </HEAD>
31125 <BODY>
31126 <H1>OPTION: Color Style</H1>
31128 UNIX Alpine only.
31129 <P>
31130 If the terminal or terminal emulator you are using is capable of displaying
31131 colors, this option controls whether or not color will be used in Alpine.
31132 If you turn color on and things are set up correctly,
31133 you should see color appear on the screen immmediately.
31134 Modern terminal emulators are usually capable of displaying colors.
31135 <P>
31136 The available options include:
31137 <P>
31139 <DL>
31140 <DT>no-color</DT>
31141 <DD>Don't use color.
31142 </DD>
31144 <DT>use-termdef</DT>
31145 <DD>In order to decide if your terminal is capable of color, Alpine looks in
31146 the terminal capabilities database, TERMINFO or TERMCAP, depending on
31147 how Alpine was compiled.
31148 This is a good option to choose if you switch between a color and a non-color
31149 terminal with the same Alpine configuration.
31150 Alpine will know to use color on the color terminal because it is described
31151 in the termcap entry, and Alpine will know to use black and white on the
31152 non-color terminal.
31153 The Alpine Technical Notes
31154 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/tech-notes/">http://www.washington.edu/alpine/tech-notes/</A></SAMP></CENTER>
31155 have more information on configuring a TERMCAP or TERMINFO
31156 entry for color Alpine.
31157 This is usually something a system administrator does.
31158 </DD>
31160 <DT>force-ansi-8color</DT>
31161 <DD>This is probably the setting that most people should use.
31162 Because setting up a termcap entry is confusing and because the
31163 terminal capabilities database is often not correctly configured for color,
31164 this choice and the next may be easier for you to use.
31165 If your terminal emulator responds to ANSI color escape sequences, which
31166 many do, this option will cause Alpine to believe your terminal will respond
31167 to the escape sequences that produce eight different foreground and background
31168 colors.
31169 The escape sequences used to set the foreground colors are
31171 <P><CENTER>ESC [ 3 <color_number> m</CENTER><P>
31173 where the color_number is an ASCII digit between 0 and 7.
31174 The numbers 0 through 7 should correspond to the colors black, red, green,
31175 yellow, blue, magenta, cyan, and white.
31176 Some terminal emulators use a pre-ANSI scheme that swaps
31177 the colors blue and red and the colors yellow and cyan.
31178 This will cause the default colors to be different, but other than that
31179 things should work fine.
31180 There is also a 9th color available, the last one shown, which is the default
31181 color from the terminal emulator.
31182 When used as a background color some people refer to this color as
31183 "transparent", which is why the letters "TRAN" are
31184 shown in the color swatch of the SETUP COLOR screen.
31185 The foreground transparent color is shown as
31186 the color of the "TRAN" text.
31187 (The transparent color will not work correctly in a PC-Alpine configuration.)
31188 The escape sequences used to set the background colors are the same
31189 as for the foreground colors except a "4" replaces the "3".
31190 The escape sequences for foreground and background default colors (transparent)
31191 are 39m and 49m.
31192 <P>
31193 Note: With the Tera Term terminal emulator this setting works well.
31194 You should also have the Tera Term "Full color" option turned OFF.
31195 You may find the "Full color" option in Tera Term's "Setup"
31196 menu, in the "Window" submenu.
31197 </DD>
31199 <DT>force-ansi-16color</DT>
31200 <DD>Many terminal emulators know about the same eight colors above
31201 plus eight more.
31202 This option attempts to use all 16 colors.
31203 The same escape sequences as for the eight-color terminal are used
31204 for the first eight colors.
31205 The escape sequences used to set foreground colors 8-15 are the same as
31206 for 0-7 except the "3" is replaced with a "9".
31207 The background color sequences for colors 8-15 are the same as for 0-7
31208 except the "4" is replaced with "10".
31209 You can tell if the 16 colors are working by turning on this option
31210 and then going into one of the color configuration screens, for example,
31211 the configuration screen for Normal Color.
31212 If you see 16 different colors to select from (plus a 17th for
31213 the transparent color), it's working.
31214 </DD>
31216 <DT>force-xterm-256color</DT>
31217 <DD>Some versions of xterm (and some other terminal emulators)
31218 have support for 256 colors.
31219 The escape sequences used to set the foreground colors are
31221 <P><CENTER>ESC [ 38 ; 5 ; <color_number> m</CENTER><P>
31223 where the color_number is an ASCII digit between 0 and 255.
31224 Background colors are the same with the 38 replaced with a 48.
31225 The numbers 0 through 15 are probably similar to the 16 color version
31226 above, then comes a 6x6x6 color cube, followed by 24 colors of gray.
31227 The terminal default (transparent) color is the 257th color at the bottom.
31228 Some terminal emulators will misinterpret these escape sequences causing
31229 the terminal to blink or overstrike characters or to do something else
31230 undesirable.
31231 <P>
31232 The PuTTY terminal emulator has an option called "Allow terminal to
31233 use xterm 256-colour mode" which allows PuTTY to work well with
31234 this 256-color setting.
31236 </DD>
31237 </DL>
31239 <P>
31240 The normal default is "no-color".
31241 <P>
31243 Once you've turned on color you may set the
31244 colors of many objects on the screen individually.
31245 For example, you may add colors to the status letters on the MESSAGE
31246 INDEX page.
31247 Most categories of color that Alpine supports are configurable here.
31248 For example, "Normal Color"
31249 is the color used to display most of the text in Alpine, and
31250 "Reverse Color" is used to display highlighted text, such as the
31251 current message in the MESSAGE INDEX.
31252 <P>
31253 Lines in the MESSAGE INDEX may also be colored.
31254 Use Setup Rules to get to the Indexcolor configuration screen.
31255 <P>
31257 <UL>
31258 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31259 </UL><P>
31260 <End of help on this topic>
31261 </BODY>
31262 </HTML>
31263 ====== h_config_disable_index_locale_dates =====
31264 <HTML>
31265 <HEAD>
31266 <TITLE>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></TITLE>
31267 </HEAD>
31268 <BODY>
31269 <H1>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></H1>
31271 This feature affects the display of dates in the MESSAGE INDEX.
31272 Normally an attempt is made to localize the dates
31273 used in the MESSAGE INDEX display to your locale.
31274 This is controlled with the
31275 LC_TIME locale setting on a UNIX system.
31276 On Windows the Regional Options control panel may be used to set the date format.
31277 At the programming level, Alpine is using the strftime routine
31278 to print the parts of a date.
31279 <P>
31280 If this feature is set, dates are displayed in English and
31281 with the conventions of the United States.
31282 <P>
31284 <UL>
31285 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31286 </UL><P>
31287 <End of help on this topic>
31288 </BODY>
31289 </HTML>
31290 ====== h_config_auto_open_unread =====
31291 <HTML>
31292 <HEAD>
31293 <TITLE>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></TITLE>
31294 </HEAD>
31295 <BODY>
31296 <H1>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></H1>
31298 This feature controls the behavior of the TAB key when traversing folders
31299 in the optional
31300 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
31301 collection or in optional <!--#echo var="VAR_news-collections"-->.
31302 <P>
31303 When the TAB
31304 (<A HREF="h_common_nextnew">NextNew</A>)
31305 key is pressed, and there
31306 are no more unseen messages in the current (incoming message or news)
31307 folder, Alpine will search the list of folders in the current collection for
31308 one containing New or Recent (new since the last time the folder was
31309 opened) messages.
31310 This behavior may be modified slightly with the
31311 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
31312 feature that causes Alpine to look for Unseen messages instead of Recent
31313 messages.
31314 Normally, when such a folder is found, Alpine will ask
31315 whether you wish to open the folder. If this feature is set, Alpine will
31316 automatically open the folder without prompting.
31317 <P>
31318 This feature also affects some other similar situations.
31319 If you have a
31320 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
31321 that is equal to one of the "separate-" values, and you are
31322 viewing a thread; then when you type the NextNew command and are at the
31323 end of the current thread you will automatically go to the next thread
31324 if this feature is set.
31325 By default, you would be asked if you want to view the next thread.
31326 You will also be asked at times whether or not you want to view the next
31327 thread after you delete the last message in the thread.
31328 Setting this feature will also cause that question to be skipped.
31329 <P>
31331 <UL>
31332 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31333 </UL><P>
31334 <End of help on this topic>
31335 </BODY>
31336 </HTML>
31337 ====== h_config_auto_include_reply =====
31338 <HTML>
31339 <HEAD>
31340 <TITLE>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></TITLE>
31341 </HEAD>
31342 <BODY>
31343 <H1>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></H1>
31345 This feature controls an aspect of Alpine's Reply command. Normally, Alpine
31346 will ask whether you wish to include the original message in your reply.
31347 If this feature is set and the feature
31348 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
31349 is <EM>not</EM> set, then the original message will be included in the reply
31350 automatically, without prompting.
31351 <P>
31352 <End of help on this topic>
31353 </BODY>
31354 </HTML>
31355 ====== h_config_select_in_bold =====
31356 <HTML>
31357 <HEAD>
31358 <TITLE>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></TITLE>
31359 </HEAD>
31360 <BODY>
31361 <H1>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></H1>
31363 This feature controls an aspect of Alpine's
31364 <A HREF="h_config_enable_agg_ops">"aggregate operation"</A>
31365 commands; in
31366 particular, the Select and WhereIs commands. Select and WhereIs (with the
31367 ^X subcommand) will search the current folder for messages meeting a
31368 specified criteria, and "tag" the resulting messages with an
31369 "X" in the
31370 first column of the applicable lines in the MESSAGE INDEX. If this feature
31371 is set, instead of using the "X" to denote a selected message,
31372 Alpine will
31373 attempt to display those index lines in boldface. Whether this is
31374 preferable to the "X" will depend on personal taste and the type of
31375 terminal being used.
31376 <P>
31377 <UL>
31378 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31379 </UL><P>
31380 <End of help on this topic>
31381 </BODY>
31382 </HTML>
31383 ====== h_config_alt_auth =====
31384 <HTML>
31385 <HEAD>
31386 <TITLE>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></TITLE>
31387 </HEAD>
31388 <BODY>
31389 <H1>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></H1>
31391 This feature affects how Alpine connects to IMAP servers.
31392 It's utility has largely been overtaken by events,
31393 but it may still be useful in some circumstances.
31394 If you only connect to modern IMAP servers that support
31395 "TLS" you can ignore this feature.
31397 <P>
31398 Details:
31400 <P>
31401 By default, Alpine will attempt to connect to an IMAP server on the
31402 normal IMAP service port (143), and if the server offers "Transport Layer
31403 Security" (TLS) and Alpine has been compiled with encryption capability,
31404 then a secure (encrypted) session will be negotiated.
31406 <P>
31407 With this feature enabled, before connecting on the normal IMAP port, Alpine
31408 will first attempt to connect to an alternate IMAP service port (993) used
31409 specifically for encrypted IMAP sessions via the Secure Sockets Layer
31410 (SSL) method.
31411 If the SSL attempt fails, Alpine will then try the default
31412 behavior described in the previous paragraph.
31414 <P>
31415 TLS negotiation on the normal port is preferred, and supersedes the use of
31416 SSL on port 993, but older servers may not provide TLS support.
31417 This feature may be convenient when accessing IMAP servers that do not support
31418 TLS, but do support SSL connections on port 993.
31419 However, it is important to understand that with this feature enabled,
31420 Alpine will <EM>attempt</EM> to make a secure connection if that is possible,
31421 but it will proceed to make an insecure connection if that is the only
31422 option offered by the server, or if the Alpine in question has been built
31423 without encryption capability.
31425 <P>
31426 Note that this feature specifies a per-user (or system-wide) default
31427 behavior, but host/folder specification flags may be used to control the
31428 behavior of any specific connection.
31429 This feature interacts with some of
31430 the possible host/folder path specification flags as follows:
31432 <P>
31433 The <SAMP>/tls</SAMP> host flag, for example,
31435 <P>
31436 <CENTER><SAMP>{foo.example.com/tls}INBOX</SAMP></CENTER>
31437 <P>
31438 will over-ride this feature for the specified host by bypassing the
31439 SSL connection attempt.
31440 Moreover, with <SAMP>/tls</SAMP> specified,
31441 the connection attempt will fail if the
31442 service on port 143 does not offer TLS support.
31444 <P>
31445 The <SAMP>/ssl</SAMP> host flag, for example,
31447 <P>
31448 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
31449 <P>
31450 will insist on an SSL connection for the specified host,
31451 and will fail if the SSL service on port 993 is not available.
31452 Alpine will not subsequently retry a connection
31453 on port 143 if <SAMP>/ssl</SAMP> is specified.
31455 <P>
31456 <UL>
31457 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31458 </UL><P>
31459 <End of help on this topic>
31460 </BODY>
31461 </HTML>
31462 ====== h_config_file_dir ======
31463 <HTML>
31464 <HEAD>
31465 <TITLE>OPTION: File Directory</TITLE>
31466 </HEAD>
31467 <BODY>
31468 <H1>OPTION: File Directory</H1>
31470 PC-Alpine only.
31471 <P>
31472 This value affects the Composer's "^J Attach" command,
31473 the Attachment Index Screen's "S Save" command, and the
31474 Message Index's "E Export" command.
31476 <P>
31477 Normally, when a filename is supplied that lacks a leading "path"
31478 component, Alpine assumes the file exists in the user's home directory.
31479 Under Windows operating systems, this definition isn't always clear. This
31480 feature allows you to explictly set where Alpine should look for files
31481 without a leading path.
31483 <P>
31484 NOTE: this feature's value is ignored if either
31485 <A HREF="h_config_use_current_dir"><!--#echo var="FEAT_use-current-dir"--></A> feature
31486 is set or the PINERC has a value for the "<!--#echo var="VAR_operating-dir"-->" variable.
31488 <P>
31489 <UL>
31490 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31491 </UL><P>
31492 <End of help on this topic>
31493 </BODY>
31494 </HTML>
31495 ====== h_config_quote_all_froms =====
31496 <HTML>
31497 <HEAD>
31498 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></TITLE>
31499 </HEAD>
31500 <BODY>
31501 <H1>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></H1>
31503 This feature controls an aspect of the Save command (and also the way
31504 outgoing messages are saved to an FCC folder). If set, Alpine will add
31505 a leading ">" character in front of message lines beginning with "From"
31506 when they are saved to another folder, including lines syntactically
31507 distinguishable from the type of message separator line commonly used on
31508 Unix systems.
31510 <P>
31511 The default behavior is that a ">" will be prepended only to lines
31512 beginning with "From " that might otherwise be confused with a message
31513 separator line on Unix systems. If pine is the only mail program you use,
31514 this default is reasonable. If another program you use has trouble
31515 displaying a message with an unquoted "From " saved by Alpine, you should
31516 enable this feature. This feature only applies to the common Unix mailbox
31517 format that uses message separator lines beginning with "From ". If
31518 Alpine has been configured to use a different mailbox format (possibly
31519 incompatible with other mail programs), then this issue does not arise,
31520 and the feature is irrelevant.
31522 <P>
31523 <End of help on this topic>
31524 </BODY>
31525 </HTML>
31526 ====== h_config_normal_color =====
31527 <HTML>
31528 <HEAD>
31529 <TITLE>OPTION: Normal Color</TITLE>
31530 </HEAD>
31531 <BODY>
31532 <H1>OPTION: Normal Color</H1>
31534 Sets the color Alpine normally uses.
31535 The foreground color is the color of the actual character and the
31536 background color is the color of the area behind the character.
31537 By default this color is black characters on a white background.
31538 <P>
31539 <A HREF="h_color_setup">Descriptions of the available commands</A>
31540 <P>
31541 Look <A HREF="h_edit_nav_cmds">here</A>
31542 to see the available Editing and Navigation commands.
31543 <P>
31544 <End of help on this topic>
31545 </BODY>
31546 </HTML>
31547 ====== h_config_reverse_color =====
31548 <HTML>
31549 <HEAD>
31550 <TITLE>OPTION: Reverse Color</TITLE>
31551 </HEAD>
31552 <BODY>
31553 <H1>OPTION: Reverse Color</H1>
31555 Sets the color Alpine uses for reverse video characters.
31556 The foreground color is the color of the actual character and the
31557 background color is the color of the area behind the character.
31558 <P>
31559 <A HREF="h_color_setup">Descriptions of the available commands</A>
31560 <P>
31561 Look <A HREF="h_edit_nav_cmds">here</A>
31562 to see the available Editing and Navigation commands.
31563 <P>
31564 <End of help on this topic>
31565 </BODY>
31566 </HTML>
31567 ====== h_config_title_color =====
31568 <HTML>
31569 <HEAD>
31570 <TITLE>OPTION: Title Color</TITLE>
31571 </HEAD>
31572 <BODY>
31573 <H1>OPTION: Title Color</H1>
31575 Sets the color Alpine uses for the titlebar (the top line on the screen).
31576 The foreground color is the color of the actual character and the
31577 background color is the color of the area behind the character.
31578 By default, the Title Color is black characters on a yellow background.
31579 <P>
31580 The actual titlebar color may be different from the Title Color if
31581 the option
31582 <A HREF="h_config_titlebar_color_style">"<!--#echo var="VAR_titlebar-color-style"-->"</A>
31583 is set to some value other than the default.
31584 It may also be different if the current folder is closed and the
31585 <A HREF="h_config_titleclosed_color">Title Closed Color</A>
31586 color is set to something different from the Title Color.
31587 <P>
31588 <A HREF="h_color_setup">Descriptions of the available commands</A>
31589 <P>
31590 Look <A HREF="h_edit_nav_cmds">here</A>
31591 to see the available Editing and Navigation commands.
31592 <P>
31593 <End of help on this topic>
31594 </BODY>
31595 </HTML>
31596 ====== h_config_titleclosed_color =====
31597 <HTML>
31598 <HEAD>
31599 <TITLE>OPTION: Title Closed Color</TITLE>
31600 </HEAD>
31601 <BODY>
31602 <H1>OPTION: Title Closed Color</H1>
31604 Sets the color Alpine uses for the titlebar (the top line on the screen)
31605 when the current folder is closed.
31606 The foreground color is the color of the actual character and the
31607 background color is the color of the area behind the character.
31608 By default, the Title Color Closed Color is white characters on a red background.
31609 <P>
31610 By setting this color to something noticeable you will be alerted to the
31611 fact that the current folder is closed, perhaps unexpectedly.
31612 <P>
31613 <End of help on this topic>
31614 </BODY>
31615 </HTML>
31616 ====== h_config_status_color =====
31617 <HTML>
31618 <HEAD>
31619 <TITLE>OPTION: Status Color</TITLE>
31620 </HEAD>
31621 <BODY>
31622 <H1>OPTION: Status Color</H1>
31624 Sets the color Alpine uses for status messages written to the message
31625 line near the bottom of the screen.
31626 The foreground color is the color of the actual character and the
31627 background color is the color of the area behind the character.
31628 By default, the Status Color is the same as the Reverse Color.
31629 <P>
31630 <A HREF="h_color_setup">Descriptions of the available commands</A>
31631 <P>
31632 Look <A HREF="h_edit_nav_cmds">here</A>
31633 to see the available Editing and Navigation commands.
31634 <P>
31635 <End of help on this topic>
31636 </BODY>
31637 </HTML>
31638 ====== h_config_index_opening_color =====
31639 <HTML>
31640 <HEAD>
31641 <TITLE>OPTION: Index Opening Color</TITLE>
31642 </HEAD>
31643 <BODY>
31644 <H1>OPTION: Index Opening Color</H1>
31646 With some setups the text of the subject is followed
31647 by the opening text of the message if there is any room available in the index line.
31648 If you have configured your
31649 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
31650 to include one of the Subject tokens that causes this behavior
31651 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), you may set the color of
31652 this opening text with this option.
31653 This coloring takes place for all but the current index line, and the Opening
31654 Color appears to be in front of any color from an Index Color Rule.
31655 <P>
31656 By default the Index Opening Color is gray characters on a white background.
31658 <P>
31659 <A HREF="h_color_setup">Descriptions of the available commands</A>
31660 <P>
31661 Look <A HREF="h_edit_nav_cmds">here</A>
31662 to see the available Editing and Navigation commands.
31663 <P>
31664 <End of help on this topic>
31665 </BODY>
31666 </HTML>
31667 ====== h_config_index_pri_color =====
31668 <HTML>
31669 <HEAD>
31670 <TITLE>OPTION: Index Priority Symbol Colors</TITLE>
31671 </HEAD>
31672 <BODY>
31673 <H1>OPTION: Index Priority Symbol Colors</H1>
31675 The X-Priority header is a non-standard header that is used in a
31676 somewhat standard way by many mail programs.
31677 Alpine expects the value of this header to be a digit with a value
31678 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
31679 Alpine can be made to display an indication of this priority in
31680 messages by use of one of the tokens
31681 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
31682 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
31683 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
31685 <P>
31686 You may set the color used to draw these tokens by use of the colors
31687 Index High Priority Symbol Color and Index Low Priority Symbol Color.
31688 This coloring takes place for all but the current index line, and the Priority
31689 Color appears to be in front of any color from an Index Color Rule.
31690 If the priority has a value of 1 or 2 the High Priority color will be
31691 used,
31692 and if the value is 4 or 5 the Low Priority color will be used.
31693 <P>
31694 If you don't set these colors the index line will be colored in the same color as
31695 the bulk of the index line.
31697 <P>
31698 <A HREF="h_color_setup">Descriptions of the available commands</A>
31699 <P>
31700 Look <A HREF="h_edit_nav_cmds">here</A>
31701 to see the available Editing and Navigation commands.
31702 <P>
31703 <End of help on this topic>
31704 </BODY>
31705 </HTML>
31706 ====== h_config_index_subject_color =====
31707 <HTML>
31708 <HEAD>
31709 <TITLE>OPTION: Index Subject Color</TITLE>
31710 </HEAD>
31711 <BODY>
31712 <H1>OPTION: Index Subject Color</H1>
31714 You may set the color used to draw the Subject part of the index line.
31715 This coloring takes place for all but the current index line, and the Subject
31716 Color appears to be in front of any color from an Index Color Rule.
31717 <P>
31718 If you don't set this color it will be colored in the same color as
31719 the bulk of the index line.
31721 <P>
31722 <A HREF="h_color_setup">Descriptions of the available commands</A>
31723 <P>
31724 Look <A HREF="h_edit_nav_cmds">here</A>
31725 to see the available Editing and Navigation commands.
31726 <P>
31727 <End of help on this topic>
31728 </BODY>
31729 </HTML>
31730 ====== h_config_index_from_color =====
31731 <HTML>
31732 <HEAD>
31733 <TITLE>OPTION: Index From Color</TITLE>
31734 </HEAD>
31735 <BODY>
31736 <H1>OPTION: Index From Color</H1>
31738 You may set the color used to draw the From part of the index line.
31739 This coloring takes place for all but the current index line, and the From
31740 Color appears to be in front of any color from an Index Color Rule.
31741 <P>
31742 If you don't set this color it will be colored in the same color as
31743 the bulk of the index line.
31745 <P>
31746 <A HREF="h_color_setup">Descriptions of the available commands</A>
31747 <P>
31748 Look <A HREF="h_edit_nav_cmds">here</A>
31749 to see the available Editing and Navigation commands.
31750 <P>
31751 <End of help on this topic>
31752 </BODY>
31753 </HTML>
31754 ====== h_config_index_arrow_color =====
31755 <HTML>
31756 <HEAD>
31757 <TITLE>OPTION: Index Arrow Color</TITLE>
31758 </HEAD>
31759 <BODY>
31760 <H1>OPTION: Index Arrow Color</H1>
31762 If you have configured your
31763 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
31764 to include the "ARROW" token, you may set the color of
31765 the arrow displayed with this option.
31766 If you don't set the color it will be colored in the same color as
31767 the bulk of the index line.
31769 <P>
31770 <A HREF="h_color_setup">Descriptions of the available commands</A>
31771 <P>
31772 Look <A HREF="h_edit_nav_cmds">here</A>
31773 to see the available Editing and Navigation commands.
31774 <P>
31775 <End of help on this topic>
31776 </BODY>
31777 </HTML>
31778 ====== h_config_index_color =====
31779 <HTML>
31780 <HEAD>
31781 <TITLE>OPTION: Index Colors</TITLE>
31782 </HEAD>
31783 <BODY>
31784 <H1>OPTION: Index Colors</H1>
31786 You may add color to the single character symbols that give the status
31787 of each message in the MESSAGE INDEX.
31788 By default the characters "+", "*", "D",
31789 "A", and "N" show up near the left hand side of the
31790 screen depending on whether the message is addressed to you, and whether
31791 the message is marked Important, is Deleted, is Answered, or is New.
31792 The color for each of those characters may be specified by setting the
31793 "Index-to-me" Symbol Color,
31794 the "Index-important" Symbol Color,
31795 the "Index-deleted" Symbol Color,
31796 the "Index-answered" Symbol Color,
31797 and the "Index-new" Symbol Color.
31798 There are also two other symbol colors called "Index-recent"
31799 and "Index-unseen".
31800 These two colors will only be used if you have configured your
31801 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
31802 to include the "IMAPSTATUS" or "SHORTIMAPSTATUS" token.
31803 <P>
31804 The default colors for these symbols are:
31805 <TABLE>
31806 <TR> <TD> Index-to-me </TD> <TD> black on cyan </TD> </TR>
31807 <TR> <TD> Index-important </TD> <TD> white on bright red </TD> </TR>
31808 <TR> <TD> Index-deleted </TD> <TD> same as Normal Color </TD> </TR>
31809 <TR> <TD> Index-answered </TD> <TD> bright red on yellow </TD> </TR>
31810 <TR> <TD> Index-new </TD> <TD> white on magenta </TD> </TR>
31811 <TR> <TD> Index-recent </TD> <TD> same as Normal Color </TD> </TR>
31812 <TR> <TD> Index-unseen </TD> <TD> same as Normal Color </TD> </TR>
31813 </TABLE>
31814 <P>
31815 Besides coloring the message status symbols, you may also color the
31816 entire index line.
31817 This is done by using the
31818 <A HREF="h_rules_incols">SETUP INDEX LINE COLORS</A> screen, which you
31819 may get to with the commands <EM>S</EM>etup/<EM>R</EM>ules/<EM>I</EM>ndexcolor.
31820 When the entire line is colored that color will be "behind" the
31821 status symbol colors talked about in the paragraph above.
31822 <P>
31823 You may also color
31824 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
31825 in the index using the
31826 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>);
31827 the <A HREF="h_config_index_arrow_color">ARROW</A> cursor;
31828 the Subject using
31829 <A HREF="h_config_index_subject_color">Index Subject Color</A>;
31830 the From field using
31831 <A HREF="h_config_index_from_color">Index From Color</A>;
31832 and the
31833 <A HREF="h_config_index_opening_color">Index Opening</A> text.
31834 <P>
31835 <A HREF="h_color_setup">Descriptions of the available commands</A>
31836 <P>
31837 Look <A HREF="h_edit_nav_cmds">here</A>
31838 to see the available Editing and Navigation commands.
31839 <P>
31840 <End of help on this topic>
31841 </BODY>
31842 </HTML>
31843 ====== h_config_metamsg_color =====
31844 <HTML>
31845 <HEAD>
31846 <TITLE>OPTION: Meta-Message Color</TITLE>
31847 </HEAD>
31848 <BODY>
31849 <H1>OPTION: Meta-Message Color</H1>
31851 Sets the color Alpine uses in the MESSAGE TEXT screen for messages to you
31852 that aren't part of the message itself.
31853 For example, an attachment that isn't shown might produce a meta
31854 message something like:
31855 <P>
31856 <CENTER><SAMP> [ Part 2, "comment" Text/PLAIN (Name: "file") ]</SAMP></CENTER>
31857 <P>
31858 If you set the
31859 <A HREF="h_config_quote_suppression"><!--#echo var="VAR_quote-suppression-threshold"--></A>
31860 option you might see
31861 <P>
31862 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
31863 <P>
31864 Warnings about suspicious looking URLs in HTML will also be colored
31865 with this color.
31866 <P>
31867 The foreground color is the color of the actual character and the
31868 background color is the color of the area behind the character.
31869 By default, the Meta-Message Color is black characters on a yellow background.
31870 <P>
31871 <A HREF="h_color_setup">Descriptions of the available commands</A>
31872 <P>
31873 Look <A HREF="h_edit_nav_cmds">here</A>
31874 to see the available Editing and Navigation commands.
31875 <P>
31876 <End of help on this topic>
31877 </BODY>
31878 </HTML>
31879 ====== h_config_keylabel_color =====
31880 <HTML>
31881 <HEAD>
31882 <TITLE>OPTION: KeyLabel Color</TITLE>
31883 </HEAD>
31884 <BODY>
31885 <H1>OPTION: KeyLabel Color</H1>
31887 Sets the color Alpine uses for the labels of the keys in the two-line
31888 menu at the bottom of the screen.
31889 For example, some of the screens have a "P PrevMsg" command.
31890 This option sets the color used when displaying "PrevMsg".
31891 The foreground color is the color of the actual character and the
31892 background color is the color of the area behind the character.
31893 By default, the KeyLabel Color is the same as the Normal Color.
31894 <P>
31895 WARNING: Some terminal emulators have the property that the screen will scroll
31896 down one line whenever a character is written to the character cell in the
31897 lower right corner of the screen.
31898 Alpine can usually avoid writing a character in that corner of the screen.
31899 However, if you have defined a KeyLabel Color then Alpine does have to write
31900 a character in that cell in order to color the cell correctly.
31901 If you find that your display sometimes scrolls up a line this could be
31902 the problem.
31903 The most obvious symptom is probably that the titlebar at the top of the
31904 screen scrolls off the screen.
31905 Try setting KeyLabel Color to Default to see if that fixes the problem.
31906 <P>
31907 <A HREF="h_color_setup">Descriptions of the available commands</A>
31908 <P>
31909 Look <A HREF="h_edit_nav_cmds">here</A>
31910 to see the available Editing and Navigation commands.
31911 <P>
31912 <End of help on this topic>
31913 </BODY>
31914 </HTML>
31915 ====== h_config_keyname_color =====
31916 <HTML>
31917 <HEAD>
31918 <TITLE>OPTION: KeyName Color</TITLE>
31919 </HEAD>
31920 <BODY>
31921 <H1>OPTION: KeyName Color</H1>
31923 Sets the color Alpine uses for the names of the keys in the two-line
31924 menu at the bottom of the screen.
31925 For example, some of the screens have a "P PrevMsg" command.
31926 This option sets the color used when displaying the "P".
31927 The foreground color is the color of the actual character and the
31928 background color is the color of the area behind the character.
31929 By default, the KeyName Color is the same as the Reverse Color.
31930 <P>
31931 <A HREF="h_color_setup">Descriptions of the available commands</A>
31932 <P>
31933 Look <A HREF="h_edit_nav_cmds">here</A>
31934 to see the available Editing and Navigation commands.
31935 <P>
31936 <End of help on this topic>
31937 </BODY>
31938 </HTML>
31939 ====== h_config_slctbl_color =====
31940 <HTML>
31941 <HEAD>
31942 <TITLE>OPTION: Selectable Item Color</TITLE>
31943 </HEAD>
31944 <BODY>
31945 <H1>OPTION: Selectable Item Color</H1>
31947 Sets the color Alpine uses for selectable items, such as URLs.
31948 The foreground color is the color of the actual character and the
31949 background color is the color of the area behind the character.
31950 By default, the Selectable Item Color is the same as the Normal Color,
31951 except that it is bold.
31952 <P>
31953 <A HREF="h_color_setup">Descriptions of the available commands</A>
31954 <P>
31955 Look <A HREF="h_edit_nav_cmds">here</A>
31956 to see the available Editing and Navigation commands.
31957 <P>
31958 <End of help on this topic>
31959 </BODY>
31960 </HTML>
31961 ====== h_config_quote_color =====
31962 <HTML>
31963 <HEAD>
31964 <TITLE>OPTION: Quote Colors</TITLE>
31965 </HEAD>
31966 <BODY>
31967 <H1>OPTION: Quote Colors</H1>
31969 Sets the colors Alpine uses for coloring quoted text in the MESSAGE TEXT
31970 screen.
31971 If a line begins with a > character (or space followed by >)
31972 it is considered a quote.
31973 That line will be given the Quote1 Color (first level quote).
31974 If there is a second level of quoting then the Quote2 Color will be used.
31975 Alpine considers there to be a second level of quoting if that first > is
31976 followed by another > (or space followed by >).
31977 If there are characters other than whitespace and > signs, then it isn't
31978 considered another level of quoting.
31979 Similarly, if there is a third level of quoting the Quote3 Color will be
31980 used.
31981 If there are more levels after that the Quote Colors are re-used.
31982 If you define all three colors then it would repeat like Color1, Color2, Color3,
31983 Color1, Color2, Color3, ...
31984 If you only define the first two it would be
31985 Color1, Color2, Color1, Color2, ...
31986 If you define only the Quote1 Color, then the entire quote would be that
31987 color regardless of the quoting levels.
31988 By default, the Quote1 Color is black characters on a greenish-blue background;
31989 the Quote2 Color is black characters on a dull yellow background; and
31990 the Quote3 Color is black characters on a green background.
31991 <P>
31992 <A HREF="h_color_setup">Descriptions of the available commands</A>
31993 <P>
31994 Look <A HREF="h_edit_nav_cmds">here</A>
31995 to see the available Editing and Navigation commands.
31996 <P>
31997 <End of help on this topic>
31998 </BODY>
31999 </HTML>
32000 ====== h_config_folder_color =====
32001 <HTML>
32002 <HEAD>
32003 <TITLE>OPTION: Folder Color</TITLE>
32004 </HEAD>
32005 <BODY>
32006 <H1>OPTION: Folder Color</H1>
32008 Sets the colors Alpine uses for coloring a folder in the FOLDER LIST
32009 screen. By default, the Folder Color is the normal text color.
32011 <P>
32012 If you set a color for this feature, other than the normal color
32013 (the default), or a color for
32014 <A HREF="h_config_directory_color">Directory Color</A>, then directories
32015 will be colored according to the color specified in the
32016 <A HREF="h_config_directory_color">Directory Color</A> option. In this
32017 case, the color will be the only indication that the colored name
32018 refers to a directory. The normal behavior is that Alpine
32019 indicates that a name refers to a directory by appending a
32020 separator (like "/" or ".") to the name of
32021 the folder.
32023 <P>
32024 If a folder is a directory, then the folder name will be painted
32025 according to the color defined by this variable, and a separator
32026 indicator (like "/" or ".") will be added
32027 to the name. That
32028 indicator will be painted according to the color defined in the
32029 <A HREF="h_config_directory_color">Directory Color</A> option.
32031 <P>
32032 <End of help on this topic>
32033 </BODY>
32034 </HTML>
32035 ====== h_config_directory_color =====
32036 <HTML>
32037 <HEAD>
32038 <TITLE>OPTION: Directory Color</TITLE>
32039 </HEAD>
32040 <BODY>
32041 <H1>OPTION: Directory Color</H1>
32043 Sets the colors Alpine uses for coloring a directory in the FOLDER LIST
32044 screen. By default, the Folder Color is the normal text color.
32045 <P>
32046 If you set a color for this feature, other than the normal color
32047 (the default), or a color for
32048 <A HREF="h_config_folder_color">Folder Color</A>, then folders
32049 will be colored according to the color specified in the
32050 <A HREF="h_config_folder_color">Folder Color</A> option. In this
32051 case, the color will be the only indication that the colored name
32052 refers to a directory. The normal behavior is that Alpine
32053 indicates that a name refers to a directory by appending a
32054 separator (like "/" or ".") to the name of
32055 the folder.
32056 <P>
32057 If a folder is a directory, then the folder name will be painted
32058 according to the color defined by the option
32059 <A HREF="h_config_folder_color">Folder Color</A>, and the separator
32060 indicator (like "/" or ".") will be added
32061 after the name. That
32062 indicator will be painted according to the color defined in this
32063 option.
32064 <P>
32065 <End of help on this topic>
32066 </BODY>
32067 </HTML>
32068 ====== h_config_folder_list_color =====
32069 <HTML>
32070 <HEAD>
32071 <TITLE>OPTION: Folder-List Color</TITLE>
32072 </HEAD>
32073 <BODY>
32074 <H1>OPTION: Folder-List Color</H1>
32076 Sets the colors Alpine uses for coloring normal text in the FOLDER LIST
32077 screen. By default, the Folder-List Color is the normal text color.
32078 <P>
32079 This text refers to the informative text that Alpine displays so you
32080 can recognize each collection. The color of the content of each collection
32081 is determined by the options <A HREF="h_config_folder_color">Folder Color</A>
32082 and <A HREF="h_config_directory_color">Directory Color</A>.
32083 <P>
32084 Unlike the options
32085 <A HREF="h_config_folder_color">Folder Color</A>
32086 and <A HREF="h_config_directory_color">Directory Color</A>, configuring
32087 this option does not affect the way that Alpine reports folders,
32088 directories and folders that are directories.
32089 <P>
32090 <End of help on this topic>
32091 </BODY>
32092 </HTML>
32093 ====== h_config_incunseen_color =====
32094 <HTML>
32095 <HEAD>
32096 <TITLE>OPTION: Incoming Unseen Color</TITLE>
32097 </HEAD>
32098 <BODY>
32099 <H1>OPTION: Incoming Unseen Color</H1>
32101 If the option
32102 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
32103 is turned on it is possible to highlight the folders that contain
32104 unseen messages by coloring them with this color.
32105 By default, this is the same as the Normal Color and no highlighting is done.
32106 <P>
32107 Usually the "current" folder (the folder the cursor is on)
32108 is highlighted using reverse video.
32109 If the current folder is colored because it contains unseen messages then
32110 the color used to show that it is also the current folder is controlled
32111 by the
32112 <A HREF="h_config_index_color_style"><!--#echo var="VAR_current-indexline-style"--></A>
32113 feature at the top of the SETUP COLOR screen.
32114 <P>
32115 <A HREF="h_color_setup">Descriptions of the available commands</A>
32116 <P>
32117 Look <A HREF="h_edit_nav_cmds">here</A>
32118 to see the available Editing and Navigation commands.
32119 <P>
32120 <End of help on this topic>
32121 </BODY>
32122 </HTML>
32123 ====== h_config_signature_color =====
32124 <HTML>
32125 <HEAD>
32126 <TITLE>OPTION: Signature Color</TITLE>
32127 </HEAD>
32128 <BODY>
32129 <H1>OPTION: Signature Color</H1>
32131 Sets the color Alpine uses for coloring the signature in the MESSAGE TEXT
32132 screen. According to USENET conventions, the signature is defined as the
32133 paragraph following the "sigdashes", that is, the special line
32134 consisting of the three characters
32135 "-- " (i.e., dash, dash, and space). Alpine allows for one
32136 empty line right after the sigdashes to be considered as part of the
32137 signature.
32138 By default, the Signature Color is blue characters on a white background.
32139 <P>
32140 <A HREF="h_color_setup">Descriptions of the available commands</A>
32141 <P>
32142 Look <A HREF="h_edit_nav_cmds">here</A>
32143 to see the available Editing and Navigation commands.
32144 <P>
32145 <End of help on this topic>
32146 </BODY>
32147 </HTML>
32148 ====== h_config_prompt_color =====
32149 <HTML>
32150 <HEAD>
32151 <TITLE>OPTION: Prompt Color</TITLE>
32152 </HEAD>
32153 <BODY>
32154 <H1>OPTION: Prompt Color</H1>
32156 Sets the color Alpine uses for confirmation prompts and questions that
32157 appear in the status line near the bottom of the screen.
32158 The foreground color is the color of the actual character and the
32159 background color is the color of the area behind the character.
32160 By default, the Prompt Color is the same as the Reverse Color.
32161 <P>
32162 <A HREF="h_color_setup">Descriptions of the available commands</A>
32163 <P>
32164 Look <A HREF="h_edit_nav_cmds">here</A>
32165 to see the available Editing and Navigation commands.
32166 <P>
32167 <End of help on this topic>
32168 </BODY>
32169 </HTML>
32170 ====== h_config_header_general_color =====
32171 <HTML>
32172 <HEAD>
32173 <TITLE>OPTION: Header General Color</TITLE>
32174 </HEAD>
32175 <BODY>
32176 <H1>OPTION: Header General Color</H1>
32178 Sets the color Alpine uses for the headers of a message in the MESSAGE TEXT
32179 screen.
32180 The foreground color is the color of the actual character and the
32181 background color is the color of the area behind the character.
32182 By default, this is the same as the Normal Color.
32183 <P>
32184 It is also possible to set the colors for specific header fields, for
32185 example the Subject, using
32186 <A HREF="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></A>.
32187 If both a Header General Color and a specific Viewer Header Color are set
32188 the specific color will override the general color, as you would expect.
32189 <P>
32190 <A HREF="h_color_setup">Descriptions of the available commands</A>
32191 <P>
32192 Look <A HREF="h_edit_nav_cmds">here</A>
32193 to see the available Editing and Navigation commands.
32194 <P>
32195 <End of help on this topic>
32196 </BODY>
32197 </HTML>
32198 ====== h_config_incol =====
32199 <HTML>
32200 <HEAD>
32201 <TITLE>Index Line Color</TITLE>
32202 </HEAD>
32203 <BODY>
32204 <H1>Index Line Color</H1>
32206 This option is used to set the color of a line in the index when the
32207 message for that line matches the Pattern.
32208 This colors the whole index line, except possibly the status letters,
32209 which may be colored separately using the
32210 <A HREF="h_color_setup">Setup Kolor</A> screen.
32211 The foreground color is the color of the actual characters and the
32212 background color is the color of the area behind the characters.
32213 <P>
32214 <A HREF="h_color_setup">Descriptions of the available commands</A>
32215 <P>
32216 Look <A HREF="h_edit_nav_cmds">here</A>
32217 to see the available Editing and Navigation commands.
32218 <P>
32219 <End of help on this topic>
32220 </BODY>
32221 </HTML>
32222 ====== h_config_usetransparent_color =====
32223 <HTML>
32224 <HEAD>
32225 <TITLE>OPTION: Use Transparent Color</TITLE>
32226 </HEAD>
32227 <BODY>
32228 <H1>OPTION: Use Transparent Color</H1>
32230 This is a special color supported by some terminal emulators.
32231 It is intended to result in the default foreground or background color
32232 from the terminal emulator.
32233 This is the color the terminal was displaying characters in before you started Alpine.
32234 The reason it is called Transparent is because you could set the foreground color
32235 to some specific color, like Red, and then set the background color to the
32236 Transparent Color. If it works as expected, the background color from the terminal
32237 window in which Alpine is running will show through but with the Red characters
32238 in the foreground.
32239 <P>
32240 <A HREF="h_color_setup">Descriptions of the available commands</A>
32241 <P>
32242 Look <A HREF="h_edit_nav_cmds">here</A>
32243 to see the available Editing and Navigation commands.
32244 <P>
32245 <End of help on this topic>
32246 </BODY>
32247 </HTML>
32248 ====== h_config_usenormal_color =====
32249 <HTML>
32250 <HEAD>
32251 <TITLE>OPTION: Use Normal Color</TITLE>
32252 </HEAD>
32253 <BODY>
32254 <H1>OPTION: Use Normal Color</H1>
32256 When you use this color value, the actual color used will be the same
32257 as the corresponding Normal Color.
32258 For example if your Normal Color is black on white and you set both
32259 the foreground and background colors here to use the Normal Color, you'll
32260 get black on white. If you later change the Normal Color to red on blue
32261 this color will also change to red on blue.
32262 <P>
32263 <A HREF="h_color_setup">Descriptions of the available commands</A>
32264 <P>
32265 Look <A HREF="h_edit_nav_cmds">here</A>
32266 to see the available Editing and Navigation commands.
32267 <P>
32268 <End of help on this topic>
32269 </BODY>
32270 </HTML>
32271 ====== h_config_usenone_color =====
32272 <HTML>
32273 <HEAD>
32274 <TITLE>OPTION: Use None Color</TITLE>
32275 </HEAD>
32276 <BODY>
32277 <H1>OPTION: Use None Color</H1>
32279 This is a special color that simply means to leave the color alone.
32280 It is useful for Index symbols and for Keyword Colors used in the Subject
32281 field of an index line.
32282 The most likely use is to set an explicit foreground color and then set
32283 the background color to the None Color.
32284 That will cause the symbol or keyword to be drawn in the foreground color
32285 with a background equal to whatever color the rest of the index line is already
32286 drawn in.
32287 You will see no visible effect unless you have assigned Indexcolor Rules to
32288 color index lines or you have set an actual color for the Reverse Color.
32289 <P>
32290 <A HREF="h_color_setup">Descriptions of the available commands</A>
32291 <P>
32292 Look <A HREF="h_edit_nav_cmds">here</A>
32293 to see the available Editing and Navigation commands.
32294 <P>
32295 <End of help on this topic>
32296 </BODY>
32297 </HTML>
32298 ====== h_config_dflt_color =====
32299 <HTML>
32300 <HEAD>
32301 <TITLE>OPTION: Default Color</TITLE>
32302 </HEAD>
32303 <BODY>
32304 <H1>OPTION: Default Color</H1>
32306 Setting default will cause the color to be the default color.
32307 Unsetting default is normally done by choosing a color, but in some cases
32308 you may want to declare the current default color to be your non-default
32309 choice.
32310 For example, the default Keyname Color is the same as the Reverse Color.
32311 Whenever the Reverse Color changes the Keyname Color will also change, unless
32312 you've changed it or unset the default box.
32313 <P>
32314 <A HREF="h_color_setup">Descriptions of the available commands</A>
32315 <P>
32316 Look <A HREF="h_edit_nav_cmds">here</A>
32317 to see the available Editing and Navigation commands.
32318 <P>
32319 <End of help on this topic>
32320 </BODY>
32321 </HTML>
32322 ====== h_config_bold_slctbl =====
32323 <HTML>
32324 <HEAD>
32325 <TITLE>OPTION: Bold</TITLE>
32326 </HEAD>
32327 <BODY>
32328 <H1>OPTION: Bold</H1>
32330 The color for this particular section may have the Bold attribute turned
32331 on or off.
32332 Setting bold will cause the characters to be bold.
32333 <P>
32334 <A HREF="h_color_setup">Descriptions of the available commands</A>
32335 <P>
32336 Look <A HREF="h_edit_nav_cmds">here</A>
32337 to see the available Editing and Navigation commands.
32338 <P>
32339 <End of help on this topic>
32340 </BODY>
32341 </HTML>
32342 ====== h_config_kw_color =====
32343 <HTML>
32344 <HEAD>
32345 <TITLE>OPTION: Keyword Colors</TITLE>
32346 </HEAD>
32347 <BODY>
32348 <H1>OPTION: Keyword Colors</H1>
32350 Sets the colors Alpine uses for Keyword fields in the MESSAGE INDEX screen.
32351 Keywords are displayed as part of the Subject by default.
32352 They are also displayed as part of the Subject if the tokens
32353 "SUBJKEY", "SUBJKEYTEXT", "SUBJKEYINIT", or "SUBJKEYINITTEXT" are used in the
32354 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
32355 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
32356 screen by using the "KEY" or "KEYINIT" tokens.
32357 <P>
32358 For example, you might have set up a Keyword
32359 "Work" using the
32360 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
32361 You could cause that Keyword to show up as a special color
32362 by setting up the Keyword Color using this option, and then including it
32363 in the MESSAGE INDEX screen using one of the tokens listed above in the
32364 <!--#echo var="VAR_index-format"-->.
32365 <P>
32366 <A HREF="h_color_setup">Descriptions of the available commands</A>
32367 <P>
32368 Look <A HREF="h_edit_nav_cmds">here</A>
32369 to see the available Editing and Navigation commands.
32370 <P>
32371 <End of help on this topic>
32372 </BODY>
32373 </HTML>
32374 ====== h_config_customhdr_color =====
32375 <HTML>
32376 <HEAD>
32377 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></TITLE>
32378 </HEAD>
32379 <BODY>
32380 <H1>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></H1>
32382 Sets the colors Alpine uses for specific header fields in the MESSAGE TEXT screen.
32383 For example, you may set the color of the Subject header or the From header.
32384 The foreground color is the color of the actual character and the
32385 background color is the color of the area behind the character.
32386 <P>
32387 In addition to setting the colors for particular headers (like the Subject)
32388 you may also set a color to be used for all headers unless overridden by a
32389 more specific Viewer Header Color.
32390 To do this use the
32391 <A HREF="h_config_header_general_color">Header General Color</A>.
32392 <P>
32393 For Header Colors,
32394 there is an additional line on the
32395 screen labeled "Pattern to match".
32396 If you leave that blank, then the whole field for that header will
32397 be colored.
32398 However, if you give a pattern to match, the coloring will only take place
32399 if there is a match for that pattern in the value of the field.
32400 For example, if you are working on a color for the Subject header and
32401 you fill in a pattern of "important", then only Subjects that
32402 contain the word "important" will be colored.
32403 <P>
32404 If the pattern you enter is a comma-separated list of patterns, then coloring
32405 happens if any of those patterns matches.
32406 <P>
32407 <A HREF="h_color_setup">Descriptions of the available commands</A>
32408 <P>
32409 Look <A HREF="h_edit_nav_cmds">here</A>
32410 to see the available Editing and Navigation commands.
32411 <P>
32412 <End of help on this topic>
32413 </BODY>
32414 </HTML>
32415 ====== h_config_indextoken_color =====
32416 <HTML>
32417 <HEAD>
32418 <TITLE>OPTION: <!--#echo var="VAR_index-token-colors"--></TITLE>
32419 </HEAD>
32420 <BODY>
32421 <H1>OPTION: <!--#echo var="VAR_index-token-colors"--></H1>
32423 This option allows you to set up the color in which any token, not specified by the
32424 previous options, will be colored in the MESSAGE INDEX screen.
32425 <P>
32426 In order to use this option, you must press the "I" <B>IndxHdr</B> command, and add
32427 a token that can be used in the index format.
32428 The list of available tokens is <A HREF="h_index_tokens">here</A>.
32429 <P>
32430 If you fail to enter a valid token your entry will be ignored, and you will be asked to
32431 enter a new one. Once you have entered a valid token, a line will be added to the
32432 configuration screen that you can use to set up the colors in which that token will
32433 be painted. This is done in the same way that you configure colors for other
32434 variables.
32436 <A HREF="h_color_setup">Descriptions of the available commands</A>
32437 <P>
32438 Look <A HREF="h_edit_nav_cmds">here</A>
32439 to see the available Editing and Navigation commands.
32440 <P>
32441 <End of help on this topic>
32442 </BODY>
32443 </HTML>
32444 ====== h_config_customhdr_pattern =====
32445 <HTML>
32446 <HEAD>
32447 <TITLE>OPTION: Viewer Header Color Pattern</TITLE>
32448 </HEAD>
32449 <BODY>
32450 <H1>OPTION: Viewer Header Color Pattern</H1>
32452 If you leave this blank, then the whole field for the header will
32453 be colored.
32454 If you give a pattern to match, the coloring will only take place
32455 if there is a match for that pattern in the value of the field.
32456 For example, if you are working on a color for the Subject header and
32457 you fill in a pattern of "important", then only Subjects that
32458 contain the word "important" will be colored.
32459 <P>
32460 For address headers (like From and To) and for the Newsgroups header,
32461 a pattern match will cause only the matched addresses or newsgroups to be
32462 colored.
32463 If there is no pattern to match, then all of the addresses or newsgroups
32464 in the relevant header will be colored.
32465 <P>
32466 The matching pattern may be a comma-separated list of patterns to match
32467 instead of a single pattern.
32468 For example, you could use the pattern "important,urgent" which would
32469 cause a match if either the word "important" or the word
32470 "urgent" appeared in the value of the header.
32471 You could list several comma-separated email addresses in the Header
32472 From Color pattern so that those addresses will be colored when any of
32473 them appear in the From header.
32474 <P>
32475 To add a new matching pattern or change the existing pattern use the
32476 <!--chtml if pinemode="function_key"-->
32477 "F4"
32478 <!--chtml else-->
32479 "C"
32480 <!--chtml endif-->
32481 "Change" command that is available when the "Pattern to
32482 match" line is highlighted.
32483 The
32484 <!--chtml if pinemode="function_key"-->
32485 "F10"
32486 <!--chtml else-->
32487 "D"
32488 <!--chtml endif-->
32489 "Delete" command may be used to quickly remove all patterns
32490 for a particular header.
32491 <P>
32492 <End of help on this topic>
32493 </BODY>
32494 </HTML>
32495 ====== h_color_setup =====
32496 <HTML>
32497 <HEAD>
32498 <TITLE>SETUP COLOR COMMANDS</TITLE>
32499 </HEAD>
32500 <BODY>
32501 <H1>SETUP COLOR COMMANDS</H1>
32502 <!--chtml if pinemode="function_key"-->
32503 <PRE>
32504 Available Commands -- Group 1
32505 -------------------------------
32506 F1 Display this help text
32507 F2 Show other available commands
32508 F3 Exit to MAIN MENU
32509 F4 Select the highlighted foreground or background color
32510 F5 Move to previous line
32511 F6 Move to next line
32512 F7 Previous page
32513 F8 Next page
32514 F9 Add a config section for a header field
32515 F10 Restore all default colors (for all sections)
32516 F11 Print color configuration screen
32517 F12 Whereis (search for word)
32519 Available Commands -- Group 2
32520 -------------------------------
32521 F1 Display this help text
32522 F2 Show other available commands
32523 F5 Delete config section for highlighted header field
32524 F6 Shuffle the order of Header Color sections
32525 </PRE>
32526 <!--chtml else-->
32527 <PRE>
32528 General commands
32529 -------------------------------------------------
32530 ? Display this help text E Exit back to MAIN MENU
32531 P Previous Line N Next Line
32532 - Previous page Spc (space bar) Next page
32533 W WhereIs (search for word) % Print color configuration screen
32535 Color Setup Commands
32536 ------------------------------------------------
32537 * Select the highlighted foreground or background color
32538 A Add a config section for a header field
32539 D Delete config section for highlighted header field
32540 R Restore all default colors (for all sections)
32541 $ Shuffle the order of Header Color sections
32542 </PRE>
32543 <!--chtml endif-->
32545 <H2>Description of the Setup Color Screen</H2>
32547 From this screen you may turn on color and set the colors of
32548 various parts of the Alpine display.
32549 For help on turning on color move your cursor into the Color Style section
32550 at the top of the Setup Color screen and ask for help.
32552 <P>
32553 There are several sections in the Setup Color Screen.
32554 At the top are some settings that handle the style of color used
32555 with your terminal emulator (UNIX only), and some settings that
32556 control how the current indexline and the titlebar are colored.
32557 After that comes a long section called GENERAL COLORS that allows
32558 you to set the color of many elements in the Alpine screens.
32559 For example, the color of the titlebar, status messages,
32560 selectable links, quotes and signatures in messages, and so on.
32561 After that is a section called INDEX COLORS that allows you to
32562 set the colors of various pieces of the displayed index lines in
32563 the MESSAGE INDEX screen.
32564 The next section is HEADER COLORS. This is for coloring headers of
32565 messages in the MESSAGE TEXT screen in just about any way you would like.
32566 Finally, the KEYWORD COLORS section allows you to highlight
32567 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
32568 in the MESSAGE INDEX screen.
32570 <P>
32571 To change a color, highlight the color you want to change (for example,
32572 the Status Color) by moving
32573 the cursor into it.
32574 You may want to read the help text for the color to see a brief desription
32575 of what you are coloring.
32576 Then press "C" for Change to set the color to something new.
32577 That will put you into a screen with two columns of colors, one for
32578 the foreground color and one for the background color.
32579 The foreground color is just the color you want the actual characters
32580 to be and the background color is the color of the rest of the rectangle
32581 behind the characters.
32582 Select the foreground and background colors desired by using the Next and
32583 Prev keys to highlight the color, and the * command to select it.
32584 <P>
32585 To set a color to its default value, set the X in the Default line at
32586 the bottom of the list of colors.
32587 <P>
32589 The HEADER COLORS section is a little bit different from the others.
32590 Besides coloring the specific fields that Alpine knows about, you may also
32591 color specific header fields when viewing a message in the MESSAGE TEXT
32592 screen.
32593 For example, you may color the Subject header a particular color.
32594 There are a few commands for use with headers.
32595 The "AddHeader" command adds a section to the color
32596 configuration screen that allows you to set the color for that header.
32597 You'll be asked for the name of the header field you want to color.
32598 If you wanted to color the Subject, you would answer
32599 with the word "subject".
32600 Once you've added a header field, the color setting works just like the
32601 other color fields, except that there is an additional line on the
32602 configuration screen labeled "Pattern to match".
32603 If you leave that blank, then the whole field for that header will always
32604 be colored.
32605 However, if you give a pattern to match, the coloring will only take place
32606 if there is a match for that pattern in the value of the field.
32607 For example, if you are working on a color for the Subject header and
32608 you fill in a pattern of "important", then only Subjects that
32609 contain the word "important" will be colored.
32610 <P>
32611 The "DeleteHdr" command removes a header section from the
32612 configuration altogether.
32613 The "Shuffle" command changes the order of header sections.
32614 This is only necessary if you use header sections with pattern fields.
32615 For example, if you have two Subject sections, one with one pattern and
32616 another with another pattern, and the subject for a particular message
32617 happens to match both, then the color from the first match is used.
32618 <P>
32620 The command "RestoreDefs" will restore all of the default colors.
32621 Each section will change to the default value used for that section when
32622 color is first enabled.
32623 When you restore all default colors the color settings for the Header Colors
32624 will be unset (since that's the default), but the header fields you've
32625 added will remain so that you may easily reset them.
32626 In order to get rid of them completely you'd have to use
32627 the "DeleteHdr" command.
32629 <P>
32630 Remember that <A HREF="h_rules_incols">Index Line Colors</A>
32631 may be set with matching rules and that is configured separately from
32632 the rest of the color settings described here.
32633 It is configured in the Setup/Rules/Indexcolors section of the configuration screen
32634 instead of in the Setup/Kolor section.
32636 <P><UL>
32637 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32638 </UL><P>
32639 <End of help on this topic>
32640 </BODY>
32641 </HTML>
32642 ====== h_config_news_uses_recent ======
32643 <HTML>
32644 <HEAD>
32645 <TITLE>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></TITLE>
32646 </HEAD>
32647 <BODY>
32648 <H1>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></H1>
32650 This feature causes certain messages to be marked as "New" in the
32651 MESSAGE INDEX of newsgroups.
32652 This feature is set by default.
32654 <P>
32656 When opening a newsgroup, Alpine will consult your "newsrc" file and
32657 determine the last message you have previously disposed of via the "D"
32658 key. If this feature is set, any subsequent messages will be shown in the
32659 Index with an "N", and the first of these messages will be highlighted.
32660 Although this is only an approximation of true "New" or "Unseen"
32661 status, it provides a useful cue to distinguish more-or-less recent
32662 messages from those you have seen previously, but are not yet ready to
32663 mark deleted.
32665 <P>
32667 Background: your "newsrc" file (used to store message status information
32668 for newsgroups) is only capable of storing a single flag, and Alpine uses
32669 this to record whether or not you are "done with" a message, as
32670 indicated by marking the message as "Deleted". Unfortunately, this
32671 means that Alpine has no way to record exactly which messages you have
32672 previously seen, so it normally does not show the "N" status flag for
32673 any messages in a newsgroup. This feature enables a starting
32674 *approximation* of seen/unseen status that may be useful.
32675 <P>
32676 <End of help on this topic>
32677 </BODY>
32678 </HTML>
32679 ====== h_config_expose_hidden_config =====
32680 <HTML>
32681 <HEAD>
32682 <TITLE>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></TITLE>
32683 </HEAD>
32684 <BODY>
32685 <H1>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></H1>
32687 If set, this causes configuration options and features that are normally
32688 hidden from view to be editable in the Setup/Config screen.
32690 <P>
32691 The purpose of this feature is to allow you to change configuration
32692 features and variables that are normally hidden.
32693 This is particularly useful if you are using a remote configuration,
32694 where it is difficult to edit the contents manually, but it may also be used
32695 on a local pinerc configuration file.
32696 <P>
32697 If set, several configuration variables and features that are normally
32698 hidden from view will show up in the Setup/Configuration screen.
32699 They will be at the bottom of the configuration screen.
32700 You can find them by searching for the words "hidden configuration".
32701 <P>
32703 Note that this is an advanced feature that should be used with care.
32704 The reason that this part of the configuration is normally hidden is because
32705 there is a significant potential for causing problems if you change these
32706 variables.
32707 If something breaks after a change try changing it back to see if that is
32708 what is causing the problem.
32709 There are also some variables that are normally hidden because they are
32710 manipulated through Alpine in other ways.
32711 For example, colors are normally set using the Setup/Kolors screen and
32712 the "<!--#echo var="VAR_address-book"-->" variable is normally set using
32713 the Setup/AddressBooks screen, so there is little reason to edit these directly.
32714 The "<!--#echo var="VAR_incoming-folders"-->" variable is normally changed by using
32715 the Add, Delete, and Rename commands in the FOLDER LIST screen,
32716 and the "<!--#echo var="VAR_last-time-prune-questioned"-->" variable is normally used
32717 internally by Alpine and not set directly by the user.
32718 <P>
32719 <UL>
32720 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32721 </UL><P>
32722 <End of help on this topic>
32723 </BODY>
32724 </HTML>
32725 ====== h_config_disable_signature_edit =====
32726 <HTML>
32727 <HEAD>
32728 <TITLE>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></TITLE>
32729 </HEAD>
32730 <BODY>
32731 <H1>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></H1>
32733 If set, this disables the editing of signature files from within
32734 the Setup/Config screen.
32735 <P>
32736 <UL>
32737 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32738 </UL><P>
32739 <End of help on this topic>
32740 </BODY>
32741 </HTML>
32742 ====== h_config_disable_roles_templateedit =====
32743 <HTML>
32744 <HEAD>
32745 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></TITLE>
32746 </HEAD>
32747 <BODY>
32748 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></H1>
32750 If set, this disables the editing of template files within the
32751 Role setup screen.
32752 <P>
32753 <UL>
32754 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32755 </UL><P>
32756 <End of help on this topic>
32757 </BODY>
32758 </HTML>
32759 ====== h_config_disable_roles_sigedit =====
32760 <HTML>
32761 <HEAD>
32762 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></TITLE>
32763 </HEAD>
32764 <BODY>
32765 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></H1>
32767 If set, this disables the editing of signature files within the
32768 Role setup screen.
32769 <P>
32770 <UL>
32771 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32772 </UL><P>
32773 <End of help on this topic>
32774 </BODY>
32775 </HTML>
32776 ====== h_config_disable_roles_setup =====
32777 <HTML>
32778 <HEAD>
32779 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></TITLE>
32780 </HEAD>
32781 <BODY>
32782 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></H1>
32784 If set, this disables the Setup/Rules/Roles command.
32785 <P>
32786 <UL>
32787 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32788 </UL><P>
32789 <End of help on this topic>
32790 </BODY>
32791 </HTML>
32792 ====== h_config_disable_pipes_in_templates =====
32793 <HTML>
32794 <HEAD>
32795 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></TITLE>
32796 </HEAD>
32797 <BODY>
32798 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></H1>
32800 By default, if a template file name is followed by a vertical bar (|) then
32801 that causes the file to be executed to produce the text for the template.
32802 If this feature is set, then this is not allowed.
32803 <P>
32804 <UL>
32805 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32806 </UL><P>
32807 <End of help on this topic>
32808 </BODY>
32809 </HTML>
32810 ====== h_config_disable_pipes_in_sigs =====
32811 <HTML>
32812 <HEAD>
32813 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></TITLE>
32814 </HEAD>
32815 <BODY>
32816 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></H1>
32818 By default, if a signature file name is followed by a vertical bar (|) then
32819 that causes the file to be executed to produce the text for the signature.
32820 If this feature is set, then this is not allowed.
32821 <P>
32822 <UL>
32823 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32824 </UL><P>
32825 <End of help on this topic>
32826 </BODY>
32827 </HTML>
32828 ====== h_config_disable_password_cmd =====
32829 <HTML>
32830 <HEAD>
32831 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></TITLE>
32832 </HEAD>
32833 <BODY>
32834 <H1>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></H1>
32836 If set, then the Setup/Newpassword command is disabled.
32837 <P>
32838 <UL>
32839 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32840 </UL><P>
32841 <End of help on this topic>
32842 </BODY>
32843 </HTML>
32844 ====== h_config_disable_password_caching =====
32845 <HTML>
32846 <HEAD>
32847 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></TITLE>
32848 </HEAD>
32849 <BODY>
32850 <H1>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></H1>
32852 Normally, loginname/password combinations are cached in Alpine so that
32853 you do not have to enter the same password more than once in a session.
32854 A disadvantage to this approach is that the password must be stored in
32855 the memory image of the running Alpine in order that it can be re-used.
32856 In the event that Alpine crashes and produces a core dump, and that core
32857 dump is readable by others, the loginname and password could be read
32858 from the core dump.
32859 <P>
32860 If this feature is set, then the passwords will not be cached and you
32861 will have to retype the password whenever Alpine needs it.
32862 Even with this feature set there is still some chance that the core
32863 file will contain a password, so care should be taken to make the
32864 core files unreadable.
32865 <P>
32866 NOTE: If PASSFILE caching is enabled, this does not disable it.
32867 That is a separate and independent feature.
32868 <UL>
32869 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32870 </UL><P>
32871 <End of help on this topic>
32872 </BODY>
32873 </HTML>
32874 ====== h_config_disable_password_file_saving =====
32875 <HTML>
32876 <HEAD>
32877 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></TITLE>
32878 </HEAD>
32879 <BODY>
32880 <H1>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></H1>
32882 This feature changes the behavior of Alpine when a login name and password combination
32883 for a specific server is not found in the password file. The default behavior is that
32884 Alpine will ask the user if they wish to save this information in the password file for future
32885 use. It is assumed that if a user created a password file it is because they intend
32886 to use it, but in some instances a user might want to save some passwords and not others.
32887 In this case, enabling this feature will make Alpine not add any more passwords to the
32888 password file and will only use the passwords that it already saved. If you wish to allow
32889 Alpine to save more passwords in the password file, disable this feature.
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_kb_lock =====
32898 <HTML>
32899 <HEAD>
32900 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></TITLE>
32901 </HEAD>
32902 <BODY>
32903 <H1>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></H1>
32905 If set, then the Keyboard Lock command is removed from the MAIN MENU.
32906 <P>
32907 <UL>
32908 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32909 </UL><P>
32910 <End of help on this topic>
32911 </BODY>
32912 </HTML>
32913 ====== h_config_disable_config_cmd =====
32914 <HTML>
32915 <HEAD>
32916 <TITLE>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></TITLE>
32917 </HEAD>
32918 <BODY>
32919 <H1>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></H1>
32921 If set, then the Setup/Config screen is disabled.
32922 <P>
32923 <UL>
32924 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32925 </UL><P>
32926 <End of help on this topic>
32927 </BODY>
32928 </HTML>
32929 ====== h_config_allow_chg_from =====
32930 <HTML>
32931 <HEAD>
32932 <TITLE>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></TITLE>
32933 </HEAD>
32934 <BODY>
32935 <H1>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></H1>
32937 This feature affects Alpine's handling of the "From:" header field
32938 in the "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" configuration
32939 option.
32940 <P>
32941 If this feature is set then the From line can be changed just like
32942 all the other header fields that can be changed.
32943 This feature defaults to <EM>ON</EM>.
32944 <P>
32945 Even with this feature turned ON (the default) you will not be able
32946 to change the From header unless you add it to your list of
32947 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>.
32948 You may also want to change the
32949 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
32950 if you want the From header to always show up in the composer without
32951 having to type the Rich Headers command first.
32952 <P>
32953 Note that many sites restrict the use of this feature in order to
32954 reduce the chance of falsified addresses and misdirected mail.
32955 If you want to change the value of what gets included in the From header
32956 in messages you send
32957 look <A HREF="h_config_change_your_from">here</A> for a description.
32958 <P>
32959 <UL>
32960 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32961 </UL><P>
32962 <End of help on this topic>
32963 </BODY>
32964 </HTML>
32965 ====== h_config_disable_collate =====
32966 <HTML>
32967 <HEAD>
32968 <TITLE>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></TITLE>
32969 </HEAD>
32970 <BODY>
32971 <H1>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></H1>
32973 This is a hard to understand feature that should only be used in rare cases.
32974 Normally, the C function call
32975 <P>
32976 <CENTER><SAMP>setlocale(LC_COLLATE, "")</SAMP></CENTER>
32977 <P>
32978 is used by Alpine.
32979 If you want to try turning it off,
32980 setting this feature will turn it off.
32981 This part of the locale has to do with the sort order
32982 of characters in your locale.
32983 <P>
32984 <UL>
32985 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32986 </UL><P>
32987 <End of help on this topic>
32988 </BODY>
32989 </HTML>
32990 ====== h_config_quell_attach_extra_prompt =====
32991 <HTML>
32992 <HEAD>
32993 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></TITLE>
32994 </HEAD>
32995 <BODY>
32996 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></H1>
32998 By default, when you attempt to view an attachment externally
32999 from the "Attachment View" screen, you are asked if you
33000 really want to view the selected attachment.
33002 <P>
33003 If this feature is set, you will <B>not</B> be prompted to confirm
33004 your selection. Prior to Alpine and to Pine 4.50, the default behavior was to not
33005 prompt. This feature was added for those wanting to preserve that
33006 behavior (along with
33007 <A HREF="h_config_quell_attach_ext_warn"><!--#echo var="FEAT_quell-attachment-extension-warn"--></A>).
33009 <P>
33010 <UL>
33011 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33012 </UL><P>
33013 <End of help on this topic>
33014 </BODY>
33015 </HTML>
33016 ====== h_config_quell_attach_ext_warn =====
33017 <HTML>
33018 <HEAD>
33019 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></TITLE>
33020 </HEAD>
33021 <BODY>
33022 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></H1>
33024 <P>
33025 This feature suppresses the extra warning you can get when trying
33026 to view an attachment for which there is no mime-type match. Turning
33027 on this feature will just run the program according to extension
33028 instead of first warning the user that it will run according to the
33029 file's extension.
33030 <P>
33031 This feature can be used along side
33032 <A HREF="h_config_quell_attach_extra_prompt"><!--#echo var="FEAT_quell-attachment-extra-prompt"--></A>
33033 to preserve the behavior exhibited in Pine versions prior to Pine 4.50.
33034 <P>
33035 <UL>
33036 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33037 </UL><P>
33038 <End of help on this topic>
33039 </BODY>
33040 </HTML>
33041 ====== h_config_mailcap_params =====
33042 <HTML>
33043 <HEAD>
33044 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></TITLE>
33045 </HEAD>
33046 <BODY>
33047 <H1>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></H1>
33049 If set, this will allow mailcap named parameter substitution to occur
33050 in mailcap entries.
33051 By default, this is turned off to prevent security problems that may occur
33052 with some incorrect mailcap configurations.
33053 For more information, see RFC1524 and look for "named parameters" in the
33054 text of the RFC.
33055 <P>
33056 <UL>
33057 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33058 </UL><P>
33059 <End of help on this topic>
33060 </BODY>
33061 </HTML>
33062 ====== h_config_disable_shared =====
33063 <HTML>
33064 <HEAD>
33065 <TITLE>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></TITLE>
33066 </HEAD>
33067 <BODY>
33068 <H1>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></H1>
33070 If this feature is set, the automatic search for namespaces "ftp",
33071 "imapshared", and "imappublic" by the underlying library
33072 will be disabled.
33073 The reason this feature exists is because there are some implementations
33074 of system password lookup routines that are very slow when presented with
33075 a long loginname that does not exist.
33076 This feature could be set to prevent the delay at startup time when the
33077 names above are searched for in the password file.
33078 <P>
33079 <UL>
33080 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33081 </UL><P>
33082 <End of help on this topic>
33083 </BODY>
33084 </HTML>
33085 ====== h_config_hide_nntp_path =====
33086 <HTML>
33087 <HEAD>
33088 <TITLE>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></TITLE>
33089 </HEAD>
33090 <BODY>
33091 <H1>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></H1>
33093 Normally the Path header that Alpine generates when posting to a newsgroup
33094 contains the name of the computer from which the message is being sent and
33095 the user name.
33096 Some believe that this information is used by spammers.
33097 If this feature is set, that information will be replaced with the text
33098 <P>
33099 <CENTER><SAMP>not-for-mail</SAMP></CENTER>
33100 <P>
33101 instead.
33102 <P>
33103 It should be noted that many servers being connected to will still reveal
33104 the information that this feature attempts to protect.
33105 <P>
33106 <UL>
33107 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33108 </UL><P>
33109 <End of help on this topic>
33110 </BODY>
33111 </HTML>
33112 ====== h_config_no_bezerk_zone =====
33113 <HTML>
33114 <HEAD>
33115 <TITLE>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></TITLE>
33116 </HEAD>
33117 <BODY>
33118 <H1>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></H1>
33120 POSIX mandates a timezone in UNIX mailbox format folder delimiters
33121 (the line that begins with From <SPACE>).
33122 Some versions of Berkeley mail have trouble with this, and don't recognize
33123 the line as a message delimiter.
33124 If this feature is set, the timezone will be left off the delimiter line.
33125 <P>
33126 <UL>
33127 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33128 </UL><P>
33129 <End of help on this topic>
33130 </BODY>
33131 </HTML>
33132 ====== h_config_quell_domain_warn =====
33133 <HTML>
33134 <HEAD>
33135 <TITLE>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></TITLE>
33136 </HEAD>
33137 <BODY>
33138 <H1>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></H1>
33140 When your configuration is set up so that your domain name contains no dots,
33141 it is usually a configuration error.
33142 By default, Alpine will warn you about this when you start it up.
33143 You will see a warning message that looks like
33145 <P>
33146 <CENTER><SAMP>Incomplete maildomain "<domain>".</SAMP></CENTER>
33148 <P>
33149 If this feature is set, the warning is turned off.
33150 <P>
33151 <UL>
33152 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33153 </UL><P>
33154 <End of help on this topic>
33155 </BODY>
33156 </HTML>
33157 ====== h_config_quell_imap_env =====
33158 <HTML>
33159 <HEAD>
33160 <TITLE>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></TITLE>
33161 </HEAD>
33162 <BODY>
33163 <H1>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></H1>
33165 In the MESSAGE INDEX screen, if the open folder is being accessed
33166 using IMAP, Alpine normally tries to paint the index lines on the screen
33167 as soon as the information arrives from the IMAP server.
33168 This means that the index information makes it onto the screen more quickly
33169 than it otherwise would.
33170 This sometimes results in behavior that bothers some users.
33171 For example, when paging to a new page of the index, it may be possible for
33172 the lines to be painted on the screen in a random order, rather than from
33173 top to bottom.
33174 <P>
33176 Setting this feature causes Alpine to wait for all of the information
33177 to be gathered before it paints the index screen.
33178 Once it collects all of the information, the screen will be painted quickly
33179 from top to bottom.
33180 <P>
33181 <UL>
33182 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33183 </UL><P>
33184 <End of help on this topic>
33185 </BODY>
33186 </HTML>
33187 ====== h_config_quell_news_env =====
33188 <HTML>
33189 <HEAD>
33190 <TITLE>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></TITLE>
33191 </HEAD>
33192 <BODY>
33193 <H1>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></H1>
33195 In the MESSAGE INDEX screen, if the open folder is being accessed
33196 using NNTP (News), Alpine normally tries to paint the index lines on the screen
33197 as soon as the information arrives from the NNTP server.
33198 This means that the index information makes it onto the screen more quickly
33199 than it otherwise would.
33200 This sometimes results in behavior that bothers some users.
33201 For example, when paging to a new page of the index, it may be possible for
33202 the lines to be painted on the screen in a random order, rather than from
33203 top to bottom.
33204 <P>
33206 Setting this feature causes Alpine to wait for all of the information
33207 to be gathered before it paints the index screen.
33208 Once it collects all of the information, the screen will be painted quickly
33209 from top to bottom.
33210 <P>
33211 <UL>
33212 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33213 </UL><P>
33214 <End of help on this topic>
33215 </BODY>
33216 </HTML>
33217 ====== h_config_quell_content_id =====
33218 <HTML>
33219 <HEAD>
33220 <TITLE>FEATURE: <!--#echo var="FEAT_quell-content-id"--></TITLE>
33221 </HEAD>
33222 <BODY>
33223 <H1>FEATURE: <!--#echo var="FEAT_quell-content-id"--></H1>
33225 This feature changes the behavior of Alpine when sending messages.
33226 It is intended to work around a bug in Microsoft's Outlook XP mail user
33227 agent.
33228 As of this writing, Microsoft has acknowledged the bug but
33229 has not added it to the Knowledge Base.
33230 We have been told that there will be a post-SP1 hotfix for Outlook XP.
33231 This particular bug has bug fix number OfficeQFE:4781.
33232 The nature of the bug is that messages with attachments that
33233 contain a Content-ID header (which standard Alpine attachments do)
33234 do not show the attachment indicator (a paperclip) when viewed with
33235 Outlook XP.
33236 So the user has no indication that the message contains an attachment.
33238 <P>
33239 If this feature is set then Alpine will remove most Content-ID headers
33240 before sending a message.
33241 If an attachment is of type MESSAGE, then the existing Content-ID headers
33242 inside the message will be left intact.
33243 This would only happen with Alpine if a message was forwarded as an attachment
33244 or if a message with a message attached was forwarded.
33245 Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded,
33246 the Content-ID headers of the alternative parts will not be removed.
33248 <P>
33249 Because the Content-ID header is a standard part of MIME it is possible
33250 that setting this feature will break something.
33251 For example, if an attachment has a Content-ID header that is necessary
33252 for the correct functioning of that attachment, it is possible that Alpine
33253 may remove that header when the attachment is forwarded.
33254 However, it seems fairly safe at this time.
33256 <P>
33257 <UL>
33258 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33259 </UL><P>
33260 <End of help on this topic>
33261 </BODY>
33262 </HTML>
33263 ====== h_config_winpos_in_config =====
33264 <HTML>
33265 <HEAD>
33266 <TITLE>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></TITLE>
33267 </HEAD>
33268 <BODY>
33269 <H1>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></H1>
33271 PC-Alpine only.
33272 <P>
33274 Normally, PC-Alpine will store its window size and position in the
33275 Windows Registry.
33276 This is convenient if you want to use the same remote
33277 configuration from more than one PC.
33278 If you use multiple configuration files to start PC-Alpine, you may want
33279 to store the window size and position in the configuration file instead
33280 of in the Registry.
33281 Setting this feature causes the value to be stored in
33282 <A HREF="h_config_window_position">Window-Position</A>.
33284 <P>
33285 <UL>
33286 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33287 </UL><P>
33288 <End of help on this topic>
33289 </BODY>
33290 </HTML>
33291 ====== h_config_quell_ssl_largeblocks =====
33292 <HTML>
33293 <HEAD>
33294 <TITLE>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></TITLE>
33295 </HEAD>
33296 <BODY>
33297 <H1>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></H1>
33299 PC-Alpine only.
33300 <P>
33301 This feature changes the behavior of fetching messages
33302 and attachments so that the message data is fetched in chunks no larger
33303 than 12K bytes.
33304 This works around a bug in Microsoft's SSL/TLS support.
33305 Some versions of Microsoft SSL are not able to read full-sized (16K)
33306 SSL/TLS packets.
33307 Some servers will send such packets and this will
33308 cause PC-Alpine to crash with the error
33310 <P>
33311 <CENTER><SAMP>incomplete SecBuffer exceeds maximum buffer size</SAMP></CENTER>
33313 <P>
33314 Microsoft is aware of the problem and has developed a hotfix for it, it is
33315 discussed in article 300562 in the Microsoft Knowledge Base.
33316 <P>
33317 <UL>
33318 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33319 </UL><P>
33320 <End of help on this topic>
33321 </BODY>
33322 </HTML>
33323 ====== h_config_quell_partial =====
33324 <HTML>
33325 <HEAD>
33326 <TITLE>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></TITLE>
33327 </HEAD>
33328 <BODY>
33329 <H1>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></H1>
33331 Partial fetching is a feature of the IMAP protocol.
33332 By default, Alpine
33333 will use partial fetching when copying the contents of a message or attachment
33334 from the IMAP server to Alpine.
33335 This means that the fetch will be done in many
33336 small chunks instead of one big chunk. The main benefit of this approach is
33337 that the fetch becomes interruptible. That is, the user can type <EM>^C</EM>
33338 to stop the fetch early. In some cases partial fetching may cause a performance
33339 problem so that the fetching of data takes significantly longer when partial
33340 fetching is used. Turning on this feature will turn off partial fetching.
33341 <P>
33342 <UL>
33343 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33344 </UL><P>
33345 <End of help on this topic>
33346 </BODY>
33347 </HTML>
33348 ====== h_config_quell_personal_name_prompt =====
33349 <HTML>
33350 <HEAD>
33351 <TITLE>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></TITLE>
33352 </HEAD>
33353 <BODY>
33354 <H1>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></H1>
33356 PC-Alpine only. This feature quells the prompting for a
33357 <A HREF="h_config_pers_name">personal name</A>. This
33358 prompt normally happens before composing a message, and only happens when
33359 there is no personal name already set.
33360 <P>
33361 <UL>
33362 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33363 </UL><P>
33364 <End of help on this topic>
33365 </BODY>
33366 </HTML>
33367 ====== h_config_quell_user_id_prompt =====
33368 <HTML>
33369 <HEAD>
33370 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></TITLE>
33371 </HEAD>
33372 <BODY>
33373 <H1>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></H1>
33375 PC-Alpine only. This feature quells the prompting for a
33376 <A HREF="h_config_user_id"><!--#echo var="VAR_user-id"--></A>
33377 if the information can be obtained from the login name used
33378 to open the INBOX. Normally, this prompt happens before composing
33379 a message, and only happens when there is no user-id already set
33380 in the configuration.
33381 <P>
33382 With this feature set, composing a message is only possible after
33383 establishing a connection to the INBOX.
33384 <P>
33385 <UL>
33386 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33387 </UL><P>
33388 <End of help on this topic>
33389 </BODY>
33390 </HTML>
33391 ====== h_config_save_aggregates =====
33392 <HTML>
33393 <HEAD>
33394 <TITLE>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></TITLE>
33395 </HEAD>
33396 <BODY>
33397 <H1>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></H1>
33399 This feature will optimize an aggregate copy operation, if
33400 possible, by issuing a single IMAP <EM>COPY</EM> command with a
33401 list of the messages to be copied.
33402 This feature is set by default.
33403 This may reduce network traffic and elapsed time for the Save.
33404 <EM>However, many IMAP servers (including the UW IMAP server) do
33405 not preserve the order of messages when this optimization is applied.</EM>
33406 If this feature is not set,
33407 Alpine will copy each message individually and the order of the messages
33408 will be preserved.
33409 <P>
33410 <UL>
33411 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33412 </UL><P>
33413 <End of help on this topic>
33414 </BODY>
33415 </HTML>
33416 ====== h_config_use_system_translation =====
33417 <HTML>
33418 <HEAD>
33419 <TITLE>FEATURE: Use System Translation</TITLE>
33420 </HEAD>
33421 <BODY>
33422 <H1>FEATURE: Use System Translation</H1>
33424 UNIX Alpine only.
33425 <P>
33426 Alpine normally uses its own internal software to convert between the multi-byte
33427 representation of characters and the Unicode representation of those
33428 same characters.
33429 It converts from the multi-byte characters your keyboard produces to Unicode,
33430 and from Unicode to the multi-byte characters your display expects.
33431 Alpine also uses its own internal software to decide how much space on
33432 the screen a particular Unicode character will occupy.
33434 <P>
33435 Setting this feature tells Alpine to use the system-supplied routines to
33436 perform these tasks instead.
33437 In particular there are three tasks and three system routines that will
33438 be used for these tasks.
33440 <P>
33441 To convert from multi-byte to Unicode the routine
33443 <P>
33444 <CENTER><SAMP>mbstowcs</SAMP></CENTER>
33445 <P>
33447 is used.
33448 To convert from Unicode to multi-byte the routine
33450 <P>
33451 <CENTER><SAMP>wcrtomb</SAMP></CENTER>
33452 <P>
33454 is used.
33455 And to find the screen width a particular Unicode character will
33456 occupy the routine used is
33458 <P>
33459 <CENTER><SAMP>wcwidth</SAMP></CENTER>
33460 <P>
33462 This feature has been only lightly tested.
33463 The internal routines should normally be used unless you run into
33464 a problem that you think may be solved by using the system routines.
33465 Note that your environment needs to be set up for these
33466 routines to work correctly.
33467 In particular, the LANG or LC_CTYPE variable in your environment will
33468 need to be set.
33470 <P>
33471 <UL>
33472 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33473 </UL><P>
33474 <End of help on this topic>
33475 </BODY>
33476 </HTML>
33477 ====== h_config_suspend_spawns =====
33478 <HTML>
33479 <HEAD>
33480 <TITLE>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></TITLE>
33481 </HEAD>
33482 <BODY>
33483 <H1>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></H1>
33485 This feature affects Alpine's behavior when process suspension is enabled
33486 and then activated via the Ctrl-Z key. Alpine suspension allows one to
33487 temporarily interact with the operating system command "shell"
33488 without
33489 quitting Alpine, and then subsequently resume the still-active Alpine session.
33490 <P>
33492 When the <A HREF="h_config_can_suspend">"<!--#echo var="FEAT_enable-suspend"-->"</A> feature
33493 is set and subsequently the Ctrl-Z key
33494 is pressed, Alpine will normally suspend itself and return temporary control
33495 to Alpine's parent shell process. However, if this feature is set, Alpine
33496 will instead create an inferior subshell process. This is useful when the
33497 parent process is not intended to be used interactively. Examples include
33498 invoking Alpine via the -e argument of the Unix "xterm" program,
33499 or via a menu system.<P>
33501 Note that one typically resumes a suspended Alpine by entering the Unix
33502 "fg" command, but if this feature is set, it will be necessary to
33503 enter the "exit" command instead.
33504 <P>
33505 <UL>
33506 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33507 </UL><P>
33508 <End of help on this topic>
33509 </BODY>
33510 </HTML>
33511 ====== h_config_8bit_smtp =====
33512 <HTML>
33513 <HEAD>
33514 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></TITLE>
33515 </HEAD>
33516 <BODY>
33517 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></H1>
33519 This feature affects Alpine's behavior when sending mail.
33520 By default, this feature is set.
33521 Internet standards
33522 require that all electronic mail messages traversing the global Internet
33523 consist of 7bit ASCII characters unless a pair of cooperating mail
33524 transfer agents explicitly agree to allow 8bit messages. In general,
33525 then, exchanging messages in non-ASCII characters requires MIME encoding.
33526 <P>
33527 However, there are now Internet standards that allow for unencoded 8bit
33528 exchange of messages between cooperating systems. When this feature is set
33529 Alpine will try to negotiate unencoded 8bit transmission during the
33530 sending process. Should the negotiation fail, Alpine will fall back to its
33531 ordinary encoding rules.
33532 <P>
33533 Note, this feature relies on your system's mail transport agent or
33534 configured <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
33535 having the negotiation mechanism introduced in
33536 "Extended SMTP" (ESMTP) and the specific extension called
33537 "8BITMIME".
33538 <P>
33539 ESMTP allows for graceful migration to upgraded mail transfer agents, but
33540 it is possible that this feature might cause problems for some servers.
33541 <P><UL>
33542 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33543 </UL>
33544 <P><End of help on this topic>
33545 </BODY>
33546 </HTML>
33547 ====== h_config_8bit_nntp =====
33548 <HTML>
33549 <HEAD>
33550 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></TITLE>
33551 </HEAD>
33552 <BODY>
33553 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></H1>
33555 This feature affects Alpine's behavior when posting news.
33557 <P>
33559 The Internet standard for exchanging USENET news messages (RFC-1036)
33560 specifies that USENET messages should conform to Internet mail standards
33561 and contain only 7bit characters, but much of the news transport software
33562 in use today is capable of successfully sending messages containing 8bit
33563 characters. Hence, many people believe that it is appropriate to send 8bit
33564 news messages without any MIME encoding.
33566 <P>
33568 Moreover, there is no Internet standard for explicitly negotiating 8bit
33569 transfer, as there is for Internet email. Therefore, Alpine provides the
33570 option of posting unencoded 8bit news messages, though not as the default.
33571 Setting this feature will turn OFF Alpine's MIME encoding of newsgroup
33572 postings that contain 8bit characters.
33574 <P>
33576 Note, articles may cross a path or pass through news transport software
33577 that is unsafe or even hostile to 8bit characters. At best this will only
33578 cause the posting to become garbled. The safest way to transmit 8bit
33579 characters is to leave Alpine's MIME encoding turned on, but recipients
33580 who lack MIME-aware tools are often annoyed when they receive MIME-encoded
33581 messages.
33582 <P>
33583 <End of help on this topic>
33584 </BODY>
33585 </HTML>
33586 ====== h_config_mark_for_cc =====
33587 <HTML>
33588 <HEAD>
33589 <TITLE>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></TITLE>
33590 </HEAD>
33591 <BODY>
33592 <H1>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></H1>
33594 This feature affects Alpine's MESSAGE INDEX display.
33595 By default, a '+' is displayed in the first column if the
33596 message is addressed directly to you.
33597 When this feature is set and the message is not addressed to you, then a
33598 '-' character is displayed if the message is instead Cc'd directly
33599 to you.
33601 <P>
33602 <UL>
33603 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33604 </UL><P>
33605 <End of help on this topic>
33606 </BODY>
33607 </HTML>
33608 ====== h_config_tab_uses_unseen =====
33609 <HTML>
33610 <HEAD>
33611 <TITLE>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></TITLE>
33612 </HEAD>
33613 <BODY>
33614 <H1>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></H1>
33616 This feature affects Alpine's behavior when using the TAB
33617 <A HREF="h_common_nextnew">NextNew Command</A>
33618 to move from one folder to the next.
33619 Alpine's usual behavior is to search for folders
33620 with <EM>Recent</EM> messages in them.
33621 Recent messages are messages that have arrived since the last time the
33622 folder was opened.
33624 <P>
33625 Setting this feature causes Alpine to search for <EM>Unseen</EM>
33626 messages instead of Recent messages.
33627 Unseen messages remain Unseen until you view them (or flag then as Seen with
33628 the <A HREF="h_common_flag">Flag Command</A>).
33629 Setting this feature allows you to locate messages you have not read
33630 instead of only recently received messages.
33631 When this feature is set, the feature
33632 <A HREF="h_config_fast_recent">"<!--#echo var="FEAT_enable-fast-recent-test"-->"</A>
33633 will have no effect, so the checking may be slower.
33635 <P>
33636 Another reason why you might want to use this feature is that Alpine sometimes
33637 opens folders implicitly behind the scenes, and this clears the
33638 Recent status of all messages in the folder.
33639 One example where this happens is when Saving or filtering a
33640 message to another folder.
33641 If that message has some <A HREF="h_config_keywords">keywords</A>
33642 set, then because of some shortcomings
33643 in the IMAP specification, the best way to ensure that those keywords are
33644 still set in the saved copy of the message is to open the folder and
33645 set the keywords explicitly.
33646 Because this clears the Recent status of all messages in that folder the
33647 folder will not be found by the NextNew command unless this feature is set.
33649 <P>
33650 <End of help on this topic>
33651 </BODY>
33652 </HTML>
33653 ====== h_config_tab_new_only =====
33654 <HTML>
33655 <HEAD>
33656 <TITLE>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></TITLE>
33657 </HEAD>
33658 <BODY>
33659 <H1>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></H1>
33661 This feature affects Alpine's behavior when using the TAB key to move from
33662 one message to the next. Alpine's usual behavior is to select the next
33663 unread message or message flagged as "Important".
33665 <P>
33667 Setting this feature causes Alpine to skip the messages flagged as important,
33668 and select unread messages exclusively. Tab behavior when there are no
33669 new messages left to select remains unchanged.
33670 <P>
33671 <End of help on this topic>
33672 </BODY>
33673 </HTML>
33674 ====== h_config_warn_if_subj_blank =====
33675 <HTML>
33676 <HEAD>
33677 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></TITLE>
33678 </HEAD>
33679 <BODY>
33680 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></H1>
33682 This feature affects Alpine's behavior when you send a message being
33683 composed.
33684 If this option is set, Alpine will check to see if the message about to be sent
33685 has a subject or not.
33686 If not, you will be asked if you want to send the message anyway.
33687 <P>
33689 <UL>
33690 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33691 </UL><P>
33692 <End of help on this topic>
33693 </BODY>
33694 </HTML>
33695 ====== h_config_warn_if_fcc_blank =====
33696 <HTML>
33697 <HEAD>
33698 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></TITLE>
33699 </HEAD>
33700 <BODY>
33701 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></H1>
33703 This feature affects Alpine's behavior when you send a message being
33704 composed.
33705 If this option is set, Alpine will check to see if the message about to be sent
33706 has an Fcc or not.
33707 If not, you will be asked if you want to send the message anyway.
33708 <P>
33710 <UL>
33711 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33712 </UL><P>
33713 <End of help on this topic>
33714 </BODY>
33715 </HTML>
33716 ====== h_config_warn_if_no_to_or_cc =====
33717 <HTML>
33718 <HEAD>
33719 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></TITLE>
33720 </HEAD>
33721 <BODY>
33722 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></H1>
33724 This feature affects Alpine's behavior when you send a message being
33725 composed.
33726 If this option is set, Alpine will check to see if the message about to be sent
33727 has either a To address, a Cc address, or a Newsgroup.
33728 If none of these is set,
33729 you will be asked if you want to send the message anyway.
33730 <P>
33732 This feature is closely related to
33733 <A HREF="h_config_auto_fcc_only"><!--#echo var="FEAT_fcc-only-without-confirm"--></A>.
33734 Alpine will normally ask if you want to copy a message only to the Fcc.
33735 This feature also applies to cases where there is a Bcc but still no To, Cc,
33736 or Newsgroup.
33737 If the <!--#echo var="FEAT_fcc-only-without-confirm"--> feature is set and you are sending a
33738 message with only an Fcc, then you won't be asked about sending with
33739 a blank To and Cc and Newsgroups header even if this feature is set.
33740 Similarly, if you have already been asked if you want to send to the Fcc
33741 only and you have answered Yes, then you won't be asked again about sending with
33742 blank To, Cc, and Newsgroups headers even if this feature is set.
33743 <P>
33745 <UL>
33746 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33747 </UL><P>
33748 <End of help on this topic>
33749 </BODY>
33750 </HTML>
33751 ====== h_config_quell_dead_letter =====
33752 <HTML>
33753 <HEAD>
33754 <TITLE>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></TITLE>
33755 </HEAD>
33756 <BODY>
33757 <H1>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></H1>
33759 This feature affects Alpine's behavior when you cancel a message being
33760 composed. Alpine's usual behavior is to write the canceled message to
33761 a file named
33762 <!--chtml if pinemode="os_windows"-->
33763 "DEADLETR",
33764 <!--chtml else-->
33765 "dead.letter" in your home directory,
33766 <!--chtml endif-->
33767 overwriting any previous message. Under
33768 some conditions (some routine), this can introduce a noticeable delay.
33769 Setting this feature will cause Alpine NOT to write canceled compositions
33770 into the file.
33771 <P>
33772 NOTE: Enabling this feature means NO record of canceled messages is
33773 maintained.
33774 <P>
33775 This feature affects the newer option
33776 <A HREF="h_config_deadlets"><!--#echo var="VAR_dead-letter-files"--></A>, which specifies the
33777 number of dead letter files to keep around.
33778 If this feature is set, then the <!--#echo var="VAR_dead-letter-files"--> option has no effect.
33779 <P>
33780 <UL>
33781 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33782 </UL><P>
33783 <End of help on this topic>
33784 </BODY>
33785 </HTML>
33786 ====== h_config_quell_beeps =====
33787 <HTML>
33788 <HEAD>
33789 <TITLE>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></TITLE>
33790 </HEAD>
33791 <BODY>
33792 <H1>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></H1>
33794 This feature affects Alpine's behavior when it displays status message
33795 (e.g., Error complaints, New mail warnings, etc). Setting this feature
33796 will not affect the display of such messages, but will cause those that
33797 emit a beep to become silent.
33799 <P>
33800 <UL>
33801 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33802 </UL><P>
33803 <End of help on this topic>
33804 </BODY>
33805 </HTML>
33806 ====== h_config_suppress_user_agent =====
33807 <HTML>
33808 <HEAD>
33809 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></TITLE>
33810 </HEAD>
33811 <BODY>
33812 <H1>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></H1>
33814 If this feature is set then Alpine will not generate a
33815 <CODE>User-Agent</CODE> header in outgoing messages.
33816 <P>
33817 <UL>
33818 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33819 </UL><P>
33820 <End of help on this topic>
33821 </BODY>
33822 </HTML>
33823 ====== h_config_quell_lock_failure_warnings =====
33824 <HTML>
33825 <HEAD>
33826 <TITLE>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></TITLE>
33827 </HEAD>
33828 <BODY>
33829 <H1>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></H1>
33831 This feature affects Alpine's behavior when it encounters a problem
33832 acquiring a mail folder lock. Typically, a secondary file associated
33833 with the mail folder being opened is created as part of the locking
33834 process. On some systems, such file creation has been administratively
33835 precluded by the system configuration.
33836 <P>
33837 Alpine issues a warning when such failures occur, which can become bothersome
33838 if the system is configured to disallow such actions. Setting this
33839 feature causes Alpine to remain silent when this part of lock creation fails.
33840 <P>
33841 WARNING: systems that have been configured in a way that precludes locking
33842 introduce some risk of mail folder corruption when more than one program
33843 attempts to modify the mail folder. This is most likely to occur to one's
33844 INBOX or other incoming message folder.
33845 <P>
33846 See also <A HREF="h_info_on_locking">"What Systems Managers Need to Know about Alpine File Locking"</A>.
33847 <P>
33848 <UL>
33849 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33850 </UL><P>
33851 <End of help on this topic>
33852 </BODY>
33853 </HTML>
33854 ====== h_config_enable_role_take ======
33855 <HTML>
33856 <HEAD>
33857 <TITLE>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></TITLE>
33858 </HEAD>
33859 <BODY>
33860 <H1>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></H1>
33862 Normally, the Take command takes addresses from a message and helps you
33863 put them into your Address Book.
33864 If you use Rules for Indexcolors, Roles, Filtering, or Scoring;
33865 you may find it useful
33866 to be able to Take information from a message's headers and put it into
33867 a new Rule.
33868 When this feature is set, you will be given an extra prompt that gives
33869 you the choice to Take into the Address Book or Take into a rule.
33870 <P><UL>
33871 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33872 </UL>
33873 <P>
33874 <End of help on this topic>
33875 </BODY>
33876 </HTML>
33877 ====== h_config_enable_take_export ======
33878 <HTML>
33879 <HEAD>
33880 <TITLE>FEATURE: <!--#echo var="FEAT_enable-take-export"--></TITLE>
33881 </HEAD>
33882 <BODY>
33883 <H1>FEATURE: <!--#echo var="FEAT_enable-take-export"--></H1>
33885 Normally, the Take command takes addresses from a message and helps you
33886 put them into your Address Book.
33887 When this feature is set, you will be given an extra prompt that gives you
33888 the choice to Take addresses into a file instead of your Address
33889 Book.
33890 Only the user@domain_name part of the address is put in the file.
33891 <P><UL>
33892 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33893 </UL>
33894 <P>
33895 <End of help on this topic>
33896 </BODY>
33897 </HTML>
33898 ====== h_config_quell_folder_internal_msg ======
33899 <HTML>
33900 <HEAD>
33901 <TITLE>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></TITLE>
33902 </HEAD>
33903 <BODY>
33904 <H1>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></H1>
33906 This feature determines whether or not Alpine will create
33907 "pseudo messages" in folders that are in standard Unix or
33908 MMDF format. <P>
33910 Alpine will normally create these pseudo messages when they are not already
33911 present in a standard Unix or MMDF folder. Their purpose is to record
33912 certain mailbox state data needed for correct IMAP and POP server
33913 operation, and also for Alpine to be able to mark messages as Answered when
33914 the Reply has been postponed.<P>
33916 Sites that do not use IMAP/POP for remote mail access, and that need to
33917 support mail tools that are adversely affected by the presence of the
33918 pseudo-messages (e.g. some mail notification tools) may enable this
33919 feature to tell Alpine not to create them. Note that Alpine's
33920 "Answered" flag
33921 capability will be adversely affected if this is done.<P>
33923 Note too that, even if this feature is enabled, Alpine will not remove
33924 pseudo-messages when it encounters them (e.g. those created by UW's imapd
33925 or ipopd servers.) This feature has no effect on folders that are not in
33926 standard Unix or MMDF format, as pseudo-messages are not needed in the
33927 other formats to record mailbox state information.
33928 <P><UL>
33929 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33930 </UL>
33931 <P>
33932 <End of help on this topic>
33933 </BODY>
33934 </HTML>
33935 ====== h_config_mulnews_as_typed ======
33936 <HTML>
33937 <HEAD>
33938 <TITLE>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></TITLE>
33939 </HEAD>
33940 <BODY>
33941 <H1>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></H1>
33943 This feature will be of little use to most users.
33944 It has no effect unless the feature
33945 <A HREF="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></A>
33946 is set.
33948 When the <!--#echo var="FEAT_enable-multiple-newsrcs"--> feature is set
33949 then the setting of this feature may have an effect on the names of the
33950 newsrc files used.
33951 Normally, the name of the news server will be canonicalized before it is
33952 used in the newsrc file name.
33953 For example, if you type the news server name
33955 <P>
33956 <CENTER><SAMP>servername</SAMP></CENTER>
33957 <P>
33959 it is likely that the canonical name will be something like
33961 <P>
33962 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
33963 <P>
33965 Or it may be the case that
33967 <P>
33968 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
33969 <P>
33971 is really an alias (a DNS CNAME) for
33973 <P>
33974 <CENTER><SAMP>othername.example.com</SAMP></CENTER>
33975 <P>
33977 If this feature is not set, then the canonicalized names will be used.
33978 If this feature is set, then the name you typed in (or put in your
33979 configuration) will be used.
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_quell_empty_dirs ======
33989 <HTML>
33990 <HEAD>
33991 <TITLE>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></TITLE>
33992 </HEAD>
33993 <BODY>
33994 <H1>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></H1>
33996 This feature causes Alpine to remove from the display any directories
33997 that do not contain at least one file or directory. This can be useful
33998 to prevent overly cluttered folder lists when a collection is stored on
33999 a server that treats all names as both a folder and a directory.
34001 <P>
34002 Note, enabling this feature can cause surprising behavior! For example,
34003 you can still use Add to create a directory, but unless you immediately
34004 enter that directory and create a folder, that newly created directory
34005 may not be displayed next time you enter the folder list.
34007 <P>
34008 The description above is not quite correct.
34009 Only directories which potentially may hold messages are hidden if empty.
34010 That is, a directory which is really just a directory and is not selectable
34011 as a folder will not be hidden.
34012 Such directories can occur on servers that treat most names as both a folder
34013 and a directory.
34014 These directories are typically created implicitly when a folder is created
34015 inside a directory that does not yet exist.
34017 <P>
34018 <UL>
34019 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34020 </UL><P>
34021 <End of help on this topic>
34022 </BODY>
34023 </HTML>
34024 ====== h_config_termcap_wins =====
34025 <HTML>
34026 <HEAD>
34027 <TITLE>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></TITLE>
34028 </HEAD>
34029 <BODY>
34030 <H1>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></H1>
34032 This feature may affect Alpine's low-level input routines. Termcap (or
34033 terminfo, depending on how your copy of Alpine was compiled and linked)
34034 is the name of the database that describes terminal capabilities. In
34035 particular, it describes the sequences of characters that various keys
34036 will emit.
34038 <P>
34039 An example would be the Up Arrow key on the keyboard. Up
34040 Arrow is not a distinct character on most Unix systems. When you press
34041 the Up Arrow key a short sequence of characters are produced. This
34042 sequence is supposed to be described in the termcap database by the
34043 "ku" capability (or by the "kcuu1" capability if you
34044 are using terminfo instead of termcap).
34046 <P>
34047 By default, Alpine defines some terminal
34048 escape sequences that are commonly used. For example, the sequence
34049 "ESC O A" is recognized as an Up Arrow key. The sequence
34050 "ESC [ A"
34051 is also recognized as an Up Arrow key. These are chosen because common
34052 terminals like VT100's or ANSI standard terminals produce these
34053 sequences when you press the Up Arrow key.
34055 <P>
34056 If your system's termcap
34057 (terminfo) database assigns some other function to the sequence
34058 "ESC O A"
34059 it is usually ignored by Alpine. Also, if your termcap (terminfo)
34060 database assigns a sequence that doesn't begin with an escape
34061 character (<SAMP>ESC</SAMP>) it is usually ignored by Alpine.
34062 This usually works fine
34063 because most terminals emit the escape sequences that Alpine has defined
34064 by default. We have also found that it is usually better to have these
34065 defaults take precedence over the definitions contained in the database
34066 because the defaults are more likely to be correct than the database.
34068 <P>
34069 There are some terminals where this breaks down. If you want Alpine to
34070 believe the definitions given in your termcap (terminfo) database in
34071 preference to the defaults the Alpine itself sets up, then you may turn
34072 this feature on. Then, sequences of characters that are defined in
34073 both termcap (terminfo) and in Alpine's set of defaults will be
34074 interpreted the way that termcap (terminfo) says they should be
34075 interpreted. Also, if your terminal capabilities database assigns a
34076 sequence that doesn't begin with escape, it will not be ignored.
34078 <P>
34079 <UL>
34080 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34081 </UL><P>
34082 <End of help on this topic>
34083 </BODY>
34084 </HTML>
34085 ====== h_config_cruise_mode =====
34086 <HTML>
34087 <HEAD>
34088 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></TITLE>
34089 </HEAD>
34090 <BODY>
34091 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></H1>
34093 This feature affects Alpine's behavior when you hit the
34094 "Space Bar" at
34095 the end of a displayed message. Typically, Alpine complains that the end
34096 of the text has already been reached. Setting this feature causes such
34097 keystrokes to be interpreted as if the "Tab" key had been hit, thus
34098 taking you to the next "interesting" message,
34099 or scanning ahead to the
34100 next incoming folder with "interesting" messages.
34102 <P>
34103 <UL>
34104 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34105 </UL><P>
34106 <End of help on this topic>
34107 </BODY>
34108 </HTML>
34109 ====== h_config_cruise_mode_delete =====
34110 <HTML>
34111 <HEAD>
34112 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></TITLE>
34113 </HEAD>
34114 <BODY>
34115 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></H1>
34117 This feature modifies the behavior of Alpine's
34118 <A HREF="h_config_cruise_mode">"<!--#echo var="FEAT_enable-cruise-mode"-->"</A> feature.
34119 Setting this feature causes Alpine to implicitly delete read
34120 messages when it moves on to display the next "interesting" message.
34121 <P>
34122 NOTE: Beware when enabling this feature AND the
34123 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
34124 feature.
34125 <P>
34126 <UL>
34127 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34128 </UL><P>
34129 <End of help on this topic>
34130 </BODY>
34131 </HTML>
34132 ====== h_config_slash_coll_entire =====
34133 <HTML>
34134 <HEAD>
34135 <TITLE>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></TITLE>
34136 </HEAD>
34137 <BODY>
34138 <H1>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></H1>
34140 The slash (/) command is available from the MESSAGE INDEX screen when
34141 the folder is sorted by either Threads or OrderedSubject, and the
34142 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
34143 is set to something other than "none".
34144 Normally, the slash command Collapses or Expands the subthread that
34145 starts at the currently highlighted message, if any.
34146 If this option is set, then the slash command Collapses or Expands the
34147 <EM>entire</EM> current thread instead of just the subthread.
34148 The current thread is simply the top-level thread that contains the
34149 current message.
34151 <P>
34152 <UL>
34153 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34154 </UL><P>
34155 <End of help on this topic>
34156 </BODY>
34157 </HTML>
34158 ====== h_config_color_thrd_import =====
34159 <HTML>
34160 <HEAD>
34161 <TITLE>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></TITLE>
34162 </HEAD>
34163 <BODY>
34164 <H1>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></H1>
34166 This option affects only the THREAD INDEX screen.
34167 Whether or not you ever see a THREAD INDEX screen depends on the setting
34168 of the configuration option
34169 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
34170 and on the sort order of the index.
34172 <P>
34173 If a message within a thread is flagged as Important
34174 and this option is set, then
34175 the entire line in the THREAD INDEX will be colored the color of the
34176 Index-important Symbol, which can be set using the
34177 <A HREF="h_color_setup">Setup Kolor</A> screen.
34179 <P>
34180 <UL>
34181 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34182 </UL><P>
34183 <End of help on this topic>
34184 </BODY>
34185 </HTML>
34186 ====== h_config_allow_goto =====
34187 <HTML>
34188 <HEAD>
34189 <TITLE>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></TITLE>
34190 </HEAD>
34191 <BODY>
34192 <H1>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></H1>
34194 This feature modifies the behavior of Alpine's file browser. Setting this
34195 feature causes Alpine to offer the "G Goto" command in the file browser.
34196 That is the default.
34198 <P>
34200 The Goto command allows you to explicitly type in the desired directory.
34201 <P>
34202 <End of help on this topic>
34203 </BODY></HTML>
34204 ====== h_config_add_ldap =====
34205 <HTML>
34206 <HEAD>
34207 <TITLE>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></TITLE>
34208 </HEAD>
34209 <BODY>
34210 <H1>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></H1>
34212 If both the Directory option
34213 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
34214 and this feature are set,
34215 then when an implicit directory lookup is done from the
34216 composer you will automatically be prompted to add the result of the
34217 directory lookup to your address book.
34218 <P>
34219 <UL>
34220 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34221 </UL><P>
34222 <End of help on this topic>
34223 </BODY>
34224 </HTML>
34225 ===== h_patterns_compat_behavior =====
34226 <HTML>
34227 <HEAD>
34228 <TITLE>Rules Behavior Changes in Pine 4.50</TITLE>
34229 </HEAD>
34230 <BODY>
34231 <H1>Rules Behavior Changes in Pine 4.50</H1>
34233 In Alpine, Rules that contain unrecognized elements
34234 are ignored.
34235 In most cases, the unrecognized elements will be something that was
34236 added as a new Rules feature in a later version of Alpine.
34237 In versions of Pine <EM>prior</EM> to 4.50, Pine did <EM>not</EM>
34238 ignore rules that contained unrecognized elements.
34239 For example, a new element of Rules that was added in Pine 4.50 is
34240 Age interval.
34241 Suppose you add an Indexcolor rule, using version Pine 4.50 or later, that colors
34242 all messages older than a week red.
34243 Now, if you run Pine 4.44 using that same configuration file, it will not
34244 recognize the Age interval and so will just ignore it.
34245 That means that all messages will match that rule so all messages will
34246 be colored red when using Pine version 4.44.
34248 <P>
34249 This behavior was considered a bug so it is fixed in Alpine and Pine 4.50 and later.
34250 However, since the behavior still exists in versions prior to Pine 4.50 and
34251 since Filtering is a potentially destructive operation, another measure
34252 was taken to attempt to avoid unintentional Filtering of messages.
34253 The first time that you run Alpine or a Pine that is version 4.50 or greater,
34254 the rules in your Filters configuration variable ("Patterns-Filters")
34255 will be copied to a new Filters configuration variable
34256 with a different name ("Patterns-Filters2").
34257 From then on, Alpine will continue to use the new
34258 variable.
34259 Of course, Pine version 4.44 or lower will continue to use the old
34260 variable.
34261 That means that if you are using Alpine
34262 and also using a version of Pine that is older than 4.50, they will not
34263 share the configuration information about Filters.
34264 If you make a change in one version you won't see it in the other version.
34266 <P>
34267 Since Scoring can be used to trigger Filtering, the same thing has been
34268 done for Score rules.
34269 The old configuration variable name is ("Patterns-Scores")
34270 and the new name is ("Patterns-Scores2").
34271 The same is not true of Role, Indexcolor, and Other rules that are
34272 thought to be less harmful when a mistake is made.
34274 <P>
34275 <End of help on this topic>
34276 </BODY>
34277 </HTML>
34278 ======= h_config_filt_opts_sentdate =======
34279 <HTML>
34280 <HEAD>
34281 <TITLE>PATTERN FEATURE: Use-Date-Header-For-Age</TITLE>
34282 </HEAD>
34283 <BODY>
34284 <H1>PATTERN FEATURE: Use-Date-Header-For-Age</H1>
34286 By default, the Age interval of a Pattern uses a message's time of
34287 arrival to compute the age of the message.
34288 If this feature is set, the date in the message's Date header will
34289 be used instead.
34290 <P>
34291 <End of help on this topic>
34292 </BODY>
34293 </HTML>
34294 ======= h_config_filt_opts_notdel =======
34295 <HTML>
34296 <HEAD>
34297 <TITLE>FILTER FEATURE: Move-Only-if-Not-Deleted</TITLE>
34298 </HEAD>
34299 <BODY>
34300 <H1>FILTER FEATURE: Move-Only-if-Not-Deleted</H1>
34302 If this option is set then a message will be moved into the
34303 specified folder only if it is not marked for deletion.
34304 This is useful if you have multiple Alpine sessions running
34305 simultaneously and you don't want messages to be filtered into a
34306 folder more than once.
34307 It is also useful if you want to filter
34308 only the "undeleted" messages in a newsgroup into a folder.
34309 This method is not foolproof.
34310 There may be cases where a message
34311 gets marked deleted and so it is never filtered into the folder.
34312 For example, if you deleted it in another Alpine session or another mail
34313 program that didn't use the filtering rule.
34314 <P>
34315 This option has no effect if the Filter Action is not set to Move.
34316 <P>
34317 <End of help on this topic>
34318 </BODY>
34319 </HTML>
34320 ======= h_config_filt_opts_nonterm =======
34321 <HTML>
34322 <HEAD>
34323 <TITLE>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</TITLE>
34324 </HEAD>
34325 <BODY>
34326 <H1>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</H1>
34328 If this option is set then this is a non-terminating rule.
34329 Usually, for each message, Alpine searches through the Filter Rules until
34330 a match is found and then it performs the action associated with that rule.
34331 Rules following the match are not considered.
34332 If this option is set then the search for matches will continue at the next
34333 rule.
34334 <P>
34335 If a non-terminating rule matches then the actions associated with
34336 that rule, except for any implied deletion of the message, are performed
34337 before the match for the next rule is checked.
34338 For example, if the non-terminating rule sets the Important status, then that
34339 status will be set when the next rule is considered.
34340 However, if the non-terminating rule Moves the message, the message will
34341 actually be copied instead of copied and deleted so that it is still there
34342 for the next rule.
34343 A moved message is deleted after all the relevant rules have been checked.
34344 The name of the "Move" action is confusing in this case because
34345 a single message can be moved to more than one folder.
34346 It turns the Move into a Copy instead, but it is still followed by a deletion
34347 at the end.
34348 <P>
34349 This option may be useful if you want to have a single message filtered to
34350 two different folders because it matches two different Patterns.
34351 For example, suppose you normally filter messages to a particular mailing
34352 list into one folder, and messages addressed directly to you into a second
34353 folder.
34354 If a message is sent to both you and the list (and you can tell that by
34355 looking at the headers of the message) this option may give you a convenient
34356 way to capture a copy to each folder.
34357 (It may also cause you to capture two copies to each folder,
34358 depending on whether your mail system delivers one or two copies of the
34359 message to you and on how the list works.)
34360 <P>
34361 <End of help on this topic>
34362 </BODY>
34363 </HTML>
34364 ===== h_mainhelp_smime ======
34365 <HTML>
34366 <HEAD>
34367 <TITLE>S/MIME Overview</TITLE>
34368 </HEAD>
34369 <BODY>
34370 <H1>S/MIME Overview</H1>
34372 S/MIME is a standard for the public key encryption and signing of email.
34373 UNIX Alpine contains a basic implementation of S/MIME based on
34374 the <A HREF="http://www.openssl.org/">OpenSSL</A> libraries.
34375 To check if this version of Alpine supports S/MIME look at
34376 <A HREF="X-Alpine-Config:">Supported Options in this Alpine</A> and look
34377 for "S/MIME" under the "Encryption" heading.
34378 <P>
34379 Some limitations:
34380 <UL>
34381 <LI> There is no PC-Alpine implementation.
34382 <LI> There is no provision for checking for CRLs
34383 (Certificate Revocation Lists) in Alpine.
34384 <LI> This built-in S/MIME implementation is not compatible with and does not help with PGP.
34385 <LI> There is no mechanism available for feeding either an entire incoming
34386 or an entire outgoing message to an external
34387 filter and using that external filter to do S/MIME or PGP processing.
34388 <LI> Because the implementation currently uses OpenSSL, there is only a very
34389 limited integration with the Mac OS Keychain (the storing and access of
34390 public certificates).
34391 </UL>
34392 <P>
34393 The S/MIME configuration screen is reached by going to the Main Menu and typing
34394 the "S Setup" command followed by "M S/MIME".
34395 <P>
34397 <H2>S/MIME BASICS</H2>
34399 In order to digitally sign messages you send you must have a public/private key-pair.
34400 This may be obtained from a public Certificate Authority (CA) such as Thawte, Verisign, Comodo,
34401 or GoDaddy; or from a smaller CA such as a university which provides certificates for its
34402 users or a company which provides certificates for its workers.
34403 These certificates are bound to an email address, so the identity being verified is the
34404 email address not a person's name.
34405 <P>
34406 Mail is signed by using the sender's private key, which only the owner of the private key
34407 has access to.
34408 The signature is verified using the signer's public key, which anyone can
34409 have access to.
34410 With Alpine, the first time you receive a signed message the public key of the
34411 sender will be stored for future use.
34413 <P>
34414 Mail is encrypted using the recipient's public key and decrypted by
34415 the recipient with their private key.
34417 <P>
34418 You need a key of your own in order to sign outgoing messages and to have others
34419 encrypt messages sent to you.
34420 You do not need a key of your own to verify signed messages sent by others or to
34421 encrypt messages sent to others.
34423 <H2>ALPINE S/MIME CERTIFICATE STORAGE</H2>
34425 By default UNIX Alpine stores the certificates it uses in a directory in your
34426 home directory.
34427 The directory name is
34428 <P>
34429 <CENTER><SAMP>.alpine-smime</SAMP></CENTER>
34430 <P>
34431 Within that directory are three subdirectories.
34432 Each of the three subdirectories contains files with PEM-encoded contents,
34433 the default format for OpenSSL.
34434 The "<SAMP>public</SAMP>" directory contains public certificates.
34435 The files within that directory have names that are email addresses with the
34436 suffix "<SAMP>.crt</SAMP>" appended.
34437 An example filename is
34438 <P>
34439 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
34440 <P>
34441 The "<SAMP>private</SAMP>" directory contains private keys, probably just one for
34442 your private key.
34443 These are also email addresses but with the suffix "<SAMP>.key</SAMP>" instead.
34444 The third directory is "<SAMP>ca</SAMP>" and it contains certificates for any Certificate
34445 Authorities that you want to trust but that aren't contained in the set of system CAs.
34446 Those files may have arbitrary names as long as they end with the
34447 suffix "<SAMP>.crt</SAMP>".
34449 <H2>HOW TO SIGN AND ENCRYPT</H2>
34451 If you have a certificate you may sign outgoing messages.
34452 After typing the Ctrl-X command to send a message you will see the prompt
34453 <P>
34454 <CENTER><SAMP>Send message?</SAMP></CENTER>
34455 <P>
34456 Available subcommands include "G Sign" and "E Encrypt".
34457 Typing the "G" command will change the prompt to
34458 <P>
34459 <CENTER><SAMP>Send message (Signed)?</SAMP></CENTER>
34460 <P>
34461 Typing the "E" command will change the prompt to
34462 <P>
34463 <CENTER><SAMP>Send message (Encrypted)?</SAMP></CENTER>
34464 <P>
34465 You may even type both to get
34466 <P>
34467 <CENTER><SAMP>Send message (Encrypted, Signed)?</SAMP></CENTER>
34468 <P>
34470 <H2>HOW TO READ SIGNED OR ENCRYPTED MESSAGES</H2>
34472 The reading of a signed message should not require any special action on
34473 your part.
34474 There should be an editorial addition at the start of the message which
34475 says either
34476 <P>
34477 <CENTER><SAMP>This message was cryptographically signed.</SAMP></CENTER>
34478 <P>
34479 or
34480 <P>
34481 <CENTER><SAMP>This message was cryptographically signed but the signature could not be verified.</SAMP></CENTER>
34482 <P>
34483 If an encrypted message is sent to you the encrypted text will not
34484 be shown.
34485 You will have to type the "Ctrl-D Decrypt" command (from the screen where
34486 you are viewing the message) and supply your passphrase when asked.
34487 <P>
34488 For a signed or encrypted message there is also a "Ctrl-E Security" command
34489 which gives you some information about the certificate used to sign or encrypt the message.
34491 <H2>MISCELLANEOUS</H2>
34493 If you have access to a private certificate in the PKCS12 format, which
34494 would sometimes be in a file with a ".p12" extension, then you can
34495 use the following commands to generate private keys, public and certificate
34496 authorities certificates. In the examples below, we assume that the
34497 certificate in the p12 format is called "certificate.p12", and
34498 that your email address is "your@address.com".
34500 <P>
34501 In order to create a private key use the command
34502 <P>
34503 <CENTER><SAMP>openssl pkcs12 -in certificate.p12 -out your@address.com.key</SAMP></CENTER>
34504 <P>
34505 In order to create a public certificate use the command
34506 <P>
34507 <CENTER><SAMP>
34508 openssl pkcs12 -in certificate.p12 -clcerts -nokeys -out your@address.com.crt
34509 </SAMP></CENTER>
34510 <P>
34511 In order to create a certificate authority certificate use the command
34512 <P>
34513 <CENTER><SAMP>
34514 openssl pkcs12 -in certificate.p12 -cacerts -nokeys -out certificate-ca.crt
34515 </SAMP></CENTER>
34517 <P> If the previous command produces an empty file, it means that the
34518 certificate authority was not included in the .p12 file, so you will have
34519 to get it from some other sources. You will need these certificates, so
34520 that you can validate correctly signatures.
34522 <P>
34523 After you have exported these certificates and keys, you can use the import
34524 command in Alpine, from the S/MIME configuration screen,
34525 to import these certificates into Alpine. They will be available for use
34526 as soon as you import them.
34527 <P>
34528 <End of help on this topic>
34529 </BODY>
34530 </HTML>
34531 ====== h_config_smime_pubcertdir =====
34532 <HTML>
34533 <HEAD>
34534 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></TITLE>
34535 </HEAD>
34536 <BODY>
34537 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></H1>
34539 UNIX Alpine only.
34540 <P>
34541 If the option
34542 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
34543 is set then this option will have no effect.
34544 <P>
34545 Normally, Public Certificates for use with S/MIME will be stored in the directory
34546 which is the value of this option.
34547 Those certificates will be stored in PEM format, one certificate per file.
34548 The name of the file for the certificate corresponding to
34549 <P>
34550 <CENTER><SAMP>emailaddress</SAMP></CENTER>
34551 <P>
34552 should be
34553 <P>
34554 <CENTER><SAMP>emailaddress.crt</SAMP></CENTER>
34555 <P>
34556 For example, a file for user@example.com would be in the file
34557 <P>
34558 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
34559 <P>
34560 in this directory.
34561 <P>
34562 Use the Setup/SMIME screen to modify this variable.
34563 <P>
34564 Typically, the public certificates that you have will come from S/MIME signed
34565 messages that are sent to you.
34566 Alpine will extract the public certificate from the signed message and store
34567 it in the certificates directory.
34568 These PEM format public certificates look something like:
34569 <PRE>
34570 -----BEGIN CERTIFICATE-----
34571 MIIFvTCCBKWgAwIBAgIQD4fYFHVI8T20yN4nus097DANBgkqhkiG9w0BAQUFADCB
34572 rjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2Ug
34573 Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExho
34574 ...
34575 2b9KGqDyMWW/rjNnmpjzjT2ObGM7lRA8lke4FLOLajhrz4ogO3b4DFfAAM1VSZH8
34576 D6sOwOLJZkLY8FRsfk63K+2EMzA2+qAzMKupgeTLqXIf
34577 -----END CERTIFICATE-----
34578 </PRE>
34579 <P>
34580 <UL>
34581 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34582 </UL><P>
34583 <P>
34584 <UL>
34585 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34586 </UL><P>
34587 <End of help on this topic>
34588 </BODY>
34589 </HTML>
34590 ====== h_config_smime_pubcertcon =====
34591 <HTML>
34592 <HEAD>
34593 <TITLE>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></TITLE>
34594 </HEAD>
34595 <BODY>
34596 <H1>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></H1>
34598 UNIX Alpine only.
34599 <P>
34600 If this option is set it will be used instead of
34601 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
34602 <P>
34603 This option gives you a way to store certificates remotely on an IMAP server
34604 instead of storing the certificates one per file locally.
34605 In order to do that you just give this option a remote folder name for a folder
34606 which does not yet exist.
34607 The name is similar to the name you might use for a remote configuration file.
34608 A remote folder name might look something like:
34609 <P>
34610 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/publiccerts</SAMP></CENTER>
34611 <P>
34612 See
34613 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34614 about the syntax of folder names.
34615 <P>
34616 Use the Setup/SMIME screen to modify this variable.
34617 <P>
34618 <UL>
34619 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34620 </UL><P>
34621 <P>
34622 <UL>
34623 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34624 </UL><P>
34625 <End of help on this topic>
34626 </BODY>
34627 </HTML>
34628 ====== h_config_smime_privkeydir =====
34629 <HTML>
34630 <HEAD>
34631 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></TITLE>
34632 </HEAD>
34633 <BODY>
34634 <H1>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></H1>
34636 UNIX Alpine only.
34637 <P>
34638 In order to sign outgoing S/MIME messages you will need a
34639 personal digital ID certificate.
34640 You will usually get such a certificate from a certificate authority such as
34641 Thawte or CAcert.
34642 (In order to encrypt outgoing messages you don't need a personal digital ID, you
34643 need the public certificate of the recipient instead.)
34644 If the option
34645 <A HREF="h_config_smime_privkeycon"><!--#echo var="VAR_smime-private-key-container"--></A>
34646 is set then this option will have no effect.
34647 <P>
34648 Normally, Private Keys for use with S/MIME will be stored in the directory
34649 which is the value of this option.
34650 Those certificates will be stored in PEM format, one certificate per file.
34651 The name of the file for the certificate corresponding to your
34652 <P>
34653 <CENTER><SAMP>emailaddress</SAMP></CENTER>
34654 <P>
34655 should be
34656 <P>
34657 <CENTER><SAMP>emailaddress.key</SAMP></CENTER>
34658 <P>
34659 For example, if your address is user@example.com the name of the file would be
34660 <P>
34661 <CENTER><SAMP>user@example.com.key</SAMP></CENTER>
34662 <P>
34663 in this directory.
34664 <P>
34665 Use the Setup/SMIME screen to modify this variable.
34666 <P>
34667 Typically, the private key that you have will come from a Certificate
34668 Authority.
34669 The private key should be stored in a PEM format file that
34670 looks something like:
34671 <PRE>
34672 -----BEGIN RSA PRIVATE KEY-----
34673 Proc-Type: 4,ENCRYPTED
34674 DEK-Info: DES-EDE3-CBC,2CBD328FD84CF5C6
34676 YBEXYLgLU9NJoc1V+vJ6UvcF08RX54S6jXsmgL0b5HGkudG6fhnmHkH7+UCvM5NI
34677 SXO/F8iuZDfs1VGG0NyitkFZ0Zn2vfaGovBvm15gx24b2xnZDLRB7/bNZkurnK5k
34678 VjAjZ2xXn2hFp2GJwqRdmxYNqsKGu52B99oti5HUWuZ2GFRaWjn5hYOqeApZE2uA
34679 ...
34680 oSRqfI51UdSRt0tmGhHeTvybUVrHm9eKft8TTGf+qSBqzSc55CsmoVbRzw4Nfhix
34681 m+4TJybNGNfAgOctSkEyY/OCb49fRRQTCBZVIhzLGGmpYmkO55HbIA==
34682 -----END RSA PRIVATE KEY-----
34683 </PRE>
34684 <P>
34685 <UL>
34686 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34687 </UL><P>
34688 <P>
34689 <UL>
34690 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34691 </UL><P>
34692 <End of help on this topic>
34693 </BODY>
34694 </HTML>
34695 ====== h_config_smime_privkeycon =====
34696 <HTML>
34697 <HEAD>
34698 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-container"--></TITLE>
34699 </HEAD>
34700 <BODY>
34701 <H1>OPTION: <!--#echo var="VAR_smime-private-key-container"--></H1>
34703 UNIX Alpine only.
34704 <P>
34705 If this option is set it will be used instead of
34706 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
34707 <P>
34708 This option gives you a way to store keys remotely on an IMAP server
34709 instead of storing the keys one per file locally.
34710 In order to do that you just give this option a remote folder name for a folder
34711 which does not yet exist.
34712 The name is similar to the name you might use for a remote configuration file.
34713 A remote folder name might look something like:
34714 <P>
34715 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/privatekeys</SAMP></CENTER>
34716 <P>
34717 See
34718 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34719 about the syntax of folder names.
34720 <P>
34721 Use the Setup/SMIME screen to modify this variable.
34722 <P>
34723 <UL>
34724 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34725 </UL><P>
34726 <P>
34727 <UL>
34728 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34729 </UL><P>
34730 <End of help on this topic>
34731 </BODY>
34732 </HTML>
34733 ====== h_config_smime_cacertdir =====
34734 <HTML>
34735 <HEAD>
34736 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></TITLE>
34737 </HEAD>
34738 <BODY>
34739 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></H1>
34741 UNIX Alpine only.
34742 <P>
34743 If the option
34744 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>
34745 is set then this option will have no effect.
34746 <P>
34747 CACert is a shorthand name for certification authority certificate.
34748 Normally Alpine will use the CACerts that are located in the standard system
34749 location for CACerts.
34750 It may be the case that one of your correspondents has a Digital ID which has
34751 been signed by a certificate authority that is not in the regular set of system certificate
34752 authorities.
34753 You may supplement the system list by adding further certificates of your own.
34754 These should be stored in the directory
34755 which is the value of this option.
34756 The certificates will be stored in PEM format, one certificate per file.
34757 The names of the files can be anything ending in ".crt".
34758 <P>
34759 Use the Setup/SMIME screen to modify this variable.
34760 <P>
34761 These PEM format CA certificates look very similar to your public
34762 certificates for particular email addresses
34763 (<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>).
34764 <P>
34765 <UL>
34766 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34767 </UL><P>
34768 <P>
34769 <UL>
34770 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34771 </UL><P>
34772 <End of help on this topic>
34773 </BODY>
34774 </HTML>
34775 ====== h_config_smime_cacertcon =====
34776 <HTML>
34777 <HEAD>
34778 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></TITLE>
34779 </HEAD>
34780 <BODY>
34781 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></H1>
34783 UNIX Alpine only.
34784 <P>
34785 If this option is set it will be used instead of
34786 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
34787 <P>
34788 This option gives you a way to store certificates remotely on an IMAP server
34789 instead of storing the certificates one per file locally.
34790 In order to do that you just give this option a remote folder name for a folder
34791 which does not yet exist.
34792 The name is similar to the name you might use for a remote configuration file.
34793 A remote folder name might look something like:
34794 <P>
34795 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/cacerts</SAMP></CENTER>
34796 <P>
34797 See
34798 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34799 about the syntax of folder names.
34800 <P>
34801 Use the Setup/SMIME screen to modify this variable.
34802 <P>
34803 <UL>
34804 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34805 </UL><P>
34806 <P>
34807 <UL>
34808 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34809 </UL><P>
34810 <End of help on this topic>
34811 </BODY>
34812 </HTML>
34813 ========== h_config_smime_sign_by_default ==========
34814 <HTML>
34815 <HEAD>
34816 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></TITLE>
34817 </HEAD>
34818 <BODY>
34819 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></H1>
34821 UNIX Alpine only.
34822 <P>
34823 This feature only has an effect if your version of Alpine includes
34824 support for S/MIME.
34825 It affects Alpine's behavior when you send a message.
34826 If this option is set, the "Sign" option will default to ON when sending messages.
34827 <P>
34828 Only the default value is affected.
34829 In any case, you may still toggle the Signing option on or off before sending
34830 with the "G Sign" command (provided you have a personal digital ID
34831 certificate).
34832 <P>
34833 <UL>
34834 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34835 </UL><P>
34836 <P>
34838 <UL>
34839 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34840 </UL><P>
34841 <End of help on this topic>
34842 </BODY>
34843 </HTML>
34844 ========== h_config_smime_use_cert_store ==========
34845 <HTML>
34846 <HEAD>
34847 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></TITLE>
34848 </HEAD>
34849 <BODY>
34850 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></H1>
34852 UNIX Alpine only.
34853 <P>
34854 This feature only has an effect if your version of Alpine includes
34855 support for S/MIME.
34856 It affects Alpine's behavior when you validate a message, and should
34857 not be disabled, unless you are performing a test.
34858 <P>
34859 There are two important aspects of validation: validation of the message
34860 (that is, the message was not modified after it was sent)
34861 as well as validation of the identity of the sender. This option has to
34862 do with the latter.
34863 <P>
34864 In order to validate that the message came from the sender in the message
34865 and not an impersonator, Alpine can
34866 either use the certificates that come in the message, or the ones that
34867 you have personally stored. If this feature is enabled (the default) then
34868 Alpine will use certificates that you have already saved in your store
34869 and not those that come in the message to validate the sender of the
34870 message. This behavior helps you prevent against impersonation, because
34871 it is assumed that you trust the certificates that you have saved, and
34872 might not trust those that came with the message that you are validating.
34873 <P>
34874 <UL>
34875 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34876 </UL><P>
34877 <P>
34879 <UL>
34880 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34881 </UL><P>
34882 <End of help on this topic>
34883 </BODY>
34884 </HTML>
34885 ========== h_config_smime_pubcerts_in_keychain ==========
34886 <HTML>
34887 <HEAD>
34888 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></TITLE>
34889 </HEAD>
34890 <BODY>
34891 <H1>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></H1>
34893 UNIX Alpine only.
34894 <P>
34895 If this feature is set the Mac OS X default keychain will be used as the place
34896 to store public certificates instead of a
34897 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
34898 or a
34899 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
34900 <P>
34901 <UL>
34902 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34903 </UL><P>
34904 <P>
34905 <UL>
34906 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34907 </UL><P>
34908 <End of help on this topic>
34909 </BODY>
34910 </HTML>
34911 ========== h_config_smime_dont_do_smime ==========
34912 <HTML>
34913 <HEAD>
34914 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></TITLE>
34915 </HEAD>
34916 <BODY>
34917 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></H1>
34919 UNIX Alpine only.
34920 <P>
34921 Setting this feature turns off all of Alpine's S/MIME support.
34922 You might want to set this if you are having trouble due to the S/MIME support.
34923 <P>
34924 <UL>
34925 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34926 </UL><P>
34927 <P>
34929 <UL>
34930 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34931 </UL><P>
34932 <End of help on this topic>
34933 </BODY>
34934 </HTML>
34935 ========== h_config_smime_encrypt_by_default ==========
34936 <HTML>
34937 <HEAD>
34938 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></TITLE>
34939 </HEAD>
34940 <BODY>
34941 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></H1>
34943 UNIX Alpine only.
34944 <P>
34945 This feature only has an effect if your version of Alpine includes
34946 support for S/MIME.
34947 It affects Alpine's behavior when you send a message.
34948 If this option is set, the "Encrypt" option will default to ON when sending messages.
34949 <P>
34950 Only the default value is affected.
34951 In any case, you may still toggle the Encrypt option on or off before sending
34952 with the "E Encrypt" command (provided you have a the public digital ID
34953 for the recipient).
34954 <P>
34955 <UL>
34956 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34957 </UL><P>
34958 <P>
34960 <UL>
34961 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34962 </UL><P>
34963 <End of help on this topic>
34964 </BODY>
34965 </HTML>
34966 ========== h_config_smime_remember_passphrase ==========
34967 <HTML>
34968 <HEAD>
34969 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></TITLE>
34970 </HEAD>
34971 <BODY>
34972 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></H1>
34974 UNIX Alpine only.
34975 <P>
34976 This feature only has an effect if your version of Alpine includes
34977 support for S/MIME.
34978 If this option is set, you will only have to enter your passphrase for your private key
34979 once during an Alpine session.
34980 <P>
34981 <UL>
34982 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34983 </UL><P>
34984 <P>
34986 <UL>
34987 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34988 </UL><P>
34989 <End of help on this topic>
34990 </BODY>
34991 </HTML>
34992 ====== h_config_smime_transfer_pub_to_con =====
34993 <HTML>
34994 <HEAD>
34995 <TITLE>S/MIME: Transfer Public Certs to Container</TITLE>
34996 </HEAD>
34997 <BODY>
34998 <H1>S/MIME: Transfer Public Certs to Container</H1>
35000 UNIX Alpine only.
35001 <P>
35002 The Transfer command will copy the public certificates in your configured
35003 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
35004 to the container in your configured
35005 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
35006 This might be useful if you decide to switch from using a cert directory to a cert
35007 container.
35008 <P>
35009 Warning: Any previous contents in the container will be lost.
35010 <P>
35011 <UL>
35012 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35013 </UL><P>
35014 <P>
35015 <UL>
35016 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35017 </UL><P>
35018 <End of help on this topic>
35019 </BODY>
35020 </HTML>
35021 ====== h_config_smime_transfer_pub_to_dir =====
35022 <HTML>
35023 <HEAD>
35024 <TITLE>S/MIME: Transfer Public Certs to Directory</TITLE>
35025 </HEAD>
35026 <BODY>
35027 <H1>S/MIME: Transfer Public Certs to Directory</H1>
35029 UNIX Alpine only.
35030 <P>
35031 The Transfer command will copy the public certificates in your configured
35032 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35033 to the directory in your configured
35034 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
35035 This might be useful if you decide to switch from using a cert container to a cert
35036 directory.
35037 <P>
35038 <UL>
35039 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35040 </UL><P>
35041 <P>
35042 <UL>
35043 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35044 </UL><P>
35045 <End of help on this topic>
35046 </BODY>
35047 </HTML>
35048 ====== h_config_smime_transfer_priv_to_con =====
35049 <HTML>
35050 <HEAD>
35051 <TITLE>S/MIME: Transfer Private Keys to Container</TITLE>
35052 </HEAD>
35053 <BODY>
35054 <H1>S/MIME: Transfer Private Keys to Container</H1>
35056 UNIX Alpine only.
35057 <P>
35058 The Transfer command will copy the private keys in your configured
35059 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35060 to the container in your configured
35061 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
35062 This might be useful if you decide to switch from using a key directory to a key
35063 container.
35064 <P>
35065 Warning: Any previous contents in the container will be lost.
35066 <P>
35067 <UL>
35068 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35069 </UL><P>
35070 <P>
35071 <UL>
35072 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35073 </UL><P>
35074 <End of help on this topic>
35075 </BODY>
35076 </HTML>
35077 ====== h_config_smime_transfer_priv_to_dir =====
35078 <HTML>
35079 <HEAD>
35080 <TITLE>S/MIME: Transfer Private Keys to Directory</TITLE>
35081 </HEAD>
35082 <BODY>
35083 <H1>S/MIME: Transfer Private Keys to Directory</H1>
35085 UNIX Alpine only.
35086 <P>
35087 The Transfer command will copy the private keys in your configured
35088 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
35089 to the directory in your configured
35090 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35091 This might be useful if you decide to switch from using a key container to a key
35092 directory.
35093 <P>
35094 <UL>
35095 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35096 </UL><P>
35097 <P>
35098 <UL>
35099 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35100 </UL><P>
35101 <End of help on this topic>
35102 </BODY>
35103 </HTML>
35104 ====== h_config_smime_transfer_cacert_to_con =====
35105 <HTML>
35106 <HEAD>
35107 <TITLE>S/MIME: Transfer CA Certs to Container</TITLE>
35108 </HEAD>
35109 <BODY>
35110 <H1>S/MIME: Transfer CA Certs to Container</H1>
35112 UNIX Alpine only.
35113 <P>
35114 The Transfer command will copy the CA certificates in your configured
35115 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>
35116 to the container in your configured
35117 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
35118 This might be useful if you decide to switch from using a CA cert directory to a CA cert
35119 container.
35120 <P>
35121 Warning: Any previous contents in the container will be lost.
35122 <P>
35123 <UL>
35124 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35125 </UL><P>
35126 <P>
35127 <UL>
35128 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35129 </UL><P>
35130 <End of help on this topic>
35131 </BODY>
35132 </HTML>
35133 ====== h_config_smime_transfer_cacert_to_dir =====
35134 <HTML>
35135 <HEAD>
35136 <TITLE>S/MIME: Transfer CA Certs to Directory</TITLE>
35137 </HEAD>
35138 <BODY>
35139 <H1>S/MIME: Transfer CA Certs to Directory</H1>
35141 UNIX Alpine only.
35142 <P>
35143 The Transfer command will copy the CA certificates in your configured
35144 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
35145 to the directory in your configured
35146 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
35147 This might be useful if you decide to switch from using a CA cert container to a CA cert
35148 directory.
35149 <P>
35150 <UL>
35151 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35152 </UL><P>
35153 <P>
35154 <UL>
35155 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35156 </UL><P>
35157 <End of help on this topic>
35158 </BODY>
35159 </HTML>
35160 ====== h_config_smime_transfer_pubcon_to_key =====
35161 <HTML>
35162 <HEAD>
35163 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
35164 </HEAD>
35165 <BODY>
35166 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
35168 Mac OS X Alpine only.
35169 <P>
35170 The Transfer command will copy the public certificates in your configured
35171 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35172 to your default Mac OS X Keychain.
35173 This might be useful if you decide to switch from using a cert container to using
35174 the Keychain to store your public certs, which you may do by using the
35175 feature
35176 <A HREF="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></A>.
35177 <P>
35178 <UL>
35179 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35180 </UL><P>
35181 <P>
35182 <UL>
35183 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35184 </UL><P>
35185 <End of help on this topic>
35186 </BODY>
35187 </HTML>
35188 ====== h_config_smime_transfer_pubkey_to_con =====
35189 <HTML>
35190 <HEAD>
35191 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
35192 </HEAD>
35193 <BODY>
35194 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
35196 UNIX Alpine only.
35197 <P>
35198 The Transfer command will copy the public certificates in your configured
35199 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35200 to your default Mac OS X Keychain.
35201 This might be useful if you decide to switch from using a cert container to using
35202 the Keychain to store your public certs.
35203 <P>
35204 <UL>
35205 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35206 </UL><P>
35207 <P>
35208 <UL>
35209 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35210 </UL><P>
35211 <End of help on this topic>
35212 </BODY>
35213 </HTML>
35214 ====== h_config_smime_public_certificates =====
35215 <HTML>
35216 <HEAD>
35217 <TITLE>S/MIME: Manage Public Certificates</TITLE>
35218 </HEAD>
35219 <BODY>
35220 <H1>S/MIME: Manage Public Certificates</H1>
35222 UNIX Alpine only.
35223 <P>
35224 This menu item allows you to manage your public certificates, this
35225 may include your own public certificate, but it normally includes
35226 certificates of people you correspond with. These certificates are
35227 saved by Alpine automatically when they are found in signed messages
35228 that you receive. This interface allows you to manage them, by
35229 giving you the option to delete them, or trust them (in the case
35230 of self-signed certificates).
35232 <P>
35233 Please note that Alpine will not validate a message that was sent to you
35234 using a self-signed certificate, unless you decide to trust that certificate.
35235 Internally, a certificate is trusted by copying it to the
35236 <A HREF="h_config_smime_certificate_authorities">Certificate Authorities</A>
35237 collection. If you decide that you want to stop trusting a self-signed
35238 certificate, you must delete such certificate from such collection.
35239 <P>
35240 The <B>I</B> Import command available in this screen allows you to
35241 import a command to this collection.
35242 <P>
35243 <UL>
35244 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35245 </UL><P>
35246 <P>
35247 <UL>
35248 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35249 </UL><P>
35250 <End of help on this topic>
35251 </BODY>
35252 </HTML>
35253 ====== h_config_smime_private_keys =====
35254 <HTML>
35255 <HEAD>
35256 <TITLE>S/MIME: Manage Private Keys</TITLE>
35257 </HEAD>
35258 <BODY>
35259 <H1>S/MIME: Manage Private Keys</H1>
35261 UNIX Alpine only.
35262 <P>
35263 This option allows you to manage your private key. Normally a person has only
35264 one key, in the same way that a person only has one valid passport, or ID card,
35265 at any given time. This option allows you to manage private keys. You can
35266 delete them or import them. Additionally, you can view information
35267 about your public certificate, such as the issuer and the dates of validity
35268 of such certificate, among others.
35270 <P>
35271 If you have more than one e-mail address for which you want to use the
35272 same private key, you must add all those addresses to the private key at
35273 the moment that the key is generated. When you receive a signed message using
35274 a key generated for several e-mail addresses, Alpine will save a
35275 certificate for each e-mail address included in such certificate.
35276 <P>
35277 The <B>I</B> Import command available in this screen allows you to
35278 import a command to this collection.
35279 <P>
35280 <UL>
35281 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35282 </UL><P>
35283 <P>
35284 <UL>
35285 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35286 </UL><P>
35287 <End of help on this topic>
35288 </BODY>
35289 </HTML>
35290 ====== h_config_smime_certificate_authorities =====
35291 <HTML>
35292 <HEAD>
35293 <TITLE>S/MIME: Manage Certificate Authorities</TITLE>
35294 </HEAD>
35295 <BODY>
35296 <H1>S/MIME: Manage Certificate Authorities</H1>
35298 UNIX Alpine only.
35299 <P>
35300 This collection contains certificates that are needed to validate the
35301 certificate of another person, and therefore contains certificates that
35302 you trust. Typically a certificate is signed by another entity, called a
35303 certificate authority. This option allows you to manage which certificates
35304 you trust, allowing you to import them and to delete them or view information
35305 about each certificate, such as the issuer and the dates of validity
35306 of such certificate.
35307 <P>
35308 The <B>I</B> Import command available in this screen allows you to
35309 import a command to this collection.
35310 <P>
35311 <UL>
35312 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35313 </UL><P>
35314 <P>
35315 <UL>
35316 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35317 </UL><P>
35318 <End of help on this topic>
35319 </BODY>
35320 </HTML>
35321 ====== h_certificate_information =====
35322 <HTML>
35323 <HEAD>
35324 <TITLE>S/MIME: Certificate Information Screen</TITLE>
35325 </HEAD>
35326 <BODY>
35327 <H1>S/MIME: Certificate Information Screen</H1>
35329 UNIX Alpine only.
35330 <P>
35331 The CERTIFICATE INFORMATION screen shows you information contained in a certificate
35332 such as its owner, e-mail address, issuer, and interval of validity,
35333 among others.
35334 <P>
35335 In the case of public certificates, this screen shows you if there was a
35336 failure when attempting to validate such message. If the certificate is
35337 self-signed, then the <B>T</B> Trust command will be available, which
35338 you can use to trust such certificate and make Alpine not fail validating
35339 signatures signed with such certificate.
35340 <P>
35341 You can also mark a certificate deleted, with the <B>D</B> command, or
35342 remove the deleted mark with the <B>U</B> undelete command.
35343 <P>
35344 In the case of your private key, Alpine shows you the information
35345 from your public key. Additionally, Alpine allows you to see public
35346 and private information about your key, with the <B>B</B> and
35347 <B>R</B> commands respectively.
35348 <UL>
35349 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35350 </UL><P>
35351 <P>
35352 <UL>
35353 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35354 </UL><P>
35355 <End of help on this topic>
35356 </BODY>
35357 </HTML>
35358 ====== h_config_smime_manage_public_menu =====
35359 <HTML>
35360 <HEAD>
35361 <TITLE>S/MIME: Menu of Commands to Manage Public Certificates</TITLE>
35362 </HEAD>
35363 <BODY>
35364 <H1>S/MIME: Commands that Manage Public Certificates</H1>
35366 UNIX Alpine only.
35367 <P>
35368 This screen allows you to manage your public certificates.
35369 <P>
35370 The format of this screen is as follows. There are five fields: The
35371 leftmost field is normally empty, but it could contain the letter
35372 "D" to indicate that that certificate has been marked for
35373 deletion. The next field is the e-mail address of the owner of the
35374 certificate, shown in its entirety. The third and fourth field are the
35375 first and last day validity for that certificate, respectively. The date
35376 is displayed in the user's locale unless the option
35377 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>
35378 is set. In this case, the month, day and year are represented by two
35379 digits, and the format used is mm/dd/yy. Finally, the fifth
35380 field is what can be displayed of the MD5 hash of the certificate. You can
35381 use any of the last three fields to distinguish between two certificates
35382 for the same owner.
35383 <P>
35384 Available commands in this screen and a short description of what they
35385 do follows.
35386 <UL>
35387 <LI> <B>I</B> Imports a public certificate to this collection.
35388 <LI> <B>V</B> View information about a certificate such as the name of the person the
35389 certificate was issued to, its dates of validity, and validity status.
35390 <LI> <B>D</B> Marks a certificate deleted.
35391 <LI> <B>U</B> Removes the deletion mark on a certificate.
35392 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
35393 <LI> <B>T</B> This command is only available for self-signed certificates, and allows you to
35394 trust a certificate by copying it to the collection of trusted certificates.
35395 </UL>
35396 <P>
35397 All commands provide feedback to let you know about their success or failure.
35398 <P>
35399 <UL>
35400 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35401 </UL><P>
35402 <P>
35403 <UL>
35404 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35405 </UL><P>
35406 <End of help on this topic>
35407 </BODY>
35408 </HTML>
35409 ====== h_config_smime_manage_private_menu =====
35410 <HTML>
35411 <HEAD>
35412 <TITLE>S/MIME: Menu of Commands to Manage Private Keys</TITLE>
35413 </HEAD>
35414 <BODY>
35415 <H1>S/MIME: Commands that Manage Private Keys</H1>
35417 UNIX Alpine only.
35418 <P>
35419 This screen allows you to manage your private key.
35420 <P>
35421 The format of this screen is as follows. There are five fields: The
35422 leftmost field is normally empty, but it could contain the letter
35423 "D" to indicate that that certificate has been marked for
35424 deletion. The next field is the e-mail address of the owner of the
35425 certificate, shown in its entirety. The third field is the first day of
35426 validity for that certificate; the fourth field in the last day that that
35427 certificate is valid, and the fifth field is what can be displayed of the
35428 MD5 hash of the public certificate corresponding to this private key. You
35429 can use any of the last three fields to distinguish between two
35430 certificates for the same owner.
35431 <P>
35432 Available commands and a short description of what they do follows.
35433 <UL>
35434 <LI> <B>I</B> Imports a new public key to this collection.
35435 <LI> <B>V</B> View information about the public certificate corresponding to this
35436 key.
35437 <LI> <B>D</B> Marks a key to be deleted.
35438 <LI> <B>U</B> Removes the deletion mark on a key.
35439 <LI> <B>X</B> Removes all keys marked deleted permanently (cannot be undone).
35440 Note that expunging a private key does not remove the public key, which must
35441 be removed separately.
35442 </UL>
35443 <P>
35444 All commands provide feedback to let you know about their success or failure.
35445 <P>
35446 <UL>
35447 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35448 </UL><P>
35449 <P>
35450 <UL>
35451 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35452 </UL><P>
35453 <End of help on this topic>
35454 </BODY>
35455 </HTML>
35456 ====== h_config_smime_manage_cacerts_menu =====
35457 <HTML>
35458 <HEAD>
35459 <TITLE>S/MIME: Menu of Commands to Manage Certificate Authorities</TITLE>
35460 </HEAD>
35461 <BODY>
35462 <H1>S/MIME: Commands that Manage Certificate Authorities</H1>
35464 UNIX Alpine only.
35465 <P>
35466 This screen allows you to manage your collection of certificates that you
35467 trust.
35468 <P>
35469 The format of this screen is as follows. There are five fields: The
35470 leftmost field is normally empty, but it could contain the letter
35471 "D" to indicate that that certificate has been marked for
35472 deletion. The next field is the e-mail address of the owner of the
35473 certificate, shown in its entirety. The third field is the first day of
35474 validity for that certificate; the fourth field in the last day that that
35475 certificate is valid, and the fifth field is what can be displayed of the
35476 MD5 hash of the certificate. You can use any of the last three fields to
35477 distinguish between two certificates for the same owner.
35478 <P>
35479 Available commands and a short description of what they do follows.
35480 <UL>
35481 <LI> <B>I</B> Imports a trusted certificate to this collection. This is
35482 done by reading the certificate and validating it. Once a certificate
35483 is found to be valid, it is saved, adding the extension ".crt"
35484 to the certificate, if necessary.
35485 <LI> <B>V</B> View information about this certificate, such as its issuer
35486 and validity dates.
35487 <LI> <B>D</B> Marks a certificate to be deleted.
35488 <LI> <B>U</B> Removes the deletion mark on a certificate.
35489 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
35490 </UL>
35491 <P>
35492 All commands provide feedback to let you know about their success or failure.
35493 <P>
35494 <UL>
35495 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35496 </UL><P>
35497 <P>
35498 <UL>
35499 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35500 </UL><P>
35501 <End of help on this topic>
35502 </BODY>
35503 </HTML>
35504 ====== h_config_lame_list_mode =====
35505 <HTML>
35506 <HEAD>
35507 <TITLE>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></TITLE>
35508 </HEAD>
35509 <BODY>
35510 <H1>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></H1>
35512 This feature modifies the method Alpine uses to ask your IMAP
35513 server for folder names to display in the FOLDER LIST screen.
35514 It is intended to compensate for a small set of IMAP servers that
35515 are programmed to ignore a part of the request, and thus respond
35516 to Alpine's query with nonsensical results.
35517 <P>
35519 If you find that Alpine is erroneously displaying blank folder lists,
35520 try enabling this feature.
35521 <P>
35523 NOTE: Enabling this feature has consequences for the Goto and Save
35524 commands. Many servers allow access to folders outside the area
35525 reserved for your personal folders via some reserved character,
35526 typically '#' (sharp), '~' (tilde) or '/' (slash). This mechanism
35527 allows, at the Goto and Save prompts, quick access to folders
35528 outside your personal folder collection without requiring a specific
35529 collection definition. This behavior will generally not be available
35530 when this feature is enabled.
35532 <P>
35533 <UL>
35534 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35535 </UL><P>
35536 <End of help on this topic>
35537 </BODY>
35538 </HTML>
35539 ====== h_config_enable_mulnewsrcs =====
35540 <HTML>
35541 <HEAD>
35542 <TITLE>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></TITLE>
35543 </HEAD>
35544 <BODY>
35545 <H1>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></H1>
35547 This feature makes it so Alpine can use multiple newsrcs based on
35548 the news server being connected to, which allows for separate lists
35549 of subscribed-to newsgroups. When this feature is not set, there is only
35550 one list of newsgroups.
35551 <P>
35552 Under this feature, the name of a newsrc is based on the news server.
35553 For example, if your <a href="h_config_newsrc_path"><!--#echo var="VAR_newsrc-path"--></a>
35554 is set to ".newsrc", and the news server you are connecting to is
35555 news.example.com, then the newsrc to be used is .newsrc-news.example.com.
35556 Setting this feature for the first time will allow for the option of using
35557 your old newsrc the next time you read news.
35558 <P>
35559 If this feature is set, then the feature
35560 <A HREF="h_config_mulnews_as_typed"><!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></A>
35561 also may affect the name of the newsrc file that is used.
35562 <P>
35563 <UL>
35564 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35565 </UL><P>
35566 <End of help on this topic>
35567 </BODY>
35568 </HTML>
35569 ======= h_ab_export_vcard =======
35570 <HTML>
35571 <HEAD>
35572 <TITLE>Address Book Export Format</TITLE>
35573 </HEAD>
35574 <BODY>
35575 <H1>Address Book Export Format</H1>
35577 You are exporting address book data from Alpine to a file outside of Alpine.
35578 You are being asked to choose the format of the export.
35579 Here are the choices:
35581 <DL>
35582 <DT><EM>A</EM>ddress List</DT>
35583 <DD>
35584 The addresses from the address book entries you are saving
35585 from will be saved one address per line.
35586 Address book lists (those with more than one address) will have
35587 all of their addresses saved separately.
35588 </DD>
35590 <DT><EM>V</EM>Card</DT>
35591 <DD>
35592 The entries will be saved in
35593 <A HREF="h_whatis_vcard">vCard</A> format.
35594 </DD>
35596 <DT><EM>T</EM>ab Separated</DT>
35597 <DD>
35598 The entries will be saved in tab-separated columns.
35599 There will be just 4 columns of data that correspond to Alpine's
35600 Nickname field, Full Name field, Address field, and Comment field.
35601 It might prove useful to Select only the Simple, non-List address book
35602 entries before Saving.
35603 </DD>
35605 <DT><EM>^C</EM> Cancel</DT>
35606 <DD>
35607 Cancel out of the Save.
35608 </DD>
35610 </DL>
35613 <P>
35614 <End of help on this topic>
35615 </BODY>
35616 </HTML>
35617 ====== h_config_predict_nntp_server =====
35618 <HTML>
35619 <HEAD>
35620 <TITLE>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></TITLE>
35621 </HEAD>
35622 <BODY>
35623 <H1>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></H1>
35625 This feature allows Alpine to assume that the open NNTP server at the
35626 time of composition is the NNTP server to which the message should be
35627 posted. This is especially recommended when there are multiple News
35628 collections. If this feature is not set, Alpine will try to post to the first server in
35629 the <a href="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></a> variable. Setting
35630 this feature also negates the need to add News collection servers to
35631 the <!--#echo var="VAR_nntp-server"--> variable.
35632 <P>
35633 This feature can be especially handy when used in conjunction with
35634 <a href="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></a>.
35635 <P>
35636 <UL>
35637 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35638 </UL><P>
35639 <End of help on this topic>
35640 </BODY>
35641 </HTML>
35642 ====== h_config_nntp_search_uses_overview =====
35643 <HTML>
35644 <HEAD>
35645 <TITLE>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></TITLE>
35646 </HEAD>
35647 <BODY>
35648 <H1>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></H1>
35650 This feature should probably be turned on unless it causes trouble.
35651 The results of the NNTP overview command (XOVER) may be used to help
35652 with some searches in news groups.
35653 It should result in quicker response time.
35654 Turning this feature on apparently causes search results which are
35655 different from what you would get with the feature turned off on some
35656 servers.
35657 <P>
35658 <UL>
35659 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35660 </UL><P>
35661 <End of help on this topic>
35662 </BODY>
35663 </HTML>
35664 ====== h_config_thread_sorts_by_arrival =====
35665 <HTML>
35666 <HEAD>
35667 <TITLE>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></TITLE>
35668 </HEAD>
35669 <BODY>
35670 <H1>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></H1>
35672 This feature affects how a threading sort arranges threads. The default way
35673 to arrange threads is by the date of the earliest message in the thread.
35674 This feature arranges threads by the last message to arrive in a thread.
35675 <P>
35676 This feature causes old threads that get recent messages to sort to the bottom,
35677 where previously a message arrival to a thread would not rearrange the order of
35678 that thread.
35679 <P>
35680 <UL>
35681 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35682 </UL><P>
35683 <End of help on this topic>
35684 </BODY>
35685 </HTML>
35686 ====== h_config_textplain_int =====
35687 <HTML>
35688 <HEAD>
35689 <TITLE>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></TITLE>
35690 </HEAD>
35691 <BODY>
35692 <H1>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></H1>
35694 This feature modifies the method Alpine uses to display Text/Plain
35695 MIME attachments from the Attachment Index screen. Normally, the
35696 "View" command searches for any externally defined (usually
35697 via the
35698 "<A HREF="h_config_mailcap_path">Mailcap</A>" file) viewer,
35699 and displays the selected text within that viewer.
35701 <P>
35702 Enabling this feature causes Alpine to ignore any external viewer
35703 settings and always display text with Alpine's internal viewer.
35705 <P>
35706 <UL>
35707 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35708 </UL><P>
35709 <End of help on this topic>
35710 </BODY>
35711 </HTML>
35712 ====== h_config_wp_columns =====
35713 <HTML>
35714 <HEAD>
35715 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></TITLE>
35716 </HEAD>
35717 <BODY>
35718 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></H1>
35720 Web Alpine only.
35721 <P>
35722 This configuration setting specifies the number of horizontal characters
35723 used to format various WebAlpine pages. Smaller values will tend to reduce
35724 the amount of horizontal scrolling required to view pages within narrow
35725 browsers, such as those found on PDAs, and larger values will tend to
35726 spread more information across the page.
35728 <P>
35729 The Message List page uses the width to determine how many characters
35730 to assign each field. Note, a smaller value may result in a disproportionate
35731 amount of blank space between fields on each line. Similarly, a large
35732 value may result in cramped fields or horizontal scrolling.
35734 <P>
35735 The Message View page uses this value to determine when to wrap lines
35736 in displayed message text. Note, a smaller value may result in jagged
35737 right margins or confusing quoting. A larger value may cause lines of text to
35738 run beyond the browser's right edge, requiring horizontal scrolling.
35740 <P>
35741 <UL>
35742 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35743 </UL><P>
35744 <End of help on this topic>
35745 </BODY>
35746 </HTML>
35747 ====== h_config_wp_state =====
35748 <HTML>
35749 <HEAD>
35750 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></TITLE>
35751 </HEAD>
35752 <BODY>
35753 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></H1>
35755 Web Alpine only.
35756 <P>
35757 Various aspects of cross-session state.
35759 <P>
35760 <UL>
35761 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35762 </UL><P>
35763 <End of help on this topic>
35764 </BODY>
35765 </HTML>
35766 ====== h_config_wp_aggstate =====
35767 <HTML>
35768 <HEAD>
35769 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></TITLE>
35770 </HEAD>
35771 <BODY>
35772 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></H1>
35774 Web Alpine only.
35775 <P>
35776 Aggregate operations tab state.
35778 <P>
35779 <UL>
35780 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35781 </UL><P>
35782 <End of help on this topic>
35783 </BODY>
35784 </HTML>
35785 ====== h_config_wp_indexlines =====
35786 <HTML>
35787 <HEAD>
35788 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></TITLE>
35789 </HEAD>
35790 <BODY>
35791 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></H1>
35793 Web Alpine only.
35794 <P>
35795 Number of index lines in table.
35797 <P>
35798 <UL>
35799 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35800 </UL><P>
35801 <End of help on this topic>
35802 </BODY>
35803 </HTML>
35804 ====== h_config_wp_indexheight =====
35805 <HTML>
35806 <HEAD>
35807 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></TITLE>
35808 </HEAD>
35809 <BODY>
35810 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></H1>
35812 Web Alpine only.
35813 <P>
35814 Index table row height.
35816 <P>
35817 <UL>
35818 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35819 </UL><P>
35820 <End of help on this topic>
35821 </BODY>
35822 </HTML>
35823 ====== h_config_rss_news =====
35824 <HTML>
35825 <HEAD>
35826 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss_news"--></TITLE>
35827 </HEAD>
35828 <BODY>
35829 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-news"--></H1>
35831 Web Alpine only.
35832 <P>
35833 RSS News feed.
35835 <P>
35836 <UL>
35837 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35838 </UL><P>
35839 <End of help on this topic>
35840 </BODY>
35841 </HTML>
35842 ====== h_config_rss_weather =====
35843 <HTML>
35844 <HEAD>
35845 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></TITLE>
35846 </HEAD>
35847 <BODY>
35848 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></H1>
35850 Web Alpine only.
35851 <P>
35852 RSS Weather feed.
35854 <P>
35855 <UL>
35856 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35857 </UL><P>
35858 <End of help on this topic>
35859 </BODY>
35860 </HTML>
35861 ====== h_config_send_confirms_only_expanded =====
35862 <HTML>
35863 <HEAD>
35864 <TITLE>FEATURE: send-confirms-only-expanded</TITLE>
35865 </HEAD>
35866 <BODY>
35867 <H1>FEATURE: send-confirms-only-expanded (Web Alpine Only)</H1>
35869 This Web Alpine option specifies whether or not a Send confirmations
35870 happens when a composed message is readied for sending or not. The
35871 default behavior is to not confirm that the nicknames were expanded to
35872 the intended addresses.
35874 <P>
35875 <UL>
35876 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35877 </UL><P>
35878 <End of help on this topic>
35879 </BODY>
35880 </HTML>
35881 ====== h_config_enable_jump_command =====
35882 <HTML>
35883 <HEAD>
35884 <TITLE>FEATURE: enable-jump-command</TITLE>
35885 </HEAD>
35886 <BODY>
35887 <H1>FEATURE: enable-jump-command (Web Alpine Only)</H1>
35889 This Web Alpine option specifies whether or not a Jump command is
35890 offered in the Message List and Message View pages. The command is
35891 implemented as an input field in the left column of the List and View
35892 screens.
35894 <P>
35895 When enabled and a number is entered in the input field while the
35896 Message List is displayed, the Message List is reframed with the
35897 specified message. While viewing a message, the message associated
35898 with the specified message number is displayed.
35900 <P>
35901 <UL>
35902 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35903 </UL><P>
35904 <End of help on this topic>
35905 </BODY>
35906 </HTML>
35907 ====== h_config_enable_newmail_sound =====
35908 <HTML>
35909 <HEAD>
35910 <TITLE>FEATURE: enable-newmail-sound</TITLE>
35911 </HEAD>
35912 <BODY>
35913 <H1>FEATURE: enable-newmail-sound (Web Alpine Only)</H1>
35915 This Web Alpine option specifies whether or not a sound file is sent
35916 to the web browser along with the newmail notification message.
35919 <P>
35920 <UL>
35921 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35922 </UL><P>
35923 <End of help on this topic>
35924 </BODY>
35925 </HTML>
35926 ====== h_config_render_html_internally =====
35927 <HTML>
35928 <HEAD>
35929 <TITLE>FEATURE: render-html-internally</TITLE>
35930 </HEAD>
35931 <BODY>
35932 <H1>FEATURE: render-html-internally (Web Alpine Only)</H1>
35934 By default, Web Alpine will pass cleansed HTML text you receive in messages
35935 to the browser for display (rendering). This feature causes Web Alpine to convert
35936 the HTML text into plain text in the same way Unix and PC-Alpine do.
35939 <P>
35940 <UL>
35941 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35942 </UL><P>
35943 <End of help on this topic>
35944 </BODY>
35945 </HTML>
35946 ====== h_config_role_undo =====
35947 Yes, remember changes and exit back to list of roles; No, discard changes
35948 made in this screen; ^C, cancel exit and stay in this config screen.
35949 ====== h_exit_editor =====
35950 S, save changes and exit from the editor; D, do not save changes but
35951 do exit from the editor; or ^C, cancel exit and stay in the editor.
35952 ====== h_config_undo =====
35953 Yes, save changes and exit; No, exit without saving any changes made since
35954 entering this CONFIGURATION screen; ^C, cancel exit and stay in config screen.
35955 ====== h_os_index_whereis =====
35956 Enter ^V or ^Y to go immediately to the last or first message in the index.
35957 Or, enter the match string followed by RETURN.
35958 ====== h_os_index_whereis_agg =====
35959 Enter ^V or ^Y to go immediately to the last or first message in the index,
35960 Or, enter the match string followed by RETURN (or ^X to select all matches).
35961 =========== h_oe_add_full ==================
35962 Type the full name of the person being added and press the RETURN key.
35963 Press ^C to cancel addition.
35964 =========== h_oe_add_nick ==================
35965 Type a short nickname and press RETURN. A nickname is a short easy-to-
35966 remember word, name or initials like "joe", or "wcfields." ^C to cancel.
35967 ========== h_oe_add_addr ================
35968 Type the e-mail address and press RETURN.
35969 Press ^C to cancel addition.
35970 ========== h_oe_crlst_full ==============
35971 Type a long name or description for the list that you are creating and
35972 press RETURN. Press ^C to cancel creation of list.
35973 =========== h_oe_crlst_nick =============
35974 Type a nickname (short, easy-to-remember name or single word) for the list
35975 you are creating and press RETURN. Press ^C to cancel.
35976 ========== h_oe_crlst_addr ==============
35977 Type an e-mail address, or a nickname already in the address book that you
35978 want to be part of this list and press RETURN.
35979 ========== h_oe_adlst_addr =============
35980 Type an e-mail address or a nickname already in the address book that you
35981 want to add to this list and press RETURN.
35982 ========== h_oe_editab_nick ============
35983 Change the nickname using the arrow keys and delete key. Press RETURN
35984 when done. Press ^C to cancel editing and leave the nickname as it was.
35985 ========== h_oe_editab_full ============
35986 Change the full name using the arrow keys and delete key. Press RETURN
35987 when done. Press ^C to cancel editing and leave the full name as it was.
35988 ========== h_oe_editab_addr ============
35989 Change the address using the arrow keys and delete key. Press RETURN
35990 when done. Press ^C to cancel editing and leave the address as it was.
35991 ========== h_oe_editab_fcc ============
35992 Change the fcc using the arrow keys and delete key. Press RETURN when
35993 done. Press ^C to cancel editing and leave the fcc as it was.
35994 ========== h_oe_editab_comment ============
35995 Change the comment field using the arrow keys and delete key. Press RETURN
35996 when done. Press ^C to cancel editing and leave the comment as it was.
35997 ====== h_ab_forward =====
35998 Yes, expand nicknames and qualify local names with your current domain name;
35999 No, leave nicknames and local names as is; ^C, cancel.
36000 ========== h_ab_export ==========
36001 Type the name of a file to write the addresses into and
36002 press RETURN. You may also specify an absolute path. Use ^C to cancel.
36003 ========== h_ab_edit_a_field ==========
36004 Edit any of the fields of the currently selected entry by typing one of the
36005 letters at the bottom of the screen. Press ^C to cancel edit.
36006 ====== h_ab_del_data_revert =====
36007 Press B to completely delete addrbook and revert to default, C to delete config
36008 and revert while leaving data, or D to only delete data (make it empty).
36009 ====== h_ab_del_data_modify =====
36010 Press B to completely delete addrbook, C to delete configuration while leaving
36011 data, or D to delete data (make it empty) but leave config. ^C to cancel.
36012 ====== h_ab_del_config_modify =====
36013 Yes, remove this address book from my configuration.
36014 No, make no changes now.
36015 ====== h_ab_del_config_revert =====
36016 Yes, remove this address book from my config and revert to default.
36017 No, make no changes now.
36018 ====== h_ab_del_default =====
36019 Yes, remove this default address book from my configuration.
36020 No, make no changes now.
36021 ====== h_ab_really_delete =====
36022 Yes, delete the actual contents of the address book, not just the
36023 configuration. No, don't delete the data after all, cancel and start over.
36024 ====== h_ab_del_ignore =====
36025 Press I to ignore all the default address books for this category. Press R to
36026 remove this one address book and add the others to your personal list.
36027 ====== h_ab_del_dir_ignore =====
36028 Press I to ignore all the default directory servers for this category.
36029 Press R to remove this one server and add the others to your personal list.
36030 ====== h_ab_copy_dups =====
36031 Yes, overwrite the existing entry.
36032 No, skip duplicates but save the rest. Press ^C to cancel.
36033 ====== h_confirm_cancel =====
36034 Type C to Confirm that you want to abandon the message you are composing.
36035 Type N or ^C to cancel out of the cancel and keep composing.
36036 ====== h_ab_text_or_vcard =====
36037 Text, start composer with displayed text already included.
36038 VCard, start composer with address book entry attached as a vCard. ^C cancels.
36039 ====== h_ab_backup_or_ldap =====
36040 Backup, copy email address from entry and allow editing of it.
36041 LDAP, copy LDAP search criteria, do not allow editing of it. ^C cancels.
36042 ====== h_ldap_text_or_vcard =====
36043 Text: export displayed text for selected entry. Address: export only the
36044 email address. VCard: export entry in vCard format. ^C cancels.
36045 ====== h_ab_save_exp =====
36046 Save, save entry or entries to an address book.
36047 Export, save to file outside of pine. ^C cancels save.
36048 ====== h_ab_add =====
36049 A, add a brand new entry to this address book.
36050 E, edit the entry that is currently highlighted. ^C to cancel.
36051 ====== h_ab_shuf =====
36052 U, swap order of highlighted address book and the one above it.
36053 D, swap order of highlighted address book and the one below it. ^C to cancel.
36054 ====== h_ab_shuf_up =====
36055 U, swap order of highlighted address book and the one above it.
36056 Press ^C to cancel.
36057 ====== h_ab_shuf_down =====
36058 D, swap order of highlighted address book and the one below it.
36059 Press ^C to cancel.
36060 ====== h_folder_prop =====
36061 Count is # of messages in the folder, Unseen means messages that have not
36062 been read, New means messages that were Recently added to the folder.
36063 ====== h_role_shuf =====
36064 U, swap order of highlighted rule and the one above it.
36065 D, swap order of highlighted rule and the one below it. ^C to cancel.
36066 ====== h_role_shuf_up =====
36067 U, swap order of highlighted rule and the one above it.
36068 Press ^C to cancel.
36069 ====== h_role_shuf_down =====
36070 D, swap order of highlighted rule and the one below it.
36071 Press ^C to cancel.
36072 ====== h_incoming_shuf =====
36073 B, swap order of highlighted directory and the one before it.
36074 F, swap order of highlighted directory and the one after it. ^C to cancel.
36075 ====== h_incoming_shuf_up =====
36076 B, swap order of highlighted directory and the one before it.
36077 Press ^C to cancel.
36078 ====== h_incoming_shuf_down =====
36079 F, swap order of highlighted directory and the one after it.
36080 Press ^C to cancel.
36081 ====== h_dir_shuf =====
36082 U, swap order of highlighted directory and the one above it.
36083 D, swap order of highlighted directory and the one below it. ^C to cancel.
36084 ====== h_dir_shuf_up =====
36085 U, swap order of highlighted directory and the one above it.
36086 Press ^C to cancel.
36087 ====== h_dir_shuf_down =====
36088 D, swap order of highlighted directory and the one below it.
36089 Press ^C to cancel.
36090 ====== h_hdrcolor_shuf =====
36091 U, swap order of highlighted Header Color and the one above it.
36092 D, swap order of highlighted Header Color and the one below it. ^C to cancel.
36093 ====== h_hdrcolor_shuf_up =====
36094 U, swap order of highlighted Header Color and the one above it.
36095 Press ^C to cancel.
36096 ====== h_hdrcolor_shuf_down =====
36097 D, swap order of highlighted Header Color and the one below it.
36098 Press ^C to cancel.
36099 ========== h_oe_editab_al ============
36100 Change the address using the arrow keys and delete key. Press RETURN
36101 when done. Press ^C to cancel editing and leave the address as it was.
36102 ========== h_dir_comp_search ===============
36103 Type a string to look for just like you would in the composer. Your configured
36104 rules for the servers with the implicit flag set will be used.
36105 ========== h_oe_searchab ===============
36106 Type the word or name you want to search for and press RETURN. If you press
36107 RETURN without entering anything the word in [] will be searched for.
36108 ========== h_oe_chooseabook ==========
36109 Choose the address book you want to save the new entry in.
36110 Use ^N or ^P to change address books. ^C to cancel.
36111 ========== h_oe_takeaddr ==========
36112 Edit the e-mail address using the arrow and delete keys. Press RETURN
36113 when done. Press ^C to cancel adding this entry to the address book.
36114 ========== h_oe_take_replace ==========
36115 Press R to replace the old entry with this new data. You will still have
36116 another chance to cancel. N to enter another nickname. ^C to cancel now.
36117 ========== h_oe_take_replace_or_add ==========
36118 Press R to replace the old entry. Press A to add the selected addresses to
36119 the old existing list. N to enter another nickname. ^C to cancel now.
36120 ========== h_oe_takename ==========
36121 Edit the full name to be correct using the arrow and delete keys. Press RETURN
36122 when done. Press ^C to cancel adding this entry to the address book.
36123 ========== h_oe_takenick ==========
36124 Type a nickname (short easy-to-remember name, initials or single word) for this
36125 entry in the address book and press RETURN. Press ^C to cancel addition.
36126 ========== h_oe_jump ==========
36127 Type the message number you want to jump to and press RETURN. The word "end"
36128 represents the last message. Press ^C to cancel jumping to another message.
36129 ========== h_oe_jump_thd ==========
36130 Type the thread number you want to jump to and press RETURN. The word "end"
36131 represents the last thread. Press ^C to cancel jumping to another thread.
36132 ========== h_oe_debuglevel ==========
36133 Higher number shows more debugging details.
36134 Press ^C if you want to cancel the change.
36135 ========== h_oe_broach ==========
36136 Type the name of the folder you want to open and press RETURN. Press ^P/^N
36137 to go to the previous/next collections in the list. Press ^C to cancel goto.
36138 ========== h_oe_foldsearch ==========
36139 Type the text you want to search for in foldernames and press RETURN. If you
36140 press RETURN without entering anything, any text in [] will be searched for.
36141 ========== h_oe_foldrename ==========
36142 Change the old name of the folder to the new name using the arrow and
36143 delete keys and press RETURN. Press ^C to cancel rename.
36144 ========== h_oe_login ==========
36145 Enter your login name for the host you are opening the mailbox on. Just press
36146 RETURN to use your login from this host as is, or edit it with delete key.
36147 ========== h_oe_passwd ==========
36148 Type your password for the host and login shown as part of the prompt.
36149 Press ^C to cancel opening folder.
36150 ========== h_oe_choosep ==========
36151 Enter the number associated with the printer you want to select. Press ^C to
36152 cancel the printer selection. The current selection is highlighted.
36153 ========== h_oe_customp ==========
36154 Type the name of the Unix print command and press RETURN. Press ^C to
36155 cancel the printer selection.
36156 ========== h_oe_searchview ==========
36157 Type the word or name you want to search for and press RETURN. If you press
36158 RETURN without entering anything the word in [] will be searched for.
36159 ========== h_oe_keylock ==========
36160 The keyboard is in use and locked by another user. Only that user can
36161 unlock this keyboard by typing the password.
36162 ========== h_wt_expire ==========
36163 At the beginning of each month Alpine offers to rename your current sent-mail
36164 folder to one named for the month so you have a sent-mail folder for each month
36165 ========== h_wt_delete_old ==========
36166 It is the beginning of the month, and we need to conserve disk
36167 space. Please delete any sent-mail that you do not need.
36168 ========== h_select_sort ==========
36169 Select the order for sorting the index by typing the capitalized letter.
36170 Arrival is by arrival in your mailbox; Date is by time/day message was sent.
36171 ========== h_no_F_arg ============
36172 Enter name of file to be opened.
36174 ========== h_sticky_personal_name ==========
36175 Type in your name as you want it to appear on outgoing email. This entry
36176 will be saved into your Alpine configuration file.
36177 ========== h_sticky_inbox ============
36178 INBOX syntax is usually {complete.machine.name}INBOX
36179 This entry will be saved in your Alpine configuration file.
36180 ========== h_sticky_smtp ============
36181 The name of the computer on your campus that relays your outgoing email
36182 to the Internet. This entry will be saved in your Alpine configuration file.
36183 ========== h_sticky_user_id ==========
36184 The username or login-id part of your email address. This entry will be
36185 saved in your Alpine configuration file.
36186 ========== h_sticky_domain ==========
36187 The domain part of your email address, NOT the name of your PC. This
36188 entry will be saved in your Alpine configuration file.
36189 ========== h_bounce =========
36190 Enter the address or nickname of the intended recipient. Alpine will resend
36191 the message, which will retain the original author's From: address.
36192 ========== h_incoming_add_folder_nickname =========
36193 Enter an (optional) nickname that will be used in lieu of the actual
36194 host and folder names in the FOLDER LIST display.
36195 ========== h_anon_forward ==========
36196 Enter the address of your intended recipient, or ^C to cancel.
36197 Example: jsmith@somewhere.edu
36198 ========== h_news_subscribe ==========
36199 Enter the name of the newsgroup to which you wish to subscribe,
36200 or ^C to cancel. Example: comp.mail.pine
36201 ========== h_pipe_msg ==========
36202 Enter the name of the Unix command to which you wish to send this
36203 message, or ^C to cancel.
36204 ========== h_pipe_attach ==========
36205 Enter the name of the Unix command to which you wish to send this
36206 attachment, or ^C to cancel.
36207 ========== h_select_by_num ==========
36208 Enter a list of message numbers (or number ranges), or ^C to cancel. The word
36209 "end" represents the last message. Example: 2-5,7-9,11,19,35-end
36210 ========== h_select_by_thrdnum ==========
36211 Enter a list of thread numbers (or number ranges), or ^C to cancel. The word
36212 "end" represents the last thread. Example: 2-5,7-9,11,19,35-end
36213 ========== h_select_txt_from ==========
36214 Messages with From: headers containing the entered string will be selected.
36215 ^C to cancel. ^G again to see original options.
36216 ========== h_select_txt_not_from ==========
36217 Messages without From: headers containing the entered string will be selected.
36218 ^C to cancel. ^G again to see original options.
36219 ========== h_select_txt_to ==========
36220 Messages with To: headers containing the entered string will be selected.
36221 ^C to cancel. ^G again to see original options.
36222 ========== h_select_txt_not_to ==========
36223 Messages without To: headers containing the entered string will be selected.
36224 ^C to cancel. ^G again to see original options.
36225 ========== h_select_txt_cc ==========
36226 Messages with Cc: headers containing the entered string will be selected.
36227 ^C to cancel. ^G again to see original options.
36228 ========== h_select_txt_not_cc ==========
36229 Messages without Cc: headers containing the entered string will be selected.
36230 ^C to cancel. ^G again to see original options.
36231 ========== h_select_txt_subj ==========
36232 Messages with Subject: headers containing the entered string will be selected.
36233 ^C to cancel. ^X enters Subject: line of current message.
36234 ========== h_select_txt_not_subj ==========
36235 Messages without Subject headers containing the entered string will be selected.
36236 ^C to cancel. ^X enters Subject: line of current message.
36237 ========== h_select_txt_all ==========
36238 All messages containing the entered string will be selected. Headers and body,
36239 but not encoded attachments, will be compared. Enter ^C to cancel.
36240 ========== h_select_txt_not_all ==========
36241 All messages that don't contain the entered string will be selected. Headers
36242 and body, but not encoded attachments, will be compared. Enter ^C to cancel.
36243 ========== h_select_txt_body ==========
36244 All messages containing the entered string will be selected. Body text, but
36245 not headers or encoded attachments, will be compared. ^C to cancel.
36246 ========== h_select_txt_not_body ==========
36247 All messages that don't contain the entered string will be selected. Body
36248 text, but not headers or encoded attachments, will be compared. ^C to cancel.
36249 ========== h_select_txt_recip ==========
36250 Messages with Cc: or To: headers containing the entered string will be selected.
36251 ^C to cancel. ^G again to see original options.
36252 ========== h_select_txt_not_recip ==========
36253 Messages without Cc: or To: headers containing the string will be selected.
36254 ^C to cancel. ^G again to see original options.
36255 ========== h_select_txt_partic ==========
36256 Messages with Cc, To, or From headers containing the string will be selected.
36257 ^C to cancel. ^G again to see original options.
36258 ========== h_select_txt_not_partic ==========
36259 Messages without Cc, To, or From headers containing the string will be selected.
36260 ^C to cancel. ^G again to see original options.
36261 ========== h_select_date ==========
36262 If typed, date may be in DD-MMM-YYYY format (04-Jul-2006) or in ISO format
36263 (2006-07-04). ^P/^N also changes default date. ^X enters date of current msg.
36264 ========== h_attach_index_whereis ==========
36265 Enter some text that appears in the Attachment Index entry for the desired
36266 attachment. The first attachment containing that text will be highlighted.
36267 ========== h_kb_lock ==========
36268 Keystrokes entered here (up to a RETURN) comprise a password that must
36269 be entered again later in order to unlock the keyboard.
36270 ========== h_compose_default ==========
36271 N, compose a new message. R, set a role.
36272 ^C to cancel.
36273 ========== h_untranslatable ==========
36274 Send using UTF-8 character set; Send but replace untranslatable characters
36275 with question marks; return to the composer; or cancel message altogether.
36276 ========== h_compose_intrptd ==========
36277 N, compose a new msg. I, continue interrupted msg. R, set a role.
36278 ^C to cancel.
36279 ========== h_compose_postponed ==========
36280 N, compose a new message. P, continue postponed msg. R, set a role.
36281 ^C to cancel.
36282 ========== h_compose_intrptd_postponed ==========
36283 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
36284 R, set a role. ^C to cancel.
36285 ========== h_compose_form ==========
36286 N, compose a new message. F, use form letter. R, set a role.
36287 ^C to cancel.
36288 ========== h_compose_intrptd_form ==========
36289 N, compose a new msg. I, continue interrupted msg. F, use form letter.
36290 R, set a role. ^C to cancel.
36291 ========== h_compose_postponed_form ==========
36292 N, compose a new message. P, continue postponed msg. F, use form letter.
36293 R, set a role. ^C to cancel.
36294 ========== h_compose_intrptd_postponed_form ==========
36295 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
36296 F, use form letter. R, set a role. ^C to cancel.
36297 ========== h_config_context_del_except ==========
36298 If you delete the last exceptional collection you can only add it back by
36299 manually editing the exceptions config file.
36300 ========== h_config_whereis ==========
36301 To move quickly to a particular line, enter a search string or
36302 ^C to cancel.
36303 ========== h_config_edit_scorei ==========
36304 Enter interval in the form (min,max). -INF and INF may be used to represent
36305 -infinity and infinity. ^C to cancel change. RETURN to accept change.
36306 ========== h_config_add ==========
36307 Enter desired value; use normal editing keys to modify (e.g. ^K, ^D). Just
36308 pressing RETURN sets the Empty Value (this turns off any global default).
36309 ========== h_config_add_custom_color ==========
36310 Enter a header fieldname. For example, "subject" or "from".
36312 ========== h_config_add_pat_hdr ==========
36313 Enter a header fieldname. For example, "reply-to" or "organization" or
36314 any fieldname you want that isn't included already.
36315 ========== h_config_print_opt_choice ==========
36316 You may edit either the initialization string (characters printed before
36317 printing starts) or the trailer string. Choose one or ^C to cancel.
36318 ========== h_config_print_init ==========
36319 Enter a C-style string for this. You may use common backslash escapes like
36320 \\n for newline, \\ooo for octal character, and \\xhh for hex character.
36321 ========== h_config_change ==========
36322 Edit the existing value using arrow keys, ^K to delete entire entry, ^D to
36323 delete current (highlighted) character, etc. Enter ^C to cancel change.
36324 ========== h_config_replace_add ==========
36325 Replace ignores the current default, Add places the current default in your
36326 editing buffer as if you had typed it in.
36327 ========== h_config_insert_after ==========
36328 Enter a nickname for this print command. (InsertBefore puts the new item
36329 before the current line, InsertAfter puts it after the current line.)
36330 ========== h_config_print_cmd ==========
36331 Enter command to be executed for the printer. Use normal editing keys
36332 to modify, ^C to cancel, carriage return to accept current value.
36333 ========== h_config_role_del ==========
36334 Answering Yes will remove this rule completely from your rules list.
36335 ========== h_config_role_addfile ==========
36336 Type the name of a file to add to your configuration. You don't need to
36337 use a file, you may add rules directly (with Add) without using a file.
36338 ========== h_config_role_delfile ==========
36339 Answering Yes will remove this rule file completely from your rules list.
36340 The rules data file itself will not be removed.
36341 ========== h_config_print_del ==========
36342 Answering Yes will remove this printer completely from your printer list.
36343 ========== h_config_print_name_cmd ==========
36344 You may edit the Nickname of this printer, the Command to be executed when
36345 printing, or change the Options associated with this printer.
36346 ========== h_send_check_fcc ==========
36347 Yes, send message without an Fcc.
36348 No, return to composer.
36349 ========== h_send_check_subj ==========
36350 Yes, send message without a Subject.
36351 No, return to composer.
36352 ========== h_send_check_to_cc ==========
36353 Yes, send message without a To address, or a Cc address, or a Newsgroup.
36354 No, return to composer.
36355 ========== h_send_fcc_only ==========
36356 Yes, copy message to Fcc only and send to NO recipients.
36357 No, return to composer.
36358 ========== h_send_prompt ==========
36359 Yes, send the message.
36360 No or ^C, return to composer.
36361 ========== h_send_prompt_flowed ==========
36362 Yes, send the message. No or ^C, return to composer.
36363 What's Flowed? See Do Not Send Flowed Text in config screen.
36364 ========== h_send_prompt_dsn ==========
36365 Yes, send the message. No or ^C, return to composer.
36366 What's DSNOpts? See Enable Delivery Status Notification in config screen.
36367 ========== h_send_prompt_dsn_flowed ==========
36368 Yes, send the message. No or ^C, return to composer. What's DSNOpts? See
36369 Enable Delivery Status Notification. What's Flowed? See Do Not Send Flowed Text.
36370 ========== h_role_confirm ==========
36371 Yes, use displayed role. No, compose without a role.
36372 ^C, cancel the message. ^T, select a role from your other eligible roles.
36373 ========== h_norole_confirm ==========
36374 Return, compose without a role.
36375 ^C, cancel the message. ^T, select a role from your eligible roles.
36376 ========== h_custom_print ==========
36377 Enter a Unix command that accepts its data on standard input.
36378 Alpine will display any information the command sends to standard output.
36379 ========== h_convert_abooks_and_sigs ==========
36380 You will be given the opportunity to convert address books and signature files
36381 to remote configurations.
36382 ========== h_convert_abooks ==========
36383 You will be given the opportunity to convert address books to remote
36384 configurations.
36385 ========== h_flag_keyword ==========
36386 Enter the name of the keyword you want to add for this folder.
36387 No spaces, parentheses, braces, percents or asterisks are allowed.
36388 ========== h_select_keyword ==========
36389 Enter the keyword you want to match, or use ^T to select a keyword from a list
36390 of possible keywords for this folder. Use ! to look for non-matches instead.
36391 ========== h_type_keyword ==========
36392 Enter the keyword you want to add. You may add a nickname in the next step.
36393 No spaces, parentheses, braces, percents or asterisks are allowed.
36394 ========== h_type_keyword_nickname ==========
36395 Enter an optional nickname for the keyword you want to add.
36396 Type Carriage return to use the keyword name instead of a nickname.
36397 ========== h_convert_sigs ==========
36398 You will be given the opportunity to convert signature files to remote
36399 configurations.
36400 ========== h_convert_abook ==========
36401 Yes is fairly safe. You will be ADDing a remote address book that is a copy
36402 of the current address book. The current abook won't be removed automatically.
36403 ========== h_convert_sig ==========
36404 Answering Yes copies the contents of the signature file into your Alpine
36405 configuration file. After that, the contents of the file will not be used.
36406 ========== h_save_addman ==========
36407 Enter the simple name of the folder you want to add. Carriage return to
36408 accept what you have typed so far. ^C to get back to SELECT FOLDER screen.
36409 ========== h_reopen_folder ==========
36410 Yes reopens the folder, as if you were starting over. This uncovers new mail.
36411 No leaves the folder index as it was without discovering new mail.
36412 ========== h_convert_pinerc_server ==========
36413 This is the name of the host (computer) where the remote Alpine configuration
36414 will be stored. This should be an IMAP server that you have permission to use.
36415 ========== h_convert_pinerc_folder ==========
36416 Enter the correct remote folder name. This folder is special and should
36417 contain only configuration data. It shouldn't contain other mail messages.
36418 ========== h_role_compose ==========
36419 Compose a New message, Reply to current message, Forward current message, or
36420 Bounce message. Then you will be asked to choose one of your Roles to be used.
36421 ========== h_save_size_changed ==========
36422 The reported size of a message is not the same as the actual size. Answer Yes
36423 to continue and hope for the best or No to Cancel the entire Save.
36424 ========== h_select_by_larger_size ==========
36425 Enter a number or ^C to cancel. All messages greater than this many characters
36426 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
36427 ========== h_select_by_smaller_size ==========
36428 Enter a number or ^C to cancel. All messages less than this many characters
36429 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
36430 ========== h_preserve_field ==========
36431 Use 'p' to toggle between preserving or not preserving the original To:
36432 and Cc: fields of the message. Enter ^C to cancel message.