Re: Fedora 13, Spamassassin, and SELinux

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/21/2010 07:14 AM, B Wooster wrote:
> Just installed Fedora 13, and ran into problems with spamassassin.
> SELinux disallows a lot of spamassassin tasks - reporting
> "If you want to allow spamassassin to bind to port 61706, you can execute
> # semanage port -a -t PORT_TYPE -p udp 61706"
>
> That of course is meaningless since the port changes all the time.
>
> So, is SELinux still a major issue, and is the best option to turn it
> off at boot time?
> Or does spamassassin have an easy fix, and that is the only problem to
> be expected?
> IE, sshd, httpd. rsync, servers will not run into SELinux problems,
> anyone knows?

# setsebool -P spamassassin_can_network 1

Could you attach the AVC messages.  I need to change the priority.

If you pipe the messages to audit2allow -w, it should tell you about the 
boolean.
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux