Change 4.51/PH/05 wasn't implemented quite correctly. I think I've now
[exim.git] / doc / doc-txt / ChangeLog
1 $Cambridge: exim/doc/doc-txt/ChangeLog,v 1.111 2005/04/05 15:47:50 ph10 Exp $
2
3 Change log file for Exim from version 4.21
4 -------------------------------------------
5
6
7 Exim version 4.51
8 -----------------
9
10 TK/01 Added Yahoo DomainKeys support via libdomainkeys. See
11 doc/experimental-spec.txt for details. (http://domainkeys.sf.net)
12
13 TK/02 Fix ACL "control" statement not being available in MIME ACL.
14
15 TK/03 Fix ACL "regex" condition not being available in MIME ACL.
16
17 PH/01 Installed a patch from the Sieve maintainer that allows -bf to be used
18 to test Sieve filters that use "vacation".
19
20 PH/02 Installed a slightly modified version of Nikos Mavrogiannopoulos' patch
21 that changes the way the GnuTLS parameters are stored in the cache file.
22 The new format can be generated externally. For backward compatibility,
23 if the data in the cache doesn't make sense, Exim assumes it has read an
24 old-format file, and it generates new data and writes a new file. This
25 means that you can't go back to an older release without removing the
26 file.
27
28 PH/03 A redirect router that has both "unseen" and "one_time" set does not
29 work if there are any delivery delays because "one_time" forces the
30 parent to be marked "delivered", so its unseen clone is never tried
31 again. For this reason, Exim now forbids the simultaneous setting of
32 these two options.
33
34 PH/04 Change 4.11/85 fixed an obscure bug concerned with addresses that are
35 redirected to themselves ("homonym" addresses). Read the long ChangeLog
36 entry if you want to know the details. The fix, however, neglected to
37 consider the case when local delivery batching is involved. The test for
38 "previously delivered" was not happening when checking to see if an
39 address could be batched with a previous (undelivered) one; under
40 certain circumstances this could lead to multiple deliveries to the same
41 address.
42
43 PH/05 Renamed the macro SOCKLEN_T as EXIM_SOCKLEN_T because AIX uses SOCKLEN_T
44 in its include files, and this causes problems building Exim.
45
46 PH/06 A number of "verify =" ACL conditions have no options (e.g. verify =
47 header_syntax) but Exim was just ignoring anything given after a slash.
48 In particular, this caused confusion with an attempt to use "verify =
49 reverse_host_lookup/defer_ok". An error is now given when options are
50 supplied for verify items that do not have them. (Maybe reverse_host_
51 lookup should have a defer_ok option, but that's a different point.)
52
53 PH/07 Increase the size of the buffer for incoming SMTP commands from 512 (as
54 defined by RFC 821) to 2048, because there were problems with some AUTH
55 commands, and RFC 1869 says the size should be increased for extended
56 SMTP commands that take arguments.
57
58 PH/08 Added ${dlfunc dynamically loaded function for expansion (code from Tony
59 Finch).
60
61 PH/09 Previously, an attempt to use ${perl when it wasn't compiled gave an
62 "unknown" error; now it says that the functionality isn't in the binary.
63
64 PH/10 Added a nasty fudge to try to recognize and flatten LDAP passwords in
65 an address' error message when a string expansion fails (syntax or
66 whatever). Otherwise not only does the password appear in the log, it may
67 also be put in a bounce message.
68
69 PH/11 Installed exipick version 20050225.0 from John Jetmore.
70
71 PH/12 If the last host in a fallback_hosts list was multihomed, only the first
72 of its addresses was ever tried. (Bugzilla bug #2.)
73
74 PH/13 If "headers_add" in a transport didn't end in a newline, Exim printed
75 the result incorrectly in the debug output. (It correctly added a newline
76 to what was transported.)
77
78 TF/01 Added $received_time.
79
80 PH/14 Modified the default configuration to add an acl_smtp_data ACL, with
81 commented out examples of how to interface to a virus scanner and to
82 SpamAssassin. Also added commented examples of av_scanner and
83 spamd_address settings.
84
85 PH/15 Further to TK/02 and TK/03 above, tidied up the tables of what conditions
86 and controls are allowed in which ACLs. There were a couple of minor
87 errors. Some of the entries in the conditions table (which is a table of
88 where they are NOT allowed) were getting very unwieldy; rewrote them as a
89 negation of where the condition IS allowed.
90
91 PH/16 Installed updated OS/os.c-cygwin from the Cygwin maintainer.
92
93 PH/17 The API for radiusclient changed at release 0.4.0. Unfortunately, the
94 header file does not have a version number, so I've had to invent a new
95 value for RADIUS_LIB_TYPE, namely "RADIUSCLIENTNEW" to request the new
96 API. The code is untested by me (my Linux distribution still has 0.3.2 of
97 radiusclient), but it was contributed by a Radius user.
98
99 PH/18 Installed Lars Mainka's patch for the support of CRL collections in
100 files or directories, for OpenSSL.
101
102 PH/19 When an Exim process that is running as root has to create an Exim log
103 file, it does so in a subprocess that runs as exim:exim so as to get the
104 ownership right at creation (otherwise, other Exim processes might see
105 the file with the wrong ownership). There was no test for failure of this
106 fork() call, which would lead to the process getting stuck as it waited
107 for a non-existent subprocess. Forks do occasionally fail when resources
108 run out. I reviewed all the other calls to fork(); they all seem to check
109 for failure.
110
111 PH/20 When checking for unexpected SMTP input at connect time (before writing
112 the banner), Exim was not dealing correctly with a non-positive return
113 from the read() function. If the client had disconnected by this time,
114 the result was a log entry for a synchronization error with an empty
115 string after "input=" when read() returned zero. If read() returned -1
116 (an event I could not check), uninitialized data bytes were printed.
117 There were reports of junk text (parts of files, etc) appearing after
118 "input=".
119
120 PH/21 Added acl_not_smtp_mime to allow for MIME scanning for non-SMTP messages.
121
122 PH/22 Added support for macro redefinition, and (re)definition in between
123 driver and ACL definitions.
124
125 PH/23 The cyrus_sasl authenticator was expanding server_hostname, but then
126 forgetting to use the resulting value; it was using the unexpanded value.
127
128 PH/24 The cyrus_sasl authenticator was advertising mechanisms for which it
129 hadn't been configured. The fix is from Juergen Kreileder, who
130 understands it better than I do:
131
132 "Here's what I see happening with three configured cyrus_sasl
133 authenticators configured (plain, login, cram-md5):
134
135 On startup auth_cyrus_sasl_init() gets called for each of these.
136 This means three calls to sasl_listmech() without a specified mech_list.
137 => SASL tests which mechs of all available mechs actually work
138 => three warnings about OTP not working
139 => the returned list contains: plain, login, cram-md5, digest-md5, ...
140
141 With the patch, sasl_listmech() also gets called three times. But now
142 SASL's mech_list option is set to the server_mech specified in the the
143 authenticator. Or in other words, the answer from sasl_listmech()
144 gets limited to just the mech you're testing for (which is different
145 for each call.)
146 => the return list contains just 'plain' or 'login', 'cram-md5' or
147 nothing depending on the value of ob->server_mech.
148
149 I've just tested the patch: Authentication still works fine,
150 unavailable mechs specified in the exim configuration are still
151 caught, and the auth.log warnings about OTP are gone."
152
153
154 A note about Exim versions 4.44 and 4.50
155 ----------------------------------------
156
157 Exim 4.50 was meant to be the next release after 4.43. It contains a lot of
158 changes of various kinds. As a consequence, a big documentation update was
159 needed. This delayed the release for rather longer than seemed good, especially
160 in the light of a couple of (minor) security issues. Therefore, the changes
161 that fixed bugs were backported into 4.43, to create a 4.44 maintenance
162 release. So 4.44 and 4.50 are in effect two different branches that both start
163 from 4.43.
164
165 I have left the 4.50 change log unchanged; it contains all the changes since
166 4.43. The change log for 4.44 is below; many of its items are identical to
167 those for 4.50. This seems to be the most sensible way to preserve the
168 historical information.
169
170
171 Exim version 4.50
172 -----------------
173
174 1. Minor wording change to the doc/README.SIEVE file.
175
176 2. Change 4.43/35 introduced a bug: if quota_filecount was set, the
177 computation of the current number of files was incorrect.
178
179 3. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
180 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
181 place.
182
183 4. Give more explanation in the error message when the command for a transport
184 filter fails to execute.
185
186 5. There are several places where Exim runs a non-Exim command in a
187 subprocess. The SIGUSR1 signal should be disabled for these processes. This
188 was being done only for the command run by the queryprogram router. It is
189 now done for all such subprocesses. The other cases are: ${run, transport
190 filters, and the commands run by the lmtp and pipe transports.
191
192 6. Added CONFIGURE_GROUP build-time option.
193
194 7. Some older OS have a limit of 256 on the maximum number of file
195 descriptors. Exim was using setrlimit() to set 1000 as a large value
196 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
197 systems. I've change it so that if it can't get 1000, it tries for 256.
198
199 8. "control=submission" was allowed, but had no effect, in a DATA ACL. This
200 was an oversight, and furthermore, ever since the addition of extra
201 controls (e.g. 4.43/32), the checks on when to allow different forms of
202 "control" were broken. There should now be diagnostics for all cases when a
203 control that does not make sense is encountered.
204
205 9. Added the /retain_sender option to "control=submission".
206
207 10. $recipients is now available in the predata ACL (oversight).
208
209 11. Tidy the search cache before the fork to do a delivery from a message
210 received from the command line. Otherwise the child will trigger a lookup
211 failure and thereby defer the delivery if it tries to use (for example) a
212 cached ldap connection that the parent has called unbind on.
213
214 12. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
215 of $address_data from the recipient verification was clobbered by the
216 sender verification.
217
218 13. The value of address_data from a sender verification is now available in
219 $sender_address_data in subsequent conditions in the ACL statement.
220
221 14. Added forbid_sieve_filter and forbid_exim_filter to the redirect router.
222
223 15. Added a new option "connect=<time>" to callout options, to set a different
224 connection timeout.
225
226 16. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
227 was its contents. (It was OK if the option was not defined at all.)
228
229 17. A "Completed" log line is now written for messages that are removed from
230 the spool by the -Mrm option.
231
232 18. New variables $sender_verify_failure and $recipient_verify_failure contain
233 information about exactly what failed.
234
235 19. Added -dd to debug only the daemon process.
236
237 20. Incorporated Michael Haardt's patch to ldap.c for improving the way it
238 handles timeouts, both on the server side and network timeouts. Renamed the
239 CONNECT parameter as NETTIMEOUT (but kept the old name for compatibility).
240
241 21. The rare case of EHLO->STARTTLS->HELO was setting the protocol to "smtp".
242 It is now set to "smtps".
243
244 22. $host_address is now set to the target address during the checking of
245 ignore_target_hosts.
246
247 23. When checking ignore_target_hosts for an ipliteral router, no host name was
248 being passed; this would have caused $sender_host_name to have been used if
249 matching the list had actually called for a host name (not very likely,
250 since this list is usually IP addresses). A host name is now passed as
251 "[x.x.x.x]".
252
253 24. Changed the calls that set up the SIGCHLD handler in the daemon to use the
254 code that specifies a non-restarting handler (typically sigaction() in
255 modern systems) in an attempt to fix a rare and obscure crash bug.
256
257 25. Narrowed the window for a race in the daemon that could cause it to ignore
258 SIGCHLD signals. This is not a major problem, because they are used only to
259 wake it up if nothing else does.
260
261 26. A malformed maildirsize file could cause Exim to calculate negative values
262 for the mailbox size or file count. Odd effects could occur as a result.
263 The maildirsize information is now recalculated if the size or filecount
264 end up negative.
265
266 27. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
267 support for a long time. Removed HAVE_SYS_VFS_H.
268
269 28. Installed the latest version of exipick from John Jetmore.
270
271 29. In an address list, if the pattern was not a regular expression, an empty
272 subject address (from a bounce message) matched only if the pattern was an
273 empty string. Non-empty patterns were not even tested. This was the wrong
274 because it is perfectly reasonable to use an empty address as part of a
275 database query. An empty address is now tested by patterns that are
276 lookups. However, all the other forms of pattern expect the subject to
277 contain a local part and a domain, and therefore, for them, an empty
278 address still always fails if the pattern is not itself empty.
279
280 30. Exim went into a mad DNS loop when attempting to do a callout where the
281 host was specified on an smtp transport, and looking it up yielded more
282 than one IP address.
283
284 31. Re-factored the code for checking spool and log partition space into a
285 function that finds that data and another that does the check. The former
286 is then used to implement four new variables: $spool_space, $log_space,
287 $spool_inodes, and $log_inodes.
288
289 32. The RFC2047 encoding function was originally intended for short strings
290 such as real names; it was not keeping to the 75-character limit for
291 encoded words that the RFC imposes. It now respects the limit, and
292 generates multiple encoded words if necessary. To be on the safe side, I
293 have increased the buffer size for the ${rfc2047: expansion operator from
294 1024 to 2048 bytes.
295
296 33. It is now permitted to omit both strings after an "if" condition; if the
297 condition is true, the result is "true". As before, when the second string
298 is omitted, a false condition yields an empty string. This makes it less
299 cumbersome to write custom ACL and router conditions.
300
301 34. Failure to deliver a bounce message always caused it to be frozen, even if
302 there was an errors_to setting on the router. The errors_to setting is now
303 respected.
304
305 35. If an IPv6 address is given for -bh or -bhc, it is now converted to the
306 canonical form (fully expanded) before being placed in
307 $sender_host_address.
308
309 36. The table in the code that translates DNS record types into text (T_A to
310 "A" for instance) was missing entries for NS and CNAME. It is just possible
311 that this could have caused confusion if both these types were looked up
312 for the same domain, because the text type is used as part of Exim's
313 per-process caching. But the chance of anyone hitting this buglet seems
314 very small.
315
316 37. The dnsdb lookup has been extended in a number of ways.
317
318 (1) There is a new type, "zns", which walks up the domain tree until it
319 finds some nameserver records. It should be used with care.
320
321 (2) There is a new type, "mxh", which is like "mx" except that it returns
322 just the host names, not the priorities.
323
324 (3) It is now possible to give a list of domains (or IP addresses) to be
325 looked up. The behaviour when one of the lookups defers can be
326 controlled by a keyword.
327
328 (4) It is now possible to specify the separator character for use when
329 multiple records are returned.
330
331 38. The dnslists ACL condition has been extended: it is now possible to supply
332 a list of IP addresses and/or domains to be looked up in a particular DNS
333 domain.
334
335 39. Added log_selector=+queue_time_overall.
336
337 40. When running the queue in the test harness, wait just a tad after forking a
338 delivery process, to get repeatability of debugging output.
339
340 41. Include certificate and key file names in error message when GnuTLS fails
341 to set them up, because the GnuTLS error message doesn't include the name
342 of the failing file when there is a problem reading it.
343
344 42. Allow both -bf and -bF in the same test run.
345
346 43. Did the same fix as 41 above for OpenSSL, which had the same infelicity.
347
348 44. The "Exiscan patch" is now merged into the mainline Exim source.
349
350 45. Sometimes the final signoff response after QUIT could fail to get
351 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
352 < 0 before doing a fflush(). This bug looks as though it goes back to the
353 introduction of TLS in release 3.20, but "sometimes" must have been rare
354 because the tests only now provoked it.
355
356 46. Reset the locale to "C" after calling embedded Perl, in case it was changed
357 (this can affect the format of dates).
358
359 47. exim_tidydb, when checking for the continued existence of a message for
360 which it has found a message-specific retry record, was not finding
361 messages that were in split spool directories. Consequently, it was
362 deleting retry records that should have stayed in existence.
363
364 48. Steve fixed some bugs in eximstats.
365
366 49. The SPA authentication driver was not abandoning authentication and moving
367 on to the next authenticator when an expansion was forced to fail,
368 contradicting the general specification for all authenticators. Instead it
369 was generating a temporary error. It now behaves as specified.
370
371 50. The default ordering of permitted cipher suites for GnuTLS was pessimal
372 (the order specifies the preference for clients). The order is now AES256,
373 AES128, 3DES, ARCFOUR128.
374
375 51. Small patch to Sieve code - explicitly set From: when generating an
376 autoreply.
377
378 52. Exim crashed if a remote delivery caused a very long error message to be
379 recorded - for instance if somebody sent an entire SpamAssassin report back
380 as a large number of 550 error lines. This bug was coincidentally fixed by
381 increasing the size of one of Exim's internal buffers (big_buffer) that
382 happened as part of the Exiscan merge. However, to be on the safe side, I
383 have made the code more robust (and fixed the comments that describe what
384 is going on).
385
386 53. Now that there can be additional text after "Completed" in log lines (if
387 the queue_time_overall log selector is set), a one-byte patch to exigrep
388 was needed to allow it to recognize "Completed" as not the last thing in
389 the line.
390
391 54. The LDAP lookup was not handling a return of LDAP_RES_SEARCH_REFERENCE. A
392 patch that reportedly fixes this has been added. I am not expert enough to
393 create a test for it. This is what the patch creator wrote:
394
395 "I found a little strange behaviour of ldap code when working with
396 Windows 2003 AD Domain, where users was placed in more than one
397 Organization Units. When I tried to give exim partial DN, the exit code
398 of ldap_search was unknown to exim because of LDAP_RES_SEARCH_REFERENCE.
399 But simultaneously result of request was absolutely normal ldap result,
400 so I produce this patch..."
401
402 Later: it seems that not all versions of LDAP support LDAP_RES_SEARCH_
403 REFERENCE, so I have modified the code to exclude the patch when that macro
404 is not defined.
405
406 55. Some experimental protocols are using DNS PTR records for new purposes. The
407 keys for these records are domain names, not reversed IP addresses. The
408 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
409 leaves it alone. Component reversal etc. now happens only for IP addresses.
410 CAN-2005-0021
411
412 56. Improve error message when ldap_search() fails in OpenLDAP or Solaris LDAP.
413
414 57. Double the size of the debug message buffer (to 2048) so that more of very
415 long debug lines gets shown.
416
417 58. The exicyclog utility now does better if the number of log files to keep
418 exceeds 99. In this case, it numbers them 001, 002 ... instead of 01, 02...
419
420 59. Two changes related to the smtp_active_hostname option:
421
422 (1) $smtp_active_hostname is now available as a variable.
423 (2) The default for smtp_banner uses $smtp_active_hostname instead
424 of $primary_hostname.
425
426 60. The host_aton() function is supposed to be passed a string that is known
427 to be a valid IP address. However, in the case of IPv6 addresses, it was
428 not checking this. This is a hostage to fortune. Exim now panics and dies
429 if the condition is not met. A case was found where this could be provoked
430 from a dnsdb PTR lookup with an IPv6 address that had more than 8
431 components; fortuitously, this particular loophole had already been fixed
432 by change 4.50/55 above.
433
434 If there are any other similar loopholes, the new check in host_aton()
435 itself should stop them being exploited. The report I received stated that
436 data on the command line could provoke the exploit when Exim was running as
437 exim, but did not say which command line option was involved. All I could
438 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
439 running as the user.
440 CAN-2005-0021
441
442 61. There was a buffer overflow vulnerability in the SPA authentication code
443 (which came originally from the Samba project). I have added a test to the
444 spa_base64_to_bits() function which I hope fixes it.
445 CAN-2005-0022
446
447 62. Configuration update for GNU/Hurd and variations. Updated Makefile-GNU and
448 os.h-GNU, and added configuration files for GNUkFreeBSD and GNUkNetBSD.
449
450 63. The daemon start-up calls getloadavg() while still root for those OS that
451 need the first call to be done as root, but it missed one case: when
452 deliver_queue_load_max is set with deliver_drop_privilege. This is
453 necessary for the benefit of the queue runner, because there is no re-exec
454 when deliver_drop_privilege is set.
455
456 64. A call to exiwhat cut short delays set up by "delay" modifiers in ACLs.
457 This has been fixed.
458
459 65. Caching of lookup data for "hosts =" ACL conditions, when a named host list
460 was in use, was not putting the data itself into the right store pool;
461 consequently, it could be overwritten for a subsequent message in the same
462 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
463 the caching.)
464
465 66. Added hosts_max_try_hardlimit to the smtp transport, default 50.
466
467 67. The string_is_ip_address() function returns 0, 4, or 6, for "no an IP
468 address", "IPv4 address", and "IPv6 address", respectively. Some calls of
469 the function were treating the return as a boolean value, which happened to
470 work because 0=false and not-0=true, but is not correct code.
471
472 68. The host_aton() function was not handling scoped IPv6 addresses (those
473 with, for example, "%eth0" on the end) correctly.
474
475 69. Fixed some compiler warnings in acl.c for the bitmaps specified with
476 negated items (that is, ~something) in unsigned ints. Some compilers
477 apparently mutter when there is no cast.
478
479 70. If an address verification called from an ACL failed, and did not produce a
480 user-specific message (i.e. there was only a "system" message), nothing was
481 put in $acl_verify_message. In this situation, it now puts the system
482 message there.
483
484 71. Change 4.23/11 added synchronization checking at the start of an SMTP
485 session; change 4.31/43 added the unwanted input to the log line - except
486 that it did not do this in the start of session case. It now does.
487
488 72. After a timeout in a callout SMTP session, Exim still sent a QUIT command.
489 This is wrong and can cause the other end to generate a synchronization
490 error if it is another Exim or anything else that does the synchronization
491 check. A QUIT command is no longer sent after a timeout.
492
493 73. $host_lookup_deferred has been added, to make it easier to detect DEFERs
494 during host lookups.
495
496 74. The defer_ok option of callout verification was not working if it was used
497 when verifying addresses in header lines, that is, for this case:
498
499 verify = header_sender/callout=defer_ok
500
501 75. A backgrounded daemon closed stdin/stdout/stderr on entry; this meant that
502 those file descriptors could be used for SMTP connections. If anything
503 wrote to stderr (the example that came up was "warn" in embedded Perl), it
504 could be sent to the SMTP client, causing chaos. The daemon now opens
505 stdin, stdout, and stderr to /dev/null when it puts itself into the
506 background.
507
508 76. Arrange for output from Perl's "warn" command to be written to Exim's main
509 log by default. The user can override this with suitable Perl magic.
510
511 77. The use of log_message on a "discard" ACL verb, which is supposed to add to
512 the log message when discard triggers, was not working for the DATA ACL or
513 for the non-SMTP ACL.
514
515 78. Error message wording change in sieve.c.
516
517 79. If smtp_accept_max_per_host was set, the number of connections could be
518 restricted to fewer than expected, because the daemon was trying to set up
519 a new connection before checking whether the processes handling previous
520 connections had finished. The check for completed processes is now done
521 earlier. On busy systems, this bug wouldn't be noticed because something
522 else would have woken the daemon, and it would have reaped the completed
523 process earlier.
524
525 80. If a message was submitted locally by a user whose login name contained one
526 or more spaces (ugh!), the spool file that Exim wrote was not re-readable.
527 It caused a spool format error. I have fixed the spool reading code. A
528 related problem was that the "from" clause in the Received: line became
529 illegal because of the space(s). It is now covered by ${quote_local_part.
530
531 81. Included the latest eximstats from Steve (adds average sizes to HTML Top
532 tables).
533
534 82. Updated OS/Makefile-AIX as per message from Mike Meredith.
535
536 83. Patch from Sieve maintainer to fix unterminated string problem in
537 "vacation" handling.
538
539 84. Some minor changes to the Linux configuration files to help with other
540 OS variants using glibc.
541
542 85. One more patch for Sieve to update vacation handling to latest spec.
543
544
545 ----------------------------------------------------
546 See the note above about the 4.44 and 4.50 releases.
547 ----------------------------------------------------
548
549
550 Exim version 4.44
551 -----------------
552
553 1. Change 4.43/35 introduced a bug that caused file counts to be
554 incorrectly computed when quota_filecount was set in an appendfile
555 transport
556
557 2. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
558 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
559 place.
560
561 3. Give more explanation in the error message when the command for a transport
562 filter fails to execute.
563
564 4. There are several places where Exim runs a non-Exim command in a
565 subprocess. The SIGUSR1 signal should be disabled for these processes. This
566 was being done only for the command run by the queryprogram router. It is
567 now done for all such subprocesses. The other cases are: ${run, transport
568 filters, and the commands run by the lmtp and pipe transports.
569
570 5. Some older OS have a limit of 256 on the maximum number of file
571 descriptors. Exim was using setrlimit() to set 1000 as a large value
572 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
573 systems. I've change it so that if it can't get 1000, it tries for 256.
574
575 6. "control=submission" was allowed, but had no effect, in a DATA ACL. This
576 was an oversight, and furthermore, ever since the addition of extra
577 controls (e.g. 4.43/32), the checks on when to allow different forms of
578 "control" were broken. There should now be diagnostics for all cases when a
579 control that does not make sense is encountered.
580
581 7. $recipients is now available in the predata ACL (oversight).
582
583 8. Tidy the search cache before the fork to do a delivery from a message
584 received from the command line. Otherwise the child will trigger a lookup
585 failure and thereby defer the delivery if it tries to use (for example) a
586 cached ldap connection that the parent has called unbind on.
587
588 9. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
589 of $address_data from the recipient verification was clobbered by the
590 sender verification.
591
592 10. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
593 was its contents. (It was OK if the option was not defined at all.)
594
595 11. A "Completed" log line is now written for messages that are removed from
596 the spool by the -Mrm option.
597
598 12. $host_address is now set to the target address during the checking of
599 ignore_target_hosts.
600
601 13. When checking ignore_target_hosts for an ipliteral router, no host name was
602 being passed; this would have caused $sender_host_name to have been used if
603 matching the list had actually called for a host name (not very likely,
604 since this list is usually IP addresses). A host name is now passed as
605 "[x.x.x.x]".
606
607 14. Changed the calls that set up the SIGCHLD handler in the daemon to use the
608 code that specifies a non-restarting handler (typically sigaction() in
609 modern systems) in an attempt to fix a rare and obscure crash bug.
610
611 15. Narrowed the window for a race in the daemon that could cause it to ignore
612 SIGCHLD signals. This is not a major problem, because they are used only to
613 wake it up if nothing else does.
614
615 16. A malformed maildirsize file could cause Exim to calculate negative values
616 for the mailbox size or file count. Odd effects could occur as a result.
617 The maildirsize information is now recalculated if the size or filecount
618 end up negative.
619
620 17. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
621 support for a long time. Removed HAVE_SYS_VFS_H.
622
623 18. Updated exipick to current release from John Jetmore.
624
625 19. Allow an empty sender to be matched against a lookup in an address list.
626 Previously the only cases considered were a regular expression, or an
627 empty pattern.
628
629 20. Exim went into a mad DNS lookup loop when doing a callout where the
630 host was specified on the transport, if the DNS lookup yielded more than
631 one IP address.
632
633 21. The RFC2047 encoding function was originally intended for short strings
634 such as real names; it was not keeping to the 75-character limit for
635 encoded words that the RFC imposes. It now respects the limit, and
636 generates multiple encoded words if necessary. To be on the safe side, I
637 have increased the buffer size for the ${rfc2047: expansion operator from
638 1024 to 2048 bytes.
639
640 22. Failure to deliver a bounce message always caused it to be frozen, even if
641 there was an errors_to setting on the router. The errors_to setting is now
642 respected.
643
644 23. If an IPv6 address is given for -bh or -bhc, it is now converted to the
645 canonical form (fully expanded) before being placed in
646 $sender_host_address.
647
648 24. Updated eximstats to version 1.33
649
650 25. Include certificate and key file names in error message when GnuTLS fails
651 to set them up, because the GnuTLS error message doesn't include the name
652 of the failing file when there is a problem reading it.
653
654 26. Expand error message when OpenSSL has problems setting up cert/key files.
655 As per change 25.
656
657 27. Reset the locale to "C" after calling embedded Perl, in case it was changed
658 (this can affect the format of dates).
659
660 28. exim_tidydb, when checking for the continued existence of a message for
661 which it has found a message-specific retry record, was not finding
662 messages that were in split spool directories. Consequently, it was
663 deleting retry records that should have stayed in existence.
664
665 29. eximstats updated to version 1.35
666 1.34 - allow eximstats to parse syslog lines as well as mainlog lines
667 1.35 - bugfix such that pie charts by volume are generated correctly
668
669 30. The SPA authentication driver was not abandoning authentication and moving
670 on to the next authenticator when an expansion was forced to fail,
671 contradicting the general specification for all authenticators. Instead it
672 was generating a temporary error. It now behaves as specified.
673
674 31. The default ordering of permitted cipher suites for GnuTLS was pessimal
675 (the order specifies the preference for clients). The order is now AES256,
676 AES128, 3DES, ARCFOUR128.
677
678 31. Small patch to Sieve code - explicitly set From: when generating an
679 autoreply.
680
681 32. Exim crashed if a remote delivery caused a very long error message to be
682 recorded - for instance if somebody sent an entire SpamAssassin report back
683 as a large number of 550 error lines. This bug was coincidentally fixed by
684 increasing the size of one of Exim's internal buffers (big_buffer) that
685 happened as part of the Exiscan merge. However, to be on the safe side, I
686 have made the code more robust (and fixed the comments that describe what
687 is going on).
688
689 33. Some experimental protocols are using DNS PTR records for new purposes. The
690 keys for these records are domain names, not reversed IP addresses. The
691 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
692 leaves it alone. Component reversal etc. now happens only for IP addresses.
693 CAN-2005-0021
694
695 34. The host_aton() function is supposed to be passed a string that is known
696 to be a valid IP address. However, in the case of IPv6 addresses, it was
697 not checking this. This is a hostage to fortune. Exim now panics and dies
698 if the condition is not met. A case was found where this could be provoked
699 from a dnsdb PTR lookup with an IPv6 address that had more than 8
700 components; fortuitously, this particular loophole had already been fixed
701 by change 4.50/55 or 4.44/33 above.
702
703 If there are any other similar loopholes, the new check in host_aton()
704 itself should stop them being exploited. The report I received stated that
705 data on the command line could provoke the exploit when Exim was running as
706 exim, but did not say which command line option was involved. All I could
707 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
708 running as the user.
709 CAN-2005-0021
710
711 35. There was a buffer overflow vulnerability in the SPA authentication code
712 (which came originally from the Samba project). I have added a test to the
713 spa_base64_to_bits() function which I hope fixes it.
714 CAN-2005-0022
715
716 36. The daemon start-up calls getloadavg() while still root for those OS that
717 need the first call to be done as root, but it missed one case: when
718 deliver_queue_load_max is set with deliver_drop_privilege. This is
719 necessary for the benefit of the queue runner, because there is no re-exec
720 when deliver_drop_privilege is set.
721
722 37. Caching of lookup data for "hosts =" ACL conditions, when a named host list
723 was in use, was not putting the data itself into the right store pool;
724 consequently, it could be overwritten for a subsequent message in the same
725 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
726 the caching.)
727
728 38. Sometimes the final signoff response after QUIT could fail to get
729 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
730 < 0 before doing a fflush(). This bug looks as though it goes back to the
731 introduction of TLS in release 3.20, but "sometimes" must have been rare
732 because the tests only now provoked it.
733
734
735 Exim version 4.43
736 -----------------
737
738 1. Fixed a longstanding but relatively impotent bug: a long time ago, before
739 PIPELINING, the function smtp_write_command() used to return TRUE or FALSE.
740 Now it returns an integer. A number of calls were still expecting a T/F
741 return. Fortuitously, in all cases, the tests worked in OK situations,
742 which is the norm. However, things would have gone wrong on any write
743 failures on the smtp file descriptor. This function is used when sending
744 messages over SMTP and also when doing verify callouts.
745
746 2. When Exim is called to do synchronous delivery of a locally submitted
747 message (the -odf or -odi options), it no longer closes stderr before doing
748 the delivery.
749
750 3. Implemented the mua_wrapper option.
751
752 4. Implemented mx_fail_domains and srv_fail_domains for the dnslookup router.
753
754 5. Implemented the functions header_remove(), header_testname(),
755 header_add_at_position(), and receive_remove_recipient(), and exported them
756 to local_scan().
757
758 6. If an ACL "warn" statement specified the addition of headers, Exim already
759 inserted X-ACL-Warn: at the start if there was no header name. However, it
760 was not making this test for the second and subsequent header lines if
761 there were newlines in the string. This meant that an invalid header could
762 be inserted if Exim was badly configured.
763
764 7. Allow an ACL "warn" statement to add header lines at the start or after all
765 the Received: headers, as well as at the end.
766
767 8. Added the rcpt_4xx retry error code.
768
769 9. Added postmaster_mailfrom=xxx to callout verification option.
770
771 10. Added mailfrom=xxxx to the callout verification option, for verify=
772 header_sender only.
773
774 11. ${substr_1_:xxxx} and ${substr__3:xxxx} are now diagnosed as syntax errors
775 (they previously behaved as ${substr_1_0:xxxx} and ${substr:_0_3:xxxx}).
776
777 12. Inserted some casts to stop certain compilers warning when using pointer
778 differences as field lengths or precisions in printf-type calls (mostly
779 affecting debugging statements).
780
781 13. Added optional readline() support for -be (dynamically loaded).
782
783 14. Obscure bug fix: if a message error (e.g. 4xx to MAIL) happened within the
784 same clock tick as a message's arrival, so that its received time was the
785 same as the "first fail" time on the retry record, and that message
786 remained on the queue past the ultimate address timeout, every queue runner
787 would try a delivery (because it was past the ultimate address timeout) but
788 after another failure, the ultimate address timeout, which should have then
789 bounced the address, did not kick in. This was a "< instead of <=" error;
790 in most cases the first failure would have been in the next clock tick
791 after the received time, and all would be well.
792
793 15. The special items beginning with @ in domain lists (e.g. @mx_any) were not
794 being recognized when the domain list was tested by the match_domain
795 condition in an expansion string.
796
797 16. Added the ${str2b64: operator.
798
799 17. Exim was always calling setrlimit() to set a large limit for the number of
800 processes, without checking whether the existing limit was already
801 adequate. (It did check for the limit on file descriptors.) Furthermore,
802 errors from getrlimit() and setrlimit() were being ignored. Now they are
803 logged to the main and panic logs, but Exim does carry on, to try to do its
804 job under whatever limits there are.
805
806 18. Imported PCRE 5.0.
807
808 19. Trivial typo in log message " temporarily refused connection" (the leading
809 space).
810
811 20. If the log selector return_path_on_delivery was set and an address was
812 redirected to /dev/null, the delivery process crashed because it assumed
813 that a return path would always be set for a "successful" delivery. In this
814 case, the whole delivery is bypassed as an optimization, and therefore no
815 return path is set.
816
817 21. Internal re-arrangement: the function for sending a challenge and reading
818 a response while authentication was assuming a zero-terminated challenge
819 string. It's now changed to take a pointer and a length, to allow for
820 binary data in such strings.
821
822 22. Added the cyrus_sasl authenticator (code supplied by MBM).
823
824 23. Exim was not respecting finduser_retries when seeking the login of the
825 uid under which it was called; it was always trying 10 times. (The default
826 setting of finduser_retries is zero.) Also, it was sleeping after the final
827 failure, which is pointless.
828
829 24. Implemented tls_on_connect_ports.
830
831 25. Implemented acl_smtp_predata.
832
833 26. If the domain in control=submission is set empty, Exim assumes that the
834 authenticated id is a complete email address when it generates From: or
835 Sender: header lines.
836
837 27. Added "#define SOCKLEN_T int" to OS/os.h-SCO and OS/os.h-SCO_SV. Also added
838 definitions to OS/Makefile-SCO and OS/Makefile-SCO_SV that put basename,
839 chown and chgrp in /bin and hostname in /usr/bin.
840
841 28. Exim was keeping the "process log" file open after each use, just as it
842 does for the main log. This opens the possibility of it remaining open for
843 long periods when the USR1 signal hits a daemon. Occasional processlog
844 errors were reported, that could have been caused by this. Anyway, it seems
845 much more sensible not to leave this file open at all, so that is what now
846 happens.
847
848 29. The long-running daemon process does not normally write to the log once it
849 has entered its main loop, and it closes the log before doing so. This is
850 so that log files can straightforwardly be renamed and moved. However,
851 there are a couple of unusual error situations where the daemon does write
852 log entries, and I had neglected to close the log afterwards.
853
854 30. The text of an SMTP error response that was received during a remote
855 delivery was being truncated at 512 bytes. This is too short for some of
856 the long messages that one sometimes sees. I've increased the limit to
857 1024.
858
859 31. It is now possible to make retry rules that apply only when a message has a
860 specific sender, in particular, an empty sender.
861
862 32. Added "control = enforce_sync" and "control = no_enforce_sync". This makes
863 it possible to be selective about when SMTP synchronization is enforced.
864
865 33. Added "control = caseful_local_part" and "control = "caselower_local_part".
866
867 32. Implemented hosts_connection_nolog.
868
869 33. Added an ACL for QUIT.
870
871 34. Setting "delay_warning=" to disable warnings was not working; it gave a
872 syntax error.
873
874 35. Added mailbox_size and mailbox_filecount to appendfile.
875
876 36. Added control = no_multiline_responses to ACLs.
877
878 37. There was a bug in the logic of the code that waits for the clock to tick
879 in the case where the clock went backwards by a substantial amount such
880 that the microsecond fraction of "now" was more than the microsecond
881 fraction of "then" (but the whole seconds number was less).
882
883 38. Added support for the libradius Radius client library this is found on
884 FreeBSD (previously only the radiusclient library was supported).
885
886
887 Exim version 4.42
888 -----------------
889
890 1. When certain lookups returned multiple values in the form name=value, the
891 quoting of the values was not always being done properly. Specifically:
892 (a) If the value started with a double quote, but contained no whitespace,
893 it was not quoted.
894 (b) If the value contained whitespace other than a space character (i.e.
895 tabs or newlines or carriage returns) it was not quoted.
896 This fix has been applied to the mysql and pgsql lookups by writing a
897 separate quoting function and calling it from the lookup code. The fix
898 should probably also be applied to nisplus, ibase and oracle lookups, but
899 since I cannot test any of those, I have not disturbed their existing code.
900
901 2. A hit in the callout cache for a specific address caused a log line with no
902 reason for rejecting RCPT. Now it says "Previous (cached) callout
903 verification failure".
904
905 3. There was an off-by-one bug in the queryprogram router. An over-long
906 return line was truncated at 256 instead of 255 characters, thereby
907 overflowing its buffer with the terminating zero. As well as fixing this, I
908 have increased the buffer size to 1024 (and made a note to document this).
909
910 4. If an interrupt, such as the USR1 signal that is send by exiwhat, arrives
911 when Exim is waiting for an SMTP response from a remote server, Exim
912 restarts its select() call on the socket, thereby resetting its timeout.
913 This is not a problem when such interrupts are rare. Somebody set up a cron
914 job to run exiwhat every 2 minutes, which is less than the normal select()
915 timeout (5 or 10 minutes). This meant that the select() timeout never
916 kicked in because it was always reset. I have fixed this by comparing the
917 time when an interrupt arrives with the time at the start of the first call
918 to select(). If more time than the timeout has elapsed, the interrupt is
919 treated as a timeout.
920
921 5. Some internal re-factoring in preparation for the addition of Sieve
922 extensions (by MH). In particular, the "personal" test is moved to a
923 separate function, and given an option for scanning Cc: and Bcc: (which is
924 not set for Exim filters).
925
926 6. When Exim created an email address using the login of the caller as the
927 local part (e.g. when creating a From: or Sender: header line), it was not
928 quoting the local part when it contained special characters such as @.
929
930 7. Installed new OpenBSD configuration files.
931
932 8. Reworded some messages for syntax errors in "and" and "or" conditions to
933 try to make them clearer.
934
935 9. Callout options, other than the timeout value, were being ignored when
936 verifying sender addresses in header lines. For example, when using
937
938 verify = header_sender/callout=no_cache
939
940 the cache was (incorrectly) being used.
941
942 10. Added a missing instance of ${EXE} to the exim_install script; this affects
943 only the Cygwin environment.
944
945 11. When return_path_on_delivery was set as a log selector, if different remote
946 addresses in the same message used different return paths and parallel
947 remote delivery occurred, the wrong values would sometimes be logged.
948 (Whenever a remote delivery process finished, the return path value from
949 the most recently started remote delivery process was logged.)
950
951 12. RFC 3848 specifies standard names for the "with" phrase in Received: header
952 lines when AUTH and/or TLS are in use. This is the "received protocol"
953 field. Exim used to use "asmtp" for authenticated SMTP, without any
954 indication (in the protocol name) for TLS use. Now it follows the RFC and
955 uses "esmtpa" if the connection is authenticated, "esmtps" if it is
956 encrypted, and "esmtpsa" if it is both encrypted and authenticated. These
957 names appear in log lines as well as in Received: header lines.
958
959 13. Installed MH's patches for Sieve to add the "copy" and "vacation"
960 extensions, and comparison tests, and to fix some bugs.
961
962 14. Changes to the "personal" filter test:
963
964 (1) The test was buggy in that it was just doing the equivalent of
965 "contains" tests on header lines. For example, if a user's address was
966 anne@some.where, the "personal" test would incorrectly be true for
967
968 To: susanne@some.where
969
970 This test is now done by extracting each address from the header in turn,
971 and checking the entire address. Other tests that are part of "personal"
972 are now done using regular expressions (for example, to check local parts
973 of addresses in From: header lines).
974
975 (2) The list of non-personal local parts in From: addresses has been
976 extended to include "listserv", "majordomo", "*-request", and "owner-*",
977 taken from the Sieve specification recommendations.
978
979 (3) If the message contains any header line starting with "List-" it is
980 treated as non-personal.
981
982 (4) The test for "circular" in the Subject: header line has been removed
983 because it now seems ill-conceived.
984
985 15. Minor typos in src/EDITME comments corrected.
986
987 16. Installed latest exipick from John Jetmore.
988
989 17. If headers_add on a router specified a text string that was too long for
990 string_sprintf() - that is, longer than 8192 bytes - Exim panicked. The use
991 of string_sprintf() is now avoided.
992
993 18. $message_body_size was not set (it was always zero) when running the DATA
994 ACL and the local_scan() function.
995
996 19. For the "mail" command in an Exim filter, no default was being set for
997 the once_repeat time, causing a random time value to be used if "once" was
998 specified. (If the value happened to be <= 0, no repeat happened.) The
999 default is now 0s, meaning "never repeat". The "vacation" command was OK
1000 (its default is 7d). It's somewhat surprising nobody ever noticed this bug
1001 (I found it when inspecting the code).
1002
1003 20. There is now an overall timeout for performing a callout verification. It
1004 defaults to 4 times the callout timeout, which applies to individual SMTP
1005 commands during the callout. The overall timeout applies when there is more
1006 than one host that can be tried. The timeout is checked before trying the
1007 next host. This prevents very long delays if there are a large number of
1008 hosts and all are timing out (e.g. when the network connections are timing
1009 out). The value of the overall timeout can be changed by specifying an
1010 additional sub-option for "callout", called "maxwait". For example:
1011
1012 verify = sender/callout=5s,maxwait=20s
1013
1014 21. Add O_APPEND to the open() call for maildirsize files (Exim already seeks
1015 to the end before writing, but this should make it even safer).
1016
1017 22. Exim was forgetting that it had advertised PIPELINING for the second and
1018 subsequent messages on an SMTP connection. It was also not resetting its
1019 memory on STARTTLS and an internal HELO.
1020
1021 23. When Exim logs an SMTP synchronization error within a session, it now
1022 records whether PIPELINING has been advertised or not.
1023
1024 24. Added 3 instances of "(long int)" casts to time_t variables that were being
1025 formatted using %ld, because on OpenBSD (and perhaps others), time_t is int
1026 rather than long int.
1027
1028 25. Installed the latest Cygwin configuration files from the Cygwin maintainer.
1029
1030 26. Added the never_mail option to autoreply.
1031
1032
1033 Exim version 4.41
1034 -----------------
1035
1036 1. A reorganization of the code in order to implement 4.40/8 caused a daemon
1037 crash if the getsockname() call failed; this can happen if a connection is
1038 closed very soon after it is established. The problem was simply in the
1039 order in which certain operations were done, causing Exim to try to write
1040 to the SMTP stream before it had set up the file descriptor. The bug has
1041 been fixed by making things happen in the correct order.
1042
1043
1044 Exim version 4.40
1045 -----------------
1046
1047 1. If "drop" was used in a DATA ACL, the SMTP output buffer was not flushed
1048 before the connection was closed, thus losing the rejection response.
1049
1050 2. Commented out the definition of SOCKLEN_T in os.h-SunOS5. It is needed for
1051 some early Solaris releases, but causes trouble in current releases where
1052 socklen_t is defined.
1053
1054 3. When std{in,out,err} are closed, re-open them to /dev/null so that they
1055 always exist.
1056
1057 4. Minor refactoring of os.c-Linux to avoid compiler warning when IPv6 is not
1058 configured.
1059
1060 5. Refactoring in expand.c to improve memory usage. Pre-allocate a block so
1061 that releasing the top of it at the end releases what was used for sub-
1062 expansions (unless the block got too big). However, discard this block if
1063 the first thing is a variable or header, so that we can use its block when
1064 it is dynamic (useful for very large $message_headers, for example).
1065
1066 6. Lookups now cache *every* query, not just the most recent. A new, separate
1067 store pool is used for this. It can be recovered when all lookup caches are
1068 flushed. Lookups now release memory at the end of their result strings.
1069 This has involved some general refactoring of the lookup sources.
1070
1071 7. Some code has been added to the store_xxx() functions to reduce the amount
1072 of flapping under certain conditions.
1073
1074 8. log_incoming_interface used to affect only the <= reception log lines. Now
1075 it causes the local interface and port to be added to several more SMTP log
1076 lines, for example "SMTP connection from", and rejection lines.
1077
1078 9. The Sieve author supplied some patches for the doc/README.SIEVE file.
1079
1080 10. Added a conditional definition of _BSD_SOCKLEN_T to os.h-Darwin.
1081
1082 11. If $host_data was set by virtue of a hosts lookup in an ACL, its value
1083 could be overwritten at the end of the current message (or the start of a
1084 new message if it was set in a HELO ACL). The value is now preserved for
1085 the duration of the SMTP connection.
1086
1087 12. If a transport had a headers_rewrite setting, and a matching header line
1088 contained an unqualified address, that address was qualified, even if it
1089 did not match any rewriting rules. The underlying bug was that the values
1090 of the flags that permit the existence of unqualified sender and recipient
1091 addresses in header lines (set by {sender,recipient}_unqualified_hosts for
1092 non-local messages, and by -bnq for local messages) were not being
1093 preserved with the message after it was received.
1094
1095 13. When Exim was logging an SMTP synchronization error, it could sometimes log
1096 "next input=" as part of the text comprising the host identity instead of
1097 the correct text. The code was using the same buffer for two different
1098 strings. However, depending on which order the printing function evaluated
1099 its arguments, the bug did not always show up. Under Linux, for example, my
1100 test suite worked just fine.
1101
1102 14. Exigrep contained a use of Perl's "our" scoping after change 4.31/70. This
1103 doesn't work with some older versions of Perl. It has been changed to "my",
1104 which in any case is probably the better facility to use.
1105
1106 15. A really picky compiler found some instances of statements for creating
1107 error messages that either had too many or two few arguments for the format
1108 string.
1109
1110 16. The size of the buffer for calls to the DNS resolver has been increased
1111 from 1024 to 2048. A larger buffer is needed when performing PTR lookups
1112 for addresses that have a lot of PTR records. This alleviates a problem; it
1113 does not fully solve it.
1114
1115 17. A dnsdb lookup for PTR records that receives more data than will fit in the
1116 buffer now truncates the list and logs the incident, which is the same
1117 action as happens when Exim is looking up a host name and its aliases.
1118 Previously in this situation something unpredictable would happen;
1119 sometimes it was "internal error: store_reset failed".
1120
1121 18. If a server dropped the connection unexpectedly when an Exim client was
1122 using GnuTLS and trying to read a response, the client delivery process
1123 crashed while trying to generate an error log message.
1124
1125 19. If a "warn" verb in an ACL added multiple headers to a message in a single
1126 string, for example:
1127
1128 warn message = H1: something\nH2: something
1129
1130 the text was added as a single header line from Exim's point of view
1131 though it ended up OK in the delivered message. However, searching for the
1132 second and subsequent header lines using $h_h2: did not work. This has been
1133 fixed. Similarly, if a system filter added multiple headers in this way,
1134 the routers could not see them.
1135
1136 20. Expanded the error message when iplsearch is called with an invalid key to
1137 suggest using net-iplsearch in a host list.
1138
1139 21. When running tests using -bh, any delays imposed by "delay" modifiers in
1140 ACLs are no longer actually imposed (and a message to that effect is
1141 output).
1142
1143 22. If a "gecos" field in a passwd entry contained escaped characters, in
1144 particular, if it contained a \" sequence, Exim got it wrong when building
1145 a From: or a Sender: header from that name. A second bug also caused
1146 incorrect handling when an unquoted " was present following a character
1147 that needed quoting.
1148
1149 23. "{crypt}" as a password encryption mechanism for a "crypteq" expansion item
1150 was not being matched caselessly.
1151
1152 24. Arranged for all hyphens in the exim.8 source to be escaped with
1153 backslashes.
1154
1155 25. Change 16 of 4.32, which reversed 71 or 4.31 didn't quite do the job
1156 properly. Recipient callout cache records were still being keyed to include
1157 the sender, even when use_sender was set false. This led to far more
1158 callouts that were necessary. The sender is no longer included in the key
1159 when use_sender is false.
1160
1161 26. Added "control = submission" modifier to ACLs.
1162
1163 27. Added the ${base62d: operator to decode base 62 numbers.
1164
1165 28. dnsdb lookups can now access SRV records.
1166
1167 29. CONFIGURE_OWNER can be set at build time to define an alternative owner for
1168 the configuration file.
1169
1170 30. The debug message "delivering xxxxxx-xxxxxx-xx" is now output in verbose
1171 (-v) mode. This makes the output for a verbose queue run more intelligible.
1172
1173 31. Added a use_postmaster feature to recipient callouts.
1174
1175 32. Added the $body_zerocount variable, containing the number of binary zero
1176 bytes in the message body.
1177
1178 33. The time of last modification of the "new" subdirectory is now used as the
1179 "mailbox time last read" when there is a quota error for a maildir
1180 delivery.
1181
1182 34. Added string comparison operators lt, lti, le, lei, gt, gti, ge, gei.
1183
1184 35. Added +ignore_unknown as a special item in host lists.
1185
1186 36. Code for decoding IPv6 addresses in host lists is now included, even if
1187 IPv6 support is not being compiled. This fixes a bug in which an IPv6
1188 address was recognized as an IP address, but was then not correctly decoded
1189 into binary, causing unexpected and incorrect effects when compared with
1190 another IP address.
1191
1192
1193 Exim version 4.34
1194 -----------------
1195
1196 1. Very minor rewording of debugging text in manualroute to say "list of
1197 hosts" instead of "hostlist".
1198
1199 2. If verify=header_syntax was set, and a header line with an unqualified
1200 address (no domain) and a large number of spaces between the end of the
1201 name and the colon was received, the reception process suffered a buffer
1202 overflow, and (when I tested it) crashed. This was caused by some obsolete
1203 code that should have been removed. The fix is to remove it!
1204
1205 3. When running in the test harness, delay a bit after writing a bounce
1206 message to get a bit more predictability in the log output.
1207
1208 4. Added a call to search_tidyup() just before forking a reception process. In
1209 theory, someone could use a lookup in the expansion of smtp_accept_max_
1210 per_host which, without the tidyup, could leave open a database connection.
1211
1212 5. Added the variables $recipient_data and $sender_data which get set from a
1213 lookup success in an ACL "recipients" or "senders" condition, or a router
1214 "senders" option, similar to $domain_data and $local_part_data.
1215
1216 6. Moved the writing of debug_print from before to after the "senders" test
1217 for routers.
1218
1219 7. Change 4.31/66 (moving the time when the Received: is generated) caused
1220 problems for message scanning, either using a data ACL, or using
1221 local_scan() because the Received: header was not generated till after they
1222 were called (in order to set the time as the time of reception completion).
1223 I have revised the way this works. The header is now generated after the
1224 body is received, but before the ACL or local_scan() are called. After they
1225 are run, the timestamp in the header is updated.
1226
1227
1228 Exim version 4.33
1229 -----------------
1230
1231 1. Change 4.24/6 introduced a bug because the SIGALRM handler was disabled
1232 before starting a queue runner without re-exec. This happened only when
1233 deliver_drop_privilege was set or when the Exim user was set to root. The
1234 effect of the bug was that timeouts during subsequent deliveries caused
1235 crashes instead of being properly handled. The handler is now left at its
1236 default (and expected) setting.
1237
1238 2. The other case in which a daemon avoids a re-exec is to deliver an incoming
1239 message, again when deliver_drop_privilege is set or Exim is run as root.
1240 The bug described in (1) was not present in this case, but the tidying up
1241 of the other signals was missing. I have made the two cases consistent.
1242
1243 3. The ignore_target_hosts setting on a manualroute router was being ignored
1244 for hosts that were looked up using the /MX notation.
1245
1246 4. Added /ignore=<ip list> feature to @mx_any, @mx_primary, and @mx_secondary
1247 in domain lists.
1248
1249 5. Change 4.31/55 was buggy, and broke when there was a rewriting rule that
1250 operated on the sender address. After changing the $sender_address to <>
1251 for the sender address verify, Exim was re-instated it as the original
1252 (before rewriting) address, but remembering that it had rewritten it, so it
1253 wasn't rewriting it again. This bug also had the effect of breaking the
1254 sender address verification caching when the sender address was rewritten.
1255
1256 6. The ignore_target_hosts option was being ignored by the ipliteral router.
1257 This has been changed so that if the ip literal address matches
1258 ignore_target_hosts, the router declines.
1259
1260 7. Added expansion conditions match_domain, match_address, and match_local_
1261 part (NOT match_host).
1262
1263 8. The placeholder for the Received: header didn't have a length field set.
1264
1265 9. Added code to Exim itself and to exim_lock to test for a specific race
1266 condition that could lead to file corruption when using MBX delivery. The
1267 issue is with the lockfile that is created in /tmp. If this file is removed
1268 after a process has opened it but before that process has acquired a lock,
1269 there is the potential for a second process to recreate the file and also
1270 acquire a lock. This could lead to two Exim processes writing to the file
1271 at the same time. The added code performs the same test as UW imapd; it
1272 checks after acquiring the lock that its file descriptor still refers to
1273 the same named file.
1274
1275 10. The buffer for building added header lines was of fixed size, 8192 bytes.
1276 It is now parameterized by HEADER_ADD_BUFFER_SIZE and this can be adjusted
1277 when Exim is built.
1278
1279 11. Added the smtp_active_hostname option. If used, this will typically be made
1280 to depend on the incoming interface address. Because $interface_address is
1281 not set up until the daemon has forked a reception process, error responses
1282 that can happen earlier (such as "too many connections") no longer contain
1283 a host name.
1284
1285 12. If an expansion in a condition on a "warn" statement fails because a lookup
1286 defers, the "warn" statement is abandoned, and the next ACL statement is
1287 processed. Previously this caused the whole ACL to be aborted.
1288
1289 13. Added the iplsearch lookup type.
1290
1291 14. Added ident_timeout as a log selector.
1292
1293 15. Added tls_certificate_verified as a log selector.
1294
1295 16. Added a global option tls_require_ciphers (compare the smtp transport
1296 option of the same name). This controls incoming TLS connections.
1297
1298 17. I finally figured out how to make tls_require_ciphers do a similar thing
1299 in GNUtls to what it does in OpenSSL, that is, set up an appropriate list
1300 before starting the TLS session.
1301
1302 18. Tabs are now shown as \t in -bP output.
1303
1304 19. If the log selector return_path_on_delivery was set, Exim crashed when
1305 bouncing a message because it had too many Received: header lines.
1306
1307 20. If two routers both had headers_remove settings, and the first one included
1308 a superfluous trailing colon, the final name in the first list and the
1309 first name in the second list were incorrectly joined into one item (with a
1310 colon in the middle).
1311
1312
1313 Exim version 4.32
1314 -----------------
1315
1316 1. Added -C and -D options to the exinext utility, mainly to make it easier
1317 to include in the automated testing, but these could be helpful when
1318 multiple configurations are in use.
1319
1320 2. The exinext utility was not formatting the output nicely when there was
1321 an alternate port involved in the retry record key, nor when there was a
1322 message id as well (for retries that were specific to a specific message
1323 and a specific host). It was also confused by IPv6 addresses, because of
1324 the additional colons they contain. I have fixed the IPv4 problem, and
1325 patched it up to do a reasonable job for IPv6.
1326
1327 3. When there is an error after a MAIL, RCPT, or DATA SMTP command during
1328 delivery, the log line now contains "pipelined" if PIPELINING was used.
1329
1330 4. An SMTP transport process used to panic and die if the bind() call to set
1331 an explicit outgoing interface failed. This has been changed; it is now
1332 treated in the same way as a connect() failure.
1333
1334 5. A reference to $sender_host_name in the part of a conditional expansion
1335 that was being skipped was still causing a DNS lookup. This no longer
1336 occurs.
1337
1338 6. The def: expansion condition was not recognizing references to header lines
1339 that used bh_ and bheader_.
1340
1341 7. Added the _cache feature to named lists.
1342
1343 8. The code for checking quota_filecount in the appendfile transport was
1344 allowing one more file than it should have been.
1345
1346 9. For compatibility with Sendmail, the command line option
1347
1348 -prval:sval
1349
1350 is equivalent to
1351
1352 -oMr rval -oMs sval
1353
1354 and sets the incoming protocol and host name (for trusted callers). The
1355 host name and its colon can be omitted when only the protocol is to be set.
1356 Note the Exim already has two private options, -pd and -ps, that refer to
1357 embedded Perl. It is therefore impossible to set a protocol value of "d" or
1358 "s", but I don't think that's a major issue.
1359
1360 10. A number of refactoring changes to the code, none of which should affect
1361 Exim's behaviour:
1362
1363 (a) The number of logging options was getting close to filling up the
1364 32-bit word that was used as a bit map. I have split them into two classes:
1365 those that are passed in the argument to log_write(), and those that are
1366 only ever tested independently outside of that function. These are now in
1367 separate 32-bit words, so there is plenty of room for expansion again.
1368 There is no change in the user interface or the logging behaviour.
1369
1370 (b) When building, for example, log lines, the code previously used a
1371 macro that called string_cat() twice, in order to add two strings. This is
1372 not really sufficiently general. Furthermore, there was one instance where
1373 it was actually wrong because one of the argument was used twice, and in
1374 one call a function was used. (As it happened, calling the function twice
1375 did not affect the overall behaviour.) The macro has been replaced by a
1376 function that can join an arbitrary number of extra strings onto a growing
1377 string.
1378
1379 (c) The code for expansion conditions now uses a table and a binary chop
1380 instead of a serial search (which was left over from when there were very
1381 few conditions). Also, it now recognizes conditions like "pam" even when
1382 the relevant support is not compiled in: a suitably worded error message is
1383 given if an attempt is made to use such a condition.
1384
1385 11. Added ${time_interval:xxxxx}.
1386
1387 12. A bug was causing one of the ddress fields not to be passed back correctly
1388 from remote delivery subprocesses. The field in question was not being
1389 subsequently used, so this caused to problems in practice.
1390
1391 13. Added new log selectors queue_time and deliver_time.
1392
1393 14. Might have fixed a bug in maildirsizefile handling that threw up
1394 "unexpected character" debug warnings, and recalculated the data
1395 unnecessarily. In any case, I expanded the warning message to give more
1396 information.
1397
1398 15. Added the message "Restricted characters in address" to the statements in
1399 the default ACL that block characters like @ and % in local parts.
1400
1401 16. Change 71 for release 4.31 proved to be much less benign that I imagined.
1402 Three changes have been made:
1403
1404 (a) There was a serious bug; a negative response to MAIL caused the whole
1405 recipient domain to be cached as invalid, thereby blocking all messages
1406 to all local parts at the same domain, from all senders. This bug has
1407 been fixed. The domain is no longer cached after a negative response to
1408 MAIL if the sender used is not empty.
1409
1410 (b) The default behaviour of using MAIL FROM:<> for recipient callouts has
1411 been restored.
1412
1413 (c) A new callout option, "use_sender" has been added for people who want
1414 the modified behaviour.
1415
1416
1417 Exim version 4.31
1418 -----------------
1419
1420 1. Removed "EXTRALIBS=-lwrap" from OS/Makefile-Unixware7 on the advice of
1421 Larry Rosenman.
1422
1423 2. Removed "LIBS = -lresolv" from OS/Makefile-Darwin as it is not needed, and
1424 indeed breaks things for older releases.
1425
1426 3. Added additional logging to the case where there is a problem reading data
1427 from a filter that is running in a subprocess using a pipe, in order to
1428 try to track down a specific problem.
1429
1430 4. Testing facility fudge: when running in the test harness and attempting
1431 to connect to 10.x.x.x (expecting a connection timeout) I'm now sometimes
1432 getting "No route to host". Convert this to a timeout.
1433
1434 5. Define ICONV_ARG2_TYPE as "char **" for Unixware7 to avoid compiler
1435 warning.
1436
1437 6. Some OS don't have socklen_t but use size_t instead. This affects the
1438 fifth argument of getsockopt() amongst other things. This is now
1439 configurable by a macro called SOCKLEN_T which defaults to socklen_t, but
1440 can be set for individual OS. I have set it for SunOS5, OSF1, and
1441 Unixware7. Current versions of SunOS5 (aka Solaris) do have socklen_t, but
1442 some earlier ones do not.
1443
1444 7. Change 4.30/15 was not doing the test caselessly.
1445
1446 8. The standard form for an IPv6 address literal was being rejected by address
1447 parsing in, for example, MAIL and RCPT commands. An example of this kind of
1448 address is [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
1449 this, as well as the form without the "IPv6" on the front (but only when
1450 address literals are enabled, of course).
1451
1452 9. Added some casts to avoid compiler warnings in OS/os.c-Linux.
1453
1454 10. Exim crashed if a message with an empty sender address specified by -f
1455 encountered a router with an errors_to setting. This could be provoked only
1456 by a command such as
1457
1458 exim -f "" ...
1459
1460 where an empty string was supplied; "<>" did not hit this bug.
1461
1462 11. Installed PCRE release 4.5.
1463
1464 12. If EHLO/HELO was rejected by an ACL, the value of $sender_helo_name
1465 remained set. It is now erased.
1466
1467 13. exiqgrep wasn't working on MacOS X because it didn't correctly compute
1468 times from message ids (which are base 36 rather than the normal 62).
1469
1470 14. "Expected" SMTP protocol errors that can arise when PIPELINING is in use
1471 were being counted as actual protocol errors, and logged if the log
1472 selector +smtp_protocol_error was set. One cannot be perfect in this test,
1473 but now, if PIPELINING has been advertised, RCPT following a rejected MAIL,
1474 and DATA following a set of rejected RCPTs do not count as protocol errors.
1475 In other words, Exim assumes they were pipelined, though this may not
1476 actually be the case. Of course, in all cases the client gets an
1477 appropriate error code.
1478
1479 15. If a lookup fails in an ACL condition, a message about the failure may
1480 be available; it is used if testing the ACL cannot continue, because most
1481 such messages specify what the cause of the deferral is. However, some
1482 messages (e.g. "MYSQL: no data found") do not cause a defer. There was bug
1483 that caused an old message to be retained and used if a later statement
1484 caused a defer, replacing the real cause of the deferral.
1485
1486 16. If an IP address had so many PTR records that the DNS lookup buffer
1487 was not large enough to hold them, Exim could crash while trying to process
1488 the truncated data. It now detects and logs this case.
1489
1490 17. Further to 4.21/58, another change has been made: if (and only if) the
1491 first line of a message (the first header line) ends with CRLF, a bare LF
1492 in a subsequent header line has a space inserted after it, so as not to
1493 terminate the header.
1494
1495 18. Refactoring: tidied an ugly bit of code in appendfile that copied data
1496 unnecessarily, used atoi() instead of strtol(), and didn't check the
1497 termination when getting file sizes from file names by regex.
1498
1499 19. Completely re-implemented the support for maildirsize files, in the light
1500 of a number of problems with the previous contributed implementation
1501 (4.30/29). In particular:
1502
1503 . If the quota is zero, the maildirsize file is maintained, but no quota is
1504 imposed.
1505
1506 . If the maildir directory does not exist, it is created before any attempt
1507 to write a maildirsize file.
1508
1509 . The quota value in the file is just a cache; if the quota is changed in
1510 the transport, the new value overrides.
1511
1512 . A regular expression is available for excluding directories from the
1513 count.
1514
1515 20. The autoreply transport checks the characters in options that define the
1516 message's headers; it allows continued headers, but it was checking with
1517 isspace() after an embedded newline instead of explicitly looking for a
1518 space or a tab.
1519
1520 21. If all the "regular" hosts to which an address was routed had passed their
1521 expiry times, and had not reached their retry times, the address was
1522 bounced, even if fallback hosts were defined. Now Exim should go on to try
1523 the fallback hosts.
1524
1525 22. Increased buffer sizes in the callout code from 1024 to 4096 to match the
1526 equivalent code in the SMTP transport. Some hosts send humungous responses
1527 to HELO/EHLO, more than 1024 it seems.
1528
1529 23. Refactoring: code in filter.c used (void *) for "any old type" but this
1530 gives compiler warnings in some environments. I've now done it "properly",
1531 using a union.
1532
1533 24. The replacement for inet_ntoa() that is used with gcc on IRIX systems
1534 (because of problems with the built-in one) was declared to return uschar *
1535 instead of char *, causing compiler failure.
1536
1537 25. Fixed a file descriptor leak when processing alias/forward files.
1538
1539 26. Fixed a minor format string issue in dbfn.c.
1540
1541 27. Typo in exim.c: ("dmbnz" for "dbmnz").
1542
1543 28. If a filter file refered to $h_xxx or $message_headers, and the headers
1544 contained RFC 2047 "words", Exim's memory could, under certain conditions,
1545 become corrupted.
1546
1547 29. When a sender address is verified, it is cached, to save repeating the test
1548 when there is more than one recipient in a message. However, when the
1549 verification involves a callout, it is possible for different callout
1550 options to be set for different recipients. It is too complicated to keep
1551 track of this in the cache, so now Exim always runs a verification when a
1552 callout is required, relying on the callout cache for the optimization.
1553 The overhead is duplication of the address routing, but this should not be
1554 too great.
1555
1556 30. Fixed a bug in callout caching. If a RCPT command caused the sender address
1557 to be verified with callout=postmaster, and the main callout worked but the
1558 postmaster check failed, the verification correctly failed. However, if a
1559 subsequent RCPT command asked for sender verification *without* the
1560 postmaster check, incorrect caching caused this verification also to fail,
1561 incorrectly.
1562
1563 31. Exim caches DNS lookup failures so as to avoid multiple timeouts; however,
1564 it was not caching the DNS options (qualify_single, search_parents) that
1565 were used when the lookup failed. A subsequent lookup with different
1566 options therefore always gave the same answer, though there were cases
1567 where it should not have. (Example: a "domains = !$mx_any" option on a
1568 dnslookup router: the "domains" option is always processed without any
1569 widening, but the router might have qualify_single set.) Now Exim uses the
1570 cached value only when the same options are set.
1571
1572 32. Added John Jetmore's "exipick" utility to the distribution.
1573
1574 33. GnuTLS: When an attempt to start a TLS session fails for any reason other
1575 than a timeout (e.g. a certificate is required, and is not provided), an
1576 Exim server now closes the connection immediately. Previously it waited for
1577 the client to close - but if the client is SSL, it seems that they each
1578 wait for each other, leading to a delay before one of them times out.
1579
1580 34: GnuTLS: Updated the code to use the new GnuTLS 1.0.0 API. I have not
1581 maintained 0.8.x compatibility because I don't think many are using it, and
1582 it is clearly obsolete.
1583
1584 35. Added TLS support for CRLs: a tls_crl global option and one for the smtp
1585 transport.
1586
1587 36. OpenSSL: $tls_certificate_verified was being set to 1 even if the
1588 client certificate was expired. A simple patch fixes this, though I don't
1589 understand the full logic of why the verify callback is called multiple
1590 times.
1591
1592 37. OpenSSL: a patch from Robert Roselius: "Enable client-bug workaround.
1593 Versions of OpenSSL as of 0.9.6d include a 'CBC countermeasure' feature,
1594 which causes problems with some clients (such as the Certicom SSL Plus
1595 library used by Eudora). This option, SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS,
1596 disables the coutermeasure allowing Eudora to connect."
1597
1598 38. Exim was not checking that a write() to a log file succeeded. This could
1599 lead to Bad Things if a log got too big, in particular if it hit a file
1600 size limit. Exim now panics and dies if it cannot write to a log file, just
1601 as it does if it cannot open a log file.
1602
1603 39. Modified OS/Makefile-Linux so that it now contains
1604
1605 CFLAGS=-O -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
1606
1607 The two -D definitions ensure that Exim is compiled with large file
1608 support, which makes it possible to handle log files that are bigger than
1609 2^31.
1610
1611 40. Fixed a subtle caching bug: if (in an ACL or a set of routers, for
1612 instance) a domain was checked against a named list that involved a lookup,
1613 causing $domain_data to be set, then another domain was checked against the
1614 same list, then the first domain was re-checked, the value of $domain_data
1615 after the final check could be wrong. In particular, if the second check
1616 failed, it could be set empty. This bug probably also applied to
1617 $localpart_data.
1618
1619 41. The strip_trailing_dot option was not being applied to the address given
1620 with the -f command-line option.
1621
1622 42. The code for reading a message's header from the spool was incrementing
1623 $received_count, but never initializing it. This meant that the value was
1624 incorrect (doubled) while delivering a message in the same process in which
1625 it was received. In the most common configuration of Exim, this never
1626 happens - a fresh exec is done - but it can happen when
1627 deliver_drop_privilege is set.
1628
1629 43. When Exim logs an SMTP synchronization error - client data sent too soon -
1630 it now includes up to 150 characters of the unexpected data in the log
1631 line.
1632
1633 44. The exim_dbmbuild utility uses fixed size buffers for reading input lines
1634 and building data strings. The size of both of these buffers was 10 000
1635 bytes - far larger than anybody would *ever* want, thought I. Needless to
1636 say, somebody hit the limit. I have increased the maximum line length to
1637 20 000 and the maximum data length of concatenated lines to 100 000. I have
1638 also fixed two bugs, because there was no checking on these buffers. Tsk,
1639 tsk. Now exim_dbmbuild gives a message and exits with an error code if a
1640 buffer is too small.
1641
1642 45. The exim_dbmbuild utility did not support quoted keys, as Exim does in
1643 lsearch lookups. Now it does.
1644
1645 46. When parsing a route_list item in a manualroute router, a fixed-length
1646 buffer was used for the list of hosts. I made this 1024 bytes long,
1647 thinking that nobody would ever have a list of hosts that long. Wrong.
1648 Somebody had a whole pile of complicated expansion conditions, and the
1649 string was silently truncated, leading to an expansion error. It turns out
1650 that it is easier to change to an unlimited length (owing to other changes
1651 that have happened since this code was originally written) than to build
1652 structure for giving a limitation error. The length of the item that
1653 expands into the list of hosts is now unlimited.
1654
1655 47. The lsearch lookup could not handle data where the length of text line was
1656 more than 4095 characters. Such lines were truncated, leading to shortened
1657 data being returned. It should now handle lines of any length.
1658
1659 48. Minor wording revision: "cannot test xxx in yyy ACL" becomes "cannot test
1660 xxx condition in yyy ACL" (e.g. "cannot test domains condition in DATA
1661 ACL").
1662
1663 49. Cosmetic tidy to scripts like exicyclog that are generated by globally
1664 replacing strings such as BIN_DIRECTORY in a source file: the replacement
1665 no longer happens in comment lines. A list of replacements is now placed
1666 at the head of all of the source files, except those whose only change is
1667 to replace PERL_COMMAND in the very first #! line.
1668
1669 50. Replaced the slow insertion sort in queue.c, for sorting the list of
1670 messages on the queue, with a bottom-up merge sort, using code contributed
1671 by Michael Haardt. This should make operations like -bp somewhat faster on
1672 large queues. It won't affect queue runners, except when queue_run_in_order
1673 is set.
1674
1675 51. Installed eximstats 1.31 in the distribution.
1676
1677 52. Added support for SRV lookups to the dnslookup router.
1678
1679 53. If an ACL referred to $message_body or $message_body_end, the value was not
1680 reset for any messages that followed in the same SMTP session.
1681
1682 54. The store-handling optimization for building very long strings was not
1683 differentiating between the different store pools. I don't think this
1684 actually made any difference in practice, but I've tidied it.
1685
1686 55. While running the routers to verify a sender address, $sender_address
1687 was still set to the sender address. This is wrong, because when routing to
1688 send a bounce to the sender, it would be empty. Therefore, I have changed
1689 it so that, while verifying a sender address, $sender_address is set to <>.
1690 (There is no change to what happens when verifying a recipient address.)
1691
1692 56. After finding MX (or SRV) records, Exim was doing a DNS lookup for the
1693 target A or AAAA records (if not already returned) without resetting the
1694 qualify_single or search_parents options of the DNS resolver. These are
1695 inappropriate in this case because the targets of MX and SRV records must
1696 be FQDNs. A broken DNS record could cause trouble if it happened to have a
1697 target that, when qualified, matched something in the local domain. These
1698 two options are now turned off when doing these lookups.
1699
1700 57. It seems that at least some releases of Reiserfs (which does not have the
1701 concept of a fixed number of inodes) returns zero and not -1 for the
1702 number of available inodes. This interacted badly with check_spool_inodes,
1703 which assumed that -1 was the "no such thing" setting. What I have done is
1704 to check that the total number of inodes is greater than zero before doing
1705 the test of how many are available.
1706
1707 58. When a "warn" ACL statement has a log_message modifier, the message is
1708 remembered, and not repeated. This is to avoid a lot of repetition when a
1709 message has many recipients that cause the same warning to be written.
1710 Howewer, Exim was preserving the list of already written lines for an
1711 entire SMTP session, which doesn't seem right. The memory is now reset if a
1712 new message is started.
1713
1714 59. The "rewrite" debugging flag was not showing the result of rewriting in the
1715 debugging output unless log_rewrite was also set.
1716
1717 60. Avoid a compiler warning on 64-bit systems in dsearch.c by avoiding the use
1718 of (int)(handle) when we know that handle contains (void *)(-1).
1719
1720 61. The Exim daemon panic-logs an error return when it closes the incoming
1721 connection. However "connection reset by peer" seems to be common, and
1722 isn't really an error worthy of noting specially, so that particular error
1723 is no long logged.
1724
1725 62. When Exim is trying to find all the local interfaces, it used to panic and
1726 die if the ioctl to get the interface flags failed. However, it seems that
1727 on at least one OS (Solaris 9) it is possible to have an interface that is
1728 included in the list of interfaces, but for which you get a failure error
1729 for this call. This happens when the interface is not "plumbed" into a
1730 protocol (i.e. neither IPv4 nor IPv6). I've changed the code so that a
1731 failure of the "get flags" call assumes that the interface is down.
1732
1733 63. Added a ${eval10: operator, which assumes all numbers are decimal. This
1734 makes life easier for people who are doing arithmetic on fields extracted
1735 from dates, where you often get leading zeros that should not be
1736 interpreted as octal.
1737
1738 64. Added qualify_domain to the redirect router, to override the global
1739 setting.
1740
1741 65. If a pathologically long header line contained very many addresses (the
1742 report of this problem mentioned 10 000) and each of them was rewritten,
1743 Exim could use up a very large amount of memory. (It kept on making new
1744 copies of the header line as it rewrote, and never released the old ones.)
1745 At the expense of a bit more processing, the header rewriting function has
1746 been changed so that it no longer eats memory in this way.
1747
1748 66. The generation of the Received: header has been moved from the time that a
1749 message starts to be received, to the time that it finishes. The timestamp
1750 in the Received: header should now be very close to that of the <= log
1751 line. There are two side-effects of this change:
1752
1753 (a) If a message is rejected by a DATA or non-SMTP ACL or local_scan(), the
1754 logged header lines no longer include the local Received: line, because
1755 it has not yet been created. The same applies to a copy of the message
1756 that is returned to a non-SMTP sender when a message is rejected.
1757
1758 (b) When a filter file is tested using -bf, no additional Received: header
1759 is added to the test message. After some thought, I decided that this
1760 is a bug fix.
1761
1762 This change does not affect the value of $received_for. It is still set
1763 after address rewriting, but before local_scan() is called.
1764
1765 67. Installed the latest Cygwin-specific files from the Cygwin maintainer.
1766
1767 68. GnuTLS: If an empty file is specified for tls_verify_certificates, GnuTLS
1768 gave an unhelpful panic error message, and a defer error. I have managed to
1769 change this behaviour so that it now rejects any supplied certificate,
1770 which seems right, as the list of acceptable certificates is empty.
1771
1772 69. OpenSSL: If an empty file is specified for tls_verify_certificates, OpenSSL
1773 gave an unhelpful defer error. I have not managed to make this reject any
1774 supplied certificates, but the error message it gives is "no certificate
1775 supplied", which is not helpful.
1776
1777 70. exigrep's output now also includes lines that are not associated with any
1778 message, but which match the given pattern. Implemented by a patch from
1779 Martin Sluka, which also tidied up the Perl a bit.
1780
1781 71. Recipient callout verification, like sender verification, was using <> in
1782 the MAIL FROM command. This isn't really the right thing, since the actual
1783 sender may affect whether the remote host accepts the recipient or not. I
1784 have changed it to use the actual sender in the callout; this means that
1785 the cache record is now keyed on a recipient/sender pair, not just the
1786 recipient address. There doesn't seem to be a real danger of callout loops,
1787 since a callout by the remote host to check the sender would use <>.
1788 [SEE ABOVE: changed after hitting problems.]
1789
1790 72. Exim treats illegal SMTP error codes that do not begin with 4 or 5 as
1791 temporary errors. However, in the case of such a code being given after
1792 the end of a data transmission (i.e. after ".") Exim was failing to write
1793 a retry record for the message. (Yes, there was some broken host that was
1794 actually sending 8xx at this point.)
1795
1796 73. An unknown lookup type in a host list could cause Exim to panic-die when
1797 the list was checked. (An example that provoked this was putting <; in the
1798 middle of a list instead of at the start.) If this happened during a DATA
1799 ACL check, a -D file could be left lying around. This kind of configuration
1800 error no longer causes Exim to die; instead it causes a defer errror. The
1801 incident is still logged to the main and panic logs.
1802
1803 74. Buglet left over from Exim 3 conversion. The message "too many messages
1804 in one connection" was written to the rejectlog but not the mainlog, except
1805 when address rewriting (yes!) was being logged.
1806
1807 75. Added write_rejectlog option.
1808
1809 76. When a system filter was run not as root (that is, when system_filter_user
1810 was set), the values of the $n variables were not being returned to the
1811 main process; thus, they were not subsequently available in the $sn
1812 variables.
1813
1814 77. Added +return_path_on_delivery log selector.
1815
1816 78. A connection timeout was being treated differently from recipients deferred
1817 when testing hosts_max_try with a message that was older than the host's
1818 retry timeout. (The host should not be counted, thus allowing all hosts to
1819 be tried at least once before bouncing.) This may have been the cause of an
1820 occasionally reported bug whereby a message would remain on the queue
1821 longer than the retry timeout, but would be bounced if a delivery was
1822 forced. I say "may" because I never totally pinned down the problem;
1823 setting up timeout/retry tests is difficult. See also the next item.
1824
1825 79. The ultimate address timeout was not being applied to errors that involved
1826 a combination of host plus message (for example, a timeout on a MAIL
1827 command). When an address resolved to a number of possible hosts, and they
1828 were not all tried for each delivery (e.g. because of hosts_max_try), a
1829 message could remain on the queue longer than the retry timeout.
1830
1831 80. Sieve bug: "stop" inside "elsif" was broken. Applied a patch from Michael
1832 Haardt.
1833
1834 81. Fixed an obscure SMTP outgoing bug which required at least the following
1835 conditions: (a) there was another message waiting for the same server;
1836 (b) the server returned 5xx to all RCPT commands in the first message so
1837 that the message was not completed; (c) the server dropped the connection
1838 or gave a negative response to the RSET that Exim sends to abort the
1839 transaction. The observed case was a dropped connection after DATA that had
1840 been sent in pipelining mode. That is, the server had advertised PIPELINING
1841 but was not implementing it correctly. The effect of the bug was incorrect
1842 behaviour, such as trying another host, and this could lead to a crash.
1843
1844
1845 Exim version 4.30
1846 -----------------
1847
1848 1. The 3rd arguments to getsockname(), getpeername(), and accept() in exim.c
1849 and daemon.c were passed as pointers to ints; they should have been
1850 pointers to socklen_t variables (which are typically unsigned ints).
1851
1852 2. Some signed/unsigned type warnings in the os.c file for Linux have been
1853 fixed.
1854
1855 3. Fixed a really odd bug that affected only the testing scheme; patching a
1856 certain fixed string in the binary changed the value of another string that
1857 happened to be identical to the end of the original first string.
1858
1859 4. When gethostbyname() (or equivalent) is passed an IP address as a "host
1860 name", it returns that address as the IP address. On some operating
1861 systems (e.g. Solaris), it also passes back the IP address string as the
1862 "host name". However, on others (e.g. Linux), it passes back an empty
1863 string. Exim wasn't checking for this, and was changing the host name to an
1864 empty string, assuming it had been canonicized.
1865
1866 5. Although rare, it is permitted to have more than one PTR record for a given
1867 IP address. I thought that gethostbyaddr() or getipnodebyaddr() always gave
1868 all the names associated with an address, because they do in Solaris.
1869 However, it seems that they do not in Linux for data that comes from the
1870 DNS. If an address in /etc/hosts has multiple names, they _are_ all given.
1871 I found this out when I moved to a new Linux workstation and tried to run
1872 the Exim test suite.
1873
1874 To get round this problem I have changed the code so that it now does its
1875 own call to the DNS to look up PTR records when searching for a host name.
1876 If nothing can be found in the DNS, it tries gethostbyaddr(), so that
1877 addresses that are only in /etc/hosts are still found.
1878
1879 This behaviour is, however, controlled by an option called host_lookup_
1880 order, which defaults to "bydns:byaddr". If people want to use the other
1881 order, or indeed, just use one or the other means of lookup, they can
1882 specify it in this variable.
1883
1884 6. If a PTR record yields an empty name, Exim treats it as non-existent. In
1885 some operating systems, this comes back from gethostbyaddr() as an empty
1886 string, and this is what Exim used to test for. However, it seems that in
1887 other systems, "." is yielded. Exim now tests for this case too.
1888
1889 7. The values of check_spool_space and check_log_space are now held internally
1890 as a number of kilobytes instead of an absolute number of bytes. If a
1891 numbers is specified without 'K' or 'M', it is rounded up to the nearest
1892 kilobyte. This means that much larger values can be stored.
1893
1894 8. Exim monitor: an attempt to get the action menu when not actually pointing
1895 at a message produces an empty menu entitled "No message selected". This
1896 works on Solaris (OpenWindows). However, XFree86 does not like a menu with
1897 no entries in it ("Shell widget menu has zero width and/or height"). So I
1898 have added a single, blank menu entry in this case.
1899
1900 9. Added ${quote_local_part.
1901
1902 10. MIME decoding is now applied to the contents of Subject: header lines when
1903 they are logged.
1904
1905 11. Now that a reference to $sender_host_address automatically causes a reverse
1906 lookup to occur if necessary (4.13/18), there is no need to arrange for a
1907 host lookup before query-style lookups in lists that might use this
1908 variable. This has therefore been abolished, and the "net-" prefix is no
1909 longer necessary for query-style lookups.
1910
1911 12. The Makefile for SCO_SV contained a setting of LDFLAGS. This appears to
1912 have been a typo for LFLAGS, so it has been changed.
1913
1914 13. The install script calls Exim with "-C /dev/null" in order to find the
1915 version number. If ALT_CONFIG_PREFIX was set, this caused an error message
1916 to be output. Howeve, since Exim outputs its version number before the
1917 error, it didn't break the script. It just looked ugly. I fixed this by
1918 always allowing "-C /dev/null" if the caller is root.
1919
1920 14. Ignore overlarge ACL variable number when reading spool file - insurance
1921 against a later release with more variables having written the file.
1922
1923 15. The standard form for an IPv6 address literal was being rejected by EHLO.
1924 Example: [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
1925 this, as well as the form without the "IPv6" on the front.
1926
1927 16. Added CHOWN_COMMAND=/usr/sbin/chown and LIBS=-lresolv to the
1928 OS/Makefile-Darwin file.
1929
1930 17. Fixed typo in lookups/ldap.c: D_LOOKUP should be D_lookup. This applied
1931 only to LDAP libraries that do not have LDAP_OPT_DEREF.
1932
1933 18. After change 4.21/52, "%ld" was used to format the contents of the $inode
1934 variable. However, some OS use ints for inodes. I've added cast to long int
1935 to get rid of the compiler warning.
1936
1937 19. I had forgotten to lock out "/../" in configuration file names when
1938 ALT_CONFIG_PREFIX was set.
1939
1940 20. Routers used for verification do not need to specify transports. However,
1941 if such a router generated a host list, and callout was configured, Exim
1942 crashed, because it could not find a port number from the (non-existent)
1943 transport. It now assumes port 25 in this circumstance.
1944
1945 21. Added the -t option to exigrep.
1946
1947 22. If LOOKUP_LSEARCH is defined, all three linear search methods (lsearch,
1948 wildlsearch, nwildlsearch) are compiled. LOOKUP_WILDLSEARCH and LOOKUP_
1949 NWILDLSEARCH are now obsolete, but retained for compatibility. If either of
1950 them is set, LOOKUP_LSEARCH is forced.
1951
1952 23. "exim -bV" now outputs a list of lookups that are included in the binary.
1953
1954 24. Added sender and host information to the "rejected by local_scan()" log
1955 line; previously there was no indication of these.
1956
1957 25. Added .include_if_exists.
1958
1959 26. Change 3.952/11 added an explicit directory sync on top of a file sync for
1960 Linux. It turns out that not all file systems support this. Apparently some
1961 versions of NFS do not. (It's rare to put Exim's spool on NFS, but people
1962 do it.) To cope with this, the error EINVAL, which means that sync-ing is
1963 not supported on the file descriptor, is now ignored when Exim is trying to
1964 sync a directory. This applies only to Linux.
1965
1966 27. Added -DBIND_8_COMPAT to the CLFAGS setting for Darwin.
1967
1968 28. In Darwin (MacOS X), the PAM headers are in /usr/include/pam and not in
1969 /usr/include/security. There's now a flag in OS/os.h-Darwin to cope with
1970 this.
1971
1972 29. Added support for maildirsize files from supplied patch (modified a bit).
1973
1974 30. The use of :fail: followed by an empty string could lead Exim to respond to
1975 sender verification failures with (e.g.):
1976
1977 550 Verification failed for <xxx>
1978 550 Sender verify failed
1979
1980 where the first response line was missing the '-' that indicates it is not
1981 the final line of the response.
1982
1983 31. The loop for finding the name of the user that called Exim had a hardwired
1984 limit of 10; it now uses the value of finduser_retries, which is used for
1985 all other user lookups.
1986
1987 32. Added $received_count variable, available in data and not_smtp ACLs, and at
1988 delivery time.
1989
1990 33. Exim was neglecting to zero errno before one call of strtol() when
1991 expanding a string and expecting an integer value. On some systems this
1992 resulted in spurious "integer overflow" errors. Also, it was casting the
1993 result into an int without checking.
1994
1995 34. Testing for a connection timeout using "timeout_connect" in the retry rules
1996 did not work. The code looks as if it has *never* worked, though it appears
1997 to have been documented since at least releast 1.62. I have made it work.
1998
1999 35. The "timeout_DNS" error in retry rules, also documented since at least
2000 1.62, also never worked. As it isn't clear exactly what this means, and
2001 clearly it isn't a major issue, I have abolished the feature by treating it
2002 as "timeout", and writing a warning to the main and panic logs.
2003
2004 36. The display of retry rules for -brt wasn't always showing the error code
2005 correctly.
2006
2007 37. Added new error conditions to retry rules: timeout_A, timeout_MX,
2008 timeout_connect_A, timeout_connect_MX.
2009
2010 38. Rewriting the envelope sender at SMTP time did not allow it to be rewritten
2011 to the empty sender.
2012
2013 39. The daemon was not analysing the content of -oX till after it had closed
2014 stderr and disconnected from the controlling terminal. This meant that any
2015 syntax errors were only noted on the panic log, and the return code from
2016 the command was 0. By re-arranging the code a little, I've made the
2017 decoding happen first, so such errors now appear on stderr, and the return
2018 code is 1. However, the actual setting up of the sockets still happens in
2019 the disconnected process, so errors there are still only recorded on the
2020 panic log.
2021
2022 40. A daemon listener on a wildcard IPv6 socket that also accepts IPv4
2023 connections (as happens on some IP stacks) was logged at start up time as
2024 just listening for IPv6. It now logs "IPv6 with IPv4". This differentiates
2025 it from "IPv6 and IPv4", which means that two separate sockets are being
2026 used.
2027
2028 41. The debug output for gethostbyname2() or getipnodebyname() failures now
2029 says whether AF_INET or AF_INET6 was passed as an argument.
2030
2031 42. Exiwhat output was messed up when time zones were included in log
2032 timestamps.
2033
2034 43. Exiwhat now gives more information about the daemon's listening ports,
2035 and whether -tls-on-connect was used.
2036
2037 44. The "port" option of the smtp transport is now expanded.
2038
2039 45. A "message" modifier in a "warn" statement in a non-message ACL was being
2040 silently ignored. Now an error message is written to the main and panic
2041 logs.
2042
2043 46. There's a new ACL modifier called "logwrite" which writes to a log file
2044 as soon as it is encountered.
2045
2046 47. Added $local_user_uid and $local_user_gid at routing time.
2047
2048 48. Exim crashed when trying to verify a sender address that was being
2049 rewritten to "<>".
2050
2051 49. Exim was recognizing only a space character after ".include". It now also
2052 recognizes a tab character.
2053
2054 50. Fixed several bugs in the Perl script that creates the exim.8 man page by
2055 extracting the relevant information from the specification. The man page no
2056 longer contains scrambled data for the -d option, and I've added a section
2057 at the front about calling Exim under different names.
2058
2059 51. Added "extra_headers" argument to the "mail" command in filter files.
2060
2061 52. Redirecting mail to an unqualified address in a Sieve filter caused Exim to
2062 crash.
2063
2064 53. Installed eximstats 1.29.
2065
2066 54. Added transport_filter_timeout as a generic transport option.
2067
2068 55. Exim no longer adds an empty Bcc: header to messages that have no To: or
2069 Cc: header lines. This was required by RFC 822, but it not required by RFC
2070 2822.
2071
2072 56. Exim used to add From:, Date:, and Message-Id: header lines to any
2073 incoming messages that did not have them. Now it does so only if the
2074 message originates locally, that is, if there is no associated remote host
2075 address. When Resent- header lines are present, this applies to the Resent-
2076 lines rather than the non-Resent- lines.
2077
2078 57. Drop incoming SMTP connection after too many syntax or protocol errors. The
2079 limit is controlled by smtp_max_synprot_errors, defaulting to 3.
2080
2081 58. Messages for configuration errors now include the name of the main
2082 configuration file - useful now that there may be more than one file in a
2083 list (.included file names were always shown).
2084
2085 59. Change 4.21/82 (run initgroups() when starting the daemon) causes problems
2086 for those rare installations that do not start the daemon as root or run it
2087 setuid root. I've cut out the call to initgroups() if the daemon is not
2088 root at that time.
2089
2090 60. The Exim user and group can now be bound into the binary as text strings
2091 that are looked up at the start of Exim's processing.
2092
2093 61. Applied a small patch for the Interbase code, supplied by Ard Biesheuvel.
2094
2095 62. Added $mailstore_basename variable.
2096
2097 63. Installed patch to sieve.c from Michael Haardt.
2098
2099 64. When Exim failed to open the panic log after failing to open the main log,
2100 the original message it was trying to log was written to stderr and debug
2101 output, but if they were not available (the usual case in production), it
2102 was lost. Now it is written to syslog before the two lines that record the
2103 failures to open the logs.
2104
2105 65. Users' Exim filters run in subprocesses under the user's uid. It is
2106 possible for a "deliver" command or an alias in a "personal" command to
2107 provoke an address rewrite. If logging of address rewriting is configured,
2108 this fails because the process is not running as root or exim. There may be
2109 a better way of dealing with this, but for the moment (because 4.30 needs
2110 to be released), I have disabled address rewrite logging when running a
2111 filter in a non-root, non-exim process.
2112
2113
2114 Exim version 4.24
2115 -----------------
2116
2117 1. The buildconfig auxiliary program wasn't quoting the value set for
2118 HEADERS_CHARSET. This caused a compilation error complaining that 'ISO' was
2119 not defined. This bug was masked in 4.22 by the effect that was fixed in
2120 change 4.23/1.
2121
2122 2. Some messages that were rejected after a message id was allocated were
2123 shown as "incomplete" by exigrep. It no longer does this for messages that
2124 are rejected by local_scan() or the DATA or non-SMTP ACLs.
2125
2126 3. If a Message-ID: header used a domain literal in the ID, and Exim did not
2127 have allow_domain_literals set, the ID did not get logged in the <= line.
2128 Domain literals are now always recognized in Message-ID: header lines.
2129
2130 4. The first argument for a ${extract expansion item is the key name or field
2131 number. Leading and trailing spaces in this item were not being ignored,
2132 causing some misleading effects.
2133
2134 5. When deliver_drop_privilege was set, single queue runner processes started
2135 manually (i.e. by the command "exim -q") or by the daemon (which uses the
2136 same command in the process it spins off) were not dropping privilege.
2137
2138 6. When the daemon running as "exim" started a queue runner, it always
2139 re-executed Exim in the spun-off process. This is a waste of effort when
2140 deliver_drop_privilege is set. The new process now just calls the
2141 queue-runner function directly.
2142
2143
2144 Exim version 4.23
2145 -----------------
2146
2147 1. Typo in the src/EDITME file: it referred to HEADERS_DECODE_TO instead of
2148 HEADERS_CHARSET.
2149
2150 2. Change 4.21/73 introduced a bug. The pid file path set by -oP was being
2151 ignored. Though the use of -oP was forcing the writing of a pid file, it
2152 was always written to the default place.
2153
2154 3. If the message "no IP address found for host xxxx" is generated during
2155 incoming verification, it is now followed by identification of the incoming
2156 connection (so you can more easily find what provoked it).
2157
2158 4. Bug fix for Sieve filters: "stop" inside a block was not working properly.
2159
2160 5. Added some features to "harden" Exim a bit more against certain attacks:
2161
2162 (a) There is now a build-time option called FIXED_NEVER_USERS that can
2163 be put in Local/Makefile. This is like the never_users runtime option,
2164 but it cannot be overridden. The default setting is "root".
2165
2166 (b) If ALT_CONFIG_PREFIX is defined in Local/Makefile, it specifies a
2167 prefix string with which any file named in a -C command line option
2168 must start.
2169
2170 (c) If ALT_CONFIG_ROOT_ONLY is defined in Local/Makefile, root privilege
2171 is retained for -C and -D only if the caller of Exim is root. Without
2172 it, the exim user may also use -C and -D and retain privilege.
2173
2174 (d) If DISABLE_D_OPTION is defined in Local/Makefile, the use of the -D
2175 command line option is disabled.
2176
2177 6. Macro names set by the -D option must start with an upper case letter, just
2178 like macro names defined in the configuration file.
2179
2180 7. Added "dereference=" facility to LDAP.
2181
2182 8. Two instances of the typo "uknown" in the source files are fixed.
2183
2184 9. If a PERL_COMMAND setting in Local/Makefile was not at the start of a line,
2185 the Configure-Makefile script screwed up while processing it.
2186
2187 10. Incorporated PCRE 4.4.
2188
2189 11. The SMTP synchronization check was not operating right at the start of an
2190 SMTP session. For example, it could not catch a HELO sent before the client
2191 waited for the greeting. There is now a check for outstanding input at the
2192 point when the greeting is written. Because of the duplex, asynchronous
2193 nature of TCP/IP, it cannot be perfect - the incorrect input may be on its
2194 way, but not yet received, when the check is performed.
2195
2196 12. Added tcp_nodelay to make it possible to turn of the setting of TCP_NODELAY
2197 on TCP/IP sockets, because this apparently causes some broken clients to
2198 timeout.
2199
2200 13. Installed revised OS/Makefile-CYGWIN and OS/os.c-cygwin (the .h file was
2201 unchanged) from the Cygwin maintainer.
2202
2203 14. The code for -bV that shows what is in the binary showed "mbx" when maildir
2204 was supported instead of testing for mbx. Effectively a typo.
2205
2206 15. The spa authenticator server code was not checking that the input it
2207 received was valid base64.
2208
2209 16. The debug output line for the "set" modifier in ACLs was not showing the
2210 name of the variable that was being set.
2211
2212 17. Code tidy: the variable type "vtype_string" was never used. Removed it.
2213
2214 18. Previously, a reference to $sender_host_name did not cause a DNS reverse
2215 lookup on its own. Something else was needed to trigger the lookup. For
2216 example, a match in host_lookup or the need for a host name in a host list.
2217 Now, if $sender_host_name is referenced and the host name has not yet been
2218 looked up, a lookup is performed. If the lookup fails, the variable remains
2219 empty, and $host_lookup_failed is set to "1".
2220
2221 19. Added "eqi" as a case-independent comparison operator.
2222
2223 20. The saslauthd authentication condition could segfault if neither service
2224 nor realm was specified.
2225
2226 21. If an overflowing value such as "2048M" was set for message_size_limit, the
2227 error message that was logged was misleading, and incoming SMTP
2228 connections were dropped. The message is now more accurate, and temporary
2229 errors are given to SMTP connections.
2230
2231 22. In some error situations (such as 21 above) Exim rejects all SMTP commands
2232 (except RSET) with a 421 error, until QUIT is received. However, it was
2233 failing to send a response to QUIT.
2234
2235 23. The HELO ACL was being run before the code for helo_try_verify_hosts,
2236 which made it impossible to use "verify = helo" in the HELO ACL. The HELO
2237 ACL is now run after the helo_try_verify_hosts code.
2238
2239 24. "{MD5}" and "{SHA1}" are now recognized as equivalent to "{md5"} and
2240 "{sha1}" in the "crypteq" expansion condition (in fact the comparison is
2241 case-independent, so other case variants are also recognized). Apparently
2242 some systems use these upper case variants.
2243
2244 25. If more than two messages were waiting for the same host, and a transport
2245 filter was specified for the transport, Exim sent two messages over the
2246 same TCP/IP connection, and then failed with "socket operation on non-
2247 socket" when it tried to send the third.
2248
2249 26. Added Exim::debug_write and Exim::log_write for embedded Perl use.
2250
2251 27. The extern definition of crypt16() in expand.c was not being excluded when
2252 the OS had its own crypt16() function.
2253
2254 28. Added bounce_return_body as a new option, and bounce_return_size_limit
2255 as a preferred synonym for return_size_limit, both as an option and as an
2256 expansion variable.
2257
2258 29. Added LIBS=-liconv to OS/Makefile-OSF1.
2259
2260 30. Changed the default configuration ACL to relax the local part checking rule
2261 for addresses that are not in any local domains. For these addresses,
2262 slashes and pipe symbols are allowed within local parts, but the sequence
2263 /../ is explicitly forbidden.
2264
2265 31. SPA server authentication was not clearing the challenge buffer before
2266 using it.
2267
2268 32. log_message in a "warn" ACL statement was writing to the reject log as
2269 well as to the main log, which contradicts the documentation and doesn't
2270 seem right (because no rejection is happening). So I have stopped it.
2271
2272 33. Added Ard Biesheuvel's lookup code for accessing an Interbase database.
2273 However, I am unable to do any testing of this.
2274
2275 34. Fixed an infelicity in the appendfile transport. When checking directories
2276 for a mailbox, to see if any needed to be created, it was accidentally
2277 using path names with one or more superfluous leading slashes; tracing
2278 would show up entries such as stat("///home/ph10", 0xFFBEEA48).
2279
2280 35. If log_message is set on a "discard" verb in a MAIL or RCPT ACL, its
2281 contents are added to the log line that is written for every discarded
2282 recipient. (Previously a log_message setting was ignored.)
2283
2284 36. The ${quote: operator now quotes the string if it is empty.
2285
2286 37. The install script runs exim in order to find its version number. If for
2287 some reason other than non-existence or emptiness, which it checks, it
2288 could not run './exim', it was installing it with an empty version number,
2289 i.e. as "exim-". This error state is now caught, and the installation is
2290 aborted.
2291
2292 38. An argument was missing from the function that creates an error message
2293 when Exim fails to connect to the socket for saslauthd authentication.
2294 This could cause Exim to crash, or give a corrupted message.
2295
2296 39. Added isip, isip4, and isip6 to ${if conditions.
2297
2298 40. The ACL variables $acl_xx are now saved with the message, and can be
2299 accessed later in routers, transports, and filters.
2300
2301 41. The new lookup type nwildlsearch is like wildlsearch, except that the key
2302 strings in the file are not string-expanded.
2303
2304 42. If a MAIL command specified a SIZE value that was too large to fit into an
2305 int variable, the check against message_size_limit failed. Such values are
2306 now forced to INT_MAX, which is around 2Gb for a 32-bit variable. Maybe one
2307 day this will have to be increased, but I don't think I want to be around
2308 when emails are that large.
2309
2310
2311
2312 Exim version 4.22
2313 -----------------
2314
2315 1. Removed HAVE_ICONV=yes from OS/Makefile-FreeBSD, since it seems that
2316 iconv() is not standard in FreeBSD.
2317
2318 2. Change 4.21/17 was buggy and could cause stack overwriting on a system with
2319 IPv6 enabled. The observed symptom was a segmentation fault on return from
2320 the function os_common_find_running_interfaces() in src/os.c.
2321
2322 3. In the check_special_case() function in daemon.c I had used "errno" as an
2323 argument name, which causes warnings on some systems. This was basically a
2324 typo, since it was named "eno" in the comments!
2325
2326 4. The code that waits for the clock to tick (at a resolution of some fraction
2327 of a second) so as to ensure message-id uniqueness was always waiting for
2328 at least one whole tick, when it could have waited for less. [This is
2329 almost certainly not relevant at current processor speeds, where it is
2330 unlikely to ever wait at all. But we try to future-proof.]
2331
2332 5. The function that sleeps for a time interval that includes fractions of a
2333 second contained a race. It did not block SIGALRM between setting the
2334 timer, and suspending (a couple of lines later). If the interval was short
2335 and the sigsuspend() was delayed until after it had expired, the suspension
2336 never ended. On busy systems this could lead to processes getting stuck for
2337 ever.
2338
2339 6. Some uncommon configurations may cause a lookup to happen in a queue runner
2340 process, before it forks any delivery processes. The open lookup caching
2341 mechanism meant that the open file or database connection was passed into
2342 the delivery process. The problem was that delivery processes always tidy
2343 up cached lookup data. This could cause a problem for the next delivery
2344 process started by the queue runner, because the external queue runner
2345 process does not know about the closure. So the next delivery process
2346 still has data in the lookup cache. In the case of a file lookup, there was
2347 no problem because closing a file descriptor in a subprocess doesn't affect
2348 the parent. However, if the lookup was caching a connection to a database,
2349 the connection was closed, and the second delivery process was likely to
2350 see errors such as "PGSQL: query failed: server closed the connection
2351 unexpectedly". The problem has been fixed by closing all cached lookups
2352 in a queue runner before running a delivery process.
2353
2354 7. Compiler warning on Linux for the second argument of iconv(), which doesn't
2355 seem to have the "const" qualifier which it has on other OS. I've
2356 parameterised it.
2357
2358 8. Change 4.21/2 was too strict. It is only if there are two authenticators
2359 *of the same type* (client or server) with the same public name that an
2360 error should be diagnosed.
2361
2362 9. When Exim looked up a host name for an IP address, but failed to find the
2363 original IP address when looking up the host name (a safety check), it
2364 output the message "<ip address> does not match any IP for NULL", which was
2365 confusing, to say the least. The bug was that the host name should have
2366 appeared instead of "NULL".
2367
2368 10. Since release 3.03, if Exim is called by a uid other than root or the Exim
2369 user that is built into the binary, and the -C or -D options is used, root
2370 privilege is dropped before the configuration file is read. In addition,
2371 logging is switched to stderr instead of the normal log files. If the
2372 configuration then re-defines the Exim user, the unprivileged environment
2373 is probably not what is expected, so Exim logs a panic warning message (but
2374 proceeds).
2375
2376 However, if deliver_drop_privilege is set, the unprivileged state may well
2377 be exactly what is intended, so the warning has been cut out in that case,
2378 and Exim is allowed to try to write to its normal log files.
2379
2380
2381 Exim version 4.21
2382 -----------------
2383
2384 1. smtp_return_error_details was not giving details for temporary sender
2385 or receiver verification errors.
2386
2387 2. Diagnose a configuration error if two authenticators have the same public
2388 name.
2389
2390 3. Exim used not to create the message log file for a message until the first
2391 delivery attempt. This could be confusing when incoming messages were held
2392 for policy or load reasons. The message log file is now created at the time
2393 the message is received, and an initial "Received" line is written to it.
2394
2395 4. The automatically generated man page for command line options had a minor
2396 bug that caused no ill effects; however, a more serious problem was that
2397 the procedure for building the man page automatically didn't always
2398 operate. Consequently, release 4.20 contains an out-of-date version. This
2399 shouldn't happen again.
2400
2401 5. When building Exim with embedded Perl support, the script that builds the
2402 Makefile was calling 'perl' to find its compile-time parameters, ignoring
2403 any setting of PERL_COMMAND in Local/Makefile. This is now fixed.
2404
2405 6. The freeze_tell option was not being used for messages that were frozen on
2406 arrival, either by an ACL or by local_scan().
2407
2408 7. Added the smtp_incomplete_transaction log selector.
2409
2410 8. After STARTTLS, Exim was not forgetting that it had advertised AUTH, so it
2411 was accepting AUTH without a new EHLO.
2412
2413 9. Added tls_remember_esmtp to cope with YAEB. This allows AUTH and other
2414 ESMTP extensions after STARTTLS without a new EHLO, in contravention of the
2415 RFC.
2416
2417 10. Logging of TCP/IP connections (when configured) now happens in the main
2418 daemon process instead of the child process, so that the TCP/IP connection
2419 count is more accurate (but it can never be perfect).
2420
2421 11. The use of "drop" in a nested ACL was not being handled correctly in the
2422 outer ACL. Now, if condition failure induced by the nested "drop" causes
2423 the outer ACL verb to deny access ("accept" or "discard" after "endpass",
2424 or "require"), the connection is dropped.
2425
2426 12. Similarly, "discard" in a nested ACL wasn't being handled. A nested ACL
2427 that yield "discard" can now be used with an "accept" or a "discard" verb,
2428 but an error is generated for any others (because I can't see a useful way
2429 to define what should happen).
2430
2431 13. When an ACL is read dynamically from a file (or anywhere else), the lines
2432 are now processed in the same way as lines in the Exim configuration file.
2433 In particular, continuation lines are supported.
2434
2435 14. Added the "dnslists = a.b.c!=n.n.n.n" feature.
2436
2437 15. Added -ti meaning -t -i.
2438
2439 16. Check for letters, digits, hyphens, and dots in the names of dnslist
2440 domains, and warn by logging if others are found.
2441
2442 17. At least on BSD, alignment is not guarenteed for the array of ifreq's
2443 returned from GIFCONF when Exim is trying to find the list of interfaces on
2444 a host. The code in os.c has been modified to copy each ifreq to an aligned
2445 structure in all cases.
2446
2447 Also, in some cases, the returned ifreq's were being copied to a 'struct
2448 ifreq' on the stack, which was subsequently passed to host_ntoa(). That
2449 means the last couple of bytes of an IPv6 address could be chopped if the
2450 ifreq contained only a normal sockaddr (14 bytes storage).
2451
2452 18. Named domain lists were not supported in the hosts_treat_as_local option.
2453 An entry such as +xxxx was not recognized, and was treated as a literal
2454 domain name.
2455
2456 19. Ensure that header lines added by a DATA ACL are included in the reject log
2457 if the ACL subsequently rejects the message.
2458
2459 20. Upgrade the cramtest.pl utility script to use Digest::MD5 instead of just
2460 MD5 (which is deprecated).
2461
2462 21. When testing a filter file using -bf, Exim was writing a message when it
2463 took the sender from a "From " line in the message, but it was not doing so
2464 when it took $return_path from a Return-Path: header line. It now does.
2465
2466 22. If the contents of a "message" modifier for a "warn" ACL verb do not begin
2467 with a valid header line field name (a series of printing characters
2468 terminated by a colon, Exim now inserts X-ACL-Warn: at the beginning.
2469
2470 23. Changed "disc" in the source to "disk" to conform to the documentation and
2471 the book and for uniformity.
2472
2473 24. Ignore Sendmail's -Ooption=value command line item.
2474
2475 25. When execve() failed while trying to run a command in a pipe transport,
2476 Exim was returning EX_UNAVAILBLE (69) from the subprocess. However, this
2477 could be confused with a return value of 69 from the command itself. This
2478 has been changed to 127, the value the shell returns if it is asked to run
2479 a non-existent command. The wording for the related log line suggests a
2480 non-existent command as the problem.
2481
2482 26. If received_header_text expands to an empty string, do not add a Received:
2483 header line to the message. (Well, it adds a token one on the spool, but
2484 marks it "old" so that it doesn't get used or transmitted.)
2485
2486 27. Installed eximstats 1.28 (addition of -nt option).
2487
2488 28. There was no check for failure on the call to getsockname() in the daemon
2489 code. This can fail if there is a shortage of resources on the system, with
2490 ENOMEM, for example. A temporary error is now given on failure.
2491
2492 29. Contrary to the C standard, it seems that in some environments, the
2493 equivalent of setlocale(LC_ALL, "C") is not obeyed at the start of a C
2494 program. Exim now does this explicitly; it affects the formatting of
2495 timestamps using strftime().
2496
2497 30. If exiqsumm was given junk data, it threw up some uninitialized variable
2498 complaints. I've now initialized all the variables, to avoid this.
2499
2500 32. Header lines added by a system filter were not being "seen" during
2501 transport-time rewrites.
2502
2503 33. The info_callback() function passed to OpenSSL is set up with type void
2504 (*)(SSL *, int, int), as described somewhere. However, when calling the
2505 function (actually a macro) that sets it up, the type void(*)() is
2506 expected. I've put in a cast to prevent warnings from picky compilers.
2507
2508 34. If a DNS black list lookup found a CNAME record, but there were no A
2509 records associated with the domain it pointed at, Exim crashed.
2510
2511 35. If a DNS black list lookup returned more than one A record, Exim ignored
2512 all but the first. It now scans all returned addresses if a particular IP
2513 value is being sought. In this situation, the contents of the
2514 $dnslist_value variable are a list of all the addresses, separated by a
2515 comma and a space.
2516
2517 36. Tightened up the rules for host name lookups using reverse DNS. Exim used
2518 to accept a host name and all its aliases if the forward lookup for any of
2519 them yielded the IP address of the incoming connection. Now it accepts only
2520 those names whose forward lookup yields the correct IP address. Any other
2521 names are discarded. This closes a loophole whereby a rogue DNS
2522 administrator could create reverse DNS records to break through a
2523 wildcarded host restriction in an ACL.
2524
2525 37. If a user filter or a system filter that ran in a subprocess used any of
2526 the numerical variables ($1, $2 etc), or $thisaddress, in a pipe command,
2527 the wrong values were passed to the pipe command ($thisaddress had the
2528 value of $0, $0 had the value of $1, etc). This bug was introduced by
2529 change 4.11/101, and not discovered because I wrote an inadequate test. :-(
2530
2531 38. Improved the line breaking for long SMTP error messages from ACLs.
2532 Previously, if there was no break point between 40 and 75 characters, Exim
2533 left the rest of the message alone. Two changes have been made: (a) I've
2534 reduced the minimum length to 35 characters; (b) if it can't find a break
2535 point between 35 and 75 characters, it looks ahead and uses the first one
2536 that it finds. This may give the occasional overlong line, but at least the
2537 remaining text gets split now.
2538
2539 39. Change 82 of 4.11 was unimaginative. It assumed the limit on the number of
2540 file descriptors might be low, and that setting 1000 would always raise it.
2541 It turns out that in some environments, the limit is already over 1000 and
2542 that lowering it causes trouble. So now Exim takes care not to decrease it.
2543
2544 40. When delivering a message, the value of $return_path is set to $sender_
2545 address at the start of routing (routers may change the value). By an
2546 oversight, this default was not being set up when an address was tested by
2547 -bt or -bv, which affected the outcome if any router or filter referred to
2548 $return_path.
2549
2550 41. The idea of the "warn" ACL verb is that it adds a header or writes to the
2551 log only when "message" or "log_message" are set. However, if one of the
2552 conditions was an address verification, or a call to a nested ACL, the
2553 messages generated by the underlying test were being passed through. This
2554 no longer happens. The underlying message is available in $acl_verify_
2555 message for both "message" and "log_message" expansions, so it can be
2556 passed through if needed.
2557
2558 42. Added RFC 2047 interpretation of header lines for $h_ expansions, with a
2559 new expansion $bh_ to give the encoded byte string without charset
2560 translation. Translation happens only if iconv() is available; HAVE_ICONV
2561 indicates this at build time. HEADERS_CHARSET gives the charset to
2562 translate to; headers_charset can change it in the configuration, and
2563 "headers charset" can change it in an individual filter file.
2564
2565 43. Now that we have a default RFC 2047 charset (see above), the code in Exim
2566 that creates RFC 2047 encoded "words" labels them as that charset instead
2567 of always using iso-8859-1. The cases are (i) the explicit ${rfc2047:
2568 expansion operator; (ii) when Exim creates a From: line for a local
2569 message; (iii) when a header line is rewritten to include a "phrase" part.
2570
2571 44. Nasty bug in exiqsumm: the regex to skip already-delivered addresses was
2572 buggy, causing it to skip the first lines of messages whose message ID
2573 ended in 'D'. This would not have bitten before Exim release 4.14, because
2574 message IDs were unlikely to end in 'D' before then. The effect was to have
2575 incorrect size information for certain domains.
2576
2577 45. #include "config.h" was missing at the start of the crypt16.c module. This
2578 caused trouble on Tru64 (aka OSF1) systems, because HAVE_CRYPT16 was not
2579 noticed.
2580
2581 46. If there was a timeout during a "random" callout check, Exim treated it as
2582 a failure of the random address, and carried on sending RSET and the real
2583 address. If the delay was just some slowness somewhere, the response to the
2584 original RCPT would be taken as a response to RSET and so on, causing
2585 mayhem of various kinds.
2586
2587 47. Change 50 for 4.20 was a heap of junk. I don't know what I was thinking
2588 when I implemented it. It didn't allow for the fact that some option values
2589 may legitimatetly be negative (e.g. size_addition), and it didn't even do
2590 the right test for positive values.
2591
2592 48. Domain names in DNS records are case-independent. Exim always looks them up
2593 in lower case. Some resolvers return domain names in exactly the case they
2594 appear in the zone file, that is, they may contain uppercase letters. Not
2595 all resolvers do this - some return always lower case. Exim was treating a
2596 change of case by a resolver as a change of domain, similar to a widening
2597 of a domain abbreviation. This triggered its re-routing code and so it was
2598 trying to route what was effectively the same domain again. This normally
2599 caused routing to fail (because the router wouldn't handle the domain
2600 twice). Now Exim checks for this case specially, and just changes the
2601 casing of the domain that it ultimately uses when it transmits the message
2602 envelope.
2603
2604 49. Added Sieve (RFC 3028) support, courtesy of Michael Haardt's contributed
2605 module.
2606
2607 50. If a filter generated a file delivery with a non-absolute name (possible if
2608 no home directory exists for the router), the forbid_file option was not
2609 forbidding it.
2610
2611 51. Added '&' feature to dnslists, to provide bit mask matching in addition to
2612 the existing equality matching.
2613
2614 52. Exim was using ints instead of ino_t variables in some places where it was
2615 dealing with inode numbers.
2616
2617 53. If TMPDIR is defined in Local/Makefile (default in src/EDITME is
2618 TMPDIR="/tmp"), Exim checks for the presence of an environment variable
2619 called TMPDIR, and if it finds it is different, it changes its value.
2620
2621 54. The smtp_printf() function is now made available to local_scan() so
2622 additional output lines can be written before returning. There is also an
2623 smtp_fflush() function to enable the detection of a dropped connection.
2624 The variables smtp_input and smtp_batched_input are exported to
2625 local_scan().
2626
2627 55. Changed the default runtime configuration: the message "Unknown user"
2628 has been removed from the ACL, and instead placed on the localuser router,
2629 using the cannot_route_message feature. This means that any verification
2630 failures that generate their own messages won't get overridden. Similarly,
2631 the "Unrouteable address" message that was in the ACL for unverifiable
2632 relay addresses has also been removed.
2633
2634 56. Added hosts_avoid_esmtp to the smtp transport.
2635
2636 57. The exicyclog script was not checking for the esoteric option
2637 CONFIGURE_FILE_USE_EUID in the Local/Makefile. It now does this, but it
2638 will work only if exicyclog is run under the appropriate euid.
2639
2640 58. Following a discussion on the list, the rules by which Exim recognises line
2641 endings on incoming messages have been changed. The -dropcr and drop_cr
2642 options are now no-ops, retained only for backwards compatibility. The
2643 following line terminators are recognized: LF CRLF CR. However, special
2644 processing applies to CR:
2645
2646 (i) The sequence CR . CR does *not* terminate an incoming SMTP message,
2647 nor a local message in the state where . is a terminator.
2648
2649 (ii) If a bare CR is encountered in a header line, an extra space is added
2650 after the line terminator so as not to end the header. The reasoning
2651 behind this is that bare CRs in header lines are most likely either
2652 to be mistakes, or people trying to play silly games.
2653
2654 59. The size of a message, as listed by "-bp" or in the Exim monitor window,
2655 was being incorrectly given as 18 bytes larger than it should have been.
2656 This is a VOB (very old bug).
2657
2658 60. This may never have affected anything current, but just in case it has:
2659 When the local host is found other than at the start of a list of hosts,
2660 the local host, those with the same MX, and any that follow, are discarded.
2661 When the list in question was part of a longer list of hosts, the following
2662 hosts (not currently being processed) were also being discarded. This no
2663 longer happens. I'm not sure if this situation could ever has previously
2664 arisen.
2665
2666 61. Added the "/MX" feature to lists of hosts in the manualroute and query
2667 program routers.
2668
2669 62. Whenever Exim generates a new message, it now adds an Auto-Submitted:
2670 header. This is something that is recommended in a new Internet Draft, and
2671 is something that is documented as being done by Sendmail. There are two
2672 possible values. For messages generated by the autoreply transport, Exim
2673 adds:
2674
2675 Auto-Submitted: auto-replied
2676
2677 whereas for all other generated messages (e.g. bounces) it adds
2678
2679 Auto-Submitted: auto-generated
2680
2681 63. The "personal" condition in filters now includes a test for the
2682 Auto-Submitted: header. If it contains the string "auto-" the message it
2683 not considered personal.
2684
2685 64. Added rcpt_include_affixes as a generic transport option.
2686
2687 65. Added queue_only_override (default true).
2688
2689 66. Added the syslog_duplication option.
2690
2691 67. If what should have been the first header line of a message consisted of
2692 a space followed by a colon, Exim was mis-interpreting it as a header line.
2693 It isn't of course - it is syntactically invalid and should therefore be
2694 treated as the start of the message body. The misbehaviour could have
2695 caused a number of strange effects, including loss of data in subsequent
2696 header lines, and spool format errors.
2697
2698 68. Formerly, the AUTH parameter on a MAIL command was trusted only if the
2699 client host had authenticated. This control can now be exercised by an ACL
2700 for more flexibility.
2701
2702 69. By default, callouts do not happen when testing with -bh. There is now a
2703 variant, -bhc, which does actually run the callout code, including
2704 consulting and updating the callout cache.
2705
2706 70. Added support for saslauthd authentication, courtesy of Alexander
2707 Sabourenkov.
2708
2709 71. If statvfs() failed on the spool or log directories while checking their
2710 size for availability, Exim confusingly gave the error "space shortage".
2711 Furthermore, in debugging mode it crashed with a floating point exception.
2712 These checks are done if check_{spool,log}_{space,inodes} are set, and when
2713 an SMTP message arrives with SIZE= on the MAIL command. As this is a really
2714 serious problem, Exim now writes to the main and panic logs when this
2715 happens, with details of the failure. It then refuses to accept the
2716 incoming message, giving the message "spool directory problem" or "log
2717 directory problem" with a 421 code for SMTP messages.
2718
2719 72. When Exim is about to re-exec itself, it ensures that the file descriptors
2720 0, 1, and 2 exist, because some OS complain for execs without them (see
2721 ChangeLog 4.05/30). If necessary, Exim opens /dev/null to use for these
2722 descriptors. However, the code omitted to check that the open succeeded,
2723 causing mysterious errors if for some reason the permissions on /dev/null
2724 got screwed. Now Exim writes a message to the main and panic logs, and
2725 bombs out if it can't open /dev/null.
2726
2727 73. Re-vamped the way daemon_smtp_port, local_interfaces, and -oX work and
2728 interact so that it is all more flexible. It is supposed to remain
2729 backwards compatible. Also added extra_local_interfaces.
2730
2731 74. Invalid data sent to a SPA (NTLM) server authenticator could cause the code
2732 to bomb out with an assertion failure - to the client this appears as a
2733 connection drop. This problem occurs in the part of the code that was taken
2734 from the Samba project. Fortunately, the assertion is in a very simple
2735 function, so I have fixed this by reproducing the function inline in the
2736 one place where it is called, and arranging for authentication to fail
2737 instead of killing the process with assert().
2738
2739 75. The SPA client code was not working when the server requested OEM rather
2740 than Unicode encoding.
2741
2742 76. Added code to make require_files with a specific uid setting more usable in
2743 the case where statting the file as root fails - usually a non-root-mounted
2744 NFS file system. When this happens and the failure is EACCES, Exim now
2745 forks a subprocess and does the per-uid checking as the relevant uid.
2746
2747 77. Added process_log_path.
2748
2749 78. If log_file_path was not explicitly set, a setting of check_log_space or
2750 check_log_inodes was ignored.
2751
2752 79. If a space check for the spool or log partitions fails, the incident is now
2753 logged. Of course, in the latter case the data may get lost...
2754
2755 80. Added the %p formatting code to string_format() so that it can be used to
2756 print addresses in debug_print(). Adjusted all the address printing in the
2757 debugging in store.c to use %p rather than %d.
2758
2759 81. There was a concern that a line of code in smtp_in.c could overflow a
2760 buffer if a HELO/EHLO command was given followed by 500 or so spaces. As
2761 initially expressed, the concern was not well-founded, because trailing
2762 spaces are removed early. However, if the trailing spaces were followed by
2763 a NULL, they did not get removed, so the overflow was possible. Two fixes
2764 were applied:
2765
2766 (a) I re-wrote the offending code in a cleaner fashion.
2767 (b) If an incoming SMTP command contains a NULL character, it is rejected
2768 as invalid.
2769
2770 82. When Exim changes uid/gid to the Exim user at daemon start time, it now
2771 runs initgroups(), so that if the Exim user is in any additional groups,
2772 they will be used during message reception.
2773
2774
2775 Exim version 4.20
2776 -----------------
2777
2778 The change log for 4.20 and earlier releases has been archived.
2779
2780 ****