search for: spamc_t

...the ''postfix_pipe_exec_t'' context and it's spooling directory needs the ''postfix_pipe_tmp_t'' context. However the script also calls the ''spamc'' binary of ''spamassassin'' for processing. Alas, this binary runs under ''spamc_t'' and thus couldn't read or write into the spool directory. > + > + After executing this process we get a ''.te'' file that looks like this: > + {{{ > + module mynewpolicy 1.0; > + > + require { > + type spamc_t; > + type postfix_...

...llow system_mail_t rpm_t:tcp_socket { read write }; allow system_mail_t rpm_var_lib_t:file { read write }; allow system_mail_t var_lib_t:file write; I've been getting the latter set continously since the upgrade. The first set appeared briefly when I did a 'setenforce 0' to diagnose a spamc_t issue with calling the /usr/sbin/sendmail symlink.. They correspond to audit.log messages similar to the following: type=AVC msg=audit(1239664501.977:9052044): avc: denied { write } for pid=18901 comm="sendmail" name="transaction-done.2009-04-12.22:52.45" dev=loop0 ino=9015...