SELinux is preventing /usr/sbin/exim from read, write access on the file /var/log/nagios/spool/checkresults/checkkkoB8s.

*****  Plugin leaks (50.5 confidence) suggests  ******************************

If you want to ignore exim trying to read write access the checkkkoB8s file, because you believe it should not need this access.
Then you should report this as a bug.  
You can generate a local policy module to dontaudit this access.
Do
# grep /usr/sbin/exim /var/log/audit/audit.log | audit2allow -D -M mypol
# semodule -i mypol.pp

*****  Plugin catchall (50.5 confidence) suggests  ***************************

If you believe that exim should be allowed read write access on the checkkkoB8s file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep mailq /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:system_mail_t:s0
Target Context                system_u:object_r:nagios_log_t:s0
Target Objects                /var/log/nagios/spool/checkresults/checkkkoB8s [
                              file ]
Source                        mailq
Source Path                   /usr/sbin/exim
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           exim-4.76-2.fc15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.16-39.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed)
                              2.6.40.6-0.fc15.x86_64 #1 SMP Tue Oct 4 00:39:50
                              UTC 2011 x86_64 x86_64
Alert Count                   1
First Seen                    Sun 09 Oct 2011 03:16:45 PM BST
Last Seen                     Sun 09 Oct 2011 03:16:45 PM BST
Local ID                      5527bac8-87b8-46e8-a62d-b773b3a368b4

Raw Audit Messages
type=AVC msg=audit(1318169805.859:393): avc:  denied  { read write } for  pid=10056 comm="mailq" path="/var/log/nagios/spool/checkresults/checkkkoB8s" dev=dm-1 ino=393980 scontext=system_u:system_r:system_mail_t:s0 tcontext=system_u:object_r:nagios_log_t:s0 tclass=file


type=SYSCALL msg=audit(1318169805.859:393): arch=x86_64 syscall=execve success=yes exit=0 a0=ce06b0 a1=1475180 a2=cdfbc0 a3=7fff37e42700 items=0 ppid=10055 pid=10056 auid=4294967295 uid=483 gid=467 euid=0 suid=0 fsuid=0 egid=467 sgid=467 fsgid=467 tty=(none) ses=4294967295 comm=mailq exe=/usr/sbin/exim subj=system_u:system_r:system_mail_t:s0 key=(null)

Hash: mailq,system_mail_t,nagios_log_t,file,read,write

audit2allow

#============= system_mail_t ==============
allow system_mail_t nagios_log_t:file { read write };

audit2allow -R

#============= system_mail_t ==============
allow system_mail_t nagios_log_t:file { read write };


This seems to be as a result of the following Nagios config, checking Exim mail queue on the local machine:
define service {
	[...]
	check_command	check_mailq!exim!5!15
}
define command {
	command_name	check_mailq
	command_line	$USER1$/check_mailq $ARG4$ --mailserver=$ARG1$ --warning=$ARG2$ --critical=$ARG3$ -v
}

Despite this, the plugin seems to return a result to Nagios without problems.

The filename is different each time the check runs.

This has only been occurring since my upgrade from F13 to F15.