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 CVS before the documentation is updated. Once
7 the documentation is updated, this file is reduced to a short list.
12 1. The new perl_taintmode option allows to run the embedded perl
13 interpreter in taint mode.
15 2. New log_selector: dnssec, adds a "DS" tag to acceptance and delivery lines.
21 1. The ACL conditions regex and mime_regex now capture substrings
22 into numeric variables $regex1 to 9, like the "match" expansion condition.
24 2. New $callout_address variable records the address used for a spam=,
25 malware= or verify= callout.
27 3. Transports now take a "max_parallel" option, to limit concurrency.
29 4. Expansion operators ${ipv6norm:<string>} and ${ipv6denorm:<string>}.
30 The latter expands to a 8-element colon-sep set of hex digits including
31 leading zeroes. A trailing ipv4-style dotted-decimal set is converted
32 to hex. Pure ipv4 addresses are converted to IPv4-mapped IPv6.
33 The former operator strips leading zeroes and collapses the longest
34 set of 0-groups to a double-colon.
36 5. New "-bP config" support, to dump the effective configuration.
38 6. New $dkim_key_length variable.
40 7. New base64d and base64 expansion items (the existing str2b64 being a
41 synonym of the latter). Add support in base64 for certificates.
43 8. New main configuration option "bounce_return_linesize_limit" to
44 avoid oversize bodies in bounces. The dafault value matches RFC
47 9. New $initial_cwd expansion variable.
53 1. Support for using the system standard CA bundle.
55 2. New expansion items $config_file, $config_dir, containing the file
56 and directory name of the main configuration file. Also $exim_version.
58 3. New "malware=" support for Avast.
60 4. New "spam=" variant option for Rspamd.
62 5. Assorted options on malware= and spam= scanners.
64 6. A commandline option to write a comment into the logfile.
66 7. If built with EXPERIMENTAL_SOCKS feature enabled, the smtp transport can
67 be configured to make connections via socks5 proxies.
69 8. If built with EXPERIMENTAL_INTERNATIONAL, support is included for
70 the transmission of UTF-8 envelope addresses.
72 9. If built with EXPERIMENTAL_INTERNATIONAL, an expansion item for a commonly
73 used encoding of Maildir folder names.
75 10. A logging option for slow DNS lookups.
77 11. New ${env {<variable>}} expansion.
79 12. A non-SMTP authenticator using information from TLS client certificates.
81 13. Main option "tls_eccurve" for selecting an Elliptic Curve for TLS.
82 Patch originally by Wolfgang Breyha.
84 14. Main option "dns_trust_aa" for trusting your local nameserver at the
91 1. If built with EXPERIMENTAL_DANE feature enabled, Exim will follow the
92 DANE smtp draft to assess a secure chain of trust of the certificate
93 used to establish the TLS connection based on a TLSA record in the
96 2. The EXPERIMENTAL_TPDA feature has been renamed to EXPERIMENTAL_EVENT
97 and several new events have been created. The reason is because it has
98 been expanded beyond just firing events during the transport phase. Any
99 existing TPDA transport options will have to be rewritten to use a new
100 $event_name expansion variable in a condition. Refer to the
101 experimental-spec.txt for details and examples.
103 3. The EXPERIMENTAL_CERTNAMES features is an enhancement to verify that
104 server certs used for TLS match the result of the MX lookup. It does
105 not use the same mechanism as DANE.
115 1. If built with the EXPERIMENTAL_PROXY feature enabled, Exim can be
116 configured to expect an initial header from a proxy that will make the
117 actual external source IP:host be used in exim instead of the IP of the
118 proxy that is connecting to it.
120 2. New verify option header_names_ascii, which will check to make sure
121 there are no non-ASCII characters in header names. Exim itself handles
122 those non-ASCII characters, but downstream apps may not, so Exim can
123 detect and reject if those characters are present.
125 3. New expansion operator ${utf8clean:string} to replace malformed UTF8
126 codepoints with valid ones.
128 4. New malware type "sock". Talks over a Unix or TCP socket, sending one
129 command line and matching a regex against the return data for trigger
130 and a second regex to extract malware_name. The mail spoolfile name can
131 be included in the command line.
133 5. The smtp transport now supports options "tls_verify_hosts" and
134 "tls_try_verify_hosts". If either is set the certificate verification
135 is split from the encryption operation. The default remains that a failed
136 verification cancels the encryption.
138 6. New SERVERS override of default ldap server list. In the ACLs, an ldap
139 lookup can now set a list of servers to use that is different from the
142 7. New command-line option -C for exiqgrep to specify alternate exim.conf
143 file when searching the queue.
145 8. OCSP now supports GnuTLS also, if you have version 3.1.3 or later of that.
147 9. Support for DNSSEC on outbound connections.
149 10. New variables "tls_(in,out)_(our,peer)cert" and expansion item
150 "certextract" to extract fields from them. Hash operators md5 and sha1
151 work over them for generating fingerprints, and a new sha256 operator
154 11. PRDR is now supported dy default.
156 12. OCSP stapling is now supported by default.
158 13. If built with the EXPERIMENTAL_DSN feature enabled, Exim will output
159 Delivery Status Notification messages in MIME format, and negociate
160 DSN features per RFC 3461.
166 1. New command-line option -bI:sieve will list all supported sieve extensions
167 of this Exim build on standard output, one per line.
168 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
169 query this to establish the correct list to include in the protocol's
170 SIEVE capability line.
172 2. If the -n option is combined with the -bP option, then the name of an
173 emitted option is not output, only the value (if visible to you).
174 For instance, "exim -n -bP pid_file_path" should just emit a pathname
175 followed by a newline, and no other text.
177 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
178 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
179 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
180 acceptable for security. (Option accepted but ignored if using OpenSSL).
181 Defaults to 1024, the old value. May be lowered only to 512, or raised as
182 far as you like. Raising this may hinder TLS interoperability with other
183 sites and is not currently recommended. Lowering this will permit you to
184 establish a TLS session which is not as secure as you might like.
186 Unless you really know what you are doing, leave it alone.
188 4. If not built with DISABLE_DNSSEC, Exim now has the main option
189 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
190 to send the DO flag to your recursive resolver. If you have a recursive
191 resolver, which can set the Authenticated Data (AD) flag in results, Exim
192 can now detect this. Exim does not perform validation itself, instead
193 relying upon a trusted path to the resolver.
195 Current status: work-in-progress; $sender_host_dnssec variable added.
197 5. DSCP support for outbound connections: on a transport using the smtp driver,
198 set "dscp = ef", for instance, to cause the connections to have the relevant
199 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
201 Similarly for inbound connections, there is a new control modifier, dscp,
202 so "warn control = dscp/ef" in the connect ACL, or after authentication.
204 Supported values depend upon system libraries. "exim -bI:dscp" to list the
205 ones Exim knows of. You can also set a raw number 0..0x3F.
207 6. The -G command-line flag is no longer ignored; it is now equivalent to an
208 ACL setting "control = suppress_local_fixups". The -L command-line flag
209 is now accepted and forces use of syslog, with the provided tag as the
210 process name. A few other flags used by Sendmail are now accepted and
213 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
214 ACL modifier; works for single-recipient mails which are recieved on and
215 deliverable via SMTP. Using the connection made for a recipient verify,
216 if requested before the verify, or a new one made for the purpose while
217 the inbound connection is still active. The bulk of the mail item is copied
218 direct from the inbound socket to the outbound (as well as the spool file).
219 When the source notifies the end of data, the data acceptance by the destination
220 is negociated before the acceptance is sent to the source. If the destination
221 does not accept the mail item, for example due to content-scanning, the item
222 is not accepted from the source and therefore there is no need to generate
223 a bounce mail. This is of benefit when providing a secondary-MX service.
224 The downside is that delays are under the control of the ultimate destination
227 The Recieved-by: header on items delivered by cutthrough is generated
228 early in reception rather than at the end; this will affect any timestamp
229 included. The log line showing delivery is recorded before that showing
230 reception; it uses a new ">>" tag instead of "=>".
232 To support the feature, verify-callout connections can now use ESMTP and TLS.
233 The usual smtp transport options are honoured, plus a (new, default everything)
234 hosts_verify_avoid_tls.
236 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
237 for specific access to the information for each connection. The old names
238 are present for now but deprecated.
240 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
242 8. New expansion operators ${listnamed:name} to get the content of a named list
243 and ${listcount:string} to count the items in a list.
245 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
246 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
247 modules. For some situations this is desirable, but we expect admin in
248 those situations to know they want the feature. More commonly, it means
249 that GUI user modules get loaded and are broken by the setuid Exim being
250 unable to access files specified in environment variables and passed
251 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
252 unless this new option is set.
254 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
255 so have also added a build option which can be used to build Exim with GnuTLS
256 but without trying to use any kind of PKCS11 support. Uncomment this in the
259 AVOID_GNUTLS_PKCS11=yes
261 10. The "acl = name" condition on an ACL now supports optional arguments.
262 New expansion item "${acl {name}{arg}...}" and expansion condition
263 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
264 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
265 Variable $acl_narg contains the number of arguments. If the ACL sets
266 a "message =" value this becomes the result of the expansion item,
267 or the value of $value for the expansion condition. If the ACL returns
268 accept the expansion condition is true; if reject, false. A defer
269 return results in a forced fail.
271 11. Routers and transports can now have multiple headers_add and headers_remove
272 option lines. The concatenated list is used.
274 12. New ACL modifier "remove_header" can remove headers before message gets
275 handled by routers/transports.
277 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
278 "aaaa" and "a" lookups is done and the full set of results returned.
280 14. New expansion variable $headers_added with content from ACL add_header
281 modifier (but not yet added to message).
283 15. New 8bitmime status logging option for received messages. Log field "M8S".
285 16. New authenticated_sender logging option, adding to log field "A".
287 17. New expansion variables $router_name and $transport_name. Useful
288 particularly for debug_print as -bt commandline option does not
289 require privilege whereas -d does.
291 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
292 proposed extension to SMTP from Eric Hall.
294 19. The pipe transport has gained the force_command option, to allow
295 decorating commands from user .forward pipe aliases with prefix
296 wrappers, for instance.
298 20. Callout connections can now AUTH; the same controls as normal delivery
301 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
302 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
303 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
304 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
305 dmarc_status. It adds new control flags dmarc_disable_verify and
306 dmarc_enable_forensic.
308 22. Add expansion variable $authenticated_fail_id, which is the username
309 provided to the authentication method which failed. It is available
310 for use in subsequent ACL processing (typically quit or notquit ACLs).
312 23. New ACL modifer "udpsend" can construct a UDP packet to send to a given
315 24. New ${hexquote:..string..} expansion operator converts non-printable
316 characters in the string to \xNN form.
318 25. Experimental TPDA (Transport Post Delivery Action) function added.
319 Patch provided by Axel Rau.
321 26. Experimental Redis lookup added. Patch provided by Warren Baker.
327 1. New authenticator driver, "gsasl". Server-only (at present).
328 This is a SASL interface, licensed under GPL, which can be found at
329 http://www.gnu.org/software/gsasl/.
330 This system does not provide sources of data for authentication, so
331 careful use needs to be made of the conditions in Exim.
333 2. New authenticator driver, "heimdal_gssapi". Server-only.
334 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
335 is no longer honoured for setuid programs by Heimdal. Use the
336 "server_keytab" option to point to the keytab.
338 3. The "pkg-config" system can now be used when building Exim to reference
339 cflags and library information for lookups and authenticators, rather
340 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
341 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
342 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
344 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
345 find the headers and libraries for PCRE.
347 4. New expansion variable $tls_bits.
349 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
350 be joined together with ASCII NUL characters to construct the key to pass
351 into the DBM library. Can be used with gsasl to access sasldb2 files as
354 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
356 Avoid release 1.0.1a if you can. Note that the default value of
357 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
358 increased susceptibility to attack. This may still have interoperability
359 implications for very old clients (see version 4.31 change 37) but
360 administrators can choose to make the trade-off themselves and restore
361 compatibility at the cost of session security.
363 7. Use of the new expansion variable $tls_sni in the main configuration option
364 tls_certificate will cause Exim to re-expand the option, if the client
365 sends the TLS Server Name Indication extension, to permit choosing a
366 different certificate; tls_privatekey will also be re-expanded. You must
367 still set these options to expand to valid files when $tls_sni is not set.
369 The SMTP Transport has gained the option tls_sni, which will set a hostname
370 for outbound TLS sessions, and set $tls_sni too.
372 A new log_selector, +tls_sni, has been added, to log received SNI values
373 for Exim as a server.
375 8. The existing "accept_8bitmime" option now defaults to true. This means
376 that Exim is deliberately not strictly RFC compliant. We're following
377 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
378 Those who disagree, or know that they are talking to mail servers that,
379 even today, are not 8-bit clean, need to turn off this option.
381 9. Exim can now be started with -bw (with an optional timeout, given as
382 -bw<timespec>). With this, stdin at startup is a socket that is
383 already listening for connections. This has a more modern name of
384 "socket activation", but forcing the activated socket to fd 0. We're
385 interested in adding more support for modern variants.
387 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
388 for numbers indicates multiplication by 1024^3.
390 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
391 gnutls_require_mac & gnutls_require_protocols are no longer supported.
392 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
393 string, documentation for which is at:
394 http://www.gnutls.org/manual/html_node/Priority-Strings.html
396 SNI support has been added to Exim's GnuTLS integration too.
398 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
399 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
401 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
402 is now available. If the contents of the file are valid, then Exim will
403 send that back in response to a TLS status request; this is OCSP Stapling.
404 Exim will not maintain the contents of the file in any way: administrators
405 are responsible for ensuring that it is up-to-date.
407 See "experimental-spec.txt" for more details.
409 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
410 identically to TXT record lookups.
412 14. New expansion variable $tod_epoch_l for higher-precision time.
414 15. New global option tls_dh_max_bits, defaulting to current value of NSS
415 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
416 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
418 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
419 Option can now be a path or an identifier for a standard prime.
420 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
421 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
424 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
425 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
426 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
432 1. New options for the ratelimit ACL condition: /count= and /unique=.
433 The /noupdate option has been replaced by a /readonly option.
435 2. The SMTP transport's protocol option may now be set to "smtps", to
436 use SSL-on-connect outbound.
438 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
439 there is a problem talking to the AV scanner, or the AV scanner running.
441 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
442 and check if the search item is a member of the list. This does not
443 support named lists, but does subject the list part to string expansion.
445 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
446 built, Exim no longer performs string expansion on the second string of
447 the match_* expansion conditions: "match_address", "match_domain",
448 "match_ip" & "match_local_part". Named lists can still be used.
454 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
455 or off in the resolver library.
461 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
462 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
463 libraries. The following global options have been added in support of
464 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
465 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
467 2. The pipe transport now takes a boolean option, "freeze_signal", default
468 false. When true, if the external delivery command exits on a signal then
469 Exim will freeze the message in the queue, instead of generating a bounce.
471 3. Log filenames may now use %M as an escape, instead of %D (still available).
472 The %M pattern expands to yyyymm, providing month-level resolution.
474 4. The $message_linecount variable is now updated for the maildir_tag option,
475 in the same way as $message_size, to reflect the real number of lines,
476 including any header additions or removals from transport.
478 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
479 Exim now selects entries randomly, to better scale in a cluster setup.
485 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
486 the flaw permitted the Exim run-time user to cause root to append to
487 arbitrary files of the attacker's choosing, with the content based
488 on content supplied by the attacker.
490 2. Exim now supports loading some lookup types at run-time, using your
491 platform's dlopen() functionality. This has limited platform support
492 and the intention is not to support every variant, it's limited to
493 dlopen(). This permits the main Exim binary to not be linked against
494 all the libraries needed for all the lookup types.
500 NOTE: this version is not guaranteed backwards-compatible, please read the
501 items below carefully
503 1. A new main configuration option, "openssl_options", is available if Exim
504 is built with SSL support provided by OpenSSL. The option allows
505 administrators to specify OpenSSL options to be used on connections;
506 typically this is to set bug compatibility features which the OpenSSL
507 developers have not enabled by default. There may be security
508 consequences for certain options, so these should not be changed
511 2. A new pipe transport option, "permit_coredumps", may help with problem
512 diagnosis in some scenarios. Note that Exim is typically installed as
513 a setuid binary, which on most OSes will inhibit coredumps by default,
514 so that safety mechanism would have to be overridden for this option to
515 be able to take effect.
517 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
518 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
519 Note that this switches Exim to use a new API ("INSTREAM") and a future
520 release of ClamAV will remove support for the old API ("STREAM").
522 The av_scanner option, when set to "clamd", now takes an optional third
523 part, "local", which causes Exim to pass a filename to ClamAV instead of
524 the file content. This is the same behaviour as when clamd is pointed at
525 a Unix-domain socket. For example:
527 av_scanner = clamd:192.0.2.3 1234:local
529 ClamAV's ExtendedDetectionInfo response format is now handled.
531 4. There is now a -bmalware option, restricted to admin users. This option
532 takes one parameter, a filename, and scans that file with Exim's
533 malware-scanning framework. This is intended purely as a debugging aid
534 to ensure that Exim's scanning is working, not to replace other tools.
535 Note that the ACL framework is not invoked, so if av_scanner references
536 ACL variables without a fallback then this will fail.
538 5. There is a new expansion operator, "reverse_ip", which will reverse IP
539 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
541 ${reverse_ip:192.0.2.4}
543 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
544 -> 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
546 6. There is a new ACL control called "debug", to enable debug logging.
547 This allows selective logging of certain incoming transactions within
548 production environments, with some care. It takes two options, "tag"
549 and "opts"; "tag" is included in the filename of the log and "opts"
550 is used as per the -d<options> command-line option. Examples, which
551 don't all make sense in all contexts:
554 control = debug/tag=.$sender_host_address
555 control = debug/opts=+expand+acl
556 control = debug/tag=.$message_exim_id/opts=+expand
558 7. It has always been implicit in the design and the documentation that
559 "the Exim user" is not root. src/EDITME said that using root was
560 "very strongly discouraged". This is not enough to keep people from
561 shooting themselves in the foot in days when many don't configure Exim
562 themselves but via package build managers. The security consequences of
563 running various bits of network code are severe if there should be bugs in
564 them. As such, the Exim user may no longer be root. If configured
565 statically, Exim will refuse to build. If configured as ref:user then Exim
566 will exit shortly after start-up. If you must shoot yourself in the foot,
567 then henceforth you will have to maintain your own local patches to strip
570 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
571 condition logic to determine truth/failure and will fail to expand many
572 strings, bool_lax{} uses the router condition logic, where most strings
574 Note: bool{00} is false, bool_lax{00} is true.
576 9. Routers now support multiple "condition" tests.
578 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
579 Setting this allows an admin to define which entry in the tcpwrappers
580 config file will be used to control access to the daemon. This option
581 is only available when Exim is built with USE_TCP_WRAPPERS. The
582 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
585 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
586 the Exim run-time user, instead of root.
588 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
589 is forced on. This is mitigated by the new build option
590 TRUSTED_CONFIG_LIST which defines a list of configuration files which
591 are trusted; one per line. If a config file is owned by root and matches
592 a pathname in the list, then it may be invoked by the Exim build-time
593 user without Exim relinquishing root privileges.
595 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
596 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
597 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
598 include the main config. As a transition mechanism, we are temporarily
599 providing a work-around: the new build option WHITELIST_D_MACROS provides
600 a colon-separated list of macro names which may be overridden by the Exim
601 run-time user. The values of these macros are constrained to the regex
602 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
608 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
609 writable, the other to locking of MBX folders (not mbox).
611 2. MySQL stored procedures are now supported.
613 3. The dkim_domain transport option is now a list, not a single string, and
614 messages will be signed for each element in the list (discarding
617 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
618 in the presence of multiple character strings within the RR. Prior to 4.70,
619 only the first string would be returned. The dnsdb lookup now, by default,
620 preserves the pre-4.70 semantics, but also now takes an extended output
621 separator specification. The separator can be followed by a semicolon, to
622 concatenate the individual text strings together with no join character,
623 or by a comma and a second separator character, in which case the text
624 strings within a TXT record are joined on that second character.
625 Administrators are reminded that DNS provides no ordering guarantees
626 between multiple records in an RRset. For example:
628 foo.example. IN TXT "a" "b" "c"
629 foo.example. IN TXT "d" "e" "f"
631 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
632 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
633 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
639 1. Native DKIM support without an external library.
640 (Note that if no action to prevent it is taken, a straight upgrade will
641 result in DKIM verification of all signed incoming emails. See spec
642 for details on conditionally disabling)
644 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
646 3. There is now a bool{} expansion condition which maps certain strings to
647 true/false condition values (most likely of use in conjunction with the
648 and{} expansion operator).
650 4. The $spam_score, $spam_bar and $spam_report variables are now available
653 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
654 options, provided that Exim is invoked by an admin_user.
656 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
657 which increases compatibility with older clients at the cost of decreased
658 security. Don't set this unless you need to support such clients.
660 7. There is a new expansion operator, ${randint:...} which will produce a
661 "random" number less than the supplied integer. This randomness is
662 not guaranteed to be cryptographically strong, but depending upon how
663 Exim was built may be better than the most naive schemes.
665 8. Exim now explicitly ensures that SHA256 is available when linked against
668 9. The transport_filter_timeout option now applies to SMTP transports too.
674 1. Preliminary DKIM support in Experimental.
680 1. The body_linecount and body_zerocount C variables are now exported in the
683 2. When a dnslists lookup succeeds, the key that was looked up is now placed
684 in $dnslist_matched. When the key is an IP address, it is not reversed in
685 this variable (though it is, of course, in the actual lookup). In simple
688 deny dnslists = spamhaus.example
690 the key is also available in another variable (in this case,
691 $sender_host_address). In more complicated cases, however, this is not
692 true. For example, using a data lookup might generate a dnslists lookup
695 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
697 If this condition succeeds, the value in $dnslist_matched might be
698 192.168.6.7 (for example).
700 3. Authenticators now have a client_condition option. When Exim is running as
701 a client, it skips an authenticator whose client_condition expansion yields
702 "0", "no", or "false". This can be used, for example, to skip plain text
703 authenticators when the connection is not encrypted by a setting such as:
705 client_condition = ${if !eq{$tls_cipher}{}}
707 Note that the 4.67 documentation states that $tls_cipher contains the
708 cipher used for incoming messages. In fact, during SMTP delivery, it
709 contains the cipher used for the delivery. The same is true for
712 4. There is now a -Mvc <message-id> option, which outputs a copy of the
713 message to the standard output, in RFC 2822 format. The option can be used
714 only by an admin user.
716 5. There is now a /noupdate option for the ratelimit ACL condition. It
717 computes the rate and checks the limit as normal, but it does not update
718 the saved data. This means that, in relevant ACLs, it is possible to lookup
719 the existence of a specified (or auto-generated) ratelimit key without
720 incrementing the ratelimit counter for that key.
722 In order for this to be useful, another ACL entry must set the rate
723 for the same key somewhere (otherwise it will always be zero).
728 # Read the rate; if it doesn't exist or is below the maximum
730 deny ratelimit = 100 / 5m / strict / noupdate
731 log_message = RATE: $sender_rate / $sender_rate_period \
732 (max $sender_rate_limit)
734 [... some other logic and tests...]
736 warn ratelimit = 100 / 5m / strict / per_cmd
737 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
738 (max $sender_rate_limit)
739 condition = ${if le{$sender_rate}{$sender_rate_limit}}
743 6. The variable $max_received_linelength contains the number of bytes in the
744 longest line that was received as part of the message, not counting the
745 line termination character(s).
747 7. Host lists can now include +ignore_defer and +include_defer, analagous to
748 +ignore_unknown and +include_unknown. These options should be used with
749 care, probably only in non-critical host lists such as whitelists.
751 8. There's a new option called queue_only_load_latch, which defaults true.
752 If set false when queue_only_load is greater than zero, Exim re-evaluates
753 the load for each incoming message in an SMTP session. Otherwise, once one
754 message is queued, the remainder are also.
756 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
757 cases when an SMTP session ends without sending QUIT. However, when Exim
758 itself is is bad trouble, such as being unable to write to its log files,
759 this ACL is not run, because it might try to do things (such as write to
760 log files) that make the situation even worse.
762 Like the QUIT ACL, this new ACL is provided to make it possible to gather
763 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
764 modifier is forbidden in this ACL.
766 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
767 to a string that indicates the reason for the termination of the SMTP
768 connection. The possible values are:
770 acl-drop Another ACL issued a "drop" command
771 bad-commands Too many unknown or non-mail commands
772 command-timeout Timeout while reading SMTP commands
773 connection-lost The SMTP connection has been lost
774 data-timeout Timeout while reading message data
775 local-scan-error The local_scan() function crashed
776 local-scan-timeout The local_scan() function timed out
777 signal-exit SIGTERM or SIGINT
778 synchronization-error SMTP synchronization error
779 tls-failed TLS failed to start
781 In most cases when an SMTP connection is closed without having received
782 QUIT, Exim sends an SMTP response message before actually closing the
783 connection. With the exception of acl-drop, the default message can be
784 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
785 "drop" verb in another ACL, it is the message from the other ACL that is
788 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
789 servers with individual queries. This is done by starting the query with
790 "servers=x:y:z;", where each item in the list may take one of two forms:
792 (1) If it is just a host name, the appropriate global option (mysql_servers
793 or pgsql_servers) is searched for a host of the same name, and the
794 remaining parameters (database, user, password) are taken from there.
796 (2) If it contains any slashes, it is taken as a complete parameter set.
798 The list of servers is used in exactly the same was as the global list.
799 Once a connection to a server has happened and a query has been
800 successfully executed, processing of the lookup ceases.
802 This feature is intended for use in master/slave situations where updates
803 are occurring, and one wants to update a master rather than a slave. If the
804 masters are in the list for reading, you might have:
806 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
808 In an updating lookup, you could then write
810 ${lookup mysql{servers=master; UPDATE ...}
812 If, on the other hand, the master is not to be used for reading lookups:
814 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
816 you can still update the master by
818 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
820 11. The message_body_newlines option (default FALSE, for backwards
821 compatibility) can be used to control whether newlines are present in
822 $message_body and $message_body_end. If it is FALSE, they are replaced by
829 1. There is a new log selector called smtp_no_mail, which is not included in
830 the default setting. When it is set, a line is written to the main log
831 whenever an accepted SMTP connection terminates without having issued a
834 2. When an item in a dnslists list is followed by = and & and a list of IP
835 addresses, the behaviour was not clear when the lookup returned more than
836 one IP address. This has been solved by the addition of == and =& for "all"
837 rather than the default "any" matching.
839 3. Up till now, the only control over which cipher suites GnuTLS uses has been
840 for the cipher algorithms. New options have been added to allow some of the
841 other parameters to be varied.
843 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
844 set, Exim compiles a runtime option called disable_fsync.
846 5. There is a new variable called $smtp_count_at_connection_start.
848 6. There's a new control called no_pipelining.
850 7. There are two new variables called $sending_ip_address and $sending_port.
851 These are set whenever an SMTP connection to another host has been set up.
853 8. The expansion of the helo_data option in the smtp transport now happens
854 after the connection to the server has been made.
856 9. There is a new expansion operator ${rfc2047d: that decodes strings that
857 are encoded as per RFC 2047.
859 10. There is a new log selector called "pid", which causes the current process
860 id to be added to every log line, in square brackets, immediately after the
863 11. Exim has been modified so that it flushes SMTP output before implementing
864 a delay in an ACL. It also flushes the output before performing a callout,
865 as this can take a substantial time. These behaviours can be disabled by
866 obeying control = no_delay_flush or control = no_callout_flush,
867 respectively, at some earlier stage of the connection.
869 12. There are two new expansion conditions that iterate over a list. They are
870 called forany and forall.
872 13. There's a new global option called dsn_from that can be used to vary the
873 contents of From: lines in bounces and other automatically generated
874 messages ("delivery status notifications" - hence the name of the option).
876 14. The smtp transport has a new option called hosts_avoid_pipelining.
878 15. By default, exigrep does case-insensitive matches. There is now a -I option
879 that makes it case-sensitive.
881 16. A number of new features ("addresses", "map", "filter", and "reduce") have
882 been added to string expansions to make it easier to process lists of
883 items, typically addresses.
885 17. There's a new ACL modifier called "continue". It does nothing of itself,
886 and processing of the ACL always continues with the next condition or
887 modifier. It is provided so that the side effects of expanding its argument
890 18. It is now possible to use newline and other control characters (those with
891 values less than 32, plus DEL) as separators in lists.
893 19. The exigrep utility now has a -v option, which inverts the matching
896 20. The host_find_failed option in the manualroute router can now be set to
903 No new features were added to 4.66.
909 No new features were added to 4.65.
915 1. ACL variables can now be given arbitrary names, as long as they start with
916 "acl_c" or "acl_m" (for connection variables and message variables), are at
917 least six characters long, with the sixth character being either a digit or
920 2. There is a new ACL modifier called log_reject_target. It makes it possible
921 to specify which logs are used for messages about ACL rejections.
923 3. There is a new authenticator called "dovecot". This is an interface to the
924 authentication facility of the Dovecot POP/IMAP server, which can support a
925 number of authentication methods.
927 4. The variable $message_headers_raw provides a concatenation of all the
928 messages's headers without any decoding. This is in contrast to
929 $message_headers, which does RFC2047 decoding on the header contents.
931 5. In a DNS black list, if two domain names, comma-separated, are given, the
932 second is used first to do an initial check, making use of any IP value
933 restrictions that are set. If there is a match, the first domain is used,
934 without any IP value restrictions, to get the TXT record.
936 6. All authenticators now have a server_condition option.
938 7. There is a new command-line option called -Mset. It is useful only in
939 conjunction with -be (that is, when testing string expansions). It must be
940 followed by a message id; Exim loads the given message from its spool
941 before doing the expansions.
943 8. Another similar new command-line option is called -bem. It operates like
944 -be except that it must be followed by the name of a file that contains a
947 9. When an address is delayed because of a 4xx response to a RCPT command, it
948 is now the combination of sender and recipient that is delayed in
949 subsequent queue runs until its retry time is reached.
951 10. Unary negation and the bitwise logical operators and, or, xor, not, and
952 shift, have been added to the eval: and eval10: expansion items.
954 11. The variables $interface_address and $interface_port have been renamed
955 as $received_ip_address and $received_port, to make it clear that they
956 relate to message reception rather than delivery. (The old names remain
957 available for compatibility.)
959 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
960 to vary the message that is sent when an SMTP command is accepted.
966 1. There is a new Boolean option called filter_prepend_home for the redirect
969 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
970 start of receiving a non-SMTP message, before any of the message has been
973 3. When an SMTP error message is specified in a "message" modifier in an ACL,
974 or in a :fail: or :defer: message in a redirect router, Exim now checks the
975 start of the message for an SMTP error code.
977 4. There is a new parameter for LDAP lookups called "referrals", which takes
978 one of the settings "follow" (the default) or "nofollow".
980 5. Version 20070721.2 of exipick now included, offering these new options:
982 After all other sorting options have bee processed, reverse order
983 before displaying messages (-R is synonym).
985 Randomize order of matching messages before displaying.
987 Instead of displaying the matching messages, display the sum
989 --sort <variable>[,<variable>...]
990 Before displaying matching messages, sort the messages according to
991 each messages value for each variable.
993 Negate the value for every test (returns inverse output from the
994 same criteria without --not).
1000 1. The ${readsocket expansion item now supports Internet domain sockets as well
1001 as Unix domain sockets. If the first argument begins "inet:", it must be of
1002 the form "inet:host:port". The port is mandatory; it may be a number or the
1003 name of a TCP port in /etc/services. The host may be a name, or it may be an
1004 IP address. An ip address may optionally be enclosed in square brackets.
1005 This is best for IPv6 addresses. For example:
1007 ${readsocket{inet:[::1]:1234}{<request data>}...
1009 Only a single host name may be given, but if looking it up yield more than
1010 one IP address, they are each tried in turn until a connection is made. Once
1011 a connection has been made, the behaviour is as for ${readsocket with a Unix
1014 2. If a redirect router sets up file or pipe deliveries for more than one
1015 incoming address, and the relevant transport has batch_max set greater than
1016 one, a batch delivery now occurs.
1018 3. The appendfile transport has a new option called maildirfolder_create_regex.
1019 Its value is a regular expression. For a maildir delivery, this is matched
1020 against the maildir directory; if it matches, Exim ensures that a
1021 maildirfolder file is created alongside the new, cur, and tmp directories.
1027 The documentation is up-to-date for the 4.61 release. Major new features since
1028 the 4.60 release are:
1030 . An option called disable_ipv6, to disable the use of IPv6 completely.
1032 . An increase in the number of ACL variables to 20 of each type.
1034 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
1035 $2, $3, (though those are still set) because the numeric variables get used
1036 for other things in complicated expansions.
1038 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
1040 . It is possible to use setclassresources() on some BSD OS to control the
1041 resources used in pipe deliveries.
1043 . A new ACL modifier called add_header, which can be used with any verb.
1045 . More errors are detectable in retry rules.
1047 There are a number of other additions too.
1053 The documentation is up-to-date for the 4.60 release. Major new features since
1054 the 4.50 release are:
1056 . Support for SQLite.
1058 . Support for IGNOREQUOTA in LMTP.
1060 . Extensions to the "submission mode" features.
1062 . Support for Client SMTP Authorization (CSA).
1064 . Support for ratelimiting hosts and users.
1066 . New expansion items to help with the BATV "prvs" scheme.
1068 . A "match_ip" condition, that matches an IP address against a list.
1070 There are many more minor changes.
git://git.exim.org / exim.git / blob