On October 6, 2014 3:03:30 PM jdime abuse <jdimeab...@gmail.com> wrote:
I have been seeing some issues with bayes detection from base64 strings within attachments causing false positives.
Train more data then, bayes needs more data to prevent it
Example: Oct 6 09:02:14.374 [15869] dbg: bayes: token 'H4f' => 0.999971186828264 Oct 6 09:02:14.374 [15869] dbg: bayes: token 'wx2' => 0.999968644662127 Oct 6 09:02:14.374 [15869] dbg: bayes: token 'z4f' => 0.999968502147581 Oct 6 09:02:14.378 [15869] dbg: bayes: token '0vf' => 0.999966604823748
Above is pretty normal for how bayes works
Is there a solution to prevent triggering bayes from the base64 data in an attachment? It was my impression that attachments should not trigger bayes data, but it seems that it is parsing it as text rather than an attachment.
Dokumentation is in perldoc Mail::SpamAssassin::Conf perldoc Mail::SpamAssassin::Plugin::Bayes If not dokumented its not supported
This is with SpamAssassin v3.3.
While 3.4 is now stable
