|--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:|
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.|
"--log-level=all" option has the same effect.
|--syslog Logs Syslog too.|
|--no-report-request Doesnt show any information received from MTA.|
Reports memory usage each milter session finished.
When MILTER_MEMORY_PROFILE environment variable is set to yes, details are reported.
% MILTER_MEMORY_PROFILE=yes milter-test-client -s inet:10025
|--daemon Runs as daemon process.|
|--user=USER Runs as USERs process. root privilege is needed.|
|--group=GROUP Runs as GROUPs process. root privilege is needed.|
|--unix-socket-group=GROUP Changes UNIX domain socket group to GROUP when "unix:PATH" format SPEC is used.|
processes to process mails. Available value is between 0 and 1000. If it is 0, no worker processes will be used.
NOTE: This item is an experimental feature.
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.
as send packets buffer size on end-of-message. Buffered packets are sent when buffer size is rather than SIZE
bytes. Buffering is disabled when SIZE
The default is 0KB. It means packet buffering is disabled by default.
|--version Shows version and exits.|
The exit status is 0 if milter starts to listen and non 0 otherwise. milter-test-client 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.
The following example runs a milter which listens at 10025 port and waits a connection from MTA.% milter-test-client -s inet:10025
milter-test-server (1), milter-performance-check (1)
|milter manager||MILTER-TEST-CLIENT (1)||November 2015|