Add comment about {} now being an error in numerical expansion
[exim.git] / src / README.UPDATING
1 $Cambridge: exim/src/README.UPDATING,v 1.14 2006/09/26 14:51:02 ph10 Exp $
3 This document contains detailed information about incompatibilities that might
4 be encountered when upgrading from one release of Exim to another. The
5 information is in reverse order of release numbers. Mostly these are relatively
6 small points, and the configuration file is normally upwards compatible, but
7 there have been two big upheavals...
10 **************************************************************************
11 * There was a big reworking of the way mail routing works for release *
12 * 4.00. Previously used "directors" were abolished, and all routing is *
13 * now done by routers. Policy controls for incoming mail are now done by *
14 * Access Control Lists instead of separate options. All this means that *
15 * pre-4.00 configuration files have to be massively converted. If you *
16 * are coming from a 3.xx release, please read the document in the file *
17 * doc/Exim4.upgrade, and allow some time to complete the upgrade. *
18 * *
19 * There was a big reworking of the way domain/host/net/address lists are *
20 * handled at release 3.00. If you are coming from a pre-3.00 release, it *
21 * might be easier to start again from a default configuration. Otherwise *
22 * you need to read doc/Exim3.upgrade and do a double conversion of your *
23 * configuration file. *
24 **************************************************************************
27 The rest of this document contains information about changes in 4.xx releases
28 that might affect a running system.
31 Exim version 4.64
32 -----------------
34 1. Callouts were setting the name used for EHLO/HELO from $smtp_active_
35 hostname. This is wrong, because it relates to the incoming message (and
36 probably the interface on which it is arriving) and not to the outgoing
37 callout (which could be using a different interface). This has been
38 changed to use the value of the helo_data option from the smtp transport
39 instead - this is what is used when a message is actually being sent. If
40 there is no remote transport (possible with a router that sets up host
41 addresses), $smtp_active_hostname is used. This change is mentioned here in
42 case somebody is relying on the use of $smtp_active_hostname.
44 2. A bug has been fixed that might just possibly be something that is relied on
45 in some configurations. In expansion items such as ${if >{xxx}{yyy}...} an
46 empty string (that is {}) was being interpreted as if it was {0} and therefore
47 treated as the number zero. From release 4.64, such strings cause an error
48 because a decimal number, possibly followed by K or M, is required (as has
49 always been documented).
52 Exim version 4.63
53 -----------------
55 When an SMTP error message is specified in a "message" modifier in an ACL, or
56 in a :fail: or :defer: message in a redirect router, Exim now checks the start
57 of the message for an SMTP error code. This consists of three digits followed
58 by a space, optionally followed by an extended code of the form n.n.n, also
59 followed by a space. If this is the case and the very first digit is the same
60 as the default error code, the code from the message is used instead. If the
61 very first digit is incorrect, a panic error is logged, and the default code is
62 used. This is an incompatible change, but it is not expected to affect many (if
63 any) configurations. It is possible to suppress the use of the supplied code in
64 a redirect router by setting the smtp_error_code option false. In this case,
65 any SMTP code is quietly ignored.
68 Exim version 4.61
69 -----------------
71 1. The default number of ACL variables of each type has been increased to 20,
72 and it's possible to compile Exim with more. You can safely upgrade to this
73 release if you already have messages on the queue with saved ACL variable
74 values. However, if you downgrade from this release with messages on the queue,
75 any saved ACL values they may have will be lost.
77 2. The default value for rfc1413_query_timeout has been changed from 30s to 5s.
80 Exim version 4.54
81 -----------------
83 There was a problem with 4.52/TF/02 in that a "name=" option on control=
84 submission terminated at the next slash, thereby not allowing for slashes in
85 the name. This has been changed so that "name=" takes the rest of the string as
86 its data. It must therefore be the last option.
89 Version 4.53
90 ------------
92 If you are using the experimental Domain Keys support, you must upgrade to
93 at least libdomainkeys 0.67 in order to run this release of Exim.
96 Version 4.51
97 ------------
99 1. The format in which GnuTLS parameters are cached (in the file gnutls-params
100 in the spool directory) has been changed. The new format can also be generated
101 externally, so it is now possible to update the values from outside Exim. This
102 has been implemented in an upwards, BUT NOT downwards, compatible manner.
103 Upgrading should be seamless: when Exim finds that it cannot understand an
104 existing cache file, it generates new parameters and writes them to the cache
105 in the new format. If, however, you downgrade from 4.51 to a previous release,
106 you MUST delete the gnutls-params file in the spool directory, because the
107 older Exim will not recognize the new format.
109 2. When doing a callout as part of verifying an address, Exim was not paying
110 attention to any local part prefix or suffix that was matched by the router
111 that accepted the address. It now behaves in the same way as it does for
112 delivery: the affixes are removed from the local part unless
113 rcpt_include_affixes is set on the transport. If you have a configuration that
114 uses prefixes or suffixes on addresses that could be used for callouts, and you
115 want the affixes to be retained, you must make sure that rcpt_include_affixes
116 is set on the transport.
118 3. Bounce and delay warning messages no longer contain details of delivery
119 errors, except for explicit messages (e.g. generated by :fail:) and SMTP
120 responses from remote hosts.
123 Version 4.50
124 ------------
126 The exicyclog script has been updated to use three-digit numbers in rotated log
127 files if the maximum number to keep is greater than 99. If you are already
128 keeping more than 99, there will be an incompatible change when you upgrade.
129 You will probably want to rename your old log files to the new form before
130 running the new exicyclog.
133 Version 4.42
134 ------------
136 RFC 3848 specifies standard names for the "with" phrase in Received: header
137 lines when AUTH and/or TLS are in use. This is the "received protocol"
138 field. Exim used to use "asmtp" for authenticated SMTP, without any
139 indication (in the protocol name) for TLS use. Now it follows the RFC and
140 uses "esmtpa" if the connection is authenticated, "esmtps" if it is
141 encrypted, and "esmtpsa" if it is both encrypted and authenticated. These names
142 appear in log lines as well as in Received: header lines.
145 Version 4.34
146 ------------
148 Change 4.31/2 gave problems to data ACLs and local_scan() functions that
149 expected to see a Received: header. I have changed to yet another scheme. The
150 Received: header is now generated after the body is received, but before the
151 ACL or local_scan() is called. After they have run, the timestamp in the
152 Received: header is updated.
154 Thus, change (a) of 4.31/2 has been reversed, but change (b) is still true,
155 which is lucky, since I decided it was a bug fix.
158 Version 4.33
159 ------------
161 If an expansion in a condition on a "warn" statement fails because a lookup
162 defers, the "warn" statement is abandoned, and the next ACL statement is
163 processed. Previously this caused the whole ACL to be aborted.
166 Version 4.32
167 ------------
169 Change 4.31/2 has been reversed, as it proved contentious. Recipient callout
170 verification now uses <> in the MAIL command by default, as it did before. A
171 new callout option, "use_sender", has been added to request the other
172 behaviour.
175 Version 4.31
176 ------------
178 1. If you compile Exim to use GnuTLS, it now requires the use of release 1.0.0
179 or greater. The interface to the obsolete 0.8.x releases is no longer
180 supported. There is one externally visible change: the format for the
181 display of Distinguished Names now uses commas as a separator rather than a
182 slash. This is to comply with RFC 2253.
184 2. When a message is received, the Received: header line is now generated when
185 reception is complete, instead of at the start of reception. For messages
186 that take a long time to come in, this changes the meaning of the timestamp.
187 There are several side-effects of this change:
189 (a) If a message is rejected by a DATA or non-SMTP ACL, or by local_scan(),
190 the logged header lines no longer include the local Received: line,
191 because it has not yet been created. If the message is a non-SMTP one,
192 and the error is processed by sending a message to the sender, the copy
193 of the original message that is returned does not have an added
194 Received: line.
196 (b) When a filter file is tested using -bf, no additional Received: header
197 is added to the test message. After some thought, I decided that this
198 is a bug fix.
200 The contents of $received_for are not affected by this change. This
201 variable still contains the single recipient of a message, copied after
202 addresses have been rewritten, but before local_scan() is run.
204 2. Recipient callout verification, like sender verification, was using <> in
205 the MAIL FROM command. This isn't really the right thing, since the actual
206 sender may affect whether the remote host accepts the recipient or not. I
207 have changed it to use the actual sender in the callout; this means that
208 the cache record is now keyed on a recipient/sender pair, not just the
209 recipient address. There doesn't seem to be a real danger of callout loops,
210 since a callout by the remote host to check the sender would use <>.
213 Version 4.30
214 ------------
216 1. I have abolished timeout_DNS as an error that can be detected in retry
217 rules, because it has never worked. Despite the fact that it has been
218 documented since at least release 1.62, there was no code to support it.
219 If you have used it in your retry rules, you will now get a warning message
220 to the log and panic log. It is now treated as plain "timeout".
222 2. After discussion on the mailing list, Exim no longer adds From:, Date:, or
223 Message-Id: header lines to messages that do not originate locally, that is,
224 messages that have an associated sending host address.
226 3. When looking up a host name from an IP address, Exim now tries the DNS
227 first, and only if that fails does it use gethostbyaddr() (or equivalent).
228 This change was made because on some OS, not all the names are given for
229 addresses with multiple PTR records via the gethostbyaddr() interface. The
230 order of lookup can be changed by setting host_lookup_order.
233 Version 4.23
234 ------------
236 1. The new FIXED_NEVER_USERS build-time option creates a list of "never users"
237 that cannot be overridden. The default in the distributed EDITME is "root".
238 If for some reason you were (against advice) running deliveries as root, you
239 will have to ensure that FIXED_NEVER_USERS is not set in your
240 Local/Makefile.
242 2. The ${quote: operator now quotes an empty string, which it did not before.
244 3. Version 4.23 saves the contents of the ACL variables with the message, so
245 that they can be used later. If one of these variables contains a newline,
246 there will be a newline character in the spool that will not be interpreted
247 correctely by a previous version of Exim. (Exim ignores keyed spool file
248 items that it doesn't understand - precisely for this kind of problem - but
249 it expects them all to be on one line.)
251 So the bottom line is: if you have newlines in your ACL variables, you
252 cannot retreat from 4.23.
255 Version 4.21
256 ------------
258 1. The idea of the "warn" ACL verb is that it adds a header or writes to the
259 log only when "message" or "log_message" are set. However, if one of the
260 conditions was an address verification, or a call to a nested ACL, the
261 messages generated by the underlying test were being passed through. This
262 no longer happens. The underlying message is available in $acl_verify_
263 message for both "message" and "log_message" expansions, so it can be
264 passed through if needed.
266 2. The way that the $h_ (and $header_) expansions work has been changed by the
267 addition of RFC 2047 decoding. See the main documentation (the NewStuff file
268 until release 4.30, then the manual) for full details. Briefly, there are
269 now three forms:
271 $rh_xxx: and $rheader_xxx: give the original content of the header
272 line(s), with no processing at all.
274 $bh_xxx: and $bheader_xxx: remove leading and trailing white space, and
275 then decode base64 or quoted-printable "words" within the header text,
276 but do not do charset translation.
278 $h_xxx: and $header_xxx: attempt to translate the $bh_ string to a
279 standard character set.
281 If you have previously been using $h_ expansions to access the raw
282 characters, you should change to $rh_ instead.
284 3. When Exim creates an RFC 2047 encoded word in a header line, it labels it
285 with the default character set from the headers_charset option instead of
286 always using iso-8859-1.
288 4. If TMPDIR is defined in Local/Makefile (default in src/EDITME is
289 TMPDIR="/tmp"), Exim checks for the presence of an environment variable
290 called TMPDIR, and if it finds it is different, it changes its value.
292 5. Following a discussion on the list, the rules by which Exim recognises line
293 endings on incoming messages have been changed. The -dropcr and drop_cr
294 options are now no-ops, retained only for backwards compatibility. The
295 following line terminators are recognized: LF CRLF CR. However, special
296 processing applies to CR:
298 (i) The sequence CR . CR does *not* terminate an incoming SMTP message,
299 nor a local message in the state where . is a terminator.
301 (ii) If a bare CR is encountered in a header line, an extra space is added
302 after the line terminator so as not to end the header. The reasoning
303 behind this is that bare CRs in header lines are most likely either
304 to be mistakes, or people trying to play silly games.
306 6. The code for using daemon_smtp_port, local_interfaces, and the -oX options
307 has been reorganized. It is supposed to be backwards compatible, but it is
308 mentioned here just in case I've screwed up.
312 Version 4.20
313 ------------
315 1. I have tidied and re-organized the code that uses alarm() for imposing time
316 limits on various things. It shouldn't affect anything, but if you notice
317 processes getting stuck, it may be that I've broken something.
319 2. The "arguments" log selector now also logs the current working directory
320 when Exim is called.
322 3. An incompatible change has been made to the appendfile transport. This
323 affects the case when it is used for file deliveries that are set up by
324 .forward and filter files. Previously, any settings of the "file" or
325 "directory" options were ignored. It is hoped that, like the address_file
326 transport in the default configuration, these options were never in fact set
327 on such transports, because they were of no use.
329 Now, if either of these options is set, it is used. The path that is passed
330 by the router is in $address_file (this is not new), so it can be used as
331 part of a longer path, or modified in any other way that expansion permits.
333 If neither "file" nor "directory" is set, the behaviour is unchanged.
335 4. Related to the above: in a filter, if a "save" command specifies a non-
336 absolute path, the value of $home/ is pre-pended. This no longer happens if
337 $home is unset or is set to an empty string.
339 5. Multiple file deliveries from a filter or .forward file can never be
340 batched; the value of batch_max on the transport is ignored for file
341 deliveries. I'm assuming that nobody ever actually set batch_max on the
342 address_file transport - it would have had odd effects previously.
344 6. DESTDIR is the more common variable that ROOT for use when installing
345 software under a different root filing system. The Exim install script now
346 recognizes DESTDIR first; if it is not set, ROOT is used.
348 7. If DESTDIR is set when installing Exim, it no longer prepends its value to
349 the path of the system aliases file that appears in the default
350 configuration (when a default configuration is installed). If an aliases
351 file is actually created, its name *does* use the prefix.
354 Version 4.14
355 ------------
357 1. The default for the maximum number of unknown SMTP commands that Exim will
358 accept before dropping a connection has been reduced from 5 to 3. However, you
359 can now change the value by setting smtp_max_unknown_commands.
361 2. The ${quote: operator has been changed so that it turns newline and carriage
362 return characters into \n and \r, respectively.
364 3. The file names used for maildir messages now include the microsecond time
365 fraction as well as the time in seconds, to cope with systems where the process
366 id can be re-used within the same second. The format is now
368 <time>.H<microsec>P<pid>.<host>
370 This should be a compatible change, but is noted here just in case.
372 4. The rules for creating message ids have changed, to cope with systems where
373 the process id can be re-used within the same second. The format, however, is
374 unchanged, so this should not cause any problems, except as noted in the next
375 item.
377 5. The maximum value for localhost_number has been reduced from 255 to 16, in
378 order to implement the new message id rules. For operating systems that have
379 case-insensitive file systems (Cygwin and Darwin), the limit is 10.
381 6. verify = header_syntax was allowing unqualified addresses in all cases. Now
382 it allows them only for locally generated messages and from hosts that match
383 sender_unqualified_hosts or recipient_unqualified_hosts, respectively.
385 7. For reasons lost in the mists of time, when a pipe transport was run, the
386 environment variable MESSAGE_ID was set to the message ID preceded by 'E' (the
387 form used in Message-ID: header lines). The 'E' has been removed.
390 Version 4.11
391 ------------
393 1. The handling of lines in the configuration file has changed. Previously,
394 macro expansion was applied to logical lines, after continuations had been
395 joined on. This meant that it could not be used in .include lines, which are
396 handled as physical rather than logical lines. Macro expansion is now done on
397 physical lines rather than logical lines. This means there are two
398 incompatibilities:
400 (a) A macro that expands to # to turn a line into a comment now applies only
401 to the physical line where it appears. Previously, it would have caused
402 any following continuations also to be ignored.
404 (b) A macro name can no longer be split over the boundary between a line and
405 its continuation. Actually, this is more of a bug fix. :-)
407 2. The -D command line option must now all be within one command line item.
408 This makes it possible to use -D to set a macro to the empty string by commands
409 such as
411 exim -DABC ...
412 exim -DABC= ...
414 Previously, these items would have moved on to the next item on the command
415 line. To include spaces in a macro definition item, quotes must be used, in
416 which case you can also have spaces after -D and surrounding the equals. For
417 example:
419 exim '-D ABC = something' ...
421 3. The way that addresses that redirect to themselves are handled has been
422 changed, in order to fix an obscure bug. This should not cause any problems
423 except in the case of wanting to go back from a 4.11 (or later) release to an
424 earlier release. If there are undelivered messages on the spool that contain
425 addresses which redirect to themselves, and the redirected addresses have
426 already been delivered, you might get a duplicate delivery if you revert to an
427 earlier Exim.
429 4. The default way of looking up IP addresses for hosts in the manualroute and
430 queryprogram routers has been changed. If "byname" or "bydns" is explicitly
431 specified, there is no change, but if no method is specified, Exim now behaves
432 as follows:
434 First, a DNS lookup is done. If this yields anything other than
435 HOST_NOT_FOUND, that result is used. Otherwise, Exim goes on to try a call to
436 getipnodebyname() (or gethostbyname() on older systems) and the result of the
437 lookup is the result of that call.
439 This change has been made because it has been discovered that on some systems,
440 if a DNS lookup called via getipnodebyname() times out, HOST_NOT_FOUND is
441 returned instead of TRY_AGAIN. Thus, it is safest to try a DNS lookup directly
442 first, and only if that gives a definite "no such host" to try the local
443 function.
445 5. In fixing the minor security problem with pid_file_path, I have removed some
446 backwards-compatible (undocumented) code which was present to ease conversion
447 from Exim 3. In Exim 4, pid_file_path is a literal; in Exim 3 it was allowed to
448 contain "%s", which was replaced by the port number for daemons listening on
449 non-standard ports. In Exim 4, such daemons do not write a pid file. The
450 backwards compatibility feature was to replace "%s" by nothing if it occurred
451 in an Exim 4 setting of pid_file_path. The bug was in this code. I have solved
452 the problem by removing the backwards compatibility feature. Thus, if you still
453 have "%s" somewhere in a setting of pid_file_path, you should remove it.
455 6. There has been an extension to lsearch files. The keys in these files may
456 now be quoted in order to allow for whitespace and colons in them. This means
457 that if you were previously using keys that began with a doublequote, you will
458 now have to wrap them with extra quotes and escape the internal quotes. The
459 possibility that anybody is actually doing this seems extremely remote, but it
460 is documented just in case.
463 Version 4.10
464 ------------
466 The build-time parameter EXIWHAT_KILL_ARG has been renamed EXIWHAT_KILL_SIGNAL
467 to better reflect its function. The OS-specific files have been updated. Only
468 if you have explicitly set this in your Makefile (highly unlikely) do you need
469 to change anything.
471 ****