Eric Rostetter wrote:
Quoting Michael Kratz <mkratz@xxxxxxxxxxxxxxxx>:
I just (yum) updated sendmail on a Redhat 7.3 box, and the RPM
overwrote my sendmail.cf file and didn't create a .rpmnew or .rpmsave!
Lucky I still had my custom .mc file and it didn't overwrite that.
Can you tell what was different between the old .cf and the new one?
The new cf appeared to be a 'fresh' default config file.
i.e. only bound to localhost, all my amavis and rbl stuff was missing, etc.
Heres the build info from the sendmail.cf post upgrade:
##### built by mockbuild@xxxxxxxxxxxxxxxxxxxxxxxxxxxx on Wed Mar 22
23:27:38 EST 2006
##### in /builddir/build/BUILD/sendmail-8.12.11/cf/cf
##### using ../ as configuration include directory
It looks like it just completely overwrote my sendmail.cf with a bog
standard config.
It shouldn't do that. It should either create its own sendmail.cf as
sendmail.cf.rpmnew, or move the existing one to sendmail.rpmsave and
then replace it.
I can see it tries to "update" the sendmail.cf to comment out any
references to "AutoRebuildAliases".
Thats not present in my sendmail.cf at all.
This "update" might look more sinister than it
is, or might even be more sinister than it means to be (e.g. if you run a
non-standard configuration). In any case, it deletes the original without
saving it... I can see where this could hose your configuration in very
rare edge cases (like running out of disk space on the device while
writing a file, etc).
In this case, pretty much everyone is going to be running a non-standard
configuration if they're running a mail server, because the standard
configuration only binds Sendmail to 127.0.0.1.
Cheers,
Michael
--
fedora-legacy-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-legacy-list
