1 $Cambridge: exim/doc/doc-txt/ChangeLog,v 1.136 2005/05/11 08:05:10 ph10 Exp $
3 Change log file for Exim from version 4.21
4 -------------------------------------------
10 TF/01 Added support for Client SMTP Authorization. See NewStuff for details.
12 PH/01 When a transport filter timed out in a pipe delivery, and the pipe
13 command itself ended in error, the underlying message about the transport
14 filter timeout was being overwritten with the pipe command error. Now the
15 underlying error message should be appended to the second error message.
17 TK/01 Fix poll() being unavailable on Mac OSX 10.2.
23 TK/01 Added Yahoo DomainKeys support via libdomainkeys. See
24 doc/experimental-spec.txt for details. (http://domainkeys.sf.net)
26 TK/02 Fix ACL "control" statement not being available in MIME ACL.
28 TK/03 Fix ACL "regex" condition not being available in MIME ACL.
30 PH/01 Installed a patch from the Sieve maintainer that allows -bf to be used
31 to test Sieve filters that use "vacation".
33 PH/02 Installed a slightly modified version of Nikos Mavrogiannopoulos' patch
34 that changes the way the GnuTLS parameters are stored in the cache file.
35 The new format can be generated externally. For backward compatibility,
36 if the data in the cache doesn't make sense, Exim assumes it has read an
37 old-format file, and it generates new data and writes a new file. This
38 means that you can't go back to an older release without removing the
41 PH/03 A redirect router that has both "unseen" and "one_time" set does not
42 work if there are any delivery delays because "one_time" forces the
43 parent to be marked "delivered", so its unseen clone is never tried
44 again. For this reason, Exim now forbids the simultaneous setting of
47 PH/04 Change 4.11/85 fixed an obscure bug concerned with addresses that are
48 redirected to themselves ("homonym" addresses). Read the long ChangeLog
49 entry if you want to know the details. The fix, however, neglected to
50 consider the case when local delivery batching is involved. The test for
51 "previously delivered" was not happening when checking to see if an
52 address could be batched with a previous (undelivered) one; under
53 certain circumstances this could lead to multiple deliveries to the same
56 PH/05 Renamed the macro SOCKLEN_T as EXIM_SOCKLEN_T because AIX uses SOCKLEN_T
57 in its include files, and this causes problems building Exim.
59 PH/06 A number of "verify =" ACL conditions have no options (e.g. verify =
60 header_syntax) but Exim was just ignoring anything given after a slash.
61 In particular, this caused confusion with an attempt to use "verify =
62 reverse_host_lookup/defer_ok". An error is now given when options are
63 supplied for verify items that do not have them. (Maybe reverse_host_
64 lookup should have a defer_ok option, but that's a different point.)
66 PH/07 Increase the size of the buffer for incoming SMTP commands from 512 (as
67 defined by RFC 821) to 2048, because there were problems with some AUTH
68 commands, and RFC 1869 says the size should be increased for extended
69 SMTP commands that take arguments.
71 PH/08 Added ${dlfunc dynamically loaded function for expansion (code from Tony
74 PH/09 Previously, an attempt to use ${perl when it wasn't compiled gave an
75 "unknown" error; now it says that the functionality isn't in the binary.
77 PH/10 Added a nasty fudge to try to recognize and flatten LDAP passwords in
78 an address' error message when a string expansion fails (syntax or
79 whatever). Otherwise the password may appear in the log. Following change
80 PH/42 below, there is no longer a chance of it appearing in a bounce
83 PH/11 Installed exipick version 20050225.0 from John Jetmore.
85 PH/12 If the last host in a fallback_hosts list was multihomed, only the first
86 of its addresses was ever tried. (Bugzilla bug #2.)
88 PH/13 If "headers_add" in a transport didn't end in a newline, Exim printed
89 the result incorrectly in the debug output. (It correctly added a newline
90 to what was transported.)
92 TF/01 Added $received_time.
94 PH/14 Modified the default configuration to add an acl_smtp_data ACL, with
95 commented out examples of how to interface to a virus scanner and to
96 SpamAssassin. Also added commented examples of av_scanner and
97 spamd_address settings.
99 PH/15 Further to TK/02 and TK/03 above, tidied up the tables of what conditions
100 and controls are allowed in which ACLs. There were a couple of minor
101 errors. Some of the entries in the conditions table (which is a table of
102 where they are NOT allowed) were getting very unwieldy; rewrote them as a
103 negation of where the condition IS allowed.
105 PH/16 Installed updated OS/os.c-cygwin from the Cygwin maintainer.
107 PH/17 The API for radiusclient changed at release 0.4.0. Unfortunately, the
108 header file does not have a version number, so I've had to invent a new
109 value for RADIUS_LIB_TYPE, namely "RADIUSCLIENTNEW" to request the new
110 API. The code is untested by me (my Linux distribution still has 0.3.2 of
111 radiusclient), but it was contributed by a Radius user.
113 PH/18 Installed Lars Mainka's patch for the support of CRL collections in
114 files or directories, for OpenSSL.
116 PH/19 When an Exim process that is running as root has to create an Exim log
117 file, it does so in a subprocess that runs as exim:exim so as to get the
118 ownership right at creation (otherwise, other Exim processes might see
119 the file with the wrong ownership). There was no test for failure of this
120 fork() call, which would lead to the process getting stuck as it waited
121 for a non-existent subprocess. Forks do occasionally fail when resources
122 run out. I reviewed all the other calls to fork(); they all seem to check
125 PH/20 When checking for unexpected SMTP input at connect time (before writing
126 the banner), Exim was not dealing correctly with a non-positive return
127 from the read() function. If the client had disconnected by this time,
128 the result was a log entry for a synchronization error with an empty
129 string after "input=" when read() returned zero. If read() returned -1
130 (an event I could not check), uninitialized data bytes were printed.
131 There were reports of junk text (parts of files, etc) appearing after
134 PH/21 Added acl_not_smtp_mime to allow for MIME scanning for non-SMTP messages.
136 PH/22 Added support for macro redefinition, and (re)definition in between
137 driver and ACL definitions.
139 PH/23 The cyrus_sasl authenticator was expanding server_hostname, but then
140 forgetting to use the resulting value; it was using the unexpanded value.
142 PH/24 The cyrus_sasl authenticator was advertising mechanisms for which it
143 hadn't been configured. The fix is from Juergen Kreileder, who
144 understands it better than I do:
146 "Here's what I see happening with three configured cyrus_sasl
147 authenticators configured (plain, login, cram-md5):
149 On startup auth_cyrus_sasl_init() gets called for each of these.
150 This means three calls to sasl_listmech() without a specified mech_list.
151 => SASL tests which mechs of all available mechs actually work
152 => three warnings about OTP not working
153 => the returned list contains: plain, login, cram-md5, digest-md5, ...
155 With the patch, sasl_listmech() also gets called three times. But now
156 SASL's mech_list option is set to the server_mech specified in the the
157 authenticator. Or in other words, the answer from sasl_listmech()
158 gets limited to just the mech you're testing for (which is different
160 => the return list contains just 'plain' or 'login', 'cram-md5' or
161 nothing depending on the value of ob->server_mech.
163 I've just tested the patch: Authentication still works fine,
164 unavailable mechs specified in the exim configuration are still
165 caught, and the auth.log warnings about OTP are gone."
167 PH/25 When debugging is enabled, the contents of the command line are added
168 to the debugging output, even when log_selector=+arguments is not
171 PH/26 Change scripts/os-type so that when "uname -s" returns just "GNU", the
172 answer is "GNU", and only if the return is "GNU/something" is the answer
175 PH/27 $acl_verify_message is now set immediately after the failure of a
176 verification in an ACL, and so is available in subsequent modifiers. In
177 particular, the message can be preserved by coding like this:
179 warn !verify = sender
180 set acl_m0 = $acl_verify_message
182 Previously, $acl_verify_message was set only while expanding "message"
183 and "log_message" when a very denied access.
185 PH/28 Modified OS/os.c-Linux with
187 -#ifndef OS_LOAD_AVERAGE
188 +#if !defined(OS_LOAD_AVERAGE) && defined(__linux__)
190 to make Exim compile on kfreebsd-gnu. (I'm totally confused about the
191 nomenclature these days.)
193 PH/29 Installed patch from the Sieve maintainer that adds the options
194 sieve_useraddress and sieve_subaddress to the redirect router.
196 PH/30 In these circumstances:
197 . Two addresses routed to the same list of hosts;
198 . First host does not offer TLS;
199 . First host accepts first address;
200 . First host gives temporary error to second address;
201 . Second host offers TLS and a TLS session is established;
202 . Second host accepts second address.
203 Exim incorrectly logged both deliveries with the TLS parameters (cipher
204 and peerdn, if requested) that were in fact used only for the second
207 PH/31 When doing a callout as part of verifying an address, Exim was not paying
208 attention to any local part prefix or suffix that was matched by the
209 router that accepted the address. It now behaves in the same way as it
210 does for delivery: the affixes are removed from the local part unless
211 rcpt_include_affixes is set on the transport.
213 PH/32 Add the sender address, as F=<...>, to the log line when logging a
214 timeout during the DATA phase of an incoming message.
216 PH/33 Sieve envelope tests were broken for match types other than :is. I have
217 applied a patch sanctioned by the Sieve maintainer.
219 PH/34 Change 4.50/80 broke Exim in that it could no longer handle cases where
220 the uid or gid is negative. A case of a negative gid caused this to be
221 noticed. The fix allows for either to be negative.
223 PH/35 ACL_WHERE_MIME is now declared unconditionally, to avoid too much code
224 clutter, but the tables that are indexed by ACL_WHERE_xxx values had been
227 PH/36 The change PH/12 above was broken. Fixed it.
229 PH/37 Exim used to check for duplicate addresses in the middle of routing, on
230 the grounds that routing the same address twice would always produce the
231 same answer. This might have been true once, but it is certainly no
232 longer true now. Routing a child address may depend on the previous
233 routing that produced that child. Some complicated redirection strategies
234 went wrong when messages had multiple recipients, and made Exim's
235 behaviour dependent on the order in which the addresses were given.
237 I have moved the duplicate checking until after the routing is complete.
238 Exim scans the addresses that are assigned to local and remote
239 transports, and removes any duplicates. This means that more work will be
240 done, as duplicates will always all be routed, but duplicates are
241 presumably rare, so I don't expect this is of any significance.
243 For deliveries to pipes, files, and autoreplies, the duplicate checking
244 still happens during the routing process, since they are not going to be
247 PH/38 Installed a patch from Ian Freislich, with the agreement of Tom Kistner.
248 It corrects a timeout issue with spamd. This is Ian's comment: "The
249 background is that sometimes spamd either never reads data from a
250 connection it has accepted, or it never writes response data. The exiscan
251 spam.[ch] uses a 3600 second timeout on spamd socket reads, further, it
252 blindly assumes that writes won't block so it may never time out."
254 PH/39 Allow G after quota size as well as K and M.
256 PH/40 The value set for $authenticated_id in an authenticator may not contain
257 binary zeroes or newlines because the value is written to log lines and
258 to spool files. There was no check on this. Now the value is run through
259 the string_printing() function so that such characters are converted to
260 printable escape sequences.
262 PH/41 $message_linecount is a new variable that contains the total number of
263 lines in the message. Compare $body_linecount, which is the count for the
266 PH/42 Exim no longer gives details of delivery errors for specific addresses in
267 bounce and delay warning messages, except in certain special cases, which
270 (a) An SMTP error message from a remote host;
271 (b) A message specified in a :fail: redirection;
272 (c) A message specified in a "fail" command in a system filter;
273 (d) A message specified in a FAIL return from the queryprogram router;
274 (e) A message specified by the cannot_route_message router option.
276 In these cases only, Exim does include the error details in bounce and
277 warning messages. There are also a few cases where bland messages such
278 as "unrouteable address" or "local delivery error" are given.
280 PH/43 $value is now also set for the "else" part of a ${run expansion.
282 PH/44 Applied patch from the Sieve maintainer: "The vacation draft is still
283 being worked on, but at least Exim now implements the latest version to
286 PH/45 In a pipe transport, although a timeout while waiting for the pipe
287 process to complete was treated as a delivery failure, a timeout while
288 writing the message to the pipe was logged, but erroneously treated as a
289 successful delivery. Such timeouts include transport filter timeouts. For
290 consistency with the overall process timeout, these timeouts are now
291 treated as errors, giving rise to delivery failures by default. However,
292 there is now a new Boolean option for the pipe transport called
293 timeout_defer, which, if set TRUE, converts the failures into defers for
294 both kinds of timeout. A transport filter timeout is now identified in
297 PH/46 The "scripts/Configure-config.h" script calls "make" at one point. On
298 systems where "make" and "gmake" are different, calling "gmake" at top
299 level broke things. I've arranged for the value of $(MAKE) to be passed
300 from the Makefile to this script so that it can call the same version of
304 A note about Exim versions 4.44 and 4.50
305 ----------------------------------------
307 Exim 4.50 was meant to be the next release after 4.43. It contains a lot of
308 changes of various kinds. As a consequence, a big documentation update was
309 needed. This delayed the release for rather longer than seemed good, especially
310 in the light of a couple of (minor) security issues. Therefore, the changes
311 that fixed bugs were backported into 4.43, to create a 4.44 maintenance
312 release. So 4.44 and 4.50 are in effect two different branches that both start
315 I have left the 4.50 change log unchanged; it contains all the changes since
316 4.43. The change log for 4.44 is below; many of its items are identical to
317 those for 4.50. This seems to be the most sensible way to preserve the
318 historical information.
324 1. Minor wording change to the doc/README.SIEVE file.
326 2. Change 4.43/35 introduced a bug: if quota_filecount was set, the
327 computation of the current number of files was incorrect.
329 3. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
330 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
333 4. Give more explanation in the error message when the command for a transport
334 filter fails to execute.
336 5. There are several places where Exim runs a non-Exim command in a
337 subprocess. The SIGUSR1 signal should be disabled for these processes. This
338 was being done only for the command run by the queryprogram router. It is
339 now done for all such subprocesses. The other cases are: ${run, transport
340 filters, and the commands run by the lmtp and pipe transports.
342 6. Added CONFIGURE_GROUP build-time option.
344 7. Some older OS have a limit of 256 on the maximum number of file
345 descriptors. Exim was using setrlimit() to set 1000 as a large value
346 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
347 systems. I've change it so that if it can't get 1000, it tries for 256.
349 8. "control=submission" was allowed, but had no effect, in a DATA ACL. This
350 was an oversight, and furthermore, ever since the addition of extra
351 controls (e.g. 4.43/32), the checks on when to allow different forms of
352 "control" were broken. There should now be diagnostics for all cases when a
353 control that does not make sense is encountered.
355 9. Added the /retain_sender option to "control=submission".
357 10. $recipients is now available in the predata ACL (oversight).
359 11. Tidy the search cache before the fork to do a delivery from a message
360 received from the command line. Otherwise the child will trigger a lookup
361 failure and thereby defer the delivery if it tries to use (for example) a
362 cached ldap connection that the parent has called unbind on.
364 12. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
365 of $address_data from the recipient verification was clobbered by the
368 13. The value of address_data from a sender verification is now available in
369 $sender_address_data in subsequent conditions in the ACL statement.
371 14. Added forbid_sieve_filter and forbid_exim_filter to the redirect router.
373 15. Added a new option "connect=<time>" to callout options, to set a different
376 16. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
377 was its contents. (It was OK if the option was not defined at all.)
379 17. A "Completed" log line is now written for messages that are removed from
380 the spool by the -Mrm option.
382 18. New variables $sender_verify_failure and $recipient_verify_failure contain
383 information about exactly what failed.
385 19. Added -dd to debug only the daemon process.
387 20. Incorporated Michael Haardt's patch to ldap.c for improving the way it
388 handles timeouts, both on the server side and network timeouts. Renamed the
389 CONNECT parameter as NETTIMEOUT (but kept the old name for compatibility).
391 21. The rare case of EHLO->STARTTLS->HELO was setting the protocol to "smtp".
392 It is now set to "smtps".
394 22. $host_address is now set to the target address during the checking of
397 23. When checking ignore_target_hosts for an ipliteral router, no host name was
398 being passed; this would have caused $sender_host_name to have been used if
399 matching the list had actually called for a host name (not very likely,
400 since this list is usually IP addresses). A host name is now passed as
403 24. Changed the calls that set up the SIGCHLD handler in the daemon to use the
404 code that specifies a non-restarting handler (typically sigaction() in
405 modern systems) in an attempt to fix a rare and obscure crash bug.
407 25. Narrowed the window for a race in the daemon that could cause it to ignore
408 SIGCHLD signals. This is not a major problem, because they are used only to
409 wake it up if nothing else does.
411 26. A malformed maildirsize file could cause Exim to calculate negative values
412 for the mailbox size or file count. Odd effects could occur as a result.
413 The maildirsize information is now recalculated if the size or filecount
416 27. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
417 support for a long time. Removed HAVE_SYS_VFS_H.
419 28. Installed the latest version of exipick from John Jetmore.
421 29. In an address list, if the pattern was not a regular expression, an empty
422 subject address (from a bounce message) matched only if the pattern was an
423 empty string. Non-empty patterns were not even tested. This was the wrong
424 because it is perfectly reasonable to use an empty address as part of a
425 database query. An empty address is now tested by patterns that are
426 lookups. However, all the other forms of pattern expect the subject to
427 contain a local part and a domain, and therefore, for them, an empty
428 address still always fails if the pattern is not itself empty.
430 30. Exim went into a mad DNS loop when attempting to do a callout where the
431 host was specified on an smtp transport, and looking it up yielded more
434 31. Re-factored the code for checking spool and log partition space into a
435 function that finds that data and another that does the check. The former
436 is then used to implement four new variables: $spool_space, $log_space,
437 $spool_inodes, and $log_inodes.
439 32. The RFC2047 encoding function was originally intended for short strings
440 such as real names; it was not keeping to the 75-character limit for
441 encoded words that the RFC imposes. It now respects the limit, and
442 generates multiple encoded words if necessary. To be on the safe side, I
443 have increased the buffer size for the ${rfc2047: expansion operator from
446 33. It is now permitted to omit both strings after an "if" condition; if the
447 condition is true, the result is "true". As before, when the second string
448 is omitted, a false condition yields an empty string. This makes it less
449 cumbersome to write custom ACL and router conditions.
451 34. Failure to deliver a bounce message always caused it to be frozen, even if
452 there was an errors_to setting on the router. The errors_to setting is now
455 35. If an IPv6 address is given for -bh or -bhc, it is now converted to the
456 canonical form (fully expanded) before being placed in
457 $sender_host_address.
459 36. The table in the code that translates DNS record types into text (T_A to
460 "A" for instance) was missing entries for NS and CNAME. It is just possible
461 that this could have caused confusion if both these types were looked up
462 for the same domain, because the text type is used as part of Exim's
463 per-process caching. But the chance of anyone hitting this buglet seems
466 37. The dnsdb lookup has been extended in a number of ways.
468 (1) There is a new type, "zns", which walks up the domain tree until it
469 finds some nameserver records. It should be used with care.
471 (2) There is a new type, "mxh", which is like "mx" except that it returns
472 just the host names, not the priorities.
474 (3) It is now possible to give a list of domains (or IP addresses) to be
475 looked up. The behaviour when one of the lookups defers can be
476 controlled by a keyword.
478 (4) It is now possible to specify the separator character for use when
479 multiple records are returned.
481 38. The dnslists ACL condition has been extended: it is now possible to supply
482 a list of IP addresses and/or domains to be looked up in a particular DNS
485 39. Added log_selector=+queue_time_overall.
487 40. When running the queue in the test harness, wait just a tad after forking a
488 delivery process, to get repeatability of debugging output.
490 41. Include certificate and key file names in error message when GnuTLS fails
491 to set them up, because the GnuTLS error message doesn't include the name
492 of the failing file when there is a problem reading it.
494 42. Allow both -bf and -bF in the same test run.
496 43. Did the same fix as 41 above for OpenSSL, which had the same infelicity.
498 44. The "Exiscan patch" is now merged into the mainline Exim source.
500 45. Sometimes the final signoff response after QUIT could fail to get
501 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
502 < 0 before doing a fflush(). This bug looks as though it goes back to the
503 introduction of TLS in release 3.20, but "sometimes" must have been rare
504 because the tests only now provoked it.
506 46. Reset the locale to "C" after calling embedded Perl, in case it was changed
507 (this can affect the format of dates).
509 47. exim_tidydb, when checking for the continued existence of a message for
510 which it has found a message-specific retry record, was not finding
511 messages that were in split spool directories. Consequently, it was
512 deleting retry records that should have stayed in existence.
514 48. Steve fixed some bugs in eximstats.
516 49. The SPA authentication driver was not abandoning authentication and moving
517 on to the next authenticator when an expansion was forced to fail,
518 contradicting the general specification for all authenticators. Instead it
519 was generating a temporary error. It now behaves as specified.
521 50. The default ordering of permitted cipher suites for GnuTLS was pessimal
522 (the order specifies the preference for clients). The order is now AES256,
523 AES128, 3DES, ARCFOUR128.
525 51. Small patch to Sieve code - explicitly set From: when generating an
528 52. Exim crashed if a remote delivery caused a very long error message to be
529 recorded - for instance if somebody sent an entire SpamAssassin report back
530 as a large number of 550 error lines. This bug was coincidentally fixed by
531 increasing the size of one of Exim's internal buffers (big_buffer) that
532 happened as part of the Exiscan merge. However, to be on the safe side, I
533 have made the code more robust (and fixed the comments that describe what
536 53. Now that there can be additional text after "Completed" in log lines (if
537 the queue_time_overall log selector is set), a one-byte patch to exigrep
538 was needed to allow it to recognize "Completed" as not the last thing in
541 54. The LDAP lookup was not handling a return of LDAP_RES_SEARCH_REFERENCE. A
542 patch that reportedly fixes this has been added. I am not expert enough to
543 create a test for it. This is what the patch creator wrote:
545 "I found a little strange behaviour of ldap code when working with
546 Windows 2003 AD Domain, where users was placed in more than one
547 Organization Units. When I tried to give exim partial DN, the exit code
548 of ldap_search was unknown to exim because of LDAP_RES_SEARCH_REFERENCE.
549 But simultaneously result of request was absolutely normal ldap result,
550 so I produce this patch..."
552 Later: it seems that not all versions of LDAP support LDAP_RES_SEARCH_
553 REFERENCE, so I have modified the code to exclude the patch when that macro
556 55. Some experimental protocols are using DNS PTR records for new purposes. The
557 keys for these records are domain names, not reversed IP addresses. The
558 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
559 leaves it alone. Component reversal etc. now happens only for IP addresses.
562 56. Improve error message when ldap_search() fails in OpenLDAP or Solaris LDAP.
564 57. Double the size of the debug message buffer (to 2048) so that more of very
565 long debug lines gets shown.
567 58. The exicyclog utility now does better if the number of log files to keep
568 exceeds 99. In this case, it numbers them 001, 002 ... instead of 01, 02...
570 59. Two changes related to the smtp_active_hostname option:
572 (1) $smtp_active_hostname is now available as a variable.
573 (2) The default for smtp_banner uses $smtp_active_hostname instead
574 of $primary_hostname.
576 60. The host_aton() function is supposed to be passed a string that is known
577 to be a valid IP address. However, in the case of IPv6 addresses, it was
578 not checking this. This is a hostage to fortune. Exim now panics and dies
579 if the condition is not met. A case was found where this could be provoked
580 from a dnsdb PTR lookup with an IPv6 address that had more than 8
581 components; fortuitously, this particular loophole had already been fixed
582 by change 4.50/55 above.
584 If there are any other similar loopholes, the new check in host_aton()
585 itself should stop them being exploited. The report I received stated that
586 data on the command line could provoke the exploit when Exim was running as
587 exim, but did not say which command line option was involved. All I could
588 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
592 61. There was a buffer overflow vulnerability in the SPA authentication code
593 (which came originally from the Samba project). I have added a test to the
594 spa_base64_to_bits() function which I hope fixes it.
597 62. Configuration update for GNU/Hurd and variations. Updated Makefile-GNU and
598 os.h-GNU, and added configuration files for GNUkFreeBSD and GNUkNetBSD.
600 63. The daemon start-up calls getloadavg() while still root for those OS that
601 need the first call to be done as root, but it missed one case: when
602 deliver_queue_load_max is set with deliver_drop_privilege. This is
603 necessary for the benefit of the queue runner, because there is no re-exec
604 when deliver_drop_privilege is set.
606 64. A call to exiwhat cut short delays set up by "delay" modifiers in ACLs.
609 65. Caching of lookup data for "hosts =" ACL conditions, when a named host list
610 was in use, was not putting the data itself into the right store pool;
611 consequently, it could be overwritten for a subsequent message in the same
612 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
615 66. Added hosts_max_try_hardlimit to the smtp transport, default 50.
617 67. The string_is_ip_address() function returns 0, 4, or 6, for "no an IP
618 address", "IPv4 address", and "IPv6 address", respectively. Some calls of
619 the function were treating the return as a boolean value, which happened to
620 work because 0=false and not-0=true, but is not correct code.
622 68. The host_aton() function was not handling scoped IPv6 addresses (those
623 with, for example, "%eth0" on the end) correctly.
625 69. Fixed some compiler warnings in acl.c for the bitmaps specified with
626 negated items (that is, ~something) in unsigned ints. Some compilers
627 apparently mutter when there is no cast.
629 70. If an address verification called from an ACL failed, and did not produce a
630 user-specific message (i.e. there was only a "system" message), nothing was
631 put in $acl_verify_message. In this situation, it now puts the system
634 71. Change 4.23/11 added synchronization checking at the start of an SMTP
635 session; change 4.31/43 added the unwanted input to the log line - except
636 that it did not do this in the start of session case. It now does.
638 72. After a timeout in a callout SMTP session, Exim still sent a QUIT command.
639 This is wrong and can cause the other end to generate a synchronization
640 error if it is another Exim or anything else that does the synchronization
641 check. A QUIT command is no longer sent after a timeout.
643 73. $host_lookup_deferred has been added, to make it easier to detect DEFERs
646 74. The defer_ok option of callout verification was not working if it was used
647 when verifying addresses in header lines, that is, for this case:
649 verify = header_sender/callout=defer_ok
651 75. A backgrounded daemon closed stdin/stdout/stderr on entry; this meant that
652 those file descriptors could be used for SMTP connections. If anything
653 wrote to stderr (the example that came up was "warn" in embedded Perl), it
654 could be sent to the SMTP client, causing chaos. The daemon now opens
655 stdin, stdout, and stderr to /dev/null when it puts itself into the
658 76. Arrange for output from Perl's "warn" command to be written to Exim's main
659 log by default. The user can override this with suitable Perl magic.
661 77. The use of log_message on a "discard" ACL verb, which is supposed to add to
662 the log message when discard triggers, was not working for the DATA ACL or
663 for the non-SMTP ACL.
665 78. Error message wording change in sieve.c.
667 79. If smtp_accept_max_per_host was set, the number of connections could be
668 restricted to fewer than expected, because the daemon was trying to set up
669 a new connection before checking whether the processes handling previous
670 connections had finished. The check for completed processes is now done
671 earlier. On busy systems, this bug wouldn't be noticed because something
672 else would have woken the daemon, and it would have reaped the completed
675 80. If a message was submitted locally by a user whose login name contained one
676 or more spaces (ugh!), the spool file that Exim wrote was not re-readable.
677 It caused a spool format error. I have fixed the spool reading code. A
678 related problem was that the "from" clause in the Received: line became
679 illegal because of the space(s). It is now covered by ${quote_local_part.
681 81. Included the latest eximstats from Steve (adds average sizes to HTML Top
684 82. Updated OS/Makefile-AIX as per message from Mike Meredith.
686 83. Patch from Sieve maintainer to fix unterminated string problem in
689 84. Some minor changes to the Linux configuration files to help with other
690 OS variants using glibc.
692 85. One more patch for Sieve to update vacation handling to latest spec.
695 ----------------------------------------------------
696 See the note above about the 4.44 and 4.50 releases.
697 ----------------------------------------------------
703 1. Change 4.43/35 introduced a bug that caused file counts to be
704 incorrectly computed when quota_filecount was set in an appendfile
707 2. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
708 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
711 3. Give more explanation in the error message when the command for a transport
712 filter fails to execute.
714 4. There are several places where Exim runs a non-Exim command in a
715 subprocess. The SIGUSR1 signal should be disabled for these processes. This
716 was being done only for the command run by the queryprogram router. It is
717 now done for all such subprocesses. The other cases are: ${run, transport
718 filters, and the commands run by the lmtp and pipe transports.
720 5. Some older OS have a limit of 256 on the maximum number of file
721 descriptors. Exim was using setrlimit() to set 1000 as a large value
722 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
723 systems. I've change it so that if it can't get 1000, it tries for 256.
725 6. "control=submission" was allowed, but had no effect, in a DATA ACL. This
726 was an oversight, and furthermore, ever since the addition of extra
727 controls (e.g. 4.43/32), the checks on when to allow different forms of
728 "control" were broken. There should now be diagnostics for all cases when a
729 control that does not make sense is encountered.
731 7. $recipients is now available in the predata ACL (oversight).
733 8. Tidy the search cache before the fork to do a delivery from a message
734 received from the command line. Otherwise the child will trigger a lookup
735 failure and thereby defer the delivery if it tries to use (for example) a
736 cached ldap connection that the parent has called unbind on.
738 9. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
739 of $address_data from the recipient verification was clobbered by the
742 10. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
743 was its contents. (It was OK if the option was not defined at all.)
745 11. A "Completed" log line is now written for messages that are removed from
746 the spool by the -Mrm option.
748 12. $host_address is now set to the target address during the checking of
751 13. When checking ignore_target_hosts for an ipliteral router, no host name was
752 being passed; this would have caused $sender_host_name to have been used if
753 matching the list had actually called for a host name (not very likely,
754 since this list is usually IP addresses). A host name is now passed as
757 14. Changed the calls that set up the SIGCHLD handler in the daemon to use the
758 code that specifies a non-restarting handler (typically sigaction() in
759 modern systems) in an attempt to fix a rare and obscure crash bug.
761 15. Narrowed the window for a race in the daemon that could cause it to ignore
762 SIGCHLD signals. This is not a major problem, because they are used only to
763 wake it up if nothing else does.
765 16. A malformed maildirsize file could cause Exim to calculate negative values
766 for the mailbox size or file count. Odd effects could occur as a result.
767 The maildirsize information is now recalculated if the size or filecount
770 17. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
771 support for a long time. Removed HAVE_SYS_VFS_H.
773 18. Updated exipick to current release from John Jetmore.
775 19. Allow an empty sender to be matched against a lookup in an address list.
776 Previously the only cases considered were a regular expression, or an
779 20. Exim went into a mad DNS lookup loop when doing a callout where the
780 host was specified on the transport, if the DNS lookup yielded more than
783 21. The RFC2047 encoding function was originally intended for short strings
784 such as real names; it was not keeping to the 75-character limit for
785 encoded words that the RFC imposes. It now respects the limit, and
786 generates multiple encoded words if necessary. To be on the safe side, I
787 have increased the buffer size for the ${rfc2047: expansion operator from
790 22. Failure to deliver a bounce message always caused it to be frozen, even if
791 there was an errors_to setting on the router. The errors_to setting is now
794 23. If an IPv6 address is given for -bh or -bhc, it is now converted to the
795 canonical form (fully expanded) before being placed in
796 $sender_host_address.
798 24. Updated eximstats to version 1.33
800 25. Include certificate and key file names in error message when GnuTLS fails
801 to set them up, because the GnuTLS error message doesn't include the name
802 of the failing file when there is a problem reading it.
804 26. Expand error message when OpenSSL has problems setting up cert/key files.
807 27. Reset the locale to "C" after calling embedded Perl, in case it was changed
808 (this can affect the format of dates).
810 28. exim_tidydb, when checking for the continued existence of a message for
811 which it has found a message-specific retry record, was not finding
812 messages that were in split spool directories. Consequently, it was
813 deleting retry records that should have stayed in existence.
815 29. eximstats updated to version 1.35
816 1.34 - allow eximstats to parse syslog lines as well as mainlog lines
817 1.35 - bugfix such that pie charts by volume are generated correctly
819 30. The SPA authentication driver was not abandoning authentication and moving
820 on to the next authenticator when an expansion was forced to fail,
821 contradicting the general specification for all authenticators. Instead it
822 was generating a temporary error. It now behaves as specified.
824 31. The default ordering of permitted cipher suites for GnuTLS was pessimal
825 (the order specifies the preference for clients). The order is now AES256,
826 AES128, 3DES, ARCFOUR128.
828 31. Small patch to Sieve code - explicitly set From: when generating an
831 32. Exim crashed if a remote delivery caused a very long error message to be
832 recorded - for instance if somebody sent an entire SpamAssassin report back
833 as a large number of 550 error lines. This bug was coincidentally fixed by
834 increasing the size of one of Exim's internal buffers (big_buffer) that
835 happened as part of the Exiscan merge. However, to be on the safe side, I
836 have made the code more robust (and fixed the comments that describe what
839 33. Some experimental protocols are using DNS PTR records for new purposes. The
840 keys for these records are domain names, not reversed IP addresses. The
841 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
842 leaves it alone. Component reversal etc. now happens only for IP addresses.
845 34. The host_aton() function is supposed to be passed a string that is known
846 to be a valid IP address. However, in the case of IPv6 addresses, it was
847 not checking this. This is a hostage to fortune. Exim now panics and dies
848 if the condition is not met. A case was found where this could be provoked
849 from a dnsdb PTR lookup with an IPv6 address that had more than 8
850 components; fortuitously, this particular loophole had already been fixed
851 by change 4.50/55 or 4.44/33 above.
853 If there are any other similar loopholes, the new check in host_aton()
854 itself should stop them being exploited. The report I received stated that
855 data on the command line could provoke the exploit when Exim was running as
856 exim, but did not say which command line option was involved. All I could
857 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
861 35. There was a buffer overflow vulnerability in the SPA authentication code
862 (which came originally from the Samba project). I have added a test to the
863 spa_base64_to_bits() function which I hope fixes it.
866 36. The daemon start-up calls getloadavg() while still root for those OS that
867 need the first call to be done as root, but it missed one case: when
868 deliver_queue_load_max is set with deliver_drop_privilege. This is
869 necessary for the benefit of the queue runner, because there is no re-exec
870 when deliver_drop_privilege is set.
872 37. Caching of lookup data for "hosts =" ACL conditions, when a named host list
873 was in use, was not putting the data itself into the right store pool;
874 consequently, it could be overwritten for a subsequent message in the same
875 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
878 38. Sometimes the final signoff response after QUIT could fail to get
879 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
880 < 0 before doing a fflush(). This bug looks as though it goes back to the
881 introduction of TLS in release 3.20, but "sometimes" must have been rare
882 because the tests only now provoked it.
888 1. Fixed a longstanding but relatively impotent bug: a long time ago, before
889 PIPELINING, the function smtp_write_command() used to return TRUE or FALSE.
890 Now it returns an integer. A number of calls were still expecting a T/F
891 return. Fortuitously, in all cases, the tests worked in OK situations,
892 which is the norm. However, things would have gone wrong on any write
893 failures on the smtp file descriptor. This function is used when sending
894 messages over SMTP and also when doing verify callouts.
896 2. When Exim is called to do synchronous delivery of a locally submitted
897 message (the -odf or -odi options), it no longer closes stderr before doing
900 3. Implemented the mua_wrapper option.
902 4. Implemented mx_fail_domains and srv_fail_domains for the dnslookup router.
904 5. Implemented the functions header_remove(), header_testname(),
905 header_add_at_position(), and receive_remove_recipient(), and exported them
908 6. If an ACL "warn" statement specified the addition of headers, Exim already
909 inserted X-ACL-Warn: at the start if there was no header name. However, it
910 was not making this test for the second and subsequent header lines if
911 there were newlines in the string. This meant that an invalid header could
912 be inserted if Exim was badly configured.
914 7. Allow an ACL "warn" statement to add header lines at the start or after all
915 the Received: headers, as well as at the end.
917 8. Added the rcpt_4xx retry error code.
919 9. Added postmaster_mailfrom=xxx to callout verification option.
921 10. Added mailfrom=xxxx to the callout verification option, for verify=
924 11. ${substr_1_:xxxx} and ${substr__3:xxxx} are now diagnosed as syntax errors
925 (they previously behaved as ${substr_1_0:xxxx} and ${substr:_0_3:xxxx}).
927 12. Inserted some casts to stop certain compilers warning when using pointer
928 differences as field lengths or precisions in printf-type calls (mostly
929 affecting debugging statements).
931 13. Added optional readline() support for -be (dynamically loaded).
933 14. Obscure bug fix: if a message error (e.g. 4xx to MAIL) happened within the
934 same clock tick as a message's arrival, so that its received time was the
935 same as the "first fail" time on the retry record, and that message
936 remained on the queue past the ultimate address timeout, every queue runner
937 would try a delivery (because it was past the ultimate address timeout) but
938 after another failure, the ultimate address timeout, which should have then
939 bounced the address, did not kick in. This was a "< instead of <=" error;
940 in most cases the first failure would have been in the next clock tick
941 after the received time, and all would be well.
943 15. The special items beginning with @ in domain lists (e.g. @mx_any) were not
944 being recognized when the domain list was tested by the match_domain
945 condition in an expansion string.
947 16. Added the ${str2b64: operator.
949 17. Exim was always calling setrlimit() to set a large limit for the number of
950 processes, without checking whether the existing limit was already
951 adequate. (It did check for the limit on file descriptors.) Furthermore,
952 errors from getrlimit() and setrlimit() were being ignored. Now they are
953 logged to the main and panic logs, but Exim does carry on, to try to do its
954 job under whatever limits there are.
956 18. Imported PCRE 5.0.
958 19. Trivial typo in log message " temporarily refused connection" (the leading
961 20. If the log selector return_path_on_delivery was set and an address was
962 redirected to /dev/null, the delivery process crashed because it assumed
963 that a return path would always be set for a "successful" delivery. In this
964 case, the whole delivery is bypassed as an optimization, and therefore no
967 21. Internal re-arrangement: the function for sending a challenge and reading
968 a response while authentication was assuming a zero-terminated challenge
969 string. It's now changed to take a pointer and a length, to allow for
970 binary data in such strings.
972 22. Added the cyrus_sasl authenticator (code supplied by MBM).
974 23. Exim was not respecting finduser_retries when seeking the login of the
975 uid under which it was called; it was always trying 10 times. (The default
976 setting of finduser_retries is zero.) Also, it was sleeping after the final
977 failure, which is pointless.
979 24. Implemented tls_on_connect_ports.
981 25. Implemented acl_smtp_predata.
983 26. If the domain in control=submission is set empty, Exim assumes that the
984 authenticated id is a complete email address when it generates From: or
985 Sender: header lines.
987 27. Added "#define SOCKLEN_T int" to OS/os.h-SCO and OS/os.h-SCO_SV. Also added
988 definitions to OS/Makefile-SCO and OS/Makefile-SCO_SV that put basename,
989 chown and chgrp in /bin and hostname in /usr/bin.
991 28. Exim was keeping the "process log" file open after each use, just as it
992 does for the main log. This opens the possibility of it remaining open for
993 long periods when the USR1 signal hits a daemon. Occasional processlog
994 errors were reported, that could have been caused by this. Anyway, it seems
995 much more sensible not to leave this file open at all, so that is what now
998 29. The long-running daemon process does not normally write to the log once it
999 has entered its main loop, and it closes the log before doing so. This is
1000 so that log files can straightforwardly be renamed and moved. However,
1001 there are a couple of unusual error situations where the daemon does write
1002 log entries, and I had neglected to close the log afterwards.
1004 30. The text of an SMTP error response that was received during a remote
1005 delivery was being truncated at 512 bytes. This is too short for some of
1006 the long messages that one sometimes sees. I've increased the limit to
1009 31. It is now possible to make retry rules that apply only when a message has a
1010 specific sender, in particular, an empty sender.
1012 32. Added "control = enforce_sync" and "control = no_enforce_sync". This makes
1013 it possible to be selective about when SMTP synchronization is enforced.
1015 33. Added "control = caseful_local_part" and "control = "caselower_local_part".
1017 32. Implemented hosts_connection_nolog.
1019 33. Added an ACL for QUIT.
1021 34. Setting "delay_warning=" to disable warnings was not working; it gave a
1024 35. Added mailbox_size and mailbox_filecount to appendfile.
1026 36. Added control = no_multiline_responses to ACLs.
1028 37. There was a bug in the logic of the code that waits for the clock to tick
1029 in the case where the clock went backwards by a substantial amount such
1030 that the microsecond fraction of "now" was more than the microsecond
1031 fraction of "then" (but the whole seconds number was less).
1033 38. Added support for the libradius Radius client library this is found on
1034 FreeBSD (previously only the radiusclient library was supported).
1040 1. When certain lookups returned multiple values in the form name=value, the
1041 quoting of the values was not always being done properly. Specifically:
1042 (a) If the value started with a double quote, but contained no whitespace,
1044 (b) If the value contained whitespace other than a space character (i.e.
1045 tabs or newlines or carriage returns) it was not quoted.
1046 This fix has been applied to the mysql and pgsql lookups by writing a
1047 separate quoting function and calling it from the lookup code. The fix
1048 should probably also be applied to nisplus, ibase and oracle lookups, but
1049 since I cannot test any of those, I have not disturbed their existing code.
1051 2. A hit in the callout cache for a specific address caused a log line with no
1052 reason for rejecting RCPT. Now it says "Previous (cached) callout
1053 verification failure".
1055 3. There was an off-by-one bug in the queryprogram router. An over-long
1056 return line was truncated at 256 instead of 255 characters, thereby
1057 overflowing its buffer with the terminating zero. As well as fixing this, I
1058 have increased the buffer size to 1024 (and made a note to document this).
1060 4. If an interrupt, such as the USR1 signal that is send by exiwhat, arrives
1061 when Exim is waiting for an SMTP response from a remote server, Exim
1062 restarts its select() call on the socket, thereby resetting its timeout.
1063 This is not a problem when such interrupts are rare. Somebody set up a cron
1064 job to run exiwhat every 2 minutes, which is less than the normal select()
1065 timeout (5 or 10 minutes). This meant that the select() timeout never
1066 kicked in because it was always reset. I have fixed this by comparing the
1067 time when an interrupt arrives with the time at the start of the first call
1068 to select(). If more time than the timeout has elapsed, the interrupt is
1069 treated as a timeout.
1071 5. Some internal re-factoring in preparation for the addition of Sieve
1072 extensions (by MH). In particular, the "personal" test is moved to a
1073 separate function, and given an option for scanning Cc: and Bcc: (which is
1074 not set for Exim filters).
1076 6. When Exim created an email address using the login of the caller as the
1077 local part (e.g. when creating a From: or Sender: header line), it was not
1078 quoting the local part when it contained special characters such as @.
1080 7. Installed new OpenBSD configuration files.
1082 8. Reworded some messages for syntax errors in "and" and "or" conditions to
1083 try to make them clearer.
1085 9. Callout options, other than the timeout value, were being ignored when
1086 verifying sender addresses in header lines. For example, when using
1088 verify = header_sender/callout=no_cache
1090 the cache was (incorrectly) being used.
1092 10. Added a missing instance of ${EXE} to the exim_install script; this affects
1093 only the Cygwin environment.
1095 11. When return_path_on_delivery was set as a log selector, if different remote
1096 addresses in the same message used different return paths and parallel
1097 remote delivery occurred, the wrong values would sometimes be logged.
1098 (Whenever a remote delivery process finished, the return path value from
1099 the most recently started remote delivery process was logged.)
1101 12. RFC 3848 specifies standard names for the "with" phrase in Received: header
1102 lines when AUTH and/or TLS are in use. This is the "received protocol"
1103 field. Exim used to use "asmtp" for authenticated SMTP, without any
1104 indication (in the protocol name) for TLS use. Now it follows the RFC and
1105 uses "esmtpa" if the connection is authenticated, "esmtps" if it is
1106 encrypted, and "esmtpsa" if it is both encrypted and authenticated. These
1107 names appear in log lines as well as in Received: header lines.
1109 13. Installed MH's patches for Sieve to add the "copy" and "vacation"
1110 extensions, and comparison tests, and to fix some bugs.
1112 14. Changes to the "personal" filter test:
1114 (1) The test was buggy in that it was just doing the equivalent of
1115 "contains" tests on header lines. For example, if a user's address was
1116 anne@some.where, the "personal" test would incorrectly be true for
1118 To: susanne@some.where
1120 This test is now done by extracting each address from the header in turn,
1121 and checking the entire address. Other tests that are part of "personal"
1122 are now done using regular expressions (for example, to check local parts
1123 of addresses in From: header lines).
1125 (2) The list of non-personal local parts in From: addresses has been
1126 extended to include "listserv", "majordomo", "*-request", and "owner-*",
1127 taken from the Sieve specification recommendations.
1129 (3) If the message contains any header line starting with "List-" it is
1130 treated as non-personal.
1132 (4) The test for "circular" in the Subject: header line has been removed
1133 because it now seems ill-conceived.
1135 15. Minor typos in src/EDITME comments corrected.
1137 16. Installed latest exipick from John Jetmore.
1139 17. If headers_add on a router specified a text string that was too long for
1140 string_sprintf() - that is, longer than 8192 bytes - Exim panicked. The use
1141 of string_sprintf() is now avoided.
1143 18. $message_body_size was not set (it was always zero) when running the DATA
1144 ACL and the local_scan() function.
1146 19. For the "mail" command in an Exim filter, no default was being set for
1147 the once_repeat time, causing a random time value to be used if "once" was
1148 specified. (If the value happened to be <= 0, no repeat happened.) The
1149 default is now 0s, meaning "never repeat". The "vacation" command was OK
1150 (its default is 7d). It's somewhat surprising nobody ever noticed this bug
1151 (I found it when inspecting the code).
1153 20. There is now an overall timeout for performing a callout verification. It
1154 defaults to 4 times the callout timeout, which applies to individual SMTP
1155 commands during the callout. The overall timeout applies when there is more
1156 than one host that can be tried. The timeout is checked before trying the
1157 next host. This prevents very long delays if there are a large number of
1158 hosts and all are timing out (e.g. when the network connections are timing
1159 out). The value of the overall timeout can be changed by specifying an
1160 additional sub-option for "callout", called "maxwait". For example:
1162 verify = sender/callout=5s,maxwait=20s
1164 21. Add O_APPEND to the open() call for maildirsize files (Exim already seeks
1165 to the end before writing, but this should make it even safer).
1167 22. Exim was forgetting that it had advertised PIPELINING for the second and
1168 subsequent messages on an SMTP connection. It was also not resetting its
1169 memory on STARTTLS and an internal HELO.
1171 23. When Exim logs an SMTP synchronization error within a session, it now
1172 records whether PIPELINING has been advertised or not.
1174 24. Added 3 instances of "(long int)" casts to time_t variables that were being
1175 formatted using %ld, because on OpenBSD (and perhaps others), time_t is int
1176 rather than long int.
1178 25. Installed the latest Cygwin configuration files from the Cygwin maintainer.
1180 26. Added the never_mail option to autoreply.
1186 1. A reorganization of the code in order to implement 4.40/8 caused a daemon
1187 crash if the getsockname() call failed; this can happen if a connection is
1188 closed very soon after it is established. The problem was simply in the
1189 order in which certain operations were done, causing Exim to try to write
1190 to the SMTP stream before it had set up the file descriptor. The bug has
1191 been fixed by making things happen in the correct order.
1197 1. If "drop" was used in a DATA ACL, the SMTP output buffer was not flushed
1198 before the connection was closed, thus losing the rejection response.
1200 2. Commented out the definition of SOCKLEN_T in os.h-SunOS5. It is needed for
1201 some early Solaris releases, but causes trouble in current releases where
1202 socklen_t is defined.
1204 3. When std{in,out,err} are closed, re-open them to /dev/null so that they
1207 4. Minor refactoring of os.c-Linux to avoid compiler warning when IPv6 is not
1210 5. Refactoring in expand.c to improve memory usage. Pre-allocate a block so
1211 that releasing the top of it at the end releases what was used for sub-
1212 expansions (unless the block got too big). However, discard this block if
1213 the first thing is a variable or header, so that we can use its block when
1214 it is dynamic (useful for very large $message_headers, for example).
1216 6. Lookups now cache *every* query, not just the most recent. A new, separate
1217 store pool is used for this. It can be recovered when all lookup caches are
1218 flushed. Lookups now release memory at the end of their result strings.
1219 This has involved some general refactoring of the lookup sources.
1221 7. Some code has been added to the store_xxx() functions to reduce the amount
1222 of flapping under certain conditions.
1224 8. log_incoming_interface used to affect only the <= reception log lines. Now
1225 it causes the local interface and port to be added to several more SMTP log
1226 lines, for example "SMTP connection from", and rejection lines.
1228 9. The Sieve author supplied some patches for the doc/README.SIEVE file.
1230 10. Added a conditional definition of _BSD_SOCKLEN_T to os.h-Darwin.
1232 11. If $host_data was set by virtue of a hosts lookup in an ACL, its value
1233 could be overwritten at the end of the current message (or the start of a
1234 new message if it was set in a HELO ACL). The value is now preserved for
1235 the duration of the SMTP connection.
1237 12. If a transport had a headers_rewrite setting, and a matching header line
1238 contained an unqualified address, that address was qualified, even if it
1239 did not match any rewriting rules. The underlying bug was that the values
1240 of the flags that permit the existence of unqualified sender and recipient
1241 addresses in header lines (set by {sender,recipient}_unqualified_hosts for
1242 non-local messages, and by -bnq for local messages) were not being
1243 preserved with the message after it was received.
1245 13. When Exim was logging an SMTP synchronization error, it could sometimes log
1246 "next input=" as part of the text comprising the host identity instead of
1247 the correct text. The code was using the same buffer for two different
1248 strings. However, depending on which order the printing function evaluated
1249 its arguments, the bug did not always show up. Under Linux, for example, my
1250 test suite worked just fine.
1252 14. Exigrep contained a use of Perl's "our" scoping after change 4.31/70. This
1253 doesn't work with some older versions of Perl. It has been changed to "my",
1254 which in any case is probably the better facility to use.
1256 15. A really picky compiler found some instances of statements for creating
1257 error messages that either had too many or two few arguments for the format
1260 16. The size of the buffer for calls to the DNS resolver has been increased
1261 from 1024 to 2048. A larger buffer is needed when performing PTR lookups
1262 for addresses that have a lot of PTR records. This alleviates a problem; it
1263 does not fully solve it.
1265 17. A dnsdb lookup for PTR records that receives more data than will fit in the
1266 buffer now truncates the list and logs the incident, which is the same
1267 action as happens when Exim is looking up a host name and its aliases.
1268 Previously in this situation something unpredictable would happen;
1269 sometimes it was "internal error: store_reset failed".
1271 18. If a server dropped the connection unexpectedly when an Exim client was
1272 using GnuTLS and trying to read a response, the client delivery process
1273 crashed while trying to generate an error log message.
1275 19. If a "warn" verb in an ACL added multiple headers to a message in a single
1276 string, for example:
1278 warn message = H1: something\nH2: something
1280 the text was added as a single header line from Exim's point of view
1281 though it ended up OK in the delivered message. However, searching for the
1282 second and subsequent header lines using $h_h2: did not work. This has been
1283 fixed. Similarly, if a system filter added multiple headers in this way,
1284 the routers could not see them.
1286 20. Expanded the error message when iplsearch is called with an invalid key to
1287 suggest using net-iplsearch in a host list.
1289 21. When running tests using -bh, any delays imposed by "delay" modifiers in
1290 ACLs are no longer actually imposed (and a message to that effect is
1293 22. If a "gecos" field in a passwd entry contained escaped characters, in
1294 particular, if it contained a \" sequence, Exim got it wrong when building
1295 a From: or a Sender: header from that name. A second bug also caused
1296 incorrect handling when an unquoted " was present following a character
1297 that needed quoting.
1299 23. "{crypt}" as a password encryption mechanism for a "crypteq" expansion item
1300 was not being matched caselessly.
1302 24. Arranged for all hyphens in the exim.8 source to be escaped with
1305 25. Change 16 of 4.32, which reversed 71 or 4.31 didn't quite do the job
1306 properly. Recipient callout cache records were still being keyed to include
1307 the sender, even when use_sender was set false. This led to far more
1308 callouts that were necessary. The sender is no longer included in the key
1309 when use_sender is false.
1311 26. Added "control = submission" modifier to ACLs.
1313 27. Added the ${base62d: operator to decode base 62 numbers.
1315 28. dnsdb lookups can now access SRV records.
1317 29. CONFIGURE_OWNER can be set at build time to define an alternative owner for
1318 the configuration file.
1320 30. The debug message "delivering xxxxxx-xxxxxx-xx" is now output in verbose
1321 (-v) mode. This makes the output for a verbose queue run more intelligible.
1323 31. Added a use_postmaster feature to recipient callouts.
1325 32. Added the $body_zerocount variable, containing the number of binary zero
1326 bytes in the message body.
1328 33. The time of last modification of the "new" subdirectory is now used as the
1329 "mailbox time last read" when there is a quota error for a maildir
1332 34. Added string comparison operators lt, lti, le, lei, gt, gti, ge, gei.
1334 35. Added +ignore_unknown as a special item in host lists.
1336 36. Code for decoding IPv6 addresses in host lists is now included, even if
1337 IPv6 support is not being compiled. This fixes a bug in which an IPv6
1338 address was recognized as an IP address, but was then not correctly decoded
1339 into binary, causing unexpected and incorrect effects when compared with
1346 1. Very minor rewording of debugging text in manualroute to say "list of
1347 hosts" instead of "hostlist".
1349 2. If verify=header_syntax was set, and a header line with an unqualified
1350 address (no domain) and a large number of spaces between the end of the
1351 name and the colon was received, the reception process suffered a buffer
1352 overflow, and (when I tested it) crashed. This was caused by some obsolete
1353 code that should have been removed. The fix is to remove it!
1355 3. When running in the test harness, delay a bit after writing a bounce
1356 message to get a bit more predictability in the log output.
1358 4. Added a call to search_tidyup() just before forking a reception process. In
1359 theory, someone could use a lookup in the expansion of smtp_accept_max_
1360 per_host which, without the tidyup, could leave open a database connection.
1362 5. Added the variables $recipient_data and $sender_data which get set from a
1363 lookup success in an ACL "recipients" or "senders" condition, or a router
1364 "senders" option, similar to $domain_data and $local_part_data.
1366 6. Moved the writing of debug_print from before to after the "senders" test
1369 7. Change 4.31/66 (moving the time when the Received: is generated) caused
1370 problems for message scanning, either using a data ACL, or using
1371 local_scan() because the Received: header was not generated till after they
1372 were called (in order to set the time as the time of reception completion).
1373 I have revised the way this works. The header is now generated after the
1374 body is received, but before the ACL or local_scan() are called. After they
1375 are run, the timestamp in the header is updated.
1381 1. Change 4.24/6 introduced a bug because the SIGALRM handler was disabled
1382 before starting a queue runner without re-exec. This happened only when
1383 deliver_drop_privilege was set or when the Exim user was set to root. The
1384 effect of the bug was that timeouts during subsequent deliveries caused
1385 crashes instead of being properly handled. The handler is now left at its
1386 default (and expected) setting.
1388 2. The other case in which a daemon avoids a re-exec is to deliver an incoming
1389 message, again when deliver_drop_privilege is set or Exim is run as root.
1390 The bug described in (1) was not present in this case, but the tidying up
1391 of the other signals was missing. I have made the two cases consistent.
1393 3. The ignore_target_hosts setting on a manualroute router was being ignored
1394 for hosts that were looked up using the /MX notation.
1396 4. Added /ignore=<ip list> feature to @mx_any, @mx_primary, and @mx_secondary
1399 5. Change 4.31/55 was buggy, and broke when there was a rewriting rule that
1400 operated on the sender address. After changing the $sender_address to <>
1401 for the sender address verify, Exim was re-instated it as the original
1402 (before rewriting) address, but remembering that it had rewritten it, so it
1403 wasn't rewriting it again. This bug also had the effect of breaking the
1404 sender address verification caching when the sender address was rewritten.
1406 6. The ignore_target_hosts option was being ignored by the ipliteral router.
1407 This has been changed so that if the ip literal address matches
1408 ignore_target_hosts, the router declines.
1410 7. Added expansion conditions match_domain, match_address, and match_local_
1411 part (NOT match_host).
1413 8. The placeholder for the Received: header didn't have a length field set.
1415 9. Added code to Exim itself and to exim_lock to test for a specific race
1416 condition that could lead to file corruption when using MBX delivery. The
1417 issue is with the lockfile that is created in /tmp. If this file is removed
1418 after a process has opened it but before that process has acquired a lock,
1419 there is the potential for a second process to recreate the file and also
1420 acquire a lock. This could lead to two Exim processes writing to the file
1421 at the same time. The added code performs the same test as UW imapd; it
1422 checks after acquiring the lock that its file descriptor still refers to
1423 the same named file.
1425 10. The buffer for building added header lines was of fixed size, 8192 bytes.
1426 It is now parameterized by HEADER_ADD_BUFFER_SIZE and this can be adjusted
1429 11. Added the smtp_active_hostname option. If used, this will typically be made
1430 to depend on the incoming interface address. Because $interface_address is
1431 not set up until the daemon has forked a reception process, error responses
1432 that can happen earlier (such as "too many connections") no longer contain
1435 12. If an expansion in a condition on a "warn" statement fails because a lookup
1436 defers, the "warn" statement is abandoned, and the next ACL statement is
1437 processed. Previously this caused the whole ACL to be aborted.
1439 13. Added the iplsearch lookup type.
1441 14. Added ident_timeout as a log selector.
1443 15. Added tls_certificate_verified as a log selector.
1445 16. Added a global option tls_require_ciphers (compare the smtp transport
1446 option of the same name). This controls incoming TLS connections.
1448 17. I finally figured out how to make tls_require_ciphers do a similar thing
1449 in GNUtls to what it does in OpenSSL, that is, set up an appropriate list
1450 before starting the TLS session.
1452 18. Tabs are now shown as \t in -bP output.
1454 19. If the log selector return_path_on_delivery was set, Exim crashed when
1455 bouncing a message because it had too many Received: header lines.
1457 20. If two routers both had headers_remove settings, and the first one included
1458 a superfluous trailing colon, the final name in the first list and the
1459 first name in the second list were incorrectly joined into one item (with a
1460 colon in the middle).
1466 1. Added -C and -D options to the exinext utility, mainly to make it easier
1467 to include in the automated testing, but these could be helpful when
1468 multiple configurations are in use.
1470 2. The exinext utility was not formatting the output nicely when there was
1471 an alternate port involved in the retry record key, nor when there was a
1472 message id as well (for retries that were specific to a specific message
1473 and a specific host). It was also confused by IPv6 addresses, because of
1474 the additional colons they contain. I have fixed the IPv4 problem, and
1475 patched it up to do a reasonable job for IPv6.
1477 3. When there is an error after a MAIL, RCPT, or DATA SMTP command during
1478 delivery, the log line now contains "pipelined" if PIPELINING was used.
1480 4. An SMTP transport process used to panic and die if the bind() call to set
1481 an explicit outgoing interface failed. This has been changed; it is now
1482 treated in the same way as a connect() failure.
1484 5. A reference to $sender_host_name in the part of a conditional expansion
1485 that was being skipped was still causing a DNS lookup. This no longer
1488 6. The def: expansion condition was not recognizing references to header lines
1489 that used bh_ and bheader_.
1491 7. Added the _cache feature to named lists.
1493 8. The code for checking quota_filecount in the appendfile transport was
1494 allowing one more file than it should have been.
1496 9. For compatibility with Sendmail, the command line option
1504 and sets the incoming protocol and host name (for trusted callers). The
1505 host name and its colon can be omitted when only the protocol is to be set.
1506 Note the Exim already has two private options, -pd and -ps, that refer to
1507 embedded Perl. It is therefore impossible to set a protocol value of "d" or
1508 "s", but I don't think that's a major issue.
1510 10. A number of refactoring changes to the code, none of which should affect
1513 (a) The number of logging options was getting close to filling up the
1514 32-bit word that was used as a bit map. I have split them into two classes:
1515 those that are passed in the argument to log_write(), and those that are
1516 only ever tested independently outside of that function. These are now in
1517 separate 32-bit words, so there is plenty of room for expansion again.
1518 There is no change in the user interface or the logging behaviour.
1520 (b) When building, for example, log lines, the code previously used a
1521 macro that called string_cat() twice, in order to add two strings. This is
1522 not really sufficiently general. Furthermore, there was one instance where
1523 it was actually wrong because one of the argument was used twice, and in
1524 one call a function was used. (As it happened, calling the function twice
1525 did not affect the overall behaviour.) The macro has been replaced by a
1526 function that can join an arbitrary number of extra strings onto a growing
1529 (c) The code for expansion conditions now uses a table and a binary chop
1530 instead of a serial search (which was left over from when there were very
1531 few conditions). Also, it now recognizes conditions like "pam" even when
1532 the relevant support is not compiled in: a suitably worded error message is
1533 given if an attempt is made to use such a condition.
1535 11. Added ${time_interval:xxxxx}.
1537 12. A bug was causing one of the ddress fields not to be passed back correctly
1538 from remote delivery subprocesses. The field in question was not being
1539 subsequently used, so this caused to problems in practice.
1541 13. Added new log selectors queue_time and deliver_time.
1543 14. Might have fixed a bug in maildirsizefile handling that threw up
1544 "unexpected character" debug warnings, and recalculated the data
1545 unnecessarily. In any case, I expanded the warning message to give more
1548 15. Added the message "Restricted characters in address" to the statements in
1549 the default ACL that block characters like @ and % in local parts.
1551 16. Change 71 for release 4.31 proved to be much less benign that I imagined.
1552 Three changes have been made:
1554 (a) There was a serious bug; a negative response to MAIL caused the whole
1555 recipient domain to be cached as invalid, thereby blocking all messages
1556 to all local parts at the same domain, from all senders. This bug has
1557 been fixed. The domain is no longer cached after a negative response to
1558 MAIL if the sender used is not empty.
1560 (b) The default behaviour of using MAIL FROM:<> for recipient callouts has
1563 (c) A new callout option, "use_sender" has been added for people who want
1564 the modified behaviour.
1570 1. Removed "EXTRALIBS=-lwrap" from OS/Makefile-Unixware7 on the advice of
1573 2. Removed "LIBS = -lresolv" from OS/Makefile-Darwin as it is not needed, and
1574 indeed breaks things for older releases.
1576 3. Added additional logging to the case where there is a problem reading data
1577 from a filter that is running in a subprocess using a pipe, in order to
1578 try to track down a specific problem.
1580 4. Testing facility fudge: when running in the test harness and attempting
1581 to connect to 10.x.x.x (expecting a connection timeout) I'm now sometimes
1582 getting "No route to host". Convert this to a timeout.
1584 5. Define ICONV_ARG2_TYPE as "char **" for Unixware7 to avoid compiler
1587 6. Some OS don't have socklen_t but use size_t instead. This affects the
1588 fifth argument of getsockopt() amongst other things. This is now
1589 configurable by a macro called SOCKLEN_T which defaults to socklen_t, but
1590 can be set for individual OS. I have set it for SunOS5, OSF1, and
1591 Unixware7. Current versions of SunOS5 (aka Solaris) do have socklen_t, but
1592 some earlier ones do not.
1594 7. Change 4.30/15 was not doing the test caselessly.
1596 8. The standard form for an IPv6 address literal was being rejected by address
1597 parsing in, for example, MAIL and RCPT commands. An example of this kind of
1598 address is [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
1599 this, as well as the form without the "IPv6" on the front (but only when
1600 address literals are enabled, of course).
1602 9. Added some casts to avoid compiler warnings in OS/os.c-Linux.
1604 10. Exim crashed if a message with an empty sender address specified by -f
1605 encountered a router with an errors_to setting. This could be provoked only
1606 by a command such as
1610 where an empty string was supplied; "<>" did not hit this bug.
1612 11. Installed PCRE release 4.5.
1614 12. If EHLO/HELO was rejected by an ACL, the value of $sender_helo_name
1615 remained set. It is now erased.
1617 13. exiqgrep wasn't working on MacOS X because it didn't correctly compute
1618 times from message ids (which are base 36 rather than the normal 62).
1620 14. "Expected" SMTP protocol errors that can arise when PIPELINING is in use
1621 were being counted as actual protocol errors, and logged if the log
1622 selector +smtp_protocol_error was set. One cannot be perfect in this test,
1623 but now, if PIPELINING has been advertised, RCPT following a rejected MAIL,
1624 and DATA following a set of rejected RCPTs do not count as protocol errors.
1625 In other words, Exim assumes they were pipelined, though this may not
1626 actually be the case. Of course, in all cases the client gets an
1627 appropriate error code.
1629 15. If a lookup fails in an ACL condition, a message about the failure may
1630 be available; it is used if testing the ACL cannot continue, because most
1631 such messages specify what the cause of the deferral is. However, some
1632 messages (e.g. "MYSQL: no data found") do not cause a defer. There was bug
1633 that caused an old message to be retained and used if a later statement
1634 caused a defer, replacing the real cause of the deferral.
1636 16. If an IP address had so many PTR records that the DNS lookup buffer
1637 was not large enough to hold them, Exim could crash while trying to process
1638 the truncated data. It now detects and logs this case.
1640 17. Further to 4.21/58, another change has been made: if (and only if) the
1641 first line of a message (the first header line) ends with CRLF, a bare LF
1642 in a subsequent header line has a space inserted after it, so as not to
1643 terminate the header.
1645 18. Refactoring: tidied an ugly bit of code in appendfile that copied data
1646 unnecessarily, used atoi() instead of strtol(), and didn't check the
1647 termination when getting file sizes from file names by regex.
1649 19. Completely re-implemented the support for maildirsize files, in the light
1650 of a number of problems with the previous contributed implementation
1651 (4.30/29). In particular:
1653 . If the quota is zero, the maildirsize file is maintained, but no quota is
1656 . If the maildir directory does not exist, it is created before any attempt
1657 to write a maildirsize file.
1659 . The quota value in the file is just a cache; if the quota is changed in
1660 the transport, the new value overrides.
1662 . A regular expression is available for excluding directories from the
1665 20. The autoreply transport checks the characters in options that define the
1666 message's headers; it allows continued headers, but it was checking with
1667 isspace() after an embedded newline instead of explicitly looking for a
1670 21. If all the "regular" hosts to which an address was routed had passed their
1671 expiry times, and had not reached their retry times, the address was
1672 bounced, even if fallback hosts were defined. Now Exim should go on to try
1675 22. Increased buffer sizes in the callout code from 1024 to 4096 to match the
1676 equivalent code in the SMTP transport. Some hosts send humungous responses
1677 to HELO/EHLO, more than 1024 it seems.
1679 23. Refactoring: code in filter.c used (void *) for "any old type" but this
1680 gives compiler warnings in some environments. I've now done it "properly",
1683 24. The replacement for inet_ntoa() that is used with gcc on IRIX systems
1684 (because of problems with the built-in one) was declared to return uschar *
1685 instead of char *, causing compiler failure.
1687 25. Fixed a file descriptor leak when processing alias/forward files.
1689 26. Fixed a minor format string issue in dbfn.c.
1691 27. Typo in exim.c: ("dmbnz" for "dbmnz").
1693 28. If a filter file refered to $h_xxx or $message_headers, and the headers
1694 contained RFC 2047 "words", Exim's memory could, under certain conditions,
1697 29. When a sender address is verified, it is cached, to save repeating the test
1698 when there is more than one recipient in a message. However, when the
1699 verification involves a callout, it is possible for different callout
1700 options to be set for different recipients. It is too complicated to keep
1701 track of this in the cache, so now Exim always runs a verification when a
1702 callout is required, relying on the callout cache for the optimization.
1703 The overhead is duplication of the address routing, but this should not be
1706 30. Fixed a bug in callout caching. If a RCPT command caused the sender address
1707 to be verified with callout=postmaster, and the main callout worked but the
1708 postmaster check failed, the verification correctly failed. However, if a
1709 subsequent RCPT command asked for sender verification *without* the
1710 postmaster check, incorrect caching caused this verification also to fail,
1713 31. Exim caches DNS lookup failures so as to avoid multiple timeouts; however,
1714 it was not caching the DNS options (qualify_single, search_parents) that
1715 were used when the lookup failed. A subsequent lookup with different
1716 options therefore always gave the same answer, though there were cases
1717 where it should not have. (Example: a "domains = !$mx_any" option on a
1718 dnslookup router: the "domains" option is always processed without any
1719 widening, but the router might have qualify_single set.) Now Exim uses the
1720 cached value only when the same options are set.
1722 32. Added John Jetmore's "exipick" utility to the distribution.
1724 33. GnuTLS: When an attempt to start a TLS session fails for any reason other
1725 than a timeout (e.g. a certificate is required, and is not provided), an
1726 Exim server now closes the connection immediately. Previously it waited for
1727 the client to close - but if the client is SSL, it seems that they each
1728 wait for each other, leading to a delay before one of them times out.
1730 34: GnuTLS: Updated the code to use the new GnuTLS 1.0.0 API. I have not
1731 maintained 0.8.x compatibility because I don't think many are using it, and
1732 it is clearly obsolete.
1734 35. Added TLS support for CRLs: a tls_crl global option and one for the smtp
1737 36. OpenSSL: $tls_certificate_verified was being set to 1 even if the
1738 client certificate was expired. A simple patch fixes this, though I don't
1739 understand the full logic of why the verify callback is called multiple
1742 37. OpenSSL: a patch from Robert Roselius: "Enable client-bug workaround.
1743 Versions of OpenSSL as of 0.9.6d include a 'CBC countermeasure' feature,
1744 which causes problems with some clients (such as the Certicom SSL Plus
1745 library used by Eudora). This option, SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS,
1746 disables the coutermeasure allowing Eudora to connect."
1748 38. Exim was not checking that a write() to a log file succeeded. This could
1749 lead to Bad Things if a log got too big, in particular if it hit a file
1750 size limit. Exim now panics and dies if it cannot write to a log file, just
1751 as it does if it cannot open a log file.
1753 39. Modified OS/Makefile-Linux so that it now contains
1755 CFLAGS=-O -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
1757 The two -D definitions ensure that Exim is compiled with large file
1758 support, which makes it possible to handle log files that are bigger than
1761 40. Fixed a subtle caching bug: if (in an ACL or a set of routers, for
1762 instance) a domain was checked against a named list that involved a lookup,
1763 causing $domain_data to be set, then another domain was checked against the
1764 same list, then the first domain was re-checked, the value of $domain_data
1765 after the final check could be wrong. In particular, if the second check
1766 failed, it could be set empty. This bug probably also applied to
1769 41. The strip_trailing_dot option was not being applied to the address given
1770 with the -f command-line option.
1772 42. The code for reading a message's header from the spool was incrementing
1773 $received_count, but never initializing it. This meant that the value was
1774 incorrect (doubled) while delivering a message in the same process in which
1775 it was received. In the most common configuration of Exim, this never
1776 happens - a fresh exec is done - but it can happen when
1777 deliver_drop_privilege is set.
1779 43. When Exim logs an SMTP synchronization error - client data sent too soon -
1780 it now includes up to 150 characters of the unexpected data in the log
1783 44. The exim_dbmbuild utility uses fixed size buffers for reading input lines
1784 and building data strings. The size of both of these buffers was 10 000
1785 bytes - far larger than anybody would *ever* want, thought I. Needless to
1786 say, somebody hit the limit. I have increased the maximum line length to
1787 20 000 and the maximum data length of concatenated lines to 100 000. I have
1788 also fixed two bugs, because there was no checking on these buffers. Tsk,
1789 tsk. Now exim_dbmbuild gives a message and exits with an error code if a
1790 buffer is too small.
1792 45. The exim_dbmbuild utility did not support quoted keys, as Exim does in
1793 lsearch lookups. Now it does.
1795 46. When parsing a route_list item in a manualroute router, a fixed-length
1796 buffer was used for the list of hosts. I made this 1024 bytes long,
1797 thinking that nobody would ever have a list of hosts that long. Wrong.
1798 Somebody had a whole pile of complicated expansion conditions, and the
1799 string was silently truncated, leading to an expansion error. It turns out
1800 that it is easier to change to an unlimited length (owing to other changes
1801 that have happened since this code was originally written) than to build
1802 structure for giving a limitation error. The length of the item that
1803 expands into the list of hosts is now unlimited.
1805 47. The lsearch lookup could not handle data where the length of text line was
1806 more than 4095 characters. Such lines were truncated, leading to shortened
1807 data being returned. It should now handle lines of any length.
1809 48. Minor wording revision: "cannot test xxx in yyy ACL" becomes "cannot test
1810 xxx condition in yyy ACL" (e.g. "cannot test domains condition in DATA
1813 49. Cosmetic tidy to scripts like exicyclog that are generated by globally
1814 replacing strings such as BIN_DIRECTORY in a source file: the replacement
1815 no longer happens in comment lines. A list of replacements is now placed
1816 at the head of all of the source files, except those whose only change is
1817 to replace PERL_COMMAND in the very first #! line.
1819 50. Replaced the slow insertion sort in queue.c, for sorting the list of
1820 messages on the queue, with a bottom-up merge sort, using code contributed
1821 by Michael Haardt. This should make operations like -bp somewhat faster on
1822 large queues. It won't affect queue runners, except when queue_run_in_order
1825 51. Installed eximstats 1.31 in the distribution.
1827 52. Added support for SRV lookups to the dnslookup router.
1829 53. If an ACL referred to $message_body or $message_body_end, the value was not
1830 reset for any messages that followed in the same SMTP session.
1832 54. The store-handling optimization for building very long strings was not
1833 differentiating between the different store pools. I don't think this
1834 actually made any difference in practice, but I've tidied it.
1836 55. While running the routers to verify a sender address, $sender_address
1837 was still set to the sender address. This is wrong, because when routing to
1838 send a bounce to the sender, it would be empty. Therefore, I have changed
1839 it so that, while verifying a sender address, $sender_address is set to <>.
1840 (There is no change to what happens when verifying a recipient address.)
1842 56. After finding MX (or SRV) records, Exim was doing a DNS lookup for the
1843 target A or AAAA records (if not already returned) without resetting the
1844 qualify_single or search_parents options of the DNS resolver. These are
1845 inappropriate in this case because the targets of MX and SRV records must
1846 be FQDNs. A broken DNS record could cause trouble if it happened to have a
1847 target that, when qualified, matched something in the local domain. These
1848 two options are now turned off when doing these lookups.
1850 57. It seems that at least some releases of Reiserfs (which does not have the
1851 concept of a fixed number of inodes) returns zero and not -1 for the
1852 number of available inodes. This interacted badly with check_spool_inodes,
1853 which assumed that -1 was the "no such thing" setting. What I have done is
1854 to check that the total number of inodes is greater than zero before doing
1855 the test of how many are available.
1857 58. When a "warn" ACL statement has a log_message modifier, the message is
1858 remembered, and not repeated. This is to avoid a lot of repetition when a
1859 message has many recipients that cause the same warning to be written.
1860 Howewer, Exim was preserving the list of already written lines for an
1861 entire SMTP session, which doesn't seem right. The memory is now reset if a
1862 new message is started.
1864 59. The "rewrite" debugging flag was not showing the result of rewriting in the
1865 debugging output unless log_rewrite was also set.
1867 60. Avoid a compiler warning on 64-bit systems in dsearch.c by avoiding the use
1868 of (int)(handle) when we know that handle contains (void *)(-1).
1870 61. The Exim daemon panic-logs an error return when it closes the incoming
1871 connection. However "connection reset by peer" seems to be common, and
1872 isn't really an error worthy of noting specially, so that particular error
1875 62. When Exim is trying to find all the local interfaces, it used to panic and
1876 die if the ioctl to get the interface flags failed. However, it seems that
1877 on at least one OS (Solaris 9) it is possible to have an interface that is
1878 included in the list of interfaces, but for which you get a failure error
1879 for this call. This happens when the interface is not "plumbed" into a
1880 protocol (i.e. neither IPv4 nor IPv6). I've changed the code so that a
1881 failure of the "get flags" call assumes that the interface is down.
1883 63. Added a ${eval10: operator, which assumes all numbers are decimal. This
1884 makes life easier for people who are doing arithmetic on fields extracted
1885 from dates, where you often get leading zeros that should not be
1886 interpreted as octal.
1888 64. Added qualify_domain to the redirect router, to override the global
1891 65. If a pathologically long header line contained very many addresses (the
1892 report of this problem mentioned 10 000) and each of them was rewritten,
1893 Exim could use up a very large amount of memory. (It kept on making new
1894 copies of the header line as it rewrote, and never released the old ones.)
1895 At the expense of a bit more processing, the header rewriting function has
1896 been changed so that it no longer eats memory in this way.
1898 66. The generation of the Received: header has been moved from the time that a
1899 message starts to be received, to the time that it finishes. The timestamp
1900 in the Received: header should now be very close to that of the <= log
1901 line. There are two side-effects of this change:
1903 (a) If a message is rejected by a DATA or non-SMTP ACL or local_scan(), the
1904 logged header lines no longer include the local Received: line, because
1905 it has not yet been created. The same applies to a copy of the message
1906 that is returned to a non-SMTP sender when a message is rejected.
1908 (b) When a filter file is tested using -bf, no additional Received: header
1909 is added to the test message. After some thought, I decided that this
1912 This change does not affect the value of $received_for. It is still set
1913 after address rewriting, but before local_scan() is called.
1915 67. Installed the latest Cygwin-specific files from the Cygwin maintainer.
1917 68. GnuTLS: If an empty file is specified for tls_verify_certificates, GnuTLS
1918 gave an unhelpful panic error message, and a defer error. I have managed to
1919 change this behaviour so that it now rejects any supplied certificate,
1920 which seems right, as the list of acceptable certificates is empty.
1922 69. OpenSSL: If an empty file is specified for tls_verify_certificates, OpenSSL
1923 gave an unhelpful defer error. I have not managed to make this reject any
1924 supplied certificates, but the error message it gives is "no certificate
1925 supplied", which is not helpful.
1927 70. exigrep's output now also includes lines that are not associated with any
1928 message, but which match the given pattern. Implemented by a patch from
1929 Martin Sluka, which also tidied up the Perl a bit.
1931 71. Recipient callout verification, like sender verification, was using <> in
1932 the MAIL FROM command. This isn't really the right thing, since the actual
1933 sender may affect whether the remote host accepts the recipient or not. I
1934 have changed it to use the actual sender in the callout; this means that
1935 the cache record is now keyed on a recipient/sender pair, not just the
1936 recipient address. There doesn't seem to be a real danger of callout loops,
1937 since a callout by the remote host to check the sender would use <>.
1938 [SEE ABOVE: changed after hitting problems.]
1940 72. Exim treats illegal SMTP error codes that do not begin with 4 or 5 as
1941 temporary errors. However, in the case of such a code being given after
1942 the end of a data transmission (i.e. after ".") Exim was failing to write
1943 a retry record for the message. (Yes, there was some broken host that was
1944 actually sending 8xx at this point.)
1946 73. An unknown lookup type in a host list could cause Exim to panic-die when
1947 the list was checked. (An example that provoked this was putting <; in the
1948 middle of a list instead of at the start.) If this happened during a DATA
1949 ACL check, a -D file could be left lying around. This kind of configuration
1950 error no longer causes Exim to die; instead it causes a defer errror. The
1951 incident is still logged to the main and panic logs.
1953 74. Buglet left over from Exim 3 conversion. The message "too many messages
1954 in one connection" was written to the rejectlog but not the mainlog, except
1955 when address rewriting (yes!) was being logged.
1957 75. Added write_rejectlog option.
1959 76. When a system filter was run not as root (that is, when system_filter_user
1960 was set), the values of the $n variables were not being returned to the
1961 main process; thus, they were not subsequently available in the $sn
1964 77. Added +return_path_on_delivery log selector.
1966 78. A connection timeout was being treated differently from recipients deferred
1967 when testing hosts_max_try with a message that was older than the host's
1968 retry timeout. (The host should not be counted, thus allowing all hosts to
1969 be tried at least once before bouncing.) This may have been the cause of an
1970 occasionally reported bug whereby a message would remain on the queue
1971 longer than the retry timeout, but would be bounced if a delivery was
1972 forced. I say "may" because I never totally pinned down the problem;
1973 setting up timeout/retry tests is difficult. See also the next item.
1975 79. The ultimate address timeout was not being applied to errors that involved
1976 a combination of host plus message (for example, a timeout on a MAIL
1977 command). When an address resolved to a number of possible hosts, and they
1978 were not all tried for each delivery (e.g. because of hosts_max_try), a
1979 message could remain on the queue longer than the retry timeout.
1981 80. Sieve bug: "stop" inside "elsif" was broken. Applied a patch from Michael
1984 81. Fixed an obscure SMTP outgoing bug which required at least the following
1985 conditions: (a) there was another message waiting for the same server;
1986 (b) the server returned 5xx to all RCPT commands in the first message so
1987 that the message was not completed; (c) the server dropped the connection
1988 or gave a negative response to the RSET that Exim sends to abort the
1989 transaction. The observed case was a dropped connection after DATA that had
1990 been sent in pipelining mode. That is, the server had advertised PIPELINING
1991 but was not implementing it correctly. The effect of the bug was incorrect
1992 behaviour, such as trying another host, and this could lead to a crash.
1998 1. The 3rd arguments to getsockname(), getpeername(), and accept() in exim.c
1999 and daemon.c were passed as pointers to ints; they should have been
2000 pointers to socklen_t variables (which are typically unsigned ints).
2002 2. Some signed/unsigned type warnings in the os.c file for Linux have been
2005 3. Fixed a really odd bug that affected only the testing scheme; patching a
2006 certain fixed string in the binary changed the value of another string that
2007 happened to be identical to the end of the original first string.
2009 4. When gethostbyname() (or equivalent) is passed an IP address as a "host
2010 name", it returns that address as the IP address. On some operating
2011 systems (e.g. Solaris), it also passes back the IP address string as the
2012 "host name". However, on others (e.g. Linux), it passes back an empty
2013 string. Exim wasn't checking for this, and was changing the host name to an
2014 empty string, assuming it had been canonicized.
2016 5. Although rare, it is permitted to have more than one PTR record for a given
2017 IP address. I thought that gethostbyaddr() or getipnodebyaddr() always gave
2018 all the names associated with an address, because they do in Solaris.
2019 However, it seems that they do not in Linux for data that comes from the
2020 DNS. If an address in /etc/hosts has multiple names, they _are_ all given.
2021 I found this out when I moved to a new Linux workstation and tried to run
2022 the Exim test suite.
2024 To get round this problem I have changed the code so that it now does its
2025 own call to the DNS to look up PTR records when searching for a host name.
2026 If nothing can be found in the DNS, it tries gethostbyaddr(), so that
2027 addresses that are only in /etc/hosts are still found.
2029 This behaviour is, however, controlled by an option called host_lookup_
2030 order, which defaults to "bydns:byaddr". If people want to use the other
2031 order, or indeed, just use one or the other means of lookup, they can
2032 specify it in this variable.
2034 6. If a PTR record yields an empty name, Exim treats it as non-existent. In
2035 some operating systems, this comes back from gethostbyaddr() as an empty
2036 string, and this is what Exim used to test for. However, it seems that in
2037 other systems, "." is yielded. Exim now tests for this case too.
2039 7. The values of check_spool_space and check_log_space are now held internally
2040 as a number of kilobytes instead of an absolute number of bytes. If a
2041 numbers is specified without 'K' or 'M', it is rounded up to the nearest
2042 kilobyte. This means that much larger values can be stored.
2044 8. Exim monitor: an attempt to get the action menu when not actually pointing
2045 at a message produces an empty menu entitled "No message selected". This
2046 works on Solaris (OpenWindows). However, XFree86 does not like a menu with
2047 no entries in it ("Shell widget menu has zero width and/or height"). So I
2048 have added a single, blank menu entry in this case.
2050 9. Added ${quote_local_part.
2052 10. MIME decoding is now applied to the contents of Subject: header lines when
2055 11. Now that a reference to $sender_host_address automatically causes a reverse
2056 lookup to occur if necessary (4.13/18), there is no need to arrange for a
2057 host lookup before query-style lookups in lists that might use this
2058 variable. This has therefore been abolished, and the "net-" prefix is no
2059 longer necessary for query-style lookups.
2061 12. The Makefile for SCO_SV contained a setting of LDFLAGS. This appears to
2062 have been a typo for LFLAGS, so it has been changed.
2064 13. The install script calls Exim with "-C /dev/null" in order to find the
2065 version number. If ALT_CONFIG_PREFIX was set, this caused an error message
2066 to be output. Howeve, since Exim outputs its version number before the
2067 error, it didn't break the script. It just looked ugly. I fixed this by
2068 always allowing "-C /dev/null" if the caller is root.
2070 14. Ignore overlarge ACL variable number when reading spool file - insurance
2071 against a later release with more variables having written the file.
2073 15. The standard form for an IPv6 address literal was being rejected by EHLO.
2074 Example: [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
2075 this, as well as the form without the "IPv6" on the front.
2077 16. Added CHOWN_COMMAND=/usr/sbin/chown and LIBS=-lresolv to the
2078 OS/Makefile-Darwin file.
2080 17. Fixed typo in lookups/ldap.c: D_LOOKUP should be D_lookup. This applied
2081 only to LDAP libraries that do not have LDAP_OPT_DEREF.
2083 18. After change 4.21/52, "%ld" was used to format the contents of the $inode
2084 variable. However, some OS use ints for inodes. I've added cast to long int
2085 to get rid of the compiler warning.
2087 19. I had forgotten to lock out "/../" in configuration file names when
2088 ALT_CONFIG_PREFIX was set.
2090 20. Routers used for verification do not need to specify transports. However,
2091 if such a router generated a host list, and callout was configured, Exim
2092 crashed, because it could not find a port number from the (non-existent)
2093 transport. It now assumes port 25 in this circumstance.
2095 21. Added the -t option to exigrep.
2097 22. If LOOKUP_LSEARCH is defined, all three linear search methods (lsearch,
2098 wildlsearch, nwildlsearch) are compiled. LOOKUP_WILDLSEARCH and LOOKUP_
2099 NWILDLSEARCH are now obsolete, but retained for compatibility. If either of
2100 them is set, LOOKUP_LSEARCH is forced.
2102 23. "exim -bV" now outputs a list of lookups that are included in the binary.
2104 24. Added sender and host information to the "rejected by local_scan()" log
2105 line; previously there was no indication of these.
2107 25. Added .include_if_exists.
2109 26. Change 3.952/11 added an explicit directory sync on top of a file sync for
2110 Linux. It turns out that not all file systems support this. Apparently some
2111 versions of NFS do not. (It's rare to put Exim's spool on NFS, but people
2112 do it.) To cope with this, the error EINVAL, which means that sync-ing is
2113 not supported on the file descriptor, is now ignored when Exim is trying to
2114 sync a directory. This applies only to Linux.
2116 27. Added -DBIND_8_COMPAT to the CLFAGS setting for Darwin.
2118 28. In Darwin (MacOS X), the PAM headers are in /usr/include/pam and not in
2119 /usr/include/security. There's now a flag in OS/os.h-Darwin to cope with
2122 29. Added support for maildirsize files from supplied patch (modified a bit).
2124 30. The use of :fail: followed by an empty string could lead Exim to respond to
2125 sender verification failures with (e.g.):
2127 550 Verification failed for <xxx>
2128 550 Sender verify failed
2130 where the first response line was missing the '-' that indicates it is not
2131 the final line of the response.
2133 31. The loop for finding the name of the user that called Exim had a hardwired
2134 limit of 10; it now uses the value of finduser_retries, which is used for
2135 all other user lookups.
2137 32. Added $received_count variable, available in data and not_smtp ACLs, and at
2140 33. Exim was neglecting to zero errno before one call of strtol() when
2141 expanding a string and expecting an integer value. On some systems this
2142 resulted in spurious "integer overflow" errors. Also, it was casting the
2143 result into an int without checking.
2145 34. Testing for a connection timeout using "timeout_connect" in the retry rules
2146 did not work. The code looks as if it has *never* worked, though it appears
2147 to have been documented since at least releast 1.62. I have made it work.
2149 35. The "timeout_DNS" error in retry rules, also documented since at least
2150 1.62, also never worked. As it isn't clear exactly what this means, and
2151 clearly it isn't a major issue, I have abolished the feature by treating it
2152 as "timeout", and writing a warning to the main and panic logs.
2154 36. The display of retry rules for -brt wasn't always showing the error code
2157 37. Added new error conditions to retry rules: timeout_A, timeout_MX,
2158 timeout_connect_A, timeout_connect_MX.
2160 38. Rewriting the envelope sender at SMTP time did not allow it to be rewritten
2161 to the empty sender.
2163 39. The daemon was not analysing the content of -oX till after it had closed
2164 stderr and disconnected from the controlling terminal. This meant that any
2165 syntax errors were only noted on the panic log, and the return code from
2166 the command was 0. By re-arranging the code a little, I've made the
2167 decoding happen first, so such errors now appear on stderr, and the return
2168 code is 1. However, the actual setting up of the sockets still happens in
2169 the disconnected process, so errors there are still only recorded on the
2172 40. A daemon listener on a wildcard IPv6 socket that also accepts IPv4
2173 connections (as happens on some IP stacks) was logged at start up time as
2174 just listening for IPv6. It now logs "IPv6 with IPv4". This differentiates
2175 it from "IPv6 and IPv4", which means that two separate sockets are being
2178 41. The debug output for gethostbyname2() or getipnodebyname() failures now
2179 says whether AF_INET or AF_INET6 was passed as an argument.
2181 42. Exiwhat output was messed up when time zones were included in log
2184 43. Exiwhat now gives more information about the daemon's listening ports,
2185 and whether -tls-on-connect was used.
2187 44. The "port" option of the smtp transport is now expanded.
2189 45. A "message" modifier in a "warn" statement in a non-message ACL was being
2190 silently ignored. Now an error message is written to the main and panic
2193 46. There's a new ACL modifier called "logwrite" which writes to a log file
2194 as soon as it is encountered.
2196 47. Added $local_user_uid and $local_user_gid at routing time.
2198 48. Exim crashed when trying to verify a sender address that was being
2201 49. Exim was recognizing only a space character after ".include". It now also
2202 recognizes a tab character.
2204 50. Fixed several bugs in the Perl script that creates the exim.8 man page by
2205 extracting the relevant information from the specification. The man page no
2206 longer contains scrambled data for the -d option, and I've added a section
2207 at the front about calling Exim under different names.
2209 51. Added "extra_headers" argument to the "mail" command in filter files.
2211 52. Redirecting mail to an unqualified address in a Sieve filter caused Exim to
2214 53. Installed eximstats 1.29.
2216 54. Added transport_filter_timeout as a generic transport option.
2218 55. Exim no longer adds an empty Bcc: header to messages that have no To: or
2219 Cc: header lines. This was required by RFC 822, but it not required by RFC
2222 56. Exim used to add From:, Date:, and Message-Id: header lines to any
2223 incoming messages that did not have them. Now it does so only if the
2224 message originates locally, that is, if there is no associated remote host
2225 address. When Resent- header lines are present, this applies to the Resent-
2226 lines rather than the non-Resent- lines.
2228 57. Drop incoming SMTP connection after too many syntax or protocol errors. The
2229 limit is controlled by smtp_max_synprot_errors, defaulting to 3.
2231 58. Messages for configuration errors now include the name of the main
2232 configuration file - useful now that there may be more than one file in a
2233 list (.included file names were always shown).
2235 59. Change 4.21/82 (run initgroups() when starting the daemon) causes problems
2236 for those rare installations that do not start the daemon as root or run it
2237 setuid root. I've cut out the call to initgroups() if the daemon is not
2240 60. The Exim user and group can now be bound into the binary as text strings
2241 that are looked up at the start of Exim's processing.
2243 61. Applied a small patch for the Interbase code, supplied by Ard Biesheuvel.
2245 62. Added $mailstore_basename variable.
2247 63. Installed patch to sieve.c from Michael Haardt.
2249 64. When Exim failed to open the panic log after failing to open the main log,
2250 the original message it was trying to log was written to stderr and debug
2251 output, but if they were not available (the usual case in production), it
2252 was lost. Now it is written to syslog before the two lines that record the
2253 failures to open the logs.
2255 65. Users' Exim filters run in subprocesses under the user's uid. It is
2256 possible for a "deliver" command or an alias in a "personal" command to
2257 provoke an address rewrite. If logging of address rewriting is configured,
2258 this fails because the process is not running as root or exim. There may be
2259 a better way of dealing with this, but for the moment (because 4.30 needs
2260 to be released), I have disabled address rewrite logging when running a
2261 filter in a non-root, non-exim process.
2267 1. The buildconfig auxiliary program wasn't quoting the value set for
2268 HEADERS_CHARSET. This caused a compilation error complaining that 'ISO' was
2269 not defined. This bug was masked in 4.22 by the effect that was fixed in
2272 2. Some messages that were rejected after a message id was allocated were
2273 shown as "incomplete" by exigrep. It no longer does this for messages that
2274 are rejected by local_scan() or the DATA or non-SMTP ACLs.
2276 3. If a Message-ID: header used a domain literal in the ID, and Exim did not
2277 have allow_domain_literals set, the ID did not get logged in the <= line.
2278 Domain literals are now always recognized in Message-ID: header lines.
2280 4. The first argument for a ${extract expansion item is the key name or field
2281 number. Leading and trailing spaces in this item were not being ignored,
2282 causing some misleading effects.
2284 5. When deliver_drop_privilege was set, single queue runner processes started
2285 manually (i.e. by the command "exim -q") or by the daemon (which uses the
2286 same command in the process it spins off) were not dropping privilege.
2288 6. When the daemon running as "exim" started a queue runner, it always
2289 re-executed Exim in the spun-off process. This is a waste of effort when
2290 deliver_drop_privilege is set. The new process now just calls the
2291 queue-runner function directly.
2297 1. Typo in the src/EDITME file: it referred to HEADERS_DECODE_TO instead of
2300 2. Change 4.21/73 introduced a bug. The pid file path set by -oP was being
2301 ignored. Though the use of -oP was forcing the writing of a pid file, it
2302 was always written to the default place.
2304 3. If the message "no IP address found for host xxxx" is generated during
2305 incoming verification, it is now followed by identification of the incoming
2306 connection (so you can more easily find what provoked it).
2308 4. Bug fix for Sieve filters: "stop" inside a block was not working properly.
2310 5. Added some features to "harden" Exim a bit more against certain attacks:
2312 (a) There is now a build-time option called FIXED_NEVER_USERS that can
2313 be put in Local/Makefile. This is like the never_users runtime option,
2314 but it cannot be overridden. The default setting is "root".
2316 (b) If ALT_CONFIG_PREFIX is defined in Local/Makefile, it specifies a
2317 prefix string with which any file named in a -C command line option
2320 (c) If ALT_CONFIG_ROOT_ONLY is defined in Local/Makefile, root privilege
2321 is retained for -C and -D only if the caller of Exim is root. Without
2322 it, the exim user may also use -C and -D and retain privilege.
2324 (d) If DISABLE_D_OPTION is defined in Local/Makefile, the use of the -D
2325 command line option is disabled.
2327 6. Macro names set by the -D option must start with an upper case letter, just
2328 like macro names defined in the configuration file.
2330 7. Added "dereference=" facility to LDAP.
2332 8. Two instances of the typo "uknown" in the source files are fixed.
2334 9. If a PERL_COMMAND setting in Local/Makefile was not at the start of a line,
2335 the Configure-Makefile script screwed up while processing it.
2337 10. Incorporated PCRE 4.4.
2339 11. The SMTP synchronization check was not operating right at the start of an
2340 SMTP session. For example, it could not catch a HELO sent before the client
2341 waited for the greeting. There is now a check for outstanding input at the
2342 point when the greeting is written. Because of the duplex, asynchronous
2343 nature of TCP/IP, it cannot be perfect - the incorrect input may be on its
2344 way, but not yet received, when the check is performed.
2346 12. Added tcp_nodelay to make it possible to turn of the setting of TCP_NODELAY
2347 on TCP/IP sockets, because this apparently causes some broken clients to
2350 13. Installed revised OS/Makefile-CYGWIN and OS/os.c-cygwin (the .h file was
2351 unchanged) from the Cygwin maintainer.
2353 14. The code for -bV that shows what is in the binary showed "mbx" when maildir
2354 was supported instead of testing for mbx. Effectively a typo.
2356 15. The spa authenticator server code was not checking that the input it
2357 received was valid base64.
2359 16. The debug output line for the "set" modifier in ACLs was not showing the
2360 name of the variable that was being set.
2362 17. Code tidy: the variable type "vtype_string" was never used. Removed it.
2364 18. Previously, a reference to $sender_host_name did not cause a DNS reverse
2365 lookup on its own. Something else was needed to trigger the lookup. For
2366 example, a match in host_lookup or the need for a host name in a host list.
2367 Now, if $sender_host_name is referenced and the host name has not yet been
2368 looked up, a lookup is performed. If the lookup fails, the variable remains
2369 empty, and $host_lookup_failed is set to "1".
2371 19. Added "eqi" as a case-independent comparison operator.
2373 20. The saslauthd authentication condition could segfault if neither service
2374 nor realm was specified.
2376 21. If an overflowing value such as "2048M" was set for message_size_limit, the
2377 error message that was logged was misleading, and incoming SMTP
2378 connections were dropped. The message is now more accurate, and temporary
2379 errors are given to SMTP connections.
2381 22. In some error situations (such as 21 above) Exim rejects all SMTP commands
2382 (except RSET) with a 421 error, until QUIT is received. However, it was
2383 failing to send a response to QUIT.
2385 23. The HELO ACL was being run before the code for helo_try_verify_hosts,
2386 which made it impossible to use "verify = helo" in the HELO ACL. The HELO
2387 ACL is now run after the helo_try_verify_hosts code.
2389 24. "{MD5}" and "{SHA1}" are now recognized as equivalent to "{md5"} and
2390 "{sha1}" in the "crypteq" expansion condition (in fact the comparison is
2391 case-independent, so other case variants are also recognized). Apparently
2392 some systems use these upper case variants.
2394 25. If more than two messages were waiting for the same host, and a transport
2395 filter was specified for the transport, Exim sent two messages over the
2396 same TCP/IP connection, and then failed with "socket operation on non-
2397 socket" when it tried to send the third.
2399 26. Added Exim::debug_write and Exim::log_write for embedded Perl use.
2401 27. The extern definition of crypt16() in expand.c was not being excluded when
2402 the OS had its own crypt16() function.
2404 28. Added bounce_return_body as a new option, and bounce_return_size_limit
2405 as a preferred synonym for return_size_limit, both as an option and as an
2408 29. Added LIBS=-liconv to OS/Makefile-OSF1.
2410 30. Changed the default configuration ACL to relax the local part checking rule
2411 for addresses that are not in any local domains. For these addresses,
2412 slashes and pipe symbols are allowed within local parts, but the sequence
2413 /../ is explicitly forbidden.
2415 31. SPA server authentication was not clearing the challenge buffer before
2418 32. log_message in a "warn" ACL statement was writing to the reject log as
2419 well as to the main log, which contradicts the documentation and doesn't
2420 seem right (because no rejection is happening). So I have stopped it.
2422 33. Added Ard Biesheuvel's lookup code for accessing an Interbase database.
2423 However, I am unable to do any testing of this.
2425 34. Fixed an infelicity in the appendfile transport. When checking directories
2426 for a mailbox, to see if any needed to be created, it was accidentally
2427 using path names with one or more superfluous leading slashes; tracing
2428 would show up entries such as stat("///home/ph10", 0xFFBEEA48).
2430 35. If log_message is set on a "discard" verb in a MAIL or RCPT ACL, its
2431 contents are added to the log line that is written for every discarded
2432 recipient. (Previously a log_message setting was ignored.)
2434 36. The ${quote: operator now quotes the string if it is empty.
2436 37. The install script runs exim in order to find its version number. If for
2437 some reason other than non-existence or emptiness, which it checks, it
2438 could not run './exim', it was installing it with an empty version number,
2439 i.e. as "exim-". This error state is now caught, and the installation is
2442 38. An argument was missing from the function that creates an error message
2443 when Exim fails to connect to the socket for saslauthd authentication.
2444 This could cause Exim to crash, or give a corrupted message.
2446 39. Added isip, isip4, and isip6 to ${if conditions.
2448 40. The ACL variables $acl_xx are now saved with the message, and can be
2449 accessed later in routers, transports, and filters.
2451 41. The new lookup type nwildlsearch is like wildlsearch, except that the key
2452 strings in the file are not string-expanded.
2454 42. If a MAIL command specified a SIZE value that was too large to fit into an
2455 int variable, the check against message_size_limit failed. Such values are
2456 now forced to INT_MAX, which is around 2Gb for a 32-bit variable. Maybe one
2457 day this will have to be increased, but I don't think I want to be around
2458 when emails are that large.
2465 1. Removed HAVE_ICONV=yes from OS/Makefile-FreeBSD, since it seems that
2466 iconv() is not standard in FreeBSD.
2468 2. Change 4.21/17 was buggy and could cause stack overwriting on a system with
2469 IPv6 enabled. The observed symptom was a segmentation fault on return from
2470 the function os_common_find_running_interfaces() in src/os.c.
2472 3. In the check_special_case() function in daemon.c I had used "errno" as an
2473 argument name, which causes warnings on some systems. This was basically a
2474 typo, since it was named "eno" in the comments!
2476 4. The code that waits for the clock to tick (at a resolution of some fraction
2477 of a second) so as to ensure message-id uniqueness was always waiting for
2478 at least one whole tick, when it could have waited for less. [This is
2479 almost certainly not relevant at current processor speeds, where it is
2480 unlikely to ever wait at all. But we try to future-proof.]
2482 5. The function that sleeps for a time interval that includes fractions of a
2483 second contained a race. It did not block SIGALRM between setting the
2484 timer, and suspending (a couple of lines later). If the interval was short
2485 and the sigsuspend() was delayed until after it had expired, the suspension
2486 never ended. On busy systems this could lead to processes getting stuck for
2489 6. Some uncommon configurations may cause a lookup to happen in a queue runner
2490 process, before it forks any delivery processes. The open lookup caching
2491 mechanism meant that the open file or database connection was passed into
2492 the delivery process. The problem was that delivery processes always tidy
2493 up cached lookup data. This could cause a problem for the next delivery
2494 process started by the queue runner, because the external queue runner
2495 process does not know about the closure. So the next delivery process
2496 still has data in the lookup cache. In the case of a file lookup, there was
2497 no problem because closing a file descriptor in a subprocess doesn't affect
2498 the parent. However, if the lookup was caching a connection to a database,
2499 the connection was closed, and the second delivery process was likely to
2500 see errors such as "PGSQL: query failed: server closed the connection
2501 unexpectedly". The problem has been fixed by closing all cached lookups
2502 in a queue runner before running a delivery process.
2504 7. Compiler warning on Linux for the second argument of iconv(), which doesn't
2505 seem to have the "const" qualifier which it has on other OS. I've
2508 8. Change 4.21/2 was too strict. It is only if there are two authenticators
2509 *of the same type* (client or server) with the same public name that an
2510 error should be diagnosed.
2512 9. When Exim looked up a host name for an IP address, but failed to find the
2513 original IP address when looking up the host name (a safety check), it
2514 output the message "<ip address> does not match any IP for NULL", which was
2515 confusing, to say the least. The bug was that the host name should have
2516 appeared instead of "NULL".
2518 10. Since release 3.03, if Exim is called by a uid other than root or the Exim
2519 user that is built into the binary, and the -C or -D options is used, root
2520 privilege is dropped before the configuration file is read. In addition,
2521 logging is switched to stderr instead of the normal log files. If the
2522 configuration then re-defines the Exim user, the unprivileged environment
2523 is probably not what is expected, so Exim logs a panic warning message (but
2526 However, if deliver_drop_privilege is set, the unprivileged state may well
2527 be exactly what is intended, so the warning has been cut out in that case,
2528 and Exim is allowed to try to write to its normal log files.
2534 1. smtp_return_error_details was not giving details for temporary sender
2535 or receiver verification errors.
2537 2. Diagnose a configuration error if two authenticators have the same public
2540 3. Exim used not to create the message log file for a message until the first
2541 delivery attempt. This could be confusing when incoming messages were held
2542 for policy or load reasons. The message log file is now created at the time
2543 the message is received, and an initial "Received" line is written to it.
2545 4. The automatically generated man page for command line options had a minor
2546 bug that caused no ill effects; however, a more serious problem was that
2547 the procedure for building the man page automatically didn't always
2548 operate. Consequently, release 4.20 contains an out-of-date version. This
2549 shouldn't happen again.
2551 5. When building Exim with embedded Perl support, the script that builds the
2552 Makefile was calling 'perl' to find its compile-time parameters, ignoring
2553 any setting of PERL_COMMAND in Local/Makefile. This is now fixed.
2555 6. The freeze_tell option was not being used for messages that were frozen on
2556 arrival, either by an ACL or by local_scan().
2558 7. Added the smtp_incomplete_transaction log selector.
2560 8. After STARTTLS, Exim was not forgetting that it had advertised AUTH, so it
2561 was accepting AUTH without a new EHLO.
2563 9. Added tls_remember_esmtp to cope with YAEB. This allows AUTH and other
2564 ESMTP extensions after STARTTLS without a new EHLO, in contravention of the
2567 10. Logging of TCP/IP connections (when configured) now happens in the main
2568 daemon process instead of the child process, so that the TCP/IP connection
2569 count is more accurate (but it can never be perfect).
2571 11. The use of "drop" in a nested ACL was not being handled correctly in the
2572 outer ACL. Now, if condition failure induced by the nested "drop" causes
2573 the outer ACL verb to deny access ("accept" or "discard" after "endpass",
2574 or "require"), the connection is dropped.
2576 12. Similarly, "discard" in a nested ACL wasn't being handled. A nested ACL
2577 that yield "discard" can now be used with an "accept" or a "discard" verb,
2578 but an error is generated for any others (because I can't see a useful way
2579 to define what should happen).
2581 13. When an ACL is read dynamically from a file (or anywhere else), the lines
2582 are now processed in the same way as lines in the Exim configuration file.
2583 In particular, continuation lines are supported.
2585 14. Added the "dnslists = a.b.c!=n.n.n.n" feature.
2587 15. Added -ti meaning -t -i.
2589 16. Check for letters, digits, hyphens, and dots in the names of dnslist
2590 domains, and warn by logging if others are found.
2592 17. At least on BSD, alignment is not guarenteed for the array of ifreq's
2593 returned from GIFCONF when Exim is trying to find the list of interfaces on
2594 a host. The code in os.c has been modified to copy each ifreq to an aligned
2595 structure in all cases.
2597 Also, in some cases, the returned ifreq's were being copied to a 'struct
2598 ifreq' on the stack, which was subsequently passed to host_ntoa(). That
2599 means the last couple of bytes of an IPv6 address could be chopped if the
2600 ifreq contained only a normal sockaddr (14 bytes storage).
2602 18. Named domain lists were not supported in the hosts_treat_as_local option.
2603 An entry such as +xxxx was not recognized, and was treated as a literal
2606 19. Ensure that header lines added by a DATA ACL are included in the reject log
2607 if the ACL subsequently rejects the message.
2609 20. Upgrade the cramtest.pl utility script to use Digest::MD5 instead of just
2610 MD5 (which is deprecated).
2612 21. When testing a filter file using -bf, Exim was writing a message when it
2613 took the sender from a "From " line in the message, but it was not doing so
2614 when it took $return_path from a Return-Path: header line. It now does.
2616 22. If the contents of a "message" modifier for a "warn" ACL verb do not begin
2617 with a valid header line field name (a series of printing characters
2618 terminated by a colon, Exim now inserts X-ACL-Warn: at the beginning.
2620 23. Changed "disc" in the source to "disk" to conform to the documentation and
2621 the book and for uniformity.
2623 24. Ignore Sendmail's -Ooption=value command line item.
2625 25. When execve() failed while trying to run a command in a pipe transport,
2626 Exim was returning EX_UNAVAILBLE (69) from the subprocess. However, this
2627 could be confused with a return value of 69 from the command itself. This
2628 has been changed to 127, the value the shell returns if it is asked to run
2629 a non-existent command. The wording for the related log line suggests a
2630 non-existent command as the problem.
2632 26. If received_header_text expands to an empty string, do not add a Received:
2633 header line to the message. (Well, it adds a token one on the spool, but
2634 marks it "old" so that it doesn't get used or transmitted.)
2636 27. Installed eximstats 1.28 (addition of -nt option).
2638 28. There was no check for failure on the call to getsockname() in the daemon
2639 code. This can fail if there is a shortage of resources on the system, with
2640 ENOMEM, for example. A temporary error is now given on failure.
2642 29. Contrary to the C standard, it seems that in some environments, the
2643 equivalent of setlocale(LC_ALL, "C") is not obeyed at the start of a C
2644 program. Exim now does this explicitly; it affects the formatting of
2645 timestamps using strftime().
2647 30. If exiqsumm was given junk data, it threw up some uninitialized variable
2648 complaints. I've now initialized all the variables, to avoid this.
2650 32. Header lines added by a system filter were not being "seen" during
2651 transport-time rewrites.
2653 33. The info_callback() function passed to OpenSSL is set up with type void
2654 (*)(SSL *, int, int), as described somewhere. However, when calling the
2655 function (actually a macro) that sets it up, the type void(*)() is
2656 expected. I've put in a cast to prevent warnings from picky compilers.
2658 34. If a DNS black list lookup found a CNAME record, but there were no A
2659 records associated with the domain it pointed at, Exim crashed.
2661 35. If a DNS black list lookup returned more than one A record, Exim ignored
2662 all but the first. It now scans all returned addresses if a particular IP
2663 value is being sought. In this situation, the contents of the
2664 $dnslist_value variable are a list of all the addresses, separated by a
2667 36. Tightened up the rules for host name lookups using reverse DNS. Exim used
2668 to accept a host name and all its aliases if the forward lookup for any of
2669 them yielded the IP address of the incoming connection. Now it accepts only
2670 those names whose forward lookup yields the correct IP address. Any other
2671 names are discarded. This closes a loophole whereby a rogue DNS
2672 administrator could create reverse DNS records to break through a
2673 wildcarded host restriction in an ACL.
2675 37. If a user filter or a system filter that ran in a subprocess used any of
2676 the numerical variables ($1, $2 etc), or $thisaddress, in a pipe command,
2677 the wrong values were passed to the pipe command ($thisaddress had the
2678 value of $0, $0 had the value of $1, etc). This bug was introduced by
2679 change 4.11/101, and not discovered because I wrote an inadequate test. :-(
2681 38. Improved the line breaking for long SMTP error messages from ACLs.
2682 Previously, if there was no break point between 40 and 75 characters, Exim
2683 left the rest of the message alone. Two changes have been made: (a) I've
2684 reduced the minimum length to 35 characters; (b) if it can't find a break
2685 point between 35 and 75 characters, it looks ahead and uses the first one
2686 that it finds. This may give the occasional overlong line, but at least the
2687 remaining text gets split now.
2689 39. Change 82 of 4.11 was unimaginative. It assumed the limit on the number of
2690 file descriptors might be low, and that setting 1000 would always raise it.
2691 It turns out that in some environments, the limit is already over 1000 and
2692 that lowering it causes trouble. So now Exim takes care not to decrease it.
2694 40. When delivering a message, the value of $return_path is set to $sender_
2695 address at the start of routing (routers may change the value). By an
2696 oversight, this default was not being set up when an address was tested by
2697 -bt or -bv, which affected the outcome if any router or filter referred to
2700 41. The idea of the "warn" ACL verb is that it adds a header or writes to the
2701 log only when "message" or "log_message" are set. However, if one of the
2702 conditions was an address verification, or a call to a nested ACL, the
2703 messages generated by the underlying test were being passed through. This
2704 no longer happens. The underlying message is available in $acl_verify_
2705 message for both "message" and "log_message" expansions, so it can be
2706 passed through if needed.
2708 42. Added RFC 2047 interpretation of header lines for $h_ expansions, with a
2709 new expansion $bh_ to give the encoded byte string without charset
2710 translation. Translation happens only if iconv() is available; HAVE_ICONV
2711 indicates this at build time. HEADERS_CHARSET gives the charset to
2712 translate to; headers_charset can change it in the configuration, and
2713 "headers charset" can change it in an individual filter file.
2715 43. Now that we have a default RFC 2047 charset (see above), the code in Exim
2716 that creates RFC 2047 encoded "words" labels them as that charset instead
2717 of always using iso-8859-1. The cases are (i) the explicit ${rfc2047:
2718 expansion operator; (ii) when Exim creates a From: line for a local
2719 message; (iii) when a header line is rewritten to include a "phrase" part.
2721 44. Nasty bug in exiqsumm: the regex to skip already-delivered addresses was
2722 buggy, causing it to skip the first lines of messages whose message ID
2723 ended in 'D'. This would not have bitten before Exim release 4.14, because
2724 message IDs were unlikely to end in 'D' before then. The effect was to have
2725 incorrect size information for certain domains.
2727 45. #include "config.h" was missing at the start of the crypt16.c module. This
2728 caused trouble on Tru64 (aka OSF1) systems, because HAVE_CRYPT16 was not
2731 46. If there was a timeout during a "random" callout check, Exim treated it as
2732 a failure of the random address, and carried on sending RSET and the real
2733 address. If the delay was just some slowness somewhere, the response to the
2734 original RCPT would be taken as a response to RSET and so on, causing
2735 mayhem of various kinds.
2737 47. Change 50 for 4.20 was a heap of junk. I don't know what I was thinking
2738 when I implemented it. It didn't allow for the fact that some option values
2739 may legitimatetly be negative (e.g. size_addition), and it didn't even do
2740 the right test for positive values.
2742 48. Domain names in DNS records are case-independent. Exim always looks them up
2743 in lower case. Some resolvers return domain names in exactly the case they
2744 appear in the zone file, that is, they may contain uppercase letters. Not
2745 all resolvers do this - some return always lower case. Exim was treating a
2746 change of case by a resolver as a change of domain, similar to a widening
2747 of a domain abbreviation. This triggered its re-routing code and so it was
2748 trying to route what was effectively the same domain again. This normally
2749 caused routing to fail (because the router wouldn't handle the domain
2750 twice). Now Exim checks for this case specially, and just changes the
2751 casing of the domain that it ultimately uses when it transmits the message
2754 49. Added Sieve (RFC 3028) support, courtesy of Michael Haardt's contributed
2757 50. If a filter generated a file delivery with a non-absolute name (possible if
2758 no home directory exists for the router), the forbid_file option was not
2761 51. Added '&' feature to dnslists, to provide bit mask matching in addition to
2762 the existing equality matching.
2764 52. Exim was using ints instead of ino_t variables in some places where it was
2765 dealing with inode numbers.
2767 53. If TMPDIR is defined in Local/Makefile (default in src/EDITME is
2768 TMPDIR="/tmp"), Exim checks for the presence of an environment variable
2769 called TMPDIR, and if it finds it is different, it changes its value.
2771 54. The smtp_printf() function is now made available to local_scan() so
2772 additional output lines can be written before returning. There is also an
2773 smtp_fflush() function to enable the detection of a dropped connection.
2774 The variables smtp_input and smtp_batched_input are exported to
2777 55. Changed the default runtime configuration: the message "Unknown user"
2778 has been removed from the ACL, and instead placed on the localuser router,
2779 using the cannot_route_message feature. This means that any verification
2780 failures that generate their own messages won't get overridden. Similarly,
2781 the "Unrouteable address" message that was in the ACL for unverifiable
2782 relay addresses has also been removed.
2784 56. Added hosts_avoid_esmtp to the smtp transport.
2786 57. The exicyclog script was not checking for the esoteric option
2787 CONFIGURE_FILE_USE_EUID in the Local/Makefile. It now does this, but it
2788 will work only if exicyclog is run under the appropriate euid.
2790 58. Following a discussion on the list, the rules by which Exim recognises line
2791 endings on incoming messages have been changed. The -dropcr and drop_cr
2792 options are now no-ops, retained only for backwards compatibility. The
2793 following line terminators are recognized: LF CRLF CR. However, special
2794 processing applies to CR:
2796 (i) The sequence CR . CR does *not* terminate an incoming SMTP message,
2797 nor a local message in the state where . is a terminator.
2799 (ii) If a bare CR is encountered in a header line, an extra space is added
2800 after the line terminator so as not to end the header. The reasoning
2801 behind this is that bare CRs in header lines are most likely either
2802 to be mistakes, or people trying to play silly games.
2804 59. The size of a message, as listed by "-bp" or in the Exim monitor window,
2805 was being incorrectly given as 18 bytes larger than it should have been.
2806 This is a VOB (very old bug).
2808 60. This may never have affected anything current, but just in case it has:
2809 When the local host is found other than at the start of a list of hosts,
2810 the local host, those with the same MX, and any that follow, are discarded.
2811 When the list in question was part of a longer list of hosts, the following
2812 hosts (not currently being processed) were also being discarded. This no
2813 longer happens. I'm not sure if this situation could ever has previously
2816 61. Added the "/MX" feature to lists of hosts in the manualroute and query
2819 62. Whenever Exim generates a new message, it now adds an Auto-Submitted:
2820 header. This is something that is recommended in a new Internet Draft, and
2821 is something that is documented as being done by Sendmail. There are two
2822 possible values. For messages generated by the autoreply transport, Exim
2825 Auto-Submitted: auto-replied
2827 whereas for all other generated messages (e.g. bounces) it adds
2829 Auto-Submitted: auto-generated
2831 63. The "personal" condition in filters now includes a test for the
2832 Auto-Submitted: header. If it contains the string "auto-" the message it
2833 not considered personal.
2835 64. Added rcpt_include_affixes as a generic transport option.
2837 65. Added queue_only_override (default true).
2839 66. Added the syslog_duplication option.
2841 67. If what should have been the first header line of a message consisted of
2842 a space followed by a colon, Exim was mis-interpreting it as a header line.
2843 It isn't of course - it is syntactically invalid and should therefore be
2844 treated as the start of the message body. The misbehaviour could have
2845 caused a number of strange effects, including loss of data in subsequent
2846 header lines, and spool format errors.
2848 68. Formerly, the AUTH parameter on a MAIL command was trusted only if the
2849 client host had authenticated. This control can now be exercised by an ACL
2850 for more flexibility.
2852 69. By default, callouts do not happen when testing with -bh. There is now a
2853 variant, -bhc, which does actually run the callout code, including
2854 consulting and updating the callout cache.
2856 70. Added support for saslauthd authentication, courtesy of Alexander
2859 71. If statvfs() failed on the spool or log directories while checking their
2860 size for availability, Exim confusingly gave the error "space shortage".
2861 Furthermore, in debugging mode it crashed with a floating point exception.
2862 These checks are done if check_{spool,log}_{space,inodes} are set, and when
2863 an SMTP message arrives with SIZE= on the MAIL command. As this is a really
2864 serious problem, Exim now writes to the main and panic logs when this
2865 happens, with details of the failure. It then refuses to accept the
2866 incoming message, giving the message "spool directory problem" or "log
2867 directory problem" with a 421 code for SMTP messages.
2869 72. When Exim is about to re-exec itself, it ensures that the file descriptors
2870 0, 1, and 2 exist, because some OS complain for execs without them (see
2871 ChangeLog 4.05/30). If necessary, Exim opens /dev/null to use for these
2872 descriptors. However, the code omitted to check that the open succeeded,
2873 causing mysterious errors if for some reason the permissions on /dev/null
2874 got screwed. Now Exim writes a message to the main and panic logs, and
2875 bombs out if it can't open /dev/null.
2877 73. Re-vamped the way daemon_smtp_port, local_interfaces, and -oX work and
2878 interact so that it is all more flexible. It is supposed to remain
2879 backwards compatible. Also added extra_local_interfaces.
2881 74. Invalid data sent to a SPA (NTLM) server authenticator could cause the code
2882 to bomb out with an assertion failure - to the client this appears as a
2883 connection drop. This problem occurs in the part of the code that was taken
2884 from the Samba project. Fortunately, the assertion is in a very simple
2885 function, so I have fixed this by reproducing the function inline in the
2886 one place where it is called, and arranging for authentication to fail
2887 instead of killing the process with assert().
2889 75. The SPA client code was not working when the server requested OEM rather
2890 than Unicode encoding.
2892 76. Added code to make require_files with a specific uid setting more usable in
2893 the case where statting the file as root fails - usually a non-root-mounted
2894 NFS file system. When this happens and the failure is EACCES, Exim now
2895 forks a subprocess and does the per-uid checking as the relevant uid.
2897 77. Added process_log_path.
2899 78. If log_file_path was not explicitly set, a setting of check_log_space or
2900 check_log_inodes was ignored.
2902 79. If a space check for the spool or log partitions fails, the incident is now
2903 logged. Of course, in the latter case the data may get lost...
2905 80. Added the %p formatting code to string_format() so that it can be used to
2906 print addresses in debug_print(). Adjusted all the address printing in the
2907 debugging in store.c to use %p rather than %d.
2909 81. There was a concern that a line of code in smtp_in.c could overflow a
2910 buffer if a HELO/EHLO command was given followed by 500 or so spaces. As
2911 initially expressed, the concern was not well-founded, because trailing
2912 spaces are removed early. However, if the trailing spaces were followed by
2913 a NULL, they did not get removed, so the overflow was possible. Two fixes
2916 (a) I re-wrote the offending code in a cleaner fashion.
2917 (b) If an incoming SMTP command contains a NULL character, it is rejected
2920 82. When Exim changes uid/gid to the Exim user at daemon start time, it now
2921 runs initgroups(), so that if the Exim user is in any additional groups,
2922 they will be used during message reception.
2928 The change log for 4.20 and earlier releases has been archived.