# $Id: pine.hlp,v 4.443 1999/02/04 23:06:40 hubert Exp $
#
#           T H E   P I N E    M E S S A G E   S Y S T E M
#
#   Laurence Lundblade, Mike Seibel, Mark Crispin, Steve Hubert,
#      Sheryl Erez, David Miller, Stefan Kramer
#   Networks & Distributed Computing
#   Computing & Communications
#   University of Washington
#   Administration Building, Box 351208
#   Seattle, Washington, 98195, USA
#
#   Email: pine@cac.washington.edu
#
#   Pine and Pico are trademarks of the University of Washington.
#   Pine, Pico and Pilot Copyright 1989-1999  University of Washington
#
#   Additional legal notices are in the Release Notes below or
#   at http://www.washington.edu/pine/legal.html
#
#   Pine was originally based in part on The Elm Mail System:
#
#    ***********************************************************************
#    *       The Elm Mail System  -  Revision: 2.13                        *
#    *                                                                     *
#    *       Copyright (c) 1986, 1987 Dave Taylor                          *
#    *       Copyright (c) 1988, 1989 USENET Community Trust               *
#    ***********************************************************************
#
#
         Help text for the Pine mailer

This file is in a format created to be turned into text strings in a C
program.

NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE

     If you are familiar with versions of this file PRIOR to 
     Pine 4.00 forget what you know.  No more '{' sensitivity.
     No more escaping double-quote character.

NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE-NOTE

There are two shell scripts that run on this.  Cmplhelp.sh is the
first and turns this into a C file (helptext.c) of text strings that
are compiled and linked. The other program, cmplhlp2.sh, turns this
into a .h file (helptext.h) with extern string definitions of the
strings in the .c file.  The code that actually processes these files
while pine is running is in help.c

The lines with "===== xxxx ====" divide the different help screens.  The
xxx is the name of the variable that strings will be put in, which are
also declared in helptext.h.

# is a comment

Help text screen text can be either plain text OR HTML.  The latter is
denoted by the first line starting with "<HTML>".  The former is simply
displayed as it's formatted here.

HTML is limited to simple formatting ala HTML 2.0.  No forms, or tables.
In addition a small set of tools are are available to customize the HTML
screen's text:

1a)  Default and function key bindings are separated like this:

<!--chtml if pinemode="function_key"-->
	Function key bindings here
<!--chtml else-->
	Default key bindings here
<!--chtml endif-->


1b)  A way to distinguish HTML text that is to be displayed when
     pine is running vs. when the text is served up outside Pine
     (someday) can be done via:

<!--chtml if pinemode="running"-->
   Text displayed when viewed within a running pine session
<!--chtml else-->
   Text displayed when HTML viewed outside pine (using chtml aware server)
<!--chtml endif-->

1c)  A way to distinguish HTML text that is to be displayed under
     PC-Pine vs. not is available via:

<!--chtml if pinemode="os_windows"-->
   Text displayed under PC-Pine
<!--chtml else-->
   Text displayed otherwise
<!--chtml endif-->

WARNING ABOUT CHTML "if-else-endif" CLAUSES: They don't nest.

2a) Several "server side include" commented elements are supported:

<!--#include file="textfile"--> 

The file "textfile" will be inserted into the HTML text directly.
Pine does no formatting of the text.  At some point we might want to
look at the first line for <HTML> but not today.

2b) Various bits of Pine's running state can be inserted into the
HTML text as well using the special comment:

<!--#echo var="variable"--> 

Where "variable" is one of either:

    PINE_VERSION
    PINE_COMPILE_DATE
    PINE_TODAYS_DATE
    _LOCAL_FULLNAME_
    _LOCAL_ADDRESS_
    _BUGS_FULLNAME_
    _BUGS_ADDRESS_
    CURRENT_DIR
    HOME_DIR

3) The URL scheme "X-Pine-Gripe:" is available to insert links to
   pine's composer such that various debugging data can be attached to the
   message. Aside from normal email addresses, this can be set to
   either "_LOCAL_ADDRESS_" for the configured local help address, or
   "_BUGS_ADDRESS_" for the configured local bug reporting address.
   Aside from the special tokens above, the default behavior only differs
   from "mailto:" by the insertion of a special Subject: prefix that
   consists of a randomly-generated token for tracking purposes.
   Several optional parameters can be included to control what is
   attached or offered for attachment to the message:

        ?config  --  Automatically attaches the user's configuration
                     information to the trouble report
        ?keys    --  Automatically attaches the user's most recent
                     keystrokes
        ?curmsg  --  Causes the user to get an offer to attach the
                     current message to the trouble report
        ?local   --  Automatically attaches the result of the script 
                     defined by VAR_BUGS_EXTRAS

For HTML-format sections, the help screen dividers  "===== xxxx ====" must 
contain one and only one space after the first and before the second set of 
equal signs.

Note to authors of this file: to mark sections that need further revision, 
please use the text string on the following line consistently so that it is 
easy to find those places again in this file:
*revision needed*

NOTE: Several sections of help text which weren't being used were removed
at RCS version number 4.122.  In particular, there were some placeholders
with help text for the config screen and the composer that didn't have any
reasonable place to be called from.

============= h_news =================
<HTML>
<HEAD>
<TITLE>RELEASE NOTES for Pine</TITLE>
</HEAD>
<BODY>                 
<H1>Pine Release Notes</H1>
<CENTER>Version <!--#echo var="PINE_VERSION"-->
<!--chtml if pinemode="running"-->
(built <!--#echo var=PINE_COMPILE_DATE-->)
<!--chtml endif-->
<BR>University of Washington</CENTER><P>

<P>
Pine&reg; is the University of Washington's &quot;Program for Internet
News and Email&quot;. It is intended to be an easy-to-use program for
sending, receiving, and filing Internet electronic mail messages and
bulletin board (Netnews) messages.  There are versions that will run on
many different flavors of the Unix&reg; operating system, as well as a
version with GUI amenities for 32-bit flavors of Microsoft Windows (95,
98, and NT).


<H2>New in Pine <!--#echo var="PINE_VERSION"--></H2>

Version <!--#echo var="PINE_VERSION"--> is an evolutionary release
that introduces both
new functionality as well as addresses several bugs found in earlier
releases.  Changes include:
<P>
<UL>
 <LI> New &quot;<A HREF="h_role_config">Roles</A>&quot; concept
 <LI> New features to enable &quot;combined&quot; list of 
<A HREF="h_config_combined_folder_display">folders</A> and 
<A HREF="h_config_combined_abook_display">address books</A>
similar to the screens found in Pine versions prior to 4.00.
 <LI> Restoration of 
<A HREF="h_config_expanded_folders">expanded-view-of-folders</A> and
<A HREF="h_config_expanded_addrbooks">addressbooks</A> when
&quot;combined list&quot; features enabled
 <LI> New send feature to <A HREF="h_config_no_fcc_attach">fcc-without-attachments</A>
 <LI> Setup/Config: features now grouped by topic
 <LI> New option to pass headers to sending filters
 <LI> Configurable <A HREF="h_config_reply_intro">Reply-Leadin</A>
to included message text
 <LI> New feature to use <A HREF="h_config_textplain_int">internal pager</A> for text attachments
 <LI> New feature to allow selection/mailto of <A HREF="h_config_enable_view_addresses">embedded email</A> addresses
 <LI> Expanded signature file options: a filename followed by &quot;|&quot; means use named program's output
 <LI> Expanded <A HREF="h_index_tokens">token support</A> permitted in signature
 and role template files as well as the new Reply-Leadin definition
 <LI> Compile-time option to permit saving passwords for Unix Pine
 <LI> Help Text improvements
 <LI> Numerous bug fixes
</UL>

<P>
Additional details on changes in this (and previous) versions of Pine
may be found at the following URL:
<P>
<CENTER><SAMP><A HREF="http://www.washington.edu/pine/changes.html">http://www.washington.edu/pine/changes.html</A></SAMP></CENTER>
<P>

<HR WIDTH="75%"><P>

<H2>Getting Help</H2>
<DL>
<DT>Online Help</DT>
<DD>
Every Pine screen and command has associated help text
accesseible via the &quot;?&quot; key (or Control-G in text-input contexts).
</DD>

<DT>Web Help</DT>
<DD>
The most current source of information about Pine,
including new version availability, is the web page at
<P>
<CENTER><SAMP><A HREF="http://www.washington.edu/pine/">http://www.washington.edu/pine/</A></SAMP></CENTER>
</DD>
</DL>

Frequently Asked Questions (and answers) may be found at the following
URL:
<P>
<CENTER><SAMP><A HREF="http://www.washington.edu/pine/faq/">http://www.washington.edu/pine/faq/</A></SAMP></CENTER>
<P>
Some topics of current interest include:
<UL>
<P><LI> Information on <A HREF="h_info_on_locking">Folder Locking</A>
<P><LI> Information on <A HREF="h_info_on_mbox">Missing mail and the mbox driver</A>
<P><LI> Information on <A HREF="h_composer_cntxt_path">Folder Namespaces</A>
<P>
</UL>

<HR WIDTH="75%"><P>

<H2>Additional Information</H2>

General Pine configuration information can be found
<A HREF="h_news_config">here</A>.
<P>
Pine is also avilable for Windows 32-bit environments.  More information
on PC-Pine can be found <A HREF="h_news_pcpine">here</A>.
<P>
<P> 
Pine was developed by the Office of Computing &amp; Communications at
the University of Washington in Seattle.  A more complete list of
principal players and key contributors can be found on the credits Web
page at

<P>
<CENTER><A HREF="http://www.washington.edu/pine/credits.html">http://www.washington.edu/pine/credits</A></CENTER>

<P>
Pine and Pico are trademarks of the University of Washington.

<P>
Pine, Pico and Pilot Copyright 1989-1999 University of Washington

<P>
Additional legal notices can be found <A HREF="h_news_legal">here</A>
or at the web URL:

<P>
<CENTER><A HREF="http://www.washington.edu/pine/legal.html">http://www.washington.edu/pine/legal</A></CENTER>

<P>
&lt;End of Release Notes&gt;
</BODY>
</HTML>
====== h_news_pcpine ======
<HTML>
<HEAD>
<TITLE>PC-Pine Notes</TITLE>
</HEAD>
<BODY>
<H1>PC-Pine Notes</H1>

PC-Pine <!--#echo var="PINE_VERSION"--> is available for 32-bit
Windows only.  While it is not a full GUI Windows
application, it supports numerous GUI amenities, including:
tool bar, scroll bar, pull-down menus, pop-up menus,
expanded mouse support, etc.
<P>
<B>New in PC-Pine 4.00:</B>
<P>
<UL>
 <LI>Built-in LDAP directory service support.
<P>
 <LI>Remote addressbook support.  The addressbook can be stored on an
IMAP server, so it can be accessed from different computers running
Unix Pine or PC-Pine <!--#echo var="PINE_VERSION"-->.  See Setup/AddressBooks screen for more details.
<P>
 <LI>POP support (though not in traditional offline mode).
<P>
 <LI>Built-in spell checking.
<P>
 <LI>Integration with Windows registry simplifies configuration
for attachment viewing and sending.
<P>
 <LI>Full READ-WRITE access to local Unix-style folders.
<P>
<H2>Problems with INBOX CLOSED DUE TO ACCESS ERROR messages</H2>

We have recently discovered that a combination of bugs in TCP/IP
implementations can lead to these errors.  In particular, a problem
with Microsoft's WINSOCK used by PC-Pine and a different problem with
many Unix TCP implementations affecting IMAP server behavior may lead to
this error.  A workaround is to change the mail-check-interval in the
pinerc file on your PC from the default value of 150 seconds to 50
seconds.
<P>
</UL>
Additional notes:
<P>
<UL>
<LI>
While message folders may be either local or remote, Pine's support
files must, generally speaking, be located on your PC's local disk.
These files include Pine's configuration file (PINERC), signature file
(PINE.SIG), interrupted message folder, and debug files.  Two files that 
are by default also located on your PC's local disk <B>may</B> be instead 
located on a remote host:
<OL>
 <LI>  The postponed messages folder can be <A
 HREF="h_config_postponed_folder">defined in the Setup/Config</A> to be
 on an IMAP server.  This allows it to be accessible from both Unix
 Pine and PC-Pine thus allowing you to, for example, begin composing a
 message in Unix Pine, postpone it, and resume its composition later
 with PC-Pine, provided that <B>both</B> Pine configurations specify the
 <B>same</B> postponed messages folder location.  For example:
 <P>
 <CENTER><SAMP>{myIMAPhost.myschool.k12.wa.us}mail/postponed</SAMP></CENTER>

 <LI>It's also possible, depending on your local system configuration, to
 arrange remote access to your NEWSRC as well.  The advantage, as with
 the postponed message folder, is that both Unix Pine and PC-Pine can
 refer to the same information. See the Main Menu's help text section on
 "<A HREF="main_menu_tx#read_news">Reading News</A>"
 for more information.
</OL>

<P>
<LI> The PC-Pine message folder format is based on byte-counts for maximum
 efficiency, so they must not be edited. The format is non-standard, but
 conversion utilities would not be difficult. This format is supported in
 Unix Pine as well.

</UL>

<P>
&lt;End of PC-Pine Notes&gt;
</BODY>
</HTML>
====== h_news_config ======
<HTML>
<HEAD>
<TITLE>Pine Configuration</TITLE>
</HEAD>
<BODY>
<H1>Pine Configuration</H1>

<H2>Configuration precedence</H2>

There are several levels of Pine configuration.  Configuration values at
a given level override corresponding values at lower levels.  In order of
increasing precedence:
<P>
<UL>
 <LI> built-in defaults
 <LI> system-wide
<!--chtml if pinemode="os_windows"-->
      config file from command line or provided
      by "PINECONF" environment variable
<!--chtml else-->
      pine.conf file
<!--chtml endif-->
 <LI> personal 
<!--chtml if pinemode="os_windows"-->
      PINERC
<!--chtml else-->
      .pinerc
<!--chtml endif-->
      file (may be set via built-in Setup/Config menu.)
 <LI> command-line options
 <!--chtml if pinemode="os_windows"--><!--chtml else-->
 <LI> system-wide pine.conf.fixed file<!--chtml endif-->
</UL>
<P>
There is one exception to the rule that configuration values are replaced
by the value of the same option in a higher-precedence file:
the feature-list variable has values that are additive, but can be
negated by prepending &quot;no-&quot; in front of an individual feature name.
Note, this is done automatically for you when you change these values via
the Setup/Config command.

<H2>File name defaults</H2>

Notes:<P>

<BR> &lt;exe dir&gt; = directory where pine.exe found.
<BR> &lt;pinerc dir&gt; = directory where pinerc found.
<BR> # = default file name is overridable in pinerc.
<BR> $HOME, if not explicitly set, defaults to root of the current drive.
<BR> $MAILCAPS, if set, is used in lieu of the default mailcap search paths.
<BR> + between the mailcap paths implies that the two files are combined.
<BR> ; between other default paths implies that the first one found is used.
</P>
Pine looks for most support files in the same directory it finds its
personal configuration file (pinerc).  The -p command-line flag may be
used to specify a particular path name for the pinerc file.  If a
pinerc file does not exist, it will be created (if directory permissions
allow).  In PC-Pine, if -p or $PINERC are not defined, Pine will look
in $HOME&#92;PINE and the directory containing the PINE.EXE.  If a PINERC
file does not exist in either one, it will create one in the first of those
two directories that is writable.  In detail:
<PRE>

PC-Pine:

 executable     &lt;DOS search path&gt;&#92;pine.exe
 help index     &lt;exe dir&gt;&#92;pine.ndx
 help text      &lt;exe dir&gt;&#92;pine.hlp

 pers config    $PINERC  ;  $HOME&#92;pine&#92;pinerc  ;  &lt;exe dir&gt;&#92;pinerc
 global cfg     $PINECONF

 password       &lt;pinerc dir&gt;&#92;pine.pwd
 debug          &lt;pinerc dir&gt;&#92;pinedebg.txt
 crash          &lt;pinerc dir&gt;&#92;pinecrsh.txt
 signature#     &lt;pinerc dir&gt;&#92;pine.sig
 addressbook#   &lt;pinerc dir&gt;&#92;addrbook
 addrbook lu    &lt;pinerc dir&gt;&#92;addrbook.lu    (appends .lu to addrbk name.)
 mailcap#       &lt;pinerc dir&gt;&#92;mailcap  +  &lt;exe dir&gt;&#92;mailcap
 mimetypes#     &lt;pinerc dir&gt;&#92;mimetype +  &lt;exe dir&gt;&#92;mimetype
 newsrc#        $HOME&#92;newsrc (if exists, else) &lt;pinerc dir&gt;&#92;newsrc
 sentmail#      $HOME&#92;mail&#92;sentmail.mtx
 postponed#     $HOME&#92;mail&#92;postpond.mtx
 interrupted    $HOME&#92;mail&#92;intruptd

Unix Pine:

 executable     &lt;Unix search path&gt;/pine
 persnl cfg     ~/.pinerc
 global cfg     /usr/local/lib/pine.conf
 fixed cfg      /usr/local/lib/pine.conf.fixed
 local help     /usr/local/lib/pine.info

 interrupted    ~/.pine-interrupted-mail
 debug          ~/.pine-debugN
 crash		~/.pine-crash
 newsrc#        ~/.newsrc
 signature#     &lt;pinerc dir&gt;/.signature
 addressbook#   &lt;pinerc dir&gt;/.addressbook
 addrbook lu    &lt;pinerc dir&gt;/.addressbook.lu  (appends .lu to addrbk name.)
 postponed#     ~/mail/postponed-msgs
 sentmail#      ~/mail/sent-mail
 mailcap#       ~/.mailcap + /etc/mailcap
                           + /usr/etc/mailcap + /usr/local/etc/mailcap
 mimetypes#     ~/.mime.types + /etc/mime.types + /usr/local/lib/mime.types

 news-spool	varies across Unix flavors, e.g. /usr/spool/news or /var/news
 active-news	varies across Unix flavors, e.g. /usr/lib/news/active
 lock files     /tmp/.&#92;usr&#92;spool&#92;mail&#92;xxxx
 inbox          /usr/spool/mail/xxxx
 password       /etc/passwd

Unix Pine and PC-Pine:

 .ab*           remote addressbook support files
 a[1-9]*        temporary (while Pine is running) addressbook files

</PRE>

<H2>Mailcap files</H2>

Pine honors the mailcap configuration system for specifying external
programs for handling attachments.  The mailcap file maps MIME attachment
types to the external programs loaded on your system which can display
and/or print the file.  A sample mailcap file comes bundled with the Pine
distribution.  It includes comments which explain the syntax you need to
use for mailcap.  With the mailcap file, any program (mail readers,
newsreaders, WWW clients) can use the same configuration for handling
MIME-encoded data.

<H2>MIME-Types files</H2>

Pine uses mime-types files (.mime.types or MIMETYPE) to determine
what Content-Type to use for labeling an attached file, based on
the file extension.  That is, this file provides a mapping between
filename extensions and MIME content-types.

<H2>Environment variables</H2>

PC-Pine uses the following environment variables:
<DL>
<DT>PINERC</DT>
<DD>Optional path to pinerc file.</DD>
<DT>PINECONF</DT>
<DD>Optional path to global pine config file.</DD>
<DT>HOME</DT>
<DT>TMP or TEMP</DT>
<DT>COMSPEC</DT>
<DT>MAILCAPS</DT>
<DD>A <B>semicolon</B> delimited list of path names to mailcap files.</DD>
<DT>USER_DICTIONARY</DT>
<DD>Used to specify the file to contain the user's spell check
dictionary.  The default is <SAMP>DICT.U</SAMP> in the same
directory as the <SAMP>SPELL32.DLL</SAMP></DD>
</DL>

Unix Pine uses the following environment variables:
<DL>
<DT>TERM</DT>
<DD>Tells Pine what kind of terminal is being used.</DD>
<DT>DISPLAY</DT>
<DD>Determines if Pine will try to display IMAGE attachments.</DD>
<DT>SHELL</DT>
<DD>If not set, default is &quot;/bin/sh&quot;.</DD>
<DT>MAILCAPS</DT>
<DD>A <B>colon</B> delimited list of path names to mailcap files.</DD>
</DL>

<P>
&lt;End of Configuration Notes&gt;
</BODY>
</HTML>
====== h_news_legal ======
<html>
<head>
<TITLE>Pine Legal Notices</TITLE>
</head>
<body>

<H1>Pine Legal Notices</H1>

Pine and Pico are registered trademarks of the University of Washington.
No commercial use of these trademarks may be made without prior written
permission of the University of Washington.
<P>
Pine, Pico, and Pilot software and its included text are Copyright
1989-1999 by the University of Washington. 
<P>
Use of Pine/Pico/Pilot:  You may compile and execute these programs for
any purpose, including commercial, without paying anything to the
University of Washington, provided that the legal notices are maintained
intact and honored.
<P>
Local modification of this release is permitted as follows, or by mutual
agreement: In order to reduce confusion and facilitate debugging, we
request that locally modified versions be denoted by appending the letter
&quot;L&quot; to the current version number, and that the local changes be
enumerated in the integral release notes and associated documentation.
<P>
Redistribution of this release is permitted as follows, or by mutual
agreement:<BR>
 (a) In free-of-charge or at-cost distributions by non-profit concerns;<BR>
 (b) In free-of-charge distributions by for-profit concerns;<BR>
 (c) Inclusion in a CD-ROM collection of free-of-charge, shareware, or
	  non-proprietary software for which a fee may be charged for the 
	  packaged distribution.
<P>
Redistribution of binary versions is further constrained by license agreements
for incorporated libraries from third parties, e.g. LDAP, GSSAPI.
<P>
The University of Washington encourages unrestricted distribution of 
individual patches to the Pine
system.  By &quot;patches&quot; we mean &quot;difference&quot; files 
that can be applied
to the University of Washington Pine source distribution in order to 
accomplish bug fixes, minor
enhancements, or adaptation to new operating systems.  Submission of these
patches to University of Washington for possible inclusion in future 
Pine versions is also
encouraged.
<P>
The above permissions are hereby granted, provided that the Pine and Pico
copyright and trademark notices appear in all copies and that both the
above copyright notice and this permission notice appear in supporting
documentation, and that the name of the University of Washington not be
used in advertising or publicity pertaining to distribution of the
software without specific, prior written permission.  This software is
made available &quot;as is&quot;, and
<P>
THE UNIVERSITY OF WASHINGTON DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
WITH REGARD TO THIS SOFTWARE, INCLUDING WITHOUT LIMITATION ALL IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND IN
NO EVENT SHALL THE UNIVERSITY OF WASHINGTON BE LIABLE FOR ANY SPECIAL,
INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, TORT
(INCLUDING NEGLIGENCE) OR STRICT LIABILITY, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 



<P>
&lt;End of Pine Legal Notices&gt;
</BODY>
</HTML>
===== h_info_on_mbox =====
<HTML>
<HEAD>
<TITLE>Information on mbox driver</TITLE>
</HEAD>
<BODY>
<H1>Information on &quot;Missing Mail&quot; and the &quot;mbox&quot; driver</H1>

Beginning with Pine 4.00 (but also with earlier versions of the
University of Washington's imapd server), a new INBOX access method is
available as part of the standard configuration.  It is called the
&quot;mbox&quot; driver and it works like this:<P>

<P>
<BLOCKQUOTE>
If the file &quot;mbox&quot; exists in the user's home directory, and
is in Unix mailbox format, then when INBOX is opened this file will be
selected as INBOX instead of the mail spool file.  Messages will be
automatically transferred from the mail spool file into the mbox
file. Beginning with Pine 4.01, a message is displayed whenever Pine
copies messages from the system mail spool directory to the mbox
file.
</BLOCKQUOTE>

<P>
The advantage of this method is that, after new mail has been copied
from the system mail spool, all subsequent access is confined to the
user's home directory, which is desirable on some systems.  However, a
possible disadvantage is that mail tools other than those from the
University of Washington will not know to look for mail in the user's
mbox file.  For example, POP or IMAP servers other than those from the
University of Washington, and many &quot;new mail notification&quot;
programs may not work as expected with this driver enabled.<P>

To disable this behavior, either remove/rename the &quot;mbox&quot;
file or find the &quot;disable-these-drivers=&quot; variable in your
Pine configuration file and add &quot;mbox&quot; to it.  You must
manually edit the config file so that you see the following:<P>
disable-these-drivers=mbox

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_info_on_locking =====
<HTML>
<HEAD>
<TITLE>FAQs on Pine Locking</TITLE>
</HEAD>
<BODY>
<H1>What Systems Managers Need to Know about Pine File Locking</H1>

There is an extensive section on locking in the Pine technical notes;
this information is intended to provide answers to some common questions:<P>
<OL>
<LI> Why did locking change in Pine 4.00?<BR>
The actual locking mechanisms did not change in 4.00.
What changed is that when one particular locking mechanism used by Pine 
fails, Pine now issues a warning message.  Prior to 4.00, the locking
failure would occur, but no warning was issued.<P>

<LI> Is this what the &quot;Mailbox vulnerable&quot; message is about?<BR>
Yes.  It means that Pine was unable to create a lockfile in the
spool directory, generally because of overly restrictive protections on the
spool directory.  The correct permissions on the spool directory for
running Pine are 1777, i.e. read-write-execute permission for everyone,
with the sticky-bit set, so only owners of a file can delete them.<P>

<LI> Why does Pine require that the mail spool directory have 1777
   protections?<BR>
Pine was designed to run without special privileges.  This means that in
order to create a lockfile in the spool directory, it is necessary to have
the spool directory permissions be world-writable.<P>

<LI> Can't you create the lockfile somewhere else?<BR>
No.  The lockfile in question must be in the mail spool directory, because
that's where the mail delivery program expects to find it, and the purpose
of the file is to coordinate access between the mail client (Pine) and the
mail delivery program.<P>

<LI> Isn't having the spool directory world-writable a big security risk?<BR>
No.  Remember that the individual mail files in the spool directory are
NOT world-writable, only the containing directory.  Setting the &quot;sticky
bit&quot; -- indicated by the &quot;1&quot; before the &quot;777&quot; mode 
-- means that only the owner of the file (or root) can delete files in the 
directory.  So the only bad behavior that is invited by the 1777 mode is that 
anyone could
create a random file in the spool directory.  If the spool directory is
under quota control along with home directories, there is little incentive
for anyone to do this, and even without quotas a periodic scan for
non-mail files usually takes care of the problem.  <P>

<LI> Why not run Pine as setgid mail?<BR>
Pine was never designed to run with privileges, and to do so introduces a
significant security vulnerability.  For example, if a user suspends Pine,
the resulting shell will have group privileges.  This is one example of
why we strongly recommend against running Pine as a privileged program.
In addition, a &quot;privileged mailer &quot paradigm would mean that normal 
users
could not test Pine versions or other mailers that had not been installed
by the system administrators.<P>


<LI> Are there any alternatives to creating .lock files in the spool dir?<BR>
There are, but they all have different sets of tradeoffs, and not all will
work on all systems.  Some examples:<UL>
 <LI> Use lock system calls.  Works fine on a few systems, provided mail
   spool is local.   Doesn't work reliably if NFS is used.
   Doesn't work unless <B>all</B> the mail programs accessing the spool dir
   use the same calls.
 <LI> Deliver mail to user's home directory.  An excellent solution, highly
   recommended -- but one which is incompatible with some &quot;legacy&quot; 
mail tools that always look in the spool directory for the mail.
</UL><P>

<LI> Are these spool directory lock files the only kinds of locks used by
   Pine?<BR>
No.  Pine also creates lockfiles in the /tmp directory.  For normal Unix
mailbox format folders, these are used to coordinate access between
multiple Pine sessions.  <P>

<LI> What about the 
<A HREF="h_config_quell_lock_failure_warnings">&quot;quell-lock-failure-warnings&quot;</A> feature added in Pine 4.01?<BR>
This is for people who are content to live dangerously, or who have
specific knowledge that the spool directory lockfiles are superfluous on
their system (because both Pine and the mail delivery program are using 
system call file locking in a context that works reliably, e.g. not NFS.)<P>

<LI> Where can I find more details on how Pine locking works?<BR>
See the Pine Technical Notes.<P>

</OL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_finding_help ====
<HTML>
<HEAD>
<TITLE>Finding more information and requesting help</TITLE>
</HEAD>
<BODY>
<H1>Places to Look for More Answers</H1>
If you have questions about or problems with Pine that you cannot resolve 
after consulting the program's internal, context-sensitive help screens, here 
are additional information resources that you may find helpful:
<P>
<UL>
  <LI> Pine's internal <A HREF="h_news">Release Notes</A>.  They contain a 
listing of changes in Pine <!--#echo var="PINE_VERSION"-->
  since the last version, which may be useful for you to be aware of, 
<B>especially</B> if a &quot;problem&quot; you are encountering is actually 
a change in the way an aspect of Pine works.  There, you will also find notes 
on Pine configuration.<P>

  <LI> The Pine Information Center (maintained by the University of
	   Washington) World Wide Web site contains, among other things
	   <UL>
	   <LI>a collection of Frequently Asked Questions (and answers!) about Pine
	   <LI>an overview of the basics for beginning Pine users
	   <LI>Technical Notes for systems administrators
	   <LI>archives (including a searchable index) of the pine-info 
mailing list, on which matters of interest to systems/email administrators,
developers, trainers, user support personnel, and others involved with Pine 
messaging on a &quot;technical&quot; level are discussed.
</UL>
	The Pine Information Center can be accessed with a WWW browser at:<P>
	    <CENTER><A HREF="http://www.washington.edu/pine/">http://www.washington.edu/pine/</A></CENTER>  
</UL>
<P><HR WIDTH="75%">
<H1>Requesting help</H1>
If the internal help, the Release Notes, the Pine Information Center, and your 
local online and print resources do not help you resolve a problem, please
start by contacting your local computer support staff and asking for help.
<p>
This is especially true if:
<ul>
  <li>You suddenly have trouble sending or receiving mail.
  <li>You receive a "disk quota exceeded" message.
  <li>You have forgotten your password.
  <li>You think your account may have been compromised.
  <li>You need help viewing an attachment.
  <li>You need to know how to configure your:
      <A HREF="h_config_nntp_server">NNTP (news) server</A>, 
      <A HREF="h_config_smtp_server">SMTP (sending mail) server</A>, 
      <A HREF="h_config_ldap_server">LDAP (directory lookup) server</A>, or
      <A HREF="h_config_inbox_path">INBOX (incoming mail) path</A>.
  <li>You want to know what alternative editors or spellcheckers you may be able to use.
  <li>You want to block email from a particular person.
  <li>You're going on vacation and need to autorespond to incoming mail.
  <li>You want to automatically file or filter incoming messages.
</ul>

In all of these cases,
you should contact <B>your</B> support staff, because <B>only they</B> 
will be able to assist you effectively. Your support staff may be, depending on who 
provides you with the email account you use Pine with, for example:<UL>
<LI> the computing help desk of (a department of) your university, school, 
employer, ... ; or
<LI> the customer service center of your Internet Service Provider; or
<LI> the friendly volunteer helpers of your Freenet; or
<LI> the person who setup your computer and internet connection.
</UL>

Due to the large number of Pine installations worldwide, and because we
receive no funding for it, the Pine development team <B>cannot provide 
individual support services outside the University of Washington</B>.
<P>
If you have no local computing support to turn to, the worldwide <b>comp.mail.pine</b>
newsgroup can be a valuable source of information and assistance for Pine 
user issues.
<P>
For systems/email administrators, developers, trainers, user support
personnel, and others involved with Pine messaging on a &quot;technical&quot;
level, the mailing list pine-info is available; for information on
subscribing and posting to it, see
<P>
<CENTER><A HREF="http://www.washington.edu/pine/pine-info/subscribing.html">http://www.washington.edu/pine/pine-info/subscribing.html</A></CENTER>
<P>

Regardless of whom you are asking for help with Pine, remember 
to provide as much detail as you can about the
nature of any problem you are encountering, such as
<UL>
<LI>when it first occurred;
<LI>what, if anything, happened that might have brought it about;
<LI>whether it still persists;
<LI>whether it is reproducible, and if so, how;
<LI>what, if anything, you already tried to solve it.
</UL> 
It may also be helpful if you specify what version of Pine you are using 
<!--chtml if pinemode="running"-->
-- this is <!--#echo var="PINE_VERSION"--> --
<!--chtml endif-->
and on what system, and when the copy of Pine you are using was created
<!--chtml if pinemode="running"-->
-- for this copy: <!--#echo var=PINE_COMPILE_DATE-->
<!--chtml endif-->

<!--chtml if pinemode="running"-->
<P>   
When the Pine program you are currently using was installed, a support
contact email address may have been set up; in that case, you can simply select
this link now to send a message to it:<BR>
<A HREF="X-Pine-Gripe:_LOCAL_ADDRESS_?local"><!--#echo var="_LOCAL_FULLNAME_"--></A><P>
<!--chtml endif-->
<!--chtml if [ -r /usr/local/lib/pine.info ]-->
<HR WIDTH="75%">Local Support Contacts:<P>
<!--#include file="/usr/local/lib/pine.info"-->
<HR WIDTH="75%">
<!--chtml endif-->
<P> 
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== new_user_greeting ======
<HTML>
<HEAD>
<TITLE>NEW USER GREETING</TITLE>
</HEAD>
<BODY>
<CENTER>&lt;&lt;&lt;This message will appear only once&gt;&gt;&gt;</CENTER>
<BR>
<H1>Welcome to Pine ... a Program for Internet News and Email</H1>
We hope you will explore Pine's many capabilities. From the Main Menu,
select Setup/Config to see many of the options available to you. Also note
that all screens have context-sensitive help text available.<P>
<!--chtml if pinemode="phone_home"-->
SPECIAL REQUEST:
This software is made available world-wide as a public service of the
University of Washington in Seattle.  In order to justify continuing
development, it is helpful to have an idea of how many people are using
Pine.  Are you willing to be counted as a Pine user?  Pressing 
<A HREF="X-Pine-Phone-Home:">Return</A>
will send an anonymous (meaning, your real email address will not be revealed) 
message to the Pine development team at the University of Washington for 
purposes of tallying.
<P>
<!--To Exit this screen and continue your Pine session press "E".-->
<!--chtml else-->
To Exit this screen and continue your Pine session press "Return".
<!--chtml endif-->
<CENTER>Pine is a trademark of the University of Washington.</CENTER>
</BODY>
</HTML>
===== new_version_greeting ======
<HTML>
<HEAD>
<TITLE>NEW VERSION GREETING</TITLE>
</HEAD>
<BODY>
<CENTER>&lt;&lt;&lt;This message will appear only once&gt;&gt;&gt;</CENTER>
<BR>
<H1>Welcome to Pine version <!--#echo var="PINE_VERSION"-->!</H1>
Your Pine configuration file indicates that you may not have used 
this version of Pine before.  This version's significant changes are
documented in the Release Notes, which may be viewed by pressing 
&quot;R&quot; now or while in the Main Menu.
<P>
<!--chtml if pinemode="phone_home"-->
SPECIAL REQUEST: 
This software is made available world-wide as a public service of the
University of Washington in Seattle.  In order to justify continuing
development, it is helpful to have an idea of how many people are using
Pine.  Are you willing to be counted as a Pine user?  Pressing 
<A HREF="X-Pine-Phone-Home:">Return</A>
will send an anonymous (meaning, your real email address will not be revealed) 
message to the Pine development team at the University of Washington for 
purposes of tallying.

<!--To Exit this screen and continue your Pine session press "E".-->
<!--chtml else-->
To Exit this screen and continue your Pine session press "Return".
<!--chtml endif-->
<P>
<CENTER>Pine is a trademark of the University of Washington.</CENTER>
</BODY>
</HTML>
===== main_menu_tx ======
<HTML>
<HEAD>
<TITLE>GENERAL INFORMATION ON THE PINE MESSAGE SYSTEM</TITLE>
</HEAD>
<BODY>
<H1>GENERAL INFORMATION ON THE PINE MESSAGE SYSTEM</H1>
<CENTER>Version <!--#echo var="PINE_VERSION"-->
<!--chtml if pinemode="running"-->
(built <!--#echo var=PINE_COMPILE_DATE-->)
<!--chtml endif-->
<BR>University of Washington</CENTER>

<H2>TABLE OF CONTENTS</H2>
<OL>
  <LI> <A HREF="#intro">Introduction</A>
  <LI> <A HREF="#pine_help">Pine Help</A>
<!--chtml if [ -r /usr/local/lib/pine.info ]-->
  <LI> <A HREF="#local_support">Local Support Contacts</A>
<!--chtml endif-->
  <LI> <A HREF="#giving_cmds">Giving Commands in Pine</A>
  <LI> <A HREF="#status_line">Status Line</A>
  <LI> <A HREF="#main_menu">Main Menu Commands</A>
  <LI> <A HREF="#cmd_line">Command Line Options</A>
  <LI> <A HREF="#pine_conf">Pine Configuration</A>
  <LI> <A HREF="#read_news">Reading News</A>
  <LI> <A HREF="#probs">Reporting Problems</A>
</OL>

<H2><A NAME="intro">Introduction</A></H2>

Pine&reg; is the University of Washington's &quot;Program for Internet
News and Email&quot;.  It is intended to be an easy-to-use program for
sending, receiving, and filing Internet electronic mail messages and
bulletin board (Netnews/Usenet) messages. Pine supports the following
Internet protocols and specifications:<P>

<DL>
<DT>SMTP</DT> <DD>Simple Mail Transport Protocol</DD>
<DT>NNTP</DT> <DD>Network News Transport Protocol</DD>
<DT>MIME</DT> <DD>Multipurpose Internet Mail Extensions</DD>
<DT>IMAP</DT> <DD>Internet Message Access Protocol</DD>
</DL>

MIME allows you to attach any kind of file to your message, provided that
your recipient also has MIME-capable mail software (which is readily
available for most types of computers, although some proprietary mail
systems do not yet support MIME).  IMAP allows access to mailboxes on
remote mailservers as if they were local.
<P>

Although originally designed for inexperienced email users, Pine has
evolved to support many advanced features.  There are an ever-growing
number of configuration and personal-preference options, though which of
them are available to you is determined by your local system managers. 

<H3>WHAT PINE DOES...</H3>

Pine is a &quot;mail user agent&quot; (MUA), which is a program that
allows you to
compose and read messages using Internet mail standards.  (Whether you
can correspond with others on the Internet depends on whether or not your
computer is connected to the Internet.)  Pine also allows reading and
posting messages on the Internet &quot;net news&quot; system, provided
that your site operates a suitable news server.

<H3>WHAT PINE DOES NOT DO...</H3>

A &quot;mail user agent&quot; such as Pine is just one part of a
messaging system. Here are some things that are <B>not</B> done by Pine,
but require other programs:<P>
<UL>
 <LI> Actual relaying of email... which is done by &quot;message transfer agents&quot;.
 <LI> Delivery filtering... putting incoming messages into different folders.
 <LI> Vacation messages... automatically responding to incoming messages
 <LI> Anything to do with &quot;talk&quot;... which has nothing to do with email.
 <LI> Anything to do with &quot;irc&quot;... which has nothing to do with email.
 <LI> List processing... resending one message to a list of recipients.
</UL>


<H2><A NAME="pine_help">Pine Help</A></H2>

Pine help is context-sensitive.  In other words, each Pine screen you use
will have its own help text, explaining the choices available for that
screen.  This particular Help section is unusual in that it will not only
describe the specific commands available from the MAIN MENU, but also
provide an overview of Pine operation.<P>

In addition to this general help on Pine, <A HREF="h_news">Release Notes</A>
on the current Pine version are also available from the MAIN MENU: Press
<!--chtml if pinemode="function_key"-->
&quot;F9&quot;
<!--chtml else-->
&quot;R&quot;
<!--chtml endif-->
there
to browse the release notes.  These include changes since the last release,
notes for PC-Pine, configuration information, the history of the Pine
project, credits, and legal notices.

Pine files and documentation are available via FTP or WWW:
<P>
<CENTER><SAMP><A HREF="ftp://ftp.cac.washington.edu/pine/">ftp://ftp.cac.washington.edu/pine/</A></SAMP></CENTER>
or
<CENTER><SAMP><A HREF="http://www.washington.edu/pine/">http://www.washington.edu/pine/</A></SAMP></CENTER>
<P>
For a copy of the current Pine &quot;Frequently Asked Questions&quot;
(FAQ) list, send an empty message to
<A HREF="mailto:pine-faq@cac.washington.edu">pine-faq@cac.washington.edu</A>.
<P>

If you would like to print <EM>all</EM> of Pine's internal help text for
a little light bedtime reading, then press
<!--chtml if pinemode="function_key"-->
&quot;F12&quot;
<!--chtml else-->
&quot;Z&quot;
<!--chtml endif-->
now.  (This assumes that the
copy of Pine you are using has been properly configured for printing
at your site.)


<!--chtml if [ -r /usr/local/lib/pine.info ]-->
<H2><A NAME="local_support">Local Support Contacts</A></H2>
<!--#include file="/usr/local/lib/pine.info"-->
<!--chtml endif-->

<H2><A NAME="giving_cmds">Giving Commands in Pine</A></H2>

<H4>Commands</H4>
The bottom two lines of the screen are always used to list the
commands you can give.  You press the keys that are highlighted to give
the command.  The commands for getting help and going back to the main
menu are always present (except when viewing help as you are now).
<!--chtml if pinemode="function_key"-->
<!--chtml else-->
<H4>Other Commands</H4>
The &quot;Other Commands&quot; function changes the keys
you see at the bottom of any screen.  In some cases there are 3 different
pages of keys which it toggles through.  <EM>All commands are active</EM>,
even if they are not currently showing at the bottom of your screen.
In other words, you <EM>never</EM> need to prefix a command key with
the 'O' key.

<H3>Control Key</H3>
When composing mail and in a few other places in Pine you
have to use Control keys which means pressing the control key and the
letter indicated at the same time.  This is usually shown with a
&quot;^&quot; in front of the letter.  On some systems, certain control
characters are intercepted before they get to Pine.  As a work-around,
you can press the ESCAPE key twice followed by the desired key.  For
example, if Control-O (^O) does not work on your system, try typing
&quot;ESC ESC O&quot;.
<!--chtml endif-->
<H3>PAGING UP/DOWN</H3>
The &quot;+&quot; and &quot;-&quot; keys are used for
moving to the next or previous page.  The space bar is a synonym for
&quot;+&quot;.  You may also use Ctrl-V to page down and Ctrl-Y to page
up as you do in the message composer.  On screens with a WhereIs (search)
command, W or Ctrl-W followed by Ctrl-V will move to the bottom of the
message or list, and W or Ctrl-W followed by Ctrl-Y will move to the top
of the message or list.

<H3>Return Key</H3>
The return key is usually a synonym for a frequently used
command.  When viewing a message, there is currently not a default
command, so RETURN does nothing; when in the index, it is synonymous with
&quot;view msg&quot;. In the key menu at the bottom of the screen, whatever is
enclosed in square brackets [] is the same as the return key.

<H3>Control Keys Not Used By Pine</H3>
Most commands in Pine are single letters,
with --we hope-- some mnemonic value, but in places where Pine is expecting
text input, e.g. in the composer or at prompts for file/folder names,
control keys must be used for editing and navigation functions.
<P>

Pine has used nearly all the control keys available.  There are, however,
certain control keys that are reserved by other programs or for technical
reasons.  Pine does not use any of these keys:
<DL>
 <DT>Ctrl-S</DT> <DD>Used by Unix as &quot;stop output&quot;</DD>
 <DT>Ctrl-Q</DT> <DD>Used by Unix as &quot;resume output&quot;</DD>
 <DT>Ctrl-]</DT> <DD>Often used by Telnet as escape key</DD>
 <DT>Ctrl-&#92;</DT> <DD>Often used by Unix as &quot;Abort&quot;</DD>
 <DT>ESC</DT> <DD>Conflicts with sequences used for arrow keys</DD>
</DL>
<P>

NOTE: For special handling see special comments regarding
<A HREF="h_special_xon_xoff">XOFF/XON</A>.

<H3>REPAINTING THE SCREEN</H3>
Sometimes what is displayed on the screen will be
incorrect due to noise on the phone line or other causes and you will want
to repaint the whole screen to make it correct.  You can use the Ctrl-L
command to do this.  It never hurts to do it when in doubt.


<H2><A NAME="status_line">Status Line</A></H2>

The top line of the screen is Pine's status line.  It will always display
the current version of Pine and will also convey information about the
status of the program.  This is where you look to find out what
collection, folder and message number is active.
<P>

If the top line says &quot;READONLY&quot; it means that the open folder
(typically your INBOX) is &quot;locked&quot; by another mail session --
most likely a more recent session of Pine has taken the INBOX lock.
<P>

If the top line says &quot;CLOSED&quot; it means that you are trying to
access a
folder on a remote mail server, and for some reason, communication with
the mail server has either been lost, or never successfully established.
This can be a result of trying to open a non-existent folder, or one
stored on an invalid or non-operational server, or it can mean that Pine
has been suspended for more that 30 minutes while accessing a remote mail
server.

<H2><A NAME="main_menu">Main Menu Commands</A></H2>
<!--chtml if pinemode="function_key"-->
&nbsp;Available&nbsp;Commands&nbsp;--&nbsp;Group&nbsp;1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Available&nbsp;Commands&nbsp;--&nbsp;Group&nbsp;2<BR>
&nbsp;------------------------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;------------------------------<BR>
&nbsp;F1&nbsp;&nbsp;Show&nbsp;this&nbsp;help&nbsp;text&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F1&nbsp;&nbsp;Show&nbsp;this&nbsp;help&nbsp;text<BR>
&nbsp;F2&nbsp;&nbsp;Show&nbsp;all&nbsp;other&nbsp;available&nbsp;commands&nbsp;&nbsp;&nbsp;F2&nbsp;&nbsp;Show&nbsp;other&nbsp;commands<BR>
&nbsp;F3&nbsp;&nbsp;Quit&nbsp;Pine<BR>
&nbsp;F4&nbsp;&nbsp;Execute&nbsp;current&nbsp;MAIN&nbsp;MENU&nbsp;command&nbsp;&nbsp;&nbsp;F4&nbsp;&nbsp;<A HREF="h_common_compose">Compose</A>&nbsp;a&nbsp;message<BR>
&nbsp;F5&nbsp;&nbsp;Select&nbsp;previous&nbsp;command&nbsp;up&nbsp;on&nbsp;menu&nbsp;&nbsp;F5&nbsp;&nbsp;<A HREF="h_common_folders">FOLDER&nbsp;LIST</A>&nbsp;screen<BR>
&nbsp;F6&nbsp;&nbsp;Select&nbsp;next&nbsp;command&nbsp;down&nbsp;on&nbsp;menu&nbsp;&nbsp;&nbsp;&nbsp;F6&nbsp;&nbsp;<A HREF="h_common_goto">Goto</A>&nbsp;a&nbsp;specified&nbsp;folder<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F7&nbsp;&nbsp;<A HREF="h_common_index">MESSAGE&nbsp;INDEX</A>&nbsp;screen<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F8&nbsp;&nbsp;<A HREF="h_main_journal">Journal</A>&nbsp;of&nbsp;status&nbsp;messages<BR>
&nbsp;F9&nbsp;&nbsp;Display&nbsp;<A HREF="h_main_release_notes">Release&nbsp;Notes</A>&nbsp;notes&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F9&nbsp;&nbsp;<A HREF="h_main_setup">SETUP</A>&nbsp;menus<BR>
&nbsp;F10&nbsp;<A HREF="h_main_kblock">Lock&nbsp;Keyboard</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F10&nbsp;<A HREF="h_main_addrbook">ADDRESS&nbsp;BOOK</A>&nbsp;screen<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F11&nbsp;<A HREF="h_main_role">Compose&nbsp;message&nbsp;using&nbsp;a&nbsp;role</a><BR>
<!--chtml else-->
&nbsp;General&nbsp;Pine&nbsp;Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Main&nbsp;Menu&nbsp;Screen&nbsp;Commands<BR>
&nbsp;---------------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-------------------------<BR>
&nbsp;?&nbsp;&nbsp;Show&nbsp;Help&nbsp;Text&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;O&nbsp;&nbsp;Show&nbsp;all&nbsp;Other&nbsp;available&nbsp;commands<BR>
&nbsp;C&nbsp;&nbsp;<A HREF="h_common_compose">Compose</A>&nbsp;a&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;P&nbsp;&nbsp;Select&nbsp;Previous&nbsp;command&nbsp;up&nbsp;on&nbsp;menu<BR>
&nbsp;I&nbsp;&nbsp;<A HREF="h_common_index">MESSAGE&nbsp;INDEX</A>&nbsp;screen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;N&nbsp;&nbsp;Select&nbsp;Next&nbsp;command&nbsp;down&nbsp;on&nbsp;menu<BR>
&nbsp;L&nbsp;&nbsp;<A HREF="h_common_folders">FOLDER&nbsp;LIST</A>&nbsp;screen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;R&nbsp;&nbsp;Display&nbsp;Pine&nbsp;<A HREF="h_main_release_notes">Release&nbsp;Notes</A><BR>
&nbsp;A&nbsp;&nbsp;<A HREF="h_main_addrbook">ADDRESS&nbsp;BOOK</A>&nbsp;screen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;K&nbsp;&nbsp;<A HREF="h_main_kblock">Lock&nbsp;Keyboard</A><BR>
&nbsp;S&nbsp;&nbsp;<A HREF="h_main_setup">SETUP</A>&nbsp;functions&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;G&nbsp;&nbsp;<A HREF="h_common_goto">Goto</A>&nbsp;a&nbsp;specified&nbsp;folder<BR>
&nbsp;Q&nbsp;&nbsp;Quit&nbsp;Pine&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;J&nbsp;&nbsp;<A HREF="h_main_journal">Journal</A>&nbsp;of&nbsp;status&nbsp;messages<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;#&nbsp;&nbsp;<A HREF="h_main_role">Compose&nbsp;message&nbsp;using&nbsp;a&nbsp;role</a><BR>
<!--chtml endif-->

<P>
NOTE:
<OL>
 <LI>For help on a particular command, hilite the bold text associated
with it above and hit Return.
 <LI> The availability of certain commands (e.g. some of the options under
SETUP) is determined by Pine configuration files and system capabilities.
At some sites, certain commands may not be available due to security or
support concerns.
</OL>


<H2><A NAME="cmd_line">Command Line Options</A></H2>

Possible Starting Arguments for Pine program:
<PRE>
	Argument                Meaning

	&lt;address&gt;...    Go directly into composer with given address
	-a              Special anonymous mode for UWIN*
	-c              Context # for interpreting -f argument
			 0=none, 1=incoming, 2=deflt coll'n, 3=next coll'n
	-d n            Debug - set debug level to 'n'
	-f &lt;folder&gt;     Folder - open &lt;folder&gt; in default collection
	-F &lt;file&gt;       File - open and view text &lt;file&gt;
	-h              Help - give this list of options
	-i              Index - Go directly to index, bypassing main menu
	-I &lt;key_list&gt;   Initial keystrokes to be executed
	-k              Keys - Force use of function keys
	-l              List - Expand List of folder collections by default
	-n &lt;number&gt;     Entry in index to begin on
	-nr             Special restricted mode for UWIN*
	-o              ReadOnly - Open first folder read-only
	-p &lt;file&gt;       Use &lt;file&gt; in place of .pinerc file
	-P &lt;file&gt;       Use &lt;file&gt; in place of pine.conf file
	-r              Restricted/demo mode
	-z              Suspend - allow use of ^Z suspension
	-sort &lt;sort&gt;    Sort - Specify sort order of MESSAGE INDEX:
		   (Subject, OrderedSubj, Arrival, Date, From, Size, /reverse)
	-conf           Configuration - Output fresh global config to stdout
	-create_lu &lt;addrbk&gt; &lt;sort&gt;  Create auxiliary look-up file and
			sort &lt;addrbk&gt; by &lt;sort&gt;.  For creating global addrbk.
	-pinerc &lt;file&gt;  Configuration - Put fresh pinerc config in &lt;file&gt;
	-&lt;option&gt;=&lt;value&gt;       Assign &lt;value&gt; to the pinerc option &lt;option&gt;
				e.g. -signature-file=sig1
				(NOTE: feature-list is additive)

		     * UWIN = University of Washington Information Navigator
</PRE>


<H2><A NAME="pine_conf">Pine Configuration</A></H2>

Unless it has been administratively disabled, the Setup command on the
MAIN MENU has a &quot;Config&quot; subcommand which will allow you to modify
Pine's behavior by setting or unsetting various features, defining folder
collections, etc.  These settings are stored in your personal
&quot;pinerc&quot; configuration file, but on shared systems these settings
may be over-ridden by a system-wide control file (due to local site
security or support policies).  A global pine configuration file can also
be used to set default values for all Pine users on a particular system.


<H2><A NAME="read_news">Reading News</A></H2>

<H3>BACKGROUND</H3>

Pine can read and post Internet news (Netnews or USENET) groups, using the
same commands as for mail.  If you do not already have a news state
(&quot;.newsrc&quot;) file, Pine will create one for you, and you can add
newsgroups to it using the &quot;Add&quot; command in the FOLDER LIST screen.
Pine can use the same newsrc as other Unix newsreaders, thus allowing you
to switch between Pine and other newsreaders; however, Pine uses the
information in the file in a slightly different way than other newsreaders.

<H3>CONFIGURATION</H3>

Pine can access news folders in any one of three different ways:
<DL>
<DT>REMOTE NNTP</DT>
<DD>Using the Network News Transport Protocol (NNTP) to
access news on a remote news server.  In this case the newsrc file is
stored on the machine where Pine is running.

<P>
To specify a remote news-collection accessed via NNTP use the
SETUP/collectionList screen's &quot;Add&quot; command.  Set the
Server: value to the NNTP server's hostname appended with the
communication method &quot;/service=NNTP&quot;, and set the Path:
value to the &quot;#news.&quot; namespace (without the quotes).  See
the &quot;<A HREF="h_composer_cntxt_server">Server:</A>&quot; field's
help text for a more complete explanation of access method, and the
&quot;<A HREF="h_composer_cntxt_path">Path:</A>&quot; field's help
text for a more complete explanation of &quot;namespace&quot;.

<DT>REMOTE IMAP</DT>
<DD>Using the Internet Message Access Protocol (IMAP) to
access news on a remote news server.  In this case, your newsrc file is
stored on the news server, in your home directory, so you must have an
account on the news server, but you would be running Pine on a different
machine.  The news server must be running an IMAPd server process. 

<P>
To specify a remote news-collection accessed via IMAP use the
SETUP/collectionList screen's &quot;Add&quot; command.  Set the
Server: value to the IMAP server's hostname, and set the Path: value
to the &quot;#news.&quot; namespace (without the quotes).  See the
&quot;<A HREF="h_composer_cntxt_path">Path:</A>&quot; field's help
text for a more complete explanation of &quot;namespace&quot;.

</DD>

<DT>LOCAL</DT>
<DD>Using local file access to the news database.  In this
case, your newsrc file is stored on the news server, in your home
directory, so you must have an account on the news server, and you would
be running Pine on the same machine.

<P>
To specify a local news-collection use the SETUP/collectionList
screen's &quot;Add&quot; command.  Leave the Server: value blank, and
set the Path: value to the &quot;#news.&quot; namespace (without the
quotes).  See the &quot;<A HREF="h_composer_cntxt_path">Path:</A>&quot;
field's help text for a more complete explanation of &quot;namespace&quot;.

</DD>
</DL>

<P>

NOTE: Should no news-collection be defined as above, Pine will
automatically create one using the Setup/Config screen's
&quot;nntp-server&quot; variable's value if defined.  The collection
will be created as a &quot;Remote NNTP&quot; as described above.

<P>

If you are a PC-Pine user, either option 1 (NNTP) or option 2 (IMAP) is
possible.  If you don't have an account on the news server, or if the news
server is not running an IMAP daemon, then you must use NNTP.  (If you are not
sure, ask your service provider, university, or company for help.)  In
this case, your Unix .newsrc file can be transferred to your PC.  A good
place to put it would be in the same directory as your PINERC file, under
the name &#92;NEWSRC, but you can 
<A HREF="h_config_newsrc_path">specify a different location</A>
via Pine's Setup/Config screen.

<P>
A future version of PC-Pine will be able to access and update a .newsrc
file stored on a Unix host, so that it will be possible to alternate
between PC-Pine and Unix-based newsreaders.

<H3>READING NEWS</H3>

Once defined in the <!--chtml if pinemode="os_windows"-->
PINERC<!--chtml else-->
.pinerc (or the global pine.conf) <!--chtml endif-->
file, the news
folder collection can be accessed either via the FOLDER LIST screen, or
via the GOTO command.
<P>

Pine uses the same commands for manipulating news folders as for mail
folders.  This means, for example, that when you are done with a message,
you would use &quot;D&quot; to mark it as Deleted (or Dismissed, if you
prefer.)  This &quot;mail-like&quot; behavior differs from that of most
newsreaders, wherein a message is implicitly dismissed after you have
looked at it once. We strongly believe that Pine should offer as much
consistency as possible between mail and news, so the mail paradigm
-- wherein a message does not magically disappear without explicit action
by the user-- is used for news as well.
<P>

News folders are actually Read Only, but the newsrc file allows Pine to
keep track of which messages you have dismissed (marked as Deleted) just
as in a regular mail folder. The difference is that, although messages
marked as Deleted will show up in the Index (just as mail messages do
until an eXpunge), you cannot expunge news messages.  However, you can use
the &quot;eXclude&quot; (X) command in order to suppress from the MESSAGE INDEX
messages that are so marked.  Also, whenever you open a newsgroup folder,
messages marked Deleted are already excluded from the Index by default.
The &quot;unexclude&quot; (&) command will restore them to the MESSAGE INDEX.
<P>

If you answer a message in a news folder, the index view will show the
&quot;A&quot; flag as usual; but the newsrc file has no way of storing
this flag, so it will not be preserved across sessions.  The Deleted flag
is the only one that is preserved between sessions.  If you Reply to a
newsgroup message and say you want to reply to all recipients, Pine will
ask if you want to post the message to all the newsgroups listed in the
original message.
<P>

If you would like Pine to mark more-or-less recent news messages as
&quot;New&quot;, then set the
<A HREF="h_config_news_uses_recent">&quot;news-approximates-new-status&quot;</A>
feature.  This will cause messages after the last one you have marked as
Deleted to appear with &quot;N&quot; status in the MESSAGE INDEX.  The
&quot;N&quot; status often makes it easier to distinguish later news
articles from those you've previously seen, but not yet disposed of via
the &quot;D&quot; key.  Note that this is an approximation, not an exact
record of which messages you have not seen.
<P>

A frequent operation in news-reading is &quot;catching up&quot;... that is,
getting rid of all the messages in the newsgroup so that you can &quot;start
fresh&quot;.  The easiest way to do this in Pine is via the
Select command.  You would enter the following four keystrokes: ;aad
Note that the
<A HREF="h_config_enable_agg_ops">&quot;enable-aggregate-command-set&quot;</A>
feature must be enabled before you can use the Select command.

<H2><A NAME="probs">Reporting Problems</A></H2>

There are now literally millions of Pine users in over 50 countries.
The Pine development team has no funding to provide support to anyone
outside of the University of Washington.  However, we certainly want Pine
to be the best tool it can be, so we do want to know about problems. We
ask that you first read the relevant help screens, if any, and then seek
assistance from your own support staff.  Once you are sure that your
difficulty is not a local configuration problem, you might look at the
help section explaining where to look for
<A HREF="h_finding_help">more information</A> and where to 
get assistance.
<P>

Please note: Pine has been adapted to several other operating systems
besides those directly supported by the University of Washington; see:
<P>
<CENTER><A HREF="http://www.washington.edu/pine/overview/non-UW.html">http://www.washington.edu/pine/overview/non-UW.html</A></CENTER>

<P>
Inquiries about these other ports (e.g., VMS and AmigaDOS) should be
directed to the individual or group that did the adaptation. 
<P>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Pine&nbsp;Development&nbsp;Team&nbsp;&lt;pine@cac.washington.edu&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Computing&nbsp;&amp;&nbsp;Communications
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;University&nbsp;of&nbsp;Washington
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Seattle,&nbsp;WA&nbsp;&nbsp;98195

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============== h_special_xon_xoff =============
<HTML>
<HEAD>
<TITLE>Explanation of Pine's XOFF/XON Handling</TITLE>
</HEAD>
<BODY>
<H1>XOFF/XON Handling within Pine</H1>

By default, Pine treats Ctrl-S or Ctrl-Q (sometimes known as XOFF
and XON) as normal characters, even though Pine does not use them.
However, the printer, modem, or communication software you are using may
be configured for &quot;software flow control,&quot; which means that
XON/XOFF must be treated as special characters by the operating system.
If you see messages such as &quot;^X not defined for this screen&quot;,
then your system is probably using software flow control. In this case
you will need to set the
<A HREF="h_config_preserve_start_stop">&quot;preserve-start-stop-characters&quot;</A>
feature.
<P>
If you <EM>do</EM> set this
feature, be advised that if you accidentally hit a Ctrl-S, Pine will
mysteriously freeze up with no warning.  In this case, try typing a Ctrl-Q
and see if that puts things right.  Printing via the
&quot;attached-to-ansi&quot; option will automatically enable software
flow-control handling for the duration of the printing.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_special_help_nav =============
<HTML>
<HEAD>
<TITLE>Help Text Navigation Explained</TITLE>
</HEAD>
<BODY>
<H1>Help Text Navigation Explained</H1>

Pine contains extensive context-sensitive help text.   At any point, 
pressing the &quot;?&quot; key will bring up a page of help text
explaining the options available to you.  You can leave the help
text screen and return to normal Pine operation by pressing
the
<!--chtml if pinemode="function_key"-->
F3 function
<!--chtml else-->
&quot;E&quot;
<!--chtml endif-->
key to Exit Help at any time.

<P>
Within the help screen you might find a word or phrase displayed in 
inverse text and others displayed in bold typeface.  Such words and
phrases are used to tell you Pine has more information available on
the topic they describe.
The inverted text is the &quot;selected&quot; topic.  
Use the arrow keys, Ctrl-F, and Ctrl-B to change which of the phrases
displayed in bold type
is &quot;selected&quot;.
Hit the Return key to display the information Pine has available on that
topic.  While viewing such additional information, the 
<!--chtml if pinemode="function_key"-->
F3 function
<!--chtml else-->
&quot;P&quot;
<!--chtml endif-->
key will return you to the previous help screen, and the
<!--chtml if pinemode="function_key"-->
F2 function
<!--chtml else-->
&quot;E&quot;
<!--chtml endif-->
key will Exit the Help system altogether.

<P>
When you are finished reading this help text, you can press the
<!--chtml if pinemode="function_key"-->
F3 function
<!--chtml else-->
&quot;P&quot;
<!--chtml endif-->
key to return to the previously displayed help text.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_mail_index =============
<HTML>
<HEAD>
<TITLE>MESSAGE INDEX COMMANDS</TITLE>
</HEAD>
<BODY>                 
<H1>MESSAGE INDEX COMMANDS</H1>
<!--chtml if pinemode="function_key"-->
Available&nbsp;&nbsp;Commands&nbsp;--&nbsp;Group&nbsp;1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Available&nbsp;Commands&nbsp;--&nbsp;Group&nbsp;2<BR>
-------------------------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-----------------------------<BR>
F1&nbsp;&nbsp;Show&nbsp;Help&nbsp;Text&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F1&nbsp;&nbsp;Show&nbsp;Help&nbsp;Text<BR>
F2&nbsp;&nbsp;Toggle&nbsp;to&nbsp;see&nbsp;more&nbsp;commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F2&nbsp;&nbsp;Toggle&nbsp;to&nbsp;see&nbsp;more&nbsp;commands<BR>
F3&nbsp;&nbsp;<A HREF="h_common_folders">FOLDER&nbsp;LIST</A>&nbsp;Screen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F3&nbsp;&nbsp;MAIN&nbsp;MENU&nbsp;Screen<BR>
F4&nbsp;&nbsp;View&nbsp;current&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F4&nbsp;&nbsp;Quit&nbsp;Pine<BR>
F5&nbsp;&nbsp;Move&nbsp;to&nbsp;previous&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F5&nbsp;&nbsp;<A HREF="h_common_compose">Compose</A>&nbsp;a&nbsp;message<BR>
F6&nbsp;&nbsp;Move&nbsp;to&nbsp;next&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F6&nbsp;&nbsp;<A HREF="h_common_goto">Goto</A>&nbsp;a&nbsp;specified&nbsp;folder<BR>
F7&nbsp;&nbsp;Show&nbsp;previous&nbsp;screen&nbsp;of&nbsp;messages&nbsp;&nbsp;&nbsp;F7&nbsp;&nbsp;<A HREF="h_common_nextnew">Next&nbsp;new</A>&nbsp;message<BR>
F8&nbsp;&nbsp;Show&nbsp;next&nbsp;screen&nbsp;of&nbsp;messages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F8&nbsp;&nbsp;<A HREF="h_index_cmd_whereis">Whereis</A><BR>
F9&nbsp;&nbsp;<A HREF="h_common_delete">Mark&nbsp;message&nbsp;for&nbsp;deletion</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F9&nbsp;&nbsp;<A HREF="h_common_print">Print</A>&nbsp;message<BR>
F10&nbsp;<A HREF="h_common_delete">Undelete</A>&nbsp;(remove&nbsp;delete&nbsp;mark)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F10&nbsp;<A HREF="h_common_take">Take&nbsp;Address</A>&nbsp;into&nbsp;address&nbsp;book<BR>
F11&nbsp;<A HREF="h_common_reply">Reply</A>&nbsp;to&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F11&nbsp;<A HREF="h_common_save">Save</A>&nbsp;message&nbsp;into&nbsp;an&nbsp;email&nbsp;folder<BR>
F12&nbsp;<A HREF="h_common_reply">Forward</A>&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F12&nbsp;<A HREF="h_common_save">Export</A>&nbsp;message&nbsp;into&nbsp;a&nbsp;plain&nbsp;file<BR>
<BR>
Available&nbsp;Commands&nbsp;--&nbsp;Group&nbsp;3<BR>
-----------------------------<BR>
F3&nbsp;&nbsp;<A HREF="h_index_cmd_expunge">Expunge/Exclude</A>&nbsp;&nbsp;&nbsp;&nbsp;F7&nbsp;<A HREF="h_index_cmd_sort">Sort</A>&nbsp;order&nbsp;of&nbsp;index&nbsp;&nbsp;F10&nbsp;<A HREF="h_common_bounce">Bounce</A>&nbsp;(remail)&nbsp;msg<BR>
F5&nbsp;&nbsp;<A HREF="h_index_cmd_select">Select</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F8&nbsp;<A HREF="h_common_jump">Jump</A>&nbsp;to&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F11&nbsp;<A HREF="h_common_flag">Flag</A>&nbsp;message&nbsp;as&nbsp;important<BR>
F6&nbsp;&nbsp;<A HREF="h_index_cmd_apply">Apply</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F9&nbsp;<A HREF="h_common_hdrmode">Full&nbsp;Header&nbsp;Mode</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F12&nbsp;<A HREF="h_common_pipe">Pipe</A>&nbsp;to&nbsp;a&nbsp;Unix&nbsp;command<BR>
<BR>
Available&nbsp;Commands&nbsp;--&nbsp;Group&nbsp;4<BR>
-----------------------------<BR>
F3&nbsp;&nbsp;Select&nbsp;Current&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F4&nbsp;&nbsp;<A HREF="h_index_cmd_zoom">Zoom</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F5&nbsp;&nbsp;COLLECTION&nbsp;LIST&nbsp;Screen
<BR>
<!--chtml else-->
Navigating&nbsp;the&nbsp;List&nbsp;of&nbsp;Messages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Operations&nbsp;on&nbsp;the&nbsp;Current&nbsp;Message<BR>
-------------------------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;---------------------------------<BR>
&nbsp;P&nbsp;&nbsp;&nbsp;Move&nbsp;to&nbsp;the&nbsp;previous&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&gt;&nbsp;&nbsp;View&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;%&nbsp;&nbsp;<A HREF="h_common_print">Print</A><BR>
&nbsp;N&nbsp;&nbsp;&nbsp;Move&nbsp;to&nbsp;the&nbsp;next&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;R&nbsp;&nbsp;<A HREF="h_common_reply">Reply</A>&nbsp;to&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F&nbsp;&nbsp;<A HREF="h_common_reply">Forward</A><BR>
&nbsp;-&nbsp;&nbsp;&nbsp;Show&nbsp;previous&nbsp;screen&nbsp;of&nbsp;messages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;D&nbsp;&nbsp;<A HREF="h_common_delete">Mark&nbsp;for&nbsp;deletion</A><BR>
Spc&nbsp;&nbsp;Show&nbsp;next&nbsp;screen&nbsp;of&nbsp;messages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;U&nbsp;&nbsp;<A HREF="h_common_delete">Undelete</A>&nbsp;(remove&nbsp;deletion&nbsp;mark)<BR>
&nbsp;J&nbsp;&nbsp;&nbsp;<A HREF="h_common_jump">Jump</A>&nbsp;to&nbsp;a&nbsp;specific&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;T&nbsp;&nbsp;<A HREF="h_common_take">Take&nbsp;Address</A>&nbsp;into&nbsp;Address&nbsp;Book<BR>
&nbsp;W&nbsp;&nbsp;&nbsp;<A HREF="h_index_cmd_whereis">Whereis</A>&nbsp;--&nbsp;search&nbsp;for&nbsp;a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;S&nbsp;&nbsp;<A HREF="h_common_save">Save</A>&nbsp;into&nbsp;an&nbsp;email&nbsp;folder<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;specific&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E&nbsp;&nbsp;<A HREF="h_common_save">Export</A>&nbsp;as&nbsp;a&nbsp;plain&nbsp;text&nbsp;file<BR>
Tab&nbsp;&nbsp;<A HREF="h_common_nextnew">Next&nbsp;new</A>&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;B&nbsp;&nbsp;<A HREF="h_common_bounce">Bounce</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;<A HREF="h_common_flag">Flag</A><BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;<A HREF="h_common_pipe">Pipe</A>&nbsp;to&nbsp;a&nbsp;Unix&nbsp;Command<BR>
Miscellaneous&nbsp;Operations<BR>
------------------------<BR>
&nbsp;G&nbsp;&nbsp;&nbsp;<A HREF="h_common_goto">Goto</A>&nbsp;a&nbsp;specified&nbsp;folder&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;General&nbsp;Pine&nbsp;Commands<BR>
&nbsp;$&nbsp;&nbsp;&nbsp;<A HREF="h_index_cmd_sort">Sort</A>&nbsp;order&nbsp;of&nbsp;index&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;---------------------<BR>
&nbsp;H&nbsp;&nbsp;&nbsp;<A HREF="h_common_hdrmode">Full&nbsp;header&nbsp;mode</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;O&nbsp;&nbsp;Show&nbsp;all&nbsp;other&nbsp;available&nbsp;commands<BR>
&nbsp;X&nbsp;&nbsp;&nbsp;<A HREF="h_index_cmd_expunge">Expunge/Exclude</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;?&nbsp;&nbsp;Show&nbsp;Help&nbsp;text&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Q&nbsp;Quit&nbsp;Pine<BR>
&nbsp;Z&nbsp;&nbsp;&nbsp;<A HREF="h_index_cmd_zoom">Zoom</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;M&nbsp;&nbsp;MAIN&nbsp;MENU&nbsp;Screen&nbsp;&nbsp;&nbsp;&lt;&nbsp;<A HREF="h_common_folders">FOLDER&nbsp;LIST</A>&nbsp;Screen<BR>
&nbsp;;&nbsp;&nbsp;&nbsp;<A HREF="h_index_cmd_select">Select</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A&nbsp;<A HREF="h_index_cmd_apply">Apply</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C&nbsp;&nbsp;<A HREF="h_common_compose">Compose</A>&nbsp;a&nbsp;new&nbsp;message<BR>
&nbsp;:&nbsp;&nbsp;&nbsp;Select&nbsp;Current&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;L&nbsp;&nbsp;COLLECTION&nbsp;LIST&nbsp;Screen<BR>
<!--chtml endif-->
<P>

NOTE:
<OL>
 <LI>For help on a particular command, hilite the bold text associated
with it above and hit Return.
 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
</OL>

<H2>Description of the MESSAGE INDEX Screen</H2>

The MESSAGE INDEX displays summary information from each
message in the current folder.
This is useful if you want to quickly
scan new messages, or find a particular message without having to go
through the text of each message, or to quickly get rid of junk
messages, etc.
The current message is always highlighted.
Each line of the MESSAGE INDEX contains the following columns (by default -- 
you can change this with the 
&quot;<A HREF="h_config_index_format">Index-Format</A>&quot; option
in the SETUP CONFIGURATION screen): <P>
<DL>
 <DT>STATUS:</DT>
 <DD> The markings on the left side of the message tell you about its
status.  You may see one or more of the following codes on any given
message:
<UL>
  <LI> &quot;D&quot; for Deleted.  You have marked this message for deletion but not
	 yet eXpunged the folder.
  <LI> &quot;N&quot; for New.  You have not looked at the text of the message yet.
  <LI> &quot;A&quot; for Answered.  Any time you reply to a message it is considered
	 to be answered.
  <LI> &quot;+&quot; for direct-to-you.  The &quot;+&quot; indicates that a message was sent
	directly to your account, your copy is not part of a cc: or a
	mailing list.
  <LI> &quot;X&quot; for selected.  You have selected the message by using the
	&quot;select&quot; command.  (Some systems may optionally allow selected
	messages to be denoted by the index line being displayed in bold
	type.)
  <LI> &quot;*&quot; for Important.  You have previously used the &quot;Flag&quot; command
      to mark this message as &quot;important&quot;.
</UL></DD><P>

 <DT>NUMBER:</DT>
 <DD>Messages in a folder are numbered, from one through the number
of messages in the folder, to help you know where you are in the folder.</DD><P>


 <DT>DATE SENT:</DT>
 <DD>The date the message was sent.  By default, messages are
ordered by arrival time, not by date sent.  Most of the time, arrival time
and date sent (effectively departure time) are similar.  Sometimes,
however, the index will appear to be out of order because a message took a
long time in delivery.</DD><P>


 <DT>SENDER:</DT>
 <DD>The name or email address of the sender.  If you are the sender,
then the recipient's name is shown here.  In Newsgroups, if you are
the sender and there are no email recipients, the newsgroup name will be
listed. </DD><P>


 <DT>SIZE:</DT>
 <DD>The number in parentheses is the number of characters in the message.</DD><P>


 <DT>SUBJECT:</DT>
 <DD>As much of the message's subject line as will fit on the screen.</DD>
</DL>

<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_mail_view ========================
<HTML>
<HEAD>
<TITLE>MESSAGE TEXT SCREEN</TITLE>
</HEAD>
<BODY>
<H1>MESSAGE TEXT SCREEN</H1>
<!--chtml if pinemode="function_key"-->
Available&nbsp;&nbsp;Commands&nbsp;--&nbsp;Group&nbsp;&nbsp;1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Available&nbsp;Commands&nbsp;--&nbsp;Group&nbsp;2<BR>
-------------------------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;------------------------------<BR>
F1&nbsp;&nbsp;Show&nbsp;Help&nbsp;Text&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F1&nbsp;&nbsp;Show&nbsp;Help&nbsp;Text<BR>
F2&nbsp;&nbsp;Toggle&nbsp;to&nbsp;see&nbsp;more&nbsp;commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F2&nbsp;&nbsp;Toggle&nbsp;to&nbsp;see&nbsp;more&nbsp;commands<BR>
F3&nbsp;&nbsp;<A HREF="h_common_index">MESSAGE&nbsp;INDEX</A>&nbsp;Screen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F3&nbsp;&nbsp;MAIN&nbsp;MENU&nbsp;Screen<BR>
F4&nbsp;&nbsp;<A HREF="h_view_cmd_viewattch">View&nbsp;attachment</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F4&nbsp;&nbsp;Quit&nbsp;Pine<BR>
F5&nbsp;&nbsp;Display&nbsp;previous&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F5&nbsp;&nbsp;<A HREF="h_common_folders">FOLDER&nbsp;LIST</A>&nbsp;Screen<BR>
F6&nbsp;&nbsp;Display&nbsp;next&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F6&nbsp;&nbsp;<A HREF="h_common_goto">Goto</A>&nbsp;a&nbsp;specified&nbsp;folder<BR>
F7&nbsp;&nbsp;Previous&nbsp;screen&nbsp;of&nbsp;this&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;F7&nbsp;&nbsp;<A HREF="h_common_compose">Compose</A>&nbsp;message<BR>
F8&nbsp;&nbsp;Next&nbsp;screen&nbsp;of&nbsp;this&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F8&nbsp;&nbsp;<A HREF="h_view_cmd_whereis">Whereis</A><BR>
F9&nbsp;&nbsp;<A HREF="h_common_delete">Mark&nbsp;message&nbsp;for&nbsp;deletion</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F9&nbsp;&nbsp;<A HREF="h_common_print">Print</A>&nbsp;message<BR>
F10&nbsp;<A HREF="h_common_delete">Undelete</A>&nbsp;(remove&nbsp;delete&nbsp;mark)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F10&nbsp;<A HREF="h_common_take">Take&nbsp;Address</A>&nbsp;into&nbsp;address&nbsp;book<BR>
F11&nbsp;<A HREF="h_common_reply">Reply</A>&nbsp;to&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F11&nbsp;<A HREF="h_common_save">Save</A>&nbsp;message&nbsp;into&nbsp;an&nbsp;email&nbsp;folder<BR>
F12&nbsp;<A HREF="h_common_reply">Forward</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F12&nbsp;<A HREF="h_common_save">Export</A>&nbsp;message&nbsp;into&nbsp;a&nbsp;plain&nbsp;file<BR>
<BR>
Available&nbsp;Commands&nbsp;--&nbsp;Group&nbsp;3<BR>
------------------------------<BR>
F1&nbsp;&nbsp;Show&nbsp;Help&nbsp;Text<BR>
F2&nbsp;&nbsp;Toggle&nbsp;to&nbsp;see&nbsp;more&nbsp;commands<BR>
F3&nbsp;&nbsp;<A HREF="h_view_cmd_hilite">View&nbsp;hilited</A><BR>
F4&nbsp;&nbsp;Select&nbsp;current&nbsp;message<BR>
F5&nbsp;&nbsp;Previous&nbsp;selectable&nbsp;item<BR>
F6&nbsp;&nbsp;Next&nbsp;selectable&nbsp;item<BR>
F7&nbsp;&nbsp;<A HREF="h_common_jump">Jump</A>&nbsp;to&nbsp;message&nbsp;number<BR>
F8&nbsp;&nbsp;<A HREF="h_common_nextnew">Next&nbsp;new</A>&nbsp;message<BR>
F9&nbsp;&nbsp;<A HREF="h_common_hdrmode">Display&nbsp;full&nbsp;headers</A><BR>
F10&nbsp;<A HREF="h_common_bounce">Bounce</A>&nbsp;message<BR>
F11&nbsp;<A HREF="h_common_flag">Flag</A>&nbsp;message<BR>
F12&nbsp;<A HREF="h_common_pipe">Pipe</A>&nbsp;to&nbsp;a&nbsp;Unix&nbsp;command<BR>
<!--chtml else-->
Operations&nbsp;on&nbsp;the&nbsp;Current&nbsp;Message<BR>
---------------------------------<BR>
<BR>
&nbsp;-&nbsp;&nbsp;&nbsp;Show&nbsp;previous&nbsp;page&nbsp;of&nbsp;this&nbsp;msg&nbsp;&nbsp;&nbsp;&nbsp;S&nbsp;&nbsp;<A HREF="h_common_save">Save</A>&nbsp;into&nbsp;an&nbsp;email&nbsp;folder<BR>
Spc&nbsp;&nbsp;Show&nbsp;next&nbsp;page&nbsp;of&nbsp;this&nbsp;msg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E&nbsp;&nbsp;<A HREF="h_common_save">Export</A>&nbsp;as&nbsp;a&nbsp;plain&nbsp;text&nbsp;file<BR>
&nbsp;&gt;&nbsp;&nbsp;&nbsp;<A HREF="h_view_cmd_viewattch">View&nbsp;attachment</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;B&nbsp;&nbsp;<A HREF="h_common_bounce">Bounce</A><BR>
&nbsp;R&nbsp;&nbsp;&nbsp;<A HREF="h_common_reply">Reply</A>&nbsp;to&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;F&nbsp;&nbsp;<A HREF="h_common_reply">Forward</A>&nbsp;message<BR>
&nbsp;D&nbsp;&nbsp;&nbsp;<A HREF="h_common_delete">Mark&nbsp;for&nbsp;deletion</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ret&nbsp;View&nbsp;<A HREF="h_view_cmd_hilite">hilited</A>&nbsp;item<BR>
&nbsp;U&nbsp;&nbsp;&nbsp;<A HREF="h_common_delete">Undelete</A>&nbsp;(remove&nbsp;deletion&nbsp;mark)&nbsp;&nbsp;^F&nbsp;&nbsp;Select&nbsp;next&nbsp;<A HREF="h_view_cmd_hilite">hilited</A>&nbsp;item&nbsp;in&nbsp;message<BR>
&nbsp;T&nbsp;&nbsp;&nbsp;<A HREF="h_common_take">Take&nbsp;Address</A>&nbsp;into&nbsp;Address&nbsp;Book&nbsp;&nbsp;&nbsp;^B&nbsp;&nbsp;Select&nbsp;previous&nbsp;<A HREF="h_view_cmd_hilite">hilited</A>&nbsp;item<BR>
&nbsp;%&nbsp;&nbsp;&nbsp;<A HREF="h_common_print">Print</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;<A HREF="h_common_flag">Flag</A>&nbsp;message<BR>
&nbsp;W&nbsp;&nbsp;&nbsp;<A HREF="h_view_cmd_whereis">Whereis</A>:&nbsp;search&nbsp;for&nbsp;text&nbsp;in&nbsp;msg&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;<A HREF="h_common_pipe">Pipe</A>&nbsp;to&nbsp;a&nbsp;Unix&nbsp;command<BR>
<BR>
Navigating&nbsp;the&nbsp;List&nbsp;of&nbsp;Messages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Other&nbsp;Commands<BR>
-------------------------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;----------------------------<BR>
&nbsp;P&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Display&nbsp;previous&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;G&nbsp;&nbsp;&nbsp;<A HREF="h_common_goto">Goto</A>&nbsp;a&nbsp;specified&nbsp;folder<BR>
&nbsp;N&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Display&nbsp;next&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;H&nbsp;&nbsp;&nbsp;<A HREF="h_common_hdrmode">Full&nbsp;header&nbsp;mode</A>&nbsp;on/off<BR>
&nbsp;J&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_common_jump">Jump</A>&nbsp;to&nbsp;a&nbsp;specific&nbsp;message&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;&nbsp;&nbsp;Select&nbsp;Current&nbsp;message<BR>
Tab&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_common_nextnew">Next&nbsp;new</A>&nbsp;message<BR>
<BR>
General&nbsp;Pine&nbsp;Commands<BR>
---------------------<BR>
&nbsp;O&nbsp;&nbsp;Show&nbsp;all&nbsp;other&nbsp;available&nbsp;commands<BR>
&nbsp;?&nbsp;&nbsp;Show&nbsp;Help&nbsp;text&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Q&nbsp;Quit&nbsp;Pine<BR>
&nbsp;M&nbsp;&nbsp;MAIN&nbsp;MENU&nbsp;Screen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;L&nbsp;<A HREF="h_common_folders">FOLDER&nbsp;LIST</A>&nbsp;Screen&nbsp;(or&nbsp;COLLECTION&nbsp;LIST&nbsp;Screen)<BR>
&nbsp;&lt;&nbsp;&nbsp;<A HREF="h_common_index">MESSAGE&nbsp;INDEX</A>&nbsp;Screen&nbsp;&nbsp;C&nbsp;<A HREF="h_common_compose">Compose</A>&nbsp;a&nbsp;new&nbsp;message<BR>
<!--chtml endif-->
<P>

NOTE:
<OL>
 <LI>For help on a particular command, hilite the bold text associated
with it above and hit Return.
 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
</OL>

<H2>Description of the MESSAGE TEXT Screen</H2>

The top line of the view message screen displays status
information about the currently open collection and folder and about the
current message.  It shows the name of the collection in angle brackets
and then the name of the folder.  The line also displays the number
of messages in the folder, the number of the current message and the
percentage of the current message that has been displayed on the screen.
If the message is marked for deletion &quot;DEL&quot; will appear in the upper
right corner.
If the message has been answered (but not deleted) &quot;ANS&quot; will show
in the corner.
<P>

NOTE: to rapidly move to the end of a message, hit the
<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
(or Ctrl-W) key followed
by Ctrl-V.  Similarly,
<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
followed by Ctrl-Y will take you to the beginning of
a message.

<H2>Explanation of Alternate Character Sets</H2>

Pine attempts to stay out of the way so that it won't prevent you from
viewing mail in any character set.  It will simply send the message to
your display device.  If the device is capable of displaying the
message as it was written it will do so.  If not, the display may be
partially or totally incorrect.  If the message is marked as being in
a character set other than &quot;US-ASCII&quot; and it is a character
set that is different from the set you have indicated with the
<A HREF="h_config_char_set">&quot;character-set&quot;</A>
variable in your configuration, then a warning message will be printed
to your screen at the beginning of the message display.<P>

In all cases Pine requires that the display device can handle the
character set.  For example, most X-terminals will display the ISO-8859-1
character set if the right font is selected.  VT220's and higher also
display ISO-8859-1.  Displays for other characters sets are less common.
<P>

Pine usually suppresses display of control characters in order to avoid
characters which may change terminal setup parameters.
If this is a problem for you, the
&quot;<A HREF="h_config_pass_control">pass-control-characters-as-is</A>&quot;
feature can be used to turn this behavior off.

<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_index_cmd_select =======
<HTML>
<HEAD>
<TITLE>Selecting: Select and WhereIs/Select</TITLE>
</HEAD>
<BODY>
<H1>Selecting: Select and WhereIs/Select</H1>

Aggregate operations give you the ability to process a group of messages
at once.  Acting on multiple messages requires two steps: (1) selecting a
set of messages and then (2) applying a command to that set. The first
part is handled by the select command.  Select allows you to
select messages based on their status (read, answered, etc.), contents
(including fielded selections on header lines) or date.  You also get
certain quick options to select a specific message or range of messages,
to select the current message or to select all messages.
<P>

After you have an initial selection, the select command changes.  It gives
you selection &quot;alteration&quot; options: unselect all, unselect current,
broaden (implements a logical OR), and narrow (implements a logical AND).
You are allowed to use select as many times as you need to get the
selected set right.
<P>

Also, starting with Pine 4.00, the WhereIs command has a new feature 
(Ctrl-X) to
select all the messages which match the WhereIs search. WhereIs searches
through just the text which appears on the MESSAGE INDEX screen.
<P>

The availability of the aggregate operations commands is determined by the
<A HREF="h_config_enable_agg_ops">&quot;enable-aggregate-command-set&quot;</A>
feature-list option in your Pine
configuration.
The features
<A HREF="h_config_auto_zoom">&quot;auto-zoom-after-select&quot;</A>
and
<A HREF="h_config_select_wo_confirm">&quot;select-without-confirm&quot;</A>
affect the behavior of the Select command.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_index_cmd_apply =======
<HTML>
<HEAD>
<TITLE>Apply Command</TITLE>
</HEAD>
<BODY>
<H1>Apply Command</H1>

Apply
(<!--chtml if pinemode="function_key"-->F6<!--chtml else-->A<!--chtml endif-->)
is the second step of most aggregate operations.  Apply
becomes active any time there is a defined set of selected messages.  The
following commands can be applied to a selected message set: delete,
undelete, reply, forward,
<!--chtml if pinemode="os_windows"-->
<!--chtml else--> 
pipe,
<!--chtml endif-->
print, take address, save, export, bounce, and flag.
<P>

The behavior of some of these commands in an aggregate sense is not easy to
explain.  Try them out to see what they do.
The feature
<A HREF="h_config_auto_unzoom">&quot;auto-unzoom-after-apply&quot;</A>
affects the behavior of the Apply command.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_index_cmd_zoom =======
<HTML>
<HEAD>
<TITLE>ZoomMode Command</TITLE>
</HEAD>
<BODY>
<H1>ZoomMode Command</H1>

Another action you might want to take on a set of selected messages is to
zoom in on them.  Like apply, zoom only becomes active when messages have
been selected.
ZoomMode
(<!--chtml if pinemode="function_key"-->F3<!--chtml else-->Z<!--chtml endif-->)
is a toggle command which allows you to
zoom-in (and only see the selected messages) and zoom-out (to see all
messages in the folder).  Neither apply nor zoom removes the markings which
define the selected set; you need to use a select command in order
to do that.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_index_cmd_sort =======
<HTML>
<HEAD>
<TITLE>Sort Command</TITLE>
</HEAD>
<BODY>
<H1>Sort Command</H1>

In Pine's generic configuration, messages are presented in the order in
which they arrive.  This default can be changed in the SETUP CONFIGURATION 
with the <A HREF="h_config_sort_key">&quot;Sort-Key&quot;</A> option.
You can also re-sort the folder on demand with the sort
(<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
command.
Your sorting options are: Subject, Arrival, From, To, Cc, Date, siZe,
OrderedSubject and Reverse.
<P>

Some of the subtleties: sorting by subject will group all messages with
the same subject together and then puts the groups in alphabetical order.
Sorting by &quot;ordered subject&quot; does a grouping intended to simulate a
&quot;threaded&quot; sort, and then presents each &quot;thread&quot; in order of the date
of the first message in the group.  Reverse simply reverses whatever the
current sort order is.<P>

Sorting a folder does not actually rearrange the way the folder is saved,
it just re-arranges how the messages are presented to you.  This means
that Pine has to do the work of sorting every time you change sort order.
Sometimes, especially with PC-Pine or with large folders, this could take
a while.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_index_cmd_whereis =======
<HTML>
<HEAD>
<TITLE>WhereIs Command</TITLE>
</HEAD>
<BODY>
<H1>WhereIs Command</H1>

The WhereIs
(<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
command lets you search the MESSAGE INDEX for a word.  It scans
through whatever you see, usually the name of the author and the subject
line.  WhereIs has special features to let you &quot;find&quot; the beginning of the
index (Ctrl-Y -- first message) or the end of the index (Ctrl-V -- last
message).  WhereIs can also be used as a quick way to select messages; see
below for more information on this.  Note that WhereIs does not see the 
&quot;X&quot; in column one of Index entries for &quot;selected&quot; messages
so it can't be used to search for selected messages (use &quot;Zoom&quot;).

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_view_cmd_whereis =======
<HTML>
<HEAD>
<TITLE>WhereIs Command</TITLE>
</HEAD>
<BODY>
<H1>WhereIs Command</H1>

The WhereIs
(<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
command does a &quot;find in current message&quot; operation.  You
type in text and Pine will try to find it in the message you are
reading.  You can also use WhereIs to jump to the beginning (Ctrl-Y)
or end (Ctrl-V) of the message.
That is, to rapidly move to the end of a message, hit the 
<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
(or Ctrl-W) key followed
by Ctrl-V.  Similarly,
<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
followed by Ctrl-Y will take you to the beginning of a message.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_view_cmd_hilite =======
<HTML>
<HEAD>
<TITLE>View Hilite and Next item/Previous item</TITLE>
</HEAD>
<BODY>
<H1>View Hilite and Next item/Previous item</H1>

Sometimes messages may be in the form of formatted HTML text
or they may contain URLs or Web server hostnames.
When any of the features
<A HREF="h_config_enable_view_url">&quot;enable-msg-view-urls&quot;</A>,
<A HREF="h_config_enable_view_web_host">&quot;enable-msg-view-web-hostnames&quot;</A>,
<A HREF="h_config_enable_view_attach">&quot;enable-msg-view-attachments&quot;</A>,
or
<A HREF="h_config_enable_view_addresses">&quot;enable-msg-view-addresses&quot;</A>
are enabled, Pine will represent such selectable items in the text
in bold typeface.  One of the selectable items will be displayed in
inverse video (hilited).  This is the &quot;currently selected&quot; item.
Press the Return key to view the currently selected item.
<P>

The Up and Down Arrows keys can be used to change the selected item
(also see the feature
<A HREF="h_config_enable_view_arrows">&quot;enable-msg-view-forced-arrows&quot;</A>).
If there are no selectable items in the direction of the arrow you
pressed, Pine will scroll the display in that direction until one
becomes visible.  To &quot;jump&quot; forwards/backwards among selectable 
items in the message text, use the Previous and Next item commands,
<!--chtml if pinemode="function_key"-->F5 and F6
<!--chtml else-->^B and Ctrl-F<!--chtml endif-->.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_view_cmd_viewattch =======
<HTML>
<HEAD>
<TITLE>ViewAttch Command</TITLE>
</HEAD>
<BODY>
<H1>ViewAttch Command</H1>


The View/Save Attachment
(<!--chtml if pinemode="function_key"-->F4<!--chtml else-->V<!--chtml endif-->)
command allows you to handle MIME attachments to a message you have
received.  Pine shows you a list of the message attachments -- you just
choose the attachment you want.  You may either view or save the
selected attachment.

<P>
Because many attachments require external programs for display, there
is some system configuration that has to happen before you can
actually display attachments.  Hopefully much of that will have been
done already by your system administrator.  MIME configuration is
handled with the &quot;mailcap&quot; configuration file.  (See the section 
on configuration in the
<A HREF="h_news">release notes</A> for more information.)

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_index_cmd_expunge =======
<HTML>
<HEAD>
<TITLE>Expunge/Exclude Command</TITLE>
</HEAD>
<BODY>
<H1>Expunge/Exclude Command</H1>

Expunge/Exclude
(<!--chtml if pinemode="function_key"-->F3<!--chtml else-->X<!--chtml endif-->)
is the command Pine uses to actually remove all messages
marked for deletion.  With regular email files, expunge literally deletes
the text from the current folder.  With newsgroups or shared mailboxes,
you don't have permission to actually remove the message, so it is an
exclude -- Pine removes the message from your view of the folder even
though it is not technically gone.
<P>

The configuration features
<A HREF="h_config_auto_expunge">&quot;expunge-without-confirm&quot;</A>
and
<A HREF="h_config_full_auto_expunge">&quot;expunge-without-confirm-everywhere&quot;</A>
affect the behavior of the Expunge command.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_compose =======
<HTML>
<HEAD>
<TITLE>Compose Command</TITLE>
</HEAD>
<BODY>
<H1>Compose Command</H1>

The Compose command takes you into the Pine message composer where you
can start a new message for sending.  This is where you type in the
message's text and specify its recipient list (the &quot;To:&quot;
address), where copies should be directed (e.g., &quot;Fcc&quot;,
&quot;Cc:&quot; or &quot;Bcc:&quot;), and which files, if any, should
be attached to the message.

<P>
When you type this command, Pine will also automatically check for any
interrupted (i.e., a message that was being composed when your modem
or network connection was broken) or previously postponed messages and
offer you a chance to continue working on those.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_index =======
<HTML>
<HEAD>
<TITLE>Message Index Command</TITLE>
</HEAD>
<BODY>
<H1>Message Index Command</H1>

The Index command takes you to the MESSAGE INDEX screen which displays a
summary caption for each message in the currently-open folder. One
message will be highlighted; this is the &quot;Current&quot; message.
The message commands available from this screen (e.g. View, Reply,
Forward, Delete, Print, Save, etc) apply to the current message.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_folders =======
<HTML>
<HEAD>
<TITLE>Folder List Command</TITLE>
</HEAD>
<BODY>
<H1>Folder List Command</H1>

This Folder List command takes you to the FOLDER LIST screen which displays
the names of all your message folders and allows you to view, rename,
delete, and add folders.  You can open (view) a different folder than the
one currently open by highlighting the desired one (using the arrow keys
or their control-key equivalents) and pressing RETURN.

<P>
If you have multiple folder collections defined (see the Help text for
the FOLDER LIST screen to learn more about Collections), you may need
to press Return to expand the collection and display all of the
folders in it.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_main_addrbook =======
<HTML>
<HEAD>
<TITLE>Address Book Command</TITLE>
</HEAD>
<BODY>
<H1>Address Book Command</H1>

This command, available only from the MAIN MENU, takes you
to the ADDRESS BOOK management screen.  From here, your personal address
book(s) may be updated.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_main_setup =======
<HTML>
<HEAD>
<TITLE>Setup Command</TITLE>
</HEAD>
<BODY>
<H1>Setup Command</H1>

The Setup command, available only from the MAIN MENU, prompts you for
one of several configuration screens, including the SETUP CONFIGURATION 
screen, by which you may activate optional Pine features.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_main_release_notes =======
<HTML>
<HEAD>
<TITLE>Release Notes Command</TITLE>
</HEAD>
<BODY>
<H1>Release Notes Command</H1>

This command displays information about Pine <!--#echo var="PINE_VERSION"-->,
as well as pointers to further information such as history and legal notes.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_main_kblock =======
<HTML>
<HEAD>
<TITLE>Keyboard Lock Command</TITLE>
</HEAD>
<BODY>
<H1>Keyboard Lock Command</H1>

This command allows your Pine session to be protected
during a temporary absence from your terminal.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_main_journal =======
<HTML>
<HEAD>
<TITLE>Journal Command</TITLE>
</HEAD>
<BODY>
<H1>Journal Command</H1>

This command displays a list of all the status messages Pine has
displayed (on the third line from the bottom of the screen). This may
be useful if a message disappeared before you had a chance to read it.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_main_role =======
<HTML>
<HEAD>
<TITLE>Role Command</TITLE>
</HEAD>
<BODY>
<H1>Role Command</H1>

The Role command is similar to the Compose command except that it starts
off by letting you select a <A HREF="h_role_config">role</A>
to be used for the composition.
You may set up alternate roles by using the Setup command.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_conditional_cmds =======
<HTML>
<HEAD>
<TITLE>Conditional Commands</TITLE>
</HEAD>
<BODY>
<H1>Conditional Commands</H1>

The presence or absence of certain commands, particularly in the
MESSAGE INDEX and MESSAGE TEXT screens, is determined by
whether or not specific features are set in your Pine configuration.  
(You can access the SETUP CONFIGURATION screen, where they are found, from 
Pine's MAIN MENU.)  To see if a desired command's availability is
conditioned on a feature setting, see the command's help text (hilite
the phrase associated with the command and hit Return).

<P>
Also note that some
commands may be administratively disabled by your system manager;
if they don't work, please check with your local help desk.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_pipe =======
<HTML>
<HEAD>
<TITLE>Pipe Command</TITLE>
</HEAD>
<BODY>
<H1>Pipe Command</H1>

Pipe
(<!--chtml if pinemode="function_key"-->F12<!--chtml else-->|<!--chtml endif-->)
allows you to send a message to a specified Unix command for external
processing.
This command's availability is controlled by the
<A HREF="h_config_enable_pipe">&quot;enable-unix-pipe-cmd&quot;</A> 
feature.
By default, the processed text of the message is sent to the command
you specify and the output is captured by Pine and shown to you.
When you run the pipe command, there are some sub-commands which may be
used to alter this behavior.
These sub-commands are described <A HREF="h_pipe_command">here</A>.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_goto =======
<HTML>
<HEAD>
<TITLE>Goto Command</TITLE>
</HEAD>
<BODY>
<H1>Goto Command</H1>

Goto
(<!--chtml if pinemode="function_key"-->F6<!--chtml else-->G<!--chtml endif-->)
is the command which lets you bypass Pine's folder selection screens
and jump directly to a new folder.  You can select any folder in the
world: one in your current collection, one in a different collection or
one in a collection you've never even used before.
<P>

Pine will help you as much as possible to narrow in on the folder you want.
However, if the folder is outside of your defined collections, you are
going to have to enter the exact folder location using the correct
<A HREF="h_valid_folder_names">syntax</A>
for a remote folder and/or fully-qualified path name.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_nextnew =======
<HTML>
<HEAD>
<TITLE>NextNew Command</TITLE>
</HEAD>
<BODY>
<H1>NextNew Command</H1>

When you press the TAB key, Pine advances to the next
&quot;interesting&quot; message.  When you are using Pine to read
email, that message is the next message in the current folder which you have
not read before or which you have previously marked
&quot;Important&quot; via the Flag command.  When reading news
folders, the next &quot;interesting&quot; message is the next one
which you have not yet deleted.
<P>

The NextNew command's behavior is affected by the configuration features
<A HREF="h_config_auto_open_unread">&quot;auto-open-next-unread&quot;</A>
and
<A HREF="h_config_tab_new_only">&quot;tab-visits-next-new-message-only&quot;</A>.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_jump =======
<HTML>
<HEAD>
<TITLE>Jump Command</TITLE>
</HEAD>
<BODY>
<H1>Jump Command</H1>

This is Pine's way of allowing you to go straight to a specific message.
Just press &quot;J&quot; and then enter the message number.  Pine can also be
configured such that typing in any number automatically jumps you to that
message 
(<A HREF="h_config_enable_jump">&quot;enable-jump-shortcut&quot;</A> 
in the SETUP CONFIGURATION).

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_flag =======
<HTML>
<HEAD>
<TITLE>Flag Command</TITLE>
</HEAD>
<BODY>
<H1>Flag Command</H1>

Flag
(<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
is the command which allows users to manipulate the status flags which
appear on the left side of the MESSAGE INDEX screen.  The most common
use of this is to mark a message as important. This is something of a
note to yourself to get back to that message.  You can also use the
flag command to set (or unset) the flags which indicate that a message
is new, answered, or deleted.<P>

The availability of the flag command is determined by the
<A HREF="h_config_enable_flag">&quot;enable-flag-cmd&quot;</A>
feature in your Pine configuration. Also, it is possible that Flag could be
administratively disabled by your system manager; if it doesn't work,
please check with your local help desk before reporting a bug.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_hdrmode =======
<HTML>
<HEAD>
<TITLE>HdrMode Command</TITLE>
</HEAD>
<BODY>
<H1>HdrMode Command</H1>

Every email message comes with some header lines that you normally
don't see (and don't want to see).
These include anywhere from 3-20 lines (or more) added by the
Internet mail transport system to record the route your message took,
for diagnostic purposes.
These are normally of no import and simply
add clutter, so Pine suppresses them in the MESSAGE TEXT display.
This also includes other non-standard headers the message may contain.
If you want to see these headers, there is a way to reveal them.
<P>

The Header Mode
(<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
command is a toggle which controls Pine's handling of these header
lines.  Normally, full headers is &quot;off&quot; and you only see a
few lines about who a message is to and who it is from.  When you
press
(<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
to turn full headers on, Pine will show you
the normal header lines as well as delivery headers, comment headers,
MIME headers, and any other headers present.
<P>

Several different Pine commands honor the header mode -- it affects how
messages are displayed, how they appear in forward and reply email, how
they are printed, how they are saved, and how they are exported.
<!--chtml if pinemode="os_windows"-->
<!--chtml else--> 
The pipe command is also affected.
<!--chtml endif-->
<P>

The presence or absence of the Header Mode command is determined by the
<A HREF="h_config_enable_full_hdr">&quot;enable-full-header-cmd&quot;</A>
feature-list option in your Pine configuration.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_print =======
<HTML>
<HEAD>
<TITLE>Print Command</TITLE>
</HEAD>
<BODY>
<H1>Print Command</H1>

The Print
(<!--chtml if pinemode="function_key"-->F9<!--chtml else-->%<!--chtml endif-->)
command allows you to print a copy of a message.
There are many SETUP CONFIGURATION features which affect the
Print command, including
<A HREF="h_config_enable_y_print">&quot;enable-print-via-y-command&quot;</A>,
<A HREF="h_config_print_index">&quot;print-index-enabled&quot;</A>,
<A HREF="h_config_custom_print">&quot;print-offers-custom-cmd-prompt&quot;</A>,
<A HREF="h_config_print_from">&quot;print-includes-from-line&quot;</A>, and
<A HREF="h_config_ff_between_msgs">&quot;print-formfeed-between-messages&quot;</A>.
You set up for printing by using the Printer option of the Setup command
on the MAIN MENU.
<P>

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_take =======
<HTML>
<HEAD>
<TITLE>TakeAddr Command</TITLE>
</HEAD>
<BODY>
<H1>TakeAddr Command</H1>


With the Take Address
(<!--chtml if pinemode="function_key"-->F10<!--chtml else-->T<!--chtml endif-->)
command, you can extract email addresses from an
incoming message and save them in an address book.  This is an easy way
to add to your address book and avoid having to remember the email
addresses of the people who write to you.
<P>

If the message is just to you individually, then you will only need to
provide a nickname.  If the message contains more than one email address,
then you will see an address
selection screen which lets you choose the address you want to save into
your address book, or lets you choose several of them add to a
personal distribution list.
<P>

Once you've added an entry to your address book, you can use it from the
message composer by typing the nickname of the entry into one of the
header fields (for example, into the To: field), or you can use ^T from
the header field to select the entry from your address book.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_save =======
<HTML>
<HEAD>
<TITLE>Save and Export Commands</TITLE>
</HEAD>
<BODY>
<H1>Save and Export Commands</H1>

Save
(<!--chtml if pinemode="function_key"-->F11<!--chtml else-->S<!--chtml endif-->)
and Export
(<!--chtml if pinemode="function_key"-->F12<!--chtml else-->E<!--chtml endif-->)
are the two alternatives Pine gives you to keep a copy of the message
you are reading. If you want to keep the message within Pine's email
world, use &quot;save&quot;; if you want to use the message in another
program, use &quot;export&quot;.
<P>

When you save a message, it is put into an existing folder or into a new
folder in one of your existing folder collections.  The message stays in
email format and can be read by Pine again.  Pine may use a special format
for its mail folders -- never edit a Pine folder by hand or with any
program other than Pine.  The exact behavior of the save command can be
configured with the
<A HREF="h_config_quote_all_froms">&quot;save-will-quote-leading-froms&quot;</A>,
<A HREF="h_config_save_wont_delete">&quot;save-will-not-delete&quot;</A>,
and 
<A HREF="h_config_save_advances">&quot;save-will-advance&quot;</A>
feature list settings.
<P>

When you use export, the message is placed in a plain text file in your
home directory 
<!--chtml if pinemode="running"-->
(which, in the present configuration of your system, is
 &quot;<!--#echo var="HOME_DIR"-->&quot;) 
<!--chtml endif-->
or current working directory
<!--chtml if pinemode="running"-->
(which, at least for your current Pine &quot;session,&quot; 
is &quot;<!--#echo var="CURRENT_DIR"-->&quot;) 
<!--chtml endif-->, depending on the
<A HREF="h_config_use_current_dir">&quot;use-current-dir&quot;</A>
configuration setting.  In the normal case, only minimal
headers are exported with the message; however, if the full header mode 
(whose availability must be enabled  by setting the feature 
<A HREF="h_config_enable_full_hdr">&quot;enable-full-header-cmd&quot;</A>
in SETUP CONFIGURATION) is
toggled on, then complete headers are exported along with the message
text. (If you have any <A HREF="h_config_display_filters">Display-Filters</A>
defined, they may affect the contents of the exported file.)

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_bounce =======
<HTML>
<HEAD>
<TITLE>Bounce Command</TITLE>
</HEAD>
<BODY>
<H1>Bounce Command</H1>

The Bounce 
(<!--chtml if pinemode="function_key"-->F10<!--chtml else-->B<!--chtml endif-->)
command allows you to re-send, or &quot;remail&quot;, a
message, as if you were never in the loop.  It is analogous to crossing
out your address on a postal letter, writing a different address on the
envelope, and putting it into the mailbox. Bounce is used primarily to
redirect email which was sent to you in error.
Also, some owners of email
lists need the bounce command to handle list traffic.
Bounce is not anonymous.
A ReSent-From header is added to the message so that the recipient may
tell that you Bounced it to them.
<P>

The presence or absence of the Bounce command is determined by the
<A HREF="h_config_enable_bounce">&quot;enable-bounce-cmd&quot;</A>
feature in your Pine configuration.
The feature
<A HREF="h_config_fcc_on_bounce">&quot;fcc-on-bounce&quot;</A>
affects the behavior of the Bounce command.
Also, it is possible that Bounce could be
administratively disabled by your system manager; if it doesn't work,
please check with your local help desk before reporting a bug.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_reply =======
<HTML>
<HEAD>
<TITLE>Reply and Forward Commands</TITLE>
</HEAD>
<BODY>

<H1>Reply and Forward Commands</H1>

Replying 
(<!--chtml if pinemode="function_key"-->F11<!--chtml else-->R<!--chtml endif-->)
and Forwarding 
(<!--chtml if pinemode="function_key"-->F12<!--chtml else-->F<!--chtml endif-->)
are your two alternatives for following up on the
message you are reading.  You would use reply if you want to get email
back to the author of the message and/or the other people who have
already seen it.  You use forward if you want somebody new to see the
message.
<P>

In the normal case, the only thing that you must supply when forwarding a
message is the name/email address of the new recipient.
Pine will include the text of the forwarded message.
Pine will also include any attachments to the message.
There is space above the forwarded text for you to include additional comments.
<P>

When replying, you usually have to answer some questions.
If the message is to multiple people and/or specified with a Reply-To: header,
then you will have to decide who should get the reply.
You also need to decide whether or not to include the previous
message in your reply.
Some of this is configurable.
Specifically, see the
<A HREF="h_config_include_header">&quot;include-header-in-reply&quot;</A>,
<A HREF="h_config_auto_include_reply">&quot;include-text-in-reply&quot;</A>,
<A HREF="h_config_attach_in_reply">&quot;include-attachments-in-reply&quot;</A>,
and
<A HREF="h_config_auto_reply_to">&quot;reply-always-uses-reply-to&quot;</A>
configuration features.
<P>

Both the Reply and Forward commands react to the full header mode toggle.
If the full header mode is on, then all the header and delivery lines are
included with the text of the message in your reply/forward.
<P>

Other configuration features which affect the Reply command are
<A HREF="h_config_sig_at_bottom">&quot;signature-at-bottom&quot;</A>,
<A HREF="h_config_sigdashes">&quot;enable-sigdashes&quot;</A>, and
<A HREF="h_config_strip_sigdashes">&quot;strip-from-sigdashes-on-reply&quot;</A>.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_delete =======
<HTML>
<HEAD>
<TITLE>Delete and Undelete Commands</TITLE>
</HEAD>
<BODY>
<H1>Delete and Undelete Commands</H1>

Delete 
(<!--chtml if pinemode="function_key"-->F9<!--chtml else-->D<!--chtml endif-->)
and Undelete 
(<!--chtml if pinemode="function_key"-->F10<!--chtml else-->U<!--chtml endif-->)
allow you to change the Deleted flag for the current message.
Delete marks a message Deleted (turns on the Deleted flag) and Undelete
removes the mark.
In the MESSAGE INDEX, deleted messages have a &quot;D&quot; in the status field
at the left hand edge of the index line.
When viewing a deleted message, the letters &quot;DEL&quot; will be present
in the upper right hand corner of the screen.
Delete simply <EM>marks</EM> a message Deleted, it does not actually
get rid of the message.
The eXpunge command (available from the MESSAGE INDEX screen) actually
removes all of the deleted messages in a folder.
Once a message is eXpunged, it can't be retrieved.
<P>

The Delete command is affected by the setting of the configuration feature
<A HREF="h_config_del_skips_del">&quot;delete-skips-deleted&quot;</A>.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_postpone =======
<HTML>
<HEAD>
<TITLE>Postpone Command</TITLE>
</HEAD>
<BODY>
<H1>Postpone Command</H1>

The postpone
<!--chtml if pinemode="function_key"-->(F11)<!--chtml else-->(^O)<!--chtml endif-->
command allows you to temporarily stop working on the current
message so you may read
other messages or compose another message.  When you want to resume a
message later, start to compose and answer &quot;yes&quot; to the
&quot;Continue postponed composition?&quot; question.  You may
postpone as many messages as you like.

<P>
Note: If a <A HREF="h_config_form_folder">form-letter-folder</A> is defined
in the Setup/Config screen, then the Postpone command will prompt you for
the folder in which to store your outgoing message.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_compose_cancel =======
<HTML>
<HEAD>
<TITLE>Cancel Command</TITLE>
</HEAD>
<BODY>
<H1>Cancel Command</H1>

Cancel
<!--chtml if pinemode="function_key"-->
(F2)
<!--chtml else-->
(^C) 
<!--chtml endif-->

The Cancel command returns you to Pine's normal mail processing and
causes the message currently under composition to be thrown out.
The message text <EM>will be lost</EM>.

<P>
Note: Unless the <A HREF="h_config_quell_dead_letter">quell-dead-letter-on-cancel</A> has been set, the text of the most recent composition cancelled
will be preserved in the file named
<!--chtml if pinemode="os_windows"-->
&quot;DEADLETR&quot;.
<!--chtml else-->
&quot;dead.letter&quot; in your home directory.
<!--chtml endif-->
If you unintentionally cancel a message, look there for its text.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_compose_richhdr =======
<HTML>
<HEAD>
<TITLE>Rich Header Command</TITLE>
</HEAD>
<BODY>
<H1>Rich Header Command</H1>

The Rich Header command allows you to toggle between the list of 
all message headers available for editing and those that are most
common.

<P>
You would use this toggle to expose, for example, the &quot;Bcc:&quot; or
&quot;Fcc:&quot; header which aren't usually necessary to set (and thus
not displayed by default), but are sometimes helpful.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_compose_send =======
<HTML>
<HEAD>
<TITLE>Send Command</TITLE>
</HEAD>
<BODY>
<H1>Send Command</H1>

The Send 
Cancel
<!--chtml if pinemode="function_key"-->
(F3)
<!--chtml else-->
(^X) 
<!--chtml endif-->
command tells Pine you are finished composing.
Before actually sending it, though, Pine will ask you to confirm 
your intention, and, at the same time, redisplayed the message text
with the recipients at the top of the screen to give you the opportunity
to review and verify that the message is addressed to the people
you intended.

<P>
This confirmation prompt may also offer, depending
on your particular Setup/Config, options allowing you to set
<A HREF="h_config_compose_dsn">delivery status notifications</A>,
include attachments in the &quot;Fcc&quot; (if you had previously
specified that they <A HREF="h_config_no_fcc_attach">exclude attachments</A>, 
observe details of the
<A HREF="h_config_verbose_post">message submission process</A>,
or choose the utility though which the
<A HREF="h_config_sending_filter">outgoing text should first pass</A>.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_compose_markcutpaste =======
<HTML>
<HEAD>
<TITLE>Mark, Cut and Paste Commands</TITLE>
</HEAD>
<BODY>
<H1>Mark, Cut and Paste Commands</H1>

You can define a &quot;block&quot; of text, which can subsequently
 be deleted or
copied as a unit, by setting a mark at the start of the block (Ctrl-^) and
then moving the cursor to the end of the desired text block.  You can then
&quot;cut&quot; the block out 
<!--chtml if pinemode="function_key"-->
&quot;F9&quot;,
<!--chtml else-->
&quot;Ctrl-K&quot;,
<!--chtml endif-->
move the cursor, and &quot;paste&quot; it
<!--chtml if pinemode="function_key"-->
&quot;F10&quot;,
<!--chtml else-->
&quot;Ctrl-U&quot;,
<!--chtml endif-->
in the new location.  Also, you can paste more than once, allowing you
to use this feature to copy a block of text.<P>

If you press 
<!--chtml if pinemode="function_key"-->
&quot;F9&quot;
<!--chtml else-->
&quot;^K&quot;
<!--chtml endif-->
without having marked anything, Pine will delete
a single line.  If you delete a group of lines together, Pine keeps them
in the same buffer, so 
<!--chtml if pinemode="function_key"-->
F10
<!--chtml else-->
^U
<!--chtml endif-->
will restore them as a block.  About
terminology:  Mark is shown as &quot;^^&quot;.  The first &quot;^&quot; means you should
hold down the &quot;Control&quot; key on your keyboard.  The second &quot;^&quot; means
&quot;type the character ^&quot;.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_compose_justify =======
<HTML>
<HEAD>
<TITLE>Justify Command</TITLE>
</HEAD>
<BODY>
<H1>Justify Command</H1>

The Justify
<!--chtml if pinemode="function_key"-->
(F4)
<!--chtml else-->
(^J) 
<!--chtml endif-->
command reformats the text in the paragraph the cursor is in.
Paragraphs are separated by one blank line or a line beginning with a space.
This is useful when you have been editing a paragraph and the lines become
uneven.  The text is left aligned or justified and the right is ragged.  If
the text is already justified as typed with auto-wrap, no justification will
be done.

<P>
When composing a reply containing included text, the justify command
will reformat text to the right of the 
&quot;<A HREF="h_config_reply_indent_string">reply-indent-string</A>&quot;,
adding or removing indented lines as needed.  Paragraphs are separated
by a blank line, a line containing only the reply-indent-string, or a
line containing the indent string and one or more blank spaces.
Included text that was previously indented (or &quot;quoted&quot;) is
not preserved.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_compose_spell =======
<HTML>
<HEAD>
<TITLE>Spell Check Command</TITLE>
</HEAD>
<BODY>
<H1>Spell Check Command</H1>

The &quot;To Spell&quot;
<!--chtml if pinemode="function_key"-->
(F12)
<!--chtml else-->
(^T) 
<!--chtml endif-->
command calls an external spell checking program to look over the
message you are composing.  By default, Pine uses the simple Unix
spell checker.

<P>
Under the default configuration, there are no suggested alternative
spellings, but Pine
will show you the &quot;incorrect&quot; word and let you fix it or
move on.  If a word is misspelled more than once, then you will be
prompted to confirm the correction of each occurrence of it.  Lines
beginning with &quot;&gt; &quot; (included messages) will not be checked.

<P>
If your system has a spell checking utility that does offer alternatives
or otherwise improves on the default, the Setup/Config Menu's
&quot;<A HREF="h_config_speller">speller</A>&quot; option will tell
Pine to use it instead.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_compose_alted =======
<HTML>
<HEAD>
<TITLE>Alt Editor Command</TITLE>
</HEAD>
<BODY>
<H1>Alt Editor Command</H1>

The &quot;Alt Editor&quot; command's availability depends on the
Setup/Config variable &quot;<A HREF="h_config_editor">editor</A>&quot;.

<P>
When the variable specifies a valid editor on your system, this
command will launch it with the current text of your message
already filled in.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_compose_readfile =======
<HTML>
<HEAD>
<TITLE>Read File Command</TITLE>
</HEAD>
<BODY>
<H1>Read File Command</H1>

The &quot;Read File&quot;
<!--chtml if pinemode="function_key"-->
(F5)
<!--chtml else-->
(^R) 
<!--chtml endif-->
command allows you to copy in text from an existing file. You will be
prompted for the name of a file to be inserted into the message.  The file
name is relative to your home directory 
<!--chtml if pinemode="running"-->
(which, in the present configuration of your system, is
 &quot;<!--#echo var="HOME_DIR"-->&quot;) 
<!--chtml endif-->
or current working directory
<!--chtml if pinemode="running"-->
(which, at least for your current Pine &quot;session,&quot; 
is &quot;<!--#echo var="CURRENT_DIR"-->&quot;) 
<!--chtml endif-->, depending on the
<A HREF="h_config_use_current_dir">&quot;use-current-dir&quot;</A>
configuration setting; or, the file name must be specified as a full path name 
<!--chtml if pinemode="os_windows"-->
-- for example: &quot;A:&#92;PAPER.TXT&quot;
<!--chtml else-->
-- for example: &quot;/tmp/wisdom-of-the-day&quot;
<!--chtml endif-->
(without the quotation marks).

<P>
The file will be inserted where the cursor is located.  <B>The
file to be read must be on the same system as Pine.</B> If you use Pine on a
Unix machine but have files on a PC or Mac, the files must be transferred
to the system Pine is running on before they can be read.  Please ask your
local computer support people about the correct way to transfer a file to 
your Pine system.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_common_suspend =======
<HTML>
<HEAD>
<TITLE>Suspend Command</TITLE>
</HEAD>
<BODY>
<H1>Suspend Command</H1>

With the <A HREF="h_config_can_suspend">enable-suspend</A> feature
enabled, you can, at almost any time, temporarily halt your Pine session,
<!--chtml if pinemode="os_windows"-->
minimizing it into an icon.
<!--chtml else-->
and return to your system prompt.
<!--chtml endif-->

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_pipe_command =======
<HTML>
<HEAD>
<TITLE>Pipe Command SubOptions</TITLE>
</HEAD>
<BODY>
<H1>Pipe Command SubOptions</H1>

By default, when you use the Pipe command, the processed text of the
message is sent to the Unix command
you specify and the output is captured by Pine and shown to you.
There are some sub-commands which may be used to alter this behavior.
These are toggles which switch the behavior between two possibilities.
They can be combined in any way you wish.
They are:
<DL>
   <DT>Shown Text or Raw Text</DT>
   <DD>This option toggles between sending the shown (processed) text
of the message to the Unix command, and sending the
raw (unprocessed) text of the message to the Unix command.
The default is to send the shown text.
The raw version of the message will contain all of the headers and any
MIME encoding that the message contains.
You can experiment with this option by piping to something simple like the
Unix &quot;cat&quot; command.
   </DD>
   <DT>Captured Output or Free Output</DT>
   <DD>This option toggles between having Pine capture the output of
the Unix pipe command for display, and not capturing it.
If the command you are piping to is a filter which will produce output
you want to view, then you want to capture that output
for display (the default).
If the Unix command doesn't produce output or handles the display itself,
then you want free output.
   </DD>
   <DT>No Delimiter or With Delimiter</DT>
   <DD>This option controls whether or not a Unix mailbox style delimiter
will come before the text of the message.
This is the delmiter used in the common Unix mailbox format.
It's the single line which begins with the five characters
&quot;From&quot; followed by a &lt;SPACE&gt; character.
You'll usually only want to include this if the Unix command requires
input in the format of a traditional Unix mailbox file.
   </DD>
   <DT>To Same Pipe or To Individual Pipes</DT>
   <DD>This option only shows up if you are running an aggregate
pipe command.
That is, the command was Apply Pipe, not just Pipe.
You have the option of piping all of the selected messages through a
single pipe to a single instance of the Unix command,
or piping each individual message through a separate pipe to separate
instances of the Unix command.
The default is that all of the output will go through a single pipe
to a single instance of the command.
You can try this option with a command like &quot;less&quot;, with Free
Output enabled.
   </DD>
</DL>

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_simple_index ========================
<HTML>
<HEAD>
<TITLE>SELECT POSTPONED MESSAGE</TITLE>
</HEAD>
<BODY>
<H1>POSTPONED MESSAGE SELECTION COMMANDS</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Messages               General Pine Commands
-------------------------------               ---------------------
 F5   Move to previous message                 F1   Show this help text
 F6   Move to next message
 F7   Show previous screen of messages
 F8   Show next screen of messages

Message Selection Commands
--------------------------
 F3   Exit the Message Select menu (canceling Send command)
 F4   Select the currently highlighted message
 F9   Mark the currently highlighted message as deleted
 F10  Undelete (remove deletion mark from) the highlighted message
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Messages               General Pine Commands
-------------------------------               ---------------------
  P  Move to previous message                  ?  Show this help text
  N  Move to next message
  -  Show previous screen of messages
 Spc Show next screen of messages

Message Selection Commands
--------------------------
  E  Exit the Message Select menu (canceling Send command)
  S  Select the currently highlighted message
  D  Mark the currently highlighted message as deleted
  U  Undelete (remove deletion mark from) the highlighted message
</PRE>
<!--chtml endif-->
<P>
<H2>Description of the Select Postponed Message Screen</H2>

This screen allows you to select one of several previously postponed
messages in order to continue composition.  Your options are very limited
-- the screen is not meant to let you manipulate these messages.  However,
you may now delete messages from this list.  Once you choose a message,
Pine reads it in and puts you into the regular message composer.
<P>

Messages do not stay in this postponed state automatically.  If you select
a message and then want to postpone it again, use the normal postpone
(Ctrl-O) command in the composer.
<P>

If you exit this screen without selecting a message, the Compose command
which got you here is canceled.  Other than messages explicitly marked
&quot;Deleted&quot;, no messages will be removed.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_collection_screen ========================
<HTML>
<HEAD>
<TITLE>COLLECTION LIST screen</TITLE>
</HEAD>
<BODY>
<H1>COLLECTION LIST screen</H1>

The COLLECTION LIST screen is used to select one of your  
collection definitions to display the folders they contain.  See
<A HREF="h_what_are_collections">Folder Collections Explained</A> for 
detailed explanation of collections.<P>

To manage your collection definitions (Add, Change, Delete, etc.), use
the <A HREF="h_collection_maint">Setup/collectionList</A> command on Pine's
MAIN MENU.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_collection_maint ========================
<HTML>
<HEAD>
<TITLE>SETUP COLLECTION LIST screen</TITLE>
</HEAD>
<BODY>
<H1>SETUP COLLECTION LIST screen</H1>

The SETUP COLLECTION LIST screen lets you manage your collection
definitions.  See 
<A HREF="h_what_are_collections">Folder Collections Explained</A> 
for detailed explanation of collections.<P>

Maintenance commands include:
<DL>
<DT>Change
<!--chtml if pinemode="function_key"-->
(F4)
<!--chtml else-->
(C)
<!--chtml endif-->
</DT>

<DD>Modify attributes of the selected collection definition.

<DT>Add Cltn
<!--chtml if pinemode="function_key"-->
(F9)
<!--chtml else-->
(A)
<!--chtml endif-->
</DT>

<DD>Create a new collection definition.
</DD>

<DT>Del Cltn
<!--chtml if pinemode="function_key"-->
(F10)
<!--chtml else-->
(D)
<!--chtml endif-->
</DT>

<DD>Delete the selected collection definition.<BR>
NOTE: The folders and directories referred to by the
collection definition are <EM>NOT</EM> deleted.  Folders must
be deleted, if that's what you wish to do, from the 
<A HREF="h_folder_maint">FOLDER LIST screen</A>, which shows the 
individual folders in a collection.
</DD>

<DT>Shuffle
<!--chtml if pinemode="function_key"-->
(F11)
<!--chtml else-->
($)
<!--chtml endif-->
</DT>

<DD>Change the order of the displayed collections.  Pine will offer
to move the currently selected collection one position UP
or DOWN.
</DD>
</DL>

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============ h_what_are_collections ==========
<HTML>
<HEAD>
<TITLE>Folder Collections Explained</TITLE>
</HEAD>
<BODY>
<H1>Folder Collections Explained</H1>


Those of you with simple mail configurations will just see a list of all the
folders you have when choosing FOLDER LIST from Pine's MAIN MENU.  
The special folders for INBOX, sent mail and saved messages
will appear at the top of the list.  All others are in alphabetical order.
<P>
If you
or your system administrator have defined more than one collection or if
you have a collection (for newsgroups or email folders) defined on your 
system, then you will see the COLLECTION LIST screen first when choosing 
FOLDER LIST from Pine's MAIN MENU.  (This selection level is new in Pine 4.00; 
previous versions showed all folder 
collections on the FOLDER LIST screen, with a &quot;Select Here to See
Expanded List&quot; button to reveal the folders in them.)
<P>
<H2>Why have multiple folder collections?</H2>
<P>
For Pine users who only maintain email folders (and not too many) on one host, 
a single folder collection is probably sufficient.<P>

However, people who have more than one email account - for example, one 
at their university, and one with their personal Internet Service Provider - 
will have different sets of folders on different hosts, and they may want to
access them all from the same installation of Pine, rather than use different 
software and/or log into other hosts to manipulate messages in different 
accounts.  (If in doubt whether one of your email accounts can be accessed 
with Pine, contact the technical support people for that account.)  Even people
who have only one email account on one host, but have dozens or
hundreds of email folders, may want to arrange these folders together in a 
meaningful way.<BR>
That is where multiple collections come in.

<H2>Types of Collections</H2>
<DL>
<DT>INCOMING FOLDERS</DT>
<DD>&quot;Incoming Message Folders&quot; 
is a special collection typically used to supplement your single INBOX.  
All the folders here are meant to be ones that receive incoming messages, 
which you intend to check more or less frequently.  
You may have multiple folders like this because you or your systems 
administrator have set up an external program (because this is not a 
function of Pine!) to filter incoming 
email messages into different folders, based on certain criteria such as 
sender, recipient, or subject; or because you have multiple accounts and 
wish to check their INBOXes easily.  This collection is established by 
setting the 
<A HREF="h_config_enable_incoming">&quot;enable-incoming-folders&quot;</A>
feature in the SETUP CONFIGURATION screen, which is accessed from the 
MAIN MENU.
</DD>

<DT>NEWS</DT>
<DD>You can also define a collection specifically for
newsgroups.  Pine does this for you implicitly when you 
<A HREF="h_config_nntp_server">define an NNTP Server</A>
in your Pine configuration.  The news collection appears last in the 
COLLECTION LIST (though you can shuffle it up in the order of presentation),
and Pine knows not to save messages there.
</DD>

<DT>DEFAULT COLLECTION</DT>
<DD>This is the default collection for your saved and sent messages folders.
</DD>
</DL>

<P>

<H2>Defining Collections</H2>
<P>
In the absence of any folder-collection definitions, Pine will assume a
single default folder collection.
<!--chtml if pinemode="os_windows"-->
<!--chtml else-->
If necessary, Pine will create the directory
&quot;mail&quot; in your Unix home directory 
to hold your folders.
<!--chtml endif-->
<P>
You can use the 
<A HREF="h_collection_maint">Setup/collectionList screen</A>, called up from 
the MAIN MENU, to manage your collection list.  
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_role_select =====
<HTML>
<HEAD>
<TITLE>ROLES SCREEN</TITLE>
</HEAD>
<BODY>
<H1>ROLES SCREEN</H1>
<H2>ROLES COMMANDS</H2>
<!--chtml if pinemode="function_key"-->
<PRE>
Available  Commands                        
-------------------------------            
F1  Show Help Text
F3  Back to MAIN Pine menu
F4  Select a role to use in composition
F5  Move to previous role
F6  Move to next role
F7  Previous page of roles
F8  Next page of roles
F12 Whereis (search role nicknames)
</PRE>
<!--chtml else-->
<PRE>
Navigation                     General Pine Commands
-----------------------        ---------------------
 P  Prev Role                     ?  Display this help text
 N  Next Role                     E  Back to MAIN Pine menu
 -  Previous page
Spc Next page
 W  WhereIs (search for word in role nicknames)

Select Role Commands
------------------------------------------------
 C  Compose using highlighted role
</PRE>
<!--chtml endif-->

<H2>Description of the Roles Screen</H2>

With this screen you select a role to be used in the composition of a
message.
Use the Previous and Next commands to highlight the role you wish to
use.
When you type C you will be placed in the composer using the highlighted role.
<P>
You don't have any non-default <A HREF="h_role_config">roles</A>
available unless you set them up.
You may do so by using the Setup command on the main menu.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_role_config =====
<HTML>
<HEAD>
<TITLE>SETUP ROLES SCREEN</TITLE>
</HEAD>
<BODY>
<H1>SETUP ROLES SCREEN</H1>
<H2>SETUP ROLES COMMANDS</H2>
<!--chtml if pinemode="function_key"-->
<PRE>
Available  Commands -- Group 1         Available Commands -- Group 2   
-------------------------------        ------------------------------  
F1  Show Help Text                      F1  Show Help Text             
F2  See commands in next group          F2  See commands in next group
F3  Back to MAIN Pine menu
F4  Change configuration for role
F5  Move to previous role               F5  Include file in role config
F6  Move to next role                   F6  Exclude file from config
F7  Previous page of roles
F8  Next page of roles
F9  Add new role
F10 Delete existing role
F11 Shuffle the order of roles
F12 Whereis (search role nicknames)
</PRE>
<!--chtml else-->
<PRE>
Navigation                     General Pine Commands
-----------------------        ---------------------
 P  Prev Role                     ?  Display this help text
 N  Next Role                     E  Back to MAIN Pine menu
 -  Previous page
Spc Next page
 W  WhereIs (search for word in role nicknames)

Setup Roles Commands
------------------------------------------------
 A  Add new role                  $  Shuffle the order of roles
 D  Delete existing role          C  Change configuration for hilited role
 I  Include file in role config   X  Exclude file from role config
</PRE>
<!--chtml endif-->

<H2>Description of the Setup Roles Screen</H2>

This screen lets you add, delete, modify, or change the order of the rules
which determine the role you are playing when replying or forwarding
a message.
<P>
You may play different roles depending on who you are replying to.
For example, if you are replying to a message addressed to help-desk you
may be acting as a Help Desk Worker.
That role may require that you use a different return address and/or
a different signature.
<P>
Roles are optional.
If you set up roles they work like this:  Each role has a set of patterns
which are used to decide which role is used and a set of actions which
are taken when that role is used.
When you reply to a message, the recipients to which the
message you are replying was sent are compared with your role patterns.
The comparisons start with the first role rule and keep going until there is
a match.
If a match is found, the matching role's actions are taken.

<H2>Role Patterns</H2>

Each rule has six possible patterns called the To, From, Sender, Cc, News,
and Subject patterns.
In order for there to be a match, all six patterns must match the
corresponding fields in the replied-to message.
A blank pattern automatically counts as a match.
A pattern which isn't blank has to match at least one of the addresses
in its category (in the case of the five address patterns) to be considered
a match.
For example, if a role has a To pattern of &quot;address1&quot; then it is
considered a match if the message being replied to was sent to
&quot;address1&quot; and &quot;address2&quot;.
(If the message has a Resent-To header, the addresses there are used in place
of the addresses in the To header.
This is only true for the To header.
Resent-cc and Resent-From headers are never used.)
<P>
Patterns are simply strings which are searched for in the corresponding
header field.
Matching is always a substring match, matches don't have to be exact.
In other words, if a field has the text &quot;mailbox@domain&quot; in it,
then the patterns &quot;box&quot;, or &quot;x@d&quot;, or
&quot;mailbox@domain&quot; are all matches.
<P>
The empty pattern which you get by entering a pair of
double quotes (&quot;&quot;) should match any message which
has the corresponding field.
You could use this, for example, to define a default news role when
responding to a message sent to any news group.
You would put the empty pattern in the News pattern field.
Some IMAP servers may not consider an empty string a match.
If you find that this is happening to you, try putting in some other character
which is sure to be in the field you're searching.
For example, a News pattern equal to
<P>
<CENTER><SAMP>.</SAMP></CENTER>
<P>
should match any news group, since all news groups have dots in their names.
And a To pattern consisting of
<P>
<CENTER><SAMP>@</SAMP></CENTER>
<P>
should match any message which you received by email.
<P>
Since patterns which are blank are considered matches, a role
which has all six patterns blank can be used as a default role.
It should be put last in the list of role rules since the matching
starts at the beginning and proceeds until one of the rules is a match.
If no rules at all match, then Pine will
use its regular methods of defining the role.
<P>
If there is more than one pattern for which you want to take the
same action there is a shorthand notation which may be used.
Any of the patterns may be a comma-separated list of patterns instead of
just a single pattern.
If any of the patterns in the list match any of the addresses in the message
then it is considered a match.
For example, if &quot;company1&quot; and &quot;company2&quot; both required
you to use the same role when replying to messages, you might have
a To pattern which looks like
<P>
<CENTER><SAMP>company1.com,company2.com</SAMP></CENTER>
<P>
That means that if the mail you are replying to was addressed to
either &quot;anything@company1.com&quot; or &quot;anything@company2.com&quot;,
then the same actions would be taken.
Note that this is <EM>NOT</EM> a way to specify that you want to
match an address in <EM>either</EM> the To field <EM>or</EM> the Cc field.
To do that you'll need to define two separate roles, one for the To field
match and another for the Cc field match.
You may find that the field called
&quot;Initialize settings using role&quot; is useful in this case.
(You'll see that field when editing a role. It's right above the &quot;Set
From&quot; line.)
That allows you to put the role's actions in one role and then refer to
them from another with just the nickname of the first role.
It's just a way to avoid entering the same actions twice.

<H2>Role Actions</H2>

Once a role match is found, the role's actions are taken.
For each role there are four possible actions that may be defined.
They are actions to set the From address, the Fcc, the Signature file,
and the Template file.
<P>
The From address is the address used on the From line of the message
you are sending.
<P>
The Fcc is used as the Fcc for the message you are sending.
<P>
The Sig is the name of a file to be used as the signature file when
this role is being used.
If the name of the file has a vertical bar following it (|)
then it is assumed that the file is a program that should be run to
produce the signature.
<P>
A Template is the name of a file to be included in the message when this
role is being used.
If the name of the file has a vertical bar following it (|)
then it is assumed that the file is a program that should be run to
produce the template.
Both signature files and template files (or the output of signature programs
and template file programs) may contain special tokens
which are replaced with contents
which depend on the message being replied to or forwarded.
See the help for the individual fields inside the role editor for more
information on template tokens.
<P>
If any of the actions are left blank, then the action depends on what
is present in the &quot;Initialize settings using role&quot; field.
If you've listed the nickname of another one of your roles there, then the
corresponding action from that role will be used here.
If that action is also blank, or if there is no nickname specified,
then Pine will do whatever it normally does to set these actions.
This depends on other configuration options and features you've set.
<P>
The Add command is used to add a new role definition to your set of
role rules.
The new role will be added before the highlighted role.
The Del command deletes the currently highlighted role.
The Change command lets you edit the nickname, patterns, and actions of the
currently highlighted role.
<P>
The Shuffle command allows you to change the order of the roles.
You may move the currently highlighted role up or down in the list.
The order of the roles is important since the roles are tested for a
match starting with the first role and continuing until a match is found.
You should place the roles with more specific patterns near the beginning
of the list, and those with more general patterns near the end so that
the more specific matches will happen when appropriate.
<P>
The IncludeFile command allows you to add a roles file to your configuration.
Usually, your roles will be contained in your Pine configuration file.
If you wish, some or all of your roles may be stored in a separate file.
If a roles file already exists (maybe it was made by somebody else using
Pine), you may insert it before the currently highlighted role rule.
You may also insert an empty file or a file which does not yet exist.
Once you have an empty roles file in your configuration, you may use
the Shuffle command to move roles into it.
The eXcludeFile command removes the roles file from your roles configuration.
(In order to exclude a roles file that file must have at least one role
in it, otherwise you won't be able to highlight a line in the file.)
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_direct_config =====
<HTML>
<HEAD>
<TITLE>SETUP LDAP DIRECTORY SERVERS SCREEN</TITLE>
</HEAD>
<BODY>
<H1>SETUP LDAP DIRECTORY SERVERS SCREEN</H1>
<H2>SETUP LDAP DIRECTORY SERVERS COMMANDS</H2>
<!--chtml if pinemode="function_key"-->
<PRE>
Available  Commands                        
-------------------------------            
F1  Show Help Text                         
F3  Back to MAIN Pine menu                 
F4  Change configuration for directory server  
F5  Move to previous directory server          
F6  Move to next directory server              
F7  Previous page of directory servers         
F8  Next page of directory servers
F9  Add new directory server
F10 Delete existing directory server
F11 Shuffle the order of directory servers
F12 Whereis (search directory server titles)   
</PRE>
<!--chtml else-->
<PRE>
Navigation                     General Pine Commands
-----------------------        ---------------------
 P  Prev Directory Server         ?  Display this help text
 N  Next Directory Server         E  Back to MAIN Pine menu
 -  Previous page
Spc Next page
 W  WhereIs (search for word in directory server titles)

Setup LDAP Directory Server Commands
------------------------------------------------
 A  Add new directory server      $  Shuffle the order of directory servers
 D  Delete existing dir server    C  Change configuration for hilited server
</PRE>
<!--chtml endif-->

<H2>Description of the Setup LDAP Directory Servers Screen</H2>

This screen lets you add, delete, modify, or change the order of your
directory servers. You may also set some optional behavior for each server.
The &quot;Add Dir&quot; command brings up a blank form to 
fill in. You will have to supply at least the name of the LDAP server.
You will often have to supply a search base to be used with that server,
as well. Once the form has been brought up on your screen, there is help
available for each of the options you may set.
<P>
The &quot;Del Dir&quot; command allows you to remove a directory server
from your configuration.
<P>
The &quot;Change&quot; command is similar to the &quot;Add Dir&quot; command.
The difference is that instead of bringing up a form for a new server
configuration, you are changing the configuration of an existing entry.
For example, you might want to correct a typing error, change a
nickname, or change one of the options set for that server.
<P>
The &quot;Shuffle&quot; command is used to change the order of directory
servers.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_address_selection ========================
<HTML>
<HEAD>
<TITLE>SEARCH RESULTS INDEX</TITLE>
</HEAD>
<BODY>
<H1>SEARCH RESULTS INDEX</H1>
This screen shows the results, if any, of your Directory Server search.  
Commands (besides those for screen navigation) are:
<DL>
<DT>View
<!--chtml if pinemode="function_key"-->
(F4)
<!--chtml else-->
(V)
<!--chtml endif-->
</DT>
<DD>See the full information for the selected entry.

<DT>Compose
<!--chtml if pinemode="function_key"-->
(F9)
<!--chtml else-->
(C)
<!--chtml endif--></DT>
<DD>Compose a message with the selected entry as the recipient.

<DT>Forward
<!--chtml if pinemode="function_key"-->
(F10)
<!--chtml else-->
(F)
<!--chtml endif--></DT>
<DD>Send the full information for the selected entry as an 
email message to someone else.

<DT>Save
<!--chtml if pinemode="function_key"-->
(F11)
<!--chtml else-->
(S)
<!--chtml endif-->
</DT>
<DD>Save to your address book:
<UL>
<LI>the result of the search (as just found through your query) for the 
selected entry; or 
<LI>the selected entry for repeated Directory Server searching when used 
in the future.
</UL>
or<BR>
Export to a file (external to Pine):
<UL>
<LI>the full information for the selected entry; or
<LI>the email address from the selected entry; or
<LI>the selected entry in <A HREF="h_whatis_vcard">vCard</A> format.
</UL>
<DT>WhereIs
<!--chtml if pinemode="function_key"-->
(F12)
<!--chtml else-->
(W)
<!--chtml endif-->
</DT>
<DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the 
displayed text, not the full records for each entry.)  
</DL>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_folder_maint =====
<HTML>
<HEAD>
<TITLE>Help for Folder List</TITLE>
</HEAD>
<BODY>
<H1>FOLDER LIST COMMANDS</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
Available Commands -- Group 1        Available Commands -- Group 2
-------------------------------      ------------------------------
F1  Show Help Text                    F1  Show Help Text               
F2  See commands in next group        F2  See commands in next group  
F3  MAIN MENU Screen                  F3  Quit Pine                    
F4  Select folder and view it         F4  Compose a message            
F5  Move to previous folder
F6  Move to next folder               F6  Specify a folder to go to
F7  Show previous screen of listing   F7  Show MESSAGE INDEX of current folder
F8  Show next screen of listing       F8  Whereis (search folder names)
F9  Delete selected folder            F9  Print folder listing
F10 Add a new folder
F11 Rename selected folder
</PRE>
<!--chtml else-->
<PRE>
Navigating the Folder Screen            Operations on the Selected Folder
----------------------------            ---------------------------------
 P   Move to previous folder              V  View Index of selected folder
 N   Move to next folder                  D  Delete
 -   Show previous page of listing        R  Rename
Spc  Show next page of listing

FOLDER LIST Screen Commands              General Pine Command
---------------------------              ---------------------
 A  Add a folder                          O  Show all other available commands
 G  Specify a folder to go to             ?  Show Help text
 I  Show MESSAGE INDEX of current folder  M  MAIN MENU Screen
 W  Whereis (search folder names)         Q  Quit Pine
 %  Print folder listing                  C  Compose a message
</PRE>
<!--chtml endif-->
These commands are only available in the FOLDER LIST screen if the 
<A HREF="h_config_enable_agg_ops">&quot;enable-aggregate-command-set&quot; 
feature</A> is set in the SETUP CONFIGURATION screen:<DL>
<DT>Select:</DT>
<DD>Select folders by certain criteria:<UL>
<LI>All: of limited use, since there is no Apply command.
<LI>by Property: <UL>
	<LI>folder contains messages not yet seen 
	<LI>folder contains new messages
	<LI>folder contains exactly as many, more, or fewer messages 
than a given number
	</UL>
<LI>by Text: <UL>
	<LI>contained in name of folder (Name Select)
	<LI>contained in messages in folder (Content Select)
	</UL>
</UL></DD>

<DT>Select current:</DT>
<DD>Select the folder the cursor is on.  (Can be used to &quot;manually&quot; 
add one or more folders to a set created with the Select command described 
above.)</DD>
<DT>Zoom mode:</DT>
<DD>Toggles display of only selected folders or all folders on and off.</DD>
</DL>
<!-- In all folder collections except Incoming-Folders:
However, once you go to a folder's MESSAGE INDEX screen, the selection you 
made in the FOLDER LIST screen is no longer retained.  -->
<P>
<CENTER>Description of the FOLDER LIST Screen</CENTER>

The purpose of the FOLDER LIST screen is to help you browse and manage
the folders and directories (also known as &quot;hierarchy&quot;)
contained within a collection.

<P>
Folders and directories are arranged alphabetically across lines of
the screen.  Directories, if present, are denoted by a special
character at the end of the name known as the hierarchy delimiter
(typically, &quot;/&quot;).  By default, folders and directories are
mixed together.  The
"<A HREF="h_config_fld_sort_rule">Folder-Sort-Rule</A>"
configuration option can be used to group directories toward the 
beginning or end of the list.

<P>
The Next/Prev Page commands help browse the list, the Next/Prev Fldr
commands change the &quot;selected&quot; (i.e., highlighted) folder or
directory, and the View Fldr/Dir commands will &quot;open&quot; the
selected item.  Folder and directory management is provided via the
Rename, Delete and Add commands.

<P><CENTER>About Folders</CENTER>
What are Folders?<P>

Folders are simply files where messages are kept.  Every message has to be
in a folder.  Most every Pine user starts out with 3 folders: an INBOX, a
folder for sent mail and a folder for saved messages.<P>

You may create as many other folders as you wish.  They must be given
names that can be filenames on the filesystem.  
<!--chtml if pinemode="os_windows"-->
Normally PC-Pine folders are
automatically given the filename extension &quot;.MTX&quot; (which stands
for Mailbox-text).  The extension is suppressed from FOLDER LIST
displays, and should not be entered when typing a folder name at a
Save or Goto prompt.  The use of the MTX extension can be overridden
by the Setup/Configuration option 
<A HREF="h_config_folder_extension">folder-extension</A>, 
which may be useful when accessing
saved-message folders on a Unix host via SMB or NFS.  PC-Pine can
understand the normal Unix mail folder format, but can only open those
folders READ-ONLY.
<!--chtml else-->
<!--chtml endif-->
<P>

You can move messages from one folder to another by opening the original
folder and saving messages into the other folder just as you can save
message from your INBOX to any other folder.<P>

Folders are typically just files in the filesystem.  However, the files
which are
folders have some special formatting in them (so that Pine knows where one
message ends and another begins) and should <EM>not</EM> be edited outside of
Pine.  If you want copies of your messages in text files that you can edit
or otherwise manipulate, use the Export command to copy them from Pine into
your regular file area.

<P>
FOR MORE INFORMATION: See the section on
<A HREF="h_valid_folder_names">Valid Folder Names</A>.
<P>
<CENTER>About Directories</CENTER>
<P>
A directory is simply a container used to group folders within a
folder list.  You can create as many directories as you like.  And 
directories can even contain directories themselves.

<P>
SPECIAL NOTES: When accessing folders on an IMAP server, it is important
to note that not all IMAP servers support directories.  If you find that
the Add command fails to offer the &quot;Create Directory&quot; subcommand,
then it's likely that directories are not supported by the server serving
in that collection.

<P>
Similarly, servers that do provide for directories may not do so in
the same way.  On some servers, for example, each folder name you
create is at the same time capable of being a directory.  When this
happens, Pine will display both the folder name and the name of the
directory (with trailing hierarchy delimiter) in the folder list.

<P>
Another issue with IMAP access, though with a much smaller set of servers,
is that not all servers accept the request to list out the available
folders and directories in the same way.  If you find yourself having
trouble viewing folders on your server, you might investigate the
&quot;<A HREF="h_config_lame_list_mode">enable-lame-list-mode</A>&quot;
feature.
<P>
<UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
========= h_valid_folder_names ========
<HTML>
<HEAD>
<TITLE>Explanation of Valid Folder Names</TITLE>
</HEAD>
<BODY>
<H1>Folder Name Syntax Explained</H1>

Once your folder collections are defined, you can usually refer to
folders by their simple (unqualified) name, or pick from a FOLDER LIST
display.  However, understanding the complete syntax for folder names,
both local and remote, is handy when using the Goto command and when
you are adding new folder collections via the Setups/collectionList screen.

<P>
Local folder names depend on the operating system used by the computer 
running Pine, as well as the configuration of that system.  For example,
&quot;C:&#92;PINE&#92;FOLDERS&#92;OCT-94&quot; might exist on a PC, and
&quot;~/mail/september-1994&quot; might be a reasonable folder name on Unix.
<!--chtml endif-->

<P>
Pine users have the option of using folders which are stored on some other
computer.  Pine accesses remote folders via IMAP (the Internet Message
Access Protocol), or in the case of news, via NNTP (the Network News
Transport Protocol).  To be able to access remote folders in Pine, the
remote host must be running the appropriate server software (imapd or
nntpd) and you must correctly specify the name of the folder to Pine,
including the domain name of the remote machine. For example,
<P>
<CENTER><SAMP>&#123;monet.art.nowhere.edu}INBOX</SAMP></CENTER>
<P>
could be a remote folder specification, and so could
<P>
<CENTER><SAMP>&#123;unixhost.art.nowhere.edu}~/mail/september-1994</SAMP></CENTER>
and
<P>
<CENTER><SAMP>&#123;winhost.art.nowhere.edu}&#92;mymail&#92;SEP-94</SAMP></CENTER>
<P>
Note that in the case of remote folders, the directory/file path in the specification is 
determined by the operating system of the remote computer, <B>not</B> by
the operating system of the computer on which you are running Pine.
<P>
As you can tell, the name of the computer is in &#123;} brackets
followed immediately by the name of the folder.  If, as in these
examples, there is no remote access protocol specified, then IMAP is
assumed.  See the Setup/collectionList Add or Change command's
<A HREF="h_composer_cntxt_server">Server:</A>
help text for a more detailed look at what options can be placed
between the brackets.

<P>
To the right of the brackets when a server name is present, or at the
start of the foldername if no server is present, the sharp sign,
&quot;#&quot;, holds special meaning.  It indicates a folder name
outside the area reserved for your personal folders.  In fact, it's
used indicate that both the name of the folder, and a special phrase
telling Pine how to interpret the name follows.

<P>
So, for example, Pine can be used to access a newsgroup that might be 
available on your computer using:
<P>
<CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
<P>
The sharp sign indicates the folder name is outside your personal
folder area.  The &quot;news.&quot; phrase after it tells Pine to 
interpret the remainder of the name as a newsgroup.

<P>
Similarly, to access a newsgroup on your IMAP server, you might
use something like:
<P>
<CENTER><SAMP>&#123;wharhol.art.nowhere.edu}#news.comp.mail.misc</SAMP></CENTER>

<P>
There are a number of such special phrases (or &quot;namespaces&quot;)
available.  For a more detailed explanation see the Setup/collectionList
Add or Change command's <A HREF="h_composer_cntxt_path">Path:</A> help text.

<P>
Note that &quot;INBOX&quot; has special meaning in both local and remote folder
names.  The name INBOX refers to your &quot;principal incoming
message folder&quot; and will be mapped to the actual file name used for your
INBOX on any given host.  Therefore, a name like
&quot;&#123;xxx.art.nowhere.edu}INBOX&quot; refers to whatever file is used to
store incoming mail for you on that particular host.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_whatis_vcard ========================
<HTML>
<HEAD>
<TITLE>VCARD EXPLAINED</TITLE>
</HEAD>
<BODY>
<H1>What is the vCard format?</H1>
A &quot;vCard&quot; is a sort of electronic business card, for exchanging 
information about and among people and organizations electronically.  
More information about vCard can be found (as of May 1998) on the WWW site 
of the Internet Mail Consortium at the URL:
<P>
<CENTER><A HREF="http://www.imc.org/pdi/">http://www.imc.org/pdi/</A></CENTER>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_folder_open =====
<HTML>
<HEAD>
<TITLE>Explanation of Folder Selection</TITLE>
</HEAD>
<BODY>
<BR>
<BR>
This screen is designed to allow you to quickly and easily survey your
folders and select one to open.
<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Folders             General Pine Commands
------------------------------             ---------------------
 P   Move to previous folder               ?   Show this help text
 N   Move to next folder
 -   Show previous screen of folders
Spc  Show next screen of folders
 W   WhereIs (search folder names)

Folder Selection Commands
-------------------------
 E   Exit the Folder Select menu (without selecting a folder)
 S   Select the currently highlighted folder
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Folders             General Pine Commands
------------------------------             ---------------------
F5   Move to previous folder               F1  Show this help text
F6   Move to next folder
F7   Show previous screen of folders
F8   Show next screen of folders
F12  WhereIs (search folder names)

Folder Selection Commands
-------------------------
F3   Exit the Folder Select menu (without selecting a folder)
F4   Select the currently highlighted folder
</PRE>
<!--chtml endif-->
<P>
FOR MORE INFORMATION: See the section on
<A HREF="h_valid_folder_names">Valid Folder Names</A>.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_folder_subscribe =====
<HTML>
<HEAD>
<TITLE>Newsgroup Subcribe Screen explained</TITLE>
</HEAD>
<BODY>
<H1>FOLDER SUBSCRIBE HELP</H1>

This screen is designed to help you subscribe to newsgroups you are
not currently subscribed to.  The screen display is a list of all
available newsgroups (or possibly a partial list if you specified a
partial name when entering the screen).  Groups you have already
subscribed to have the letters &quot;SUB&quot; next to them.  You may
select a single new group to subscribe to by moving the cursor to that
group and pressing &quot;S&quot; or carriage return.  Alternatively,
you may change into ListMode with the &quot;ListMode&quot; command.
The display will change slightly so that each group has a checkbox in
front of it.  Use the cursor and the Set/Unset command to place an
&quot;X&quot; in front of each newsgroup you wish to subscribe to.
<P>

When you are finished marking groups, the &quot;Subscribe&quot;
command will subscribe you to those groups you have marked.  Note, you
may not unsubscribe to groups with this command.  Instead of the
&quot;A&quot; &quot;Subscribe&quot; command, use the &quot;D&quot;
UnSbscrbe command.
<P>

<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Newsgroups          General Pine Commands
---------------------------------          ---------------------
F5   Move to previous group                F1   Show this help text
F6   Move to next group
F7   Show previous screen of groups
F8   Show next screen of groups
F12  WhereIs (search group names)
F9   Use ListMode

Group Selection Commands
-------------------------
F3  Exit the News Subscribe menu (without selecting any groups)
F4  Subscribe to the currently highlighted newsgroup
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Newsgroups          General Pine Commands
---------------------------------          ---------------------
 P   Move to previous group                ?   Show this help text
 N   Move to next group
 -   Show previous screen of groups
Spc  Show next screen of groups
 W   WhereIs (search group names)
 L   Use ListMode

Group Selection Commands
-------------------------
 E   Exit the News Subscribe menu (without selecting any groups)
 S   Subscribe to the currently highlighted newsgroup
</PRE>
<!--chtml endif-->
<P>
When in ListMode, there is an additional command for marking groups to
subscribe to:
<P>
<!--chtml if pinemode="function_key"-->
<PRE>
ListMode Commands
-------------------------
F9  Set or unset the highlighted group
</PRE>
<!--chtml else-->
<PRE>
ListMode Commands
-------------------------
X   Set or unset the highlighted group
</PRE>
<!--chtml endif-->
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_folder_postnews =====
<HTML>
<HEAD>
<TITLE>Newsgroup selecting for Posting explained</TITLE>
</HEAD>
<BODY>
This screen is designed to allow you to quickly and easily survey
the available newsgroups and select one to post news to.
<P>
<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Newsgroups          General Pine Commands
---------------------------------          ---------------------
F5   Move to previous group                F1  Show this help text
F6   Move to next group
F7   Show previous screen of groups
F8   Show next screen of groups
F12  WhereIs (search group names)

Group Selection Commands
-------------------------
F3   Exit the Selection menu (without selecting a group)
F4   Select the currently highlighted newsgroup
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Newsgroups          General Pine Commands
---------------------------------          ---------------------
 P   Move to previous group                ?  Show this help text
 N   Move to next group
 -   Show previous screen of groups
Spc  Show next screen of groups
 W   WhereIs (search group names)

Group Selection Commands
-------------------------
 E   Exit the Selection menu (without selecting a group)
 S   Select the currently highlighted newsgroup
</PRE>
<!--chtml endif-->
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_folder_save =====
<HTML>
<HEAD>
<TITLE>Folder Select for Save Explained</TITLE>
</HEAD>
<BODY>
This screen is designed to allow you to quickly and easily survey your
folders and select one to use for saving the current message.
<P>

<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Folders             General Pine Commands
------------------------------             ---------------------
F5   Move to previous folder               F1  Show this help text
F6   Move to next folder
F7   Show previous screen of folders
F8   Show next screen of folders
F12  WhereIs (search folder names)

Folder Selection Commands
-------------------------
F3   Exit the Folder Select menu (without selecting a folder)
F4   Select the currently highlighted folder
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Folders             General Pine Commands
------------------------------             ---------------------
 P   Move to previous folder               ?  Show this help text
 N   Move to next folder
 -   Show previous screen of folders
Spc  Show next screen of folders
 W   WhereIs (search folder names)

Folder Selection Commands
-------------------------
 E   Exit the Folder Select menu (without selecting a folder)
 S   Select the currently highlighted folder
</PRE>
<!--chtml endif-->
<P>
FOR MORE INFORMATION: See the section on
<A HREF="h_valid_folder_names">Valid Folder Names</A>.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_folder_fcc =====
<HTML>
<HEAD>
<TITLE>Folder Select for Fcc Explained</TITLE>
</HEAD>
<BODY>
This screen is designed to allow you to quickly and easily survey your
folders and select one to use as the file carbon copy (fcc) for the
current message.
<P>

<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Folders             General Pine Commands
------------------------------             ---------------------
F5   Move to previous folder               F1  Show this help text
F6   Move to next folder
F7   Show previous screen of folders
F8   Show next screen of folders
F12  WhereIs (search folder names)

Folder Selection Commands
-------------------------
F3   Exit the Folder Select menu (without selecting a folder)
F4   Select the currently highlighted folder
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Folders             General Pine Commands
------------------------------             ---------------------
 P   Move to previous folder               ?  Show this help text
 N   Move to next folder
 -   Show previous screen of folders
Spc  Show next screen of folders
 W   WhereIs (search folder names)

Folder Selection Commands
-------------------------
 E   Exit the Folder Select menu (without selecting a folder)
 S   Select the currently highlighted folder
</PRE>
<!--chtml endif-->
<P>
FOR MORE INFORMATION: See the section on
<A HREF="h_valid_folder_names">Valid Folder Names</A>.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_abook_config =====
<HTML>
<HEAD>
<TITLE>SETUP ADDRESS BOOKS SCREEN</TITLE>
</HEAD>
<BODY>
<H1>SETUP ADDRESS BOOKS SCREEN</H1>
<H2>SETUP ADDRESS BOOKS COMMANDS</H2>
<!--chtml if pinemode="function_key"-->
<PRE>
Available  Commands                        
-------------------------------            
F1  Show Help Text                         
F3  Back to MAIN Pine menu                 
F4  Change configuration for address book  
F5  Move to previous address book          
F6  Move to next address book              
F7  Previous page of address books         
F8  Next page of address books             
F9  Add new address book                   
F10 Delete existing address book           
F11 Shuffle the order of address books     
F12 Whereis (search address book titles)   
</PRE>
<!--chtml else-->
<PRE>
Navigation                     General Pine Commands
-----------------------        ---------------------
 P  Prev Address Book             ?  Display this help text
 N  Next Address Book             E  Back to MAIN Pine menu
 -  Previous page
Spc Next page
 W  WhereIs (search for word in address book titles)

Setup Address Books Commands
------------------------------------------------
 A  Add new address book          $  Shuffle the order of address books
 D  Delete existing address book  C  Change configuration for address book
</PRE>
<!--chtml endif-->

<H2>Description of the Setup Address Books Screen</H2>

This screen lets you add, delete, modify, or change the order of your
address books.  The &quot;Add Abook&quot; command brings up a blank form to 
fill in.  If you are adding a remote address book on an IMAP server
you should fill in the name of the IMAP server.  Otherwise, leave
that field blank.  (Note that remote IMAP address books are a Pine
concept and are unlikely to interoperate with other mail clients.)
For a remote address book, fill in the name of the remote folder
in the Folder field.  This should be a folder which is used only for
this one purpose, not a general purpose folder you expect to store
messages in.
<P>If you are adding a local address book, fill in the
Folder Name field with a local file name (e.g., .addressbook).
<P>
<B>Please note:</B> Remote address books stored on an IMAP server are 
of an entirely different format (namely, a special-purpose 
&quot;mail folder&quot;) than that of the local addressbook familiar 
to Pine users.  Therefore, 
you cannot use &quot;add a remote address book&quot; to make an existing 
Pine .addressbook file you may have on a remote IMAP server accessible to 
Pine running on a different host.  
<P>

The &quot;Del Abook&quot; command allows you to remove an address book
from your configuration.  It will also ask you if you wish to remove
the data for that address book, which would erase all traces of the
address book if you answer Yes.
<P>

The &quot;Change&quot; command is similar to the &quot;Add Abook&quot; command.
The difference is that instead of adding a new address book to your
configuration, you are changing the configuration of an existing entry.
For example, you might want to correct a typing error or change a
nickname.  The &quot;Change&quot; command is not a move command.  If you
change the folder name or server name the data will not be moved for you.
<P>

The &quot;Shuffle&quot; command is used for two purposes.  If you shuffle
an address book toward another address book in the same group then
the order of those two address books will be swapped.  If you shuffle
the last Personal address book down towards the Global address book
section, it will become a Global address book.  If you shuffle
the first Global address book up it will become a Personal address
book.  The main difference between Personal and Global address
books is that Global address books are forced read-only.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_abook_top =====
<HTML>
<HEAD>
<TITLE>ADDRESS BOOK LIST COMMANDS</TITLE>
</HEAD>
<BODY>
<H1>ADDRESS BOOK LIST COMMANDS</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
Available  Commands -- Group 1         Available Commands -- Group 2
-------------------------------        ------------------------------
F1  Show Help Text                      F1  Show Help Text
F2  See commands in next group          F2  See commands in next group
F3  Exit to Main Menu                   F3  Quit Pine
F4  View/Edit selected address book
F5  Move to previous address book       F5  FOLDER LIST screen
F6  Move to next address book           F6  Specify a folder to go to
F7  Previous page                       F7  MESSAGE INDEX screen
F8  Next page                           F9  Print list of address books
F12 Whereis (search for word)
</PRE>
<!--chtml else-->
<PRE>
Navigation                       General Pine Commands
-----------------------          ---------------------
 P  Previous Entry                ?  Display this help text
 N  Next Entry                    O  Show all other available commands
 -  Previous page                 &lt;  Back to MAIN Pine menu
Spc Next page                     Q  Quit Pine
 W  WhereIs (search for word)     L  FOLDER LIST screen
				  G  Specify a folder to go to
Address Book Commands             I  MESSAGE INDEX screen
------------------------------------------------
 &gt;  View/Edit selected address book
	      or
 &gt;  Search on selected directory server

 %  Print list of address books and directory servers
</PRE>
<!--chtml endif-->

<H2>Description of the Address Book List Screen</H2>

From this screen you may choose which address book you wish to view
or edit. For more information on address books, view one of your
address books (with
<!--chtml if pinemode="function_key"-->
F4
<!--chtml else-->
&quot;&gt;&quot;
<!--chtml endif-->)
and see the Help Text there.<P>

You may also choose a directory server on which to search for entries.
You do that by highlighting the directory server line and using
<!--chtml if pinemode="function_key"-->
F4
<!--chtml else-->
&quot;&gt;&quot;
<!--chtml endif-->.<P>

If you wish to define new address books or directory servers go to the Main
menu and choose Setup. You may then either choose to setup AddressBooks or
Directory (among other things). It's possible that the Directory option
will not be there if the Pine you are using does not contain LDAP directory
lookup functionality.

<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_abook_opened =====
<HTML>
<HEAD>
<TITLE>THE PINE ADDRESS BOOK</TITLE>
</HEAD>
<BODY>
<H1>THE PINE ADDRESS BOOK</H1>
<H2>ADDRESS BOOK COMMANDS</H2>
<PRE>
<!--chtml if pinemode="function_key"-->
Available  Commands -- Group 1         Available Commands -- Group 2   
-------------------------------        ------------------------------  
F1  Show Help Text                      F1  Show Help Text             
F2  See commands in next group          F2  See commands in next group
F3  Exit this screen                    F3  Quit Pine                  
F4  View/Edit selected entry            F4  Go to MAIN menu screen     
F5  Move to previous entry              F5  FOLDER LIST screen         
F6  Move to next entry                  F6  Specify a folder to go to  
F7  Previous page of address book       F7  MESSAGE INDEX screen        
F8  Next page of address book           F8  Copy entries to an addrbook
F9  Add new entry to address book       F9  Print address book         
F10 Delete selected entry               F10 TakeAddr to another addrbook
F11 Compose to selected entry           F11 Export entry to a file      
F12 Whereis (search address book)       F12 Forward entry by mail       

Available Commands -- Group 3                                           
------------------------------                                          
F3  Select                              F6  Zoom (or unZoom)            
F5  Select Current                      F7  Apply Command to Selection  
<!--chtml else-->
Address Book Navigation        General Pine Commands
-----------------------        ---------------------
 P  Prev Address                  ?  Display this help text
 N  Next Address                  O  Show all other available commands
 -  Previous page of address book M  Back to MAIN menu
Spc Next page of address book     Q  Quit Pine
 W  WhereIs (search for word      C  Compose message to selected addr
     or name in address book)     L  FOLDER LIST screen
 &lt;  To List of Address Books if   G  Specify a folder to go to
     more than one, else to MAIN  I  MESSAGE INDEX screen

Address Book Commands
----------------------------------------------------
 &gt;  View/Update selected entry    D  Delete selected entries
 %  Print address book            S  Save or Export address book selections
 F  Forward entries by mail       @  Add new entry to address book

 ;  Select command                Z  Toggle Zoom Mode
 :  Select highlighted entry      A  Apply command to selected entries

<!--chtml endif-->
</PRE>
Note:  The presence or absence of the final four commands above is
controlled by the option 
<A HREF="h_config_enable_agg_ops">&quot;enable-aggregate-command-set&quot;</A>
which you may turn on in the SETUP CONFIGURATION screen.
<P>

<H2>Description of the Address Book Screen</H2>

This screen lets you edit and manage entries in your address book.  It
also acts as a short-cut for composing messages to people in the address
book.  When, from this screen, you press <!--chtml if pinemode="function_key"-->F11<!--chtml else-->&quot;C&quot;<!--chtml endif--> for ComposeTo, the
message starts &quot;pre-addressed&quot; to whatever address book entry is
currently selected.
<P>
Pine's address book helps you keep a list of addresses you send email to so
you do not have to remember addresses that are often complex.  Each entry
in the address book has five fields, all of them optional.  The three
elements which are usually visible on the ADDRESS BOOK display, are: <DL>

	<P><DT>NICKNAME: <DD>A short easy-to-remember label to identify the entry.
	This is what you type in as you are addressing the message in the
	composer.  If there is a matching entry in your address book(s),
	Pine will extract the corresponding FullName and Address fields to
	generate the actual address for your message.

	<P><DT>FULLNAME: <DD>A longer field where you can put the full name 
of the
	person or organization.  Usually the full names are put in last
	name first so they sort nicely in alphabetical order.  Whatever
	you put as the name here will appear on the message when it is
	finally delivered.  Examples:<PRE>
	   Garcia Marquez, Gabriel
	   Henscheid, Eckhard
	   Pine-Info mailing list
	   Library materials renewal requests
	   Kim An-guk
	   &quot;George III, King of Great Britain, 1738-1820&quot;
</PRE>
(In the second-to-last example, no comma is used in the name so that 
the family name appears first in the address book and when the entry is 
used in the composer.
In the last example, retaining the commas is intended; 
double-quotation marks surround the name to 
prevent the transposition of its parts when the entry is used in 
the composer.)

	<P><DT>ADDRESS: <DD>This is the actual email address itself.  This must be
	a valid Internet address that conforms to the Internet message
	header standard, RFC-822.  (See also <A HREF="h_address_format">Explanation of Address formats</A>.)</DL>

The two fields which aren't usually visible are:<DL>

  <P><DT>FCC: <DD>The name of the folder you would like a copy of any outgoing
	message to this address to be saved in.  If this field is set, and
	this address is the first one in the message's To: header, then
	Pine will use this folder name for the FCC in lieu of the normal
	FCC folder name.

  <P><DT>COMMENTS: <DD>This field contains arbitrary text for your convenience.
	</DL>
<P>
Due to screen width limitations, these last two fields do not show up in
the normal ADDRESS BOOK display.  You may select the 
&quot;View/Update&quot; command to
view or modify them.  You may use the configuration variable
<A HREF="h_config_abook_formats">&quot;addressbook-formats&quot;</A>
to add these fields to your ADDRESS BOOK 
display, or to modify the format of the display.

<H2>Sorting the Address book</H2>

By default, address book entries are sorted alphabetically on the full
name with distribution lists sorted to the end.  Sorting can be changed by
resetting the address book sort rule in the Pine SETUP CONFIGURATION screen
--assuming you have &quot;write&quot; permission for the address book file.
<P>
Unlike the sorting of folders (which only changes presentation), sorting an
address book actually changes the file as it is kept on the computer.  For
this reason you won't be able to sort a shared or system-wide address
book.

<H2>Adding New Entries</H2>

The easiest way to add new entries to your address book is to use the
&quot;TakeAddr&quot; command when viewing a message.
This command allows you to take addresses from the header and body of the
message and put them into your address book, without having to type
them in.
<P>

To add a new entry from within the address book screen, use the AddNew
(<!--chtml if pinemode="function_key"-->F9<!--chtml else-->&quot;@&quot;<!--chtml endif-->) command.
Use this command both for adding a simple alias and for adding a
distribution list.

<H2>Distribution Lists</H2>

Address book entries can be simple cases of aliases (a single nickname is linked
to a single email address) or distribution lists (a single nickname
pointing at more than one email address).  Each distribution list has a
nickname, a full name and a list of addresses.  The addresses may be
actual addresses or they may be other nicknames in your address book.
They may even refer to other distribution lists.
There's really no difference between a simple alias and a distribution list,
other than the number of addresses.
Therefore, you can turn a simple alias with one address into a distribution
list simply by adding more addresses.
To add entries to an existing list or alias
use the View/Update (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->&quot;&gt;&quot;<!--chtml endif-->) command.  Delete (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->&quot;D&quot;<!--chtml endif-->) will delete
a single address from the list if the cursor is placed on the address;
it will delete the entire distribution list if the cursor is on the
nickname/fullname line.  View/Update may also be used to delete addresses
from a list.
<P>
Address field entries in distribution lists may take any one of three
forms: a nickname existing in any of the defined address books, a normal
address of the form &quot;jsmith@art.nowhere.edu&quot;, or a complete
fullname/address combination, e.g. &quot;John Smith
&lt;jsmith@art.nowhere.edu&gt;&quot;.
<P>
Distribution lists in Pine address books can only be used by the person or
people who have access to that address book.  They are not usually used to
implement discussion groups, but can be used to facilitate small
discussion groups if all the participants have access to the same shared
address book.

<H2>FCC and Comments</H2>

As mentioned above, each entry in the address book also has two other optional
fields, fcc and comments.  The command to look at or change either of these
is the same View/Update command used for all of the fields (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->&quot;&gt;&quot;<!--chtml endif-->).  The
comments field is just for your own use.  The fcc field overrides the
default fcc if this address is the first one on the To line.  The WhereIs
command may be used to search for particular strings in the address book,
including fields which are not visible (like comment and fcc by default).

<H2>Aggregate Operations</H2>

If the feature
<A HREF="h_config_enable_agg_ops">&quot;enable-aggregate-command-set&quot;</A>
is turned on, then the four commands &quot;Select&quot;,
&quot;Select Current&quot;, &quot;Zoom&quot;, and &quot;Apply&quot;
are available.  The two selection commands allow you to mark a set of
address book entries as being selected.  If you have more than one address
book, the selections may be in more than one of those address books.
The &quot;Zoom&quot; command will toggle between displaying only the selected
messages and all the messages.  The &quot;Apply&quot; command allows you to
apply one of the regular address book commands to all of the selected
entries.  Usually the address book commands apply to only the entry
highlighted by the cursor.  The &quot;Apply&quot; command works with the
commands &quot;ComposeTo&quot;, &quot;Delete&quot;, &quot;Print&quot;, 
&quot;Save&quot;, and &quot;Forward&quot;.

<H2>Exporting and Forwarding Address book entries</H2>

Under the save option, when you use the Export (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->&quot;X&quot;<!--chtml endif-->) command, the currently highlighted
address book entry is placed in a plain text file in your home directory
<!--chtml if pinemode="running"-->
(which, in the present configuration of your system, is
 &quot;<!--#echo var="HOME_DIR"-->&quot;) 
<!--chtml endif-->
or current working directory
<!--chtml if pinemode="running"-->
(which, at least for your current Pine &quot;session,&quot; 
is &quot;<!--#echo var="CURRENT_DIR"-->&quot;) 
<!--chtml endif-->, depending on the 
<A HREF="h_config_use_current_dir">&quot;use-current-dir&quot;</A>
configuration setting.  If you have some entries selected and use the
Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->&quot;A&quot;<!--chtml endif-->) Export command, all of the selected addresses will be
placed in the text file.
<P>
When you use the Forward (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->&quot;F&quot;<!--chtml endif-->) command, the currently highlighted
address book entry is placed in a special attachment and you are put into
the composer.  You can fill in some comments in the body of the message,
if you'd like, and send it to somebody else who uses Pine.  The recipient
may use the TakeAddr command on that message to insert the address book
entry you sent in their own address book.  If you have some entries
selected and use the Apply Forward command all of the selected entries
will be forwarded in a single message.  In Pine 4.00 or later you may
use Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->&quot;A&quot;<!--chtml endif-->) Forward to forward a copy of an entire address book.
The recipient must be using Pine 4 in order to receive this correctly.
One way for the recipient to handle this might be to create an empty
address book and then &quot;Take&quot; your forwarded address book entries into
that empty address book.

<H2>Multiple and/or Site-Wide Address books</H2>

You may have more than one personal address book.  In addition, there may
be one or more global address books.  This capability allows you to have
multiple personal address books (some of which may be shared) and it also
allows system administrators to implement site-wide address books that
contain entries for users on multiple machines within the organization.
<P><DL>
<DT>Searching. 
  <DD> If you enter a nickname when composing a message, your
  personal address books will be searched through in order, and then the
  global address book(s) searched. If more than one address book has an entry
  for the nickname, Pine uses the first one that it finds, so an entry in
  your personal address book would override a global address book entry. If
  after searching all the address books there is still no match, (Unix) Pine
  then searches the local host password file on the assumption that you have
  entered a local user name rather than an address book nickname.
  You may change the search order of your address books with the <!--chtml if pinemode="function_key"-->F3<!--chtml else-->$<!--chtml endif--> Shuffle
  command, but global address books are always searched after personal
  address books.

  <P><DT>Defining. 
  <DD> You define multiple personal address books in the 
  <A HREF="h_abook_config">SETUP AddressBooks</A> screen.  
  You can add as many as you like.  Global address books are usually
  site-wide address books defined by the System administrator, but
  you may define global address books of your own just like you define
  personal address books.

  <P><DT>Creating and updating. 
  <DD> Personal address books are normally created empty
  and populated by explicit additions from within Pine, e.g. via the
  TakeAddr command.  Unlike personal address books, global address books may
  not be modified/updated from within Pine; that is, they are Read-Only.
  Thus, global address books are created, populated and updated outside of
  Pine. They might be hand-edited, generated by a program from another
  database, or by copying an existing address book.  They might also be
  some other user's personal address book, and so be modified normally by
  that user but accessed Read-Only by you.  See the Pine Technical
  Notes document (included in the Pine distribution) for more information on
  this.

  <P><DT>Accessing.  
  <DD>There are two different types of address books in Pine.
  A local address book is stored in a regular file and the normal file
  access permissions apply.  A remote address book is stored on an IMAP
  server in a special folder which contains only messages pertaining to
  that address book.  The last message in the remote folder contains a
  copy of the address book data, and that data is copied to a local cache
  file in your home directory.  From there it is accessed just like a local
  address book.  The name of the cache file is kept track of in a special
  file called the &quot;remote-abook-metafile&quot;, the name of which is stored in
  your Pine configuration file the first time you use a remote address book.
  Just as local Pine address books use a format that only Pine understands,
  remote Pine address books do the same and other mail reading programs
  are unlikely to be able to understand them.<P>
  While global address books are explicitly intended to be shared, there is
  nothing to prevent you from sharing a personal address book with other
  Pine users. This might be useful in the case of a small workgroup.
  However, it is recommended that updates to shared personal address books
  be done when other Pine users are not accessing the address book. Pine
  does not do any file-locking to manage concurrent updates to the
  addressbook, but it does check to see if the file has been modified before
  making any changes.  Consequently, inadvertent concurrent updates will
  only cause other Pine users to have to restart their address book
  operation, which will cause Pine to re-open the updated file.

  <P><DT>Converting to Remote.  
  <DD>The easiest way to convert an existing local
  address book into a remote address book is to create an empty new remote
  address book with the &quot;Add Abook&quot; command in the SETUP Addressbook screen.
  After you have added the empty
  remote address book, go into the screen for the address book you wish
  to copy and &quot;Select&quot; &quot;All&quot;.  This selects every entry in that
  address book.  Then type the command &quot;Apply Save&quot;.
  You will be asked for the address book to save to.  You may use ^P and ^N
  to get to the new empty address book, then hit RETURN and the addresses
  will be copied.
  At this point you'll probably want to unselect all the entries in the local
  address book before proceeding. You do that with
  &quot;Select&quot; &quot;unselect All&quot;.

</DL>
<UL>
<LI><A HREF="h_address_format">Explanation of Address formats</A>
</UL>
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_abook_select_addr =====
<HTML>
<HEAD>
<TITLE>Addressbook Selection Explained</TITLE>
</HEAD>
<BODY>
<H1>SELECT ADDRESS</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Messages               General Pine Commands
-------------------------------               ---------------------
F5   Move to previous entry                   F1  Show this help text
F6   Move to next entry
F7   Show previous screen of address book
F8   Show next screen of address book
F12  WhereIs (search through address book)

Address Selection Commands
--------------------------
F3   Exit the Address Select screen (without selecting an address)
F4   Select the currently highlighted entry
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Messages               General Pine Commands
-------------------------------               ---------------------
 P   Move to previous entry                   ?  Show this help text
 N   Move to next entry
 -   Show previous screen of address book
Spc  Show next screen of address book
 W   WhereIs (search through address book)

Address Selection Commands
--------------------------
 E   Exit the Address Select screen (without selecting an address)
 S   Select the currently highlighted entry
</PRE>
<!--chtml endif-->
<P>

This screen is designed to let you easily scan your address book(s) in
order to select an entry for the message you are composing.  You cannot
edit your address book in any way at this time, for address book
maintenance, select the address book command when not composing a message.
<P>

If you are composing a message and know the nickname of the person/list you
want, you can bypass this screen by simply typing in the nickname on the
appropriate header line (To:, Cc:, etc.)  Exiting this screen without
selecting an entry does not cancel your message.
<P>

FOR MORE INFORMATION on addressing see
<A HREF="h_address_format">Explanation of Address formats</A>, and the
<A HREF="h_abook_opened">Address Book Screen's</A>
help text.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_abook_select_top =====
<HTML>
<HEAD>
<TITLE>Addressbook Selection Navigation Explained</TITLE>
</HEAD>
<BODY>
<H1>NAVIGATING WHILE SELECTING ADDRESSES</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Address Books       General Pine Commands
-------------------------------            ---------------------
F4   View the highlighted address book
F5   Move to previous address book         F1  Show this help text
F6   Move to next address book
F7   Show previous screen of address books
F8   Show next screen of address books
F12  WhereIs (search through address books)

Address Selection Commands
--------------------------
F3   Exit the Address Select screen (without selecting an address)
F4   Select the currently selected entries (if using ListMode)
F9   Change to ListMode
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Address Books       General Pine Commands
-------------------------------            ---------------------
 &gt;   View the highlighted address book
 P   Move to previous address book         ?  Show this help text
 N   Move to next address book
 -   Show previous screen of address books
Spc  Show next screen of address books
 W   WhereIs (search through address books)

Address Selection Commands
--------------------------
 E   Exit the Address Select screen (without selecting an address)
 S   Select the currently selected entries (if using ListMode)
 L   Change to ListMode
</PRE>
<!--chtml endif-->
<P>

This screen is designed to let you easily scan your address book(s) in
order to select entries for the message you are composing.  You cannot
edit your address book in any way at this time.  For address book
maintenance, select the address book command when not composing a message.
<P>

If you are composing a message and know the nickname of the person/list you
want, you can bypass this screen by simply typing in the nickname on the
appropriate header line (To:, Cc:, etc.)  Exiting this screen without
selecting an entry does not cancel your message.
<P>

The ListMode command will add a column at the left edge of the screen.
You mark the entries which you wish to select with the &quot;X&quot; command.
This allows you to choose more than one entry at a time.
<P>

An alternative method of composing a message to entries in your
address book(s) is to first use the &quot;Select&quot; command from
the address book maintenance screen and then the &quot;Apply&quot;
&quot;ComposeTo&quot; command to start the composer composing to the
selected entries.
<P>

FOR MORE INFORMATION on addressing see
<A HREF="h_address_format">Explanation of Address formats</A>, and the
<A HREF="h_abook_opened">Address Book Screen's</A>
help text.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_abook_select_listmode =====
<HTML>
<HEAD>
<TITLE>Address Listmode Selection from Composer Explained</TITLE>
</HEAD>
<BODY>
<H1>COMPOSER: SELECT ADDRESSES</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Messages                 General Pine Commands
-------------------------------                 ---------------------
F5   Move to previous entry                     F1  Show this help text
F6   Move to next entry
F7   Show previous screen of address book
F8   Show next screen of address book
F12  WhereIs (search through address book)

Address Selection Commands
--------------------------
F3   Exit the Address Select screen (without selecting an address)
F4   Select the currently highlighted entry
F9   Change to ListMode
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Messages                 General Pine Commands
-------------------------------                 ---------------------
 P   Move to previous entry                     ?  Show this help text
 N   Move to next entry
 -   Show previous screen of address book
Spc  Show next screen of address book
 W   WhereIs (search through address book)

Address Selection Commands
--------------------------
 E   Exit the Address Select screen (without selecting an address)
 S   Select the currently highlighted entry
 L   Change to ListMode
</PRE>
<!--chtml endif-->
<P>

This screen is designed to let you easily scan your address book(s) in
order to select entries for the message you are composing.  You cannot
edit your address book in any way at this time, for address book
maintenance, select the address book command when not composing a message.
<P>

If you are composing a message and know the nickname of the person/list you
want, you can bypass this screen by simply typing in the nickname on the
appropriate header line (To:, Cc:, etc.)  Exiting this screen without
selecting an entry does not cancel your message.
<P>

The ListMode command will add a column at the left edge of the screen.
You mark the entries which you wish to select with the &quot;X&quot; command.
This allows you to choose more than one entry at a time.
<P>

An alternative method of composing a message to entries in your
address book(s) is to first use the &quot;Select&quot; command from
the address book maintenance screen and then the &quot;Apply&quot;
&quot;ComposeTo&quot; command to start the composer composing to the
selected entries.
<P>

FOR MORE INFORMATION on addressing see
<A HREF="h_address_format">Explanation of Address formats</A>, and the
<A HREF="h_abook_opened">Address Book Screen's</A>
help text.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_abook_select_checks =====
<HTML>
<HEAD>
<TITLE>Address Selection from Composer Explained</TITLE>
</HEAD>
<BODY>
<H1>COMPOSER: SELECT ADDRESSES</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Messages                 General Pine Commands
-------------------------------                 ---------------------
F5   Move to previous entry                     F1  Show this help text
F6   Move to next entry
F7   Show previous screen of address book
F8   Show next screen of address book
F12  WhereIs (search through address book)

Address Selection Commands
--------------------------
F3   Exit the Address Select screen (without selecting an address)
F4   Select the currently highlighted entry
F9   Set or Unset the highlighted entry
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Messages                 General Pine Commands
-------------------------------                 ---------------------
 P   Move to previous entry                     ?  Show this help text
 N   Move to next entry
 -   Show previous screen of address book
Spc  Show next screen of address book
 W   WhereIs (search through address book)

Address Selection Commands
--------------------------
 E   Exit the Address Select screen (without selecting an address)
 S   Select the currently highlighted entry
 X   Set or Unset the highlighted entry
</PRE>
<!--chtml endif-->
<P>

Mark the entries you wish to select with the &quot;X Set/Unset&quot;
command.  Type &quot;S Select&quot; to select all of the entries you
have marked, just as if you had typed them in by hand.
<P>

An alternative method of composing a message to entries in your
address book(s) is to first use the &quot;Select&quot; command from
the address book maintenance screen and then the &quot;Apply&quot;
&quot;ComposeTo&quot; command to start the composer composing to the
selected entries.
<P>

FOR MORE INFORMATION on addressing see
<A HREF="h_address_format">Explanation of Address formats</A>, and the
<A HREF="h_abook_opened">Address Book Screen's</A>
help text.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_abook_select_nicks_take =====
<HTML>
<HEAD>
<TITLE>Take Address Nickname Selection Explained</TITLE>
</HEAD>
<BODY>
<H1>TAKEADDR: SELECT NICKNAME</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Messages                 General Pine Commands
-------------------------------                 ---------------------
F5   Move to previous entry                     F1  Show this help text
F6   Move to next entry
F7   Show previous screen of address book
F8   Show next screen of address book
F12  WhereIs (search through address book)

Message Selection Commands
--------------------------
F3   Exit the Nickname Select screen (without selecting an address)
F4   Select the currently highlighted entry
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Messages                 General Pine Commands
-------------------------------                 ---------------------
 P   Move to previous entry                     ?  Show this help text
 N   Move to next entry
 -   Show previous screen of address book
Spc  Show next screen of address book
 W   WhereIs (search through address book)

Message Selection Commands
--------------------------
 E   Exit the Nickname Select screen (without selecting an address)
 S   Select the currently highlighted entry
</PRE>
<!--chtml endif-->
<P>

This screen is designed to let you modify or add to an existing
address book entry.  You have already selected the name(s) and
address(es) through &quot;Take Address&quot;.  This screen simply lets
you scan your address books and select the nickname to be
changed/augmented.  If you want to add a new entry, then you are in
the wrong place-- Select &quot;Exit&quot; command.
<P>

FOR MORE INFORMATION on addressing see
<A HREF="h_address_format">Explanation of Address formats</A>, and the
<A HREF="h_abook_opened">Address Book Screen's</A>
help text.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_abook_select_nick =====
<HTML>
<HEAD>
<TITLE>Nickname Selection Explained</TITLE>
</HEAD>
<BODY>
<H1>SELECT NICKNAME</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Messages                 General Pine Commands
-------------------------------                 ---------------------
F5   Move to previous entry                     F1  Show this help text
F6   Move to next entry
F7   Show previous screen of address book
F8   Show next screen of address book
F12  WhereIs (search through address book)

Message Selection Commands
--------------------------
F3   Exit the Nickname Select screen (without selecting an address)
F4   Select the currently highlighted entry
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Messages                 General Pine Commands
-------------------------------                 ---------------------
 P   Move to previous entry                     ?  Show this help text
 N   Move to next entry
 -   Show previous screen of address book
Spc  Show next screen of address book
 W   WhereIs (search through address book)

Message Selection Commands
--------------------------
 E   Exit the Nickname Select screen (without selecting an address)
 S   Select the currently highlighted entry
</PRE>
<!--chtml endif-->
<P>

This screen is designed to let you look at the nicknames in your address
books before choosing a new one.
<P>

FOR MORE INFORMATION on addressing see
<A HREF="h_address_format">Explanation of Address formats</A>, and the
<A HREF="h_abook_opened">Address Book Screen's</A>
help text.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_takeaddr_screen =====
<HTML>
<HEAD>
<TITLE>Take Address Screen Explained</TITLE>
</HEAD>
<BODY>
<H1>TAKE ADDRESS COMMANDS</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
Navigating the List of Addresses       Address Selection Commands        
--------------------------------       --------------------------        
 F5  Move to previous entry            F3  Exit without taking address
 F6  Move to next entry                F4  Take current address(es)
 F7  Show previous page of address list
 F8  Show next page of address list
 F2  WhereIs (search list)
			       --------------
Mode Toggle            F9  Set/Unset current address
-----------            F10 Set all
 F12 Toggle between List and single mode       F11 Unset all
</PRE>
<!--chtml else-->
<PRE>
Navigating the List of Addresses       Address Selection Commands
--------------------------------       --------------------------
 P  Move to previous entry              &lt;  Exit without taking address
 N  Move to next entry                  T  Take address
 -  Show previous page of address list
Spc Show next page of address list
 W  WhereIs (search list)              List Mode
				       ---------
Single Mode                             X  Set/Unset current address
-----------                             A  Set all addresses
 L  Switch to list mode                 U  Unset all addresses
					S  Switch to single mode
</PRE>
<!--chtml endif-->

<H2>Description of the Take Address Screen</H2>

This screen is designed to let you select one or more address/name
combinations from the current message into your address book.  The
cursor is initially placed on the line with the message author.  Other
lines include the names of people and/or mailing lists who also
received the message.  Other people &quot;involved&quot; in the
message (e.g. the person named as Reply-To:) are also listed here.
<P>

The simple case is adding a new, single entry into your address book. To
do this, simply highlight the correct line and press 
<!--chtml if pinemode="function_key"-->
F4.
<!--chtml else-->
&quot;T&quot;.
<!--chtml endif-->
To create a new list or add to an existing list, switch the screen display
into List Mode by pressing
<!--chtml if pinemode="function_key"-->
F12.
<!--chtml else-->
&quot;L&quot;.
<!--chtml endif-->
In List Mode, you select the
group of addresses you wish to manipulate by marking them with an
&quot;X&quot;.
The Set/Unset
<!--chtml if pinemode="function_key"-->
(F9)
<!--chtml else-->
(&quot;X&quot;)
<!--chtml endif-->
command will turn the &quot;X&quot; on for the
highlighted address if it was off or turn it off if it was previously on.
The SetAll command will select all of the addresses, and the UnSetAll
command will turn off all the selections.  Once you've gotten the
selection the way you want it, you may create a new list by pressing
<!--chtml if pinemode="function_key"-->
F4.
<!--chtml else-->
&quot;T&quot;.
<!--chtml endif-->
<P>

In both the simple and list cases, after choosing to take the address,
you will be asked for the nickname of the entry.  Typing in a new name
creates the new entry/list.  Entering an existing nickname will replace
the entry (simple case) or add to the list (list case).  Alternatively,
you can press Ctrl-T at the nickname prompt and select an existing
nickname from your address book.
<P>

You will normally start in Single Mode, unless you used the Apply command
to startup the TakeAddr screen, in which case you will start in List Mode.
You may switch between the two modes at any time.  If you've already
selected several addresses in List Mode, those will be remembered when you
switch to Single Mode and then back to List Mode.  The set of addresses
that are pre-selected when you start in List Mode are the From addresses
of all of the messages you are operating on.  You may, of course, easily
erase those selections with the UnSetAll command.
<P>

If you have more than one writable address book, you will be prompted for
the name of the address book you wish to add the new entry to before
anything else. You can use ^N and ^P to choose among the defined address
books, or type in the address book name.
<P>

FOR MORE INFORMATION on addressing see
<A HREF="h_address_format">Explanation of Address formats</A>, and the
<A HREF="h_abook_opened">Address Book Screen's</A>
help text.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_abook_view ========================
<HTML>
<HEAD>
<TITLE>Address Book View Explained</TITLE>
</HEAD>
<BODY>
This function allows you to view the contents of an address book entry. You
can only view one entry at a time.
<P>
<DL>
<DT>Help
<!--chtml if pinemode="function_key"-->
(F1)
<!--chtml else-->
(?)
<!--chtml endif-->
</DT>
<DD>
Display this help text.

<DT>Abook
<!--chtml if pinemode="function_key"-->
(F3)
<!--chtml else-->
(&lt;)
<!--chtml endif-->
</DT>
<DD>
Go back to index of address book entries.

<DT>Update
<!--chtml if pinemode="function_key"-->
(F4)
<!--chtml else-->
(U)
<!--chtml endif-->
</DT>
<DD>
Update (modify) this entry.


<DT>ComposeTo
<!--chtml if pinemode="function_key"-->
(F6)
<!--chtml else-->
(C)
<!--chtml endif-->
</DT>
<DD>Compose a message to the address(es) in this entry.

<DT>Prev Page
<!--chtml if pinemode="function_key"-->
(F8)
<!--chtml else-->
(Space)
<!--chtml endif-->
</DT>
<DD>
Show the next page of the current entry.

<DT>Print
<!--chtml if pinemode="function_key"-->
(F9)
<!--chtml else-->
(%)
<!--chtml endif-->
</DT>
<DD>Print the current entry.  You can select the
printer or the print command via the &quot;Setup&quot; command
on the Main menu.

<DT>WhereIs
<!--chtml if pinemode="function_key"-->
(F10)
<!--chtml else-->
(W)
<!--chtml endif-->
</DT>
<DD>Search the entry for a string of letters.  If it is
found, move to it.  The string can be one word or a phrase.
If there are multiple occurrences, the cursor moves to the
first occurrence beyond the current cursor position.

<DT>Fwd Email
<!--chtml if pinemode="function_key"-->
(F11)
<!--chtml else-->
(F)
<!--chtml endif-->
</DT>
<DD>Begin composition of a new mail message with the displayed
text already inserted in the message body.

</DL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_ldap_view ========================
<HTML>
<HEAD>
<TITLE>LDAP Response View Explained</TITLE>
</HEAD>
<BODY>
This function allows you to view the contents of a directory entry. You
can only view one entry at a time.
<P>
<DL>
<DT>Help
<!--chtml if pinemode="function_key"-->
(F1)
<!--chtml else-->
(?)
<!--chtml endif-->
</DT>
<DD>
Display this help text.

<DT>Dir Index
<!--chtml if pinemode="function_key"-->
(F3)
<!--chtml else-->
(&lt;)
<!--chtml endif-->
</DT>
<DD>Go back to index of directory entries.

<DT>Prev Page
<!--chtml if pinemode="function_key"-->
(F8)
<!--chtml else-->
(Space)
<!--chtml endif-->
</DT>
<DD>
Show the next page of the current entry.

<DT>Print
<!--chtml if pinemode="function_key"-->
(F9)
<!--chtml else-->
(%)
<!--chtml endif-->
</DT>
<DD>Print the current entry on paper.  You can select the
printer or the print command via the &quot;Setup&quot; command
on the Main menu.

<DT>WhereIs
<!--chtml if pinemode="function_key"-->
(F10)
<!--chtml else-->
(W)
<!--chtml endif-->
</DT>
<DD>Search the entry for a string of letters.  If it is
found, move to it.  The string can be one word or a phrase.
If there are multiple occurrences, the cursor moves to the
first occurrence beyond the current cursor position.

<DT>Fwd Email
<!--chtml if pinemode="function_key"-->
(F11)
<!--chtml else-->
(F)
<!--chtml endif-->
</DT>
<DD>Begin composition of a new mail message with the displayed
text already inserted in the message body.

<DT>Save
<!--chtml if pinemode="function_key"-->
(F12)
<!--chtml else-->
(S)
<!--chtml endif-->
</DT>
<DD>Save the displayed entry to one of your address books or export
it to a file.
</DL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_attachment_screen =====
<HTML>
<HEAD>
<TITLE>Attachment Index Screen Explained</TITLE>
</HEAD>
<BODY>
The &quot;ATTACHMENT INDEX&quot; displays a list of the current
message's attachments, and allows various operations on them.  The
first attachment is usually the message text, but does not include the
header portion of the message.
<P>
Available commands include:
<P>
<DL>

<DT>Help</DT>
<DD>Show this help text.

<DT>Msg #<I>num</I></DT>
<DD>Leave this screen without displaying or saving any attachments.

<DT>View</DT>
<DD>View the currently selected attachment.

<DT>Prev Attach</DT>
<DD>Move to previous attachment.

<DT>Next Attach</DT>
<DD>Move to next attachment.

<DT>Prev Page</DT>
<DD>Previous page of the listed attachments.

<DT>Next Page</DT>
<DD>Next page of the listed attachments.

<DT>Delete</DT>
<DD>Mark the currently selected attachment for Deletion.  The delete
flag <EM>only</EM> has effect when saving the message to a folder.
Attachments marked for deletion are exluded from the messsage when
it is saved.  In addition, the delete mark <EM>only</EM> applies to
this Pine session.

<DT>Undelete</DT>
<DD>Turn off the Delete flag for the selected attachment.

<DT>Save</DT>
<DD>Save the selected attachment to a file.  If the attachment is of
type &quot;RFC822/Message&quot;, then the attachment will be saved to
the specified mail folder.

<DT>Export</DT>
<DD>If the attachment is of
type &quot;RFC822/Message&quot;, then &quot;Export&quot; is used to
copy the message to a file in the same way this command works on 
messages in the MESSAGE INDEX and MESSAGE TEXT screens.

<DT>Pipe</DT>
<DD>Pipe the attachment contents into a UNIX command (if enabled).
A description of the Pipe sub-commands is  <A HREF="h_pipe_command">here</A>.

<DT>WhereIs</DT>
<DD>Find a matching string in the attachment list.

<DT>AboutAttch</DT>
<DD>Examine various aspects of the selected attachment.

<DT>Print</DT>
<DD>Print the selected attachment.

<DT>Forward</DT>
<DD>Forward the selected attachment as an attachment.
</DL>

<P>

All attachments can be saved or piped into a UNIX command, but some may
not be readily displayed by either Pine or an external tool.  In such
cases, the reason why the message cannot be displayed is displayed on
Pine's message line.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_mail_text_att_view ========================
<HTML>
<HEAD>
<TITLE>Attachment View Screen Explained</TITLE>
</HEAD>
<BODY>
This function allows you to view the contents of a text attachment. You
can only view one attachment at a time.
<P>
Available commands include:
<P>
<DL>

<DT>Help</DT>
<DD>Display this help text

<DT>AttchIndex</DT>
<DD>Leave viewer and return to the &quot;ATTACHMENT INDEX&quot; screen

<DT>Prev Page</DT>
<DD>Show the previous page of the current attachment.

<DT>Next Page</DT>
<DD>Show the next page of the current attachment by pressing the space bar.

<DT>Delete</DT>
<DD>Mark the viewed attachment for Deletion.  The delete
flag <EM>only</EM> has affect when saving the message to a folder.
Attachments marked for deletion are exluded from the messsage when
it is saved.  In addition, the delete mark <EM>only</EM> applies to
this Pine session.

<DT>Undelete</DT>
<DD>Turn off the Delete flag for the selected attachment.

<DT>Save</DT>
<DD>Copy the current attachment to a file.  If you just enter
a filename, the attachment will be saved with that name in
your home directory 
<!--chtml if pinemode="running"-->
(which, in the present configuration of your system, is
 &quot;<!--#echo var="HOME_DIR"-->&quot;) 
<!--chtml endif-->
or current working directory
<!--chtml if pinemode="running"-->
(which, at least for your current Pine &quot;session,&quot; 
is &quot;<!--#echo var="CURRENT_DIR"-->&quot;) 
<!--chtml endif-->, depending on the
<A HREF="h_config_use_current_dir">&quot;use-current-dir&quot;</A>
configuration setting.  You may enter the full
path and filename to save it in another directory instead.

<DT>Export</DT>
<DD>If the attachment is of
type &quot;RFC822/Message&quot;, then &quot;Export&quot; is used to
copy the message to a file in the same way this command works on 
messages in the MESSAGE INDEX and MESSAGE TEXT screens.
(If you have any <A HREF="h_config_display_filters">Display-Filters</A>
defined, they may affect the contents of the exported file.)

<DT>Pipe</DT>
<DD>Pipe the attachment contents into a UNIX command (if enabled)

<DT>WhereIs</DT>
<DD>Search the attachment for a string of letters.  If it is
found, move to it.  The string can be one word or a phrase.
If there are multiple occurrences, the cursor moves to the
first occurrence beyond the current cursor position.

<DT>Print</DT>
<DD>Print the current attachment on paper.  You can select the
printer or the print command via the &quot;Setup&quot; command
on the Main menu.

<DT>Forward</DT>
<DD>Forward the selected attachment as an attachment.
</DL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
============= h_simple_text_view ==============
<HTML>
<HEAD>
<TITLE>Simple Text View Screen Explained</TITLE>
</HEAD>
<BODY>

The following commands are available on this screen:
<P>
<DL>
<DT>Help</DT>
<DD>Show this help text

<DT>Exit</DT>
<DD>Exit Viewer, and go back to mail processing

<DT>Prev Page</DT>
<DD>Show the previous page text

<DT>Next Page</DT>
<DD>Show the next page of text by pressing the space bar

<DT>Print</DT>
<DD>Print the displayed text on paper.  You can select the
printer or the print command via the &quot;Setup&quot; command
on the Main menu.

<DT>Fwd Email</DT>
<DD>Begin composition of a new mail message with the displayed
text already inserted in the message body.

<DT>Save</DT>
<DD>Copy the displayed text to a file.  If you just enter
a filename, the attachment will be saved with that name in
your 
home directory 
<!--chtml if pinemode="running"-->
(which, in the present configuration of your system, is
 &quot;<!--#echo var="HOME_DIR"-->&quot;) 
<!--chtml endif-->
or current working directory
<!--chtml if pinemode="running"-->
(which, at least for your current Pine &quot;session,&quot; 
is &quot;<!--#echo var="CURRENT_DIR"-->&quot;) 
<!--chtml endif-->, depending on the
<A HREF="h_config_use_current_dir">&quot;use-current-dir&quot;</A>
configuration setting.   You may enter the full
path and filename to save it in another directory instead.

<DT>WhereIs</DT>
<DD>Search the attachment for a string of letters.  If it is
found, move to it.  The string can be one word or a phrase.
If there are multiple occurrences, the cursor moves to the
first occurrence beyond the current cursor position.
</DL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_pine_for_windows ========
<HTML>
<HEAD>
<TITLE>GETTING HELP IN PINE</TITLE>
</HEAD>
<BODY>
<H1>Getting Help In PC-Pine</H1>
PC-Pine offers specific help for every screen via the 
<!--chtml if pinemode="function_key"-->
&quot;F1&quot; key.
<!--chtml else-->
&quot;?&quot; or &quot;^G&quot;
keys.  (The Control-G key is used in contexts where &quot;?&quot; would be
mistaken as text being entered.)
<!--chtml endif-->
<P>

The <A HREF="main_menu_tx">MAIN MENU</A> help 
<!--chtml if pinemode="function_key"-->
(&quot;F1&quot;)
<!--chtml else-->
(&quot;?&quot;) 
<!--chtml endif-->
provides a general overview of Pine, as
well as information specific to that screen.  There is also a
&quot;<A HREF="h_news">Release Notes</A>&quot; command available
from the MAIN MENU.

<P>
Although this version of Pine is for Microsoft Windows, it is not what
native Windows users would consider a full
&quot;Graphical User Interface&quot; application.

<P>
However, it does make available many of the controls such users are
accustom to such as scrollbars, menu and toolbars.

<P>
In addition, it offers considerable mouse support.  For example,
screens with selectable items (such as messages in the MESSAGE INDEX,
or hyperlinks and URLs in MESSAGE TEXT when the suitable
&quot;enable-msg-view-*&quot; features are enabled) can be
highlighted with a single click or chosen with a double click.
Similarly, menu items on the bottom of the screen can be executed by
placing the mouse on them and single clicking.

<P>
Further, PC-Pine provides context-sensitive pop-up menus that offer
convenient short-cuts when selecting or navigating PC-Pines screens.
For example, a right-button click on a message in the MESSAGE INDEX
brings up a menu offering to, among other things, View the selected
message in a separate window.  A similar menu's offered when
right-button clicking on selectable attachments (if the
&quot;enable-msg-view-attachments&quot; feature is enabled.

<P>
Pop-ups also allow for convenient Copying of text onto the clipboard.
Use the drag the mouse with the left-button down to select text, and then
the right-button pop-up to copy it onto the clipboard.

<P>
Similarly, you can Cut/Copy/Paste in the compser using this same
method.  In addtion, if you move the mouse above the top or below the
bottom of the window while selecting text the message text will
scroll.  Shift-Click will extend an existing selection.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_composer =====
<HTML>
<HEAD>
<TITLE>COMPOSER COMMANDS</TITLE>
</HEAD>
<BODY>
<H1>COMPOSER COMMANDS</H1>

CURSOR&nbsp;MOTION&nbsp;KEYS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|EDITING&nbsp;KEYS<BR>
&nbsp;&nbsp;^B&nbsp;(Left&nbsp;Arrow)&nbsp;&nbsp;&nbsp;Back&nbsp;character&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Delete&nbsp;current&nbsp;character<BR>
&nbsp;&nbsp;^F&nbsp;(Right&nbsp;Arrow)&nbsp;&nbsp;Forward&nbsp;character&nbsp;&nbsp;|&nbsp;^H&nbsp;(DEL)&nbsp;Delete&nbsp;previous&nbsp;character<BR>
&nbsp;&nbsp;^P&nbsp;(Up&nbsp;Arrow)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Previous&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^^&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Set&nbsp;a&nbsp;<A HREF="h_compose_markcutpaste">mark</A><BR>
&nbsp;&nbsp;^N&nbsp;(Down&nbsp;Arrow)&nbsp;&nbsp;&nbsp;Next&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;<!--chtml if pinemode="function_key"-->F9<!--chtml else-->^K<!--chtml endif-->&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_compose_markcutpaste">Cut</A>&nbsp;marked&nbsp;text&nbsp;or<BR>
&nbsp;&nbsp;^A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Beginning&nbsp;of&nbsp;line&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;delete&nbsp;current&nbsp;line<BR>
&nbsp;&nbsp;^E&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;End&nbsp;of&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;<!--chtml if pinemode="function_key"-->F10<!--chtml else-->^U<!--chtml endif-->&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_compose_markcutpaste">Paste</A>&nbsp;text,&nbsp;undelete&nbsp;lines<BR>
&nbsp;&nbsp;^Y&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Previous&nbsp;page&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cut&nbsp;with&nbsp;^K,&nbsp;or&nbsp;unjustify<BR>
&nbsp;&nbsp;^V&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Next&nbsp;page&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|-------------------------------------<BR>
&nbsp;&nbsp;^@&nbsp;(Ctrl-SPACE)&nbsp;&nbsp;&nbsp;Next&nbsp;word&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|SCREEN/COMPOSITION&nbsp;COMMANDS<BR>
---------------------------------------|&nbsp;<!--chtml if pinemode="function_key"-->F6<!--chtml else-->^W<!--chtml endif-->&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_composer_search">Whereis</A>&nbsp;(search&nbsp;for&nbsp;string)<BR>
MESSAGE&nbsp;COMMANDS&nbsp;|&nbsp;GENERAL&nbsp;COMMANDS&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;<!--chtml if pinemode="function_key"-->F12<!--chtml else-->^T&nbsp;<!--chtml endif-->&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_compose_spell">Spell&nbsp;checker</A><BR>
&nbsp;<!--chtml if pinemode="function_key"-->F3<!--chtml else-->^C<!--chtml endif-->&nbsp;&nbsp;&nbsp;<A HREF="h_compose_cancel">Cancel</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;<!--chtml if pinemode="function_key"-->F1<!--chtml else-->^G<!--chtml endif-->&nbsp;&nbsp;&nbsp;&nbsp;Get&nbsp;help&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;<!--chtml if pinemode="function_key"-->F4<!--chtml else-->^J<!--chtml endif-->&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_compose_justify">Justify</A>&nbsp;paragraph<BR>
&nbsp;<!--chtml if pinemode="function_key"-->F11<!--chtml else-->^O&nbsp;<!--chtml endif-->&nbsp;&nbsp;<A HREF="h_common_postpone">Postpone</A>&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;^Z&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_common_suspend">Suspend</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^L&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Redraw&nbsp;Screen<BR>
&nbsp;<!--chtml if pinemode="function_key"-->F2<!--chtml else-->^X<!--chtml endif-->&nbsp;&nbsp;&nbsp;<A HREF="h_compose_send">Send</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;<!--chtml if pinemode="function_key"-->F6<!--chtml else-->^_<!--chtml endif-->&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_compose_alted">Alt.&nbsp;editor</A>&nbsp;&nbsp;|&nbsp;<!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif-->&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_compose_readfile">Read&nbsp;in&nbsp;a&nbsp;file</A><BR>

<P>
NOTE:
<OL>
 <LI>For help on a particular command, hilite the bold text associated
with it above and hit Return.
 <LI> The availability of certain commands
is determined by Pine configuration files and system capabilities.
At some sites, certain commands may not be available due to security or
support concerns.
 <LI>Pine does not use the following keys:  Ctrl-S, Ctrl-Q, Ctrl-],
Ctrl-&#92;, ESC.
 <LI>For special handling of Ctrl-S and Ctrl-Q see special comments regarding
<A HREF="h_special_xon_xoff">&quot;XOFF/XON&quot;</A>.
</OL>

<P>
HINT: To move rapidly to the bottom of a message you are composing,
enter ^W^V.  To go to the top, ^W^Y.  These can be used in conjunction
with the Mark and Cut commands to eliminate large amounts of unwanted
text in a Reply.

<H2>Description of Composer</H2>

Pine has a built-in editing program which allows you to compose messages
without having to leave Pine.  The editor is designed to be very simple to
use so that you can get started writing email right away.

<P>
Messages are usually just text, about 80 columns wide.  Using upper and
lower case is encouraged.  On some systems the size limit of the message
is about 100,000 characters, which is about 2,000 lines.  You can include
punctuation and special characters found on most keyboards, but you can't
include characters with diacritical marks and certain special symbols.

<P>
Text automatically wraps as you type past the end of a line so you do not
have to hit return.  Using the
&quot;<A HREF="h_compose_justify">Justify</A>&quot; command,
you can also reformat text explicitly, perhaps after you have
deleted some text.

<P>
You can include other text files with the 
&quot;<A HREF="h_compose_readfile">Read File</A>&quot; command
which will prompt you for the name of the file to insert at the
current cursor postion.

<P>
<UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_composer_browse =====
<HTML>
<HEAD>
<TITLE>BROWSER</TITLE>
</HEAD>
<BODY>
<H1>BROWSER</H1>
This screen lets you browse your files and directories.  To go to another 
directory (identified by &quot;(dir)&quot;), move the cursor to it and 
choose &quot;Select&quot; (the default choice on the menu); 
or choose &quot;Goto&quot; and enter the name of the directory.
<!--chtml if pinemode="os_windows"-->
<!--chtml else--> 
In Unix Pine, you may use 
&quot;~&quot; to refer to your home directory or &quot;~user&quot; to refer 
to another's home directory.  
<!--chtml endif--><P>
To select a file, move the cursor to it and 
choose &quot;Select&quot; (the default choice on the menu).  
<P>
<UL>
<LI>Note <B>if</B> you are currently using the BROWSER for choosing a file for 
inclusion in the 
message body (that is, you chose &quot;Read File&quot; with the cursor under 
the 
&quot;----- Message Text -----&quot; line
while composing, then &quot;To Files&quot;):  Since the file 
selected will become part of the message text, it must be in a format 
suitable for that (Pine does not check!), such as a plain text file.
Files of other formats (for example, graphics, databases, software 
programs) should be 
<B>attached</B> to the message instead --
by moving the cursor in the COMPOSE MESSAGE screen into the 
message header area and pressing 
<!--chtml if pinemode="function_key"-->
F6.
<!--chtml else-->
Ctrl-J.
<!--chtml endif--> 
 
<P><LI>
Note <B>if</B> you are currently using the BROWSER for saving a message 
attachment, or exporting a message, to a file: You can use the Add command to 
provide the name for a new file to save/export to, and then select that name 
to use it for the save/export operation.  Back at the prompt 
&quot;EXPORT: Copy message to file in ...&quot; hit Enter, then choose 
either Overwrite or Append (it doesn't make a difference, since the file is 
so far empty).  Note: If you cancel the 
operation at that point, the file created with the Add command will remain 
0 bytes in size.

</UL>
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_composer_ins =====
<HTML>
<HEAD>
<TITLE>INSERT TEXT FILE</TITLE>
</HEAD>
<BODY>
<H1>INSERT TEXT FILE</H1>

Use this function to insert a text file into your message. The file name
given can be an absolute file path name for your system
<!--chtml if pinemode="os_windows"-->
(for example, &quot;H:&#92;SIGFILES&#92;FULLINFO.TXT&quot;), a file
with a relative pathname, or simply a file name without
drive or directory specification.  
<!--chtml else-->
(for example, &quot;/tmp/exported.earlier&quot; on Unix hosts), 
a file in your home directory, or a file path relative to your 
home directory.  In Unix Pine, you may use &quot;~&quot; to refer to 
your home directory or &quot;~user&quot; to refer to another
account's home directory.
<!--chtml endif-->
<P>
No wild card characters may be used.  
The file must reside on the system running Pine.
<P>
If the 
<A HREF="h_config_use_current_dir">&quot;use-current-dir&quot;</A>
feature is set, names are relative to your current working directory 
<!--chtml if pinemode="running"-->
(which, at least for your current Pine &quot;session,&quot; 
is &quot;<!--#echo var="CURRENT_DIR"-->&quot;) 
<!--chtml endif-->
rather than your home directory
<!--chtml if pinemode="running"-->
(which, in the present configuration of your system, is
 &quot;<!--#echo var="HOME_DIR"-->&quot;) 
<!--chtml endif-->
.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_composer_ins_m =====
<HTML>
<HEAD>
<TITLE>INSERT MESSAGE</TITLE>
</HEAD>
<BODY>
<H1>INSERT MESSAGE</H1>

Type in the number of a message in the currently open folder to insert it
into your message.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_composer_search =====
<HTML>
<HEAD>
<TITLE>Explanation of Composer Whereis Command </TITLE>
</HEAD>
<BODY>
<H1>Help For Whereis Command</H1>

Whereis is used to search the message for a word or part of a word.
When searching in the composer, only the message part of your mail is
searched, and the cursor is put on the first occurrence appearing
after the location of the cursor.  The search will wrap to the
beginning of the message when it no longer finds matches in the
remainder of the message.

To search for the same string a second time, press 
<!--chtml if pinemode="function_key"-->
&quot;F6&quot;
<!--chtml else-->
&quot;^W&quot;
<!--chtml endif-->
to begin search and then just press RETURN to accept the previous
search string shown in square brackets rather than entering a new
search string.<P>

The &quot;Search&quot; prompt has several sub-command available:

<DL>
<DT>Get Help</DT>
<DD> Takes you to this help page.

<DT>Cancel</DT>
<DD> Cancels the prompt.  No search takes place.

<DT>First Line</DT>
<DD> Takes you back to the composer with the cursor on the first character
of the first line of text.

<DT>Last Line</DT>
<DD> Takes you back to the composer with the cursor on the last character
of the last line of text.

<DT>Replace (Optional)</DT>
<DD> This sub-command is enabled by the 
<A HREF="h_config_enable_search_and_repl">&quot;enable-search-and-replace&quot;</A>
feature; see its help screen for details on how replacing works.

</DL>

&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_to ====
<HTML>
<HEAD>
<TITLE>THE MESSAGE COMPOSER'S TO FIELD</TITLE>
</HEAD>
<BODY>
<H1>THE MESSAGE COMPOSER'S TO FIELD</H1>

<H2>The &quot;To:&quot; field</H2>
The address you enter here must be a valid email address which is reachable
from your site. 

<H2>Email Address Format</H2>
You may enter a full name and email address, 
<!--chtml if pinemode="os_windows"-->
<!--chtml else-->
a local (meaning, on the same 
host as the one you are running Pine on) username that Pine will
complete for you, 
<!--chtml endif-->
the nickname of someone in a 
<A HREF="h_abook_opened">Pine Address Book</A>, or a local
mail alias defined by your system administrator.  When you move the cursor
out of this field, the nicknames will be expanded to the addresses in your
address book, and the local usernames will be expanded to include the 
persons' actual names.  You may enter as many addresses as you wish, but they 
must be separated by commas.  You can move around this and other header fields
with the arrow keys and use many of the usual composer editing keys.
<P>
<UL>
<LI><A HREF="h_address_format">Explanation of Address formats</A>
</UL>

<P>
<H2>MESSAGE HEADER COMMANDS</H2>
<!--chtml if pinemode="function_key"-->
CURSOR&nbsp;MOTION&nbsp;KEYS----------------------|EDITING&nbsp;KEYS-------------------------<BR>
^B&nbsp;(Left&nbsp;Arrow)&nbsp;&nbsp;&nbsp;&nbsp;Back&nbsp;character&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Delete&nbsp;current&nbsp;character<BR>
^F&nbsp;(Right&nbsp;Arrow)&nbsp;&nbsp;&nbsp;Forward&nbsp;character&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^H&nbsp;(DEL)&nbsp;Delete&nbsp;previous&nbsp;character<BR>
^P&nbsp;(Up&nbsp;Arrow)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Previous&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<BR>
^N&nbsp;(Down&nbsp;Arrow)&nbsp;&nbsp;&nbsp;&nbsp;Next&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;F9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Cut&nbsp;marked&nbsp;text&nbsp;or<BR>
^A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Beginning&nbsp;of&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;delete&nbsp;current&nbsp;line<BR>
^E&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;End&nbsp;of&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;F10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Undelete&nbsp;line(s)<BR>
F7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Previous&nbsp;page&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^W&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_composer_search">Whereis</A>&nbsp;(search&nbsp;text)<BR>
F8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Next&nbsp;page&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|-------------------------------------<BR>
^@&nbsp;(Ctrl-SPACE)&nbsp;&nbsp;&nbsp;&nbsp;Next&nbsp;word&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|SCREEN/COMPOSITION&nbsp;COMMANDS<BR>
----------------------------------------|<BR>
MESSAGE&nbsp;COMMANDS&nbsp;&nbsp;|&nbsp;GENERAL&nbsp;COMMANDS&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;F12&nbsp;&nbsp;&nbsp;&nbsp;To&nbsp;Addressbook/Browser<BR>
F3&nbsp;&nbsp;&nbsp;<A HREF="h_compose_cancel">Cancel</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;F1&nbsp;&nbsp;&nbsp;&nbsp;Get&nbsp;help&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;F4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Attach&nbsp;File<BR>
F11&nbsp;&nbsp;<A HREF="h_common_postpone">Postpone</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;^Z&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_common_suspend">Suspend</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^L&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Redraw&nbsp;Screen<BR>
F2&nbsp;&nbsp;&nbsp;<A HREF="h_compose_send">Send</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;F5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_compose_richhdr">Rich&nbsp;Headers</A><BR>
<!--chtml else-->
CURSOR&nbsp;MOTION&nbsp;KEYS----------------------|EDITING&nbsp;KEYS-------------------------<BR>
^B&nbsp;(Left&nbsp;Arrow)&nbsp;&nbsp;&nbsp;&nbsp;Back&nbsp;character&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Delete&nbsp;current&nbsp;character<BR>
^F&nbsp;(Right&nbsp;Arrow)&nbsp;&nbsp;&nbsp;Forward&nbsp;character&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^H&nbsp;(DEL)&nbsp;Delete&nbsp;previous&nbsp;character<BR>
^P&nbsp;(Up&nbsp;Arrow)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Previous&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;<BR>
^N&nbsp;(Down&nbsp;Arrow)&nbsp;&nbsp;&nbsp;&nbsp;Next&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^K&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Cut&nbsp;marked&nbsp;text&nbsp;or<BR>
^A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Beginning&nbsp;of&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;delete&nbsp;current&nbsp;line<BR>
^E&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;End&nbsp;of&nbsp;line&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^U&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Undelete&nbsp;line(s)<BR>
^Y&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Previous&nbsp;page&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<BR>
^V&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Next&nbsp;page&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|-------------------------------------<BR>
^@&nbsp;(Ctrl-SPACE)&nbsp;&nbsp;&nbsp;&nbsp;Next&nbsp;word&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|SCREEN/COMPOSITION&nbsp;COMMANDS<BR>
----------------------------------------|<BR>
MESSAGE&nbsp;COMMANDS&nbsp;&nbsp;|&nbsp;GENERAL&nbsp;COMMANDS&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^T&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;To&nbsp;Addressbook/Browser<BR>
^C&nbsp;&nbsp;&nbsp;<A HREF="h_compose_cancel">Cancel</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;^G&nbsp;&nbsp;&nbsp;&nbsp;Get&nbsp;help&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^J&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Attach&nbsp;File<BR>
^O&nbsp;&nbsp;&nbsp;<A HREF="h_common_postpone">Postpone</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;^Z&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_common_suspend">Suspend</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^L&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Redraw&nbsp;Screen<BR>
^X&nbsp;&nbsp;&nbsp;<A HREF="h_compose_send">Send</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;^R&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="h_compose_richhdr">Rich&nbsp;Headers</A><BR>
<!--chtml endif-->

<P>
NOTE:
<OL>
 <LI>For help on a particular command, hilite the bold text associated
with it above and hit Return.
 <LI> The availability of certain commands 
is determined by Pine configuration files and system capabilities.
At some sites, certain commands may not be available due to security or
support concerns.
</OL>

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_cc ====
<HTML>
<HEAD>
<TITLE>THE MESSAGE COMPOSER'S CC FIELD</TITLE>
</HEAD>
<BODY>
<H1>THE MESSAGE COMPOSER'S CC FIELD</H1>
The Cc: field is just like the To: field, except it is used for addressees
that you wish to send a &quot;carbon&quot; copy to.  That is, the message is 
not directly meant directly &quot;for&quot; these recipients, but you wanted 
them to see the message.  The only difference the recipients see is that their 
name is in the Cc: field, rather than the To: field.
<P>
For help with Cc: field editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<P>
<UL>
<LI><A HREF="h_address_format">Explanation of Address formats</A>
</UL>
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_bcc ====
<HTML>
<HEAD>
<TITLE>THE MESSAGE COMPOSER'S BCC FIELD</TITLE>
</HEAD>
<BODY>
<H1>THE MESSAGE COMPOSER'S BCC FIELD</H1>
The &quot;Bcc:&quot; (Blind carbon copy) header is used when you wish to send 
a copy of the message to one or more people whose addresses you do not
wish disclosed, either to reduce clutter or for confidentiality.
<P>
The format of the Bcc: field is just the same as the To: and Cc: fields in
the way the addresses are entered.  The recipients listed here will
receive a copy of the message, but --assuming your site's mail transport
software is properly configured-- their addresses will not show up in the
headers of the message, as delivered to all of the recipients.  The To:
and Cc:  recipients will not know a copy was sent to the Bcc: recipients.
<P>
Note: if there is no To: or Cc: or Lcc: address in the message, Pine
will automatically generate and place in the To: field a pseudo-address of 
  &quot;Undisclosed recipients: ;&quot;
or whatever string has been specified in the 
<A HREF="h_config_empty_hdr_msg">&quot;empty-header-message&quot;</A>
variable.
<P>
The reason for this is to avoid embarrassment caused by some Internet
mail transfer software that interprets a &quot;missing&quot; To: header as 
an error and replaces it with an Apparently-to: header that may contain
the addresses you entered on the Bcc: line.  In addition, it may be
less disconcerting to Bcc: recipients to see <B>something</B> in the To: field.
<P>
You can manipulate what text ends up on the (originally) empty To:
field.  Just remember to put a colon and semicolon at the end of the
field, which is a special notation denoting that it is not a real address.
<P>
For information on message header editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<P>
<UL>
<LI><A HREF="h_address_format">Explanation of Address formats</A>
</UL>
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_lcc ====
<HTML>
<HEAD>
<TITLE>THE MESSAGE COMPOSER'S LCC FIELD</TITLE>
</HEAD>
<BODY>
<H1>THE MESSAGE COMPOSER'S LCC FIELD</H1>
The &quot;Lcc:&quot; (List carbon copy) header is intended to be used when
you wish to send a message to a list of people but avoid having all
of their addresses visible, in order to reduce clutter when the
message is received.
<P>
It is similar to the 
<A HREF="h_composer_bcc">&quot;Bcc&quot; (Blind carbon copy) header</A> 
in that individual
addressees are hidden, but Lcc is designed to work specifically with
distribution lists you have created in your 
<A HREF="h_abook_opened">Pine Address Book</A>.  Placing
the nickname of the list on the Lcc line will result in the full name of
your Pine Address Book list being placed on the To: line of the message,
using a special notation that distinguishes it from a real address. You
must leave the To: line blank for your list name to appear there.
<P>
For example, if you have this list entered in your Address Book:<PRE>

	largo         Key Largo List       DISTRIBUTION LIST:
					   bogie@mgm.com
					   lauren@mgm.com
					   walter@mgm.com</PRE>


and you enter &quot;largo&quot; on the Lcc: line while composing a message, 
the result is:<PRE>

	To      : Key Largo List: ;
	Cc      :
	Bcc     :
	Fcc     : sent-mail
	Lcc     : Key Largo List &lt;bogie@mgm.com&gt;,
		  lauren@mgm.com,
		  walter@mgm.com
	Subject :</PRE>

Each recipient listed on the Lcc: line receives a copy of the message
without their address being visible (as though they were listed on the
Bcc: line). The colon-semicolon notation used to put the full-name of the
list on the To: line is a special address format that doesn't specify any
actual addressees, but does give some information to the recipients of the
message.
<P>
Note: if after entering an LCC, you delete the list name that is placed
on the To: line, then recipients will see <PRE>
       To: Undisclosed recipients: ;</PRE>

(or whatever string is defined in the 
<A HREF="h_config_empty_hdr_msg">&quot;empty-header-message&quot;</A>
variable) just as in the BCC case. 
<P>
For help with Lcc: field editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<P>
<UL>
<LI><A HREF="h_address_format">Explanation of Address formats</A>
</UL>
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_from =======
<HTML>
<HEAD>
<TITLE>THE MESSAGE COMPOSER'S FROM FIELD</TITLE>
</HEAD>
<BODY>
<H1>THE MESSAGE COMPOSER'S FROM FIELD</H1>

This header carries your return address.  It is the address toward which
replies (and often, future unrelated correspondence) will be directed,
unless you have <A HREF="h_config_custom_hdrs">defined an optional 
&quot;Reply-To:&quot; header</A> in the SETUP CONFIGURATION screen.  Make 
sure this address is correct.
<P>
For help with message header editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<P>
<UL>
<LI><A HREF="h_address_format">Explanation of Address formats</A>
</UL>
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_reply_to =======
<HTML>
<HEAD>
<TITLE>THE MESSAGE COMPOSER'S REPLY-TO FIELD</TITLE>
</HEAD>
<BODY>
<H1>THE MESSAGE COMPOSER'S REPLY-TO FIELD</H1>

Most people should not need this header. The Reply-To: header is used in
cases where you would like replies to your messages to be directed to an
address other than your normal &quot;From:&quot; address.  This is atypical, 
but can happen when you use multiple machines and do not have the same account
name on each one, or when you wish to direct certain replies to accounts
or folders designated for specific classes of correspondence.
<P>
For help with message header editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<P>
<UL>
<LI><A HREF="h_address_format">Explanation of Address formats</A>
</UL>

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_custom_addr ====
<HTML>
<HEAD>
<TITLE>CUSTOMIZED HEADER FIELD</TITLE>
</HEAD>
<BODY>
<H1>CUSTOMIZED HEADER FIELD</H1>
This is a customized header, i.e. not one that is part of Pine's normal
set of Compose headers.
<P>
For help with message header editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<P>
<UL>
<LI><A HREF="h_address_format">Explanation of Address formats</A>
</UL>
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_custom_free ====
<HTML>
<HEAD>
<TITLE>CUSTOMIZED HEADER FIELD</TITLE>
</HEAD>
<BODY>
<H1>CUSTOMIZED HEADER FIELD</H1>
This is a customized header, i.e. not one that is part of Pine's normal
set of Compose headers.
<P>
This field consists of arbitrary text.
<P>
For help with message header editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_composer_news =====
<HTML>
<HEAD>
<TITLE>THE MESSAGE COMPOSER'S NEWSGRPS LINE</TITLE>
</HEAD>
<BODY>
<h1>THE MESSAGE COMPOSER'S NEWSGRPS LINE</h1>
Use the newsgroups line to specify any and all USENET newsgroups to which
your message should be posted.  When composing a message from scratch, this
line may be hidden.  If so, just press the rich headers command
(<!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif-->)
to make it visible.
<P>
<EM>Be aware</EM> that when you post to a newsgroup thousands of
people will be reading your message.  Also, you or your system manager
must have defined a &quot;nntp-server&quot; in your Pine configuration
in order for you to be able to post.
<P>
For help with message header editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_fcc ====
<html>
<header>
<title>THE MESSAGE COMPOSER'S FCC FIELD</title>
</header>
<body>
<h1>THE MESSAGE COMPOSER'S FCC FIELD</h1>
The FCC (File Carbon Copy) specifies the folder used to keep a copy of
each outgoing message.  The default value can be configured with the
"default-fcc" and "fcc-name-rule" options.  You can change or remove
the file carbon copy on any message you send by editing the FCC header.<p>

You may type ^T to get a list of all your folders and select one to use as
the FCC for this message.<p>

For help with message header editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<p>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
======= h_composer_subject ====
<html>
<header>
<title>THE MESSAGE COMPOSER'S SUBJECT FIELD</title>
</header>
<body>
<h1>THE MESSAGE COMPOSER'S SUBJECT FIELD</h1>

The subject header provides a place to enter a few words that summarize
the topic of the message you are sending.  You may leave this line blank,
but it is considered a courtesy to use a meaningful subject.<p>

For help with message header editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
======= h_composer_attachment ====
<HTML>
<HEAD>
<TITLE>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</TITLE>
</HEAD>
<BODY>
<H1>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</H1>

The &quot;Attchmnt:&quot; field is where you specify what file or
files you'd like attached to
the message you are composing.  Those files must reside on the machine
running Pine. If your file is on a PC or Mac and you run Pine with an
account on a Unix machine, you'll have to transfer it before attaching it.
Contact local computer support people for assistance with transferring.

<P>
The file name
given can be an absolute file path name for your system
<!--chtml if pinemode="os_windows"-->
(for example, &quot;H:&#92;SIGFILES&#92;FULLINFO.TXT&quot;), a file
with a relative pathname, or simply a file name without
drive or directory specification.  
<!--chtml else-->
(for example, &quot;/tmp/exported.earlier&quot; on Unix hosts), 
a file in your home directory, or a file path relative to your 
home directory.  In Unix Pine, you may use &quot;~&quot; to refer to 
your home directory or &quot;~user&quot; to refer to another
account's home directory.
<!--chtml endif--><P>
No wild card characters may be used.
<P>If the 
<A HREF="h_config_use_current_dir">&quot;use-current-dir&quot;</A>
feature is set, names are relative to your current working directory 
<!--chtml if pinemode="running"-->
(which, at least for your current Pine &quot;session,&quot; 
is &quot;<!--#echo var="CURRENT_DIR"-->&quot;) 
<!--chtml endif-->
rather than your home directory
<!--chtml if pinemode="running"-->
(which, in the present configuration of your system, is
 &quot;<!--#echo var="HOME_DIR"-->&quot;) 
<!--chtml endif-->
.
<P>
Pine uses MIME encoding for attachments, so binaries and files of any
length can safely be delivered to any MIME-capable mail reading program.
If you send an attachment to someone who does not have a MIME-capable mail
reading program yet, then the main message text will be readable, but
attachments (even attachments which are just plain text) are not.
<P>

Typing the filename on the Attchmnt: line achieves the same
result as using the 
<!--chtml if pinemode="function_key"-->
F6
<!--chtml else-->
Ctrl-J
<!--chtml endif--> command.
<P>

If you Forward a message with attachments, you may delete them from your
Forwarded message by editing the Attchmnt header line.
<P>

For help with message header editing
commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_ctrl_j ====
<HTML>
<HEAD>
<TITLE>COMPOSER ATTACH</TITLE>
</HEAD>
<BODY>
After the
<!--chtml if pinemode="function_key"-->
F6
<!--chtml else-->
Ctrl-J
<!--chtml endif--> command:
At the &quot;File to attach:&quot; prompt, enter the name of the 
existing file to attach to your message.  
If the 
<A HREF="h_config_enable_tab_complete">&quot;enable-tab-completion&quot;</A>
feature is set in SETUP CONFIGURATION, 
you need only enter the beginning of the filename (enough of it to uniquely 
identify the file) and press TAB to complete it.

Or, press ^T to use the BROWSER screen for 
selecting the file.  <P>
For more information on attaching files, see the help screen for the 
composer's 
<A HREF="h_composer_attachment">Attchmnt: field</A>, which is normally hidden,
but can be revealed using the 
<!--chtml if pinemode="function_key"-->
F5
<!--chtml else-->
Ctrl-R
<!--chtml endif--> 
command with the cursor positioned above the
&quot;----- Message Text -----&quot; line in the COMPOSE MESSAGE screen.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_edit_nav_cmds =========
<HTML>
<HEAD>
<TITLE>Composer Editing Commands Explained</TITLE>
</HEAD>
<BODY>
<H1>EDITING and NAVIGATION COMMANDS</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
^B (Left Arrow)    Back character       | ^D       Delete current character
^F (Right Arrow)   Forward character    | ^H (DEL) Delete previous character
^P (Up Arrow)      Previous line        |
^N (Down Arrow)    Next line            | F9       Cut marked text or
^A                 Beginning of line    |            delete current line
^E                 End of line          | F10      Undelete line(s)
F7                 Previous page        |
F8                 Next page            |-------------------------------------
^@ (Ctrl-SPACE)    Next word            | MISCELLANEOUS COMMANDS
----------------------------------------|
EXIT COMMANDS    |  GENERAL COMMANDS    | F12    To Addressbook
F3   Cancel      |   F1    Get help     | F12    RichView (expand lists)
F2  eXit/save    |   ^Z    Suspend      | ^L     Redraw Screen
</PRE>
<!--chtml else-->
<PRE>
CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
^B (Left Arrow)    Back character       | ^D       Delete current character
^F (Right Arrow)   Forward character    | ^H (DEL) Delete previous character
^P (Up Arrow)      Previous line        |
^N (Down Arrow)    Next line            | ^K       Cut marked text or
^A                 Beginning of line    |            delete current line
^E                 End of line          | ^U       Undelete line(s)
^Y                 Previous page        |
^V                 Next page            |-------------------------------------
^@ (Ctrl-SPACE)    Next word            | MISCELLANEOUS COMMANDS
----------------------------------------|
EXIT COMMANDS    |  GENERAL COMMANDS    | ^T     To Addressbook
^C   Cancel      |   ^G    Get help     | ^R     RichView  (expand lists)
^X   eXit/save   |   ^Z    Suspend      | ^L     Redraw Screen
</PRE>
<!--chtml endif-->
&lt;End of help on this topic&gt;
</BODY>
</HTML>
===== h_composer_sigedit =====
<HTML>
<HEAD>
<TITLE>Signature Editor Commands Explained</TITLE>
</HEAD>
<BODY>
<H1>SIGNATURE EDITOR COMMANDS</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
CURSOR MOTION KEYS                     |EDITING KEYS
  ^B (Left Arrow)   Back character     | ^D       Delete current character
  ^F (Right Arrow)  Forward character  | ^H (DEL) Delete previous character
  ^P (Up Arrow)     Previous line      | ^^       Set a mark
  ^N (Down Arrow)   Next line          | F9       Cut marked text or
  ^A                Beginning of line  |           delete current line
  ^E                End of line        | F10       Paste text, undelete lines
  F7                Previous page      |           cut with ^K, or unjustify
  F8                Next page          |-------------------------------------
  ^@ (Ctrl-SPACE)   Next word          |SCREEN/COMPOSITION COMMANDS
---------------------------------------| F6       Whereis (search for string)
MESSAGE COMMANDS | GENERAL COMMANDS    | F12      Spell checker
 F3   Cancel     |  F1    Get help     | F4       Justify paragraph
                 |  ^Z    Suspend      | ^L       Redraw Screen
 F2   Send       |  F6    Alt. editor  | F5       Read in a file
</PRE>
<!--chtml else-->
<PRE>
CURSOR MOTION KEYS                     |EDITING KEYS
  ^B (Left Arrow)   Back character     | ^D       Delete current character
  ^F (Right Arrow)  Forward character  | ^H (DEL) Delete previous character
  ^P (Up Arrow)     Previous line      | ^^       Set a mark
  ^N (Down Arrow)   Next line          | ^K       Cut marked text or
  ^A                Beginning of line  |           delete current line
  ^E                End of line        | ^U        Paste text, undelete lines
  ^Y                Previous page      |           cut with ^K, or unjustify
  ^V                Next page          |-------------------------------------
  ^@ (Ctrl-SPACE)   Next word          |SCREEN/COMPOSITION COMMANDS
---------------------------------------| ^W       <A HREF="h_composer_search">Whereis</A> (search text)
MESSAGE COMMANDS | GENERAL COMMANDS    | ^T       Spell checker
 ^C   Cancel     |  ^G    Get help     | ^J       <A HREF="h_compose_justify">Justify</A> paragraph
                 |  ^Z    <A HREF="h_common_suspend">Suspend</A>      | ^L       Redraw Screen
 ^X   Send       |  ^_    Alt. editor  | ^R       Read in a file
</PRE>
<!--chtml endif-->

NOTE: The presence or absence of the following commands is determined
by &quot;feature-list&quot; options in your Pine configuration.  Also,
some of these commands may be administratively disabled by your system
manager; if they don't work, please check with your local help desk
before reporting a bug.
<P>
<UL>
 <LI>Suspend (suspends Pine and gives a system prompt)
 <LI>Alternate editor (allows you to compose with your own editor)
</UL>
<P>

Pine does not use the following keys:  Ctrl-S, Ctrl-Q, Ctrl-],
Ctrl-&#92;, ESC
<P>

NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
<A HREF="h_special_xon_xoff">&quot;XOFF/XON&quot;</A>.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_abook_nick =======
<HTML>
<HEAD>
<TITLE>Addressbook Nickname Explained</TITLE>
</HEAD>
<BODY>
This is a short nickname for this address book entry.  If it is used in
place of an address from the composer, the composer will fill in the
address(es) for the entry that matches the nickname. 
<P>

Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_abook_full =======
<HTML>
<HEAD>
<TITLE>Addressbook Fullname Explained</TITLE>
</HEAD>
<BODY>
This is the full name field for this entry.  If this is going to be a
distribution list (more than one address), it should be a descriptive
phrase describing the list.  It will be included in the mail header if you
put the list in the To: or CC: field, or in the To: line if you put the
list in the Lcc: field.  It's OK to leave this field blank (and OK to
leave any of the other fields blank, too). If this address book entry is
going to be a simple entry with just one address, then this field is the
person's name. When you send mail to this entry, this is the field to the
left of the brackets. That is, it is the most readable part of the 
address. For example, in the sample address:
<PRE>
       John Doe &lt;jdoe@some.domain&gt;
</PRE>
"John Doe" is the full name field. If you are sorting your address book
with one of the options that uses full names, then it might be useful to
enter the full name as "Last, First", for example:
<PRE>
       Doe, John
</PRE>
so that it will be sorted using Doe instead of John. This will be changed
back into John Doe when you use it.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_abook_fcc =======
<HTML>
<HEAD>
<TITLE>Addressbook Fcc Explained</TITLE>
</HEAD>
<BODY>
If this entry is the first one in the To: line of an outgoing message,
this field will be used for the Fcc (File Carbon Copy) instead of whatever
you would normally get (which depends on which
<A HREF="h_config_saved_msg_name_rule">"saved-msg-name-rule"</A>
you've chosen). 
<P>
If this field consists of two double quotes (&quot;&quot;) that tells Pine
that you don't want any Fcc associated with this entry.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_combined_abook_display =====
<HTML>
<HEAD>
<TITLE>FEATURE: combined-addrbook-display</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: combined-addrbook-display</H1>

This feature affects the address book display screens.
Normally, expanding an address book from the ADDRESS BOOK LIST screen
will cause the remaining address books and directory servers to disappear
from the screen, leaving only the entries of the expanded address book.
If this feature is set, then the other address books will remain on the screen,
so that all of the address books can be present at once.

<P>
The way that commands work won't be changed.
For example, the Select All command will select all of the entries in the
current address book, not all of the entries in all of the address books.
The WhereIs command will change a little.
It will search through all of the text on the screen plus all of the entries
from expanded address books.

<P>
When this feature is set, the setting of the feature
<A HREF="h_config_expanded_addrbooks">&quot;expanded-view-of-addressbooks&quot;</A>
has an effect.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_expanded_addrbooks =====
<HTML>
<HEAD>
<TITLE>FEATURE: expanded-view-of-addressbooks</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: expanded-view-of-addressbooks</H1>

If multiple address books (either personal or global) are defined, and you
wish to have them all expanded implicitly upon entering the ADDRESS BOOK
screen, then set this feature. This feature will have no effect unless the
feature
<A HREF="h_config_combined_abook_display">&quot;combined-addrbook-display&quot;</A>
is also set.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_combined_folder_display =====
<HTML>
<HEAD>
<TITLE>FEATURE: combined-folder-display</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: combined-folder-display</H1>

This feature affects the folder list display screens.
Normally, each folder list is viewed within its collection only.  This
command allows folder lists to be viewed within a single screen that
combines the contents of all collections.

<P>
The way that commands work won't be changed.
For example, the Select All command will select all of the folders in the
current collection, not all of the entries in all of the collections.
The WhereIs command will change a little.
It will search through all of the folders in the current collection as well
as all the folder in any other expanded collection.

<P>
When this feature is set, the setting of the feature
<A HREF="h_config_expanded_folders">&quot;expanded-view-of-folders&quot;</A>
has an effect.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_combined_subdir_display =====
<HTML>
<HEAD>
<TITLE>FEATURE: combined-subdirectory-display</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: combined-subdirectory-display</H1>

This feature affects the Folder List screen when
the
<A HREF="h_config_combined_folder_display">&quot;combined-folder-display&quot;</A>
feature is enabled.  Normally, selecting a directory from the Folder
List takes you into a new screen displaying only the contents of
that directory.

<P>
Enabling this feature will cause the contents of the selected
directory to be
displayed within the boundaries of the &quot;Collection&quot; it
is a part of.  All previously displayed collections will remain
in the screen.

<P>
The way that commands work won't be changed.
For example, the Select All command will select all of the folders in the
directory, as opposed to all of the entries in all of the collections.
The WhereIs command will change a little.
It will search through all of the folders in the current collection as well
as all the folder in any other expanded collection.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_separate_fold_dir_view =====
<HTML>
<HEAD>
<TITLE>FEATURE: separate-folder-and-directory-display</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: separate-folder-and-directory-display</H1>

This feature affects folder collections wherein a folder
and directory can have the same name.  By default, Pine displays them
only once, denoting that it is both a folder and directory by appending
the folder name with the hierarchy character enclosed
in square brackets.


<P>
Enabling this feature will cause Pine to display such names
separately marking the name representing a directory with a trailing
hierarchy delimiter (typically the slash, &quot;/&quot;, character).

<P>
The feature also alters the command set slightly.  By default, the
right-arrow descends into the directory, while hitting the Return key will
cause the folder by that name to be opened.

<P>
With this feature set, the Return key will open the hilited folder, or
enter the hilited directory.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_expanded_folders =====
<HTML>
<HEAD>
<TITLE>FEATURE: expanded-view-of-folders</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: expanded-view-of-folders</H1>

If multiple folder collections are defined, and you
wish to have them all expanded implicitly upon entering the FOLDER LIST
screen, then set this feature. This feature will have no effect unless the
feature
<A HREF="h_config_combined_folder_display">&quot;combined-folder-display&quot;</A>
is also set.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_server =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: ldap-server</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: ldap-server</H1>
This is the name of the host where an LDAP server is running.
<P>
To find out whether your organization has its own LDAP server, 
contact its computing support staff.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_base =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: search-base</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: search-base</H1>

This is the search base to be used on this server.  It functions as a filter 
by restricting your searches in the LDAP server database
to the specified contents of the specified fields.  Without it, searches 
submitted to this directory server may fail.  It might be something
like:

<PRE>
      O = &lt;Your Organization Name&gt;, C = US
</PRE>
or it might be blank.  
(Some LDAP servers actually ignore anything specified here.)
<P>
If in doubt what parameters you should specify here, 
contact the maintainers of the LDAP server.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_port =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: port</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: port</H1>

This is the TCP port number to be used with this LDAP server. If you leave
this blank port 389 will be used.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_nick =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: nickname</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: nickname</H1>

This is a nickname to be used in displays. If you don't supply a
nickname the server name
(<A HREF="h_config_ldap_server">&quot;ldap-server&quot;</A>)
will be used instead.  This option is strictly for your convenience.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_opts_impl =======
<HTML>
<HEAD>
<TITLE>LDAP FEATURE: use-implicitly-from-composer</TITLE>
</HEAD>
<BODY>
<H1>LDAP FEATURE: use-implicitly-from-composer</H1>

Set this to have lookups done to this server implicitly from the composer.
If an address doesn't look like a fully-qualified address, it will be looked
up in your address books, and if it doesn't match a nickname there, then it
will be looked up on the LDAP servers which have this feature set.
Also see the LDAP feature
<A HREF="h_config_ldap_opts_rhs">&quot;lookup-addrbook-contents&quot;</A>
and the Setup/Config feature
<A HREF="h_config_add_ldap">&quot;ldap-result-to-addrbook-add&quot;</A>.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_ldap_opts_rhs =====
<HTML>
<HEAD>
<TITLE>LDAP FEATURE: lookup-addrbook-contents</TITLE>
</HEAD>
<BODY>
<H1>LDAP FEATURE: lookup-addrbook-contents</H1>

Normally implicit LDAP lookups from the composer are done only for the
strings you type in from the composer screen. In other words, you type in
something in the To or CC field and press return, then the string is looked up.
First that string is looked up in your address books. If a match is found
there, then the results of that match are looked up again. If you place
a string in your address book that you want to have looked up on the LDAP
directory server, you need to turn on this feature. If you set this feature
for a server, you almost always will also want to set the
<A HREF="h_config_ldap_opts_impl">&quot;use-implicitly-from-composer&quot;</A>
feature. An example might serve to best illustrate this feature.
<P>
If an LDAP lookup of &quot;William Clinton&quot; normally returns an
entry with an
address of pres@whitehouse.gov, then you might put an entry in your address
book that looks like:
<PRE>
    Nickname     Address
    bill         &quot;William Clinton&quot;
</PRE>
Now, when you type &quot;bill&quot; into an
address field in the composer Pine will
find the &quot;bill&quot; entry in your address book.
It will replace &quot;bill&quot; with
&quot;William Clinton&quot;.
It will then search for an entry with that nickname
in your address book and not find one. If this feature
is set, Pine will then attempt to lookup
&quot;William Clinton&quot; on the LDAP server and find the entry with address
pres@whitehouse.gov.
<P>
A better way to accomplish the same thing is probably to use the feature
<A HREF="h_config_ldap_opts_ref">&quot;save-search-criteria-not-result&quot;</A>.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_ldap_opts_ref =====
<HTML>
<HEAD>
<TITLE>LDAP FEATURE: save-search-criteria-not-result</TITLE>
</HEAD>
<BODY>
<H1>LDAP FEATURE: save-search-criteria-not-result</H1>

Normally when you save the results of an LDAP directory lookup to your
address book the results of the lookup are saved. If this feature is set
and the entry being saved was found on this directory server, then the
search criteria is saved instead of the results of the search. When this
address book entry is used in the future, instead of copying the results
from the address book the directory lookup will be done again. This could
be useful if the copied result might become stale because the data on
the directory server changes (for example, the entry's email address changes).
You probably don't want to set this feature if the server is at all slow or
unreliable.
<P>
The way this actually works is that instead of saving the email address
in your address book, Pine saves enough information to look up the same
directory entry again. In particular, it saves the server name and the
distinguished name of the entry. It's possible that the server administrators
might change the format of distinguished names on the server, or that the
entry might be removed from the server. If Pine notices this, you will be warned
and a backup copy of the email address will be used. You may want to create
a new entry in this case, since you will get the annoying warning every
time you use the old entry. You may do that by Saving the entry to a new
nickname in the same address book. You will be asked whether or not you
want to use the backup email address.
<P>
A related feature in the Setup/Config screen is
<A HREF="h_config_add_ldap">&quot;ldap-result-to-addrbook-add&quot;</A>.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_opts_nosub =======
<HTML>
<HEAD>
<TITLE>LDAP FEATURE: disable-ad-hoc-space-substitution</TITLE>
</HEAD>
<BODY>
<H1>LDAP FEATURE: disable-ad-hoc-space-substitution</H1>

Spaces in your input are normally handled specially.
Each space character is replaced
by
<PRE>
     * &lt;SPACE&gt;
</PRE>
in the search query (but not by &quot;* &lt;SPACE&gt; *&quot;).
The reason this is done is so the input string
<PRE>
     Greg Donald
</PRE>
(which is converted to &quot;Greg* Donald&quot;) will match
the names &quot;Greg Donald&quot;,
&quot;Gregory Donald&quot;, &quot;Greg F. Donald&quot;, and
&quot;Gregory F Donald&quot;; but it won't match &quot;Greg McDonald&quot;.
If the &quot;Search-Rule&quot; you were using was &quot;begins-with&quot;,
then it would also match the name &quot;Greg Donaldson&quot;.
<P>
Turning on this feature will disable this substitution.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_ldap_searchtypes =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: Search-Type</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: Search-Type</H1>

This affects the way that LDAP searches are done.
In particular, this tells the server where to look for the string to be matched.
If set to &quot;name&quot; then the string that is being searched for will
be compared with the string in the
&quot;Name&quot; field on the server
(technically, it is the &quot;commonname&quot; field on the server).
&quot;Surname&quot; means we're looking for a
match in the &quot;Surname&quot; field on the
server (actually the &quot;sn&quot; field).
&quot;Givenname&quot; really is &quot;givenname&quot;
and &quot;email&quot; is the electronic mail address (this is actually the field
called &quot;mail&quot; or &quot;electronicmail&quot; on the server).
The other three types are combinations of
the types listed so far. &quot;Name-or-email&quot;
means the string should appear
in either the &quot;name&quot; field OR the &quot;email&quot; field.
Likewise, &quot;surname-or-givenname&quot;
means &quot;surname&quot; OR &quot;givenname&quot;
and &quot;sur-or-given-or-name-or-email&quot; means the obvious thing.
<P>
This search TYPE is combined with the
search <A HREF="h_config_ldap_searchrules">RULE</A>
to form the actual search query.
<P>
The usual default value for this
option is &quot;sur-or-given-or-name-or-email&quot;.
This type of search may be slow on some servers.
Try &quot;name-or-email&quot;, which is often
faster, or just &quot;name&quot; if the performance seems to be a problem.
<P>
Some servers have been configured with different attribute names for
these four fields.
In other words, instead of using the attribute name &quot;mail&quot;
for the email address field, the server might be configured to use something
else, for example, &quot;rfc822mail&quot; or &quot;internetemailaddress&quot;.
Pine can be configured to use these different attribute names by using
the four configuration options:
<P><UL>
<LI><A HREF="h_config_ldap_email_attr">&quot;EmailAttribute&quot;</A>
</UL>
<P><UL>
<LI><A HREF="h_config_ldap_cn_attr">&quot;NameAttribute&quot;</A>
</UL>
<P><UL>
<LI><A HREF="h_config_ldap_sn_attr">&quot;SurnameAttribute&quot;</A>
</UL>
<P><UL>
<LI><A HREF="h_config_ldap_gn_attr">&quot;GivennameAttribute&quot;</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_ldap_searchrules =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: Search-Rule</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: Search-Rule</H1>

This affects the way that LDAP searches are done.
If set to &quot;equals&quot; then
only exact matches count.
&quot;Contains&quot; means that the string you type in
is a substring of what you are matching against.
&quot;Begins-with&quot; and &quot;ends-with&quot;
mean that the string starts or ends with the string you type in.
<P>
Spaces in your input are normally handled specially, but you can turn that
special handling off with the
<A HREF="h_config_ldap_opts_nosub">&quot;disable-ad-hoc-space-substitution&quot;</A>
feature.
<P>
The usual default value for this option is &quot;begins-with&quot;.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_email_attr =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: EmailAttribute</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: EmailAttribute</H1>

This is the name of the attribute which is searched for when looking for
an email address. The default value for this option is &quot;mail&quot; or
&quot;electronicmail&quot;.
If the server you are using uses a different attribute name for the email
address, put that attribute name here.
<P>
This will affect the search filter used if your Search-Type is one that
contains a search for &quot;email&quot;.
It will also cause the attribute value matching this attribute name to be used
as the email address when you look up an entry from the composer.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_sn_attr =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: SurnameAttribute</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: SurnameAttribute</H1>

This is the name of the attribute which is searched for when looking for
the surname of the entry. The default value for this option is &quot;sn&quot;.
If the server you are using uses a different attribute name for the surname,
put that attribute name here.
This will affect the search filter used if your Search-Type is one that
contains a search for &quot;surname&quot;.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_gn_attr =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: GivennameAttribute</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: GivennameAttribute</H1>

This is the name of the attribute which is searched for when looking for
the given name of the entry. The default value for this option is &quot;givenname&quot;.
If the server you are using uses a different attribute name for the given name,
put that attribute name here.
This will affect the search filter used if your Search-Type is one that
contains a search for &quot;givenname&quot;.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_cn_attr =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: NameAttribute</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: NameAttribute</H1>

This is the name of the attribute which is searched for when looking for
the name of the entry. The default value for this option is &quot;cn&quot;, which
stands for common name.
If the server you are using uses a different attribute name for the name,
put that attribute name here.
This will affect the search filter used if your Search-Type is one that
contains a search for &quot;name&quot;.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_time =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: Timelimit</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: Timelimit</H1>

This places a limit on the number of seconds the LDAP search will continue.
The default is 30 seconds. A value of 0 means no limit. Note that some servers
may place limits of their own on searches.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_size =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: Sizelimit</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: Sizelimit</H1>

This places a limit on the number of entries returned by the LDAP server.
A value of 0 means no limit. The default is 0. Note that some servers
may place limits of their own on searches.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_ldap_cust =======
<HTML>
<HEAD>
<TITLE>LDAP OPTION: Custom-Search-Filter</TITLE>
</HEAD>
<BODY>
<H1>LDAP OPTION: Custom-Search-Filter</H1>

This one is for advanced users only! If you define this, then the
&quot;Search-Type&quot; and &quot;Search-Rule&quot; defined are both ignored.
However, the feature
<A HREF="h_config_ldap_opts_nosub">&quot;disable-ad-hoc-space-substitution&quot;</A>
is still in effect.
That is, the space substitution will take place even in a custom filter unless
you disable it.
<P>
If your LDAP service stops working and you suspect it might be because
of your custom filter, just delete this filter and try using the
&quot;Search-Type&quot; and &quot;Search-Rule&quot; instead.
Another option that sometimes causes trouble is the
<A HREF="h_config_ldap_base">&quot;search-base&quot;</A> option.
<P>
This variable may be set to the string representation of an LDAP search
filter (see RFC1960). In the places where you want the address string to be
substituted in, put a '%s' in this filter string. Here are some examples:
<P>
A &quot;Search-Type&quot; of &quot;name&quot; with &quot;Search-Rule&quot; of &quot;begins-with&quot;
is equivalent to the &quot;custom-search-filter&quot;
<PRE>
     (cn=%s*)
</PRE>
When you try to match against the string &quot;string&quot; the program replaces
the &quot;%s&quot; with &quot;string&quot; (without the quotes). You may have multiple &quot;%s&quot;'s and
they will all be replaced with the string. There is a limit of 10 &quot;%s&quot;'s.
<P>
A &quot;Search-Type&quot; of &quot;name-or-email&quot; with &quot;Search-Rule&quot;
of &quot;contains&quot; is equivalent to
<PRE>
     (|(cn=*%s*)(mail=*%s*))
</PRE>
<P>
If your server uses a different attribute <EM>name</EM> than
Pine uses by default,
(for example, it uses &quot;rfc822mail&quot; instead of &quot;mail&quot;),
then you may be able to use one or more of the four attribute configuration
options instead of defining a custom filter:
<P><UL>
<LI><A HREF="h_config_ldap_email_attr">&quot;EmailAttribute&quot;</A>
</UL>
<P><UL>
<LI><A HREF="h_config_ldap_cn_attr">&quot;NameAttribute&quot;</A>
</UL>
<P><UL>
<LI><A HREF="h_config_ldap_sn_attr">&quot;SurnameAttribute&quot;</A>
</UL>
<P><UL>
<LI><A HREF="h_config_ldap_gn_attr">&quot;GivennameAttribute&quot;</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_abook_comment =======
<HTML>
<HEAD>
<TITLE>Addressbook Comment Explained</TITLE>
</HEAD>
<BODY>
This is a comment to help you remember what this entry is. The WhereIs
command searches comments so that it is easier to find an entry with a comment
you know about attached to it. This field is not used in the outgoing message.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_abook_addrs =======

This is a list of addresses to send to when sending to this address book
entry.  Each member of the list may be an address or another nickname from
any of your address books.  If it is an address, it is OK to include the
full name field as well as the electronic address portion of that address.
For example, the following are all legitimate entries in this field:

     john               (a nickname in your address book)
     jdoe@some.domain
     John Doe <jdoe@some.domain>

The addresses should be listed separated by commas, just like you would
enter them from the composer.

The only difference between a distribution list and a simple entry with a
single address, is that a distribution list has more than one address   
listed in the Addresses: field, whereas a simple personal entry has just  
one address.

For individual address book entries, if there is a full name in the
Fullname: field (filling in the Fullname: field is not required), it is
used.  If the full name is specified in the Address: field and not in the
Fullname: field, then the full name from the Address: field is used.

If you type the nickname of a distribution list from one of your address 
books in the Lcc: field, then the full name of that list is used in the  
To: field.  If you put a list in the To: or Cc: fields, that list will be
expanded into all of its addresses.  If the list has a full name, then
that will appear at the beginning of the addresses.

Sewing Club <john@somewhere>, nancy@something.else, Sal <sal@here.there>

If the first address in the distribution list also has a full name, then
the list full name and that full name are combined into something like the
following:

Sewing Club -- John Smith <john@somewhere>

If you specify a list via Lcc, the full name is used in the To: line.  If
you specify a list in the To: or Cc: fields, then it uses the same method
as for individual entries for filling in the full name.

For help with editing and navigation commands, check the Help for the
Nickname: field.

<End of help on this topic>
======= h_config_role_nick =======
<HTML>
<HEAD>
<TITLE>Role Nickname Explained</TITLE>
</HEAD>
<BODY>
<H1>Role Nickname Explained</H1>

This is a nickname to help you.
You should have a different nickname for each role you define.
The nickname will be used in the SETUP ROLES screen to allow you to
pick a role to edit.
It will also be used when you send a message to let you know you are
sending with a different role than you use by default.
This field is not used in the outgoing message.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_topat =======
<HTML>
<HEAD>
<TITLE>Role To Pattern Explained</TITLE>
</HEAD>
<BODY>
<H1>Role To Pattern Explained</H1>

If this pattern is non-blank, then for this role to be considered a
match, at least one of the recipients from
the To line of the message being replied to
must match this pattern.
If this pattern is a comma-separated list of patterns, then at least one of the
recipients must match at least one of the patterns.
(Any other non-blank patterns must match, too.)
If the message being replied to has a Resent-To header line, then that is
used in place of the To line.
<P>
If you wish,
you may choose an address from your address book with the
&quot;T&quot; command.
<P>
If you leave all of the patterns blank, that matches any message.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_frompat =======
<HTML>
<HEAD>
<TITLE>Role From Pattern Explained</TITLE>
</HEAD>
<BODY>
<H1>Role From Pattern Explained</H1>

This is just like the To pattern except that it is compared with
the address from the From header of the message being replied to instead
of the addresses from the To header.
<P>
If you wish,
you may choose an address from your address book with the
&quot;T&quot; command.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_senderpat =======
<HTML>
<HEAD>
<TITLE>Role Sender Pattern Explained</TITLE>
</HEAD>
<BODY>
<H1>Role Sender Pattern Explained</H1>

This is just like the To pattern except that it is compared with
the address from the Sender header of the message being replied to instead
of the addresses from the To header.
<P>
If you wish,
you may choose an address from your address book with the
&quot;T&quot; command.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_ccpat =======
<HTML>
<HEAD>
<TITLE>Role Cc Pattern Explained</TITLE>
</HEAD>
<BODY>
<H1>Role Cc Pattern Explained</H1>

This is just like the To pattern except that it is compared with
the addresses from the Cc header of the message being replied to instead
of the addresses from the To header.
<P>
If you wish,
you may choose an address from your address book with the
&quot;T&quot; command.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_newspat =======
<HTML>
<HEAD>
<TITLE>Role News Pattern Explained</TITLE>
</HEAD>
<BODY>
<H1>Role News Pattern Explained</H1>

If this pattern is non-blank, then for this role to be considered a
match, at least one of the news groups from
the Newsgroups line of the message being replied to
must match this pattern.
If this pattern is a comma-separated list of patterns, then at least one of the
news groups must match at least one of the patterns.
(Any other non-blank patterns must match, too.)
<P>
Since all news groups contain a dot, the News pattern which consists
of a single dot will match whenever the message contains a Newsgroups header
and at least one news group.
This can be used to define a default news role when responding to a message
sent to any news group.
<P>
If you leave all of the patterns blank, that matches any message.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_subjpat =======
<HTML>
<HEAD>
<TITLE>Role Subject Pattern Explained</TITLE>
</HEAD>
<BODY>
<H1>Role Subject Pattern Explained</H1>

This is just like the other patterns except that it is compared with
the contents from the Subject of the message being replied to.
<P>
If you enter non-ascii characters in this field then the search will be
done using the character set you have defined with the
<A HREF="h_config_char_set">&quot;character-set&quot;</A>
configuration variable.
(The truly sophisticated may use an alternate character set for a search
by entering the MIME encoding of the header string here.)
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_inick =======
<HTML>
<HEAD>
<TITLE>Initialize Values From Role Explained</TITLE>
</HEAD>
<BODY>
<H1>Initialize Values From Role Explained</H1>

This is a power user feature.
You will usually want to leave this field empty.
The value of this field is the nickname of another one of your roles.
The action values from that other role
(the four items that begin with &quot;Set&quot;)
are used as the initial values of the action items for this role.
If you put something in any of the action fields for this role, that will
override whatever was in the corresponding field of the initializer role.
The fields affected by this field are the fields labeled
&quot;Set From&quot;,
&quot;Set Fcc&quot;,
&quot;Set Signature&quot;, and
&quot;Set Template&quot;.
<P>
You might use this field if the &quot;action&quot; part of one of your roles
is something you want to use in more than one role.
Instead of filling in those action values again for each role, you
may give the nickname of the role where the values are filled in.
It's just a shortcut way to define role actions.
<P>
Here's an example to help explain how this works.
Suppose you have a role with nickname &quot;role1&quot; and role1 has
(among other things)
<P>
<CENTER><SAMP>Set Signature = sig_file1</SAMP></CENTER>
<P>
set.
If in &quot;role2&quot; you set &quot;Initialize settings using role&quot; to
&quot;role1&quot;, then role2 will inherit the Set Signature value
from role1 by default (and any of the three other action values that are set).
So if role2 had
<P>
<CENTER><SAMP>Set Signature =</SAMP></CENTER>
<P>
defined, the signature file used with role2 would be &quot;sig-file1&quot;.
However, if role2 had
<P>
<CENTER><SAMP>Set Signature = sig_file2</SAMP></CENTER>
<P>
defined, then the signature file used with role2 would be &quot;sig-file2&quot;.
<P>
If you wish,
you may choose a nickname from your list of roles by using the
&quot;T&quot; command.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_setfrom =======
<HTML>
<HEAD>
<TITLE>Role Set From Action Explained</TITLE>
</HEAD>
<BODY>
<H1>Role Set From Action Explained</H1>

This describes part of the action to be taken if the patterns for this
role are a match.
This field consists of a single address which will be used as the From
address on the message you are sending.
This should be a fully-qualified address like
<P>
<CENTER><SAMP>Full Name &lt;user@domain&gt;</SAMP></CENTER>
<P>
or just
<P>
<CENTER><SAMP>user@domain</SAMP></CENTER>
<P>
If you wish,
you may choose an address from your address book with the
&quot;T&quot; command.
<P>
If this is left blank, then your normal From address will be used.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_setfcc =======
<HTML>
<HEAD>
<TITLE>Role Set Fcc Action Explained</TITLE>
</HEAD>
<BODY>
<H1>Role Set Fcc Action Explained</H1>

This describes part of the action to be taken if the patterns for this
role are a match.
This field consists of a single folder name which will be used in
the Fcc field of the message you are sending.
You may put anything here that you would normally type into the Fcc
field from the composer.
<P>
In addition, an fcc of &quot;&quot; (two double quotation marks) means
no Fcc.
<P>
A blank field here means that Pine will use its normal rules for deciding
the default value of the Fcc field.
For many roles, perhaps most, it may make more sense for you to use the
other Pine facilities for setting the Fcc.
In particular, if you want the Fcc to depend on who you are sending the
message to then the <A HREF="h_config_fcc_rule">&quot;fcc-name-rule&quot;</A>
is probably more useful.
In that case, you would want to leave the Fcc field here blank.
However, if you have a role that depends on who the message you are replying
to was From, or what address that message was sent to;
then it might make sense to set the Fcc for that role here.
<P>
If you wish,
you may choose a folder from your folder collections by using the
&quot;T&quot; command.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_setsig =======
<HTML>
<HEAD>
<TITLE>Role Set Sig Action Explained</TITLE>
</HEAD>
<BODY>
<H1>Role Set Sig Action Explained</H1>

This describes part of the action to be taken if the patterns for this
role are a match.
This field consists of a filename which will be used as the signature
file when using this role.
<P>
If the filename is followed by a vertical bar (|) then instead
of reading the contents of the file the file is assumed to be a
program which will produce the text to be used on its standard output.
The program can't have any arguments and doesn't receive any input from Pine,
but the rest of the processing works as if the contents came from a file.
<P>
If you type &quot;F&quot; you may edit the contents of the file (as opposed to
the name of the file) you have specified.
If you type &quot;T&quot; you may use a browser to choose an existing filename.
<P>
Besides containing regular text, a signature file may also
contain (or a signature program may produce) tokens which are replaced with text
which depends on the message you are replying to or forwarding.
The tokens all look like _word_ (a word surrounded by underscores).
For example, if the token
<P>
<CENTER><SAMP>_DATE_</SAMP></CENTER>
<P>
is included in the text of the signature file, then when you reply to
or forward a message, the token will be replaced with the actual date
the message you are replying to or forwarding was sent.
<P>
If you use a role which has a signature file for a plain composition
(that is, not a reply or forward) then there is no original message, so
any tokens which depend on the message will be replaced with nothing.
So if you want a signature file to be useful for new compositions it
shouldn't include any of the tokens which depend on the message being
replied to or forwarded.
<P>
The list of available tokens is
<A HREF="h_index_tokens">here</A>.
<P>
Actually, for the adventurous, there is a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
It's explained in detail
<A HREF="h_reply_token_conditionals">here</A>.
<P>
A blank field here means that Pine will use its normal rules for deciding
which file (if any) to use for the signature file.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_settempl =======
<HTML>
<HEAD>
<TITLE>Role Set Template Action Explained</TITLE>
</HEAD>
<BODY>
<H1>Role Set Template Action Explained</H1>

This describes part of the action to be taken if the patterns for this
role are a match.
This field consists of a filename which will be used as the template
file when using this role.
The template file is a file which is included at the top of the message you
are composing.
<P>
If the filename is followed by a vertical bar (|) then instead
of reading the contents of the file the file is assumed to be a
program which will produce the text to be used on its standard output.
The program can't have any arguments and doesn't receive any input from Pine,
but the rest of the processing works as if the contents came from a file.
<P>
If you type &quot;F&quot; you may edit the contents of the file (as opposed to
the name of the file) you have specified.
If you type &quot;T&quot; you may use a browser to choose an existing filename.
<P>
Besides containing regular text, the template file may also
contain (or a template file program may produce) tokens which are replaced with text
which depends on the message you are replying to or forwarding.
The tokens all look like _word_ (a word surrounded by underscores).
For example, if the token
<P>
<CENTER><SAMP>_DATE_</SAMP></CENTER>
<P>
is included in the text of the template file, then when you reply to
or forward a message, the token will be replaced with the actual date
the message you are replying to or forwarding was sent.
<P>
If you use a role which has a template file for a plain composition
(that is, not a reply or forward) then there is no original message, so
any tokens which depend on the message will be replaced with nothing.
So if you want a template file to be useful for new compositions it
shouldn't include any of the tokens which depend on the message being
replied to or forwarded.
<P>
The list of available tokens is
<A HREF="h_index_tokens">here</A>.
<P>
Actually, for the adventurous, there is a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
It's explained in detail
<A HREF="h_reply_token_conditionals">here</A>.
<P>
A blank template field means that Pine will not use a template file when
this role is being used.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_replyuse =======
<HTML>
<HEAD>
<TITLE>Role Reply Use Explained</TITLE>
</HEAD>
<BODY>
<H1>Role Reply Use Explained</H1>

This option determines how this particular role will be used when Replying
to a message.
There are three possible values for this option.
The default setting is that this role will never be a candidate for use
when Replying.
Even if the pattern matches the message being replied to, this role will
not be used.
<P>

The second and third options
will cause this role's pattern to be compared with the message being
replied to.
If there is a match (and it's the first match), then this role will either be used without confirmation
or will be the default when confirmation is asked for, depending on
which option is selected.
<P>

If confirmation is requested, you will have a chance to
manually change the role to one of your other Reply roles.
<P>

You won't be prompted for confirmation if none of your roles patterns
match the message.
In other words, if the default role selected is just your default Pine role
(as opposed to a role you've defined in the Setup/Roles screen) then you
will not be prompted.
This is independent of the value of the current option.
The <A HREF="h_config_confirm_role">confirm-role-even-for-default</A>
feature may be used to change this behavior.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_config_role_forwarduse =======
<HTML>
<HEAD>
<TITLE>Role Forward Use Explained</TITLE>
</HEAD>
<BODY>
<H1>Role Forward Use Explained</H1>

This option determines how this particular role will be used when Forwarding
a message.
There are three possible values for this option.
The default setting is that this role will never be a candidate for use
when Forwarding.
Even if the pattern matches the message being forwarded, this role will
not be used.
<P>

The second and third options
will cause this role's pattern to be compared with the message being
forwarded.
If there is a match (and it's the first match), then this role will either be used without confirmation
or will be the default when confirmation is asked for, depending on
which option is selected.
<P>

If confirmation is requested, you will have a chance to
manually change the role to one of your other Forward roles.
<P>

You won't be prompted for confirmation if none of your roles patterns
match the message.
In other words, if the default role selected is just your default Pine role
(as opposed to a role you've defined in the Setup/Roles screen) then you
will not be prompted.
This is independent of the value of the current option.
The <A HREF="h_config_confirm_role">confirm-role-even-for-default</A>
feature may be used to change this behavior.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_index_tokens =======
<HTML>
<HEAD>
<TITLE>Tokens for Index and Replying</TITLE>
</HEAD>
<BODY>

This set of special tokens may be used in the
<A HREF="h_config_index_format">&quot;Index-Format&quot; option</A>,
in the <A HREF="h_config_reply_intro">&quot;Reply-Leadin&quot; option</A>,
in signature files,
and in template files used in
<A HREF="h_role_config">&quot;roles&quot;</A>.
Some of them aren't available in all situations.
<P>
The tokens are used as they appear below for the &quot;Index-Format&quot;
option, but they must be surrounded by underscores for the
&quot;Reply-Leadin&quot; option and in signature and template files.
<P>
<P>

<H1><EM>Tokens Available for all Cases</EM></H1>

<DL>
<DT>DATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format MMM DD. For example, &quot;Oct 23&quot;.
</DD>

<DT>SMARTDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It is &quot;Today&quot; if the message was sent today,
&quot;Yesterday&quot; for yesterday,
&quot;Wednesday&quot; if it was last Wednesday, and so on. If the
message is from more than six months ago it includes the year, as well.
There is no adjustment made for different time zones, so you'll get
the day the message was sent according to the time zone the sender
was in.
</DD>

<DT>LONGDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format MMM DD, YYYY. For example, &quot;Oct 23, 1999&quot;.
</DD>

<DT>SHORTDATE1</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format MM/DD/YY. For example, &quot;10/23/98&quot;.
</DD>

<DT>SHORTDATE2</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format DD/MM/YY. For example, &quot;23/10/98&quot;.
</DD>

<DT>SHORTDATE3</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format DD.MM.YY. For example, &quot;23.10.98&quot;.
</DD>

<DT>SHORTDATE4</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format YY.MM.DD. For example, &quot;98.10.23&quot;.
</DD>

<DT>TIME24</DT>
<DD>
This token represents the time at which the message was sent, according
to the &quot;Date&quot; header field.
There is no adjustment made for different time zones, so you'll get
the time the message was sent according to the time zone the sender
was in.
It has the format HH:MM. For example, &quot;17:28&quot;.
</DD>

<DT>TIME12</DT>
<DD>
This token represents the time at which the message was sent, according
to the &quot;Date&quot; header field.
This time is for a 12 hour clock.
It has the format HH:MMpm.
For example, &quot;5:28pm&quot; or &quot;11:13am&quot;.
</DD>

<DT>SUBJECT</DT>
<DD>
This token represents the Subject the sender gave the message.
</DD>

<DT>FROM</DT>
<DD>
This token represents the personal name (or email address if the name
is unavailable) of the person specified in the message's &quot;From:&quot;
header field.
</DD>

<DT>SENDER</DT>
<DD>
This token represents the personal name (or email address) of the person
listed in the message's &quot;Sender:&quot; header field.
</DD>

<DT>TO</DT>
<DD>
This token represents the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's &quot;To:&quot; header field.
</DD>

<DT>CURDATE</DT>
<DD>
This token represents the current date.
It has the format MMM DD. For example, &quot;Oct 23&quot;.
</DD>

<DT>CURTIME24</DT>
<DD>
This token represents the current time.
It has the format HH:MM. For example, &quot;17:28&quot;.
</DD>

<DT>CURTIME12</DT>
<DD>
This token represents the current time.
This time is for a 12 hour clock.
It has the format HH:MMpm.
For example, &quot;5:28pm&quot; or &quot;11:13am&quot;.
</DD>

<DT>MONTHABBREV</DT>
<DD>
This token represents the month the message was sent, according
to the &quot;Date&quot; header field.
For example, &quot;Oct&quot;.
</DD>

</DL>

<P>
<H1><EM>Tokens Available Only for Index-Format</EM></H1>

<DL>
<DT>MSGNO</DT>
<DD>
This token represents the message's current position in the folder which,
of course, may change as the folder is sorted or new mail arrives.
</DD>

<DT>STATUS</DT>
<DD>
This token represents a three character wide field displaying various
aspects of the message's state.
The first character is either blank,
a '*' for message marked Important, or a '+' indicating a message
addressed directly to you (as opposed to your having received it via a
mailing list, for example).
The second character is typically blank,
though the arrow cursor may occupy it if the 
&quot;<A HREF="h_config_force_low_speed">assume-slow-link</A>&quot;
feature is set, or you actually are on a slow link.
The third character is either the letter 'D' if the
message is deleted, 'A' if it is answered (but not deleted), or 'N' if
it is new (but not deleted or answered), or blank if it is neither
deleted, answered nor new.
</DD>

<DT>FULLSTATUS</DT>
<DD>
This token represents a less abbreviated alternative
to the &quot;STATUS&quot; field.
It is six characters wide.
The first character is '+' or blank, the
second blank, the third either '*' or blank, the fourth 'N' or blank,
the fifth 'A' or blank, and the sixth character is either 'D' or
blank.
</DD>

<DT>IMAPSTATUS</DT>
<DD>
This token represents an even less abbreviated alternative to the
&quot;FULLSTATUS&quot; field.
It differs in only the fourth character which is
either an 'N' if the message is new to this folder since the last time
it was opened <EM>and</EM> it has not been viewed, an 'R' if the message
is new to the folder and has been viewed (Recent), a 'U' if the message is not 
new to the folder since it was last opened <EM>but</EM> has not been
viewed (Unseen), or a blank if the message has been in the folder since it was
last opened and has been viewed.
</DD>

<DT>SIZE</DT>
<DD>
This token represents the total size, in bytes, of the message.
</DD>

<DT>DESCRIPSIZE</DT>
<DD>
This token is intended to represent a more useful description of the
message than just its size, but it isn't very useful at this point.
The plus sign in this view means there are attachments.
Note that including this token in
the &quot;Index-Format&quot; could slow down the
display a little while Pine collects the necessary information.
</DD>

<DT>ATT</DT>
<DD>
This is a one column wide field which represents the number of attachments
a message has. It will be blank if there are no attachments, a single
digit for one to nine attachments, or an asterisk for more than nine.
Note that including this token in
the &quot;Index-Format&quot; could slow down the
display a little while Pine collects the necessary information.
</DD>

<DT>FROMORTO</DT>
<DD>
This token represents the personal name (or email address) of
<EM>either</EM> the person listed in the message's &quot;From:&quot; header
field, <EM>or</EM>, if that address is yours or one of your
<A HREF="h_config_alt_addresses">alternate addresses</A>,
the first person specified in the
message's &quot;To:&quot; header field.
</DD>
</DL>

<P>
<H1><EM>Tokens Available for all but Index-Format</EM></H1>

<DL>
<DT>NEWSANDTO</DT>
<DD>
This token represents the news groups from the
message's &quot;Newsgroups:&quot; header field <EM>and</EM>
the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's &quot;To:&quot; header field.
</DD>

<DT>TOANDNEWS</DT>
<DD>
Same as &quot;NEWSANDTO&quot; except in the opposite order.
</DD>

<DT>NEWS</DT>
<DD>
This token represents the news groups from the
message's &quot;Newsgroups:&quot; header field.
</DD>

<DT>CC</DT>
<DD>
This token represents the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's &quot;Cc:&quot; header field.
</DD>

<DT>RECIPS</DT>
<DD>
This token represents the personal names (or email addresses if the names
are unavailable) of the persons specified in both the
message's &quot;To:&quot; header field and
the message's &quot;Cc:&quot; header field.
</DD>

<DT>NEWSANDRECIPS</DT>
<DD>
This token represents the news groups from the
message's &quot;Newsgroups:&quot; header field <EM>and</EM>
the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's &quot;To:&quot; and &quot;Cc:&quot; header fields.
</DD>

<DT>RECIPSANDNEWS</DT>
<DD>
Same as &quot;NEWSANDRECIPS&quot; except in the opposite order.
</DD>

<DT>ADDRESS</DT>
<DD>
This is similar to the &quot;FROM&quot; token, only it is always the
email address, never the personal name.
For example, &quot;mailbox@domain&quot;.
</DD>

<DT>MAILBOX</DT>
<DD>
This is the same as the &quot;ADDRESS&quot; except that the 
domain part of the address is left off.
For example, &quot;mailbox&quot;.
</DD>

<DT>DAYDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It looks like &quot;Sat, 24 Oct 1999&quot; unless the day of
the week is not available, in which case it looks like
&quot;24 Oct 1999&quot;.
</DD>

<DT>DAY</DT>
<DD>
This token represents the day of the month on which the message was sent,
according to the &quot;Date&quot; header field.
For example, &quot;24&quot;.
</DD>

<DT>MONTHLONG</DT>
<DD>
This token represents the month in which the message was sent, according
to the &quot;Date&quot; header field.
For example, &quot;October&quot;.
</DD>

<DT>MONTH</DT>
<DD>
This token represents the month in which the message was sent, according
to the &quot;Date&quot; header field.
For example, &quot;10&quot;.
</DD>

<DT>YEAR</DT>
<DD>
This token represents the year the message was sent, according
to the &quot;Date&quot; header field.
For example, &quot;1999&quot;.
</DD>

<DT>MSGID</DT>
<DD>
This token represents the message ID of the message.
</DD>
</DL>

<P>
<H1><EM>Tokens Available Only for Templates and Signatures</EM></H1>

<DL>
<DT>CURSORPOS</DT>
<DD>
This token is different from the others.
When it is replaced it is replaced with nothing, but it sets a Pine
internal variable which tells the composer to start with the cursor
positioned at the position where this token was.
If both the template file and the signature file contain
a &quot;CURSORPOS&quot; token, then the position in the template file
is used.
If there is a template file and neither it nor the signature file contains
a &quot;CURSORPOS&quot; token, then the cursor is positioned
after the end of the contents of the
template file when the composer starts up.
</DD>
</DL>

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_reply_token_conditionals =======
<HTML>
<HEAD>
<TITLE>Conditional Inclusion of Text for Reply-Leadin, Signatures, and Templates</TITLE>
</HEAD>
<BODY>

Conditional text inclusion may be used with
the <A HREF="h_config_reply_intro">&quot;Reply-Leadin&quot; option</A>,
in signature files, and in template files used in
<A HREF="h_role_config">&quot;roles&quot;</A>.
It may <EM>not</EM> be used with the
&quot;Index-Format&quot; option.

<P>
There is a limited if-else capability for including text.
The if-else condition is based
on whether or not a given token would result in replacement text you
specify.
The syntax of this conditional inclusion is
<P>
<CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER>
<P>
The left parenthesis must follow the underscore immediately, with no
intervening space.
It means the token is expanded and the results of that expansion are
compared against the &quot;match_this&quot; argument.
If there is an exact match, then the &quot;if_matched&quot; text is used
as the replacement text.
Otherwise, the &quot;if_not_matched&quot; text is used.
One of the most useful values for the &quot;match_this&quot; argument is
the empty string, &quot;&quot;.
In that case the expansion is compared against the empty string.
<P>
Here's an example to make it clearer.
This text could be included in one of your template files:
<P>
<CENTER><SAMP>_NEWS_(&quot;&quot;, &quot;I'm replying to email&quot;,&quot;I'm replying to news&quot;)</SAMP></CENTER>
<P>
If that is included in a template file which you are using while replying
to a message (because you chose to use the role it was part of),
and that message has a newsgroup header and a news group in that header,
then the text
<P>
<CENTER><SAMP>I'm replying to news</SAMP></CENTER>
<P>
will be included in the message you are about to compose.
On the other hand, if the message you are replying to does not have
a news group, then the text
<P>
<CENTER><SAMP>I'm replying to email</SAMP></CENTER>
<P>
would be included instead.
This would also work in signature files and in
the &quot;Reply-Leadin&quot; option.
If the &quot;match_this&quot;, &quot;if_matched&quot;,
or &quot;if_not_matched&quot; arguments contain
spaces, parentheses, or commas;
they have to be quoted with double quotation marks (like in the example
above).
If you want to include a literal quote in the text you must escape the
quote by preceding it with a backslash character.
If you want to include a literal backslash character you must escape it
by preceding it with another backslash.
<P>
The comma followed by &quot;if_not_matched&quot; is optional.
If there is no &quot;if_not_matched&quot;
present then no text is included if the not_matched case is true.
Here's another example:
<P>
<CENTER><SAMP>_NEWS_(&quot;&quot;, &quot;&quot;, &quot;This msg was seen in group: _NEWS_.&quot;)</SAMP></CENTER>
<P>
Here you can see that tokens may appear inside
the &quot;if_matched&quot; or &quot;if_not_matched&quot; arguments.
The same is true for tokens with the conditional parentheses.
They may appear inside the &quot;if_matched&quot; or &quot;if_not_matched&quot;,
though you do have to be careful to get the quoting and escaping of
nested double quotes correct.
If this was in the signature file being used and you were replying to a message
sent to comp.mail.pine the resulting text would be:
<P>
<CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER>
<P>
If you were replying to a message which wasn't sent to any news group the
resulting text would be a single blank line.
The reason you'd get a blank line is because the end of the line is
outside of the conditional, so is always included.
If you wanted to get rid of that blank line you could do so by moving
the end of line inside the conditional.
In other words, it's ok to have multi-line
&quot;if_matched&quot; or &quot;if_not_matched&quot; arguments.
The text just continues until the next double quotation, even if it's not
on the same line.
<P>
Here's one more (contrived) example illustrating a matching argument
which is not the empty string.
<P>
<CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER>
<P>
If this was the value of your &quot;Reply-Leadin&quot; option and you
were replying to
a message which was sent today, then the value of the &quot;Reply-Leadin&quot;
would be
<P>
<CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER>
<P>
But if you were replying to a message sent on Oct. 27 (and that wasn't
today) you would get
<P>
<CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER>
<P>

&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_cntxt_nick =======
<HTML>
<HEAD>
<TITLE>Collection Nickname Explained</TITLE>
</HEAD>
<BODY>
<H1>Collection Edit Help -- Nickname Field</H1>

This field is provided so you can add a short nickname to use when
referring to this collection within Pine.  Spaces are allowed, and
you don't need to use double-quotes.  However, the double-quote
character is not allowed.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_cntxt_server =======
<HTML>
<HEAD>
<TITLE>Collection Server: Explained</TITLE>
</HEAD>
<BODY>
<H1>Collection Edit Help -- Server Field</H1>

This collection's &quot;Server:&quot; definition indicates the
hostname of the server providing access to the folders in this
collection.  It's a good idea to use the host's fully qualified
network name.  However, IP addresses are allowed if it's delimited
with square-brackets (e.g., [127.0.0.1]).

<P>
Additionally, an optional network port number can be supplied by appending
the server name with a colon, &quot;:&quot;, followed by the port number
on the server to connect to.  By default, the IMAP port number, 143, is used.

<P>
Besides server name and optional port number, various parameters can
be supplied as well that alter Pine's interaction with the server.  A
parameter is supplied by appending the server's name with a slash,
&quot;/&quot;, character followed by the parameter's name and,
depending on the particular parameter, the value assigned to that
name.  Currently supported parameters include:

<DL>
<DT>User</DT>
<DD>This parameter requires an associated value, and is intended to
provide the username identifier with which to establish the server
connection.  An example might be: &quot;/user=katie&quot;
</DD>
<DT>Service</DT>
<DD>This parameter requires an associated value.  The default value is
&quot;IMAP&quot; which indicates communication with the server based
on the IMAP4.1 protocol (defined in RFC 2060 -- see 
<A HREF="http://www.imap.org/docs/rfc2060.html">http://www.imap.org/docs/rfc2060.html</A>).</DD>
 </DL>

Other values include:
 <DL>
 <DT>NNTP</DT>
 <DD>This value indicates communication with the server takes place via
the Network News Transfer Protocol.  Use this to define a collection
of newsgroups on a remote news server.  So, &quot;/service=NNTP&quot;
(without the quotes) is the way to specify NNTP access.
 </DD>
 <DT>POP3</DT>
 <DD>This value indicates communication with the server takes place via the
Post Office Protocol 3 protocol.  Note that there are several important issues
to consider when selecting this option:
<OL>
 <LI> POP3 provides access to only your INBOX.  In other words,
secondary folders such as your &quot;saved-messages&quot; are inaccessible.
 <LI> Pine's implementation of POP3 does not follow the traditional POP
model and will leave your mail on the server.
 <LI> Pine's implementation of POP3 is not fully supported and,
as such, has known limitations and inefficiencies.
</OL>
</DD>


<DT>Anonymous</DT>
<DD>This is a unary parameter indicating that the connection be
established use &quot;public&quot; authentication credentials.
</DD>
<DT>Secure</DT>
<DD>This is a unary parameter indicating that the connection use the
most secure authentication method mutually supported by Pine and the
server.  Pine is capable of authenticating connections to 
the server using several methods.  By default, Pine will attempt each
method until either a connection is established or the
list of methods is exhausted.  This parameter causes Pine to fail 
the connection if the first (generally most &quot;secure&quot;) method
fails.
</DD>
<DT>Debug</DT>
<DD>This is a unary parameter indicating that the connection be established
in a verbose mode.  Basically, it causes Pine to log the communication with
the server in Pine's debug file.
</DD>
</DL>
<P>

Parameters names are <EM>not</EM> case sensitive.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_cntxt_path =======
<HTML>
<HEAD>
<TITLE>Collection Path: Explained</TITLE>
</HEAD>
<BODY>
<H1>Collection Edit Help -- Path Field</H1>

The collection's &quot;Path:&quot; definition indicates the location
of the folders in this collection.  If the path or any of its components
do not exist, Pine will prompt you for their creation when exiting the
Add/Change screen.

<P> 
By default the path is interpreted as defining a section of your personal
folder area.  This area and how you specify it are defined by the
server, if one is specified in the collection, or, typically, the home
directory if no server is defined.

<P>
To define a collection outside the default &quot;area&quot;, prefix
the path with the &quot;namespace&quot; to use when interpreting the
given path.  If a namespace is specified, the Path begins with the
sharp, &quot;#&quot;, character followed by the name of the namespace
and then the namespace's path-element-delimiter.  Aside from the
path's format, namespaces can also imply access rights, content
policy, audience, location, and, occasionally, access methods.

<P>
Each server exports its own set (possibly of size one) of 
namespaces.  Hence, it's likely communication with your server's
administrator will be required for specific configurations.  Some of
the more common namespaces, however, include:

<DL>
<DT>#news.</DT>
<DD>This specifies a set of folders in the newsgroup namespace.  Newsgroup
names are hierarchically defined with each level delimited by a period.
</DD>
<DT>#public/</DT>
<DD>This specifies a folder area that the server may export to the general
public.
</DD>
<DT>#shared/</DT>
<DD>This specifies a folder area that the folder may export to groups
of users.
</DD>
<DT>#ftp/</DT>
<DD>This specifies a folder area that is the same as that it may have 
exported via the &quot;File Transfer Protocol&quot;.
</DD>
<DT>#mh/</DT>
<DD>This specifies the personal folder area associated with folders
and directories that were created using the MH message handling system.
</DD>
</DL>
<P>

In addition, the server may support access to other user's folders,
provided you have suitable permissions.  Common methods use a prefix
of either &quot;~<VAR>user</VAR>/&quot;, or &quot;/<VAR>user</VAR>/&quot; to
indicate the root of the other user's folder area.

<P>
No, nothing's simple.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_cntxt_view =======
<HTML>
<HEAD>
<TITLE>Collection View: Explained</TITLE>
</HEAD>
<BODY>
<H1>Collection Edit Help -- View Field</H1>

The collection's &quot;View:&quot; definition provides a way to limit
the displayed list of folders within a collection.  By default, only
folders that contain the specified characters anywhere in their name
are shown in the collection's folder list.

<P>
Additionally, you can use a wildcard character to better control
the list of folders selected for display.  The wildcard specifier is
the star, &quot;*&quot;, character.

<P>
So, for example, to define a collection of all folders ending with
&quot;c&quot;, you'd specify a view of &quot;*c&quot; (without the
quote characters!).  Or, similarly, to define a collection of folders
whose names start with &quot;a&quot; and end with &quot;z&quot;, you'd
specify a view of &quot;a*z&quot;.

<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_abook_add_server =======
<HTML>
<HEAD>
<TITLE>Addressbook Server Name Field Explained</TITLE>
</HEAD>
<BODY>
This field should be left blank if the address book is stored in a regular
file on this system.  If it is a remote address book stored on an IMAP
server then this is the name of that IMAP server.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_abook_add_folder =======
<HTML>
<HEAD>
<TITLE>Addressbook Folder Name Field Explained</TITLE>
</HEAD>
<BODY>
For a remote address book (one for which the Server Name is filled in)
this is the name of a folder on the remote server. The address book data
will be stored in this folder. This folder should be used only for
storing this single address book, not for other address books or for
other messages.
<P>
For a local address book (one for which the Server Name is not filled in)
this is the name of a file in which the address book will be stored.
The file is in the same directory as the Pine configuration file.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_abook_add_nick =======
<HTML>
<HEAD>
<TITLE>Addressbook NickName Field Explained</TITLE>
</HEAD>
<BODY>
This is just an optional nickname for this address book. If present, it
is used in some of the displays and error messages in the address book
maintenance screens. It is for your convenience only and serves no
other purpose.
<P>
Look <A HREF="h_edit_nav_cmds">here</A>
to see the available Editing and Navigation commands.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_qserv_cn =======
<HTML>
<HEAD>
<TITLE>Directory Query Form Explained</TITLE>
</HEAD>
<BODY>

Fill in as many of these fields as you wish to narrow down your
search. All the fields you fill in must match in order for an entry
to be returned. You may use the wildcard character &quot;*&quot; in
any of the fields, it matches any zero or more characters at that
point in the string. There are no implicit wildcards, so the match is
exact unless you include wildcards.
<P>

Note that if an attribute isn't present at all, then the match will fail.
For example, if a server doesn't support the Locality attribute, then no
matter what you put in the Locality field (other than leaving it empty)
the search will fail.
<P>

This field, the Common Name field, is typically a person's full name.
<P>

<H1>EDITING and NAVIGATION COMMANDS</H1>
<!--chtml if pinemode="function_key"-->
<PRE>
CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
^B (Left Arrow)    Back character       | ^D       Delete current character
^F (Right Arrow)   Forward character    | ^H (DEL) Delete previous character
^P (Up Arrow)      Previous line        |
^N (Down Arrow)    Next line            | F9       Cut marked text or
^A                 Beginning of line    |            delete current line
^E                 End of line          | F10      Undelete line(s)
F7                 Previous page        |
F8                 Next page            |-------------------------------------
^@ (Ctrl-SPACE)    Next word            | MISCELLANEOUS COMMANDS
----------------------------------------|
EXIT COMMANDS    |  GENERAL COMMANDS    | F5    Restore previous search
F2   Cancel      |   F1    Get help     |
F3   Search      |   ^Z    Suspend      | ^L    Redraw Screen
</PRE>
<!--chtml else-->
<PRE>
CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
^B (Left Arrow)    Back character       | ^D       Delete current character
^F (Right Arrow)   Forward character    | ^H (DEL) Delete previous character
^P (Up Arrow)      Previous line        |
^N (Down Arrow)    Next line            | ^K       Cut marked text or
^A                 Beginning of line    |            delete current line
^E                 End of line          | ^U       Undelete line(s)
^Y                 Previous page        |
^V                 Next page            |-------------------------------------
^@ (Ctrl-SPACE)    Next word            | MISCELLANEOUS COMMANDS
----------------------------------------|
EXIT COMMANDS    |  GENERAL COMMANDS    | ^R     Restore previous search
^C   Cancel      |   ^G    Get help     |
^X   Search      |   ^Z    Suspend      | ^L     Redraw Screen
</PRE>
<!--chtml endif-->
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_composer_qserv_sn =======

The Surname is usually the family name of a person.

<End of help on this topic>
======= h_composer_qserv_gn =======

This is the part of a person's name which isn't the surname or initials.

<End of help on this topic>
======= h_composer_qserv_mail =======

This is the email address of a person.

<End of help on this topic>
======= h_composer_qserv_org =======

This is the organization a person belongs to.

<End of help on this topic>
======= h_composer_qserv_unit =======

This is the organizational unit a person belongs to.

<End of help on this topic>
======= h_composer_qserv_country =======

This is the country a person belongs to.

<End of help on this topic>
======= h_composer_qserv_state =======

This is the state a person belongs to.

<End of help on this topic>
======= h_composer_qserv_locality =======

This is the locality a person belongs to.

<End of help on this topic>
======= h_composer_qserv_custom =======

This one is for advanced users only! If you put something in this field,
then the rest of the fields are ignored.

This field may be set to the string representation of an LDAP search
filter (see RFC1960). Here are some examples:

To search for an entry with a surname equal to "clinton" you could set
the custom filter to:

     (sn=clinton)
    
This is equivalent to putting "clinton" in the SurName field.
To search for an entry which has a surname which begins with "clint" and
has a givenname equal to "william" you could use:

     (&(sn=clint*)(givenname=william))
    
This is equivalent to setting the SurName field to "clint*" and the
GivenName field to "william".
To search for an entry where either the common name OR the email address
contains "abcde" you could use:

     (|(cn=*abcde*)(mail=*abcde*))

That isn't equivalent to anything you can do by setting the other fields
because of the OR.

<End of help on this topic>
======= h_composer_qserv_qq =======

This one is a little different from the rest of the categories.  It causes
a search to be formed from the configured search filter that you filled
in when you added the directory server to your configuration. It can also
be combined with the other fields if you'd like.

<End of help on this topic>
======= h_address_format =======
<HTML>
<HEAD>
<TITLE>INTERNET EMAIL ADDRESS FORMAT</TITLE>
</HEAD>
<BODY>
<H1>INTERNET EMAIL ADDRESS FORMAT</H1>

A valid email address on the Internet has a username, an &quot;@&quot; sign, 
and then a domain, with no spaces.  
For example, jsmith@art.nowhere.edu might be the email address
of a person  
with the username &quot;jsmith&quot; who has an account in the domain
&quot;art.nowhere.edu&quot;.  The number of dot-separated segments on the 
right of the &quot;@&quot; sign can vary - a shorter example would be 
isabelle@elsewhere.edu (the shortest possible form: here, only the 
organization's domain is specified after the &quot;@&quot; sign); a longer 
example would be 
 jsingh@shakti.edutech.nowhere.edu
(here, the name of the host &quot;shakti&quot; in the domain 
edutech.nowhere.edu is also specified).  
<P>  
If you do not know the exact email address of someone you want to write 
to, ask them what it is using other means of communication than email; or 
use the tools for 
finding people's addresses that are available on the Internet.  See, 
for example, the World Wide Web site:
<P>
<CENTER><A HREF="http://www.washington.edu/nic/addresses">http://www.washington.edu/nic/addresses</A></CENTER>
<P>
If you are sending to someone on the same system as you are, you can leave
the &quot;@&quot; sign and all the information to its right off of the 
address, and Pine will fill it in automatically, 
unless the feature 
<A HREF="h_config_compose_rejects_unqual">&quot;compose-rejects-unqualified-addrs&quot;</A> is set in SETUP CONFIGURATION.  Sometimes you can also
abbreviate the right part of the address if you are at the same domain.<P>

When an email address you send a message to is not reachable -- either because 
it is simply an incorrect address, or because email can temporarily not be 
delivered to it due to a technical problem on the way to or at the recipient's 
end -- you will almost always get an error notification email message back.
<P>
If you encounter problems with, or have questions about, email delivery or
email address syntax, contact your local network computing consultants.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
======= h_flag_important =======

Th "Important" flag, indicated by an asterisk in Pine's MESSAGE INDEX
screen, can only be set by the user, and is intended to be used in
whatever fashion makes sense to you.  You are the only one that can set or
clear it. 

<End of help on this topic>
======= h_flag_new =======

Th "New" flag, indicated by the letter 'N' in Pine's MESSAGE INDEX screen,
is automatically set when messages are delivered to your Inbox (or other
folder specified outside of Pine).  Likewise, it is cleared automatically
the first time you read the message it is associated with.

Sometimes it's helpful in prioritizing your mail.  For example, perhaps
a message isn't weighty enough to assign it an "Important" flag, but
you'd like to be reminded of it next time you read mail.  This can be done
easily by explicitly resetting the "New" flag.

<End of help on this topic>
======= h_flag_answered =======

The "Answered" flag, indicated by the letter 'A' in Pine's MESSAGE INDEX
screen, is automatically set when you reply to a message.  This flag is not
automatically cleared.

<End of help on this topic>
======= h_flag_deleted =======

The "Deleted" flag, indicated by the letter 'D' in Pine's MESSAGE INDEX
screen, is set when you use the "D Delete" command.  It is cleared
when you use the "U Undelete" command.

However, there can be other actions implicit in the "D Delete" command,
such as advancing to the next message, that may be momentarily undesirable.
For this reason, it's sometimes useful to set or clear the "Deleted" flag
explicitly.

<End of help on this topic>
====== h_config_pers_name ======
<html>
<title>OPTION: Personal-Name</title>
<body>
<h1>OPTION: Personal-Name</h1>
This value is used to determine the full name part of the "From" address
on messages you send.
<!--chtml if pinemode="os_windows"-->
 PC-Pine requires that this be set in order to properly construct the "From" address.
<!--chtml else-->
 If unset, Unix Pine will obtain your full name from
 the system password file. PC-Pine, on the other hand, requires that this be set.
<!--chtml endif-->
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_pruned_folders ======
<html>
<header>
<title>OPTION: Pruned-folders</title>
</header>
<body>
<h1>OPTION: Pruned-folders</h1>

This variable allows you to define a list of one or more folders that
Pine will offer to prune for you in the same way it automatically offers
to prune your "sent-mail" folder each month.<p>

That is, once a month for each folder listed, Pine will offer to move
the contents of the folder to a new folder of the same name but with
the previous month's date appended.  Pine will then look for any such
date-appended folder names created for a previous month, and offer each
one it finds for deletion.<p>

If you decline the first offer, no mail is moved and no new folder is
created.<p>

Folders listed are assumed to exist, and the archive folders will be created,
in the first collection defined by the "folder-collections" variable.<p>

<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</body>
</html>
====== h_config_upload_cmd ======
<HTML>
<HEAD>
<TITLE>OPTION: Upload-command</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Upload-command</H1>
 
This option affects the behavior of the Composer's &quot;Read File&quot; 
(^R in the message body) and &quot;Attach File&quot; (^J in the header) 
commands.  It specifies
a Unix program name, and any necessary command line arguments, that Pine can
use to transfer files from your personal computer into messages that you are
composing.<P>

<B>Note:</B> this facility is intended for use with serial line transfer 
protocols, such as kermit, xmodem, or zmodem.  It is <B>not</B> intended
to work with TCP/IP file transfer programs such as ftp.<P>

If a program is specified, the commands listed above are modified to offer a
subcommand (^Y) to activate the transfer.  Obviously, the Unix program
specified here must match the transfer program or protocol available on the
personal computer.<P>

Pine expects to exchange uploaded data via a file on your Unix system.  When
the specified upload program finishes, Pine expects the uploaded data to be
contained in this file.<P>

When upload is invoked via the &quot;Read File&quot; subcommand, Pine 
generates a
temporary file name that it will pass to the specified Unix program.  Pine
will read the resulting uploaded text from this file and then delete it when
the upload command is finished.<P>

When upload is invoked via the &quot;Attach File&quot; subcommand, Pine will 
prompt
you for the name of the file that is to contain the uploaded information that
it is to attach.  Pine will attach this file to the composition, but will
<B>not</B> delete this file after the upload command is finished.<P>

The special token &quot;_FILE_&quot; may be included among the Unix program's 
command
line arguments.  Pine will replace this symbol with the name of the file
being used to exchange the uploaded information.  This token allows you to
position the file name where it is required in the Unix program's command
line arguments.<P>

If the &quot;_FILE_&quot; token is not present in the specified command, the
temporary file's name is automatically appended to the specified Unix
program.  In other words, you don't need to use &quot;_FILE_&quot; if it is the
<B>last</B> command line argument.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_upload_prefix ======
<HTML>
<HEAD>
<TITLE>OPTION: Upload-command-prefix</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Upload-command-prefix</H1>

This option is used in conjunction with the Upload-command option.
It defines text to be written to the terminal emulator (via standard output)
immediately prior to starting upload command.  This is useful for
integrated serial line file transfer agents that permit command passing
(e.g., Kermit's APC method).<P>

The special token &quot;_FILE_&quot; may be included in the string specification.
That symbol will be replaced with the (Pine-created) name of the temporary
file in which Pine will expect to find the uploaded file.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_download_cmd ======
<HTML>
<HEAD>
<TITLE>OPTION: Download-command</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Download-command</H1>

This option affects the behavior of the Export command.  It specifies a Unix
program name, and any necessary command line arguments, that Pine can use to
transfer the exported message to your personal computer's disk.<P>
Note: this facility is intended for use with serial line transfer 
protocols, such as kermit, xmodem, or zmodem.  It is <B>not</B> intended
to work with TCP/IP file transfer programs such as ftp.<P>
If a program is specified, the Export command is modified to offer a
subcommand (^V) to activate the transfer (in lieu of saving it to
 the machine where Pine is running).  Obviously, the Unix program
specified here must match the transfer program or protocol available on the
personal computer.<P>

When this subcommand is selected and before Pine invokes the specified Unix
program, Pine will create a temporary file containing the text of the
exported message.  Pine uses this file to pass the exported message text to
the specified Unix program.<P>

The special token &quot;_FILE_&quot; may be included among the Unix program's command
line arguments.  Pine will replace this symbol with the temporary file's name
before executing the Unix program.  This token allows you to position the
file name where it is required in the Unix program's command line arguments.
<P>
If the &quot;_FILE_&quot; token is not present in the specified command, the
temporary file's name is automatically appended to the specified Unix
program.  In other words, you don't need to use &quot;_FILE_&quot; if it is the
<B>last</B> command line argument.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_download_prefix ======
<HTML>
<HEAD>
<TITLE>OPTION: Download-command-prefix</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Download-command-prefix</H1>

This option is used in conjunction with the Download-command option.
It defines text to be written to the terminal emulator (via standard output)
immediately prior to starting the download command.  This is useful for
integrated serial line file transfer agents that permit command passing
(e.g., Kermit's APC method).
<P>
The special token &quot;_FILE_&quot; may be included in the string 
specification.
That symbol will be replaced with the (Pine-created) name of the temporary
file into which Pine will place the message to be downloaded.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_mailcap_path ======
<HTML>
<HEAD>
<TITLE>OPTION: mailcap-search-path</TITLE>
</HEAD>
<BODY>
<H1>OPTION: mailcap-search-path</H1>
This variable is used to replace Pine's default mailcap file search path.
It takes one or more file names (full paths must be specified) in which to
look for mail capability data.  The default search path can be found in the
<A HREF="h_news">release notes</A> (accessible via the &quot;R&quot; command 
from the main menu).
If there is more than one file name listed, list members should be delimited
by 
<!--chtml if pinemode="os_windows"-->
a semi-colon (;) under Windows; for example:<PRE>
        C:&#92;MYCONFIG&#92;MAILCAP.TXT;H:&#92;NETCONFIG&#92;MAILCAP.TXT
</PRE>
<!--chtml else-->
a colon (:) under UNIX; for example:<PRE>
        ~/.mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
</PRE>
<!--chtml endif-->
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_mimetype_path ======
        OPTION: mimetype-search-path

This variable is used to replace Pine's default mime.types file search path.
It takes one or more file names (full paths must be specified) in which to
look for file-name-extension to MIME type mapping data.  The default search
path can be found in the release notes ("R" command off the main menu).

If there is more than one file name listed, list members should be delimited
by a colon (:) under UNIX and a semi-colon (;) under Windows.

<End of help on this topic>
====== h_config_set_att_ansi ======
        OPTION: Set printer to attached ansi printer

Type "S" to set your printer to "attached-to-ansi".
It is OK to include "attached-to-ansi" in your personal list below.

<End of help on this topic>
====== h_config_set_att_ansi2 ======
        OPTION: Set printer to attached ansi printer (no formfeed)

Type "S" to set your printer to "attached-to-ansi-no-formfeed".
It is OK to include "attached-to-ansi-no-formfeed" in your personal
list below.

This is the same as the "attached-to-ansi" option except that a
formfeed character will not be appended to the end of the print job.
If your printer already ejects the paper by itself at the end of the
job, you may prefer the "no-formfeed" form of this printer so that you
don't get an extra blank page between print jobs.

<End of help on this topic>
====== h_config_set_stand_print ======
        OPTION: Set default printer

Move to the printer you want and type "S" to set it to be your
default printer.  This list is not modifiable by you and has been
set up by the system administrators.  If there is more than one printer
listed in the Command List, you will be able to cycle through that
whole list at the time you print, starting with your default.
It is OK to include entries from this Standard list in your personal
list below.

<End of help on this topic>
====== h_config_set_custom_print ======
        OPTION: Set default printer

You may add as many print commands as you want to your personal list.
Specify one of them as your default printer by moving to the printer
you want and typing "S".  If there is more than one printer listed
in the Command List, you will be able to cycle through that list at
the time you print, starting with your default.  It is OK to include
entries from the Standard list above or to include the command
"attached-to-ansi" or "attached-to-ansi-no-formfeed" as one of the
entries here.

<End of help on this topic>
====== h_config_user_id =====
<html>
<head>
<title>OPTION: User-Identification</title>
</head>
<body>
<h1>OPTION: User-Identification</h1>
This value is used as part of the "From" address on messages you send.
It is also the default login name for remote IMAP server access.  Set this
to the username part you want to appear on outgoing email.

<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</body>
</html>
====== h_config_user_dom =====
<HTML>
<HEAD>
<TITLE>OPTION: User-Domain</TITLE>
</HEAD>
<BODY>
<H1>OPTION: User-Domain</H1>
This value specifies the domain part (right-hand side) of your return
address on outgoing email and is also used as the default domain for email
composed to a local user.
<!--chtml if pinemode="os_windows"-->
 This value is required for PC-Pine. If you are unsure as to what this should be,
 contact your local help desk, system administrator, or Internet Service Provider.
<!--chtml else-->
 If unset, Unix Pine will obtain the domain from
 the system.  Often this value will be set for your whole site by the
 system administrator.<P>
<!--chtml endif-->
If you set this, see also the <A HREF="h_config_quell_local_lookup">
&quot;quell-user-lookup-in-passwd-file&quot;</A> feature.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_smtp_server =====
<HTML>
<HEAD>
<TITLE>OPTION: SMTP-Server</TITLE>
</HEAD>
<BODY>
<H1>OPTION: SMTP-Server</H1>
This value specifies the name of one or more SMTP 
(Simple Mail Transfer Protocol) servers for sending mail. 
<!--chtml if pinemode="os_windows"-->
You must have an SMTP server for use with PC-Pine.  SMTP servers are
normally set up by a system administrator for use by all members of a given
campus or department.  Contact your local help desk to ask what SMTP
servers you should use.  
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<!--chtml else-->
Unix Pine users do not need to use an SMTP server
and can leave this blank.
<!--chtml endif-->
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_nntp_server =====
<HTML>
<HEAD>
<TITLE>OPTION: NNTP-Server</TITLE></HEAD>
<BODY>
<H1>OPTION: NNTP-Server</H1>

This value specifies the name of the NNTP (Network News Transfer Protocol)
server for reading and posting USENET news.  NNTP servers are normally
set up by a system administrator for use by all members of a given campus
or department.  Contact your local help desk to ask what NNTP servers you
should use.  
<!--chtml if pinemode="os_windows"--><!--chtml else-->
Often Unix Pine users will find that this variable has been
set for the whole system (and they don't have to worry about it).  
<!--chtml endif-->
When you
define an NNTP server here, Pine implicitly defines a news collection for
you, assuming that server as the news server and assuming that you will
use the NNTP protocol and a local newsrc configuration file for reading
news.  For more about reading news with Pine, see the 
<A HREF="h_news">release notes</A>.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_inbox_path =====
<HTML>
<HEAD>
<TITLE>OPTION: Inbox-Path</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Inbox-Path</H1>

This value overrides the default value of your INBOX name/path/location.
<!--chtml if pinemode="os_windows"-->
PC-Pine users must specify an inbox path and it must be a folder on an
IMAP server.  
<!--chtml else-->
Unix and VMS Pine users will often find that this variable
has been pre-configured by your system administrator.  
<!--chtml endif-->
You may be able to specify an alternate INBOX which is either a local folder 
or a folder on an IMAP server.
<P>
A typical remote inbox-path entry would be: &#123;monet.art.nowhere.edu}INBOX
where &quot;monet.art.nowhere.edu&quot; is replaced by the name of your IMAP
mail server.
<P>
See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
details on the syntax of folder definitions.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_default_fcc =====
<HTML>
<HEAD>
<TITLE>OPTION: Default-FCC (File Carbon Copy)</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Default-FCC (File Carbon Copy)</H1>

This value specifies where a copy of outgoing mail should be saved.  If
this is not a path name, it will be in the default collection for saves.
Any valid folder specification, local or IMAP, is allowed.  This default
folder carbon copy only applies when the 
<A HREF="h_config_fcc_rule">&quot;fcc-name-rule&quot;</A> 
is set to use the default folder.  
<!--chtml if pinemode="os_windows"-->
PC-Pine default is &quot;SENTMAIL&quot; (normally stored as SENTMAIL.MTX)
<!--chtml else-->
Unix Pine default
is normally &quot;sent-mail&quot; in the default folder collection. 
<!--chtml endif-->
<P>
If you access your email through an IMAP server, especially if you often switch between Un$
and PC-Pine, or between various desktop email systems, you may want to set this to a folde$
IMAP server (remember that in order to later access this remote folder through Pine, it
must be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
for more information). An example:<p>
<CENTER><SAMP>{monet.art.nowhere.edu}mail/sent-mail</SAMP></CENTER>
<P>
To suppress saving of outgoing mail, set: default-fcc=&quot;&quot;
<P>
See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
details on the syntax of folder definitions.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_def_save_folder =====
<HTML>
<HEAD>
<TITLE>OPTION: Default-Saved-Msg-Folder</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Default-Saved-Msg-Folder</H1>

This option determines the default folder name for save-message operations 
(&quot;saves&quot;).
<P>
If this is not a path name, it will be in the default collection for saves.
Any valid folder specification, local or IMAP, is allowed.  This default
folder only applies when the <A HREF="h_config_saved_msg_name_rule">&quot;
saved-msg-name-rule&quot;</A> doesn't override it.  
<!--chtml if pinemode="os_windows"-->
PC-Pine default is &quot;SAVEMAIL&quot; (normally stored as SAVEMAIL.MTX).
<!--chtml else-->
Unix Pine default
is normally &quot;saved-messages&quot; in the default folder collection.
<!--chtml endif-->
If you access your email through an IMAP server, especially if you often switch between Un$
and PC-Pine, or between various desktop email systems, you may want to set this to a folde$
IMAP server (remember that in order to later access this remote folder through Pine, it
must be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
for more information). An example:<p>
<CENTER><SAMP>{monet.art.nowhere.edu}mail/saved-messages</SAMP></CENTER>
<P>
See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
details on the syntax of folder definitions.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_postponed_folder =====
<HTML>
<HEAD>
<TITLE>OPTION: Postponed-Folder</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Postponed-Folder</H1>
This value overrides the default name for the folder where postponed
messages are saved.  If this is not a path name, it will be in the default
collection for message Saves.  Any valid folder specification, local or
remote, is allowed. 
PC-Pine default
is &quot;POSTPOND&quot; (stored as POSTPOND.MTX).
The Unix Pine default is normally &quot;postponed-msgs&quot;
in the default collection. 
<P>
Tip: If you are using different installations of (PC-)Pine -- for example, PC-Pine on your personal
computer at home, and Unix Pine on campus -- you can postpone a composition begun with one Pine and
resume it later with the other if you set this option to the <B>same folder on the same IMAP host</B>
in all Pine copies you use. 
(Remember that in order to later access this remote folder through Pine, it must be in a folder
collection. See <A HREF="h_what_are_collections">Folder Collections Extensions Explained</a>
for more information). An
example:<p> 
<CENTER><SAMP>{monet.art.nowhere.edu}mail/postponed-msgs</SAMP></CENTER>
<P>
See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
details on the syntax of folder definitions.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_read_message_folder =====
<HTML>
<HEAD>
<TITLE>OPTION: Read-Message-Folder</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Read-Message-Folder</H1>

By virtue of specifying a folder name here, Pine will be configured to
save all messages which you have read during a session into the designated
&quot;read messages&quot; folder.  This allows you to more easily distinguish
between your really new email (in your INBOX) and those which you have
already read.  Depending on how you define the 
<A HREF="h_config_auto_read_msgs">&quot;auto-move-read-messages&quot;</A>
setting, you may or may not be asked when you quit
Pine if you want read messages to be moved to this folder.  In either
case, moving the messages means they will be deleted from your INBOX.
<P>
If this is not a path name, it will be in the default collection for
saves.  Any valid folder specification, local or remote (via IMAP), is
allowed.  There is no default for the name of the read message folder.
<P>
See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
details on the syntax of folder definitions.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_form_folder =====
<HTML>
<HEAD>
<TITLE>OPTION: Form-Letter-Folder</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Form-Letter-Folder</H1>

A &quot;Form-Letter-Folder&quot; is a mail folder that is intended to
contain messages that you have composed and that are intended to be
sent in their original form repeatedly.

<P>
Setting this variable will alter Pine's usual behavior when you
execute the Compose command.  Normally, Pine offers a chance to
continue a postponed or interrupted message should one or the other
exist.  When this variable is set to a folder name that exists, Pine
will also offer the chance to select a message from the folder to
insert into the composer (much like when continuing a postponed message).
The difference, however, is that Pine will not automatically delete
the selected message from the Form Letter Folder.
<P>
Setting this variable will also affect Pine's behavior when you
Postpone a message from the composer.  Normally, Pine simply stashes
the message away in your
&quot;<A HREF="h_config_postponed_folder">Postponed-Folder</A>&quot;.
Regardless of the specified folder's existence, Pine will ask which
folder you intend the message to be stored in.  Choose the
&quot;F&quot; option to store the message in your Form Letter Folder.
This is the most common way to add a message to the folder.

<P>
Another method of adding messages to the folder is via the Pine
composer's <SAMP>Fcc:</SAMP> field.  If you are sending a message that
you expect to send in the same form again, you can enter the Form
Letter Folder's name in this field.  Pine, as usual, will copy the
message as it's sent.  Note, when you later select this message from 
your Form Letter Folder, it will have the same recipients as the original
message.

<P>
To delete a message from the Form Letter Folder, you can either select
the folder from a suitable FOLDER LIST screen, or use the Delete
command in the MESSAGE INDEX offered when selecting from the folder as
part of the Compose command.  You can delete a Form Letter Folder just
as any other folder from a suitable FOLDER LIST screen.

<P>
You may find that the <A HREF="h_role_config">&quot;Roles&quot;</A>
facility introduced in Pine 4.10 can be used
to replace the Form Letter Folder.

<P>
See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
details on the syntax of folder definitions.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_archived_folders =====
<HTML>
<HEAD>
<TITLE>OPTION: Incoming-Archive-Folders</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Incoming-Archive-Folders</H1>
 
This is like
<A HREF="h_config_read_message_folder">Read-Message-Folder</A>,
only more general.  You may archive
any of the folders in your incoming collection.  This is a list of folder
pairs, with the first separated from the second in the pair by a space.
The first folder in a pair is the folder you want to archive, and the
second folder is the folder that read messages from the first should be
moved to.  Depending on how you define the
<A HREF="h_config_auto_read_msgs">&quot;auto-move-read-messages&quot;</A>
setting, you may or may not be asked when you
leave the first folder if you want read messages to be moved to the
second folder.  In either case, moving the messages means they will be
deleted from the first folder.
<P>
The name of the first folder in each pair can be either the technical
specification of the folder (like what appears in your configuration file)
or (much easier) the nickname that you gave the folder when you made it
an incoming folder.
<p>
For example:<p>
<CENTER><SAMP>{monet.art.nowhere.edu}inbox {monet.art.nowhere.edu}mail/inbox-archive</SAMP></CENTER>
<p>or, using nicknames:<p>
<CENTER><SAMP>inbox inbox-archive</SAMP></CENTER>
<P>
If these are not path names, they will be in the default collection for
saves. Any valid folder specification, local or remote (via IMAP), is
allowed. There is no default.
<P>
See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
details on the syntax of folder definitions.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_newsrc_path ======
<HTML>
<HEAD>
<TITLE>OPTION: newsrc-path</TITLE>
</HEAD>
<BODY>
<H1>OPTION: newsrc-path</H1>

This option overrides the default name Pine uses for your "newsrc" news
status and subscription file.  If set, Pine will take this value as the
full pathname for the desired newsrc file.<P>

If this option is <B>not</B> set, 
<!--chtml if pinemode="os_windows"-->
PC-Pine looks first for $HOME&#92;NEWSRC (where $HOME defaults to the root
of the current drive, e.g. &quot;C:&#92;&quot;) and then it looks in the same
directory as your pinerc file for NEWSRC.
<!--chtml else-->
Unix Pine looks for the file ~/.newsrc (that is, the file named .newsrc in 
your account's home directory).
<!--chtml endif-->
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_signature_file =====
<HTML>
<HEAD>
<TITLE>OPTION: signature-file</TITLE>
</HEAD>
<BODY>
<H1>OPTION: signature-file</H1>

This is the name of a file which will be automatically inserted into
outgoing messages.
It typically contains information such as your
name, email address and organizational affiliation.
Pine adds the
signature into the message as soon as you enter the composer so you
can choose to remove it or edit it on a message by message basis.
Signature file placement in message replies is controlled by the
&quot;<A HREF="h_config_sig_at_bottom">signature-at-bottom</A>&quot;
setting in the feature list.
<P>

The default file name is
<!--chtml if pinemode="os_windows"-->
&quot;PINE.SIG&quot; in the same directory as your PINERC file.
<!--chtml else-->
&quot;.signature&quot;.
<!--chtml endif-->
The signature file must be kept on the local system, not a remote
IMAP server.
<P>

To create or edit your signature file choose Setup from the Main Menu
and then select S for Signature (Main/Setup/Signature).
This puts you
into the Signature Editor where you can enter a <EM>few</EM> lines of
text containing your identity and affiliation.

<P>
If the filename is followed by a vertical bar (|) then instead
of reading the contents of the file the file is assumed to be a
program which will produce the text to be used on its standard output.
The program can't have any arguments and doesn't receive any input from Pine,
but the rest of the processing works as if the contents came from a file.

<P>
Besides regular text, the signature file may also contain
(or a signature program may produce) tokens which
are replaced with text which usually depends on the message you are replying
to or forwarding.
For example, if the signature file contains the token
<P>
<CENTER><SAMP>_DATE_</SAMP></CENTER>
<P>
anywhere in the text, then that token is replaced by the date
the message you are replying to or forwarding was sent.
If it contains
<P>
<CENTER><SAMP>_CURDATE_</SAMP></CENTER>
<P>
that is replaced with the current date.
The first is an example of a token which depends on the message you
are replying to (or forwarding) and the second is an example which
doesn't depend on anything other than the current date.
You have to be a little careful with this facility since tokens which
depend on the message you are replying to or forwarding will be replaced
by nothing in the case where you are composing a new message from scratch.
The use of <A HREF="h_role_config">&quot;roles&quot;</A> may help you
in this respect.
It allows you to use different signature files in different cases.
<P>

The list of tokens available for use in the signature file is
<A HREF="h_index_tokens">here</A>.
<P>

Instead of, or along with the use of &quot;roles&quot; to give you
different signature files in different situations, there is also
a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
This is explained in detail
<A HREF="h_reply_token_conditionals">here</A>.
This isn't for the faint of heart.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_init_cmd_list =====
<html>
<header>
<title>OPTION: Initial-Keystroke-List</title>
</header>
<body
<h1>OPTION: Initial-Keystroke-List</h1>

The initial keystroke--or command--list option lets you start Pine at
any place you like.  Whatever keystrokes you specify here will be executed
by Pine upon startup as a macro.  The words SPACE, TAB, DOWN, UP, LEFT, and
RIGHT indicate the pressing of those keys.  CR indicates the pressing of
the RETURN key.  F1 through F12 represent the function keys, and ^ followed
by a character indicates that key pressed along with the control key (in
other words, ^P means control-P).  A string delimited by double-quotes (")
will be expanded into the individual keystrokes (excluding the double-quote 
characters).  For example, to view message 1 on startup, you would specify 
i,j,1,CR,v.<p>

Restrictions: You cannot pre-type into the composer with the initial
keystroke list, and you cannot mix function key commands with letter
commands.<p>

<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</body>
</html>
====== h_config_comp_hdrs =====
<html>
<header>
<title>OPTION: Default-Composer-Headers</title>
</header>
<body>
<h1>OPTION: Default-Composer-Headers</title>

You can decide which headers you want visible when composing outgoing
email using this option.  You can specify any of the regular set, any rich
header or any custom header which you have already defined.  If you use
this setting at all, you must specify all the headers you want to see, you
can't just add to the regular header set.  The default set is To:, Cc:,
Attchmnt:, and Subject:.<p>

Note that the "Newsgroups:" header will be abbreviated in the Composer
display, but should be spelled out in full here.<p>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</body>
</html>
====== h_config_custom_hdrs =====
<HTML>
<HEAD>
<TITLE>OPTION: Customized-Headers</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Customized-Headers</H1>

You may add your own custom headers to all outgoing messages.  Each header
you specify here must include the header tag 
(<A HREF="h_composer_reply_to">Reply-To:</A>, Approved:, etc.)
and may optionally include a value for that header.  If you want to see
these custom headers each time you compose a message, you must add them to
your <A HREF="h_config_comp_hdrs">default composer headers</A> list, 
otherwise they become part
of the rich header set which you only see when you press the rich header
<!--chtml if pinemode="function_key"-->(F5)
<!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_viewer_headers =====
<HTML>
<HEAD>
<TITLE>OPTION: Viewer-Headers</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Viewer-Headers</H1>

You may change the default list of headers that are viewed by listing
the headers you want to view here.  If the headers in your
&quot;viewer-hdrs&quot; list are present in the message, then they
will be shown.  The order of the headers you list will be honored.  If
the special value &quot;all-except&quot; is included as the first
header in the &quot;viewer-hdrs&quot; list, then all headers in the
message except those in the list will be shown.  The values are all
case insensitive.

<P>
Note that once you put anything in the &quot;viewer-hdrs&quot; list,
then the original default headers are ignored.  So, if you just wanted
to add the header Organization to the list, you would have to list
Organization plus all of the other headers originally in the default
list.  If you just included Organization and nothing else, then you
would see only the Organization header, nothing else.

<P>
The default list of headers includes:
<UL>
  <LI>From
  <LI>Resent-From
  <LI>To
  <LI>Resent-To
  <LI>Cc
  <LI>Resent-cc
  <LI>Bcc
  <LI>Newsgroups
  <LI>Followup-To
  <LI>Date
  <LI>Resent-Date
  <LI>Subject
  <LI>Resent-Subject
  <LI>Reply-To
</UL>

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_saved_msg_name_rule =====
<HTML>
<HEAD>
<TITLE>OPTION: Saved-Msg-Name-Rule</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Saved-Msg-Name-Rule</H1>

This option determines the default folder name when saving (i.e. using
the Save option) a message.  Choose one of the following:
default-folder, last-folder-used, by-from, by-sender, by-recipient,
by-nick-of-from, by-nick-of-sender, by-nick-of-recip, by-fcc-of-from,  
by-fcc-of-sender, by-fcc-of-recip, by-nick-of-from-then-from,
by-nick-of-sender-then-sender, by-nick-of-recip-then-recip,
by-fcc-of-from-then-from,  by-fcc-of-sender-then-sender,
or by-fcc-of-recip-then-recip.

<P>
The default option is &quot;default-folder&quot;, which is the folder
called &quot;saved-messages&quot; in Unix Pine and
&quot;savemail&quot; in PC-Pine.  To change the default folder, modify
the variable called &quot;default-saved-msg-folder&quot;.

<P>
Choosing any of the &quot;by-&quot; options cause Pine to attempt to
get the chosen option's value for the message being saved.  For
example, if &quot;by-from&quot; is chosen, Pine attempts to get the
value of who the message came from (i.e. the from address).  Pine then
attempts to save the message to a folder matching that value. If
&quot;by-from&quot; is chosen and no value is obtained, Pine uses
&quot;by-sender&quot;. The opposite is also true.  If
&quot;by-recipient&quot; was chosen and the message was posted to a
newsgroup, Pine will use the newsgroup name.

<P>
If any of the &quot;by-nick&quot; options are chosen, the resulting
address is looked up in the user's address book and if found, the
nickname for that entry is used.  Similarly, if any of the
&quot;by-fcc&quot; options are chosen, the fcc from the corresponding
address book entry is used.  If no value is found in the address book,
then if the chosen option ends with the &quot;then-from&quot;,
&quot;then-sender&quot;, or &quot;then-recip&quot; suffix, Pine
reverts to the same behavior as &quot;by-from&quot;,
&quot;by-sender&quot; or &quot;by-recipient&quot; depending on which
option was specified.  If the chosen option doesn't end with one of
the &quot;then-&quot; suffixes, then Pine reverts to the default
folder when no match is found in the address book.

<P>
Choosing the option called &quot;last-folder-used&quot;, causes Pine
to save to the folder that you saved to the last time you saved a
message.  The first time you save a message in a Pine session, Pine
attempts to save the message to the default folder.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_fcc_rule =====
<HTML>
<HEAD>
<TITLE>OPTION: FCC-Name-Rule</TITLE>
</HEAD>
<BODY>
<H1>OPTION: FCC-Name-Rule</H1>

This option determines the default name for folder carbon copy. Choose
one:

<DL>
<DT>default-fcc</DT>
<DD>This is the normal default, the value of which is set in the
&quot;default-fcc&quot; variable as specified earlier in this
configuration.
</DD>

<DT>last-fcc-used</DT>
<DD> Causes Pine to use the folder that was last
used in the fcc field
</DD>

<DT>by-nickname</DT>
<DD>Means that Pine will use the nickname
from your address book that matches the first address in the To line.
If there is no match, it will use the value of the
&quot;default-fcc&quot; variable.
</DD>

<DT>by-recipient</DT>
<DD>Means Pine will form a folder name
based on the left hand side of the first address in the To line.
</DD>

<DT>by-nick-then-recip</DT>
<DD>Means that it will use the
matching nickname from your address book if there is one, otherwise it
will extract the recipient name from the address and use that (like
by-recipient).
</DD>

<DT>current-folder</DT>
<DD>Causes a copy to be written to
the currently open folder, unless that is the INBOX.  In the case
where the current folder is the INBOX, the &quot;default-fcc&quot; is
used instead.
</DD>
</DL>

<P>
Note: Whatever the fcc specified by the rule here, it will be
over-ridden by any fcc entries you have in your address book.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_sort_key =====
<HTML>
<HEAD>
<TITLE>OPTION: Sort-Key</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Sort-Key</H1>

This option determines the order in which messages will be displayed in
the MESSAGE INDEX screen.  Choose from:

<DL>
<DT>Date</DT>
<DD>Sort folders according to the date and time they were
sent. On a folder like INBOX, sorting by &quot;Date&quot; should be almost
identical to sorting by &quot;Arrival&quot;.
</DD>

<DT>Arrival</DT>
<DD>Sort messages into the order in which they arrived.
</DD>

<DT>From</DT>
<DD>Sort messages by the name of the author of the message.
Messages with the same author are grouped together. Groups of
messages are then put into alphabetical order according to message
author.
</DD>

<DT>Subject</DT>
<DD>Sort messages by subject. Messages with the same subject are
grouped together. Pine ignores leading &quot;Re:&quot; and
&quot;re:&quot; and trailing &quot;(fwd)&quot; when determining the
likeness and alphabetical order of subject lines. Groups of messages
are put into alphabetical order according to subject.
</DD>

<DT>OrderedSubj</DT>
<DD>Grouping of all messages with the same subject
together is done in the same way as sort by subject. With
&quot;OrderedSubj&quot; however, groups of messages are put into date order
according to the oldest message on a given subject. This sorting
provides pseudo threading of messages.
</DD>

<DT>ReverseDate</DT>
<DD>Like &quot;Date&quot; but the newest message is first.
</DD>

<DT>ReverseArrival</DT>
<DD>Like &quot;Arrival&quot; but the newest message is first.
</DD>

<DT>ReverseFrom</DT>
<DD>Like &quot;From&quot; but groups of messages are ordered in
reverse alphabetical order (Z-A).
</DD>

<DT>ReverseSubject</DT>
<DD>Like &quot;Subject&quot; but groups of messages are
ordered in reverse alphabetical order (Z-A).
</DD>

<DT>ReverseOrderedSubj</DT>
<DD>Like &quot;OrderedSubj&quot; but groups of messages
are ordered with the newest groups first (according to the first
message of each group).
</DD>
</DL>

<P>
Normal default is &quot;arrival&quot;.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_fld_sort_rule =====
<HTML>
<HEAD>
<TITLE>OPTION: Folder-Sort-Rule</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Folder-Sort-Rule</H1>

This option controls the order in which folder list entries will be
presented in the FOLDER LIST screen.  Choose one of the following:

<DL>
<DT>Alphabetical</DT>
<DD>sort by alphabetical name independent of type
</DD>

<DT>Alpha-with-dirs-last</DT>
<DD>sort by alphabetical name grouping directory entries
to the end of the list
</DD>

<DT>Alpha-with-dirs-first</DT>
<DD>sort by alphabetical name grouping directory entries
to the start of the list
</DD>
</DL>

The normal default is &quot;Alphabetical&quot;.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_ab_sort_rule =====
<HTML>
<HEAD>
<TITLE>OPTION: Address-Book-Sort-Rule</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Address-Book-Sort-Rule</H1>

This option controls the order in which address book entries will be
presented.  Choose one of the following:

<DL>
<DT>fullname</DT>
<DD>use fullname field, lists mixed in
</DD>

<DT>fullname-with-lists-last</DT>
<DD>use fullname field, but put lists at end
</DD>

<DT>nickname</DT>
<DD>use nickname field, lists mixed in
</DD>

<DT>nickname-with-lists-last</DT>
<DD>use nickname field, but put lists at end
</DD>

<DT>dont-sort</DT>
<DD>don't change order of file
</DD>
</DL>

<P>
The normal default is &quot;fullname-with-lists-last&quot;.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_char_set =====
<HTML>
<HEAD>
<TITLE>OPTION: Character-Set</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Character-Set</H1>

The character set is used primarily to mark outgoing email appropriately.
Set it to whatever character set you might use to compose messages.
Whenever you actually send a message, Pine checks it to see if it is, in
fact, US-ASCII (a subset of the other sets allowable). If it is US-ASCII,
the outgoing message will be marked as such no matter what you have set as
your character set. Normal default is US-ASCII.  Typical alternatives
include ISO-8859-x, where x is a number between 1 and 9, or 13, or 15.
<P>
Note: if this option is <B>not</B> set and you send a message containing
an 8-bit character (such as characters with umlauts, or symbols like 
the R in a circle for &quot;registered trademark,&quot; 
which are not part of the US-ASCII character set) -- for 
example, by attaching a text file, or inserting another message or file 
into the message body, that contains an 8-bit character  --
then the outgoing message will be identified to be in the 
&quot;X-UNKNOWN&quot; character set.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_editor =====
<HTML>
<HEAD>
<TITLE>OPTION: Editor</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Editor</H1>
Editor specifies the program invoked by ^_ in the Composer. This is
normally an alternative to Pine's internal composer (Pico).  You could use
this setting to specify an alternate editor to use occasionally or if you
have a favorite editor and want to use it all the time (see the 
<A HREF="h_config_alt_ed_now">&quot;enable-alternate-editor-implicitly&quot;</A> setting).  <P>
If you specify multiple editors for this option, ^_ will invoke the first one 
of those specified that exists and is executable.  When specifying a program 
for use here, make sure that the format of the text it saves -- which, when 
you exit it, will become the message body in Pine -- is appropriate 
for the body of an email message; avoid proprietary formats that may result in 
a message body that the recipient of your message will be unable to decipher.
<P>
<!--chtml if pinemode="os_windows"-->
<!--chtml else-->
If you are in doubt about what editors are available on your system, or which 
of them may be appropriate for specification here, ask your local computing 
support staff.  
<!--chtml endif-->
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_speller =====
<HTML>
<HEAD>
<TITLE>OPTION: Speller</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Speller</H1>

This option affects the behavior of the ^T (spell check) command in the
Composer.  It specifies the program invoked by ^T in the Composer.  By
default, Pine uses the system's &quot;spell&quot; command.  Pine will use the
command defined by this option (if any) instead.  When invoking the
spell-checking program, Pine appends a tempfile name (where the message is
passed) to the command line. Pine expects the speller to correct the
spelling in that file. When you exit from that program Pine will read the
tempfile back into the composer.

<P>
If this option is not set, then the system's &quot;spell&quot; command is used.
The spell command does not work the same as the alternate speller.
It produces a list of misspelled words on its standard output, instead.
Don't set this speller option to the standard Unix spell command.
That won't work. If you want to use the standard Unix spell command,
set the speller option to nothing.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_display_filters =====
<HTML>
<HEAD>
<TITLE>OPTION: Display-Filters</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Display-Filters</H1>

This option defines a list of text-filtering commands (programs or
scripts) that may be used to filter text portions of received messages
prior to their use (e.g., presentation in the &quot;MESSAGE TEXT&quot;
display screen, exporting to a text file).  
For security reasons, the full path name of the
filter command must be specified.

<P>
The command is executed and the message is piped into its standard input. 
The standard output of the command is read back by Pine.  The
&quot;_TMPFILE_&quot; token (see below) overrides this default behavior. 

<P> 
The filter's use is based on the configured &quot;trigger&quot; string.  The
format of a filter definition is:

<P>   
<CENTER>&lt;trigger&gt; &lt;command&gt; &lt;arguments&gt;</CENTER>

<P>
You can specify as many filters as you wish, separating them with a comma.  
Each filter can have only one trigger and command.  Thus, two trigger 
strings which invoke the same command require separate filter 
specifications. 

<P> 
The &quot;trigger&quot; is simply text that, if found in the message,
will invoke the associated command.  If the trigger contains any space
characters, it must be placed within quotes.  Likewise, should you
wish a filter to be invoked unconditionally, define the trigger as the
null string, &quot;&quot; (two consecutive double-quote characters).  If the
trigger string is found anywhere in the text of the message the filter
is invoked.  Placing the trigger text within the tokens defined below
changes where within the text the trigger must be before considering
it a match.

<P>  
Trigger Modifying Tokens:
<DL>
<DT>_CHARSET(<VAR>string</VAR>)_</DT>
<DD>This token tells Pine to invoke the supplied command
if the text is in a character set matching <VAR>string</VAR>
(e.g., ISO-8859-2 or ISO-2022-JP).
</DD>


<DT>_LEADING(<VAR>string</VAR>)_</DT>
<DD>This token tells Pine to invoke the supplied command
if the enclosed <VAR>string</VAR> is found to be the first
non-whitespace text.
<BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
the space character.
</DD>

<DT>_BEGINNING(<VAR>string</VAR>)_</DT>
<DD>This token tells Pine to invoke the supplied command
if the enclosed <VAR>string</VAR> is found at the beginning
of any line in the text.
<BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
the space character.
</DD>
</DL>

<P>
The &quot;command&quot; and &quot;arguments&quot; portion is simply
the command line to be invoked if the trigger string is found.  Below
are tokens that Pine will recognize and replace with special values
when the command is actually invoked.

<P>
Command Modifying Tokens:

<DL>
<DT>_RECIPIENTS_</DT>
<DD>
When the command is executed, this token is replaced 
with the space delimited list of recipients of the 
message being displayed.
</DD>
                        
<DT>_TMPFILE_</DT>
<DD>When the command is executed, this token is 
replaced with the path and name of the temporary 
file containing the text to be filtered.  Pine 
expects the filter to replace this data with the 
filter's result.

<P>
NOTE: Use of this token implies that the text to 
be filtered is not piped into standard input of the 
executed command and its standard output is ignored. 
Pine restores the tty modes before invoking the
filter in case the filter interacts with the user
via its own standard input and output.  
</DD>
                        
<DT>_RESULTFILE_</DT>
<DD>When the command is executed, this token is 
replaced with the path and name of a temporary 
file intended to contain a status message from the 
filter.  Pine displays this in the message status 
field. 
</DD>
 
<DT>_DATAFILE_</DT>
<DD>When the command is executed, this token is 
replaced with the path and name of a temporary 
file that Pine creates once per session and deletes 
upon exit.  The file is intended to be used by the 
filter to store state information between instances 
of the filter.
</DD>
   
<DT>_PREPENDKEY_</DT>
<DD>When the command is executed, this token indicates that a random
number will be passed down the input stream before the message text.
This number could be used as a session key.  It is sent in this way to
improve security.  The number is unique to the current Pine session
and is only generated once per session.
</DD>
</DL>

<P>
Performance caveat/considerations:
<BR>
Testing for the trigger and invoking the filter doesn't come for free.
There is overhead associated with searching for the trigger string, testing
for the filter's existence and actually piping the text through the filter.
The impact can be reduced if the Trigger Modifying Tokens above are 
employed.
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_sending_filter =====
<HTML>
<HEAD>
<TITLE>OPTION: Sending-Filters</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Sending-Filters</H1>
      
This option defines a list of text-filtering commands (programs and
scripts) that may be selectively invoked to process a message just before
it is sent.  If set, the Composer's ^X (Send) command will allow you to
select which filter (or none) to apply to the message before it is sent. 
For security reasons, the full path of the filter program must be
specified. 

<P>
Command Modifying Tokens:

<DL>
<DT>_RECIPIENTS_</DT>
<DD>When the command is executed, this token is replaced 
with the space delimited list of recipients of the 
message being sent. 
</DD>
        
<DT>_TMPFILE_</DT>
<DD>
When the command is executed, this token is 
replaced with the path and name of the temporary 
file containing the text to be filtered.  Pine 
expects the filter to replace this data with the 
filter's result.

<P>
NOTE: Use of this token implies that the text to 
be filtered is not piped into standard input of the 
executed command and its standard output is ignored. 
Pine restores the tty modes before invoking the
filter in case the filter interacts with the user
via its own standard input and output.  
</DD>
                        
<DT>_RESULTFILE_</DT>
<DD>When the command is executed, this token is 
replaced with the path and name of a temporary 
file intended to contain a status message from the 
filter.  Pine displays this in the message status 
field. 
</DD>
 
<DT>_DATAFILE_</DT>
<DD>When the command is executed, this token is replaced 
in the command line with the path and name of a 
temporary file that Pine creates once per session 
and deletes upon exit.  The file is intended to be 
used by the filter to store state information between 
instances of the filter.
</DD>
   
<DT>_PREPENDKEY_</DT>
<DD>When the command is executed, this token indicates 
that a random number will be passed down the input 
stream before the message text.  This number could 
be used as a session key.  It is sent in this way 
to improve security.  The number is unique to the 
current Pine session and is only generated once per 
session. 
</DD>

<DT>_INCLUDEALLHDRS_</DT>
<DD>When the command is executed, this token indicates 
that the headers of the message will be passed down the input stream
before the message text.
</DD>

<DT>_MIMETYPE_</DT>
<DD>When the command is executed, this token is replaced in the
command name with a temporary file name used to accept any new MIME
Content-Type information necessitated by the output of the filter.
Upon the filter's exit, if the file contains new MIME type
information, Pine verifies its format and replaces the outgoing
message's MIME type information with that contained in the file. This
is basically a cheap way of sending something other than Text/Plain.
</DD>
</DL>

<P>   
NOTE: Only the body text, which is visible in the Composer, is piped
through this filter.  Attachments are not sent to the filter.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_alt_addresses =====
<HTML>
<HEAD>
<TITLE>OPTION: Alt-Addresses</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Alt-Addresses</H1>

This option provides a place for you to list alternative email addresses
you may have.  If set, the option affects the behavior of the Reply
command and the &quot;+&quot; symbol in the MESSAGE INDEX, which denotes that
a message has been addressed specifically to you.

<P>
With respect to Reply, the reply-to-all option will exclude addresses
listed here.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_abook_formats =====
<HTML>
<HEAD>
<TITLE>OPTION: Addressbook-Formats</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Addressbook-Formats</H1>

This option specifies the format that address books are displayed in.
Normally, address books are displayed with the nicknames in the first
column, the fullnames in the second column, and addresses in the third
column.  The system figures out reasonable defaults for the widths of
the columns.  An address book may be given a different format by
listing special tokens in the order you want them to display.  The
possible tokens are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT.
So, for example, to get the default behavior you could list

<P>
<CENTER>addressbook-formats=NICKNAME&nbsp;FULLNAME&nbsp;ADDRESS</CENTER>

<P>
(You can also use the token DEFAULT to get the default behavior for
an address book format.)

<P>
The tokens are separated by spaces.  &quot;Addressbook-formats&quot;
is a list, so if you have more than one address book you may have a
separate format for each by putting its format at the corresponding
location in the "addressbook-formats" list.

<P>

Listed first are the personal address books, then the global address
books.  So, if you have two personal address books and one global
address book, you may have up to three formats in the
&quot;addressbook-formats&quot; list.  If
&quot;addressbook-formats&quot; doesn't have as many elements as there
are address books, the last element is used repeatedly.

<P>

Each of the tokens may also be optionally followed by parentheses with
either a number or a percentage inside the parentheses.  For example,
<SAMP>FULLNAME(13)</SAMP> means to allocate 13 characters of space to
the fullnames column, <SAMP>FULLNAME(20%)</SAMP> means to allocate 20%
of the available space (the screen width minus the space for
inter-column spaces) to the fullnames column, while plain
<SAMP>FULLNAME</SAMP> means the system will attempt to figure out a
reasonable number of columns.

<P>
There are always 2 spaces between every column, so if you use
fixed column widths (like 13) you should remember to take that into
account.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_index_format =====
<HTML>
<HEAD>
<TITLE>OPTION: Index-Format</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Index-Format</H1>

This option is used to customize the content of lines in the
<A HREF="h_mail_index">MESSAGE INDEX screen</A>.  Each line is intended 
to convey some amount of immediately relevant information about each 
message in the current folder.
<P>

Pine provides a pre-defined set of informational fields with
reasonable column widths automatically computed.  You can, however,
replace this default set by listing special tokens in the order you
want them displayed.
<P>

The list of available tokens is
<A HREF="h_index_tokens">here</A>.
<P>

Spaces are used to separate listed tokens.  Additionally, you can
specify how much of the screen's width the taken's associated data
should occupy on the index line by appending the token with a pair of
parentheses enclosing either a number or percentage.  For example,
&quot;SUBJECT(13)&quot; means to allocate 13 characters of space to the subject
column, and &quot;SUBJECT(20%)&quot; means to
allocate 20% of the available space
to the subjects column, while plain &quot;SUBJECT&quot; means the system will
attempt to figure out a reasonable amount of space.
<P>

There is always one space between every pair of columns, so if you use fixed
column widths (like 13) you should remember to take that into account.
Several of the fields are virtually fixed-width, so it doesn't make
much sense to specify the width for them.  The fields STATUS,
FULLSTATUS, MSGNO, the DATE fields, SIZE, and DESCRIPSIZE all fall into that
category.  You <EM>may</EM> specify widths for those if you wish, but
you're probably better off letting the system pick those widths.  <P>

<P>
The default is equivalent to:

<P>
<CENTER><SAMP>index-format=STATUS&nbsp;MSGNO&nbsp;DATE&nbsp;FROMORTO(33%)&nbsp;SIZE&nbsp;SUBJECT(67%)</SAMP></CENTER>

<P>
This means that the four fields without percentages will be allocated
first, and then 33% and 67% of the <EM>remaining</EM> space will go to
the from and subject fields.  If one of those two fields is specified
as a percentage and the other is left for the system to choose, then
the percentage is taken as an absolute percentage of the screen, not
of the space remaining after allocating the first four columns.  It
doesn't usually make sense to do it that way.  If you leave off all
the widths, then the subject and from fields (if both are present) are
allocated space in a 2 to 1 ratio, which is almost exactly the same as
the default.

<P>
What you are most likely to do with this configuration option is to
specify which fields appear at all, which order they appear in, and the
percentage of screen that is used for the from and subject fields if you
don't like the 2 to 1 default.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_reply_intro =====
<HTML>
<HEAD>
<TITLE>OPTION: Reply-Leadin</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Reply-Leadin</H1>

This option is used to customize the content of the introduction line
that is included when replying to a message and including the original
message in the reply.
The normal default (what you will get if you delete this variable) looks
something like:
<P>
<CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
<P>
where the day of the week is only included if it is available in the
original message.
You can replace this default with text of your own.
The text may contain tokens which are replaced with text
which depends on the message you are replying to.
For example, the default is equivalent to:
<P>
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
<P>

Since this variable includes regular text mixed with special tokens
the tokens have to be surrounded by underscore characters.
For example, to use the token &quot;<SAMP>DATE</SAMP>&quot;
you would need to use &quot;<SAMP>_DATE_</SAMP>&quot;,
not &quot;<SAMP>DATE</SAMP>&quot;.
<P>
The list of available tokens is
<A HREF="h_index_tokens">here</A>.

<P>
For the adventurous, there is a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
It's explained in detail
<A HREF="h_reply_token_conditionals">here</A>.

<P>

If your &quot;Reply-Leadin&quot; turns out to be longer
than 80 characters when replying to a particular message, it is shortened.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_composer_wrap_column =====
<HTML>
<HEAD>
<TITLE>OPTION: Composer-Wrap-Column</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Composer-Wrap-Column</H1>


This option specifies an aspect of Pine's Composer.  This gives the
maximum width that auto-wrapped lines will have.  It's also the maximum
width of lines justified using the <A HREF="h_compose_justify">^J
Justify</A> command.  The normal default
is &quot;74&quot;.  The largest allowed setting is normally &quot;80&quot;
in order to
prevent very long lines from being sent in outgoing mail.  When the mail
is actually sent, trailing spaces will be stripped off of each line.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_viewer_overlap =====
<html>
<header>
<title>OPTION: Viewer-Overlap</title>
</header>
<body>
<h1>OPTION: Viewer-Overlap</h1>

This option specifies an aspect of Pine's Message Viewing screen.  When
the space bar is used to page forward in a message, the number of lines
specified by the "viewer-overlap" variable will be repeated from the
bottom of the screen.  That is, if this was set to two lines, then the
bottom two lines of the screen would be repeated on the top of the next
screen.  The normal default value is "2".<p>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</body>
</html>
====== h_config_scroll_margin =====
<HTML>
<HEAD>
<TITLE>OPTION: Scroll-margin</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Scroll-margin</H1>

This option controls when Pine's line-by-line scrolling occurs.
Typically, when a selected item is at the top or bottom screen edge
and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are struck, the
displayed items are scrolled down or up by a single line.

<P>
This option allows you to tell Pine the number of lines from the top and
bottom screen edge that line-by-line paging should occcur.  For example,
setting this value to one (1) will cause Pine to scroll the display
vertically when you move to select an item on the display's top or
bottom edge.

<P>
By default, this variable is zero, indicating that scrolling happens
when you move up or down to select an item immediately off the display's
top or bottom edge.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_reply_indent_string =====
<HTML>
<HEAD>
<TITLE>OPTION: Reply-Indent-String</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Reply-Indent-String</H1>

This variable specifies an aspect of Pine's Reply command.  When a
message is replied to and the text of the message is included, the
included text usually has the string &quot;&gt; &quot;, the default, prepended
to each line indicating it is quoted text.

<P>
This variable specifies a different value for that string.  If you wish to
use a string which begins or ends with a space, enclose the string in double
quotes.

<P>
Besides a simple text, the prepended string can be dynamically based
on the message being replied to.  The following tokens are substituted
for the message's corresponding value:

<DL>
<DT>_FROM_</DT>
<DD>This token gets replaced with the message sender's &quot;username&quot;.
</DD>

<DT>_NICK_</DT>
<DD>This token gets replaced with the nickname of the message sender's
address as found in your addressbook.  If no addressbook entry is found,
Pine behaves as if &quot;_NICK_&quot; was not set.
</DD>

<DT>_INIT_</DT>
<DD>This token gets replaced with the message's sender's initials.
</DD>

</DL>

NOTE: When the
<A HREF="h_config_prefix_editing">&quot;enable-reply-indent-string-editing&quot;</A>
feature is enabled, you are given the opportunity to edit the string, whether 
it is the default or one automatically generated using the above tokens.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_empty_hdr_msg =====
<HTML>
<HEAD>
<TITLE>OPTION: Empty-Header-Message</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Empty-Header-Message</H1>

When sending, if all of the To, Cc, and Newsgroups fields are empty,
Pine will put a special address in the To line.  The default value is:

<P>
<CENTER><SAMP>Undisclosed&nbsp;recipients:&nbsp;;</SAMP></CENTER>

<P>
The reason for this is to avoid embarrassment caused by some Internet
mail transfer software that interprets a &quot;missing&quot;
<SAMP>To:</SAMP> header as an error and replaces it with an
<SAMP>Apparently-to:</SAMP> header that may contain the addresses you
entered on the <SAMP>Bcc:</SAMP> line, defeating the purpose of the
Bcc.  You may change the part of this message that comes before the
&quot;:&nbsp;;&quot; by setting the &quot;empty-header-message&quot;
variable to something else.

<P>
The normal default is &quot;Undisclosed&nbsp;recipients&quot;.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_status_msg_delay =====
<HTML>
<HEAD>
<TITLE>OPTION: Status-Message-Delay</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Status-Message-Delay</H1>

If this is set to a positive number, it causes the cursor to move to the
status line whenever a status message is printed and pause there for this
many seconds.  It will probably only be useful if the 
<A HREF="h_config_show_cursor">&quot;show-cursor&quot;</A> feature is also turned on.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_mailcheck =====
<html>
<header>
<title>OPTION: Mail-Check-Interval</title>
</header>
<body>
<h1>OPTION: Mail-Check-Interval</h1>

This options specifies, in seconds, how often Pine will check for new
mail.  If set to zero, new-mail checking is disabled.  There is a minimum
value, normally 15 seconds.<p>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</body>
</html>
====== h_config_news_active =====
<html>
<header>
<title>OPTION: News-Active-File-Path</title>
</header>
<body>
<h1>OPTION: News-Active-File-Path</h1>

This option tells Pine where to look for the "active file" for newsgroups
when accessing news locally, rather than via NNTP.  The default path is
usually "/usr/lib/news/active".<p>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</body>
</html>
====== h_config_news_spool =====
<html>
<header>
<title>OPTION: News-Spool-Directory</title>
</header>
<body>
<h1>OPTION: News-Spool-Directory</h1>
This option tells Pine where to look for the "news spool" for newsgroups
when accessing news locally, rather than via NNTP.  The default path is
usually "/usr/spool/news".<p>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</body>
</html>
====== h_config_image_viewer =====
<html>
<header>
<title>OPTION: Image-Viewer</title>
</header>
<body>
<h1>OPTION: Image-Viewer</h1>
<body>
This option specifies the program Pine should call to view MIME
attachments of type IMAGE (e.g. GIF or TIFF).  The Image Viewer setting is
no longer needed, but remains for backward compatibility.  The more
general method for associating external printing and viewing programs with
specific MIME data types is to use the system's (or your personal)
"mailcap" configuration file.<p>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</body>
</html>
====== h_config_domain_name =====
<HTML>
<HEAD>
<TITLE>OPTION: Use-Only-Domain-Name</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Use-Only-Domain-Name</H1>

This option is used only if the 
<A HREF="h_config_user_dom">&quot;user-domain&quot;</A> option is <B>not</B> 
set.  If set to &quot;Yes&quot; (and user-domain is not used), then Pine 
strips the hostname from your return (&quot;From&quot;) address and when 
completing unqualified addresses that you enter into the composer.
<P>
If you set this, see also the <A HREF="h_config_quell_local_lookup">
&quot;quell-user-lookup-in-passwd-file&quot;</A> feature.


<!--chtml if pinemode="os_windows"-->
<P>This option is not applicable to PC-Pine.
<!--chtml else-->
<P>
<!--chtml endif-->
<UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_prune_date =====
<HTML>
<HEAD>
<TITLE>OPTION: Last-Time-Prune Question</TITLE>
</HEAD>
<BODY>
<H1>OPTION: Last-Time-Prune Question</H1>

This value records the last time you were asked about deleting old
sent-mail. It is set automatically by Pine at the beginning of each
month. If you wish to suppress the monthly sent-mail pruning feature, set
this to a date in the future.  This value is relative to the year 1900, so 
to set this, for example, to October 2005, use 105.10; to set it to 
May 1999, to 99.05.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_goto_default =====
<HTML>
<HEAD>
<TITLE>OPTION: goto-default-rule</TITLE>
</HEAD>
<BODY>
<H1>OPTION: goto-default-rule</H1>

This value affects Pine's behavior when you use the Goto command.
Pine's usual behavior has two parts.  If your current folder is
&quot;Inbox&quot;, Pine will offer the last open folder as the
default.  If the current folder is other than &quot;Inbox&quot;,
&quot;Inbox&quot; is offered as the default.

<P>
The available options include:

<DL>
<DT>inbox-or-folder-in-recent-collection</DT>
<DD>
This is the default described above.
</DD>

<DT>inbox-or-folder-in-first-collection</DT>
<DD>This option is a variation on the default which again offers
&quot;Inbox&quot; if it isn't currently open, but otherwise offers the
most recent folder in the first collection found in the &quot;FOLDER
LIST&quot; screen.
</DD>

<DT>most-recent-folder</DT>
<DD>This option simply causes the most recently opened folder
to be offered as the default regardless of the currently opened folder.
</DD>
</DL>

<P>
NOTE: The default while a newsgroup is open remains the same; the last
open newsgroup.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_inc_startup =====
<HTML>
<HEAD>
<TITLE>OPTION: incoming-startup-rule</TITLE>
</HEAD>
<BODY>
<H1>OPTION: incoming-startup-rule</H1>

This value affects Pine's behavior when opening the &quot;INBOX&quot; or 
one of the &quot;INCOMING MESSAGE FOLDERS&quot;.  By default, when the 
&quot;INBOX&quot; or another
incoming folder is first opened, the current message is set to the first
unseen message which has not been marked deleted, or the last message if
all of the messages have been seen previously.

<P>
The four possible values for this option are:

<DL>
<DT>first-unseen</DT>
<DD>This is the default described above.
</DD>

<DT>first-recent</DT>
<DD>Similar to the default, but rather than starting on the first
unseen message Pine starts you on the first <EM>recent</EM> message.
A message is recent if it arrived since the last time the folder was
open.  This value causes the current message to be set to the first
recent and undeleted message if there is one, otherwise the last
message in the folder.
</DD>

<DT>First</DT>
<DD>Simply starts you on the <EM>first</EM> undeleted message in the folder.
If all messages are deleted you start on the last message.
</DD>

<DT>Last</DT>
<DD>Simply starts you on the <EM>last</EM> undeleted message in the folder
If all messages are deleted you start on the last message.
</DD>
</DL>

<P>
NOTE:  For newsgroups in the incoming collection, &quot;first-unseen&quot; and
&quot;first-recent&quot; are the same and are affected by whether or not the
feature 
<A HREF="h_config_news_uses_recent">&quot;news-approximates-new-status&quot;</A> is turned on.  

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_browser =====
<HTML>
<HEAD>
<TITLE>OPTION: url-viewers</TITLE>
</HEAD>
<BODY>
<H1>OPTION: url-viewers</H1>
<!--chtml if pinemode="os_windows"-->
PC-Pine users do not need to enter anything here, unless:<UL>
<LI> they want to override, for use with Pine, the application defined
in the Windows operating system for handling URLs; or
<LI> they are (planning on) using the same configuration file with 
Unix Pine.
</UL><HR><P>
<!--chtml endif-->
This option affects Pine's handling of URLs that are found in 
messages you read.  Normally, only URLs Pine can handle directly
are automatically offered for selection in the &quot;Message
Text&quot; screen.  When one or more applications
capable of deciphering URLs on their command line are added here, Pine
will choose the first available to display URLs it cannot handle directly.
A viewer's availability is based on its being specified with a <B>full
directory path</B> and the evaluation of any optionally supplied
parameters described below.

<P>
Additionally, to support various connection methods and applications, each
entry in this list can optionally begin with one or more of
the following special tokens.  The allowed tokens include:

<P>
<DL>
<DT>_TEST(<VAR>test-string</VAR>)_</DT>
<DD>
The <VAR>test-string</VAR> is a shell command that Pine will run to
evaluate a viewer's availability.  The command specified by the test
string is run and if its resulting exit status is non-zero, Pine will
not consider the associated viewer for use.
</DD>

<DT>_SCHEME(<VAR>scheme-list</VAR>)_</DT>
<DD>
The <VAR>scheme-list</VAR> is a list of one or more (comma-delimited)
URL schemes that are to be used with the associated viewer.  This is
the way to configure Pine to recognize URLs other than the built-in set.
<P>
It can also be used to override Pine's built-in handlers.
For example, you could specify &quot;news&quot; in the <VAR>scheme-list</VAR>,
and Pine would use (provided it passed all other criteria) the associated
viewer when it encounterd a URL of the form &quot;news:comp.mail.pine&quot;.

</DD>
</DL>

<P>
By default, Pine will simply append a space character followed by the
selected URL prior to launching the command in your specified SHELL.  You can
optionally specify where in the command the selected URL should appear
by using the &quot;_URL_&quot; token.  All occurrences found in the command
will be replaced with the selected URL before the command is handed
to the shell.  If such replacement occurs, the default appending of the
selected URL does not take place.

<P>
NOTE: If the viewer you specify has any command-line arguments,
including the &quot;_URL_&quot; token, you will need to add a
double-quote character before the command path and after the last
argument (see the &quot;lynx&quot; example below).

<P>
So, here are some example entries:
<PRE>
url-viewers = _TEST(&quot;test -n '$&#123;DISPLAY}'&quot;)_  /usr/local/bin/netscape
              &quot;/usr/local/bin/lynx _URL_&quot;
              C:&#92;BIN&#92;NETSCAPE.BAT
</PRE>
<P>
This example shows that for the first viewer in the list to be used
the environment variable &quot;DISPLAY&quot; must be defined.  If it
is, then the path and file &quot;/usr/local/bin/netscape&quot; must exist.  
If neither condition is met,
then the path and file &quot;/usr/local/bin/lynx&quot; must exist.  
If it does, then the &quot;_URL_&quot; token is replaced by the selected URL. 
If the path to &quot;lynx&quot; is invalid,
then the final path and file C:&#92;BIN&#92;NETSCAPE.BAT must exist.  
Note that the last
entry is a DOS/Windows path.  This is one way to support Pine running
on more than one architecture with the same configuration file.<P>
<P>
<!--chtml if pinemode="os_windows"-->
<!--chtml else-->
Note that depending on the type of browser used and the method of 
its invocation (such as whether it will open in a separate window) from
the MESSAGE TEXT screen, the browser may &quot;supplant&quot; 
the MESSAGE TEXT screen, and you will have to quit the browser to return to 
it (for example, when using Lynx; to exit Lynx, use the &quot;Q&quot; command).
In other words, launching the browser from Pine may make Pine 
&quot;disappear&quot; (although it is still &quot;running&quot;)
until you close the browser again.<P>  
<UL><LI><A HREF="h_config_browser_xterm">Defining url-viewers in an X windows 
environment: for advanced users and  systems administrators</A>
</UL>
<!--chtml endif-->
<P>If you are unsure what browsers are available on your system or how to 
specify them in Pine's url-viewers option for best usability, contact your 
local computing support staff.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_browser_xterm =====
<HTML>
<HEAD>
<TITLE>url-viewers and X windows applications</TITLE>
</HEAD>
<BODY>
<H1>Defining url-viewers in an X windows 
environment: for advanced users and  systems administrators</H1>
If you are using Pine with an X-terminal (emulator) and want to define an 
X windows-based application in url-viewers, 
you may want to do so in a manner that causes any <B>already</B> 
invoked viewer application to be used for viewing URLs you select from Pine 
messages, and a <B>new</B> URL-viewer process to be 
started <B>only</B> if the same application has <B>not already</B> 
been launched -- for one reason, to avoid file-locking contentions among 
multiple invocations of the same URL-viewer application.  
(The example entries set in the help screen for the &quot;url-viewers&quot; 
option does not do this.)  A method of doing that would be:<OL>
<LI> use 
the _TEST(<VAR>test-string</VAR>)_ token in the <B>first</B> entry to 
check (using commands appropriate for your Unix shell
in place of <VAR>test-string</VAR>) for the presence of a 
lockfile created by the URL-viewer application -- which implies that the 
application is already running, though this is not foolproof. 
Following that in the same url-viewers entry, specify the 
application with its appropriate command line option(s) to 
show the URL selected from the Pine message in an already open window of 
that application, or perhaps in a new window of that application.  

<LI> In the 
<B>second</B> entry for the url-viewers option, specify the same 
application without those command line options, but this time using the 
_TEST(...)_ token to check whether the environment variable &quot;DISPLAY&quot;
is defined.
<LI> If you may be using Pine (with the same .pinerc file) outside of the X 
windows environment (for instance, using VT-100 terminal emulation), you 
may wish to specify a non-X windows URL-viewer application such as Lynx
as the last entry.
</OL><BR>
How exactly you define your url-viewers entries to do this will depend on 
the command shell, the URL-viewer application(s), and possibly the specific 
version of the latter, you are using.  
<P>
Relevant command 
line options for the Netscape browser for showing URLs (selected from Pine) 
when Netscape is already running are discussed in the document
&quot;Remote Control of UNIX Netscape&quot; 
found at the URL (as of 12 Aug. 1998):
<P>

<CENTER><A HREF="http://home.netscape.com/newsref/std/x-remote.html">http://home.netscape.com/newsref/std/x-remote.html</A></CENTER>

<P>(If the URL-viewer application is 
<B>not</B> running on the same host as Pine, but being launched from an 
applications server, you may not be able to use the command line options for 
using an existing invocation of the application in Pine's url-viewers entry.)
<P>
<!--chtml if this-method="shown-to-work"-->
An example using the Korn shell and the Netscape browser (first entry wrapped 
because of its length, but should all appear on one line):
<P>
url-viewers = _TEST("test -L /myhomedir/.netscape/lock")_ &quot;/usr/local/bin/netscape -remote 'openURL(_URL_,  new-window)' &amp;&quot;<BR>

_TEST(&quot;test -n '$&#123;DISPLAY}'&quot;)_ &quot;/usr/local/bin/netscape &amp;&quot;<BR>
              &quot;/usr/local/bin/lynx '_URL_'&quot;
<P>
<!--chtml endif-->
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_enable_full_hdr =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-full-header-cmd</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-full-header-cmd</H1>

This feature enables the &quot;H Full Headers&quot; command which toggles between
the display of all headers in the message and the normal edited view of
headers.  The Full Header command also controls which headers are included
for Export, Pipe, Print, Forward, and Reply functions.  (For Reply, the
Full Header mode will respect the
<A HREF="h_config_include_header">&quot;include-headers-in-reply&quot;</A>
feature setting.)
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_enable_pipe =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-unix-pipe-cmd</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-unix-pipe-cmd</H1>

This feature enables the "| Pipe" command that sends the current message
to the specified Unix command for external processing.  Not available on
PC-Pine.
<P>

A short description of how the pipe command works is given
<A HREF="h_pipe_command">here</A>.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_enable_tab_complete =====
        FEATURE: enable-tab-completion

This feature enables the TAB key when at a prompt for a filename. In this
case, TAB will cause the partial name already entered to be automatically
completed, provided the partial name is unambiguous.

<End of help on this topic>
====== h_config_quit_wo_confirm =====
         FEATURE: quit-without-confirm

This feature controls whether or not Pine will ask for confirmation when a
Quit command is received.

<End of help on this topic>
====== h_config_enable_jump =====
         FEATURE: enable-jump-shortcut

Setting this feature will allow you to enter a number (followed by RETURN)
and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT
screens.  In other words, it obviates the need for typing the "J" for the
Jump command.

<End of help on this topic>
====== h_config_enable_alt_ed =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-alternate-editor-cmd</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-alternate-editor-cmd</H1>

If this feature is set, and the 
<A HREF="h_config_editor">&quot;editor&quot;</A> option
<B>is not</B> set, entering
the ^_ (Control-underscore) key while composing a message will prompt you
for the name of the editor you would like to use.
<P>
If the environment variable $EDITOR is set, its value will be offered as
a default.
<P>
If the <A HREF="h_config_editor">&quot;editor&quot;</A> option
<B>is</B> set, the ^_ key will activate the specified
editor without prompting, in which case it is not necessary to
set the &quot;enable-alternate-editor-cmd&quot; feature.  
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_alt_ed_now =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-alternate-editor-implicitly</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-alternate-editor-implicitly</H1>

If this feature and the <A HREF="h_config_editor">&quot;editor&quot;</A>
variable are both set, Pine will
automatically activate the specified editor when the cursor is moved from
the header of the message being composed into the message text.  For
replies, the alternate editor will be activated immediately.  If this
feature is set but the &quot;editor&quot; variable is not set, then Pine will
automatically ask for the name of an alternate editor when the cursor
is moved out of the header being composed, or if a reply is being done.

<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_enable_bounce =====
         FEATURE: enable-bounce-cmd

Setting this feature enables the "B Bounce" command, which will prompt
for an address and *remail* the message to the new recipient.  This command
is used to re-direct messages that you have received in error, or need to
be redirected for some other reason (e.g. list moderation).  The final
recipient will see a header indicating that you have Resent the msg, but
the message's From: header will show the original author of the message,
and replies to it will go back to that author, and not to you.

<End of help on this topic>
====== h_config_enable_agg_ops =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-aggregate-command-set</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-aggregate-command-set</H1>
Setting this feature enables the commands and subcommands that relate to
performing operations on more than one message at a time.  We call these
&quot;aggregate operations&quot;.  In particular, the 
<!--chtml if pinemode="function_key"-->&quot;F5
<!--chtml else-->&quot;;
<!--chtml endif--> Select&quot;, 

<!--chtml if pinemode="function_key"-->
&quot;F6
<!--chtml else-->
&quot;A 
<!--chtml endif-->
Apply&quot;, and 
<!--chtml if pinemode="function_key"-->
&quot;F4
<!--chtml else-->
&quot;Z 
<!--chtml endif-->
Zoom&quot; commands are enabled by this feature.  Select is used to
&quot;tag&quot; one or more messages meeting the specified criteria.  Apply can
then be used to apply any message command to all of the selected/tagged
messages.  Further, the Zoom command allows you to toggle the MESSAGE INDEX
view between just those Selected and all messages in the folder.
<P>
This feature also enables the 
<!--chtml if pinemode="function_key"-->
&quot;F7&quot; 
<!--chtml else-->
&quot;^X&quot; 
<!--chtml endif-->

subcommand in the MESSAGE INDEX 
WhereIs command which causes all messages matching the WhereIs argument to 
become selected; and the Select, Select Current, and ZoomMode commands in the
<A HREF="h_folder_maint">FOLDER LIST screen</A>.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>

====== h_config_enable_flag =====
         FEATURE: enable-flag-cmd

Setting this feature enables the "* Flag" command which allows you to
manipulate the status flags associated with a message.  By default, Flag
will set the "Important" flag, which results in an asterisk being
displayed in column one of the MESSAGE INDEX for such messages.

<End of help on this topic>
====== h_config_flag_screen_default =====
         FEATURE: enable-flag-screen-implicitly

The feature modifies the behavior of the "* Flag" command (provided it
too is enabled).  By default, when the "* Flag" command is selected,
Pine offers a prompt to set one of several flags and also offers the
option of entering the detailed flag manipulation screen via the "^T"
key. Enabling this feature causes Pine to immediately enter the detailed
flag screen rather than first offer the simple prompt.

<End of help on this topic>
====== h_config_can_suspend =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-suspend</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-suspend</H1>

Setting this feature will allow you to type ^Z (Control Z) to 
<!--chtml if pinemode="os_windows"-->
minimize Pine into its icon, bringing into focus whatever
application is running behind the PC-Pine window.
<!--chtml else-->
temporarily suspend Pine.

<P>
This does not exit Pine, but puts it in the background to watch
for new mail and such.  Normally, you type a command, such
as &quot;fg&quot; at your system prompt to return to your Pine session.

<P>
The <A HREF="h_config_suspend_spawns">use-subshell-for-suspend</A> feature
adjusts whether Pine is placed into the background of the shell its 
running in or starts a news shell.
<!--chtml endif-->

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_take_lastfirst ======
         FEATURE: disable-take-last-comma-first

Normally, when TakeAddr is used to copy an address from a message into
an address book entry, Pine will attempt to rewrite the full name of the
address in the form

       Last, First

instead of

       First Last

It does this because many people find it useful to sort by Last name instead
of First name.  If this feature is set, then the TakeAddr command will
not attempt to reverse the name in this manner.

<End of help on this topic>
====== h_config_print_from ======
         FEATURE: print-includes-from-line

If this feature is set, then the Berkeley-mail style From line is included
at the start of each message that is printed.  This line looks something
like the following, with the address replaced by the address from the
From line of the message being printed:

   From user@domain.somewhere.com Mon May 13 14:11:06 1998

<End of help on this topic>
====== h_config_expanded_distlists ======
         FEATURE: expanded-view-of-distribution-lists

If this feature is set, then distribution lists in the address book
screen will always be expanded automatically.

<End of help on this topic>
====== h_config_compose_news_wo_conf ======
         FEATURE: compose-sets-newsgroup-without-confirm

This feature controls one aspect of Pine's Composer.  If you enter the
composer while reading a newsgroup, you will normally be prompted to
determine whether you intend the new message to be posted to the current
newsgroup or not.  If this feature is set, Pine will not prompt you
in this situation, and will assume that you do indeed wish to post
to the newsgroup you are reading.

<End of help on this topic>
====== h_config_compose_rejects_unqual ======
<HTML>
<HEAD>
<TITLE>FEATURE: compose-rejects-unqualified-addrs</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: compose-rejects-unqualified-addrs</H1>

This feature controls one aspect of the message composer; in particular,
what happens when an unqualified name is entered into an address header.
If set, unqualified names entered as addresses will be treated as errors
unless they match an addressbook nickname.  Pine will not attempt to turn
them into complete addresses by adding your local domain.<P>

A complete (fully qualified) address is one containing a username followed
by an &quot;@&quot; (&quot;at&quot;) symbol, followed by a domain name (e.g.
&quot;jsmith@nowhere.edu&quot;).  An unqualified name is one <B>without</B> 
the &quot;@&quot; symbol and domain name (e.g. &quot;jsmith&quot;). 

(See also <A HREF="h_address_format">Explanation of Address formats</A>.)

<P>

When you enter a fully qualified address, Pine does not interpret or
modify it, but simply passes it on to the mail-transport-agent (MTA) for
your system.  Pine conforms to the Internet standards governing message
headers and will not send an unqualifed name to the MTA.  Therefore, when
you enter an unqualified name, Pine will normally attempt to turn it into
a fully qualified address, first by checking to see if you have entered a
matching nickname in your addressbook, or failing that, by simply adding
your own domain to the name entered.  So if your address is
&quot;jsmith@nowhere.edu&quot; and you enter &quot;fred&quot;, then (assuming 
&quot;fred&quot; is not a nickname in your addressbook), Pine will turn 
that into &quot;fred@nowhere.edu&quot;.<P>

There are situations where it is not desirable for Pine to interpret such
unqualified names as valid (local) addresses.  For example, if &quot;fred&quot;
turned out to be a typo (intended to be an addressbook nickname), but
there actually was a &quot;fred&quot; in your local domain, the message might 
be mis-delivered without your realizing it.  In order to reduce the likelihood
of such accidents, setting this feature will cause Pine to treat such
addresses as errors, and require that you explicitly enter the full local
address (e.g. &quot;fred@nowhere.edu&quot;) or correct the name so that it 
matches an address book nickname.<P>

Consider this a safety feature against mis-directed mail.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_quell_local_lookup ======
<HTML>
<HEAD>
<TITLE>FEATURE: quell-user-lookup-in-passwd-file</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: quell-user-lookup-in-passwd-file</H1>

This feature controls an aspect of Pine's Composer, and if needed, will
usually be set by your system manager in Pine's system-wide configuration
file. Specifically, if this feature is set, Pine will not attempt to look
in the system password file to find a Full Name for the entered address.
<P>
Normally, names you enter into address fields (e.g. To: or Cc:) are
checked against your address book(s) to see if they match an address book
nickname.  Failing that, (in Unix Pine) the name is then checked against
the Unix password file.  If the entered name matches a username in the
system password file, Pine extracts the corresponding Full Name information
for that individual, and adds that to the address being entered.
<P>
However, password file matching can have surprising (incorrect) results if
other users of the system do not receive mail at the domain you are using.
That is, if either the 
<A HREF="h_config_user_dom">&quot;user-domain&quot;</A> or 
<A HREF="h_config_domain_name">&quot;use-only-domain-name&quot;</A>
option
is set such that the administrative domain of other users on the system
isn't accurately reflected, Pine should be told that a passwd file match
is coincidental, and Full Name info will be incorrect.  For example, a
personal name from the password file could get falsely paired with the
entered name as it is turned into an address in the configured domain.
<P>
If you are seeing this behavior, enabling this feature will prevent Unix
Pine from looking up names in the password file to find the Full Name
for incomplete addresses you enter.<P>
<UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_preserve_start_stop ======
         FEATURE: preserve-start-stop-characters

This feature controls how special control key characters, typically
Ctrl-S and Ctrl-Q, are interpreted when input to Pine.  These characters
are known as the "start" and "stop" characters and are sometimes used in
communications paths to control data flow between devices that operate at
different speeds.

By default, Pine turns the system's handling of these special characters
off except during printing.  However, if you see Pine reporting input errors
such as:

            [ Command "^Q" not defined for this screen. ]

and, at the same time, see your display become garbled, then it is likely
that setting this option will solve the problem.  Be aware, though, that
enabling this feature will also cause Pine to ostensibly "hang" 
whenever the Ctrl-S key combination is entered as the system is now
interpreting such input as a "stop output" command.  To "start
output"  again, simply type Ctrl-Q. 

<End of help on this topic>
====== h_config_enable_incoming ======
<HTML>
<HEAD>
<TITLE>FEATURE: enable-incoming-folders</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-incoming-folders</H1>

If set, this feature defines a pseudo-folder collection called
&quot;INCOMING MESSAGE FOLDERS&quot;.  Initially, the only folder included
in this collection will be your INBOX, which will no longer show up in
your Default folder collection.
<P>

You may add more folders to the Incoming Message Folders collection by
using the
<!--chtml if pinemode="function_key"-->
&quot;F10
<!--chtml else-->
&quot;A
<!--chtml endif-->
Add&quot; command in the FOLDER LIST screen.  You will be prompted for
the host the folder is stored on (which defaults to the same host used
for your INBOX), a nickname, and the actual folder name.  Once a set
of Incoming Message Folders are defined, the TAB key (in MESSAGE INDEX
or MESSAGE TEXT screens) may be used to scan the folders for those
with Recent messages.  If you add more folders to
your Incoming-Folders collection, turning this feature back off will have
no effect.
<P>
NOTE: Pine does <B>not</B> do &quot;delivery filtering&quot;; this is the
province of other programs such as &quot;filter&quot; or
&quot;procmail&quot;.  Pine's Incoming Message Folders collection
provides a convenient way to access multiple incoming folders, once
they are created by other programs.  It is also useful if you have
accounts on multiple computers.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_attach_in_reply ======
         FEATURE: include-attachments-in-reply

This feature controls an aspect of Pine's Reply command. If set, any MIME
attachments that were part of the original message will automatically be
included in the Reply.

<End of help on this topic>
====== h_config_include_header =====
         FEATURE: include-header-in-reply

This feature controls an aspect of Pine's Reply command. If set, and the
original message is being included in the reply, then headers from that
message will also be part of the reply.

<End of help on this topic>
====== h_config_sig_at_bottom =====
        FEATURE: signature-at-bottom

This feature controls an aspect of Pine's Reply command.  If this feature
is set, and the original message is being included in the reply, then the
contents of your signature file (if any) will be inserted after the included
message.

This feature does not affect the results of a Forward command.

<End of help on this topic>
====== h_config_sigdashes =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-sigdashes</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-sigdashes</H1>

This feature enables support for the common USENET news convention 
of preceding a message signature with the special line consisting of 
the three characters &quot;--&nbsp;&quot; (i.e., dash, dash, and space).

<P>
When enabled and a
&quot;<A HREF="h_config_signature_file">signature-file</A>&quot; exists,
Pine will insert the special line before including the file's text (unless
the special line already exists somewhere in the file's text).

<P>
In addition, when you Reply or Followup to a message containing one of
these special lines and choose to include its text, Pine will observe
the convention of not including text beyond the special line in your
reply.

<P>
See also &quot;<a href="h_config_strip_sigdashes">strip-from-sigdashes-on-reply</a>&quot;
for a related feature.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_strip_sigdashes =====
<HTML>
<HEAD>
<TITLE>FEATURE: strip-from-sigdashes-on-reply</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: strip-from-sigdashes-on-reply</H1>

This feature doesn't do anything if the feature
&quot;<A HREF="h_config_sigdashes">enable-sigdashes</A>&quot; is turned on.
However, if the &quot;enable-sigdashes&quot; feature is not turned on,
then turning on this feature enables support for the convention
of not including text beyond the sigdashes line when Replying or Following
up to a message and including the text of that message.
<P>
In other words, this is a way to turn on the signature stripping behavior
without also turning on the dashes-adding behavior.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_sub_lists =====
        FEATURE: enable-partial-match-lists

This feature affects the subcommands available when Saving, 
or when Opening a new folder. If set, the subcommand ^X ListMatches will be
available. This command allows you to type in a substring of the folder
you are looking for and when you type ^X it will display all folders
which contain that substring in their names.

<End of help on this topic>
====== h_config_use_sender_not_x =====
        FEATURE: use-sender-not-X-Sender

Normally Pine adds a header line labeled X-Sender, if the sender is
different from the From: line.  The standard specifies that this header
line should be labeled Sender, not X-Sender.  Setting this feature causes
Sender to be used instead of X-Sender.

<End of help on this topic>
====== h_config_use_fk =====
        FEATURE: use-function-keys

This feature specifies that Pine will respond to function keys instead of
the normal single-letter commands. In this mode, the key menus at the
bottom of each screen will show function key designations instead of the
normal mnemonic key.

<End of help on this topic>
====== h_config_compose_maps_del =====
        FEATURE: compose-maps-delete-key-to-ctrl-d

This feature affects the behavior of the DELETE key.
If set, Delete will be equivalent to Control-D, and delete
the current character.  Normally Pine defines the Delete key
to be equivalent to Control-H, which deletes the *previous*
character.

<End of help on this topic>
====== h_config_compose_bg_post =====
        FEATURE: enable-background-sending

This feature affects the behavior of Pine's mail sending.  If set, this
feature enables a subcommand in the composer's "Send?" confirmation
prompt.  The subcommand allows you to tell Pine to handle the actual
posting in the background.  While this feature usually allows posting
to appear to happen very fast, it has no affect on the actual delivery
time it takes a message to arrive at its destination.

NOTE 1: This feature isn't supported on all systems.  All DOS and Windows,
        as well as several Unix ports, do not recognize this feature.

NOTE 2: Error handling is significantly different when this feature is
        enabled.  Any message posting failure results in the message
        being appended to your "Interrupted" mail folder.  When you
        type the "Compose" command, Pine will notice this folder and
        offer to extract any messages contained.  Upon continuing a 
        failed message, Pine will display the nature of the failure 
        in the status message line.

WARNING: Under extreme conditions, it is possible for message data to
         get lost.  Do not enable this feature if you typically run close
         to any sort of disk-space limits or quotas.

<End of help on this topic>
====== h_config_compose_dsn =====
        FEATURE: enable-delivery-status-notification

This feature affects the behavior of Pine's mail sending.  If set, this
feature enables a subcommand in the composer's "Send?" confirmation
prompt.  The subcommand allows you to tell Pine to request the type of
Delivery Status Notification (DSN) which you would like.  Most users will
be happy with the default, and need not enable this feature.

Turning on this feature and then turning on the DSNOpts from the send
prompt reveals four on-off toggles at the bottom of the screen.
The "X" command toggles between NoErrRets and ErrRets.  NoErrRets requests
that no notification be returned to you, even if there is a delivery
failure.  The "D" key toggles between Delay and NoDelay.  This tells the
server that you are willing (or not) to receive delay notifications, which
happen when there is an unusual delay at some mail server (in that mail
server's opinion).  The "S" key toggles between Success and NoSuccess.
Success requests that you be sent a DSN message when the message is
successfully delivered to the recipients mailbox.  Setting NoErrRets will
automatically turn off Delay and Success notification, and will flip the
toggles to show that.  Similarly, turning on Delay and/or Success will
automatically toggle the "X" key to ErrRets.  The fourth command, the
"H" key, toggles between RetHdrs and RetFull.  RetFull requests that
the full message be returned in any failed DSN.  RetHdrs requests that
only the headers be returned in any failed DSN.  Notice that this command
applies only to failed delivery status reports.  For delay or success
reports, the full message is never returned, only the headers are returned.

If you don't enable the DSN feature or if you don't turn it on for a
particular message, the default is that you will be notified about failures,
you might be notified about delays, and you won't be notified about
successes.  You will usually receive the full message back when there is
a failure.

If you turn on the DSNOpts the default is to return as much information as
possible to you.  That is, by default, the Success and Delay options are
turned on and the full message will be returned on failure.

The sending prompt will display the current DSN request (if any) in a
shorthand form.  It will be:

		 [Never]

if you have requested NoErrRets.  Otherwise, it will look something like:

		 [FDS-Hdrs]

The "F" will always be there, indicating that you will be notified
of failures.  (Pine doesn't provide a way to request no failure notification
and at the same time request either success or delay notification.  The only
way to request no failure notifications is to request no notifications at
all with NoErrRets.)  The "D" and/or "S" will be present if you have
requested Delay and/or Success notification.  If one of those is missing,
that means you are requesting no notification of the corresponding type.
After the dash it will say either Hdrs or Full.  Hdrs means to return only
the headers and Full means to return the full message (applies to
failure notifications only).

Note, this feature relies on your system's mail transport agent or
configured "smtp-server" having the negotiation mechanism introduced in
"Extended SMTP" (ESMTP) and the specific extension called
"Delivery Status Notification" (DSN).  If the mail tranport agent you
are using doesn't support DSN, a short warning will be shown to you on
the message line at the bottom of the screen after you send your message,
but your message will have been sent anyway.

Note that DSNs don't provide a mechanism to request read receipts.  That
is, if you request notification on success you are notified when the
message is delivered to the mailbox, not when the message is read.

ESMTP allows for graceful migration to upgraded mail transfer agents, but
it is possible that this feature might cause problems for some servers. 

<End of help on this topic>
====== h_config_auto_zoom =====
        FEATURE: auto-zoom-after-select

This feature affects the behavior of the Select command.
If set, the select command will automatically perform a zoom
after the select is complete.

<End of help on this topic>
====== h_config_auto_unzoom =====
        FEATURE: auto-unzoom-after-apply

This feature affects the behavior of the Apply command.  If set, and if
you are currently looking at a Zoomed Index view of selected messages,
the Apply command will do the operation you specify, but then will
implicitly do an "UnZoom", so that you will automatically be back in
the normal Index view after the Apply. 

<End of help on this topic>
====== h_config_fast_recent =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-fast-recent-test</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-fast-recent-test</H1>

This feature controls the behavior of the TAB key when traversing folders
in the optional 
<A HREF="h_config_enable_incoming">&quot;incoming-folders&quot; collection</A> 
or in optional news-collections.

<P>
When the TAB (Next New) key is pressed, the default behavior is to
explicitly examine the status of the folder for the number of recent
messages (messages delivered since the last time it was viewed).
Depending on the size and number of messages in the folder, this test
can be time consuming.

<P>
Enabling this feature will cause Pine to only test for the existence of
any recent messages rather than the obtain the count.  This is much faster
in many cases.  The downside is that you're not given the number of recent
messages when prompted to view the next folder.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_arrow_nav =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-arrow-navigation</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-arrow-navigation</H1>

This feature controls the behavior of the left and right arrow keys.
If set, the left and right arrow keys will operate like the usual
navigation keys &lt; and &gt;.

<P>
If you set this feature, and do not like the changed behavior of the up/down 
arrow 
keys when navigating through the FOLDER LIST screen -- 
<B>first</B> from column to column, if more than one folder is 
displayed per row, 
and <B>then</B> from row to row -- you may either also wish to set the feature 
&quot;<A HREF="h_config_relaxed_arrow_nav">enable-arrow-navigation-relaxed</A>&quot;, 
&quot;<A HREF="h_config_single_list">single-column-folder-list</A>&quot;, or
use the ^P/^N (instead of up/down arrow) keys to move up/down the list of 
folders in each column.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_relaxed_arrow_nav =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-arrow-navigation-relaxed</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-arrow-navigation-relaxed</H1>

This feature controls the behavior of the left, right, up and down
arrow keys in the FOLDER LIST screen when the &quot;<A
HREF="h_config_arrow_nav">enable-arrow-navigation</A>&quot; feature is
enabled.

<P>
Normally, when the &quot;enable-arrow-navigation&quot; feature is set,
the left and right arrow keys in the Folder List screen strictly
track the commands bound to the '&lt;' and '&gt;' keys, and the up
and down arrow keys move the hilite bar to the previous and next
folder or directory name.

<P>

When enabled, this feature returns the left, right, up and down
arrow keys' functionality in the FOLDER LIST screen to what it was
before enabling
&quot;enable-arrow-navigation&quot;.  In other words, left and right
arrows move the hilite bar to the left or right, and the up and
down arrows move it up or down.


<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_del_from_dot =====
        FEATURE: compose-cut-from-cursor

This feature controls the behavior of the Control-K command in the composer.
If set, ^K will cut from the current cursor position to the end of the line,
rather than cutting the entire line.

<End of help on this topic>
====== h_config_print_index =====
        FEATURE: print-index-enabled

This feature controls the behavior of the Print command when in the
MESSAGE INDEX screen.  If set, the print command will give you a prompt
asking if you wish to print the message index, or the currently highlighted
message. If not set, the message will be printed.

<End of help on this topic>
====== h_config_allow_talk =====
        FEATURE: allow-talk

By default, permission for others to "talk" to your terminal is turned
off when you are running Pine.  When this feature is set, permission is
instead turned on.  If enabled, you may see unexpected messages in the
middle of your Pine screen from someone attempting to contact you via the
"talk" program.

Note: The "talk" program has nothing to do with Pine or email.  The 
talk daemon on your system will attempt to print a message on your screen 
when someone else is trying to contact you.  If you wish to see these
messages while you are running Pine, you should enable this feature.

If you do enable this feature and see a "talk" message, you must 
suspend or quit Pine before you can respond.

<End of help on this topic>
====== h_config_send_filter_dflt =====
<HTML>
<HEAD>
<TITLE>FEATURE: compose-send-offers-first-filter</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: compose-send-offers-first-filter</H1>
If you have <A HREF="h_config_sending_filter">&quot;sending-filters&quot;</A> 
configured, setting this feature will cause
the first filter in the sending-filters list to be offered as the default
instead of unfiltered, the usual default.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_custom_print =====
        FEATURE: print-offers-custom-cmd-prompt

When this feature is set, the print command will have an additional
subcommand called "C CustomPrint".  If selected, you will have
the opportunity to enter any system print command --instead of being 
restricted to using those that have been previously configured in the 
printer setup menu.

<End of help on this topic>
====== h_config_enable_dot_files =====
        FEATURE: enable-dot-files

When this feature is set, files beginning with dot (".") will be
visible in the file browser.  For example, you'll be able to select them
when using the browser to add an attachment to a message.

<End of help on this topic>
====== h_config_enable_dot_folders =====
        FEATURE: enable-dot-folders

When this feature is set, folders beginning with dot (".") may be added
and viewed.

<End of help on this topic>
====== h_config_ff_between_msgs =====
        FEATURE: print-formfeed-between-messages

Setting this feature causes a formfeed to be printed between messages when
printing multiple messages (with Apply Print command).

<End of help on this topic>
====== h_config_blank_keymenu =====
        FEATURE: disable-keymenu

If this feature is set the command key menu that normally appears on the
bottom two lines of the screen will not usually be there.  Asking for
help with ^G or ? will cause the key menu to appear instead of causing
the help message to come up.  If you want to actually see the help text,
another ^G or ? will show it to you.  After the key menu has popped
up with the help key it will remain there for an O for Other command but
disappear if any other command is typed.

<End of help on this topic>
====== h_config_enable_mouse =====
        FEATURE: enable-mouse-in-xterm

This feature controls whether or not an X terminal mouse can be used with
Pine.  If set, and the $DISPLAY variable indicates that an X terminal is
being used, the left mouse button on the mouse can be used to select text
or commands.

Note: if this feature is set, the behavior of X terminal cut-and-paste is
also modified.  It is necessary to hold the shift key down while clicking
left or middle mouse buttons for the normal xterm cut/paste operations. 

<End of help on this topic>
====== h_config_enable_xterm_newmail =====
        FEATURE: enable-newmail-in-xterm-icon

This feature controls whether or not Pine will attempt to announce new
mail arrival when it is running in an X terminal window and that window
is iconified.  If set, and the $DISPLAY variable indicates that an X
terminal is being used, Pine will send appropriate escape sequences to
the X terminal to modify the label on Pine's icon to indicate that new
mail has arrived. 

<End of help on this topic>
====== h_config_prefix_editing =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-reply-indent-string-editing</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-reply-indent-string-editing</H1>

This feature affects the Reply command's &quot;Include original message
in Reply?&quot; prompt.  When enabled, it causes the
&quot;Edit Indent String&quot; sub-command to appear which allows 
you to edit the string Pine would otherwise use to denote included 
text from the message being replied to.<P>

Thus, you can change Pine's default message quote character (usually
an angle bracket) on a per message basis. So you could change your quoted message to
look, for example, like this:<p>
 
<pre>On Tues, 26 Jan 1999, John Q. Smith wrote:
 
JS> I just wanted to say hello and to congratulate you
JS> on a job well done!</pre><p>

NOTE: Edited reply-indent-strings only apply to the message
currently being replied to.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_enable_search_and_repl =====
        FEATURE: enable-search-and-replace

This feature modifies the behavior of Pine's composer.  Setting this
feature causes Pine to offer the "^R Replace" subcommand, which
allows you to search and replace text strings in a message you are composing, 
inside the "^W Where is" command.  

To search and replace text, first enter the text to be replaced at the 
"Search: " prompt.  Then, rather than pressing Enter to just search for that
text, press ^R, which turns the prompt into 

Search (to replace): 

and then press Enter.  The cursor will highlight the first occurrence 
of the text string you entered, and the prompt will show: 

Replace "<your text string>" with : 

where <your text string> is what you entered at the previous prompt;
here, enter the replacement text.  To only replace the highlighted 
occurrence, simply press Enter now; to replace all occurrences in the 
message, press ^X (Repl All), then Enter.  You will then be asked to confirm 
each replacement.

The command ^R toggles between "Replace" and "Don't Replace"; its subcommand
^X toggles between "Replace All" and "Replace One."

If you previously searched for text in a message, it will be offered for 
reuse as part of the prompt, shown in [ ] brackets.

<End of help on this topic>
====== h_config_enable_view_attach =====
        FEATURE: enable-msg-view-attachments

This feature modifies the behavior of Pine's MESSAGE TEXT screen.
Setting this feature causes Pine to present attachments in boldface.
The first available attachment is displayed in inverse.  This is the
"selected" attachment.  Pressing RETURN will cause Pine to display
the selected attachment.  Use the arrow keys to change which of the
attachments displayed in boldface is the current selection.

Speaking of arrow keys, the Up and Down Arrows will select the next
and previous attachments if one is available on the screen for selection.
Otherwise, they will simply adjust the viewed text one line up or down.

Similarly, when selectable items are present in a message, the Ctrl-F
key can be used to select the next item in the message independent
of which portion of the viewed message is currently displayed. The
Ctrl-B key can be used to select the previous item in the same way.

<End of help on this topic>
====== h_config_enable_y_print =====
        FEATURE: enable-print-via-y-command

This feature modifies the behavior of Pine's Print command.

By default, Pine's print command is available by pressing the "%" key.  
(This command is a substantial change from Pine versions before 4.00 -- 
where the print command was "Y" -- based on numerous complaints about 
printing being invoked inadvertently, since Y also means "Yes.")  

This feature is supplied to mitigate any disruption or anxiety users 
might feel as a result of this change.  

Enabling this feature will cause Pine to recognize both the old
command, "Y" for Prynt, as well the new "%" method for invoking
printing.  Note, key menu labels are not changed as a result of
enabling this feature.

<End of help on this topic>
====== h_config_enable_lessthan_exit =====
        FEATURE: enable-exit-via-lessthan-command

If this feature is set, then on screens where there is an Exit command
but no < command, the < key will perform the same function as the Exit
command.

<End of help on this topic>
====== h_config_enable_view_url =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-msg-view-urls</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-msg-view-urls</H1>
This feature modifies the behavior of Pine's MESSAGE TEXT screen.
Setting this feature causes Pine to select possible URLs from the
displayed text and display them in boldface for selection.
<P>
The first available URL is displayed in inverse.  This is the
&quot;selected&quot; URL.  Pressing RETURN will cause Pine to display
the selected URL via either build-in means as with mailto:, imap:,
news:, and nntp:, or via an external application as defined
by the <A HREF="h_config_browser">&quot;url-viewer&quot;</A> 
variable.
<P>
Use the arrow keys to change which of the URLs displayed in boldface
is the current selection.
<P>
Speaking of arrow keys, the Up and Down Arrows will select the next
and previous URL if one is available on the screen for selection (unless 
you have set the feature 
<A HREF="h_config_enable_view_arrows">&quot;enable-msg-view-forced-arrows&quot;</A>).
Otherwise, they will simply adjust the viewed text one line up or down.
<P>
Similarly, when selectable items are present in a message, the Ctrl-F
key can be used to select the next item in the message independent
of which portion of the viewed message is currently displayed. The
Ctrl-B key can be used to select the previous item in the same way.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_enable_view_web_host =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-msg-view-web-hostnames</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-msg-view-web-hostnames</H1>

This feature modifies the behavior of Pine's MESSAGE TEXT screen.
Setting this feature causes Pine to select possible web hostnames
from the displayed text and display them in boldface for selection.  
This can be useful when you receive messages referencing World Wide Web 
sites without the use of complete URLs; for example, specifying only 
&quot;www.washington.edu/pine/&quot; (which will <B>not</B> become a 
selectable 
item by setting <A HREF="h_config_enable_view_url">&quot;enable-msg-view-urls&quot;</A>) 
rather than explicitly
&quot;http://www.washington.edu/pine/&quot;.  
<P>
The first available hostname is displayed in inverse.  This is the
&quot;selected&quot; hostname.  Pressing RETURN will cause Pine to display
the selected hostname via an external application as defined
by the <A HREF="h_config_browser">&quot;url-viewer&quot;</A> 
variable.
<P>
Use the arrow keys (unless you have set the feature 
<A HREF="h_config_enable_view_arrows">&quot;enable-msg-view-forced-arrows&quot;</A>) 
to change which of the hostnames displayed in
boldface is the current selection.
<P>
Similarly, when selectable web hostnames are present in a message, the Ctrl-F
key can be used to select the next web hostname in the message independent
of which portion of the viewed message is currently displayed. The
Ctrl-B key can be used to select the previous web hostnames in the same way.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_enable_view_addresses =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-msg-view-addresses</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-msg-view-addresses</H1>

This feature modifies the behavior of Pine's MESSAGE TEXT screen.
Setting this feature causes Pine to select possible email addresses
from the displayed text and display them in boldface for selection.  

<P>
The first available email address is displayed in inverse.  This is the
&quot;selected&quot; address.  Pressing RETURN will cause Pine to enter
the message composition screen with the To: field filled in with the
selected address.
<P>
Use the arrow keys (unless you have set the feature 
<A HREF="h_config_enable_view_arrows">&quot;enable-msg-view-forced-arrows&quot;</A>) 
to change which of the hostnames displayed in
boldface is the current selection.
<P>
Similarly, when selectable web hostnames are present in a message, the Ctrl-F
key can be used to select the next web hostname in the message independent
of which portion of the viewed message is currently displayed. The
Ctrl-B key can be used to select the previous web hostnames in the same way.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_enable_view_arrows =====
        FEATURE: enable-msg-view-forced-arrows

This feature modifies Up and Down arrow key behavior in Pine's
MESSAGE TEXT screen when selectable Attachments, URL's, or
web-hostnames are presented. Pine's usual behavior is to move to
the next or previous selectable item if currently displayed or
simply to adjust the screen view by one line.

Setting this feature causes the UP and Down arrow key to behave as
if no selectable items were present in the message.

Note, the Ctrl-F (next selectable item) and Ctrl-B (previous selectable
item) functionality is unchanged.

<End of help on this topic>
====== h_config_pass_control =====
        FEATURE: pass-control-characters-as-is

This feature controls how certain characters contained in messages are
displayed.  If set, all characters in a message will be sent to the
screen.  Normally, control characters are automatically suppressed in
order to avoid inadvertently changing terminal setup parameters.

<End of help on this topic>
====== h_config_fcc_on_bounce =====
        FEATURE: fcc-on-bounce

This feature controls an aspect of Pine's behavior when bouncing a
message. If set, normal FCC ("File Carbon Copy") processing will be
done, just as if you had composed a message to the address you are
bouncing to.  If not set, no FCC of the message will be saved. 

<End of help on this topic>
====== h_config_show_cursor =====
        FEATURE: show-cursor

This feature controls an aspect of Pine's displays.  If set, the system
cursor will move to convenient locations in the displays.  For example,
to the beginning of the status field of the highlighted index line, or
to the highlighted word after a successful WhereIs command.  It is intended
to draw your attention to an "interesting" spot on the screen.

<End of help on this topic>
====== h_config_single_list =====
        FEATURE: single-column-folder-list

This feature controls an aspect of Pine's FOLDER LIST screen.  If set,
the folders will be listed one per line instead of several per line
in the FOLDER LIST display.

<End of help on this topic>
====== h_config_vertical_list =====
        FEATURE: vertical-folder-list

This feature controls an aspect of Pine's FOLDER LIST screen.  If set,
the folders will be listed alphabetically down the columns rather
than across the columns as is the default.

<End of help on this topic>
====== h_config_verbose_post =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-verbose-smtp-posting</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-verbose-smtp-posting</H1>
This feature controls an aspect of Pine's message sending.  When enabled,
Pine will send a VERB (i.e., VERBose) command early in the posting process
intended to cause the SMTP server to provide a more detailed account of
the transaction.  This feature is typically only useful to system
administrators and other support personel as an aid in troublshooting
problems.
<P>
Note, this feature relies on a specific capability of the system's mail
transport agent or configured 
<A HREF="h_config_smtp_server">&quot;smtp-server&quot;</A>.  
It is possible that this
feature will cause problems for some tranport agents, and may result in
sending failure.  In addition, as the verbose output comes from the mail
transport agent, it is likely to vary from one system to another. 
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_auto_reply_to =====
        FEATURE: reply-always-uses-reply-to

This feature controls an aspect of Pine's Reply command.  If set, Pine
will not prompt when a message being replied to contains a "Reply-To:"
header value, but will simply use its value (as opposed to using the
"From:" field's value).

Note: Using the "Reply-To:" address is usually the preferred behavior,
however, some mailing list managers choose to place the list's address in
the "Reply-To:" field of any message sent out to the list.  In such
cases, this feature makes it all too easy for personal replies to be
inadvertently sent to the entire mail list, so be careful! 

<End of help on this topic>
====== h_config_del_skips_del =====
        FEATURE: delete-skips-deleted

This feature controls an aspect of Pine's Delete command.  If set, this
feature will cause the Delete command to advance past other messages that
are marked deleted.  In other words, pressing "D" will both mark the
current message deleted and advance to the next message that is not marked
deleted.

<End of help on this topic>
====== h_config_auto_expunge =====
<HTML>
<HEAD>
<TITLE>FEATURE: expunge-without-confirm</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: expunge-without-confirm</H1>
This features controls an aspect of Pine's eXpunge command.  If set, you
will <B>not</B> be prompted to confirm your intent before the expunge takes 
place.
Actually, this is only true for the INBOX folder and for folders in the
Incoming Folders collection. See the feature
<A HREF="h_config_full_auto_expunge">&quot;expunge-without-confirm-everywhere&quot;</A>.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_full_auto_expunge =====
<HTML>
<HEAD>
<TITLE>FEATURE: expunge-without-confirm-everywhere</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: expunge-without-confirm-everywhere</H1>
This features controls an aspect of Pine's eXpunge command.  If set, you
will <B>not</B> be prompted to confirm your intent before the expunge 
takes place.  This feature sets this behavior for all folders, unlike the
<A HREF="h_config_auto_expunge">&quot;expunge-without-confirm&quot;</A>
feature which works only for incoming folders.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_auto_read_msgs =====
<HTML>
<HEAD>
<TITLE>FEATURE: auto-move-read-msgs</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: auto-move-read-msgs</H1>
This feature controls an aspect of Pine's behavior upon quitting.  If set,
and the 
<A HREF="h_config_read_message_folder">&quot;read-message-folder&quot;</A>
option is also set, then Pine will
automatically transfer all read messages to the designated folder and mark
them as deleted in the INBOX.  Messages in the INBOX marked with an 
&quot;N&quot; (meaning New, or unseen) are not affected.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_auto_fcc_only =====
<HTML>
<HEAD>
<TITLE>FEATURE: fcc-only-without-confirm</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: fcc-only-without-confirm</H1>
This features controls an aspect of Pine's composer.
The only time this feature will be used is if you attempt to send mail
which has no recipients but does have an Fcc.
Normally, Pine will ask if you really mean to copy the message only to
the Fcc.
That is, it asks if you really meant to have no recipients.
If this feature is set, you
will <B>not</B> be prompted to confirm your intent to make only a copy
of a message with no recipients.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_no_fcc_attach =====
<HTML>
<HEAD>
<TITLE>FEATURE: fcc-without-attachments</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: fcc-without-attachments</H1>

This features controls the way FCC's (File Carbon Copies) are
made of the messages you send.

<P>
Normally, Pine saves an exact copy of your message as it was sent.
When this feature is enabled, the &quot;body&quot; of the message
you send (the text you type in the composer) is preserved in the 
copy as before, however all attachments are replaced with text
explaining what had been sent rather than the attachments themselves.

<P>
This feature also affects Pine's &quot;Send ?&quot; confirmation prompt
in that a new &quot;^F Fcc Attchmnts&quot; option becomes available which
allows you to interactively set whether or not attachments are saved
to the Fcc'd copy.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_read_in_newsrc_order =====
<HTML>
<HEAD>
<TITLE>FEATURE: news-read-in-newsrc-order</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: news-read-in-newsrc-order</H1>
This feature controls the order in which newsgroups will be presented.  If
set, they will be presented in the same order as they occur in your 
<!--chtml if pinemode="os_windows"-->
&quot;NEWSRC&quot;
<!--chtml else-->
&quot;.newsrc&quot;
<!--chtml endif-->
file (the default location of which can be changed with the 
<A HREF="h_config_newsrc_path">&quot;newsrc-path&quot;</A> option).  
<P>
If not set, the newsgroups will be presented in alphabetical order.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_post_wo_validation =====
        FEATURE: news-post-without-validation

This feature controls whether the NNTP server is queried as newsgroups
are entered for posting.  Validation over slow links (e.g. dialup using
SLIP or PPP) can cause delays.  Set this feature to eliminate such delays.

<End of help on this topic>
====== h_config_confirm_role =====
<HTML>
<HEAD>
<TITLE>FEATURE: confirm-role-even-for-default</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: confirm-role-even-for-default</H1>

If you have roles, when you reply or forward a message Pine
will search through your roles for one which matches the message.
Normally, if no matches are found you will be placed into the composer
with no opportunity to select a non-default role.
If this feature is set, then you will be asked to confirm the role
selection even in this case.
That is, the default role selected will be the default role (no role at
all) and you will have the opportunity to change that.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_news_cross_deletes =====
<HTML>
<HEAD>
<TITLE>FEATURE: news-deletes-across-groups</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: news-deletes-across-groups</H1>

This feature controls what Pine does when you delete a message in a
newsgroup that appears in more than one newsgroup.  Such a message
is sometimes termed a &quot;crossposting&quot; in that it was posted
across several newsgroups.

<P>
Pine's default behavior when you delete such a message is to remove
only the copy in the current newsgroup from view when you use the
&quot;Exclude&quot; command or the next time you visit the newsgroup.

<P>
Enabling this feature causes Pine to remove every occurrence of the
message from all newsgroups it appears in and to which you are
subscribed.

<P>
NOTE: As currently implemented, enabling this feature may increase the
time it takes the Expunge command and newsgroup closing to complete.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_select_wo_confirm =====
        FEATURE: select-without-confirm

This feature controls an aspect of Pine's Save, Export, and Goto commands.
These commands all take text input to specify the name of the folder or
file to be used, but allow you to press ^T for a list of possible names.
If set, the selected name will be used immediately, without further
opportunity to confirm or edit the name.

<End of help on this topic>
====== h_config_use_current_dir =====
<HTML>
<HEAD>
<TITLE>FEATURE: use-current-dir</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: use-current-dir</H1>

This feature controls an aspect of several commands. 
If set, your &quot;current working directory&quot; 
<!--chtml if pinemode="running"-->
(which, at least for your current Pine &quot;session,&quot; 
is &quot;<!--#echo var="CURRENT_DIR"-->&quot;) 
<!--chtml endif-->
will be used instead of your home directory 
<!--chtml if pinemode="running"-->
(which, in the present configuration of your system, is
 &quot;<!--#echo var="HOME_DIR"-->&quot;) 
<!--chtml endif-->
for all of the following operations:<UL>
    <LI> Export in the MESSAGE INDEX and MESSAGE TEXT screens
    <LI> Attachment Save in the MESSAGE TEXT and ATTACHMENT TEXT screens
    <LI> <!--chtml if pinemode="function_key"-->F4
         <!--chtml else-->Ctrl-R
         <!--chtml endif--> file inclusion in the COMPOSER
    <LI> <!--chtml if pinemode="function_key"-->F5
         <!--chtml else-->Ctrl-J
         <!--chtml endif--> file attachment in the COMPOSER
</UL>
<!--chtml if pinemode="os_windows"-->
<P>
If you are starting PC-Pine from a desktop icon or the Start menu, 
you can set the &quot;current drive&quot; 
by specifying it in the &quot;Start in:&quot; 
box found in the Shortcut tab of the Properties.  
<!--chtml endif-->
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_save_wont_delete =====
          FEATURE: save-will-not-delete

This feature controls one aspect of the Save command.  If set, Save will
not mark the message "deleted" (its default behavior) after it has been
copied to the designated folder.

<End of help on this topic>
====== h_config_save_advances =====
          FEATURE: save-will-advance

This feature controls one aspect of the Save command.  If set, Save will
(in addition to copying the current message to the designated folder) also
advance to the next message.

<End of help on this topic>
====== h_config_force_low_speed =====
          FEATURE: assume-slow-link

This feature affects Pine's display routines.  If set, the normal
inverse-video cursor (used to highlight the current item in a list) will be
replaced by an "arrow" cursor and other screen update optimizations for
low-speed links (e.g. 2400 bps dialup connections) will be activated.

<End of help on this topic>
====== h_config_show_delay_cue =====
          FEATURE: enable-mail-check-cue

If set, this feature will cause an asterisk to appear in the upper
left-hand corner of the screen whenever Pine checks for new mail, and two
asterisks whenever Pine saves (checkpoints) the state of the current
mailbox to disk.

<End of help on this topic>
====== h_config_auto_open_unread =====
<HTML>
<HEAD>
<TITLE>FEATURE: auto-open-next-unread</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: auto-open-next-unread</H1>

This feature controls the behavior of the TAB key when traversing folders
in the optional 
<A HREF="h_config_enable_incoming">&quot;incoming-folders&quot; collection</A> 
or in optional news-collections.
<P>
When the TAB (Next New) key is pressed, and there
are no more unseen messages in the current (incoming message or news)
folder, Pine will search the list of folders in the current collection for
one containing New or Recent (new since the last time the folder was
opened) messages.  Normally, when such a folder is found, Pine will ask
whether you wish to open the folder.  If this feature is set, Pine will
automatically open the folder without prompting.<P>

<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_auto_include_reply =====
         FEATURE: include-text-in-reply

This feature controls an aspect of Pine's Reply command.  Normally, Pine
will ask whether you wish to include the original message in your reply.
If this feature is set, the original message will be included in the reply
automatically, without prompting.

<End of help on this topic>
====== h_config_select_in_bold =====
<HTML>
<HEAD>
<TITLE>FEATURE: show-selected-in-boldface</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: show-selected-in-boldface</H1>

This feature controls an aspect of Pine's 
<A HREF="h_config_enable_agg_ops">&quot;aggregate operation&quot;</A>
commands; in
particular, the Select and WhereIs commands. Select and WhereIs (with the
^X subcommand) will search the current folder for messages meeting a
specified criteria, and &quot;tag&quot; the resulting messages with an 
&quot;X&quot; in the
first column of the applicable lines in the MESSAGE INDEX.  If this feature
is set, instead of using the &quot;X&quot; to denote a selected message, 
Pine will
attempt to display those index lines in boldface. Whether this is
preferable to the &quot;X&quot; will depend on personal taste and the type of
terminal being used.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_file_dir ======
<HTML>
<HEAD>
<TITLE>OPTION: file-directory</TITLE>
</HEAD>
<BODY>
<H1>OPTION: file-directory</H1>

This value affects the Composer's &quot;^J&nbsp;Attach&quot; command, 
the Attachment Index Screen's &quot;S&nbsp;Save&quot; command, and the
Message Index's &quot;E&nbsp;Export&quot; command.

<P>
Normally, when a filename is supplied that lacks a leading &quot;path&quot;
component, Pine assumes the file exists in the user's home directory.
Under Windows operating systems, this definition isn't always clear.  This 
feature allows you to explictly set where Pine should look for files
without a leading path.

<P>
NOTE: this feature's value is ignored if either 
<A HREF="h_config_use_current_dir">use-current-dir</A> feature
is set or the PINERC has a value for the &quot;operating-dir&quot; variable.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_folder_extension ======
        OPTION: folder-extension

Normally PC-Pine appends the extension "MTX" to all local (PC) folder
names and suppresses that extension when listing those folders.  By
setting this option, you override this behavior.  In particular, you may
set "folder-extension" to the "null string" which tells PC-Pine to
neither add nor hide-from-view *any* folder name extension.

The reason you might wish to override the MTX default is that recent
versions of PC-Pine have the ability to open (albeit READ-ONLY) normal
Unix mail folders. Since it might be inconvenient to rename all of them to
have an MTX extension, it is possible with this option to switch PC-Pine's
behavior so that such folders can be seen and accessed without changing
their names. However, doing this means that your existing PC-Pine local
folders will have apparently changed their names.  For example, if you had
a local folder named "FOO" it will now appear in the FOLDER LIST as
"FOO.MTX". If you wish to save additional messages to that folder, you
will need to enter the full name, "FOO.MTX" at the Save prompt.
Likewise for GOTO.

If you wish to permanently avoid having to deal with folder name extensions,
you will need to set this option to the null string by entering two double-
quote marks, and you will need to rename your existing local folders to
not have the MTX extension.  At the DOS prompt, this can be done in one 
command, once you have changed to your mail directory:  RENAME  *.MTX  *.

We don't know why you might wish to, but you could also use this option
to tell PC-Pine to use an extension other than MTX.  In this case, enter
the three characters you desire to use in lieu of "MTX".  Note that
your existing folders will need to be renamed to correspond to this new
extension.


<End of help on this topic>
====== h_config_disable_password_cmd =====
        FEATURE: disable-password-cmd

This feature is intended for use by system managers who wish to globally
disable Pine's password-changing command (Main/Setup/Password) at sites
where it is inappropriate.

<End of help on this topic>
====== h_config_disable_kblock_cmd =====
        FEATURE: disable-kblock-cmd

This feature is intended for use by system managers who wish to globally
disable the keyboard lock command (Main/KBlock).

<End of help on this topic>
====== h_config_quote_all_froms =====
        FEATURE: save-will-quote-leading-froms

This feature controls an aspect of the Save command (and also the way
outgoing messages are saved to an FCC folder).  If set, Pine will add
a leading ">" character in front of message lines beginning with "From" 
when they are saved to another folder, including lines syntactically
distinguishable from the type of message separator line commonly used on
Unix systems.

The default behavior is that a ">" will be prepended only to lines
beginning with "From " that might otherwise be confused with a message
separator line on Unix systems.  If pine is the only mail program you use,
this default is reasonable.  If another program you use has trouble
displaying a message with an unquoted "From " saved by Pine, you should
enable this feature.  This feature only applies to the common Unix mailbox
format that uses message separator lines beginning with "From ".  If
Pine has been configured to use a different mailbox format (possibly
incompatible with other mail programs), then this issue does not arise,
and the feature is irrelevant.

<End of help on this topic>
====== h_config_normal_fg =====
        OPTION: normal-foreground-color

Sets PC-Pine's foreground (the actual character) color.

<End of help on this topic>
====== h_config_normal_bg =====
        OPTION: normal-background-color

Sets PC-Pine's background (the area behind the character) color.

<End of help on this topic>
====== h_config_reverse_fg =====
        OPTION: reverse-foreground-color

Sets PC-Pine's foreground (the actual character) color for reverse video
characters.

<End of help on this topic>
====== h_config_reverse_bg =====
        OPTION: reverse-background-color

Sets PC-Pine's background (the area behind the character) color for
reverse video characters.

<End of help on this topic>
====== h_config_news_uses_recent ======
        FEATURE: news-approximates-new-status

This feature causes certain messages to be marked as "New" in the
MESSAGE INDEX of newsgroups.

When opening a newsgroup, Pine will consult your "newsrc" file and
determine the last message you have previously disposed of via the "D"
key.  If this feature is set, any subsequent messages will be shown in the
Index with an "N", and the first of these messages will be highlighted.
Although this is only an approximation of true "New" or "unseen"
status, it provides a useful cue to distinguish more-or-less recent
messages from those you have seen previously, but are not yet ready to
mark deleted.

Background: your "newsrc" file (used to store message status information
for newsgroups) is only capable of storing a single flag, and Pine uses
this to record whether or not you are "done with" a message, as
indicated by marking the message as "Deleted".  Unfortunately, this
means that Pine has no way to record exactly which messages you have
previously seen, so it normally does not show the "N" status flag for
any messages in a newsgroup. This feature enables a starting
*approximation* of seen/unseen status that may be useful.

<End of help on this topic>
====== h_config_suspend_spawns =====
<HTML>
<HEAD>
<TITLE>FEATURE: use-subshell-for-suspend</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: use-subshell-for-suspend</H1>

This feature affects Pine's behavior when process suspension is enabled
and then activated via the Ctrl-Z key.  Pine suspension allows one to
temporarily interact with the operating system command &quot;shell&quot; 
without
quitting Pine, and then subsequently resume the still-active Pine session.
<P>

When the <A HREF="h_config_can_suspend">&quot;enable-suspend&quot;</A> feature
is set and subsequently the Ctrl-Z key
is pressed, Pine will normally suspend itself and return temporary control
to Pine's parent shell process.  However, if this feature is set, Pine
will instead create an inferior subshell process.  This is useful when the
parent process is not intended to be used interactively.  Examples include
invoking Pine via the -e argument of the Unix &quot;xterm&quot; program, 
or via a menu system.<P>

Note that one typically resumes a suspended Pine by entering the Unix
&quot;fg&quot; command, but if this feature is set, it will be necessary to
enter the &quot;exit&quot; command instead.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_8bit_smtp =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-8bit-to-smtp-server</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-8bit-to-smtp-server</H1>
This feature affects Pine's behavior when sending mail.  Internet standards
require that all electronic mail messages traversing the global Internet
consist of 7bit ASCII characters unless a pair of cooperating mail 
transfer agents explicitly agree to allow 8bit messages.  In general, 
then, exchanging messages in non-ASCII characters requires MIME encoding.
<P>
However, there are now Internet standards that allow for unencoded 8bit
exchange of messages between cooperating systems.  Setting this feature
tells Pine to try to negotiate unencoded 8bit transmission during the
sending process.  Should the negotiation fail, Pine will fall back to its
ordinary encoding rules. 
<P>
Note, this feature relies on your system's mail transport agent or
configured <A HREF="h_config_smtp_server">&quot;smtp-server&quot;</A>
having the negotiation mechanism introduced in
&quot;Extended SMTP&quot; (ESMTP) and the specific extension called
&quot;8BITMIME&quot;. 
<P>
ESMTP allows for graceful migration to upgraded mail transfer agents, but
it is possible that this feature might cause problems for some servers. 
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_8bit_nntp =====
        FEATURE: enable-8bit-nntp-posting

This feature affects Pine's behavior when posting news.  

The Internet standard for exchanging USENET news messages (RFC-1036)
specifies that USENET messages should conform to Internet mail standards
and contain only 7bit characters, but much of the news transport software
in use today is capable of successfully sending messages containing 8bit
characters.  Hence, many people believe that it is appropriate to send 8bit
news messages without any MIME encoding.

Moreover, there is no Internet standard for explicitly negotiating 8bit
transfer, as there is for Internet email.  Therefore, Pine provides the
option of posting unencoded 8bit news messages, though not as the default.
Setting this feature will turn OFF Pine's MIME encoding of newsgroup
postings that contain 8bit characters. 

Note, articles may cross a path or pass through news transport software
that is unsafe or even hostile to 8bit characters.  At best this will only
cause the posting to become garbled.  The safest way to transmit 8bit
characters is to leave Pine's MIME encoding turned on, but recipients
who lack MIME-aware tools are often annoyed when they receive MIME-encoded 
messages.

<End of help on this topic>
====== h_config_tab_new_only =====
        FEATURE: tab-visits-next-new-message-only

This feature affects Pine's behavior when using the TAB key to move from
one message to the next.  Pine's usual behavior is to select the next
unread message or message flagged as "Important".

Setting this feature causes Pine to skip the messages flagged as important,
and select unread messages exclusively.  Tab behavior when there are no
new messages left to select remains unchanged.

<End of help on this topic>
====== h_config_quell_dead_letter =====
<HTML>
<HEAD>
<TITLE>FEATURE: quell-dead-letter-on-cancel</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: quell-dead-letter-on-cancel</H1>

This feature affects Pine's behavior when you cancel a message being
composed.  Pine's usual behavior is to write the canceled message to
a file named 
<!--chtml if pinemode="os_windows"-->
&quot;DEADLETR&quot;,
<!--chtml else-->
&quot;dead.letter&quot; in your home directory,
<!--chtml endif-->
overwriting any previous message. Under
some conditions (some routine), this can introduce a noticeable delay.
Setting this feature will cause Pine NOT to write canceled compositions
into the file.
<P>
NOTE: Enabling this feature means NO record of canceled messages is
maintained.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_quell_beeps =====
<HTML>
<HEAD>
<TITLE>FEATURE: quell-status-message-beeping</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: quell-status-message-beeping</H1>

This feature affects Pine's behavior when it displays status message
(e.g., Error complaints, New mail warnings, etc).  Setting this feature
will not affect the display of such messages, but will cause those that
emit a beep to become silent.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_quell_lock_failure_warnings =====
<HTML>
<HEAD>
<TITLE>FEATURE: quell-lock-failure-warnings</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: quell-lock-failure-warnings</H1>

This feature affects Pine's behavior when it encounters a problem
acquiring a mail folder lock.  Typically, a secondary file associated
with the mail folder being opened is created as part of the locking
process.  On some systems, such file creation has been administratively
precluded by the system configuration.
<P>
Pine issues a warning when such failures occur, which can become bothersome
if the system is configured to disallow such actions.  Setting this
feature causes Pine to remain silent when this part of lock creation fails.
<P>
WARNING: systems that have been configured in a way that precludes locking
introduce some risk of mail folder corruption when more than one program
attempts to modify the mail folder.  This is most likely to occur to one's
INBOX or other incoming message folder. 
<P>
See also <A HREF="h_info_on_locking">&quot;What Systems Managers Need to Know about Pine File Locking&quot;</A>.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_quell_folder_internal_msg ======
<HTML>
<HEAD>
<TITLE>FEATURE: quell-folder-internal-msg</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: quell-folder-internal-msg</H1>
This feature determines whether or not Pine will create 
&quot;pseudo messages&quot; in folders that are in standard Unix or 
MMDF format. <P> 

Pine will normally create these pseudo messages when they are not already
present in a standard Unix or MMDF folder.  Their purpose is to record
certain mailbox state data needed for correct IMAP and POP server
operation, and also for Pine to be able to mark messages as Answered when
the Reply has been postponed.<P>

Sites which do not use IMAP/POP for remote mail access, and which need to
support mail tools that are adversely affected by the presence of the
pseudo-messages (e.g. some mail notification tools) may enable this
feature to tell Pine not to create them.  Note that Pine's 
&quot;Answered&quot; flag
capability will be adversely affected if this is done.<P>

Note too that, even if this feature is enabled, Pine will not remove
pseudo-messages when it encounters them (e.g. those created by UW's imapd
or ipopd servers.) This feature has no effect on folders that are not in
standard Unix or MMDF format, as pseudo-messages are not needed in the
other formats to record mailbox state information.
<P><UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL>
<P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_quell_empty_dirs ======
<HTML>
<HEAD>
<TITLE>FEATURE: quell-empty-directories</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: quell-empty-directories</H1>

This feature causes Pine to remove from the display any directories
that do not contain at least one file or directory.  This can be useful
to prevent overly cluttered folder lists when a collection is stored on
a server that treats all names as both a folder and a directory.

<P>
Note, enabling this feature can cause surprising behavior!  For example,
you can still use Add to create a directory, but unless you immediately
enter that directory and create a folder, that newly created directory
may not be displayed next time you enter the folder list.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_no_part_fetch =====
<HTML>
<HEAD>
<TITLE>FEATURE: quell-partial-fetching</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: quell-partial-fetching</H1>

This feature affects the way Pine interacts with IMAP 4rev1 mail servers.
By default, when a large message or attachment is viewed or saved, Pine
asks the server for message data in segments.  This allows the command 
that caused the request to be interrupted.

<P>
Testing has shown that, while extremely rare, it is possible for such
requests to cause some servers distress.  If you're having trouble
viewing or saving large messages, then you might try listing this feature
in your pinerc's feature list.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_change_from =====
<HTML>
<HEAD>
<TITLE>FEATURE: allow-changing-from</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: allow-changing-from</H1>

This feature affects Pine's handling of the &quot;From:&quot; header field
in the "<A HREF="h_config_custom_hdrs">Customized-Headers</A>" configuration
option.

<P>
By default, Pine restricts the use of this field in order to minimize the
risk of misconfiguration (e.g., sending mail that can't be replied to).
When this feature is added to your pinerc's feature list, the field,
when configured, becomes editable in the composer.

<P>
Note that many sites restrict the use of this feature in order to reduce the chance
of falsified addresses and misdirected mail.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_tcap_wins =====
<HTML>
<HEAD>
<TITLE>FEATURE: termdef-takes-precedence</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: termdef-takes-precedence</H1>

This feature may affect Pine's low-level input routines.  Termcap (or
terminfo, depending on how your copy of Pine was compiled and linked)
is the name of the database which describes terminal capabilities.  In
particular, it describes the sequences of characters that various keys
will emit.

<P>
An example would be the Up Arrow key on the keyboard.  Up
Arrow is not a distinct character on most Unix systems.  When you press
the Up Arrow key a short sequence of characters are produced.  This
sequence is supposed to be described in the termcap database by the
&quot;ku&quot; capability (or by the &quot;kcuu1&quot; capability if you
are using terminfo instead of termcap).

<P>
By default, Pine defines some terminal
escape sequences that are commonly used.  For example, the sequence
&quot;ESC&nbsp;O&nbsp;A&quot; is recognized as an Up Arrow key.  The sequence
&quot;ESC&nbsp;[&nbsp;A&quot;
is also recognized as an Up Arrow key.  These are chosen because common
terminals like VT100's or ANSI standard terminals produce these
sequences when you press the Up Arrow key.

<P>
If your system's termcap
(terminfo) database assigns some other function to the sequence
&quot;ESC&nbsp;O&nbsp;A&quot;
it is usually ignored by Pine.  Also, if your termcap (terminfo)
database assigns a sequence which doesn't begin with an escape
character (<SAMP>ESC</SAMP>) it is usually ignored by Pine.
This usually works fine
because most terminals emit the escape sequences that Pine has defined
by default.  We have also found that it is usually better to have these
defaults take precedence over the definitions contained in the database
because the defaults are more likely to be correct than the database.

<P>
There are some terminals where this breaks down.  If you want Pine to
believe the definitions given in your termcap (terminfo) database in
preference to the defaults the Pine itself sets up, then you may turn
this feature on.  Then, sequences of characters which are defined in
both termcap (terminfo) and in Pine's set of defaults will be
interpreted the way that termcap (terminfo) says they should be
interpreted.  Also, if your terminal capabilities database assigns a
sequence which doesn't begin with escape, it will not be ignored.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_cruise_mode =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-cruise-mode</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-cruise-mode</H1>

This feature affects Pine's behavior when you hit the
&quot;Space&nbsp;Bar&quot; at
the end of a displayed message.  Typically, Pine complains that the end
of the text has already been reached.  Setting this feature causes such
keystrokes to be interpreted as if the &quot;Tab&quot; key had been hit, thus
taking you to the next &quot;interesting&quot; message,
or scanning ahead to the 
next incoming folder with &quot;interesting&quot; messages.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_cruise_mode_delete =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-cruise-mode-delete</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-cruise-mode-delete</H1>

This feature modifies the behavior of Pine's 
<A HREF="h_config_cruise_mode">&quot;enable-cruise-mode&quot;</A> feature.  
Setting this feature causes Pine to implicitly delete read
messages when it moves on to display the next &quot;interesting&quot; message.
<P>
NOTE: Beware when enabling this feature AND the 
<A HREF="h_config_auto_expunge">&quot;expunge-without-confirm&quot;</A> 
feature.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_allow_goto =====
        FEATURE: enable-goto-in-file-browser

This feature modifies the behavior of Pine's file browser.  Setting this
feature causes Pine to offer the "G Goto" command in the file browser.

This command allows you to explicitly set the displayed directory.  Pine's
default behavior requires you to visit each intermediate directory when moving
between two distant directories.

<End of help on this topic>
====== h_config_add_ldap =====
<HTML>
<HEAD>
<TITLE>FEATURE: ldap-result-to-addrbook-add</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: ldap-result-to-addrbook-add</H1>

If both the Directory option
<A HREF="h_config_ldap_opts_impl">&quot;use-implicitly-from-composer&quot;</A>  
and this feature are set,
then when an implicit directory lookup is done from the
composer you will automatically be prompted to add the result of the
directory lookup to your address book.
<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_lame_list_mode =====
<HTML>
<HEAD>
<TITLE>FEATURE: enable-lame-list-mode</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: enable-lame-list-mode</H1>

This feature modifies the method Pine uses to ask your IMAP
server for folder names to display in the the FOLDER LIST screen.
It is intended to compensate for a small set of IMAP servers that
are programmed to ignore a part of the request, and thus respond
to Pine's query with nonsensical results.
<P>

If you find that Pine is erroneously displaying blank folder lists,
try enabling this feature.
<P>

NOTE: Enabling this feature has consequences for the Goto and Save
commands.  Many servers allow access to folders outside the area
reserved for your personal folders via some reserved character,
typically '#' (sharp), '~' (tilde) or '/' (slash).  This mechanism
allows, at the Goto and Save prompts, quick access to folders
outside your personal folder collection without requiring a specific
collection definition.  This behavior will generally not be available
when this feature is enabled.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_textplain_int =====
<HTML>
<HEAD>
<TITLE>FEATURE: show-plain-text-internally</TITLE>
</HEAD>
<BODY>
<H1>FEATURE: show-plain-text-internally</H1>

This feature modifies the method Pine uses to display Text/Plain
MIME attachments from the Attachment Index screen.  Normally, the
&quot;View&quot; command searches for any externally defined (usually
via the
&quot;<A HREF="h_config_mailcap_path">Mailcap</A>&quot; file) viewer,
and displays the selected text within that viewer.

<P>
Enabling this feature causes Pine to ignore any external viewer
settings and always display text with Pine's internal viewer.

<P>
<UL>   
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
</UL><P>
&lt;End of help on this topic&gt;
</BODY>
</HTML>
====== h_config_role_undo =====
Yes, remember changes and exit back to list of roles; No, discard changes
made in this screen; ^C, cancel exit and stay in this config screen.
====== h_config_undo =====
Yes, save changes and exit; No, exit without saving any changes made since
entering this CONFIGURATION screen; ^C, cancel exit and stay in config screen.
====== h_os_index_whereis =====
Enter ^V or ^Y to go immediately to the last or first message in the index.
Or, enter the match string followed by RETURN.
====== h_os_index_whereis_agg =====
Enter ^V or ^Y to go immediately to the last or first message in the index,
Or, enter the match string followed by RETURN (or ^X to select all matches).
=========== h_oe_add_full ==================
Type the full name of the person being added and press the RETURN key.
Press ^C to cancel addition.
=========== h_oe_add_nick ==================
Type a short nickname and press RETURN.  A nickname is a short easy-to-
remember word, name or initials like "joe", or "wcfields."  ^C to cancel.
========== h_oe_add_addr ================
Type the e-mail address and press RETURN.
Press ^C to cancel addition.
========== h_oe_crlst_full ==============
Type a long name or description for the list that you are creating and
press RETURN.  Press ^C to cancel creation of list.
=========== h_oe_crlst_nick =============
Type a nickname (short, easy-to-remember name or single word) for the list
you are creating and press RETURN.  Press ^C to cancel.
========== h_oe_crlst_addr ==============
Type an e-mail address, or a nickname already in the address book that you
want to be part of this list and press RETURN.
========== h_oe_adlst_addr =============
Type an e-mail address or a nickname already in the address book that you
want to add to this list and press RETURN.
========== h_oe_editab_nick ============
Change the nickname using the arrow keys and delete key.  Press RETURN
when done.  Press ^C to cancel editing and leave the nickname as it was.
========== h_oe_editab_full ============
Change the full name using the arrow keys and delete key.  Press RETURN
when done.  Press ^C to cancel editing and leave the full name as it was.
========== h_oe_editab_addr ============
Change the address using the arrow keys and delete key.  Press RETURN
when done.  Press ^C to cancel editing and leave the address as it was.
========== h_oe_editab_fcc ============
Change the fcc using the arrow keys and delete key.  Press RETURN when
done.  Press ^C to cancel editing and leave the fcc as it was.
========== h_oe_editab_comment ============
Change the comment field using the arrow keys and delete key.  Press RETURN
when done.  Press ^C to cancel editing and leave the comment as it was.
====== h_ab_forward =====
Yes, expand nicknames and qualify local names with your current domain name;
No, leave nicknames and local names as is;  ^C, cancel.
========== h_ab_export ==========
Type the name of a file to write the addresses into and
press RETURN.  You may also specify an absolute path.  Use ^C to cancel.
========== h_ab_edit_a_field ==========
Edit any of the fields of the currently selected entry by typing one of the
letters at the bottom of the screen.  Press ^C to cancel edit.
====== h_ab_del_data_revert =====
Press B to completely delete addrbook and revert to default, C to delete config
and revert while leaving data, or D to only delete data (make it empty).
====== h_ab_del_data_modify =====
Press B to completely delete addrbook, C to delete configuration while leaving
data, or D to delete data (make it empty) but leave config. ^C to cancel.
====== h_ab_del_config_modify =====
Yes, remove this address book from my configuration.
No, make no changes now.
====== h_ab_del_config_revert =====
Yes, remove this address book from my config and revert to default.
No, make no changes now.
====== h_ab_del_default =====
Yes, remove this default address book from my configuration.
No, make no changes now.
====== h_ab_really_delete =====
Yes, delete the actual contents of the address book, not just the 
configuration.  No, don't delete the data after all, cancel and start over.
====== h_ab_del_ignore =====
Press I to ignore all the default address books for this category.  Press R to
remove this one address book and add the others to your personal list.
====== h_ab_del_dir_ignore =====
Press I to ignore all the default directory servers for this category.
Press R to remove this one server and add the others to your personal list.
====== h_ab_copy_dups =====
Yes, overwrite the existing entry.
No, skip duplicates but save the rest. Press ^C to cancel.
====== h_ab_export_vcard =====
A, export list of addresses to file.
V, export as much vCard information as possible to file. ^C to cancel.
====== h_ab_text_or_vcard =====
Text, start composer with displayed text already included.
VCard, start composer with address book entry attached as a vCard. ^C cancels.
====== h_ab_backup_or_ldap =====
Backup, copy email address from entry and allow editing of it.
LDAP, copy LDAP search criteria, do not allow editing of it. ^C cancels.
====== h_ldap_text_or_vcard =====
Text: export displayed text for selected entry. Address: export only the
email address. VCard: export entry in vCard format. ^C cancels.
====== h_ab_save_exp =====
Save, save entry or entries to an address book.
Export, save to file outside of pine. ^C cancels save.
====== h_ab_add =====
A, add a brand new entry to this address book.
E, edit the entry which is currently highlighted. ^C to cancel.
====== h_ab_shuf =====
U, swap order of highlighted address book and the one above it.
D, swap order of highlighted address book and the one below it. ^C to cancel.
====== h_ab_shuf_up =====
U, swap order of highlighted address book and the one above it.
Press ^C to cancel.
====== h_ab_shuf_down =====
D, swap order of highlighted address book and the one below it.
Press ^C to cancel.
====== h_role_shuf =====
U, swap order of highlighted rule and the one above it.
D, swap order of highlighted rule and the one below it. ^C to cancel.
====== h_role_shuf_up =====
U, swap order of highlighted rule and the one above it.
Press ^C to cancel.
====== h_role_shuf_down =====
D, swap order of highlighted rule and the one below it.
Press ^C to cancel.
====== h_dir_shuf =====
U, swap order of highlighted directory and the one above it.
D, swap order of highlighted directory and the one below it. ^C to cancel.
====== h_dir_shuf_up =====
U, swap order of highlighted directory and the one above it.
Press ^C to cancel.
====== h_dir_shuf_down =====
D, swap order of highlighted directory and the one below it.
Press ^C to cancel.
========== h_oe_editab_al ============
Change the address using the arrow keys and delete key.  Press RETURN
when done.  Press ^C to cancel editing and leave the address as it was.
========== h_dir_comp_search ===============
Type a string to look for just like you would in the composer. Your configured
rules for the servers with the implicit flag set will be used.
========== h_oe_searchab ===============
Type the word or name you want to search for and press RETURN.  If you press
RETURN without entering anything the word in [] will be searched for.
========== h_oe_save ==========
Type the name of the folder you want to save the message in and press RETURN.
Press ^T to get a list of your folders.  Press ^C to cancel saving this mail.
========== h_oe_chooseabook ==========
Choose the address book you want to save the new entry in.
Use ^N or ^P to change address books.  ^C to cancel.
========== h_oe_takeaddr ==========
Edit the e-mail address using the arrow and delete keys.  Press RETURN
when done.  Press ^C to cancel adding this entry to the address book.
========== h_oe_take_replace ==========
Press R to replace the old entry with this new data.  You will still have
another chance to cancel.  N to enter another nickname.  ^C to cancel now.
========== h_oe_take_replace_or_add ==========
Press R to replace the old entry.  Press A to add the selected addresses to
the old existing list.  N to enter another nickname. ^C to cancel now.
========== h_oe_takename ==========
Edit the full name to be correct using the arrow and delete keys.  Press RETURN
when done.  Press ^C to cancel adding this entry to the address book.
========== h_oe_takenick ==========
Type a nickname (short easy-to-remember name, initials or single word) for this
entry in the address book and press RETURN.  Press ^C to cancel addition.
========== h_oe_jump ==========
Type the number of the message number you want to jump to and press
RETURN.  Press ^C if you want to cancel jumping to another message.
========== h_oe_broach ==========
Type the name of the folder you want to open and press RETURN.  Press ^P/^N
to go to the previous/next collections in the list.  Press ^C to cancel goto.
========== h_oe_foldsearch ==========
Type the text you want to search for in foldernames and press RETURN.  If you
press RETURN without entering anything, any text in [] will be searched for.
========== h_oe_foldadd ==========
Type the name of the folder you want to add and press RETURN.  Press ^C to
cancel adding a new folder.
========== h_oe_foldrename ==========
Change the old name of the folder to the new name using the arrow and
delete keys and press RETURN.  Press ^C to cancel rename.
========== h_oe_login ==========
Enter your login name for the host you are opening the mailbox on.  Just press
RETURN to use your login from this host as is, or edit it with delete key.
========== h_oe_passwd ==========
Type your password for the host and login shown as part of the prompt.
Press ^C to cancel opening folder.
========== h_oe_choosep ==========
Enter the number associated with the printer you want to select.  Press ^C to
cancel the printer selection.  The current selection is highlighted.
========== h_oe_customp ==========
Type the name of the Unix print command and press RETURN.  Press ^C to
cancel the printer selection.
========== h_oe_searchview ==========
Type the word or name you want to search for and press RETURN.  If you press
RETURN without entering anything the word in [] will be searched for.
========== h_oe_keylock ==========
The keyboard is in use and locked by another user.  Only that user can
unlock this keyboard by typing the password.
========== h_oe_export ==========
Type the name of a file to write into and press RETURN.
You may also specify an absolute path.  Use ^C to cancel.
========== h_wt_expire ==========
At the beginning of each month Pine offers to rename your current sent-mail
folder to one named for the month so you have a sent-mail folder for each month
========== h_wt_delete_old ==========
It is the beginning of the month, and we need to conserve disk
space.  Please delete any sent-mail that you do not need.
========== h_select_sort ==========
Select the order for sorting the index by typing the capitalized letter.
Arrival is by arrival in your mailbox; Date is by time/day message was sent.
========== h_mini_setup ==========
Select one of the setup tasks by typing the capitalized letter.
========== h_sticky_personal_name ==========
Type in your name as you want it to appear on outgoing email.  This entry
will be saved into your Pine configuration file.
========== h_sticky_inbox ============
INBOX syntax is usually {complete.machine.name}INBOX
This entry will be saved in your Pine configuration file.
========== h_sticky_smtp ============
The name of the computer on your campus which relays your outgoing email
to the Internet.  This entry will be saved in your Pine configuration file.
========== h_sticky_user_id ==========
The username or login-id part of your email address.  This entry will be
saved in your Pine configuration file.
========== h_sticky_domain ==========
The domain part of your email address, NOT the name of your PC.  This
entry will be saved in your Pine configuration file.
========== h_bounce =========
Enter the address or nickname of the intended recipient.  Pine will resend
the message, which will retain the original author's From: address.
========== h_incoming_add_folder_host =========
Enter RETURN if the folder is on the machine where Pine is running;
otherwise enter the host name of the mail server, or ^X if same as INBOX.
========== h_incoming_add_folder_name =========
Enter the name of the desired folder. Pine will attempt to create this
folder on the previously specified mail server.
========== h_incoming_add_folder_nickname =========
Enter an (optional) nickname that will be used in lieu of the actual
host and folder names in the FOLDER LIST display.
========== h_anon_forward ==========
Enter the address of your intended recipient, or ^C to cancel.
Example: jsmith@somewhere.edu
========== h_news_subscribe ==========
Enter the name of the newsgroup to which you wish to subscribe,
or ^C to cancel.  Example: comp.mail.pine
========== h_pipe_msg ==========
Enter the name of the Unix command to which you wish to send this
message, or ^C to cancel.
========== h_pipe_attach ==========
Enter the name of the Unix command to which you wish to send this
attachment, or ^C to cancel.
========== h_select_by_num ==========
Enter a list of numbers (or number range(s)), or ^C to cancel.  The messages
corresponding to the numbers will be selected.  Example: 2-5,7-9,11,19
========== h_select_txt_from ==========
Messages with From: headers containing the entered string will be selected.
^C to cancel. ^R enters current msg From: address.  ^T enters To: address.
========== h_select_txt_to ==========
Messages with To: headers containing the entered string will be selected.
^C to cancel. ^R enters current msg From: address.  ^T enters To: address.
========== h_select_txt_cc ==========
Messages with Cc: headers containing the entered string will be selected.
^C to cancel. ^R enters current msg From: address.  ^T enters To: address.
========== h_select_txt_subj ==========
Messages with Subject: headers containing the entered string will be selected.
^C to cancel.  ^X enters Subject: line of current message.
========== h_select_txt_all ==========
All messages containing the entered string will be selected.  Headers,
but not encoded attachments, will be compared.  Enter ^C to cancel.
========== h_select_date ==========
If typed, date must be in DD-MMM-YYYY format, where MMM is three-letter 
abbreviation of month. ^P/^N also changes date. ^X enters date of current msg.
========== h_attach_index_whereis ==========
Enter some text that appears in the Attachment Index entry for the desired
attachment.  The first attachment containing that text will be highlighted.
========== h_kb_lock ==========
Keystrokes entered here (up to a RETURN) comprise a password that must
be entered again later in order to unlock the keyboard.
========== h_config_whereis ==========
To move quickly to a particular line, enter a search string or
^C to cancel.
========== h_config_add ==========
Enter desired value; use normal editing keys to modify (e.g. ^K, ^D).  Just
pressing RETURN sets the Empty Value (this turns off any global default).
========== h_config_print_opt_choice ==========
You may edit either the initialization string (characters printed before
printing starts) or the trailer string.  Choose one or ^C to cancel.
========== h_config_print_init ==========
Enter a C-style string for this.  You may use common backslash escapes like
\\n for newline, \\ooo for octal character, and \\xhh for hex character.
========== h_config_change ==========
Edit the existing value using arrow keys, ^K to delete entire entry, ^D to
delete current (highlighted) character, etc.  Enter ^C to cancel change.
========== h_config_replace_add ==========
Replace ignores the current default, Add places the current default in your
editing buffer as if you had typed it in.
========== h_config_insert_after ==========
Enter a nickname for this print command.  (InsertBefore puts the new item
before the current line, InsertAfter puts it after the current line.)
========== h_config_print_cmd ==========
Enter command to be executed for the printer.  Use normal editing keys
to modify, ^C to cancel, carriage return to accept current value.
========== h_config_role_del ==========
Answering Yes will remove this role rule completely from your roles list.
========== h_config_role_addfile ==========
Type the name of a file to add to your roles configuration. You don't need to
use a file, you may add roles directly (with Add) without using a file.
========== h_config_role_delfile ==========
Answering Yes will remove this role file completely from your roles list.
The roles data file itself will not be removed.
========== h_config_print_del ==========
Answering Yes will remove this printer completely from your printer list.
========== h_config_print_name_cmd ==========
You may edit the Nickname of this printer, the Command to be executed when
printing, or change the Options associated with this printer.
========== h_send_fcc_only ==========
Yes, copy message to Fcc only and send to NO recipients.
No, return to composer.
========== h_send_prompt ==========
Yes, send the message.
No or ^C, return to composer.
========== h_send_prompt_dsn ==========
Yes, send the message.  No or ^C, return to composer.
What's DSNOpts? See enable-delivery-status-notification in config screen.
========== h_role_confirm ==========
Yes accepts current role. ^N and ^P toggle to next or previous role (or to
the default role). No or ^C will Cancel the message.
========== h_custom_print ==========
Enter a Unix command that accepts its data on standard input.
Pine will display any information the command sends to standard output.


