From: (no name) (no email)
Date: Wed May 01 2002 - 12:15:04 EDT
On 04/29/2002 05:41:44 PM Victor wrote:
>On Mon, 29 Apr 2002, Alex Michlin wrote:
>
>> I am running postfix 1.1.7 and have the following as a body_check:
>>
>> # Block banned file types
>>
/^Content-(Disposition|Type):.*name="?.*\.(exe|bat|com|pif|vb|lnk|scr|reg|chm|
>> wsh|js|inf|shs|job|ini|shb|scp|scf|wsc|sct|dll)/ REJECT The attached
file
>> type(s) are banned by this server.
>
>body_checks is not an effective pre-emptive mechanism. It is best at
>filtering repeated instances of specific message patterns. If you want to
>block MIME attachments based on filename and content-type criteria, you
>need a MIME filter. The Postfix content_filter mechanism allows you to
>plug one in, but Postfix itself does not provide anything in this space.
>
I'm about to build a test server with the combo of Postfix, SpamAssassin,
and Anomy Sanitizer. I'm using the Procmail html-trap now, but Anomy
seems to have taken this product, rewritten it in Perl, and given it more
configurability.
I'm going to use SpamAssassin instead of RBL checks in Postfix because I
have continual collateral damage. SA is not all or nothing. It will give
a score if a site appears on your RBLs. By tweaking this score, other
Spam indicators may need to be activated before it is labelled Spam. My
goal is to use this to eliminate continual maintenance of whitelists and
body/header RX.
See --> http://advosys.ca/papers/postfix-filtering.html
<<Dan>>
-
To unsubscribe, send mail to with content
(not subject): unsubscribe postfix-users
|
|
|