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