Hi Brett,
I recommend to edit updated sendmail.mc and make sendmail.cf.
Because, updated sendmail.mc is enabled some feature such as
SMTPS, Submission port and SMTP Auth.
So, if these settings are not in sendmail.cf, then these
feature doesn't work correctly.
Updated sendmail.mc has these new settings.
TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5
LOGIN PLAIN')dnl
define(`confCACERT_PATH',`/usr/share/ssl/certs')
define(`confCACERT',`/usr/share/ssl/certs/ca-bundle.crt')
define(`confSERVER_CERT',`/usr/share/ssl/certs/sendmail.pem')
define(`confSERVER_KEY',`/usr/share/ssl/certs/sendmail.pem')
DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnl
DAEMON_OPTIONS(`Port=submission, Name=MSA, M=Ea')dnl
DAEMON_OPTIONS(`Port=smtps, Name=TLSMTA, M=s')dnl
define(`confSMTP_LOGIN_MSG',$?{if_name}${if_name}$|$j$. Sendmail
Ready; $b)dnl
Hisao
On 2006/09/19, at 23:07, Vapor wrote:
> I've successfully upgraded a few test boxen and happy so far with
> them, so I'm
> preparing to upgrade production boxen shortly. Just a quick
> question which hopefully
> saves me some time in the future.
>
> In the past I started to make changed to my sendmail setups by
> editing the sendmail.mc
> file and doing a "make" to generate the new sendmail.cf - however,
> past a point I had
> to make changes to the sendmail.cf file directly as further
> upgrades via yum made
> changes directly to the .cf file and provided no new sendmail.mc
> file for me to "make"
> a fresh .cf file with the updates included.
>
> So my question is, on an ongoing basis should I expect updates to
> be made directly to
> the sendmail.cf file and totally abandon the sendmail.mc + make
> route? Or do we know /
> have any assurances that changes will be propagated via an updated
> sendmail.mc file
> which we can edit and "make"?
>
> Any insight appreciated.
>
> Brett