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