4 This file contains descriptions of new features that have been added to Exim.
5 Before a formal release, there may be quite a lot of detail so that people can
6 test from the snapshots or the Git before the documentation is updated. Once
7 the documentation is updated, this file is reduced to a short list.
12 1. PKG_CONFIG_PATH can now be set in Local/Makefile;
13 wildcards will be expanded, values are collapsed.
15 2. The ${readsocket } expansion now takes an option to not shutdown the
16 connection after sending the query string. The default remains to do so.
18 3. An smtp transport option "hosts_noproxy_tls" to control whether multiple
19 deliveries on a single TCP connection can maintain a TLS connection
20 open. By default disabled for all hosts, doing so saves the cost of
21 making new TLS sessions, at the cost of having to proxy the data via
22 another process. Logging is also affected.
24 4. A malware connection type for the FPSCAND protocol.
30 1. Allow relative config file names for ".include"
32 2. A main-section config option "debug_store" to control the checks on
33 variable locations during store-reset. Normally false but can be enabled
34 when a memory corrution issue is suspected on a production system.
40 1. The new perl_taintmode option allows to run the embedded perl
41 interpreter in taint mode.
43 2. New log_selector: dnssec, adds a "DS" tag to acceptance and delivery lines.
45 3. Speculative debugging, via a "kill" option to the "control=debug" ACL
48 4. New expansion item ${sha3:<string>} / ${sha3_<N>:<string>}.
49 N can be 224, 256 (default), 384, 512.
50 With GnuTLS 3.5.0 or later, only.
52 5. Facility for named queues: A command-line argument can specify
53 the queue name for a queue operation, and an ACL modifier can set
54 the queue to be used for a message. A $queue_name variable gives
57 6. New expansion operators base32/base32d.
59 7. The CHUNKING ESMTP extension from RFC 3030. May give some slight
60 performance increase and network load decrease. Main config option
61 chunking_advertise_hosts, and smtp transport option hosts_try_chunking
64 8. LMDB lookup support, as Experimental. Patch supplied by Andrew Colin Kissa.
66 9. Expansion operator escape8bit, like escape but not touching newline etc..
68 10. Feature macros, generated from compile options. All start with "_HAVE_"
69 and go on with some roughly recognisable name. Driver macros, for
70 router, transport and authentication drivers; names starting with "_DRIVER_".
71 Option macros, for each configuration-file option; all start with "_OPT_".
72 Use the "-bP macros" command-line option to see what is present.
74 11. Integer values for options can take a "G" multiplier.
76 12. defer=pass option for the ACL control cutthrough_delivery, to reflect 4xx
77 returns from the target back to the initiator, rather than spooling the
80 13. New built-in constants available for tls_dhparam and default changed.
82 14. If built with EXPERIMENTAL_QUEUEFILE, a queuefile transport, for writing
83 out copies of the message spool files for use by 3rd-party scanners.
85 15. A new option on the smtp transport, hosts_try_fastopen. If the system
86 supports it (on Linux it must be enabled in the kernel by the sysadmin)
87 try to use RFC 7413 "TCP Fast Open". No data is sent on the SYN segment
88 but it permits a peer that also supports the facility to send its SMTP
89 banner immediately after the SYN,ACK segment rather then waiting for
90 another ACK - so saving up to one roundtrip time. Because it requires
91 previous communication with the peer (we save a cookie from it) this
92 will only become active on frequently-contacted destinations.
94 16. A new syslog_pid option to suppress PID duplication in syslog lines.
100 1. The ACL conditions regex and mime_regex now capture substrings
101 into numeric variables $regex1 to 9, like the "match" expansion condition.
103 2. New $callout_address variable records the address used for a spam=,
104 malware= or verify= callout.
106 3. Transports now take a "max_parallel" option, to limit concurrency.
108 4. Expansion operators ${ipv6norm:<string>} and ${ipv6denorm:<string>}.
109 The latter expands to a 8-element colon-sep set of hex digits including
110 leading zeroes. A trailing ipv4-style dotted-decimal set is converted
111 to hex. Pure ipv4 addresses are converted to IPv4-mapped IPv6.
112 The former operator strips leading zeroes and collapses the longest
113 set of 0-groups to a double-colon.
115 5. New "-bP config" support, to dump the effective configuration.
117 6. New $dkim_key_length variable.
119 7. New base64d and base64 expansion items (the existing str2b64 being a
120 synonym of the latter). Add support in base64 for certificates.
122 8. New main configuration option "bounce_return_linesize_limit" to
123 avoid oversize bodies in bounces. The default value matches RFC
126 9. New $initial_cwd expansion variable.
132 1. Support for using the system standard CA bundle.
134 2. New expansion items $config_file, $config_dir, containing the file
135 and directory name of the main configuration file. Also $exim_version.
137 3. New "malware=" support for Avast.
139 4. New "spam=" variant option for Rspamd.
141 5. Assorted options on malware= and spam= scanners.
143 6. A command-line option to write a comment into the logfile.
145 7. If built with EXPERIMENTAL_SOCKS feature enabled, the smtp transport can
146 be configured to make connections via socks5 proxies.
148 8. If built with EXPERIMENTAL_INTERNATIONAL, support is included for
149 the transmission of UTF-8 envelope addresses.
151 9. If built with EXPERIMENTAL_INTERNATIONAL, an expansion item for a commonly
152 used encoding of Maildir folder names.
154 10. A logging option for slow DNS lookups.
156 11. New ${env {<variable>}} expansion.
158 12. A non-SMTP authenticator using information from TLS client certificates.
160 13. Main option "tls_eccurve" for selecting an Elliptic Curve for TLS.
161 Patch originally by Wolfgang Breyha.
163 14. Main option "dns_trust_aa" for trusting your local nameserver at the
164 same level as DNSSEC.
170 1. If built with EXPERIMENTAL_DANE feature enabled, Exim will follow the
171 DANE SMTP draft to assess a secure chain of trust of the certificate
172 used to establish the TLS connection based on a TLSA record in the
173 domain of the sender.
175 2. The EXPERIMENTAL_TPDA feature has been renamed to EXPERIMENTAL_EVENT
176 and several new events have been created. The reason is because it has
177 been expanded beyond just firing events during the transport phase. Any
178 existing TPDA transport options will have to be rewritten to use a new
179 $event_name expansion variable in a condition. Refer to the
180 experimental-spec.txt for details and examples.
182 3. The EXPERIMENTAL_CERTNAMES features is an enhancement to verify that
183 server certs used for TLS match the result of the MX lookup. It does
184 not use the same mechanism as DANE.
194 1. If built with the EXPERIMENTAL_PROXY feature enabled, Exim can be
195 configured to expect an initial header from a proxy that will make the
196 actual external source IP:host be used in exim instead of the IP of the
197 proxy that is connecting to it.
199 2. New verify option header_names_ascii, which will check to make sure
200 there are no non-ASCII characters in header names. Exim itself handles
201 those non-ASCII characters, but downstream apps may not, so Exim can
202 detect and reject if those characters are present.
204 3. New expansion operator ${utf8clean:string} to replace malformed UTF8
205 codepoints with valid ones.
207 4. New malware type "sock". Talks over a Unix or TCP socket, sending one
208 command line and matching a regex against the return data for trigger
209 and a second regex to extract malware_name. The mail spoolfile name can
210 be included in the command line.
212 5. The smtp transport now supports options "tls_verify_hosts" and
213 "tls_try_verify_hosts". If either is set the certificate verification
214 is split from the encryption operation. The default remains that a failed
215 verification cancels the encryption.
217 6. New SERVERS override of default ldap server list. In the ACLs, an ldap
218 lookup can now set a list of servers to use that is different from the
221 7. New command-line option -C for exiqgrep to specify alternate exim.conf
222 file when searching the queue.
224 8. OCSP now supports GnuTLS also, if you have version 3.1.3 or later of that.
226 9. Support for DNSSEC on outbound connections.
228 10. New variables "tls_(in,out)_(our,peer)cert" and expansion item
229 "certextract" to extract fields from them. Hash operators md5 and sha1
230 work over them for generating fingerprints, and a new sha256 operator
233 11. PRDR is now supported dy default.
235 12. OCSP stapling is now supported by default.
237 13. If built with the EXPERIMENTAL_DSN feature enabled, Exim will output
238 Delivery Status Notification messages in MIME format, and negotiate
239 DSN features per RFC 3461.
245 1. New command-line option -bI:sieve will list all supported sieve extensions
246 of this Exim build on standard output, one per line.
247 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
248 query this to establish the correct list to include in the protocol's
249 SIEVE capability line.
251 2. If the -n option is combined with the -bP option, then the name of an
252 emitted option is not output, only the value (if visible to you).
253 For instance, "exim -n -bP pid_file_path" should just emit a pathname
254 followed by a newline, and no other text.
256 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
257 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
258 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
259 acceptable for security. (Option accepted but ignored if using OpenSSL).
260 Defaults to 1024, the old value. May be lowered only to 512, or raised as
261 far as you like. Raising this may hinder TLS interoperability with other
262 sites and is not currently recommended. Lowering this will permit you to
263 establish a TLS session which is not as secure as you might like.
265 Unless you really know what you are doing, leave it alone.
267 4. If not built with DISABLE_DNSSEC, Exim now has the main option
268 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
269 to send the DO flag to your recursive resolver. If you have a recursive
270 resolver, which can set the Authenticated Data (AD) flag in results, Exim
271 can now detect this. Exim does not perform validation itself, instead
272 relying upon a trusted path to the resolver.
274 Current status: work-in-progress; $sender_host_dnssec variable added.
276 5. DSCP support for outbound connections: on a transport using the smtp driver,
277 set "dscp = ef", for instance, to cause the connections to have the relevant
278 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
280 Similarly for inbound connections, there is a new control modifier, dscp,
281 so "warn control = dscp/ef" in the connect ACL, or after authentication.
283 Supported values depend upon system libraries. "exim -bI:dscp" to list the
284 ones Exim knows of. You can also set a raw number 0..0x3F.
286 6. The -G command-line flag is no longer ignored; it is now equivalent to an
287 ACL setting "control = suppress_local_fixups". The -L command-line flag
288 is now accepted and forces use of syslog, with the provided tag as the
289 process name. A few other flags used by Sendmail are now accepted and
292 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
293 ACL modifier; works for single-recipient mails which are received on and
294 deliverable via SMTP. Using the connection made for a recipient verify,
295 if requested before the verify, or a new one made for the purpose while
296 the inbound connection is still active. The bulk of the mail item is copied
297 direct from the inbound socket to the outbound (as well as the spool file).
298 When the source notifies the end of data, the data acceptance by the destination
299 is negotiated before the acceptance is sent to the source. If the destination
300 does not accept the mail item, for example due to content-scanning, the item
301 is not accepted from the source and therefore there is no need to generate
302 a bounce mail. This is of benefit when providing a secondary-MX service.
303 The downside is that delays are under the control of the ultimate destination
306 The Received-by: header on items delivered by cutthrough is generated
307 early in reception rather than at the end; this will affect any timestamp
308 included. The log line showing delivery is recorded before that showing
309 reception; it uses a new ">>" tag instead of "=>".
311 To support the feature, verify-callout connections can now use ESMTP and TLS.
312 The usual smtp transport options are honoured, plus a (new, default everything)
313 hosts_verify_avoid_tls.
315 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
316 for specific access to the information for each connection. The old names
317 are present for now but deprecated.
319 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
321 8. New expansion operators ${listnamed:name} to get the content of a named list
322 and ${listcount:string} to count the items in a list.
324 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
325 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
326 modules. For some situations this is desirable, but we expect admin in
327 those situations to know they want the feature. More commonly, it means
328 that GUI user modules get loaded and are broken by the setuid Exim being
329 unable to access files specified in environment variables and passed
330 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
331 unless this new option is set.
333 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
334 so have also added a build option which can be used to build Exim with GnuTLS
335 but without trying to use any kind of PKCS11 support. Uncomment this in the
338 AVOID_GNUTLS_PKCS11=yes
340 10. The "acl = name" condition on an ACL now supports optional arguments.
341 New expansion item "${acl {name}{arg}...}" and expansion condition
342 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
343 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
344 Variable $acl_narg contains the number of arguments. If the ACL sets
345 a "message =" value this becomes the result of the expansion item,
346 or the value of $value for the expansion condition. If the ACL returns
347 accept the expansion condition is true; if reject, false. A defer
348 return results in a forced fail.
350 11. Routers and transports can now have multiple headers_add and headers_remove
351 option lines. The concatenated list is used.
353 12. New ACL modifier "remove_header" can remove headers before message gets
354 handled by routers/transports.
356 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
357 "aaaa" and "a" lookups is done and the full set of results returned.
359 14. New expansion variable $headers_added with content from ACL add_header
360 modifier (but not yet added to message).
362 15. New 8bitmime status logging option for received messages. Log field "M8S".
364 16. New authenticated_sender logging option, adding to log field "A".
366 17. New expansion variables $router_name and $transport_name. Useful
367 particularly for debug_print as -bt command-line option does not
368 require privilege whereas -d does.
370 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
371 proposed extension to SMTP from Eric Hall.
373 19. The pipe transport has gained the force_command option, to allow
374 decorating commands from user .forward pipe aliases with prefix
375 wrappers, for instance.
377 20. Callout connections can now AUTH; the same controls as normal delivery
380 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
381 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
382 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
383 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
384 dmarc_status. It adds new control flags dmarc_disable_verify and
385 dmarc_enable_forensic.
387 22. Add expansion variable $authenticated_fail_id, which is the username
388 provided to the authentication method which failed. It is available
389 for use in subsequent ACL processing (typically quit or notquit ACLs).
391 23. New ACL modifier "udpsend" can construct a UDP packet to send to a given
394 24. New ${hexquote:..string..} expansion operator converts non-printable
395 characters in the string to \xNN form.
397 25. Experimental TPDA (Transport Post Delivery Action) function added.
398 Patch provided by Axel Rau.
400 26. Experimental Redis lookup added. Patch provided by Warren Baker.
406 1. New authenticator driver, "gsasl". Server-only (at present).
407 This is a SASL interface, licensed under GPL, which can be found at
408 http://www.gnu.org/software/gsasl/.
409 This system does not provide sources of data for authentication, so
410 careful use needs to be made of the conditions in Exim.
412 2. New authenticator driver, "heimdal_gssapi". Server-only.
413 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
414 is no longer honoured for setuid programs by Heimdal. Use the
415 "server_keytab" option to point to the keytab.
417 3. The "pkg-config" system can now be used when building Exim to reference
418 cflags and library information for lookups and authenticators, rather
419 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
420 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
421 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
423 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
424 find the headers and libraries for PCRE.
426 4. New expansion variable $tls_bits.
428 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
429 be joined together with ASCII NUL characters to construct the key to pass
430 into the DBM library. Can be used with gsasl to access sasldb2 files as
433 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
435 Avoid release 1.0.1a if you can. Note that the default value of
436 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
437 increased susceptibility to attack. This may still have interoperability
438 implications for very old clients (see version 4.31 change 37) but
439 administrators can choose to make the trade-off themselves and restore
440 compatibility at the cost of session security.
442 7. Use of the new expansion variable $tls_sni in the main configuration option
443 tls_certificate will cause Exim to re-expand the option, if the client
444 sends the TLS Server Name Indication extension, to permit choosing a
445 different certificate; tls_privatekey will also be re-expanded. You must
446 still set these options to expand to valid files when $tls_sni is not set.
448 The SMTP Transport has gained the option tls_sni, which will set a hostname
449 for outbound TLS sessions, and set $tls_sni too.
451 A new log_selector, +tls_sni, has been added, to log received SNI values
452 for Exim as a server.
454 8. The existing "accept_8bitmime" option now defaults to true. This means
455 that Exim is deliberately not strictly RFC compliant. We're following
456 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
457 Those who disagree, or know that they are talking to mail servers that,
458 even today, are not 8-bit clean, need to turn off this option.
460 9. Exim can now be started with -bw (with an optional timeout, given as
461 -bw<timespec>). With this, stdin at startup is a socket that is
462 already listening for connections. This has a more modern name of
463 "socket activation", but forcing the activated socket to fd 0. We're
464 interested in adding more support for modern variants.
466 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
467 for numbers indicates multiplication by 1024^3.
469 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
470 gnutls_require_mac & gnutls_require_protocols are no longer supported.
471 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
472 string, documentation for which is at:
473 http://www.gnutls.org/manual/html_node/Priority-Strings.html
475 SNI support has been added to Exim's GnuTLS integration too.
477 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
478 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
480 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
481 is now available. If the contents of the file are valid, then Exim will
482 send that back in response to a TLS status request; this is OCSP Stapling.
483 Exim will not maintain the contents of the file in any way: administrators
484 are responsible for ensuring that it is up-to-date.
486 See "experimental-spec.txt" for more details.
488 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
489 identically to TXT record lookups.
491 14. New expansion variable $tod_epoch_l for higher-precision time.
493 15. New global option tls_dh_max_bits, defaulting to current value of NSS
494 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
495 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
497 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
498 Option can now be a path or an identifier for a standard prime.
499 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
500 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
503 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
504 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
505 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
511 1. New options for the ratelimit ACL condition: /count= and /unique=.
512 The /noupdate option has been replaced by a /readonly option.
514 2. The SMTP transport's protocol option may now be set to "smtps", to
515 use SSL-on-connect outbound.
517 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
518 there is a problem talking to the AV scanner, or the AV scanner running.
520 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
521 and check if the search item is a member of the list. This does not
522 support named lists, but does subject the list part to string expansion.
524 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
525 built, Exim no longer performs string expansion on the second string of
526 the match_* expansion conditions: "match_address", "match_domain",
527 "match_ip" & "match_local_part". Named lists can still be used.
533 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
534 or off in the resolver library.
540 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
541 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
542 libraries. The following global options have been added in support of
543 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
544 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
546 2. The pipe transport now takes a boolean option, "freeze_signal", default
547 false. When true, if the external delivery command exits on a signal then
548 Exim will freeze the message in the queue, instead of generating a bounce.
550 3. Log filenames may now use %M as an escape, instead of %D (still available).
551 The %M pattern expands to yyyymm, providing month-level resolution.
553 4. The $message_linecount variable is now updated for the maildir_tag option,
554 in the same way as $message_size, to reflect the real number of lines,
555 including any header additions or removals from transport.
557 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
558 Exim now selects entries randomly, to better scale in a cluster setup.
564 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
565 the flaw permitted the Exim run-time user to cause root to append to
566 arbitrary files of the attacker's choosing, with the content based
567 on content supplied by the attacker.
569 2. Exim now supports loading some lookup types at run-time, using your
570 platform's dlopen() functionality. This has limited platform support
571 and the intention is not to support every variant, it's limited to
572 dlopen(). This permits the main Exim binary to not be linked against
573 all the libraries needed for all the lookup types.
579 NOTE: this version is not guaranteed backwards-compatible, please read the
580 items below carefully
582 1. A new main configuration option, "openssl_options", is available if Exim
583 is built with SSL support provided by OpenSSL. The option allows
584 administrators to specify OpenSSL options to be used on connections;
585 typically this is to set bug compatibility features which the OpenSSL
586 developers have not enabled by default. There may be security
587 consequences for certain options, so these should not be changed
590 2. A new pipe transport option, "permit_coredumps", may help with problem
591 diagnosis in some scenarios. Note that Exim is typically installed as
592 a setuid binary, which on most OSes will inhibit coredumps by default,
593 so that safety mechanism would have to be overridden for this option to
594 be able to take effect.
596 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
597 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
598 Note that this switches Exim to use a new API ("INSTREAM") and a future
599 release of ClamAV will remove support for the old API ("STREAM").
601 The av_scanner option, when set to "clamd", now takes an optional third
602 part, "local", which causes Exim to pass a filename to ClamAV instead of
603 the file content. This is the same behaviour as when clamd is pointed at
604 a Unix-domain socket. For example:
606 av_scanner = clamd:192.0.2.3 1234:local
608 ClamAV's ExtendedDetectionInfo response format is now handled.
610 4. There is now a -bmalware option, restricted to admin users. This option
611 takes one parameter, a filename, and scans that file with Exim's
612 malware-scanning framework. This is intended purely as a debugging aid
613 to ensure that Exim's scanning is working, not to replace other tools.
614 Note that the ACL framework is not invoked, so if av_scanner references
615 ACL variables without a fallback then this will fail.
617 5. There is a new expansion operator, "reverse_ip", which will reverse IP
618 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
620 ${reverse_ip:192.0.2.4}
622 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
623 -> 3.0.2.0.0.0.0.c.d.c.b.a.1.0.0.0.9.0.0.0.2.4.c.0.8.b.d.0.1.0.0.2
625 6. There is a new ACL control called "debug", to enable debug logging.
626 This allows selective logging of certain incoming transactions within
627 production environments, with some care. It takes two options, "tag"
628 and "opts"; "tag" is included in the filename of the log and "opts"
629 is used as per the -d<options> command-line option. Examples, which
630 don't all make sense in all contexts:
633 control = debug/tag=.$sender_host_address
634 control = debug/opts=+expand+acl
635 control = debug/tag=.$message_exim_id/opts=+expand
637 7. It has always been implicit in the design and the documentation that
638 "the Exim user" is not root. src/EDITME said that using root was
639 "very strongly discouraged". This is not enough to keep people from
640 shooting themselves in the foot in days when many don't configure Exim
641 themselves but via package build managers. The security consequences of
642 running various bits of network code are severe if there should be bugs in
643 them. As such, the Exim user may no longer be root. If configured
644 statically, Exim will refuse to build. If configured as ref:user then Exim
645 will exit shortly after start-up. If you must shoot yourself in the foot,
646 then henceforth you will have to maintain your own local patches to strip
649 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
650 condition logic to determine truth/failure and will fail to expand many
651 strings, bool_lax{} uses the router condition logic, where most strings
653 Note: bool{00} is false, bool_lax{00} is true.
655 9. Routers now support multiple "condition" tests.
657 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
658 Setting this allows an admin to define which entry in the tcpwrappers
659 config file will be used to control access to the daemon. This option
660 is only available when Exim is built with USE_TCP_WRAPPERS. The
661 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
664 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
665 the Exim run-time user, instead of root.
667 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
668 is forced on. This is mitigated by the new build option
669 TRUSTED_CONFIG_LIST which defines a list of configuration files which
670 are trusted; one per line. If a config file is owned by root and matches
671 a pathname in the list, then it may be invoked by the Exim build-time
672 user without Exim relinquishing root privileges.
674 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
675 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
676 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
677 include the main config. As a transition mechanism, we are temporarily
678 providing a work-around: the new build option WHITELIST_D_MACROS provides
679 a colon-separated list of macro names which may be overridden by the Exim
680 run-time user. The values of these macros are constrained to the regex
681 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
687 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
688 writable, the other to locking of MBX folders (not mbox).
690 2. MySQL stored procedures are now supported.
692 3. The dkim_domain transport option is now a list, not a single string, and
693 messages will be signed for each element in the list (discarding
696 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
697 in the presence of multiple character strings within the RR. Prior to 4.70,
698 only the first string would be returned. The dnsdb lookup now, by default,
699 preserves the pre-4.70 semantics, but also now takes an extended output
700 separator specification. The separator can be followed by a semicolon, to
701 concatenate the individual text strings together with no join character,
702 or by a comma and a second separator character, in which case the text
703 strings within a TXT record are joined on that second character.
704 Administrators are reminded that DNS provides no ordering guarantees
705 between multiple records in an RRset. For example:
707 foo.example. IN TXT "a" "b" "c"
708 foo.example. IN TXT "d" "e" "f"
710 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
711 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
712 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
718 1. Native DKIM support without an external library.
719 (Note that if no action to prevent it is taken, a straight upgrade will
720 result in DKIM verification of all signed incoming emails. See spec
721 for details on conditionally disabling)
723 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
725 3. There is now a bool{} expansion condition which maps certain strings to
726 true/false condition values (most likely of use in conjunction with the
727 and{} expansion operator).
729 4. The $spam_score, $spam_bar and $spam_report variables are now available
732 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
733 options, provided that Exim is invoked by an admin_user.
735 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
736 which increases compatibility with older clients at the cost of decreased
737 security. Don't set this unless you need to support such clients.
739 7. There is a new expansion operator, ${randint:...} which will produce a
740 "random" number less than the supplied integer. This randomness is
741 not guaranteed to be cryptographically strong, but depending upon how
742 Exim was built may be better than the most naive schemes.
744 8. Exim now explicitly ensures that SHA256 is available when linked against
747 9. The transport_filter_timeout option now applies to SMTP transports too.
753 1. Preliminary DKIM support in Experimental.
759 1. The body_linecount and body_zerocount C variables are now exported in the
762 2. When a dnslists lookup succeeds, the key that was looked up is now placed
763 in $dnslist_matched. When the key is an IP address, it is not reversed in
764 this variable (though it is, of course, in the actual lookup). In simple
767 deny dnslists = spamhaus.example
769 the key is also available in another variable (in this case,
770 $sender_host_address). In more complicated cases, however, this is not
771 true. For example, using a data lookup might generate a dnslists lookup
774 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
776 If this condition succeeds, the value in $dnslist_matched might be
777 192.168.6.7 (for example).
779 3. Authenticators now have a client_condition option. When Exim is running as
780 a client, it skips an authenticator whose client_condition expansion yields
781 "0", "no", or "false". This can be used, for example, to skip plain text
782 authenticators when the connection is not encrypted by a setting such as:
784 client_condition = ${if !eq{$tls_cipher}{}}
786 Note that the 4.67 documentation states that $tls_cipher contains the
787 cipher used for incoming messages. In fact, during SMTP delivery, it
788 contains the cipher used for the delivery. The same is true for
791 4. There is now a -Mvc <message-id> option, which outputs a copy of the
792 message to the standard output, in RFC 2822 format. The option can be used
793 only by an admin user.
795 5. There is now a /noupdate option for the ratelimit ACL condition. It
796 computes the rate and checks the limit as normal, but it does not update
797 the saved data. This means that, in relevant ACLs, it is possible to lookup
798 the existence of a specified (or auto-generated) ratelimit key without
799 incrementing the ratelimit counter for that key.
801 In order for this to be useful, another ACL entry must set the rate
802 for the same key somewhere (otherwise it will always be zero).
807 # Read the rate; if it doesn't exist or is below the maximum
809 deny ratelimit = 100 / 5m / strict / noupdate
810 log_message = RATE: $sender_rate / $sender_rate_period \
811 (max $sender_rate_limit)
813 [... some other logic and tests...]
815 warn ratelimit = 100 / 5m / strict / per_cmd
816 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
817 (max $sender_rate_limit)
818 condition = ${if le{$sender_rate}{$sender_rate_limit}}
822 6. The variable $max_received_linelength contains the number of bytes in the
823 longest line that was received as part of the message, not counting the
824 line termination character(s).
826 7. Host lists can now include +ignore_defer and +include_defer, analagous to
827 +ignore_unknown and +include_unknown. These options should be used with
828 care, probably only in non-critical host lists such as whitelists.
830 8. There's a new option called queue_only_load_latch, which defaults true.
831 If set false when queue_only_load is greater than zero, Exim re-evaluates
832 the load for each incoming message in an SMTP session. Otherwise, once one
833 message is queued, the remainder are also.
835 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
836 cases when an SMTP session ends without sending QUIT. However, when Exim
837 itself is is bad trouble, such as being unable to write to its log files,
838 this ACL is not run, because it might try to do things (such as write to
839 log files) that make the situation even worse.
841 Like the QUIT ACL, this new ACL is provided to make it possible to gather
842 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
843 modifier is forbidden in this ACL.
845 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
846 to a string that indicates the reason for the termination of the SMTP
847 connection. The possible values are:
849 acl-drop Another ACL issued a "drop" command
850 bad-commands Too many unknown or non-mail commands
851 command-timeout Timeout while reading SMTP commands
852 connection-lost The SMTP connection has been lost
853 data-timeout Timeout while reading message data
854 local-scan-error The local_scan() function crashed
855 local-scan-timeout The local_scan() function timed out
856 signal-exit SIGTERM or SIGINT
857 synchronization-error SMTP synchronization error
858 tls-failed TLS failed to start
860 In most cases when an SMTP connection is closed without having received
861 QUIT, Exim sends an SMTP response message before actually closing the
862 connection. With the exception of acl-drop, the default message can be
863 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
864 "drop" verb in another ACL, it is the message from the other ACL that is
867 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
868 servers with individual queries. This is done by starting the query with
869 "servers=x:y:z;", where each item in the list may take one of two forms:
871 (1) If it is just a host name, the appropriate global option (mysql_servers
872 or pgsql_servers) is searched for a host of the same name, and the
873 remaining parameters (database, user, password) are taken from there.
875 (2) If it contains any slashes, it is taken as a complete parameter set.
877 The list of servers is used in exactly the same was as the global list.
878 Once a connection to a server has happened and a query has been
879 successfully executed, processing of the lookup ceases.
881 This feature is intended for use in master/slave situations where updates
882 are occurring, and one wants to update a master rather than a slave. If the
883 masters are in the list for reading, you might have:
885 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
887 In an updating lookup, you could then write
889 ${lookup mysql{servers=master; UPDATE ...}
891 If, on the other hand, the master is not to be used for reading lookups:
893 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
895 you can still update the master by
897 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
899 11. The message_body_newlines option (default FALSE, for backwards
900 compatibility) can be used to control whether newlines are present in
901 $message_body and $message_body_end. If it is FALSE, they are replaced by
908 1. There is a new log selector called smtp_no_mail, which is not included in
909 the default setting. When it is set, a line is written to the main log
910 whenever an accepted SMTP connection terminates without having issued a
913 2. When an item in a dnslists list is followed by = and & and a list of IP
914 addresses, the behaviour was not clear when the lookup returned more than
915 one IP address. This has been solved by the addition of == and =& for "all"
916 rather than the default "any" matching.
918 3. Up till now, the only control over which cipher suites GnuTLS uses has been
919 for the cipher algorithms. New options have been added to allow some of the
920 other parameters to be varied.
922 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
923 set, Exim compiles a runtime option called disable_fsync.
925 5. There is a new variable called $smtp_count_at_connection_start.
927 6. There's a new control called no_pipelining.
929 7. There are two new variables called $sending_ip_address and $sending_port.
930 These are set whenever an SMTP connection to another host has been set up.
932 8. The expansion of the helo_data option in the smtp transport now happens
933 after the connection to the server has been made.
935 9. There is a new expansion operator ${rfc2047d: that decodes strings that
936 are encoded as per RFC 2047.
938 10. There is a new log selector called "pid", which causes the current process
939 id to be added to every log line, in square brackets, immediately after the
942 11. Exim has been modified so that it flushes SMTP output before implementing
943 a delay in an ACL. It also flushes the output before performing a callout,
944 as this can take a substantial time. These behaviours can be disabled by
945 obeying control = no_delay_flush or control = no_callout_flush,
946 respectively, at some earlier stage of the connection.
948 12. There are two new expansion conditions that iterate over a list. They are
949 called forany and forall.
951 13. There's a new global option called dsn_from that can be used to vary the
952 contents of From: lines in bounces and other automatically generated
953 messages ("delivery status notifications" - hence the name of the option).
955 14. The smtp transport has a new option called hosts_avoid_pipelining.
957 15. By default, exigrep does case-insensitive matches. There is now a -I option
958 that makes it case-sensitive.
960 16. A number of new features ("addresses", "map", "filter", and "reduce") have
961 been added to string expansions to make it easier to process lists of
962 items, typically addresses.
964 17. There's a new ACL modifier called "continue". It does nothing of itself,
965 and processing of the ACL always continues with the next condition or
966 modifier. It is provided so that the side effects of expanding its argument
969 18. It is now possible to use newline and other control characters (those with
970 values less than 32, plus DEL) as separators in lists.
972 19. The exigrep utility now has a -v option, which inverts the matching
975 20. The host_find_failed option in the manualroute router can now be set to
982 No new features were added to 4.66.
988 No new features were added to 4.65.
994 1. ACL variables can now be given arbitrary names, as long as they start with
995 "acl_c" or "acl_m" (for connection variables and message variables), are at
996 least six characters long, with the sixth character being either a digit or
999 2. There is a new ACL modifier called log_reject_target. It makes it possible
1000 to specify which logs are used for messages about ACL rejections.
1002 3. There is a new authenticator called "dovecot". This is an interface to the
1003 authentication facility of the Dovecot POP/IMAP server, which can support a
1004 number of authentication methods.
1006 4. The variable $message_headers_raw provides a concatenation of all the
1007 messages's headers without any decoding. This is in contrast to
1008 $message_headers, which does RFC2047 decoding on the header contents.
1010 5. In a DNS black list, if two domain names, comma-separated, are given, the
1011 second is used first to do an initial check, making use of any IP value
1012 restrictions that are set. If there is a match, the first domain is used,
1013 without any IP value restrictions, to get the TXT record.
1015 6. All authenticators now have a server_condition option.
1017 7. There is a new command-line option called -Mset. It is useful only in
1018 conjunction with -be (that is, when testing string expansions). It must be
1019 followed by a message id; Exim loads the given message from its spool
1020 before doing the expansions.
1022 8. Another similar new command-line option is called -bem. It operates like
1023 -be except that it must be followed by the name of a file that contains a
1026 9. When an address is delayed because of a 4xx response to a RCPT command, it
1027 is now the combination of sender and recipient that is delayed in
1028 subsequent queue runs until its retry time is reached.
1030 10. Unary negation and the bitwise logical operators and, or, xor, not, and
1031 shift, have been added to the eval: and eval10: expansion items.
1033 11. The variables $interface_address and $interface_port have been renamed
1034 as $received_ip_address and $received_port, to make it clear that they
1035 relate to message reception rather than delivery. (The old names remain
1036 available for compatibility.)
1038 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
1039 to vary the message that is sent when an SMTP command is accepted.
1045 1. There is a new Boolean option called filter_prepend_home for the redirect
1048 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
1049 start of receiving a non-SMTP message, before any of the message has been
1052 3. When an SMTP error message is specified in a "message" modifier in an ACL,
1053 or in a :fail: or :defer: message in a redirect router, Exim now checks the
1054 start of the message for an SMTP error code.
1056 4. There is a new parameter for LDAP lookups called "referrals", which takes
1057 one of the settings "follow" (the default) or "nofollow".
1059 5. Version 20070721.2 of exipick now included, offering these new options:
1061 After all other sorting options have bee processed, reverse order
1062 before displaying messages (-R is synonym).
1064 Randomize order of matching messages before displaying.
1066 Instead of displaying the matching messages, display the sum
1068 --sort <variable>[,<variable>...]
1069 Before displaying matching messages, sort the messages according to
1070 each messages value for each variable.
1072 Negate the value for every test (returns inverse output from the
1073 same criteria without --not).
1079 1. The ${readsocket expansion item now supports Internet domain sockets as well
1080 as Unix domain sockets. If the first argument begins "inet:", it must be of
1081 the form "inet:host:port". The port is mandatory; it may be a number or the
1082 name of a TCP port in /etc/services. The host may be a name, or it may be an
1083 IP address. An ip address may optionally be enclosed in square brackets.
1084 This is best for IPv6 addresses. For example:
1086 ${readsocket{inet:[::1]:1234}{<request data>}...
1088 Only a single host name may be given, but if looking it up yield more than
1089 one IP address, they are each tried in turn until a connection is made. Once
1090 a connection has been made, the behaviour is as for ${readsocket with a Unix
1093 2. If a redirect router sets up file or pipe deliveries for more than one
1094 incoming address, and the relevant transport has batch_max set greater than
1095 one, a batch delivery now occurs.
1097 3. The appendfile transport has a new option called maildirfolder_create_regex.
1098 Its value is a regular expression. For a maildir delivery, this is matched
1099 against the maildir directory; if it matches, Exim ensures that a
1100 maildirfolder file is created alongside the new, cur, and tmp directories.
1106 The documentation is up-to-date for the 4.61 release. Major new features since
1107 the 4.60 release are:
1109 . An option called disable_ipv6, to disable the use of IPv6 completely.
1111 . An increase in the number of ACL variables to 20 of each type.
1113 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
1114 $2, $3, (though those are still set) because the numeric variables get used
1115 for other things in complicated expansions.
1117 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
1119 . It is possible to use setclassresources() on some BSD OS to control the
1120 resources used in pipe deliveries.
1122 . A new ACL modifier called add_header, which can be used with any verb.
1124 . More errors are detectable in retry rules.
1126 There are a number of other additions too.
1132 The documentation is up-to-date for the 4.60 release. Major new features since
1133 the 4.50 release are:
1135 . Support for SQLite.
1137 . Support for IGNOREQUOTA in LMTP.
1139 . Extensions to the "submission mode" features.
1141 . Support for Client SMTP Authorization (CSA).
1143 . Support for ratelimiting hosts and users.
1145 . New expansion items to help with the BATV "prvs" scheme.
1147 . A "match_ip" condition, that matches an IP address against a list.
1149 There are many more minor changes.
git://git.exim.org / users / heiko / exim.git / blob