> I've been playing with this on and off (mostly off) for a bit. I've > got pre-acceptance filtering going with amavisd-milter, but I'm still > unclear exactly which policies/actions are applied. > > Using v2.0.7 > > Supposing a message matches the pre-requisites for policies A, B, and > D, but not C - and that A, B, C, D are in increasing priority. > > If I have an action (eg Greylisting) for each of A, B, and D - > exactly what values will be used ? I know that anything explicitly > set in D will be used, but if I set "inherit", is the inherited value > from A or B ? > The one with the highest priority.
> If I have an action that matches A and B, but not D, then B is used ? > Depends on the module, some modules allow more than one policy to match allowing you to do different things. ie. A system limit on number of messages vs. a domain limit vs. a user limit > Since policy C is not matched, nothing I set in it will affect > processing of this message ? > Correct. > Lastly, is there logging that clearly shows which policies have been > matched, and which actions are being applied ? Log level 3 shows each > match element of each policy and whether it's been matched - but then > I have to work out how that translates into actions performed. Level > 4 is just too verbose to be useful. > Turn on "policie,modules" logging on highest debug level, that should give you a good idea of what policyd is doing. That together with the log messages in the mail log which will give you info on what is done with a message, if anything. -N _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
