Installing Cone

First, make sure that all the necessary requirements (README) are satisfied. See RPM instructions below if building for Red Hat Linux. See additional notes below for upgrade instructions. Otherwise:


Do not forget make install-configure. It is required.

Unless other options are used, Cone installs in /usr/local:


The configuration file.


The shell script that runs Cone.


The Cone program itself.


Documentation, online help, other files.

/usr/local/lib and /usr/local/include

The development libraries and include files (only if --with-devel was specified to the configure script).

These installation directories, and other options, may be controlled by additional options to the configure script:

--prefix, --bindir, and others...

./configure --help lists about a dozen parameters to the ./configure that specify the directories where various files should be installed.


Sets a non-default location for the systemwide trusted SSL certificate authorities. If not specified, a default list of directories and files is searched for:

  • /etc/ssl/certs
  • /etc/ssl/cert.pem
  • /etc/pki/tls/cert.pem

Select the GnuTLS library even if the OpenSSL library is also installed. The configure script automatically selects whichever one is available. The OpenSSL library is selected if both are present. Use this option to override and select GnuTLS instead.


Install LibMAIL , the mail library used by Cone to access and handle E-mail messages.


Cone can use either aspell or pspell for spell checking. aspell is used if both are installed. This option selects pspell instead.

Upgrading from an earlier version of Cone

Upgrading Cone consists simply of building the new version, and installing it. The new version will overwrite the previous version. Special upgrade instructions are given below.

Upgrading from version 0.96 and earlier

Cone 0.97 is a coordinated update with other Courier packages that introduces support for Unicode-based E-mail protocols. As part of this update, maildir folder names are also changed to use Unicode instead of custom IMAP naming scheme.

Manual conversion steps are needed for local maildir (and mbox) folders. No action is needed if Cone is used exclusively with IMAP and POP3 accounts.

Refer to for additional information; specifically the Converting pre-Unicode maildirs section. When updating Cone together with Courier, Courier-IMAP, or SqWebMail, use the same conversion steps for any maildirs that do not get converted as part of updating Courier, Courier-IMAP, or SqWebMail. When updating Cone only by itself, the maildirmake does not get installed together with Cone but it gets built in the libs/maildir source subdirectory.

Any mbox folders also need to be renamed, but there are no automated tools for that. They'll need to be renamed manually, (or in Cone itself).

Upgrading from version 0.59 and earlier

The address book format has changed in version 0.60. The old address book format will be automatically converted to the new format, when necessary, so no manual intervention is necessary. If Cone is later downgraded to an earlier version, addresses in an address book that contain non-English characters will not be shown correctly.

RPM builds

Use the following procedure to build Cone.

The first step is to create a work area for building RPMs. Skip this step if an RPM build directory is already configured.

echo "%_topdir    $HOME/rpm" > $HOME/.rpmmacros
mkdir $HOME/rpm
cd $HOME/rpm

Finally, download the source code to Cone from Do not unpack the tarball. Execute rpmbuild -ta cone-version.tar.bz2. Two binary RPMs will be created: the main binary package contains Cone. The devel package contains the LibMAIL library and development files. It is only necessary to install the main package to run Cone the devel subpackage is only needed for additional development with LibMAIL .

Git repository

It is also possible to check out the source from git, however additional requirements apply. Besides the usual prerequisites for building Cone, additional development software must be installed. See the Source code repository instructions at