Spamassasin Problem

[W. Scott Wilburn]

Hi,

	Since upgrading from spamassassin.i386 3.0.4-2.fc4 to 
spamassassin.i386 3.0.4-1.fc4, I get avc denied messages:

Nov 20 04:05:44 scooby kernel: audit(1132484744.807:45387): avc:  denied  
{ search } for  pid=25548 comm="spamd" name=".spamassassin" dev=md0 
ino=2197675 scontext=root:system_r:spamd_t 
tcontext=user_u:object_r:user_home_t tclass=dir

FC4, targeted policy enforcing mode
selinux-policy-targeted-sources.noarch 1.27.1-2.11

Since the problem occurred with a spamassassin update, not selinux, I 
assume something in the behavior of spamassassin has changed.

Any help appreciated.

Scott Wilburn
--

[Nicolas Mailhot]

W. Scott Wilburn wrote:

>  Since the problem occurred with a spamassassin update, not selinux, I
>
>  assume something in the behavior of spamassassin has changed. 
There is a boatload of spamassassin+selinux problems in bugzilla, I'm
not sure Dan will have the time to fix them before FC5, let alone look
at FC4 problems.

Spamassassin does so many things (resolves names, writes in user homes,
launches pluggins like pyzor/razor, some client/server spamc/spamd
stuff...) from so many contexts (procmail, user, mta...) it seems every
single policy/spamassassin update breaks something.

-- 
Nicolas Mailhot

[Bjorn Victor]

On Mon, 05 Dec 2005 23:50:45 +0100 Nicolas Mailhot <nicolas.mailhot(a)laposte.net&gt;
wrote:

>  W. Scott Wilburn wrote:
>
> > Since the problem occurred with a spamassassin update, not selinux, I 
> > assume something in the behavior of spamassassin has changed.
>
>  There is a boatload of spamassassin+selinux problems in bugzilla, I'm
>  not sure Dan will have the time to fix them before FC5, let alone look
>  at FC4 problems.
>
>  Spamassassin does so many things (resolves names, writes in user homes,
>  launches pluggins like pyzor/razor, some client/server spamc/spamd
>  stuff...) from so many contexts (procmail, user, mta...) it seems every
>  single policy/spamassassin update breaks something. 
Any advise on how to make spamassassin/spamd work (without disabling
SElinux entirely) would be very welcome.

-- Bjorn

[Nicolas Mailhot]

Bjorn Victor wrote:
>  On Mon, 05 Dec 2005 23:50:45 +0100 Nicolas Mailhot
> <nicolas.mailhot(a)laposte.net&gt; wrote:
>  
> > W. Scott Wilburn wrote:
> >
> >> Since the problem occurred with a spamassassin update, not selinux, I 
> >> assume something in the behavior of spamassassin has changed.
> > There is a boatload of spamassassin+selinux problems in bugzilla, I'm
> > not sure Dan will have the time to fix them before FC5, let alone look
> > at FC4 problems.
> >
> > Spamassassin does so many things (resolves names, writes in user homes,
> > launches pluggins like pyzor/razor, some client/server spamc/spamd
> > stuff...) from so many contexts (procmail, user, mta...) it seems every
> > single policy/spamassassin update breaks something.
>  
>  Any advise on how to make spamassassin/spamd work (without disabling
>  SElinux entirely) would be very welcome. 
Report AVCs in bugzilla, confirm existing bugs, etc

-- 
Nicolas Mailhot

[Daniel J Walsh]

Bjorn Victor wrote:
>  On Mon, 05 Dec 2005 23:50:45 +0100 Nicolas Mailhot
> <nicolas.mailhot(a)laposte.net&gt; wrote:
>
>    
> > W. Scott Wilburn wrote:
> >
> >     
> >> Since the problem occurred with a spamassassin update, not selinux, I 
> >> assume something in the behavior of spamassassin has changed.
> >>       
> > There is a boatload of spamassassin+selinux problems in bugzilla, I'm
> > not sure Dan will have the time to fix them before FC5, let alone look
> > at FC4 problems.
> >
> > Spamassassin does so many things (resolves names, writes in user homes,
> > launches pluggins like pyzor/razor, some client/server spamc/spamd
> > stuff...) from so many contexts (procmail, user, mta...) it seems every
> > single policy/spamassassin update breaks something.
> >     
>
>  Any advise on how to make spamassassin/spamd work (without disabling
>  SElinux entirely) would be very welcome.
>
>  -- Bjorn
>
>  --
>  fedora-selinux-list mailing list
>  fedora-selinux-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-selinux-list
>     
Try selinux-policy-targeted-1.27.1-2.16 which was just released to Updates.

--