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