> [UPDATE]
>
> 2009/5/15 Guy <[email protected]>:
>
>> I'm trying to have two policies, each with a different quota attached.
>> A message matching both policies will have both quotas applied.
>> Is there any chance of Inheritance being included at some stage for
>> Quotas like it is in Greylisting?
>> I have similar multilevel greylisting policies which work perfectly
>> because of the option to inherit.
>>
>
> After thinking it through a bit more I realised that inheritance
> wouldn't solve the problem I'm having with quotas.
>
> I've currently got a permissive quota set on a policy with source set
> to a group of SASL usernames. I then have a more restrictive quota
> with source set to anything not in the group of SASL usernames. This
> works fine except for one thing. Some messages arriving from remote
> mail servers are being tracked with a blank SASL username. I get lines
> like the one below in my logs:
>
> May 16 23:50:38 server01 cbpolicyd[8745]: module=Quotas, mode=update,
> host=134.158.91.23, helo=as3.lal.in2p3.fr,
> [email protected], [email protected],
> reason=quota_update, policy=2, quota=4, limit=5, track=SASLUsername:,
> counter=MessageCount, quota=30/10000 (0.3%)
>
> I know all SASL usernames can be listed with $*, but is there some way
> to match a blank SASL username so I can exclude it from the source
> list for the policy that uses the restrictive quota? Or is there some
> other way of doing this that I'm missing?
>
From: http://www.policyd.org/tiki-index.php?page=Policies %26
Groups&structure=Documentation
$sasl_username
This will match a SASL username. You can also use $* to match any SASL
username and $- to match no SASL username.
Regards
Nigel
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
