Messages that have been tagged as having malicious content viruses also have a header inserted:
X-CSD-MailScanner: Found to be infected
...this header can be used to filter out infected messages with procmail, MS Outlook, or other mail filtering software. See below for more details on filtering these messages.
The mailscanner will also insert one of the following warnings into the subject of the message, indicating that suspicious content was found:
| {Virus?} |
A virus was found and removed by the virus scanner |
| {Dangerous Content?} |
Dangerous Object Codebase
tag HTML was found by the virus scanner |
| {Filename?} | A prohibited type of file attachment was found and removed |
| .scr |
Windows Screen Saver |
| .bat |
Windows Batch File |
| .com |
Windows Command File |
| .reg |
Windows Registry File |
| .cpl |
Windows Control Panel File |
| .pif |
MS-Dos program shortcut |
| .wsc .wsf .wsh |
Windows Scripting Extensions |
| .vbe .vbs |
Visual Basic Scripting Extensions |
:0
* ^X-CSD-MailScanner: Found to be infected
Mail/virus
X-CSD-MailScanner-SpamCheck: spam
Here is an example of a .procmailrc rule that will allow you to do this:
:0
* ^X-CSD-MailScanner-SpamCheck: spam
Mail/spam
If you are also running your own local instance of spamassassin, we recommend ordering your rules as follows to minimize the CPU load on your machine. This removes already-tagged viruses and spam before they are reprocessed with spamassassin:
##
## Remove messages that the mailscanner tagged
## as viruses
##
:0
* ^X-CSD-MailScanner: Found to be infected
Mail/virus
##
## Remove messages that the mailscanner tagged
## as spam
##
:0
* ^X-CSD-MailScanner-SpamCheck: spam
Mail/spam
##
## Tag with local spamassassin
##
:0fw
| /usr/local/bin/spamassassin
##
## Remove messages that spamassassin tagged
## as spam
##
:0
* ^X-Spam-Status: Yes
Mail/spam
There is also a spam score header that looks like this:
X-CSD-MailScanner-SpamScore: sssssssssssssssss
The significance of this header is that the number of 's's reflects the magnitude of the likelihood that this message is spam. spamassassin traditionally considers anything with a score of five or more to be spam. If you like, you can filter messages with a custom score using this header.
For example, if you wanted to filter anything with a score of seven or more, you could use this procmail rule:
:0
* ^X-CSD-MailScanner-SpamScore:\ sssssss
Mail/spam
Or if you wanted to filter anything with a score of three or more, you could use this rule:
:0
* ^X-CSD-MailScanner-SpamScore:\ sss
Mail/spam