On Sat, Jan 14, 2006 at 01:26:18AM +0100, Mark Martinec wrote:
> Brian,
>
> > I would like to exclude a recipient from my site-wide banned rules,
> > yet be subject to another set of banned rules which is slightly
> > different from the site-wide one. Is this possible?
> > In my specific case, these users need to receive a certain file type,
> > yet everyone else shouldnt be receiving this type.I would like a
> > maintainable method of creating such exceptions.
>
> It should be possible to have per-recipient banning rules.
> See release notes of 2.3.0 where it was first introduced.
>
> > I use LDAP, and the attribute 'amavisBannedRuleNames' has me believing
> > I can create a named set of banned rules and reference them in the
> > users lookup table. Much like having different behavior in a policy
> > bank. Am I misinterpreting this attribute? If not, how can I go about
> > setting this up?
>
> It has indeed been reported before I believe that this does not work with
> LDAP, but I never got around to locate and fix the problem, mostly because
> I'm not running LDAP myself. The bug should not be that deep, I would
> appreciate help here from interested parties.
I've submitted and Mark has incorporated a patch to fix this issue.
My initial post of it got stuck in moderation, for the benefit of those
who want to try it below is the patch to 'amavisd'. Its undoubtly mangled
but you should get the idea of what changed, basically the attribute was
change from multi-valued to single-valued and is a comma-seperated list
of rule names (same as with SQL lookups. The full patch also includes,
schema, documentation updates as well.
diff -urN amavisd-new-2.3.3.orig/amavisd amavisd-new-2.3.3/amavisd
--- amavisd-new-2.3.3.orig/amavisd Wed Jan 25 21:38:12 2006
+++ amavisd-new-2.3.3/amavisd Wed Jan 25 21:45:22 2006
@@ -6675,7 +6675,7 @@
unshift(@Amavis::Conf::spam_admin_maps, $lf->('amavisSpamAdmin',
'S-'));
unshift(@Amavis::Conf::banned_admin_maps, $lf->('amavisBannedAdmin
', 'S-'));
unshift(@Amavis::Conf::bad_header_admin_maps, $lf->('amavisBadHeaderAd
min', 'S-'));
- unshift(@Amavis::Conf::banned_filename_maps, $lf->('amavisBannedRuleN
ames', 'L-'));
+ unshift(@Amavis::Conf::banned_filename_maps, $lf->('amavisBannedRuleN
ames', 'S-'));
section_time('ldap-prepare');
}
if (defined $sql_policy && !$implicit_maps_inserted) {
@@ -10743,9 +10743,7 @@
amavisBadHeaderAdmin amavisBannedRuleNames
);
- @mv_ldap_attrs = qw(amavisBlacklistSender amavisWhitelistSender
- amavisBannedRuleNames
- );
+ @mv_ldap_attrs = qw(amavisBlacklistSender amavisWhitelistSender);
}
sub new {
--
Nobody cares if you can't dance well. Just get up and dance.
Mike Hall,
System Admin - Rock Island Communications <[EMAIL PROTECTED]>
System Admin - riverside.org, ssdd.org <[EMAIL PROTECTED]>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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/
