pine [ options ] [ address , address ]
pinef [ options ] [ address , address ]
Pine is a screen-oriented message-handling tool. In its default configuration, Pine offers an intentionally limited set of functions geared toward the novice user, but it also has a growing list of optional "power-user" and personal-preference features. pinef is a variant of Pine that uses function keys rather than mnemonic single-letter commands. Pine's basic feature set includes:
Pine supports MIME (Multipurpose Internet Mail Extensions), an Internet Standard for representing multipart and multimedia data in email. Pine allows you to save MIME objects to files, and in some cases, can also initiate the correct program for viewing the object. It uses the system's mailcap configuration file to determine what program can process a particular MIME object type. Pine's message composer does not have integral multimedia capability, but any type of data file --including multimedia-- can be attached to a text message and sent using MIME's encoding rules. This allows any group of individuals with MIME-capable mail software (e.g. Pine, PC-Pine, or many other programs) to exchange formatted documents, spread-sheets, image files, etc, via Internet email.
Pine uses the c-client messaging API to access local and remote mail folders. This library provides a variety of low-level message-handling functions, including drivers for a variety of different mail file formats, as well as routines to access remote mail and news servers, using IMAP (Internet Message Access Protocol) and NNTP (Network News Transport Protocol). Outgoing mail is usually handed-off to the Unix sendmail, program but it can optionally be posted directly via SMTP (Simple Mail Transfer Protocol).
The command line options/arguments are:
* UWIN = University of Washington Information Navigator
There are several levels of Pine configuration. Configuration values at a given level over-ride corresponding values at lower levels. In order of increasing precedence:
o built-in defaults.
o system-wide
pine.conf
file.
o personal
.pinerc
file (may be set via built-in Setup/Config menu.)
o command-line options.
o system-wide
pine.conf.fixed
file.
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 "no-" in front of an individual feature name. Unix Pine also uses the following environment variables:
TERM
DISPLAY (determines if Pine can display IMAGE attachments.)
SHELL (if not set, default is /bin/sh )
MAILCAPS (semicolon delimited list of path names to mailcap files)
/usr/spool/mail/xxxx Default folder for incoming mail.
~/mail Default directory for mail folders.
~/.addressbook Default address book file.
~/.addressbook.lu Default address book index file.
~/.pine-debug[1-4] Diagnostic log for debugging.
~/.pinerc Personal pine config file.
~/.newsrc News subscription/state file.
~/.signature Default signature file.
~/.mailcap Personal mail capabilities file.
~/.mime.types Personal file extension to MIME type mapping
/etc/mailcap System-wide mail capabilities file.
/etc/mime.types System-wide file ext. to MIME type mapping
/usr/local/lib/pine.info Local pointer to system administrator.
/usr/local/lib/pine.conf System-wide configuration file.
/usr/local/lib/pine.conf.fixed Non-overridable configuration file.
/tmp/.\usr\spool\mail\xxxx Per-folder mailbox lock files.
~/.pine-interrupted-mail Message which was interrupted.
~/mail/postponed-msgs For postponed messages.
~/mail/sent-mail Outgoing message archive (FCC).
~/mail/saved-messages Default destination for Saving messages.
pico(1), binmail(1), aliases(5), mailaddr(7), sendmail(8), spell(1), imapd(8)
Newsgroup: comp.mail.pine
Pine Information Center: http://www.washington.edu/pine
Source distribution: ftp://ftp.cac.washington.edu/pine/pine.tar.Z
Pine Technical Notes, included in the source distribution.
C-Client messaging API library, included in the source distribution.
The University of Washington Pine development team (part of the UW Office of Computing & Communications) includes: Project Leader: Mike Seibel. Principal authors: Mike Seibel, Steve Hubert, Laurence Lundblade. C-Client library & IMAPd: Mark Crispin. Pico, the PIne COmposer: Mike Seibel. Bug triage, user support: David Miller. Port integration: David Miller. Documentation: David Miller, Stefan Kramer, Kathryn Sharpe. PC-Pine for DOS: Mike Seibel. PC-Pine for Windows: Tom Unger. Project oversight: Terry Gray. Principal Patrons: Ron Johnson, Mike Bryant. Additional support: NorthWestNet. Initial Pine code base: Elm, by Dave Taylor & USENET Community Trust. Initial Pico code base: MicroEmacs 3.6, by Dave G. Conroy. User Interface design: Inspired by UCLA's "Ben" mailer for MVS. Suggestions/fixes/ports: Folks from all over! Copyright 1989-1996 by the University of Washington. Pine and Pico are trademarks of the University of Washington. 96.02.17