Nigel Kukard wrote: > Good question... > > $server->log(LOG_WARN,"[QUOTAS] Unknown key > specification in TrackSenderIP"); > > > Could you find that line in the .pm module, then change it to ... > $server->log(LOG_WARN,"[QUOTAS] Unknown key > specification in TrackSenderIP '$spec'"); > > Lets see what the error message says then. > > -N >
Hi Nigel, [2009/07/16-10:37:30 - 14246] [CORE] INFO: Starting "1" children [2009/07/16-10:37:30 - 14255] [CORE] INFO: 2009/07/16-10:37:30 CONNECT TCP Peer: "127.0.0.1:43258" Local: "127.0.0.1:10031" [2009/07/16-10:37:30 - 14292] [CORE] DEBUG: Child Preforked (14292) [2009/07/16-10:37:30 - 14292] [CBPOLICYD] DEBUG: Starting up caching engine [2009/07/16-10:37:30 - 14255] [POLICIES] INFO: [ID:8/Name:swift_IP]: Source matching result: matched=1 [2009/07/16-10:37:30 - 14255] [QUOTAS] WARNING: Unknown key specification in TrackSenderIP '0.0.0.0/0' [2009/07/16-10:37:30 - 14255] [QUOTAS] ERROR: No key found for quota ID '3' And I just wanted to ask if it's possible to limit messages per each IP to for example 500 per day using policyd ? Doesn't 0.0.0.0/0 mean 192.168.0.1 and 10.0.0.1 in the same time ? It must be unique. 192.168.0.1 must be allowed to accept 500 messages and 10.0.0.1 too and other too. The problem is I'm going to run it on the smart host where I've got 220 allowed full class C and 800 smaller classes or singular IPs. The best way would be if I could limit it by a one simple rule for example 0.0.0.0/0 means to track IP address which is unique. It's important. I hope you know what I mean. Regards, Jarek _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
