https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6052
--- Comment #5 from Karsten Bräckelmann <[email protected]> 2009-01-29 07:46:01 PST --- (In reply to comment #4) > Yea you guys are right this has nada to do with spamc. I send an email through > the system and then the selinux error comes up. I think selinux just needs to Kevin, did you already file a bug with RH? > be updated to ignore this, unless there is some reason why I shouldn't be > sending my mail through spamassassin in /etc/procmailrc? I don't bother to > load spamd because my system only receives a tiny amount of email right now. Frankly, IMHO, using spamc/d is worth it in almost all cases, no matter how low the traffic might be. If you feel the need for SA in the first place... After some quick discussion, I believe James is correct about DNS. Kevin, you can test this. While this warning still is present, try scanning a mail with local tests only. spamassassin -L < message Does this come out clan, no SELinux warning? Also, since SELinux prevented this: Your SA is most likely performing rather poor. Even with network tests enabled, it won't get any results. Not closing for now, until we get some more facts. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
