|
If the disk where the sendmail log file is not full, it is likely that SE_Linux is denying sendmail the right to write into its own log. If this is happening, you ought to see a line in /var/log/messages indicating the violation.
This can happen if the log file is in a non-standard location, or if it was copied from another place. In the first case, you will have to read up on how to adjust the selinux system to permit the access; in the second, you might be able to get away with using restorecon to put the security context back to what it should be for where the logfile is currently sitting.
Or it might be something entirely different. If there are no audit messages in your syslog file, then this analysis is probably all wrong.
|
stat=Deferred: 421 Unexpected log failure, please try later in sendmail
