This email can be ignored. The .conf had SENDERMSGLIMIT=512 and users getting caught were the heavy ones.
I guess the limit in the conf overrides the '0' placed in sql? Many thanks Jon Duggan Nuco Technologies Ltd [EMAIL PROTECTED] Tel. 0870 165 1300 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Duggan Sent: 10 October 2007 13:39 To: policyd-users@lists.sourceforge.net Subject: [policyd-users] Policy rejection behaviour Hi All, We're using policyd for sasl sender throttling. It's working great and helps give us a good break down of monthly usage etc Occasionally we get the odd user who gets rejected with quota exceeded even though they're either; a) way below the quotas b) sometimes have 0 set for quota (none) I've attached a debug=2 output for the specific email that was rejected. (The one thing I notice that's strange is that we're throttling by sasl_username, the last function in the debug output is updating _abuse_cur=1 where _from=(ENVELOPE SENDER), When infact _from == the sasl_username (astraseal) (we've added a column called _passwd and are authenticating against this). Can anyone shed some light on this? Or perhaps give me a bump at where i should be looking Many thanks Jon Duggan Nuco Technologies Ltd [EMAIL PROTECTED] Tel. 0870 165 1300 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
