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