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