https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6939
Karsten Bräckelmann <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Karsten Bräckelmann <[email protected]> --- (In reply to Kip from comment #2) > > Both Ubuntu 12.04 and 13.04 are shipping SA 3.3.2, thus not a SA bug. > > Please ask your distro for support. > > Sorry, I don't follow. I thought this was the issue tracker for SA? It is indeed. > > Which it seems you did. Ubuntu bug 1178826 is the same report... > > That's a downstream report, but the actual upstream it is linked to is > here. > I'm sorry, but that's actually standard practise with Launchpad, and a > good thing at that. This is why we have a feature to link to the > upstream issue. > <https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1178826> That bug is filed against the "evolution" package in Ubuntu 13.04. The upstream bug-tracker for Evolution is https://bugzilla.gnome.org Product Evolution, Component Plugins (which is where the spam filter integration lives). > > Closing RESOLVED INVALID, not a SA bug. > > I'm sorry, but that's just not a constructive answer. If it's not a bug, > then you could at least tell me why you believe it is not a bug. There > isn't any information in your post to indicate otherwise, even if you > are right. My answer was constructive, in telling you where to head next for support. Moreover, I did tell you why I believe it is not a SA bug. (Note the subtle difference in your and my phrase. I did not say "not a bug", but "not a SA bug".) The first sentence of my comment 1 provided the reasoning for closing the bug report in this bug-tracker. According to your original report comment 0, the bug did not happen with Ubuntu 12.04. It does happen with Ubuntu 13.04 after a fresh install. However, *both* versions are shipping the same SA upstream version 3.3.2. It should be easy to understand that there is no code change in SA. There has been a plethora of changes in Ubuntu in general, though, as well as major parts of the Linux kernel, GNOME, Evolution, Perl. Possibly even in the Ubuntu provided packages with custom patches. And since this is a fresh install, there could even be missing dependencies, or configuration changes -- including really low-level config like enabling SELinux. Closing RESOLVED INVALID, not a SA bug. (FWIW, I am not yelling there, neither emphasizing "invalid", which is just the less friendly default way of saying "not a bug". These parts are uppercase, because that's how they are referred to in bugzilla. The case, as well as always clearly stating status changes is how I got used to during many years of GNOME bugsquad participation.) -- You are receiving this mail because: You are the assignee for the bug.
