https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6486
Karsten Bräckelmann <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID --- Comment #5 from Karsten Bräckelmann <[email protected]> 2010-09-15 08:16:01 UTC --- Thanks for getting back to this and the confirmation. :) However, as far as this bugtracker (and a SA bug report) is concerned, this report is INVALID (read: there is no SA bug), even though the "status" of your particular issue is FIXED now. (For future searches, resolution fixed means, a bug indeed has been corrected in the source.) Re-setting the Resolution. (In reply to comment #3) > Karsten, thank you for the assistance. Indeed each mail is fed to SA twice - > from /etc/procmailrc, the mail is filtered to spamassassin and spamc that > gives > the double score. Funny enough, some junk mail get only a single score. Does > this mean it was identified as SPAM by one engine and not the other? That probably indicates the message has exceeded a (very low?) size threshold, so 'spamc' won't scan it while 'spamassassin' does. Or any other rule in your procmail recipes prevented the second scan. It is almost always preferable to use spamc/spamd in production, rather than the plain 'spamassassin' script -- the latter comes with a severe per-message startup cost, unlike the daemon and light-weight client. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
