I've got BayesAfterHMM set to 0.3-0.7 Sometimes, I see bayesian run even though HMM scores a probability of 1.00000. Is that right? Could this be happening because HMM doesn't have enough hits? If that's the case can we tell ASSP to ignore HMM it's unsure and use Bayesian INSTEAD (only) in these cases?
Sorry for the HMM questions, but the concept's new to me. Clearly my databases aren't quite perfect, but I was hoping that senderbase would bring the HMM score down enough to pass it. However, with Bayesian running too, we exceed the max and it's blocked. X-ASSP-Message-Score: -35 (White Organization/Domain 'RESPONSYS') X-ASSP-IP-Score: -34 (White Organization/Domain 'RESPONSYS') X-ASSP-Detected-URI: rsys2.com(1), e.hotwire.com(1), hotwire.com(7) X-ASSP-Message-Score: 49 (HMM Probability: 1.0000) X-ASSP-IP-Score: 49 (HMM Probability: 1.0000) X-ASSP-Message-Score: 49 (Bayesian Probability: 1.00000) X-ASSP-IP-Score: 49 (Bayesian Probability: 1.00000) X-ASSP-Spam-Prob: 1.00000 X-ASSP-HMM-Spam-Prob: 1.00000 X-ASSP-Tag: MessageLimit X-ASSP-Spam-Reason: MessageScore 63, limit 50 X-ASSP-Message-Totalscore: 63 ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
