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