Previous | Next | Contents | Index |
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 thebugs-address
andbugs-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 asLocal 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 themimetype-search-path
option in their Pine resource file.
7.7.3.1 Precedence of Configuration Settings
There are potentially four sources of configuration settings which are
shown below in decreasing order of precedence:
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.
Previous | Next | Contents | Index |