Red Hat Bugzilla – Bug 398931
sendmail updates overwrites custom sedmail configuration
Last modified: 2007-11-30 17:12:24 EST
Description of problem:
The last few sendmail updates have restarted sendmail using a standard
configuration, rather than my local customized configuration, causing loss and
delay of messages. It's a terrible idea for a sendmail upgrade to override a
modified configuration and restart the daemon without the modifications. It
would be better to leave the modified configuration in place (which rpm claims
to do, storing the new config in .rpmnew) and restart the new daemon with it.
Then, if it fails to restart, at least it won't lose messages and the failure
will be noticed relatively quickly.
Oddly, there are sendmail.cf.rpmnew files left behind after the latest update.
This is probably an artifact of having got both i386 and x86_64 versions of
sendmail.cf installed. RPM has some trouble with configuration files modified
as part of the current transaction when the other-arch build of the package
attempts to install it too.
Version-Release number of selected component (if applicable):
You shound not modify sendmail.cf by hand. Please use sendmail.mc for
customizations. Service sendmail start will create a new sendmail.cf, if at
minimum one of the mc files is newer than the cf file.
Closing as NOT A BUG.