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