I get a few selinux denials when using exim on a default install. avc: denied { setuid } for comm="sendmail" egid=93 euid=0 exe="/usr/sbin/exim" exit=-1 fsgid=93 fsuid=0 gid=93 items=0 pid=2411 scontext=system_u:system_r:logwatch_t:s0-s0:c0.c1023 sgid=93 subj=system_u:system_r:logwatch_t:s0-s0:c0.c1023 suid=0 tclass=capability tcontext=system_u:system_r:logwatch_t:s0-s0:c0.c1023 tty=(none) uid=0 avc: denied { append } for comm="sendmail" dev=dm-0 egid=93 euid=0 exe="/usr/sbin/exim" exit=-13 fsgid=93 fsuid=0 gid=93 items=0 name="main.log" pid=2410 scontext=system_u:system_r:logwatch_t:s0-s0:c0.c1023 sgid=93 subj=system_u:system_r:logwatch_t:s0-s0:c0.c1023 suid=0 tclass=file tcontext=system_u:object_r:var_log_t:s0 tty=(none) uid=0 avc: denied { write } for comm="sendmail" dev=tmpfs egid=93 euid=0 exe="/usr/sbin/exim" exit=-13 fsgid=93 fsuid=0 gid=93 items=0 name="console" pid=2409 scontext=system_u:system_r:logwatch_t:s0-s0:c0.c1023 sgid=93 subj=system_u:system_r:logwatch_t:s0-s0:c0.c1023 suid=0 tclass=chr_file tcontext=system_u:object_r:console_device_t:s0 tty=(none) uid=0 avc: denied { write } for comm="sendmail" dev=dm-0 egid=93 euid=0 exe="/usr/sbin/exim" exit=-13 fsgid=93 fsuid=0 gid=93 items=0 name="exim" pid=2411 scontext=system_u:system_r:logwatch_t:s0-s0:c0.c1023 sgid=93 subj=system_u:system_r:logwatch_t:s0-s0:c0.c1023 suid=0 tclass=dir tcontext=system_u:object_r:var_log_t:s0 tty=(none) uid=0 avc: denied { create } for comm="sendmail" egid=93 euid=0 exe="/usr/sbin/exim" exit=-13 fsgid=93 fsuid=0 gid=93 items=0 pid=2409 scontext=system_u:system_r:logwatch_t:s0-s0:c0.c1023 sgid=93 subj=system_u:system_r:logwatch_t:s0-s0:c0.c1023 suid=0 tclass=unix_dgram_socket tcontext=system_u:system_r:logwatch_t:s0-s0:c0.c1023 tty=(none) uid=0 exim gets picked as the provider of /usr/bin/sendmail, because it has the shortest name out of sendmail, postfix, or exim.
If you chcon -t sendmail_exec_t /usr/sbin/exim, does the problem go away?
I can't seem to duplicate this. Did you do any selinux changes for exim recently?
no
Just my 2 cents here, but I received a few similar errors today. They were easily fixed through advice from setroubleshoot however. the fixes were semanage fcontext -a -t bin_t sudoedit restorecon -v /var/log/exim/main.log setsebool -P allow_daemons_use_tty=1 restorecon /var/log/exim/panic.log Not sure why or when I started getting these and I don't recall the specific errors. Hope this helps
Please attach your avc messages?