./pine/osdep/os-xxx.hwhere "xxx" is the 3-letter code for your platform. You can give the command
build helpto see the list of ports incorporated into Pine and their associated 3-letter codes. The file
./pine/makefile.xxxis where you would set your compiler options. By default, Pine will be compiled with debugging on, optimization and profile off. Note that if you compile with DEBUG off, then Pine will not create its normal debug files, no matter how the debug-level and debug command line flag are set.
Most of Pine's behaviors are set in the file
./pine/osdep/os-xxx.h, which includes comments that explain
each setting. Some of these can only be set when you compile. Others,
however, can be overridden by command-line flags to Pine or settings in
Pine's user or system configuration files. Some of the options which can
be set when compiling:
/usr/lib/sendmail -oi -oem -t.
There are a couple of more obscure options which are in the source code because a few people have asked for them or because we changed our minds about them being a good idea in general.
From's at the beginning of lines don't end up being escaped by >'s. Most people seem to dislike the Q-P encoding more than the > escapes so this is off by default. Once everyone has MIME mail readers, we'll turn this on by default.
./pico/os_unix.h.Whatever is set will effect the behavior of the Pico stand-alone program as well as the composer within Pine.
ftp.cac.washington.eduin the directory
build helpto see the list of ports incorporated into Pine. What you need is the three letter code for the platform. Some examples are
nxtfor the Next operating system and
ultfor Ultrix. If your platform is not in the list of ports, then you might have some work ahead of you. First, check the file
doc/pine-portsto see if there are others working on a port for your platform or to see if the port is included in the "contrib" section of the source code. Ports in the
contribdirectory were contributed by Pine administrators from around the world, but the Pine development team has not been able to test the code. If Pine has not yet been ported to your platform at all, read the section on Porting Pine in this document.
lsyou should see the following files and directories (or something close to it):
README build doc makefile pine bin contrib imap pico
build clean. This should take only a few seconds to run.
buildxxx where xxx is the three letter code you picked in step 1. The compiler should grind away for a few minutes.
bindirectory contains a link to each program compiled. You can just copy them out of
binor try them from there.
/usr/local/binthough sometimes they are placed in
/usr/bin. All the help text is compiled into Pine so there are no required auxiliary files.
There are, however, three optional auxiliary files:
/usr/local/lib/pine.conf.fixed. The file
pine.info contains text on how to get further help on the
local system. It is presented as the first page of the help text for the
main menu and should probably refer to the local help desk or the system
administrator. If this file doesn't exist a generic version which
suggests ``talking to the computer support staff at your site'' is shown.
pine.conf is used to set system-wide default
configurations for Pine. The file
pine.conf.fixed is also
used to set system-wide default configurations for Pine. The difference
between these two files is that configuration variables set in the
pine.conf.fixed file may not normally be over-ridden by a
user. See the section on Pine Configuration later in this document for
details about the
[pctcp ifcust 0] ip-address=xx.xx.xx.xx
WATTCP.CFGincluded in the Pine distribution. The file includes 5 configuration settings--IP-address, gateway, netmask, nameserver(s) and domainslist. If you have a network configuration file for NCSA Telnet then
WATTCP.CFGis just a pared down version of the
CONFIG.TELfile you already made. Take a look at
CONFIG.TELto find the correct settings for
WATTCP.CFG. Once the configuration file is made, the DOS environment variable
WATTCP.CFGneeds to point at it. For example:
In addition to networking software issues, you might need to worry about setting the time zone. PC-Pine includes the time zone as part of outgoing email. There is a generic way for PC applications to get the time zone, but, because PC-Pine is one of a very few applications which requires this information, time zone might not be previously configured.
The trick is to add an environment variable, TZ, to your PC's
AUTOEXEC.BAT file. The format for the TZ
environment variable is as follows:
ZZZ[+H]H[:MM:SSTTT]First is the 3-letter code for your standard time, then a "+" or a "-" for direction of offset from GMT, then the amount of offset (hours, minutes, seconds) and finally the 3-letter code for your summer- or daylight savings time. Everything in  brackets is optional.
The default time zone is "
PST-8PDT" (U.S. Pacific Time).
Coincidentally, Microsoft is headquartered in that time zone.
As an example, people in the Eastern part of the US should add this line
imapd, is compiled. Installing
imapdrequires placing the binary in the appropriate directory, usually
/usr/etc, and adding entries to
/etc/inetd.confor their counterparts. The following line is appropriate for
imap 143/tcp # Mail transferand the next line is appropriate for
imap stream tcp nowait root /usr/etc/imapd imapdThe
/etc/inetd.conffile entry may vary on different versions of UNIX. Some have a slightly different set of fields. Also the pathname in
/etc/inetd.confmust match the path where
With this configuration, the IMAP server runs without pre-authentication.
Each new IMAP connection requires a correct username and password. IMAP
can also be run with pre-authentication based on the standard rsh
mechanism. To enable this, the user account on the IMAP server must
contain a valid file which grants access to the client machine. Enabling
rimap authentication is done by creating a link called
imapd. Basically, what is
happening is that Pine is taking advantage of the ability that
rsh has to use privileged TCP ports so it doesn't have to run
in privileged mode. If the
rimap authentication fails it
will drop back to plain password authentication.
PC-Pine cannot take advantage of rimap authentication. Also, if your system uses a distributed configuration database, like NIS, Yellow Pages or Netinfo, be sure that appropriate steps are taken to ensure the above mentioned information is updated.
The location of the following support files may be controlled by variables in the personal or global Pine configuration file: signature, addressbook and its index file, postponed messages, and newsrc.
Unix Pine uses the following environment variables:
PC-Pine's help text and help text index file are expected to reside in the
same directory as the
PINE.EXE executable, as they are
essentially extensions of the executable. The personal configuration file
may be in the same directory as the executable, or if that is inconvenient
because the executable is on a shared or read-only drive, then it can be
in a file named by the
$PINERC environment variable, or in
$HOME\PINE\PINERC, where if not set,
defaults to the root of the current working drive.
Most of the other support files key off of the location of the
PINERC file. However, in the case of the NEWSRC file, the
$HOME\NEWSRC is checked first. Also, the postponed
messages and interrupted message folders are placed in the default folder
collection, normally in the directory
The location of the following support files may be controlled by variables in the personal or global Pine configuration file: signature, addressbook (and its index file), postponed messages, and newsrc.
PC-Pine uses the following environment variables: