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