Commit | Line | Data |
---|---|---|
0f4f2a88 PH |
1 | This document contains detailed information about incompatibilities that might |
2 | be encountered when upgrading from one release of Exim to another. The | |
3 | information is in reverse order of release numbers. Mostly these are relatively | |
4 | small points, and the configuration file is normally upwards compatible, but | |
5 | there have been two big upheavals... | |
6 | ||
7 | ||
8 | ************************************************************************** | |
9 | * There was a big reworking of the way mail routing works for release * | |
10 | * 4.00. Previously used "directors" were abolished, and all routing is * | |
11 | * now done by routers. Policy controls for incoming mail are now done by * | |
12 | * Access Control Lists instead of separate options. All this means that * | |
13 | * pre-4.00 configuration files have to be massively converted. If you * | |
14 | * are coming from a 3.xx release, please read the document in the file * | |
15 | * doc/Exim4.upgrade, and allow some time to complete the upgrade. * | |
16 | * * | |
17 | * There was a big reworking of the way domain/host/net/address lists are * | |
18 | * handled at release 3.00. If you are coming from a pre-3.00 release, it * | |
19 | * might be easier to start again from a default configuration. Otherwise * | |
20 | * you need to read doc/Exim3.upgrade and do a double conversion of your * | |
21 | * configuration file. * | |
22 | ************************************************************************** | |
23 | ||
24 | ||
25 | The rest of this document contains information about changes in 4.xx releases | |
26 | that might affect a running system. | |
2eda48c6 | 27 | |
e6acf885 | 28 | |
83e2f8a2 | 29 | Exim version 4.80 |
dec5017e PP |
30 | ----------------- |
31 | ||
83e2f8a2 PP |
32 | * BEWARE backwards-incompatible changes in SSL libraries, thus the version |
33 | bump. See points below for details. | |
c2b063d4 | 34 | Also an LDAP data returned format change. |
83e2f8a2 | 35 | |
dec5017e PP |
36 | * The value of $tls_peerdn is now print-escaped when written to the spool file |
37 | in a -tls_peerdn line, and unescaped when read back in. We received reports | |
38 | of values with embedded newlines, which caused spool file corruption. | |
39 | ||
40 | If you have a corrupt spool file and you wish to recover the contents after | |
41 | upgrading, then lock the message, replace the new-lines that should be part | |
42 | of the -tls_peerdn line with the two-character sequence \n and then unlock | |
43 | the message. No tool has been provided as we believe this is a rare | |
44 | occurence. | |
45 | ||
f0f5a555 PP |
46 | * For OpenSSL, SSLv2 is now disabled by default. (GnuTLS does not support |
47 | SSLv2). RFC 6176 prohibits SSLv2 and some informal surveys suggest no | |
48 | actual usage. You can re-enable with the "openssl_options" Exim option, | |
49 | in the main configuration section. Note that supporting SSLv2 exposes | |
50 | you to ciphersuite downgrade attacks. | |
51 | ||
c80c5570 PP |
52 | * With OpenSSL 1.0.1+, Exim now supports TLS 1.1 and TLS 1.2. If built |
53 | against 1.0.1a then you will get a warning message and the | |
54 | "openssl_options" value will not parse "no_tlsv1_1": the value changes | |
55 | incompatibly between 1.0.1a and 1.0.1b, because the value chosen for 1.0.1a | |
56 | is infelicitous. We advise avoiding 1.0.1a. | |
57 | ||
58 | "openssl_options" gains "no_tlsv1_1", "no_tlsv1_2" and "no_compression". | |
59 | ||
da3ad30d | 60 | COMPATIBILITY WARNING: The default value of "openssl_options" is no longer |
f0f5a555 PP |
61 | "+dont_insert_empty_fragments". We default to "+no_sslv2". |
62 | That old default was grandfathered in from before openssl_options became a | |
63 | configuration option. | |
da3ad30d PP |
64 | Empty fragments are inserted by default through TLS1.0, to partially defend |
65 | against certain attacks; TLS1.1+ change the protocol so that this is not | |
66 | needed. The DIEF SSL option was required for some old releases of mail | |
67 | clients which did not gracefully handle the empty fragments, and was | |
68 | initially set in Exim release 4.31 (see ChangeLog, item 37). | |
69 | ||
70 | If you still have affected mail-clients, and you see SSL protocol failures | |
71 | with this release of Exim, set: | |
72 | openssl_options = +dont_insert_empty_fragments | |
73 | in the main section of your Exim configuration file. You're trading off | |
74 | security for compatibility. Exim is now defaulting to higher security and | |
75 | rewarding more modern clients. | |
76 | ||
3375e053 PP |
77 | If the option tls_dhparams is set and the parameters loaded from the file |
78 | have a bit-count greater than the new option tls_dh_max_bits, then the file | |
79 | will now be ignored. If this affects you, raise the tls_dh_max_bits limit. | |
80 | We suspect that most folks are using dated defaults and will not be affected. | |
81 | ||
5407bfff JH |
82 | * Ldap lookups returning multi-valued attributes now separate the attributes |
83 | with only a comma, not a comma-space sequence. Also, an actual comma within | |
84 | a returned attribute is doubled. This makes it possible to parse the | |
85 | attribute as a comma-separated list. Note the distinction from multiple | |
86 | attributes being returned, where each one is a name=value pair. | |
c80c5570 | 87 | |
c2b063d4 PP |
88 | If you are currently splitting the results from LDAP upon a comma, then you |
89 | should check carefully to see if adjustments are needed. | |
90 | ||
91 | This change lets cautious folks distinguish "comma used as separator for | |
92 | joining values" from "comma inside the data". | |
93 | ||
9cbad13b PP |
94 | * accept_8bitmime now defaults on, which is not RFC compliant but is better |
95 | suited to today's Internet. See http://cr.yp.to/smtp/8bitmime.html for a | |
96 | sane rationale. Those who wish to be strictly RFC compliant, or know that | |
97 | they need to talk to servers that are not 8-bit-clean, now need to take | |
98 | explicit configuration action to default this option off. This is not a | |
99 | new option, you can safely force it off before upgrading, to decouple | |
100 | configuration changes from the binary upgrade while remaining RFC compliant. | |
101 | ||
f90a9fd1 PP |
102 | * The GnuTLS support has been mostly rewritten, to use APIs which don't cause |
103 | deprecation warnings in GnuTLS 2.12.x. As part of this, these three options | |
104 | are no longer supported: | |
17c76198 PP |
105 | |
106 | gnutls_require_kx | |
107 | gnutls_require_mac | |
108 | gnutls_require_protocols | |
109 | ||
f90a9fd1 PP |
110 | Their functionality is entirely subsumed into tls_require_ciphers. In turn, |
111 | tls_require_ciphers is no longer an Exim list and is not parsed by Exim, but | |
112 | is instead given to gnutls_priority_init(3), which expects a priority string; | |
113 | this behaviour is much closer to the OpenSSL behaviour. See: | |
17c76198 PP |
114 | |
115 | http://www.gnu.org/software/gnutls/manual/html_node/Priority-Strings.html | |
116 | ||
117 | for fuller documentation of the strings parsed. The three gnutls_require_* | |
118 | options are still parsed by Exim and, for this release, silently ignored. | |
119 | A future release will add warnings, before a later still release removes | |
120 | parsing entirely and the presence of the options will be a configuration | |
121 | error. | |
122 | ||
83e2f8a2 PP |
123 | Note that by default, GnuTLS will not accept RSA-MD5 signatures in chains. |
124 | A tls_require_ciphers value of NORMAL:%VERIFY_ALLOW_SIGN_RSA_MD5 may | |
125 | re-enable support, but this is not supported by the Exim maintainers. | |
126 | Our test suite no longer includes MD5-based certificates. | |
127 | ||
17c76198 PP |
128 | This rewrite means that Exim will continue to build against GnuTLS in the |
129 | future, brings Exim closer to other GnuTLS applications and lets us add | |
130 | support for SNI and other features more readily. We regret that it wasn't | |
131 | feasible to retain the three dropped options. | |
132 | ||
3375e053 PP |
133 | * If built with TLS support, then Exim will now validate the value of |
134 | the main section tls_require_ciphers option at start-up. Before, this | |
135 | would cause a STARTTLS 4xx failure, now it causes a failure to start. | |
136 | Running with a broken configuration which causes failures that may only | |
137 | be left in the logs has been traded off for something more visible. This | |
138 | change makes an existing problem more prominent, but we do not believe | |
139 | anyone would deliberately be running with an invalid tls_require_ciphers | |
140 | option. | |
141 | ||
142 | This also means that library linkage issues caused by conflicts of some | |
143 | kind might take out the main daemon, not just the delivery or receiving | |
144 | process. Conceivably some folks might prefer to continue delivering | |
145 | mail plaintext when their binary is broken in this way, if there is a | |
146 | server that is a candidate to receive such mails that does not advertise | |
147 | STARTTLS. Note that Exim is typically a setuid root binary and given | |
148 | broken linkage problems that cause segfaults, we feel it is safer to | |
149 | fail completely. (The check is not done as root, to ensure that problems | |
150 | here are not made worse by the check). | |
151 | ||
a799883d PP |
152 | * The "tls_dhparam" option has been updated, so that it can now specify a |
153 | path or an identifier for a standard DH prime from one of a few RFCs. | |
154 | The default for OpenSSL is no longer to not use DH but instead to use | |
155 | one of these standard primes. The default for GnuTLS is no longer to use | |
156 | a file in the spool directory, but to use that same standard prime. | |
157 | The option is now used by GnuTLS too. If it points to a path, then | |
158 | GnuTLS will use that path, instead of a file in the spool directory; | |
159 | GnuTLS will attempt to create it if it does not exist. | |
160 | ||
161 | To preserve the previous behaviour of generating files in the spool | |
162 | directory, set "tls_dhparam = historic". Since prior releases of Exim | |
163 | ignored tls_dhparam when using GnuTLS, this can safely be done before | |
164 | the upgrade. | |
165 | ||
166 | ||
dec5017e | 167 | |
c566dd90 PP |
168 | Exim version 4.77 |
169 | ----------------- | |
170 | ||
171 | * GnuTLS will now attempt to use TLS 1.2 and TLS 1.1 before TLS 1.0 and SSL3, | |
172 | if supported by your GnuTLS library. Use the existing | |
173 | "gnutls_require_protocols" option to downgrade this if that will be a | |
174 | problem. Prior to this release, supported values were "TLS1" and "SSL3", | |
175 | so you should be able to update configuration prior to update. | |
176 | ||
0215ec07 PP |
177 | [nb: gnutls_require_protocols removed in Exim 4.80, instead use |
178 | tls_require_ciphers to provide a priority string; see notes above] | |
179 | ||
39257585 PP |
180 | * The match_<type>{string1}{string2} expansion conditions no longer subject |
181 | string2 to string expansion, unless Exim was built with the new | |
182 | "EXPAND_LISTMATCH_RHS" option. Too many people have inadvertently created | |
183 | insecure configurations that way. If you need the functionality and turn on | |
184 | that build option, please let the developers know, and know why, so we can | |
185 | try to provide a safer mechanism for you. | |
186 | ||
a7ee5955 PP |
187 | The match{}{} expansion condition (for regular expressions) is NOT affected. |
188 | For match_<type>{s1}{s2}, all list functionality is unchanged. The only | |
189 | change is that a '$' appearing in s2 will not trigger expansion, but instead | |
190 | will be treated as a literal $ sign; the effect is very similar to having | |
191 | wrapped s2 with \N...\N. If s2 contains a named list and the list definition | |
192 | uses $expansions then those _will_ be processed as normal. It is only the | |
193 | point at which s2 is read where expansion is inhibited. | |
194 | ||
195 | If you are trying to test if two email addresses are equal, use eqi{s1}{s2}. | |
196 | If you are testing if the address in s1 occurs in the list of items given | |
197 | in s2, either use the new inlisti{s1}{s2} condition (added in 4.77) or use | |
198 | the pre-existing forany{s2}{eqi{$item}{s1}} condition. | |
199 | ||
c566dd90 | 200 | |
e6acf885 PP |
201 | Exim version 4.74 |
202 | ----------------- | |
203 | ||
4050a044 PP |
204 | * The integrated support for dynamically loadable lookup modules has an ABI |
205 | change from the modules supported by some OS vendors through an unofficial | |
206 | patch. Don't try to mix & match. | |
207 | ||
208 | * Some parts of the build system are now beginning to assume that the host | |
209 | environment is POSIX. If you're building on a system where POSIX tools are | |
210 | not the default, you might have an easier time if you switch to the POSIX | |
211 | tools. Feel free to report non-POSIX issues as a request for a feature | |
212 | enhancement, but if the POSIX variants are available then the fix will | |
213 | probably just involve some coercion. See the README instructions for | |
214 | building on such hosts. | |
e6acf885 PP |
215 | |
216 | ||
217 | Exim version 4.73 | |
218 | ----------------- | |
219 | ||
220 | * The Exim run-time user can no longer be root; this was always | |
221 | strongly discouraged, but is now prohibited both at build and | |
222 | run-time. If you need Exim to run routinely as root, you'll need to | |
223 | patch the source and accept the risk. Here be dragons. | |
224 | ||
225 | * Exim will no longer accept a configuration file owned by the Exim | |
226 | run-time user, unless that account is explicitly the value in | |
227 | CONFIGURE_OWNER, which we discourage. Exim now checks to ensure that | |
a7ee5955 | 228 | files are not writeable by other accounts. |
e6acf885 PP |
229 | |
230 | * The ALT_CONFIG_ROOT_ONLY build option is no longer optional and is forced | |
231 | on; the Exim user can, by default, no longer use -C/-D and retain privilege. | |
232 | Two new build options mitigate this. | |
233 | ||
234 | * TRUSTED_CONFIG_LIST defines a file containing a whitelist of config | |
235 | files that are trusted to be selected by the Exim user; one per line. | |
236 | This is the recommended approach going forward. | |
237 | ||
238 | * WHITELIST_D_MACROS defines a colon-separated list of macro names which | |
239 | the Exim run-time user may safely pass without dropping privileges. | |
240 | Because changes to this involve a recompile, this is not the recommended | |
241 | approach but may ease transition. The values of the macros, when | |
43236f35 | 242 | overridden, are constrained to match this regex: ^[A-Za-z0-9_/.-]*$ |
e6acf885 PP |
243 | |
244 | * The system_filter_user option now defaults to the Exim run-time user, | |
245 | rather than root. You can still set it explicitly to root and this | |
246 | can be done with prior versions too, letting you roll versions | |
247 | without needing to change this configuration option. | |
248 | ||
249 | * ClamAV must be at least version 0.95 unless WITH_OLD_CLAMAV_STREAM is | |
250 | defined at build time. | |
251 | ||
252 | ||
2eda48c6 TK |
253 | Exim version 4.70 |
254 | ----------------- | |
255 | ||
256 | 1. Experimental Yahoo! Domainkeys support has been dropped in this release. | |
257 | It has been superceded by a native implementation of its successor DKIM. | |
258 | ||
259 | 2. Up to version 4.69, Exim came with an embedded version of the PCRE library. | |
260 | As of 4.70, this is no longer the case. To compile Exim, you will need PCRE | |
a7ee5955 | 261 | installed. Most OS distributions have ready-made library and development |
2eda48c6 | 262 | packages. |
0f4f2a88 PH |
263 | |
264 | ||
3c223874 PH |
265 | Exim version 4.68 |
266 | ----------------- | |
267 | ||
268 | 1. The internal implementation of the database keys that are used for ACL | |
269 | ratelimiting has been tidied up. This means that an update to 4.68 might cause | |
270 | Exim to "forget" previous rates that it had calculated, and reset them to zero. | |
271 | ||
272 | ||
26da7e20 PH |
273 | Exim version 4.64 |
274 | ----------------- | |
275 | ||
276 | 1. Callouts were setting the name used for EHLO/HELO from $smtp_active_ | |
277 | hostname. This is wrong, because it relates to the incoming message (and | |
278 | probably the interface on which it is arriving) and not to the outgoing | |
279 | callout (which could be using a different interface). This has been | |
280 | changed to use the value of the helo_data option from the smtp transport | |
281 | instead - this is what is used when a message is actually being sent. If | |
282 | there is no remote transport (possible with a router that sets up host | |
283 | addresses), $smtp_active_hostname is used. This change is mentioned here in | |
284 | case somebody is relying on the use of $smtp_active_hostname. | |
285 | ||
ebc9d865 PH |
286 | 2. A bug has been fixed that might just possibly be something that is relied on |
287 | in some configurations. In expansion items such as ${if >{xxx}{yyy}...} an | |
288 | empty string (that is {}) was being interpreted as if it was {0} and therefore | |
289 | treated as the number zero. From release 4.64, such strings cause an error | |
290 | because a decimal number, possibly followed by K or M, is required (as has | |
291 | always been documented). | |
292 | ||
b6c27e28 PH |
293 | 3. There has been a change to the GnuTLS support (ChangeLog/PH/20) to improve |
294 | Exim's performance. Unfortunately, this has the side effect of being slightly | |
295 | non-upwards compatible for versions 4.50 and earlier. If you are upgrading from | |
296 | one of these earlier versions and you use GnuTLS, you must remove the file | |
297 | called gnutls-params in Exim's spool directory. If you don't do this, you will | |
298 | see this error: | |
299 | ||
300 | TLS error on connection from ... (DH params import): Base64 decoding error. | |
301 | ||
302 | Removing the file causes Exim to recompute the relevant encryption parameters | |
303 | and cache them in the new format that was introduced for release 4.51 (May | |
304 | 2005). If you are upgrading from release 4.51 or later, there should be no | |
305 | problem. | |
306 | ||
26da7e20 | 307 | |
a5bd321b PH |
308 | Exim version 4.63 |
309 | ----------------- | |
310 | ||
311 | When an SMTP error message is specified in a "message" modifier in an ACL, or | |
312 | in a :fail: or :defer: message in a redirect router, Exim now checks the start | |
313 | of the message for an SMTP error code. This consists of three digits followed | |
314 | by a space, optionally followed by an extended code of the form n.n.n, also | |
315 | followed by a space. If this is the case and the very first digit is the same | |
316 | as the default error code, the code from the message is used instead. If the | |
317 | very first digit is incorrect, a panic error is logged, and the default code is | |
318 | used. This is an incompatible change, but it is not expected to affect many (if | |
319 | any) configurations. It is possible to suppress the use of the supplied code in | |
320 | a redirect router by setting the smtp_error_code option false. In this case, | |
321 | any SMTP code is quietly ignored. | |
322 | ||
323 | ||
47ca6d6c PH |
324 | Exim version 4.61 |
325 | ----------------- | |
326 | ||
8def5aaf PH |
327 | 1. The default number of ACL variables of each type has been increased to 20, |
328 | and it's possible to compile Exim with more. You can safely upgrade to this | |
329 | release if you already have messages on the queue with saved ACL variable | |
330 | values. However, if you downgrade from this release with messages on the queue, | |
331 | any saved ACL values they may have will be lost. | |
332 | ||
333 | 2. The default value for rfc1413_query_timeout has been changed from 30s to 5s. | |
47ca6d6c PH |
334 | |
335 | ||
8857ccfd PH |
336 | Exim version 4.54 |
337 | ----------------- | |
338 | ||
339 | There was a problem with 4.52/TF/02 in that a "name=" option on control= | |
340 | submission terminated at the next slash, thereby not allowing for slashes in | |
341 | the name. This has been changed so that "name=" takes the rest of the string as | |
342 | its data. It must therefore be the last option. | |
343 | ||
344 | ||
f3f0a1f0 PH |
345 | Version 4.53 |
346 | ------------ | |
347 | ||
348 | If you are using the experimental Domain Keys support, you must upgrade to | |
349 | at least libdomainkeys 0.67 in order to run this release of Exim. | |
350 | ||
351 | ||
b5aea5e1 PH |
352 | Version 4.51 |
353 | ------------ | |
354 | ||
c688b954 PH |
355 | 1. The format in which GnuTLS parameters are cached (in the file gnutls-params |
356 | in the spool directory) has been changed. The new format can also be generated | |
b5aea5e1 PH |
357 | externally, so it is now possible to update the values from outside Exim. This |
358 | has been implemented in an upwards, BUT NOT downwards, compatible manner. | |
359 | Upgrading should be seamless: when Exim finds that it cannot understand an | |
360 | existing cache file, it generates new parameters and writes them to the cache | |
361 | in the new format. If, however, you downgrade from 4.51 to a previous release, | |
362 | you MUST delete the gnutls-params file in the spool directory, because the | |
363 | older Exim will not recognize the new format. | |
364 | ||
c688b954 PH |
365 | 2. When doing a callout as part of verifying an address, Exim was not paying |
366 | attention to any local part prefix or suffix that was matched by the router | |
367 | that accepted the address. It now behaves in the same way as it does for | |
368 | delivery: the affixes are removed from the local part unless | |
369 | rcpt_include_affixes is set on the transport. If you have a configuration that | |
370 | uses prefixes or suffixes on addresses that could be used for callouts, and you | |
371 | want the affixes to be retained, you must make sure that rcpt_include_affixes | |
372 | is set on the transport. | |
373 | ||
447d236c PH |
374 | 3. Bounce and delay warning messages no longer contain details of delivery |
375 | errors, except for explicit messages (e.g. generated by :fail:) and SMTP | |
376 | responses from remote hosts. | |
377 | ||
b5aea5e1 | 378 | |
8b5af54d PH |
379 | Version 4.50 |
380 | ------------ | |
381 | ||
4964e932 PH |
382 | The exicyclog script has been updated to use three-digit numbers in rotated log |
383 | files if the maximum number to keep is greater than 99. If you are already | |
384 | keeping more than 99, there will be an incompatible change when you upgrade. | |
385 | You will probably want to rename your old log files to the new form before | |
c3af992c | 386 | running the new exicyclog. |
8b5af54d PH |
387 | |
388 | ||
0f4f2a88 PH |
389 | Version 4.42 |
390 | ------------ | |
391 | ||
392 | RFC 3848 specifies standard names for the "with" phrase in Received: header | |
393 | lines when AUTH and/or TLS are in use. This is the "received protocol" | |
394 | field. Exim used to use "asmtp" for authenticated SMTP, without any | |
395 | indication (in the protocol name) for TLS use. Now it follows the RFC and | |
396 | uses "esmtpa" if the connection is authenticated, "esmtps" if it is | |
397 | encrypted, and "esmtpsa" if it is both encrypted and authenticated. These names | |
398 | appear in log lines as well as in Received: header lines. | |
399 | ||
400 | ||
401 | Version 4.34 | |
402 | ------------ | |
403 | ||
404 | Change 4.31/2 gave problems to data ACLs and local_scan() functions that | |
405 | expected to see a Received: header. I have changed to yet another scheme. The | |
406 | Received: header is now generated after the body is received, but before the | |
407 | ACL or local_scan() is called. After they have run, the timestamp in the | |
408 | Received: header is updated. | |
409 | ||
410 | Thus, change (a) of 4.31/2 has been reversed, but change (b) is still true, | |
411 | which is lucky, since I decided it was a bug fix. | |
412 | ||
413 | ||
414 | Version 4.33 | |
415 | ------------ | |
416 | ||
417 | If an expansion in a condition on a "warn" statement fails because a lookup | |
418 | defers, the "warn" statement is abandoned, and the next ACL statement is | |
419 | processed. Previously this caused the whole ACL to be aborted. | |
420 | ||
421 | ||
422 | Version 4.32 | |
423 | ------------ | |
424 | ||
425 | Change 4.31/2 has been reversed, as it proved contentious. Recipient callout | |
426 | verification now uses <> in the MAIL command by default, as it did before. A | |
427 | new callout option, "use_sender", has been added to request the other | |
428 | behaviour. | |
429 | ||
430 | ||
431 | Version 4.31 | |
432 | ------------ | |
433 | ||
434 | 1. If you compile Exim to use GnuTLS, it now requires the use of release 1.0.0 | |
435 | or greater. The interface to the obsolete 0.8.x releases is no longer | |
436 | supported. There is one externally visible change: the format for the | |
437 | display of Distinguished Names now uses commas as a separator rather than a | |
438 | slash. This is to comply with RFC 2253. | |
439 | ||
440 | 2. When a message is received, the Received: header line is now generated when | |
441 | reception is complete, instead of at the start of reception. For messages | |
442 | that take a long time to come in, this changes the meaning of the timestamp. | |
443 | There are several side-effects of this change: | |
444 | ||
445 | (a) If a message is rejected by a DATA or non-SMTP ACL, or by local_scan(), | |
446 | the logged header lines no longer include the local Received: line, | |
447 | because it has not yet been created. If the message is a non-SMTP one, | |
448 | and the error is processed by sending a message to the sender, the copy | |
449 | of the original message that is returned does not have an added | |
450 | Received: line. | |
451 | ||
452 | (b) When a filter file is tested using -bf, no additional Received: header | |
453 | is added to the test message. After some thought, I decided that this | |
454 | is a bug fix. | |
455 | ||
456 | The contents of $received_for are not affected by this change. This | |
457 | variable still contains the single recipient of a message, copied after | |
458 | addresses have been rewritten, but before local_scan() is run. | |
459 | ||
460 | 2. Recipient callout verification, like sender verification, was using <> in | |
461 | the MAIL FROM command. This isn't really the right thing, since the actual | |
462 | sender may affect whether the remote host accepts the recipient or not. I | |
463 | have changed it to use the actual sender in the callout; this means that | |
464 | the cache record is now keyed on a recipient/sender pair, not just the | |
465 | recipient address. There doesn't seem to be a real danger of callout loops, | |
466 | since a callout by the remote host to check the sender would use <>. | |
467 | ||
468 | ||
469 | Version 4.30 | |
470 | ------------ | |
471 | ||
472 | 1. I have abolished timeout_DNS as an error that can be detected in retry | |
473 | rules, because it has never worked. Despite the fact that it has been | |
474 | documented since at least release 1.62, there was no code to support it. | |
475 | If you have used it in your retry rules, you will now get a warning message | |
476 | to the log and panic log. It is now treated as plain "timeout". | |
477 | ||
478 | 2. After discussion on the mailing list, Exim no longer adds From:, Date:, or | |
479 | Message-Id: header lines to messages that do not originate locally, that is, | |
480 | messages that have an associated sending host address. | |
481 | ||
482 | 3. When looking up a host name from an IP address, Exim now tries the DNS | |
483 | first, and only if that fails does it use gethostbyaddr() (or equivalent). | |
484 | This change was made because on some OS, not all the names are given for | |
485 | addresses with multiple PTR records via the gethostbyaddr() interface. The | |
486 | order of lookup can be changed by setting host_lookup_order. | |
487 | ||
488 | ||
489 | Version 4.23 | |
490 | ------------ | |
491 | ||
492 | 1. The new FIXED_NEVER_USERS build-time option creates a list of "never users" | |
493 | that cannot be overridden. The default in the distributed EDITME is "root". | |
494 | If for some reason you were (against advice) running deliveries as root, you | |
495 | will have to ensure that FIXED_NEVER_USERS is not set in your | |
496 | Local/Makefile. | |
497 | ||
498 | 2. The ${quote: operator now quotes an empty string, which it did not before. | |
499 | ||
500 | 3. Version 4.23 saves the contents of the ACL variables with the message, so | |
501 | that they can be used later. If one of these variables contains a newline, | |
502 | there will be a newline character in the spool that will not be interpreted | |
503 | correctely by a previous version of Exim. (Exim ignores keyed spool file | |
504 | items that it doesn't understand - precisely for this kind of problem - but | |
505 | it expects them all to be on one line.) | |
506 | ||
507 | So the bottom line is: if you have newlines in your ACL variables, you | |
508 | cannot retreat from 4.23. | |
509 | ||
510 | ||
511 | Version 4.21 | |
512 | ------------ | |
513 | ||
514 | 1. The idea of the "warn" ACL verb is that it adds a header or writes to the | |
515 | log only when "message" or "log_message" are set. However, if one of the | |
516 | conditions was an address verification, or a call to a nested ACL, the | |
517 | messages generated by the underlying test were being passed through. This | |
518 | no longer happens. The underlying message is available in $acl_verify_ | |
519 | message for both "message" and "log_message" expansions, so it can be | |
520 | passed through if needed. | |
521 | ||
522 | 2. The way that the $h_ (and $header_) expansions work has been changed by the | |
523 | addition of RFC 2047 decoding. See the main documentation (the NewStuff file | |
524 | until release 4.30, then the manual) for full details. Briefly, there are | |
525 | now three forms: | |
526 | ||
527 | $rh_xxx: and $rheader_xxx: give the original content of the header | |
528 | line(s), with no processing at all. | |
529 | ||
530 | $bh_xxx: and $bheader_xxx: remove leading and trailing white space, and | |
531 | then decode base64 or quoted-printable "words" within the header text, | |
532 | but do not do charset translation. | |
533 | ||
534 | $h_xxx: and $header_xxx: attempt to translate the $bh_ string to a | |
535 | standard character set. | |
536 | ||
537 | If you have previously been using $h_ expansions to access the raw | |
538 | characters, you should change to $rh_ instead. | |
539 | ||
540 | 3. When Exim creates an RFC 2047 encoded word in a header line, it labels it | |
541 | with the default character set from the headers_charset option instead of | |
542 | always using iso-8859-1. | |
543 | ||
544 | 4. If TMPDIR is defined in Local/Makefile (default in src/EDITME is | |
545 | TMPDIR="/tmp"), Exim checks for the presence of an environment variable | |
546 | called TMPDIR, and if it finds it is different, it changes its value. | |
547 | ||
548 | 5. Following a discussion on the list, the rules by which Exim recognises line | |
549 | endings on incoming messages have been changed. The -dropcr and drop_cr | |
550 | options are now no-ops, retained only for backwards compatibility. The | |
551 | following line terminators are recognized: LF CRLF CR. However, special | |
552 | processing applies to CR: | |
553 | ||
554 | (i) The sequence CR . CR does *not* terminate an incoming SMTP message, | |
555 | nor a local message in the state where . is a terminator. | |
556 | ||
557 | (ii) If a bare CR is encountered in a header line, an extra space is added | |
558 | after the line terminator so as not to end the header. The reasoning | |
559 | behind this is that bare CRs in header lines are most likely either | |
560 | to be mistakes, or people trying to play silly games. | |
561 | ||
562 | 6. The code for using daemon_smtp_port, local_interfaces, and the -oX options | |
563 | has been reorganized. It is supposed to be backwards compatible, but it is | |
564 | mentioned here just in case I've screwed up. | |
565 | ||
566 | ||
567 | ||
568 | Version 4.20 | |
569 | ------------ | |
570 | ||
571 | 1. I have tidied and re-organized the code that uses alarm() for imposing time | |
572 | limits on various things. It shouldn't affect anything, but if you notice | |
573 | processes getting stuck, it may be that I've broken something. | |
574 | ||
575 | 2. The "arguments" log selector now also logs the current working directory | |
576 | when Exim is called. | |
577 | ||
578 | 3. An incompatible change has been made to the appendfile transport. This | |
579 | affects the case when it is used for file deliveries that are set up by | |
580 | .forward and filter files. Previously, any settings of the "file" or | |
581 | "directory" options were ignored. It is hoped that, like the address_file | |
582 | transport in the default configuration, these options were never in fact set | |
583 | on such transports, because they were of no use. | |
584 | ||
585 | Now, if either of these options is set, it is used. The path that is passed | |
586 | by the router is in $address_file (this is not new), so it can be used as | |
587 | part of a longer path, or modified in any other way that expansion permits. | |
588 | ||
589 | If neither "file" nor "directory" is set, the behaviour is unchanged. | |
590 | ||
591 | 4. Related to the above: in a filter, if a "save" command specifies a non- | |
592 | absolute path, the value of $home/ is pre-pended. This no longer happens if | |
593 | $home is unset or is set to an empty string. | |
594 | ||
595 | 5. Multiple file deliveries from a filter or .forward file can never be | |
596 | batched; the value of batch_max on the transport is ignored for file | |
597 | deliveries. I'm assuming that nobody ever actually set batch_max on the | |
598 | address_file transport - it would have had odd effects previously. | |
599 | ||
600 | 6. DESTDIR is the more common variable that ROOT for use when installing | |
601 | software under a different root filing system. The Exim install script now | |
602 | recognizes DESTDIR first; if it is not set, ROOT is used. | |
603 | ||
604 | 7. If DESTDIR is set when installing Exim, it no longer prepends its value to | |
605 | the path of the system aliases file that appears in the default | |
606 | configuration (when a default configuration is installed). If an aliases | |
607 | file is actually created, its name *does* use the prefix. | |
608 | ||
609 | ||
610 | Version 4.14 | |
611 | ------------ | |
612 | ||
613 | 1. The default for the maximum number of unknown SMTP commands that Exim will | |
614 | accept before dropping a connection has been reduced from 5 to 3. However, you | |
615 | can now change the value by setting smtp_max_unknown_commands. | |
616 | ||
617 | 2. The ${quote: operator has been changed so that it turns newline and carriage | |
618 | return characters into \n and \r, respectively. | |
619 | ||
620 | 3. The file names used for maildir messages now include the microsecond time | |
621 | fraction as well as the time in seconds, to cope with systems where the process | |
622 | id can be re-used within the same second. The format is now | |
623 | ||
624 | <time>.H<microsec>P<pid>.<host> | |
625 | ||
626 | This should be a compatible change, but is noted here just in case. | |
627 | ||
628 | 4. The rules for creating message ids have changed, to cope with systems where | |
629 | the process id can be re-used within the same second. The format, however, is | |
630 | unchanged, so this should not cause any problems, except as noted in the next | |
631 | item. | |
632 | ||
633 | 5. The maximum value for localhost_number has been reduced from 255 to 16, in | |
634 | order to implement the new message id rules. For operating systems that have | |
635 | case-insensitive file systems (Cygwin and Darwin), the limit is 10. | |
636 | ||
637 | 6. verify = header_syntax was allowing unqualified addresses in all cases. Now | |
638 | it allows them only for locally generated messages and from hosts that match | |
639 | sender_unqualified_hosts or recipient_unqualified_hosts, respectively. | |
640 | ||
641 | 7. For reasons lost in the mists of time, when a pipe transport was run, the | |
642 | environment variable MESSAGE_ID was set to the message ID preceded by 'E' (the | |
643 | form used in Message-ID: header lines). The 'E' has been removed. | |
644 | ||
645 | ||
646 | Version 4.11 | |
647 | ------------ | |
648 | ||
649 | 1. The handling of lines in the configuration file has changed. Previously, | |
650 | macro expansion was applied to logical lines, after continuations had been | |
651 | joined on. This meant that it could not be used in .include lines, which are | |
652 | handled as physical rather than logical lines. Macro expansion is now done on | |
653 | physical lines rather than logical lines. This means there are two | |
654 | incompatibilities: | |
655 | ||
656 | (a) A macro that expands to # to turn a line into a comment now applies only | |
657 | to the physical line where it appears. Previously, it would have caused | |
658 | any following continuations also to be ignored. | |
659 | ||
660 | (b) A macro name can no longer be split over the boundary between a line and | |
661 | its continuation. Actually, this is more of a bug fix. :-) | |
662 | ||
663 | 2. The -D command line option must now all be within one command line item. | |
664 | This makes it possible to use -D to set a macro to the empty string by commands | |
665 | such as | |
666 | ||
667 | exim -DABC ... | |
668 | exim -DABC= ... | |
669 | ||
670 | Previously, these items would have moved on to the next item on the command | |
671 | line. To include spaces in a macro definition item, quotes must be used, in | |
672 | which case you can also have spaces after -D and surrounding the equals. For | |
673 | example: | |
674 | ||
675 | exim '-D ABC = something' ... | |
676 | ||
677 | 3. The way that addresses that redirect to themselves are handled has been | |
678 | changed, in order to fix an obscure bug. This should not cause any problems | |
679 | except in the case of wanting to go back from a 4.11 (or later) release to an | |
680 | earlier release. If there are undelivered messages on the spool that contain | |
681 | addresses which redirect to themselves, and the redirected addresses have | |
682 | already been delivered, you might get a duplicate delivery if you revert to an | |
683 | earlier Exim. | |
684 | ||
685 | 4. The default way of looking up IP addresses for hosts in the manualroute and | |
686 | queryprogram routers has been changed. If "byname" or "bydns" is explicitly | |
687 | specified, there is no change, but if no method is specified, Exim now behaves | |
688 | as follows: | |
689 | ||
690 | First, a DNS lookup is done. If this yields anything other than | |
691 | HOST_NOT_FOUND, that result is used. Otherwise, Exim goes on to try a call to | |
692 | getipnodebyname() (or gethostbyname() on older systems) and the result of the | |
693 | lookup is the result of that call. | |
694 | ||
695 | This change has been made because it has been discovered that on some systems, | |
696 | if a DNS lookup called via getipnodebyname() times out, HOST_NOT_FOUND is | |
697 | returned instead of TRY_AGAIN. Thus, it is safest to try a DNS lookup directly | |
698 | first, and only if that gives a definite "no such host" to try the local | |
699 | function. | |
700 | ||
701 | 5. In fixing the minor security problem with pid_file_path, I have removed some | |
702 | backwards-compatible (undocumented) code which was present to ease conversion | |
703 | from Exim 3. In Exim 4, pid_file_path is a literal; in Exim 3 it was allowed to | |
704 | contain "%s", which was replaced by the port number for daemons listening on | |
705 | non-standard ports. In Exim 4, such daemons do not write a pid file. The | |
706 | backwards compatibility feature was to replace "%s" by nothing if it occurred | |
707 | in an Exim 4 setting of pid_file_path. The bug was in this code. I have solved | |
708 | the problem by removing the backwards compatibility feature. Thus, if you still | |
709 | have "%s" somewhere in a setting of pid_file_path, you should remove it. | |
710 | ||
711 | 6. There has been an extension to lsearch files. The keys in these files may | |
712 | now be quoted in order to allow for whitespace and colons in them. This means | |
713 | that if you were previously using keys that began with a doublequote, you will | |
714 | now have to wrap them with extra quotes and escape the internal quotes. The | |
715 | possibility that anybody is actually doing this seems extremely remote, but it | |
716 | is documented just in case. | |
717 | ||
718 | ||
719 | Version 4.10 | |
720 | ------------ | |
721 | ||
722 | The build-time parameter EXIWHAT_KILL_ARG has been renamed EXIWHAT_KILL_SIGNAL | |
723 | to better reflect its function. The OS-specific files have been updated. Only | |
724 | if you have explicitly set this in your Makefile (highly unlikely) do you need | |
725 | to change anything. | |
726 | ||
727 | **** |