Looks like I might have solved my own issue. The source of %internal_ips, %internal_domains is shown in several places and is the default value set up in the installation. But when I break that into two members for the default outbound policy and that appears to work. The two members are:
%internal_ips to !%internal_domains %intenal_domains to !%internal_domains But should I make that first member to be: %internal_ips to !%internal_ips I don’t know if that makes a significant difference or not. ~ Rob On Apr 11, 2014, at 10:42 AM, Rob Tanner <[email protected]<mailto:[email protected]>> wrote: I was using the default policy (any to any) and that world fine except when a user send mail to one or more of our internal mailing lists in a single message because that could generate anywhere from several hundred to a couple thousand messages to internal recipients. Since they are mostly all internal destinations except for the few who might have set up forwarding to an off-campus email address, I thought that default outbound policy might be the better choice when doing quotas. Unfortunately, it seems to be failing to catch off-campus messages. The policy has one member which was setup by default, %internal_ips, %internal_domains to !%internal_domains. Under policy groups, internal_domains is defined as @linfield.edu<http://linfield.edu/> and internal_ips is defined as 10.0.0.0/8. When I disable the default outbound policy (priority 2), the default policy has the next highest priority (5) and then messages are counted and quotas applied. So, what am I missing? Thanks Rob Tanner UNIX Services Manager Linfield College, McMinnville Oregon ITS will never ask you for your password. Please don’t share yours with anyone!
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
