| blob | 59ab557465ad60e34e3841debb7026d2160bc62c |
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-2014 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 52 2014-04-08 23:57:42
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-2014 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 2008 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 <P>
183 <UL>
184 <LI> Upgrade UW-IMAP to Panda IMAP from
185 <A HREF="https://github.com/jonabbey/panda-imap">https://github.com/jonabbey/panda-imap</A>.
186 <LI> S/MIME: Add screen to manage certificates.
187 <LI> Replace tabs by spaces in From and Subject fields to control for
188 size in screen of these fields. Change only in index screen display.
189 <LI> Add support to selective expunge through a subcommand of the
190 select-apply commands. Read more in the <A
191 HREF="h_index_cmd_expunge">help</A> for the expunge command.
192 <LI> Pico: New subcommand of the search command, allows to reverse the
193 direction of search.
194 <LI> If a password file is defined, and S/MIME is enabled, the key that is
195 used to encrypt the password file is saved under the name password_file_key.
196 <LI> Add /tls1, /tls1_1, /tls1_2 and /dtls1 to the definition of a
197 server to use different ways to connect using ssl, for
198 example {server.com/tls1} will attempt to connect to
199 server.com at the ssl imap port (port 993) and establish a
200 connection using TLSv1. These flags can be used in
201 conjunction with the /ssl flag, the ssl flag is redundant.
202 Conversely, however, the /ssl flag does not imply any of
203 these flags; the /ssl flag means SSLv3 or, if not available,
204 SSLv2 in the SSL port.
205 <LI> Alpine does not attempt to automatically reopen a collection
206 that was not opened due to cancellation by the user.
207 Instead, the user must try to open it explicitly.
208 <LI> Alpine searches for a certificate that matches an email address in
209 all addresses in a certificate (instead of just the first
210 one) but when it tries to unlock the certificate, it asks
211 for the password for the first email address in that
212 certificate.
213 <LI> Style tag in body of html message causes Alpine to not write its content
214 until a new </style>
215 <LI> Experimental: Write the content-type of a message in
216 lowercase, as some non-compliant servers do not understand
217 uppercase content-type, such as those of GMX.de.
218 <LI> Opening a folder updates recent count in maildrops (this
219 already works for other types of folders)
220 <LI> Automatically redraw screen after opening an attachment
221 instead of simply clearing it.
222 <LI> Pico: Justification works without need of a predefined quote
223 string. This allows justification of blocks of text that are
224 indented with spaces.
225 <LI> Check bounds and tie strings off to improve security. Contributed
226 by James Jerkins.
227 </UL>
229 <P>
230 Bugs that have been addressed include:
231 <UL>
232 <LI> Fix _INIT_ token for reply quote string to include support for 8-bit
233 in personal names. Reported by Lev Gorenstein.
234 <LI> When writing the .pinerc file, lines were truncated if they were longer
235 than 10,000 characters. This could cause data corruption, so now lines
236 are allowed to be of any length.
237 <LI> In Unix Alpine (but not in MAC OSX) fix a problem that made Alpine
238 remove attachments before they were open by a mailcap viewer. It
239 requires that the user has an equivalent to a command such as "ps
240 auxww" to list the list of processes, and check if there is any
241 program using the attachment. The default is "/bin/ps auxww", but
242 it can be changed at compile time with the option --with-ps-cmd.
243 See the help of the variable
244 <a href="h_config_psleep"><!--#echo var="VAR_mailcap-check-interval"--></a>
245 for more information.
246 <LI> S/MIME: signed messages that contained an attachment would not validate.
247 <LI> S/MIME: signed and encrypted messages from Thunderbird would not
248 validate. Thanks to Andreas Schamanek for testing, debugging and
249 advising during the process of fixing this problem.
250 <LI> S/MIME: Forwarding messages with multipart content-type failed to be signed
251 with "Error writing pipe" message. Reported by Andreas Schamanek
252 and Stefan Mueller.
253 <LI> S/MIME: Certificates are lost when using a pinerc file outside of the
254 home directory.
255 <LI> S/MIME: accessing the S/MIME configuration screen would deinitialize
256 SMIME making it not possible to sign or encrypt messages.
257 <LI> Crash when tcp connection to NNTP server was lost after connection
258 had been established, but lost immediately afterwards.
259 <LI> WebAlpine: add _GNU_SOURCE to make pubcookie build.
260 <LI> Save command did not warn of existence of a message with a deleted
261 attachment in an aggregate save, unless cursor was positioned on a message
262 with a deleted attachment. Reported by Florian Herzig.
263 <LI> Transformation of UTF-8 to MUTF7 was not being done when creating a folder
264 in an IMAP server.
265 <LI> DATE tokens were not internally transformed to UTF-8, which made their
266 values not appear complete in the screen. Reported by Werner Scheinast.
267 <LI> Fixes to configure script so that it will not require PAM for every system.
268 <LI> Fix to configure script so that it will use CPPFLAGS instead of
269 CPPCFLAGS, and so the --with-ssl-include-dir option take effect
270 during the build. Fix by Ulf-Dietrich Braumann.
271 <LI> Fix in WebAlpine: do not use deprecated dereference in pointer,
272 needs to use tcl_getstringresult() instead. Reported by
273 Ulf-Dietrich Braumann.
274 <LI> Quoted string in URL Viewers configuration variable were not
275 unquoted before passing to viewer.
276 <LI> Fix in configure script to detect location of tcl library; add
277 /usr/local in FreeBSD and fix a bug in configure script that used
278 $alpine_TCLINC instead of $alpine_TCLINC/tcl.h. Reported and fixed
279 by Werner Scheinast.
280 <LI> Move SSL configurations from UW-IMAP to configure script, and
281 update OpenSSL configuration for mac OSX.
282 <LI> Remove -lregex from linker flags when building --with-supplied-regex.
283 </UL>
284 <P>
287 <P>
288 Version 2.11 addresses bugs found in previous releases and has a few
289 additions as well.
291 <P>
292 Additions include:
293 <P>
295 <UL>
296 <LI> Alpine requires version 1.0.1c of Openssl to build.
297 <LI> Increase encryption of S/MIME encrypted messages.
298 <LI> Pico: Improvements in justification of paragraphs: lines that begin
299 with a quote string, followed by a space were considered individual paragraphs,
300 now they are considered part of a paragraph. Based on earlier joint work
301 with Jeff Franklin.
302 <LI> Unix Alpine: Allow local .pinerc file to be a symbolic link.
303 <LI> Experimental extended support of recognition of UTF-8 in urls based on
304 information from <A HREF="http://url.spec.whatwg.org">http://url.spec.whatwg.org</A>.
305 <LI> Added recognition of ws and wss URIs.
306 <LI> Add ability to <A HREF="h_config_folder_color">color folder names</A>,
307 <A HREF="h_config_directory_color">directory names</A>,
308 and <A HREF="h_config_folder_list_color">text</A> in the FOLDER SCREEN.
309 <LI> Add the ability to <A HREF="h_config_indextoken_color">color any token</A>
310 used in the display of the INDEX SCREEN.
311 <LI> New option <A HREF="h_config_preserve_field"><!--#echo var="FEAT_preserve-original-fields"--></A>
312 that adds the ability to preserve To: and Cc: fields when replying to a
313 message, as specified by original sender.
314 <LI> Add a _SILENT_ token to the <A HREF="h_config_display_filters">list of tokens</A>
315 for a display filter, so that Alpine will not redraw the screen when it is unnecessary.
316 <LI> Quota command includes subcommands for printing, forwarding, etc.
317 </UL>
319 <P>
320 Bugs that have been addressed include:
321 <P>
322 <UL>
323 <LI> Crash when a non-compliant SMTP server closes a connection without a QUIT command.
324 <LI> Crash when resizing the screen in a configuration screen.
325 <LI> Do not bail out during a tcp timeout, instead close connection and avoid crash.
326 <LI> Do not use a shell to open a browser.
327 <LI> Configure script did not test for crypto or pam libraries.
328 <LI> Configure script attempted to build web component, even if header file tcl.h was not present.
329 <LI> Change Cygwin directory separator to "/".
330 <LI> Alpine could set List- headers, contrary to RFC 2369.
331 </UL>
333 <P>
334 Version 2.10 addresses bugs found in previous releases and has a few
335 additions as well.
337 <P>
338 Additions include:
339 <P>
341 <UL>
342 <LI> Quota report for IMAP folders that support it (press the "@" command in the index screen of such folder).
343 <LI> Search a folder for the content of any header with the ";" command.
344 <LI> Foreign characters are decoded correctly in IMAP folders.
345 <LI> Question about breaking connection to slow servers includes their name.
346 <LI> Internal x-alpine-help: resource locator for sending links to internal help.
347 <LI> OpenSuse: Alpine find location of OpenSSL certificates.
348 <LI> Cygwin: Alpine builds without need of patch.
349 <LI> Recognition of proper mime type for docx, xlsx, and pptx files.
350 <LI> When composing a message, Alpine will create a new thread when the subject is erased.
351 <LI> Add support for strong encryption of password file when S/MIME is built in.
352 </UL>
354 <P>
355 Bugs that have been addressed include:
356 <P>
358 <UL>
359 <LI> Alpine will close a folder after confirming with user their intention and not reopen it.
360 <LI> Double allocation of memory in Pico.
361 <LI> Alpine does not give warning of message sent and posted upon receipt by email of message posted in newsgroup.
362 <LI> Handling of STYLE html parameter may make Alpine not display the content of a message.
363 <LI> Not recognition of environment variables in some options.
364 <LI> Not display of login prompt during initial keystrokes.
365 <LI> justification of long urls breaks them.
366 <LI> Incorrect New Mail message when envelope is not available.
367 <LI> Inorrect display of PREFDATE, PREFDATETIME and PREFTIME tokens.
368 <LI> Crash when resizing the screen after display of LDAP search.
369 <LI> Crash when redrawing screen while opening a remote folder collection.
370 <LI> Infinite loop in scrolltool function during notification of new mail.
371 <LI> No repaint of the screen after midnight was done when the SMARTDATE token is used in the index screen.
372 <LI> No display of signed and encrypted S/MIME messages.
373 <LI> Alpine will not build with OpenSSL.
374 <LI> Crash for double locking in calls to c-client.
375 <LI> Bad recognition of mime-encoded text may make Alpine not print the subject of a message.
376 <LI> Ignore the references header when threading messages
377 <LI> No update of colors in index screen after update to addressbook.
378 </UL>
380 <P>
381 Version 2.01 addresses bugs found in previous releases and has a few
382 additions as well.
384 <P>
385 Additions include:
386 <P>
388 <UL>
389 <LI> Fixed non-ASCII web alpine handling
390 <LI> Added web alpine help.
391 <LI> Allow web alpine inbox on second IMAP server.
392 <LI> Allow web alpine config reset after bad inbox-path gets set.
393 <LI> Added web alpine ability to create group contact from contact list members.
394 <LI> Backed out web alpine coercing of default sort-key of arrival to date/reverse.
395 <LI> Tidied up web alpine script layout.
396 <LI> Fixed web alpine status message ordering
397 <LI> Added web alpine Fcc setting via Contacts in Compose
398 <LI> Fixed web alpine autodraft attachment issues
399 <LI> Fixed web alpine problems with recent count maintenance
400 <LI> Fixed web alpine newmail arrival display in message list
401 <LI> Added web alpine confirmation to folder create for Move/Copy
402 <LI> Added web alpine user-domain support
403 <LI> Fixed web alpine to support INBOX-within-a-collection deletion
404 </UL>
406 <P>
407 Bugs that have been addressed include:
408 <P>
410 <UL>
411 <LI> In web alpine fixed delete all selected within a search result to reorient
412 correctly to whole-mailbox message list.
413 <LI> Fixed web alpine delete in view page to be sensitive to sort
414 <LI> Fixed web alpine open of folder within directory from folder manager page.
415 <LI> Fixed web alpine open of folder within directory from left column's recent cache.
416 <LI> Fixed web alpine problems with spaces in special folder names like Drafts
417 <LI> Fixed web alpine adding contacts from message list and view
418 <LI> Fixed web alpine create of non-existent fcc
419 <LI> Remove mistakenly left debugger statement in web alpine javascript.
420 <LI> Some UNIX alpine build problems fixed
421 <LI> Crash in pico and pilot when nl_langinfo returned something unrecognizable
422 or NULL. Add recognition of "646" to nl_langinfo wrapper. This is returned
423 by locale charmap call on some Solaris 8 systems.
424 <LI> MacOS Keychain logins were not working correctly with generic host names, like
425 imap.gmail.com, as opposed to specific instances like rx-in-209.google.com, causing
426 new password requests when not needed
427 <LI> Possible crash in WhereIs command while in FOLDER LIST when cursor is located on the
428 last folder in the list
429 <LI> Change to S/MIME get_x509_subject_email so that X509v3 alternative names are
430 looked for along with the email address
431 <LI> Changes to configure to get spellcheck options with work with arguments.
432 <LI> Add change from Mark Crispin of panda.com to at least minimally handle non-ascii hostname
433 returned by gethostname (iPhone can do this)
434 <LI> Fixed a bug that prevents a filter that moves a message into a local folder
435 from also setting the DELETE flag in that moved message. Fix from Eduardo Chappa.
436 <LI> Changed size of shellpath in open_system_pipe from 32 to MAXPATH. Fix from
437 Jake Scott of marganstanley.com.
438 <LI> Buffer overflow bug in c-client's tmail/dmail, fix from Mark Crispin. This
439 is not used in alpine.
440 <LI> Imapd server crash from unguarded fs_give in IDLE code, fix from Crispin.
441 Apparently this causes RIM Blackberry BIS service problems. This is not
442 used in alpine.
443 <LI> Tmail uninitialized pointer fix from Neil Hoggarth. Not used in alpine.
444 <LI> Buffer overflow possibility in RFC822BUFFER routines in c-client library.
445 Fix from Ludwig Nussel of SUSE and from Crispin.
446 <LI> Include whole filename in export filename history
447 <LI> Fix display bug in pico when Replace command is canceled. Fix from Eduardo Chappa.
448 </UL>
450 <P>
451 Version 2.00
452 addressed bugs found in previous releases and had a few additions as well.
453 <P>
454 Additions included:
455 <P>
457 <UL>
458 <LI> Redesigned Web Alpine interface
459 <LI> Experimental <A HREF="h_mainhelp_smime">S/MIME support</A> added
460 in UNIX versions of Alpine
461 <LI> Attempt to include the attachment filename as part of the name of the
462 temporary file used when viewing an attachment with an external program.
463 Add some randomness to that filename to make it hard to predict the filename.
464 Add a filename extension, usually derived from the type/subtype, to the
465 temporary filename. This was previously done only on Windows and MacOS X.
466 <LI> Enhance address completion in the composer (TAB command) so that it looks
467 through nicknames, fullnames, and addresses from the address book; addresses
468 from the message being viewed, if any; and the results from
469 <A HREF="h_direct_config">LDAP Directory Server</A>
470 lookups for all of the defined directory servers that have the
471 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
472 feature set.
473 <LI> Make the default character set setting more liberal in what it will accept
474 from the UNIX nl_langinfo call and the various values of LANG seen in the wild
475 <LI> Remove the Alpine revision number from the titlebar in released versions
476 while leaving it there in snapshot versions
477 <LI> Add a <A HREF="h_config_quell_asterisks">feature</A> to suppress the
478 display of asterisks when you type a password for Alpine
479 <LI> Add line wrapping when displaying <EM>PRE</EM> formatted sections of HTML
480 <LI> When the
481 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
482 feature is turned on convert not only the dates in the index screen but also
483 the dates in the MESSAGE VIEW
484 </UL>
486 <P>
487 Bugs addressed in the 2.00 release included:
488 <P>
490 <UL>
491 <LI> Crash when using tab-completion for selecting a Save filename
492 <LI> Make Web Alpine help text images relative for more portability
493 <LI> Fixed attach save of html parts in Web Alpine
494 <LI> Viewing, printing, exporting, replying, and bouncing of message
495 digests was broken. Replying and bouncing should not have been
496 allowed at all for digests. It would be nice to have a more standard
497 index-like view of a message digest but that has not been addressed
498 with this minor bug fix.
499 <LI> Adjust wrapping of HTML messages so that the margins specified by
500 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
501 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>
502 are observed correctly
503 <LI> Interrupt of WhereIs command in index was broken
504 <LI> The <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
505 option did not work correctly interpreting unknown characters in message headers
506 <LI> Long address lines could cause blank continuation lines
507 <LI> Save to a local default INBOX failed if the primary collection was also local,
508 which it is by default. The save went to ~/mail/inbox instead.
509 <LI> Make a default save folder of "inbox" always mean the real
510 inbox, not the inbox in the primary collection
511 <LI> Address book entries with lots of addresses would be truncated when
512 entered in the composer with a screen size wider than 270 or so charcters
513 <LI> Some fields in the index screen were truncated when the screen width was
514 wider than 256 characters
515 <LI> Crash when TABing to next folder, the next folder with new mail is a POP
516 folder, and there is a more than 10 minute pause between typing the TAB
517 and typing the Yes
518 </UL>
520 <P>
521 Version 1.10(962)
522 addressed bugs found in previous releases and had a few additions as well.
523 <P>
524 Additions included:
525 <P>
527 <UL>
528 <LI> Add the possibility of setting a default role
529 (see <A HREF="h_role_select">Roles Screen</A>)
530 which may be convenient if your work flow involves acting in one
531 role for a while then switching to another role and staying in the
532 new role for another period of time
533 <LI> When Saving and the IMAP server problem "Message to save shrank!"
534 is encountered, ask the user if he or she wants to continue with the
535 risky Save anyway instead of aborting. This may be helpful if your
536 IMAP server is broken in this way but be aware that it is possible there
537 was a real error instead of just a broken server implementation.
538 <LI> Some configure adjustments for Kerberos detection and
539 for SCO OpenServer 5 support
540 <LI> Hide INBOX in a collection if it also appears as an
541 <A HREF="h_config_enable_incoming">Incoming Folder</A>
542 <LI> Show asterisks for feedback when the user is typing a password
543 <LI> Performance improvement for threading of large folders
544 <LI> Previously, the search used to find
545 Pattern matches containing To patterns searched for both To
546 and Resent-To headers. The relatively complicated search this
547 produces causes problems when using some deficient IMAP servers.
548 Now the default is to look only for To headers and ignore the
549 presence of Resent-To. The previous behavior may be restored
550 with the <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> feature.
551 <LI> Add an
552 <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
553 to help with reading malformed unlabeled messages
554 <LI><A HREF="h_config_suppress_user_agent"><!--#echo var="FEAT_suppress-user-agent-when-sending"--></A> option added
555 <LI> Map some Shift-LeftArrow escape sequences to LeftArrow
556 <LI> Add feature <A HREF="h_config_warn_if_fcc_blank"><!--#echo var="FEAT_warn-if-blank-fcc"--></A>
557 </UL>
559 <P>
560 Bugs addressed in the 1.10(962) release included:
561 <P>
563 <UL>
564 <LI> Crash when encountering certain errors from an SMTP server
565 <LI> Crash in composer caused by overflow in replace_pat()
566 <LI> Hang when authenticating to an SMTP server that fails with a
567 "connection disconnected" error
568 <LI> Bug in handling of trailing tab character in flowed text
569 <LI> Security enhancement for mailcap parameter substitution
570 <LI> <A HREF="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></A>
571 did not work if the message being replied to was not flowed text
572 and <A HREF="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></A>
573 was not turned on
574 <LI> Don't allow printer to be changed through hidden config screen
575 if system administrator didn't want it to be allowed
576 <LI> Attempts are sometimes made to set the Forwarded flag when alpine
577 should know that it won't work, causing error messages to appear
578 <LI> A <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
579 of double-quote double-quote didn't work right
580 <LI> Quoting wasn't being done to protect special characters from the
581 MacOS X shell when
582 <A HREF="h_config_browser"><!--#echo var="VAR_url-viewers"--></A>
583 was not defined
584 <LI> On MacOS X message attachments should be shown internally instead of
585 being shown using the Mail application
586 <LI> When replying to a message with a charset of X-UNKNOWN Alpine would
587 sometimes set the outgoing charset to X-UNKNOWN, making the result
588 unreadable
589 <LI> When the sending of a message failed lines with leading spaces had one
590 additional space inserted in each of those lines when the user
591 was returned to the composer
592 <LI> The <A HREF="h_index_cmd_whereis">WhereIs</A> command missed some index lines
593 that contained non-ascii characters because it was truncating the
594 line being searched so that it was shorter than what was visible on
595 the screen
596 <LI> When composing, an attachment with a long name that causes wrapping in
597 just the wrong place would generate an error and cause the send
598 of the attachment to fail
599 <LI> After calling the file browser to attach a file in the composer, a resize
600 of the window when back in the composer would redraw the last screen that
601 had been shown in the browser instead of the current composer screen
602 <LI> Possible crash in index screen when encountering unparseable addresses
603 or when using one of the PRIORITY tokens or the HEADER token in the
604 <a href="h_config_index_format"><!--#echo var="VAR_index-format"--></a>
605 <LI> Problems with Header Color editing if the configuration option
606 <a href="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></a>
607 was inadvertently changed to the Empty Value in the hidden config screen
608 <LI> When resuming the final postponed message from an Exchange server the user
609 could get a certificate validation failure because alpine was trying
610 to validate the canonical name of the folder instead of the name the
611 user used
612 <LI> Windows line endings in a mimetypes file on a Unix system cause a
613 failure to find a match
614 <LI> Make matching of extension names case independent in mimetypes files
615 <LI> Windows dialog boxes for entering text were not working correctly
616 <LI> Replying to or Forwarding multipart/alternative messages which had a
617 single text/html part did not work well
618 <LI> Printing the print confirmation page caused a crash
619 <LI> A To line with a long, quoted personal name could display incorrectly
620 if it was close to the same width as the screen
621 <LI> When <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
622 and <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
623 are turned on hide (0/0) when the folder is empty
624 <LI> Folder completion while Saving didn't work if the collection being
625 saved to was the local home directory
626 </UL>
628 <P>
629 Version 1.00
630 was an evolutionary release based on
631 <A HREF="http://www.washington.edu/pine/">Pine</A>, which was also
632 developed at the University of Washington.
633 It is upwards-compatible for existing Pine users.
635 <P>
636 Changes included:
637 <P>
638 <UL>
639 <LI> Ground-up reorganization of source code around addition
640 of "pith/" core routine library.
641 <LI> Fundamental improvement in Alpine's internal text handling, which
642 is now based exclusively on Unicode. This allows displaying incoming
643 messages and producing outgoing messages in many different languages.
644 <LI> Ground-up reorganization of build and install procedures
645 based on GNU Build System's autotools. NOTE, the included IMAP library
646 build is not based on autotools, so some features will not work. However,
647 it should get built automatically during the Alpine build process.
648 <LI> Web-based version included built on TCL designed to run under
649 a suitable CGI-supporting web server such as Apache.
650 </UL>
652 <P>
654 Details on changes in previous (prerelease) versions of Alpine
655 may be found at the following URL:
656 <P>
657 <CENTER><SAMP><A HREF="http://patches.freeiz.com/alpine/release/">http://patches.freeiz.com/alpine/release/</A></SAMP></CENTER>
658 <P>
660 <HR WIDTH="75%"><P>
662 <H2>Getting Help</H2>
663 <DL>
664 <DT>Online Help</DT>
665 <DD>
666 Every Alpine screen and command has associated help text
667 accessible via the "?" key (or Ctrl-G in text-input contexts).
668 </DD>
670 <DT>Web Help</DT>
671 <DD>
672 The most current source of information about Alpine,
673 including new version availability, is the web page at
674 <P>
675 <CENTER><SAMP><A HREF="http://patches.freeiz.com/alpine/">http://patches.freeiz.com/alpine/</A></SAMP></CENTER>
676 </DD>
677 </DL>
679 Frequently Asked Questions (and answers) may be found at the following
680 URL:
681 <P>
682 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/faq/">http://www.washington.edu/alpine/faq/</A></SAMP></CENTER>
683 <P>
685 <HR WIDTH="75%"><P>
687 <H2>Additional Information</H2>
689 General Alpine configuration information can be found
690 <A HREF="h_news_config">here</A>.
691 <P>
692 This is revision (<!--#echo var="ALPINE_REVISION"-->) of the Alpine software.
693 Alpine mailbox and <A HREF="https://github.com/jonabbey/panda-imap/">IMAP</A> server
694 access is provided by the IMAP Toolkit Environment (c-client library)
695 version <!--#echo var="C_CLIENT_VERSION"-->.
696 <P>
697 Alpine was developed until 2009 by the Office of Computing
698 & Communications at the University of Washington in Seattle.
699 Since then, the effort of developing Alpine has been continued by
700 a community of volunteers who make a good software even better!
702 <P>
703 Alpine Copyright 2013-2014 Eduardo Chappa,
704 <BR> Copyright 2006-2008 University of Washington.
706 <P>
707 Additional legal notices can be found <A HREF="h_news_legal">here</A>,
708 or instead you can find the Apache License, version 2.0 at the web URL:
710 <P>
711 <CENTER><A HREF="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</A></CENTER>
713 <P>
714 <End of Release Notes>
715 </BODY>
716 </HTML>
717 ====== h_tls_failure_details ======
718 <HTML>
719 <HEAD>
720 <TITLE>Certificate Validation Details</TITLE>
721 </HEAD>
722 <BODY>
723 <H1>Certificate Validation Details</H1>
725 This screen gives details as to why the certificate validation failed: the
726 name of the desired server system; the reason for failure; and the name on
727 the certificate. This is primarily of interest to experts.
729 <P>
730 <End of help>
731 </BODY>
732 </HTML>
733 ====== h_tls_failure ======
734 <HTML>
735 <HEAD>
736 <TITLE>TLS or SSL Failure</TITLE>
737 </HEAD>
738 <BODY>
739 <H1>TLS or SSL Failure</H1>
741 An attempt was made to establish a secure, encrypted connection to the
742 server system using either Transport Layer Security (TLS) or the older
743 Secure Sockets Layer (SSL). This attempt failed.
745 <P>
746 You should contact your server system management for more assistance.
747 The problem is probably at the server system and not in Alpine or your local
748 system. The text in this screen may be helpful for the server system
749 management in debugging the problem,
751 <P>
752 <End of help>
753 </BODY>
754 </HTML>
755 ====== h_tls_validation_failure ======
756 <HTML>
757 <HEAD>
758 <TITLE>TLS and SSL Certificate Validation Failures</TITLE>
759 </HEAD>
760 <BODY>
761 <H1>TLS and SSL Certificate Validation Failures</H1>
763 An attempt was made to establish a secure, encrypted connection to the
764 server system using either Transport Layer Security (TLS) or the older
765 Secure Sockets Layer (SSL).
767 <P>
768 An important part of this procedure is server certificate validation. A
769 server certificate is an "electronic identification card" for the server
770 system that is signed by a well-known certificate authority (CA). Alpine
771 compares the server system identity in the server certificate with the
772 name of the server system to which it is trying to connect. Alpine also
773 verifies that the CA signature is authentic.
775 <P>
776 Some common failure conditions are:
777 <P>
779 <UL>
780 <LI> [UNIX Alpine] Self signed certificate. This means that the server system
781 signed its own certificate. This does not necessarily indicate anything
782 bad; the server operators may simply have elected to not purchase a
783 signed certificate from a certificate authority.
785 <LI> [UNIX Alpine] Unable to get local issuer certificate. This means that
786 the signature on the server system is from an unknown certificate authority.
787 It can also mean that no certificate authority certificates have been
788 installed on the local UNIX system.
790 <LI> [PC Alpine] Self-signed certificate or untrusted authority. This is
791 the same as either of the above two conditions in UNIX Alpine. Note that
792 Windows systems typically have a full set of certificate authority
793 certificates installed, so it is more likely to be a self-signed
794 certificate than an unknown certificate authority.
796 <LI> Server name does not match certificate. This means that the server
797 presented a proper signed certificate for a name other than the desired
798 name.
799 </UL>
801 <P>
802 Any of these conditions can indicate that you are being attacked and have
803 been directed to an imposter server that will record your password and
804 your private mail messages. It can also mean something innocuous.
806 <P>
807 If you are certain that the problem is innocuous, you can append the
808 option
810 <P>
811 <CENTER><SAMP>/novalidate-cert</SAMP></CENTER>
812 <P>
814 to the server system name where it appears in your configuration (e.g. the
815 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>,
816 a folder-collection, or a news or SMTP server). This will
817 disable certificate validation. On the other hand, if you are attacked,
818 you will get no warning if you do this.
820 <P>
821 <End of Cert Validation Failures help>
822 </BODY>
823 </HTML>
824 ====== h_release_tlscerts ======
825 <HTML>
826 <HEAD>
827 <TITLE>TLS and SSL usage note</TITLE>
828 </HEAD>
829 <BODY>
830 <H1>TLS and SSL usage note</H1>
832 <P>
833 When using Alpine from Unix or Windows 2000,
834 server certificates must be signed by a trusted certificate authority.
835 You may relax this requirement (at the cost of some security) by using
836 the
837 <A HREF="h_folder_server_syntax">NoValidate-Cert</A>
838 modifier in the mailbox name.
840 <P>
841 <CENTER><SAMP>{foo.example.com/novalidate-cert}INBOX</SAMP></CENTER>
842 <P>
844 The fully-qualified host name of the server should be used
845 so that it matches the host name in the server certificate.
846 <P>
847 Here is an example of a host specification that directs Alpine to use
848 the SSL port (993) and an encrypted data stream.
849 <P>
850 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
851 <P>
852 <End of TLS usage help>
853 </BODY>
854 </HTML>
855 ====== h_news_config ======
856 <HTML>
857 <HEAD>
858 <TITLE>Alpine Configuration</TITLE>
859 </HEAD>
860 <BODY>
861 <H1>Alpine Configuration</H1>
863 <H2>Using Environment Variables</H2>
865 The values of Alpine configuration options may include environment variables
866 that are replaced by the value of the variable at the time Alpine is run
867 (and also at the time the config option is changed).
868 The syntax to use environment variables is a subset of the common Unix
869 shell dollar-syntax.
870 For example, if
872 <P><CENTER><SAMP>$VAR</SAMP></CENTER><P>
874 appears in the value of an Alpine configuration option it is looked up in the
875 environent (using getenv("VAR")) and its
876 looked-up value replaces the <SAMP>$VAR</SAMP> part of the option value.
877 To include a literal dollar sign you may precede the dollar sign with another
878 dollar sign.
879 In other words, if the text
881 <P><CENTER><SAMP>$$text</SAMP></CENTER><P>
883 is the value of a configuration option, it will be expanded to
885 <P><CENTER><SAMP>$text</SAMP></CENTER><P>
887 and no environment lookup will be done.
888 For Unix Alpine it will also work to use a backslash character to
889 escape the special meaning of the dollar sign, but $$ is preferable since
890 it works for both PC-Alpine and Unix Alpine, allowing the configuration option
891 to be in a shared configuration file.
892 <P>
894 This all sounds more complicated than it actually is.
895 An example may make it clearer.
896 Unfortunately, the way in which environment variables are set is OS-dependent
897 and command shell-dependent.
898 In some Unix command shells you may use
900 <P><CENTER><SAMP>PERSNAME="Fred Flintstone"</SAMP></CENTER><P>
901 <CENTER><SAMP>export PERSNAME</SAMP></CENTER><P>
903 Now, if you use Alpine's Setup/Config screen to set
905 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=$PERSNAME</SAMP></CENTER><P>
907 the <SAMP>$PERSNAME</SAMP> would be replaced by <SAMP>Fred Flintstone</SAMP>
908 so that this would be equivalent to
910 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=Fred Flintstone</SAMP></CENTER><P>
912 Note, environment variable substitution happens after configuration
913 options that are lists are split into the separate elements of the list,
914 so a single environment variable can't contain a list of values.
916 <P>
917 The environment variable doesn't have to be the only thing
918 after the equal sign.
919 However, if the name of the variable is not at the end of the line or
920 followed by a space (so that you can tell where the variable name ends),
921 it must be enclosed in curly braces like
923 <P><CENTER><SAMP>${VAR}</SAMP></CENTER><P>
925 It is always ok to use the braces even if you don't need to.
926 <P>
927 It is also possible to set a default value for an environment variable.
928 This default value will be used if the environment variable is not
929 set (that is, if getenv("VAR") returns NULL).
930 The syntax used to set a default value is
932 <P><CENTER><SAMP>${VAR:-default value}</SAMP></CENTER><P>
934 If the config file contains
936 <P><CENTER><SAMP>personal-name=${VAR:-Fred Flintstone}</SAMP></CENTER><P>
938 then when Alpine is run <SAMP>VAR</SAMP> will be looked up in the environment.
939 If <SAMP>VAR</SAMP> is found then <SAMP>personal-name</SAMP> will have
940 the value that <SAMP>VAR</SAMP> was set to, otherwise,
941 <SAMP>personal-name</SAMP> will be set to <SAMP>Fred Flintstone</SAMP>,
942 the default value.
943 (Note that the variable is called "personal-name" in the config
944 file but is displayed in the config screen as
945 "<!--#echo var="VAR_personal-name"-->".
946 In general, the value that goes into a config file is never exactly the
947 same as the value you see on the screen.)
949 <P>
950 An example where an environment variable might be useful is the
951 variable <SAMP>Inbox-Path</SAMP> in the global configuration file.
952 Suppose most users used the server
954 <P><CENTER><SAMP>imapserver.example.com</SAMP></CENTER><P>
956 but that there were some exceptions who used
958 <P><CENTER><SAMP>altimapserver.example.com</SAMP></CENTER><P>
960 In this case, the system manager might include the following line in
961 the systemwide default Alpine configuration file
963 <P><CENTER><SAMP>Inbox-Path=${IMAPSERVER:-imapserver.example.com}</SAMP></CENTER><P>
965 For the exceptional users adding
967 <P><CENTER><SAMP>IMAPSERVER=altimapserver.example.com</SAMP></CENTER><P>
969 to their environment should work.
970 <P>
971 Another example might be the case where a user has to use a different
972 SMTP server from work and from home.
973 The setup might be something as simple as
975 <P><CENTER><SAMP>smtp-server=$SMTP</SAMP></CENTER><P>
977 or perhaps a default value could be given.
978 Note that, as mentioned above, the variable <SAMP>SMTP</SAMP> cannot contain
979 a list of SMTP servers.
980 <P>
982 <H2>Configuration precedence</H2>
984 There are several levels of Alpine configuration. Configuration values at
985 a given level override corresponding values at lower levels. In order of
986 increasing precedence:
987 <P>
988 <UL>
989 <LI> built-in defaults
990 <LI> system-wide
991 <!--chtml if pinemode="os_windows"-->
992 config file from command line or provided
993 by "PINECONF" environment variable
994 <!--chtml else-->
995 pine.conf file
996 <!--chtml endif-->
997 <LI> personal configuration file
998 <LI> personal exceptions configuration file
999 <LI> command-line options
1000 <!--chtml if pinemode="os_windows"--><!--chtml else-->
1001 <LI> system-wide pine.conf.fixed file<!--chtml endif-->
1002 </UL>
1003 <P>
1004 The values in both the personal configuration file and the
1005 <A HREF="h_config_exceptions">exceptions</A>
1006 configuration file may be set using the Setup command.
1007 Setup/Config is the command to change most of the personal configuration
1008 options.
1009 The other Setup subcommands are also used to change the configuration,
1010 for example, Setup/AddressBook, Setup/Rules, and so on.
1011 Changing the personal exceptions configuration is very similar.
1012 To change a value in the Config screen you would use the command
1013 Setup/eXceptions/Config.
1014 Likewise for the other Setup subcommands (Setup/eXceptions/Rules and so on).
1015 <P>
1016 There are a couple exceptions to the rule that configuration values are replaced
1017 by the value of the same option in a higher-precedence file.
1018 The Feature-List variable has values that are additive, but can be
1019 negated by prepending "no-" in front of an individual feature name.
1020 So for features, each individual feature's value is replaced by the value
1021 of the same feature in a higher-precedence file.
1022 Note that this is done automatically for you when you change these values via
1023 the Setup/Config command.
1024 The other exception to the <EM>replace</EM> semantics happens when you
1025 use <A HREF="h_config_inheritance">configuration inheritance</A>
1026 for option lists.
1027 <P>
1029 <H2>File name defaults</H2>
1031 Notes:<P>
1033 <BR> <exe dir> = directory where pine.exe found.
1034 <BR> <pinerc dir> = directory where pinerc found.
1035 <BR> # = default file name is overridable in pinerc.
1036 <BR> $HOME, if not explicitly set, defaults to root of the current drive.
1037 <BR> $MAILCAPS, if set, is used in lieu of the default mailcap search paths.
1038 <BR> + between the mailcap paths implies that the two files are combined.
1039 <BR> ; between other default paths implies that the first one found is used.
1040 </P>
1041 Alpine looks for most support files in the same directory it finds its
1042 personal configuration file (pinerc). The -p command-line flag may be
1043 used to specify a particular path name for the pinerc file. If a
1044 pinerc file does not exist, it will be created (if directory permissions
1045 allow). In PC-Alpine, if -p or $PINERC are not defined, Alpine will look
1046 in $HOME\PINE and the directory containing the PINE.EXE. If a PINERC
1047 file does not exist in either one, it will create one in the first of those
1048 two directories that is writable. In detail:
1049 <PRE>
1051 PC-Alpine:
1053 executable <DOS search path>\pine.exe
1054 help index <exe dir>\pine.ndx
1055 help text <exe dir>\pine.hlp
1057 pers config $PINERC ; $HOME\pine\PINERC ; <exe dir>\PINERC
1058 except config $PINERCEX ; $HOME\pine\PINERCEX ; <exe dir>\PINERCEX
1059 global cfg $PINECONF
1061 debug <pinerc dir>\pinedebg.txtN
1062 crash <pinerc dir>\pinecrsh.txt
1063 signature# <pinerc dir>\pine.sig
1064 addressbook# <pinerc dir>\addrbook
1065 mailcap# <pinerc dir>\mailcap + <exe dir>\mailcap
1066 mimetypes# <pinerc dir>\mimetype + <exe dir>\mimetype
1067 newsrc# $HOME\newsrc (if exists, else) <pinerc dir>\newsrc
1068 sentmail# $HOME\mail\sentmail.mtx
1069 postponed# $HOME\mail\postpond.mtx
1070 interrupted $HOME\mail\intruptd
1072 Unix Alpine:
1074 executable <Unix search path>/pine
1075 persnl cfg ~/.pinerc
1076 except cfg ~/.pinercex
1077 global cfg <!--#echo var="PINE_CONF_PATH"-->
1078 fixed cfg <!--#echo var="PINE_CONF_FIXED_PATH"-->
1079 local help <!--#echo var="PINE_INFO_PATH"-->
1081 interrupted ~/.pine-interrupted-mail
1082 debug ~/.pine-debugN
1083 crash ~/.pine-crash
1084 newsrc# ~/.newsrc
1085 signature# <pinerc dir>/.signature
1086 addressbook# <pinerc dir>/.addressbook
1087 postponed# ~/mail/postponed-msgs
1088 sentmail# ~/mail/sent-mail
1089 mailcap# ~/.mailcap + /etc/mailcap
1090 + /usr/etc/mailcap + /usr/local/etc/mailcap
1091 mimetypes# ~/.mime.types + /etc/mime.types + /usr/local/lib/mime.types
1093 news-spool varies across Unix flavors, e.g. /var/spool/news or /usr/spool/news
1094 active-news varies across Unix flavors, e.g. /usr/lib/news/active
1095 lock files /tmp/.<!--#echo var="MAIL_SPOOL_LOCK_PATH"-->
1096 inbox <!--#echo var="MAIL_SPOOL_PATH"-->
1097 password /etc/passwd
1099 Unix Alpine and PC-Alpine:
1101 .ab* remote addressbook support files
1102 a[1-9]* temporary (while Alpine is running) addressbook files
1104 </PRE>
1105 <P>
1107 <H2>Mailcap files</H2>
1109 Alpine honors the mailcap configuration system for specifying external
1110 programs for handling attachments. The mailcap file maps MIME attachment
1111 types to the external programs loaded on your system that can display
1112 and/or print the file. A sample mailcap file comes bundled with the Alpine
1113 distribution. It includes comments that explain the syntax you need to
1114 use for mailcap. With the mailcap file, any program (mail readers,
1115 newsreaders, WWW clients) can use the same configuration for handling
1116 MIME-encoded data.
1117 <P>
1119 <H2>MIME-Types files</H2>
1121 Alpine uses mime-types files (.mime.types or MIMETYPE) to determine
1122 what Content-Type to use for labeling an attached file, based on
1123 the file extension. That is, this file provides a mapping between
1124 filename extensions and MIME content-types.
1125 <P>
1127 <H2>Environment variables</H2>
1129 PC-Alpine uses the following environment variables:
1130 <DL>
1131 <DT>PINERC</DT>
1132 <DD>Optional path to pinerc file.</DD>
1133 <DT>PINERCEX</DT>
1134 <DD>Optional path to personal exceptions configuration file.</DD>
1135 <DT>PINECONF</DT>
1136 <DD>Optional path to global pine config file.</DD>
1137 <DT>HOME</DT>
1138 <DT>TMPDIR, TMP, or TEMP</DT>
1139 <DT>COMSPEC</DT>
1140 <DT>MAILCAPS</DT>
1141 <DD>A <B>semicolon</B> delimited list of path names to mailcap files.</DD>
1142 <DT>USER_DICTIONARY</DT>
1143 <DD>Used to specify the file to contain the user's spell check
1144 dictionary. The default is <SAMP>DICT.U</SAMP> in the same
1145 directory as the <SAMP>SPELL32.DLL</SAMP></DD>
1146 </DL>
1148 Unix Alpine uses the following environment variables:
1149 <DL>
1150 <DT>TERM</DT>
1151 <DD>Tells Alpine what kind of terminal is being used.</DD>
1152 <DT>DISPLAY</DT>
1153 <DD>Determines if Alpine will try to display IMAGE attachments.</DD>
1154 <DT>SHELL</DT>
1155 <DD>If not set, default is "/bin/sh".</DD>
1156 <DT>TMPDIR, TMP, or TEMP</DT>
1157 <DT>MAILCAPS</DT>
1158 <DD>A <B>colon</B> delimited list of path names to mailcap files.</DD>
1159 </DL>
1160 <!--chtml if pinemode="os_windows"-->
1161 <P>
1162 <H2>Common PC-Alpine Configuration Problems</H2>
1164 <H3>Configuration settings aren't being saved</H3>
1166 <P>This problem can happen if you run pine from one directory and
1167 then decide to move your pine directory to another location. PC-Alpine
1168 stores certain variables, including the configuration location, in the
1169 Windows Registry (which you shouldn't ever need to manually edit). There
1170 are a couple of ways to go about removing or resetting the values in the
1171 registry.
1173 <P>
1174 1) Run PC-Alpine's registry value deletion command. This can be done by
1175 running: "<your pine directory>\pine.exe -registry clear" from the DOS
1176 prompt. You could create a shortcut to pine.exe and change the "Target"
1177 value to the above command.
1179 <P>
1180 2) Tell PC-Alpine where to look for the configuration file. Configuration
1181 information is stored in a file called the PINERC. With the "-p PINERC"
1182 option, you can tell PC-Alpine the location of your pinerc. An example of
1183 this would be to run: "<your pine directory>\pine.exe -p C:\pine\mypinerc".
1184 Again, you can use the DOS prompt or the shortcut method explained in (1).
1186 <P>
1187 Additionally, there is the "-registry set" option, which will actively
1188 set registry values to the current setting, and is therefore useful with
1189 the "-p PINERC" option.
1191 <!--chtml endif-->
1192 <P>
1193 <End of Configuration Notes>
1194 </BODY>
1195 </HTML>
1196 ====== h_news_legal ======
1197 <html>
1198 <head>
1199 <TITLE>Alpine Legal Notices</TITLE>
1200 </head>
1201 <body>
1203 <H1>Alpine Legal Notices</H1>
1205 Alpine and its constituent programs are covered by the Apache License Version 2.0.
1208 <P>
1209 <End of Alpine Legal Notices>
1210 </BODY>
1211 </HTML>
1212 ===== h_info_on_mbox =====
1213 <HTML>
1214 <HEAD>
1215 <TITLE>Information on mbox driver</TITLE>
1216 </HEAD>
1217 <BODY>
1218 <H1>Information on "Missing Mail" and the "mbox" driver</H1>
1220 Beginning with Pine 4.00 (Pine came before Alpine)
1221 a new INBOX access method is
1222 available as part of the standard configuration. It is called the
1223 "mbox" driver and it works like this:<P>
1225 <P>
1226 <BLOCKQUOTE>
1227 If the file "mbox" exists in the user's home directory, and
1228 is in Unix mailbox format, then when INBOX is opened this file will be
1229 selected as INBOX instead of the mail spool file. Messages will be
1230 automatically transferred from the mail spool file into the mbox
1231 file.
1232 </BLOCKQUOTE>
1234 <P>
1235 The advantage of this method is that, after new mail has been copied
1236 from the system mail spool, all subsequent access is confined to the
1237 user's home directory, which is desirable on some systems. However, a
1238 possible disadvantage is that mail tools other than those from the
1239 University of Washington will not know to look for mail in the user's
1240 mbox file. For example, POP or IMAP servers other than those from the
1241 University of Washington, and many "new mail notification"
1242 programs may not work as expected with this driver enabled.<P>
1244 To disable this behavior, either remove/rename the "mbox"
1245 file or find the <A HREF="h_config_disable_drivers"><!--#echo var="VAR_disable-these-drivers"--></A>
1246 option in Setup/Config
1247 and add "mbox" to it:
1248 <P>
1249 <CENTER><SAMP><!--#echo var="VAR_disable-these-drivers"-->=mbox</SAMP></CENTER>
1250 <P>
1251 <End of help on this topic>
1252 </BODY>
1253 </HTML>
1254 ===== h_info_on_locking =====
1255 <HTML>
1256 <HEAD>
1257 <TITLE>FAQs on Alpine Locking</TITLE>
1258 </HEAD>
1259 <BODY>
1260 <H1>What Systems Managers Need to Know about Alpine File Locking</H1>
1262 There is an extensive section on locking in the Alpine technical notes;
1263 this information is intended to provide answers to some common questions:<P>
1264 <OL>
1265 <LI> Why did locking change in Pine 4.00?<BR>
1266 The actual locking mechanisms did not change in 4.00.
1267 What changed is that when one particular locking mechanism used by Alpine
1268 fails, Alpine now issues a warning message. Prior to Pine 4.00, the locking
1269 failure would occur, but no warning was issued.<P>
1271 <LI> Is this what the "Mailbox vulnerable" message is about?<BR>
1272 Yes. It means that Alpine was unable to create a lockfile in the
1273 spool directory, generally because of overly restrictive protections on the
1274 spool directory. The correct permissions on the spool directory for
1275 running Alpine are 1777, i.e. read-write-execute permission for everyone,
1276 with the sticky-bit set, so only owners of a file can delete them.<P>
1278 <LI> Why does Alpine require that the mail spool directory have 1777
1279 protections?<BR>
1280 Alpine was designed to run without special privileges. This means that in
1281 order to create a lockfile in the spool directory, it is necessary to have
1282 the spool directory permissions be world-writable.<P>
1284 <LI> Can't you create the lockfile somewhere else?<BR>
1285 No. The lockfile in question must be in the mail spool directory, because
1286 that's where the mail delivery program expects to find it, and the purpose
1287 of the file is to coordinate access between the mail client (Alpine) and the
1288 mail delivery program.<P>
1290 <LI> Isn't having the spool directory world-writable a big security risk?<BR>
1291 No. Remember that the individual mail files in the spool directory are
1292 NOT world-writable, only the containing directory. Setting the "sticky
1293 bit" -- indicated by the "1" before the "777" mode
1294 -- means that only the owner of the file (or root) can delete files in the
1295 directory. So the only bad behavior that is invited by the 1777 mode is that
1296 anyone could
1297 create a random file in the spool directory. If the spool directory is
1298 under quota control along with home directories, there is little incentive
1299 for anyone to do this, and even without quotas a periodic scan for
1300 non-mail files usually takes care of the problem. <P>
1302 <LI> Why not run Alpine as setgid mail?<BR>
1303 Alpine was never designed to run with privileges, and to do so introduces a
1304 significant security vulnerability. For example, if a user suspends Alpine,
1305 the resulting shell will have group privileges. This is one example of
1306 why we strongly recommend against running Alpine as a privileged program.
1307 In addition, a "privileged mailer " paradigm would mean that normal
1308 users
1309 could not test Alpine versions or other mailers that had not been installed
1310 by the system administrators.<P>
1313 <LI> Are there any alternatives to creating .lock files in the spool dir?<BR>
1314 There are, but they all have different sets of tradeoffs, and not all will
1315 work on all systems. Some examples:<UL>
1316 <LI> Use lock system calls. Works fine on a few systems, provided mail
1317 spool is local. Doesn't work reliably if NFS is used.
1318 Doesn't work unless <B>all</B> the mail programs accessing the spool dir
1319 use the same calls.
1320 <LI> Deliver mail to user's home directory. An excellent solution, highly
1321 recommended -- but one which is incompatible with some "legacy"
1322 mail tools that always look in the spool directory for the mail.
1323 </UL><P>
1325 <LI> Are these spool directory lock files the only kinds of locks used by
1326 Alpine?<BR>
1327 No. Alpine also creates lockfiles in the /tmp directory. For normal Unix
1328 mailbox format folders, these are used to coordinate access between
1329 multiple Alpine sessions. <P>
1331 <LI> What about the
1332 <A HREF="h_config_quell_lock_failure_warnings">"<!--#echo var="FEAT_quell-lock-failure-warnings"-->"</A> feature added in Pine 4.01?<BR>
1333 This is for people who are content to live dangerously, or who have
1334 specific knowledge that the spool directory lockfiles are superfluous on
1335 their system (because both Alpine and the mail delivery program are using
1336 system call file locking in a context that works reliably, e.g. not NFS.)<P>
1338 <LI> Where can I find more details on how Alpine locking works?<BR>
1339 See the Alpine Technical Notes.<P>
1341 </OL>
1342 <P>
1343 <End of help on this topic>
1344 </BODY>
1345 </HTML>
1346 ===== h_finding_help ====
1347 <HTML>
1348 <HEAD>
1349 <TITLE>Finding more information and requesting help</TITLE>
1350 </HEAD>
1351 <BODY>
1352 <H1>Places to Look for More Answers</H1>
1353 If you have questions about or problems with Alpine that you cannot resolve
1354 after consulting the program's internal, context-sensitive help screens, here
1355 are additional information resources that you may find helpful:
1356 <P>
1357 <UL>
1358 <LI> Alpine's top-level <A HREF="main_menu_tx">MAIN MENU HELP</A>.<P>
1360 <LI> Alpine's <A HREF="h_help_index">Help Index</A>.<P>
1362 <LI> Alpine's internal <A HREF="h_news">Release Notes</A>. They contain a
1363 listing of changes in Alpine <!--#echo var="ALPINE_VERSION"-->
1364 since the last version, which may be useful for you to be aware of,
1365 <B>especially</B> if a "problem" you are encountering is actually
1366 a change in the way an aspect of Alpine works. There, you will also find notes
1367 on Alpine configuration.<P>
1369 <LI> The main site for Alpine contains information on configuring and solving problems
1370 with Alpine, it can be found at
1372 <CENTER><A HREF="http://patches.freeiz.com/alpine/">http://patches.freeiz.com/alpine/</A></CENTER>
1374 <LI> The Alpine Information Center (maintained by the University of
1375 Washington) World Wide Web site contains, among other things
1376 <UL>
1377 <LI>a collection of Frequently Asked Questions (and answers!) about Alpine
1378 <LI>an overview of the basics for beginning Alpine users
1379 <LI>Technical Notes for systems administrators
1380 <LI>archives (including a searchable index) of the alpine-info
1381 mailing list, on which matters of interest to systems/email administrators,
1382 developers, trainers, user support personnel, and others involved with Alpine
1383 messaging on a "technical" level are discussed.
1384 </UL>
1385 The Alpine Information Center can be accessed with a WWW browser at:<P>
1386 <CENTER><A HREF="http://www.washington.edu/alpine/">http://www.washington.edu/alpine/</A></CENTER>
1387 </UL>
1388 <P><HR WIDTH="75%">
1389 <H1>Requesting help</H1>
1390 If the internal help, the Release Notes, the Alpine Information Center, and your
1391 local online and print resources do not help you resolve a problem, please
1392 start by contacting your local computer support staff and asking for help.
1393 <p>
1394 This is especially true if:
1395 <ul>
1396 <li>You suddenly have trouble sending or receiving mail.
1397 <li>You receive a "disk quota exceeded" message.
1398 <li>You have forgotten your password.
1399 <li>You think your account may have been compromised.
1400 <li>You need help viewing an attachment.
1401 <li>You need to know how to configure your:
1402 <A HREF="h_config_nntp_server">NNTP (news) server</A>,
1403 <A HREF="h_config_smtp_server">SMTP (sending mail) server</A>,
1404 <A HREF="h_config_ldap_server">LDAP (directory lookup) server</A>, or
1405 <A HREF="h_config_inbox_path">INBOX (incoming mail) path</A>.
1406 <li>You want to know what alternative editors or spellcheckers you may be able to use.
1407 <li>You want to block email from a particular person.
1408 <li>You're going on vacation and need to autorespond to incoming mail.
1409 <li>You want to automatically file or filter incoming messages.
1410 </ul>
1412 In all of these cases,
1413 you should contact <B>your</B> support staff, because <B>only they</B>
1414 will be able to assist you effectively. Your support staff may be, depending on who
1415 provides you with the email account you use Alpine with, for example:<UL>
1416 <LI> the computing help desk of (a department of) your university, school,
1417 employer, ... ; or
1418 <LI> the customer service center of your Internet Service Provider; or
1419 <LI> the friendly volunteer helpers of your Freenet; or
1420 <LI> the person who setup your computer and internet connection.
1421 </UL>
1423 Due to the large number of Alpine installations worldwide, and because we
1424 receive no funding for it, the Alpine development team <B>cannot provide
1425 individual support services outside the University of Washington</B>.
1426 <P>
1427 If you have no local computing support to turn to, the worldwide <b>comp.mail.pine</b>
1428 newsgroup can be a valuable source of information and assistance for Alpine
1429 user issues.
1430 <P>
1431 For systems/email administrators, developers, trainers, user support
1432 personnel, and others involved with Alpine messaging on a "technical"
1433 level, the mailing list alpine-info is available; for information on
1434 subscribing and posting to it, see
1435 <P>
1436 <CENTER><A HREF="http://www.washington.edu/alpine/alpine-info/subscribing.html">http://www.washington.edu/alpine/alpine-info/subscribing.html</A></CENTER>
1437 <P>
1439 Regardless of whom you are asking for help with Alpine, remember
1440 to provide as much detail as you can about the
1441 nature of any problem you are encountering, such as
1442 <UL>
1443 <LI>when it first occurred;
1444 <LI>what, if anything, happened that might have brought it about;
1445 <LI>whether it still persists;
1446 <LI>whether it is reproducible, and if so, how;
1447 <LI>what, if anything, you already tried to solve it.
1448 </UL>
1449 It may also be helpful if you specify what version of Alpine you are using
1450 <!--chtml if pinemode="running"-->
1451 -- this is <!--#echo var="ALPINE_VERSION"--> --
1452 <!--chtml endif-->
1453 and on what system, and when the copy of Alpine you are using was created
1454 <!--chtml if pinemode="running"-->
1455 -- for this copy: <!--#echo var=ALPINE_COMPILE_DATE-->
1456 <!--chtml endif-->
1458 <!--chtml if pinemode="running"-->
1459 <P>
1460 When the Alpine program you are currently using was installed, a support
1461 contact email address may have been set up; in that case, you can simply select
1462 this link now to send a message to it:<BR>
1463 <A HREF="X-Alpine-Gripe:_LOCAL_ADDRESS_?local"><!--#echo var="_LOCAL_FULLNAME_"--></A><P>
1464 <!--chtml endif-->
1465 <!--chtml if [ -r PINE_INFO_PATH ]-->
1466 <HR WIDTH="75%">Local Support Contacts:<P>
1467 <!--#include file="PINE_INFO_PATH"-->
1468 <HR WIDTH="75%">
1469 <!--chtml endif-->
1470 <P>
1471 <End of help on this topic>
1472 </BODY>
1473 </HTML>
1474 ===== new_user_greeting ======
1475 <HTML>
1476 <HEAD>
1477 <TITLE>NEW USER GREETING</TITLE>
1478 </HEAD>
1479 <BODY>
1480 <CENTER><<<This message will appear only once>>></CENTER>
1481 <BR>
1482 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
1483 We hope you will explore Alpine's many capabilities. From the MAIN MENU,
1484 select Setup/Config to see many of the options available to you. Also note
1485 that all screens have context-sensitive help text available.<P>
1486 <!--chtml if pinemode="phone_home"-->
1487 SPECIAL REQUEST:
1488 This software is made available as a public service of the
1489 University of Washington in Seattle. We are no longer actively developing
1490 the software, but it is still helpful to us to have an idea of how many
1491 people are using Alpine. Are you willing to be counted as an Alpine user? Pressing
1492 <A HREF="X-Alpine-Phone-Home:">Return</A>
1493 will send an anonymous (meaning, your real email address will not be revealed)
1494 message to the Alpine team at the University of Washington for purposes of tallying.
1495 <P>
1496 <!--To Exit this screen and continue your Alpine session press "E".-->
1497 <!--chtml else-->
1498 To Exit this screen and continue your Alpine session press "Return".
1499 <!--chtml endif-->
1500 </BODY>
1501 </HTML>
1502 ===== new_alpine_user_greeting ======
1503 <HTML>
1504 <HEAD>
1505 <TITLE>NEW ALPINE USER GREETING</TITLE>
1506 </HEAD>
1507 <BODY>
1508 <CENTER><<<This message will appear only once>>></CENTER>
1509 <BR>
1510 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
1511 Your Alpine configuration file indicates that you may have used Pine before
1512 but not Alpine.
1513 If you are familiar with the way Pine works, you should be comfortable
1514 using Alpine.
1515 Your Pine configuration file is automatically used for Alpine.
1516 The Release Notes may be viewed by pressing
1517 "R" now or while in the MAIN MENU.
1518 <P>
1519 <!--chtml if pinemode="phone_home"-->
1520 SPECIAL REQUEST:
1521 This software is made available as a public service of the
1522 University of Washington in Seattle. We are no longer actively developing
1523 the software, but it is still helpful to us to have an idea of how many
1524 people are using Alpine. Are you willing to be counted as an Alpine user? Pressing
1525 <A HREF="X-Alpine-Phone-Home:">Return</A>
1526 will send an anonymous (meaning, your real email address will not be revealed)
1527 message to the Alpine team at the University of Washington for purposes of tallying.
1528 <P>
1529 <!--To Exit this screen and continue your Alpine session press "E".-->
1530 <!--chtml else-->
1531 To Exit this screen and continue your Alpine session press "Return".
1532 <!--chtml endif-->
1533 </BODY>
1534 </HTML>
1535 ===== new_version_greeting ======
1536 <HTML>
1537 <HEAD>
1538 <TITLE>NEW VERSION GREETING</TITLE>
1539 </HEAD>
1540 <BODY>
1541 <CENTER><<<This message will appear only once>>></CENTER>
1542 <BR>
1543 <H1>Welcome to Alpine version <!--#echo var="ALPINE_VERSION"-->!</H1>
1544 Your Alpine configuration file indicates that you may not have used
1545 this version of Alpine before. This version's significant changes are
1546 documented in the Release Notes, which may be viewed by pressing
1547 "R" now or while in the MAIN MENU.
1548 <P>
1549 <!--chtml if pinemode="phone_home"-->
1550 SPECIAL REQUEST:
1551 This software is made available as a public service of the
1552 University of Washington in Seattle. We are no longer actively developing
1553 the software, but it is still helpful to us to have an idea of how many
1554 people are using Alpine. Are you willing to be counted as an Alpine user? Pressing
1555 <A HREF="X-Alpine-Phone-Home:">Return</A>
1556 will send an anonymous (meaning, your real email address will not be revealed)
1557 message to the Alpine team at the University of Washington for purposes of tallying.
1559 <!--To Exit this screen and continue your Alpine session press "E".-->
1560 <!--chtml else-->
1561 To Exit this screen and continue your Alpine session press "Return".
1562 <!--chtml endif-->
1563 </BODY>
1564 </HTML>
1566 ===== main_menu_tx ======
1567 <HTML>
1568 <HEAD>
1569 <TITLE>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</TITLE>
1570 </HEAD>
1571 <BODY>
1572 <H1>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</H1>
1573 <DIV ALIGN=CENTER>
1574 Version <!--#echo var="ALPINE_VERSION"-->
1575 <!--chtml if pinemode="running"-->
1576 <BR>(built <!--#echo var=ALPINE_COMPILE_DATE-->)
1577 <!--chtml endif-->
1578 </DIV>
1579 <CENTER>Copyright 2013-2014 Eduardo Chappa,
1580 <BR>Copyright 2006-2008 University of Washington.
1581 </CENTER>
1583 <P>
1584 When you are viewing a help screen, there may be links to
1585 other topics highlighted (in Reverse video) in the text.
1586 Here is an example.
1587 The word "Introduction" in the TABLE OF CONTENTS below should be
1588 highlighted.
1589 If you type carriage return (or V for View Link, see the commands at the
1590 bottom of the screen) you will be taken to a new help screen to view the
1591 Introduction.
1592 The commands at the bottom of the screen should then include
1593 "P Prev Help".
1594 If you type "P" you will end up back here.
1595 If you type "E" for Exit, you will be back out of help and returned
1596 to the place you were in Alpine when you entered Help.
1597 In this case, you would go back to the MAIN MENU.
1598 There are also other links that are highlighted in bold (or the color used
1599 by your terminal to display bold).
1600 The items after the Introduction in the TABLE OF CONTENTS are all examples
1601 of such links.
1602 In order to view those links, you first have to make the link you want
1603 to view the current link.
1604 The "NextLink" and "PrevLink" commands
1605 (see bottom of screen) can do that for you.
1606 <P>
1608 <H2>TABLE OF CONTENTS</H2>
1609 <OL>
1610 <LI> <A HREF="h_mainhelp_intro">Introduction</A>
1611 <LI> <A HREF="h_mainhelp_pinehelp">Alpine Help</A>
1612 <!--chtml if [ -r PINE_INFO_PATH ]-->
1613 <LI> <A HREF="h_mainhelp_localsupport">Local Support Contacts</A>
1614 <!--chtml endif-->
1615 <LI> <A HREF="h_mainhelp_cmds">Giving Commands in Alpine</A>
1616 <LI> <A HREF="h_mainhelp_config">Alpine Configuration</A>
1617 <LI> <A HREF="h_mainhelp_status">Titlebar Line</A>
1618 <LI> <A HREF="h_mainhelp_mainmenu">Main Menu</A>
1619 <LI> <A HREF="h_mainhelp_index">Index of Messages</A>
1620 <LI> <A HREF="h_mainhelp_reading">Reading Messages</A>
1621 <LI> <A HREF="h_mainhelp_composing">Composing Messages</A>
1622 <LI> <A HREF="h_mainhelp_readingnews">Reading News</A>
1623 <LI> <A HREF="h_mainhelp_abooks">Address Books</A>
1624 <LI> <A HREF="h_mainhelp_ldap">LDAP Directories</A>
1625 <LI> <A HREF="h_mainhelp_folders">Folders</A>
1626 <LI> <A HREF="h_mainhelp_collections">Collection Lists</A>
1627 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
1628 <LI> <A HREF="h_mainhelp_color">Color Setup</A>
1629 <LI> <A HREF="h_mainhelp_filtering">Filtering</A>
1630 <LI> <A HREF="h_mainhelp_roles">Roles</A>
1631 <LI> <A HREF="h_mainhelp_patterns">Patterns</A>
1632 <LI> <A HREF="h_mainhelp_keywords">Keywords (or Flags, or Labels)</A>
1633 <LI> <A HREF="h_mainhelp_mouse">Using a Mouse</A>
1634 <LI> <A HREF="h_mainhelp_cmdlineopts">Command Line Options</A>
1635 <LI> <A HREF="h_mainhelp_securing">Securing Your Alpine Session</A>
1636 <LI> <A HREF="h_mainhelp_smime">S/MIME</A>
1637 <LI> <A HREF="h_mainhelp_problems">Reporting Problems</A>
1638 <LI> <A HREF="X-Alpine-Config:">Show Supported Options in this Alpine</A>
1639 <LI> <A HREF="h_help_index">Index to Alpine's Online Help</A>
1640 </OL>
1642 <P>
1643 <End of help on this topic>
1644 </BODY>
1645 </HTML>
1646 ===== h_mainhelp_intro ======
1647 <HTML>
1648 <HEAD>
1649 <TITLE>Introduction</TITLE>
1650 </HEAD>
1651 <BODY>
1652 <H1>Introduction</H1>
1654 Alpine is an "Alternatively Licensed Program for Internet
1655 News and Email" produced until 2008 by the University of Washington.
1656 It is intended to be an easy-to-use program for
1657 sending, receiving, and filing Internet electronic mail messages and
1658 bulletin board (Netnews/Usenet) messages. Alpine supports the following
1659 Internet protocols and specifications: SMTP (Simple Mail Transport Protocol),
1660 NNTP (Network News Transport Protocol), MIME (Multipurpose Internet Mail
1661 Extensions), IMAP (Internet Message Access Protocol), and LDAP (Lightweight
1662 Directory Access Protocol).<p>
1664 Although originally designed for inexperienced email users, Alpine has
1665 evolved to support many advanced features. There are an ever-growing
1666 number of configuration and personal-preference options, though which of
1667 them are available to you is determined by your local system managers.
1669 <H2>WHAT ALPINE DOES...</H2>
1671 Alpine is a "mail user agent" (MUA), which is a program that
1672 allows you to
1673 compose and read messages using Internet mail standards. (Whether you
1674 can correspond with others on the Internet depends on whether or not your
1675 computer is connected to the Internet.) Alpine also allows reading and
1676 posting messages on the Internet "net news" system, provided
1677 that your site operates a suitable news server.
1679 <H2>WHAT ALPINE DOES NOT DO...</H2>
1681 A "mail user agent" such as Alpine is just one part of a
1682 messaging system. Here are some things that are <B>not</B> done by Alpine,
1683 but require other programs:<P>
1684 <UL>
1685 <LI> Actual relaying of email... which is done by "message transfer
1686 agents".
1687 <LI> Vacation messages... automatically responding to incoming messages
1688 <LI> Anything to do with "talk"... which has nothing to do with
1689 email.
1690 <LI> Anything to do with "irc"... which has nothing to do with email.
1691 <LI> List processing... resending one message to a list of recipients.
1692 </UL>
1694 <P>
1695 <End of help on this topic>
1696 </BODY>
1697 </HTML>
1699 ===== h_mainhelp_pinehelp ======
1700 <HTML>
1701 <HEAD>
1702 <TITLE>Alpine Help</TITLE>
1703 </HEAD>
1704 <BODY>
1705 <H1>Alpine Help</H1>
1707 Alpine help is generally context-sensitive. In other words, each Alpine screen you
1708 use will have its own help text, explaining the choices available for that
1709 screen. This general help section, on the other hand, attempts to give an
1710 overall picture of what Alpine is capable of doing, as well as pointers to
1711 additional help sections about specific topics.<p>
1713 Much of the help text contains links to further help topics, similar to
1714 how the World Wide Web works.
1715 You may choose a link to view using the "NextLink" and
1716 "PrevLink" commands to change the link that is highlighted.
1717 The "View Link" command will then show you the highlighted link.
1718 Similar to the Back button in a web browser, the "Prev Help" command
1719 will return you to where you were before viewing the link, and "Exit Help"
1720 will return you to the location in Alpine before you asked for help.
1721 For example, if you are reading this text in Alpine you may return to the
1722 help table of contents with the "Prev Help" command or you may view the
1723 Release notes link in the next paragraph and then return here with
1724 "Prev Help".
1725 <P>
1727 In addition to this general help on Alpine, <A HREF="h_news">Release Notes</A>
1728 on the current Alpine version are also available from the MAIN MENU: Press
1729 <!--chtml if pinemode="function_key"-->
1730 "F9"
1731 <!--chtml else-->
1732 "R"
1733 <!--chtml endif-->
1734 to browse the release notes. These include changes since the last release,
1735 configuration information, the history of the Alpine
1736 project, credits, and legal notices.
1738 Alpine releases are available via the world wide web at
1739 <P>
1740 <CENTER><SAMP><A
1741 HREF="http://patches.freeiz.com/alpine/release/">http://patches.freeiz.com/alpine/release/</A></SAMP
1742 ></CENTER>
1743 <P>
1745 If you would like to print <EM>all</EM> of Alpine's internal help text
1746 (not recommended) for a little light bedtime reading, then press
1747 <!--chtml if pinemode="function_key"-->
1748 "F12"
1749 <!--chtml else-->
1750 "Z"
1751 <!--chtml endif-->
1752 now. (This assumes that the
1753 copy of Alpine you are using has been properly configured for printing
1754 at your site.)
1755 <P>
1756 <End of help on this topic>
1757 </BODY>
1758 </HTML>
1759 ===== h_mainhelp_localsupport ======
1760 <HTML>
1761 <HEAD>
1762 <TITLE>Local Support Contacts</TITLE>
1763 </HEAD>
1764 <BODY>
1765 <H1>Local Support Contacts</H1>
1767 <!--chtml if [ -r PINE_INFO_PATH ]-->
1768 <!--#include file="PINE_INFO_PATH"-->
1769 <!--chtml else-->
1770 No Local Support Contacts configured.
1771 <!--chtml endif-->
1773 <P>
1774 <End of help on this topic>
1775 </BODY>
1776 </HTML>
1778 ===== h_mainhelp_cmds ======
1779 <HTML>
1780 <HEAD>
1781 <TITLE>Giving Commands in Alpine</TITLE>
1782 </HEAD>
1783 <BODY>
1784 <H1>Giving Commands in Alpine</H1>
1786 Unless configured otherwise
1787 (<A HREF="h_config_blank_keymenu"><!--#echo var="FEAT_disable-keymenu"--></A>)
1788 the bottom two lines of the screen are always used to list the
1789 commands you can give. You press the keys that are highlighted to give
1790 the command. The commands for getting help and going back to the main
1791 menu are always present (except when viewing help as you are now).
1792 <!--chtml if pinemode="function_key"-->
1793 <!--chtml else-->
1794 <p>
1795 Pressing O (meaning "Other Commands") changes the keys
1796 you see at the bottom of any screen. In some cases there are 3 or
1797 even 4 different
1798 sets of keys that can be seen by using the O key. <EM>All commands are
1799 active</EM>, even if they are not currently showing at the bottom of your
1800 screen. In other words, you <EM>never</EM> need to press the O key, except to
1801 remind yourself of the proper key to press to perform an operation.
1803 <H2>Control Key Commands</H2>
1804 When composing mail, and in a few other places, in Alpine you
1805 have to use Control keys. This means pressing the Control key (usually labeled
1806 "Ctrl") and the
1807 letter indicated at the same time. Usually, this is shown with a
1808 "^" in front of the letter. On some systems, certain control
1809 characters are intercepted before they get to Alpine. As a work-around,
1810 you can press the ESCAPE key twice followed by the desired key. For
1811 example, if Ctrl-O (^O) does not work on your system, try typing
1812 "ESC ESC O".
1813 <!--chtml endif-->
1814 <H2>Paging Up and Down</H2>
1815 The "+" and "-" keys are used for
1816 moving to the next or previous page. The space bar is a synonym for
1817 "+". You may also use Ctrl-V to page down and Ctrl-Y to page
1818 up as you do in the message composer. On screens with a WhereIs (search)
1819 command, W or Ctrl-W followed by Ctrl-V will move to the bottom of the
1820 message or list, and W or Ctrl-W followed by Ctrl-Y will move to the top
1821 of the message or list.
1823 <H2>Return Key</H2>
1824 The return key is usually a synonym for a frequently used
1825 command. When viewing a message, there is currently not a default
1826 command, so RETURN does nothing; when in the index, it is synonymous with
1827 "view msg". In the key menu at the bottom of the screen, whatever is
1828 enclosed in square brackets [] is the same as the return key.
1830 <H2>Control Keys Not Used By Alpine</H2>
1831 Most commands in Alpine are single letters, with -- we hope -- some mnemonic
1832 value, but in places where Alpine is expecting text input, e.g. in the composer or
1833 at prompts for file/folder names, control keys must be used for editing and
1834 navigation functions.
1835 <P>
1837 Alpine has used nearly all the control keys available. There are, however,
1838 certain control keys that are reserved by other programs or for technical
1839 reasons. Alpine does not use any of these keys:
1840 <DL>
1841 <DT>Ctrl-S</DT> <DD>Used by Unix as "stop output"</DD>
1842 <DT>Ctrl-Q</DT> <DD>Used by Unix as "resume output"</DD>
1843 <DT>Ctrl-]</DT> <DD>Often used by Telnet as escape key</DD>
1844 </DL>
1845 <P>
1846 Note: Ctrl-S and Ctrl-Q can be subject to
1847 <A HREF="h_special_xon_xoff">special handling</A>.
1848 <P>
1849 In addition, while the ESC key alone is not used for command input,
1850 Alpine will recognize two consecutive ESC key presses followed by a letter
1851 key as a substitute for control key input. For example, the control key
1852 <SAMP>Ctrl-X</SAMP> can alternatively be entered using the
1853 three keystrokes: <SAMP>ESC ESC x</SAMP>.
1854 This is useful if the communication program you are using
1855 (e.g. Telnet) has its own, conflicting, idea of what certain control
1856 characters mean.
1859 <H2>Repainting the Screen</H2>
1860 Sometimes what is displayed on the screen will be
1861 incorrect due to noise on the phone line or other causes and you will want
1862 to repaint the whole screen to make it correct. You can use the Ctrl-L
1863 command to do this. It never hurts to do it when in doubt.
1865 <P>
1866 <End of help on this topic>
1867 </BODY>
1868 </HTML>
1869 ===== h_mainhelp_status ======
1870 <HTML>
1871 <HEAD>
1872 <TITLE>Titlebar Line</TITLE>
1873 </HEAD>
1874 <BODY>
1875 <H1>Titlebar Line</H1>
1877 The top line of the screen is Alpine's titlebar line. It will always display
1878 the current version of Alpine and will also convey information about the
1879 status of the program. This is where you look to find out what
1880 collection, folder and message number is active and where you are in Alpine.
1881 <P>
1883 If the titlebar line says "READONLY" it means that the open folder
1884 (typically your INBOX) is "locked" by another mail session --
1885 most likely a more recent session of Alpine has taken the INBOX lock.
1886 <P>
1888 If the titlebar line says "CLOSED" it means that you are trying to
1889 access a
1890 folder on a remote mail server, and for some reason, communication with
1891 the mail server has either been lost, or never successfully established.
1892 This can be a result of trying to open a non-existent folder, or one
1893 stored on an invalid or non-operational server, or it can mean that Alpine
1894 has been suspended for more that 30 minutes while accessing a remote mail
1895 server.
1897 <P>
1898 <End of help on this topic>
1899 </BODY>
1900 </HTML>
1901 ===== h_mainhelp_mainmenu ======
1902 <HTML>
1903 <HEAD>
1904 <TITLE>Main Menu</TITLE>
1905 </HEAD>
1906 <BODY>
1907 <H1>Main Menu</H1>
1909 The Main Menu lists Alpine's main options.
1910 The key or keys you must type to enter your
1911 choice are to the left of each option or command name.
1912 You can type either uppercase or lowercase letters,
1913 and you should not press <Return> after typing the
1914 letter (unless you are specifically asking for the default,
1915 highlighted command).
1916 <P>
1918 From the Main Menu you can choose to read online help, write (compose) and
1919 send a message, look at an index of your mail messages, open or maintain
1920 your mail folders, update your address book, configure Alpine, and quit Alpine.
1921 There are additional options listed at
1922 the bottom of the screen as well.
1924 <P>
1925 The Help command usually returns context-sensitive help information.
1926 However, in the Main Menu you get the most general help, which includes
1927 a Table of Contents.
1928 The last entry in the Table of Contents is an Index of help topics,
1929 so this is a good place to go if you are having trouble finding how
1930 to do something.
1932 <H2>Main Menu Commands</H2>
1933 The Alpine main menu lists the most common Alpine functions. A <a
1934 href="h_main_menu_commands">full list of these
1935 commands</a> and what they do is available.
1936 <P>
1937 <End of help on this topic>
1938 </BODY>
1939 </HTML>
1940 ===== h_mainhelp_abooks ======
1941 <HTML>
1942 <HEAD>
1943 <TITLE>Address Books</TITLE>
1944 </HEAD>
1945 <BODY>
1946 <H1>Address Books</H1>
1949 As you use email, you can build a list of your regular email correspondents
1950 in your Alpine
1951 Address Book. At the Alpine MAIN MENU, press A to see the Address Book List
1952 screen. Your
1953 personal address book will be highlighted. Press <Return> to view it.
1954 You can use the address book to store email addresses for individuals or
1955 groups, to create easily
1956 remembered "nicknames" for these addresses, and to quickly retrieve an email
1957 address when you are composing a message.
1958 <P>
1959 There are two ways to add addresses to your address book: you can add them
1960 manually or take them from messages (by pressing T to access the Take command).
1961 With either method, you specify nicknames for your correspondents. A single
1962 address book entry (or nickname) can point to just one email address, or, it can
1963 point to more than one. When it points to more than one, it is called a
1964 distribution list. Each distribution list has a nickname, a full name, and a
1965 list of addresses. These
1966 addresses may be actual addresses, other nicknames in your address book, or
1967 other
1968 distribution lists.
1970 <P>
1971 Additional information is available in Alpine's online help:
1972 <ul>
1973 <li><a href="h_abook_opened">The Alpine Address Book</a></li>
1974 </ul>
1975 <P>
1976 <End of help on this topic>
1977 </BODY>
1978 </HTML>
1979 ===== h_mainhelp_ldap ======
1980 <HTML>
1981 <HEAD>
1982 <TITLE>LDAP</TITLE>
1983 </HEAD>
1984 <BODY>
1985 <H1>LDAP</H1>
1987 LDAP (Lightweight Directory Access Protocol) is a standard means of accessing
1988 an organization's shared
1989 directories. Essentially, using LDAP, Alpine is able to find email addresses in
1990 large address
1991 books, rather like the White Pages provided by the phone company. As an Alpine
1992 user, it is not
1993 necessary to know much about how this works, only how to use it and how to
1994 configure
1995 it.
1996 <P>
1997 More information on configuring LDAP is available in Alpine's online help:
1998 <ul>
1999 <li><a href="h_direct_config">Setup LDAP Directory Servers</a></li>
2000 </ul>
2001 <P>
2002 Additional help on using LDAP in Alpine is also available:
2003 <ul>
2004 <li><a href="h_ldap_view">LDAP Response View Explained</a></li>
2005 </ul>
2006 <P>
2007 <End of help on this topic>
2008 </BODY>
2009 </HTML>
2010 ===== h_mainhelp_index ======
2011 <HTML>
2012 <HEAD>
2013 <TITLE>Index of Messages</TITLE>
2014 </HEAD>
2015 <BODY>
2016 <H1>Index of Messages</H1>
2018 In Alpine's message index, the selected message is highlighted. The first
2019 column on the left is blank, shows a "+" if the message was
2020 sent directly to you (i.e., it is not a
2021 copy or from a list), or a "-" if you were explicitly Cc'd.
2022 <P>
2023 The second column may be blank, or it may contain:
2024 <ul>
2025 <li>"N" if the message is new (unread), </li>
2026 <li>"A" if you have answered the message (using the Reply command), </li>
2027 <li>"D" if you have marked the message for deletion.</li>
2028 </ul>
2030 <P>
2031 Note: If you answer a message as well as mark it deleted (in either order),
2032 you will only see the "D".
2034 <P>
2035 The rest of the columns in the message line show you the message
2036 number, date sent, sender, size, and subject. For details, press ? (Help).
2037 The behavior and appearance of the Index screen is highly configurable.
2038 In the Setup/Config screen search (with the WhereIs command) for options
2039 that contain the words "index" or "thread" to see
2040 many of the configuration possibilities.
2041 In particular, the
2042 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
2043 option may be used to configure the look of the standard MESSAGE INDEX lines
2044 in many different ways.
2045 Find <!--#echo var="VAR_index-format"--> in the Setup/Config screen and
2046 read the help text there for more information.
2047 <P>
2048 Most of the commands you need to handle your messages are visible at the
2049 bottom of the screen, and you can press O (OTHER CMDS) to see additional
2050 commands that are available.
2051 You do not need to see these "other commands"
2052 on the screen to use them. That is, you never need to press O as a prefix
2053 for any other command.
2055 <P>
2056 Additional information is available in Alpine's online help:
2057 <ul>
2058 <li><a href="h_mail_index">Message Index Commands</a></li>
2059 </ul>
2060 <P>
2061 <End of help on this topic>
2062 </BODY>
2063 </HTML>
2064 ===== h_mainhelp_reading ======
2065 <HTML>
2066 <HEAD>
2067 <TITLE>Reading Messages</TITLE>
2068 </HEAD>
2069 <BODY>
2070 <H1>Reading Messages</H1>
2072 The message text screen shows you the text of the message along with
2073 its header. If a message has attachments, those will be listed (but not
2074 displayed) also. The titlebar line displays information about the currently
2075 open message, folder and collection. You see the name of the collection
2076 (if there is one) in angle brackets, then the name of the folder, then the
2077 message number and finally the position within the current message (in
2078 percent). If the message is marked for deletion
2079 "DEL" will appear in the
2080 upper right as well.
2082 <P>
2083 As with every Alpine screen, the bottom two lines show you the commands
2084 available.
2086 <P>Additional information is available in Alpine's online help:
2087 <ul>
2088 <li><a href="h_mail_view">Message Text Screen</a></li>
2089 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a></li>
2090 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a></li>
2091 </ul>
2092 <P>
2093 <End of help on this topic>
2094 </BODY>
2095 </HTML>
2096 ===== h_mainhelp_composing ======
2097 <HTML>
2098 <HEAD>
2099 <TITLE>Composing Messages</TITLE>
2100 </HEAD>
2101 <BODY>
2102 <H1>Composing Messages</H1>
2104 To write a message, press C (Compose). You see the Compose Message
2105 screen, which is divided into two parts: the header area and the message
2106 text area. The header area is where information on the recipient (the To:
2107 field) and the subject line go, while the message text area contains the
2108 actual text of the email message. Different commands are available to you
2109 when your cursor is in different areas on this screen. To see additional
2110 help on commands in either the message text or header area, type
2111 <Control>G (Get help).
2113 <P>
2114 To move around, use the arrow keys or Ctrl-N (Next line) and Ctrl-P
2115 (Previous line); to correct typing errors, use <Backspace> or <Delete>.
2117 <P>The following information from Alpine's online help may prove useful:
2118 <ul>
2119 <li><a href="h_composer_to">Message Header Commands</a></li>
2120 <li><a href="h_compose_richhdr">Rich Header Command</a></li>
2121 <li><a href="h_composer">Composer Commands</a></li>
2122 <li><a href="h_edit_nav_cmds">Composer Editing Commands</a></li>
2123 <li><a href="h_config_change_your_from">Changing your From Address</a></li>
2124 <li><a href="h_compose_send">Send Command</a></li>
2125 <li><a href="h_compose_spell">Spell Check Command</a></li>
2126 </ul>
2127 <P>
2128 <End of help on this topic>
2129 </BODY>
2130 </HTML>
2131 ===== h_mainhelp_collections ======
2132 <HTML>
2133 <HEAD>
2134 <TITLE>Collection Lists</TITLE>
2135 </HEAD>
2136 <BODY>
2137 <H1>Collection Lists</H1>
2139 Collection lists are Alpine's way of organizing groups of folders. Each
2140 "collection" can reside on a different server, for example, and contain a
2141 different group of mail folders.
2143 <P>
2144 For more information on this, see:
2145 <ul>
2146 <li><a href="h_what_are_collections">Folder Collections Explained</a></li>
2147 </ul>
2148 <P>
2149 Additional information relating to collection lists is also available in
2150 Alpine's online
2151 help:
2152 <ul>
2153 <li><a href="h_collection_maint">Setup Collection List Screen</a></li>
2154 <li><a href="h_collection_screen">Collection List Screen</a></li>
2155 </ul>
2156 <P>
2157 <End of help on this topic>
2158 </BODY>
2159 </HTML>
2160 ===== h_mainhelp_folders ======
2161 <HTML>
2162 <HEAD>
2163 <TITLE>Folders</TITLE>
2164 </HEAD>
2165 <BODY>
2166 <H1>Folders</H1>
2168 Messages can quickly accumulate in your INBOX folder. If you use email
2169 often, you soon could have hundreds. You need to delete messages you do
2170 not want, and you can use folders to organize messages you wish to save. A
2171 folder is a collection of one or more messages that are stored (just like
2172 the messages in your INBOX) so you can access and manage them.
2174 <P>
2175 You can organize your email messages into different folders by topic,
2176 correspondent, date, or any other category that is meaningful to you. You
2177 can create your own folders, and Alpine automatically provides three:
2178 <ul>
2179 <li>The INBOX folder: messages sent to you are listed in this folder.
2180 When you first start Alpine and go to the Message Index screen, you are
2181 looking at the list of messages in your INBOX folder. Every incoming
2182 message remains in your INBOX until you delete it or save it in another
2183 folder. </li>
2184 <li>The sent-mail folder: copies of messages you send are stored in this
2185 folder. This is
2186 convenient if you cannot remember whether you actually sent a message and want
2187 to check, or
2188 if you want to send a message again.</li>
2189 <li>The saved-messages folder: copies of messages you save are stored in this
2190 folder
2191 unless you choose to save them to other folders you create yourself.</li>
2192 </ul>
2194 <P>
2195 More information about folders is available in Alpine's online help:
2196 <ul>
2197 <li><a href="h_folder_open">Explanation of Folder Selection</a></li>
2198 <li><a href="h_folder_maint">Help for Folder List</a></li>
2199 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a></li>
2200 <li><a href="h_folder_fcc">Folder Select for Fcc ("sent-mail")
2201 Explained</a></li>
2202 <li><a href="h_folder_save">Folder Select for Save Explained</a></li>
2203 </ul>
2204 <P>
2205 <End of help on this topic>
2206 </BODY>
2207 </HTML>
2208 ===== h_mainhelp_color ======
2209 <HTML>
2210 <HEAD>
2211 <TITLE>Color</TITLE>
2212 </HEAD>
2213 <BODY>
2214 <H1>Color</H1>
2216 If the terminal emulator you are using is capable of displaying color or if
2217 you are using PC-Alpine, then it is possible to set up Alpine so that various
2218 parts of the display will be shown in colors you configure. This is done
2219 using the Setup Color screen, available from the MAIN MENU by selecting
2220 the Setup command followed by "K" for Kolor (because "C"
2221 stands for Config in this context).
2223 <P>
2224 For example, you may color things like the titlebar, the current item,
2225 the keymenu, and the status messages.
2226 You may also color lines in the index, and headers and quoted text in the
2227 MESSAGE TEXT screen.
2228 You use the Color Setup screen for configuring most of this, but you must
2229 use the IndexColor setup for coloring whole index lines.
2230 These are available from the MAIN MENU under Setup/Kolor and Setup/Rules/IndexColor.
2232 <P>
2233 The following entries in Alpine's online help provide additional information
2234 about how to use color:
2235 <UL>
2236 <LI> <A HREF="h_color_setup">Color Setup screen</A>
2237 <LI> <A HREF="h_rules_incols">Index Line Color</A>
2238 <LI> <A HREF="h_config_quote_color">quoted text</A> in message view
2239 <LI> <A HREF="h_config_customhdr_pattern">text associated with user-defined headers</A> in message view
2240 </UL>
2241 <P>
2242 <End of help on this topic>
2243 </BODY>
2244 </HTML>
2245 ===== h_mainhelp_mouse ======
2246 <HTML>
2247 <HEAD>
2248 <TITLE>Using a Mouse</TITLE>
2249 </HEAD>
2250 <BODY>
2251 <H1>Using a Mouse</H1>
2253 If you are using PC-Alpine mouse support is turned on automatically.
2254 If you are using UNIX Alpine within an X terminal window or within
2255 a terminal emulator that supports an xterm-style mouse, then you may
2256 turn on support for the mouse with the feature
2257 <A HREF="h_config_enable_mouse"><!--#echo var="FEAT_enable-mouse-in-xterm"--></A>.
2258 For UNIX Alpine you will also need to set the $DISPLAY environment variable.
2259 <P>
2260 PC-Alpine offers considerable mouse support. You can view what is
2261 "clickable" by dragging your mouse over any screen; when the
2262 arrow cursor changes into a hand, you found something. Mouse-click
2263 possibilities include navigating between screens and folders and
2264 double-clicking on hyperlinks to open your Web browser.
2265 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
2266 screen. Examples of right-click options include "copy" after
2267 selecting text to copy and "View in New Window" when you click
2268 on a particular message in the Message Index. The menu choices available
2269 to you will vary based upon what screen is open, where on the screen your
2270 cursor is located, and even what action you have already taken.
2271 Within a folder, you may set the "Important" flag on any
2272 message.
2273 <P>
2274 X terminal mouse support is more limited but still quite powerful.
2275 As with PC-Alpine, clicking on any of the commands in the keymenu at
2276 the bottom of the screen will execute that command as if you typed it.
2277 Double-clicking on a link, for example the link to the
2278 <!--#echo var="FEAT_enable-mouse-in-xterm"--> feature in the paragraph above,
2279 will take you to that link.
2280 Double-clicking on an index line will view the message, and so on.
2281 <P>
2282 <End of help on this topic>
2283 </BODY>
2284 </HTML>
2285 ===== h_mainhelp_keywords ======
2286 <HTML>
2287 <HEAD>
2288 <TITLE>Keywords</TITLE>
2289 </HEAD>
2290 <BODY>
2291 <H1>Keywords</H1>
2293 Within a folder, you may set the "Important" flag on any
2294 message.
2295 This doesn't have any system-defined meaning and is only called
2296 the Important flag because many users use it to signify that a message
2297 is important to them in some way.
2298 <P>
2299 You may also define your own set of keywords.
2300 You might know these as user defined flags or as labels.
2301 These are similar to the Important flag but you choose the names for yourself.
2302 <P>
2303 Alpine will only display keywords that
2304 have been added by you in the Flag Details screen or
2305 that have been configured by you using the Setup/Config option
2306 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
2307 Keywords set by other means (for example, by another email client) will not
2308 show up in Alpine unless you configure Alpine to know about them.
2309 They will show up in the Flag Details screen, but will not show up, for example,
2310 in the index line.
2312 <P>
2313 The following entries in Alpine's online help provide additional information
2314 about how to use keywords:
2315 <ul>
2316 <li><A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--> config option</A></li>
2317 <li><A HREF="h_common_flag">Flag command to set keywords</A></li>
2318 </ul>
2319 <P>
2320 <End of help on this topic>
2321 </BODY>
2322 </HTML>
2323 ===== h_mainhelp_roles ======
2324 <HTML>
2325 <HEAD>
2326 <TITLE>Roles</TITLE>
2327 </HEAD>
2328 <BODY>
2329 <H1>Roles</H1>
2331 You may play different roles depending on who you are replying to. For
2332 example, if you are replying to a message addressed to help-desk you may
2333 be acting as a Help Desk Worker. That role may require that you use a
2334 different return address and/or a different signature.
2336 <P>
2337 To configure roles, go to the MAIN MENU and use the Setup command
2338 followed by "Rules" and then "Roles".
2339 The following entries in Alpine's online help provide additional information
2340 about how to
2341 use roles:
2342 <ul>
2343 <li><a href="h_rules_roles">Setup Roles Screen</a></li>
2344 <li><a href="h_role_select">Roles Screen</a></li>
2345 </ul>
2346 <P>
2347 <End of help on this topic>
2348 </BODY>
2349 </HTML>
2350 ===== h_mainhelp_filtering ======
2351 <HTML>
2352 <HEAD>
2353 <TITLE>Filtering</TITLE>
2354 </HEAD>
2355 <BODY>
2356 <H1>Filtering</H1>
2358 The software that actually delivers mail (the stuff that happens
2359 before Alpine is involved) for you is in a better position to do mail filtering
2360 than Alpine itself.
2361 If possible, you may want to look into using that sort of mail filtering to
2362 deliver mail to different folders, delete it, or forward it.
2363 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
2365 <P>
2366 Filtering is a way to automatically move certain messages from one folder
2367 to another or to automatically delete messages.
2368 You may also automatically set the state (Important, New, Deleted, Answered) of messages
2369 and set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
2370 Alpine doesn't have the ability to forward mail to another address or
2371 to deliver vacation messages.
2373 <P>
2374 To configure filtering, go to the MAIN MENU and use the Setup command
2375 followed by "Rules" and then "Filters".
2376 The following entries in Alpine's online help provide additional information
2377 about how to use filtering:
2378 <UL>
2379 <LI> <A HREF="h_rules_filter">Filtering Setup screen</A>
2380 </UL>
2381 <P>
2382 <End of help on this topic>
2383 </BODY>
2384 </HTML>
2385 ===== h_mainhelp_patterns ======
2386 <HTML>
2387 <HEAD>
2388 <TITLE>Patterns</TITLE>
2389 </HEAD>
2390 <BODY>
2391 <H1>Patterns</H1>
2393 Patterns are used with Roles, Filtering, Index Coloring,
2394 Scoring, Other Rules, and Search Rules, so it may help you to understand exactly how Patterns work.
2395 The following entries in Alpine's online help provide information
2396 about using Patterns:
2397 <UL>
2398 <LI> <A HREF="h_rule_patterns">Patterns</A>
2399 </UL>
2400 <P>
2401 <End of help on this topic>
2402 </BODY>
2403 </HTML>
2404 ===== h_mainhelp_cmdlineopts ======
2405 <HTML>
2406 <HEAD>
2407 <TITLE>Command Line Options</TITLE>
2408 </HEAD>
2409 <BODY>
2410 <H1>Command Line Options</H1>
2412 Alpine accepts a number of command line arguments, allowing you, for
2413 example, to start Alpine and immediately access a particular folder.
2414 Many of these arguments overlap with options in the Alpine configuration file.
2415 If there is a difference, then an option set on the command line takes
2416 precedence.
2417 Alpine expects command line arguments (other than addresses) to be
2418 preceded by a "-" (dash) as normally used by UNIX programs.
2419 A <a href="h_command_line_options">full list</a> of command line
2420 possibilities is available.
2421 <P>
2422 <End of help on this topic>
2423 </BODY>
2424 </HTML>
2425 ===== h_mainhelp_config ======
2426 <HTML>
2427 <HEAD>
2428 <TITLE>Alpine Configuration</TITLE>
2429 </HEAD>
2430 <BODY>
2431 <H1>Alpine Configuration</H1>
2433 Unless it has been administratively disabled, the Setup command on the
2434 MAIN MENU has several subcommands that allow you to modify Alpine's behavior.
2435 The possible subcommands are for general Configuration settings,
2436 Printer settings, Changing your Password, Signature setup,
2437 AddressBook setup, Collection Lists setup, Rules (including Roles, Filters,
2438 Scores, Search, Indexcolor, and Other rules), LDAP Directory setup,
2439 and Color configuration.
2440 In particular, the "Config" subcommand has many features you may
2441 set or unset and many other configuration variables that may be set to change
2442 the way Alpine works.
2443 Every one of the hundreds of options available in that configuration settings
2444 screen has help text associated with it.
2445 You may read that text by moving the cursor to highlight the option and then
2446 typing the Help command.
2447 <P>
2448 These settings are stored in your personal
2449 "pinerc" configuration file (or, optionally, they may be stored
2450 <A HREF="h_config_remote_config">remotely</A>),
2451 but on shared systems these settings
2452 may be over-ridden by a system-wide control file (due to local site
2453 security or support policies). A global pine configuration file can also
2454 be used to set default values for all Alpine users on a particular system.
2455 Power users may be interested in splitting their personal configuration
2456 data into two pieces, a generic piece and
2457 <A HREF="h_config_exceptions">exceptions</A> which apply to
2458 a particular platform.
2459 They may also be interested in <A HREF="h_config_inheritance">configuration inheritance</A>.
2460 General Alpine configuration information can be found
2461 <A HREF="h_news_config">here</A>.
2462 <P>
2463 <End of help on this topic>
2464 </BODY>
2465 </HTML>
2466 ===== h_mainhelp_aggops ======
2467 <HTML>
2468 <HEAD>
2469 <TITLE>Aggregate Operations</TITLE>
2470 </HEAD>
2471 <BODY>
2472 <H1>Aggregate Operations</H1>
2474 When you are in the MESSAGE INDEX, the available commands
2475 (for example, Delete, Undelete, Save, Reply, and so on)
2476 normally act on a single message.
2477 So, for example, if you press the Delete command, the currently highlighted
2478 message is marked Deleted.
2479 These commands that normally act on a single message may be applied to
2480 several messages at once instead.
2481 <P>
2482 By default this feature is turned on, but it could be administratively turned
2483 off to reduce complexity.
2484 The feature
2485 <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>
2486 in the Setup/Config screen is used to turn it off or on.
2487 When this feature is turned on, the four commands "Select",
2488 "SelectCur", "ZoomMode", and "Apply"
2489 are available.
2490 The two selection commands allow you to mark a set of
2491 messages as being "selected".
2492 The "ZoomMode" command will toggle between
2493 displaying only the selected messages and displaying all the messages.
2494 The "Apply" command allows you to
2495 apply one of the regular MESSAGE INDEX commands to all of the selected
2496 messages instead of to only the highlighted message.
2497 <P>
2498 An example aggregate operation would be to catch up when reading
2499 a news group.
2500 That is, get rid of all the messages in the news group so that you can
2501 start fresh.
2502 The easiest way to do this in Alpine is to use aggregate operations.
2503 You want to Delete all of the messages in the group.
2504 You could start at the top and type "D" once for every message.
2505 A much faster method is to first Select all of the messages in the group,
2506 and then Delete all of them.
2507 This would take four keystrokes:
2508 <P>
2509 <CENTER><SAMP>; a (to select all messages)</SAMP></CENTER>
2510 <BR>
2511 <CENTER><SAMP>a d (to delete all selected messages)</SAMP></CENTER>
2512 <P>
2513 Another use of Select is to use it for searching for a particular message
2514 or set of messages in a large folder.
2515 You may know that the message was From a certain user.
2516 You could select all messages from that user to start, and use Zoom to
2517 look at only those messages.
2518 If there were still too many messages to look at you could Narrow the
2519 set of messages further by selecting from all of those messages only
2520 the ones that were after a certain date, or contained a particular phrase
2521 in the Subject, or were too a particular address, and so on.
2522 That may be the end of what you are doing, or you may want to use Apply to
2523 Save or Forward or Print all of the selected messages.
2524 <P>
2525 Some related help topics are
2526 <UL>
2527 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
2528 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
2529 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
2530 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
2531 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
2532 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
2533 </UL>
2534 <P>
2535 <End of help on this topic>
2536 </BODY>
2537 </HTML>
2538 ===== h_mainhelp_readingnews ======
2539 <HTML>
2540 <HEAD>
2541 <TITLE>Reading News</TITLE>
2542 </HEAD>
2543 <BODY>
2544 <H1>Reading News</H1>
2546 <H2>Background</H2>
2547 Alpine can read and post to Internet (or USENET) newsgroups, using the same
2548 commands as for mail. Similar to mailing lists but existing on a larger scale,
2549 Usenet newsgroups allow groups of people with common interests to discuss
2550 particular topics. You might find newsgroups related to your career, or you
2551 might wish to check out the online discussion among the fans of your favorite
2552 television show.
2554 <H2>Configuring Alpine for Reading News</H2>
2555 Alpine often arrives
2556 pre-configured by your system administrator to automatically access the
2557 newsgroups offered by your organization, Internet Service Provider, or
2558 school. PC-Alpine users, and those attempting to customize Unix Alpine, will
2559 need additional details on <a href="h_configuring_news">how to
2560 configure Alpine to read news</a>.
2562 <H2>Accessing Newsgroups</H2>
2563 The first step in reading news is to access the newsgroups collections
2564 screen from Alpine. If everything is configured properly, you should be able
2565 to do this by first typing L (folder List), then selecting the folder
2566 collection listed as "News." The actual name of this collection may differ
2567 from system to system.
2569 <H2>Subscribing to Newsgroups</H2>
2571 Once you have accessed the news collection, you need to subscribe to a
2572 newsgroup that interests you. Subscribing to a newsgroup means that Alpine
2573 will keep a record of the newsgroups in which you are interested and which
2574 articles in those newsgroups have been read.
2576 <H2>Using Newsgroups</H2>
2577 Alpine uses the similar commands to read news as to read mail. For example,
2578 the D command marks messages as Deleted (or "Dismissed," if you prefer),
2579 and the R command Replies to a news posting. Basically, Alpine allows you to
2580 read news as if it were mail, so you don't need to change the way you
2581 interact with Alpine.
2582 <P>
2583 There is also additional Alpine help available on
2584 <A HREF="h_reading_news">how to use Alpine to read news</A>.
2585 <P>
2586 <End of help on this topic>
2587 </BODY>
2588 </HTML>
2589 ===== h_mainhelp_securing ======
2590 <HTML>
2591 <HEAD>
2592 <TITLE>Securing your Alpine Session</TITLE>
2593 </HEAD>
2594 <BODY>
2595 <H1>Securing your Alpine Session</H1>
2597 By default, Alpine will attempt to connect to an IMAP server on the normal
2598 IMAP service port (143).
2599 If the Alpine you are using has been built to
2600 support "Transport Layer Security" (TLS)
2601 and "Secure Sockets Layer" (SSL)
2602 (check by clicking <A HREF="X-Alpine-Config:">here</A>),
2603 and the server offers the STARTTLS capability, then a secure (encrypted)
2604 session will be established.
2605 <P>
2606 When you are connected to a remote folder the titlebar will contain a plus sign
2607 in the far right column if the connection is encrypted using TLS or SSL.
2608 Similarly, when you are being prompted for a password a plus sign will appear in the prompt
2609 if the connection is encrypted.
2611 <H2>More Information on Alpine with SSL and TLS</H2>
2612 <UL>
2613 <LI> <A HREF="h_release_tlscerts">TLS and SSL Usage Note</A> </LI>
2614 <LI> <A HREF="h_folder_server_syntax">/SSL</A> option for older servers which support port 993 SSL but not TLS </LI>
2615 <LI> <A HREF="h_config_alt_auth"><!--#echo var="FEAT_try-alternative-authentication-driver-first"--></A> feature </LI>
2616 <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>
2617 </UL>
2618 <H2>Here are some other security-related features and options</H2>
2619 <P>
2620 <UL>
2621 <LI> <A HREF="h_config_disable_password_caching"><!--#echo var="FEAT_disable-password-caching"--></A> feature to disable password caching </LI>
2622 <LI> <A HREF="h_config_mailcap_params"><!--#echo var="FEAT_enable-mailcap-param-substitution"--></A> feature </LI>
2623 <LI> <A HREF="h_config_disable_auths"><!--#echo var="VAR_disable-these-authenticators"--></A> option </LI>
2624 </UL>
2625 <P>
2626 <End of help on this topic>
2627 </BODY>
2628 </HTML>
2629 ===== h_mainhelp_problems ======
2630 <HTML>
2631 <HEAD>
2632 <TITLE>Reporting Problems</TITLE>
2633 </HEAD>
2634 <BODY>
2635 <H1>Reporting Problems</H1>
2637 We ask that you first read the relevant help screens and then seek
2638 assistance from your own local support staff. Once you are sure that your
2639 difficulty is not a local configuration problem, you might look at the
2640 help section explaining where to look for
2641 <A HREF="h_finding_help">more information</A> and where to
2642 get assistance.
2643 <P>
2645 <ADDRESS>
2646 Eduardo Chappa <chappa@gmx.com>
2647 </ADDRESS>
2649 <P>
2650 <End of help on this topic>
2651 </BODY>
2652 </HTML>
2653 ===== h_main_menu_commands ======
2654 <HTML>
2655 <HEAD>
2656 <TITLE>MAIN MENU COMMANDS</TITLE>
2657 </HEAD>
2658 <BODY>
2659 <H1>MAIN MENU COMMANDS</H1>
2661 <!--chtml if pinemode="function_key"-->
2662 Available Commands --
2663 Group 1 Available Commands -- Group 2<BR>
2664 ------------------------------
2665 --------------------
2666 ----------<BR>
2667 F1 Show this help text F1 Show this help text<BR>
2668 F2 Show all other available commands F2 Show other commands<BR>
2669 F3 Quit Alpine<BR>
2670 F4 Execute current MAIN MENU command F4 <A
2671 HREF="h_common_compose">Compose</A> a message<BR>
2672 F5 Select previous command up on menu F5 <A
2673 HREF="h_common_folders">FOLDER LIST</A> screen<BR>
2674 F6 Select next command down on menu F6 <A
2675 HREF="h_common_goto">Goto</A> a specified folder<BR>
2676
2677 F7 <A
2678 HREF="h_common_index">MESSAGE INDEX</A> screen<BR>
2679
2680 F8 <A
2681 HREF="h_main_journal">Journal</A> of status messages<BR>
2682 F9 Display <A
2683 HREF="h_main_release_notes">Release Notes</A> notes F9 <A
2684 HREF="h_main_setup">SETUP</A> menus<BR>
2685 F10 <A
2686 HREF="h_main_kblock">Lock Keyboard</A> F10 <A
2687 HREF="h_main_addrbook">ADDRESS BOOK</A> screen<BR>
2688
2689 F11 <A
2690 HREF="h_common_role">Compose message using a role</a><BR>
2691 <!--chtml else-->
2692 General Alpine Commands Main Menu Screen Commands<BR>
2693 --------------------- --------------------------<BR>
2694 ? Show Help Text O Show all Other available commands<BR>
2695 C <A
2696 HREF="h_common_compose">Compose</A> a message P Select Previous command up on menu<BR>
2697 I <A
2698 HREF="h_common_index">MESSAGE INDEX</A> screen N Select Next command down on menu<BR>
2699 L <A
2700 HREF="h_common_folders">FOLDER LIST</A> screen R Display Alpine <A HREF="h_main_release_notes">Release Notes</A><BR>
2701 A <A
2702 HREF="h_main_addrbook">ADDRESS BOOK</A> screen K <A
2703 HREF="h_main_kblock">Lock Keyboard</A><BR>
2704 S <A
2705 HREF="h_main_setup">SETUP</A> functions G <A
2706 HREF="h_common_goto">Goto</A> a specified folder<BR>
2707 Q Quit Alpine J <A HREF="h_main_journal">Journal</A> of status messages<BR>
2708 # <A
2709 HREF="h_common_role">Compose message using a role</a><BR>
2710 <!--chtml endif-->
2712 <P>
2713 NOTE:
2714 <OL>
2715 <LI>For help on a particular command, highlight the bold text associated
2716 with it above and hit Return.
2717 <LI> The availability of certain commands (e.g. some of the options under
2718 SETUP) is determined by Alpine configuration files and system capabilities.
2719 At some sites, certain commands may not be available due to security or
2720 support concerns.
2721 </OL>
2722 <P>
2723 <End of help on this topic>
2724 </BODY>
2725 </HTML>
2727 ===== h_command_line_options ======
2728 <HTML>
2729 <HEAD>
2730 <TITLE>COMMAND LINE OPTIONS</TITLE>
2731 </HEAD>
2732 <BODY>
2733 <H1>COMMAND LINE OPTIONS</H1>
2734 Possible starting arguments for Alpine:
2736 <DL COMPACT>
2738 <DT> <EM>[addresses]</EM>
2740 <DD> Send-to: If you give <EM>Alpine</EM> an argument or arguments which
2741 do not begin with a dash, <EM>Alpine</EM> treats them as email addresses.
2742 <EM>Alpine</EM> will startup in
2743 the composer with a message started to the addresses specified.
2744 Once the message is sent, the <EM>Alpine</EM> session closes.
2745 Standard input redirection is allowed.
2746 Separate multiple addresses with a space between them.
2747 Addresses are placed in the "To" field only.
2748 <P>
2750 <DT> < <EM>file</EM>
2752 <DD> <EM>Alpine</EM> will startup in the composer with <EM>file</EM> read
2753 into the body of the message.
2754 Once the message is sent, the <EM>Alpine</EM> session closes.
2755 <P>
2757 <DT> -attach <EM>file</EM>
2759 <DD> Go directly into composer with given file attached.
2760 <P>
2762 <DT> -attachlist <EM>file-list</EM>
2764 <DD> Go directly into composer with given files attached.
2765 This must be the last option on the command line.
2766 <P>
2768 <DT> -attach_and_delete <EM>file</EM>
2770 <DD> Go directly into composer with given file attached, delete when finished.
2771 <P>
2773 <DT> -aux <EM>local_directory</EM>
2775 <DD> <EM>PC-Alpine</EM> only.
2776 This tells <EM>PC-Alpine</EM> the local directory to use for storing auxiliary
2777 files, like debug files, address books, and signature files. The pinerc may
2778 be local or remote.
2779 <P>
2781 <DT> -bail
2783 <DD> If the personal configuration file doesn't already exist, exit.
2784 This might be useful if the configuration file is accessed using some
2785 remote filesystem protocol. If the remote mount is missing this will cause
2786 <EM>Alpine</EM> to quit instead of creating a new pinerc.
2787 <P>
2789 <DT> -c <EM>n</EM>
2791 <DD> When used with the <CODE>-f</CODE> option, apply the <EM>n</EM>th context.
2792 This is used when there are multiple folder collections (contexts) and you
2793 want to open a folder not in the primary collection.
2794 <P>
2796 <DT> -conf
2798 <DD> Configuration: Prints a sample system configuration file to the
2799 screen or standard output. To generate an initial system configuration
2800 file, execute
2802 <PRE><CODE>
2803 pine -conf > <!--#echo var="PINE_CONF_PATH"-->
2804 </CODE></PRE>
2805 <P>
2807 To generate a system configuration file using settings from an old
2808 system configuration file, execute
2810 <PRE><CODE>
2811 pine -P old-pine.conf -conf > <!--#echo var="PINE_CONF_PATH"-->
2812 </CODE></PRE>
2813 <P>
2814 A system configuration file is not required.
2815 <P>
2817 <DT> -copy_abook <<EM>local_abook_file</EM>> <<EM>remote_abook_folder</EM>>
2819 <DD> Copy an address book file to a remote address book folder.
2820 If the remote folder doesn't exist, it will be created.
2821 If it exists but the first message in the folder isn't a remote address
2822 book header message, the copy will be aborted.
2823 This flag will not usually be used by a user.
2824 Instead, the user will create a remote address book from within <EM>Alpine</EM>
2825 and copy entries from the local address book by using aggregate Save in
2826 the address book screen.
2827 <P>
2829 <DT> -copy_pinerc <<EM>local_pinerc_file</EM>> <<EM>remote_pinerc_folder</EM>>
2831 <DD> Copy a pinerc configuration file to a remote pinerc folder.
2832 If the remote folder doesn't exist, it will be created.
2833 If it exists but the first message in the folder isn't a remote pinerc
2834 header message, the copy will be aborted.
2835 This flag may be useful to users who already have a local pinerc file and
2836 would like to convert it to a remote pinerc folder and use that instead.
2837 This gives a way to bootstrap that conversion without having to manually
2838 reset all of the variables in the remote pinerc folder.
2839 <P>
2841 <DT> -d <EM>debug-level</EM>
2843 <DD> Debug Level: Sets the level of debugging information written by
2844 <EM>Alpine</EM>.
2845 <EM>debug-level</EM> can be set to any integer 0-9.
2846 A debug level of 0 turns off debugging for the session.
2847 (Actually there are some levels higher than 9, but you probably don't
2848 want to see them.)
2849 <P>
2851 <DT> -d <EM>keywords</EM>
2853 <DD> You may use a more detailed version of the debugging flag to set
2854 the debug level in separate parts of <EM>Alpine</EM>.
2855 The possibilities are flush, timestamp, imap=0..4, tcp, numfiles=0..31, and
2856 verbose=0..9.
2857 <EM>Flush</EM> causes debugging information to be flushed immediately to
2858 the debug file as it is written.
2859 <EM>Verbose</EM> is the general debugging verbosity level.
2860 <EM>Timestamp</EM> causes timestamps to be added to the debug file, which
2861 is useful when you are trying to figure out what is responsible for delays.
2862 <EM>Numfiles</EM> sets the number of debug files saved.
2863 <EM>Imap</EM> sets the debug level for the debugging statements related
2864 to the conversation with the IMAP server, and more generally, for the
2865 debugging related to <EM>Alpine</EM>'s interaction with the C-Client library.
2866 <EM>Tcp</EM> turns on some TCP/IP debugging.
2867 <P>
2869 <DT> -f <EM>folder</EM>
2871 <DD> Startup folder: <EM>Alpine</EM> will open this folder in place
2872 of the standard INBOX.
2873 <P>
2875 <DT> -F <EM>file</EM>
2877 <DD> Open named text file for viewing and forwarding.
2878 <P>
2880 <DT> -h
2882 <DD> Help: Prints the list of available command-line arguments to the
2883 screen.
2884 <P>
2886 <DT> -i
2888 <DD> <EM>Alpine</EM> will start up in the FOLDER INDEX
2889 screen instead of the MAIN MENU.
2890 <P>
2892 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"-->=i</EM>.
2893 <P>
2895 <DT> -I <EM>a,b,c,...</EM>
2897 <DD> Initial Keystrokes: <EM>Alpine</EM> will execute this comma-separated
2898 sequence of commands upon startup.
2899 This allows users to get <EM>Alpine</EM> to start in any
2900 of its menus/screens.
2901 You cannot include any input to the composer in the initial keystrokes.
2902 The key <Return> is represented by a ``CR'' in
2903 the keystroke list; the spacebar is designated by the letters ``SPACE''.
2904 Control keys are two character sequences beginning with ``^'', such as
2905 ``^I''.
2906 A tab character is ``TAB''.
2907 Function keys are ``F1'' - ``F12'' and the arrow keys are ``UP'',
2908 ``DOWN'', ``LEFT'', and ``RIGHT''.
2909 A restriction is that you can't mix function keys and character keys in this
2910 list even though you can, in some cases, mix them when running <EM>Alpine</EM>.
2911 A user can always use only <EM>character</EM> keys in the startup list even
2912 if he or she is using <EM>function</EM> keys normally, or vice versa.
2913 If an element in this list is a string of characters surrounded by double
2914 quotes (") then it will be expanded into the individual characters in
2915 the string, excluding the double quotes.
2916 <P>
2918 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"--></EM>
2919 <P>
2921 <DT> -install
2923 <DD> For <EM>PC-Alpine</EM> only, this option prompts the user for
2924 some basic information to help with getting properly set up.
2925 <P>
2927 <DT> -k
2929 <DD> Function-Key Mode: When invoked in this way, <EM>Alpine</EM> expects
2930 the input of commands to be function-keys.
2931 Otherwise, commands are linked to the regular character keys.
2932 <P>
2934 Configuration equivalent: <EM><!--#echo var="FEAT_use-function-keys"--></EM> included in
2935 <EM>Feature-List</EM>.
2936 <P>
2938 <DT> -n <EM>n</EM>
2940 <DD> Message-Number: When specified, <EM>Alpine</EM> starts up in the
2941 FOLDER INDEX screen with the current message being the specified
2942 message number.
2943 <P>
2945 <DT> -nosplash
2947 <DD> <EM>PC-Alpine</EM> only.
2948 This tells <EM>PC-Alpine</EM> not to display the splash screen upon startup.
2949 This may be helpful for certain troubleshooting or terminal server scenarios.
2950 <P>
2952 <DT> -o <EM>folder</EM>
2954 <DD> Opens the INBOX (or a folder specified via the -f argument) ReadOnly.
2955 <P>
2957 <DT> -p <EM>pinerc</EM>
2959 <DD> Uses the named file as the personal configuration file instead of
2960 <EM>~/.pinerc</EM> or the default PINERC search sequence <EM>PC-Alpine</EM> uses.
2961 Alpinerc may be either a local file or a remote configuration folder.
2962 <P>
2964 <DT> -P <EM>pinerc</EM>
2966 <DD> Uses the named file as the system wide configuration file instead of
2967 <EM><!--#echo var="PINE_CONF_PATH"--></EM> on UNIX, or nothing on <EM>PC-Alpine</EM>.
2968 Alpinerc may be either a local file or a remote configuration folder.
2969 <P>
2971 <DT> -passfile <EM>passfile</EM>
2973 <DD> This tells <EM>Alpine</EM> what file should be used as the password file.
2974 This should be a fully-qualified filename.
2975 <P>
2977 <DT> -pinerc <EM>file</EM>
2979 <DD> Output fresh pinerc configuration to <EM>file</EM>, preserving the
2980 settings of variables that the user has made.
2981 Use <EM>file</EM> set to ``-'' to make output go to standard out.
2982 <P>
2984 <DT> -r
2986 <DD> Restricted Mode: For UNIX <EM>Alpine</EM> only.
2987 <EM>Alpine</EM> in restricted mode can only send email to itself.
2988 Save and export are limited.
2989 <P>
2991 <DT> -registry <EM>cmd</EM>
2993 <DD> For <EM>PC-Alpine</EM> only, this option affects the values of
2994 <EM>Alpine</EM>'s registry entries.
2995 Possible values for <EM>cmd</EM> are set, clear, and dump.
2996 <EM>Set</EM> will always reset <EM>Alpine</EM>'s registry
2997 entries according to its current settings.
2998 <EM>Clear</EM> will clear the registry values.
2999 <EM>Clearsilent</EM> will clear the registry values without any dialogs.
3000 <EM>Dump</EM> will display the values of current registry settings.
3001 Note that the dump command is currently disabled.
3002 Without the -registry option, <EM>PC-Alpine</EM> will write values into
3003 the registry only if there currently aren't any values set.
3004 <P>
3006 <DT> -sort <EM>key</EM>
3008 <DD> Sort-Key: Specifies the order messages will be displayed in for the
3009 FOLDER INDEX screen.
3010 <EM>Key</EM> can have the following values:
3011 arrival, date, subject, orderedsubj, thread, from, size, score, to, cc,
3012 arrival/reverse, date/reverse, subject/reverse, orderedsubj/reverse, thread/reverse,
3013 from/reverse, size/reverse, score/reverse, to/reverse, and cc/reverse.
3014 The default value is "arrival".
3015 The <EM>key</EM> value reverse is equivalent to arrival/reverse.
3016 <P>
3018 Configuration equivalent: <EM><!--#echo var="VAR_sort-key"--></EM>.
3019 <P>
3021 <DT> -uninstall
3023 <DD> For <EM>PC-Alpine</EM> only, this option removes references to Alpine
3024 in Windows settings. The registry settings are removed and
3025 the password cache is cleared.
3026 <P>
3028 <DT> -url <EM>url</EM>
3030 <DD> Open the given URL.
3031 <P>
3033 <DT> -v
3035 <DD> Version: Print version information to the screen.
3036 <P>
3038 <DT> -x <EM>exceptions_config</EM>
3040 <DD> Configuration settings in the exceptions configuration override your normal
3041 default settings.
3042 <EM>Exceptions_config</EM> may be either a local file or a remote Alpine configuration folder.
3043 <P>
3045 <DT> -z
3047 <DD> Enable Suspend: When run with this flag, the key sequence ctrl-z
3048 will suspend the <EM>Alpine</EM> session.
3049 <P>
3051 Configuration equivalent: <EM><!--#echo var="FEAT_enable-suspend"--></EM> included in
3052 <EM>Feature-List</EM>.
3053 <P>
3055 <DT> -<EM>option</EM>=<EM>value</EM>
3057 <DD> Assign <EM>value</EM> to the config option <EM>option</EM>.
3058 For example, <EM>-signature-file=sig1</EM> or
3059 <EM>-Feature-List=signature-at-bottom</EM>.
3060 Note: Feature-List values are
3061 additive and features may be preceded with no- to turn them off.
3062 Also, as a special case, the "Feature-List=" part of that may be
3063 omitted. For example, <EM>-signature-at-bottom</EM> is equivalent to
3064 <EM>-Feature-List=signature-at-bottom</EM>.
3065 <P>
3067 </DL>
3068 <P>
3069 <End of help on this topic>
3070 </BODY>
3071 </HTML>
3072 ===== h_configuring_news ======
3073 <HTML>
3074 <HEAD>
3075 <TITLE>CONFIGURING NEWS</TITLE>
3076 </HEAD>
3077 <BODY>
3078 <H1>CONFIGURING NEWS</H1>
3079 Alpine can access news folders in any one of three different ways:
3080 <DL>
3081 <DT>REMOTE NNTP</DT>
3082 <DD>Using the Network News Transport Protocol (NNTP) to
3083 access news on a remote news server. In this case the newsrc file is
3084 stored on the machine where Alpine is running.
3086 <P>
3087 To specify a remote news-collection accessed via NNTP use the
3088 SETUP/collectionList screen's "Add" command. Set the
3089 Server: value to the NNTP server's hostname appended with the
3090 communication method "/service=NNTP", and set the Path:
3091 value to the "#news." namespace (without the quotes). See
3092 the "<A HREF="h_composer_cntxt_server">Server:</A>" field's
3093 help text for a more complete explanation of access method, and the
3094 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3095 text for a more complete explanation of "namespace".
3096 <P>
3097 Instead of specifying a news-collection, you may simply set the
3098 <A HREF="h_config_nntp_server">NNTP Server</A>
3099 option, which will cause Alpine to create a default news-collection for you.
3100 Another NNTP option that may be of interest is
3101 <A HREF="h_config_nntprange"><!--#echo var="VAR_nntp-range"--></A>.
3103 <DT>REMOTE IMAP</DT>
3104 <DD>Using the Internet Message Access Protocol (IMAP) to
3105 access news on a remote news server. In this case, your newsrc file is
3106 stored on the news server, in your home directory, so you must have an
3107 account on the news server, but you would be running Alpine on a different
3108 machine. The news server must be running an IMAPd server process.
3110 <P>
3111 To specify a remote news-collection accessed via IMAP use the
3112 SETUP/collectionList screen's "Add" command. Set the
3113 Server: value to the IMAP server's hostname, and set the Path: value
3114 to the "#news." namespace (without the quotes). See the
3115 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3116 text for a more complete explanation of "namespace".
3118 </DD>
3120 <DT>LOCAL</DT>
3121 <DD>Using local file access to the news database. In this
3122 case, your newsrc file is stored on the news server, in your home
3123 directory, so you must have an account on the news server, and you would
3124 be running Alpine on the same machine.
3126 <P>
3127 To specify a local news-collection use the SETUP/collectionList
3128 screen's "Add" command. Leave the Server: value blank, and
3129 set the Path: value to the "#news." namespace (without the
3130 quotes). See the "<A HREF="h_composer_cntxt_path">Path:</A>"
3131 field's help text for a more complete explanation of "namespace".
3133 </DD>
3134 </DL>
3136 <P>
3138 NOTE: Should no news-collection be defined as above, Alpine will
3139 automatically create one using the Setup/Config screen's
3140 "<!--#echo var="VAR_nntp-server"-->" variable's value if defined. The collection
3141 will be created as a "Remote NNTP" as described above.
3143 <P>
3145 If you are a PC-Alpine user, either option 1 (NNTP) or option 2 (IMAP) is
3146 possible. If you don't have an account on the news server, or if the news
3147 server is not running an IMAP daemon, then you must use NNTP. (If you are not
3148 sure, ask your service provider, university, or company for help.) In
3149 this case, your Unix .newsrc file can be transferred to your PC. A good
3150 place to put it would be in the same directory as your PINERC file, under
3151 the name NEWSRC, but you can
3152 <A HREF="h_config_newsrc_path">specify a different location</A>
3153 via Alpine's Setup/Config screen.
3155 <P>
3156 Other configuration features related to news are
3157 <A HREF="h_config_8bit_nntp"><!--#echo var="FEAT_enable-8bit-nntp-posting"--></A>.
3158 <A HREF="h_config_compose_news_wo_conf"><!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></A>,
3159 <A HREF="h_config_news_uses_recent"><!--#echo var="FEAT_news-approximates-new-status"--></A>,
3160 <A HREF="h_config_news_cross_deletes"><!--#echo var="FEAT_news-deletes-across-groups"--></A>,
3161 <A HREF="h_config_news_catchup"><!--#echo var="FEAT_news-offers-catchup-on-close"--></A>,
3162 <A HREF="h_config_post_wo_validation"><!--#echo var="FEAT_news-post-without-validation"--></A>,
3163 <A HREF="h_config_read_in_newsrc_order"><!--#echo var="FEAT_news-read-in-newsrc-order"--></A>, and
3164 <A HREF="h_config_quell_post_prompt"><!--#echo var="FEAT_quell-extra-post-prompt"--></A>.
3166 <P>
3167 <End of help on this topic>
3168 </BODY>
3169 </HTML>
3170 ===== h_reading_news ======
3171 <HTML>
3172 <HEAD>
3173 <TITLE>READING NEWS</TITLE>
3174 </HEAD>
3175 <BODY>
3176 <H1>READING NEWS</H1>
3178 Alpine uses almost the same commands for manipulating news folders as for
3179 mail folders. This means, for example, that when you are done with a
3180 message, you would use "D" to mark it as Deleted (or Dismissed,
3181 if you prefer.) This "mail-like" behavior differs from that of
3182 most newsreaders, wherein a message is implicitly dismissed after you have
3183 looked at it once. We strongly believe that Alpine should offer as much
3184 consistency as possible between mail and news, so the mail paradigm --
3185 wherein a message does not magically disappear without explicit action by
3186 the user -- is used for news as well. <P>
3188 If you answer a message in a news folder, the index view will show the
3189 "A" flag as usual; but the industry standard file Alpine uses to
3190 keep track of what news as been read has no way of storing this flag, so
3191 it will not be preserved across sessions. The Deleted flag is the only
3192 one that is preserved when you leave and then return to a newsgroup. As an
3193 additional note on replies, when you Reply to a newsgroup message and say
3194 you want to reply to all recipients, Alpine will ask if you want to post the
3195 message to all the newsgroups listed in the original message. <P>
3197 If you would like Alpine to mark more-or-less recent news messages as
3198 "New", then set the
3199 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
3200 feature (which is set by default). This will cause messages after the last one you have marked as
3201 Deleted to appear with "N" status in the MESSAGE INDEX. The
3202 "N" status often makes it easier to distinguish later news
3203 articles from those you've previously seen, but not yet disposed of via
3204 the "D" key. Note that this is an approximation, not an exact
3205 record of which messages you have not seen.
3206 <P>
3208 A frequent operation in news-reading is "catching up" -- that
3209 is, getting rid of all the messages in the newsgroup so that you can
3210 "start fresh." The easiest way to do this in Alpine is via the
3211 Select command. You would enter the following four keystrokes:
3212 <tt>;aad</tt> to select all messaged, and then apply the delete (or
3213 dismiss) command to all of them.
3215 <P>
3216 There are also additional details on
3217 <A HREF="h_configuring_news">configuring news</a>.
3219 <P>
3220 <End of help on this topic>
3221 </BODY>
3222 </HTML>
3223 ====== h_help_index ======
3224 <HTML>
3225 <HEAD>
3226 <TITLE>Help Index</TITLE>
3227 </HEAD>
3228 <BODY>
3229 <H1>Help Index</H1>
3230 <ul>
3231 <li><a href="h_mainhelp_abooks">Address Books</a></li>
3232 <li><a href="h_abook_top">ADDRESS BOOK LIST COMMANDS</a>
3233 <li><a href="h_main_addrbook">Address Book Command</a>
3234 <li><a href="h_abook_view">Address Book View Explained</a>
3235 <li><a href="h_compose_addrcomplete">Address Completion</a>
3236 <li><a href="h_abook_select_listmode">Address Listmode Selection from Composer Explained</a>
3237 <li><a href="h_abook_select_checks">Address Selection from Composer Explained</a>
3238 <li><a href="h_composer_abook_comment">Addressbook Comment Explained</a>
3239 <li><a href="h_composer_abook_fcc">Addressbook Fcc Explained</a>
3240 <li><a href="h_composer_abook_add_folder">Addressbook Folder Name Field Explained</a>
3241 <li><a href="h_composer_abook_full">Addressbook Fullname Explained</a>
3242 <li><a href="h_composer_abook_add_nick">Addressbook NickName Field Explained</a>
3243 <li><a href="h_composer_abook_nick">Addressbook Nickname Explained</a>
3244 <li><a href="h_abook_select_addr">Addressbook Selection Explained</a>
3245 <li><a href="h_abook_select_top">Addressbook Selection Navigation Explained</a>
3246 <li><a href="h_composer_abook_add_server">Addressbook Server Name Field Explained</a>
3247 <li><a href="h_mainhelp_aggops">Aggregate Operations</a>
3248 <li><a href="h_mainhelp_config">Alpine Configuration</a>
3249 <li><a href="h_mainhelp_pinehelp">Alpine Help</a>
3250 <li><a href="h_news_legal">Alpine Legal Notices</a>
3251 <li><a href="h_compose_alted">Alt Editor Command</a>
3252 <li><a href="h_index_cmd_apply">Apply Command</a>
3253 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a>
3254 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a>
3255 <li><a href="h_mainhelp_filtering">Blocking Messages</a>
3256 <li><a href="h_composer_browse">BROWSER</a>
3257 <li><a href="h_common_bounce">Bounce Command</a>
3258 <li><a href="h_compose_cancel">Cancel Command</a>
3259 <li><a href="h_config_change_your_from">Changing your From Address</a>
3260 <li><a href="h_collection_screen">COLLECTION LIST screen</a>
3261 <li><a href="h_mainhelp_color">Color</a>
3262 <li><a href="h_composer_ctrl_j">COMPOSER ATTACH</a>
3263 <li><a href="h_composer">COMPOSER COMMANDS</a>
3264 <li><a href="h_mainhelp_composing">Composing Messages</a>
3265 <li><a href="h_mainhelp_collections">Collection Lists</a>
3266 <li><a href="h_composer_cntxt_nick">Collection Nickname Explained</a>
3267 <li><a href="h_composer_cntxt_path">Collection Path: Explained</a>
3268 <li><a href="h_composer_cntxt_server">Collection Server: Explained</a>
3269 <li><a href="h_composer_cntxt_view">Collection View: Explained</a>
3270 <li><a href="h_mainhelp_cmdlineopts">Command Line Options</a>
3271 <li><a href="h_common_compose">Compose Command</a>
3272 <li><a href="h_edit_nav_cmds">Composer Editing Commands Explained</a>
3273 <li><a href="h_common_conditional_cmds">Conditional Commands</a>
3274 <li><a href="h_reply_token_conditionals">Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</a>
3275 <li><a href="h_mainhelp_config">Configuration</a>
3276 <li><a href="h_composer_custom_free">CUSTOMIZED HEADER FIELD</a>
3277 <li><a href="h_config_dflt_color">Default Color</a>
3278 <li><a href="h_common_delete">Delete and Undelete Commands</a>
3279 <li><a href="h_composer_qserv_cn">Directory Query Form Explained</a>
3280 <li><a href="h_special_list_commands">Email List Commands Explained</a>
3281 <li><a href="h_composer_search">Explanation of Composer Whereis Command </a>
3282 <li><a href="h_folder_open">Explanation of Folder Selection</a>
3283 <li><a href="h_special_xon_xoff">Explanation of Alpine's XOFF/XON Handling</a>
3284 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a>
3285 <li><a href="h_ge_export">Export File Selection</a>
3286 <li><a href="h_ge_allparts">Export Message File Selection</a>
3287 <li><a href="h_index_cmd_expunge">Expunge/Exclude Command</a>
3288 <li><a href="h_info_on_locking">FAQs on Alpine Locking</a>
3289 <li><a href="h_config_allow_chg_from">FEATURE: <!--#echo var="FEAT_allow-changing-from"--></a>
3290 <li><a href="h_config_allow_talk">FEATURE: <!--#echo var="FEAT_allow-talk"--></a>
3291 <li><a href="h_config_alt_compose_menu">FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></a>
3292 <li><a href="h_config_alt_role_menu">FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></a>
3293 <li><a href="h_config_force_low_speed">FEATURE: <!--#echo var="FEAT_assume-slow-link"--></a>
3294 <li><a href="h_config_auto_read_msgs">FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></a>
3295 <li><a href="h_config_auto_open_unread">FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></a>
3296 <li><a href="h_config_auto_unselect">FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></a>
3297 <li><a href="h_config_auto_unzoom">FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></a>
3298 <li><a href="h_config_auto_zoom">FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></a>
3299 <li><a href="h_config_use_boring_spinner">FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></a>
3300 <li><a href="h_config_check_mail_onquit">FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></a>
3301 <li><a href="h_config_combined_abook_display">FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></a>
3302 <li><a href="h_config_combined_folder_display">FEATURE: <!--#echo var="FEAT_combined-folder-display"--></a>
3303 <li><a href="h_config_combined_subdir_display">FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></a>
3304 <li><a href="h_config_cancel_confirm">FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></a>
3305 <li><a href="h_config_lame_list_mode">FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></a>
3306 <li><a href="h_config_compose_rejects_unqual">FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></a>
3307 <li><a href="h_config_send_filter_dflt">FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></a>
3308 <li><a href="h_config_compose_news_wo_conf">FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></a>
3309 <li><a href="h_config_del_from_dot">FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></a>
3310 <li><a href="h_config_compose_maps_del">FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></a>
3311 <li><a href="h_config_confirm_role">FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></a>
3312 <li><a href="h_config_tab_no_prompt">FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></a>
3313 <li><a href="h_config_dates_to_local">FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></a>
3314 <li><a href="h_config_copy_to_to_from">FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></a>
3315 <li><a href="h_config_del_skips_del">FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></a>
3316 <li><a href="h_config_disable_config_cmd">FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></a>
3317 <li><a href="h_config_disable_index_locale_dates">FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></a>
3318 <li><a href="h_config_disable_kb_lock">FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></a>
3319 <li><a href="h_config_blank_keymenu">FEATURE: <!--#echo var="FEAT_disable-keymenu"--></a>
3320 <li><a href="h_config_disable_password_caching">FEATURE: <!--#echo var="FEAT_disable-password-caching"--></a>
3321 <li><a href="h_config_disable_password_cmd">FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></a>
3322 <li><a href="h_config_disable_pipes_in_sigs">FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></a>
3323 <li><a href="h_config_disable_pipes_in_templates">FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></a>
3324 <li><a href="h_config_disable_regex">FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
3325 <li><a href="h_config_disable_roles_setup">FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></a>
3326 <li><a href="h_config_disable_roles_sigedit">FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></a>
3327 <li><a href="h_config_disable_roles_templateedit">FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></a>
3328 <li><a href="h_config_input_history">FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></a>
3329 <li><a href="h_config_disable_collate">FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></a>
3330 <li><a href="h_config_disable_shared">FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></a>
3331 <li><a href="h_config_disable_signature_edit">FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></a>
3332 <li><a href="h_config_take_fullname">FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></a>
3333 <li><a href="h_config_take_lastfirst">FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></a>
3334 <li><a href="h_config_disable_reset_disp">FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></a>
3335 <li><a href="h_config_disable_sender">FEATURE: <!--#echo var="FEAT_disable-sender"--></a>
3336 <li><a href="h_config_quell_dead_letter">FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></a>
3337 <li><a href="h_config_quell_flowed_text">FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></a>
3338 <li><a href="h_downgrade_multipart_to_text">FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></a>
3339 <li><a href="h_config_8bit_smtp">FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></a>
3340 <li><a href="h_config_8bit_nntp">FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></a>
3341 <li><a href="h_config_enable_agg_ops">FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></a>
3342 <li><a href="h_config_enable_alt_ed">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></a>
3343 <li><a href="h_config_alt_ed_now">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></a>
3344 <li><a href="h_config_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></a>
3345 <li><a href="h_config_relaxed_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></a>
3346 <li><a href="h_config_compose_bg_post">FEATURE: <!--#echo var="FEAT_enable-background-sending"--></a>
3347 <li><a href="h_config_enable_bounce">FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></a>
3348 <li><a href="h_config_cruise_mode">FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></a>
3349 <li><a href="h_config_cruise_mode_delete">FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></a>
3350 <li><a href="h_config_compose_dsn">FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></a>
3351 <li><a href="h_config_enable_dot_files">FEATURE: <!--#echo var="FEAT_enable-dot-files"--></a>
3352 <li><a href="h_config_enable_lessthan_exit">FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></a>
3353 <li><a href="h_config_fast_recent">FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></a>
3354 <li><a href="h_config_enable_flag">FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></a>
3355 <li><a href="h_config_flag_screen_default">FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></a>
3356 <li><a href="h_config_flag_screen_kw_shortcut">FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></a>
3357 <li><a href="h_config_enable_full_hdr_and_text">FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></a>
3358 <li><a href="h_config_enable_full_hdr">FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></a>
3359 <li><a href="h_config_allow_goto">FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></a>
3360 <li><a href="h_config_enable_dot_folders">FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></a>
3361 <li><a href="h_config_enable_incoming">FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></a>
3362 <li><a href="h_config_enable_incoming_checking">FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></a>
3363 <li><a href="h_config_enable_jump">FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></a>
3364 <li><a href="h_config_show_delay_cue">FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></a>
3365 <li><a href="h_config_mailcap_params">FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></a>
3366 <li><a href="h_config_enable_mouse">FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></a>
3367 <li><a href="h_config_enable_view_addresses">FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></a>
3368 <li><a href="h_config_enable_view_attach">FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></a>
3369 <li><a href="h_config_enable_view_arrows">FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></a>
3370 <li><a href="h_config_enable_view_url">FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></a>
3371 <li><a href="h_config_enable_view_web_host">FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></a>
3372 <li><a href="h_config_enable_mulnewsrcs">FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></a>
3373 <li><a href="h_config_enable_xterm_newmail">FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></a>
3374 <li><a href="h_config_enable_newmail_short_text">FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>
3375 <li><a href="h_config_sub_lists">FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></a>
3376 <li><a href="h_config_enable_y_print">FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></a>
3377 <li><a href="h_config_prefix_editing">FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></a>
3378 <li><a href="h_config_enable_search_and_repl">FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></a>
3379 <li><a href="h_config_sigdashes">FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></a>
3380 <li><a href="h_config_new_thread_blank_subject">FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></a>
3381 <li><a href="h_config_can_suspend">FEATURE: <!--#echo var="FEAT_enable-suspend"--></a>
3382 <li><a href="h_config_enable_tab_complete">FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></a>
3383 <li><a href="h_config_enable_take_export">FEATURE: <!--#echo var="FEAT_enable-take-export"--></a>
3384 <li><a href="h_config_enable_role_take">FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></a>
3385 <li><a href="h_config_tray_icon">FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></a>
3386 <li><a href="h_config_enable_pipe">FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></a>
3387 <li><a href="h_config_verbose_post">FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></a>
3388 <li><a href="h_config_expanded_addrbooks">FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></a>
3389 <li><a href="h_config_expanded_distlists">FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></a>
3390 <li><a href="h_config_expanded_folders">FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></a>
3391 <li><a href="h_config_expose_hidden_config">FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></a>
3392 <li><a href="h_config_expunge_manually">FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></a>
3393 <li><a href="h_config_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></a>
3394 <li><a href="h_config_full_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></a>
3395 <li><a href="h_config_no_fcc_attach">FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></a>
3396 <li><a href="h_config_force_arrow">FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></a>
3397 <li><a href="h_config_forward_as_attachment">FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></a>
3398 <li><a href="h_config_preserve_field">FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></a>
3399 <li><a href="h_config_quell_empty_dirs">FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></a>
3400 <li><a href="h_config_hide_nntp_path">FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></a>
3401 <li><a href="h_config_attach_in_reply">FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></a>
3402 <li><a href="h_config_fcc_on_bounce">FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></a>
3403 <li><a href="h_config_include_header">FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></a>
3404 <li><a href="h_config_auto_include_reply">FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></a>
3405 <li><a href="h_config_incoming_checking_total">FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></a>
3406 <li><a href="h_config_incoming_checking_recent">FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></a>
3407 <li><a href="h_config_add_ldap">FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></a>
3408 <li><a href="h_config_maildrops_preserve_state">FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></a>
3409 <li><a href="h_config_mark_fcc_seen">FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></a>
3410 <li><a href="h_config_mark_for_cc">FEATURE: <!--#echo var="FEAT_mark-for-cc"--></a>
3411 <li><a href="h_config_mulnews_as_typed">FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></a>
3412 <li><a href="h_config_news_uses_recent">FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></a>
3413 <li><a href="h_config_news_cross_deletes">FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></a>
3414 <li><a href="h_config_news_catchup">FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></a>
3415 <li><a href="h_config_post_wo_validation">FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></a>
3416 <li><a href="h_config_read_in_newsrc_order">FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></a>
3417 <li><a href="h_config_nntp_search_uses_overview">FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></a>
3418 <li><a href="h_config_thread_sorts_by_arrival">FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></a>
3419 <li><a href="h_config_expunge_inbox">FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></a>
3420 <li><a href="h_config_expunge_stayopens">FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></a>
3421 <li><a href="h_config_pass_c1_control">FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></a>
3422 <li><a href="h_config_pass_control">FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></a>
3423 <li><a href="h_config_predict_nntp_server">FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></a>
3424 <li><a href="h_config_prefer_plain_text">FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></a>
3425 <li><a href="h_config_preopen_stayopens">FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></a>
3426 <li><a href="h_config_preserve_start_stop">FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></a>
3427 <li><a href="h_config_quell_folder_internal_msg">FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></a>
3428 <li><a href="h_config_quell_checks_comp">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></a>
3429 <li><a href="h_config_quell_checks_comp_inbox">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></a>
3430 <li><a href="h_config_quell_partial">FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></a>
3431 <li><a href="h_config_quell_local_lookup">FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></a>
3432 <li><a href="h_config_ff_between_msgs">FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></a>
3433 <li><a href="h_config_print_from">FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></a>
3434 <li><a href="h_config_print_index">FEATURE: <!--#echo var="FEAT_print-index-enabled"--></a>
3435 <li><a href="h_config_custom_print">FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></a>
3436 <li><a href="h_config_prune_uses_iso">FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></a>
3437 <li><a href="h_config_quell_personal_name_prompt">FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></a>
3438 <li><a href="h_config_quell_ssl_largeblocks">FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></a>
3439 <li><a href="h_config_quell_user_id_prompt">FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></a>
3440 <li><a href="h_config_quit_wo_confirm">FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></a>
3441 <li><a href="h_config_quote_replace_noflow">FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></a>
3442 <li><a href="h_config_next_thrd_wo_confirm">FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></a>
3443 <li><a href="h_config_auto_reply_to">FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></a>
3444 <li><a href="h_config_inbox_no_confirm">FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></a>
3445 <li><a href="h_config_save_aggregates">FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></a>
3446 <li><a href="h_config_save_part_wo_confirm">FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></a>
3447 <li><a href="h_config_save_advances">FEATURE: <!--#echo var="FEAT_save-will-advance"--></a>
3448 <li><a href="h_config_save_wont_delete">FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></a>
3449 <li><a href="h_config_quote_all_froms">FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></a>
3450 <li><a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
3451 <li><a href="h_config_select_wo_confirm">FEATURE: <!--#echo var="FEAT_select-without-confirm"--></a>
3452 <li><a href="h_config_auto_fcc_only">FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></a>
3453 <li><a href="h_config_send_wo_confirm">FEATURE: <!--#echo var="FEAT_send-without-confirm"--></a>
3454 <li><a href="h_config_separate_fold_dir_view">FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></a>
3455 <li><a href="h_config_show_cursor">FEATURE: <!--#echo var="FEAT_show-cursor"--></a>
3456 <li><a href="h_config_textplain_int">FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></a>
3457 <li><a href="h_config_select_in_bold">FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></a>
3458 <li><a href="h_config_show_sort">FEATURE: <!--#echo var="FEAT_show-sort"--></a>
3459 <li><a href="h_config_single_list">FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></a>
3460 <li><a href="h_config_sig_at_bottom">FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></a>
3461 <li><a href="h_config_slash_coll_entire">FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></a>
3462 <li><a href="h_config_sort_fcc_alpha">FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></a>
3463 <li><a href="h_config_sort_save_alpha">FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></a>
3464 <li><a href="h_config_always_spell_check">FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></a>
3465 <li><a href="h_config_winpos_in_config">FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></a>
3466 <li><a href="h_config_strip_sigdashes">FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>
3467 <li><a href="h_config_strip_ws_before_send">FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></a>
3468 <li><a href="h_config_quells_asterisks">FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></a>
3469 <li><a href="h_config_quell_attach_ext_warn">FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></a>
3470 <li><a href="h_config_quell_attach_extra_prompt">FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></a>
3471 <li><a href="h_config_no_bezerk_zone">FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></a>
3472 <li><a href="h_config_quell_charset_warning">FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></a>
3473 <li><a href="h_config_quell_content_id">FEATURE: <!--#echo var="FEAT_quell-content-id"--></a>
3474 <li><a href="h_config_quell_post_prompt">FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></a>
3475 <li><a href="h_config_quell_filtering_done_message">FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></a>
3476 <li><a href="h_config_quell_filtering_messages">FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></a>
3477 <li><a href="h_config_quell_full_hdr_reset">FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></a>
3478 <li><a href="h_config_quell_imap_env">FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></a>
3479 <li><a href="h_config_quell_lock_failure_warnings">FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></a>
3480 <li><a href="h_config_quell_domain_warn">FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></a>
3481 <li><a href="h_config_quell_news_env">FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></a>
3482 <li><a href="h_config_quell_host_after_url">FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></a>
3483 <li><a href="h_config_quell_beeps">FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></a>
3484 <li><a href="h_config_quell_tz_comment">FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></a>
3485 <li><a href="h_config_suppress_user_agent">FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></a>
3486 <li><a href="h_config_tab_checks_recent">FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></a>
3487 <li><a href="h_config_tab_uses_unseen">FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></a>
3488 <li><a href="h_config_tab_new_only">FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></a>
3489 <li><a href="h_config_termcap_wins">FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></a>
3490 <li><a href="h_config_color_thrd_import">FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></a>
3491 <li><a href="h_config_alt_auth">FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></a>
3492 <li><a href="h_config_unsel_wont_advance">FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></a>
3493 <li><a href="h_config_use_current_dir">FEATURE: <!--#echo var="FEAT_use-current-dir"--></a>
3494 <li><a href="h_config_use_fk">FEATURE: <!--#echo var="FEAT_use-function-keys"--></a>
3495 <li><a href="h_config_use_reg_start_for_stayopen">FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></a>
3496 <li><a href="h_config_use_resentto">FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></a>
3497 <li><a href="h_config_use_sender_not_x">FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></a>
3498 <li><a href="h_config_suspend_spawns">FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></a>
3499 <li><a href="h_config_use_system_translation">FEATURE: Use System Translation</a>
3500 <li><a href="h_config_vertical_list">FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></a>
3501 <li><a href="h_config_warn_if_fcc_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></a>
3502 <li><a href="h_config_warn_if_subj_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></a>
3503 <li><a href="h_config_warn_if_no_to_or_cc">FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></a>
3504 <li><a href="h_mainhelp_filtering">Filtering</a>
3505 <li><a href="h_finding_help">Finding more information and requesting help</a>
3506 <li><a href="h_common_flag">Flag Command</a>
3507 <li><a href="h_config_quell_flowed_text">Flowed Text</a>
3508 <li><a href="h_mainhelp_folders">Folders</a>
3509 <li><a href="h_what_are_collections">Folder Collections Explained</a>
3510 <li><a href="h_common_folders">Folder List Command</a>
3511 <li><a href="h_folder_fcc">Folder Select for Fcc Explained</a>
3512 <li><a href="h_folder_save">Folder Select for Save Explained</a>
3513 <li><a href="h_folder_server_syntax">Folder Server Name Syntax</a>
3514 <li><a href="h_config_change_your_from">From Address, Changing</a>
3515 <li><a href="main_menu_tx">GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</a>
3516 <li><a href="h_pine_for_windows">GETTING HELP IN ALPINE</a>
3517 <li><a href="h_common_goto">Goto Command</a>
3518 <li><a href="h_common_hdrmode">HdrMode Command</a>
3519 <li><a href="h_mainhelp_pinehelp">Help</a>
3520 <li><a href="h_special_help_nav">Help Text Navigation Explained</a>
3521 <li><a href="h_folder_maint">Help for Folder List</a>
3522 <li><a href="h_valid_folder_names">IMAP</a>
3523 <li><a href="h_ge_import">Import File Selection</a>
3524 <li><a href="h_mainhelp_index">Index of Messages</a>
3525 <li><a href="h_composer_ins_m">INSERT MESSAGE</a>
3526 <li><a href="h_composer_ins">INSERT TEXT FILE</a>
3527 <li><a href="h_address_format">INTERNET EMAIL ADDRESS FORMAT</a>
3528 <li><a href="h_info_on_mbox">Information on mbox driver</a>
3529 <li><a href="h_mainhelp_intro">Introduction</a>
3530 <li><a href="h_main_journal">Journal Command</a>
3531 <li><a href="h_common_jump">Jump Command</a>
3532 <li><a href="h_compose_justify">Justify Command</a>
3533 <li><a href="h_main_kblock">Keyboard Lock Command</a>
3534 <li><a href="h_mainhelp_keywords">Keywords (or Flags, or Labels)</a>
3535 <li><a href="h_mainhelp_ldap">LDAP</a>
3536 <li><a href="h_config_ldap_opts_tls">LDAP FEATURE: Attempt-TLS-On-Connection</a>
3537 <li><a href="h_config_ldap_opts_nosub">LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</a>
3538 <li><a href="h_config_ldap_opts_rhs">LDAP FEATURE: Lookup-Addrbook-Contents</a>
3539 <li><a href="h_config_ldap_opts_tlsmust">LDAP FEATURE: Require-TLS-On-Connection</a>
3540 <li><a href="h_config_ldap_opts_ref">LDAP FEATURE: Save-Search-Criteria-Not-Result</a>
3541 <li><a href="h_config_ldap_opts_impl">LDAP FEATURE: Use-Implicitly-From-Composer</a>
3542 <li><a href="h_config_ldap_binddn">LDAP OPTION: Bind-DN</a>
3543 <li><a href="h_config_ldap_cust">LDAP OPTION: Custom-Search-Filter</a>
3544 <li><a href="h_config_ldap_email_attr">LDAP OPTION: EmailAttribute</a>
3545 <li><a href="h_config_ldap_gn_attr">LDAP OPTION: GivennameAttribute</a>
3546 <li><a href="h_config_ldap_server">LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></a>
3547 <li><a href="h_config_ldap_cn_attr">LDAP OPTION: NameAttribute</a>
3548 <li><a href="h_config_ldap_nick">LDAP OPTION: Nickname</a>
3549 <li><a href="h_config_ldap_port">LDAP OPTION: Port</a>
3550 <li><a href="h_config_ldap_base">LDAP OPTION: Search-Base</a>
3551 <li><a href="h_config_ldap_searchrules">LDAP OPTION: Search-Rule</a>
3552 <li><a href="h_config_ldap_searchtypes">LDAP OPTION: Search-Type</a>
3553 <li><a href="h_config_ldap_size">LDAP OPTION: Sizelimit</a>
3554 <li><a href="h_config_ldap_sn_attr">LDAP OPTION: SurnameAttribute</a>
3555 <li><a href="h_config_ldap_time">LDAP OPTION: Timelimit</a>
3556 <li><a href="h_ldap_view">LDAP Response View Explained</a>
3557 <li><a href="h_maildrop">Mail Drop: What is it?</a>
3558 <li><a href="h_mainhelp_mainmenu">MAIN MENU</a>
3559 <li><a href="h_mail_index">MESSAGE INDEX COMMANDS</a>
3560 <li><a href="h_mail_view">MESSAGE TEXT SCREEN</a>
3561 <li><a href="h_compose_markcutpaste">Mark, Cut and Paste Commands</a>
3562 <li><a href="h_common_index">Message Index Command</a>
3563 <li><a href="h_mainhelp_mouse">Mouse</a>
3564 <li><a href="h_mainhelp_aggops">Multiple Message Operations</a>
3565 <li><a href="new_user_greeting">NEW USER GREETING</a>
3566 <li><a href="new_version_greeting">NEW VERSION GREETING</a>
3567 <li><a href="h_mainhelp_readingnews">News Reading</a>
3568 <li><a href="h_folder_subscribe">Newsgroup Subcribe Screen explained</a>
3569 <li><a href="h_folder_postnews">Newsgroup selecting for Posting explained</a>
3570 <li><a href="h_common_nextnew">NextNew Command</a>
3571 <li><a href="h_abook_select_nick">Nickname Selection Explained</a>
3572 <li><a href="h_mainhelp_readingnews">NNTP</a>
3573 <li><a href="h_config_address_book">OPTION: <!--#echo var="VAR_address-book"--></a>
3574 <li><a href="h_config_abook_formats">OPTION: <!--#echo var="VAR_addressbook-formats"--></a>
3575 <li><a href="h_config_ab_sort_rule">OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></a>
3576 <li><a href="h_config_alt_addresses">OPTION: <!--#echo var="VAR_alt-addresses"--></a>
3577 <li><a href="h_config_active_msg_interval">OPTION: <!--#echo var="VAR_busy-cue-rate"--></a>
3578 <li><a href="h_config_color_style">OPTION: Color Style</a>
3579 <li><a href="h_config_wordseps">OPTION: <!--#echo var="VAR_composer-word-separators"--></a>
3580 <li><a href="h_config_composer_wrap_column">OPTION: <!--#echo var="VAR_composer-wrap-column"--></a>
3581 <li><a href="h_config_index_color_style">OPTION: <!--#echo var="VAR_current-indexline-style"--></a>
3582 <li><a href="h_config_cursor_style">OPTION: Cursor Style</a>
3583 <li><a href="h_config_custom_hdrs">OPTION: <!--#echo var="VAR_customized-hdrs"--></a>
3584 <li><a href="h_config_deadlets">OPTION: <!--#echo var="VAR_dead-letter-files"--></a>
3585 <li><a href="h_config_comp_hdrs">OPTION: <!--#echo var="VAR_default-composer-hdrs"--></a>
3586 <li><a href="h_config_default_fcc">OPTION: <!--#echo var="VAR_default-fcc"--></a>
3587 <li><a href="h_config_def_save_folder">OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></a>
3588 <li><a href="h_config_disable_auths">OPTION: <!--#echo var="VAR_disable-these-authenticators"--></a>
3589 <li><a href="h_config_disable_drivers">OPTION: <!--#echo var="VAR_disable-these-drivers"--></a>
3590 <li><a href="h_config_char_set">OPTION: Display Character Set</a>
3591 <li><a href="h_config_display_filters">OPTION: <!--#echo var="VAR_display-filters"--></a>
3592 <li><a href="h_config_download_cmd">OPTION: <!--#echo var="VAR_download-command"--></a>
3593 <li><a href="h_config_download_prefix">OPTION: <!--#echo var="VAR_download-command-prefix"--></a>
3594 <li><a href="h_config_editor">OPTION: <!--#echo var="VAR_editor"--></a>
3595 <li><a href="h_config_empty_hdr_msg">OPTION: <!--#echo var="VAR_empty-header-message"--></a>
3596 <li><a href="h_config_fcc_rule">OPTION: <!--#echo var="VAR_fcc-name-rule"--></a>
3597 <li><a href="h_config_file_dir">OPTION: File Directory</a>
3598 <li><a href="h_config_folder_spec">OPTION: <!--#echo var="VAR_folder-collections"--></a>
3599 <li><a href="h_config_reopen_rule">OPTION: <!--#echo var="VAR_folder-reopen-rule"--></a>
3600 <li><a href="h_config_fld_sort_rule">OPTION: <!--#echo var="VAR_folder-sort-rule"--></a>
3601 <li><a href="h_config_font_char_set">OPTION: Font Character Set</a>
3602 <li><a href="h_config_font_name">OPTION: Font Name</a>
3603 <li><a href="h_config_font_size">OPTION: Font Size</a>
3604 <li><a href="h_config_font_style">OPTION: Font Style</a>
3605 <li><a href="h_config_form_folder">OPTION: <!--#echo var="VAR_form-letter-folder"--></a>
3606 <li><a href="h_config_glob_addrbook">OPTION: <!--#echo var="VAR_global-address-book"--></a>
3607 <li><a href="h_config_goto_default">OPTION: <!--#echo var="VAR_goto-default-rule"--></a>
3608 <li><a href="h_config_header_general_color">OPTION: Header General Color</a>
3609 <li><a href="h_config_image_viewer">OPTION: <!--#echo var="VAR_image-viewer"--></a>
3610 <li><a href="h_config_inbox_path">OPTION: <!--#echo var="VAR_inbox-path"--></a>
3611 <li><a href="h_config_archived_folders">OPTION: <!--#echo var="VAR_incoming-archive-folders"--></a>
3612 <li><a href="h_config_psleep">OPTION: <!--#echo var="VAR_mailcap-check-interval"--></a>
3613 <li><a href="h_config_incoming_interv">OPTION: <!--#echo var="VAR_incoming-check-interval"--></a>
3614 <li><a href="h_config_incoming_second_interv">OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></a>
3615 <li><a href="h_config_incoming_list">OPTION: <!--#echo var="VAR_incoming-check-list"--></a>
3616 <li><a href="h_config_incoming_timeo">OPTION: <!--#echo var="VAR_incoming-check-timeout"--></a>
3617 <li><a href="h_config_incoming_folders">OPTION: <!--#echo var="VAR_incoming-folders"--></a>
3618 <li><a href="h_config_inc_startup">OPTION: <!--#echo var="VAR_incoming-startup-rule"--></a>
3619 <li><a href="h_config_incunseen_color">OPTION: Incoming Unseen Color</a>
3620 <li><a href="h_config_index_arrow_color">OPTION: Index Arrow Color</a>
3621 <li><a href="h_config_index_color">OPTION: Index Colors</a>
3622 <li><a href="h_config_index_format">OPTION: <!--#echo var="VAR_index-format"--></a>
3623 <li><a href="h_config_index_from_color">OPTION: Index From Color</a>
3624 <li><a href="h_config_index_opening_color">OPTION: Index Opening Color</a>
3625 <li><a href="h_config_index_pri_color">OPTION: Index Priority Symbol Colors</a>
3626 <li><a href="h_config_index_subject_color">OPTION: Index Subject Color</a>
3627 <li><a href="h_config_init_cmd_list">OPTION: <!--#echo var="VAR_initial-keystroke-list"--></a>
3628 <li><a href="h_config_key_char_set">OPTION: Keyboard Character Set</a>
3629 <li><a href="h_config_keylabel_color">OPTION: KeyLabel Color</a>
3630 <li><a href="h_config_keyname_color">OPTION: KeyName Color</a>
3631 <li><a href="h_config_keywords">OPTION: <!--#echo var="VAR_keywords"--></a>
3632 <li><a href="h_config_kw_color">OPTION: Keyword Colors</a>
3633 <li><a href="h_config_kw_braces">OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></a>
3634 <li><a href="h_config_prune_date">OPTION: <!--#echo var="VAR_last-time-prune-questioned"--></a>
3635 <li><a href="h_config_last_vers">OPTION: <!--#echo var="VAR_last-version-used"--></a>
3636 <li><a href="h_config_literal_sig">OPTION: <!--#echo var="VAR_literal-signature"--></a>
3637 <li><a href="h_config_mailcheck">OPTION: <!--#echo var="VAR_mail-check-interval"--></a>
3638 <li><a href="h_config_mailchecknoncurr">OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></a>
3639 <li><a href="h_config_mailcap_path">OPTION: <!--#echo var="VAR_mailcap-search-path"--></a>
3640 <li><a href="h_config_maildropcheck">OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></a>
3641 <li><a href="h_config_maxremstream">OPTION: <!--#echo var="VAR_max-remote-connections"--></a>
3642 <li><a href="h_config_metamsg_color">OPTION: Meta-Message Color</a>
3643 <li><a href="h_config_mimetype_path">OPTION: <!--#echo var="VAR_mimetype-search-path"--></a>
3644 <li><a href="h_config_new_ver_quell">OPTION: <!--#echo var="VAR_new-version-threshold"--></a>
3645 <li><a href="h_config_fifopath">OPTION: NewMail FIFO Path</a>
3646 <li><a href="h_config_newmailwidth">OPTION: <!--#echo var="VAR_newmail-window-width"--></a>
3647 <li><a href="h_config_news_active">OPTION: <!--#echo var="VAR_news-active-file-path"--></a>
3648 <li><a href="h_config_news_spec">OPTION: <!--#echo var="VAR_news-collections"--></a>
3649 <li><a href="h_config_news_spool">OPTION: <!--#echo var="VAR_news-spool-directory"--></a>
3650 <li><a href="h_config_newsrc_path">OPTION: <!--#echo var="VAR_newsrc-path"--></a>
3651 <li><a href="h_config_nntprange">OPTION: <!--#echo var="VAR_nntp-range"--></a>
3652 <li><a href="h_config_nntp_server">OPTION: <!--#echo var="VAR_nntp-server"--></HEAD></a>
3653 <li><a href="h_config_normal_color">OPTION: Normal Color</a>
3654 <li><a href="h_config_opening_sep">OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></a>
3655 <li><a href="h_config_oper_dir">OPTION: <!--#echo var="VAR_operating-dir"--></a>
3656 <li><a href="h_config_pat_old">OPTION: Patterns</a>
3657 <li><a href="h_config_pat_filts">OPTION: <!--#echo var="VAR_patterns-filters2"--></a>
3658 <li><a href="h_config_pat_other">OPTION: <!--#echo var="VAR_patterns-other"--></a>
3659 <li><a href="h_config_pat_roles">OPTION: <!--#echo var="VAR_patterns-roles"--></a>
3660 <li><a href="h_config_pat_scores">OPTION: <!--#echo var="VAR_patterns-scores2"--></a>
3661 <li><a href="h_config_pers_name">OPTION: <!--#echo var="VAR_personal-name"--></a>
3662 <li><a href="h_config_print_cat">OPTION: <!--#echo var="VAR_personal-print-category"--></a>
3663 <li><a href="h_config_print_command">OPTION: <!--#echo var="VAR_personal-print-command"--></a>
3664 <li><a href="h_config_post_char_set">OPTION: <!--#echo var="VAR_posting-character-set"--></a>
3665 <li><a href="h_config_postponed_folder">OPTION: <!--#echo var="VAR_postponed-folder"--></a>
3666 <li><a href="h_config_print_font_char_set">OPTION: Print-Font-Char-Set</a>
3667 <li><a href="h_config_print_font_name">OPTION: Print-Font-Name</a>
3668 <li><a href="h_config_print_font_size">OPTION: Print-Font-Size</a>
3669 <li><a href="h_config_print_font_style">OPTION: Print-Font-Style</a>
3670 <li><a href="h_config_printer">OPTION: Printer</a>
3671 <li><a href="h_config_prompt_color">OPTION: Prompt Color</a>
3672 <li><a href="h_config_pruned_folders">OPTION: <!--#echo var="VAR_pruned-folders"--></a>
3673 <li><a href="h_config_pruning_rule">OPTION: <!--#echo var="VAR_pruning-rule"--></a>
3674 <li><a href="h_config_quote_color">OPTION: Quote Colors</a>
3675 <li><a href="h_config_quote_replace_string">OPTION: <!--#echo var="VAR_quote-replace-string"--></a>
3676 <li><a href="h_config_quote_suppression">OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></a>
3677 <li><a href="h_config_read_message_folder">OPTION: <!--#echo var="VAR_read-message-folder"--></a>
3678 <li><a href="h_config_remote_abook_history">OPTION: <!--#echo var="VAR_remote-abook-history"--></a>
3679 <li><a href="h_config_abook_metafile">OPTION: <!--#echo var="VAR_remote-abook-metafile"--></a>
3680 <li><a href="h_config_remote_abook_validity">OPTION: <!--#echo var="VAR_remote-abook-validity"--></a>
3681 <li><a href="h_config_reply_indent_string">OPTION: <!--#echo var="VAR_reply-indent-string"--></a>
3682 <li><a href="h_config_reply_intro">OPTION: <!--#echo var="VAR_reply-leadin"--></a>
3683 <li><a href="h_config_reverse_color">OPTION: Reverse Color</a>
3684 <li><a href="h_config_rshcmd">OPTION: <!--#echo var="VAR_rsh-command"--></a>
3685 <li><a href="h_config_rsh_open_timeo">OPTION: <!--#echo var="VAR_rsh-open-timeout"--></a>
3686 <li><a href="h_config_rshpath">OPTION: <!--#echo var="VAR_rsh-path"--></a>
3687 <li><a href="h_config_saved_msg_name_rule">OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></a>
3688 <li><a href="h_config_scroll_margin">OPTION: <!--#echo var="VAR_scroll-margin"--></a>
3689 <li><a href="h_config_slctbl_color">OPTION: Selectable Item Color</a>
3690 <li><a href="h_config_sending_filter">OPTION: <!--#echo var="VAR_sending-filters"--></a>
3691 <li><a href="h_config_sendmail_path">OPTION: <!--#echo var="VAR_sendmail-path"--></a>
3692 <li><a href="h_config_signature_color">OPTION: Signature Color</a>
3693 <li><a href="h_config_signature_file">OPTION: <!--#echo var="VAR_signature-file"--></a>
3694 <li><a href="h_config_smtp_server">OPTION: <!--#echo var="VAR_smtp-server"--></a>
3695 <li><a href="h_config_sort_key">OPTION: <!--#echo var="VAR_sort-key"--></a>
3696 <li><a href="h_config_speller">OPTION: <!--#echo var="VAR_speller"--></a>
3697 <li><a href="h_config_sshcmd">OPTION: <!--#echo var="VAR_ssh-command"--></a>
3698 <li><a href="h_config_ssh_open_timeo">OPTION: <!--#echo var="VAR_ssh-open-timeout"--></a>
3699 <li><a href="h_config_sshpath">OPTION: <!--#echo var="VAR_ssh-path"--></a>
3700 <li><a href="h_config_status_color">OPTION: Status Color</a>
3701 <li><a href="h_config_status_msg_delay">OPTION: <!--#echo var="VAR_status-message-delay"--></a>
3702 <li><a href="h_config_permlocked">OPTION: <!--#echo var="VAR_stay-open-folders"--></a>
3703 <li><a href="h_config_tcp_open_timeo">OPTION: <!--#echo var="VAR_tcp-open-timeout"--></a>
3704 <li><a href="h_config_tcp_query_timeo">OPTION: <!--#echo var="VAR_tcp-query-timeout"--></a>
3705 <li><a href="h_config_tcp_readwarn_timeo">OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></a>
3706 <li><a href="h_config_tcp_writewarn_timeo">OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></a>
3707 <li><a href="h_config_thread_disp_style">OPTION: <!--#echo var="VAR_threading-display-style"--></a>
3708 <li><a href="h_config_thread_exp_char">OPTION: <!--#echo var="VAR_threading-expanded-character"--></a>
3709 <li><a href="h_config_thread_index_style">OPTION: <!--#echo var="VAR_threading-index-style"--></a>
3710 <li><a href="h_config_thread_indicator_char">OPTION: <!--#echo var="VAR_threading-indicator-character"--></a>
3711 <li><a href="h_config_thread_lastreply_char">OPTION: <!--#echo var="VAR_threading-lastreply-character"--></a>
3712 <li><a href="h_config_title_color">OPTION: Title Color</a>
3713 <li><a href="h_config_titleclosed_color">OPTION: Title Closed Color</a>
3714 <li><a href="h_config_titlebar_color_style">OPTION: <!--#echo var="VAR_titlebar-color-style"--></a>
3715 <li><a href="h_config_unk_char_set">OPTION: <!--#echo var="VAR_unknown-character-set"--></a>
3716 <li><a href="h_config_upload_cmd">OPTION: <!--#echo var="VAR_upload-command"--></a>
3717 <li><a href="h_config_upload_prefix">OPTION: <!--#echo var="VAR_upload-command-prefix"--></a>
3718 <li><a href="h_config_browser">OPTION: <!--#echo var="VAR_url-viewers"--></a>
3719 <li><a href="h_config_domain_name">OPTION: <!--#echo var="VAR_use-only-domain-name"--></a>
3720 <li><a href="h_config_user_dom">OPTION: <!--#echo var="VAR_user-domain"--></a>
3721 <li><a href="h_config_user_id">OPTION: <!--#echo var="VAR_user-id"--></a>
3722 <li><a href="h_config_user_input_timeo">OPTION: <!--#echo var="VAR_user-input-timeout"--></a>
3723 <li><a href="h_config_viewer_headers">OPTION: <!--#echo var="VAR_viewer-hdrs"--></a>
3724 <li><a href="h_config_customhdr_pattern">OPTION: Viewer Header Color Pattern</a>
3725 <li><a href="h_config_customhdr_color">OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></a>
3726 <li><a href="h_config_viewer_margin_left">OPTION: <!--#echo var="VAR_viewer-margin-left"--></a>
3727 <li><a href="h_config_viewer_margin_right">OPTION: <!--#echo var="VAR_viewer-margin-right"--></a>
3728 <li><a href="h_config_viewer_overlap">OPTION: <!--#echo var="VAR_viewer-overlap"--></a>
3729 <li><a href="h_config_window_position">OPTION: Window-Position</a>
3730 <li><a href="h_mainhelp_patterns">Patterns</a>
3731 <li><a href="h_config_role_abookfrom">PATTERNS: Address in Address Book</a>
3732 <li><a href="h_config_role_age">PATTERNS: Age Interval</a>
3733 <li><a href="h_config_role_alltextpat">PATTERNS: AllText Pattern</a>
3734 <li><a href="h_config_role_bom">PATTERNS: Beginning of Month</a>
3735 <li><a href="h_config_role_boy">PATTERNS: Beginning of Year</a>
3736 <li><a href="h_config_role_bodytextpat">PATTERNS: BodyText Pattern</a>
3737 <li><a href="h_config_role_cat_cmd">PATTERNS: Categorizer Command</a>
3738 <li><a href="h_config_role_cat_cmd_example">PATTERNS: Categorizer Command Example</a>
3739 <li><a href="h_config_role_ccpat">PATTERNS: Cc Pattern</a>
3740 <li><a href="h_config_role_cat_limit">PATTERNS: Character Limit</a>
3741 <li><a href="h_config_role_charsetpat">PATTERNS: Character Set Pattern</a>
3742 <li><a href="h_config_role_comment">PATTERNS: Comment</a>
3743 <li><a href="h_config_role_fldr_type">PATTERNS: Current Folder Type</a>
3744 <li><a href="h_config_role_cat_status">PATTERNS: Exit Status Interval</a>
3745 <li><a href="h_config_role_arbpat">PATTERNS: Extra Headers Pattern</a>
3746 <li><a href="h_config_role_frompat">PATTERNS: From Pattern</a>
3747 <li><a href="h_config_role_keywordpat">PATTERNS: Keyword Pattern</a>
3748 <li><a href="h_config_role_stat_ans">PATTERNS: Message Answered Status</a>
3749 <li><a href="h_config_role_stat_del">PATTERNS: Message Deleted Status</a>
3750 <li><a href="h_config_role_stat_imp">PATTERNS: Message Important Status</a>
3751 <li><a href="h_config_role_stat_new">PATTERNS: Message New Status</a>
3752 <li><a href="h_config_role_stat_recent">PATTERNS: Message Recent Status</a>
3753 <li><a href="h_config_role_newspat">PATTERNS: News Pattern</a>
3754 <li><a href="h_config_role_nick">PATTERNS: Nickname</a>
3755 <li><a href="h_config_role_particpat">PATTERNS: Participant Pattern</a>
3756 <li><a href="h_config_role_stat_8bitsubj">PATTERNS: Raw 8-bit in Subject</a>
3757 <li><a href="h_config_role_recippat">PATTERNS: Recipient Pattern</a>
3758 <li><a href="h_config_role_scorei">PATTERNS: Score Interval</a>
3759 <li><a href="h_config_role_senderpat">PATTERNS: Sender Pattern</a>
3760 <li><a href="h_config_role_size">PATTERNS: Size Interval</a>
3761 <li><a href="h_config_role_subjpat">PATTERNS: Subject Pattern</a>
3762 <li><a href="h_config_role_topat">PATTERNS: To Pattern</a>
3763 <li><a href="h_config_filt_opts_nonterm">PATTERNS FEATURE: Dont-Stop-Even-if-Rule-Matches</a>
3764 <li><a href="h_config_filt_opts_notdel">PATTERNS FEATURE: Move-Only-if-Not-Deleted</a>
3765 <li><a href="h_config_filt_opts_sentdate">PATTERNS FEATURE: Use-Date-Header-For-Age</a>
3766 <li><a href="h_config_filt_rule_type">PATTERNS FILTER ACTION: Filter Action</a>
3767 <li><a href="h_config_filter_kw_clr">PATTERNS FILTER ACTION: Clear These Keywords</a>
3768 <li><a href="h_config_filt_stat_ans">PATTERNS FILTER ACTION: Set Answered Status</a>
3769 <li><a href="h_config_filt_stat_del">PATTERNS FILTER ACTION: Set Deleted Status</a>
3770 <li><a href="h_config_filt_stat_imp">PATTERNS FILTER ACTION: Set Important Status</a>
3771 <li><a href="h_config_filt_stat_new">PATTERNS FILTER ACTION: Set New Status</a>
3772 <li><a href="h_config_filter_kw_set">PATTERNS FILTER ACTION: Set These Keywords</a>
3773 <li><a href="h_config_incol">PATTERNS INDEXCOLOR ACTION: Index Line Color</a>
3774 <li><a href="h_config_set_index_format">PATTERNS OTHER ACTION: Set Index Format</a>
3775 <li><a href="h_config_perfolder_sort">PATTERNS OTHER ACTION: Set Sort Order</a>
3776 <li><a href="h_config_other_startup">PATTERNS OTHER ACTION: Set Startup Rule</a>
3777 <li><a href="h_config_role_inick">PATTERNS ROLE ACTION: Initialize Values From Role</a>
3778 <li><a href="h_config_role_setfcc">PATTERNS ROLE ACTION: Set Fcc</a>
3779 <li><a href="h_config_role_setfrom">PATTERNS ROLE ACTION: Set From</a>
3780 <li><a href="h_config_role_setlitsig">PATTERNS ROLE ACTION: Set Literal Signature</a>
3781 <li><a href="h_config_role_setotherhdr">PATTERNS ROLE ACTION: Set Other Headers</a>
3782 <li><a href="h_config_role_setreplyto">PATTERNS ROLE ACTION: Set Reply-To</a>
3783 <li><a href="h_config_role_setsig">PATTERNS ROLE ACTION: Set Signature</a>
3784 <li><a href="h_config_role_settempl">PATTERNS ROLE ACTION: Set Template</a>
3785 <li><a href="h_config_role_usenntp">PATTERNS ROLE ACTION: Use NNTP Server</a>
3786 <li><a href="h_config_role_usesmtp">PATTERNS ROLE ACTION: Use SMTP Server</a>
3787 <li><a href="h_config_role_scoreval">PATTERNS SCORE ACTION: Score Value</a>
3788 <li><a href="h_config_role_scorehdrtok">PATTERNS SCORE ACTION: Score Value From Header</a>
3789 <li><a href="h_config_role_composeuse">PATTERNS USE: Compose Use</a>
3790 <li><a href="h_config_role_forwarduse">PATTERNS USE: Forward Use</a>
3791 <li><a href="h_config_role_replyuse">PATTERNS USE: Reply Use</a>
3792 <li><a href="h_pipe_command">Pipe Command SubOptions</a>
3793 <li><a href="h_common_pipe">Pipe Command</a>
3794 <li><a href="h_valid_folder_names">POP</a>
3795 <li><a href="h_common_postpone">Postpone Command</a>
3796 <li><a href="h_common_print">Print Command</a>
3797 <li><a href="h_mainhelp_readingnews">Reading News</a>
3798 <li><a href="h_news">RELEASE NOTES for Alpine</a>
3799 <li><a href="h_mainhelp_roles">Roles</a>
3800 <li><a href="h_role_select">ROLES SCREEN</a>
3801 <li><a href="h_compose_readfile">Read File Command</a>
3802 <li><a href="h_mainhelp_reading">Reading Messages</a>
3803 <li><a href="h_main_release_notes">Release Notes Command</a>
3804 <li><a href="h_common_reply">Reply and Forward Commands</a>
3805 <li><a href="h_compose_richhdr">Rich Header Command</a>
3806 <li><a href="h_common_role">Role Command</a>
3807 <li><a href="h_mainhelp_smime">S/MIME</a>
3808 <li><a href="h_index_cmd_select">Searching for Messages</a>
3809 <li><a href="h_address_display">SEARCH RESULTS INDEX</a>
3810 <li><a href="h_address_select">SEARCH RESULTS INDEX</a>
3811 <li><a href="h_simple_index">SELECT POSTPONED MESSAGE</a>
3812 <li><a href="h_abook_config">SETUP ADDRESS BOOKS SCREEN</a>
3813 <li><a href="h_collection_maint">SETUP COLLECTION LIST screen</a>
3814 <li><a href="h_color_setup">SETUP COLOR COMMANDS</a>
3815 <li><a href="h_direct_config">SETUP LDAP DIRECTORY SERVERS SCREEN</a>
3816 <li><a href="h_rules_roles">SETUP ROLES SCREEN</a>
3817 <li><a href="h_rules_incols">SETUP INDEX COLORS SCREEN</a>
3818 <li><a href="h_rules_filter">SETUP FILTERING SCREEN</a>
3819 <li><a href="h_rules_score">SETUP SCORING SCREEN</a>
3820 <li><a href="h_common_save">Save and Export Commands</a>
3821 <li><a href="h_mainhelp_securing">Securing Your Alpine Session</a>
3822 <li><a href="h_index_cmd_select">Selecting: Select and WhereIs/Select</a>
3823 <li><a href="h_compose_send">Send Command</a>
3824 <li><a href="h_folder_server_syntax">Server Name Syntax</a>
3825 <li><a href="h_main_setup">Setup Command</a>
3826 <li><a href="X-Alpine-Config:">Show Supported Options in this Alpine</a>
3827 <li><a href="h_composer_sigedit">Signature Editor Commands Explained</a>
3828 <li><a href="h_simple_text_view">Simple Text View Screen Explained</a>
3829 <li><a href="h_mainhelp_smime">S/MIME</a>
3830 <li><a href="h_config_smime_dont_do_smime">S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></a>
3831 <li><a href="h_config_smime_encrypt_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></a>
3832 <li><a href="h_config_smime_remember_passphrase">S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></a>
3833 <li><a href="h_config_smime_sign_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></a>
3834 <li><a href="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></a>
3835 <li><a href="h_config_smime_cacertcon">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></a>
3836 <li><a href="h_config_smime_cacertdir">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></a>
3837 <li><a href="h_config_smime_privkeycon">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-container"--></a>
3838 <li><a href="h_config_smime_privkeydir">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-directory"--></a>
3839 <li><a href="h_config_smime_pubcertcon">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-container"--></a>
3840 <li><a href="h_config_smime_pubcertdir">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></a>
3841 <li><a href="h_config_smime_transfer_cacert_to_con">S/MIME: Transfer CA Certs to Container</a>
3842 <li><a href="h_config_smime_transfer_cacert_to_dir">S/MIME: Transfer CA Certs to Directory</a>
3843 <li><a href="h_config_smime_transfer_priv_to_con">S/MIME: Transfer Private Keys to Container</a>
3844 <li><a href="h_config_smime_transfer_priv_to_dir">S/MIME: Transfer Private Keys to Directory</a>
3845 <li><a href="h_config_smime_transfer_pub_to_con">S/MIME: Transfer Public Certs to Container</a>
3846 <li><a href="h_config_smime_transfer_pub_to_dir">S/MIME: Transfer Public Certs to Directory</a>
3847 <li><a href="h_config_smime_public_certificates">S/MIME: Manage Public Certificates</a>
3848 <li><a href="h_config_smime_private_keys">S/MIME: Manage Private Keys</a>
3849 <li><a href="h_config_smime_certificate_authorities">S/MIME: Manage Certificate Authorities</a>
3850 <li><a href="h_index_cmd_sort">Sort Command</a>
3851 <li><a href="h_compose_spell">Spell Check Command</a>
3852 <li><a href="h_common_suspend">Suspend Command</a>
3853 <li><a href="h_compose_addrcomplete">THE MESSAGE COMPOSER'S ADDRESS COMPLETION</a>
3854 <li><a href="h_composer_attachment">THE MESSAGE COMPOSER'S ATTCHMNT FIELD</a>
3855 <li><a href="h_composer_bcc">THE MESSAGE COMPOSER'S BCC FIELD</a>
3856 <li><a href="h_composer_cc">THE MESSAGE COMPOSER'S CC FIELD</a>
3857 <li><a href="h_composer_from">THE MESSAGE COMPOSER'S FROM FIELD</a>
3858 <li><a href="h_composer_lcc">THE MESSAGE COMPOSER'S LCC FIELD</a>
3859 <li><a href="h_composer_news">THE MESSAGE COMPOSER'S NEWSGRPS LINE</a>
3860 <li><a href="h_composer_reply_to">THE MESSAGE COMPOSER'S REPLY-TO FIELD</a>
3861 <li><a href="h_composer_to">THE MESSAGE COMPOSER'S TO FIELD</a>
3862 <li><a href="h_abook_opened">THE ALPINE ADDRESS BOOK</a>
3863 <li><a href="h_abook_select_nicks_take">Take Address Nickname Selection Explained</a>
3864 <li><a href="h_takeaddr_screen">Take Address Screen Explained</a>
3865 <li><a href="h_common_take">TakeAddr Command</a>
3866 <li><a href="h_mainhelp_status">Titlebar Line</a>
3867 <li><a href="h_index_tokens">Tokens for Index and Replying</a>
3868 <li><a href="h_config_usenone_color">Use None Color</a>
3869 <li><a href="h_config_usenormal_color">Use Normal Color</a>
3870 <li><a href="h_config_usetransparent_color">Use Transparent Color</a>
3871 <li><a href="h_whatis_vcard">VCARD EXPLAINED</a>
3872 <li><a href="h_view_cmd_hilite">View Hilite and Next item/Previous item</a>
3873 <li><a href="h_view_cmd_viewattch">ViewAttch Command</a>
3874 <li><a href="h_index_cmd_whereis">WhereIs Command</a>
3875 <li><a href="h_view_cmd_whereis">WhereIs Command</a>
3876 <li><a href="h_index_cmd_zoom">ZoomMode Command</a>
3877 <li><a href="h_config_browser_xterm"><!--#echo var="VAR_url-viewers"--> and X windows applications</a>
3878 </UL>
3880 <P>
3881 <End of Help Index>
3882 </BODY>
3883 </HTML>
3886 ============== h_config_remote_config =============
3887 <HTML>
3888 <HEAD>
3889 <TITLE>Remote Configuration</TITLE>
3890 </HEAD>
3891 <BODY>
3892 <H1>Remote Configuration</H1>
3894 You may use the command line argument "-p pinerc" to tell
3895 Alpine to use a non-default configuration file.
3896 There are two types of storage for configuration information.
3897 <EM>Local</EM> configuration files are used by default.
3898 These are just regular files on the UNIX system or on the PC.
3899 The file "<CODE>.pinerc</CODE>" is the default for Unix Alpine and the
3900 file "<CODE>PINERC</CODE>" is the default for PC-Alpine.
3901 <EM>Remote</EM> configuration folders are stored on an IMAP server.
3902 The advantage of using a remote configuration is that the same information
3903 may be accessed from multiple platforms.
3904 For example, if you use one computer at work and another at home, the same
3905 configuration could be used from both places.
3906 A configuration change from one place would be seen in both places.
3907 To use a remote configuration you simply give a
3908 <A HREF="h_valid_folder_names">remote folder name</A>
3909 as the argument to the "-p" command line option.
3910 The command line might look something like:
3911 <P>
3912 <CENTER><SAMP>pine -p {my.imap.server}remote_pinerc</SAMP></CENTER>
3913 <P>
3914 If there are special characters in the command shell you use, you may need to
3915 quote the last argument (to protect the curly braces from the shell).
3916 The command might look like:
3917 <P>
3918 <CENTER><SAMP>pine -p "{my.imap.server}remote_pinerc"</SAMP></CENTER>
3919 <P>
3920 You should choose a folder name for a folder that does not yet exist.
3921 It will be created containing an empty configuration.
3922 Do not use a folder that you wish to store regular mail messages in.
3923 <P>
3924 The Setup/RemoteConfigSetup command will help you convert from a local
3925 configuration to a remote configuration.
3926 It will create a remote configuration for you and copy your current local
3927 configuration to it.
3928 It will also help you convert local address books into remote address books
3929 and local signature files into literal signatures contained in the
3930 remote configuration file.
3931 <P>
3932 If the Setup/RemoteConfigSetup command doesn't do what you want, you
3933 may copy a local pinerc file to a remote configuration folder by hand
3934 by using the command line option "-copy_pinerc".
3935 <P>
3936 Another command line option, which is somewhat related to remote
3937 configuration, is the option "-x exceptions_config".
3938 The configuration settings in the exceptions configuration override
3939 your default settings.
3940 It may be useful to store the default configuration (the -p argument) remotely
3941 and to have the exceptions configuration stored in a local file.
3942 You might put generic configuration information in the remote configuration
3943 and platform-specific configuration on each platform in the exceptions
3944 configuration.
3945 The arguments to the "-p" and "-x" options
3946 can be either remote folders or local files.
3947 <P>
3948 There is another command line argument that works only with PC-Alpine and
3949 which may prove useful when using a remote configuration.
3950 The option "-aux local_directory" allows you to tell PC-Alpine where
3951 to store your local auxiliary files.
3952 This only has an effect if your configuration file is remote.
3953 Some examples of auxiliary files are debug files, address book files, and
3954 signature files.
3955 <P>
3956 <End of help on this topic>
3957 </BODY>
3958 </HTML>
3959 ============== h_config_exceptions =============
3960 <HTML>
3961 <HEAD>
3962 <TITLE>Generic and Exceptional Configuration</TITLE>
3963 </HEAD>
3964 <BODY>
3965 <H1>Generic and Exceptional Configuration</H1>
3967 If you use Alpine from more than one platform it may be convenient
3968 to split your configuration information into two pieces, a generic piece
3969 and exceptions that apply to a particular platform.
3970 For example, suppose you use Alpine from home and from work.
3971 Most of your configuration settings are probably the
3972 same in both locations, so those settings belong in the generic settings
3973 configuration.
3974 However, you may use a different SMTP server and INBOX
3975 from home than you do from work.
3976 The
3977 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
3978 and
3979 <A HREF="h_config_inbox_path">"<!--#echo var="VAR_inbox-path"-->"</A>
3980 options could be
3981 part of your exceptional configuration so that they could be different in the
3982 two places.
3983 <P>
3984 The command line option "-x exceptions_config"
3985 may be used to split your configuration into generic and exceptional pieces.
3986 "Exceptions_config" may be either local or remote.
3987 The regular Alpine configuration file will contain the generic data, and
3988 "exceptions_config" will contain the exceptional data.
3989 <P>
3990 For Unix Alpine, if you don't have a "-x" command line option,
3991 Alpine will look for the file "<CODE>.pinercex</CODE>"
3992 in the same local directory that the regular config file is located in (usually
3993 the Unix home directory).
3994 If the regular config file is remote (because the command line option
3995 "-p remote_config" was used) then Unix Alpine looks in the Unix home
3996 directory for "<CODE>.pinercex</CODE>".
3997 If the file does not already exist then no exceptions will be used.
3998 You can force exceptions to be used by using the "-x" option or
3999 by creating an empty "<CODE>.pinercex</CODE>" file.
4000 <P>
4001 For PC-Alpine, if you don't have a "-x" command line option,
4002 PC-Alpine will use the value of the
4003 environment variable <CODE>$PINERCEX</CODE>.
4004 If that is not set, PC-Alpine will look for
4005 the local file "<CODE>PINERCEX</CODE>"
4006 in the same local directory that the regular config file is located in.
4007 If the regular config file is remote (because the command line option
4008 "-p remote_config" was used) then PC-Alpine looks in the
4009 local directory specified by the "-aux local_directory" command
4010 line argument, or the directory <CODE>$HOME\PINE</CODE>, or
4011 in the <CODE><PINE.EXE </CODE>directory<CODE>></CODE>.
4012 <P>
4013 When you have an exception configuration there is a new command
4014 in the Alpine Setup screen, Setup/eXceptions.
4015 It toggles between exceptions and the regular configuration.
4016 This is the usual way to make changes in your exceptional configuration data.
4017 For example, you would type "S" for Setup, "X" for
4018 eXception, then follow that with one of the Setup commands, like "C"
4019 for Config or "K" for Kolor.
4020 <P>
4021 For most people, splitting the configuration information into two pieces is
4022 going to be most useful if the generic information is accessed
4023 <A HREF="h_config_remote_config">remotely</A>).
4024 That data will be the same no matter where you access it from and if you
4025 change it that change will show up everywhere.
4026 The exceptional data will most commonly be in a local file, so that the
4027 contents may easily be different on each computing platform used.
4028 <P>
4029 If you already have a local configuration file with settings you like
4030 you may find that the command Setup/RemoteConfigSetup is useful
4031 in helping you convert to a remote configuration.
4032 The command line flag "-copy_pinerc"
4033 may also be useful.
4034 <P>
4035 <End of help on this topic>
4036 </BODY>
4037 </HTML>
4038 ============== h_config_inheritance =============
4039 <HTML>
4040 <HEAD>
4041 <TITLE>Configuration Inheritance</TITLE>
4042 </HEAD>
4043 <BODY>
4044 <H1>Configuration Inheritance</H1>
4046 Configuration inheritance is a power user feature.
4047 It is confusing and not completely supported by the configuration
4048 user interface.
4049 We start with an explanation of how configuration works in hopes of making
4050 it easier to describe how inheritance works.
4051 <P>
4052 Alpine uses a hierarchy of configuration values from different locations.
4053 There are five ways in which each configuration option (configuration
4054 variable) can be set.
4055 In increasing order of precedence they are:
4056 <P>
4057 <OL>
4058 <LI> the system-wide configuration file.
4060 <LI> the personal configuration file
4062 <LI> the personal exceptions file
4064 <LI> a command line argument
4066 <LI> the system-wide <EM>fixed</EM> configuration file (Unix Alpine only)
4067 </OL>
4068 <P>
4069 The fixed configuration file is normally
4070 <CODE><!--#echo var="PINE_CONF_FIXED_PATH"--></CODE>.
4071 <P>
4072 The system-wide configuration file is normally
4073 <CODE><!--#echo var="PINE_CONF_PATH"--></CODE> for Unix Alpine and is normally not
4074 set for PC-Alpine.
4075 For PC-Alpine, if the environment variable <EM>$PINECONF</EM> is set, that
4076 is used for the system-wide configuration.
4077 This location can be set or changed on the command line with the -P flag.
4078 The system-wide configuration file can be either a local file or a
4079 remote configuration folder.
4080 <P>
4081 For Unix Alpine, the personal configuration file is normally the file
4082 <CODE>.pinerc</CODE> in the user's home directory.
4083 This can be changed with the -p command line flag.
4084 For PC-Alpine, the personal configuration file is in
4085 <CODE>$PINERC</CODE> or <CODE><AlpineRC registry value></CODE> or
4086 <CODE>$HOME\PINE\PINERC</CODE> or
4087 <CODE><PINE.EXE </CODE>dir<CODE>>\PINERC</CODE>.
4088 This can be changed with the -p command line flag.
4089 If -p is used, the configuration data may be in a local file or a remote config
4090 folder.
4091 <P>
4092 For Unix Alpine, the personal exceptions configuration file is named
4093 <CODE>.pinercex</CODE> and is in the same directory as the personal
4094 configuration file, if that configuration file is not remote, and is in
4095 the home directory if the personal configuration file is remote.
4096 If the file exists, then exceptions are turned on.
4097 If it doesn't, then you are not using exceptions.
4098 Alternatively, you may change the location of the exceptions configuration
4099 by using the command line argument "-x <exceptions_config>".
4100 Like the personal configuration data, exceptions_config may be
4101 either local or remote.
4102 <P>
4103 For PC-Alpine, the personal exceptions configuration file is named
4104 <CODE>PINERCEX</CODE> and is in the same directory as the personal
4105 configuration file unless the personal configuration file is remote.
4106 In that case, it is in the local directory specfied by the
4107 "-aux local_directory" command line argument.
4108 (In the case that the personal configuration is remote and there is no
4109 "-aux" command line argument, Alpine searches for
4110 a PINERCEX file in the directory <CODE>$HOME\PINE</CODE> and
4111 the directory <CODE><PINE.EXE </CODE>dir<CODE>></CODE>.)
4112 If the file exists, then exceptions are turned on.
4113 If it doesn't, then you are not using exceptions.
4114 You may change the location of the exceptions configuration
4115 by using the command line argument "-x <exceptions_config>".
4116 or with the
4117 environment variable <CODE>$PINERCEX</CODE> (if there is no "-x"
4118 option).
4119 <P>
4120 To reiterate, the value of a configuration option is taken from the
4121 last location in the list above in which it is set.
4122 Or, thinking about it slightly differently, a default value for an option
4123 is established in the system-wide configuration file (or internally by Alpine
4124 if there is no value in the system-wide file).
4125 That default remains in effect until and unless it is overridden by a value in a
4126 location further down the list, in which case a new "default"
4127 value is established.
4128 As we continue down the list of locations we either retain the
4129 value at each step or establish a new value.
4130 The value that is still set after going through the whole list of
4131 configuration locations is the one that is used.
4132 <P>
4133 So, for example, if an option is set in the system-wide configuration
4134 file and in the personal configuration file, but is not set in the
4135 exceptions, on the command line, or in the fixed file; then the value
4136 from the personal configuration file is the one that is used.
4137 Or, if it is set in the system-wide config, in the personal config, not
4138 in the exceptions, but is set on the command line; then the value
4139 on the command line is used.
4140 <P>
4141 Finally we get to inheritance.
4142 For configuration options that are lists, like "<!--#echo var="VAR_smtp-server"-->" or
4143 "<!--#echo var="VAR_incoming-folders"-->",
4144 the inheritance mechanism makes it possible to <EM>combine</EM>
4145 the values from different locations instead of <EM>replacing</EM> the value.
4146 This is true of all configuration lists other than the "Feature-List",
4147 for which you may already set whatever you want at
4148 any configuration location (by using the "no-" prefix if
4149 necessary).
4150 <P>
4151 To use inheritance, set the first item in a configuration list to the
4152 token "INHERIT", without the quotes.
4153 If the first item is "INHERIT",
4154 then instead of replacing the default value established so far, the rest of
4155 the list is appended to the default value established so far and that is
4156 the new value.
4157 <P>
4158 Here is an example which may make it clearer. Suppose we have:
4159 <P>
4160 <PRE>
4161 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4162 Personal config : smtp-server = INHERIT, mysmtp.home
4163 Exceptions config : smtp-server = <No Value Set>
4164 Command line : smtp-server = <No Value Set>
4165 Fixed config : smtp-server = <No Value Set>
4166 </PRE>
4167 <P>
4169 This would result in an effective smtp-server option of
4170 <P>
4171 <PRE>
4172 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home
4173 </PRE>
4174 <P>
4175 The "INHERIT" token can be used in any of the configuration files
4176 and the effect cascades.
4177 For example, if we change the above example to:
4178 <P>
4179 <PRE>
4180 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4181 Personal config : smtp-server = INHERIT, mysmtp.home
4182 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4183 Command line : smtp-server = <No Value Set>
4184 Fixed config : smtp-server = <No Value Set>
4185 </PRE>
4186 <P>
4188 This would result in:
4189 <P>
4190 <PRE>
4191 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home, yoursmtp.org
4192 </PRE>
4193 <P>
4194 Unset variables are skipped over (the default value is carried forward) so
4195 that, for example:
4196 <P>
4197 <PRE>
4198 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4199 Personal config : smtp-server = <No Value Set>
4200 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4201 Command line : smtp-server = <No Value Set>
4202 Fixed config : smtp-server = <No Value Set>
4203 </PRE>
4204 <P>
4206 produces:
4207 <P>
4208 <PRE>
4209 smtp-server = smtp1.corp.com, smtp2.corp.com, yoursmtp.org
4210 </PRE>
4211 <P>
4213 If any later configuration location has a value set (for a particular list
4214 option) which does <EM>not</EM> begin with "INHERIT",
4215 then that value replaces whatever value has been defined up to that point.
4216 In other words, that cancels out any previous inheritance.
4217 <P>
4218 <PRE>
4219 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4220 Personal config : smtp-server = INHERIT, mysmtp.org
4221 Exceptions config : smtp-server = yoursmtp.org
4222 Command line : smtp-server = <No Value Set>
4223 Fixed config : smtp-server = <No Value Set>
4224 </PRE>
4225 <P>
4227 results in:
4228 <P>
4229 <PRE>
4230 smtp-server = yoursmtp.org
4231 </PRE>
4232 <P>
4234 For some configuration options, like "<!--#echo var="VAR_viewer-hdr-colors"-->" or
4235 "<!--#echo var="VAR_patterns-roles"-->", it is
4236 difficult to insert the value "INHERIT" into the list of values
4237 for the option using the normal Setup tools.
4238 In other words, the color setting screen (for example) does not
4239 provide a way to input the text "INHERIT" as the first
4240 item in the <!--#echo var="VAR_viewer-hdr-colors"--> option.
4241 The way to do this is to either edit the pinerc file directly and manually
4242 insert it, or turn
4243 on the <A HREF="h_config_expose_hidden_config"><!--#echo var="FEAT_expose-hidden-config"--></A>
4244 feature and insert it using the Setup/Config screen.
4245 <P>
4246 <End of help on this topic>
4247 </BODY>
4248 </HTML>
4249 ============== h_special_xon_xoff =============
4250 <HTML>
4251 <HEAD>
4252 <TITLE>Explanation of Alpine's XOFF/XON Handling</TITLE>
4253 </HEAD>
4254 <BODY>
4255 <H1>XOFF/XON Handling within Alpine</H1>
4257 By default, Alpine treats Ctrl-S or Ctrl-Q (sometimes known as XOFF
4258 and XON) as normal characters, even though Alpine does not use them.
4259 However, the printer, modem, or communication software you are using may
4260 be configured for "software flow control," which means that
4261 XON/XOFF must be treated as special characters by the operating system.
4262 If you see messages such as "^S not defined for this screen",
4263 then your system is probably using software flow control. In this case
4264 you will need to set the
4265 <A HREF="h_config_preserve_start_stop">"<!--#echo var="FEAT_preserve-start-stop-characters"-->"</A>
4266 feature.
4267 <P>
4268 If you <EM>do</EM> set this
4269 feature, be advised that if you accidentally hit a Ctrl-S, Alpine will
4270 mysteriously freeze up with no warning. In this case, try typing a Ctrl-Q
4271 and see if that puts things right. Printing via the
4272 "attached-to-ansi" or
4273 "attached-to-wyse"
4274 option will automatically enable software
4275 flow-control handling for the duration of the printing.
4276 <P>
4277 <End of help on this topic>
4278 </BODY>
4279 </HTML>
4280 ============= h_special_help_nav =============
4281 <HTML>
4282 <HEAD>
4283 <TITLE>Help Text Navigation Explained</TITLE>
4284 </HEAD>
4285 <BODY>
4286 <H1>Help Text Navigation Explained</H1>
4288 Alpine contains extensive context-sensitive help text. At any point,
4289 pressing the "?" key will bring up a page of help text
4290 explaining the options available to you. You can leave the help
4291 text screen and return to normal Alpine operation by pressing
4292 the
4293 <!--chtml if pinemode="function_key"-->
4294 F3 function
4295 <!--chtml else-->
4296 "E"
4297 <!--chtml endif-->
4298 key to Exit Help at any time.
4300 <P>
4301 Within the help screen you might find a word or phrase displayed in
4302 inverse text and others displayed in bold typeface. Such words and
4303 phrases are used to tell you Alpine has more information available on
4304 the topic they describe.
4305 The inverted text is the "selected" topic.
4306 Use the arrow keys, Ctrl-F, and Ctrl-B to change which of the phrases
4307 displayed in bold type
4308 is "selected".
4309 Hit the Return key to display the information Alpine has available on that
4310 topic. While viewing such additional information, the
4311 <!--chtml if pinemode="function_key"-->
4312 F3 function
4313 <!--chtml else-->
4314 "P"
4315 <!--chtml endif-->
4316 key will return you to the previous help screen, and the
4317 <!--chtml if pinemode="function_key"-->
4318 F2 function
4319 <!--chtml else-->
4320 "E"
4321 <!--chtml endif-->
4322 key will Exit the Help system altogether.
4324 <P>
4325 The "N" command will tell you the internal name of the help text you are
4326 reading each time, so that you can send this name in the text of a message
4327 and create a direct link to that internal help using the x-pine-help URL
4328 scheme. For example, the direct link to this item is
4329 x-pine-help:h_special_help_nav. If you add this text to a message, then
4330 a person using Pine to read such message would have a direct link to this
4331 help text.
4333 <P>
4334 When you are finished reading this help text, you can press the
4335 <!--chtml if pinemode="function_key"-->
4336 F3 function
4337 <!--chtml else-->
4338 "P"
4339 <!--chtml endif-->
4340 key to return to the previously displayed help text.
4342 <P>
4343 <End of help on this topic>
4344 </BODY>
4345 </HTML>
4346 ============= h_special_list_commands =============
4347 <HTML>
4348 <HEAD>
4349 <TITLE>Email List Commands Explained</TITLE>
4350 </HEAD>
4351 <BODY>
4352 <H1>Email List Commands Explained</H1>
4354 Electonic mail lists provide a way for like-minded users to join in
4355 discussions on topics of interest. The email list itself is
4356 represented by a
4357 single address that participants send messages to when they have
4358 something of interest to share with other members of the list. The
4359 receiving computer then, either automatically or after review by the
4360 list's owner (or moderator), sends a copy of that message to each
4361 member of the list.
4363 <P>
4364 Usually, subscribing and unsubscribing is done by sending requests in
4365 an email message to a special address setup to handle managing list
4366 membership. Often this is the name of the list followed by
4367 <I>-request</I>. This address is almost <EM>never</EM> the same as
4368 the address used to send messages to the list.
4370 <P>
4371 Unfortunately, email list participation commands are more a matter
4372 of convention than standard, and thus may vary from list to list.
4373 Increasingly, list management software is adding information to
4374 the copy of the postings as they're copied to the list members that
4375 explains how to do the various list management functions.
4377 <P>
4378 Alpine will recognize this information and offer the management commands
4379 they represent in a simple display. One or more of the following
4380 operations will be made available:
4382 <DL>
4383 <DT>Help</DT>
4384 <DD>
4385 A method to get help on subscribing, unsubscribing,
4386 an explanation of what the list is about, or special instructions
4387 for participation. This may be in the form of a reply in response
4388 to an email message, or instructions on how to connect to a Web site.
4389 </DD>
4391 <DT>Unsubscribe</DT>
4392 <DD>
4393 A method to get your email addressed removed from the list of
4394 recipients of the email list.
4395 </DD>
4397 <DT>Subscribe</DT>
4398 <DD>
4399 A method to get your email address added to the list of recipients
4400 of the email list. It may be in the form of a message sent to
4401 a special address or you may be connected to a web site.
4402 <DD>
4403 </DD>
4405 <DT>Post</DT>
4406 <DD>
4407 A method used to post to the email list. However, it might also
4408 indicate that no posting is allowed directly to the list.
4409 </DD>
4411 <DT>Owner</DT>
4412 <DD>
4413 A method to contact the list owner for special questions you might
4414 have regarding the list.
4415 </DD>
4417 <DT>Archive</DT>
4418 <DD>
4419 A method to view an archive of previous messages posted to the list.
4420 This may be in the form of a mail folder on a remote computer, an
4421 IMAP mailbox or even a Web site.
4422 </DD>
4423 </DL>
4425 <P>
4426 <End of help on this topic>
4427 </BODY>
4428 </HTML>
4429 ============= h_quota_command =============
4430 <HTML>
4431 <HEAD>
4432 <TITLE>Quota Screen Explained</TITLE>
4433 </HEAD>
4434 <BODY>
4435 <H1>Quota Screen Explained</H1>
4437 <P> This screen summarizes the quota report for this mailbox in the
4438 IMAP server. For each resource that you have a quota, this reports summarizes
4439 its use and limit.
4441 <P> Your IMAP server administrator may have set a quota based either on
4442 the total size of your mailbox (STORAGE), or the number of messages in
4443 your mailbox (MESSAGES), or some other criteria. This will be reported
4444 to you indicating the type of quota, its total use and its limit.
4446 <P> The report for STORAGE is reported in kibibytes (KiB). One kibibyte is
4447 1024 bytes. Each of the characters that you see in this help text is one
4448 byte, and this help text is about 1 kibibyte in size. Small messages sent
4449 by Alpine are normally less than 4 kibibytes in size (which includes
4450 headers and text). Other email programs may send messages with bigger
4451 sizes when they send messages, since they send plain text and an
4452 alternative part in HTML.
4454 <P> A convenient way to save space for the STORAGE type of quota is by
4455 deleting attachments. This is done on each individual message by pressing
4456 the "V" command while reading the message text, then moving the cursor
4457 to the position of the attachment that is to be deleted, then pressing
4458 "D" to delete such attachment, going back to reading the
4459 message with the "<" command and pressing "S" to
4460 save the message in the same folder you are reading from. The saved
4461 message will not have the attachment that was marked deleted. Now you
4462 can delete and expunge the message with the unwanted attachment.
4464 <P>
4465 <End of help on this topic>
4466 </BODY>
4467 </HTML>
4468 ============= h_mail_thread_index =============
4469 <HTML>
4470 <HEAD>
4471 <TITLE>THREAD INDEX COMMANDS</TITLE>
4472 </HEAD>
4473 <BODY>
4474 <H1>THREAD INDEX COMMANDS</H1>
4475 <!--chtml if pinemode="function_key"-->
4476 Available Commands -- Group 1 Available Commands -- Group 2<BR>
4477 ------------------------------- -----------------------------<BR>
4478 F1 Show Help Text F1 Show Help Text<BR>
4479 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
4480 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
4481 F4 View current thread F4 Quit Alpine<BR>
4482 F5 Move to previous thread F5 <A HREF="h_common_compose">Compose</A> a message<BR>
4483 F6 Move to next thread F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
4484 F7 Show previous screen F7 <A HREF="h_common_nextnew">Next new</A> thread<BR>
4485 F8 Show next screen F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
4486 F9 <A HREF="h_common_delete">Mark thread for deletion</A> F9 <A HREF="h_common_print">Print</A> index<BR>
4487 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
4488 F11 <A HREF="h_common_reply">Reply</A> to thread F11 <A HREF="h_common_save">Save</A> messages into an email folder<BR>
4489 F12 <A HREF="h_common_reply">Forward</A> messages F12 <A HREF="h_common_save">Export</A> messages into a plain file<BR>
4490 <BR>
4491 Available Commands -- Group 3<BR>
4492 -----------------------------<BR>
4493 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>
4494 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>
4495 F6 F9 <A HREF="h_common_hdrmode">Full Header Mode</A> F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
4496 <BR>
4497 Available Commands -- Group 4<BR>
4498 -----------------------------<BR>
4499 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
4500 F6 <A HREF="h_common_role">Compose using a role</A><BR>
4501 <BR>
4502 <!--chtml else-->
4503 Navigating the List of Threads Operations on the Current Thread<BR>
4504 ------------------------------- ---------------------------------<BR>
4505 P Move to the previous thread > View Thread % <A HREF="h_common_print">Print</A><BR>
4506 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>
4507 - Show previous screen D <A HREF="h_common_delete">Mark thread for deletion</A><BR>
4508 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
4509 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>
4510 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>
4511 specific thread E <A HREF="h_common_save">Export</A> as a plain text file<BR>
4512 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>
4513 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
4514 <BR>
4515 Miscellaneous Operations General Alpine Commands<BR>
4516 ------------------------ ---------------------<BR>
4517 G <A HREF="h_common_goto">Goto</A> a specified folder O Show all other available commands<BR>
4518 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ? Show Helptext Q Quit Alpine<BR>
4519 H <A HREF="h_common_hdrmode">Full header mode</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
4520 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> C <A HREF="h_common_compose">Compose</A> a new message<BR>
4521 Z <A HREF="h_index_cmd_zoom">Zoom</A> # <A HREF="h_common_role">Compose using a role</A><BR>
4522 ; <A HREF="h_index_cmd_select">Select</A> A <A HREF="h_index_cmd_apply">Apply</A> L COLLECTION LIST Screen<BR>
4523 : Select Messages in Current Thread<BR>
4524 <!--chtml endif-->
4525 <P>
4527 NOTE:
4528 <OL>
4529 <LI>For help on a particular command, highlight the bold text associated
4530 with it above and hit Return.
4531 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
4532 </OL>
4534 <H2>Description of the THREAD INDEX Screen</H2>
4536 The THREAD INDEX displays summary information from each
4537 thread (conversation) in the current folder.
4538 This is useful if you want to quickly
4539 scan new threads, or find a particular thread without having to go
4540 through the text of each message, or to quickly get rid of junk
4541 threads, etc.
4542 The current thread is always highlighted.
4543 Each line of the THREAD INDEX contains the following columns: <P>
4544 <DL>
4545 <DT>STATUS:</DT>
4546 <DD> The markings on the left side of the thread tell you about its
4547 status. You may see one or more of the following codes on any given
4548 thread:
4549 <UL>
4550 <LI> "D" for Deleted. All of the messages in this thread are marked for deletion but not yet eXpunged from the folder.
4551 <LI> "A" for Answered. All of the messages in this thread are marked answered.
4552 <LI> "N" for New. At least one message in the thread is New (you haven't looked at it yet).
4553 <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.
4554 <LI> "-" for cc-to-you. The "-" indicates that a
4555 message in the thread was sent to you as a cc:. This symbol will only show up if
4556 the feature
4557 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
4558 <LI> "X" for selected. You have selected at least one message in the thread by using the
4559 "select" command. (Some systems may optionally allow selected
4560 messages to be denoted by the index line being displayed in bold
4561 type instead.)
4562 <LI> "*" for Important. You have previously used the "Flag" command
4563 to mark at least one message in this thread as "important".
4564 </UL></DD><P>
4566 <DT>THREAD NUMBER:</DT>
4567 <DD>Threads in a folder are numbered, from one through the number
4568 of threads in the folder, to help you know where you are in the folder.
4569 </DD><P>
4571 <DT>DATE STARTED:</DT>
4572 <DD>The date the thread was started. This is actually from the Date header
4573 of the first message in the thread. It doesn't take different time zones
4574 into account.</DD><P>
4576 <DT>WHO STARTED THE THREAD:</DT>
4577 <DD>This is usually the name of the sender of the first message in the thread, taken from
4578 the From header of the message.
4579 If there is no personal name given in that
4580 address, then the email address is used instead.
4581 If the message is from you (or from one of your
4582 <A HREF="h_config_alt_addresses">alternate addresses</A>),
4583 then the recipient's name is shown here instead, with the characters
4584 "To: " inserted before the name.
4585 (The idea of this is that if you started the thread you would rather see who
4586 the mail was sent to instead of that the mail was from you.)
4587 In Newsgroups, if you are
4588 the sender and there are no email recipients, the newsgroup name will be
4589 listed after the "To: ".
4590 </DD><P>
4592 <DT>SIZE:</DT>
4593 <DD>The number in parentheses is the number of messages in the thread.</DD><P>
4595 <DT>SUBJECT:</DT>
4596 <DD>As much of the thread's subject line as will fit on the screen.
4597 This is the subject of the first message in the thread.</DD>
4598 </DL>
4600 <P><UL>
4601 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
4602 </UL>
4603 <P>
4604 <End of help on this topic>
4605 </BODY>
4606 </HTML>
4607 ============= h_mail_index =============
4608 <HTML>
4609 <HEAD>
4610 <TITLE>MESSAGE INDEX COMMANDS</TITLE>
4611 </HEAD>
4612 <BODY>
4613 <H1>MESSAGE INDEX COMMANDS</H1>
4614 <!--chtml if pinemode="function_key"-->
4615 Available Commands -- Group 1 Available Commands -- Group 2<BR>
4616 ------------------------------- -----------------------------<BR>
4617 F1 Show Help Text F1 Show Help Text<BR>
4618 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
4619 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
4620 F4 View current message F4 Quit Alpine<BR>
4621 F5 Move to previous message F5 <A HREF="h_common_compose">Compose</A> a message<BR>
4622 F6 Move to next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
4623 F7 Show previous screen of messages F7 <A HREF="h_common_nextnew">Next new</A> message<BR>
4624 F8 Show next screen of messages F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
4625 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
4626 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
4627 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
4628 F12 <A HREF="h_common_reply">Forward</A> message F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
4629 <BR>
4630 Available Commands -- Group 3<BR>
4631 -----------------------------<BR>
4632 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>
4633 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>
4634 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>
4635 <BR>
4636 Available Commands -- Group 4<BR>
4637 -----------------------------<BR>
4638 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
4639 F6 <A HREF="h_common_role">Compose using a role</A> F10 <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread<BR>
4640 <BR>
4641 <!--chtml else-->
4642 Navigating the List of Messages Operations on the Current Message<BR>
4643 ------------------------------- ---------------------------------<BR>
4644 P Move to the previous message > View % <A HREF="h_common_print">Print</A><BR>
4645 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>
4646 - Show previous screen of messages D <A HREF="h_common_delete">Mark for deletion</A><BR>
4647 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
4648 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>
4649 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>
4650 specific message E <A HREF="h_common_save">Export</A> as a plain text file<BR>
4651 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>
4652 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
4653 Miscellaneous Operations<BR>
4654 ------------------------<BR>
4655 G <A HREF="h_common_goto">Goto</A> a specified folder General Alpine Commands<BR>
4656 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ---------------------<BR>
4657 H <A HREF="h_common_hdrmode">Full header mode</A> O Show all other available commands<BR>
4658 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> ? Show Help text Q Quit Alpine<BR>
4659 Z <A HREF="h_index_cmd_zoom">Zoom</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
4660 ; <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>
4661 : Select Current message # <A HREF="h_common_role">Compose using a role</A><BR>
4662 / <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread L COLLECTION LIST Screen<BR>
4663 <!--chtml endif-->
4664 <P>
4666 NOTE:
4667 <OL>
4668 <LI>For help on a particular command, highlight the bold text associated
4669 with it above and hit Return.
4670 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
4671 </OL>
4673 <H2>Description of the MESSAGE INDEX Screen</H2>
4675 The MESSAGE INDEX displays summary information from each
4676 message in the current folder.
4677 This is useful if you want to quickly
4678 scan new messages, or find a particular message without having to go
4679 through the text of each message, or to quickly get rid of junk
4680 messages, etc.
4681 <P>
4682 The current message is always highlighted
4683 and many commands operate on the current message.
4684 For example, the Delete command will delete the current message.
4685 If the folder is sorted by either Threads or OrderedSubject, then, depending
4686 on some of your configuration settings, a single line in the index may
4687 refer to an entire thread or to a subthread.
4688 If that is the case, then the commands that normally operate on the current
4689 message will operate on the thread or subthread instead.
4690 For example, the Delete command will delete the whole collapsed thread
4691 instead of just a single message.
4692 <P>
4693 Each line of the MESSAGE INDEX contains the following columns (by default --
4694 you can change this with the
4695 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
4696 in the SETUP CONFIGURATION screen): <P>
4697 <DL>
4698 <DT>STATUS:</DT>
4699 <DD> The markings on the left side of the message tell you about its
4700 status. You may see one or more of the following codes on any given
4701 message:
4702 <UL>
4703 <LI> "D" for Deleted. You have marked this message for deletion but not
4704 yet eXpunged the folder.
4705 <LI> "N" for New. You have not looked at the text of the message yet.
4706 <LI> "A" for Answered. Any time you reply to a message it is considered
4707 to be answered.
4708 <LI> "F" for Forwarded. Similar to Answered, this is set whenever you
4709 forward a message.
4710 <LI> "+" for direct-to-you. The "+" indicates that a message was sent
4711 directly to your account, your copy is not part of a cc: or a
4712 mailing list.
4713 <LI> "-" for cc-to-you. The "-" indicates that a
4714 message was sent to you as a cc:. This symbol will only show up if
4715 the feature
4716 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
4717 <LI> "X" for selected. You have selected the message by using the
4718 "select" command. (Some systems may optionally allow selected
4719 messages to be denoted by the index line being displayed in bold
4720 type.)
4721 <LI> "*" for Important. You have previously used the "Flag" command
4722 to mark this message as "important".
4723 </UL></DD><P>
4725 <DT>MESSAGE NUMBER:</DT>
4726 <DD>Messages in a folder are numbered, from one through the number
4727 of messages in the folder, to help you know where you are in the folder.
4728 These numbers are always in increasing order, even if you sort the folder
4729 in a different way.</DD><P>
4731 <DT>DATE SENT:</DT>
4732 <DD>The date the message was sent. By default, messages are
4733 ordered by arrival time, not by date sent. Most of the time, arrival time
4734 and date sent (effectively departure time) are similar. Sometimes,
4735 however, the index will appear to be out of order because a message took a
4736 long time in delivery or because the sender is in a different time
4737 zone than you are. This date is just the date from the Date header
4738 field in the message.</DD><P>
4740 <DT>WHO SENT THE MESSAGE:</DT>
4741 <DD>This is usually the name of the sender of the message, taken from
4742 the From header of the message.
4743 If there is no personal name given in that
4744 address, then the email address is used instead.
4745 If the message is from you (or from one of your
4746 <A HREF="h_config_alt_addresses">alternate addresses</A>),
4747 then the recipient's name is shown here instead, with the characters
4748 "To: " inserted before the name.
4749 (The idea of this is that if you sent the mail you would rather see who
4750 the mail was sent to instead of that the mail was from you.
4751 This behavior may be changed by modifying the <!--#echo var="VAR_index-format"--> option mentioned
4752 above.
4753 In particular, use the FROM token or the FROMORTONOTNEWS token
4754 in place of the FROMORTO token.)
4755 In Newsgroups, if you are
4756 the sender and there are no email recipients, the newsgroup name will be
4757 listed after the "To: ". </DD><P>
4759 <DT>SIZE:</DT>
4760 <DD>The number in parentheses is the number of characters in the message.
4761 It may have a suffix of K, M, or G which means the number should be
4762 multiplied by one thousand, one million, or one billion to get the
4763 size of the message.</DD><P>
4765 <DT>SUBJECT:</DT>
4766 <DD>As much of the message's subject line as will fit on the screen.</DD>
4767 </DL>
4769 <P><UL>
4770 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
4771 </UL>
4772 <P>
4773 <End of help on this topic>
4774 </BODY>
4775 </HTML>
4776 ============= h_mail_view ========================
4777 <HTML>
4778 <HEAD>
4779 <TITLE>MESSAGE TEXT SCREEN</TITLE>
4780 </HEAD>
4781 <BODY>
4782 <H1>MESSAGE TEXT SCREEN</H1>
4783 <!--chtml if pinemode="function_key"-->
4784 Available Commands -- Group 1 Available Commands -- Group 2<BR>
4785 ------------------------------- ------------------------------<BR>
4786 F1 Show Help Text F1 Show Help Text<BR>
4787 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
4788 F3 <A HREF="h_common_index">MESSAGE INDEX</A> Screen F3 MAIN MENU Screen<BR>
4789 F4 <A HREF="h_view_cmd_viewattch">View attachment</A> F4 Quit Alpine<BR>
4790 F5 Display previous message F5 <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
4791 F6 Display next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
4792 F7 Previous screen of this message F7 <A HREF="h_common_compose">Compose</A> message<BR>
4793 F8 Next screen of this message F8 <A HREF="h_view_cmd_whereis">Whereis</A><BR>
4794 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
4795 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
4796 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
4797 F12 <A HREF="h_common_reply">Forward</A> F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
4798 <BR>
4799 Available Commands -- Group 3<BR>
4800 ------------------------------<BR>
4801 F1 Show Help Text<BR>
4802 F2 Toggle to see more commands<BR>
4803 F3 <A HREF="h_view_cmd_hilite">View hilited</A><BR>
4804 F4 Select current message<BR>
4805 F5 Previous selectable item<BR>
4806 F6 Next selectable item<BR>
4807 F7 <A HREF="h_common_jump">Jump</A> to message number<BR>
4808 F8 <A HREF="h_common_nextnew">Next new</A> message<BR>
4809 F9 <A HREF="h_common_hdrmode">Display full headers</A><BR>
4810 F10 <A HREF="h_common_bounce">Bounce</A> message<BR>
4811 F11 <A HREF="h_common_flag">Flag</A> message<BR>
4812 F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
4813 Available Commands -- Group 4<BR>
4814 F5 <A HREF="h_common_role">Compose using a role</A><BR>
4815 <!--chtml else-->
4816 Operations on the Current Message<BR>
4817 ---------------------------------<BR>
4818 <BR>
4819 - Show previous page of this msg S <A HREF="h_common_save">Save</A> into an email folder<BR>
4820 Spc (space bar) Show next page E <A HREF="h_common_save">Export</A> as a plain text file<BR>
4821 > <A HREF="h_view_cmd_viewattch">View attachment</A> B <A HREF="h_common_bounce">Bounce</A><BR>
4822 R <A HREF="h_common_reply">Reply</A> to message F <A HREF="h_common_reply">Forward</A> message<BR>
4823 D <A HREF="h_common_delete">Mark for deletion</A> Ret View <A HREF="h_view_cmd_hilite">hilited</A> item<BR>
4824 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>
4825 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>
4826 % <A HREF="h_common_print">Print</A> * <A HREF="h_common_flag">Flag</A> message<BR>
4827 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>
4828 <BR>
4829 Navigating the List of Messages Other Commands<BR>
4830 ------------------------------- ----------------------------<BR>
4831 P Display previous message G <A HREF="h_common_goto">Goto</A> a specified folder<BR>
4832 N Display next message H <A HREF="h_common_hdrmode">Full header mode</A> on/off<BR>
4833 J <A HREF="h_common_jump">Jump</A> to a specific message : Select Current message<BR>
4834 Tab <A HREF="h_common_nextnew">Next new</A> message A <A HREF="h_config_prefer_plain_text">Toggle Prefer Plain Text</A><BR>
4835 <BR>
4836 General Alpine Commands<BR>
4837 ---------------------<BR>
4838 O Show all other available commands<BR>
4839 ? Show Help text Q Quit Alpine<BR>
4840 M MAIN MENU Screen L <A HREF="h_common_folders">FOLDER LIST</A> Screen (or COLLECTION LIST Screen)<BR>
4841 < <A HREF="h_common_index">MESSAGE INDEX</A> Screen C <A HREF="h_common_compose">Compose</A> a new message<BR>
4842 # <A HREF="h_common_role">Compose using a role</A><BR>
4843 <!--chtml endif-->
4844 <P>
4846 NOTE:
4847 <OL>
4848 <LI>For help on a particular command, highlight the bold text associated
4849 with it above and hit Return.
4850 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
4851 </OL>
4853 <H2>Description of the MESSAGE TEXT Screen</H2>
4855 The top line of the view message screen displays status
4856 information about the currently open collection and folder and about the
4857 current message. It shows the name of the collection in angle brackets
4858 and then the name of the folder. The line also displays the number
4859 of messages in the folder, the number of the current message and the
4860 percentage of the current message that has been displayed on the screen.
4861 If the message is marked for deletion "DEL" will appear in the upper
4862 right corner.
4863 If the message has been answered (but not deleted) "ANS" will show
4864 in the corner.
4865 <P>
4867 NOTE: to rapidly move to the end of a message, hit the
4868 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
4869 (or Ctrl-W) key followed
4870 by Ctrl-V. Similarly,
4871 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
4872 followed by Ctrl-Y will take you to the beginning of
4873 a message.
4875 <H2>Explanation of Alternate Character Sets</H2>
4877 Alpine attempts to stay out of the way so that it won't prevent you from
4878 viewing mail in any character set. It will simply send the message to
4879 your display device. If the device is capable of displaying the
4880 message as it was written it will do so. If not, the display may be
4881 partially or totally incorrect.
4882 If the message contains characters that are not representable in your
4883 <A HREF="h_config_char_set">"Display Character Set"</A>
4884 variable in your configuration, then a warning message will be printed
4885 to your screen at the beginning of the message display.
4886 It is probably best to use UNIX Alpine in a terminal emulator
4887 capable of displaying UTF-8 characters.
4888 See <A HREF="h_config_char_set">Display Character Set</A> for a little
4889 more information about character set settings.
4891 <P><UL>
4892 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
4893 </UL>
4894 <P>
4895 <End of help on this topic>
4896 </BODY>
4897 </HTML>
4898 ======= h_index_cmd_select =======
4899 <HTML>
4900 <HEAD>
4901 <TITLE>Selecting: Select and WhereIs/Select</TITLE>
4902 </HEAD>
4903 <BODY>
4904 <H1>Selecting: Select and WhereIs/Select</H1>
4906 Aggregate operations give you the ability to process a group of messages
4907 at once. Acting on multiple messages requires two steps: (1) selecting a
4908 set of messages and then; (2) applying a command to that set. The first
4909 part is handled by the select command. Select allows you to
4910 select messages based on their status (read, answered, etc.), contents,
4911 date, size, or keywords.
4912 You may also select based on one of your Rules or based on threads,
4913 and there are quick options to select a specific message or range of messages,
4914 to select the current message, or to select all messages.
4915 <P>
4917 We describe the various selection criteria briefly:
4918 <P>
4920 <DL>
4921 <DT>select All</DT>
4922 <DD> Marks all the messages in the folder as selected.
4923 </DD>
4925 <DT>select Cur</DT>
4926 <DD> Selects the currently highlighted message or currently highlighted
4927 set of messages if in a threaded view.
4928 </DD>
4930 <DT>select by Number</DT>
4931 <DD> Select by message number. This may be a comma-separated list instead or
4932 a single entry.
4933 Each element in the list may be either a single message number or a range
4934 of numbers with a dash between the lowest and highest member of the range.
4935 Some examples are 7 to select only message number 7; 2-5 to select messages
4936 2 through 5; and 2-5,7-9,11 to select messages 2, 3, 4, 5, 7, 8, 9, and 11.
4937 The word "end" may be used as a substitute for the highest numbered
4938 message in the folder.
4939 If in a separate thread index where the numbers refer to threads instead of
4940 to messages, then you will be selecting all of the messages in the
4941 referenced threads instead of selecting by message number.
4942 </DD>
4944 <DT>select by Date</DT>
4945 <DD> Select by either the date stored in the Date headers of each message,
4946 or by the date when the messages arrived.
4947 This does not adjust for different time zones, but just checks to see what
4948 day the message was sent on.
4949 You may type in a date. If you do, the date should be in the form
4950 <P><SAMP><CENTER>DD-Mon-YYYY</CENTER></SAMP><P>
4951 For example,
4952 <P><SAMP><CENTER>24-Nov-2004</CENTER></SAMP><P>
4953 or
4954 <P><SAMP><CENTER>09-Nov-2004</CENTER></SAMP><P>
4955 If the date you want is close to the current date, it is probably
4956 easier to use the "^P Prev Day" or "^N Next Day" commands to change the default date that
4957 is displayed, instead of typing in the date yourself.
4958 Or, the "^X Cur Msg" command may be used to fill in
4959 the date of the currently highlighted message.
4960 <P>
4961 There are six possible settings that are selected using the
4962 "^W Toggle When" command.
4963 Three of them select messages based on the Date headers.
4964 They are "SENT SINCE", "SENT BEFORE",
4965 and "SENT ON".
4966 SINCE is all messages with the selected date or later.
4967 BEFORE is all messages earlier than the selected date (not including the day
4968 itself).
4969 ON is all messages sent on the selected date.
4970 The other three select messages in the same way but they use the arrival
4971 times of the messages instead of the Date headers included in the messages.
4972 Those three are "ARRIVED SINCE", "ARRIVED BEFORE",
4973 and "ARRIVED ON".
4974 When you save a message from one folder to another the arrival time is
4975 preserved.
4976 </DD>
4978 <DT>select by Text</DT>
4979 <DD> Selects messages based on the message contents.
4980 This allows you to select a set of messages based on whether or not the
4981 message headers or message body contain specified text.
4982 You may look for text in the Subject, the From header,
4983 the To header, or the Cc header.
4984 You may also choose Recipient, which searches for the text in
4985 either the To or the Cc header;
4986 or Participant, which means To or Cc or From.
4987 Besides those specific header searches, you may also search the entire
4988 header and text of the message with "All Text", or just the
4989 body of the message.
4990 <P>
4991 To search for the absence of text, first type the "! Not" command
4992 before typing the specific type of text search.
4993 For example, you could type "!" followed by "S" to
4994 search for all messages that do not contain a particular word in their
4995 Subjects.
4996 <P>
4997 If you choose a Subject search, you may use the subject from the current
4998 message by typing the "^X Cur Subject" command.
4999 You may then edit it further if you wish.
5000 For example, you might select the subject of a reply and edit the
5001 "Re: " off of the front of it in order to search for
5002 the original message being replied to.
5003 All of the other header searches allow you to use addresses from the
5004 headers of the current message if you want to.
5005 You may use the "^T Cur To", "^R Cur From", or
5006 "^W Cur Cc".
5007 In each case, if there is more than one address, only the first is offered.
5008 </DD>
5010 <DT>select by Status</DT>
5011 <DD> Selects messages based on their status.
5012 You may select all New, Important, Deleted, Answered, Recent, or Unseen
5013 messages.
5014 Or, if you first type the "! Not" command, you get not New,
5015 or not Important, and so on.
5016 If you select Deleted messages, you will get all messages with their
5017 Deleted flag set.
5018 Likewise for Important messages, all messages that you have flagged as
5019 being Important with the
5020 <A HREF="h_common_flag">Flag</A> command.
5021 The "New" and "Answered" choices are a little bit odd
5022 because they try to match what you see on the screen by default.
5023 "New" is a shorthand for messages that are Unseen, Undeleted,
5024 and Unanswered.
5025 If you have looked at the message, or deleted it, or answered it; then it
5026 is not considered "New ".
5027 "! New" is the opposite of "New".
5028 <P>
5029 "Answered" is another one that is a little different.
5030 It means that the message has been Answered <EM>and</EM> is not deleted.
5031 And to make it even more confusing, "! Answered" is not
5032 the opposite of "Answered"!
5033 Instead, "! Answered" stands for messages that are
5034 both Unanswered <EM>and</EM> not deleted.
5035 <P>
5036 The other two types were added later because the special nature of the
5037 New flag was not what was wanted by all users.
5038 New does match what you see in the index by default, but if you use
5039 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5040 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5041 be exactly what you want.
5042 "Unseen" simply selects all unseen messages, whether or not
5043 they are deleted or answered, and
5044 "Recent" selects all of the messages that have been added to
5045 the folder since you started this Alpine session.
5046 (That's not technically quite true. If there are multiple mail clients
5047 reading an IMAP mailbox, each message will be marked as Recent in only
5048 one of the client's sessions.)
5049 </DD>
5051 <DT>select by siZe</DT>
5052 <DD> Selects messages based on their size being smaller than or larger
5053 than the size you specify.
5054 The size is the number of bytes.
5055 You may use the suffix "K" or "k" to mean 1,000 times
5056 the number.
5057 For example, 7K is the same as 7000.
5058 The suffix "M" or "m" means 1,000,000 times the number,
5059 and the suffix "G" or "g" means 1,000,000,000 times.
5060 Use the "^W" command to toggle back and forth between Smaller
5061 and Larger.
5062 </DD>
5064 <DT>select by Keyword</DT>
5065 <DD> Selects messages that either have or do not have
5066 (using the "! Not" command)
5067 a particular <A HREF="h_config_keywords">Keyword</A> set.
5068 One way to select a keyword is to use the "^T To List"
5069 command to select one from your list of keywords.
5070 The
5071 <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.
5072 </DD>
5074 <DT>select by Rule</DT>
5075 <DD> Selects messages that either match or don't match
5076 (using the "! Not" command)
5077 one of the Rules you have defined.
5078 The most likely method of filling in the Rule is to use the
5079 "^T To List"
5080 command to select one of your Rules.
5081 All of the Rules you have defined will be in the list, including
5082 Rules for Searching, Indexcolors, Filtering, Roles, Score setting, and Other.
5083 They may not all make sense for this purpose, but they are all there for
5084 flexibility.
5085 You might find it useful to define some rules solely for the purpose
5086 of being used by the Select command.
5087 There is a special category for such Rules. They are called Search Rules.
5088 <P>
5089 Unfortunately, Alpine does not allow all possible Rules to be defined.
5090 For example, there is no logical OR operation.
5091 OR is accomplished in the Filter Rules or the other types of Rules by
5092 simply defining two rules, one that matches the first part of the OR
5093 and another that matches the second part.
5094 But you can't do that here, since you only have a single Rule to work with.
5095 Likewise, the order of Rules is usually important.
5096 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5097 a message, then that stops the search for a further match.
5098 This means that you may be confused if you try to use Select by Rule to
5099 check your Filter rules because the order is important when filtering but
5100 is not considered here.
5101 </DD>
5103 <DT>select by tHread</DT>
5104 <DD> Selects all of the messages in the current thread.
5105 </DD>
5106 </DL>
5108 After you have an initial selection, the next and subsequent selection
5109 commands modify the selection.
5110 The select command changes. It first gives
5111 you selection "alteration" options: "unselect All",
5112 "unselect Current",
5113 "Broaden selection" (implements a logical OR), and
5114 "Narrow selection" (implements a logical AND).
5115 After you choose either Broaden or Narrow, you then choose one of the
5116 selection criteria listed above (by Text or Number or ...).
5117 You may use select as many times as you wish to get the selected set right.
5118 <P>
5120 The WhereIs command has a feature (Ctrl-X) to
5121 select all the messages that match the WhereIs search. WhereIs searches
5122 through just the text that appears on the MESSAGE INDEX screen.
5123 This method is often slower than using the select command itself, unless the
5124 line you are looking for is not too far away in the index.
5125 <P>
5127 The availability of the aggregate operations commands is determined by the
5128 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
5129 Feature-List option in your Alpine
5130 configuration, which defaults to set.
5131 The features
5132 <A HREF="h_config_auto_zoom">"<!--#echo var="FEAT_auto-zoom-after-select"-->"</A>
5133 and
5134 <A HREF="h_config_select_wo_confirm">"<!--#echo var="FEAT_select-without-confirm"-->"</A>
5135 affect the behavior of the Select command.
5137 <P>
5138 <End of help on this topic>
5139 </BODY>
5140 </HTML>
5141 ======= h_select_rule =======
5142 <HTML>
5143 <HEAD>
5144 <TITLE>Select: Rule</TITLE>
5145 </HEAD>
5146 <BODY>
5147 <H1>Select: Rule</H1>
5149 You are selecting messages that either match or don't match
5150 one of the Rules you have defined.
5151 You may either type the nickname of the Rule at the prompt, or use the
5152 "^T To List"
5153 command to select one of your Rules.
5154 All of the Rules you have defined will be in the list, including
5155 Rules for Indexcolors, Filtering, Roles, Score setting, and Other.
5156 They may not all make sense for this purpose, but they are all there for
5157 flexibility.
5158 Rules may be added by using the Setup/Rules screen off of the main Alpine
5159 menu.
5160 <P>
5161 Unfortunately, Alpine does not allow all possible Rules to be defined.
5162 For example, there is no logical OR operation.
5163 OR is accomplished in the Filter Rules or the other types of Rules by
5164 simply defining two rules, one that matches the first part of the OR
5165 and another that matches the second part.
5166 But you can't do that here, since you only have a single Rule to work with.
5167 Likewise, the order of Rules is usually important.
5168 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5169 a message, then that stops the search for a further match.
5170 This means that you may be confused if you try to use Select by Rule to
5171 check your Filter rules because the order is important when filtering but
5172 is not considered here.
5174 <P>
5175 <End of help on this topic>
5176 </BODY>
5177 </HTML>
5178 ======= h_select_text =======
5179 <HTML>
5180 <HEAD>
5181 <TITLE>Select: Text</TITLE>
5182 </HEAD>
5183 <BODY>
5184 <H1>Select: Text</H1>
5186 You are selecting messages based on the contents of the message.
5187 This allows you to select a set of messages based on whether or not the
5188 message headers or message body contain specified text.
5189 You may look for text in the Subject, the From header,
5190 the To header, or the Cc header.
5191 You may also choose Recipient, which searches for the text in
5192 either the To or the Cc header;
5193 or Participant, which means either the To header, or the Cc header,
5194 or the From header.
5195 Besides those specific header searches, you may also search the entire
5196 header and text of the message with "All Text", or just the
5197 body of the message with "Body".
5198 <P>
5199 To search for the absence of text, first type the "! Not" command
5200 before typing the specific type of text search.
5201 For example, you could type "!" followed by "S" to
5202 search for all messages that do not contain a particular word in their
5203 Subjects.
5204 <P>
5205 If you choose a Subject search, you may use the subject from the current
5206 message by typing the "^X Cur Subject" command.
5207 You may then edit it further if you wish.
5208 For example, you might select the subject of a reply and edit the
5209 "Re: " off of the front of it in order to search for
5210 the original message being replied to.
5211 All of the other header searches allow you to use addresses from the
5212 headers of the current message if you want to.
5213 You may use the "^T Cur To", "^R Cur From", or
5214 "^W Cur Cc".
5215 In each case, if there is more than one address, only the first is offered.
5217 <P>
5218 <End of help on this topic>
5219 </BODY>
5220 </HTML>
5221 ======= h_select_status =======
5222 <HTML>
5223 <HEAD>
5224 <TITLE>Select: Status</TITLE>
5225 </HEAD>
5226 <BODY>
5227 <H1>Select: Status</H1>
5229 You are selecting messages based on the status of the message.
5230 For example, whether or not the message has been marked Deleted or Important,
5231 or whether or not it has been Answered or is New.
5232 If you first type the "! Not" command, you will get the
5233 opposite: not Deleted, not Important, and so on.
5234 <P>
5235 If you select Deleted messages, you will get all messages with their
5236 Deleted flag set.
5237 Likewise for Important messages, all messages that you have flagged as
5238 being Important with the
5239 <A HREF="h_common_flag">Flag</A> command.
5240 The "New" and "Answered" choices are a little bit odd
5241 because they try to match what you see on the screen by default.
5242 "New" is a shorthand for messages that are Unseen, Undeleted,
5243 and Unanswered.
5244 If you have looked at the message, or deleted it, or answered it; then it
5245 is not considered "New ".
5246 "! New" is the opposite of "New".
5247 <P>
5248 "Answered" is another one that is a little different.
5249 It means that the message has been Answered <EM>and</EM> is not deleted.
5250 And to make it even more confusing, "! Answered" is not
5251 the opposite of "Answered"!
5252 Instead, "! Answered" stands for messages that are
5253 both Unanswered <EM>and</EM> not deleted.
5254 <P>
5255 (The New and Answered options may seem counter-intuitive.
5256 The reason it is done this way is
5257 because, by default, a Deleted message will show up with the "D"
5258 symbol in the MAIL INDEX screen even if it is New or Answered.
5259 The Delete symbol overrides the New and Answered symbols, because you
5260 usually don't care about the message anymore once you've deleted it.
5261 Similarly, you usually only care about whether a message is Answered or
5262 not if it is not Deleted.
5263 Once it is Deleted you've put it out of your mind.)
5264 <P>
5265 The other two options were added later because the special nature of the
5266 New flag was not what was wanted by all users.
5267 New does match what you see in the index by default, but if you use
5268 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5269 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5270 be exactly what you expect.
5271 "Unseen" simply selects all unseen messages, whether or not
5272 they are deleted or answered, and
5273 "Recent" selects all of the messages that have been added to
5274 the folder since you started this Alpine session.
5275 (That's not technically quite true. If there are multiple mail clients
5276 reading an IMAP mailbox, each message will be marked as Recent in only
5277 one of the client's sessions.
5278 That behavior can be convenienent for some purposes, like filtering, but
5279 it isn't usually what you expect when selecting.)
5281 <P>
5282 <End of help on this topic>
5283 </BODY>
5284 </HTML>
5285 ======= h_index_cmd_apply =======
5286 <HTML>
5287 <HEAD>
5288 <TITLE>Apply Command</TITLE>
5289 </HEAD>
5290 <BODY>
5291 <H1>Apply Command</H1>
5293 Apply
5294 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->A<!--chtml endif-->)
5295 is the second step of most aggregate operations. Apply
5296 becomes active any time there is a defined set of selected messages. The
5297 following commands can be applied to a selected message set: delete,
5298 undelete, reply, forward,
5299 <!--chtml if pinemode="os_windows"-->
5300 <!--chtml else-->
5301 pipe,
5302 <!--chtml endif-->
5303 print, take address, save, export, bounce, and flag.
5304 <P>
5306 The behavior of some of these commands in an aggregate sense is not easy to
5307 explain. Try them out to see what they do.
5308 The feature
5309 <A HREF="h_config_auto_unzoom">"<!--#echo var="FEAT_auto-unzoom-after-apply"-->"</A>
5310 affects the behavior of the Apply command, as does the feature
5311 <A HREF="h_config_auto_unselect">"<!--#echo var="FEAT_auto-unselect-after-apply"-->"</A>.
5313 <P>
5314 <End of help on this topic>
5315 </BODY>
5316 </HTML>
5317 ======= h_index_cmd_zoom =======
5318 <HTML>
5319 <HEAD>
5320 <TITLE>ZoomMode Command</TITLE>
5321 </HEAD>
5322 <BODY>
5323 <H1>ZoomMode Command</H1>
5325 Another action you might want to take on a set of selected messages is to
5326 zoom in on them. Like apply, zoom only becomes active when messages have
5327 been selected.
5328 ZoomMode
5329 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->Z<!--chtml endif-->)
5330 is a toggle command that allows you to
5331 zoom-in (and only see the selected messages) and zoom-out (to see all
5332 messages in the folder). Neither apply nor zoom removes the markings that
5333 define the selected set; you need to use a select command in order
5334 to do that.
5336 <P>
5337 <End of help on this topic>
5338 </BODY>
5339 </HTML>
5340 ======= h_index_collapse_expand =======
5341 <HTML>
5342 <HEAD>
5343 <TITLE>Collapse/Expand Command</TITLE>
5344 </HEAD>
5345 <BODY>
5346 <H1>Collapse/Expand Command</H1>
5348 The Collapse/Expand command is only available from the MESSAGE INDEX screen when
5349 the folder is sorted by either Threads or OrderedSubject, and the
5350 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
5351 is set to something other than "none".
5352 By default, this command collapses or expands the subthread that starts at
5353 the currently highlighted message, if any.
5354 If the subthread is already collapsed, then this command expands it.
5355 If the subthread is expanded, then this command collapses it.
5356 If there are no more messages below the current message in the
5357 thread tree (that is, there are no replies to the current message) then
5358 this command does nothing.
5360 <P>
5361 The behavior of this command is affected by the option
5362 <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>.
5363 Normally, this command Collapses or Expands the subthread that
5364 starts at the currently highlighted message.
5365 If the above option is set, then this command Collapses or Expands the
5366 entire current thread instead of just the subthread.
5367 The current thread is simply the top-level thread that contains the
5368 current message.
5370 <P>
5371 <End of help on this topic>
5372 </BODY>
5373 </HTML>
5374 ======= h_index_cmd_sort =======
5375 <HTML>
5376 <HEAD>
5377 <TITLE>Sort Command</TITLE>
5378 </HEAD>
5379 <BODY>
5380 <H1>Sort Command</H1>
5382 In Alpine's generic configuration, messages are presented in the order in
5383 which they arrive. This default can be changed in the SETUP CONFIGURATION
5384 with the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
5385 You can also re-sort the folder on demand with the sort
5386 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
5387 command.
5388 Your sorting options are:
5389 <P>
5390 <UL>
5391 <LI> <A HREF="h_index_sort_arrival">A</A>rrival
5392 <LI> <A HREF="h_index_sort_date">D</A>ate
5393 <LI> <A HREF="h_index_sort_subj">S</A>ubject
5394 <LI> <A HREF="h_index_sort_ordsubj">O</A>rderedSubject
5395 <LI> t<A HREF="h_index_sort_thread">H</A>read
5396 <LI> <A HREF="h_index_sort_from">F</A>rom
5397 <LI> si<A HREF="h_index_sort_size">Z</A>e
5398 <LI> scor<A HREF="h_index_sort_score">E</A>,
5399 <LI> <A HREF="h_index_sort_to">T</A>o
5400 <LI> <A HREF="h_index_sort_cc">C</A>c
5401 </UL>
5403 <P>
5404 The Reverse option will toggle the order the index is currently
5405 sorted by, but will not change the relative sort order.
5407 <P>
5408 Sorting a folder does not actually rearrange the way the folder is saved,
5409 it just re-arranges how the messages are presented to you. This means
5410 that Alpine has to do the work of sorting every time you change sort order.
5411 Sometimes, especially with PC-Alpine or with large folders, this could take
5412 a while.
5414 <P>
5415 <End of help on this topic>
5416 </BODY>
5417 </HTML>
5418 ======= h_index_sort_default =======
5419 <HTML>
5420 <HEAD>
5421 <TITLE>SORT OPTION: Default</TITLE>
5422 </HEAD>
5423 <BODY>
5424 <H1>SORT OPTION: Default</H1>
5426 The <EM>Default</EM> sort option just means to use the default sort order
5427 set in the
5428 <li><a href="h_config_sort_key"><!--#echo var="VAR_sort-key"--></a>
5429 option in Setup/Config.
5431 <P>
5432 <End of help on this topic>
5433 </BODY>
5434 </HTML>
5435 ======= h_index_sort_arrival =======
5436 <HTML>
5437 <HEAD>
5438 <TITLE>SORT OPTION: Arrival</TITLE>
5439 </HEAD>
5440 <BODY>
5441 <H1>SORT OPTION: Arrival</H1>
5443 The <EM>Arrival</EM> sort option arranges messages in the MESSAGE INDEX
5444 in the order that they exist in the folder. This is usually the same as the
5445 order in which they arrived. This option is comparable to not sorting
5446 the messages at all.
5448 <P>
5449 <End of help on this topic>
5450 </BODY>
5451 </HTML>
5452 ======= h_index_sort_date =======
5453 <HTML>
5454 <HEAD>
5455 <TITLE>SORT OPTION: Date</TITLE>
5456 </HEAD>
5457 <BODY>
5458 <H1>SORT OPTION: Date</H1>
5460 The <EM>Date</EM> sort option arranges messages in the MESSAGE INDEX
5461 according to the date and time they were
5462 sent.
5464 <P>
5465 On a folder like INBOX, sorting by "Date" should be almost
5466 identical to sorting by "Arrival".
5468 <P>
5469 <End of help on this topic>
5470 </BODY>
5471 </HTML>
5472 ======= h_index_sort_subj =======
5473 <HTML>
5474 <HEAD>
5475 <TITLE>SORT OPTION: Subject</TITLE>
5476 </HEAD>
5477 <BODY>
5478 <H1>SORT OPTION: Subject</H1>
5480 The <EM>Subject</EM> sort option arranges messages in the MESSAGE INDEX
5481 by subject.
5483 <P>
5484 Messages with the same subject are
5485 first grouped together, and then the groups of like-subject messages
5486 are arranged alphabetically.
5488 <P>
5489 Alpine ignores leading "Re:" and
5490 "re:" and trailing "(fwd)" when determining the
5491 likeness and alphabetical order of subject lines.
5493 <P>
5494 <End of help on this topic>
5495 </BODY>
5496 </HTML>
5497 ======= h_index_sort_ordsubj =======
5498 <HTML>
5499 <HEAD>
5500 <TITLE>SORT OPTION: OrderedSubject</TITLE>
5501 </HEAD>
5502 <BODY>
5503 <H1>SORT OPTION: OrderedSubject</H1>
5505 The <EM>OrderedSubject</EM> sort option arranges messages in the
5506 MESSAGE INDEX by grouping all messages with the same subject
5507 together, similar to sort by <A HREF="h_index_sort_subj">S</A>ubject.
5509 <P>
5510 However, <EM>OrderedSubj</EM> then arranges the groups of like-subject
5511 messages by the date of the oldest message in the group.
5513 <P>
5514 This sort method provides for pseudo threading of conversations within
5515 a folder.
5516 You may want to try sorting by Thread instead.
5518 <P>
5519 <End of help on this topic>
5520 </BODY>
5521 </HTML>
5522 ======= h_index_sort_thread =======
5523 <HTML>
5524 <HEAD>
5525 <TITLE>SORT OPTION: Thread</TITLE>
5526 </HEAD>
5527 <BODY>
5528 <H1>SORT OPTION: Thread</H1>
5530 The <EM>Thread</EM> sort option arranges messages in the
5531 MESSAGE INDEX by grouping all messages that indicate
5532 they are part of a conversation (discussion thread) taking
5533 place within a mailbox or newsgroup. This indication is
5534 based on information in the message's header -- specifically
5535 its <tt>References:</tt>, <tt>Message-ID:</tt>, and <tt>Subject:</tt> fields.
5537 <P>
5538 <End of help on this topic>
5539 </BODY>
5540 </HTML>
5541 ======= h_index_sort_from =======
5542 <HTML>
5543 <HEAD>
5544 <TITLE>SORT OPTION: From</TITLE>
5545 </HEAD>
5546 <BODY>
5547 <H1>SORT OPTION: From</H1>
5549 The <EM>From</EM> sort option arranges messages in the MESSAGE INDEX
5550 by the name of the author of the message.
5552 <P>
5553 Messages with the same author are grouped together. Groups of
5554 messages are then put into alphabetical order according to message
5555 author.
5557 <P>
5558 <End of help on this topic>
5559 </BODY>
5560 </HTML>
5561 ======= h_index_sort_size =======
5562 <HTML>
5563 <HEAD>
5564 <TITLE>SORT OPTION: Size</TITLE>
5565 </HEAD>
5566 <BODY>
5567 <H1>SORT OPTION: Size</H1>
5569 The <EM>Size</EM> sort option arranges messages in the MESSAGE INDEX
5570 by their relative sizes.
5572 <P>
5573 <End of help on this topic>
5574 </BODY>
5575 </HTML>
5576 ======= h_index_sort_score =======
5577 <HTML>
5578 <HEAD>
5579 <TITLE>SORT OPTION: Score</TITLE>
5580 </HEAD>
5581 <BODY>
5582 <H1>SORT OPTION: Score</H1>
5584 The <EM>Score</EM> sort option arranges messages in the MESSAGE INDEX
5585 by their scores.
5587 <P>
5588 Messages with the same score are sorted in arrival order.
5589 Scores are something you create using the
5590 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
5592 <P>
5593 <End of help on this topic>
5594 </BODY>
5595 </HTML>
5596 ======= h_index_sort_to =======
5597 <HTML>
5598 <HEAD>
5599 <TITLE>SORT OPTION: To</TITLE>
5600 </HEAD>
5601 <BODY>
5602 <H1>SORT OPTION: To</H1>
5604 The <EM>To</EM> sort option arranges messages in the MESSAGE INDEX
5605 by the names of the recipients of the message.
5607 <P>
5608 Messages with the same recipients are grouped together. Groups of
5609 messages are then put into alphabetical order according to message
5610 recipients.
5612 <P>
5613 <End of help on this topic>
5614 </BODY>
5615 </HTML>
5616 ======= h_index_sort_cc =======
5617 <HTML>
5618 <HEAD>
5619 <TITLE>SORT OPTION: Cc</TITLE>
5620 </HEAD>
5621 <BODY>
5622 <H1>SORT OPTION: Cc</H1>
5624 The <EM>Cc</EM> sort option arranges messages in the MESSAGE INDEX by
5625 the names of the carbon copy addresses of the message.
5627 <P>
5628 <End of help on this topic>
5629 </BODY>
5630 </HTML>
5631 ======= h_index_cmd_whereis =======
5632 <HTML>
5633 <HEAD>
5634 <TITLE>WhereIs Command</TITLE>
5635 </HEAD>
5636 <BODY>
5637 <H1>WhereIs Command</H1>
5639 The WhereIs
5640 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
5641 command lets you search the MESSAGE INDEX for a word.
5642 It scans through whatever you see, usually the name of the author
5643 and the Subject line.
5644 WhereIs has special subcommands to let you find the beginning of the
5645 index (Ctrl-Y -- first message)
5646 or the end of the index (Ctrl-V -- last message).
5647 <P>
5648 Note that WhereIs only searches through the visible text on the screen.
5649 For example, if only part of the Subject of a message is shown because it
5650 is long, then only the visible portion of the Subject is searched.
5651 Also note that WhereIs does not "see" the
5652 "X" in column one of Index entries for selected messages
5653 so it can't be used to search for
5654 selected messages (use "Zoom" instead).
5655 <P>
5656 If the feature
5657 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
5658 is turned on,
5659 WhereIs can also be used as a quick way to select messages that match the
5660 string being searched for.
5661 Instead of typing carriage return to search for the next match, type
5662 Ctrl-X to select all matches.
5663 Once again, this only selects matches that are (or would be if the right
5664 index line was on the screen) visible.
5665 Truncated From lines or Subjects will cause matches to be missed.
5666 Although WhereIs is sometimes convenient for quick matching, the Select
5667 command is usually more powerful and usually faster.
5669 <P>
5670 <End of help on this topic>
5671 </BODY>
5672 </HTML>
5673 ======= h_view_cmd_whereis =======
5674 <HTML>
5675 <HEAD>
5676 <TITLE>WhereIs Command</TITLE>
5677 </HEAD>
5678 <BODY>
5679 <H1>WhereIs Command</H1>
5681 The WhereIs
5682 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
5683 command does a "find in current message" operation. You
5684 type in text and Alpine will try to find it in the message you are
5685 reading. WhereIs also has subcommands to jump to the beginning (Ctrl-Y)
5686 or end (Ctrl-V) of the message.
5687 That is, to rapidly move to the end of a message, hit the
5688 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5689 (or Ctrl-W) key followed
5690 by Ctrl-V. Similarly,
5691 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5692 followed by Ctrl-Y will take you to the beginning of a message.
5694 <P>
5695 <End of help on this topic>
5696 </BODY>
5697 </HTML>
5698 ======= h_view_cmd_hilite =======
5699 <HTML>
5700 <HEAD>
5701 <TITLE>View Hilite and Next item/Previous item</TITLE>
5702 </HEAD>
5703 <BODY>
5704 <H1>View Hilite and Next item/Previous item</H1>
5706 Sometimes messages may be in the form of formatted HTML text
5707 or they may contain URLs or Web server hostnames.
5708 When any of the features
5709 <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>,
5710 <A HREF="h_config_enable_view_web_host">"<!--#echo var="FEAT_enable-msg-view-web-hostnames"-->"</A>,
5711 <A HREF="h_config_enable_view_attach">"<!--#echo var="FEAT_enable-msg-view-attachments"-->"</A>,
5712 or
5713 <A HREF="h_config_enable_view_addresses">"<!--#echo var="FEAT_enable-msg-view-addresses"-->"</A>
5714 are enabled, Alpine will represent such selectable items in the text
5715 in bold typeface. One of the selectable items will be displayed in
5716 inverse video (highlighted). This is the "currently selected" item.
5717 Press the Return key to view the currently selected item.
5718 <P>
5720 The Up and Down Arrows keys can be used to change the selected item
5721 (also see the feature
5722 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
5723 If there are no selectable items in the direction of the arrow you
5724 pressed, Alpine will scroll the display in that direction until one
5725 becomes visible. To "jump" forwards/backwards among selectable
5726 items in the message text, use the Previous and Next item commands,
5727 <!--chtml if pinemode="function_key"-->F5 and F6
5728 <!--chtml else-->^B and ^F<!--chtml endif-->.
5730 <P>
5731 <End of help on this topic>
5732 </BODY>
5733 </HTML>
5734 ======= h_view_cmd_viewattch =======
5735 <HTML>
5736 <HEAD>
5737 <TITLE>ViewAttch Command</TITLE>
5738 </HEAD>
5739 <BODY>
5740 <H1>ViewAttch Command</H1>
5743 The View/Save Attachment
5744 (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->V<!--chtml endif-->)
5745 command allows you to handle MIME attachments to a message you have
5746 received. Alpine shows you a list of the message attachments -- you just
5747 choose the attachment you want. You may either view or save the
5748 selected attachment.
5750 <P>
5751 Because many attachments require external programs for display, there
5752 is some system configuration that has to happen before you can
5753 actually display attachments. Hopefully much of that will have been
5754 done already by your system administrator. MIME configuration is
5755 handled with the "mailcap" configuration file. (See the section
5756 on configuration in the
5757 <A HREF="h_news">release notes</A> for more information.)
5759 <P>
5760 <End of help on this topic>
5761 </BODY>
5762 </HTML>
5763 ======= h_index_cmd_expunge =======
5764 <HTML>
5765 <HEAD>
5766 <TITLE>Expunge/Exclude Command</TITLE>
5767 </HEAD>
5768 <BODY>
5769 <H1>Expunge/Exclude Command</H1>
5771 Expunge/Exclude
5772 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->X<!--chtml endif-->)
5773 is the command Alpine uses to actually remove all messages
5774 marked for deletion. With regular email files, expunge literally deletes
5775 the text from the current folder. With newsgroups or shared mailboxes,
5776 you don't have permission to actually remove the message, so it is an
5777 exclude -- Alpine removes the message from your view of the folder even
5778 though it is not technically gone.
5780 <P> A selective expunge command is available in IMAP folders that support
5781 the UID EXPUNGE extension in <A
5782 HREF="http://tools.ietf.org/html/rfc4315">RFC 4315</A> as well as for all
5783 other folders (local folders in all formats, POP3 inbox, and newsgroups)
5784 as a subcommand of the apply command. If some selected messages are marked
5785 deleted, then the apply command will offer the eXpunge command, which when
5786 executed will only expunge those messages that are selected and deleted.
5788 <P>
5789 Observe that the expunge command (when not used from the apply command)
5790 will expunge/exclude all deleted messages from the folder, and so all
5791 messages marked deleted will be expunged, regardless of if they are
5792 selected or not. In other words, there is no protection against
5793 potentially expunging more messages than only those that have been
5794 selected and deleted.
5795 <P>
5797 The configuration features
5798 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
5799 and
5800 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>
5801 affect the behavior of the Expunge command.
5803 <P>
5804 <End of help on this topic>
5805 </BODY>
5806 </HTML>
5807 ======= h_common_compose =======
5808 <HTML>
5809 <HEAD>
5810 <TITLE>Compose Command</TITLE>
5811 </HEAD>
5812 <BODY>
5813 <H1>Compose Command</H1>
5815 The Compose command takes you into the Alpine message composer where you
5816 can start a new message for sending. This is where you type in the
5817 message's text and specify its recipient list (the "To:"
5818 address), where copies should be directed (e.g., "Fcc",
5819 "Cc:" or "Bcc:"), and which files, if any, should
5820 be attached to the message.
5822 <P>
5823 When you type this command, Alpine will also automatically check for any
5824 interrupted (i.e., a message that was being composed when your modem
5825 or network connection was broken) or previously postponed messages and
5826 offer you a chance to continue working on those.
5828 <P>
5829 <UL>
5830 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5831 </UL><P>
5832 <End of help on this topic>
5833 </BODY>
5834 </HTML>
5835 ======= h_common_index =======
5836 <HTML>
5837 <HEAD>
5838 <TITLE>Message Index Command</TITLE>
5839 </HEAD>
5840 <BODY>
5841 <H1>Message Index Command</H1>
5843 The Index command takes you to the MESSAGE INDEX screen that displays a
5844 summary caption for each message in the currently-open folder. One
5845 message will be highlighted; this is the "Current" message.
5846 The message commands available from this screen (e.g. View, Reply,
5847 Forward, Delete, Print, Save, etc) apply to the current message.
5849 <P>
5850 <End of help on this topic>
5851 </BODY>
5852 </HTML>
5853 ======= h_common_folders =======
5854 <HTML>
5855 <HEAD>
5856 <TITLE>Folder List Command</TITLE>
5857 </HEAD>
5858 <BODY>
5859 <H1>Folder List Command</H1>
5861 This Folder List command takes you to the FOLDER LIST screen that displays
5862 the names of all your message folders and allows you to view, rename,
5863 delete, and add folders. You can open (view) a different folder than the
5864 one currently open by highlighting the desired one (using the arrow keys
5865 or their control-key equivalents) and pressing RETURN.
5867 <P>
5868 If you have multiple folder collections defined (see the Help text for
5869 the FOLDER LIST screen to learn more about Collections), you may need
5870 to press Return to expand the collection and display all of the
5871 folders in it.
5873 <P>
5874 <End of help on this topic>
5875 </BODY>
5876 </HTML>
5877 ======= h_main_addrbook =======
5878 <HTML>
5879 <HEAD>
5880 <TITLE>Address Book Command</TITLE>
5881 </HEAD>
5882 <BODY>
5883 <H1>Address Book Command</H1>
5885 This command, available only from the MAIN MENU, takes you
5886 to the ADDRESS BOOK management screen. From here, your personal address
5887 book(s) may be updated.
5889 <P>
5890 <End of help on this topic>
5891 </BODY>
5892 </HTML>
5893 ======= h_main_setup =======
5894 <HTML>
5895 <HEAD>
5896 <TITLE>Setup Command</TITLE>
5897 </HEAD>
5898 <BODY>
5899 <H1>Setup Command</H1>
5901 The Setup command, available only from the MAIN MENU, prompts you for
5902 one of several configuration screens, including the SETUP CONFIGURATION
5903 screen, by which you may activate optional Alpine features.
5905 <P>
5906 <End of help on this topic>
5907 </BODY>
5908 </HTML>
5909 ======= h_main_release_notes =======
5910 <HTML>
5911 <HEAD>
5912 <TITLE>Release Notes Command</TITLE>
5913 </HEAD>
5914 <BODY>
5915 <H1>Release Notes Command</H1>
5917 This command displays information about Alpine <!--#echo var="ALPINE_VERSION"-->,
5918 as well as pointers to further information such as history and legal notes.
5920 <P>
5921 <End of help on this topic>
5922 </BODY>
5923 </HTML>
5924 ======= h_main_kblock =======
5925 <HTML>
5926 <HEAD>
5927 <TITLE>Keyboard Lock Command</TITLE>
5928 </HEAD>
5929 <BODY>
5930 <H1>Keyboard Lock Command</H1>
5932 This command allows your Alpine session to be protected
5933 during a temporary absence from your terminal.
5935 <P>
5936 <End of help on this topic>
5937 </BODY>
5938 </HTML>
5939 ======= h_main_journal =======
5940 <HTML>
5941 <HEAD>
5942 <TITLE>Journal Command</TITLE>
5943 </HEAD>
5944 <BODY>
5945 <H1>Journal Command</H1>
5947 This command displays a list of all the status messages Alpine has
5948 displayed (on the third line from the bottom of the screen). This may
5949 be useful if a message disappeared before you had a chance to read it.
5951 <P>
5952 <End of help on this topic>
5953 </BODY>
5954 </HTML>
5955 ======= h_common_role =======
5956 <HTML>
5957 <HEAD>
5958 <TITLE>Role Command</TITLE>
5959 </HEAD>
5960 <BODY>
5961 <H1>Role Command</H1>
5963 The Role command is similar to the Compose command except that it starts
5964 off by letting you select a <A HREF="h_rules_roles">role</A>
5965 to be used for the composition.
5966 You may set up alternate roles by using Setup/Rules/Roles.
5968 <P>
5969 <End of help on this topic>
5970 </BODY>
5971 </HTML>
5972 ======= h_common_conditional_cmds =======
5973 <HTML>
5974 <HEAD>
5975 <TITLE>Conditional Commands</TITLE>
5976 </HEAD>
5977 <BODY>
5978 <H1>Conditional Commands</H1>
5980 The presence or absence of certain commands, particularly in the
5981 MESSAGE INDEX and MESSAGE TEXT screens, is determined by
5982 whether or not specific features are set in your Alpine configuration.
5983 (You can access the SETUP CONFIGURATION screen, where they are found, from
5984 Alpine's MAIN MENU.) To see if a desired command's availability is
5985 conditioned on a feature setting, see the command's help text (highlight
5986 the phrase associated with the command and hit Return).
5988 <P>
5989 Also note that some
5990 commands may be administratively disabled by your system manager;
5991 if they don't work, please check with your local help desk.
5993 <P>
5994 <UL>
5995 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5996 </UL><P>
5997 <End of help on this topic>
5998 </BODY>
5999 </HTML>
6000 ======= h_common_pipe =======
6001 <HTML>
6002 <HEAD>
6003 <TITLE>Pipe Command</TITLE>
6004 </HEAD>
6005 <BODY>
6006 <H1>Pipe Command</H1>
6008 Pipe
6009 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->|<!--chtml endif-->)
6010 allows you to send a message to a specified Unix command for external
6011 processing.
6012 This command's availability is controlled by the
6013 <A HREF="h_config_enable_pipe">"<!--#echo var="FEAT_enable-unix-pipe-cmd"-->"</A>
6014 feature.
6015 By default, the processed text of the message is sent to the command
6016 you specify and the output is captured by Alpine and shown to you.
6017 When you run the pipe command, there are some sub-commands which may be
6018 used to alter this behavior.
6019 These sub-commands are described <A HREF="h_pipe_command">here</A>.
6021 <P>
6022 <End of help on this topic>
6023 </BODY>
6024 </HTML>
6025 ======= h_common_goto =======
6026 <HTML>
6027 <HEAD>
6028 <TITLE>Goto Command</TITLE>
6029 </HEAD>
6030 <BODY>
6031 <H1>Goto Command</H1>
6033 Goto
6034 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->G<!--chtml endif-->)
6035 is the command that lets you bypass Alpine's folder selection screens
6036 and jump directly to a new folder. You can select any folder in the
6037 world: one in your current collection, one in a different collection or
6038 one in a collection you've never even used before.
6039 <P>
6041 Alpine will help you as much as possible to narrow in on the folder you want.
6042 However, if the folder is outside of your defined collections, you are
6043 going to have to enter the exact folder location using the correct
6044 <A HREF="h_valid_folder_names">syntax</A>
6045 for a remote folder and/or fully-qualified path name.
6047 <P>
6048 <End of help on this topic>
6049 </BODY>
6050 </HTML>
6051 ======= h_common_nextnew =======
6052 <HTML>
6053 <HEAD>
6054 <TITLE>NextNew Command</TITLE>
6055 </HEAD>
6056 <BODY>
6057 <H1>NextNew Command</H1>
6059 When you press the TAB key, Alpine advances to the next
6060 "interesting" message.
6061 This will be the next message you have not seen before, or the next message
6062 you have flagged Important, whichever comes first.
6063 Unread messages that have been deleted are not considered interesting.
6064 (A note about reading news. Alpine expects you to "Delete" news
6065 articles after you have read them if you want to remove them from future
6066 consideration. See <A HREF="h_mainhelp_readingnews">Reading News</A> for
6067 more information.)
6069 <P>
6070 The NextNew command is affected by the feature
6071 <A HREF="h_config_tab_new_only">"<!--#echo var="FEAT_tab-visits-next-new-message-only"-->"</A>,
6072 which causes Alpine to only consider Unread messages interesting, not messages
6073 flagged Important.
6075 <P>
6076 This command behaves a little differently when it finds there are no more
6077 interesting messages left in the current folder.
6078 If the current folder is one of your Incoming Message Folders
6079 (<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>)
6080 or it is a newsgroup, then Alpine will try to find the next folder or
6081 newsgroup that contains <EM>Recent</EM> messages and will ask you
6082 if you want to open that folder.
6083 This behavior may be modified by using the
6084 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
6085 feature that causes Alpine to look for Unseen messages instead of Recent
6086 messages.
6087 The NextNew command's behavior is also affected by the configuration features
6088 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A>,
6089 and
6090 <A HREF="h_config_tab_no_prompt">"<!--#echo var="FEAT_continue-tab-without-confirm"-->"</A>.
6092 <P>
6093 <End of help on this topic>
6094 </BODY>
6095 </HTML>
6096 ======= h_common_jump =======
6097 <HTML>
6098 <HEAD>
6099 <TITLE>Jump Command</TITLE>
6100 </HEAD>
6101 <BODY>
6102 <H1>Jump Command</H1>
6104 This is Alpine's way of allowing you to go straight to a specific message.
6105 Just press "J" and then enter the message number. By default, Alpine is also
6106 configured such that typing in any number automatically jumps you to that
6107 message
6108 (<A HREF="h_config_enable_jump">"<!--#echo var="FEAT_enable-jump-shortcut"-->"</A>
6109 in the SETUP CONFIGURATION).
6111 <P>
6112 <End of help on this topic>
6113 </BODY>
6114 </HTML>
6115 ======= h_common_flag =======
6116 <HTML>
6117 <HEAD>
6118 <TITLE>Flag Command</TITLE>
6119 </HEAD>
6120 <BODY>
6121 <H1>Flag Command</H1>
6123 Flag
6124 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6125 is the command that allows users to manipulate the status flags that
6126 appear on the left side of the MESSAGE INDEX screen. The most common
6127 use of this is to mark a message as important. This is something of a
6128 note to yourself to get back to that message. You may also use the
6129 flag command to set (or unset) the flags that indicate that a message
6130 is new, answered, deleted, or forwarded.<P>
6132 Provided the mail server supports it,
6133 you may also manipulate user-defined keywords
6134 for a message using the flag command.
6135 These keywords will be available if you use the Flag Details screen that you
6136 can get to after typing the
6137 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6138 command.
6139 They will be listed after the Important, New, Answered, Deleted , and Forwarded flags,
6140 which are always present.
6141 You may add new keywords by using the Add KW command from the Flag Details screen
6142 or by defining them in the <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
6144 The availability of the flag command is determined by the
6145 <A HREF="h_config_enable_flag">"<!--#echo var="FEAT_enable-flag-cmd"-->"</A>
6146 feature in your Alpine configuration. Also, it is possible that Flag could be
6147 administratively disabled by your system manager; if it doesn't work,
6148 please check with your local help desk before reporting a bug.
6149 The behavior of the flag command may be modified by the
6150 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
6151 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
6153 <P>
6154 <End of help on this topic>
6155 </BODY>
6156 </HTML>
6157 ======= h_common_hdrmode =======
6158 <HTML>
6159 <HEAD>
6160 <TITLE>HdrMode Command</TITLE>
6161 </HEAD>
6162 <BODY>
6163 <H1>HdrMode Command</H1>
6165 Every email message comes with some header lines that you normally
6166 don't see (and don't want to see).
6167 These include anywhere from 3-20 lines (or more) added by the
6168 Internet mail transport system to record the route your message took,
6169 for diagnostic purposes.
6170 These are normally of no import and simply
6171 add clutter, so Alpine suppresses them in the MESSAGE TEXT display.
6172 This also includes other non-standard headers the message may contain.
6173 If you want to see these headers, there is a way to reveal them.
6174 <P>
6176 The Header Mode
6177 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6178 command is a toggle that controls Alpine's handling of these header
6179 lines. Normally, full headers is "off" and you only see a
6180 few lines about who a message is to and who it is from. When you
6181 press
6182 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6183 to turn full headers on, Alpine will show you
6184 the normal header lines as well as delivery headers, comment headers,
6185 MIME headers, and any other headers present.
6186 <P>
6188 Several different Alpine commands honor the header mode -- it affects how
6189 messages are displayed, how they appear in forward and reply email, how
6190 they are printed, how they are saved, and how they are exported.
6191 <!--chtml if pinemode="os_windows"-->
6192 <!--chtml else-->
6193 The pipe command is also affected.
6194 <!--chtml endif-->
6195 <P>
6197 The presence or absence of the Header Mode command is determined by the
6198 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
6199 Feature-List option in your Alpine configuration.
6201 <P>
6202 If you have also turned on the
6203 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
6204 option then the HdrMode command actually rotates through three states
6205 instead of just two.
6206 The first is the normal view with long quotes suppressed.
6207 The second is the normal view but with the long quotes included.
6208 The last enables the display of all headers in the message.
6209 When using Export, Pipe, Print, Forward, or Reply the quotes are
6210 never suppressed, so the first two states are identical.
6212 <P>
6213 The behavior of the Header Mode command may be altered slightly by
6214 turning on the
6215 <A HREF="h_config_quell_full_hdr_reset">"<!--#echo var="FEAT_quell-full-header-auto-reset"-->"</A>
6216 Feature-List option in your Alpine configuration.
6217 In particular, it will cause the Header Mode to be persistent when moving
6218 from message to message instead of resetting to the default for each message.
6220 <P>
6221 <UL>
6222 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6223 </UL><P>
6224 <End of help on this topic>
6225 </BODY>
6226 </HTML>
6227 ======= h_common_print =======
6228 <HTML>
6229 <HEAD>
6230 <TITLE>Print Command</TITLE>
6231 </HEAD>
6232 <BODY>
6233 <H1>Print Command</H1>
6235 The Print
6236 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->%<!--chtml endif-->)
6237 command allows you to print a copy of a message.
6238 There are many SETUP CONFIGURATION features that affect the
6239 Print command, including
6240 <A HREF="h_config_enable_y_print">"<!--#echo var="FEAT_enable-print-via-y-command"-->"</A>,
6241 <A HREF="h_config_print_index">"<!--#echo var="FEAT_print-index-enabled"-->"</A>,
6242 <A HREF="h_config_custom_print">"<!--#echo var="FEAT_print-offers-custom-cmd-prompt"-->"</A>,
6243 <A HREF="h_config_print_from">"<!--#echo var="FEAT_print-includes-from-line"-->"</A>, and
6244 <A HREF="h_config_ff_between_msgs">"<!--#echo var="FEAT_print-formfeed-between-messages"-->"</A>.
6245 You set up for printing by using the Printer option of the Setup command
6246 on the MAIN MENU.
6247 <P>
6249 <P>
6250 <End of help on this topic>
6251 </BODY>
6252 </HTML>
6253 ======= h_common_take =======
6254 <HTML>
6255 <HEAD>
6256 <TITLE>TakeAddr Command</TITLE>
6257 </HEAD>
6258 <BODY>
6259 <H1>TakeAddr Command</H1>
6262 With the Take Address
6263 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->T<!--chtml endif-->)
6264 command, you can extract email addresses from an
6265 incoming message and save them in an address book. This is an easy way
6266 to add to your address book and avoid having to remember the email
6267 addresses of the people who write to you.
6268 <P>
6270 If the message is just to you individually, then you will only need to
6271 provide a nickname. If the message contains more than one email address,
6272 then you will see an address
6273 selection screen that lets you choose the address you want to save into
6274 your address book, or lets you choose several of them add to a
6275 personal distribution list.
6276 <P>
6278 Once you've added an entry to your address book, you can use it from the
6279 message composer by typing the nickname of the entry into one of the
6280 header fields (for example, into the To: field), or you can use ^T from
6281 the header field to select the entry from your address book.
6282 <P>
6284 If the configuration feature
6285 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
6286 is set, the behavior of the Take command is altered slightly.
6288 <P>
6289 <End of help on this topic>
6290 </BODY>
6291 </HTML>
6292 ======= h_ge_import =======
6293 <HTML>
6294 <HEAD>
6295 <TITLE>Import File Selection</TITLE>
6296 </HEAD>
6297 <BODY>
6298 <H1>Import File Selection</H1>
6300 You are importing a file that you previously
6301 exported from Alpine.
6302 You are now being asked for the name of that file.
6303 The easiest way to select a file is probably with the "^T"
6304 "To Files" command.
6305 Alternatively, you may type in a file name.
6306 It may be an absolute pathname.
6307 Otherwise, it is a file located in your home directory
6308 or current working directory
6309 <!--chtml if pinemode="running"-->
6310 (which, at least for your current Alpine "session,"
6311 is "<!--#echo var="CURRENT_DIR"-->")
6312 <!--chtml endif-->, depending on the
6313 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6314 In any case, you finish by typing a carriage return to accept the
6315 file name that is displayed.
6316 When the feature
6317 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6318 is turned on you may use TAB to complete partially typed in names.
6319 <P>
6320 You may cancel the import operation by typing "^C" after exiting
6321 this help.
6322 <P>
6323 <End of help on this topic>
6324 </BODY>
6325 </HTML>
6326 ======= h_ge_allparts =======
6327 <HTML>
6328 <HEAD>
6329 <TITLE>Export Message File Selection</TITLE>
6330 </HEAD>
6331 <BODY>
6332 <H1>Export Message File Selection</H1>
6334 You are Exporting a message from an Alpine mail folder
6335 to a plain text file.
6336 You also have the option of exporting all of the attachments associated
6337 with the message.
6338 You are now being asked for the name of the file to export <EM>to</EM>.
6339 The easiest way to select a file is probably with the "^T"
6340 "To Files" subcommand.
6341 After returning from that subcommand you will still be allowed to
6342 edit the name you have selected.
6343 Alternatively, you may type in a file name.
6344 It may be an absolute pathname.
6345 Otherwise, it is a file located in your home directory
6346 or current working directory
6347 <!--chtml if pinemode="running"-->
6348 (which, at least for your current Alpine "session,"
6349 is "<!--#echo var="CURRENT_DIR"-->")
6350 <!--chtml endif-->, depending on the
6351 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6352 In any case, you finish by typing a carriage return to accept the
6353 file name that is displayed.
6354 When the feature
6355 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6356 is turned on you may use TAB to complete partially typed in names.
6357 <P>
6358 The message you are exporting appears to have some attachments.
6359 If you wish to save <EM>all</EM> of the attachments at once,
6360 type the "^P" "AllParts" command to turn on
6361 saving of the attachments.
6362 You may turn it back off by typing "^P" again, which will now
6363 be labeled "NoAllParts" instead.
6364 If you want to save the parts the command displayed should be
6365 "NoAllParts"!
6366 When you choose to save attachments like this, the attachments will be saved
6367 in a newly created directory.
6368 That directory will have the same name as the file name you choose here,
6369 with the letters ".d" appended.
6370 If that directory already exists, then the letters ".d_1" will
6371 be tried, then ".d_2" and so on until a name that doesn't exist
6372 is found.
6373 For example, if you select the file name
6374 <P>
6375 <CENTER><SAMP>filename</SAMP></CENTER>
6376 <P>
6377 to export the message to, then the directory used for the attachments will be
6378 <P>
6379 <CENTER><SAMP>filename.d</SAMP></CENTER>
6380 <P>
6381 or perhaps
6382 <P>
6383 <CENTER><SAMP>filename.d_<n></SAMP></CENTER>
6384 <P>
6385 The attachments will then be put into files inside that directory.
6386 The names for the attachment files will be derived from the attachments
6387 if possible.
6388 This is done in the same way as the default values are derived if you
6389 save them one at a time.
6390 (The "filename" parameter from the Content-Disposition header
6391 is the first choice. If that doesn't exist, the "name"
6392 parameter from the Content-Type header is used.)
6393 If a name for a particular attachment is not available, then the
6394 part number of the attachment is used, with the characters "part_"
6395 prepended.
6396 An example of that would be
6397 <P>
6398 <CENTER><SAMP>part_2.1</SAMP></CENTER>
6399 <P>
6400 If you want to save only some of the attachments or if you want more control
6401 over the directory and filename where an attachment is saved you may
6402 cancel out of this command and View the attachment list.
6403 From there you can save each attachment individually.
6404 <P>
6405 You may cancel the Export operation by typing "^C" after exiting
6406 this help.
6407 <P>
6408 <End of help on this topic>
6409 </BODY>
6410 </HTML>
6411 ======= h_ge_export =======
6412 <HTML>
6413 <HEAD>
6414 <TITLE>Export File Selection</TITLE>
6415 </HEAD>
6416 <BODY>
6417 <H1>Export File Selection</H1>
6419 You are Exporting or Saving something from within the Alpine world
6420 (a message, an attachment, etc.)
6421 to a plain text file.
6422 You are now being asked for the name of the file to export <EM>to</EM>.
6423 The easiest way to select a file is probably with the "^T"
6424 "To Files" subcommand.
6425 After returning from that subcommand you will still be allowed to
6426 edit the name you have selected.
6427 Alternatively, you may type in a file name.
6428 It may be an absolute pathname.
6429 Otherwise, it is a file located in your home directory
6430 or current working directory
6431 <!--chtml if pinemode="running"-->
6432 (which, at least for your current Alpine "session,"
6433 is "<!--#echo var="CURRENT_DIR"-->")
6434 <!--chtml endif-->, depending on the
6435 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6436 In any case, you finish by typing a carriage return to accept the
6437 file name that is displayed.
6438 When the feature
6439 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6440 is turned on you may use TAB to complete partially typed in names.
6441 <P>
6442 If the object you are exporting is a message with some attachments,
6443 you may wish to save all of the attachments by typing the "^P"
6444 "AllParts" command to turn on saving of the attachments.
6445 This subcommand will only be visible if the message actually has attachments.
6446 You may also View the attachment list and save individual attachments from
6447 there.
6448 <P>
6449 You may cancel the Export operation by typing "^C" after exiting
6450 this help.
6451 <P>
6452 <End of help on this topic>
6453 </BODY>
6454 </HTML>
6455 ======= h_common_save =======
6456 <HTML>
6457 <HEAD>
6458 <TITLE>Save and Export Commands</TITLE>
6459 </HEAD>
6460 <BODY>
6461 <H1>Save and Export Commands</H1>
6463 Save
6464 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->S<!--chtml endif-->)
6465 and Export
6466 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->E<!--chtml endif-->)
6467 are the two alternatives Alpine gives you to keep a copy of the message
6468 you are reading. If you want to keep the message within Alpine's email
6469 world, use "Save"; if you want to use the message in another
6470 program, use "Export".
6471 <P>
6473 When you Save a message, it is put into an existing folder or into a new
6474 folder in one of your existing folder collections. The message stays in
6475 email format and can be read by Alpine again. Alpine may use a special format
6476 for its mail folders -- never edit an Alpine folder by hand or with any
6477 program other than Alpine. The exact behavior of the Save command can be
6478 configured with the
6479 <A HREF="h_config_quote_all_froms">"<!--#echo var="FEAT_save-will-quote-leading-froms"-->"</A>,
6480 <A HREF="h_config_save_wont_delete">"<!--#echo var="FEAT_save-will-not-delete"-->"</A>,
6481 and
6482 <A HREF="h_config_save_advances">"<!--#echo var="FEAT_save-will-advance"-->"</A>
6483 feature list settings.
6484 The name of the folder offered as a default is controlled by the option
6485 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>.
6486 <P>
6488 When you use Export, the message is placed in a plain text file in your
6489 home directory
6490 <!--chtml if pinemode="running"-->
6491 (which, in the present configuration of your system, is
6492 "<!--#echo var="HOME_DIR"-->")
6493 <!--chtml endif-->
6494 or current working directory
6495 <!--chtml if pinemode="running"-->
6496 (which, at least for your current Alpine "session,"
6497 is "<!--#echo var="CURRENT_DIR"-->")
6498 <!--chtml endif-->, depending on the
6499 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
6500 configuration setting. In the normal case, only minimal
6501 headers are exported with the message; however, if the full header mode
6502 (whose availability may be disabled by setting the feature
6503 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
6504 in SETUP CONFIGURATION) is
6505 toggled on, then complete headers are exported along with the message
6506 text. (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
6507 defined, they may affect the contents of the exported file.)
6509 <P>
6510 <End of help on this topic>
6511 </BODY>
6512 </HTML>
6513 ======= h_common_bounce =======
6514 <HTML>
6515 <HEAD>
6516 <TITLE>Bounce Command</TITLE>
6517 </HEAD>
6518 <BODY>
6519 <H1>Bounce Command</H1>
6521 The Bounce
6522 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->B<!--chtml endif-->)
6523 command allows you to re-send, or "remail", a
6524 message, as if you were never in the loop. It is analogous to crossing
6525 out your address on a postal letter, writing a different address on the
6526 envelope, and putting it into the mailbox. Bounce is used primarily to
6527 redirect email that was sent to you in error.
6528 Also, some owners of email
6529 lists need the bounce command to handle list traffic.
6530 Bounce is not anonymous.
6531 A ReSent-From header is added to the message so that the recipient may
6532 tell that you Bounced it to them.
6533 <P>
6535 The presence or absence of the Bounce command is determined by the
6536 <A HREF="h_config_enable_bounce">"<!--#echo var="FEAT_enable-bounce-cmd"-->"</A>
6537 feature in your Alpine configuration.
6538 The feature
6539 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A>
6540 affects the behavior of the Bounce command.
6541 Also, it is possible that Bounce could be
6542 administratively disabled by your system manager; if it doesn't work,
6543 please check with your local help desk before reporting a bug.
6545 <P>
6546 <End of help on this topic>
6547 </BODY>
6548 </HTML>
6549 ======= h_common_reply =======
6550 <HTML>
6551 <HEAD>
6552 <TITLE>Reply and Forward Commands</TITLE>
6553 </HEAD>
6554 <BODY>
6556 <H1>Reply and Forward Commands</H1>
6558 Replying
6559 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->R<!--chtml endif-->)
6560 and Forwarding
6561 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->F<!--chtml endif-->)
6562 are your two alternatives for following up on the
6563 message you are reading. You would use reply if you want to get email
6564 back to the author of the message and/or the other people who have
6565 already seen it. You use forward if you want somebody new to see the
6566 message.
6567 <P>
6569 In the normal case, the only thing that you must supply when forwarding a
6570 message is the name/email address of the new recipient.
6571 Alpine will include the text of the forwarded message.
6572 Alpine will also include any attachments to the message.
6573 There is space above the forwarded text for you to include additional comments.
6574 <P>
6576 When replying, you usually have to answer some questions.
6577 If the message is to multiple people and/or specified with a Reply-To: header,
6578 then you will have to decide who should get the reply.
6579 You also need to decide whether or not to include the previous
6580 message in your reply.
6581 Some of this is configurable.
6582 Specifically, see the
6583 <A HREF="h_config_include_header">"<!--#echo var="FEAT_include-header-in-reply"-->"</A>,
6584 <A HREF="h_config_auto_include_reply">"<!--#echo var="FEAT_include-text-in-reply"-->"</A>,
6585 <A HREF="h_config_attach_in_reply">"<!--#echo var="FEAT_include-attachments-in-reply"-->"</A>,
6586 and
6587 <A HREF="h_config_auto_reply_to">"<!--#echo var="FEAT_reply-always-uses-reply-to"-->"</A>
6588 configuration features.
6589 <P>
6591 Both the Reply and Forward commands react to the full header mode toggle.
6592 If the full header mode is on, then all the header and delivery lines are
6593 included with the text of the message in your reply/forward.
6594 <P>
6596 Other configuration features that affect the Reply command are
6597 <A HREF="h_config_sig_at_bottom">"<!--#echo var="FEAT_signature-at-bottom"-->"</A>,
6598 <A HREF="h_config_sigdashes">"<!--#echo var="FEAT_enable-sigdashes"-->"</A>, and
6599 <A HREF="h_config_strip_sigdashes">"<!--#echo var="FEAT_strip-from-sigdashes-on-reply"-->"</A>.
6601 <P>
6602 <End of help on this topic>
6603 </BODY>
6604 </HTML>
6605 ======= h_common_delete =======
6606 <HTML>
6607 <HEAD>
6608 <TITLE>Delete and Undelete Commands</TITLE>
6609 </HEAD>
6610 <BODY>
6611 <H1>Delete and Undelete Commands</H1>
6613 Delete
6614 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->D<!--chtml endif-->)
6615 and Undelete
6616 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->U<!--chtml endif-->)
6617 allow you to change the Deleted flag for the current message.
6618 Delete marks a message Deleted (turns on the Deleted flag) and Undelete
6619 removes the mark.
6620 In the MESSAGE INDEX, deleted messages have a "D" in the status field
6621 at the left hand edge of the index line.
6622 When viewing a deleted message, the letters "DEL" will be present
6623 in the upper right hand corner of the screen.
6624 Delete simply <EM>marks</EM> a message Deleted, it does not actually
6625 get rid of the message.
6626 The eXpunge command (available from the MESSAGE INDEX screen) actually
6627 removes all of the deleted messages in a folder.
6628 Once a message is eXpunged, it can't be retrieved.
6629 <P>
6631 The Delete command is affected by the setting of the configuration feature
6632 <A HREF="h_config_del_skips_del">"<!--#echo var="FEAT_delete-skips-deleted"-->"</A>.
6634 <P>
6635 <End of help on this topic>
6636 </BODY>
6637 </HTML>
6638 ======= h_common_postpone =======
6639 <HTML>
6640 <HEAD>
6641 <TITLE>Postpone Command</TITLE>
6642 </HEAD>
6643 <BODY>
6644 <H1>Postpone Command</H1>
6646 The postpone
6647 <!--chtml if pinemode="function_key"-->(F11)<!--chtml else-->(^O)<!--chtml endif-->
6648 command allows you to temporarily stop working on the current
6649 message so you may read
6650 other messages or compose another message. When you want to resume a
6651 message later, start to compose and answer "yes" to the
6652 "Continue postponed composition?" question. You may
6653 postpone as many messages as you like.
6655 <P>
6656 Note: If a <A HREF="h_config_form_folder"><!--#echo var="VAR_form-letter-folder"--></A> is defined
6657 in the Setup/Config screen, then the Postpone command will prompt you for
6658 the folder in which to store your outgoing message.
6660 <P>
6661 <End of help on this topic>
6662 </BODY>
6663 </HTML>
6664 ======= h_compose_cancel =======
6665 <HTML>
6666 <HEAD>
6667 <TITLE>Cancel Command</TITLE>
6668 </HEAD>
6669 <BODY>
6670 <H1>Cancel Command</H1>
6672 Cancel
6673 <!--chtml if pinemode="function_key"-->
6674 (F2)
6675 <!--chtml else-->
6676 (^C)
6677 <!--chtml endif-->
6679 The Cancel command returns you to Alpine's normal mail processing and
6680 causes the message currently under composition to be thrown out.
6681 The message text <EM>will be lost</EM>.
6683 <P>
6684 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
6685 will be preserved in the file named
6686 <!--chtml if pinemode="os_windows"-->
6687 "DEADLETR".
6688 <!--chtml else-->
6689 "dead.letter" in your home directory.
6690 <!--chtml endif-->
6691 If you unintentionally cancel a message, look there for its text.
6693 <P>
6694 <End of help on this topic>
6695 </BODY>
6696 </HTML>
6697 ======= h_compose_addrcomplete =======
6698 <HTML>
6699 <HEAD>
6700 <TITLE>Address Completion</TITLE>
6701 </HEAD>
6702 <BODY>
6703 <H1>Address Completion</H1>
6705 When entering addresses in the address fields of the composer (To, Cc, etc.)
6706 the TAB key may be used to help complete the address.
6707 Type a partial nickname and tap the TAB key to complete the typing.
6708 The unambiguous part of the name will be filled in automatically.
6709 Typing TAB twice in succession will bring up a selection list of possibilities,
6710 making it easy to find and choose the correct address.
6712 <P>
6713 The matching algorithm is rather ad hoc.
6714 The search starts with a search of your address book.
6715 It counts as a match if the nickname, address, or fullname field of an
6716 entry begins with the text typed in so far. It is also a match if
6717 a later word in the fullname (for example, the middle name or last name)
6718 begins with the entered text.
6719 <P>
6720 Next comes an LDAP search.
6721 The search will happen for any servers that have the
6722 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
6723 feature set. You can set or unset the feature for each server independently
6724 in the Setup/Directory screen.
6725 <P>
6726 Finally, if you are replying to or forwarding a message, that message is
6727 searched for likely candidate addresses that match the typed-in text.
6729 <P>
6730 <End of help on this topic>
6731 </BODY>
6732 </HTML>
6733 ======= h_compose_richhdr =======
6734 <HTML>
6735 <HEAD>
6736 <TITLE>Rich Header Command</TITLE>
6737 </HEAD>
6738 <BODY>
6739 <H1>Rich Header Command</H1>
6741 The Rich Header command allows you to toggle between the list of
6742 all message headers available for editing and those that are most
6743 common.
6745 <P>
6746 Use this toggle to expose headers that are not normally visible by
6747 default.
6748 This set usually includes the
6749 "Bcc:",
6750 "Fcc:",
6751 "Lcc:",
6752 and "Newsgroups"
6753 headers.
6754 If you are posting to a newsgroup the set of defaults is a little different.
6755 Obviously, in that case, the Newsgroups header is of interest so is not
6756 hidden.
6757 For news posting the hidden set includes the
6758 "To:",
6759 "Cc:",
6760 "Bcc:",
6761 "Fcc:",
6762 and "Lcc:"
6763 headers.
6764 You won't normally want to edit these, which is why they are hidden,
6765 but it is sometimes useful to be able to set them manually.
6767 <P>
6768 The default sets of headers listed above can be altered.
6769 Any header that you have added to the
6770 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
6771 option, but not to the
6772 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
6773 option will appear when you use the Rich Headers command to
6774 make the Rich Headers visible.
6775 (Headers listed in the <!--#echo var="VAR_default-composer-hdrs"--> list will be visible
6776 even without toggling the Rich Headers command.)
6778 <P>
6779 <End of help on this topic>
6780 </BODY>
6781 </HTML>
6782 ======= h_compose_send =======
6783 <HTML>
6784 <HEAD>
6785 <TITLE>Send Command</TITLE>
6786 </HEAD>
6787 <BODY>
6788 <H1>Send Command</H1>
6790 The Send command
6791 <!--chtml if pinemode="function_key"-->
6792 (F3)
6793 <!--chtml else-->
6794 (^X)
6795 <!--chtml endif-->
6796 tells Alpine you are finished composing.
6797 Before actually sending it, though, Alpine will ask you to confirm
6798 your intention, and, at the same time, redisplayed the message text
6799 with the recipients at the top of the screen to give you the opportunity
6800 to review and verify that the message is addressed to the people
6801 you intended.
6802 <P>
6803 If the feature
6804 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
6805 then this confirmation prompt and any options it allows are skipped.
6807 <P>
6808 This confirmation prompt may also offer, depending
6809 on your particular Setup/Config, options allowing you to set
6810 <A HREF="h_config_compose_dsn">delivery status notifications</A>,
6811 include attachments in the "Fcc" (if you had previously
6812 specified that they <A HREF="h_config_no_fcc_attach">exclude attachments</A>,
6813 observe details of the
6814 <A HREF="h_config_verbose_post">message submission process</A>,
6815 choose the filter through which the
6816 <A HREF="h_config_sending_filter">outgoing text should first pass</A>,
6817 or turn of flowed text generation.
6819 <P>
6820 <End of help on this topic>
6821 </BODY>
6822 </HTML>
6823 ======= h_compose_markcutpaste =======
6824 <HTML>
6825 <HEAD>
6826 <TITLE>Mark, Cut and Paste Commands</TITLE>
6827 </HEAD>
6828 <BODY>
6829 <H1>Mark, Cut and Paste Commands</H1>
6831 You can define a "block" of text, which can subsequently
6832 be deleted or
6833 copied as a unit, by setting a mark at the start of the block (Ctrl-^) and
6834 then moving the cursor to the end of the desired text block. You can then
6835 "cut" the block out
6836 <!--chtml if pinemode="function_key"-->
6837 "F9",
6838 <!--chtml else-->
6839 "Ctrl-K",
6840 <!--chtml endif-->
6841 move the cursor, and "paste" it
6842 <!--chtml if pinemode="function_key"-->
6843 "F10",
6844 <!--chtml else-->
6845 "Ctrl-U",
6846 <!--chtml endif-->
6847 in the new location. Also, you can paste more than once, allowing you
6848 to use this feature to copy a block of text.<P>
6850 If you press
6851 <!--chtml if pinemode="function_key"-->
6852 "F9"
6853 <!--chtml else-->
6854 "^K"
6855 <!--chtml endif-->
6856 without having marked anything, Alpine will delete
6857 a single line. If you delete a group of lines together, Alpine keeps them
6858 in the same buffer, so
6859 <!--chtml if pinemode="function_key"-->
6860 F10
6861 <!--chtml else-->
6862 ^U
6863 <!--chtml endif-->
6864 will restore them as a block. About
6865 terminology: Mark is shown as "^^". The first "^" means you should
6866 hold down the "Control" key on your keyboard. The second "^" means
6867 "type the character ^".
6869 <P>
6870 <End of help on this topic>
6871 </BODY>
6872 </HTML>
6873 ======= h_compose_justify =======
6874 <HTML>
6875 <HEAD>
6876 <TITLE>Justify Command</TITLE>
6877 </HEAD>
6878 <BODY>
6879 <H1>Justify Command</H1>
6881 The Justify
6882 <!--chtml if pinemode="function_key"-->
6883 (F4)
6884 <!--chtml else-->
6885 (^J)
6886 <!--chtml endif-->
6887 command reformats the text in the paragraph the cursor is in.
6888 Paragraphs are separated by one blank line or a line beginning with a space.
6889 This is useful when you have been editing a paragraph and the lines become
6890 uneven. The text is left aligned or justified and the right is ragged. If
6891 the text is already justified as typed with auto-wrap, no justification will
6892 be done.
6894 <P>
6895 If you have set a <A HREF="h_compose_markcutpaste">mark</A> to select a
6896 block of text, the Justify command is modified.
6897 Instead of automatically justifying the current paragraph you will be
6898 asked if you want to justify the paragraph, justify the selected region,
6899 or adjust the quote level of the selected region.
6900 Adjusting the quote level only works if you are using standard
6901 "> " or ">" quotes, which is the default if you haven't
6902 changed "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>".
6904 <P>
6905 When composing a reply containing included text, the justify command
6906 will reformat text to the right of the
6907 "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>",
6908 adding or removing indented lines as needed. Paragraphs are separated
6909 by a blank line, a line containing only the <!--#echo var="VAR_reply-indent-string"-->, or a
6910 line containing the indent string and one or more blank spaces.
6911 Included text that was previously indented (or "quoted") is
6912 not preserved.
6914 <P>
6915 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
6916 in 1999 and its wide-spread adoption since then, you will usually be better off if you
6917 use the standard
6918 "> " or ">" quotes.
6920 <P>
6921 <End of help on this topic>
6922 </BODY>
6923 </HTML>
6924 ======= h_compose_spell =======
6925 <HTML>
6926 <HEAD>
6927 <TITLE>Spell Check Command</TITLE>
6928 </HEAD>
6929 <BODY>
6930 <H1>Spell Check Command</H1>
6932 The "To Spell"
6933 <!--chtml if pinemode="function_key"-->
6934 (F12)
6935 <!--chtml else-->
6936 (^T)
6937 <!--chtml endif-->
6938 command calls an external spell checking program to look over the
6939 message you are composing. By default, Alpine uses
6940 <P>
6941 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
6942 <P>
6943 if it knows where to find "aspell".
6944 If there is no "aspell" command available but the command "ispell" is available
6945 then the command used is
6946 <P>
6947 <CENTER><SAMP>ispell -l</SAMP></CENTER>
6948 <P>
6949 Otherwise, the ancient "spell" command is used.
6950 <P>
6951 For PC-Alpine, you must install the aspell library code that you
6952 may get from
6953 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
6955 <P>
6956 <End of help on this topic>
6957 </BODY>
6958 </HTML>
6959 ======= h_compose_alted =======
6960 <HTML>
6961 <HEAD>
6962 <TITLE>Alt Editor Command</TITLE>
6963 </HEAD>
6964 <BODY>
6965 <H1>Alt Editor Command</H1>
6967 The "Alt Editor" command's availability depends on the
6968 Setup/Config variable "<A HREF="h_config_editor"><!--#echo var="VAR_editor"--></A>".
6970 <P>
6971 When the variable specifies a valid editor on your system, this
6972 command will launch it with the current text of your message
6973 already filled in.
6975 <P>
6976 <End of help on this topic>
6977 </BODY>
6978 </HTML>
6979 ======= h_compose_readfile =======
6980 <HTML>
6981 <HEAD>
6982 <TITLE>Read File Command</TITLE>
6983 </HEAD>
6984 <BODY>
6985 <H1>Read File Command</H1>
6987 The "Read File"
6988 <!--chtml if pinemode="function_key"-->
6989 (F5)
6990 <!--chtml else-->
6991 (^R)
6992 <!--chtml endif-->
6993 command allows you to copy in text from an existing file. You will be
6994 prompted for the name of a file to be inserted into the message. The file
6995 name is relative to your home directory
6996 <!--chtml if pinemode="running"-->
6997 (which, in the present configuration of your system, is
6998 "<!--#echo var="HOME_DIR"-->")
6999 <!--chtml endif-->
7000 or current working directory
7001 <!--chtml if pinemode="running"-->
7002 (which, at least for your current Alpine "session,"
7003 is "<!--#echo var="CURRENT_DIR"-->")
7004 <!--chtml endif-->, depending on the
7005 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
7006 configuration setting; or, the file name must be specified as a full path name
7007 <!--chtml if pinemode="os_windows"-->
7008 -- for example: "A:\PAPER.TXT"
7009 <!--chtml else-->
7010 -- for example: "/tmp/wisdom-of-the-day"
7011 <!--chtml endif-->
7012 (without the quotation marks).
7014 <P>
7015 The file will be inserted where the cursor is located. <B>The
7016 file to be read must be on the same system as Alpine.</B> If you use Alpine on a
7017 Unix machine but have files on a PC or Mac, the files must be transferred
7018 to the system Alpine is running on before they can be read. Please ask your
7019 local computer support people about the correct way to transfer a file to
7020 your Alpine system.
7022 <P>
7023 <End of help on this topic>
7024 </BODY>
7025 </HTML>
7026 ======= h_config_tray_icon =======
7027 <HTML>
7028 <HEAD>
7029 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></TITLE>
7030 </HEAD>
7031 <BODY>
7032 <H1>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></H1>
7034 PC-Alpine only.
7035 <P>
7036 This option restores a behavior of previous versions of PC-Alpine.
7037 These
7038 versions, when started, installed a PC-Alpine icon in the notification
7039 tray of Window's Taskbar. The primary use of this icon was to indicate
7040 new mail arrival by turning red (while the Taskbar icon remained green).
7041 Additionally, the icon now changes to yellow to signify that a mail folder
7042 has been closed unexpectedly.
7044 <P>
7045 Rather than add another icon to the Taskbar, this version of PC-Alpine will
7046 color its Taskbar entry's icon red (as well as the icon in the Window
7047 Title). This feature is only provided for backwards compatibility.
7049 <P>
7050 <End of help on this topic>
7051 </BODY>
7052 </HTML>
7053 ======= h_common_suspend =======
7054 <HTML>
7055 <HEAD>
7056 <TITLE>Suspend Command</TITLE>
7057 </HEAD>
7058 <BODY>
7059 <H1>Suspend Command</H1>
7061 With the <A HREF="h_config_can_suspend"><!--#echo var="FEAT_enable-suspend"--></A> feature
7062 enabled, you can, at almost any time, temporarily halt your Alpine session,
7063 <!--chtml if pinemode="os_windows"-->
7064 minimizing it into an icon.
7065 <!--chtml else-->
7066 and return to your system prompt.
7067 <!--chtml endif-->
7069 <P>
7070 <End of help on this topic>
7071 </BODY>
7072 </HTML>
7073 ======= h_pipe_command =======
7074 <HTML>
7075 <HEAD>
7076 <TITLE>Pipe Command SubOptions</TITLE>
7077 </HEAD>
7078 <BODY>
7079 <H1>Pipe Command SubOptions</H1>
7081 By default, when you use the Pipe command, the processed text of the
7082 message is sent to the Unix command
7083 you specify and the output is captured by Alpine and shown to you.
7084 (This command is available in PC-Alpine, as well, but there aren't many
7085 Windows commands that work well with piping.)
7086 There are some sub-commands that may be used to alter this behavior.
7087 These are toggles that switch the behavior between two possibilities.
7088 They can be combined in any way you wish.
7089 <P>
7090 By default, the prompt at the bottom of the screen looks like
7091 <P>
7092 <CENTER><SAMP>Pipe message 37 to :</SAMP></CENTER>
7093 <P>
7094 or
7095 <P>
7096 <CENTER><SAMP>Pipe messages to :</SAMP></CENTER>
7097 <P>
7098 if you are piping more than one message.
7099 <P>
7100 The sub-command options are:
7101 <DL>
7102 <DT>Shown Text or Raw Text</DT>
7103 <DD>This option toggles between sending the shown (processed) text
7104 of the message to the Unix command, and sending the
7105 raw (unprocessed) text of the message to the Unix command.
7106 The default is to send the shown text.
7107 The raw version of the message will contain all of the headers and any
7108 MIME encoding that the message contains.
7109 If you've selected the Raw Text then the prompt will have the additional word
7110 "RAW" in it, like
7111 <P>
7112 <CENTER><SAMP>Pipe RAW messages to :</SAMP></CENTER>
7113 <P>
7114 You can experiment with this option by piping to something simple like the
7115 Unix "cat" command.
7116 </DD>
7117 <DT>Captured Output or Free Output</DT>
7118 <DD>This option toggles between having Alpine capture the output of
7119 the Unix pipe command for display, and not capturing it.
7120 If the command you are piping to is a filter that will produce output
7121 you want to view, then you want to capture that output
7122 for display (the default).
7123 If the Unix command doesn't produce output or handles the display itself,
7124 then you want free output.
7125 When you've selected the Free Output option the prompt will change to
7126 <P>
7127 <CENTER><SAMP>Pipe messages to (uncaptured) :</SAMP></CENTER>
7128 <P>
7129 </DD>
7130 <DT>No Delimiter or With Delimiter</DT>
7131 <DD>This option controls whether or not a Unix mailbox style delimiter
7132 will come before the text of the message.
7133 This is the delimiter used in the common Unix mailbox format.
7134 It's the single line that begins with the five characters
7135 "From" followed by a <SPACE> character.
7136 You'll usually only want to include this if the Unix command requires
7137 input in the format of a traditional Unix mailbox file.
7138 When you've selected the With Delimiter option the prompt will change to
7139 <P>
7140 <CENTER><SAMP>Pipe messages to (delimited) :</SAMP></CENTER>
7141 <P>
7142 </DD>
7143 <DT>To Same Pipe or To Individual Pipes</DT>
7144 <DD>This option only shows up if you are running an aggregate
7145 pipe command.
7146 That is, the command was Apply Pipe, not just Pipe.
7147 You have the option of piping all of the selected messages through a
7148 single pipe to a single instance of the Unix command,
7149 or piping each individual message through a separate pipe to separate
7150 instances of the Unix command.
7151 The default is that all of the output will go through a single pipe
7152 to a single instance of the command.
7153 You can try this option with a command like "less", with Free
7154 Output enabled.
7155 When you've selected the Individual Pipes option the prompt will change to
7156 <P>
7157 <CENTER><SAMP>Pipe messages to (new pipe) :</SAMP></CENTER>
7158 <P>
7159 </DD>
7160 </DL>
7162 <P>
7163 As mentioned earlier, the options can be combined in any way you wish.
7164 You may leave them all off, turn them all on, or turn some of them on
7165 and some of them off.
7166 If you use the pipe command a second time in the same session the default
7167 options will be what you used the last time.
7169 <P>
7170 <End of help on this topic>
7171 </BODY>
7172 </HTML>
7173 ========== h_emptydir_subfolder_name =========
7174 <HTML>
7175 <HEAD>
7176 <TITLE>ENTER SUBFOLDER NAME</TITLE>
7177 </HEAD>
7178 <BODY>
7179 <H1>Enter Subfolder Name</H1>
7181 <P>
7182 This is the name of a new subfolder in the directory you are creating.
7183 Because empty directories are hidden and therefore not useful, you must also
7184 create a subfolder in the directory you are creating in order that the
7185 directory remains visible.
7186 <P>
7187 Alternatively, you may turn off the configuration feature
7188 <A HREF="h_config_quell_empty_dirs"><!--#echo var="FEAT_quell-empty-directories"--></A>
7189 so that empty directories remain visible.
7190 If you do that, you will not be required to create the subfolder when you
7191 create a directory.
7193 <P>
7194 <End of help on this topic>
7195 </BODY>
7196 </HTML>
7197 ========== h_incoming_add_folder_name =========
7198 <HTML>
7199 <HEAD>
7200 <TITLE>ENTER FOLDER NAME</TITLE>
7201 </HEAD>
7202 <BODY>
7203 <H1>Enter Folder Name</H1>
7205 <P>
7206 This is the name of the folder on the previously specified server.
7207 By default the folder name is interpreted as defining a section of your personal
7208 folder area. This area and how you specify it are defined by the
7209 server, if one is specified.
7211 <P>
7212 To define a folder outside the default area, prefix
7213 the path with the namespace to use when interpreting the
7214 given path. If a namespace is specified, the folder name begins with the
7215 sharp (#) character followed by the name of the namespace
7216 and then the namespace's path-element-delimiter. Aside from the
7217 name's format, namespaces can also imply access rights, content
7218 policy, audience, location, and, occasionally, access methods.
7220 <P>
7221 Each server exports its own set (possibly of size one) of
7222 namespaces.
7223 For a more detailed explanation read about
7224 <A HREF="h_folder_name_namespaces">Namespaces</A>.
7226 <P>
7227 To specify the default for INBOX on the server you can usually just enter
7228 "INBOX", and the server will understand the special meaning of
7229 that word.
7231 <P>
7232 <End of help on this topic>
7233 </BODY>
7234 </HTML>
7235 ========== h_incoming_add_folder_host =========
7236 <HTML>
7237 <HEAD>
7238 <TITLE>ENTER INCOMING FOLDER SERVER</TITLE>
7239 </HEAD>
7240 <BODY>
7241 <H1>Enter Incoming Folder Server</H1>
7243 You are being asked for the name of the server for use with this incoming
7244 folder.
7245 If the folder is on the machine where Alpine is running, then just enter
7246 RETURN without typing a server name.
7248 <P>
7249 If the folder is on an IMAP server then type the server's name followed
7250 by RETURN.
7251 You may use the ^X command if the server is the same as the server that
7252 the INBOX is on.
7254 <P>
7255 You may have to add optional extra information to the server name.
7256 For example, if the IMAP server is using a non-standard port number you
7257 would specify that by appending a colon (:) followed by the port number
7258 to the server name
7260 <P>
7261 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7262 <P>
7264 or you may need to specify a different protocol if the server is not an
7265 IMAP server. For example:
7267 <P>
7268 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7269 <P>
7271 for a POP server or
7273 <P>
7274 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7275 <P>
7277 for an NNTP news server.
7278 For an explanation of all of the possibilities, see
7279 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7280 for folders.
7282 <P>
7283 There is a special command (^W) if you want to set up a folder that gets its
7284 mail from a
7285 <A HREF="h_maildrop">Mail Drop</A>.
7286 If you type that command, you will be prompted for the information for
7287 both the Mail Drop folder and the destination folder.
7289 <P>
7290 <End of help on this topic>
7291 </BODY>
7292 </HTML>
7293 ========== h_incoming_add_inbox =========
7294 <HTML>
7295 <HEAD>
7296 <TITLE>ENTER INBOX SERVER</TITLE>
7297 </HEAD>
7298 <BODY>
7299 <H1>Enter INBOX Server</H1>
7301 You are being asked for the name of the server for use with
7302 the INBOX folder.
7303 Type the server's name followed by RETURN.
7305 <P>
7306 You may have to add optional extra information to the server name.
7307 For example, if the server is using a non-standard port number you
7308 would specify that by appending a colon (:) followed by the port number
7309 to the server name
7311 <P>
7312 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7313 <P>
7315 or you may need to specify a different protocol if the server is not an
7316 IMAP server. For example:
7318 <P>
7319 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7320 <P>
7322 for a POP server.
7323 <P>
7325 For an explanation of all of the possibilities, see
7326 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7327 for folders.
7329 <P>
7330 If the INBOX folder is on the machine where Alpine is running, then just enter
7331 RETURN without typing a server name.
7333 <P>
7334 There is a special command (^W) if you want to set up a folder that gets its
7335 mail from a
7336 <A HREF="h_maildrop">Mail Drop</A>.
7337 If you type that command, you will be prompted for the information for
7338 both the Mail Drop folder and the destination folder, which will be used
7339 as your INBOX folder.
7341 <P>
7342 <End of help on this topic>
7343 </BODY>
7344 </HTML>
7345 ========== h_incoming_add_maildrop_destn =========
7346 <HTML>
7347 <HEAD>
7348 <TITLE>ENTER DESTINATION SERVER</TITLE>
7349 </HEAD>
7350 <BODY>
7351 <H1>Enter Destination Server</H1>
7353 You are being asked for the name of the server where the destination
7354 folder is for use with this Mail Drop incoming folder.
7355 That is, you are using a Mail Drop for this incoming folder and
7356 you've already entered
7357 the server and folder name for the Mail Drop.
7358 Now you need to enter the server for the destination folder
7359 where the mail should be copied to.
7360 Mail will come from the Mail Drop and be copied to the destination folder.
7362 <P>
7363 Type the server's name followed by RETURN.
7364 If the folder is local to this computer, just type RETURN without entering
7365 a server name.
7367 <P>
7368 You may have to add optional extra information to the server name.
7369 For example, if the server is using a non-standard port number you
7370 would specify that by appending a colon (:) followed by the port number
7371 to the server name
7373 <P>
7374 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7375 <P>
7377 For an explanation of all of the possibilities, see
7378 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7379 for folders.
7381 <P>
7382 <End of help on this topic>
7383 </BODY>
7384 </HTML>
7385 ========== h_inbox_add_maildrop_destn =========
7386 <HTML>
7387 <HEAD>
7388 <TITLE>ENTER DESTINATION SERVER</TITLE>
7389 </HEAD>
7390 <BODY>
7391 <H1>Enter Destination Server</H1>
7393 You are being asked for the name of the server where the destination
7394 folder is for use with your Mail Drop INBOX.
7395 That is, you are using a Mail Drop for your INBOX and you've already entered
7396 the server and folder name for the Mail Drop.
7397 Now you need to enter the server for the destination folder
7398 where the mail should be copied to.
7399 Mail will come from the Mail Drop and be copied to the destination folder.
7401 <P>
7402 Type the server's name followed by RETURN.
7403 If the folder is local to this computer, just type RETURN without entering
7404 a server name.
7406 <P>
7407 You may have to add optional extra information to the server name.
7408 For example, if the server is using a non-standard port number you
7409 would specify that by appending a colon (:) followed by the port number
7410 to the server name
7412 <P>
7413 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7414 <P>
7416 For an explanation of all of the possibilities, see
7417 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7418 for folders.
7420 <P>
7421 <End of help on this topic>
7422 </BODY>
7423 </HTML>
7424 ========== h_inbox_add_maildrop =========
7425 <HTML>
7426 <HEAD>
7427 <TITLE>ENTER MAILDROP SERVER</TITLE>
7428 </HEAD>
7429 <BODY>
7430 <H1>Enter Mail Drop Server</H1>
7432 You are being asked for the name of the Mail Drop server for use with
7433 your INBOX.
7435 <P>
7436 Type the server's name followed by RETURN.
7438 <P>
7439 You may have to add optional extra information to the server name.
7440 For example, if the server is using a non-standard port number you
7441 would specify that by appending a colon (:) followed by the port number
7442 to the server name
7444 <P>
7445 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7446 <P>
7448 or you may need to specify a different protocol if the server is not an
7449 IMAP server. For example:
7451 <P>
7452 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7453 <P>
7455 for a POP server or
7457 <P>
7458 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7459 <P>
7461 for an NNTP news server.
7462 For an explanation of all of the possibilities, see
7463 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7464 for folders.
7466 <P>
7467 <End of help on this topic>
7468 </BODY>
7469 </HTML>
7470 ========== h_incoming_add_maildrop =========
7471 <HTML>
7472 <HEAD>
7473 <TITLE>ENTER MAILDROP SERVER</TITLE>
7474 </HEAD>
7475 <BODY>
7476 <H1>Enter Mail Drop Server</H1>
7478 You are being asked for the name of the Mail Drop server for use with
7479 this incoming folder.
7481 <P>
7482 Type the server's name followed by RETURN.
7483 You may use the ^X command if the server is the same as the server that
7484 the INBOX is on.
7486 <P>
7487 You may have to add optional extra information to the server name.
7488 For example, if the server is using a non-standard port number you
7489 would specify that by appending a colon (:) followed by the port number
7490 to the server name
7492 <P>
7493 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7494 <P>
7496 or you may need to specify a different protocol if the server is not an
7497 IMAP server. For example:
7499 <P>
7500 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7501 <P>
7503 for a POP server or
7505 <P>
7506 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7507 <P>
7509 for an NNTP news server.
7510 For an explanation of all of the possibilities, see
7511 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7512 for folders.
7514 <P>
7515 If the Mail Drop folder is on the machine where Alpine is running, then just enter
7516 RETURN without typing a server name.
7518 <P>
7519 <End of help on this topic>
7520 </BODY>
7521 </HTML>
7522 ========== h_maildrop =========
7523 <HTML>
7524 <HEAD>
7525 <TITLE>WHAT IS A MAIL DROP?</TITLE>
7526 </HEAD>
7527 <BODY>
7528 <H1>What is a Mail Drop?</H1>
7530 In some situaions it may make sense to have your mail delivered to one
7531 folder (the Mail Drop) and then when you want to read mail that has been
7532 delivered to the Mail Drop folder Alpine will move it to another
7533 destination folder.
7534 Often the Mail Drop will be a remote folder and messages will be moved from
7535 there to a local destination folder.
7537 <P>
7538 One example where this might make sense is if the Mail Drop folder is accessible
7539 only with the POP protocol.
7540 You could designate your POP inbox as the Mail Drop folder and have Alpine move
7541 mail from there to a local (on the same machine Alpine is running on)
7542 destination folder, where you'll read it.
7544 <P>
7545 A Mail Drop may only be used as your Inbox or as an
7546 <A HREF="h_config_enable_incoming">"Incoming folder"</A>.
7548 <P>
7549 There is no attempt to synchronize the contents of the destination folder
7550 with the contents of the Mail Drop folder.
7551 All that happens is that all of the messages in the Mail Drop folder are
7552 copied to the destination folder and then they are deleted and expunged (if possible)
7553 from the Mail Drop folder.
7554 The next time a check for new mail is made, any messages in the Mail
7555 Drop folder are once again copied to the destination folder and deleted
7556 and expunged from the Mail Drop folder.
7557 (If the Mail Drop folder is a news group, then the messages can't be
7558 expunged from the newsgroup. Instead, only Recent messages are copied from
7559 the newsgroup to the destination folder.)
7561 <P>
7562 Configuration of a Mail Drop is a little different from configuration of
7563 a folder that does not use a Mail Drop because you have to specify two
7564 folder names instead of one.
7565 The two folders may be any types of folders that Alpine can normally use.
7566 They don't have to be a remote folder and a local folder, that is
7567 simply the most common usage.
7568 When you use a Mail Drop folder Alpine will periodically re-open the Mail
7569 Drop to check for new mail.
7570 The new-mail checks will happen at the frequency set with the
7571 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option,
7572 but with a minimum time
7573 (<A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>)
7574 between checks.
7575 Because of this minimum you may notice that new mail does not
7576 appear promptly when you expect it.
7577 The reason for this is to protect the server from over-zealous opening and
7578 closing of the Mail Drop folder.
7579 If the user initiates the check by typing ^L (Ctrl-L) or the Next command when at
7580 the end of the folder index, then the check will happen, regardless of how
7581 long it has been since the previous check.
7582 <P>
7583 If there is new mail, that mail will be copied to the destination folder
7584 and then will be deleted from the Mail Drop.
7585 Note that using a Mail Drop with a local destination folder does not make
7586 sense if you read mail from more than one machine, because the mail is
7587 downloaded to the destination folder (which is accessible from only one
7588 machine) and deleted from the Mail Drop.
7589 <P>
7590 The feature <A HREF="h_config_maildrops_preserve_state"><!--#echo var="FEAT_maildrops-preserve-state"--></A> modifies the operation of Mail Drops.
7592 <P>
7593 The actual syntax used by Alpine for a folder that uses a Mail Drop is:
7595 <P>
7596 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
7597 <P>
7598 The brackets are not literal.
7599 <P>
7600 <CENTER><SAMP><DELIM></SAMP></CENTER>
7601 <P>
7602 is a single character that does not appear in the MailDropFolder name.
7603 If the name doesn't contain spaces then it can be a space character.
7604 The two folder names are full technical
7605 <A HREF="h_valid_folder_names">folder names</A>
7606 as used by Alpine.
7607 Here are a couple examples to give you an idea what is being talked about:
7609 <P>
7610 <CENTER><SAMP>#move {popserver.example.com/pop3}inbox localfolder</SAMP></CENTER>
7611 <P>
7612 <CENTER><SAMP>#move+{nntpserver.example.com/nntp}#news.comp.mail.pine+local folder</SAMP></CENTER>
7613 <P>
7615 A #move folder may only be used as an
7616 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
7617 an Inbox.
7618 When you are in the FOLDER LIST of Incoming Message Folders (after turning
7619 on the
7620 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
7621 option)
7622 the Add command has a subcommand "Use Mail Drop"
7623 which may be helpful for defining the folder in your Alpine configuration.
7624 The same is true when you edit the
7625 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
7626 option in Setup/Config.
7627 Each of these configuration methods will also create the DestinationFolder
7628 if it doesn't already exist.
7629 If you are having problems, make sure the DestinationFolder exists.
7631 <P>
7632 <End of help on this topic>
7633 </BODY>
7634 </HTML>
7635 ========== h_save =========
7636 <HTML>
7637 <HEAD>
7638 <TITLE>CHOOSE A FOLDER TO SAVE INTO</TITLE>
7639 </HEAD>
7640 <BODY>
7641 <H1>Choose a Folder to Save Into</H1>
7643 After Exiting from this help text,
7644 type the name of the folder you want to save into and press RETURN.
7645 <P>
7646 Press ^T to get a list of your folders to choose from.
7647 Press ^C to cancel the Save.
7648 <P>
7649 If you have Folder Collections defined you may use
7650 Ctrl-P (Previous collection) and Ctrl-N (Next collection) to switch
7651 the collection being saved to.
7652 <P>
7653 If Tab Completion is enabled (it is enabled by default)
7654 you may type a Tab character to have Alpine complete the folder name for you.
7655 <P>
7656 If Partial Match Lists is enabled (it is enabled by default) you may type
7657 Ctrl-X to get a list of matches to the prefix you've typed in so far.
7658 <P>
7659 If the Ctrl-R subcommand is present that means you can decide to Delete or
7660 not Delete the message you are saving after you save it.
7661 The label on that key gives the action to switch to.
7662 If it says Delete and you type Ctrl-R the label displayed will change to
7663 No Delete and the source message will be deleted after the save. If it
7664 says No Delete and you type Ctrl-R the label displayed will change to
7665 Delete and the message will not be deleted.
7666 You can control the default for the Delete parameter with the
7667 configuration feature <!--#echo var="FEAT_save-will-not-delete"-->.
7668 <P>
7669 Similarly, if the Ctrl-W subcommand is present that means you can decide
7670 to Preserve the order of the messages being saved or not.
7671 If it is labeled Preserve Order and you type Ctrl-W, the resulting Saved messages
7672 will be in the same order as you see them in the source folder now.
7673 The opposite action (which is usually the default) is that you don't care
7674 about the order.
7675 The Saved messages may or may not be in the same order in the destination folder.
7676 There may be a performance penalty for choosing to save the messages in order.
7677 You can control the default for the Preserve Order parameter with the
7678 configuration feature
7679 <!--#echo var="FEAT_save-aggregates-copy-sequence"-->.
7681 <P>
7682 If you haven't disabled the Save Input History and you've already done a
7683 Save earlier in this session then you may use the Up and Down arrows to retrieve
7684 a folder name used in a previous Save.
7686 <P>
7687 <End of help on this topic>
7688 </BODY>
7689 </HTML>
7690 ============= h_simple_index ========================
7691 <HTML>
7692 <HEAD>
7693 <TITLE>SELECT POSTPONED MESSAGE</TITLE>
7694 </HEAD>
7695 <BODY>
7696 <H1>POSTPONED MESSAGE SELECTION COMMANDS</H1>
7697 <!--chtml if pinemode="function_key"-->
7698 <PRE>
7699 Navigating the List of Messages General Alpine Commands
7700 ------------------------------- -----------------------
7701 F5 Move to previous message F1 Show this help text
7702 F6 Move to next message
7703 F7 Show previous screen of messages
7704 F8 Show next screen of messages
7706 Message Selection Commands
7707 --------------------------
7708 F3 Exit the Message Select menu (canceling Send command)
7709 F4 Select the currently highlighted message
7710 F9 Mark the currently highlighted message as deleted
7711 F10 Undelete (remove deletion mark from) the highlighted message
7712 </PRE>
7713 <!--chtml else-->
7714 <PRE>
7715 Navigating the List of Messages General Alpine Commands
7716 ------------------------------- -----------------------
7717 P Move to previous message ? Show this help text
7718 N Move to next message
7719 - Show previous screen of messages
7720 Spc (space bar) Show next screen of messages
7722 Message Selection Commands
7723 --------------------------
7724 E Exit the Message Select menu (canceling Send command)
7725 S Select the currently highlighted message
7726 D Mark the currently highlighted message as deleted
7727 U Undelete (remove deletion mark from) the highlighted message
7728 </PRE>
7729 <!--chtml endif-->
7730 <P>
7731 <H2>Description of the Select Postponed Message Screen</H2>
7733 This screen allows you to select one of several previously postponed
7734 messages in order to continue composition. Your options are very limited
7735 -- the screen is not meant to let you manipulate these messages. However,
7736 you may now delete messages from this list. Once you choose a message,
7737 Alpine reads it in and puts you into the regular message composer.
7738 <P>
7740 Messages do not stay in this postponed state automatically. If you select
7741 a message and then want to postpone it again, use the normal postpone
7742 (Ctrl-O) command in the composer.
7743 <P>
7745 If you exit this screen without selecting a message, the Compose command
7746 that got you here is canceled. Other than messages explicitly marked
7747 "Deleted", no messages will be removed.
7749 <P>
7750 <End of help on this topic>
7751 </BODY>
7752 </HTML>
7753 ============= h_collection_screen ========================
7754 <HTML>
7755 <HEAD>
7756 <TITLE>COLLECTION LIST screen</TITLE>
7757 </HEAD>
7758 <BODY>
7759 <H1>COLLECTION LIST screen</H1>
7761 The COLLECTION LIST screen is used to select one of your
7762 collection definitions to display the folders they contain. See
7763 <A HREF="h_what_are_collections">Folder Collections Explained</A> for
7764 detailed explanation of collections.<P>
7766 To manage your collection definitions (Add, Change, Delete, etc.), use
7767 the <A HREF="h_collection_maint">Setup/collectionList</A> command on Alpine's
7768 MAIN MENU.
7770 <P>
7771 <End of help on this topic>
7772 </BODY>
7773 </HTML>
7774 ============= h_collection_maint ========================
7775 <HTML>
7776 <HEAD>
7777 <TITLE>SETUP COLLECTION LIST screen</TITLE>
7778 </HEAD>
7779 <BODY>
7780 <H1>SETUP COLLECTION LIST screen</H1>
7782 The SETUP COLLECTION LIST screen lets you manage your collection
7783 definitions. See
7784 <A HREF="h_what_are_collections">Folder Collections Explained</A>
7785 for detailed explanation of collections.<P>
7787 Maintenance commands include:
7788 <DL>
7789 <DT>Change
7790 <!--chtml if pinemode="function_key"-->
7791 (F4)
7792 <!--chtml else-->
7793 (C)
7794 <!--chtml endif-->
7795 </DT>
7797 <DD>Modify attributes of the selected collection definition.
7799 <DT>Add Cltn
7800 <!--chtml if pinemode="function_key"-->
7801 (F9)
7802 <!--chtml else-->
7803 (A)
7804 <!--chtml endif-->
7805 </DT>
7807 <DD>Create a new collection definition.
7808 </DD>
7810 <DT>Del Cltn
7811 <!--chtml if pinemode="function_key"-->
7812 (F10)
7813 <!--chtml else-->
7814 (D)
7815 <!--chtml endif-->
7816 </DT>
7818 <DD>Delete the selected collection definition.<BR>
7819 NOTE: The folders and directories referred to by the
7820 collection definition are <EM>NOT</EM> deleted. Folders must
7821 be deleted, if that's what you wish to do, from the
7822 <A HREF="h_folder_maint">FOLDER LIST screen</A>, which shows the
7823 individual folders in a collection.
7824 </DD>
7826 <DT>Shuffle
7827 <!--chtml if pinemode="function_key"-->
7828 (F11)
7829 <!--chtml else-->
7830 ($)
7831 <!--chtml endif-->
7832 </DT>
7834 <DD>Change the order of the displayed collections. Alpine will offer
7835 to move the currently selected collection one position UP
7836 or DOWN.
7837 </DD>
7838 </DL>
7840 <P>
7841 <End of help on this topic>
7842 </BODY>
7843 </HTML>
7844 ============ h_what_are_collections ==========
7845 <HTML>
7846 <HEAD>
7847 <TITLE>Folder Collections Explained</TITLE>
7848 </HEAD>
7849 <BODY>
7850 <H1>Folder Collections Explained</H1>
7853 Those of you with simple mail configurations will just see a list of all the
7854 folders you have when choosing FOLDER LIST from Alpine's MAIN MENU.
7855 The special folders for INBOX, sent mail and saved messages
7856 will appear at the top of the list. All others are in alphabetical order.
7857 <P>
7858 If you
7859 or your system administrator have defined more than one collection or if
7860 you have a collection (for newsgroups or email folders) defined on your
7861 system, then you will see the COLLECTION LIST screen first when choosing
7862 FOLDER LIST from Alpine's MAIN MENU.
7863 <P>
7864 <H2>Why have multiple folder collections?</H2>
7865 <P>
7866 For Alpine users who only maintain email folders (and not too many) on one host,
7867 a single folder collection is probably sufficient.<P>
7869 However, people who have more than one email account - for example, one
7870 at their university, and one with their personal Internet Service Provider -
7871 will have different sets of folders on different hosts, and they may want to
7872 access them all from the same installation of Alpine, rather than use different
7873 software and/or log into other hosts to manipulate messages in different
7874 accounts. (If in doubt whether one of your email accounts can be accessed
7875 with Alpine, contact the technical support people for that account.) Even people
7876 who have only one email account on one host, but have dozens or
7877 hundreds of email folders, may want to arrange these folders together in a
7878 meaningful way.<BR>
7879 That is where multiple collections come in.
7881 <H2>Types of Collections</H2>
7882 <DL>
7883 <DT>INCOMING FOLDERS</DT>
7884 <DD>"Incoming Message Folders"
7885 is a special collection typically used to supplement your single INBOX.
7886 All the folders here are meant to be ones that receive incoming messages,
7887 which you intend to check more or less frequently.
7888 You may have multiple folders like this because you or your systems
7889 administrator have set up an external program or you may have set up
7890 Alpine to filter incoming
7891 messages into different folders, based on certain criteria such as
7892 sender, recipient, or subject; or because you have multiple accounts and
7893 wish to check their INBOXes easily. This collection is established by
7894 setting the
7895 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
7896 feature in the SETUP CONFIGURATION screen, which is accessed from the
7897 MAIN MENU.
7898 </DD>
7900 <DT>NEWS</DT>
7901 <DD>You can also define a collection specifically for
7902 newsgroups. Alpine does this for you implicitly when you
7903 <A HREF="h_config_nntp_server">define an NNTP Server</A>
7904 in your Alpine configuration. The news collection appears last in the
7905 COLLECTION LIST (though you can shuffle it up in the order of presentation),
7906 and Alpine knows not to save messages there.
7907 </DD>
7909 <DT>DEFAULT COLLECTION</DT>
7910 <DD>This is the default collection for your saved and sent messages folders.
7911 </DD>
7912 </DL>
7914 <P>
7916 <H2>Defining Collections</H2>
7917 <P>
7918 In the absence of any folder-collection definitions, Alpine will assume a
7919 single default folder collection.
7920 <!--chtml if pinemode="os_windows"-->
7921 <!--chtml else-->
7922 If necessary, Alpine will create the directory
7923 "mail" in your Unix home directory
7924 to hold your folders.
7925 <!--chtml endif-->
7926 <P>
7927 You can use the
7928 <A HREF="h_collection_maint">Setup/collectionList screen</A>, called up from
7929 the MAIN MENU, to manage your collection list.
7930 <P>
7931 <End of help on this topic>
7932 </BODY>
7933 </HTML>
7934 ===== h_select_address_screen =====
7935 <HTML>
7936 <HEAD>
7937 <TITLE>SELECT AN ADDRESS SCREEN</TITLE>
7938 </HEAD>
7939 <BODY>
7940 <H1>SELECT AN ADDRESS SCREEN</H1>
7941 <H2>COMMANDS</H2>
7942 <!--chtml if pinemode="function_key"-->
7943 <PRE>
7944 Available Commands
7945 -------------------------------
7946 F1 Show Help Text
7947 F3 Exit without selecting anything
7948 F4 Select the highlighted address
7949 F5 Move highlight to previous address
7950 F6 Move highlight to next address
7951 F7 Previous page of addresses
7952 F8 Next page of addresses
7953 F11 Print
7954 F12 WhereIs
7955 </PRE>
7956 <!--chtml else-->
7957 <PRE>
7958 Navigation General Alpine Commands
7959 ------------------------- -----------------------
7960 P Prev Address ? Display this help text
7961 N Next Address E Exit without selecting anything
7962 - Previous page % Print
7963 Spc (space bar) Next page
7964 W WhereIs
7966 Select Command
7967 ------------------------------------------------
7968 S Select the highlighted address
7969 </PRE>
7970 <!--chtml endif-->
7972 <H2>Description of the Select Address Screen</H2>
7974 This screen gives you an easy way to select an address from all of
7975 the address book entries that match the prefix typed so far.
7977 <P><UL>
7978 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
7979 </UL>
7980 <P>
7981 <End of help on this topic>
7982 </BODY>
7983 </HTML>
7984 ===== h_select_rule_screen =====
7985 <HTML>
7986 <HEAD>
7987 <TITLE>SELECT A RULE SCREEN</TITLE>
7988 </HEAD>
7989 <BODY>
7990 <H1>SELECT A RULE SCREEN</H1>
7991 <H2>COMMANDS</H2>
7992 <!--chtml if pinemode="function_key"-->
7993 <PRE>
7994 Available Commands
7995 -------------------------------
7996 F1 Show Help Text
7997 F3 Exit without selecting anything
7998 F4 Select the highlighted rule
7999 F5 Move highlight to previous rule
8000 F6 Move highlight to next rule
8001 F7 Previous page of rules
8002 F8 Next page of rules
8003 F11 Print
8004 F12 WhereIs
8005 </PRE>
8006 <!--chtml else-->
8007 <PRE>
8008 Navigation General Alpine Commands
8009 ------------------------- -----------------------
8010 P Prev Rule ? Display this help text
8011 N Next Rule E Exit without selecting anything
8012 - Previous page % Print
8013 Spc (space bar) Next page
8014 W WhereIs
8016 Select Command
8017 ------------------------------------------------
8018 S Select the highlighted rule
8019 </PRE>
8020 <!--chtml endif-->
8022 <H2>Description of the Select Rule Screen</H2>
8024 This screen just gives you an easy way to select a rule from all of your
8025 defined rules.
8026 The list of rules presented is the list of nicknames of all of the rules
8027 defined using Setup/Rules.
8028 For selecting messages, it is likely that the Indexcolor rules and possibly
8029 the Roles rules will be most useful.
8030 The others are there also, in case you find a use for them.
8031 <P>
8032 In order for this to be useful for selecting messages, the nicknames of
8033 the rules have to be different.
8034 Alpine actually just gets the nickname of the rule that you select and then
8035 looks up that rule using the nickname.
8036 So if there are duplicate nicknames, the first rule that has that
8037 nickname will be used.
8039 <P><UL>
8040 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8041 </UL>
8042 <P>
8043 <End of help on this topic>
8044 </BODY>
8045 </HTML>
8046 ===== h_select_priority_screen =====
8047 <HTML>
8048 <HEAD>
8049 <TITLE>SELECT A PRIORITY SCREEN</TITLE>
8050 </HEAD>
8051 <BODY>
8052 <H1>SELECT A PRIORITY SCREEN</H1>
8053 <H2>COMMANDS</H2>
8054 <!--chtml if pinemode="function_key"-->
8055 <PRE>
8056 Available Commands
8057 -------------------------------
8058 F1 Show Help Text
8059 F3 Exit without selecting anything
8060 F4 Select the highlighted priority
8061 F5 Move highlight to previous priority
8062 F6 Move highlight to next priority
8063 F7 Previous page of priorities
8064 F8 Next page of priorities
8065 F11 Print
8066 F12 WhereIs
8067 </PRE>
8068 <!--chtml else-->
8069 <PRE>
8070 Navigation General Alpine Commands
8071 ------------------------- -----------------------
8072 P Prev Priority ? Display this help text
8073 N Next Priority E Exit without selecting anything
8074 - Previous page % Print
8075 Spc (space bar) Next page
8076 W WhereIs
8078 Select Command
8079 ------------------------------------------------
8080 S Select the highlighted priority
8081 </PRE>
8082 <!--chtml endif-->
8084 <H2>Description of the Select Priority Screen</H2>
8086 This screen gives you a way to select a priority for the message you are sending.
8087 This priority will be placed in the non-standard X-Priority header of your outgoing mail.
8088 Some mail programs will display an indication of the priority level to
8089 the recipient of the message, some will ignore it.
8090 Even in cases where the mail programs of both the sender and the recipient
8091 agree on the meaning of this header, keep in mind that it is
8092 something that the sender sets so it is only an indication
8093 of the priority that the sender attaches to the mail.
8094 Alpine can be made to display an indication of this priority in incoming
8095 messages by use of one of the tokens
8096 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
8097 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
8098 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
8100 <P><UL>
8101 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8102 </UL>
8103 <P>
8104 <End of help on this topic>
8105 </BODY>
8106 </HTML>
8107 ===== h_select_keyword_screen =====
8108 <HTML>
8109 <HEAD>
8110 <TITLE>SELECT A KEYWORD SCREEN</TITLE>
8111 </HEAD>
8112 <BODY>
8113 <H1>SELECT A KEYWORD SCREEN</H1>
8114 <H2>COMMANDS</H2>
8115 <!--chtml if pinemode="function_key"-->
8116 <PRE>
8117 Available Commands
8118 -------------------------------
8119 F1 Show Help Text
8120 F3 Exit without selecting anything
8121 F4 Select the highlighted keyword
8122 F5 Move highlight to previous keyword
8123 F6 Move highlight to next keyword
8124 F7 Previous page of keywords
8125 F8 Next page of keywords
8126 F11 Print
8127 F12 WhereIs
8128 </PRE>
8129 <!--chtml else-->
8130 <PRE>
8131 Navigation General Alpine Commands
8132 ------------------------- -----------------------
8133 P Prev Keyword ? Display this help text
8134 N Next Keyword E Exit without selecting anything
8135 - Previous page % Print
8136 Spc (space bar) Next page
8137 W WhereIs
8139 Select Command
8140 ------------------------------------------------
8141 S Select the highlighted keyword
8142 </PRE>
8143 <!--chtml endif-->
8145 <H2>Description of the Select Keyword Screen</H2>
8147 This screen just gives you an easy way to select a keyword.
8148 The list of keywords presented is the list of all keywords defined in your
8149 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8150 If you have given a keyword a nickname, that nickname is displayed
8151 instead of the actual keyword.
8153 <P><UL>
8154 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8155 </UL>
8156 <P>
8157 <End of help on this topic>
8158 </BODY>
8159 </HTML>
8160 ===== h_select_charset_screen =====
8161 <HTML>
8162 <HEAD>
8163 <TITLE>SELECT A CHARACTER SET SCREEN</TITLE>
8164 </HEAD>
8165 <BODY>
8166 <H1>SELECT A CHARACTER SET SCREEN</H1>
8167 <H2>COMMANDS</H2>
8168 <!--chtml if pinemode="function_key"-->
8169 <PRE>
8170 Available Commands
8171 -------------------------------
8172 F1 Show Help Text
8173 F3 Exit without selecting anything
8174 F4 Select the highlighted character set
8175 F5 Move highlight to previous character set
8176 F6 Move highlight to next character set
8177 F7 Previous page of character sets
8178 F8 Next page of character sets
8179 F11 Print
8180 F12 WhereIs
8181 </PRE>
8182 <!--chtml else-->
8183 <PRE>
8184 Navigation General Alpine Commands
8185 ------------------------- -----------------------
8186 P Prev Character Set ? Display this help text
8187 N Next Character Set E Exit without selecting anything
8188 - Previous page % Print
8189 Spc (space bar) Next page
8190 W WhereIs
8192 Select Command
8193 ------------------------------------------------
8194 S Select the highlighted character set
8195 </PRE>
8196 <!--chtml endif-->
8198 <H2>Description of the Select A Character Set Screen</H2>
8200 This screen just gives you an easy way to select a character set from the
8201 set of character sets Alpine knows about.
8202 The list presented will vary slightly depending on what option you are
8203 selecting the character set for.
8205 <P><UL>
8206 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8207 </UL>
8208 <P>
8209 <End of help on this topic>
8210 </BODY>
8211 </HTML>
8212 ===== h_select_multcharsets_screen =====
8213 <HTML>
8214 <HEAD>
8215 <TITLE>SELECT CHARACTER SETS SCREEN</TITLE>
8216 </HEAD>
8217 <BODY>
8218 <H1>SELECT CHARACTER SETS SCREEN</H1>
8219 <H2>COMMANDS</H2>
8220 <!--chtml if pinemode="function_key"-->
8221 <PRE>
8222 Available Commands
8223 -------------------------------
8224 F1 Show Help Text
8225 F3 Exit without selecting anything
8226 F4 Select the highlighted charset (or chosen charsets in ListMode)
8227 F5 Move highlight to previous charset
8228 F6 Move highlight to next charset
8229 F7 Previous page of charsets
8230 F8 Next page of charsets
8231 F9 Toggle choices when using ListMode
8232 F10 Turn on/off ListMode (makes it easy to choose multiple charsets)
8233 F11 Print
8234 F12 WhereIs
8235 </PRE>
8236 <!--chtml else-->
8237 <PRE>
8238 Navigation General Alpine Commands
8239 ------------------------- -----------------------
8240 P Prev Charset ? Display this help text
8241 N Next Charset E Exit without selecting anything
8242 - Previous page % Print
8243 Spc (space bar) Next page
8244 W WhereIs
8246 Select Command
8247 ------------------------------------------------
8248 S Select the highlighted charset (or chosen charsets in ListMode)
8249 L Turn on ListMode (makes it easy to choose multiple charsets)
8250 1 Turn off ListMode
8251 X Toggle choices when using ListMode
8252 </PRE>
8253 <!--chtml endif-->
8255 <H2>Description of the Select Character Set Screen</H2>
8257 This screen just gives you an easy way to select a character set or a list of
8258 character sets.
8259 The list of character sets presented is the list of all character sets known to
8260 Alpine.
8261 You may select other character sets by typing them in directly.
8263 <P><UL>
8264 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8265 </UL>
8266 <P>
8267 <End of help on this topic>
8268 </BODY>
8269 </HTML>
8270 ===== h_select_multkeyword_screen =====
8271 <HTML>
8272 <HEAD>
8273 <TITLE>SELECT KEYWORDS SCREEN</TITLE>
8274 </HEAD>
8275 <BODY>
8276 <H1>SELECT KEYWORDS SCREEN</H1>
8277 <H2>COMMANDS</H2>
8278 <!--chtml if pinemode="function_key"-->
8279 <PRE>
8280 Available Commands
8281 -------------------------------
8282 F1 Show Help Text
8283 F3 Exit without selecting anything
8284 F4 Select the highlighted keyword (or chosen keywords in ListMode)
8285 F5 Move highlight to previous keyword
8286 F6 Move highlight to next keyword
8287 F7 Previous page of keywords
8288 F8 Next page of keywords
8289 F9 Toggle choices when using ListMode
8290 F10 Turn on/off ListMode (makes it easy to choose multiple keywords)
8291 F11 Print
8292 F12 WhereIs
8293 </PRE>
8294 <!--chtml else-->
8295 <PRE>
8296 Navigation General Alpine Commands
8297 ------------------------- -----------------------
8298 P Prev Keyword ? Display this help text
8299 N Next Keyword E Exit without selecting anything
8300 - Previous page % Print
8301 Spc (space bar) Next page
8302 W WhereIs
8304 Select Command
8305 ------------------------------------------------
8306 S Select the highlighted keyword (or chosen keywords in ListMode)
8307 L Turn on ListMode (makes it easy to choose multiple keywords)
8308 1 Turn off ListMode
8309 X Toggle choices when using ListMode
8310 </PRE>
8311 <!--chtml endif-->
8313 <H2>Description of the Select Keyword Screen</H2>
8315 This screen just gives you an easy way to select a keyword or a list of
8316 keywords.
8317 The list of keywords presented is the list of all keywords defined in your
8318 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8319 If you have given a keyword a nickname, that nickname is displayed
8320 instead of the actual keyword.
8322 <P><UL>
8323 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8324 </UL>
8325 <P>
8326 <End of help on this topic>
8327 </BODY>
8328 </HTML>
8329 ===== h_select_incoming_to_monitor =====
8330 <HTML>
8331 <HEAD>
8332 <TITLE>SELECT FOLDERS TO CHECK SCREEN</TITLE>
8333 </HEAD>
8334 <BODY>
8335 <H1>SELECT FOLDERS TO CHECK SCREEN</H1>
8336 <H2>COMMANDS</H2>
8337 <!--chtml if pinemode="function_key"-->
8338 <PRE>
8339 Available Commands
8340 -------------------------------
8341 F1 Show Help Text
8342 F3 Exit without selecting anything
8343 F4 Select the marked folders
8344 F5 Move highlight to previous folder
8345 F6 Move highlight to next folder
8346 F7 Previous page of folders
8347 F8 Next page of folders
8348 F9 Toggle choices on or off
8349 F11 Print
8350 F12 WhereIs
8351 </PRE>
8352 <!--chtml else-->
8353 <PRE>
8354 Navigation General Alpine Commands
8355 ------------------------- -----------------------
8356 P Prev Folder ? Display this help text
8357 N Next Folder ^C exit without changing anything
8358 - Previous page % Print
8359 Spc (space bar) Next page
8360 W WhereIs
8362 Select Command
8363 ------------------------------------------------
8364 S Select the marked folders
8365 X Toggle choices on or off
8366 </PRE>
8367 <!--chtml endif-->
8369 <H2>Description of the Select Folders to Check Screen</H2>
8371 This screen is only useful if the feature
8372 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
8373 is set.
8374 By default, when you set that feature all of your incoming folders
8375 will be checked periodically for Unseen messages.
8376 By using this screen, you may restrict the set of monitored folders to
8377 a subset of all of the incoming folders.
8378 <P>
8379 Mark the folders you want to monitor for Unseen messages with
8380 an "X".
8381 When you've finished marking all your selections use the Select
8382 command to register your choices.
8383 To return to the default of checking all incoming folders
8384 delete all folders or unmark all folders.
8386 <P><UL>
8387 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8388 </UL>
8389 <P>
8390 <End of help on this topic>
8391 </BODY>
8392 </HTML>
8393 ===== h_role_select =====
8394 <HTML>
8395 <HEAD>
8396 <TITLE>ROLES SCREEN</TITLE>
8397 </HEAD>
8398 <BODY>
8399 <H1>ROLES SCREEN</H1>
8400 <H2>ROLES COMMANDS</H2>
8401 <!--chtml if pinemode="function_key"-->
8402 <PRE>
8403 Available Commands
8404 -------------------------------
8405 F1 Show Help Text
8406 F3 Exit without a selection
8407 F4 Select a role to use in composition
8408 F5 Move to previous role
8409 F6 Move to next role
8410 F7 Previous page of roles
8411 F8 Next page of roles
8412 F11 Change Default Role
8413 F12 Whereis (search role nicknames)
8414 </PRE>
8415 <!--chtml else-->
8416 <PRE>
8417 Navigation General Alpine Commands
8418 ------------------------- -----------------------
8419 P Prev Role ? Display this help text
8420 N Next Role E Exit without a selection
8421 - Previous page
8422 Spc (space bar) Next page
8423 W WhereIs (search for word in role nicknames)
8425 Select Role Commands
8426 ------------------------------------------------
8427 [Return] Select highlighted role
8428 D Change Default Role
8429 </PRE>
8430 <!--chtml endif-->
8432 <H2>Description of the Roles Screen</H2>
8434 With this screen you select a role to be used in the composition of a
8435 message.
8436 Use the Previous and Next commands to highlight the role you wish to
8437 use.
8438 When you type carriage return you will be placed in the composer using the highlighted role.
8439 <P>
8440 You don't have any non-default <A HREF="h_rules_roles">roles</A>
8441 available unless you set them up.
8442 You may do so by using the Setup/Rules command on the MAIN MENU.
8443 <P>
8444 By using the D command, you may set a default role that will persist until
8445 you change it or until you exit Alpine.
8446 The D command toggles through three states: set the default role, unset the
8447 default role, and leave the default role as it is.
8448 <P><UL>
8449 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8450 </UL>
8451 <P>
8452 <End of help on this topic>
8453 </BODY>
8454 </HTML>
8455 ===== h_role_abook_select =====
8456 <HTML>
8457 <HEAD>
8458 <TITLE>SELECT ADDRESS BOOK SCREEN</TITLE>
8459 </HEAD>
8460 <BODY>
8461 <H1>SELECT ADDRESS BOOK SCREEN</H1>
8462 <H2>COMMANDS</H2>
8463 <!--chtml if pinemode="function_key"-->
8464 <PRE>
8465 Available Commands
8466 -------------------------------
8467 F1 Show Help Text
8468 F3 Exit screen without selecting anything
8469 F4 Select highlighted address book
8470 F5 Move to previous address book
8471 F6 Move to next address book
8472 F7 Previous page of address books
8473 F8 Next page of address books
8474 F12 Whereis
8475 </PRE>
8476 <!--chtml else-->
8477 <PRE>
8478 Navigation General Alpine Commands
8479 ------------------------- -----------------------
8480 P Previous addrbook ? Display this help text
8481 N Next addrbook
8482 - Previous page
8483 Spc (space bar) Next page
8484 W WhereIs
8486 Select Role Commands
8487 ------------------------------------------------
8488 S Select highlighted address book
8489 E Exit screen without selecting anything
8490 </PRE>
8491 <!--chtml endif-->
8493 <H2>Description of the Select Address Book Screen</H2>
8495 This screen helps you select one of your address books.
8496 Use the Previous and Next commands to highlight the address book you wish to
8497 select.
8498 <P><UL>
8499 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8500 </UL>
8501 <P>
8502 <End of help on this topic>
8503 </BODY>
8504 </HTML>
8505 ======== h_rule_patterns =============
8506 <HTML>
8507 <HEAD>
8508 <TITLE>PATTERNS</TITLE>
8509 </HEAD>
8510 <BODY>
8511 <H1>PATTERNS</H1>
8512 Patterns are used with Roles, Filtering, Index Coloring,
8513 Scoring, Other Rules, and Search Rules.
8514 Patterns are compared with a message to see if there is a match.
8515 For Filtering, the messages being checked are all the messages in the
8516 folder, one at a time.
8517 For Index Line Coloring, each message that is visible on the screen is
8518 checked for matches with the Index Coloring Patterns.
8519 Roles are used with the Reply, Forward, and Compose commands.
8520 For Reply, the message used to compare the Pattern with is the message
8521 being replied to;
8522 for Forward, the message used to compare the Pattern with is the message
8523 being forwarded;
8524 and for Compose, there is no message, so the parts of the Pattern that depend
8525 on a message (everything other than Current Folder Type and the
8526 Beginning of Month and Year)
8527 are not used.
8528 Only the Current Folder Type matters for Compose (plus the Beginning of
8529 Month or Year, which you wouldn't usually use for a Role).
8530 For Scoring, the message being scored is compared with all of the Score
8531 Patterns, and the Score Values from the ones that match are added together to
8532 get the message's score.
8533 For Other Rules, there is no message. Only the Current Folder Type is checked
8534 for Other Rules.
8535 <P>
8536 Each Pattern has several possible parts, all of which are optional.
8537 In order for there to be a match, <EM>ALL</EM> of the
8538 <EM>defined</EM> parts of the Pattern must match the message.
8539 If a part is not defined it is considered a match, but note that a filtering
8540 Pattern must have at least one defined part or it will be ignored.
8541 For example, if the To pattern is not defined it will be
8542 displayed as
8543 <P>
8544 <CENTER>To pattern = <No Value Set></CENTER>
8545 <P>
8546 That is considered a match because it is not defined.
8547 This means that the Pattern with nothing defined is a match if the
8548 Current Folder Type matches, but there is an exception that was mentioned
8549 in the previous paragraph.
8550 Because filtering is a potentially destructive action, filtering Patterns
8551 with nothing other than Current Folder Type defined are ignored.
8552 If you really want a filtering Pattern to match all messages (subject to
8553 Current Folder Type) the best way to do it is to define a Score interval
8554 that includes all possible scores.
8555 This would be the score interval <SAMP>(-INF,INF)</SAMP>.
8556 This can be used even if you haven't defined any rules to Set Scores.
8557 <P>
8558 There are six predefined header patterns called the To, From, Sender, Cc, News,
8559 and Subject patterns.
8560 Besides those six predefined header patterns, you may add
8561 additional header patterns with header fieldnames of your choosing.
8562 You add an extra header pattern by placing the cursor on one of the
8563 patterns while in the role editor and using the "eXtraHdr" command.
8564 The Recip pattern is a header pattern that stands for Recipient (To OR Cc)
8565 and the Partic pattern is a header pattern that stands for
8566 Participant (From OR To OR Cc).
8567 (Defining the Recip pattern does not have the same effect as defining both
8568 the To and Cc patterns. Recip is To <EM>OR</EM> Cc, not To <EM>AND</EM> Cc.)
8569 Similar to the header patterns are the AllText pattern and the BodyText pattern.
8570 Instead of comparing this pattern's text against only the contents of
8571 a particular header field, the text for the AllText pattern is compared
8572 with text anywhere in the message's header or body, and the text for the
8573 BodyText pattern is compared with text anywhere in the message's body.
8574 <P>
8575 Any of the header patterns, the AllText pattern, or the BodyText pattern may be negated with the
8576 "!" "toggle NOT" command.
8577 You can tell that <EM>NOT</EM> has been turned on by looking for the character
8578 "!" at the beginning of the pattern line.
8579 When the "!" is present, it reverses the meaning of the match.
8580 That is, if the pattern matches then it is considered to NOT be a match, and
8581 if it does not match it is considered to be a match.
8582 <P>
8583 Don't make the mistake of putting the "!" in the data field for
8584 a pattern.
8585 For example, if you type the characters "!urgent" into the Subject
8586 pattern, the pattern will look like:
8587 <P>
8588 <PRE>
8589 Subject pattern = !urgent
8590 </PRE>
8591 <P>
8592 This means you want to match the 7 character sequence "!urgent".
8593 In order to match messages that do not have "urgent" in
8594 their Subject field, first type the characters "urgent" followed
8595 by carriage return for the value of the Subject pattern, then negate it
8596 by typing the "!" command.
8597 It should look like
8598 <P>
8599 <PRE>
8600 ! Subject pattern = urgent
8601 </PRE>
8602 <P>
8603 The contents of each of these header patterns (or the AllText or BodyText patterns) may
8604 be a complete email address, part of an address, or a random set of
8605 characters to match against.
8606 It may also be a list of such patterns, which means you
8607 are looking for a match against the first pattern in the list <EM>OR</EM>
8608 the second pattern <EM>OR</EM> the third and so on.
8609 For example, a Subject pattern equal to
8610 <P>
8611 <PRE>
8612 Subject pattern = urgent
8613 emergency
8614 alert
8615 </PRE>
8616 <P>
8617 would match all messages with a subject that contained at least one
8618 of those words.
8619 It would also match subjects containing the words "alerts" or
8620 "Urgently".
8621 <P>
8622 The same example with "NOT" turned on would be
8623 <P>
8624 <PRE>
8625 ! Subject pattern = urgent
8626 emergency
8627 alert
8628 </PRE>
8629 <P>
8630 which would match all messages with a subject that did <EM>NOT</EM> contain any of
8631 those words.
8632 You can use the "Add Value" command to add new words to the list,
8633 or you can enter them as a comma-separated list.
8634 <P>
8635 (It is not possible to specify two patterns that must <EM>BOTH</EM> be
8636 present for a match.
8637 It is only possible to specify that <EM>EITHER</EM> pattern1 <EM>OR</EM>
8638 pattern2 must be present,
8639 and that is exactly what using a list does.)
8640 <P>
8641 The "Current Folder Type" and the "Score Interval" are
8642 also part of the Pattern, although the "Score Interval" is not used
8643 when checking for matches for Scoring.
8644 There are five similar settings that relate to the status of the message.
8645 These settings rely on the message being New or not, Deleted or not,
8646 Answered or not, Important or not, and Recent or not.
8647 There are also some other miscellaneous settings.
8648 The first is the Age of the message in days.
8649 Another is the Size of the message, in bytes.
8650 The third is a setting that detects whether or not the Subject of a
8651 message contains raw 8-bit characters (unencoded characters with the most
8652 significant bit set).
8653 There is a setting that detects whether or not this is the first time
8654 Alpine has been run this month (doesn't depend on individual messages),
8655 and another that detects whether or not this is the first time Alpine has
8656 been run this year.
8657 Other parts of the Pattern detect whether or not the From address of a
8658 message appears in your address book, whether or not certain keywords
8659 are set for a message, and whether or not certain character sets are
8660 used in a message.
8662 <H2>Parts of a Pattern</H2>
8664 <H3>Header patterns</H3>
8666 A header pattern is simply text that is searched for in the corresponding
8667 header field.
8668 For example, if a Pattern has a From header pattern with the value
8669 "@company.com", then only messages that have a From header
8670 that contains the text "@company.com" will be possible
8671 matches.
8672 Matches don't have to be exact.
8673 For example, if the relevant field of a message contains the text
8674 "mailbox@domain" somewhere
8675 in it, then header patterns of "box", or "x@d", or
8676 "mailbox@domain" are all matches.
8677 <P>
8678 All parts of the Pattern must match so, for example,
8679 if a message matches a defined
8680 From pattern, it still must be checked against the other parts of the
8681 Pattern that have been defined.
8682 The To header pattern is a slightly special case.
8683 If the message being checked has a Resent-To header
8684 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, the addresses
8685 there are used in place of the addresses in the To header.
8686 This is only true for the To header.
8687 Resent-cc and Resent-From headers are never used unless you add them
8688 with the eXtraHdrs command.
8689 <P>
8690 The meaning of a header pattern may be negated with the
8691 "!" "toggle NOT" command.
8692 You can tell that <EM>NOT</EM> has been turned on by looking for the character
8693 "!" at the beginning of the pattern line.
8694 It would look something like
8695 <P>
8696 <PRE>
8697 ! From pattern = susan@example.com
8698 </PRE>
8699 <P>
8700 When the "!" is present, it reverses the meaning of the match.
8701 <P>
8702 If you want to check for the presence of a header field but don't care
8703 about its value, then
8704 the empty pattern that you get by entering a pair of
8705 double quotes ("") should match any message that
8706 has the corresponding header field.
8708 <H3><A NAME="pattern_alltext">AllText patterns</A></H3>
8710 AllText patterns are just like header patterns except that the text is
8711 searched for anywhere in the message's headers or body, not just in the
8712 contents of a particular header field.
8713 <P>
8715 <H3><A NAME="pattern_bodytext">BodyText patterns</A></H3>
8717 BodyText patterns are just like header patterns except that the text is
8718 searched for anywhere in the message's body, not just in the
8719 contents of a particular header field.
8720 <P>
8722 If there is more than one header pattern or AllText pattern or BodyText pattern
8723 for which you want to take the
8724 same action there is a shorthand notation that may be used.
8725 Any of these patterns may be a list of patterns instead of
8726 just a single pattern.
8727 If any one of the patterns in the list matches the message
8728 then it is considered a match.
8729 For example, if "company1" and "company2" both required
8730 you to use the same role when replying to messages, you might have
8731 a To pattern that looks like
8732 <P>
8733 <PRE>
8734 To pattern = company1.com
8735 company2.com
8736 </PRE>
8737 <P>
8738 This means that if the mail you are replying to was addressed to
8739 either "anything@company1.com" or "anything@company2.com",
8740 then this Pattern is a match and the same actions will be taken.
8741 <P>
8742 The meaning of an AllText or BodyText pattern may be negated with the
8743 "!" "toggle NOT" command.
8744 You can tell that <EM>NOT</EM> has been turned on by looking for the character
8745 "!" at the beginning of the pattern line.
8746 When the "!" is present, it reverses the meaning of the match.
8747 <P>
8748 A technicality: Since comma is the character used to separate multiple values
8749 in any of the fields that may have multiple values (such as header patterns,
8750 AllText patterns, BodyText patterns, keywords, folder lists, and so on),
8751 you must escape comma with a
8752 backslash (\) if you want to include a literal comma in one of those fields.
8753 In other words, if you type a backslash followed by a comma it will
8754 be interpreted as a comma by Alpine, instead of as a separator between
8755 pattern values.
8756 All other backslashes (those not followed by a comma) are literal
8757 backslashes and should not be escaped.
8758 It's unlikely you'll ever need to enter a literal comma or backslash in
8759 any of the patterns.
8761 <H3><A NAME="pattern_current_folder">Current Folder Type</A></H3>
8763 The "Current Folder Type" may be set to one of four different
8764 values: "Any", "News", "Email", or
8765 "Specific".
8766 If the value is set to "News", then the
8767 Pattern will only match if the currently open folder is a newsgroup.
8768 The value "Email" only matches if the current folder is not news and
8769 the value "Any" causes any folder to match.
8770 If the value of "Current Folder Type" is set to "Specific",
8771 then you must fill in a value for "Folder", which is on the line
8772 below the "Specific" line.
8773 In this case you will only get a match if the currently open folder is
8774 the specific folder you list.
8775 You may give a list of folders instead of just a single
8776 folder name, in which case the Pattern will match if the open folder is
8777 any one of the folders in the list.
8778 The name of each folder in the list may be either "INBOX",
8779 the technical specification
8780 of the folder (like what appears in your configuration file) or, if the
8781 folder is one of your incoming folders, it may be the nickname you've given
8782 the folder.
8783 Here are some samples of specific folder names:
8784 <P>
8785 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
8786 <P>
8787 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
8788 <P>
8789 <CENTER><SAMP>mail/local-folder</SAMP></CENTER>
8790 <P>
8791 The easiest way to fill in the "Folder" field is to use
8792 the "T" command that is available when the "Folder" line is
8793 highlighted, or to use the "Take" command with the configuration
8794 feature
8795 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
8796 turned on.
8797 <P>
8798 When reading a newsgroup, there may be a performance penalty
8799 incurred when collecting the information necessary to check whether
8800 or not a Pattern matches a message.
8801 For this reason, the default Current Folder Type is set to "Email".
8802 If you have Patterns with a Current Folder Type of either
8803 "Any" or "News" and those Patterns are used for
8804 Index Line Coloring or Scoring, you may experience
8805 slower screen redrawing in the MESSAGE INDEX screen when in a newsgroup.
8807 <H3><A NAME="pattern_age_interval">Age Interval</A></H3>
8809 The "Age Interval" may be set to an interval of message
8810 ages that should be considered a match.
8811 Like the other parts of the Pattern, if it is unset it will be ignored.
8812 The Age Interval looks like
8813 <P>
8814 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
8815 <P>
8816 where "min_age" and "max_age" are integers greater
8817 than or equal to zero.
8818 The special value "INF" may be used for
8819 the max value. It represents infinity.
8820 <P>
8821 Actually, this option may be defined as a list of intervals instead
8822 of just a single interval.
8823 The list is separated by commas.
8824 It can look like
8825 <P>
8826 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
8827 <P>
8828 When there is an Age Interval defined, it is a match if the age, in days, of
8829 the message is contained in any of the intervals.
8830 The intervals include both endpoints.
8831 <P>
8832 Even though this option is called Age, it isn't actually
8833 the <EM>age</EM> of the message.
8834 Instead, it is how many days ago the message arrived in one of your folders.
8835 If the current time is a little past midnight, then a message that arrived
8836 just before midnight arrived yesterday, even though the message is only
8837 a few minutes old.
8838 By default, the date being used is not the date in the Date
8839 header of the message.
8840 It is the date that the message arrived in one of your folders.
8841 When you Save a message from one folder to another that arrival date
8842 is preserved.
8843 If you would like to use the date in the Date header that is possible.
8844 Turn on the option
8845 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
8846 near the bottom of the rule definition.
8847 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
8849 <H3><A NAME="pattern_size_interval">Size Interval</A></H3>
8851 The "Size Interval" may be set to an interval of message
8852 sizes that should be considered a match.
8853 Like the other parts of the Pattern, if it is unset it will be ignored.
8854 The Size Interval looks like
8855 <P>
8856 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
8857 <P>
8858 where "min_size" and "max_size" are integers greater
8859 than or equal to zero.
8860 The special value "INF" may be used for
8861 the max value. It represents infinity.
8862 <P>
8863 Actually, this option may be defined as a list of intervals instead
8864 of just a single interval.
8865 The list is separated by commas.
8866 It can look like
8867 <P>
8868 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
8869 <P>
8870 When there is a Size Interval defined, it is a match if the size, in bytes, of
8871 the message is contained in any of the intervals.
8872 The intervals include both endpoints.
8874 <H3><A NAME="pattern_score_interval">Score Interval</A></H3>
8876 The "Score Interval" may be set to an interval of message
8877 scores that should be considered a match.
8878 Like the other parts of the Pattern, if it is unset it will be ignored.
8879 The Score Interval looks like
8880 <P>
8881 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
8882 <P>
8883 where "min_score" and "max_score" are positive or
8884 negative integers, with min_score less than or equal to max_score.
8885 The special values "-INF" and "INF" may be used for
8886 the min and max values to represent negative and positive infinity.
8887 <P>
8888 Actually, a list of intervals may be used if you wish.
8889 A list would look like
8890 <P>
8891 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
8892 <P>
8893 When there is a Score Interval defined, it is a match if the score for
8894 the message is contained in any of the intervals in the list.
8895 The intervals include the endpoints.
8896 The score for a message is calculated by looking at every Score rule defined and
8897 adding up the Score Values for the ones that match the message.
8898 When deciding whether or not a Pattern matches a message for purposes of
8899 calculating the score, the Score Interval is ignored.
8901 <H3><A NAME="pattern_message_status">Message Status</A></H3>
8903 There are five separate message status settings.
8904 By default, all five are set to the value "Don't care", which
8905 will match any message.
8906 The value "Yes" means that the particular status must be true
8907 for a match, and the value "No" means that the particular
8908 status must not be true for a match.
8909 For example, one of the five Message Status settings is whether a message
8910 is marked Important or not.
8911 A "Yes" means that the message must be Important to be
8912 considered a match and "No" means that the message must not be
8913 Important to be considered a match.
8914 The same is true of the other four message status settings that depend
8915 on whether or not the message is New; whether the message has
8916 been Answered or not; whether the message has been Deleted or not, and
8917 whether the message is Recent or not.
8918 <P>
8919 The nomenclature for New and Recent is a bit confusing:
8920 <P>
8921 New means that the message is Unseen.
8922 It could have been in your mailbox for a long time but if you haven't looked
8923 at it, it is still considered New.
8924 That matches the default Alpine index display that shows an N for such a
8925 message.
8926 <P>
8927 Recent means that the message was added to this folder since the last time
8928 you opened the folder.
8929 Alpine also shows an N by default for these types of messages.
8930 If you were to run two copies of Alpine that opened a folder one right after
8931 the other, a message would only show up as Recent in (at most) the first
8932 Alpine session.
8934 <H3><A NAME="pattern_message_keywords">Message Keywords</A></H3>
8936 Keywords are similar to Message Status, but they are chosen by the user.
8937 Provided the mail server allows for it, you may add a set of possible keywords
8938 to a folder and then you may set those keywords or not for each message
8939 in the folder (see <A HREF="h_common_flag">Flag Command</A>).
8940 The syntax of this part of the Pattern is similar to the header patterns.
8941 It is a list of keywords.
8942 The Keyword part of the Pattern is a match if the message has any of
8943 the keywords in the list set.
8944 Like other parts of the Pattern, if this is unset it will be ignored.
8946 <H3><A NAME="pattern_message_charsets">Message Character Sets</A></H3>
8948 A message may use one or more character sets.
8949 This part of the Pattern matches messages that make use of one or more of
8950 the character sets specified in the pattern.
8951 It will be considered a match if a message uses any of the character
8952 sets in the list you give here.
8954 <P>
8955 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
8956 GB2312) you may also use some shorthand names that Alpine provides.
8957 These names are more understandable shorthand names for sets of
8958 character set names.
8959 Two examples are "Cyrillic" and "Greek".
8960 Selecting one of these shorthand names is equivalent to selecting all of
8961 the character sets that make up the set.
8962 You can see all of these shorthand names and the lists of character sets
8963 they stand for by typing the "T" command with the Character
8964 Set pattern highlighted.
8965 The syntax of this part of the Pattern is similar to the header patterns
8966 and the Message Keywords pattern.
8967 It is a list of character sets (or shorthand names).
8968 The Character Set part of the Pattern is a match if the message uses any
8969 of the character sets in the list.
8970 Like other parts of the Pattern, if this is unset it will be ignored.
8972 <H3><A NAME="pattern_8bit_subject">Raw 8-bit in Subject</A></H3>
8974 It seems that lots of unwanted email contains unencoded 8-bit characters
8975 in the Subject.
8976 Normally, characters with the 8th bit set are not allowed in the Subject
8977 header unless they are MIME-encoded.
8978 This option gives you a way to match messages that have Subjects that
8979 contain unencoded 8-bit characters.
8980 By default, the value of this option is "Don't care", which
8981 will match any message.
8982 The value "Yes" means that there must be raw 8-bit characters in
8983 the Subject of the message in order for there to be a match,
8984 and the value "No" is the opposite.
8985 Setting this option will affect performance in large folders because the
8986 subject of each message in the folder has to be checked.
8988 <H3><A NAME="pattern_bom">Beginning of Month</A></H3>
8990 This option gives you a way to take some action once per month.
8991 By default, the value of this option is "Don't care", which
8992 will always match.
8993 The value "Yes" means that this must be the first time Alpine has
8994 been run this month in order to count as a match,
8995 and the value "No" is the opposite.
8997 <H3><A NAME="pattern_boy">Beginning of Year</A></H3>
8999 This option gives you a way to take some action once per year.
9000 By default, the value of this option is "Don't care", which
9001 will always match.
9002 The value "Yes" means that this must be the first time Alpine has
9003 been run this year in order to count as a match,
9004 and the value "No" is the opposite.
9006 <H3><A NAME="pattern_abookfrom">Address in Address Books</A></H3>
9008 This option gives you a way to match messages that have an address
9009 that is in one of your address books.
9010 Only the simple entries in your address books are searched.
9011 Address book distribution lists are ignored!
9012 By default, the value of this option is "Don't care", which
9013 will match any message.
9014 The value "Yes, in any address book" means the address
9015 from the message must be in at least one of your
9016 address books in order to be a match.
9017 The value "No, not in any address book"
9018 means none of the addresses may
9019 be in any of your address books in order to be a match.
9020 The values "Yes, in specific address books" and
9021 "No, not in any of specific address books" are similar but instead
9022 of depending on all address books you are allowed to give a list of address
9023 books to look in.
9024 The addresses from the message that are checked for are determined by the
9025 setting you have for "Types of addresses to check for in address book".
9026 If you set this to "From" the From address from the message will
9027 be looked up in the address book.
9028 If you set it to only "To" then the To addresses will be used.
9029 If any of the To addresses are in the address book then it is considered
9030 a match for "Yes" or not a match for "No".
9031 You could set it to both From and To, in which case all of the From and To
9032 addresses are used.
9033 The "Reply-To" and "Sender" cases are a little unusual.
9034 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
9035 exists or the From address if there is no Reply-To address.
9036 Same for the Sender address.
9037 Setting this option may affect performance in large folders because the
9038 From and Reply-To of each message in the folder have to be checked.
9040 <H3><A NAME="pattern_categorizer">Categorizer Command</A></H3>
9042 This is a command that is run with its standard input set to the message
9043 being checked and its standard output discarded.
9044 The full directory path should be specified.
9045 The command will be run and then its exit status will be checked against
9046 the Exit Status Interval, which defaults to just the value zero.
9047 If the exit status of the command falls in the interval, it is considered
9048 a match, otherwise it is not a match.
9049 <P>
9051 This option may actually be a list of commands.
9052 The first one that exists and is executable is used.
9053 That makes it possible to use the same configuration with Unix Alpine and
9054 PC-Alpine.
9055 <P>
9057 If none of the commands in the list exists and is executable then the rule
9058 is <EM>not</EM> a match.
9059 If it is possible that the command may not exist, you should be careful
9060 to structure your rules so that nothing destructive
9061 happens when the command does not exist.
9062 For example, you might have a filter that filters away spam when there is
9063 a match but does nothing when there is not a match.
9064 That would continue to work correctly if the command didn't exist.
9065 However, if you have a filter that filters away spam when there is not
9066 a match and keeps it when there is a match, that would filter everything
9067 if the categorizer command didn't exist.
9068 <P>
9069 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
9070 setup for the bogofilter filter.
9072 <P>
9073 <End of help on this topic>
9074 </BODY>
9075 </HTML>
9076 ===== h_rules_roles =====
9077 <HTML>
9078 <HEAD>
9079 <TITLE>SETUP ROLES SCREEN</TITLE>
9080 </HEAD>
9081 <BODY>
9082 <H1>SETUP ROLES SCREEN</H1>
9083 <H2>SETUP ROLES COMMANDS</H2>
9084 <!--chtml if pinemode="function_key"-->
9085 <PRE>
9086 Available Commands -- Group 1 Available Commands -- Group 2
9087 ------------------------------- ------------------------------
9088 F1 Show Help Text F1 Show Help Text
9089 F2 See commands in next group F2 See commands in next group
9090 F3 Back to MAIN Alpine menu
9091 F4 Change configuration for role
9092 F5 Move to previous role F5 Include file in role config
9093 F6 Move to next role F6 Exclude file from config
9094 F7 Previous page of roles
9095 F8 Next page of roles
9096 F9 Add new role F9 Replicate existing role
9097 F10 Delete existing role
9098 F11 Shuffle the order of roles
9099 F12 Whereis (search role nicknames)
9100 </PRE>
9101 <!--chtml else-->
9102 <PRE>
9103 Navigation General Alpine Commands
9104 ------------------------- -----------------------
9105 P Prev Role ? Display this help text
9106 N Next Role E Back to MAIN Alpine menu
9107 - Previous page
9108 Spc (space bar) Next page
9109 W WhereIs (search for word in role nicknames)
9111 Setup Roles Commands
9112 ------------------------------------------------
9113 A Add new role $ Shuffle the order of roles
9114 D Delete existing role C Change configuration for highlighted role
9115 R Replicate existing role
9116 I Include file in role config X Exclude file from role config
9117 </PRE>
9118 <!--chtml endif-->
9120 <H2>Description of the Setup Roles Screen</H2>
9122 This screen lets you add, delete, modify, or change the order of the rules
9123 that determine the role you are playing when composing a message.
9124 <P>
9125 You may play different roles depending on who you are replying to.
9126 For example, if you are replying to a message addressed to help-desk you
9127 may be acting as a Help Desk Worker.
9128 That role may require that you use a different return address and/or
9129 a different signature.
9130 <P>
9131 Roles are optional.
9132 If you set up roles they work like this: Each role has a set of
9133 "Uses", which indicate whether or not a role is eligible to be
9134 considered for a particular use; a "Pattern",
9135 which is used to decide which of the eligible roles is used; and a set
9136 of "Actions", which are taken when that role is used.
9137 When you reply to a message, the message you are replying to is compared
9138 with the Patterns of the roles marked as eligible for use when replying.
9139 The comparisons start with the first eligible role and keep going until there
9140 is a match.
9141 If a match is found, the matching role's Actions are taken.
9142 <P>
9143 It is also possible to set a default role and to change that role during
9144 your Alpine session.
9145 When you start Alpine no default role will be set.
9146 You may set or change the current default role by using the "D"
9147 command in the role selection screen.
9148 You'll see that screen while composing a message and being asked to select
9149 a role.
9150 An easy way to get to that screen is to use the <A HREF="h_common_role">Role Command</A> to
9151 compose a message.
9152 You may find a default role useful if you normally perform the duties of one
9153 of your roles for a while, then you switch to another role and stay in the
9154 new role for another period of time.
9155 It may be easier than using the Role Command to select the role each time you
9156 compose a message.
9158 <H2>Role Uses</H2>
9160 There are three types of use to be configured;
9161 one for Replying, one for Forwarding, and one for Composing.
9162 These indicate whether or not you want a role to be considered when you
9163 type the Reply, Forward, or Compose commands.
9164 (The Role command is an alternate form of the Compose command, and it is
9165 not affected by these settings.)
9166 Each of these Use types has three possible values.
9167 The value "Never"
9168 means that the role will never be considered as a candidate for use with
9169 the corresponding command.
9170 For example, if you set a role's Reply Use to Never, then when you Reply to
9171 a message, that role won't even be considered.
9172 (That isn't quite true. If the message you are replying to matches some other
9173 role that requires confirmation,
9174 then there will be a ^T command available which allows you to select a role
9175 from all of your roles, not just the reply-eligible roles.)
9176 <P>
9178 The options "With confirmation" and "Without confirmation"
9179 both mean that you do want to consider this role when using the corresponding
9180 command.
9181 For either of these settings the role's Pattern will
9182 be checked to see if it matches the message.
9183 For Reply Use, the message used to compare the Pattern with is the message
9184 being replied to.
9185 For Forward Use, the message used to compare the Pattern with is the message
9186 being forwarded.
9187 For Compose Use, there is no message, so the parts of the Pattern that depend
9188 on a message (everything other than Current Folder Type) are ignored.
9189 In all cases, the Current Folder Type is checked if defined.
9190 If there is a match then this role will either be used without confirmation
9191 or will be the default when confirmation is asked for, depending on
9192 which of the two options is selected.
9193 If confirmation is requested, you will have a chance to
9194 choose No Role instead of the offered role, or to
9195 change the role to any one of your other roles (with the ^T command).
9197 <H2>Role Patterns</H2>
9199 In order to determine whether or not a message matches a role the message is
9200 compared with the Role's Pattern.
9201 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9202 Scoring, Other Rules, and Search Rules, so are described in only one place,
9203 "<A HREF="h_rule_patterns">here</A>".
9204 <P>
9205 Since header patterns, AllText patterns, and BodyText patterns that are unset are ignored,
9206 a role that has all header patterns unset, the AllText pattern unset,
9207 the BodyText pattern unset,
9208 the Score Interval unset, and the Current Folder Type set to
9209 "Any" may be used as a default role.
9210 It should be put last in the list of roles since the matching
9211 starts at the beginning and proceeds until one of the roles is a match.
9212 If no roles at all match, then Alpine will
9213 use its regular methods of defining the role.
9214 If you wanted to, you could define a different "default" role
9215 for Replying, Forwarding, and Composing by setting the
9216 "Use" fields appropriately.
9218 <H2>Role Actions</H2>
9220 Once a role match is found, the role's Actions are taken.
9221 For each role there are several possible actions that may be defined.
9222 They are actions to set the From address, the Reply-To address,
9223 the Fcc, the Signature, the Template file, and Other Headers.
9225 <H3>Set From</H3>
9227 The From address is the address used on the From line of the message
9228 you are sending.
9230 <H3>Set Reply-To</H3>
9232 The Reply-To address is the address used on the Reply-To line of the message
9233 you are sending.
9234 You don't need a Reply-To address unless it is different from the From address.
9236 <H3>Set Other Headers</H3>
9238 If you want to set the value of the From or Reply-To headers, use
9239 the specific fields "Set From" or "Set Reply-To".
9240 If you want to set the values of other headers, use this field.
9241 This field is similar to the
9242 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> configuration option.
9243 Each header you specify here must include the header tag
9244 ("To:", "Approved:", etc.)
9245 and may optionally include a value for that header.
9246 It is different from the <!--#echo var="VAR_customized-hdrs"--> in that the value you give
9247 for a header here will replace any value that already exists.
9248 For example, if you are Replying to a message there will be at least one
9249 address in the To header (the address you are Replying to).
9250 However, if you Reply using a role that sets the To header, that role's
9251 To header value will be used instead.
9253 <H3>Set Fcc</H3>
9255 The Fcc is used as the Fcc for the message you are sending.
9257 <H3>Set Signature or Set LiteralSig</H3>
9259 The Signature is the name of a file to be used as the signature file when
9260 this role is being used.
9261 If the name of the file has a vertical bar following it (|)
9262 then it is assumed that the file is a program that should be run to
9263 produce the signature.
9264 If the LiteralSig is set, then it is used instead of the signature file.
9265 LiteralSig is just a different way to store the signature.
9266 It is stored in the pine configuration file instead of in a separate
9267 signature file.
9268 If the <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined
9269 either in the role or as the default signature in the Setup/Config screen,
9270 then the signature file is ignored.
9272 <H3>Set Template</H3>
9274 A Template is the name of a file to be included in the message when this
9275 role is being used.
9276 If the name of the file has a vertical bar following it (|)
9277 then it is assumed that the file is a program that should be run to
9278 produce the template.
9280 <P>
9281 Both signature files and template files may be stored remotely on an IMAP
9282 server.
9283 In order to do that you just give the file a remote name.
9284 This works just like the regular
9285 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>
9286 option that is configured from the Setup/Configuration screen.
9287 A remote signature file name might look like:
9288 <P>
9289 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
9290 <P>
9291 Once you have named the remote signature or template file you create its
9292 contents by using the "F" "editFile" command when the
9293 cursor is on the "Set Signature" or "Set Template"
9294 line of the role editor.
9296 <P>
9297 Both signature files and template files (or the output of signature programs
9298 and template file programs) may contain special tokens
9299 that are replaced with contents
9300 that depend on the message being replied to or forwarded.
9301 See the help for the individual fields inside the role editor for more
9302 information on tokens.
9304 <H3>Use SMTP Server</H3>
9306 If this field has a value, then it will be used as the SMTP server
9307 to send mail when this role is being used (unless the SMTP server variable
9308 is set in the system-wide fixed configuration file).
9309 It has the same semantics as the
9310 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
9311 variable in the Setup/Config screen.
9312 When you postpone the composition this SMTP server list will be saved
9313 with the postponed composition and it cannot be changed later.
9314 Because of that, you may want to make this a list of SMTP servers
9315 with the preferred server at the front of the list and alternate servers
9316 later in the list.
9318 <P>
9319 If any of the actions are left unset, then the action depends on what
9320 is present in the "Initialize settings using role" field.
9321 If you've listed the nickname of another one of your roles there, then the
9322 corresponding action from that role will be used here.
9323 If that action is also blank, or if there is no nickname specified,
9324 then Alpine will do whatever it normally does to set these actions.
9325 This depends on other configuration options and features you've set.
9327 <H2>Command Descriptions</H2>
9329 <H3>Add</H3>
9331 The Add command is used to add a new role definition to your set of
9332 roles.
9333 The new role will be added after the highlighted role.
9335 <H3>Delete</H3>
9337 The Delete command deletes the currently highlighted role.
9339 <H3>Change</H3>
9341 The Change command lets you edit the nickname, Uses, Pattern,
9342 and Actions of the currently highlighted role.
9344 <H3>Shuffle</H3>
9346 The Shuffle command allows you to change the order of the roles.
9347 You may move the currently highlighted role up or down in the list.
9348 The order of the roles is important since the roles are tested for a
9349 match starting with the first role and continuing until a match is found.
9350 You should place the roles with more specific Patterns near the beginning
9351 of the list, and those with more general Patterns near the end so that
9352 the more specific matches will happen when appropriate.
9354 <H3>Replicate</H3>
9356 The Replicate command is used to copy an existing role and modify it.
9357 The new role will be added after the highlighted role.
9359 <H3>IncludeFile</H3>
9361 The IncludeFile command allows you to add a roles file to your configuration.
9362 Usually, your roles will be contained in your Alpine configuration file.
9363 If you wish, some or all of your roles may be stored in a separate file.
9364 If a roles file already exists (maybe it was made by somebody else using
9365 Alpine), you may insert it before the currently highlighted role.
9366 You may also insert an empty file or a file that does not yet exist.
9367 Once you have an empty roles file in your configuration, you may use
9368 the Shuffle command to move roles into it.
9369 In fact, that's the only way to get the initial role into the file.
9371 <H3>eXcludeFile</H3>
9373 The eXcludeFile command removes a roles file from your roles configuration.
9374 A limitation of the program is that in order to exclude a roles file
9375 that file must have at least one role
9376 in it, otherwise you won't be able to highlight a line in the file.
9377 So you may have to add a dummy role to the file in order to exclude the file.
9378 <P><UL>
9379 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9380 </UL>
9381 <P>
9382 <End of help on this topic>
9383 </BODY>
9384 </HTML>
9385 ===== h_rules_other =====
9386 <HTML>
9387 <HEAD>
9388 <TITLE>SETUP OTHER RULES SCREEN</TITLE>
9389 </HEAD>
9390 <BODY>
9391 <H1>SETUP OTHER RULES SCREEN</H1>
9392 <H2>SETUP OTHER RULES COMMANDS</H2>
9393 <!--chtml if pinemode="function_key"-->
9394 <PRE>
9395 Available Commands -- Group 1 Available Commands -- Group 2
9396 ------------------------------- ------------------------------
9397 F1 Show Help Text F1 Show Help Text
9398 F2 See commands in next group F2 See commands in next group
9399 F3 Back to MAIN Alpine menu
9400 F4 Change configuration for rule
9401 F5 Move to previous rule F5 Include file in rule config
9402 F6 Move to next rule F6 Exclude file from config
9403 F7 Previous page of rules
9404 F8 Next page of rules
9405 F9 Add new rule F9 Replicate existing rule
9406 F10 Delete existing rule
9407 F11 Shuffle the order of rules
9408 F12 Whereis (search rule nicknames)
9409 </PRE>
9410 <!--chtml else-->
9411 <PRE>
9412 Navigation General Alpine Commands
9413 ------------------------- -----------------------
9414 P Prev rule ? Display this help text
9415 N Next rule E Back to MAIN Alpine menu
9416 - Previous page
9417 Spc (space bar) Next page
9418 W WhereIs (search for word in rule nicknames)
9420 Setup Other Rules Commands
9421 ------------------------------------------------
9422 A Add new rule $ Shuffle the order of rules
9423 D Delete existing rule C Change configuration for highlighted rule
9424 R Replicate existing rule
9425 I Include file in rule config X Exclude file from rule config
9426 </PRE>
9427 <!--chtml endif-->
9429 <H2>Description of the Setup Other Rules Screen</H2>
9431 This is where you may set various actions that do not fit well into the
9432 other Rules categories.
9434 <H2>Patterns</H2>
9436 Other Rules are a little different from the rest of the Rules because
9437 they depend only on the current folder, and not on a particular message.
9438 In order to determine whether or not a rule's actions should be applied
9439 the current folder is compared with the rule's Pattern, which consists
9440 of only the Current Folder Type.
9441 Current Folder Type works the same for Other Rules as it does for Roles,
9442 Filtering, Index Coloring, and Scoring.
9443 Keep in mind that the only part of the Pattern that applies to Other
9444 Rules is the Current Folder Type when looking at the description of
9445 Patterns given
9446 "<A HREF="h_rule_patterns">here</A>".
9448 <H2>The Actions</H2>
9450 <H3>Set Sort Order</H3>
9452 When you enter a new folder, these rules will be checked to see if you
9453 have set a sort order that is different from your default sort order.
9454 The default is set in the Setup/Config screen with
9455 the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
9456 If the Sort Order action is set, then the folder will be displayed sorted in
9457 that sort order instead of in the default order.
9458 <P>
9459 A possible point of confusion arises when you change the configuration
9460 of the Sort Order for the currently open folder.
9461 The folder will normally be re-sorted when you go back to viewing the
9462 index.
9463 However, if you have manually sorted the folder with the
9464 Sort
9465 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
9466 command, then it will not be re-sorted until the next time it is opened.
9468 <H3>Set Index Format</H3>
9470 When you enter a new folder, these rules will be checked to see if you
9471 have set an Index Format that is different from your default Index Format,
9472 which is set with the
9473 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
9474 If so, the index will be displayed with this format instead of the default.
9476 <H3>Set Startup Rule</H3>
9478 When you enter a new folder, these rules will be checked to see if you
9479 have set a startup rule that is different from the default startup rule.
9480 The default for incoming folders is set in the Setup/Config screen with
9481 the "<!--#echo var="VAR_incoming-startup-rule"-->" option.
9482 The default for folders other than INBOX that are not part of your
9483 incoming collection
9484 (see <A HREF="h_config_enable_incoming"><!--#echo var="FEAT_enable-incoming-folders"--></A> feature)
9485 is to start with the last message in the folder.
9486 If the Startup Rule is set to something other than "default",
9487 then the rule will determine which message will be the current message when
9488 the folder is first opened.
9489 <P>
9490 The various startup rule possibilities work the same here as they do in
9491 the incoming collection, so check
9492 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
9493 for more help.
9495 <H2>Command Descriptions</H2>
9497 <H3>Add</H3>
9499 The Add command is used to add a new rule definition to your set of
9500 rules.
9501 The new rule will be added after the highlighted rule.
9503 <H3>Delete</H3>
9505 The Delete command deletes the currently highlighted rule.
9507 <H3>Change</H3>
9509 The Change command lets you edit the nickname, Pattern,
9510 and Action of the currently highlighted rule.
9512 <H3>Shuffle</H3>
9514 The Shuffle command allows you to change the order of the rules.
9515 You may move the currently highlighted rule up or down in the list.
9516 The order of the rules is important since the rules are tested for a
9517 match starting with the first rule and continuing until a match is found.
9518 You should place the rules with more specific Patterns near the beginning
9519 of the list, and those with more general Patterns near the end so that
9520 the more specific matches will happen when appropriate.
9522 <H3>Replicate</H3>
9524 The Replicate command is used to copy an existing rule definition and modify it.
9525 The new rule will be added after the highlighted rule.
9527 <H3>IncludeFile</H3>
9529 The IncludeFile command allows you to add a rules file to your configuration.
9530 Usually, your rules will be contained in your Alpine configuration file.
9531 If you wish, some or all of your rules may be stored in a separate file.
9532 If a rules file already exists (maybe it was made by somebody else using
9533 Alpine), you may insert it before the currently highlighted rule.
9534 You may also insert an empty file or a file that does not yet exist.
9535 Once you have an empty rules file in your configuration, you may use
9536 the Shuffle command to move rules into it.
9537 In fact, that's the only way to get the initial rule into the file.
9539 <H3>eXcludeFile</H3>
9541 The eXcludeFile command removes a rules file from your rules configuration.
9542 A limitation of the program is that in order to exclude a rules file
9543 that file must have at least one rule
9544 in it, otherwise you won't be able to highlight a line in the file.
9545 So you may have to add a dummy rule to the file in order to exclude the file.
9546 <P><UL>
9547 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9548 </UL>
9549 <P>
9550 <End of help on this topic>
9551 </BODY>
9552 </HTML>
9553 ===== h_rules_srch =====
9554 <HTML>
9555 <HEAD>
9556 <TITLE>SETUP SEARCH RULES SCREEN</TITLE>
9557 </HEAD>
9558 <BODY>
9559 <H1>SETUP SEARCH RULES SCREEN</H1>
9560 <H2>SETUP SEARCH RULES COMMANDS</H2>
9561 <!--chtml if pinemode="function_key"-->
9562 <PRE>
9563 Available Commands -- Group 1 Available Commands -- Group 2
9564 ------------------------------- ------------------------------
9565 F1 Show Help Text F1 Show Help Text
9566 F2 See commands in next group F2 See commands in next group
9567 F3 Back to MAIN Alpine menu
9568 F4 Change configuration for rule
9569 F5 Move to previous rule F5 Include file in rule config
9570 F6 Move to next rule F6 Exclude file from config
9571 F7 Previous page of rules
9572 F8 Next page of rules
9573 F9 Add new rule F9 Replicate existing rule
9574 F10 Delete existing rule
9575 F11 Shuffle the order of rules
9576 F12 Whereis (search rule nicknames)
9577 </PRE>
9578 <!--chtml else-->
9579 <PRE>
9580 Navigation General Alpine Commands
9581 ------------------------- -----------------------
9582 P Prev rule ? Display this help text
9583 N Next rule E Back to MAIN Alpine menu
9584 - Previous page
9585 Spc (space bar) Next page
9586 W WhereIs (search for word in rule nicknames)
9588 Setup Search Rules Commands
9589 ------------------------------------------------
9590 A Add new rule $ Shuffle the order of rules
9591 D Delete existing rule C Change configuration for highlighted rule
9592 R Replicate existing rule
9593 I Include file in rule config X Exclude file from rule config
9594 </PRE>
9595 <!--chtml endif-->
9597 <H2>Description of the Setup Search Rules Screen</H2>
9599 One of the commands that becomes available when that feature is turned on
9600 is the "; Select" command, which is used in the MESSAGE INDEX
9601 screen to select a set of messages.
9602 One way of selecting messages is to use a Rule.
9603 All of the messages that match (or don't match if you wish)
9604 a Rule's Pattern will be selected.
9605 <P>
9606 Any of your Rules may be used for this purpose.
9607 You might already have Rules set up for filtering, index line color, scores, or roles;
9608 and you may use any of those Rules with the Select command.
9609 However, you might find it more convenient to set up a separate set of Rules
9610 just for this purpose without having to worry about what other effects
9611 they may cause.
9612 That is the purpose of these Select Rules.
9614 <P>
9615 Each rule has a "Pattern"
9616 that is used to decide which messages are selected when you use it with
9617 the Select command.
9619 <H2>Patterns</H2>
9621 In order to determine whether or not a message should be selected
9622 the message is compared with the rule's Pattern.
9623 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9624 Scoring, Other Rules, and Search Rules, so are described in only one place,
9625 "<A HREF="h_rule_patterns">here</A>".
9627 <H2>Command Descriptions</H2>
9629 <H3>Add</H3>
9631 The Add command is used to add a new rule definition to your set of
9632 rules.
9633 The new rule will be added after the highlighted rule.
9635 <H3>Delete</H3>
9637 The Delete command deletes the currently highlighted rule.
9639 <H3>Change</H3>
9641 The Change command lets you edit the nickname and Pattern
9642 of the currently highlighted rule.
9644 <H3>Shuffle</H3>
9646 The Shuffle command allows you to change the order of the rules.
9647 This affects only the order they are presented in when you use the
9648 ^T subcommand of the Select by Rule command.
9649 You may move the currently highlighted rule up or down in the list.
9651 <H3>Replicate</H3>
9653 The Replicate command is used to copy an existing rule definition and modify it.
9654 The new rule will be added after the highlighted rule.
9656 <H3>IncludeFile</H3>
9658 The IncludeFile command allows you to add a rules file to your configuration.
9659 Usually, your rules will be contained in your Alpine configuration file.
9660 If you wish, some or all of your rules may be stored in a separate file.
9661 If a rules file already exists (maybe it was made by somebody else using
9662 Alpine), you may insert it before the currently highlighted rule.
9663 You may also insert an empty file or a file that does not yet exist.
9664 Once you have an empty rules file in your configuration, you may use
9665 the Shuffle command to move rules into it.
9666 In fact, that's the only way to get the initial rule into the file.
9668 <H3>eXcludeFile</H3>
9670 The eXcludeFile command removes a rules file from your rules configuration.
9671 A limitation of the program is that in order to exclude a rules file
9672 that file must have at least one rule
9673 in it, otherwise you won't be able to highlight a line in the file.
9674 So you may have to add a dummy rule to the file in order to exclude the file.
9675 <P><UL>
9676 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9677 </UL>
9678 <P>
9679 <End of help on this topic>
9680 </BODY>
9681 </HTML>
9682 ===== h_rules_incols =====
9683 <HTML>
9684 <HEAD>
9685 <TITLE>SETUP INDEX LINE COLORS SCREEN</TITLE>
9686 </HEAD>
9687 <BODY>
9688 <H1>SETUP INDEX LINE COLORS SCREEN</H1>
9689 <H2>SETUP INDEX LINE COLORS COMMANDS</H2>
9690 <!--chtml if pinemode="function_key"-->
9691 <PRE>
9692 Available Commands -- Group 1 Available Commands -- Group 2
9693 ------------------------------- ------------------------------
9694 F1 Show Help Text F1 Show Help Text
9695 F2 See commands in next group F2 See commands in next group
9696 F3 Back to MAIN Alpine menu
9697 F4 Change configuration for rule
9698 F5 Move to previous rule F5 Include file in rule config
9699 F6 Move to next rule F6 Exclude file from config
9700 F7 Previous page of rules
9701 F8 Next page of rules
9702 F9 Add new rule F9 Replicate existing rule
9703 F10 Delete existing rule
9704 F11 Shuffle the order of rules
9705 F12 Whereis (search rule nicknames)
9706 </PRE>
9707 <!--chtml else-->
9708 <PRE>
9709 Navigation General Alpine Commands
9710 ------------------------- -----------------------
9711 P Prev rule ? Display this help text
9712 N Next rule E Back to MAIN Alpine menu
9713 - Previous page
9714 Spc (space bar) Next page
9715 W WhereIs (search for word in rule nicknames)
9717 Setup Index Color Commands
9718 ------------------------------------------------
9719 A Add new rule $ Shuffle the order of rules
9720 D Delete existing rule C Change configuration for highlighted rule
9721 R Replicate existing rule
9722 I Include file in rule config X Exclude file from rule config
9723 </PRE>
9724 <!--chtml endif-->
9726 <H2>Description of the Setup Index Line Colors Screen</H2>
9728 Index Line Color causes lines in the MESSAGE INDEX screen to be colored.
9729 This action is only available if your terminal is capable of displaying
9730 color and color display has been enabled with the
9731 <A HREF="h_config_color_style">Color Style</A> option within the
9732 Setup Color screen.
9733 (In PC-Alpine, color is always enabled so there is no option to turn on.)
9734 This screen lets you add, delete, modify, or change the order of the rules
9735 that cause the lines in the MESSAGE INDEX to be displayed in different
9736 colors.
9737 <P>
9738 Each rule has a "Pattern",
9739 which is used to decide which of the rules is used; and the color that
9740 is used if the Pattern matches a particular message.
9742 <H2>Index Color Patterns</H2>
9744 In order to determine whether or not a message matches an Index Color Rule
9745 the message is compared with the rule's Pattern.
9746 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9747 Scoring, Other Rules, and Search Rules, so are described in only one place,
9748 "<A HREF="h_rule_patterns">here</A>".
9750 <P>
9751 If none of the Index Color rules is a match for a particular index line,
9752 then the color used is set using
9753 the <A HREF="h_color_setup">Setup Kolor</A> screen.
9755 <H2>Index Line Color</H2>
9757 This is the color that index lines are colored when there is a matching
9758 Pattern.
9759 This colors the whole index line, except possibly the status letters,
9760 which may be colored separately using
9761 the <A HREF="h_color_setup">Setup Kolor</A> screen.
9763 <H2>Command Descriptions</H2>
9765 <H3>Add</H3>
9767 The Add command is used to add a new rule definition to your set of
9768 rules.
9769 The new rule will be added after the highlighted rule.
9771 <H3>Delete</H3>
9773 The Delete command deletes the currently highlighted rule.
9775 <H3>Change</H3>
9777 The Change command lets you edit the nickname, Pattern,
9778 and Index Line Color of the currently highlighted rule.
9780 <H3>Shuffle</H3>
9782 The Shuffle command allows you to change the order of the rules.
9783 You may move the currently highlighted rule up or down in the list.
9784 The order of the rules is important since the rules are tested for a
9785 match starting with the first rule and continuing until a match is found.
9786 You should place the rules with more specific Patterns near the beginning
9787 of the list, and those with more general Patterns near the end so that
9788 the more specific matches will happen when appropriate.
9790 <H3>Replicate</H3>
9792 The Replicate command is used to copy an existing rule definition and modify it.
9793 The new rule will be added after the highlighted rule.
9795 <H3>IncludeFile</H3>
9797 The IncludeFile command allows you to add a rules file to your configuration.
9798 Usually, your rules will be contained in your Alpine configuration file.
9799 If you wish, some or all of your rules may be stored in a separate file.
9800 If a rules file already exists (maybe it was made by somebody else using
9801 Alpine), you may insert it before the currently highlighted rule.
9802 You may also insert an empty file or a file that does not yet exist.
9803 Once you have an empty rules file in your configuration, you may use
9804 the Shuffle command to move rules into it.
9805 In fact, that's the only way to get the initial rule into the file.
9807 <H3>eXcludeFile</H3>
9809 The eXcludeFile command removes a rules file from your rules configuration.
9810 A limitation of the program is that in order to exclude a rules file
9811 that file must have at least one rule
9812 in it, otherwise you won't be able to highlight a line in the file.
9813 So you may have to add a dummy rule to the file in order to exclude the file.
9814 <P><UL>
9815 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9816 </UL>
9817 <P>
9818 <End of help on this topic>
9819 </BODY>
9820 </HTML>
9821 ===== h_rules_filter =====
9822 <HTML>
9823 <HEAD>
9824 <TITLE>SETUP FILTERING SCREEN</TITLE>
9825 </HEAD>
9826 <BODY>
9827 <H1>SETUP FILTERING SCREEN</H1>
9828 <H2>SETUP FILTERING COMMANDS</H2>
9829 <!--chtml if pinemode="function_key"-->
9830 <PRE>
9831 Available Commands -- Group 1 Available Commands -- Group 2
9832 ------------------------------- ------------------------------
9833 F1 Show Help Text F1 Show Help Text
9834 F2 See commands in next group F2 See commands in next group
9835 F3 Back to MAIN Alpine menu
9836 F4 Change configuration for filter
9837 F5 Move to previous filter F5 Include file in filter config
9838 F6 Move to next filter F6 Exclude file from config
9839 F7 Previous page of filters
9840 F8 Next page of filters
9841 F9 Add new filter F9 Replicate existing filter
9842 F10 Delete existing filter
9843 F11 Shuffle the order of filters
9844 F12 Whereis (search filter nicknames)
9845 </PRE>
9846 <!--chtml else-->
9847 <PRE>
9848 Navigation General Alpine Commands
9849 ------------------------- -----------------------
9850 P Prev Filter ? Display this help text
9851 N Next Filter E Back to MAIN Alpine menu
9852 - Previous page
9853 Spc (space bar) Next page
9854 W WhereIs (search for word in filter nicknames)
9856 Setup Filters Commands
9857 ------------------------------------------------
9858 A Add new filter $ Shuffle the order of filters
9859 D Delete existing filter C Change configuration for highlighted filter
9860 R Replicate existing filter
9861 I Include file in filter config X Exclude file from filter config
9862 </PRE>
9863 <!--chtml endif-->
9865 <H2>Description of the Setup Filtering Screen</H2>
9867 This screen lets you add, delete, modify, or change the order of the rules
9868 that determine the filtering Alpine does on folders you view.
9869 <P>
9870 The software that actually delivers mail (the stuff that happens
9871 before Alpine is involved) for you is in a better position to do mail filtering
9872 than Alpine itself.
9873 If possible, you may want to look into using that sort of mail filtering to
9874 deliver mail to different folders, delete it, or forward it.
9875 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
9876 <P>
9877 Filtering is a way to automatically move certain messages from one folder
9878 to another or to delete messages.
9879 It can also be used to set message status (Important, Deleted, New,
9880 Answered) and to set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
9881 Alpine doesn't have the ability to forward mail to another address or
9882 to deliver vacation messages.
9883 <P>
9884 Each filtering rule has a "Pattern" and a "Filter Action".
9885 When a folder is opened, when new mail arrives in an open folder, or
9886 when mail is Expunged from a folder; each
9887 message is compared with the Patterns of your filtering rules.
9888 The comparisons start with the first rule and keep going until there
9889 is a match.
9890 If a match is found, the message may be deleted or moved, depending on
9891 the setting of the Filter Action.
9892 If the message is not deleted, it may have its status altered.
9894 <P>
9895 <EM>NOTE:</EM>
9896 When setting up a Pattern used to delete messages,
9897 it is recommended that you test the Pattern first with a "Move"
9898 folder specified in
9899 case unintended matches occur. Messages that are deleted will be removed
9900 from the folder and <EM>unrecoverable</EM> from within Alpine after the
9901 next Expunge command or once the folder being filtered has been closed.
9903 <H2>Filter Patterns</H2>
9905 In order to determine whether or not a message matches a filter the message is
9906 compared with the Filter's Pattern.
9907 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9908 Scoring, Other Rules, and Search Rules, so are described in only one place,
9909 "<A HREF="h_rule_patterns">here</A>".
9910 <P>
9911 Since filtering is a potentially destructive action, if you have a filtering
9912 Pattern with nothing other than Current Folder Type set, that filtering
9913 rule is ignored.
9915 <H2>Filter Actions</H2>
9917 Once a filter match is found for a particular message, there are some actions
9918 that may be taken.
9919 First, the message may have its status changed.
9920 This is the same message status that you can manipulate manually using the
9921 <a href="h_common_flag">Flag Command</a>.
9922 There are always four elements of message status that you can control.
9923 You can set or clear the Important status, the New status, the Deleted
9924 status, and the Answered status.
9925 Of course, if the filter is going to delete the message,
9926 then there is no point in setting message status.
9927 You may also be able to set user-defined keywords for a message.
9928 Read a little about keywords in the help text for the
9929 <A HREF="h_common_flag">Flag</A> command.
9930 <P>
9931 Second, the filter may delete or move the message.
9932 Deleting the message marks it Deleted and removes it from view.
9933 It is effectively gone forever (though it technically is still there until
9934 the next expunge command, which may happen implicitly).
9935 Moving the message moves it from the open folder into the folder
9936 listed on the "Folder List" line of the filter configuration.
9937 If you list more than one folder name (separated by commas) then the message
9938 will be copied to each of those folders.
9939 In any case, if "Delete" or "Move" is set then the
9940 message is removed from the current folder.
9941 If you just want to set the messages status without deleting it from
9942 the folder, then set the filter action to
9943 "Just Set Message Status".
9944 <P>
9945 (There is no way to do a Copy instead of a Move, due to the difficulties
9946 involved in keeping track of whether or not a message has
9947 already been copied.)
9949 <H2>Command Descriptions</H2>
9951 <H3>Add</H3>
9953 The Add command is used to add a new filter definition to your set of
9954 filters.
9955 The new filter will be added after the highlighted filter.
9957 <H3>Delete</H3>
9959 The Delete command deletes the currently highlighted filter.
9961 <H3>Change</H3>
9963 The Change command lets you edit the nickname, Pattern,
9964 and Folder of the currently highlighted filter.
9966 <H3>Shuffle</H3>
9968 The Shuffle command allows you to change the order of the filters.
9969 You may move the currently highlighted filter up or down in the list.
9970 The order of the filters is important since the filters are tested for a
9971 match starting with the first filter and continuing until a match is found.
9972 You should place the filters with more specific Patterns near the beginning
9973 of the list, and those with more general Patterns near the end so that
9974 the more specific matches will happen when appropriate.
9976 <H3>Replicate</H3>
9978 The Replicate command is used to copy an existing filter and modify it.
9979 The new filter will be added after the highlighted filter.
9981 <H3>IncludeFile</H3>
9983 The IncludeFile command allows you to add a filters file to your configuration.
9984 Usually, your filters will be contained in your Alpine configuration file.
9985 If you wish, some or all of your filters may be stored in a separate file.
9986 If a filters file already exists (maybe it was made by somebody else using
9987 Alpine), you may insert it before the currently highlighted filter.
9988 You may also insert an empty file or a file that does not yet exist.
9989 Once you have an empty filters file in your configuration, you may use
9990 the Shuffle command to move filters into it.
9991 In fact, that's the only way to get the initial filter into the file.
9993 <H3>eXcludeFile</H3>
9995 The eXcludeFile command removes a filters file from your filters configuration.
9996 A limitation of the program is that in order to exclude a filters file
9997 that file must have at least one filter
9998 in it, otherwise you won't be able to highlight a line in the file.
9999 So you may have to add a dummy filter to the file in order to exclude the file.
10000 <P><UL>
10001 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10002 </UL>
10003 <P>
10004 <H3>Performance Considerations</H3>
10005 The number and type of patterns being tested can
10006 adversely effect performance. Issues to be aware
10007 of include:
10008 <P>
10009 <UL>
10010 <LI> The more filters you have defined the longer it will take to run down
10011 the list. Deleting unused filters is a good idea.
10012 <LI> Filtering in newsgroups served by an NNTP server will be slow
10013 if your patterns include tests other than "From:"
10014 or "Subject:".
10015 </UL>
10016 <P>
10017 <End of help on this topic>
10018 </BODY>
10019 </HTML>
10020 ===== h_rules_score =====
10021 <HTML>
10022 <HEAD>
10023 <TITLE>SETUP SCORING SCREEN</TITLE>
10024 </HEAD>
10025 <BODY>
10026 <H1>SETUP SCORING SCREEN</H1>
10027 <H2>SETUP SCORING COMMANDS</H2>
10028 <!--chtml if pinemode="function_key"-->
10029 <PRE>
10030 Available Commands -- Group 1 Available Commands -- Group 2
10031 ------------------------------- ------------------------------
10032 F1 Show Help Text F1 Show Help Text
10033 F2 See commands in next group F2 See commands in next group
10034 F3 Back to MAIN Alpine menu
10035 F4 Change configuration for rule
10036 F5 Move to previous rule F5 Include file in rule config
10037 F6 Move to next rule F6 Exclude file from config
10038 F7 Previous page of rules
10039 F8 Next page of rules
10040 F9 Add new rule F9 Replicate existing rule
10041 F10 Delete existing rule
10042 F11 Shuffle the order of rules
10043 F12 Whereis (search rule nicknames)
10044 </PRE>
10045 <!--chtml else-->
10046 <PRE>
10047 Navigation General Alpine Commands
10048 ------------------------- -----------------------
10049 P Prev rule ? Display this help text
10050 N Next rule E Back to MAIN Alpine menu
10051 - Previous page
10052 Spc (space bar) Next page
10053 W WhereIs (search for word in rule nicknames)
10055 Setup Scoring Commands
10056 ------------------------------------------------
10057 A Add new rule $ Shuffle the order of rules
10058 D Delete existing rule C Change configuration for highlighted rule
10059 R Replicate existing rule
10060 I Include file in rule config X Exclude file from rule config
10061 </PRE>
10062 <!--chtml endif-->
10064 <H2>Description of the Setup Scoring Screen</H2>
10066 Most people will not use scores at all, but if you do use them, here's how
10067 they work in Alpine.
10068 Using this screen, you may define Scoring rules.
10069 The score for a message is calculated by looking at every Score rule defined
10070 and adding up the Score Values for the ones that match the message.
10071 If there are no matches for a message, it has a score of zero.
10072 Message scores may be used a couple of ways in Alpine.
10074 <H3>Sorting by Score</H3>
10076 One of the methods you may use to sort message indexes is to sort by
10077 score.
10078 The scores of all the messages in a folder will be calculated and then
10079 the index will be ordered by placing the messages in order of ascending or
10080 descending score.
10082 <H3>Scores for use in Patterns</H3>
10084 The Patterns used for Roles, Index Line Coloring, and Filtering have a
10085 category labeled "Score Interval".
10086 When a message is being compared with a Pattern to check for a match, if
10087 the Score Interval is set only messages that have a score somewhere in
10088 the interval are a match.
10090 <H2>Scoring Rule Patterns</H2>
10092 In order to determine whether or not a message matches a scoring rule
10093 the message is compared with the rule's Pattern.
10094 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10095 Scoring, Other Rules, and Search Rules, so are described in only one place,
10096 "<A HREF="h_rule_patterns">here</A>".
10098 <P>
10099 Actually, Scoring rule Patterns are slightly different from the other types of
10100 Patterns because Scoring rule Patterns don't contain a Score Interval.
10101 In other words, when calculating the score for a message, which is done
10102 by looking at the Scoring rule Patterns, scores aren't used.
10104 <H2>Score Value</H2>
10106 This is the value that will be added to the score for a message if the
10107 rule's Pattern is a match.
10108 Each individual Score Value is an integer between -100 and 100, and the
10109 values from matching rules are added together to get a message's score.
10110 There is also a way to extract the value from a particular header of each
10111 message. See the help text for Score Value for further information.
10113 <H2>Command Descriptions</H2>
10115 <H3>Add</H3>
10117 The Add command is used to add a new scoring rule definition.
10118 The new rule will be added after the highlighted rule.
10120 <H3>Delete</H3>
10122 The Delete command deletes the currently highlighted scoring rule.
10124 <H3>Change</H3>
10126 The Change command lets you edit the nickname, Pattern,
10127 and Score Value of the currently highlighted scoring rule.
10129 <H3>Shuffle</H3>
10131 The Shuffle command allows you to change the order of the scoring rules.
10132 You may move the currently highlighted rule up or down in the list.
10133 The order of the rules is important since the rules are tested for a
10134 match starting with the first rule and continuing until a match is found.
10135 You should place the rules with more specific Patterns near the beginning
10136 of the list, and those with more general Patterns near the end so that
10137 the more specific matches will happen when appropriate.
10139 <H3>Replicate</H3>
10141 The Replicate command is used to copy an existing rule and modify it.
10142 The new rule will be added after the highlighted rule.
10144 <H3>IncludeFile</H3>
10146 The IncludeFile command allows you to add a rules file to your configuration.
10147 Usually, your rules will be contained in your Alpine configuration file.
10148 If you wish, some or all of your rules may be stored in a separate file.
10149 If a rules file already exists (maybe it was made by somebody else using
10150 Alpine), you may insert it before the currently highlighted rule.
10151 You may also insert an empty file or a file that does not yet exist.
10152 Once you have an empty rules file in your configuration, you may use
10153 the Shuffle command to move rules into it.
10154 In fact, that's the only way to get the initial rule into the file.
10156 <H3>eXcludeFile</H3>
10158 The eXcludeFile command removes a rules file from your rules configuration.
10159 A limitation of the program is that in order to exclude a rules file
10160 that file must have at least one rule
10161 in it, otherwise you won't be able to highlight a line in the file.
10162 So you may have to add a dummy rule to the file in order to exclude the file.
10163 <P><UL>
10164 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10165 </UL>
10166 <P>
10167 <End of help on this topic>
10168 </BODY>
10169 </HTML>
10170 ===== h_direct_config =====
10171 <HTML>
10172 <HEAD>
10173 <TITLE>SETUP LDAP DIRECTORY SERVERS SCREEN</TITLE>
10174 </HEAD>
10175 <BODY>
10176 <H1>SETUP LDAP DIRECTORY SERVERS SCREEN</H1>
10177 <H2>SETUP LDAP DIRECTORY SERVERS COMMANDS</H2>
10178 <!--chtml if pinemode="function_key"-->
10179 <PRE>
10180 Available Commands
10181 -------------------------------
10182 F1 Show Help Text
10183 F3 Back to MAIN Alpine menu
10184 F4 Change configuration for directory server
10185 F5 Move to previous directory server
10186 F6 Move to next directory server
10187 F7 Previous page of directory servers
10188 F8 Next page of directory servers
10189 F9 Add new directory server
10190 F10 Delete existing directory server
10191 F11 Shuffle the order of directory servers
10192 F12 Whereis (search directory server titles)
10193 </PRE>
10194 <!--chtml else-->
10195 <PRE>
10196 Navigation General Alpine Commands
10197 ------------------------- -----------------------
10198 P Prev Directory Server ? Display this help text
10199 N Next Directory Server E Back to MAIN Alpine menu
10200 - Previous page
10201 Spc (space bar) Next page
10202 W WhereIs (search for word in directory server titles)
10204 Setup LDAP Directory Server Commands
10205 ------------------------------------------------
10206 A Add new directory server $ Shuffle the order of directory servers
10207 D Delete existing dir server C Change configuration for highlighted server
10208 </PRE>
10209 <!--chtml endif-->
10211 <H2>Description of the Setup LDAP Directory Servers Screen</H2>
10213 This screen lets you add, delete, modify, or change the order of your
10214 directory servers. You may also set some optional behavior for each server.
10215 The "Add Dir" command brings up a blank form to
10216 fill in. You will have to supply at least the name of the LDAP server.
10217 You will often have to supply a search base to be used with that server,
10218 as well. Once the form has been brought up on your screen, there is help
10219 available for each of the options you may set.
10220 <P>
10221 The "Del Dir" command allows you to remove a directory server
10222 from your configuration.
10223 <P>
10224 The "Change" command is similar to the "Add Dir" command.
10225 The difference is that instead of bringing up a form for a new server
10226 configuration, you are changing the configuration of an existing entry.
10227 For example, you might want to correct a typing error, change a
10228 nickname, or change one of the options set for that server.
10229 <P>
10230 The "Shuffle" command is used to change the order of directory
10231 servers.
10232 <P><UL>
10233 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10234 </UL>
10235 <P>
10236 <End of help on this topic>
10237 </BODY>
10238 </HTML>
10239 ============= h_address_display ========================
10240 <HTML>
10241 <HEAD>
10242 <TITLE>SEARCH RESULTS INDEX</TITLE>
10243 </HEAD>
10244 <BODY>
10245 <H1>SEARCH RESULTS INDEX</H1>
10246 This screen shows the results, if any, of your Directory Server search.
10247 Commands (besides those for screen navigation) are:
10248 <DL>
10249 <DT>View
10250 <!--chtml if pinemode="function_key"-->
10251 (F4)
10252 <!--chtml else-->
10253 (V)
10254 <!--chtml endif-->
10255 </DT>
10256 <DD>See the full information for the selected entry.
10258 <DT>Compose
10259 <!--chtml if pinemode="function_key"-->
10260 (F9)
10261 <!--chtml else-->
10262 (C)
10263 <!--chtml endif--></DT>
10264 <DD>Compose a message with the selected entry as the recipient.
10266 <DT>Role
10267 <!--chtml if pinemode="function_key"-->
10268 (F2)
10269 <!--chtml else-->
10270 (#)
10271 <!--chtml endif--></DT>
10272 <DD>Compose a message with the selected entry as the recipient. This differs
10273 from Compose in that you may select a role before beginning your composition.
10275 <DT>Forward
10276 <!--chtml if pinemode="function_key"-->
10277 (F10)
10278 <!--chtml else-->
10279 (F)
10280 <!--chtml endif--></DT>
10281 <DD>Send the full information for the selected entry as an
10282 email message to someone else.
10284 <DT>Save
10285 <!--chtml if pinemode="function_key"-->
10286 (F11)
10287 <!--chtml else-->
10288 (S)
10289 <!--chtml endif-->
10290 </DT>
10291 <DD>Save to your address book:
10292 <UL>
10293 <LI>the result of the search (as just found through your query) for the
10294 selected entry; or
10295 <LI>the selected entry for repeated Directory Server searching when used
10296 in the future.
10297 </UL>
10298 or<BR>
10299 Export to a file (external to Alpine):
10300 <UL>
10301 <LI>the full information for the selected entry; or
10302 <LI>the email address from the selected entry; or
10303 <LI>the selected entry in <A HREF="h_whatis_vcard">vCard</A> format.
10304 </UL>
10305 <DT>WhereIs
10306 <!--chtml if pinemode="function_key"-->
10307 (F12)
10308 <!--chtml else-->
10309 (W)
10310 <!--chtml endif-->
10311 </DT>
10312 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10313 displayed text, not the full records for each entry.)
10314 </DL>
10315 <End of help on this topic>
10316 </BODY>
10317 </HTML>
10318 ============= h_address_select ========================
10319 <HTML>
10320 <HEAD>
10321 <TITLE>SEARCH RESULTS INDEX</TITLE>
10322 </HEAD>
10323 <BODY>
10324 <H1>SEARCH RESULTS INDEX</H1>
10325 This screen shows the results, if any, of your Directory Server search.
10326 Commands (besides those for screen navigation) are:
10327 <DL>
10328 <DT>Select
10329 </DT>
10330 <DD>Select this entry for use.
10332 <DT>ExitSelect
10333 <DD>Exit without selecting any of the entries.
10335 <DT>WhereIs
10336 </DT>
10337 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10338 displayed text, not the full records for each entry.)
10339 </DL>
10340 <End of help on this topic>
10341 </BODY>
10342 </HTML>
10343 ===== h_folder_maint =====
10344 <HTML>
10345 <HEAD>
10346 <TITLE>Help for Folder List</TITLE>
10347 </HEAD>
10348 <BODY>
10349 <H1>FOLDER LIST COMMANDS</H1>
10350 <!--chtml if pinemode="function_key"-->
10351 <PRE>
10352 Available Commands -- Group 1 Available Commands -- Group 2
10353 ------------------------------- ------------------------------
10354 F1 Show Help Text F1 Show Help Text
10355 F2 See commands in next group F2 See commands in next group
10356 F3 MAIN MENU Screen F3 Quit Alpine
10357 F4 Select folder and view it F4 MAIN MENU Screen
10358 F5 Move to previous folder
10359 F6 Move to next folder F6 Specify a folder to go to
10360 F7 Show previous screen of listing F7 Show MESSAGE INDEX of current folder
10361 F8 Show next screen of listing F8 Compose a message
10362 F9 Add a new folder F9 Print folder listing
10363 F10 Delete selected folder
10364 F11 Rename selected folder
10365 F12 Whereis (search folder names)
10367 Available Commands -- Group 3
10368 F1 Show Help Text
10369 F2 See commands in next group
10370 F5 Go to next new message
10371 (or count recent messages if <A HREF="h_config_tab_checks_recent"><!--#echo var="FEAT_tab-checks-recent"--></A> is set)
10372 F8 Compose a message using roles
10373 F9 Export folder to a file
10374 F10 Import the file back to a folder
10375 </PRE>
10376 <!--chtml else-->
10377 <PRE>
10378 Navigating the Folder Screen Operations on the Selected Folder
10379 ---------------------------- ---------------------------------
10380 P Move to previous folder V View Index of selected folder
10381 N Move to next folder D Delete
10382 - Show previous page of listing R Rename
10383 Spc (space bar) Show next page E Export to file
10384 U Import from file to folder
10386 FOLDER LIST Screen Commands General Alpine Command
10387 --------------------------- -----------------------
10388 A Add a folder O Show all other available commands
10389 G Specify a folder to go to ? Show Help text
10390 I Show MESSAGE INDEX of current folder M MAIN MENU Screen
10391 W Whereis (search folder names) Q Quit Alpine
10392 % Print folder listing C Compose a message
10393 # Compose a message using roles
10394 </PRE>
10395 <!--chtml endif-->
10396 <P>
10397 These commands are only available in the FOLDER LIST screen when the
10398 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"
10399 feature</A> is set in the SETUP CONFIGURATION screen:<DL>
10400 <DT>Select:</DT>
10401 <DD>Select folders by certain criteria:<UL>
10402 <LI>All: of limited use, since there is no Apply command.
10403 <LI>by Property: <UL>
10404 <LI>folder contains messages not yet seen
10405 <LI>folder contains new messages
10406 <LI>folder contains exactly as many, more, or fewer messages
10407 than a given number
10408 </UL>
10409 <LI>by Text: <UL>
10410 <LI>contained in name of folder (Name Select)
10411 <LI>contained in messages in folder (Content Select)
10412 </UL>
10413 </UL></DD>
10415 <DT>Select current:</DT>
10416 <DD>Select the folder the cursor is on. (Can be used to "manually"
10417 add one or more folders to a set created with the Select command described
10418 above.)</DD>
10419 <DT>Zoom mode:</DT>
10420 <DD>Toggles display of only selected folders or all folders on and off.</DD>
10421 </DL>
10422 <P>
10423 If the feature
10424 <A HREF="h_config_tab_checks_recent">"<!--#echo var="FEAT_tab-checks-recent"-->"</A>
10425 is set then the TAB key will display the number of recent messages and
10426 the total number of messages in the highlighted folder.
10427 <P>
10428 The "Export" command causes the lowest common denominator style
10429 mailbox to be written to a file.
10430 If the file already exists, you are asked if you want to delete it.
10431 If you say No, then the operation is aborted.
10432 Export might be a reasonable way to store a backup or an archival copy of
10433 a folder.
10434 The exported-to file is a local file on the system where you are running Alpine.
10435 The "Import" command is the opposite of the Export command.
10436 It reads a file created by Export and asks where it should save it in your
10437 folders.
10438 This could be a new folder or an existing folder.
10439 If the folder already exists, the messages from the exported file will be
10440 appended to the folder.
10441 <P>
10442 <CENTER>Description of the FOLDER LIST Screen</CENTER>
10444 The purpose of the FOLDER LIST screen is to help you browse and manage
10445 the folders and directories (also known as "hierarchy")
10446 contained within a collection.
10448 <P>
10449 Folders and directories are arranged alphabetically across lines of
10450 the screen. Directories, if present, are denoted by a special
10451 character at the end of the name known as the hierarchy delimiter
10452 (typically, "/"). By default, folders and directories are
10453 mixed together. The
10454 "<A HREF="h_config_fld_sort_rule"><!--#echo var="VAR_folder-sort-rule"--></A>"
10455 configuration option can be used to group directories toward the
10456 beginning or end of the list.
10458 <P>
10459 The Next/Prev Page commands help browse the list, the Next/Prev Fldr
10460 commands change the "selected" (i.e., highlighted) folder or
10461 directory, and the View Fldr/Dir commands will "open" the
10462 selected item. Folder and directory management is provided via the
10463 Rename, Delete and Add commands.
10465 <P><CENTER>About Folders</CENTER>
10466 What are Folders?<P>
10468 Folders are simply files where messages are kept. Every message has to be
10469 in a folder. Most every Alpine user starts out with 3 folders: an INBOX, a
10470 folder for sent mail and a folder for saved messages.<P>
10472 You may create as many other folders as you wish. They must be given
10473 names that can be filenames on the filesystem.
10474 <P>
10476 You can move messages from one folder to another by opening the original
10477 folder and saving messages into the other folder just as you can save
10478 message from your INBOX to any other folder.<P>
10480 Folders are typically just files in the filesystem. However, the files
10481 that are
10482 folders have some special formatting in them (so that Alpine knows where one
10483 message ends and another begins) and should <EM>not</EM> be edited outside of
10484 Alpine. If you want copies of your messages in text files that you can edit
10485 or otherwise manipulate, use the Export command to copy them from Alpine into
10486 your regular file area.
10488 <P>
10489 FOR MORE INFORMATION: See the section on
10490 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
10491 <P>
10492 <CENTER>About Directories</CENTER>
10493 <P>
10494 A directory is simply a container used to group folders within a
10495 folder list. You can create as many directories as you like. And
10496 directories can even contain directories themselves.
10498 <P>
10499 SPECIAL NOTES: When accessing folders on an IMAP server, it is important
10500 to note that not all IMAP servers support directories. If you find that
10501 the Add command fails to offer the "Create Directory" subcommand,
10502 then it's likely that directories are not supported by the server serving
10503 in that collection.
10505 <P>
10506 Similarly, servers that do provide for directories may not do so in
10507 the same way. On some servers, for example, each folder name you
10508 create is at the same time capable of being a directory. When this
10509 happens, Alpine will display both the folder name and the name of the
10510 directory (with trailing hierarchy delimiter) in the folder list.
10512 <P>
10513 Another issue with IMAP access, though with a much smaller set of servers,
10514 is that not all servers accept the request to list out the available
10515 folders and directories in the same way. If you find yourself having
10516 trouble viewing folders on your server, you might investigate the
10517 "<A HREF="h_config_lame_list_mode"><!--#echo var="FEAT_enable-lame-list-mode"--></A>"
10518 feature.
10519 <P>
10520 <UL>
10521 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10522 </UL>
10523 <P>
10524 <End of help on this topic>
10525 </BODY>
10526 </HTML>
10527 ========= h_valid_folder_names ========
10528 <HTML>
10529 <HEAD>
10530 <TITLE>Explanation of Valid Folder Names</TITLE>
10531 </HEAD>
10532 <BODY>
10533 <H1>Folder Name Syntax Explained</H1>
10535 Once your folder collections are defined, you can usually refer to
10536 folders by their simple (unqualified) name, or pick from a FOLDER LIST
10537 display. However, understanding the complete syntax for folder names,
10538 both local and remote, is handy when using the Goto command and when
10539 you are adding new folder collections via the Setups/collectionList screen.
10540 <P>
10541 An Alpine folder name looks like
10543 <P>
10544 <CENTER><SAMP>[{<remote-specification>}][#<namespace>]<namespace-specific-part></SAMP></CENTER>
10545 <P>
10547 The square brackets ([]) mean that the part is optional.
10549 <P>
10550 If there is no remote-specification, then the folder name is interpreted
10551 locally on the computer running Alpine.
10552 Local folder names depend on the operating system used by the computer
10553 running Alpine, as well as the configuration of that system. For example,
10554 "C:\PINE\FOLDERS\OCT-94" might exist on a PC, and
10555 "~/mail/september-1994" might be a reasonable folder name on a
10556 system running Unix.
10558 <P>
10559 Alpine users have the option of using folders that are stored on some other
10560 computer. Alpine accesses remote folders via IMAP (the Internet Message
10561 Access Protocol), or in the case of news, via NNTP (the Network News
10562 Transport Protocol). To be able to access remote folders in Alpine, the
10563 remote host must be running the appropriate server software (imapd or
10564 nntpd) and you must correctly specify the name of the folder to Alpine,
10565 including the domain name of the remote machine. For example,
10566 <P>
10567 <CENTER><SAMP>{monet.art.example.com}INBOX</SAMP></CENTER>
10568 <P>
10569 could be a remote folder specification, and so could
10570 <P>
10571 <CENTER><SAMP>{unixhost.art.example.com}~/mail/september-1994</SAMP></CENTER>
10572 and
10573 <P>
10574 <CENTER><SAMP>{winhost.art.example.com}\mymail\SEP-94</SAMP></CENTER>
10575 <P>
10576 Note that in the case of remote folders, the directory/file path in the specification is
10577 determined by the operating system of the remote computer, <B>not</B> by
10578 the operating system of the computer on which you are running Alpine.
10579 <P>
10580 As you can tell, the name of the computer is in {} brackets
10581 followed immediately by the name of the folder. (In each of these cases the
10582 optional namespace is missing.) If, as in these
10583 examples, there is no remote access protocol specified, then IMAP is
10584 assumed. Check
10585 <A HREF="h_folder_server_syntax">here</A>
10586 for a more detailed look at what options can be placed between the brackets.
10587 If there are no brackets at all, then the folder name is interpreted locally
10588 on the computer on which you are running Alpine.
10590 <P>
10591 To the right of the brackets when a server name is present, or at the
10592 start of the foldername if no server is present, the sharp sign,
10593 "#", holds special meaning. It indicates a folder name
10594 outside the area reserved for your personal folders. In fact, it's
10595 used to indicate both the name of the folder, and a special phrase
10596 telling Alpine how to interpret the name that follows.
10598 <P>
10599 So, for example, Alpine can be used to access a newsgroup that might be
10600 available on your computer using:
10601 <P>
10602 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
10603 <P>
10604 The sharp sign indicates the folder name is outside your personal
10605 folder area. The "news." phrase after it tells Alpine to
10606 interpret the remainder of the name as a newsgroup.
10608 <P>
10609 Similarly, to access a newsgroup on your IMAP server, you might
10610 use something like:
10611 <P>
10612 <CENTER><SAMP>{wharhol.art.example.com}#news.comp.mail.misc</SAMP></CENTER>
10614 <P>
10615 There are a number of such special phrases (or "namespaces")
10616 available. For a more detailed explanation read about
10617 <A HREF="h_folder_name_namespaces">Namespaces</A>.
10619 <P>
10620 Note that "INBOX" has special meaning in both local and remote folder
10621 names. The name INBOX refers to your "principal incoming
10622 message folder" and will be mapped to the actual file name used for your
10623 INBOX on any given host. Therefore, a name like
10624 "{xxx.art.example.com}INBOX" refers to whatever file is used to
10625 store incoming mail for you on that particular host.
10627 <P>
10628 <End of help on this topic>
10629 </BODY>
10630 </HTML>
10631 ======= h_folder_name_namespaces =======
10632 <HTML>
10633 <HEAD>
10634 <TITLE>FOLDER NAME NAMESPACES EXPLAINED</TITLE>
10635 </HEAD>
10636 <BODY>
10637 <H1>Folder Name Namespaces Explained</H1>
10639 An Alpine folder name looks like
10641 <P>
10642 <CENTER><SAMP>[{<remote-specification>}][#<namespace>][<namespace-specific-part>]</SAMP></CENTER>
10643 <P>
10645 The local part of a folder name has an optional "Namespace" which
10646 tells Alpine how to interpret the rest of the name.
10648 <P>
10649 By default the folder name is interpreted as defining a section of your personal
10650 folder area. This area and how you specify it are defined by the
10651 server, if one is specified, or, typically, the home
10652 directory, if no server is defined.
10654 <P>
10655 If a namespace is specified, it begins with the
10656 sharp, "#", character followed by the name of the namespace
10657 and then the namespace's path-element-delimiter. Aside from the
10658 path's format, namespaces can also imply access rights, content
10659 policy, audience, location, and, occasionally, access methods.
10661 <P>
10662 Each server exports its own set (possibly of size one) of
10663 namespaces. Hence, it's likely communication with your server's
10664 administrator will be required for specific configurations. Some of
10665 the more common namespaces, however, include:
10667 <DL>
10668 <DT>#news.</DT>
10669 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
10670 names are hierarchically defined with each level delimited by a period.
10671 <P>
10672 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
10673 <P>
10674 </DD>
10675 <DT>#public/</DT>
10676 <DD>This specifies a folder area that the server may export to the general
10677 public.
10678 </DD>
10679 <DT>#shared/</DT>
10680 <DD>This specifies a folder area that the server may export to groups
10681 of users.
10682 </DD>
10683 <DT>#ftp/</DT>
10684 <DD>This specifies a folder area that is the same as that it may have
10685 exported via the "File Transfer Protocol".
10686 </DD>
10687 <DT>#mh/</DT>
10688 <DD>This specifies the personal folder area associated with folders
10689 and directories that were created using the MH message handling system.
10690 </DD>
10691 <DT>#move/</DT>
10692 <DD>This namespace is interpreted locally by Alpine. It has an unusual interpretation and format.
10693 <P>
10694 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
10695 <P>
10696 The #move namespace is followed by two folder names separated by a delimiter
10697 character.
10698 The delimiter character may be any character that does not appear in
10699 the MailDropFolder name.
10700 The meaning of #move is that mail will be copied from the MailDropFolder to
10701 the DestinationFolder and then deleted (if possible) from the MailDropFolder.
10702 Periodic checks at frequency
10703 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A>, but with a minimum
10704 time between checks set by
10705 <A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>,
10706 are made for new mail arriving in the MailDropFolder.
10707 An example that copies mail from a POP inbox to a local folder follows
10708 <P>
10709 <CENTER><SAMP>#move+{popserver.example.com/pop3/ssl}inbox+local folder</SAMP></CENTER>
10710 <P>
10711 To you it appears that mail is being delivered to the local folder when it
10712 is copied from the MailDropFolder, and you read mail from the local folder.
10713 <P>
10714 Note that if the DestinationFolder does not exist then the messages are not
10715 copied from the MailDropFolder.
10716 A #move folder may only be used as an
10717 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
10718 an Inbox.
10719 When you are in the FOLDER LIST of Incoming Message Folders (after turning
10720 on the
10721 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
10722 option)
10723 the Add command has a subcommand "Use Mail Drop"
10724 which may be helpful for defining the folder in your Alpine configuration.
10725 The same is true when you edit the
10726 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
10727 option in Setup/Config.
10728 Each of these configuration methods will also create the DestinationFolder
10729 if it doesn't already exist.
10730 If you are having problems, make sure the DestinationFolder exists.
10731 You may find some more useful information about Mail Drops at
10732 <A HREF="h_maildrop">What is a Mail Drop?</A>.
10733 </DD>
10734 </DL>
10735 <P>
10737 In addition, the server may support access to other user's folders,
10738 provided you have suitable permissions. Common methods use a prefix
10739 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
10740 indicate the root of the other user's folder area.
10742 <P>
10743 No, nothing's simple.
10745 <P>
10746 <End of help on this topic>
10747 </BODY>
10748 </HTML>
10749 ============= h_whatis_vcard ========================
10750 <HTML>
10751 <HEAD>
10752 <TITLE>VCARD EXPLAINED</TITLE>
10753 </HEAD>
10754 <BODY>
10755 <H1>What is the vCard format?</H1>
10756 A "vCard" is a sort of electronic business card, for exchanging
10757 information about and among people and organizations electronically.
10758 More information about vCard can be found (as of May 1998) on the WWW site
10759 of the Internet Mail Consortium at the URL:
10760 <P>
10761 <CENTER><A HREF="http://www.imc.org/pdi/">http://www.imc.org/pdi/</A></CENTER>
10762 <P>
10763 <End of help on this topic>
10764 </BODY>
10765 </HTML>
10766 ===== h_folder_open =====
10767 <HTML>
10768 <HEAD>
10769 <TITLE>Explanation of Folder Selection</TITLE>
10770 </HEAD>
10771 <BODY>
10772 <BR>
10773 <BR>
10774 This screen is designed to allow you to quickly and easily survey your
10775 folders and select one to open.
10776 <!--chtml if pinemode="function_key"-->
10777 <PRE>
10778 Navigating the List of Folders General Alpine Commands
10779 ------------------------------ -----------------------
10780 P Move to previous folder ? Show this help text
10781 N Move to next folder
10782 - Show previous screen of folders
10783 Spc (space bar) Show next screen
10784 W WhereIs (search folder names)
10786 Folder Selection Commands
10787 -------------------------
10788 E Exit the Folder Select menu (without selecting a folder)
10789 S Select the currently highlighted folder
10790 </PRE>
10791 <!--chtml else-->
10792 <PRE>
10793 Navigating the List of Folders General Alpine Commands
10794 ------------------------------ -----------------------
10795 F5 Move to previous folder F1 Show this help text
10796 F6 Move to next folder
10797 F7 Show previous screen of folders
10798 F8 Show next screen of folders
10799 F12 WhereIs (search folder names)
10801 Folder Selection Commands
10802 -------------------------
10803 F3 Exit the Folder Select menu (without selecting a folder)
10804 F4 Select the currently highlighted folder
10805 </PRE>
10806 <!--chtml endif-->
10807 <P>
10808 FOR MORE INFORMATION: See the section on
10809 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
10810 <P>
10811 <End of help on this topic>
10812 </BODY>
10813 </HTML>
10814 ===== h_folder_subscribe =====
10815 <HTML>
10816 <HEAD>
10817 <TITLE>Newsgroup Subcribe Screen explained</TITLE>
10818 </HEAD>
10819 <BODY>
10820 <H1>FOLDER SUBSCRIBE HELP</H1>
10822 This screen is designed to help you subscribe to newsgroups you are
10823 not currently subscribed to. The screen display is a list of all
10824 available newsgroups (or possibly a partial list if you specified a
10825 partial name when entering the screen). Groups you have already
10826 subscribed to have the letters "SUB" next to them. You may
10827 select a single new group to subscribe to by moving the cursor to that
10828 group and pressing "S" or carriage return. Alternatively,
10829 you may change into ListMode with the "ListMode" command.
10830 The display will change slightly so that each group has a checkbox in
10831 front of it. Use the cursor and the Set/Unset command to place an
10832 "X" in front of each newsgroup you wish to subscribe to.
10833 <P>
10835 When you are finished marking groups, the "Subscribe"
10836 command will subscribe you to those groups you have marked. Note, you
10837 may not unsubscribe to groups with this command. Instead of the
10838 "A" "Subscribe" command, use the "D"
10839 UnSbscrbe command.
10840 <P>
10842 <!--chtml if pinemode="function_key"-->
10843 <PRE>
10844 Navigating the List of Newsgroups General Alpine Commands
10845 --------------------------------- -----------------------
10846 F5 Move to previous group F1 Show this help text
10847 F6 Move to next group
10848 F7 Show previous screen of groups
10849 F8 Show next screen of groups
10850 F12 WhereIs (search group names)
10851 F9 Use ListMode
10853 Group Selection Commands
10854 -------------------------
10855 F3 Exit the News Subscribe menu (without selecting any groups)
10856 F4 Subscribe to the currently highlighted newsgroup
10857 </PRE>
10858 <!--chtml else-->
10859 <PRE>
10860 Navigating the List of Newsgroups General Alpine Commands
10861 --------------------------------- -----------------------
10862 P Move to previous group ? Show this help text
10863 N Move to next group
10864 - Show previous screen of groups
10865 Spc (space bar) Show next screen
10866 W WhereIs (search group names)
10867 L Use ListMode
10869 Group Selection Commands
10870 -------------------------
10871 E Exit the News Subscribe menu (without selecting any groups)
10872 S Subscribe to the currently highlighted newsgroup
10873 </PRE>
10874 <!--chtml endif-->
10875 <P>
10876 When in ListMode, there is an additional command for marking groups to
10877 subscribe to:
10878 <P>
10879 <!--chtml if pinemode="function_key"-->
10880 <PRE>
10881 ListMode Commands
10882 -------------------------
10883 F9 Set or unset the highlighted group
10884 </PRE>
10885 <!--chtml else-->
10886 <PRE>
10887 ListMode Commands
10888 -------------------------
10889 X Set or unset the highlighted group
10890 </PRE>
10891 <!--chtml endif-->
10892 <P>
10893 <End of help on this topic>
10894 </BODY>
10895 </HTML>
10896 ===== h_folder_postnews =====
10897 <HTML>
10898 <HEAD>
10899 <TITLE>Newsgroup selecting for Posting explained</TITLE>
10900 </HEAD>
10901 <BODY>
10902 This screen is designed to allow you to quickly and easily survey
10903 the available newsgroups and select one to post news to.
10904 <P>
10905 <!--chtml if pinemode="function_key"-->
10906 <PRE>
10907 Navigating the List of Newsgroups General Alpine Commands
10908 --------------------------------- -----------------------
10909 F5 Move to previous group F1 Show this help text
10910 F6 Move to next group
10911 F7 Show previous screen of groups
10912 F8 Show next screen of groups
10913 F12 WhereIs (search group names)
10915 Group Selection Commands
10916 -------------------------
10917 F3 Exit the Selection menu (without selecting a group)
10918 F4 Select the currently highlighted newsgroup
10919 </PRE>
10920 <!--chtml else-->
10921 <PRE>
10922 Navigating the List of Newsgroups General Alpine Commands
10923 --------------------------------- -----------------------
10924 P Move to previous group ? Show this help text
10925 N Move to next group
10926 - Show previous screen of groups
10927 Spc (space bar) Show next screen of groups
10928 W WhereIs (search group names)
10930 Group Selection Commands
10931 -------------------------
10932 E Exit the Selection menu (without selecting a group)
10933 S Select the currently highlighted newsgroup
10934 </PRE>
10935 <!--chtml endif-->
10936 <P>
10937 <End of help on this topic>
10938 </BODY>
10939 </HTML>
10940 ===== h_folder_save =====
10941 <HTML>
10942 <HEAD>
10943 <TITLE>Folder Select for Save Explained</TITLE>
10944 </HEAD>
10945 <BODY>
10946 This screen is designed to allow you to quickly and easily survey your
10947 folders and select one to use for saving the current message.
10948 <P>
10950 <!--chtml if pinemode="function_key"-->
10951 <PRE>
10952 Navigating the List of Folders General Alpine Commands
10953 ------------------------------ -----------------------
10954 F5 Move to previous folder F1 Show this help text
10955 F6 Move to next folder
10956 F7 Show previous screen of folders
10957 F8 Show next screen of folders
10958 F12 WhereIs (search folder names)
10960 Folder Selection Commands
10961 -------------------------
10962 F3 Exit the Folder Select menu (without selecting a folder)
10963 F4 Select the currently highlighted folder
10964 F11 AddNew folder (just like Select, but you type in a new folder name)
10965 </PRE>
10966 <!--chtml else-->
10967 <PRE>
10968 Navigating the List of Folders General Alpine Commands
10969 ------------------------------ -----------------------
10970 P Move to previous folder ? Show this help text
10971 N Move to next folder
10972 - Show previous screen of folders
10973 Spc (space bar) Show next screen of folders
10974 W WhereIs (search folder names)
10976 Folder Selection Commands
10977 -------------------------
10978 E Exit the Folder Select menu (without selecting a folder)
10979 S Select the currently highlighted folder
10980 A AddNew folder (just like Select, but you type in a new folder name)
10981 </PRE>
10982 <!--chtml endif-->
10983 <P>
10984 FOR MORE INFORMATION: See the section on
10985 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
10986 <P>
10987 <End of help on this topic>
10988 </BODY>
10989 </HTML>
10990 ===== h_folder_fcc =====
10991 <HTML>
10992 <HEAD>
10993 <TITLE>Folder Select for Fcc Explained</TITLE>
10994 </HEAD>
10995 <BODY>
10996 This screen is designed to allow you to quickly and easily survey your
10997 folders and select one to use as the file carbon copy (fcc) for the
10998 current message.
10999 <P>
11001 <!--chtml if pinemode="function_key"-->
11002 <PRE>
11003 Navigating the List of Folders General Alpine Commands
11004 ------------------------------ -----------------------
11005 F5 Move to previous folder F1 Show this help text
11006 F6 Move to next folder
11007 F7 Show previous screen of folders
11008 F8 Show next screen of folders
11009 F12 WhereIs (search folder names)
11011 Folder Selection Commands
11012 -------------------------
11013 F3 Exit the Folder Select menu (without selecting a folder)
11014 F4 Select the currently highlighted folder
11015 F11 AddNew folder (just like Select, but you type in a new folder name)
11016 </PRE>
11017 <!--chtml else-->
11018 <PRE>
11019 Navigating the List of Folders General Alpine Commands
11020 ------------------------------ -----------------------
11021 P Move to previous folder ? Show this help text
11022 N Move to next folder
11023 - Show previous screen of folders
11024 Spc (space bar) Show next screen of folders
11025 W WhereIs (search folder names)
11027 Folder Selection Commands
11028 -------------------------
11029 E Exit the Folder Select menu (without selecting a folder)
11030 S Select the currently highlighted folder
11031 A AddNew folder (just like Select, but you type in a new folder name)
11032 </PRE>
11033 <!--chtml endif-->
11034 <P>
11035 FOR MORE INFORMATION: See the section on
11036 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11037 <P>
11038 <End of help on this topic>
11039 </BODY>
11040 </HTML>
11041 ===== h_folder_pattern_roles =====
11042 <HTML>
11043 <HEAD>
11044 <TITLE>Folder Select for Current Folder Explained</TITLE>
11045 </HEAD>
11046 <BODY>
11047 This screen is designed to allow you to quickly and easily survey your
11048 folders and select one to use as the specific Current Folder
11049 in a Pattern.
11050 <P>
11052 <!--chtml if pinemode="function_key"-->
11053 <PRE>
11054 Navigating the List of Folders General Alpine Commands
11055 ------------------------------ -----------------------
11056 F5 Move to previous folder F1 Show this help text
11057 F6 Move to next folder
11058 F7 Show previous screen of folders
11059 F8 Show next screen of folders
11060 F12 WhereIs (search folder names)
11062 Folder Selection Commands
11063 -------------------------
11064 F3 Exit the Folder Select menu (without selecting a folder)
11065 F4 Select the currently highlighted folder
11066 F11 AddNew folder (just like Select, but you type in a new folder name)
11067 </PRE>
11068 <!--chtml else-->
11069 <PRE>
11070 Navigating the List of Folders General Alpine Commands
11071 ------------------------------ -----------------------
11072 P Move to previous folder ? Show this help text
11073 N Move to next folder
11074 - Show previous screen of folders
11075 Spc (space bar) Show next screen of folders
11076 W WhereIs (search folder names)
11078 Folder Selection Commands
11079 -------------------------
11080 E Exit the Folder Select menu (without selecting a folder)
11081 S Select the currently highlighted folder
11082 A AddNew folder (just like Select, but you type in a new folder name)
11083 </PRE>
11084 <!--chtml endif-->
11085 <P>
11086 FOR MORE INFORMATION: See the section on
11087 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11088 <P>
11089 <End of help on this topic>
11090 </BODY>
11091 </HTML>
11092 ===== h_folder_stayopen_folders =====
11093 <HTML>
11094 <HEAD>
11095 <TITLE>Folder Select Explained</TITLE>
11096 </HEAD>
11097 <BODY>
11098 This screen is designed to allow you to quickly and easily survey your
11099 folders and select one to use as a Stay-Open folder.
11100 <P>
11102 <!--chtml if pinemode="function_key"-->
11103 <PRE>
11104 Navigating the List of Folders General Alpine Commands
11105 ------------------------------ -----------------------
11106 F5 Move to previous folder F1 Show this help text
11107 F6 Move to next folder
11108 F7 Show previous screen of folders
11109 F8 Show next screen of folders
11110 F12 WhereIs (search folder names)
11112 Folder Selection Commands
11113 -------------------------
11114 F3 Exit the Folder Select menu (without selecting a folder)
11115 F4 Select the currently highlighted folder
11116 F11 AddNew folder (just like Select, but you type in a new folder name)
11117 </PRE>
11118 <!--chtml else-->
11119 <PRE>
11120 Navigating the List of Folders General Alpine Commands
11121 ------------------------------ -----------------------
11122 P Move to previous folder ? Show this help text
11123 N Move to next folder
11124 - Show previous screen of folders
11125 Spc (space bar) Show next screen of folders
11126 W WhereIs (search folder names)
11128 Folder Selection Commands
11129 -------------------------
11130 E Exit the Folder Select menu (without selecting a folder)
11131 S Select the currently highlighted folder
11132 A AddNew folder (just like Select, but you type in a new folder name)
11133 </PRE>
11134 <!--chtml endif-->
11135 <P>
11136 FOR MORE INFORMATION: See the section on
11137 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11138 <P>
11139 <End of help on this topic>
11140 </BODY>
11141 </HTML>
11142 ===== h_folder_action_roles =====
11143 <HTML>
11144 <HEAD>
11145 <TITLE>Folder Select Explained</TITLE>
11146 </HEAD>
11147 <BODY>
11148 This screen is designed to allow you to quickly and easily survey your
11149 folders and select one to use as the folder into which messages
11150 matching this filter will be moved.
11151 <P>
11153 <!--chtml if pinemode="function_key"-->
11154 <PRE>
11155 Navigating the List of Folders General Alpine Commands
11156 ------------------------------ -----------------------
11157 F5 Move to previous folder F1 Show this help text
11158 F6 Move to next folder
11159 F7 Show previous screen of folders
11160 F8 Show next screen of folders
11161 F12 WhereIs (search folder names)
11163 Folder Selection Commands
11164 -------------------------
11165 F3 Exit the Folder Select menu (without selecting a folder)
11166 F4 Select the currently highlighted folder
11167 F11 AddNew folder (just like Select, but you type in a new folder name)
11168 </PRE>
11169 <!--chtml else-->
11170 <PRE>
11171 Navigating the List of Folders General Alpine Commands
11172 ------------------------------ -----------------------
11173 P Move to previous folder ? Show this help text
11174 N Move to next folder
11175 - Show previous screen of folders
11176 Spc (space bar) Show next screen of folders
11177 W WhereIs (search folder names)
11179 Folder Selection Commands
11180 -------------------------
11181 E Exit the Folder Select menu (without selecting a folder)
11182 S Select the currently highlighted folder
11183 A AddNew folder (just like Select, but you type in a new folder name)
11184 </PRE>
11185 <!--chtml endif-->
11186 <P>
11187 FOR MORE INFORMATION: See the section on
11188 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11189 <P>
11190 <End of help on this topic>
11191 </BODY>
11192 </HTML>
11193 ===== h_abook_config =====
11194 <HTML>
11195 <HEAD>
11196 <TITLE>SETUP ADDRESS BOOKS SCREEN</TITLE>
11197 </HEAD>
11198 <BODY>
11199 <H1>SETUP ADDRESS BOOKS SCREEN</H1>
11200 <H2>SETUP ADDRESS BOOKS COMMANDS</H2>
11201 <!--chtml if pinemode="function_key"-->
11202 <PRE>
11203 Available Commands
11204 -------------------------------
11205 F1 Show Help Text
11206 F3 Back to MAIN Alpine menu
11207 F4 Change configuration for address book
11208 F5 Move to previous address book
11209 F6 Move to next address book
11210 F7 Previous page of address books
11211 F8 Next page of address books
11212 F9 Add new address book
11213 F10 Delete existing address book
11214 F11 Shuffle the order of address books
11215 F12 Whereis (search address book titles)
11216 </PRE>
11217 <!--chtml else-->
11218 <PRE>
11219 Navigation General Alpine Commands
11220 ----------------------- -----------------------
11221 P Prev Address Book ? Display this help text
11222 N Next Address Book E Back to MAIN Alpine menu
11223 - Previous page
11224 Spc (space bar) Next page
11225 W WhereIs (search for word in address book titles)
11227 Setup Address Books Commands
11228 ------------------------------------------------
11229 A Add new address book $ Shuffle the order of address books
11230 D Delete existing address book C Change configuration for address book
11231 </PRE>
11232 <!--chtml endif-->
11234 <H2>Description of the Setup Address Books Screen</H2>
11236 This screen lets you add, delete, modify, or change the order of your
11237 address books. The "Add Abook" command brings up a blank form to
11238 fill in. If you are adding a remote address book on an IMAP server
11239 you should fill in the name of the IMAP server. Otherwise, leave
11240 that field blank. (Note that remote IMAP address books are an Alpine
11241 concept and are unlikely to interoperate with other mail clients.)
11242 For a remote address book, fill in the name of the remote folder
11243 in the Folder field. This should be a folder that is used only for
11244 this one purpose, not a general purpose folder you expect to store
11245 messages in.
11246 <P>If you are adding a local address book, fill in the
11247 Folder Name field with a local file name (e.g., .addressbook).
11248 <P>
11249 <B>Please note:</B> Remote address books stored on an IMAP server are
11250 of an entirely different format (namely, a special-purpose
11251 "mail folder") than that of the local addressbook familiar
11252 to Alpine users. Therefore,
11253 you cannot use "add a remote address book" to make an existing
11254 Alpine .addressbook file you may have on a remote IMAP server accessible to
11255 Alpine running on a different host.
11256 <P>
11258 The "Del Abook" command allows you to remove an address book
11259 from your configuration. It will also ask you if you wish to remove
11260 the data for that address book, which would erase all traces of the
11261 address book if you answer Yes.
11262 <P>
11264 The "Change" command is similar to the "Add Abook" command.
11265 The difference is that instead of adding a new address book to your
11266 configuration, you are changing the configuration of an existing entry.
11267 For example, you might want to correct a typing error or change a
11268 nickname. The "Change" command is not a move command. If you
11269 change the folder name or server name the data will not be moved for you.
11270 <P>
11272 The "Shuffle" command is used for two purposes. If you shuffle
11273 an address book toward another address book in the same group then
11274 the order of those two address books will be swapped. If you shuffle
11275 the last Personal address book down towards the Global address book
11276 section, it will become a Global address book. If you shuffle
11277 the first Global address book up it will become a Personal address
11278 book. The main difference between Personal and Global address
11279 books is that Global address books are forced read-only.
11280 <P><UL>
11281 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11282 </UL>
11283 <P>
11284 <End of help on this topic>
11285 </BODY>
11286 </HTML>
11287 ===== h_abook_top =====
11288 <HTML>
11289 <HEAD>
11290 <TITLE>ADDRESS BOOK LIST COMMANDS</TITLE>
11291 </HEAD>
11292 <BODY>
11293 <H1>ADDRESS BOOK LIST COMMANDS</H1>
11294 <!--chtml if pinemode="function_key"-->
11295 <PRE>
11296 Available Commands -- Group 1 Available Commands -- Group 2
11297 ------------------------------- ------------------------------
11298 F1 Show Help Text F1 Show Help Text
11299 F2 See commands in next group F2 See commands in next group
11300 F3 Exit to MAIN MENU F3 Quit Alpine
11301 F4 View/Edit selected address book
11302 F5 Move to previous address book F5 FOLDER LIST screen
11303 F6 Move to next address book F6 Specify a folder to go to
11304 F7 Previous page F7 MESSAGE INDEX screen
11305 F8 Next page F9 Print list of address books
11306 F12 Whereis (search for word)
11307 </PRE>
11308 <!--chtml else-->
11309 <PRE>
11310 Navigation General Alpine Commands
11311 ----------------------- -----------------------
11312 P Previous Entry ? Display this help text
11313 N Next Entry O Show all other available commands
11314 - Previous page < Back to MAIN Alpine menu
11315 Spc (space bar) Next page Q Quit Alpine
11316 W WhereIs (search for word) L FOLDER LIST screen
11317 G Specify a folder to go to
11318 Address Book Commands I MESSAGE INDEX screen
11319 ------------------------------------------------
11320 > View/Edit selected address book
11321 or
11322 > Search on selected directory server
11324 % Print list of address books and directory servers
11325 </PRE>
11326 <!--chtml endif-->
11328 <H2>Description of the Address Book List Screen</H2>
11330 From this screen you may choose which address book you wish to view
11331 or edit. For more information on address books, view one of your
11332 address books (with
11333 <!--chtml if pinemode="function_key"-->
11334 F4
11335 <!--chtml else-->
11336 ">"
11337 <!--chtml endif-->)
11338 and see the Help Text there.<P>
11340 You may also choose a directory server on which to search for entries.
11341 You do that by highlighting the directory server line and using
11342 <!--chtml if pinemode="function_key"-->
11343 F4
11344 <!--chtml else-->
11345 ">"
11346 <!--chtml endif-->.<P>
11348 If you wish to define new address books or directory servers go to the Main
11349 menu and choose Setup. You may then either choose to setup AddressBooks or
11350 Directory (among other things). It's possible that the Directory option
11351 will not be there if the Alpine you are using does not contain LDAP directory
11352 lookup functionality.
11354 <P><UL>
11355 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11356 </UL><P>
11357 <End of help on this topic>
11358 </BODY>
11359 </HTML>
11360 ===== h_abook_opened =====
11361 <HTML>
11362 <HEAD>
11363 <TITLE>THE ALPINE ADDRESS BOOK</TITLE>
11364 </HEAD>
11365 <BODY>
11366 <H1>THE ALPINE ADDRESS BOOK</H1>
11367 <H2>ADDRESS BOOK COMMANDS</H2>
11368 <PRE>
11369 <!--chtml if pinemode="function_key"-->
11370 Available Commands -- Group 1 Available Commands -- Group 2
11371 ------------------------------- ------------------------------
11372 F1 Show Help Text F1 Show Help Text
11373 F2 See commands in next group F2 See commands in next group
11374 F3 Exit this screen F3 Quit Alpine
11375 F4 View/Edit selected entry F4 Go to MAIN MENU screen
11376 F5 Move to previous entry F5 FOLDER LIST screen
11377 F6 Move to next entry F6 Specify a folder to go to
11378 F7 Previous page of address book F7 MESSAGE INDEX screen
11379 F8 Next page of address book F8 Compose to entry using roles
11380 F9 Add new entry to address book F9 Print address book
11381 F10 Delete selected entry F10 TakeAddr to another addrbook
11382 F11 Compose to selected entry F11 Save or Export addrbook selections
11383 F12 Whereis (search address book) F12 Forward entry by mail
11385 Available Commands -- Group 3
11386 ------------------------------
11387 F3 Select F6 Zoom (or unZoom)
11388 F5 Select Current F7 Apply Command to Selection
11389 <!--chtml else-->
11390 Address Book Navigation General Alpine Commands
11391 ----------------------- -----------------------
11392 P Prev Address ? Display this help text
11393 N Next Address O Show all other available commands
11394 - Previous page of address book M Back to MAIN MENU
11395 Spc (space bar) Next page Q Quit Alpine
11396 W WhereIs (search for word C Compose message to selected addr
11397 or name in address book) # Compose to addr using roles
11398 < To List of Address Books if L FOLDER LIST screen
11399 more than one, else to MAIN G Specify a folder to go to
11400 I MESSAGE INDEX screen
11402 Address Book Commands
11403 ----------------------------------------------------
11404 > View/Update selected entry D Delete selected entries
11405 % Print address book S Save or Export address book selections
11406 F Forward entries by mail @ Add new entry to address book
11408 ; Select command Z Toggle Zoom Mode
11409 : Select highlighted entry A Apply command to selected entries
11411 <!--chtml endif-->
11412 </PRE>
11413 Note: The presence or absence of the final four commands above is
11414 controlled by the option
11415 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>.
11416 <P>
11418 <H2>Description of the Address Book Screen</H2>
11420 This screen lets you edit and manage entries in your address book. It
11421 also acts as a short-cut for composing messages to people in the address
11422 book. When, from this screen, you press <!--chtml if pinemode="function_key"-->F11<!--chtml else-->"C"<!--chtml endif--> for ComposeTo, the
11423 message starts "pre-addressed" to whatever address book entry is
11424 currently selected. If you use the <!--chtml if pinemode="function_key"-->F8<!--chtml else-->"#"<!--chtml endif--> for Role, you may first select a
11425 role to use in your composition.
11426 <P>
11427 Alpine's address book helps you keep a list of addresses you send email to so
11428 you do not have to remember addresses that are often complex. Each entry
11429 in the address book has five fields, all of them optional. The three
11430 elements that are usually visible on the ADDRESS BOOK display, are: <DL>
11432 <P><DT>NICKNAME: <DD>A short easy-to-remember label to identify the entry.
11433 This is what you type in as you are addressing the message in the
11434 composer. If there is a matching entry in your address book(s),
11435 Alpine will extract the corresponding FullName and Address fields to
11436 generate the actual address for your message.
11438 <P><DT>FULLNAME: <DD>A longer field where you can put the full name
11439 of the
11440 person or organization. Usually the full names are put in last
11441 name first so they sort nicely in alphabetical order. Whatever
11442 you put as the name here will appear on the message when it is
11443 finally delivered. Examples:<PRE>
11444 Garcia Marquez, Gabriel
11445 Henscheid, Eckhard
11446 Alpine-Info mailing list
11447 Library materials renewal requests
11448 Kim An-guk
11449 "George III, King of Great Britain, 1738-1820"
11450 </PRE>
11451 (In the second-to-last example, no comma is used in the name so that
11452 the family name appears first in the address book and when the entry is
11453 used in the composer.
11454 In the last example, retaining the commas is intended;
11455 double-quotation marks surround the name to
11456 prevent the transposition of its parts when the entry is used in
11457 the composer.)
11459 <P><DT>ADDRESS: <DD>This is the actual email address itself. This must be
11460 a valid Internet address that conforms to the Internet message
11461 header standard, RFC-822. (See also <A HREF="h_address_format">Explanation of Address formats</A>.)</DL>
11463 The two fields that aren't usually visible are:<DL>
11465 <P><DT>FCC: <DD>The name of the folder you would like a copy of any outgoing
11466 message to this address to be saved in. If this field is set, and
11467 this address is the first one in the message's To: header, then
11468 Alpine will use this folder name for the FCC in lieu of the normal
11469 FCC folder name.
11471 <P><DT>COMMENTS: <DD>This field contains arbitrary text for your convenience.
11472 </DL>
11473 <P>
11474 Due to screen width limitations, these last two fields do not show up in
11475 the normal ADDRESS BOOK display. You may select the
11476 "View/Update" command to
11477 view or modify them. You may use the configuration variable
11478 <A HREF="h_config_abook_formats">"<!--#echo var="VAR_addressbook-formats"-->"</A>
11479 to add these fields to your ADDRESS BOOK
11480 display, or to modify the format of the display.
11482 <H2>Sorting the Address book</H2>
11484 By default, address book entries are sorted alphabetically on the full
11485 name with distribution lists sorted to the end. Sorting can be changed by
11486 resetting the address book sort rule in the Alpine SETUP CONFIGURATION screen
11487 --assuming you have "write" permission for the address book file.
11488 <P>
11489 Unlike the sorting of folders (which only changes presentation), sorting an
11490 address book actually changes the file as it is kept on the computer. For
11491 this reason you won't be able to sort a shared or system-wide address
11492 book.
11494 <H2>Adding New Entries</H2>
11496 The easiest way to add new entries to your address book is to use the
11497 "TakeAddr" command when viewing a message.
11498 This command allows you to take addresses from the header and body of the
11499 message and put them into your address book, without having to type
11500 them in.
11501 <P>
11503 To manually add a new entry from within the address book screen, use the AddNew
11504 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->"@"<!--chtml endif-->) command.
11505 Use this command both for adding a simple alias and for adding a
11506 distribution list.
11508 <H2>Distribution Lists</H2>
11510 Address book entries can be simple cases of aliases (a single nickname is linked
11511 to a single email address) or distribution lists (a single nickname
11512 pointing at more than one email address). Each distribution list has a
11513 nickname, a full name and a list of addresses. The addresses may be
11514 actual addresses or they may be other nicknames in your address book.
11515 They may even refer to other distribution lists.
11516 There's really no difference between a simple alias and a distribution list,
11517 other than the number of addresses.
11518 Therefore, you can turn a simple alias with one address into a distribution
11519 list simply by adding more addresses.
11520 To add entries to an existing list or alias
11521 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
11522 a single address from the list if the cursor is placed on the address;
11523 it will delete the entire distribution list if the cursor is on the
11524 nickname/fullname line. View/Update may also be used to delete addresses
11525 from a list.
11526 <P>
11527 Address field entries in distribution lists may take any one of three
11528 forms: a nickname existing in any of the defined address books, a normal
11529 address of the form "jsmith@art.example.com", or a complete
11530 fullname/address combination, e.g. "John Smith
11531 <jsmith@art.example.com>".
11532 <P>
11533 Distribution lists in Alpine address books can only be used by the person or
11534 people who have access to that address book. They are not usually used to
11535 implement discussion groups, but can be used to facilitate small
11536 discussion groups if all the participants have access to the same shared
11537 address book.
11539 <H2>FCC and Comments</H2>
11541 As mentioned above, each entry in the address book also has two other optional
11542 fields, Fcc and Comments. The command to look at or change either of these
11543 is the same View/Update command used for all of the fields (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->">"<!--chtml endif-->). The
11544 Comments field is just for your own use. The Fcc field overrides the
11545 default Fcc if this address is the first one on the To line. The WhereIs
11546 command may be used to search for particular strings in the address book,
11547 including fields that are not visible (like Comment and Fcc by default).
11549 <H2>Aggregate Operations</H2>
11551 If the feature
11552 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
11553 is turned on (the default), then the four commands "Select",
11554 "Select Current", "Zoom", and "Apply"
11555 are available. The two selection commands allow you to mark a set of
11556 address book entries as being selected. If you have more than one address
11557 book, the selections may be in more than one of those address books.
11558 The "Zoom" command will toggle between displaying only the selected
11559 entries and all of the entries. The "Apply" command allows you to
11560 apply one of the regular address book commands to all of the selected
11561 entries. Usually the address book commands apply to only the entry
11562 highlighted by the cursor. The "Apply" command works with the
11563 commands "ComposeTo", "Delete", "Print",
11564 "Save", "Forward", and "Role".
11566 <H2>Exporting and Forwarding Address book entries</H2>
11568 Under the save option, when you use the Export (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->"X"<!--chtml endif-->) command, the currently highlighted
11569 address book entry is placed in a plain text file in your home directory
11570 <!--chtml if pinemode="running"-->
11571 (which, in the present configuration of your system, is
11572 "<!--#echo var="HOME_DIR"-->")
11573 <!--chtml endif-->
11574 or current working directory
11575 <!--chtml if pinemode="running"-->
11576 (which, at least for your current Alpine "session,"
11577 is "<!--#echo var="CURRENT_DIR"-->")
11578 <!--chtml endif-->, depending on the
11579 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
11580 configuration setting. If you have some entries selected and use the
11581 Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Export command, all of the selected addresses will be
11582 placed in the text file.
11583 <P>
11584 When you use the Forward (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->"F"<!--chtml endif-->) command, the currently highlighted
11585 address book entry is placed in a special attachment and you are put into
11586 the composer. You can fill in some comments in the body of the message,
11587 if you'd like, and send it to somebody else who uses Alpine. The recipient
11588 may use the TakeAddr command on that message to insert the address book
11589 entry you sent in their own address book. If you have some entries
11590 selected and use the Apply Forward command all of the selected entries
11591 will be forwarded in a single message. You may
11592 use Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Forward to forward a copy of an entire address book.
11593 The recipient must be using Alpine in order to receive this correctly.
11594 One way for the recipient to handle this might be to create an empty
11595 address book and then "Take" your forwarded address book entries into
11596 that empty address book.
11598 <H2>Multiple and/or Site-Wide Address books</H2>
11600 You may have more than one personal address book. In addition, there may
11601 be one or more global address books. This capability allows you to have
11602 multiple personal address books (some of which may be shared) and it also
11603 allows system administrators to implement site-wide address books that
11604 contain entries for users on multiple machines within the organization.
11605 <P><DL>
11606 <DT>Searching
11607 <DD> If you enter a nickname when composing a message, your
11608 personal address books will be searched through in order, and then the
11609 global address book(s) searched. If more than one address book has an entry
11610 for the nickname, Alpine uses the first one that it finds, so an entry in
11611 your personal address book would override a global address book entry. If
11612 after searching all the address books there is still no match, (Unix) Alpine
11613 then searches the local host password file on the assumption that you have
11614 entered a local user name rather than an address book nickname.
11615 You may change the search order of your address books with the <!--chtml if pinemode="function_key"-->F3<!--chtml else-->$<!--chtml endif--> Shuffle
11616 command, but global address books are always searched after personal
11617 address books.
11619 <P><DT>Tab completion
11620 <DD> If the
11621 <A HREF="h_config_enable_tab_complete"><!--#echo var="FEAT_enable-tab-completion"--></A>
11622 feature is turned on (the default) then the Tab key may be used
11623 in the composer to complete partially typed nicknames in the To
11624 or Cc lines. You type the first few letters of a nickname and then
11625 press the Tab key. It there is only one nickname that matches it will
11626 be filled in by Alpine. If there is more than one the unambiguous part
11627 of the nicknames will be filled in. For example, if your address book or
11628 books contains only the two entries "barley" and "barbecue"
11629 beginning with the letters "ba", then if you type "ba"
11630 followed by a Tab character Alpine will fill in "bar" and stop.
11631 If you then type a second Tab character you will be presented with a list
11632 of matching nicknames to select from. Alternatively, you could type another
11633 "b" resulting in "barb" and then a Tab would fill
11634 in the entire "barbecue" entry.
11636 <P><DT>Defining
11637 <DD> You define multiple personal address books in the
11638 <A HREF="h_abook_config">SETUP AddressBooks</A> screen, which you may reach
11639 from the MAIN MENU.
11640 You may add as many as you like. Global address books are usually
11641 site-wide address books defined by the System administrator, but
11642 you may define global address books of your own just like you define
11643 personal address books.
11645 <P><DT>Creating and updating
11646 <DD> Personal address books are normally created empty
11647 and populated by explicit additions from within Alpine, e.g. via the
11648 TakeAddr command. Unlike personal address books, global address books may
11649 not be modified/updated from within Alpine; that is, they are Read-Only.
11650 Thus, global address books are created, populated and updated outside of
11651 Alpine. They might be hand-edited, generated by a program from another
11652 database, or by copying an existing address book. They might also be
11653 some other user's personal address book, and so be modified normally by
11654 that user but accessed Read-Only by you. See the Alpine Technical
11655 Notes document (included in the Alpine distribution) for more information on
11656 this.
11658 <P><DT>Accessing
11659 <DD>There are two different types of address books in Alpine.
11660 A local address book is stored in a regular file and the normal file
11661 access permissions apply. A remote address book is stored on an IMAP
11662 server in a special folder that contains only messages pertaining to
11663 that address book. The last message in the remote folder contains a
11664 copy of the address book data, and that data is copied to a local cache
11665 file in your home directory. From there it is accessed just like a local
11666 address book. The name of the cache file is kept track of in a special
11667 file called the
11668 <A HREF="h_config_abook_metafile"><!--#echo var="VAR_remote-abook-metafile"--></A>,
11669 the name of which is stored in
11670 your Alpine configuration file the first time you use a remote address book.
11671 Just as local Alpine address books use a format that only Alpine understands,
11672 remote Alpine address books do the same and other mail reading programs
11673 are unlikely to be able to understand them.<P>
11674 While global address books are explicitly intended to be shared, there is
11675 nothing to prevent you from sharing a personal address book with other
11676 Alpine users. This might be useful in the case of a small workgroup.
11677 However, it is recommended that updates to shared personal address books
11678 be done when other Alpine users are not accessing the address book. Alpine
11679 does not do any file-locking to manage concurrent updates to the
11680 addressbook, but it does check to see if the file has been modified before
11681 making any changes. Consequently, inadvertent concurrent updates will
11682 only cause other Alpine users to have to restart their address book
11683 operation, which will cause Alpine to reopen the updated file.
11685 <P><DT>Converting to Remote
11686 <DD>The easiest way to convert an existing local
11687 address book into a remote address book is to create an empty new remote
11688 personal address book by typing "A" to execute the
11689 "Add Pers Abook" command in the SETUP Addressbook screen.
11690 Make sure you add a <EM>personal</EM> address book, not a <EM>global</EM>
11691 address book.
11692 After you have added the empty
11693 remote address book, go into the screen for the address book you wish
11694 to copy and "Select" "All".
11695 This selects every entry in that
11696 address book. Then type the command "Apply Save".
11697 You will be asked for the address book to save to. You may use ^P and ^N
11698 to get to the new empty address book, then hit RETURN and the addresses
11699 will be copied.
11700 At this point you'll probably want to unselect all the entries in the local
11701 address book before proceeding. You do that with
11702 "Select" "unselect All".
11704 </DL>
11705 <UL>
11706 <LI><A HREF="h_address_format">Explanation of Address formats</A>
11707 </UL>
11708 <P><UL>
11709 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11710 </UL>
11711 <P>
11712 <End of help on this topic>
11713 </BODY>
11714 </HTML>
11715 ===== h_abook_select_addr =====
11716 <HTML>
11717 <HEAD>
11718 <TITLE>Addressbook Selection Explained</TITLE>
11719 </HEAD>
11720 <BODY>
11721 <H1>SELECT ADDRESS</H1>
11722 <!--chtml if pinemode="function_key"-->
11723 <PRE>
11724 Navigating the List of Messages General Alpine Commands
11725 ------------------------------- -----------------------
11726 F5 Move to previous entry F1 Show this help text
11727 F6 Move to next entry
11728 F7 Show previous screen of address book
11729 F8 Show next screen of address book
11730 F12 WhereIs (search through address book)
11732 Address Selection Commands
11733 --------------------------
11734 F3 Exit the Address Select screen (without selecting an address)
11735 F4 Select the currently highlighted entry
11736 </PRE>
11737 <!--chtml else-->
11738 <PRE>
11739 Navigating the List of Messages General Alpine Commands
11740 ------------------------------- -----------------------
11741 P Move to previous entry ? Show this help text
11742 N Move to next entry
11743 - Show previous screen of address book
11744 Spc (space bar) Show next screen of address book
11745 W WhereIs (search through address book)
11747 Address Selection Commands
11748 --------------------------
11749 E Exit the Address Select screen (without selecting an address)
11750 S Select the currently highlighted entry
11751 </PRE>
11752 <!--chtml endif-->
11753 <P>
11755 This screen is designed to let you easily scan your address book(s) in
11756 order to select an entry for the message you are composing. You cannot
11757 edit your address book in any way at this time, for address book
11758 maintenance, select the address book command when not composing a message.
11759 <P>
11761 If you are composing a message and know the nickname of the person/list you
11762 want, you can bypass this screen by simply typing in the nickname on the
11763 appropriate header line (To:, Cc:, etc.) Exiting this screen without
11764 selecting an entry does not cancel your message.
11765 <P>
11767 FOR MORE INFORMATION on addressing see
11768 <A HREF="h_address_format">Explanation of Address formats</A>, and the
11769 <A HREF="h_abook_opened">Address Book Screen's</A>
11770 help text.
11771 <P>
11772 <End of help on this topic>
11773 </BODY>
11774 </HTML>
11775 ===== h_abook_select_top =====
11776 <HTML>
11777 <HEAD>
11778 <TITLE>Addressbook Selection Navigation Explained</TITLE>
11779 </HEAD>
11780 <BODY>
11781 <H1>NAVIGATING WHILE SELECTING ADDRESSES</H1>
11782 <!--chtml if pinemode="function_key"-->
11783 <PRE>
11784 Navigating the List of Address Books General Alpine Commands
11785 ------------------------------------ -----------------------
11786 F4 View the highlighted address book
11787 F5 Move to previous address book F1 Show this help text
11788 F6 Move to next address book
11789 F7 Show previous screen of address books
11790 F8 Show next screen of address books
11791 F12 WhereIs (search through address books)
11793 Address Selection Commands
11794 --------------------------
11795 F3 Exit the Address Select screen (without selecting an address)
11796 F4 Select the currently selected entries (if using ListMode)
11797 F9 Change to ListMode
11798 </PRE>
11799 <!--chtml else-->
11800 <PRE>
11801 Navigating the List of Address Books General Alpine Commands
11802 ------------------------------------ -----------------------
11803 > View the highlighted address book
11804 P Move to previous address book ? Show this help text
11805 N Move to next address book
11806 - Show previous screen of address books
11807 Spc (space bar) Show next screen of address books
11808 W WhereIs (search through address books)
11810 Address Selection Commands
11811 --------------------------
11812 E Exit the Address Select screen (without selecting an address)
11813 S Select the currently selected entries (if using ListMode)
11814 L Change to ListMode
11815 </PRE>
11816 <!--chtml endif-->
11817 <P>
11819 This screen is designed to let you easily scan your address book(s) in
11820 order to select entries for the message you are composing. You cannot
11821 edit your address book in any way at this time. For address book
11822 maintenance, select the address book command when not composing a message.
11823 <P>
11825 If you are composing a message and know the nickname of the person/list you
11826 want, you can bypass this screen by simply typing in the nickname on the
11827 appropriate header line (To:, Cc:, etc.) Exiting this screen without
11828 selecting an entry does not cancel your message.
11829 <P>
11831 The ListMode command will add a column at the left edge of the screen.
11832 You mark the entries that you wish to select with the "X" command.
11833 This allows you to choose more than one entry at a time.
11834 <P>
11836 An alternative method of composing a message to entries in your
11837 address book(s) is to first use the "Select" command from
11838 the address book maintenance screen and then the "Apply"
11839 "ComposeTo" command to start the composer composing to the
11840 selected entries.
11841 <P>
11843 FOR MORE INFORMATION on addressing see
11844 <A HREF="h_address_format">Explanation of Address formats</A>, and the
11845 <A HREF="h_abook_opened">Address Book Screen's</A>
11846 help text.
11847 <P>
11848 <End of help on this topic>
11849 </BODY>
11850 </HTML>
11851 ===== h_abook_select_listmode =====
11852 <HTML>
11853 <HEAD>
11854 <TITLE>Address Listmode Selection from Composer Explained</TITLE>
11855 </HEAD>
11856 <BODY>
11857 <H1>COMPOSER: SELECT ADDRESSES</H1>
11858 <!--chtml if pinemode="function_key"-->
11859 <PRE>
11860 Navigating the List of Messages General Alpine Commands
11861 ------------------------------- -----------------------
11862 F5 Move to previous entry F1 Show this help text
11863 F6 Move to next entry
11864 F7 Show previous screen of address book
11865 F8 Show next screen of address book
11866 F12 WhereIs (search through address book)
11868 Address Selection Commands
11869 --------------------------
11870 F3 Exit the Address Select screen (without selecting an address)
11871 F4 Select the currently highlighted entry
11872 F9 Change to ListMode
11873 </PRE>
11874 <!--chtml else-->
11875 <PRE>
11876 Navigating the List of Messages General Alpine Commands
11877 ------------------------------- -----------------------
11878 P Move to previous entry ? Show this help text
11879 N Move to next entry
11880 - Show previous screen of address book
11881 Spc (space bar) Show next screen of address book
11882 W WhereIs (search through address book)
11884 Address Selection Commands
11885 --------------------------
11886 E Exit the Address Select screen (without selecting an address)
11887 S Select the currently highlighted entry
11888 L Change to ListMode
11889 </PRE>
11890 <!--chtml endif-->
11891 <P>
11893 This screen is designed to let you easily scan your address book(s) in
11894 order to select entries for the message you are composing. You cannot
11895 edit your address book in any way at this time, for address book
11896 maintenance, select the address book command when not composing a message.
11897 <P>
11899 If you are composing a message and know the nickname of the person/list you
11900 want, you can bypass this screen by simply typing in the nickname on the
11901 appropriate header line (To:, Cc:, etc.) Exiting this screen without
11902 selecting an entry does not cancel your message.
11903 <P>
11905 The ListMode command will add a column at the left edge of the screen.
11906 You mark the entries that you wish to select with the "X" command.
11907 This allows you to choose more than one entry at a time.
11908 <P>
11910 An alternative method of composing a message to entries in your
11911 address book(s) is to first use the "Select" command from
11912 the address book maintenance screen and then the "Apply"
11913 "ComposeTo" command to start the composer composing to the
11914 selected entries.
11915 <P>
11917 FOR MORE INFORMATION on addressing see
11918 <A HREF="h_address_format">Explanation of Address formats</A>, and the
11919 <A HREF="h_abook_opened">Address Book Screen's</A>
11920 help text.
11921 <P>
11922 <End of help on this topic>
11923 </BODY>
11924 </HTML>
11925 ===== h_abook_select_checks =====
11926 <HTML>
11927 <HEAD>
11928 <TITLE>Address Selection from Composer Explained</TITLE>
11929 </HEAD>
11930 <BODY>
11931 <H1>COMPOSER: SELECT ADDRESSES</H1>
11932 <!--chtml if pinemode="function_key"-->
11933 <PRE>
11934 Navigating the List of Messages General Alpine Commands
11935 ------------------------------- -----------------------
11936 F5 Move to previous entry F1 Show this help text
11937 F6 Move to next entry
11938 F7 Show previous screen of address book
11939 F8 Show next screen of address book
11940 F12 WhereIs (search through address book)
11942 Address Selection Commands
11943 --------------------------
11944 F3 Exit the Address Select screen (without selecting an address)
11945 F4 Select the currently highlighted entry
11946 F8 Either Sets or Unsets all entries in this address book
11947 F9 Set or Unset the highlighted entry
11948 </PRE>
11949 <!--chtml else-->
11950 <PRE>
11951 Navigating the List of Messages General Alpine Commands
11952 ------------------------------- -----------------------
11953 P Move to previous entry ? Show this help text
11954 N Move to next entry
11955 - Show previous screen of address book
11956 Spc (space bar) Show next screen of address book
11957 W WhereIs (search through address book)
11959 Address Selection Commands
11960 --------------------------
11961 E Exit the Address Select screen (without selecting an address)
11962 S Select the currently highlighted entry
11963 X Set or Unset the highlighted entry
11964 A Either Sets or Unsets all entries in this address book
11965 </PRE>
11966 <!--chtml endif-->
11967 <P>
11969 Mark the entries you wish to select with the "X Set/Unset"
11970 command. Type "S Select" to select all of the entries you
11971 have marked, just as if you had typed them in by hand.
11972 <P>
11974 An alternative method of composing a message to entries in your
11975 address book(s) is to first use the "Select" command from
11976 the address book maintenance screen and then the "Apply"
11977 "ComposeTo" command to start the composer composing to the
11978 selected entries.
11979 <P>
11981 FOR MORE INFORMATION on addressing see
11982 <A HREF="h_address_format">Explanation of Address formats</A>, and the
11983 <A HREF="h_abook_opened">Address Book Screen's</A>
11984 help text.
11985 <P>
11986 <End of help on this topic>
11987 </BODY>
11988 </HTML>
11989 ===== h_abook_select_nicks_take =====
11990 <HTML>
11991 <HEAD>
11992 <TITLE>Take Address Nickname Selection Explained</TITLE>
11993 </HEAD>
11994 <BODY>
11995 <H1>TAKEADDR: SELECT NICKNAME</H1>
11996 <!--chtml if pinemode="function_key"-->
11997 <PRE>
11998 Navigating the List of Messages General Alpine Commands
11999 ------------------------------- -----------------------
12000 F5 Move to previous entry F1 Show this help text
12001 F6 Move to next entry
12002 F7 Show previous screen of address book
12003 F8 Show next screen of address book
12004 F12 WhereIs (search through address book)
12006 Message Selection Commands
12007 --------------------------
12008 F3 Exit the Nickname Select screen (without selecting an address)
12009 F4 Select the currently highlighted entry
12010 </PRE>
12011 <!--chtml else-->
12012 <PRE>
12013 Navigating the List of Messages General Alpine Commands
12014 ------------------------------- -----------------------
12015 P Move to previous entry ? Show this help text
12016 N Move to next entry
12017 - Show previous screen of address book
12018 Spc (space bar) Show next screen of address book
12019 W WhereIs (search through address book)
12021 Message Selection Commands
12022 --------------------------
12023 E Exit the Nickname Select screen (without selecting an address)
12024 S Select the currently highlighted entry
12025 </PRE>
12026 <!--chtml endif-->
12027 <P>
12029 This screen is designed to let you modify or add to an existing
12030 address book entry. You have already selected the name(s) and
12031 address(es) through "Take Address". This screen simply lets
12032 you scan your address books and select the nickname to be
12033 changed/augmented. If you want to add a new entry, then you are in
12034 the wrong place-- Select "Exit" command.
12035 <P>
12037 FOR MORE INFORMATION on addressing see
12038 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12039 <A HREF="h_abook_opened">Address Book Screen's</A>
12040 help text.
12041 <P>
12042 <End of help on this topic>
12043 </BODY>
12044 </HTML>
12045 ===== h_abook_select_nick =====
12046 <HTML>
12047 <HEAD>
12048 <TITLE>Nickname Selection Explained</TITLE>
12049 </HEAD>
12050 <BODY>
12051 <H1>SELECT NICKNAME</H1>
12052 <!--chtml if pinemode="function_key"-->
12053 <PRE>
12054 Navigating the List of Messages General Alpine Commands
12055 ------------------------------- -----------------------
12056 F5 Move to previous entry F1 Show this help text
12057 F6 Move to next entry
12058 F7 Show previous screen of address book
12059 F8 Show next screen of address book
12060 F12 WhereIs (search through address book)
12062 Message Selection Commands
12063 --------------------------
12064 F3 Exit the Nickname Select screen (without selecting an address)
12065 F4 Select the currently highlighted entry
12066 </PRE>
12067 <!--chtml else-->
12068 <PRE>
12069 Navigating the List of Messages General Alpine Commands
12070 ------------------------------- -----------------------
12071 P Move to previous entry ? Show this help text
12072 N Move to next entry
12073 - Show previous screen of address book
12074 Spc (space bar) Show next screen of address book
12075 W WhereIs (search through address book)
12077 Message Selection Commands
12078 --------------------------
12079 E Exit the Nickname Select screen (without selecting an address)
12080 S Select the currently highlighted entry
12081 </PRE>
12082 <!--chtml endif-->
12083 <P>
12085 This screen is designed to let you look at the nicknames in your address
12086 books before choosing a new one.
12087 <P>
12089 FOR MORE INFORMATION on addressing see
12090 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12091 <A HREF="h_abook_opened">Address Book Screen's</A>
12092 help text.
12093 <P>
12094 <End of help on this topic>
12095 </BODY>
12096 </HTML>
12097 ===== h_takeaddr_screen =====
12098 <HTML>
12099 <HEAD>
12100 <TITLE>Take Address Screen Explained</TITLE>
12101 </HEAD>
12102 <BODY>
12103 <H1>TAKE ADDRESS COMMANDS</H1>
12104 <!--chtml if pinemode="function_key"-->
12105 <PRE>
12106 Navigating the List of Addresses Address Selection Commands
12107 -------------------------------- --------------------------
12108 F5 Move to previous entry F3 Exit without taking address
12109 F6 Move to next entry F4 Take current address(es)
12110 F7 Show previous page of address list
12111 F8 Show next page of address list
12112 F2 WhereIs (search list)
12113 --------------
12114 Mode Toggle F9 Set/Unset current address
12115 ----------- F10 Set all
12116 F12 Toggle between List and single mode F11 Unset all
12117 </PRE>
12118 <!--chtml else-->
12119 <PRE>
12120 Navigating the List of Addresses Address Selection Commands
12121 -------------------------------- --------------------------
12122 P Move to previous entry < Exit without taking address
12123 N Move to next entry T Take address
12124 - Show previous page of address list
12125 Spc (space bar) Show next page of address list
12126 W WhereIs (search list) List Mode
12127 ---------
12128 Single Mode X Set/Unset current address
12129 ----------- A Set all addresses
12130 L Switch to list mode U Unset all addresses
12131 S Switch to single mode
12132 </PRE>
12133 <!--chtml endif-->
12135 <H2>Description of the Take Address Screen</H2>
12137 This screen is designed to let you select one or more address/name
12138 combinations from the current message and put them into your address book.
12139 The cursor is initially placed on the line with the message author.
12140 Other lines include the names of people and/or mailing lists who also
12141 received the message. Other people "involved" in the
12142 message (e.g. the person named as Reply-To:) are also listed here.
12143 <P>
12145 The simple case is adding a new, single entry into your address book. To
12146 do this, simply highlight the correct line and press
12147 <!--chtml if pinemode="function_key"-->
12148 F4.
12149 <!--chtml else-->
12150 "T".
12151 <!--chtml endif-->
12152 To create a new list or add to an existing list, switch the screen display
12153 into List Mode by pressing
12154 <!--chtml if pinemode="function_key"-->
12155 F12.
12156 <!--chtml else-->
12157 "L".
12158 <!--chtml endif-->
12159 In List Mode, you select the
12160 group of addresses you wish to manipulate by marking them with an
12161 "X".
12162 The Set/Unset
12163 <!--chtml if pinemode="function_key"-->
12164 (F9)
12165 <!--chtml else-->
12166 ("X")
12167 <!--chtml endif-->
12168 command will turn the "X" on for the
12169 highlighted address if it was off or turn it off if it was previously on.
12170 The SetAll command will select all of the addresses, and the UnSetAll
12171 command will turn off all the selections. Once you've gotten the
12172 selection the way you want it, you may create a new list by pressing
12173 <!--chtml if pinemode="function_key"-->
12174 F4.
12175 <!--chtml else-->
12176 "T".
12177 <!--chtml endif-->
12178 <P>
12180 In both the simple and list cases, after choosing to take the address,
12181 you will be asked for the nickname of the entry. Typing in a new name
12182 creates the new entry/list. Entering an existing nickname will replace
12183 the entry (simple case) or add to the list (list case). Alternatively,
12184 you can press Ctrl-T at the nickname prompt and select an existing
12185 nickname from your address book.
12186 <P>
12188 You will normally start in Single Mode, unless you used the Apply command
12189 to startup the TakeAddr screen, in which case you will start in List Mode.
12190 You may switch between the two modes at any time. If you've already
12191 selected several addresses in List Mode, those will be remembered when you
12192 switch to Single Mode and then back to List Mode. The set of addresses
12193 that are pre-selected when you start in List Mode are the From addresses
12194 of all of the messages you are operating on. You may, of course, easily
12195 erase those selections with the UnSetAll command.
12196 <P>
12198 If you have more than one writable address book, you will be prompted for
12199 the name of the address book you wish to add the new entry to before
12200 anything else. You can use ^N and ^P to choose among the defined address
12201 books, or type in the address book name.
12202 <P>
12204 FOR MORE INFORMATION on addressing see
12205 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12206 <A HREF="h_abook_opened">Address Book Screen's</A>
12207 help text.
12208 <P>
12209 <End of help on this topic>
12210 </BODY>
12211 </HTML>
12212 ===== h_takeexport_screen =====
12213 <HTML>
12214 <HEAD>
12215 <TITLE>Take Export Screen Explained</TITLE>
12216 </HEAD>
12217 <BODY>
12218 <H1>TAKE EXPORT COMMANDS</H1>
12219 <!--chtml if pinemode="function_key"-->
12220 <PRE>
12221 Navigating the List of Addresses Address Selection Commands
12222 -------------------------------- --------------------------
12223 F5 Move to previous entry F3 Exit without taking address
12224 F6 Move to next entry F4 Take current address(es)
12225 F7 Show previous page of address list
12226 F8 Show next page of address list
12227 F2 WhereIs (search list)
12228 --------------
12229 Mode Toggle F9 Set/Unset current address
12230 ----------- F10 Set all
12231 F12 Toggle between List and single mode F11 Unset all
12232 </PRE>
12233 <!--chtml else-->
12234 <PRE>
12235 Navigating the List of Addresses Address Selection Commands
12236 -------------------------------- --------------------------
12237 P Move to previous entry < Exit without taking address
12238 N Move to next entry T Take address
12239 - Show previous page of address list
12240 Spc (space bar) Show next page of address list
12241 W WhereIs (search list) List Mode
12242 ---------
12243 Single Mode X Set/Unset current address
12244 ----------- A Set all addresses
12245 L Switch to list mode U Unset all addresses
12246 S Switch to single mode
12247 </PRE>
12248 <!--chtml endif-->
12250 <H2>Description of the Take Export Screen</H2>
12252 This screen is designed to let you select one or more addresses
12253 from the current message and put them into a file.
12254 Only the user@domain_name part of each address is put into the file.
12255 <P>
12257 To put a single entry into a file simply highlight the correct line and press
12258 <!--chtml if pinemode="function_key"-->
12259 F4.
12260 <!--chtml else-->
12261 "T".
12262 <!--chtml endif-->
12263 To put more than one entry into a file
12264 switch the screen display
12265 into List Mode by pressing
12266 <!--chtml if pinemode="function_key"-->
12267 F12.
12268 <!--chtml else-->
12269 "L".
12270 <!--chtml endif-->
12271 In List Mode, you select the
12272 group of addresses you wish to manipulate by marking them with an
12273 "X".
12274 The Set/Unset
12275 <!--chtml if pinemode="function_key"-->
12276 (F9)
12277 <!--chtml else-->
12278 ("X")
12279 <!--chtml endif-->
12280 command will turn the "X" on for the
12281 highlighted address if it was off or turn it off if it was previously on.
12282 The SetAll command will select all of the addresses, and the UnSetAll
12283 command will turn off all the selections. Once you've gotten the
12284 selection the way you want it, you may put the addresses in a file by typing
12285 <!--chtml if pinemode="function_key"-->
12286 F4.
12287 <!--chtml else-->
12288 "T".
12289 <!--chtml endif-->
12290 <P>
12292 You will be asked for the name of a file to put the addresses in.
12293 If the file already exists, you will be asked whether you want to Overwrite
12294 (replace) the contents of the file or Append to the contents of the file.
12295 <P>
12297 <End of help on this topic>
12298 </BODY>
12299 </HTML>
12300 ============= h_abook_view ========================
12301 <HTML>
12302 <HEAD>
12303 <TITLE>Address Book View Explained</TITLE>
12304 </HEAD>
12305 <BODY>
12306 This function allows you to view the contents of an address book entry. You
12307 can only view one entry at a time.
12308 <P>
12309 <DL>
12310 <DT>Help
12311 <!--chtml if pinemode="function_key"-->
12312 (F1)
12313 <!--chtml else-->
12314 (?)
12315 <!--chtml endif-->
12316 </DT>
12317 <DD>
12318 Display this help text.
12320 <DT>Abook
12321 <!--chtml if pinemode="function_key"-->
12322 (F3)
12323 <!--chtml else-->
12324 (<)
12325 <!--chtml endif-->
12326 </DT>
12327 <DD>
12328 Go back to index of address book entries.
12330 <DT>Update
12331 <!--chtml if pinemode="function_key"-->
12332 (F4)
12333 <!--chtml else-->
12334 (U)
12335 <!--chtml endif-->
12336 </DT>
12337 <DD>
12338 Update (modify) this entry.
12340 <DT>ComposeTo
12341 <!--chtml if pinemode="function_key"-->
12342 (F5)
12343 <!--chtml else-->
12344 (C)
12345 <!--chtml endif-->
12346 </DT>
12347 <DD>Compose a message to the address(es) in this entry.
12349 <DT>Role
12350 <!--chtml if pinemode="function_key"-->
12351 (F6)
12352 <!--chtml else-->
12353 (#)
12354 <!--chtml endif-->
12355 </DT>
12356 <DD>Compose a message to the address(es) in this entry using roles.
12358 <DT>Prev Page
12359 <!--chtml if pinemode="function_key"-->
12360 (F7)
12361 <!--chtml else-->
12362 (-)
12363 <!--chtml endif-->
12364 </DT>
12365 <DD>
12366 Show the previous page of the current entry.
12368 <DT>Next Page
12369 <!--chtml if pinemode="function_key"-->
12370 (F8)
12371 <!--chtml else-->
12372 (Space)
12373 <!--chtml endif-->
12374 </DT>
12375 <DD>
12376 Show the next page of the current entry.
12378 <DT>Print
12379 <!--chtml if pinemode="function_key"-->
12380 (F9)
12381 <!--chtml else-->
12382 (%)
12383 <!--chtml endif-->
12384 </DT>
12385 <DD>Print the current entry. You can select the
12386 printer or the print command via the "Setup" command
12387 on the MAIN MENU.
12389 <DT>WhereIs
12390 <!--chtml if pinemode="function_key"-->
12391 (F10)
12392 <!--chtml else-->
12393 (W)
12394 <!--chtml endif-->
12395 </DT>
12396 <DD>Search the entry for a string of letters. If it is
12397 found, move to it. The string can be one word or a phrase.
12398 If there are multiple occurrences, the cursor moves to the
12399 first occurrence beyond the current cursor position.
12401 <DT>Fwd Email
12402 <!--chtml if pinemode="function_key"-->
12403 (F11)
12404 <!--chtml else-->
12405 (F)
12406 <!--chtml endif-->
12407 </DT>
12408 <DD>Begin composition of a new mail message with the displayed
12409 text already inserted in the message body.
12411 </DL>
12412 <P>
12413 <End of help on this topic>
12414 </BODY>
12415 </HTML>
12416 ============= h_ldap_view ========================
12417 <HTML>
12418 <HEAD>
12419 <TITLE>LDAP Response View Explained</TITLE>
12420 </HEAD>
12421 <BODY>
12422 This function allows you to view the contents of a directory entry. You
12423 can only view one entry at a time.
12424 <P>
12425 <DL>
12426 <DT>Help
12427 <!--chtml if pinemode="function_key"-->
12428 (F1)
12429 <!--chtml else-->
12430 (?)
12431 <!--chtml endif-->
12432 </DT>
12433 <DD>
12434 Display this help text.
12436 <DT>Results Index
12437 <!--chtml if pinemode="function_key"-->
12438 (F3)
12439 <!--chtml else-->
12440 (<)
12441 <!--chtml endif-->
12442 </DT>
12443 <DD>Go back to index of search results.
12445 <DT>ComposeTo
12446 <!--chtml if pinemode="function_key"-->
12447 (F5)
12448 <!--chtml else-->
12449 (C)
12450 <!--chtml endif-->
12451 </DT>
12452 <DD>Compose a message to the address(es) in this entry.
12454 <DT>Role
12455 <!--chtml if pinemode="function_key"-->
12456 (F6)
12457 <!--chtml else-->
12458 (#)
12459 <!--chtml endif-->
12460 </DT>
12461 <DD>Compose a message to the address(es) in this entry using roles.
12463 <DT>Prev Page
12464 <!--chtml if pinemode="function_key"-->
12465 (F7)
12466 <!--chtml else-->
12467 (-)
12468 <!--chtml endif-->
12469 </DT>
12470 <DD>
12471 Show the previous page of the current entry.
12473 <DT>Next Page
12474 <!--chtml if pinemode="function_key"-->
12475 (F8)
12476 <!--chtml else-->
12477 (Space)
12478 <!--chtml endif-->
12479 </DT>
12480 <DD>
12481 Show the next page of the current entry.
12483 <DT>Print
12484 <!--chtml if pinemode="function_key"-->
12485 (F9)
12486 <!--chtml else-->
12487 (%)
12488 <!--chtml endif-->
12489 </DT>
12490 <DD>Print the current entry on paper. You can select the
12491 printer or the print command via the "Setup" command
12492 on the MAIN MENU.
12494 <DT>WhereIs
12495 <!--chtml if pinemode="function_key"-->
12496 (F10)
12497 <!--chtml else-->
12498 (W)
12499 <!--chtml endif-->
12500 </DT>
12501 <DD>Search the entry for a string of letters. If it is
12502 found, move to it. The string can be one word or a phrase.
12503 If there are multiple occurrences, the cursor moves to the
12504 first occurrence beyond the current cursor position.
12506 <DT>Fwd Email
12507 <!--chtml if pinemode="function_key"-->
12508 (F11)
12509 <!--chtml else-->
12510 (F)
12511 <!--chtml endif-->
12512 </DT>
12513 <DD>Begin composition of a new mail message with the displayed
12514 text already inserted in the message body.
12516 <DT>Save
12517 <!--chtml if pinemode="function_key"-->
12518 (F12)
12519 <!--chtml else-->
12520 (S)
12521 <!--chtml endif-->
12522 </DT>
12523 <DD>Save the displayed entry to one of your address books or export
12524 it to a file.
12525 </DL>
12526 <P>
12527 <End of help on this topic>
12528 </BODY>
12529 </HTML>
12530 ===== h_attachment_screen =====
12531 <HTML>
12532 <HEAD>
12533 <TITLE>Attachment Index Screen Explained</TITLE>
12534 </HEAD>
12535 <BODY>
12536 The "ATTACHMENT INDEX" displays a list of the current
12537 message's attachments, and allows various operations on them. The
12538 first attachment is usually the message text, but does not include the
12539 header portion of the message.
12540 <P>
12541 Available commands include:
12542 <P>
12543 <DL>
12545 <DT>Help</DT>
12546 <DD>Show this help text.
12548 <DT>Msg #<I>num</I></DT>
12549 <DD>Leave this screen without displaying or saving any attachments.
12551 <DT>View</DT>
12552 <DD>View the currently selected attachment.
12554 <DT>Prev Attach</DT>
12555 <DD>Move to previous attachment.
12557 <DT>Next Attach</DT>
12558 <DD>Move to next attachment.
12560 <DT>Prev Page</DT>
12561 <DD>Previous page of the listed attachments.
12563 <DT>Next Page</DT>
12564 <DD>Next page of the listed attachments.
12566 <DT>Delete</DT>
12567 <DD>Mark the currently selected attachment for Deletion.
12568 This does not modify the current message by deleting the attachment from
12569 it, but instead the delete flag <EM>only</EM> has an effect when saving
12570 the message to a folder.
12571 Attachments marked for deletion are not copied to the destination folder
12572 along with the rest of the message when it is saved.
12573 It is ok for the destination folder to be the same as the current folder.
12574 In addition, the delete mark <EM>only</EM> applies to this Alpine session.
12576 <DT>Undelete</DT>
12577 <DD>Turn off the Delete flag for the selected attachment.
12579 <DT>Save</DT>
12580 <DD>Save the selected attachment to a file. If the attachment is of
12581 type "RFC822/Message", then the attachment will be saved to
12582 the specified mail folder.
12584 <DT>Export</DT>
12585 <DD>If the attachment is of
12586 type "RFC822/Message", then "Export" is used to
12587 copy the message to a file in the same way this command works on
12588 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
12590 <DT>Pipe</DT>
12591 <DD>Pipe the attachment contents into a UNIX command (if enabled).
12592 A description of the Pipe sub-commands is <A HREF="h_pipe_command">here</A>.
12594 <DT>WhereIs</DT>
12595 <DD>Find a matching string in the attachment list.
12597 <DT>AboutAttch</DT>
12598 <DD>Examine various aspects of the selected attachment.
12600 <DT>Print</DT>
12601 <DD>Print the selected attachment.
12603 <DT>Forward</DT>
12604 <DD>Forward the selected attachment as an attachment.
12605 </DL>
12607 <P>
12609 All attachments can be saved or piped into a UNIX command, but some may
12610 not be readily displayed by either Alpine or an external tool. In such
12611 cases, the reason why the message cannot be displayed is displayed on
12612 Alpine's message line.
12613 <P>
12614 <End of help on this topic>
12615 </BODY>
12616 </HTML>
12617 ============= h_mail_text_att_view ========================
12618 <HTML>
12619 <HEAD>
12620 <TITLE>Attachment View Screen Explained</TITLE>
12621 </HEAD>
12622 <BODY>
12623 This function allows you to view the contents of a text attachment. You
12624 can only view one attachment at a time.
12625 <P>
12626 Available commands include:
12627 <P>
12628 <DL>
12630 <DT>Help</DT>
12631 <DD>Display this help text
12633 <DT>AttchIndex</DT>
12634 <DD>Leave viewer and return to the "ATTACHMENT INDEX" screen
12636 <DT>Prev Page</DT>
12637 <DD>Show the previous page of the current attachment.
12639 <DT>Next Page</DT>
12640 <DD>Show the next page of the current attachment by pressing the space bar.
12642 <DT>Delete</DT>
12643 <DD>Mark the viewed attachment for Deletion. The delete
12644 flag <EM>only</EM> has affect when saving the message to a folder.
12645 Attachments marked for deletion are exluded from the messsage when
12646 it is saved. In addition, the delete mark <EM>only</EM> applies to
12647 this Alpine session.
12649 <DT>Undelete</DT>
12650 <DD>Turn off the Delete flag for the selected attachment.
12652 <DT>Save</DT>
12653 <DD>Copy the current attachment to a file. If you just enter
12654 a filename, the attachment will be saved with that name in
12655 your home directory
12656 <!--chtml if pinemode="running"-->
12657 (which, in the present configuration of your system, is
12658 "<!--#echo var="HOME_DIR"-->")
12659 <!--chtml endif-->
12660 or current working directory
12661 <!--chtml if pinemode="running"-->
12662 (which, at least for your current Alpine "session,"
12663 is "<!--#echo var="CURRENT_DIR"-->")
12664 <!--chtml endif-->, depending on the
12665 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
12666 configuration setting. You may enter the full
12667 path and filename to save it in another directory instead.
12669 <DT>Export</DT>
12670 <DD>If the attachment is of
12671 type "RFC822/Message", then "Export" is used to
12672 copy the message to a file in the same way this command works on
12673 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
12674 (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
12675 defined, they may affect the contents of the exported file.)
12677 <DT>Pipe</DT>
12678 <DD>Pipe the attachment contents into a UNIX command (if enabled)
12680 <DT>WhereIs</DT>
12681 <DD>Search the attachment for a string of letters. If it is
12682 found, move to it. The string can be one word or a phrase.
12683 If there are multiple occurrences, the cursor moves to the
12684 first occurrence beyond the current cursor position.
12686 <DT>Print</DT>
12687 <DD>Print the current attachment on paper. You can select the
12688 printer or the print command via the "Setup" command
12689 on the MAIN MENU.
12691 <DT>Forward</DT>
12692 <DD>Forward the selected attachment as an attachment.
12693 </DL>
12694 <P>
12695 <End of help on this topic>
12696 </BODY>
12697 </HTML>
12698 ============= h_journal ==============
12699 <HTML>
12700 <HEAD>
12701 <TITLE>Recent Message Journal Explained</TITLE>
12702 </HEAD>
12703 <BODY>
12705 The following commands are available on this screen:
12706 <P>
12707 <DL>
12708 <DT>Help</DT>
12709 <DD>Show this help text
12711 <DT>Exit</DT>
12712 <DD>Exit Viewer, and go back to mail processing
12714 <DT>Prev Page</DT>
12715 <DD>Show the previous page text
12717 <DT>Next Page</DT>
12718 <DD>Show the next page of text by pressing the space bar
12720 <DT>Print</DT>
12721 <DD>Print the displayed text on paper. You can select the
12722 printer or the print command via the "Setup" command
12723 on the MAIN MENU.
12725 <DT>Fwd Email</DT>
12726 <DD>Begin composition of a new mail message with the displayed
12727 text already inserted in the message body.
12729 <DT>Save</DT>
12730 <DD>Copy the displayed text to a file. If you just enter
12731 a filename, the text will be saved with that name in
12732 your
12733 home directory
12734 <!--chtml if pinemode="running"-->
12735 (which, in the present configuration of your system, is
12736 "<!--#echo var="HOME_DIR"-->")
12737 <!--chtml endif-->
12738 or current working directory
12739 <!--chtml if pinemode="running"-->
12740 (which, at least for your current Alpine "session,"
12741 is "<!--#echo var="CURRENT_DIR"-->")
12742 <!--chtml endif-->, depending on the
12743 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
12744 configuration setting. You may enter the full
12745 path and filename to save it in another directory instead.
12747 <DT>WhereIs</DT>
12748 <DD>Search the text for a string of letters. If it is
12749 found, move to it. The string can be one word or a phrase.
12750 If there are multiple occurrences, the cursor moves to the
12751 first occurrence beyond the current cursor position.
12752 </DL>
12753 <P>
12754 <End of help on this topic>
12755 </BODY>
12756 </HTML>
12757 ============= h_debugjournal ==============
12758 <HTML>
12759 <HEAD>
12760 <TITLE>Debug Journal Explained</TITLE>
12761 </HEAD>
12762 <BODY>
12764 The following commands are available on this screen:
12765 <P>
12766 <DL>
12767 <DT>Help</DT>
12768 <DD>Show this help text
12770 <DT>Exit</DT>
12771 <DD>Exit Viewer, and go back to mail processing
12773 <DT>Timestamps</DT>
12774 <DD>Turn on or off timestamps.
12776 <DT>DebugView</DT>
12777 <DD>Set the level of debugging you want to see. The level may be any number
12778 in the range 0-9. Higher numbers show more debugging detail. Note that the
12779 debugging information has already been captured. This setting just causes the
12780 debugging information that you see to be filtered. If you set this to
12781 the number "5" then you will be shown all of the debugging information
12782 at levels 5 and below.
12783 It's actually a bit more complicated than that. A fixed amount of memory
12784 is used to store the debug information.
12785 Since the amount of memory used is limited the debugging information
12786 has to be trimmed back when it gets too large.
12788 <DT>Prev Page</DT>
12789 <DD>Show the previous page text
12791 <DT>Next Page</DT>
12792 <DD>Show the next page of text by pressing the space bar
12794 <DT>Print</DT>
12795 <DD>Print the displayed text on paper. You can select the
12796 printer or the print command via the "Setup" command
12797 on the MAIN MENU.
12799 <DT>Fwd Email</DT>
12800 <DD>Begin composition of a new mail message with the displayed
12801 text already inserted in the message body.
12803 <DT>Save</DT>
12804 <DD>Copy the displayed text to a file. If you just enter
12805 a filename, the text will be saved with that name in
12806 your
12807 home directory
12808 <!--chtml if pinemode="running"-->
12809 (which, in the present configuration of your system, is
12810 "<!--#echo var="HOME_DIR"-->")
12811 <!--chtml endif-->
12812 or current working directory
12813 <!--chtml if pinemode="running"-->
12814 (which, at least for your current Alpine "session,"
12815 is "<!--#echo var="CURRENT_DIR"-->")
12816 <!--chtml endif-->, depending on the
12817 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
12818 configuration setting. You may enter the full
12819 path and filename to save it in another directory instead.
12821 <DT>WhereIs</DT>
12822 <DD>Search the text for a string of letters. If it is
12823 found, move to it. The string can be one word or a phrase.
12824 If there are multiple occurrences, the cursor moves to the
12825 first occurrence beyond the current cursor position.
12826 </DL>
12827 <P>
12828 <End of help on this topic>
12829 </BODY>
12830 </HTML>
12831 ============= h_simple_text_view ==============
12832 <HTML>
12833 <HEAD>
12834 <TITLE>Simple Text View Screen Explained</TITLE>
12835 </HEAD>
12836 <BODY>
12838 The following commands are available on this screen:
12839 <P>
12840 <DL>
12841 <DT>Help</DT>
12842 <DD>Show this help text
12844 <DT>Exit</DT>
12845 <DD>Exit Viewer, and go back to mail processing
12847 <DT>Prev Page</DT>
12848 <DD>Show the previous page text
12850 <DT>Next Page</DT>
12851 <DD>Show the next page of text by pressing the space bar
12853 <DT>Print</DT>
12854 <DD>Print the displayed text on paper. You can select the
12855 printer or the print command via the "Setup" command
12856 on the MAIN MENU.
12858 <DT>Fwd Email</DT>
12859 <DD>Begin composition of a new mail message with the displayed
12860 text already inserted in the message body.
12862 <DT>Save</DT>
12863 <DD>Copy the displayed text to a file. If you just enter
12864 a filename, the attachment will be saved with that name in
12865 your
12866 home directory
12867 <!--chtml if pinemode="running"-->
12868 (which, in the present configuration of your system, is
12869 "<!--#echo var="HOME_DIR"-->")
12870 <!--chtml endif-->
12871 or current working directory
12872 <!--chtml if pinemode="running"-->
12873 (which, at least for your current Alpine "session,"
12874 is "<!--#echo var="CURRENT_DIR"-->")
12875 <!--chtml endif-->, depending on the
12876 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
12877 configuration setting. You may enter the full
12878 path and filename to save it in another directory instead.
12880 <DT>WhereIs</DT>
12881 <DD>Search the attachment for a string of letters. If it is
12882 found, move to it. The string can be one word or a phrase.
12883 If there are multiple occurrences, the cursor moves to the
12884 first occurrence beyond the current cursor position.
12885 </DL>
12886 <P>
12887 <End of help on this topic>
12888 </BODY>
12889 </HTML>
12890 ======= h_pine_for_windows ========
12891 <HTML>
12892 <HEAD>
12893 <TITLE>GETTING HELP IN PC-ALPINE</TITLE>
12894 </HEAD>
12895 <BODY>
12896 <H1>Getting Help In PC-Alpine</H1>
12898 <P>
12899 PC-Alpine offers general and specific help text. From the <A
12900 HREF="main_menu_tx">MAIN MENU</A>, you will find an overview in the MAIN
12901 MENU HELP and the <A HREF="h_news">Release Notes</A>. On all screens,
12902 specific help for that screen is available from the toolbar Help menu or
12903 with the
12904 <!--chtml if pinemode="function_key"-->
12905 "F1" key.
12906 <!--chtml else-->
12907 "?" or "Ctrl-G" keys. "Ctrl-G" is used where
12908 typing "?" would be mistaken as entering text.
12909 <!--chtml endif-->
12911 <P>
12912 Although this version of Alpine is for Microsoft Windows, it is not
12913 considered a full "Graphical User Interface" application.
12914 Yet, many of the controls that Windows users are accustomed to seeing,
12915 such as scrollbars and toolbars, are available.
12917 <P>
12918 PC-Alpine offers considerable mouse support. You can view what is
12919 "click-able" by dragging your mouse over any screen; when the
12920 arrow cursor changes into a hand, you found something. Mouse-click
12921 possibilities include navigating between screens and folders and
12922 double-clicking on hyperlinks to open your Web browser.
12923 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
12924 screen. Examples of right-click options include "copy" after
12925 selecting text to copy and "View in New Window" when you click
12926 on a particular message in the Message Index. The menu choices available
12927 to you will vary based upon what screen is open, where on the screen your
12928 cursor is located, and even what action you have already taken.
12930 <P>
12931 <End of help on this topic>
12932 </BODY>
12933 </HTML>
12934 ===== h_composer =====
12935 <HTML>
12936 <HEAD>
12937 <TITLE>COMPOSER COMMANDS</TITLE>
12938 </HEAD>
12939 <BODY>
12940 <H1>COMPOSER COMMANDS</H1>
12942 CURSOR MOTION KEYS |EDITING KEYS<BR>
12943 ^B (Left Arrow) Back character | ^D Delete current character<BR>
12944 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
12945 ^P (Up Arrow) Previous line | ^^ Set a <A HREF="h_compose_markcutpaste">mark</A><BR>
12946 ^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>
12947 ^A Beginning of line | delete current line<BR>
12948 ^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>
12949 ^Y Previous page | cut with ^K, or unjustify<BR>
12950 ^V Next page |-------------------------------------<BR>
12951 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
12952 ---------------------------------------| <!--chtml if pinemode="function_key"-->F6<!--chtml else-->^W<!--chtml endif--> <A HREF="h_composer_search">Whereis</A> (search for string)<BR>
12953 MESSAGE COMMANDS | GENERAL COMMANDS | <!--chtml if pinemode="function_key"-->F12<!--chtml else-->^T <!--chtml endif--> <A HREF="h_compose_spell">Spell checker</A><BR>
12954 <!--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>
12955 <!--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>
12956 <!--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>
12958 <P>
12959 NOTE:
12960 <OL>
12961 <LI>For help on a particular command, highlight the bold text associated
12962 with it above and hit Return.
12963 <LI> The availability of certain commands
12964 is determined by Alpine configuration files and system capabilities.
12965 At some sites, certain commands may not be available due to security or
12966 support concerns.
12967 <LI>Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
12968 Ctrl-\, ESC.
12969 <LI>For special handling of Ctrl-S and Ctrl-Q see special comments regarding
12970 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
12971 </OL>
12973 <P>
12974 HINT: To move rapidly to the bottom of a message you are composing,
12975 enter ^W^V. To go to the top, ^W^Y. These can be used in conjunction
12976 with the Mark and Cut commands to eliminate large amounts of unwanted
12977 text in a Reply.
12979 <H2>Description of Composer</H2>
12981 Alpine has a built-in editing program that allows you to compose messages
12982 without having to leave Alpine. The editor is designed to be very simple to
12983 use so that you can get started writing email right away.
12985 <P>
12986 Messages are usually just text, about 80 columns wide. Using upper and
12987 lower case is encouraged. On some systems the size limit of the message
12988 is about 100,000 characters, which is about 2,000 lines. You can include
12989 punctuation and special characters found on most keyboards, but you can't
12990 include characters with diacritical marks and certain special symbols.
12992 <P>
12993 Text automatically wraps as you type past the end of a line so you do not
12994 have to hit return. Using the
12995 "<A HREF="h_compose_justify">Justify</A>" command,
12996 you can also reformat text explicitly, perhaps after you have
12997 deleted some text.
12999 <P>
13000 You can include other text files with the
13001 "<A HREF="h_compose_readfile">Read File</A>" command,
13002 which will prompt you for the name of the file to insert at the
13003 current cursor postion.
13005 <P>
13006 <UL>
13007 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13008 </UL>
13009 <P>
13010 <End of help on this topic>
13011 </BODY>
13012 </HTML>
13013 ====== h_composer_browse =====
13014 <HTML>
13015 <HEAD>
13016 <TITLE>BROWSER</TITLE>
13017 </HEAD>
13018 <BODY>
13019 <H1>BROWSER</H1>
13020 This screen lets you browse your files and directories. To go to another
13021 directory (identified by "(dir)"), move the cursor to it and
13022 choose "Select" (the default choice on the menu);
13023 or choose "Goto" and enter the name of the directory.
13024 <!--chtml if pinemode="os_windows"-->
13025 <!--chtml else-->
13026 In Unix Alpine, you may use
13027 "~" to refer to your home directory or "~user" to refer
13028 to another's home directory.
13029 <!--chtml endif--><P>
13030 To select a file, move the cursor to it and
13031 choose "Select" (the default choice on the menu).
13032 <P>
13033 <UL>
13034 <LI>Note <B>if</B> you are currently using the BROWSER for choosing a file for
13035 inclusion in the
13036 message body (that is, you chose "Read File" with the cursor under
13037 the
13038 "----- Message Text -----" line
13039 while composing, then "To Files"): Since the file
13040 selected will become part of the message text, it must be in a format
13041 suitable for that (Alpine does not check!), such as a plain text file.
13042 Files of other formats (for example, graphics, databases, software
13043 programs) should be
13044 <B>attached</B> to the message instead --
13045 by moving the cursor in the COMPOSE MESSAGE screen into the
13046 message header area and pressing
13047 <!--chtml if pinemode="function_key"-->
13048 F6.
13049 <!--chtml else-->
13050 Ctrl-J.
13051 <!--chtml endif-->
13053 <P><LI>
13054 Note <B>if</B> you are currently using the BROWSER for saving a message
13055 attachment, or exporting a message, to a file: You can use the Add command to
13056 provide the name for a new file to save/export to, and then select that name
13057 to use it for the save/export operation. Back at the prompt
13058 "EXPORT: Copy message to file in ..." hit Enter, then choose
13059 either Overwrite or Append (it doesn't make a difference, since the file is
13060 so far empty). Note: If you cancel the
13061 operation at that point, the file created with the Add command will remain
13062 0 bytes in size.
13064 </UL>
13065 <P><UL>
13066 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13067 </UL>
13068 <P>
13069 <End of help on this topic>
13070 </BODY>
13071 </HTML>
13072 ====== h_composer_ins =====
13073 <HTML>
13074 <HEAD>
13075 <TITLE>INSERT TEXT FILE</TITLE>
13076 </HEAD>
13077 <BODY>
13078 <H1>INSERT TEXT FILE</H1>
13080 Use this function to insert a text file. The file name
13081 given can be an absolute file path name for your system
13082 <!--chtml if pinemode="os_windows"-->
13083 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
13084 with a relative pathname, or simply a file name without
13085 drive or directory specification.
13086 <!--chtml else-->
13087 (for example, "/tmp/exported.earlier" on Unix hosts),
13088 a file in your home directory, or a file path relative to your
13089 home directory. In Unix Alpine, you may use "~" to refer to
13090 your home directory or "~user" to refer to another
13091 account's home directory.
13092 <!--chtml endif-->
13093 <P>
13094 No wild card characters may be used.
13095 The file must reside on the system running Alpine.
13096 <P>
13097 If the
13098 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13099 feature is set, names are relative to your current working directory
13100 <!--chtml if pinemode="running"-->
13101 (which, at least for your current Alpine "session,"
13102 is "<!--#echo var="CURRENT_DIR"-->")
13103 <!--chtml endif-->
13104 rather than your home directory
13105 <!--chtml if pinemode="running"-->
13106 (which, in the present configuration of your system, is
13107 "<!--#echo var="HOME_DIR"-->")
13108 <!--chtml endif-->
13109 .
13110 <P><UL>
13111 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13112 </UL>
13113 <P>
13114 <End of help on this topic>
13115 </BODY>
13116 </HTML>
13117 ====== h_composer_ins_m =====
13118 <HTML>
13119 <HEAD>
13120 <TITLE>INSERT MESSAGE</TITLE>
13121 </HEAD>
13122 <BODY>
13123 <H1>INSERT MESSAGE</H1>
13125 Type in the number of a message in the currently open folder to insert it
13126 into your message.
13127 <P><UL>
13128 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13129 </UL>
13130 <P>
13131 <End of help on this topic>
13132 </BODY>
13133 </HTML>
13134 ====== h_composer_search =====
13135 <HTML>
13136 <HEAD>
13137 <TITLE>Explanation of Composer Whereis Command </TITLE>
13138 </HEAD>
13139 <BODY>
13140 <H1>Help For Whereis Command</H1>
13142 Whereis is used to search the message for a word or part of a word.
13143 When searching in the composer, only the message part of your mail is
13144 searched, and the cursor is put on the first occurrence appearing
13145 after the location of the cursor. The search will wrap to the
13146 beginning of the message when it no longer finds matches in the
13147 remainder of the message.
13149 To search for the same string a second time, press
13150 <!--chtml if pinemode="function_key"-->
13151 "F6"
13152 <!--chtml else-->
13153 "^W"
13154 <!--chtml endif-->
13155 to begin search and then just press RETURN to accept the previous
13156 search string shown in square brackets rather than entering a new
13157 search string.<P>
13159 The "Search" prompt has several sub-command available:
13161 <DL>
13162 <DT>Get Help</DT>
13163 <DD> Takes you to this help page.
13165 <DT>Cancel</DT>
13166 <DD> Cancels the prompt. No search takes place.
13168 <DT>First Line</DT>
13169 <DD> Takes you back to the composer with the cursor on the first character
13170 of the first line of text.
13172 <DT>Last Line</DT>
13173 <DD> Takes you back to the composer with the cursor on the last character
13174 of the last line of text.
13176 <DT>Replace (Optional)</DT>
13177 <DD> This sub-command is enabled by the
13178 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13179 feature (which is on by default); see its help screen for details on how replacing works.
13181 </DL>
13183 <End of help on this topic>
13184 </BODY>
13185 </HTML>
13186 ====== h_sigedit_search =====
13187 <HTML>
13188 <HEAD>
13189 <TITLE>Explanation of Whereis Command </TITLE>
13190 </HEAD>
13191 <BODY>
13192 <H1>Help For Whereis Command</H1>
13194 Whereis is used to search for a word or part of a word.
13195 When searching the cursor is put on the first occurrence appearing
13196 after the location of the cursor. The search will wrap to the
13197 beginning of the signature when it no longer finds matches in the
13198 remainder of the signature.
13200 To search for the same string a second time, press
13201 <!--chtml if pinemode="function_key"-->
13202 "F6"
13203 <!--chtml else-->
13204 "^W"
13205 <!--chtml endif-->
13206 to begin search and then just press RETURN to accept the previous
13207 search string shown in square brackets rather than entering a new
13208 search string.<P>
13210 The "Search" prompt has several sub-command available:
13212 <DL>
13213 <DT>Get Help</DT>
13214 <DD> Takes you to this help page.
13216 <DT>Cancel</DT>
13217 <DD> Cancels the prompt. No search takes place.
13219 <DT>First Line</DT>
13220 <DD> Takes you back to the composer with the cursor on the first character
13221 of the first line of text.
13223 <DT>Last Line</DT>
13224 <DD> Takes you back to the composer with the cursor on the last character
13225 of the last line of text.
13227 <DT>Replace (Optional)</DT>
13228 <DD> This sub-command is enabled by the
13229 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13230 feature (which is on by default); see its help screen for details on how replacing works.
13232 </DL>
13234 <End of help on this topic>
13235 </BODY>
13236 </HTML>
13237 ======= h_composer_to ====
13238 <HTML>
13239 <HEAD>
13240 <TITLE>THE MESSAGE COMPOSER'S TO FIELD</TITLE>
13241 </HEAD>
13242 <BODY>
13243 <H1>THE MESSAGE COMPOSER'S TO FIELD</H1>
13245 <H2>The "To:" field</H2>
13246 The address you enter here must be a valid email address that is reachable
13247 from your site.
13249 <H2>Email Address Format</H2>
13250 You may enter a full name and email address,
13251 <!--chtml if pinemode="os_windows"-->
13252 <!--chtml else-->
13253 a local (meaning, on the same
13254 host as the one you are running Alpine on) username that Alpine will
13255 complete for you,
13256 <!--chtml endif-->
13257 the nickname of someone in a
13258 <A HREF="h_abook_opened">Alpine Address Book</A>, or a local
13259 mail alias defined by your system administrator. When you move the cursor
13260 out of this field, the nicknames will be expanded to the addresses in your
13261 address book, and the local usernames will be expanded to include the
13262 persons' actual names. You may enter as many addresses as you wish, but they
13263 must be separated by commas. You can move around this and other header fields
13264 with the arrow keys and use many of the usual composer editing keys.
13265 <P>
13266 <UL>
13267 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13268 </UL>
13270 <P>
13271 <H2>MESSAGE HEADER COMMANDS</H2>
13272 <!--chtml if pinemode="function_key"-->
13273 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13274 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13275 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13276 ^P (Up Arrow) Previous line |<BR>
13277 ^N (Down Arrow) Next line | F9 Cut marked text or<BR>
13278 ^A Beginning of line | delete current line<BR>
13279 ^E End of line | F10 Undelete line(s)<BR>
13280 F7 Previous page | ^W <A HREF="h_composer_search">Whereis</A> (search text)<BR>
13281 F8 Next page |-------------------------------------<BR>
13282 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13283 ----------------------------------------|<BR>
13284 MESSAGE COMMANDS | GENERAL COMMANDS | F12 To Addressbook/Browser<BR>
13285 F3 <A HREF="h_compose_cancel">Cancel</A> | F1 Get help | F4 Attach File<BR>
13286 F11 <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13287 F2 <A HREF="h_compose_send">Send</A> | | F5 <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13288 <!--chtml else-->
13289 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13290 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13291 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13292 ^P (Up Arrow) Previous line | <BR>
13293 ^N (Down Arrow) Next line | ^K Cut marked text or<BR>
13294 ^A Beginning of line | delete current line<BR>
13295 ^E End of line | ^U Undelete line(s)<BR>
13296 ^Y Previous page |<BR>
13297 ^V Next page |-------------------------------------<BR>
13298 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13299 ----------------------------------------| ^R <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13300 MESSAGE COMMANDS | GENERAL COMMANDS | ^T To Addressbook/Browser<BR>
13301 ^C <A HREF="h_compose_cancel">Cancel</A> | ^G Get help | ^J Attach File<BR>
13302 ^O <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13303 ^X <A HREF="h_compose_send">Send</A> | | TAB <A HREF="h_compose_addrcomplete">Address Completion</A><BR>
13304 <!--chtml endif-->
13306 <P>
13307 NOTE:
13308 <OL>
13309 <LI>For help on a particular command, highlight the bold text associated
13310 with it above and hit Return.
13311 <LI> The availability of certain commands
13312 is determined by Alpine configuration files and system capabilities.
13313 At some sites, certain commands may not be available due to security or
13314 support concerns.
13315 </OL>
13317 <P>
13318 <UL>
13319 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13320 </UL><P>
13321 <End of help on this topic>
13322 </BODY>
13323 </HTML>
13324 ======= h_composer_cc ====
13325 <HTML>
13326 <HEAD>
13327 <TITLE>THE MESSAGE COMPOSER'S CC FIELD</TITLE>
13328 </HEAD>
13329 <BODY>
13330 <H1>THE MESSAGE COMPOSER'S CC FIELD</H1>
13331 The Cc: field is just like the To: field, except it is used for addressees
13332 that you wish to send a "carbon" copy to. That is, the message is
13333 not directly meant directly "for" these recipients, but you wanted
13334 them to see the message. The only difference the recipients see is that their
13335 name is in the Cc: field, rather than the To: field.
13336 <P>
13337 For help with Cc: field editing
13338 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13339 <P>
13340 <UL>
13341 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13342 </UL>
13343 <P>
13344 <UL>
13345 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13346 </UL><P>
13347 <End of help on this topic>
13348 </BODY>
13349 </HTML>
13350 ======= h_composer_bcc ====
13351 <HTML>
13352 <HEAD>
13353 <TITLE>THE MESSAGE COMPOSER'S BCC FIELD</TITLE>
13354 </HEAD>
13355 <BODY>
13356 <H1>THE MESSAGE COMPOSER'S BCC FIELD</H1>
13357 The "Bcc:" (Blind carbon copy) header is used when you wish to send
13358 a copy of the message to one or more people whose addresses you do not
13359 wish disclosed, either to reduce clutter or for confidentiality.
13360 <P>
13361 The format of the Bcc: field is just the same as the To: and Cc: fields in
13362 the way the addresses are entered. The recipients listed here will
13363 receive a copy of the message, but --assuming your site's mail transport
13364 software is properly configured-- their addresses will not show up in the
13365 headers of the message, as delivered to all of the recipients. The To:
13366 and Cc: recipients will not know a copy was sent to the Bcc: recipients.
13367 <P>
13368 Note: if there is no To: or Cc: or Lcc: address in the message, Alpine
13369 will automatically generate and place in the To: field a pseudo-address of
13370 "undisclosed-recipients: ;"
13371 or whatever string has been specified in the
13372 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
13373 variable.
13374 <P>
13375 The reason for this is to avoid embarrassment caused by some Internet
13376 mail transfer software that interprets a "missing" To: header as
13377 an error and replaces it with an Apparently-to: header that may contain
13378 the addresses you entered on the Bcc: line. In addition, it may be
13379 less disconcerting to Bcc: recipients to see <B>something</B> in the To: field.
13380 <P>
13381 You can manipulate what text ends up on the (originally) empty To:
13382 field. Just remember to put a colon and semicolon at the end of the
13383 field, which is a special notation denoting that it is not a real address.
13384 <P>
13385 For information on message header editing
13386 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13387 <P>
13388 <UL>
13389 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13390 </UL>
13391 <P>
13392 <UL>
13393 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13394 </UL><P>
13395 <End of help on this topic>
13396 </BODY>
13397 </HTML>
13398 ======= h_composer_lcc ====
13399 <HTML>
13400 <HEAD>
13401 <TITLE>THE MESSAGE COMPOSER'S LCC FIELD</TITLE>
13402 </HEAD>
13403 <BODY>
13404 <H1>THE MESSAGE COMPOSER'S LCC FIELD</H1>
13405 The "Lcc:" (List carbon copy) header is intended to be used when
13406 you wish to send a message to a list of people but avoid having all
13407 of their addresses visible, in order to reduce clutter when the
13408 message is received.
13409 <P>
13410 It is similar to the
13411 <A HREF="h_composer_bcc">"Bcc" (Blind carbon copy) header</A>
13412 in that individual
13413 addressees are hidden, but Lcc is designed to work specifically with
13414 distribution lists you have created in your
13415 <A HREF="h_abook_opened">Alpine Address Book</A>. Placing
13416 the nickname of the list on the Lcc line will result in the full name of
13417 your Alpine Address Book list being placed on the To: line of the message,
13418 using a special notation that distinguishes it from a real address. You
13419 must leave the To: line blank for your list name to appear there.
13420 <P>
13421 For example, if you have this list entered in your Address Book:<PRE>
13423 largo Key Largo List DISTRIBUTION LIST:
13424 bogie@mgm.com
13425 lauren@mgm.com
13426 walter@mgm.com</PRE>
13429 and you enter "largo" on the Lcc: line while composing a message,
13430 the result is:<PRE>
13432 To : Key Largo List: ;
13433 Cc :
13434 Bcc :
13435 Fcc : sent-mail
13436 Lcc : Key Largo List <bogie@mgm.com>,
13437 lauren@mgm.com,
13438 walter@mgm.com
13439 Subject :</PRE>
13441 Each recipient listed on the Lcc: line receives a copy of the message
13442 without their address being visible (as though they were listed on the
13443 Bcc: line). The colon-semicolon notation used to put the full-name of the
13444 list on the To: line is a special address format that doesn't specify any
13445 actual addressees, but does give some information to the recipients of the
13446 message.
13447 <P>
13448 Note: if after entering an LCC, you delete the list name that is placed
13449 on the To: line, then recipients will see <PRE>
13450 To: undisclosed-recipients: ;</PRE>
13452 (or whatever string is defined in the
13453 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
13454 variable) just as in the BCC case.
13455 <P>
13456 For help with Lcc: field editing
13457 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13458 <P>
13459 <UL>
13460 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13461 </UL>
13462 <P>
13463 <UL>
13464 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13465 </UL><P>
13466 <End of help on this topic>
13467 </BODY>
13468 </HTML>
13469 ======= h_composer_from =======
13470 <HTML>
13471 <HEAD>
13472 <TITLE>THE MESSAGE COMPOSER'S FROM FIELD</TITLE>
13473 </HEAD>
13474 <BODY>
13475 <H1>THE MESSAGE COMPOSER'S FROM FIELD</H1>
13477 This header carries your return address. It is the address toward which
13478 replies (and often, future unrelated correspondence) will be directed,
13479 unless you have <A HREF="h_config_custom_hdrs">defined an optional
13480 "Reply-To:" header</A> in the SETUP CONFIGURATION screen. Make
13481 sure this address is correct.
13482 <P>
13483 For help with message header editing
13484 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13485 <P>
13486 <UL>
13487 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13488 </UL>
13489 <P>
13490 <UL>
13491 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13492 </UL><P>
13493 <End of help on this topic>
13494 </BODY>
13495 </HTML>
13496 ======= h_composer_reply_to =======
13497 <HTML>
13498 <HEAD>
13499 <TITLE>THE MESSAGE COMPOSER'S REPLY-TO FIELD</TITLE>
13500 </HEAD>
13501 <BODY>
13502 <H1>THE MESSAGE COMPOSER'S REPLY-TO FIELD</H1>
13504 Most people should not need this header. The Reply-To: header is used in
13505 cases where you would like replies to your messages to be directed to an
13506 address other than your normal "From:" address. This is atypical,
13507 but can happen when you use multiple machines and do not have the same account
13508 name on each one, or when you wish to direct certain replies to accounts
13509 or folders designated for specific classes of correspondence.
13510 <P>
13511 For help with message header editing
13512 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13513 <P>
13514 <UL>
13515 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13516 </UL>
13518 <P>
13519 <UL>
13520 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13521 </UL><P>
13522 <End of help on this topic>
13523 </BODY>
13524 </HTML>
13525 ======= h_composer_custom_addr ====
13526 <HTML>
13527 <HEAD>
13528 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
13529 </HEAD>
13530 <BODY>
13531 <H1>CUSTOMIZED HEADER FIELD</H1>
13532 This is a customized header, i.e. not one that is part of Alpine's normal
13533 set of Compose headers.
13534 <P>
13535 For help with message header editing
13536 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13537 <P>
13538 <UL>
13539 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13540 </UL>
13541 <P>
13542 <UL>
13543 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13544 </UL><P>
13545 <End of help on this topic>
13546 </BODY>
13547 </HTML>
13548 ======= h_composer_custom_free ====
13549 <HTML>
13550 <HEAD>
13551 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
13552 </HEAD>
13553 <BODY>
13554 <H1>CUSTOMIZED HEADER FIELD</H1>
13555 This is a customized header, i.e. not one that is part of Alpine's normal
13556 set of Compose headers.
13557 <P>
13558 This field consists of arbitrary text.
13559 <P>
13560 For help with message header editing
13561 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13562 <P>
13563 <UL>
13564 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13565 </UL><P>
13566 <End of help on this topic>
13567 </BODY>
13568 </HTML>
13569 ====== h_composer_news =====
13570 <HTML>
13571 <HEAD>
13572 <TITLE>THE MESSAGE COMPOSER'S NEWSGRPS LINE</TITLE>
13573 </HEAD>
13574 <BODY>
13575 <h1>THE MESSAGE COMPOSER'S NEWSGRPS LINE</h1>
13576 Use the newsgroups line to specify any and all USENET newsgroups to which
13577 your message should be posted. When composing a message from scratch, this
13578 line may be hidden. If so, just press the rich headers command
13579 (<!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif-->)
13580 to make it visible.
13581 <P>
13582 <EM>Be aware</EM> that when you post to a newsgroup thousands of
13583 people will be reading your message. Also, you or your system manager
13584 must have defined an "<!--#echo var="VAR_nntp-server"-->" in your Alpine configuration
13585 in order for you to be able to post.
13586 <P>
13587 For help with message header editing
13588 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13589 <P><UL>
13590 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13591 </UL>
13592 <P>
13593 <End of help on this topic>
13594 </BODY>
13595 </HTML>
13596 ======= h_composer_fcc ====
13597 <HTML>
13598 <HEADER>
13599 <TITLE>THE MESSAGE COMPOSER'S FCC FIELD</TITLE>
13600 </HEADER>
13601 <BODY>
13602 <H1>THE MESSAGE COMPOSER'S FCC FIELD</H1>
13603 The FCC (File Carbon Copy) specifies the folder used to keep a copy of
13604 each outgoing message. The default value can be configured with the
13605 "<!--#echo var="VAR_default-fcc"-->" and "<!--#echo var="VAR_fcc-name-rule"-->" options. You can change or remove
13606 the file carbon copy on any message you send by editing the FCC header.<p>
13608 You may type ^T to get a list of all your folders and select one to use as
13609 the FCC for this message.<P>
13611 For help with message header editing
13612 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13613 <P>
13614 <UL>
13615 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13616 </UL><P>
13617 <End of help on this topic>
13618 </BODY>
13619 </HTML>
13620 ======= h_composer_subject ====
13621 <HTML>
13622 <HEADER>
13623 <TITLE>THE MESSAGE COMPOSER'S SUBJECT FIELD</TITLE>
13624 </HEADER>
13625 <BODY>
13626 <H1>THE MESSAGE COMPOSER'S SUBJECT FIELD</H1>
13628 The subject header provides a place to enter a few words that summarize
13629 the topic of the message you are sending. You may leave this line blank,
13630 but it is considered a courtesy to use a meaningful subject.<p>
13632 For help with message header editing
13633 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13634 <P>
13635 <UL>
13636 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13637 </UL><P>
13638 <End of help on this topic>
13639 </BODY>
13640 </HTML>
13641 ======= h_composer_attachment ====
13642 <HTML>
13643 <HEAD>
13644 <TITLE>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</TITLE>
13645 </HEAD>
13646 <BODY>
13647 <H1>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</H1>
13649 The "Attchmnt:" field is where you specify what file or
13650 files you'd like attached to
13651 the message you are composing. Those files must reside on the machine
13652 running Alpine. If your file is on a PC or Mac and you run Alpine with an
13653 account on a Unix machine, you'll have to transfer it before attaching it.
13654 Contact local computer support people for assistance with transferring.
13656 <P>
13657 The file name
13658 given can be an absolute file path name for your system
13659 <!--chtml if pinemode="os_windows"-->
13660 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
13661 with a relative pathname, or simply a file name without
13662 drive or directory specification.
13663 <!--chtml else-->
13664 (for example, "/tmp/exported.earlier" on Unix hosts),
13665 a file in your home directory, or a file path relative to your
13666 home directory. In Unix Alpine, you may use "~" to refer to
13667 your home directory or "~user" to refer to another
13668 account's home directory.
13669 <!--chtml endif--><P>
13670 No wild card characters may be used.
13671 <P>If the
13672 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13673 feature is set, names are relative to your current working directory
13674 <!--chtml if pinemode="running"-->
13675 (which, at least for your current Alpine "session,"
13676 is "<!--#echo var="CURRENT_DIR"-->")
13677 <!--chtml endif-->
13678 rather than your home directory
13679 <!--chtml if pinemode="running"-->
13680 (which, in the present configuration of your system, is
13681 "<!--#echo var="HOME_DIR"-->")
13682 <!--chtml endif-->
13683 .
13684 <P>
13685 Alpine uses MIME encoding for attachments, so binaries and files of any
13686 length can safely be delivered to any MIME-capable mail reading program.
13687 If you send an attachment to someone who does not have a MIME-capable mail
13688 reading program yet, then the main message text will be readable, but
13689 attachments (even attachments that are just plain text) are not.
13690 <P>
13692 Typing the filename on the Attchmnt: line achieves the same
13693 result as using the
13694 <!--chtml if pinemode="function_key"-->
13695 F6
13696 <!--chtml else-->
13697 Ctrl-J
13698 <!--chtml endif--> command.
13699 <P>
13701 If you Forward a message with attachments, you may delete them from your
13702 Forwarded message by editing the Attchmnt header line.
13703 <P>
13705 For help with message header editing
13706 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13707 <P>
13708 <UL>
13709 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13710 </UL><P>
13711 <End of help on this topic>
13712 </BODY>
13713 </HTML>
13714 ======= h_composer_ctrl_j ====
13715 <HTML>
13716 <HEAD>
13717 <TITLE>COMPOSER ATTACH</TITLE>
13718 </HEAD>
13719 <BODY>
13720 After the
13721 <!--chtml if pinemode="function_key"-->
13722 F6
13723 <!--chtml else-->
13724 Ctrl-J
13725 <!--chtml endif--> command:
13726 At the "File to attach:" prompt, enter the name of the
13727 existing file to attach to your message.
13728 When the feature
13729 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
13730 is set
13731 you need only enter the beginning of the filename (enough of it to uniquely
13732 identify the file) and press TAB to complete it.
13734 Or, press ^T to use the BROWSER screen for
13735 selecting the file. <P>
13736 For more information on attaching files, see the help screen for the
13737 composer's
13738 <A HREF="h_composer_attachment">Attchmnt: field</A>, which is normally hidden,
13739 but can be revealed using the
13740 <!--chtml if pinemode="function_key"-->
13741 F5
13742 <!--chtml else-->
13743 Ctrl-R
13744 <!--chtml endif-->
13745 command with the cursor positioned above the
13746 "----- Message Text -----" line in the COMPOSE MESSAGE screen.
13747 <P>
13748 <End of help on this topic>
13749 </BODY>
13750 </HTML>
13751 ======= h_edit_nav_cmds =========
13752 <HTML>
13753 <HEAD>
13754 <TITLE>Composer Editing Commands Explained</TITLE>
13755 </HEAD>
13756 <BODY>
13757 <H1>EDITING and NAVIGATION COMMANDS</H1>
13758 <!--chtml if pinemode="function_key"-->
13759 <PRE>
13760 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
13761 ^B (Left Arrow) Back character | ^D Delete current character
13762 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
13763 ^P (Up Arrow) Previous line |
13764 ^N (Down Arrow) Next line | F9 Cut marked text or
13765 ^A Beginning of line | delete current line
13766 ^E End of line | F10 Undelete line(s)
13767 F7 Previous page |
13768 F8 Next page |-------------------------------------
13769 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
13770 ----------------------------------------|
13771 EXIT COMMANDS | GENERAL COMMANDS | F12 To Addressbook
13772 F3 Cancel | F1 Get help | F12 RichView (expand lists)
13773 F2 eXit/save | ^Z Suspend | ^L Redraw Screen
13774 </PRE>
13775 <!--chtml else-->
13776 <PRE>
13777 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
13778 ^B (Left Arrow) Back character | ^D Delete current character
13779 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
13780 ^P (Up Arrow) Previous line |
13781 ^N (Down Arrow) Next line | ^K Cut marked text or
13782 ^A Beginning of line | delete current line
13783 ^E End of line | ^U Undelete line(s)
13784 ^Y Previous page |
13785 ^V Next page |-------------------------------------
13786 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
13787 ----------------------------------------|
13788 EXIT COMMANDS | GENERAL COMMANDS | ^T To Addressbook
13789 ^C Cancel | ^G Get help | ^R RichView (expand lists)
13790 ^X eXit/save | ^Z Suspend | ^L Redraw Screen
13791 </PRE>
13792 <!--chtml endif-->
13793 <End of help on this topic>
13794 </BODY>
13795 </HTML>
13796 ===== h_composer_sigedit =====
13797 <HTML>
13798 <HEAD>
13799 <TITLE>Signature Editor Commands Explained</TITLE>
13800 </HEAD>
13801 <BODY>
13802 <H1>SIGNATURE EDITOR COMMANDS</H1>
13803 <!--chtml if pinemode="function_key"-->
13804 <PRE>
13805 CURSOR MOTION KEYS |EDITING KEYS
13806 ^B (Left Arrow) Back character | ^D Delete current character
13807 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
13808 ^P (Up Arrow) Previous line | ^^ Set a mark
13809 ^N (Down Arrow) Next line | F9 Cut marked text or
13810 ^A Beginning of line | delete current line
13811 ^E End of line | F10 Paste text, undelete lines
13812 F7 Previous page | cut with ^K, or unjustify
13813 F8 Next page |-------------------------------------
13814 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
13815 ---------------------------------------| F6 Whereis (search for string)
13816 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
13817 F3 Cancel | F1 Get help | F4 Justify paragraph
13818 | ^Z Suspend | ^L Redraw Screen
13819 F2 Send | F6 Alt. editor | F5 Read in a file
13820 </PRE>
13821 <!--chtml else-->
13822 <PRE>
13823 CURSOR MOTION KEYS |EDITING KEYS
13824 ^B (Left Arrow) Back character | ^D Delete current character
13825 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
13826 ^P (Up Arrow) Previous line | ^^ Set a mark
13827 ^N (Down Arrow) Next line | ^K Cut marked text or
13828 ^A Beginning of line | delete current line
13829 ^E End of line | ^U Paste text, undelete lines
13830 ^Y Previous page | cut with ^K, or unjustify
13831 ^V Next page |-------------------------------------
13832 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
13833 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
13834 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
13835 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
13836 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
13837 ^X Send | ^_ Alt. editor | ^R Read in a file
13838 </PRE>
13839 <!--chtml endif-->
13841 NOTE: The presence or absence of the following commands is determined
13842 by "Feature-List" options in your Alpine configuration. Also,
13843 some of these commands may be administratively disabled by your system
13844 manager; if they don't work, please check with your local help desk
13845 before reporting a bug.
13846 <P>
13847 <UL>
13848 <LI>Suspend (suspends Alpine and gives a system prompt)
13849 <LI>Alternate editor (allows you to compose with your own editor)
13850 </UL>
13851 <P>
13853 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
13854 Ctrl-\, ESC
13855 <P>
13857 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
13858 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
13859 <P>
13860 <End of help on this topic>
13861 </BODY>
13862 </HTML>
13863 ===== h_composer_commentedit =====
13864 <HTML>
13865 <HEAD>
13866 <TITLE>Comment Editor Commands Explained</TITLE>
13867 </HEAD>
13868 <BODY>
13869 <H1>COMMENT EDITOR COMMANDS</H1>
13870 <!--chtml if pinemode="function_key"-->
13871 <PRE>
13872 CURSOR MOTION KEYS |EDITING KEYS
13873 ^B (Left Arrow) Back character | ^D Delete current character
13874 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
13875 ^P (Up Arrow) Previous line | ^^ Set a mark
13876 ^N (Down Arrow) Next line | F9 Cut marked text or
13877 ^A Beginning of line | delete current line
13878 ^E End of line | F10 Paste text, undelete lines
13879 F7 Previous page | cut with ^K, or unjustify
13880 F8 Next page |-------------------------------------
13881 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
13882 ---------------------------------------| F6 Whereis (search for string)
13883 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
13884 F3 Cancel | F1 Get help | F4 Justify paragraph
13885 | ^Z Suspend | ^L Redraw Screen
13886 F2 Send | F6 Alt. editor | F5 Read in a file
13887 </PRE>
13888 <!--chtml else-->
13889 <PRE>
13890 CURSOR MOTION KEYS |EDITING KEYS
13891 ^B (Left Arrow) Back character | ^D Delete current character
13892 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
13893 ^P (Up Arrow) Previous line | ^^ Set a mark
13894 ^N (Down Arrow) Next line | ^K Cut marked text or
13895 ^A Beginning of line | delete current line
13896 ^E End of line | ^U Paste text, undelete lines
13897 ^Y Previous page | cut with ^K, or unjustify
13898 ^V Next page |-------------------------------------
13899 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
13900 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
13901 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
13902 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
13903 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
13904 ^X Send | ^_ Alt. editor | ^R Read in a file
13905 </PRE>
13906 <!--chtml endif-->
13908 NOTE: The presence or absence of the following commands is determined
13909 by "Feature-List" options in your Alpine configuration. Also,
13910 some of these commands may be administratively disabled by your system
13911 manager; if they don't work, please check with your local help desk
13912 before reporting a bug.
13913 <P>
13914 <UL>
13915 <LI>Suspend (suspends Alpine and gives a system prompt)
13916 <LI>Alternate editor (allows you to compose with your own editor)
13917 </UL>
13918 <P>
13920 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
13921 Ctrl-\, ESC
13922 <P>
13924 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
13925 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
13926 <P>
13927 <End of help on this topic>
13928 </BODY>
13929 </HTML>
13930 ======= h_composer_abook_nick =======
13931 <HTML>
13932 <HEAD>
13933 <TITLE>Addressbook Nickname Explained</TITLE>
13934 </HEAD>
13935 <BODY>
13936 This is a short nickname for this address book entry. If it is used in
13937 place of an address from the composer, the composer will fill in the
13938 address(es) for the entry that matches the nickname.
13939 <P>
13941 Look <A HREF="h_edit_nav_cmds">here</A>
13942 to see the available Editing and Navigation commands.
13943 <P>
13944 <End of help on this topic>
13945 </BODY>
13946 </HTML>
13947 ======= h_composer_abook_full =======
13948 <HTML>
13949 <HEAD>
13950 <TITLE>Addressbook Fullname Explained</TITLE>
13951 </HEAD>
13952 <BODY>
13953 This is the full name field for this entry. If this is going to be a
13954 distribution list (more than one address), it should be a descriptive
13955 phrase describing the list. It will be included in the mail header if you
13956 put the list in the To: or CC: field, or in the To: line if you put the
13957 list in the Lcc: field. It's OK to leave this field blank (and OK to
13958 leave any of the other fields blank, too). If this address book entry is
13959 going to be a simple entry with just one address, then this field is the
13960 person's name. When you send mail to this entry, this is the field to the
13961 left of the brackets. That is, it is the most readable part of the
13962 address. For example, in the sample address:
13963 <PRE>
13964 John Doe <jdoe@some.domain>
13965 </PRE>
13966 "John Doe" is the full name field. If you are sorting your address book
13967 with one of the options that uses full names, then it might be useful to
13968 enter the full name as "Last, First", for example:
13969 <PRE>
13970 Doe, John
13971 </PRE>
13972 so that it will be sorted using Doe instead of John. This will be changed
13973 back into John Doe when you use it.
13974 <P>
13975 Look <A HREF="h_edit_nav_cmds">here</A>
13976 to see the available Editing and Navigation commands.
13977 <P>
13978 <End of help on this topic>
13979 </BODY>
13980 </HTML>
13981 ======= h_composer_abook_fcc =======
13982 <HTML>
13983 <HEAD>
13984 <TITLE>Addressbook Fcc Explained</TITLE>
13985 </HEAD>
13986 <BODY>
13987 If this entry is the first one in the To: line of an outgoing message,
13988 this field will be used for the Fcc (File Carbon Copy) instead of whatever
13989 you would normally get (which depends on which
13990 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
13991 you've chosen).
13992 <P>
13993 If this field consists of two double quotes ("") that tells Alpine
13994 that you don't want any Fcc associated with this entry.
13995 <P>
13996 Look <A HREF="h_edit_nav_cmds">here</A>
13997 to see the available Editing and Navigation commands.
13998 <P>
13999 <End of help on this topic>
14000 </BODY>
14001 </HTML>
14002 ====== h_config_combined_abook_display =====
14003 <HTML>
14004 <HEAD>
14005 <TITLE>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></TITLE>
14006 </HEAD>
14007 <BODY>
14008 <H1>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></H1>
14010 This feature affects the address book display screens.
14011 Normally, expanding an address book from the ADDRESS BOOK LIST screen
14012 will cause the remaining address books and directory servers to disappear
14013 from the screen, leaving only the entries of the expanded address book.
14014 If this feature is set, then the other address books will remain on the screen,
14015 so that all of the address books can be present at once.
14017 <P>
14018 The way that commands work won't be changed.
14019 For example, the Select All command will select all of the entries in the
14020 current address book, not all of the entries in all of the address books.
14021 The WhereIs command will change a little.
14022 It will search through all of the text on the screen plus all of the entries
14023 from expanded address books.
14025 <P>
14026 When this feature is set, the setting of the feature
14027 <A HREF="h_config_expanded_addrbooks">"<!--#echo var="FEAT_expanded-view-of-addressbooks"-->"</A>
14028 has an effect.
14029 <P>
14030 <End of help on this topic>
14031 </BODY>
14032 </HTML>
14033 ====== h_config_titlebar_color_style =====
14034 <HTML>
14035 <HEAD>
14036 <TITLE>OPTION: <!--#echo var="VAR_titlebar-color-style"--></TITLE>
14037 </HEAD>
14038 <BODY>
14039 <H1>OPTION: <!--#echo var="VAR_titlebar-color-style"--></H1>
14041 This option affects the colors used to display the titlebar (the top
14042 line on the screen) when viewing a message.
14044 <P>
14045 The available options include:
14046 <P>
14048 <DL>
14049 <DT>default</DT>
14050 <DD>The color of the titlebar will be the color you set for the
14051 <A HREF="h_config_title_color">Title Color</A>.
14052 The Title Color may be set by using the
14053 <A HREF="h_color_setup">Setup Kolor</A> screen.
14054 </DD>
14056 <DT>indexline</DT>
14057 <DD>The color of the titlebar will be the same as the color of the
14058 index line corresponding to the message being viewed.
14059 The rules that determine what color the index line will be may be set
14060 up by going to the Setup/Rules/Indexcolor screen.
14061 If the index line for a message is not colored explicitly by the
14062 Indexcolor rules, then the titlebar will be colored the same as for
14063 the "default" option above (which is not the same color that
14064 the index line itself will have).
14065 </DD>
14067 <DT>reverse-indexline</DT>
14068 <DD>This is similar to the "indexline" option except the
14069 foreground and background colors from the corresponding index line will
14070 be reversed.
14071 For example, if the index line color is red letters on a white background,
14072 then the titlebar will be white letters on a red background.
14073 If the index line for a message is not colored explicitly by the
14074 Indexcolor rules, then the titlebar will be colored the same as for
14075 the "default" option above (which is not the same color that
14076 the index line itself will have).
14077 </DD>
14078 </DL>
14080 <P>
14082 <UL>
14083 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14084 </UL><P>
14085 <End of help on this topic>
14086 </BODY>
14087 </HTML>
14088 ====== h_config_index_color_style =====
14089 <HTML>
14090 <HEAD>
14091 <TITLE>OPTION: <!--#echo var="VAR_current-indexline-style"--></TITLE>
14092 </HEAD>
14093 <BODY>
14094 <H1>OPTION: <!--#echo var="VAR_current-indexline-style"--></H1>
14096 This option affects the colors used to display the current line in the
14097 MESSAGE INDEX screen.
14098 If you do not have Index Color Rules defined, then this option will
14099 have no effect in the index.
14100 Those Rules may be defined by going to the Setup/Rules/Indexcolor screen.
14101 <P>
14102 If the option
14103 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
14104 is turned on and the
14105 <A HREF="h_config_incunseen_color">Incoming Unseen Color</A>
14106 is set to something other than the default, then
14107 this option also affects the color used to display the current folder
14108 in the Incoming FOLDER LIST screen.
14110 <P>
14111 The available options include:
14112 <P>
14114 <DL>
14115 <DT>flip-colors</DT>
14116 <DD>This is the default.
14117 If an index line is colored because it matches one of your
14118 Index Color Rules, then its colors will be reversed when it is the currently
14119 highlighted line.
14120 For example, if the line is normally red text on a blue background, then
14121 when it is the current line it will be drawn as blue text on a red background.
14122 <P>
14123 The rest of the option values all revert to this flip-colors behavior if
14124 there is no Reverse Color defined.
14125 </DD>
14127 <DT>reverse</DT>
14128 <DD>With this option the Reverse color is always used to highlight the
14129 current line.
14130 </DD>
14132 <DT>reverse-fg</DT>
14133 <DD>The foreground part of the Reverse Color is used to highlight
14134 the current line.
14135 If this would cause the text to be unreadable (because the foreground and
14136 background colors are the same) or if it would cause no change in the
14137 color of the index line, then the colors are flipped instead.
14138 <P>
14139 Some people think this works particularly well if you use different
14140 background colors to emphasize "interesting" lines,
14141 but always with the same Normal foreground color,
14142 and you use a different foreground color for the Reverse Color.
14143 </DD>
14145 <DT>reverse-fg-no-ambiguity</DT>
14146 <DD>With the "reverse-fg" rule above, it is possible that
14147 the resulting color will be exactly the same as the regular Reverse
14148 Color.
14149 That can lead to some possible confusion because an
14150 "interesting"
14151 line that is the current line will be displayed exactly the same as a
14152 non-interesting line that is current.
14153 You can't tell whether the line is just a regular current line or if it is
14154 an "interesting" current line by looking at the color.
14155 Setting the option to this value removes that ambiguity.
14156 It is the same as the "reverse-fg" setting unless the resulting
14157 interesting current line would look just like a non-interesting current line.
14158 In that case, the interesting line's colors are simply flipped (like in the
14159 default behavior).
14160 <P>
14161 As an alternative way to preserve the line's interestingness in this case,
14162 you may find that using both a different foreground and a different
14163 background color for the interesting line will help.
14164 </DD>
14166 <DT>reverse-bg</DT>
14167 <DD>The background part of the Reverse Color is used to highlight
14168 the current line.
14169 If this would cause the text to be unreadable (because the foreground and
14170 background colors are the same) or if it would cause no change in the
14171 color of the index line, then the colors are flipped instead.
14172 <P>
14173 Some people think this works particularly well if you use different
14174 foreground colors to emphasize "interesting" lines,
14175 but always with the same Normal background color,
14176 and you use a different background color for the Reverse Color.
14177 </DD>
14179 <DT>reverse-bg-no-ambiguity</DT>
14180 <DD>As with the "reverse-fg" case, the "reverse-bg"
14181 rule may also result in a color that is exactly the same as the regular
14182 Reverse Color.
14183 Setting the option to this value removes that ambiguity.
14184 It is the same as the "reverse-bg" setting unless the resulting
14185 current line has the same color as the Reverse Color.
14186 In that case, the interesting line's colors are simply flipped (like in the
14187 default behavior).
14188 </DD>
14189 </DL>
14191 <P>
14193 <UL>
14194 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14195 </UL><P>
14196 <End of help on this topic>
14197 </BODY>
14198 </HTML>
14199 ====== h_config_expanded_addrbooks =====
14200 <HTML>
14201 <HEAD>
14202 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></TITLE>
14203 </HEAD>
14204 <BODY>
14205 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></H1>
14207 If multiple address books (either personal or global) are defined, and you
14208 wish to have them all expanded implicitly upon entering the ADDRESS BOOK
14209 screen, then set this feature. This feature will have no effect unless the
14210 feature
14211 <A HREF="h_config_combined_abook_display">"<!--#echo var="FEAT_combined-addrbook-display"-->"</A>
14212 is also set.
14213 <P>
14214 <End of help on this topic>
14215 </BODY>
14216 </HTML>
14217 ====== h_config_combined_folder_display =====
14218 <HTML>
14219 <HEAD>
14220 <TITLE>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></TITLE>
14221 </HEAD>
14222 <BODY>
14223 <H1>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></H1>
14225 This feature affects the folder list display screens.
14226 Normally, each folder list is viewed within its collection only. This
14227 command allows folder lists to be viewed within a single screen that
14228 combines the contents of all collections.
14230 <P>
14231 The way that commands work won't be changed.
14232 For example, the Select All command will select all of the folders in the
14233 current collection, not all of the entries in all of the collections.
14234 The WhereIs command will change a little.
14235 It will search through all of the folders in the current collection as well
14236 as all the folder in any other expanded collection.
14238 <P>
14239 When this feature is set, the setting of the feature
14240 <A HREF="h_config_expanded_folders">"<!--#echo var="FEAT_expanded-view-of-folders"-->"</A>
14241 has an effect.
14242 <P>
14243 <End of help on this topic>
14244 </BODY>
14245 </HTML>
14246 ====== h_config_combined_subdir_display =====
14247 <HTML>
14248 <HEAD>
14249 <TITLE>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></TITLE>
14250 </HEAD>
14251 <BODY>
14252 <H1>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></H1>
14254 This feature affects the Folder List screen when
14255 the
14256 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14257 feature is enabled. Normally, selecting a directory from the Folder
14258 List takes you into a new screen displaying only the contents of
14259 that directory.
14261 <P>
14262 Enabling this feature will cause the contents of the selected
14263 directory to be
14264 displayed within the boundaries of the "Collection" it
14265 is a part of. All previously displayed collections will remain
14266 in the screen.
14268 <P>
14269 The way that commands work won't be changed.
14270 For example, the Select All command will select all of the folders in the
14271 directory, as opposed to all of the entries in all of the collections.
14272 The WhereIs command will change a little.
14273 It will search through all of the folders in the current collection as well
14274 as all the folder in any other expanded collection.
14276 <P>
14277 <End of help on this topic>
14278 </BODY>
14279 </HTML>
14280 ====== h_config_separate_fold_dir_view =====
14281 <HTML>
14282 <HEAD>
14283 <TITLE>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></TITLE>
14284 </HEAD>
14285 <BODY>
14286 <H1>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></H1>
14288 This feature affects folder collections wherein a folder
14289 and directory can have the same name. By default, Alpine displays them
14290 only once, denoting that it is both a folder and directory by appending
14291 the folder name with the hierarchy character enclosed
14292 in square brackets.
14295 <P>
14296 Enabling this feature will cause Alpine to display such names
14297 separately marking the name representing a directory with a trailing
14298 hierarchy delimiter (typically the slash, "/", character).
14300 <P>
14301 The feature also alters the command set slightly. By default, the
14302 right-arrow descends into the directory, while hitting the Return key will
14303 cause the folder by that name to be opened.
14305 <P>
14306 With this feature set, the Return key will open the highlighted folder, or
14307 enter the highlighted directory.
14309 <P>
14310 <End of help on this topic>
14311 </BODY>
14312 </HTML>
14313 ====== h_config_expanded_folders =====
14314 <HTML>
14315 <HEAD>
14316 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></TITLE>
14317 </HEAD>
14318 <BODY>
14319 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></H1>
14321 If multiple folder collections are defined, and you
14322 wish to have them all expanded implicitly upon entering the FOLDER LIST
14323 screen, then set this feature. This feature will have no effect unless the
14324 feature
14325 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14326 is also set.
14327 <P>
14328 <End of help on this topic>
14329 </BODY>
14330 </HTML>
14331 ======= h_config_ldap_server =======
14332 <HTML>
14333 <HEAD>
14334 <TITLE>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
14335 </HEAD>
14336 <BODY>
14337 <H1>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
14338 This is the name of the host where an LDAP server is running.
14339 For redundancy, this may be a space-delimited set of server names, in which
14340 case the first server that answers is used.
14341 Each of the server names may be optionally followed by
14342 a colon and a port number.
14343 If this form is used then the port number configured below in the
14344 <EM>port</EM> field is not used.
14345 <P>
14346 To find out whether your organization has its own LDAP server,
14347 contact its computing support staff.
14348 <P><UL>
14349 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14350 </UL>
14351 <P>
14352 <End of help on this topic>
14353 </BODY>
14354 </HTML>
14355 ======= h_config_ldap_base =======
14356 <HTML>
14357 <HEAD>
14358 <TITLE>LDAP OPTION: Search-Base</TITLE>
14359 </HEAD>
14360 <BODY>
14361 <H1>LDAP OPTION: Search-Base</H1>
14363 This is the search base to be used on this server. It functions as a filter
14364 by restricting your searches in the LDAP server database
14365 to the specified contents of the specified fields. Without it, searches
14366 submitted to this directory server may fail. It might be something
14367 like:
14369 <PRE>
14370 O = <Your Organization Name>, C = US
14371 </PRE>
14372 or it might be blank.
14373 (Some LDAP servers actually ignore anything specified here.)
14374 <P>
14375 If in doubt what parameters you should specify here,
14376 contact the maintainers of the LDAP server.
14377 <P><UL>
14378 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14379 </UL>
14380 <P>
14381 <End of help on this topic>
14382 </BODY>
14383 </HTML>
14384 ======= h_config_ldap_port =======
14385 <HTML>
14386 <HEAD>
14387 <TITLE>LDAP OPTION: Port</TITLE>
14388 </HEAD>
14389 <BODY>
14390 <H1>LDAP OPTION: Port</H1>
14392 This is the TCP port number to be used with this LDAP server. If you leave
14393 this blank port 389 will be used.
14394 <P>
14395 <End of help on this topic>
14396 </BODY>
14397 </HTML>
14398 ======= h_config_ldap_nick =======
14399 <HTML>
14400 <HEAD>
14401 <TITLE>LDAP OPTION: Nickname</TITLE>
14402 </HEAD>
14403 <BODY>
14404 <H1>LDAP OPTION: Nickname</H1>
14406 This is a nickname to be used in displays. If you don't supply a
14407 nickname the server name
14408 (<A HREF="h_config_ldap_server">"<!--#echo var="VAR_ldap-servers"-->"</A>)
14409 will be used instead. This option is strictly for your convenience.
14410 <P>
14411 <End of help on this topic>
14412 </BODY>
14413 </HTML>
14414 ======= h_config_ldap_binddn =======
14415 <HTML>
14416 <HEAD>
14417 <TITLE>LDAP OPTION: Bind-DN</TITLE>
14418 </HEAD>
14419 <BODY>
14420 <H1>LDAP OPTION: Bind-DN</H1>
14422 You may need to authenticate to the LDAP server before you are able to use it.
14423 This is the Distinguished Name to bind to when authenticating to this server.
14424 Try leaving this blank until you know you need it.
14425 <P>
14426 Alpine only knows about LDAP Simple authentication.
14427 It does not attempt LDAP SASL authentication.
14428 The DN and password will be sent in the clear unless TLS encryption is
14429 being used on this connection.
14430 Because of this, you may want to set the LDAP feature
14431 <A HREF="h_config_ldap_opts_tls">"Attempt-TLS-On-Connection"</A>
14432 or the feature
14433 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
14434 if you are going to be providing a password.
14435 <P><UL>
14436 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14437 </UL>
14438 <P>
14439 <End of help on this topic>
14440 </BODY>
14441 </HTML>
14442 ======= h_config_ldap_opts_impl =======
14443 <HTML>
14444 <HEAD>
14445 <TITLE>LDAP FEATURE: Use-Implicitly-From-Composer</TITLE>
14446 </HEAD>
14447 <BODY>
14448 <H1>LDAP FEATURE: Use-Implicitly-From-Composer</H1>
14450 Set this to have lookups done to this server implicitly from the composer.
14451 If an address doesn't look like a fully-qualified address, it will be looked
14452 up in your address books, and if it doesn't match a nickname there, then it
14453 will be looked up on the LDAP servers that have this feature set.
14454 The lookups will also be done when using the address completion feature
14455 (TAB command) in the composer if any of the serves have this feature set.
14456 Also see the LDAP feature
14457 <A HREF="h_config_ldap_opts_rhs">"Lookup-Addrbook-Contents"</A>
14458 and the Setup/Config feature
14459 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
14460 <P>
14461 <End of help on this topic>
14462 </BODY>
14463 </HTML>
14464 ======= h_config_ldap_opts_tls =======
14465 <HTML>
14466 <HEAD>
14467 <TITLE>LDAP FEATURE: Attempt-TLS-On-Connection</TITLE>
14468 </HEAD>
14469 <BODY>
14470 <H1>LDAP FEATURE: Attempt-TLS-On-Connection</H1>
14472 When connecting to this server Alpine will attempt to use TLS encryption
14473 on the connection.
14474 Also see the closely related feature
14475 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
14476 <P>
14477 <End of help on this topic>
14478 </BODY>
14479 </HTML>
14480 ======= h_config_ldap_opts_tlsmust =======
14481 <HTML>
14482 <HEAD>
14483 <TITLE>LDAP FEATURE: Require-TLS-On-Connection</TITLE>
14484 </HEAD>
14485 <BODY>
14486 <H1>LDAP FEATURE: Require-TLS-On-Connection</H1>
14488 When connecting to this server Alpine will attempt to use TLS encryption
14489 on the connection.
14490 If the StartTLS operation fails then the connection will not be used.
14491 <P>
14492 <End of help on this topic>
14493 </BODY>
14494 </HTML>
14495 ====== h_config_ldap_opts_rhs =====
14496 <HTML>
14497 <HEAD>
14498 <TITLE>LDAP FEATURE: Lookup-Addrbook-Contents</TITLE>
14499 </HEAD>
14500 <BODY>
14501 <H1>LDAP FEATURE: Lookup-Addrbook-Contents</H1>
14503 Normally implicit LDAP lookups from the composer are done only for the
14504 strings you type in from the composer screen. In other words, you type in
14505 something in the To or CC field and press return, then the string is looked up.
14506 First that string is looked up in your address books. If a match is found
14507 there, then the results of that match are looked up again. If you place
14508 a string in your address book that you want to have looked up on the LDAP
14509 directory server, you need to turn on this feature. If you set this feature
14510 for a server, you almost always will also want to set the
14511 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
14512 feature. An example might serve to best illustrate this feature.
14513 <P>
14514 If an LDAP lookup of "William Clinton" normally returns an
14515 entry with an
14516 address of pres@whitehouse.gov, then you might put an entry in your address
14517 book that looks like:
14518 <P>
14519 <CENTER><SAMP>Nickname = bill</SAMP></CENTER><BR>
14520 <CENTER><SAMP>Address = "William Clinton"</SAMP></CENTER>
14521 <P>
14522 Now, when you type "bill" into an
14523 address field in the composer Alpine will
14524 find the "bill" entry in your address book.
14525 It will replace "bill" with
14526 "William Clinton".
14527 It will then search for an entry with that nickname
14528 in your address book and not find one. If this feature
14529 is set, Alpine will then attempt to lookup
14530 "William Clinton" on the LDAP server and find the entry with address
14531 pres@whitehouse.gov.
14532 <P>
14533 A better way to accomplish the same thing is probably to use the feature
14534 <A HREF="h_config_ldap_opts_ref">"Save-Search-Criteria-Not-Result"</A>.
14535 <P>
14536 <End of help on this topic>
14537 </BODY>
14538 </HTML>
14539 ====== h_config_ldap_opts_ref =====
14540 <HTML>
14541 <HEAD>
14542 <TITLE>LDAP FEATURE: Save-Search-Criteria-Not-Result</TITLE>
14543 </HEAD>
14544 <BODY>
14545 <H1>LDAP FEATURE: Save-Search-Criteria-Not-Result</H1>
14547 Normally when you save the results of an LDAP directory lookup to your
14548 address book the results of the lookup are saved. If this feature is set
14549 and the entry being saved was found on this directory server, then the
14550 search criteria is saved instead of the results of the search. When this
14551 address book entry is used in the future, instead of copying the results
14552 from the address book the directory lookup will be done again. This could
14553 be useful if the copied result might become stale because the data on
14554 the directory server changes (for example, the entry's email address changes).
14555 You probably don't want to set this feature if the server is at all slow or
14556 unreliable.
14557 <P>
14558 The way this actually works is that instead of saving the email address
14559 in your address book, Alpine saves enough information to look up the same
14560 directory entry again. In particular, it saves the server name and the
14561 distinguished name of the entry. It's possible that the server administrators
14562 might change the format of distinguished names on the server, or that the
14563 entry might be removed from the server. If Alpine notices this, you will be warned
14564 and a backup copy of the email address will be used. You may want to create
14565 a new entry in this case, since you will get the annoying warning every
14566 time you use the old entry. You may do that by Saving the entry to a new
14567 nickname in the same address book. You will be asked whether or not you
14568 want to use the backup email address.
14569 <P>
14570 A related feature in the Setup/Config screen is
14571 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
14572 <P>
14573 <End of help on this topic>
14574 </BODY>
14575 </HTML>
14576 ======= h_config_ldap_opts_nosub =======
14577 <HTML>
14578 <HEAD>
14579 <TITLE>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</TITLE>
14580 </HEAD>
14581 <BODY>
14582 <H1>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</H1>
14584 Spaces in your input are normally handled specially.
14585 Each space character is replaced
14586 by
14587 <P>
14588 <CENTER><SAMP>* <SPACE></SAMP></CENTER>
14589 <P>
14590 in the search query (but not by "* <SPACE> *").
14591 The reason this is done is so the input string
14592 <P>
14593 <CENTER><SAMP>Greg Donald</SAMP></CENTER>
14594 <P>
14595 (which is converted to "Greg* Donald") will match
14596 the names "Greg Donald",
14597 "Gregory Donald", "Greg F. Donald", and
14598 "Gregory F Donald"; but it won't match "Greg McDonald".
14599 If the "Search-Rule" you were using was "begins-with",
14600 then it would also match the name "Greg Donaldson".
14601 <P>
14602 Turning on this feature will disable this substitution.
14603 <P>
14604 <End of help on this topic>
14605 </BODY>
14606 </HTML>
14607 ====== h_config_ldap_searchtypes =======
14608 <HTML>
14609 <HEAD>
14610 <TITLE>LDAP OPTION: Search-Type</TITLE>
14611 </HEAD>
14612 <BODY>
14613 <H1>LDAP OPTION: Search-Type</H1>
14615 This affects the way that LDAP searches are done.
14616 In particular, this tells the server where to look for the string to be matched.
14617 If set to "name" then the string that is being searched for will
14618 be compared with the string in the
14619 "Name" field on the server
14620 (technically, it is the "commonname" field on the server).
14621 "Surname" means we're looking for a
14622 match in the "Surname" field on the
14623 server (actually the "sn" field).
14624 "Givenname" really is "givenname"
14625 and "email" is the electronic mail address (this is actually the field
14626 called "mail" or "electronicmail" on the server).
14627 The other three types are combinations of
14628 the types listed so far. "Name-or-email"
14629 means the string should appear
14630 in either the "name" field OR the "email" field.
14631 Likewise, "surname-or-givenname"
14632 means "surname" OR "givenname"
14633 and "sur-or-given-or-name-or-email" means the obvious thing.
14634 <P>
14635 This search TYPE is combined with the
14636 search <A HREF="h_config_ldap_searchrules">RULE</A>
14637 to form the actual search query.
14638 <P>
14639 The usual default value for this
14640 option is "sur-or-given-or-name-or-email".
14641 This type of search may be slow on some servers.
14642 Try "name-or-email", which is often
14643 faster, or just "name" if the performance seems to be a problem.
14644 <P>
14645 Some servers have been configured with different attribute names for
14646 these four fields.
14647 In other words, instead of using the attribute name "mail"
14648 for the email address field, the server might be configured to use something
14649 else, for example, "rfc822mail" or "internetemailaddress".
14650 Alpine can be configured to use these different attribute names by using
14651 the four configuration options:
14652 <P><UL>
14653 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
14654 </UL>
14655 <P><UL>
14656 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
14657 </UL>
14658 <P><UL>
14659 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
14660 </UL>
14661 <P><UL>
14662 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
14663 </UL>
14664 <P>
14665 <End of help on this topic>
14666 </BODY>
14667 </HTML>
14668 ====== h_config_ldap_searchrules =======
14669 <HTML>
14670 <HEAD>
14671 <TITLE>LDAP OPTION: Search-Rule</TITLE>
14672 </HEAD>
14673 <BODY>
14674 <H1>LDAP OPTION: Search-Rule</H1>
14676 This affects the way that LDAP searches are done.
14677 If set to "equals" then
14678 only exact matches count.
14679 "Contains" means that the string you type in
14680 is a substring of what you are matching against.
14681 "Begins-with" and "ends-with"
14682 mean that the string starts or ends with the string you type in.
14683 <P>
14684 Spaces in your input are normally handled specially, but you can turn that
14685 special handling off with the
14686 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
14687 feature.
14688 <P>
14689 The usual default value for this option is "begins-with".
14690 <P>
14691 <End of help on this topic>
14692 </BODY>
14693 </HTML>
14694 ======= h_config_ldap_email_attr =======
14695 <HTML>
14696 <HEAD>
14697 <TITLE>LDAP OPTION: EmailAttribute</TITLE>
14698 </HEAD>
14699 <BODY>
14700 <H1>LDAP OPTION: EmailAttribute</H1>
14702 This is the name of the attribute that is searched for when looking for
14703 an email address. The default value for this option is "mail" or
14704 "electronicmail".
14705 If the server you are using uses a different attribute name for the email
14706 address, put that attribute name here.
14707 <P>
14708 This will affect the search filter used if your Search-Type is one that
14709 contains a search for "email".
14710 It will also cause the attribute value matching this attribute name to be used
14711 as the email address when you look up an entry from the composer.
14712 <P>
14713 <End of help on this topic>
14714 </BODY>
14715 </HTML>
14716 ======= h_config_ldap_sn_attr =======
14717 <HTML>
14718 <HEAD>
14719 <TITLE>LDAP OPTION: SurnameAttribute</TITLE>
14720 </HEAD>
14721 <BODY>
14722 <H1>LDAP OPTION: SurnameAttribute</H1>
14724 This is the name of the attribute that is searched for when looking for
14725 the surname of the entry. The default value for this option is "sn".
14726 If the server you are using uses a different attribute name for the surname,
14727 put that attribute name here.
14728 This will affect the search filter used if your Search-Type is one that
14729 contains a search for "surname".
14730 <P>
14731 <End of help on this topic>
14732 </BODY>
14733 </HTML>
14734 ======= h_config_ldap_gn_attr =======
14735 <HTML>
14736 <HEAD>
14737 <TITLE>LDAP OPTION: GivennameAttribute</TITLE>
14738 </HEAD>
14739 <BODY>
14740 <H1>LDAP OPTION: GivennameAttribute</H1>
14742 This is the name of the attribute that is searched for when looking for
14743 the given name of the entry. The default value for this option is "givenname".
14744 If the server you are using uses a different attribute name for the given name,
14745 put that attribute name here.
14746 This will affect the search filter used if your Search-Type is one that
14747 contains a search for "givenname".
14748 <P>
14749 <End of help on this topic>
14750 </BODY>
14751 </HTML>
14752 ======= h_config_ldap_cn_attr =======
14753 <HTML>
14754 <HEAD>
14755 <TITLE>LDAP OPTION: NameAttribute</TITLE>
14756 </HEAD>
14757 <BODY>
14758 <H1>LDAP OPTION: NameAttribute</H1>
14760 This is the name of the attribute that is searched for when looking for
14761 the name of the entry. The default value for this option is "cn", which
14762 stands for common name.
14763 If the server you are using uses a different attribute name for the name,
14764 put that attribute name here.
14765 This will affect the search filter used if your Search-Type is one that
14766 contains a search for "name".
14767 <P>
14768 <End of help on this topic>
14769 </BODY>
14770 </HTML>
14771 ======= h_config_ldap_time =======
14772 <HTML>
14773 <HEAD>
14774 <TITLE>LDAP OPTION: Timelimit</TITLE>
14775 </HEAD>
14776 <BODY>
14777 <H1>LDAP OPTION: Timelimit</H1>
14779 This places a limit on the number of seconds the LDAP search will continue.
14780 The default is 30 seconds. A value of 0 means no limit. Note that some servers
14781 may place limits of their own on searches.
14782 <P>
14783 <End of help on this topic>
14784 </BODY>
14785 </HTML>
14786 ======= h_config_ldap_size =======
14787 <HTML>
14788 <HEAD>
14789 <TITLE>LDAP OPTION: Sizelimit</TITLE>
14790 </HEAD>
14791 <BODY>
14792 <H1>LDAP OPTION: Sizelimit</H1>
14794 This places a limit on the number of entries returned by the LDAP server.
14795 A value of 0 means no limit. The default is 0. Note that some servers
14796 may place limits of their own on searches.
14797 <P>
14798 <End of help on this topic>
14799 </BODY>
14800 </HTML>
14801 ======= h_config_ldap_cust =======
14802 <HTML>
14803 <HEAD>
14804 <TITLE>LDAP OPTION: Custom-Search-Filter</TITLE>
14805 </HEAD>
14806 <BODY>
14807 <H1>LDAP OPTION: Custom-Search-Filter</H1>
14809 This one is for advanced users only! If you define this, then the
14810 "Search-Type" and "Search-Rule" defined are both ignored.
14811 However, the feature
14812 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
14813 is still in effect.
14814 That is, the space substitution will take place even in a custom filter unless
14815 you disable it.
14816 <P>
14817 If your LDAP service stops working and you suspect it might be because
14818 of your custom filter, just delete this filter and try using the
14819 "Search-Type" and "Search-Rule" instead.
14820 Another option that sometimes causes trouble is the
14821 <A HREF="h_config_ldap_base">"Search-Base"</A> option.
14822 <P>
14823 This variable may be set to the string representation of an LDAP search
14824 filter (see RFC1960). In the places where you want the address string to be
14825 substituted in, put a '%s' in this filter string. Here are some examples:
14826 <P>
14827 A "Search-Type" of "name" with "Search-Rule" of "begins-with"
14828 is equivalent to the "Custom-Search-Filter"
14829 <PRE>
14830 (cn=%s*)
14831 </PRE>
14832 When you try to match against the string "string" the program replaces
14833 the "%s" with "string" (without the quotes). You may have multiple "%s"'s and
14834 they will all be replaced with the string. There is a limit of 10 "%s"'s.
14835 <P>
14836 A "Search-Type" of "name-or-email" with "Search-Rule"
14837 of "contains" is equivalent to
14838 <PRE>
14839 (|(cn=*%s*)(mail=*%s*))
14840 </PRE>
14841 <P>
14842 If your server uses a different attribute <EM>name</EM> than
14843 Alpine uses by default,
14844 (for example, it uses "rfc822mail" instead of "mail"),
14845 then you may be able to use one or more of the four attribute configuration
14846 options instead of defining a custom filter:
14847 <P><UL>
14848 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
14849 </UL>
14850 <P><UL>
14851 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
14852 </UL>
14853 <P><UL>
14854 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
14855 </UL>
14856 <P><UL>
14857 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
14858 </UL>
14859 <P>
14860 <End of help on this topic>
14861 </BODY>
14862 </HTML>
14863 ======= h_composer_abook_comment =======
14864 <HTML>
14865 <HEAD>
14866 <TITLE>Addressbook Comment Explained</TITLE>
14867 </HEAD>
14868 <BODY>
14869 This is a comment to help you remember what this entry is. The WhereIs
14870 command searches comments so that it is easier to find an entry with a comment
14871 you know about attached to it. This field is not used in the outgoing message.
14872 <P>
14873 Look <A HREF="h_edit_nav_cmds">here</A>
14874 to see the available Editing and Navigation commands.
14875 <P>
14876 <End of help on this topic>
14877 </BODY>
14878 </HTML>
14879 ======= h_composer_abook_addrs =======
14880 <HTML>
14881 <HEAD>
14882 <TITLE>Addressbook Lists</TITLE>
14883 </HEAD>
14884 <BODY>
14885 <H1>Addressbook Lists</H1>
14887 This is a list of addresses to send to when sending to this address book
14888 entry. Each member of the list may be an address or another nickname from
14889 any of your address books. If it is an address, it is OK to include the
14890 full name field as well as the electronic address portion of that address.
14891 For example, the following are all legitimate entries in this field:
14893 <DL><DT> </DT>
14894 <DD>john (a nickname in your address book)
14895 <DD>jdoe@some.domain
14896 <DD>John Doe <jdoe@some.domain>
14897 </DL>
14899 The addresses should be listed separated by commas, just like you would
14900 enter them from the composer.
14902 <P>
14904 The only difference between a distribution list and a simple entry with a
14905 single address, is that a distribution list has more than one address
14906 listed in the Addresses: field, whereas a simple personal entry has just
14907 one address.
14909 <P>
14911 For individual address book entries, if there is a full name in the
14912 Fullname: field (filling in the Fullname: field is not required), it is
14913 used. If the full name is specified in the Address: field and not in the
14914 Fullname: field, then the full name from the Address: field is used.
14916 <P>
14918 If you type the nickname of a distribution list from one of your address
14919 books in the Lcc: field, then the full name of that list is used in the
14920 To: field. If you put a list in the To: or Cc: fields, that list will be
14921 expanded into all of its addresses. If the list has a full name, then
14922 that will appear at the beginning of the addresses.
14924 <DL><DT> </DT>
14925 <DD>Sewing Club <john@somewhere>, nancy@something.else, Sal
14926 <sal@here.there>
14927 </DL>
14929 If the first address in the distribution list also has a full name, then
14930 the list full name and that full name are combined into something like the
14931 following:
14933 <DL><DT> </DT>
14934 <DD>Sewing Club -- John Smith <john@somewhere>
14935 </DL>
14938 If you specify a list via Lcc, the full name is used in the To: line. If
14939 you specify a list in the To: or Cc: fields, then it uses the same method
14940 as for individual entries for filling in the full name.
14942 <P>
14944 For help with editing and navigation commands, check the Help for the
14945 Nickname: field.
14947 <P>
14948 <End of help on this topic>
14949 </BODY>
14950 </HTML>
14951 ======= h_config_role_nick =======
14952 <HTML>
14953 <HEAD>
14954 <TITLE>Nickname Explained</TITLE>
14955 </HEAD>
14956 <BODY>
14957 <H1>Nickname Explained</H1>
14959 This is a nickname to help you.
14960 You should have a different nickname for each role you define.
14961 The nickname will be used in the SETUP ROLE RULES screen to allow you to
14962 pick a role to edit.
14963 It will also be used when you send a message to let you know you are
14964 sending with a different role than you use by default, and
14965 it will be useful for choosing a role when composing with the Role command
14966 or when composing with one of the Role Uses set to With Confirmation.
14967 This field is not used in the outgoing message.
14968 <P>
14969 Look <A HREF="h_edit_nav_cmds">here</A>
14970 to see the available Editing and Navigation commands.
14971 <P>
14972 <End of help on this topic>
14973 </BODY>
14974 </HTML>
14975 ======= h_config_role_comment =======
14976 <HTML>
14977 <HEAD>
14978 <TITLE>Comment Explained</TITLE>
14979 </HEAD>
14980 <BODY>
14981 <H1>Comment Explained</H1>
14983 This is a comment to help you.
14984 This comment does not play any functional role, it is simply an optional
14985 comment to help you remember what the rule is for.
14986 <P>
14987 Look <A HREF="h_edit_nav_cmds">here</A>
14988 to see the available Editing and Navigation commands.
14989 <P>
14990 <End of help on this topic>
14991 </BODY>
14992 </HTML>
14993 ======= h_config_other_nick =======
14994 <HTML>
14995 <HEAD>
14996 <TITLE>Nickname Explained</TITLE>
14997 </HEAD>
14998 <BODY>
14999 <H1>Nickname Explained</H1>
15001 This is a nickname to help you.
15002 You should have a different nickname for each rule you define.
15003 The nickname will be used in the SETUP OTHER RULES screen to allow you to
15004 pick a rule to edit.
15005 <P>
15006 Look <A HREF="h_edit_nav_cmds">here</A>
15007 to see the available Editing and Navigation commands.
15008 <P>
15009 <End of help on this topic>
15010 </BODY>
15011 </HTML>
15012 ======= h_config_score_nick =======
15013 <HTML>
15014 <HEAD>
15015 <TITLE>Nickname Explained</TITLE>
15016 </HEAD>
15017 <BODY>
15018 <H1>Nickname Explained</H1>
15020 This is a nickname to help you.
15021 You should have a different nickname for each scoring rule you define.
15022 The nickname will be used in the SETUP SCORING RULES screen to allow you to
15023 pick a rule to edit.
15024 <P>
15025 Look <A HREF="h_edit_nav_cmds">here</A>
15026 to see the available Editing and Navigation commands.
15027 <P>
15028 <End of help on this topic>
15029 </BODY>
15030 </HTML>
15031 ======= h_config_incol_nick =======
15032 <HTML>
15033 <HEAD>
15034 <TITLE>Nickname Explained</TITLE>
15035 </HEAD>
15036 <BODY>
15037 <H1>Nickname Explained</H1>
15039 This is a nickname to help you.
15040 You should have a different nickname for each color rule you define.
15041 The nickname will be used in the SETUP INDEX COLOR RULES screen to allow you to
15042 pick a rule to edit.
15043 <P>
15044 Look <A HREF="h_edit_nav_cmds">here</A>
15045 to see the available Editing and Navigation commands.
15046 <P>
15047 <End of help on this topic>
15048 </BODY>
15049 </HTML>
15050 ======= h_config_filt_nick =======
15051 <HTML>
15052 <HEAD>
15053 <TITLE>Nickname Explained</TITLE>
15054 </HEAD>
15055 <BODY>
15056 <H1>Nickname Explained</H1>
15058 This is a nickname to help you.
15059 You should have a different nickname for each filtering rule you define.
15060 The nickname will be used in the SETUP FILTERING RULES screen to allow you to
15061 pick a rule to edit.
15062 <P>
15063 Look <A HREF="h_edit_nav_cmds">here</A>
15064 to see the available Editing and Navigation commands.
15065 <P>
15066 <End of help on this topic>
15067 </BODY>
15068 </HTML>
15069 ======= h_config_score_topat =======
15070 <HTML>
15071 <HEAD>
15072 <TITLE>"To:" Pattern Explained</TITLE>
15073 </HEAD>
15074 <BODY>
15075 <H1>"To:" Pattern Explained</H1>
15077 Any text you enter as the "To pattern"
15078 will be compared to the recipients from the To: line of
15079 the message being scored.
15080 When the text you entered matches
15081 all or part of the To: line of a message, then the Score Value
15082 you have specified will be added to the score for the message.
15083 (Any other non-blank parts of the Pattern must match, too.)
15084 <P>
15086 You may enter a complete email address, part of an address, or a
15087 list of addresses or partial addresses.
15088 For example:
15089 <P>
15091 <PRE>
15092 To pattern = friend@public.com
15094 To pattern = rated.net
15096 To pattern = xxx@adults.com
15097 admin@msn.com
15098 fool@motleyfool.com
15099 </PRE>
15101 <P>
15102 Each of those are valid To patterns.
15103 <P>
15105 Messages match those patterns if any of the
15106 addresses in the To: line of the message contains the pattern.
15107 If the pattern is a list of patterns
15108 (like the last example above) then it is a match if any of the patterns in
15109 the list match any of the addresses in the To: line.
15110 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15111 present for a match.
15112 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15113 address2 must be present.
15114 That is exactly what using a list does.)
15115 <P>
15117 Some messages may be "bounced" to you, and will
15118 have a "Resent-To:" header line.
15119 If the message contains a Resent-To: line
15120 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15121 Alpine will look for
15122 matches to your "To patterns" there, and <EM>NOT</EM> in
15123 the original To: line.
15124 <P>
15126 When entering a pattern, you may choose an address from your address book
15127 with the "T" command.
15128 <P>
15130 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15131 "!" "toggle NOT" command.
15132 This changes the meaning of the To pattern so that it has the opposite meaning.
15133 It will be considered a match if there are no matches between the
15134 addresses in the To: line and the list of To patterns.
15135 <P>
15136 Don't make the mistake of putting the "!" in the data field for
15137 the pattern.
15138 For example, if you type the characters "!frizzle" into the To
15139 pattern, the pattern will look like:
15140 <P>
15141 <PRE>
15142 To pattern = !frizzle
15143 </PRE>
15144 <P>
15145 This means you want to match the 8 character sequence "!frizzle".
15146 In order to match messages that do not have "frizzle" in
15147 their To field, first type the characters "frizzle" followed
15148 by carriage return for the value of the To pattern, then negate it
15149 by typing the "!" command.
15150 It should end up looking like
15151 <P>
15152 <PRE>
15153 ! To pattern = frizzle
15154 </PRE>
15155 <P>
15156 You are not limited to using the six standard header patterns that are
15157 normally shown (To, From, Sender, Cc, News, and Subject).
15158 You may add any other header to a Pattern by
15159 using the "eXtraHdr" command to specify a different
15160 message header line; and then the Add or Change command to fill in
15161 a pattern for the new header line, just like you would for a standard header.
15162 <P>
15163 A technicality: Since comma is the character used to separate multiple
15164 values in a pattern field, you have to escape comma with a backslash (\) if
15165 you want to include a literal comma in the field.
15166 In other words, if you type a backslash followed by a comma it will
15167 be interpreted as a comma by Alpine, instead of as a separator between
15168 pattern values.
15169 All other backslashes are literal backslashes and should not be escaped.
15170 <P>
15171 Look "<A HREF="h_rule_patterns">here</A>"
15172 for more information on Patterns.
15173 <P>
15174 Look <A HREF="h_edit_nav_cmds">here</A>
15175 to see the available Editing and Navigation commands.
15176 <P>
15177 <End of help on this topic>
15178 </BODY>
15179 </HTML>
15180 ======= h_config_incol_topat =======
15181 <HTML>
15182 <HEAD>
15183 <TITLE>"To:" Pattern Explained</TITLE>
15184 </HEAD>
15185 <BODY>
15186 <H1>"To:" Pattern Explained</H1>
15188 Any text you enter as the "To pattern"
15189 will be compared to the recipients from the To: lines of
15190 the messages in the index.
15191 When the text you entered matches
15192 all or part of the To: line of a message, then the Index Line Color you have
15193 specified will be used for that line in the index.
15194 (Any other non-blank parts of the Pattern must match, too.)
15195 <P>
15197 You may enter a complete email address, part of an address, or a
15198 list of addresses or partial addresses.
15199 For example:
15200 <P>
15202 <PRE>
15203 To pattern = friend@public.com
15204 To pattern = rated.net
15205 To pattern = xxx@adults.com
15206 admin@msn.com
15207 fool@motleyfool.com
15208 </PRE>
15210 <P>
15211 Each of those are valid To patterns.
15212 <P>
15214 Messages match those patterns if any of the
15215 addresses in the To: line of the message contains the pattern.
15216 If the pattern is a list of patterns
15217 (like the last example above) then it is a match if any of the patterns in
15218 the list match any of the addresses in the To: line.
15219 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15220 present for a match.
15221 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15222 address2 must be present.
15223 That is exactly what using a list does.)
15224 <P>
15226 Some messages may be "bounced" to you, and will
15227 have a "Resent-To:" header line.
15228 If the message contains a Resent-To: line
15229 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15230 Alpine will look for
15231 matches to your "To patterns" there, and <EM>NOT</EM> in
15232 the original To: line.
15233 <P>
15235 When entering a pattern, you may choose an address from your address book
15236 with the "T" command.
15237 <P>
15239 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15240 "!" "toggle NOT" command.
15241 This changes the meaning of the To pattern so that it has the opposite meaning.
15242 It will be considered a match if there are no matches between the
15243 addresses in the To: line and the list of To patterns.
15244 <P>
15245 Don't make the mistake of putting the "!" in the data field for
15246 the pattern.
15247 For example, if you type the characters "!frizzle" into the To
15248 pattern, the pattern will look like:
15249 <P>
15250 <PRE>
15251 To pattern = !frizzle
15252 </PRE>
15253 <P>
15254 This means you want to match the 8 character sequence "!frizzle".
15255 In order to match messages that do not have "frizzle" in
15256 their To field, first type the characters "frizzle" followed
15257 by carriage return for the value of the To pattern, then negate it
15258 by typing the "!" command.
15259 It should end up looking like
15260 <P>
15261 <PRE>
15262 ! To pattern = frizzle
15263 </PRE>
15264 <P>
15266 You are not limited to using the six standard header patterns that are
15267 normally shown (To, From, Sender, Cc, News, and Subject).
15268 You may add any other header to a Pattern by
15269 using the "eXtraHdr" command to specify a different
15270 message header line; and then the Add or Change command to fill in
15271 a pattern for the new header line, just like you would for a standard header.
15272 <P>
15273 A technicality: Since comma is the character used to separate multiple
15274 values in a pattern field, you have to escape comma with a backslash (\) if
15275 you want to include a literal comma in the field.
15276 In other words, if you type a backslash followed by a comma it will
15277 be interpreted as a comma by Alpine, instead of as a separator between
15278 pattern values.
15279 All other backslashes are literal backslashes and should not be escaped.
15280 <P>
15281 Look "<A HREF="h_rule_patterns">here</A>"
15282 for more information on Patterns.
15283 <P>
15284 Look <A HREF="h_edit_nav_cmds">here</A>
15285 to see the available Editing and Navigation commands.
15286 <P>
15287 <End of help on this topic>
15288 </BODY>
15289 </HTML>
15290 ======= h_config_other_topat =======
15291 <HTML>
15292 <HEAD>
15293 <TITLE>"To:" Pattern Explained</TITLE>
15294 </HEAD>
15295 <BODY>
15296 <H1>"To:" Pattern Explained</H1>
15298 For some of the OTHER RULES actions, there is no message that is being
15299 compared against.
15300 If that is the case, then only the Current Folder Type is checked.
15301 In particular, this To pattern is ignored.
15302 Actions that fall into this category include both
15303 Sort Order and Index Format.
15304 <P>
15305 A technicality: Since comma is the character used to separate multiple
15306 values in a pattern field, you have to escape comma with a backslash (\) if
15307 you want to include a literal comma in the field.
15308 In other words, if you type a backslash followed by a comma it will
15309 be interpreted as a comma by Alpine, instead of as a separator between
15310 pattern values.
15311 All other backslashes are literal backslashes and should not be escaped.
15312 <P>
15313 Look "<A HREF="h_rule_patterns">here</A>"
15314 for more information on Patterns.
15315 <P>
15316 Look <A HREF="h_edit_nav_cmds">here</A>
15317 to see the available Editing and Navigation commands.
15318 <P>
15319 <End of help on this topic>
15320 </BODY>
15321 </HTML>
15322 ======= h_config_filt_topat =======
15323 <HTML>
15324 <HEAD>
15325 <TITLE>"To:" Pattern Explained</TITLE>
15326 </HEAD>
15327 <BODY>
15328 <H1>"To:" Pattern Explained</H1>
15330 Any text you enter as the "To pattern"
15331 will be compared to the recipients from the To: line of
15332 messages when Alpine opens folders.
15333 When the text you entered matches
15334 all or part of the To: line of a message, then the Filter Action you have
15335 specified will be carried out.
15336 (Any other non-blank parts of the Pattern must match, too.)
15337 <P>
15339 You may enter a complete email address, part of an address, or a
15340 list of addresses or partial addresses.
15341 For example:
15342 <P>
15344 <PRE>
15345 To pattern = friend@public.com
15346 To pattern = rated.net
15347 To pattern = xxx@adults.com
15348 admin@msn.com
15349 fool@motleyfool.com
15350 </PRE>
15352 <P>
15353 Each of those are valid To patterns.
15354 <P>
15356 Messages match those patterns if any of the
15357 addresses in the To: line of the message contains the pattern.
15358 If the pattern is a list of patterns
15359 (like the last example above) then it is a match if any of the patterns in
15360 the list match any of the addresses in the To: line.
15361 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15362 present for a match.
15363 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15364 address2 must be present.
15365 That is exactly what using a list does.)
15366 <P>
15368 Some messages may be "bounced" to you, and will
15369 have a "Resent-To:" header line.
15370 If the message contains a Resent-To: line
15371 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15372 Alpine will look for
15373 matches to your "To patterns" there, and <EM>NOT</EM> in
15374 the original To: line.
15375 <P>
15377 When entering a pattern, you may choose an address from your address book
15378 with the "T" command.
15379 <P>
15381 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15382 "!" "toggle NOT" command.
15383 This changes the meaning of the To pattern so that it has the opposite meaning.
15384 It will be considered a match if there are no matches between the
15385 addresses in the To: line and the list of To patterns.
15386 <P>
15387 Don't make the mistake of putting the "!" in the data field for
15388 the pattern.
15389 For example, if you type the characters "!frizzle" into the To
15390 pattern, the pattern will look like:
15391 <P>
15392 <PRE>
15393 To pattern = !frizzle
15394 </PRE>
15395 <P>
15396 This means you want to match the 8 character sequence "!frizzle".
15397 In order to match messages that do not have "frizzle" in
15398 their To field, first type the characters "frizzle" followed
15399 by carriage return for the value of the To pattern, then negate it
15400 by typing the "!" command.
15401 It should end up looking like
15402 <P>
15403 <PRE>
15404 ! To pattern = frizzle
15405 </PRE>
15406 <P>
15408 You are not limited to using the six standard header patterns that are
15409 normally shown (To, From, Sender, Cc, News, and Subject).
15410 You may add any other header to a Pattern by
15411 using the "eXtraHdr" command to specify a different
15412 message header line; and then the Add or Change command to fill in
15413 a pattern for the new header line, just like you would for a standard header.
15414 <P>
15415 A technicality: Since comma is the character used to separate multiple
15416 values in a pattern field, you have to escape comma with a backslash (\) if
15417 you want to include a literal comma in the field.
15418 In other words, if you type a backslash followed by a comma it will
15419 be interpreted as a comma by Alpine, instead of as a separator between
15420 pattern values.
15421 All other backslashes are literal backslashes and should not be escaped.
15422 <P>
15423 Look "<A HREF="h_rule_patterns">here</A>"
15424 for more information on Patterns.
15425 <P>
15426 Look <A HREF="h_edit_nav_cmds">here</A>
15427 to see the available Editing and Navigation commands.
15428 <P>
15429 <End of help on this topic>
15430 </BODY>
15431 </HTML>
15432 ======= h_config_role_topat =======
15433 <HTML>
15434 <HEAD>
15435 <TITLE>"To:" Pattern Explained</TITLE>
15436 </HEAD>
15437 <BODY>
15438 <H1>"To:" Pattern Explained</H1>
15440 Any text you enter as the "To pattern"
15441 will be compared to the recipients from the To: line of
15442 the message being replied to or forwarded.
15443 (Any other non-blank parts of the Pattern must match, too.)
15444 In the case of the Compose command, this pattern and the other header
15445 patterns are ignored.
15446 <P>
15448 You may enter a complete email address, part of an address, or a
15449 list of addresses or partial addresses.
15450 For example:
15451 <P>
15453 <PRE>
15454 To pattern = friend@public.com
15455 To pattern = rated.net
15456 To pattern = xxx@adults.com
15457 admin@msn.com
15458 fool@motleyfool.com
15459 </PRE>
15461 <P>
15462 Each of those are valid To patterns.
15463 <P>
15465 Messages match those patterns if any of the
15466 addresses in the To: line of the message contains the pattern.
15467 If the pattern is a list of patterns
15468 (like the last example above) then it is a match if any of the patterns in
15469 the list match any of the addresses in the To: line.
15470 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15471 present for a match.
15472 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15473 address2 must be present.
15474 That is exactly what using a list does.)
15475 <P>
15477 Some messages may be "bounced" to you, and will
15478 have a "Resent-To:" header line.
15479 If the message contains a Resent-To: line
15480 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15481 Alpine will look for
15482 matches to your "To patterns" there, and <EM>NOT</EM> in
15483 the original To: line.
15484 <P>
15486 When entering a pattern, you may choose an address from your address book
15487 with the "T" command.
15488 <P>
15490 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15491 "!" "toggle NOT" command.
15492 This changes the meaning of the To pattern so that it has the opposite meaning.
15493 It will be considered a match if there are no matches between the
15494 addresses in the To: line and the list of To patterns.
15495 <P>
15496 Don't make the mistake of putting the "!" in the data field for
15497 the pattern.
15498 For example, if you type the characters "!frizzle" into the To
15499 pattern, the pattern will look like:
15500 <P>
15501 <PRE>
15502 To pattern = !frizzle
15503 </PRE>
15504 <P>
15505 This means you want to match the 8 character sequence "!frizzle".
15506 In order to match messages that do not have "frizzle" in
15507 their To field, first type the characters "frizzle" followed
15508 by carriage return for the value of the To pattern, then negate it
15509 by typing the "!" command.
15510 It should end up looking like
15511 <P>
15512 <PRE>
15513 ! To pattern = frizzle
15514 </PRE>
15515 <P>
15517 You are not limited to using the six standard header patterns that are
15518 normally shown (To, From, Sender, Cc, News, and Subject).
15519 You may add any other header to a Pattern by
15520 using the "eXtraHdr" command to specify a different
15521 message header line; and then the Add or Change command to fill in
15522 a pattern for the new header line, just like you would for a standard header.
15523 <P>
15524 A technicality: Since comma is the character used to separate multiple
15525 values in a pattern field, you have to escape comma with a backslash (\) if
15526 you want to include a literal comma in the field.
15527 In other words, if you type a backslash followed by a comma it will
15528 be interpreted as a comma by Alpine, instead of as a separator between
15529 pattern values.
15530 All other backslashes are literal backslashes and should not be escaped.
15531 <P>
15532 Look "<A HREF="h_rule_patterns">here</A>"
15533 for more information on Patterns.
15534 <P>
15535 Look <A HREF="h_edit_nav_cmds">here</A>
15536 to see the available Editing and Navigation commands.
15537 <P>
15538 <End of help on this topic>
15539 </BODY>
15540 </HTML>
15541 ======= h_config_role_frompat =======
15542 <HTML>
15543 <HEAD>
15544 <TITLE>"From:" Pattern Explained</TITLE>
15545 </HEAD>
15546 <BODY>
15547 <H1>"From:" Pattern Explained</H1>
15549 This is just like the "To pattern" except that it is compared with
15550 the address in the From: line of the message
15551 instead of the addresses from the To: line.
15552 See the help for the To pattern for more information on header patterns.
15553 <P>
15554 Look "<A HREF="h_rule_patterns">here</A>"
15555 for more information on Patterns.
15556 <P>
15557 Look <A HREF="h_edit_nav_cmds">here</A>
15558 to see the available Editing and Navigation commands.
15559 <P>
15560 <End of help on this topic>
15561 </BODY>
15562 </HTML>
15563 ======= h_config_role_senderpat =======
15564 <HTML>
15565 <HEAD>
15566 <TITLE>"Sender:" Pattern Explained</TITLE>
15567 </HEAD>
15568 <BODY>
15569 <H1>"Sender:" Pattern Explained</H1>
15571 This is just like the "To pattern" except that it is compared with
15572 the address from the Sender: line of the message
15573 instead of the addresses from the To: line.
15574 See the help for the To pattern for more information on header patterns.
15575 <P>
15576 Look "<A HREF="h_rule_patterns">here</A>"
15577 for more information on Patterns.
15578 <P>
15579 Look <A HREF="h_edit_nav_cmds">here</A>
15580 to see the available Editing and Navigation commands.
15581 <P>
15582 <End of help on this topic>
15583 </BODY>
15584 </HTML>
15585 ======= h_config_role_ccpat =======
15586 <HTML>
15587 <HEAD>
15588 <TITLE>"Cc:" Pattern Explained</TITLE>
15589 </HEAD>
15590 <BODY>
15591 <H1>"Cc:" Pattern Explained</H1>
15593 This is just like the "To pattern" except that it is compared with
15594 the addresses from the Cc: line of the message
15595 instead of the addresses from the To: line.
15596 See the help for the To pattern for more information on header patterns.
15597 <P>
15598 Look "<A HREF="h_rule_patterns">here</A>"
15599 for more information on Patterns.
15600 <P>
15601 Look <A HREF="h_edit_nav_cmds">here</A>
15602 to see the available Editing and Navigation commands.
15603 <P>
15604 <End of help on this topic>
15605 </BODY>
15606 </HTML>
15607 ======= h_config_role_recippat =======
15608 <HTML>
15609 <HEAD>
15610 <TITLE>Recipient Pattern Explained</TITLE>
15611 </HEAD>
15612 <BODY>
15613 <H1>Recipient Pattern Explained</H1>
15615 This is just like the "To pattern" except that it is compared with
15616 the addresses from both the To: line and the Cc: line of the
15617 message instead of just the addresses from the To: line.
15618 In other words, it is considered a match if the pattern matches
15619 <EM>EITHER</EM> an address in the To: line <EM>OR</EM> an address
15620 in the Cc: line.
15621 (Notice that defining the Recipient pattern does not have the same
15622 effect as defining both the To and Cc patterns.
15623 Recipient is To <EM>OR</EM> Cc; not To <EM>AND</EM> Cc.
15624 It is equivalent to having two different rules;
15625 one with a To pattern and the other with the same Cc pattern.)
15626 <P>
15627 A technicality: Since comma is the character used to separate multiple
15628 values in a pattern field, you have to escape comma with a backslash (\) if
15629 you want to include a literal comma in the field.
15630 In other words, if you type a backslash followed by a comma it will
15631 be interpreted as a comma by Alpine, instead of as a separator between
15632 pattern values.
15633 All other backslashes are literal backslashes and should not be escaped.
15634 <P>
15635 Look "<A HREF="h_rule_patterns">here</A>"
15636 for more information on Patterns.
15637 <P>
15638 Look <A HREF="h_edit_nav_cmds">here</A>
15639 to see the available Editing and Navigation commands.
15640 <P>
15641 <End of help on this topic>
15642 </BODY>
15643 </HTML>
15644 ======= h_config_role_particpat =======
15645 <HTML>
15646 <HEAD>
15647 <TITLE>Participant Pattern Explained</TITLE>
15648 </HEAD>
15649 <BODY>
15650 <H1>Participant Pattern Explained</H1>
15652 This is just like the "To pattern" except that it is compared with
15653 the addresses from the From: line, the To: line, and the Cc: line of the
15654 message instead of just the addresses from the To: line.
15655 In other words, it is considered a match if the pattern matches
15656 <EM>EITHER</EM> an address in the From: line, <EM>OR</EM> an address
15657 in the To: line, <EM>OR</EM> an address in the Cc: line.
15658 (Notice that defining the Participant pattern does not have the same
15659 effect as defining all of the From, To, and Cc patterns.
15660 Participant is From <EM>OR</EM> To <EM>OR</EM> Cc; not
15661 From <EM>AND</EM> To <EM>AND</EM> Cc.
15662 It is equivalent to having three different rules;
15663 one with a From pattern, another with the same To pattern, and a third with
15664 the same Cc pattern.)
15665 <P>
15666 A technicality: Since comma is the character used to separate multiple
15667 values in a pattern field, you have to escape comma with a backslash (\) if
15668 you want to include a literal comma in the field.
15669 In other words, if you type a backslash followed by a comma it will
15670 be interpreted as a comma by Alpine, instead of as a separator between
15671 pattern values.
15672 All other backslashes are literal backslashes and should not be escaped.
15673 <P>
15674 Look "<A HREF="h_rule_patterns">here</A>"
15675 for more information on Patterns.
15676 <P>
15677 Look <A HREF="h_edit_nav_cmds">here</A>
15678 to see the available Editing and Navigation commands.
15679 <P>
15680 <End of help on this topic>
15681 </BODY>
15682 </HTML>
15683 ======= h_config_role_newspat =======
15684 <HTML>
15685 <HEAD>
15686 <TITLE>News Pattern Explained</TITLE>
15687 </HEAD>
15688 <BODY>
15689 <H1>News Pattern Explained</H1>
15691 If this pattern is non-blank, then for this rule to be considered a
15692 match, at least one of the newsgroups from
15693 the Newsgroups line of the message must match this pattern.
15694 If this pattern is a list of patterns, then at least one of the
15695 newsgroups must match at least one of the patterns.
15696 (Any other non-blank parts of the Pattern must match, too.)
15697 <P>
15698 It is possible to add a <EM>NOT</EM> to the News Pattern meaning with the
15699 "!" "toggle NOT" command.
15700 This changes the meaning of the News pattern so that it has the opposite meaning.
15701 It will be considered a match if there are no matches between the
15702 addresses in the Newsgroups: line and the list of News patterns.
15703 <P>
15704 Don't make the mistake of putting the "!" in the data field for
15705 the pattern.
15706 For example, if you type the characters "!frizzle" into the News
15707 pattern, the pattern will look like:
15708 <P>
15709 <PRE>
15710 News pattern = !frizzle
15711 </PRE>
15712 <P>
15713 This means you want to match the 8 character sequence "!frizzle".
15714 In order to match messages that do not have "frizzle" in
15715 their Newsgroups header, first type the characters "frizzle" followed
15716 by carriage return for the value of the News pattern, then negate it
15717 by typing the "!" command.
15718 It should end up looking like
15719 <P>
15720 <PRE>
15721 ! News pattern = frizzle
15722 </PRE>
15723 <P>
15724 A technicality: Since comma is the character used to separate multiple
15725 values in a pattern field, you have to escape comma with a backslash (\) if
15726 you want to include a literal comma in the field.
15727 In other words, if you type a backslash followed by a comma it will
15728 be interpreted as a comma by Alpine, instead of as a separator between
15729 pattern values.
15730 All other backslashes are literal backslashes and should not be escaped.
15731 <P>
15733 Look "<A HREF="h_rule_patterns">here</A>"
15734 for more information on Patterns.
15735 <P>
15736 Look <A HREF="h_edit_nav_cmds">here</A>
15737 to see the available Editing and Navigation commands.
15738 <P>
15739 <End of help on this topic>
15740 </BODY>
15741 </HTML>
15742 ======= h_config_role_subjpat =======
15743 <HTML>
15744 <HEAD>
15745 <TITLE>"Subject:" Pattern Explained</TITLE>
15746 </HEAD>
15747 <BODY>
15748 <H1>"Subject:" Pattern Explained</H1>
15750 This is similar to the other parts of the Pattern.
15751 It is compared with
15752 the contents from the Subject of the message.
15753 <P>
15754 Look "<A HREF="h_rule_patterns">here</A>"
15755 for more information on Patterns.
15756 <P>
15757 It is possible to add a <EM>NOT</EM> to the Subject Pattern meaning with the
15758 "!" "toggle NOT" command.
15759 This changes the meaning of the Subject pattern so that it has the opposite meaning.
15760 It will be considered a match if there are no matches between the
15761 text in the Subject: line and the list of Subject patterns.
15762 <P>
15764 If you wish to have a header pattern that is not one of the six standard
15765 header patterns, you may add it with the "eXtraHdr" command.
15766 <P>
15767 A technicality: Since comma is the character used to separate multiple
15768 values in a pattern field, you have to escape comma with a backslash (\) if
15769 you want to include a literal comma in the field.
15770 In other words, if you type a backslash followed by a comma it will
15771 be interpreted as a comma by Alpine, instead of as a separator between
15772 pattern values.
15773 All other backslashes are literal backslashes and should not be escaped.
15774 <P>
15775 Look <A HREF="h_edit_nav_cmds">here</A>
15776 to see the available Editing and Navigation commands.
15777 <P>
15778 <End of help on this topic>
15779 </BODY>
15780 </HTML>
15781 ======= h_config_role_alltextpat =======
15782 <HTML>
15783 <HEAD>
15784 <TITLE>AllText Pattern Explained</TITLE>
15785 </HEAD>
15786 <BODY>
15787 <H1>AllText Pattern Explained</H1>
15789 This is similar to the header patterns.
15790 Instead of comparing with text in a particular header field it
15791 is compared with all of the text in the message header and body.
15792 <P>
15793 It is possible to add a <EM>NOT</EM> to the AllText Pattern meaning with the
15794 "!" "toggle NOT" command.
15795 This changes the meaning of the AllText pattern so that it has the opposite meaning.
15796 It will be considered a match if there are no matches between the
15797 text of the message and the list of AllText patterns.
15798 <P>
15799 Don't make the mistake of putting the "!" in the data field for
15800 the pattern.
15801 For example, if you type the characters "!frizzle" into the AllText
15802 pattern, the pattern will look like:
15803 <P>
15804 <PRE>
15805 AllText pattern = !frizzle
15806 </PRE>
15807 <P>
15808 This means you want to match the 8 character sequence "!frizzle".
15809 In order to match messages that do not have "frizzle" in
15810 the text of the message, first type the characters "frizzle" followed
15811 by carriage return for the value of the AllText pattern, then negate it
15812 by typing the "!" command.
15813 It should end up looking like
15814 <P>
15815 <PRE>
15816 ! AllText pattern = frizzle
15817 </PRE>
15818 <P>
15819 It is possible that you may notice degraded performance when using
15820 AllText Patterns.
15821 <P>
15822 A technicality: Since comma is the character used to separate multiple
15823 values in a pattern field, you have to escape comma with a backslash (\) if
15824 you want to include a literal comma in the field.
15825 In other words, if you type a backslash followed by a comma it will
15826 be interpreted as a comma by Alpine, instead of as a separator between
15827 pattern values.
15828 All other backslashes are literal backslashes and should not be escaped.
15829 <P>
15830 Look "<A HREF="h_rule_patterns">here</A>"
15831 for more information on Patterns.
15832 <P>
15833 Look <A HREF="h_edit_nav_cmds">here</A>
15834 to see the available Editing and Navigation commands.
15835 <P>
15836 <End of help on this topic>
15837 </BODY>
15838 </HTML>
15839 ======= h_config_role_bodytextpat =======
15840 <HTML>
15841 <HEAD>
15842 <TITLE>BodyText Pattern Explained</TITLE>
15843 </HEAD>
15844 <BODY>
15845 <H1>BodyText Pattern Explained</H1>
15847 This is similar to the header patterns.
15848 Instead of comparing with text in a particular header field it
15849 is compared with all of the text in the message body.
15850 <P>
15851 It is possible to add a <EM>NOT</EM> to the BodyText Pattern meaning with the
15852 "!" "toggle NOT" command.
15853 This changes the meaning of the BodyText pattern so that it has the opposite meaning.
15854 It will be considered a match if there are no matches between the
15855 text of the body of the message and the list of BodyText patterns.
15856 <P>
15857 Don't make the mistake of putting the "!" in the data field for
15858 the pattern.
15859 For example, if you type the characters "!frizzle" into the BodyText
15860 pattern, the pattern will look like:
15861 <P>
15862 <PRE>
15863 BdyText pattern = !frizzle
15864 </PRE>
15865 <P>
15866 This means you want to match the 8 character sequence "!frizzle".
15867 In order to match messages that do not have "frizzle" in
15868 their BodyText, first type the characters "frizzle" followed
15869 by carriage return for the value of the BodyText pattern, then negate it
15870 by typing the "!" command.
15871 It should end up looking like
15872 <P>
15873 <PRE>
15874 ! BodyText pattern = frizzle
15875 </PRE>
15876 <P>
15877 It is possible that you may notice degraded performance when using
15878 BodyText Patterns.
15879 <P>
15880 A technicality: Since comma is the character used to separate multiple
15881 values in a pattern field, you have to escape comma with a backslash (\) if
15882 you want to include a literal comma in the field.
15883 In other words, if you type a backslash followed by a comma it will
15884 be interpreted as a comma by Alpine, instead of as a separator between
15885 pattern values.
15886 All other backslashes are literal backslashes and should not be escaped.
15887 <P>
15888 Look "<A HREF="h_rule_patterns">here</A>"
15889 for more information on Patterns.
15890 <P>
15891 Look <A HREF="h_edit_nav_cmds">here</A>
15892 to see the available Editing and Navigation commands.
15893 <P>
15894 <End of help on this topic>
15895 </BODY>
15896 </HTML>
15897 ======= h_config_role_charsetpat =======
15898 <HTML>
15899 <HEAD>
15900 <TITLE>Character Set Pattern Explained</TITLE>
15901 </HEAD>
15902 <BODY>
15903 <H1>Character Set Pattern Explained</H1>
15905 A message may use one or more character sets.
15906 This part of the Pattern matches messages that make use of
15907 certain specified character sets.
15908 It will be considered a match if a message uses any of the character
15909 sets in the list you give here.
15911 <P>
15912 When filling in a value for this field, you may use
15913 the "T" command, which presents you with a large list of
15914 possible character sets to choose from.
15915 You may also just type in the name of a character set, and it need not
15916 be one that Alpine knows about.
15918 <P>
15919 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
15920 GB2312) you may also use some shorthand names that Alpine provides.
15921 These names are more understandable shorthand names for sets of
15922 character set names.
15923 Two examples are "Cyrillic" and "Greek".
15924 Selecting one of these shorthand names is equivalent to selecting all of
15925 the character sets that make up the set.
15926 You can see all of these shorthand names and the lists of character sets
15927 they stand for by typing the "T" command.
15929 <P>
15930 For the purposes of this Pattern,
15931 Alpine will search through a message for all of the text parts and
15932 collect the character sets declared for each part.
15933 It will also look in the Subject line for a character set used there.
15934 Alpine does not actually look at the text of the message or the text
15935 of the Subject to determine if a declared character set is actually
15936 used, it looks only at the declarations themselves in the MIME part headers
15937 and in the Subject.
15939 <P>
15940 It is possible to add a <EM>NOT</EM> to the Character Set Pattern meaning with the
15941 "!" "toggle NOT" command.
15942 This changes the meaning of the Character Set pattern so that
15943 it has the opposite meaning.
15944 It will be considered a match if none of the character sets in the
15945 list are used in a message.
15946 <P>
15947 Don't make the mistake of putting the "!" in the data field for
15948 the pattern.
15949 For example, if you type the characters "!GB2312" into the
15950 Character Set pattern, the pattern will look like:
15951 <P>
15952 <PRE>
15953 Charset pattern = !GB2312
15954 </PRE>
15955 <P>
15956 This means you want to match the 7 character sequence "!GB2312".
15957 In order to match messages that do not have the
15958 character set "GB2312"
15959 set, first type the characters "GB2312" followed
15960 by carriage return for the value of the Character Set pattern, then negate it
15961 by typing the "!" command.
15962 It should end up looking like
15963 <P>
15964 <PRE>
15965 ! Charset pattern = GB2312
15966 </PRE>
15967 <P>
15968 A technicality: Since comma is the character used to separate multiple
15969 values in a pattern field, you have to escape comma with a backslash (\) if
15970 you want to include a literal comma in the field.
15971 In other words, if you type a backslash followed by a comma it will
15972 be interpreted as a comma by Alpine, instead of as a separator between
15973 pattern values.
15974 All other backslashes are literal backslashes and should not be escaped.
15975 <P>
15976 Look "<A HREF="h_rule_patterns">here</A>"
15977 for more information on Patterns.
15978 <P>
15979 Look <A HREF="h_edit_nav_cmds">here</A>
15980 to see the available Editing and Navigation commands.
15981 <P>
15982 <End of help on this topic>
15983 </BODY>
15984 </HTML>
15985 ======= h_config_role_keywordpat =======
15986 <HTML>
15987 <HEAD>
15988 <TITLE>Keyword Pattern Explained</TITLE>
15989 </HEAD>
15990 <BODY>
15991 <H1>Keyword Pattern Explained</H1>
15993 A folder may have user-defined keywords.
15994 These are similar to the Important flag, which the user may set using the
15995 Flag command.
15996 The difference is that the Important flag is always present for each folder.
15997 User-defined keywords are picked by the user.
15998 You may add new keywords by defining them in the
15999 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
16000 After you have added a potential keyword with the <!--#echo var="VAR_keywords"--> option,
16001 the Flag command may be used to set or clear the keyword on individual messages.
16002 If you have given a keyword a nickname when configuring it,
16003 that nickname may be used instead of the actual keyword.
16005 <P>
16006 When filling in a value for this field, it may be easiest to use
16007 the "T" command, which presents you with a list of the keywords
16008 you have defined to choose from.
16010 <P>
16011 This part of the Pattern matches messages with certain keywords set.
16012 It will be considered a match if a message has any of the keywords in the
16013 list set.
16014 A keyword that you have not defined using the
16015 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16016 will not be a match.
16018 <P>
16019 It is possible to add a <EM>NOT</EM> to the Keyword Pattern meaning with the
16020 "!" "toggle NOT" command.
16021 This changes the meaning of the Keyword pattern so that it has the opposite meaning.
16022 It will be considered a match if none of the keywords in the list are set
16023 for a message.
16024 A keyword that you have not defined using the
16025 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16026 will not be a match, so a <EM>NOT</EM> of that keyword does match.
16027 <P>
16028 Don't make the mistake of putting the "!" in the data field for
16029 the pattern.
16030 For example, if you type the characters "!frizzle" into the Keyword
16031 pattern, the pattern will look like:
16032 <P>
16033 <PRE>
16034 Keyword pattern = !frizzle
16035 </PRE>
16036 <P>
16037 This means you want to match the 8 character sequence "!frizzle".
16038 In order to match messages that do not have the keyword "frizzle"
16039 set, first type the characters "frizzle" followed
16040 by carriage return for the value of the Keyword pattern, then negate it
16041 by typing the "!" command.
16042 It should end up looking like
16043 <P>
16044 <PRE>
16045 ! Keyword pattern = frizzle
16046 </PRE>
16047 <P>
16048 A technicality: Since comma is the character used to separate multiple
16049 values in a pattern field, you have to escape comma with a backslash (\) if
16050 you want to include a literal comma in the field.
16051 In other words, if you type a backslash followed by a comma it will
16052 be interpreted as a comma by Alpine, instead of as a separator between
16053 pattern values.
16054 All other backslashes are literal backslashes and should not be escaped.
16055 <P>
16056 Look "<A HREF="h_rule_patterns">here</A>"
16057 for more information on Patterns.
16058 <P>
16059 Look <A HREF="h_edit_nav_cmds">here</A>
16060 to see the available Editing and Navigation commands.
16061 <P>
16062 <End of help on this topic>
16063 </BODY>
16064 </HTML>
16065 ======= h_config_role_arbpat =======
16066 <HTML>
16067 <HEAD>
16068 <TITLE>Extra Header Patterns Explained</TITLE>
16069 </HEAD>
16070 <BODY>
16071 <H1>Extra Header Patterns Explained</H1>
16073 The header patterns that come after the Participant pattern but before the
16074 AllText pattern are extra header patterns that you have added to a rule's
16075 Pattern. These are just like the other header patterns except that
16076 the contents of the particular header listed on the left hand side will
16077 be used for comparisons.
16078 <P>
16079 The "eXtraHdr" command may be used to add more of these
16080 header patterns to the rule you are editing.
16081 <P>
16082 The "RemoveHdr" command may be used to delete the highlighted
16083 extra header pattern from the rule you are editing.
16084 <P>
16085 It is possible to add a <EM>NOT</EM> to the Extra Header Pattern meaning with the
16086 "!" "toggle NOT" command.
16087 This changes the meaning of the pattern so that it has the opposite meaning.
16088 It will be considered a match if there are no matches between the
16089 text in the header line and the list of patterns.
16090 <P>
16091 Don't make the mistake of putting the "!" in the data field for
16092 the pattern.
16093 For example, if you type the characters "!frizzle" into the
16094 pattern, the pattern will look like:
16095 <P>
16096 <PRE>
16097 Xyz pattern = !frizzle
16098 </PRE>
16099 <P>
16100 This means you want to match the 8 character sequence "!frizzle".
16101 In order to match messages that do not have "frizzle" in
16102 their Xyz field, first type the characters "frizzle" followed
16103 by carriage return for the value of the pattern, then negate it
16104 by typing the "!" command.
16105 It should end up looking like
16106 <P>
16107 <PRE>
16108 ! Xyz pattern = frizzle
16109 </PRE>
16111 <P>
16112 A technicality: Since comma is the character used to separate multiple
16113 values in a pattern field, you have to escape comma with a backslash (\) if
16114 you want to include a literal comma in the field.
16115 In other words, if you type a backslash followed by a comma it will
16116 be interpreted as a comma by Alpine, instead of as a separator between
16117 pattern values.
16118 All other backslashes are literal backslashes and should not be escaped.
16119 <P>
16120 Look "<A HREF="h_rule_patterns">here</A>"
16121 for more information on Patterns.
16122 <P>
16123 Look <A HREF="h_edit_nav_cmds">here</A>
16124 to see the available Editing and Navigation commands.
16125 <P>
16126 <End of help on this topic>
16127 </BODY>
16128 </HTML>
16129 ======= h_config_role_cat_cmd =======
16130 <HTML>
16131 <HEAD>
16132 <TITLE>Categorizer Command Explained</TITLE>
16133 </HEAD>
16134 <BODY>
16135 <H1>Categorizer Command Explained</H1>
16137 This is a command that is run with its standard input set to the message
16138 being checked and its standard output discarded.
16139 The full directory path should be specified.
16140 The command will be run and then its exit status will be checked against
16141 the Exit Status Interval, which defaults to just the value zero.
16142 If the exit status of the command falls in the interval, it is considered
16143 a match, otherwise it is not a match.
16144 <P>
16146 This option may actually be a list of commands.
16147 The first one that exists and is executable is used.
16148 That makes it possible to use the same configuration with Unix Alpine and
16149 PC-Alpine.
16150 <P>
16152 If none of the commands in the list exists and is executable then the rule
16153 is <EM>not</EM> a match.
16154 If it is possible that the command may not exist, you should be careful
16155 to structure your rules so that nothing destructive
16156 happens when the command does not exist.
16157 For example, you might have a filter that filters away spam when there is
16158 a match but does nothing when there is not a match.
16159 That would cause no harm if the command didn't exist.
16160 However, if you have a filter that filters away spam when there is not
16161 a match and keeps it when there is a match, that would filter everything
16162 if the categorizer command didn't exist.
16163 <P>
16164 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
16165 setup for the bogofilter filter.
16167 <P>
16168 Look "<A HREF="h_rule_patterns">here</A>"
16169 for more information on Patterns.
16170 <P>
16171 Look <A HREF="h_edit_nav_cmds">here</A>
16172 to see the available Editing and Navigation commands.
16173 <P>
16174 <End of help on this topic>
16175 </BODY>
16176 </HTML>
16177 ======= h_config_role_cat_cmd_example =======
16178 <HTML>
16179 <HEAD>
16180 <TITLE>Categorizer Command Example</TITLE>
16181 </HEAD>
16182 <BODY>
16183 <H1>Categorizer Command Example</H1>
16185 Bogofilter
16186 (<A HREF="http://bogofilter.sourceforge.net/">http://bogofilter.sourceforge.net/</A>)
16187 is a mail filter that attempts to classify mail as spam or
16188 non-spam using statistical analysis of the message content.
16189 When run with no arguments and a message as standard input, it exits with
16190 exit status 0 if it thinks a message is spam and 1 if it thinks
16191 it is not spam.
16192 To use bogofilter as your Categorizer Command you would simply set Command to
16193 the pathname of the bogofilter program.
16194 For example,
16195 <P>
16196 <CENTER><SAMP>Command = /usr/local/bin/bogofilter</SAMP></CENTER>
16197 <P>
16198 Exit status of zero is what you are interested in, so you'd set the
16199 Exit Status Interval to
16200 <P>
16201 <CENTER><SAMP>Exit Status Interval = (0,0)</SAMP></CENTER>
16202 <P>
16204 In order to prevent downloading an entire huge message to check for spam, you
16205 might want to set the Character Limit to a few thousand characters (the
16206 assumption being that the spam will reveal itself in those characters)
16207 <P>
16208 <CENTER><SAMP>Character Limit = 50000</SAMP></CENTER>
16209 <P>
16211 You would probably use bogofilter in an Alpine Filter Rule, and have the action
16212 be to move the message to a spam folder.
16213 It would usually be wise to also check the "Message is Recent"
16214 part of the rule so that messages are only checked when they first arrive,
16215 and to restrict the Current Folder Type to just your INBOX.
16216 The reason for checking only Recent messages is to save the time it takes
16217 to run bogofilter on each message.
16218 As an experiment, you might start out by using this in an Indexcolor Rule
16219 instead of a Filter Rule.
16220 In that case, you probably wouldn't check the Recent checkbox.
16221 <P>
16222 The use described above assumes that you are somehow maintaining bogofilter's
16223 database of words associated with spam and non-spam messages.
16224 One way to start your database would be to select a bunch of spam messages
16225 in Alpine (you might Save spam messages to a special folder or use Alpine's
16226 Select command to select several) and then Apply
16227 (<A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>)
16228 a pipe command to the spam messages.
16229 For example, you could have a shell script or an alias
16230 called <EM>this_is_spam</EM>, which would simply be the command
16231 <P>
16232 <CENTER><SAMP>bogofilter -s</SAMP></CENTER>
16233 <P>
16235 It is probably best to use the pipe command's Raw Text, With Delimiter,
16236 and Free Output options,
16237 which are at the bottom of the screen when you type the pipe command.
16238 That's because bogofilter expects the raw message as input, and uses
16239 the Delimiters to tell when a new message starts.
16240 You would not need to use a separate pipe for each message, because
16241 bogofilter can handle multiple messages at once.
16242 <P>
16243 Similarly, you would select a group of non-spam messages
16244 and run them through a <EM>this_is_nonspam</EM> script
16245 that was something like
16246 <P>
16247 <CENTER><SAMP>bogofilter -n</SAMP></CENTER>
16248 <P>
16250 For the more adventurous, the next step might be to automate the upkeep of
16251 the bogofilter database.
16252 It might make more sense to have bogofilter be part of the delivery process,
16253 but it is also possible to do it entirely from within Alpine.
16254 Instead of using just plain "bogofilter" as the Categorizer Command,
16255 the "-u" argument will cause bogofilter to update the database.
16256 <P>
16257 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16258 <P>
16259 You'd want a couple more aliases or shell scripts called something like
16260 <EM>change_to_spam</EM>
16261 <P>
16262 <CENTER><SAMP>bogofilter -Ns</SAMP></CENTER>
16263 <P>
16264 and
16265 <EM>change_to_nonspam</EM>
16266 <P>
16267 <CENTER><SAMP>bogofilter -Sn</SAMP></CENTER>
16268 <P>
16269 When you run across a message in your INBOX that should have been
16270 classified as spam you would pipe it to the change_to_spam script, and
16271 when you run across a message in your spam folder that should have been
16272 left in your INBOX you would pipe it through change_to_nonspam.
16274 <P>
16275 There is a technical problem with this approach.
16276 Alpine may check your filters more than once.
16277 In particular, every time you start Alpine the filters will be checked for
16278 each message.
16279 Also, if you have any filters that depend on message state (New, Deleted, etc.)
16280 then Alpine will recheck for matches in messages that have changed state
16281 at the time you close the folder and before expunging.
16282 This is usually ok.
16283 However, in this case it is a problem because the command
16284 <P>
16285 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16286 <P>
16287 has the side effect of updating the database.
16288 So you run the risk of updating the database multiple times for a single
16289 message instead of updating it just once per message.
16290 There are some ways to work around this problem.
16291 What you need is a way to mark the message after you have run the filter.
16292 One way to mark messages is with the use of a keyword (say "Bogo").
16293 Besides having the filter move the message to a spam folder, also have it
16294 set the Bogo keyword.
16295 (Note that you will have to set up the "Bogo" keyword in the
16296 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in Setup/Config.)
16297 This rule can only set the Bogo keyword for the messages that it matches.
16298 You will also need to add a second rule right after this one that
16299 matches all the messages that don't have the Bogo keyword set
16300 (put the keyword in the Keyword pattern and toggle
16301 the Not with the ! command)
16302 and takes the action of setting it.
16303 Then change the "bogofilter -u" rule so that it won't be a match
16304 (and so it won't re-run the bogofilter command) if the keyword is already
16305 set.
16306 <P>
16307 What you will end up with is a rule that runs "bogofilter -u"
16308 on all messages that don't have the Bogo keyword set.
16309 This will have the side effect of inserting that message in the bogofilter
16310 database, match or not.
16311 If this rule matches (it is spam), the Bogo keyword will be set and
16312 the message will be moved to a spam folder.
16313 If it does not match, the
16314 following rule will mark the message by turning on the keyword.
16315 This second rule should be a non-terminating
16316 (<A HREF="h_config_filt_opts_nonterm">Dont-Stop-Even-if-Rule-Matches</A>)
16317 rule so that it doesn't stop the filtering process before the rest of
16318 your rules are consulted.
16320 <P>
16321 In summary, the first rule is something like
16322 <PRE>
16323 Nickname = bogofilter -u rule
16324 Current Folder Type =
16325 (*) Specific
16326 Folder = INBOX
16328 ! Keyword pattern = Bogo
16330 External Categorizer Commands =
16331 Command = /usr/local/bin/bogofilter -u
16332 Exit Status Interval = (0,0)
16333 Character Limit = <No Value Set: using "-1"> (optionally set this)
16335 Filter Action =
16336 (*) Move
16337 Folder = spam
16339 Set These Keywords = Bogo
16340 </PRE>
16341 <P>
16342 and the following rule is
16343 <PRE>
16344 Nickname = Set Bogo Keyword
16345 Current Folder Type =
16346 (*) Specific
16347 Folder = INBOX
16349 ! Keyword pattern = Bogo
16351 Filter Action =
16352 (*) Just Set Message Status
16354 Set These Keywords = Bogo
16356 Features =
16357 [X] dont-stop-even-if-rule-matches
16358 </PRE>
16359 <P>
16360 If it is possible for you to insert bogofilter in the delivery process instead
16361 of having it called from Alpine you could prevent having to wait
16362 for the bogofilter processing while you read your mail.
16363 You would have bogofilter add a header to the message at the time of delivery
16364 that identified it as spam or nonspam.
16365 With this method, you could avoid using a Categorizer Command while running Alpine,
16366 and just match on the header instead.
16367 You might still want to use the scripts mentioned above to initialize the
16368 database or to re-classify wrongly classified messages.
16370 <P>
16371 Finally, it isn't for the faint-hearted,
16372 but it is also possible to run bogofilter from PC-Alpine.
16373 You can install Cygwin from
16374 <A HREF="http://www.cygwin.com/">http://www.cygwin.com/</A> and
16375 then compile bogofilter in the cygwin environment, and run it from
16376 within PC-Alpine.
16377 You would end up with a Categorizer command that looked something like
16378 <P>
16379 <CENTER><SAMP>Command = C:\cygwin\bin\bogofilter.exe -u</SAMP></CENTER>
16380 <P>
16381 Note that the ".exe" extension is explicit,
16382 and that the bogofilter.exe executable should be in the same directory
16383 as cygwin1.dll.
16385 <P>
16386 <End of help on this topic>
16387 </BODY>
16388 </HTML>
16389 ======= h_config_role_cat_status =======
16390 <HTML>
16391 <HEAD>
16392 <TITLE>Exit Status Interval Explained</TITLE>
16393 </HEAD>
16394 <BODY>
16395 <H1>Exit Status Interval Explained</H1>
16397 The categorizer command is run and the result is the exit status of
16398 that command.
16399 If that exit status falls in the Exit Status Interval
16400 then it is considered a match, otherwise it is not a match.
16401 Of course for the entire rule to match, it must also be checked against
16402 the other defined parts of the Pattern.
16403 <P>
16404 The Exit Status Interval defaults to the single value 0 (zero).
16405 If you define it, it should be set to something like:
16406 <P>
16407 <CENTER><SAMP>(min_exit_value,max_exit_value)</SAMP></CENTER>
16408 <P>
16409 where "min_exit_value" and "max_exit_value" are integers.
16410 The special values "INF" and "-INF" may be used for large
16411 positive and negative integers.
16412 <P>
16413 Actually, a list of intervals may be used if you wish.
16414 A list would look like
16415 <P>
16416 <CENTER><SAMP>(min_exit_value1,max_exit_value1),(min_exit_value2,max_exit_value2),...</SAMP></CENTER>
16417 <P>
16418 When there is an Exit Status Interval defined, it is a match if the exit status
16419 of the categorizer command is contained in any of the intervals.
16420 The intervals include both endpoints.
16421 <P>
16422 The default interval is
16423 <P>
16424 <CENTER><SAMP>(0,0)</SAMP></CENTER>
16425 <P>
16426 and it matches only if the command exits with exit status equal to zero.
16428 <P>
16429 Look "<A HREF="h_rule_patterns">here</A>"
16430 for more information on Patterns.
16431 <P>
16432 Look <A HREF="h_edit_nav_cmds">here</A>
16433 to see the available Editing and Navigation commands.
16434 <P>
16435 <End of help on this topic>
16436 </BODY>
16437 </HTML>
16438 ======= h_config_role_cat_limit =======
16439 <HTML>
16440 <HEAD>
16441 <TITLE>Character Limit Explained</TITLE>
16442 </HEAD>
16443 <BODY>
16444 <H1>Character Limit Explained</H1>
16446 Setting this option makes it possible to limit how much of the message
16447 is made available to the categorizer command as input.
16448 The default value (-1) means that the entire message is fed to the
16449 command.
16450 A value of 0 (zero) means that only the headers of the message are
16451 made available.
16452 A positive integer means that the headers plus that many characters from
16453 the body of the message are passed to the categorizer.
16455 <P>
16456 Look "<A HREF="h_rule_patterns">here</A>"
16457 for more information on Patterns.
16458 <P>
16459 Look <A HREF="h_edit_nav_cmds">here</A>
16460 to see the available Editing and Navigation commands.
16461 <P>
16462 <End of help on this topic>
16463 </BODY>
16464 </HTML>
16465 ======= h_config_role_age =======
16466 <HTML>
16467 <HEAD>
16468 <TITLE>Age Interval Explained</TITLE>
16469 </HEAD>
16470 <BODY>
16471 <H1>Age Interval Explained</H1>
16473 The Age Interval, if defined, is part of the Pattern.
16474 If you use this, it should be set to something like:
16475 <P>
16476 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
16477 <P>
16478 where "min_age" and "max_age" are non-negative integers.
16479 The special value "INF" may be used for the max value.
16480 It represents infinity.
16481 <P>
16482 In rare cases it may be useful to use the more general form of the value,
16483 which is a comma-separated list of intervals.
16484 It would look something like:
16485 <P>
16486 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
16487 <P>
16488 When there is an Age Interval defined, it is a match if the age, in days, of
16489 the message is contained in the interval.
16490 The interval includes both endpoints.
16491 If the option is set to a list of intervals then it is a match if the
16492 age of the message is contained in any of the intervals.
16493 <P>
16494 Even though this option is called Age, it isn't actually
16495 the <EM>age</EM> of the message.
16496 Instead, it is how many days ago the message arrived in one of your folders.
16497 If the current time is a little past midnight, then a message that arrived
16498 just before midnight arrived yesterday, even though the message is only
16499 a few minutes old.
16500 By default, the date being used is not the date in the Date
16501 header of the message.
16502 It is the date that the message arrived in one of your folders.
16503 When you Save a message from one folder to another that arrival date
16504 is preserved.
16505 If you would like to use the date in the Date header that is possible.
16506 Turn on the option
16507 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
16508 near the bottom of the rule definition.
16509 <P>
16510 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
16511 The age interval
16512 <P>
16513 <CENTER><SAMP>(2,2)</SAMP></CENTER>
16514 <P>
16515 matches all messages that arrived on the day before yesterday.
16516 The interval
16517 <P>
16518 <CENTER><SAMP>(180,INF)</SAMP></CENTER>
16519 <P>
16520 matches all messages that arrived at least 180 days before today.
16521 The interval
16522 <P>
16523 <CENTER><SAMP>(0,1)</SAMP></CENTER>
16524 <P>
16525 matches all messages that arrived today or yesterday.
16527 <P>
16528 Look "<A HREF="h_rule_patterns">here</A>"
16529 for more information on Patterns.
16530 <P>
16531 Look <A HREF="h_edit_nav_cmds">here</A>
16532 to see the available Editing and Navigation commands.
16533 <P>
16534 <End of help on this topic>
16535 </BODY>
16536 </HTML>
16537 ======= h_config_role_size =======
16538 <HTML>
16539 <HEAD>
16540 <TITLE>Size Interval Explained</TITLE>
16541 </HEAD>
16542 <BODY>
16543 <H1>Size Interval Explained</H1>
16545 The Size Interval, if defined, is part of the Pattern.
16546 If you use this, it should be set to something like:
16547 <P>
16548 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
16549 <P>
16550 where "min_size" and "max_size" are non-negative integers.
16551 The special value "INF" may be used for the max value.
16552 It represents infinity.
16553 <P>
16554 In rare cases it may be useful to use the more general form of the value,
16555 which is a comma-separated list of intervals.
16556 It would look something like:
16557 <P>
16558 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
16559 <P>
16560 When there is a Size Interval defined, it is a match if the size of
16561 the message is contained in the interval.
16562 The interval includes both endpoints.
16563 If the option is set to a list of intervals then it is a match if the
16564 size of the message is contained in any of the intervals.
16565 <P>
16566 The size interval
16567 <P>
16568 <CENTER><SAMP>(10000,50000)</SAMP></CENTER>
16569 <P>
16570 matches all messages with sizes greater than or equal to 10000, and less
16571 than or equal to 50000.
16572 The interval
16573 <P>
16574 <CENTER><SAMP>(100000,INF)</SAMP></CENTER>
16575 <P>
16576 matches all messages with sizes greater than or equal to 100000.
16578 <P>
16579 Look "<A HREF="h_rule_patterns">here</A>"
16580 for more information on Patterns.
16581 <P>
16582 Look <A HREF="h_edit_nav_cmds">here</A>
16583 to see the available Editing and Navigation commands.
16584 <P>
16585 <End of help on this topic>
16586 </BODY>
16587 </HTML>
16588 ======= h_config_role_scorei =======
16589 <HTML>
16590 <HEAD>
16591 <TITLE>Score Interval Explained</TITLE>
16592 </HEAD>
16593 <BODY>
16594 <H1>Score Interval Explained</H1>
16596 The Score Interval, if defined, is part of the Pattern.
16597 If you use this, it should be set to something like:
16598 <P>
16599 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
16600 <P>
16601 where "min_score" and "max_score" are integers between
16602 -32000 and 32000.
16603 The special values "-INF" and "INF" may be used for
16604 the min and max values.
16605 These represent negative and positive infinity.
16606 <P>
16607 Actually, the value may be a list of intervals rather than just a
16608 single interval if that is useful.
16609 The elements of the list are separated by commas like:
16610 <P>
16611 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
16612 <P>
16613 When there is a Score Interval defined, it is a match if the score for
16614 the message is contained in any of the intervals.
16615 The intervals include both endpoints.
16616 The score for a message is calculated by looking at every scoring rule
16617 defined and adding up the Score Values for the rules that match the message.
16618 Scoring rules are created using the
16619 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
16621 <P>
16622 Look "<A HREF="h_rule_patterns">here</A>"
16623 for more information on Patterns.
16624 <P>
16625 Look <A HREF="h_edit_nav_cmds">here</A>
16626 to see the available Editing and Navigation commands.
16627 <P>
16628 <End of help on this topic>
16629 </BODY>
16630 </HTML>
16631 ======= h_config_role_fldr_type =======
16632 <HTML>
16633 <HEAD>
16634 <TITLE>Current Folder Type Explained</TITLE>
16635 </HEAD>
16636 <BODY>
16637 <H1>Current Folder Type Explained</H1>
16639 The Current Folder Type is part of the role's Pattern.
16640 It refers to the type of the currently open folder, which is the folder
16641 you were last looking at from the MESSAGE INDEX or MESSAGE TEXT screen.
16642 In order for a role to be considered a match, the current folder must
16643 be of the type you set here.
16644 The three types "Any", "News", and "Email" are
16645 all what you might think.
16646 <P>
16647 If the Current Folder Type for a role's Pattern is set to "News", for
16648 example, then
16649 that role will only be a match if the current folder is a newsgroup and
16650 the rest of the Pattern matches.
16651 The value "Specific" may be used when you want to limit the match
16652 to a specific folder (not just a specific type of folder), or to a list of
16653 specific folders.
16654 <P>
16655 In order to match a specific folder you Select the "Specific"
16656 button <EM>AND</EM> fill in
16657 the name (or list of names) of
16658 the folder in the "Folder List" field.
16659 If the current folder is any of the folders in the list, that is considered
16660 a match.
16661 The name of each folder in the list may be either "INBOX",
16662 the technical specification
16663 of the folder (like what appears in your configuration file) or, if the
16664 folder is one of your incoming folders, it may be the nickname you've given
16665 the folder.
16666 Here are a couple samples of specific folder names:
16667 <P>
16668 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
16669 <P>
16670 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
16671 <P>
16672 The easiest way to fill in the "Folder List" field is to use
16673 the "T" command that is available when the "Folder List" line is
16674 highlighted, or to use the "Take" command with the configuration
16675 feature
16676 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
16677 turned on.
16678 Note that you won't be able to edit the "Folder List" line unless the
16679 Current Folder Type is set to "Specific", and any value that
16680 "Folder List" has is ignored unless the type
16681 is set to "Specific".
16682 <P>
16683 When reading a newsgroup, there may be a performance penalty
16684 incurred when collecting the information necessary to check a Pattern.
16685 For this reason, the default Current Folder Type is set to "Email".
16686 <P>
16687 Look "<A HREF="h_rule_patterns">here</A>"
16688 for more information on Patterns.
16689 <P>
16690 Look <A HREF="h_edit_nav_cmds">here</A>
16691 to see the available Editing and Navigation commands.
16692 <P>
16693 <End of help on this topic>
16694 </BODY>
16695 </HTML>
16696 ======= h_config_filt_rule_type =======
16697 <HTML>
16698 <HEAD>
16699 <TITLE>Filter Action Explained</TITLE>
16700 </HEAD>
16701 <BODY>
16702 <H1>Filter Action Explained</H1>
16704 The Filter Action specifies the action to be taken when the Pattern is a
16705 match.
16706 It may be set to "Delete" "Move", or
16707 "Just Set Message Status".
16708 <P>
16709 If it is set to "Delete", then the message that matches the
16710 Pattern will be deleted from the open folder.
16711 <P>
16712 If it is set to "Move", then the name of the folder to which
16713 the matching message should be moved is given in the "Folder List" field on the
16714 next line of the screen.
16715 A list of folders separated by commas may be given, in which case the
16716 message will be copied to all of the folders in the list before it is
16717 deleted.
16718 <P>
16719 If it is set to neither of those two values (it is set to the value
16720 labeled "Just Set Message Status") then the message status
16721 setting will happen
16722 but the message will not be deleted or moved.
16723 <P>
16724 If you are Moving a message you may also set Message Status if you wish.
16725 <P>
16726 The easiest way to fill in the "Folder List" field is to use
16727 the T command that is available when the "Folder List" line is
16728 highlighted.
16729 Note that you won't be able to edit the "Folder List" line unless the
16730 Filter Action is set to "Move", and any value that
16731 "Folder List" has is ignored unless the type
16732 is set to "Move".
16733 <P>
16734 There are a few tokens that may be used in the names in the Folder List.
16735 They are all related to the date on which the filtering is taking place.
16736 The tokens are words surrounded by underscores.
16737 For example, if you want your filter to move messages to a folder named
16738 <P><CENTER><SAMP>abc-year-mon</SAMP></CENTER><P>
16739 you could specify the folder as
16740 <P><CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER><P>
16741 which would result in a file named something like
16742 <P><CENTER><SAMP>abc-2004-oct</SAMP></CENTER><P>
16743 or
16744 <P><CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER><P>
16745 which would result in a file named something like
16746 <P><CENTER><SAMP>abc-04-10</SAMP></CENTER><P>
16747 The available tokens are listed
16748 <A HREF="h_index_tokens">here</A>.
16749 <P>
16750 Look "<A HREF="h_rule_patterns">here</A>"
16751 for more information on Patterns.
16752 <P>
16753 Look <A HREF="h_edit_nav_cmds">here</A>
16754 to see the available Editing and Navigation commands.
16755 <P>
16756 <End of help on this topic>
16757 </BODY>
16758 </HTML>
16759 ======= h_config_score_fldr_type =======
16760 <HTML>
16761 <HEAD>
16762 <TITLE>Current Folder Type Explained</TITLE>
16763 </HEAD>
16764 <BODY>
16765 <H1>Current Folder Type Explained</H1>
16767 The Current Folder Type is part of the scoring rule's Pattern.
16768 It refers to the type of the folder that
16769 the message being scored is in.
16770 In order for a rule to be considered a match, the current folder must
16771 be of the type you set here.
16772 The three types "Any", "News", and "Email" are
16773 all what you might think.
16774 <P>
16775 If the Current Folder Type for a Pattern is set to "News", for
16776 example, then
16777 that Pattern will only match if the current folder is a newsgroup and
16778 the rest of the Pattern matches.
16779 The value "Specific" may be used when you want to limit the match
16780 to a specific folder (not just a specific type of folder), or to a list of
16781 specific folders.
16782 <P>
16783 In order to match a specific folder you Select the "Specific"
16784 button <EM>AND</EM> fill in
16785 the name (or list of names) of
16786 the folder in the "Folder List" field.
16787 If the current folder is any of the folders in the list, that is considered
16788 a match.
16789 The name of each folder in the list may be either "INBOX", the technical specification
16790 of the folder (like what appears in your configuration file) or, if the
16791 folder is one of your incoming folders, it may be the nickname you've given
16792 the folder.
16793 Here are a couple samples of specific folder names:
16794 <P>
16795 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
16796 <P>
16797 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
16798 <P>
16799 The easiest way to fill in the "Folder List" field is to use
16800 the T command that is available when the "Folder List" line is
16801 highlighted.
16802 Note that you won't be able to edit the "Folder List" line unless the
16803 Current Folder Type is set to "Specific", and any value that
16804 "Folder List" has is ignored unless the type
16805 is set to "Specific".
16806 <P>
16807 When reading a newsgroup, there may be a performance penalty
16808 incurred when collecting the information necessary to check a Pattern.
16809 For this reason, the default Current Folder Type is set to "Email".
16810 For example, if you have Index Line Coloring rules that have Score Intervals
16811 defined then the scores for all the visible messages will need to be calculated.
16812 If some of your Scoring rules have
16813 a Current Folder Type of
16814 "Any" or "News" this may cause the MESSAGE INDEX
16815 screen to draw more slowly when in a newsgroup.
16816 <P>
16817 Look "<A HREF="h_rule_patterns">here</A>"
16818 for more information on Patterns.
16819 <P>
16820 Look <A HREF="h_edit_nav_cmds">here</A>
16821 to see the available Editing and Navigation commands.
16822 <P>
16823 <End of help on this topic>
16824 </BODY>
16825 </HTML>
16826 ======= h_config_other_fldr_type =======
16827 <HTML>
16828 <HEAD>
16829 <TITLE>Current Folder Type Explained</TITLE>
16830 </HEAD>
16831 <BODY>
16832 <H1>Current Folder Type Explained</H1>
16834 The Current Folder Type is part of the rule's Pattern.
16835 It refers to the type of the folder being viewed.
16836 In order for a rule to be considered a match, the current folder must
16837 be of the type you set here.
16838 The three types "Any", "News", and "Email" are
16839 all what you might think.
16840 <P>
16841 If the Current Folder Type for a Pattern is set to "News", for
16842 example, then
16843 that Pattern will only match if the current folder is a newsgroup.
16844 The value "Specific" may be used when you want to limit the match
16845 to a specific folder (not just a specific type of folder), or to a list of
16846 specific folders.
16847 <P>
16848 In order to match a specific folder you Select the "Specific"
16849 button <EM>AND</EM> fill in
16850 the name (or list of names) of
16851 the folder in the "Folder List" field.
16852 If the current folder is any of the folders in the list, that is considered
16853 a match.
16854 The name of each folder in the list may be either "INBOX", the technical specification
16855 of the folder (like what appears in your configuration file) or, if the
16856 folder is one of your incoming folders, it may be the nickname you've given
16857 the folder.
16858 Here are a couple samples of specific folder names:
16859 <P>
16860 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
16861 <P>
16862 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
16863 <P>
16864 The easiest way to fill in the "Folder List" field is to use
16865 the T command that is available when the "Folder List" line is
16866 highlighted.
16867 Note that you won't be able to edit the "Folder List" line unless the
16868 Current Folder Type is set to "Specific", and any value that
16869 "Folder List" has is ignored unless the type
16870 is set to "Specific".
16871 <P>
16872 Look "<A HREF="h_rule_patterns">here</A>"
16873 for more information on Patterns.
16874 <P>
16875 Look <A HREF="h_edit_nav_cmds">here</A>
16876 to see the available Editing and Navigation commands.
16877 <P>
16878 <End of help on this topic>
16879 </BODY>
16880 </HTML>
16881 ======= h_config_incol_fldr_type =======
16882 <HTML>
16883 <HEAD>
16884 <TITLE>Current Folder Type Explained</TITLE>
16885 </HEAD>
16886 <BODY>
16887 <H1>Current Folder Type Explained</H1>
16889 The Current Folder Type is part of the Line Coloring rule's Pattern.
16890 It refers to the type of the folder for which the MESSAGE INDEX is
16891 being viewed.
16892 In order for a rule to be considered a match, the current folder must
16893 be of the type you set here.
16894 The three types "Any", "News", and "Email" are
16895 all what you might think.
16896 <P>
16897 If the Current Folder Type for a Pattern is set to "News", for
16898 example, then
16899 that Pattern will only match if the current folder is a newsgroup and
16900 the rest of the Pattern matches.
16901 The value "Specific" may be used when you want to limit the match
16902 to a specific folder (not just a specific type of folder), or to a list of
16903 specific folders.
16904 <P>
16905 In order to match a specific folder you Select the "Specific"
16906 button <EM>AND</EM> fill in
16907 the name (or list of names) of
16908 the folder in the "Folder List" field.
16909 If the current folder is any of the folders in the list, that is considered
16910 a match.
16911 The name of each folder in the list may be either "INBOX", the technical specification
16912 of the folder (like what appears in your configuration file) or, if the
16913 folder is one of your incoming folders, it may be the nickname you've given
16914 the folder.
16915 Here are a couple samples of specific folder names:
16916 <P>
16917 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
16918 <P>
16919 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
16920 <P>
16921 The easiest way to fill in the "Folder List" field is to use
16922 the T command that is available when the "Folder List" line is
16923 highlighted.
16924 Note that you won't be able to edit the "Folder List" line unless the
16925 Current Folder Type is set to "Specific", and any value that
16926 "Folder List" has is ignored unless the type
16927 is set to "Specific".
16928 <P>
16929 When reading a newsgroup, there may be a performance penalty
16930 incurred when collecting the information necessary to check a Pattern.
16931 For this reason, the default Current Folder Type is set to "Email".
16932 For example, a rule with a non-Normal Index Line Color
16933 and a Current Folder Type of
16934 "Any" or "News" may cause the MESSAGE INDEX
16935 screen to draw more slowly when in a newsgroup.
16936 <P>
16937 Look "<A HREF="h_rule_patterns">here</A>"
16938 for more information on Patterns.
16939 <P>
16940 Look <A HREF="h_edit_nav_cmds">here</A>
16941 to see the available Editing and Navigation commands.
16942 <P>
16943 <End of help on this topic>
16944 </BODY>
16945 </HTML>
16946 ======= h_config_filt_fldr_type =======
16947 <HTML>
16948 <HEAD>
16949 <TITLE>Current Folder Type Explained</TITLE>
16950 </HEAD>
16951 <BODY>
16952 <H1>Current Folder Type Explained</H1>
16954 The Current Folder Type is part of the Filtering rule's Pattern.
16955 It refers to the type of the folder for which the filtering is being done.
16956 In order for a rule to be considered a match, the current folder must
16957 be of the type you set here.
16958 The three types "Any", "News", and "Email" are
16959 all what you might think.
16960 <P>
16961 If the Current Folder Type for a Pattern is set to "News", for
16962 example, then
16963 that Pattern will only match if the current folder is a newsgroup and
16964 the rest of the Pattern matches.
16965 The value "Specific" may be used when you want to limit the match
16966 to a specific folder (not just a specific type of folder), or to a list of
16967 specific folders.
16968 <P>
16969 In order to match a specific folder you Select the "Specific"
16970 button <EM>AND</EM> fill in
16971 the name (or list of names) of
16972 the folder in the "Folder List" field.
16973 If the current folder is any of the folders in the list, that is considered
16974 a match.
16975 The name of each folder in the list may be either "INBOX", the technical specification
16976 of the folder (like what appears in your configuration file) or, if the
16977 folder is one of your incoming folders, it may be the nickname you've given
16978 the folder.
16979 Here are a couple samples of specific folder names:
16980 <P>
16981 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
16982 <P>
16983 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
16984 <P>
16985 The easiest way to fill in the "Folder List" field is to use
16986 the T command that is available when the "Folder List" line is
16987 highlighted.
16988 Note that you won't be able to edit the "Folder List" line unless the
16989 Current Folder Type is set to "Specific", and any value that
16990 "Folder List" has is ignored unless the type
16991 is set to "Specific".
16992 <P>
16993 When reading a newsgroup, there may be a performance penalty
16994 incurred when collecting the information necessary to check a Pattern.
16995 For this reason, the default Current Folder Type is set to "Email".
16996 For example, a rule with a Current Folder Type of either
16997 "Any" or "News" may cause the filtering to happen
16998 more slowly when opening a newsgroup.
16999 <P>
17000 Look "<A HREF="h_rule_patterns">here</A>"
17001 for more information on Patterns.
17002 <P>
17003 Look <A HREF="h_edit_nav_cmds">here</A>
17004 to see the available Editing and Navigation commands.
17005 <P>
17006 <End of help on this topic>
17007 </BODY>
17008 </HTML>
17009 ======= h_config_role_stat_imp =======
17010 <HTML>
17011 <HEAD>
17012 <TITLE>Message Important Status Explained</TITLE>
17013 </HEAD>
17014 <BODY>
17015 <H1>Message Important Status Explained</H1>
17017 This part of the Pattern may have one of three possible values.
17018 The default value is "Don't care", which matches any message.
17019 The other two values are "Yes", which means the message must be
17020 flagged "Important" in order to be a match; or "No", which
17021 means the message must <EM>not</EM> be flagged "Important" in order
17022 to be a match.
17023 <P>
17024 Look "<A HREF="h_rule_patterns">here</A>"
17025 for more information on Patterns.
17026 <P>
17027 Look <A HREF="h_edit_nav_cmds">here</A>
17028 to see the available Editing and Navigation commands.
17029 <P>
17030 <End of help on this topic>
17031 </BODY>
17032 </HTML>
17033 ======= h_config_role_stat_new =======
17034 <HTML>
17035 <HEAD>
17036 <TITLE>Message New Status Explained</TITLE>
17037 </HEAD>
17038 <BODY>
17039 <H1>Message New Status Explained</H1>
17041 This part of the Pattern may have one of three possible values.
17042 The default value is "Don't care", which matches any message.
17043 The other two values are "Yes", which means the message must be
17044 "New" in order to be a match; or "No", which
17045 means the message must <EM>not</EM> be "New" in order
17046 to be a match.
17047 "New" is the same as <EM>Unseen</EM> and not "New" is the
17048 same as <EM>Seen</EM>.
17049 <P>
17050 The nomenclature for New and Recent is a bit confusing:
17051 <P>
17052 New means that the message is Unseen.
17053 It could have been in your mailbox for a long time but if you haven't looked
17054 at it, it is still considered New.
17055 That matches the default Alpine index display that shows an N for such a
17056 message.
17057 <P>
17058 Recent means that the message was added to this folder since the last time
17059 you opened the folder.
17060 Alpine also shows an N by default for these types of messages.
17061 If you were to run two copies of Alpine that opened a folder one right after
17062 the other, a message would only show up as Recent in (at most) the first
17063 Alpine session.
17064 <P>
17065 Look "<A HREF="h_rule_patterns">here</A>"
17066 for more information on Patterns.
17067 <P>
17068 Look <A HREF="h_edit_nav_cmds">here</A>
17069 to see the available Editing and Navigation commands.
17070 <P>
17071 <End of help on this topic>
17072 </BODY>
17073 </HTML>
17074 ======= h_config_role_stat_recent =======
17075 <HTML>
17076 <HEAD>
17077 <TITLE>Message Recent Status Explained</TITLE>
17078 </HEAD>
17079 <BODY>
17080 <H1>Message Recent Status Explained</H1>
17082 This part of the Pattern may have one of three possible values.
17083 The default value is "Don't care", which matches any message.
17084 The other two values are "Yes", which means the message must be
17085 "Recent" in order to be a match; or "No", which
17086 means the message must <EM>not</EM> be "Recent" in order
17087 to be a match.
17088 "Recent" means that the message was added to the folder since
17089 the last time the folder was opened.
17090 If more than one mail client has the folder opened, the message will
17091 appear to be "Recent" to only one of the clients.
17092 <P>
17093 The nomenclature for New and Recent is a bit confusing:
17094 <P>
17095 New means that the message is Unseen.
17096 It could have been in your mailbox for a long time but if you haven't looked
17097 at it, it is still considered New.
17098 That matches the default Alpine index display that shows an N for such a
17099 message.
17100 <P>
17101 Recent means that the message was added to this folder since the last time
17102 you opened the folder.
17103 Alpine also shows an N by default for these types of messages.
17104 If you were to run two copies of Alpine that opened a folder one right after
17105 the other, a message would only show up as Recent in (at most) the first
17106 Alpine session.
17107 <P>
17108 Look "<A HREF="h_rule_patterns">here</A>"
17109 for more information on Patterns.
17110 <P>
17111 Look <A HREF="h_edit_nav_cmds">here</A>
17112 to see the available Editing and Navigation commands.
17113 <P>
17114 <End of help on this topic>
17115 </BODY>
17116 </HTML>
17117 ======= h_config_role_stat_del =======
17118 <HTML>
17119 <HEAD>
17120 <TITLE>Message Deleted Status Explained</TITLE>
17121 </HEAD>
17122 <BODY>
17123 <H1>Message Deleted Status Explained</H1>
17125 This part of the Pattern may have one of three possible values.
17126 The default value is "Don't care", which matches any message.
17127 The other two values are "Yes", which means the message must be
17128 marked "Deleted" in order to be a match; or "No", which
17129 means the message must <EM>not</EM> be marked "Deleted" in order
17130 to be a match.
17131 <P>
17132 If you are thinking of using this part of the Pattern as a way to prevent
17133 messages from being filtered more than once in a Filter Pattern,
17134 take a look at the Filter Option
17135 <A HREF="h_config_filt_opts_notdel">"Move-Only-if-Not-Deleted"</A>
17136 instead.
17137 It should work better than using this field since it will hide the filtered
17138 messages even if they are already Deleted.
17139 That option is at the bottom of the Filter configuration screen.
17140 <P>
17141 Look "<A HREF="h_rule_patterns">here</A>"
17142 for more information on Patterns.
17143 <P>
17144 Look <A HREF="h_edit_nav_cmds">here</A>
17145 to see the available Editing and Navigation commands.
17146 <P>
17147 <End of help on this topic>
17148 </BODY>
17149 </HTML>
17150 ======= h_config_role_stat_ans =======
17151 <HTML>
17152 <HEAD>
17153 <TITLE>Message Answered Status Explained</TITLE>
17154 </HEAD>
17155 <BODY>
17156 <H1>Message Answered Status Explained</H1>
17158 This part of the Pattern may have one of three possible values.
17159 The default value is "Don't care", which matches any message.
17160 The other two values are "Yes", which means the message must be
17161 marked "Answered" in order to be a match; or "No", which
17162 means the message must <EM>not</EM> be marked "Answered" in order
17163 to be a match.
17164 <P>
17165 Look "<A HREF="h_rule_patterns">here</A>"
17166 for more information on Patterns.
17167 <P>
17168 Look <A HREF="h_edit_nav_cmds">here</A>
17169 to see the available Editing and Navigation commands.
17170 <P>
17171 <End of help on this topic>
17172 </BODY>
17173 </HTML>
17174 ======= h_config_role_abookfrom =======
17175 <HTML>
17176 <HEAD>
17177 <TITLE>Address in Address Book Explained</TITLE>
17178 </HEAD>
17179 <BODY>
17180 <H1>Address in Address Book Explained</H1>
17182 This option gives you a way to match messages that contain an address
17183 that is in one of your address books.
17184 Only the simple entries in your address books are searched.
17185 Address book distribution lists are ignored!
17186 <P>
17187 This part of the Pattern may have one of five possible values.
17188 The default value is "Don't care", which matches any message.
17189 The value "Yes, in any address book" means at least one of the addresses
17190 from the message must be in at least one of your
17191 address books in order to be a match.
17192 The value "No, not in any address book"
17193 means none of the addresses may
17194 be in any of your address books in order to be a match.
17195 <P>
17196 The values "Yes, in specific address books" and
17197 "No, not in any of specific address books" are similar but instead
17198 of depending on all address books you are allowed to give a list of address
17199 books to look in.
17200 Usually this would be a single address book but it may be a
17201 list of address books as well.
17202 For each of these "specific" address book options you Select which
17203 of the Specific options you want (Yes or No) <EM>AND</EM> fill in the
17204 name (or list of names) of the address book in the
17205 "Abook List" field.
17206 The names to be used are those that appear in the ADDRESS BOOK LIST screen.
17207 The easiest way to fill in the Abook List field it to use
17208 the "T" command that is available when the "Abook List"
17209 line is highlighted.
17210 Note that you won't be able to edit the "Abook List" line unless the
17211 option is set to one of the two "Specific", values.
17212 <P>
17213 The addresses from the message that are checked for are determined by the
17214 setting you have for "Types of addresses to check for in address book".
17215 If you set this to "From" the From address from the message will
17216 be looked up in the address book.
17217 If you set it to "To" instead then the To addresses will be used.
17218 If any of the To addresses are in the address book then it is considered
17219 a match for "Yes" or not a match for "No".
17220 You could set it to both From and To, in which case all of the From and To
17221 addresses are used.
17222 The "Reply-To" and "Sender" cases are a little unusual.
17223 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
17224 exists or the From address if there is no Reply-To address.
17225 Same for the Sender address.
17226 <P>
17227 Look "<A HREF="h_rule_patterns">here</A>"
17228 for more information on Patterns.
17229 <P>
17230 Look <A HREF="h_edit_nav_cmds">here</A>
17231 to see the available Editing and Navigation commands.
17232 <P>
17233 <End of help on this topic>
17234 </BODY>
17235 </HTML>
17236 ======= h_config_inabook_from =======
17237 <HTML>
17238 <HEAD>
17239 <TITLE>From</TITLE>
17240 </HEAD>
17241 <BODY>
17242 <H1>From</H1>
17244 Setting the From line will cause the address from the From header line
17245 of the message to be checked for in the address book.
17246 <P>
17247 <End of help on this topic>
17248 </BODY>
17249 </HTML>
17250 ======= h_config_inabook_replyto =======
17251 <HTML>
17252 <HEAD>
17253 <TITLE>Reply-To</TITLE>
17254 </HEAD>
17255 <BODY>
17256 <H1>Reply-To</H1>
17258 Setting the Reply-To line will cause the address from the Reply-To header line
17259 of the message to be checked for in the address book.
17260 However, if there is no Reply-To header line in the message the From header
17261 line will be used instead.
17262 We understand this is dumb but we don't have an easy way around it.
17263 <P>
17264 <End of help on this topic>
17265 </BODY>
17266 </HTML>
17267 ======= h_config_inabook_sender =======
17268 <HTML>
17269 <HEAD>
17270 <TITLE>Sender</TITLE>
17271 </HEAD>
17272 <BODY>
17273 <H1>Sender</H1>
17275 Setting the Sender line will cause the address from the Sender header line
17276 of the message to be checked for in the address book.
17277 However, if there is no Sender header line in the message the From header
17278 line will be used instead.
17279 We understand this is dumb but we don't have an easy way around it.
17280 <P>
17281 <End of help on this topic>
17282 </BODY>
17283 </HTML>
17284 ======= h_config_inabook_to =======
17285 <HTML>
17286 <HEAD>
17287 <TITLE>To</TITLE>
17288 </HEAD>
17289 <BODY>
17290 <H1>To</H1>
17292 Setting the To line will cause the address from the To header line
17293 of the message to be checked for in the address book.
17294 <P>
17295 <End of help on this topic>
17296 </BODY>
17297 </HTML>
17298 ======= h_config_inabook_cc =======
17299 <HTML>
17300 <HEAD>
17301 <TITLE>CC</TITLE>
17302 </HEAD>
17303 <BODY>
17304 <H1>CC</H1>
17306 Setting the CC line will cause the address from the CC header line
17307 of the message to be checked for in the address book.
17308 <P>
17309 <End of help on this topic>
17310 </BODY>
17311 </HTML>
17312 ======= h_config_role_stat_8bitsubj =======
17313 <HTML>
17314 <HEAD>
17315 <TITLE>Raw 8-bit in Subject Explained</TITLE>
17316 </HEAD>
17317 <BODY>
17318 <H1>Raw 8-bit in Subject Explained</H1>
17320 It seems that lots of unwanted email contains unencoded 8-bit characters
17321 in the Subject.
17322 Normally, characters with the 8th bit set are not allowed in the Subject
17323 header unless they are MIME-encoded.
17324 This option gives you a way to match messages that have Subjects that
17325 contain unencoded 8-bit characters.
17326 <P>
17327 This part of the Pattern may have one of three possible values.
17328 The default value is "Don't care", which matches any message.
17329 The other two values are "Yes", which means the Subject of
17330 the message must contain unencoded 8-bit characters (characters with the
17331 most significant bit set)
17332 in order to be a match; or "No", which
17333 means the Subject must <EM>not</EM>
17334 contain unencoded 8-bit characters in order to be a match.
17335 <P>
17336 Look "<A HREF="h_rule_patterns">here</A>"
17337 for more information on Patterns.
17338 <P>
17339 Look <A HREF="h_edit_nav_cmds">here</A>
17340 to see the available Editing and Navigation commands.
17341 <P>
17342 <End of help on this topic>
17343 </BODY>
17344 </HTML>
17345 ======= h_config_role_bom =======
17346 <HTML>
17347 <HEAD>
17348 <TITLE>Beginning of Month</TITLE>
17349 </HEAD>
17350 <BODY>
17351 <H1>Beginning of Month</H1>
17353 This option gives you a limited ability to take different actions depending on whether
17354 this is the first time Alpine has been run this month or not.
17355 Though it would be nice to have such an option available, this is not the
17356 same as whether or not this is the first time a paricular folder has been
17357 opened this month.
17358 If you want some action (probably Filtering) to take place in a folder each
17359 month, then you will need to be sure that the folder is opened during the
17360 first Alpine session of the month in order for this option to be helpful.
17361 <P>
17362 This part of the Pattern may have one of three possible values.
17363 The default value is "Don't care", which matches any message.
17364 The other two values are "Yes", which means this is the first
17365 time Alpine has been run this month;
17366 or "No", which
17367 means this is not the first time Alpine has been run this month.
17368 <P>
17369 Look "<A HREF="h_rule_patterns">here</A>"
17370 for more information on Patterns.
17371 <P>
17372 Here are some technical details.
17373 The way that Alpine decides if it is the beginning of the month or not is
17374 to compare today's date with the date stored in the
17375 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
17376 variable in the config file.
17377 If the month of today's date is later than the month stored in the variable,
17378 then this is considered to be the first time you have run Alpine this month, and
17379 that turns the Beginning of the Month option on.
17380 <P>
17381 Look <A HREF="h_edit_nav_cmds">here</A>
17382 to see the available Editing and Navigation commands.
17383 <P>
17384 <End of help on this topic>
17385 </BODY>
17386 </HTML>
17387 ======= h_config_role_boy =======
17388 <HTML>
17389 <HEAD>
17390 <TITLE>Beginning of Year</TITLE>
17391 </HEAD>
17392 <BODY>
17393 <H1>Beginning of Year</H1>
17395 This option gives you a limited ability to take different actions depending on whether
17396 this is the first time Alpine has been run this year or not.
17397 Though it would be nice to have such an option available, this is not the
17398 same as whether or not this is the first time a paricular folder has been
17399 opened this year.
17400 If you want some action (probably Filtering) to take place in a folder each
17401 year, then you will need to be sure that the folder is opened during the
17402 first Alpine session of the year in order for this option to be helpful.
17403 <P>
17404 This part of the Pattern may have one of three possible values.
17405 The default value is "Don't care", which matches any message.
17406 The other two values are "Yes", which means this is the first
17407 time Alpine has been run this year;
17408 or "No", which
17409 means this is not the first time Alpine has been run this year.
17410 <P>
17411 Look "<A HREF="h_rule_patterns">here</A>"
17412 for more information on Patterns.
17413 <P>
17414 Here are some technical details.
17415 The way that Alpine decides if it is the beginning of the year or not is
17416 to compare today's date with the date stored in the
17417 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
17418 variable in the config file.
17419 If the year of today's date is later than the year stored in the variable,
17420 then this is considered to be the first time you have run Alpine this year, and
17421 that turns the Beginning of the Year option on.
17422 <P>
17423 Look <A HREF="h_edit_nav_cmds">here</A>
17424 to see the available Editing and Navigation commands.
17425 <P>
17426 <End of help on this topic>
17427 </BODY>
17428 </HTML>
17429 ======= h_config_role_inick =======
17430 <HTML>
17431 <HEAD>
17432 <TITLE>Initialize Values From Role Explained</TITLE>
17433 </HEAD>
17434 <BODY>
17435 <H1>Initialize Values From Role Explained</H1>
17437 This is a power user feature.
17438 You will usually want to leave this field empty.
17439 The value of this field is the nickname of another one of your roles.
17440 The Action values from that other role
17441 are used as the initial values of the Action items for this role.
17442 If you put something in any of the action fields for this role, that will
17443 override whatever was in the corresponding field of the initializer role.
17444 <P>
17445 You might use this field if the "Action" part of one of your roles
17446 is something you want to use in more than one role.
17447 Instead of filling in those action values again for each role, you
17448 may give the nickname of the role where the values are filled in.
17449 It's just a shortcut way to define Role Actions.
17450 <P>
17451 Here's an example to help explain how this works.
17452 Suppose you have a role with nickname "role1" and role1 has
17453 (among other things)
17454 <P>
17455 <CENTER><SAMP>Set Reply-To = The Pres <president@example.com></SAMP></CENTER>
17456 <P>
17457 set.
17458 If in "role2" you set "Initialize settings using role" to
17459 "role1", then role2 will inherit the Set Reply-To value
17460 from role1 by default (and any of the other inheritable action values
17461 that are set).
17462 So if role2 had
17463 <P>
17464 <CENTER><SAMP>Set Reply-To = <No Value Set></SAMP></CENTER>
17465 <P>
17466 defined, the Reply-To used with role2 would be "The Pres <president@example.com>"
17467 However, if role2 had
17468 <P>
17469 <CENTER><SAMP>Set Reply-To = VP <vicepresident@example.com></SAMP></CENTER>
17470 <P>
17471 defined, then the Reply-To used with role2 would be "VP <vicepresident@example.com>" instead.
17472 <P>
17473 If you wish,
17474 you may choose a nickname from your list of roles by using the
17475 "T" command.
17476 If the role you are using to initialize also has a role it initializes from,
17477 then that initialization happens first.
17478 That is, inheritance works as expected with the grandparent and
17479 great-grandparent (and so on) roles having the expected effect.
17480 <P>
17481 Look <A HREF="h_edit_nav_cmds">here</A>
17482 to see the available Editing and Navigation commands.
17483 <P>
17484 <End of help on this topic>
17485 </BODY>
17486 </HTML>
17487 ======= h_config_role_setfrom =======
17488 <HTML>
17489 <HEAD>
17490 <TITLE>Set From Explained</TITLE>
17491 </HEAD>
17492 <BODY>
17493 <H1>Set From Explained</H1>
17495 This describes part of the action to be taken if the Pattern for this
17496 role is a match.
17497 This field consists of a single address that will be used as the From
17498 address on the message you are sending.
17499 This should be a fully-qualified address like
17500 <P>
17501 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
17502 <P>
17503 or just
17504 <P>
17505 <CENTER><SAMP>user@domain</SAMP></CENTER>
17506 <P>
17507 If you wish,
17508 you may choose an address from your address book with the
17509 "T" command.
17510 <P>
17511 If this is left blank, then your normal From address will be used.
17512 <P>
17513 You may also find it useful to add the changed From address to the
17514 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
17515 configuration option.
17516 <P>
17517 Look <A HREF="h_edit_nav_cmds">here</A>
17518 to see the available Editing and Navigation commands.
17519 <P>
17520 <End of help on this topic>
17521 </BODY>
17522 </HTML>
17523 ======= h_config_role_setreplyto =======
17524 <HTML>
17525 <HEAD>
17526 <TITLE>Set Reply-To Explained</TITLE>
17527 </HEAD>
17528 <BODY>
17529 <H1>Set Reply-To Explained</H1>
17531 This describes part of the action to be taken if the Pattern for this
17532 role is a match.
17533 This field consists of a single address that will be used as the Reply-To
17534 address on the message you are sending.
17535 This may be a fully-qualified address like
17536 <P>
17537 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
17538 <P>
17539 or just
17540 <P>
17541 <CENTER><SAMP>user@domain</SAMP></CENTER>
17542 <P>
17543 If you wish,
17544 you may choose an address from your address book with the
17545 "T" command.
17546 <P>
17547 If this is left blank, then there won't be a Reply-To address unless
17548 you have configured one specially with the
17549 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>"
17550 configuration option.
17551 <P>
17552 Look <A HREF="h_edit_nav_cmds">here</A>
17553 to see the available Editing and Navigation commands.
17554 <P>
17555 <End of help on this topic>
17556 </BODY>
17557 </HTML>
17558 ======= h_config_role_setfcc =======
17559 <HTML>
17560 <HEAD>
17561 <TITLE>Set Fcc Explained</TITLE>
17562 </HEAD>
17563 <BODY>
17564 <H1>Set Fcc Explained</H1>
17566 This describes part of the action to be taken if the Pattern for this
17567 role is a match.
17568 This field consists of a single folder name that will be used in
17569 the Fcc field of the message you are sending.
17570 You may put anything here that you would normally type into the Fcc
17571 field from the composer.
17572 <P>
17573 In addition, an fcc of "" (two double quotation marks) means
17574 no Fcc.
17575 <P>
17576 A blank field here means that Alpine will use its normal rules for deciding
17577 the default value of the Fcc field.
17578 For many roles, perhaps most, it may make more sense for you to use the
17579 other Alpine facilities for setting the Fcc.
17580 In particular, if you want the Fcc to depend on who you are sending the
17581 message to then the <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
17582 is probably more useful.
17583 In that case, you would want to leave the Fcc field here blank.
17584 However, if you have a role that depends on who the message you are replying
17585 to was From, or what address that message was sent to;
17586 then it might make sense to set the Fcc for that role here.
17587 <P>
17588 If you wish,
17589 you may choose a folder from your folder collections by using the
17590 "T" command.
17591 <P>
17592 Look <A HREF="h_edit_nav_cmds">here</A>
17593 to see the available Editing and Navigation commands.
17594 <P>
17595 <End of help on this topic>
17596 </BODY>
17597 </HTML>
17598 ======= h_config_role_usesmtp =======
17599 <HTML>
17600 <HEAD>
17601 <TITLE>Use SMTP Server Explained</TITLE>
17602 </HEAD>
17603 <BODY>
17604 <H1>Use SMTP Server Explained</H1>
17606 This describes part of the action to be taken if the Pattern for this
17607 role is a match.
17608 If this field has a value, then it will be used as the SMTP server
17609 to send mail when this role is being used (unless the SMTP server variable
17610 is set in the system-wide fixed configuration file).
17611 It has the same semantics as the
17612 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
17613 variable in the Setup/Config screen.
17614 <P>
17615 If you are using this to post from home when you are at home and from
17616 work when you are at work you need to be careful about postponing messages.
17617 When you postpone a composition that was using a role with this variable
17618 set, the SMTP server list will be saved
17619 with the postponed composition.
17620 It cannot be changed later.
17621 Because of this, you may want to make this a list of SMTP servers
17622 with the preferred server at the front of the list and alternate servers
17623 later in the list.
17624 In your "Home" role you would put the home SMTP server first and
17625 the work SMTP server last.
17626 In your "Work" role you would put the work SMTP server first and
17627 the home SMTP server last.
17628 Then if you start a composition as "Work", postpone
17629 it, and then later resume it from home the work SMTP server will fail but
17630 the home SMTP server later in the list will succeed.
17631 <P>
17632 You may be able to simplify things by making the regular
17633 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
17634 variable in the Setup/Config screen a list instead of using roles
17635 to set the SMTP server.
17637 <P>
17638 Look <A HREF="h_edit_nav_cmds">here</A>
17639 to see the available Editing and Navigation commands.
17640 <P>
17641 <End of help on this topic>
17642 </BODY>
17643 </HTML>
17644 ======= h_config_role_usenntp =======
17645 <HTML>
17646 <HEAD>
17647 <TITLE>Use NNTP Server Explained</TITLE>
17648 </HEAD>
17649 <BODY>
17650 <H1>Use NNTP Server Explained</H1>
17652 This describes part of the action to be taken if the Pattern for this
17653 role is a match.
17654 If this field has a value, then it will be used as the NNTP server
17655 to post to newsgroups when this role is being used (unless the NNTP server
17656 variable
17657 is set in the system-wide fixed configuration file).
17658 It has the same semantics as the
17659 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
17660 variable in the Setup/Config screen.
17661 <P>
17662 This role setting can facilitate posting to the right nntp server for someone
17663 who reads news from various news sources. The feature
17664 <A HREF="h_config_predict_nntp_server">"<!--#echo var="FEAT_predict-nntp-server"-->"</A>
17665 allows for setting the correct <!--#echo var="VAR_nntp-server"--> without having to individually
17666 set a role for that <!--#echo var="VAR_nntp-server"-->, but for greater flexibility, setting
17667 nntp servers for roles may be more desirable for some people.
17668 <P>
17669 If you are using this to post from home when you are at home and from
17670 work when you are at work you need to be careful about postponing messages.
17671 When you postpone a composition that was using a role with this variable
17672 set, the NNTP server list will be saved
17673 with the postponed composition.
17674 It cannot be changed later.
17675 Because of this, you may want to make this a list of NNTP servers
17676 with the preferred server at the front of the list and alternate servers
17677 later in the list.
17678 In your "Home" role you would put the home NNTP server first and
17679 the work NNTP server last.
17680 In your "Work" role you would put the work NNTP server first and
17681 the home NNTP server last.
17682 Then if you start a composition as "Work", postpone
17683 it, and then later resume it from home the work NNTP server will fail but
17684 the home NNTP server later in the list will succeed.
17685 <P>
17686 You may be able to simplify things by making the regular
17687 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
17688 variable in the Setup/Config screen a list instead of using roles
17689 to set the NNTP server.
17691 <P>
17692 Look <A HREF="h_edit_nav_cmds">here</A>
17693 to see the available Editing and Navigation commands.
17694 <P>
17695 <End of help on this topic>
17696 </BODY>
17697 </HTML>
17698 ======= h_config_role_setotherhdr =======
17699 <HTML>
17700 <HEAD>
17701 <TITLE>Set Other Headers Explained</TITLE>
17702 </HEAD>
17703 <BODY>
17704 <H1>Set Other Headers Explained</H1>
17706 This describes part of the action to be taken if the Pattern for this
17707 role is a match.
17708 This field gives you a way to set values for headers besides
17709 "From" and "Reply-To".
17710 If you want to set either of those, use the specific
17711 "Set From" and "Set Reply-To" settings above.
17712 <P>
17713 This field is similar to the
17714 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" option.
17715 Each header you specify here must include the header tag
17716 ("To:", "Approved:", etc.)
17717 and may optionally include a value for that header.
17718 In order to see these headers when you compose using this role you
17719 must use the rich header
17720 <!--chtml if pinemode="function_key"-->(F5)
17721 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
17722 Here's an example that shows how you might set the To address.
17723 <P>
17724 <CENTER><SAMP>Set Other Hdrs = To: Full Name <user@domain></SAMP></CENTER>
17725 <P>
17726 Headers set in this way are different from headers set with the
17727 <!--#echo var="VAR_customized-hdrs"--> option in that the value you give for a header here
17728 will replace any value that already exists.
17729 For example, if you are Replying to a message there will already be at
17730 least one address in the To header (the address you are Replying to).
17731 However, if you Reply using a role that sets the To header, that role's
17732 To header value will be used instead.
17733 <P>
17734 Limitation: Because commas are used to separate the list of
17735 Other Headers, it is not possible to have the value of a
17736 header contain a comma;
17737 nor is there currently an "escape" mechanism provided
17738 to make this work.
17739 <P>
17740 Look <A HREF="h_edit_nav_cmds">here</A>
17741 to see the available Editing and Navigation commands.
17742 <P>
17743 <End of help on this topic>
17744 </BODY>
17745 </HTML>
17746 ======= h_config_role_setlitsig =======
17747 <HTML>
17748 <HEAD>
17749 <TITLE>Set Literal Signature Explained</TITLE>
17750 </HEAD>
17751 <BODY>
17752 <H1>Set Literal Signature Explained</H1>
17754 This describes part of the action to be taken if the Pattern for this
17755 role is a match.
17756 This field contains the actual text for your signature, as opposed to
17757 the name of a file containing your signature.
17758 If this is defined it takes precedence over any value set in the
17759 "Set Signature" field.
17760 <P>
17761 This is simply a different way to store the signature.
17762 The signature is stored inside your Alpine configuration file instead of in
17763 a separate file.
17764 Tokens work the same way they do with
17765 <A HREF="h_config_role_setsig">Set Signature</A>, so refer to the
17766 help text there for more information.
17767 <P>
17769 The two character sequence \n (backslash followed by
17770 the character n) will be used to signify a line-break in your signature.
17771 You don't have to enter the \n, but it will be visible in the
17772 CHANGE THIS ROLE RULE window after you are done editing the signature.
17773 <P>
17774 Look <A HREF="h_edit_nav_cmds">here</A>
17775 to see the available Editing and Navigation commands.
17776 <P>
17777 <End of help on this topic>
17778 </BODY>
17779 </HTML>
17780 ======= h_config_role_setsig =======
17781 <HTML>
17782 <HEAD>
17783 <TITLE>Set Signature Explained</TITLE>
17784 </HEAD>
17785 <BODY>
17786 <H1>Set Signature Explained</H1>
17788 This describes part of the action to be taken if the Pattern for this
17789 role is a match.
17790 <P>
17791 If either the default <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A>
17792 option from Setup/Config
17793 or the "Set LiteralSig" option for this role are defined,
17794 then this option will be ignored.
17795 You can tell that that is the case because the value of this
17796 option will show up as
17797 <P>
17798 <CENTER><SAMP><Ignored: using LiteralSig instead></SAMP></CENTER>
17799 <P>
17800 You may either use all Literal Signatures (signatures stored in your
17801 configuration file) throughout Alpine, or all signature files.
17802 You can't mix the two.
17803 <P>
17804 This field consists of a filename that will be used as the signature
17805 file when using this role.
17806 <P>
17807 If the filename is followed by a vertical bar (|) then instead
17808 of reading the contents of the file the file is assumed to be a
17809 program that will produce the text to be used on its standard output.
17810 The program can't have any arguments and doesn't receive any input from Alpine,
17811 but the rest of the processing works as if the contents came from a file.
17812 <P>
17813 Instead of storing the data in a local file, the
17814 signature data may be stored remotely in an IMAP folder.
17815 In order to do this,
17816 you must use a remote name for the signature.
17817 A remote signature name might look like:
17818 <P>
17819 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
17820 <P>
17822 The syntax used here is the same as the syntax used for a remote
17823 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
17824 Note that you may not access an existing signature file remotely,
17825 you have to create a new <EM>folder</EM> that contains the signature data.
17826 If the name you use here for the signature data is a remote name, then when
17827 you edit the file using the "F" command the data will
17828 be saved remotely in the folder.
17829 You aren't required to do anything special to create the folder, it
17830 gets created if you use a remote name.
17832 <P>
17833 If you type "F" you may edit the contents of the file (as opposed to
17834 the name of the file) you have specified.
17835 If you type "T" you may use a browser to choose an existing filename.
17836 <P>
17837 Besides containing regular text, a signature file may also
17838 contain (or a signature program may produce) tokens that are replaced with text
17839 that depends on the message you are replying to or forwarding.
17840 The tokens all look like _word_ (a word surrounded by underscores).
17841 For example, if the token
17842 <P>
17843 <CENTER><SAMP>_DATE_</SAMP></CENTER>
17844 <P>
17845 is included in the text of the signature file, then when you reply to
17846 or forward a message, the token will be replaced with the actual date
17847 the message you are replying to or forwarding was sent.
17848 <P>
17849 If you use a role that has a signature file for a plain composition
17850 (that is, not a reply or forward) then there is no original message, so
17851 any tokens that depend on the message will be replaced with nothing.
17852 So if you want a signature file to be useful for new compositions it
17853 shouldn't include any of the tokens that depend on the message being
17854 replied to or forwarded.
17855 <P>
17856 The list of available tokens is
17857 <A HREF="h_index_tokens">here</A>.
17858 <P>
17859 Actually, for the adventurous, there is a way to conditionally include text based
17860 on whether or not a token would result in specific replacement text.
17861 For example, you could include some text based on whether or not
17862 the _NEWS_ token would result in any newsgroups if it was used.
17863 It's explained in detail
17864 <A HREF="h_reply_token_conditionals">here</A>.
17865 <P>
17866 In the very unlikely event that you want to include a literal token in
17867 a signature file, you must precede it with a backslash character.
17868 For example, to include the literal text _DATE_ you must actually use
17869 \_DATE_.
17870 It is not possible to have a literal backslash followed by an expanded token.
17871 <P>
17872 A blank field here means that Alpine will use its normal rules for deciding
17873 which file (if any) to use for the signature file.
17874 <P>
17875 An alternate method for storing the signature is available in
17876 <A HREF="h_config_role_setlitsig">Set Literal Signature</A>.
17877 <P>
17878 Look <A HREF="h_edit_nav_cmds">here</A>
17879 to see the available Editing and Navigation commands.
17880 <P>
17881 <End of help on this topic>
17882 </BODY>
17883 </HTML>
17884 ======= h_config_role_settempl =======
17885 <HTML>
17886 <HEAD>
17887 <TITLE>Set Template Explained</TITLE>
17888 </HEAD>
17889 <BODY>
17890 <H1>Set Template Explained</H1>
17892 This describes part of the action to be taken if the Pattern for this
17893 role is a match.
17894 This field consists of a filename that will be used as the template
17895 file when using this role.
17896 The template file is a file that is included at the top of the message you
17897 are composing.
17898 <P>
17899 If the filename is followed by a vertical bar (|) then instead
17900 of reading the contents of the file the file is assumed to be a
17901 program that will produce the text to be used on its standard output.
17902 The program can't have any arguments and doesn't receive any input from Alpine,
17903 but the rest of the processing works as if the contents came from a file.
17904 <P>
17905 Instead of storing the data in a local file, the
17906 template may be stored remotely in an IMAP folder.
17907 In order to do this,
17908 you must use a remote name for the template.
17909 A remote template name might look like:
17910 <P>
17911 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/templ3</SAMP></CENTER>
17912 <P>
17914 The syntax used here is the same as the syntax used for a remote
17915 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
17916 Note that you may not access an existing template file remotely,
17917 you have to create a new <EM>folder</EM> that contains the template data.
17918 If the name you use here for the template is a remote name, then when
17919 you edit the file using the "F" command the data will
17920 be saved remotely in the folder.
17921 You aren't required to do anything special to create the folder, it
17922 gets created if you use a remote name.
17923 <P>
17924 If you type "F" you may edit the contents of the file (as opposed to
17925 the name of the file) you have specified.
17926 If you type "T" you may use a browser to choose an existing filename.
17927 <P>
17928 Besides containing regular text, the template file may also
17929 contain (or a template file program may produce) tokens that are replaced with text
17930 that depends on the message you are replying to or forwarding.
17931 The tokens all look like _word_ (a word surrounded by underscores).
17932 For example, if the token
17933 <P>
17934 <CENTER><SAMP>_DATE_</SAMP></CENTER>
17935 <P>
17936 is included in the text of the template file, then when you reply to
17937 or forward a message, the token will be replaced with the actual date
17938 the message you are replying to or forwarding was sent.
17939 <P>
17940 If you use a role that has a template file for a plain composition
17941 (that is, not a reply or forward) then there is no original message, so
17942 any tokens that depend on the message will be replaced with nothing.
17943 So if you want a template file to be useful for new compositions it
17944 shouldn't include any of the tokens that depend on the message being
17945 replied to or forwarded.
17946 <P>
17947 The list of available tokens is
17948 <A HREF="h_index_tokens">here</A>.
17949 <P>
17950 Actually, for the adventurous, there is a way to conditionally include text based
17951 on whether or not a token would result in specific replacement text.
17952 For example, you could include some text based on whether or not
17953 the _NEWS_ token would result in any newsgroups if it was used.
17954 It's explained in detail
17955 <A HREF="h_reply_token_conditionals">here</A>.
17956 <P>
17957 In the very unlikely event that you want to include a literal token in
17958 a template file, you must precede it with a backslash character.
17959 For example, to include the literal text _DATE_ you must actually use
17960 \_DATE_.
17961 It is not possible to have a literal backslash followed by an expanded token.
17962 <P>
17963 A blank template field means that Alpine will not use a template file when
17964 this role is being used.
17965 <P>
17966 Look <A HREF="h_edit_nav_cmds">here</A>
17967 to see the available Editing and Navigation commands.
17968 <P>
17969 <End of help on this topic>
17970 </BODY>
17971 </HTML>
17972 ======= h_config_filt_stat_imp =======
17973 <HTML>
17974 <HEAD>
17975 <TITLE>Set Important Status Explained</TITLE>
17976 </HEAD>
17977 <BODY>
17978 <H1>Set Important Status Explained</H1>
17980 This describes part of the action to be taken if the Pattern for this
17981 filter is a match.
17982 If set to "Don't change it" then this does nothing.
17983 If set to "Set this state" then the Important flag is set
17984 for the matching message.
17985 If set to "Clear this state" then the Important flag is cleared
17986 for the matching message.
17987 The important flag usually causes an asterisk to show up in the MESSAGE
17988 INDEX.
17989 It may also be useful when selecting a set of messages
17990 with the Select command.
17991 <P>
17992 Look <A HREF="h_edit_nav_cmds">here</A>
17993 to see the available Editing and Navigation commands.
17994 <P>
17995 <End of help on this topic>
17996 </BODY>
17997 </HTML>
17998 ======= h_config_filt_stat_new =======
17999 <HTML>
18000 <HEAD>
18001 <TITLE>Set New Status Explained</TITLE>
18002 </HEAD>
18003 <BODY>
18004 <H1>Set New Status Explained</H1>
18006 This describes part of the action to be taken if the Pattern for this
18007 filter is a match.
18008 If set to "Don't change it" then this does nothing.
18009 If set to "Set this state" then the
18010 matching message is marked New.
18011 If set to "Clear this state" then the
18012 matching message is marked Seen.
18013 <P>
18014 Look <A HREF="h_edit_nav_cmds">here</A>
18015 to see the available Editing and Navigation commands.
18016 <P>
18017 <End of help on this topic>
18018 </BODY>
18019 </HTML>
18020 ======= h_config_filt_stat_ans =======
18021 <HTML>
18022 <HEAD>
18023 <TITLE>Set Answered Status Explained</TITLE>
18024 </HEAD>
18025 <BODY>
18026 <H1>Set Answered Status Explained</H1>
18028 This describes part of the action to be taken if the Pattern for this
18029 filter is a match.
18030 If set to "Don't change it" then this does nothing.
18031 If set to "Set this state" then the Answered flag is set
18032 for the matching message.
18033 If set to "Clear this state" then the Answered flag is cleared
18034 for the matching message.
18035 <P>
18036 Look <A HREF="h_edit_nav_cmds">here</A>
18037 to see the available Editing and Navigation commands.
18038 <P>
18039 <End of help on this topic>
18040 </BODY>
18041 </HTML>
18042 ======= h_config_filt_stat_del =======
18043 <HTML>
18044 <HEAD>
18045 <TITLE>Set Deleted Status Explained</TITLE>
18046 </HEAD>
18047 <BODY>
18048 <H1>Set Deleted Status Explained</H1>
18050 This describes part of the action to be taken if the Pattern for this
18051 filter is a match.
18052 If set to "Don't change it" then this does nothing.
18053 If set to "Set this state" then the
18054 matching message is marked Deleted.
18055 If set to "Clear this state" then the
18056 matching message is marked UnDeleted.
18057 <P>
18058 You should not use this option unless you are prepared to have matching
18059 messages expunged from the folder permanently.
18060 For example, if you type the Expunge command, this filter is applied
18061 before the expunge, so matching messages will be marked Deleted and then
18062 will be permanently expunged from the folder.
18063 However, since the index isn't redrawn in between the time that the message
18064 is marked Deleted and the time that you are asked to expunge, the only
18065 indication that you are expunging the message comes in the number of messages
18066 being expunged.
18067 The same thing may happen when you close a folder.
18068 It is also possible that an expunge not initiated by you will
18069 delete matching messages.
18070 <P>
18071 Look <A HREF="h_edit_nav_cmds">here</A>
18072 to see the available Editing and Navigation commands.
18073 <P>
18074 <End of help on this topic>
18075 </BODY>
18076 </HTML>
18077 ======= h_config_role_scoreval =======
18078 <HTML>
18079 <HEAD>
18080 <TITLE>Score Value Explained</TITLE>
18081 </HEAD>
18082 <BODY>
18083 <H1>Score Value Explained</H1>
18085 A message's score is the sum of the Score Values from all of the Scoring rules
18086 with Patterns that match the message.
18087 The value you give here is the Score Value associated with this rule.
18088 A Score Value is an integer between -100 and 100, with the default
18089 value of zero.
18090 <P>
18091 Alternatively, if the
18092 <A HREF="h_config_role_scorehdrtok">"Score From Header"</A>
18093 field is defined
18094 (on the line right below the "Score Value" field)
18095 then the "Score Value" is ignored and
18096 the "Score From Header" field is used instead.
18097 <P>
18098 Look <A HREF="h_edit_nav_cmds">here</A>
18099 to see the available Editing and Navigation commands.
18100 <P>
18101 <End of help on this topic>
18102 </BODY>
18103 </HTML>
18104 ======= h_config_role_scorehdrtok =======
18105 <HTML>
18106 <HEAD>
18107 <TITLE>Score Value From Header Explained</TITLE>
18108 </HEAD>
18109 <BODY>
18110 <H1>Score Value From Header Explained</H1>
18112 This option provides a way to use a number that appears in the headers of your
18113 messages as the message's score, or as a component of that score.
18114 If this field is defined then it is used instead of the "Score Value".
18115 The idea behind this option is that there may be a score embedded in the
18116 headers of messages that has already been calculated outside of Alpine.
18117 For example, messages delivered to you may contain an "X-Spam" header and
18118 somewhere in that header there is a score.
18119 <P>
18120 The value for this option is the name of the header followed by parentheses
18121 with two arguments inside:
18122 <P>
18123 <CENTER><SAMP>HeaderName(field_number,field_separators)</SAMP></CENTER>
18124 <P>
18125 No space is allowed between the comma and the start of the field_separators.
18126 It would be interpreted as the first separator if it was there.
18127 Field 0 is the whole line, Field 1 is the data up to the first separator, Field 2
18128 starts after that and goes to the second separator, and so on.
18129 It's easier to explain with examples.
18130 <P>
18131 <CENTER><SAMP>X-Spam(2," ")</SAMP></CENTER>
18132 <P>
18133 In the above example the header that is used is the "X-Spam" header.
18134 The value of that header (the part after the colon and the space) is split
18135 into fields separated by spaces.
18136 <P>
18137 <CENTER><SAMP>Field1 <space> Field2 <space> Field3 ...</SAMP></CENTER>
18138 <P>
18139 The second field is selected and converted to an integer. It only makes sense
18140 if Field2 really is an integer.
18141 <P>
18142 Here's an example of a SpamAssassin header.
18143 The exact look of the header will vary, but if your incoming mail
18144 contains headers that look like the following
18145 <P>
18146 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
18147 <P>
18148 you might want to use the hits value as a score.
18149 Since the score is an integer value you can't make use of the decimal part of
18150 the number, but
18151 you might split off the hits=10 part as a score by using the characters "="
18152 and "." as your separators.
18153 <P>
18154 <CENTER><SAMP>X-Spam-Status(2,"=.")</SAMP></CENTER>
18155 <P>
18156 The first field starts with the Y in Yes and goes until the "=" after
18157 hits.
18158 The second field is "10" so the score value would be 10.
18159 <P>
18160 Another example we've seen has headers that look like
18161 <P>
18162 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
18163 <P>
18164 Because there are two equals before the 7% the value
18165 <P>
18166 <CENTER><SAMP>X-Spam(3,"=%")</SAMP></CENTER>
18167 <P>
18168 should capture the probability as the score.
18169 <P>
18170 The Score From Header scoring value actually works just like the
18171 regular Score Value in that the rest of the pattern has to match before
18172 it is used and the scores from all the different scoring rules that
18173 match for a particular message are added together.
18174 When using the Score From Header method it may (or may not) make sense to
18175 use only a single scoring rule with a pattern that matches every message.
18176 <P>
18177 Look <A HREF="h_edit_nav_cmds">here</A>
18178 to see the available Editing and Navigation commands.
18179 <P>
18180 <End of help on this topic>
18181 </BODY>
18182 </HTML>
18183 ======= h_config_role_replyuse =======
18184 <HTML>
18185 <HEAD>
18186 <TITLE>Reply Use Explained</TITLE>
18187 </HEAD>
18188 <BODY>
18189 <H1>Reply Use Explained</H1>
18191 This option determines how this particular role will be used when Replying
18192 to a message.
18193 There are three possible values for this option.
18194 The value "Never"
18195 means that this role will not be a candidate for use when Replying.
18196 The role's Pattern will not be checked for a match, however the role will
18197 be available to be manually switched to if there is a confirmation prompt.
18198 <P>
18200 The options "With confirmation" and "Without confirmation"
18201 mean that you do want to consider this role when Replying.
18202 For either of these settings, the role's Pattern will be compared with
18203 the message being replied to.
18204 If there is a match then this role will either be used without confirmation
18205 or will be the default when confirmation is asked for, depending on
18206 which of the two options is selected.
18207 If confirmation is requested, you will also have a chance to
18208 manually change the role to any one of your other roles.
18209 <P>
18211 You won't be prompted for confirmation if none of your role Patterns
18212 match the message being replied to.
18213 This is independent of the value of the current option.
18214 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18215 feature may be used to change this behavior.
18216 <P>
18217 <End of help on this topic>
18218 </BODY>
18219 </HTML>
18220 ======= h_config_role_forwarduse =======
18221 <HTML>
18222 <HEAD>
18223 <TITLE>Forward Use Explained</TITLE>
18224 </HEAD>
18225 <BODY>
18226 <H1>Forward Use Explained</H1>
18228 This option determines how this particular role will be used when Forwarding
18229 a message.
18230 There are three possible values for this option.
18231 The value "Never"
18232 means that this role will not be a candidate for use when Forwarding.
18233 The role's Pattern will not be checked for a match, however the role will
18234 be available to be manually switched to if there is a confirmation prompt.
18235 <P>
18237 The options "With confirmation" and "Without confirmation"
18238 mean that you do want to consider this role when Forwarding.
18239 For either of these settings, the role's Pattern will be compared with
18240 the message being forwarded.
18241 If there is a match then this role will either be used without confirmation
18242 or will be the default when confirmation is asked for, depending on
18243 which of the two options is selected.
18244 If confirmation is requested, you will also have a chance to
18245 manually change the role to any one of your other roles.
18246 <P>
18248 You won't be prompted for confirmation if none of your role Patterns
18249 match the message being forwarded.
18250 This is independent of the value of the current option.
18251 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18252 feature may be used to change this behavior.
18253 <P>
18254 <End of help on this topic>
18255 </BODY>
18256 </HTML>
18257 ======= h_config_role_composeuse =======
18258 <HTML>
18259 <HEAD>
18260 <TITLE>Compose Use Explained</TITLE>
18261 </HEAD>
18262 <BODY>
18263 <H1>Compose Use Explained</H1>
18265 This option determines how this particular role will be used when Composing
18266 a new message using the "Compose" command.
18267 This does not affect what happens when using the "Role" command
18268 to compose a new message.
18269 The "Role" command allows you to select a role from all of the
18270 roles you have defined, regardless of what Uses you've assigned to those
18271 roles.
18272 <P>
18274 There are three possible values for this option.
18275 The value "Never"
18276 means that this role will not be a candidate for use when Composing.
18277 The role's Current Folder Type will not be checked for a match, however the role
18278 will be available to be manually switched to if there is a confirmation prompt.
18279 <P>
18281 The options "With confirmation" and "Without confirmation"
18282 mean that you do want to consider this role when Composing.
18283 For either of these settings,
18284 the role's Current Folder Type will be checked (since there is no message
18285 to compare with, the rest of the Pattern is considered a match).
18286 If there is a match then this role will either be used without confirmation
18287 or will be the default when confirmation is asked for, depending on
18288 which of the two options is selected.
18289 If confirmation is requested, you will also have a chance to
18290 manually change the role to any one of your other roles.
18291 <P>
18293 When using the Compose command the role checking is a little different
18294 because there is no message being replied to or forwarded.
18295 Because of this the Current Folder Type is checked but the header pattern
18296 fields, the AllText pattern, the BodyText pattern, and the Score Interval are all ignored.
18297 A role is considered to be a match if it is a candidate for Compose Use and
18298 its Current Folder Type matches the currently open folder.
18299 This could be useful if you want to set a role based on the folder you
18300 are reading, or the type of folder you are reading.
18301 <P>
18303 You won't be prompted for confirmation if none of your role Patterns
18304 are a match.
18305 This is independent of the value of the current option.
18306 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18307 feature may be used to change this behavior.
18308 <P>
18309 <End of help on this topic>
18310 </BODY>
18311 </HTML>
18312 ======= h_config_filter_folder =======
18313 <HTML>
18314 <HEAD>
18315 <TITLE>Filter Folder Explained</TITLE>
18316 </HEAD>
18317 <BODY>
18318 <H1>Filter Folder Explained</H1>
18320 When the Filter Action is set to "Move",
18321 the folder or folders specified here will be used to store messages matching
18322 the provided pattern.
18324 <P>
18325 If you set the Filter Action to "Move" you must give a folder name
18326 here.
18328 <P>
18329 If you wish,
18330 you may choose a folder from your folder collections by using the
18331 "T" command.
18332 <P>
18333 Besides regular text, the folder name may also contain
18334 tokens that are replaced with text representing the current date
18335 when you run Alpine.
18336 For example, if the folder name you use is
18337 <P>
18338 <CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER>
18339 <P>
18340 that is replaced with something like
18341 <P>
18342 <CENTER><SAMP>abc-2004-oct</SAMP></CENTER>
18343 <P>
18344 Or,
18345 <P>
18346 <CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER>
18347 <P>
18348 becomes
18349 <P>
18350 <CENTER><SAMP>abc-04-10</SAMP></CENTER>
18351 <P>
18352 The token names must be surrounded by underscores in order to be recognized
18353 as tokens.
18354 The tokens that may be used are those that are derived from the current date.
18355 They're listed near the bottom of the list of tokens give
18356 <A HREF="h_index_tokens">here</A>.
18357 <P>
18358 Look "<A HREF="h_rule_patterns">here</A>"
18359 for more information on Patterns.
18360 <P>
18361 Look <A HREF="h_edit_nav_cmds">here</A>
18362 to see the available Editing and Navigation commands.
18363 <P>
18364 <End of help on this topic>
18365 </BODY>
18366 </HTML>
18367 ======= h_config_filter_kw_set =======
18368 <HTML>
18369 <HEAD>
18370 <TITLE>Set These Keywords Explained</TITLE>
18371 </HEAD>
18372 <BODY>
18373 <H1>Set These Keywords Explained</H1>
18375 This describes part of the action to be taken if the Pattern for this
18376 filter is a match.
18377 Read a little about keywords in the help text for the
18378 <A HREF="h_common_flag">Flag</A> command.
18379 This option is a list of keywords that will be Set when there is a match.
18380 If you wish, you may choose keywords from the list of keywords you have
18381 defined with the "T" command.
18382 You may add new keywords by defining them in the
18383 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
18384 If you have given a keyword a nickname when configuring it,
18385 that nickname may be used instead of the actual keyword.
18387 <P>
18388 Look <A HREF="h_edit_nav_cmds">here</A>
18389 to see the available Editing and Navigation commands.
18390 <P>
18391 <End of help on this topic>
18392 </BODY>
18393 </HTML>
18394 ======= h_config_filter_kw_clr =======
18395 <HTML>
18396 <HEAD>
18397 <TITLE>Clear These Keywords Explained</TITLE>
18398 </HEAD>
18399 <BODY>
18400 <H1>Clear These Keywords Explained</H1>
18402 This describes part of the action to be taken if the Pattern for this
18403 filter is a match.
18404 Read a little about keywords in the help text for the
18405 <A HREF="h_common_flag">Flag</A> command.
18406 This option is a list of keywords that will be Cleared when there is a match.
18407 If you wish, you may choose keywords from the list of keywords you have
18408 defined with the "T" command.
18409 You may add new keywords by defining them in the
18410 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
18411 If you have given a keyword a nickname when configuring it,
18412 that nickname may be used instead of the actual keyword.
18414 <P>
18415 Look <A HREF="h_edit_nav_cmds">here</A>
18416 to see the available Editing and Navigation commands.
18417 <P>
18418 <End of help on this topic>
18419 </BODY>
18420 </HTML>
18421 ======= h_index_tokens =======
18422 <HTML>
18423 <HEAD>
18424 <TITLE>Tokens for Index and Replying</TITLE>
18425 </HEAD>
18426 <BODY>
18428 This set of special tokens may be used in the
18429 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option,
18430 in the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
18431 in signature files,
18432 in template files used in
18433 <A HREF="h_rules_roles">"roles"</A>, and in the folder name
18434 that is the target of a Filter Rule.
18435 Some of them aren't available in all situations.
18436 <P>
18437 The tokens are used as they appear below for the "<!--#echo var="VAR_index-format"-->"
18438 option, but they must be surrounded by underscores for the
18439 "<!--#echo var="VAR_reply-leadin"-->" option, in signature and template files,
18440 and in the target of Filter Rules.
18441 <P>
18442 <P>
18444 <H1><EM>Tokens Available for all Cases (except Filter Rules)</EM></H1>
18446 <DL>
18447 <DT>SUBJECT</DT>
18448 <DD>
18449 This token represents the Subject the sender gave the message.
18450 Alternatives for use in the index screen are
18451 SUBJKEY, SUBJKEYINIT, SUBJECTTEXT, SUBJKEYTEXT, and SUBJKEYINITTEXT.
18452 You may color the subject text in the MESSAGE INDEX screen differently by using the
18453 <A HREF="h_config_index_subject_color">Index Subject Color</A> and the
18454 <A HREF="h_config_index_opening_color">Index Opening Color</A>
18455 options available from
18456 the <A HREF="h_color_setup">Setup Kolor</A> screen.
18457 </DD>
18459 <DT>FROM</DT>
18460 <DD>
18461 This token represents the personal name (or email address if the name
18462 is unavailable) of the person specified in the message's "From:"
18463 header field.
18464 You may color the from text in the MESSAGE INDEX screen differently by using the
18465 <A HREF="h_config_index_from_color">Index From Color</A>
18466 option available from
18467 the <A HREF="h_color_setup">Setup Kolor</A> screen.
18468 </DD>
18470 <DT>ADDRESS</DT>
18471 <DD>
18472 This is similar to the "FROM" token, only it is always the
18473 email address, never the personal name.
18474 For example, "mailbox@domain".
18475 </DD>
18477 <DT>MAILBOX</DT>
18478 <DD>
18479 This is the same as the "ADDRESS" except that the
18480 domain part of the address is left off.
18481 For example, "mailbox".
18482 </DD>
18484 <DT>SENDER</DT>
18485 <DD>
18486 This token represents the personal name (or email address) of the person
18487 listed in the message's "Sender:" header field.
18488 </DD>
18490 <DT>TO</DT>
18491 <DD>
18492 This token represents the personal names (or email addresses if the names
18493 are unavailable) of the persons specified in the
18494 message's "To:" header field.
18495 </DD>
18497 <DT>NEWSANDTO</DT>
18498 <DD>
18499 This token represents the newsgroups from the
18500 message's "Newsgroups:" header field <EM>and</EM>
18501 the personal names (or email addresses if the names
18502 are unavailable) of the persons specified in the
18503 message's "To:" header field.
18504 </DD>
18506 <DT>TOANDNEWS</DT>
18507 <DD>
18508 Same as "NEWSANDTO" except in the opposite order.
18509 </DD>
18511 <DT>NEWS</DT>
18512 <DD>
18513 This token represents the newsgroups from the
18514 message's "Newsgroups:" header field.
18515 </DD>
18517 <DT>CC</DT>
18518 <DD>
18519 This token represents the personal names (or email addresses if the names
18520 are unavailable) of the persons specified in the
18521 message's "Cc:" header field.
18522 </DD>
18524 <DT>RECIPS</DT>
18525 <DD>
18526 This token represents the personal names (or email addresses if the names
18527 are unavailable) of the persons specified in both the
18528 message's "To:" header field and
18529 the message's "Cc:" header field.
18530 </DD>
18532 <DT>NEWSANDRECIPS</DT>
18533 <DD>
18534 This token represents the newsgroups from the
18535 message's "Newsgroups:" header field <EM>and</EM>
18536 the personal names (or email addresses if the names
18537 are unavailable) of the persons specified in the
18538 message's "To:" and "Cc:" header fields.
18539 </DD>
18541 <DT>RECIPSANDNEWS</DT>
18542 <DD>
18543 Same as "NEWSANDRECIPS" except in the opposite order.
18544 </DD>
18546 <DT>INIT</DT>
18547 <DD>
18548 This token represents the initials from the personal name
18549 of the person specified in the message's "From:"
18550 header field.
18551 If there is no personal name, it is blank.
18552 </DD>
18554 <DT>DATE</DT>
18555 <DD>
18556 This token represents the date on which the message was sent, according
18557 to the "Date" header field.
18558 It has the format MMM DD. For example, "Oct 23".
18559 The feature
18560 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>,
18561 which adjusts for the timezone the message was sent from,
18562 may have an affect on the value of this token as well as the values of
18563 all of the other DATE or TIME tokens.
18564 Some of the DATE and TIME tokens are displayed in a locale-specific
18565 way unless the option
18566 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is set.
18567 </DD>
18569 <DT>SMARTDATE</DT>
18570 <DD>
18571 This token represents the date on which the message was sent, according
18572 to the "Date" header field.
18573 It is "Today" if the message was sent today,
18574 "Yesterday" for yesterday,
18575 "Wednesday" if it was last Wednesday, and so on. If the
18576 message is from last year and is more than six months old it includes the year, as well.
18577 See the SMARTDATE alternatives below, as well.
18578 </DD>
18580 <DT>SMARTTIME</DT>
18581 <DD>
18582 This token represents the most relevant elements of the date on which
18583 the message was sent (according to the "Date" header field),
18584 in a compact form. If the message was sent today, only the time is used
18585 (e.g. "9:22am", "10:07pm"); if it was sent during
18586 the past week, the day of the week and the hour are used
18587 (e.g. "Wed09am", "Thu10pm"); other dates are
18588 given as date, month, and year (e.g. "23Aug00",
18589 "9Apr98").
18590 </DD>
18592 <DT>SMARTDATETIME</DT>
18593 <DD>
18594 This is a combination of SMARTDATE and SMARTTIME.
18595 It is SMARTDATE unless the SMARTDATE value is "Today", in which
18596 case it is SMARTTIME.
18597 See the SMARTDATETIME alternatives below, as well.
18598 </DD>
18600 <DT>DATEISO</DT>
18601 <DD>
18602 This token represents the date on which the message was sent, according
18603 to the "Date" header field.
18604 It has the format YYYY-MM-DD. For example, "1998-10-23".
18605 </DD>
18607 <DT>SHORTDATEISO</DT>
18608 <DD>
18609 This token represents the date on which the message was sent, according
18610 to the "Date" header field.
18611 It has the format YY-MM-DD. For example, "98-10-23".
18612 </DD>
18614 <DT>SHORTDATE1</DT>
18615 <DD>
18616 This token represents the date on which the message was sent, according
18617 to the "Date" header field.
18618 It has the format MM/DD/YY. For example, "10/23/98".
18619 </DD>
18621 <DT>SHORTDATE2</DT>
18622 <DD>
18623 This token represents the date on which the message was sent, according
18624 to the "Date" header field.
18625 It has the format DD/MM/YY. For example, "23/10/98".
18626 </DD>
18628 <DT>SHORTDATE3</DT>
18629 <DD>
18630 This token represents the date on which the message was sent, according
18631 to the "Date" header field.
18632 It has the format DD.MM.YY. For example, "23.10.98".
18633 </DD>
18635 <DT>SHORTDATE4</DT>
18636 <DD>
18637 This token represents the date on which the message was sent, according
18638 to the "Date" header field.
18639 It has the format YY.MM.DD. For example, "98.10.23".
18640 </DD>
18642 <DT>LONGDATE</DT>
18643 <DD>
18644 This token represents the date on which the message was sent, according
18645 to the "Date" header field.
18646 It has the format MMM DD, YYYY. For example, "Oct 23, 1998".
18647 </DD>
18649 <DT>SMARTDATE alternatives</DT>
18650 <DD>
18651 There are several versions of SMARTDATE that are all the same except
18652 for the way they format dates far in the past.
18653 SMARTDATE formats the date using the information from your locale settings
18654 to format the date string. It may end up formatting dates so that they look
18655 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
18656 The feature
18657 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
18658 may have an affect on the values of these tokens.
18659 If you want more control you may use one of the following.
18660 <DL>
18661 <DT>SMARTDATE</DT> <DD>If the option
18662 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
18663 then this will be locale specific. Control this with the
18664 LC_TIME locale setting on a UNIX system. On Windows
18665 the Regional Options control panel may be used to set the Short date
18666 format. At the programming level, the strftime routine is what Alpine
18667 uses to print the date.
18668 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
18669 to SMARTDATES1.</DD>
18670 <DT>SMARTDATEISO</DT> <DD>DATEISO format. See text above.</DD>
18671 <DT>SMARTDATESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
18672 <DT>SMARTDATES1</DT> <DD>SHORTDATE1 format.</DD>
18673 <DT>SMARTDATES2</DT> <DD>SHORTDATE2 format.</DD>
18674 <DT>SMARTDATES3</DT> <DD>SHORTDATE3 format.</DD>
18675 <DT>SMARTDATES4</DT> <DD>SHORTDATE4 format.</DD>
18676 </DL>
18677 </DD>
18679 <DT>SMARTDATETIME alternatives</DT>
18680 <DD>
18681 There are several versions of SMARTDATETIME that are all very similar.
18682 The ones that end in 24 use a 24-hour clock for Today's messages instead
18683 of a 12-hour clock.
18684 The other variation is
18685 for the way they format dates far in the past.
18686 SMARTDATETIME and SMARTDATETIME24 format the date using the information from your locale settings
18687 to format the date string. It may end up formatting dates so that they look
18688 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
18689 The feature
18690 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
18691 may have an affect on the values of these tokens.
18692 The possible choices are:
18693 <DL>
18694 <DT>SMARTDATETIME</DT> <DD>If the option
18695 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
18696 then this will be locale specific. Control this with the
18697 LC_TIME locale setting on a UNIX system. On Windows
18698 the Regional Options control panel may be used to set the Short date
18699 format. At the programming level, the strftime routine is what Alpine
18700 uses to print the date.
18701 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
18702 to SMARTDATETIMES1.</DD>
18703 <DT>SMARTDATETIME24</DT> <DD>Use TIME24 for Today</DD>
18704 <DT>SMARTDATETIMEISO</DT> <DD>DATEISO format. See text above.</DD>
18705 <DT>SMARTDATETIMEISO24</DT> <DD>Use TIME24 for Today</DD>
18706 <DT>SMARTDATETIMESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
18707 <DT>SMARTDATETIMESHORTISO24</DT> <DD>Use TIME24 for Today</DD>
18708 <DT>SMARTDATETIMES1</DT> <DD>SHORTDATE1 format.</DD>
18709 <DT>SMARTDATETIMES124</DT> <DD>Use TIME24 for Today</DD>
18710 <DT>SMARTDATETIMES2</DT> <DD>SHORTDATE2 format.</DD>
18711 <DT>SMARTDATETIMES224</DT> <DD>Use TIME24 for Today</DD>
18712 <DT>SMARTDATETIMES3</DT> <DD>SHORTDATE3 format.</DD>
18713 <DT>SMARTDATETIMES324</DT> <DD>Use TIME24 for Today</DD>
18714 <DT>SMARTDATETIMES4</DT> <DD>SHORTDATE4 format.</DD>
18715 <DT>SMARTDATETIMES424</DT> <DD>Use TIME24 for Today</DD>
18716 </DL>
18717 </DD>
18719 <DT>DAYDATE</DT>
18720 <DD>
18721 This token represents the date on which the message was sent, according
18722 to the "Date" header field.
18723 It looks like "Sat, 23 Oct 1998".
18724 This token is never converted in any locale-specific way.
18725 </DD>
18727 <DT>PREFDATE</DT>
18728 <DD>
18729 This token represents the date on which the message was sent, according
18730 to the "Date" header field.
18731 It is your operating system's idea of the preferred date representation for the current locale.
18732 Internally it uses the %x version of the date from the strftime routine.
18733 </DD>
18735 <DT>PREFTIME</DT>
18736 <DD>
18737 This token represents the time at which the message was sent, according
18738 to the "Date" header field.
18739 It is the preferred time representation for the current locale.
18740 Internally it uses the %X version of the time from the strftime routine.
18741 </DD>
18743 <DT>PREFDATETIME</DT>
18744 <DD>
18745 This token represents the date and time at which the message was sent, according
18746 to the "Date" header field.
18747 It is the preferred date and time representation for the current locale.
18748 Internally it uses the %c version of the time from the strftime routine.
18749 </DD>
18751 <DT>DAY</DT>
18752 <DD>
18753 This token represents the day of the month on which the message was sent,
18754 according to the "Date" header field.
18755 For example, "23" or "9".
18756 </DD>
18758 <DT>DAY2DIGIT</DT>
18759 <DD>
18760 This token represents the day of the month on which the message was sent,
18761 according to the "Date" header field.
18762 For example, "23" or "09".
18763 It is always 2 digits.
18764 </DD>
18766 <DT>DAYORDINAL</DT>
18767 <DD>
18768 This token represents the ordinal number that is the day of
18769 the month on which the message was sent,
18770 according to the "Date" header field.
18771 For example, "23rd" or "9th".
18772 </DD>
18774 <DT>DAYOFWEEK</DT>
18775 <DD>
18776 This token represents the day of the week on which the message was sent,
18777 according to the "Date" header field.
18778 For example, "Sunday" or "Wednesday".
18779 </DD>
18781 <DT>DAYOFWEEKABBREV</DT>
18782 <DD>
18783 This token represents the day of the week on which the message was sent,
18784 according to the "Date" header field.
18785 For example, "Sun" or "Wed".
18786 </DD>
18788 <DT>MONTHABBREV</DT>
18789 <DD>
18790 This token represents the month the message was sent, according
18791 to the "Date" header field.
18792 For example, "Oct".
18793 </DD>
18795 <DT>MONTHLONG</DT>
18796 <DD>
18797 This token represents the month in which the message was sent, according
18798 to the "Date" header field.
18799 For example, "October".
18800 </DD>
18802 <DT>MONTH</DT>
18803 <DD>
18804 This token represents the month in which the message was sent, according
18805 to the "Date" header field.
18806 For example, "10" or "9".
18807 </DD>
18809 <DT>MONTH2DIGIT</DT>
18810 <DD>
18811 This token represents the month in which the message was sent, according
18812 to the "Date" header field.
18813 For example, "10" or "09".
18814 It is always 2 digits.
18815 </DD>
18817 <DT>YEAR</DT>
18818 <DD>
18819 This token represents the year the message was sent, according
18820 to the "Date" header field.
18821 For example, "1998" or "2001".
18822 </DD>
18824 <DT>YEAR2DIGIT</DT>
18825 <DD>
18826 This token represents the year the message was sent, according
18827 to the "Date" header field.
18828 For example, "98" or "01".
18829 It is always 2 digits.
18830 </DD>
18832 <DT>TIME24</DT>
18833 <DD>
18834 This token represents the time at which the message was sent, according
18835 to the "Date" header field.
18836 There is no adjustment made for different time zones, so you'll get
18837 the time the message was sent according to the time zone the sender
18838 was in.
18839 It has the format HH:MM. For example, "17:28".
18840 </DD>
18842 <DT>TIME12</DT>
18843 <DD>
18844 This token represents the time at which the message was sent, according
18845 to the "Date" header field.
18846 This time is for a 12 hour clock.
18847 It has the format HH:MMpm.
18848 For example, "5:28pm" or "11:13am".
18849 </DD>
18851 <DT>TIMEZONE</DT>
18852 <DD>
18853 This token represents the numeric timezone from
18854 the "Date" header field.
18855 It has the format [+-]HHMM. For example, "-0800".
18856 </DD>
18858 </DL>
18860 <P>
18861 <H1><EM>Tokens Available Only for <!--#echo var="VAR_index-format"--></EM></H1>
18863 <DL>
18864 <DT>MSGNO</DT>
18865 <DD>
18866 This token represents the message's current position in the folder that,
18867 of course, may change as the folder is sorted or new mail arrives.
18868 </DD>
18870 <DT>STATUS</DT>
18871 <DD>
18872 This token represents a three character wide field displaying various
18873 aspects of the message's state.
18874 The first character is either blank,
18875 a '*' for message marked Important, or a '+' indicating a message
18876 addressed directly to you (as opposed to your having received it via a
18877 mailing list, for example).
18878 When the feature
18879 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>"
18880 is set, if the first character would have been
18881 blank then it will instead be a '-' if the message is cc'd to you.
18882 The second character is typically blank,
18883 though the arrow cursor may occupy it if either the
18884 "<A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>"
18885 or the
18886 "<A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A>" feature
18887 is set (or you actually are on a slow link).
18888 The third character is either '<A HREF="h_flag_deleted">D</A>' (Deleted),
18889 '<A HREF="h_flag_answered">A</A>' (Answered),
18890 '<A HREF="h_flag_forwarded">F</A>' (Forwarded),
18891 '<A HREF="h_flag_new">N</A>' (New), or blank.
18892 <P>
18893 If you are using a threaded view of the index and this message is at the
18894 top of a collapsed portion of a thread,
18895 then this token refers to all of the messages in the collapsed portion of
18896 the thread instead of just the top message.
18897 The first character will be a '*' if <EM>any</EM> of the messages in the thread
18898 are marked Important, else a '+' if any of the messages are addressed
18899 to you, else a '-' if any of the messages are cc'd to you.
18900 The third character will be a 'D' if <EM>all</EM> of the messages
18901 in the collapsed thread are marked deleted,
18902 an 'A' if <EM>all</EM> of the messages
18903 in the collapsed thread are marked answered,
18904 it will be an 'N' if any of
18905 the messages are undeleted and unseen, and it will be blank otherwise.
18906 </DD>
18908 <DT>FULLSTATUS</DT>
18909 <DD>
18910 This token represents a less abbreviated alternative
18911 to the "STATUS" token.
18912 It is six characters wide.
18913 The first character is '+', '-', or blank, the
18914 second blank, the third either '*' or blank, the fourth
18915 '<A HREF="h_flag_new">N</A>' or blank,
18916 the fifth '<A HREF="h_flag_answered">A</A>'
18917 or blank, and the sixth character is
18918 either '<A HREF="h_flag_deleted">D</A>' or
18919 blank.
18920 <P>
18921 If you are using a threaded view of the index and this message is at the
18922 top of a collapsed portion of a thread,
18923 then this token refers to all of the messages in the collapsed portion of
18924 the thread instead of just the top message.
18925 The first character is '+', '-', or blank depending on whether <EM>any</EM>
18926 of the messages in the collapsed thread are addressed to you or cc'd to you.
18927 The third character will be '*' if any of the messages are marked
18928 Important.
18929 The fourth character will be 'N' if all of the messages in the thread
18930 are New, else 'n' if some of the messages in the thread are New, else blank.
18931 The fifth character will be 'A' or 'a' or blank, and the sixth character
18932 will be 'D' or 'd' or blank.
18933 </DD>
18935 <DT>IMAPSTATUS</DT>
18936 <DD>
18937 This token represents an even less abbreviated alternative to the
18938 "STATUS" token.
18939 It differs from "FULLSTATUS" in only the fourth character, which is
18940 an 'N' if the message is new to this folder since the last time
18941 it was opened <EM>and</EM> it has not been viewed, an 'R' (Recent) if the message
18942 is new to the folder and has been viewed, a 'U' (Unseen) if the message is not
18943 new to the folder since it was last opened <EM>but</EM> has not been
18944 viewed, or a blank if the message has been in the folder since it was
18945 last opened and has been viewed.
18946 <P>
18947 If you are using a threaded view of the index and this message is at the
18948 top of a collapsed portion of a thread,
18949 then the fourth character will be
18950 'N' if all of the messages in the thread are unseen and recent;
18951 else 'n' if some of the messages in the thread are unseen and recent;
18952 else 'U' if all of the messages in the thread are unseen and not recent;
18953 else 'u' if some of the messages in the thread are unseen and not recent;
18954 else 'R' if all of the messages in the thread are seen and recent;
18955 else 'r' if some of the messages in the thread are seen and recent;
18956 else blank.
18957 </DD>
18959 <DT>SHORTIMAPSTATUS</DT>
18960 <DD>
18961 This is the same as the last four of the six characters of IMAPSTATUS,
18962 so the '+' To Me information will be missing.
18963 </DD>
18965 <DT>SIZE</DT>
18966 <DD>
18967 This token represents the total size, in bytes, of the message.
18968 If a "K" (Kilobyte)
18969 follows the number, the size is approximately 1,000
18970 times that many bytes (rounded to the nearest 1,000).
18971 If an "M" (Megabyte) follows the number, the size is approximately
18972 1,000,000 times that many bytes.
18973 Commas are not used in this field.
18974 This field is seven characters wide, including the enclosing parentheses.
18975 Sizes are rounded when "K" or "M" is present.
18976 The progression of sizes used looks like:
18978 <P>
18979 <CENTER><SAMP>0 1 ... 9999 10K ... 999K 1.0M ... 99.9M 100M ... 2000M</SAMP></CENTER>
18980 <P>
18981 </DD>
18983 <DT>SIZECOMMA</DT>
18984 <DD>
18985 This token represents the total size, in bytes, of the message.
18986 If a "K" (Kilobyte)
18987 follows the number, the size is approximately 1,000
18988 times that many bytes (rounded to the nearest 1,000).
18989 If an "M" (Megabyte) follows the number, the size is approximately
18990 1,000,000 times that many bytes.
18991 Commas are used if the number shown is 1,000 or greater.
18992 The SIZECOMMA field is one character wider than the SIZE field.
18993 Sizes are rounded when "K" or "M" is present.
18994 The progression of sizes used looks like:
18996 <P>
18997 <CENTER><SAMP>0 1 ... 99,999 100K ... 9,999K 10.0M ... 999.9M 1,000M ... 2,000M</SAMP></CENTER>
18998 <P>
18999 </DD>
19001 <DT>KSIZE</DT>
19002 <DD>
19003 This token represents the total size of the message, expressed in
19004 kilobytes or megabytes, as most appropriate.
19005 These are 1,024 byte kilobytes and 1,024 x 1,024 byte megabytes.
19006 The progression of sizes used looks like:
19008 <P>
19009 <CENTER><SAMP>0K 1K ... 1023K 1.0M ... 99.9M 100M ... 2047M</SAMP></CENTER>
19010 <P>
19011 </DD>
19013 <DT>SIZENARROW</DT>
19014 <DD>
19015 This token represents the total size, in bytes, of the message.
19016 If a "K" (Kilobyte)
19017 follows the number, the size is approximately 1,000
19018 times that many bytes.
19019 If an "M" (Megabyte) follows the number, the size is approximately
19020 1,000,000 times that many bytes.
19021 If a "G" (Gigabyte) follows the number, the size is approximately
19022 1,000,000,000 times that many bytes.
19023 This field uses only five characters of screen width, including the enclosing
19024 parentheses.
19025 The progression of sizes used looks like:
19027 <P>
19028 <CENTER><SAMP>0 1 ... 999 1K ... 99K .1M ... .9M 1M ... 99M .1G ... .9G 1G 2G</SAMP></CENTER>
19029 <P>
19030 </DD>
19032 <DT>DESCRIPSIZE</DT>
19033 <DD>
19034 This token is intended to represent a more useful description of the
19035 message than just its size, but it isn't very useful at this point.
19036 The plus sign in this view means there are attachments.
19037 Note that including this token in
19038 the "<!--#echo var="VAR_index-format"-->" could slow down the
19039 display a little while Alpine collects the necessary information.
19040 </DD>
19042 <DT>SUBJKEY</DT>
19043 <DD>
19044 This token is the same as the SUBJECT token unless keywords are set for
19045 the message.
19046 In that case, a list of keywords enclosed in braces will be prepended to
19047 the subject of the message.
19048 Only those keywords that you have defined in your
19049 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19050 in Setup/Config are considered in the list.
19051 In other words, keywords that have been set by some other means, perhaps
19052 by another email program, won't show up unless included in
19053 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19054 Having this set in the <!--#echo var="VAR_index-format"--> will also cause the keywords to be
19055 prepended to the subject in the MESSAGE TEXT screen.
19056 If you have given a keyword a nickname
19057 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19058 instead of the actual keyword.
19059 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19060 option may be used to modify this token slightly.
19061 It is also possible to color keywords in the index using the
19062 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19063 </DD>
19065 <DT>SUBJKEYINIT</DT>
19066 <DD>
19067 This token is the same as the SUBJKEY token except that instead of
19068 prepending a list of keywords to the subject, a list of first initials
19069 of keywords will be prepended instead.
19070 For example, if a message has the keywords <EM>Work</EM> and <EM>Now</EM>
19071 set (or Work and Now are the Alpine nicknames of keywords that are set)
19072 then the SUBJKEY token would cause a result like
19073 <P>
19074 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
19075 <P>
19076 whereas the SUBJKEYINIT token would give
19077 <P>
19078 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
19079 <P>
19080 Only those keywords that you have defined in your
19081 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19082 in Setup/Config are considered in the list.
19083 In other words, keywords that have been set by some other means, perhaps
19084 by another email program, won't show up unless included in
19085 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19086 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19087 option may be used to modify this token slightly.
19088 It is also possible to color keywords in the index using the
19089 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19090 </DD>
19092 <DT>SUBJECTTEXT</DT>
19093 <DD>
19094 Same as SUBJECT but if there is room in the Subject field for more text,
19095 the opening part of the text of the message is displayed after the subject.
19096 The time needed to fetch the text may cause a performance problem
19097 which can, of course, be avoided by using the SUBJECT version of
19098 the Subject instead.
19099 You may color this opening text differently by using the
19100 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19101 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19102 You may adjust the characters that are displayed between the Subject and the
19103 opening text with the option
19104 <A HREF="h_config_opening_sep"><!--#echo var="VAR_opening-text-separator-chars"--></A>.
19105 </DD>
19107 <DT>SUBJKEYTEXT</DT>
19108 <DD>
19109 Same as SUBJKEY but with the opening message text.
19110 </DD>
19112 <DT>OPENINGTEXT</DT>
19113 <DD>
19114 This is similar to SUBJECTTEXT.
19115 Instead of combining the Subject and the opening text in a single
19116 field in the index screen this token allows you to allocate a
19117 separate column just for the opening text of the message.
19118 The time needed to fetch this text may cause a performance problem.
19119 You may color this opening text differently by using the
19120 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19121 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19122 </DD>
19124 <DT>OPENINGTEXTNQ</DT>
19125 <DD>
19126 This is very similar to OPENINGTEXT.
19127 The NQ stands for No Quotes.
19128 The only difference is that quoted text (lines beginning with >) is deleted.
19129 For some messages this may be confusing.
19130 For example, a message might have a line preceding some quoted
19131 text that reads something like "On May 8th person A said."
19132 That no longer makes sense after the quoted text is deleted and it
19133 will appear that person A said whatever the text after the quote
19134 is, even though that is really person B talking.
19135 </DD>
19137 <DT>SUBJKEYINITTEXT</DT>
19138 <DD>
19139 Same as SUBJKEYINIT but with the opening message text.
19140 </DD>
19142 <DT>KEY</DT>
19143 <DD>
19144 This is a space-delimited list of keywords that are set for the message.
19145 Only those keywords that you have defined in your
19146 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19147 in Setup/Config are considered in the list.
19148 In other words, keywords that have been set by some other means, perhaps
19149 by another email program, won't show up unless included in
19150 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19151 If you have given a keyword a nickname
19152 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19153 instead of the actual keyword.
19154 It is also possible to color keywords in the index using the
19155 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19156 This token defaults to an arbitrary width of 5.
19157 You should set it to whatever width suits you using something
19158 like KEY(17) in the <!--#echo var="VAR_index-format"-->.
19159 </DD>
19161 <DT>KEYINIT</DT>
19162 <DD>
19163 This is a list of keyword initials that are set for the message.
19164 If you have given a keyword a nickname
19165 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), the initial of that nickname
19166 is displayed instead of the initial of the actual keyword.
19167 It is also possible to color keyword initials in the index using the
19168 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19169 This token defaults to an arbitrary width of 2.
19170 You should set it to whatever width suits you using something
19171 like KEYINIT(3) in the <!--#echo var="VAR_index-format"-->.
19172 </DD>
19174 <DT>PRIORITY</DT>
19175 <DD>
19176 The X-Priority header is a non-standard header that is used in a
19177 somewhat standard way by many mail programs.
19178 Alpine expects the value of this header to be a digit with a value
19179 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
19180 Since this priority is something that the sender sets it is only an indication
19181 of the priority that the sender attaches to the mail and it is therefore almost
19182 totally unreliable for use as a filtering criterion.
19183 This token will display the numeric value of the priority if it is between
19184 1 and 5.
19185 It will be suppressed (blank) if the value is 3, which is normal priority.
19186 This token may be colored with the
19187 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19188 </DD>
19190 <DT>PRIORITYALPHA</DT>
19191 <DD>
19192 This is a more verbose interpretation of the X-Priority field.
19193 Once again nothing is displayed unless the value of the field
19194 is 1, 2, 4, or 5.
19195 The values displayed for those values are:
19196 <P>
19197 <TABLE>
19198 <TR> <TD>1</TD> <TD>Highest</TD> </TR>
19199 <TR> <TD>2</TD> <TD>High</TD> </TR>
19200 <TR> <TD>4</TD> <TD>Low</TD> </TR>
19201 <TR> <TD>5</TD> <TD>Lowest</TD> </TR>
19202 </TABLE>
19203 <P>
19204 This token may be colored with the
19205 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19206 </DD>
19208 <DT>PRIORITY!</DT>
19209 <DD>
19210 This is a one character, non-numeric version of the X-Priority field.
19211 If the value of the X-Priority header is 1 or 2 an exclamation
19212 point is displayed.
19213 If the value is 4 or 5 a "v" (think down arrow) is displayed.
19214 This token may be colored with the
19215 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19216 </DD>
19218 <DT>ATT</DT>
19219 <DD>
19220 This is a one column wide field that represents the number of attachments
19221 a message has. It will be blank if there are no attachments, a single
19222 digit for one to nine attachments, or an asterisk for more than nine.
19223 Note that including this token in
19224 the "<!--#echo var="VAR_index-format"-->" could slow down the
19225 display a little while Alpine collects the necessary information.
19226 </DD>
19228 <DT>FROMORTO</DT>
19229 <DD>
19230 This token represents <EM>either</EM> the personal name (or email address) of
19231 the person listed in the message's "From:" header
19232 field, <EM>or</EM>, if that address is yours or one of your
19233 <A HREF="h_config_alt_addresses">alternate addresses</A>,
19234 the first person specified in the
19235 message's "To:" header field
19236 with the prefix "To: " prepended.
19237 If the from address is yours and there is also no "To" address,
19238 Alpine will use the address on the "Cc" line.
19239 If there is no address there, either, Alpine will look for a newsgroup name
19240 from the "Newsgroups" header field and put
19241 that after the "To: " prefix.
19242 </DD>
19244 <DT>FROMORTONOTNEWS</DT>
19245 <DD>
19246 This is almost the same as <EM>FROMORTO</EM>.
19247 The difference is that newsgroups aren't considered.
19248 When a message is from you, doesn't have a To or Cc, and does have
19249 a Newsgroups header; this token will be your name instead of the name
19250 of the newsgroup (like it would be with FROMORTO).
19251 </DD>
19253 <DT>TEXT</DT>
19254 <DD>
19255 This is a different sort of token.
19256 It allows you to display a label within each index line.
19257 It will be the same fixed text for each line.
19258 It is different from all the other tokens in that there is no space column
19259 displayed after this token.
19260 Instead, it is butted up against the following field.
19261 It also has a different syntax.
19262 The text to display is given following a colon after the
19263 word "TEXT".
19264 For example,
19265 <P>
19266 <CENTER><SAMP>TEXT:abc=</SAMP></CENTER>
19267 <P>
19268 would insert the literal text "abc=" (without the quotes)
19269 into the index display line.
19270 You must quote the text if it includes space characters, like
19271 <P>
19272 <CENTER><SAMP>TEXT:"abc = "</SAMP></CENTER>
19273 <P>
19274 </DD>
19276 <DT>HEADER</DT>
19277 <DD>
19278 This allows you to display the text from a particular header line in the
19279 message.
19280 The syntax for this token is substantially different from all the others
19281 in order that you might be able to display a portion of the text following
19282 a particular header.
19283 The header name you are interested in is given following a colon
19284 after the word "HEADER".
19285 For example,
19286 <P>
19287 <CENTER><SAMP>HEADER:X-Spam</SAMP></CENTER>
19288 <P>
19289 would display the text of the X-Spam header, if any.
19290 Like for other index tokens a width field may (and probably should)
19291 follow this.
19292 <P>
19293 <CENTER><SAMP>HEADER:X-Spam(10)</SAMP></CENTER>
19294 <P>
19295 displays the first ten characters of the X-Spam header.
19296 Unlike other index tokens, the syntax for HEADER is more flexible.
19297 An optional second argument comes after a comma inside the parentheses.
19298 It specifies the "field" number.
19299 By default, the field separator is a space character.
19300 No extra space characters are allowed in the argument list.
19301 <P>
19302 <CENTER><SAMP>HEADER:X-Spam(10,2)</SAMP></CENTER>
19303 <P>
19304 would display the second field, left-justified, in a 10 character
19305 wide field.
19306 The second field would consist of all the text after the first space
19307 up to the next space or the end of the header.
19308 The default field number is zero, which stands for the entire line.
19309 There is also an optional third argument that is a list of field
19310 separators. It defaults to a space character.
19311 The example
19312 <P>
19313 <CENTER><SAMP>HEADER:X-Spam(10,2,:% )</SAMP></CENTER>
19314 <P>
19315 would cause the field separators to be any of colon, percent,
19316 or space (there is a space character between the percent and the
19317 right parenthesis).
19318 The first field runs from the start of the header value up to the first
19319 colon, percent, or space; the second goes from there to the next; and so on.
19320 In order to use a comma character as a field separator you must escape
19321 it by preceding it with a backslash (\).
19322 The same is true of the backslash character itself.
19323 There is one further optional argument.
19324 It is an R or an L to specify right or left adjustment of the text
19325 within the field.
19326 The default is to left justify, however if you are displaying numbers
19327 you might prefer to right justify.
19328 <P>
19329 Here's an example of a SpamAssassin header.
19330 The exact look of the header will vary, but if your incoming mail
19331 contains headers that look like the following
19332 <P>
19333 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
19334 <P>
19335 you might want to display the hits value.
19336 The first field starts with the Y in Yes.
19337 To get what you're interested in you might use "=" and
19338 space as the field separators and display the third field, like
19339 <P>
19340 <CENTER><SAMP>HEADER:X-Spam-Status(4,3,= )</SAMP></CENTER>
19341 <P>
19342 or maybe you would break at the dot instead
19343 <P>
19344 <CENTER><SAMP>HEADER:X-Spam-Status(2,2,=.,R)</SAMP></CENTER>
19345 <P>
19346 Another example we've seen has headers that look like
19347 <P>
19348 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
19349 <P>
19350 Because there are two equals and a comma before the 7% and a comma
19351 after it, the token
19352 <P>
19353 <CENTER><SAMP>HEADER:X-Spam(3,4,=\,,R)</SAMP></CENTER>
19354 <P>
19355 should display the probability (for example 7% or 83%) right justified
19356 in a 3-wide field.
19357 </DD>
19359 <DT>ARROW</DT>
19360 <DD>
19361 This gives an alternative way to display the current message in the
19362 MESSAGE INDEX screen.
19363 Usually the current message is indicated by the line being shown in
19364 reverse video.
19365 Instead, if the ARROW token is included in your <!--#echo var="VAR_index-format"-->,
19366 the current line will include an "arrow" that
19367 looks like
19368 <P>
19369 <CENTER><SAMP>-></SAMP></CENTER>
19370 <P>
19371 in the ARROW token's field.
19372 For all of the non-current messages, the ARROW field will be filled
19373 with blanks.
19374 If you use the fixed-field width feature the length of the "arrow"
19375 may be adjusted.
19376 The arrow will be drawn as width-1 dashes followed by a greater than sign.
19377 For example, if you use ARROW(3) you will get
19378 <P>
19379 <CENTER><SAMP>--></SAMP></CENTER>
19380 <P>
19381 and ARROW(1) will give you just
19382 <P>
19383 <CENTER><SAMP>></SAMP></CENTER>
19384 <P>
19385 It is also possible to set the color of the ARROW field.
19386 By default (and for non-current messages) the arrow is colored the same
19387 as the index line it is part of.
19388 You may set it to be another color with the
19389 <A HREF="h_config_index_arrow_color">Index Arrow Color</A> option available from
19390 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19391 </DD>
19393 <DT>SCORE</DT>
19394 <DD>
19395 This gives the
19396 <a href="h_rules_score">score</a>
19397 of each message.
19398 This will be six columns wide to accomodate the widest possible score.
19399 You will probably want to use the <!--#echo var="VAR_index-format"--> fixed-field width feature
19400 to limit the width of the field to the widest score that
19401 you use (e.g. SCORE(3) if your scores are always between 0 and 999).
19402 If you have not defined any score rules the scores will all be zero.
19403 If any of your score rules contain AllText or BodyText patterns
19404 then including SCORE in the <!--#echo var="VAR_index-format"-->
19405 may slow down the display of the MESSAGE INDEX screen.
19406 </DD>
19407 </DL>
19409 <P>
19410 <H1><EM>Tokens Available for all but <!--#echo var="VAR_index-format"--></EM></H1>
19412 <DL>
19413 <DT>CURNEWS</DT>
19414 <DD>
19415 This token represents the current newsgroup if there is one.
19416 For example, "comp.mail.pine".
19417 </DD>
19419 <DT>MSGID</DT>
19420 <DD>
19421 This token represents the message ID of the message.
19422 This token does not work with Filter Rule folder names.
19423 </DD>
19425 <DT>CURDATE</DT>
19426 <DD>
19427 This token represents the current date.
19428 It has the format MMM DD. For example, "Oct 23".
19429 </DD>
19431 <DT>CURDATEISO</DT>
19432 <DD>
19433 This token represents the current date.
19434 It has the format YYYY-MM-DD. For example, "1998-10-23".
19435 </DD>
19437 <DT>CURDATEISOS</DT>
19438 <DD>
19439 This token represents the current date.
19440 It has the format YY-MM-DD. For example, "98-10-23".
19441 </DD>
19443 <DT>CURPREFDATE</DT>
19444 <DD>
19445 This token represents the current date.
19446 It is your operating system's idea of the preferred date representation for the current locale.
19447 Internally it uses the %x version of the date from the strftime routine.
19448 </DD>
19450 <DT>CURPREFTIME</DT>
19451 <DD>
19452 This token represents the current time.
19453 It is the preferred time representation for the current locale.
19454 Internally it uses the %X version of the time from the strftime routine.
19455 </DD>
19457 <DT>CURPREFDATETIME</DT>
19458 <DD>
19459 This token represents the current date and time.
19460 It is the preferred date and time representation for the current locale.
19461 Internally it uses the %c version of the time from the strftime routine.
19462 </DD>
19464 <DT>CURTIME24</DT>
19465 <DD>
19466 This token represents the current time.
19467 It has the format HH:MM. For example, "17:28".
19468 </DD>
19470 <DT>CURTIME12</DT>
19471 <DD>
19472 This token represents the current time.
19473 This time is for a 12 hour clock.
19474 It has the format HH:MMpm.
19475 For example, "5:28pm" or "11:13am".
19476 </DD>
19478 <DT>CURDAY</DT>
19479 <DD>
19480 This token represents the current day of the month.
19481 For example, "23" or "9".
19482 </DD>
19484 <DT>CURDAY2DIGIT</DT>
19485 <DD>
19486 This token represents the current day of the month.
19487 For example, "23" or "09".
19488 It is always 2 digits.
19489 </DD>
19491 <DT>CURDAYOFWEEK</DT>
19492 <DD>
19493 This token represents the current day of the week.
19494 For example, "Sunday" or "Wednesday".
19495 </DD>
19497 <DT>CURDAYOFWEEKABBREV</DT>
19498 <DD>
19499 This token represents the current day of the week.
19500 For example, "Sun" or "Wed".
19501 </DD>
19503 <DT>CURMONTH</DT>
19504 <DD>
19505 This token represents the current month.
19506 For example, "10" or "9".
19507 </DD>
19509 <DT>CURMONTH2DIGIT</DT>
19510 <DD>
19511 This token represents the current month.
19512 For example, "10" or "09".
19513 It is always 2 digits.
19514 </DD>
19516 <DT>CURMONTHLONG</DT>
19517 <DD>
19518 This token represents the current month.
19519 For example, "October".
19520 </DD>
19522 <DT>CURMONTHABBREV</DT>
19523 <DD>
19524 This token represents the current month.
19525 For example, "Oct".
19526 </DD>
19528 <DT>CURYEAR</DT>
19529 <DD>
19530 This token represents the current year.
19531 For example, "1998" or "2001".
19532 </DD>
19534 <DT>CURYEAR2DIGIT</DT>
19535 <DD>
19536 This token represents the current year.
19537 For example, "98" or "01".
19538 It is always 2 digits.
19539 </DD>
19541 <DT>LASTMONTH</DT>
19542 <DD>
19543 This token represents last month.
19544 For example, if this is November (the 11th month),
19545 it is equal to "10" or if this is October (the 10th month),
19546 it is "9".
19547 It is possible that this and the other tokens beginning with LASTMONTH
19548 below could be useful when used with a Filtering Rule that
19549 has the "Beginning of Month" option set.
19550 </DD>
19552 <DT>LASTMONTH2DIGIT</DT>
19553 <DD>
19554 This token represents last month.
19555 For example, if this is November (the 11th month),
19556 it is equal to "10" or if this is October (the 10th month),
19557 it is "09".
19558 It is always 2 digits.
19559 </DD>
19561 <DT>LASTMONTHLONG</DT>
19562 <DD>
19563 This token represents last month.
19564 For example, if this is November the value is "October".
19565 </DD>
19567 <DT>LASTMONTHABBREV</DT>
19568 <DD>
19569 This token represents last month.
19570 For example, if this is November the value is "Oct".
19571 </DD>
19573 <DT>LASTMONTHYEAR</DT>
19574 <DD>
19575 This token represents what the year was a month ago.
19576 For example, if this is October, 1998, it is "1998".
19577 If this is January, 1998, it is "1997".
19578 </DD>
19580 <DT>LASTMONTHYEAR2DIGIT</DT>
19581 <DD>
19582 This token represents what the year was a month ago.
19583 For example, if this is October, 1998, it is "98".
19584 If this is January, 1998, it is "97".
19585 </DD>
19587 <DT>LASTYEAR</DT>
19588 <DD>
19589 This token represents last year.
19590 For example, if this is 1998, it equals "1997".
19591 It is possible that this
19592 could be useful when used with a Filtering Rule that
19593 has the "Beginning of Year" option set.
19594 </DD>
19596 <DT>LASTYEAR2DIGIT</DT>
19597 <DD>
19598 This token represents last year.
19599 For example, if this is 1998, it equals "97".
19600 It is always 2 digits.
19601 </DD>
19603 <DT>ROLENICK</DT>
19604 <DD>
19605 This token represents the nickname of the
19606 role currently being used. If no role is being used,
19607 then no text will be printed for this token.
19608 This token does not work with Filter Rule folder names.
19609 </DD>
19610 </DL>
19612 <P>
19613 <H1><EM>Token Available Only for <!--#echo var="VAR_reply-leadin"--></EM></H1>
19614 See the help for the
19615 <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option
19616 to see why you might want to use this.
19617 Since the <!--#echo var="VAR_reply-leadin"--> contains free text this token
19618 must be surrounded by underscores when used.
19620 <DL>
19621 <DT>NEWLINE</DT>
19622 <DD>
19623 This is an end of line marker.
19624 </DD>
19625 </DL>
19627 <P>
19628 <H1><EM>Token Available Only for Templates and Signatures</EM></H1>
19630 <DL>
19631 <DT>CURSORPOS</DT>
19632 <DD>
19633 This token is different from the others.
19634 When it is replaced it is replaced with nothing, but it sets an Alpine
19635 internal variable that tells the composer to start with the cursor
19636 positioned at the position where this token was.
19637 If both the template file and the signature file contain
19638 a "CURSORPOS" token, then the position in the template file
19639 is used.
19640 If there is a template file and neither it nor the signature file contains
19641 a "CURSORPOS" token, then the cursor is positioned
19642 after the end of the contents of the
19643 template file when the composer starts up.
19644 </DD>
19645 </DL>
19647 <P>
19648 <End of help on this topic>
19649 </BODY>
19650 </HTML>
19651 ======= h_reply_token_conditionals =======
19652 <HTML>
19653 <HEAD>
19654 <TITLE>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</TITLE>
19655 </HEAD>
19656 <BODY>
19657 <H1>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</H1>
19659 Conditional text inclusion may be used with
19660 the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
19661 in signature files, and in template files used in
19662 <A HREF="h_rules_roles">"roles"</A>.
19663 It may <EM>not</EM> be used with the
19664 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
19666 <P>
19667 There is a limited if-else capability for including text.
19668 The if-else condition is based
19669 on whether or not a given token would result in replacement text you
19670 specify.
19671 The syntax of this conditional inclusion is
19672 <P>
19673 <CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER>
19674 <P>
19675 The left parenthesis must follow the underscore immediately, with no
19676 intervening space.
19677 It means the token is expanded and the results of that expansion are
19678 compared against the "match_this" argument.
19679 If there is an exact match, then the "if_matched" text is used
19680 as the replacement text.
19681 Otherwise, the "if_not_matched" text is used.
19682 One of the most useful values for the "match_this" argument is
19683 the empty string, "".
19684 In that case the expansion is compared against the empty string.
19685 <P>
19686 Here's an example to make it clearer.
19687 This text could be included in one of your template files:
19688 <P>
19689 <CENTER><SAMP>_NEWS_("", "I'm replying to email", "I'm replying to news")</SAMP></CENTER>
19690 <P>
19691 If that is included in a template file that you are using while replying
19692 to a message (because you chose to use the role it was part of),
19693 and that message has a newsgroup header and a newsgroup in that header,
19694 then the text
19695 <P>
19696 <CENTER><SAMP>I'm replying to news</SAMP></CENTER>
19697 <P>
19698 will be included in the message you are about to compose.
19699 On the other hand, if the message you are replying to does not have
19700 a newsgroup, then the text
19701 <P>
19702 <CENTER><SAMP>I'm replying to email</SAMP></CENTER>
19703 <P>
19704 would be included instead.
19705 This would also work in signature files and in
19706 the "<!--#echo var="VAR_reply-leadin"-->" option.
19707 If the "match_this", "if_matched",
19708 or "if_not_matched" arguments contain
19709 spaces, parentheses, or commas;
19710 they have to be quoted with double quotation marks (like in the example
19711 above).
19712 If you want to include a literal quote (") in the text you must escape the
19713 quote by preceding it with a backslash (\) character.
19714 If you want to include a literal backslash character you must escape it
19715 by preceding it with another backslash.
19716 <P>
19717 The comma followed by "if_not_matched" is optional.
19718 If there is no "if_not_matched"
19719 present then no text is included if the not_matched case is true.
19720 Here's another example:
19721 <P>
19722 <CENTER><SAMP>_NEWS_("", "", "This msg was seen in group: _NEWS_.")</SAMP></CENTER>
19723 <P>
19724 Here you can see that tokens may appear in the arguments.
19725 The same is true for tokens with the conditional parentheses.
19726 They may appear in arguments,
19727 though you do have to be careful to get the quoting and escaping of
19728 nested double quotes correct.
19729 If this was in the signature file being used and you were replying to a message
19730 sent to comp.mail.pine the resulting text would be:
19731 <P>
19732 <CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER>
19733 <P>
19734 If you were replying to a message that wasn't sent to any newsgroup the
19735 resulting text would be a single blank line.
19736 The reason you'd get a blank line is because the end of the line is
19737 outside of the conditional, so is always included.
19738 If you wanted to get rid of that blank line you could do so by moving
19739 the end of line inside the conditional.
19740 In other words, it's ok to have multi-line
19741 "if_matched" or "if_not_matched" arguments in your
19742 template file.
19743 The text just continues until the next double quotation, even if it's not
19744 on the same line.
19745 <P>
19746 Here's an example for use in the "<!--#echo var="VAR_reply-leadin"-->":
19747 <P>
19748 <CENTER><SAMP>On _DAYDATE_, _FROM__CURNEWS_("", "", "seen in _CURNEWS_,") wrote</SAMP></CENTER>
19749 <P>
19750 If this was in your <!--#echo var="VAR_reply-leadin"--> and you were replying to a message
19751 while reading the newsgroup comp.mail.pine the resulting text would be:
19752 <P>
19753 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone, seen in comp.mail.pine, wrote:</SAMP></CENTER>
19754 <P>
19755 If you were replying to a message while reading an email folder instead
19756 of a newsgroup the resulting leadin text would be
19757 <P>
19758 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
19759 <P>
19760 Here's one more (contrived) example illustrating a matching argument
19761 that is not the empty string.
19762 <P>
19763 <CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER>
19764 <P>
19765 If this was the value of your "<!--#echo var="VAR_reply-leadin"-->" option and you
19766 were replying to
19767 a message that was sent today, then the value of the "<!--#echo var="VAR_reply-leadin"-->"
19768 would be
19769 <P>
19770 <CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER>
19771 <P>
19772 But if you were replying to a message sent on Oct. 27 (and that wasn't
19773 today) you would get
19774 <P>
19775 <CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER>
19776 <P>
19778 <End of help on this topic>
19779 </BODY>
19780 </HTML>
19781 ======= h_composer_cntxt_nick =======
19782 <HTML>
19783 <HEAD>
19784 <TITLE>Collection Nickname Explained</TITLE>
19785 </HEAD>
19786 <BODY>
19787 <H1>Collection Edit Help -- Nickname Field</H1>
19789 This field is provided so you can add a short nickname to use when
19790 referring to this collection within Alpine. Spaces are allowed, and
19791 you don't need to use double-quotes. However, the double-quote
19792 character is not allowed.
19793 <P>
19794 Look <A HREF="h_edit_nav_cmds">here</A>
19795 to see the available Editing and Navigation commands.
19796 <P>
19797 <End of help on this topic>
19798 </BODY>
19799 </HTML>
19800 ======= h_folder_server_syntax =======
19801 <HTML>
19802 <HEAD>
19803 <TITLE>Server Name Syntax</TITLE>
19804 </HEAD>
19805 <BODY>
19806 <H1>Server Name Syntax</H1>
19808 This help describes the syntax that may be used for server names
19809 that may be associated with remote folders or SMTP servers.
19811 <P>
19812 A server name is the hostname of the server.
19813 It's a good idea to use the host's fully-qualified network name.
19815 <P>
19816 <CENTER><SAMP>foo.example.com</SAMP></CENTER>
19817 <P>
19819 However, IP addresses are allowed if surrounded
19820 with square-brackets.
19822 <P>
19823 <CENTER><SAMP>[127.0.0.1]</SAMP></CENTER>
19824 <P>
19826 An optional network port number may be supplied by appending
19827 a colon (:) followed by the port number
19828 to the server name.
19829 By default, the IMAP port number, 143, is used.
19831 <P>
19832 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
19833 <P>
19835 Besides server name and optional port number, various other optional
19836 parameters may be supplied that alter Alpine's interaction with the server.
19837 A parameter is supplied by appending a slash (/) character followed by
19838 the parameter's name and,
19839 depending on the particular parameter, the value assigned to that
19840 name, to the server name (and optional port number).
19841 Parameter names are <EM>not</EM> case sensitive.
19842 Currently supported parameters include:
19844 <DL>
19846 <DT>User</DT>
19847 <DD>This parameter requires an associated value, and is intended to
19848 provide the username identifier with which to establish the server
19849 connection.
19850 If your SMTP server offers SMTP AUTH authentication, adding this
19851 parameter to the
19852 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
19853 option will cause Alpine to attempt to authenticate to the server using the
19854 supplied username.
19855 Similarly, if your NNTP server offers NNTP "AUTHINFO SASL"
19856 or "AUTHINFO USER" authentication, adding this parameter to the
19857 <A HREF="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></A>
19858 option (or to the server name for any folder collection using NNTP)
19859 will cause Alpine to attempt
19860 to authenticate to the server using the supplied username.
19861 An example might be:
19863 <P>
19864 <CENTER><SAMP>/user=katie</SAMP></CENTER>
19865 <P>
19867 </DD>
19869 <DT>TLS</DT>
19870 <DD>
19871 Normally, when a new connection is made an attempt is made to
19872 negotiate a secure (encrypted) session using Transport Layer Security (TLS).
19873 If that fails then a non-encrypted connection will be attempted instead.
19874 This is a unary parameter indicating communication with the server must
19875 take place over a TLS connection. If the attempt to use TLS fails then
19876 this parameter will cause the connection to fail instead of falling
19877 back to an unsecure connection.
19879 <P>
19880 <CENTER><SAMP>/tls</SAMP></CENTER>
19881 <P>
19883 </DD>
19885 <DT>SSL</DT>
19886 <DD>
19887 This is a unary parameter indicating communication with the server should
19888 take place over a Secure Socket Layer connection. The server must support
19889 this method, and be prepared to accept connections on the appropriate
19890 port (993 by default).
19891 Alpine must be linked with an SSL library for this option to be operational.
19893 <P>
19894 <CENTER><SAMP>/ssl</SAMP></CENTER>
19895 <P>
19897 </DD>
19899 <DT>TLS1</DT>
19900 <DD>
19901 This parameter indicates that the connection to the server will be made
19902 over the SSL port, but using the TLSv1 protocol, instead of the usual
19903 SSLv3 or SSLv2 protocols.
19904 Alpine must be linked with an SSL library for this option to be operational.
19906 <P>
19907 <CENTER><SAMP>/tls1</SAMP></CENTER>
19908 <P>
19910 </DD>
19912 <DT>DTLS1</DT>
19913 <DD>
19914 This parameter indicates that the connection to the server will be made
19915 over the SSL port, but using the DTLSv1 protocol, instead of the usual
19916 SSLv3 or SSLv2 protocols.
19917 Alpine must be linked with an SSL library for this option to be operational.
19919 <P>
19920 <CENTER><SAMP>/dtls1</SAMP></CENTER>
19921 <P>
19923 </DD>
19925 <DT>TLS1_1</DT>
19926 <DD>
19927 This parameter indicates that the connection to the server will be made
19928 over the SSL port, but using the TLSv1.1 protocol, instead of the usual
19929 SSLv3 or SSLv2 protocols.
19930 Alpine must be linked with an SSL library for this option to be operational.
19932 <P>
19933 <CENTER><SAMP>/tls1_1</SAMP></CENTER>
19934 <P>
19936 </DD>
19938 <DT>TLS1_2</DT>
19939 <DD>
19940 This parameter indicates that the connection to the server will be made
19941 over the SSL port, but using the TLSv1.2 protocol, instead of the usual
19942 SSLv3 or SSLv2 protocols.
19943 Alpine must be linked with an SSL library for this option to be operational.
19945 <P>
19946 <CENTER><SAMP>/tls1_2</SAMP></CENTER>
19947 <P>
19949 </DD>
19952 <DT>NoValidate-Cert</DT>
19953 <DD>Do not validate certificates (for TLS or SSL connections) from the server.
19954 This is needed if the server uses self-signed certificates or if Alpine
19955 cannot validate the certificate for some other known reason.
19956 <P>
19957 </DD>
19959 <DT>Anonymous</DT>
19960 <DD>This is a unary parameter (that means it does not have a value)
19961 indicating that the connection be logged in as
19962 "anonymous" rather than a specific user.
19963 Not all servers offer anonymous
19964 access; those which do generally only offer read-only access to certain
19965 "public" folders.
19967 <P>
19968 <CENTER><SAMP>/anonymous</SAMP></CENTER>
19969 <P>
19971 </DD>
19973 <DT>Secure</DT>
19974 <DD>This is a unary parameter indicating that the connection use the
19975 most secure authentication method mutually supported by Alpine and the
19976 server.
19977 Alpine is capable of authenticating connections to
19978 the server using several methods.
19979 By default, Alpine will attempt each
19980 method until either a connection is established or the
19981 list of methods is exhausted.
19982 This parameter causes Alpine to instead fail
19983 the connection if the first (generally most "secure") method fails.
19985 <P>
19986 <CENTER><SAMP>/secure</SAMP></CENTER>
19987 <P>
19989 </DD>
19991 <DT>Submit</DT>
19992 <DD>This is a unary parameter for use with the
19993 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> option.
19994 It indicates that the connection should be made to the Submit server
19995 (<A HREF="http://www.ietf.org/rfc/rfc2476.txt">RFC 3676</A>)
19996 (port 587) instead of the SMTP port (25).
19997 At the time this help was written the submit option was equivalent to
19998 specifying port 587.
20000 <P>
20001 <CENTER><SAMP>/submit</SAMP></CENTER>
20002 <P>
20003 or
20004 <P>
20005 <CENTER><SAMP>host:587</SAMP></CENTER>
20006 <P>
20008 </DD>
20010 <DT>Debug</DT>
20011 <DD>This is a unary parameter indicating that the connection be established
20012 in a verbose mode. Basically, it causes Alpine to log the communication with
20013 the server in Alpine's debug file.
20014 Normally, the pine -d command-line flag would be used instead.
20015 <P>
20016 </DD>
20018 <DT>NoRsh</DT>
20019 <DD>By default, Alpine attempts to login using "rsh",
20020 the UNIX remote shell program.
20021 Including "NoRsh" will cause connections to this server to skip
20022 the "rsh" attempt.
20023 This might be useful to avoid long timeouts caused by rsh firewalls, for
20024 example.
20025 <P>
20026 </DD>
20028 <DT>Loser</DT>
20029 <DD>This option makes sense only for IMAP servers that do not perform
20030 a SEARCH command correctly. If your filtering rules
20031 fail to filter some messages, that should have been filtered, then this
20032 option will make Alpine download all data necessary to perform that search.
20033 There is a performance penalty when using this option. Downloading the
20034 data to perfom the search will take longer than requesting the IMAP
20035 server to perform the filtering, but the filtering will be done correctly.
20036 <P>
20037 </DD>
20040 <DT>Service</DT>
20041 <DD>This parameter requires an associated value. The default value is
20042 "IMAP" which indicates communication with the server based
20043 on the IMAP4rev1 protocol (defined in RFC 3501 -- see
20044 <A HREF="http://www.imap.org/docs/rfc3501.html">http://www.imap.org/docs/rfc3501.html</A>).</DD>
20046 Other service values include:
20047 <DL>
20048 <DT>NNTP</DT>
20049 <DD>This value indicates communication with the server takes place via
20050 the Network News Transfer Protocol. Use this to define a collection
20051 of newsgroups on a remote news server. So
20053 <P>
20054 <CENTER><SAMP>/service=NNTP</SAMP></CENTER>
20055 <P>
20056 or just
20057 <P>
20058 <CENTER><SAMP>/NNTP</SAMP></CENTER>
20059 <P>
20061 is the way to specify NNTP access.
20062 <P>
20063 </DD>
20065 <DT>POP3</DT>
20066 <DD>This value indicates communication with the server takes place via the
20067 Post Office Protocol 3 protocol.
20069 <P>
20070 <CENTER><SAMP>/service=POP3</SAMP></CENTER>
20071 <P>
20072 or just
20073 <P>
20074 <CENTER><SAMP>/POP3</SAMP></CENTER>
20075 <P>
20077 Note that there are several important issues
20078 to consider when selecting this option:
20079 <OL>
20080 <LI> POP3 provides access to only your INBOX. In other words,
20081 secondary folders such as your "saved-messages" are inaccessible.
20082 <LI> Alpine's implementation of POP3 does not follow the traditional POP
20083 model and will leave your mail on the server. Refer to the
20084 <A HREF="h_maildrop">Mail Drop</A> functionality for a possible way around this problem.
20085 <LI> See the discussion about new-mail checking in <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
20086 </OL>
20087 </DD>
20088 </DL>
20089 </DL>
20091 <P>
20092 Note that it is possible to include more than one parameter in a server
20093 specification by concatenating the parameters. For example:
20095 <P>
20096 <CENTER><SAMP>foo.example.com:port/user=katie/novalidate-cert/debug</SAMP></CENTER>
20097 <P>
20099 <P>
20100 <End of help on this topic>
20101 </BODY>
20102 </HTML>
20103 ======= h_composer_cntxt_server =======
20104 <HTML>
20105 <HEAD>
20106 <TITLE>Collection Server: Explained</TITLE>
20107 </HEAD>
20108 <BODY>
20109 <H1>Collection Edit Help -- Server Field</H1>
20111 This collection's "Server:" definition indicates the
20112 hostname of the server providing access to the folders in this
20113 collection.
20114 The syntax of this server name is the same as for other server names used
20115 in remote folder names in
20116 Alpine and is described
20117 <A HREF="h_folder_server_syntax">here</A>.
20119 <P>
20120 <End of help on this topic>
20121 </BODY>
20122 </HTML>
20123 ======= h_composer_cntxt_path =======
20124 <HTML>
20125 <HEAD>
20126 <TITLE>Collection Path: Explained</TITLE>
20127 </HEAD>
20128 <BODY>
20129 <H1>Collection Edit Help -- Path Field</H1>
20131 The collection's "Path:" definition indicates the location
20132 of the folders in this collection. If the path or any of its components
20133 do not exist, Alpine will prompt you for their creation when exiting the
20134 Add/Change screen.
20136 <P>
20137 By default the path is interpreted as defining a section of your personal
20138 folder area. This area and how you specify it are defined by the
20139 server, if one is specified in the collection, or, typically, the home
20140 directory if no server is defined.
20142 <P>
20143 To define a collection outside the default "area", prefix
20144 the path with the "namespace" to use when interpreting the
20145 given path. If a namespace is specified, the Path begins with the
20146 sharp, "#", character followed by the name of the namespace
20147 and then the namespace's path-element-delimiter. Aside from the
20148 path's format, namespaces can also imply access rights, content
20149 policy, audience, location, and, occasionally, access methods.
20151 <P>
20152 Each server exports its own set (possibly of size one) of
20153 namespaces. Hence, it's likely communication with your server's
20154 administrator will be required for specific configurations. Some of
20155 the more common namespaces, however, include:
20157 <DL>
20158 <DT>#news.</DT>
20159 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
20160 names are hierarchically defined with each level delimited by a period.
20161 </DD>
20162 <DT>#public/</DT>
20163 <DD>This specifies a folder area that the server may export to the general
20164 public.
20165 </DD>
20166 <DT>#shared/</DT>
20167 <DD>This specifies a folder area that the folder may export to groups
20168 of users.
20169 </DD>
20170 <DT>#ftp/</DT>
20171 <DD>This specifies a folder area that is the same as that it may have
20172 exported via the "File Transfer Protocol".
20173 </DD>
20174 <DT>#mh/</DT>
20175 <DD>This specifies the personal folder area associated with folders
20176 and directories that were created using the MH message handling system.
20177 </DD>
20178 </DL>
20179 <P>
20181 In addition, the server may support access to other user's folders,
20182 provided you have suitable permissions. Common methods use a prefix
20183 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
20184 indicate the root of the other user's folder area.
20186 <P>
20187 No, nothing's simple.
20189 <P>
20190 <End of help on this topic>
20191 </BODY>
20192 </HTML>
20193 ======= h_composer_cntxt_view =======
20194 <HTML>
20195 <HEAD>
20196 <TITLE>Collection View: Explained</TITLE>
20197 </HEAD>
20198 <BODY>
20199 <H1>Collection Edit Help -- View Field</H1>
20201 The collection's "View:" definition provides a way to limit
20202 the displayed list of folders within a collection. By default, only
20203 folders that contain the specified characters anywhere in their name
20204 are shown in the collection's folder list.
20206 <P>
20207 Additionally, you can use a wildcard character to better control
20208 the list of folders selected for display. The wildcard specifier is
20209 the star, "*", character.
20211 <P>
20212 So, for example, to define a collection of all folders ending with
20213 "c", you'd specify a view of "*c" (without the
20214 quote characters!). Or, similarly, to define a collection of folders
20215 whose names start with "a" and end with "z", you'd
20216 specify a view of "a*z".
20218 <P>
20219 <End of help on this topic>
20220 </BODY>
20221 </HTML>
20222 ======= h_composer_abook_add_server =======
20223 <HTML>
20224 <HEAD>
20225 <TITLE>Addressbook Server Name Field Explained</TITLE>
20226 </HEAD>
20227 <BODY>
20228 This field should be left blank if the address book is stored in a regular
20229 file on this system. If it is a remote address book stored on an IMAP
20230 server then this is the name of that IMAP server.
20231 <P>
20232 Look <A HREF="h_edit_nav_cmds">here</A>
20233 to see the available Editing and Navigation commands.
20234 <P>
20235 <End of help on this topic>
20236 </BODY>
20237 </HTML>
20238 ======= h_composer_abook_add_folder =======
20239 <HTML>
20240 <HEAD>
20241 <TITLE>Addressbook Folder Name Field Explained</TITLE>
20242 </HEAD>
20243 <BODY>
20244 For a remote address book (one for which the Server Name is filled in)
20245 this is the name of a folder on the remote server. The address book data
20246 will be stored in this folder. This folder should be used only for
20247 storing this single address book, not for other address books or for
20248 other messages.
20249 <P>
20250 For a local address book (one for which the Server Name is not filled in)
20251 this is the name of a file in which the address book will be stored.
20252 The file is in the same directory as the Alpine configuration file if the
20253 configuration file is local.
20254 If the configuration file is remote, then this will be in the home directory
20255 for Unix Alpine and in the directory specified by the
20256 "-aux local_directory" command line argument.
20257 <P>
20258 Look <A HREF="h_edit_nav_cmds">here</A>
20259 to see the available Editing and Navigation commands.
20260 <P>
20261 <End of help on this topic>
20262 </BODY>
20263 </HTML>
20264 ======= h_composer_abook_add_nick =======
20265 <HTML>
20266 <HEAD>
20267 <TITLE>Addressbook NickName Field Explained</TITLE>
20268 </HEAD>
20269 <BODY>
20270 This is just an optional nickname for this address book. If present, it
20271 is used in some of the displays and error messages in the address book
20272 maintenance screens. It is for your convenience only and serves no
20273 other purpose.
20274 <P>
20275 Look <A HREF="h_edit_nav_cmds">here</A>
20276 to see the available Editing and Navigation commands.
20277 <P>
20278 <End of help on this topic>
20279 </BODY>
20280 </HTML>
20281 ======= h_composer_qserv_cn =======
20282 <HTML>
20283 <HEAD>
20284 <TITLE>Directory Query Form Explained</TITLE>
20285 </HEAD>
20286 <BODY>
20288 Fill in as many of these fields as you wish to narrow down your
20289 search. All the fields you fill in must match in order for an entry
20290 to be returned. You may use the wildcard character "*" in
20291 any of the fields, it matches any zero or more characters at that
20292 point in the string. There are no implicit wildcards, so the match is
20293 exact unless you include wildcards.
20294 <P>
20296 Note that if an attribute isn't present at all, then the match will fail.
20297 For example, if a server doesn't support the Locality attribute, then no
20298 matter what you put in the Locality field (other than leaving it empty)
20299 the search will fail.
20300 <P>
20302 This field, the Common Name field, is typically a person's full name.
20303 <P>
20305 <H1>EDITING and NAVIGATION COMMANDS</H1>
20306 <!--chtml if pinemode="function_key"-->
20307 <PRE>
20308 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
20309 ^B (Left Arrow) Back character | ^D Delete current character
20310 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
20311 ^P (Up Arrow) Previous line |
20312 ^N (Down Arrow) Next line | F9 Cut marked text or
20313 ^A Beginning of line | delete current line
20314 ^E End of line | F10 Undelete line(s)
20315 F7 Previous page |
20316 F8 Next page |-------------------------------------
20317 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
20318 ----------------------------------------|
20319 EXIT COMMANDS | GENERAL COMMANDS | F5 Restore previous search
20320 F2 Cancel | F1 Get help |
20321 F3 Search | ^Z Suspend | ^L Redraw Screen
20322 </PRE>
20323 <!--chtml else-->
20324 <PRE>
20325 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
20326 ^B (Left Arrow) Back character | ^D Delete current character
20327 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
20328 ^P (Up Arrow) Previous line |
20329 ^N (Down Arrow) Next line | ^K Cut marked text or
20330 ^A Beginning of line | delete current line
20331 ^E End of line | ^U Undelete line(s)
20332 ^Y Previous page |
20333 ^V Next page |-------------------------------------
20334 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
20335 ----------------------------------------|
20336 EXIT COMMANDS | GENERAL COMMANDS | ^R Restore previous search
20337 ^C Cancel | ^G Get help |
20338 ^X Search | ^Z Suspend | ^L Redraw Screen
20339 </PRE>
20340 <!--chtml endif-->
20341 <P><UL>
20342 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20343 </UL><P>
20344 <End of help on this topic>
20345 </BODY>
20346 </HTML>
20347 ======= h_composer_qserv_sn =======
20349 The Surname is usually the family name of a person.
20351 <End of help on this topic>
20352 ======= h_composer_qserv_gn =======
20354 This is the part of a person's name that isn't the surname or initials.
20356 <End of help on this topic>
20357 ======= h_composer_qserv_mail =======
20359 This is the email address of a person.
20361 <End of help on this topic>
20362 ======= h_composer_qserv_org =======
20364 This is the organization a person belongs to.
20366 <End of help on this topic>
20367 ======= h_composer_qserv_unit =======
20369 This is the organizational unit a person belongs to.
20371 <End of help on this topic>
20372 ======= h_composer_qserv_country =======
20374 This is the country a person belongs to.
20376 <End of help on this topic>
20377 ======= h_composer_qserv_state =======
20379 This is the state a person belongs to.
20381 <End of help on this topic>
20382 ======= h_composer_qserv_locality =======
20384 This is the locality a person belongs to.
20386 <End of help on this topic>
20387 ======= h_composer_qserv_custom =======
20389 This one is for advanced users only! If you put something in this field,
20390 then the rest of the fields are ignored.
20392 This field may be set to the string representation of an LDAP search
20393 filter (see RFC1960). Here are some examples:
20395 To search for an entry with a surname equal to "clinton" you could set
20396 the custom filter to:
20398 (sn=clinton)
20400 This is equivalent to putting "clinton" in the SurName field.
20401 To search for an entry that has a surname that begins with "clint" and
20402 has a givenname equal to "william" you could use:
20404 (&(sn=clint*)(givenname=william))
20406 This is equivalent to setting the SurName field to "clint*" and the
20407 GivenName field to "william".
20408 To search for an entry where either the common name OR the email address
20409 contains "abcde" you could use:
20411 (|(cn=*abcde*)(mail=*abcde*))
20413 That isn't equivalent to anything you can do by setting the other fields
20414 because of the OR.
20416 <End of help on this topic>
20417 ======= h_composer_qserv_qq =======
20419 This one is a little different from the rest of the categories. It causes
20420 a search to be formed from the configured search filter that you filled
20421 in when you added the directory server to your configuration. It can also
20422 be combined with the other fields if you'd like.
20424 <End of help on this topic>
20425 ======= h_address_format =======
20426 <HTML>
20427 <HEAD>
20428 <TITLE>INTERNET EMAIL ADDRESS FORMAT</TITLE>
20429 </HEAD>
20430 <BODY>
20431 <H1>INTERNET EMAIL ADDRESS FORMAT</H1>
20433 A valid email address on the Internet has a username, an "@" sign,
20434 and then a domain, with no spaces.
20435 For example, jsmith@art.example.com might be the email address
20436 of a person
20437 with the username "jsmith" who has an account in the domain
20438 "art.example.com". The number of dot-separated segments on the
20439 right of the "@" sign can vary - a shorter example would be
20440 isabelle@elsewhere.edu (the shortest possible form: here, only the
20441 organization's domain is specified after the "@" sign); a longer
20442 example would be
20443 jsingh@shakti.edutech.example.com
20444 (here, the name of the host "shakti" in the domain
20445 edutech.example.com is also specified).
20446 <P>
20447 If you do not know the exact email address of someone you want to write
20448 to, ask them what it is using other means of communication than email; or
20449 use the tools for
20450 finding people's addresses that are available on the Internet.
20451 <P>
20452 If you are sending to someone on the same system as you are, you can leave
20453 the "@" sign and all the information to its right off of the
20454 address, and Alpine will fill it in automatically,
20455 unless the feature
20456 <A HREF="h_config_compose_rejects_unqual">"<!--#echo var="FEAT_compose-rejects-unqualified-addrs"-->"</A> is set in SETUP CONFIGURATION.
20457 <P>
20459 When an email address you send a message to is not reachable -- either because
20460 it is simply an incorrect address, or because email can temporarily not be
20461 delivered to it due to a technical problem on the way to or at the recipient's
20462 end -- you will almost always get an error notification email message back.
20463 <P>
20464 If you encounter problems with, or have questions about, email delivery or
20465 email address syntax, contact your local network computing consultants.
20466 <P><UL>
20467 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20468 </UL>
20469 <P>
20470 <End of help on this topic>
20471 </BODY>
20472 </HTML>
20473 ======= h_flag_user_flag =======
20474 <HTML>
20475 <HEAD>
20476 <TITLE>STATUS FLAG: User Defined Keyword</TITLE>
20477 </HEAD>
20478 <BODY>
20479 <H1>STATUS FLAG: User Defined Keyword</h1>
20481 This is a keyword that is defined for this folder.
20482 It was most likely defined by the owner of the folder.
20483 Alpine will not set or clear this flag on its own.
20485 <P><UL>
20486 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20487 </UL><P>
20488 <End of help on this topic>
20489 </BODY>
20490 </HTML>
20491 ======= h_flag_important =======
20492 <html>
20493 <title>STATUS FLAG: Important</title>
20494 <body>
20495 <h1>STATUS FLAG: Important</h1>
20498 The <EM>Important</EM> flag, indicated by an asterisk in Alpine's
20499 MESSAGE INDEX
20500 screen, can only be set by the user, and is intended to be used in
20501 whatever fashion makes sense to you. You are the only one that can set or
20502 clear it.
20504 <P>
20505 <End of help on this topic>
20506 </BODY>
20507 </HTML>
20508 ======= h_flag_new =======
20509 <html>
20510 <title>STATUS FLAG: New</title>
20511 <body>
20512 <h1>STATUS FLAG: New</h1>
20515 The <EM>New</EM> flag, indicated by the letter 'N' in Alpine's
20516 MESSAGE INDEX screen,
20517 is automatically set when messages are delivered to your Inbox (or other
20518 folder specified outside of Alpine). Likewise, it is cleared automatically
20519 the first time you read the message it is associated with.
20521 <P>
20522 Sometimes it's helpful in prioritizing your mail. For example, perhaps
20523 a message isn't weighty enough to assign it an <A HREF="h_flag_important">Important</A> flag, but
20524 you'd like to be reminded of it next time you read mail. This can be done
20525 easily by <A HREF="h_common_flag">explicitly</A> resetting the <EM>New</EM> flag.
20528 <P>
20529 <End of help on this topic>
20530 </BODY>
20531 </HTML>
20532 ======= h_flag_answered =======
20533 <html>
20534 <title>STATUS FLAG: Answered</title>
20535 <body>
20536 <h1>STATUS FLAG: Answered</h1>
20538 The <EM>Answered</EM> flag, indicated by the letter 'A' in Alpine's
20539 MESSAGE INDEX
20540 screen, is automatically set when you reply to a message. This flag is not
20541 automatically cleared.
20543 <P>
20544 <End of help on this topic>
20545 </BODY>
20546 </HTML>
20547 ======= h_flag_forwarded =======
20548 <html>
20549 <title>STATUS FLAG: Forwarded</title>
20550 <body>
20551 <h1>STATUS FLAG: Forwarded</h1>
20553 The <EM>Forwarded</EM> flag, indicated by the letter 'F' in Alpine's
20554 MESSAGE INDEX
20555 screen, is automatically set when you forward a message. This flag is not
20556 automatically cleared.
20558 <P>
20559 <End of help on this topic>
20560 </BODY>
20561 </HTML>
20562 ======= h_flag_deleted =======
20563 <html>
20564 <title>STATUS FLAG: Deleted</title>
20565 <body>
20566 <h1>STATUS FLAG: Deleted</h1>
20568 The <EM>Deleted</EM> flag, indicated by the letter 'D' in Alpine's
20569 MESSAGE INDEX
20570 screen, is set when you use the ""D Delete" command.
20571 It is cleared
20572 when you use the "U Undelete" command.
20574 <P>
20575 Messages marked with this flag will be permanently removed from
20576 the folder when you issue the <A HREF="h_index_cmd_expunge">Expunge</A>
20577 command, or
20578 when you indicate acceptance of their removal upon leaving the folder.
20580 <P>
20581 Note, there can be other actions implicit in the
20582 "D Delete" command,
20583 such as advancing to the next message, that may be momentarily undesirable.
20584 For this reason, it's sometimes useful to set or clear the <EM>Deleted</EM>
20585 flag <A HREF="h_common_flag">explicitly</A>.
20587 <P>
20588 <End of help on this topic>
20589 </BODY>
20590 </HTML>
20591 ====== h_config_incoming_timeo ======
20592 <HTML>
20593 <HEAD>
20594 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></TITLE>
20595 </HEAD>
20596 <BODY>
20597 <H1>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></H1>
20599 This option has no effect unless the feature
20600 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
20601 is set, which in turn has no effect unless
20602 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
20603 is set.
20604 <P>
20605 Sets the time in seconds that Alpine will
20606 attempt to open a network connection used for monitoring for Unseen
20607 messages in Incoming Folders. The default is 5.
20608 If a connection has not completed within this many seconds Alpine will
20609 give up and consider it a failed connection.
20610 <P>
20611 <UL>
20612 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20613 </UL><P>
20614 <End of help on this topic>
20615 </BODY>
20616 </HTML>
20617 ====== h_config_psleep ======
20618 <HTML>
20619 <HEAD>
20620 <TITLE>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</TITLE>
20621 </HEAD>
20622 <BODY>
20623 <H1>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</H1>
20625 <P>
20626 In the good old days a mailcap viewer was used to examine an
20627 attachment before saving it, and after viewing the attachment control
20628 would return to the operating system when the viewer was closed. Therefore,
20629 when the mailcap viewer returned control to the operating system, it
20630 could be assumed that the user who opened the attachment was done
20631 examining it, and the copy of the attachment that was used, could be removed.
20633 <P>
20634 However, today this assumption is not longer valid. Some viewers return
20635 control to the operating system before they actually read the attachment
20636 to be examined. This causes Alpine to delete the attachment before it
20637 is read by the viewer, causing the viewer to fail opening the attachment.
20639 <P>
20640 In order to work around this problem, Alpine checks, after the viewer has
20641 returned control to the operating system, if there is any process that is
20642 using the attachment. This variable controls the number of seconds that
20643 must elapse between checks. Once it is found that no process is using the
20644 attachment, this is removed.
20646 <P>
20647 The minimum value for this variable is 60 (checks will be made once per
20648 minute), and the maximum value is 600 (checks will be made once every 10
20649 minutes). The default value is 60.
20651 <P>
20652 <UL>
20653 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20654 </UL><P>
20655 <End of help on this topic>
20656 </BODY>
20657 </HTML>
20658 ====== h_config_incoming_interv ======
20659 <HTML>
20660 <HEAD>
20661 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval"--></TITLE>
20662 </HEAD>
20663 <BODY>
20664 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval"--></H1>
20666 This option has no effect unless the feature
20667 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
20668 is set, which in turn has no effect unless
20669 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
20670 is set.
20671 <P>
20672 This option specifies, in seconds, how often Alpine will check
20673 for new mail and state changes in Incoming Folders when Incoming Folders
20674 Checking is turned on.
20675 The default is 3 minutes (180).
20676 This value applies only to folders that are local to the system that
20677 Alpine is running on or that are accessed using the IMAP protocol.
20678 The similar option
20679 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>
20680 applies to all other monitored folders.
20681 <P>
20682 <UL>
20683 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20684 </UL><P>
20685 <End of help on this topic>
20686 </BODY>
20687 </HTML>
20688 ====== h_config_incoming_second_interv ======
20689 <HTML>
20690 <HEAD>
20691 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></TITLE>
20692 </HEAD>
20693 <BODY>
20694 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></H1>
20696 This option has no effect unless the feature
20697 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
20698 is set, which in turn has no effect unless
20699 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
20700 is set.
20701 <P>
20702 This option together with the option
20703 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
20704 specifies, in seconds, how often Alpine will check
20705 for new mail and state changes in Incoming Folders when Incoming Folders
20706 Checking is turned on.
20707 The default for this option is 3 minutes (180).
20708 For folders that are local to this system or
20709 that are accessed using the IMAP protocol
20710 the value of the option
20711 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
20712 is used.
20713 For all other monitored folders, the value of this option is used.
20714 <P>
20715 The reason there are two separate options is because it is usually
20716 less expensive to check local and IMAP folders than it is to check
20717 other types, like POP or NNTP folders.
20718 You may want to set this secondary value to a higher number than
20719 the primary check interval.
20720 <P>
20721 <UL>
20722 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20723 </UL><P>
20724 <End of help on this topic>
20725 </BODY>
20726 </HTML>
20727 ====== h_config_incoming_list ======
20728 <HTML>
20729 <HEAD>
20730 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-list"--></TITLE>
20731 </HEAD>
20732 <BODY>
20733 <H1>OPTION: <!--#echo var="VAR_incoming-check-list"--></H1>
20735 This option has no effect unless the feature
20736 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
20737 is set, which in turn has no effect unless
20738 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
20739 is set.
20740 <P>
20741 When monitoring the Incoming Message Folders for Unseen messages Alpine will
20742 normally monitor all Incoming Folders.
20743 You may use this option to restrict the list of monitored folders to a
20744 subset of all Incoming Folders.
20745 <P>
20746 <UL>
20747 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20748 </UL><P>
20749 <End of help on this topic>
20750 </BODY>
20751 </HTML>
20752 ====== h_config_pers_name ======
20753 <HTML>
20754 <HEAD>
20755 <TITLE>OPTION: <!--#echo var="VAR_personal-name"--></TITLE>
20756 </HEAD>
20757 <BODY>
20758 <H1>OPTION: <!--#echo var="VAR_personal-name"--></H1>
20760 This value is used to determine the full name part of the "From" address
20761 on messages you send.
20762 <!--chtml if pinemode="os_windows"-->
20763 PC-Alpine requires that this be set in order to properly construct the "From" address.
20764 <!--chtml else-->
20765 If unset, Unix Alpine will obtain your full name from
20766 the system password file. PC-Alpine, on the other hand, requires that this be set.
20767 <!--chtml endif-->
20768 <P>
20769 If you want to change the value of what gets included in the From header
20770 in messages you send (other than just the Personal Name)
20771 look <A HREF="h_config_change_your_from">here</A> for a description.
20772 <P><UL>
20773 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20774 </UL><P>
20775 <End of help on this topic>
20776 </BODY>
20777 </HTML>
20778 ====== h_config_pruned_folders ======
20779 <html>
20780 <header>
20781 <title>OPTION: <!--#echo var="VAR_pruned-folders"--></title>
20782 </header>
20783 <body>
20784 <h1>OPTION: <!--#echo var="VAR_pruned-folders"--></h1>
20786 This variable allows you to define a list of one or more folders that
20787 Alpine will offer to prune for you in the same way it automatically offers
20788 to prune your "sent-mail" folder each month.
20789 Each folder in this list must be a folder in your default folder collection
20790 (the first folder collection if you have more than one), and it is just
20791 the relative name of the folder in the collection, not the fully-qualified name.
20792 It is similar to sent-mail.
20793 Instead of something like
20794 <P>
20795 <CENTER><SAMP><!--#echo var="VAR_pruned-folders"-->={servername}mail/folder</SAMP></CENTER>
20796 <P>
20797 the correct value to use would be
20798 <P>
20799 <CENTER><SAMP>folder</SAMP></CENTER>
20800 <P>
20801 There is an assumption here that your first collection is the folders in
20802 <P>
20803 <CENTER><SAMP>{servername}mail</SAMP></CENTER>
20804 <P>
20806 Once a month, for each folder listed, Alpine will offer to move
20807 the contents of the folder to a new folder of the same name but with
20808 the previous month's date appended. Alpine will then look for any such
20809 date-appended folder names created for a previous month, and offer each
20810 one it finds for deletion.
20811 <P>
20813 If you decline the first offer, no mail is moved and no new folder is
20814 created.
20815 <P>
20817 The new folders will be created
20818 in your default folder collection.
20819 <P>
20821 <UL>
20822 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20823 </UL><P>
20824 <End of help on this topic>
20825 </body>
20826 </html>
20827 ====== h_config_upload_cmd ======
20828 <HTML>
20829 <HEAD>
20830 <TITLE>OPTION: <!--#echo var="VAR_upload-command"--></TITLE>
20831 </HEAD>
20832 <BODY>
20833 <H1>OPTION: <!--#echo var="VAR_upload-command"--></H1>
20835 This option affects the behavior of the Composer's "Read File"
20836 (^R in the message body) and "Attach File" (^J in the header)
20837 commands. It specifies
20838 a Unix program name, and any necessary command line arguments, that Alpine can
20839 use to transfer files from your personal computer into messages that you are
20840 composing.<P>
20842 <B>Note:</B> this facility is intended for use with serial line transfer
20843 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
20844 to work with TCP/IP file transfer programs such as ftp.<P>
20846 If a program is specified, the commands listed above are modified to offer a
20847 subcommand (^Y) to activate the transfer. Obviously, the Unix program
20848 specified here must match the transfer program or protocol available on the
20849 personal computer.<P>
20851 Alpine expects to exchange uploaded data via a file on your Unix system. When
20852 the specified upload program finishes, Alpine expects the uploaded data to be
20853 contained in this file.<P>
20855 When upload is invoked via the "Read File" subcommand, Alpine
20856 generates a
20857 temporary file name that it will pass to the specified Unix program. Alpine
20858 will read the resulting uploaded text from this file and then delete it when
20859 the upload command is finished.<P>
20861 When upload is invoked via the "Attach File" subcommand, Alpine will
20862 prompt
20863 you for the name of the file that is to contain the uploaded information that
20864 it is to attach. Alpine will attach this file to the composition, but will
20865 <B>not</B> delete this file after the upload command is finished.<P>
20867 The special token "_FILE_" may be included among the Unix program's
20868 command
20869 line arguments. Alpine will replace this symbol with the name of the file
20870 being used to exchange the uploaded information. This token allows you to
20871 position the file name where it is required in the Unix program's command
20872 line arguments.<P>
20874 If the "_FILE_" token is not present in the specified command, the
20875 temporary file's name is automatically appended to the specified Unix
20876 program. In other words, you don't need to use "_FILE_" if it is the
20877 <B>last</B> command line argument.
20878 <P><UL>
20879 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20880 </UL><P>
20881 <End of help on this topic>
20882 </BODY>
20883 </HTML>
20884 ====== h_config_upload_prefix ======
20885 <HTML>
20886 <HEAD>
20887 <TITLE>OPTION: <!--#echo var="VAR_upload-command-prefix"--></TITLE>
20888 </HEAD>
20889 <BODY>
20890 <H1>OPTION: <!--#echo var="VAR_upload-command-prefix"--></H1>
20892 This option is used in conjunction with the <!--#echo var="VAR_upload-command"--> option.
20893 It defines text to be written to the terminal emulator (via standard output)
20894 immediately prior to starting upload command. This is useful for
20895 integrated serial line file transfer agents that permit command passing
20896 (e.g., Kermit's APC method).<P>
20898 The special token "_FILE_" may be included in the string specification.
20899 That symbol will be replaced with the (Alpine-created) name of the temporary
20900 file in which Alpine will expect to find the uploaded file.
20901 <P><UL>
20902 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20903 </UL><P>
20904 <End of help on this topic>
20905 </BODY>
20906 </HTML>
20907 ====== h_config_download_cmd ======
20908 <HTML>
20909 <HEAD>
20910 <TITLE>OPTION: <!--#echo var="VAR_download-command"--></TITLE>
20911 </HEAD>
20912 <BODY>
20913 <H1>OPTION: <!--#echo var="VAR_download-command"--></H1>
20915 This option affects the behavior of the Export command. It specifies a Unix
20916 program name, and any necessary command line arguments, that Alpine can use to
20917 transfer the exported message to your personal computer's disk.<P>
20918 Note: this facility is intended for use with serial line transfer
20919 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
20920 to work with TCP/IP file transfer programs such as ftp.<P>
20921 If a program is specified, the Export command is modified to offer a
20922 subcommand (^V) to activate the transfer (in lieu of saving it to
20923 the machine where Alpine is running). Obviously, the Unix program
20924 specified here must match the transfer program or protocol available on the
20925 personal computer.<P>
20927 When this subcommand is selected and before Alpine invokes the specified Unix
20928 program, Alpine will create a temporary file containing the text of the
20929 exported message. Alpine uses this file to pass the exported message text to
20930 the specified Unix program.<P>
20932 The special token "_FILE_" may be included among the Unix program's command
20933 line arguments. Alpine will replace this symbol with the temporary file's name
20934 before executing the Unix program. This token allows you to position the
20935 file name where it is required in the Unix program's command line arguments.
20936 <P>
20937 If the "_FILE_" token is not present in the specified command, the
20938 temporary file's name is automatically appended to the specified Unix
20939 program. In other words, you don't need to use "_FILE_" if it is the
20940 <B>last</B> command line argument.
20941 <P><UL>
20942 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20943 </UL><P>
20944 <End of help on this topic>
20945 </BODY>
20946 </HTML>
20947 ====== h_config_download_prefix ======
20948 <HTML>
20949 <HEAD>
20950 <TITLE>OPTION: <!--#echo var="VAR_download-command-prefix"--></TITLE>
20951 </HEAD>
20952 <BODY>
20953 <H1>OPTION: <!--#echo var="VAR_download-command-prefix"--></H1>
20955 This option is used in conjunction with the <!--#echo var="VAR_download-command"--> option.
20956 It defines text to be written to the terminal emulator (via standard output)
20957 immediately prior to starting the download command. This is useful for
20958 integrated serial line file transfer agents that permit command passing
20959 (e.g., Kermit's APC method).
20960 <P>
20961 The special token "_FILE_" may be included in the string
20962 specification.
20963 That symbol will be replaced with the (Alpine-created) name of the temporary
20964 file into which Alpine will place the message to be downloaded.
20965 <P><UL>
20966 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20967 </UL><P>
20968 <End of help on this topic>
20969 </BODY>
20970 </HTML>
20971 ====== h_config_mailcap_path ======
20972 <HTML>
20973 <HEAD>
20974 <TITLE>OPTION: <!--#echo var="VAR_mailcap-search-path"--></TITLE>
20975 </HEAD>
20976 <BODY>
20977 <H1>OPTION: <!--#echo var="VAR_mailcap-search-path"--></H1>
20978 This variable is used to replace Alpine's default mailcap file search path.
20979 It takes one or more file names (full paths must be specified) in which to
20980 look for mail capability data. The default search path can be found in this
20981 <A HREF="h_news_config">Alpine Configuration</A> help, near the bottom.
20982 If there is more than one file name listed, list members should be delimited
20983 by
20984 <!--chtml if pinemode="os_windows"-->
20985 a semi-colon (;) under Windows; for example:<PRE>
20986 C:\MYCONFIG\MAILCAP.TXT;H:\NETCONFIG\MAILCAP.TXT
20987 </PRE>
20988 <!--chtml else-->
20989 a colon (:) under UNIX; for example:<PRE>
20990 ~/.mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
20991 </PRE>
20992 <!--chtml endif-->
20993 <P><UL>
20994 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20995 </UL>
20996 <P>
20997 <End of help on this topic>
20998 </BODY>
20999 </HTML>
21000 ====== h_config_mimetype_path ======
21001 <HTML>
21002 <HEAD>
21003 <TITLE>OPTION: <!--#echo var="VAR_mimetype-search-path"--></TITLE>
21004 </HEAD>
21005 <BODY>
21006 <H1>OPTION: <!--#echo var="VAR_mimetype-search-path"--></H1>
21008 This variable is used to replace Alpine's default mime.types file search path.
21009 It takes one or more file names (full paths must be specified) in which to
21010 look for file-name-extension to MIME type mapping data. The default search
21011 path can be found in this
21012 <A HREF="h_news_config">Alpine Configuration</A> help.
21014 <P>
21016 If there is more than one file name listed, list members should be delimited
21017 by a colon (:) under UNIX and a semi-colon (;) under Windows.
21018 <P>
21019 <End of help on this topic>
21020 </BODY></HTML>
21021 ====== h_config_set_att_ansi ======
21022 <HTML><HEAD>
21023 <TITLE>OPTION: Set printer to attached ansi printer</TITLE>
21024 </HEAD>
21025 <BODY>
21026 <H1>OPTION: Set printer to attached ansi printer</H1>
21028 Type "S" to set your printer to "attached-to-ansi".<BR>
21029 It is OK to include "attached-to-ansi" in your personal list below.
21030 <P>
21031 <End of help on this topic>
21032 </BODY></HTML>
21033 ====== h_config_set_att_ansi2 ======
21034 <HTML><HEAD>
21035 <TITLE>OPTION: Set printer to attached ansi printer (no formfeed)</TITLE>
21036 </HEAD>
21037 <BODY>
21038 <H1>OPTION: Set printer to attached ansi printer (no formfeed)</H1>
21040 Type "S" to set your printer to "attached-to-ansi-no-formfeed".<BR>
21041 It is OK to include "attached-to-ansi-no-formfeed" in your personal
21042 list below.
21044 <P>
21046 This is the same as the "attached-to-ansi" option except that a
21047 formfeed character will not be appended to the end of the print job.
21048 If your printer already ejects the paper by itself at the end of the
21049 job, you may prefer the "no-formfeed" form of this printer so that you
21050 don't get an extra blank page between print jobs.
21051 <P>
21053 <End of help on this topic>
21054 </BODY></HTML>
21055 ====== h_config_set_att_wyse ======
21056 <HTML><HEAD>
21057 <TITLE>OPTION: Set printer to attached Wyse60 printer</TITLE>
21058 </HEAD>
21059 <BODY>
21060 <H1>OPTION: Set printer to attached Wyse60 printer</H1>
21062 Type "S" to set your printer to "attached-to-wyse".<BR>
21063 It is OK to include "attached-to-wyse" in your personal list below.
21064 <P>
21065 This is very similar to "attached-to-ansi".
21066 The only difference is in the control characters sent to turn the printer
21067 on and off.
21068 The ansi version of the printer uses ESC LEFT_BRACKET 5 i
21069 to turn on the printer and ESC LEFT_BRACKET 4 i
21070 to turn it off.
21071 The Wyse version uses Ctrl-R for on, and Ctrl-T for off.
21072 <End of help on this topic>
21073 </BODY></HTML>
21074 ====== h_config_set_att_wyse2 ======
21075 <HTML><HEAD>
21076 <TITLE>OPTION: Set printer to attached Wyse60 printer (no formfeed)</TITLE>
21077 </HEAD>
21078 <BODY>
21079 <H1>OPTION: Set printer to attached Wyse60 printer (no formfeed)</H1>
21081 Type "S" to set your printer to "attached-to-wyse-no-formfeed".<BR>
21082 It is OK to include "attached-to-wyse-no-formfeed" in your personal
21083 list below.
21085 <P>
21087 This is the same as the "attached-to-wyse" option except that a
21088 formfeed character will not be appended to the end of the print job.
21089 If your printer already ejects the paper by itself at the end of the
21090 job, you may prefer the "no-formfeed" form of this printer so that you
21091 don't get an extra blank page between print jobs.
21092 <P>
21094 <End of help on this topic>
21095 </BODY></HTML>
21096 ====== h_config_set_stand_print ======
21097 <HTML>
21098 <HEAD>
21099 <TITLE>OPTION: Set default printer</TITLE>
21100 </HEAD>
21101 <H1>OPTION: Set default printer</H1>
21102 <BODY>
21103 Move to the printer you want and type "S" to set it to be your
21104 default printer. This list is not modifiable by you and has been
21105 set up by the system administrators. If there is more than one printer
21106 listed in the Command List, you will be able to cycle through that
21107 whole list at the time you print, starting with your default.
21108 It is OK to include entries from this Standard list in your personal
21109 list below.
21110 <P>
21111 <End of help on this topic>
21112 </BODY>
21113 </HTML>
21114 ====== h_config_set_custom_print ======
21115 <HTML>
21116 <HEAD>
21117 <TITLE>OPTION: Set default printer</TITLE>
21118 </HEAD>
21119 <H1>OPTION: Set default printer</H1>
21120 <BODY>
21121 You may add as many print commands as you want to your personal list.
21122 Specify one of them as your default printer by moving to the printer
21123 you want and typing "S". If there is more than one printer listed
21124 in the Command List, you will be able to cycle through that list at
21125 the time you print, starting with your default. It is OK to include
21126 entries from the Standard list above or to include the command
21127 "attached-to-ansi", "attached-to-ansi-no-formfeed", "attached-to-wyse", or
21128 "attached-to-wyse-no-formfeed" as one of the entries here.
21129 <P>
21130 <End of help on this topic>
21131 </BODY>
21132 </HTML>
21133 ====== h_config_user_id =====
21134 <HTML>
21135 <HEAD>
21136 <TITLE>OPTION: <!--#echo var="VAR_user-id"--></TITLE>
21137 </HEAD>
21138 <BODY>
21139 <H1>OPTION: <!--#echo var="VAR_user-id"--></H1>
21141 This value is used as part of the "From" address on messages you send.
21142 It is also the default login name for remote IMAP server access. Set this
21143 to the username part you want to appear on outgoing email.
21144 <P>
21145 If you want to change the value of what gets included in the From header
21146 in messages you send (other than just the User ID)
21147 look <A HREF="h_config_change_your_from">here</A> for a description.
21149 <P><UL>
21150 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21151 </UL><P>
21152 <End of help on this topic>
21153 </BODY>
21154 </HTML>
21155 ====== h_config_user_dom =====
21156 <HTML>
21157 <HEAD>
21158 <TITLE>OPTION: <!--#echo var="VAR_user-domain"--></TITLE>
21159 </HEAD>
21160 <BODY>
21161 <H1>OPTION: <!--#echo var="VAR_user-domain"--></H1>
21163 This value specifies the domain part (right-hand side) of your return
21164 address on outgoing email and is also used as the default domain for email
21165 composed to a local user.
21166 <!--chtml if pinemode="os_windows"-->
21167 This value is required for PC-Alpine. If you are unsure as to what this should be,
21168 contact your local help desk, system administrator, or Internet Service Provider.
21169 <!--chtml else-->
21170 If unset, Unix Alpine will obtain the domain from
21171 the system. Often this value will be set for your whole site by the
21172 system administrator.<P>
21173 <!--chtml endif-->
21174 If you set this, see also the <A HREF="h_config_quell_local_lookup">
21175 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
21176 <P>
21177 If you want to change the value of what gets included in the From header
21178 in messages you send (other than just the User Domain)
21179 look <A HREF="h_config_change_your_from">here</A> for a description.
21180 <P><UL>
21181 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21182 </UL><P>
21183 <End of help on this topic>
21184 </BODY>
21185 </HTML>
21186 ====== h_config_smtp_server =====
21187 <HTML>
21188 <HEAD>
21189 <TITLE>OPTION: <!--#echo var="VAR_smtp-server"--></TITLE>
21190 </HEAD>
21191 <BODY>
21192 <H1>OPTION: <!--#echo var="VAR_smtp-server"--></H1>
21193 This value specifies the name of one or more SMTP
21194 (Simple Mail Transfer Protocol) servers for sending mail.
21195 <!--chtml if pinemode="os_windows"-->
21196 You must have an SMTP server for use with PC-Alpine.
21197 SMTP servers are
21198 normally set up by a system administrator for use by all members of a given
21199 campus or department.
21200 Contact your local help desk to ask what SMTP
21201 servers you should use.
21202 <!--chtml else-->
21203 Unix Alpine users may not need to set an SMTP server.
21204 Alpine will attempt to execute the program (usually sendmail) that is used
21205 to insert mail into the mail system.
21206 If this works for you, you may leave this option blank.
21207 If there is an SMTP server running on the Unix host you may be able to
21208 improve sending performance slightly by setting the SMTP server option
21209 to "localhost" or to the actual name of the Unix host.
21210 <P>
21211 If the Unix host doesn't work the way Alpine was expecting you will need to
21212 set the value of this option.
21213 SMTP servers are
21214 normally set up by a system administrator for use by all members of a given
21215 campus or department.
21216 Contact your local help desk to ask what SMTP
21217 servers you should use.
21218 <!--chtml endif-->
21219 <P>
21220 Your SMTP server may offer SMTP AUTH authentication.
21221 It may even require it.
21222 If your SMTP server offers SMTP AUTH authentication you may specify a
21223 "user" name parameter to cause Alpine to attempt to authenticate.
21224 This parameter requires an associated value,
21225 the username identifier with which to establish the server
21226 connection.
21227 An example might be:
21229 <P>
21230 <CENTER><SAMP>smtpserver.example.com/user=katie</SAMP></CENTER>
21231 <P>
21233 If AUTH authentication is offered by the server, this will cause Alpine to
21234 attempt to use it.
21235 If AUTH authentication is not offered by the server, this will cause Alpine
21236 to fail sending with an error similar to:
21238 <P>
21239 <CENTER><SAMP>Error: SMTP authentication not available</SAMP></CENTER>
21240 <P>
21242 Another type of authentication that is used by some ISPs is called
21243 "POP before SMTP" or "IMAP before SMTP",
21244 which means that you have to authenticate
21245 yourself to the POP or IMAP server by opening a mailbox before you
21246 can send mail.
21247 To do this, you usually only have to open your INBOX.
21249 <P>
21250 You may tell Alpine to use the
21251 <A HREF="http://www.ietf.org/rfc/rfc2476.txt">Message Submission</A>
21252 port (587) instead of the SMTP port (25) by including the "submit"
21253 parameter
21254 in this option.
21255 At this time "/submit" is simply equivalent to specifying
21256 port 587, though it may imply more than that at some point in the future.
21257 Some ISPs are blocking port 25 in order to reduce the amount of spam
21258 being sent to their users.
21259 You may find that the submit option allows you to get around such a block.
21261 <P>
21262 <CENTER><SAMP>smtpserver.example.com/submit</SAMP></CENTER>
21263 <P>
21265 To specify any non-standard port number on the SMTP server you may follow
21266 the hostname with a colon followed by the portnumber.
21268 <P>
21269 <CENTER><SAMP>smtpserver.example.com:12345</SAMP></CENTER>
21270 <P>
21272 Normally, when a connection is made to the Smtp-Server Alpine will attempt
21273 to negotiate a secure (encrypted) session using Transport Layer Security (TLS).
21274 If that fails then a non-encrypted connection will be attempted instead.
21275 You may specify that a TLS connection is required if you wish.
21276 If you append "/tls" to the name then the connection will fail
21277 instead of falling back to a non-secure connection.
21279 <P>
21280 <CENTER><SAMP>smtpserver.example.com/tls</SAMP></CENTER>
21281 <P>
21284 For more details about server name possibilities see
21285 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
21286 <P>
21288 <UL>
21289 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21290 </UL>
21291 <P>
21292 <End of help on this topic>
21293 </BODY>
21294 </HTML>
21295 ====== h_config_nntp_server =====
21296 <HTML>
21297 <HEAD>
21298 <TITLE>OPTION: <!--#echo var="VAR_nntp-server"--></TITLE></HEAD>
21299 <BODY>
21300 <H1>OPTION: <!--#echo var="VAR_nntp-server"--></H1>
21302 This value specifies the name of one or more NNTP
21303 (Network News Transfer Protocol)
21304 servers for reading and posting USENET news.
21305 NNTP servers are normally
21306 set up by a system administrator for use by all members of a given campus
21307 or department.
21308 Contact your local help desk to ask what NNTP servers you should use.
21309 <!--chtml if pinemode="os_windows"--><!--chtml else-->
21310 Often Unix Alpine users will find that this variable has been
21311 set for the whole system (and they don't have to worry about it).
21312 <!--chtml endif-->
21313 When you define an NNTP server here, Alpine implicitly defines a news
21314 collection for you, assuming that server as the news server and assuming
21315 that you will use the NNTP protocol and a local newsrc configuration file
21316 for reading news.
21317 For more about reading news with Alpine, see
21318 <A HREF="h_reading_news">how to use Alpine to read news</A>.
21319 <P>
21320 Your NNTP server may offer NNTP "AUTHINFO SASL"
21321 or "AUTHINFO USER" authentication.
21322 It may even require it.
21323 If your NNTP server does offer such authentication you may specify a user name
21324 parameter to cause Alpine to attempt to authenticate.
21325 The same is true for the server name in a folder collection that uses NNTP.
21326 This parameter requires an associated value,
21327 the username identifier with which to establish the server connection.
21328 An example might be:
21330 <P>
21331 <CENTER><SAMP>nntpserver.example.com/user=katie</SAMP></CENTER>
21332 <P>
21334 If authentication is offered by the server, this will cause Alpine to
21335 attempt to use it.
21336 If authentication is not offered by the server, this will cause Alpine
21337 to fail with an error similar to:
21339 <P>
21340 <CENTER><SAMP>Error: NNTP authentication not available</SAMP></CENTER>
21341 <P>
21342 For more details about the server name possibilities see
21343 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
21344 <P><UL>
21345 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21346 </UL><P>
21347 <End of help on this topic>
21348 </BODY>
21349 </HTML>
21350 ====== h_config_inbox_path =====
21351 <HTML>
21352 <HEAD>
21353 <TITLE>OPTION: <!--#echo var="VAR_inbox-path"--></TITLE>
21354 </HEAD>
21355 <BODY>
21356 <H1>OPTION: <!--#echo var="VAR_inbox-path"--></H1>
21358 This value overrides the default value of your INBOX name/path/location.
21359 <!--chtml if pinemode="os_windows"-->
21360 PC-Alpine users must specify an inbox path and it must be a folder on an
21361 IMAP server.
21362 <!--chtml else-->
21363 Unix and VMS Alpine users will often find that this variable
21364 has been pre-configured by your system administrator.
21365 <!--chtml endif-->
21366 You may be able to specify an alternate INBOX that is either a local folder
21367 or a folder on an IMAP server.
21368 <P>
21369 A typical remote <!--#echo var="VAR_inbox-path"--> entry would be: {monet.art.example.com}INBOX
21370 where "monet.art.example.com" is replaced by the name of your IMAP
21371 mail server.
21372 <P>
21373 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21374 details on the syntax of folder definitions.
21375 <P>
21376 See <A HREF="h_info_on_mbox">Missing mail and the mbox driver</A> if your
21377 mail is disappearing.
21378 <P><UL>
21379 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21380 </UL><P>
21381 <End of help on this topic>
21382 </BODY>
21383 </HTML>
21384 ====== h_config_change_your_from =====
21385 <HTML>
21386 <HEAD>
21387 <TITLE>How to Change your From Address</TITLE>
21388 </HEAD>
21389 <BODY>
21390 <H1>How to Change your From Address</H1>
21392 If the From address that Alpine includes in mail that you send is not correct,
21393 you may want to configure a different default value for the From address.
21394 You may follow these directions to change the default:
21396 <P>
21397 <UL>
21398 <LI> Go to the Main Alpine Menu
21399 <LI> From there type the Setup Command
21400 <LI> From there type the Config Command
21401 </UL>
21403 <P>
21404 You've probably already seen this SETUP CONFIGURATION screen.
21405 If not, there are many options you may want to set here.
21406 To set the value of the From header you may use the
21407 <A href="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> option.
21408 Find it by scrolling down a few pages or use the WhereIs command to
21409 search for "customized".
21410 You may want to read the help text associated with the option.
21411 <P>
21412 To add a custom From header, type the Add command and enter the
21413 full header line, including the leading "From: ".
21414 For example:
21415 <P>
21416 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
21417 <P>
21418 Now exit the Setup command and try sending mail to yourself to see
21419 what the From line looks like.
21420 <P>
21421 When you are in the composer you may edit the custom From line by typing
21422 Ctrl-R while your cursor is in the headers of the message and then moving
21423 to the From line and editing.
21424 If you want to leave the default value the same but add the possibility
21425 of being able to edit the header when you compose, add just the header
21426 name without a value.
21427 For example:
21428 <P>
21429 <CENTER><SAMP>From:</SAMP></CENTER>
21430 <P>
21431 If you change your From address you may also find it useful to add the
21432 changed From address to the
21433 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
21434 configuration option.
21435 <P>
21436 <UL>
21437 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21438 </UL><P>
21439 <End of help on this topic>
21440 </BODY>
21441 </HTML>
21442 ====== h_config_default_fcc =====
21443 <HTML>
21444 <HEAD>
21445 <TITLE>OPTION: <!--#echo var="VAR_default-fcc"--></TITLE>
21446 </HEAD>
21447 <BODY>
21448 <H1>OPTION: <!--#echo var="VAR_default-fcc"--></H1>
21450 This value specifies where a copy of outgoing mail should be saved. If
21451 this is not a path name, it will be in the default collection for saves.
21452 Any valid folder specification, local or IMAP, is allowed. This default
21453 folder carbon copy only applies when the
21454 <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
21455 is set to use the default folder.
21456 <!--chtml if pinemode="os_windows"-->
21457 PC-Alpine default is "SENTMAIL" (normally stored as SENTMAIL.MTX)
21458 <!--chtml else-->
21459 Unix Alpine default
21460 is normally "sent-mail" in the default folder collection.
21461 <!--chtml endif-->
21462 <P>
21463 If you access your email through an IMAP server, especially if you often switch between Unix Alpine
21464 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on your
21465 IMAP server (remember that in order to later access this remote folder through Alpine, it
21466 must be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
21467 for more information). An example:<p>
21468 <CENTER><SAMP>{monet.art.example.com}mail/sent-mail</SAMP></CENTER>
21469 <P>
21470 To suppress saving of outgoing mail, set: <!--#echo var="VAR_default-fcc"-->=""
21471 <P>
21472 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21473 details on the syntax of folder definitions.
21474 <P>
21475 <UL>
21476 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21477 </UL><P>
21478 <End of help on this topic>
21479 </BODY>
21480 </HTML>
21481 ====== h_config_def_save_folder =====
21482 <HTML>
21483 <HEAD>
21484 <TITLE>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></TITLE>
21485 </HEAD>
21486 <BODY>
21487 <H1>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></H1>
21489 This option determines the default folder name for save-message operations
21490 ("saves").
21491 <P>
21492 If this is not a path name, it will be in the default collection for saves.
21493 Any valid folder specification, local or IMAP, is allowed. This default
21494 folder only applies when the
21495 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
21496 doesn't override it.
21497 <!--chtml if pinemode="os_windows"-->
21498 PC-Alpine default is "SAVEMAIL" (normally stored as SAVEMAIL.MTX).
21499 <!--chtml else-->
21500 Unix Alpine default
21501 is normally "saved-messages" in the default folder collection.
21502 <!--chtml endif-->
21503 If you access your email through an IMAP server, especially if you often switch between Unix
21504 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on an
21505 IMAP server (remember that in order to later access this remote folder through Alpine, it
21506 should be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
21507 for more information). An example:<p>
21508 <CENTER><SAMP>{monet.art.example.com}mail/saved-messages</SAMP></CENTER>
21509 <P>
21510 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21511 details on the syntax of folder definitions.
21512 <P>
21513 <UL>
21514 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21515 </UL><P>
21516 <End of help on this topic>
21517 </BODY>
21518 </HTML>
21519 ====== h_config_postponed_folder =====
21520 <HTML>
21521 <HEAD>
21522 <TITLE>OPTION: <!--#echo var="VAR_postponed-folder"--></TITLE>
21523 </HEAD>
21524 <BODY>
21525 <H1>OPTION: <!--#echo var="VAR_postponed-folder"--></H1>
21527 This value overrides the default name for the folder where postponed
21528 messages are saved. If this is not a path name, it will be in the default
21529 collection for message Saves. Any valid folder specification, local or
21530 remote, is allowed.
21531 PC-Alpine default
21532 is "POSTPOND" (stored as POSTPOND.MTX).
21533 The Unix Alpine default is normally "postponed-msgs"
21534 in the default collection.
21535 <P>
21536 Tip: If you are using different installations of (PC-)Alpine -- for example, PC-Alpine on your personal
21537 computer at home, and Unix Alpine on campus -- you can postpone a composition begun with one Alpine and
21538 resume it later with the other if you set this option to the <B>same folder on the same IMAP host</B>
21539 in all Alpine copies you use.
21540 (Remember that in order to later access this remote folder through Alpine, it must be in a folder
21541 collection. See <A HREF="h_what_are_collections">Folder Collections Extensions Explained</a>
21542 for more information). An
21543 example:<p>
21544 <CENTER><SAMP>{monet.art.example.com}mail/postponed-msgs</SAMP></CENTER>
21545 <P>
21546 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21547 details on the syntax of folder definitions.
21548 <P>
21549 <UL>
21550 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21551 </UL><P>
21552 <End of help on this topic>
21553 </BODY>
21554 </HTML>
21555 ====== h_config_read_message_folder =====
21556 <HTML>
21557 <HEAD>
21558 <TITLE>OPTION: <!--#echo var="VAR_read-message-folder"--></TITLE>
21559 </HEAD>
21560 <BODY>
21561 <H1>OPTION: <!--#echo var="VAR_read-message-folder"--></H1>
21563 By virtue of specifying a folder name here, Alpine will be configured to
21564 save all messages that you have read during a session into the designated
21565 "read messages" folder. This allows you to more easily distinguish
21566 between your really new email (in your INBOX) and those that you have
21567 already read. Depending on how you define the
21568 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
21569 setting, you may or may not be asked when you quit
21570 Alpine if you want read messages to be moved to this folder. In either
21571 case, moving the messages means they will be deleted from your INBOX.
21572 <P>
21573 If this is not a path name, it will be in the default collection for
21574 saves. Any valid folder specification, local or remote (via IMAP), is
21575 allowed. There is no default for the name of the read message folder.
21576 <P>
21577 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21578 details on the syntax of folder definitions.
21579 <P>
21580 <UL>
21581 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21582 </UL><P>
21583 <End of help on this topic>
21584 </BODY>
21585 </HTML>
21586 ====== h_config_form_folder =====
21587 <HTML>
21588 <HEAD>
21589 <TITLE>OPTION: <!--#echo var="VAR_form-letter-folder"--></TITLE>
21590 </HEAD>
21591 <BODY>
21592 <H1>OPTION: <!--#echo var="VAR_form-letter-folder"--></H1>
21594 A "<!--#echo var="VAR_form-letter-folder"-->" is a mail folder that is intended to
21595 contain messages that you have composed and that are intended to be
21596 sent in their original form repeatedly.
21598 <P>
21599 Setting this variable will alter Alpine's usual behavior when you
21600 execute the Compose command. Normally, Alpine offers a chance to
21601 continue a postponed or interrupted message should one or the other
21602 exist. When this variable is set to a folder name that exists, Alpine
21603 will also offer the chance to select a message from the folder to
21604 insert into the composer (much like when continuing a postponed message).
21605 The difference, however, is that Alpine will not automatically delete
21606 the selected message from the Form Letter Folder.
21607 <P>
21608 Setting this variable will also affect Alpine's behavior when you
21609 Postpone a message from the composer. Normally, Alpine simply stashes
21610 the message away in your
21611 "<A HREF="h_config_postponed_folder"><!--#echo var="VAR_postponed-folder"--></A>".
21612 Regardless of the specified folder's existence, Alpine will ask which
21613 folder you intend the message to be stored in. Choose the
21614 "F" option to store the message in your Form Letter Folder.
21615 This is the most common way to add a message to the folder.
21617 <P>
21618 Another method of adding messages to the folder is via the Alpine
21619 composer's <SAMP>Fcc:</SAMP> field. If you are sending a message that
21620 you expect to send in the same form again, you can enter the Form
21621 Letter Folder's name in this field. Alpine, as usual, will copy the
21622 message as it's sent. Note, when you later select this message from
21623 your Form Letter Folder, it will have the same recipients as the original
21624 message.
21626 <P>
21627 To delete a message from the Form Letter Folder, you can either select
21628 the folder from a suitable FOLDER LIST screen, or use the Delete
21629 command in the MESSAGE INDEX offered when selecting from the folder as
21630 part of the Compose command. You can delete a Form Letter Folder just
21631 as any other folder from a suitable FOLDER LIST screen.
21633 <P>
21634 You may find that the <A HREF="h_rules_roles">"Roles"</A>
21635 facility can be used
21636 to replace the Form Letter Folder.
21638 <P>
21639 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21640 details on the syntax of folder definitions.
21642 <P>
21643 <UL>
21644 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21645 </UL><P>
21646 <End of help on this topic>
21647 </BODY>
21648 </HTML>
21649 ====== h_config_archived_folders =====
21650 <HTML>
21651 <HEAD>
21652 <TITLE>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></TITLE>
21653 </HEAD>
21654 <BODY>
21655 <H1>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></H1>
21657 This is like
21658 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>,
21659 only more general. You may archive
21660 any of the folders in your incoming collection. This is a list of folder
21661 pairs, with the first separated from the second in the pair by a space.
21662 The first folder in a pair is the folder you want to archive, and the
21663 second folder is the folder that read messages from the first should be
21664 moved to. Depending on how you define the
21665 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
21666 setting, you may or may not be asked when you
21667 leave the first folder if you want read messages to be moved to the
21668 second folder. In either case, moving the messages means they will be
21669 deleted from the first folder.
21670 <P>
21671 The name of the first folder in each pair can be either the technical
21672 specification of the folder (like what appears in your configuration file)
21673 or (much easier) the nickname that you gave the folder when you made it
21674 an incoming folder.
21675 <p>
21676 For example:<p>
21677 <CENTER><SAMP>{monet.art.example.com}inbox {monet.art.example.com}mail/inbox-archive</SAMP></CENTER>
21678 <p>or, using nicknames:<p>
21679 <CENTER><SAMP>inbox inbox-archive</SAMP></CENTER>
21680 <P>
21681 If these are not path names, they will be in the default collection for
21682 saves. Any valid folder specification, local or remote (via IMAP), is
21683 allowed. There is no default.
21684 <P>
21685 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21686 details on the syntax of folder definitions.
21687 <P>
21688 <UL>
21689 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21690 </UL><P>
21691 <End of help on this topic>
21692 </BODY>
21693 </HTML>
21694 ====== h_config_newsrc_path ======
21695 <HTML>
21696 <HEAD>
21697 <TITLE>OPTION: <!--#echo var="VAR_newsrc-path"--></TITLE>
21698 </HEAD>
21699 <BODY>
21700 <H1>OPTION: <!--#echo var="VAR_newsrc-path"--></H1>
21702 This option overrides the default name Alpine uses for your "newsrc" news
21703 status and subscription file. If set, Alpine will take this value as the
21704 full pathname for the desired newsrc file.<P>
21706 If this option is <B>not</B> set,
21707 <!--chtml if pinemode="os_windows"-->
21708 PC-Alpine looks first for $HOME\NEWSRC (where $HOME defaults to the root
21709 of the current drive, e.g. "C:\") and then it looks in the same
21710 directory as your pinerc file for NEWSRC.
21711 <!--chtml else-->
21712 Unix Alpine looks for the file ~/.newsrc (that is, the file named .newsrc in
21713 your account's home directory).
21714 <!--chtml endif-->
21715 <P><UL>
21716 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21717 </UL>
21718 <P>
21719 <End of help on this topic>
21720 </BODY>
21721 </HTML>
21722 ====== h_config_literal_sig =====
21723 <HTML>
21724 <HEAD>
21725 <TITLE>OPTION: <!--#echo var="VAR_literal-signature"--></TITLE>
21726 </HEAD>
21727 <BODY>
21728 <H1>OPTION: <!--#echo var="VAR_literal-signature"--></H1>
21730 With this option your actual signature, as opposed to
21731 the name of a file containing your signature,
21732 is stored in the Alpine configuration file.
21733 If this is defined it takes precedence over the <!--#echo var="VAR_signature-file"--> option.
21734 <P>
21736 This is simply a different way to store the signature.
21737 The signature is stored inside your Alpine configuration file instead of in
21738 a separate file.
21739 Tokens work the same way they do with the
21740 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A> so look there for
21741 help.
21742 <P>
21744 The Setup/Signature command on Alpine's MAIN MENU will edit
21745 the "<!--#echo var="VAR_literal-signature"-->" by default. However, if no
21746 "<!--#echo var="VAR_literal-signature"-->" is defined and the file named in the
21747 "<!--#echo var="VAR_signature-file"-->" option exists, then the latter will be used
21748 instead.
21749 <P>
21751 The two character sequence \n (backslash followed by
21752 the character n) will be used to signify a line-break in your signature.
21753 You don't have to enter the \n, but it will be visible in the
21754 SETUP CONFIGURATION window after you are done editing the signature.
21756 <P>
21757 <UL>
21758 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21759 </UL><P>
21760 <End of help on this topic>
21761 </BODY>
21762 </HTML>
21763 ====== h_config_signature_file =====
21764 <HTML>
21765 <HEAD>
21766 <TITLE>OPTION: <!--#echo var="VAR_signature-file"--></TITLE>
21767 </HEAD>
21768 <BODY>
21769 <H1>OPTION: <!--#echo var="VAR_signature-file"--></H1>
21771 If a <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined,
21772 then this "<!--#echo var="VAR_signature-file"-->" option will be ignored.
21773 You can tell that that is the case because the value of the
21774 "<!--#echo var="VAR_signature-file"-->" will show up as
21775 <P>
21776 <CENTER><SAMP><Ignored: using <!--#echo var="VAR_literal-signature"--> instead></SAMP></CENTER>
21777 <P>
21778 You may either use all Literal Signatures (signatures stored in your
21779 configuration file) throughout Alpine, or all signature files.
21780 You can't mix the two.
21781 <P>
21782 This is the name of a file that will be automatically inserted into
21783 outgoing messages.
21784 It typically contains information such as your
21785 name, email address and organizational affiliation.
21786 Alpine adds the
21787 signature into the message as soon as you enter the composer so you
21788 can choose to remove it or edit it on a message by message basis.
21789 Signature file placement in message replies is controlled by the
21790 "<A HREF="h_config_sig_at_bottom"><!--#echo var="FEAT_signature-at-bottom"--></A>"
21791 setting in the feature list.
21792 <P>
21794 The default file name is
21795 <!--chtml if pinemode="os_windows"-->
21796 "PINE.SIG" in the same directory as your PINERC file if your
21797 PINERC file is a local file.
21798 If your PINERC file is remote, then it will be in the directory specified
21799 by the "-aux local_directory" command line option.
21800 <!--chtml else-->
21801 ".signature".
21802 <!--chtml endif-->
21803 <P>
21805 To create or edit your signature file choose Setup from the MAIN MENU
21806 and then select S for Signature (Main/Setup/Signature). This puts you
21807 into the Signature Editor where you can enter a <EM>few</EM> lines of
21808 text containing your identity and affiliation.
21810 <P>
21811 If the filename is followed by a vertical bar (|) then instead
21812 of reading the contents of the file the file is assumed to be a
21813 program that will produce the text to be used on its standard output.
21814 The program can't have any arguments and doesn't receive any input from Alpine,
21815 but the rest of the processing works as if the contents came from a file.
21817 <P>
21818 Instead of storing the data in a local file, the
21819 signature data may be stored remotely in an IMAP folder.
21820 In order to do this,
21821 you must use a remote name for the file.
21822 A remote <!--#echo var="VAR_signature-file"--> name might look like:
21823 <P>
21824 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/signature</SAMP></CENTER>
21825 <P>
21827 The syntax used here is the same as the syntax used for remote configuration
21828 files from the command line.
21829 Note that you may not access an existing signature file remotely,
21830 you have to create a new <EM>folder</EM> that contains the signature data.
21831 If the name you use here for the signature file is a remote name, then when
21832 you edit the file from the Setup/Signature command the data will be stored
21833 remotely in the folder.
21834 You aren't required to do anything special to create the folder, it
21835 gets created automatically if you use a remote name.
21837 <P>
21838 Besides regular text, the signature file may also contain
21839 (or a signature program may produce) tokens that
21840 are replaced with text that usually depends on the message you are replying
21841 to or forwarding.
21842 For example, if the signature file contains the token
21843 <P>
21844 <CENTER><SAMP>_DATE_</SAMP></CENTER>
21845 <P>
21846 anywhere in the text, then that token is replaced by the date
21847 the message you are replying to or forwarding was sent.
21848 If it contains
21849 <P>
21850 <CENTER><SAMP>_CURDATE_</SAMP></CENTER>
21851 <P>
21852 that is replaced with the current date.
21853 The first is an example of a token that depends on the message you
21854 are replying to (or forwarding) and the second is an example which
21855 doesn't depend on anything other than the current date.
21856 You have to be a little careful with this facility since tokens that
21857 depend on the message you are replying to or forwarding will be replaced
21858 by nothing in the case where you are composing a new message from scratch.
21859 The use of <A HREF="h_rules_roles">"roles"</A> may help you
21860 in this respect.
21861 It allows you to use different signature files in different cases.
21862 <P>
21864 The list of tokens available for use in the signature file is
21865 <A HREF="h_index_tokens">here</A>.
21866 <P>
21868 Instead of, or along with the use of "roles" to give you
21869 different signature files in different situations, there is also
21870 a way to conditionally include text based
21871 on whether or not a token would result in specific replacement text.
21872 For example, you could include some text based on whether or not
21873 the _NEWS_ token would result in any newsgroups if it was used.
21874 This is explained in detail
21875 <A HREF="h_reply_token_conditionals">here</A>.
21876 This isn't for the faint of heart.
21877 <P>
21878 In the very unlikely event that you want to include a literal token
21879 in the signature you must precede it with a backslash character.
21880 For example,
21881 <P>
21882 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
21883 <P>
21884 would produce something like
21885 <P>
21886 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
21887 <P>
21888 It is not possible to have a literal backslash followed by an expanded token.
21889 <P>
21890 An alternate method for storing the signature data is available by using the
21891 <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> configuration option.
21892 This variable will be used by default.
21893 <P>
21894 <UL>
21895 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21896 </UL><P>
21897 <End of help on this topic>
21898 </BODY>
21899 </HTML>
21900 ====== h_config_init_cmd_list =====
21901 <HTML>
21902 <HEAD>
21903 <TITLE>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></TITLE>
21904 </HEAD>
21905 <BODY>
21906 <H1>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></H1>
21908 The initial keystroke--or command--list option lets you start Alpine at
21909 any place you like.
21910 Whatever keystrokes you specify here will be executed
21911 by Alpine upon startup as a macro.
21912 The words SPACE, TAB, DOWN, UP, LEFT, and
21913 RIGHT indicate the pressing of those keys.
21914 CR indicates the pressing of the RETURN key.
21915 F1 through F12 represent the function keys, and ^ followed
21916 by a character indicates that key pressed along with the control key (in
21917 other words, ^P means Ctrl-P).
21918 As a shortcut notation, an element of the list may be several characters
21919 surrounded by double-quotes (").
21920 That will be expanded into the individual keystrokes
21921 (excluding the double-quote characters).
21922 For example, the quoted-string
21924 <P><CENTER>"ABC"</CENTER>
21926 <P>
21927 is interpreted the same as the three separate list members
21929 <P><CENTER>A and B and C</CENTER>
21931 <P>
21932 which is also the same as
21934 <P><CENTER>A,B,C</CENTER>
21936 <P>
21937 An example: To view message 1 on startup,
21938 you could use an <!--#echo var="VAR_initial-keystroke-list"--> equal to
21940 <P><CENTER>I,J,1,CR,V</CENTER>
21942 <P>
21943 An equivalent version of this is
21945 <P><CENTER>"IJ1",CR,V</CENTER>
21947 <P>
21948 Restrictions: You cannot pre-type into the composer with the initial
21949 keystroke list, and you cannot mix function key commands with letter
21950 commands.
21952 <P><UL>
21953 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21954 </UL>
21955 <P>
21956 <End of help on this topic>
21957 </BODY>
21958 </HTML>
21959 ====== h_config_comp_hdrs =====
21960 <html>
21961 <header>
21962 <title>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></title>
21963 </header>
21964 <body>
21965 <h1>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></h1>
21967 You can control which headers you want visible when composing outgoing
21968 email using this option.
21969 You can specify any of the regular set, any
21970 <A HREF="h_compose_richhdr">Rich Header</A>,
21971 or any <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
21972 that you have already defined.
21973 If you use this setting at all, you must specify all the
21974 headers you want to see, you can't just add to the regular header set.
21975 The default set is To:, Cc:, Attchmnt:, and Subject:.<p>
21977 Note that the "Newsgroups:" header will be abbreviated in the Composer
21978 display, but should be spelled out in full here.<p>
21979 <UL>
21980 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21981 </UL><P>
21982 <End of help on this topic>
21983 </body>
21984 </html>
21985 ====== h_config_custom_hdrs =====
21986 <HTML>
21987 <HEAD>
21988 <TITLE>OPTION: <!--#echo var="VAR_customized-hdrs"--></TITLE>
21989 </HEAD>
21990 <BODY>
21991 <H1>OPTION: <!--#echo var="VAR_customized-hdrs"--></H1>
21993 You may add your own custom headers to outgoing messages.
21994 Each header you specify here must include the header tag
21995 (<A HREF="h_composer_reply_to">Reply-To:</A>, Approved:, etc.)
21996 and may optionally include a value for that header.
21997 If you want to see these custom headers each time you compose a message,
21998 you must add them to your
21999 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> list,
22000 otherwise they become part
22001 of the rich header set that you only see when you press the
22002 <A HREF="h_compose_richhdr">Rich Header</A>
22003 <!--chtml if pinemode="function_key"-->(F5)
22004 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
22005 (If you are looking for a way to change which headers are <EM>displayed</EM>
22006 when you view a message, take a look at the
22007 <A HREF="h_config_viewer_headers"><!--#echo var="VAR_viewer-hdrs"--></A>
22008 option instead.)
22009 Here's an example that shows how you might set your From address
22010 <P>
22011 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
22012 <P>
22013 and another showing how you might set a Reply-To address
22014 <P>
22015 <CENTER><SAMP>Reply-To: user@example.com</SAMP></CENTER>
22016 <P>
22017 You may also set non-standard header values here.
22018 For example, you could add
22019 <P>
22020 <CENTER><SAMP>Organization: My Organization Name</SAMP></CENTER>
22021 <P>
22022 or even
22023 <P>
22024 <CENTER><SAMP>X-Favorite-Colors: Purple and Gold</SAMP></CENTER>
22025 <P>
22026 If you include a value after the colon then that header will be included
22027 in your outgoing messages unless you delete it before sending.
22028 If a header in the <!--#echo var="VAR_customized-hdrs"--> list has only a tag but no value, then
22029 it will not be included in outgoing messages unless you edit a value
22030 in manually.
22031 For example, if
22032 <P>
22033 <CENTER><SAMP>Reply-To:</SAMP></CENTER>
22034 <P>
22035 is in the list, then the Reply-To header will be available for editing
22036 but won't be included unless a value is added while in the composer.
22037 <P>
22038 It's actually a little more complicated than that.
22039 The values of headers that you set with the <!--#echo var="VAR_customized-hdrs"--> option are
22040 defaults.
22041 If the message you are about to compose already has a value for a header,
22042 that value is used instead of a value from your <!--#echo var="VAR_customized-hdrs"-->.
22043 For example, if you are Replying to a message the Subject field
22044 will already be filled in.
22045 In that case, if the <!--#echo var="VAR_customized-hdrs"--> list contains a Subject line, the
22046 custom subject will <EM>NOT</EM> be used.
22047 The subject derived from the subject of the message you are Replying
22048 to will be used instead.
22049 <P>
22050 It is also possible to make header setting even more complicated and more
22051 automatic by using
22052 <A HREF="h_rules_roles">Roles</A>,
22053 but if all you want to do is set a default value for a header, you don't
22054 need to think about Roles.
22055 <P>
22056 If you change your From address you may also find it useful to add the
22057 changed From address to the
22058 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
22059 configuration option.
22060 <P>
22061 Limitation: Because commas are used to separate the list of
22062 <!--#echo var="VAR_customized-hdrs"-->, it is not possible to have the value of a
22063 header contain a comma.
22064 Nor is there currently an "escape" mechanism provided
22065 to make this work.
22066 <P><UL>
22067 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22068 </UL>
22069 <P>
22070 <End of help on this topic>
22071 </BODY>
22072 </HTML>
22073 ====== h_config_viewer_headers =====
22074 <HTML>
22075 <HEAD>
22076 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdrs"--></TITLE>
22077 </HEAD>
22078 <BODY>
22079 <H1>OPTION: <!--#echo var="VAR_viewer-hdrs"--></H1>
22081 You may change the default list of headers that are viewed by listing
22082 the headers you want to view here. If the headers in your
22083 "<!--#echo var="VAR_viewer-hdrs"-->" list are present in the message, then they
22084 will be shown. The order of the headers you list will be honored. If
22085 the special value "all-except" is included as the first
22086 header in the "<!--#echo var="VAR_viewer-hdrs"-->" list, then all headers in the
22087 message except those in the list will be shown. The values are all
22088 case insensitive.
22090 <P>
22091 Note that once you put anything in the "<!--#echo var="VAR_viewer-hdrs"-->" list,
22092 then the original default headers are ignored. So, if you just wanted
22093 to add the header Organization to the list, you would have to list
22094 Organization plus all of the other headers originally in the default
22095 list. If you just included Organization and nothing else, then you
22096 would see only the Organization header, nothing else.
22098 <P>
22099 The default list of headers includes:
22100 <UL>
22101 <LI>From
22102 <LI>Resent-From
22103 <LI>To
22104 <LI>Resent-To
22105 <LI>Cc
22106 <LI>Resent-cc
22107 <LI>Bcc
22108 <LI>Newsgroups
22109 <LI>Followup-To
22110 <LI>Date
22111 <LI>Resent-Date
22112 <LI>Subject
22113 <LI>Resent-Subject
22114 <LI>Reply-To
22115 </UL>
22117 <P>
22118 If you are looking for a way to control which headers are included in
22119 outgoing mail and are visible or not in the composer, take a look at the
22120 options
22121 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22122 and <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> instead of
22123 this option.
22124 <P>
22125 <UL>
22126 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22127 </UL><P>
22128 <End of help on this topic>
22129 </BODY>
22130 </HTML>
22131 ====== h_config_viewer_margin_left =====
22132 <HTML>
22133 <HEAD>
22134 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-left"--></TITLE>
22135 </HEAD>
22136 <BODY>
22137 <H1>OPTION: <!--#echo var="VAR_viewer-margin-left"--></H1>
22139 This variable controls the left-hand vertical margin's width in
22140 Alpine's Message Viewing screen.
22141 Its value is the number of space characters preceding each displayed line.
22142 For consistency with
22143 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>,
22144 you may specify the column number to start in
22145 (column numbering begins with number 1)
22146 instead of the width of the margin by appending a lower case letter
22147 "c" to the number.
22148 For example, a value of "2c" means to start the text in column two,
22149 which is entirely equivalent to a value of "1", which means to
22150 leave a margin of 1 space.
22151 <P>
22152 The default is a left margin of 0 (zero).
22153 Misconfigurations (for example, negative values or values with starting
22154 left columns greater than the ending right column)
22155 are silently ignored.
22156 If the number of columns for text between the <!--#echo var="VAR_viewer-margin-left"--> and
22157 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22158 instead.
22160 <P>
22161 <End of help on this topic>
22162 </BODY>
22163 </HTML>
22164 ====== h_config_viewer_margin_right =====
22165 <HTML>
22166 <HEAD>
22167 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-right"--></TITLE>
22168 </HEAD>
22169 <BODY>
22170 <H1>OPTION: <!--#echo var="VAR_viewer-margin-right"--></H1>
22172 This variable controls the right-hand vertical margin's width in
22173 Alpine's Message Viewing screen.
22174 Its value is the number of space characters following each displayed line.
22175 You may specify the column number to end the text in
22176 (column numbering begins with number 1)
22177 instead of the width of the margin by appending a lower case letter
22178 "c" to the number.
22179 For example, a value of "76c" means to end the text in column 76.
22180 If the screen is 80 characters wide, this is equivalent to a value
22181 of "4", which means to leave a margin of 4 spaces.
22182 However, if you use different size screens at different times, then these
22183 two values are not equivalent.
22184 <P>
22185 The default right margin is 4.
22186 Misconfigurations (for example, negative values or values with starting
22187 left columns greater than the ending right column)
22188 are silently ignored.
22189 If the number of columns for text between the
22190 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
22191 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22192 instead.
22194 <P>
22195 <End of help on this topic>
22196 </BODY>
22197 </HTML>
22198 ====== h_config_quote_suppression =====
22199 <HTML>
22200 <HEAD>
22201 <TITLE>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></TITLE>
22202 </HEAD>
22203 <BODY>
22204 <H1>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></H1>
22206 This option should be used with care.
22207 It will cause some of the quoted text to be eliminated from the
22208 display when viewing a message in the MESSAGE TEXT screen.
22209 For example, if you set the <!--#echo var="VAR_quote-suppression-threshold"--> to the
22210 value "5",
22211 this will cause quoted text that is longer than five lines to be truncated.
22212 Quoted text of five or fewer consecutive lines will be displayed in its entirety.
22213 Quoted text of more than six lines will have the first five lines displayed
22214 followed by a line that looks something like
22215 <P>
22216 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
22217 <P>
22218 As a special case, if exactly one line of quoted text would be hidden, the
22219 entire quote will be shown instead.
22220 So for the above example, quoted text that is exactly six lines long will
22221 will be shown in its entirety.
22222 (In other words, instead of hiding a single line and adding a line
22223 that announces that one line was hidden, the line is just shown.)
22224 <P>
22225 If the sender of a message has carefully chosen the quotes that he or she
22226 includes, hiding those quotes may change the meaning of the message.
22227 For that reason, Alpine requires that when you want to set the value of this
22228 variable to something less than four lines, you actually have to set it
22229 to the negative of that number.
22230 So if you want to set this option to "3", you actually have to
22231 set it to "-3".
22232 The only purpose of this is to get you to think about whether or not you
22233 really want to do this!
22234 If you want to delete all quoted text you set the value of this option
22235 to the special value "-10".
22236 <P>
22237 The legal values for this option are
22238 <P>
22239 <TABLE>
22240 <TR>
22241 <TD> 0 </TD>
22242 <TD> Default, don't hide anything </TD>
22243 </TR>
22244 <TR>
22245 <TD> -1,-2,-3 </TD>
22246 <TD> Suppress quote lines past 1, 2, or 3 lines </TD>
22247 </TR>
22248 <TR>
22249 <TD> 4,5,6,... </TD>
22250 <TD> Suppress if more than that many lines </TD>
22251 </TR>
22252 <TR>
22253 <TD> -10 </TD>
22254 <TD> Suppress all quoted lines </TD>
22255 </TR>
22256 </TABLE>
22257 <P>
22258 If you set this option to a non-default value you may sometimes wish to
22259 view the quoted text that is not shown.
22260 When this is the case, the
22261 <A HREF="h_common_hdrmode">HdrMode Command</A>
22262 may be used to show the hidden text.
22263 Typing the "H" command once will show the hidden text.
22264 Typing a second "H" will also turn on Full Header mode.
22265 The presence or absence of the HdrMode command is determined by the
22266 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
22267 Feature-List option in your Alpine configuration, so you will want to
22268 be sure that is turned on if you use quote suppression.
22269 <P>
22270 For the purposes of this option, a quote is a line that begins with the
22271 character ">".
22272 <P>
22273 Quotes are only suppressed when displaying a message on the screen.
22274 The entire quote will be left intact when printing or forwarding or something
22275 similar.
22276 <P>
22277 <End of help on this topic>
22278 </BODY>
22279 </HTML>
22280 ====== h_config_saved_msg_name_rule =====
22281 <HTML>
22282 <HEAD>
22283 <TITLE>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></TITLE>
22284 </HEAD>
22285 <BODY>
22286 <H1>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></H1>
22288 This option determines the default folder name when saving
22289 a message.
22291 <P>
22292 The default option is "default-folder", which is the folder
22293 called "saved-messages" in Unix Alpine and
22294 "savemail" in PC-Alpine. To change the default folder, modify
22295 the Alpine option called
22296 <A HREF="h_config_def_save_folder">"<!--#echo var="VAR_default-saved-msg-folder"-->"</A>.
22298 <P>
22299 Choosing any of the "by-" options cause Alpine to attempt to
22300 get the chosen option's value for the message being saved (or for the
22301 first message being saved if using an aggregrate save).
22302 For example, if "by-from" is chosen, Alpine attempts to get the
22303 value of who the message came from (i.e. the from address).
22304 Alpine then attempts to save the message to a folder matching that value.
22305 If "by-from" is chosen and no value is obtained, Alpine uses
22306 "by-sender".
22307 The opposite is also true.
22308 If "by-recipient" is chosen and the message was posted to a
22309 newsgroup, Alpine will use the newsgroup name.
22310 If "by-replyto" is chosen and no value is obtained, Alpine uses
22311 "by-from".
22313 <P>
22314 If any of the "by-realname" options are chosen, Alpine will attempt
22315 to use the personal name part of the address instead of the mailbox part.
22316 If any of the "by-nick" options are chosen, the
22317 address is looked up in your address book and if found, the
22318 nickname for that entry is used.
22319 Only simple address book entries are checked, not distribution lists.
22320 Similarly, if any of the
22321 "by-fcc" options are chosen, the fcc from the corresponding
22322 address book entry is used.
22323 If by-realname, or the by-nick or by-fcc lookups result in no value,
22324 then if the chosen option ends with the "then-from",
22325 "then-sender", "then-replyto",
22326 or "then-recip" suffix, Alpine
22327 reverts to the same behavior as "by-from",
22328 "by-sender", "by-replyto", or "by-recip"
22329 depending on which option was specified.
22330 If the chosen option doesn't end with one of
22331 the "then-" suffixes, then Alpine reverts to the default
22332 folder when no match is found in the address book.
22334 <P>
22335 Choosing the option called "last-folder-used", causes Alpine
22336 to save to the folder that you saved to the last time you saved a
22337 message. The first time you save a message in an Alpine session, Alpine
22338 attempts to save the message to the default folder.
22340 <P>
22341 Here is an example to make some of the options clearer.
22342 If the message is From
22343 <P>
22344 <CENTER><SAMP>Fred Flintstone <flint@bedrock.org></SAMP></CENTER>
22345 <P>
22346 and this rule is set to "by-from", then the default folder offered
22347 in the save dialog would be "flint".
22348 <P>
22349 If this rule is set to "by-realname-of-from" then the default would
22350 be "Fred Flintstone".
22351 <P>
22352 If this rule is set to "by-nick-of-from" then Alpine will search
22353 for the address "flint@bedrock.org" in your address book.
22354 If an entry is found and it has a nickname associated with it, that nickname
22355 will be offered as the default folder.
22356 If not, the default saved message folder will be offered as the default.
22357 <P>
22358 If this rule is set to "by-fcc-of-from" then Alpine will search
22359 for the address "flint@bedrock.org" in your address book.
22360 If an entry is found and it has an Fcc associated with it, that Fcc
22361 will be offered as the default folder.
22362 If not, the default saved message folder will be offered as the default.
22363 <P>
22364 If this rule is set to "by-nick-of-from-then-from" then Alpine will search
22365 for the address "flint@bedrock.org" in your address book.
22366 If an entry is found and it has a nickname associated with it, that nickname
22367 will be offered as the default folder.
22368 If it is not found (or has no nickname) then the default offered will be
22369 the same as it would be for the "by-from" rule.
22370 That is, it would be "flint"
22371 <P>
22372 <UL>
22373 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22374 </UL><P>
22375 <End of help on this topic>
22376 </BODY>
22377 </HTML>
22378 ====== h_config_fcc_rule =====
22379 <HTML>
22380 <HEAD>
22381 <TITLE>OPTION: <!--#echo var="VAR_fcc-name-rule"--></TITLE>
22382 </HEAD>
22383 <BODY>
22384 <H1>OPTION: <!--#echo var="VAR_fcc-name-rule"--></H1>
22386 This option determines the default name for folder carbon copy. Choose
22387 one:
22389 <DL>
22390 <DT>default-fcc</DT>
22391 <DD>This is the normal default, the value of which is set in the
22392 "<!--#echo var="VAR_default-fcc"-->" variable as specified earlier in this
22393 configuration.
22394 </DD>
22396 <DT>last-fcc-used</DT>
22397 <DD> Causes Alpine to use the folder that was last
22398 used in the fcc field
22399 </DD>
22401 <DT>by-nickname</DT>
22402 <DD>Means that Alpine will use the nickname
22403 from your address book that matches the first address in the To line.
22404 If there is no match, it will use the value of the
22405 "<!--#echo var="VAR_default-fcc"-->" variable.
22406 </DD>
22408 <DT>by-recipient</DT>
22409 <DD>Means Alpine will form a folder name
22410 based on the left hand side of the first address in the To line.
22411 </DD>
22413 <DT>by-nick-then-recip</DT>
22414 <DD>Means that it will use the
22415 matching nickname from your address book if there is one, otherwise it
22416 will extract the recipient name from the address and use that (like
22417 by-recipient).
22418 </DD>
22420 <DT>current-folder</DT>
22421 <DD>Causes a copy to be written to
22422 the currently open folder, unless that is the INBOX. In the case
22423 where the current folder is the INBOX, the "<!--#echo var="VAR_default-fcc"-->" is
22424 used instead.
22425 </DD>
22426 </DL>
22428 <P>
22429 Note: Whatever the fcc specified by the rule here, it will be
22430 over-ridden by any fcc entries you have in your address book.
22432 <P>
22433 <UL>
22434 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22435 </UL><P>
22436 <End of help on this topic>
22437 </BODY>
22438 </HTML>
22439 ====== h_config_sort_key =====
22440 <HTML>
22441 <HEAD>
22442 <TITLE>OPTION: <!--#echo var="VAR_sort-key"--></TITLE>
22443 </HEAD>
22444 <BODY>
22445 <H1>OPTION: <!--#echo var="VAR_sort-key"--></H1>
22447 This option determines the order in which messages will be displayed in
22448 the MESSAGE INDEX screen. Choose from:
22449 <P>
22450 <UL>
22451 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
22452 <LI> <A HREF="h_index_sort_date">Date</A>
22453 <LI> <A HREF="h_index_sort_subj">Subject</A>
22454 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
22455 <LI> <A HREF="h_index_sort_thread">Thread</A>
22456 <LI> <A HREF="h_index_sort_from">From</A>
22457 <LI> <A HREF="h_index_sort_size">Size</A>
22458 <LI> <A HREF="h_index_sort_score">Score</A>
22459 <LI> <A HREF="h_index_sort_to">To</A>
22460 <LI> <A HREF="h_index_sort_cc">Cc</A>
22461 </UL>
22463 <P>
22464 Each type of sort may also be reversed.
22465 Normal default is by "Arrival".
22467 <P>
22468 A possible point of confusion arises when you change the configuration
22469 of the <!--#echo var="VAR_sort-key"-->.
22470 The folder will normally be re-sorted when you go back to viewing the
22471 index.
22472 However, if you have manually sorted the folder with the
22473 Sort
22474 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
22475 command, then it will not be re-sorted until the next time it is opened.
22477 <P>
22478 <UL>
22479 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22480 </UL><P>
22481 <End of help on this topic>
22482 </BODY>
22483 </HTML>
22484 ====== h_config_other_startup =====
22485 <HTML>
22486 <HEAD>
22487 <TITLE>OPTION: Set Startup Rule</TITLE>
22488 </HEAD>
22489 <BODY>
22490 <H1>OPTION: Set Startup Rule</H1>
22492 This option determines which message will be the <EM>current message</EM> when
22493 the folder is first opened.
22494 It works the same way that the option
22495 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
22496 works, so look there for help.
22497 It may be used for any folder, not just incoming folders.
22499 <P>
22500 <UL>
22501 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22502 </UL><P>
22503 <End of help on this topic>
22504 </BODY>
22505 </HTML>
22506 ====== h_config_perfolder_sort =====
22507 <HTML>
22508 <HEAD>
22509 <TITLE>Set Sort Order</TITLE>
22510 </HEAD>
22511 <BODY>
22512 <H1>Set Sort Order</H1>
22514 This option determines the order in which messages will be displayed in
22515 the MESSAGE INDEX screen when the Current Folder Type set in the
22516 Pattern is a match. Choose from:
22517 <P>
22518 <UL>
22519 <LI> <A HREF="h_index_sort_default">Default</A>
22520 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
22521 <LI> <A HREF="h_index_sort_date">Date</A>
22522 <LI> <A HREF="h_index_sort_subj">Subject</A>
22523 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
22524 <LI> <A HREF="h_index_sort_thread">Thread</A>
22525 <LI> <A HREF="h_index_sort_from">From</A>
22526 <LI> <A HREF="h_index_sort_size">Size</A>
22527 <LI> <A HREF="h_index_sort_score">Score</A>
22528 <LI> <A HREF="h_index_sort_to">To</A>
22529 <LI> <A HREF="h_index_sort_cc">Cc</A>
22530 </UL>
22532 <P>
22533 Each type of sort may also be reversed.
22534 Normal default is by "Arrival".
22536 <P>
22537 A possible point of confusion arises when you change the configuration
22538 of the Sort Order for the currently open folder.
22539 The folder will normally be re-sorted when you go back to viewing the
22540 index.
22541 However, if you have manually sorted the folder with the
22542 Sort
22543 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
22544 command, then it will not be re-sorted until the next time it is opened.
22546 <P>
22547 <UL>
22548 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22549 </UL><P>
22550 <End of help on this topic>
22551 </BODY>
22552 </HTML>
22553 ====== h_config_fld_sort_rule =====
22554 <HTML>
22555 <HEAD>
22556 <TITLE>OPTION: <!--#echo var="VAR_folder-sort-rule"--></TITLE>
22557 </HEAD>
22558 <BODY>
22559 <H1>OPTION: <!--#echo var="VAR_folder-sort-rule"--></H1>
22561 This option controls the order in which folder list entries will be
22562 presented in the FOLDER LIST screen. Choose one of the following:
22564 <DL>
22565 <DT>Alphabetical</DT>
22566 <DD>sort by alphabetical name independent of type
22567 </DD>
22569 <DT>Alpha-with-dirs-last</DT>
22570 <DD>sort by alphabetical name grouping directory entries
22571 to the end of the list
22572 </DD>
22574 <DT>Alpha-with-dirs-first</DT>
22575 <DD>sort by alphabetical name grouping directory entries
22576 to the start of the list
22577 </DD>
22578 </DL>
22580 The normal default is "Alphabetical".
22582 <P>
22583 <UL>
22584 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22585 </UL><P>
22586 <End of help on this topic>
22587 </BODY>
22588 </HTML>
22589 ====== h_config_ab_sort_rule =====
22590 <HTML>
22591 <HEAD>
22592 <TITLE>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></TITLE>
22593 </HEAD>
22594 <BODY>
22595 <H1>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></H1>
22597 This option controls the order in which address book entries will be
22598 presented. Choose one of the following:
22600 <DL>
22601 <DT>fullname</DT>
22602 <DD>use fullname field, lists mixed in
22603 </DD>
22605 <DT>fullname-with-lists-last</DT>
22606 <DD>use fullname field, but put lists at end
22607 </DD>
22609 <DT>nickname</DT>
22610 <DD>use nickname field, lists mixed in
22611 </DD>
22613 <DT>nickname-with-lists-last</DT>
22614 <DD>use nickname field, but put lists at end
22615 </DD>
22617 <DT>dont-sort</DT>
22618 <DD>don't change order of file
22619 </DD>
22620 </DL>
22622 <P>
22623 The normal default is "fullname-with-lists-last".
22624 If you use an address book from more than one computer and those
22625 computers sort the address book differently then the sort order
22626 will be the order where the last change to the address book was
22627 made.
22628 There are two reasons the sorting might be different on different
22629 systems.
22630 First, the <!--#echo var="VAR_addrbook-sort-rule"--></a> may be set differently in the two
22631 places.
22632 Second, the collation rules on the two computers may be different.
22633 For example, one system might ignore special characters while the other
22634 doesn't or one may sort upper and lower case letters together while
22635 the other doesn't.
22636 In any case, the order you see is the order on the system where the
22637 last change was made, for example by an address book edit or a
22638 Take Address command.
22640 <P>
22641 <UL>
22642 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22643 </UL><P>
22644 <End of help on this topic>
22645 </BODY>
22646 </HTML>
22647 ====== h_config_post_char_set =====
22648 <HTML>
22649 <HEAD>
22650 <TITLE>OPTION: <!--#echo var="VAR_posting-character-set"--></TITLE>
22651 </HEAD>
22652 <BODY>
22653 <H1>OPTION: <!--#echo var="VAR_posting-character-set"--></H1>
22655 The <!--#echo var="VAR_posting-character-set"--> configuration option is used
22656 when sending messages.
22658 <P>
22660 When sending a message the text typed in the composer is
22661 labeled with the character set specified by this option.
22662 If the composed text is not fully representable in the
22663 specified <!--#echo var="VAR_posting-character-set"-->, then it is labeled as "UTF-8."
22664 instead;
22666 <P>
22667 Attachments are labeled with your
22668 <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>.
22670 <P>
22671 Generally, there should be little need to set this option.
22672 If left unset, the
22673 default behavior is to label composed text as specifically as
22674 possible. That is, if the composed text has no non-ASCII characters,
22675 it is labeled as "US-ASCII." Similarly, if it is composed of
22676 only ISO-8859-15 characters, it is labeled as such. Alpine will
22677 attempt to automatically detect a number of character sets including ISO-8859-15,
22678 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
22679 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, and EUC-KR.
22680 If the message contains a mix of character sets,
22681 it is labeled as "UTF-8."
22683 <P>
22685 This setting is provided to allow you to force a particular character set that
22686 Alpine does not automatically detect. For example, if a message is representable
22687 in more than one character set then Alpine may choose a different default
22688 than you want.
22689 Lastly, by setting this option explicitly to
22690 "UTF-8" all non-ASCII messages you send will be labeled as
22691 "UTF-8" instead of something more specific.
22693 <P>
22694 In the Setup/Config screen you may choose from a list of all the
22695 character sets Alpine knows about by using the "T" ToCharsets command.
22697 <P>
22698 The options
22699 <A HREF="h_config_char_set">"Display Character Set"</A>
22700 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
22701 are closely related.
22702 Setting the feature
22703 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
22704 should cause this option to be ignored.
22706 <P>
22707 <UL>
22708 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22709 </UL><P>
22710 <End of help on this topic>
22711 </BODY>
22712 </HTML>
22713 ====== h_config_unk_char_set =====
22714 <HTML>
22715 <HEAD>
22716 <TITLE>OPTION: <!--#echo var="VAR_unknown-character-set"--></TITLE>
22717 </HEAD>
22718 <BODY>
22719 <H1>OPTION: <!--#echo var="VAR_unknown-character-set"--></H1>
22721 The <!--#echo var="VAR_unknown-character-set"--> configuration option is used
22722 when reading or replying to messages.
22724 <P>
22726 A text message should either be made up of all US-ASCII characters
22727 or it should contain a charset label which tells the software which
22728 character set encoding to use to interpret the message.
22729 Sometimes a malformed message may be unlabeled but contain non-ascii text.
22730 This message is outside of the standards so any attempt to read it could fail.
22731 When Alpine attempts to read such a message it will try to interpret the
22732 text in the character set you specify here.
22733 For example, if you have correspondents who send you unlabeled messages that
22734 are usually made up of characters from the WINDOWS-1251 character set, setting
22735 this <!--#echo var="VAR_unknown-character-set"--> to <CODE>WINDOWS-1251</CODE> will
22736 allow you to read those messages.
22737 Of course, if the unlabeled message is actually in some other character set,
22738 then you may see garbage on your screen.
22739 <P>
22740 Instead of just unlabeled text, this option also affects text which is labeled
22741 with the charsets "X-Unknown" or "US-ASCII".
22743 <P>
22744 In the Setup/Config screen you may choose from a list of all the
22745 character sets Alpine knows about by using the "T" ToCharsets command.
22747 <P>
22748 <UL>
22749 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22750 </UL><P>
22751 <End of help on this topic>
22752 </BODY>
22753 </HTML>
22754 ====== h_config_char_set =====
22755 <HTML>
22756 <HEAD>
22757 <TITLE>OPTION: Display Character Set</TITLE>
22758 </HEAD>
22759 <BODY>
22760 <H1>OPTION: Display Character Set</H1>
22762 The Display Character Set configuration option is used when viewing messages.
22763 <P>
22764 Alpine uses Unicode characters internally and
22765 it is a goal for Alpine to handle email in many different languages.
22766 Alpine will properly display only left-to-right character sets
22767 in a fixed-width font. Specifically, Alpine assumes that a fixed-width
22768 font is in use, in the sense that
22769 characters are assumed to take up zero, one, or two character cell
22770 widths from left to right on the screen. This is true even in PC-Alpine.
22771 <P>
22773 Alpine recognizes some local character sets that are right-to-left
22774 (Arabic, Hebrew, and Thai) or not representable in a fixed-width font
22775 (Arabic) and properly converts texts in these character sets to/from
22776 Unicode; however, there are known display bugs with these character
22777 sets.
22778 <P>
22780 There are three possible configuration character settings and some
22781 environment variable settings that can affect how Alpine
22782 handles international characters.
22783 The first two of these are only available in UNIX Alpine.
22784 The three configuration options are
22785 Display Character Set,
22786 Keyboard Character Set, and
22787 <!--#echo var="VAR_posting-character-set"-->.
22788 The Keyboard Character Set defaults to being the same value
22789 as the Display Character Set, and that is usually correct, because
22790 the keyboard almost always produces characters in the same character set
22791 as the display displays.
22792 The Display Character Set is the character set that Alpine
22793 will attempt to use when sending characters to the display.
22794 <P>
22796 By default, the Display Character Set variable is not set and UNIX Alpine
22797 will attempt to get this information from the environment.
22798 In particular, the <CODE>nl_langinfo(CODESET)</CODE> call is used.
22799 This usually depends on the setting of the environment variables LANG or LC_CTYPE.
22800 An explicit configuration setting for Display Character Set will,
22801 of course, override any default setting.
22802 <P>
22803 For PC-Alpine the Display Character Set
22804 and the Keyboard Character Set
22805 are always equivalent to <CODE>UTF-8</CODE> and this is not settable.
22806 <P>
22808 It is probably best to use UNIX Alpine in a terminal emulator
22809 capable of displaying UTF-8 characters, since that will allow you to
22810 view just about any received text that is correctly formatted (note,
22811 however, the above comments about known index display bugs with certain
22812 character sets). You'll need to have an emulator that uses a UTF-8 font
22813 and you'll need to set up your environment to use a UTF-8 charmap. For
22814 example, on a Linux system you might include
22815 <P>
22816 <CENTER> <CODE>setenv LANG en_US.UTF-8</CODE> </CENTER>
22817 <P>
22819 or something similar in your UNIX startup files.
22820 You'd also have to select a UTF-8 font in your terminal emulator.
22821 <P>
22823 The types of values that the character set variables may be set to are
22824 <CODE>UTF-8</CODE>, <CODE>ISO-8859-1</CODE>, or <CODE>EUC-JP</CODE>.
22825 The <CODE>ISO-2022</CODE> character sets are not supported for input or
22826 for display, but as a special case, <CODE>ISO-2022-JP</CODE> is supported
22827 for use only as a <!--#echo var="VAR_posting-character-set"-->.
22828 In the Setup/Config screen you may choose from a list of all the
22829 character sets Alpine knows about by using the "T" ToCharsets command.
22830 Here is a list of many of the possible character sets:
22832 <P>
22833 <TABLE>
22834 <TR> <TD>UTF-8</TD> <TD>Unicode</TD> </TR>
22835 <TR> <TD>US-ASCII</TD> <TD>7 bit American English characters</TD> </TR>
22836 <TR> <TD>ISO-8859-1</TD> <TD>8 bit European "Latin 1" character set</TD> </TR>
22837 <TR> <TD>ISO-8859-2</TD> <TD>8 bit European "Latin 2" character set</TD> </TR>
22838 <TR> <TD>ISO-8859-3</TD> <TD>8 bit European "Latin 3" character set</TD> </TR>
22839 <TR> <TD>ISO-8859-4</TD> <TD>8 bit European "Latin 4" character set</TD> </TR>
22840 <TR> <TD>ISO-8859-5</TD> <TD>8 bit Latin and Cyrillic</TD> </TR>
22841 <TR> <TD>ISO-8859-6</TD> <TD>8 bit Latin and Arabic</TD> </TR>
22842 <TR> <TD>ISO-8859-7</TD> <TD>8 bit Latin and Greek</TD> </TR>
22843 <TR> <TD>ISO-8859-8</TD> <TD>8 bit Latin and Hebrew</TD> </TR>
22844 <TR> <TD>ISO-8859-9</TD> <TD>8 bit European "Latin 5" character set</TD> </TR>
22845 <TR> <TD>ISO-8859-10</TD> <TD>8 bit European "Latin 6" character set</TD> </TR>
22846 <TR> <TD>ISO-8859-11</TD> <TD>Latin and Thai</TD> </TR>
22847 <TR> <TD>ISO-8859-12</TD> <TD>Reserved</TD> </TR>
22848 <TR> <TD>ISO-8859-13</TD> <TD>8 bit European "Latin 7" character set</TD> </TR>
22849 <TR> <TD>ISO-8859-14</TD> <TD>8 bit European "Latin 8" character set</TD> </TR>
22850 <TR> <TD>ISO-8859-15</TD> <TD>8 bit European "Latin 9" character set</TD> </TR>
22851 <TR> <TD>ISO-8859-16</TD> <TD>8 bit European "Latin 10" character set</TD> </TR>
22852 <TR> <TD>KOI8-R</TD> <TD>8 bit Latin and Russian</TD> </TR>
22853 <TR> <TD>KOI8-U</TD> <TD>8 bit Latin and Ukranian</TD> </TR>
22854 <TR> <TD>WINDOWS-1251</TD> <TD>8 bit Latin and Russian</TD> </TR>
22855 <TR> <TD>TIS-620</TD> <TD>8 bit Latin and Thai</TD> </TR>
22856 <TR> <TD>VISCII</TD> <TD>8 bit Latin and Vietnamese</TD> </TR>
22857 <TR> <TD>GBK</TD> <TD>Latin and Chinese Simplified</TD> </TR>
22858 <TR> <TD>GB2312</TD> <TD>Latin and Chinese Simplified</TD> </TR>
22859 <TR> <TD>CN-GB</TD> <TD>Latin and Chinese Simplified</TD> </TR>
22860 <TR> <TD>BIG5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
22861 <TR> <TD>BIG-5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
22862 <TR> <TD>EUC-JP</TD> <TD>Latin and Japanese</TD> </TR>
22863 <TR> <TD>SHIFT-JIS</TD> <TD>Latin and Japanese</TD> </TR>
22864 <TR> <TD>EUC-KR</TD> <TD>Latin and Korean</TD> </TR>
22865 <TR> <TD>KSC5601</TD> <TD>Latin and Korean</TD> </TR>
22866 </TABLE>
22867 <P>
22869 When reading incoming email, Alpine understands many different
22870 character sets and is able to convert the incoming mail into Unicode.
22871 The Unicode will be converted to the Display Character Set
22872 for display on your terminal.
22873 Characters typed at the keyboard will be converted from the
22874 Keyboard Character Set to Unicode for Alpine's internal
22875 use.
22876 You may find that you can read some malformed messages that do not
22877 contain a character set label by setting the option
22878 <A HREF="h_config_unk_char_set">"<!--#echo var="VAR_unknown-character-set"-->"</A>.
22879 <P>
22881 The <!--#echo var="VAR_posting-character-set"--> is used when sending messages.
22882 The default behavior obtained by leaving this variable unset is usually
22883 what is wanted. In that default case, Alpine will attempt
22884 to label the message with the most specific character set from the
22885 rather arbitrary set
22886 <P>
22887 US-ASCII, ISO-8859-15,
22888 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
22889 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, EUC-KR, and UTF-8.
22890 <P>
22892 For example, if the message is made up of only US-ASCII characters, it
22893 will be labeled US-ASCII. Otherwise, if it is all ISO-8859-15 characters,
22894 that will be the label. If that doesn't work the same is tried for the
22895 remaining members of the list.
22897 <P>
22898 It might make sense to set <!--#echo var="VAR_posting-character-set"--> to an
22899 explicit value instead.
22900 For example, if you usually send messages in Greek, setting this
22901 option to ISO-8859-7 will result in messages being labeled as
22902 US-ASCII if there are no non-ascii characters, ISO-8859-7 if there
22903 are only Greek characters, or UTF-8 if there are some characters
22904 that aren't representable in ISO-8859-7.
22905 Another possibility is to set this option explicitly to UTF-8.
22906 In that case
22907 Alpine labels only ascii messages as US-ASCII and all other
22908 messages as UTF-8.
22909 <P>
22911 The options
22912 <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
22913 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
22914 are closely related to this option.
22915 Setting the feature
22916 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
22917 should cause this option to be ignored.
22919 <P>
22920 When displaying a message, Alpine compares this setting to the character
22921 set specified in the message. If not all of the
22922 characters in the message can be displayed using the Display Character Set
22923 then Alpine places an editorial
22924 comment in the displayed text (enclosed in square-brackets) indicating
22925 that some characters may not be displayed correctly.
22926 This comment may be eliminated by turning on the option
22927 <A HREF="h_config_quell_charset_warning"><!--#echo var="FEAT_quell-charset-warning"--></A>.
22929 <P>
22930 <UL>
22931 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22932 </UL><P>
22933 <End of help on this topic>
22934 </BODY>
22935 </HTML>
22936 ====== h_config_key_char_set =====
22937 <HTML>
22938 <HEAD>
22939 <TITLE>OPTION: Keyboard Character Set</TITLE>
22940 </HEAD>
22941 <BODY>
22942 <H1>OPTION: Keyboard Character Set</H1>
22944 UNIX Alpine only.
22945 <P>
22946 The Keyboard Character Set identifies the character set of the characters
22947 coming from your keyboard.
22948 It defaults to having the same value as your
22949 <A HREF="h_config_char_set">"Display Character Set"</A>,
22950 which in turn defaults to a value obtained from your environment.
22951 It is unlikely that you will need to use this option, because the keyboard
22952 almost always produces the same kind of characters as the display displays.
22954 <P>
22955 This character set is also used when accessing files in your local
22956 file system.
22957 The names of the files are assumed to be in the same character set as
22958 what the keyboard produces, as well as the contents of the files.
22960 <P>
22961 In the Setup/Config screen you may choose from a list of all the
22962 character sets Alpine knows about by using the "T" ToCharsets command.
22964 <P>
22965 The options
22966 <A HREF="h_config_char_set">"Display Character Set"</A>
22967 and <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
22968 are closely related.
22969 Setting the feature
22970 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
22971 should cause this option to be ignored.
22973 <P>
22974 <UL>
22975 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22976 </UL><P>
22977 <End of help on this topic>
22978 </BODY>
22979 </HTML>
22980 ====== h_config_editor =====
22981 <HTML>
22982 <HEAD>
22983 <TITLE>OPTION: <!--#echo var="VAR_editor"--></TITLE>
22984 </HEAD>
22985 <BODY>
22986 <H1>OPTION: <!--#echo var="VAR_editor"--></H1>
22988 <!--#echo var="VAR_editor"--> specifies the program invoked by ^_ in the Composer. This is
22989 normally an alternative to Alpine's internal composer (Pico). You could use
22990 this setting to specify an alternate editor to use occasionally or if you
22991 have a favorite editor and want to use it all the time (see the
22992 <A HREF="h_config_alt_ed_now">"<!--#echo var="FEAT_enable-alternate-editor-implicitly"-->"</A> setting). <P>
22993 If you specify multiple editors for this option, ^_ will invoke the first one
22994 of those specified that exists and is executable. When specifying a program
22995 for use here, make sure that the format of the text it saves -- which, when
22996 you exit it, will become the message body in Alpine -- is appropriate
22997 for the body of an email message; avoid proprietary formats that may result in
22998 a message body that the recipient of your message will be unable to decipher.
22999 <P>
23000 <!--chtml if pinemode="os_windows"-->
23001 <!--chtml else-->
23002 If you are in doubt about what editors are available on your system, or which
23003 of them may be appropriate for specification here, ask your local computing
23004 support staff.
23005 <!--chtml endif-->
23006 <P>
23007 Note that if <a href="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></a> is
23008 unset, outgoing text will be set as flowed. In most cases this will be fine,
23009 but if the editor has a "flowed text" mode, it would be best to
23010 use that.
23012 <P><UL>
23013 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23014 </UL>
23015 <P>
23016 <End of help on this topic>
23017 </BODY>
23018 </HTML>
23019 ====== h_config_speller =====
23020 <HTML>
23021 <HEAD>
23022 <TITLE>OPTION: <!--#echo var="VAR_speller"--></TITLE>
23023 </HEAD>
23024 <BODY>
23025 <H1>OPTION: <!--#echo var="VAR_speller"--></H1>
23027 UNIX Alpine only.
23028 <P>
23029 For PC-Alpine, you must install the aspell library code that you
23030 may get from
23031 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
23032 <P>
23033 This option affects the behavior of the ^T (spell check) command in the
23034 Composer. It specifies the program invoked by ^T in the Composer.
23035 By default, Alpine uses
23036 <P>
23037 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
23038 <P>
23039 if it knows where to find "aspell".
23040 If there is no "aspell" command available but the command "ispell" is available
23041 then the command used is
23042 <P>
23043 <CENTER><SAMP>ispell -l</SAMP></CENTER>
23044 <P>
23045 Otherwise, the ancient "spell" command is used.
23046 <P>
23047 If you specify a value for this command (with full pathname) then that is what
23048 will be used instead of any of the defaults.
23049 When invoking this
23050 spell-checking program, Alpine appends a tempfile name (where the message is
23051 passed) to the command line. Alpine expects the speller to correct the
23052 spelling in that file. When you exit from that program Alpine will read the
23053 tempfile back into the composer.
23054 <P>
23055 Don't set this speller option to the standard Unix spell command.
23056 That won't work because spell works in a different way.
23058 <P>
23059 <UL>
23060 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23061 </UL><P>
23062 <End of help on this topic>
23063 </BODY>
23064 </HTML>
23065 ====== h_config_display_filters =====
23066 <HTML>
23067 <HEAD>
23068 <TITLE>OPTION: <!--#echo var="VAR_display-filters"--></TITLE>
23069 </HEAD>
23070 <BODY>
23071 <H1>OPTION: <!--#echo var="VAR_display-filters"--></H1>
23073 This option defines a list of text-filtering commands (programs or
23074 scripts) that may be used to filter text portions of received messages
23075 prior to their use (e.g., presentation in the "MESSAGE TEXT"
23076 display screen, exporting to a text file).
23077 For security reasons, the full path name of the
23078 filter command must be specified.
23080 <P>
23081 The command is executed and the message is piped into its standard input.
23082 The standard output of the command is read back by Alpine. The
23083 "_TMPFILE_" token (see below) overrides this default behavior.
23085 <P>
23086 The filter's use is based on the configured "trigger" string. The
23087 format of a filter definition is:
23089 <P>
23090 <CENTER><trigger> <command> <arguments></CENTER>
23092 <P>
23093 You can specify as many filters as you wish, separating them with a comma.
23094 Each filter can have only one trigger and command. Thus, two trigger
23095 strings that invoke the same command require separate filter
23096 specifications.
23098 <P>
23099 The "trigger" is simply text that, if found in the message,
23100 will invoke the associated command. If the trigger contains any space
23101 characters, it must be placed within quotes. Likewise, should you
23102 wish a filter to be invoked unconditionally, define the trigger as the
23103 null string, "" (two consecutive double-quote characters). If the
23104 trigger string is found anywhere in the text of the message the filter
23105 is invoked. Placing the trigger text within the tokens defined below
23106 changes where within the text the trigger must be before considering
23107 it a match.
23109 <P>
23110 Trigger Modifying Tokens:
23111 <DL>
23112 <DT>_CHARSET(<VAR>string</VAR>)_</DT>
23113 <DD>This token tells Alpine to invoke the supplied command
23114 if the text is in a character set matching <VAR>string</VAR>
23115 (e.g., ISO-8859-2 or ISO-2022-JP).
23116 </DD>
23119 <DT>_LEADING(<VAR>string</VAR>)_</DT>
23120 <DD>This token tells Alpine to invoke the supplied command
23121 if the enclosed <VAR>string</VAR> is found to be the first
23122 non-whitespace text.
23123 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23124 the space character.
23125 </DD>
23127 <DT>_BEGINNING(<VAR>string</VAR>)_</DT>
23128 <DD>This token tells Alpine to invoke the supplied command
23129 if the enclosed <VAR>string</VAR> is found at the beginning
23130 of any line in the text.
23131 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23132 the space character.
23133 </DD>
23134 </DL>
23136 <P>
23137 The "command" and "arguments" portion is simply
23138 the command line to be invoked if the trigger string is found. Below
23139 are tokens that Alpine will recognize and replace with special values
23140 when the command is actually invoked.
23142 <P>
23143 Command Modifying Tokens:
23145 <DL>
23146 <DT>_TMPFILE_</DT>
23147 <DD>When the command is executed, this token is
23148 replaced with the path and name of the temporary
23149 file containing the text to be filtered. Alpine
23150 expects the filter to replace this data with the
23151 filter's result.
23153 <P>
23154 NOTE: Use of this token implies that the text to
23155 be filtered is not piped into standard input of the
23156 executed command and its standard output is ignored.
23157 Alpine restores the tty modes before invoking the
23158 filter in case the filter interacts with the user
23159 via its own standard input and output.
23160 </DD>
23162 <DT>_RESULTFILE_</DT>
23163 <DD>When the command is executed, this token is
23164 replaced with the path and name of a temporary
23165 file intended to contain a status message from the
23166 filter. Alpine displays this in the message status
23167 field.
23168 </DD>
23170 <DT>_DATAFILE_</DT>
23171 <DD>When the command is executed, this token is
23172 replaced with the path and name of a temporary
23173 file that Alpine creates once per session and deletes
23174 upon exit. The file is intended to be used by the
23175 filter to store state information between instances
23176 of the filter.
23177 </DD>
23179 <DT>_PREPENDKEY_</DT>
23180 <DD>When the command is executed, this token indicates that a random
23181 number will be passed down the input stream before the message text.
23182 This number could be used as a session key. It is sent in this way to
23183 improve security. The number is unique to the current Alpine session
23184 and is only generated once per session.
23185 </DD>
23187 <DT>_SILENT_</DT>
23188 <DD>When the filter is executed, this token tells Alpine not to repaint
23189 the screen while the command is being executed. This can be used with
23190 filters that do not interact with the user, and therefore repainting
23191 the screen is not necessary.
23192 </DD>
23193 </DL>
23195 <P>
23196 The feature
23197 <A HREF="h_config_disable_reset_disp"><!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></A> is related.
23198 <P>
23199 Performance caveat/considerations:
23200 <BR>
23201 Testing for the trigger and invoking the filter doesn't come for free.
23202 There is overhead associated with searching for the trigger string, testing
23203 for the filter's existence and actually piping the text through the filter.
23204 The impact can be reduced if the Trigger Modifying Tokens above are
23205 employed.
23206 <P>
23207 <End of help on this topic>
23208 </BODY>
23209 </HTML>
23210 ====== h_config_sending_filter =====
23211 <HTML>
23212 <HEAD>
23213 <TITLE>OPTION: <!--#echo var="VAR_sending-filters"--></TITLE>
23214 </HEAD>
23215 <BODY>
23216 <H1>OPTION: <!--#echo var="VAR_sending-filters"--></H1>
23218 This option defines a list of text-filtering commands (programs and
23219 scripts) that may be selectively invoked to process a message just before
23220 it is sent. If set, the Composer's ^X (Send) command will allow you to
23221 select which filter (or none) to apply to the message before it is sent.
23222 For security reasons, the full path of the filter program must be
23223 specified.
23225 <P>
23226 Command Modifying Tokens:
23228 <DL>
23229 <DT>_RECIPIENTS_</DT>
23230 <DD>When the command is executed, this token is replaced
23231 with the space delimited list of recipients of the
23232 message being sent.
23233 </DD>
23235 <DT>_TMPFILE_</DT>
23236 <DD>
23237 When the command is executed, this token is
23238 replaced with the path and name of the temporary
23239 file containing the text to be filtered. Alpine
23240 expects the filter to replace this data with the
23241 filter's result.
23243 <P>
23244 NOTE: Use of this token implies that the text to
23245 be filtered is not piped into standard input of the
23246 executed command and its standard output is ignored.
23247 Alpine restores the tty modes before invoking the
23248 filter in case the filter interacts with the user
23249 via its own standard input and output.
23250 </DD>
23252 <DT>_RESULTFILE_</DT>
23253 <DD>When the command is executed, this token is
23254 replaced with the path and name of a temporary
23255 file intended to contain a status message from the
23256 filter. Alpine displays this in the message status
23257 field.
23258 </DD>
23260 <DT>_DATAFILE_</DT>
23261 <DD>When the command is executed, this token is replaced
23262 in the command line with the path and name of a
23263 temporary file that Alpine creates once per session
23264 and deletes upon exit. The file is intended to be
23265 used by the filter to store state information between
23266 instances of the filter.
23267 </DD>
23269 <DT>_PREPENDKEY_</DT>
23270 <DD>When the command is executed, this token indicates
23271 that a random number will be passed down the input
23272 stream before the message text. This number could
23273 be used as a session key. It is sent in this way
23274 to improve security. The number is unique to the
23275 current Alpine session and is only generated once per
23276 session.
23277 </DD>
23279 <DT>_INCLUDEALLHDRS_</DT>
23280 <DD>When the command is executed, this token indicates
23281 that the headers of the message will be passed down the input stream
23282 before the message text.
23283 </DD>
23285 <DT>_MIMETYPE_</DT>
23286 <DD>When the command is executed, this token is replaced in the
23287 command name with a temporary file name used to accept any new MIME
23288 Content-Type information necessitated by the output of the filter.
23289 Upon the filter's exit, if the file contains new MIME type
23290 information, Alpine verifies its format and replaces the outgoing
23291 message's MIME type information with that contained in the file. This
23292 is basically a cheap way of sending something other than Text/Plain.
23293 </DD>
23294 </DL>
23296 <P>
23297 NOTE: Only the body text, which is visible in the Composer, is piped
23298 through this filter. Attachments are not sent to the filter.
23299 <P>
23300 Sending filters are not used if the feature
23301 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set.
23302 <P>
23303 <UL>
23304 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23305 </UL><P>
23306 <End of help on this topic>
23307 </BODY>
23308 </HTML>
23309 ====== h_config_keywords =====
23310 <HTML>
23311 <HEAD>
23312 <TITLE>OPTION: <!--#echo var="VAR_keywords"--></TITLE>
23313 </HEAD>
23314 <BODY>
23315 <H1>OPTION: <!--#echo var="VAR_keywords"--></H1>
23317 You may define your own set of keywords and optionally set them on a
23318 message by message basis.
23319 These are similar to the "Important" flag which the user
23320 may set using the Flag command.
23321 The difference is that the Important flag is always present for each folder.
23322 User-defined keywords are chosen by the user.
23323 You may set up the list of possible keywords here, or you may add keywords
23324 from the Flag Details screen that you
23325 can get to after typing the
23326 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
23327 command.
23328 After the keywords have been defined,
23329 then you use the <A HREF="h_common_flag">Flag command</A>
23330 to set or clear the keywords in each message.
23331 The behavior of the flag command may be modified by using the
23332 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
23333 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
23335 <P>
23336 Keywords may be used when Selecting messages (Select Keyword).
23337 Keywords may also be used in the Patterns of Rules (Filters, Indexcolors, etc).
23338 Filter Rules may be used to set keywords automatically.
23339 Keywords may be displayed as part of the Subject of a message by using
23340 the SUBJKEY or SUBJKEYINIT tokens in the
23341 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
23342 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
23343 option may be used to modify the display of keywords using
23344 SUBJKEY and SUBJKEYINIT slightly.
23345 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
23346 screen by using the KEY or KEYINIT tokens.
23347 It is also possible to color keywords in the index using the
23348 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
23349 Keywords are not supported by all mail servers.
23351 <P>
23352 You may give keywords nicknames if you wish.
23353 If the keyword definition you type in contains a SPACE character, then the
23354 actual value of the keyword is everything after the last SPACE and the
23355 nickname for that keyword is everything before the last SPACE.
23356 For example, suppose you are trying to interoperate with another email program
23357 that uses a particular keyword with an unpleasant name.
23358 Maybe it uses a keyword called
23359 <P>
23360 <CENTER><SAMP>VendorName.SoftwareName.08</SAMP></CENTER>
23361 <P>
23362 but for you that keyword means that the message is work-related.
23363 You could define a keyword to have the value
23364 <P>
23365 <CENTER><SAMP>Work VendorName.SoftwareName.08</SAMP></CENTER>
23366 <P>
23367 and then you would use the name "Work" when dealing with
23368 that keyword in Alpine.
23369 If you defined it as
23370 <P>
23371 <CENTER><SAMP>My Work VendorName.SoftwareName.08</SAMP></CENTER>
23372 <P>
23373 the nickname would be everything before the last SPACE, that is the nickname
23374 would be "My Work".
23375 <P>
23376 Some commonly used keywords begin with dollar signs.
23377 This presents a slight complication, because the dollar sign is normally used
23378 to signify
23379 <A HREF="h_news_config">environment variable expansion</A>
23380 in the Alpine configuration.
23381 In order to specify a keyword that begins with a dollar sign you must
23382 precede the dollar sign with a second dollar sign to escape its special
23383 meaning.
23384 For example, if you want to include the keyword
23385 <P>
23386 <CENTER><SAMP>$Label1</SAMP></CENTER>
23387 <P>
23388 as one of your possible keywords, you must enter the text
23389 <P>
23390 <CENTER><SAMP>$$Label1</SAMP></CENTER>
23391 <P>
23393 instead.
23394 <P>
23395 There are a couple limitations.
23396 First, not all servers support keywords.
23397 Second, some servers (including the IMAP server included with Alpine)
23398 have a per folder limit on the number of keywords that may be defined.
23399 This count commonly includes every keyword you have ever used in the
23400 folder, even if it is no longer being used.
23401 In other words, you can add keywords but you cannot remove them easily.
23402 If you have changed keywords over the life of a folder and find that
23403 you have reached such a limit, one possible solution might be to copy
23404 all of the messages to a newly created folder (using Alpine) and then
23405 delete the original and rename the new folder.
23406 The reason this might work is that only the keywords currently set in
23407 any of the messages will be used in the new folder, hopefully putting you
23408 under the limit.
23410 <P>
23411 <UL>
23412 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23413 </UL><P>
23414 <End of help on this topic>
23415 </BODY>
23416 </HTML>
23417 ====== h_config_alt_addresses =====
23418 <HTML>
23419 <HEAD>
23420 <TITLE>OPTION: <!--#echo var="VAR_alt-addresses"--></TITLE>
23421 </HEAD>
23422 <BODY>
23423 <H1>OPTION: <!--#echo var="VAR_alt-addresses"--></H1>
23425 This option provides a place for you to list alternate email addresses
23426 you may have.
23427 Each address in the list should be the actual email address part of an
23428 address, without the full name field or the angle brackets.
23429 For example:
23431 <P>
23432 <CENTER><SAMP>user@example.com</SAMP></CENTER>
23433 <P>
23435 The matching is case-insensitive, so this would match any of
23436 <SAMP>User@example.com</SAMP>, <SAMP>user@Example.Com</SAMP>, or
23437 <SAMP>USER@EXAMPLE.COM</SAMP> as well.
23439 <P>
23440 If set, the option affects the behavior of the Reply
23441 command and the "+" symbol in the MESSAGE INDEX, which denotes that
23442 a message has been addressed specifically to you.
23444 <P>
23445 In the default INDEX display
23446 the personal name (or email address) of
23447 the person listed in the message's "From:" header
23448 field is usually displayed except when that address is yours or one of your
23449 alternate addresses.
23450 In that case you will usually see the name of
23451 the first person specified in the
23452 message's "To:" header field
23453 with the prefix "To: " prepended.
23455 <P>
23456 With respect to Reply, the reply-to-all option will exclude addresses
23457 listed here.
23459 <P>
23460 The feature
23461 <A HREF="h_config_copy_to_to_from"><!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></A>
23462 is somewhat related to this option.
23464 <P>
23465 In addition to a list of actual addresses,
23466 you may use regular expressions (as used with egrep with the ignore case flag)
23467 to describe the addresses you want to match.
23468 Alpine will somewhat arbitrarily interpret your entry as a regular
23469 expression if it contains any of the characters
23470 *, |, +, ?, {, [, ^, $, or \.
23471 Otherwise, it will be treated literally.
23472 The feature
23473 <a href="h_config_disable_regex"><!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
23474 may be used to turn off regular expression processing regardless of whether or not
23475 special characters appear in the entry.
23477 <P>
23478 A description of how regular expressions work is beyond the
23479 scope of this help text, but some examples follow.
23481 <P>
23482 The entry
23484 <P>
23485 <CENTER><SAMP>.*@example.com</SAMP></CENTER>
23486 <P>
23488 in the <!--#echo var="VAR_alt-addresses"--> list would mean that any
23489 address with a domain name of <SAMP>example.com</SAMP> (such as
23490 <SAMP>fred@example.com</SAMP> or <SAMP>wilma@example.com</SAMP>) will be considered
23491 one of your alternate addresses.
23492 Strictly speaking, the dot in <SAMP>example.com</SAMP> ought to be escaped with
23493 a backslash, as in <SAMP>example\.com</SAMP>, and a dollar sign anchor ought
23494 to come at the end of the expression to prevent a match of <SAMP>example.com.org</SAMP>.
23495 Complicating things further, the dollar sign
23496 is special in the Alpine configuration (it signifies environment variable expansion)
23497 so the dollar sign should be doubled or backslash escaped for Alpine's sake.
23498 Quotes around the whole expression will not escape the dollar sign successfully.
23499 So this example should look like
23501 <P>
23502 <CENTER><SAMP>.*@example\.com$$</SAMP></CENTER>
23503 <P>
23505 <P>
23506 The entry
23508 <P>
23509 <CENTER><SAMP>^fred[0-9]*@example.com$$</SAMP></CENTER>
23510 <P>
23512 would match
23513 <SAMP>fred3@example.com</SAMP> or <SAMP>fred17@example.com</SAMP> as well
23514 as <SAMP>fred@example.com</SAMP>.
23516 <P>
23517 You could match all addresses that look like
23518 <SAMP>fred+stuff@example.com</SAMP> for any value of <SAMP>stuff</SAMP> with the
23519 entry
23521 <P>
23522 <CENTER><SAMP>^fred\+.*@example.com$$</SAMP></CENTER>
23523 <P>
23525 Notice that you have to escape the plus sign with a backslash because plus
23526 is a special character in regular expressions.
23527 If you wanted to match plain <SAMP>fred</SAMP> as well as <SAMP>fred+stuff</SAMP>
23528 the expression
23530 <P>
23531 <CENTER><SAMP>^fred(()|\+.*)@example.com$$</SAMP></CENTER>
23532 <P>
23534 would do it, but it would be easier to just add fred@example.com as a
23535 separate entry.
23537 <P>
23538 One more example, a match of all first-level subdomains, is given by
23540 <P>
23541 <CENTER><SAMP>^fred@[[:alnum:]_-]*\.example\.com$$</SAMP></CENTER>
23542 <P>
23544 <P>
23545 Because the regular expression matching is based on an old library
23546 (<SAMP>hs_regex</SAMP>) the regular expressions might not work exactly as you expect,
23547 but they should be close.
23549 <P>
23550 <UL>
23551 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23552 </UL><P>
23553 <End of help on this topic>
23554 </BODY>
23555 </HTML>
23556 ====== h_config_abook_formats =====
23557 <HTML>
23558 <HEAD>
23559 <TITLE>OPTION: <!--#echo var="VAR_addressbook-formats"--></TITLE>
23560 </HEAD>
23561 <BODY>
23562 <H1>OPTION: <!--#echo var="VAR_addressbook-formats"--></H1>
23564 This option specifies the format that address books are displayed in.
23565 Normally, address books are displayed with the nicknames in the first
23566 column, the fullnames in the second column, and addresses in the third
23567 column. The system figures out reasonable defaults for the widths of
23568 the columns. An address book may be given a different format by
23569 listing special tokens in the order you want them to display. The
23570 possible tokens are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT.
23571 So, for example, to get the default behavior you could list
23573 <P>
23574 <CENTER><!--#echo var="VAR_addressbook-formats"-->=NICKNAME FULLNAME ADDRESS</CENTER>
23576 <P>
23577 (You can also use the token DEFAULT to get the default behavior for
23578 an address book format.)
23580 <P>
23581 The tokens are separated by spaces. "<!--#echo var="VAR_addressbook-formats"-->"
23582 is a list, so if you have more than one address book you may have a
23583 separate format for each by putting its format at the corresponding
23584 location in the "<!--#echo var="VAR_addressbook-formats"-->" list.
23586 <P>
23588 Listed first are the personal address books, then the global address
23589 books. So, if you have two personal address books and one global
23590 address book, you may have up to three formats in the
23591 "<!--#echo var="VAR_addressbook-formats"-->" list. If
23592 "<!--#echo var="VAR_addressbook-formats"-->" doesn't have as many elements as there
23593 are address books, the last element is used repeatedly.
23595 <P>
23597 Each of the tokens may also be optionally followed by parentheses with
23598 either a number or a percentage inside the parentheses. For example,
23599 <SAMP>FULLNAME(13)</SAMP> means to allocate 13 characters of space to
23600 the fullnames column, <SAMP>FULLNAME(20%)</SAMP> means to allocate 20%
23601 of the available space (the screen width minus the space for
23602 inter-column spaces) to the fullnames column, while plain
23603 <SAMP>FULLNAME</SAMP> means the system will attempt to figure out a
23604 reasonable number of columns.
23606 <P>
23607 There are always 2 spaces between every column, so if you use
23608 fixed column widths (like 13) you should remember to take that into
23609 account.
23611 <P>
23612 <UL>
23613 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23614 </UL><P>
23615 <End of help on this topic>
23616 </BODY>
23617 </HTML>
23618 ====== h_config_set_index_format =====
23619 <HTML>
23620 <HEAD>
23621 <TITLE>Set Index Format</TITLE>
23622 </HEAD>
23623 <BODY>
23624 <H1>Set Index Format</H1>
23626 This option is used to customize the content of lines in the
23627 <A HREF="h_mail_index">MESSAGE INDEX screen</A>.
23628 This action works exactly like the regular
23629 "<!--#echo var="VAR_index-format"-->" option in the Setup/Config screen,
23630 except that you can have a folder-specific value for it if you specify it here.
23631 Consult the help for
23632 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
23633 for more information.
23635 <P>
23636 <UL>
23637 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23638 </UL><P>
23639 <End of help on this topic>
23640 </BODY>
23641 </HTML>
23642 ====== h_config_index_format =====
23643 <HTML>
23644 <HEAD>
23645 <TITLE>OPTION: <!--#echo var="VAR_index-format"--></TITLE>
23646 </HEAD>
23647 <BODY>
23648 <H1>OPTION: <!--#echo var="VAR_index-format"--></H1>
23650 This option is used to customize the content of lines in the
23651 <A HREF="h_mail_index">MESSAGE INDEX screen</A>. Each line is intended
23652 to convey some amount of immediately relevant information about each
23653 message in the current folder.
23654 <P>
23656 Alpine provides a pre-defined set of informational fields with
23657 reasonable column widths automatically computed. You can, however,
23658 replace this default set by listing special tokens in the order you
23659 want them displayed.
23660 <P>
23662 The list of available tokens is
23663 <A HREF="h_index_tokens">here</A>.
23664 <P>
23666 Spaces are used to separate listed tokens. Additionally, you can
23667 specify how much of the screen's width the token's associated data
23668 should occupy on the index line by appending to the token a pair of
23669 parentheses enclosing either a number or percentage. For example,
23670 "SUBJECT(13)" means to allocate 13 characters of space to the subject
23671 column, and "SUBJECT(20%)" means to
23672 allocate 20% of the available space
23673 to the subjects column, while plain "SUBJECT" means the system will
23674 attempt to figure out a reasonable amount of space.
23675 <P>
23677 There is always one space between every pair of columns, so if you use fixed
23678 column widths (like 13) you should remember to take that into account.
23679 Several of the fields are virtually fixed-width, so it doesn't make
23680 much sense to specify the width for them. The fields STATUS,
23681 FULLSTATUS, IMAPSTATUS, MSGNO, the DATE fields, SIZE,
23682 and DESCRIPSIZE all fall into that category.
23683 You <EM>may</EM> specify widths for those if you wish, but
23684 you're probably better off letting the system pick those widths. <P>
23686 <P>
23687 The default is equivalent to:
23689 <P>
23690 <CENTER><SAMP>STATUS MSGNO SMARTDATETIME24 FROMORTO(33%) SIZENARROW SUBJKEY(67%)</SAMP></CENTER>
23692 <P>
23693 This means that the four fields without percentages will be allocated
23694 first, and then 33% and 67% of the <EM>remaining</EM> space will go to
23695 the from and subject fields. If one of those two fields is specified
23696 as a percentage and the other is left for the system to choose, then
23697 the percentage is taken as an absolute percentage of the screen, not
23698 of the space remaining after allocating the first four columns. It
23699 doesn't usually make sense to do it that way. If you leave off all
23700 the widths, then the subject and from fields (if both are present) are
23701 allocated space in a 2 to 1 ratio, which is almost exactly the same as
23702 the default.
23704 <P>
23705 What you are most likely to do with this configuration option is to
23706 specify which fields appear at all, which order they appear in, and the
23707 percentage of screen that is used for the from and subject fields if you
23708 don't like the 2 to 1 default.
23710 <P>
23711 If you want to retain the default format that Pine 4.64 had, use
23713 <P>
23714 <CENTER><SAMP><!--#echo var="VAR_index-format"-->=STATUS MSGNO DATE FROMORTO(33%) SIZE SUBJKEY(67%)</SAMP></CENTER>
23715 <P>
23716 <EM>and</EM> set the feature
23717 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>.
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_reply_intro =====
23725 <HTML>
23726 <HEAD>
23727 <TITLE>OPTION: <!--#echo var="VAR_reply-leadin"--></TITLE>
23728 </HEAD>
23729 <BODY>
23730 <H1>OPTION: <!--#echo var="VAR_reply-leadin"--></H1>
23732 This option is used to customize the content of the introduction line
23733 that is included when replying to a message and including the original
23734 message in the reply.
23735 The normal default (what you will get if you delete this variable) looks
23736 something like:
23737 <P>
23738 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
23739 <P>
23740 where the day of the week is only included if it is available in the
23741 original message.
23742 You can replace this default with text of your own.
23743 The text may contain tokens that are replaced with text
23744 that depends on the message you are replying to.
23745 For example, the default is equivalent to:
23746 <P>
23747 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
23748 <P>
23750 Since this variable includes regular text mixed with special tokens
23751 the tokens have to be surrounded by underscore characters.
23752 For example, to use the token "<SAMP>PREFDATE</SAMP>"
23753 you would need to use "<SAMP>_PREFDATE_</SAMP>",
23754 not "<SAMP>PREFDATE</SAMP>".
23755 <P>
23756 The list of available tokens is
23757 <A HREF="h_index_tokens">here</A>.
23759 <P>
23760 By default, the text is all on a single line and is followed by a blank line.
23761 If your "<!--#echo var="VAR_reply-leadin"-->" turns out to be longer
23762 than 80 characters when replying to a particular message, it is shortened.
23763 However, if you use the token
23764 <P>
23765 <CENTER><SAMP>_NEWLINE_</SAMP></CENTER>
23766 <P>
23768 anywhere in the value, no end of line or blank line is appended, and no
23769 shortening is done.
23770 The _NEWLINE_ token may be used to get rid of the blank line following
23771 the text, to add more blank lines, or to form a multi-line
23772 "<!--#echo var="VAR_reply-leadin"-->".
23773 To clarify how _NEWLINE_ works recall that the default value is:
23774 <P>
23775 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
23776 <P>
23778 That is equivalent to
23779 <P>
23780 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE__NEWLINE_</SAMP></CENTER>
23781 <P>
23783 In the former case, two newlines are added automatically because
23784 no _NEWLINE_ token appears in the value of the option (for backwards
23785 compatibility). In the latter case, the newlines are explicit.
23786 If you want to remove the blank line that follows the
23787 "<!--#echo var="VAR_reply-leadin"-->" text use a single
23788 _NEWLINE_ token like
23789 <P>
23790 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE_</SAMP></CENTER>
23791 <P>
23793 Because of the backwards compatibility problem, it is not possible to
23794 remove all of the ends of lines, because then there will be no _NEWLINE_ tokens
23795 and that will cause the automatic adding of two newlines!
23796 If you want, you may embed newlines in the middle of the text, as well,
23797 producing a multi-line "<!--#echo var="VAR_reply-leadin"-->".
23799 <P>
23800 By default, no attempt is made to localize the date.
23801 If you prefer a localized form you may find that one of the tokens
23802 _PREFDATE_ or _PREFDATETIME_ is a satisfactory substitute.
23803 If you want more control one of the many other date tokens, such as _DATEISO_,
23804 might be better.
23806 <P>
23807 For the adventurous, there is a way to conditionally include text based
23808 on whether or not a token would result in specific replacement text.
23809 For example, you could include some text based on whether or not
23810 the _NEWS_ token would result in any newsgroups if it was used.
23811 It's explained in detail
23812 <A HREF="h_reply_token_conditionals">here</A>.
23814 <P>
23815 In the very unlikely event that you want to include a literal token
23816 in the introduction line you must precede it with a backslash character.
23817 For example,
23818 <P>
23819 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
23820 <P>
23821 would produce something like
23822 <P>
23823 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
23824 <P>
23825 It is not possible to have a literal backslash followed by an expanded token.
23826 <P>
23827 <UL>
23828 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23829 </UL><P>
23830 <End of help on this topic>
23831 </BODY>
23832 </HTML>
23833 ====== h_config_remote_abook_history =====
23834 <HTML>
23835 <HEAD>
23836 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-history"--></TITLE>
23837 </HEAD>
23838 <BODY>
23839 <H1>OPTION: <!--#echo var="VAR_remote-abook-history"--></H1>
23841 Sets how many extra copies of
23842 remote address book
23843 data will be kept in each remote address book folder.
23844 The default is three.
23845 These extra copies are simply old versions of the data. Each time a change
23846 is made a new copy of the address book data is appended to the folder. Old
23847 copies are trimmed, if possible, when Alpine exits.
23848 An old copy can be put back into use by
23849 deleting and expunging newer versions of the data from the folder.
23850 Don't delete the first message from the folder. It is a special header
23851 message for the remote address book and it must be there.
23852 This is to prevent regular folders from being used as remote address book
23853 folders and having their data destroyed.
23854 <P>
23855 This option is also used to determine how many extra copies of remote
23856 Alpine configuration files are kept.
23857 <P>
23858 <UL>
23859 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23860 </UL><P>
23861 <End of help on this topic>
23862 </BODY>
23863 </HTML>
23864 ====== h_config_remote_abook_validity =====
23865 <HTML>
23866 <HEAD>
23867 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-validity"--></TITLE>
23868 </HEAD>
23869 <BODY>
23870 <H1>OPTION: <!--#echo var="VAR_remote-abook-validity"--></H1>
23872 Sets the minimum number of minutes that a
23873 remote address book will be considered up to date.
23874 Whenever an entry contained in a remote address book is used,
23875 if more than this many minutes have
23876 passed since the last check the remote server will be queried to see if the
23877 address book has changed.
23878 If it has changed, the local copy is updated.
23879 The default value is five minutes.
23880 The special value of -1 means never check.
23881 The special value of zero means only check when the address book is first
23882 opened.
23883 <P>
23884 No matter what the value, the validity check is always done when the
23885 address book is about to be changed by the user.
23886 The check can be initiated manually by typing <EM>^L</EM> (Ctrl-L)
23887 while in the address book maintenance screen for the remote address book.
23888 <P>
23889 <UL>
23890 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23891 </UL><P>
23892 <End of help on this topic>
23893 </BODY>
23894 </HTML>
23895 ====== h_config_user_input_timeo =====
23896 <HTML>
23897 <HEAD>
23898 <TITLE>OPTION: <!--#echo var="VAR_user-input-timeout"--></TITLE>
23899 </HEAD>
23900 <BODY>
23901 <H1>OPTION: <!--#echo var="VAR_user-input-timeout"--></H1>
23903 If this is set to an integer greater than zero, then this is the number
23904 of <EM>hours</EM> to wait for user input before Alpine times out.
23905 If Alpine is
23906 in the midst of composing a message or is waiting for user response to
23907 a question, then it will not timeout.
23908 However, if Alpine is sitting idle waiting for
23909 the user to tell it what to do next and the user does not give any
23910 input for this many hours, Alpine will exit.
23911 No expunging or moving of read
23912 messages will take place.
23913 It will exit similarly to the way it would exit
23914 if it received a hangup signal.
23915 This may be useful for cleaning up unused Alpine sessions that have been
23916 forgotten by their owners.
23917 The Alpine developers envision system administrators
23918 setting this to a value of several hours (24?) so that it won't surprise
23919 a user who didn't want to be disconnected.
23920 <P>
23921 <UL>
23922 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23923 </UL><P>
23924 <End of help on this topic>
23925 </BODY>
23926 </HTML>
23927 ====== h_config_ssh_open_timeo =====
23928 <HTML>
23929 <HEAD>
23930 <TITLE>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></TITLE>
23931 </HEAD>
23932 <BODY>
23933 <H1>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></H1>
23935 Sets the time in seconds that Alpine will
23936 attempt to open a UNIX secure shell connection.
23937 The default is 15, the minimum non-zero value is 5,
23938 and the maximum is unlimited. If this is set to zero ssh connections
23939 will be completely disabled.
23940 <P>
23941 <UL>
23942 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23943 </UL><P>
23944 <End of help on this topic>
23945 </BODY>
23946 </HTML>
23947 ====== h_config_rsh_open_timeo =====
23948 <HTML>
23949 <HEAD>
23950 <TITLE>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></TITLE>
23951 </HEAD>
23952 <BODY>
23953 <H1>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></H1>
23955 Sets the time in seconds that Alpine will
23956 attempt to open a UNIX remote shell connection.
23957 The default is 15, the minimum non-zero value is 5,
23958 and the maximum is unlimited. If this is set to zero rsh connections
23959 will be completely disabled.
23960 This might be useful if rsh connections will never work in your environment
23961 but are causing delays due to firewalls or some other reason.
23962 <P>
23963 <UL>
23964 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23965 </UL><P>
23966 <End of help on this topic>
23967 </BODY>
23968 </HTML>
23969 ====== h_config_tcp_open_timeo =====
23970 <HTML>
23971 <HEAD>
23972 <TITLE>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></TITLE>
23973 </HEAD>
23974 <BODY>
23975 <H1>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></H1>
23977 Sets the time in seconds that Alpine will
23978 attempt to open a network connection. The default is 30, the minimum is 5,
23979 and the maximum is system defined (typically 75). If a connection has not
23980 completed within this many seconds Alpine will give up and consider it a
23981 failed connection.
23982 <P>
23983 <UL>
23984 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23985 </UL><P>
23986 <End of help on this topic>
23987 </BODY>
23988 </HTML>
23989 ====== h_config_tcp_readwarn_timeo =====
23990 <HTML>
23991 <HEAD>
23992 <TITLE>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></TITLE>
23993 </HEAD>
23994 <BODY>
23995 <H1>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></H1>
23997 Sets the time in seconds that Alpine will
23998 wait for a network read before warning you that things are moving slowly
23999 and possibly giving you the option to break the connection.
24000 The default is 15 seconds. The minimum is 5 seconds and the maximumn is
24001 1000 seconds.
24002 <P>
24003 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24004 <P>
24005 <UL>
24006 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24007 </UL><P>
24008 <End of help on this topic>
24009 </BODY>
24010 </HTML>
24011 ====== h_config_tcp_writewarn_timeo =====
24012 <HTML>
24013 <HEAD>
24014 <TITLE>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></TITLE>
24015 </HEAD>
24016 <BODY>
24017 <H1>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></H1>
24019 Sets the time in seconds that Alpine will
24020 wait for a network write before warning you that things are moving slowly
24021 and possibly giving you the option to break the connection.
24022 The default is 0 which means it is unset. If set to a non-zero value, the
24023 minimum is 5 and the maximum is 1000.
24024 <P>
24025 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24026 <P>
24027 <UL>
24028 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24029 </UL><P>
24030 <End of help on this topic>
24031 </BODY>
24032 </HTML>
24033 ====== h_config_tcp_query_timeo =====
24034 <HTML>
24035 <HEAD>
24036 <TITLE>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></TITLE>
24037 </HEAD>
24038 <BODY>
24039 <H1>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></H1>
24041 When Alpine times out a network read or write it will normally just display
24042 a message saying "Still waiting".
24043 However, if enough time has elapsed since it started waiting it will offer
24044 to let you break the connection.
24045 That amount of time is set by this option, which defaults to 60 seconds,
24046 has a minimum of 5 seconds, and a maximum of 1000 seconds.
24047 <P>
24048 <UL>
24049 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24050 </UL><P>
24051 <End of help on this topic>
24052 </BODY>
24053 </HTML>
24054 ====== h_config_incoming_folders =====
24055 <HTML>
24056 <HEAD>
24057 <TITLE>OPTION: <!--#echo var="VAR_incoming-folders"--></TITLE>
24058 </HEAD>
24059 <BODY>
24060 <H1>OPTION: <!--#echo var="VAR_incoming-folders"--></H1>
24062 This is a list of one or more folders other than <EM>INBOX</EM> that
24063 may receive new messages.
24064 It is related to the
24065 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
24066 feature.
24067 This variable is normally manipulated with the Add, Delete, and Rename
24068 commands in the FOLDER LIST for the Incoming Message Folders collection.
24069 <P>
24070 <UL>
24071 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24072 </UL><P>
24073 <End of help on this topic>
24074 </BODY>
24075 </HTML>
24076 ====== h_config_folder_spec =====
24077 <HTML>
24078 <HEAD>
24079 <TITLE>OPTION: <!--#echo var="VAR_folder-collections"--></TITLE>
24080 </HEAD>
24081 <BODY>
24082 <H1>OPTION: <!--#echo var="VAR_folder-collections"--></H1>
24084 This is a list of one or more collections where saved mail is stored.
24085 The first collection in this list is the default
24086 collection for <EM>Save</EM>s,
24087 including <A HREF="h_config_default_fcc"><!--#echo var="VAR_default-fcc"--></A>.
24088 <P>
24089 This variable is normally manipulated using the Setup/collectionList screen.
24090 <P>
24091 <UL>
24092 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24093 </UL><P>
24094 <End of help on this topic>
24095 </BODY>
24096 </HTML>
24097 ====== h_config_news_spec =====
24098 <HTML>
24099 <HEAD>
24100 <TITLE>OPTION: <!--#echo var="VAR_news-collections"--></TITLE>
24101 </HEAD>
24102 <BODY>
24103 <H1>OPTION: <!--#echo var="VAR_news-collections"--></H1>
24105 This is a list of collections where news folders are located.
24106 <P>
24107 This variable is normally manipulated using the Setup/collectionList screen.
24108 <P>
24109 <UL>
24110 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24111 </UL><P>
24112 <End of help on this topic>
24113 </BODY>
24114 </HTML>
24115 ====== h_config_address_book =====
24116 <HTML>
24117 <HEAD>
24118 <TITLE>OPTION: <!--#echo var="VAR_address-book"--></TITLE>
24119 </HEAD>
24120 <BODY>
24121 <H1>OPTION: <!--#echo var="VAR_address-book"--></H1>
24123 A list of personal address books.
24124 Each entry in the list is an
24125 optional nickname followed by a pathname or file name relative to the home
24126 directory.
24127 The nickname is separated from the rest of the line with whitespace.
24128 Instead of a local pathname or file name, a remote folder name can be given.
24129 This causes the address book to
24130 be a Remote address book.
24131 <P>
24132 Use the Setup/AddressBook screen to modify this variable.
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_glob_addrbook =====
24141 <HTML>
24142 <HEAD>
24143 <TITLE>OPTION: <!--#echo var="VAR_global-address-book"--></TITLE>
24144 </HEAD>
24145 <BODY>
24146 <H1>OPTION: <!--#echo var="VAR_global-address-book"--></H1>
24148 A list of shared address books. Each entry in the list is an
24149 optional nickname followed by a pathname or file name relative to the home
24150 directory.
24151 A SPACE character separates the nickname from the rest of the line.
24152 Instead of a local pathname or file name, a remote folder name can be given.
24153 This causes the address book to
24154 be a Remote address book.
24155 Global address books are
24156 defined to be ReadOnly.
24157 <P>
24158 Use the Setup/AddressBook screen to modify this variable.
24159 <P>
24160 <UL>
24161 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24162 </UL><P>
24163 <End of help on this topic>
24164 </BODY>
24165 </HTML>
24166 ====== h_config_last_vers =====
24167 <HTML>
24168 <HEAD>
24169 <TITLE>OPTION: <!--#echo var="VAR_last-version-used"--></TITLE>
24170 </HEAD>
24171 <BODY>
24172 <H1>OPTION: <!--#echo var="VAR_last-version-used"--></H1>
24174 This is set automatically by Alpine.
24175 It is used to keep track of the last version of Alpine that
24176 was run by the user.
24177 Whenever the version number increases, a new version message is printed out.
24178 This may not be set in the system-wide configuration files.
24179 <P>
24180 <UL>
24181 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24182 </UL><P>
24183 <End of help on this topic>
24184 </BODY>
24185 </HTML>
24186 ====== h_config_printer =====
24187 <HTML>
24188 <HEAD>
24189 <TITLE>OPTION: Printer</TITLE>
24190 </HEAD>
24191 <BODY>
24192 <H1>OPTION: Printer</H1>
24194 Your default printer selection.
24195 <P>
24196 Use the Setup/Printer screen to modify this variable.
24197 <P>
24198 <UL>
24199 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24200 </UL><P>
24201 <End of help on this topic>
24202 </BODY>
24203 </HTML>
24204 ====== h_config_print_cat =====
24205 <HTML>
24206 <HEAD>
24207 <TITLE>OPTION: <!--#echo var="VAR_personal-print-category"--></TITLE>
24208 </HEAD>
24209 <BODY>
24210 <H1>OPTION: <!--#echo var="VAR_personal-print-category"--></H1>
24212 This is an internal Alpine variable.
24213 It will be equal to 1, 2, or 3 depending on whether the default printer is
24214 attached, standard, or a personal print command.
24215 <P>
24216 Use the Setup/Printer screen to modify this variable.
24217 <P>
24218 <UL>
24219 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24220 </UL><P>
24221 <End of help on this topic>
24222 </BODY>
24223 </HTML>
24224 ====== h_config_print_command =====
24225 <HTML>
24226 <HEAD>
24227 <TITLE>OPTION: <!--#echo var="VAR_personal-print-command"--></TITLE>
24228 </HEAD>
24229 <BODY>
24230 <H1>OPTION: <!--#echo var="VAR_personal-print-command"--></H1>
24232 List of personal print commands.
24233 <P>
24234 Use the Setup/Printer screen to modify this variable.
24235 <P>
24236 <UL>
24237 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24238 </UL><P>
24239 <End of help on this topic>
24240 </BODY>
24241 </HTML>
24242 ====== h_config_pat_old =====
24243 <HTML>
24244 <HEAD>
24245 <TITLE>OPTION: Patterns</TITLE>
24246 </HEAD>
24247 <BODY>
24248 <H1>OPTION: Patterns</H1>
24250 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by the
24251 options Patterns-Roles, Patterns-Filters, Patterns-Scores, Patterns-Indexcolors,
24252 and Patterns-Other.
24253 Patterns-Scores and Patterns-Filters have been replaced since then by
24254 Patterns-Scores2 and Patterns-Filters2.
24255 <P>
24256 Use the Setup/Rules screens to modify these variable.
24257 <P>
24258 <UL>
24259 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24260 </UL><P>
24261 <End of help on this topic>
24262 </BODY>
24263 </HTML>
24264 ====== h_config_pat_roles =====
24265 <HTML>
24266 <HEAD>
24267 <TITLE>OPTION: <!--#echo var="VAR_patterns-roles"--></TITLE>
24268 </HEAD>
24269 <BODY>
24270 <H1>OPTION: <!--#echo var="VAR_patterns-roles"--></H1>
24272 List of rules used for roles.
24273 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by this and
24274 other options.
24275 <P>
24276 Use the Setup/Rules/Roles screen to modify this variable.
24277 <P>
24278 <UL>
24279 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24280 </UL><P>
24281 <End of help on this topic>
24282 </BODY>
24283 </HTML>
24284 ====== h_config_pat_filts =====
24285 <HTML>
24286 <HEAD>
24287 <TITLE>OPTION: <!--#echo var="VAR_patterns-filters2"--></TITLE>
24288 </HEAD>
24289 <BODY>
24290 <H1>OPTION: <!--#echo var="VAR_patterns-filters2"--></H1>
24292 List of rules used for filters.
24293 <P>
24294 Use the Setup/Rules/Filters screen to modify this variable.
24295 <P>
24296 <UL>
24297 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24298 </UL><P>
24299 <End of help on this topic>
24300 </BODY>
24301 </HTML>
24302 ====== h_config_pat_scores =====
24303 <HTML>
24304 <HEAD>
24305 <TITLE>OPTION: <!--#echo var="VAR_patterns-scores2"--></TITLE>
24306 </HEAD>
24307 <BODY>
24308 <H1>OPTION: <!--#echo var="VAR_patterns-scores2"--></H1>
24310 List of rules used for scoring.
24311 <P>
24312 Use the Setup/Rules/SetScores screen to modify this variable.
24313 <P>
24314 <UL>
24315 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24316 </UL><P>
24317 <End of help on this topic>
24318 </BODY>
24319 </HTML>
24320 ====== h_config_pat_other =====
24321 <HTML>
24322 <HEAD>
24323 <TITLE>OPTION: <!--#echo var="VAR_patterns-other"--></TITLE>
24324 </HEAD>
24325 <BODY>
24326 <H1>OPTION: <!--#echo var="VAR_patterns-other"--></H1>
24328 List of rules used for miscellaneous configuration.
24329 <P>
24330 Use the Setup/Rules/Other screen to modify this variable.
24331 <P>
24332 <UL>
24333 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24334 </UL><P>
24335 <End of help on this topic>
24336 </BODY>
24337 </HTML>
24338 ====== h_config_pat_incols =====
24339 <HTML>
24340 <HEAD>
24341 <TITLE>OPTION: patterns-indexcolors</TITLE>
24342 </HEAD>
24343 <BODY>
24344 <H1>OPTION: patterns-indexcolors</H1>
24346 List of rules used for coloring lines in the index.
24347 <P>
24348 Use the Setup/Rules/Indexcolor screen to modify this variable.
24349 <P>
24350 <UL>
24351 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24352 </UL><P>
24353 <End of help on this topic>
24354 </BODY>
24355 </HTML>
24356 ====== h_config_pat_srch =====
24357 <HTML>
24358 <HEAD>
24359 <TITLE>OPTION: patterns-search</TITLE>
24360 </HEAD>
24361 <BODY>
24362 <H1>OPTION: patterns-search</H1>
24364 List of rules used only for searching with the Select command in the MESSAGE INDEX.
24365 <P>
24366 Use the Setup/Rules/searCh screen to modify this variable.
24367 <P>
24368 <UL>
24369 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24370 </UL><P>
24371 <End of help on this topic>
24372 </BODY>
24373 </HTML>
24374 ====== h_config_font_name =====
24375 <HTML>
24376 <HEAD>
24377 <TITLE>OPTION: Font Name</TITLE>
24378 </HEAD>
24379 <BODY>
24380 <H1>OPTION: Font Name</H1>
24382 PC-Alpine only.
24383 <P>
24384 Name of normal font.
24385 <P>
24386 Use the pulldown Config menu to modify this variable.
24387 <P>
24388 <UL>
24389 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24390 </UL><P>
24391 <End of help on this topic>
24392 </BODY>
24393 </HTML>
24394 ====== h_config_font_size =====
24395 <HTML>
24396 <HEAD>
24397 <TITLE>OPTION: Font Size</TITLE>
24398 </HEAD>
24399 <BODY>
24400 <H1>OPTION: Font Size</H1>
24402 PC-Alpine only.
24403 <P>
24404 Size of normal font.
24405 <P>
24406 Use the pulldown Config menu to modify this variable.
24407 <P>
24408 <UL>
24409 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24410 </UL><P>
24411 <End of help on this topic>
24412 </BODY>
24413 </HTML>
24414 ====== h_config_font_style =====
24415 <HTML>
24416 <HEAD>
24417 <TITLE>OPTION: Font Style</TITLE>
24418 </HEAD>
24419 <BODY>
24420 <H1>OPTION: Font Style</H1>
24422 PC-Alpine only.
24423 <P>
24424 Style of normal font.
24425 <P>
24426 Use the pulldown Config menu to modify this variable.
24427 <P>
24428 <UL>
24429 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24430 </UL><P>
24431 <End of help on this topic>
24432 </BODY>
24433 </HTML>
24434 ====== h_config_font_char_set =====
24435 <HTML>
24436 <HEAD>
24437 <TITLE>OPTION: Font Character Set</TITLE>
24438 </HEAD>
24439 <BODY>
24440 <H1>OPTION: Font Character Set</H1>
24442 PC-Alpine only.
24443 <P>
24444 Character set of normal font.
24445 <P>
24446 Use the pulldown Config menu to modify this variable.
24447 <P>
24448 <UL>
24449 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24450 </UL><P>
24451 <End of help on this topic>
24452 </BODY>
24453 </HTML>
24454 ====== h_config_print_font_name =====
24455 <HTML>
24456 <HEAD>
24457 <TITLE>OPTION: Print-Font-Name</TITLE>
24458 </HEAD>
24459 <BODY>
24460 <H1>OPTION: Print-Font-Name</H1>
24462 PC-Alpine only.
24463 <P>
24464 Name of printer font.
24465 <P>
24466 Use the pulldown Config menu to modify this variable.
24467 <P>
24468 <UL>
24469 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24470 </UL><P>
24471 <End of help on this topic>
24472 </BODY>
24473 </HTML>
24474 ====== h_config_print_font_size =====
24475 <HTML>
24476 <HEAD>
24477 <TITLE>OPTION: Print-Font-Size</TITLE>
24478 </HEAD>
24479 <BODY>
24480 <H1>OPTION: Print-Font-Size</H1>
24482 PC-Alpine only.
24483 <P>
24484 Size of printer font.
24485 <P>
24486 Use the pulldown Config menu to modify this variable.
24487 <P>
24488 <UL>
24489 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24490 </UL><P>
24491 <End of help on this topic>
24492 </BODY>
24493 </HTML>
24494 ====== h_config_print_font_style =====
24495 <HTML>
24496 <HEAD>
24497 <TITLE>OPTION: Print-Font-Style</TITLE>
24498 </HEAD>
24499 <BODY>
24500 <H1>OPTION: Print-Font-Style</H1>
24502 PC-Alpine only.
24503 <P>
24504 Style of printer font.
24505 <P>
24506 Use the pulldown Config menu to modify this variable.
24507 <P>
24508 <UL>
24509 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24510 </UL><P>
24511 <End of help on this topic>
24512 </BODY>
24513 </HTML>
24514 ====== h_config_print_font_char_set =====
24515 <HTML>
24516 <HEAD>
24517 <TITLE>OPTION: Print-Font-Char-Set</TITLE>
24518 </HEAD>
24519 <BODY>
24520 <H1>OPTION: Print-Font-Char-Set</H1>
24522 PC-Alpine only.
24523 <P>
24524 Character set of printer font.
24525 <P>
24526 Use the pulldown Config menu to modify this variable.
24527 <P>
24528 <UL>
24529 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24530 </UL><P>
24531 <End of help on this topic>
24532 </BODY>
24533 </HTML>
24534 ====== h_config_window_position =====
24535 <HTML>
24536 <HEAD>
24537 <TITLE>OPTION: Window-Position</TITLE>
24538 </HEAD>
24539 <BODY>
24540 <H1>OPTION: Window-Position</H1>
24542 PC-Alpine only.
24543 <P>
24544 Position on the screen of the Alpine window.
24545 <P>
24546 Alpine normally maintains this variable itself, and it is set automatically.
24547 This variable is provided to those who wish to use the same window position
24548 across different machines from the same configuration.
24549 <A HREF="h_config_winpos_in_config"><!--#echo var="FEAT_store-window-position-in-config"--></A>
24550 must also be set for this setting to be used.
24551 <P>
24552 The format for this variable is of the form: <CODE>CxR+X+Y</CODE>, where
24553 C is the number of columns, R is the number of rows, and X and Y specify the
24554 top left corner of the window.
24555 <P>
24556 <UL>
24557 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24558 </UL><P>
24559 <End of help on this topic>
24560 </BODY>
24561 </HTML>
24562 ====== h_config_cursor_style =====
24563 <HTML>
24564 <HEAD>
24565 <TITLE>OPTION: Cursor Style</TITLE>
24566 </HEAD>
24567 <BODY>
24568 <H1>OPTION: Cursor Style</H1>
24570 PC-Alpine only.
24571 <P>
24572 Cursor style.
24573 <P>
24574 Use the pulldown Config menu to modify this variable.
24575 <P>
24576 <UL>
24577 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24578 </UL><P>
24579 <End of help on this topic>
24580 </BODY>
24581 </HTML>
24582 ====== h_config_ldap_servers =====
24583 <HTML>
24584 <HEAD>
24585 <TITLE>OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
24586 </HEAD>
24587 <BODY>
24588 <H1>OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
24590 List of LDAP servers and associated data.
24591 <P>
24592 Use the Setup/Directory screen to modify this variable.
24593 <P>
24594 <UL>
24595 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24596 </UL><P>
24597 <End of help on this topic>
24598 </BODY>
24599 </HTML>
24600 ====== h_config_sendmail_path =====
24601 <HTML>
24602 <HEAD>
24603 <TITLE>OPTION: <!--#echo var="VAR_sendmail-path"--></TITLE>
24604 </HEAD>
24605 <BODY>
24606 <H1>OPTION: <!--#echo var="VAR_sendmail-path"--></H1>
24608 This names the path to an
24609 alternative program, and any necessary arguments, to be used in posting
24610 mail messages. See the Technical notes for more information.
24611 <P>
24612 <UL>
24613 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24614 </UL><P>
24615 <End of help on this topic>
24616 </BODY>
24617 </HTML>
24618 ====== h_config_oper_dir =====
24619 <HTML>
24620 <HEAD>
24621 <TITLE>OPTION: <!--#echo var="VAR_operating-dir"--></TITLE>
24622 </HEAD>
24623 <BODY>
24624 <H1>OPTION: <!--#echo var="VAR_operating-dir"--></H1>
24626 This names the root of the
24627 tree to which you are restricted when reading and writing folders and
24628 files. It is usually used in the system-wide,
24629 <EM>fixed</EM> configuration file.
24630 <P>
24631 <UL>
24632 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24633 </UL><P>
24634 <End of help on this topic>
24635 </BODY>
24636 </HTML>
24637 ====== h_config_rshpath =====
24638 <HTML>
24639 <HEAD>
24640 <TITLE>OPTION: <!--#echo var="VAR_rsh-path"--></TITLE>
24641 </HEAD>
24642 <BODY>
24643 <H1>OPTION: <!--#echo var="VAR_rsh-path"--></H1>
24645 Sets the name of the command used to open a UNIX remote shell
24646 connection. The default is typically <CODE>/usr/ucb/rsh</CODE>.
24647 <P>
24648 <UL>
24649 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24650 </UL><P>
24651 <End of help on this topic>
24652 </BODY>
24653 </HTML>
24654 ====== h_config_rshcmd =====
24655 <HTML>
24656 <HEAD>
24657 <TITLE>OPTION: <!--#echo var="VAR_rsh-command"--></TITLE>
24658 </HEAD>
24659 <BODY>
24660 <H1>OPTION: <!--#echo var="VAR_rsh-command"--></H1>
24662 Sets the format of the command used to
24663 open a UNIX remote shell connection. The default is
24664 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
24665 provided command. The first is for the command's pathname, the second is
24666 for the host to connnect to, the third is for the user to connect as, and
24667 the fourth is for the connection method (typically <CODE>imap</CODE>).
24668 <P>
24669 <UL>
24670 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24671 </UL><P>
24672 <End of help on this topic>
24673 </BODY>
24674 </HTML>
24675 ====== h_config_sshpath =====
24676 <HTML>
24677 <HEAD>
24678 <TITLE>OPTION: <!--#echo var="VAR_ssh-path"--></TITLE>
24679 </HEAD>
24680 <BODY>
24681 <H1>OPTION: <!--#echo var="VAR_ssh-path"--></H1>
24683 Sets the name of the command used to open a UNIX secure shell
24684 connection. The default is typically <CODE>/usr/bin/ssh</CODE>.
24685 <P>
24686 <UL>
24687 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24688 </UL><P>
24689 <End of help on this topic>
24690 </BODY>
24691 </HTML>
24692 ====== h_config_sshcmd =====
24693 <HTML>
24694 <HEAD>
24695 <TITLE>OPTION: <!--#echo var="VAR_ssh-command"--></TITLE>
24696 </HEAD>
24697 <BODY>
24698 <H1>OPTION: <!--#echo var="VAR_ssh-command"--></H1>
24700 Sets the format of the command used to
24701 open a UNIX secure shell connection. The default is
24702 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
24703 provided command. The first is for the command's pathname, the second is
24704 for the host to connnect to, the third is for the user to connect as, and
24705 the fourth is for the connection method (typically <CODE>imap</CODE>).
24706 <P>
24707 <UL>
24708 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24709 </UL><P>
24710 <End of help on this topic>
24711 </BODY>
24712 </HTML>
24713 ====== h_config_new_ver_quell =====
24714 <HTML>
24715 <HEAD>
24716 <TITLE>OPTION: <!--#echo var="VAR_new-version-threshold"--></TITLE>
24717 </HEAD>
24718 <BODY>
24719 <H1>OPTION: <!--#echo var="VAR_new-version-threshold"--></H1>
24721 When a new version of Alpine is run for the first time it offers a
24722 special explanatory screen to the user upon startup. This option
24723 helps control when and if that special screen appears for users that
24724 have previously run Alpine. It takes as its value an Alpine version
24725 number. Alpine versions less than the specified value will supress this
24726 special screen while versions equal to or greater than that specified
24727 will behave normally.
24728 <P>
24729 <UL>
24730 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24731 </UL><P>
24732 <End of help on this topic>
24733 </BODY>
24734 </HTML>
24735 ====== h_config_disable_drivers =====
24736 <HTML>
24737 <HEAD>
24738 <TITLE>OPTION: <!--#echo var="VAR_disable-these-drivers"--></TITLE>
24739 </HEAD>
24740 <BODY>
24741 <H1>OPTION: <!--#echo var="VAR_disable-these-drivers"--></H1>
24743 This variable is a list of mail drivers that will be disabled.
24744 The candidates for disabling are listed below.
24745 There may be more in the future if you compile Alpine with
24746 a newer version of the c-client library.
24747 <P>
24749 <UL>
24750 <LI> mbox
24751 <LI> mbx
24752 <LI> mh
24753 <LI> mmdf
24754 <LI> mtx
24755 <LI> mx
24756 <LI> news
24757 <LI> phile
24758 <LI> tenex
24759 <LI> unix
24760 </UL>
24761 <P>
24763 The <EM>mbox</EM> driver enables the following behavior: if there is a
24764 file called <CODE>mbox</CODE>
24765 in your home directory, and if that file is either empty or in Unix mailbox
24766 format, then every time you open <EM>INBOX</EM> the <EM>mbox</EM> driver
24767 will automatically transfer mail from the system mail spool directory into the
24768 <CODE>mbox</CODE> file and
24769 delete it from the spool directory. If you disable the <EM>mbox</EM> driver,
24770 this will not happen.
24771 <P>
24773 It is not recommended to disable the driver that supports the system default
24774 mailbox format. On most non-SCO systems, that driver is the
24775 <EM>unix</EM> driver.
24776 On most SCO systems, it is the <EM>mmdf</EM> driver.
24777 The system default driver may be
24778 configured to something else on your system; check with your system manager
24779 for additional information.
24780 <P>
24782 It is most likely not very useful for you to disable any of the drivers other
24783 than possibly <EM>mbox</EM>.
24784 You could disable some of the others if you know for
24785 certain that you don't need them but the performance gain in doing so
24786 is very modest.
24787 <P>
24788 <UL>
24789 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24790 </UL><P>
24791 <End of help on this topic>
24792 </BODY>
24793 </HTML>
24794 ====== h_config_disable_auths =====
24795 <HTML>
24796 <HEAD>
24797 <TITLE>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></TITLE>
24798 </HEAD>
24799 <BODY>
24800 <H1>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></H1>
24802 This variable is a list of SASL (Simple Authentication and Security
24803 Layer) authenticators that will be disabled.
24804 SASL is a mechanism for
24805 authenticating to IMAP, POP3, SMTP, and other network servers.
24806 <P>
24808 Alpine matches its list of supported authenticators with the server to
24809 determine the most secure authenticator that is supported by both.
24810 If no matching authenticators are found, Alpine will revert to plaintext
24811 login (or, in the case of SMTP, will be unable to authenticate at all).
24812 <P>
24813 The candidates for disabling can be found <A HREF="X-Alpine-Config:">here</A>.
24814 <P>
24816 Normally, you will not disable any authenticators.
24817 There are two exceptions:
24818 <P>
24819 <OL>
24820 <LI> You use a broken server that advertises an authenticator,
24821 but does not actually implement it.
24822 <LI> You have a Kerberos-capable version of Alpine and the server is
24823 also Kerberos-capable, but you can not obtain Kerberos
24824 credentials on the server machine, thus you desire to disable
24825 GSSAPI (which in turn disables Alpine's Kerberos support).
24826 </OL>
24827 <P>
24828 It is never necessary to disable authenticators, since Alpine will try
24829 other authenticators before giving up.
24830 However, disabling the relevant authenticator avoids annoying error messages.
24831 <P>
24832 <UL>
24833 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24834 </UL><P>
24835 <End of help on this topic>
24836 </BODY>
24837 </HTML>
24838 ====== h_config_abook_metafile =====
24839 <HTML>
24840 <HEAD>
24841 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></TITLE>
24842 </HEAD>
24843 <BODY>
24844 <H1>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></H1>
24846 This is usually set by Alpine and is the name of a file
24847 that contains data about
24848 remote address books and remote configuration files.
24849 <P>
24850 <UL>
24851 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24852 </UL><P>
24853 <End of help on this topic>
24854 </BODY>
24855 </HTML>
24856 ====== h_config_composer_wrap_column =====
24857 <HTML>
24858 <HEAD>
24859 <TITLE>OPTION: <!--#echo var="VAR_composer-wrap-column"--></TITLE>
24860 </HEAD>
24861 <BODY>
24862 <H1>OPTION: <!--#echo var="VAR_composer-wrap-column"--></H1>
24865 This option specifies an aspect of Alpine's Composer. This gives the
24866 maximum width that auto-wrapped lines will have. It's also the maximum
24867 width of lines justified using the <A HREF="h_compose_justify">^J
24868 Justify</A> command. The normal default
24869 is "74". The largest allowed setting is normally "80"
24870 in order to
24871 prevent very long lines from being sent in outgoing mail. When the mail
24872 is actually sent, trailing spaces will be stripped off of each line.
24874 <P>
24875 <UL>
24876 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24877 </UL><P>
24878 <End of help on this topic>
24879 </BODY>
24880 </HTML>
24881 ====== h_config_deadlets =====
24882 <HTML>
24883 <HEAD>
24884 <TITLE>OPTION: <!--#echo var="VAR_dead-letter-files"--></TITLE>
24885 </HEAD>
24886 <BODY>
24887 <H1>OPTION: <!--#echo var="VAR_dead-letter-files"--></H1>
24890 This option affects Alpine's behavior when you cancel a message being
24891 composed. Alpine's usual behavior is to write the canceled message to
24892 a file named
24893 <!--chtml if pinemode="os_windows"-->
24894 "DEADLETR",
24895 <!--chtml else-->
24896 "dead.letter" in your home directory,
24897 <!--chtml endif-->
24898 overwriting any previous message.
24899 <P>
24900 If you set this option to a value higher than one, then that many copies
24901 of dead letter files will be saved.
24902 For example, if you set this option to "3" then you may have
24903 files named
24904 <!--chtml if pinemode="os_windows"-->
24905 "DEADLETR",
24906 "DEADLETR2", and
24907 "DEADLETR3".
24908 <!--chtml else-->
24909 "dead.letter",
24910 "dead.letter2", and
24911 "dead.letter3" in your home directory.
24912 <!--chtml endif-->
24913 In this example, the most recently cancelled message will be in
24914 <!--chtml if pinemode="os_windows"-->
24915 "DEADLETR",
24916 <!--chtml else-->
24917 "dead.letter",
24918 <!--chtml endif-->
24919 and the third most recently cancelled message will be in
24920 <!--chtml if pinemode="os_windows"-->
24921 "DEADLETR3".
24922 <!--chtml else-->
24923 "dead.letter3".
24924 <!--chtml endif-->
24925 The fourth most recently cancelled message will no longer be saved.
24927 <P>
24928 If you set this option to zero, then NO record of canceled messages is
24929 maintained.
24930 <P>
24931 If the feature
24932 <A HREF="h_config_quell_dead_letter"><!--#echo var="FEAT_quell-dead-letter-on-cancel"--></A>
24933 is set, that overrides whatever you set for this option.
24934 If this option had existed at the time, then the Quell feature would not
24935 have been added, but it is still there for backwards compatibility.
24936 So, in order for this option to have the desired effect, make sure the
24937 Quell feature is turned off.
24939 <P>
24940 <UL>
24941 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24942 </UL><P>
24943 <End of help on this topic>
24944 </BODY>
24945 </HTML>
24946 ====== h_config_maxremstream =====
24947 <HTML>
24948 <HEAD>
24949 <TITLE>OPTION: <!--#echo var="VAR_max-remote-connections"--></TITLE>
24950 </HEAD>
24951 <BODY>
24952 <H1>OPTION: <!--#echo var="VAR_max-remote-connections"--></H1>
24954 This option affects low-level behavior of Alpine.
24955 The default value for this option is <EM>3</EM>.
24956 If your INBOX is accessed using the IMAP protocol
24957 from an IMAP server, that connection is kept open throughout the
24958 duration of your Alpine session, independent of the value of this option.
24959 The same is true of any
24960 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
24961 you have defined.
24962 This option controls Alpine's behavior when connecting to remote IMAP folders
24963 other than your INBOX or your <!--#echo var="VAR_stay-open-folders"-->.
24964 It specifies the maximum number of remote IMAP connections (other than
24965 those mentioned above) that Alpine will use for accessing the rest of your
24966 folders.
24967 If you set this option to zero, you will turn off most remote connection
24968 re-use.
24969 It's difficult to understand exactly what this option does, and it is usually
24970 fine to leave it set to its default value.
24971 It is probably more likely that you will be interested in setting the
24972 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A> option
24973 instead of changing the value of this option.
24974 A slightly longer explanation of what is going on with this option
24975 is given in the next paragraphs.
24977 <P>
24978 There are some time costs involved in opening and closing remote IMAP
24979 folders, the main costs being the time you have to wait for the connection
24980 to the server and the time for the folder to open.
24981 Opening a folder may involve not only the time the server takes to do its
24982 processing but time that Alpine uses to do filtering.
24983 These times can vary widely.
24984 They depend on how loaded the server is, how large
24985 the folder being opened is, and how you set up filtering, among other things.
24986 Once Alpine has opened a connection to a particular folder, it will attempt
24987 to keep that connection open in case you use it again.
24988 In order to do this,
24989 Alpine will attempt to use the <!--#echo var="VAR_max-remote-connections"--> (the value of
24990 this option) IMAP connections you have alloted for this purpose.
24991 <P>
24992 For example, suppose the value of this option is set to "2".
24993 If your INBOX is accessed on a remote server using the IMAP protocol, that
24994 doesn't count as one of the remote connections but it is always kept open.
24995 If you then open another IMAP folder, that would be your first
24996 remote connection counted as one of the <!--#echo var="VAR_max-remote-connections"--> connections.
24997 If you open a third folder the second will be left open, in case you
24998 return to it.
24999 You won't be able to tell it has been left open.
25000 It will appear to be closed when you leave the folder but the connection
25001 will remain in the background.
25002 Now suppose you go back to the second folder (the first folder after the
25003 INBOX).
25004 A connection to that folder is still open so you won't have to wait
25005 for the startup time to open it.
25006 Meanwhile, the connection to the third folder will be left behind.
25007 Now, if you open a fourth folder, you will bump into the
25008 <!--#echo var="VAR_max-remote-connections"--> limit, because this will be the third folder other
25009 than INBOX and you have the option set to "2".
25010 The connection that is being used for
25011 the third folder will be re-used for this new fourth folder.
25012 If you go back to the third folder after this, it is no longer already
25013 connected when you get there.
25014 You'll still save some time since Alpine will re-use the connection to the
25015 fourth folder and you have already logged in on that connection,
25016 but the folder will have to be re-opened from scratch.
25017 <P>
25018 If a folder is large and the startup cost is dominated by the time it takes
25019 to open that folder or to run filters on it, then it will pay to make the
25020 value of this option large enough to keep it open.
25021 On the other hand, if you only revisit a handful of folders or if
25022 the folders are small, then it might
25023 make more sense to keep this number small so that the reconnect
25024 time (the time to start up a new connection and authenticate)
25025 is eliminated instead.
25026 <P>
25027 You may also need to consider the impact on the server.
25028 On the surface, a larger number here may cause a larger impact on the
25029 server, since you will have more connections open to the server.
25030 On the other hand, not only will <EM>you</EM> be avoiding the startup costs
25031 associated with reopening a folder, but the <EM>server</EM> will be
25032 avoiding those costs as well.
25033 <P>
25034 When twenty five minutes pass without any active use of an IMAP connection
25035 being saved for possible re-use, that connection will be shut down,
25037 <P>
25038 <UL>
25039 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25040 </UL><P>
25041 <End of help on this topic>
25042 </BODY>
25043 </HTML>
25044 ====== h_config_permlocked =====
25045 <HTML>
25046 <HEAD>
25047 <TITLE>OPTION: <!--#echo var="VAR_stay-open-folders"--></TITLE>
25048 </HEAD>
25049 <BODY>
25050 <H1>OPTION: <!--#echo var="VAR_stay-open-folders"--></H1>
25052 This option affects low-level behavior of Alpine.
25053 There is no default value for this option.
25054 It is related to the options
25055 <A HREF="h_config_preopen_stayopens">"<!--#echo var="FEAT_preopen-stayopen-folders"-->"</A>,
25056 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>,
25057 and <A HREF="h_config_expunge_stayopens">"<!--#echo var="FEAT_offer-expunge-of-stayopen-folders"-->"</A>.
25059 <P>
25060 Note: changes made to this list take effect the next time you open a
25061 folder in the list.
25063 <P>
25064 This is a list of folders that will be permanently kept open once they
25065 are first opened.
25066 The names in this list may be either the nickname of an Incoming folder
25067 or the full technical specification of a folder.
25068 The folders in this list need not be remote IMAP folders, they could usefully
25069 be local folders, as well.
25070 If a folder in the list is a newsgroup or is not accessed either locally
25071 or via IMAP, then the entry will be ignored.
25072 For example, folders accessed via NNTP or POP3 will not be kept open, since
25073 the way that new mail is found with those protocols involves closing and
25074 reopening the connection.
25075 <P>
25076 Once a Stay Open folder has been opened, new-mail checking will continue
25077 to happen on that folder for the rest of the Alpine session.
25078 Your INBOX is always implicitly included in this Stay-Open list and doesn't
25079 need to be added explicitly.
25080 <P>
25081 Another difference that you may notice between a Stay Open folder and a
25082 non-Stay Open folder is which message is selected as the current message
25083 when you enter the folder index.
25084 Normally, the starting position for an incoming folder (which most Stay Open
25085 folders will likely be) is controlled by the
25086 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
25087 However, if a folder is a Stay Open folder, when you re-enter the folder
25088 after the first time the current message will be the same as it was when
25089 you left the folder.
25090 An exception is made if you use the TAB command to get to the folder.
25091 In that case, the message number will be incremented by one from what it
25092 was when you left the folder.
25093 <P>
25094 The above special behavior is thought to be useful.
25095 However, it is special and different from what you might at first expect.
25096 The feature
25097 <A HREF="h_config_use_reg_start_for_stayopen"><!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></A>
25098 may be used to turn off this special treatment.
25099 <P>
25100 If the message that was current when you left the folder no longer exists,
25101 then the regular startup rule will be used instead.
25103 <P>
25104 <UL>
25105 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25106 </UL><P>
25107 <End of help on this topic>
25108 </BODY>
25109 </HTML>
25110 ====== h_config_viewer_overlap =====
25111 <html>
25112 <header>
25113 <title>OPTION: <!--#echo var="VAR_viewer-overlap"--></title>
25114 </header>
25115 <body>
25116 <h1>OPTION: <!--#echo var="VAR_viewer-overlap"--></h1>
25118 This option specifies an aspect of Alpine's Message Viewing screen. When
25119 the space bar is used to page forward in a message, the number of lines
25120 specified by the "<!--#echo var="VAR_viewer-overlap"-->" variable will be repeated from the
25121 bottom of the screen. That is, if this was set to two lines, then the
25122 bottom two lines of the screen would be repeated on the top of the next
25123 screen. The normal default value is "2".<p>
25124 <UL>
25125 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25126 </UL><P>
25127 <End of help on this topic>
25128 </body>
25129 </html>
25130 ====== h_config_scroll_margin =====
25131 <HTML>
25132 <HEAD>
25133 <TITLE>OPTION: <!--#echo var="VAR_scroll-margin"--></TITLE>
25134 </HEAD>
25135 <BODY>
25136 <H1>OPTION: <!--#echo var="VAR_scroll-margin"--></H1>
25138 This option controls when Alpine's line-by-line scrolling occurs.
25139 Typically, when a selected item is at the top or bottom screen edge
25140 and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are struck, the
25141 displayed items are scrolled down or up by a single line.
25143 <P>
25144 This option allows you to tell Alpine the number of lines from the top and
25145 bottom screen edge that line-by-line paging should occcur. For example,
25146 setting this value to one (1) will cause Alpine to scroll the display
25147 vertically when you move to select an item on the display's top or
25148 bottom edge.
25150 <P>
25151 By default, this variable is zero, indicating that scrolling happens
25152 when you move up or down to select an item immediately off the display's
25153 top or bottom edge.
25155 <P>
25156 <UL>
25157 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25158 </UL><P>
25159 <End of help on this topic>
25160 </BODY>
25161 </HTML>
25162 ====== h_config_wordseps =====
25163 <HTML>
25164 <HEAD>
25165 <TITLE>OPTION: <!--#echo var="VAR_composer-word-separators"--></TITLE>
25166 </HEAD>
25167 <BODY>
25168 <H1>OPTION: <!--#echo var="VAR_composer-word-separators"--></H1>
25170 This option affects how a "word" is defined in the composer.
25171 The definition of a word is used when using the Forward Word and Backward
25172 Word commands in the composer, as well as when using the spell checker.
25173 Whitespace is always considered a word separator.
25174 Punctuation (like question marks, periods, commas, and so on) is always
25175 a word separator if it comes at the end of a word.
25176 By default, a punctuation character that is in the middle of a word does
25177 not break up that word as long as the character before and the character
25178 after it are both alphanumeric.
25179 If you add a character to this option it will be considered a
25180 word separator even when it occurs in the middle of an alphanumeric word.
25181 For example, if you want to skip through each part of an address instead
25182 of skipping the whole address at once you might want to include "@"
25183 and "." in this list.
25184 If you want the word-skipper to stop on each part of a UNIX filename you
25185 could add "/" to the list.
25186 The equal sign and dash are other possibilities you might find helpful.
25187 <P>
25188 <UL>
25189 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25190 </UL><P>
25191 <End of help on this topic>
25192 </BODY>
25193 </HTML>
25194 ====== h_config_reply_indent_string =====
25195 <HTML>
25196 <HEAD>
25197 <TITLE>OPTION: <!--#echo var="VAR_reply-indent-string"--></TITLE>
25198 </HEAD>
25199 <BODY>
25200 <H1>OPTION: <!--#echo var="VAR_reply-indent-string"--></H1>
25202 This option specifies an aspect of Alpine's Reply command.
25203 When a message is replied to and the text of the message is included, the
25204 included text usually has the string "> " prepended
25205 to each line indicating it is quoted text.
25206 (In case you haven't seen this before, "string" is a technical term
25207 that means chunk of text.)
25209 <P>
25210 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
25211 in 1999 and its wide-spread adoption since then, you will usually be better off if you
25212 use one of the standard values,
25213 "> " or ">", for this option.
25215 <P>
25216 This option specifies a different value for that string.
25217 If you wish to use a string that begins or ends with a space,
25218 enclose the string in double quotes.
25220 <P>
25221 Besides simple text, the prepended string can be based
25222 on the message being replied to.
25223 The following tokens are substituted for the message's corresponding value:
25225 <DL>
25226 <DT>_FROM_</DT>
25227 <DD>This token gets replaced with the message sender's "username".
25228 If the name is longer than six characters, only the first six characters are
25229 used.
25230 </DD>
25232 <DT>_NICK_</DT>
25233 <DD>This token gets replaced with the nickname of the message sender's
25234 address as found in your addressbook.
25235 If no addressbook entry is found,
25236 Alpine replaces the characters "_NICK_" with nothing.
25237 If the nickname is longer than six characters, only the first six characters are
25238 used.
25239 </DD>
25241 <DT>_INIT_</DT>
25242 <DD>This token gets replaced with the initials of the sender of the message.
25243 </DD>
25245 </DL>
25247 NOTE: When the
25248 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
25249 feature is enabled, you are given the opportunity to edit the string, whether
25250 it is the default or one automatically generated using the above tokens.
25251 <P>
25252 If you change your <!--#echo var="VAR_reply-indent-string"-->
25253 so that it is not equal to the default value of "> ", then
25254 quoted text will not be flowed
25255 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
25256 when you reply.
25257 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
25258 set to the default value.
25259 <P>
25260 <UL>
25261 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25262 </UL><P>
25263 <End of help on this topic>
25264 </BODY>
25265 </HTML>
25266 ====== h_config_quote_replace_string =====
25267 <HTML>
25268 <HEAD>
25269 <TITLE>OPTION: <!--#echo var="VAR_quote-replace-string"--></TITLE>
25270 </HEAD>
25271 <BODY>
25272 <H1>OPTION: <!--#echo var="VAR_quote-replace-string"--></H1>
25274 This option specifies what string to use as a quote when <b>viewing</b> a
25275 message. The standard way of quoting messages when replying is the string
25276 "> " (quote space).
25277 With this variable set, viewing a message will
25278 replace occurrences of
25279 "> " and ">" with the replacement string.
25280 This setting works best when
25281 <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
25282 or the equivalent setting in your correspondents' mail programs
25283 is set to the default
25284 "> ", but it will also work fine with the
25285 <!--#echo var="VAR_reply-indent-string"--> set to ">".
25286 <P>
25287 By default, this setting will only work on messages that are flowed, which is
25288 the default way of sending messages for many mail clients including
25289 Alpine. Enable the feature
25290 <A HREF="h_config_quote_replace_noflow"><!--#echo var="FEAT_quote-replace-nonflowed"--></A>
25291 to also have quote-replacement performed on non-flowed messages.
25292 <P>
25294 Setting this option will replace ">" and
25295 "> " with the new setting. This string may include trailing
25296 spaces. To preserve those spaces enclose the full string in double quotes.
25297 <P>
25298 No padding to separate the text of the message from the quote string is
25299 added. This means that if you do not add trailing spaces to the value of
25300 this variable, text will be displayed right next to the quote string,
25301 which may be undesirable. This can be avoided by adding a new string
25302 separated by a space from your selection of quote string replacement. This
25303 last string will be used for padding. For example, setting this variable to
25304 <br>">" " " has the effect of setting
25305 ">" as the <!--#echo var="VAR_quote-replace-string"-->, with the text padded by
25306 a space from the last quote string to make it more readable.
25307 <P>
25308 One possible setting for this variable could be
25309 " " (four spaces wrapped in quotes), which
25310 would have the effect of indenting each level of quoting four spaces and
25311 removing the ">"'s. Different levels of quoting could be made
25312 more discernible by setting colors for quoted text.
25313 <P>
25314 Replying to or forwarding the viewed message will preserve the original
25315 formatting of the message, so quote-replacement will not be performed on
25316 messages that are being composed.
25317 <P>
25318 <UL>
25319 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25320 </UL><P>
25321 <End of help on this topic>
25322 </BODY>
25323 </HTML>
25324 ====== h_config_empty_hdr_msg =====
25325 <HTML>
25326 <HEAD>
25327 <TITLE>OPTION: <!--#echo var="VAR_empty-header-message"--></TITLE>
25328 </HEAD>
25329 <BODY>
25330 <H1>OPTION: <!--#echo var="VAR_empty-header-message"--></H1>
25332 When sending, if both the To and Cc fields are empty and you
25333 are sending the message to a Bcc,
25334 Alpine will put a special address in the To line. The default value is:
25336 <P>
25337 <CENTER><SAMP>undisclosed-recipients: ;</SAMP></CENTER>
25339 <P>
25340 The reason for this is to avoid embarrassment caused by some Internet
25341 mail transfer software that interprets a "missing"
25342 <SAMP>To:</SAMP> header as an error and replaces it with an
25343 <SAMP>Apparently-to:</SAMP> header that may contain the addresses you
25344 entered on the <SAMP>Bcc:</SAMP> line, defeating the purpose of the
25345 Bcc. You may change the part of this message that comes before the
25346 ": ;" by setting the "<!--#echo var="VAR_empty-header-message"-->"
25347 variable to something else.
25349 <P>
25350 The normal default is "undisclosed-recipients".
25352 <P>
25353 <UL>
25354 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25355 </UL><P>
25356 <End of help on this topic>
25357 </BODY>
25358 </HTML>
25359 ====== h_config_status_msg_delay =====
25360 <HTML>
25361 <HEAD>
25362 <TITLE>OPTION: <!--#echo var="VAR_status-message-delay"--></TITLE>
25363 </HEAD>
25364 <BODY>
25365 <H1>OPTION: <!--#echo var="VAR_status-message-delay"--></H1>
25367 This option has evolved over time, causing the possible values to be
25368 counter-intuitive.
25369 Read carefully before you set this option.
25370 First we explain what the option does, then there is a longer discussion
25371 following that.
25372 <P>
25373 If this is set to zero, the default value, it has <EM>no</EM> effect.
25374 Positive and negative values serve two similar, but different purposes.
25375 <P>
25376 If it is set to a positive number, it causes the cursor to move to the
25377 status line whenever a status message is printed and pause there for this
25378 many seconds.
25379 It will probably only be useful if the
25380 <A HREF="h_config_show_cursor">"<!--#echo var="FEAT_show-cursor"-->"</A> feature is
25381 also turned on.
25382 Setting this option to a positive number can only be used to
25383 <EM>increase</EM> the status message delay.
25384 This may be useful for Braille displays, or other non-traditional displays.
25385 <P>
25386 If it is set to a negative number the interpretation is a bit complicated.
25387 Negative numbers are used to <EM>decrease</EM> the amount of delay Alpine uses to
25388 allow you to read important status messages.
25389 Of course, this may cause you to miss some important messages.
25390 If you see a message flash by but miss what it says you can use the
25391 Journal command from the MAIN MENU to read it.
25392 If you set this option to a negative value, the delay will be
25393 no more than one second less than the absolute value
25394 of the value you set.
25395 So if you set it to -1, the delay will be no more than zero seconds, no
25396 delay at all.
25397 If you set it to -2, the delay will be no more than 1 second.
25398 And so on, -3 is 2 seconds, -4 is 3 seconds, ...
25399 If the delay that Alpine would have used by default is less than this delay,
25400 then the smaller delay set by Alpine will be used.
25401 Setting this option to a negative value can only reduce the amount of
25402 delay, never increase it.
25403 <P>
25404 Here is a more detailed explanation.
25405 Status messages are the messages that show up spontaneously in the
25406 status message line, usually the third line from the bottom of the screen.
25407 By default, Alpine assigns each status message it produces a minimum
25408 display time.
25409 Some status messages have a minimum display time of zero.
25410 You can see an example of such a message by paging up in this help text
25411 until you reach the top of the screen.
25412 If you try to page past the top you will see the message
25413 <P>
25414 <CENTER><SAMP>[Already at start of help text]</SAMP></CENTER>
25415 <P>
25416 in the status line.
25417 If there is another more important use of the status message line this message
25418 might be replaced quickly, or it even might not be shown at all.
25419 However, if there is no reason to get rid of the message, it might stay
25420 there for several seconds while you read the help.
25421 An example where it is replaced immediately happens when you page up in
25422 the help text past the top of the screen, but then type the "WhereIs"
25423 command right after paging up.
25424 The message will disappear immediately without causing a delay (unless you
25425 have set this option to a positive value) to allow you to type input for
25426 the "WhereIs" command.
25427 Since it isn't a very important message, Alpine has set its minimum display
25428 time to zero seconds.
25429 <P>
25430 Other messages have minimum display times of three or more seconds.
25431 These are usually error messages that Alpine thinks you ought to see.
25432 For example, it might be a message about a failed Save or a failed folder open.
25433 It is often the case that this minimum display time won't delay you in
25434 any way because the status message line is not needed for another reason.
25435 However, there are times when Alpine has to delay what it is doing in
25436 order to display a status message for the minimum display time.
25437 This happens when a message is being displayed and Alpine wants to ask
25438 for input from the keyboard.
25439 For example, when you Save a message you use the status message line.
25440 You get a prompt there asking for the name of the folder to save to.
25441 If there is a status message being displayed that has not
25442 yet displayed for its minimum
25443 time Alpine will display that status message surrounded with the characters
25444 > and < to show you that it is delaying.
25445 That might happen, for example, if you tried to save to a folder that
25446 caused an error, then followed that immediately with another Save command.
25447 You might find yourself waiting for a status message like
25448 <P>
25449 <CENTER><SAMP>[>Can't get write access to mailbox, access is readonly<]</SAMP></CENTER>
25450 <P>
25451 to finish displaying for three seconds.
25452 If that is something you find happening to you frequently, you may use
25453 negative values of this option to decrease or eliminate that delay, at
25454 the risk of missing the message.
25455 <P>
25456 <UL>
25457 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25458 </UL><P>
25459 <End of help on this topic>
25460 </BODY>
25461 </HTML>
25462 ====== h_config_active_msg_interval =====
25463 <HTML>
25464 <HEAD>
25465 <TITLE>OPTION: <!--#echo var="VAR_busy-cue-rate"--></TITLE>
25466 </HEAD>
25467 <BODY>
25468 <H1>OPTION: <!--#echo var="VAR_busy-cue-rate"--></H1>
25470 When Alpine is delayed for some reason it usually shows that
25471 something is happening with a small animated display in the status
25472 message line near the bottom of the screen.
25473 This option sets how frequently the characters (for example, a spinning bar)
25474 in the active status message lines are updated.
25475 At most, it can be set to be udpated 20 times per second.
25477 <P>
25478 Setting this value to zero will prevent display of the animations
25479 altogether.
25481 <P>
25482 The option <A HREF="h_config_use_boring_spinner"><!--#echo var="FEAT_busy-cue-spinner-only"--></A>
25483 can be used to remove the randomness from this animated display.
25485 <P>
25486 <UL>
25487 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25488 </UL><P>
25489 <End of help on this topic>
25490 </BODY>
25491 </HTML>
25492 ====== h_config_mailchecknoncurr =====
25493 <HTML>
25494 <HEADER>
25495 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></TITLE>
25496 </HEADER>
25497 <BODY>
25498 <H1>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></H1>
25500 This option is closely related to the
25501 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
25502 option, as well as the
25503 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A> and
25504 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> options.
25505 If the "<!--#echo var="VAR_mail-check-interval"-->" option is set to zero, then automatic
25506 new-mail checking is disabled and this option will have no effect.
25507 <P>
25508 Normally this option is set to zero, which means that the value used will be
25509 the same as the value for the "<!--#echo var="VAR_mail-check-interval"-->".
25510 If you set this option to a value different from zero
25511 (usually larger than the value for "<!--#echo var="VAR_mail-check-interval"-->")
25512 then that is the check interval that will be used
25513 for folders that are not the currently open folder or the INBOX.
25514 You may not even have any folders that are noncurrent and not the INBOX.
25515 If you do, it is likely that they are due to
25516 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
25517 you have configured.
25518 This option also affects the rate of mail checking done on cached
25519 connections to folders you previously had open but are no longer actively
25520 using.
25521 You aren't expected to understand that last sentence, but if you are interested
25522 take a look at
25523 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>
25524 and the related options.
25525 <P>
25526 <UL>
25527 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25528 </UL><P>
25529 <End of help on this topic>
25530 </BODY>
25531 </HTML>
25532 ====== h_config_fifopath =====
25533 <HTML>
25534 <HEADER>
25535 <TITLE>OPTION: NewMail FIFO Path</TITLE>
25536 </HEADER>
25537 <BODY>
25538 <H1>OPTION: NewMail FIFO Path</H1>
25540 This option is only available in UNIX Alpine.
25541 However, there is a very similar feature built in to PC-Alpine.
25542 In PC-Alpine's Config menu at the top of the screen
25543 is an option called "New Mail Window".
25544 <P>
25545 You may have Alpine create a FIFO special file (also called a named pipe) where
25546 it will send a one-line message each time a new message is received in
25547 the current folder, the INBOX, or any open
25548 <A HREF="h_config_permlocked"><!--#echo var="VAR_stay-open-folders"--></A>.
25549 To protect against two different Alpines both writing to the same FIFO, Alpine
25550 will only create the FIFO and write to it if it doesn't already exist.
25551 <P>
25552 A possible way to use this option would be to have a separate window
25553 on your screen running the command
25554 <P>
25555 <CENTER><SAMP>cat filename</SAMP></CENTER>
25556 <P>
25557 where "filename" is the name of the file given for this option.
25558 Because the file won't exist until after you start Alpine, you must <EM>first</EM>
25559 start Alpine and <EM>then</EM> run the "cat" command.
25560 You may be tempted to use "tail -f filename" to view the new
25561 mail log.
25562 However, the common implementations of the tail command will not do what you
25563 are hoping.
25564 <P>
25565 The width of the messages produced for the FIFO may be altered with the
25566 <A HREF="h_config_newmailwidth"><!--#echo var="VAR_newmail-window-width"--></A> option.
25567 <P>
25568 On some systems, fifos may only be created in a local filesystem.
25569 In other words, they may not be in NFS filesystems.
25570 This requirement is not universal.
25571 If the system you are using supports it, it should work.
25572 (It is often the case that your home directory is in an NFS filesystem.
25573 If that is the case, you might try using a file in the "/tmp"
25574 filesystem, which is usually a local filesytem.)
25575 Even when it is possible to use an NFS-mounted filesystem as a place to name
25576 the fifo (for example, your home directory), it will still be the case that
25577 the reader (probably the "cat" command) and the
25578 writer (Alpine) of the fifo must be running on the same system.
25579 <P>
25580 <UL>
25581 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25582 </UL><P>
25583 <End of help on this topic>
25584 </BODY>
25585 </HTML>
25586 ====== h_config_newmailwidth =====
25587 <HTML>
25588 <HEADER>
25589 <TITLE>OPTION: <!--#echo var="VAR_newmail-window-width"--></TITLE>
25590 </HEADER>
25591 <BODY>
25592 <H1>OPTION: <!--#echo var="VAR_newmail-window-width"--></H1>
25594 For UNIX Alpine, this option is only useful if you have turned on the
25595 <A HREF="h_config_fifopath">NewMail FIFO Path</A> option.
25596 That option causes new mail messages to be sent to a fifo file.
25597 Those messages will be 80 characters wide by default.
25598 You can change the width of those messages by changing this option.
25599 For example, if you are reading those messages in another window you might
25600 want to set this width to the width of that other window.
25601 <P>
25602 If you are using PC-Alpine, it has an option in the Config menu to turn
25603 on the "New Mail Window".
25604 This present option also controls the width of that window.
25605 <P>
25606 <UL>
25607 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25608 </UL><P>
25609 <End of help on this topic>
25610 </BODY>
25611 </HTML>
25612 ====== h_config_mailcheck =====
25613 <HTML>
25614 <HEADER>
25615 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval"--></TITLE>
25616 </HEADER>
25617 <BODY>
25618 <H1>OPTION: <!--#echo var="VAR_mail-check-interval"--></H1>
25620 This option specifies, in seconds,
25621 how often Alpine will check for new mail.
25622 If set to zero, new-mail checking is disabled.
25623 (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
25624 current message is the last message of the folder.)
25625 There is a minimum value for this option, normally 15 seconds.
25626 The default value is normally 150 seconds.
25627 The higher you set this option, the easier it is on the server.
25628 <P>
25629 There are some situations where automatic new-mail checking does not work.
25630 See the discussion about new-mail checking in
25631 <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
25632 <P>
25633 The new-mail checking will not happen exactly at the frequency that you specify.
25634 For example, Alpine may elect to defer a non-INBOX mail check if you
25635 are busy typing.
25636 Or, it may check more frequently than you have specified if that is
25637 thought to be necessary to keep the server from closing the connection
25638 to the folder due to inactivity.
25639 If Alpine checks for new mail as a side effect of another command, it will reset
25640 the timer, so that new-mail checking may seem to happen irregularly instead of
25641 every X seconds like clockwork.
25642 <P>
25643 If you are anxious to know about new mail as soon as possible, set the check
25644 interval low, and you'll know about the new mail by approximately
25645 that amount of time after it arrives.
25646 If you aren't so worried about knowing right away, set this option to a
25647 higher value.
25648 That will save the server some processing time and may save you some of
25649 the time you spend waiting for new-mail checks to happen if you are
25650 dealing with a slow server or slow network connection.
25651 <P>
25652 If you suspect that new-mail checking is causing slow downs for you,
25653 you may want to look into the options
25654 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>,
25655 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> and
25656 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A>,
25657 which refine when mail checking is done.
25658 <P>
25659 If the mailbox being checked uses a <A HREF="h_maildrop">Mail Drop</A> then
25660 there is a minimum time
25661 (<A HREF="h_config_maildropcheck">"<!--#echo var="VAR_maildrop-check-minimum"-->"</A>)
25662 between new-mail checks.
25663 Because of this minimum you may notice that new mail does not
25664 appear promptly when you expect it.
25665 The reason for this is to protect the server from over-zealous opening and
25666 closing of the Mail Drop folder, since that is a costly operation.
25667 <P>
25668 <UL>
25669 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25670 </UL><P>
25671 <End of help on this topic>
25672 </BODY>
25673 </HTML>
25674 ====== h_config_quell_checks_comp =====
25675 <HTML>
25676 <HEAD>
25677 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></TITLE>
25678 </HEAD>
25679 <BODY>
25680 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></H1>
25682 This option is closely related to the
25683 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
25684 option, the
25685 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
25686 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A>.
25687 <P>
25688 If this option is set, then the normal new-mail checking that happens
25689 while you are composing will not happen for folders other than your
25690 INBOX (which depends on the setting
25691 of "<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->").
25692 <P>
25693 You might want to set this option if you are experiencing delays while
25694 composing that you think might be related to the speed of the new-mail
25695 checks.
25696 <P>
25697 Even with this option turned on, an occasional new-mail check may be done
25698 in order to keep the server from killing the connection to the folder.
25699 For example, IMAP servers may remove a connection to a folder if there
25700 has been no activity on the connection for 30 minutes or more.
25701 Instead of letting that happen, Alpine will check for new mail before the
25702 30 minutes is up even though you have turned on this feature to quell
25703 those checks.
25704 <P>
25705 Besides new-mail checks, checkpoint operations on the folders
25706 will also be quelled when you set this option.
25707 The purpose of checkpointing is to write the changes to a folder out to
25708 disk periodically in order to avoid losing those changes when system or
25709 software problems occur.
25710 New-mail checking and checkpointing while you are not composing are not
25711 affected by this option.
25713 <P>
25714 <End of help on this topic>
25715 </BODY>
25716 </HTML>
25717 ====== h_config_quell_checks_comp_inbox =====
25718 <HTML>
25719 <HEAD>
25720 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></TITLE>
25721 </HEAD>
25722 <BODY>
25723 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></H1>
25725 This option is closely related to the
25726 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
25727 option, the
25728 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
25729 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>.
25730 <P>
25731 If this option is set, then the normal new-mail checking that happens
25732 while you are composing will not happen for your INBOX.
25733 Checking of other folders is controlled in a similar way with the
25734 "<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->" option.
25735 <P>
25736 You might want to set this option if you are experiencing delays while
25737 composing that you think might be related to the speed of the new-mail
25738 checks.
25739 <P>
25740 Even with this option turned on, an occasional new-mail check may be done
25741 in order to keep the server from killing the connection to the folder.
25742 For example, IMAP servers may remove a connection to a folder if there
25743 has been no activity on the connection for 30 minutes or more.
25744 Instead of letting that happen, Alpine will check for new mail before the
25745 30 minutes is up even though you have turned on this feature to quell
25746 those checks.
25747 <P>
25748 Besides new-mail checks, checkpoint operations on the INBOX
25749 will also be quelled when you set this option.
25750 The purpose of checkpointing is to write the changes to a folder out to
25751 disk periodically in order to avoid losing those changes when system or
25752 software problems occur.
25753 New-mail checking and checkpointing while you are not composing are not
25754 affected by this option.
25755 <P>
25756 <End of help on this topic>
25757 </BODY>
25758 </HTML>
25759 ====== h_config_maildropcheck =====
25760 <HTML>
25761 <HEADER>
25762 <TITLE>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></TITLE>
25763 </HEADER>
25764 <BODY>
25765 <H1>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></H1>
25767 New-mail checking for a
25768 <A HREF="h_maildrop">Mail Drop</A> is a little different from new
25769 mail checking for a regular folder.
25770 One of the differences is that the connection to the Mail Drop is not
25771 kept open and so the cost of checking
25772 (delay for you and additional load for the server) may be significant.
25773 Because of this additional cost we set a minimum time that
25774 must pass between checks.
25775 This minimum only applies to the automatic checking done by Alpine.
25776 If you force a check by typing ^L (Ctrl-L) or by typing the Next command when you are
25777 at the end of a folder index, then the check is done right away.
25778 <P>
25779 This option specifies, in seconds, the <EM>minimum</EM> time between Mail Drop
25780 new-mail checks.
25781 You may want to set this minimum high in order to avoid experiencing some
25782 of the delays associated with the checks.
25783 Note that the time between checks is still controlled by the regular
25784 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option.
25785 When Alpine is about to do an automatic check for new mail (because
25786 the <!--#echo var="VAR_mail-check-interval"--> has expired) then if the time since the last
25787 new-mail check
25788 of any open Mail Drops has been greater than the <!--#echo var="VAR_maildrop-check-minimum"-->,
25789 the Mail Drop is checked for new mail as well.
25790 Therefore, it is only useful to set this option to a value that is higher
25791 than the <!--#echo var="VAR_mail-check-interval"-->.
25792 <P>
25793 If this option is set to zero, automatic Mail Drop new-mail
25794 checking is disabled.
25795 There is a minimum value, normally 60 seconds.
25796 The default value is normally 60 seconds as well.
25797 This applies to the INBOX and to the currently open folder if that is
25798 different from the INBOX.
25800 <P>
25801 <UL>
25802 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25803 </UL><P>
25804 <End of help on this topic>
25805 </BODY>
25806 </HTML>
25807 ====== h_config_nntprange =====
25808 <HTML>
25809 <HEADER>
25810 <TITLE>OPTION: <!--#echo var="VAR_nntp-range"--></TITLE>
25811 </HEADER>
25812 <BODY>
25813 <H1>OPTION: <!--#echo var="VAR_nntp-range"--></H1>
25815 This option applies only to newsgroups accessed using the NNTP protocol.
25816 It does not, for example,
25817 apply to newsgroups accessed using an IMAP-to-NNTP proxy.
25819 <P>
25820 When you open a connection to a News server using the NNTP protocol, you
25821 normally have access to all of the articles in each newsgroup.
25822 If a server keeps a large backlog of messages it may speed performance
25823 some to restrict attention to only the newer messages in a group.
25824 This option allows you to set how many article numbers should be checked
25825 when opening a newsgroup.
25826 You can think of "<!--#echo var="VAR_nntp-range"-->" as specifying the maximum number
25827 of messages you ever want to see.
25828 For example, if you only ever wanted to look at the last 500 messages in each
25829 newsgroup you could set this option to 500.
25830 In actuality, it isn't quite that.
25831 Instead, for performance reasons, it specifies the range of article
25832 numbers to be checked, beginning
25833 with the highest numbered article and going backwards from there.
25834 If there are messages that have been canceled or deleted
25835 their article numbers are still counted as part of the range.
25836 <P>
25837 So, more precisely, setting the "<!--#echo var="VAR_nntp-range"-->" will cause article
25838 numbers
25839 <P><CENTER>last_article_number - <!--#echo var="VAR_nntp-range"--> + 1 through last_article_number</CENTER>
25840 <P>
25841 to be considered when reading a newsgroup.
25842 The number of messages that show up in your index will be less than or equal
25843 to the value of "<!--#echo var="VAR_nntp-range"-->".
25845 <P>
25846 The purpose of this option is simply to speed up access when reading news.
25847 The speedup comes because Alpine can ignore all but the last <!--#echo var="VAR_nntp-range"--> article
25848 numbers, and can avoid downloading any information about the ignored articles.
25849 There is a cost you pay for this speedup.
25850 That cost is that there is no way for you to see those ignored articles.
25851 The articles that come before the range you specify are invisible to you and
25852 to Alpine, as if they did not exist at all.
25853 There is no way to see those messages using, for example, an unexclude command
25854 or something similar.
25855 The only way to see those articles is to set this option high enough (or
25856 set it to zero) and then to reopen the newsgroup.
25858 <P>
25859 If this option is set to 0 (which is also the default),
25860 then the range is unlimited.
25861 This option applies globally to all NNTP servers and to all newsgroups
25862 on those servers.
25863 There is no way to set different values for different newsgroups or servers.
25865 <P>
25866 <UL>
25867 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25868 </UL><P>
25869 <End of help on this topic>
25870 </BODY>
25871 </HTML>
25872 ====== h_config_news_active =====
25873 <html>
25874 <header>
25875 <title>OPTION: <!--#echo var="VAR_news-active-file-path"--></title>
25876 </header>
25877 <body>
25878 <h1>OPTION: <!--#echo var="VAR_news-active-file-path"--></h1>
25880 This option tells Alpine where to look for the "active file" for newsgroups
25881 when accessing news locally, rather than via NNTP. The default path is
25882 usually "/usr/lib/news/active".<p>
25883 <UL>
25884 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25885 </UL><P>
25886 <End of help on this topic>
25887 </body>
25888 </html>
25889 ====== h_config_news_spool =====
25890 <html>
25891 <header>
25892 <title>OPTION: <!--#echo var="VAR_news-spool-directory"--></title>
25893 </header>
25894 <body>
25895 <h1>OPTION: <!--#echo var="VAR_news-spool-directory"--></h1>
25897 This option tells Alpine where to look for the "news spool" for newsgroups
25898 when accessing news locally, rather than via NNTP. The default path is
25899 usually "/var/spool/news".<p>
25900 <UL>
25901 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25902 </UL><P>
25903 <End of help on this topic>
25904 </body>
25905 </html>
25906 ====== h_config_image_viewer =====
25907 <html>
25908 <header>
25909 <title>OPTION: <!--#echo var="VAR_image-viewer"--></title>
25910 </header>
25911 <body>
25912 <h1>OPTION: <!--#echo var="VAR_image-viewer"--></h1>
25913 <body>
25914 This option specifies the program Alpine should call to view MIME
25915 attachments of type IMAGE (e.g. GIF or TIFF). The Image Viewer setting is
25916 no longer needed, but remains for backward compatibility. The more
25917 general method for associating external printing and viewing programs with
25918 specific MIME data types is to use the system's (or your personal)
25919 "mailcap" configuration file.<p>
25920 <UL>
25921 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25922 </UL><P>
25923 <End of help on this topic>
25924 </body>
25925 </html>
25926 ====== h_config_domain_name =====
25927 <HTML>
25928 <HEAD>
25929 <TITLE>OPTION: <!--#echo var="VAR_use-only-domain-name"--></TITLE>
25930 </HEAD>
25931 <BODY>
25932 <H1>OPTION: <!--#echo var="VAR_use-only-domain-name"--></H1>
25934 This option is used only if the
25935 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> option is <B>not</B>
25936 set. If set to "Yes" (and <!--#echo var="VAR_user-domain"--> is not used), then Alpine
25937 strips the hostname from your return ("From") address and when
25938 completing unqualified addresses that you enter into the composer.
25939 <P>
25940 If you set this, see also the <A HREF="h_config_quell_local_lookup">
25941 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
25944 <!--chtml if pinemode="os_windows"-->
25945 <P>This option is not applicable to PC-Alpine.
25946 <!--chtml else-->
25947 <P>
25948 <!--chtml endif-->
25949 <UL>
25950 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25951 </UL>
25952 <P>
25953 <End of help on this topic>
25954 </BODY>
25955 </HTML>
25956 ====== h_config_prune_date =====
25957 <HTML>
25958 <HEAD>
25959 <TITLE>OPTION: Last-Time-Prune Question</TITLE>
25960 </HEAD>
25961 <BODY>
25962 <H1>OPTION: Last-Time-Prune Question</H1>
25964 This value records the last time you were asked about deleting old
25965 sent-mail.
25966 It is set automatically by Alpine at the beginning of each month.
25967 In the past, if you wished to suppress the monthly sent-mail
25968 pruning feature, you could set this to a date in the future.
25969 This value is relative to the year 1900, so
25970 to set this, for example, to October 2005, use 105.10.
25971 <P>
25972 You can still do that if you wish, or you can use the
25973 <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option, which is probably
25974 a little more convenient to use.
25975 <P>
25976 <UL>
25977 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25978 </UL><P>
25979 <End of help on this topic>
25980 </BODY>
25981 </HTML>
25982 ====== h_config_goto_default =====
25983 <HTML>
25984 <HEAD>
25985 <TITLE>OPTION: <!--#echo var="VAR_goto-default-rule"--></TITLE>
25986 </HEAD>
25987 <BODY>
25988 <H1>OPTION: <!--#echo var="VAR_goto-default-rule"--></H1>
25990 This value affects Alpine's behavior when you use the Goto command.
25991 Alpine's usual behavior has two parts. If your current folder is
25992 "Inbox", Alpine will offer the last open folder as the
25993 default. If the current folder is other than "Inbox",
25994 "Inbox" is offered as the default.
25996 <P>
25997 The available options include:
25999 <DL>
26001 <DT>folder-in-first-collection</DT>
26003 <DD> Alpine will offer the most recently visited folder in the default
26004 collection found in the "Collection List" screen as the default.
26005 </DD>
26007 <DT> inbox-or-folder-in-first-collection</DT>
26009 <DD> If the current folder is "Inbox",
26010 Alpine will offer the most recently visited folder in the
26011 default collection found in the "Collection List" screen.
26012 If the current folder is other than "Inbox",
26013 "Inbox" is offered as the default.
26014 </DD>
26016 <DT> inbox-or-folder-in-recent-collection</DT>
26018 <DD> This is Alpine's default behavior.
26019 If the current folder is "Inbox",
26020 Alpine will offer the last open
26021 folder as the default.
26022 If the current folder is other than "Inbox",
26023 "Inbox" is offered as the default.
26024 </DD>
26026 <DT> first-collection-with-inbox-default</DT>
26028 <DD> Instead of offering the most recently visited folder in the default
26029 collection, the default collection is offered but with "Inbox" as
26030 the default folder.
26031 If you type in a folder name it will be in the default collection.
26032 If you simply accept the default, however, your "Inbox" will be opened.
26033 </DD>
26035 <DT> most-recent-folder</DT>
26037 <DD> The last accepted value simply causes the most recently opened
26038 folder to be offered as the default regardless of the currently opened
26039 folder.
26040 </DD>
26041 </DL>
26043 <P>
26044 NOTE: The default while a newsgroup is open remains the same; the last
26045 open newsgroup.
26047 <P>
26048 <UL>
26049 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26050 </UL><P>
26051 <End of help on this topic>
26052 </BODY>
26053 </HTML>
26054 ====== h_config_thread_lastreply_char =====
26055 <HTML>
26056 <HEAD>
26057 <TITLE>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></TITLE>
26058 </HEAD>
26059 <BODY>
26060 <H1>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></H1>
26062 The <!--#echo var="VAR_threading-lastreply-character"--> option has a small effect on the MESSAGE
26063 INDEX display when using a
26064 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
26065 of "show-thread-structure", "mutt-like", or
26066 "show-structure-in-from"; and sorting by Threads or OrderedSubject.
26067 The value of this option is a single character.
26068 This character is used instead of the vertical line character when there are
26069 no more replies directly to the parent of the current message.
26070 It can be used to "round-off" the bottom of the vertical line
26071 by setting it to a character such as a backslash (\) or
26072 a backquote (`).
26073 The default value of this option is the backslash character (\).
26074 This option may not be set to the Empty Value.
26075 In that case, the default will be used instead.
26077 <P>
26078 <UL>
26079 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26080 </UL><P>
26081 <End of help on this topic>
26082 </BODY>
26083 </HTML>
26084 ====== h_config_thread_indicator_char =====
26085 <HTML>
26086 <HEAD>
26087 <TITLE>OPTION: <!--#echo var="VAR_threading-indicator-character"--></TITLE>
26088 </HEAD>
26089 <BODY>
26090 <H1>OPTION: <!--#echo var="VAR_threading-indicator-character"--></H1>
26092 The <!--#echo var="VAR_threading-indicator-character"--> option has a small effect on the MESSAGE
26093 INDEX display when using a
26094 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26095 than "none" and sorting by Threads or OrderedSubject.
26096 The value of this option is a single character.
26097 This character is used to indicate that part of a thread (a conversation) is
26098 hidden beneath a message.
26099 The message could be expanded
26100 if desired with the "/" Collapse/Expand command.
26101 By default, the value of this option is the greater than sign (>).
26102 <P>
26103 If this option is set to the Empty Value, then the column (and the following
26104 blank column) will be deleted from the display.
26106 <P>
26107 This option is closely related to the
26108 <A HREF="h_config_thread_exp_char"><!--#echo var="VAR_threading-expanded-character"--></A> option.
26109 Another similar option that affects the thread display is the
26110 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26112 <P>
26113 <UL>
26114 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26115 </UL><P>
26116 <End of help on this topic>
26117 </BODY>
26118 </HTML>
26119 ====== h_config_thread_exp_char =====
26120 <HTML>
26121 <HEAD>
26122 <TITLE>OPTION: <!--#echo var="VAR_threading-expanded-character"--></TITLE>
26123 </HEAD>
26124 <BODY>
26125 <H1>OPTION: <!--#echo var="VAR_threading-expanded-character"--></H1>
26127 The <!--#echo var="VAR_threading-expanded-character"--> option has a small effect on the MESSAGE
26128 INDEX display when using a
26129 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26130 than "none".
26131 The value of this option is a single character.
26132 This character is used to indicate that part of a thread has been expanded
26133 and could be collapsed if desired with
26134 the "/" Collapse/Expand command.
26135 By default, the value of this option is a dot (.).
26136 <P>
26137 If this option is set to the Empty Value, then the column (and the following
26138 blank column) will be deleted from the display.
26140 <P>
26141 This option is closely related to the
26142 <A HREF="h_config_thread_indicator_char"><!--#echo var="VAR_threading-indicator-character"--></A> option.
26143 Another similar option that affects the thread display is the
26144 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26146 <P>
26147 <UL>
26148 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26149 </UL><P>
26150 <End of help on this topic>
26151 </BODY>
26152 </HTML>
26153 ====== h_config_thread_index_style =====
26154 <HTML>
26155 <HEAD>
26156 <TITLE>OPTION: <!--#echo var="VAR_threading-index-style"--></TITLE>
26157 </HEAD>
26158 <BODY>
26159 <H1>OPTION: <!--#echo var="VAR_threading-index-style"--></H1>
26161 When a folder is sorted by Threads or OrderedSubject,
26162 this option will affect the INDEX displays.
26163 <P>
26165 The possible values for this option are:
26167 <DL>
26168 <DT>regular-index-with-expanded-threads</DT>
26169 <DD>This is the default display.
26170 If the configuration option
26171 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26172 is set to something other than "none", then this setting
26173 will cause Alpine to start off with a MESSAGE INDEX with all of
26174 the threads expanded.
26175 That is, each message will have a line in the MESSAGE INDEX display.
26176 The Collapse/Expand command (/) may be used to manually collapse or
26177 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26178 <P>
26179 This setting affects the display when the folder is first threaded.
26180 The collapsed state may also be re-initialized by re-sorting the folder manually
26181 using the SortIndex command ($).
26182 After re-sorting the threads will once again all be expanded, even if you
26183 have previously collapsed some of them.
26184 <P>
26185 If "<!--#echo var="VAR_threading-display-style"-->" is set to "none", then
26186 the display will be the regular default Alpine MESSAGE INDEX, but sorted
26187 in a different order.
26188 </DD>
26190 <DT>regular-index-with-collapsed-threads</DT>
26191 <DD>If the configuration option
26192 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26193 is set to something other than "none", then this setting
26194 will cause Alpine to start out with all of the threads collapsed instead of
26195 starting out with all of the threads expanded.
26196 The Collapse/Expand command (/) may be used to manually collapse or
26197 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26198 <P>
26199 This setting affects the display when the folder is first threaded.
26200 The collapsed state may also be re-initialized by re-sorting the folder manually
26201 using the SortIndex command ($).
26202 After re-sorting the threads will once again all be collapsed, even if you
26203 have previously expanded some of them.
26204 </DD>
26206 <DT>separate-index-screen-always</DT>
26207 <DD>With this setting and the next, you will see an index of threads
26208 instead of an
26209 index of messages, provided you have sorted by Threads or OrderedSubject.
26210 <P>
26211 The THREAD INDEX contains a '*' in the first column if any message in the thread
26212 is marked Important.
26213 If not, it contains a '+' if any message in the thread is to you.
26214 The second column is blank. The third column contains a 'D' if all of the
26215 messages in the thread are deleted.
26216 Otherwise, it contains an 'N' if any of the messages in the thread are New.
26217 <P>
26218 When you view a particular thread from the THREAD INDEX you will be
26219 in the MESSAGE INDEX display
26220 but the index will only contain messages from the thread you are viewing.
26221 </DD>
26223 <DT>separate-index-screen-except-for-single-messages</DT>
26224 <DD>This is very similar to the option above.
26225 When you are in the THREAD INDEX, one of the available commands
26226 is "ViewThd".
26227 With the setting "separate-index-screen-always" (the option above)
26228 when you view a particular thread you will be in the
26229 MESSAGE INDEX display and the index will only contain messages from
26230 the thread you are viewing.
26231 If the thread you are viewing consists of a single message, the MESSAGE INDEX
26232 will be an index with only one message in it.
26233 If you use this "separate-index-screen-except-for-single-messages"
26234 setting instead, then that index that contains a single message
26235 will be skipped and you will go directly from the THREAD INDEX into the
26236 MESSAGE TEXT screen.
26237 </DD>
26239 </DL>
26241 <P>
26242 <UL>
26243 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26244 </UL><P>
26245 <End of help on this topic>
26246 </BODY>
26247 </HTML>
26248 ====== h_config_thread_disp_style =====
26249 <HTML>
26250 <HEAD>
26251 <TITLE>OPTION: <!--#echo var="VAR_threading-display-style"--></TITLE>
26252 </HEAD>
26253 <BODY>
26254 <H1>OPTION: <!--#echo var="VAR_threading-display-style"--></H1>
26256 When a folder is sorted by Threads or OrderedSubject,
26257 this option will affect the MESSAGE INDEX display.
26258 By default, Alpine will display the MESSAGE INDEX in the
26259 "show-thread-structure" style if a folder is sorted
26260 by Threads or OrderedSubject.
26261 <P>
26263 The possible values for this option are:
26265 <DL>
26266 <DT>none</DT>
26267 <DD>Regular index display.
26268 The same index line as would be displayed without threading is used.
26269 The only difference will be in the order of the messages.
26270 </DD>
26272 <DT>show-thread-structure</DT>
26273 <DD>Threaded Subjects will be indented and vertical bars and horizontal
26274 lines will be added to make it easier to see the relationships among
26275 the messages in a thread (a conversation).
26276 </DD>
26278 <DT>mutt-like</DT>
26279 <DD>This is the same as the option above except that the Subject
26280 is suppressed (is blank) if it matches the previous Subject in the thread.
26281 The name comes from the email client <A HREF="http://www.mutt.org/">Mutt</A>.
26282 Here is an example of what a mutt-like index might look like.
26283 In this example, the first column represents the message number, the
26284 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
26285 is set to "regular-index-with-expanded-threads", and the
26286 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A>
26287 is set to a backslash:
26288 <PRE>
26289 1 Some topic
26290 2 . Subject original message in thread
26291 3 |-> reply to 2
26292 4 . |-> another reply to 2
26293 5 . | \-> reply to 4
26294 6 . | \-> reply to 5
26295 7 | \-> reply to 6
26296 8 |-> another reply to 2
26297 9 . |->New subject another reply to 2 but with a New subject
26298 10 | |-> reply to 9
26299 11 | \-> another reply to 9
26300 12 | \-> reply to 11
26301 13 \-> final reply to 2
26302 14 Next topic
26303 </PRE>
26304 </DD>
26306 <DT>indent-subject-1</DT>
26307 <DD>Threaded Subjects will be indented one space per level of the conversation.
26308 The bars and lines that show up in the show-thread-structure display will
26309 not be there with this style.
26310 </DD>
26312 <DT>indent-subject-2</DT>
26313 <DD>Same as above but indent two spaces per level instead of one space.
26314 </DD>
26316 <DT>indent-from-1</DT>
26317 <DD>Similar to indent-subject-1, except that instead of indenting the
26318 Subject field one space the From field of a thread will be indented one
26319 space per level of the conversation.
26320 </DD>
26322 <DT>indent-from-2</DT>
26323 <DD>Same as above but indent two spaces per level instead of one space.
26324 </DD>
26326 <DT>show-structure-in-from</DT>
26327 <DD>The structure of the thread is illustrated with indenting, vertical bars,
26328 and horizontal lines just like with the show-thread-structure option, but
26329 the From field is used to show the relationships instead of the Subject field.
26330 </DD>
26332 </DL>
26334 <P>
26335 <UL>
26336 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26337 </UL><P>
26338 <End of help on this topic>
26339 </BODY>
26340 </HTML>
26341 ====== h_config_pruning_rule =====
26342 <HTML>
26343 <HEAD>
26344 <TITLE>OPTION: <!--#echo var="VAR_pruning-rule"--></TITLE>
26345 </HEAD>
26346 <BODY>
26347 <H1>OPTION: <!--#echo var="VAR_pruning-rule"--></H1>
26349 By default, Alpine will ask at the beginning of each month whether or not
26350 you want to rename your sent-mail folder to a name like sent-mail-month-year.
26351 (See the feature <A HREF="h_config_prune_uses_iso"><!--#echo var="FEAT_prune-uses-yyyy-mm"--></A> to
26352 change the format of the folder to sent-mail-yyyy-mm.)
26353 It will also ask whether you would like to delete old sent-mail folders.
26354 If you have defined
26355 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>
26356 or
26357 <A HREF="h_config_pruned_folders"><!--#echo var="VAR_pruned-folders"--></A>
26358 Alpine will also ask about pruning those folders.
26359 <P>
26361 With this option you may provide an automatic answer to these questions.
26362 The default value is to ask you what you'd like to do.
26363 <P>
26365 The six possible values for this option are:
26367 <DL>
26368 <DT>ask about rename, ask about deleting</DT>
26369 <DD>This is the default.
26370 Alpine will ask whether you want to rename the folders and whether you
26371 want to delete each of the old folders.
26372 </DD>
26374 <DT>ask about rename, don't delete</DT>
26375 <DD>Alpine will ask whether you want to rename the folders, but won't
26376 ask about or delete old folders.
26377 </DD>
26379 <DT>always rename, ask about deleting</DT>
26380 <DD>This means you want to always answer yes and have Alpine automatically
26381 rename the folder if possible.
26382 You will also be asked about deleting old folders.
26383 </DD>
26385 <DT>always rename, don't delete</DT>
26386 <DD>This means you want to always answer yes and have Alpine automatically
26387 rename the folder if possible.
26388 There will be no deleting of old folders.
26389 </DD>
26391 <DT>don't rename, ask about deleting</DT>
26392 <DD>This means you want to always answer no.
26393 Alpine will not rename the folder.
26394 You will be asked about deleting old folders.
26395 </DD>
26397 <DT>don't rename, don't delete</DT>
26398 <DD>This means you want to always answer no.
26399 Alpine will not rename the folder.
26400 There will be no deleting of old folders, either.
26401 </DD>
26402 </DL>
26404 <P>
26405 <UL>
26406 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26407 </UL><P>
26408 <End of help on this topic>
26409 </BODY>
26410 </HTML>
26411 ====== h_config_reopen_rule =====
26412 <HTML>
26413 <HEAD>
26414 <TITLE>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></TITLE>
26415 </HEAD>
26416 <BODY>
26417 <H1>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></H1>
26419 Alpine normally checks for new mail in the currently open folder
26420 and in the INBOX every few <A HREF="h_config_mailcheck">minutes</A>.
26422 <P>
26423 There are some situations where automatic new-mail checking does not work.
26424 For example, if a mail folder is opened using the POP protocol or a newsgroup
26425 is being read using the NNTP protocol, then new-mail checking is disabled.
26427 <P>
26428 It may be possible to check for new mail in these cases by reopening the
26429 folder.
26430 Alpine does not do this for you automatically, but you may do the commands
26431 manually to cause this to happen.
26432 You reopen by going back to the folder list screen from the message
26433 index screen with the "<" command,
26434 and then going back into the message index screen with
26435 the ">" command.
26436 (Actually, any method you would normally use to open a folder will work the
26437 same as the "<" followed by ">" method.
26438 For example, the GoTo Folder command will work, or you may use L to go to the
26439 Folder List screen and Carriage Return to reopen the folder.)
26441 <P>
26442 There are some cases where Alpine knows that reopening the folder should
26443 be useful as a way to discover new mail.
26444 At the time of this writing, connections made using the POP protocol,
26445 news reading using the NNTP protocol, local news reading, and local
26446 ReadOnly folders that are in the traditional UNIX or the MMDF format all
26447 fall into this category.
26448 There are other cases where it <EM>may</EM> be a way to discover new mail, but Alpine
26449 has no way of knowing, so it might also just be an exercise in futility.
26450 All remote, ReadOnly folders other than those listed just above fall into this
26451 category.
26452 The setting of this option together with the type of folder
26453 controls how Alpine will react to the apparent attempt to reopen a folder.
26455 <P>
26456 If you don't reopen, then you will just be back in
26457 the message index with no change.
26458 You left the index and came back, but the folder remained "open"
26459 the whole time.
26460 However, if you do reopen the folder, the folder is closed and then reopened.
26461 In this case, the current state of the open folder is lost.
26462 The New status, Important and Answered flags,
26463 selected state, Zoom state, collapsed or expanded state of threads,
26464 current message number,
26465 and any other temporary state is all lost when the reopen happens.
26466 For POP folders (but not NNTP newsgroups) the Deleted flags are also lost.
26468 <P>
26469 In the possibilities listed below, the text says "POP/NNTP" in
26470 several places.
26471 That really implies the case where Alpine knows it is a good way to discover
26472 new mail, which is more than just POP and NNTP, but POP and NNTP are
26473 the cases of most interest.
26474 This option probably has more possible values than it deserves. They are:
26476 <DL>
26477 <DT>Always reopen</DT>
26478 <DD>Alpine will not ask whether you want to reopen but will just do the reopen
26479 whenever you type a command that implies a reopen, regardless of the
26480 access method.
26481 In other words, it is assumed you would always answer Yes if asked
26482 about reopening.
26483 </DD>
26485 <DT>Yes for POP/NNTP, Ask about other remote [Yes]</DT>
26486 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
26487 will ask you whether to reopen other remote folders,
26488 with a default answer of Yes.
26489 </DD>
26491 <DT>Yes for POP/NNTP, Ask about other remote [No]</DT>
26492 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
26493 will ask you whether to reopen other remote folders,
26494 with a default answer of No.
26495 </DD>
26497 <DT>Yes for POP/NNTP, No for other remote</DT>
26498 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, and
26499 will assume a No answer for all other remote folders.
26500 </DD>
26502 <DT>Always ask [Yes]</DT>
26503 <DD>Alpine will not differentiate based on access method.
26504 It will always ask for all remote folders, with a default answer of Yes.
26505 </DD>
26507 <DT>Always ask [No]</DT>
26508 <DD>Alpine will not differentiate based on access method.
26509 It will always ask for all remote folders, with a default answer of No.
26510 </DD>
26512 <DT>Ask about POP/NNTP [Yes], No for other remote</DT>
26513 <DD>Alpine will ask if the access method is POP or NNTP, with a default answer
26514 of Yes.
26515 It will never attempt to reopen other remote folders.
26516 </DD>
26518 <DT>Ask about POP/NNTP [No], No for other remote</DT>
26519 <DD>This is the default.
26520 Alpine will ask if the access method is POP or NNTP, with a default answer
26521 of No.
26522 It will never attempt to reopen other remote folders.
26523 </DD>
26525 <DT>Never reopen</DT>
26526 <DD>Alpine will never attempt to reopen already open folders.
26527 </DD>
26528 </DL>
26530 <P>
26531 Remember, wherever it says POP or NNTP above it really means POP or NNTP or
26532 any of the other situations where it is likely that reopening is a good way
26533 to discover new mail.
26535 <P>
26536 There is an alternative that may be of useful in some situations.
26537 Instead of manually checking for new mail you can set up a
26538 <A HREF="h_maildrop">Mail Drop</A>
26539 and automatically check for new mail.
26541 <P>
26542 <UL>
26543 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26544 </UL><P>
26545 <End of help on this topic>
26546 </BODY>
26547 </HTML>
26548 ====== h_config_inc_startup =====
26549 <HTML>
26550 <HEAD>
26551 <TITLE>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></TITLE>
26552 </HEAD>
26553 <BODY>
26554 <H1>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></H1>
26556 This value affects Alpine's behavior when opening the "INBOX" or
26557 one of the "INCOMING MESSAGE FOLDERS".
26558 It determines which message will be the <EM>current message</EM> when
26559 the folder is first opened.
26560 The default value is "first-unseen".
26562 <P>
26563 The seven possible values for this option are:
26565 <DL>
26566 <DT>first-unseen</DT>
26567 <DD>The current message is set to the first
26568 unseen message that has not been marked deleted, or the last message if
26569 all of the messages have been seen previously.
26570 Messages which have not been seen or which have been seen but re-marked
26571 as New are considered unseen messages.
26572 See the note at the bottom of this help about newsgroups.
26573 </DD>
26575 <DT>first-recent</DT>
26576 <DD>Similar to the default, but rather than starting on the first
26577 unseen message Alpine starts on the first <EM>recent</EM> message.
26578 A message is recent if it arrived since the last time the folder was
26579 open. This value causes the current message to be set to the first
26580 recent message if there is one, otherwise to the last
26581 message in the folder.
26582 </DD>
26584 <DT>first-important</DT>
26585 <DD>This will result in the current message being set to the first
26586 message marked Important (but not Deleted).
26587 If no messages are marked Important, then it will be the last message.
26588 Messages are marked Important by <EM>you</EM>, not by the sender, using
26589 the
26590 <A HREF="h_common_flag">Flag command</A>.
26591 Or they may be marked Important by an Alpine
26592 <A HREF="h_mainhelp_filtering">Filter</A>
26593 that you have set up.
26594 </DD>
26596 <DT>first-important-or-unseen</DT>
26597 <DD>This selects the first of the first unseen and the first important
26598 messages.
26599 </DD>
26601 <DT>first-important-or-recent</DT>
26602 <DD>This selects the first of the first recent and the first important
26603 messages.
26604 </DD>
26606 <DT>first</DT>
26607 <DD>Simply starts you on the <EM>first</EM> undeleted message in the folder.
26608 If all messages are deleted you start on the last message.
26609 </DD>
26611 <DT>last</DT>
26612 <DD>Simply starts you on the <EM>last</EM> undeleted message in the folder
26613 If all messages are deleted you start on the last message.
26614 </DD>
26615 </DL>
26617 <P>
26618 NOTE: For newsgroups in the incoming collection, "first-unseen" and
26619 "first-recent" are the same and are affected by whether or not the
26620 feature
26621 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
26622 is turned on.
26623 Also, there is no permanent storage in news for an Important flag.
26624 This means that no messages will be marked Important when a newsgroup is
26625 first opened.
26627 <P>
26628 <UL>
26629 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26630 </UL><P>
26631 <End of help on this topic>
26632 </BODY>
26633 </HTML>
26634 ====== h_config_browser =====
26635 <HTML>
26636 <HEAD>
26637 <TITLE>OPTION: <!--#echo var="VAR_url-viewers"--></TITLE>
26638 </HEAD>
26639 <BODY>
26640 <H1>OPTION: <!--#echo var="VAR_url-viewers"--></H1>
26641 <!--chtml if pinemode="os_windows"-->
26642 PC-Alpine users do not need to enter anything here, unless:<UL>
26643 <LI> they want to override, for use with Alpine, the application defined
26644 in the Windows operating system for handling URLs; or
26645 <LI> they are (planning on) using the same configuration file with
26646 Unix Alpine.
26647 </UL>
26648 <P>
26649 Note that if using a viewer that has a space in its path, you should
26650 use the DOS name for that directory or file. Example:
26651 <PRE>
26652 url-viewer=C:\Progra~1\mozilla\mozilla.exe
26653 </PRE>
26654 <HR><P>
26655 <!--chtml endif-->
26656 This option affects Alpine's handling of URLs that are found in
26657 messages you read. Normally, only URLs Alpine can handle directly
26658 are automatically offered for selection in the "Message
26659 Text" screen. When one or more applications
26660 capable of deciphering URLs on their command line are added here, Alpine
26661 will choose the first available to display URLs it cannot handle directly.
26662 A viewer's availability is based on its being specified with a <B>full
26663 directory path</B> and the evaluation of any optionally supplied
26664 parameters described below.
26666 <P>
26667 Additionally, to support various connection methods and applications, each
26668 entry in this list can optionally begin with one or more of
26669 the following special tokens. The allowed tokens include:
26671 <P>
26672 <DL>
26673 <DT>_TEST(<VAR>test-string</VAR>)_</DT>
26674 <DD>
26675 The <VAR>test-string</VAR> is a shell command that Alpine will run to
26676 evaluate a viewer's availability. The command specified by the test
26677 string is run and if its resulting exit status is non-zero, Alpine will
26678 not consider the associated viewer for use.
26679 </DD>
26681 <DT>_SCHEME(<VAR>scheme-list</VAR>)_</DT>
26682 <DD>
26683 The <VAR>scheme-list</VAR> is a list of one or more (comma-delimited)
26684 URL schemes that are to be used with the associated viewer. This is
26685 the way to configure Alpine to recognize URLs other than the built-in set.
26686 <P>
26687 It can also be used to override Alpine's built-in handlers.
26688 For example, you could specify "news" in the <VAR>scheme-list</VAR>,
26689 and Alpine would use (provided it passed all other criteria) the associated
26690 viewer when it encounterd a URL of the form "news:comp.mail.pine".
26692 </DD>
26693 </DL>
26695 <P>
26696 By default, Alpine will simply append a space character followed by the
26697 selected URL prior to launching the command in your specified SHELL. You can
26698 optionally specify where in the command the selected URL should appear
26699 by using the "_URL_" token. All occurrences found in the command
26700 will be replaced with the selected URL before the command is handed
26701 to the shell. If such replacement occurs, the default appending of the
26702 selected URL does not take place.
26704 <P>
26705 NOTE: If the viewer you specify has any command-line arguments,
26706 including the "_URL_" token, you will need to add a
26707 double-quote character before the command path and after the last
26708 argument (see the "lynx" example below).
26710 <P>
26711 So, here are some example entries:
26712 <PRE>
26713 url-viewers = _TEST("test -n '${DISPLAY}'")_ /usr/local/bin/netscape
26714 "/usr/local/bin/lynx _URL_"
26715 C:\BIN\NETSCAPE.BAT
26716 </PRE>
26717 <P>
26718 This example shows that for the first viewer in the list to be used
26719 the environment variable "DISPLAY" must be defined. If it
26720 is, then the path and file "/usr/local/bin/netscape" must exist.
26721 If neither condition is met,
26722 then the path and file "/usr/local/bin/lynx" must exist.
26723 If it does, then the "_URL_" token is replaced by the selected URL.
26724 If the path to "lynx" is invalid,
26725 then the final path and file C:\BIN\NETSCAPE.BAT must exist.
26726 Note that the last
26727 entry is a DOS/Windows path. This is one way to support Alpine running
26728 on more than one architecture with the same configuration file.<P>
26729 <P>
26730 <!--chtml if pinemode="os_windows"-->
26731 <!--chtml else-->
26732 Note that depending on the type of browser used and the method of
26733 its invocation (such as whether it will open in a separate window) from
26734 the MESSAGE TEXT screen, the browser may "supplant"
26735 the MESSAGE TEXT screen, and you will have to quit the browser to return to
26736 it (for example, when using Lynx; to exit Lynx, use the "Q" command).
26737 In other words, launching the browser from Alpine may make Alpine
26738 "disappear" (although it is still "running")
26739 until you close the browser again.<P>
26740 <UL><LI><A HREF="h_config_browser_xterm">Defining <!--#echo var="VAR_url-viewers"--> in an X windows
26741 environment: for advanced users and systems administrators</A>
26742 </UL>
26743 <!--chtml endif-->
26744 <P>If you are unsure what browsers are available on your system or how to
26745 specify them in Alpine's <!--#echo var="VAR_url-viewers"--> option for best usability, contact your
26746 local computing support staff.
26747 <P><UL>
26748 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26749 </UL>
26750 <P>
26751 <End of help on this topic>
26752 </BODY>
26753 </HTML>
26754 ====== h_config_browser_xterm =====
26755 <HTML>
26756 <HEAD>
26757 <TITLE><!--#echo var="VAR_url-viewers"--> and X windows applications</TITLE>
26758 </HEAD>
26759 <BODY>
26760 <H1>Defining <!--#echo var="VAR_url-viewers"--> in an X windows
26761 environment: for advanced users and systems administrators</H1>
26762 If you are using Alpine with an X-terminal (emulator) and want to define an
26763 X windows-based application in <!--#echo var="VAR_url-viewers"-->,
26764 you may want to do so in a manner that causes any <B>already</B>
26765 invoked viewer application to be used for viewing URLs you select from Alpine
26766 messages, and a <B>new</B> URL-viewer process to be
26767 started <B>only</B> if the same application has <B>not already</B>
26768 been launched -- for one reason, to avoid file-locking contentions among
26769 multiple invocations of the same URL-viewer application.
26770 (The example entries set in the help screen for the "<!--#echo var="VAR_url-viewers"-->"
26771 option does not do this.) A method of doing that would be:<OL>
26772 <LI> use
26773 the _TEST(<VAR>test-string</VAR>)_ token in the <B>first</B> entry to
26774 check (using commands appropriate for your Unix shell
26775 in place of <VAR>test-string</VAR>) for the presence of a
26776 lockfile created by the URL-viewer application -- which implies that the
26777 application is already running, though this is not foolproof.
26778 Following that in the same <!--#echo var="VAR_url-viewers"--> entry, specify the
26779 application with its appropriate command line option(s) to
26780 show the URL selected from the Alpine message in an already open window of
26781 that application, or perhaps in a new window of that application.
26783 <LI> In the
26784 <B>second</B> entry for the <!--#echo var="VAR_url-viewers"--> option, specify the same
26785 application without those command line options, but this time using the
26786 _TEST(...)_ token to check whether the environment variable "DISPLAY"
26787 is defined.
26788 <LI> If you will be using Alpine (with the same .pinerc file) outside of the X
26789 windows environment (for instance, using VT-100 terminal emulation), you
26790 may wish to specify a non-X windows URL-viewer application such as Lynx
26791 as the last entry.
26792 </OL><BR>
26793 How exactly you define your <!--#echo var="VAR_url-viewers"--> entries to do this will depend on
26794 the command shell, the URL-viewer application(s), and possibly the specific
26795 version of the latter, you are using.
26796 <P>
26797 Relevant command
26798 line options for the Netscape browser for showing URLs (selected from Alpine)
26799 when Netscape is already running are discussed in the document
26800 "Remote Control of UNIX Netscape"
26801 found at the URL (as of 12 Aug. 1998):
26802 <P>
26804 <CENTER><A HREF="http://home.netscape.com/newsref/std/x-remote.html">http://home.netscape.com/newsref/std/x-remote.html</A></CENTER>
26806 <P>(If the URL-viewer application is
26807 <B>not</B> running on the same host as Alpine, but being launched from an
26808 applications server, you may not be able to use the command line options for
26809 using an existing invocation of the application in Alpine's <!--#echo var="VAR_url-viewers"--> entry.)
26810 <P>
26811 <!--chtml if this-method="shown-to-work"-->
26812 An example using the Korn shell and the Netscape browser (first entry wrapped
26813 because of its length, but should all appear on one line):
26814 <P>
26815 url-viewers = _TEST("test -L /myhomedir/.netscape/lock")_ "/usr/local/bin/netscape -remote 'openURL(_URL_, new-window)' &"<BR>
26817 _TEST("test -n '${DISPLAY}'")_ "/usr/local/bin/netscape &"<BR>
26818 "/usr/local/bin/lynx '_URL_'"
26819 <P>
26820 <!--chtml endif-->
26821 <P>
26822 <UL>
26823 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26824 </UL><P>
26825 <End of help on this topic>
26826 </BODY>
26827 </HTML>
26828 ====== h_config_enable_full_hdr =====
26829 <HTML>
26830 <HEAD>
26831 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></TITLE>
26832 </HEAD>
26833 <BODY>
26834 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></H1>
26836 This feature enables the "H Full Headers" command which toggles between
26837 the display of all headers in the message and the normal edited view of
26838 headers. The Full Header command also controls which headers are included
26839 for Export, Pipe, Print, Forward, and Reply functions. (For Reply, the
26840 Full Header mode will respect the
26841 <A HREF="h_config_include_header">"Include-Headers-in-Reply"</A>
26842 feature setting.)
26843 <P>
26844 If Full Header mode is turned on and you Forward a message, you will
26845 be asked if you'd like to forward the message as an attachment, as opposed
26846 to including the text of the message in the body of your new message.
26847 <P>
26848 If you have also turned on the
26849 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
26850 option then the Full Headers command actually rotates through three states
26851 instead of just two.
26852 The first is the normal view with long quotes suppressed.
26853 The second is the normal view but with the long quotes included.
26854 The last enables the display of all headers in the message.
26855 When using Export, Pipe, Print, Forward, or Reply the quotes are
26856 never suppressed, so the first two states are identical.
26857 <P>
26858 Normally, the Header Mode will reset
26859 to the default behavior when moving to a new message.
26860 The mode can be made to persist from message to message by setting the feature
26861 <A HREF="h_config_quell_full_hdr_reset"><!--#echo var="FEAT_quell-full-header-auto-reset"--></A>.
26862 <P>
26863 <UL>
26864 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26865 </UL><P>
26866 <End of help on this topic>
26867 </BODY>
26868 </HTML>
26869 ====== h_config_enable_full_hdr_and_text =====
26870 <HTML>
26871 <HEAD>
26872 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></TITLE>
26873 </HEAD>
26874 <BODY>
26875 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></H1>
26877 This feature affects how the "H Full Headers" command displays
26878 message text. If set, the raw message text will be displayed. This
26879 especially affects MIME formatted email, where the entire MIME format
26880 will be displayed. This feature similarly affects how messages are
26881 included for the Export, Pipe, Print, Forward, and Reply functions.
26882 <P>
26883 When viewing a raw message that has attachments with this feature set,
26884 you will not be able to view attachments without first leaving full
26885 headers mode. This is because MIME parsing is not done on the raw message.
26886 <P>
26887 <UL>
26888 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26889 </UL><P>
26890 <End of help on this topic>
26891 </BODY>
26892 </HTML>
26893 ====== h_config_enable_pipe =====
26894 <HTML>
26895 <HEAD>
26896 <TITLE>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></TITLE>
26897 </HEAD>
26898 <BODY>
26899 <H1>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></H1>
26901 This feature enables the "| Pipe" command that sends the current message
26902 to the specified command for external processing.
26903 <P>
26905 A short description of how the pipe command works is given
26906 <A HREF="h_pipe_command">here</A>.
26908 <P>
26909 <UL>
26910 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26911 </UL><P>
26912 <End of help on this topic>
26913 </BODY>
26914 </HTML>
26915 ====== h_config_quell_full_hdr_reset =====
26916 <HTML>
26917 <HEAD>
26918 <TITLE>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></TITLE>
26919 </HEAD>
26920 <BODY>
26921 <H1>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></H1>
26923 The <A HREF="h_common_hdrmode">HdrMode Command</A>
26924 normally resets to the default state when switching to a new message.
26925 For example, if you've used the "H" command to turn on Full
26926 Headers for a message you are viewing, and then you type the Next command
26927 to look at the next message, the full headers will no longer be shown.
26928 Setting this feature disables that reset.
26929 Instead, the Header Mode remains the same from message to message.
26931 <P>
26932 The presence or absence of the HdrMode command is determined by the
26933 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
26934 Feature-List option.
26935 <P>
26936 <UL>
26937 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26938 </UL><P>
26939 <End of help on this topic>
26940 </BODY>
26941 </HTML>
26942 ====== h_config_enable_tab_complete =====
26943 <HTML>
26944 <HEAD>
26945 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></TITLE>
26946 </HEAD>
26947 <BODY>
26948 <H1>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></H1>
26950 This feature enables the TAB key when at a prompt for a filename. In this
26951 case, TAB will cause the partial name already entered to be automatically
26952 completed, provided the partial name is unambiguous.
26953 This feature is on by default.
26954 <P>
26955 Similarly, this feature also enables TAB completion of address book
26956 nicknames when at a prompt for a nickname,
26957 or when typing in an address field in the composer.
26958 <P>
26959 <End of help on this topic>
26960 </BODY>
26961 </HTML>
26962 ====== h_config_quit_wo_confirm =====
26963 <HTML>
26964 <HEAD>
26965 <TITLE>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></TITLE>
26966 </HEAD>
26967 <BODY>
26968 <H1>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></H1>
26970 This feature controls whether or not Alpine will ask for confirmation when a
26971 Quit command is received.
26972 <P>
26973 <End of help on this topic>
26974 </BODY>
26975 </HTML>
26976 ====== h_config_quote_replace_noflow =====
26977 <HTML>
26978 <HEAD>
26979 <TITLE>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></TITLE>
26980 </HEAD>
26981 <BODY>
26982 <H1>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></H1>
26984 This feature, which is only active when
26985 <A HREF="h_config_quote_replace_string"><!--#echo var="VAR_quote-replace-string"--></A> is
26986 also set,
26987 enables quote-replacement on non-flowed messages. It is off
26988 by default because a non-flowed message is more dependent on its format,
26989 and thus quote-replacement may cause less-than-pleasing results.
26990 Setting this feature will cause quote-replacement similar to that of flowed
26991 messages, but with the added possibility of long lines being wrapped
26992 into new lines if the Quote-Replacement-String is longer than the string
26993 it is replacing, which is "> ".
26994 <P>
26995 <End of help on this topic>
26996 </BODY>
26997 </HTML>
26998 ====== h_config_enable_jump =====
26999 <HTML>
27000 <HEAD>
27001 <TITLE>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></TITLE>
27002 </HEAD>
27003 <BODY>
27004 <H1>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></H1>
27006 When this feature is set you may enter a number (followed by RETURN)
27007 and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT
27008 screens. In other words, it obviates the need for typing the "J" for the
27009 Jump command.
27010 <P>
27011 <End of help on this topic>
27012 </BODY>
27013 </HTML>
27014 ====== h_config_enable_alt_ed =====
27015 <HTML>
27016 <HEAD>
27017 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></TITLE>
27018 </HEAD>
27019 <BODY>
27020 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></H1>
27022 If this feature is set (the default), and the
27023 <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27024 <B>is not</B> set, entering
27025 the ^_ (Ctrl-underscore) key while composing a message will prompt you
27026 for the name of the editor you would like to use.
27027 <P>
27028 If the environment variable $EDITOR is set, its value will be offered as
27029 a default.
27030 <P>
27031 If the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27032 <B>is</B> set, the ^_ key will activate the specified
27033 editor without prompting, in which case it is not necessary to
27034 set the "<!--#echo var="FEAT_enable-alternate-editor-cmd"-->" feature.
27035 <P>
27036 <UL>
27037 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27038 </UL><P>
27039 <End of help on this topic>
27040 </BODY>
27041 </HTML>
27042 ====== h_config_alt_ed_now =====
27043 <HTML>
27044 <HEAD>
27045 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></TITLE>
27046 </HEAD>
27047 <BODY>
27048 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></H1>
27050 If this feature and the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A>
27051 variable are both set, Alpine will
27052 automatically activate the specified editor when the cursor is moved from
27053 the header of the message being composed into the message text. For
27054 replies, the alternate editor will be activated immediately. If this
27055 feature is set but the "<!--#echo var="VAR_editor"-->" variable is not set, then Alpine will
27056 automatically ask for the name of an alternate editor when the cursor
27057 is moved out of the header being composed, or if a reply is being done.
27059 <P><UL>
27060 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27061 </UL>
27062 <P>
27063 <End of help on this topic>
27064 </BODY>
27065 </HTML>
27066 ====== h_config_enable_bounce =====
27067 <HTML>
27068 <HEAD>
27069 <TITLE>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></TITLE>
27070 </HEAD>
27071 <H1>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></H1>
27072 <BODY>
27074 Setting this feature enables the "B Bounce" command, which will prompt
27075 for an address and *remail* the message to the new recipient. This command
27076 is used to re-direct messages that you have received in error, or need to
27077 be redirected for some other reason (e.g. list moderation). The final
27078 recipient will see a header indicating that you have Resent the msg, but
27079 the message's From: header will show the original author of the message,
27080 and replies to it will go back to that author, and not to you.
27081 <P>
27082 <End of help on this topic>
27083 </BODY>
27084 </HTML>
27085 ====== h_config_enable_agg_ops =====
27086 <HTML>
27087 <HEAD>
27088 <TITLE>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></TITLE>
27089 </HEAD>
27090 <BODY>
27091 <H1>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></H1>
27093 When this feature is set you may use the commands and subcommands that relate to
27094 performing operations on more than one message at a time. We call these
27095 "aggregate operations". In particular, the
27096 <!--chtml if pinemode="function_key"-->"F5
27097 <!--chtml else-->";
27098 <!--chtml endif--> Select",
27100 <!--chtml if pinemode="function_key"-->
27101 "F6
27102 <!--chtml else-->
27103 "A
27104 <!--chtml endif-->
27105 Apply", and
27106 <!--chtml if pinemode="function_key"-->
27107 "F4
27108 <!--chtml else-->
27109 "Z
27110 <!--chtml endif-->
27111 Zoom" commands are enabled by this feature. Select is used to
27112 "tag" one or more messages meeting the specified criteria. Apply can
27113 then be used to apply any message command to all of the selected/tagged
27114 messages. Further, the Zoom command allows you to toggle the MESSAGE INDEX
27115 view between just those Selected and all messages in the folder.
27116 <P>
27117 This feature also enables the
27118 <!--chtml if pinemode="function_key"-->
27119 "F7"
27120 <!--chtml else-->
27121 "^X"
27122 <!--chtml endif-->
27124 subcommand in the MESSAGE INDEX
27125 WhereIs command that causes all messages matching the WhereIs argument to
27126 become selected; and the Select, Select Current, and ZoomMode commands in the
27127 <A HREF="h_folder_maint">FOLDER LIST screen</A>.
27128 <P>
27129 Some related help topics are
27130 <UL>
27131 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
27132 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
27133 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
27134 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
27135 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
27136 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
27137 </UL>
27138 <P>
27139 <UL>
27140 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27141 </UL><P>
27142 <End of help on this topic>
27143 </BODY>
27144 </HTML>
27146 ====== h_config_enable_flag =====
27147 <HTML>
27148 <HEAD>
27149 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></TITLE>
27150 </HEAD>
27151 <BODY>
27152 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></H1>
27154 Setting this feature enables the
27155 <A HREF="h_common_flag">"* Flag"</A>
27156 command that allows you to
27157 manipulate the status flags associated with a message. By default, Flag
27158 will set the "Important" flag, which results in an asterisk being
27159 displayed in column one of the MESSAGE INDEX for such messages.
27160 <P>
27161 <End of help on this topic>
27162 </BODY>
27163 </HTML>
27164 ====== h_config_flag_screen_default =====
27165 <HTML>
27166 <HEAD>
27167 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></TITLE>
27168 </HEAD>
27169 <BODY>
27170 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></H1>
27172 The feature modifies the behavior of the
27173 <a href="h_common_flag">Flag</a>
27174 command (provided it too is
27175 <A HREF="h_config_enable_flag">enabled</A>).
27176 By default, when the "* Flag" command is selected,
27177 Alpine offers a prompt to set one of several flags and also offers the
27178 option of entering the detailed flag manipulation screen via the "^T"
27179 key. Enabling this feature causes Alpine to immediately enter the detailed
27180 flag screen rather than first offer the simple prompt.
27181 The
27182 <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.
27183 <P>
27184 <End of help on this topic>
27185 </BODY>
27186 </HTML>
27187 ====== h_config_flag_screen_kw_shortcut =====
27188 <HTML>
27189 <HEAD>
27190 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></TITLE>
27191 </HEAD>
27192 <BODY>
27193 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></H1>
27195 This feature modifies the behavior of the
27196 <a href="h_common_flag">Flag</a> command
27197 and the <A HREF="h_index_cmd_select">Select</A> command.
27198 This feature is set by default.
27199 When this feature is not set, when the "* Flag" command is selected,
27200 Alpine offers a prompt to set one of several flags and also offers the
27201 option of entering the detailed flag manipulation screen via the "^T"
27202 key.
27203 If you have
27204 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
27205 defined, then enabling this feature adds a shortcut way to set or unset
27206 keywords.
27207 You use "*" followed by the first letter of a keyword (or the nickname of
27208 a keyword if you've given it a nickname) and that will set the keyword.
27209 <P>
27210 An example is easier to understand than the explanation.
27211 The flag command can always be used to set the system flags.
27212 For example, to set the Answered flag you would type
27213 <P>
27214 <CENTER><SAMP>* A</SAMP></CENTER>
27215 <P>
27216 Now suppose you have defined a keyword "Work" using the <!--#echo var="VAR_keywords"-->
27217 option in the Config screen.
27218 By default, to set a keyword like "Work" you would usually
27219 have to go to the Flag Details screen using
27220 the "^T To Flag Details" command.
27221 Instead, if you have enabled this feature, you may type
27222 <P>
27223 <CENTER><SAMP>* W</SAMP></CENTER>
27224 <P>
27225 to set the Work flag, or
27226 <P>
27227 <CENTER><SAMP>* ! W</SAMP></CENTER>
27228 <P>
27229 to unset it.
27230 Just like for the other flag setting commands, the case of the letter does
27231 not matter, so "w" or "W" both set the "Work"
27232 keyword.
27233 <P>
27234 Notice that you can only use this trick for one keyword that begins
27235 with "W".
27236 If you happen to have a "Work" keyword and another keyword that is
27237 "WIFI" the "* W" command will set the first one in
27238 your list of keywords.
27239 Also, there are five letters that are reserved for system
27240 flags and the NOT command.
27241 If you type "* A" it will always set the Answered flag, not
27242 your "Aardvark" keyword.
27243 In order to set the "Aardvark" keyword you'll still have to use
27244 the Flag Details screen.
27245 <P>
27246 Because enabling the
27247 <A HREF="h_config_flag_screen_default"><!--#echo var="FEAT_enable-flag-screen-implicitly"--></A>
27248 option causes Alpine to skip directly to the Flag Details screen when the
27249 Flag command is used,
27250 setting it will cause this feature to have no effect at all.
27251 <P>
27252 Similarly, when Selecting by Keyword, setting this option will allow you
27253 to use Keyword initials instead of full keywords.
27254 <P>
27255 <End of help on this topic>
27256 </BODY>
27257 </HTML>
27258 ====== h_config_can_suspend =====
27259 <HTML>
27260 <HEAD>
27261 <TITLE>FEATURE: <!--#echo var="FEAT_enable-suspend"--></TITLE>
27262 </HEAD>
27263 <BODY>
27264 <H1>FEATURE: <!--#echo var="FEAT_enable-suspend"--></H1>
27266 Setting this feature will allow you to type ^Z (Control Z) to
27267 <!--chtml if pinemode="os_windows"-->
27268 minimize Alpine into its icon, bringing into focus whatever
27269 application is running behind the PC-Alpine window.
27270 <!--chtml else-->
27271 temporarily suspend Alpine.
27273 <P>
27274 This does not exit Alpine, but puts it in the background to watch
27275 for new mail and such. Normally, you type a command, such
27276 as "fg" at your system prompt to return to your Alpine session.
27278 <P>
27279 The <A HREF="h_config_suspend_spawns"><!--#echo var="FEAT_use-subshell-for-suspend"--></A> feature
27280 adjusts whether Alpine is placed into the background of the shell its
27281 running in or starts a news shell.
27282 <!--chtml endif-->
27284 <P>
27285 <UL>
27286 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27287 </UL><P>
27288 <End of help on this topic>
27289 </BODY>
27290 </HTML>
27291 ====== h_config_take_lastfirst ======
27292 <HTML>
27293 <HEAD>
27294 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></TITLE>
27295 </HEAD>
27296 <BODY>
27297 <H1>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></H1>
27299 Normally, when TakeAddr is used to copy an address from a message into
27300 an address book entry, Alpine will attempt to rewrite the full name of the
27301 address in the form
27302 <P>
27304 Last, First<P>
27306 instead of<P>
27308 First Last
27310 <P>
27311 It does this because many people find it useful to sort by Last name
27312 instead of First name. If this feature is set, then the TakeAddr command
27313 will not attempt to reverse the name in this manner.
27314 <P>
27315 <End of help on this topic>
27316 </BODY></HTML>
27317 ====== h_config_disable_regex ======
27318 <HTML>
27319 <HEAD>
27320 <TITLE>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></TITLE>
27321 </HEAD>
27322 <BODY>
27323 <H1>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></H1>
27325 Normally, the
27326 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
27327 option is interpreted as a regular expression.
27328 One type of address that might cause trouble is an address that
27329 contains a plus sign.
27330 If you want to have an address with a plus as one of your
27331 <!--#echo var="VAR_alt-addresses"-->
27332 and you don't want to use regular expressions, then setting this
27333 feature will cause Alpine to treat the addresses you list literally instead.
27334 <P>
27335 <End of help on this topic>
27336 </BODY></HTML>
27337 ====== h_config_take_fullname ======
27338 <HTML>
27339 <HEAD>
27340 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></TITLE>
27341 </HEAD>
27342 <BODY>
27343 <H1>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></H1>
27345 Normally, when TakeAddr is used to copy an address or addresses
27346 from a message into an address book entry, Alpine will try to preserve
27347 the full name associated with each address in the list of addresses.
27348 The reason for this is so that if the entry is a list or later becomes a
27349 list, then information about the individual addresses in the list
27350 is preserved.
27351 If you would rather just have the simple addresses in the list of addresses,
27352 set this feature. For example, with the default setting you might
27353 see something like this in the ADDRESS BOOK editor after you type TakeAddr
27354 <P>
27355 <PRE>
27356 Nickname : nick
27357 Fullname : Bedrock Elders
27358 Fcc :
27359 Comment :
27360 Addresses : Fred Flintstone <flint@bedrock.org>,
27361 Barney Rubble <rubble@bedrock.org>
27362 </PRE>
27363 <P>
27364 but with this feature set it would look like
27365 <P>
27366 <PRE>
27367 Nickname : nick
27368 Fullname : Bedrock Elders
27369 Fcc :
27370 Comment :
27371 Addresses : flint@bedrock.org,
27372 rubble@bedrock.org
27373 </PRE>
27374 <P>
27375 instead. Note the difference in the Addresses field.
27376 <P>
27377 <End of help on this topic>
27378 </BODY></HTML>
27379 ====== h_config_print_from ======
27380 <HTML>
27381 <HEAD>
27382 <TITLE>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></TITLE>
27383 </HEAD>
27384 <BODY>
27385 <H1>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></H1>
27387 If this feature is set, then the Berkeley-mail style From line is included
27388 at the start of each message that is printed. This line looks something
27389 like the following, with the address replaced by the address from the
27390 From line of the message being printed:
27391 <P>
27392 From user@domain.somewhere.com Mon May 13
27393 14:11:06 1998
27394 <P>
27395 <End of help on this topic>
27396 </BODY>
27397 </HTML>
27398 ====== h_config_expanded_distlists ======
27399 <HTML>
27400 <HEAD>
27401 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></TITLE>
27402 </HEAD>
27403 <BODY>
27404 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></H1>
27405 If this feature is set, then distribution lists in the address book
27406 screen will always be expanded automatically.
27407 <P>
27408 <End of help on this topic>
27409 </BODY>
27410 </HTML>
27411 ====== h_config_compose_news_wo_conf ======
27412 <HTML>
27413 <HEAD>
27414 <TITLE>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></TITLE>
27415 </HEAD>
27416 <BODY>
27417 <H1>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></H1>
27418 This feature controls one aspect of Alpine's Composer. If you enter the
27419 composer while reading a newsgroup, you will normally be prompted to
27420 determine whether you intend the new message to be posted to the current
27421 newsgroup or not. If this feature is set, Alpine will not prompt you
27422 in this situation, and will assume that you do indeed wish to post
27423 to the newsgroup you are reading.
27424 <P>
27425 <End of help on this topic>
27426 </BODY>
27427 </HTML>
27428 ====== h_config_compose_rejects_unqual ======
27429 <HTML>
27430 <HEAD>
27431 <TITLE>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></TITLE>
27432 </HEAD>
27433 <BODY>
27434 <H1>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></H1>
27436 This feature controls one aspect of the message composer; in particular,
27437 what happens when an unqualified name is entered into an address header.
27438 If set, unqualified names entered as addresses will be treated as errors
27439 unless they match an addressbook nickname. Alpine will not attempt to turn
27440 them into complete addresses by adding your local domain.<P>
27442 A complete (fully qualified) address is one containing a username followed
27443 by an "@" ("at") symbol, followed by a domain name (e.g.
27444 "jsmith@example.com"). An unqualified name is one <B>without</B>
27445 the "@" symbol and domain name (e.g. "jsmith").
27447 (See also <A HREF="h_address_format">Explanation of Address formats</A>.)
27449 <P>
27451 When you enter a fully qualified address, Alpine does not interpret or
27452 modify it, but simply passes it on to the mail-transport-agent (MTA) for
27453 your system. Alpine conforms to the Internet standards governing message
27454 headers and will not send an unqualifed name to the MTA. Therefore, when
27455 you enter an unqualified name, Alpine will normally attempt to turn it into
27456 a fully qualified address, first by checking to see if you have entered a
27457 matching nickname in your addressbook, or failing that, by simply adding
27458 your own domain to the name entered. So if your address is
27459 "jsmith@example.com" and you enter "fred", then (assuming
27460 "fred" is not a nickname in your addressbook), Alpine will turn
27461 that into "fred@example.com".<P>
27463 There are situations where it is not desirable for Alpine to interpret such
27464 unqualified names as valid (local) addresses. For example, if "fred"
27465 turned out to be a typo (intended to be an addressbook nickname), but
27466 there actually was a "fred" in your local domain, the message might
27467 be mis-delivered without your realizing it. In order to reduce the likelihood
27468 of such accidents, setting this feature will cause Alpine to treat such
27469 addresses as errors, and require that you explicitly enter the full local
27470 address (e.g. "fred@example.com") or correct the name so that it
27471 matches an address book nickname.<P>
27473 Consider this a safety feature against mis-directed mail.
27474 <P>
27475 <UL>
27476 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27477 </UL><P>
27478 <End of help on this topic>
27479 </BODY>
27480 </HTML>
27481 ====== h_config_quell_local_lookup ======
27482 <HTML>
27483 <HEAD>
27484 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></TITLE>
27485 </HEAD>
27486 <BODY>
27487 <H1>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></H1>
27489 This feature controls an aspect of Alpine's Composer, and if needed, will
27490 usually be set by your system manager in Alpine's system-wide configuration
27491 file. Specifically, if this feature is set, Alpine will not attempt to look
27492 in the system password file to find a Full Name for the entered address.
27493 <P>
27494 Normally, names you enter into address fields (e.g. To: or Cc:) are
27495 checked against your address book(s) to see if they match an address book
27496 nickname. Failing that, (in Unix Alpine) the name is then checked against
27497 the Unix password file. If the entered name matches a username in the
27498 system password file, Alpine extracts the corresponding Full Name information
27499 for that individual, and adds that to the address being entered.
27500 <P>
27501 However, password file matching can have surprising (incorrect) results if
27502 other users of the system do not receive mail at the domain you are using.
27503 That is, if either the
27504 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> or
27505 <A HREF="h_config_domain_name">"<!--#echo var="VAR_use-only-domain-name"-->"</A>
27506 option
27507 is set such that the administrative domain of other users on the system
27508 isn't accurately reflected, Alpine should be told that a passwd file match
27509 is coincidental, and Full Name info will be incorrect. For example, a
27510 personal name from the password file could get falsely paired with the
27511 entered name as it is turned into an address in the configured domain.
27512 <P>
27513 If you are seeing this behavior, enabling this feature will prevent Unix
27514 Alpine from looking up names in the password file to find the Full Name
27515 for incomplete addresses you enter.<P>
27516 <UL>
27517 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27518 </UL>
27519 <P>
27520 <End of help on this topic>
27521 </BODY>
27522 </HTML>
27523 ====== h_config_tab_checks_recent ======
27524 <HTML>
27525 <HEAD>
27526 <TITLE>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></TITLE>
27527 </HEAD>
27528 <BODY>
27529 <H1>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></H1>
27531 In a FOLDER LIST screen, the TAB key usually just changes which
27532 folder is highlighted.
27533 If this feature is set, then the TAB key will cause the number of
27534 recent messages and the total number of messages in the highlighted folder
27535 to be displayed instead.
27537 <P>
27538 <End of help on this topic>
27539 </BODY>
27540 </HTML>
27541 ====== h_config_maildrops_preserve_state ======
27542 <HTML>
27543 <HEAD>
27544 <TITLE>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></TITLE>
27545 </HEAD>
27546 <BODY>
27547 <H1>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></H1>
27549 This feature affects the way <A HREF="h_maildrop">Mail Drops</A> work.
27550 Normally, when mail is moved from a Mail Drop folder to a destination
27551 folder, it is delivered as new mail.
27552 Any Seen/New, Answered, Important/Flagged state that has changed will be
27553 ignored.
27554 All of the mail will be considered unSeen, unAnswered, and unImportant after
27555 it is moved.
27556 <P>
27557 If this feature is set, then the state changes that have been made
27558 to the messages in the Mail Drop folder will be preserved.
27559 <P>
27560 In any case, messages that are already marked Deleted when the
27561 mail is to be moved from the Mail Drop will be ignored.
27562 <P>
27563 <End of help on this topic>
27564 </BODY>
27565 </HTML>
27566 ====== h_config_preopen_stayopens ======
27567 <HTML>
27568 <HEAD>
27569 <TITLE>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></TITLE>
27570 </HEAD>
27571 <BODY>
27572 <H1>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></H1>
27574 This feature is related to the option
27575 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
27576 Normally, Stay Open folders are only opened on demand, when the user
27577 asks to open them.
27578 From then on they are kept open for the duration of the session.
27579 However, if this feature is set, then the Stay Open folders will all be
27580 opened at startup, at the same time that the INBOX is opened.
27582 <P>
27583 <End of help on this topic>
27584 </BODY>
27585 </HTML>
27586 ====== h_config_expunge_inbox ======
27587 <HTML>
27588 <HEAD>
27589 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></TITLE>
27590 </HEAD>
27591 <BODY>
27592 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></H1>
27594 The INBOX is normally treated differently from regular folders in several
27595 ways.
27596 One of the differences is that the normal "close" sequence of
27597 events is deferred until Alpine is exited, instead of happening when you
27598 leave the INBOX to view another folder.
27599 The "close" sequence normally includes the Expunging
27600 of deleted messages
27601 (either automatically or after a prompt, controlled by the features
27602 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
27603 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
27604 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
27605 handling of the
27606 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>.
27608 <P>
27609 If this feature is set the "close" sequence handling will take
27610 place every time you leave the INBOX.
27611 The INBOX will still be kept open, but the offer to Expunge and the archiving
27612 to the <!--#echo var="VAR_read-message-folder"-->
27613 will take place each time you leave the INBOX instead of only once at the
27614 end of the session.
27616 <P>
27617 <End of help on this topic>
27618 </BODY>
27619 </HTML>
27620 ====== h_config_expunge_stayopens ======
27621 <HTML>
27622 <HEAD>
27623 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></TITLE>
27624 </HEAD>
27625 <BODY>
27626 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></H1>
27628 This feature is related to the option
27629 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
27630 Stay Open folders are treated differently from regular folders in several
27631 ways.
27632 One of the differences is that the normal "close" sequence of
27633 events is deferred until Alpine is exited, instead of happening when you
27634 leave the folder to view another folder.
27635 The "close" sequence normally includes the Expunging
27636 of deleted messages
27637 (either automatically or after a prompt, controlled by the features
27638 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
27639 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
27640 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
27641 handling of
27642 <A HREF="h_config_archived_folders"><!--#echo var="VAR_incoming-archive-folders"--></A>.
27644 <P>
27645 If this feature is set the "close" sequence handling will take
27646 place when you leave the Stay Open folder.
27647 The folder will still be kept open, but the offer to Expunge and the archiving
27648 will take place each time you leave the folder instead of only once at the
27649 end of the session.
27650 This feature does not affect the INBOX, which will still only be processed
27651 when you exit Alpine.
27652 However, there is a similar feature that affects only the INBOX called
27653 <A HREF="h_config_expunge_inbox">"<!--#echo var="FEAT_offer-expunge-of-inbox"-->"</A>.
27655 <P>
27656 <End of help on this topic>
27657 </BODY>
27658 </HTML>
27659 ====== h_config_preserve_start_stop ======
27660 <HTML>
27661 <HEAD>
27662 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></TITLE>
27663 </HEAD>
27664 <BODY>
27665 <H1>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></H1>
27667 This feature controls how special control key characters, typically
27668 Ctrl-S and Ctrl-Q, are interpreted when input to Alpine. These characters
27669 are known as the "stop" and "start" characters and are sometimes used in
27670 communications paths to control data flow between devices that operate at
27671 different speeds.
27673 <P>
27675 By default, Alpine turns the system's handling of these special characters
27676 off except during printing. However, if you see Alpine reporting input errors
27677 such as:
27678 <P>
27679 [ Command "^Q" not defined for this screen.]
27680 <P>
27681 and, at the same time, see your display become garbled, then it is likely
27682 that setting this option will solve the problem. Be aware, though, that
27683 enabling this feature will also cause Alpine to ostensibly "hang"
27684 whenever the Ctrl-S key combination is entered as the system is now
27685 interpreting such input as a "stop output" command. To "start
27686 output" again, simply type Ctrl-Q.
27687 <P>
27688 <End of help on this topic>
27689 </BODY>
27690 </HTML>
27691 ====== h_config_enable_incoming ======
27692 <HTML>
27693 <HEAD>
27694 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></TITLE>
27695 </HEAD>
27696 <BODY>
27697 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></H1>
27699 Alpine's Incoming Message Folders collection
27700 provides a convenient way to access multiple incoming folders.
27701 It is also useful if you have accounts on multiple computers.
27702 <P>
27704 If set, this feature defines a pseudo-folder collection called
27705 "INCOMING MESSAGE FOLDERS". Initially, the only folder included
27706 in this collection will be your INBOX, which will no longer show up in
27707 your Default folder collection.
27708 <P>
27710 You may add more folders to the Incoming Message Folders collection by
27711 using the
27712 <!--chtml if pinemode="function_key"-->
27713 "F10
27714 <!--chtml else-->
27715 "A
27716 <!--chtml endif-->
27717 Add" command in the FOLDER LIST screen. You will be prompted for
27718 the host the folder is stored on (which defaults to the same host used
27719 for your INBOX), a nickname, and the actual folder name. Once a set
27720 of Incoming Message Folders are defined, the TAB key (in MESSAGE INDEX
27721 or MESSAGE TEXT screens) may be used to scan the folders for those
27722 with Recent messages. If you add more folders to
27723 your <!--#echo var="VAR_incoming-folders"--> collection, turning this feature back off will have
27724 no effect.
27725 <P>
27726 NOTE: Normally the software that actually delivers mail (the stuff that happens
27727 before Alpine is involved) is in a better position to do delivery filtering
27728 than is Alpine itself.
27729 If possible, you may want to look at programs such as
27730 "filter" or "procmail", which are examples of delivery
27731 filtering programs.
27732 If you'd prefer to have Alpine do the filtering for you, you may set that
27733 up.
27734 Look <A HREF="h_rules_filter">here</A> for help with Alpine filtering.
27735 <P>
27736 <UL>
27737 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27738 </UL><P>
27739 <End of help on this topic>
27740 </BODY>
27741 </HTML>
27742 ====== h_config_enable_incoming_checking ======
27743 <HTML>
27744 <HEAD>
27745 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></TITLE>
27746 </HEAD>
27747 <BODY>
27748 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></H1>
27750 This feature is only operational if you have enabled the optional
27751 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> collection.
27752 If you do have Incoming Message Folders and you also set this feature,
27753 then the number of Unseen messages in each folder will be displayed
27754 in the FOLDER LIST screen for the Incoming Message Folders.
27755 The number of Unseen messages in a folder will be displayed in parentheses
27756 to the right of the name of each folder.
27757 If there are no Unseen messages in a folder then only the name
27758 is displayed, not a set of parentheses with zero inside them.
27759 A redraw command, Ctrl-L, can be used in the FOLDER LIST screen for
27760 the Incoming Message Folders to cause an immediate update.
27761 <P>
27762 If a check for Unseen messages fails for a particular folder then Alpine
27763 will no longer attempt to check that folder for the duration of the
27764 session and this will be indicated by a question mark inside the
27765 parentheses.
27766 <P>
27767 The features
27768 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>,
27769 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>,
27770 <A HREF="h_config_incoming_list"><!--#echo var="VAR_incoming-check-list"--></A>,
27771 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>,
27772 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>, and
27773 <A HREF="h_config_incoming_timeo"><!--#echo var="VAR_incoming-check-timeout"--></A>
27774 all affect how this feature behaves.
27775 <P>
27776 <UL>
27777 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27778 </UL><P>
27779 <End of help on this topic>
27780 </BODY>
27781 </HTML>
27782 ====== h_config_incoming_checking_total ======
27783 <HTML>
27784 <HEAD>
27785 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></TITLE>
27786 </HEAD>
27787 <BODY>
27788 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></H1>
27790 This option has no effect unless the feature
27791 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
27792 is set, which in turn has no effect unless
27793 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
27794 is set.
27795 <P>
27796 When incoming folder checking is turned on the default is to display
27797 the number of unseen messages in each folder.
27798 More precisely, it is the number of undeleted unseen messages.
27799 Using this option you may also display the total number of messages
27800 in each folder.
27801 Instead of a single number representing the number of unseen messages
27802 you will get two numbers separated by a slash character.
27803 The first is the number of unseen messages and the second is the
27804 total number of messages.
27805 <P>
27806 You may also use the recent message count instead of the unseen message
27807 count by turning on the feature
27808 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>.
27809 <P>
27810 <UL>
27811 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27812 </UL><P>
27813 <End of help on this topic>
27814 </BODY>
27815 </HTML>
27816 ====== h_config_incoming_checking_recent ======
27817 <HTML>
27818 <HEAD>
27819 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></TITLE>
27820 </HEAD>
27821 <BODY>
27822 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></H1>
27824 This option has no effect unless the feature
27825 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
27826 is set, which in turn has no effect unless
27827 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
27828 is set.
27829 <P>
27830 When incoming folder checking is turned on the default is to display
27831 the number of unseen messages in each folder.
27832 More precisely, it is the number of undeleted unseen messages.
27833 Using this option you may display the number of recent messages instead
27834 of the number of unseen messages.
27835 A message is only counted as recent if this is the first session to
27836 see it, so the recent count might be less than the unseen count.
27837 The difference between the two would be accounted for by the unseen messages
27838 in the folder which were there previously but have not been looked at yet.
27839 <P>
27840 If you simultaneously run more than one email client at a time
27841 (for example, you run more than one Alpine in parallel) then turning
27842 this feature on can cause some confusion.
27843 The confusion stems from the fact that each message is only considered to be
27844 recent in one session.
27845 That means that the counts of new messages may be different in the two
27846 Alpines running side by side, because each incoming message will only be
27847 counted as recent in one of the two sessions.
27848 <P>
27849 You may also display the total number of messages
27850 in each folder by using the
27851 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
27852 option.
27853 <P>
27854 <UL>
27855 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27856 </UL><P>
27857 <End of help on this topic>
27858 </BODY>
27859 </HTML>
27860 ====== h_config_attach_in_reply ======
27861 <HTML>
27862 <HEAD>
27863 <TITLE>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></TITLE>
27864 </HEAD>
27865 <BODY>
27866 <H1>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></H1>
27868 This feature controls an aspect of Alpine's Reply command. If set, any MIME
27869 attachments that were part of the original message will automatically be
27870 included in the Reply.
27871 <P>
27872 <End of help on this topic>
27873 </BODY>
27874 </HTML>
27875 ====== h_config_include_header =====
27876 <HTML>
27877 <HEAD>
27878 <TITLE>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></TITLE>
27879 </HEAD>
27880 <BODY>
27881 <H1>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></H1>
27883 This feature controls an aspect of Alpine's Reply command. If set, and the
27884 original message is being included in the reply, then headers from that
27885 message will also be part of the reply.
27886 <P>
27887 <End of help on this topic>
27888 </HEAD>
27889 </HTML>
27890 ====== h_config_sig_at_bottom =====
27891 <HTML>
27892 <HEAD>
27893 <TITLE>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></TITLE>
27894 </HEAD>
27895 <BODY>
27896 <H1>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></H1>
27898 This feature controls an aspect of Alpine's Reply command. If this feature
27899 is set, and the original message is being included in the reply, then the
27900 contents of your signature file (if any) will be inserted after the included
27901 message.
27902 <P>
27903 This feature does not affect the results of a Forward command.
27904 <P>
27905 <End of help on this topic>
27906 </BODY>
27907 </HTML>
27908 ====== h_config_sigdashes =====
27909 <HTML>
27910 <HEAD>
27911 <TITLE>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></TITLE>
27912 </HEAD>
27913 <BODY>
27914 <H1>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></H1>
27916 This feature enables support for the common USENET news convention
27917 of preceding a message signature with the special line consisting of
27918 the three characters "-- " (i.e., dash, dash, and space).
27920 <P>
27921 When enabled and a
27922 "<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>" exists,
27923 Alpine will insert the special line before including the file's text (unless
27924 the special line already exists somewhere in the file's text).
27926 <P>
27927 In addition, when you Reply or Followup to a message containing one of
27928 these special lines and choose to include its text, Alpine will observe
27929 the convention of not including text beyond the special line in your
27930 reply.
27931 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
27932 mode is enabled and turned on, then Alpine <EM>will</EM>
27933 include the text beyond the special line regardless of the setting of
27934 this feature.
27936 <P>
27937 See also "<a href="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>"
27938 for a related feature.
27940 <P>
27941 <UL>
27942 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27943 </UL><P>
27944 <End of help on this topic>
27945 </BODY>
27946 </HTML>
27947 ====== h_config_new_thread_blank_subject =====
27948 <HTML>
27949 <HEAD>
27950 <TITLE>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></TITLE>
27951 </HEAD>
27952 <BODY>
27953 <H1>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></H1>
27955 When this feature is enabled (the default) Alpine will create a new thread
27956 every time that the subject line becomes empty at any time during composition.
27958 <P>
27959 This behavior is particularly useful in case you are replying to a message.
27960 Replying to a message causes the message to be in the same thread than the
27961 original message that is being replied to. However, many authors want to create
27962 a new message (in a different thread) while replying to a message, and they do
27963 this by changing the full subject, by first deleting the original subject and
27964 typing the new subject of the current message.
27966 <P>
27967 Enabling this feature causes that any time that the subject is deleted, the
27968 message being composed will be considered the first message of a new thread.
27970 <P>
27971 <UL>
27972 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27973 </UL><P>
27974 <End of help on this topic>
27975 </BODY>
27976 </HTML>
27977 ====== h_config_strip_sigdashes =====
27978 <HTML>
27979 <HEAD>
27980 <TITLE>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></TITLE>
27981 </HEAD>
27982 <BODY>
27983 <H1>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></H1>
27985 This feature doesn't do anything if the feature
27986 "<A HREF="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></A>" is turned on.
27987 However, if the "<!--#echo var="FEAT_enable-sigdashes"-->" feature is not turned on,
27988 then turning on this feature enables support for the convention
27989 of not including text beyond the sigdashes line when Replying or Following
27990 up to a message and including the text of that message.
27991 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
27992 mode is enabled and turned on, then Alpine <EM>will</EM>
27993 include the text beyond the special line regardless of the setting of
27994 this feature.
27995 <P>
27996 In other words, this is a way to turn on the signature stripping behavior
27997 without also turning on the dashes-adding behavior.
27998 <P>
27999 <UL>
28000 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28001 </UL><P>
28002 <End of help on this topic>
28003 </BODY>
28004 </HTML>
28005 ====== h_config_forward_as_attachment =====
28006 <HTML>
28007 <HEAD>
28008 <TITLE>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></TITLE>
28009 </HEAD>
28010 <BODY>
28011 <H1>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></H1>
28013 This feature affects the way forwarded message text is handled. When set, rather than
28014 include the text of the forwarded message below any additional text you provide in the
28015 composer, the forwarded message is attached in its entirety to the message you send.
28016 <P>
28017 This is useful in that it keeps the text you provide in the composer distinct from the
28018 text of the forwarded message. Similarly, it allows the recipient to
28019 conveniently operate on the forwarded message. For example, they might reply directly to
28020 the sender of the forwarded message, or process it as part of a spam report.
28021 <UL>
28022 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28023 </UL><P>
28024 <End of help on this topic>
28025 </BODY>
28026 </HTML>
28027 ====== h_config_preserve_field =====
28028 <HTML>
28029 <HEAD>
28030 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></TITLE>
28031 </HEAD>
28032 <BODY>
28033 <H1>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></H1>
28035 This feature affects Alpine's behavior when one replies to a message.
28036 When you receive a message, some or all of the recipients of the message
28037 have been added to the To: and Cc: fields. If you reply to such message,
28038 and this feature is disabled, then the original sender of the message is
28039 added to the To: field, and all other recipients are added to the Cc:
28040 field, while your address is added to the From: field.
28042 <P>
28043 However, if this feature is enabled, then Alpine will preserve the
28044 original fields as sent in the original message, so the Cc: and To:
28045 fields will be preserved. The sender's address will be added to the To:
28046 field, while your address is added to the From: field.
28048 <P>
28049 The behavior of this feature is that replies to all messages will behave
28050 in the way described above. If you only intend this to happen on a per
28051 message basis, then keep this feature disabled, and when replying to a
28052 message you will see a new option in the menu for the "Reply to all
28053 recipients?" question. In this case, pressing "p" will
28054 make Alpine toggle its question so you can preserve the To: and Cc:
28055 fields for that message only.
28057 <UL>
28058 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28059 </UL><P>
28060 <End of help on this topic>
28061 </BODY>
28062 </HTML>
28063 ====== h_config_sub_lists =====
28064 <HTML>
28065 <HEAD>
28066 <TITLE>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></TITLE>
28067 </HEAD>
28068 <BODY>
28069 <H1>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></H1>
28071 This feature affects the subcommands available when Saving,
28072 or when Opening a new folder. If set, the subcommand ^X ListMatches will be
28073 available. This command allows you to type in a substring of the folder
28074 you are looking for and when you type ^X it will display all folders
28075 that contain that substring in their names.
28076 This feature is set by default.
28078 <P>
28079 <End of help on this topic>
28080 </BODY>
28081 </HTML>
28082 ====== h_config_scramble_message_id =====
28083 <HTML>
28084 <HEAD>
28085 <TITLE>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></TITLE>
28086 </HEAD>
28087 <BODY>
28088 <H1>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></H1>
28090 Normally the Message-ID header that Alpine generates when sending a message
28091 contains the name of the computer from which the message is being sent.
28092 Some believe that this hostname could be used by spammers or could
28093 be used by others for nefarious purposes.
28094 If this feature is set, that name will be transformed with a simple
28095 Rot13 transformation.
28096 The result will still have the correct syntax for a Message-ID but the
28097 part of the MessageID that is often a domain name will not be an actual
28098 domain name because the letters will be scrambled.
28099 <P>
28100 It is possible (but unlikely?) that some spam detection
28101 software will use that as a reason to reject the mail as spam.
28102 It has also been reported that some spam detection software uses the
28103 fact that there are no dots after the "@" as a reason to reject
28104 messages.
28105 If your PC-Alpine Message-ID is using a name without a dot that is because
28106 that is what Windows thinks is your "Full computer name".
28107 The method used to set this varies from one type of Windows to another but
28108 check under Settings -> Control Panel -> System and
28109 look for Network Identification or Computer Name or something similar.
28110 How to set it is beyond the scope of Alpine.
28112 <P>
28113 <End of help on this topic>
28114 </BODY>
28115 </HTML>
28116 ====== h_downgrade_multipart_to_text =====
28117 <HTML>
28118 <HEAD>
28119 <TITLE>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></TITLE>
28120 </HEAD>
28121 <BODY>
28122 <H1>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></H1>
28124 <P>
28125 This feature affects Alpine's behavior when sending mail. Internet
28126 standards require Alpine to translate all non-ASCII characters in
28127 messages that it sends using MIME encoding. This encoding can be
28128 ostensibly broken for recipients if any agent between Alpine and the
28129 recipient, such as an email list expander, appends text to the
28130 message, such as list information or advertising. When sending such
28131 messages Alpine attempts to protect such encoding by placing extra
28132 MIME boundaries around the message text.
28133 <P>
28134 These extra boundaries are invisible to recipients that
28135 use MIME-aware email programs (the vast majority). However, if
28136 you correspond with users of email programs that are not MIME-aware,
28137 or do not handle the extra boundaries gracefully, you can
28138 use this feature to prevent Alpine from including the extra
28139 MIME information. Of course, it will increase the likelihood
28140 that non-ASCII text you send may appear corrupt to the recipient.
28141 <P>
28142 <End of help on this topic>
28143 </BODY>
28144 </HTML>
28145 ====== h_config_show_sort =====
28146 <HTML>
28147 <HEAD>
28148 <TITLE>FEATURE: <!--#echo var="FEAT_show-sort"--></TITLE>
28149 </HEAD>
28150 <BODY>
28151 <H1>FEATURE: <!--#echo var="FEAT_show-sort"--></H1>
28153 If this feature is set and there is sufficient space on the screen,
28154 a short indication of the current sort order will be
28155 added in the titlebar (the top line on the screen), before the name
28156 of the folder.
28157 For example, with the default Arrival sort in effect,
28158 the display would have the characters
28160 <P><CENTER>[A]</CENTER><P>
28162 added between the title of the screen and the folder name.
28163 The letters are the same as the letters you may type to manually
28164 sort a folder with the SortIndex command ($).
28165 The letters in the table below are the ones that may show
28166 up in the titlebar line.
28167 <P>
28168 <TABLE>
28169 <TR> <TD> A </TD> <TD> <EM>A</EM>rrival </TD> </TR>
28170 <TR> <TD> S </TD> <TD> <EM>S</EM>ubject </TD> </TR>
28171 <TR> <TD> F </TD> <TD> <EM>F</EM>rom </TD> </TR>
28172 <TR> <TD> T </TD> <TD> <EM>T</EM>o </TD> </TR>
28173 <TR> <TD> C </TD> <TD> <EM>C</EM>c </TD> </TR>
28174 <TR> <TD> D </TD> <TD> <EM>D</EM>ate </TD> </TR>
28175 <TR> <TD> Z </TD> <TD> si<EM>Z</EM>e </TD> </TR>
28176 <TR> <TD> O </TD> <TD> <EM>O</EM>rderedsubject </TD> </TR>
28177 <TR> <TD> E </TD> <TD> scor<EM>E</EM> </TD> </TR>
28178 <TR> <TD> H </TD> <TD> t<EM>H</EM>read </TD> </TR>
28179 </TABLE>
28180 <P>
28181 If the sort order is Reversed, the letter above will be preceded by the letter
28182 "R", for example
28184 <P><CENTER>[RS]</CENTER><P>
28186 means that a Reverse Subject sort is in effect.
28187 For the case where the sort is in Reverse Arrival order, the "A" is
28188 left out, and just an "R" is shown.
28190 <P><CENTER>[R]</CENTER>
28192 <P>
28193 <End of help on this topic>
28194 </BODY>
28195 </HTML>
28196 ====== h_config_disable_reset_disp =====
28197 <HTML>
28198 <HEAD>
28199 <TITLE>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></TITLE>
28200 </HEAD>
28201 <BODY>
28202 <H1>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></H1>
28204 UNIX Alpine only.
28205 <P>
28206 This feature affects Alpine's behavior when using
28207 <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>.
28208 Normally, before the display filter is run, the terminal mode is reset
28209 to what it was before you started Alpine.
28210 This may be necessary if the filter requires the use of the terminal.
28211 For example, it may need to interact with you.
28212 If you set this feature, then the terminal mode will not be reset.
28213 One thing that turning on this feature should fix is the coloring of
28214 <A HREF="h_config_quote_color">quoted text</A> in the message view, which
28215 breaks because the terminal reset resets the color state of the terminal.
28217 <P>
28218 <End of help on this topic>
28219 </BODY>
28220 </HTML>
28221 ====== h_config_disable_sender =====
28222 <HTML>
28223 <HEAD>
28224 <TITLE>FEATURE: <!--#echo var="FEAT_disable-sender"--></TITLE>
28225 </HEAD>
28226 <BODY>
28227 <H1>FEATURE: <!--#echo var="FEAT_disable-sender"--></H1>
28229 This feature affects Alpine's generation of the "Sender:" or
28230 <A HREF="h_config_use_sender_not_x">"X-X-Sender"</A>
28231 header fields.
28232 By default, Alpine will generate such a header in situations where the
28233 username or domain are not the same as
28234 the "From:" header on the message.
28235 With this feature set,
28236 no "Sender:" or "X-X-Sender" header will be generated.
28237 This may be desirable on a system that is virtually hosting many domains,
28238 and the sysadmin has other methods available for tracking a message to
28239 its originator.
28240 <P>
28241 See also <A HREF="h_config_allow_chg_from">"<!--#echo var="FEAT_allow-changing-from"-->"</A>.
28243 <P>
28244 <End of help on this topic>
28245 </BODY>
28246 </HTML>
28247 ====== h_config_use_sender_not_x =====
28248 <HTML>
28249 <HEAD>
28250 <TITLE>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></TITLE>
28251 </HEAD>
28252 <BODY>
28253 <H1>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></H1>
28255 Normally Alpine adds a header line
28256 labeled "X-X-Sender", if the sender is
28257 different from the From: line.
28258 The standard specifies that this header
28259 line should be labeled "Sender", not "X-X-Sender".
28260 Setting this feature causes
28261 "Sender" to be used instead of "X-X-Sender".
28262 <P>
28263 See also <A HREF="h_config_disable_sender">"<!--#echo var="FEAT_disable-sender"-->"</A>.
28265 <P>
28266 <End of help on this topic>
28267 </BODY>
28268 </HTML>
28269 ====== h_config_use_fk =====
28270 <HTML>
28271 <HEAD>
28272 <TITLE>FEATURE: <!--#echo var="FEAT_use-function-keys"--></TITLE>
28273 </HEAD>
28274 <BODY>
28275 <H1>FEATURE: <!--#echo var="FEAT_use-function-keys"--></H1>
28277 This feature specifies that Alpine will respond to function keys instead of
28278 the normal single-letter commands. In this mode, the key menus at the
28279 bottom of each screen will show function key designations instead of the
28280 normal mnemonic key.
28282 <P>
28283 <End of help on this topic>
28284 </BODY>
28285 </HTML>
28286 ====== h_config_cancel_confirm =====
28287 <HTML>
28288 <HEAD>
28289 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></TITLE>
28290 </HEAD>
28291 <BODY>
28292 <H1>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></H1>
28294 This feature affects what happens when you type ^C to cancel a composition.
28295 By default, if you attempt to cancel a composition by typing ^C, you will be
28296 asked to confirm the cancellation by typing a "C"
28297 for <EM>C</EM>onfirm.
28298 It logically ought to be a "Y" for <EM>Y</EM>es, but that is
28299 risky because the "^C Y" needed to cancel a message
28300 is close (on the keyboard) to the "^X Y" needed to send a message.
28301 <P>
28302 If this feature is set the confirmation asked for
28303 will be a "<EM>Y</EM>es"
28304 instead of a "<EM>C</EM>onfirm" response.
28306 <P>
28307 <End of help on this topic>
28308 </BODY>
28309 </HTML>
28310 ====== h_config_compose_maps_del =====
28311 <HTML>
28312 <HEAD>
28313 <TITLE>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></TITLE>
28314 </HEAD>
28315 <BODY>
28316 <H1>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></H1>
28318 This feature affects the behavior of the DELETE key.
28319 If set, Delete will be equivalent to ^D, and delete
28320 the current character. Normally Alpine defines the Delete key
28321 to be equivalent to ^H, which deletes the <EM>previous</EM>
28322 character.
28324 <P>
28325 <End of help on this topic>
28326 </BODY>
28327 </HTML>
28328 ====== h_config_compose_bg_post =====
28329 <HTML>
28330 <HEAD>
28331 <TITLE>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></TITLE>
28332 </HEAD>
28333 <BODY>
28334 <H1>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></H1>
28336 This feature affects the behavior of Alpine's mail sending. If set, this
28337 feature enables a subcommand in the composer's "Send?" confirmation
28338 prompt. The subcommand allows you to tell Alpine to handle the actual
28339 posting in the background. While this feature usually allows posting
28340 to appear to happen very fast, it has no affect on the actual delivery
28341 time it takes a message to arrive at its destination.
28343 <P>
28344 Please Note:
28345 <OL>
28346 <LI>This feature will have no effect if the feature
28347 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A>
28348 is set.
28349 <LI>This feature isn't supported on all systems. All DOS and Windows,
28350 as well as several Unix ports, do not recognize this feature.
28351 <LI>Error handling is significantly different when this feature is
28352 enabled. Any message posting failure results in the message
28353 being appended to your "Interrupted" mail folder. When you
28354 type the <A HREF="h_common_compose">C</A>ompose command,
28355 Alpine will notice this folder and
28356 offer to extract any messages contained. Upon continuing a
28357 failed message, Alpine will display the nature of the failure
28358 in the status message line.
28359 <LI> <EM>WARNING</EM>: Under extreme conditions, it is possible
28360 for message data to
28361 get lost. <EM>Do</EM> <EM>not</EM> enable this feature
28362 if you typically run close to any sort of disk-space limits or quotas.
28363 </OL>
28364 <P>
28365 <End of help on this topic>
28366 </BODY>
28367 </HTML>
28368 ====== h_config_compose_dsn =====
28369 <HTML>
28370 <HEAD>
28371 <TITLE>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></TITLE>
28372 </HEAD>
28373 <BODY>
28374 <H1>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></H1>
28376 This feature affects the behavior of Alpine's mail sending. If set, this
28377 feature enables a subcommand in the composer's "Send?" confirmation
28378 prompt. The subcommand allows you to tell Alpine to request the type of
28379 Delivery Status Notification (DSN) that you would like. Most users will
28380 be happy with the default, and need not enable this feature.
28381 <P>
28382 If the feature
28383 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
28384 then this feature has no effect and the type of DSN is not selectable.
28386 <P>
28387 Turning on this feature and then turning on the DSNOpts from the send
28388 prompt reveals four on-off toggles at the bottom of the screen.
28389 The "X" command toggles between NoErrRets and ErrRets. NoErrRets requests
28390 that no notification be returned to you, even if there is a delivery
28391 failure. The "D" key toggles between Delay and NoDelay. This tells the
28392 server that you are willing (or not) to receive delay notifications, which
28393 happen when there is an unusual delay at some mail server (in that mail
28394 server's opinion). The "S" key toggles between Success and NoSuccess.
28395 Success requests that you be sent a DSN message when the message is
28396 successfully delivered to the recipients mailbox. Setting NoErrRets will
28397 automatically turn off Delay and Success notification, and will flip the
28398 toggles to show that. Similarly, turning on Delay and/or Success will
28399 automatically toggle the "X" key to ErrRets. The fourth command, the
28400 "H" key, toggles between RetHdrs and RetFull. RetFull requests that
28401 the full message be returned in any failed DSN. RetHdrs requests that
28402 only the headers be returned in any failed DSN. Notice that this command
28403 applies only to failed delivery status reports. For delay or success
28404 reports, the full message is never returned, only the headers are returned.
28406 <P>
28407 If you don't enable the DSN feature or if you don't turn it on for a
28408 particular message, the default is that you will be notified about failures,
28409 you might be notified about delays, and you won't be notified about
28410 successes. You will usually receive the full message back when there is
28411 a failure.
28413 <P>
28414 If you turn on the DSNOpts the default is to return as much information as
28415 possible to you. That is, by default, the Success and Delay options are
28416 turned on and the full message will be returned on failure.
28418 <P>
28419 The sending prompt will display the current DSN request (if any) in a
28420 shorthand form. It will be:
28422 <P><CENTER>[Never]</CENTER>
28424 <P>
28425 if you have requested NoErrRets. Otherwise, it will look something like:
28427 <P><CENTER>[FDS-Hdrs]</CENTER>
28429 <P>
28430 The "F" will always be there, indicating that you will be notified
28431 of failures. (Alpine doesn't provide a way to request no failure notification
28432 and at the same time request either success or delay notification. The only
28433 way to request no failure notifications is to request no notifications at
28434 all with NoErrRets.) The "D" and/or "S" will be present if you have
28435 requested Delay and/or Success notification. If one of those is missing,
28436 that means you are requesting no notification of the corresponding type.
28437 After the dash it will say either Hdrs or Full. Hdrs means to return only
28438 the headers and Full means to return the full message (applies to
28439 failure notifications only).
28441 <P>
28442 NOTE: This feature relies on your system's mail transport agent or
28443 configured
28444 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
28445 having the negotiation mechanism introduced in
28446 "Extended SMTP" (ESMTP) and the specific extension called
28447 "Delivery Status Notification" (DSN). If the mail tranport agent you
28448 are using doesn't support DSN, a short warning will be shown to you on
28449 the message line at the bottom of the screen after you send your message,
28450 but your message will have been sent anyway.
28452 <P>
28453 Note that DSNs don't provide a mechanism to request read receipts. That
28454 is, if you request notification on success you are notified when the
28455 message is delivered to the mailbox, not when the message is read.
28457 <P>
28458 ESMTP allows for graceful migration to upgraded mail transfer agents, but
28459 it is possible that this feature might cause problems for some servers.
28461 <P>
28462 <End of help on this topic>
28463 </BODY>
28464 </HTML>
28465 ====== h_config_auto_zoom =====
28466 <HTML>
28467 <HEAD>
28468 <TITLE>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></TITLE>
28469 </HEAD>
28470 <BODY>
28471 <H1>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></H1>
28473 This feature affects the behavior of the Select command.
28474 If set, the select command will automatically perform a zoom
28475 after the select is complete.
28476 This feature is set by default.
28477 <P>
28478 Some related help topics are
28479 <UL>
28480 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28481 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28482 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28483 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
28484 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
28485 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28486 </UL>
28488 <P>
28489 <End of help on this topic>
28490 </BODY>
28491 </HTML>
28492 ====== h_config_auto_unzoom =====
28493 <HTML>
28494 <HEAD>
28495 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></TITLE>
28496 </HEAD>
28497 <BODY>
28498 <H1>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></H1>
28500 This feature affects the behavior of the Apply command. If set, and if
28501 you are currently looking at a Zoomed Index view of selected messages,
28502 the Apply command will do the operation you specify, but then will
28503 implicitly do an "UnZoom", so that you will automatically be back in
28504 the normal Index view after the Apply.
28505 This feature is set by default.
28507 <P>
28508 Some related help topics are
28509 <UL>
28510 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28511 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28512 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28513 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
28514 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
28515 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28516 </UL>
28517 <P>
28518 <End of help on this topic>
28519 </BODY>
28520 </HTML>
28521 ====== h_config_auto_unselect =====
28522 <HTML>
28523 <HEAD>
28524 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></TITLE>
28525 </HEAD>
28526 <BODY>
28527 <H1>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></H1>
28529 This feature affects the behavior of the Apply command. If set,
28530 the Apply command will do the operation you specify, but then will
28531 implicitly do an "UnSelect All", so that you will automatically be back in
28532 the normal Index view after the Apply.
28534 <P>
28535 Some related help topics are
28536 <UL>
28537 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28538 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28539 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28540 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
28541 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
28542 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28543 </UL>
28544 <P>
28545 <End of help on this topic>
28546 </BODY>
28547 </HTML>
28548 ====== h_config_fast_recent =====
28549 <HTML>
28550 <HEAD>
28551 <TITLE>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></TITLE>
28552 </HEAD>
28553 <BODY>
28554 <H1>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></H1>
28556 This feature controls the behavior of the TAB key when traversing folders
28557 in the optional
28558 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28559 collection or in optional <!--#echo var="VAR_news-collections"-->.
28561 <P>
28562 When the TAB
28563 (<A HREF="h_common_nextnew">NextNew</A>)
28564 key is pressed, the default behavior is to
28565 explicitly examine the status of the folder for the number of recent
28566 messages (messages delivered since the last time it was viewed).
28567 Depending on the size and number of messages in the folder, this test
28568 can be time consuming.
28570 <P>
28571 Enabling this feature will cause Alpine to only test for the existence of
28572 any recent messages rather than to obtain the count. This is much faster
28573 in many cases. The downside is that you're not given the number of recent
28574 messages when prompted to view the next folder.
28575 If the feature
28576 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
28577 is turned on, then the present feature will have no effect.
28579 <P>
28580 <UL>
28581 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28582 </UL><P>
28583 <End of help on this topic>
28584 </BODY>
28585 </HTML>
28586 ====== h_config_arrow_nav =====
28587 <HTML>
28588 <HEAD>
28589 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></TITLE>
28590 </HEAD>
28591 <BODY>
28592 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></H1>
28594 This feature controls the behavior of the left and right arrow keys.
28595 If set, the left and right arrow keys will operate like the usual
28596 navigation keys < and >.
28597 This feature is set by default.
28599 <P>
28600 If you set this feature, and do not like the changed behavior of the up/down
28601 arrow
28602 keys when navigating through the FOLDER LIST screen --
28603 <B>first</B> from column to column, if more than one folder is
28604 displayed per row,
28605 and <B>then</B> from row to row -- you may either also wish to set the feature
28606 "<A HREF="h_config_relaxed_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></A>",
28607 "<A HREF="h_config_single_list"><!--#echo var="FEAT_single-column-folder-list"--></A>", or
28608 use the ^P/^N (instead of up/down arrow) keys to move up/down the list of
28609 folders in each column.
28610 <P>
28611 <UL>
28612 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28613 </UL><P>
28614 <End of help on this topic>
28615 </BODY>
28616 </HTML>
28617 ====== h_config_relaxed_arrow_nav =====
28618 <HTML>
28619 <HEAD>
28620 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></TITLE>
28621 </HEAD>
28622 <BODY>
28623 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></H1>
28625 This feature controls the behavior of the left, right, up and down
28626 arrow keys in the FOLDER LIST screen when the "<A
28627 HREF="h_config_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation"--></A>" feature is
28628 set.
28629 This feature is set by default.
28631 <P>
28633 When this feature is set, the left and right
28634 arrow keys in the FOLDER LIST screen
28635 move the highlight bar to the left or right, and the up and
28636 down arrows move it up or down.
28638 <P>
28639 When the "<!--#echo var="FEAT_enable-arrow-navigation"-->" feature is set and this
28640 feature is not set;
28641 the left and right arrow keys in the Folder List screen strictly
28642 track the commands bound to the '<' and '>' keys, and the up
28643 and down arrow keys move the highlight bar to the previous and next
28644 folder or directory name.
28646 <P>
28647 <UL>
28648 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28649 </UL><P>
28650 <End of help on this topic>
28651 </BODY>
28652 </HTML>
28653 ====== h_config_alt_compose_menu =====
28654 <HTML>
28655 <HEAD>
28656 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></TITLE>
28657 </HEAD>
28658 <BODY>
28659 <H1>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></H1>
28661 This feature controls the menu that is displayed when Compose is selected.
28662 If set, a list of options will be presented, with each option representing
28663 the type of composition that could be used. This feature is most useful for
28664 users who want to avoid being prompted with each option separately, or who
28665 want to avoid the checking of remote postponed or form letter folders.
28666 The possible types of composition are:
28668 <P>
28669 New, for starting a new composition. Note that if New is selected and roles
28670 are set, roles are checked for matches and applied according to the setting
28671 of the matching role.
28673 <P>
28674 Interrupted, for continuing an interrupted composition. This option is only
28675 offered if an interrupted message folder is detected.
28677 <P>
28678 Postponed, for continuing postponed compositions. This option is offered
28679 if a <!--#echo var="VAR_postponed-folder"--> is set in the config REGARDLESS OF whether or not
28680 the postponed folder actually exists. This option is especially handy
28681 for avoiding having to check for the existence of a remote postponed folder.
28683 <P>
28684 Form, for using form letters. This option is offered if the <!--#echo var="VAR_form-letter-folder"-->
28685 is set in the config, and is not checked for existence for reasons similar
28686 to those explained by the postponed option.
28688 <P>
28689 setRole, for selecting a role to apply to a composition.
28691 <P>
28692 <End of help on this topic>
28693 </BODY>
28694 </HTML>
28695 ====== h_config_alt_role_menu =====
28696 <HTML>
28697 <HEAD>
28698 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></TITLE>
28699 </HEAD>
28700 <BODY>
28701 <H1>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></H1>
28703 Normally the <A HREF="h_common_role">Role Command</A> allows you to choose
28704 a role and compose a new message using that role.
28705 When this feature is set, the role command will first ask whether you want to
28706 Compose a new message, Forward the current message, Reply to the
28707 current message, or Bounce the current message.
28708 If you are not in the MESSAGE INDEX and are not viewing a message,
28709 then there is no current message and the question will be skipped.
28710 After you have chosen to Compose, Forward, Reply, or Bounce you will
28711 then choose the role to be used.
28712 <P>
28713 When Bouncing the "Set From" address is used for the
28714 Resent-From header, the "Set Fcc" value is used for the Fcc
28715 provided that the option
28716 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A> is turned on,
28717 and the "Use SMTP Server" value is used for the SMTP server, if
28718 set.
28719 Other actions of the role are ignored when Bouncing.
28721 <P>
28722 <End of help on this topic>
28723 </BODY>
28724 </HTML>
28725 ====== h_config_always_spell_check =====
28726 <HTML>
28727 <HEAD>
28728 <TITLE>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></TITLE>
28729 </HEAD>
28730 <BODY>
28731 <H1>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></H1>
28732 <P>
28733 When this feature is set, every composed message will be spell-checked before
28734 being sent.
28735 <P>
28736 <End of help on this topic>
28737 </BODY>
28738 </HTML>
28739 ====== h_config_quell_asterisks =====
28740 <HTML>
28741 <HEAD>
28742 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></TITLE>
28743 </HEAD>
28744 <BODY>
28745 <H1>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></H1>
28746 <P>
28747 When you are running Alpine you will sometimes be asked for a password
28748 in a prompt on the third line from the bottom of the screen.
28749 Normally each password character you type will cause an asterisk to echo
28750 on the screen. That gives you some feedback to know that your typing is
28751 being recognized.
28752 There is a very slight security risk in doing it this way because someone
28753 watching over your shoulder might be able to see how many characters there
28754 are in your password.
28755 If you'd like to suppress the echoing of the asterisks set this feature.
28756 <P>
28757 <End of help on this topic>
28758 </BODY>
28759 </HTML>
28760 ====== h_config_quell_flowed_text =====
28761 <HTML>
28762 <HEAD>
28763 <TITLE>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></TITLE>
28764 </HEAD>
28765 <BODY>
28766 <H1>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></H1>
28767 <P>
28768 Alpine generates flowed text where possible.
28769 The method for generating flowed text is defined by
28770 <A HREF="http://www.ietf.org/rfc/rfc3676.txt">RFC 3676</A>,
28771 the benefit of doing so is
28772 to send message text that can properly be viewed both on normal width displays
28773 and on displays with smaller or larger than normal screen widths.
28774 With flowed text, a space at the end of a line tells the receiving mail
28775 client that the following line belongs to the same paragraph.
28776 Quoted text will also be affected, with only the innermost
28777 level of ">" quoting being followed by a space.
28778 However, if you have changed the
28779 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
28780 so that it is not equal to the default value of "> ", then
28781 quoted text will not be flowed.
28782 For this reason, we recommend that you leave your
28783 "<!--#echo var="VAR_reply-indent-string"-->" set to the default.
28784 <P>
28785 This feature turns off the generation of flowed text, as it might be
28786 desired to more tightly control how a message is displayed on the receiving end.
28787 <P>
28788 If this feature is <EM>not</EM> set, you can control on a message by message
28789 basis whether or not flowed text is generated.
28790 You do this by typing ^V at the Send confirmation prompt that you get
28791 after typing ^X to send a message.
28792 ^V is a toggle that turns flowing off and back on if typed again.
28793 If for some reason flowing cannot be done on a particular message, then the
28794 ^V command will not be available.
28795 This would be the case, for example, if this feature was set, or if your
28796 "<!--#echo var="VAR_reply-indent-string"-->" was set to a non-default value.
28797 If the feature
28798 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
28799 then the opportunity to control on a message by message basis
28800 whether or not flowed text is generated is lost.
28801 <P>
28802 When this feature is not set and you have typed ^V to turn off flowing,
28803 the Send confirmation prompt will change to look like
28804 <P>
28805 <CENTER><SAMP>Send message (not flowed)?</SAMP></CENTER>
28806 <P>
28807 <A HREF="h_config_strip_ws_before_send">"<!--#echo var="FEAT_strip-whitespace-before-send"-->"</A> will
28808 also turn off the sending of flowed text messages, but it differs in that
28809 it also trims all trailing white space from a message before sending it.
28810 <P>
28811 If alternate editors are used extensively, be aware that a message will still
28812 be sent flowed if this feature is unset. In most cases this will be fine,
28813 but if the editor has a "flowed text" mode, it would be best to
28814 use that.
28815 <P>
28816 <End of help on this topic>
28817 </BODY>
28818 </HTML>
28819 ====== h_config_strip_ws_before_send =====
28820 <HTML>
28821 <HEAD>
28822 <TITLE>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></TITLE>
28823 </HEAD>
28824 <BODY>
28825 <H1>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></H1>
28826 <P>
28827 By default, trailing whitespace is not stripped from
28828 a message before sending. Trailing whitespace should have no effect on an
28829 email message, and in flowed text can aid in delimiting paragraphs.
28830 However, the old behavior of stripping trailing whitespace was in place
28831 to better deal with older clients that couldn't handle certain types of
28832 text encodings. This feature restores the old behavior
28833 <P>
28834 Trailing whitespace is of aid to flowed-text-formatted messages, which are
28835 generated by default but can be turned off via the
28836 <A HREF="h_config_quell_flowed_text">"<!--#echo var="FEAT_quell-flowed-text"-->"</A> feature.
28837 <!--#echo var="FEAT_strip-whitespace-before-send"--> also has the effect of turning off sending
28838 of flowed text.
28839 <P>
28840 <End of help on this topic>
28841 </BODY>
28842 </HTML>
28843 ====== h_config_del_from_dot =====
28844 <HTML>
28845 <HEAD>
28846 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></TITLE>
28847 </HEAD>
28848 <BODY>
28849 <H1>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></H1>
28851 This feature controls the behavior of the Ctrl-K command in the composer.
28852 If set, ^K will cut from the current cursor position to the end of the line,
28853 rather than cutting the entire line.
28855 <P>
28856 <End of help on this topic>
28857 </BODY>
28858 </HTML>
28859 ====== h_config_print_index =====
28860 <HTML>
28861 <HEAD>
28862 <TITLE>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></TITLE>
28863 </HEAD>
28864 <BODY>
28865 <H1>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></H1>
28867 This feature controls the behavior of the Print command when in the
28868 MESSAGE INDEX screen. If set, the print command will give you a prompt
28869 asking if you wish to print the message index, or the currently highlighted
28870 message. If not set, the message will be printed.
28872 <P>
28873 <End of help on this topic>
28874 </BODY>
28875 </HTML>
28876 ====== h_config_allow_talk =====
28877 <HTML>
28878 <HEAD>
28879 <TITLE>FEATURE: <!--#echo var="FEAT_allow-talk"--></TITLE>
28880 </HEAD>
28881 <BODY>
28882 <H1>FEATURE: <!--#echo var="FEAT_allow-talk"--></H1>
28884 UNIX Alpine only.
28885 <P>
28886 By default, permission for others to "talk" to your terminal is turned
28887 off when you are running Alpine. When this feature is set, permission is
28888 instead turned on. If enabled, you may see unexpected messages in the
28889 middle of your Alpine screen from someone attempting to contact you via the
28890 "talk" program.
28892 <P>
28893 NOTE: The "talk" program has nothing to do with Alpine or email. The
28894 talk daemon on your system will attempt to print a message on your screen
28895 when someone else is trying to contact you. If you wish to see these
28896 messages while you are running Alpine, you should enable this feature.
28898 <P>
28899 If you do enable this feature and see a "talk" message, you must
28900 suspend or quit Alpine before you can respond.
28902 <P>
28903 <End of help on this topic>
28904 </BODY>
28905 </HTML>
28906 ====== h_config_send_filter_dflt =====
28907 <HTML>
28908 <HEAD>
28909 <TITLE>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></TITLE>
28910 </HEAD>
28911 <BODY>
28912 <H1>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></H1>
28913 If you have <A HREF="h_config_sending_filter">"<!--#echo var="VAR_sending-filters"-->"</A>
28914 configured, setting this feature will cause
28915 the first filter in the <!--#echo var="VAR_sending-filters"--> list to be offered as the default
28916 instead of unfiltered, the usual default.
28917 <P>
28918 <UL>
28919 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28920 </UL><P>
28921 <End of help on this topic>
28922 </BODY>
28923 </HTML>
28924 ====== h_config_custom_print =====
28925 <HTML>
28926 <HEAD>
28927 <TITLE>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></TITLE>
28928 </HEAD>
28929 <BODY>
28930 <H1>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></H1>
28932 When this feature is set, the print command will have an additional
28933 subcommand called "C CustomPrint". If selected, you will have
28934 the opportunity to enter any system print command --instead of being
28935 restricted to using those that have been previously configured in the
28936 printer setup menu.
28937 <P>
28939 <End of help on this topic>
28940 </BODY>
28941 </HTML>
28942 ====== h_config_enable_dot_files =====
28943 <HTML>
28944 <HEAD>
28945 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></TITLE>
28946 </HEAD>
28947 <BODY>
28948 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></H1>
28950 When this feature is set, files beginning with dot (".") will be
28951 visible in the file browser. For example, you'll be able to select them
28952 when using the browser to add an attachment to a message.
28953 <P>
28954 <End of help on this topic>
28955 </BODY>
28956 </HTML>
28957 ====== h_config_enable_dot_folders =====
28958 <HTML>
28959 <HEAD>
28960 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></TITLE>
28961 </HEAD>
28962 <BODY>
28963 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></H1>
28965 When this feature is set, folders beginning with dot (".") may be added
28966 and viewed.
28967 <P>
28968 <End of help on this topic>
28969 </BODY>
28970 </HTML>
28971 ====== h_config_ff_between_msgs =====
28972 <HTML>
28973 <HEAD>
28974 <TITLE>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></TITLE>
28975 </HEAD>
28976 <BODY>
28977 <H1>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></H1>
28979 Setting this feature causes a formfeed to be printed between messages when
28980 printing multiple messages (with Apply Print command).
28981 <P>
28982 <End of help on this topic>
28983 </BODY>
28984 </HTML>
28985 ====== h_config_blank_keymenu =====
28986 <HTML>
28987 <HEAD>
28988 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></TITLE>
28989 </HEAD>
28990 <BODY>
28991 <H1>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></H1>
28993 If this feature is set the command key menu that normally appears on the
28994 bottom two lines of the screen will not usually be there. Asking for
28995 help with ^G or ? will cause the key menu to appear instead of causing
28996 the help message to come up. If you want to actually see the help text,
28997 another ^G or ? will show it to you. After the key menu has popped
28998 up with the help key it will remain there for an O for Other command but
28999 disappear if any other command is typed.
29000 <P>
29001 <End of help on this topic>
29002 </BODY>
29003 </HTML>
29004 ====== h_config_enable_mouse =====
29005 <HTML>
29006 <HEAD>
29007 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></TITLE>
29008 </HEAD>
29009 <BODY>
29010 <H1>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></H1>
29012 This feature controls whether or not an X terminal mouse can be used with
29013 Alpine. If set, and the $DISPLAY variable indicates that an X terminal is
29014 being used, the left mouse button on the mouse can be used to select text
29015 or commands.
29016 Clicking on a command at the bottom of the screen will behave as if you had
29017 typed that command.
29018 Clicking on an index line will move the current message highlight to
29019 that line.
29020 Double-clicking on an index line will view the message.
29021 Double-clicking on a link will view the link.
29022 <P>
29023 This type of mouse support will also work in some terminal emulators which are
29024 not actually X terminals, but which have extra code to support the xterm
29025 style mouse.
29026 For those emulators you not only need to turn this feature on but you also
29027 have to set the $DISPLAY environment variable even though it isn't needed
29028 for your terminal.
29029 That will cause Alpine to think that it is an xterm and to properly interpret the
29030 escape sequences sent by the mouse.
29031 <P>
29032 Note: if this feature is set, the behavior of X terminal cut-and-paste is
29033 also modified. It is sometimes possible to hold the shift key down while clicking
29034 left or middle mouse buttons for the normal xterm cut/paste operations.
29035 There is also an Alpine command to toggle this mode on or off.
29036 The command is Ctrl-\ (Control-backslash).
29037 <P>
29038 <End of help on this topic>
29039 </BODY>
29040 </HTML>
29041 ====== h_config_enable_xterm_newmail =====
29042 <HTML>
29043 <HEAD>
29044 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></TITLE>
29045 </HEAD>
29046 <BODY>
29047 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></H1>
29049 This feature controls whether or not Alpine will attempt to announce new
29050 mail arrival when it is running in an X terminal window and that window
29051 is iconified. If set, and the $DISPLAY variable indicates that an X
29052 terminal is being used, Alpine will send appropriate escape sequences to
29053 the X terminal to modify the label on Alpine's icon to indicate that new
29054 mail has arrived. Alpine will also modify the Alpine window's title to
29055 indicate new mail.
29056 See also <a href="h_config_enable_newmail_short_text"><!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>.
29057 <P>
29058 <End of help on this topic>
29059 </BODY></HTML>
29060 ====== h_config_enable_newmail_short_text =====
29061 <HTML>
29062 <HEAD>
29063 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></TITLE>
29064 </HEAD>
29065 <BODY>
29066 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></H1>
29068 This feature controls the text to be displayed in an icon in the event
29069 of a new message arrival. Normally, the message will
29070 be the one that is displayed on the screen. This feature shortens the
29071 message to a count of the number of new messages in brackets. This may be
29072 more useful for those who use the window's title bar in the task bar as a
29073 new mail indicator. This feature is only useful if the
29074 <A HREF="h_config_enable_xterm_newmail"><!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></A>
29075 feature is also set. Like the <!--#echo var="FEAT_enable-newmail-in-xterm-icon"-->
29076 feature, this feature is only relevant when run in an xterm environment.
29077 <P>
29078 <End of help on this topic>
29079 </BODY></HTML>
29080 ====== h_config_copy_to_to_from =====
29081 <HTML>
29082 <HEAD>
29083 <TITLE>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></TITLE>
29084 </HEAD>
29085 <BODY>
29086 <H1>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></H1>
29088 This feature affects the From address used when Replying to a message.
29089 It is probably only useful if you have some
29090 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
29091 defined.
29092 When enabled, it checks to see if any of the addresses in the To or Cc
29093 fields of the message you are replying to is one of your addresses.
29094 If it is, and there is only one of them, then that address is used as
29095 the From address in the message you are composing.
29096 In other words, you will be using a From address that is the same
29097 as the To address that was used to get the mail to you in the first place.
29099 <P>
29100 If a role is being used and it has a From address defined, that From address will
29101 be used rather than the one derived from this feature.
29103 <P>
29104 <UL>
29105 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29106 </UL><P>
29107 <End of help on this topic>
29108 </BODY>
29109 </HTML>
29110 ====== h_config_prefix_editing =====
29111 <HTML>
29112 <HEAD>
29113 <TITLE>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></TITLE>
29114 </HEAD>
29115 <BODY>
29116 <H1>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></H1>
29118 This feature affects the Reply command's "Include original message
29119 in Reply?" prompt. When enabled, it causes the
29120 "Edit Indent String" sub-command to appear which allows
29121 you to edit the string Alpine would otherwise use to denote included
29122 text from the message being replied to.<P>
29124 Thus, you can change Alpine's default message quote character (usually
29125 an angle bracket) on a per message basis. So you could change your quoted message to
29126 look, for example, like this:<p>
29128 <pre>On Tues, 26 Jan 1999, John Q. Smith wrote:
29130 John: I just wanted to say hello and to congratulate you
29131 John: on a job well done!</pre><p>
29133 The configuration option
29134 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29135 may be used to change what appears as the default string to be edited.
29136 <P>
29137 NOTE: Edited <!--#echo var="VAR_reply-indent-string"--> only apply to the message
29138 currently being replied to.
29139 <P>
29140 If you change your <!--#echo var="VAR_reply-indent-string"-->
29141 so that it is not equal to the default value of "> ", then
29142 quoted text will not be flowed
29143 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
29144 when you reply.
29145 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
29146 set to the default value.
29147 <P>
29148 <UL>
29149 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29150 </UL><P>
29151 <End of help on this topic>
29152 </BODY>
29153 </HTML>
29154 ====== h_config_enable_search_and_repl =====
29155 <HTML>
29156 <HEAD>
29157 <TITLE>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></TITLE>
29158 </HEAD>
29159 <BODY>
29160 <H1>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></H1>
29162 This feature modifies the behavior of Alpine's composer. Setting this
29163 feature causes Alpine to offer the "^R Replace" subcommand, which
29164 allows you to search and replace text strings in a message you are composing,
29165 inside the "^W Where is" command.
29167 <P>
29169 To search and replace text, first enter the text to be replaced at the
29170 "Search: " prompt. Then, rather than pressing Enter to just search for that
29171 text, press ^R, which turns the prompt into
29173 <P>
29175 Search (to replace):
29177 <P>
29179 and then press Enter. The cursor will highlight the first occurrence
29180 of the text string you entered, and the prompt will show:
29182 <P>
29184 Replace "<your text string>" with :
29186 <P>
29188 where <your text string> is what you entered at the previous prompt;
29189 here, enter the replacement text. To only replace the highlighted
29190 occurrence, simply press Enter now; to replace all occurrences in the
29191 message, press ^X (Repl All), then Enter. You will then be asked to confirm
29192 each replacement.
29194 <P>
29196 The command ^R toggles between "Replace" and "Don't Replace"; its subcommand
29197 ^X toggles between "Replace All" and "Replace One."
29199 <P>
29201 If you previously searched for text in a message, it will be offered for
29202 re-use as part of the prompt, shown in [ ] brackets.
29204 <P>
29205 <End of help on this topic>
29206 </BODY>
29207 </HTML>
29208 ====== h_config_enable_view_attach =====
29209 <HTML>
29210 <HEAD>
29211 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></TITLE>
29212 </HEAD>
29213 <BODY>
29214 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></H1>
29216 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29217 Setting this feature causes Alpine to present attachments in boldface.
29218 The first available attachment is displayed in inverse. This is the
29219 "selected" attachment. Pressing RETURN will cause Alpine to display
29220 the selected attachment. Use the arrow keys to change which of the
29221 attachments displayed in boldface is the current selection.
29223 <P>
29225 Speaking of arrow keys, the Up and Down Arrows will select the next
29226 and previous attachments if one is available on the screen for selection.
29227 Otherwise, they will simply adjust the viewed text one line up or down.
29229 <P>
29231 Similarly, when selectable items are present in a message, the Ctrl-F key
29232 can be used to select the next item in the message independent of which
29233 portion of the viewed message is currently displayed. The Ctrl-B key can
29234 be used to select the previous item in the same way.
29235 <P>
29236 <End of help on this topic>
29237 </BODY>
29238 </HTML>
29239 ====== h_config_enable_y_print =====
29240 <HTML>
29241 <HEAD>
29242 <TITLE>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></TITLE>
29243 </HEAD>
29244 <BODY>
29245 <H1>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></H1>
29247 This feature modifies the behavior of Alpine's Print command.
29248 <P>
29249 By default, Alpine's print command is available by pressing the "%" key.
29250 (This command is a substantial change from Pine versions before 4.00 --
29251 where the print command was "Y" -- based on numerous complaints about
29252 printing being invoked inadvertently, since Y also means "Yes.")
29254 <P>
29256 This feature is supplied to mitigate any disruption or anxiety users
29257 might feel as a result of this change.
29259 <P>
29261 Enabling this feature will cause Alpine to recognize both the old
29262 command, "Y" for Prynt, as well the new "%" method for invoking
29263 printing. Note, key menu labels are not changed as a result of
29264 enabling this feature.
29266 <P>
29268 <End of help on this topic>
29269 </BODY>
29270 </HTML>
29271 ====== h_config_enable_lessthan_exit =====
29272 <HTML>
29273 <HEAD>
29274 <TITLE>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></TITLE>
29275 </HEAD>
29276 <BODY>
29277 <H1>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></H1>
29279 If this feature is set, then on screens where there is an Exit command
29280 but no < command, the < key will perform the same function as the Exit
29281 command.
29282 This feature is set by default.
29283 <P>
29284 <End of help on this topic>
29285 </BODY>
29286 </HTML>
29287 ====== h_config_enable_view_url =====
29288 <HTML>
29289 <HEAD>
29290 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></TITLE>
29291 </HEAD>
29292 <BODY>
29293 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></H1>
29294 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29295 When this feature is set (the default) Alpine will select possible URLs from the
29296 displayed text and display them in boldface for selection.
29297 <P>
29298 The first available URL is displayed in inverse. This is the
29299 "selected" URL. Pressing RETURN will cause Alpine to display
29300 the selected URL via either built-in means as with mailto:, imap:,
29301 news:, and nntp:, or via an external application as defined
29302 by the <A HREF="h_config_browser">"url-viewer"</A>
29303 variable.
29304 <P>
29305 Use the arrow keys to change which of the URLs displayed in boldface
29306 is the current selection.
29307 <P>
29308 Speaking of arrow keys, the Up and Down Arrows will select the next
29309 and previous URL if one is available on the screen for selection (unless
29310 you have set the feature
29311 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
29312 Otherwise, they will simply adjust the viewed text one line up or down.
29313 <P>
29314 Similarly, when selectable items are present in a message, the Ctrl-F
29315 key can be used to select the next item in the message independent
29316 of which portion of the viewed message is currently displayed. The
29317 Ctrl-B key can be used to select the previous item in the same way.
29318 <P>
29319 <UL>
29320 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29321 </UL><P>
29322 <End of help on this topic>
29323 </BODY>
29324 </HTML>
29325 ====== h_config_enable_view_web_host =====
29326 <HTML>
29327 <HEAD>
29328 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></TITLE>
29329 </HEAD>
29330 <BODY>
29331 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></H1>
29333 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29334 When this feature is set (the default) Alpine will select possible web hostnames
29335 from the displayed text and display them in boldface for selection.
29336 This can be useful when you receive messages referencing World Wide Web
29337 sites without the use of complete URLs; for example, specifying only
29338 "www.patches.freeiz.com/alpine/" (which will <B>not</B> become a
29339 selectable
29340 item by setting <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>)
29341 rather than explicitly
29342 "http://www.patches.freeiz.com/alpine/".
29343 <P>
29344 The first available hostname is displayed in inverse. This is the
29345 "selected" hostname. Pressing RETURN will cause Alpine to display
29346 the selected hostname via an external application as defined
29347 by the <A HREF="h_config_browser">"url-viewer"</A>
29348 variable.
29349 <P>
29350 Use the arrow keys (unless you have set the feature
29351 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
29352 to change which of the hostnames displayed in
29353 boldface is the current selection.
29354 <P>
29355 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
29356 key can be used to select the next web hostname in the message independent
29357 of which portion of the viewed message is currently displayed. The
29358 Ctrl-B key can be used to select the previous web hostnames in the same way.
29359 <P>
29360 <UL>
29361 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29362 </UL><P>
29363 <End of help on this topic>
29364 </BODY>
29365 </HTML>
29366 ====== h_config_enable_view_addresses =====
29367 <HTML>
29368 <HEAD>
29369 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></TITLE>
29370 </HEAD>
29371 <BODY>
29372 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></H1>
29374 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29375 Setting this feature causes Alpine to select possible email addresses
29376 from the displayed text and display them in boldface for selection.
29378 <P>
29379 The first available email address is displayed in inverse. This is the
29380 "selected" address. Pressing RETURN will cause Alpine to enter
29381 the message composition screen with the To: field filled in with the
29382 selected address.
29383 <P>
29384 Use the arrow keys (unless you have set the feature
29385 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
29386 to change which of the hostnames displayed in
29387 boldface is the current selection.
29388 <P>
29389 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
29390 key can be used to select the next web hostname in the message independent
29391 of which portion of the viewed message is currently displayed. The
29392 Ctrl-B key can be used to select the previous web hostnames in the same way.
29393 <P>
29394 <UL>
29395 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29396 </UL><P>
29397 <End of help on this topic>
29398 </BODY>
29399 </HTML>
29400 ====== h_config_enable_view_arrows =====
29401 <HTML>
29402 <HEAD>
29403 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></TITLE>
29404 </HEAD>
29405 <BODY>
29406 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></H1>
29408 This feature modifies Up and Down arrow key behavior in Alpine's
29409 MESSAGE TEXT screen when selectable Attachments, URL's, or
29410 web-hostnames are presented. Alpine's usual behavior is to move to
29411 the next or previous selectable item if currently displayed or
29412 simply to adjust the screen view by one line.
29414 <P>
29416 Setting this feature causes the UP and Down arrow key to behave as
29417 if no selectable items were present in the message.
29419 <P>
29421 Note, the Ctrl-F (next selectable item) and Ctrl-B (previous selectable
29422 item) functionality is unchanged.
29423 <P>
29425 <End of help on this topic>
29426 </BODY>
29427 <HTML>
29428 ====== h_config_quell_charset_warning =====
29429 <HTML>
29430 <HEAD>
29431 <TITLE>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></TITLE>
29432 </HEAD>
29433 <BODY>
29434 <H1>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></H1>
29436 By default, if the message you are viewing contains characters that are
29437 not representable in your
29438 <A HREF="h_config_char_set">"Display Character Set"</A>
29439 then Alpine will
29440 add a warning to the start of the displayed text.
29441 If this option is set, then that editorial message will be suppressed.
29442 <P>
29443 Setting this feature also suppresses the comment about the character set
29444 in header lines.
29445 For example, when viewing a message you might see
29446 <P>
29447 <CENTER><SAMP>From: "[ISO-8859-2] Name" <address></SAMP></CENTER>
29448 <P>
29449 in the From header if your Character-Set is something other than ISO-8859-2.
29450 If you set this feature, the comment about the character set will
29451 no longer be there.
29452 <P>
29453 <End of help on this topic>
29454 </BODY>
29455 </HTML>
29456 ====== h_config_quell_host_after_url =====
29457 <HTML>
29458 <HEAD>
29459 <TITLE>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></TITLE>
29460 </HEAD>
29461 <BODY>
29462 <H1>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></H1>
29464 By default, links in HTML text are displayed with the host the link
29465 references appended, within square brackets, to the link text. Alpine
29466 does this to help indicate where a link will take you, particularly when
29467 the link text might suggest a different destination.
29469 <P>
29470 Setting this feature will prevent the server name from being appended
29471 to the displayed text.
29473 <P>
29474 <End of help on this topic>
29475 </BODY>
29476 </HTML>
29477 ====== h_config_prefer_plain_text =====
29478 <HTML>
29479 <HEAD>
29480 <TITLE>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></TITLE>
29481 </HEAD>
29482 <BODY>
29483 <H1>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></H1>
29485 A message being viewed may contain alternate versions of the same content.
29486 Those alternate versions are supposed to be ordered by the sending software such that the
29487 first alternative is the least preferred and the last alternative is the
29488 most preferred. Alpine will normally display the most-preferred version that
29489 it knows how to display. This is most often encountered where the two
29490 alternate versions are a plain text version and an HTML version, with the
29491 HTML version listed last as the most preferred.
29492 <P>
29493 If this option is set, then any plain text version will be preferred to
29494 all other versions.
29495 <P>
29496 When viewing a message there is a command "A TogglePreferPlain",
29497 which will temporarily change the sense of this option.
29498 If this option is set you will first see the plain text version of a
29499 message.
29500 If you then type the "A" command, you will see the most preferred version,
29501 most likely HTML, instead.
29502 Typing the "A" command a second time will switch it back.
29503 Alternatively, if the present option is not set you will originally see
29504 the most preferred version of the message and typing "A" will switch to
29505 the plain text version.
29506 <P>
29507 <End of help on this topic>
29508 </BODY>
29509 </HTML>
29510 ====== h_config_pass_control =====
29511 <HTML>
29512 <HEAD>
29513 <TITLE>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></TITLE>
29514 </HEAD>
29515 <BODY>
29516 <H1>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></H1>
29518 It is probably not useful to set this option.
29519 This is a legacy option left behind "just in case".
29520 Multi-byte characters that have an octet that has the same
29521 value as a control character are permitted through whether or not
29522 this option is turned on.
29523 <P>
29524 This feature controls how certain characters contained in messages are
29525 displayed.
29526 If set, all characters in a message will be sent to the
29527 screen. Normally, control characters are displayed as shown below to
29528 avoid a garbled screen and to
29529 avoid inadvertently changing terminal setup parameters.
29530 Control characters are usually displayed as two character sequences like
29531 <P><CENTER><SAMP> ^C </SAMP></CENTER><P>
29532 for Control-C,
29533 <P><CENTER><SAMP> ^[ </SAMP></CENTER><P>
29534 for ESCAPE,
29535 <P><CENTER><SAMP> ^? </SAMP></CENTER><P>
29536 for DELETE, and
29537 <P><CENTER><SAMP> ~E </SAMP></CENTER><P>
29538 for the character with value 133 (0x85).
29539 (The DEL character is displayed as ^?, regular control characters are displayed
29540 as the character ^ followed by the character obtained by adding the
29541 five low-order bits of the character to 0x40, and the C1
29542 control characters 0x80 - 0x9F are displayed as the character ~ followed by the
29543 character obtained by adding the
29544 five low-order bits of the character to 0x40.)
29545 Sometimes, in cases where changing a single control character into a
29546 two-character sequence would confuse Alpine's display routines,
29547 a question mark is substituted for the control character.
29548 <P>
29549 If you wish to filter out regular control characters but pass the
29550 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
29551 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.
29552 <P>
29553 <End of help on this topic>
29554 </BODY>
29555 </HTML>
29556 ====== h_config_pass_c1_control =====
29557 <HTML>
29558 <HEAD>
29559 <TITLE>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></TITLE>
29560 </HEAD>
29561 <BODY>
29562 <H1>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></H1>
29564 It is probably not useful to set this option.
29565 This is a legacy option left behind "just in case".
29566 Multi-byte characters that have an octet that has the same
29567 value as a control character are permitted through whether or not
29568 this option is turned on.
29569 <P>
29570 If the feature <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
29571 is set, then this feature has no effect.
29572 However, if you wish to filter out regular control characters but pass the
29573 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
29574 you may leave <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
29575 unset and set this feature.
29576 <P>
29577 <End of help on this topic>
29578 </BODY>
29579 </HTML>
29580 ====== h_config_fcc_on_bounce =====
29581 <HTML>
29582 <HEAD>
29583 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></TITLE>
29584 </HEAD>
29585 <BODY>
29586 <H1>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></H1>
29588 This feature controls an aspect of Alpine's behavior when bouncing a
29589 message. If set, normal FCC ("File Carbon Copy") processing will be
29590 done, just as if you had composed a message to the address you are
29591 bouncing to. If not set, no FCC of the message will be saved.
29592 <P>
29593 <End of help on this topic>
29594 </BODY>
29595 </HTML>
29596 ====== h_config_show_cursor =====
29597 <HTML>
29598 <HEAD>
29599 <TITLE>FEATURE: <!--#echo var="FEAT_show-cursor"--></TITLE>
29600 </HEAD>
29601 <BODY>
29602 <H1>FEATURE: <!--#echo var="FEAT_show-cursor"--></H1>
29604 This feature controls an aspect of Alpine's displays. If set, the system
29605 cursor will move to convenient locations in the displays. For example,
29606 to the beginning of the status field of the highlighted index line, or
29607 to the highlighted word after a successful WhereIs command. It is intended
29608 to draw your attention to an "interesting" spot on the screen.
29609 <P>
29610 <End of help on this topic>
29611 </BODY>
29612 </HTML>
29613 ====== h_config_sort_fcc_alpha =====
29614 <HTML>
29615 <HEAD>
29616 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></TITLE>
29617 </HEAD>
29618 <BODY>
29619 <H1>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></H1>
29621 This feature controls an aspect of Alpine's FOLDER LIST screen.
29622 If set, the default Fcc folder will be sorted alphabetically with the other
29623 folders instead of appearing right after the INBOX.
29624 <P>
29625 <End of help on this topic>
29626 </BODY>
29627 </HTML>
29628 ====== h_config_sort_save_alpha =====
29629 <HTML>
29630 <HEAD>
29631 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></TITLE>
29632 </HEAD>
29633 <BODY>
29634 <H1>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></H1>
29636 This feature controls an aspect of Alpine's FOLDER LIST screen.
29637 If set, the default save folder will be sorted alphabetically with the other
29638 folders instead of appearing right after the INBOX (and default FCC folder).
29639 <P>
29640 <End of help on this topic>
29641 </BODY>
29642 </HTML>
29643 ====== h_config_single_list =====
29644 <HTML>
29645 <HEAD>
29646 <TITLE>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></TITLE>
29647 </HEAD>
29648 <BODY>
29649 <H1>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></H1>
29651 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
29652 the folders will be listed one per line instead of several per line
29653 in the FOLDER LIST display.
29654 <P>
29655 <End of help on this topic>
29656 </BODY>
29657 </HTML>
29658 ====== h_config_vertical_list =====
29659 <HTML>
29660 <HEAD>
29661 <TITLE>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></TITLE>
29662 </HEAD>
29663 <BODY>
29664 <H1>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></H1>
29666 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
29667 the folders will be listed alphabetically down the columns rather
29668 than across the columns as is the default.
29669 <P>
29670 <End of help on this topic>
29671 </BODY>
29672 </HTML>
29673 ====== h_config_verbose_post =====
29674 <HTML>
29675 <HEAD>
29676 <TITLE>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></TITLE>
29677 </HEAD>
29678 <BODY>
29679 <H1>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></H1>
29680 This feature controls an aspect of Alpine's message sending. When enabled,
29681 Alpine will send a VERB (i.e., VERBose) command early in the posting process
29682 intended to cause the SMTP server to provide a more detailed account of
29683 the transaction. This feature is typically only useful to system
29684 administrators and other support personel as an aid in troublshooting
29685 problems.
29686 <P>
29687 Note, this feature relies on a specific capability of the system's mail
29688 transport agent or configured
29689 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>.
29690 It is possible that this
29691 feature will cause problems for some tranport agents, and may result in
29692 sending failure. In addition, as the verbose output comes from the mail
29693 transport agent, it is likely to vary from one system to another.
29694 <P><UL>
29695 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29696 </UL><P>
29697 <End of help on this topic>
29698 </BODY>
29699 </HTML>
29700 ====== h_config_auto_reply_to =====
29701 <HTML>
29702 <HEAD>
29703 <TITLE>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></TITLE>
29704 </HEAD>
29705 <BODY>
29706 <H1>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></H1>
29708 This feature controls an aspect of Alpine's Reply command. If set, Alpine
29709 will not prompt when a message being replied to contains a "Reply-To:"
29710 header value, but will simply use its value (as opposed to using the
29711 "From:" field's value).
29713 <P>
29715 Note: Using the "Reply-To:" address is usually the preferred behavior,
29716 however, some mailing list managers choose to place the list's address in
29717 the "Reply-To:" field of any message sent out to the list. In such
29718 cases, this feature makes it all too easy for personal replies to be
29719 inadvertently sent to the entire mail list, so be careful!
29720 <P>
29721 <End of help on this topic>
29722 </BODY>
29723 </HTML>
29724 ====== h_config_del_skips_del =====
29725 <HTML>
29726 <HEAD>
29727 <TITLE>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></TITLE>
29728 </HEAD>
29729 <BODY>
29730 <H1>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></H1>
29732 This feature controls an aspect of Alpine's Delete command. If set, this
29733 feature will cause the Delete command to advance past following messages that
29734 are marked deleted. In other words, pressing "D" will both mark the
29735 current message deleted and advance to the next message that is not marked
29736 deleted.
29737 This feature is set by default.
29738 <P>
29739 <End of help on this topic>
29740 </BODY></HTML>
29741 ====== h_config_expunge_manually =====
29742 <HTML>
29743 <HEAD>
29744 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></TITLE>
29745 </HEAD>
29746 <BODY>
29747 <H1>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></H1>
29749 Normally, when you close a folder that contains deleted messages you are
29750 asked if you want to expunge those messages from the folder permanently.
29751 If this feature is set, you won't be asked and the deleted messages will
29752 remain in the folder.
29753 If you choose to set this feature you will have to expunge the
29754 messages manually using the eXpunge command, which you can use while
29755 in the MESSAGE INDEX screen.
29756 If you do not expunge deleted messages the size of your
29757 folder will continue to increase until you are out of disk space.
29758 <P>
29759 <UL>
29760 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29761 </UL><P>
29762 <End of help on this topic>
29763 </BODY>
29764 </HTML>
29765 ====== h_config_auto_expunge =====
29766 <HTML>
29767 <HEAD>
29768 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></TITLE>
29769 </HEAD>
29770 <BODY>
29771 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></H1>
29773 This features controls an aspect of Alpine's eXpunge command. If set, you
29774 will <B>not</B> be prompted to confirm your intent before the expunge takes
29775 place.
29776 Actually, this is only true for the INBOX folder and for folders in the
29777 Incoming Folders collection. See the feature
29778 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>.
29779 <P>
29780 <UL>
29781 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29782 </UL><P>
29783 <End of help on this topic>
29784 </BODY>
29785 </HTML>
29786 ====== h_config_full_auto_expunge =====
29787 <HTML>
29788 <HEAD>
29789 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></TITLE>
29790 </HEAD>
29791 <BODY>
29792 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></H1>
29794 This features controls an aspect of Alpine's eXpunge command. If set, you
29795 will <B>not</B> be prompted to confirm your intent before the expunge
29796 takes place. This feature sets this behavior for all folders, unlike the
29797 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
29798 feature that works only for incoming folders.
29799 <P>
29800 <UL>
29801 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29802 </UL><P>
29803 <End of help on this topic>
29804 </BODY>
29805 </HTML>
29806 ====== h_config_auto_read_msgs =====
29807 <HTML>
29808 <HEAD>
29809 <TITLE>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></TITLE>
29810 </HEAD>
29811 <BODY>
29812 <H1>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></H1>
29813 This feature controls an aspect of Alpine's behavior upon quitting. If set,
29814 and the
29815 <A HREF="h_config_read_message_folder">"<!--#echo var="VAR_read-message-folder"-->"</A>
29816 option is also set, then Alpine will
29817 automatically transfer all read messages to the designated folder and mark
29818 them as deleted in the INBOX. Messages in the INBOX marked with an
29819 "N" (meaning New, or unseen) are not affected.
29820 <P>
29821 <UL>
29822 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29823 </UL><P>
29824 <End of help on this topic>
29825 </BODY>
29826 </HTML>
29827 ====== h_config_auto_fcc_only =====
29828 <HTML>
29829 <HEAD>
29830 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></TITLE>
29831 </HEAD>
29832 <BODY>
29833 <H1>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></H1>
29834 This features controls an aspect of Alpine's composer.
29835 The only time this feature will be used is if you attempt to send mail
29836 that has no recipients but does have an Fcc.
29837 Normally, Alpine will ask if you really mean to copy the message only to
29838 the Fcc.
29839 That is, it asks if you really meant to have no recipients.
29840 If this feature is set, you
29841 will <B>not</B> be prompted to confirm your intent to make only a copy
29842 of a message with no recipients.
29843 <P>
29844 This feature is closely related to
29845 <A HREF="h_config_warn_if_no_to_or_cc"><!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></A>.
29846 The difference between this feature and that feature is that this feature
29847 considers a Bcc to be a recipient while that feature will ask for confirmation
29848 even if there is a Bcc when there is no To, Cc, or Newsgroup.
29849 The default values also differ. This feature defaults to asking the question
29850 and you have to turn it off.
29851 The <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--> feature defaults to not asking
29852 unless you turn it on.
29853 <P>
29855 <UL>
29856 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29857 </UL><P>
29858 <End of help on this topic>
29859 </BODY>
29860 </HTML>
29861 ====== h_config_mark_fcc_seen =====
29862 <HTML>
29863 <HEAD>
29864 <TITLE>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></TITLE>
29865 </HEAD>
29866 <BODY>
29867 <H1>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></H1>
29869 This features controls the way Fccs (File carbon copies) are
29870 made of the messages you send.
29872 <P>
29873 Normally, when Alpine saves a copy of a message you sent as an Fcc, that
29874 copy will be marked as Unseen.
29875 When you look at the folder it was saved in the message will appear to
29876 be a New message until you read it.
29877 When this feature is enabled, the message will be marked as having
29878 been Seen.
29880 <P>
29881 <UL>
29882 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29883 </UL><P>
29884 <End of help on this topic>
29885 </BODY>
29886 </HTML>
29887 ====== h_config_no_fcc_attach =====
29888 <HTML>
29889 <HEAD>
29890 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></TITLE>
29891 </HEAD>
29892 <BODY>
29893 <H1>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></H1>
29895 This features controls the way Fcc's (File carbon copies) are
29896 made of the messages you send.
29898 <P>
29899 Normally, Alpine saves an exact copy of your message as it was sent.
29900 When this feature is enabled, the "body" of the message
29901 you send (the text you type in the composer) is preserved in the
29902 copy as before, however all attachments are replaced with text
29903 explaining what had been sent rather than the attachments themselves.
29905 <P>
29906 This feature also affects Alpine's "Send ?" confirmation prompt
29907 in that a new "^F Fcc Attchmnts" option becomes available which
29908 allows you to interactively set whether or not attachments are saved
29909 to the Fcc'd copy.
29911 <P>
29912 <UL>
29913 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29914 </UL><P>
29915 <End of help on this topic>
29916 </BODY>
29917 </HTML>
29918 ====== h_config_read_in_newsrc_order =====
29919 <HTML>
29920 <HEAD>
29921 <TITLE>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></TITLE>
29922 </HEAD>
29923 <BODY>
29924 <H1>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></H1>
29926 This feature controls the order in which newsgroups will be presented. If
29927 set, they will be presented in the same order as they occur in your
29928 <!--chtml if pinemode="os_windows"-->
29929 "NEWSRC"
29930 <!--chtml else-->
29931 ".newsrc"
29932 <!--chtml endif-->
29933 file (the default location of which can be changed with the
29934 <A HREF="h_config_newsrc_path">"<!--#echo var="VAR_newsrc-path"-->"</A> option).
29935 <P>
29936 If not set, the newsgroups will be presented in alphabetical order.
29937 <P>
29938 <UL>
29939 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29940 </UL><P>
29941 <End of help on this topic>
29942 </BODY>
29943 </HTML>
29944 ====== h_config_quell_tz_comment =====
29945 <HTML>
29946 <HEAD>
29947 <TITLE>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></TITLE>
29948 </HEAD>
29949 <BODY>
29950 <H1>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></H1>
29952 Normally, when Alpine generates a Date header for outgoing mail,
29953 it will try to include the symbolic timezone at the end of the
29954 header inside parentheses.
29955 The symbolic timezone is often three characters long, but on
29956 some operating systems, it may be longer.
29957 Apparently there are some SMTP servers in the world that will reject an
29958 incoming message if it has a Date header longer than about 80 characters.
29959 If this feature is set, the symbolic timezone normally generated by
29960 Alpine will not be included.
29961 You probably don't need to worry about this feature unless you run into
29962 the problem described above.
29964 <P>
29965 <End of help on this topic>
29966 </BODY>
29967 </HTML>
29968 ====== h_config_post_wo_validation =====
29969 <HTML>
29970 <HEAD>
29971 <TITLE>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></TITLE>
29972 </HEAD>
29973 <BODY>
29974 <H1>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></H1>
29976 This feature controls whether the NNTP server is queried as newsgroups
29977 are entered for posting. Validation over slow links (e.g. dialup using
29978 SLIP or PPP) can cause delays. Set this feature to eliminate such delays.
29979 <P>
29980 <End of help on this topic>
29981 </BODY>
29982 </HTML>
29983 ====== h_config_send_wo_confirm =====
29984 <HTML>
29985 <HEAD>
29986 <TITLE>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></TITLE>
29987 </HEAD>
29988 <BODY>
29989 <H1>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></H1>
29991 By default, when you send or post a message you will be asked to confirm
29992 with a question that looks something like:
29994 <P>
29995 <CENTER><SAMP>Send message?</SAMP></CENTER>
29996 <P>
29998 If this feature is set, you
29999 will <B>not</B> be prompted to confirm your intent to send
30000 and your message will be sent.
30001 <P>
30002 If this feature is set it disables some possibilities and renders some
30003 other features meaningless.
30004 You will not be able to use
30005 <A HREF="h_config_sending_filter">Sending Filters</A>,
30006 Verbose sending mode,
30007 <A HREF="h_config_compose_bg_post">Background Sending</A>,
30008 <A HREF="h_config_compose_dsn">Delivery Status Notifications</A>,
30009 or ^V to turn off the generation of flowed text for this message.
30010 These options are normally available as suboptions in the Send prompt, but
30011 with no Send prompt the options are gone.
30013 <P>
30014 A somewhat related feature is
30015 <A HREF="h_config_quell_post_prompt">"<!--#echo var="FEAT_quell-extra-post-prompt"-->"</A>,
30016 which may be used to eliminate the extra confirmation
30017 question when posting to a newsgroup.
30018 <P>
30019 <UL>
30020 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30021 </UL><P>
30022 <End of help on this topic>
30023 </BODY>
30024 </HTML>
30025 ====== h_config_quell_filtering_done_message =====
30026 <HTML>
30027 <HEAD>
30028 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></TITLE>
30029 </HEAD>
30030 <BODY>
30031 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></H1>
30033 If you use Filter Rules that move messages or set status of messages
30034 you sometimes see a message from Alpine that looks like
30036 <P>
30037 <CENTER><SAMP>filtering done</SAMP></CENTER>
30038 <P>
30040 If this feature is set, this message will be suppressed.
30041 If the feature
30042 <A HREF="h_config_quell_filtering_messages"><!--#echo var="FEAT_quell-filtering-messages"--></A>
30043 is set then this message will be suppressed regardless.
30045 <P>
30046 <UL>
30047 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30048 </UL><P>
30049 <End of help on this topic>
30050 </BODY>
30051 </HTML>
30052 ====== h_config_quell_filtering_messages =====
30053 <HTML>
30054 <HEAD>
30055 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></TITLE>
30056 </HEAD>
30057 <BODY>
30058 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></H1>
30060 If you use Filter Rules that move messages or set status of messages
30061 you sometimes see messages from Alpine that look like
30063 <P>
30064 <CENTER><SAMP><filter name>: Moving 2 filtered messages to <folder name></SAMP></CENTER>
30065 <P>
30067 or
30069 <P>
30070 <CENTER><SAMP><filter name>: Setting flags in 5 messages</SAMP></CENTER>
30071 <P>
30073 or
30075 <P>
30076 <CENTER><SAMP>Processing filter <filter name></SAMP></CENTER>
30077 <P>
30079 If this feature is set, these messages will be suppressed.
30080 The feature
30081 <A HREF="h_config_quell_filtering_done_message"><!--#echo var="FEAT_quell-filtering-done-message"--></A>
30082 is related.
30084 <P>
30085 <UL>
30086 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30087 </UL><P>
30088 <End of help on this topic>
30089 </BODY>
30090 </HTML>
30091 ====== h_config_quell_post_prompt =====
30092 <HTML>
30093 <HEAD>
30094 <TITLE>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></TITLE>
30095 </HEAD>
30096 <BODY>
30097 <H1>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></H1>
30099 By default, when you post a message to a newsgroup you are asked to confirm
30100 that you want to post with the question
30102 <P>
30103 <CENTER><SAMP>Posted message may go to thousands of readers. Really post?</SAMP></CENTER>
30104 <P>
30106 If this feature is set, you
30107 will <B>not</B> be prompted to confirm your intent to post to a newsgroup
30108 and your message will be posted.
30110 <P>
30111 <UL>
30112 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30113 </UL><P>
30114 <End of help on this topic>
30115 </BODY>
30116 </HTML>
30117 ====== h_config_check_mail_onquit =====
30118 <HTML>
30119 <HEAD>
30120 <TITLE>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></TITLE>
30121 </HEAD>
30122 <BODY>
30123 <H1>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></H1>
30125 If this feature is set, Alpine will check for new mail after you give the
30126 Quit command.
30127 If new mail has arrived since the previous check, you will be notified
30128 and given the choice of quitting or not quitting.
30129 <P>
30130 <UL>
30131 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30132 </UL><P>
30133 <End of help on this topic>
30134 </BODY>
30135 </HTML>
30136 ====== h_config_inbox_no_confirm =====
30137 <HTML>
30138 <HEAD>
30139 <TITLE>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></TITLE>
30140 </HEAD>
30141 <BODY>
30142 <H1>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></H1>
30144 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
30145 command and there are no more folders or newsgroups to visit, you are asked
30146 if you want to return to the INBOX.
30147 If this feature is set you will not be asked.
30148 It will be assumed that you do want to return to the INBOX.
30149 <P>
30150 <UL>
30151 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30152 </UL><P>
30153 <End of help on this topic>
30154 </BODY>
30155 </HTML>
30156 ====== h_config_dates_to_local =====
30157 <HTML>
30158 <HEAD>
30159 <TITLE>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></TITLE>
30160 </HEAD>
30161 <BODY>
30162 <H1>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></H1>
30164 Normally, the message dates that you see in the
30165 MESSAGE INDEX and MESSAGE VIEW are displayed in the timezone they were sent from.
30166 For example, if a message was sent to you from a few timezones to the east
30167 it might appear that it was sent from the future;
30168 or if it was sent from somewhere to the west it might appear
30169 as if it is from yesterday even though it was sent only a few minutes ago.
30170 If this feature is set an attempt will be made to convert the dates
30171 to your local timezone to be displayed.
30172 <P>
30173 Note that this does not affect the results of Select by Date or of
30174 anything else other than these displayed dates.
30175 When viewing the message you may look at the original unconverted value of the Date
30176 header by using the <A HREF="h_common_hdrmode">HdrMode Command</A>.
30177 <P>
30178 <UL>
30179 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30180 </UL><P>
30181 <End of help on this topic>
30182 </BODY>
30183 </HTML>
30184 ====== h_config_tab_no_prompt =====
30185 <HTML>
30186 <HEAD>
30187 <TITLE>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></TITLE>
30188 </HEAD>
30189 <BODY>
30190 <H1>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></H1>
30192 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
30193 command and there is a problem checking a folder, you are asked
30194 whether you want to continue with the search in the following folder or not.
30195 This question gives you a chance to stop the NextNew processing.
30196 (The checking problem might be caused by the fact that the folder does not
30197 exist, or by an authentication problem, or by a server problem
30198 of some sort.)
30199 <P>
30201 If this feature is set you will not be asked.
30202 It will be assumed that you do want to continue.
30203 <P>
30204 <UL>
30205 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30206 </UL><P>
30207 <End of help on this topic>
30208 </BODY>
30209 </HTML>
30210 ====== h_config_input_history =====
30211 <HTML>
30212 <HEAD>
30213 <TITLE>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></TITLE>
30214 </HEAD>
30215 <BODY>
30216 <H1>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></H1>
30218 Many of the prompts that ask for input in the status line near the
30219 bottom of the screen will respond to Up Arrow and Down Arrow
30220 with the history of previous entries.
30221 For example, in the MESSAGE INDEX screen when you use the WhereIs
30222 command the text you entered will be remembered and can be recalled
30223 by using the Up Arrow key.
30224 Another example, when saving a message the folders saved to will
30225 be remembered and can be recalled using the arrow keys.
30226 <P>
30227 In the Save prompt, some users prefer that the Up and Down arrow keys
30228 be used for the Previous Collection and Next Collection commands
30229 instead of for a history of previous saves.
30230 If this option is set the Up and Down arrow keys will become synonyms for the
30231 Previous Collection and Next Collection (^P and ^N) commands in the
30232 prompt for the name of a folder to Save to or in the prompt for the
30233 name of a folder to GoTo.
30234 When this feature is not set (the default), ^P and ^N will change the
30235 collection and the arrow keys will show the history.
30236 <P>
30237 <UL>
30238 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30239 </UL><P>
30240 <End of help on this topic>
30241 </BODY>
30242 </HTML>
30243 ====== h_config_confirm_role =====
30244 <HTML>
30245 <HEAD>
30246 <TITLE>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></TITLE>
30247 </HEAD>
30248 <BODY>
30249 <H1>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></H1>
30251 If you have roles, when you Reply to or Forward a message, or Compose
30252 a new message, Alpine
30253 will search through your roles for one that matches.
30254 Normally, if no matches are found you will be placed into the composer
30255 with no opportunity to select a role.
30256 If this feature is set, then you will be asked to confirm that you don't
30257 want a role.
30258 This will give you the opportunity to select a role (with the ^T command).
30259 If you confirm no role with a Return, you will be placed in
30260 the composer with no role.
30261 You may also confirm with either an "N" or a "Y".
30262 These behave the same as if you pressed the Return.
30263 (The "N" and "Y" answers are available because they
30264 match what you might type if there was a role match.)
30265 <P>
30266 If you are using the alternate form of the Compose command called
30267 "Role", then all of your roles will be available to you,
30268 independent of the value of this feauture and of the values set for all of
30269 Reply Use, Forward Use, and Compose Use.
30270 <P>
30271 <UL>
30272 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30273 </UL><P>
30274 <End of help on this topic>
30275 </BODY>
30276 </HTML>
30277 ====== h_config_news_cross_deletes =====
30278 <HTML>
30279 <HEAD>
30280 <TITLE>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></TITLE>
30281 </HEAD>
30282 <BODY>
30283 <H1>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></H1>
30285 This feature controls what Alpine does when you delete a message in a
30286 newsgroup that appears in more than one newsgroup. Such a message
30287 is sometimes termed a "crossposting" in that it was posted
30288 across several newsgroups.
30290 <P>
30291 Alpine's default behavior when you delete such a message is to remove
30292 only the copy in the current newsgroup from view when you use the
30293 "Exclude" command or the next time you visit the newsgroup.
30295 <P>
30296 Enabling this feature causes Alpine to remove every occurrence of the
30297 message from all newsgroups it appears in and to which you are
30298 subscribed.
30300 <P>
30301 NOTE: As currently implemented, enabling this feature may increase the
30302 time it takes the Expunge command and newsgroup closing to complete.
30304 <P>
30305 <UL>
30306 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30307 </UL><P>
30308 <End of help on this topic>
30309 </BODY>
30310 </HTML>
30311 ====== h_config_news_catchup =====
30312 <HTML>
30313 <HEAD>
30314 <TITLE>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></TITLE>
30315 </HEAD>
30316 <BODY>
30317 <H1>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></H1>
30319 This feature controls what Alpine does as it closes a newsgroup.
30320 When set, Alpine will offer to delete all messages from the newsgroup
30321 as you are quitting Alpine or opening a new folder.
30323 <P>
30324 This feature is useful if you typically read all the interesting messages
30325 in a newsgroup each time you open it. This feature saves you from
30326 having to delete each message in a newsgroup as you read it or from
30327 selecting all the messages and doing an
30328 <A HREF="h_config_enable_agg_ops">aggregate delete</A> before you
30329 move on to the next folder or newsgroup.
30331 <P>
30332 <UL>
30333 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30334 </UL><P>
30335 <End of help on this topic>
30336 </BODY>
30337 </HTML>
30338 ====== h_config_next_thrd_wo_confirm =====
30339 <HTML>
30340 <HEAD>
30341 <TITLE>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></TITLE>
30342 </HEAD>
30343 <BODY>
30344 <H1>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></H1>
30346 This feature controls an aspect of Alpine's Next and Prev commands in
30347 the case where you are using one of the
30348 "separate-index-screen" styles for the configuration option
30349 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
30350 and currently have the folder sorted by a Threaded or OrderedSubject sort.
30351 When you are Viewing a particular thread you have a
30352 MESSAGE INDEX of only the messages in that thread.
30353 If you press the Next command with the last message in the thread highlighted
30354 you will normally be asked if you want to "View next thread?",
30355 assuming there is a next thread to view.
30356 If this feature is set it will be assumed that you always want to view the
30357 next thread and you won't be asked to confirm that.
30358 Similarly, if the first message of the thread is highlighted and you
30359 press the Prev command, this feature will prevent the question
30360 "View previous thread".
30361 <P>
30362 This feature only has an effect in the MESSAGE INDEX screen.
30363 If you then view a particular message from that screen and press the
30364 Next command, you will be sent to the next thread without being asked,
30365 independent of the setting of this feature.
30366 <P>
30367 The feature
30368 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A> also has some similar effects.
30369 <P>
30370 <End of help on this topic>
30371 </BODY>
30372 </HTML>
30373 ====== h_config_kw_braces =====
30374 <HTML>
30375 <HEAD>
30376 <TITLE>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></TITLE>
30377 </HEAD>
30378 <BODY>
30379 <H1>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></H1>
30381 This option controls a minor aspect of Alpine's MESSAGE INDEX and MESSAGE
30382 TEXT screens.
30383 If you have modified the
30384 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
30385 so that either the "SUBJKEY" or "SUBJKEYINIT" tokens
30386 are used to display keywords or their initials along with the Subject; then
30387 this option may be used to modify the resulting display slightly.
30388 By default, the keywords or initials displayed for these tokens will be
30389 surrounded with curly braces ({ and }) and a trailing space.
30390 For example, if keywords "Work" and "Now" are set for
30391 a message, the "SUBJKEY" token will normally look like
30392 <P>
30393 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
30394 <P>
30395 and the SUBJKEYINIT token would look like
30396 <P>
30397 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
30398 <P>
30399 The default character before the keywords is the left brace ({) and the
30400 default after the keywords is the right brace followed by a space (} ).
30401 <P>
30402 This option allows you to change that.
30403 You should set it to two values separated by a space.
30404 The values may be quoted if they include space characters.
30405 So, for example, the default value could be specified explicitly by setting this
30406 option to
30407 <P>
30408 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="{" "} "</SAMP></CENTER>
30409 <P>
30410 The first part wouldn't need to be quoted (but it doesn't hurt).
30411 The second part does need the quotes because it includes a space character.
30412 If you wanted to change the braces to brackets you could use
30413 <P>
30414 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="[" "] "</SAMP></CENTER>
30415 <P>
30416 Inside the quotes you can use backslash quote to mean quote, so
30417 <P>
30418 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="\"" "\" "</SAMP></CENTER>
30419 <P>
30420 would produce
30421 <P>
30422 <CENTER><SAMP>"Work Now" actual subject</SAMP></CENTER>
30423 <P>
30424 It is also possible to color keywords in the index using the
30425 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
30426 <P>
30427 It is not possible to change the fact that a space character is used to
30428 separate the keywords if more than one keyword is set for a message.
30429 It is also not possible to change the fact that there are no separators
30430 between the keyword initials if more than one keyword is set.
30431 <P>
30432 <End of help on this topic>
30433 </BODY>
30434 </HTML>
30435 ====== h_config_opening_sep =====
30436 <HTML>
30437 <HEAD>
30438 <TITLE>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></TITLE>
30439 </HEAD>
30440 <BODY>
30441 <H1>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></H1>
30443 This option controls a minor aspect of Alpine's MESSAGE INDEX screen.
30444 With some setups the text of the subject is followed
30445 by the opening text of the message if there is any room available in the index line.
30446 If you have configured your
30447 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
30448 to include one of the Subject tokens that causes this behavior
30449 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), then this option may be used
30450 to modify what is displayed slightly.
30451 By default, the Subject is separated from the opening text of the message by
30452 the three characters space dash space;
30453 <P>
30454 <CENTER><SAMP>" - "</SAMP></CENTER>
30455 <P>
30456 Use this option to set it to something different.
30457 The value must be quoted if it includes any space characters.
30458 For example, the default value could be specified explicitly by setting this
30459 option to
30460 <P>
30461 <CENTER><SAMP><!--#echo var="VAR_opening-text-separator-chars"-->=" - "</SAMP></CENTER>
30462 <P>
30463 <End of help on this topic>
30464 </BODY>
30465 </HTML>
30466 ====== h_config_select_wo_confirm =====
30467 <HTML>
30468 <HEAD>
30469 <TITLE>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></TITLE>
30470 </HEAD>
30471 <BODY>
30472 <H1>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></H1>
30474 This feature controls an aspect of Alpine's Save, Export, and Goto commands.
30475 These commands all take text input to specify the name of the folder or
30476 file to be used, but allow you to press ^T for a list of possible names.
30477 If set, the selected name will be used immediately, without further
30478 opportunity to confirm or edit the name.
30479 <P>
30480 Some related help topics are
30481 <UL>
30482 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
30483 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
30484 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
30485 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
30486 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
30487 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>.
30488 </UL>
30489 <P>
30490 <End of help on this topic>
30491 </BODY>
30492 </HTML>
30493 ====== h_config_save_part_wo_confirm =====
30494 <HTML>
30495 <HEAD>
30496 <TITLE>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></TITLE>
30497 </HEAD>
30498 <BODY>
30499 <H1>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></H1>
30501 This feature controls an aspect of Alpine's Save command.
30502 By default, when you Save a message that has some deleted parts, you will
30503 be asked to confirm that you want to Save with a prompt that looks like:
30504 <P>
30505 <CENTER><SAMP>Saved copy will NOT include entire message! Continue?</SAMP></CENTER>
30506 <P>
30507 If this feature is set, you will not be asked.
30508 <P>
30509 <End of help on this topic>
30510 </BODY>
30511 </HTML>
30512 ====== h_config_use_resentto =====
30513 <HTML>
30514 <HEAD>
30515 <TITLE>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></TITLE>
30516 </HEAD>
30517 <BODY>
30518 <H1>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></H1>
30520 This feature is turned off by default because turning it on causes problems
30521 with some deficient IMAP servers.
30522 In Alpine <A HREF="h_mainhelp_filtering">Filters</A> and other types of Rules, if the
30523 <A HREF="h_rule_patterns">Pattern</A>
30524 contains a To header pattern and this feature is turned on,
30525 then a check is made in the message to see
30526 if a Resent-To header is present, and that is used instead of the To header.
30527 If this feature is not turned on, then the regular To header will always
30528 be used.
30530 <P>
30531 <End of help on this topic>
30532 </BODY>
30533 </HTML>
30534 ====== h_config_use_reg_start_for_stayopen =====
30535 <HTML>
30536 <HEAD>
30537 <TITLE>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></TITLE>
30538 </HEAD>
30539 <BODY>
30540 <H1>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></H1>
30542 This feature affects which message is selected as the current message
30543 when you enter a
30544 <A HREF="h_config_permlocked">Stay Open</A> folder.
30545 <P>
30546 Normally, the starting position for an incoming folder (which most Stay Open
30547 folders will likely be) is controlled by the
30548 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
30549 However, if a folder is a Stay Open folder, when you re-enter the folder
30550 after the first time the current message will be the same as it was when
30551 you left the folder.
30552 An exception is made if you use the TAB command to get to the folder.
30553 In that case, the message number will be incremented by one from what it
30554 was when you left the folder.
30555 <P>
30556 The above special behavior is thought to be useful.
30557 However, it is special and different from what you might at first expect.
30558 If this feature is set, then Stay Open folders will not be treated specially
30559 as far as the startup rule is concerned.
30561 <P>
30562 <End of help on this topic>
30563 </BODY>
30564 </HTML>
30565 ====== h_config_use_current_dir =====
30566 <HTML>
30567 <HEAD>
30568 <TITLE>FEATURE: <!--#echo var="FEAT_use-current-dir"--></TITLE>
30569 </HEAD>
30570 <BODY>
30571 <H1>FEATURE: <!--#echo var="FEAT_use-current-dir"--></H1>
30573 This feature controls an aspect of several commands.
30574 If set, your "current working directory"
30575 <!--chtml if pinemode="running"-->
30576 (which, at least for your current Alpine "session,"
30577 is "<!--#echo var="CURRENT_DIR"-->")
30578 <!--chtml endif-->
30579 will be used instead of your home directory
30580 <!--chtml if pinemode="running"-->
30581 (which, in the present configuration of your system, is
30582 "<!--#echo var="HOME_DIR"-->")
30583 <!--chtml endif-->
30584 for all of the following operations:<UL>
30585 <LI> Export in the MESSAGE INDEX and MESSAGE TEXT screens
30586 <LI> Attachment Save in the MESSAGE TEXT and ATTACHMENT TEXT screens
30587 <LI> <!--chtml if pinemode="function_key"-->F4
30588 <!--chtml else-->Ctrl-R
30589 <!--chtml endif--> file inclusion in the COMPOSER
30590 <LI> <!--chtml if pinemode="function_key"-->F5
30591 <!--chtml else-->Ctrl-J
30592 <!--chtml endif--> file attachment in the COMPOSER
30593 </UL>
30594 <!--chtml if pinemode="os_windows"-->
30595 <P>
30596 If you are starting PC-Alpine from a desktop icon or the Start menu,
30597 you can set the "current drive"
30598 by specifying it in the "Start in:"
30599 box found in the Shortcut tab of the Properties.
30600 <!--chtml endif-->
30601 <P>
30602 <UL>
30603 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30604 </UL>
30606 <P>
30607 <End of help on this topic>
30608 </BODY>
30609 </HTML>
30610 ====== h_config_save_wont_delete =====
30611 <HTML>
30612 <HEAD>
30613 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></TITLE>
30614 </HEAD>
30615 <BODY>
30616 <H1>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></H1>
30618 This feature controls one aspect of the Save command. If set, Save will
30619 not mark the message "deleted" (its default behavior) after
30620 it has been copied to the designated folder.
30622 <P>
30623 <End of help on this topic>
30624 </BODY>
30625 </HTML>
30626 ====== h_config_use_boring_spinner =====
30627 <HTML>
30628 <HEAD>
30629 <TITLE>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></TITLE>
30630 </HEAD>
30631 <BODY>
30632 <H1>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></H1>
30634 When Alpine is delayed for some reason it usually shows that
30635 something is happening with a small animated display in the status
30636 message line near the bottom of the screen.
30637 Setting this feature will cause that animation to be the same
30638 each time instead of having Alpine choose a random animation.
30639 You may turn the animation off altogether by setting the
30640 <A HREF="h_config_active_msg_interval"><!--#echo var="VAR_busy-cue-rate"--></A>
30641 option to zero.
30643 <P>
30644 <End of help on this topic>
30645 </BODY>
30646 </HTML>
30647 ====== h_config_unsel_wont_advance =====
30648 <HTML>
30649 <HEAD>
30650 <TITLE>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></TITLE>
30651 </HEAD>
30652 <BODY>
30653 <H1>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></H1>
30655 This feature controls one aspect of the Unselect Current message command.
30656 Normally, when the Unselect current message command (:) is typed when the
30657 current message is selected, the message will be unselected and the next
30658 message will become the current message.
30659 If this feature is set, the cursor will not advance to the next message.
30660 Instead, the current message will remain the current message after
30661 unselecting.
30663 <P>
30664 <End of help on this topic>
30665 </BODY>
30666 </HTML>
30667 ====== h_config_prune_uses_iso =====
30668 <HTML>
30669 <HEAD>
30670 <TITLE>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></TITLE>
30671 </HEAD>
30672 <BODY>
30673 <H1>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></H1>
30675 By default, Alpine asks monthly whether or not you would like to rename
30676 some folders to a new name containing the date.
30677 It also asks whether or not you would like to delete some old folders.
30678 See the <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option for an
30679 explanation.
30681 <P>
30682 By default, the name used when renaming a folder looks like
30683 <P>
30684 <CENTER><SAMP><foldername>-<month>-<year></SAMP></CENTER>
30685 <P>
30686 For example, the first time you run Alpine in May of 2004,
30687 the folder "sent-mail" might be renamed to
30688 <P>
30689 <CENTER><SAMP>sent-mail-apr-2004</SAMP></CENTER>
30690 <P>
30691 If this feature is set, the name used will be of the form
30692 <P>
30693 <CENTER><SAMP><foldername>-<yyyy>-<mm></SAMP></CENTER>
30694 <P>
30695 where "yyyy" is the year and "mm" is the two-digit
30696 month (01, 02, ..., 12).
30697 For the April, 2004 example above, it would instead be
30698 <P>
30699 <CENTER><SAMP>sent-mail-2004-04</SAMP></CENTER>
30700 <P>
30701 because April is the 4th month of the year.
30702 A reason you might want to set this feature is so that the folders
30703 will sort in chronological order.
30705 <P>
30706 <End of help on this topic>
30707 </BODY>
30708 </HTML>
30709 ====== h_config_save_advances =====
30710 <HTML>
30711 <HEAD>
30712 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-advance"--></TITLE>
30713 </HEAD>
30714 <BODY>
30715 <H1>FEATURE: <!--#echo var="FEAT_save-will-advance"--></H1>
30717 This feature controls one aspect of the Save command. If set, Save will
30718 (in addition to copying the current message to the designated folder) also
30719 advance to the next message.
30721 <P>
30722 <End of help on this topic>
30723 </BODY>
30724 </HTML>
30725 ====== h_config_force_arrow =====
30726 <HTML>
30727 <HEAD>
30728 <TITLE>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></TITLE>
30729 </HEAD>
30730 <BODY>
30731 <H1>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></H1>
30733 This feature affects Alpine's MESSAGE INDEX display routine.
30734 If set, the normal inverse-video cursor will be
30735 replaced by a simple "arrow" cursor, which normally occupies the
30736 second column of the index display.
30737 <P>
30738 This is the same index cursor you get if you turn on
30739 <A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>, but the index
30740 line coloring will still be present if this feature is turned on and
30741 <!--#echo var="FEAT_assume-slow-link"--> is off.
30742 <P>
30743 An alternative version of the Arrow cursor is available by including the
30744 <A HREF="h_config_index_arrow_color">ARROW</A>
30745 token in the
30746 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
30747 <P>
30748 It ought to be the case that this feature also affects the ATTACHMENT INDEX,
30749 but that is not implemented.
30751 <P>
30752 <End of help on this topic>
30753 </BODY>
30754 </HTML>
30755 ====== h_config_force_low_speed =====
30756 <HTML>
30757 <HEAD>
30758 <TITLE>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></TITLE>
30759 </HEAD>
30760 <BODY>
30761 <H1>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></H1>
30763 UNIX Alpine only.
30764 <P>
30765 This feature affects Alpine's display routines. If set, the normal
30766 inverse-video cursor (used to highlight the current item in a list) will be
30767 replaced by an "arrow" cursor and other
30768 screen update optimizations for
30769 low-speed links (e.g. 2400 bps dialup connections) will be activated.
30770 One of the optimizations is that colored index lines (set up with Indexcolor
30771 Rules) will not be colored.
30772 If you are just turning this feature on because you like using
30773 the "arrow" cursor you may have an arrow cursor with index line
30774 coloring by turning this feature off and the
30775 <A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A> on.
30777 <P>
30778 <End of help on this topic>
30779 </BODY>
30780 </HTML>
30781 ====== h_config_show_delay_cue =====
30782 <HTML>
30783 <HEAD>
30784 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></TITLE>
30785 </HEAD>
30786 <BODY>
30787 <H1>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></H1>
30789 If set, this feature will cause an asterisk to appear in the upper
30790 left-hand corner of the screen whenever Alpine checks for new mail.
30791 Two asterisks whenever Alpine saves (checkpoints) the state of the current
30792 mailbox to disk.
30794 <!--chtml if pinemode="os_windows"-->
30795 <P>
30796 In addition, PC-Alpine will display a less-than symbol, '<', when
30797 it is trying to open a network connection (e.g, to open your INBOX
30798 on an IMAP
30799 server) or read from the network connection. A greater-than symbol,
30800 will be displayed when PC-Alpine is trying to write to the network
30801 connection (e.g, sending a command to your IMAP server).
30802 <!--chtml endif-->
30804 <P>
30805 <End of help on this topic>
30806 </BODY>
30807 </HTML>
30808 ====== h_config_color_style =====
30809 <HTML>
30810 <HEAD>
30811 <TITLE>OPTION: Color Style</TITLE>
30812 </HEAD>
30813 <BODY>
30814 <H1>OPTION: Color Style</H1>
30816 UNIX Alpine only.
30817 <P>
30818 If the terminal or terminal emulator you are using is capable of displaying
30819 colors, this option controls whether or not color will be used in Alpine.
30820 If you turn color on and things are set up correctly,
30821 you should see color appear on the screen immmediately.
30822 Modern terminal emulators are usually capable of displaying colors.
30823 <P>
30824 The available options include:
30825 <P>
30827 <DL>
30828 <DT>no-color</DT>
30829 <DD>Don't use color.
30830 </DD>
30832 <DT>use-termdef</DT>
30833 <DD>In order to decide if your terminal is capable of color, Alpine looks in
30834 the terminal capabilities database, TERMINFO or TERMCAP, depending on
30835 how Alpine was compiled.
30836 This is a good option to choose if you switch between a color and a non-color
30837 terminal with the same Alpine configuration.
30838 Alpine will know to use color on the color terminal because it is described
30839 in the termcap entry, and Alpine will know to use black and white on the
30840 non-color terminal.
30841 The Alpine Technical Notes
30842 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/tech-notes/">http://www.washington.edu/alpine/tech-notes/</A></SAMP></CENTER>
30843 have more information on configuring a TERMCAP or TERMINFO
30844 entry for color Alpine.
30845 This is usually something a system administrator does.
30846 </DD>
30848 <DT>force-ansi-8color</DT>
30849 <DD>This is probably the setting that most people should use.
30850 Because setting up a termcap entry is confusing and because the
30851 terminal capabilities database is often not correctly configured for color,
30852 this choice and the next may be easier for you to use.
30853 If your terminal emulator responds to ANSI color escape sequences, which
30854 many do, this option will cause Alpine to believe your terminal will respond
30855 to the escape sequences that produce eight different foreground and background
30856 colors.
30857 The escape sequences used to set the foreground colors are
30859 <P><CENTER>ESC [ 3 <color_number> m</CENTER><P>
30861 where the color_number is an ASCII digit between 0 and 7.
30862 The numbers 0 through 7 should correspond to the colors black, red, green,
30863 yellow, blue, magenta, cyan, and white.
30864 Some terminal emulators use a pre-ANSI scheme that swaps
30865 the colors blue and red and the colors yellow and cyan.
30866 This will cause the default colors to be different, but other than that
30867 things should work fine.
30868 There is also a 9th color available, the last one shown, which is the default
30869 color from the terminal emulator.
30870 When used as a background color some people refer to this color as
30871 "transparent", which is why the letters "TRAN" are
30872 shown in the color swatch of the SETUP COLOR screen.
30873 The foreground transparent color is shown as
30874 the color of the "TRAN" text.
30875 (The transparent color will not work correctly in a PC-Alpine configuration.)
30876 The escape sequences used to set the background colors are the same
30877 as for the foreground colors except a "4" replaces the "3".
30878 The escape sequences for foreground and background default colors (transparent)
30879 are 39m and 49m.
30880 <P>
30881 Note: With the Tera Term terminal emulator this setting works well.
30882 You should also have the Tera Term "Full color" option turned OFF.
30883 You may find the "Full color" option in Tera Term's "Setup"
30884 menu, in the "Window" submenu.
30885 </DD>
30887 <DT>force-ansi-16color</DT>
30888 <DD>Many terminal emulators know about the same eight colors above
30889 plus eight more.
30890 This option attempts to use all 16 colors.
30891 The same escape sequences as for the eight-color terminal are used
30892 for the first eight colors.
30893 The escape sequences used to set foreground colors 8-15 are the same as
30894 for 0-7 except the "3" is replaced with a "9".
30895 The background color sequences for colors 8-15 are the same as for 0-7
30896 except the "4" is replaced with "10".
30897 You can tell if the 16 colors are working by turning on this option
30898 and then going into one of the color configuration screens, for example,
30899 the configuration screen for Normal Color.
30900 If you see 16 different colors to select from (plus a 17th for
30901 the transparent color), it's working.
30902 </DD>
30904 <DT>force-xterm-256color</DT>
30905 <DD>Some versions of xterm (and some other terminal emulators)
30906 have support for 256 colors.
30907 The escape sequences used to set the foreground colors are
30909 <P><CENTER>ESC [ 38 ; 5 ; <color_number> m</CENTER><P>
30911 where the color_number is an ASCII digit between 0 and 255.
30912 Background colors are the same with the 38 replaced with a 48.
30913 The numbers 0 through 15 are probably similar to the 16 color version
30914 above, then comes a 6x6x6 color cube, followed by 24 colors of gray.
30915 The terminal default (transparent) color is the 257th color at the bottom.
30916 Some terminal emulators will misinterpret these escape sequences causing
30917 the terminal to blink or overstrike characters or to do something else
30918 undesirable.
30919 <P>
30920 The PuTTY terminal emulator has an option called "Allow terminal to
30921 use xterm 256-colour mode" which allows PuTTY to work well with
30922 this 256-color setting.
30924 </DD>
30925 </DL>
30927 <P>
30928 The normal default is "no-color".
30929 <P>
30931 Once you've turned on color you may set the
30932 colors of many objects on the screen individually.
30933 For example, you may add colors to the status letters on the MESSAGE
30934 INDEX page.
30935 Most categories of color that Alpine supports are configurable here.
30936 For example, "Normal Color"
30937 is the color used to display most of the text in Alpine, and
30938 "Reverse Color" is used to display highlighted text, such as the
30939 current message in the MESSAGE INDEX.
30940 <P>
30941 Lines in the MESSAGE INDEX may also be colored.
30942 Use Setup Rules to get to the Indexcolor configuration screen.
30943 <P>
30945 <UL>
30946 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30947 </UL><P>
30948 <End of help on this topic>
30949 </BODY>
30950 </HTML>
30951 ====== h_config_disable_index_locale_dates =====
30952 <HTML>
30953 <HEAD>
30954 <TITLE>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></TITLE>
30955 </HEAD>
30956 <BODY>
30957 <H1>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></H1>
30959 This feature affects the display of dates in the MESSAGE INDEX.
30960 Normally an attempt is made to localize the dates
30961 used in the MESSAGE INDEX display to your locale.
30962 This is controlled with the
30963 LC_TIME locale setting on a UNIX system.
30964 On Windows the Regional Options control panel may be used to set the date format.
30965 At the programming level, Alpine is using the strftime routine
30966 to print the parts of a date.
30967 <P>
30968 If this feature is set, dates are displayed in English and
30969 with the conventions of the United States.
30970 <P>
30972 <UL>
30973 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30974 </UL><P>
30975 <End of help on this topic>
30976 </BODY>
30977 </HTML>
30978 ====== h_config_auto_open_unread =====
30979 <HTML>
30980 <HEAD>
30981 <TITLE>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></TITLE>
30982 </HEAD>
30983 <BODY>
30984 <H1>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></H1>
30986 This feature controls the behavior of the TAB key when traversing folders
30987 in the optional
30988 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
30989 collection or in optional <!--#echo var="VAR_news-collections"-->.
30990 <P>
30991 When the TAB
30992 (<A HREF="h_common_nextnew">NextNew</A>)
30993 key is pressed, and there
30994 are no more unseen messages in the current (incoming message or news)
30995 folder, Alpine will search the list of folders in the current collection for
30996 one containing New or Recent (new since the last time the folder was
30997 opened) messages.
30998 This behavior may be modified slightly with the
30999 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
31000 feature that causes Alpine to look for Unseen messages instead of Recent
31001 messages.
31002 Normally, when such a folder is found, Alpine will ask
31003 whether you wish to open the folder. If this feature is set, Alpine will
31004 automatically open the folder without prompting.
31005 <P>
31006 This feature also affects some other similar situations.
31007 If you have a
31008 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
31009 that is equal to one of the "separate-" values, and you are
31010 viewing a thread; then when you type the NextNew command and are at the
31011 end of the current thread you will automatically go to the next thread
31012 if this feature is set.
31013 By default, you would be asked if you want to view the next thread.
31014 You will also be asked at times whether or not you want to view the next
31015 thread after you delete the last message in the thread.
31016 Setting this feature will also cause that question to be skipped.
31017 <P>
31019 <UL>
31020 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31021 </UL><P>
31022 <End of help on this topic>
31023 </BODY>
31024 </HTML>
31025 ====== h_config_auto_include_reply =====
31026 <HTML>
31027 <HEAD>
31028 <TITLE>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></TITLE>
31029 </HEAD>
31030 <BODY>
31031 <H1>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></H1>
31033 This feature controls an aspect of Alpine's Reply command. Normally, Alpine
31034 will ask whether you wish to include the original message in your reply.
31035 If this feature is set and the feature
31036 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
31037 is <EM>not</EM> set, then the original message will be included in the reply
31038 automatically, without prompting.
31039 <P>
31040 <End of help on this topic>
31041 </BODY>
31042 </HTML>
31043 ====== h_config_select_in_bold =====
31044 <HTML>
31045 <HEAD>
31046 <TITLE>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></TITLE>
31047 </HEAD>
31048 <BODY>
31049 <H1>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></H1>
31051 This feature controls an aspect of Alpine's
31052 <A HREF="h_config_enable_agg_ops">"aggregate operation"</A>
31053 commands; in
31054 particular, the Select and WhereIs commands. Select and WhereIs (with the
31055 ^X subcommand) will search the current folder for messages meeting a
31056 specified criteria, and "tag" the resulting messages with an
31057 "X" in the
31058 first column of the applicable lines in the MESSAGE INDEX. If this feature
31059 is set, instead of using the "X" to denote a selected message,
31060 Alpine will
31061 attempt to display those index lines in boldface. Whether this is
31062 preferable to the "X" will depend on personal taste and the type of
31063 terminal being used.
31064 <P>
31065 <UL>
31066 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31067 </UL><P>
31068 <End of help on this topic>
31069 </BODY>
31070 </HTML>
31071 ====== h_config_alt_auth =====
31072 <HTML>
31073 <HEAD>
31074 <TITLE>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></TITLE>
31075 </HEAD>
31076 <BODY>
31077 <H1>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></H1>
31079 This feature affects how Alpine connects to IMAP servers.
31080 It's utility has largely been overtaken by events,
31081 but it may still be useful in some circumstances.
31082 If you only connect to modern IMAP servers that support
31083 "TLS" you can ignore this feature.
31085 <P>
31086 Details:
31088 <P>
31089 By default, Alpine will attempt to connect to an IMAP server on the
31090 normal IMAP service port (143), and if the server offers "Transport Layer
31091 Security" (TLS) and Alpine has been compiled with encryption capability,
31092 then a secure (encrypted) session will be negotiated.
31094 <P>
31095 With this feature enabled, before connecting on the normal IMAP port, Alpine
31096 will first attempt to connect to an alternate IMAP service port (993) used
31097 specifically for encrypted IMAP sessions via the Secure Sockets Layer
31098 (SSL) method.
31099 If the SSL attempt fails, Alpine will then try the default
31100 behavior described in the previous paragraph.
31102 <P>
31103 TLS negotiation on the normal port is preferred, and supersedes the use of
31104 SSL on port 993, but older servers may not provide TLS support.
31105 This feature may be convenient when accessing IMAP servers that do not support
31106 TLS, but do support SSL connections on port 993.
31107 However, it is important to understand that with this feature enabled,
31108 Alpine will <EM>attempt</EM> to make a secure connection if that is possible,
31109 but it will proceed to make an insecure connection if that is the only
31110 option offered by the server, or if the Alpine in question has been built
31111 without encryption capability.
31113 <P>
31114 Note that this feature specifies a per-user (or system-wide) default
31115 behavior, but host/folder specification flags may be used to control the
31116 behavior of any specific connection.
31117 This feature interacts with some of
31118 the possible host/folder path specification flags as follows:
31120 <P>
31121 The <SAMP>/tls</SAMP> host flag, for example,
31123 <P>
31124 <CENTER><SAMP>{foo.example.com/tls}INBOX</SAMP></CENTER>
31125 <P>
31126 will over-ride this feature for the specified host by bypassing the
31127 SSL connection attempt.
31128 Moreover, with <SAMP>/tls</SAMP> specified,
31129 the connection attempt will fail if the
31130 service on port 143 does not offer TLS support.
31132 <P>
31133 The <SAMP>/ssl</SAMP> host flag, for example,
31135 <P>
31136 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
31137 <P>
31138 will insist on an SSL connection for the specified host,
31139 and will fail if the SSL service on port 993 is not available.
31140 Alpine will not subsequently retry a connection
31141 on port 143 if <SAMP>/ssl</SAMP> is specified.
31143 <P>
31144 <UL>
31145 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31146 </UL><P>
31147 <End of help on this topic>
31148 </BODY>
31149 </HTML>
31150 ====== h_config_file_dir ======
31151 <HTML>
31152 <HEAD>
31153 <TITLE>OPTION: File Directory</TITLE>
31154 </HEAD>
31155 <BODY>
31156 <H1>OPTION: File Directory</H1>
31158 PC-Alpine only.
31159 <P>
31160 This value affects the Composer's "^J Attach" command,
31161 the Attachment Index Screen's "S Save" command, and the
31162 Message Index's "E Export" command.
31164 <P>
31165 Normally, when a filename is supplied that lacks a leading "path"
31166 component, Alpine assumes the file exists in the user's home directory.
31167 Under Windows operating systems, this definition isn't always clear. This
31168 feature allows you to explictly set where Alpine should look for files
31169 without a leading path.
31171 <P>
31172 NOTE: this feature's value is ignored if either
31173 <A HREF="h_config_use_current_dir"><!--#echo var="FEAT_use-current-dir"--></A> feature
31174 is set or the PINERC has a value for the "<!--#echo var="VAR_operating-dir"-->" variable.
31176 <P>
31177 <UL>
31178 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31179 </UL><P>
31180 <End of help on this topic>
31181 </BODY>
31182 </HTML>
31183 ====== h_config_quote_all_froms =====
31184 <HTML>
31185 <HEAD>
31186 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></TITLE>
31187 </HEAD>
31188 <BODY>
31189 <H1>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></H1>
31191 This feature controls an aspect of the Save command (and also the way
31192 outgoing messages are saved to an FCC folder). If set, Alpine will add
31193 a leading ">" character in front of message lines beginning with "From"
31194 when they are saved to another folder, including lines syntactically
31195 distinguishable from the type of message separator line commonly used on
31196 Unix systems.
31198 <P>
31199 The default behavior is that a ">" will be prepended only to lines
31200 beginning with "From " that might otherwise be confused with a message
31201 separator line on Unix systems. If pine is the only mail program you use,
31202 this default is reasonable. If another program you use has trouble
31203 displaying a message with an unquoted "From " saved by Alpine, you should
31204 enable this feature. This feature only applies to the common Unix mailbox
31205 format that uses message separator lines beginning with "From ". If
31206 Alpine has been configured to use a different mailbox format (possibly
31207 incompatible with other mail programs), then this issue does not arise,
31208 and the feature is irrelevant.
31210 <P>
31211 <End of help on this topic>
31212 </BODY>
31213 </HTML>
31214 ====== h_config_normal_color =====
31215 <HTML>
31216 <HEAD>
31217 <TITLE>OPTION: Normal Color</TITLE>
31218 </HEAD>
31219 <BODY>
31220 <H1>OPTION: Normal Color</H1>
31222 Sets the color Alpine normally uses.
31223 The foreground color is the color of the actual character and the
31224 background color is the color of the area behind the character.
31225 By default this color is black characters on a white background.
31226 <P>
31227 <A HREF="h_color_setup">Descriptions of the available commands</A>
31228 <P>
31229 Look <A HREF="h_edit_nav_cmds">here</A>
31230 to see the available Editing and Navigation commands.
31231 <P>
31232 <End of help on this topic>
31233 </BODY>
31234 </HTML>
31235 ====== h_config_reverse_color =====
31236 <HTML>
31237 <HEAD>
31238 <TITLE>OPTION: Reverse Color</TITLE>
31239 </HEAD>
31240 <BODY>
31241 <H1>OPTION: Reverse Color</H1>
31243 Sets the color Alpine uses for reverse video characters.
31244 The foreground color is the color of the actual character and the
31245 background color is the color of the area behind the character.
31246 <P>
31247 <A HREF="h_color_setup">Descriptions of the available commands</A>
31248 <P>
31249 Look <A HREF="h_edit_nav_cmds">here</A>
31250 to see the available Editing and Navigation commands.
31251 <P>
31252 <End of help on this topic>
31253 </BODY>
31254 </HTML>
31255 ====== h_config_title_color =====
31256 <HTML>
31257 <HEAD>
31258 <TITLE>OPTION: Title Color</TITLE>
31259 </HEAD>
31260 <BODY>
31261 <H1>OPTION: Title Color</H1>
31263 Sets the color Alpine uses for the titlebar (the top line on the screen).
31264 The foreground color is the color of the actual character and the
31265 background color is the color of the area behind the character.
31266 By default, the Title Color is black characters on a yellow background.
31267 <P>
31268 The actual titlebar color may be different from the Title Color if
31269 the option
31270 <A HREF="h_config_titlebar_color_style">"<!--#echo var="VAR_titlebar-color-style"-->"</A>
31271 is set to some value other than the default.
31272 It may also be different if the current folder is closed and the
31273 <A HREF="h_config_titleclosed_color">Title Closed Color</A>
31274 color is set to something different from the Title Color.
31275 <P>
31276 <A HREF="h_color_setup">Descriptions of the available commands</A>
31277 <P>
31278 Look <A HREF="h_edit_nav_cmds">here</A>
31279 to see the available Editing and Navigation commands.
31280 <P>
31281 <End of help on this topic>
31282 </BODY>
31283 </HTML>
31284 ====== h_config_titleclosed_color =====
31285 <HTML>
31286 <HEAD>
31287 <TITLE>OPTION: Title Closed Color</TITLE>
31288 </HEAD>
31289 <BODY>
31290 <H1>OPTION: Title Closed Color</H1>
31292 Sets the color Alpine uses for the titlebar (the top line on the screen)
31293 when the current folder is closed.
31294 The foreground color is the color of the actual character and the
31295 background color is the color of the area behind the character.
31296 By default, the Title Color Closed Color is white characters on a red background.
31297 <P>
31298 By setting this color to something noticeable you will be alerted to the
31299 fact that the current folder is closed, perhaps unexpectedly.
31300 <P>
31301 <End of help on this topic>
31302 </BODY>
31303 </HTML>
31304 ====== h_config_status_color =====
31305 <HTML>
31306 <HEAD>
31307 <TITLE>OPTION: Status Color</TITLE>
31308 </HEAD>
31309 <BODY>
31310 <H1>OPTION: Status Color</H1>
31312 Sets the color Alpine uses for status messages written to the message
31313 line near the bottom of the screen.
31314 The foreground color is the color of the actual character and the
31315 background color is the color of the area behind the character.
31316 By default, the Status Color is the same as the Reverse Color.
31317 <P>
31318 <A HREF="h_color_setup">Descriptions of the available commands</A>
31319 <P>
31320 Look <A HREF="h_edit_nav_cmds">here</A>
31321 to see the available Editing and Navigation commands.
31322 <P>
31323 <End of help on this topic>
31324 </BODY>
31325 </HTML>
31326 ====== h_config_index_opening_color =====
31327 <HTML>
31328 <HEAD>
31329 <TITLE>OPTION: Index Opening Color</TITLE>
31330 </HEAD>
31331 <BODY>
31332 <H1>OPTION: Index Opening Color</H1>
31334 With some setups the text of the subject is followed
31335 by the opening text of the message if there is any room available in the index line.
31336 If you have configured your
31337 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
31338 to include one of the Subject tokens that causes this behavior
31339 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), you may set the color of
31340 this opening text with this option.
31341 This coloring takes place for all but the current index line, and the Opening
31342 Color appears to be in front of any color from an Index Color Rule.
31343 <P>
31344 By default the Index Opening Color is gray characters on a white background.
31346 <P>
31347 <A HREF="h_color_setup">Descriptions of the available commands</A>
31348 <P>
31349 Look <A HREF="h_edit_nav_cmds">here</A>
31350 to see the available Editing and Navigation commands.
31351 <P>
31352 <End of help on this topic>
31353 </BODY>
31354 </HTML>
31355 ====== h_config_index_pri_color =====
31356 <HTML>
31357 <HEAD>
31358 <TITLE>OPTION: Index Priority Symbol Colors</TITLE>
31359 </HEAD>
31360 <BODY>
31361 <H1>OPTION: Index Priority Symbol Colors</H1>
31363 The X-Priority header is a non-standard header that is used in a
31364 somewhat standard way by many mail programs.
31365 Alpine expects the value of this header to be a digit with a value
31366 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
31367 Alpine can be made to display an indication of this priority in
31368 messages by use of one of the tokens
31369 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
31370 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
31371 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
31373 <P>
31374 You may set the color used to draw these tokens by use of the colors
31375 Index High Priority Symbol Color and Index Low Priority Symbol Color.
31376 This coloring takes place for all but the current index line, and the Priority
31377 Color appears to be in front of any color from an Index Color Rule.
31378 If the priority has a value of 1 or 2 the High Priority color will be
31379 used,
31380 and if the value is 4 or 5 the Low Priority color will be used.
31381 <P>
31382 If you don't set these colors the index line will be colored in the same color as
31383 the bulk of the index line.
31385 <P>
31386 <A HREF="h_color_setup">Descriptions of the available commands</A>
31387 <P>
31388 Look <A HREF="h_edit_nav_cmds">here</A>
31389 to see the available Editing and Navigation commands.
31390 <P>
31391 <End of help on this topic>
31392 </BODY>
31393 </HTML>
31394 ====== h_config_index_subject_color =====
31395 <HTML>
31396 <HEAD>
31397 <TITLE>OPTION: Index Subject Color</TITLE>
31398 </HEAD>
31399 <BODY>
31400 <H1>OPTION: Index Subject Color</H1>
31402 You may set the color used to draw the Subject part of the index line.
31403 This coloring takes place for all but the current index line, and the Subject
31404 Color appears to be in front of any color from an Index Color Rule.
31405 <P>
31406 If you don't set this color it will be colored in the same color as
31407 the bulk of the index line.
31409 <P>
31410 <A HREF="h_color_setup">Descriptions of the available commands</A>
31411 <P>
31412 Look <A HREF="h_edit_nav_cmds">here</A>
31413 to see the available Editing and Navigation commands.
31414 <P>
31415 <End of help on this topic>
31416 </BODY>
31417 </HTML>
31418 ====== h_config_index_from_color =====
31419 <HTML>
31420 <HEAD>
31421 <TITLE>OPTION: Index From Color</TITLE>
31422 </HEAD>
31423 <BODY>
31424 <H1>OPTION: Index From Color</H1>
31426 You may set the color used to draw the From part of the index line.
31427 This coloring takes place for all but the current index line, and the From
31428 Color appears to be in front of any color from an Index Color Rule.
31429 <P>
31430 If you don't set this color it will be colored in the same color as
31431 the bulk of the index line.
31433 <P>
31434 <A HREF="h_color_setup">Descriptions of the available commands</A>
31435 <P>
31436 Look <A HREF="h_edit_nav_cmds">here</A>
31437 to see the available Editing and Navigation commands.
31438 <P>
31439 <End of help on this topic>
31440 </BODY>
31441 </HTML>
31442 ====== h_config_index_arrow_color =====
31443 <HTML>
31444 <HEAD>
31445 <TITLE>OPTION: Index Arrow Color</TITLE>
31446 </HEAD>
31447 <BODY>
31448 <H1>OPTION: Index Arrow Color</H1>
31450 If you have configured your
31451 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
31452 to include the "ARROW" token, you may set the color of
31453 the arrow displayed with this option.
31454 If you don't set the color it will be colored in the same color as
31455 the bulk of the index line.
31457 <P>
31458 <A HREF="h_color_setup">Descriptions of the available commands</A>
31459 <P>
31460 Look <A HREF="h_edit_nav_cmds">here</A>
31461 to see the available Editing and Navigation commands.
31462 <P>
31463 <End of help on this topic>
31464 </BODY>
31465 </HTML>
31466 ====== h_config_index_color =====
31467 <HTML>
31468 <HEAD>
31469 <TITLE>OPTION: Index Colors</TITLE>
31470 </HEAD>
31471 <BODY>
31472 <H1>OPTION: Index Colors</H1>
31474 You may add color to the single character symbols that give the status
31475 of each message in the MESSAGE INDEX.
31476 By default the characters "+", "*", "D",
31477 "A", and "N" show up near the left hand side of the
31478 screen depending on whether the message is addressed to you, and whether
31479 the message is marked Important, is Deleted, is Answered, or is New.
31480 The color for each of those characters may be specified by setting the
31481 "Index-to-me" Symbol Color,
31482 the "Index-important" Symbol Color,
31483 the "Index-deleted" Symbol Color,
31484 the "Index-answered" Symbol Color,
31485 and the "Index-new" Symbol Color.
31486 There are also two other symbol colors called "Index-recent"
31487 and "Index-unseen".
31488 These two colors will only be used if you have configured your
31489 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
31490 to include the "IMAPSTATUS" or "SHORTIMAPSTATUS" token.
31491 <P>
31492 The default colors for these symbols are:
31493 <TABLE>
31494 <TR> <TD> Index-to-me </TD> <TD> black on cyan </TD> </TR>
31495 <TR> <TD> Index-important </TD> <TD> white on bright red </TD> </TR>
31496 <TR> <TD> Index-deleted </TD> <TD> same as Normal Color </TD> </TR>
31497 <TR> <TD> Index-answered </TD> <TD> bright red on yellow </TD> </TR>
31498 <TR> <TD> Index-new </TD> <TD> white on magenta </TD> </TR>
31499 <TR> <TD> Index-recent </TD> <TD> same as Normal Color </TD> </TR>
31500 <TR> <TD> Index-unseen </TD> <TD> same as Normal Color </TD> </TR>
31501 </TABLE>
31502 <P>
31503 Besides coloring the message status symbols, you may also color the
31504 entire index line.
31505 This is done by using the
31506 <A HREF="h_rules_incols">SETUP INDEX LINE COLORS</A> screen, which you
31507 may get to with the commands <EM>S</EM>etup/<EM>R</EM>ules/<EM>I</EM>ndexcolor.
31508 When the entire line is colored that color will be "behind" the
31509 status symbol colors talked about in the paragraph above.
31510 <P>
31511 You may also color
31512 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
31513 in the index using the
31514 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>);
31515 the <A HREF="h_config_index_arrow_color">ARROW</A> cursor;
31516 the Subject using
31517 <A HREF="h_config_index_subject_color">Index Subject Color</A>;
31518 the From field using
31519 <A HREF="h_config_index_from_color">Index From Color</A>;
31520 and the
31521 <A HREF="h_config_index_opening_color">Index Opening</A> text.
31522 <P>
31523 <A HREF="h_color_setup">Descriptions of the available commands</A>
31524 <P>
31525 Look <A HREF="h_edit_nav_cmds">here</A>
31526 to see the available Editing and Navigation commands.
31527 <P>
31528 <End of help on this topic>
31529 </BODY>
31530 </HTML>
31531 ====== h_config_metamsg_color =====
31532 <HTML>
31533 <HEAD>
31534 <TITLE>OPTION: Meta-Message Color</TITLE>
31535 </HEAD>
31536 <BODY>
31537 <H1>OPTION: Meta-Message Color</H1>
31539 Sets the color Alpine uses in the MESSAGE TEXT screen for messages to you
31540 that aren't part of the message itself.
31541 For example, an attachment that isn't shown might produce a meta
31542 message something like:
31543 <P>
31544 <CENTER><SAMP> [ Part 2, "comment" Text/PLAIN (Name: "file") ]</SAMP></CENTER>
31545 <P>
31546 If you set the
31547 <A HREF="h_config_quote_suppression"><!--#echo var="VAR_quote-suppression-threshold"--></A>
31548 option you might see
31549 <P>
31550 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
31551 <P>
31552 Warnings about suspicious looking URLs in HTML will also be colored
31553 with this color.
31554 <P>
31555 The foreground color is the color of the actual character and the
31556 background color is the color of the area behind the character.
31557 By default, the Meta-Message Color is black characters on a yellow background.
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_keylabel_color =====
31568 <HTML>
31569 <HEAD>
31570 <TITLE>OPTION: KeyLabel Color</TITLE>
31571 </HEAD>
31572 <BODY>
31573 <H1>OPTION: KeyLabel Color</H1>
31575 Sets the color Alpine uses for the labels of the keys in the two-line
31576 menu at the bottom of the screen.
31577 For example, some of the screens have a "P PrevMsg" command.
31578 This option sets the color used when displaying "PrevMsg".
31579 The foreground color is the color of the actual character and the
31580 background color is the color of the area behind the character.
31581 By default, the KeyLabel Color is the same as the Normal Color.
31582 <P>
31583 WARNING: Some terminal emulators have the property that the screen will scroll
31584 down one line whenever a character is written to the character cell in the
31585 lower right corner of the screen.
31586 Alpine can usually avoid writing a character in that corner of the screen.
31587 However, if you have defined a KeyLabel Color then Alpine does have to write
31588 a character in that cell in order to color the cell correctly.
31589 If you find that your display sometimes scrolls up a line this could be
31590 the problem.
31591 The most obvious symptom is probably that the titlebar at the top of the
31592 screen scrolls off the screen.
31593 Try setting KeyLabel Color to Default to see if that fixes the problem.
31594 <P>
31595 <A HREF="h_color_setup">Descriptions of the available commands</A>
31596 <P>
31597 Look <A HREF="h_edit_nav_cmds">here</A>
31598 to see the available Editing and Navigation commands.
31599 <P>
31600 <End of help on this topic>
31601 </BODY>
31602 </HTML>
31603 ====== h_config_keyname_color =====
31604 <HTML>
31605 <HEAD>
31606 <TITLE>OPTION: KeyName Color</TITLE>
31607 </HEAD>
31608 <BODY>
31609 <H1>OPTION: KeyName Color</H1>
31611 Sets the color Alpine uses for the names of the keys in the two-line
31612 menu at the bottom of the screen.
31613 For example, some of the screens have a "P PrevMsg" command.
31614 This option sets the color used when displaying the "P".
31615 The foreground color is the color of the actual character and the
31616 background color is the color of the area behind the character.
31617 By default, the KeyName Color is the same as the Reverse Color.
31618 <P>
31619 <A HREF="h_color_setup">Descriptions of the available commands</A>
31620 <P>
31621 Look <A HREF="h_edit_nav_cmds">here</A>
31622 to see the available Editing and Navigation commands.
31623 <P>
31624 <End of help on this topic>
31625 </BODY>
31626 </HTML>
31627 ====== h_config_slctbl_color =====
31628 <HTML>
31629 <HEAD>
31630 <TITLE>OPTION: Selectable Item Color</TITLE>
31631 </HEAD>
31632 <BODY>
31633 <H1>OPTION: Selectable Item Color</H1>
31635 Sets the color Alpine uses for selectable items, such as URLs.
31636 The foreground color is the color of the actual character and the
31637 background color is the color of the area behind the character.
31638 By default, the Selectable Item Color is the same as the Normal Color,
31639 except that it is bold.
31640 <P>
31641 <A HREF="h_color_setup">Descriptions of the available commands</A>
31642 <P>
31643 Look <A HREF="h_edit_nav_cmds">here</A>
31644 to see the available Editing and Navigation commands.
31645 <P>
31646 <End of help on this topic>
31647 </BODY>
31648 </HTML>
31649 ====== h_config_quote_color =====
31650 <HTML>
31651 <HEAD>
31652 <TITLE>OPTION: Quote Colors</TITLE>
31653 </HEAD>
31654 <BODY>
31655 <H1>OPTION: Quote Colors</H1>
31657 Sets the colors Alpine uses for coloring quoted text in the MESSAGE TEXT
31658 screen.
31659 If a line begins with a > character (or space followed by >)
31660 it is considered a quote.
31661 That line will be given the Quote1 Color (first level quote).
31662 If there is a second level of quoting then the Quote2 Color will be used.
31663 Alpine considers there to be a second level of quoting if that first > is
31664 followed by another > (or space followed by >).
31665 If there are characters other than whitespace and > signs, then it isn't
31666 considered another level of quoting.
31667 Similarly, if there is a third level of quoting the Quote3 Color will be
31668 used.
31669 If there are more levels after that the Quote Colors are re-used.
31670 If you define all three colors then it would repeat like Color1, Color2, Color3,
31671 Color1, Color2, Color3, ...
31672 If you only define the first two it would be
31673 Color1, Color2, Color1, Color2, ...
31674 If you define only the Quote1 Color, then the entire quote would be that
31675 color regardless of the quoting levels.
31676 By default, the Quote1 Color is black characters on a greenish-blue background;
31677 the Quote2 Color is black characters on a dull yellow background; and
31678 the Quote3 Color is black characters on a green background.
31679 <P>
31680 <A HREF="h_color_setup">Descriptions of the available commands</A>
31681 <P>
31682 Look <A HREF="h_edit_nav_cmds">here</A>
31683 to see the available Editing and Navigation commands.
31684 <P>
31685 <End of help on this topic>
31686 </BODY>
31687 </HTML>
31688 ====== h_config_folder_color =====
31689 <HTML>
31690 <HEAD>
31691 <TITLE>OPTION: Folder Color</TITLE>
31692 </HEAD>
31693 <BODY>
31694 <H1>OPTION: Folder Color</H1>
31696 Sets the colors Alpine uses for coloring a folder in the FOLDER LIST
31697 screen. By default, the Folder Color is the normal text color.
31699 <P>
31700 If you set a color for this feature, other than the normal color
31701 (the default), or a color for
31702 <A HREF="h_config_directory_color">Directory Color</A>, then directories
31703 will be colored according to the color specified in the
31704 <A HREF="h_config_directory_color">Directory Color</A> option. In this
31705 case, the color will be the only indication that the colored name
31706 refers to a directory. The normal behavior is that Alpine
31707 indicates that a name refers to a directory by appending a
31708 separator (like "/" or ".") to the name of
31709 the folder.
31711 <P>
31712 If a folder is a directory, then the folder name will be painted
31713 according to the color defined by this variable, and a separator
31714 indicator (like "/" or ".") will be added
31715 to the name. That
31716 indicator will be painted according to the color defined in the
31717 <A HREF="h_config_directory_color">Directory Color</A> option.
31719 <P>
31720 <End of help on this topic>
31721 </BODY>
31722 </HTML>
31723 ====== h_config_directory_color =====
31724 <HTML>
31725 <HEAD>
31726 <TITLE>OPTION: Directory Color</TITLE>
31727 </HEAD>
31728 <BODY>
31729 <H1>OPTION: Directory Color</H1>
31731 Sets the colors Alpine uses for coloring a directory in the FOLDER LIST
31732 screen. By default, the Folder Color is the normal text color.
31733 <P>
31734 If you set a color for this feature, other than the normal color
31735 (the default), or a color for
31736 <A HREF="h_config_folder_color">Folder Color</A>, then folders
31737 will be colored according to the color specified in the
31738 <A HREF="h_config_folder_color">Folder Color</A> option. In this
31739 case, the color will be the only indication that the colored name
31740 refers to a directory. The normal behavior is that Alpine
31741 indicates that a name refers to a directory by appending a
31742 separator (like "/" or ".") to the name of
31743 the folder.
31744 <P>
31745 If a folder is a directory, then the folder name will be painted
31746 according to the color defined by the option
31747 <A HREF="h_config_folder_color">Folder Color</A>, and the separator
31748 indicator (like "/" or ".") will be added
31749 after the name. That
31750 indicator will be painted according to the color defined in this
31751 option.
31752 <P>
31753 <End of help on this topic>
31754 </BODY>
31755 </HTML>
31756 ====== h_config_folder_list_color =====
31757 <HTML>
31758 <HEAD>
31759 <TITLE>OPTION: Folder-List Color</TITLE>
31760 </HEAD>
31761 <BODY>
31762 <H1>OPTION: Folder-List Color</H1>
31764 Sets the colors Alpine uses for coloring normal text in the FOLDER LIST
31765 screen. By default, the Folder-List Color is the normal text color.
31766 <P>
31767 This text refers to the informative text that Alpine displays so you
31768 can recognize each collection. The color of the content of each collection
31769 is determined by the options <A HREF="h_config_folder_color">Folder Color</A>
31770 and <A HREF="h_config_directory_color">Directory Color</A>.
31771 <P>
31772 Unlike the options
31773 <A HREF="h_config_folder_color">Folder Color</A>
31774 and <A HREF="h_config_directory_color">Directory Color</A>, configuring
31775 this option does not affect the way that Alpine reports folders,
31776 directories and folders that are directories.
31777 <P>
31778 <End of help on this topic>
31779 </BODY>
31780 </HTML>
31781 ====== h_config_incunseen_color =====
31782 <HTML>
31783 <HEAD>
31784 <TITLE>OPTION: Incoming Unseen Color</TITLE>
31785 </HEAD>
31786 <BODY>
31787 <H1>OPTION: Incoming Unseen Color</H1>
31789 If the option
31790 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
31791 is turned on it is possible to highlight the folders that contain
31792 unseen messages by coloring them with this color.
31793 By default, this is the same as the Normal Color and no highlighting is done.
31794 <P>
31795 Usually the "current" folder (the folder the cursor is on)
31796 is highlighted using reverse video.
31797 If the current folder is colored because it contains unseen messages then
31798 the color used to show that it is also the current folder is controlled
31799 by the
31800 <A HREF="h_config_index_color_style"><!--#echo var="VAR_current-indexline-style"--></A>
31801 feature at the top of the SETUP COLOR screen.
31802 <P>
31803 <A HREF="h_color_setup">Descriptions of the available commands</A>
31804 <P>
31805 Look <A HREF="h_edit_nav_cmds">here</A>
31806 to see the available Editing and Navigation commands.
31807 <P>
31808 <End of help on this topic>
31809 </BODY>
31810 </HTML>
31811 ====== h_config_signature_color =====
31812 <HTML>
31813 <HEAD>
31814 <TITLE>OPTION: Signature Color</TITLE>
31815 </HEAD>
31816 <BODY>
31817 <H1>OPTION: Signature Color</H1>
31819 Sets the color Alpine uses for coloring the signature in the MESSAGE TEXT
31820 screen. According to USENET conventions, the signature is defined as the
31821 paragraph following the "sigdashes", that is, the special line
31822 consisting of the three characters
31823 "-- " (i.e., dash, dash, and space). Alpine allows for one
31824 empty line right after the sigdashes to be considered as part of the
31825 signature.
31826 By default, the Signature Color is blue characters on a white background.
31827 <P>
31828 <A HREF="h_color_setup">Descriptions of the available commands</A>
31829 <P>
31830 Look <A HREF="h_edit_nav_cmds">here</A>
31831 to see the available Editing and Navigation commands.
31832 <P>
31833 <End of help on this topic>
31834 </BODY>
31835 </HTML>
31836 ====== h_config_prompt_color =====
31837 <HTML>
31838 <HEAD>
31839 <TITLE>OPTION: Prompt Color</TITLE>
31840 </HEAD>
31841 <BODY>
31842 <H1>OPTION: Prompt Color</H1>
31844 Sets the color Alpine uses for confirmation prompts and questions that
31845 appear in the status line near the bottom of the screen.
31846 The foreground color is the color of the actual character and the
31847 background color is the color of the area behind the character.
31848 By default, the Prompt Color is the same as the Reverse Color.
31849 <P>
31850 <A HREF="h_color_setup">Descriptions of the available commands</A>
31851 <P>
31852 Look <A HREF="h_edit_nav_cmds">here</A>
31853 to see the available Editing and Navigation commands.
31854 <P>
31855 <End of help on this topic>
31856 </BODY>
31857 </HTML>
31858 ====== h_config_header_general_color =====
31859 <HTML>
31860 <HEAD>
31861 <TITLE>OPTION: Header General Color</TITLE>
31862 </HEAD>
31863 <BODY>
31864 <H1>OPTION: Header General Color</H1>
31866 Sets the color Alpine uses for the headers of a message in the MESSAGE TEXT
31867 screen.
31868 The foreground color is the color of the actual character and the
31869 background color is the color of the area behind the character.
31870 By default, this is the same as the Normal Color.
31871 <P>
31872 It is also possible to set the colors for specific header fields, for
31873 example the Subject, using
31874 <A HREF="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></A>.
31875 If both a Header General Color and a specific Viewer Header Color are set
31876 the specific color will override the general color, as you would expect.
31877 <P>
31878 <A HREF="h_color_setup">Descriptions of the available commands</A>
31879 <P>
31880 Look <A HREF="h_edit_nav_cmds">here</A>
31881 to see the available Editing and Navigation commands.
31882 <P>
31883 <End of help on this topic>
31884 </BODY>
31885 </HTML>
31886 ====== h_config_incol =====
31887 <HTML>
31888 <HEAD>
31889 <TITLE>Index Line Color</TITLE>
31890 </HEAD>
31891 <BODY>
31892 <H1>Index Line Color</H1>
31894 This option is used to set the color of a line in the index when the
31895 message for that line matches the Pattern.
31896 This colors the whole index line, except possibly the status letters,
31897 which may be colored separately using the
31898 <A HREF="h_color_setup">Setup Kolor</A> screen.
31899 The foreground color is the color of the actual characters and the
31900 background color is the color of the area behind the characters.
31901 <P>
31902 <A HREF="h_color_setup">Descriptions of the available commands</A>
31903 <P>
31904 Look <A HREF="h_edit_nav_cmds">here</A>
31905 to see the available Editing and Navigation commands.
31906 <P>
31907 <End of help on this topic>
31908 </BODY>
31909 </HTML>
31910 ====== h_config_usetransparent_color =====
31911 <HTML>
31912 <HEAD>
31913 <TITLE>OPTION: Use Transparent Color</TITLE>
31914 </HEAD>
31915 <BODY>
31916 <H1>OPTION: Use Transparent Color</H1>
31918 This is a special color supported by some terminal emulators.
31919 It is intended to result in the default foreground or background color
31920 from the terminal emulator.
31921 This is the color the terminal was displaying characters in before you started Alpine.
31922 The reason it is called Transparent is because you could set the foreground color
31923 to some specific color, like Red, and then set the background color to the
31924 Transparent Color. If it works as expected, the background color from the terminal
31925 window in which Alpine is running will show through but with the Red characters
31926 in the foreground.
31927 <P>
31928 <A HREF="h_color_setup">Descriptions of the available commands</A>
31929 <P>
31930 Look <A HREF="h_edit_nav_cmds">here</A>
31931 to see the available Editing and Navigation commands.
31932 <P>
31933 <End of help on this topic>
31934 </BODY>
31935 </HTML>
31936 ====== h_config_usenormal_color =====
31937 <HTML>
31938 <HEAD>
31939 <TITLE>OPTION: Use Normal Color</TITLE>
31940 </HEAD>
31941 <BODY>
31942 <H1>OPTION: Use Normal Color</H1>
31944 When you use this color value, the actual color used will be the same
31945 as the corresponding Normal Color.
31946 For example if your Normal Color is black on white and you set both
31947 the foreground and background colors here to use the Normal Color, you'll
31948 get black on white. If you later change the Normal Color to red on blue
31949 this color will also change to red on blue.
31950 <P>
31951 <A HREF="h_color_setup">Descriptions of the available commands</A>
31952 <P>
31953 Look <A HREF="h_edit_nav_cmds">here</A>
31954 to see the available Editing and Navigation commands.
31955 <P>
31956 <End of help on this topic>
31957 </BODY>
31958 </HTML>
31959 ====== h_config_usenone_color =====
31960 <HTML>
31961 <HEAD>
31962 <TITLE>OPTION: Use None Color</TITLE>
31963 </HEAD>
31964 <BODY>
31965 <H1>OPTION: Use None Color</H1>
31967 This is a special color that simply means to leave the color alone.
31968 It is useful for Index symbols and for Keyword Colors used in the Subject
31969 field of an index line.
31970 The most likely use is to set an explicit foreground color and then set
31971 the background color to the None Color.
31972 That will cause the symbol or keyword to be drawn in the foreground color
31973 with a background equal to whatever color the rest of the index line is already
31974 drawn in.
31975 You will see no visible effect unless you have assigned Indexcolor Rules to
31976 color index lines or you have set an actual color for the Reverse Color.
31977 <P>
31978 <A HREF="h_color_setup">Descriptions of the available commands</A>
31979 <P>
31980 Look <A HREF="h_edit_nav_cmds">here</A>
31981 to see the available Editing and Navigation commands.
31982 <P>
31983 <End of help on this topic>
31984 </BODY>
31985 </HTML>
31986 ====== h_config_dflt_color =====
31987 <HTML>
31988 <HEAD>
31989 <TITLE>OPTION: Default Color</TITLE>
31990 </HEAD>
31991 <BODY>
31992 <H1>OPTION: Default Color</H1>
31994 Setting default will cause the color to be the default color.
31995 Unsetting default is normally done by choosing a color, but in some cases
31996 you may want to declare the current default color to be your non-default
31997 choice.
31998 For example, the default Keyname Color is the same as the Reverse Color.
31999 Whenever the Reverse Color changes the Keyname Color will also change, unless
32000 you've changed it or unset the default box.
32001 <P>
32002 <A HREF="h_color_setup">Descriptions of the available commands</A>
32003 <P>
32004 Look <A HREF="h_edit_nav_cmds">here</A>
32005 to see the available Editing and Navigation commands.
32006 <P>
32007 <End of help on this topic>
32008 </BODY>
32009 </HTML>
32010 ====== h_config_bold_slctbl =====
32011 <HTML>
32012 <HEAD>
32013 <TITLE>OPTION: Bold</TITLE>
32014 </HEAD>
32015 <BODY>
32016 <H1>OPTION: Bold</H1>
32018 The color for this particular section may have the Bold attribute turned
32019 on or off.
32020 Setting bold will cause the characters to be bold.
32021 <P>
32022 <A HREF="h_color_setup">Descriptions of the available commands</A>
32023 <P>
32024 Look <A HREF="h_edit_nav_cmds">here</A>
32025 to see the available Editing and Navigation commands.
32026 <P>
32027 <End of help on this topic>
32028 </BODY>
32029 </HTML>
32030 ====== h_config_kw_color =====
32031 <HTML>
32032 <HEAD>
32033 <TITLE>OPTION: Keyword Colors</TITLE>
32034 </HEAD>
32035 <BODY>
32036 <H1>OPTION: Keyword Colors</H1>
32038 Sets the colors Alpine uses for Keyword fields in the MESSAGE INDEX screen.
32039 Keywords are displayed as part of the Subject by default.
32040 They are also displayed as part of the Subject if the tokens
32041 "SUBJKEY", "SUBJKEYTEXT", "SUBJKEYINIT", or "SUBJKEYINITTEXT" are used in the
32042 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
32043 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
32044 screen by using the "KEY" or "KEYINIT" tokens.
32045 <P>
32046 For example, you might have set up a Keyword
32047 "Work" using the
32048 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
32049 You could cause that Keyword to show up as a special color
32050 by setting up the Keyword Color using this option, and then including it
32051 in the MESSAGE INDEX screen using one of the tokens listed above in the
32052 <!--#echo var="VAR_index-format"-->.
32053 <P>
32054 <A HREF="h_color_setup">Descriptions of the available commands</A>
32055 <P>
32056 Look <A HREF="h_edit_nav_cmds">here</A>
32057 to see the available Editing and Navigation commands.
32058 <P>
32059 <End of help on this topic>
32060 </BODY>
32061 </HTML>
32062 ====== h_config_customhdr_color =====
32063 <HTML>
32064 <HEAD>
32065 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></TITLE>
32066 </HEAD>
32067 <BODY>
32068 <H1>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></H1>
32070 Sets the colors Alpine uses for specific header fields in the MESSAGE TEXT screen.
32071 For example, you may set the color of the Subject header or the From header.
32072 The foreground color is the color of the actual character and the
32073 background color is the color of the area behind the character.
32074 <P>
32075 In addition to setting the colors for particular headers (like the Subject)
32076 you may also set a color to be used for all headers unless overridden by a
32077 more specific Viewer Header Color.
32078 To do this use the
32079 <A HREF="h_config_header_general_color">Header General Color</A>.
32080 <P>
32081 For Header Colors,
32082 there is an additional line on the
32083 screen labeled "Pattern to match".
32084 If you leave that blank, then the whole field for that header will
32085 be colored.
32086 However, if you give a pattern to match, the coloring will only take place
32087 if there is a match for that pattern in the value of the field.
32088 For example, if you are working on a color for the Subject header and
32089 you fill in a pattern of "important", then only Subjects that
32090 contain the word "important" will be colored.
32091 <P>
32092 If the pattern you enter is a comma-separated list of patterns, then coloring
32093 happens if any of those patterns matches.
32094 <P>
32095 <A HREF="h_color_setup">Descriptions of the available commands</A>
32096 <P>
32097 Look <A HREF="h_edit_nav_cmds">here</A>
32098 to see the available Editing and Navigation commands.
32099 <P>
32100 <End of help on this topic>
32101 </BODY>
32102 </HTML>
32103 ====== h_config_indextoken_color =====
32104 <HTML>
32105 <HEAD>
32106 <TITLE>OPTION: <!--#echo var="VAR_index-token-colors"--></TITLE>
32107 </HEAD>
32108 <BODY>
32109 <H1>OPTION: <!--#echo var="VAR_index-token-colors"--></H1>
32111 This option allows you to set up the color in which any token, not specified by the
32112 previous options, will be colored in the MESSAGE INDEX screen.
32113 <P>
32114 In order to use this option, you must press the "I" <B>IndxHdr</B> command, and add
32115 a token that can be used in the index format.
32116 The list of available tokens is <A HREF="h_index_tokens">here</A>.
32117 <P>
32118 If you fail to enter a valid token your entry will be ignored, and you will be asked to
32119 enter a new one. Once you have entered a valid token, a line will be added to the
32120 configuration screen that you can use to set up the colors in which that token will
32121 be painted. This is done in the same way that you configure colors for other
32122 variables.
32124 <A HREF="h_color_setup">Descriptions of the available commands</A>
32125 <P>
32126 Look <A HREF="h_edit_nav_cmds">here</A>
32127 to see the available Editing and Navigation commands.
32128 <P>
32129 <End of help on this topic>
32130 </BODY>
32131 </HTML>
32132 ====== h_config_customhdr_pattern =====
32133 <HTML>
32134 <HEAD>
32135 <TITLE>OPTION: Viewer Header Color Pattern</TITLE>
32136 </HEAD>
32137 <BODY>
32138 <H1>OPTION: Viewer Header Color Pattern</H1>
32140 If you leave this blank, then the whole field for the header will
32141 be colored.
32142 If you give a pattern to match, the coloring will only take place
32143 if there is a match for that pattern in the value of the field.
32144 For example, if you are working on a color for the Subject header and
32145 you fill in a pattern of "important", then only Subjects that
32146 contain the word "important" will be colored.
32147 <P>
32148 For address headers (like From and To) and for the Newsgroups header,
32149 a pattern match will cause only the matched addresses or newsgroups to be
32150 colored.
32151 If there is no pattern to match, then all of the addresses or newsgroups
32152 in the relevant header will be colored.
32153 <P>
32154 The matching pattern may be a comma-separated list of patterns to match
32155 instead of a single pattern.
32156 For example, you could use the pattern "important,urgent" which would
32157 cause a match if either the word "important" or the word
32158 "urgent" appeared in the value of the header.
32159 You could list several comma-separated email addresses in the Header
32160 From Color pattern so that those addresses will be colored when any of
32161 them appear in the From header.
32162 <P>
32163 To add a new matching pattern or change the existing pattern use the
32164 <!--chtml if pinemode="function_key"-->
32165 "F4"
32166 <!--chtml else-->
32167 "C"
32168 <!--chtml endif-->
32169 "Change" command that is available when the "Pattern to
32170 match" line is highlighted.
32171 The
32172 <!--chtml if pinemode="function_key"-->
32173 "F10"
32174 <!--chtml else-->
32175 "D"
32176 <!--chtml endif-->
32177 "Delete" command may be used to quickly remove all patterns
32178 for a particular header.
32179 <P>
32180 <End of help on this topic>
32181 </BODY>
32182 </HTML>
32183 ====== h_color_setup =====
32184 <HTML>
32185 <HEAD>
32186 <TITLE>SETUP COLOR COMMANDS</TITLE>
32187 </HEAD>
32188 <BODY>
32189 <H1>SETUP COLOR COMMANDS</H1>
32190 <!--chtml if pinemode="function_key"-->
32191 <PRE>
32192 Available Commands -- Group 1
32193 -------------------------------
32194 F1 Display this help text
32195 F2 Show other available commands
32196 F3 Exit to MAIN MENU
32197 F4 Select the highlighted foreground or background color
32198 F5 Move to previous line
32199 F6 Move to next line
32200 F7 Previous page
32201 F8 Next page
32202 F9 Add a config section for a header field
32203 F10 Restore all default colors (for all sections)
32204 F11 Print color configuration screen
32205 F12 Whereis (search for word)
32207 Available Commands -- Group 2
32208 -------------------------------
32209 F1 Display this help text
32210 F2 Show other available commands
32211 F5 Delete config section for highlighted header field
32212 F6 Shuffle the order of Header Color sections
32213 </PRE>
32214 <!--chtml else-->
32215 <PRE>
32216 General commands
32217 -------------------------------------------------
32218 ? Display this help text E Exit back to MAIN MENU
32219 P Previous Line N Next Line
32220 - Previous page Spc (space bar) Next page
32221 W WhereIs (search for word) % Print color configuration screen
32223 Color Setup Commands
32224 ------------------------------------------------
32225 * Select the highlighted foreground or background color
32226 A Add a config section for a header field
32227 D Delete config section for highlighted header field
32228 R Restore all default colors (for all sections)
32229 $ Shuffle the order of Header Color sections
32230 </PRE>
32231 <!--chtml endif-->
32233 <H2>Description of the Setup Color Screen</H2>
32235 From this screen you may turn on color and set the colors of
32236 various parts of the Alpine display.
32237 For help on turning on color move your cursor into the Color Style section
32238 at the top of the Setup Color screen and ask for help.
32240 <P>
32241 There are several sections in the Setup Color Screen.
32242 At the top are some settings that handle the style of color used
32243 with your terminal emulator (UNIX only), and some settings that
32244 control how the current indexline and the titlebar are colored.
32245 After that comes a long section called GENERAL COLORS that allows
32246 you to set the color of many elements in the Alpine screens.
32247 For example, the color of the titlebar, status messages,
32248 selectable links, quotes and signatures in messages, and so on.
32249 After that is a section called INDEX COLORS that allows you to
32250 set the colors of various pieces of the displayed index lines in
32251 the MESSAGE INDEX screen.
32252 The next section is HEADER COLORS. This is for coloring headers of
32253 messages in the MESSAGE TEXT screen in just about any way you would like.
32254 Finally, the KEYWORD COLORS section allows you to highlight
32255 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
32256 in the MESSAGE INDEX screen.
32258 <P>
32259 To change a color, highlight the color you want to change (for example,
32260 the Status Color) by moving
32261 the cursor into it.
32262 You may want to read the help text for the color to see a brief desription
32263 of what you are coloring.
32264 Then press "C" for Change to set the color to something new.
32265 That will put you into a screen with two columns of colors, one for
32266 the foreground color and one for the background color.
32267 The foreground color is just the color you want the actual characters
32268 to be and the background color is the color of the rest of the rectangle
32269 behind the characters.
32270 Select the foreground and background colors desired by using the Next and
32271 Prev keys to highlight the color, and the * command to select it.
32272 <P>
32273 To set a color to its default value, set the X in the Default line at
32274 the bottom of the list of colors.
32275 <P>
32277 The HEADER COLORS section is a little bit different from the others.
32278 Besides coloring the specific fields that Alpine knows about, you may also
32279 color specific header fields when viewing a message in the MESSAGE TEXT
32280 screen.
32281 For example, you may color the Subject header a particular color.
32282 There are a few commands for use with headers.
32283 The "AddHeader" command adds a section to the color
32284 configuration screen that allows you to set the color for that header.
32285 You'll be asked for the name of the header field you want to color.
32286 If you wanted to color the Subject, you would answer
32287 with the word "subject".
32288 Once you've added a header field, the color setting works just like the
32289 other color fields, except that there is an additional line on the
32290 configuration screen labeled "Pattern to match".
32291 If you leave that blank, then the whole field for that header will always
32292 be colored.
32293 However, if you give a pattern to match, the coloring will only take place
32294 if there is a match for that pattern in the value of the field.
32295 For example, if you are working on a color for the Subject header and
32296 you fill in a pattern of "important", then only Subjects that
32297 contain the word "important" will be colored.
32298 <P>
32299 The "DeleteHdr" command removes a header section from the
32300 configuration altogether.
32301 The "Shuffle" command changes the order of header sections.
32302 This is only necessary if you use header sections with pattern fields.
32303 For example, if you have two Subject sections, one with one pattern and
32304 another with another pattern, and the subject for a particular message
32305 happens to match both, then the color from the first match is used.
32306 <P>
32308 The command "RestoreDefs" will restore all of the default colors.
32309 Each section will change to the default value used for that section when
32310 color is first enabled.
32311 When you restore all default colors the color settings for the Header Colors
32312 will be unset (since that's the default), but the header fields you've
32313 added will remain so that you may easily reset them.
32314 In order to get rid of them completely you'd have to use
32315 the "DeleteHdr" command.
32317 <P>
32318 Remember that <A HREF="h_rules_incols">Index Line Colors</A>
32319 may be set with matching rules and that is configured separately from
32320 the rest of the color settings described here.
32321 It is configured in the Setup/Rules/Indexcolors section of the configuration screen
32322 instead of in the Setup/Kolor section.
32324 <P><UL>
32325 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32326 </UL><P>
32327 <End of help on this topic>
32328 </BODY>
32329 </HTML>
32330 ====== h_config_news_uses_recent ======
32331 <HTML>
32332 <HEAD>
32333 <TITLE>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></TITLE>
32334 </HEAD>
32335 <BODY>
32336 <H1>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></H1>
32338 This feature causes certain messages to be marked as "New" in the
32339 MESSAGE INDEX of newsgroups.
32340 This feature is set by default.
32342 <P>
32344 When opening a newsgroup, Alpine will consult your "newsrc" file and
32345 determine the last message you have previously disposed of via the "D"
32346 key. If this feature is set, any subsequent messages will be shown in the
32347 Index with an "N", and the first of these messages will be highlighted.
32348 Although this is only an approximation of true "New" or "Unseen"
32349 status, it provides a useful cue to distinguish more-or-less recent
32350 messages from those you have seen previously, but are not yet ready to
32351 mark deleted.
32353 <P>
32355 Background: your "newsrc" file (used to store message status information
32356 for newsgroups) is only capable of storing a single flag, and Alpine uses
32357 this to record whether or not you are "done with" a message, as
32358 indicated by marking the message as "Deleted". Unfortunately, this
32359 means that Alpine has no way to record exactly which messages you have
32360 previously seen, so it normally does not show the "N" status flag for
32361 any messages in a newsgroup. This feature enables a starting
32362 *approximation* of seen/unseen status that may be useful.
32363 <P>
32364 <End of help on this topic>
32365 </BODY>
32366 </HTML>
32367 ====== h_config_expose_hidden_config =====
32368 <HTML>
32369 <HEAD>
32370 <TITLE>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></TITLE>
32371 </HEAD>
32372 <BODY>
32373 <H1>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></H1>
32375 If set, this causes configuration options and features that are normally
32376 hidden from view to be editable in the Setup/Config screen.
32378 <P>
32379 The purpose of this feature is to allow you to change configuration
32380 features and variables that are normally hidden.
32381 This is particularly useful if you are using a remote configuration,
32382 where it is difficult to edit the contents manually, but it may also be used
32383 on a local pinerc configuration file.
32384 <P>
32385 If set, several configuration variables and features that are normally
32386 hidden from view will show up in the Setup/Configuration screen.
32387 They will be at the bottom of the configuration screen.
32388 You can find them by searching for the words "hidden configuration".
32389 <P>
32391 Note that this is an advanced feature that should be used with care.
32392 The reason that this part of the configuration is normally hidden is because
32393 there is a significant potential for causing problems if you change these
32394 variables.
32395 If something breaks after a change try changing it back to see if that is
32396 what is causing the problem.
32397 There are also some variables that are normally hidden because they are
32398 manipulated through Alpine in other ways.
32399 For example, colors are normally set using the Setup/Kolors screen and
32400 the "<!--#echo var="VAR_address-book"-->" variable is normally set using
32401 the Setup/AddressBooks screen, so there is little reason to edit these directly.
32402 The "<!--#echo var="VAR_incoming-folders"-->" variable is normally changed by using
32403 the Add, Delete, and Rename commands in the FOLDER LIST screen,
32404 and the "<!--#echo var="VAR_last-time-prune-questioned"-->" variable is normally used
32405 internally by Alpine and not set directly by the user.
32406 <P>
32407 <UL>
32408 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32409 </UL><P>
32410 <End of help on this topic>
32411 </BODY>
32412 </HTML>
32413 ====== h_config_disable_signature_edit =====
32414 <HTML>
32415 <HEAD>
32416 <TITLE>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></TITLE>
32417 </HEAD>
32418 <BODY>
32419 <H1>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></H1>
32421 If set, this disables the editing of signature files from within
32422 the Setup/Config screen.
32423 <P>
32424 <UL>
32425 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32426 </UL><P>
32427 <End of help on this topic>
32428 </BODY>
32429 </HTML>
32430 ====== h_config_disable_roles_templateedit =====
32431 <HTML>
32432 <HEAD>
32433 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></TITLE>
32434 </HEAD>
32435 <BODY>
32436 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></H1>
32438 If set, this disables the editing of template files within the
32439 Role setup screen.
32440 <P>
32441 <UL>
32442 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32443 </UL><P>
32444 <End of help on this topic>
32445 </BODY>
32446 </HTML>
32447 ====== h_config_disable_roles_sigedit =====
32448 <HTML>
32449 <HEAD>
32450 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></TITLE>
32451 </HEAD>
32452 <BODY>
32453 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></H1>
32455 If set, this disables the editing of signature files within the
32456 Role setup screen.
32457 <P>
32458 <UL>
32459 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32460 </UL><P>
32461 <End of help on this topic>
32462 </BODY>
32463 </HTML>
32464 ====== h_config_disable_roles_setup =====
32465 <HTML>
32466 <HEAD>
32467 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></TITLE>
32468 </HEAD>
32469 <BODY>
32470 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></H1>
32472 If set, this disables the Setup/Rules/Roles command.
32473 <P>
32474 <UL>
32475 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32476 </UL><P>
32477 <End of help on this topic>
32478 </BODY>
32479 </HTML>
32480 ====== h_config_disable_pipes_in_templates =====
32481 <HTML>
32482 <HEAD>
32483 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></TITLE>
32484 </HEAD>
32485 <BODY>
32486 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></H1>
32488 By default, if a template file name is followed by a vertical bar (|) then
32489 that causes the file to be executed to produce the text for the template.
32490 If this feature is set, then this is not allowed.
32491 <P>
32492 <UL>
32493 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32494 </UL><P>
32495 <End of help on this topic>
32496 </BODY>
32497 </HTML>
32498 ====== h_config_disable_pipes_in_sigs =====
32499 <HTML>
32500 <HEAD>
32501 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></TITLE>
32502 </HEAD>
32503 <BODY>
32504 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></H1>
32506 By default, if a signature file name is followed by a vertical bar (|) then
32507 that causes the file to be executed to produce the text for the signature.
32508 If this feature is set, then this is not allowed.
32509 <P>
32510 <UL>
32511 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32512 </UL><P>
32513 <End of help on this topic>
32514 </BODY>
32515 </HTML>
32516 ====== h_config_disable_password_cmd =====
32517 <HTML>
32518 <HEAD>
32519 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></TITLE>
32520 </HEAD>
32521 <BODY>
32522 <H1>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></H1>
32524 If set, then the Setup/Newpassword command is disabled.
32525 <P>
32526 <UL>
32527 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32528 </UL><P>
32529 <End of help on this topic>
32530 </BODY>
32531 </HTML>
32532 ====== h_config_disable_password_caching =====
32533 <HTML>
32534 <HEAD>
32535 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></TITLE>
32536 </HEAD>
32537 <BODY>
32538 <H1>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></H1>
32540 Normally, loginname/password combinations are cached in Alpine so that
32541 you do not have to enter the same password more than once in a session.
32542 A disadvantage to this approach is that the password must be stored in
32543 the memory image of the running Alpine in order that it can be re-used.
32544 In the event that Alpine crashes and produces a core dump, and that core
32545 dump is readable by others, the loginname and password could be read
32546 from the core dump.
32547 <P>
32548 If this feature is set, then the passwords will not be cached and you
32549 will have to retype the password whenever Alpine needs it.
32550 Even with this feature set there is still some chance that the core
32551 file will contain a password, so care should be taken to make the
32552 core files unreadable.
32553 <P>
32554 NOTE: If PASSFILE caching is enabled, this does not disable it.
32555 That is a separate and independent feature.
32556 <UL>
32557 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32558 </UL><P>
32559 <End of help on this topic>
32560 </BODY>
32561 </HTML>
32562 ====== h_config_disable_kb_lock =====
32563 <HTML>
32564 <HEAD>
32565 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></TITLE>
32566 </HEAD>
32567 <BODY>
32568 <H1>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></H1>
32570 If set, then the Keyboard Lock command is removed from the MAIN MENU.
32571 <P>
32572 <UL>
32573 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32574 </UL><P>
32575 <End of help on this topic>
32576 </BODY>
32577 </HTML>
32578 ====== h_config_disable_config_cmd =====
32579 <HTML>
32580 <HEAD>
32581 <TITLE>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></TITLE>
32582 </HEAD>
32583 <BODY>
32584 <H1>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></H1>
32586 If set, then the Setup/Config screen is disabled.
32587 <P>
32588 <UL>
32589 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32590 </UL><P>
32591 <End of help on this topic>
32592 </BODY>
32593 </HTML>
32594 ====== h_config_allow_chg_from =====
32595 <HTML>
32596 <HEAD>
32597 <TITLE>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></TITLE>
32598 </HEAD>
32599 <BODY>
32600 <H1>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></H1>
32602 This feature affects Alpine's handling of the "From:" header field
32603 in the "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" configuration
32604 option.
32605 <P>
32606 If this feature is set then the From line can be changed just like
32607 all the other header fields that can be changed.
32608 This feature defaults to <EM>ON</EM>.
32609 <P>
32610 Even with this feature turned ON (the default) you will not be able
32611 to change the From header unless you add it to your list of
32612 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>.
32613 You may also want to change the
32614 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
32615 if you want the From header to always show up in the composer without
32616 having to type the Rich Headers command first.
32617 <P>
32618 Note that many sites restrict the use of this feature in order to
32619 reduce the chance of falsified addresses and misdirected mail.
32620 If you want to change the value of what gets included in the From header
32621 in messages you send
32622 look <A HREF="h_config_change_your_from">here</A> for a description.
32623 <P>
32624 <UL>
32625 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32626 </UL><P>
32627 <End of help on this topic>
32628 </BODY>
32629 </HTML>
32630 ====== h_config_disable_collate =====
32631 <HTML>
32632 <HEAD>
32633 <TITLE>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></TITLE>
32634 </HEAD>
32635 <BODY>
32636 <H1>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></H1>
32638 This is a hard to understand feature that should only be used in rare cases.
32639 Normally, the C function call
32640 <P>
32641 <CENTER><SAMP>setlocale(LC_COLLATE, "")</SAMP></CENTER>
32642 <P>
32643 is used by Alpine.
32644 If you want to try turning it off,
32645 setting this feature will turn it off.
32646 This part of the locale has to do with the sort order
32647 of characters in your locale.
32648 <P>
32649 <UL>
32650 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32651 </UL><P>
32652 <End of help on this topic>
32653 </BODY>
32654 </HTML>
32655 ====== h_config_quell_attach_extra_prompt =====
32656 <HTML>
32657 <HEAD>
32658 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></TITLE>
32659 </HEAD>
32660 <BODY>
32661 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></H1>
32663 By default, when you attempt to view an attachment externally
32664 from the "Attachment View" screen, you are asked if you
32665 really want to view the selected attachment.
32667 <P>
32668 If this feature is set, you will <B>not</B> be prompted to confirm
32669 your selection. Prior to Alpine and to Pine 4.50, the default behavior was to not
32670 prompt. This feature was added for those wanting to preserve that
32671 behavior (along with
32672 <A HREF="h_config_quell_attach_ext_warn"><!--#echo var="FEAT_quell-attachment-extension-warn"--></A>).
32674 <P>
32675 <UL>
32676 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32677 </UL><P>
32678 <End of help on this topic>
32679 </BODY>
32680 </HTML>
32681 ====== h_config_quell_attach_ext_warn =====
32682 <HTML>
32683 <HEAD>
32684 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></TITLE>
32685 </HEAD>
32686 <BODY>
32687 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></H1>
32689 <P>
32690 This feature suppresses the extra warning you can get when trying
32691 to view an attachment for which there is no mime-type match. Turning
32692 on this feature will just run the program according to extension
32693 instead of first warning the user that it will run according to the
32694 file's extension.
32695 <P>
32696 This feature can be used along side
32697 <A HREF="h_config_quell_attach_extra_prompt"><!--#echo var="FEAT_quell-attachment-extra-prompt"--></A>
32698 to preserve the behavior exhibited in Pine versions prior to Pine 4.50.
32699 <P>
32700 <UL>
32701 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32702 </UL><P>
32703 <End of help on this topic>
32704 </BODY>
32705 </HTML>
32706 ====== h_config_mailcap_params =====
32707 <HTML>
32708 <HEAD>
32709 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></TITLE>
32710 </HEAD>
32711 <BODY>
32712 <H1>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></H1>
32714 If set, this will allow mailcap named parameter substitution to occur
32715 in mailcap entries.
32716 By default, this is turned off to prevent security problems that may occur
32717 with some incorrect mailcap configurations.
32718 For more information, see RFC1524 and look for "named parameters" in the
32719 text of the RFC.
32720 <P>
32721 <UL>
32722 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32723 </UL><P>
32724 <End of help on this topic>
32725 </BODY>
32726 </HTML>
32727 ====== h_config_disable_shared =====
32728 <HTML>
32729 <HEAD>
32730 <TITLE>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></TITLE>
32731 </HEAD>
32732 <BODY>
32733 <H1>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></H1>
32735 If this feature is set, the automatic search for namespaces "ftp",
32736 "imapshared", and "imappublic" by the underlying library
32737 will be disabled.
32738 The reason this feature exists is because there are some implementations
32739 of system password lookup routines that are very slow when presented with
32740 a long loginname that does not exist.
32741 This feature could be set to prevent the delay at startup time when the
32742 names above are searched for in the password file.
32743 <P>
32744 <UL>
32745 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32746 </UL><P>
32747 <End of help on this topic>
32748 </BODY>
32749 </HTML>
32750 ====== h_config_hide_nntp_path =====
32751 <HTML>
32752 <HEAD>
32753 <TITLE>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></TITLE>
32754 </HEAD>
32755 <BODY>
32756 <H1>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></H1>
32758 Normally the Path header that Alpine generates when posting to a newsgroup
32759 contains the name of the computer from which the message is being sent and
32760 the user name.
32761 Some believe that this information is used by spammers.
32762 If this feature is set, that information will be replaced with the text
32763 <P>
32764 <CENTER><SAMP>not-for-mail</SAMP></CENTER>
32765 <P>
32766 instead.
32767 <P>
32768 It should be noted that many servers being connected to will still reveal
32769 the information that this feature attempts to protect.
32770 <P>
32771 <UL>
32772 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32773 </UL><P>
32774 <End of help on this topic>
32775 </BODY>
32776 </HTML>
32777 ====== h_config_no_bezerk_zone =====
32778 <HTML>
32779 <HEAD>
32780 <TITLE>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></TITLE>
32781 </HEAD>
32782 <BODY>
32783 <H1>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></H1>
32785 POSIX mandates a timezone in UNIX mailbox format folder delimiters
32786 (the line that begins with From <SPACE>).
32787 Some versions of Berkeley mail have trouble with this, and don't recognize
32788 the line as a message delimiter.
32789 If this feature is set, the timezone will be left off the delimiter line.
32790 <P>
32791 <UL>
32792 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32793 </UL><P>
32794 <End of help on this topic>
32795 </BODY>
32796 </HTML>
32797 ====== h_config_quell_domain_warn =====
32798 <HTML>
32799 <HEAD>
32800 <TITLE>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></TITLE>
32801 </HEAD>
32802 <BODY>
32803 <H1>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></H1>
32805 When your configuration is set up so that your domain name contains no dots,
32806 it is usually a configuration error.
32807 By default, Alpine will warn you about this when you start it up.
32808 You will see a warning message that looks like
32810 <P>
32811 <CENTER><SAMP>Incomplete maildomain "<domain>".</SAMP></CENTER>
32813 <P>
32814 If this feature is set, the warning is turned off.
32815 <P>
32816 <UL>
32817 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32818 </UL><P>
32819 <End of help on this topic>
32820 </BODY>
32821 </HTML>
32822 ====== h_config_quell_imap_env =====
32823 <HTML>
32824 <HEAD>
32825 <TITLE>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></TITLE>
32826 </HEAD>
32827 <BODY>
32828 <H1>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></H1>
32830 In the MESSAGE INDEX screen, if the open folder is being accessed
32831 using IMAP, Alpine normally tries to paint the index lines on the screen
32832 as soon as the information arrives from the IMAP server.
32833 This means that the index information makes it onto the screen more quickly
32834 than it otherwise would.
32835 This sometimes results in behavior that bothers some users.
32836 For example, when paging to a new page of the index, it may be possible for
32837 the lines to be painted on the screen in a random order, rather than from
32838 top to bottom.
32839 <P>
32841 Setting this feature causes Alpine to wait for all of the information
32842 to be gathered before it paints the index screen.
32843 Once it collects all of the information, the screen will be painted quickly
32844 from top to bottom.
32845 <P>
32846 <UL>
32847 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32848 </UL><P>
32849 <End of help on this topic>
32850 </BODY>
32851 </HTML>
32852 ====== h_config_quell_news_env =====
32853 <HTML>
32854 <HEAD>
32855 <TITLE>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></TITLE>
32856 </HEAD>
32857 <BODY>
32858 <H1>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></H1>
32860 In the MESSAGE INDEX screen, if the open folder is being accessed
32861 using NNTP (News), Alpine normally tries to paint the index lines on the screen
32862 as soon as the information arrives from the NNTP server.
32863 This means that the index information makes it onto the screen more quickly
32864 than it otherwise would.
32865 This sometimes results in behavior that bothers some users.
32866 For example, when paging to a new page of the index, it may be possible for
32867 the lines to be painted on the screen in a random order, rather than from
32868 top to bottom.
32869 <P>
32871 Setting this feature causes Alpine to wait for all of the information
32872 to be gathered before it paints the index screen.
32873 Once it collects all of the information, the screen will be painted quickly
32874 from top to bottom.
32875 <P>
32876 <UL>
32877 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32878 </UL><P>
32879 <End of help on this topic>
32880 </BODY>
32881 </HTML>
32882 ====== h_config_quell_content_id =====
32883 <HTML>
32884 <HEAD>
32885 <TITLE>FEATURE: <!--#echo var="FEAT_quell-content-id"--></TITLE>
32886 </HEAD>
32887 <BODY>
32888 <H1>FEATURE: <!--#echo var="FEAT_quell-content-id"--></H1>
32890 This feature changes the behavior of Alpine when sending messages.
32891 It is intended to work around a bug in Microsoft's Outlook XP mail user
32892 agent.
32893 As of this writing, Microsoft has acknowledged the bug but
32894 has not added it to the Knowledge Base.
32895 We have been told that there will be a post-SP1 hotfix for Outlook XP.
32896 This particular bug has bug fix number OfficeQFE:4781.
32897 The nature of the bug is that messages with attachments that
32898 contain a Content-ID header (which standard Alpine attachments do)
32899 do not show the attachment indicator (a paperclip) when viewed with
32900 Outlook XP.
32901 So the user has no indication that the message contains an attachment.
32903 <P>
32904 If this feature is set then Alpine will remove most Content-ID headers
32905 before sending a message.
32906 If an attachment is of type MESSAGE, then the existing Content-ID headers
32907 inside the message will be left intact.
32908 This would only happen with Alpine if a message was forwarded as an attachment
32909 or if a message with a message attached was forwarded.
32910 Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded,
32911 the Content-ID headers of the alternative parts will not be removed.
32913 <P>
32914 Because the Content-ID header is a standard part of MIME it is possible
32915 that setting this feature will break something.
32916 For example, if an attachment has a Content-ID header that is necessary
32917 for the correct functioning of that attachment, it is possible that Alpine
32918 may remove that header when the attachment is forwarded.
32919 However, it seems fairly safe at this time.
32921 <P>
32922 <UL>
32923 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32924 </UL><P>
32925 <End of help on this topic>
32926 </BODY>
32927 </HTML>
32928 ====== h_config_winpos_in_config =====
32929 <HTML>
32930 <HEAD>
32931 <TITLE>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></TITLE>
32932 </HEAD>
32933 <BODY>
32934 <H1>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></H1>
32936 PC-Alpine only.
32937 <P>
32939 Normally, PC-Alpine will store its window size and position in the
32940 Windows Registry.
32941 This is convenient if you want to use the same remote
32942 configuration from more than one PC.
32943 If you use multiple configuration files to start PC-Alpine, you may want
32944 to store the window size and position in the configuration file instead
32945 of in the Registry.
32946 Setting this feature causes the value to be stored in
32947 <A HREF="h_config_window_position">Window-Position</A>.
32949 <P>
32950 <UL>
32951 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32952 </UL><P>
32953 <End of help on this topic>
32954 </BODY>
32955 </HTML>
32956 ====== h_config_quell_ssl_largeblocks =====
32957 <HTML>
32958 <HEAD>
32959 <TITLE>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></TITLE>
32960 </HEAD>
32961 <BODY>
32962 <H1>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></H1>
32964 PC-Alpine only.
32965 <P>
32966 This feature changes the behavior of fetching messages
32967 and attachments so that the message data is fetched in chunks no larger
32968 than 12K bytes.
32969 This works around a bug in Microsoft's SSL/TLS support.
32970 Some versions of Microsoft SSL are not able to read full-sized (16K)
32971 SSL/TLS packets.
32972 Some servers will send such packets and this will
32973 cause PC-Alpine to crash with the error
32975 <P>
32976 <CENTER><SAMP>incomplete SecBuffer exceeds maximum buffer size</SAMP></CENTER>
32978 <P>
32979 Microsoft is aware of the problem and has developed a hotfix for it, it is
32980 discussed in article 300562 in the Microsoft Knowledge Base.
32981 <P>
32982 <UL>
32983 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32984 </UL><P>
32985 <End of help on this topic>
32986 </BODY>
32987 </HTML>
32988 ====== h_config_quell_partial =====
32989 <HTML>
32990 <HEAD>
32991 <TITLE>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></TITLE>
32992 </HEAD>
32993 <BODY>
32994 <H1>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></H1>
32996 Partial fetching is a feature of the IMAP protocol.
32997 By default, Alpine
32998 will use partial fetching when copying the contents of a message or attachment
32999 from the IMAP server to Alpine.
33000 This means that the fetch will be done in many
33001 small chunks instead of one big chunk. The main benefit of this approach is
33002 that the fetch becomes interruptible. That is, the user can type <EM>^C</EM>
33003 to stop the fetch early. In some cases partial fetching may cause a performance
33004 problem so that the fetching of data takes significantly longer when partial
33005 fetching is used. Turning on this feature will turn off partial fetching.
33006 <P>
33007 <UL>
33008 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33009 </UL><P>
33010 <End of help on this topic>
33011 </BODY>
33012 </HTML>
33013 ====== h_config_quell_personal_name_prompt =====
33014 <HTML>
33015 <HEAD>
33016 <TITLE>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></TITLE>
33017 </HEAD>
33018 <BODY>
33019 <H1>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></H1>
33021 PC-Alpine only. This feature quells the prompting for a
33022 <A HREF="h_config_pers_name">personal name</A>. This
33023 prompt normally happens before composing a message, and only happens when
33024 there is no personal name already set.
33025 <P>
33026 <UL>
33027 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33028 </UL><P>
33029 <End of help on this topic>
33030 </BODY>
33031 </HTML>
33032 ====== h_config_quell_user_id_prompt =====
33033 <HTML>
33034 <HEAD>
33035 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></TITLE>
33036 </HEAD>
33037 <BODY>
33038 <H1>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></H1>
33040 PC-Alpine only. This feature quells the prompting for a
33041 <A HREF="h_config_user_id"><!--#echo var="VAR_user-id"--></A>
33042 if the information can be obtained from the login name used
33043 to open the INBOX. Normally, this prompt happens before composing
33044 a message, and only happens when there is no user-id already set
33045 in the configuration.
33046 <P>
33047 With this feature set, composing a message is only possible after
33048 establishing a connection to the INBOX.
33049 <P>
33050 <UL>
33051 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33052 </UL><P>
33053 <End of help on this topic>
33054 </BODY>
33055 </HTML>
33056 ====== h_config_save_aggregates =====
33057 <HTML>
33058 <HEAD>
33059 <TITLE>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></TITLE>
33060 </HEAD>
33061 <BODY>
33062 <H1>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></H1>
33064 This feature will optimize an aggregate copy operation, if
33065 possible, by issuing a single IMAP <EM>COPY</EM> command with a
33066 list of the messages to be copied.
33067 This feature is set by default.
33068 This may reduce network traffic and elapsed time for the Save.
33069 <EM>However, many IMAP servers (including the UW IMAP server) do
33070 not preserve the order of messages when this optimization is applied.</EM>
33071 If this feature is not set,
33072 Alpine will copy each message individually and the order of the messages
33073 will be preserved.
33074 <P>
33075 <UL>
33076 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33077 </UL><P>
33078 <End of help on this topic>
33079 </BODY>
33080 </HTML>
33081 ====== h_config_use_system_translation =====
33082 <HTML>
33083 <HEAD>
33084 <TITLE>FEATURE: Use System Translation</TITLE>
33085 </HEAD>
33086 <BODY>
33087 <H1>FEATURE: Use System Translation</H1>
33089 UNIX Alpine only.
33090 <P>
33091 Alpine normally uses its own internal software to convert between the multi-byte
33092 representation of characters and the Unicode representation of those
33093 same characters.
33094 It converts from the multi-byte characters your keyboard produces to Unicode,
33095 and from Unicode to the multi-byte characters your display expects.
33096 Alpine also uses its own internal software to decide how much space on
33097 the screen a particular Unicode character will occupy.
33099 <P>
33100 Setting this feature tells Alpine to use the system-supplied routines to
33101 perform these tasks instead.
33102 In particular there are three tasks and three system routines that will
33103 be used for these tasks.
33105 <P>
33106 To convert from multi-byte to Unicode the routine
33108 <P>
33109 <CENTER><SAMP>mbstowcs</SAMP></CENTER>
33110 <P>
33112 is used.
33113 To convert from Unicode to multi-byte the routine
33115 <P>
33116 <CENTER><SAMP>wcrtomb</SAMP></CENTER>
33117 <P>
33119 is used.
33120 And to find the screen width a particular Unicode character will
33121 occupy the routine used is
33123 <P>
33124 <CENTER><SAMP>wcwidth</SAMP></CENTER>
33125 <P>
33127 This feature has been only lightly tested.
33128 The internal routines should normally be used unless you run into
33129 a problem that you think may be solved by using the system routines.
33130 Note that your environment needs to be set up for these
33131 routines to work correctly.
33132 In particular, the LANG or LC_CTYPE variable in your environment will
33133 need to be set.
33135 <P>
33136 <UL>
33137 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33138 </UL><P>
33139 <End of help on this topic>
33140 </BODY>
33141 </HTML>
33142 ====== h_config_suspend_spawns =====
33143 <HTML>
33144 <HEAD>
33145 <TITLE>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></TITLE>
33146 </HEAD>
33147 <BODY>
33148 <H1>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></H1>
33150 This feature affects Alpine's behavior when process suspension is enabled
33151 and then activated via the Ctrl-Z key. Alpine suspension allows one to
33152 temporarily interact with the operating system command "shell"
33153 without
33154 quitting Alpine, and then subsequently resume the still-active Alpine session.
33155 <P>
33157 When the <A HREF="h_config_can_suspend">"<!--#echo var="FEAT_enable-suspend"-->"</A> feature
33158 is set and subsequently the Ctrl-Z key
33159 is pressed, Alpine will normally suspend itself and return temporary control
33160 to Alpine's parent shell process. However, if this feature is set, Alpine
33161 will instead create an inferior subshell process. This is useful when the
33162 parent process is not intended to be used interactively. Examples include
33163 invoking Alpine via the -e argument of the Unix "xterm" program,
33164 or via a menu system.<P>
33166 Note that one typically resumes a suspended Alpine by entering the Unix
33167 "fg" command, but if this feature is set, it will be necessary to
33168 enter the "exit" command instead.
33169 <P>
33170 <UL>
33171 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33172 </UL><P>
33173 <End of help on this topic>
33174 </BODY>
33175 </HTML>
33176 ====== h_config_8bit_smtp =====
33177 <HTML>
33178 <HEAD>
33179 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></TITLE>
33180 </HEAD>
33181 <BODY>
33182 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></H1>
33184 This feature affects Alpine's behavior when sending mail.
33185 By default, this feature is set.
33186 Internet standards
33187 require that all electronic mail messages traversing the global Internet
33188 consist of 7bit ASCII characters unless a pair of cooperating mail
33189 transfer agents explicitly agree to allow 8bit messages. In general,
33190 then, exchanging messages in non-ASCII characters requires MIME encoding.
33191 <P>
33192 However, there are now Internet standards that allow for unencoded 8bit
33193 exchange of messages between cooperating systems. When this feature is set
33194 Alpine will try to negotiate unencoded 8bit transmission during the
33195 sending process. Should the negotiation fail, Alpine will fall back to its
33196 ordinary encoding rules.
33197 <P>
33198 Note, this feature relies on your system's mail transport agent or
33199 configured <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
33200 having the negotiation mechanism introduced in
33201 "Extended SMTP" (ESMTP) and the specific extension called
33202 "8BITMIME".
33203 <P>
33204 ESMTP allows for graceful migration to upgraded mail transfer agents, but
33205 it is possible that this feature might cause problems for some servers.
33206 <P><UL>
33207 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33208 </UL>
33209 <P><End of help on this topic>
33210 </BODY>
33211 </HTML>
33212 ====== h_config_8bit_nntp =====
33213 <HTML>
33214 <HEAD>
33215 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></TITLE>
33216 </HEAD>
33217 <BODY>
33218 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></H1>
33220 This feature affects Alpine's behavior when posting news.
33222 <P>
33224 The Internet standard for exchanging USENET news messages (RFC-1036)
33225 specifies that USENET messages should conform to Internet mail standards
33226 and contain only 7bit characters, but much of the news transport software
33227 in use today is capable of successfully sending messages containing 8bit
33228 characters. Hence, many people believe that it is appropriate to send 8bit
33229 news messages without any MIME encoding.
33231 <P>
33233 Moreover, there is no Internet standard for explicitly negotiating 8bit
33234 transfer, as there is for Internet email. Therefore, Alpine provides the
33235 option of posting unencoded 8bit news messages, though not as the default.
33236 Setting this feature will turn OFF Alpine's MIME encoding of newsgroup
33237 postings that contain 8bit characters.
33239 <P>
33241 Note, articles may cross a path or pass through news transport software
33242 that is unsafe or even hostile to 8bit characters. At best this will only
33243 cause the posting to become garbled. The safest way to transmit 8bit
33244 characters is to leave Alpine's MIME encoding turned on, but recipients
33245 who lack MIME-aware tools are often annoyed when they receive MIME-encoded
33246 messages.
33247 <P>
33248 <End of help on this topic>
33249 </BODY>
33250 </HTML>
33251 ====== h_config_mark_for_cc =====
33252 <HTML>
33253 <HEAD>
33254 <TITLE>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></TITLE>
33255 </HEAD>
33256 <BODY>
33257 <H1>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></H1>
33259 This feature affects Alpine's MESSAGE INDEX display.
33260 By default, a '+' is displayed in the first column if the
33261 message is addressed directly to you.
33262 When this feature is set and the message is not addressed to you, then a
33263 '-' character is displayed if the message is instead Cc'd directly
33264 to you.
33266 <P>
33267 <UL>
33268 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33269 </UL><P>
33270 <End of help on this topic>
33271 </BODY>
33272 </HTML>
33273 ====== h_config_tab_uses_unseen =====
33274 <HTML>
33275 <HEAD>
33276 <TITLE>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></TITLE>
33277 </HEAD>
33278 <BODY>
33279 <H1>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></H1>
33281 This feature affects Alpine's behavior when using the TAB
33282 <A HREF="h_common_nextnew">NextNew Command</A>
33283 to move from one folder to the next.
33284 Alpine's usual behavior is to search for folders
33285 with <EM>Recent</EM> messages in them.
33286 Recent messages are messages that have arrived since the last time the
33287 folder was opened.
33289 <P>
33290 Setting this feature causes Alpine to search for <EM>Unseen</EM>
33291 messages instead of Recent messages.
33292 Unseen messages remain Unseen until you view them (or flag then as Seen with
33293 the <A HREF="h_common_flag">Flag Command</A>).
33294 Setting this feature allows you to locate messages you have not read
33295 instead of only recently received messages.
33296 When this feature is set, the feature
33297 <A HREF="h_config_fast_recent">"<!--#echo var="FEAT_enable-fast-recent-test"-->"</A>
33298 will have no effect, so the checking may be slower.
33300 <P>
33301 Another reason why you might want to use this feature is that Alpine sometimes
33302 opens folders implicitly behind the scenes, and this clears the
33303 Recent status of all messages in the folder.
33304 One example where this happens is when Saving or filtering a
33305 message to another folder.
33306 If that message has some <A HREF="h_config_keywords">keywords</A>
33307 set, then because of some shortcomings
33308 in the IMAP specification, the best way to ensure that those keywords are
33309 still set in the saved copy of the message is to open the folder and
33310 set the keywords explicitly.
33311 Because this clears the Recent status of all messages in that folder the
33312 folder will not be found by the NextNew command unless this feature is set.
33314 <P>
33315 <End of help on this topic>
33316 </BODY>
33317 </HTML>
33318 ====== h_config_tab_new_only =====
33319 <HTML>
33320 <HEAD>
33321 <TITLE>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></TITLE>
33322 </HEAD>
33323 <BODY>
33324 <H1>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></H1>
33326 This feature affects Alpine's behavior when using the TAB key to move from
33327 one message to the next. Alpine's usual behavior is to select the next
33328 unread message or message flagged as "Important".
33330 <P>
33332 Setting this feature causes Alpine to skip the messages flagged as important,
33333 and select unread messages exclusively. Tab behavior when there are no
33334 new messages left to select remains unchanged.
33335 <P>
33336 <End of help on this topic>
33337 </BODY>
33338 </HTML>
33339 ====== h_config_warn_if_subj_blank =====
33340 <HTML>
33341 <HEAD>
33342 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></TITLE>
33343 </HEAD>
33344 <BODY>
33345 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></H1>
33347 This feature affects Alpine's behavior when you send a message being
33348 composed.
33349 If this option is set, Alpine will check to see if the message about to be sent
33350 has a subject or not.
33351 If not, you will be asked if you want to send the message anyway.
33352 <P>
33354 <UL>
33355 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33356 </UL><P>
33357 <End of help on this topic>
33358 </BODY>
33359 </HTML>
33360 ====== h_config_warn_if_fcc_blank =====
33361 <HTML>
33362 <HEAD>
33363 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></TITLE>
33364 </HEAD>
33365 <BODY>
33366 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></H1>
33368 This feature affects Alpine's behavior when you send a message being
33369 composed.
33370 If this option is set, Alpine will check to see if the message about to be sent
33371 has an Fcc or not.
33372 If not, you will be asked if you want to send the message anyway.
33373 <P>
33375 <UL>
33376 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33377 </UL><P>
33378 <End of help on this topic>
33379 </BODY>
33380 </HTML>
33381 ====== h_config_warn_if_no_to_or_cc =====
33382 <HTML>
33383 <HEAD>
33384 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></TITLE>
33385 </HEAD>
33386 <BODY>
33387 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></H1>
33389 This feature affects Alpine's behavior when you send a message being
33390 composed.
33391 If this option is set, Alpine will check to see if the message about to be sent
33392 has either a To address, a Cc address, or a Newsgroup.
33393 If none of these is set,
33394 you will be asked if you want to send the message anyway.
33395 <P>
33397 This feature is closely related to
33398 <A HREF="h_config_auto_fcc_only"><!--#echo var="FEAT_fcc-only-without-confirm"--></A>.
33399 Alpine will normally ask if you want to copy a message only to the Fcc.
33400 This feature also applies to cases where there is a Bcc but still no To, Cc,
33401 or Newsgroup.
33402 If the <!--#echo var="FEAT_fcc-only-without-confirm"--> feature is set and you are sending a
33403 message with only an Fcc, then you won't be asked about sending with
33404 a blank To and Cc and Newsgroups header even if this feature is set.
33405 Similarly, if you have already been asked if you want to send to the Fcc
33406 only and you have answered Yes, then you won't be asked again about sending with
33407 blank To, Cc, and Newsgroups headers even if this feature is set.
33408 <P>
33410 <UL>
33411 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33412 </UL><P>
33413 <End of help on this topic>
33414 </BODY>
33415 </HTML>
33416 ====== h_config_quell_dead_letter =====
33417 <HTML>
33418 <HEAD>
33419 <TITLE>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></TITLE>
33420 </HEAD>
33421 <BODY>
33422 <H1>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></H1>
33424 This feature affects Alpine's behavior when you cancel a message being
33425 composed. Alpine's usual behavior is to write the canceled message to
33426 a file named
33427 <!--chtml if pinemode="os_windows"-->
33428 "DEADLETR",
33429 <!--chtml else-->
33430 "dead.letter" in your home directory,
33431 <!--chtml endif-->
33432 overwriting any previous message. Under
33433 some conditions (some routine), this can introduce a noticeable delay.
33434 Setting this feature will cause Alpine NOT to write canceled compositions
33435 into the file.
33436 <P>
33437 NOTE: Enabling this feature means NO record of canceled messages is
33438 maintained.
33439 <P>
33440 This feature affects the newer option
33441 <A HREF="h_config_deadlets"><!--#echo var="VAR_dead-letter-files"--></A>, which specifies the
33442 number of dead letter files to keep around.
33443 If this feature is set, then the <!--#echo var="VAR_dead-letter-files"--> option has no effect.
33444 <P>
33445 <UL>
33446 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33447 </UL><P>
33448 <End of help on this topic>
33449 </BODY>
33450 </HTML>
33451 ====== h_config_quell_beeps =====
33452 <HTML>
33453 <HEAD>
33454 <TITLE>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></TITLE>
33455 </HEAD>
33456 <BODY>
33457 <H1>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></H1>
33459 This feature affects Alpine's behavior when it displays status message
33460 (e.g., Error complaints, New mail warnings, etc). Setting this feature
33461 will not affect the display of such messages, but will cause those that
33462 emit a beep to become silent.
33464 <P>
33465 <UL>
33466 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33467 </UL><P>
33468 <End of help on this topic>
33469 </BODY>
33470 </HTML>
33471 ====== h_config_suppress_user_agent =====
33472 <HTML>
33473 <HEAD>
33474 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></TITLE>
33475 </HEAD>
33476 <BODY>
33477 <H1>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></H1>
33479 If this feature is set then Alpine will not generate a
33480 <CODE>User-Agent</CODE> header in outgoing messages.
33481 <P>
33482 <UL>
33483 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33484 </UL><P>
33485 <End of help on this topic>
33486 </BODY>
33487 </HTML>
33488 ====== h_config_quell_lock_failure_warnings =====
33489 <HTML>
33490 <HEAD>
33491 <TITLE>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></TITLE>
33492 </HEAD>
33493 <BODY>
33494 <H1>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></H1>
33496 This feature affects Alpine's behavior when it encounters a problem
33497 acquiring a mail folder lock. Typically, a secondary file associated
33498 with the mail folder being opened is created as part of the locking
33499 process. On some systems, such file creation has been administratively
33500 precluded by the system configuration.
33501 <P>
33502 Alpine issues a warning when such failures occur, which can become bothersome
33503 if the system is configured to disallow such actions. Setting this
33504 feature causes Alpine to remain silent when this part of lock creation fails.
33505 <P>
33506 WARNING: systems that have been configured in a way that precludes locking
33507 introduce some risk of mail folder corruption when more than one program
33508 attempts to modify the mail folder. This is most likely to occur to one's
33509 INBOX or other incoming message folder.
33510 <P>
33511 See also <A HREF="h_info_on_locking">"What Systems Managers Need to Know about Alpine File Locking"</A>.
33512 <P>
33513 <UL>
33514 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33515 </UL><P>
33516 <End of help on this topic>
33517 </BODY>
33518 </HTML>
33519 ====== h_config_enable_role_take ======
33520 <HTML>
33521 <HEAD>
33522 <TITLE>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></TITLE>
33523 </HEAD>
33524 <BODY>
33525 <H1>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></H1>
33527 Normally, the Take command takes addresses from a message and helps you
33528 put them into your Address Book.
33529 If you use Rules for Indexcolors, Roles, Filtering, or Scoring;
33530 you may find it useful
33531 to be able to Take information from a message's headers and put it into
33532 a new Rule.
33533 When this feature is set, you will be given an extra prompt that gives
33534 you the choice to Take into the Address Book or Take into a rule.
33535 <P><UL>
33536 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33537 </UL>
33538 <P>
33539 <End of help on this topic>
33540 </BODY>
33541 </HTML>
33542 ====== h_config_enable_take_export ======
33543 <HTML>
33544 <HEAD>
33545 <TITLE>FEATURE: <!--#echo var="FEAT_enable-take-export"--></TITLE>
33546 </HEAD>
33547 <BODY>
33548 <H1>FEATURE: <!--#echo var="FEAT_enable-take-export"--></H1>
33550 Normally, the Take command takes addresses from a message and helps you
33551 put them into your Address Book.
33552 When this feature is set, you will be given an extra prompt that gives you
33553 the choice to Take addresses into a file instead of your Address
33554 Book.
33555 Only the user@domain_name part of the address is put in the file.
33556 <P><UL>
33557 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33558 </UL>
33559 <P>
33560 <End of help on this topic>
33561 </BODY>
33562 </HTML>
33563 ====== h_config_quell_folder_internal_msg ======
33564 <HTML>
33565 <HEAD>
33566 <TITLE>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></TITLE>
33567 </HEAD>
33568 <BODY>
33569 <H1>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></H1>
33571 This feature determines whether or not Alpine will create
33572 "pseudo messages" in folders that are in standard Unix or
33573 MMDF format. <P>
33575 Alpine will normally create these pseudo messages when they are not already
33576 present in a standard Unix or MMDF folder. Their purpose is to record
33577 certain mailbox state data needed for correct IMAP and POP server
33578 operation, and also for Alpine to be able to mark messages as Answered when
33579 the Reply has been postponed.<P>
33581 Sites that do not use IMAP/POP for remote mail access, and that need to
33582 support mail tools that are adversely affected by the presence of the
33583 pseudo-messages (e.g. some mail notification tools) may enable this
33584 feature to tell Alpine not to create them. Note that Alpine's
33585 "Answered" flag
33586 capability will be adversely affected if this is done.<P>
33588 Note too that, even if this feature is enabled, Alpine will not remove
33589 pseudo-messages when it encounters them (e.g. those created by UW's imapd
33590 or ipopd servers.) This feature has no effect on folders that are not in
33591 standard Unix or MMDF format, as pseudo-messages are not needed in the
33592 other formats to record mailbox state information.
33593 <P><UL>
33594 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33595 </UL>
33596 <P>
33597 <End of help on this topic>
33598 </BODY>
33599 </HTML>
33600 ====== h_config_mulnews_as_typed ======
33601 <HTML>
33602 <HEAD>
33603 <TITLE>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></TITLE>
33604 </HEAD>
33605 <BODY>
33606 <H1>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></H1>
33608 This feature will be of little use to most users.
33609 It has no effect unless the feature
33610 <A HREF="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></A>
33611 is set.
33613 When the <!--#echo var="FEAT_enable-multiple-newsrcs"--> feature is set
33614 then the setting of this feature may have an effect on the names of the
33615 newsrc files used.
33616 Normally, the name of the news server will be canonicalized before it is
33617 used in the newsrc file name.
33618 For example, if you type the news server name
33620 <P>
33621 <CENTER><SAMP>servername</SAMP></CENTER>
33622 <P>
33624 it is likely that the canonical name will be something like
33626 <P>
33627 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
33628 <P>
33630 Or it may be the case that
33632 <P>
33633 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
33634 <P>
33636 is really an alias (a DNS CNAME) for
33638 <P>
33639 <CENTER><SAMP>othername.example.com</SAMP></CENTER>
33640 <P>
33642 If this feature is not set, then the canonicalized names will be used.
33643 If this feature is set, then the name you typed in (or put in your
33644 configuration) will be used.
33646 <P><UL>
33647 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33648 </UL>
33649 <P>
33650 <End of help on this topic>
33651 </BODY>
33652 </HTML>
33653 ====== h_config_quell_empty_dirs ======
33654 <HTML>
33655 <HEAD>
33656 <TITLE>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></TITLE>
33657 </HEAD>
33658 <BODY>
33659 <H1>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></H1>
33661 This feature causes Alpine to remove from the display any directories
33662 that do not contain at least one file or directory. This can be useful
33663 to prevent overly cluttered folder lists when a collection is stored on
33664 a server that treats all names as both a folder and a directory.
33666 <P>
33667 Note, enabling this feature can cause surprising behavior! For example,
33668 you can still use Add to create a directory, but unless you immediately
33669 enter that directory and create a folder, that newly created directory
33670 may not be displayed next time you enter the folder list.
33672 <P>
33673 The description above is not quite correct.
33674 Only directories which potentially may hold messages are hidden if empty.
33675 That is, a directory which is really just a directory and is not selectable
33676 as a folder will not be hidden.
33677 Such directories can occur on servers that treat most names as both a folder
33678 and a directory.
33679 These directories are typically created implicitly when a folder is created
33680 inside a directory that does not yet exist.
33682 <P>
33683 <UL>
33684 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33685 </UL><P>
33686 <End of help on this topic>
33687 </BODY>
33688 </HTML>
33689 ====== h_config_termcap_wins =====
33690 <HTML>
33691 <HEAD>
33692 <TITLE>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></TITLE>
33693 </HEAD>
33694 <BODY>
33695 <H1>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></H1>
33697 This feature may affect Alpine's low-level input routines. Termcap (or
33698 terminfo, depending on how your copy of Alpine was compiled and linked)
33699 is the name of the database that describes terminal capabilities. In
33700 particular, it describes the sequences of characters that various keys
33701 will emit.
33703 <P>
33704 An example would be the Up Arrow key on the keyboard. Up
33705 Arrow is not a distinct character on most Unix systems. When you press
33706 the Up Arrow key a short sequence of characters are produced. This
33707 sequence is supposed to be described in the termcap database by the
33708 "ku" capability (or by the "kcuu1" capability if you
33709 are using terminfo instead of termcap).
33711 <P>
33712 By default, Alpine defines some terminal
33713 escape sequences that are commonly used. For example, the sequence
33714 "ESC O A" is recognized as an Up Arrow key. The sequence
33715 "ESC [ A"
33716 is also recognized as an Up Arrow key. These are chosen because common
33717 terminals like VT100's or ANSI standard terminals produce these
33718 sequences when you press the Up Arrow key.
33720 <P>
33721 If your system's termcap
33722 (terminfo) database assigns some other function to the sequence
33723 "ESC O A"
33724 it is usually ignored by Alpine. Also, if your termcap (terminfo)
33725 database assigns a sequence that doesn't begin with an escape
33726 character (<SAMP>ESC</SAMP>) it is usually ignored by Alpine.
33727 This usually works fine
33728 because most terminals emit the escape sequences that Alpine has defined
33729 by default. We have also found that it is usually better to have these
33730 defaults take precedence over the definitions contained in the database
33731 because the defaults are more likely to be correct than the database.
33733 <P>
33734 There are some terminals where this breaks down. If you want Alpine to
33735 believe the definitions given in your termcap (terminfo) database in
33736 preference to the defaults the Alpine itself sets up, then you may turn
33737 this feature on. Then, sequences of characters that are defined in
33738 both termcap (terminfo) and in Alpine's set of defaults will be
33739 interpreted the way that termcap (terminfo) says they should be
33740 interpreted. Also, if your terminal capabilities database assigns a
33741 sequence that doesn't begin with escape, it will not be ignored.
33743 <P>
33744 <UL>
33745 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33746 </UL><P>
33747 <End of help on this topic>
33748 </BODY>
33749 </HTML>
33750 ====== h_config_cruise_mode =====
33751 <HTML>
33752 <HEAD>
33753 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></TITLE>
33754 </HEAD>
33755 <BODY>
33756 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></H1>
33758 This feature affects Alpine's behavior when you hit the
33759 "Space Bar" at
33760 the end of a displayed message. Typically, Alpine complains that the end
33761 of the text has already been reached. Setting this feature causes such
33762 keystrokes to be interpreted as if the "Tab" key had been hit, thus
33763 taking you to the next "interesting" message,
33764 or scanning ahead to the
33765 next incoming folder with "interesting" messages.
33767 <P>
33768 <UL>
33769 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33770 </UL><P>
33771 <End of help on this topic>
33772 </BODY>
33773 </HTML>
33774 ====== h_config_cruise_mode_delete =====
33775 <HTML>
33776 <HEAD>
33777 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></TITLE>
33778 </HEAD>
33779 <BODY>
33780 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></H1>
33782 This feature modifies the behavior of Alpine's
33783 <A HREF="h_config_cruise_mode">"<!--#echo var="FEAT_enable-cruise-mode"-->"</A> feature.
33784 Setting this feature causes Alpine to implicitly delete read
33785 messages when it moves on to display the next "interesting" message.
33786 <P>
33787 NOTE: Beware when enabling this feature AND the
33788 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
33789 feature.
33790 <P>
33791 <UL>
33792 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33793 </UL><P>
33794 <End of help on this topic>
33795 </BODY>
33796 </HTML>
33797 ====== h_config_slash_coll_entire =====
33798 <HTML>
33799 <HEAD>
33800 <TITLE>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></TITLE>
33801 </HEAD>
33802 <BODY>
33803 <H1>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></H1>
33805 The slash (/) command is available from the MESSAGE INDEX screen when
33806 the folder is sorted by either Threads or OrderedSubject, and the
33807 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
33808 is set to something other than "none".
33809 Normally, the slash command Collapses or Expands the subthread that
33810 starts at the currently highlighted message, if any.
33811 If this option is set, then the slash command Collapses or Expands the
33812 <EM>entire</EM> current thread instead of just the subthread.
33813 The current thread is simply the top-level thread that contains the
33814 current message.
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_color_thrd_import =====
33824 <HTML>
33825 <HEAD>
33826 <TITLE>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></TITLE>
33827 </HEAD>
33828 <BODY>
33829 <H1>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></H1>
33831 This option affects only the THREAD INDEX screen.
33832 Whether or not you ever see a THREAD INDEX screen depends on the setting
33833 of the configuration option
33834 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
33835 and on the sort order of the index.
33837 <P>
33838 If a message within a thread is flagged as Important
33839 and this option is set, then
33840 the entire line in the THREAD INDEX will be colored the color of the
33841 Index-important Symbol, which can be set using the
33842 <A HREF="h_color_setup">Setup Kolor</A> screen.
33844 <P>
33845 <UL>
33846 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33847 </UL><P>
33848 <End of help on this topic>
33849 </BODY>
33850 </HTML>
33851 ====== h_config_allow_goto =====
33852 <HTML>
33853 <HEAD>
33854 <TITLE>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></TITLE>
33855 </HEAD>
33856 <BODY>
33857 <H1>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></H1>
33859 This feature modifies the behavior of Alpine's file browser. Setting this
33860 feature causes Alpine to offer the "G Goto" command in the file browser.
33861 That is the default.
33863 <P>
33865 The Goto command allows you to explicitly type in the desired directory.
33866 <P>
33867 <End of help on this topic>
33868 </BODY></HTML>
33869 ====== h_config_add_ldap =====
33870 <HTML>
33871 <HEAD>
33872 <TITLE>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></TITLE>
33873 </HEAD>
33874 <BODY>
33875 <H1>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></H1>
33877 If both the Directory option
33878 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
33879 and this feature are set,
33880 then when an implicit directory lookup is done from the
33881 composer you will automatically be prompted to add the result of the
33882 directory lookup to your address book.
33883 <P>
33884 <UL>
33885 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33886 </UL><P>
33887 <End of help on this topic>
33888 </BODY>
33889 </HTML>
33890 ===== h_patterns_compat_behavior =====
33891 <HTML>
33892 <HEAD>
33893 <TITLE>Rules Behavior Changes in Pine 4.50</TITLE>
33894 </HEAD>
33895 <BODY>
33896 <H1>Rules Behavior Changes in Pine 4.50</H1>
33898 In Alpine, Rules that contain unrecognized elements
33899 are ignored.
33900 In most cases, the unrecognized elements will be something that was
33901 added as a new Rules feature in a later version of Alpine.
33902 In versions of Pine <EM>prior</EM> to 4.50, Pine did <EM>not</EM>
33903 ignore rules that contained unrecognized elements.
33904 For example, a new element of Rules that was added in Pine 4.50 is
33905 Age interval.
33906 Suppose you add an Indexcolor rule, using version Pine 4.50 or later, that colors
33907 all messages older than a week red.
33908 Now, if you run Pine 4.44 using that same configuration file, it will not
33909 recognize the Age interval and so will just ignore it.
33910 That means that all messages will match that rule so all messages will
33911 be colored red when using Pine version 4.44.
33913 <P>
33914 This behavior was considered a bug so it is fixed in Alpine and Pine 4.50 and later.
33915 However, since the behavior still exists in versions prior to Pine 4.50 and
33916 since Filtering is a potentially destructive operation, another measure
33917 was taken to attempt to avoid unintentional Filtering of messages.
33918 The first time that you run Alpine or a Pine that is version 4.50 or greater,
33919 the rules in your Filters configuration variable ("Patterns-Filters")
33920 will be copied to a new Filters configuration variable
33921 with a different name ("Patterns-Filters2").
33922 From then on, Alpine will continue to use the new
33923 variable.
33924 Of course, Pine version 4.44 or lower will continue to use the old
33925 variable.
33926 That means that if you are using Alpine
33927 and also using a version of Pine that is older than 4.50, they will not
33928 share the configuration information about Filters.
33929 If you make a change in one version you won't see it in the other version.
33931 <P>
33932 Since Scoring can be used to trigger Filtering, the same thing has been
33933 done for Score rules.
33934 The old configuration variable name is ("Patterns-Scores")
33935 and the new name is ("Patterns-Scores2").
33936 The same is not true of Role, Indexcolor, and Other rules that are
33937 thought to be less harmful when a mistake is made.
33939 <P>
33940 <End of help on this topic>
33941 </BODY>
33942 </HTML>
33943 ======= h_config_filt_opts_sentdate =======
33944 <HTML>
33945 <HEAD>
33946 <TITLE>PATTERN FEATURE: Use-Date-Header-For-Age</TITLE>
33947 </HEAD>
33948 <BODY>
33949 <H1>PATTERN FEATURE: Use-Date-Header-For-Age</H1>
33951 By default, the Age interval of a Pattern uses a message's time of
33952 arrival to compute the age of the message.
33953 If this feature is set, the date in the message's Date header will
33954 be used instead.
33955 <P>
33956 <End of help on this topic>
33957 </BODY>
33958 </HTML>
33959 ======= h_config_filt_opts_notdel =======
33960 <HTML>
33961 <HEAD>
33962 <TITLE>FILTER FEATURE: Move-Only-if-Not-Deleted</TITLE>
33963 </HEAD>
33964 <BODY>
33965 <H1>FILTER FEATURE: Move-Only-if-Not-Deleted</H1>
33967 If this option is set then a message will be moved into the
33968 specified folder only if it is not marked for deletion.
33969 This is useful if you have multiple Alpine sessions running
33970 simultaneously and you don't want messages to be filtered into a
33971 folder more than once.
33972 It is also useful if you want to filter
33973 only the "undeleted" messages in a newsgroup into a folder.
33974 This method is not foolproof.
33975 There may be cases where a message
33976 gets marked deleted and so it is never filtered into the folder.
33977 For example, if you deleted it in another Alpine session or another mail
33978 program that didn't use the filtering rule.
33979 <P>
33980 This option has no effect if the Filter Action is not set to Move.
33981 <P>
33982 <End of help on this topic>
33983 </BODY>
33984 </HTML>
33985 ======= h_config_filt_opts_nonterm =======
33986 <HTML>
33987 <HEAD>
33988 <TITLE>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</TITLE>
33989 </HEAD>
33990 <BODY>
33991 <H1>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</H1>
33993 If this option is set then this is a non-terminating rule.
33994 Usually, for each message, Alpine searches through the Filter Rules until
33995 a match is found and then it performs the action associated with that rule.
33996 Rules following the match are not considered.
33997 If this option is set then the search for matches will continue at the next
33998 rule.
33999 <P>
34000 If a non-terminating rule matches then the actions associated with
34001 that rule, except for any implied deletion of the message, are performed
34002 before the match for the next rule is checked.
34003 For example, if the non-terminating rule sets the Important status, then that
34004 status will be set when the next rule is considered.
34005 However, if the non-terminating rule Moves the message, the message will
34006 actually be copied instead of copied and deleted so that it is still there
34007 for the next rule.
34008 A moved message is deleted after all the relevant rules have been checked.
34009 The name of the "Move" action is confusing in this case because
34010 a single message can be moved to more than one folder.
34011 It turns the Move into a Copy instead, but it is still followed by a deletion
34012 at the end.
34013 <P>
34014 This option may be useful if you want to have a single message filtered to
34015 two different folders because it matches two different Patterns.
34016 For example, suppose you normally filter messages to a particular mailing
34017 list into one folder, and messages addressed directly to you into a second
34018 folder.
34019 If a message is sent to both you and the list (and you can tell that by
34020 looking at the headers of the message) this option may give you a convenient
34021 way to capture a copy to each folder.
34022 (It may also cause you to capture two copies to each folder,
34023 depending on whether your mail system delivers one or two copies of the
34024 message to you and on how the list works.)
34025 <P>
34026 <End of help on this topic>
34027 </BODY>
34028 </HTML>
34029 ===== h_mainhelp_smime ======
34030 <HTML>
34031 <HEAD>
34032 <TITLE>S/MIME Overview</TITLE>
34033 </HEAD>
34034 <BODY>
34035 <H1>S/MIME Overview</H1>
34037 S/MIME is a standard for the public key encryption and signing of email.
34038 UNIX Alpine contains a basic implementation of S/MIME based on
34039 the <A HREF="http://www.openssl.org/">OpenSSL</A> libraries.
34040 To check if this version of Alpine supports S/MIME look at
34041 <A HREF="X-Alpine-Config:">Supported Options in this Alpine</A> and look
34042 for "S/MIME" under the "Encryption" heading.
34043 <P>
34044 Some limitations:
34045 <UL>
34046 <LI> There is no PC-Alpine implementation.
34047 <LI> There is no provision for checking for CRLs
34048 (Certificate Revocation Lists) in Alpine.
34049 <LI> This built-in S/MIME implementation is not compatible with and does not help with PGP.
34050 <LI> There is no mechanism available for feeding either an entire incoming
34051 or an entire outgoing message to an external
34052 filter and using that external filter to do S/MIME or PGP processing.
34053 <LI> Because the implementation currently uses OpenSSL, there is only a very
34054 limited integration with the Mac OS Keychain (the storing and access of
34055 public certificates).
34056 </UL>
34057 <P>
34058 The S/MIME configuration screen is reached by going to the Main Menu and typing
34059 the "S Setup" command followed by "M S/MIME".
34060 <P>
34062 <H2>S/MIME BASICS</H2>
34064 In order to digitally sign messages you send you must have a public/private key-pair.
34065 This may be obtained from a public Certificate Authority (CA) such as Thawte, Verisign, Comodo,
34066 or GoDaddy; or from a smaller CA such as a university which provides certificates for its
34067 users or a company which provides certificates for its workers.
34068 These certificates are bound to an email address, so the identity being verified is the
34069 email address not a person's name.
34070 <P>
34071 Mail is signed by using the sender's private key, which only the owner of the private key
34072 has access to.
34073 The signature is verified using the signer's public key, which anyone can
34074 have access to.
34075 With Alpine, the first time you receive a signed message the public key of the
34076 sender will be stored for future use.
34078 <P>
34079 Mail is encrypted using the recipient's public key and decrypted by
34080 the recipient with their private key.
34082 <P>
34083 You need a key of your own in order to sign outgoing messages and to have others
34084 encrypt messages sent to you.
34085 You do not need a key of your own to verify signed messages sent by others or to
34086 encrypt messages sent to others.
34088 <H2>ALPINE S/MIME CERTIFICATE STORAGE</H2>
34090 By default UNIX Alpine stores the certificates it uses in a directory in your
34091 home directory.
34092 The directory name is
34093 <P>
34094 <CENTER><SAMP>.alpine-smime</SAMP></CENTER>
34095 <P>
34096 Within that directory are three subdirectories.
34097 Each of the three subdirectories contains files with PEM-encoded contents,
34098 the default format for OpenSSL.
34099 The "<SAMP>public</SAMP>" directory contains public certificates.
34100 The files within that directory have names that are email addresses with the
34101 suffix "<SAMP>.crt</SAMP>" appended.
34102 An example filename is
34103 <P>
34104 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
34105 <P>
34106 The "<SAMP>private</SAMP>" directory contains private keys, probably just one for
34107 your private key.
34108 These are also email addresses but with the suffix "<SAMP>.key</SAMP>" instead.
34109 The third directory is "<SAMP>ca</SAMP>" and it contains certificates for any Certificate
34110 Authorities that you want to trust but that aren't contained in the set of system CAs.
34111 Those files may have arbitrary names as long as they end with the
34112 suffix "<SAMP>.crt</SAMP>".
34114 <H2>HOW TO SIGN AND ENCRYPT</H2>
34116 If you have a certificate you may sign outgoing messages.
34117 After typing the Ctrl-X command to send a message you will see the prompt
34118 <P>
34119 <CENTER><SAMP>Send message?</SAMP></CENTER>
34120 <P>
34121 Available subcommands include "G Sign" and "E Encrypt".
34122 Typing the "G" command will change the prompt to
34123 <P>
34124 <CENTER><SAMP>Send message (Signed)?</SAMP></CENTER>
34125 <P>
34126 Typing the "E" command will change the prompt to
34127 <P>
34128 <CENTER><SAMP>Send message (Encrypted)?</SAMP></CENTER>
34129 <P>
34130 You may even type both to get
34131 <P>
34132 <CENTER><SAMP>Send message (Encrypted, Signed)?</SAMP></CENTER>
34133 <P>
34135 <H2>HOW TO READ SIGNED OR ENCRYPTED MESSAGES</H2>
34137 The reading of a signed message should not require any special action on
34138 your part.
34139 There should be an editorial addition at the start of the message which
34140 says either
34141 <P>
34142 <CENTER><SAMP>This message was cryptographically signed.</SAMP></CENTER>
34143 <P>
34144 or
34145 <P>
34146 <CENTER><SAMP>This message was cryptographically signed but the signature could not be verified.</SAMP></CENTER>
34147 <P>
34148 If an encrypted message is sent to you the encrypted text will not
34149 be shown.
34150 You will have to type the "Ctrl-D Decrypt" command (from the screen where
34151 you are viewing the message) and supply your passphrase when asked.
34152 <P>
34153 For a signed or encrypted message there is also a "Ctrl-E Security" command
34154 which gives you some information about the certificate used to sign or encrypt the message.
34156 <H2>MISCELLANEOUS</H2>
34158 You may have access to a private certificate in the PKCS12 format,
34159 which would sometimes be in a file with a ".p12" suffix.
34160 The UNIX shell command
34161 <P>
34162 <CENTER><SAMP>openssl pkcs12 -in file.p12 -out file.pem</SAMP></CENTER>
34163 <P>
34164 may work to convert that from the PKCS12 format to the PEM format.
34165 Then that file could be placed in the "<SAMP>private</SAMP>"
34166 directory with a filename of your email address followed by the
34167 suffix "<SAMP>.key</SAMP>".
34169 <P>
34170 <End of help on this topic>
34171 </BODY>
34172 </HTML>
34173 ====== h_config_smime_pubcertdir =====
34174 <HTML>
34175 <HEAD>
34176 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></TITLE>
34177 </HEAD>
34178 <BODY>
34179 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></H1>
34181 UNIX Alpine only.
34182 <P>
34183 If the option
34184 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
34185 is set then this option will have no effect.
34186 <P>
34187 Normally, Public Certificates for use with S/MIME will be stored in the directory
34188 which is the value of this option.
34189 Those certificates will be stored in PEM format, one certificate per file.
34190 The name of the file for the certificate corresponding to
34191 <P>
34192 <CENTER><SAMP>emailaddress</SAMP></CENTER>
34193 <P>
34194 should be
34195 <P>
34196 <CENTER><SAMP>emailaddress.crt</SAMP></CENTER>
34197 <P>
34198 For example, a file for user@example.com would be in the file
34199 <P>
34200 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
34201 <P>
34202 in this directory.
34203 <P>
34204 Use the Setup/SMIME screen to modify this variable.
34205 <P>
34206 Typically, the public certificates that you have will come from S/MIME signed
34207 messages that are sent to you.
34208 Alpine will extract the public certificate from the signed message and store
34209 it in the certificates directory.
34210 These PEM format public certificates look something like:
34211 <PRE>
34212 -----BEGIN CERTIFICATE-----
34213 MIIFvTCCBKWgAwIBAgIQD4fYFHVI8T20yN4nus097DANBgkqhkiG9w0BAQUFADCB
34214 rjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2Ug
34215 Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExho
34216 ...
34217 2b9KGqDyMWW/rjNnmpjzjT2ObGM7lRA8lke4FLOLajhrz4ogO3b4DFfAAM1VSZH8
34218 D6sOwOLJZkLY8FRsfk63K+2EMzA2+qAzMKupgeTLqXIf
34219 -----END CERTIFICATE-----
34220 </PRE>
34221 <P>
34222 <UL>
34223 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34224 </UL><P>
34225 <P>
34226 <UL>
34227 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34228 </UL><P>
34229 <End of help on this topic>
34230 </BODY>
34231 </HTML>
34232 ====== h_config_smime_pubcertcon =====
34233 <HTML>
34234 <HEAD>
34235 <TITLE>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></TITLE>
34236 </HEAD>
34237 <BODY>
34238 <H1>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></H1>
34240 UNIX Alpine only.
34241 <P>
34242 If this option is set it will be used instead of
34243 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
34244 <P>
34245 This option gives you a way to store certificates remotely on an IMAP server
34246 instead of storing the certificates one per file locally.
34247 In order to do that you just give this option a remote folder name for a folder
34248 which does not yet exist.
34249 The name is similar to the name you might use for a remote configuration file.
34250 A remote folder name might look something like:
34251 <P>
34252 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/publiccerts</SAMP></CENTER>
34253 <P>
34254 See
34255 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34256 about the syntax of folder names.
34257 <P>
34258 Use the Setup/SMIME screen to modify this variable.
34259 <P>
34260 <UL>
34261 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34262 </UL><P>
34263 <P>
34264 <UL>
34265 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34266 </UL><P>
34267 <End of help on this topic>
34268 </BODY>
34269 </HTML>
34270 ====== h_config_smime_privkeydir =====
34271 <HTML>
34272 <HEAD>
34273 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></TITLE>
34274 </HEAD>
34275 <BODY>
34276 <H1>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></H1>
34278 UNIX Alpine only.
34279 <P>
34280 In order to sign outgoing S/MIME messages you will need a
34281 personal digital ID certificate.
34282 You will usually get such a certificate from a certificate authority such as
34283 Thawte or CAcert.
34284 (In order to encrypt outgoing messages you don't need a personal digital ID, you
34285 need the public certificate of the recipient instead.)
34286 If the option
34287 <A HREF="h_config_smime_privkeycon"><!--#echo var="VAR_smime-private-key-container"--></A>
34288 is set then this option will have no effect.
34289 <P>
34290 Normally, Private Keys for use with S/MIME will be stored in the directory
34291 which is the value of this option.
34292 Those certificates will be stored in PEM format, one certificate per file.
34293 The name of the file for the certificate corresponding to your
34294 <P>
34295 <CENTER><SAMP>emailaddress</SAMP></CENTER>
34296 <P>
34297 should be
34298 <P>
34299 <CENTER><SAMP>emailaddress.key</SAMP></CENTER>
34300 <P>
34301 For example, if your address is user@example.com the name of the file would be
34302 <P>
34303 <CENTER><SAMP>user@example.com.key</SAMP></CENTER>
34304 <P>
34305 in this directory.
34306 <P>
34307 Use the Setup/SMIME screen to modify this variable.
34308 <P>
34309 Typically, the private key that you have will come from a Certificate
34310 Authority.
34311 The private key should be stored in a PEM format file that
34312 looks something like:
34313 <PRE>
34314 -----BEGIN RSA PRIVATE KEY-----
34315 Proc-Type: 4,ENCRYPTED
34316 DEK-Info: DES-EDE3-CBC,2CBD328FD84CF5C6
34318 YBEXYLgLU9NJoc1V+vJ6UvcF08RX54S6jXsmgL0b5HGkudG6fhnmHkH7+UCvM5NI
34319 SXO/F8iuZDfs1VGG0NyitkFZ0Zn2vfaGovBvm15gx24b2xnZDLRB7/bNZkurnK5k
34320 VjAjZ2xXn2hFp2GJwqRdmxYNqsKGu52B99oti5HUWuZ2GFRaWjn5hYOqeApZE2uA
34321 ...
34322 oSRqfI51UdSRt0tmGhHeTvybUVrHm9eKft8TTGf+qSBqzSc55CsmoVbRzw4Nfhix
34323 m+4TJybNGNfAgOctSkEyY/OCb49fRRQTCBZVIhzLGGmpYmkO55HbIA==
34324 -----END RSA PRIVATE KEY-----
34325 </PRE>
34326 <P>
34327 <UL>
34328 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34329 </UL><P>
34330 <P>
34331 <UL>
34332 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34333 </UL><P>
34334 <End of help on this topic>
34335 </BODY>
34336 </HTML>
34337 ====== h_config_smime_privkeycon =====
34338 <HTML>
34339 <HEAD>
34340 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-container"--></TITLE>
34341 </HEAD>
34342 <BODY>
34343 <H1>OPTION: <!--#echo var="VAR_smime-private-key-container"--></H1>
34345 UNIX Alpine only.
34346 <P>
34347 If this option is set it will be used instead of
34348 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
34349 <P>
34350 This option gives you a way to store keys remotely on an IMAP server
34351 instead of storing the keys one per file locally.
34352 In order to do that you just give this option a remote folder name for a folder
34353 which does not yet exist.
34354 The name is similar to the name you might use for a remote configuration file.
34355 A remote folder name might look something like:
34356 <P>
34357 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/privatekeys</SAMP></CENTER>
34358 <P>
34359 See
34360 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34361 about the syntax of folder names.
34362 <P>
34363 Use the Setup/SMIME screen to modify this variable.
34364 <P>
34365 <UL>
34366 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34367 </UL><P>
34368 <P>
34369 <UL>
34370 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34371 </UL><P>
34372 <End of help on this topic>
34373 </BODY>
34374 </HTML>
34375 ====== h_config_smime_cacertdir =====
34376 <HTML>
34377 <HEAD>
34378 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></TITLE>
34379 </HEAD>
34380 <BODY>
34381 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></H1>
34383 UNIX Alpine only.
34384 <P>
34385 If the option
34386 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>
34387 is set then this option will have no effect.
34388 <P>
34389 CACert is a shorthand name for certification authority certificate.
34390 Normally Alpine will use the CACerts that are located in the standard system
34391 location for CACerts.
34392 It may be the case that one of your correspondents has a Digital ID which has
34393 been signed by a certificate authority that is not in the regular set of system certificate
34394 authorities.
34395 You may supplement the system list by adding further certificates of your own.
34396 These should be stored in the directory
34397 which is the value of this option.
34398 The certificates will be stored in PEM format, one certificate per file.
34399 The names of the files can be anything ending in ".crt".
34400 <P>
34401 Use the Setup/SMIME screen to modify this variable.
34402 <P>
34403 These PEM format CA certificates look very similar to your public
34404 certificates for particular email addresses
34405 (<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>).
34406 <P>
34407 <UL>
34408 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34409 </UL><P>
34410 <P>
34411 <UL>
34412 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34413 </UL><P>
34414 <End of help on this topic>
34415 </BODY>
34416 </HTML>
34417 ====== h_config_smime_cacertcon =====
34418 <HTML>
34419 <HEAD>
34420 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></TITLE>
34421 </HEAD>
34422 <BODY>
34423 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></H1>
34425 UNIX Alpine only.
34426 <P>
34427 If this option is set it will be used instead of
34428 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
34429 <P>
34430 This option gives you a way to store certificates remotely on an IMAP server
34431 instead of storing the certificates one per file locally.
34432 In order to do that you just give this option a remote folder name for a folder
34433 which does not yet exist.
34434 The name is similar to the name you might use for a remote configuration file.
34435 A remote folder name might look something like:
34436 <P>
34437 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/cacerts</SAMP></CENTER>
34438 <P>
34439 See
34440 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34441 about the syntax of folder names.
34442 <P>
34443 Use the Setup/SMIME screen to modify this variable.
34444 <P>
34445 <UL>
34446 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34447 </UL><P>
34448 <P>
34449 <UL>
34450 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34451 </UL><P>
34452 <End of help on this topic>
34453 </BODY>
34454 </HTML>
34455 ========== h_config_smime_sign_by_default ==========
34456 <HTML>
34457 <HEAD>
34458 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></TITLE>
34459 </HEAD>
34460 <BODY>
34461 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></H1>
34463 UNIX Alpine only.
34464 <P>
34465 This feature only has an effect if your version of Alpine includes
34466 support for S/MIME.
34467 It affects Alpine's behavior when you send a message.
34468 If this option is set, the "Sign" option will default to ON when sending messages.
34469 <P>
34470 Only the default value is affected.
34471 In any case, you may still toggle the Signing option on or off before sending
34472 with the "G Sign" command (provided you have a personal digital ID
34473 certificate).
34474 <P>
34475 <UL>
34476 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34477 </UL><P>
34478 <P>
34480 <UL>
34481 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34482 </UL><P>
34483 <End of help on this topic>
34484 </BODY>
34485 </HTML>
34486 ========== h_config_smime_pubcerts_in_keychain ==========
34487 <HTML>
34488 <HEAD>
34489 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></TITLE>
34490 </HEAD>
34491 <BODY>
34492 <H1>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></H1>
34494 UNIX Alpine only.
34495 <P>
34496 If this feature is set the Mac OS X default keychain will be used as the place
34497 to store public certificates instead of a
34498 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
34499 or a
34500 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
34501 <P>
34502 <UL>
34503 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34504 </UL><P>
34505 <P>
34506 <UL>
34507 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34508 </UL><P>
34509 <End of help on this topic>
34510 </BODY>
34511 </HTML>
34512 ========== h_config_smime_dont_do_smime ==========
34513 <HTML>
34514 <HEAD>
34515 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></TITLE>
34516 </HEAD>
34517 <BODY>
34518 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></H1>
34520 UNIX Alpine only.
34521 <P>
34522 Setting this feature turns off all of Alpine's S/MIME support.
34523 You might want to set this if you are having trouble due to the S/MIME support.
34524 <P>
34525 <UL>
34526 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34527 </UL><P>
34528 <P>
34530 <UL>
34531 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34532 </UL><P>
34533 <End of help on this topic>
34534 </BODY>
34535 </HTML>
34536 ========== h_config_smime_encrypt_by_default ==========
34537 <HTML>
34538 <HEAD>
34539 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></TITLE>
34540 </HEAD>
34541 <BODY>
34542 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></H1>
34544 UNIX Alpine only.
34545 <P>
34546 This feature only has an effect if your version of Alpine includes
34547 support for S/MIME.
34548 It affects Alpine's behavior when you send a message.
34549 If this option is set, the "Encrypt" option will default to ON when sending messages.
34550 <P>
34551 Only the default value is affected.
34552 In any case, you may still toggle the Encrypt option on or off before sending
34553 with the "E Encrypt" command (provided you have a the public digital ID
34554 for the recipient).
34555 <P>
34556 <UL>
34557 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34558 </UL><P>
34559 <P>
34561 <UL>
34562 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34563 </UL><P>
34564 <End of help on this topic>
34565 </BODY>
34566 </HTML>
34567 ========== h_config_smime_remember_passphrase ==========
34568 <HTML>
34569 <HEAD>
34570 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></TITLE>
34571 </HEAD>
34572 <BODY>
34573 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></H1>
34575 UNIX Alpine only.
34576 <P>
34577 This feature only has an effect if your version of Alpine includes
34578 support for S/MIME.
34579 If this option is set, you will only have to enter your passphrase for your private key
34580 once during an Alpine session.
34581 <P>
34582 <UL>
34583 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34584 </UL><P>
34585 <P>
34587 <UL>
34588 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34589 </UL><P>
34590 <End of help on this topic>
34591 </BODY>
34592 </HTML>
34593 ====== h_config_smime_transfer_pub_to_con =====
34594 <HTML>
34595 <HEAD>
34596 <TITLE>S/MIME: Transfer Public Certs to Container</TITLE>
34597 </HEAD>
34598 <BODY>
34599 <H1>S/MIME: Transfer Public Certs to Container</H1>
34601 UNIX Alpine only.
34602 <P>
34603 The Transfer command will copy the public certificates in your configured
34604 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
34605 to the container in your configured
34606 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
34607 This might be useful if you decide to switch from using a cert directory to a cert
34608 container.
34609 <P>
34610 Warning: Any previous contents in the container will be lost.
34611 <P>
34612 <UL>
34613 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34614 </UL><P>
34615 <P>
34616 <UL>
34617 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34618 </UL><P>
34619 <End of help on this topic>
34620 </BODY>
34621 </HTML>
34622 ====== h_config_smime_transfer_pub_to_dir =====
34623 <HTML>
34624 <HEAD>
34625 <TITLE>S/MIME: Transfer Public Certs to Directory</TITLE>
34626 </HEAD>
34627 <BODY>
34628 <H1>S/MIME: Transfer Public Certs to Directory</H1>
34630 UNIX Alpine only.
34631 <P>
34632 The Transfer command will copy the public certificates in your configured
34633 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
34634 to the directory in your configured
34635 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
34636 This might be useful if you decide to switch from using a cert container to a cert
34637 directory.
34638 <P>
34639 <UL>
34640 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34641 </UL><P>
34642 <P>
34643 <UL>
34644 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34645 </UL><P>
34646 <End of help on this topic>
34647 </BODY>
34648 </HTML>
34649 ====== h_config_smime_transfer_priv_to_con =====
34650 <HTML>
34651 <HEAD>
34652 <TITLE>S/MIME: Transfer Private Keys to Container</TITLE>
34653 </HEAD>
34654 <BODY>
34655 <H1>S/MIME: Transfer Private Keys to Container</H1>
34657 UNIX Alpine only.
34658 <P>
34659 The Transfer command will copy the private keys in your configured
34660 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
34661 to the container in your configured
34662 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
34663 This might be useful if you decide to switch from using a key directory to a key
34664 container.
34665 <P>
34666 Warning: Any previous contents in the container will be lost.
34667 <P>
34668 <UL>
34669 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34670 </UL><P>
34671 <P>
34672 <UL>
34673 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34674 </UL><P>
34675 <End of help on this topic>
34676 </BODY>
34677 </HTML>
34678 ====== h_config_smime_transfer_priv_to_dir =====
34679 <HTML>
34680 <HEAD>
34681 <TITLE>S/MIME: Transfer Private Keys to Directory</TITLE>
34682 </HEAD>
34683 <BODY>
34684 <H1>S/MIME: Transfer Private Keys to Directory</H1>
34686 UNIX Alpine only.
34687 <P>
34688 The Transfer command will copy the private keys in your configured
34689 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
34690 to the directory in your configured
34691 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
34692 This might be useful if you decide to switch from using a key container to a key
34693 directory.
34694 <P>
34695 <UL>
34696 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34697 </UL><P>
34698 <P>
34699 <UL>
34700 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34701 </UL><P>
34702 <End of help on this topic>
34703 </BODY>
34704 </HTML>
34705 ====== h_config_smime_transfer_cacert_to_con =====
34706 <HTML>
34707 <HEAD>
34708 <TITLE>S/MIME: Transfer CA Certs to Container</TITLE>
34709 </HEAD>
34710 <BODY>
34711 <H1>S/MIME: Transfer CA Certs to Container</H1>
34713 UNIX Alpine only.
34714 <P>
34715 The Transfer command will copy the CA certificates in your configured
34716 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>
34717 to the container in your configured
34718 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
34719 This might be useful if you decide to switch from using a CA cert directory to a CA cert
34720 container.
34721 <P>
34722 Warning: Any previous contents in the container will be lost.
34723 <P>
34724 <UL>
34725 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34726 </UL><P>
34727 <P>
34728 <UL>
34729 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34730 </UL><P>
34731 <End of help on this topic>
34732 </BODY>
34733 </HTML>
34734 ====== h_config_smime_transfer_cacert_to_dir =====
34735 <HTML>
34736 <HEAD>
34737 <TITLE>S/MIME: Transfer CA Certs to Directory</TITLE>
34738 </HEAD>
34739 <BODY>
34740 <H1>S/MIME: Transfer CA Certs to Directory</H1>
34742 UNIX Alpine only.
34743 <P>
34744 The Transfer command will copy the CA certificates in your configured
34745 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
34746 to the directory in your configured
34747 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
34748 This might be useful if you decide to switch from using a CA cert container to a CA cert
34749 directory.
34750 <P>
34751 <UL>
34752 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34753 </UL><P>
34754 <P>
34755 <UL>
34756 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34757 </UL><P>
34758 <End of help on this topic>
34759 </BODY>
34760 </HTML>
34761 ====== h_config_smime_transfer_pubcon_to_key =====
34762 <HTML>
34763 <HEAD>
34764 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
34765 </HEAD>
34766 <BODY>
34767 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
34769 Mac OS X Alpine only.
34770 <P>
34771 The Transfer command will copy the public certificates in your configured
34772 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
34773 to your default Mac OS X Keychain.
34774 This might be useful if you decide to switch from using a cert container to using
34775 the Keychain to store your public certs, which you may do by using the
34776 feature
34777 <A HREF="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></A>.
34778 <P>
34779 <UL>
34780 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34781 </UL><P>
34782 <P>
34783 <UL>
34784 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34785 </UL><P>
34786 <End of help on this topic>
34787 </BODY>
34788 </HTML>
34789 ====== h_config_smime_transfer_pubkey_to_con =====
34790 <HTML>
34791 <HEAD>
34792 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
34793 </HEAD>
34794 <BODY>
34795 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
34797 UNIX Alpine only.
34798 <P>
34799 The Transfer command will copy the public certificates in your configured
34800 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
34801 to your default Mac OS X Keychain.
34802 This might be useful if you decide to switch from using a cert container to using
34803 the Keychain to store your public certs.
34804 <P>
34805 <UL>
34806 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34807 </UL><P>
34808 <P>
34809 <UL>
34810 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34811 </UL><P>
34812 <End of help on this topic>
34813 </BODY>
34814 </HTML>
34815 ====== h_config_smime_public_certificates =====
34816 <HTML>
34817 <HEAD>
34818 <TITLE>S/MIME: Manage Public Certificates</TITLE>
34819 </HEAD>
34820 <BODY>
34821 <H1>S/MIME: Manage Public Certificates</H1>
34823 UNIX Alpine only.
34824 <P>
34825 This menu item allows you to manage your public certificates, this
34826 may include your own public certificate, but it normally includes
34827 certificates of people you correspond with. These certificates are
34828 saved by Alpine automatically when they are found in signed messages
34829 that you receive. This interface allows you to manage them, by
34830 giving you the option to delete them, or trust them (in the case
34831 of self-signed certificates).
34833 <P>
34834 Please note that Alpine will not validate a message that was sent to you
34835 using a self-signed certificate, unless you decide to trust that certificate.
34836 Internally, a certificate is trusted by copying it to the
34837 <A HREF="h_config_smime_certificate_authorities">Certificate Authorities</A>
34838 collection. If you decide that you want to stop trusting a self-signed
34839 certificate, you must delete such certificate from such collection.
34840 <P>
34841 The <B>I</B> Import command available in this screen allows you to
34842 import a command to this collection.
34843 <P>
34844 <UL>
34845 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34846 </UL><P>
34847 <P>
34848 <UL>
34849 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34850 </UL><P>
34851 <End of help on this topic>
34852 </BODY>
34853 </HTML>
34854 ====== h_config_smime_private_keys =====
34855 <HTML>
34856 <HEAD>
34857 <TITLE>S/MIME: Manage Private Keys</TITLE>
34858 </HEAD>
34859 <BODY>
34860 <H1>S/MIME: Manage Private Keys</H1>
34862 UNIX Alpine only.
34863 <P>
34864 This option allows you to manage your private key. Normally a person has only
34865 one key, in the same way that a person only has one valid passport, or ID card,
34866 at any given time. This option allows you to manage private keys. You can
34867 delete them or import them. Additionally, you can view information
34868 about your public certificate, such as the issuer and the dates of validity
34869 of such certificate, among others.
34871 <P>
34872 If you have more than one e-mail address for which you want to use the
34873 same private key, you must add all those addresses to the private key at
34874 the moment that the key is generated. When you receive a signed message using
34875 a key generated for several e-mail addresses, Alpine will save a
34876 certificate for each e-mail address included in such certificate.
34877 <P>
34878 The <B>I</B> Import command available in this screen allows you to
34879 import a command to this collection.
34880 <P>
34881 <UL>
34882 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34883 </UL><P>
34884 <P>
34885 <UL>
34886 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34887 </UL><P>
34888 <End of help on this topic>
34889 </BODY>
34890 </HTML>
34891 ====== h_config_smime_certificate_authorities =====
34892 <HTML>
34893 <HEAD>
34894 <TITLE>S/MIME: Manage Certificate Authorities</TITLE>
34895 </HEAD>
34896 <BODY>
34897 <H1>S/MIME: Manage Certificate Authorities</H1>
34899 UNIX Alpine only.
34900 <P>
34901 This collection contains certificates that are needed to validate the
34902 certificate of another person, and therefore contains certificates that
34903 you trust. Typically a certificate is signed by another entity, called a
34904 certificate authority. This option allows you to manage which certificates
34905 you trust, allowing you to import them and to delete them or view information
34906 about each certificate, such as the issuer and the dates of validity
34907 of such certificate.
34908 <P>
34909 The <B>I</B> Import command available in this screen allows you to
34910 import a command to this collection.
34911 <P>
34912 <UL>
34913 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34914 </UL><P>
34915 <P>
34916 <UL>
34917 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34918 </UL><P>
34919 <End of help on this topic>
34920 </BODY>
34921 </HTML>
34922 ====== h_certificate_information =====
34923 <HTML>
34924 <HEAD>
34925 <TITLE>S/MIME: Certificate Information Screen</TITLE>
34926 </HEAD>
34927 <BODY>
34928 <H1>S/MIME: Certificate Information Screen</H1>
34930 UNIX Alpine only.
34931 <P>
34932 The CERTIFICATE INFORMATION screen shows you information contained in a certificate
34933 such as its owner, e-mail address, issuer, and interval of validity,
34934 among others.
34935 <P>
34936 In the case of public certificates, this screen shows you if there was a
34937 failure when attempting to validate such message. If the certificate is
34938 self-signed, then the <B>T</B> Trust command will be available, which
34939 you can use to trust such certificate and make Alpine not fail validating
34940 signatures signed with such certificate.
34941 <P>
34942 You can also mark a certificate deleted, with the <B>D</B> command, or
34943 remove the deleted mark with the <B>U</B> undelete command.
34944 <P>
34945 In the case of your private key, Alpine shows you the information
34946 from your public key. Additionally, Alpine allows you to see public
34947 and private information about your key, with the <B>B</B> and
34948 <B>R</B> commands respectively.
34949 <UL>
34950 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34951 </UL><P>
34952 <P>
34953 <UL>
34954 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34955 </UL><P>
34956 <End of help on this topic>
34957 </BODY>
34958 </HTML>
34959 ====== h_config_smime_manage_public_menu =====
34960 <HTML>
34961 <HEAD>
34962 <TITLE>S/MIME: Menu of Commands to Manage Public Certificates</TITLE>
34963 </HEAD>
34964 <BODY>
34965 <H1>S/MIME: Commands that Manage Public Certificates</H1>
34967 UNIX Alpine only.
34968 <P>
34969 This screen allows you to manage your public certificates. Available commands and
34970 a short description of what they do follows.
34971 <UL>
34972 <LI> <B>I</B> Imports a public certificate to this collection.
34973 <LI> <B>V</B> View information about a certificate such as the name of the person the
34974 certificate was issued to, its dates of validity, and validity status.
34975 <LI> <B>D</B> Marks a certificate deleted.
34976 <LI> <B>U</B> Removes the deletion mark on a certificate.
34977 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
34978 <LI> <B>T</B> This command is only available for self-signed certificates, and allows you to
34979 trust a certificate by copying it to the collection of trusted certificates.
34980 </UL>
34981 <P>
34982 All commands provide feedback to let you know about their success or failure.
34983 <P>
34984 <UL>
34985 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34986 </UL><P>
34987 <P>
34988 <UL>
34989 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34990 </UL><P>
34991 <End of help on this topic>
34992 </BODY>
34993 </HTML>
34994 ====== h_config_smime_manage_private_menu =====
34995 <HTML>
34996 <HEAD>
34997 <TITLE>S/MIME: Menu of Commands to Manage Private Keys</TITLE>
34998 </HEAD>
34999 <BODY>
35000 <H1>S/MIME: Commands that Manage Private Keys</H1>
35002 UNIX Alpine only.
35003 <P>
35004 This screen allows you to manage your private key. Available commands and
35005 a short description of what they do follows.
35006 <UL>
35007 <LI> <B>I</B> Imports a new public key to this collection.
35008 <LI> <B>V</B> View information about the public certificate corresponding to this
35009 key.
35010 <LI> <B>D</B> Marks a key to be deleted.
35011 <LI> <B>U</B> Removes the deletion mark on a key.
35012 <LI> <B>X</B> Removes all keys marked deleted permanently (cannot be undone).
35013 Note that expunging a private key does not remove the public key, which must
35014 be removed separately.
35015 </UL>
35016 <P>
35017 All commands provide feedback to let you know about their success or failure.
35018 <P>
35019 <UL>
35020 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35021 </UL><P>
35022 <P>
35023 <UL>
35024 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35025 </UL><P>
35026 <End of help on this topic>
35027 </BODY>
35028 </HTML>
35029 ====== h_config_smime_manage_cacerts_menu =====
35030 <HTML>
35031 <HEAD>
35032 <TITLE>S/MIME: Menu of Commands to Manage Certificate Authorities</TITLE>
35033 </HEAD>
35034 <BODY>
35035 <H1>S/MIME: Commands that Manage Certificate Authorities</H1>
35037 UNIX Alpine only.
35038 <P>
35039 This screen allows you to manage your collection of certificates that you
35040 trust. Available commands and a short description of what they do follows.
35041 <UL>
35042 <LI> <B>I</B> Imports a trusted certificate to this collection. This is
35043 done by reading the certificate and validating it. Once a certificate
35044 is found to be valid, it is saved, adding the extension ".crt"
35045 to the certificate, if necessary.
35046 <LI> <B>V</B> View information about this certificate, such as its issuer
35047 and validity dates.
35048 <LI> <B>D</B> Marks a certificate to be deleted.
35049 <LI> <B>U</B> Removes the deletion mark on a certificate.
35050 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
35051 </UL>
35052 <P>
35053 All commands provide feedback to let you know about their success or failure.
35054 <P>
35055 <UL>
35056 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35057 </UL><P>
35058 <P>
35059 <UL>
35060 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35061 </UL><P>
35062 <End of help on this topic>
35063 </BODY>
35064 </HTML>
35065 ====== h_config_lame_list_mode =====
35066 <HTML>
35067 <HEAD>
35068 <TITLE>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></TITLE>
35069 </HEAD>
35070 <BODY>
35071 <H1>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></H1>
35073 This feature modifies the method Alpine uses to ask your IMAP
35074 server for folder names to display in the FOLDER LIST screen.
35075 It is intended to compensate for a small set of IMAP servers that
35076 are programmed to ignore a part of the request, and thus respond
35077 to Alpine's query with nonsensical results.
35078 <P>
35080 If you find that Alpine is erroneously displaying blank folder lists,
35081 try enabling this feature.
35082 <P>
35084 NOTE: Enabling this feature has consequences for the Goto and Save
35085 commands. Many servers allow access to folders outside the area
35086 reserved for your personal folders via some reserved character,
35087 typically '#' (sharp), '~' (tilde) or '/' (slash). This mechanism
35088 allows, at the Goto and Save prompts, quick access to folders
35089 outside your personal folder collection without requiring a specific
35090 collection definition. This behavior will generally not be available
35091 when this feature is enabled.
35093 <P>
35094 <UL>
35095 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35096 </UL><P>
35097 <End of help on this topic>
35098 </BODY>
35099 </HTML>
35100 ====== h_config_enable_mulnewsrcs =====
35101 <HTML>
35102 <HEAD>
35103 <TITLE>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></TITLE>
35104 </HEAD>
35105 <BODY>
35106 <H1>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></H1>
35108 This feature makes it so Alpine can use multiple newsrcs based on
35109 the news server being connected to, which allows for separate lists
35110 of subscribed-to newsgroups. When this feature is not set, there is only
35111 one list of newsgroups.
35112 <P>
35113 Under this feature, the name of a newsrc is based on the news server.
35114 For example, if your <a href="h_config_newsrc_path"><!--#echo var="VAR_newsrc-path"--></a>
35115 is set to ".newsrc", and the news server you are connecting to is
35116 news.example.com, then the newsrc to be used is .newsrc-news.example.com.
35117 Setting this feature for the first time will allow for the option of using
35118 your old newsrc the next time you read news.
35119 <P>
35120 If this feature is set, then the feature
35121 <A HREF="h_config_mulnews_as_typed"><!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></A>
35122 also may affect the name of the newsrc file that is used.
35123 <P>
35124 <UL>
35125 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35126 </UL><P>
35127 <End of help on this topic>
35128 </BODY>
35129 </HTML>
35130 ======= h_ab_export_vcard =======
35131 <HTML>
35132 <HEAD>
35133 <TITLE>Address Book Export Format</TITLE>
35134 </HEAD>
35135 <BODY>
35136 <H1>Address Book Export Format</H1>
35138 You are exporting address book data from Alpine to a file outside of Alpine.
35139 You are being asked to choose the format of the export.
35140 Here are the choices:
35142 <DL>
35143 <DT><EM>A</EM>ddress List</DT>
35144 <DD>
35145 The addresses from the address book entries you are saving
35146 from will be saved one address per line.
35147 Address book lists (those with more than one address) will have
35148 all of their addresses saved separately.
35149 </DD>
35151 <DT><EM>V</EM>Card</DT>
35152 <DD>
35153 The entries will be saved in
35154 <A HREF="h_whatis_vcard">vCard</A> format.
35155 </DD>
35157 <DT><EM>T</EM>ab Separated</DT>
35158 <DD>
35159 The entries will be saved in tab-separated columns.
35160 There will be just 4 columns of data that correspond to Alpine's
35161 Nickname field, Full Name field, Address field, and Comment field.
35162 It might prove useful to Select only the Simple, non-List address book
35163 entries before Saving.
35164 </DD>
35166 <DT><EM>^C</EM> Cancel</DT>
35167 <DD>
35168 Cancel out of the Save.
35169 </DD>
35171 </DL>
35174 <P>
35175 <End of help on this topic>
35176 </BODY>
35177 </HTML>
35178 ====== h_config_predict_nntp_server =====
35179 <HTML>
35180 <HEAD>
35181 <TITLE>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></TITLE>
35182 </HEAD>
35183 <BODY>
35184 <H1>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></H1>
35186 This feature allows Alpine to assume that the open NNTP server at the
35187 time of composition is the NNTP server to which the message should be
35188 posted. This is especially recommended when there are multiple News
35189 collections. If this feature is not set, Alpine will try to post to the first server in
35190 the <a href="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></a> variable. Setting
35191 this feature also negates the need to add News collection servers to
35192 the <!--#echo var="VAR_nntp-server"--> variable.
35193 <P>
35194 This feature can be especially handy when used in conjunction with
35195 <a href="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></a>.
35196 <P>
35197 <UL>
35198 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35199 </UL><P>
35200 <End of help on this topic>
35201 </BODY>
35202 </HTML>
35203 ====== h_config_nntp_search_uses_overview =====
35204 <HTML>
35205 <HEAD>
35206 <TITLE>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></TITLE>
35207 </HEAD>
35208 <BODY>
35209 <H1>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></H1>
35211 This feature should probably be turned on unless it causes trouble.
35212 The results of the NNTP overview command (XOVER) may be used to help
35213 with some searches in news groups.
35214 It should result in quicker response time.
35215 Turning this feature on apparently causes search results which are
35216 different from what you would get with the feature turned off on some
35217 servers.
35218 <P>
35219 <UL>
35220 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35221 </UL><P>
35222 <End of help on this topic>
35223 </BODY>
35224 </HTML>
35225 ====== h_config_thread_sorts_by_arrival =====
35226 <HTML>
35227 <HEAD>
35228 <TITLE>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></TITLE>
35229 </HEAD>
35230 <BODY>
35231 <H1>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></H1>
35233 This feature affects how a threading sort arranges threads. The default way
35234 to arrange threads is by the date of the earliest message in the thread.
35235 This feature arranges threads by the last message to arrive in a thread.
35236 <P>
35237 This feature causes old threads that get recent messages to sort to the bottom,
35238 where previously a message arrival to a thread would not rearrange the order of
35239 that thread.
35240 <P>
35241 <UL>
35242 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35243 </UL><P>
35244 <End of help on this topic>
35245 </BODY>
35246 </HTML>
35247 ====== h_config_textplain_int =====
35248 <HTML>
35249 <HEAD>
35250 <TITLE>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></TITLE>
35251 </HEAD>
35252 <BODY>
35253 <H1>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></H1>
35255 This feature modifies the method Alpine uses to display Text/Plain
35256 MIME attachments from the Attachment Index screen. Normally, the
35257 "View" command searches for any externally defined (usually
35258 via the
35259 "<A HREF="h_config_mailcap_path">Mailcap</A>" file) viewer,
35260 and displays the selected text within that viewer.
35262 <P>
35263 Enabling this feature causes Alpine to ignore any external viewer
35264 settings and always display text with Alpine's internal viewer.
35266 <P>
35267 <UL>
35268 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35269 </UL><P>
35270 <End of help on this topic>
35271 </BODY>
35272 </HTML>
35273 ====== h_config_wp_columns =====
35274 <HTML>
35275 <HEAD>
35276 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></TITLE>
35277 </HEAD>
35278 <BODY>
35279 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></H1>
35281 Web Alpine only.
35282 <P>
35283 This configuration setting specifies the number of horizontal characters
35284 used to format various WebAlpine pages. Smaller values will tend to reduce
35285 the amount of horizontal scrolling required to view pages within narrow
35286 browsers, such as those found on PDAs, and larger values will tend to
35287 spread more information across the page.
35289 <P>
35290 The Message List page uses the width to determine how many characters
35291 to assign each field. Note, a smaller value may result in a disproportionate
35292 amount of blank space between fields on each line. Similarly, a large
35293 value may result in cramped fields or horizontal scrolling.
35295 <P>
35296 The Message View page uses this value to determine when to wrap lines
35297 in displayed message text. Note, a smaller value may result in jagged
35298 right margins or confusing quoting. A larger value may cause lines of text to
35299 run beyond the browser's right edge, requiring horizontal scrolling.
35301 <P>
35302 <UL>
35303 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35304 </UL><P>
35305 <End of help on this topic>
35306 </BODY>
35307 </HTML>
35308 ====== h_config_wp_state =====
35309 <HTML>
35310 <HEAD>
35311 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></TITLE>
35312 </HEAD>
35313 <BODY>
35314 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></H1>
35316 Web Alpine only.
35317 <P>
35318 Various aspects of cross-session state.
35320 <P>
35321 <UL>
35322 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35323 </UL><P>
35324 <End of help on this topic>
35325 </BODY>
35326 </HTML>
35327 ====== h_config_wp_aggstate =====
35328 <HTML>
35329 <HEAD>
35330 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></TITLE>
35331 </HEAD>
35332 <BODY>
35333 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></H1>
35335 Web Alpine only.
35336 <P>
35337 Aggregate operations tab state.
35339 <P>
35340 <UL>
35341 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35342 </UL><P>
35343 <End of help on this topic>
35344 </BODY>
35345 </HTML>
35346 ====== h_config_wp_indexlines =====
35347 <HTML>
35348 <HEAD>
35349 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></TITLE>
35350 </HEAD>
35351 <BODY>
35352 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></H1>
35354 Web Alpine only.
35355 <P>
35356 Number of index lines in table.
35358 <P>
35359 <UL>
35360 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35361 </UL><P>
35362 <End of help on this topic>
35363 </BODY>
35364 </HTML>
35365 ====== h_config_wp_indexheight =====
35366 <HTML>
35367 <HEAD>
35368 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></TITLE>
35369 </HEAD>
35370 <BODY>
35371 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></H1>
35373 Web Alpine only.
35374 <P>
35375 Index table row height.
35377 <P>
35378 <UL>
35379 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35380 </UL><P>
35381 <End of help on this topic>
35382 </BODY>
35383 </HTML>
35384 ====== h_config_rss_news =====
35385 <HTML>
35386 <HEAD>
35387 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss_news"--></TITLE>
35388 </HEAD>
35389 <BODY>
35390 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-news"--></H1>
35392 Web Alpine only.
35393 <P>
35394 RSS News feed.
35396 <P>
35397 <UL>
35398 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35399 </UL><P>
35400 <End of help on this topic>
35401 </BODY>
35402 </HTML>
35403 ====== h_config_rss_weather =====
35404 <HTML>
35405 <HEAD>
35406 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></TITLE>
35407 </HEAD>
35408 <BODY>
35409 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></H1>
35411 Web Alpine only.
35412 <P>
35413 RSS Weather feed.
35415 <P>
35416 <UL>
35417 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35418 </UL><P>
35419 <End of help on this topic>
35420 </BODY>
35421 </HTML>
35422 ====== h_config_send_confirms_only_expanded =====
35423 <HTML>
35424 <HEAD>
35425 <TITLE>FEATURE: send-confirms-only-expanded</TITLE>
35426 </HEAD>
35427 <BODY>
35428 <H1>FEATURE: send-confirms-only-expanded (Web Alpine Only)</H1>
35430 This Web Alpine option specifies whether or not a Send confirmations
35431 happens when a composed message is readied for sending or not. The
35432 default behavior is to not confirm that the nicknames were expanded to
35433 the intended addresses.
35435 <P>
35436 <UL>
35437 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35438 </UL><P>
35439 <End of help on this topic>
35440 </BODY>
35441 </HTML>
35442 ====== h_config_enable_jump_command =====
35443 <HTML>
35444 <HEAD>
35445 <TITLE>FEATURE: enable-jump-command</TITLE>
35446 </HEAD>
35447 <BODY>
35448 <H1>FEATURE: enable-jump-command (Web Alpine Only)</H1>
35450 This Web Alpine option specifies whether or not a Jump command is
35451 offered in the Message List and Message View pages. The command is
35452 implemented as an input field in the left column of the List and View
35453 screens.
35455 <P>
35456 When enabled and a number is entered in the input field while the
35457 Message List is displayed, the Message List is reframed with the
35458 specified message. While viewing a message, the message associated
35459 with the specified message number is displayed.
35461 <P>
35462 <UL>
35463 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35464 </UL><P>
35465 <End of help on this topic>
35466 </BODY>
35467 </HTML>
35468 ====== h_config_enable_newmail_sound =====
35469 <HTML>
35470 <HEAD>
35471 <TITLE>FEATURE: enable-newmail-sound</TITLE>
35472 </HEAD>
35473 <BODY>
35474 <H1>FEATURE: enable-newmail-sound (Web Alpine Only)</H1>
35476 This Web Alpine option specifies whether or not a sound file is sent
35477 to the web browser along with the newmail notification message.
35480 <P>
35481 <UL>
35482 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35483 </UL><P>
35484 <End of help on this topic>
35485 </BODY>
35486 </HTML>
35487 ====== h_config_render_html_internally =====
35488 <HTML>
35489 <HEAD>
35490 <TITLE>FEATURE: render-html-internally</TITLE>
35491 </HEAD>
35492 <BODY>
35493 <H1>FEATURE: render-html-internally (Web Alpine Only)</H1>
35495 By default, Web Alpine will pass cleansed HTML text you receive in messages
35496 to the browser for display (rendering). This feature causes Web Alpine to convert
35497 the HTML text into plain text in the same way Unix and PC-Alpine do.
35500 <P>
35501 <UL>
35502 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35503 </UL><P>
35504 <End of help on this topic>
35505 </BODY>
35506 </HTML>
35507 ====== h_config_role_undo =====
35508 Yes, remember changes and exit back to list of roles; No, discard changes
35509 made in this screen; ^C, cancel exit and stay in this config screen.
35510 ====== h_exit_editor =====
35511 S, save changes and exit from the editor; D, do not save changes but
35512 do exit from the editor; or ^C, cancel exit and stay in the editor.
35513 ====== h_config_undo =====
35514 Yes, save changes and exit; No, exit without saving any changes made since
35515 entering this CONFIGURATION screen; ^C, cancel exit and stay in config screen.
35516 ====== h_os_index_whereis =====
35517 Enter ^V or ^Y to go immediately to the last or first message in the index.
35518 Or, enter the match string followed by RETURN.
35519 ====== h_os_index_whereis_agg =====
35520 Enter ^V or ^Y to go immediately to the last or first message in the index,
35521 Or, enter the match string followed by RETURN (or ^X to select all matches).
35522 =========== h_oe_add_full ==================
35523 Type the full name of the person being added and press the RETURN key.
35524 Press ^C to cancel addition.
35525 =========== h_oe_add_nick ==================
35526 Type a short nickname and press RETURN. A nickname is a short easy-to-
35527 remember word, name or initials like "joe", or "wcfields." ^C to cancel.
35528 ========== h_oe_add_addr ================
35529 Type the e-mail address and press RETURN.
35530 Press ^C to cancel addition.
35531 ========== h_oe_crlst_full ==============
35532 Type a long name or description for the list that you are creating and
35533 press RETURN. Press ^C to cancel creation of list.
35534 =========== h_oe_crlst_nick =============
35535 Type a nickname (short, easy-to-remember name or single word) for the list
35536 you are creating and press RETURN. Press ^C to cancel.
35537 ========== h_oe_crlst_addr ==============
35538 Type an e-mail address, or a nickname already in the address book that you
35539 want to be part of this list and press RETURN.
35540 ========== h_oe_adlst_addr =============
35541 Type an e-mail address or a nickname already in the address book that you
35542 want to add to this list and press RETURN.
35543 ========== h_oe_editab_nick ============
35544 Change the nickname using the arrow keys and delete key. Press RETURN
35545 when done. Press ^C to cancel editing and leave the nickname as it was.
35546 ========== h_oe_editab_full ============
35547 Change the full name using the arrow keys and delete key. Press RETURN
35548 when done. Press ^C to cancel editing and leave the full name as it was.
35549 ========== h_oe_editab_addr ============
35550 Change the address using the arrow keys and delete key. Press RETURN
35551 when done. Press ^C to cancel editing and leave the address as it was.
35552 ========== h_oe_editab_fcc ============
35553 Change the fcc using the arrow keys and delete key. Press RETURN when
35554 done. Press ^C to cancel editing and leave the fcc as it was.
35555 ========== h_oe_editab_comment ============
35556 Change the comment field using the arrow keys and delete key. Press RETURN
35557 when done. Press ^C to cancel editing and leave the comment as it was.
35558 ====== h_ab_forward =====
35559 Yes, expand nicknames and qualify local names with your current domain name;
35560 No, leave nicknames and local names as is; ^C, cancel.
35561 ========== h_ab_export ==========
35562 Type the name of a file to write the addresses into and
35563 press RETURN. You may also specify an absolute path. Use ^C to cancel.
35564 ========== h_ab_edit_a_field ==========
35565 Edit any of the fields of the currently selected entry by typing one of the
35566 letters at the bottom of the screen. Press ^C to cancel edit.
35567 ====== h_ab_del_data_revert =====
35568 Press B to completely delete addrbook and revert to default, C to delete config
35569 and revert while leaving data, or D to only delete data (make it empty).
35570 ====== h_ab_del_data_modify =====
35571 Press B to completely delete addrbook, C to delete configuration while leaving
35572 data, or D to delete data (make it empty) but leave config. ^C to cancel.
35573 ====== h_ab_del_config_modify =====
35574 Yes, remove this address book from my configuration.
35575 No, make no changes now.
35576 ====== h_ab_del_config_revert =====
35577 Yes, remove this address book from my config and revert to default.
35578 No, make no changes now.
35579 ====== h_ab_del_default =====
35580 Yes, remove this default address book from my configuration.
35581 No, make no changes now.
35582 ====== h_ab_really_delete =====
35583 Yes, delete the actual contents of the address book, not just the
35584 configuration. No, don't delete the data after all, cancel and start over.
35585 ====== h_ab_del_ignore =====
35586 Press I to ignore all the default address books for this category. Press R to
35587 remove this one address book and add the others to your personal list.
35588 ====== h_ab_del_dir_ignore =====
35589 Press I to ignore all the default directory servers for this category.
35590 Press R to remove this one server and add the others to your personal list.
35591 ====== h_ab_copy_dups =====
35592 Yes, overwrite the existing entry.
35593 No, skip duplicates but save the rest. Press ^C to cancel.
35594 ====== h_confirm_cancel =====
35595 Type C to Confirm that you want to abandon the message you are composing.
35596 Type N or ^C to cancel out of the cancel and keep composing.
35597 ====== h_ab_text_or_vcard =====
35598 Text, start composer with displayed text already included.
35599 VCard, start composer with address book entry attached as a vCard. ^C cancels.
35600 ====== h_ab_backup_or_ldap =====
35601 Backup, copy email address from entry and allow editing of it.
35602 LDAP, copy LDAP search criteria, do not allow editing of it. ^C cancels.
35603 ====== h_ldap_text_or_vcard =====
35604 Text: export displayed text for selected entry. Address: export only the
35605 email address. VCard: export entry in vCard format. ^C cancels.
35606 ====== h_ab_save_exp =====
35607 Save, save entry or entries to an address book.
35608 Export, save to file outside of pine. ^C cancels save.
35609 ====== h_ab_add =====
35610 A, add a brand new entry to this address book.
35611 E, edit the entry that is currently highlighted. ^C to cancel.
35612 ====== h_ab_shuf =====
35613 U, swap order of highlighted address book and the one above it.
35614 D, swap order of highlighted address book and the one below it. ^C to cancel.
35615 ====== h_ab_shuf_up =====
35616 U, swap order of highlighted address book and the one above it.
35617 Press ^C to cancel.
35618 ====== h_ab_shuf_down =====
35619 D, swap order of highlighted address book and the one below it.
35620 Press ^C to cancel.
35621 ====== h_folder_prop =====
35622 Count is # of messages in the folder, Unseen means messages that have not
35623 been read, New means messages that were Recently added to the folder.
35624 ====== h_role_shuf =====
35625 U, swap order of highlighted rule and the one above it.
35626 D, swap order of highlighted rule and the one below it. ^C to cancel.
35627 ====== h_role_shuf_up =====
35628 U, swap order of highlighted rule and the one above it.
35629 Press ^C to cancel.
35630 ====== h_role_shuf_down =====
35631 D, swap order of highlighted rule and the one below it.
35632 Press ^C to cancel.
35633 ====== h_incoming_shuf =====
35634 B, swap order of highlighted directory and the one before it.
35635 F, swap order of highlighted directory and the one after it. ^C to cancel.
35636 ====== h_incoming_shuf_up =====
35637 B, swap order of highlighted directory and the one before it.
35638 Press ^C to cancel.
35639 ====== h_incoming_shuf_down =====
35640 F, swap order of highlighted directory and the one after it.
35641 Press ^C to cancel.
35642 ====== h_dir_shuf =====
35643 U, swap order of highlighted directory and the one above it.
35644 D, swap order of highlighted directory and the one below it. ^C to cancel.
35645 ====== h_dir_shuf_up =====
35646 U, swap order of highlighted directory and the one above it.
35647 Press ^C to cancel.
35648 ====== h_dir_shuf_down =====
35649 D, swap order of highlighted directory and the one below it.
35650 Press ^C to cancel.
35651 ====== h_hdrcolor_shuf =====
35652 U, swap order of highlighted Header Color and the one above it.
35653 D, swap order of highlighted Header Color and the one below it. ^C to cancel.
35654 ====== h_hdrcolor_shuf_up =====
35655 U, swap order of highlighted Header Color and the one above it.
35656 Press ^C to cancel.
35657 ====== h_hdrcolor_shuf_down =====
35658 D, swap order of highlighted Header Color and the one below it.
35659 Press ^C to cancel.
35660 ========== h_oe_editab_al ============
35661 Change the address using the arrow keys and delete key. Press RETURN
35662 when done. Press ^C to cancel editing and leave the address as it was.
35663 ========== h_dir_comp_search ===============
35664 Type a string to look for just like you would in the composer. Your configured
35665 rules for the servers with the implicit flag set will be used.
35666 ========== h_oe_searchab ===============
35667 Type the word or name you want to search for and press RETURN. If you press
35668 RETURN without entering anything the word in [] will be searched for.
35669 ========== h_oe_chooseabook ==========
35670 Choose the address book you want to save the new entry in.
35671 Use ^N or ^P to change address books. ^C to cancel.
35672 ========== h_oe_takeaddr ==========
35673 Edit the e-mail address using the arrow and delete keys. Press RETURN
35674 when done. Press ^C to cancel adding this entry to the address book.
35675 ========== h_oe_take_replace ==========
35676 Press R to replace the old entry with this new data. You will still have
35677 another chance to cancel. N to enter another nickname. ^C to cancel now.
35678 ========== h_oe_take_replace_or_add ==========
35679 Press R to replace the old entry. Press A to add the selected addresses to
35680 the old existing list. N to enter another nickname. ^C to cancel now.
35681 ========== h_oe_takename ==========
35682 Edit the full name to be correct using the arrow and delete keys. Press RETURN
35683 when done. Press ^C to cancel adding this entry to the address book.
35684 ========== h_oe_takenick ==========
35685 Type a nickname (short easy-to-remember name, initials or single word) for this
35686 entry in the address book and press RETURN. Press ^C to cancel addition.
35687 ========== h_oe_jump ==========
35688 Type the message number you want to jump to and press RETURN. The word "end"
35689 represents the last message. Press ^C to cancel jumping to another message.
35690 ========== h_oe_jump_thd ==========
35691 Type the thread number you want to jump to and press RETURN. The word "end"
35692 represents the last thread. Press ^C to cancel jumping to another thread.
35693 ========== h_oe_debuglevel ==========
35694 Higher number shows more debugging details.
35695 Press ^C if you want to cancel the change.
35696 ========== h_oe_broach ==========
35697 Type the name of the folder you want to open and press RETURN. Press ^P/^N
35698 to go to the previous/next collections in the list. Press ^C to cancel goto.
35699 ========== h_oe_foldsearch ==========
35700 Type the text you want to search for in foldernames and press RETURN. If you
35701 press RETURN without entering anything, any text in [] will be searched for.
35702 ========== h_oe_foldrename ==========
35703 Change the old name of the folder to the new name using the arrow and
35704 delete keys and press RETURN. Press ^C to cancel rename.
35705 ========== h_oe_login ==========
35706 Enter your login name for the host you are opening the mailbox on. Just press
35707 RETURN to use your login from this host as is, or edit it with delete key.
35708 ========== h_oe_passwd ==========
35709 Type your password for the host and login shown as part of the prompt.
35710 Press ^C to cancel opening folder.
35711 ========== h_oe_choosep ==========
35712 Enter the number associated with the printer you want to select. Press ^C to
35713 cancel the printer selection. The current selection is highlighted.
35714 ========== h_oe_customp ==========
35715 Type the name of the Unix print command and press RETURN. Press ^C to
35716 cancel the printer selection.
35717 ========== h_oe_searchview ==========
35718 Type the word or name you want to search for and press RETURN. If you press
35719 RETURN without entering anything the word in [] will be searched for.
35720 ========== h_oe_keylock ==========
35721 The keyboard is in use and locked by another user. Only that user can
35722 unlock this keyboard by typing the password.
35723 ========== h_wt_expire ==========
35724 At the beginning of each month Alpine offers to rename your current sent-mail
35725 folder to one named for the month so you have a sent-mail folder for each month
35726 ========== h_wt_delete_old ==========
35727 It is the beginning of the month, and we need to conserve disk
35728 space. Please delete any sent-mail that you do not need.
35729 ========== h_select_sort ==========
35730 Select the order for sorting the index by typing the capitalized letter.
35731 Arrival is by arrival in your mailbox; Date is by time/day message was sent.
35732 ========== h_no_F_arg ============
35733 Enter name of file to be opened.
35735 ========== h_sticky_personal_name ==========
35736 Type in your name as you want it to appear on outgoing email. This entry
35737 will be saved into your Alpine configuration file.
35738 ========== h_sticky_inbox ============
35739 INBOX syntax is usually {complete.machine.name}INBOX
35740 This entry will be saved in your Alpine configuration file.
35741 ========== h_sticky_smtp ============
35742 The name of the computer on your campus that relays your outgoing email
35743 to the Internet. This entry will be saved in your Alpine configuration file.
35744 ========== h_sticky_user_id ==========
35745 The username or login-id part of your email address. This entry will be
35746 saved in your Alpine configuration file.
35747 ========== h_sticky_domain ==========
35748 The domain part of your email address, NOT the name of your PC. This
35749 entry will be saved in your Alpine configuration file.
35750 ========== h_bounce =========
35751 Enter the address or nickname of the intended recipient. Alpine will resend
35752 the message, which will retain the original author's From: address.
35753 ========== h_incoming_add_folder_nickname =========
35754 Enter an (optional) nickname that will be used in lieu of the actual
35755 host and folder names in the FOLDER LIST display.
35756 ========== h_anon_forward ==========
35757 Enter the address of your intended recipient, or ^C to cancel.
35758 Example: jsmith@somewhere.edu
35759 ========== h_news_subscribe ==========
35760 Enter the name of the newsgroup to which you wish to subscribe,
35761 or ^C to cancel. Example: comp.mail.pine
35762 ========== h_pipe_msg ==========
35763 Enter the name of the Unix command to which you wish to send this
35764 message, or ^C to cancel.
35765 ========== h_pipe_attach ==========
35766 Enter the name of the Unix command to which you wish to send this
35767 attachment, or ^C to cancel.
35768 ========== h_select_by_num ==========
35769 Enter a list of message numbers (or number ranges), or ^C to cancel. The word
35770 "end" represents the last message. Example: 2-5,7-9,11,19,35-end
35771 ========== h_select_by_thrdnum ==========
35772 Enter a list of thread numbers (or number ranges), or ^C to cancel. The word
35773 "end" represents the last thread. Example: 2-5,7-9,11,19,35-end
35774 ========== h_select_txt_from ==========
35775 Messages with From: headers containing the entered string will be selected.
35776 ^C to cancel. ^G again to see original options.
35777 ========== h_select_txt_not_from ==========
35778 Messages without From: headers containing the entered string will be selected.
35779 ^C to cancel. ^G again to see original options.
35780 ========== h_select_txt_to ==========
35781 Messages with To: headers containing the entered string will be selected.
35782 ^C to cancel. ^G again to see original options.
35783 ========== h_select_txt_not_to ==========
35784 Messages without To: headers containing the entered string will be selected.
35785 ^C to cancel. ^G again to see original options.
35786 ========== h_select_txt_cc ==========
35787 Messages with Cc: headers containing the entered string will be selected.
35788 ^C to cancel. ^G again to see original options.
35789 ========== h_select_txt_not_cc ==========
35790 Messages without Cc: headers containing the entered string will be selected.
35791 ^C to cancel. ^G again to see original options.
35792 ========== h_select_txt_subj ==========
35793 Messages with Subject: headers containing the entered string will be selected.
35794 ^C to cancel. ^X enters Subject: line of current message.
35795 ========== h_select_txt_not_subj ==========
35796 Messages without Subject headers containing the entered string will be selected.
35797 ^C to cancel. ^X enters Subject: line of current message.
35798 ========== h_select_txt_all ==========
35799 All messages containing the entered string will be selected. Headers and body,
35800 but not encoded attachments, will be compared. Enter ^C to cancel.
35801 ========== h_select_txt_not_all ==========
35802 All messages that don't contain the entered string will be selected. Headers
35803 and body, but not encoded attachments, will be compared. Enter ^C to cancel.
35804 ========== h_select_txt_body ==========
35805 All messages containing the entered string will be selected. Body text, but
35806 not headers or encoded attachments, will be compared. ^C to cancel.
35807 ========== h_select_txt_not_body ==========
35808 All messages that don't contain the entered string will be selected. Body
35809 text, but not headers or encoded attachments, will be compared. ^C to cancel.
35810 ========== h_select_txt_recip ==========
35811 Messages with Cc: or To: headers containing the entered string will be selected.
35812 ^C to cancel. ^G again to see original options.
35813 ========== h_select_txt_not_recip ==========
35814 Messages without Cc: or To: headers containing the string will be selected.
35815 ^C to cancel. ^G again to see original options.
35816 ========== h_select_txt_partic ==========
35817 Messages with Cc, To, or From headers containing the string will be selected.
35818 ^C to cancel. ^G again to see original options.
35819 ========== h_select_txt_not_partic ==========
35820 Messages without Cc, To, or From headers containing the string will be selected.
35821 ^C to cancel. ^G again to see original options.
35822 ========== h_select_date ==========
35823 If typed, date may be in DD-MMM-YYYY format (04-Jul-2006) or in ISO format
35824 (2006-07-04). ^P/^N also changes default date. ^X enters date of current msg.
35825 ========== h_attach_index_whereis ==========
35826 Enter some text that appears in the Attachment Index entry for the desired
35827 attachment. The first attachment containing that text will be highlighted.
35828 ========== h_kb_lock ==========
35829 Keystrokes entered here (up to a RETURN) comprise a password that must
35830 be entered again later in order to unlock the keyboard.
35831 ========== h_compose_default ==========
35832 N, compose a new message. R, set a role.
35833 ^C to cancel.
35834 ========== h_untranslatable ==========
35835 Send using UTF-8 character set; Send but replace untranslatable characters
35836 with question marks; return to the composer; or cancel message altogether.
35837 ========== h_compose_intrptd ==========
35838 N, compose a new msg. I, continue interrupted msg. R, set a role.
35839 ^C to cancel.
35840 ========== h_compose_postponed ==========
35841 N, compose a new message. P, continue postponed msg. R, set a role.
35842 ^C to cancel.
35843 ========== h_compose_intrptd_postponed ==========
35844 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
35845 R, set a role. ^C to cancel.
35846 ========== h_compose_form ==========
35847 N, compose a new message. F, use form letter. R, set a role.
35848 ^C to cancel.
35849 ========== h_compose_intrptd_form ==========
35850 N, compose a new msg. I, continue interrupted msg. F, use form letter.
35851 R, set a role. ^C to cancel.
35852 ========== h_compose_postponed_form ==========
35853 N, compose a new message. P, continue postponed msg. F, use form letter.
35854 R, set a role. ^C to cancel.
35855 ========== h_compose_intrptd_postponed_form ==========
35856 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
35857 F, use form letter. R, set a role. ^C to cancel.
35858 ========== h_config_context_del_except ==========
35859 If you delete the last exceptional collection you can only add it back by
35860 manually editing the exceptions config file.
35861 ========== h_config_whereis ==========
35862 To move quickly to a particular line, enter a search string or
35863 ^C to cancel.
35864 ========== h_config_edit_scorei ==========
35865 Enter interval in the form (min,max). -INF and INF may be used to represent
35866 -infinity and infinity. ^C to cancel change. RETURN to accept change.
35867 ========== h_config_add ==========
35868 Enter desired value; use normal editing keys to modify (e.g. ^K, ^D). Just
35869 pressing RETURN sets the Empty Value (this turns off any global default).
35870 ========== h_config_add_custom_color ==========
35871 Enter a header fieldname. For example, "subject" or "from".
35873 ========== h_config_add_pat_hdr ==========
35874 Enter a header fieldname. For example, "reply-to" or "organization" or
35875 any fieldname you want that isn't included already.
35876 ========== h_config_print_opt_choice ==========
35877 You may edit either the initialization string (characters printed before
35878 printing starts) or the trailer string. Choose one or ^C to cancel.
35879 ========== h_config_print_init ==========
35880 Enter a C-style string for this. You may use common backslash escapes like
35881 \\n for newline, \\ooo for octal character, and \\xhh for hex character.
35882 ========== h_config_change ==========
35883 Edit the existing value using arrow keys, ^K to delete entire entry, ^D to
35884 delete current (highlighted) character, etc. Enter ^C to cancel change.
35885 ========== h_config_replace_add ==========
35886 Replace ignores the current default, Add places the current default in your
35887 editing buffer as if you had typed it in.
35888 ========== h_config_insert_after ==========
35889 Enter a nickname for this print command. (InsertBefore puts the new item
35890 before the current line, InsertAfter puts it after the current line.)
35891 ========== h_config_print_cmd ==========
35892 Enter command to be executed for the printer. Use normal editing keys
35893 to modify, ^C to cancel, carriage return to accept current value.
35894 ========== h_config_role_del ==========
35895 Answering Yes will remove this rule completely from your rules list.
35896 ========== h_config_role_addfile ==========
35897 Type the name of a file to add to your configuration. You don't need to
35898 use a file, you may add rules directly (with Add) without using a file.
35899 ========== h_config_role_delfile ==========
35900 Answering Yes will remove this rule file completely from your rules list.
35901 The rules data file itself will not be removed.
35902 ========== h_config_print_del ==========
35903 Answering Yes will remove this printer completely from your printer list.
35904 ========== h_config_print_name_cmd ==========
35905 You may edit the Nickname of this printer, the Command to be executed when
35906 printing, or change the Options associated with this printer.
35907 ========== h_send_check_fcc ==========
35908 Yes, send message without an Fcc.
35909 No, return to composer.
35910 ========== h_send_check_subj ==========
35911 Yes, send message without a Subject.
35912 No, return to composer.
35913 ========== h_send_check_to_cc ==========
35914 Yes, send message without a To address, or a Cc address, or a Newsgroup.
35915 No, return to composer.
35916 ========== h_send_fcc_only ==========
35917 Yes, copy message to Fcc only and send to NO recipients.
35918 No, return to composer.
35919 ========== h_send_prompt ==========
35920 Yes, send the message.
35921 No or ^C, return to composer.
35922 ========== h_send_prompt_flowed ==========
35923 Yes, send the message. No or ^C, return to composer.
35924 What's Flowed? See Do Not Send Flowed Text in config screen.
35925 ========== h_send_prompt_dsn ==========
35926 Yes, send the message. No or ^C, return to composer.
35927 What's DSNOpts? See Enable Delivery Status Notification in config screen.
35928 ========== h_send_prompt_dsn_flowed ==========
35929 Yes, send the message. No or ^C, return to composer. What's DSNOpts? See
35930 Enable Delivery Status Notification. What's Flowed? See Do Not Send Flowed Text.
35931 ========== h_role_confirm ==========
35932 Yes, use displayed role. No, compose without a role.
35933 ^C, cancel the message. ^T, select a role from your other eligible roles.
35934 ========== h_norole_confirm ==========
35935 Return, compose without a role.
35936 ^C, cancel the message. ^T, select a role from your eligible roles.
35937 ========== h_custom_print ==========
35938 Enter a Unix command that accepts its data on standard input.
35939 Alpine will display any information the command sends to standard output.
35940 ========== h_convert_abooks_and_sigs ==========
35941 You will be given the opportunity to convert address books and signature files
35942 to remote configurations.
35943 ========== h_convert_abooks ==========
35944 You will be given the opportunity to convert address books to remote
35945 configurations.
35946 ========== h_flag_keyword ==========
35947 Enter the name of the keyword you want to add for this folder.
35948 No spaces, parentheses, braces, percents or asterisks are allowed.
35949 ========== h_select_keyword ==========
35950 Enter the keyword you want to match, or use ^T to select a keyword from a list
35951 of possible keywords for this folder. Use ! to look for non-matches instead.
35952 ========== h_type_keyword ==========
35953 Enter the keyword you want to add. You may add a nickname in the next step.
35954 No spaces, parentheses, braces, percents or asterisks are allowed.
35955 ========== h_type_keyword_nickname ==========
35956 Enter an optional nickname for the keyword you want to add.
35957 Type Carriage return to use the keyword name instead of a nickname.
35958 ========== h_convert_sigs ==========
35959 You will be given the opportunity to convert signature files to remote
35960 configurations.
35961 ========== h_convert_abook ==========
35962 Yes is fairly safe. You will be ADDing a remote address book that is a copy
35963 of the current address book. The current abook won't be removed automatically.
35964 ========== h_convert_sig ==========
35965 Answering Yes copies the contents of the signature file into your Alpine
35966 configuration file. After that, the contents of the file will not be used.
35967 ========== h_save_addman ==========
35968 Enter the simple name of the folder you want to add. Carriage return to
35969 accept what you have typed so far. ^C to get back to SELECT FOLDER screen.
35970 ========== h_reopen_folder ==========
35971 Yes reopens the folder, as if you were starting over. This uncovers new mail.
35972 No leaves the folder index as it was without discovering new mail.
35973 ========== h_convert_pinerc_server ==========
35974 This is the name of the host (computer) where the remote Alpine configuration
35975 will be stored. This should be an IMAP server that you have permission to use.
35976 ========== h_convert_pinerc_folder ==========
35977 Enter the correct remote folder name. This folder is special and should
35978 contain only configuration data. It shouldn't contain other mail messages.
35979 ========== h_role_compose ==========
35980 Compose a New message, Reply to current message, Forward current message, or
35981 Bounce message. Then you will be asked to choose one of your Roles to be used.
35982 ========== h_save_size_changed ==========
35983 The reported size of a message is not the same as the actual size. Answer Yes
35984 to continue and hope for the best or No to Cancel the entire Save.
35985 ========== h_select_by_larger_size ==========
35986 Enter a number or ^C to cancel. All messages greater than this many characters
35987 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
35988 ========== h_select_by_smaller_size ==========
35989 Enter a number or ^C to cancel. All messages less than this many characters
35990 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
35991 ========== h_preserve_field ==========
35992 Use 'p' to toggle between preserving or not preserving the original To:
35993 and Cc: fields of the message. Enter ^C to cancel message.