1 $Cambridge: exim/doc/doc-txt/ChangeLog,v 1.137 2005/05/17 09:53:34 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.
19 PH/02 Reduce the amount of output that "make" produces by default. Full output
20 can still be requested.
26 TK/01 Added Yahoo DomainKeys support via libdomainkeys. See
27 doc/experimental-spec.txt for details. (http://domainkeys.sf.net)
29 TK/02 Fix ACL "control" statement not being available in MIME ACL.
31 TK/03 Fix ACL "regex" condition not being available in MIME ACL.
33 PH/01 Installed a patch from the Sieve maintainer that allows -bf to be used
34 to test Sieve filters that use "vacation".
36 PH/02 Installed a slightly modified version of Nikos Mavrogiannopoulos' patch
37 that changes the way the GnuTLS parameters are stored in the cache file.
38 The new format can be generated externally. For backward compatibility,
39 if the data in the cache doesn't make sense, Exim assumes it has read an
40 old-format file, and it generates new data and writes a new file. This
41 means that you can't go back to an older release without removing the
44 PH/03 A redirect router that has both "unseen" and "one_time" set does not
45 work if there are any delivery delays because "one_time" forces the
46 parent to be marked "delivered", so its unseen clone is never tried
47 again. For this reason, Exim now forbids the simultaneous setting of
50 PH/04 Change 4.11/85 fixed an obscure bug concerned with addresses that are
51 redirected to themselves ("homonym" addresses). Read the long ChangeLog
52 entry if you want to know the details. The fix, however, neglected to
53 consider the case when local delivery batching is involved. The test for
54 "previously delivered" was not happening when checking to see if an
55 address could be batched with a previous (undelivered) one; under
56 certain circumstances this could lead to multiple deliveries to the same
59 PH/05 Renamed the macro SOCKLEN_T as EXIM_SOCKLEN_T because AIX uses SOCKLEN_T
60 in its include files, and this causes problems building Exim.
62 PH/06 A number of "verify =" ACL conditions have no options (e.g. verify =
63 header_syntax) but Exim was just ignoring anything given after a slash.
64 In particular, this caused confusion with an attempt to use "verify =
65 reverse_host_lookup/defer_ok". An error is now given when options are
66 supplied for verify items that do not have them. (Maybe reverse_host_
67 lookup should have a defer_ok option, but that's a different point.)
69 PH/07 Increase the size of the buffer for incoming SMTP commands from 512 (as
70 defined by RFC 821) to 2048, because there were problems with some AUTH
71 commands, and RFC 1869 says the size should be increased for extended
72 SMTP commands that take arguments.
74 PH/08 Added ${dlfunc dynamically loaded function for expansion (code from Tony
77 PH/09 Previously, an attempt to use ${perl when it wasn't compiled gave an
78 "unknown" error; now it says that the functionality isn't in the binary.
80 PH/10 Added a nasty fudge to try to recognize and flatten LDAP passwords in
81 an address' error message when a string expansion fails (syntax or
82 whatever). Otherwise the password may appear in the log. Following change
83 PH/42 below, there is no longer a chance of it appearing in a bounce
86 PH/11 Installed exipick version 20050225.0 from John Jetmore.
88 PH/12 If the last host in a fallback_hosts list was multihomed, only the first
89 of its addresses was ever tried. (Bugzilla bug #2.)
91 PH/13 If "headers_add" in a transport didn't end in a newline, Exim printed
92 the result incorrectly in the debug output. (It correctly added a newline
93 to what was transported.)
95 TF/01 Added $received_time.
97 PH/14 Modified the default configuration to add an acl_smtp_data ACL, with
98 commented out examples of how to interface to a virus scanner and to
99 SpamAssassin. Also added commented examples of av_scanner and
100 spamd_address settings.
102 PH/15 Further to TK/02 and TK/03 above, tidied up the tables of what conditions
103 and controls are allowed in which ACLs. There were a couple of minor
104 errors. Some of the entries in the conditions table (which is a table of
105 where they are NOT allowed) were getting very unwieldy; rewrote them as a
106 negation of where the condition IS allowed.
108 PH/16 Installed updated OS/os.c-cygwin from the Cygwin maintainer.
110 PH/17 The API for radiusclient changed at release 0.4.0. Unfortunately, the
111 header file does not have a version number, so I've had to invent a new
112 value for RADIUS_LIB_TYPE, namely "RADIUSCLIENTNEW" to request the new
113 API. The code is untested by me (my Linux distribution still has 0.3.2 of
114 radiusclient), but it was contributed by a Radius user.
116 PH/18 Installed Lars Mainka's patch for the support of CRL collections in
117 files or directories, for OpenSSL.
119 PH/19 When an Exim process that is running as root has to create an Exim log
120 file, it does so in a subprocess that runs as exim:exim so as to get the
121 ownership right at creation (otherwise, other Exim processes might see
122 the file with the wrong ownership). There was no test for failure of this
123 fork() call, which would lead to the process getting stuck as it waited
124 for a non-existent subprocess. Forks do occasionally fail when resources
125 run out. I reviewed all the other calls to fork(); they all seem to check
128 PH/20 When checking for unexpected SMTP input at connect time (before writing
129 the banner), Exim was not dealing correctly with a non-positive return
130 from the read() function. If the client had disconnected by this time,
131 the result was a log entry for a synchronization error with an empty
132 string after "input=" when read() returned zero. If read() returned -1
133 (an event I could not check), uninitialized data bytes were printed.
134 There were reports of junk text (parts of files, etc) appearing after
137 PH/21 Added acl_not_smtp_mime to allow for MIME scanning for non-SMTP messages.
139 PH/22 Added support for macro redefinition, and (re)definition in between
140 driver and ACL definitions.
142 PH/23 The cyrus_sasl authenticator was expanding server_hostname, but then
143 forgetting to use the resulting value; it was using the unexpanded value.
145 PH/24 The cyrus_sasl authenticator was advertising mechanisms for which it
146 hadn't been configured. The fix is from Juergen Kreileder, who
147 understands it better than I do:
149 "Here's what I see happening with three configured cyrus_sasl
150 authenticators configured (plain, login, cram-md5):
152 On startup auth_cyrus_sasl_init() gets called for each of these.
153 This means three calls to sasl_listmech() without a specified mech_list.
154 => SASL tests which mechs of all available mechs actually work
155 => three warnings about OTP not working
156 => the returned list contains: plain, login, cram-md5, digest-md5, ...
158 With the patch, sasl_listmech() also gets called three times. But now
159 SASL's mech_list option is set to the server_mech specified in the the
160 authenticator. Or in other words, the answer from sasl_listmech()
161 gets limited to just the mech you're testing for (which is different
163 => the return list contains just 'plain' or 'login', 'cram-md5' or
164 nothing depending on the value of ob->server_mech.
166 I've just tested the patch: Authentication still works fine,
167 unavailable mechs specified in the exim configuration are still
168 caught, and the auth.log warnings about OTP are gone."
170 PH/25 When debugging is enabled, the contents of the command line are added
171 to the debugging output, even when log_selector=+arguments is not
174 PH/26 Change scripts/os-type so that when "uname -s" returns just "GNU", the
175 answer is "GNU", and only if the return is "GNU/something" is the answer
178 PH/27 $acl_verify_message is now set immediately after the failure of a
179 verification in an ACL, and so is available in subsequent modifiers. In
180 particular, the message can be preserved by coding like this:
182 warn !verify = sender
183 set acl_m0 = $acl_verify_message
185 Previously, $acl_verify_message was set only while expanding "message"
186 and "log_message" when a very denied access.
188 PH/28 Modified OS/os.c-Linux with
190 -#ifndef OS_LOAD_AVERAGE
191 +#if !defined(OS_LOAD_AVERAGE) && defined(__linux__)
193 to make Exim compile on kfreebsd-gnu. (I'm totally confused about the
194 nomenclature these days.)
196 PH/29 Installed patch from the Sieve maintainer that adds the options
197 sieve_useraddress and sieve_subaddress to the redirect router.
199 PH/30 In these circumstances:
200 . Two addresses routed to the same list of hosts;
201 . First host does not offer TLS;
202 . First host accepts first address;
203 . First host gives temporary error to second address;
204 . Second host offers TLS and a TLS session is established;
205 . Second host accepts second address.
206 Exim incorrectly logged both deliveries with the TLS parameters (cipher
207 and peerdn, if requested) that were in fact used only for the second
210 PH/31 When doing a callout as part of verifying an address, Exim was not paying
211 attention to any local part prefix or suffix that was matched by the
212 router that accepted the address. It now behaves in the same way as it
213 does for delivery: the affixes are removed from the local part unless
214 rcpt_include_affixes is set on the transport.
216 PH/32 Add the sender address, as F=<...>, to the log line when logging a
217 timeout during the DATA phase of an incoming message.
219 PH/33 Sieve envelope tests were broken for match types other than :is. I have
220 applied a patch sanctioned by the Sieve maintainer.
222 PH/34 Change 4.50/80 broke Exim in that it could no longer handle cases where
223 the uid or gid is negative. A case of a negative gid caused this to be
224 noticed. The fix allows for either to be negative.
226 PH/35 ACL_WHERE_MIME is now declared unconditionally, to avoid too much code
227 clutter, but the tables that are indexed by ACL_WHERE_xxx values had been
230 PH/36 The change PH/12 above was broken. Fixed it.
232 PH/37 Exim used to check for duplicate addresses in the middle of routing, on
233 the grounds that routing the same address twice would always produce the
234 same answer. This might have been true once, but it is certainly no
235 longer true now. Routing a child address may depend on the previous
236 routing that produced that child. Some complicated redirection strategies
237 went wrong when messages had multiple recipients, and made Exim's
238 behaviour dependent on the order in which the addresses were given.
240 I have moved the duplicate checking until after the routing is complete.
241 Exim scans the addresses that are assigned to local and remote
242 transports, and removes any duplicates. This means that more work will be
243 done, as duplicates will always all be routed, but duplicates are
244 presumably rare, so I don't expect this is of any significance.
246 For deliveries to pipes, files, and autoreplies, the duplicate checking
247 still happens during the routing process, since they are not going to be
250 PH/38 Installed a patch from Ian Freislich, with the agreement of Tom Kistner.
251 It corrects a timeout issue with spamd. This is Ian's comment: "The
252 background is that sometimes spamd either never reads data from a
253 connection it has accepted, or it never writes response data. The exiscan
254 spam.[ch] uses a 3600 second timeout on spamd socket reads, further, it
255 blindly assumes that writes won't block so it may never time out."
257 PH/39 Allow G after quota size as well as K and M.
259 PH/40 The value set for $authenticated_id in an authenticator may not contain
260 binary zeroes or newlines because the value is written to log lines and
261 to spool files. There was no check on this. Now the value is run through
262 the string_printing() function so that such characters are converted to
263 printable escape sequences.
265 PH/41 $message_linecount is a new variable that contains the total number of
266 lines in the message. Compare $body_linecount, which is the count for the
269 PH/42 Exim no longer gives details of delivery errors for specific addresses in
270 bounce and delay warning messages, except in certain special cases, which
273 (a) An SMTP error message from a remote host;
274 (b) A message specified in a :fail: redirection;
275 (c) A message specified in a "fail" command in a system filter;
276 (d) A message specified in a FAIL return from the queryprogram router;
277 (e) A message specified by the cannot_route_message router option.
279 In these cases only, Exim does include the error details in bounce and
280 warning messages. There are also a few cases where bland messages such
281 as "unrouteable address" or "local delivery error" are given.
283 PH/43 $value is now also set for the "else" part of a ${run expansion.
285 PH/44 Applied patch from the Sieve maintainer: "The vacation draft is still
286 being worked on, but at least Exim now implements the latest version to
289 PH/45 In a pipe transport, although a timeout while waiting for the pipe
290 process to complete was treated as a delivery failure, a timeout while
291 writing the message to the pipe was logged, but erroneously treated as a
292 successful delivery. Such timeouts include transport filter timeouts. For
293 consistency with the overall process timeout, these timeouts are now
294 treated as errors, giving rise to delivery failures by default. However,
295 there is now a new Boolean option for the pipe transport called
296 timeout_defer, which, if set TRUE, converts the failures into defers for
297 both kinds of timeout. A transport filter timeout is now identified in
300 PH/46 The "scripts/Configure-config.h" script calls "make" at one point. On
301 systems where "make" and "gmake" are different, calling "gmake" at top
302 level broke things. I've arranged for the value of $(MAKE) to be passed
303 from the Makefile to this script so that it can call the same version of
307 A note about Exim versions 4.44 and 4.50
308 ----------------------------------------
310 Exim 4.50 was meant to be the next release after 4.43. It contains a lot of
311 changes of various kinds. As a consequence, a big documentation update was
312 needed. This delayed the release for rather longer than seemed good, especially
313 in the light of a couple of (minor) security issues. Therefore, the changes
314 that fixed bugs were backported into 4.43, to create a 4.44 maintenance
315 release. So 4.44 and 4.50 are in effect two different branches that both start
318 I have left the 4.50 change log unchanged; it contains all the changes since
319 4.43. The change log for 4.44 is below; many of its items are identical to
320 those for 4.50. This seems to be the most sensible way to preserve the
321 historical information.
327 1. Minor wording change to the doc/README.SIEVE file.
329 2. Change 4.43/35 introduced a bug: if quota_filecount was set, the
330 computation of the current number of files was incorrect.
332 3. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
333 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
336 4. Give more explanation in the error message when the command for a transport
337 filter fails to execute.
339 5. There are several places where Exim runs a non-Exim command in a
340 subprocess. The SIGUSR1 signal should be disabled for these processes. This
341 was being done only for the command run by the queryprogram router. It is
342 now done for all such subprocesses. The other cases are: ${run, transport
343 filters, and the commands run by the lmtp and pipe transports.
345 6. Added CONFIGURE_GROUP build-time option.
347 7. Some older OS have a limit of 256 on the maximum number of file
348 descriptors. Exim was using setrlimit() to set 1000 as a large value
349 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
350 systems. I've change it so that if it can't get 1000, it tries for 256.
352 8. "control=submission" was allowed, but had no effect, in a DATA ACL. This
353 was an oversight, and furthermore, ever since the addition of extra
354 controls (e.g. 4.43/32), the checks on when to allow different forms of
355 "control" were broken. There should now be diagnostics for all cases when a
356 control that does not make sense is encountered.
358 9. Added the /retain_sender option to "control=submission".
360 10. $recipients is now available in the predata ACL (oversight).
362 11. Tidy the search cache before the fork to do a delivery from a message
363 received from the command line. Otherwise the child will trigger a lookup
364 failure and thereby defer the delivery if it tries to use (for example) a
365 cached ldap connection that the parent has called unbind on.
367 12. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
368 of $address_data from the recipient verification was clobbered by the
371 13. The value of address_data from a sender verification is now available in
372 $sender_address_data in subsequent conditions in the ACL statement.
374 14. Added forbid_sieve_filter and forbid_exim_filter to the redirect router.
376 15. Added a new option "connect=<time>" to callout options, to set a different
379 16. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
380 was its contents. (It was OK if the option was not defined at all.)
382 17. A "Completed" log line is now written for messages that are removed from
383 the spool by the -Mrm option.
385 18. New variables $sender_verify_failure and $recipient_verify_failure contain
386 information about exactly what failed.
388 19. Added -dd to debug only the daemon process.
390 20. Incorporated Michael Haardt's patch to ldap.c for improving the way it
391 handles timeouts, both on the server side and network timeouts. Renamed the
392 CONNECT parameter as NETTIMEOUT (but kept the old name for compatibility).
394 21. The rare case of EHLO->STARTTLS->HELO was setting the protocol to "smtp".
395 It is now set to "smtps".
397 22. $host_address is now set to the target address during the checking of
400 23. When checking ignore_target_hosts for an ipliteral router, no host name was
401 being passed; this would have caused $sender_host_name to have been used if
402 matching the list had actually called for a host name (not very likely,
403 since this list is usually IP addresses). A host name is now passed as
406 24. Changed the calls that set up the SIGCHLD handler in the daemon to use the
407 code that specifies a non-restarting handler (typically sigaction() in
408 modern systems) in an attempt to fix a rare and obscure crash bug.
410 25. Narrowed the window for a race in the daemon that could cause it to ignore
411 SIGCHLD signals. This is not a major problem, because they are used only to
412 wake it up if nothing else does.
414 26. A malformed maildirsize file could cause Exim to calculate negative values
415 for the mailbox size or file count. Odd effects could occur as a result.
416 The maildirsize information is now recalculated if the size or filecount
419 27. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
420 support for a long time. Removed HAVE_SYS_VFS_H.
422 28. Installed the latest version of exipick from John Jetmore.
424 29. In an address list, if the pattern was not a regular expression, an empty
425 subject address (from a bounce message) matched only if the pattern was an
426 empty string. Non-empty patterns were not even tested. This was the wrong
427 because it is perfectly reasonable to use an empty address as part of a
428 database query. An empty address is now tested by patterns that are
429 lookups. However, all the other forms of pattern expect the subject to
430 contain a local part and a domain, and therefore, for them, an empty
431 address still always fails if the pattern is not itself empty.
433 30. Exim went into a mad DNS loop when attempting to do a callout where the
434 host was specified on an smtp transport, and looking it up yielded more
437 31. Re-factored the code for checking spool and log partition space into a
438 function that finds that data and another that does the check. The former
439 is then used to implement four new variables: $spool_space, $log_space,
440 $spool_inodes, and $log_inodes.
442 32. The RFC2047 encoding function was originally intended for short strings
443 such as real names; it was not keeping to the 75-character limit for
444 encoded words that the RFC imposes. It now respects the limit, and
445 generates multiple encoded words if necessary. To be on the safe side, I
446 have increased the buffer size for the ${rfc2047: expansion operator from
449 33. It is now permitted to omit both strings after an "if" condition; if the
450 condition is true, the result is "true". As before, when the second string
451 is omitted, a false condition yields an empty string. This makes it less
452 cumbersome to write custom ACL and router conditions.
454 34. Failure to deliver a bounce message always caused it to be frozen, even if
455 there was an errors_to setting on the router. The errors_to setting is now
458 35. If an IPv6 address is given for -bh or -bhc, it is now converted to the
459 canonical form (fully expanded) before being placed in
460 $sender_host_address.
462 36. The table in the code that translates DNS record types into text (T_A to
463 "A" for instance) was missing entries for NS and CNAME. It is just possible
464 that this could have caused confusion if both these types were looked up
465 for the same domain, because the text type is used as part of Exim's
466 per-process caching. But the chance of anyone hitting this buglet seems
469 37. The dnsdb lookup has been extended in a number of ways.
471 (1) There is a new type, "zns", which walks up the domain tree until it
472 finds some nameserver records. It should be used with care.
474 (2) There is a new type, "mxh", which is like "mx" except that it returns
475 just the host names, not the priorities.
477 (3) It is now possible to give a list of domains (or IP addresses) to be
478 looked up. The behaviour when one of the lookups defers can be
479 controlled by a keyword.
481 (4) It is now possible to specify the separator character for use when
482 multiple records are returned.
484 38. The dnslists ACL condition has been extended: it is now possible to supply
485 a list of IP addresses and/or domains to be looked up in a particular DNS
488 39. Added log_selector=+queue_time_overall.
490 40. When running the queue in the test harness, wait just a tad after forking a
491 delivery process, to get repeatability of debugging output.
493 41. Include certificate and key file names in error message when GnuTLS fails
494 to set them up, because the GnuTLS error message doesn't include the name
495 of the failing file when there is a problem reading it.
497 42. Allow both -bf and -bF in the same test run.
499 43. Did the same fix as 41 above for OpenSSL, which had the same infelicity.
501 44. The "Exiscan patch" is now merged into the mainline Exim source.
503 45. Sometimes the final signoff response after QUIT could fail to get
504 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
505 < 0 before doing a fflush(). This bug looks as though it goes back to the
506 introduction of TLS in release 3.20, but "sometimes" must have been rare
507 because the tests only now provoked it.
509 46. Reset the locale to "C" after calling embedded Perl, in case it was changed
510 (this can affect the format of dates).
512 47. exim_tidydb, when checking for the continued existence of a message for
513 which it has found a message-specific retry record, was not finding
514 messages that were in split spool directories. Consequently, it was
515 deleting retry records that should have stayed in existence.
517 48. Steve fixed some bugs in eximstats.
519 49. The SPA authentication driver was not abandoning authentication and moving
520 on to the next authenticator when an expansion was forced to fail,
521 contradicting the general specification for all authenticators. Instead it
522 was generating a temporary error. It now behaves as specified.
524 50. The default ordering of permitted cipher suites for GnuTLS was pessimal
525 (the order specifies the preference for clients). The order is now AES256,
526 AES128, 3DES, ARCFOUR128.
528 51. Small patch to Sieve code - explicitly set From: when generating an
531 52. Exim crashed if a remote delivery caused a very long error message to be
532 recorded - for instance if somebody sent an entire SpamAssassin report back
533 as a large number of 550 error lines. This bug was coincidentally fixed by
534 increasing the size of one of Exim's internal buffers (big_buffer) that
535 happened as part of the Exiscan merge. However, to be on the safe side, I
536 have made the code more robust (and fixed the comments that describe what
539 53. Now that there can be additional text after "Completed" in log lines (if
540 the queue_time_overall log selector is set), a one-byte patch to exigrep
541 was needed to allow it to recognize "Completed" as not the last thing in
544 54. The LDAP lookup was not handling a return of LDAP_RES_SEARCH_REFERENCE. A
545 patch that reportedly fixes this has been added. I am not expert enough to
546 create a test for it. This is what the patch creator wrote:
548 "I found a little strange behaviour of ldap code when working with
549 Windows 2003 AD Domain, where users was placed in more than one
550 Organization Units. When I tried to give exim partial DN, the exit code
551 of ldap_search was unknown to exim because of LDAP_RES_SEARCH_REFERENCE.
552 But simultaneously result of request was absolutely normal ldap result,
553 so I produce this patch..."
555 Later: it seems that not all versions of LDAP support LDAP_RES_SEARCH_
556 REFERENCE, so I have modified the code to exclude the patch when that macro
559 55. Some experimental protocols are using DNS PTR records for new purposes. The
560 keys for these records are domain names, not reversed IP addresses. The
561 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
562 leaves it alone. Component reversal etc. now happens only for IP addresses.
565 56. Improve error message when ldap_search() fails in OpenLDAP or Solaris LDAP.
567 57. Double the size of the debug message buffer (to 2048) so that more of very
568 long debug lines gets shown.
570 58. The exicyclog utility now does better if the number of log files to keep
571 exceeds 99. In this case, it numbers them 001, 002 ... instead of 01, 02...
573 59. Two changes related to the smtp_active_hostname option:
575 (1) $smtp_active_hostname is now available as a variable.
576 (2) The default for smtp_banner uses $smtp_active_hostname instead
577 of $primary_hostname.
579 60. The host_aton() function is supposed to be passed a string that is known
580 to be a valid IP address. However, in the case of IPv6 addresses, it was
581 not checking this. This is a hostage to fortune. Exim now panics and dies
582 if the condition is not met. A case was found where this could be provoked
583 from a dnsdb PTR lookup with an IPv6 address that had more than 8
584 components; fortuitously, this particular loophole had already been fixed
585 by change 4.50/55 above.
587 If there are any other similar loopholes, the new check in host_aton()
588 itself should stop them being exploited. The report I received stated that
589 data on the command line could provoke the exploit when Exim was running as
590 exim, but did not say which command line option was involved. All I could
591 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
595 61. There was a buffer overflow vulnerability in the SPA authentication code
596 (which came originally from the Samba project). I have added a test to the
597 spa_base64_to_bits() function which I hope fixes it.
600 62. Configuration update for GNU/Hurd and variations. Updated Makefile-GNU and
601 os.h-GNU, and added configuration files for GNUkFreeBSD and GNUkNetBSD.
603 63. The daemon start-up calls getloadavg() while still root for those OS that
604 need the first call to be done as root, but it missed one case: when
605 deliver_queue_load_max is set with deliver_drop_privilege. This is
606 necessary for the benefit of the queue runner, because there is no re-exec
607 when deliver_drop_privilege is set.
609 64. A call to exiwhat cut short delays set up by "delay" modifiers in ACLs.
612 65. Caching of lookup data for "hosts =" ACL conditions, when a named host list
613 was in use, was not putting the data itself into the right store pool;
614 consequently, it could be overwritten for a subsequent message in the same
615 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
618 66. Added hosts_max_try_hardlimit to the smtp transport, default 50.
620 67. The string_is_ip_address() function returns 0, 4, or 6, for "no an IP
621 address", "IPv4 address", and "IPv6 address", respectively. Some calls of
622 the function were treating the return as a boolean value, which happened to
623 work because 0=false and not-0=true, but is not correct code.
625 68. The host_aton() function was not handling scoped IPv6 addresses (those
626 with, for example, "%eth0" on the end) correctly.
628 69. Fixed some compiler warnings in acl.c for the bitmaps specified with
629 negated items (that is, ~something) in unsigned ints. Some compilers
630 apparently mutter when there is no cast.
632 70. If an address verification called from an ACL failed, and did not produce a
633 user-specific message (i.e. there was only a "system" message), nothing was
634 put in $acl_verify_message. In this situation, it now puts the system
637 71. Change 4.23/11 added synchronization checking at the start of an SMTP
638 session; change 4.31/43 added the unwanted input to the log line - except
639 that it did not do this in the start of session case. It now does.
641 72. After a timeout in a callout SMTP session, Exim still sent a QUIT command.
642 This is wrong and can cause the other end to generate a synchronization
643 error if it is another Exim or anything else that does the synchronization
644 check. A QUIT command is no longer sent after a timeout.
646 73. $host_lookup_deferred has been added, to make it easier to detect DEFERs
649 74. The defer_ok option of callout verification was not working if it was used
650 when verifying addresses in header lines, that is, for this case:
652 verify = header_sender/callout=defer_ok
654 75. A backgrounded daemon closed stdin/stdout/stderr on entry; this meant that
655 those file descriptors could be used for SMTP connections. If anything
656 wrote to stderr (the example that came up was "warn" in embedded Perl), it
657 could be sent to the SMTP client, causing chaos. The daemon now opens
658 stdin, stdout, and stderr to /dev/null when it puts itself into the
661 76. Arrange for output from Perl's "warn" command to be written to Exim's main
662 log by default. The user can override this with suitable Perl magic.
664 77. The use of log_message on a "discard" ACL verb, which is supposed to add to
665 the log message when discard triggers, was not working for the DATA ACL or
666 for the non-SMTP ACL.
668 78. Error message wording change in sieve.c.
670 79. If smtp_accept_max_per_host was set, the number of connections could be
671 restricted to fewer than expected, because the daemon was trying to set up
672 a new connection before checking whether the processes handling previous
673 connections had finished. The check for completed processes is now done
674 earlier. On busy systems, this bug wouldn't be noticed because something
675 else would have woken the daemon, and it would have reaped the completed
678 80. If a message was submitted locally by a user whose login name contained one
679 or more spaces (ugh!), the spool file that Exim wrote was not re-readable.
680 It caused a spool format error. I have fixed the spool reading code. A
681 related problem was that the "from" clause in the Received: line became
682 illegal because of the space(s). It is now covered by ${quote_local_part.
684 81. Included the latest eximstats from Steve (adds average sizes to HTML Top
687 82. Updated OS/Makefile-AIX as per message from Mike Meredith.
689 83. Patch from Sieve maintainer to fix unterminated string problem in
692 84. Some minor changes to the Linux configuration files to help with other
693 OS variants using glibc.
695 85. One more patch for Sieve to update vacation handling to latest spec.
698 ----------------------------------------------------
699 See the note above about the 4.44 and 4.50 releases.
700 ----------------------------------------------------
706 1. Change 4.43/35 introduced a bug that caused file counts to be
707 incorrectly computed when quota_filecount was set in an appendfile
710 2. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
711 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
714 3. Give more explanation in the error message when the command for a transport
715 filter fails to execute.
717 4. There are several places where Exim runs a non-Exim command in a
718 subprocess. The SIGUSR1 signal should be disabled for these processes. This
719 was being done only for the command run by the queryprogram router. It is
720 now done for all such subprocesses. The other cases are: ${run, transport
721 filters, and the commands run by the lmtp and pipe transports.
723 5. Some older OS have a limit of 256 on the maximum number of file
724 descriptors. Exim was using setrlimit() to set 1000 as a large value
725 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
726 systems. I've change it so that if it can't get 1000, it tries for 256.
728 6. "control=submission" was allowed, but had no effect, in a DATA ACL. This
729 was an oversight, and furthermore, ever since the addition of extra
730 controls (e.g. 4.43/32), the checks on when to allow different forms of
731 "control" were broken. There should now be diagnostics for all cases when a
732 control that does not make sense is encountered.
734 7. $recipients is now available in the predata ACL (oversight).
736 8. Tidy the search cache before the fork to do a delivery from a message
737 received from the command line. Otherwise the child will trigger a lookup
738 failure and thereby defer the delivery if it tries to use (for example) a
739 cached ldap connection that the parent has called unbind on.
741 9. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
742 of $address_data from the recipient verification was clobbered by the
745 10. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
746 was its contents. (It was OK if the option was not defined at all.)
748 11. A "Completed" log line is now written for messages that are removed from
749 the spool by the -Mrm option.
751 12. $host_address is now set to the target address during the checking of
754 13. When checking ignore_target_hosts for an ipliteral router, no host name was
755 being passed; this would have caused $sender_host_name to have been used if
756 matching the list had actually called for a host name (not very likely,
757 since this list is usually IP addresses). A host name is now passed as
760 14. Changed the calls that set up the SIGCHLD handler in the daemon to use the
761 code that specifies a non-restarting handler (typically sigaction() in
762 modern systems) in an attempt to fix a rare and obscure crash bug.
764 15. Narrowed the window for a race in the daemon that could cause it to ignore
765 SIGCHLD signals. This is not a major problem, because they are used only to
766 wake it up if nothing else does.
768 16. A malformed maildirsize file could cause Exim to calculate negative values
769 for the mailbox size or file count. Odd effects could occur as a result.
770 The maildirsize information is now recalculated if the size or filecount
773 17. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
774 support for a long time. Removed HAVE_SYS_VFS_H.
776 18. Updated exipick to current release from John Jetmore.
778 19. Allow an empty sender to be matched against a lookup in an address list.
779 Previously the only cases considered were a regular expression, or an
782 20. Exim went into a mad DNS lookup loop when doing a callout where the
783 host was specified on the transport, if the DNS lookup yielded more than
786 21. The RFC2047 encoding function was originally intended for short strings
787 such as real names; it was not keeping to the 75-character limit for
788 encoded words that the RFC imposes. It now respects the limit, and
789 generates multiple encoded words if necessary. To be on the safe side, I
790 have increased the buffer size for the ${rfc2047: expansion operator from
793 22. Failure to deliver a bounce message always caused it to be frozen, even if
794 there was an errors_to setting on the router. The errors_to setting is now
797 23. If an IPv6 address is given for -bh or -bhc, it is now converted to the
798 canonical form (fully expanded) before being placed in
799 $sender_host_address.
801 24. Updated eximstats to version 1.33
803 25. Include certificate and key file names in error message when GnuTLS fails
804 to set them up, because the GnuTLS error message doesn't include the name
805 of the failing file when there is a problem reading it.
807 26. Expand error message when OpenSSL has problems setting up cert/key files.
810 27. Reset the locale to "C" after calling embedded Perl, in case it was changed
811 (this can affect the format of dates).
813 28. exim_tidydb, when checking for the continued existence of a message for
814 which it has found a message-specific retry record, was not finding
815 messages that were in split spool directories. Consequently, it was
816 deleting retry records that should have stayed in existence.
818 29. eximstats updated to version 1.35
819 1.34 - allow eximstats to parse syslog lines as well as mainlog lines
820 1.35 - bugfix such that pie charts by volume are generated correctly
822 30. The SPA authentication driver was not abandoning authentication and moving
823 on to the next authenticator when an expansion was forced to fail,
824 contradicting the general specification for all authenticators. Instead it
825 was generating a temporary error. It now behaves as specified.
827 31. The default ordering of permitted cipher suites for GnuTLS was pessimal
828 (the order specifies the preference for clients). The order is now AES256,
829 AES128, 3DES, ARCFOUR128.
831 31. Small patch to Sieve code - explicitly set From: when generating an
834 32. Exim crashed if a remote delivery caused a very long error message to be
835 recorded - for instance if somebody sent an entire SpamAssassin report back
836 as a large number of 550 error lines. This bug was coincidentally fixed by
837 increasing the size of one of Exim's internal buffers (big_buffer) that
838 happened as part of the Exiscan merge. However, to be on the safe side, I
839 have made the code more robust (and fixed the comments that describe what
842 33. Some experimental protocols are using DNS PTR records for new purposes. The
843 keys for these records are domain names, not reversed IP addresses. The
844 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
845 leaves it alone. Component reversal etc. now happens only for IP addresses.
848 34. The host_aton() function is supposed to be passed a string that is known
849 to be a valid IP address. However, in the case of IPv6 addresses, it was
850 not checking this. This is a hostage to fortune. Exim now panics and dies
851 if the condition is not met. A case was found where this could be provoked
852 from a dnsdb PTR lookup with an IPv6 address that had more than 8
853 components; fortuitously, this particular loophole had already been fixed
854 by change 4.50/55 or 4.44/33 above.
856 If there are any other similar loopholes, the new check in host_aton()
857 itself should stop them being exploited. The report I received stated that
858 data on the command line could provoke the exploit when Exim was running as
859 exim, but did not say which command line option was involved. All I could
860 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
864 35. There was a buffer overflow vulnerability in the SPA authentication code
865 (which came originally from the Samba project). I have added a test to the
866 spa_base64_to_bits() function which I hope fixes it.
869 36. The daemon start-up calls getloadavg() while still root for those OS that
870 need the first call to be done as root, but it missed one case: when
871 deliver_queue_load_max is set with deliver_drop_privilege. This is
872 necessary for the benefit of the queue runner, because there is no re-exec
873 when deliver_drop_privilege is set.
875 37. Caching of lookup data for "hosts =" ACL conditions, when a named host list
876 was in use, was not putting the data itself into the right store pool;
877 consequently, it could be overwritten for a subsequent message in the same
878 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
881 38. Sometimes the final signoff response after QUIT could fail to get
882 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
883 < 0 before doing a fflush(). This bug looks as though it goes back to the
884 introduction of TLS in release 3.20, but "sometimes" must have been rare
885 because the tests only now provoked it.
891 1. Fixed a longstanding but relatively impotent bug: a long time ago, before
892 PIPELINING, the function smtp_write_command() used to return TRUE or FALSE.
893 Now it returns an integer. A number of calls were still expecting a T/F
894 return. Fortuitously, in all cases, the tests worked in OK situations,
895 which is the norm. However, things would have gone wrong on any write
896 failures on the smtp file descriptor. This function is used when sending
897 messages over SMTP and also when doing verify callouts.
899 2. When Exim is called to do synchronous delivery of a locally submitted
900 message (the -odf or -odi options), it no longer closes stderr before doing
903 3. Implemented the mua_wrapper option.
905 4. Implemented mx_fail_domains and srv_fail_domains for the dnslookup router.
907 5. Implemented the functions header_remove(), header_testname(),
908 header_add_at_position(), and receive_remove_recipient(), and exported them
911 6. If an ACL "warn" statement specified the addition of headers, Exim already
912 inserted X-ACL-Warn: at the start if there was no header name. However, it
913 was not making this test for the second and subsequent header lines if
914 there were newlines in the string. This meant that an invalid header could
915 be inserted if Exim was badly configured.
917 7. Allow an ACL "warn" statement to add header lines at the start or after all
918 the Received: headers, as well as at the end.
920 8. Added the rcpt_4xx retry error code.
922 9. Added postmaster_mailfrom=xxx to callout verification option.
924 10. Added mailfrom=xxxx to the callout verification option, for verify=
927 11. ${substr_1_:xxxx} and ${substr__3:xxxx} are now diagnosed as syntax errors
928 (they previously behaved as ${substr_1_0:xxxx} and ${substr:_0_3:xxxx}).
930 12. Inserted some casts to stop certain compilers warning when using pointer
931 differences as field lengths or precisions in printf-type calls (mostly
932 affecting debugging statements).
934 13. Added optional readline() support for -be (dynamically loaded).
936 14. Obscure bug fix: if a message error (e.g. 4xx to MAIL) happened within the
937 same clock tick as a message's arrival, so that its received time was the
938 same as the "first fail" time on the retry record, and that message
939 remained on the queue past the ultimate address timeout, every queue runner
940 would try a delivery (because it was past the ultimate address timeout) but
941 after another failure, the ultimate address timeout, which should have then
942 bounced the address, did not kick in. This was a "< instead of <=" error;
943 in most cases the first failure would have been in the next clock tick
944 after the received time, and all would be well.
946 15. The special items beginning with @ in domain lists (e.g. @mx_any) were not
947 being recognized when the domain list was tested by the match_domain
948 condition in an expansion string.
950 16. Added the ${str2b64: operator.
952 17. Exim was always calling setrlimit() to set a large limit for the number of
953 processes, without checking whether the existing limit was already
954 adequate. (It did check for the limit on file descriptors.) Furthermore,
955 errors from getrlimit() and setrlimit() were being ignored. Now they are
956 logged to the main and panic logs, but Exim does carry on, to try to do its
957 job under whatever limits there are.
959 18. Imported PCRE 5.0.
961 19. Trivial typo in log message " temporarily refused connection" (the leading
964 20. If the log selector return_path_on_delivery was set and an address was
965 redirected to /dev/null, the delivery process crashed because it assumed
966 that a return path would always be set for a "successful" delivery. In this
967 case, the whole delivery is bypassed as an optimization, and therefore no
970 21. Internal re-arrangement: the function for sending a challenge and reading
971 a response while authentication was assuming a zero-terminated challenge
972 string. It's now changed to take a pointer and a length, to allow for
973 binary data in such strings.
975 22. Added the cyrus_sasl authenticator (code supplied by MBM).
977 23. Exim was not respecting finduser_retries when seeking the login of the
978 uid under which it was called; it was always trying 10 times. (The default
979 setting of finduser_retries is zero.) Also, it was sleeping after the final
980 failure, which is pointless.
982 24. Implemented tls_on_connect_ports.
984 25. Implemented acl_smtp_predata.
986 26. If the domain in control=submission is set empty, Exim assumes that the
987 authenticated id is a complete email address when it generates From: or
988 Sender: header lines.
990 27. Added "#define SOCKLEN_T int" to OS/os.h-SCO and OS/os.h-SCO_SV. Also added
991 definitions to OS/Makefile-SCO and OS/Makefile-SCO_SV that put basename,
992 chown and chgrp in /bin and hostname in /usr/bin.
994 28. Exim was keeping the "process log" file open after each use, just as it
995 does for the main log. This opens the possibility of it remaining open for
996 long periods when the USR1 signal hits a daemon. Occasional processlog
997 errors were reported, that could have been caused by this. Anyway, it seems
998 much more sensible not to leave this file open at all, so that is what now
1001 29. The long-running daemon process does not normally write to the log once it
1002 has entered its main loop, and it closes the log before doing so. This is
1003 so that log files can straightforwardly be renamed and moved. However,
1004 there are a couple of unusual error situations where the daemon does write
1005 log entries, and I had neglected to close the log afterwards.
1007 30. The text of an SMTP error response that was received during a remote
1008 delivery was being truncated at 512 bytes. This is too short for some of
1009 the long messages that one sometimes sees. I've increased the limit to
1012 31. It is now possible to make retry rules that apply only when a message has a
1013 specific sender, in particular, an empty sender.
1015 32. Added "control = enforce_sync" and "control = no_enforce_sync". This makes
1016 it possible to be selective about when SMTP synchronization is enforced.
1018 33. Added "control = caseful_local_part" and "control = "caselower_local_part".
1020 32. Implemented hosts_connection_nolog.
1022 33. Added an ACL for QUIT.
1024 34. Setting "delay_warning=" to disable warnings was not working; it gave a
1027 35. Added mailbox_size and mailbox_filecount to appendfile.
1029 36. Added control = no_multiline_responses to ACLs.
1031 37. There was a bug in the logic of the code that waits for the clock to tick
1032 in the case where the clock went backwards by a substantial amount such
1033 that the microsecond fraction of "now" was more than the microsecond
1034 fraction of "then" (but the whole seconds number was less).
1036 38. Added support for the libradius Radius client library this is found on
1037 FreeBSD (previously only the radiusclient library was supported).
1043 1. When certain lookups returned multiple values in the form name=value, the
1044 quoting of the values was not always being done properly. Specifically:
1045 (a) If the value started with a double quote, but contained no whitespace,
1047 (b) If the value contained whitespace other than a space character (i.e.
1048 tabs or newlines or carriage returns) it was not quoted.
1049 This fix has been applied to the mysql and pgsql lookups by writing a
1050 separate quoting function and calling it from the lookup code. The fix
1051 should probably also be applied to nisplus, ibase and oracle lookups, but
1052 since I cannot test any of those, I have not disturbed their existing code.
1054 2. A hit in the callout cache for a specific address caused a log line with no
1055 reason for rejecting RCPT. Now it says "Previous (cached) callout
1056 verification failure".
1058 3. There was an off-by-one bug in the queryprogram router. An over-long
1059 return line was truncated at 256 instead of 255 characters, thereby
1060 overflowing its buffer with the terminating zero. As well as fixing this, I
1061 have increased the buffer size to 1024 (and made a note to document this).
1063 4. If an interrupt, such as the USR1 signal that is send by exiwhat, arrives
1064 when Exim is waiting for an SMTP response from a remote server, Exim
1065 restarts its select() call on the socket, thereby resetting its timeout.
1066 This is not a problem when such interrupts are rare. Somebody set up a cron
1067 job to run exiwhat every 2 minutes, which is less than the normal select()
1068 timeout (5 or 10 minutes). This meant that the select() timeout never
1069 kicked in because it was always reset. I have fixed this by comparing the
1070 time when an interrupt arrives with the time at the start of the first call
1071 to select(). If more time than the timeout has elapsed, the interrupt is
1072 treated as a timeout.
1074 5. Some internal re-factoring in preparation for the addition of Sieve
1075 extensions (by MH). In particular, the "personal" test is moved to a
1076 separate function, and given an option for scanning Cc: and Bcc: (which is
1077 not set for Exim filters).
1079 6. When Exim created an email address using the login of the caller as the
1080 local part (e.g. when creating a From: or Sender: header line), it was not
1081 quoting the local part when it contained special characters such as @.
1083 7. Installed new OpenBSD configuration files.
1085 8. Reworded some messages for syntax errors in "and" and "or" conditions to
1086 try to make them clearer.
1088 9. Callout options, other than the timeout value, were being ignored when
1089 verifying sender addresses in header lines. For example, when using
1091 verify = header_sender/callout=no_cache
1093 the cache was (incorrectly) being used.
1095 10. Added a missing instance of ${EXE} to the exim_install script; this affects
1096 only the Cygwin environment.
1098 11. When return_path_on_delivery was set as a log selector, if different remote
1099 addresses in the same message used different return paths and parallel
1100 remote delivery occurred, the wrong values would sometimes be logged.
1101 (Whenever a remote delivery process finished, the return path value from
1102 the most recently started remote delivery process was logged.)
1104 12. RFC 3848 specifies standard names for the "with" phrase in Received: header
1105 lines when AUTH and/or TLS are in use. This is the "received protocol"
1106 field. Exim used to use "asmtp" for authenticated SMTP, without any
1107 indication (in the protocol name) for TLS use. Now it follows the RFC and
1108 uses "esmtpa" if the connection is authenticated, "esmtps" if it is
1109 encrypted, and "esmtpsa" if it is both encrypted and authenticated. These
1110 names appear in log lines as well as in Received: header lines.
1112 13. Installed MH's patches for Sieve to add the "copy" and "vacation"
1113 extensions, and comparison tests, and to fix some bugs.
1115 14. Changes to the "personal" filter test:
1117 (1) The test was buggy in that it was just doing the equivalent of
1118 "contains" tests on header lines. For example, if a user's address was
1119 anne@some.where, the "personal" test would incorrectly be true for
1121 To: susanne@some.where
1123 This test is now done by extracting each address from the header in turn,
1124 and checking the entire address. Other tests that are part of "personal"
1125 are now done using regular expressions (for example, to check local parts
1126 of addresses in From: header lines).
1128 (2) The list of non-personal local parts in From: addresses has been
1129 extended to include "listserv", "majordomo", "*-request", and "owner-*",
1130 taken from the Sieve specification recommendations.
1132 (3) If the message contains any header line starting with "List-" it is
1133 treated as non-personal.
1135 (4) The test for "circular" in the Subject: header line has been removed
1136 because it now seems ill-conceived.
1138 15. Minor typos in src/EDITME comments corrected.
1140 16. Installed latest exipick from John Jetmore.
1142 17. If headers_add on a router specified a text string that was too long for
1143 string_sprintf() - that is, longer than 8192 bytes - Exim panicked. The use
1144 of string_sprintf() is now avoided.
1146 18. $message_body_size was not set (it was always zero) when running the DATA
1147 ACL and the local_scan() function.
1149 19. For the "mail" command in an Exim filter, no default was being set for
1150 the once_repeat time, causing a random time value to be used if "once" was
1151 specified. (If the value happened to be <= 0, no repeat happened.) The
1152 default is now 0s, meaning "never repeat". The "vacation" command was OK
1153 (its default is 7d). It's somewhat surprising nobody ever noticed this bug
1154 (I found it when inspecting the code).
1156 20. There is now an overall timeout for performing a callout verification. It
1157 defaults to 4 times the callout timeout, which applies to individual SMTP
1158 commands during the callout. The overall timeout applies when there is more
1159 than one host that can be tried. The timeout is checked before trying the
1160 next host. This prevents very long delays if there are a large number of
1161 hosts and all are timing out (e.g. when the network connections are timing
1162 out). The value of the overall timeout can be changed by specifying an
1163 additional sub-option for "callout", called "maxwait". For example:
1165 verify = sender/callout=5s,maxwait=20s
1167 21. Add O_APPEND to the open() call for maildirsize files (Exim already seeks
1168 to the end before writing, but this should make it even safer).
1170 22. Exim was forgetting that it had advertised PIPELINING for the second and
1171 subsequent messages on an SMTP connection. It was also not resetting its
1172 memory on STARTTLS and an internal HELO.
1174 23. When Exim logs an SMTP synchronization error within a session, it now
1175 records whether PIPELINING has been advertised or not.
1177 24. Added 3 instances of "(long int)" casts to time_t variables that were being
1178 formatted using %ld, because on OpenBSD (and perhaps others), time_t is int
1179 rather than long int.
1181 25. Installed the latest Cygwin configuration files from the Cygwin maintainer.
1183 26. Added the never_mail option to autoreply.
1189 1. A reorganization of the code in order to implement 4.40/8 caused a daemon
1190 crash if the getsockname() call failed; this can happen if a connection is
1191 closed very soon after it is established. The problem was simply in the
1192 order in which certain operations were done, causing Exim to try to write
1193 to the SMTP stream before it had set up the file descriptor. The bug has
1194 been fixed by making things happen in the correct order.
1200 1. If "drop" was used in a DATA ACL, the SMTP output buffer was not flushed
1201 before the connection was closed, thus losing the rejection response.
1203 2. Commented out the definition of SOCKLEN_T in os.h-SunOS5. It is needed for
1204 some early Solaris releases, but causes trouble in current releases where
1205 socklen_t is defined.
1207 3. When std{in,out,err} are closed, re-open them to /dev/null so that they
1210 4. Minor refactoring of os.c-Linux to avoid compiler warning when IPv6 is not
1213 5. Refactoring in expand.c to improve memory usage. Pre-allocate a block so
1214 that releasing the top of it at the end releases what was used for sub-
1215 expansions (unless the block got too big). However, discard this block if
1216 the first thing is a variable or header, so that we can use its block when
1217 it is dynamic (useful for very large $message_headers, for example).
1219 6. Lookups now cache *every* query, not just the most recent. A new, separate
1220 store pool is used for this. It can be recovered when all lookup caches are
1221 flushed. Lookups now release memory at the end of their result strings.
1222 This has involved some general refactoring of the lookup sources.
1224 7. Some code has been added to the store_xxx() functions to reduce the amount
1225 of flapping under certain conditions.
1227 8. log_incoming_interface used to affect only the <= reception log lines. Now
1228 it causes the local interface and port to be added to several more SMTP log
1229 lines, for example "SMTP connection from", and rejection lines.
1231 9. The Sieve author supplied some patches for the doc/README.SIEVE file.
1233 10. Added a conditional definition of _BSD_SOCKLEN_T to os.h-Darwin.
1235 11. If $host_data was set by virtue of a hosts lookup in an ACL, its value
1236 could be overwritten at the end of the current message (or the start of a
1237 new message if it was set in a HELO ACL). The value is now preserved for
1238 the duration of the SMTP connection.
1240 12. If a transport had a headers_rewrite setting, and a matching header line
1241 contained an unqualified address, that address was qualified, even if it
1242 did not match any rewriting rules. The underlying bug was that the values
1243 of the flags that permit the existence of unqualified sender and recipient
1244 addresses in header lines (set by {sender,recipient}_unqualified_hosts for
1245 non-local messages, and by -bnq for local messages) were not being
1246 preserved with the message after it was received.
1248 13. When Exim was logging an SMTP synchronization error, it could sometimes log
1249 "next input=" as part of the text comprising the host identity instead of
1250 the correct text. The code was using the same buffer for two different
1251 strings. However, depending on which order the printing function evaluated
1252 its arguments, the bug did not always show up. Under Linux, for example, my
1253 test suite worked just fine.
1255 14. Exigrep contained a use of Perl's "our" scoping after change 4.31/70. This
1256 doesn't work with some older versions of Perl. It has been changed to "my",
1257 which in any case is probably the better facility to use.
1259 15. A really picky compiler found some instances of statements for creating
1260 error messages that either had too many or two few arguments for the format
1263 16. The size of the buffer for calls to the DNS resolver has been increased
1264 from 1024 to 2048. A larger buffer is needed when performing PTR lookups
1265 for addresses that have a lot of PTR records. This alleviates a problem; it
1266 does not fully solve it.
1268 17. A dnsdb lookup for PTR records that receives more data than will fit in the
1269 buffer now truncates the list and logs the incident, which is the same
1270 action as happens when Exim is looking up a host name and its aliases.
1271 Previously in this situation something unpredictable would happen;
1272 sometimes it was "internal error: store_reset failed".
1274 18. If a server dropped the connection unexpectedly when an Exim client was
1275 using GnuTLS and trying to read a response, the client delivery process
1276 crashed while trying to generate an error log message.
1278 19. If a "warn" verb in an ACL added multiple headers to a message in a single
1279 string, for example:
1281 warn message = H1: something\nH2: something
1283 the text was added as a single header line from Exim's point of view
1284 though it ended up OK in the delivered message. However, searching for the
1285 second and subsequent header lines using $h_h2: did not work. This has been
1286 fixed. Similarly, if a system filter added multiple headers in this way,
1287 the routers could not see them.
1289 20. Expanded the error message when iplsearch is called with an invalid key to
1290 suggest using net-iplsearch in a host list.
1292 21. When running tests using -bh, any delays imposed by "delay" modifiers in
1293 ACLs are no longer actually imposed (and a message to that effect is
1296 22. If a "gecos" field in a passwd entry contained escaped characters, in
1297 particular, if it contained a \" sequence, Exim got it wrong when building
1298 a From: or a Sender: header from that name. A second bug also caused
1299 incorrect handling when an unquoted " was present following a character
1300 that needed quoting.
1302 23. "{crypt}" as a password encryption mechanism for a "crypteq" expansion item
1303 was not being matched caselessly.
1305 24. Arranged for all hyphens in the exim.8 source to be escaped with
1308 25. Change 16 of 4.32, which reversed 71 or 4.31 didn't quite do the job
1309 properly. Recipient callout cache records were still being keyed to include
1310 the sender, even when use_sender was set false. This led to far more
1311 callouts that were necessary. The sender is no longer included in the key
1312 when use_sender is false.
1314 26. Added "control = submission" modifier to ACLs.
1316 27. Added the ${base62d: operator to decode base 62 numbers.
1318 28. dnsdb lookups can now access SRV records.
1320 29. CONFIGURE_OWNER can be set at build time to define an alternative owner for
1321 the configuration file.
1323 30. The debug message "delivering xxxxxx-xxxxxx-xx" is now output in verbose
1324 (-v) mode. This makes the output for a verbose queue run more intelligible.
1326 31. Added a use_postmaster feature to recipient callouts.
1328 32. Added the $body_zerocount variable, containing the number of binary zero
1329 bytes in the message body.
1331 33. The time of last modification of the "new" subdirectory is now used as the
1332 "mailbox time last read" when there is a quota error for a maildir
1335 34. Added string comparison operators lt, lti, le, lei, gt, gti, ge, gei.
1337 35. Added +ignore_unknown as a special item in host lists.
1339 36. Code for decoding IPv6 addresses in host lists is now included, even if
1340 IPv6 support is not being compiled. This fixes a bug in which an IPv6
1341 address was recognized as an IP address, but was then not correctly decoded
1342 into binary, causing unexpected and incorrect effects when compared with
1349 1. Very minor rewording of debugging text in manualroute to say "list of
1350 hosts" instead of "hostlist".
1352 2. If verify=header_syntax was set, and a header line with an unqualified
1353 address (no domain) and a large number of spaces between the end of the
1354 name and the colon was received, the reception process suffered a buffer
1355 overflow, and (when I tested it) crashed. This was caused by some obsolete
1356 code that should have been removed. The fix is to remove it!
1358 3. When running in the test harness, delay a bit after writing a bounce
1359 message to get a bit more predictability in the log output.
1361 4. Added a call to search_tidyup() just before forking a reception process. In
1362 theory, someone could use a lookup in the expansion of smtp_accept_max_
1363 per_host which, without the tidyup, could leave open a database connection.
1365 5. Added the variables $recipient_data and $sender_data which get set from a
1366 lookup success in an ACL "recipients" or "senders" condition, or a router
1367 "senders" option, similar to $domain_data and $local_part_data.
1369 6. Moved the writing of debug_print from before to after the "senders" test
1372 7. Change 4.31/66 (moving the time when the Received: is generated) caused
1373 problems for message scanning, either using a data ACL, or using
1374 local_scan() because the Received: header was not generated till after they
1375 were called (in order to set the time as the time of reception completion).
1376 I have revised the way this works. The header is now generated after the
1377 body is received, but before the ACL or local_scan() are called. After they
1378 are run, the timestamp in the header is updated.
1384 1. Change 4.24/6 introduced a bug because the SIGALRM handler was disabled
1385 before starting a queue runner without re-exec. This happened only when
1386 deliver_drop_privilege was set or when the Exim user was set to root. The
1387 effect of the bug was that timeouts during subsequent deliveries caused
1388 crashes instead of being properly handled. The handler is now left at its
1389 default (and expected) setting.
1391 2. The other case in which a daemon avoids a re-exec is to deliver an incoming
1392 message, again when deliver_drop_privilege is set or Exim is run as root.
1393 The bug described in (1) was not present in this case, but the tidying up
1394 of the other signals was missing. I have made the two cases consistent.
1396 3. The ignore_target_hosts setting on a manualroute router was being ignored
1397 for hosts that were looked up using the /MX notation.
1399 4. Added /ignore=<ip list> feature to @mx_any, @mx_primary, and @mx_secondary
1402 5. Change 4.31/55 was buggy, and broke when there was a rewriting rule that
1403 operated on the sender address. After changing the $sender_address to <>
1404 for the sender address verify, Exim was re-instated it as the original
1405 (before rewriting) address, but remembering that it had rewritten it, so it
1406 wasn't rewriting it again. This bug also had the effect of breaking the
1407 sender address verification caching when the sender address was rewritten.
1409 6. The ignore_target_hosts option was being ignored by the ipliteral router.
1410 This has been changed so that if the ip literal address matches
1411 ignore_target_hosts, the router declines.
1413 7. Added expansion conditions match_domain, match_address, and match_local_
1414 part (NOT match_host).
1416 8. The placeholder for the Received: header didn't have a length field set.
1418 9. Added code to Exim itself and to exim_lock to test for a specific race
1419 condition that could lead to file corruption when using MBX delivery. The
1420 issue is with the lockfile that is created in /tmp. If this file is removed
1421 after a process has opened it but before that process has acquired a lock,
1422 there is the potential for a second process to recreate the file and also
1423 acquire a lock. This could lead to two Exim processes writing to the file
1424 at the same time. The added code performs the same test as UW imapd; it
1425 checks after acquiring the lock that its file descriptor still refers to
1426 the same named file.
1428 10. The buffer for building added header lines was of fixed size, 8192 bytes.
1429 It is now parameterized by HEADER_ADD_BUFFER_SIZE and this can be adjusted
1432 11. Added the smtp_active_hostname option. If used, this will typically be made
1433 to depend on the incoming interface address. Because $interface_address is
1434 not set up until the daemon has forked a reception process, error responses
1435 that can happen earlier (such as "too many connections") no longer contain
1438 12. If an expansion in a condition on a "warn" statement fails because a lookup
1439 defers, the "warn" statement is abandoned, and the next ACL statement is
1440 processed. Previously this caused the whole ACL to be aborted.
1442 13. Added the iplsearch lookup type.
1444 14. Added ident_timeout as a log selector.
1446 15. Added tls_certificate_verified as a log selector.
1448 16. Added a global option tls_require_ciphers (compare the smtp transport
1449 option of the same name). This controls incoming TLS connections.
1451 17. I finally figured out how to make tls_require_ciphers do a similar thing
1452 in GNUtls to what it does in OpenSSL, that is, set up an appropriate list
1453 before starting the TLS session.
1455 18. Tabs are now shown as \t in -bP output.
1457 19. If the log selector return_path_on_delivery was set, Exim crashed when
1458 bouncing a message because it had too many Received: header lines.
1460 20. If two routers both had headers_remove settings, and the first one included
1461 a superfluous trailing colon, the final name in the first list and the
1462 first name in the second list were incorrectly joined into one item (with a
1463 colon in the middle).
1469 1. Added -C and -D options to the exinext utility, mainly to make it easier
1470 to include in the automated testing, but these could be helpful when
1471 multiple configurations are in use.
1473 2. The exinext utility was not formatting the output nicely when there was
1474 an alternate port involved in the retry record key, nor when there was a
1475 message id as well (for retries that were specific to a specific message
1476 and a specific host). It was also confused by IPv6 addresses, because of
1477 the additional colons they contain. I have fixed the IPv4 problem, and
1478 patched it up to do a reasonable job for IPv6.
1480 3. When there is an error after a MAIL, RCPT, or DATA SMTP command during
1481 delivery, the log line now contains "pipelined" if PIPELINING was used.
1483 4. An SMTP transport process used to panic and die if the bind() call to set
1484 an explicit outgoing interface failed. This has been changed; it is now
1485 treated in the same way as a connect() failure.
1487 5. A reference to $sender_host_name in the part of a conditional expansion
1488 that was being skipped was still causing a DNS lookup. This no longer
1491 6. The def: expansion condition was not recognizing references to header lines
1492 that used bh_ and bheader_.
1494 7. Added the _cache feature to named lists.
1496 8. The code for checking quota_filecount in the appendfile transport was
1497 allowing one more file than it should have been.
1499 9. For compatibility with Sendmail, the command line option
1507 and sets the incoming protocol and host name (for trusted callers). The
1508 host name and its colon can be omitted when only the protocol is to be set.
1509 Note the Exim already has two private options, -pd and -ps, that refer to
1510 embedded Perl. It is therefore impossible to set a protocol value of "d" or
1511 "s", but I don't think that's a major issue.
1513 10. A number of refactoring changes to the code, none of which should affect
1516 (a) The number of logging options was getting close to filling up the
1517 32-bit word that was used as a bit map. I have split them into two classes:
1518 those that are passed in the argument to log_write(), and those that are
1519 only ever tested independently outside of that function. These are now in
1520 separate 32-bit words, so there is plenty of room for expansion again.
1521 There is no change in the user interface or the logging behaviour.
1523 (b) When building, for example, log lines, the code previously used a
1524 macro that called string_cat() twice, in order to add two strings. This is
1525 not really sufficiently general. Furthermore, there was one instance where
1526 it was actually wrong because one of the argument was used twice, and in
1527 one call a function was used. (As it happened, calling the function twice
1528 did not affect the overall behaviour.) The macro has been replaced by a
1529 function that can join an arbitrary number of extra strings onto a growing
1532 (c) The code for expansion conditions now uses a table and a binary chop
1533 instead of a serial search (which was left over from when there were very
1534 few conditions). Also, it now recognizes conditions like "pam" even when
1535 the relevant support is not compiled in: a suitably worded error message is
1536 given if an attempt is made to use such a condition.
1538 11. Added ${time_interval:xxxxx}.
1540 12. A bug was causing one of the ddress fields not to be passed back correctly
1541 from remote delivery subprocesses. The field in question was not being
1542 subsequently used, so this caused to problems in practice.
1544 13. Added new log selectors queue_time and deliver_time.
1546 14. Might have fixed a bug in maildirsizefile handling that threw up
1547 "unexpected character" debug warnings, and recalculated the data
1548 unnecessarily. In any case, I expanded the warning message to give more
1551 15. Added the message "Restricted characters in address" to the statements in
1552 the default ACL that block characters like @ and % in local parts.
1554 16. Change 71 for release 4.31 proved to be much less benign that I imagined.
1555 Three changes have been made:
1557 (a) There was a serious bug; a negative response to MAIL caused the whole
1558 recipient domain to be cached as invalid, thereby blocking all messages
1559 to all local parts at the same domain, from all senders. This bug has
1560 been fixed. The domain is no longer cached after a negative response to
1561 MAIL if the sender used is not empty.
1563 (b) The default behaviour of using MAIL FROM:<> for recipient callouts has
1566 (c) A new callout option, "use_sender" has been added for people who want
1567 the modified behaviour.
1573 1. Removed "EXTRALIBS=-lwrap" from OS/Makefile-Unixware7 on the advice of
1576 2. Removed "LIBS = -lresolv" from OS/Makefile-Darwin as it is not needed, and
1577 indeed breaks things for older releases.
1579 3. Added additional logging to the case where there is a problem reading data
1580 from a filter that is running in a subprocess using a pipe, in order to
1581 try to track down a specific problem.
1583 4. Testing facility fudge: when running in the test harness and attempting
1584 to connect to 10.x.x.x (expecting a connection timeout) I'm now sometimes
1585 getting "No route to host". Convert this to a timeout.
1587 5. Define ICONV_ARG2_TYPE as "char **" for Unixware7 to avoid compiler
1590 6. Some OS don't have socklen_t but use size_t instead. This affects the
1591 fifth argument of getsockopt() amongst other things. This is now
1592 configurable by a macro called SOCKLEN_T which defaults to socklen_t, but
1593 can be set for individual OS. I have set it for SunOS5, OSF1, and
1594 Unixware7. Current versions of SunOS5 (aka Solaris) do have socklen_t, but
1595 some earlier ones do not.
1597 7. Change 4.30/15 was not doing the test caselessly.
1599 8. The standard form for an IPv6 address literal was being rejected by address
1600 parsing in, for example, MAIL and RCPT commands. An example of this kind of
1601 address is [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
1602 this, as well as the form without the "IPv6" on the front (but only when
1603 address literals are enabled, of course).
1605 9. Added some casts to avoid compiler warnings in OS/os.c-Linux.
1607 10. Exim crashed if a message with an empty sender address specified by -f
1608 encountered a router with an errors_to setting. This could be provoked only
1609 by a command such as
1613 where an empty string was supplied; "<>" did not hit this bug.
1615 11. Installed PCRE release 4.5.
1617 12. If EHLO/HELO was rejected by an ACL, the value of $sender_helo_name
1618 remained set. It is now erased.
1620 13. exiqgrep wasn't working on MacOS X because it didn't correctly compute
1621 times from message ids (which are base 36 rather than the normal 62).
1623 14. "Expected" SMTP protocol errors that can arise when PIPELINING is in use
1624 were being counted as actual protocol errors, and logged if the log
1625 selector +smtp_protocol_error was set. One cannot be perfect in this test,
1626 but now, if PIPELINING has been advertised, RCPT following a rejected MAIL,
1627 and DATA following a set of rejected RCPTs do not count as protocol errors.
1628 In other words, Exim assumes they were pipelined, though this may not
1629 actually be the case. Of course, in all cases the client gets an
1630 appropriate error code.
1632 15. If a lookup fails in an ACL condition, a message about the failure may
1633 be available; it is used if testing the ACL cannot continue, because most
1634 such messages specify what the cause of the deferral is. However, some
1635 messages (e.g. "MYSQL: no data found") do not cause a defer. There was bug
1636 that caused an old message to be retained and used if a later statement
1637 caused a defer, replacing the real cause of the deferral.
1639 16. If an IP address had so many PTR records that the DNS lookup buffer
1640 was not large enough to hold them, Exim could crash while trying to process
1641 the truncated data. It now detects and logs this case.
1643 17. Further to 4.21/58, another change has been made: if (and only if) the
1644 first line of a message (the first header line) ends with CRLF, a bare LF
1645 in a subsequent header line has a space inserted after it, so as not to
1646 terminate the header.
1648 18. Refactoring: tidied an ugly bit of code in appendfile that copied data
1649 unnecessarily, used atoi() instead of strtol(), and didn't check the
1650 termination when getting file sizes from file names by regex.
1652 19. Completely re-implemented the support for maildirsize files, in the light
1653 of a number of problems with the previous contributed implementation
1654 (4.30/29). In particular:
1656 . If the quota is zero, the maildirsize file is maintained, but no quota is
1659 . If the maildir directory does not exist, it is created before any attempt
1660 to write a maildirsize file.
1662 . The quota value in the file is just a cache; if the quota is changed in
1663 the transport, the new value overrides.
1665 . A regular expression is available for excluding directories from the
1668 20. The autoreply transport checks the characters in options that define the
1669 message's headers; it allows continued headers, but it was checking with
1670 isspace() after an embedded newline instead of explicitly looking for a
1673 21. If all the "regular" hosts to which an address was routed had passed their
1674 expiry times, and had not reached their retry times, the address was
1675 bounced, even if fallback hosts were defined. Now Exim should go on to try
1678 22. Increased buffer sizes in the callout code from 1024 to 4096 to match the
1679 equivalent code in the SMTP transport. Some hosts send humungous responses
1680 to HELO/EHLO, more than 1024 it seems.
1682 23. Refactoring: code in filter.c used (void *) for "any old type" but this
1683 gives compiler warnings in some environments. I've now done it "properly",
1686 24. The replacement for inet_ntoa() that is used with gcc on IRIX systems
1687 (because of problems with the built-in one) was declared to return uschar *
1688 instead of char *, causing compiler failure.
1690 25. Fixed a file descriptor leak when processing alias/forward files.
1692 26. Fixed a minor format string issue in dbfn.c.
1694 27. Typo in exim.c: ("dmbnz" for "dbmnz").
1696 28. If a filter file refered to $h_xxx or $message_headers, and the headers
1697 contained RFC 2047 "words", Exim's memory could, under certain conditions,
1700 29. When a sender address is verified, it is cached, to save repeating the test
1701 when there is more than one recipient in a message. However, when the
1702 verification involves a callout, it is possible for different callout
1703 options to be set for different recipients. It is too complicated to keep
1704 track of this in the cache, so now Exim always runs a verification when a
1705 callout is required, relying on the callout cache for the optimization.
1706 The overhead is duplication of the address routing, but this should not be
1709 30. Fixed a bug in callout caching. If a RCPT command caused the sender address
1710 to be verified with callout=postmaster, and the main callout worked but the
1711 postmaster check failed, the verification correctly failed. However, if a
1712 subsequent RCPT command asked for sender verification *without* the
1713 postmaster check, incorrect caching caused this verification also to fail,
1716 31. Exim caches DNS lookup failures so as to avoid multiple timeouts; however,
1717 it was not caching the DNS options (qualify_single, search_parents) that
1718 were used when the lookup failed. A subsequent lookup with different
1719 options therefore always gave the same answer, though there were cases
1720 where it should not have. (Example: a "domains = !$mx_any" option on a
1721 dnslookup router: the "domains" option is always processed without any
1722 widening, but the router might have qualify_single set.) Now Exim uses the
1723 cached value only when the same options are set.
1725 32. Added John Jetmore's "exipick" utility to the distribution.
1727 33. GnuTLS: When an attempt to start a TLS session fails for any reason other
1728 than a timeout (e.g. a certificate is required, and is not provided), an
1729 Exim server now closes the connection immediately. Previously it waited for
1730 the client to close - but if the client is SSL, it seems that they each
1731 wait for each other, leading to a delay before one of them times out.
1733 34: GnuTLS: Updated the code to use the new GnuTLS 1.0.0 API. I have not
1734 maintained 0.8.x compatibility because I don't think many are using it, and
1735 it is clearly obsolete.
1737 35. Added TLS support for CRLs: a tls_crl global option and one for the smtp
1740 36. OpenSSL: $tls_certificate_verified was being set to 1 even if the
1741 client certificate was expired. A simple patch fixes this, though I don't
1742 understand the full logic of why the verify callback is called multiple
1745 37. OpenSSL: a patch from Robert Roselius: "Enable client-bug workaround.
1746 Versions of OpenSSL as of 0.9.6d include a 'CBC countermeasure' feature,
1747 which causes problems with some clients (such as the Certicom SSL Plus
1748 library used by Eudora). This option, SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS,
1749 disables the coutermeasure allowing Eudora to connect."
1751 38. Exim was not checking that a write() to a log file succeeded. This could
1752 lead to Bad Things if a log got too big, in particular if it hit a file
1753 size limit. Exim now panics and dies if it cannot write to a log file, just
1754 as it does if it cannot open a log file.
1756 39. Modified OS/Makefile-Linux so that it now contains
1758 CFLAGS=-O -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
1760 The two -D definitions ensure that Exim is compiled with large file
1761 support, which makes it possible to handle log files that are bigger than
1764 40. Fixed a subtle caching bug: if (in an ACL or a set of routers, for
1765 instance) a domain was checked against a named list that involved a lookup,
1766 causing $domain_data to be set, then another domain was checked against the
1767 same list, then the first domain was re-checked, the value of $domain_data
1768 after the final check could be wrong. In particular, if the second check
1769 failed, it could be set empty. This bug probably also applied to
1772 41. The strip_trailing_dot option was not being applied to the address given
1773 with the -f command-line option.
1775 42. The code for reading a message's header from the spool was incrementing
1776 $received_count, but never initializing it. This meant that the value was
1777 incorrect (doubled) while delivering a message in the same process in which
1778 it was received. In the most common configuration of Exim, this never
1779 happens - a fresh exec is done - but it can happen when
1780 deliver_drop_privilege is set.
1782 43. When Exim logs an SMTP synchronization error - client data sent too soon -
1783 it now includes up to 150 characters of the unexpected data in the log
1786 44. The exim_dbmbuild utility uses fixed size buffers for reading input lines
1787 and building data strings. The size of both of these buffers was 10 000
1788 bytes - far larger than anybody would *ever* want, thought I. Needless to
1789 say, somebody hit the limit. I have increased the maximum line length to
1790 20 000 and the maximum data length of concatenated lines to 100 000. I have
1791 also fixed two bugs, because there was no checking on these buffers. Tsk,
1792 tsk. Now exim_dbmbuild gives a message and exits with an error code if a
1793 buffer is too small.
1795 45. The exim_dbmbuild utility did not support quoted keys, as Exim does in
1796 lsearch lookups. Now it does.
1798 46. When parsing a route_list item in a manualroute router, a fixed-length
1799 buffer was used for the list of hosts. I made this 1024 bytes long,
1800 thinking that nobody would ever have a list of hosts that long. Wrong.
1801 Somebody had a whole pile of complicated expansion conditions, and the
1802 string was silently truncated, leading to an expansion error. It turns out
1803 that it is easier to change to an unlimited length (owing to other changes
1804 that have happened since this code was originally written) than to build
1805 structure for giving a limitation error. The length of the item that
1806 expands into the list of hosts is now unlimited.
1808 47. The lsearch lookup could not handle data where the length of text line was
1809 more than 4095 characters. Such lines were truncated, leading to shortened
1810 data being returned. It should now handle lines of any length.
1812 48. Minor wording revision: "cannot test xxx in yyy ACL" becomes "cannot test
1813 xxx condition in yyy ACL" (e.g. "cannot test domains condition in DATA
1816 49. Cosmetic tidy to scripts like exicyclog that are generated by globally
1817 replacing strings such as BIN_DIRECTORY in a source file: the replacement
1818 no longer happens in comment lines. A list of replacements is now placed
1819 at the head of all of the source files, except those whose only change is
1820 to replace PERL_COMMAND in the very first #! line.
1822 50. Replaced the slow insertion sort in queue.c, for sorting the list of
1823 messages on the queue, with a bottom-up merge sort, using code contributed
1824 by Michael Haardt. This should make operations like -bp somewhat faster on
1825 large queues. It won't affect queue runners, except when queue_run_in_order
1828 51. Installed eximstats 1.31 in the distribution.
1830 52. Added support for SRV lookups to the dnslookup router.
1832 53. If an ACL referred to $message_body or $message_body_end, the value was not
1833 reset for any messages that followed in the same SMTP session.
1835 54. The store-handling optimization for building very long strings was not
1836 differentiating between the different store pools. I don't think this
1837 actually made any difference in practice, but I've tidied it.
1839 55. While running the routers to verify a sender address, $sender_address
1840 was still set to the sender address. This is wrong, because when routing to
1841 send a bounce to the sender, it would be empty. Therefore, I have changed
1842 it so that, while verifying a sender address, $sender_address is set to <>.
1843 (There is no change to what happens when verifying a recipient address.)
1845 56. After finding MX (or SRV) records, Exim was doing a DNS lookup for the
1846 target A or AAAA records (if not already returned) without resetting the
1847 qualify_single or search_parents options of the DNS resolver. These are
1848 inappropriate in this case because the targets of MX and SRV records must
1849 be FQDNs. A broken DNS record could cause trouble if it happened to have a
1850 target that, when qualified, matched something in the local domain. These
1851 two options are now turned off when doing these lookups.
1853 57. It seems that at least some releases of Reiserfs (which does not have the
1854 concept of a fixed number of inodes) returns zero and not -1 for the
1855 number of available inodes. This interacted badly with check_spool_inodes,
1856 which assumed that -1 was the "no such thing" setting. What I have done is
1857 to check that the total number of inodes is greater than zero before doing
1858 the test of how many are available.
1860 58. When a "warn" ACL statement has a log_message modifier, the message is
1861 remembered, and not repeated. This is to avoid a lot of repetition when a
1862 message has many recipients that cause the same warning to be written.
1863 Howewer, Exim was preserving the list of already written lines for an
1864 entire SMTP session, which doesn't seem right. The memory is now reset if a
1865 new message is started.
1867 59. The "rewrite" debugging flag was not showing the result of rewriting in the
1868 debugging output unless log_rewrite was also set.
1870 60. Avoid a compiler warning on 64-bit systems in dsearch.c by avoiding the use
1871 of (int)(handle) when we know that handle contains (void *)(-1).
1873 61. The Exim daemon panic-logs an error return when it closes the incoming
1874 connection. However "connection reset by peer" seems to be common, and
1875 isn't really an error worthy of noting specially, so that particular error
1878 62. When Exim is trying to find all the local interfaces, it used to panic and
1879 die if the ioctl to get the interface flags failed. However, it seems that
1880 on at least one OS (Solaris 9) it is possible to have an interface that is
1881 included in the list of interfaces, but for which you get a failure error
1882 for this call. This happens when the interface is not "plumbed" into a
1883 protocol (i.e. neither IPv4 nor IPv6). I've changed the code so that a
1884 failure of the "get flags" call assumes that the interface is down.
1886 63. Added a ${eval10: operator, which assumes all numbers are decimal. This
1887 makes life easier for people who are doing arithmetic on fields extracted
1888 from dates, where you often get leading zeros that should not be
1889 interpreted as octal.
1891 64. Added qualify_domain to the redirect router, to override the global
1894 65. If a pathologically long header line contained very many addresses (the
1895 report of this problem mentioned 10 000) and each of them was rewritten,
1896 Exim could use up a very large amount of memory. (It kept on making new
1897 copies of the header line as it rewrote, and never released the old ones.)
1898 At the expense of a bit more processing, the header rewriting function has
1899 been changed so that it no longer eats memory in this way.
1901 66. The generation of the Received: header has been moved from the time that a
1902 message starts to be received, to the time that it finishes. The timestamp
1903 in the Received: header should now be very close to that of the <= log
1904 line. There are two side-effects of this change:
1906 (a) If a message is rejected by a DATA or non-SMTP ACL or local_scan(), the
1907 logged header lines no longer include the local Received: line, because
1908 it has not yet been created. The same applies to a copy of the message
1909 that is returned to a non-SMTP sender when a message is rejected.
1911 (b) When a filter file is tested using -bf, no additional Received: header
1912 is added to the test message. After some thought, I decided that this
1915 This change does not affect the value of $received_for. It is still set
1916 after address rewriting, but before local_scan() is called.
1918 67. Installed the latest Cygwin-specific files from the Cygwin maintainer.
1920 68. GnuTLS: If an empty file is specified for tls_verify_certificates, GnuTLS
1921 gave an unhelpful panic error message, and a defer error. I have managed to
1922 change this behaviour so that it now rejects any supplied certificate,
1923 which seems right, as the list of acceptable certificates is empty.
1925 69. OpenSSL: If an empty file is specified for tls_verify_certificates, OpenSSL
1926 gave an unhelpful defer error. I have not managed to make this reject any
1927 supplied certificates, but the error message it gives is "no certificate
1928 supplied", which is not helpful.
1930 70. exigrep's output now also includes lines that are not associated with any
1931 message, but which match the given pattern. Implemented by a patch from
1932 Martin Sluka, which also tidied up the Perl a bit.
1934 71. Recipient callout verification, like sender verification, was using <> in
1935 the MAIL FROM command. This isn't really the right thing, since the actual
1936 sender may affect whether the remote host accepts the recipient or not. I
1937 have changed it to use the actual sender in the callout; this means that
1938 the cache record is now keyed on a recipient/sender pair, not just the
1939 recipient address. There doesn't seem to be a real danger of callout loops,
1940 since a callout by the remote host to check the sender would use <>.
1941 [SEE ABOVE: changed after hitting problems.]
1943 72. Exim treats illegal SMTP error codes that do not begin with 4 or 5 as
1944 temporary errors. However, in the case of such a code being given after
1945 the end of a data transmission (i.e. after ".") Exim was failing to write
1946 a retry record for the message. (Yes, there was some broken host that was
1947 actually sending 8xx at this point.)
1949 73. An unknown lookup type in a host list could cause Exim to panic-die when
1950 the list was checked. (An example that provoked this was putting <; in the
1951 middle of a list instead of at the start.) If this happened during a DATA
1952 ACL check, a -D file could be left lying around. This kind of configuration
1953 error no longer causes Exim to die; instead it causes a defer errror. The
1954 incident is still logged to the main and panic logs.
1956 74. Buglet left over from Exim 3 conversion. The message "too many messages
1957 in one connection" was written to the rejectlog but not the mainlog, except
1958 when address rewriting (yes!) was being logged.
1960 75. Added write_rejectlog option.
1962 76. When a system filter was run not as root (that is, when system_filter_user
1963 was set), the values of the $n variables were not being returned to the
1964 main process; thus, they were not subsequently available in the $sn
1967 77. Added +return_path_on_delivery log selector.
1969 78. A connection timeout was being treated differently from recipients deferred
1970 when testing hosts_max_try with a message that was older than the host's
1971 retry timeout. (The host should not be counted, thus allowing all hosts to
1972 be tried at least once before bouncing.) This may have been the cause of an
1973 occasionally reported bug whereby a message would remain on the queue
1974 longer than the retry timeout, but would be bounced if a delivery was
1975 forced. I say "may" because I never totally pinned down the problem;
1976 setting up timeout/retry tests is difficult. See also the next item.
1978 79. The ultimate address timeout was not being applied to errors that involved
1979 a combination of host plus message (for example, a timeout on a MAIL
1980 command). When an address resolved to a number of possible hosts, and they
1981 were not all tried for each delivery (e.g. because of hosts_max_try), a
1982 message could remain on the queue longer than the retry timeout.
1984 80. Sieve bug: "stop" inside "elsif" was broken. Applied a patch from Michael
1987 81. Fixed an obscure SMTP outgoing bug which required at least the following
1988 conditions: (a) there was another message waiting for the same server;
1989 (b) the server returned 5xx to all RCPT commands in the first message so
1990 that the message was not completed; (c) the server dropped the connection
1991 or gave a negative response to the RSET that Exim sends to abort the
1992 transaction. The observed case was a dropped connection after DATA that had
1993 been sent in pipelining mode. That is, the server had advertised PIPELINING
1994 but was not implementing it correctly. The effect of the bug was incorrect
1995 behaviour, such as trying another host, and this could lead to a crash.
2001 1. The 3rd arguments to getsockname(), getpeername(), and accept() in exim.c
2002 and daemon.c were passed as pointers to ints; they should have been
2003 pointers to socklen_t variables (which are typically unsigned ints).
2005 2. Some signed/unsigned type warnings in the os.c file for Linux have been
2008 3. Fixed a really odd bug that affected only the testing scheme; patching a
2009 certain fixed string in the binary changed the value of another string that
2010 happened to be identical to the end of the original first string.
2012 4. When gethostbyname() (or equivalent) is passed an IP address as a "host
2013 name", it returns that address as the IP address. On some operating
2014 systems (e.g. Solaris), it also passes back the IP address string as the
2015 "host name". However, on others (e.g. Linux), it passes back an empty
2016 string. Exim wasn't checking for this, and was changing the host name to an
2017 empty string, assuming it had been canonicized.
2019 5. Although rare, it is permitted to have more than one PTR record for a given
2020 IP address. I thought that gethostbyaddr() or getipnodebyaddr() always gave
2021 all the names associated with an address, because they do in Solaris.
2022 However, it seems that they do not in Linux for data that comes from the
2023 DNS. If an address in /etc/hosts has multiple names, they _are_ all given.
2024 I found this out when I moved to a new Linux workstation and tried to run
2025 the Exim test suite.
2027 To get round this problem I have changed the code so that it now does its
2028 own call to the DNS to look up PTR records when searching for a host name.
2029 If nothing can be found in the DNS, it tries gethostbyaddr(), so that
2030 addresses that are only in /etc/hosts are still found.
2032 This behaviour is, however, controlled by an option called host_lookup_
2033 order, which defaults to "bydns:byaddr". If people want to use the other
2034 order, or indeed, just use one or the other means of lookup, they can
2035 specify it in this variable.
2037 6. If a PTR record yields an empty name, Exim treats it as non-existent. In
2038 some operating systems, this comes back from gethostbyaddr() as an empty
2039 string, and this is what Exim used to test for. However, it seems that in
2040 other systems, "." is yielded. Exim now tests for this case too.
2042 7. The values of check_spool_space and check_log_space are now held internally
2043 as a number of kilobytes instead of an absolute number of bytes. If a
2044 numbers is specified without 'K' or 'M', it is rounded up to the nearest
2045 kilobyte. This means that much larger values can be stored.
2047 8. Exim monitor: an attempt to get the action menu when not actually pointing
2048 at a message produces an empty menu entitled "No message selected". This
2049 works on Solaris (OpenWindows). However, XFree86 does not like a menu with
2050 no entries in it ("Shell widget menu has zero width and/or height"). So I
2051 have added a single, blank menu entry in this case.
2053 9. Added ${quote_local_part.
2055 10. MIME decoding is now applied to the contents of Subject: header lines when
2058 11. Now that a reference to $sender_host_address automatically causes a reverse
2059 lookup to occur if necessary (4.13/18), there is no need to arrange for a
2060 host lookup before query-style lookups in lists that might use this
2061 variable. This has therefore been abolished, and the "net-" prefix is no
2062 longer necessary for query-style lookups.
2064 12. The Makefile for SCO_SV contained a setting of LDFLAGS. This appears to
2065 have been a typo for LFLAGS, so it has been changed.
2067 13. The install script calls Exim with "-C /dev/null" in order to find the
2068 version number. If ALT_CONFIG_PREFIX was set, this caused an error message
2069 to be output. Howeve, since Exim outputs its version number before the
2070 error, it didn't break the script. It just looked ugly. I fixed this by
2071 always allowing "-C /dev/null" if the caller is root.
2073 14. Ignore overlarge ACL variable number when reading spool file - insurance
2074 against a later release with more variables having written the file.
2076 15. The standard form for an IPv6 address literal was being rejected by EHLO.
2077 Example: [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
2078 this, as well as the form without the "IPv6" on the front.
2080 16. Added CHOWN_COMMAND=/usr/sbin/chown and LIBS=-lresolv to the
2081 OS/Makefile-Darwin file.
2083 17. Fixed typo in lookups/ldap.c: D_LOOKUP should be D_lookup. This applied
2084 only to LDAP libraries that do not have LDAP_OPT_DEREF.
2086 18. After change 4.21/52, "%ld" was used to format the contents of the $inode
2087 variable. However, some OS use ints for inodes. I've added cast to long int
2088 to get rid of the compiler warning.
2090 19. I had forgotten to lock out "/../" in configuration file names when
2091 ALT_CONFIG_PREFIX was set.
2093 20. Routers used for verification do not need to specify transports. However,
2094 if such a router generated a host list, and callout was configured, Exim
2095 crashed, because it could not find a port number from the (non-existent)
2096 transport. It now assumes port 25 in this circumstance.
2098 21. Added the -t option to exigrep.
2100 22. If LOOKUP_LSEARCH is defined, all three linear search methods (lsearch,
2101 wildlsearch, nwildlsearch) are compiled. LOOKUP_WILDLSEARCH and LOOKUP_
2102 NWILDLSEARCH are now obsolete, but retained for compatibility. If either of
2103 them is set, LOOKUP_LSEARCH is forced.
2105 23. "exim -bV" now outputs a list of lookups that are included in the binary.
2107 24. Added sender and host information to the "rejected by local_scan()" log
2108 line; previously there was no indication of these.
2110 25. Added .include_if_exists.
2112 26. Change 3.952/11 added an explicit directory sync on top of a file sync for
2113 Linux. It turns out that not all file systems support this. Apparently some
2114 versions of NFS do not. (It's rare to put Exim's spool on NFS, but people
2115 do it.) To cope with this, the error EINVAL, which means that sync-ing is
2116 not supported on the file descriptor, is now ignored when Exim is trying to
2117 sync a directory. This applies only to Linux.
2119 27. Added -DBIND_8_COMPAT to the CLFAGS setting for Darwin.
2121 28. In Darwin (MacOS X), the PAM headers are in /usr/include/pam and not in
2122 /usr/include/security. There's now a flag in OS/os.h-Darwin to cope with
2125 29. Added support for maildirsize files from supplied patch (modified a bit).
2127 30. The use of :fail: followed by an empty string could lead Exim to respond to
2128 sender verification failures with (e.g.):
2130 550 Verification failed for <xxx>
2131 550 Sender verify failed
2133 where the first response line was missing the '-' that indicates it is not
2134 the final line of the response.
2136 31. The loop for finding the name of the user that called Exim had a hardwired
2137 limit of 10; it now uses the value of finduser_retries, which is used for
2138 all other user lookups.
2140 32. Added $received_count variable, available in data and not_smtp ACLs, and at
2143 33. Exim was neglecting to zero errno before one call of strtol() when
2144 expanding a string and expecting an integer value. On some systems this
2145 resulted in spurious "integer overflow" errors. Also, it was casting the
2146 result into an int without checking.
2148 34. Testing for a connection timeout using "timeout_connect" in the retry rules
2149 did not work. The code looks as if it has *never* worked, though it appears
2150 to have been documented since at least releast 1.62. I have made it work.
2152 35. The "timeout_DNS" error in retry rules, also documented since at least
2153 1.62, also never worked. As it isn't clear exactly what this means, and
2154 clearly it isn't a major issue, I have abolished the feature by treating it
2155 as "timeout", and writing a warning to the main and panic logs.
2157 36. The display of retry rules for -brt wasn't always showing the error code
2160 37. Added new error conditions to retry rules: timeout_A, timeout_MX,
2161 timeout_connect_A, timeout_connect_MX.
2163 38. Rewriting the envelope sender at SMTP time did not allow it to be rewritten
2164 to the empty sender.
2166 39. The daemon was not analysing the content of -oX till after it had closed
2167 stderr and disconnected from the controlling terminal. This meant that any
2168 syntax errors were only noted on the panic log, and the return code from
2169 the command was 0. By re-arranging the code a little, I've made the
2170 decoding happen first, so such errors now appear on stderr, and the return
2171 code is 1. However, the actual setting up of the sockets still happens in
2172 the disconnected process, so errors there are still only recorded on the
2175 40. A daemon listener on a wildcard IPv6 socket that also accepts IPv4
2176 connections (as happens on some IP stacks) was logged at start up time as
2177 just listening for IPv6. It now logs "IPv6 with IPv4". This differentiates
2178 it from "IPv6 and IPv4", which means that two separate sockets are being
2181 41. The debug output for gethostbyname2() or getipnodebyname() failures now
2182 says whether AF_INET or AF_INET6 was passed as an argument.
2184 42. Exiwhat output was messed up when time zones were included in log
2187 43. Exiwhat now gives more information about the daemon's listening ports,
2188 and whether -tls-on-connect was used.
2190 44. The "port" option of the smtp transport is now expanded.
2192 45. A "message" modifier in a "warn" statement in a non-message ACL was being
2193 silently ignored. Now an error message is written to the main and panic
2196 46. There's a new ACL modifier called "logwrite" which writes to a log file
2197 as soon as it is encountered.
2199 47. Added $local_user_uid and $local_user_gid at routing time.
2201 48. Exim crashed when trying to verify a sender address that was being
2204 49. Exim was recognizing only a space character after ".include". It now also
2205 recognizes a tab character.
2207 50. Fixed several bugs in the Perl script that creates the exim.8 man page by
2208 extracting the relevant information from the specification. The man page no
2209 longer contains scrambled data for the -d option, and I've added a section
2210 at the front about calling Exim under different names.
2212 51. Added "extra_headers" argument to the "mail" command in filter files.
2214 52. Redirecting mail to an unqualified address in a Sieve filter caused Exim to
2217 53. Installed eximstats 1.29.
2219 54. Added transport_filter_timeout as a generic transport option.
2221 55. Exim no longer adds an empty Bcc: header to messages that have no To: or
2222 Cc: header lines. This was required by RFC 822, but it not required by RFC
2225 56. Exim used to add From:, Date:, and Message-Id: header lines to any
2226 incoming messages that did not have them. Now it does so only if the
2227 message originates locally, that is, if there is no associated remote host
2228 address. When Resent- header lines are present, this applies to the Resent-
2229 lines rather than the non-Resent- lines.
2231 57. Drop incoming SMTP connection after too many syntax or protocol errors. The
2232 limit is controlled by smtp_max_synprot_errors, defaulting to 3.
2234 58. Messages for configuration errors now include the name of the main
2235 configuration file - useful now that there may be more than one file in a
2236 list (.included file names were always shown).
2238 59. Change 4.21/82 (run initgroups() when starting the daemon) causes problems
2239 for those rare installations that do not start the daemon as root or run it
2240 setuid root. I've cut out the call to initgroups() if the daemon is not
2243 60. The Exim user and group can now be bound into the binary as text strings
2244 that are looked up at the start of Exim's processing.
2246 61. Applied a small patch for the Interbase code, supplied by Ard Biesheuvel.
2248 62. Added $mailstore_basename variable.
2250 63. Installed patch to sieve.c from Michael Haardt.
2252 64. When Exim failed to open the panic log after failing to open the main log,
2253 the original message it was trying to log was written to stderr and debug
2254 output, but if they were not available (the usual case in production), it
2255 was lost. Now it is written to syslog before the two lines that record the
2256 failures to open the logs.
2258 65. Users' Exim filters run in subprocesses under the user's uid. It is
2259 possible for a "deliver" command or an alias in a "personal" command to
2260 provoke an address rewrite. If logging of address rewriting is configured,
2261 this fails because the process is not running as root or exim. There may be
2262 a better way of dealing with this, but for the moment (because 4.30 needs
2263 to be released), I have disabled address rewrite logging when running a
2264 filter in a non-root, non-exim process.
2270 1. The buildconfig auxiliary program wasn't quoting the value set for
2271 HEADERS_CHARSET. This caused a compilation error complaining that 'ISO' was
2272 not defined. This bug was masked in 4.22 by the effect that was fixed in
2275 2. Some messages that were rejected after a message id was allocated were
2276 shown as "incomplete" by exigrep. It no longer does this for messages that
2277 are rejected by local_scan() or the DATA or non-SMTP ACLs.
2279 3. If a Message-ID: header used a domain literal in the ID, and Exim did not
2280 have allow_domain_literals set, the ID did not get logged in the <= line.
2281 Domain literals are now always recognized in Message-ID: header lines.
2283 4. The first argument for a ${extract expansion item is the key name or field
2284 number. Leading and trailing spaces in this item were not being ignored,
2285 causing some misleading effects.
2287 5. When deliver_drop_privilege was set, single queue runner processes started
2288 manually (i.e. by the command "exim -q") or by the daemon (which uses the
2289 same command in the process it spins off) were not dropping privilege.
2291 6. When the daemon running as "exim" started a queue runner, it always
2292 re-executed Exim in the spun-off process. This is a waste of effort when
2293 deliver_drop_privilege is set. The new process now just calls the
2294 queue-runner function directly.
2300 1. Typo in the src/EDITME file: it referred to HEADERS_DECODE_TO instead of
2303 2. Change 4.21/73 introduced a bug. The pid file path set by -oP was being
2304 ignored. Though the use of -oP was forcing the writing of a pid file, it
2305 was always written to the default place.
2307 3. If the message "no IP address found for host xxxx" is generated during
2308 incoming verification, it is now followed by identification of the incoming
2309 connection (so you can more easily find what provoked it).
2311 4. Bug fix for Sieve filters: "stop" inside a block was not working properly.
2313 5. Added some features to "harden" Exim a bit more against certain attacks:
2315 (a) There is now a build-time option called FIXED_NEVER_USERS that can
2316 be put in Local/Makefile. This is like the never_users runtime option,
2317 but it cannot be overridden. The default setting is "root".
2319 (b) If ALT_CONFIG_PREFIX is defined in Local/Makefile, it specifies a
2320 prefix string with which any file named in a -C command line option
2323 (c) If ALT_CONFIG_ROOT_ONLY is defined in Local/Makefile, root privilege
2324 is retained for -C and -D only if the caller of Exim is root. Without
2325 it, the exim user may also use -C and -D and retain privilege.
2327 (d) If DISABLE_D_OPTION is defined in Local/Makefile, the use of the -D
2328 command line option is disabled.
2330 6. Macro names set by the -D option must start with an upper case letter, just
2331 like macro names defined in the configuration file.
2333 7. Added "dereference=" facility to LDAP.
2335 8. Two instances of the typo "uknown" in the source files are fixed.
2337 9. If a PERL_COMMAND setting in Local/Makefile was not at the start of a line,
2338 the Configure-Makefile script screwed up while processing it.
2340 10. Incorporated PCRE 4.4.
2342 11. The SMTP synchronization check was not operating right at the start of an
2343 SMTP session. For example, it could not catch a HELO sent before the client
2344 waited for the greeting. There is now a check for outstanding input at the
2345 point when the greeting is written. Because of the duplex, asynchronous
2346 nature of TCP/IP, it cannot be perfect - the incorrect input may be on its
2347 way, but not yet received, when the check is performed.
2349 12. Added tcp_nodelay to make it possible to turn of the setting of TCP_NODELAY
2350 on TCP/IP sockets, because this apparently causes some broken clients to
2353 13. Installed revised OS/Makefile-CYGWIN and OS/os.c-cygwin (the .h file was
2354 unchanged) from the Cygwin maintainer.
2356 14. The code for -bV that shows what is in the binary showed "mbx" when maildir
2357 was supported instead of testing for mbx. Effectively a typo.
2359 15. The spa authenticator server code was not checking that the input it
2360 received was valid base64.
2362 16. The debug output line for the "set" modifier in ACLs was not showing the
2363 name of the variable that was being set.
2365 17. Code tidy: the variable type "vtype_string" was never used. Removed it.
2367 18. Previously, a reference to $sender_host_name did not cause a DNS reverse
2368 lookup on its own. Something else was needed to trigger the lookup. For
2369 example, a match in host_lookup or the need for a host name in a host list.
2370 Now, if $sender_host_name is referenced and the host name has not yet been
2371 looked up, a lookup is performed. If the lookup fails, the variable remains
2372 empty, and $host_lookup_failed is set to "1".
2374 19. Added "eqi" as a case-independent comparison operator.
2376 20. The saslauthd authentication condition could segfault if neither service
2377 nor realm was specified.
2379 21. If an overflowing value such as "2048M" was set for message_size_limit, the
2380 error message that was logged was misleading, and incoming SMTP
2381 connections were dropped. The message is now more accurate, and temporary
2382 errors are given to SMTP connections.
2384 22. In some error situations (such as 21 above) Exim rejects all SMTP commands
2385 (except RSET) with a 421 error, until QUIT is received. However, it was
2386 failing to send a response to QUIT.
2388 23. The HELO ACL was being run before the code for helo_try_verify_hosts,
2389 which made it impossible to use "verify = helo" in the HELO ACL. The HELO
2390 ACL is now run after the helo_try_verify_hosts code.
2392 24. "{MD5}" and "{SHA1}" are now recognized as equivalent to "{md5"} and
2393 "{sha1}" in the "crypteq" expansion condition (in fact the comparison is
2394 case-independent, so other case variants are also recognized). Apparently
2395 some systems use these upper case variants.
2397 25. If more than two messages were waiting for the same host, and a transport
2398 filter was specified for the transport, Exim sent two messages over the
2399 same TCP/IP connection, and then failed with "socket operation on non-
2400 socket" when it tried to send the third.
2402 26. Added Exim::debug_write and Exim::log_write for embedded Perl use.
2404 27. The extern definition of crypt16() in expand.c was not being excluded when
2405 the OS had its own crypt16() function.
2407 28. Added bounce_return_body as a new option, and bounce_return_size_limit
2408 as a preferred synonym for return_size_limit, both as an option and as an
2411 29. Added LIBS=-liconv to OS/Makefile-OSF1.
2413 30. Changed the default configuration ACL to relax the local part checking rule
2414 for addresses that are not in any local domains. For these addresses,
2415 slashes and pipe symbols are allowed within local parts, but the sequence
2416 /../ is explicitly forbidden.
2418 31. SPA server authentication was not clearing the challenge buffer before
2421 32. log_message in a "warn" ACL statement was writing to the reject log as
2422 well as to the main log, which contradicts the documentation and doesn't
2423 seem right (because no rejection is happening). So I have stopped it.
2425 33. Added Ard Biesheuvel's lookup code for accessing an Interbase database.
2426 However, I am unable to do any testing of this.
2428 34. Fixed an infelicity in the appendfile transport. When checking directories
2429 for a mailbox, to see if any needed to be created, it was accidentally
2430 using path names with one or more superfluous leading slashes; tracing
2431 would show up entries such as stat("///home/ph10", 0xFFBEEA48).
2433 35. If log_message is set on a "discard" verb in a MAIL or RCPT ACL, its
2434 contents are added to the log line that is written for every discarded
2435 recipient. (Previously a log_message setting was ignored.)
2437 36. The ${quote: operator now quotes the string if it is empty.
2439 37. The install script runs exim in order to find its version number. If for
2440 some reason other than non-existence or emptiness, which it checks, it
2441 could not run './exim', it was installing it with an empty version number,
2442 i.e. as "exim-". This error state is now caught, and the installation is
2445 38. An argument was missing from the function that creates an error message
2446 when Exim fails to connect to the socket for saslauthd authentication.
2447 This could cause Exim to crash, or give a corrupted message.
2449 39. Added isip, isip4, and isip6 to ${if conditions.
2451 40. The ACL variables $acl_xx are now saved with the message, and can be
2452 accessed later in routers, transports, and filters.
2454 41. The new lookup type nwildlsearch is like wildlsearch, except that the key
2455 strings in the file are not string-expanded.
2457 42. If a MAIL command specified a SIZE value that was too large to fit into an
2458 int variable, the check against message_size_limit failed. Such values are
2459 now forced to INT_MAX, which is around 2Gb for a 32-bit variable. Maybe one
2460 day this will have to be increased, but I don't think I want to be around
2461 when emails are that large.
2468 1. Removed HAVE_ICONV=yes from OS/Makefile-FreeBSD, since it seems that
2469 iconv() is not standard in FreeBSD.
2471 2. Change 4.21/17 was buggy and could cause stack overwriting on a system with
2472 IPv6 enabled. The observed symptom was a segmentation fault on return from
2473 the function os_common_find_running_interfaces() in src/os.c.
2475 3. In the check_special_case() function in daemon.c I had used "errno" as an
2476 argument name, which causes warnings on some systems. This was basically a
2477 typo, since it was named "eno" in the comments!
2479 4. The code that waits for the clock to tick (at a resolution of some fraction
2480 of a second) so as to ensure message-id uniqueness was always waiting for
2481 at least one whole tick, when it could have waited for less. [This is
2482 almost certainly not relevant at current processor speeds, where it is
2483 unlikely to ever wait at all. But we try to future-proof.]
2485 5. The function that sleeps for a time interval that includes fractions of a
2486 second contained a race. It did not block SIGALRM between setting the
2487 timer, and suspending (a couple of lines later). If the interval was short
2488 and the sigsuspend() was delayed until after it had expired, the suspension
2489 never ended. On busy systems this could lead to processes getting stuck for
2492 6. Some uncommon configurations may cause a lookup to happen in a queue runner
2493 process, before it forks any delivery processes. The open lookup caching
2494 mechanism meant that the open file or database connection was passed into
2495 the delivery process. The problem was that delivery processes always tidy
2496 up cached lookup data. This could cause a problem for the next delivery
2497 process started by the queue runner, because the external queue runner
2498 process does not know about the closure. So the next delivery process
2499 still has data in the lookup cache. In the case of a file lookup, there was
2500 no problem because closing a file descriptor in a subprocess doesn't affect
2501 the parent. However, if the lookup was caching a connection to a database,
2502 the connection was closed, and the second delivery process was likely to
2503 see errors such as "PGSQL: query failed: server closed the connection
2504 unexpectedly". The problem has been fixed by closing all cached lookups
2505 in a queue runner before running a delivery process.
2507 7. Compiler warning on Linux for the second argument of iconv(), which doesn't
2508 seem to have the "const" qualifier which it has on other OS. I've
2511 8. Change 4.21/2 was too strict. It is only if there are two authenticators
2512 *of the same type* (client or server) with the same public name that an
2513 error should be diagnosed.
2515 9. When Exim looked up a host name for an IP address, but failed to find the
2516 original IP address when looking up the host name (a safety check), it
2517 output the message "<ip address> does not match any IP for NULL", which was
2518 confusing, to say the least. The bug was that the host name should have
2519 appeared instead of "NULL".
2521 10. Since release 3.03, if Exim is called by a uid other than root or the Exim
2522 user that is built into the binary, and the -C or -D options is used, root
2523 privilege is dropped before the configuration file is read. In addition,
2524 logging is switched to stderr instead of the normal log files. If the
2525 configuration then re-defines the Exim user, the unprivileged environment
2526 is probably not what is expected, so Exim logs a panic warning message (but
2529 However, if deliver_drop_privilege is set, the unprivileged state may well
2530 be exactly what is intended, so the warning has been cut out in that case,
2531 and Exim is allowed to try to write to its normal log files.
2537 1. smtp_return_error_details was not giving details for temporary sender
2538 or receiver verification errors.
2540 2. Diagnose a configuration error if two authenticators have the same public
2543 3. Exim used not to create the message log file for a message until the first
2544 delivery attempt. This could be confusing when incoming messages were held
2545 for policy or load reasons. The message log file is now created at the time
2546 the message is received, and an initial "Received" line is written to it.
2548 4. The automatically generated man page for command line options had a minor
2549 bug that caused no ill effects; however, a more serious problem was that
2550 the procedure for building the man page automatically didn't always
2551 operate. Consequently, release 4.20 contains an out-of-date version. This
2552 shouldn't happen again.
2554 5. When building Exim with embedded Perl support, the script that builds the
2555 Makefile was calling 'perl' to find its compile-time parameters, ignoring
2556 any setting of PERL_COMMAND in Local/Makefile. This is now fixed.
2558 6. The freeze_tell option was not being used for messages that were frozen on
2559 arrival, either by an ACL or by local_scan().
2561 7. Added the smtp_incomplete_transaction log selector.
2563 8. After STARTTLS, Exim was not forgetting that it had advertised AUTH, so it
2564 was accepting AUTH without a new EHLO.
2566 9. Added tls_remember_esmtp to cope with YAEB. This allows AUTH and other
2567 ESMTP extensions after STARTTLS without a new EHLO, in contravention of the
2570 10. Logging of TCP/IP connections (when configured) now happens in the main
2571 daemon process instead of the child process, so that the TCP/IP connection
2572 count is more accurate (but it can never be perfect).
2574 11. The use of "drop" in a nested ACL was not being handled correctly in the
2575 outer ACL. Now, if condition failure induced by the nested "drop" causes
2576 the outer ACL verb to deny access ("accept" or "discard" after "endpass",
2577 or "require"), the connection is dropped.
2579 12. Similarly, "discard" in a nested ACL wasn't being handled. A nested ACL
2580 that yield "discard" can now be used with an "accept" or a "discard" verb,
2581 but an error is generated for any others (because I can't see a useful way
2582 to define what should happen).
2584 13. When an ACL is read dynamically from a file (or anywhere else), the lines
2585 are now processed in the same way as lines in the Exim configuration file.
2586 In particular, continuation lines are supported.
2588 14. Added the "dnslists = a.b.c!=n.n.n.n" feature.
2590 15. Added -ti meaning -t -i.
2592 16. Check for letters, digits, hyphens, and dots in the names of dnslist
2593 domains, and warn by logging if others are found.
2595 17. At least on BSD, alignment is not guarenteed for the array of ifreq's
2596 returned from GIFCONF when Exim is trying to find the list of interfaces on
2597 a host. The code in os.c has been modified to copy each ifreq to an aligned
2598 structure in all cases.
2600 Also, in some cases, the returned ifreq's were being copied to a 'struct
2601 ifreq' on the stack, which was subsequently passed to host_ntoa(). That
2602 means the last couple of bytes of an IPv6 address could be chopped if the
2603 ifreq contained only a normal sockaddr (14 bytes storage).
2605 18. Named domain lists were not supported in the hosts_treat_as_local option.
2606 An entry such as +xxxx was not recognized, and was treated as a literal
2609 19. Ensure that header lines added by a DATA ACL are included in the reject log
2610 if the ACL subsequently rejects the message.
2612 20. Upgrade the cramtest.pl utility script to use Digest::MD5 instead of just
2613 MD5 (which is deprecated).
2615 21. When testing a filter file using -bf, Exim was writing a message when it
2616 took the sender from a "From " line in the message, but it was not doing so
2617 when it took $return_path from a Return-Path: header line. It now does.
2619 22. If the contents of a "message" modifier for a "warn" ACL verb do not begin
2620 with a valid header line field name (a series of printing characters
2621 terminated by a colon, Exim now inserts X-ACL-Warn: at the beginning.
2623 23. Changed "disc" in the source to "disk" to conform to the documentation and
2624 the book and for uniformity.
2626 24. Ignore Sendmail's -Ooption=value command line item.
2628 25. When execve() failed while trying to run a command in a pipe transport,
2629 Exim was returning EX_UNAVAILBLE (69) from the subprocess. However, this
2630 could be confused with a return value of 69 from the command itself. This
2631 has been changed to 127, the value the shell returns if it is asked to run
2632 a non-existent command. The wording for the related log line suggests a
2633 non-existent command as the problem.
2635 26. If received_header_text expands to an empty string, do not add a Received:
2636 header line to the message. (Well, it adds a token one on the spool, but
2637 marks it "old" so that it doesn't get used or transmitted.)
2639 27. Installed eximstats 1.28 (addition of -nt option).
2641 28. There was no check for failure on the call to getsockname() in the daemon
2642 code. This can fail if there is a shortage of resources on the system, with
2643 ENOMEM, for example. A temporary error is now given on failure.
2645 29. Contrary to the C standard, it seems that in some environments, the
2646 equivalent of setlocale(LC_ALL, "C") is not obeyed at the start of a C
2647 program. Exim now does this explicitly; it affects the formatting of
2648 timestamps using strftime().
2650 30. If exiqsumm was given junk data, it threw up some uninitialized variable
2651 complaints. I've now initialized all the variables, to avoid this.
2653 32. Header lines added by a system filter were not being "seen" during
2654 transport-time rewrites.
2656 33. The info_callback() function passed to OpenSSL is set up with type void
2657 (*)(SSL *, int, int), as described somewhere. However, when calling the
2658 function (actually a macro) that sets it up, the type void(*)() is
2659 expected. I've put in a cast to prevent warnings from picky compilers.
2661 34. If a DNS black list lookup found a CNAME record, but there were no A
2662 records associated with the domain it pointed at, Exim crashed.
2664 35. If a DNS black list lookup returned more than one A record, Exim ignored
2665 all but the first. It now scans all returned addresses if a particular IP
2666 value is being sought. In this situation, the contents of the
2667 $dnslist_value variable are a list of all the addresses, separated by a
2670 36. Tightened up the rules for host name lookups using reverse DNS. Exim used
2671 to accept a host name and all its aliases if the forward lookup for any of
2672 them yielded the IP address of the incoming connection. Now it accepts only
2673 those names whose forward lookup yields the correct IP address. Any other
2674 names are discarded. This closes a loophole whereby a rogue DNS
2675 administrator could create reverse DNS records to break through a
2676 wildcarded host restriction in an ACL.
2678 37. If a user filter or a system filter that ran in a subprocess used any of
2679 the numerical variables ($1, $2 etc), or $thisaddress, in a pipe command,
2680 the wrong values were passed to the pipe command ($thisaddress had the
2681 value of $0, $0 had the value of $1, etc). This bug was introduced by
2682 change 4.11/101, and not discovered because I wrote an inadequate test. :-(
2684 38. Improved the line breaking for long SMTP error messages from ACLs.
2685 Previously, if there was no break point between 40 and 75 characters, Exim
2686 left the rest of the message alone. Two changes have been made: (a) I've
2687 reduced the minimum length to 35 characters; (b) if it can't find a break
2688 point between 35 and 75 characters, it looks ahead and uses the first one
2689 that it finds. This may give the occasional overlong line, but at least the
2690 remaining text gets split now.
2692 39. Change 82 of 4.11 was unimaginative. It assumed the limit on the number of
2693 file descriptors might be low, and that setting 1000 would always raise it.
2694 It turns out that in some environments, the limit is already over 1000 and
2695 that lowering it causes trouble. So now Exim takes care not to decrease it.
2697 40. When delivering a message, the value of $return_path is set to $sender_
2698 address at the start of routing (routers may change the value). By an
2699 oversight, this default was not being set up when an address was tested by
2700 -bt or -bv, which affected the outcome if any router or filter referred to
2703 41. The idea of the "warn" ACL verb is that it adds a header or writes to the
2704 log only when "message" or "log_message" are set. However, if one of the
2705 conditions was an address verification, or a call to a nested ACL, the
2706 messages generated by the underlying test were being passed through. This
2707 no longer happens. The underlying message is available in $acl_verify_
2708 message for both "message" and "log_message" expansions, so it can be
2709 passed through if needed.
2711 42. Added RFC 2047 interpretation of header lines for $h_ expansions, with a
2712 new expansion $bh_ to give the encoded byte string without charset
2713 translation. Translation happens only if iconv() is available; HAVE_ICONV
2714 indicates this at build time. HEADERS_CHARSET gives the charset to
2715 translate to; headers_charset can change it in the configuration, and
2716 "headers charset" can change it in an individual filter file.
2718 43. Now that we have a default RFC 2047 charset (see above), the code in Exim
2719 that creates RFC 2047 encoded "words" labels them as that charset instead
2720 of always using iso-8859-1. The cases are (i) the explicit ${rfc2047:
2721 expansion operator; (ii) when Exim creates a From: line for a local
2722 message; (iii) when a header line is rewritten to include a "phrase" part.
2724 44. Nasty bug in exiqsumm: the regex to skip already-delivered addresses was
2725 buggy, causing it to skip the first lines of messages whose message ID
2726 ended in 'D'. This would not have bitten before Exim release 4.14, because
2727 message IDs were unlikely to end in 'D' before then. The effect was to have
2728 incorrect size information for certain domains.
2730 45. #include "config.h" was missing at the start of the crypt16.c module. This
2731 caused trouble on Tru64 (aka OSF1) systems, because HAVE_CRYPT16 was not
2734 46. If there was a timeout during a "random" callout check, Exim treated it as
2735 a failure of the random address, and carried on sending RSET and the real
2736 address. If the delay was just some slowness somewhere, the response to the
2737 original RCPT would be taken as a response to RSET and so on, causing
2738 mayhem of various kinds.
2740 47. Change 50 for 4.20 was a heap of junk. I don't know what I was thinking
2741 when I implemented it. It didn't allow for the fact that some option values
2742 may legitimatetly be negative (e.g. size_addition), and it didn't even do
2743 the right test for positive values.
2745 48. Domain names in DNS records are case-independent. Exim always looks them up
2746 in lower case. Some resolvers return domain names in exactly the case they
2747 appear in the zone file, that is, they may contain uppercase letters. Not
2748 all resolvers do this - some return always lower case. Exim was treating a
2749 change of case by a resolver as a change of domain, similar to a widening
2750 of a domain abbreviation. This triggered its re-routing code and so it was
2751 trying to route what was effectively the same domain again. This normally
2752 caused routing to fail (because the router wouldn't handle the domain
2753 twice). Now Exim checks for this case specially, and just changes the
2754 casing of the domain that it ultimately uses when it transmits the message
2757 49. Added Sieve (RFC 3028) support, courtesy of Michael Haardt's contributed
2760 50. If a filter generated a file delivery with a non-absolute name (possible if
2761 no home directory exists for the router), the forbid_file option was not
2764 51. Added '&' feature to dnslists, to provide bit mask matching in addition to
2765 the existing equality matching.
2767 52. Exim was using ints instead of ino_t variables in some places where it was
2768 dealing with inode numbers.
2770 53. If TMPDIR is defined in Local/Makefile (default in src/EDITME is
2771 TMPDIR="/tmp"), Exim checks for the presence of an environment variable
2772 called TMPDIR, and if it finds it is different, it changes its value.
2774 54. The smtp_printf() function is now made available to local_scan() so
2775 additional output lines can be written before returning. There is also an
2776 smtp_fflush() function to enable the detection of a dropped connection.
2777 The variables smtp_input and smtp_batched_input are exported to
2780 55. Changed the default runtime configuration: the message "Unknown user"
2781 has been removed from the ACL, and instead placed on the localuser router,
2782 using the cannot_route_message feature. This means that any verification
2783 failures that generate their own messages won't get overridden. Similarly,
2784 the "Unrouteable address" message that was in the ACL for unverifiable
2785 relay addresses has also been removed.
2787 56. Added hosts_avoid_esmtp to the smtp transport.
2789 57. The exicyclog script was not checking for the esoteric option
2790 CONFIGURE_FILE_USE_EUID in the Local/Makefile. It now does this, but it
2791 will work only if exicyclog is run under the appropriate euid.
2793 58. Following a discussion on the list, the rules by which Exim recognises line
2794 endings on incoming messages have been changed. The -dropcr and drop_cr
2795 options are now no-ops, retained only for backwards compatibility. The
2796 following line terminators are recognized: LF CRLF CR. However, special
2797 processing applies to CR:
2799 (i) The sequence CR . CR does *not* terminate an incoming SMTP message,
2800 nor a local message in the state where . is a terminator.
2802 (ii) If a bare CR is encountered in a header line, an extra space is added
2803 after the line terminator so as not to end the header. The reasoning
2804 behind this is that bare CRs in header lines are most likely either
2805 to be mistakes, or people trying to play silly games.
2807 59. The size of a message, as listed by "-bp" or in the Exim monitor window,
2808 was being incorrectly given as 18 bytes larger than it should have been.
2809 This is a VOB (very old bug).
2811 60. This may never have affected anything current, but just in case it has:
2812 When the local host is found other than at the start of a list of hosts,
2813 the local host, those with the same MX, and any that follow, are discarded.
2814 When the list in question was part of a longer list of hosts, the following
2815 hosts (not currently being processed) were also being discarded. This no
2816 longer happens. I'm not sure if this situation could ever has previously
2819 61. Added the "/MX" feature to lists of hosts in the manualroute and query
2822 62. Whenever Exim generates a new message, it now adds an Auto-Submitted:
2823 header. This is something that is recommended in a new Internet Draft, and
2824 is something that is documented as being done by Sendmail. There are two
2825 possible values. For messages generated by the autoreply transport, Exim
2828 Auto-Submitted: auto-replied
2830 whereas for all other generated messages (e.g. bounces) it adds
2832 Auto-Submitted: auto-generated
2834 63. The "personal" condition in filters now includes a test for the
2835 Auto-Submitted: header. If it contains the string "auto-" the message it
2836 not considered personal.
2838 64. Added rcpt_include_affixes as a generic transport option.
2840 65. Added queue_only_override (default true).
2842 66. Added the syslog_duplication option.
2844 67. If what should have been the first header line of a message consisted of
2845 a space followed by a colon, Exim was mis-interpreting it as a header line.
2846 It isn't of course - it is syntactically invalid and should therefore be
2847 treated as the start of the message body. The misbehaviour could have
2848 caused a number of strange effects, including loss of data in subsequent
2849 header lines, and spool format errors.
2851 68. Formerly, the AUTH parameter on a MAIL command was trusted only if the
2852 client host had authenticated. This control can now be exercised by an ACL
2853 for more flexibility.
2855 69. By default, callouts do not happen when testing with -bh. There is now a
2856 variant, -bhc, which does actually run the callout code, including
2857 consulting and updating the callout cache.
2859 70. Added support for saslauthd authentication, courtesy of Alexander
2862 71. If statvfs() failed on the spool or log directories while checking their
2863 size for availability, Exim confusingly gave the error "space shortage".
2864 Furthermore, in debugging mode it crashed with a floating point exception.
2865 These checks are done if check_{spool,log}_{space,inodes} are set, and when
2866 an SMTP message arrives with SIZE= on the MAIL command. As this is a really
2867 serious problem, Exim now writes to the main and panic logs when this
2868 happens, with details of the failure. It then refuses to accept the
2869 incoming message, giving the message "spool directory problem" or "log
2870 directory problem" with a 421 code for SMTP messages.
2872 72. When Exim is about to re-exec itself, it ensures that the file descriptors
2873 0, 1, and 2 exist, because some OS complain for execs without them (see
2874 ChangeLog 4.05/30). If necessary, Exim opens /dev/null to use for these
2875 descriptors. However, the code omitted to check that the open succeeded,
2876 causing mysterious errors if for some reason the permissions on /dev/null
2877 got screwed. Now Exim writes a message to the main and panic logs, and
2878 bombs out if it can't open /dev/null.
2880 73. Re-vamped the way daemon_smtp_port, local_interfaces, and -oX work and
2881 interact so that it is all more flexible. It is supposed to remain
2882 backwards compatible. Also added extra_local_interfaces.
2884 74. Invalid data sent to a SPA (NTLM) server authenticator could cause the code
2885 to bomb out with an assertion failure - to the client this appears as a
2886 connection drop. This problem occurs in the part of the code that was taken
2887 from the Samba project. Fortunately, the assertion is in a very simple
2888 function, so I have fixed this by reproducing the function inline in the
2889 one place where it is called, and arranging for authentication to fail
2890 instead of killing the process with assert().
2892 75. The SPA client code was not working when the server requested OEM rather
2893 than Unicode encoding.
2895 76. Added code to make require_files with a specific uid setting more usable in
2896 the case where statting the file as root fails - usually a non-root-mounted
2897 NFS file system. When this happens and the failure is EACCES, Exim now
2898 forks a subprocess and does the per-uid checking as the relevant uid.
2900 77. Added process_log_path.
2902 78. If log_file_path was not explicitly set, a setting of check_log_space or
2903 check_log_inodes was ignored.
2905 79. If a space check for the spool or log partitions fails, the incident is now
2906 logged. Of course, in the latter case the data may get lost...
2908 80. Added the %p formatting code to string_format() so that it can be used to
2909 print addresses in debug_print(). Adjusted all the address printing in the
2910 debugging in store.c to use %p rather than %d.
2912 81. There was a concern that a line of code in smtp_in.c could overflow a
2913 buffer if a HELO/EHLO command was given followed by 500 or so spaces. As
2914 initially expressed, the concern was not well-founded, because trailing
2915 spaces are removed early. However, if the trailing spaces were followed by
2916 a NULL, they did not get removed, so the overflow was possible. Two fixes
2919 (a) I re-wrote the offending code in a cleaner fashion.
2920 (b) If an incoming SMTP command contains a NULL character, it is rejected
2923 82. When Exim changes uid/gid to the Exim user at daemon start time, it now
2924 runs initgroups(), so that if the Exim user is in any additional groups,
2925 they will be used during message reception.
2931 The change log for 4.20 and earlier releases has been archived.