Hi Mark,
I'm using gentoo. It's the 2.3.3-r2 version from gentoo, with the patch
for LDAP amavisBannedRuleNames applied. I did a diff against 2.3.3:
diff -urN /usr/sbin/amavisd amavisd
--- /usr/sbin/amavisd 2006-02-02 13:59:11.0 -0200
+++ amavisd 2005-08-21 20:46:15.0 -03
Hi all,
I'm having problems to make banned_filename_maps and banned_rules work.
I'm using:
%banned_rules = (
'DEFAULT' => $banned_filename_re
);
@banned_filename_maps = ( { '.' => 'DEFAULT' } );
Or
@banned_filename_maps = ( 'DEFAULT' );
This allows a file calle
Hi Mark,
Right, the truth is that I don't want exactly remove the banned parts,
but substitute the banned part with a .txt telling the user that
something was banned from the message and why.
Somebody told me that eTrust Antivirus, associated with Exchange, does that.
IMHO, it's a good featu
It's possible to set D_PASS to $final_banned_destiny, but remove the
banned parts from the message ?
Kind regards,
Aury
---
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Cert
Hi all,
I found the same bug that Jerome Schell reported some days ago.
Looking at the sources in 2.3.3, in line 5293:
if (!exists($banned_rules{$n})) {
do_log(2,"INFO: unknown banned table name $n,
recip=$recip");
} elsif (!defined($banned_rules{$n}))
Anybody can help me on this issue ?
Thanks.
Aury Fink Filho wrote:
Hi all,
I found the same bug that Jerome Schell reported some days ago about
LDAP per recipient.
Looking at the sources in 2.3.3, in line 5293:
if (!exists($banned_rules{$n})) {
do_log(2,"
T=dat",
matching_key="(constant:DEFAULT)"
Sep 14 13:16:22 tatooine amavis[669]: (00669-01) banned check: any=1,
all=Y (1)
My amavisd.conf
@banned_filename_maps = ( 'DEFAULT' );
%banned_rules = ('DEFAULT' => $banned_filename_re);
