two more header order changes
[exim.git] / doc / doc-txt / NewStuff
1 $Cambridge: exim/doc/doc-txt/NewStuff,v 1.165 2010/06/03 15:20:41 jetmore Exp $
2
3 New Features in Exim
4 --------------------
5
6 This file contains descriptions of new features that have been added to Exim.
7 Before a formal release, there may be quite a lot of detail so that people can
8 test from the snapshots or the CVS before the documentation is updated. Once
9 the documentation is updated, this file is reduced to a short list.
10
11
12 Version 4.72
13 ------------
14
15 1. TWO SECURITY FIXES: one relating to mail-spools which are globally
16 writable, the other to locking of MBX folders (not mbox).
17
18 2. MySQL stored procedures are now supported.
19
20 3. The dkim_domain transport option is now a list, not a single string, and
21 messages will be signed for each element in the list (discarding
22 duplicates).
23
24 4. The 4.70 release unexpectedly changed the behaviour of dnsdb TXT lookups
25 in the presence of multiple character strings within the RR. Prior to 4.70,
26 only the first string would be returned. The dnsdb lookup now, by default,
27 preserves the pre-4.70 semantics, but also now takes an extended output
28 separator specification. The separator can be followed by a semicolon, to
29 concatenate the individual text strings together with no join character,
30 or by a comma and a second separator character, in which case the text
31 strings within a TXT record are joined on that second character.
32 Administrators are reminded that DNS provides no ordering guarantees
33 between multiple records in an RRset. For example:
34
35 foo.example. IN TXT "a" "b" "c"
36 foo.example. IN TXT "d" "e" "f"
37
38 ${lookup dnsdb{>/ txt=foo.example}} -> "a/d"
39 ${lookup dnsdb{>/; txt=foo.example}} -> "def/abc"
40 ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
41
42
43 Version 4.70 / 4.71
44 -------------------
45
46 1. Native DKIM support without an external library.
47 (Note that if no action to prevent it is taken, a straight upgrade will
48 result in DKIM verification of all signed incoming emails. See spec
49 for details on conditionally disabling)
50
51 2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).
52
53 3. There is now a bool{} expansion condition which maps certain strings to
54 true/false condition values (most likely of use in conjuction with the
55 and{} expansion operator).
56
57 4. The $spam_score, $spam_bar and $spam_report variables are now available
58 at delivery time.
59
60 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
61 options, provided that Exim is invoked by an admin_user.
62
63 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
64 which increases compatibility with older clients at the cost of decreased
65 security. Don't set this unless you need to support such clients.
66
67 7. There is a new expansion operator, ${randint:...} which will produce a
68 "random" number less than the supplied integer. This randomness is
69 not guaranteed to be cryptographically strong, but depending upon how
70 Exim was built may be better than the most naive schemes.
71
72 8. Exim now explicitly ensures that SHA256 is available when linked against
73 OpenSSL.
74
75 9. The transport_filter_timeout option now applies to SMTP transports too.
76
77
78 Version 4.68
79 ------------
80
81 1. The body_linecount and body_zerocount C variables are now exported in the
82 local_scan API.
83
84 2. When a dnslists lookup succeeds, the key that was looked up is now placed
85 in $dnslist_matched. When the key is an IP address, it is not reversed in
86 this variable (though it is, of course, in the actual lookup). In simple
87 cases, for example:
88
89 deny dnslists = spamhaus.example
90
91 the key is also available in another variable (in this case,
92 $sender_host_address). In more complicated cases, however, this is not
93 true. For example, using a data lookup might generate a dnslists lookup
94 like this:
95
96 deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|...
97
98 If this condition succeeds, the value in $dnslist_matched might be
99 192.168.6.7 (for example).
100
101 3. Authenticators now have a client_condition option. When Exim is running as
102 a client, it skips an authenticator whose client_condition expansion yields
103 "0", "no", or "false". This can be used, for example, to skip plain text
104 authenticators when the connection is not encrypted by a setting such as:
105
106 client_condition = ${if !eq{$tls_cipher}{}}
107
108 Note that the 4.67 documentation states that $tls_cipher contains the
109 cipher used for incoming messages. In fact, during SMTP delivery, it
110 contains the cipher used for the delivery. The same is true for
111 $tls_peerdn.
112
113 4. There is now a -Mvc <message-id> option, which outputs a copy of the
114 message to the standard output, in RFC 2822 format. The option can be used
115 only by an admin user.
116
117 5. There is now a /noupdate option for the ratelimit ACL condition. It
118 computes the rate and checks the limit as normal, but it does not update
119 the saved data. This means that, in relevant ACLs, it is possible to lookup
120 the existence of a specified (or auto-generated) ratelimit key without
121 incrementing the ratelimit counter for that key.
122
123 In order for this to be useful, another ACL entry must set the rate
124 for the same key somewhere (otherwise it will always be zero).
125
126 Example:
127
128 acl_check_connect:
129 # Read the rate; if it doesn't exist or is below the maximum
130 # we update it below
131 deny ratelimit = 100 / 5m / strict / noupdate
132 log_message = RATE: $sender_rate / $sender_rate_period \
133 (max $sender_rate_limit)
134
135 [... some other logic and tests...]
136
137 warn ratelimit = 100 / 5m / strict / per_cmd
138 log_message = RATE UPDATE: $sender_rate / $sender_rate_period \
139 (max $sender_rate_limit)
140 condition = ${if le{$sender_rate}{$sender_rate_limit}}
141
142 accept
143
144 6. The variable $max_received_linelength contains the number of bytes in the
145 longest line that was received as part of the message, not counting the
146 line termination character(s).
147
148 7. Host lists can now include +ignore_defer and +include_defer, analagous to
149 +ignore_unknown and +include_unknown. These options should be used with
150 care, probably only in non-critical host lists such as whitelists.
151
152 8. There's a new option called queue_only_load_latch, which defaults true.
153 If set false when queue_only_load is greater than zero, Exim re-evaluates
154 the load for each incoming message in an SMTP session. Otherwise, once one
155 message is queued, the remainder are also.
156
157 9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
158 cases when an SMTP session ends without sending QUIT. However, when Exim
159 itself is is bad trouble, such as being unable to write to its log files,
160 this ACL is not run, because it might try to do things (such as write to
161 log files) that make the situation even worse.
162
163 Like the QUIT ACL, this new ACL is provided to make it possible to gather
164 statistics. Whatever it returns (accept or deny) is immaterial. The "delay"
165 modifier is forbidden in this ACL.
166
167 When the NOTQUIT ACL is running, the variable $smtp_notquit_reason is set
168 to a string that indicates the reason for the termination of the SMTP
169 connection. The possible values are:
170
171 acl-drop Another ACL issued a "drop" command
172 bad-commands Too many unknown or non-mail commands
173 command-timeout Timeout while reading SMTP commands
174 connection-lost The SMTP connection has been lost
175 data-timeout Timeout while reading message data
176 local-scan-error The local_scan() function crashed
177 local-scan-timeout The local_scan() function timed out
178 signal-exit SIGTERM or SIGINT
179 synchronization-error SMTP synchronization error
180 tls-failed TLS failed to start
181
182 In most cases when an SMTP connection is closed without having received
183 QUIT, Exim sends an SMTP response message before actually closing the
184 connection. With the exception of acl-drop, the default message can be
185 overridden by the "message" modifier in the NOTQUIT ACL. In the case of a
186 "drop" verb in another ACL, it is the message from the other ACL that is
187 used.
188
189 10. For MySQL and PostgreSQL lookups, it is now possible to specify a list of
190 servers with individual queries. This is done by starting the query with
191 "servers=x:y:z;", where each item in the list may take one of two forms:
192
193 (1) If it is just a host name, the appropriate global option (mysql_servers
194 or pgsql_servers) is searched for a host of the same name, and the
195 remaining parameters (database, user, password) are taken from there.
196
197 (2) If it contains any slashes, it is taken as a complete parameter set.
198
199 The list of servers is used in exactly the same was as the global list.
200 Once a connection to a server has happened and a query has been
201 successfully executed, processing of the lookup ceases.
202
203 This feature is intended for use in master/slave situations where updates
204 are occurring, and one wants to update a master rather than a slave. If the
205 masters are in the list for reading, you might have:
206
207 mysql_servers = slave1/db/name/pw:slave2/db/name/pw:master/db/name/pw
208
209 In an updating lookup, you could then write
210
211 ${lookup mysql{servers=master; UPDATE ...}
212
213 If, on the other hand, the master is not to be used for reading lookups:
214
215 pgsql_servers = slave1/db/name/pw:slave2/db/name/pw
216
217 you can still update the master by
218
219 ${lookup pgsql{servers=master/db/name/pw; UPDATE ...}
220
221 11. The message_body_newlines option (default FALSE, for backwards
222 compatibility) can be used to control whether newlines are present in
223 $message_body and $message_body_end. If it is FALSE, they are replaced by
224 spaces.
225
226
227 Version 4.67
228 ------------
229
230 1. There is a new log selector called smtp_no_mail, which is not included in
231 the default setting. When it is set, a line is written to the main log
232 whenever an accepted SMTP connection terminates without having issued a
233 MAIL command.
234
235 2. When an item in a dnslists list is followed by = and & and a list of IP
236 addresses, the behaviour was not clear when the lookup returned more than
237 one IP address. This has been solved by the addition of == and =& for "all"
238 rather than the default "any" matching.
239
240 3. Up till now, the only control over which cipher suites GnuTLS uses has been
241 for the cipher algorithms. New options have been added to allow some of the
242 other parameters to be varied.
243
244 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is
245 set, Exim compiles a runtime option called disable_fsync.
246
247 5. There is a new variable called $smtp_count_at_connection_start.
248
249 6. There's a new control called no_pipelining.
250
251 7. There are two new variables called $sending_ip_address and $sending_port.
252 These are set whenever an SMTP connection to another host has been set up.
253
254 8. The expansion of the helo_data option in the smtp transport now happens
255 after the connection to the server has been made.
256
257 9. There is a new expansion operator ${rfc2047d: that decodes strings that
258 are encoded as per RFC 2047.
259
260 10. There is a new log selector called "pid", which causes the current process
261 id to be added to every log line, in square brackets, immediately after the
262 time and date.
263
264 11. Exim has been modified so that it flushes SMTP output before implementing
265 a delay in an ACL. It also flushes the output before performing a callout,
266 as this can take a substantial time. These behaviours can be disabled by
267 obeying control = no_delay_flush or control = no_callout_flush,
268 respectively, at some earlier stage of the connection.
269
270 12. There are two new expansion conditions that iterate over a list. They are
271 called forany and forall.
272
273 13. There's a new global option called dsn_from that can be used to vary the
274 contents of From: lines in bounces and other automatically generated
275 messages ("delivery status notifications" - hence the name of the option).
276
277 14. The smtp transport has a new option called hosts_avoid_pipelining.
278
279 15. By default, exigrep does case-insensitive matches. There is now a -I option
280 that makes it case-sensitive.
281
282 16. A number of new features ("addresses", "map", "filter", and "reduce") have
283 been added to string expansions to make it easier to process lists of
284 items, typically addresses.
285
286 17. There's a new ACL modifier called "continue". It does nothing of itself,
287 and processing of the ACL always continues with the next condition or
288 modifier. It is provided so that the side effects of expanding its argument
289 can be used.
290
291 18. It is now possible to use newline and other control characters (those with
292 values less than 32, plus DEL) as separators in lists.
293
294 19. The exigrep utility now has a -v option, which inverts the matching
295 condition.
296
297 20. The host_find_failed option in the manualroute router can now be set to
298 "ignore".
299
300
301 Version 4.66
302 ------------
303
304 No new features were added to 4.66.
305
306
307 Version 4.65
308 ------------
309
310 No new features were added to 4.65.
311
312
313 Version 4.64
314 ------------
315
316 1. ACL variables can now be given arbitrary names, as long as they start with
317 "acl_c" or "acl_m" (for connection variables and message variables), are at
318 least six characters long, with the sixth character being either a digit or
319 an underscore.
320
321 2. There is a new ACL modifier called log_reject_target. It makes it possible
322 to specify which logs are used for messages about ACL rejections.
323
324 3. There is a new authenticator called "dovecot". This is an interface to the
325 authentication facility of the Dovecot POP/IMAP server, which can support a
326 number of authentication methods.
327
328 4. The variable $message_headers_raw provides a concatenation of all the
329 messages's headers without any decoding. This is in contrast to
330 $message_headers, which does RFC2047 decoding on the header contents.
331
332 5. In a DNS black list, if two domain names, comma-separated, are given, the
333 second is used first to do an initial check, making use of any IP value
334 restrictions that are set. If there is a match, the first domain is used,
335 without any IP value restrictions, to get the TXT record.
336
337 6. All authenticators now have a server_condition option.
338
339 7. There is a new command-line option called -Mset. It is useful only in
340 conjunction with -be (that is, when testing string expansions). It must be
341 followed by a message id; Exim loads the given message from its spool
342 before doing the expansions.
343
344 8. Another similar new command-line option is called -bem. It operates like
345 -be except that it must be followed by the name of a file that contains a
346 message.
347
348 9. When an address is delayed because of a 4xx response to a RCPT command, it
349 is now the combination of sender and recipient that is delayed in
350 subsequent queue runs until its retry time is reached.
351
352 10. Unary negation and the bitwise logical operators and, or, xor, not, and
353 shift, have been added to the eval: and eval10: expansion items.
354
355 11. The variables $interface_address and $interface_port have been renamed
356 as $received_ip_address and $received_port, to make it clear that they
357 relate to message reception rather than delivery. (The old names remain
358 available for compatibility.)
359
360 12. The "message" modifier can now be used on "accept" and "discard" acl verbs
361 to vary the message that is sent when an SMTP command is accepted.
362
363
364 Version 4.63
365 ------------
366
367 1. There is a new Boolean option called filter_prepend_home for the redirect
368 router.
369
370 2. There is a new acl, set by acl_not_smtp_start, which is run right at the
371 start of receiving a non-SMTP message, before any of the message has been
372 read.
373
374 3. When an SMTP error message is specified in a "message" modifier in an ACL,
375 or in a :fail: or :defer: message in a redirect router, Exim now checks the
376 start of the message for an SMTP error code.
377
378 4. There is a new parameter for LDAP lookups called "referrals", which takes
379 one of the settings "follow" (the default) or "nofollow".
380
381 5. Version 20070721.2 of exipick now included, offering these new options:
382 --reverse
383 After all other sorting options have bee processed, reverse order
384 before displaying messages (-R is synonym).
385 --random
386 Randomize order of matching messages before displaying.
387 --size
388 Instead of displaying the matching messages, display the sum
389 of their sizes.
390 --sort <variable>[,<variable>...]
391 Before displaying matching messages, sort the messages according to
392 each messages value for each variable.
393 --not
394 Negate the value for every test (returns inverse output from the
395 same criteria without --not).
396
397
398 Version 4.62
399 ------------
400
401 1. The ${readsocket expansion item now supports Internet domain sockets as well
402 as Unix domain sockets. If the first argument begins "inet:", it must be of
403 the form "inet:host:port". The port is mandatory; it may be a number or the
404 name of a TCP port in /etc/services. The host may be a name, or it may be an
405 IP address. An ip address may optionally be enclosed in square brackets.
406 This is best for IPv6 addresses. For example:
407
408 ${readsocket{inet:[::1]:1234}{<request data>}...
409
410 Only a single host name may be given, but if looking it up yield more than
411 one IP address, they are each tried in turn until a connection is made. Once
412 a connection has been made, the behaviour is as for ${readsocket with a Unix
413 domain socket.
414
415 2. If a redirect router sets up file or pipe deliveries for more than one
416 incoming address, and the relevant transport has batch_max set greater than
417 one, a batch delivery now occurs.
418
419 3. The appendfile transport has a new option called maildirfolder_create_regex.
420 Its value is a regular expression. For a maildir delivery, this is matched
421 against the maildir directory; if it matches, Exim ensures that a
422 maildirfolder file is created alongside the new, cur, and tmp directories.
423
424
425 Version 4.61
426 ------------
427
428 The documentation is up-to-date for the 4.61 release. Major new features since
429 the 4.60 release are:
430
431 . An option called disable_ipv6, to disable the use of IPv6 completely.
432
433 . An increase in the number of ACL variables to 20 of each type.
434
435 . A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1,
436 $2, $3, (though those are still set) because the numeric variables get used
437 for other things in complicated expansions.
438
439 . The default for rfc1413_query_timeout has been changed from 30s to 5s.
440
441 . It is possible to use setclassresources() on some BSD OS to control the
442 resources used in pipe deliveries.
443
444 . A new ACL modifier called add_header, which can be used with any verb.
445
446 . More errors are detectable in retry rules.
447
448 There are a number of other additions too.
449
450
451 Version 4.60
452 ------------
453
454 The documentation is up-to-date for the 4.60 release. Major new features since
455 the 4.50 release are:
456
457 . Support for SQLite.
458
459 . Support for IGNOREQUOTA in LMTP.
460
461 . Extensions to the "submission mode" features.
462
463 . Support for Client SMTP Authorization (CSA).
464
465 . Support for ratelimiting hosts and users.
466
467 . New expansion items to help with the BATV "prvs" scheme.
468
469 . A "match_ip" condition, that matches an IP address against a list.
470
471 There are many more minor changes.
472
473 ****