> > So it evaluates each policy, and creates a list of policies that have > at least one member that matches. Then picks the highest priority > policy, then executes each feature. > > This last step, does it execute them in turn until one say YES (with > an inferred reject at the end), or until one says NO (with an > inferred accept at the end), or something else ? >
V2 also has a 'stop here' feature which one can apply to a policy, if you don't want to traverse the priorities, but otherwise, i believe it'll ascend all priorities before deciding yes or no. If you don't match a policy it will default to DUNNO iirc. > Another question. Am I right in thinking that the Amavis test can't > add any headers to the email ? IIRC I read somewhere that this is a > limitation of the Postfix policy protocol. Postfix policy protocol can prepend a header, some people have suggested you can add more by using \r\n to separate, although i've not personally tested this. As for the amavis policy bank, i don't personally use it in policyd so Nigel is in a better position to answer, but i believe it doesn't make any changes. > -- > Simon Hobson Jon Duggan _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
