Email with Citadel on Ubuntu 9.04 (Jaunty)

Select distribution:
Traducciones al Español
Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.

This guide has been deprecated and is no longer being maintained.

Citadel is a groupware suite that provides system administrators with an easy method to set up and manage email, calendars, mailing lists and other collaboration tools. It also features an automated installation process and versatile deployment options that allow the application to be scaled across multiple servers.

Before installing Citadel, it is assumed that you have followed our Setting Up and Securing a Compute Instance. If you are new to Linux server administration, you may be interested in our introduction to Linux concepts guide, beginner’s guide and administration basics guide.

This guide also assumes that you wish to run Citadel by itself on this server on port 80 or 443 for browser-based access. Please note: If you intend to install Citadel alongside another web server package such as Apache or nginx, select the “internal” option when asked about web server integration. Be sure to specify unique ports for Citadel such as 8080 for HTTP or 4343 for HTTPS.


Before beginning the Citadel installation process, it is important that you satisfy a few prerequisites. Unless otherwise indicated, all steps should be performed as root.

Configure Package Sources

You’ll need to make sure the universe repositories are enabled in your /etc/apt/sources.list file. If necessary, uncomment or add them as follows:

File: /etc/apt/sources.list
## universe repositories
deb jaunty universe
deb-src jaunty universe
deb jaunty-updates universe
deb-src jaunty-updates universe
deb jaunty-security universe
deb-src jaunty-security universe

Run the following commands to make sure your system is up to date:

apt-get update
apt-get upgrade --show-upgraded

Set the Timezone

You will need to set the timezone of your server. Issue the following command:

dpkg-reconfigure tzdata

If you’re unsure of which timezone to use, you may wish to set this to your timezone or the timezone that the bulk of your users will be in. Additionally, you may want to use Universal Coordinated Time (also known as Greenwich Mean Time).

Set the Hostname

You’ll also need to set the hostname for your system. This can be any name you like, but it should be something that you will remember. In this example, the machine will be named “username”.

echo "username" > /etc/hostname
hostname -F /etc/hostname

Now you will need to configure your Linode so that it associates its hostname with its public IP address. Edit the /etc/hosts file so that the first section resembles the following example. Replace and with your Linode’s public IP and FQDN (

File: /etc/hosts
2 localhost.localdomain localhost username

You’re now ready to begin installing Citadel!

Installing Citadel

Begin by installing the citadel-suite, spamassassin and amavisd-new packages:

apt-get install citadel-suite spamassassin amavisd-new

The installation process will prompt you to answer a couple of questions. Choose “Internal” for web server integration and enter “80” when asked the “Webcit HTTP port” question. If you need to reconfigure any of these options later, you can use the following command:

dpkg-reconfigure citadel-server

Enabling Spamassassin Filtering

Edit the /etc/mailname file to reflect your system’s domain name:

File: /etc/mailname

You’ll need to edit the SpamAssassin configuration file to enable spamd:

File: /etc/default/spamassassin
# Change to one to enable spamd

Start the spamassassin service as follows:

/etc/init.d/spamassassin start

Please note that you’ll finish enabling SpamAssassin support within Citadel later in the “Notes” section.

Running Citadel

Customize the logon banner for your Citadel server by editing the relevant file:

File: /usr/share/citadel-server/messages/hello
Citadel Groupware Server Login

Use the following startup script to initialize Citadel.

/etc/init.d/citadel restart

Visit the web interface in your Web browser. Using our preceding example, the Web address to visit would look like:

The SSL certificate for your Citadel web interface will be self-signed; accept it to continue. If you don’t get a login page in your web browser, you may need to start “webcit” with the following command:

webcit -d

Notes for Running Citadel

At this point, your email system should be fully functional and can be configured through the Webcit interface. When you log in for the first time as “Administrator”, you will not need a password. However, it is recommended that you set a password as soon as possible under the “Advanced” tab.

To finish enabling SpamAssassin support, select “Administration” in the control panel. Next, click “Domain names and Internet mail configuration”. Enter “” in the box for the SpamAssassin host.

Lost Password Recovery

If you lose the password to your administrator account, re-run the setup as follows:

dpkg-reconfigure citadel-server

Specify a different name for the admin user and restart Citadel as follows:

/etc/init.d/citadel restart

You should be able to log in as the new admin user with no password. You may then reset the password for your original administrator account. After this is done, log back in as the original administrator and delete the temporary admin account.

More Information

You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.

This page was originally published on

Your Feedback Is Important

Let us know if this guide was helpful to you.

Join the conversation.
Read other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our Support team or asking on our Community Site.
The Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please update your Cookie Preferences on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser.