On 2013-08-28 12:24, Nigel Kukard wrote:
On 28/08/2013 16:04, Jeff McKeon wrote:
On 2013-08-28 11:24, Jeff McKeon wrote:
On 2013-08-28 10:18, Nigel Kukard wrote:
On 28/08/2013 13:46, Jeff McKeon wrote:
Hello,

I've got a new iRedmail installation on OpenSUSE 12.3 that uses mysql.

the problem I have is that cluebringer_autowhitelist table is not populating as I believe it should (unless I am understanding things wrong).

I set up a test script on another server to send emails to my mail server every minute or so, same email, same to/from etc..

my cluebringer.greylisting table has the following settings for autowhitelist:

AutoWhitelistCount = 5
AutoWhitelistPercentage = 50

in the clubringer.greylisting_tracking table I have a record from the test emails that has:

Tries= 8
count= 750

yet no record has appeared in the greylisting_autowhitelist table as I expect it should have.

Doe anyone have any suggestions on where to look for this issue?


Best bet, enable full debugging of all modules and watch the output to
see if the module is being run.

The autowhitelist is populated as per the wiki, when a certain number of triplets is seen and a % of that is authenticated the entry should
be added with the specified timeout.

-N


ok, debugging on

deleted the greylisting_tracking record for the email address my test is coming from. ran the email script again to pump out emails every minute or so...

AutoWhitelistCount = 5
AutoWhitelistPercentage = 50

greylisting_tracking record info:

Tries: 8
Count: 24

still no record in greylisting_autowhitelist

watched cbpolicyd.log

all I see is this: (<test server> substituted for actual server name)

[2013/08/28-11:51:24 - 28671] [CBPOLICYD] INFO: Got request #67 (pipelined) [2013/08/28-11:51:45 - 28671] [CBPOLICYD] INFO: Got request #68 (pipelined) [2013/08/28-11:51:45 - 28671] [CHECKHELO] DEBUG: Updated timestamp for helo '<test server>' from address '66.246.168.21' [2013/08/28-11:51:45 - 28671] [GREYLISTING] DEBUG: Updated greylisting triplet ('SenderIP:66.246.168.0/24','root@<test server>','[email protected]') @ 1377705105 [2013/08/28-11:51:46 - 28671] [CBPOLICYD] INFO: Got request #69 (pipelined) [2013/08/28-11:51:54 - 28671] [CBPOLICYD] INFO: Got request #70 (pipelined) [2013/08/28-11:51:54 - 28671] [CHECKHELO] DEBUG: Updated timestamp for helo '<test server>' from address '66.246.168.21' [2013/08/28-11:51:54 - 28671] [GREYLISTING] DEBUG: Updated greylisting triplet ('SenderIP:66.246.168.0/24','root@o<test server>','[email protected]') @ 1377705114 [2013/08/28-11:51:54 - 28671] [CBPOLICYD] INFO: Got request #71 (pipelined) [2013/08/28-11:52:15 - 28671] [CBPOLICYD] INFO: Got request #72 (pipelined) [2013/08/28-11:52:15 - 28671] [CHECKHELO] DEBUG: Updated timestamp for helo '<test server>' from address '66.246.168.21' [2013/08/28-11:52:15 - 28671] [GREYLISTING] DEBUG: Updated greylisting triplet ('SenderIP:66.246.168.0/24','root@<test server>','[email protected]') @ 1377705135 [2013/08/28-11:52:16 - 28671] [CBPOLICYD] INFO: Got request #73 (pipelined) [2013/08/28-11:52:25 - 28671] [CBPOLICYD] INFO: Got request #74 (pipelined) [2013/08/28-11:52:25 - 28671] [CHECKHELO] DEBUG: Updated timestamp for helo '<test server>' from address '66.246.168.21' [2013/08/28-11:52:25 - 28671] [GREYLISTING] DEBUG: Updated greylisting triplet ('SenderIP:66.246.168.0/24','root@<test server>','[email protected]') @ 1377705145 [2013/08/28-11:52:25 - 28671] [CBPOLICYD] INFO: Got request #75 (pipelined) [2013/08/28-11:52:29 - 28671] [CBPOLICYD] WARNING: Client closed connection => Peer: 127.0.0.1:60837, Local: 127.0.0.1:10031
[2013/08/28-11:52:29 - 28668] [CORE] INFO: Killing "1" children
[2013/08/28-11:52:29 - 28684] [CBPOLICYD] DEBUG: Shutting down caching engine (28684)
[2013/08/28-11:52:45 - 28668] [CORE] INFO: Starting "1" children
[2013/08/28-11:52:45 - 28673] [CORE] INFO: 2013/08/28-11:52:45 CONNECT TCP Peer: "127.0.0.1:33196" Local: "127.0.0.1:10031"
[2013/08/28-11:52:45 - 30048] [CORE] DEBUG: Child Preforked (30048)
[2013/08/28-11:52:45 - 30048] [CBPOLICYD] DEBUG: Starting up caching engine
[2013/08/28-11:52:46 - 28673] [CBPOLICYD] INFO: Got request #1
[2013/08/28-11:52:46 - 28673] [CHECKHELO] DEBUG: Updated timestamp for helo '<test server>' from address '66.246.168.21' [2013/08/28-11:52:46 - 28673] [GREYLISTING] DEBUG: Updated greylisting triplet ('SenderIP:66.246.168.0/24','root@<test server>','[email protected]') @ 1377705165



no mention of cluebringer_autowhitelist at all....

it should have tripped by now i would have thought.. am I wrong?


Same sender, same sending IP same recipient. This is counted as 1
triplet if I'm reading the above right.



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

ok, so them maybe I am mis-understanding.. yes it's the same server, same sender and recipient.. why is that counted as only one triplet? Shouldn't it auto whitelist if the same sender, server send enough approved emails? if not, what is the logic for auto whitelisting?

--
Best Regards,

Jeff

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

Reply via email to