https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7908
John Hardin <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Resolution|--- |FIXED Status|REOPENED |RESOLVED --- Comment #11 from John Hardin <[email protected]> --- (In reply to WebStars from comment #9) > Spam Assassing rules block PRO domain as untrusted. The currently published rules *do not* do so. > It should be changed. It *has been* changed. > Are you going to help or only close the ticket to have more free time? The SpamAssassin project has done all it can to address this problem. The currently published rules only score *one* point for mailing from or mentioning the .pro domain. SA is not centrally controlled. The SA project *publishes* rules for sites to download and install, it does not *push* them onto all existing SA installs. We have no control over sites that are using stale rules. We cannot force them to update their rules. SpamAssassin installations do not register, so the SA project has no way to know where SA is being used, or what portion of those installs are stale or misconfigured. We have no way to contact them unless they voluntarily subscribe to the SA Users mailing list. We're not simply ignoring you, or the problem. We've done all we can to fix it. If a customer of yours sees a message from you being scored like that, then they (or you) need to contact *their* ISP and tell them their SpamAssassin install is stale and is rejecting messages it should not. I'm sorry that that is the best we can do, but it is, and ranting about it won't change that situation. -- You are receiving this mail because: You are the assignee for the bug.
