cantscan.conf - Specifies the action the pmx_virus_cantscan
should take if pmx_virus
fails to scan a message attachment
/opt/pmx/etc/virus.d/cantscan.conf
pmx_virus_cantscan
should take if pmx_virus
fails to scan a message attachment. The Sophos virus scanner returns
failure codes if it cannot scan an attachment. Some common failure
codes are:
A scan_failed_action
section contains the following:
What action should be taken for this failure code. If a message matches more than one failure code, a 'deny' action always overrides any other actions. Also, if the message contains viruses and unscannable parts, the action is always to 'deny'.
pmx_virus
to ignore this failure code and allow the data
to pass through. This introduces a potential security risk as the
attachment is not guaranteed to be virus-free, and the user is not warned.
pmx_virus
.
It causes pmx_virus_clean
to add a warning (from the template
specified by the template option) about the unscannable part, but does not
replace it.
Also this will cause pmx_virus_cantscan
to return true, which can be
used to treat 'allowed' unscannable messages differently from truly viral
ones.
pmx_virus
.
This value tells pmx_virus_clean
to replace the message part with a
template, like it normally does to parts containing a virus.
It also causes pmx_virus_cantscan
to return false.
language
setting above.
The pmx_virus
test always logs a message to the message log
(located by default in /opt/pmx/var/log) when it fails to scan an
attachment.
Copyright (C) 2000-2008 Sophos Group. All rights reserved. Sophos and PureMessage are trademarks of Sophos Plc and Sophos Group.