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