pmx-mlog-watch - Scans the PureMessage message log and reports on anomalies
The pmx-mlog-watch
program scans the activity in the message
log's inbound traffic for anomalies that may indicate spam activity.
The message log is specified in the message_log
setting within
<Milter> sections of the pmx.conf file.
If anomalies are detected, a report is generated that describes the activity and the envelope sender or relay that was the cause.
Options can be specified either in a configuration file (by default, etc/logwatch.conf), or on the command line. Options specified on the command line override those specified in the configuration file.
pmx-log-watch
from
running too long if lots of messages were received and the --scan-window
is too large. If this number is met or exceeded, a warning is written
to the log specified in the log_to
setting in the pmx.conf configuration
file (by default, pmx_log
). The default is 10000 lines.
--scan-window
. If a relay sends more than this
number of messages, a report is generated. The default is 5000 messages.
--scan-window
. If a sender sends more than this
number of messages, a report is generated. The default is 5000 messages.
--max-rcpts
. If a relay
triggers the --max-rcpts
counter more than the number of times specified
here during the --scan-window
, a report is generated. The default is 5000
triggers.
--max-size
. If a sender
triggers the --max-size
counter more than the number of times specified
here during the --scan-window
, a report is generated. The default is 5000
triggers.
the pmx-mlog manpage, the pmx-mlog-react manpage, the logwatch.conf manpage
Copyright (C) 2000-2008 Sophos Group. All rights reserved. Sophos and PureMessage are trademarks of Sophos Plc and Sophos Group.