On 18/08/2013 12:22, Zhang Huangbin wrote:
Dear developer,I'm confused with how priority works. The wiki page[1] says "Priorities are processed in an ascending fashion, this means that 0 will be processed before 1, 10 before 20 etc." ok, i know it processes in ascending order, but when will it stop? that's what confuses me. Let's say we have an incoming email which match 2 policies: priority=3 (Default Inbound) will apply greylisting on it and priority=100 (my custom rule, disable greylisting for certain local domains/users) will not apply greylisting for this incoming email. As wiki mentioned, Cluebringer will process rule priority=0 first, then rule priority=100. But will it stop at first matched rule (proirity=0, apply greylisting)? Or last one (priority=100, no greylisting)? I checked SQL queries generated by Cluebringer, seems it queries all matched policies, but the last one (priority=100, no greylisting) is used. I hope developer can explain this and make it clear in wiki page[1]. Thanks very much. [1] Wiki page: http://wiki.policyd.org/policies#priorities
You choose what will happen. Some modules allow inheriting values from previously matched policies. Some will override (ACL) and some allow stopping there (rate limits) using the "Stop processing" flag.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
