Sendmail 8.11.1 Release Notes

By using delay_checks, the rulesets check_mail and check_relay will
not be called when a client connects or issues a MAIL command, respectively.
Instead, those rulesets will be called by the check_rcpt ruleset; they will be
skipped if a sender has been authenticated using a "trusted" mechanism, i.e.
one that is defined via the list of AuthMechanisms. If check_mail returns
an error, the RCPT TO command will be rejected with that error. If it returns
some other result starting with $#, then check_relay will be skipped. If the
sender address (or a part of it) is listed in the access map and it has a RHS of
OK or RELAY, then check_relay will be skipped.
3. relay_mail_from
This option can be used to facilitate relaying through a user’s machine.The
sender’s name, which is listed as “RELAY” in the access map (tagged with
From:) can be specified using this option. The domain portion of the mail
sender is also checked, when the optional argument ‘domain’ is provided.
4. ldap_routing
This option can be used to implement the ldap-based email recipient routing.
This provides a method for re-routing addresses with a domain portion in
class {LdapRoute} to either a different mail host or to a different address.
NOTE: For more information, refer to “LDAP-based Routing” section.
5. no_default_msa
This option can be used to generate the configuration file without
‘DaemonPortOptions’ option for Message Submission Agent (MSA) daemon.
The sendmail.cf configuration file will not contain the following line:
O DaemonPortOptions=Port=587, Name=MSA, M=E
6. receive_only
This option generates a sendmail.cf file with a new set of rules called
‘check_compat’. You can only receive mail messages, but cannot send them.
Two new flags have been added in /etc/rc.config.d/mailservs file.
They are:
a. SENDMAIL_RECVONLY
This flag must be set to ‘1’ in order to use “receive_only” feature.
b. SENDMAIL_SENDONLY
This flag may not be set to any value.
12 New and Changed Features