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