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