https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6052
--- Comment #2 from James Wilkinson <[email protected]> 2009-01-28 12:31:26 PST --- This probably isn't a SpamAssassin bug. The SpamAssassin SELinux policy isn't distributed with SpamAssassin, even on Fedora. The question, as I see it, is why is SpamAssassin trying to use UDP port 7500? (Is it always port 7500? If not, I'd suspect that this is just SpamAssassin trying to do DNS-based network tests, and opening port 7500 to listen for replies). I suspect you're being confused by the "spamc_t", which is a SELinux type, IIRC. I'd expect it to apply whether you're running spamassassin directly or spamc. Note the exe="/usr/bin/perl": spamc is written in C. In the meantime, you might want to look at system-config-selinux (from a root terminal in X: it's also Gnome System menu -> Administration -> SELinux Management). On the Boolean tab, look for the SpamAssassin module, check that "allow user spamassassin clients to use the network" is enabled. You may want to review the rest of the settings in this program. If that doesn't help, then you might want to do what the SELinux message says, and file a Fedora bug. The SELinux maintainers have a reputation for being very quick off the mark. SpamAssassin developers: I hope you don't mind me using Bugzilla in this way until it's clear there isn't a SpamAssassin bug. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
