On Wed, Jun 23, 2010 at 5:25 PM, Daniel J Walsh wrote:
> On 06/22/2010 06:58 PM, B Wooster wrote:
>> But I'm all set now, for other reasons, am running with selinux=0
> Well ask questions about what caused you to disable SELInux. Remember
> you can always put the machine int
On Tue, Jun 22, 2010 at 3:53 PM, B Wooster wrote:
> Just updated to Fedora 13, and mutt html viewer stopped working.
> using /etc/mailcap also fails the same way.
> That Fedora mailcap seems incomplete for links anyway, it says:
> text/html; /usr/bin/xdg-open %s ; copiousoutput
> w
On Tue, Jun 22, 2010 at 8:14 AM, Daniel J Walsh wrote:
>
> Did you turn on the boolean
>
> # setsebool -P spamassassin_can_network 1
>
Oh yes, that seems to fix the problem - I don't see any new messages
in audit.log after doing that, I thought you wanted to see the log
messages before the fix -
Not sure if this is a config or mutt issue - but in case anyone has any ideas.
Just updated to Fedora 13, and mutt html viewer stopped working.
It says:
Invoking autoview command: /usr/bin/links '/tmp/mutt.html'
and just hangs there when viewing a html message.
Hitting CNTRL-C shows the page (q,
>On Mon, Jun 21, 2010 at 7: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
> #
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
