https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6552
--- Comment #10 from Josh <[email protected]> 2011-03-19 00:56:05 EDT --- 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? Sorry, I'm not up on how your update process works. Thanks :) (In reply to comment #8) > (In reply to comment #6) > > Thanks for moving my ticket, > > > > This is an issue in SpamAssassin 3.3.1, is this going to be fixed in a new > > version or something I need to do? > > See comment 1. The fix actually is available for SA 3.3.x (not only 3.3.1). > This fix needs to be back-ported (done in SVN) and made available via > sa-update > for 3.2.x, too. > > The *recipient* then needs to run sa-update, to get the corrected rules. > > In your case, from bug 6555, I see you are the recipient, on a SA 3.2.x > installation. The following method will fix it immediately for you. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
