Search | Directories | Reference Tools
UW Home > Discover UW > IT Connect > Alpine Messaging System 
 Search the Alpine Messaging System site

Obtaining Alpine software

Source Download

The full Alpine 2.00 source and documentation release, containing code to generate Unix Alpine, PC-Alpine and Web Alpine as well as imapd and supporting tools, is available in either:

alpine/alpine.tar.Z  (MD5: c4be68e6889e78d8238e6beef6986871 )
alpine/alpine.tar.gz  (MD5: 0f4757167baf5c73aa44f2ffa4860093 )
alpine/alpine.tar.bz2  (MD5: 84e44cbf71ed674800a5d57eed9c1c52 )

As a convenience, the UW Alpine Team also offers packages and pre-compiled binaries for a variety of platforms including Windows. Snapshots of development sources are available in a ReadOnly Subversion repository. In addition, contributors from around the world provide resources and adaptations of Alpine as well as mirrored distribution sites.

Package Downloads

Packages for the two main styles of packaging systems, the RedHat/Fedora RPM-style packaging system, and the Debian dpkg-style system are offered. Likewise, the scripts to build these packages and instructions on how to use them are included in the source distribution under the packages directory.

The RPM packages will likely work across the most recent versions of RedHat and Fedora, with a good chance of also working on Mandrake or SuSE, which also use the RPM system.

RedHat/Fedora RPM packages (built on Fedora Core 7)

alpine-2.00-1.i386.rpm  (binary, MD5: 8854b6a12bc3606c5c87e1ea4dd1e5e4 )
alpine-2.00-1.src.rpm  (source, MD5: 877a19da8a0e1ea3e8c23eec524bdb35 )
RPM installation instructions

Debian .deb package (built on Debian GNU/Linux 4.0)

alpine_2.00_i386.deb  (MD5: 911c422f02054c6e58a472776b06787b )
.deb installation instructions

These packages include Alpine, Pico, and other smaller programs that are also part of a standard alpine build. UW-Imapd, which is also part of a standard Alpine build, is a program of which it is recommended to have a better understanding, and is thus not included in these Alpine packages.

Installing RPMs

For most cases, it should be enough simply to grab the first binary package and run the following command:

rpm -ivh alpine-2.00-1.i386.rpm
This installation should succeed on most recent RedHat and Fedora systems, and will likely succeed on recent Mandrake systems as well. Other useful rpm commands include:
rpm -Uvh alpine-2.00-1.i386.rpm
to upgrade an existing alpine installation, and
rpm -e alpine
to uninstall an existing alpine installation.

If installing the binary RPM fails, you will quite likely succeed by installing from the source RPM. You can build from source RPM either by installing the RPM as you would the binary one, building it using the alpine.spec file that gets put in the SPECS directory, or by running the command
rpmbuild --rebuild alpine-2.00-1.src.rpm
Both of these methods require having sufficient permissions to build in the source directory; consult the instructions for building using spec files in packages/README in the full source (alpine.tar.gz) to better understand how to do this.

Installing .debs

To install the .deb package, the following command should suffice:

dpkg -i alpine_2.00_i386.deb
Uninstalling the package can be done by running the command
dpkg -r alpine

As with building RPMs, the alpine distribution includes a collection of files for building .deb files yourself.

Windows Downloads

The PC-Alpine Windows application is available as either an installer program, or as an individual binary to be installed manually. The installer, which will install and set up Alpine and Pico so that it shows in the Windows start menu programs list, is the preferred method for most users. It is available here:

PC-Alpine setup program  (MD5: 6085cc628179eb9606765154a74732f4 )

If you prefer to setup PC-Alpine yourself, download the .zip file containing only the PC-Alpine program.

alpine-2.00-wnt.zip  (MD5: cef694c0b13419c6b43585ba1da35304 )

If upgrading from PC-Pine, PC-Alpine can be installed alongside the older program. Installing PC-Alpine leaves PC-Pine in place, to be removed at the user's discretion. PC-Alpine can be set up to point to its own configuration, or it can be pointed to PC-Pine's configuration. If upgrading from an older version of PC-Alpine, the installer will update the PC-Alpine already in place.

PC-Alpine relies on an external program, aspell, for its spell checker. Aspell can be obtained at http://aspell.net/win32.

The Alpine Technical Notes contain detailed explanations about installation, support files and environment variables, and noteworthy facts about running the Alpine email client on a personal computer.

Pre-Compiled Binary Downloads

Because Alpine, Pico and other components of the Alpine Messaging system are self contained applications, it is usually sufficient to simply download the pre-compiled binaries and copy them to a generally accessible directory, such as /usr/local/bin.

Mac OS X Universal Binaries (Alpine version 1.10)

Mac OS X binaries are built under version 10.5 using configure options --enable-osx-universal-binaries and --disable-dependency-tracking. Binaries currently available are:

alpine  (MD5: d498be54d419b9cfa4ce8c6b3aba06cd )
pico  (MD5: 15348b216e6c9a90e680423511f9c7fe )
imapd  (MD5: 4867e06137df7f2efc5203aa55f6f005 )
mailutil  (MD5: 43193486e3ec35791d313da9267366cf )
pilot  (MD5: 7aa38c25cfae96b973a0095d37d27424 )
rpdump  (MD5: 3eeee5eb007c61be7a07bc13385b33ae )
rpload  (MD5: 25bd22bf7c7993dd1c113c843fd21280 )

Nokia N800 binaries (Alpine version 1.10)

Nokia N800 binaries are built for IT OS 2007 and later and presumed to run on IT OS 2006 using configure options --with-passfile=.pinepwd. Binaries are currently available as a gzip'd tar file at:

alpine-1.10-n800.tar.gz  (MD5: 0ef1001843bbaf94f01cef31608c00b0 )

Snapshots of Development Code

Snapshots of our development sources for Alpine are available from our ReadOnly Subversion (svn) repository at:
https://svn.cac.washington.edu/public/alpine/snapshots/

The Unix svn command might be used like this:

% mkdir alpinetest
% cd alpinetest
% svn checkout https://svn.cac.washington.edu/public/alpine/snapshots/
% cd snapshots
% ./configure; make

After the first checkout a later update could be done like this:

% cd alpinetest/snapshots
% svn update
% make

When building on a Windows system there is no configure command and the make command is replaced with the command

.\build wnt