|Main Archive Page > Month Archives > spamassassin-dev archives|
--- Comment #19 from Karsten BrÃ¤ckelmann <firstname.lastname@example.org> 2011-10-27 02:05:06 UTC ---
(In reply to comment #18)
> I think in the absence of enough other rules to accumulate to push an email
> over the threshold, it makes plenty of sense to use a blacklist with a single
> rule that alone is over the threshold. Not an ideal situation, but if it's
> your only way to effectively block spam, and you can do it without causing a
> problematic false positive rate, go for it.
If $admin does it on his server, and knows the blacklist, sure. If you are
publishing rules for others, your responsibilities are much greater.
Also, again, this is about SCORING, thus pushing the score above the SA default
threshold of 5. Aiming at 15 or 20 is something different.
classified spam != SMTP reject
> Lemat changing the status of this bug back to "fixed" when posting comment #13
> was weird.
Dunno how that happened, but keeping a bug open in the browser and reloading
(without shift) is prone to keep the drop-down boxes' state -- and thus
reverting changes with the next comment.
-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.