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_use_dnssec; 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
40 Current status: work-in-progress; $sender_host_dnssec variable added.
42 5. DSCP support for outbound connections: on a transport using the smtp driver,
43 set "dscp = ef", for instance, to cause the connections to have the relevant
44 DSCP (IPv4 TOS or IPv6 TCLASS) value in the header. Supported values depend
45 upon system libraries. "exim -bI:dscp" to list the ones Exim knows of.
46 You can also set a raw number 0..0x3F.
52 1. New authenticator driver, "gsasl". Server-only (at present).
53 This is a SASL interface, licensed under GPL, which can be found at
54 http://www.gnu.org/software/gsasl/.
55 This system does not provide sources of data for authentication, so
56 careful use needs to be made of the conditions in Exim.
58 2. New authenticator driver, "heimdal_gssapi". Server-only.
59 A replacement for using cyrus_sasl with Heimdal, now that $KRB5_KTNAME
60 is no longer honoured for setuid programs by Heimdal. Use the
61 "server_keytab" option to point to the keytab.
63 3. The "pkg-config" system can now be used when building Exim to reference
64 cflags and library information for lookups and authenticators, rather
65 than having to update "CFLAGS", "AUTH_LIBS", "LOOKUP_INCLUDE" and
66 "LOOKUP_LIBS" directly. Similarly for handling the TLS library support
67 without adjusting "TLS_INCLUDE" and "TLS_LIBS".
69 In addition, setting PCRE_CONFIG=yes will query the pcre-config tool to
70 find the headers and libraries for PCRE.
72 4. New expansion variable $tls_bits.
74 5. New lookup type, "dbmjz". Key is an Exim list, the elements of which will
75 be joined together with ASCII NUL characters to construct the key to pass
76 into the DBM library. Can be used with gsasl to access sasldb2 files as
79 6. OpenSSL now supports TLS1.1 and TLS1.2 with OpenSSL 1.0.1.
81 Avoid release 1.0.1a if you can. Note that the default value of
82 "openssl_options" is no longer "+dont_insert_empty_fragments", as that
83 increased susceptibility to attack. This may still have interoperability
84 implications for very old clients (see version 4.31 change 37) but
85 administrators can choose to make the trade-off themselves and restore
86 compatibility at the cost of session security.
88 7. Use of the new expansion variable $tls_sni in the main configuration option
89 tls_certificate will cause Exim to re-expand the option, if the client
90 sends the TLS Server Name Indication extension, to permit choosing a
91 different certificate; tls_privatekey will also be re-expanded. You must
92 still set these options to expand to valid files when $tls_sni is not set.
94 The SMTP Transport has gained the option tls_sni, which will set a hostname
95 for outbound TLS sessions, and set $tls_sni too.
97 A new log_selector, +tls_sni, has been added, to log received SNI values
100 8. The existing "accept_8bitmime" option now defaults to true. This means
101 that Exim is deliberately not strictly RFC compliant. We're following
102 Dan Bernstein's advice in http://cr.yp.to/smtp/8bitmime.html by default.
103 Those who disagree, or know that they are talking to mail servers that,
104 even today, are not 8-bit clean, need to turn off this option.
106 9. Exim can now be started with -bw (with an optional timeout, given as
107 -bw<timespec>). With this, stdin at startup is a socket that is
108 already listening for connections. This has a more modern name of
109 "socket activation", but forcing the activated socket to fd 0. We're
110 interested in adding more support for modern variants.
112 10. ${eval } now uses 64-bit values on supporting platforms. A new "G" suffix
113 for numbers indicates multiplication by 1024^3.
115 11. The GnuTLS support has been revamped; the three options gnutls_require_kx,
116 gnutls_require_mac & gnutls_require_protocols are no longer supported.
117 tls_require_ciphers is now parsed by gnutls_priority_init(3) as a priority
118 string, documentation for which is at:
119 http://www.gnu.org/software/gnutls/manual/html_node/Priority-Strings.html
121 SNI support has been added to Exim's GnuTLS integration too.
123 For sufficiently recent GnuTLS libraries, ${randint:..} will now use
124 gnutls_rnd(), asking for GNUTLS_RND_NONCE level randomness.
126 12. With OpenSSL, if built with EXPERIMENTAL_OCSP, a new option tls_ocsp_file
127 is now available. If the contents of the file are valid, then Exim will
128 send that back in response to a TLS status request; this is OCSP Stapling.
129 Exim will not maintain the contents of the file in any way: administrators
130 are responsible for ensuring that it is up-to-date.
132 See "experimental-spec.txt" for more details.
134 13. ${lookup dnsdb{ }} supports now SPF record types. They are handled
135 identically to TXT record lookups.
137 14. New expansion variable $tod_epoch_l for higher-precision time.
139 15. New global option tls_dh_max_bits, defaulting to current value of NSS
140 hard-coded limit of DH ephemeral bits, to fix interop problems caused by
141 GnuTLS 2.12 library recommending a bit count higher than NSS supports.
143 16. tls_dhparam now used by both OpenSSL and GnuTLS, can be path or identifier.
144 Option can now be a path or an identifier for a standard prime.
145 If unset, we use the DH prime from section 2.2 of RFC 5114, "ike23".
146 Set to "historic" to get the old GnuTLS behaviour of auto-generated DH
149 17. SSLv2 now disabled by default in OpenSSL. (Never supported by GnuTLS).
150 Use "openssl_options -no_sslv2" to re-enable support, if your OpenSSL
151 install was not built with OPENSSL_NO_SSL2 ("no-ssl2").
157 1. New options for the ratelimit ACL condition: /count= and /unique=.
158 The /noupdate option has been replaced by a /readonly option.
160 2. The SMTP transport's protocol option may now be set to "smtps", to
161 use SSL-on-connect outbound.
163 3. New variable $av_failed, set true if the AV scanner deferred; ie, when
164 there is a problem talking to the AV scanner, or the AV scanner running.
166 4. New expansion conditions, "inlist" and "inlisti", which take simple lists
167 and check if the search item is a member of the list. This does not
168 support named lists, but does subject the list part to string expansion.
170 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
171 built, Exim no longer performs string expansion on the second string of
172 the match_* expansion conditions: "match_address", "match_domain",
173 "match_ip" & "match_local_part". Named lists can still be used.
179 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on
180 or off in the resolver library.
186 1. In addition to the existing LDAP and LDAP/SSL ("ldaps") support, there
187 is now LDAP/TLS support, given sufficiently modern OpenLDAP client
188 libraries. The following global options have been added in support of
189 this: ldap_ca_cert_dir, ldap_ca_cert_file, ldap_cert_file, ldap_cert_key,
190 ldap_cipher_suite, ldap_require_cert, ldap_start_tls.
192 2. The pipe transport now takes a boolean option, "freeze_signal", default
193 false. When true, if the external delivery command exits on a signal then
194 Exim will freeze the message in the queue, instead of generating a bounce.
196 3. Log filenames may now use %M as an escape, instead of %D (still available).
197 The %M pattern expands to yyyymm, providing month-level resolution.
199 4. The $message_linecount variable is now updated for the maildir_tag option,
200 in the same way as $message_size, to reflect the real number of lines,
201 including any header additions or removals from transport.
203 5. When contacting a pool of SpamAssassin servers configured in spamd_address,
204 Exim now selects entries randomly, to better scale in a cluster setup.
210 1. SECURITY FIX: privilege escalation flaw fixed. On Linux (and only Linux)
211 the flaw permitted the Exim run-time user to cause root to append to
212 arbitrary files of the attacker's choosing, with the content based
213 on content supplied by the attacker.
215 2. Exim now supports loading some lookup types at run-time, using your
216 platform's dlopen() functionality. This has limited platform support
217 and the intention is not to support every variant, it's limited to
218 dlopen(). This permits the main Exim binary to not be linked against
219 all the libraries needed for all the lookup types.
225 NOTE: this version is not guaranteed backwards-compatible, please read the
226 items below carefully
228 1. A new main configuration option, "openssl_options", is available if Exim
229 is built with SSL support provided by OpenSSL. The option allows
230 administrators to specify OpenSSL options to be used on connections;
231 typically this is to set bug compatibility features which the OpenSSL
232 developers have not enabled by default. There may be security
233 consequences for certain options, so these should not be changed
236 2. A new pipe transport option, "permit_coredumps", may help with problem
237 diagnosis in some scenarios. Note that Exim is typically installed as
238 a setuid binary, which on most OSes will inhibit coredumps by default,
239 so that safety mechanism would have to be overridden for this option to
240 be able to take effect.
242 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless
243 Local/Makefile sets: WITH_OLD_CLAMAV_STREAM=yes
244 Note that this switches Exim to use a new API ("INSTREAM") and a future
245 release of ClamAV will remove support for the old API ("STREAM").
247 The av_scanner option, when set to "clamd", now takes an optional third
248 part, "local", which causes Exim to pass a filename to ClamAV instead of
249 the file content. This is the same behaviour as when clamd is pointed at
250 a Unix-domain socket. For example:
252 av_scanner = clamd:192.0.2.3 1234:local
254 ClamAV's ExtendedDetectionInfo response format is now handled.
256 4. There is now a -bmalware option, restricted to admin users. This option
257 takes one parameter, a filename, and scans that file with Exim's
258 malware-scanning framework. This is intended purely as a debugging aid
259 to ensure that Exim's scanning is working, not to replace other tools.
260 Note that the ACL framework is not invoked, so if av_scanner references
261 ACL variables without a fallback then this will fail.
263 5. There is a new expansion operator, "reverse_ip", which will reverse IP
264 addresses; IPv4 into dotted quad, IPv6 into dotted nibble. Examples:
266 ${reverse_ip:192.0.2.4}
268 ${reverse_ip:2001:0db8:c42:9:1:abcd:192.0.2.3}
269 -> 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
271 6. There is a new ACL control called "debug", to enable debug logging.
272 This allows selective logging of certain incoming transactions within
273 production environments, with some care. It takes two options, "tag"
274 and "opts"; "tag" is included in the filename of the log and "opts"
275 is used as per the -d<options> command-line option. Examples, which
276 don't all make sense in all contexts:
279 control = debug/tag=.$sender_host_address
280 control = debug/opts=+expand+acl
281 control = debug/tag=.$message_exim_id/opts=+expand
283 7. It has always been implicit in the design and the documentation that
284 "the Exim user" is not root. src/EDITME said that using root was
285 "very strongly discouraged". This is not enough to keep people from
286 shooting themselves in the foot in days when many don't configure Exim
287 themselves but via package build managers. The security consequences of
288 running various bits of network code are severe if there should be bugs in
289 them. As such, the Exim user may no longer be root. If configured
290 statically, Exim will refuse to build. If configured as ref:user then Exim
291 will exit shortly after start-up. If you must shoot yourself in the foot,
292 then henceforth you will have to maintain your own local patches to strip
295 8. There is a new expansion operator, bool_lax{}. Where bool{} uses the ACL
296 condition logic to determine truth/failure and will fail to expand many
297 strings, bool_lax{} uses the router condition logic, where most strings
299 Note: bool{00} is false, bool_lax{00} is true.
301 9. Routers now support multiple "condition" tests,
303 10. There is now a runtime configuration option "tcp_wrappers_daemon_name".
304 Setting this allows an admin to define which entry in the tcpwrappers
305 config file will be used to control access to the daemon. This option
306 is only available when Exim is built with USE_TCP_WRAPPERS. The
307 default value is set at build time using the TCP_WRAPPERS_DAEMON_NAME
310 11. [POSSIBLE CONFIG BREAKAGE] The default value for system_filter_user is now
311 the Exim run-time user, instead of root.
313 12. [POSSIBLE CONFIG BREAKAGE] ALT_CONFIG_ROOT_ONLY is no longer optional and
314 is forced on. This is mitigated by the new build option
315 TRUSTED_CONFIG_LIST which defines a list of configuration files which
316 are trusted; one per line. If a config file is owned by root and matches
317 a pathname in the list, then it may be invoked by the Exim build-time
318 user without Exim relinquishing root privileges.
320 13. [POSSIBLE CONFIG BREAKAGE] The Exim user is no longer automatically
321 trusted to supply -D<Macro[=Value]> overrides on the command-line. Going
322 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that
323 include the main config. As a transition mechanism, we are temporarily
324 providing a work-around: the new build option WHITELIST_D_MACROS provides
325 a colon-separated list of macro names which may be overridden by the Exim
326 run-time user. The values of these macros are constrained to the regex
327 ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).
333 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
334 writable, the other to locking of MBX folders (not mbox).
336 2. MySQL stored procedures are now supported.
338 3. The dkim_domain transport option is now a list, not a single string, and
339 messages will be signed for each element in the list (discarding
342 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
343 in the presence of multiple character strings within the RR. Prior to 4.70,
344 only the first string would be returned. The dnsdb lookup now, by default,
345 preserves the pre-4.70 semantics, but also now takes an extended output
346 separator specification. The separator can be followed by a semicolon, to
347 concatenate the individual text strings together with no join character,
348 or by a comma and a second separator character, in which case the text
349 strings within a TXT record are joined on that second character.
350 Administrators are reminded that DNS provides no ordering guarantees
351 between multiple records in an RRset. For example:
353 foo.example. IN TXT "a" "b" "c"
354 foo.example. IN TXT "d" "e" "f"
356 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
357 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
358 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
364 1. Native DKIM support without an external library.
365 (Note that if no action to prevent it is taken, a straight upgrade will
366 result in DKIM verification of all signed incoming emails. See spec
367 for details on conditionally disabling)
369 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
371 3. There is now a bool{} expansion condition which maps certain strings to
372 true/false condition values (most likely of use in conjunction with the
373 and{} expansion operator).
375 4. The $spam_score, $spam_bar and $spam_report variables are now available
378 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
379 options, provided that Exim is invoked by an admin_user.
381 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
382 which increases compatibility with older clients at the cost of decreased
383 security. Don't set this unless you need to support such clients.
385 7. There is a new expansion operator, ${randint:...} which will produce a
386 "random" number less than the supplied integer. This randomness is
387 not guaranteed to be cryptographically strong, but depending upon how
388 Exim was built may be better than the most naive schemes.
390 8. Exim now explicitly ensures that SHA256 is available when linked against
393 9. The transport_filter_timeout option now applies to SMTP transports too.
399 1. Preliminary DKIM support in Experimental.
405 1. The body_linecount and body_zerocount C variables are now exported in the
408 2. When a dnslists lookup succeeds, the key that was looked up is now placed
409 in $dnslist_matched. When the key is an IP address, it is not reversed in
410 this variable (though it is, of course, in the actual lookup). In simple
413 deny dnslists = spamhaus.example
415 the key is also available in another variable (in this case,
416 $sender_host_address). In more complicated cases, however, this is not
417 true. For example, using a data lookup might generate a dnslists lookup
420 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
422 If this condition succeeds, the value in $dnslist_matched might be
423 192.168.6.7 (for example).
425 3. Authenticators now have a client_condition option. When Exim is running as
426 a client, it skips an authenticator whose client_condition expansion yields
427 "0", "no", or "false". This can be used, for example, to skip plain text
428 authenticators when the connection is not encrypted by a setting such as:
430 client_condition = ${if !eq{$tls_cipher}{}}
432 Note that the 4.67 documentation states that $tls_cipher contains the
433 cipher used for incoming messages. In fact, during SMTP delivery, it
434 contains the cipher used for the delivery. The same is true for
437 4. There is now a -Mvc <message-id> option, which outputs a copy of the
438 message to the standard output, in RFC 2822 format. The option can be used
439 only by an admin user.
441 5. There is now a /noupdate option for the ratelimit ACL condition. It
442 computes the rate and checks the limit as normal, but it does not update
443 the saved data. This means that, in relevant ACLs, it is possible to lookup
444 the existence of a specified (or auto-generated) ratelimit key without
445 incrementing the ratelimit counter for that key.
447 In order for this to be useful, another ACL entry must set the rate
448 for the same key somewhere (otherwise it will always be zero).
453 # Read the rate; if it doesn't exist or is below the maximum
455 deny ratelimit = 100 / 5m / strict / noupdate
456 log_message = RATE: $sender_rate / $sender_rate_period \
457 (max $sender_rate_limit)
459 [... some other logic and tests...]
461 warn ratelimit = 100 / 5m / strict / per_cmd
462 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
463 (max $sender_rate_limit)
464 condition = ${if le{$sender_rate}{$sender_rate_limit}}
468 6. The variable $max_received_linelength contains the number of bytes in the
469 longest line that was received as part of the message, not counting the
470 line termination character(s).
472 7. Host lists can now include +ignore_defer and +include_defer, analagous to
473 +ignore_unknown and +include_unknown. These options should be used with
474 care, probably only in non-critical host lists such as whitelists.
476 8. There's a new option called queue_only_load_latch, which defaults true.
477 If set false when queue_only_load is greater than zero, Exim re-evaluates
478 the load for each incoming message in an SMTP session. Otherwise, once one
479 message is queued, the remainder are also.
481 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
482 cases when an SMTP session ends without sending QUIT. However, when Exim
483 itself is is bad trouble, such as being unable to write to its log files,
484 this ACL is not run, because it might try to do things (such as write to
485 log files) that make the situation even worse.
487 Like the QUIT ACL, this new ACL is provided to make it possible to gather
488 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
489 modifier is forbidden in this ACL.
491 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
492 to a string that indicates the reason for the termination of the SMTP
493 connection. The possible values are:
495 acl-drop Another ACL issued a "drop" command
496 bad-commands Too many unknown or non-mail commands
497 command-timeout Timeout while reading SMTP commands
498 connection-lost The SMTP connection has been lost
499 data-timeout Timeout while reading message data
500 local-scan-error The local_scan() function crashed
501 local-scan-timeout The local_scan() function timed out
502 signal-exit SIGTERM or SIGINT
503 synchronization-error SMTP synchronization error
504 tls-failed TLS failed to start
506 In most cases when an SMTP connection is closed without having received
507 QUIT, Exim sends an SMTP response message before actually closing the
508 connection. With the exception of acl-drop, the default message can be
509 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
510 "drop" verb in another ACL, it is the message from the other ACL that is
513 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
514 servers with individual queries. This is done by starting the query with
515 "servers=x:y:z;", where each item in the list may take one of two forms:
517 (1) If it is just a host name, the appropriate global option (mysql_servers
518 or pgsql_servers) is searched for a host of the same name, and the
519 remaining parameters (database, user, password) are taken from there.
521 (2) If it contains any slashes, it is taken as a complete parameter set.
523 The list of servers is used in exactly the same was as the global list.
524 Once a connection to a server has happened and a query has been
525 successfully executed, processing of the lookup ceases.
527 This feature is intended for use in master/slave situations where updates
528 are occurring, and one wants to update a master rather than a slave. If the
529 masters are in the list for reading, you might have:
531 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
533 In an updating lookup, you could then write
535 ${lookup mysql{servers=master; UPDATE ...}
537 If, on the other hand, the master is not to be used for reading lookups:
539 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
541 you can still update the master by
543 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
545 11. The message_body_newlines option (default FALSE, for backwards
546 compatibility) can be used to control whether newlines are present in
547 $message_body and $message_body_end. If it is FALSE, they are replaced by
554 1. There is a new log selector called smtp_no_mail, which is not included in
555 the default setting. When it is set, a line is written to the main log
556 whenever an accepted SMTP connection terminates without having issued a
559 2. When an item in a dnslists list is followed by = and & and a list of IP
560 addresses, the behaviour was not clear when the lookup returned more than
561 one IP address. This has been solved by the addition of == and =& for "all"
562 rather than the default "any" matching.
564 3. Up till now, the only control over which cipher suites GnuTLS uses has been
565 for the cipher algorithms. New options have been added to allow some of the
566 other parameters to be varied.
568 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
569 set, Exim compiles a runtime option called disable_fsync.
571 5. There is a new variable called $smtp_count_at_connection_start.
573 6. There's a new control called no_pipelining.
575 7. There are two new variables called $sending_ip_address and $sending_port.
576 These are set whenever an SMTP connection to another host has been set up.
578 8. The expansion of the helo_data option in the smtp transport now happens
579 after the connection to the server has been made.
581 9. There is a new expansion operator ${rfc2047d: that decodes strings that
582 are encoded as per RFC 2047.
584 10. There is a new log selector called "pid", which causes the current process
585 id to be added to every log line, in square brackets, immediately after the
588 11. Exim has been modified so that it flushes SMTP output before implementing
589 a delay in an ACL. It also flushes the output before performing a callout,
590 as this can take a substantial time. These behaviours can be disabled by
591 obeying control = no_delay_flush or control = no_callout_flush,
592 respectively, at some earlier stage of the connection.
594 12. There are two new expansion conditions that iterate over a list. They are
595 called forany and forall.
597 13. There's a new global option called dsn_from that can be used to vary the
598 contents of From: lines in bounces and other automatically generated
599 messages ("delivery status notifications" - hence the name of the option).
601 14. The smtp transport has a new option called hosts_avoid_pipelining.
603 15. By default, exigrep does case-insensitive matches. There is now a -I option
604 that makes it case-sensitive.
606 16. A number of new features ("addresses", "map", "filter", and "reduce") have
607 been added to string expansions to make it easier to process lists of
608 items, typically addresses.
610 17. There's a new ACL modifier called "continue". It does nothing of itself,
611 and processing of the ACL always continues with the next condition or
612 modifier. It is provided so that the side effects of expanding its argument
615 18. It is now possible to use newline and other control characters (those with
616 values less than 32, plus DEL) as separators in lists.
618 19. The exigrep utility now has a -v option, which inverts the matching
621 20. The host_find_failed option in the manualroute router can now be set to
628 No new features were added to 4.66.
634 No new features were added to 4.65.
640 1. ACL variables can now be given arbitrary names, as long as they start with
641 "acl_c" or "acl_m" (for connection variables and message variables), are at
642 least six characters long, with the sixth character being either a digit or
645 2. There is a new ACL modifier called log_reject_target. It makes it possible
646 to specify which logs are used for messages about ACL rejections.
648 3. There is a new authenticator called "dovecot". This is an interface to the
649 authentication facility of the Dovecot POP/IMAP server, which can support a
650 number of authentication methods.
652 4. The variable $message_headers_raw provides a concatenation of all the
653 messages's headers without any decoding. This is in contrast to
654 $message_headers, which does RFC2047 decoding on the header contents.
656 5. In a DNS black list, if two domain names, comma-separated, are given, the
657 second is used first to do an initial check, making use of any IP value
658 restrictions that are set. If there is a match, the first domain is used,
659 without any IP value restrictions, to get the TXT record.
661 6. All authenticators now have a server_condition option.
663 7. There is a new command-line option called -Mset. It is useful only in
664 conjunction with -be (that is, when testing string expansions). It must be
665 followed by a message id; Exim loads the given message from its spool
666 before doing the expansions.
668 8. Another similar new command-line option is called -bem. It operates like
669 -be except that it must be followed by the name of a file that contains a
672 9. When an address is delayed because of a 4xx response to a RCPT command, it
673 is now the combination of sender and recipient that is delayed in
674 subsequent queue runs until its retry time is reached.
676 10. Unary negation and the bitwise logical operators and, or, xor, not, and
677 shift, have been added to the eval: and eval10: expansion items.
679 11. The variables $interface_address and $interface_port have been renamed
680 as $received_ip_address and $received_port, to make it clear that they
681 relate to message reception rather than delivery. (The old names remain
682 available for compatibility.)
684 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
685 to vary the message that is sent when an SMTP command is accepted.
691 1. There is a new Boolean option called filter_prepend_home for the redirect
694 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
695 start of receiving a non-SMTP message, before any of the message has been
698 3. When an SMTP error message is specified in a "message" modifier in an ACL,
699 or in a :fail: or :defer: message in a redirect router, Exim now checks the
700 start of the message for an SMTP error code.
702 4. There is a new parameter for LDAP lookups called "referrals", which takes
703 one of the settings "follow" (the default) or "nofollow".
705 5. Version 20070721.2 of exipick now included, offering these new options:
707 After all other sorting options have bee processed, reverse order
708 before displaying messages (-R is synonym).
710 Randomize order of matching messages before displaying.
712 Instead of displaying the matching messages, display the sum
714 --sort <variable>[,<variable>...]
715 Before displaying matching messages, sort the messages according to
716 each messages value for each variable.
718 Negate the value for every test (returns inverse output from the
719 same criteria without --not).
725 1. The ${readsocket expansion item now supports Internet domain sockets as well
726 as Unix domain sockets. If the first argument begins "inet:", it must be of
727 the form "inet:host:port". The port is mandatory; it may be a number or the
728 name of a TCP port in /etc/services. The host may be a name, or it may be an
729 IP address. An ip address may optionally be enclosed in square brackets.
730 This is best for IPv6 addresses. For example:
732 ${readsocket{inet:[::1]:1234}{<request data>}...
734 Only a single host name may be given, but if looking it up yield more than
735 one IP address, they are each tried in turn until a connection is made. Once
736 a connection has been made, the behaviour is as for ${readsocket with a Unix
739 2. If a redirect router sets up file or pipe deliveries for more than one
740 incoming address, and the relevant transport has batch_max set greater than
741 one, a batch delivery now occurs.
743 3. The appendfile transport has a new option called maildirfolder_create_regex.
744 Its value is a regular expression. For a maildir delivery, this is matched
745 against the maildir directory; if it matches, Exim ensures that a
746 maildirfolder file is created alongside the new, cur, and tmp directories.
752 The documentation is up-to-date for the 4.61 release. Major new features since
753 the 4.60 release are:
755 . An option called disable_ipv6, to disable the use of IPv6 completely.
757 . An increase in the number of ACL variables to 20 of each type.
759 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
760 $2, $3, (though those are still set) because the numeric variables get used
761 for other things in complicated expansions.
763 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
765 . It is possible to use setclassresources() on some BSD OS to control the
766 resources used in pipe deliveries.
768 . A new ACL modifier called add_header, which can be used with any verb.
770 . More errors are detectable in retry rules.
772 There are a number of other additions too.
778 The documentation is up-to-date for the 4.60 release. Major new features since
779 the 4.50 release are:
781 . Support for SQLite.
783 . Support for IGNOREQUOTA in LMTP.
785 . Extensions to the "submission mode" features.
787 . Support for Client SMTP Authorization (CSA).
789 . Support for ratelimiting hosts and users.
791 . New expansion items to help with the BATV "prvs" scheme.
793 . A "match_ip" condition, that matches an IP address against a list.
795 There are many more minor changes.
git://git.exim.org / users / heiko / exim.git / blob