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 -- fedora-selinux-list mailing list fedora-selinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-selinux-list
