Hi all,
I am newbe with cluebringer.

The scenario is: two policy (60 and 300 msg/hour), priority for 300 is
lower than 60.

60 policy match any address, 300 match some specific address like
[email protected].

mysql> select id,PolicyID,Name from quotas where disabled=0;
*************************** 1. row ***************************
      id: 3
PolicyID: 6
    Name: 60 msg/hour
*************************** 2. row ***************************
      id: 4
PolicyID: 7
    Name: 300 msg/hour

I want that my user [email protected] below to 300 policy can send 300 msg.

The result:

for each message send, postfix update each two policy (I suspected the
problem born here)

Oct 31 15:12:01 smtp cbpolicyd[14780]: module=Quotas, mode=update,
host=5.150.XX.XX, helo=[192.168.9.7], [email protected],
[email protected], reason=quota_update, policy=7, quota=4, limit=5,
track=Sender:[email protected], counter=MessageCount, quota=61/300 (20.3%)

Oct 31 15:12:01 smtp cbpolicyd[14780]: module=Quotas, mode=update,
host=5.150.XX.XX, helo=[192.168.9.7], [email protected],
[email protected], reason=quota_update, policy=6, quota=3, limit=4,
track=Sender:[email protected], counter=MessageCount, quota=61/60 (101.6%)

Postfix match the first policy and user cannot send more than 60 msg, I
wish it can send 300 msg, I am confused why cluebringer want use all
policy and not exit after the first match (like iptables works).

ii  postfix-cluebringer                2.0.10-1
all          anti-spam plugin for Postfix

This confirmed from quotas_tracking table

mysql> select * from quotas_tracking order by Counter desc limit 10;
+----------------+-------------------------------------------+------------+---------+
| QuotasLimitsID | TrackKey                                  |
LastUpdate | Counter |
+----------------+-------------------------------------------+------------+---------+
|              4 | Sender:[email protected]                 | 1477923121 |
60.9637 |
|              5 | Sender:[email protected]                 | 1477923121 |
60.9637 |

I tried to reverse priority policy, but the result is the same.

Should I use LastAccounting options available from 348+ and v2.1.x

Oct 31 15:12:11 smtp cbpolicyd[14861]: module=Quotas, action=defer,
host=5.150.XX.XX, helo=[192.168.9.7], [email protected],
[email protected], reason=quota_match, policy=6, quota=3, limit=4,
track=Sender:[email protected], counter=MessageCount, quota=62/60 (103.0%)

My wish is that user match policy 300 msg can send really 300 msg and
not rejected after first 60 ;-)

TIA

Alessandro - Lota

PS please reply to my address in CC, I am not subscribe in this list yet

_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org

Reply via email to