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