One of the
classifications that may be assigned is Document
.
This denotes that the information is a compound document.
Examples of compound documents are Word (.doc),
PowerPoint (.ppt) and Excel (.xls).
MAILsweeper can be
configured to detect and block documents. This is achieved by
editing the [Validation]
configuration section, to
ensure that the DetectDocument
directive is no
longer commented out.
![]() |
For
MAILsweeper the [Validation] section is found
in the validator configuration file, VALIDATE.CFG.
|
[Validation]
;DetectDocument=VALATTR
[Validation]
DetectDocument=VALATTR
![]() |
The MAILsweeper service will have to be restarted for these changes to come into effect. |
If DetectDocument
is activated for MAILsweeper, any message with a
document attached is discarded. The sender of the message is
informed accordingly.
You may wish to block or allow documents 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 [DetectDocument]
section, using a PerformIf
directive (to block
documents for certain users only) or a SkipIf
directive (to allow documents for certain users only).
RESPONSE allow ...RESPONSE No_Documents PRIORITY 2
FROM *@* To *@* allow ;allow everythingFROM user1@company.com ;List of users not allowed user2@company.com ;to send documents.
user3@company.comTo *@* No_Documents
FINISH
A new AMUcheck rule is defined.
In this example, the
rule names the users not allowed to send
documents.1 When the
addresses of a message match with this rule the <Response>
generated by AMUcheck is No_Documents
.
A new RESPONSE
statement is also listed in the first section of the file, to
define the No_Documents
<Response>.
[AMU]
AuthFile=C:\MSW\CONFIG\AUTHFILE.TXT
If=No_Documents, NoDocuments=TRUE, allow
This is the attribute
that is checked by the PerformIf
directive in the [DetectDocument]
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.
[DetectDocument]
PerformIf=NoDocuments==TRUE
HaveDocument=ContainerClass==Document
If the value is TRUE
then checking by the [DetectDocument]
section is performed.
For a similar
configuration, using SkipIf
to allow documents for
certain users only, see the blocking executables example on page 5-26.
![]() |
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.