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.
16 1. New command-line option -bI:sieve will list all supported sieve extensions
17 of this Exim build on standard output, one per line.
18 ManageSieve (RFC 5804) providers managing scripts for use by Exim should
19 query this to establish the correct list to include in the protocol's
20 SIEVE capability line.
22 2. If the -n option is combined with the -bP option, then the name of an
23 emitted option is not output, only the value (if visible to you).
24 For instance, "exim -n -bP pid_file_path" should just emit a pathname
25 followed by a newline, and no other text.
27 3. When built with SUPPORT_TLS and USE_GNUTLS, the SMTP transport driver now
28 has a "tls_dh_min_bits" option, to set the minimum acceptable number of
29 bits in the Diffie-Hellman prime offered by a server (in DH ciphersuites)
30 acceptable for security. (Option accepted but ignored if using OpenSSL).
31 Defaults to 1024, the old value. May be lowered only to 512, or raised as
32 far as you like. Raising this may hinder TLS interoperability with other
33 sites and is not currently recommended. Lowering this will permit you to
34 establish a TLS session which is not as secure as you might like.
36 Unless you really know what you are doing, leave it alone.
38 4. If not built with DISABLE_DNSSEC, Exim now has the main option
39 dns_dnssec_ok; if set to 1 then Exim will initialise the resolver library
40 to send the DO flag to your recursive resolver. If you have a recursive
41 resolver, which can set the Authenticated Data (AD) flag in results, Exim
42 can now detect this. Exim does not perform validation itself, instead
43 relying upon a trusted path to the resolver.
45 Current status: work-in-progress; $sender_host_dnssec variable added.
47 5. DSCP support for outbound connections: on a transport using the smtp driver,
48 set "dscp = ef", for instance, to cause the connections to have the relevant
49 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header.
51 Similarly for inbound connections, there is a new control modifier, dscp,
52 so "warn control = dscp/ef" in the connect ACL, or after authentication.
54 Supported values depend upon system libraries. "exim -bI:dscp" to list the
55 ones Exim knows of. You can also set a raw number 0..0x3F.
57 6. The -G command-line flag is no longer ignored; it is now equivalent to an
58 ACL setting "control = suppress_local_fixups". The -L command-line flag
59 is now accepted and forces use of syslog, with the provided tag as the
60 process name. A few other flags used by Sendmail are now accepted and
63 7. New cutthrough routing feature. Requested by a "control = cutthrough_delivery"
64 ACL modifier; works for single-recipient mails which are recieved on and
65 deliverable via SMTP. Using the connection made for a recipient verify,
66 if requested before the verify, or a new one made for the purpose while
67 the inbound connection is still active. The bulk of the mail item is copied
68 direct from the inbound socket to the outbound (as well as the spool file).
69 When the source notifies the end of data, the data acceptance by the destination
70 is negociated before the acceptance is sent to the source. If the destination
71 does not accept the mail item, for example due to content-scanning, the item
72 is not accepted from the source and therefore there is no need to generate
73 a bounce mail. This is of benefit when providing a secondary-MX service.
74 The downside is that delays are under the control of the ultimate destination
77 The Recieved-by: header on items delivered by cutthrough is generated
78 early in reception rather than at the end; this will affect any timestamp
79 included. The log line showing delivery is recorded before that showing
80 reception; it uses a new ">>" tag instead of "=>".
82 To support the feature, verify-callout connections can now use ESMTP and TLS.
83 The usual smtp transport options are honoured, plus a (new, default everything)
84 hosts_verify_avoid_tls.
86 New variable families named tls_in_cipher, tls_out_cipher etc. are introduced
87 for specific access to the information for each connection. The old names
88 are present for now but deprecated.
90 Not yet supported: IGNOREQUOTA, SIZE, PIPELINING.
92 8. New expansion operators ${listnamed:name} to get the content of a named list
93 and ${listcount:string} to count the items in a list.
95 9. New global option "gnutls_allow_auto_pkcs11", defaults false. The GnuTLS
96 rewrite in 4.80 combines with GnuTLS 2.12.0 or later, to autoload PKCS11
97 modules. For some situations this is desirable, but we expect admin in
98 those situations to know they want the feature. More commonly, it means
99 that GUI user modules get loaded and are broken by the setuid Exim being
100 unable to access files specified in environment variables and passed
101 through, thus breakage. So we explicitly inhibit the PKCS11 initialisation
102 unless this new option is set.
104 Some older OS's with earlier versions of GnuTLS might not have pkcs11 ability,
105 so have also added a build option which can be used to build Exim with GnuTLS
106 but without trying to use any kind of PKCS11 support. Uncomment this in the
109 AVOID_GNUTLS_PKCS11=yes
111 10. The "acl = name" condition on an ACL now supports optional arguments.
112 New expansion item "${acl {name}{arg}...}" and expansion condition
113 "acl {{name}{arg}...}" are added. In all cases up to nine arguments
114 can be used, appearing in $acl_arg1 to $acl_arg9 for the called ACL.
115 Variable $acl_narg contains the number of arguments. If the ACL sets
116 a "message =" value this becomes the result of the expansion item,
117 or the value of $value for the expansion condition. If the ACL returns
118 accept the expansion condition is true; if reject, false. A defer
119 return results in a forced fail.
121 11. Routers and transports can now have multiple headers_add and headers_remove
122 option lines. The concatenated list is used.
124 12. New ACL modifier "remove_header" can remove headers before message gets
125 handled by routers/transports.
127 13. New dnsdb lookup pseudo-type "a+". A sequence of "a6" (if configured),
128 "aaaa" and "a" lookups is done and the full set of results returned.
130 14. New expansion variable $headers_added with content from ACL add_header
131 modifier (but not yet added to messsage).
133 15. New 8bitmime status logging option for received messages. Log field "M8S".
135 16. New authenticated_sender logging option, adding to log field "A".
137 17. New expansion variables $router_name and $transport_name. Useful
138 particularly for debug_print as -bt commandline option does not
139 require privilege whereas -d does.
141 18. If built with EXPERIMENTAL_PRDR, per-recipient data responses per a
142 proposed extension to SMTP from Eric Hall.
144 19. The pipe transport has gained the force_command option, to allow
145 decorating commands from user .forward pipe aliases with prefix
146 wrappers, for instance.
148 20. Callout connections can now AUTH; the same controls as normal delivery
151 21. Support for DMARC, using opendmarc libs, can be enabled. It adds new
152 options: dmarc_forensic_sender, dmarc_history_file, and dmarc_tld_file.
153 It adds new expansion variables $dmarc_ar_header, $dmarc_status,
154 $dmarc_status_text, and $dmarc_used_domain. It adds a new acl modifier
155 dmarc_status. It adds new control flags dmarc_disable_verify and
156 dmarc_enable_forensic.
158 22. Add expansion variable $authenticated_fail_id, which is the username
159 provided to the authentication method which failed. It is available
160 for use in subsequent ACL processing (typically quit or notquit ACLs).
162 23. New ACL modifer "udpsend" can construct a UDP packet to send to a given
165 24. New ${hexquote:..string..} expansion operator converts non-printable
166 characters in the string to \xNN form.
168 25. Experimental TPDA (Transport Post Delivery Action) function added.
169 Patch provided by Axel Rau.
171 26. Experimental Redis lookup added. Patch provided by Warren Baker.
177 1. New authenticator driver, "gsasl". Server-only (at present).
178 This is a SASL interface, licensed under GPL, which can be found at
179 http://www.gnu.org/software/gsasl/.
180 This system does not provide sources of data for authentication, so
181 careful use needs to be made of the conditions in Exim.
183 2. New authenticator driver, "heimdal_gssapi". Server-only.
184 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
185 is no longer honoured for setuid programs by Heimdal. Use the
186 "server_keytab" option to point to the keytab.
188 3. The "pkg-config" system can now be used when building Exim to reference
189 cflags and library information for lookups and authenticators, rather
190 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
191 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
192 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
194 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
195 find the headers and libraries for PCRE.
197 4. New expansion variable $tls_bits.
199 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
200 be joined together with ASCII NUL characters to construct the key to pass
201 into the DBM library. Can be used with gsasl to access sasldb2 files as
204 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
206 Avoid release 1.0.1a if you can. Note that the default value of
207 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
208 increased susceptibility to attack. This may still have interoperability
209 implications for very old clients (see version 4.31 change 37) but
210 administrators can choose to make the trade-off themselves and restore
211 compatibility at the cost of session security.
213 7. Use of the new expansion variable $tls_sni in the main configuration option
214 tls_certificate will cause Exim to re-expand the option, if the client
215 sends the TLS Server Name Indication extension, to permit choosing a
216 different certificate; tls_privatekey will also be re-expanded. You must
217 still set these options to expand to valid files when $tls_sni is not set.
219 The SMTP Transport has gained the option tls_sni, which will set a hostname
220 for outbound TLS sessions, and set $tls_sni too.
222 A new log_selector, +tls_sni, has been added, to log received SNI values
223 for Exim as a server.
225 8. The existing "accept_8bitmime" option now defaults to true. This means
226 that Exim is deliberately not strictly RFC compliant. We're following
227 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
228 Those who disagree, or know that they are talking to mail servers that,
229 even today, are not 8-bit clean, need to turn off this option.
231 9. Exim can now be started with -bw (with an optional timeout, given as
232 -bw<timespec>). With this, stdin at startup is a socket that is
233 already listening for connections. This has a more modern name of
234 "socket activation", but forcing the activated socket to fd 0. We're
235 interested in adding more support for modern variants.
237 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
238 for numbers indicates multiplication by 1024^3.
240 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
241 gnutls_require_mac & gnutls_require_protocols are no longer supported.
242 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
243 string, documentation for which is at:
244 http://www.gnutls.org/manual/html_node/Priority-Strings.html
246 SNI support has been added to Exim's GnuTLS integration too.
248 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
249 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
251 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
252 is now available. If the contents of the file are valid, then Exim will
253 send that back in response to a TLS status request; this is OCSP Stapling.
254 Exim will not maintain the contents of the file in any way: administrators
255 are responsible for ensuring that it is up-to-date.
257 See "experimental-spec.txt" for more details.
259 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
260 identically to TXT record lookups.
262 14. New expansion variable $tod_epoch_l for higher-precision time.
264 15. New global option tls_dh_max_bits, defaulting to current value of NSS
265 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
266 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
268 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
269 Option can now be a path or an identifier for a standard prime.
270 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
271 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
274 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
275 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
276 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
282 1. New options for the ratelimit ACL condition: /count= and /unique=.
283 The /noupdate option has been replaced by a /readonly option.
285 2. The SMTP transport's protocol option may now be set to "smtps", to
286 use SSL-on-connect outbound.
288 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
289 there is a problem talking to the AV scanner, or the AV scanner running.
291 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
292 and check if the search item is a member of the list. This does not
293 support named lists, but does subject the list part to string expansion.
295 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
296 built, Exim no longer performs string expansion on the second string of
297 the match_* expansion conditions: "match_address", "match_domain",
298 "match_ip" & "match_local_part". Named lists can still be used.
304 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
305 or off in the resolver library.
311 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
312 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
313 libraries. The following global options have been added in support of
314 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
315 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
317 2. The pipe transport now takes a boolean option, "freeze_signal", default
318 false. When true, if the external delivery command exits on a signal then
319 Exim will freeze the message in the queue, instead of generating a bounce.
321 3. Log filenames may now use %M as an escape, instead of %D (still available).
322 The %M pattern expands to yyyymm, providing month-level resolution.
324 4. The $message_linecount variable is now updated for the maildir_tag option,
325 in the same way as $message_size, to reflect the real number of lines,
326 including any header additions or removals from transport.
328 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
329 Exim now selects entries randomly, to better scale in a cluster setup.
335 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
336 the flaw permitted the Exim run-time user to cause root to append to
337 arbitrary files of the attacker's choosing, with the content based
338 on content supplied by the attacker.
340 2. Exim now supports loading some lookup types at run-time, using your
341 platform's dlopen() functionality. This has limited platform support
342 and the intention is not to support every variant, it's limited to
343 dlopen(). This permits the main Exim binary to not be linked against
344 all the libraries needed for all the lookup types.
350 NOTE: this version is not guaranteed backwards-compatible, please read the
351 items below carefully
353 1. A new main configuration option, "openssl_options", is available if Exim
354 is built with SSL support provided by OpenSSL. The option allows
355 administrators to specify OpenSSL options to be used on connections;
356 typically this is to set bug compatibility features which the OpenSSL
357 developers have not enabled by default. There may be security
358 consequences for certain options, so these should not be changed
361 2. A new pipe transport option, "permit_coredumps", may help with problem
362 diagnosis in some scenarios. Note that Exim is typically installed as
363 a setuid binary, which on most OSes will inhibit coredumps by default,
364 so that safety mechanism would have to be overridden for this option to
365 be able to take effect.
367 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
368 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
369 Note that this switches Exim to use a new API ("INSTREAM") and a future
370 release of ClamAV will remove support for the old API ("STREAM").
372 The av_scanner option, when set to "clamd", now takes an optional third
373 part, "local", which causes Exim to pass a filename to ClamAV instead of
374 the file content. This is the same behaviour as when clamd is pointed at
375 a Unix-domain socket. For example:
377 av_scanner = clamd:192.0.2.3 1234:local
379 ClamAV's ExtendedDetectionInfo response format is now handled.
381 4. There is now a -bmalware option, restricted to admin users. This option
382 takes one parameter, a filename, and scans that file with Exim's
383 malware-scanning framework. This is intended purely as a debugging aid
384 to ensure that Exim's scanning is working, not to replace other tools.
385 Note that the ACL framework is not invoked, so if av_scanner references
386 ACL variables without a fallback then this will fail.
388 5. There is a new expansion operator, "reverse_ip", which will reverse IP
389 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
391 ${reverse_ip:192.0.2.4}
393 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
394 -> 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
396 6. There is a new ACL control called "debug", to enable debug logging.
397 This allows selective logging of certain incoming transactions within
398 production environments, with some care. It takes two options, "tag"
399 and "opts"; "tag" is included in the filename of the log and "opts"
400 is used as per the -d<options> command-line option. Examples, which
401 don't all make sense in all contexts:
404 control = debug/tag=.$sender_host_address
405 control = debug/opts=+expand+acl
406 control = debug/tag=.$message_exim_id/opts=+expand
408 7. It has always been implicit in the design and the documentation that
409 "the Exim user" is not root. src/EDITME said that using root was
410 "very strongly discouraged". This is not enough to keep people from
411 shooting themselves in the foot in days when many don't configure Exim
412 themselves but via package build managers. The security consequences of
413 running various bits of network code are severe if there should be bugs in
414 them. As such, the Exim user may no longer be root. If configured
415 statically, Exim will refuse to build. If configured as ref:user then Exim
416 will exit shortly after start-up. If you must shoot yourself in the foot,
417 then henceforth you will have to maintain your own local patches to strip
420 8. There is a new expansion condition, bool_lax{}. Where bool{} uses the ACL
421 condition logic to determine truth/failure and will fail to expand many
422 strings, bool_lax{} uses the router condition logic, where most strings
424 Note: bool{00} is false, bool_lax{00} is true.
426 9. Routers now support multiple "condition" tests.
428 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
429 Setting this allows an admin to define which entry in the tcpwrappers
430 config file will be used to control access to the daemon. This option
431 is only available when Exim is built with USE_TCP_WRAPPERS. The
432 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
435 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
436 the Exim run-time user, instead of root.
438 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
439 is forced on. This is mitigated by the new build option
440 TRUSTED_CONFIG_LIST which defines a list of configuration files which
441 are trusted; one per line. If a config file is owned by root and matches
442 a pathname in the list, then it may be invoked by the Exim build-time
443 user without Exim relinquishing root privileges.
445 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
446 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
447 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
448 include the main config. As a transition mechanism, we are temporarily
449 providing a work-around: the new build option WHITELIST_D_MACROS provides
450 a colon-separated list of macro names which may be overridden by the Exim
451 run-time user. The values of these macros are constrained to the regex
452 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
458 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
459 writable, the other to locking of MBX folders (not mbox).
461 2. MySQL stored procedures are now supported.
463 3. The dkim_domain transport option is now a list, not a single string, and
464 messages will be signed for each element in the list (discarding
467 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
468 in the presence of multiple character strings within the RR. Prior to 4.70,
469 only the first string would be returned. The dnsdb lookup now, by default,
470 preserves the pre-4.70 semantics, but also now takes an extended output
471 separator specification. The separator can be followed by a semicolon, to
472 concatenate the individual text strings together with no join character,
473 or by a comma and a second separator character, in which case the text
474 strings within a TXT record are joined on that second character.
475 Administrators are reminded that DNS provides no ordering guarantees
476 between multiple records in an RRset. For example:
478 foo.example. IN TXT "a" "b" "c"
479 foo.example. IN TXT "d" "e" "f"
481 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
482 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
483 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
489 1. Native DKIM support without an external library.
490 (Note that if no action to prevent it is taken, a straight upgrade will
491 result in DKIM verification of all signed incoming emails. See spec
492 for details on conditionally disabling)
494 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
496 3. There is now a bool{} expansion condition which maps certain strings to
497 true/false condition values (most likely of use in conjunction with the
498 and{} expansion operator).
500 4. The $spam_score, $spam_bar and $spam_report variables are now available
503 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
504 options, provided that Exim is invoked by an admin_user.
506 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
507 which increases compatibility with older clients at the cost of decreased
508 security. Don't set this unless you need to support such clients.
510 7. There is a new expansion operator, ${randint:...} which will produce a
511 "random" number less than the supplied integer. This randomness is
512 not guaranteed to be cryptographically strong, but depending upon how
513 Exim was built may be better than the most naive schemes.
515 8. Exim now explicitly ensures that SHA256 is available when linked against
518 9. The transport_filter_timeout option now applies to SMTP transports too.
524 1. Preliminary DKIM support in Experimental.
530 1. The body_linecount and body_zerocount C variables are now exported in the
533 2. When a dnslists lookup succeeds, the key that was looked up is now placed
534 in $dnslist_matched. When the key is an IP address, it is not reversed in
535 this variable (though it is, of course, in the actual lookup). In simple
538 deny dnslists = spamhaus.example
540 the key is also available in another variable (in this case,
541 $sender_host_address). In more complicated cases, however, this is not
542 true. For example, using a data lookup might generate a dnslists lookup
545 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
547 If this condition succeeds, the value in $dnslist_matched might be
548 192.168.6.7 (for example).
550 3. Authenticators now have a client_condition option. When Exim is running as
551 a client, it skips an authenticator whose client_condition expansion yields
552 "0", "no", or "false". This can be used, for example, to skip plain text
553 authenticators when the connection is not encrypted by a setting such as:
555 client_condition = ${if !eq{$tls_cipher}{}}
557 Note that the 4.67 documentation states that $tls_cipher contains the
558 cipher used for incoming messages. In fact, during SMTP delivery, it
559 contains the cipher used for the delivery. The same is true for
562 4. There is now a -Mvc <message-id> option, which outputs a copy of the
563 message to the standard output, in RFC 2822 format. The option can be used
564 only by an admin user.
566 5. There is now a /noupdate option for the ratelimit ACL condition. It
567 computes the rate and checks the limit as normal, but it does not update
568 the saved data. This means that, in relevant ACLs, it is possible to lookup
569 the existence of a specified (or auto-generated) ratelimit key without
570 incrementing the ratelimit counter for that key.
572 In order for this to be useful, another ACL entry must set the rate
573 for the same key somewhere (otherwise it will always be zero).
578 # Read the rate; if it doesn't exist or is below the maximum
580 deny ratelimit = 100 / 5m / strict / noupdate
581 log_message = RATE: $sender_rate / $sender_rate_period \
582 (max $sender_rate_limit)
584 [... some other logic and tests...]
586 warn ratelimit = 100 / 5m / strict / per_cmd
587 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
588 (max $sender_rate_limit)
589 condition = ${if le{$sender_rate}{$sender_rate_limit}}
593 6. The variable $max_received_linelength contains the number of bytes in the
594 longest line that was received as part of the message, not counting the
595 line termination character(s).
597 7. Host lists can now include +ignore_defer and +include_defer, analagous to
598 +ignore_unknown and +include_unknown. These options should be used with
599 care, probably only in non-critical host lists such as whitelists.
601 8. There's a new option called queue_only_load_latch, which defaults true.
602 If set false when queue_only_load is greater than zero, Exim re-evaluates
603 the load for each incoming message in an SMTP session. Otherwise, once one
604 message is queued, the remainder are also.
606 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
607 cases when an SMTP session ends without sending QUIT. However, when Exim
608 itself is is bad trouble, such as being unable to write to its log files,
609 this ACL is not run, because it might try to do things (such as write to
610 log files) that make the situation even worse.
612 Like the QUIT ACL, this new ACL is provided to make it possible to gather
613 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
614 modifier is forbidden in this ACL.
616 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
617 to a string that indicates the reason for the termination of the SMTP
618 connection. The possible values are:
620 acl-drop Another ACL issued a "drop" command
621 bad-commands Too many unknown or non-mail commands
622 command-timeout Timeout while reading SMTP commands
623 connection-lost The SMTP connection has been lost
624 data-timeout Timeout while reading message data
625 local-scan-error The local_scan() function crashed
626 local-scan-timeout The local_scan() function timed out
627 signal-exit SIGTERM or SIGINT
628 synchronization-error SMTP synchronization error
629 tls-failed TLS failed to start
631 In most cases when an SMTP connection is closed without having received
632 QUIT, Exim sends an SMTP response message before actually closing the
633 connection. With the exception of acl-drop, the default message can be
634 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
635 "drop" verb in another ACL, it is the message from the other ACL that is
638 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
639 servers with individual queries. This is done by starting the query with
640 "servers=x:y:z;", where each item in the list may take one of two forms:
642 (1) If it is just a host name, the appropriate global option (mysql_servers
643 or pgsql_servers) is searched for a host of the same name, and the
644 remaining parameters (database, user, password) are taken from there.
646 (2) If it contains any slashes, it is taken as a complete parameter set.
648 The list of servers is used in exactly the same was as the global list.
649 Once a connection to a server has happened and a query has been
650 successfully executed, processing of the lookup ceases.
652 This feature is intended for use in master/slave situations where updates
653 are occurring, and one wants to update a master rather than a slave. If the
654 masters are in the list for reading, you might have:
656 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
658 In an updating lookup, you could then write
660 ${lookup mysql{servers=master; UPDATE ...}
662 If, on the other hand, the master is not to be used for reading lookups:
664 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
666 you can still update the master by
668 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
670 11. The message_body_newlines option (default FALSE, for backwards
671 compatibility) can be used to control whether newlines are present in
672 $message_body and $message_body_end. If it is FALSE, they are replaced by
679 1. There is a new log selector called smtp_no_mail, which is not included in
680 the default setting. When it is set, a line is written to the main log
681 whenever an accepted SMTP connection terminates without having issued a
684 2. When an item in a dnslists list is followed by = and & and a list of IP
685 addresses, the behaviour was not clear when the lookup returned more than
686 one IP address. This has been solved by the addition of == and =& for "all"
687 rather than the default "any" matching.
689 3. Up till now, the only control over which cipher suites GnuTLS uses has been
690 for the cipher algorithms. New options have been added to allow some of the
691 other parameters to be varied.
693 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
694 set, Exim compiles a runtime option called disable_fsync.
696 5. There is a new variable called $smtp_count_at_connection_start.
698 6. There's a new control called no_pipelining.
700 7. There are two new variables called $sending_ip_address and $sending_port.
701 These are set whenever an SMTP connection to another host has been set up.
703 8. The expansion of the helo_data option in the smtp transport now happens
704 after the connection to the server has been made.
706 9. There is a new expansion operator ${rfc2047d: that decodes strings that
707 are encoded as per RFC 2047.
709 10. There is a new log selector called "pid", which causes the current process
710 id to be added to every log line, in square brackets, immediately after the
713 11. Exim has been modified so that it flushes SMTP output before implementing
714 a delay in an ACL. It also flushes the output before performing a callout,
715 as this can take a substantial time. These behaviours can be disabled by
716 obeying control = no_delay_flush or control = no_callout_flush,
717 respectively, at some earlier stage of the connection.
719 12. There are two new expansion conditions that iterate over a list. They are
720 called forany and forall.
722 13. There's a new global option called dsn_from that can be used to vary the
723 contents of From: lines in bounces and other automatically generated
724 messages ("delivery status notifications" - hence the name of the option).
726 14. The smtp transport has a new option called hosts_avoid_pipelining.
728 15. By default, exigrep does case-insensitive matches. There is now a -I option
729 that makes it case-sensitive.
731 16. A number of new features ("addresses", "map", "filter", and "reduce") have
732 been added to string expansions to make it easier to process lists of
733 items, typically addresses.
735 17. There's a new ACL modifier called "continue". It does nothing of itself,
736 and processing of the ACL always continues with the next condition or
737 modifier. It is provided so that the side effects of expanding its argument
740 18. It is now possible to use newline and other control characters (those with
741 values less than 32, plus DEL) as separators in lists.
743 19. The exigrep utility now has a -v option, which inverts the matching
746 20. The host_find_failed option in the manualroute router can now be set to
753 No new features were added to 4.66.
759 No new features were added to 4.65.
765 1. ACL variables can now be given arbitrary names, as long as they start with
766 "acl_c" or "acl_m" (for connection variables and message variables), are at
767 least six characters long, with the sixth character being either a digit or
770 2. There is a new ACL modifier called log_reject_target. It makes it possible
771 to specify which logs are used for messages about ACL rejections.
773 3. There is a new authenticator called "dovecot". This is an interface to the
774 authentication facility of the Dovecot POP/IMAP server, which can support a
775 number of authentication methods.
777 4. The variable $message_headers_raw provides a concatenation of all the
778 messages's headers without any decoding. This is in contrast to
779 $message_headers, which does RFC2047 decoding on the header contents.
781 5. In a DNS black list, if two domain names, comma-separated, are given, the
782 second is used first to do an initial check, making use of any IP value
783 restrictions that are set. If there is a match, the first domain is used,
784 without any IP value restrictions, to get the TXT record.
786 6. All authenticators now have a server_condition option.
788 7. There is a new command-line option called -Mset. It is useful only in
789 conjunction with -be (that is, when testing string expansions). It must be
790 followed by a message id; Exim loads the given message from its spool
791 before doing the expansions.
793 8. Another similar new command-line option is called -bem. It operates like
794 -be except that it must be followed by the name of a file that contains a
797 9. When an address is delayed because of a 4xx response to a RCPT command, it
798 is now the combination of sender and recipient that is delayed in
799 subsequent queue runs until its retry time is reached.
801 10. Unary negation and the bitwise logical operators and, or, xor, not, and
802 shift, have been added to the eval: and eval10: expansion items.
804 11. The variables $interface_address and $interface_port have been renamed
805 as $received_ip_address and $received_port, to make it clear that they
806 relate to message reception rather than delivery. (The old names remain
807 available for compatibility.)
809 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
810 to vary the message that is sent when an SMTP command is accepted.
816 1. There is a new Boolean option called filter_prepend_home for the redirect
819 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
820 start of receiving a non-SMTP message, before any of the message has been
823 3. When an SMTP error message is specified in a "message" modifier in an ACL,
824 or in a :fail: or :defer: message in a redirect router, Exim now checks the
825 start of the message for an SMTP error code.
827 4. There is a new parameter for LDAP lookups called "referrals", which takes
828 one of the settings "follow" (the default) or "nofollow".
830 5. Version 20070721.2 of exipick now included, offering these new options:
832 After all other sorting options have bee processed, reverse order
833 before displaying messages (-R is synonym).
835 Randomize order of matching messages before displaying.
837 Instead of displaying the matching messages, display the sum
839 --sort <variable>[,<variable>...]
840 Before displaying matching messages, sort the messages according to
841 each messages value for each variable.
843 Negate the value for every test (returns inverse output from the
844 same criteria without --not).
850 1. The ${readsocket expansion item now supports Internet domain sockets as well
851 as Unix domain sockets. If the first argument begins "inet:", it must be of
852 the form "inet:host:port". The port is mandatory; it may be a number or the
853 name of a TCP port in /etc/services. The host may be a name, or it may be an
854 IP address. An ip address may optionally be enclosed in square brackets.
855 This is best for IPv6 addresses. For example:
857 ${readsocket{inet:[::1]:1234}{<request data>}...
859 Only a single host name may be given, but if looking it up yield more than
860 one IP address, they are each tried in turn until a connection is made. Once
861 a connection has been made, the behaviour is as for ${readsocket with a Unix
864 2. If a redirect router sets up file or pipe deliveries for more than one
865 incoming address, and the relevant transport has batch_max set greater than
866 one, a batch delivery now occurs.
868 3. The appendfile transport has a new option called maildirfolder_create_regex.
869 Its value is a regular expression. For a maildir delivery, this is matched
870 against the maildir directory; if it matches, Exim ensures that a
871 maildirfolder file is created alongside the new, cur, and tmp directories.
877 The documentation is up-to-date for the 4.61 release. Major new features since
878 the 4.60 release are:
880 . An option called disable_ipv6, to disable the use of IPv6 completely.
882 . An increase in the number of ACL variables to 20 of each type.
884 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
885 $2, $3, (though those are still set) because the numeric variables get used
886 for other things in complicated expansions.
888 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
890 . It is possible to use setclassresources() on some BSD OS to control the
891 resources used in pipe deliveries.
893 . A new ACL modifier called add_header, which can be used with any verb.
895 . More errors are detectable in retry rules.
897 There are a number of other additions too.
903 The documentation is up-to-date for the 4.60 release. Major new features since
904 the 4.50 release are:
906 . Support for SQLite.
908 . Support for IGNOREQUOTA in LMTP.
910 . Extensions to the "submission mode" features.
912 . Support for Client SMTP Authorization (CSA).
914 . Support for ratelimiting hosts and users.
916 . New expansion items to help with the BATV "prvs" scheme.
918 . A "match_ip" condition, that matches an IP address against a list.
920 There are many more minor changes.
git://git.exim.org / users / heiko / exim.git / blob