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