Le 12/12/2017 à 21:25, Gordon Messmer a écrit : > You may have had a custom context set on /var/log/spamassassin or a > sub-path in the past, overwritten by a recent update. That's a normal > occurrence if you set context using chcon rather than "semanage > fcontext". The latter is persistent; the former is not. > > Spamassassin can write to /var/lib/spamassassin, which makes that a more > suitable location for bayes_toks than /var/log. However, if you'd > prefer to keep your bayes_toks file where it is, use: > > semanage fcontext -a -t spamd_var_lib_t > /var/log/spamassassin/.spamassassin > restorecon -Rv /var/log/spamassassin/.spamassassin Thanks very much. That got me on the right track, though I solved the problem a bit differently. # semanage fcontext -a -t spamd_var_lib_t '/var/log/spamassassin(/.*)?' # restorecon -Rv /var/log/spamassassin/ That did the trick. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info at microlinux.fr Tél. : 04 66 63 10 32