Hi,
i am very happy with 1.3.1, so i use it on my stable server. 1.3.3.1 does not
work so good for me so i will look forward to 1.3.3.3, but i prefer a version
that is stable for a few month. 1.3.3.2 is installed on a testing enviroment,
but i do not have real data at this time.
Using message scoring PB and corresponding tests are set to 3, everything works
fine for most mails with one expetion. When we reach low threshold eraly it
seems that later/further test will be skipped. Example we hit the low-Score
during dns-checks and bayes and ClamAV will not be done. The message is also
bayesian spam, so if these tests will also be done Message Limit grows from LOW
to HIGH and spam will be deleted and not bother my users.
Is this wanted/standard behavior, or did i miss something in my configuration?
If standard behavior, will newer versions also skip tests after low threshold?
Aug-22-07
12:07:50 id-77772691 217.91.49.222 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
Received-SPF: neutral (he.feron.de: 217.91.49.222 is neither permitted nor
denied by domain of [EMAIL PROTECTED]) client-ip=217.91.49.222;
[EMAIL PROTECTED]; helo=pd95b31de.dip0.t-ipconnect.de;
Aug-22-07
12:07:50 Commencing DNSBL checks on 217.91.49.222
Aug-22-07
12:07:56 Completed DNSBL checks on 217.91.49.222
Aug-22-07
12:07:56 id-77772691 217.91.49.222 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
Received-RBL: neutral (ix.dnsbl.manitu.net->127.0.0.2; )
Aug-22-07
12:07:56 id-77772691 217.91.49.222 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
Received-URIBL: pass
Aug-22-07
12:07:56 id-77772691 217.91.49.222 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
passing if safe because testmode, otherwise Message Scoring: 45 > 40 (low
threshold)
Aug-22-07
12:07:56 id-77772691 217.91.49.222 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
spam determined to be safe, passing on to recipient
Nie_mehr_zu_frueh_kommen_your_splits_Best_of_all_i -> ./spam/2414.eml
Aug-22-07
12:08:47 id-77773273 212.37.192.53 <[EMAIL PROTECTED]> renewing
tuplet: (212.37.192.0,specialchem.com) age: 2m 12s
Aug-22-07
12:08:47 id-77773273 212.37.192.53 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
scoring + 5: blacklisted HELO: 'smtp1.internet-fr.net'
Aug-22-07
12:08:48 id-77773273 212.37.192.53 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
Received-SPF: neutral (he.feron.de: local policy) client-ip=212.37.192.53;
[EMAIL PROTECTED]; helo=smtp1.internet-fr.net;
Aug-22-07
12:08:48 Commencing DNSBL checks on 212.37.192.53
Aug-22-07
12:08:48 Completed DNSBL checks on 212.37.192.53
Aug-22-07
12:08:48 id-77773273 212.37.192.53 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
Received-RBL: pass
Aug-22-07
12:08:48 id-77773273 212.37.192.53 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
Received-URIBL: pass
Aug-22-07
12:08:48 id-77773273 212.37.192.53 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
ClamAV: scanning 17290 bytes done OK
Aug-22-07
12:08:48 id-77773273 212.37.192.53 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
Bayesian Check Prob: 1.00000 => spam
Aug-22-07
12:08:48 id-77773273 212.37.192.53 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
passing if safe because testmode, otherwise Message Scoring: 50 > 40 (low
threshold)
Aug-22-07
12:08:48 id-77773273 212.37.192.53 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
spam determined to be safe, passing on to recipient -> ./spam/2467.eml
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s
mit dem neuen Yahoo! Mail. www.yahoo.de/mail
-------------------------------------------------------------------------
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/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
