The whitelist (actually, whiteSenderBaseRE for "yahoo.com") only contributed -15 to the message score, but each of the HMM and Bayes contributed +46 and +43 respectively to the score. Along with the bombRE fo "Precedence: bulk" adding another +10 to the score, and the SPF match contibuting -1 to the score, you end up with:
-15 + 46 + 43 +10 - 1 = 83. And, you'll see: X-Assp-Spam-Reason: MessageScore 82, limit 45 (How it thinks the total is 82 and not 83 doesn't make sense to me - probably an off-by-one bug somewhere in ASSP.) Since 82 > 45, the message is marked as spam. My guess is you have DoOrgWhiting set to "score" and not "whiting" and sworgValencePB set to -15 (the default is -25). Eithe change DoOrgWhiting to "whiting" or maybe set sworgValencePB to something like -100, if you want matches in your whiteSenderBase to prevail over the HMM/Bayes filter. On 4/15/16 2:16 PM, PlusPlus Internet Solutions LLC wrote: > Thanx! Im aware of it...my question is why is marked as spam if the > sender email address is on whitelist? -- Dossy Shiobara | "He realized the fastest way to change [email protected] | is to laugh at your own folly -- then you http://panoptic.com/ | can let go and quickly move on." (p. 70) * WordPress * jQuery * MySQL * Security * Business Continuity * ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
