3.0.0 was released on on 2008-08-25.
This is a feature release and we expect to release 3.0.1 soon.
The new features in 3.0.0 include:
- aox has command-line searches;
show search helps construct
searches, aox undelete and aox add view use searches.
- aox add alias etc. has more friendly syntax (higher dwim factor).
- Bodyparts can have the same MD5 hash.
- Full-text search is available. Needs
PostgreSQL 8.3 and the new command
aox tune database.
- Memory usage is configurable
(memory-limit=32); bigger numbers
imply more caching.
- Message rejection is now configurable using
- The tables can be put in
any schema, not just public.
listen/notify used instead of the ocd.
- aox shutdown includes a two-second pause, is more polite to
clients, and handles the race condition described in
- The message injector can inject several messages at a time,
speeding up aoximport and other
- Client usage is logged using the
connections log table.
- Syslog support added (note: syslog
has limited line length).
- Less logging by default.
- SASL DIGEST-MD5 disabled by default due to
widespread interoperability problems.
- Sieve ereject support added.
allows/disallows forged From on outgoing mail.
The bugfixes in 2.11 are also in this release. In
addition there are some unremarkable changes:
- Various SQL improvements: More set logic (=any(…)) instead of
boolean logic, more use of savepoints.
- Various IMAP optimisations (store, status, select, fetch).
- The pool of database connections is managed more cleverly.
- aox grant privileges uses clearer queries, and
aox upgrade schema checks/fixes privileges.
- Some support for old (>2 years) databases removed.
- Support for >2GB logfiles added.
- Magic hacks to avoid queries that bother PostgreSQL 8.1.
- HTTP-related changes, still not conclusive.
- IMAP VIEW command removed, views remain supported.
- IMAP commands finish in order (even if executed concurrently).
- Fetch responses are sent at regular pace, to avoid timing out clients.
- IMAP Search has been cleaned up for reuse (likely release in 3.1).
- A couple of message parsing improvements that were hard to do in 2.11.
- The privileges needed for each table are explicitly marked in the
CREATE TABLE statements.
- We have our first-ever unintentionally undocumented feature.
- Compile fixes for new warnings in g++ 4.3.
If you are upgrading from 2.x, please run "aox stop" before you
install the new release (because the location of the pid files has
changed, so the new aox won't be able to stop the running server).
The 2.11 bugfix release uses a database that is
compatible with this release, so if you upgrade from 2.x to 3.0.0 and
encounter problems, you can fall back safely to 2.11.
Although we support PostgreSQL 8.1.x, we strongly recommend that you
upgrade to PostgreSQL 8.3 to get better performance from this release.
The next 3.0.x bugfix release is 3.0.1. We have not decided on a
release date yet.
If you would like to be notified of future releases, please
join our announcements list.
We appreciate your feedback. If you try out Archiveopteryx, please
consider sharing your experiences on the
In case of questions, please write to email@example.com.
About this page
Last modified: 2010-11-19