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.
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.