On most linux systems these commands will install mopher behind the prefix
/usr/local. Use common configure arguments like --prefix or --sysconfdir to
adjust the installation directories to your needs.

Check if mopher was installed correctly:

user@host $ mopherd -v
mopherd-0.5.0

Note: For this to work mopherd needs to be installed somewhere in your $PATH.

Initial configuration

The mopher daemon process uses two configuration files:

mopherd.conf

mopherd.acl

If mopherd.conf does not exist mopherd runs with the builtin default
configuration.

Bulitin default configuration overview

The following table contains the most important default values.

Default

Key

Value

User

moperd_user

nobody

Group

moperd_group

nogroup

Database driver

table

memdb (for all tables)

Milter socket

milter_socket

inet:44555@127.0.0.1

Control socket

control_socket

inet:44554@127.0.0.1

Mopherd user and group

You should change the mopherd user and group to something better than nobody
and nogroup. Add a new system user and group named mopher and configure mopher
to use the new account.

Add a mopher system account:

user@host $ sudo useradd -r mopher

Note: Command may be different on your system. See man useradd(8).

Example mopher.conf:

mopherd_user = "mopher"
mopherd_group = "mopher"

Persistent database storage

If you are using the default database driver memdb, all mopher tables are lost
after the mopherd process is terminated. If you want your mopher tables to
survive a restart you have to use a persistent database driver.

Example mopherd.acl using Spamassassin:

mopherd.acl

The mopherd.acl file controls how mail is filtered. The source distribution
ships with a very basic ACL file. You might want to adjust this file to your
requirements. Following an example of a complete mopherd.acl.