Hi,
I am playing around with the per-user banned files settings
(amavisd-new-2.3.3) and would like some clarification on
one point.
Consider the following in the policy table:
+--------------------+------------------+
| policy_name | banned_rulenames |
+--------------------+------------------+
| [EMAIL PROTECTED] | foobar_ruleset |
| @example.com | example_ruleset |
| @. | default_ruleset |
+--------------------+------------------+
and the following in amavisd.conf:
#
# The actual rulesets don't matter for this example
#
$foobar_rs = new_RE(.....);
$example_rs = new_RE(.....);
$default_rs = new_RE(.....);
$allowall_rs = new_RE(.....); # ruleset to allow everything
%banned_rules = ('foobar_ruleset' => $foobar_rs,
'example_ruleset' => $example_rs,
'allowall_ruleset' => $allowall_rs,
'default_ruleset' => $default_rs,
'DEFAULT' => $banned_filename_re);
When amavisd performs its lookup for banned_rulenames for
'[EMAIL PROTECTED]' it also lookups the '@example.com'
and '@.' policies and sorts by priority resulting in all 3
rulesets been checked in the order foobar_ruleset,
example_ruleset, default_ruleset.
I would have thought that amavisd would just use the ruleset(s)
for the highest priority query (ie '[EMAIL PROTECTED]').
This way, for example, one could define a fairly restrictive
policy for the domain, and a more relaxed one for certain users
if required. Now, I realise that I can workaround this restriction
by appending an allowall_ruleset (which basically would allow
everything) to the banned_rulenames for foobar. However, I'm just
curious why amavisd doesn't just use the highest priority
banned_rulenames only?
- Sean
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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/