|--help Shows available options and exits.|
|--connection-spec=SPEC Specifies a socket that accepts connections from MTA. SPEC should be formatted as one of the followings:|
This option overrides "manager.connection_spec" in configuration file.
|--config-dir=DIRECTORY Specifies a directory that includes milter-managers configuration file. milter-manager tries to load DIRECTORY/milter-manager.conf. If it isnt find, milter-manager loads milter-manager.conf in default directory.|
Saves process ID of milter-manager to FILE.
This option overrides "manager.pid_file" in configuration file.
Runs milter-manager as NAME user. milter-manager should be started by root.
This option overrides "security.effective_user" in configuration file.
Runs milter-manager as NAME group. milter-manager should be started by root.
This option overrides "security.effective_group" in configuration file.
Changes group of UNIX domain socket for accepting connection by milter-manager to NAME group. Specified group should be one of the effective users supplementary groups.
This option overrides "manager.unix_socket_group" in configuration file.
Runs milter-manager as daemon process.
This option overrides "manager.daemon" in configuration file.
|--no-daemon This option cancels the prior --daemon option.|
|--show-config Shows the current configuration and exits. The output format can be used in configuration file. This option is useful for confirming registered milters and reporting your milter-managers configuration when you report milter-managers problems.|
Specifies log output items. You can specify multiple items by separating items with "|" like "error|warning|message".
|--log-path=PATH Specifies log output path. If you dont specify this option, log output is the standard output. You can use "-" to output to the standard output.|
as event loop backend. Available values are glib
.If you use glib backend, please refer to the following note.
NOTE: For the sake of improving milter-manager performance per process, event-driven model based architecture pattern is choosed in this software. If this feature is implemented by glib, it is expressed as a callback. Note that glibs callback registration upper limit makes the limitation of the number of communications. This limitations exist against glib backend only.
Logs verbosely. Logs by syslog with "mail". If milter-manager isnt daemon process, standard output is also used.
"--log-level=all" option has the same effect.
|--version Shows version and exits.|
The exit status is 0 if milter starts to listen and non 0 otherwise. milter-manager cant start to listen when connection spec is invalid format or other connection specific problems. e.g. the port number is already used, permission isnt granted for create UNIX domain socket and so on.
/usr/local/etc/milter-manager/milter-manager.conf The default configuration file.
Milter-manager processes the following signals:
SIGHUP Milter-manager reloads its configuration file. SIGUSR1 Milter-manager reopenes log file.
The following example is good for debugging milter-manager behavior. In the case, milter-manager works in the foreground and logs are outputted to the standard output.% milter-manager --no-daemon --verbose
milter-test-server (1), milter-test-client (1), milter-performance-check (1), milter-manager-log-analyzer (1)
|milter manager||MILTER-MANAGER (1)||November 2015|