I have upgraded to V1.5.1.2(0.0.14) and the problem persists - however I have I think found an acceptable workaround.
Taking DNSBL as the example, although baysien checking seems to be effected the same way if ValidateRBL is set to 1 - Block, then test mode is also selected (so they are blocked, then passed as testmode) if ValidateRBL is set to 3 - Score, then they are scored, later blocked because of their score and crucially test mode is not invoked. I for one can live with that, scoring is not a bad way to handle it, but there remains an underlying problem - I dont know how this will effect Early DNSBL blocking for instance. I can rest easier now that I can get the scored messages out of peoples inboxes, and I thank everyone for their help on this - I know (a little) more now about the inner workings of ASSP Kind Regards Kevin -----Original Message----- From: Kevin Lawry [mailto:[email protected]] Sent: 09 April 2009 09:36 To: ASSP development mailing list Subject: Re: [Assp-test] V1.5.1.2(0.0.09) DNSBL Test mode et al Thanks I don't knowingly have another test mode set - I'll double check I am about to install 0.0.14 - is that the current latest version? K -----Original Message----- From: Fritz Borgstedt [mailto:[email protected]] Sent: 09 April 2009 09:23 To: ASSP development mailing list Subject: Re: [Assp-test] V1.5.1.2(0.0.09) DNSBL Test mode et al After looking again into the code I saw a bug. You must have another testmode set. Please load the newest version. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
