|
Mailismus can optionally be configured to use a relational database for some of its functions.
We say "optionally", in the sense that some subsystems (eg. the Queue) have an optional database flavour but can also work equally well without it, while other susbsystems (eg. Blacklisting, Greylisting) do require a backing database, but are themselves optional.
Mailismus supports multiple types of databases, which can be divided into two broad families:
• Server databases: Potentially located across the network and shared with other users
• Embedded databases: Private local files that are not shared with other applications
Section §4.8 has already gone through the supported database types, and the basic config settings which underpin them all, so this section explains how to do any prior installation and setup that may be required before Mailismus can access a database.
Mailismus uses Java's JDBC interface to connect to the database, so you will need to install the appropriate driver for each database.
A JDBC driver is simply a vendor-provided JAR file.
Having obtained the JAR file and put it somewhere on your system, "installation" simply consists of adding its pathname to the Mailismus classpath.
The most convenient way to do this is to put it in the
dependjars
config item in the
naf.xml
config file - see NAF Guide section §2.
You can easily locate the download pages for the database types listed in §4.8, and while some of them may offer more or less elaborate installation procedures, all that Mailismus needs is their JARs, not a functioning system.
For the vast majority of databases, the JDBC driver maps to a single JAR, but in some cases this may have dependencies on other JARs, or even on underlying native libraries
(.so
files for Unix,
DLLs
for Windows), so you would need to put those on your Path as well.