azurIt wrote:

>i think i found a bug in quotas when using SASL username for 
>tracking. When there's no SASL username (no user is logged), 
>tracking is enforced anyway with empty SASL. This is not very good 
>behaivor because ANYONE who is sending e-mails to you is not logged. 
>policyd should ignore tracking when there's empty SASL username.

I'd say this isn't a bug - an empty username is still a unique value. 
You should arrange your policies so that you aren't tracking quota on 
SASL username for incoming mail.

Some modules apply all matching policies rather than the highest 
priority only. So I figured out ages ago that the best technique to 
use is to make all your policies mutually exclusive so that a message 
will match only one and there can be no confusion over which modules 
will do what. IN particular, the quota module applies the quota for 
all matching policies - not the quota for the highest priority 
matching policy.

So, I have a policy for inbound mail, with a member specification of 
"!$*,!%internal_ips" for source. This matches where there is no SASL 
username, and it's not an internal address (actually only 127.0.0.1).

Then for outbound, I have two policies : 
"$*,!%hi-vol-sasl,!%Our_Network" and "%hi-vol-sasl". hi-vol-sasl is a 
group into which I can put the SASL username of users permitted to 
send a higher level of mail - and by excluding this group from other 
policies, it avoids any conflict there.

I have another policy for internally generated mail (ie from our own 
servers) with members of "%Our_Network,$*,!%hi-vol-sasl".

So that's 4 different policies, all mutually exclusive - and you can 
configure the modules for each policy safe in the knowledge that you 
won't have problems with multiple matches.

-- 
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

Reply via email to