R M Waters wrote: >I had not known that I could create a policy other than >outbound/inbound/all. I had been thinking "firewall". >I was able to create a new policy to affect individual domains (or >groups of domains).
I would suggest you also make your policies mutually exclusive. I learned the hard way that while the documentation for some modules states that restrictions are applied in an "inherit and override" manner - for some, all matching policies are applied. If you have more than one or two domains, then it may be worth defining 'classes' of users/domains rather than doing rules for them individually. Eg, have a policy for medium traffic users, and another for high traffic users - matching on groups by domain name in each case. Then redefine your default in and out policies to exclude members of these groups. Ie : default : not a member of medium-traffic-domains and not a member of high-traffic-domains medium : member of medium-traffic-domains high : member of high-traffic-domains Then, when a new domain comes along needing a bump in their quota, you can just add it to one or other of the groups. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
