alpine [ options ] [ address , address ]
alpinef [ options ] [ address , address ]
Alpine is a screen-oriented message-handling tool. In its default configuration, Alpine offers an intentionally limited set of functions geared toward the novice user, but it also has a large list of optional "power-user" and personal-preference features. alpinef is a variant of Alpine that uses function keys rather than mnemonic single-letter commands. Alpine's basic feature set includes:
Alpine supports MIME (Multipurpose Internet Mail Extensions), an Internet Standard for representing multipart and multimedia data in email. Alpine 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. Alpine'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. Alpine, PC-Alpine, or many other programs) to exchange formatted documents, spread-sheets, image files, etc, via Internet email.
Alpine 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 posted directly via SMTP (Simple Mail Transfer Protocol).
The command line options/arguments are:
There are several levels of Alpine 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 Alpine also uses the following environment variables:
TERM
DISPLAY (determines if Alpine 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.
~/.pine-debug[1-4] Diagnostic log for debugging.
~/.pinerc Personal alpine config file.
~/.newsrc News subscription/state 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
Alpine Information Center: http://www.washington.edu/alpine
Source distribution: ftp://ftp.cac.washington.edu/alpine/alpine.tar.gz
Alpine Technical Notes, included in the source distribution.
C-Client messaging API library, included in the source distribution.
The University of Washington Alpine development team (part of the UW Office of Computing & Communications) includes: Project Leader: Mike Seibel Principal authors: Mike Seibel, Steve Hubert, Jeff Franklin C-Client library & IMAPd: Mark Crispin Documentation: Many people! Project oversight: Terry Gray, Lori Stevens Principal Patrons: Ron Johnson, Mike Bryant Initial Alpine code base: Pine - by the University of Washington, 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! $Date: 2008-08-22 13:40:16 -0700 (Fri, 22 Aug 2008) $
alpine Version 2.00
Editing commands are entered using control-key combinations. As a work-around for communications programs that swallow certain control characters, you can emulate a control key by pressing ESCAPE twice, followed by the desired control character, e.g. "ESC ESC c" would be equivalent to entering a ctrl-c. The editor has five basic features: paragraph justification, searching, block cut/paste, a spelling checker, and a file browser.
Paragraph justification (or filling) takes place in the paragraph that contains the cursor, or, if the cursor is between lines, in the paragraph immediately below. Paragraphs are delimited by blank lines, or by lines beginning with a space or tab. Unjustification can be done immediately after justification using the control-U key combination.
String searches are not sensitive to case. A search begins at the current cursor position and wraps around the end of the text. The most recent search string is offered as the default in subsequent searches.
Blocks of text can be moved, copied or deleted with creative use of the command for mark (ctrl-^), delete (ctrl-k) and undelete (ctrl-u). The delete command will remove text between the "mark" and the current cursor position, and place it in the "cut" buffer. The undelete command effects a "paste" at the current cursor position.
The spell checker examines all words in the text. It then offers, in turn, each misspelled word for correction while highlighting it in the text. Spell checking can be cancelled at any time. Alternatively, pico will substitute for the default spell checking routine a routine defined by the SPELL environment variable. The replacement routine should read standard input and write standard output.
The file browser is offered as an option in the "Read File" and "Write Out" command prompts. It is intended to help in searching for specific files and navigating directory hierarchies. Filenames with sizes and names of directories in the current working directory are presented for selection. The current working directory is displayed on the top line of the display while the list of available commands takes up the bottom two. Several basic file manipulation functions are supported: file renaming, copying, and deletion.
More specific help is available in pico's online help.
Lastly, when a running pico is disconnected (i.e., receives a SIGHUP), pico will save the current work if needed before exiting. Work is saved under the current filename with ".save" appended. If the current work is unnamed, it is saved under the filename "pico.save".
pico.save Unnamed interrupted work saved here. *.save Interrupted work on a named file is saved here.
$Date: 2008-08-22 13:40:16 -0700 (Fri, 22 Aug 2008) $
pico Version 5.04
Pilot displays the current working directory at the top of the screen. The directory's contents are displayed in columns of file name, file size pairs. Names that are directories are indicated by the name "(dir)" in place of the file size. The parent of the current working directory is indicated by the file name ".." and size of "(parent dir)". File names that are symbolic links to other files are displayed with a file size of "--".
Several basic file manipulation commands are provided: Delete, Rename, Copy, View, Launch, and Edit. The "View" and "Edit" commands operate on text files only. By default, the "View" command displays files using "alpine -F", but will respect the environment variable PAGER if set. The "Edit" command simply invokes "pico". The "Launch" command provides a convenient way to either execute the selected file or to run an application on it.
More specific help is available in pilot's online help.
$Date: 2005/01/14 20:40:14 $
pilot Version 1.1
All commands accept the -d, -v, and -u switches in addition to any command-specific switches.
mailutil check [MAILBOX]
mailutil create MAILBOX
mailutil delete MAILBOX
mailutil rename SOURCE DESTINATION
mailutil copy [-rw] [-kw] [-ig] SOURCE DESTINATION
mailutil move [-rw] [-kw] [-ig] SOURCE DESTINATION
mailutil append [-rw] [-kw] [-ig] SOURCE DESTINATION
mailutil appenddelete [-rw] [-kw] [-ig] SOURCE DESTINATION
mailutil prune MAILBOX CRITERIA
mailutil transfer [-m mode] [-rw] [-kw] [-ig] SOURCE DESTINATION
mailutil check determines whether new mail exists in the given mailbox (the default is INBOX). The number of new messages is defined as the number of messages that have "Recent" status set. If the mailbox contains no new messages, mailutil check will indicate that no new mail is present; otherwise, it will report the number of new messages. In either case, it will also indicate the canonical form of the name of the mailbox.
mailutil create
creates a new
mailbox
with the given name. The mailbox name must not already exist. A mailbox
can be created in a particular format by prefixing the name with
#driver.
followed by the format name and a
/
character. For example, the command
mailutil create #driver.mbx/junkmail
will create a new mailbox named "junkmail" in mbx format.
mailutil delete deletes an existing mailbox with the given name.
mailutil rename renames an existing mailbox to a new name (which must not already exist). This only works if the old and new names are in the same mail store. A more general means to rename a mailbox is to do a mailutil copy of the old name to the new name, followed by a mailutil delete of the old name.
mailutil copy
creates a new mailbox and copies messages from the old mailbox to the
new mailbox. As in
mailutil create
a mailbox format can be specified with the new mailbox. For example, the
command
mailutil copy INBOX #driver.mbx/INBOX
will copy messages from your existing INBOX to an mbx-format INBOX.
mailutil move is similar to mailutil copy but in addition will also remove (delete and expunge) the messages from the old mailbox after copying them to the new mailbox.
mailutil append and mailutil appenddelete are similar to mailutil copy and mailutil move respectively except that they do not create the destination mailbox.
mailutil prune
prunes the mailbox of messages which match certain criteria, which are
in the form of IMAP2 (RFC 1176) SEARCH arguments. For example, the
command.
mailutil prune INBOX "before 1-jan-2004"
will delete and expunge all messages written before January 1, 2004.
Note that mailutil implements pruning by deleting the matching messages, and then expunging the mailbox. Consequently, mailutil will also expunge any messages which were deleted at the time of the pruning.
mailutil transfer copies an entire hierarchy of mailboxes from the named source to the named destination. Mailboxes are created on the destination as needed. Any error in copying messages will cause the transfer to stop.
Normally, any error in creation will cause the transfer to stop. However, if -m MODE or -merge MODE is specified, a merging transfer is performed. The MODE argument indicats the type of merge:
-m[erge] prompt indicates that the user should be asked for an alternative name to create. If creating the new name fails, the user will be asked again.
-m[erge] append indicates that it's alright to copy the messages into an existing mailbox with that name. If the mailbox does not exist, the user will be prompted for an alternative name.
-m[erge] suffix=XXXX where XXXX is any string, indicates that an alternative name should be built by appending the given suffix to the name. It that alternative name can't be created, then the user will be prompted for an alternative name.
The source hierarchy consists of all mailboxes which start
with the given source name. With the exception of a remote system
specification (within "{}" braces), the source name is used as the
name of the destination. The destination hierarchy is a prefix
applied to any new names being created. For example,
mailutil transfer foo bar
will copy all mailboxes with names beginning with "foo" to names
beginning with "bar" (hence "foobar" will be copied to "barfoobar").
Similarly,
mailutil transfer "{imap.foo.com}" "{imap.bar.com}old/"
will copy all mailboxes from the imap.foo.com IMAP server to
equivalent names starting with "old/" on the imap.bar.com IMAP server.
The -v or -verbose flag prints verbose (non-error) telemetry.
The -u USERID or -user USERID switch attempts to become the indicated user. This is for the benefit of system administrators who want to do mailutil operations on a userid that does not normally have shell access.
The -rw or -rwcopy flag causes the source mailbox to be open in readwrite mode rather than readonly mode. Normally, mailutil tries to use readonly mode to avoid altering any flags in the source mailbox, but some mailbox types, e.g. POP3, can't be open in readonly mode.
The -kw or -kwcopy flag causes the keywords of the source mailbox to be created in the destination mailbox. Normally, mailutil does not create keywords in the destination mailbox so only those keywords that are already defined in the destination mailbox will be preserved. Note that some IMAP servers may automatically create keywords, so this flag may not be necessary.
The -ig or -ignore flag causes the keywords of the source mailbox to be ignored completely and no attempt is made to copy them to the destination mailbox.
The -ig[nore] and -kw[copy] flags are mutually exclusive.
Meaning
See your system manager for more information about the types of mailboxes which are available on your system.
You must surround a #driver.format/mailbox argument with quotation marks if you run mailutil from a shell in which "#" is the comment character.
mailutil March 3, 2008
rpload [ -f ] [ -s trimSize ] -t Type -l Local_file -r Remote_folder
Rpload may be used to convert local Alpine configuration files or address books into remote configurations or address books. It is intended to be used by system administrators. Regular users should normally use the facilities provided within Alpine.
Local_file will usually be a user's alpine configuration file, and Remote_folder is the IMAP folder which will be used (with the help of Alpine's -p, -P, and -x commands or PINECONF, PINERC, and PINERCEX environment variables) as the user's remote configuration folder. A copy of Local_file will be placed in the folder with the correct header lines to satisfy Alpine.
Copyright 1989-2007 by the University of Washington.
$Date: 2005/01/14 20:40:14 $
rpdump [ -f ] -l Local_file -r Remote_folder
Rpdump may be used to copy the actual data from remote Alpine configuration files or address books into a local file. It is intended to be used by system administrators. Regular users should normally use the facilities provided within Alpine.
Local_file will normally be a local temporary file. Remote_folder is the IMAP folder being used as a remote Alpine configuration (with the help of Alpine's -P, -p, and -x commands or PINECONF, PINERC, and PINERCEX environment variables) or remote Alpine address book folder. A copy of the data from Remote_folder will be copied to Local_file.
Copyright 1989-2007 by the University of Washington.
$Date: 2005/01/14 20:40:14 $