One of the
classifications that may be assigned is Binary
. This
denotes that the information is a data file containing binary
information. For example, a database file.
MAILsweeper can be
configured to detect and block binary files. This is achieved by
editing the [Validation]
configuration section, to
ensure that the DetectBinary
directive is no longer
commented out.
![]() |
For
MAILsweeper the [Validation] section is found
in the validator configuration file, VALIDATE.CFG.
|
[Validation]
;DetectBinary=VALATTR
[Validation]
DetectBinary=VALATTR
![]() |
The MAILsweeper service will have to be restarted for these changes to come into effect. |
If DetectBinary
is activated for MAILsweeper, any message with a
binary file attached is discarded. The sender of the message is
informed accordingly.
You may wish to block or allow binary files for certain users or groups of users only.
This can be achieved
by creating a new AMUcheck rule to name the users and then
setting an attribute during AMUcheck validation. This attribute
can subsequently be checked in the [DetectBinary]
section, using a PerformIf
directive (to block
binary files for certain users only) or a SkipIf
directive (to allow binary files for certain users only).
RESPONSE allow RESPONSE isjunkmail PRIORITY 1 RESPONSE copyadministrator PRIORITY 1 RESPONSE deny PRIORITY 2RESPONSE Allow_Binary PRIORITY 1
FROM *@* To *@* allow ;allow everythingFROM user1@company.com ;List of users allowed user2@company.com ;to send binary files. user3@company.com To *@* Allow_Binary
FINISH
A new AMUcheck rule is defined.
In this example, the
rule names the users allowed to send binary
files.1 When the addresses
of a message match with this rule the <Response>
generated by AMUcheck is Allow_Binary
.
A new RESPONSE
statement is also listed in the first section of the file, to
define the Allow_Binary
<Response>.
[AMU]
AuthFile=C:\MSW\CONFIG\AUTHFILE.TXT
If=Allow_Binary, AllowBinary=TRUE, allow
This is the attribute
that is checked by the SkipIf
directive in the [DetectBinary]
configuration section.
The <Response>
is then reset to allow
. This is the actual <Response>
generated by AMUcheck. It allows the message to be delivered
normally, assuming no higher priority <Response>
is generated by one of the configured plug-in validator
instances.
[DetectBinary]
SkipIf=AllowBinary==TRUE
HaveBinary=ContainerClass==Binary
If the value is TRUE
then checking by the [DetectBinary]
section is skipped.
For a similar
configuration, using PerformIf
to block binary files
for certain users only, see the blocking attachments example on page 5-29.
![]() |
See the AMUcheck section on page 7-97 for
more details. Also, for more details on the If ,
PerformIf and SkipIf
directives, see the Common validator directives section
on page 7-102. |
Copyright © 1998, Content Technologies Limited. All rights reserved.