Configuring SAMS with LifeKeeper
Sendmail Configuration File The following are a few more important points to note in the Sendmail
configuration file (/etc/mail/sendmail.cf).
Masquerading
Masquerading is used to translate an email address with a given hostname
into the address of the domain or that of another mailhub/mailserver.
Masquerading can be done at either the domain level or at the host level of
the mailhub/mailserver itself. If masquerading has already been established
to translate the hostname address into that of the domain, then it will not
impact the LifeKeeper SAMS Recovery Kit and you can continue using this
method. However, if masquerading is not used at all, then unpredictable
results will occur during and after a switchover. If masquerading has not
been used prior to implementing LifeKeeper, it is recommended that the
hostname address be masqueraded as the LifeKeeper-protected switchable IP
address.
Port Definition and the SAMS Recovery Kit
The SAMS Recovery Kit listens to the port specified in the
DaemonPortOptions entry in the Sendmail configuration file. If the port is
specified as a service name (e.g., smtp) then the port number is looked up in
the /etc/services file. If DaemonPortOptions is not defined in the Sendmail
configuration file, the port number defaults to the smtp port number defined
in the /etc/services file. If the smtp port number is not defined in
/etc/services, port number 25 is used. If the port is defined in /etc/services
and not in the Sendmail configuration file, you have the advantage of
defining a different port on both the primary and backup servers.
Daemon Mode (Red Hat)
If running on Red Hat Linux, be aware that the SAMS Recovery Kit does not
support disabling the Sendmail daemon feature. Be sure that the Sendmail
system configuration file (/etc/sysconfig/sendmail) has the Daemon option
set as DAEMON=yes.
10 SAMS Recovery Kit Administration Guide