PMDF Pine uses PMDF extensively. PMDF must be installed and
    configured on the system for Pine to function. Pine uses PMDF
    to send mail, to parse addresses, and to save copies of messages
    you have sent, if the Pine DEFAULT-FCC option is set. Once PMDF
    is configured and installed on a system, PMDF Pine is usually
    ready for use, although see under PMDF Pine System_configuration
    UCX Emulation and PMDF Pine System_configuration Subprocess Quota
    for descriptions of two installation issues to check, and see
    under PMDF Pine System_configuration Configuration Files for a
    description of tailoring the Pine environment on a system wide
    basis.

    In particular, note that Pine does not, by default, use IMAP
    to talk to your local system, so it is not necessary to have
    an IMAP server running on your system just to use Pine. (Only
    if a user were to specifically request that Pine treat the
    local system as if it were instead a remote system with an IMAP
    server, by specifying the IMAP-HOST field when accessing a folder
    collection, would PMDF Pine attempt to make an IMAP connection to
    the local system.)

    Pine is installed by PMDF with the privileges SYSPRV and CMKRNL.
    Without those privileges, users can not send mail, although they
    can still read mail.

1  –  UCX Emulation

    UCX$IPC_SHR is an executive-mode logical name pointing to a
    shareable image supplied by your TCP/IP vendor. If this logical
    is not defined, then either TCP/IP is not installed, or, in the
    case of a package other than DEC's TCP/IP Services for OpenVMS
    (a.k.a. UCX), UCX emulation was not installed when the package
    was installed. In order to use the TCP/IP functionality of
    PMDF Pine, this logical must be defined and be pointing to the
    appropriate image for your TCP/IP package. Moreover, the image
    must be installed as a known image,

    $ INSTALL UCX$IPC_SHR /OPEN/SHARED

    If you are running Pine on a system without any TCP/IP software,
    a dummy shareable image PMDF_EXE:UCX_DUMMY.EXE is provided with
    PMDF. Your system manager should define a system-wide, executive-
    mode logical named UCX$IPC_SHR which points to it and then
    install it:

    $ DEFINE/SYSTEM/EXEC UCX$IPC_SHR PMDF_EXE:UCX_DUMMY.EXE
    $ INSTALL UCX$IPC_SHR /OPEN/SHARED

                                   NOTE

       If you install any TCP/IP package later, remember to
       deassign the logical name or you won't have a functional
       TCP/IP.

    The definition of the logical and installation of the image
    should be made part of the system startup procedure. Note that
    the installation of the image can be effected through the site-
    supplied PMDF_COM:SITEIMAGE.DAT file which uses the same format
    as the Process-supplied PMDF_COM:PMDFIMAGE.DAT file.

2  –  Subprocess Quota

    Pine uses subprocesses to perform several of its tasks. As such,
    users without subprocess quota cannot do any of the following:

    o  use a customized printing command,

    o  view image or video attachments,

    o  use the spell checker, or

    o  use an alternate editor.

    A side effect of using subprocesses in Pine when you have a
    remote IMAP connection is that the connection might timeout while
    waiting for a subprocess to complete. This is especially likely
    when using an alternate editor to compose a message.

3  –  Configuration Files

    A system manager can tailor Pine's environment on a per system
    basis by the use of files described below. These files should all
    be world readable.

 PMDF_TABLE:PINE.CONF

    This file is shipped with PMDF and contains a default system-wide
    configuration for Pine. A new version is shipped with every PMDF
    release, so you should keep a copy of your customizations. This
    default configuration provides for one folder collection with the
    default mail file on the local system.

 PMDF_TABLE:PINE.CONF-FIXED

    You can create this Pine resource file and place in it options
    which you do not want users to be able to change or override.
    This file, as supplied with PMDF, initially contains the same
    information as hardcoded in the program for the BUGS-ADDRESS and
    BUGS-FULLNAME options with the local Postmaster being the one to
    receive the bug reports. You can change it to a different address
    if necessary, but we suggest you direct it to a local support
    address.

 PMDF_TABLE:PINE.INFO

    When this file exists, the information contained in it is
    presented to the user as LOCAL SUPPORT CONTACTS from the main
    menu's help screen.

 PMDF_TABLE:MIME.TYPES

    This file provides a basic set of file extension to MIME type
    mappings. Users can supplement or override these defaults with
    their own choices in their own file, via the MIMETYPE-SEARCH-PATH
    option in their Pine resource file.

3.1  –  Precedence of Settings

    There are potentially four sources of configuration settings
    which are shown below in decreasing order of precedence:

    1. Unchangeable, system-wide settings from the PMDF_
       TABLE:PINE.CONF-FIXED file.

    2. Per-user settings from the user's PMDF_INIT:PINE.PINERC file.

    3. System-wide settings from the PMDF_TABLE:PINE.CONF file.

    4. Default Pine values.

    One exception to the above precedence scheme is the FEATURE-LIST
    option which is cumulative. In order to turn off a feature, you
    have to negate it by prepending NO- in front of an individual
    feature.