an effective anti-spam with milter - milter manager

Install to Debian GNU/Linux

Install to Debian GNU/Linux describes it. You can maintain milter manager package easily because milter manager can be installed with aptitude.

Install to Ubuntu Linux

Install to Ubuntu Linux describes it. You can maintain milter manager package easily because milter manager can be installed with aptitude.

Install to CentOS

Install to CentOS describes it. You can maintain milter manager package easily because milter manager can be installed as RPM package.

Install to FreeBSD

Install to FreeBSD describes it.

Generate graphs for statistics data

There are documents for each platform:

Find a configuration file

Here are configuration file locations when you install milter manager followed by install manual for your platform:

milter-manager.local.conf is a file what you create newly. milter-manager.conf loads milter-manager.local.conf in the same directory by default.

Connect milter-manager via TCP/IP

"inet:" is used for manager.connection_spec .

# Listen on 10025 port. milter-manager accepts a connection from localhost
manager.connection_spec = "inet:10025@localhost"

Connect milter-manager via UNIX domain socket

"unix:" is used for manager.connection_spec .

# Listen on /var/run/milter/milter-manager.sock.
manager.connection_spec = "unix://var/run/milter/milter-manager.sock"

A socket file permission can be specified by manager.unix_socket_mode .

# Users who belongs to the same group that owns the socket
# can connect to milter-manager.
manager.unix_socket_mode = 0660

A group for socket file can be specified by manager.unix_socket_group .

# Socket file is belongs to "milter" group.
manager.unix_socket_group = "milter"

Cleanup UNIX domain socket

Creating socket is failed when the same name of newly UNIX domain socket. To avoid the situation, milter-manager provides features that remove socket file on the following points:

Normally, milter-manager doesn't fail to create a socket by 'socket file already exists' reason because milter-manager enables both of them by default.

If you want to disable the features, change the following configuration respectively:

Here is an configuration to disable both of them:

# Don't remove an existing socket file before creating a socket file
manager.remove_unix_socket_on_create = false
# Don't remove a socket file after its use
manager.remove_unix_socket_on_close = false

Apply milters to messages only for specified accounts

milter-manager provides a sample configuration to restrict milter application to specified account. This section shows an example that all registered milters only applied to the following accounts:

Here is a configuration to be appended to milter-manager.local.conf :

restrict_accounts_by_list("test-user@example.com",
                          /@test\.example\.com\z/)

This configuration syntax may be changed because this is still sample. But a feature provided by this configuration will be still provided. The feature will be more powerful by supporting database and LDAP as an account source in the future.