![]() |
![]()
| ![]() |
![]()
NAMEOverview of Archiveopteryx.SYNOPSIS/etc/init.d/archiveopteryx {start,stop}/usr/local/etc/archiveopteryx/*.conf DESCRIPTIONArchiveopteryx is a mail server system optimised for long-term storage and heavy access. It comprises a set of server programs that provide access to mail stored in a relational database (PostgreSQL).GETTING STARTEDThe following five steps should suffice to install Archiveopteryx. If they don't, or if anything is unclear, more detailed instructions are available at http://archiveopteryx.org/installation1. Install ArchiveopteryxUsually, this is as simple as:
http://archiveopteryx.org/installation explains what to do in other cases. Use
to start Archiveopteryx using the default configuration from archiveopteryx.conf, which tries hard to be sensible. 2. Add a userRun
to create a username and password. 3. Inject some test mailYou can use deliver(8) to inject some mail you already have.This command injects all the messages from a berkeley mbox file:
4. Check that you can read mailThe mail you just delivered is in your inbox, and you can read it with any IMAP or POP3 client.5. Configure your MTAThe normal way to deliver mail from your MTA into Archiveopteryx is via LMTP. By default, Archiveopteryx listens on 127.0.0.1 port 2026.On aox.org we describe how to configure some common MTAs to work with Archiveopteryx. See e.g. http://archiveopteryx.org/postfix for postfix(1). ARCHITECTUREArchiveopteryx consists of a number of frontend servers, each of which uses backend servers:
Each server is described more fully in its own man page: logd(8), postgres(1) and archiveopteryx(8) for the frontend server, which serves IMAP, POP3, LMTP and/or SMTP and perhaps webmail. Normally, there is one logd(8) process running. In addition there will be at least one postgres(1) and one archiveopteryx(8) process. The servers use TCP to communicate internally, so they can be distributed across a server cluster. Generally, one host will run the database backend, one host (perhaps the same) will run logd(8) and as many as required will run frontends. The man pages for each server explain the use and configuration of each. See archiveopteryx.conf(5) for more about configuring Archiveopteryx in general. SECURITYAll Archiveopteryx servers run in chroot directories.The user-facing servers run in a special jail directory. They have neither read nor write access to this directory. logd(8) runs chrooted to another directories. All of the servers close all open files at startup and drop root privileges. By default they run as user aox, group aox, although these names can be changed using archiveopteryx.conf(5). The servers check that they lose prvileges as expected, and refuse to start if they're too privileged. Note that logd(8) must have permission to create the logfile. MAIL STORAGEArchiveopteryx does not store mail in the RFC-822 format. It parses each message upon delivery, and stores a normalized representation, optimized for fast and reliable search and categorization.This offers the following advantages, among others:
LICENSINGArchiveopteryx is available under two licences, namely the OSL 3.0 license and a commercial software license.The OSL 3.0 (see http://archiveopteryx.org/opensource) is a fairly restrictive open source license similar to the more well-known GNU licenses. It includes a disclaimer of responsibility. Our commercial license offers more flexibility than the OSL and a full warranty. There are also extra services. Contact info@aox.org for more details, or see http://archiveopteryx.org/commercial DEFAULTSThe configurable file and directory names in this build are as follows:
These variables can be changed only by editing the file Jamsettings and recompiling Archiveopteryx. Jamsettings also contains some variables used only during compilation and/or installation, and some which provide defaults for archiveopteryx.conf(5) settings. FILES
AUTHORThe Archiveopteryx Developers, info@aox.org.VERSIONThis man page covers Archiveopteryx version 3.2.0, released 2013-12-02, http://archiveopteryx.org/3.1.3SEE ALSOarchiveopteryx(8), archiveopteryx.conf(5), deliver(8), logd(8), http://archiveopteryx.org
|