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. The fast-ramp two phase queue run support, previously experimental, is
13 now supported by default.
15 2. The native SRS support, previously experimental, is now supported. It is
16 not built unless specified in the Local/Makefile.
18 3. TLS resumption support, previously experimental, is now supported and
19 included in default builds.
21 4. Single-key LMDB lookups, previously experimental, are now supported.
22 The support is not built unless specified in the Local/Makefile.
24 5. Option "message_linelength_limit" on the smtp transport to enforce (by
25 default) the RFC 998 character limit.
27 6. An option to ignore the cache on a lookup.
29 7. Quota checking during reception (i.e. at SMTP time) for appendfile-
30 transport-managed quotas.
32 8. Sqlite lookups accept a "file=<path>" option to specify a per-operation
33 db file, replacing the previous prefix to the SQL string (which had
34 issues when the SQL used tainted values).
36 9. Lsearch lookups accept a "ret=full" option, to return both the portion
37 of the line matching the key, and the remainder.
39 10. A command-line option to have a daemon not create a notifier socket.
41 11. Faster TLS startup. When various configuration options contain no
42 expandable elements, the information can be preloaded and cached rather
43 than the provious behaviour of always loading at startup time for every
44 connection. This helps particularly for the CA bundle.
46 12. Proxy Protocol Timeout is configurable via "proxy_protocol_timeout"
49 13. Option "smtp_accept_msx_per_connection" is now expanded.
51 13. A main config option "allow_insecure_tainted_data" allows to turn
52 taint errors into warnings.
57 1. EXPERIMENTAL_SRS_NATIVE optional build feature. See the experimental.spec
60 2. Channel-binding for authenticators is now supported under OpenSSL.
61 Previously it was GnuTLS-only.
65 4. Client-side support in the gsasl authenticator. Tested against the
66 plaintext driver for PLAIN; only against itself for SCRAM-SHA-1 and
67 SCRAM-SHA-1-PLUS methods.
69 5. Server-side support in the gsasl authenticator for encrypted passwords, as
70 an alternate for the existing plaintext.
72 6. Variable $local_part_data now also set by router check_local_user option,
73 with an de-tainted version of $local_part.
75 7. Named-list definitions can now be prefixed "hide" so that "-bP" commands do
76 not output the content. Previously this could only be done on options.
78 8. As an experimental feature, the dovecot authentication driver supports inet
79 sockets. Previously it was unix-domain sockets only.
81 9. The ACL control "queue_only" can also be spelled "queue", and now takes an
82 option "first_pass_route" to do the same as a "-odqs" on the command line.
84 10. Items specified for the router and transport headers_remove option can use
85 a trailing asterisk to specify globbing.
87 11. New $queue_size variable.
89 12. New variables $local_part_{pre,suf}fix_v.
91 13. New main option "sqlite_dbfile", for use in preference to prefixing the
92 lookup string. The older method fails when tainted variables are used
93 in the lookup, as the filename becomes tainted. The new method keeps the
96 14. Options on the dsearch lookup, to return the full path and to filter
97 filetypes for matching.
99 15. Options on pgsql and mysql lookups, to specify server separate from the
102 16. An option on all single-key lookups, to return (on a hit) a de-tainted
103 version of the lookup key rather than the looked-up data.
105 17. $domain_data and $local_part_data are now set by all list-match successes.
106 Previously only list items that performed lookups did so.
107 Also, matching list items that are tail-match or RE-match now set the
108 numeric variables $0 (etc) in the same way os other RE matches.
110 18. Expansion item ${listquote {<char} {<item>}}.
112 19. An option for the ${readsocket {}{}{}} expansion to make the result data
115 20. dkim_verify_min_keysizes, a list of minimum acceptable public-key sizes.
117 21. bounce_message_file and warn_message_file are now expanded before use.
119 22. New main config option spf_smtp_comment_template to customise the
120 $spf_smtp_comment variable
127 1. An "external" authenticator, per RFC 4422 Appendix A.
129 2. A JSON lookup type, and JSON variants of the forall/any expansion conditions.
131 3. Variables $tls_in_cipher_std, $tls_out_cipher_std giving the RFC names
134 4. Log_selectors "msg_id" (on by default) and "msg_id_created".
136 5. A case_insensitive option for verify=not_blind.
138 6. EXPERIMENTAL_TLS_RESUME optional build feature. See the experimental.spec
141 7. A main option exim_version to override the version Exim
142 reports in verious places ($exim_version, $version_number).
144 8. Expansion operator ${sha2_N:} for N=256, 384, 512.
146 9. Router variables, $r_... settable from router options and usable in routers
149 10. The spf lookup now supports IPv6.
151 11. Main options for DKIM verify to filter hash and key types.
153 12. With TLS1.3, support for full-chain OCSP stapling.
155 13. Dual-certificate stacks on servers now support OCSP stapling, under OpenSSL.
157 14: An smtp:ehlo transport event, for observability of the remote offered features.
159 15: Support under OpenSSL for writing NSS-style key files for packet-capture
160 decode. The environment variable SSLKEYLOGFILE is used; if an absolute path
161 it must indicate a file under the spool directory; if relative the the spool
162 directory is prepended. Works on the server side only. Support under
163 GnuTLS was already there, being done purely by the library (server side
164 only, and exim must be run as root).
166 16: Command-line option to move messages from one named queue to another.
168 17. Variables $tls_in_ver, $tls_out_ver.
174 1. ${l_header:<name>} and ${l_h:<name>} expansion items, giving a colon-sep
175 list when there are multiple headers having a given name. This matters
176 when individual headers are wrapped onto multiple lines; with previous
177 facilities hard to parse.
179 2. The ${readsocket } expansion item now takes a "tls" option, doing the
182 3. EXPERIMENTAL_REQUIRETLS and EXPERIMENTAL_PIPE_CONNECT optional build
183 features. See the experimental.spec file.
185 4. If built with SUPPORT_I18N a "utf8_downconvert" option on the smtp transport.
187 5. A "pipelining" log_selector.
189 6. Builtin macros for supported log_selector and openssl_options values.
191 7. JSON variants of the ${extract } expansion item.
193 8. A "noutf8" debug option, for disabling the UTF-8 characters in debug output.
195 9. TCP Fast Open support on MacOS.
200 1. Dual-certificate stacks on servers now support OCSP stapling, under GnuTLS
201 version 3.5.6 or later.
203 2. DANE is now supported under GnuTLS version 3.0.0 or later. Both GnuTLS and
204 OpenSSL versions are moved to mainline support from Experimental.
205 New SMTP transport option "dane_require_tls_ciphers".
207 3. Feature macros for the compiled-in set of malware scanner interfaces.
209 4. SPF support is promoted from Experimental to mainline status. The template
210 src/EDITME makefile does not enable its inclusion.
212 5. Logging control for DKIM verification. The existing DKIM log line is
213 controlled by a "dkim_verbose" selector which is _not_ enabled by default.
214 A new tag "DKIM=<domain>" is added to <= lines by default, controlled by
215 a "dkim" log_selector.
217 6. Receive duration on <= lines, under a new log_selector "receive_time".
219 7. Options "ipv4_only" and "ipv4_prefer" on the dnslookup router and on
220 routing rules in the manualroute router.
222 8. Expansion item ${sha3:<string>} / ${sha3_<N>:<string>} now also supported
223 under OpenSSL version 1.1.1 or later.
225 9. DKIM operations can now use the Ed25519 algorithm in addition to RSA, under
226 GnuTLS 3.6.0 or OpenSSL 1.1.1 or later.
228 10. Builtin feature-macros _CRYPTO_HASH_SHA3 and _CRYPTO_SIGN_ED25519, library
231 11. "exim -bP macro <name>" returns caller-usable status.
233 12. Expansion item ${authresults {<machine>}} for creating an
234 Authentication-Results: header.
236 13. EXPERIMENTAL_ARC. See the experimental.spec file.
237 See also new util/renew-opendmarc-tlds.sh script for use with DMARC/ARC.
239 14: A dane:fail event, intended to facilitate reporting.
241 15. "Lightweight" support for Redis Cluster. Requires redis_servers list to
242 contain all the servers in the cluster, all of which must be reachable from
243 the running exim instance. If the cluster has master/slave replication, the
244 list must contain all the master and slave servers.
246 16. Add an option to the Avast scanner interface: "pass_unscanned". This
247 allows to treat unscanned files as clean. Files may be unscanned for
248 several reasons: decompression bombs, broken archives.
254 1. PKG_CONFIG_PATH can now be set in Local/Makefile;
255 wildcards will be expanded, values are collapsed.
257 2. The ${readsocket } expansion now takes an option to not shutdown the
258 connection after sending the query string. The default remains to do so.
260 3. An smtp transport option "hosts_noproxy_tls" to control whether multiple
261 deliveries on a single TCP connection can maintain a TLS connection
262 open. By default disabled for all hosts, doing so saves the cost of
263 making new TLS sessions, at the cost of having to proxy the data via
264 another process. Logging is also affected.
266 4. A malware connection type for the FPSCAND protocol.
268 5. An option for recipient verify callouts to hold the connection open for
269 further recipients and for delivery.
271 6. The reproducible build $SOURCE_DATE_EPOCH environment variable is now
274 7. Optionally, an alternate format for spool data-files which matches the
275 wire format - meaning more efficient reception and transmission (at the
276 cost of difficulty with standard Unix tools). Only used for messages
277 received using the ESMTP CHUNKING option, and when a new main-section
278 option "spool_wireformat" (false by default) is set.
280 8. New main configuration option "commandline_checks_require_admin" to
281 restrict who can use various introspection options.
283 9. New option modifier "no_check" for quota and quota_filecount
284 appendfile transport.
286 10. Variable $smtp_command_history returning a comma-sep list of recent
289 11. Millisecond timetamps in logs, on log_selector "millisec". Also affects
290 log elements QT, DT and D, and timstamps in debug output.
292 12. TCP Fast Open logging. As a server, logs when the SMTP banner was sent
293 while still in SYN_RECV state; as a client logs when the connection
294 is opened with a TFO cookie.
296 13. DKIM support for multiple signing, by domain and/or key-selector.
297 DKIM support for multiple hashes, and for alternate-identity tags.
298 Builtin macro with default list of signed headers.
299 Better syntax for specifying oversigning.
300 The DKIM ACL can override verification status, and status is visible in
303 14. Exipick understands -C|--config for an alternative Exim
306 15. TCP Fast Open used, with data-on-SYN, for client SMTP via SOCKS5 proxy,
307 for ${readsocket } expansions, and for ClamAV.
309 16. The "-be" expansion test mode now supports macros. Macros are expanded
310 in test lines, and new macros can be defined.
312 17. Support for server-side dual-certificate-stacks (eg. RSA + ECDSA).
318 1. Allow relative config file names for ".include"
320 2. A main-section config option "debug_store" to control the checks on
321 variable locations during store-reset. Normally false but can be enabled
322 when a memory corruption issue is suspected on a production system.
328 1. The new perl_taintmode option allows to run the embedded perl
329 interpreter in taint mode.
331 2. New log_selector: dnssec, adds a "DS" tag to acceptance and delivery lines.
333 3. Speculative debugging, via a "kill" option to the "control=debug" ACL
336 4. New expansion item ${sha3:<string>} / ${sha3_<N>:<string>}.
337 N can be 224, 256 (default), 384, 512.
338 With GnuTLS 3.5.0 or later, only.
340 5. Facility for named queues: A command-line argument can specify
341 the queue name for a queue operation, and an ACL modifier can set
342 the queue to be used for a message. A $queue_name variable gives
345 6. New expansion operators base32/base32d.
347 7. The CHUNKING ESMTP extension from RFC 3030. May give some slight
348 performance increase and network load decrease. Main config option
349 chunking_advertise_hosts, and smtp transport option hosts_try_chunking
352 8. LMDB lookup support, as Experimental. Patch supplied by Andrew Colin Kissa.
354 9. Expansion operator escape8bit, like escape but not touching newline etc..
356 10. Feature macros, generated from compile options. All start with "_HAVE_"
357 and go on with some roughly recognisable name. Driver macros, for
358 router, transport and authentication drivers; names starting with "_DRIVER_".
359 Option macros, for each configuration-file option; all start with "_OPT_".
360 Use the "-bP macros" command-line option to see what is present.
362 11. Integer values for options can take a "G" multiplier.
364 12. defer=pass option for the ACL control cutthrough_delivery, to reflect 4xx
365 returns from the target back to the initiator, rather than spooling the
368 13. New built-in constants available for tls_dhparam and default changed.
370 14. If built with EXPERIMENTAL_QUEUEFILE, a queuefile transport, for writing
371 out copies of the message spool files for use by 3rd-party scanners.
373 15. A new option on the smtp transport, hosts_try_fastopen. If the system
374 supports it (on Linux it must be enabled in the kernel by the sysadmin)
375 try to use RFC 7413 "TCP Fast Open". No data is sent on the SYN segment
376 but it permits a peer that also supports the facility to send its SMTP
377 banner immediately after the SYN,ACK segment rather then waiting for
378 another ACK - so saving up to one roundtrip time. Because it requires
379 previous communication with the peer (we save a cookie from it) this
380 will only become active on frequently-contacted destinations.
382 16. A new syslog_pid option to suppress PID duplication in syslog lines.
388 1. The ACL conditions regex and mime_regex now capture substrings
389 into numeric variables $regex1 to 9, like the "match" expansion condition.
391 2. New $callout_address variable records the address used for a spam=,
392 malware= or verify= callout.
394 3. Transports now take a "max_parallel" option, to limit concurrency.
396 4. Expansion operators ${ipv6norm:<string>} and ${ipv6denorm:<string>}.
397 The latter expands to a 8-element colon-sep set of hex digits including
398 leading zeroes. A trailing ipv4-style dotted-decimal set is converted
399 to hex. Pure ipv4 addresses are converted to IPv4-mapped IPv6.
400 The former operator strips leading zeroes and collapses the longest
401 set of 0-groups to a double-colon.
403 5. New "-bP config" support, to dump the effective configuration.
405 6. New $dkim_key_length variable.
407 7. New base64d and base64 expansion items (the existing str2b64 being a
408 synonym of the latter). Add support in base64 for certificates.
410 8. New main configuration option "bounce_return_linesize_limit" to
411 avoid oversize bodies in bounces. The default value matches RFC
414 9. New $initial_cwd expansion variable.
420 1. Support for using the system standard CA bundle.
422 2. New expansion items $config_file, $config_dir, containing the file
423 and directory name of the main configuration file. Also $exim_version.
425 3. New "malware=" support for Avast.
427 4. New "spam=" variant option for Rspamd.
429 5. Assorted options on malware= and spam= scanners.
431 6. A command-line option to write a comment into the logfile.
433 7. If built with EXPERIMENTAL_SOCKS feature enabled, the smtp transport can
434 be configured to make connections via socks5 proxies.
436 8. If built with EXPERIMENTAL_INTERNATIONAL, support is included for
437 the transmission of UTF-8 envelope addresses.
439 9. If built with EXPERIMENTAL_INTERNATIONAL, an expansion item for a commonly
440 used encoding of Maildir folder names.
442 10. A logging option for slow DNS lookups.
444 11. New ${env {<variable>}} expansion.
446 12. A non-SMTP authenticator using information from TLS client certificates.
448 13. Main option "tls_eccurve" for selecting an Elliptic Curve for TLS.
449 Patch originally by Wolfgang Breyha.
451 14. Main option "dns_trust_aa" for trusting your local nameserver at the
452 same level as DNSSEC.
457 1. If built with EXPERIMENTAL_DANE feature enabled, Exim will follow the
458 DANE SMTP draft to assess a secure chain of trust of the certificate
459 used to establish the TLS connection based on a TLSA record in the
460 domain of the sender.
462 2. The EXPERIMENTAL_TPDA feature has been renamed to EXPERIMENTAL_EVENT
463 and several new events have been created. The reason is because it has
464 been expanded beyond just firing events during the transport phase. Any
465 existing TPDA transport options will have to be rewritten to use a new
466 $event_name expansion variable in a condition. Refer to the
467 experimental-spec.txt for details and examples.
469 3. The EXPERIMENTAL_CERTNAMES features is an enhancement to verify that
470 server certs used for TLS match the result of the MX lookup. It does
471 not use the same mechanism as DANE.
481 1. If built with the EXPERIMENTAL_PROXY feature enabled, Exim can be
482 configured to expect an initial header from a proxy that will make the
483 actual external source IP:host be used in exim instead of the IP of the
484 proxy that is connecting to it.
486 2. New verify option header_names_ascii, which will check to make sure
487 there are no non-ASCII characters in header names. Exim itself handles
488 those non-ASCII characters, but downstream apps may not, so Exim can
489 detect and reject if those characters are present.
491 3. New expansion operator ${utf8clean:string} to replace malformed UTF8
492 codepoints with valid ones.
494 4. New malware type "sock". Talks over a Unix or TCP socket, sending one
495 command line and matching a regex against the return data for trigger
496 and a second regex to extract malware_name. The mail spoolfile name can
497 be included in the command line.
499 5. The smtp transport now supports options "tls_verify_hosts" and
500 "tls_try_verify_hosts". If either is set the certificate verification
501 is split from the encryption operation. The default remains that a failed
502 verification cancels the encryption.
504 6. New SERVERS override of default ldap server list. In the ACLs, an ldap
505 lookup can now set a list of servers to use that is different from the
508 7. New command-line option -C for exiqgrep to specify alternate exim.conf
509 file when searching the queue.
511 8. OCSP now supports GnuTLS also, if you have version 3.1.3 or later of that.
513 9. Support for DNSSEC on outbound connections.
515 10. New variables "tls_(in,out)_(our,peer)cert" and expansion item
516 "certextract" to extract fields from them. Hash operators md5 and sha1
517 work over them for generating fingerprints, and a new sha256 operator
520 11. PRDR is now supported dy default.
522 12. OCSP stapling is now supported by default.
524 13. If built with the EXPERIMENTAL_DSN feature enabled, Exim will output
525 Delivery Status Notification messages in MIME format, and negotiate
526 DSN features per RFC 3461.
532 1. New command-line option -bI:sieve will list all supported sieve extensions
533 of this Exim build on standard output, one per line.
534 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
535 query this to establish the correct list to include in the protocol's
536 SIEVE capability line.
538 2. If the -n option is combined with the -bP option, then the name of an
539 emitted option is not output, only the value (if visible to you).
540 For instance, "exim -n -bP pid_file_path" should just emit a pathname
541 followed by a newline, and no other text.
543 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
544 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
545 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
546 acceptable for security. (Option accepted but ignored if using OpenSSL).
547 Defaults to 1024, the old value. May be lowered only to 512, or raised as
548 far as you like. Raising this may hinder TLS interoperability with other
549 sites and is not currently recommended. Lowering this will permit you to
550 establish a TLS session which is not as secure as you might like.
552 Unless you really know what you are doing, leave it alone.
554 4. If not built with DISABLE_DNSSEC, Exim now has the main option
555 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
556 to send the DO flag to your recursive resolver. If you have a recursive
557 resolver, which can set the Authenticated Data (AD) flag in results, Exim
558 can now detect this. Exim does not perform validation itself, instead
559 relying upon a trusted path to the resolver.
561 Current status: work-in-progress; $sender_host_dnssec variable added.
563 5. DSCP support for outbound connections: on a transport using the smtp driver,
564 set "dscp = ef", for instance, to cause the connections to have the relevant
565 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
567 Similarly for inbound connections, there is a new control modifier, dscp,
568 so "warn control = dscp/ef" in the connect ACL, or after authentication.
570 Supported values depend upon system libraries. "exim -bI:dscp" to list the
571 ones Exim knows of. You can also set a raw number 0..0x3F.
573 6. The -G command-line flag is no longer ignored; it is now equivalent to an
574 ACL setting "control = suppress_local_fixups". The -L command-line flag
575 is now accepted and forces use of syslog, with the provided tag as the
576 process name. A few other flags used by Sendmail are now accepted and
579 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
580 ACL modifier; works for single-recipient mails which are received on and
581 deliverable via SMTP. Using the connection made for a recipient verify,
582 if requested before the verify, or a new one made for the purpose while
583 the inbound connection is still active. The bulk of the mail item is copied
584 direct from the inbound socket to the outbound (as well as the spool file).
585 When the source notifies the end of data, the data acceptance by the destination
586 is negotiated before the acceptance is sent to the source. If the destination
587 does not accept the mail item, for example due to content-scanning, the item
588 is not accepted from the source and therefore there is no need to generate
589 a bounce mail. This is of benefit when providing a secondary-MX service.
590 The downside is that delays are under the control of the ultimate destination
593 The Received-by: header on items delivered by cutthrough is generated
594 early in reception rather than at the end; this will affect any timestamp
595 included. The log line showing delivery is recorded before that showing
596 reception; it uses a new ">>" tag instead of "=>".
598 To support the feature, verify-callout connections can now use ESMTP and TLS.
599 The usual smtp transport options are honoured, plus a (new, default everything)
600 hosts_verify_avoid_tls.
602 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
603 for specific access to the information for each connection. The old names
604 are present for now but deprecated.
606 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
608 8. New expansion operators ${listnamed:name} to get the content of a named list
609 and ${listcount:string} to count the items in a list.
611 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
612 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
613 modules. For some situations this is desirable, but we expect admin in
614 those situations to know they want the feature. More commonly, it means
615 that GUI user modules get loaded and are broken by the setuid Exim being
616 unable to access files specified in environment variables and passed
617 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
618 unless this new option is set.
620 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
621 so have also added a build option which can be used to build Exim with GnuTLS
622 but without trying to use any kind of PKCS11 support. Uncomment this in the
625 AVOID_GNUTLS_PKCS11=yes
627 10. The "acl = name" condition on an ACL now supports optional arguments.
628 New expansion item "${acl {name}{arg}...}" and expansion condition
629 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
630 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
631 Variable $acl_narg contains the number of arguments. If the ACL sets
632 a "message =" value this becomes the result of the expansion item,
633 or the value of $value for the expansion condition. If the ACL returns
634 accept the expansion condition is true; if reject, false. A defer
635 return results in a forced fail.
637 11. Routers and transports can now have multiple headers_add and headers_remove
638 option lines. The concatenated list is used.
640 12. New ACL modifier "remove_header" can remove headers before message gets
641 handled by routers/transports.
643 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
644 "aaaa" and "a" lookups is done and the full set of results returned.
646 14. New expansion variable $headers_added with content from ACL add_header
647 modifier (but not yet added to message).
649 15. New 8bitmime status logging option for received messages. Log field "M8S".
651 16. New authenticated_sender logging option, adding to log field "A".
653 17. New expansion variables $router_name and $transport_name. Useful
654 particularly for debug_print as -bt command-line option does not
655 require privilege whereas -d does.
657 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
658 proposed extension to SMTP from Eric Hall.
660 19. The pipe transport has gained the force_command option, to allow
661 decorating commands from user .forward pipe aliases with prefix
662 wrappers, for instance.
664 20. Callout connections can now AUTH; the same controls as normal delivery
667 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
668 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
669 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
670 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
671 dmarc_status. It adds new control flags dmarc_disable_verify and
672 dmarc_enable_forensic. The default for the dmarc_tld_file option is
673 "/etc/exim/opendmarc.tlds" and can be changed via EDITME.
675 22. Add expansion variable $authenticated_fail_id, which is the username
676 provided to the authentication method which failed. It is available
677 for use in subsequent ACL processing (typically quit or notquit ACLs).
679 23. New ACL modifier "udpsend" can construct a UDP packet to send to a given
682 24. New ${hexquote:..string..} expansion operator converts non-printable
683 characters in the string to \xNN form.
685 25. Experimental TPDA (Transport Post Delivery Action) function added.
686 Patch provided by Axel Rau.
688 26. Experimental Redis lookup added. Patch provided by Warren Baker.
694 1. New authenticator driver, "gsasl". Server-only (at present).
695 This is a SASL interface, licensed under GPL, which can be found at
696 http://www.gnu.org/software/gsasl/.
697 This system does not provide sources of data for authentication, so
698 careful use needs to be made of the conditions in Exim.
700 2. New authenticator driver, "heimdal_gssapi". Server-only.
701 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
702 is no longer honoured for setuid programs by Heimdal. Use the
703 "server_keytab" option to point to the keytab.
705 3. The "pkg-config" system can now be used when building Exim to reference
706 cflags and library information for lookups and authenticators, rather
707 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
708 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
709 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
711 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
712 find the headers and libraries for PCRE.
714 4. New expansion variable $tls_bits.
716 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
717 be joined together with ASCII NUL characters to construct the key to pass
718 into the DBM library. Can be used with gsasl to access sasldb2 files as
721 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
723 Avoid release 1.0.1a if you can. Note that the default value of
724 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
725 increased susceptibility to attack. This may still have interoperability
726 implications for very old clients (see version 4.31 change 37) but
727 administrators can choose to make the trade-off themselves and restore
728 compatibility at the cost of session security.
730 7. Use of the new expansion variable $tls_sni in the main configuration option
731 tls_certificate will cause Exim to re-expand the option, if the client
732 sends the TLS Server Name Indication extension, to permit choosing a
733 different certificate; tls_privatekey will also be re-expanded. You must
734 still set these options to expand to valid files when $tls_sni is not set.
736 The SMTP Transport has gained the option tls_sni, which will set a hostname
737 for outbound TLS sessions, and set $tls_sni too.
739 A new log_selector, +tls_sni, has been added, to log received SNI values
740 for Exim as a server.
742 8. The existing "accept_8bitmime" option now defaults to true. This means
743 that Exim is deliberately not strictly RFC compliant. We're following
744 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
745 Those who disagree, or know that they are talking to mail servers that,
746 even today, are not 8-bit clean, need to turn off this option.
748 9. Exim can now be started with -bw (with an optional timeout, given as
749 -bw<timespec>). With this, stdin at startup is a socket that is
750 already listening for connections. This has a more modern name of
751 "socket activation", but forcing the activated socket to fd 0. We're
752 interested in adding more support for modern variants.
754 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
755 for numbers indicates multiplication by 1024^3.
757 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
758 gnutls_require_mac & gnutls_require_protocols are no longer supported.
759 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
760 string, documentation for which is at:
761 http://www.gnutls.org/manual/html_node/Priority-Strings.html
763 SNI support has been added to Exim's GnuTLS integration too.
765 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
766 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
768 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
769 is now available. If the contents of the file are valid, then Exim will
770 send that back in response to a TLS status request; this is OCSP Stapling.
771 Exim will not maintain the contents of the file in any way: administrators
772 are responsible for ensuring that it is up-to-date.
774 See "experimental-spec.txt" for more details.
776 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
777 identically to TXT record lookups.
779 14. New expansion variable $tod_epoch_l for higher-precision time.
781 15. New global option tls_dh_max_bits, defaulting to current value of NSS
782 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
783 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
785 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
786 Option can now be a path or an identifier for a standard prime.
787 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
788 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
791 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
792 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
793 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
799 1. New options for the ratelimit ACL condition: /count= and /unique=.
800 The /noupdate option has been replaced by a /readonly option.
802 2. The SMTP transport's protocol option may now be set to "smtps", to
803 use SSL-on-connect outbound.
805 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
806 there is a problem talking to the AV scanner, or the AV scanner running.
808 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
809 and check if the search item is a member of the list. This does not
810 support named lists, but does subject the list part to string expansion.
812 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
813 built, Exim no longer performs string expansion on the second string of
814 the match_* expansion conditions: "match_address", "match_domain",
815 "match_ip" & "match_local_part". Named lists can still be used.
821 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
822 or off in the resolver library.
828 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
829 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
830 libraries. The following global options have been added in support of
831 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
832 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
834 2. The pipe transport now takes a boolean option, "freeze_signal", default
835 false. When true, if the external delivery command exits on a signal then
836 Exim will freeze the message in the queue, instead of generating a bounce.
838 3. Log filenames may now use %M as an escape, instead of %D (still available).
839 The %M pattern expands to yyyymm, providing month-level resolution.
841 4. The $message_linecount variable is now updated for the maildir_tag option,
842 in the same way as $message_size, to reflect the real number of lines,
843 including any header additions or removals from transport.
845 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
846 Exim now selects entries randomly, to better scale in a cluster setup.
852 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
853 the flaw permitted the Exim run-time user to cause root to append to
854 arbitrary files of the attacker's choosing, with the content based
855 on content supplied by the attacker.
857 2. Exim now supports loading some lookup types at run-time, using your
858 platform's dlopen() functionality. This has limited platform support
859 and the intention is not to support every variant, it's limited to
860 dlopen(). This permits the main Exim binary to not be linked against
861 all the libraries needed for all the lookup types.
867 NOTE: this version is not guaranteed backwards-compatible, please read the
868 items below carefully
870 1. A new main configuration option, "openssl_options", is available if Exim
871 is built with SSL support provided by OpenSSL. The option allows
872 administrators to specify OpenSSL options to be used on connections;
873 typically this is to set bug compatibility features which the OpenSSL
874 developers have not enabled by default. There may be security
875 consequences for certain options, so these should not be changed
878 2. A new pipe transport option, "permit_coredumps", may help with problem
879 diagnosis in some scenarios. Note that Exim is typically installed as
880 a setuid binary, which on most OSes will inhibit coredumps by default,
881 so that safety mechanism would have to be overridden for this option to
882 be able to take effect.
884 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
885 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
886 Note that this switches Exim to use a new API ("INSTREAM") and a future
887 release of ClamAV will remove support for the old API ("STREAM").
889 The av_scanner option, when set to "clamd", now takes an optional third
890 part, "local", which causes Exim to pass a filename to ClamAV instead of
891 the file content. This is the same behaviour as when clamd is pointed at
892 a Unix-domain socket. For example:
894 av_scanner = clamd:192.0.2.3 1234:local
896 ClamAV's ExtendedDetectionInfo response format is now handled.
898 4. There is now a -bmalware option, restricted to admin users. This option
899 takes one parameter, a filename, and scans that file with Exim's
900 malware-scanning framework. This is intended purely as a debugging aid
901 to ensure that Exim's scanning is working, not to replace other tools.
902 Note that the ACL framework is not invoked, so if av_scanner references
903 ACL variables without a fallback then this will fail.
905 5. There is a new expansion operator, "reverse_ip", which will reverse IP
906 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
908 ${reverse_ip:192.0.2.4}
910 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
911 -> 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
913 6. There is a new ACL control called "debug", to enable debug logging.
914 This allows selective logging of certain incoming transactions within
915 production environments, with some care. It takes two options, "tag"
916 and "opts"; "tag" is included in the filename of the log and "opts"
917 is used as per the -d<options> command-line option. Examples, which
918 don't all make sense in all contexts:
921 control = debug/tag=.$sender_host_address
922 control = debug/opts=+expand+acl
923 control = debug/tag=.$message_exim_id/opts=+expand
925 7. It has always been implicit in the design and the documentation that
926 "the Exim user" is not root. src/EDITME said that using root was
927 "very strongly discouraged". This is not enough to keep people from
928 shooting themselves in the foot in days when many don't configure Exim
929 themselves but via package build managers. The security consequences of
930 running various bits of network code are severe if there should be bugs in
931 them. As such, the Exim user may no longer be root. If configured
932 statically, Exim will refuse to build. If configured as ref:user then Exim
933 will exit shortly after start-up. If you must shoot yourself in the foot,
934 then henceforth you will have to maintain your own local patches to strip
937 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
938 condition logic to determine truth/failure and will fail to expand many
939 strings, bool_lax{} uses the router condition logic, where most strings
941 Note: bool{00} is false, bool_lax{00} is true.
943 9. Routers now support multiple "condition" tests.
945 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
946 Setting this allows an admin to define which entry in the tcpwrappers
947 config file will be used to control access to the daemon. This option
948 is only available when Exim is built with USE_TCP_WRAPPERS. The
949 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
952 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
953 the Exim run-time user, instead of root.
955 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
956 is forced on. This is mitigated by the new build option
957 TRUSTED_CONFIG_LIST which defines a list of configuration files which
958 are trusted; one per line. If a config file is owned by root and matches
959 a pathname in the list, then it may be invoked by the Exim build-time
960 user without Exim relinquishing root privileges.
962 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
963 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
964 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
965 include the main config. As a transition mechanism, we are temporarily
966 providing a work-around: the new build option WHITELIST_D_MACROS provides
967 a colon-separated list of macro names which may be overridden by the Exim
968 run-time user. The values of these macros are constrained to the regex
969 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
975 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
976 writable, the other to locking of MBX folders (not mbox).
978 2. MySQL stored procedures are now supported.
980 3. The dkim_domain transport option is now a list, not a single string, and
981 messages will be signed for each element in the list (discarding
984 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
985 in the presence of multiple character strings within the RR. Prior to 4.70,
986 only the first string would be returned. The dnsdb lookup now, by default,
987 preserves the pre-4.70 semantics, but also now takes an extended output
988 separator specification. The separator can be followed by a semicolon, to
989 concatenate the individual text strings together with no join character,
990 or by a comma and a second separator character, in which case the text
991 strings within a TXT record are joined on that second character.
992 Administrators are reminded that DNS provides no ordering guarantees
993 between multiple records in an RRset. For example:
995 foo.example. IN TXT "a" "b" "c"
996 foo.example. IN TXT "d" "e" "f"
998 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
999 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
1000 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
1006 1. Native DKIM support without an external library.
1007 (Note that if no action to prevent it is taken, a straight upgrade will
1008 result in DKIM verification of all signed incoming emails. See spec
1009 for details on conditionally disabling)
1011 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
1013 3. There is now a bool{} expansion condition which maps certain strings to
1014 true/false condition values (most likely of use in conjunction with the
1015 and{} expansion operator).
1017 4. The $spam_score, $spam_bar and $spam_report variables are now available
1020 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
1021 options, provided that Exim is invoked by an admin_user.
1023 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
1024 which increases compatibility with older clients at the cost of decreased
1025 security. Don't set this unless you need to support such clients.
1027 7. There is a new expansion operator, ${randint:...} which will produce a
1028 "random" number less than the supplied integer. This randomness is
1029 not guaranteed to be cryptographically strong, but depending upon how
1030 Exim was built may be better than the most naive schemes.
1032 8. Exim now explicitly ensures that SHA256 is available when linked against
1035 9. The transport_filter_timeout option now applies to SMTP transports too.
1041 1. Preliminary DKIM support in Experimental.
1047 1. The body_linecount and body_zerocount C variables are now exported in the
1050 2. When a dnslists lookup succeeds, the key that was looked up is now placed
1051 in $dnslist_matched. When the key is an IP address, it is not reversed in
1052 this variable (though it is, of course, in the actual lookup). In simple
1055 deny dnslists = spamhaus.example
1057 the key is also available in another variable (in this case,
1058 $sender_host_address). In more complicated cases, however, this is not
1059 true. For example, using a data lookup might generate a dnslists lookup
1062 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
1064 If this condition succeeds, the value in $dnslist_matched might be
1065 192.168.6.7 (for example).
1067 3. Authenticators now have a client_condition option. When Exim is running as
1068 a client, it skips an authenticator whose client_condition expansion yields
1069 "0", "no", or "false". This can be used, for example, to skip plain text
1070 authenticators when the connection is not encrypted by a setting such as:
1072 client_condition = ${if !eq{$tls_cipher}{}}
1074 Note that the 4.67 documentation states that $tls_cipher contains the
1075 cipher used for incoming messages. In fact, during SMTP delivery, it
1076 contains the cipher used for the delivery. The same is true for
1079 4. There is now a -Mvc <message-id> option, which outputs a copy of the
1080 message to the standard output, in RFC 2822 format. The option can be used
1081 only by an admin user.
1083 5. There is now a /noupdate option for the ratelimit ACL condition. It
1084 computes the rate and checks the limit as normal, but it does not update
1085 the saved data. This means that, in relevant ACLs, it is possible to lookup
1086 the existence of a specified (or auto-generated) ratelimit key without
1087 incrementing the ratelimit counter for that key.
1089 In order for this to be useful, another ACL entry must set the rate
1090 for the same key somewhere (otherwise it will always be zero).
1095 # Read the rate; if it doesn't exist or is below the maximum
1096 # we update it below
1097 deny ratelimit = 100 / 5m / strict / noupdate
1098 log_message = RATE: $sender_rate / $sender_rate_period \
1099 (max $sender_rate_limit)
1101 [... some other logic and tests...]
1103 warn ratelimit = 100 / 5m / strict / per_cmd
1104 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
1105 (max $sender_rate_limit)
1106 condition = ${if le{$sender_rate}{$sender_rate_limit}}
1110 6. The variable $max_received_linelength contains the number of bytes in the
1111 longest line that was received as part of the message, not counting the
1112 line termination character(s).
1114 7. Host lists can now include +ignore_defer and +include_defer, analogous to
1115 +ignore_unknown and +include_unknown. These options should be used with
1116 care, probably only in non-critical host lists such as whitelists.
1118 8. There's a new option called queue_only_load_latch, which defaults true.
1119 If set false when queue_only_load is greater than zero, Exim re-evaluates
1120 the load for each incoming message in an SMTP session. Otherwise, once one
1121 message is queued, the remainder are also.
1123 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
1124 cases when an SMTP session ends without sending QUIT. However, when Exim
1125 itself is is bad trouble, such as being unable to write to its log files,
1126 this ACL is not run, because it might try to do things (such as write to
1127 log files) that make the situation even worse.
1129 Like the QUIT ACL, this new ACL is provided to make it possible to gather
1130 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
1131 modifier is forbidden in this ACL.
1133 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
1134 to a string that indicates the reason for the termination of the SMTP
1135 connection. The possible values are:
1137 acl-drop Another ACL issued a "drop" command
1138 bad-commands Too many unknown or non-mail commands
1139 command-timeout Timeout while reading SMTP commands
1140 connection-lost The SMTP connection has been lost
1141 data-timeout Timeout while reading message data
1142 local-scan-error The local_scan() function crashed
1143 local-scan-timeout The local_scan() function timed out
1144 signal-exit SIGTERM or SIGINT
1145 synchronization-error SMTP synchronization error
1146 tls-failed TLS failed to start
1148 In most cases when an SMTP connection is closed without having received
1149 QUIT, Exim sends an SMTP response message before actually closing the
1150 connection. With the exception of acl-drop, the default message can be
1151 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
1152 "drop" verb in another ACL, it is the message from the other ACL that is
1155 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
1156 servers with individual queries. This is done by starting the query with
1157 "servers=x:y:z;", where each item in the list may take one of two forms:
1159 (1) If it is just a host name, the appropriate global option (mysql_servers
1160 or pgsql_servers) is searched for a host of the same name, and the
1161 remaining parameters (database, user, password) are taken from there.
1163 (2) If it contains any slashes, it is taken as a complete parameter set.
1165 The list of servers is used in exactly the same was as the global list.
1166 Once a connection to a server has happened and a query has been
1167 successfully executed, processing of the lookup ceases.
1169 This feature is intended for use in master/slave situations where updates
1170 are occurring, and one wants to update a master rather than a slave. If the
1171 masters are in the list for reading, you might have:
1173 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
1175 In an updating lookup, you could then write
1177 ${lookup mysql{servers=master; UPDATE ...}
1179 If, on the other hand, the master is not to be used for reading lookups:
1181 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
1183 you can still update the master by
1185 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
1187 11. The message_body_newlines option (default FALSE, for backwards
1188 compatibility) can be used to control whether newlines are present in
1189 $message_body and $message_body_end. If it is FALSE, they are replaced by
1196 1. There is a new log selector called smtp_no_mail, which is not included in
1197 the default setting. When it is set, a line is written to the main log
1198 whenever an accepted SMTP connection terminates without having issued a
1201 2. When an item in a dnslists list is followed by = and & and a list of IP
1202 addresses, the behaviour was not clear when the lookup returned more than
1203 one IP address. This has been solved by the addition of == and =& for "all"
1204 rather than the default "any" matching.
1206 3. Up till now, the only control over which cipher suites GnuTLS uses has been
1207 for the cipher algorithms. New options have been added to allow some of the
1208 other parameters to be varied.
1210 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
1211 set, Exim compiles a runtime option called disable_fsync.
1213 5. There is a new variable called $smtp_count_at_connection_start.
1215 6. There's a new control called no_pipelining.
1217 7. There are two new variables called $sending_ip_address and $sending_port.
1218 These are set whenever an SMTP connection to another host has been set up.
1220 8. The expansion of the helo_data option in the smtp transport now happens
1221 after the connection to the server has been made.
1223 9. There is a new expansion operator ${rfc2047d: that decodes strings that
1224 are encoded as per RFC 2047.
1226 10. There is a new log selector called "pid", which causes the current process
1227 id to be added to every log line, in square brackets, immediately after the
1230 11. Exim has been modified so that it flushes SMTP output before implementing
1231 a delay in an ACL. It also flushes the output before performing a callout,
1232 as this can take a substantial time. These behaviours can be disabled by
1233 obeying control = no_delay_flush or control = no_callout_flush,
1234 respectively, at some earlier stage of the connection.
1236 12. There are two new expansion conditions that iterate over a list. They are
1237 called forany and forall.
1239 13. There's a new global option called dsn_from that can be used to vary the
1240 contents of From: lines in bounces and other automatically generated
1241 messages ("delivery status notifications" - hence the name of the option).
1243 14. The smtp transport has a new option called hosts_avoid_pipelining.
1245 15. By default, exigrep does case-insensitive matches. There is now a -I option
1246 that makes it case-sensitive.
1248 16. A number of new features ("addresses", "map", "filter", and "reduce") have
1249 been added to string expansions to make it easier to process lists of
1250 items, typically addresses.
1252 17. There's a new ACL modifier called "continue". It does nothing of itself,
1253 and processing of the ACL always continues with the next condition or
1254 modifier. It is provided so that the side effects of expanding its argument
1257 18. It is now possible to use newline and other control characters (those with
1258 values less than 32, plus DEL) as separators in lists.
1260 19. The exigrep utility now has a -v option, which inverts the matching
1263 20. The host_find_failed option in the manualroute router can now be set to
1270 No new features were added to 4.66.
1276 No new features were added to 4.65.
1282 1. ACL variables can now be given arbitrary names, as long as they start with
1283 "acl_c" or "acl_m" (for connection variables and message variables), are at
1284 least six characters long, with the sixth character being either a digit or
1287 2. There is a new ACL modifier called log_reject_target. It makes it possible
1288 to specify which logs are used for messages about ACL rejections.
1290 3. There is a new authenticator called "dovecot". This is an interface to the
1291 authentication facility of the Dovecot POP/IMAP server, which can support a
1292 number of authentication methods.
1294 4. The variable $message_headers_raw provides a concatenation of all the
1295 messages's headers without any decoding. This is in contrast to
1296 $message_headers, which does RFC2047 decoding on the header contents.
1298 5. In a DNS black list, if two domain names, comma-separated, are given, the
1299 second is used first to do an initial check, making use of any IP value
1300 restrictions that are set. If there is a match, the first domain is used,
1301 without any IP value restrictions, to get the TXT record.
1303 6. All authenticators now have a server_condition option.
1305 7. There is a new command-line option called -Mset. It is useful only in
1306 conjunction with -be (that is, when testing string expansions). It must be
1307 followed by a message id; Exim loads the given message from its spool
1308 before doing the expansions.
1310 8. Another similar new command-line option is called -bem. It operates like
1311 -be except that it must be followed by the name of a file that contains a
1314 9. When an address is delayed because of a 4xx response to a RCPT command, it
1315 is now the combination of sender and recipient that is delayed in
1316 subsequent queue runs until its retry time is reached.
1318 10. Unary negation and the bitwise logical operators and, or, xor, not, and
1319 shift, have been added to the eval: and eval10: expansion items.
1321 11. The variables $interface_address and $interface_port have been renamed
1322 as $received_ip_address and $received_port, to make it clear that they
1323 relate to message reception rather than delivery. (The old names remain
1324 available for compatibility.)
1326 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
1327 to vary the message that is sent when an SMTP command is accepted.
1333 1. There is a new Boolean option called filter_prepend_home for the redirect
1336 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
1337 start of receiving a non-SMTP message, before any of the message has been
1340 3. When an SMTP error message is specified in a "message" modifier in an ACL,
1341 or in a :fail: or :defer: message in a redirect router, Exim now checks the
1342 start of the message for an SMTP error code.
1344 4. There is a new parameter for LDAP lookups called "referrals", which takes
1345 one of the settings "follow" (the default) or "nofollow".
1347 5. Version 20070721.2 of exipick now included, offering these new options:
1349 After all other sorting options have bee processed, reverse order
1350 before displaying messages (-R is synonym).
1352 Randomize order of matching messages before displaying.
1354 Instead of displaying the matching messages, display the sum
1356 --sort <variable>[,<variable>...]
1357 Before displaying matching messages, sort the messages according to
1358 each messages value for each variable.
1360 Negate the value for every test (returns inverse output from the
1361 same criteria without --not).
1367 1. The ${readsocket expansion item now supports Internet domain sockets as well
1368 as Unix domain sockets. If the first argument begins "inet:", it must be of
1369 the form "inet:host:port". The port is mandatory; it may be a number or the
1370 name of a TCP port in /etc/services. The host may be a name, or it may be an
1371 IP address. An ip address may optionally be enclosed in square brackets.
1372 This is best for IPv6 addresses. For example:
1374 ${readsocket{inet:[::1]:1234}{<request data>}...
1376 Only a single host name may be given, but if looking it up yield more than
1377 one IP address, they are each tried in turn until a connection is made. Once
1378 a connection has been made, the behaviour is as for ${readsocket with a Unix
1381 2. If a redirect router sets up file or pipe deliveries for more than one
1382 incoming address, and the relevant transport has batch_max set greater than
1383 one, a batch delivery now occurs.
1385 3. The appendfile transport has a new option called maildirfolder_create_regex.
1386 Its value is a regular expression. For a maildir delivery, this is matched
1387 against the maildir directory; if it matches, Exim ensures that a
1388 maildirfolder file is created alongside the new, cur, and tmp directories.
1394 The documentation is up-to-date for the 4.61 release. Major new features since
1395 the 4.60 release are:
1397 . An option called disable_ipv6, to disable the use of IPv6 completely.
1399 . An increase in the number of ACL variables to 20 of each type.
1401 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
1402 $2, $3, (though those are still set) because the numeric variables get used
1403 for other things in complicated expansions.
1405 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
1407 . It is possible to use setclassresources() on some BSD OS to control the
1408 resources used in pipe deliveries.
1410 . A new ACL modifier called add_header, which can be used with any verb.
1412 . More errors are detectable in retry rules.
1414 There are a number of other additions too.
1420 The documentation is up-to-date for the 4.60 release. Major new features since
1421 the 4.50 release are:
1423 . Support for SQLite.
1425 . Support for IGNOREQUOTA in LMTP.
1427 . Extensions to the "submission mode" features.
1429 . Support for Client SMTP Authorization (CSA).
1431 . Support for ratelimiting hosts and users.
1433 . New expansion items to help with the BATV "prvs" scheme.
1435 . A "match_ip" condition, that matches an IP address against a list.
1437 There are many more minor changes.