1 $Cambridge: exim/doc/doc-txt/ChangeLog,v 1.132 2005/05/03 14:20:00 ph10 Exp $
3 Change log file for Exim from version 4.21
4 -------------------------------------------
10 TK/01 Added Yahoo DomainKeys support via libdomainkeys. See
11 doc/experimental-spec.txt for details. (http://domainkeys.sf.net)
13 TK/02 Fix ACL "control" statement not being available in MIME ACL.
15 TK/03 Fix ACL "regex" condition not being available in MIME ACL.
17 PH/01 Installed a patch from the Sieve maintainer that allows -bf to be used
18 to test Sieve filters that use "vacation".
20 PH/02 Installed a slightly modified version of Nikos Mavrogiannopoulos' patch
21 that changes the way the GnuTLS parameters are stored in the cache file.
22 The new format can be generated externally. For backward compatibility,
23 if the data in the cache doesn't make sense, Exim assumes it has read an
24 old-format file, and it generates new data and writes a new file. This
25 means that you can't go back to an older release without removing the
28 PH/03 A redirect router that has both "unseen" and "one_time" set does not
29 work if there are any delivery delays because "one_time" forces the
30 parent to be marked "delivered", so its unseen clone is never tried
31 again. For this reason, Exim now forbids the simultaneous setting of
34 PH/04 Change 4.11/85 fixed an obscure bug concerned with addresses that are
35 redirected to themselves ("homonym" addresses). Read the long ChangeLog
36 entry if you want to know the details. The fix, however, neglected to
37 consider the case when local delivery batching is involved. The test for
38 "previously delivered" was not happening when checking to see if an
39 address could be batched with a previous (undelivered) one; under
40 certain circumstances this could lead to multiple deliveries to the same
43 PH/05 Renamed the macro SOCKLEN_T as EXIM_SOCKLEN_T because AIX uses SOCKLEN_T
44 in its include files, and this causes problems building Exim.
46 PH/06 A number of "verify =" ACL conditions have no options (e.g. verify =
47 header_syntax) but Exim was just ignoring anything given after a slash.
48 In particular, this caused confusion with an attempt to use "verify =
49 reverse_host_lookup/defer_ok". An error is now given when options are
50 supplied for verify items that do not have them. (Maybe reverse_host_
51 lookup should have a defer_ok option, but that's a different point.)
53 PH/07 Increase the size of the buffer for incoming SMTP commands from 512 (as
54 defined by RFC 821) to 2048, because there were problems with some AUTH
55 commands, and RFC 1869 says the size should be increased for extended
56 SMTP commands that take arguments.
58 PH/08 Added ${dlfunc dynamically loaded function for expansion (code from Tony
61 PH/09 Previously, an attempt to use ${perl when it wasn't compiled gave an
62 "unknown" error; now it says that the functionality isn't in the binary.
64 PH/10 Added a nasty fudge to try to recognize and flatten LDAP passwords in
65 an address' error message when a string expansion fails (syntax or
66 whatever). Otherwise the password may appear in the log. Following change
67 PH/42 below, there is no longer a chance of it appearing in a bounce
70 PH/11 Installed exipick version 20050225.0 from John Jetmore.
72 PH/12 If the last host in a fallback_hosts list was multihomed, only the first
73 of its addresses was ever tried. (Bugzilla bug #2.)
75 PH/13 If "headers_add" in a transport didn't end in a newline, Exim printed
76 the result incorrectly in the debug output. (It correctly added a newline
77 to what was transported.)
79 TF/01 Added $received_time.
81 PH/14 Modified the default configuration to add an acl_smtp_data ACL, with
82 commented out examples of how to interface to a virus scanner and to
83 SpamAssassin. Also added commented examples of av_scanner and
84 spamd_address settings.
86 PH/15 Further to TK/02 and TK/03 above, tidied up the tables of what conditions
87 and controls are allowed in which ACLs. There were a couple of minor
88 errors. Some of the entries in the conditions table (which is a table of
89 where they are NOT allowed) were getting very unwieldy; rewrote them as a
90 negation of where the condition IS allowed.
92 PH/16 Installed updated OS/os.c-cygwin from the Cygwin maintainer.
94 PH/17 The API for radiusclient changed at release 0.4.0. Unfortunately, the
95 header file does not have a version number, so I've had to invent a new
96 value for RADIUS_LIB_TYPE, namely "RADIUSCLIENTNEW" to request the new
97 API. The code is untested by me (my Linux distribution still has 0.3.2 of
98 radiusclient), but it was contributed by a Radius user.
100 PH/18 Installed Lars Mainka's patch for the support of CRL collections in
101 files or directories, for OpenSSL.
103 PH/19 When an Exim process that is running as root has to create an Exim log
104 file, it does so in a subprocess that runs as exim:exim so as to get the
105 ownership right at creation (otherwise, other Exim processes might see
106 the file with the wrong ownership). There was no test for failure of this
107 fork() call, which would lead to the process getting stuck as it waited
108 for a non-existent subprocess. Forks do occasionally fail when resources
109 run out. I reviewed all the other calls to fork(); they all seem to check
112 PH/20 When checking for unexpected SMTP input at connect time (before writing
113 the banner), Exim was not dealing correctly with a non-positive return
114 from the read() function. If the client had disconnected by this time,
115 the result was a log entry for a synchronization error with an empty
116 string after "input=" when read() returned zero. If read() returned -1
117 (an event I could not check), uninitialized data bytes were printed.
118 There were reports of junk text (parts of files, etc) appearing after
121 PH/21 Added acl_not_smtp_mime to allow for MIME scanning for non-SMTP messages.
123 PH/22 Added support for macro redefinition, and (re)definition in between
124 driver and ACL definitions.
126 PH/23 The cyrus_sasl authenticator was expanding server_hostname, but then
127 forgetting to use the resulting value; it was using the unexpanded value.
129 PH/24 The cyrus_sasl authenticator was advertising mechanisms for which it
130 hadn't been configured. The fix is from Juergen Kreileder, who
131 understands it better than I do:
133 "Here's what I see happening with three configured cyrus_sasl
134 authenticators configured (plain, login, cram-md5):
136 On startup auth_cyrus_sasl_init() gets called for each of these.
137 This means three calls to sasl_listmech() without a specified mech_list.
138 => SASL tests which mechs of all available mechs actually work
139 => three warnings about OTP not working
140 => the returned list contains: plain, login, cram-md5, digest-md5, ...
142 With the patch, sasl_listmech() also gets called three times. But now
143 SASL's mech_list option is set to the server_mech specified in the the
144 authenticator. Or in other words, the answer from sasl_listmech()
145 gets limited to just the mech you're testing for (which is different
147 => the return list contains just 'plain' or 'login', 'cram-md5' or
148 nothing depending on the value of ob->server_mech.
150 I've just tested the patch: Authentication still works fine,
151 unavailable mechs specified in the exim configuration are still
152 caught, and the auth.log warnings about OTP are gone."
154 PH/25 When debugging is enabled, the contents of the command line are added
155 to the debugging output, even when log_selector=+arguments is not
158 PH/26 Change scripts/os-type so that when "uname -s" returns just "GNU", the
159 answer is "GNU", and only if the return is "GNU/something" is the answer
162 PH/27 $acl_verify_message is now set immediately after the failure of a
163 verification in an ACL, and so is available in subsequent modifiers. In
164 particular, the message can be preserved by coding like this:
166 warn !verify = sender
167 set acl_m0 = $acl_verify_message
169 Previously, $acl_verify_message was set only while expanding "message"
170 and "log_message" when a very denied access.
172 PH/28 Modified OS/os.c-Linux with
174 -#ifndef OS_LOAD_AVERAGE
175 +#if !defined(OS_LOAD_AVERAGE) && defined(__linux__)
177 to make Exim compile on kfreebsd-gnu. (I'm totally confused about the
178 nomenclature these days.)
180 PH/29 Installed patch from the Sieve maintainer that adds the options
181 sieve_useraddress and sieve_subaddress to the redirect router.
183 PH/30 In these circumstances:
184 . Two addresses routed to the same list of hosts;
185 . First host does not offer TLS;
186 . First host accepts first address;
187 . First host gives temporary error to second address;
188 . Second host offers TLS and a TLS session is established;
189 . Second host accepts second address.
190 Exim incorrectly logged both deliveries with the TLS parameters (cipher
191 and peerdn, if requested) that were in fact used only for the second
194 PH/31 When doing a callout as part of verifying an address, Exim was not paying
195 attention to any local part prefix or suffix that was matched by the
196 router that accepted the address. It now behaves in the same way as it
197 does for delivery: the affixes are removed from the local part unless
198 rcpt_include_affixes is set on the transport.
200 PH/32 Add the sender address, as F=<...>, to the log line when logging a
201 timeout during the DATA phase of an incoming message.
203 PH/33 Sieve envelope tests were broken for match types other than :is. I have
204 applied a patch sanctioned by the Sieve maintainer.
206 PH/34 Change 4.50/80 broke Exim in that it could no longer handle cases where
207 the uid or gid is negative. A case of a negative gid caused this to be
208 noticed. The fix allows for either to be negative.
210 PH/35 ACL_WHERE_MIME is now declared unconditionally, to avoid too much code
211 clutter, but the tables that are indexed by ACL_WHERE_xxx values had been
214 PH/36 The change PH/12 above was broken. Fixed it.
216 PH/37 Exim used to check for duplicate addresses in the middle of routing, on
217 the grounds that routing the same address twice would always produce the
218 same answer. This might have been true once, but it is certainly no
219 longer true now. Routing a child address may depend on the previous
220 routing that produced that child. Some complicated redirection strategies
221 went wrong when messages had multiple recipients, and made Exim's
222 behaviour dependent on the order in which the addresses were given.
224 I have moved the duplicate checking until after the routing is complete.
225 Exim scans the addresses that are assigned to local and remote
226 transports, and removes any duplicates. This means that more work will be
227 done, as duplicates will always all be routed, but duplicates are
228 presumably rare, so I don't expect this is of any significance.
230 For deliveries to pipes, files, and autoreplies, the duplicate checking
231 still happens during the routing process, since they are not going to be
234 PH/38 Installed a patch from Ian Freislich, with the agreement of Tom Kistner.
235 It corrects a timeout issue with spamd. This is Ian's comment: "The
236 background is that sometimes spamd either never reads data from a
237 connection it has accepted, or it never writes response data. The exiscan
238 spam.[ch] uses a 3600 second timeout on spamd socket reads, further, it
239 blindly assumes that writes won't block so it may never time out."
241 PH/39 Allow G after quota size as well as K and M.
243 PH/40 The value set for $authenticated_id in an authenticator may not contain
244 binary zeroes or newlines because the value is written to log lines and
245 to spool files. There was no check on this. Now the value is run through
246 the string_printing() function so that such characters are converted to
247 printable escape sequences.
249 PH/41 $message_linecount is a new variable that contains the total number of
250 lines in the message. Compare $body_linecount, which is the count for the
253 PH/42 Exim no longer gives details of delivery errors for specific addresses in
254 bounce and delay warning messages, except in certain special cases, which
257 (a) An SMTP error message from a remote host;
258 (b) A message specified in a :fail: redirection;
259 (c) A message specified in a "fail" command in a system filter;
260 (d) A message specified in a FAIL return from the queryprogram router;
261 (e) A message specified by the cannot_route_message router option.
263 In these cases only, Exim does include the error details in bounce and
264 warning messages. There are also a few cases where bland messages such
265 as "unrouteable address" or "local delivery error" are given.
267 PH/43 $value is now also set for the "else" part of a ${run expansion.
269 PH/44 Applied patch from the Sieve maintainer: "The vacation draft is still
270 being worked on, but at least Exim now implements the latest version to
273 PH/45 In a pipe transport, although a timeout while waiting for the pipe
274 process to complete was treated as a delivery failure, a timeout while
275 writing the message to the pipe was logged, but erroneously treated as a
276 successful delivery. Such timeouts include transport filter timeouts. For
277 consistency with the overall process timeout, these timeouts are now
278 treated as errors, giving rise to delivery failures by default. However,
279 there is now a new Boolean option for the pipe transport called
280 timeout_defer, which, if set TRUE, converts the failures into defers for
281 both kinds of timeout. A transport filter timeout is now identified in
285 A note about Exim versions 4.44 and 4.50
286 ----------------------------------------
288 Exim 4.50 was meant to be the next release after 4.43. It contains a lot of
289 changes of various kinds. As a consequence, a big documentation update was
290 needed. This delayed the release for rather longer than seemed good, especially
291 in the light of a couple of (minor) security issues. Therefore, the changes
292 that fixed bugs were backported into 4.43, to create a 4.44 maintenance
293 release. So 4.44 and 4.50 are in effect two different branches that both start
296 I have left the 4.50 change log unchanged; it contains all the changes since
297 4.43. The change log for 4.44 is below; many of its items are identical to
298 those for 4.50. This seems to be the most sensible way to preserve the
299 historical information.
305 1. Minor wording change to the doc/README.SIEVE file.
307 2. Change 4.43/35 introduced a bug: if quota_filecount was set, the
308 computation of the current number of files was incorrect.
310 3. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
311 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
314 4. Give more explanation in the error message when the command for a transport
315 filter fails to execute.
317 5. There are several places where Exim runs a non-Exim command in a
318 subprocess. The SIGUSR1 signal should be disabled for these processes. This
319 was being done only for the command run by the queryprogram router. It is
320 now done for all such subprocesses. The other cases are: ${run, transport
321 filters, and the commands run by the lmtp and pipe transports.
323 6. Added CONFIGURE_GROUP build-time option.
325 7. Some older OS have a limit of 256 on the maximum number of file
326 descriptors. Exim was using setrlimit() to set 1000 as a large value
327 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
328 systems. I've change it so that if it can't get 1000, it tries for 256.
330 8. "control=submission" was allowed, but had no effect, in a DATA ACL. This
331 was an oversight, and furthermore, ever since the addition of extra
332 controls (e.g. 4.43/32), the checks on when to allow different forms of
333 "control" were broken. There should now be diagnostics for all cases when a
334 control that does not make sense is encountered.
336 9. Added the /retain_sender option to "control=submission".
338 10. $recipients is now available in the predata ACL (oversight).
340 11. Tidy the search cache before the fork to do a delivery from a message
341 received from the command line. Otherwise the child will trigger a lookup
342 failure and thereby defer the delivery if it tries to use (for example) a
343 cached ldap connection that the parent has called unbind on.
345 12. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
346 of $address_data from the recipient verification was clobbered by the
349 13. The value of address_data from a sender verification is now available in
350 $sender_address_data in subsequent conditions in the ACL statement.
352 14. Added forbid_sieve_filter and forbid_exim_filter to the redirect router.
354 15. Added a new option "connect=<time>" to callout options, to set a different
357 16. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
358 was its contents. (It was OK if the option was not defined at all.)
360 17. A "Completed" log line is now written for messages that are removed from
361 the spool by the -Mrm option.
363 18. New variables $sender_verify_failure and $recipient_verify_failure contain
364 information about exactly what failed.
366 19. Added -dd to debug only the daemon process.
368 20. Incorporated Michael Haardt's patch to ldap.c for improving the way it
369 handles timeouts, both on the server side and network timeouts. Renamed the
370 CONNECT parameter as NETTIMEOUT (but kept the old name for compatibility).
372 21. The rare case of EHLO->STARTTLS->HELO was setting the protocol to "smtp".
373 It is now set to "smtps".
375 22. $host_address is now set to the target address during the checking of
378 23. When checking ignore_target_hosts for an ipliteral router, no host name was
379 being passed; this would have caused $sender_host_name to have been used if
380 matching the list had actually called for a host name (not very likely,
381 since this list is usually IP addresses). A host name is now passed as
384 24. Changed the calls that set up the SIGCHLD handler in the daemon to use the
385 code that specifies a non-restarting handler (typically sigaction() in
386 modern systems) in an attempt to fix a rare and obscure crash bug.
388 25. Narrowed the window for a race in the daemon that could cause it to ignore
389 SIGCHLD signals. This is not a major problem, because they are used only to
390 wake it up if nothing else does.
392 26. A malformed maildirsize file could cause Exim to calculate negative values
393 for the mailbox size or file count. Odd effects could occur as a result.
394 The maildirsize information is now recalculated if the size or filecount
397 27. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
398 support for a long time. Removed HAVE_SYS_VFS_H.
400 28. Installed the latest version of exipick from John Jetmore.
402 29. In an address list, if the pattern was not a regular expression, an empty
403 subject address (from a bounce message) matched only if the pattern was an
404 empty string. Non-empty patterns were not even tested. This was the wrong
405 because it is perfectly reasonable to use an empty address as part of a
406 database query. An empty address is now tested by patterns that are
407 lookups. However, all the other forms of pattern expect the subject to
408 contain a local part and a domain, and therefore, for them, an empty
409 address still always fails if the pattern is not itself empty.
411 30. Exim went into a mad DNS loop when attempting to do a callout where the
412 host was specified on an smtp transport, and looking it up yielded more
415 31. Re-factored the code for checking spool and log partition space into a
416 function that finds that data and another that does the check. The former
417 is then used to implement four new variables: $spool_space, $log_space,
418 $spool_inodes, and $log_inodes.
420 32. The RFC2047 encoding function was originally intended for short strings
421 such as real names; it was not keeping to the 75-character limit for
422 encoded words that the RFC imposes. It now respects the limit, and
423 generates multiple encoded words if necessary. To be on the safe side, I
424 have increased the buffer size for the ${rfc2047: expansion operator from
427 33. It is now permitted to omit both strings after an "if" condition; if the
428 condition is true, the result is "true". As before, when the second string
429 is omitted, a false condition yields an empty string. This makes it less
430 cumbersome to write custom ACL and router conditions.
432 34. Failure to deliver a bounce message always caused it to be frozen, even if
433 there was an errors_to setting on the router. The errors_to setting is now
436 35. If an IPv6 address is given for -bh or -bhc, it is now converted to the
437 canonical form (fully expanded) before being placed in
438 $sender_host_address.
440 36. The table in the code that translates DNS record types into text (T_A to
441 "A" for instance) was missing entries for NS and CNAME. It is just possible
442 that this could have caused confusion if both these types were looked up
443 for the same domain, because the text type is used as part of Exim's
444 per-process caching. But the chance of anyone hitting this buglet seems
447 37. The dnsdb lookup has been extended in a number of ways.
449 (1) There is a new type, "zns", which walks up the domain tree until it
450 finds some nameserver records. It should be used with care.
452 (2) There is a new type, "mxh", which is like "mx" except that it returns
453 just the host names, not the priorities.
455 (3) It is now possible to give a list of domains (or IP addresses) to be
456 looked up. The behaviour when one of the lookups defers can be
457 controlled by a keyword.
459 (4) It is now possible to specify the separator character for use when
460 multiple records are returned.
462 38. The dnslists ACL condition has been extended: it is now possible to supply
463 a list of IP addresses and/or domains to be looked up in a particular DNS
466 39. Added log_selector=+queue_time_overall.
468 40. When running the queue in the test harness, wait just a tad after forking a
469 delivery process, to get repeatability of debugging output.
471 41. Include certificate and key file names in error message when GnuTLS fails
472 to set them up, because the GnuTLS error message doesn't include the name
473 of the failing file when there is a problem reading it.
475 42. Allow both -bf and -bF in the same test run.
477 43. Did the same fix as 41 above for OpenSSL, which had the same infelicity.
479 44. The "Exiscan patch" is now merged into the mainline Exim source.
481 45. Sometimes the final signoff response after QUIT could fail to get
482 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
483 < 0 before doing a fflush(). This bug looks as though it goes back to the
484 introduction of TLS in release 3.20, but "sometimes" must have been rare
485 because the tests only now provoked it.
487 46. Reset the locale to "C" after calling embedded Perl, in case it was changed
488 (this can affect the format of dates).
490 47. exim_tidydb, when checking for the continued existence of a message for
491 which it has found a message-specific retry record, was not finding
492 messages that were in split spool directories. Consequently, it was
493 deleting retry records that should have stayed in existence.
495 48. Steve fixed some bugs in eximstats.
497 49. The SPA authentication driver was not abandoning authentication and moving
498 on to the next authenticator when an expansion was forced to fail,
499 contradicting the general specification for all authenticators. Instead it
500 was generating a temporary error. It now behaves as specified.
502 50. The default ordering of permitted cipher suites for GnuTLS was pessimal
503 (the order specifies the preference for clients). The order is now AES256,
504 AES128, 3DES, ARCFOUR128.
506 51. Small patch to Sieve code - explicitly set From: when generating an
509 52. Exim crashed if a remote delivery caused a very long error message to be
510 recorded - for instance if somebody sent an entire SpamAssassin report back
511 as a large number of 550 error lines. This bug was coincidentally fixed by
512 increasing the size of one of Exim's internal buffers (big_buffer) that
513 happened as part of the Exiscan merge. However, to be on the safe side, I
514 have made the code more robust (and fixed the comments that describe what
517 53. Now that there can be additional text after "Completed" in log lines (if
518 the queue_time_overall log selector is set), a one-byte patch to exigrep
519 was needed to allow it to recognize "Completed" as not the last thing in
522 54. The LDAP lookup was not handling a return of LDAP_RES_SEARCH_REFERENCE. A
523 patch that reportedly fixes this has been added. I am not expert enough to
524 create a test for it. This is what the patch creator wrote:
526 "I found a little strange behaviour of ldap code when working with
527 Windows 2003 AD Domain, where users was placed in more than one
528 Organization Units. When I tried to give exim partial DN, the exit code
529 of ldap_search was unknown to exim because of LDAP_RES_SEARCH_REFERENCE.
530 But simultaneously result of request was absolutely normal ldap result,
531 so I produce this patch..."
533 Later: it seems that not all versions of LDAP support LDAP_RES_SEARCH_
534 REFERENCE, so I have modified the code to exclude the patch when that macro
537 55. Some experimental protocols are using DNS PTR records for new purposes. The
538 keys for these records are domain names, not reversed IP addresses. The
539 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
540 leaves it alone. Component reversal etc. now happens only for IP addresses.
543 56. Improve error message when ldap_search() fails in OpenLDAP or Solaris LDAP.
545 57. Double the size of the debug message buffer (to 2048) so that more of very
546 long debug lines gets shown.
548 58. The exicyclog utility now does better if the number of log files to keep
549 exceeds 99. In this case, it numbers them 001, 002 ... instead of 01, 02...
551 59. Two changes related to the smtp_active_hostname option:
553 (1) $smtp_active_hostname is now available as a variable.
554 (2) The default for smtp_banner uses $smtp_active_hostname instead
555 of $primary_hostname.
557 60. The host_aton() function is supposed to be passed a string that is known
558 to be a valid IP address. However, in the case of IPv6 addresses, it was
559 not checking this. This is a hostage to fortune. Exim now panics and dies
560 if the condition is not met. A case was found where this could be provoked
561 from a dnsdb PTR lookup with an IPv6 address that had more than 8
562 components; fortuitously, this particular loophole had already been fixed
563 by change 4.50/55 above.
565 If there are any other similar loopholes, the new check in host_aton()
566 itself should stop them being exploited. The report I received stated that
567 data on the command line could provoke the exploit when Exim was running as
568 exim, but did not say which command line option was involved. All I could
569 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
573 61. There was a buffer overflow vulnerability in the SPA authentication code
574 (which came originally from the Samba project). I have added a test to the
575 spa_base64_to_bits() function which I hope fixes it.
578 62. Configuration update for GNU/Hurd and variations. Updated Makefile-GNU and
579 os.h-GNU, and added configuration files for GNUkFreeBSD and GNUkNetBSD.
581 63. The daemon start-up calls getloadavg() while still root for those OS that
582 need the first call to be done as root, but it missed one case: when
583 deliver_queue_load_max is set with deliver_drop_privilege. This is
584 necessary for the benefit of the queue runner, because there is no re-exec
585 when deliver_drop_privilege is set.
587 64. A call to exiwhat cut short delays set up by "delay" modifiers in ACLs.
590 65. Caching of lookup data for "hosts =" ACL conditions, when a named host list
591 was in use, was not putting the data itself into the right store pool;
592 consequently, it could be overwritten for a subsequent message in the same
593 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
596 66. Added hosts_max_try_hardlimit to the smtp transport, default 50.
598 67. The string_is_ip_address() function returns 0, 4, or 6, for "no an IP
599 address", "IPv4 address", and "IPv6 address", respectively. Some calls of
600 the function were treating the return as a boolean value, which happened to
601 work because 0=false and not-0=true, but is not correct code.
603 68. The host_aton() function was not handling scoped IPv6 addresses (those
604 with, for example, "%eth0" on the end) correctly.
606 69. Fixed some compiler warnings in acl.c for the bitmaps specified with
607 negated items (that is, ~something) in unsigned ints. Some compilers
608 apparently mutter when there is no cast.
610 70. If an address verification called from an ACL failed, and did not produce a
611 user-specific message (i.e. there was only a "system" message), nothing was
612 put in $acl_verify_message. In this situation, it now puts the system
615 71. Change 4.23/11 added synchronization checking at the start of an SMTP
616 session; change 4.31/43 added the unwanted input to the log line - except
617 that it did not do this in the start of session case. It now does.
619 72. After a timeout in a callout SMTP session, Exim still sent a QUIT command.
620 This is wrong and can cause the other end to generate a synchronization
621 error if it is another Exim or anything else that does the synchronization
622 check. A QUIT command is no longer sent after a timeout.
624 73. $host_lookup_deferred has been added, to make it easier to detect DEFERs
627 74. The defer_ok option of callout verification was not working if it was used
628 when verifying addresses in header lines, that is, for this case:
630 verify = header_sender/callout=defer_ok
632 75. A backgrounded daemon closed stdin/stdout/stderr on entry; this meant that
633 those file descriptors could be used for SMTP connections. If anything
634 wrote to stderr (the example that came up was "warn" in embedded Perl), it
635 could be sent to the SMTP client, causing chaos. The daemon now opens
636 stdin, stdout, and stderr to /dev/null when it puts itself into the
639 76. Arrange for output from Perl's "warn" command to be written to Exim's main
640 log by default. The user can override this with suitable Perl magic.
642 77. The use of log_message on a "discard" ACL verb, which is supposed to add to
643 the log message when discard triggers, was not working for the DATA ACL or
644 for the non-SMTP ACL.
646 78. Error message wording change in sieve.c.
648 79. If smtp_accept_max_per_host was set, the number of connections could be
649 restricted to fewer than expected, because the daemon was trying to set up
650 a new connection before checking whether the processes handling previous
651 connections had finished. The check for completed processes is now done
652 earlier. On busy systems, this bug wouldn't be noticed because something
653 else would have woken the daemon, and it would have reaped the completed
656 80. If a message was submitted locally by a user whose login name contained one
657 or more spaces (ugh!), the spool file that Exim wrote was not re-readable.
658 It caused a spool format error. I have fixed the spool reading code. A
659 related problem was that the "from" clause in the Received: line became
660 illegal because of the space(s). It is now covered by ${quote_local_part.
662 81. Included the latest eximstats from Steve (adds average sizes to HTML Top
665 82. Updated OS/Makefile-AIX as per message from Mike Meredith.
667 83. Patch from Sieve maintainer to fix unterminated string problem in
670 84. Some minor changes to the Linux configuration files to help with other
671 OS variants using glibc.
673 85. One more patch for Sieve to update vacation handling to latest spec.
676 ----------------------------------------------------
677 See the note above about the 4.44 and 4.50 releases.
678 ----------------------------------------------------
684 1. Change 4.43/35 introduced a bug that caused file counts to be
685 incorrectly computed when quota_filecount was set in an appendfile
688 2. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
689 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
692 3. Give more explanation in the error message when the command for a transport
693 filter fails to execute.
695 4. There are several places where Exim runs a non-Exim command in a
696 subprocess. The SIGUSR1 signal should be disabled for these processes. This
697 was being done only for the command run by the queryprogram router. It is
698 now done for all such subprocesses. The other cases are: ${run, transport
699 filters, and the commands run by the lmtp and pipe transports.
701 5. Some older OS have a limit of 256 on the maximum number of file
702 descriptors. Exim was using setrlimit() to set 1000 as a large value
703 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
704 systems. I've change it so that if it can't get 1000, it tries for 256.
706 6. "control=submission" was allowed, but had no effect, in a DATA ACL. This
707 was an oversight, and furthermore, ever since the addition of extra
708 controls (e.g. 4.43/32), the checks on when to allow different forms of
709 "control" were broken. There should now be diagnostics for all cases when a
710 control that does not make sense is encountered.
712 7. $recipients is now available in the predata ACL (oversight).
714 8. Tidy the search cache before the fork to do a delivery from a message
715 received from the command line. Otherwise the child will trigger a lookup
716 failure and thereby defer the delivery if it tries to use (for example) a
717 cached ldap connection that the parent has called unbind on.
719 9. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
720 of $address_data from the recipient verification was clobbered by the
723 10. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
724 was its contents. (It was OK if the option was not defined at all.)
726 11. A "Completed" log line is now written for messages that are removed from
727 the spool by the -Mrm option.
729 12. $host_address is now set to the target address during the checking of
732 13. When checking ignore_target_hosts for an ipliteral router, no host name was
733 being passed; this would have caused $sender_host_name to have been used if
734 matching the list had actually called for a host name (not very likely,
735 since this list is usually IP addresses). A host name is now passed as
738 14. Changed the calls that set up the SIGCHLD handler in the daemon to use the
739 code that specifies a non-restarting handler (typically sigaction() in
740 modern systems) in an attempt to fix a rare and obscure crash bug.
742 15. Narrowed the window for a race in the daemon that could cause it to ignore
743 SIGCHLD signals. This is not a major problem, because they are used only to
744 wake it up if nothing else does.
746 16. A malformed maildirsize file could cause Exim to calculate negative values
747 for the mailbox size or file count. Odd effects could occur as a result.
748 The maildirsize information is now recalculated if the size or filecount
751 17. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
752 support for a long time. Removed HAVE_SYS_VFS_H.
754 18. Updated exipick to current release from John Jetmore.
756 19. Allow an empty sender to be matched against a lookup in an address list.
757 Previously the only cases considered were a regular expression, or an
760 20. Exim went into a mad DNS lookup loop when doing a callout where the
761 host was specified on the transport, if the DNS lookup yielded more than
764 21. The RFC2047 encoding function was originally intended for short strings
765 such as real names; it was not keeping to the 75-character limit for
766 encoded words that the RFC imposes. It now respects the limit, and
767 generates multiple encoded words if necessary. To be on the safe side, I
768 have increased the buffer size for the ${rfc2047: expansion operator from
771 22. Failure to deliver a bounce message always caused it to be frozen, even if
772 there was an errors_to setting on the router. The errors_to setting is now
775 23. If an IPv6 address is given for -bh or -bhc, it is now converted to the
776 canonical form (fully expanded) before being placed in
777 $sender_host_address.
779 24. Updated eximstats to version 1.33
781 25. Include certificate and key file names in error message when GnuTLS fails
782 to set them up, because the GnuTLS error message doesn't include the name
783 of the failing file when there is a problem reading it.
785 26. Expand error message when OpenSSL has problems setting up cert/key files.
788 27. Reset the locale to "C" after calling embedded Perl, in case it was changed
789 (this can affect the format of dates).
791 28. exim_tidydb, when checking for the continued existence of a message for
792 which it has found a message-specific retry record, was not finding
793 messages that were in split spool directories. Consequently, it was
794 deleting retry records that should have stayed in existence.
796 29. eximstats updated to version 1.35
797 1.34 - allow eximstats to parse syslog lines as well as mainlog lines
798 1.35 - bugfix such that pie charts by volume are generated correctly
800 30. The SPA authentication driver was not abandoning authentication and moving
801 on to the next authenticator when an expansion was forced to fail,
802 contradicting the general specification for all authenticators. Instead it
803 was generating a temporary error. It now behaves as specified.
805 31. The default ordering of permitted cipher suites for GnuTLS was pessimal
806 (the order specifies the preference for clients). The order is now AES256,
807 AES128, 3DES, ARCFOUR128.
809 31. Small patch to Sieve code - explicitly set From: when generating an
812 32. Exim crashed if a remote delivery caused a very long error message to be
813 recorded - for instance if somebody sent an entire SpamAssassin report back
814 as a large number of 550 error lines. This bug was coincidentally fixed by
815 increasing the size of one of Exim's internal buffers (big_buffer) that
816 happened as part of the Exiscan merge. However, to be on the safe side, I
817 have made the code more robust (and fixed the comments that describe what
820 33. Some experimental protocols are using DNS PTR records for new purposes. The
821 keys for these records are domain names, not reversed IP addresses. The
822 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
823 leaves it alone. Component reversal etc. now happens only for IP addresses.
826 34. The host_aton() function is supposed to be passed a string that is known
827 to be a valid IP address. However, in the case of IPv6 addresses, it was
828 not checking this. This is a hostage to fortune. Exim now panics and dies
829 if the condition is not met. A case was found where this could be provoked
830 from a dnsdb PTR lookup with an IPv6 address that had more than 8
831 components; fortuitously, this particular loophole had already been fixed
832 by change 4.50/55 or 4.44/33 above.
834 If there are any other similar loopholes, the new check in host_aton()
835 itself should stop them being exploited. The report I received stated that
836 data on the command line could provoke the exploit when Exim was running as
837 exim, but did not say which command line option was involved. All I could
838 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
842 35. There was a buffer overflow vulnerability in the SPA authentication code
843 (which came originally from the Samba project). I have added a test to the
844 spa_base64_to_bits() function which I hope fixes it.
847 36. The daemon start-up calls getloadavg() while still root for those OS that
848 need the first call to be done as root, but it missed one case: when
849 deliver_queue_load_max is set with deliver_drop_privilege. This is
850 necessary for the benefit of the queue runner, because there is no re-exec
851 when deliver_drop_privilege is set.
853 37. Caching of lookup data for "hosts =" ACL conditions, when a named host list
854 was in use, was not putting the data itself into the right store pool;
855 consequently, it could be overwritten for a subsequent message in the same
856 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
859 38. Sometimes the final signoff response after QUIT could fail to get
860 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
861 < 0 before doing a fflush(). This bug looks as though it goes back to the
862 introduction of TLS in release 3.20, but "sometimes" must have been rare
863 because the tests only now provoked it.
869 1. Fixed a longstanding but relatively impotent bug: a long time ago, before
870 PIPELINING, the function smtp_write_command() used to return TRUE or FALSE.
871 Now it returns an integer. A number of calls were still expecting a T/F
872 return. Fortuitously, in all cases, the tests worked in OK situations,
873 which is the norm. However, things would have gone wrong on any write
874 failures on the smtp file descriptor. This function is used when sending
875 messages over SMTP and also when doing verify callouts.
877 2. When Exim is called to do synchronous delivery of a locally submitted
878 message (the -odf or -odi options), it no longer closes stderr before doing
881 3. Implemented the mua_wrapper option.
883 4. Implemented mx_fail_domains and srv_fail_domains for the dnslookup router.
885 5. Implemented the functions header_remove(), header_testname(),
886 header_add_at_position(), and receive_remove_recipient(), and exported them
889 6. If an ACL "warn" statement specified the addition of headers, Exim already
890 inserted X-ACL-Warn: at the start if there was no header name. However, it
891 was not making this test for the second and subsequent header lines if
892 there were newlines in the string. This meant that an invalid header could
893 be inserted if Exim was badly configured.
895 7. Allow an ACL "warn" statement to add header lines at the start or after all
896 the Received: headers, as well as at the end.
898 8. Added the rcpt_4xx retry error code.
900 9. Added postmaster_mailfrom=xxx to callout verification option.
902 10. Added mailfrom=xxxx to the callout verification option, for verify=
905 11. ${substr_1_:xxxx} and ${substr__3:xxxx} are now diagnosed as syntax errors
906 (they previously behaved as ${substr_1_0:xxxx} and ${substr:_0_3:xxxx}).
908 12. Inserted some casts to stop certain compilers warning when using pointer
909 differences as field lengths or precisions in printf-type calls (mostly
910 affecting debugging statements).
912 13. Added optional readline() support for -be (dynamically loaded).
914 14. Obscure bug fix: if a message error (e.g. 4xx to MAIL) happened within the
915 same clock tick as a message's arrival, so that its received time was the
916 same as the "first fail" time on the retry record, and that message
917 remained on the queue past the ultimate address timeout, every queue runner
918 would try a delivery (because it was past the ultimate address timeout) but
919 after another failure, the ultimate address timeout, which should have then
920 bounced the address, did not kick in. This was a "< instead of <=" error;
921 in most cases the first failure would have been in the next clock tick
922 after the received time, and all would be well.
924 15. The special items beginning with @ in domain lists (e.g. @mx_any) were not
925 being recognized when the domain list was tested by the match_domain
926 condition in an expansion string.
928 16. Added the ${str2b64: operator.
930 17. Exim was always calling setrlimit() to set a large limit for the number of
931 processes, without checking whether the existing limit was already
932 adequate. (It did check for the limit on file descriptors.) Furthermore,
933 errors from getrlimit() and setrlimit() were being ignored. Now they are
934 logged to the main and panic logs, but Exim does carry on, to try to do its
935 job under whatever limits there are.
937 18. Imported PCRE 5.0.
939 19. Trivial typo in log message " temporarily refused connection" (the leading
942 20. If the log selector return_path_on_delivery was set and an address was
943 redirected to /dev/null, the delivery process crashed because it assumed
944 that a return path would always be set for a "successful" delivery. In this
945 case, the whole delivery is bypassed as an optimization, and therefore no
948 21. Internal re-arrangement: the function for sending a challenge and reading
949 a response while authentication was assuming a zero-terminated challenge
950 string. It's now changed to take a pointer and a length, to allow for
951 binary data in such strings.
953 22. Added the cyrus_sasl authenticator (code supplied by MBM).
955 23. Exim was not respecting finduser_retries when seeking the login of the
956 uid under which it was called; it was always trying 10 times. (The default
957 setting of finduser_retries is zero.) Also, it was sleeping after the final
958 failure, which is pointless.
960 24. Implemented tls_on_connect_ports.
962 25. Implemented acl_smtp_predata.
964 26. If the domain in control=submission is set empty, Exim assumes that the
965 authenticated id is a complete email address when it generates From: or
966 Sender: header lines.
968 27. Added "#define SOCKLEN_T int" to OS/os.h-SCO and OS/os.h-SCO_SV. Also added
969 definitions to OS/Makefile-SCO and OS/Makefile-SCO_SV that put basename,
970 chown and chgrp in /bin and hostname in /usr/bin.
972 28. Exim was keeping the "process log" file open after each use, just as it
973 does for the main log. This opens the possibility of it remaining open for
974 long periods when the USR1 signal hits a daemon. Occasional processlog
975 errors were reported, that could have been caused by this. Anyway, it seems
976 much more sensible not to leave this file open at all, so that is what now
979 29. The long-running daemon process does not normally write to the log once it
980 has entered its main loop, and it closes the log before doing so. This is
981 so that log files can straightforwardly be renamed and moved. However,
982 there are a couple of unusual error situations where the daemon does write
983 log entries, and I had neglected to close the log afterwards.
985 30. The text of an SMTP error response that was received during a remote
986 delivery was being truncated at 512 bytes. This is too short for some of
987 the long messages that one sometimes sees. I've increased the limit to
990 31. It is now possible to make retry rules that apply only when a message has a
991 specific sender, in particular, an empty sender.
993 32. Added "control = enforce_sync" and "control = no_enforce_sync". This makes
994 it possible to be selective about when SMTP synchronization is enforced.
996 33. Added "control = caseful_local_part" and "control = "caselower_local_part".
998 32. Implemented hosts_connection_nolog.
1000 33. Added an ACL for QUIT.
1002 34. Setting "delay_warning=" to disable warnings was not working; it gave a
1005 35. Added mailbox_size and mailbox_filecount to appendfile.
1007 36. Added control = no_multiline_responses to ACLs.
1009 37. There was a bug in the logic of the code that waits for the clock to tick
1010 in the case where the clock went backwards by a substantial amount such
1011 that the microsecond fraction of "now" was more than the microsecond
1012 fraction of "then" (but the whole seconds number was less).
1014 38. Added support for the libradius Radius client library this is found on
1015 FreeBSD (previously only the radiusclient library was supported).
1021 1. When certain lookups returned multiple values in the form name=value, the
1022 quoting of the values was not always being done properly. Specifically:
1023 (a) If the value started with a double quote, but contained no whitespace,
1025 (b) If the value contained whitespace other than a space character (i.e.
1026 tabs or newlines or carriage returns) it was not quoted.
1027 This fix has been applied to the mysql and pgsql lookups by writing a
1028 separate quoting function and calling it from the lookup code. The fix
1029 should probably also be applied to nisplus, ibase and oracle lookups, but
1030 since I cannot test any of those, I have not disturbed their existing code.
1032 2. A hit in the callout cache for a specific address caused a log line with no
1033 reason for rejecting RCPT. Now it says "Previous (cached) callout
1034 verification failure".
1036 3. There was an off-by-one bug in the queryprogram router. An over-long
1037 return line was truncated at 256 instead of 255 characters, thereby
1038 overflowing its buffer with the terminating zero. As well as fixing this, I
1039 have increased the buffer size to 1024 (and made a note to document this).
1041 4. If an interrupt, such as the USR1 signal that is send by exiwhat, arrives
1042 when Exim is waiting for an SMTP response from a remote server, Exim
1043 restarts its select() call on the socket, thereby resetting its timeout.
1044 This is not a problem when such interrupts are rare. Somebody set up a cron
1045 job to run exiwhat every 2 minutes, which is less than the normal select()
1046 timeout (5 or 10 minutes). This meant that the select() timeout never
1047 kicked in because it was always reset. I have fixed this by comparing the
1048 time when an interrupt arrives with the time at the start of the first call
1049 to select(). If more time than the timeout has elapsed, the interrupt is
1050 treated as a timeout.
1052 5. Some internal re-factoring in preparation for the addition of Sieve
1053 extensions (by MH). In particular, the "personal" test is moved to a
1054 separate function, and given an option for scanning Cc: and Bcc: (which is
1055 not set for Exim filters).
1057 6. When Exim created an email address using the login of the caller as the
1058 local part (e.g. when creating a From: or Sender: header line), it was not
1059 quoting the local part when it contained special characters such as @.
1061 7. Installed new OpenBSD configuration files.
1063 8. Reworded some messages for syntax errors in "and" and "or" conditions to
1064 try to make them clearer.
1066 9. Callout options, other than the timeout value, were being ignored when
1067 verifying sender addresses in header lines. For example, when using
1069 verify = header_sender/callout=no_cache
1071 the cache was (incorrectly) being used.
1073 10. Added a missing instance of ${EXE} to the exim_install script; this affects
1074 only the Cygwin environment.
1076 11. When return_path_on_delivery was set as a log selector, if different remote
1077 addresses in the same message used different return paths and parallel
1078 remote delivery occurred, the wrong values would sometimes be logged.
1079 (Whenever a remote delivery process finished, the return path value from
1080 the most recently started remote delivery process was logged.)
1082 12. RFC 3848 specifies standard names for the "with" phrase in Received: header
1083 lines when AUTH and/or TLS are in use. This is the "received protocol"
1084 field. Exim used to use "asmtp" for authenticated SMTP, without any
1085 indication (in the protocol name) for TLS use. Now it follows the RFC and
1086 uses "esmtpa" if the connection is authenticated, "esmtps" if it is
1087 encrypted, and "esmtpsa" if it is both encrypted and authenticated. These
1088 names appear in log lines as well as in Received: header lines.
1090 13. Installed MH's patches for Sieve to add the "copy" and "vacation"
1091 extensions, and comparison tests, and to fix some bugs.
1093 14. Changes to the "personal" filter test:
1095 (1) The test was buggy in that it was just doing the equivalent of
1096 "contains" tests on header lines. For example, if a user's address was
1097 anne@some.where, the "personal" test would incorrectly be true for
1099 To: susanne@some.where
1101 This test is now done by extracting each address from the header in turn,
1102 and checking the entire address. Other tests that are part of "personal"
1103 are now done using regular expressions (for example, to check local parts
1104 of addresses in From: header lines).
1106 (2) The list of non-personal local parts in From: addresses has been
1107 extended to include "listserv", "majordomo", "*-request", and "owner-*",
1108 taken from the Sieve specification recommendations.
1110 (3) If the message contains any header line starting with "List-" it is
1111 treated as non-personal.
1113 (4) The test for "circular" in the Subject: header line has been removed
1114 because it now seems ill-conceived.
1116 15. Minor typos in src/EDITME comments corrected.
1118 16. Installed latest exipick from John Jetmore.
1120 17. If headers_add on a router specified a text string that was too long for
1121 string_sprintf() - that is, longer than 8192 bytes - Exim panicked. The use
1122 of string_sprintf() is now avoided.
1124 18. $message_body_size was not set (it was always zero) when running the DATA
1125 ACL and the local_scan() function.
1127 19. For the "mail" command in an Exim filter, no default was being set for
1128 the once_repeat time, causing a random time value to be used if "once" was
1129 specified. (If the value happened to be <= 0, no repeat happened.) The
1130 default is now 0s, meaning "never repeat". The "vacation" command was OK
1131 (its default is 7d). It's somewhat surprising nobody ever noticed this bug
1132 (I found it when inspecting the code).
1134 20. There is now an overall timeout for performing a callout verification. It
1135 defaults to 4 times the callout timeout, which applies to individual SMTP
1136 commands during the callout. The overall timeout applies when there is more
1137 than one host that can be tried. The timeout is checked before trying the
1138 next host. This prevents very long delays if there are a large number of
1139 hosts and all are timing out (e.g. when the network connections are timing
1140 out). The value of the overall timeout can be changed by specifying an
1141 additional sub-option for "callout", called "maxwait". For example:
1143 verify = sender/callout=5s,maxwait=20s
1145 21. Add O_APPEND to the open() call for maildirsize files (Exim already seeks
1146 to the end before writing, but this should make it even safer).
1148 22. Exim was forgetting that it had advertised PIPELINING for the second and
1149 subsequent messages on an SMTP connection. It was also not resetting its
1150 memory on STARTTLS and an internal HELO.
1152 23. When Exim logs an SMTP synchronization error within a session, it now
1153 records whether PIPELINING has been advertised or not.
1155 24. Added 3 instances of "(long int)" casts to time_t variables that were being
1156 formatted using %ld, because on OpenBSD (and perhaps others), time_t is int
1157 rather than long int.
1159 25. Installed the latest Cygwin configuration files from the Cygwin maintainer.
1161 26. Added the never_mail option to autoreply.
1167 1. A reorganization of the code in order to implement 4.40/8 caused a daemon
1168 crash if the getsockname() call failed; this can happen if a connection is
1169 closed very soon after it is established. The problem was simply in the
1170 order in which certain operations were done, causing Exim to try to write
1171 to the SMTP stream before it had set up the file descriptor. The bug has
1172 been fixed by making things happen in the correct order.
1178 1. If "drop" was used in a DATA ACL, the SMTP output buffer was not flushed
1179 before the connection was closed, thus losing the rejection response.
1181 2. Commented out the definition of SOCKLEN_T in os.h-SunOS5. It is needed for
1182 some early Solaris releases, but causes trouble in current releases where
1183 socklen_t is defined.
1185 3. When std{in,out,err} are closed, re-open them to /dev/null so that they
1188 4. Minor refactoring of os.c-Linux to avoid compiler warning when IPv6 is not
1191 5. Refactoring in expand.c to improve memory usage. Pre-allocate a block so
1192 that releasing the top of it at the end releases what was used for sub-
1193 expansions (unless the block got too big). However, discard this block if
1194 the first thing is a variable or header, so that we can use its block when
1195 it is dynamic (useful for very large $message_headers, for example).
1197 6. Lookups now cache *every* query, not just the most recent. A new, separate
1198 store pool is used for this. It can be recovered when all lookup caches are
1199 flushed. Lookups now release memory at the end of their result strings.
1200 This has involved some general refactoring of the lookup sources.
1202 7. Some code has been added to the store_xxx() functions to reduce the amount
1203 of flapping under certain conditions.
1205 8. log_incoming_interface used to affect only the <= reception log lines. Now
1206 it causes the local interface and port to be added to several more SMTP log
1207 lines, for example "SMTP connection from", and rejection lines.
1209 9. The Sieve author supplied some patches for the doc/README.SIEVE file.
1211 10. Added a conditional definition of _BSD_SOCKLEN_T to os.h-Darwin.
1213 11. If $host_data was set by virtue of a hosts lookup in an ACL, its value
1214 could be overwritten at the end of the current message (or the start of a
1215 new message if it was set in a HELO ACL). The value is now preserved for
1216 the duration of the SMTP connection.
1218 12. If a transport had a headers_rewrite setting, and a matching header line
1219 contained an unqualified address, that address was qualified, even if it
1220 did not match any rewriting rules. The underlying bug was that the values
1221 of the flags that permit the existence of unqualified sender and recipient
1222 addresses in header lines (set by {sender,recipient}_unqualified_hosts for
1223 non-local messages, and by -bnq for local messages) were not being
1224 preserved with the message after it was received.
1226 13. When Exim was logging an SMTP synchronization error, it could sometimes log
1227 "next input=" as part of the text comprising the host identity instead of
1228 the correct text. The code was using the same buffer for two different
1229 strings. However, depending on which order the printing function evaluated
1230 its arguments, the bug did not always show up. Under Linux, for example, my
1231 test suite worked just fine.
1233 14. Exigrep contained a use of Perl's "our" scoping after change 4.31/70. This
1234 doesn't work with some older versions of Perl. It has been changed to "my",
1235 which in any case is probably the better facility to use.
1237 15. A really picky compiler found some instances of statements for creating
1238 error messages that either had too many or two few arguments for the format
1241 16. The size of the buffer for calls to the DNS resolver has been increased
1242 from 1024 to 2048. A larger buffer is needed when performing PTR lookups
1243 for addresses that have a lot of PTR records. This alleviates a problem; it
1244 does not fully solve it.
1246 17. A dnsdb lookup for PTR records that receives more data than will fit in the
1247 buffer now truncates the list and logs the incident, which is the same
1248 action as happens when Exim is looking up a host name and its aliases.
1249 Previously in this situation something unpredictable would happen;
1250 sometimes it was "internal error: store_reset failed".
1252 18. If a server dropped the connection unexpectedly when an Exim client was
1253 using GnuTLS and trying to read a response, the client delivery process
1254 crashed while trying to generate an error log message.
1256 19. If a "warn" verb in an ACL added multiple headers to a message in a single
1257 string, for example:
1259 warn message = H1: something\nH2: something
1261 the text was added as a single header line from Exim's point of view
1262 though it ended up OK in the delivered message. However, searching for the
1263 second and subsequent header lines using $h_h2: did not work. This has been
1264 fixed. Similarly, if a system filter added multiple headers in this way,
1265 the routers could not see them.
1267 20. Expanded the error message when iplsearch is called with an invalid key to
1268 suggest using net-iplsearch in a host list.
1270 21. When running tests using -bh, any delays imposed by "delay" modifiers in
1271 ACLs are no longer actually imposed (and a message to that effect is
1274 22. If a "gecos" field in a passwd entry contained escaped characters, in
1275 particular, if it contained a \" sequence, Exim got it wrong when building
1276 a From: or a Sender: header from that name. A second bug also caused
1277 incorrect handling when an unquoted " was present following a character
1278 that needed quoting.
1280 23. "{crypt}" as a password encryption mechanism for a "crypteq" expansion item
1281 was not being matched caselessly.
1283 24. Arranged for all hyphens in the exim.8 source to be escaped with
1286 25. Change 16 of 4.32, which reversed 71 or 4.31 didn't quite do the job
1287 properly. Recipient callout cache records were still being keyed to include
1288 the sender, even when use_sender was set false. This led to far more
1289 callouts that were necessary. The sender is no longer included in the key
1290 when use_sender is false.
1292 26. Added "control = submission" modifier to ACLs.
1294 27. Added the ${base62d: operator to decode base 62 numbers.
1296 28. dnsdb lookups can now access SRV records.
1298 29. CONFIGURE_OWNER can be set at build time to define an alternative owner for
1299 the configuration file.
1301 30. The debug message "delivering xxxxxx-xxxxxx-xx" is now output in verbose
1302 (-v) mode. This makes the output for a verbose queue run more intelligible.
1304 31. Added a use_postmaster feature to recipient callouts.
1306 32. Added the $body_zerocount variable, containing the number of binary zero
1307 bytes in the message body.
1309 33. The time of last modification of the "new" subdirectory is now used as the
1310 "mailbox time last read" when there is a quota error for a maildir
1313 34. Added string comparison operators lt, lti, le, lei, gt, gti, ge, gei.
1315 35. Added +ignore_unknown as a special item in host lists.
1317 36. Code for decoding IPv6 addresses in host lists is now included, even if
1318 IPv6 support is not being compiled. This fixes a bug in which an IPv6
1319 address was recognized as an IP address, but was then not correctly decoded
1320 into binary, causing unexpected and incorrect effects when compared with
1327 1. Very minor rewording of debugging text in manualroute to say "list of
1328 hosts" instead of "hostlist".
1330 2. If verify=header_syntax was set, and a header line with an unqualified
1331 address (no domain) and a large number of spaces between the end of the
1332 name and the colon was received, the reception process suffered a buffer
1333 overflow, and (when I tested it) crashed. This was caused by some obsolete
1334 code that should have been removed. The fix is to remove it!
1336 3. When running in the test harness, delay a bit after writing a bounce
1337 message to get a bit more predictability in the log output.
1339 4. Added a call to search_tidyup() just before forking a reception process. In
1340 theory, someone could use a lookup in the expansion of smtp_accept_max_
1341 per_host which, without the tidyup, could leave open a database connection.
1343 5. Added the variables $recipient_data and $sender_data which get set from a
1344 lookup success in an ACL "recipients" or "senders" condition, or a router
1345 "senders" option, similar to $domain_data and $local_part_data.
1347 6. Moved the writing of debug_print from before to after the "senders" test
1350 7. Change 4.31/66 (moving the time when the Received: is generated) caused
1351 problems for message scanning, either using a data ACL, or using
1352 local_scan() because the Received: header was not generated till after they
1353 were called (in order to set the time as the time of reception completion).
1354 I have revised the way this works. The header is now generated after the
1355 body is received, but before the ACL or local_scan() are called. After they
1356 are run, the timestamp in the header is updated.
1362 1. Change 4.24/6 introduced a bug because the SIGALRM handler was disabled
1363 before starting a queue runner without re-exec. This happened only when
1364 deliver_drop_privilege was set or when the Exim user was set to root. The
1365 effect of the bug was that timeouts during subsequent deliveries caused
1366 crashes instead of being properly handled. The handler is now left at its
1367 default (and expected) setting.
1369 2. The other case in which a daemon avoids a re-exec is to deliver an incoming
1370 message, again when deliver_drop_privilege is set or Exim is run as root.
1371 The bug described in (1) was not present in this case, but the tidying up
1372 of the other signals was missing. I have made the two cases consistent.
1374 3. The ignore_target_hosts setting on a manualroute router was being ignored
1375 for hosts that were looked up using the /MX notation.
1377 4. Added /ignore=<ip list> feature to @mx_any, @mx_primary, and @mx_secondary
1380 5. Change 4.31/55 was buggy, and broke when there was a rewriting rule that
1381 operated on the sender address. After changing the $sender_address to <>
1382 for the sender address verify, Exim was re-instated it as the original
1383 (before rewriting) address, but remembering that it had rewritten it, so it
1384 wasn't rewriting it again. This bug also had the effect of breaking the
1385 sender address verification caching when the sender address was rewritten.
1387 6. The ignore_target_hosts option was being ignored by the ipliteral router.
1388 This has been changed so that if the ip literal address matches
1389 ignore_target_hosts, the router declines.
1391 7. Added expansion conditions match_domain, match_address, and match_local_
1392 part (NOT match_host).
1394 8. The placeholder for the Received: header didn't have a length field set.
1396 9. Added code to Exim itself and to exim_lock to test for a specific race
1397 condition that could lead to file corruption when using MBX delivery. The
1398 issue is with the lockfile that is created in /tmp. If this file is removed
1399 after a process has opened it but before that process has acquired a lock,
1400 there is the potential for a second process to recreate the file and also
1401 acquire a lock. This could lead to two Exim processes writing to the file
1402 at the same time. The added code performs the same test as UW imapd; it
1403 checks after acquiring the lock that its file descriptor still refers to
1404 the same named file.
1406 10. The buffer for building added header lines was of fixed size, 8192 bytes.
1407 It is now parameterized by HEADER_ADD_BUFFER_SIZE and this can be adjusted
1410 11. Added the smtp_active_hostname option. If used, this will typically be made
1411 to depend on the incoming interface address. Because $interface_address is
1412 not set up until the daemon has forked a reception process, error responses
1413 that can happen earlier (such as "too many connections") no longer contain
1416 12. If an expansion in a condition on a "warn" statement fails because a lookup
1417 defers, the "warn" statement is abandoned, and the next ACL statement is
1418 processed. Previously this caused the whole ACL to be aborted.
1420 13. Added the iplsearch lookup type.
1422 14. Added ident_timeout as a log selector.
1424 15. Added tls_certificate_verified as a log selector.
1426 16. Added a global option tls_require_ciphers (compare the smtp transport
1427 option of the same name). This controls incoming TLS connections.
1429 17. I finally figured out how to make tls_require_ciphers do a similar thing
1430 in GNUtls to what it does in OpenSSL, that is, set up an appropriate list
1431 before starting the TLS session.
1433 18. Tabs are now shown as \t in -bP output.
1435 19. If the log selector return_path_on_delivery was set, Exim crashed when
1436 bouncing a message because it had too many Received: header lines.
1438 20. If two routers both had headers_remove settings, and the first one included
1439 a superfluous trailing colon, the final name in the first list and the
1440 first name in the second list were incorrectly joined into one item (with a
1441 colon in the middle).
1447 1. Added -C and -D options to the exinext utility, mainly to make it easier
1448 to include in the automated testing, but these could be helpful when
1449 multiple configurations are in use.
1451 2. The exinext utility was not formatting the output nicely when there was
1452 an alternate port involved in the retry record key, nor when there was a
1453 message id as well (for retries that were specific to a specific message
1454 and a specific host). It was also confused by IPv6 addresses, because of
1455 the additional colons they contain. I have fixed the IPv4 problem, and
1456 patched it up to do a reasonable job for IPv6.
1458 3. When there is an error after a MAIL, RCPT, or DATA SMTP command during
1459 delivery, the log line now contains "pipelined" if PIPELINING was used.
1461 4. An SMTP transport process used to panic and die if the bind() call to set
1462 an explicit outgoing interface failed. This has been changed; it is now
1463 treated in the same way as a connect() failure.
1465 5. A reference to $sender_host_name in the part of a conditional expansion
1466 that was being skipped was still causing a DNS lookup. This no longer
1469 6. The def: expansion condition was not recognizing references to header lines
1470 that used bh_ and bheader_.
1472 7. Added the _cache feature to named lists.
1474 8. The code for checking quota_filecount in the appendfile transport was
1475 allowing one more file than it should have been.
1477 9. For compatibility with Sendmail, the command line option
1485 and sets the incoming protocol and host name (for trusted callers). The
1486 host name and its colon can be omitted when only the protocol is to be set.
1487 Note the Exim already has two private options, -pd and -ps, that refer to
1488 embedded Perl. It is therefore impossible to set a protocol value of "d" or
1489 "s", but I don't think that's a major issue.
1491 10. A number of refactoring changes to the code, none of which should affect
1494 (a) The number of logging options was getting close to filling up the
1495 32-bit word that was used as a bit map. I have split them into two classes:
1496 those that are passed in the argument to log_write(), and those that are
1497 only ever tested independently outside of that function. These are now in
1498 separate 32-bit words, so there is plenty of room for expansion again.
1499 There is no change in the user interface or the logging behaviour.
1501 (b) When building, for example, log lines, the code previously used a
1502 macro that called string_cat() twice, in order to add two strings. This is
1503 not really sufficiently general. Furthermore, there was one instance where
1504 it was actually wrong because one of the argument was used twice, and in
1505 one call a function was used. (As it happened, calling the function twice
1506 did not affect the overall behaviour.) The macro has been replaced by a
1507 function that can join an arbitrary number of extra strings onto a growing
1510 (c) The code for expansion conditions now uses a table and a binary chop
1511 instead of a serial search (which was left over from when there were very
1512 few conditions). Also, it now recognizes conditions like "pam" even when
1513 the relevant support is not compiled in: a suitably worded error message is
1514 given if an attempt is made to use such a condition.
1516 11. Added ${time_interval:xxxxx}.
1518 12. A bug was causing one of the ddress fields not to be passed back correctly
1519 from remote delivery subprocesses. The field in question was not being
1520 subsequently used, so this caused to problems in practice.
1522 13. Added new log selectors queue_time and deliver_time.
1524 14. Might have fixed a bug in maildirsizefile handling that threw up
1525 "unexpected character" debug warnings, and recalculated the data
1526 unnecessarily. In any case, I expanded the warning message to give more
1529 15. Added the message "Restricted characters in address" to the statements in
1530 the default ACL that block characters like @ and % in local parts.
1532 16. Change 71 for release 4.31 proved to be much less benign that I imagined.
1533 Three changes have been made:
1535 (a) There was a serious bug; a negative response to MAIL caused the whole
1536 recipient domain to be cached as invalid, thereby blocking all messages
1537 to all local parts at the same domain, from all senders. This bug has
1538 been fixed. The domain is no longer cached after a negative response to
1539 MAIL if the sender used is not empty.
1541 (b) The default behaviour of using MAIL FROM:<> for recipient callouts has
1544 (c) A new callout option, "use_sender" has been added for people who want
1545 the modified behaviour.
1551 1. Removed "EXTRALIBS=-lwrap" from OS/Makefile-Unixware7 on the advice of
1554 2. Removed "LIBS = -lresolv" from OS/Makefile-Darwin as it is not needed, and
1555 indeed breaks things for older releases.
1557 3. Added additional logging to the case where there is a problem reading data
1558 from a filter that is running in a subprocess using a pipe, in order to
1559 try to track down a specific problem.
1561 4. Testing facility fudge: when running in the test harness and attempting
1562 to connect to 10.x.x.x (expecting a connection timeout) I'm now sometimes
1563 getting "No route to host". Convert this to a timeout.
1565 5. Define ICONV_ARG2_TYPE as "char **" for Unixware7 to avoid compiler
1568 6. Some OS don't have socklen_t but use size_t instead. This affects the
1569 fifth argument of getsockopt() amongst other things. This is now
1570 configurable by a macro called SOCKLEN_T which defaults to socklen_t, but
1571 can be set for individual OS. I have set it for SunOS5, OSF1, and
1572 Unixware7. Current versions of SunOS5 (aka Solaris) do have socklen_t, but
1573 some earlier ones do not.
1575 7. Change 4.30/15 was not doing the test caselessly.
1577 8. The standard form for an IPv6 address literal was being rejected by address
1578 parsing in, for example, MAIL and RCPT commands. An example of this kind of
1579 address is [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
1580 this, as well as the form without the "IPv6" on the front (but only when
1581 address literals are enabled, of course).
1583 9. Added some casts to avoid compiler warnings in OS/os.c-Linux.
1585 10. Exim crashed if a message with an empty sender address specified by -f
1586 encountered a router with an errors_to setting. This could be provoked only
1587 by a command such as
1591 where an empty string was supplied; "<>" did not hit this bug.
1593 11. Installed PCRE release 4.5.
1595 12. If EHLO/HELO was rejected by an ACL, the value of $sender_helo_name
1596 remained set. It is now erased.
1598 13. exiqgrep wasn't working on MacOS X because it didn't correctly compute
1599 times from message ids (which are base 36 rather than the normal 62).
1601 14. "Expected" SMTP protocol errors that can arise when PIPELINING is in use
1602 were being counted as actual protocol errors, and logged if the log
1603 selector +smtp_protocol_error was set. One cannot be perfect in this test,
1604 but now, if PIPELINING has been advertised, RCPT following a rejected MAIL,
1605 and DATA following a set of rejected RCPTs do not count as protocol errors.
1606 In other words, Exim assumes they were pipelined, though this may not
1607 actually be the case. Of course, in all cases the client gets an
1608 appropriate error code.
1610 15. If a lookup fails in an ACL condition, a message about the failure may
1611 be available; it is used if testing the ACL cannot continue, because most
1612 such messages specify what the cause of the deferral is. However, some
1613 messages (e.g. "MYSQL: no data found") do not cause a defer. There was bug
1614 that caused an old message to be retained and used if a later statement
1615 caused a defer, replacing the real cause of the deferral.
1617 16. If an IP address had so many PTR records that the DNS lookup buffer
1618 was not large enough to hold them, Exim could crash while trying to process
1619 the truncated data. It now detects and logs this case.
1621 17. Further to 4.21/58, another change has been made: if (and only if) the
1622 first line of a message (the first header line) ends with CRLF, a bare LF
1623 in a subsequent header line has a space inserted after it, so as not to
1624 terminate the header.
1626 18. Refactoring: tidied an ugly bit of code in appendfile that copied data
1627 unnecessarily, used atoi() instead of strtol(), and didn't check the
1628 termination when getting file sizes from file names by regex.
1630 19. Completely re-implemented the support for maildirsize files, in the light
1631 of a number of problems with the previous contributed implementation
1632 (4.30/29). In particular:
1634 . If the quota is zero, the maildirsize file is maintained, but no quota is
1637 . If the maildir directory does not exist, it is created before any attempt
1638 to write a maildirsize file.
1640 . The quota value in the file is just a cache; if the quota is changed in
1641 the transport, the new value overrides.
1643 . A regular expression is available for excluding directories from the
1646 20. The autoreply transport checks the characters in options that define the
1647 message's headers; it allows continued headers, but it was checking with
1648 isspace() after an embedded newline instead of explicitly looking for a
1651 21. If all the "regular" hosts to which an address was routed had passed their
1652 expiry times, and had not reached their retry times, the address was
1653 bounced, even if fallback hosts were defined. Now Exim should go on to try
1656 22. Increased buffer sizes in the callout code from 1024 to 4096 to match the
1657 equivalent code in the SMTP transport. Some hosts send humungous responses
1658 to HELO/EHLO, more than 1024 it seems.
1660 23. Refactoring: code in filter.c used (void *) for "any old type" but this
1661 gives compiler warnings in some environments. I've now done it "properly",
1664 24. The replacement for inet_ntoa() that is used with gcc on IRIX systems
1665 (because of problems with the built-in one) was declared to return uschar *
1666 instead of char *, causing compiler failure.
1668 25. Fixed a file descriptor leak when processing alias/forward files.
1670 26. Fixed a minor format string issue in dbfn.c.
1672 27. Typo in exim.c: ("dmbnz" for "dbmnz").
1674 28. If a filter file refered to $h_xxx or $message_headers, and the headers
1675 contained RFC 2047 "words", Exim's memory could, under certain conditions,
1678 29. When a sender address is verified, it is cached, to save repeating the test
1679 when there is more than one recipient in a message. However, when the
1680 verification involves a callout, it is possible for different callout
1681 options to be set for different recipients. It is too complicated to keep
1682 track of this in the cache, so now Exim always runs a verification when a
1683 callout is required, relying on the callout cache for the optimization.
1684 The overhead is duplication of the address routing, but this should not be
1687 30. Fixed a bug in callout caching. If a RCPT command caused the sender address
1688 to be verified with callout=postmaster, and the main callout worked but the
1689 postmaster check failed, the verification correctly failed. However, if a
1690 subsequent RCPT command asked for sender verification *without* the
1691 postmaster check, incorrect caching caused this verification also to fail,
1694 31. Exim caches DNS lookup failures so as to avoid multiple timeouts; however,
1695 it was not caching the DNS options (qualify_single, search_parents) that
1696 were used when the lookup failed. A subsequent lookup with different
1697 options therefore always gave the same answer, though there were cases
1698 where it should not have. (Example: a "domains = !$mx_any" option on a
1699 dnslookup router: the "domains" option is always processed without any
1700 widening, but the router might have qualify_single set.) Now Exim uses the
1701 cached value only when the same options are set.
1703 32. Added John Jetmore's "exipick" utility to the distribution.
1705 33. GnuTLS: When an attempt to start a TLS session fails for any reason other
1706 than a timeout (e.g. a certificate is required, and is not provided), an
1707 Exim server now closes the connection immediately. Previously it waited for
1708 the client to close - but if the client is SSL, it seems that they each
1709 wait for each other, leading to a delay before one of them times out.
1711 34: GnuTLS: Updated the code to use the new GnuTLS 1.0.0 API. I have not
1712 maintained 0.8.x compatibility because I don't think many are using it, and
1713 it is clearly obsolete.
1715 35. Added TLS support for CRLs: a tls_crl global option and one for the smtp
1718 36. OpenSSL: $tls_certificate_verified was being set to 1 even if the
1719 client certificate was expired. A simple patch fixes this, though I don't
1720 understand the full logic of why the verify callback is called multiple
1723 37. OpenSSL: a patch from Robert Roselius: "Enable client-bug workaround.
1724 Versions of OpenSSL as of 0.9.6d include a 'CBC countermeasure' feature,
1725 which causes problems with some clients (such as the Certicom SSL Plus
1726 library used by Eudora). This option, SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS,
1727 disables the coutermeasure allowing Eudora to connect."
1729 38. Exim was not checking that a write() to a log file succeeded. This could
1730 lead to Bad Things if a log got too big, in particular if it hit a file
1731 size limit. Exim now panics and dies if it cannot write to a log file, just
1732 as it does if it cannot open a log file.
1734 39. Modified OS/Makefile-Linux so that it now contains
1736 CFLAGS=-O -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
1738 The two -D definitions ensure that Exim is compiled with large file
1739 support, which makes it possible to handle log files that are bigger than
1742 40. Fixed a subtle caching bug: if (in an ACL or a set of routers, for
1743 instance) a domain was checked against a named list that involved a lookup,
1744 causing $domain_data to be set, then another domain was checked against the
1745 same list, then the first domain was re-checked, the value of $domain_data
1746 after the final check could be wrong. In particular, if the second check
1747 failed, it could be set empty. This bug probably also applied to
1750 41. The strip_trailing_dot option was not being applied to the address given
1751 with the -f command-line option.
1753 42. The code for reading a message's header from the spool was incrementing
1754 $received_count, but never initializing it. This meant that the value was
1755 incorrect (doubled) while delivering a message in the same process in which
1756 it was received. In the most common configuration of Exim, this never
1757 happens - a fresh exec is done - but it can happen when
1758 deliver_drop_privilege is set.
1760 43. When Exim logs an SMTP synchronization error - client data sent too soon -
1761 it now includes up to 150 characters of the unexpected data in the log
1764 44. The exim_dbmbuild utility uses fixed size buffers for reading input lines
1765 and building data strings. The size of both of these buffers was 10 000
1766 bytes - far larger than anybody would *ever* want, thought I. Needless to
1767 say, somebody hit the limit. I have increased the maximum line length to
1768 20 000 and the maximum data length of concatenated lines to 100 000. I have
1769 also fixed two bugs, because there was no checking on these buffers. Tsk,
1770 tsk. Now exim_dbmbuild gives a message and exits with an error code if a
1771 buffer is too small.
1773 45. The exim_dbmbuild utility did not support quoted keys, as Exim does in
1774 lsearch lookups. Now it does.
1776 46. When parsing a route_list item in a manualroute router, a fixed-length
1777 buffer was used for the list of hosts. I made this 1024 bytes long,
1778 thinking that nobody would ever have a list of hosts that long. Wrong.
1779 Somebody had a whole pile of complicated expansion conditions, and the
1780 string was silently truncated, leading to an expansion error. It turns out
1781 that it is easier to change to an unlimited length (owing to other changes
1782 that have happened since this code was originally written) than to build
1783 structure for giving a limitation error. The length of the item that
1784 expands into the list of hosts is now unlimited.
1786 47. The lsearch lookup could not handle data where the length of text line was
1787 more than 4095 characters. Such lines were truncated, leading to shortened
1788 data being returned. It should now handle lines of any length.
1790 48. Minor wording revision: "cannot test xxx in yyy ACL" becomes "cannot test
1791 xxx condition in yyy ACL" (e.g. "cannot test domains condition in DATA
1794 49. Cosmetic tidy to scripts like exicyclog that are generated by globally
1795 replacing strings such as BIN_DIRECTORY in a source file: the replacement
1796 no longer happens in comment lines. A list of replacements is now placed
1797 at the head of all of the source files, except those whose only change is
1798 to replace PERL_COMMAND in the very first #! line.
1800 50. Replaced the slow insertion sort in queue.c, for sorting the list of
1801 messages on the queue, with a bottom-up merge sort, using code contributed
1802 by Michael Haardt. This should make operations like -bp somewhat faster on
1803 large queues. It won't affect queue runners, except when queue_run_in_order
1806 51. Installed eximstats 1.31 in the distribution.
1808 52. Added support for SRV lookups to the dnslookup router.
1810 53. If an ACL referred to $message_body or $message_body_end, the value was not
1811 reset for any messages that followed in the same SMTP session.
1813 54. The store-handling optimization for building very long strings was not
1814 differentiating between the different store pools. I don't think this
1815 actually made any difference in practice, but I've tidied it.
1817 55. While running the routers to verify a sender address, $sender_address
1818 was still set to the sender address. This is wrong, because when routing to
1819 send a bounce to the sender, it would be empty. Therefore, I have changed
1820 it so that, while verifying a sender address, $sender_address is set to <>.
1821 (There is no change to what happens when verifying a recipient address.)
1823 56. After finding MX (or SRV) records, Exim was doing a DNS lookup for the
1824 target A or AAAA records (if not already returned) without resetting the
1825 qualify_single or search_parents options of the DNS resolver. These are
1826 inappropriate in this case because the targets of MX and SRV records must
1827 be FQDNs. A broken DNS record could cause trouble if it happened to have a
1828 target that, when qualified, matched something in the local domain. These
1829 two options are now turned off when doing these lookups.
1831 57. It seems that at least some releases of Reiserfs (which does not have the
1832 concept of a fixed number of inodes) returns zero and not -1 for the
1833 number of available inodes. This interacted badly with check_spool_inodes,
1834 which assumed that -1 was the "no such thing" setting. What I have done is
1835 to check that the total number of inodes is greater than zero before doing
1836 the test of how many are available.
1838 58. When a "warn" ACL statement has a log_message modifier, the message is
1839 remembered, and not repeated. This is to avoid a lot of repetition when a
1840 message has many recipients that cause the same warning to be written.
1841 Howewer, Exim was preserving the list of already written lines for an
1842 entire SMTP session, which doesn't seem right. The memory is now reset if a
1843 new message is started.
1845 59. The "rewrite" debugging flag was not showing the result of rewriting in the
1846 debugging output unless log_rewrite was also set.
1848 60. Avoid a compiler warning on 64-bit systems in dsearch.c by avoiding the use
1849 of (int)(handle) when we know that handle contains (void *)(-1).
1851 61. The Exim daemon panic-logs an error return when it closes the incoming
1852 connection. However "connection reset by peer" seems to be common, and
1853 isn't really an error worthy of noting specially, so that particular error
1856 62. When Exim is trying to find all the local interfaces, it used to panic and
1857 die if the ioctl to get the interface flags failed. However, it seems that
1858 on at least one OS (Solaris 9) it is possible to have an interface that is
1859 included in the list of interfaces, but for which you get a failure error
1860 for this call. This happens when the interface is not "plumbed" into a
1861 protocol (i.e. neither IPv4 nor IPv6). I've changed the code so that a
1862 failure of the "get flags" call assumes that the interface is down.
1864 63. Added a ${eval10: operator, which assumes all numbers are decimal. This
1865 makes life easier for people who are doing arithmetic on fields extracted
1866 from dates, where you often get leading zeros that should not be
1867 interpreted as octal.
1869 64. Added qualify_domain to the redirect router, to override the global
1872 65. If a pathologically long header line contained very many addresses (the
1873 report of this problem mentioned 10 000) and each of them was rewritten,
1874 Exim could use up a very large amount of memory. (It kept on making new
1875 copies of the header line as it rewrote, and never released the old ones.)
1876 At the expense of a bit more processing, the header rewriting function has
1877 been changed so that it no longer eats memory in this way.
1879 66. The generation of the Received: header has been moved from the time that a
1880 message starts to be received, to the time that it finishes. The timestamp
1881 in the Received: header should now be very close to that of the <= log
1882 line. There are two side-effects of this change:
1884 (a) If a message is rejected by a DATA or non-SMTP ACL or local_scan(), the
1885 logged header lines no longer include the local Received: line, because
1886 it has not yet been created. The same applies to a copy of the message
1887 that is returned to a non-SMTP sender when a message is rejected.
1889 (b) When a filter file is tested using -bf, no additional Received: header
1890 is added to the test message. After some thought, I decided that this
1893 This change does not affect the value of $received_for. It is still set
1894 after address rewriting, but before local_scan() is called.
1896 67. Installed the latest Cygwin-specific files from the Cygwin maintainer.
1898 68. GnuTLS: If an empty file is specified for tls_verify_certificates, GnuTLS
1899 gave an unhelpful panic error message, and a defer error. I have managed to
1900 change this behaviour so that it now rejects any supplied certificate,
1901 which seems right, as the list of acceptable certificates is empty.
1903 69. OpenSSL: If an empty file is specified for tls_verify_certificates, OpenSSL
1904 gave an unhelpful defer error. I have not managed to make this reject any
1905 supplied certificates, but the error message it gives is "no certificate
1906 supplied", which is not helpful.
1908 70. exigrep's output now also includes lines that are not associated with any
1909 message, but which match the given pattern. Implemented by a patch from
1910 Martin Sluka, which also tidied up the Perl a bit.
1912 71. Recipient callout verification, like sender verification, was using <> in
1913 the MAIL FROM command. This isn't really the right thing, since the actual
1914 sender may affect whether the remote host accepts the recipient or not. I
1915 have changed it to use the actual sender in the callout; this means that
1916 the cache record is now keyed on a recipient/sender pair, not just the
1917 recipient address. There doesn't seem to be a real danger of callout loops,
1918 since a callout by the remote host to check the sender would use <>.
1919 [SEE ABOVE: changed after hitting problems.]
1921 72. Exim treats illegal SMTP error codes that do not begin with 4 or 5 as
1922 temporary errors. However, in the case of such a code being given after
1923 the end of a data transmission (i.e. after ".") Exim was failing to write
1924 a retry record for the message. (Yes, there was some broken host that was
1925 actually sending 8xx at this point.)
1927 73. An unknown lookup type in a host list could cause Exim to panic-die when
1928 the list was checked. (An example that provoked this was putting <; in the
1929 middle of a list instead of at the start.) If this happened during a DATA
1930 ACL check, a -D file could be left lying around. This kind of configuration
1931 error no longer causes Exim to die; instead it causes a defer errror. The
1932 incident is still logged to the main and panic logs.
1934 74. Buglet left over from Exim 3 conversion. The message "too many messages
1935 in one connection" was written to the rejectlog but not the mainlog, except
1936 when address rewriting (yes!) was being logged.
1938 75. Added write_rejectlog option.
1940 76. When a system filter was run not as root (that is, when system_filter_user
1941 was set), the values of the $n variables were not being returned to the
1942 main process; thus, they were not subsequently available in the $sn
1945 77. Added +return_path_on_delivery log selector.
1947 78. A connection timeout was being treated differently from recipients deferred
1948 when testing hosts_max_try with a message that was older than the host's
1949 retry timeout. (The host should not be counted, thus allowing all hosts to
1950 be tried at least once before bouncing.) This may have been the cause of an
1951 occasionally reported bug whereby a message would remain on the queue
1952 longer than the retry timeout, but would be bounced if a delivery was
1953 forced. I say "may" because I never totally pinned down the problem;
1954 setting up timeout/retry tests is difficult. See also the next item.
1956 79. The ultimate address timeout was not being applied to errors that involved
1957 a combination of host plus message (for example, a timeout on a MAIL
1958 command). When an address resolved to a number of possible hosts, and they
1959 were not all tried for each delivery (e.g. because of hosts_max_try), a
1960 message could remain on the queue longer than the retry timeout.
1962 80. Sieve bug: "stop" inside "elsif" was broken. Applied a patch from Michael
1965 81. Fixed an obscure SMTP outgoing bug which required at least the following
1966 conditions: (a) there was another message waiting for the same server;
1967 (b) the server returned 5xx to all RCPT commands in the first message so
1968 that the message was not completed; (c) the server dropped the connection
1969 or gave a negative response to the RSET that Exim sends to abort the
1970 transaction. The observed case was a dropped connection after DATA that had
1971 been sent in pipelining mode. That is, the server had advertised PIPELINING
1972 but was not implementing it correctly. The effect of the bug was incorrect
1973 behaviour, such as trying another host, and this could lead to a crash.
1979 1. The 3rd arguments to getsockname(), getpeername(), and accept() in exim.c
1980 and daemon.c were passed as pointers to ints; they should have been
1981 pointers to socklen_t variables (which are typically unsigned ints).
1983 2. Some signed/unsigned type warnings in the os.c file for Linux have been
1986 3. Fixed a really odd bug that affected only the testing scheme; patching a
1987 certain fixed string in the binary changed the value of another string that
1988 happened to be identical to the end of the original first string.
1990 4. When gethostbyname() (or equivalent) is passed an IP address as a "host
1991 name", it returns that address as the IP address. On some operating
1992 systems (e.g. Solaris), it also passes back the IP address string as the
1993 "host name". However, on others (e.g. Linux), it passes back an empty
1994 string. Exim wasn't checking for this, and was changing the host name to an
1995 empty string, assuming it had been canonicized.
1997 5. Although rare, it is permitted to have more than one PTR record for a given
1998 IP address. I thought that gethostbyaddr() or getipnodebyaddr() always gave
1999 all the names associated with an address, because they do in Solaris.
2000 However, it seems that they do not in Linux for data that comes from the
2001 DNS. If an address in /etc/hosts has multiple names, they _are_ all given.
2002 I found this out when I moved to a new Linux workstation and tried to run
2003 the Exim test suite.
2005 To get round this problem I have changed the code so that it now does its
2006 own call to the DNS to look up PTR records when searching for a host name.
2007 If nothing can be found in the DNS, it tries gethostbyaddr(), so that
2008 addresses that are only in /etc/hosts are still found.
2010 This behaviour is, however, controlled by an option called host_lookup_
2011 order, which defaults to "bydns:byaddr". If people want to use the other
2012 order, or indeed, just use one or the other means of lookup, they can
2013 specify it in this variable.
2015 6. If a PTR record yields an empty name, Exim treats it as non-existent. In
2016 some operating systems, this comes back from gethostbyaddr() as an empty
2017 string, and this is what Exim used to test for. However, it seems that in
2018 other systems, "." is yielded. Exim now tests for this case too.
2020 7. The values of check_spool_space and check_log_space are now held internally
2021 as a number of kilobytes instead of an absolute number of bytes. If a
2022 numbers is specified without 'K' or 'M', it is rounded up to the nearest
2023 kilobyte. This means that much larger values can be stored.
2025 8. Exim monitor: an attempt to get the action menu when not actually pointing
2026 at a message produces an empty menu entitled "No message selected". This
2027 works on Solaris (OpenWindows). However, XFree86 does not like a menu with
2028 no entries in it ("Shell widget menu has zero width and/or height"). So I
2029 have added a single, blank menu entry in this case.
2031 9. Added ${quote_local_part.
2033 10. MIME decoding is now applied to the contents of Subject: header lines when
2036 11. Now that a reference to $sender_host_address automatically causes a reverse
2037 lookup to occur if necessary (4.13/18), there is no need to arrange for a
2038 host lookup before query-style lookups in lists that might use this
2039 variable. This has therefore been abolished, and the "net-" prefix is no
2040 longer necessary for query-style lookups.
2042 12. The Makefile for SCO_SV contained a setting of LDFLAGS. This appears to
2043 have been a typo for LFLAGS, so it has been changed.
2045 13. The install script calls Exim with "-C /dev/null" in order to find the
2046 version number. If ALT_CONFIG_PREFIX was set, this caused an error message
2047 to be output. Howeve, since Exim outputs its version number before the
2048 error, it didn't break the script. It just looked ugly. I fixed this by
2049 always allowing "-C /dev/null" if the caller is root.
2051 14. Ignore overlarge ACL variable number when reading spool file - insurance
2052 against a later release with more variables having written the file.
2054 15. The standard form for an IPv6 address literal was being rejected by EHLO.
2055 Example: [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
2056 this, as well as the form without the "IPv6" on the front.
2058 16. Added CHOWN_COMMAND=/usr/sbin/chown and LIBS=-lresolv to the
2059 OS/Makefile-Darwin file.
2061 17. Fixed typo in lookups/ldap.c: D_LOOKUP should be D_lookup. This applied
2062 only to LDAP libraries that do not have LDAP_OPT_DEREF.
2064 18. After change 4.21/52, "%ld" was used to format the contents of the $inode
2065 variable. However, some OS use ints for inodes. I've added cast to long int
2066 to get rid of the compiler warning.
2068 19. I had forgotten to lock out "/../" in configuration file names when
2069 ALT_CONFIG_PREFIX was set.
2071 20. Routers used for verification do not need to specify transports. However,
2072 if such a router generated a host list, and callout was configured, Exim
2073 crashed, because it could not find a port number from the (non-existent)
2074 transport. It now assumes port 25 in this circumstance.
2076 21. Added the -t option to exigrep.
2078 22. If LOOKUP_LSEARCH is defined, all three linear search methods (lsearch,
2079 wildlsearch, nwildlsearch) are compiled. LOOKUP_WILDLSEARCH and LOOKUP_
2080 NWILDLSEARCH are now obsolete, but retained for compatibility. If either of
2081 them is set, LOOKUP_LSEARCH is forced.
2083 23. "exim -bV" now outputs a list of lookups that are included in the binary.
2085 24. Added sender and host information to the "rejected by local_scan()" log
2086 line; previously there was no indication of these.
2088 25. Added .include_if_exists.
2090 26. Change 3.952/11 added an explicit directory sync on top of a file sync for
2091 Linux. It turns out that not all file systems support this. Apparently some
2092 versions of NFS do not. (It's rare to put Exim's spool on NFS, but people
2093 do it.) To cope with this, the error EINVAL, which means that sync-ing is
2094 not supported on the file descriptor, is now ignored when Exim is trying to
2095 sync a directory. This applies only to Linux.
2097 27. Added -DBIND_8_COMPAT to the CLFAGS setting for Darwin.
2099 28. In Darwin (MacOS X), the PAM headers are in /usr/include/pam and not in
2100 /usr/include/security. There's now a flag in OS/os.h-Darwin to cope with
2103 29. Added support for maildirsize files from supplied patch (modified a bit).
2105 30. The use of :fail: followed by an empty string could lead Exim to respond to
2106 sender verification failures with (e.g.):
2108 550 Verification failed for <xxx>
2109 550 Sender verify failed
2111 where the first response line was missing the '-' that indicates it is not
2112 the final line of the response.
2114 31. The loop for finding the name of the user that called Exim had a hardwired
2115 limit of 10; it now uses the value of finduser_retries, which is used for
2116 all other user lookups.
2118 32. Added $received_count variable, available in data and not_smtp ACLs, and at
2121 33. Exim was neglecting to zero errno before one call of strtol() when
2122 expanding a string and expecting an integer value. On some systems this
2123 resulted in spurious "integer overflow" errors. Also, it was casting the
2124 result into an int without checking.
2126 34. Testing for a connection timeout using "timeout_connect" in the retry rules
2127 did not work. The code looks as if it has *never* worked, though it appears
2128 to have been documented since at least releast 1.62. I have made it work.
2130 35. The "timeout_DNS" error in retry rules, also documented since at least
2131 1.62, also never worked. As it isn't clear exactly what this means, and
2132 clearly it isn't a major issue, I have abolished the feature by treating it
2133 as "timeout", and writing a warning to the main and panic logs.
2135 36. The display of retry rules for -brt wasn't always showing the error code
2138 37. Added new error conditions to retry rules: timeout_A, timeout_MX,
2139 timeout_connect_A, timeout_connect_MX.
2141 38. Rewriting the envelope sender at SMTP time did not allow it to be rewritten
2142 to the empty sender.
2144 39. The daemon was not analysing the content of -oX till after it had closed
2145 stderr and disconnected from the controlling terminal. This meant that any
2146 syntax errors were only noted on the panic log, and the return code from
2147 the command was 0. By re-arranging the code a little, I've made the
2148 decoding happen first, so such errors now appear on stderr, and the return
2149 code is 1. However, the actual setting up of the sockets still happens in
2150 the disconnected process, so errors there are still only recorded on the
2153 40. A daemon listener on a wildcard IPv6 socket that also accepts IPv4
2154 connections (as happens on some IP stacks) was logged at start up time as
2155 just listening for IPv6. It now logs "IPv6 with IPv4". This differentiates
2156 it from "IPv6 and IPv4", which means that two separate sockets are being
2159 41. The debug output for gethostbyname2() or getipnodebyname() failures now
2160 says whether AF_INET or AF_INET6 was passed as an argument.
2162 42. Exiwhat output was messed up when time zones were included in log
2165 43. Exiwhat now gives more information about the daemon's listening ports,
2166 and whether -tls-on-connect was used.
2168 44. The "port" option of the smtp transport is now expanded.
2170 45. A "message" modifier in a "warn" statement in a non-message ACL was being
2171 silently ignored. Now an error message is written to the main and panic
2174 46. There's a new ACL modifier called "logwrite" which writes to a log file
2175 as soon as it is encountered.
2177 47. Added $local_user_uid and $local_user_gid at routing time.
2179 48. Exim crashed when trying to verify a sender address that was being
2182 49. Exim was recognizing only a space character after ".include". It now also
2183 recognizes a tab character.
2185 50. Fixed several bugs in the Perl script that creates the exim.8 man page by
2186 extracting the relevant information from the specification. The man page no
2187 longer contains scrambled data for the -d option, and I've added a section
2188 at the front about calling Exim under different names.
2190 51. Added "extra_headers" argument to the "mail" command in filter files.
2192 52. Redirecting mail to an unqualified address in a Sieve filter caused Exim to
2195 53. Installed eximstats 1.29.
2197 54. Added transport_filter_timeout as a generic transport option.
2199 55. Exim no longer adds an empty Bcc: header to messages that have no To: or
2200 Cc: header lines. This was required by RFC 822, but it not required by RFC
2203 56. Exim used to add From:, Date:, and Message-Id: header lines to any
2204 incoming messages that did not have them. Now it does so only if the
2205 message originates locally, that is, if there is no associated remote host
2206 address. When Resent- header lines are present, this applies to the Resent-
2207 lines rather than the non-Resent- lines.
2209 57. Drop incoming SMTP connection after too many syntax or protocol errors. The
2210 limit is controlled by smtp_max_synprot_errors, defaulting to 3.
2212 58. Messages for configuration errors now include the name of the main
2213 configuration file - useful now that there may be more than one file in a
2214 list (.included file names were always shown).
2216 59. Change 4.21/82 (run initgroups() when starting the daemon) causes problems
2217 for those rare installations that do not start the daemon as root or run it
2218 setuid root. I've cut out the call to initgroups() if the daemon is not
2221 60. The Exim user and group can now be bound into the binary as text strings
2222 that are looked up at the start of Exim's processing.
2224 61. Applied a small patch for the Interbase code, supplied by Ard Biesheuvel.
2226 62. Added $mailstore_basename variable.
2228 63. Installed patch to sieve.c from Michael Haardt.
2230 64. When Exim failed to open the panic log after failing to open the main log,
2231 the original message it was trying to log was written to stderr and debug
2232 output, but if they were not available (the usual case in production), it
2233 was lost. Now it is written to syslog before the two lines that record the
2234 failures to open the logs.
2236 65. Users' Exim filters run in subprocesses under the user's uid. It is
2237 possible for a "deliver" command or an alias in a "personal" command to
2238 provoke an address rewrite. If logging of address rewriting is configured,
2239 this fails because the process is not running as root or exim. There may be
2240 a better way of dealing with this, but for the moment (because 4.30 needs
2241 to be released), I have disabled address rewrite logging when running a
2242 filter in a non-root, non-exim process.
2248 1. The buildconfig auxiliary program wasn't quoting the value set for
2249 HEADERS_CHARSET. This caused a compilation error complaining that 'ISO' was
2250 not defined. This bug was masked in 4.22 by the effect that was fixed in
2253 2. Some messages that were rejected after a message id was allocated were
2254 shown as "incomplete" by exigrep. It no longer does this for messages that
2255 are rejected by local_scan() or the DATA or non-SMTP ACLs.
2257 3. If a Message-ID: header used a domain literal in the ID, and Exim did not
2258 have allow_domain_literals set, the ID did not get logged in the <= line.
2259 Domain literals are now always recognized in Message-ID: header lines.
2261 4. The first argument for a ${extract expansion item is the key name or field
2262 number. Leading and trailing spaces in this item were not being ignored,
2263 causing some misleading effects.
2265 5. When deliver_drop_privilege was set, single queue runner processes started
2266 manually (i.e. by the command "exim -q") or by the daemon (which uses the
2267 same command in the process it spins off) were not dropping privilege.
2269 6. When the daemon running as "exim" started a queue runner, it always
2270 re-executed Exim in the spun-off process. This is a waste of effort when
2271 deliver_drop_privilege is set. The new process now just calls the
2272 queue-runner function directly.
2278 1. Typo in the src/EDITME file: it referred to HEADERS_DECODE_TO instead of
2281 2. Change 4.21/73 introduced a bug. The pid file path set by -oP was being
2282 ignored. Though the use of -oP was forcing the writing of a pid file, it
2283 was always written to the default place.
2285 3. If the message "no IP address found for host xxxx" is generated during
2286 incoming verification, it is now followed by identification of the incoming
2287 connection (so you can more easily find what provoked it).
2289 4. Bug fix for Sieve filters: "stop" inside a block was not working properly.
2291 5. Added some features to "harden" Exim a bit more against certain attacks:
2293 (a) There is now a build-time option called FIXED_NEVER_USERS that can
2294 be put in Local/Makefile. This is like the never_users runtime option,
2295 but it cannot be overridden. The default setting is "root".
2297 (b) If ALT_CONFIG_PREFIX is defined in Local/Makefile, it specifies a
2298 prefix string with which any file named in a -C command line option
2301 (c) If ALT_CONFIG_ROOT_ONLY is defined in Local/Makefile, root privilege
2302 is retained for -C and -D only if the caller of Exim is root. Without
2303 it, the exim user may also use -C and -D and retain privilege.
2305 (d) If DISABLE_D_OPTION is defined in Local/Makefile, the use of the -D
2306 command line option is disabled.
2308 6. Macro names set by the -D option must start with an upper case letter, just
2309 like macro names defined in the configuration file.
2311 7. Added "dereference=" facility to LDAP.
2313 8. Two instances of the typo "uknown" in the source files are fixed.
2315 9. If a PERL_COMMAND setting in Local/Makefile was not at the start of a line,
2316 the Configure-Makefile script screwed up while processing it.
2318 10. Incorporated PCRE 4.4.
2320 11. The SMTP synchronization check was not operating right at the start of an
2321 SMTP session. For example, it could not catch a HELO sent before the client
2322 waited for the greeting. There is now a check for outstanding input at the
2323 point when the greeting is written. Because of the duplex, asynchronous
2324 nature of TCP/IP, it cannot be perfect - the incorrect input may be on its
2325 way, but not yet received, when the check is performed.
2327 12. Added tcp_nodelay to make it possible to turn of the setting of TCP_NODELAY
2328 on TCP/IP sockets, because this apparently causes some broken clients to
2331 13. Installed revised OS/Makefile-CYGWIN and OS/os.c-cygwin (the .h file was
2332 unchanged) from the Cygwin maintainer.
2334 14. The code for -bV that shows what is in the binary showed "mbx" when maildir
2335 was supported instead of testing for mbx. Effectively a typo.
2337 15. The spa authenticator server code was not checking that the input it
2338 received was valid base64.
2340 16. The debug output line for the "set" modifier in ACLs was not showing the
2341 name of the variable that was being set.
2343 17. Code tidy: the variable type "vtype_string" was never used. Removed it.
2345 18. Previously, a reference to $sender_host_name did not cause a DNS reverse
2346 lookup on its own. Something else was needed to trigger the lookup. For
2347 example, a match in host_lookup or the need for a host name in a host list.
2348 Now, if $sender_host_name is referenced and the host name has not yet been
2349 looked up, a lookup is performed. If the lookup fails, the variable remains
2350 empty, and $host_lookup_failed is set to "1".
2352 19. Added "eqi" as a case-independent comparison operator.
2354 20. The saslauthd authentication condition could segfault if neither service
2355 nor realm was specified.
2357 21. If an overflowing value such as "2048M" was set for message_size_limit, the
2358 error message that was logged was misleading, and incoming SMTP
2359 connections were dropped. The message is now more accurate, and temporary
2360 errors are given to SMTP connections.
2362 22. In some error situations (such as 21 above) Exim rejects all SMTP commands
2363 (except RSET) with a 421 error, until QUIT is received. However, it was
2364 failing to send a response to QUIT.
2366 23. The HELO ACL was being run before the code for helo_try_verify_hosts,
2367 which made it impossible to use "verify = helo" in the HELO ACL. The HELO
2368 ACL is now run after the helo_try_verify_hosts code.
2370 24. "{MD5}" and "{SHA1}" are now recognized as equivalent to "{md5"} and
2371 "{sha1}" in the "crypteq" expansion condition (in fact the comparison is
2372 case-independent, so other case variants are also recognized). Apparently
2373 some systems use these upper case variants.
2375 25. If more than two messages were waiting for the same host, and a transport
2376 filter was specified for the transport, Exim sent two messages over the
2377 same TCP/IP connection, and then failed with "socket operation on non-
2378 socket" when it tried to send the third.
2380 26. Added Exim::debug_write and Exim::log_write for embedded Perl use.
2382 27. The extern definition of crypt16() in expand.c was not being excluded when
2383 the OS had its own crypt16() function.
2385 28. Added bounce_return_body as a new option, and bounce_return_size_limit
2386 as a preferred synonym for return_size_limit, both as an option and as an
2389 29. Added LIBS=-liconv to OS/Makefile-OSF1.
2391 30. Changed the default configuration ACL to relax the local part checking rule
2392 for addresses that are not in any local domains. For these addresses,
2393 slashes and pipe symbols are allowed within local parts, but the sequence
2394 /../ is explicitly forbidden.
2396 31. SPA server authentication was not clearing the challenge buffer before
2399 32. log_message in a "warn" ACL statement was writing to the reject log as
2400 well as to the main log, which contradicts the documentation and doesn't
2401 seem right (because no rejection is happening). So I have stopped it.
2403 33. Added Ard Biesheuvel's lookup code for accessing an Interbase database.
2404 However, I am unable to do any testing of this.
2406 34. Fixed an infelicity in the appendfile transport. When checking directories
2407 for a mailbox, to see if any needed to be created, it was accidentally
2408 using path names with one or more superfluous leading slashes; tracing
2409 would show up entries such as stat("///home/ph10", 0xFFBEEA48).
2411 35. If log_message is set on a "discard" verb in a MAIL or RCPT ACL, its
2412 contents are added to the log line that is written for every discarded
2413 recipient. (Previously a log_message setting was ignored.)
2415 36. The ${quote: operator now quotes the string if it is empty.
2417 37. The install script runs exim in order to find its version number. If for
2418 some reason other than non-existence or emptiness, which it checks, it
2419 could not run './exim', it was installing it with an empty version number,
2420 i.e. as "exim-". This error state is now caught, and the installation is
2423 38. An argument was missing from the function that creates an error message
2424 when Exim fails to connect to the socket for saslauthd authentication.
2425 This could cause Exim to crash, or give a corrupted message.
2427 39. Added isip, isip4, and isip6 to ${if conditions.
2429 40. The ACL variables $acl_xx are now saved with the message, and can be
2430 accessed later in routers, transports, and filters.
2432 41. The new lookup type nwildlsearch is like wildlsearch, except that the key
2433 strings in the file are not string-expanded.
2435 42. If a MAIL command specified a SIZE value that was too large to fit into an
2436 int variable, the check against message_size_limit failed. Such values are
2437 now forced to INT_MAX, which is around 2Gb for a 32-bit variable. Maybe one
2438 day this will have to be increased, but I don't think I want to be around
2439 when emails are that large.
2446 1. Removed HAVE_ICONV=yes from OS/Makefile-FreeBSD, since it seems that
2447 iconv() is not standard in FreeBSD.
2449 2. Change 4.21/17 was buggy and could cause stack overwriting on a system with
2450 IPv6 enabled. The observed symptom was a segmentation fault on return from
2451 the function os_common_find_running_interfaces() in src/os.c.
2453 3. In the check_special_case() function in daemon.c I had used "errno" as an
2454 argument name, which causes warnings on some systems. This was basically a
2455 typo, since it was named "eno" in the comments!
2457 4. The code that waits for the clock to tick (at a resolution of some fraction
2458 of a second) so as to ensure message-id uniqueness was always waiting for
2459 at least one whole tick, when it could have waited for less. [This is
2460 almost certainly not relevant at current processor speeds, where it is
2461 unlikely to ever wait at all. But we try to future-proof.]
2463 5. The function that sleeps for a time interval that includes fractions of a
2464 second contained a race. It did not block SIGALRM between setting the
2465 timer, and suspending (a couple of lines later). If the interval was short
2466 and the sigsuspend() was delayed until after it had expired, the suspension
2467 never ended. On busy systems this could lead to processes getting stuck for
2470 6. Some uncommon configurations may cause a lookup to happen in a queue runner
2471 process, before it forks any delivery processes. The open lookup caching
2472 mechanism meant that the open file or database connection was passed into
2473 the delivery process. The problem was that delivery processes always tidy
2474 up cached lookup data. This could cause a problem for the next delivery
2475 process started by the queue runner, because the external queue runner
2476 process does not know about the closure. So the next delivery process
2477 still has data in the lookup cache. In the case of a file lookup, there was
2478 no problem because closing a file descriptor in a subprocess doesn't affect
2479 the parent. However, if the lookup was caching a connection to a database,
2480 the connection was closed, and the second delivery process was likely to
2481 see errors such as "PGSQL: query failed: server closed the connection
2482 unexpectedly". The problem has been fixed by closing all cached lookups
2483 in a queue runner before running a delivery process.
2485 7. Compiler warning on Linux for the second argument of iconv(), which doesn't
2486 seem to have the "const" qualifier which it has on other OS. I've
2489 8. Change 4.21/2 was too strict. It is only if there are two authenticators
2490 *of the same type* (client or server) with the same public name that an
2491 error should be diagnosed.
2493 9. When Exim looked up a host name for an IP address, but failed to find the
2494 original IP address when looking up the host name (a safety check), it
2495 output the message "<ip address> does not match any IP for NULL", which was
2496 confusing, to say the least. The bug was that the host name should have
2497 appeared instead of "NULL".
2499 10. Since release 3.03, if Exim is called by a uid other than root or the Exim
2500 user that is built into the binary, and the -C or -D options is used, root
2501 privilege is dropped before the configuration file is read. In addition,
2502 logging is switched to stderr instead of the normal log files. If the
2503 configuration then re-defines the Exim user, the unprivileged environment
2504 is probably not what is expected, so Exim logs a panic warning message (but
2507 However, if deliver_drop_privilege is set, the unprivileged state may well
2508 be exactly what is intended, so the warning has been cut out in that case,
2509 and Exim is allowed to try to write to its normal log files.
2515 1. smtp_return_error_details was not giving details for temporary sender
2516 or receiver verification errors.
2518 2. Diagnose a configuration error if two authenticators have the same public
2521 3. Exim used not to create the message log file for a message until the first
2522 delivery attempt. This could be confusing when incoming messages were held
2523 for policy or load reasons. The message log file is now created at the time
2524 the message is received, and an initial "Received" line is written to it.
2526 4. The automatically generated man page for command line options had a minor
2527 bug that caused no ill effects; however, a more serious problem was that
2528 the procedure for building the man page automatically didn't always
2529 operate. Consequently, release 4.20 contains an out-of-date version. This
2530 shouldn't happen again.
2532 5. When building Exim with embedded Perl support, the script that builds the
2533 Makefile was calling 'perl' to find its compile-time parameters, ignoring
2534 any setting of PERL_COMMAND in Local/Makefile. This is now fixed.
2536 6. The freeze_tell option was not being used for messages that were frozen on
2537 arrival, either by an ACL or by local_scan().
2539 7. Added the smtp_incomplete_transaction log selector.
2541 8. After STARTTLS, Exim was not forgetting that it had advertised AUTH, so it
2542 was accepting AUTH without a new EHLO.
2544 9. Added tls_remember_esmtp to cope with YAEB. This allows AUTH and other
2545 ESMTP extensions after STARTTLS without a new EHLO, in contravention of the
2548 10. Logging of TCP/IP connections (when configured) now happens in the main
2549 daemon process instead of the child process, so that the TCP/IP connection
2550 count is more accurate (but it can never be perfect).
2552 11. The use of "drop" in a nested ACL was not being handled correctly in the
2553 outer ACL. Now, if condition failure induced by the nested "drop" causes
2554 the outer ACL verb to deny access ("accept" or "discard" after "endpass",
2555 or "require"), the connection is dropped.
2557 12. Similarly, "discard" in a nested ACL wasn't being handled. A nested ACL
2558 that yield "discard" can now be used with an "accept" or a "discard" verb,
2559 but an error is generated for any others (because I can't see a useful way
2560 to define what should happen).
2562 13. When an ACL is read dynamically from a file (or anywhere else), the lines
2563 are now processed in the same way as lines in the Exim configuration file.
2564 In particular, continuation lines are supported.
2566 14. Added the "dnslists = a.b.c!=n.n.n.n" feature.
2568 15. Added -ti meaning -t -i.
2570 16. Check for letters, digits, hyphens, and dots in the names of dnslist
2571 domains, and warn by logging if others are found.
2573 17. At least on BSD, alignment is not guarenteed for the array of ifreq's
2574 returned from GIFCONF when Exim is trying to find the list of interfaces on
2575 a host. The code in os.c has been modified to copy each ifreq to an aligned
2576 structure in all cases.
2578 Also, in some cases, the returned ifreq's were being copied to a 'struct
2579 ifreq' on the stack, which was subsequently passed to host_ntoa(). That
2580 means the last couple of bytes of an IPv6 address could be chopped if the
2581 ifreq contained only a normal sockaddr (14 bytes storage).
2583 18. Named domain lists were not supported in the hosts_treat_as_local option.
2584 An entry such as +xxxx was not recognized, and was treated as a literal
2587 19. Ensure that header lines added by a DATA ACL are included in the reject log
2588 if the ACL subsequently rejects the message.
2590 20. Upgrade the cramtest.pl utility script to use Digest::MD5 instead of just
2591 MD5 (which is deprecated).
2593 21. When testing a filter file using -bf, Exim was writing a message when it
2594 took the sender from a "From " line in the message, but it was not doing so
2595 when it took $return_path from a Return-Path: header line. It now does.
2597 22. If the contents of a "message" modifier for a "warn" ACL verb do not begin
2598 with a valid header line field name (a series of printing characters
2599 terminated by a colon, Exim now inserts X-ACL-Warn: at the beginning.
2601 23. Changed "disc" in the source to "disk" to conform to the documentation and
2602 the book and for uniformity.
2604 24. Ignore Sendmail's -Ooption=value command line item.
2606 25. When execve() failed while trying to run a command in a pipe transport,
2607 Exim was returning EX_UNAVAILBLE (69) from the subprocess. However, this
2608 could be confused with a return value of 69 from the command itself. This
2609 has been changed to 127, the value the shell returns if it is asked to run
2610 a non-existent command. The wording for the related log line suggests a
2611 non-existent command as the problem.
2613 26. If received_header_text expands to an empty string, do not add a Received:
2614 header line to the message. (Well, it adds a token one on the spool, but
2615 marks it "old" so that it doesn't get used or transmitted.)
2617 27. Installed eximstats 1.28 (addition of -nt option).
2619 28. There was no check for failure on the call to getsockname() in the daemon
2620 code. This can fail if there is a shortage of resources on the system, with
2621 ENOMEM, for example. A temporary error is now given on failure.
2623 29. Contrary to the C standard, it seems that in some environments, the
2624 equivalent of setlocale(LC_ALL, "C") is not obeyed at the start of a C
2625 program. Exim now does this explicitly; it affects the formatting of
2626 timestamps using strftime().
2628 30. If exiqsumm was given junk data, it threw up some uninitialized variable
2629 complaints. I've now initialized all the variables, to avoid this.
2631 32. Header lines added by a system filter were not being "seen" during
2632 transport-time rewrites.
2634 33. The info_callback() function passed to OpenSSL is set up with type void
2635 (*)(SSL *, int, int), as described somewhere. However, when calling the
2636 function (actually a macro) that sets it up, the type void(*)() is
2637 expected. I've put in a cast to prevent warnings from picky compilers.
2639 34. If a DNS black list lookup found a CNAME record, but there were no A
2640 records associated with the domain it pointed at, Exim crashed.
2642 35. If a DNS black list lookup returned more than one A record, Exim ignored
2643 all but the first. It now scans all returned addresses if a particular IP
2644 value is being sought. In this situation, the contents of the
2645 $dnslist_value variable are a list of all the addresses, separated by a
2648 36. Tightened up the rules for host name lookups using reverse DNS. Exim used
2649 to accept a host name and all its aliases if the forward lookup for any of
2650 them yielded the IP address of the incoming connection. Now it accepts only
2651 those names whose forward lookup yields the correct IP address. Any other
2652 names are discarded. This closes a loophole whereby a rogue DNS
2653 administrator could create reverse DNS records to break through a
2654 wildcarded host restriction in an ACL.
2656 37. If a user filter or a system filter that ran in a subprocess used any of
2657 the numerical variables ($1, $2 etc), or $thisaddress, in a pipe command,
2658 the wrong values were passed to the pipe command ($thisaddress had the
2659 value of $0, $0 had the value of $1, etc). This bug was introduced by
2660 change 4.11/101, and not discovered because I wrote an inadequate test. :-(
2662 38. Improved the line breaking for long SMTP error messages from ACLs.
2663 Previously, if there was no break point between 40 and 75 characters, Exim
2664 left the rest of the message alone. Two changes have been made: (a) I've
2665 reduced the minimum length to 35 characters; (b) if it can't find a break
2666 point between 35 and 75 characters, it looks ahead and uses the first one
2667 that it finds. This may give the occasional overlong line, but at least the
2668 remaining text gets split now.
2670 39. Change 82 of 4.11 was unimaginative. It assumed the limit on the number of
2671 file descriptors might be low, and that setting 1000 would always raise it.
2672 It turns out that in some environments, the limit is already over 1000 and
2673 that lowering it causes trouble. So now Exim takes care not to decrease it.
2675 40. When delivering a message, the value of $return_path is set to $sender_
2676 address at the start of routing (routers may change the value). By an
2677 oversight, this default was not being set up when an address was tested by
2678 -bt or -bv, which affected the outcome if any router or filter referred to
2681 41. The idea of the "warn" ACL verb is that it adds a header or writes to the
2682 log only when "message" or "log_message" are set. However, if one of the
2683 conditions was an address verification, or a call to a nested ACL, the
2684 messages generated by the underlying test were being passed through. This
2685 no longer happens. The underlying message is available in $acl_verify_
2686 message for both "message" and "log_message" expansions, so it can be
2687 passed through if needed.
2689 42. Added RFC 2047 interpretation of header lines for $h_ expansions, with a
2690 new expansion $bh_ to give the encoded byte string without charset
2691 translation. Translation happens only if iconv() is available; HAVE_ICONV
2692 indicates this at build time. HEADERS_CHARSET gives the charset to
2693 translate to; headers_charset can change it in the configuration, and
2694 "headers charset" can change it in an individual filter file.
2696 43. Now that we have a default RFC 2047 charset (see above), the code in Exim
2697 that creates RFC 2047 encoded "words" labels them as that charset instead
2698 of always using iso-8859-1. The cases are (i) the explicit ${rfc2047:
2699 expansion operator; (ii) when Exim creates a From: line for a local
2700 message; (iii) when a header line is rewritten to include a "phrase" part.
2702 44. Nasty bug in exiqsumm: the regex to skip already-delivered addresses was
2703 buggy, causing it to skip the first lines of messages whose message ID
2704 ended in 'D'. This would not have bitten before Exim release 4.14, because
2705 message IDs were unlikely to end in 'D' before then. The effect was to have
2706 incorrect size information for certain domains.
2708 45. #include "config.h" was missing at the start of the crypt16.c module. This
2709 caused trouble on Tru64 (aka OSF1) systems, because HAVE_CRYPT16 was not
2712 46. If there was a timeout during a "random" callout check, Exim treated it as
2713 a failure of the random address, and carried on sending RSET and the real
2714 address. If the delay was just some slowness somewhere, the response to the
2715 original RCPT would be taken as a response to RSET and so on, causing
2716 mayhem of various kinds.
2718 47. Change 50 for 4.20 was a heap of junk. I don't know what I was thinking
2719 when I implemented it. It didn't allow for the fact that some option values
2720 may legitimatetly be negative (e.g. size_addition), and it didn't even do
2721 the right test for positive values.
2723 48. Domain names in DNS records are case-independent. Exim always looks them up
2724 in lower case. Some resolvers return domain names in exactly the case they
2725 appear in the zone file, that is, they may contain uppercase letters. Not
2726 all resolvers do this - some return always lower case. Exim was treating a
2727 change of case by a resolver as a change of domain, similar to a widening
2728 of a domain abbreviation. This triggered its re-routing code and so it was
2729 trying to route what was effectively the same domain again. This normally
2730 caused routing to fail (because the router wouldn't handle the domain
2731 twice). Now Exim checks for this case specially, and just changes the
2732 casing of the domain that it ultimately uses when it transmits the message
2735 49. Added Sieve (RFC 3028) support, courtesy of Michael Haardt's contributed
2738 50. If a filter generated a file delivery with a non-absolute name (possible if
2739 no home directory exists for the router), the forbid_file option was not
2742 51. Added '&' feature to dnslists, to provide bit mask matching in addition to
2743 the existing equality matching.
2745 52. Exim was using ints instead of ino_t variables in some places where it was
2746 dealing with inode numbers.
2748 53. If TMPDIR is defined in Local/Makefile (default in src/EDITME is
2749 TMPDIR="/tmp"), Exim checks for the presence of an environment variable
2750 called TMPDIR, and if it finds it is different, it changes its value.
2752 54. The smtp_printf() function is now made available to local_scan() so
2753 additional output lines can be written before returning. There is also an
2754 smtp_fflush() function to enable the detection of a dropped connection.
2755 The variables smtp_input and smtp_batched_input are exported to
2758 55. Changed the default runtime configuration: the message "Unknown user"
2759 has been removed from the ACL, and instead placed on the localuser router,
2760 using the cannot_route_message feature. This means that any verification
2761 failures that generate their own messages won't get overridden. Similarly,
2762 the "Unrouteable address" message that was in the ACL for unverifiable
2763 relay addresses has also been removed.
2765 56. Added hosts_avoid_esmtp to the smtp transport.
2767 57. The exicyclog script was not checking for the esoteric option
2768 CONFIGURE_FILE_USE_EUID in the Local/Makefile. It now does this, but it
2769 will work only if exicyclog is run under the appropriate euid.
2771 58. Following a discussion on the list, the rules by which Exim recognises line
2772 endings on incoming messages have been changed. The -dropcr and drop_cr
2773 options are now no-ops, retained only for backwards compatibility. The
2774 following line terminators are recognized: LF CRLF CR. However, special
2775 processing applies to CR:
2777 (i) The sequence CR . CR does *not* terminate an incoming SMTP message,
2778 nor a local message in the state where . is a terminator.
2780 (ii) If a bare CR is encountered in a header line, an extra space is added
2781 after the line terminator so as not to end the header. The reasoning
2782 behind this is that bare CRs in header lines are most likely either
2783 to be mistakes, or people trying to play silly games.
2785 59. The size of a message, as listed by "-bp" or in the Exim monitor window,
2786 was being incorrectly given as 18 bytes larger than it should have been.
2787 This is a VOB (very old bug).
2789 60. This may never have affected anything current, but just in case it has:
2790 When the local host is found other than at the start of a list of hosts,
2791 the local host, those with the same MX, and any that follow, are discarded.
2792 When the list in question was part of a longer list of hosts, the following
2793 hosts (not currently being processed) were also being discarded. This no
2794 longer happens. I'm not sure if this situation could ever has previously
2797 61. Added the "/MX" feature to lists of hosts in the manualroute and query
2800 62. Whenever Exim generates a new message, it now adds an Auto-Submitted:
2801 header. This is something that is recommended in a new Internet Draft, and
2802 is something that is documented as being done by Sendmail. There are two
2803 possible values. For messages generated by the autoreply transport, Exim
2806 Auto-Submitted: auto-replied
2808 whereas for all other generated messages (e.g. bounces) it adds
2810 Auto-Submitted: auto-generated
2812 63. The "personal" condition in filters now includes a test for the
2813 Auto-Submitted: header. If it contains the string "auto-" the message it
2814 not considered personal.
2816 64. Added rcpt_include_affixes as a generic transport option.
2818 65. Added queue_only_override (default true).
2820 66. Added the syslog_duplication option.
2822 67. If what should have been the first header line of a message consisted of
2823 a space followed by a colon, Exim was mis-interpreting it as a header line.
2824 It isn't of course - it is syntactically invalid and should therefore be
2825 treated as the start of the message body. The misbehaviour could have
2826 caused a number of strange effects, including loss of data in subsequent
2827 header lines, and spool format errors.
2829 68. Formerly, the AUTH parameter on a MAIL command was trusted only if the
2830 client host had authenticated. This control can now be exercised by an ACL
2831 for more flexibility.
2833 69. By default, callouts do not happen when testing with -bh. There is now a
2834 variant, -bhc, which does actually run the callout code, including
2835 consulting and updating the callout cache.
2837 70. Added support for saslauthd authentication, courtesy of Alexander
2840 71. If statvfs() failed on the spool or log directories while checking their
2841 size for availability, Exim confusingly gave the error "space shortage".
2842 Furthermore, in debugging mode it crashed with a floating point exception.
2843 These checks are done if check_{spool,log}_{space,inodes} are set, and when
2844 an SMTP message arrives with SIZE= on the MAIL command. As this is a really
2845 serious problem, Exim now writes to the main and panic logs when this
2846 happens, with details of the failure. It then refuses to accept the
2847 incoming message, giving the message "spool directory problem" or "log
2848 directory problem" with a 421 code for SMTP messages.
2850 72. When Exim is about to re-exec itself, it ensures that the file descriptors
2851 0, 1, and 2 exist, because some OS complain for execs without them (see
2852 ChangeLog 4.05/30). If necessary, Exim opens /dev/null to use for these
2853 descriptors. However, the code omitted to check that the open succeeded,
2854 causing mysterious errors if for some reason the permissions on /dev/null
2855 got screwed. Now Exim writes a message to the main and panic logs, and
2856 bombs out if it can't open /dev/null.
2858 73. Re-vamped the way daemon_smtp_port, local_interfaces, and -oX work and
2859 interact so that it is all more flexible. It is supposed to remain
2860 backwards compatible. Also added extra_local_interfaces.
2862 74. Invalid data sent to a SPA (NTLM) server authenticator could cause the code
2863 to bomb out with an assertion failure - to the client this appears as a
2864 connection drop. This problem occurs in the part of the code that was taken
2865 from the Samba project. Fortunately, the assertion is in a very simple
2866 function, so I have fixed this by reproducing the function inline in the
2867 one place where it is called, and arranging for authentication to fail
2868 instead of killing the process with assert().
2870 75. The SPA client code was not working when the server requested OEM rather
2871 than Unicode encoding.
2873 76. Added code to make require_files with a specific uid setting more usable in
2874 the case where statting the file as root fails - usually a non-root-mounted
2875 NFS file system. When this happens and the failure is EACCES, Exim now
2876 forks a subprocess and does the per-uid checking as the relevant uid.
2878 77. Added process_log_path.
2880 78. If log_file_path was not explicitly set, a setting of check_log_space or
2881 check_log_inodes was ignored.
2883 79. If a space check for the spool or log partitions fails, the incident is now
2884 logged. Of course, in the latter case the data may get lost...
2886 80. Added the %p formatting code to string_format() so that it can be used to
2887 print addresses in debug_print(). Adjusted all the address printing in the
2888 debugging in store.c to use %p rather than %d.
2890 81. There was a concern that a line of code in smtp_in.c could overflow a
2891 buffer if a HELO/EHLO command was given followed by 500 or so spaces. As
2892 initially expressed, the concern was not well-founded, because trailing
2893 spaces are removed early. However, if the trailing spaces were followed by
2894 a NULL, they did not get removed, so the overflow was possible. Two fixes
2897 (a) I re-wrote the offending code in a cleaner fashion.
2898 (b) If an incoming SMTP command contains a NULL character, it is rejected
2901 82. When Exim changes uid/gid to the Exim user at daemon start time, it now
2902 runs initgroups(), so that if the Exim user is in any additional groups,
2903 they will be used during message reception.
2909 The change log for 4.20 and earlier releases has been archived.