Hi, We are successfully using PolicyD with SASLuser-based quota and accounting... no problems.
However - I'm now trying to setup a policy which is IP-based (so we quota via a list of IP addresses instead of SASL authenticating). I need to quota (and account) by an aggregate of a number of IP addresses (150 of them), so have set up a PolicyMembersGroup with those IP addresses in, and created a Policy, Quota and Limit that are all linked. The Quota tracks the Policy. However - as soon as I enable the Policy, the number of cbpolicyd processes on the Server *rockets* - from about 6 to over 40... What could the reason for this be? Obviously adding new policy items will increase the work required by cbpolicyd - but we have thousands of SASLuser entries in the quota and tracking, and I wouldn't have thought this should have had *that* much impact. Version is 2.1.0.a and we're running with postfix 2.5.1 Thanks in advance! -Craig
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Users mailing list Users@lists.policyd.org http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org