On Tue, Jul 28, 2015 at 05:09:33AM -0400, Nico Kadel-Garcia wrote:
On Mon, Jul 27, 2015 at 7:52 PM, Fred Smith fredex@fcshome.stoneham.ma.us wrote:
On Mon, Jul 27, 2015 at 01:23:07PM -0700, Akemi Yagi wrote:
On Mon, Jul 27, 2015 at 12:38 PM, Fred Smith fredex@fcshome.stoneham.ma.us wrote:
FYI, I ran all the (then current) updates from the CR repo this morning, and found that it stepped on my sendmail.cf. (presumably the sendmail rpm was the culprit.)
I wouldn't think that was the desired beavhior, would you? I'd expect it to drop either a rpm.old or rpm.new file instead.
luckily, easy to fix once I figured out why incoming mail was busticated.
If you look into the /etc/mail directory, don't you see sendmail.cf.bak? At least in my case, that file was created by sendmail* update.
Akemi
Yes, I do.
Nevertheless, it seems kinda rude of it to break a working configuration...
But I'm no expert, what do I know? :)
Sounds like you edited sendmail.cf directly. That's not the standard
No, I have a .mc file and generate sendmail.cf.
but it's still a pain to have an important subsystem broken by an update that drops a config file on top of the locally configured one.
configuration file for local changes, those usually live in sendmail.mc and are processed with the m4 macro language. As I remember sendmail from.... oh, a very long time ago, you need to use the "sendmail.fc" or "frozen configuration" config file if you want to protect it from rebuilds based on sendmail.mc.