Expansions: new ${lheader:<name>}. Bug 2272
[exim.git] / doc / doc-txt / NewStuff
1 New Features in Exim
2 --------------------
3
4 This file contains descriptions of new features that have been added to Exim.
5 Before a formal release, there may be quite a lot of detail so that people can
6 test from the snapshots or the Git before the documentation is updated. Once
7 the documentation is updated, this file is reduced to a short list.
8
9 Version 4.92
10 --------------
11
12 1. ${l_header:<name>} and ${l_h:<name>} expansion items, giving a colon-sep
13 list when there are multiple headers having a given name. This matters
14 when individual headers are wrapped onto multiple lines; with previous
15 facilities hard to parse.
16
17 Version 4.91
18 --------------
19
20 1. Dual-certificate stacks on servers now support OCSP stapling, under GnuTLS
21 version 3.5.6 or later.
22
23 2. DANE is now supported under GnuTLS version 3.0.0 or later. Both GnuTLS and
24 OpenSSL versions are moved to mainline support from Experimental.
25 New SMTP transport option "dane_require_tls_ciphers".
26
27 3. Feature macros for the compiled-in set of malware scanner interfaces.
28
29 4. SPF support is promoted from Experimental to mainline status. The template
30 src/EDITME makefile does not enable its inclusion.
31
32 5. Logging control for DKIM verification. The existing DKIM log line is
33 controlled by a "dkim_verbose" selector which is _not_ enabled by default.
34 A new tag "DKIM=<domain>" is added to <= lines by default, controlled by
35 a "dkim" log_selector.
36
37 6. Receive duration on <= lines, under a new log_selector "receive_time".
38
39 7. Options "ipv4_only" and "ipv4_prefer" on the dnslookup router and on
40 routing rules in the manualroute router.
41
42 8. Expansion item ${sha3:<string>} / ${sha3_<N>:<string>} now also supported
43 under OpenSSL version 1.1.1 or later.
44
45 9. DKIM operations can now use the Ed25519 algorithm in addition to RSA, under
46 GnuTLS 3.6.0 or OpenSSL 1.1.1 or later.
47
48 10. Builtin feature-macros _CRYPTO_HASH_SHA3 and _CRYPTO_SIGN_ED25519, library
49 version dependent.
50
51 11. "exim -bP macro <name>" returns caller-usable status.
52
53 12. Expansion item ${authresults {<machine>}} for creating an
54 Authentication-Results: header.
55
56 13. EXPERIMENTAL_ARC. See the experimental.spec file.
57 See also new util/renew-opendmarc-tlds.sh script for use with DMARC/ARC.
58
59 14: A dane:fail event, intended to facilitate reporting.
60
61 15. "Lightweight" support for Redis Cluster. Requires redis_servers list to
62 contain all the servers in the cluster, all of which must be reachable from
63 the running exim instance. If the cluster has master/slave replication, the
64 list must contain all the master and slave servers.
65
66 16. Add an option to the Avast scanner interface: "pass_unscanned". This
67 allows to treat unscanned files as clean. Files may be unscanned for
68 several reasons: decompression bombs, broken archives.
69
70
71 Version 4.90
72 ------------
73
74 1. PKG_CONFIG_PATH can now be set in Local/Makefile;
75 wildcards will be expanded, values are collapsed.
76
77 2. The ${readsocket } expansion now takes an option to not shutdown the
78 connection after sending the query string. The default remains to do so.
79
80 3. An smtp transport option "hosts_noproxy_tls" to control whether multiple
81 deliveries on a single TCP connection can maintain a TLS connection
82 open. By default disabled for all hosts, doing so saves the cost of
83 making new TLS sessions, at the cost of having to proxy the data via
84 another process. Logging is also affected.
85
86 4. A malware connection type for the FPSCAND protocol.
87
88 5. An option for recipient verify callouts to hold the connection open for
89 further recipients and for delivery.
90
91 6. The reproducible build $SOURCE_DATE_EPOCH environment variable is now
92 supported.
93
94 7. Optionally, an alternate format for spool data-files which matches the
95 wire format - meaning more efficient reception and transmission (at the
96 cost of difficulty with standard Unix tools). Only used for messages
97 received using the ESMTP CHUNKING option, and when a new main-section
98 option "spool_wireformat" (false by default) is set.
99
100 8. New main configuration option "commandline_checks_require_admin" to
101 restrict who can use various introspection options.
102
103 9. New option modifier "no_check" for quota and quota_filecount
104 appendfile transport.
105
106 10. Variable $smtp_command_history returning a comma-sep list of recent
107 SMTP commands.
108
109 11. Millisecond timetamps in logs, on log_selector "millisec". Also affects
110 log elements QT, DT and D, and timstamps in debug output.
111
112 12. TCP Fast Open logging. As a server, logs when the SMTP banner was sent
113 while still in SYN_RECV state; as a client logs when the connection
114 is opened with a TFO cookie.
115
116 13. DKIM support for multiple signing, by domain and/or key-selector.
117 DKIM support for multiple hashes, and for alternate-identity tags.
118 Builtin macro with default list of signed headers.
119 Better syntax for specifying oversigning.
120 The DKIM ACL can override verification status, and status is visible in
121 the data ACL.
122
123 14. Exipick understands -C|--config for an alternative Exim
124 configuration file.
125
126 15. TCP Fast Open used, with data-on-SYN, for client SMTP via SOCKS5 proxy,
127 for ${readsocket } expansions, and for ClamAV.
128
129 16. The "-be" expansion test mode now supports macros. Macros are expanded
130 in test lines, and new macros can be defined.
131
132 17. Support for server-side dual-certificate-stacks (eg. RSA + ECDSA).
133
134
135 Version 4.89
136 ------------
137
138 1. Allow relative config file names for ".include"
139
140 2. A main-section config option "debug_store" to control the checks on
141 variable locations during store-reset. Normally false but can be enabled
142 when a memory corrution issue is suspected on a production system.
143
144
145 Version 4.88
146 ------------
147
148 1. The new perl_taintmode option allows to run the embedded perl
149 interpreter in taint mode.
150
151 2. New log_selector: dnssec, adds a "DS" tag to acceptance and delivery lines.
152
153 3. Speculative debugging, via a "kill" option to the "control=debug" ACL
154 modifier.
155
156 4. New expansion item ${sha3:<string>} / ${sha3_<N>:<string>}.
157 N can be 224, 256 (default), 384, 512.
158 With GnuTLS 3.5.0 or later, only.
159
160 5. Facility for named queues: A command-line argument can specify
161 the queue name for a queue operation, and an ACL modifier can set
162 the queue to be used for a message. A $queue_name variable gives
163 visibility.
164
165 6. New expansion operators base32/base32d.
166
167 7. The CHUNKING ESMTP extension from RFC 3030. May give some slight
168 performance increase and network load decrease. Main config option
169 chunking_advertise_hosts, and smtp transport option hosts_try_chunking
170 for control.
171
172 8. LMDB lookup support, as Experimental. Patch supplied by Andrew Colin Kissa.
173
174 9. Expansion operator escape8bit, like escape but not touching newline etc..
175
176 10. Feature macros, generated from compile options. All start with "_HAVE_"
177 and go on with some roughly recognisable name. Driver macros, for
178 router, transport and authentication drivers; names starting with "_DRIVER_".
179 Option macros, for each configuration-file option; all start with "_OPT_".
180 Use the "-bP macros" command-line option to see what is present.
181
182 11. Integer values for options can take a "G" multiplier.
183
184 12. defer=pass option for the ACL control cutthrough_delivery, to reflect 4xx
185 returns from the target back to the initiator, rather than spooling the
186 message.
187
188 13. New built-in constants available for tls_dhparam and default changed.
189
190 14. If built with EXPERIMENTAL_QUEUEFILE, a queuefile transport, for writing
191 out copies of the message spool files for use by 3rd-party scanners.
192
193 15. A new option on the smtp transport, hosts_try_fastopen. If the system
194 supports it (on Linux it must be enabled in the kernel by the sysadmin)
195 try to use RFC 7413 "TCP Fast Open". No data is sent on the SYN segment
196 but it permits a peer that also supports the facility to send its SMTP
197 banner immediately after the SYN,ACK segment rather then waiting for
198 another ACK - so saving up to one roundtrip time. Because it requires
199 previous communication with the peer (we save a cookie from it) this
200 will only become active on frequently-contacted destinations.
201
202 16. A new syslog_pid option to suppress PID duplication in syslog lines.
203
204
205 Version 4.87
206 ------------
207
208 1. The ACL conditions regex and mime_regex now capture substrings
209 into numeric variables $regex1 to 9, like the "match" expansion condition.
210
211 2. New $callout_address variable records the address used for a spam=,
212 malware= or verify= callout.
213
214 3. Transports now take a "max_parallel" option, to limit concurrency.
215
216 4. Expansion operators ${ipv6norm:<string>} and ${ipv6denorm:<string>}.
217 The latter expands to a 8-element colon-sep set of hex digits including
218 leading zeroes. A trailing ipv4-style dotted-decimal set is converted
219 to hex. Pure ipv4 addresses are converted to IPv4-mapped IPv6.
220 The former operator strips leading zeroes and collapses the longest
221 set of 0-groups to a double-colon.
222
223 5. New "-bP config" support, to dump the effective configuration.
224
225 6. New $dkim_key_length variable.
226
227 7. New base64d and base64 expansion items (the existing str2b64 being a
228 synonym of the latter). Add support in base64 for certificates.
229
230 8. New main configuration option "bounce_return_linesize_limit" to
231 avoid oversize bodies in bounces. The default value matches RFC
232 limits.
233
234 9. New $initial_cwd expansion variable.
235
236
237 Version 4.86
238 ------------
239
240 1. Support for using the system standard CA bundle.
241
242 2. New expansion items $config_file, $config_dir, containing the file
243 and directory name of the main configuration file. Also $exim_version.
244
245 3. New "malware=" support for Avast.
246
247 4. New "spam=" variant option for Rspamd.
248
249 5. Assorted options on malware= and spam= scanners.
250
251 6. A command-line option to write a comment into the logfile.
252
253 7. If built with EXPERIMENTAL_SOCKS feature enabled, the smtp transport can
254 be configured to make connections via socks5 proxies.
255
256 8. If built with EXPERIMENTAL_INTERNATIONAL, support is included for
257 the transmission of UTF-8 envelope addresses.
258
259 9. If built with EXPERIMENTAL_INTERNATIONAL, an expansion item for a commonly
260 used encoding of Maildir folder names.
261
262 10. A logging option for slow DNS lookups.
263
264 11. New ${env {<variable>}} expansion.
265
266 12. A non-SMTP authenticator using information from TLS client certificates.
267
268 13. Main option "tls_eccurve" for selecting an Elliptic Curve for TLS.
269 Patch originally by Wolfgang Breyha.
270
271 14. Main option "dns_trust_aa" for trusting your local nameserver at the
272 same level as DNSSEC.
273
274
275 Version 4.85
276 ------------
277
278 1. If built with EXPERIMENTAL_DANE feature enabled, Exim will follow the
279 DANE SMTP draft to assess a secure chain of trust of the certificate
280 used to establish the TLS connection based on a TLSA record in the
281 domain of the sender.
282
283 2. The EXPERIMENTAL_TPDA feature has been renamed to EXPERIMENTAL_EVENT
284 and several new events have been created. The reason is because it has
285 been expanded beyond just firing events during the transport phase. Any
286 existing TPDA transport options will have to be rewritten to use a new
287 $event_name expansion variable in a condition. Refer to the
288 experimental-spec.txt for details and examples.
289
290 3. The EXPERIMENTAL_CERTNAMES features is an enhancement to verify that
291 server certs used for TLS match the result of the MX lookup. It does
292 not use the same mechanism as DANE.
293
294
295 Version 4.84
296 ------------
297
298
299 Version 4.83
300 ------------
301
302 1. If built with the EXPERIMENTAL_PROXY feature enabled, Exim can be
303 configured to expect an initial header from a proxy that will make the
304 actual external source IP:host be used in exim instead of the IP of the
305 proxy that is connecting to it.
306
307 2. New verify option header_names_ascii, which will check to make sure
308 there are no non-ASCII characters in header names. Exim itself handles
309 those non-ASCII characters, but downstream apps may not, so Exim can
310 detect and reject if those characters are present.
311
312 3. New expansion operator ${utf8clean:string} to replace malformed UTF8
313 codepoints with valid ones.
314
315 4. New malware type "sock". Talks over a Unix or TCP socket, sending one
316 command line and matching a regex against the return data for trigger
317 and a second regex to extract malware_name. The mail spoolfile name can
318 be included in the command line.
319
320 5. The smtp transport now supports options "tls_verify_hosts" and
321 "tls_try_verify_hosts". If either is set the certificate verification
322 is split from the encryption operation. The default remains that a failed
323 verification cancels the encryption.
324
325 6. New SERVERS override of default ldap server list. In the ACLs, an ldap
326 lookup can now set a list of servers to use that is different from the
327 default list.
328
329 7. New command-line option -C for exiqgrep to specify alternate exim.conf
330 file when searching the queue.
331
332 8. OCSP now supports GnuTLS also, if you have version 3.1.3 or later of that.
333
334 9. Support for DNSSEC on outbound connections.
335
336 10. New variables "tls_(in,out)_(our,peer)cert" and expansion item
337 "certextract" to extract fields from them. Hash operators md5 and sha1
338 work over them for generating fingerprints, and a new sha256 operator
339 for them added.
340
341 11. PRDR is now supported dy default.
342
343 12. OCSP stapling is now supported by default.
344
345 13. If built with the EXPERIMENTAL_DSN feature enabled, Exim will output
346 Delivery Status Notification messages in MIME format, and negotiate
347 DSN features per RFC 3461.
348
349
350 Version 4.82
351 ------------
352
353 1. New command-line option -bI:sieve will list all supported sieve extensions
354 of this Exim build on standard output, one per line.
355 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
356 query this to establish the correct list to include in the protocol's
357 SIEVE capability line.
358
359 2. If the -n option is combined with the -bP option, then the name of an
360 emitted option is not output, only the value (if visible to you).
361 For instance, "exim -n -bP pid_file_path" should just emit a pathname
362 followed by a newline, and no other text.
363
364 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
365 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
366 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
367 acceptable for security. (Option accepted but ignored if using OpenSSL).
368 Defaults to 1024, the old value. May be lowered only to 512, or raised as
369 far as you like. Raising this may hinder TLS interoperability with other
370 sites and is not currently recommended. Lowering this will permit you to
371 establish a TLS session which is not as secure as you might like.
372
373 Unless you really know what you are doing, leave it alone.
374
375 4. If not built with DISABLE_DNSSEC, Exim now has the main option
376 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
377 to send the DO flag to your recursive resolver. If you have a recursive
378 resolver, which can set the Authenticated Data (AD) flag in results, Exim
379 can now detect this. Exim does not perform validation itself, instead
380 relying upon a trusted path to the resolver.
381
382 Current status: work-in-progress; $sender_host_dnssec variable added.
383
384 5. DSCP support for outbound connections: on a transport using the smtp driver,
385 set "dscp = ef", for instance, to cause the connections to have the relevant
386 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
387
388 Similarly for inbound connections, there is a new control modifier, dscp,
389 so "warn control = dscp/ef" in the connect ACL, or after authentication.
390
391 Supported values depend upon system libraries. "exim -bI:dscp" to list the
392 ones Exim knows of. You can also set a raw number 0..0x3F.
393
394 6. The -G command-line flag is no longer ignored; it is now equivalent to an
395 ACL setting "control = suppress_local_fixups". The -L command-line flag
396 is now accepted and forces use of syslog, with the provided tag as the
397 process name. A few other flags used by Sendmail are now accepted and
398 ignored.
399
400 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
401 ACL modifier; works for single-recipient mails which are received on and
402 deliverable via SMTP. Using the connection made for a recipient verify,
403 if requested before the verify, or a new one made for the purpose while
404 the inbound connection is still active. The bulk of the mail item is copied
405 direct from the inbound socket to the outbound (as well as the spool file).
406 When the source notifies the end of data, the data acceptance by the destination
407 is negotiated before the acceptance is sent to the source. If the destination
408 does not accept the mail item, for example due to content-scanning, the item
409 is not accepted from the source and therefore there is no need to generate
410 a bounce mail. This is of benefit when providing a secondary-MX service.
411 The downside is that delays are under the control of the ultimate destination
412 system not your own.
413
414 The Received-by: header on items delivered by cutthrough is generated
415 early in reception rather than at the end; this will affect any timestamp
416 included. The log line showing delivery is recorded before that showing
417 reception; it uses a new ">>" tag instead of "=>".
418
419 To support the feature, verify-callout connections can now use ESMTP and TLS.
420 The usual smtp transport options are honoured, plus a (new, default everything)
421 hosts_verify_avoid_tls.
422
423 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
424 for specific access to the information for each connection. The old names
425 are present for now but deprecated.
426
427 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
428
429 8. New expansion operators ${listnamed:name} to get the content of a named list
430 and ${listcount:string} to count the items in a list.
431
432 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
433 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
434 modules. For some situations this is desirable, but we expect admin in
435 those situations to know they want the feature. More commonly, it means
436 that GUI user modules get loaded and are broken by the setuid Exim being
437 unable to access files specified in environment variables and passed
438 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
439 unless this new option is set.
440
441 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
442 so have also added a build option which can be used to build Exim with GnuTLS
443 but without trying to use any kind of PKCS11 support. Uncomment this in the
444 Local/Makefile:
445
446 AVOID_GNUTLS_PKCS11=yes
447
448 10. The "acl = name" condition on an ACL now supports optional arguments.
449 New expansion item "${acl {name}{arg}...}" and expansion condition
450 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
451 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
452 Variable $acl_narg contains the number of arguments. If the ACL sets
453 a "message =" value this becomes the result of the expansion item,
454 or the value of $value for the expansion condition. If the ACL returns
455 accept the expansion condition is true; if reject, false. A defer
456 return results in a forced fail.
457
458 11. Routers and transports can now have multiple headers_add and headers_remove
459 option lines. The concatenated list is used.
460
461 12. New ACL modifier "remove_header" can remove headers before message gets
462 handled by routers/transports.
463
464 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
465 "aaaa" and "a" lookups is done and the full set of results returned.
466
467 14. New expansion variable $headers_added with content from ACL add_header
468 modifier (but not yet added to message).
469
470 15. New 8bitmime status logging option for received messages. Log field "M8S".
471
472 16. New authenticated_sender logging option, adding to log field "A".
473
474 17. New expansion variables $router_name and $transport_name. Useful
475 particularly for debug_print as -bt command-line option does not
476 require privilege whereas -d does.
477
478 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
479 proposed extension to SMTP from Eric Hall.
480
481 19. The pipe transport has gained the force_command option, to allow
482 decorating commands from user .forward pipe aliases with prefix
483 wrappers, for instance.
484
485 20. Callout connections can now AUTH; the same controls as normal delivery
486 connections apply.
487
488 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
489 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
490 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
491 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
492 dmarc_status. It adds new control flags dmarc_disable_verify and
493 dmarc_enable_forensic. The default for the dmarc_tld_file option is
494 "/etc/exim/opendmarc.tlds" and can be changed via EDITME.
495
496 22. Add expansion variable $authenticated_fail_id, which is the username
497 provided to the authentication method which failed. It is available
498 for use in subsequent ACL processing (typically quit or notquit ACLs).
499
500 23. New ACL modifier "udpsend" can construct a UDP packet to send to a given
501 UDP host and port.
502
503 24. New ${hexquote:..string..} expansion operator converts non-printable
504 characters in the string to \xNN form.
505
506 25. Experimental TPDA (Transport Post Delivery Action) function added.
507 Patch provided by Axel Rau.
508
509 26. Experimental Redis lookup added. Patch provided by Warren Baker.
510
511
512 Version 4.80
513 ------------
514
515 1. New authenticator driver, "gsasl". Server-only (at present).
516 This is a SASL interface, licensed under GPL, which can be found at
517 http://www.gnu.org/software/gsasl/.
518 This system does not provide sources of data for authentication, so
519 careful use needs to be made of the conditions in Exim.
520
521 2. New authenticator driver, "heimdal_gssapi". Server-only.
522 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
523 is no longer honoured for setuid programs by Heimdal. Use the
524 "server_keytab" option to point to the keytab.
525
526 3. The "pkg-config" system can now be used when building Exim to reference
527 cflags and library information for lookups and authenticators, rather
528 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
529 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
530 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
531
532 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
533 find the headers and libraries for PCRE.
534
535 4. New expansion variable $tls_bits.
536
537 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
538 be joined together with ASCII NUL characters to construct the key to pass
539 into the DBM library. Can be used with gsasl to access sasldb2 files as
540 used by Cyrus SASL.
541
542 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
543
544 Avoid release 1.0.1a if you can. Note that the default value of
545 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
546 increased susceptibility to attack. This may still have interoperability
547 implications for very old clients (see version 4.31 change 37) but
548 administrators can choose to make the trade-off themselves and restore
549 compatibility at the cost of session security.
550
551 7. Use of the new expansion variable $tls_sni in the main configuration option
552 tls_certificate will cause Exim to re-expand the option, if the client
553 sends the TLS Server Name Indication extension, to permit choosing a
554 different certificate; tls_privatekey will also be re-expanded. You must
555 still set these options to expand to valid files when $tls_sni is not set.
556
557 The SMTP Transport has gained the option tls_sni, which will set a hostname
558 for outbound TLS sessions, and set $tls_sni too.
559
560 A new log_selector, +tls_sni, has been added, to log received SNI values
561 for Exim as a server.
562
563 8. The existing "accept_8bitmime" option now defaults to true. This means
564 that Exim is deliberately not strictly RFC compliant. We're following
565 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
566 Those who disagree, or know that they are talking to mail servers that,
567 even today, are not 8-bit clean, need to turn off this option.
568
569 9. Exim can now be started with -bw (with an optional timeout, given as
570 -bw<timespec>). With this, stdin at startup is a socket that is
571 already listening for connections. This has a more modern name of
572 "socket activation", but forcing the activated socket to fd 0. We're
573 interested in adding more support for modern variants.
574
575 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
576 for numbers indicates multiplication by 1024^3.
577
578 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
579 gnutls_require_mac & gnutls_require_protocols are no longer supported.
580 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
581 string, documentation for which is at:
582 http://www.gnutls.org/manual/html_node/Priority-Strings.html
583
584 SNI support has been added to Exim's GnuTLS integration too.
585
586 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
587 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
588
589 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
590 is now available. If the contents of the file are valid, then Exim will
591 send that back in response to a TLS status request; this is OCSP Stapling.
592 Exim will not maintain the contents of the file in any way: administrators
593 are responsible for ensuring that it is up-to-date.
594
595 See "experimental-spec.txt" for more details.
596
597 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
598 identically to TXT record lookups.
599
600 14. New expansion variable $tod_epoch_l for higher-precision time.
601
602 15. New global option tls_dh_max_bits, defaulting to current value of NSS
603 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
604 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
605
606 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
607 Option can now be a path or an identifier for a standard prime.
608 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
609 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
610 primes.
611
612 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
613 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
614 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
615
616
617 Version 4.77
618 ------------
619
620 1. New options for the ratelimit ACL condition: /count= and /unique=.
621 The /noupdate option has been replaced by a /readonly option.
622
623 2. The SMTP transport's protocol option may now be set to "smtps", to
624 use SSL-on-connect outbound.
625
626 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
627 there is a problem talking to the AV scanner, or the AV scanner running.
628
629 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
630 and check if the search item is a member of the list. This does not
631 support named lists, but does subject the list part to string expansion.
632
633 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
634 built, Exim no longer performs string expansion on the second string of
635 the match_* expansion conditions: "match_address", "match_domain",
636 "match_ip" & "match_local_part". Named lists can still be used.
637
638
639 Version 4.76
640 ------------
641
642 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
643 or off in the resolver library.
644
645
646 Version 4.75
647 ------------
648
649 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
650 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
651 libraries. The following global options have been added in support of
652 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
653 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
654
655 2. The pipe transport now takes a boolean option, "freeze_signal", default
656 false. When true, if the external delivery command exits on a signal then
657 Exim will freeze the message in the queue, instead of generating a bounce.
658
659 3. Log filenames may now use %M as an escape, instead of %D (still available).
660 The %M pattern expands to yyyymm, providing month-level resolution.
661
662 4. The $message_linecount variable is now updated for the maildir_tag option,
663 in the same way as $message_size, to reflect the real number of lines,
664 including any header additions or removals from transport.
665
666 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
667 Exim now selects entries randomly, to better scale in a cluster setup.
668
669
670 Version 4.74
671 ------------
672
673 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
674 the flaw permitted the Exim run-time user to cause root to append to
675 arbitrary files of the attacker's choosing, with the content based
676 on content supplied by the attacker.
677
678 2. Exim now supports loading some lookup types at run-time, using your
679 platform's dlopen() functionality. This has limited platform support
680 and the intention is not to support every variant, it's limited to
681 dlopen(). This permits the main Exim binary to not be linked against
682 all the libraries needed for all the lookup types.
683
684
685 Version 4.73
686 ------------
687
688 NOTE: this version is not guaranteed backwards-compatible, please read the
689 items below carefully
690
691 1. A new main configuration option, "openssl_options", is available if Exim
692 is built with SSL support provided by OpenSSL. The option allows
693 administrators to specify OpenSSL options to be used on connections;
694 typically this is to set bug compatibility features which the OpenSSL
695 developers have not enabled by default. There may be security
696 consequences for certain options, so these should not be changed
697 frivolously.
698
699 2. A new pipe transport option, "permit_coredumps", may help with problem
700 diagnosis in some scenarios. Note that Exim is typically installed as
701 a setuid binary, which on most OSes will inhibit coredumps by default,
702 so that safety mechanism would have to be overridden for this option to
703 be able to take effect.
704
705 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
706 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
707 Note that this switches Exim to use a new API ("INSTREAM") and a future
708 release of ClamAV will remove support for the old API ("STREAM").
709
710 The av_scanner option, when set to "clamd", now takes an optional third
711 part, "local", which causes Exim to pass a filename to ClamAV instead of
712 the file content. This is the same behaviour as when clamd is pointed at
713 a Unix-domain socket. For example:
714
715 av_scanner = clamd:192.0.2.3 1234:local
716
717 ClamAV's ExtendedDetectionInfo response format is now handled.
718
719 4. There is now a -bmalware option, restricted to admin users. This option
720 takes one parameter, a filename, and scans that file with Exim's
721 malware-scanning framework. This is intended purely as a debugging aid
722 to ensure that Exim's scanning is working, not to replace other tools.
723 Note that the ACL framework is not invoked, so if av_scanner references
724 ACL variables without a fallback then this will fail.
725
726 5. There is a new expansion operator, "reverse_ip", which will reverse IP
727 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
728
729 ${reverse_ip:192.0.2.4}
730 -> 4.2.0.192
731 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
732 -> 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
733
734 6. There is a new ACL control called "debug", to enable debug logging.
735 This allows selective logging of certain incoming transactions within
736 production environments, with some care. It takes two options, "tag"
737 and "opts"; "tag" is included in the filename of the log and "opts"
738 is used as per the -d<options> command-line option. Examples, which
739 don't all make sense in all contexts:
740
741 control = debug
742 control = debug/tag=.$sender_host_address
743 control = debug/opts=+expand+acl
744 control = debug/tag=.$message_exim_id/opts=+expand
745
746 7. It has always been implicit in the design and the documentation that
747 "the Exim user" is not root. src/EDITME said that using root was
748 "very strongly discouraged". This is not enough to keep people from
749 shooting themselves in the foot in days when many don't configure Exim
750 themselves but via package build managers. The security consequences of
751 running various bits of network code are severe if there should be bugs in
752 them. As such, the Exim user may no longer be root. If configured
753 statically, Exim will refuse to build. If configured as ref:user then Exim
754 will exit shortly after start-up. If you must shoot yourself in the foot,
755 then henceforth you will have to maintain your own local patches to strip
756 the safeties off.
757
758 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
759 condition logic to determine truth/failure and will fail to expand many
760 strings, bool_lax{} uses the router condition logic, where most strings
761 do evaluate true.
762 Note: bool{00} is false, bool_lax{00} is true.
763
764 9. Routers now support multiple "condition" tests.
765
766 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
767 Setting this allows an admin to define which entry in the tcpwrappers
768 config file will be used to control access to the daemon. This option
769 is only available when Exim is built with USE_TCP_WRAPPERS. The
770 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
771 build option.
772
773 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
774 the Exim run-time user, instead of root.
775
776 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
777 is forced on. This is mitigated by the new build option
778 TRUSTED_CONFIG_LIST which defines a list of configuration files which
779 are trusted; one per line. If a config file is owned by root and matches
780 a pathname in the list, then it may be invoked by the Exim build-time
781 user without Exim relinquishing root privileges.
782
783 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
784 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
785 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
786 include the main config. As a transition mechanism, we are temporarily
787 providing a work-around: the new build option WHITELIST_D_MACROS provides
788 a colon-separated list of macro names which may be overridden by the Exim
789 run-time user. The values of these macros are constrained to the regex
790 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
791
792
793 Version 4.72
794 ------------
795
796 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
797 writable, the other to locking of MBX folders (not mbox).
798
799 2. MySQL stored procedures are now supported.
800
801 3. The dkim_domain transport option is now a list, not a single string, and
802 messages will be signed for each element in the list (discarding
803 duplicates).
804
805 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
806 in the presence of multiple character strings within the RR. Prior to 4.70,
807 only the first string would be returned. The dnsdb lookup now, by default,
808 preserves the pre-4.70 semantics, but also now takes an extended output
809 separator specification. The separator can be followed by a semicolon, to
810 concatenate the individual text strings together with no join character,
811 or by a comma and a second separator character, in which case the text
812 strings within a TXT record are joined on that second character.
813 Administrators are reminded that DNS provides no ordering guarantees
814 between multiple records in an RRset. For example:
815
816 foo.example. IN TXT "a" "b" "c"
817 foo.example. IN TXT "d" "e" "f"
818
819 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
820 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
821 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
822
823
824 Version 4.70 / 4.71
825 -------------------
826
827 1. Native DKIM support without an external library.
828 (Note that if no action to prevent it is taken, a straight upgrade will
829 result in DKIM verification of all signed incoming emails. See spec
830 for details on conditionally disabling)
831
832 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
833
834 3. There is now a bool{} expansion condition which maps certain strings to
835 true/false condition values (most likely of use in conjunction with the
836 and{} expansion operator).
837
838 4. The $spam_score, $spam_bar and $spam_report variables are now available
839 at delivery time.
840
841 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
842 options, provided that Exim is invoked by an admin_user.
843
844 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
845 which increases compatibility with older clients at the cost of decreased
846 security. Don't set this unless you need to support such clients.
847
848 7. There is a new expansion operator, ${randint:...} which will produce a
849 "random" number less than the supplied integer. This randomness is
850 not guaranteed to be cryptographically strong, but depending upon how
851 Exim was built may be better than the most naive schemes.
852
853 8. Exim now explicitly ensures that SHA256 is available when linked against
854 OpenSSL.
855
856 9. The transport_filter_timeout option now applies to SMTP transports too.
857
858
859 Version 4.69
860 ------------
861
862 1. Preliminary DKIM support in Experimental.
863
864
865 Version 4.68
866 ------------
867
868 1. The body_linecount and body_zerocount C variables are now exported in the
869 local_scan API.
870
871 2. When a dnslists lookup succeeds, the key that was looked up is now placed
872 in $dnslist_matched. When the key is an IP address, it is not reversed in
873 this variable (though it is, of course, in the actual lookup). In simple
874 cases, for example:
875
876 deny dnslists = spamhaus.example
877
878 the key is also available in another variable (in this case,
879 $sender_host_address). In more complicated cases, however, this is not
880 true. For example, using a data lookup might generate a dnslists lookup
881 like this:
882
883 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
884
885 If this condition succeeds, the value in $dnslist_matched might be
886 192.168.6.7 (for example).
887
888 3. Authenticators now have a client_condition option. When Exim is running as
889 a client, it skips an authenticator whose client_condition expansion yields
890 "0", "no", or "false". This can be used, for example, to skip plain text
891 authenticators when the connection is not encrypted by a setting such as:
892
893 client_condition = ${if !eq{$tls_cipher}{}}
894
895 Note that the 4.67 documentation states that $tls_cipher contains the
896 cipher used for incoming messages. In fact, during SMTP delivery, it
897 contains the cipher used for the delivery. The same is true for
898 $tls_peerdn.
899
900 4. There is now a -Mvc <message-id> option, which outputs a copy of the
901 message to the standard output, in RFC 2822 format. The option can be used
902 only by an admin user.
903
904 5. There is now a /noupdate option for the ratelimit ACL condition. It
905 computes the rate and checks the limit as normal, but it does not update
906 the saved data. This means that, in relevant ACLs, it is possible to lookup
907 the existence of a specified (or auto-generated) ratelimit key without
908 incrementing the ratelimit counter for that key.
909
910 In order for this to be useful, another ACL entry must set the rate
911 for the same key somewhere (otherwise it will always be zero).
912
913 Example:
914
915 acl_check_connect:
916 # Read the rate; if it doesn't exist or is below the maximum
917 # we update it below
918 deny ratelimit = 100 / 5m / strict / noupdate
919 log_message = RATE: $sender_rate / $sender_rate_period \
920 (max $sender_rate_limit)
921
922 [... some other logic and tests...]
923
924 warn ratelimit = 100 / 5m / strict / per_cmd
925 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
926 (max $sender_rate_limit)
927 condition = ${if le{$sender_rate}{$sender_rate_limit}}
928
929 accept
930
931 6. The variable $max_received_linelength contains the number of bytes in the
932 longest line that was received as part of the message, not counting the
933 line termination character(s).
934
935 7. Host lists can now include +ignore_defer and +include_defer, analagous to
936 +ignore_unknown and +include_unknown. These options should be used with
937 care, probably only in non-critical host lists such as whitelists.
938
939 8. There's a new option called queue_only_load_latch, which defaults true.
940 If set false when queue_only_load is greater than zero, Exim re-evaluates
941 the load for each incoming message in an SMTP session. Otherwise, once one
942 message is queued, the remainder are also.
943
944 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
945 cases when an SMTP session ends without sending QUIT. However, when Exim
946 itself is is bad trouble, such as being unable to write to its log files,
947 this ACL is not run, because it might try to do things (such as write to
948 log files) that make the situation even worse.
949
950 Like the QUIT ACL, this new ACL is provided to make it possible to gather
951 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
952 modifier is forbidden in this ACL.
953
954 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
955 to a string that indicates the reason for the termination of the SMTP
956 connection. The possible values are:
957
958 acl-drop Another ACL issued a "drop" command
959 bad-commands Too many unknown or non-mail commands
960 command-timeout Timeout while reading SMTP commands
961 connection-lost The SMTP connection has been lost
962 data-timeout Timeout while reading message data
963 local-scan-error The local_scan() function crashed
964 local-scan-timeout The local_scan() function timed out
965 signal-exit SIGTERM or SIGINT
966 synchronization-error SMTP synchronization error
967 tls-failed TLS failed to start
968
969 In most cases when an SMTP connection is closed without having received
970 QUIT, Exim sends an SMTP response message before actually closing the
971 connection. With the exception of acl-drop, the default message can be
972 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
973 "drop" verb in another ACL, it is the message from the other ACL that is
974 used.
975
976 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
977 servers with individual queries. This is done by starting the query with
978 "servers=x:y:z;", where each item in the list may take one of two forms:
979
980 (1) If it is just a host name, the appropriate global option (mysql_servers
981 or pgsql_servers) is searched for a host of the same name, and the
982 remaining parameters (database, user, password) are taken from there.
983
984 (2) If it contains any slashes, it is taken as a complete parameter set.
985
986 The list of servers is used in exactly the same was as the global list.
987 Once a connection to a server has happened and a query has been
988 successfully executed, processing of the lookup ceases.
989
990 This feature is intended for use in master/slave situations where updates
991 are occurring, and one wants to update a master rather than a slave. If the
992 masters are in the list for reading, you might have:
993
994 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
995
996 In an updating lookup, you could then write
997
998 ${lookup mysql{servers=master; UPDATE ...}
999
1000 If, on the other hand, the master is not to be used for reading lookups:
1001
1002 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
1003
1004 you can still update the master by
1005
1006 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
1007
1008 11. The message_body_newlines option (default FALSE, for backwards
1009 compatibility) can be used to control whether newlines are present in
1010 $message_body and $message_body_end. If it is FALSE, they are replaced by
1011 spaces.
1012
1013
1014 Version 4.67
1015 ------------
1016
1017 1. There is a new log selector called smtp_no_mail, which is not included in
1018 the default setting. When it is set, a line is written to the main log
1019 whenever an accepted SMTP connection terminates without having issued a
1020 MAIL command.
1021
1022 2. When an item in a dnslists list is followed by = and & and a list of IP
1023 addresses, the behaviour was not clear when the lookup returned more than
1024 one IP address. This has been solved by the addition of == and =& for "all"
1025 rather than the default "any" matching.
1026
1027 3. Up till now, the only control over which cipher suites GnuTLS uses has been
1028 for the cipher algorithms. New options have been added to allow some of the
1029 other parameters to be varied.
1030
1031 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
1032 set, Exim compiles a runtime option called disable_fsync.
1033
1034 5. There is a new variable called $smtp_count_at_connection_start.
1035
1036 6. There's a new control called no_pipelining.
1037
1038 7. There are two new variables called $sending_ip_address and $sending_port.
1039 These are set whenever an SMTP connection to another host has been set up.
1040
1041 8. The expansion of the helo_data option in the smtp transport now happens
1042 after the connection to the server has been made.
1043
1044 9. There is a new expansion operator ${rfc2047d: that decodes strings that
1045 are encoded as per RFC 2047.
1046
1047 10. There is a new log selector called "pid", which causes the current process
1048 id to be added to every log line, in square brackets, immediately after the
1049 time and date.
1050
1051 11. Exim has been modified so that it flushes SMTP output before implementing
1052 a delay in an ACL. It also flushes the output before performing a callout,
1053 as this can take a substantial time. These behaviours can be disabled by
1054 obeying control = no_delay_flush or control = no_callout_flush,
1055 respectively, at some earlier stage of the connection.
1056
1057 12. There are two new expansion conditions that iterate over a list. They are
1058 called forany and forall.
1059
1060 13. There's a new global option called dsn_from that can be used to vary the
1061 contents of From: lines in bounces and other automatically generated
1062 messages ("delivery status notifications" - hence the name of the option).
1063
1064 14. The smtp transport has a new option called hosts_avoid_pipelining.
1065
1066 15. By default, exigrep does case-insensitive matches. There is now a -I option
1067 that makes it case-sensitive.
1068
1069 16. A number of new features ("addresses", "map", "filter", and "reduce") have
1070 been added to string expansions to make it easier to process lists of
1071 items, typically addresses.
1072
1073 17. There's a new ACL modifier called "continue". It does nothing of itself,
1074 and processing of the ACL always continues with the next condition or
1075 modifier. It is provided so that the side effects of expanding its argument
1076 can be used.
1077
1078 18. It is now possible to use newline and other control characters (those with
1079 values less than 32, plus DEL) as separators in lists.
1080
1081 19. The exigrep utility now has a -v option, which inverts the matching
1082 condition.
1083
1084 20. The host_find_failed option in the manualroute router can now be set to
1085 "ignore".
1086
1087
1088 Version 4.66
1089 ------------
1090
1091 No new features were added to 4.66.
1092
1093
1094 Version 4.65
1095 ------------
1096
1097 No new features were added to 4.65.
1098
1099
1100 Version 4.64
1101 ------------
1102
1103 1. ACL variables can now be given arbitrary names, as long as they start with
1104 "acl_c" or "acl_m" (for connection variables and message variables), are at
1105 least six characters long, with the sixth character being either a digit or
1106 an underscore.
1107
1108 2. There is a new ACL modifier called log_reject_target. It makes it possible
1109 to specify which logs are used for messages about ACL rejections.
1110
1111 3. There is a new authenticator called "dovecot". This is an interface to the
1112 authentication facility of the Dovecot POP/IMAP server, which can support a
1113 number of authentication methods.
1114
1115 4. The variable $message_headers_raw provides a concatenation of all the
1116 messages's headers without any decoding. This is in contrast to
1117 $message_headers, which does RFC2047 decoding on the header contents.
1118
1119 5. In a DNS black list, if two domain names, comma-separated, are given, the
1120 second is used first to do an initial check, making use of any IP value
1121 restrictions that are set. If there is a match, the first domain is used,
1122 without any IP value restrictions, to get the TXT record.
1123
1124 6. All authenticators now have a server_condition option.
1125
1126 7. There is a new command-line option called -Mset. It is useful only in
1127 conjunction with -be (that is, when testing string expansions). It must be
1128 followed by a message id; Exim loads the given message from its spool
1129 before doing the expansions.
1130
1131 8. Another similar new command-line option is called -bem. It operates like
1132 -be except that it must be followed by the name of a file that contains a
1133 message.
1134
1135 9. When an address is delayed because of a 4xx response to a RCPT command, it
1136 is now the combination of sender and recipient that is delayed in
1137 subsequent queue runs until its retry time is reached.
1138
1139 10. Unary negation and the bitwise logical operators and, or, xor, not, and
1140 shift, have been added to the eval: and eval10: expansion items.
1141
1142 11. The variables $interface_address and $interface_port have been renamed
1143 as $received_ip_address and $received_port, to make it clear that they
1144 relate to message reception rather than delivery. (The old names remain
1145 available for compatibility.)
1146
1147 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
1148 to vary the message that is sent when an SMTP command is accepted.
1149
1150
1151 Version 4.63
1152 ------------
1153
1154 1. There is a new Boolean option called filter_prepend_home for the redirect
1155 router.
1156
1157 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
1158 start of receiving a non-SMTP message, before any of the message has been
1159 read.
1160
1161 3. When an SMTP error message is specified in a "message" modifier in an ACL,
1162 or in a :fail: or :defer: message in a redirect router, Exim now checks the
1163 start of the message for an SMTP error code.
1164
1165 4. There is a new parameter for LDAP lookups called "referrals", which takes
1166 one of the settings "follow" (the default) or "nofollow".
1167
1168 5. Version 20070721.2 of exipick now included, offering these new options:
1169 --reverse
1170 After all other sorting options have bee processed, reverse order
1171 before displaying messages (-R is synonym).
1172 --random
1173 Randomize order of matching messages before displaying.
1174 --size
1175 Instead of displaying the matching messages, display the sum
1176 of their sizes.
1177 --sort <variable>[,<variable>...]
1178 Before displaying matching messages, sort the messages according to
1179 each messages value for each variable.
1180 --not
1181 Negate the value for every test (returns inverse output from the
1182 same criteria without --not).
1183
1184
1185 Version 4.62
1186 ------------
1187
1188 1. The ${readsocket expansion item now supports Internet domain sockets as well
1189 as Unix domain sockets. If the first argument begins "inet:", it must be of
1190 the form "inet:host:port". The port is mandatory; it may be a number or the
1191 name of a TCP port in /etc/services. The host may be a name, or it may be an
1192 IP address. An ip address may optionally be enclosed in square brackets.
1193 This is best for IPv6 addresses. For example:
1194
1195 ${readsocket{inet:[::1]:1234}{<request data>}...
1196
1197 Only a single host name may be given, but if looking it up yield more than
1198 one IP address, they are each tried in turn until a connection is made. Once
1199 a connection has been made, the behaviour is as for ${readsocket with a Unix
1200 domain socket.
1201
1202 2. If a redirect router sets up file or pipe deliveries for more than one
1203 incoming address, and the relevant transport has batch_max set greater than
1204 one, a batch delivery now occurs.
1205
1206 3. The appendfile transport has a new option called maildirfolder_create_regex.
1207 Its value is a regular expression. For a maildir delivery, this is matched
1208 against the maildir directory; if it matches, Exim ensures that a
1209 maildirfolder file is created alongside the new, cur, and tmp directories.
1210
1211
1212 Version 4.61
1213 ------------
1214
1215 The documentation is up-to-date for the 4.61 release. Major new features since
1216 the 4.60 release are:
1217
1218 . An option called disable_ipv6, to disable the use of IPv6 completely.
1219
1220 . An increase in the number of ACL variables to 20 of each type.
1221
1222 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
1223 $2, $3, (though those are still set) because the numeric variables get used
1224 for other things in complicated expansions.
1225
1226 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
1227
1228 . It is possible to use setclassresources() on some BSD OS to control the
1229 resources used in pipe deliveries.
1230
1231 . A new ACL modifier called add_header, which can be used with any verb.
1232
1233 . More errors are detectable in retry rules.
1234
1235 There are a number of other additions too.
1236
1237
1238 Version 4.60
1239 ------------
1240
1241 The documentation is up-to-date for the 4.60 release. Major new features since
1242 the 4.50 release are:
1243
1244 . Support for SQLite.
1245
1246 . Support for IGNOREQUOTA in LMTP.
1247
1248 . Extensions to the "submission mode" features.
1249
1250 . Support for Client SMTP Authorization (CSA).
1251
1252 . Support for ratelimiting hosts and users.
1253
1254 . New expansion items to help with the BATV "prvs" scheme.
1255
1256 . A "match_ip" condition, that matches an IP address against a list.
1257
1258 There are many more minor changes.
1259
1260 ****