mail server storing messages in a database
Project homepage: http://www.archiveopteryx.org/
Description
Archiveopteryx 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).
Package information
- Ports path
- mail/archiveopteryx
- Package architecture
- amd64
- Maintainer
- The OpenBSD ports mailing-list <ports@openbsd.org>
- Categories
- mail, databases
- Available flavors
- None listed
- Only for architectures
- aarch64, amd64, arm, i386, mips64, mips64el, powerpc, powerpc64, riscv64, sparc64, alpha, hppa, m88k, sh
Ports list build and test dependencies as well as runtime dependencies. pkg_add selects those needed for installation.
Direct dependencies
Build
OpenBSD README
This README contains unresolved ports variables; replace them before using its commands.
+-----------------------------------------------------------------------
| Running archiveopteryx on OpenBSD
+-----------------------------------------------------------------------
Archiveopteryx is now installed, and sample configuration files were
created in ${SYSCONFDIR}/archiveopteryx.conf and ${SYSCONFDIR}/aoxsuper.conf
Before using it, you will need to create PostgreSQL users and database,
and you'll need to set aox db user password in archiveopteryx.conf,
and aoxsuper db user password in aoxsuper.conf.
Database initialisation
=======================
Assuming you have an administrative account named `postgres',
you can create the aox/aoxsuper users and archiveopteryx database like
this:
createuser -U postgres --pwprompt --no-superuser --no-createdb \
--no-createrole aox
createuser -U postgres --pwprompt --no-superuser --no-createdb \
--no-createrole aoxsuper
createdb -U postgres -T template0 -E UTF8 -O aoxsuper archiveopteryx
Now load the database schema:
psql -U postgres archiveopteryx -f - <<PSQL;
\set ON_ERROR_STOP
CREATE EXTENSION citext;
SET SESSION AUTHORIZATION aoxsuper;
SET client_min_messages TO 'ERROR';
\i ${TRUEPREFIX}/libexec/archiveopteryx/schema.pg
\i ${TRUEPREFIX}/libexec/archiveopteryx/flag-names
\i ${TRUEPREFIX}/libexec/archiveopteryx/field-names
\i ${TRUEPREFIX}/libexec/archiveopteryx/downgrades
PSQL
Grant privileges to user 'aox':
aox grant privileges aox
If performing an upgrade, you might need to update schema with:
aox upgrade schema
Certificate generation
======================
By default, archiveopteryx uses TLS (unless use-tls is set to no), so it
needs an ssl certificate file in /etc/ssl/archiveopteryx.pem containing
both private key and signed certificate to function properly. If you
don't already have one, edit /etc/ssl/archiveopteryx-openssl.conf to fit
your needs (only CA field is mandatory) and generate a self-signed
certificate with the following command:
openssl req -config /etc/ssl/archiveopteryx-openssl.conf -x509 -days \
1764 -newkey rsa -nodes -keyout /etc/ssl/archiveopteryx.pem \
-out /etc/ssl/archiveopteryx.pem
Startup/Shutdown configuration
==============================
Make sure to startup archiveopteryx after your DB server.
aox show status can give you the status of processes.
Now refer to http://www.archiveopteryx.org/ for more fine-tuned
configuration.