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