> I had better luck by doing this (for example):
>
> %banned_rules = (
> 'BLOCK_EXE' => new_RE(
> # block double extensions in names:
> qr'\.[^./]*\.(exe|vbs|pif|scr|bat|cmd|com|cpl|dll)\.?$'i,
> # blocks MS executable file(1) types:
> qr'^\.(exe|exe-ms)$',
> # block these MIME types
> qr'^application/x-msdownload$'i,
> qr'^application/x-msdos-program$'i,
> ),
> 'DEFAULT' => $banned_filename_re,
> );
>
> $policy_bank{'MYNETS'} = {
> spam_lovers_maps => [1], # don't stop spam
> final_spam_destiny => D_PASS,
> banned_filename_maps => ['BLOCK_EXE'],
> };
'
Yes Gary, now works perfectly. :D
> You have to place these after where $banned_filename_re is set.
Mmmm... I placed it before, but I suppose the file is interpreted in
order, so if any $ it's not defined before, it doesn't work.
Maybe I'll put the $banned_filename_re definition in header in order to
be more clear.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
