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