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