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