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