The other thing you can do is rely upon the RH startup routines, or the inferstructure RH put in place for sendmail.
Whenever sendmail starts on a RH box (RH8 or newer), it steps through the following code:
echo -n $"Starting $prog: "
if test -x /usr/bin/make -a -f /etc/mail/Makefile ; then
make all -C /etc/mail -s > /dev/null
else
for i in virtusertable access domaintable mailertable ; do
if [ -f /etc/mail/$i ] ; then
makemap hash /etc/mail/$i < /etc/mail/$i
fi
done
fi
/usr/bin/newaliases > /dev/null 2>&1
Simply put, it runs a 'make' in the '/etc/mail' directory, which will re-build any CF files if an MC file has been updated.
it also forcibly re-makes any of the database files, and re-creates the alias database.
Basically, if you make a change and restart sendmail, the changes should come through without having to go to extra lengths.
If you just make a change to one of the databases, you can either do a 'make' in '/etc/mail' or do a 'service sendmail reload' (which will basically do that anyway, but it will also HUP sendmail).
Much fun.. ;)
One long-haired git at your service...