 |
| ||||
Sendmail implements a general purpose internetwork mail routing facility under the UNIX operating system.
Sendmail has a number of features that can be used to monitor or adjust its operation.
It is not tied to any one transport protocol — its function may be likened to a crossbar switch, relaying messages from one domain into another.
In the process, it can do a limited amount of message header editing to put the message into a format that is appropriate for the receiving domain. All of this is done under the control of a configuration file.
Due to the requirements of flexibility for sendmail, the configuration file can seem somewhat unapproachable.
However, there are only a few basic configurations for most sites, for which standard configuration files have been supplied. Most other configurations can be built by adjusting an existing configuration file incrementally.
Sendmail is based on: RFC 821 (Simple Mail Transport Protocol), RFC 822 (Internet Mail Headers Format), RFC 974 (MX routing), RFC 1123 (Internet Host Requirements), RFC 1413 (Identification server), RFC 1652 (SMTP 8BITMIME Extension), RFC 1869 (SMTP Service Extensions), RFC 1870 (SMTP SIZE Extension), RFC 1891 (SMTP Delivery Status Notifications), RFC 1892 (Multipart/Report), RFC 1893 (Enhanced Mail System Status Codes), RFC 1894 (Delivery Status Notifications), RFC 1985 (SMTP Service Extension for Remote Message Queue Starting), RFC 2033 (Local Message Transmission Protocol), RFC 2034 (SMTP Service Extension for Returning Enhanced Error Codes), RFC 2045 (MIME), RFC 2476 (Message Submission), RFC 2487 (SMTP Service Extension for Secure SMTP over TLS), RFC 2554 (SMTP Service Extension for Authentication), RFC 2821 (Simple Mail Transfer Protocol), RFC 2822 (Internet Message Format), RFC 2852 (Deliver By SMTP Service Extension), and RFC 2920 (SMTP Service Extension for Command Pipelining).
However, since sendmail is designed to work in a wider world, in many cases it can be configured to exceed these protocols
What's New in This Release: [ read full changelog ]
SECURITY:
· Handle bogus certificates containing NUL characters in CNs by placing a string indicating a bad certificate in the {cn_subject} or {cn_issuer} macro.
· During the generation of a queue identifier an integer overflow could occur which might result in bogus characters being used.
· The value of headers, e.g., Precedence, Content-Type, et.al., was not processed correctly.
· Between 8.11.7 and 8.12.0 the length limitation on a return path was erroneously reduced from MAXNAME (256) to MAXSHORTSTR (203).
· Prevent a crash when a hostname lookup returns a seemingly valid result which contains a NULL pointer (this seems to be happening on some Linux versions).
· The process title was missing the current load average when the MTA was delaying connections due to DelayLA.
· Do not reset the number of queue entries in shared memory if only some of them are processed.
· Fix overflow of an internal array when parsing some replies from a milter.
· If STARTTLS is turned off in the server (via M=S) then it would not be initialized for use in the client either.
· If a Diffie-Hellman cipher is selected for STARTTLS, the handshake could fail with some TLS implementations because the prime used by the server is not long enough. Note: the initialization of the DSA/DH parameters for the server can take a significant amount of time on slow machines. This can be turned off by setting DHParameters to none or a file (see doc/op/op.me).
Via: Sendmail 8.14.6
0 Comment:
Post a Comment