https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7686
Jordan <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #2 from Jordan <[email protected]> --- (In reply to Bill Cole from comment #1) Thanks Bill! > FIRST: You've reported the bug against (and your example shows) SpamAssassin > v3.4.0, which is obsolete, buggy and insecure. You should upgrade, and your > problem MAY have been fixed during the 4+ years between the releases of 3.4.0 > and 3.4.2. I figured that would be an issue. I'm using CentOS 7, and so getting updates sadly means recompiling from src RPM, which isn't always a smooth process. It's too bad you guys never got a repo of your own set up as was discussed here: https://lists.apache.org/thread.html/ae9c9281fece9c8d9d21d18fe7f035ef804f080fe10f0707e3715004@%3Cusers.spamassassin.apache.org%3E We'll be discussing internally how best to proceed as if we compile our own, then we also have to ensure to stay on top of updates manually (rather than relying on the standard yum update channels. --- Will be testing and confirming the missing value from msa_networks as suggested. I think between not running latest release and my likely misconfiguration of msa_networks, it's safe to mark this resolved -- if I find otherwise in my tests, we can always re-open it. -Jordan -- You are receiving this mail because: You are the assignee for the bug.
