https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6552
--- Comment #11 from Karsten Bräckelmann <[email protected]> 2011-03-19 01:17:20 EDT --- (In reply to comment #10) > I know I could fix our versions of SpamAssassin, but I'm wondering when this > fix is going to go out to everyone, as we have people complaining to us about > mail getting marked as spam from mailservers we don't control. > > If it's fixed for SA 3.3.x, how come mailservers are still marking this as > spam > when they have v.3.3.1? Details escape me, and I am too lazy to dig into the history, but yeah, it is at least possible stock 3.3.1 got released without the fix. I either case, running *any* 3.3.x version, 'sa-update' will fix it and pull in the corrected rules. sa-update obviously needs to be run on the recipient side, and generally should be run at least once a week. Best practice is to run it no less than once a day. If you're suffering from this, tell the recipient end to review their use of sa-update. And actually, to do that. ;) > Sorry, I'm not up on how your update process works. Well, your original bug 6555 suggested you are the recipient, running SA 3.2.3. For 3.2.x versions, the fix is not (yet) available via sa-update. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
