> Apologies if this seems obvious, I've looked through the archives for > the last few months and not found anything that answered my question. > > I'm trying to setup a new server with policyd (V2), but I'm > struggling to get my head round the relationship between the various > bits of the setup. I can see how each individual bit works (I think), > but I'm just missing how they hang together. > > So assuming I'm processing an inbound message, I've got Policies, > Groups, and the various checks (eg Greylisting and Amavis). > > Is it a case of checking each policy in turn until I find a group > that matches the message and is attached to that policy, and then > running the checks that inherit from that policy ? So I have to > define groups until I get messages to match a policy, and then > configure the checks I want done under that policy ? > Ok .... a message matches a policy.
A policy can contain various specifiers, like [email protected], @example.org, 192.168.0.0/24 or %group .... where %group is a group. Group members are matched a OR b OR c OR d, where a b c are members of that group. Policy members are matched a AND b AND c AND d, where a b c d are members of that policy. You then attach a feature to a policy, wither an ACL, greylisting or maybe quotas. Regards Nigel
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
