1 $Cambridge: exim/doc/doc-txt/ChangeLog,v 1.145 2005/05/25 20:32:44 tom 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.
22 PH/03 The warning log line about a condition test deferring for a "warn" verb
23 was being output only once per connection, rather than after each
24 occurrence (because it was using the same function as for successful
25 "warn" verbs). This seems wrong, so I have changed it.
27 TF/02 Two buglets in acl.c which caused Exim to read a few bytes of memory that
28 it should not have, which might have caused a crash in the right
29 circumstances, but probably never did.
31 PH/04 Installed a modified version of Tony Finch's patch to make submission
32 mode fix the return path as well as the Sender: header line, and to
33 add a /name= option so that you can make the user's friendly name appear
36 TF/03 Added the control = fakedefer ACL modifier.
38 TF/04 Added the ratelimit ACL condition. See NewStuff for details.
40 TK/02 Rewrote SPF support to work with libspf2 versions >1.2.0.
42 TK/03 Merged latest SRS patch from Miles Wilton.
44 PH/05 There's a shambles in IRIX6 - it defines EX_OK in unistd.h which conflicts
45 with the definition in sysexits.h (which is #included earlier).
46 Fortunately, Exim does not actually use EX_OK. The code used to try to
47 preserve the sysexits.h value, by assumimg that macro definitions were
48 scanned for macro replacements. I have been disabused of this notion,
49 so now the code just undefines EX_OK before #including unistd.h.
51 PH/06 There is a timeout for writing blocks of data, set by, e.g. data_timeout
52 in the smtp transport. When a block could not be written in a single
53 write() function, the timeout was being re-applied to each part-write.
54 This seems wrong - if the receiver was accepting one byte at a time it
55 would take for ever. The timeout is now adjusted when this happens. It
56 doesn't have to be particularly precise.
58 TK/04 Added simple SPF lookup method in EXPERIMENTAL_SPF. See NewStuff for
59 details. Thanks to Chris Webb <chris@arachsys.com> for the patch!
65 TK/01 Added Yahoo DomainKeys support via libdomainkeys. See
66 doc/experimental-spec.txt for details. (http://domainkeys.sf.net)
68 TK/02 Fix ACL "control" statement not being available in MIME ACL.
70 TK/03 Fix ACL "regex" condition not being available in MIME ACL.
72 PH/01 Installed a patch from the Sieve maintainer that allows -bf to be used
73 to test Sieve filters that use "vacation".
75 PH/02 Installed a slightly modified version of Nikos Mavrogiannopoulos' patch
76 that changes the way the GnuTLS parameters are stored in the cache file.
77 The new format can be generated externally. For backward compatibility,
78 if the data in the cache doesn't make sense, Exim assumes it has read an
79 old-format file, and it generates new data and writes a new file. This
80 means that you can't go back to an older release without removing the
83 PH/03 A redirect router that has both "unseen" and "one_time" set does not
84 work if there are any delivery delays because "one_time" forces the
85 parent to be marked "delivered", so its unseen clone is never tried
86 again. For this reason, Exim now forbids the simultaneous setting of
89 PH/04 Change 4.11/85 fixed an obscure bug concerned with addresses that are
90 redirected to themselves ("homonym" addresses). Read the long ChangeLog
91 entry if you want to know the details. The fix, however, neglected to
92 consider the case when local delivery batching is involved. The test for
93 "previously delivered" was not happening when checking to see if an
94 address could be batched with a previous (undelivered) one; under
95 certain circumstances this could lead to multiple deliveries to the same
98 PH/05 Renamed the macro SOCKLEN_T as EXIM_SOCKLEN_T because AIX uses SOCKLEN_T
99 in its include files, and this causes problems building Exim.
101 PH/06 A number of "verify =" ACL conditions have no options (e.g. verify =
102 header_syntax) but Exim was just ignoring anything given after a slash.
103 In particular, this caused confusion with an attempt to use "verify =
104 reverse_host_lookup/defer_ok". An error is now given when options are
105 supplied for verify items that do not have them. (Maybe reverse_host_
106 lookup should have a defer_ok option, but that's a different point.)
108 PH/07 Increase the size of the buffer for incoming SMTP commands from 512 (as
109 defined by RFC 821) to 2048, because there were problems with some AUTH
110 commands, and RFC 1869 says the size should be increased for extended
111 SMTP commands that take arguments.
113 PH/08 Added ${dlfunc dynamically loaded function for expansion (code from Tony
116 PH/09 Previously, an attempt to use ${perl when it wasn't compiled gave an
117 "unknown" error; now it says that the functionality isn't in the binary.
119 PH/10 Added a nasty fudge to try to recognize and flatten LDAP passwords in
120 an address' error message when a string expansion fails (syntax or
121 whatever). Otherwise the password may appear in the log. Following change
122 PH/42 below, there is no longer a chance of it appearing in a bounce
125 PH/11 Installed exipick version 20050225.0 from John Jetmore.
127 PH/12 If the last host in a fallback_hosts list was multihomed, only the first
128 of its addresses was ever tried. (Bugzilla bug #2.)
130 PH/13 If "headers_add" in a transport didn't end in a newline, Exim printed
131 the result incorrectly in the debug output. (It correctly added a newline
132 to what was transported.)
134 TF/01 Added $received_time.
136 PH/14 Modified the default configuration to add an acl_smtp_data ACL, with
137 commented out examples of how to interface to a virus scanner and to
138 SpamAssassin. Also added commented examples of av_scanner and
139 spamd_address settings.
141 PH/15 Further to TK/02 and TK/03 above, tidied up the tables of what conditions
142 and controls are allowed in which ACLs. There were a couple of minor
143 errors. Some of the entries in the conditions table (which is a table of
144 where they are NOT allowed) were getting very unwieldy; rewrote them as a
145 negation of where the condition IS allowed.
147 PH/16 Installed updated OS/os.c-cygwin from the Cygwin maintainer.
149 PH/17 The API for radiusclient changed at release 0.4.0. Unfortunately, the
150 header file does not have a version number, so I've had to invent a new
151 value for RADIUS_LIB_TYPE, namely "RADIUSCLIENTNEW" to request the new
152 API. The code is untested by me (my Linux distribution still has 0.3.2 of
153 radiusclient), but it was contributed by a Radius user.
155 PH/18 Installed Lars Mainka's patch for the support of CRL collections in
156 files or directories, for OpenSSL.
158 PH/19 When an Exim process that is running as root has to create an Exim log
159 file, it does so in a subprocess that runs as exim:exim so as to get the
160 ownership right at creation (otherwise, other Exim processes might see
161 the file with the wrong ownership). There was no test for failure of this
162 fork() call, which would lead to the process getting stuck as it waited
163 for a non-existent subprocess. Forks do occasionally fail when resources
164 run out. I reviewed all the other calls to fork(); they all seem to check
167 PH/20 When checking for unexpected SMTP input at connect time (before writing
168 the banner), Exim was not dealing correctly with a non-positive return
169 from the read() function. If the client had disconnected by this time,
170 the result was a log entry for a synchronization error with an empty
171 string after "input=" when read() returned zero. If read() returned -1
172 (an event I could not check), uninitialized data bytes were printed.
173 There were reports of junk text (parts of files, etc) appearing after
176 PH/21 Added acl_not_smtp_mime to allow for MIME scanning for non-SMTP messages.
178 PH/22 Added support for macro redefinition, and (re)definition in between
179 driver and ACL definitions.
181 PH/23 The cyrus_sasl authenticator was expanding server_hostname, but then
182 forgetting to use the resulting value; it was using the unexpanded value.
184 PH/24 The cyrus_sasl authenticator was advertising mechanisms for which it
185 hadn't been configured. The fix is from Juergen Kreileder, who
186 understands it better than I do:
188 "Here's what I see happening with three configured cyrus_sasl
189 authenticators configured (plain, login, cram-md5):
191 On startup auth_cyrus_sasl_init() gets called for each of these.
192 This means three calls to sasl_listmech() without a specified mech_list.
193 => SASL tests which mechs of all available mechs actually work
194 => three warnings about OTP not working
195 => the returned list contains: plain, login, cram-md5, digest-md5, ...
197 With the patch, sasl_listmech() also gets called three times. But now
198 SASL's mech_list option is set to the server_mech specified in the the
199 authenticator. Or in other words, the answer from sasl_listmech()
200 gets limited to just the mech you're testing for (which is different
202 => the return list contains just 'plain' or 'login', 'cram-md5' or
203 nothing depending on the value of ob->server_mech.
205 I've just tested the patch: Authentication still works fine,
206 unavailable mechs specified in the exim configuration are still
207 caught, and the auth.log warnings about OTP are gone."
209 PH/25 When debugging is enabled, the contents of the command line are added
210 to the debugging output, even when log_selector=+arguments is not
213 PH/26 Change scripts/os-type so that when "uname -s" returns just "GNU", the
214 answer is "GNU", and only if the return is "GNU/something" is the answer
217 PH/27 $acl_verify_message is now set immediately after the failure of a
218 verification in an ACL, and so is available in subsequent modifiers. In
219 particular, the message can be preserved by coding like this:
221 warn !verify = sender
222 set acl_m0 = $acl_verify_message
224 Previously, $acl_verify_message was set only while expanding "message"
225 and "log_message" when a very denied access.
227 PH/28 Modified OS/os.c-Linux with
229 -#ifndef OS_LOAD_AVERAGE
230 +#if !defined(OS_LOAD_AVERAGE) && defined(__linux__)
232 to make Exim compile on kfreebsd-gnu. (I'm totally confused about the
233 nomenclature these days.)
235 PH/29 Installed patch from the Sieve maintainer that adds the options
236 sieve_useraddress and sieve_subaddress to the redirect router.
238 PH/30 In these circumstances:
239 . Two addresses routed to the same list of hosts;
240 . First host does not offer TLS;
241 . First host accepts first address;
242 . First host gives temporary error to second address;
243 . Second host offers TLS and a TLS session is established;
244 . Second host accepts second address.
245 Exim incorrectly logged both deliveries with the TLS parameters (cipher
246 and peerdn, if requested) that were in fact used only for the second
249 PH/31 When doing a callout as part of verifying an address, Exim was not paying
250 attention to any local part prefix or suffix that was matched by the
251 router that accepted the address. It now behaves in the same way as it
252 does for delivery: the affixes are removed from the local part unless
253 rcpt_include_affixes is set on the transport.
255 PH/32 Add the sender address, as F=<...>, to the log line when logging a
256 timeout during the DATA phase of an incoming message.
258 PH/33 Sieve envelope tests were broken for match types other than :is. I have
259 applied a patch sanctioned by the Sieve maintainer.
261 PH/34 Change 4.50/80 broke Exim in that it could no longer handle cases where
262 the uid or gid is negative. A case of a negative gid caused this to be
263 noticed. The fix allows for either to be negative.
265 PH/35 ACL_WHERE_MIME is now declared unconditionally, to avoid too much code
266 clutter, but the tables that are indexed by ACL_WHERE_xxx values had been
269 PH/36 The change PH/12 above was broken. Fixed it.
271 PH/37 Exim used to check for duplicate addresses in the middle of routing, on
272 the grounds that routing the same address twice would always produce the
273 same answer. This might have been true once, but it is certainly no
274 longer true now. Routing a child address may depend on the previous
275 routing that produced that child. Some complicated redirection strategies
276 went wrong when messages had multiple recipients, and made Exim's
277 behaviour dependent on the order in which the addresses were given.
279 I have moved the duplicate checking until after the routing is complete.
280 Exim scans the addresses that are assigned to local and remote
281 transports, and removes any duplicates. This means that more work will be
282 done, as duplicates will always all be routed, but duplicates are
283 presumably rare, so I don't expect this is of any significance.
285 For deliveries to pipes, files, and autoreplies, the duplicate checking
286 still happens during the routing process, since they are not going to be
289 PH/38 Installed a patch from Ian Freislich, with the agreement of Tom Kistner.
290 It corrects a timeout issue with spamd. This is Ian's comment: "The
291 background is that sometimes spamd either never reads data from a
292 connection it has accepted, or it never writes response data. The exiscan
293 spam.[ch] uses a 3600 second timeout on spamd socket reads, further, it
294 blindly assumes that writes won't block so it may never time out."
296 PH/39 Allow G after quota size as well as K and M.
298 PH/40 The value set for $authenticated_id in an authenticator may not contain
299 binary zeroes or newlines because the value is written to log lines and
300 to spool files. There was no check on this. Now the value is run through
301 the string_printing() function so that such characters are converted to
302 printable escape sequences.
304 PH/41 $message_linecount is a new variable that contains the total number of
305 lines in the message. Compare $body_linecount, which is the count for the
308 PH/42 Exim no longer gives details of delivery errors for specific addresses in
309 bounce and delay warning messages, except in certain special cases, which
312 (a) An SMTP error message from a remote host;
313 (b) A message specified in a :fail: redirection;
314 (c) A message specified in a "fail" command in a system filter;
315 (d) A message specified in a FAIL return from the queryprogram router;
316 (e) A message specified by the cannot_route_message router option.
318 In these cases only, Exim does include the error details in bounce and
319 warning messages. There are also a few cases where bland messages such
320 as "unrouteable address" or "local delivery error" are given.
322 PH/43 $value is now also set for the "else" part of a ${run expansion.
324 PH/44 Applied patch from the Sieve maintainer: "The vacation draft is still
325 being worked on, but at least Exim now implements the latest version to
328 PH/45 In a pipe transport, although a timeout while waiting for the pipe
329 process to complete was treated as a delivery failure, a timeout while
330 writing the message to the pipe was logged, but erroneously treated as a
331 successful delivery. Such timeouts include transport filter timeouts. For
332 consistency with the overall process timeout, these timeouts are now
333 treated as errors, giving rise to delivery failures by default. However,
334 there is now a new Boolean option for the pipe transport called
335 timeout_defer, which, if set TRUE, converts the failures into defers for
336 both kinds of timeout. A transport filter timeout is now identified in
339 PH/46 The "scripts/Configure-config.h" script calls "make" at one point. On
340 systems where "make" and "gmake" are different, calling "gmake" at top
341 level broke things. I've arranged for the value of $(MAKE) to be passed
342 from the Makefile to this script so that it can call the same version of
346 A note about Exim versions 4.44 and 4.50
347 ----------------------------------------
349 Exim 4.50 was meant to be the next release after 4.43. It contains a lot of
350 changes of various kinds. As a consequence, a big documentation update was
351 needed. This delayed the release for rather longer than seemed good, especially
352 in the light of a couple of (minor) security issues. Therefore, the changes
353 that fixed bugs were backported into 4.43, to create a 4.44 maintenance
354 release. So 4.44 and 4.50 are in effect two different branches that both start
357 I have left the 4.50 change log unchanged; it contains all the changes since
358 4.43. The change log for 4.44 is below; many of its items are identical to
359 those for 4.50. This seems to be the most sensible way to preserve the
360 historical information.
366 1. Minor wording change to the doc/README.SIEVE file.
368 2. Change 4.43/35 introduced a bug: if quota_filecount was set, the
369 computation of the current number of files was incorrect.
371 3. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
372 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
375 4. Give more explanation in the error message when the command for a transport
376 filter fails to execute.
378 5. There are several places where Exim runs a non-Exim command in a
379 subprocess. The SIGUSR1 signal should be disabled for these processes. This
380 was being done only for the command run by the queryprogram router. It is
381 now done for all such subprocesses. The other cases are: ${run, transport
382 filters, and the commands run by the lmtp and pipe transports.
384 6. Added CONFIGURE_GROUP build-time option.
386 7. Some older OS have a limit of 256 on the maximum number of file
387 descriptors. Exim was using setrlimit() to set 1000 as a large value
388 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
389 systems. I've change it so that if it can't get 1000, it tries for 256.
391 8. "control=submission" was allowed, but had no effect, in a DATA ACL. This
392 was an oversight, and furthermore, ever since the addition of extra
393 controls (e.g. 4.43/32), the checks on when to allow different forms of
394 "control" were broken. There should now be diagnostics for all cases when a
395 control that does not make sense is encountered.
397 9. Added the /retain_sender option to "control=submission".
399 10. $recipients is now available in the predata ACL (oversight).
401 11. Tidy the search cache before the fork to do a delivery from a message
402 received from the command line. Otherwise the child will trigger a lookup
403 failure and thereby defer the delivery if it tries to use (for example) a
404 cached ldap connection that the parent has called unbind on.
406 12. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
407 of $address_data from the recipient verification was clobbered by the
410 13. The value of address_data from a sender verification is now available in
411 $sender_address_data in subsequent conditions in the ACL statement.
413 14. Added forbid_sieve_filter and forbid_exim_filter to the redirect router.
415 15. Added a new option "connect=<time>" to callout options, to set a different
418 16. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
419 was its contents. (It was OK if the option was not defined at all.)
421 17. A "Completed" log line is now written for messages that are removed from
422 the spool by the -Mrm option.
424 18. New variables $sender_verify_failure and $recipient_verify_failure contain
425 information about exactly what failed.
427 19. Added -dd to debug only the daemon process.
429 20. Incorporated Michael Haardt's patch to ldap.c for improving the way it
430 handles timeouts, both on the server side and network timeouts. Renamed the
431 CONNECT parameter as NETTIMEOUT (but kept the old name for compatibility).
433 21. The rare case of EHLO->STARTTLS->HELO was setting the protocol to "smtp".
434 It is now set to "smtps".
436 22. $host_address is now set to the target address during the checking of
439 23. When checking ignore_target_hosts for an ipliteral router, no host name was
440 being passed; this would have caused $sender_host_name to have been used if
441 matching the list had actually called for a host name (not very likely,
442 since this list is usually IP addresses). A host name is now passed as
445 24. Changed the calls that set up the SIGCHLD handler in the daemon to use the
446 code that specifies a non-restarting handler (typically sigaction() in
447 modern systems) in an attempt to fix a rare and obscure crash bug.
449 25. Narrowed the window for a race in the daemon that could cause it to ignore
450 SIGCHLD signals. This is not a major problem, because they are used only to
451 wake it up if nothing else does.
453 26. A malformed maildirsize file could cause Exim to calculate negative values
454 for the mailbox size or file count. Odd effects could occur as a result.
455 The maildirsize information is now recalculated if the size or filecount
458 27. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
459 support for a long time. Removed HAVE_SYS_VFS_H.
461 28. Installed the latest version of exipick from John Jetmore.
463 29. In an address list, if the pattern was not a regular expression, an empty
464 subject address (from a bounce message) matched only if the pattern was an
465 empty string. Non-empty patterns were not even tested. This was the wrong
466 because it is perfectly reasonable to use an empty address as part of a
467 database query. An empty address is now tested by patterns that are
468 lookups. However, all the other forms of pattern expect the subject to
469 contain a local part and a domain, and therefore, for them, an empty
470 address still always fails if the pattern is not itself empty.
472 30. Exim went into a mad DNS loop when attempting to do a callout where the
473 host was specified on an smtp transport, and looking it up yielded more
476 31. Re-factored the code for checking spool and log partition space into a
477 function that finds that data and another that does the check. The former
478 is then used to implement four new variables: $spool_space, $log_space,
479 $spool_inodes, and $log_inodes.
481 32. The RFC2047 encoding function was originally intended for short strings
482 such as real names; it was not keeping to the 75-character limit for
483 encoded words that the RFC imposes. It now respects the limit, and
484 generates multiple encoded words if necessary. To be on the safe side, I
485 have increased the buffer size for the ${rfc2047: expansion operator from
488 33. It is now permitted to omit both strings after an "if" condition; if the
489 condition is true, the result is "true". As before, when the second string
490 is omitted, a false condition yields an empty string. This makes it less
491 cumbersome to write custom ACL and router conditions.
493 34. Failure to deliver a bounce message always caused it to be frozen, even if
494 there was an errors_to setting on the router. The errors_to setting is now
497 35. If an IPv6 address is given for -bh or -bhc, it is now converted to the
498 canonical form (fully expanded) before being placed in
499 $sender_host_address.
501 36. The table in the code that translates DNS record types into text (T_A to
502 "A" for instance) was missing entries for NS and CNAME. It is just possible
503 that this could have caused confusion if both these types were looked up
504 for the same domain, because the text type is used as part of Exim's
505 per-process caching. But the chance of anyone hitting this buglet seems
508 37. The dnsdb lookup has been extended in a number of ways.
510 (1) There is a new type, "zns", which walks up the domain tree until it
511 finds some nameserver records. It should be used with care.
513 (2) There is a new type, "mxh", which is like "mx" except that it returns
514 just the host names, not the priorities.
516 (3) It is now possible to give a list of domains (or IP addresses) to be
517 looked up. The behaviour when one of the lookups defers can be
518 controlled by a keyword.
520 (4) It is now possible to specify the separator character for use when
521 multiple records are returned.
523 38. The dnslists ACL condition has been extended: it is now possible to supply
524 a list of IP addresses and/or domains to be looked up in a particular DNS
527 39. Added log_selector=+queue_time_overall.
529 40. When running the queue in the test harness, wait just a tad after forking a
530 delivery process, to get repeatability of debugging output.
532 41. Include certificate and key file names in error message when GnuTLS fails
533 to set them up, because the GnuTLS error message doesn't include the name
534 of the failing file when there is a problem reading it.
536 42. Allow both -bf and -bF in the same test run.
538 43. Did the same fix as 41 above for OpenSSL, which had the same infelicity.
540 44. The "Exiscan patch" is now merged into the mainline Exim source.
542 45. Sometimes the final signoff response after QUIT could fail to get
543 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
544 < 0 before doing a fflush(). This bug looks as though it goes back to the
545 introduction of TLS in release 3.20, but "sometimes" must have been rare
546 because the tests only now provoked it.
548 46. Reset the locale to "C" after calling embedded Perl, in case it was changed
549 (this can affect the format of dates).
551 47. exim_tidydb, when checking for the continued existence of a message for
552 which it has found a message-specific retry record, was not finding
553 messages that were in split spool directories. Consequently, it was
554 deleting retry records that should have stayed in existence.
556 48. Steve fixed some bugs in eximstats.
558 49. The SPA authentication driver was not abandoning authentication and moving
559 on to the next authenticator when an expansion was forced to fail,
560 contradicting the general specification for all authenticators. Instead it
561 was generating a temporary error. It now behaves as specified.
563 50. The default ordering of permitted cipher suites for GnuTLS was pessimal
564 (the order specifies the preference for clients). The order is now AES256,
565 AES128, 3DES, ARCFOUR128.
567 51. Small patch to Sieve code - explicitly set From: when generating an
570 52. Exim crashed if a remote delivery caused a very long error message to be
571 recorded - for instance if somebody sent an entire SpamAssassin report back
572 as a large number of 550 error lines. This bug was coincidentally fixed by
573 increasing the size of one of Exim's internal buffers (big_buffer) that
574 happened as part of the Exiscan merge. However, to be on the safe side, I
575 have made the code more robust (and fixed the comments that describe what
578 53. Now that there can be additional text after "Completed" in log lines (if
579 the queue_time_overall log selector is set), a one-byte patch to exigrep
580 was needed to allow it to recognize "Completed" as not the last thing in
583 54. The LDAP lookup was not handling a return of LDAP_RES_SEARCH_REFERENCE. A
584 patch that reportedly fixes this has been added. I am not expert enough to
585 create a test for it. This is what the patch creator wrote:
587 "I found a little strange behaviour of ldap code when working with
588 Windows 2003 AD Domain, where users was placed in more than one
589 Organization Units. When I tried to give exim partial DN, the exit code
590 of ldap_search was unknown to exim because of LDAP_RES_SEARCH_REFERENCE.
591 But simultaneously result of request was absolutely normal ldap result,
592 so I produce this patch..."
594 Later: it seems that not all versions of LDAP support LDAP_RES_SEARCH_
595 REFERENCE, so I have modified the code to exclude the patch when that macro
598 55. Some experimental protocols are using DNS PTR records for new purposes. The
599 keys for these records are domain names, not reversed IP addresses. The
600 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
601 leaves it alone. Component reversal etc. now happens only for IP addresses.
604 56. Improve error message when ldap_search() fails in OpenLDAP or Solaris LDAP.
606 57. Double the size of the debug message buffer (to 2048) so that more of very
607 long debug lines gets shown.
609 58. The exicyclog utility now does better if the number of log files to keep
610 exceeds 99. In this case, it numbers them 001, 002 ... instead of 01, 02...
612 59. Two changes related to the smtp_active_hostname option:
614 (1) $smtp_active_hostname is now available as a variable.
615 (2) The default for smtp_banner uses $smtp_active_hostname instead
616 of $primary_hostname.
618 60. The host_aton() function is supposed to be passed a string that is known
619 to be a valid IP address. However, in the case of IPv6 addresses, it was
620 not checking this. This is a hostage to fortune. Exim now panics and dies
621 if the condition is not met. A case was found where this could be provoked
622 from a dnsdb PTR lookup with an IPv6 address that had more than 8
623 components; fortuitously, this particular loophole had already been fixed
624 by change 4.50/55 above.
626 If there are any other similar loopholes, the new check in host_aton()
627 itself should stop them being exploited. The report I received stated that
628 data on the command line could provoke the exploit when Exim was running as
629 exim, but did not say which command line option was involved. All I could
630 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
634 61. There was a buffer overflow vulnerability in the SPA authentication code
635 (which came originally from the Samba project). I have added a test to the
636 spa_base64_to_bits() function which I hope fixes it.
639 62. Configuration update for GNU/Hurd and variations. Updated Makefile-GNU and
640 os.h-GNU, and added configuration files for GNUkFreeBSD and GNUkNetBSD.
642 63. The daemon start-up calls getloadavg() while still root for those OS that
643 need the first call to be done as root, but it missed one case: when
644 deliver_queue_load_max is set with deliver_drop_privilege. This is
645 necessary for the benefit of the queue runner, because there is no re-exec
646 when deliver_drop_privilege is set.
648 64. A call to exiwhat cut short delays set up by "delay" modifiers in ACLs.
651 65. Caching of lookup data for "hosts =" ACL conditions, when a named host list
652 was in use, was not putting the data itself into the right store pool;
653 consequently, it could be overwritten for a subsequent message in the same
654 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
657 66. Added hosts_max_try_hardlimit to the smtp transport, default 50.
659 67. The string_is_ip_address() function returns 0, 4, or 6, for "no an IP
660 address", "IPv4 address", and "IPv6 address", respectively. Some calls of
661 the function were treating the return as a boolean value, which happened to
662 work because 0=false and not-0=true, but is not correct code.
664 68. The host_aton() function was not handling scoped IPv6 addresses (those
665 with, for example, "%eth0" on the end) correctly.
667 69. Fixed some compiler warnings in acl.c for the bitmaps specified with
668 negated items (that is, ~something) in unsigned ints. Some compilers
669 apparently mutter when there is no cast.
671 70. If an address verification called from an ACL failed, and did not produce a
672 user-specific message (i.e. there was only a "system" message), nothing was
673 put in $acl_verify_message. In this situation, it now puts the system
676 71. Change 4.23/11 added synchronization checking at the start of an SMTP
677 session; change 4.31/43 added the unwanted input to the log line - except
678 that it did not do this in the start of session case. It now does.
680 72. After a timeout in a callout SMTP session, Exim still sent a QUIT command.
681 This is wrong and can cause the other end to generate a synchronization
682 error if it is another Exim or anything else that does the synchronization
683 check. A QUIT command is no longer sent after a timeout.
685 73. $host_lookup_deferred has been added, to make it easier to detect DEFERs
688 74. The defer_ok option of callout verification was not working if it was used
689 when verifying addresses in header lines, that is, for this case:
691 verify = header_sender/callout=defer_ok
693 75. A backgrounded daemon closed stdin/stdout/stderr on entry; this meant that
694 those file descriptors could be used for SMTP connections. If anything
695 wrote to stderr (the example that came up was "warn" in embedded Perl), it
696 could be sent to the SMTP client, causing chaos. The daemon now opens
697 stdin, stdout, and stderr to /dev/null when it puts itself into the
700 76. Arrange for output from Perl's "warn" command to be written to Exim's main
701 log by default. The user can override this with suitable Perl magic.
703 77. The use of log_message on a "discard" ACL verb, which is supposed to add to
704 the log message when discard triggers, was not working for the DATA ACL or
705 for the non-SMTP ACL.
707 78. Error message wording change in sieve.c.
709 79. If smtp_accept_max_per_host was set, the number of connections could be
710 restricted to fewer than expected, because the daemon was trying to set up
711 a new connection before checking whether the processes handling previous
712 connections had finished. The check for completed processes is now done
713 earlier. On busy systems, this bug wouldn't be noticed because something
714 else would have woken the daemon, and it would have reaped the completed
717 80. If a message was submitted locally by a user whose login name contained one
718 or more spaces (ugh!), the spool file that Exim wrote was not re-readable.
719 It caused a spool format error. I have fixed the spool reading code. A
720 related problem was that the "from" clause in the Received: line became
721 illegal because of the space(s). It is now covered by ${quote_local_part.
723 81. Included the latest eximstats from Steve (adds average sizes to HTML Top
726 82. Updated OS/Makefile-AIX as per message from Mike Meredith.
728 83. Patch from Sieve maintainer to fix unterminated string problem in
731 84. Some minor changes to the Linux configuration files to help with other
732 OS variants using glibc.
734 85. One more patch for Sieve to update vacation handling to latest spec.
737 ----------------------------------------------------
738 See the note above about the 4.44 and 4.50 releases.
739 ----------------------------------------------------
745 1. Change 4.43/35 introduced a bug that caused file counts to be
746 incorrectly computed when quota_filecount was set in an appendfile
749 2. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
750 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
753 3. Give more explanation in the error message when the command for a transport
754 filter fails to execute.
756 4. There are several places where Exim runs a non-Exim command in a
757 subprocess. The SIGUSR1 signal should be disabled for these processes. This
758 was being done only for the command run by the queryprogram router. It is
759 now done for all such subprocesses. The other cases are: ${run, transport
760 filters, and the commands run by the lmtp and pipe transports.
762 5. Some older OS have a limit of 256 on the maximum number of file
763 descriptors. Exim was using setrlimit() to set 1000 as a large value
764 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
765 systems. I've change it so that if it can't get 1000, it tries for 256.
767 6. "control=submission" was allowed, but had no effect, in a DATA ACL. This
768 was an oversight, and furthermore, ever since the addition of extra
769 controls (e.g. 4.43/32), the checks on when to allow different forms of
770 "control" were broken. There should now be diagnostics for all cases when a
771 control that does not make sense is encountered.
773 7. $recipients is now available in the predata ACL (oversight).
775 8. Tidy the search cache before the fork to do a delivery from a message
776 received from the command line. Otherwise the child will trigger a lookup
777 failure and thereby defer the delivery if it tries to use (for example) a
778 cached ldap connection that the parent has called unbind on.
780 9. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
781 of $address_data from the recipient verification was clobbered by the
784 10. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
785 was its contents. (It was OK if the option was not defined at all.)
787 11. A "Completed" log line is now written for messages that are removed from
788 the spool by the -Mrm option.
790 12. $host_address is now set to the target address during the checking of
793 13. When checking ignore_target_hosts for an ipliteral router, no host name was
794 being passed; this would have caused $sender_host_name to have been used if
795 matching the list had actually called for a host name (not very likely,
796 since this list is usually IP addresses). A host name is now passed as
799 14. Changed the calls that set up the SIGCHLD handler in the daemon to use the
800 code that specifies a non-restarting handler (typically sigaction() in
801 modern systems) in an attempt to fix a rare and obscure crash bug.
803 15. Narrowed the window for a race in the daemon that could cause it to ignore
804 SIGCHLD signals. This is not a major problem, because they are used only to
805 wake it up if nothing else does.
807 16. A malformed maildirsize file could cause Exim to calculate negative values
808 for the mailbox size or file count. Odd effects could occur as a result.
809 The maildirsize information is now recalculated if the size or filecount
812 17. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
813 support for a long time. Removed HAVE_SYS_VFS_H.
815 18. Updated exipick to current release from John Jetmore.
817 19. Allow an empty sender to be matched against a lookup in an address list.
818 Previously the only cases considered were a regular expression, or an
821 20. Exim went into a mad DNS lookup loop when doing a callout where the
822 host was specified on the transport, if the DNS lookup yielded more than
825 21. The RFC2047 encoding function was originally intended for short strings
826 such as real names; it was not keeping to the 75-character limit for
827 encoded words that the RFC imposes. It now respects the limit, and
828 generates multiple encoded words if necessary. To be on the safe side, I
829 have increased the buffer size for the ${rfc2047: expansion operator from
832 22. Failure to deliver a bounce message always caused it to be frozen, even if
833 there was an errors_to setting on the router. The errors_to setting is now
836 23. If an IPv6 address is given for -bh or -bhc, it is now converted to the
837 canonical form (fully expanded) before being placed in
838 $sender_host_address.
840 24. Updated eximstats to version 1.33
842 25. Include certificate and key file names in error message when GnuTLS fails
843 to set them up, because the GnuTLS error message doesn't include the name
844 of the failing file when there is a problem reading it.
846 26. Expand error message when OpenSSL has problems setting up cert/key files.
849 27. Reset the locale to "C" after calling embedded Perl, in case it was changed
850 (this can affect the format of dates).
852 28. exim_tidydb, when checking for the continued existence of a message for
853 which it has found a message-specific retry record, was not finding
854 messages that were in split spool directories. Consequently, it was
855 deleting retry records that should have stayed in existence.
857 29. eximstats updated to version 1.35
858 1.34 - allow eximstats to parse syslog lines as well as mainlog lines
859 1.35 - bugfix such that pie charts by volume are generated correctly
861 30. The SPA authentication driver was not abandoning authentication and moving
862 on to the next authenticator when an expansion was forced to fail,
863 contradicting the general specification for all authenticators. Instead it
864 was generating a temporary error. It now behaves as specified.
866 31. The default ordering of permitted cipher suites for GnuTLS was pessimal
867 (the order specifies the preference for clients). The order is now AES256,
868 AES128, 3DES, ARCFOUR128.
870 31. Small patch to Sieve code - explicitly set From: when generating an
873 32. Exim crashed if a remote delivery caused a very long error message to be
874 recorded - for instance if somebody sent an entire SpamAssassin report back
875 as a large number of 550 error lines. This bug was coincidentally fixed by
876 increasing the size of one of Exim's internal buffers (big_buffer) that
877 happened as part of the Exiscan merge. However, to be on the safe side, I
878 have made the code more robust (and fixed the comments that describe what
881 33. Some experimental protocols are using DNS PTR records for new purposes. The
882 keys for these records are domain names, not reversed IP addresses. The
883 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
884 leaves it alone. Component reversal etc. now happens only for IP addresses.
887 34. The host_aton() function is supposed to be passed a string that is known
888 to be a valid IP address. However, in the case of IPv6 addresses, it was
889 not checking this. This is a hostage to fortune. Exim now panics and dies
890 if the condition is not met. A case was found where this could be provoked
891 from a dnsdb PTR lookup with an IPv6 address that had more than 8
892 components; fortuitously, this particular loophole had already been fixed
893 by change 4.50/55 or 4.44/33 above.
895 If there are any other similar loopholes, the new check in host_aton()
896 itself should stop them being exploited. The report I received stated that
897 data on the command line could provoke the exploit when Exim was running as
898 exim, but did not say which command line option was involved. All I could
899 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
903 35. There was a buffer overflow vulnerability in the SPA authentication code
904 (which came originally from the Samba project). I have added a test to the
905 spa_base64_to_bits() function which I hope fixes it.
908 36. The daemon start-up calls getloadavg() while still root for those OS that
909 need the first call to be done as root, but it missed one case: when
910 deliver_queue_load_max is set with deliver_drop_privilege. This is
911 necessary for the benefit of the queue runner, because there is no re-exec
912 when deliver_drop_privilege is set.
914 37. Caching of lookup data for "hosts =" ACL conditions, when a named host list
915 was in use, was not putting the data itself into the right store pool;
916 consequently, it could be overwritten for a subsequent message in the same
917 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
920 38. Sometimes the final signoff response after QUIT could fail to get
921 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
922 < 0 before doing a fflush(). This bug looks as though it goes back to the
923 introduction of TLS in release 3.20, but "sometimes" must have been rare
924 because the tests only now provoked it.
930 1. Fixed a longstanding but relatively impotent bug: a long time ago, before
931 PIPELINING, the function smtp_write_command() used to return TRUE or FALSE.
932 Now it returns an integer. A number of calls were still expecting a T/F
933 return. Fortuitously, in all cases, the tests worked in OK situations,
934 which is the norm. However, things would have gone wrong on any write
935 failures on the smtp file descriptor. This function is used when sending
936 messages over SMTP and also when doing verify callouts.
938 2. When Exim is called to do synchronous delivery of a locally submitted
939 message (the -odf or -odi options), it no longer closes stderr before doing
942 3. Implemented the mua_wrapper option.
944 4. Implemented mx_fail_domains and srv_fail_domains for the dnslookup router.
946 5. Implemented the functions header_remove(), header_testname(),
947 header_add_at_position(), and receive_remove_recipient(), and exported them
950 6. If an ACL "warn" statement specified the addition of headers, Exim already
951 inserted X-ACL-Warn: at the start if there was no header name. However, it
952 was not making this test for the second and subsequent header lines if
953 there were newlines in the string. This meant that an invalid header could
954 be inserted if Exim was badly configured.
956 7. Allow an ACL "warn" statement to add header lines at the start or after all
957 the Received: headers, as well as at the end.
959 8. Added the rcpt_4xx retry error code.
961 9. Added postmaster_mailfrom=xxx to callout verification option.
963 10. Added mailfrom=xxxx to the callout verification option, for verify=
966 11. ${substr_1_:xxxx} and ${substr__3:xxxx} are now diagnosed as syntax errors
967 (they previously behaved as ${substr_1_0:xxxx} and ${substr:_0_3:xxxx}).
969 12. Inserted some casts to stop certain compilers warning when using pointer
970 differences as field lengths or precisions in printf-type calls (mostly
971 affecting debugging statements).
973 13. Added optional readline() support for -be (dynamically loaded).
975 14. Obscure bug fix: if a message error (e.g. 4xx to MAIL) happened within the
976 same clock tick as a message's arrival, so that its received time was the
977 same as the "first fail" time on the retry record, and that message
978 remained on the queue past the ultimate address timeout, every queue runner
979 would try a delivery (because it was past the ultimate address timeout) but
980 after another failure, the ultimate address timeout, which should have then
981 bounced the address, did not kick in. This was a "< instead of <=" error;
982 in most cases the first failure would have been in the next clock tick
983 after the received time, and all would be well.
985 15. The special items beginning with @ in domain lists (e.g. @mx_any) were not
986 being recognized when the domain list was tested by the match_domain
987 condition in an expansion string.
989 16. Added the ${str2b64: operator.
991 17. Exim was always calling setrlimit() to set a large limit for the number of
992 processes, without checking whether the existing limit was already
993 adequate. (It did check for the limit on file descriptors.) Furthermore,
994 errors from getrlimit() and setrlimit() were being ignored. Now they are
995 logged to the main and panic logs, but Exim does carry on, to try to do its
996 job under whatever limits there are.
998 18. Imported PCRE 5.0.
1000 19. Trivial typo in log message " temporarily refused connection" (the leading
1003 20. If the log selector return_path_on_delivery was set and an address was
1004 redirected to /dev/null, the delivery process crashed because it assumed
1005 that a return path would always be set for a "successful" delivery. In this
1006 case, the whole delivery is bypassed as an optimization, and therefore no
1009 21. Internal re-arrangement: the function for sending a challenge and reading
1010 a response while authentication was assuming a zero-terminated challenge
1011 string. It's now changed to take a pointer and a length, to allow for
1012 binary data in such strings.
1014 22. Added the cyrus_sasl authenticator (code supplied by MBM).
1016 23. Exim was not respecting finduser_retries when seeking the login of the
1017 uid under which it was called; it was always trying 10 times. (The default
1018 setting of finduser_retries is zero.) Also, it was sleeping after the final
1019 failure, which is pointless.
1021 24. Implemented tls_on_connect_ports.
1023 25. Implemented acl_smtp_predata.
1025 26. If the domain in control=submission is set empty, Exim assumes that the
1026 authenticated id is a complete email address when it generates From: or
1027 Sender: header lines.
1029 27. Added "#define SOCKLEN_T int" to OS/os.h-SCO and OS/os.h-SCO_SV. Also added
1030 definitions to OS/Makefile-SCO and OS/Makefile-SCO_SV that put basename,
1031 chown and chgrp in /bin and hostname in /usr/bin.
1033 28. Exim was keeping the "process log" file open after each use, just as it
1034 does for the main log. This opens the possibility of it remaining open for
1035 long periods when the USR1 signal hits a daemon. Occasional processlog
1036 errors were reported, that could have been caused by this. Anyway, it seems
1037 much more sensible not to leave this file open at all, so that is what now
1040 29. The long-running daemon process does not normally write to the log once it
1041 has entered its main loop, and it closes the log before doing so. This is
1042 so that log files can straightforwardly be renamed and moved. However,
1043 there are a couple of unusual error situations where the daemon does write
1044 log entries, and I had neglected to close the log afterwards.
1046 30. The text of an SMTP error response that was received during a remote
1047 delivery was being truncated at 512 bytes. This is too short for some of
1048 the long messages that one sometimes sees. I've increased the limit to
1051 31. It is now possible to make retry rules that apply only when a message has a
1052 specific sender, in particular, an empty sender.
1054 32. Added "control = enforce_sync" and "control = no_enforce_sync". This makes
1055 it possible to be selective about when SMTP synchronization is enforced.
1057 33. Added "control = caseful_local_part" and "control = "caselower_local_part".
1059 32. Implemented hosts_connection_nolog.
1061 33. Added an ACL for QUIT.
1063 34. Setting "delay_warning=" to disable warnings was not working; it gave a
1066 35. Added mailbox_size and mailbox_filecount to appendfile.
1068 36. Added control = no_multiline_responses to ACLs.
1070 37. There was a bug in the logic of the code that waits for the clock to tick
1071 in the case where the clock went backwards by a substantial amount such
1072 that the microsecond fraction of "now" was more than the microsecond
1073 fraction of "then" (but the whole seconds number was less).
1075 38. Added support for the libradius Radius client library this is found on
1076 FreeBSD (previously only the radiusclient library was supported).
1082 1. When certain lookups returned multiple values in the form name=value, the
1083 quoting of the values was not always being done properly. Specifically:
1084 (a) If the value started with a double quote, but contained no whitespace,
1086 (b) If the value contained whitespace other than a space character (i.e.
1087 tabs or newlines or carriage returns) it was not quoted.
1088 This fix has been applied to the mysql and pgsql lookups by writing a
1089 separate quoting function and calling it from the lookup code. The fix
1090 should probably also be applied to nisplus, ibase and oracle lookups, but
1091 since I cannot test any of those, I have not disturbed their existing code.
1093 2. A hit in the callout cache for a specific address caused a log line with no
1094 reason for rejecting RCPT. Now it says "Previous (cached) callout
1095 verification failure".
1097 3. There was an off-by-one bug in the queryprogram router. An over-long
1098 return line was truncated at 256 instead of 255 characters, thereby
1099 overflowing its buffer with the terminating zero. As well as fixing this, I
1100 have increased the buffer size to 1024 (and made a note to document this).
1102 4. If an interrupt, such as the USR1 signal that is send by exiwhat, arrives
1103 when Exim is waiting for an SMTP response from a remote server, Exim
1104 restarts its select() call on the socket, thereby resetting its timeout.
1105 This is not a problem when such interrupts are rare. Somebody set up a cron
1106 job to run exiwhat every 2 minutes, which is less than the normal select()
1107 timeout (5 or 10 minutes). This meant that the select() timeout never
1108 kicked in because it was always reset. I have fixed this by comparing the
1109 time when an interrupt arrives with the time at the start of the first call
1110 to select(). If more time than the timeout has elapsed, the interrupt is
1111 treated as a timeout.
1113 5. Some internal re-factoring in preparation for the addition of Sieve
1114 extensions (by MH). In particular, the "personal" test is moved to a
1115 separate function, and given an option for scanning Cc: and Bcc: (which is
1116 not set for Exim filters).
1118 6. When Exim created an email address using the login of the caller as the
1119 local part (e.g. when creating a From: or Sender: header line), it was not
1120 quoting the local part when it contained special characters such as @.
1122 7. Installed new OpenBSD configuration files.
1124 8. Reworded some messages for syntax errors in "and" and "or" conditions to
1125 try to make them clearer.
1127 9. Callout options, other than the timeout value, were being ignored when
1128 verifying sender addresses in header lines. For example, when using
1130 verify = header_sender/callout=no_cache
1132 the cache was (incorrectly) being used.
1134 10. Added a missing instance of ${EXE} to the exim_install script; this affects
1135 only the Cygwin environment.
1137 11. When return_path_on_delivery was set as a log selector, if different remote
1138 addresses in the same message used different return paths and parallel
1139 remote delivery occurred, the wrong values would sometimes be logged.
1140 (Whenever a remote delivery process finished, the return path value from
1141 the most recently started remote delivery process was logged.)
1143 12. RFC 3848 specifies standard names for the "with" phrase in Received: header
1144 lines when AUTH and/or TLS are in use. This is the "received protocol"
1145 field. Exim used to use "asmtp" for authenticated SMTP, without any
1146 indication (in the protocol name) for TLS use. Now it follows the RFC and
1147 uses "esmtpa" if the connection is authenticated, "esmtps" if it is
1148 encrypted, and "esmtpsa" if it is both encrypted and authenticated. These
1149 names appear in log lines as well as in Received: header lines.
1151 13. Installed MH's patches for Sieve to add the "copy" and "vacation"
1152 extensions, and comparison tests, and to fix some bugs.
1154 14. Changes to the "personal" filter test:
1156 (1) The test was buggy in that it was just doing the equivalent of
1157 "contains" tests on header lines. For example, if a user's address was
1158 anne@some.where, the "personal" test would incorrectly be true for
1160 To: susanne@some.where
1162 This test is now done by extracting each address from the header in turn,
1163 and checking the entire address. Other tests that are part of "personal"
1164 are now done using regular expressions (for example, to check local parts
1165 of addresses in From: header lines).
1167 (2) The list of non-personal local parts in From: addresses has been
1168 extended to include "listserv", "majordomo", "*-request", and "owner-*",
1169 taken from the Sieve specification recommendations.
1171 (3) If the message contains any header line starting with "List-" it is
1172 treated as non-personal.
1174 (4) The test for "circular" in the Subject: header line has been removed
1175 because it now seems ill-conceived.
1177 15. Minor typos in src/EDITME comments corrected.
1179 16. Installed latest exipick from John Jetmore.
1181 17. If headers_add on a router specified a text string that was too long for
1182 string_sprintf() - that is, longer than 8192 bytes - Exim panicked. The use
1183 of string_sprintf() is now avoided.
1185 18. $message_body_size was not set (it was always zero) when running the DATA
1186 ACL and the local_scan() function.
1188 19. For the "mail" command in an Exim filter, no default was being set for
1189 the once_repeat time, causing a random time value to be used if "once" was
1190 specified. (If the value happened to be <= 0, no repeat happened.) The
1191 default is now 0s, meaning "never repeat". The "vacation" command was OK
1192 (its default is 7d). It's somewhat surprising nobody ever noticed this bug
1193 (I found it when inspecting the code).
1195 20. There is now an overall timeout for performing a callout verification. It
1196 defaults to 4 times the callout timeout, which applies to individual SMTP
1197 commands during the callout. The overall timeout applies when there is more
1198 than one host that can be tried. The timeout is checked before trying the
1199 next host. This prevents very long delays if there are a large number of
1200 hosts and all are timing out (e.g. when the network connections are timing
1201 out). The value of the overall timeout can be changed by specifying an
1202 additional sub-option for "callout", called "maxwait". For example:
1204 verify = sender/callout=5s,maxwait=20s
1206 21. Add O_APPEND to the open() call for maildirsize files (Exim already seeks
1207 to the end before writing, but this should make it even safer).
1209 22. Exim was forgetting that it had advertised PIPELINING for the second and
1210 subsequent messages on an SMTP connection. It was also not resetting its
1211 memory on STARTTLS and an internal HELO.
1213 23. When Exim logs an SMTP synchronization error within a session, it now
1214 records whether PIPELINING has been advertised or not.
1216 24. Added 3 instances of "(long int)" casts to time_t variables that were being
1217 formatted using %ld, because on OpenBSD (and perhaps others), time_t is int
1218 rather than long int.
1220 25. Installed the latest Cygwin configuration files from the Cygwin maintainer.
1222 26. Added the never_mail option to autoreply.
1228 1. A reorganization of the code in order to implement 4.40/8 caused a daemon
1229 crash if the getsockname() call failed; this can happen if a connection is
1230 closed very soon after it is established. The problem was simply in the
1231 order in which certain operations were done, causing Exim to try to write
1232 to the SMTP stream before it had set up the file descriptor. The bug has
1233 been fixed by making things happen in the correct order.
1239 1. If "drop" was used in a DATA ACL, the SMTP output buffer was not flushed
1240 before the connection was closed, thus losing the rejection response.
1242 2. Commented out the definition of SOCKLEN_T in os.h-SunOS5. It is needed for
1243 some early Solaris releases, but causes trouble in current releases where
1244 socklen_t is defined.
1246 3. When std{in,out,err} are closed, re-open them to /dev/null so that they
1249 4. Minor refactoring of os.c-Linux to avoid compiler warning when IPv6 is not
1252 5. Refactoring in expand.c to improve memory usage. Pre-allocate a block so
1253 that releasing the top of it at the end releases what was used for sub-
1254 expansions (unless the block got too big). However, discard this block if
1255 the first thing is a variable or header, so that we can use its block when
1256 it is dynamic (useful for very large $message_headers, for example).
1258 6. Lookups now cache *every* query, not just the most recent. A new, separate
1259 store pool is used for this. It can be recovered when all lookup caches are
1260 flushed. Lookups now release memory at the end of their result strings.
1261 This has involved some general refactoring of the lookup sources.
1263 7. Some code has been added to the store_xxx() functions to reduce the amount
1264 of flapping under certain conditions.
1266 8. log_incoming_interface used to affect only the <= reception log lines. Now
1267 it causes the local interface and port to be added to several more SMTP log
1268 lines, for example "SMTP connection from", and rejection lines.
1270 9. The Sieve author supplied some patches for the doc/README.SIEVE file.
1272 10. Added a conditional definition of _BSD_SOCKLEN_T to os.h-Darwin.
1274 11. If $host_data was set by virtue of a hosts lookup in an ACL, its value
1275 could be overwritten at the end of the current message (or the start of a
1276 new message if it was set in a HELO ACL). The value is now preserved for
1277 the duration of the SMTP connection.
1279 12. If a transport had a headers_rewrite setting, and a matching header line
1280 contained an unqualified address, that address was qualified, even if it
1281 did not match any rewriting rules. The underlying bug was that the values
1282 of the flags that permit the existence of unqualified sender and recipient
1283 addresses in header lines (set by {sender,recipient}_unqualified_hosts for
1284 non-local messages, and by -bnq for local messages) were not being
1285 preserved with the message after it was received.
1287 13. When Exim was logging an SMTP synchronization error, it could sometimes log
1288 "next input=" as part of the text comprising the host identity instead of
1289 the correct text. The code was using the same buffer for two different
1290 strings. However, depending on which order the printing function evaluated
1291 its arguments, the bug did not always show up. Under Linux, for example, my
1292 test suite worked just fine.
1294 14. Exigrep contained a use of Perl's "our" scoping after change 4.31/70. This
1295 doesn't work with some older versions of Perl. It has been changed to "my",
1296 which in any case is probably the better facility to use.
1298 15. A really picky compiler found some instances of statements for creating
1299 error messages that either had too many or two few arguments for the format
1302 16. The size of the buffer for calls to the DNS resolver has been increased
1303 from 1024 to 2048. A larger buffer is needed when performing PTR lookups
1304 for addresses that have a lot of PTR records. This alleviates a problem; it
1305 does not fully solve it.
1307 17. A dnsdb lookup for PTR records that receives more data than will fit in the
1308 buffer now truncates the list and logs the incident, which is the same
1309 action as happens when Exim is looking up a host name and its aliases.
1310 Previously in this situation something unpredictable would happen;
1311 sometimes it was "internal error: store_reset failed".
1313 18. If a server dropped the connection unexpectedly when an Exim client was
1314 using GnuTLS and trying to read a response, the client delivery process
1315 crashed while trying to generate an error log message.
1317 19. If a "warn" verb in an ACL added multiple headers to a message in a single
1318 string, for example:
1320 warn message = H1: something\nH2: something
1322 the text was added as a single header line from Exim's point of view
1323 though it ended up OK in the delivered message. However, searching for the
1324 second and subsequent header lines using $h_h2: did not work. This has been
1325 fixed. Similarly, if a system filter added multiple headers in this way,
1326 the routers could not see them.
1328 20. Expanded the error message when iplsearch is called with an invalid key to
1329 suggest using net-iplsearch in a host list.
1331 21. When running tests using -bh, any delays imposed by "delay" modifiers in
1332 ACLs are no longer actually imposed (and a message to that effect is
1335 22. If a "gecos" field in a passwd entry contained escaped characters, in
1336 particular, if it contained a \" sequence, Exim got it wrong when building
1337 a From: or a Sender: header from that name. A second bug also caused
1338 incorrect handling when an unquoted " was present following a character
1339 that needed quoting.
1341 23. "{crypt}" as a password encryption mechanism for a "crypteq" expansion item
1342 was not being matched caselessly.
1344 24. Arranged for all hyphens in the exim.8 source to be escaped with
1347 25. Change 16 of 4.32, which reversed 71 or 4.31 didn't quite do the job
1348 properly. Recipient callout cache records were still being keyed to include
1349 the sender, even when use_sender was set false. This led to far more
1350 callouts that were necessary. The sender is no longer included in the key
1351 when use_sender is false.
1353 26. Added "control = submission" modifier to ACLs.
1355 27. Added the ${base62d: operator to decode base 62 numbers.
1357 28. dnsdb lookups can now access SRV records.
1359 29. CONFIGURE_OWNER can be set at build time to define an alternative owner for
1360 the configuration file.
1362 30. The debug message "delivering xxxxxx-xxxxxx-xx" is now output in verbose
1363 (-v) mode. This makes the output for a verbose queue run more intelligible.
1365 31. Added a use_postmaster feature to recipient callouts.
1367 32. Added the $body_zerocount variable, containing the number of binary zero
1368 bytes in the message body.
1370 33. The time of last modification of the "new" subdirectory is now used as the
1371 "mailbox time last read" when there is a quota error for a maildir
1374 34. Added string comparison operators lt, lti, le, lei, gt, gti, ge, gei.
1376 35. Added +ignore_unknown as a special item in host lists.
1378 36. Code for decoding IPv6 addresses in host lists is now included, even if
1379 IPv6 support is not being compiled. This fixes a bug in which an IPv6
1380 address was recognized as an IP address, but was then not correctly decoded
1381 into binary, causing unexpected and incorrect effects when compared with
1388 1. Very minor rewording of debugging text in manualroute to say "list of
1389 hosts" instead of "hostlist".
1391 2. If verify=header_syntax was set, and a header line with an unqualified
1392 address (no domain) and a large number of spaces between the end of the
1393 name and the colon was received, the reception process suffered a buffer
1394 overflow, and (when I tested it) crashed. This was caused by some obsolete
1395 code that should have been removed. The fix is to remove it!
1397 3. When running in the test harness, delay a bit after writing a bounce
1398 message to get a bit more predictability in the log output.
1400 4. Added a call to search_tidyup() just before forking a reception process. In
1401 theory, someone could use a lookup in the expansion of smtp_accept_max_
1402 per_host which, without the tidyup, could leave open a database connection.
1404 5. Added the variables $recipient_data and $sender_data which get set from a
1405 lookup success in an ACL "recipients" or "senders" condition, or a router
1406 "senders" option, similar to $domain_data and $local_part_data.
1408 6. Moved the writing of debug_print from before to after the "senders" test
1411 7. Change 4.31/66 (moving the time when the Received: is generated) caused
1412 problems for message scanning, either using a data ACL, or using
1413 local_scan() because the Received: header was not generated till after they
1414 were called (in order to set the time as the time of reception completion).
1415 I have revised the way this works. The header is now generated after the
1416 body is received, but before the ACL or local_scan() are called. After they
1417 are run, the timestamp in the header is updated.
1423 1. Change 4.24/6 introduced a bug because the SIGALRM handler was disabled
1424 before starting a queue runner without re-exec. This happened only when
1425 deliver_drop_privilege was set or when the Exim user was set to root. The
1426 effect of the bug was that timeouts during subsequent deliveries caused
1427 crashes instead of being properly handled. The handler is now left at its
1428 default (and expected) setting.
1430 2. The other case in which a daemon avoids a re-exec is to deliver an incoming
1431 message, again when deliver_drop_privilege is set or Exim is run as root.
1432 The bug described in (1) was not present in this case, but the tidying up
1433 of the other signals was missing. I have made the two cases consistent.
1435 3. The ignore_target_hosts setting on a manualroute router was being ignored
1436 for hosts that were looked up using the /MX notation.
1438 4. Added /ignore=<ip list> feature to @mx_any, @mx_primary, and @mx_secondary
1441 5. Change 4.31/55 was buggy, and broke when there was a rewriting rule that
1442 operated on the sender address. After changing the $sender_address to <>
1443 for the sender address verify, Exim was re-instated it as the original
1444 (before rewriting) address, but remembering that it had rewritten it, so it
1445 wasn't rewriting it again. This bug also had the effect of breaking the
1446 sender address verification caching when the sender address was rewritten.
1448 6. The ignore_target_hosts option was being ignored by the ipliteral router.
1449 This has been changed so that if the ip literal address matches
1450 ignore_target_hosts, the router declines.
1452 7. Added expansion conditions match_domain, match_address, and match_local_
1453 part (NOT match_host).
1455 8. The placeholder for the Received: header didn't have a length field set.
1457 9. Added code to Exim itself and to exim_lock to test for a specific race
1458 condition that could lead to file corruption when using MBX delivery. The
1459 issue is with the lockfile that is created in /tmp. If this file is removed
1460 after a process has opened it but before that process has acquired a lock,
1461 there is the potential for a second process to recreate the file and also
1462 acquire a lock. This could lead to two Exim processes writing to the file
1463 at the same time. The added code performs the same test as UW imapd; it
1464 checks after acquiring the lock that its file descriptor still refers to
1465 the same named file.
1467 10. The buffer for building added header lines was of fixed size, 8192 bytes.
1468 It is now parameterized by HEADER_ADD_BUFFER_SIZE and this can be adjusted
1471 11. Added the smtp_active_hostname option. If used, this will typically be made
1472 to depend on the incoming interface address. Because $interface_address is
1473 not set up until the daemon has forked a reception process, error responses
1474 that can happen earlier (such as "too many connections") no longer contain
1477 12. If an expansion in a condition on a "warn" statement fails because a lookup
1478 defers, the "warn" statement is abandoned, and the next ACL statement is
1479 processed. Previously this caused the whole ACL to be aborted.
1481 13. Added the iplsearch lookup type.
1483 14. Added ident_timeout as a log selector.
1485 15. Added tls_certificate_verified as a log selector.
1487 16. Added a global option tls_require_ciphers (compare the smtp transport
1488 option of the same name). This controls incoming TLS connections.
1490 17. I finally figured out how to make tls_require_ciphers do a similar thing
1491 in GNUtls to what it does in OpenSSL, that is, set up an appropriate list
1492 before starting the TLS session.
1494 18. Tabs are now shown as \t in -bP output.
1496 19. If the log selector return_path_on_delivery was set, Exim crashed when
1497 bouncing a message because it had too many Received: header lines.
1499 20. If two routers both had headers_remove settings, and the first one included
1500 a superfluous trailing colon, the final name in the first list and the
1501 first name in the second list were incorrectly joined into one item (with a
1502 colon in the middle).
1508 1. Added -C and -D options to the exinext utility, mainly to make it easier
1509 to include in the automated testing, but these could be helpful when
1510 multiple configurations are in use.
1512 2. The exinext utility was not formatting the output nicely when there was
1513 an alternate port involved in the retry record key, nor when there was a
1514 message id as well (for retries that were specific to a specific message
1515 and a specific host). It was also confused by IPv6 addresses, because of
1516 the additional colons they contain. I have fixed the IPv4 problem, and
1517 patched it up to do a reasonable job for IPv6.
1519 3. When there is an error after a MAIL, RCPT, or DATA SMTP command during
1520 delivery, the log line now contains "pipelined" if PIPELINING was used.
1522 4. An SMTP transport process used to panic and die if the bind() call to set
1523 an explicit outgoing interface failed. This has been changed; it is now
1524 treated in the same way as a connect() failure.
1526 5. A reference to $sender_host_name in the part of a conditional expansion
1527 that was being skipped was still causing a DNS lookup. This no longer
1530 6. The def: expansion condition was not recognizing references to header lines
1531 that used bh_ and bheader_.
1533 7. Added the _cache feature to named lists.
1535 8. The code for checking quota_filecount in the appendfile transport was
1536 allowing one more file than it should have been.
1538 9. For compatibility with Sendmail, the command line option
1546 and sets the incoming protocol and host name (for trusted callers). The
1547 host name and its colon can be omitted when only the protocol is to be set.
1548 Note the Exim already has two private options, -pd and -ps, that refer to
1549 embedded Perl. It is therefore impossible to set a protocol value of "d" or
1550 "s", but I don't think that's a major issue.
1552 10. A number of refactoring changes to the code, none of which should affect
1555 (a) The number of logging options was getting close to filling up the
1556 32-bit word that was used as a bit map. I have split them into two classes:
1557 those that are passed in the argument to log_write(), and those that are
1558 only ever tested independently outside of that function. These are now in
1559 separate 32-bit words, so there is plenty of room for expansion again.
1560 There is no change in the user interface or the logging behaviour.
1562 (b) When building, for example, log lines, the code previously used a
1563 macro that called string_cat() twice, in order to add two strings. This is
1564 not really sufficiently general. Furthermore, there was one instance where
1565 it was actually wrong because one of the argument was used twice, and in
1566 one call a function was used. (As it happened, calling the function twice
1567 did not affect the overall behaviour.) The macro has been replaced by a
1568 function that can join an arbitrary number of extra strings onto a growing
1571 (c) The code for expansion conditions now uses a table and a binary chop
1572 instead of a serial search (which was left over from when there were very
1573 few conditions). Also, it now recognizes conditions like "pam" even when
1574 the relevant support is not compiled in: a suitably worded error message is
1575 given if an attempt is made to use such a condition.
1577 11. Added ${time_interval:xxxxx}.
1579 12. A bug was causing one of the ddress fields not to be passed back correctly
1580 from remote delivery subprocesses. The field in question was not being
1581 subsequently used, so this caused to problems in practice.
1583 13. Added new log selectors queue_time and deliver_time.
1585 14. Might have fixed a bug in maildirsizefile handling that threw up
1586 "unexpected character" debug warnings, and recalculated the data
1587 unnecessarily. In any case, I expanded the warning message to give more
1590 15. Added the message "Restricted characters in address" to the statements in
1591 the default ACL that block characters like @ and % in local parts.
1593 16. Change 71 for release 4.31 proved to be much less benign that I imagined.
1594 Three changes have been made:
1596 (a) There was a serious bug; a negative response to MAIL caused the whole
1597 recipient domain to be cached as invalid, thereby blocking all messages
1598 to all local parts at the same domain, from all senders. This bug has
1599 been fixed. The domain is no longer cached after a negative response to
1600 MAIL if the sender used is not empty.
1602 (b) The default behaviour of using MAIL FROM:<> for recipient callouts has
1605 (c) A new callout option, "use_sender" has been added for people who want
1606 the modified behaviour.
1612 1. Removed "EXTRALIBS=-lwrap" from OS/Makefile-Unixware7 on the advice of
1615 2. Removed "LIBS = -lresolv" from OS/Makefile-Darwin as it is not needed, and
1616 indeed breaks things for older releases.
1618 3. Added additional logging to the case where there is a problem reading data
1619 from a filter that is running in a subprocess using a pipe, in order to
1620 try to track down a specific problem.
1622 4. Testing facility fudge: when running in the test harness and attempting
1623 to connect to 10.x.x.x (expecting a connection timeout) I'm now sometimes
1624 getting "No route to host". Convert this to a timeout.
1626 5. Define ICONV_ARG2_TYPE as "char **" for Unixware7 to avoid compiler
1629 6. Some OS don't have socklen_t but use size_t instead. This affects the
1630 fifth argument of getsockopt() amongst other things. This is now
1631 configurable by a macro called SOCKLEN_T which defaults to socklen_t, but
1632 can be set for individual OS. I have set it for SunOS5, OSF1, and
1633 Unixware7. Current versions of SunOS5 (aka Solaris) do have socklen_t, but
1634 some earlier ones do not.
1636 7. Change 4.30/15 was not doing the test caselessly.
1638 8. The standard form for an IPv6 address literal was being rejected by address
1639 parsing in, for example, MAIL and RCPT commands. An example of this kind of
1640 address is [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
1641 this, as well as the form without the "IPv6" on the front (but only when
1642 address literals are enabled, of course).
1644 9. Added some casts to avoid compiler warnings in OS/os.c-Linux.
1646 10. Exim crashed if a message with an empty sender address specified by -f
1647 encountered a router with an errors_to setting. This could be provoked only
1648 by a command such as
1652 where an empty string was supplied; "<>" did not hit this bug.
1654 11. Installed PCRE release 4.5.
1656 12. If EHLO/HELO was rejected by an ACL, the value of $sender_helo_name
1657 remained set. It is now erased.
1659 13. exiqgrep wasn't working on MacOS X because it didn't correctly compute
1660 times from message ids (which are base 36 rather than the normal 62).
1662 14. "Expected" SMTP protocol errors that can arise when PIPELINING is in use
1663 were being counted as actual protocol errors, and logged if the log
1664 selector +smtp_protocol_error was set. One cannot be perfect in this test,
1665 but now, if PIPELINING has been advertised, RCPT following a rejected MAIL,
1666 and DATA following a set of rejected RCPTs do not count as protocol errors.
1667 In other words, Exim assumes they were pipelined, though this may not
1668 actually be the case. Of course, in all cases the client gets an
1669 appropriate error code.
1671 15. If a lookup fails in an ACL condition, a message about the failure may
1672 be available; it is used if testing the ACL cannot continue, because most
1673 such messages specify what the cause of the deferral is. However, some
1674 messages (e.g. "MYSQL: no data found") do not cause a defer. There was bug
1675 that caused an old message to be retained and used if a later statement
1676 caused a defer, replacing the real cause of the deferral.
1678 16. If an IP address had so many PTR records that the DNS lookup buffer
1679 was not large enough to hold them, Exim could crash while trying to process
1680 the truncated data. It now detects and logs this case.
1682 17. Further to 4.21/58, another change has been made: if (and only if) the
1683 first line of a message (the first header line) ends with CRLF, a bare LF
1684 in a subsequent header line has a space inserted after it, so as not to
1685 terminate the header.
1687 18. Refactoring: tidied an ugly bit of code in appendfile that copied data
1688 unnecessarily, used atoi() instead of strtol(), and didn't check the
1689 termination when getting file sizes from file names by regex.
1691 19. Completely re-implemented the support for maildirsize files, in the light
1692 of a number of problems with the previous contributed implementation
1693 (4.30/29). In particular:
1695 . If the quota is zero, the maildirsize file is maintained, but no quota is
1698 . If the maildir directory does not exist, it is created before any attempt
1699 to write a maildirsize file.
1701 . The quota value in the file is just a cache; if the quota is changed in
1702 the transport, the new value overrides.
1704 . A regular expression is available for excluding directories from the
1707 20. The autoreply transport checks the characters in options that define the
1708 message's headers; it allows continued headers, but it was checking with
1709 isspace() after an embedded newline instead of explicitly looking for a
1712 21. If all the "regular" hosts to which an address was routed had passed their
1713 expiry times, and had not reached their retry times, the address was
1714 bounced, even if fallback hosts were defined. Now Exim should go on to try
1717 22. Increased buffer sizes in the callout code from 1024 to 4096 to match the
1718 equivalent code in the SMTP transport. Some hosts send humungous responses
1719 to HELO/EHLO, more than 1024 it seems.
1721 23. Refactoring: code in filter.c used (void *) for "any old type" but this
1722 gives compiler warnings in some environments. I've now done it "properly",
1725 24. The replacement for inet_ntoa() that is used with gcc on IRIX systems
1726 (because of problems with the built-in one) was declared to return uschar *
1727 instead of char *, causing compiler failure.
1729 25. Fixed a file descriptor leak when processing alias/forward files.
1731 26. Fixed a minor format string issue in dbfn.c.
1733 27. Typo in exim.c: ("dmbnz" for "dbmnz").
1735 28. If a filter file refered to $h_xxx or $message_headers, and the headers
1736 contained RFC 2047 "words", Exim's memory could, under certain conditions,
1739 29. When a sender address is verified, it is cached, to save repeating the test
1740 when there is more than one recipient in a message. However, when the
1741 verification involves a callout, it is possible for different callout
1742 options to be set for different recipients. It is too complicated to keep
1743 track of this in the cache, so now Exim always runs a verification when a
1744 callout is required, relying on the callout cache for the optimization.
1745 The overhead is duplication of the address routing, but this should not be
1748 30. Fixed a bug in callout caching. If a RCPT command caused the sender address
1749 to be verified with callout=postmaster, and the main callout worked but the
1750 postmaster check failed, the verification correctly failed. However, if a
1751 subsequent RCPT command asked for sender verification *without* the
1752 postmaster check, incorrect caching caused this verification also to fail,
1755 31. Exim caches DNS lookup failures so as to avoid multiple timeouts; however,
1756 it was not caching the DNS options (qualify_single, search_parents) that
1757 were used when the lookup failed. A subsequent lookup with different
1758 options therefore always gave the same answer, though there were cases
1759 where it should not have. (Example: a "domains = !$mx_any" option on a
1760 dnslookup router: the "domains" option is always processed without any
1761 widening, but the router might have qualify_single set.) Now Exim uses the
1762 cached value only when the same options are set.
1764 32. Added John Jetmore's "exipick" utility to the distribution.
1766 33. GnuTLS: When an attempt to start a TLS session fails for any reason other
1767 than a timeout (e.g. a certificate is required, and is not provided), an
1768 Exim server now closes the connection immediately. Previously it waited for
1769 the client to close - but if the client is SSL, it seems that they each
1770 wait for each other, leading to a delay before one of them times out.
1772 34: GnuTLS: Updated the code to use the new GnuTLS 1.0.0 API. I have not
1773 maintained 0.8.x compatibility because I don't think many are using it, and
1774 it is clearly obsolete.
1776 35. Added TLS support for CRLs: a tls_crl global option and one for the smtp
1779 36. OpenSSL: $tls_certificate_verified was being set to 1 even if the
1780 client certificate was expired. A simple patch fixes this, though I don't
1781 understand the full logic of why the verify callback is called multiple
1784 37. OpenSSL: a patch from Robert Roselius: "Enable client-bug workaround.
1785 Versions of OpenSSL as of 0.9.6d include a 'CBC countermeasure' feature,
1786 which causes problems with some clients (such as the Certicom SSL Plus
1787 library used by Eudora). This option, SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS,
1788 disables the coutermeasure allowing Eudora to connect."
1790 38. Exim was not checking that a write() to a log file succeeded. This could
1791 lead to Bad Things if a log got too big, in particular if it hit a file
1792 size limit. Exim now panics and dies if it cannot write to a log file, just
1793 as it does if it cannot open a log file.
1795 39. Modified OS/Makefile-Linux so that it now contains
1797 CFLAGS=-O -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
1799 The two -D definitions ensure that Exim is compiled with large file
1800 support, which makes it possible to handle log files that are bigger than
1803 40. Fixed a subtle caching bug: if (in an ACL or a set of routers, for
1804 instance) a domain was checked against a named list that involved a lookup,
1805 causing $domain_data to be set, then another domain was checked against the
1806 same list, then the first domain was re-checked, the value of $domain_data
1807 after the final check could be wrong. In particular, if the second check
1808 failed, it could be set empty. This bug probably also applied to
1811 41. The strip_trailing_dot option was not being applied to the address given
1812 with the -f command-line option.
1814 42. The code for reading a message's header from the spool was incrementing
1815 $received_count, but never initializing it. This meant that the value was
1816 incorrect (doubled) while delivering a message in the same process in which
1817 it was received. In the most common configuration of Exim, this never
1818 happens - a fresh exec is done - but it can happen when
1819 deliver_drop_privilege is set.
1821 43. When Exim logs an SMTP synchronization error - client data sent too soon -
1822 it now includes up to 150 characters of the unexpected data in the log
1825 44. The exim_dbmbuild utility uses fixed size buffers for reading input lines
1826 and building data strings. The size of both of these buffers was 10 000
1827 bytes - far larger than anybody would *ever* want, thought I. Needless to
1828 say, somebody hit the limit. I have increased the maximum line length to
1829 20 000 and the maximum data length of concatenated lines to 100 000. I have
1830 also fixed two bugs, because there was no checking on these buffers. Tsk,
1831 tsk. Now exim_dbmbuild gives a message and exits with an error code if a
1832 buffer is too small.
1834 45. The exim_dbmbuild utility did not support quoted keys, as Exim does in
1835 lsearch lookups. Now it does.
1837 46. When parsing a route_list item in a manualroute router, a fixed-length
1838 buffer was used for the list of hosts. I made this 1024 bytes long,
1839 thinking that nobody would ever have a list of hosts that long. Wrong.
1840 Somebody had a whole pile of complicated expansion conditions, and the
1841 string was silently truncated, leading to an expansion error. It turns out
1842 that it is easier to change to an unlimited length (owing to other changes
1843 that have happened since this code was originally written) than to build
1844 structure for giving a limitation error. The length of the item that
1845 expands into the list of hosts is now unlimited.
1847 47. The lsearch lookup could not handle data where the length of text line was
1848 more than 4095 characters. Such lines were truncated, leading to shortened
1849 data being returned. It should now handle lines of any length.
1851 48. Minor wording revision: "cannot test xxx in yyy ACL" becomes "cannot test
1852 xxx condition in yyy ACL" (e.g. "cannot test domains condition in DATA
1855 49. Cosmetic tidy to scripts like exicyclog that are generated by globally
1856 replacing strings such as BIN_DIRECTORY in a source file: the replacement
1857 no longer happens in comment lines. A list of replacements is now placed
1858 at the head of all of the source files, except those whose only change is
1859 to replace PERL_COMMAND in the very first #! line.
1861 50. Replaced the slow insertion sort in queue.c, for sorting the list of
1862 messages on the queue, with a bottom-up merge sort, using code contributed
1863 by Michael Haardt. This should make operations like -bp somewhat faster on
1864 large queues. It won't affect queue runners, except when queue_run_in_order
1867 51. Installed eximstats 1.31 in the distribution.
1869 52. Added support for SRV lookups to the dnslookup router.
1871 53. If an ACL referred to $message_body or $message_body_end, the value was not
1872 reset for any messages that followed in the same SMTP session.
1874 54. The store-handling optimization for building very long strings was not
1875 differentiating between the different store pools. I don't think this
1876 actually made any difference in practice, but I've tidied it.
1878 55. While running the routers to verify a sender address, $sender_address
1879 was still set to the sender address. This is wrong, because when routing to
1880 send a bounce to the sender, it would be empty. Therefore, I have changed
1881 it so that, while verifying a sender address, $sender_address is set to <>.
1882 (There is no change to what happens when verifying a recipient address.)
1884 56. After finding MX (or SRV) records, Exim was doing a DNS lookup for the
1885 target A or AAAA records (if not already returned) without resetting the
1886 qualify_single or search_parents options of the DNS resolver. These are
1887 inappropriate in this case because the targets of MX and SRV records must
1888 be FQDNs. A broken DNS record could cause trouble if it happened to have a
1889 target that, when qualified, matched something in the local domain. These
1890 two options are now turned off when doing these lookups.
1892 57. It seems that at least some releases of Reiserfs (which does not have the
1893 concept of a fixed number of inodes) returns zero and not -1 for the
1894 number of available inodes. This interacted badly with check_spool_inodes,
1895 which assumed that -1 was the "no such thing" setting. What I have done is
1896 to check that the total number of inodes is greater than zero before doing
1897 the test of how many are available.
1899 58. When a "warn" ACL statement has a log_message modifier, the message is
1900 remembered, and not repeated. This is to avoid a lot of repetition when a
1901 message has many recipients that cause the same warning to be written.
1902 Howewer, Exim was preserving the list of already written lines for an
1903 entire SMTP session, which doesn't seem right. The memory is now reset if a
1904 new message is started.
1906 59. The "rewrite" debugging flag was not showing the result of rewriting in the
1907 debugging output unless log_rewrite was also set.
1909 60. Avoid a compiler warning on 64-bit systems in dsearch.c by avoiding the use
1910 of (int)(handle) when we know that handle contains (void *)(-1).
1912 61. The Exim daemon panic-logs an error return when it closes the incoming
1913 connection. However "connection reset by peer" seems to be common, and
1914 isn't really an error worthy of noting specially, so that particular error
1917 62. When Exim is trying to find all the local interfaces, it used to panic and
1918 die if the ioctl to get the interface flags failed. However, it seems that
1919 on at least one OS (Solaris 9) it is possible to have an interface that is
1920 included in the list of interfaces, but for which you get a failure error
1921 for this call. This happens when the interface is not "plumbed" into a
1922 protocol (i.e. neither IPv4 nor IPv6). I've changed the code so that a
1923 failure of the "get flags" call assumes that the interface is down.
1925 63. Added a ${eval10: operator, which assumes all numbers are decimal. This
1926 makes life easier for people who are doing arithmetic on fields extracted
1927 from dates, where you often get leading zeros that should not be
1928 interpreted as octal.
1930 64. Added qualify_domain to the redirect router, to override the global
1933 65. If a pathologically long header line contained very many addresses (the
1934 report of this problem mentioned 10 000) and each of them was rewritten,
1935 Exim could use up a very large amount of memory. (It kept on making new
1936 copies of the header line as it rewrote, and never released the old ones.)
1937 At the expense of a bit more processing, the header rewriting function has
1938 been changed so that it no longer eats memory in this way.
1940 66. The generation of the Received: header has been moved from the time that a
1941 message starts to be received, to the time that it finishes. The timestamp
1942 in the Received: header should now be very close to that of the <= log
1943 line. There are two side-effects of this change:
1945 (a) If a message is rejected by a DATA or non-SMTP ACL or local_scan(), the
1946 logged header lines no longer include the local Received: line, because
1947 it has not yet been created. The same applies to a copy of the message
1948 that is returned to a non-SMTP sender when a message is rejected.
1950 (b) When a filter file is tested using -bf, no additional Received: header
1951 is added to the test message. After some thought, I decided that this
1954 This change does not affect the value of $received_for. It is still set
1955 after address rewriting, but before local_scan() is called.
1957 67. Installed the latest Cygwin-specific files from the Cygwin maintainer.
1959 68. GnuTLS: If an empty file is specified for tls_verify_certificates, GnuTLS
1960 gave an unhelpful panic error message, and a defer error. I have managed to
1961 change this behaviour so that it now rejects any supplied certificate,
1962 which seems right, as the list of acceptable certificates is empty.
1964 69. OpenSSL: If an empty file is specified for tls_verify_certificates, OpenSSL
1965 gave an unhelpful defer error. I have not managed to make this reject any
1966 supplied certificates, but the error message it gives is "no certificate
1967 supplied", which is not helpful.
1969 70. exigrep's output now also includes lines that are not associated with any
1970 message, but which match the given pattern. Implemented by a patch from
1971 Martin Sluka, which also tidied up the Perl a bit.
1973 71. Recipient callout verification, like sender verification, was using <> in
1974 the MAIL FROM command. This isn't really the right thing, since the actual
1975 sender may affect whether the remote host accepts the recipient or not. I
1976 have changed it to use the actual sender in the callout; this means that
1977 the cache record is now keyed on a recipient/sender pair, not just the
1978 recipient address. There doesn't seem to be a real danger of callout loops,
1979 since a callout by the remote host to check the sender would use <>.
1980 [SEE ABOVE: changed after hitting problems.]
1982 72. Exim treats illegal SMTP error codes that do not begin with 4 or 5 as
1983 temporary errors. However, in the case of such a code being given after
1984 the end of a data transmission (i.e. after ".") Exim was failing to write
1985 a retry record for the message. (Yes, there was some broken host that was
1986 actually sending 8xx at this point.)
1988 73. An unknown lookup type in a host list could cause Exim to panic-die when
1989 the list was checked. (An example that provoked this was putting <; in the
1990 middle of a list instead of at the start.) If this happened during a DATA
1991 ACL check, a -D file could be left lying around. This kind of configuration
1992 error no longer causes Exim to die; instead it causes a defer errror. The
1993 incident is still logged to the main and panic logs.
1995 74. Buglet left over from Exim 3 conversion. The message "too many messages
1996 in one connection" was written to the rejectlog but not the mainlog, except
1997 when address rewriting (yes!) was being logged.
1999 75. Added write_rejectlog option.
2001 76. When a system filter was run not as root (that is, when system_filter_user
2002 was set), the values of the $n variables were not being returned to the
2003 main process; thus, they were not subsequently available in the $sn
2006 77. Added +return_path_on_delivery log selector.
2008 78. A connection timeout was being treated differently from recipients deferred
2009 when testing hosts_max_try with a message that was older than the host's
2010 retry timeout. (The host should not be counted, thus allowing all hosts to
2011 be tried at least once before bouncing.) This may have been the cause of an
2012 occasionally reported bug whereby a message would remain on the queue
2013 longer than the retry timeout, but would be bounced if a delivery was
2014 forced. I say "may" because I never totally pinned down the problem;
2015 setting up timeout/retry tests is difficult. See also the next item.
2017 79. The ultimate address timeout was not being applied to errors that involved
2018 a combination of host plus message (for example, a timeout on a MAIL
2019 command). When an address resolved to a number of possible hosts, and they
2020 were not all tried for each delivery (e.g. because of hosts_max_try), a
2021 message could remain on the queue longer than the retry timeout.
2023 80. Sieve bug: "stop" inside "elsif" was broken. Applied a patch from Michael
2026 81. Fixed an obscure SMTP outgoing bug which required at least the following
2027 conditions: (a) there was another message waiting for the same server;
2028 (b) the server returned 5xx to all RCPT commands in the first message so
2029 that the message was not completed; (c) the server dropped the connection
2030 or gave a negative response to the RSET that Exim sends to abort the
2031 transaction. The observed case was a dropped connection after DATA that had
2032 been sent in pipelining mode. That is, the server had advertised PIPELINING
2033 but was not implementing it correctly. The effect of the bug was incorrect
2034 behaviour, such as trying another host, and this could lead to a crash.
2040 1. The 3rd arguments to getsockname(), getpeername(), and accept() in exim.c
2041 and daemon.c were passed as pointers to ints; they should have been
2042 pointers to socklen_t variables (which are typically unsigned ints).
2044 2. Some signed/unsigned type warnings in the os.c file for Linux have been
2047 3. Fixed a really odd bug that affected only the testing scheme; patching a
2048 certain fixed string in the binary changed the value of another string that
2049 happened to be identical to the end of the original first string.
2051 4. When gethostbyname() (or equivalent) is passed an IP address as a "host
2052 name", it returns that address as the IP address. On some operating
2053 systems (e.g. Solaris), it also passes back the IP address string as the
2054 "host name". However, on others (e.g. Linux), it passes back an empty
2055 string. Exim wasn't checking for this, and was changing the host name to an
2056 empty string, assuming it had been canonicized.
2058 5. Although rare, it is permitted to have more than one PTR record for a given
2059 IP address. I thought that gethostbyaddr() or getipnodebyaddr() always gave
2060 all the names associated with an address, because they do in Solaris.
2061 However, it seems that they do not in Linux for data that comes from the
2062 DNS. If an address in /etc/hosts has multiple names, they _are_ all given.
2063 I found this out when I moved to a new Linux workstation and tried to run
2064 the Exim test suite.
2066 To get round this problem I have changed the code so that it now does its
2067 own call to the DNS to look up PTR records when searching for a host name.
2068 If nothing can be found in the DNS, it tries gethostbyaddr(), so that
2069 addresses that are only in /etc/hosts are still found.
2071 This behaviour is, however, controlled by an option called host_lookup_
2072 order, which defaults to "bydns:byaddr". If people want to use the other
2073 order, or indeed, just use one or the other means of lookup, they can
2074 specify it in this variable.
2076 6. If a PTR record yields an empty name, Exim treats it as non-existent. In
2077 some operating systems, this comes back from gethostbyaddr() as an empty
2078 string, and this is what Exim used to test for. However, it seems that in
2079 other systems, "." is yielded. Exim now tests for this case too.
2081 7. The values of check_spool_space and check_log_space are now held internally
2082 as a number of kilobytes instead of an absolute number of bytes. If a
2083 numbers is specified without 'K' or 'M', it is rounded up to the nearest
2084 kilobyte. This means that much larger values can be stored.
2086 8. Exim monitor: an attempt to get the action menu when not actually pointing
2087 at a message produces an empty menu entitled "No message selected". This
2088 works on Solaris (OpenWindows). However, XFree86 does not like a menu with
2089 no entries in it ("Shell widget menu has zero width and/or height"). So I
2090 have added a single, blank menu entry in this case.
2092 9. Added ${quote_local_part.
2094 10. MIME decoding is now applied to the contents of Subject: header lines when
2097 11. Now that a reference to $sender_host_address automatically causes a reverse
2098 lookup to occur if necessary (4.13/18), there is no need to arrange for a
2099 host lookup before query-style lookups in lists that might use this
2100 variable. This has therefore been abolished, and the "net-" prefix is no
2101 longer necessary for query-style lookups.
2103 12. The Makefile for SCO_SV contained a setting of LDFLAGS. This appears to
2104 have been a typo for LFLAGS, so it has been changed.
2106 13. The install script calls Exim with "-C /dev/null" in order to find the
2107 version number. If ALT_CONFIG_PREFIX was set, this caused an error message
2108 to be output. Howeve, since Exim outputs its version number before the
2109 error, it didn't break the script. It just looked ugly. I fixed this by
2110 always allowing "-C /dev/null" if the caller is root.
2112 14. Ignore overlarge ACL variable number when reading spool file - insurance
2113 against a later release with more variables having written the file.
2115 15. The standard form for an IPv6 address literal was being rejected by EHLO.
2116 Example: [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
2117 this, as well as the form without the "IPv6" on the front.
2119 16. Added CHOWN_COMMAND=/usr/sbin/chown and LIBS=-lresolv to the
2120 OS/Makefile-Darwin file.
2122 17. Fixed typo in lookups/ldap.c: D_LOOKUP should be D_lookup. This applied
2123 only to LDAP libraries that do not have LDAP_OPT_DEREF.
2125 18. After change 4.21/52, "%ld" was used to format the contents of the $inode
2126 variable. However, some OS use ints for inodes. I've added cast to long int
2127 to get rid of the compiler warning.
2129 19. I had forgotten to lock out "/../" in configuration file names when
2130 ALT_CONFIG_PREFIX was set.
2132 20. Routers used for verification do not need to specify transports. However,
2133 if such a router generated a host list, and callout was configured, Exim
2134 crashed, because it could not find a port number from the (non-existent)
2135 transport. It now assumes port 25 in this circumstance.
2137 21. Added the -t option to exigrep.
2139 22. If LOOKUP_LSEARCH is defined, all three linear search methods (lsearch,
2140 wildlsearch, nwildlsearch) are compiled. LOOKUP_WILDLSEARCH and LOOKUP_
2141 NWILDLSEARCH are now obsolete, but retained for compatibility. If either of
2142 them is set, LOOKUP_LSEARCH is forced.
2144 23. "exim -bV" now outputs a list of lookups that are included in the binary.
2146 24. Added sender and host information to the "rejected by local_scan()" log
2147 line; previously there was no indication of these.
2149 25. Added .include_if_exists.
2151 26. Change 3.952/11 added an explicit directory sync on top of a file sync for
2152 Linux. It turns out that not all file systems support this. Apparently some
2153 versions of NFS do not. (It's rare to put Exim's spool on NFS, but people
2154 do it.) To cope with this, the error EINVAL, which means that sync-ing is
2155 not supported on the file descriptor, is now ignored when Exim is trying to
2156 sync a directory. This applies only to Linux.
2158 27. Added -DBIND_8_COMPAT to the CLFAGS setting for Darwin.
2160 28. In Darwin (MacOS X), the PAM headers are in /usr/include/pam and not in
2161 /usr/include/security. There's now a flag in OS/os.h-Darwin to cope with
2164 29. Added support for maildirsize files from supplied patch (modified a bit).
2166 30. The use of :fail: followed by an empty string could lead Exim to respond to
2167 sender verification failures with (e.g.):
2169 550 Verification failed for <xxx>
2170 550 Sender verify failed
2172 where the first response line was missing the '-' that indicates it is not
2173 the final line of the response.
2175 31. The loop for finding the name of the user that called Exim had a hardwired
2176 limit of 10; it now uses the value of finduser_retries, which is used for
2177 all other user lookups.
2179 32. Added $received_count variable, available in data and not_smtp ACLs, and at
2182 33. Exim was neglecting to zero errno before one call of strtol() when
2183 expanding a string and expecting an integer value. On some systems this
2184 resulted in spurious "integer overflow" errors. Also, it was casting the
2185 result into an int without checking.
2187 34. Testing for a connection timeout using "timeout_connect" in the retry rules
2188 did not work. The code looks as if it has *never* worked, though it appears
2189 to have been documented since at least releast 1.62. I have made it work.
2191 35. The "timeout_DNS" error in retry rules, also documented since at least
2192 1.62, also never worked. As it isn't clear exactly what this means, and
2193 clearly it isn't a major issue, I have abolished the feature by treating it
2194 as "timeout", and writing a warning to the main and panic logs.
2196 36. The display of retry rules for -brt wasn't always showing the error code
2199 37. Added new error conditions to retry rules: timeout_A, timeout_MX,
2200 timeout_connect_A, timeout_connect_MX.
2202 38. Rewriting the envelope sender at SMTP time did not allow it to be rewritten
2203 to the empty sender.
2205 39. The daemon was not analysing the content of -oX till after it had closed
2206 stderr and disconnected from the controlling terminal. This meant that any
2207 syntax errors were only noted on the panic log, and the return code from
2208 the command was 0. By re-arranging the code a little, I've made the
2209 decoding happen first, so such errors now appear on stderr, and the return
2210 code is 1. However, the actual setting up of the sockets still happens in
2211 the disconnected process, so errors there are still only recorded on the
2214 40. A daemon listener on a wildcard IPv6 socket that also accepts IPv4
2215 connections (as happens on some IP stacks) was logged at start up time as
2216 just listening for IPv6. It now logs "IPv6 with IPv4". This differentiates
2217 it from "IPv6 and IPv4", which means that two separate sockets are being
2220 41. The debug output for gethostbyname2() or getipnodebyname() failures now
2221 says whether AF_INET or AF_INET6 was passed as an argument.
2223 42. Exiwhat output was messed up when time zones were included in log
2226 43. Exiwhat now gives more information about the daemon's listening ports,
2227 and whether -tls-on-connect was used.
2229 44. The "port" option of the smtp transport is now expanded.
2231 45. A "message" modifier in a "warn" statement in a non-message ACL was being
2232 silently ignored. Now an error message is written to the main and panic
2235 46. There's a new ACL modifier called "logwrite" which writes to a log file
2236 as soon as it is encountered.
2238 47. Added $local_user_uid and $local_user_gid at routing time.
2240 48. Exim crashed when trying to verify a sender address that was being
2243 49. Exim was recognizing only a space character after ".include". It now also
2244 recognizes a tab character.
2246 50. Fixed several bugs in the Perl script that creates the exim.8 man page by
2247 extracting the relevant information from the specification. The man page no
2248 longer contains scrambled data for the -d option, and I've added a section
2249 at the front about calling Exim under different names.
2251 51. Added "extra_headers" argument to the "mail" command in filter files.
2253 52. Redirecting mail to an unqualified address in a Sieve filter caused Exim to
2256 53. Installed eximstats 1.29.
2258 54. Added transport_filter_timeout as a generic transport option.
2260 55. Exim no longer adds an empty Bcc: header to messages that have no To: or
2261 Cc: header lines. This was required by RFC 822, but it not required by RFC
2264 56. Exim used to add From:, Date:, and Message-Id: header lines to any
2265 incoming messages that did not have them. Now it does so only if the
2266 message originates locally, that is, if there is no associated remote host
2267 address. When Resent- header lines are present, this applies to the Resent-
2268 lines rather than the non-Resent- lines.
2270 57. Drop incoming SMTP connection after too many syntax or protocol errors. The
2271 limit is controlled by smtp_max_synprot_errors, defaulting to 3.
2273 58. Messages for configuration errors now include the name of the main
2274 configuration file - useful now that there may be more than one file in a
2275 list (.included file names were always shown).
2277 59. Change 4.21/82 (run initgroups() when starting the daemon) causes problems
2278 for those rare installations that do not start the daemon as root or run it
2279 setuid root. I've cut out the call to initgroups() if the daemon is not
2282 60. The Exim user and group can now be bound into the binary as text strings
2283 that are looked up at the start of Exim's processing.
2285 61. Applied a small patch for the Interbase code, supplied by Ard Biesheuvel.
2287 62. Added $mailstore_basename variable.
2289 63. Installed patch to sieve.c from Michael Haardt.
2291 64. When Exim failed to open the panic log after failing to open the main log,
2292 the original message it was trying to log was written to stderr and debug
2293 output, but if they were not available (the usual case in production), it
2294 was lost. Now it is written to syslog before the two lines that record the
2295 failures to open the logs.
2297 65. Users' Exim filters run in subprocesses under the user's uid. It is
2298 possible for a "deliver" command or an alias in a "personal" command to
2299 provoke an address rewrite. If logging of address rewriting is configured,
2300 this fails because the process is not running as root or exim. There may be
2301 a better way of dealing with this, but for the moment (because 4.30 needs
2302 to be released), I have disabled address rewrite logging when running a
2303 filter in a non-root, non-exim process.
2309 1. The buildconfig auxiliary program wasn't quoting the value set for
2310 HEADERS_CHARSET. This caused a compilation error complaining that 'ISO' was
2311 not defined. This bug was masked in 4.22 by the effect that was fixed in
2314 2. Some messages that were rejected after a message id was allocated were
2315 shown as "incomplete" by exigrep. It no longer does this for messages that
2316 are rejected by local_scan() or the DATA or non-SMTP ACLs.
2318 3. If a Message-ID: header used a domain literal in the ID, and Exim did not
2319 have allow_domain_literals set, the ID did not get logged in the <= line.
2320 Domain literals are now always recognized in Message-ID: header lines.
2322 4. The first argument for a ${extract expansion item is the key name or field
2323 number. Leading and trailing spaces in this item were not being ignored,
2324 causing some misleading effects.
2326 5. When deliver_drop_privilege was set, single queue runner processes started
2327 manually (i.e. by the command "exim -q") or by the daemon (which uses the
2328 same command in the process it spins off) were not dropping privilege.
2330 6. When the daemon running as "exim" started a queue runner, it always
2331 re-executed Exim in the spun-off process. This is a waste of effort when
2332 deliver_drop_privilege is set. The new process now just calls the
2333 queue-runner function directly.
2339 1. Typo in the src/EDITME file: it referred to HEADERS_DECODE_TO instead of
2342 2. Change 4.21/73 introduced a bug. The pid file path set by -oP was being
2343 ignored. Though the use of -oP was forcing the writing of a pid file, it
2344 was always written to the default place.
2346 3. If the message "no IP address found for host xxxx" is generated during
2347 incoming verification, it is now followed by identification of the incoming
2348 connection (so you can more easily find what provoked it).
2350 4. Bug fix for Sieve filters: "stop" inside a block was not working properly.
2352 5. Added some features to "harden" Exim a bit more against certain attacks:
2354 (a) There is now a build-time option called FIXED_NEVER_USERS that can
2355 be put in Local/Makefile. This is like the never_users runtime option,
2356 but it cannot be overridden. The default setting is "root".
2358 (b) If ALT_CONFIG_PREFIX is defined in Local/Makefile, it specifies a
2359 prefix string with which any file named in a -C command line option
2362 (c) If ALT_CONFIG_ROOT_ONLY is defined in Local/Makefile, root privilege
2363 is retained for -C and -D only if the caller of Exim is root. Without
2364 it, the exim user may also use -C and -D and retain privilege.
2366 (d) If DISABLE_D_OPTION is defined in Local/Makefile, the use of the -D
2367 command line option is disabled.
2369 6. Macro names set by the -D option must start with an upper case letter, just
2370 like macro names defined in the configuration file.
2372 7. Added "dereference=" facility to LDAP.
2374 8. Two instances of the typo "uknown" in the source files are fixed.
2376 9. If a PERL_COMMAND setting in Local/Makefile was not at the start of a line,
2377 the Configure-Makefile script screwed up while processing it.
2379 10. Incorporated PCRE 4.4.
2381 11. The SMTP synchronization check was not operating right at the start of an
2382 SMTP session. For example, it could not catch a HELO sent before the client
2383 waited for the greeting. There is now a check for outstanding input at the
2384 point when the greeting is written. Because of the duplex, asynchronous
2385 nature of TCP/IP, it cannot be perfect - the incorrect input may be on its
2386 way, but not yet received, when the check is performed.
2388 12. Added tcp_nodelay to make it possible to turn of the setting of TCP_NODELAY
2389 on TCP/IP sockets, because this apparently causes some broken clients to
2392 13. Installed revised OS/Makefile-CYGWIN and OS/os.c-cygwin (the .h file was
2393 unchanged) from the Cygwin maintainer.
2395 14. The code for -bV that shows what is in the binary showed "mbx" when maildir
2396 was supported instead of testing for mbx. Effectively a typo.
2398 15. The spa authenticator server code was not checking that the input it
2399 received was valid base64.
2401 16. The debug output line for the "set" modifier in ACLs was not showing the
2402 name of the variable that was being set.
2404 17. Code tidy: the variable type "vtype_string" was never used. Removed it.
2406 18. Previously, a reference to $sender_host_name did not cause a DNS reverse
2407 lookup on its own. Something else was needed to trigger the lookup. For
2408 example, a match in host_lookup or the need for a host name in a host list.
2409 Now, if $sender_host_name is referenced and the host name has not yet been
2410 looked up, a lookup is performed. If the lookup fails, the variable remains
2411 empty, and $host_lookup_failed is set to "1".
2413 19. Added "eqi" as a case-independent comparison operator.
2415 20. The saslauthd authentication condition could segfault if neither service
2416 nor realm was specified.
2418 21. If an overflowing value such as "2048M" was set for message_size_limit, the
2419 error message that was logged was misleading, and incoming SMTP
2420 connections were dropped. The message is now more accurate, and temporary
2421 errors are given to SMTP connections.
2423 22. In some error situations (such as 21 above) Exim rejects all SMTP commands
2424 (except RSET) with a 421 error, until QUIT is received. However, it was
2425 failing to send a response to QUIT.
2427 23. The HELO ACL was being run before the code for helo_try_verify_hosts,
2428 which made it impossible to use "verify = helo" in the HELO ACL. The HELO
2429 ACL is now run after the helo_try_verify_hosts code.
2431 24. "{MD5}" and "{SHA1}" are now recognized as equivalent to "{md5"} and
2432 "{sha1}" in the "crypteq" expansion condition (in fact the comparison is
2433 case-independent, so other case variants are also recognized). Apparently
2434 some systems use these upper case variants.
2436 25. If more than two messages were waiting for the same host, and a transport
2437 filter was specified for the transport, Exim sent two messages over the
2438 same TCP/IP connection, and then failed with "socket operation on non-
2439 socket" when it tried to send the third.
2441 26. Added Exim::debug_write and Exim::log_write for embedded Perl use.
2443 27. The extern definition of crypt16() in expand.c was not being excluded when
2444 the OS had its own crypt16() function.
2446 28. Added bounce_return_body as a new option, and bounce_return_size_limit
2447 as a preferred synonym for return_size_limit, both as an option and as an
2450 29. Added LIBS=-liconv to OS/Makefile-OSF1.
2452 30. Changed the default configuration ACL to relax the local part checking rule
2453 for addresses that are not in any local domains. For these addresses,
2454 slashes and pipe symbols are allowed within local parts, but the sequence
2455 /../ is explicitly forbidden.
2457 31. SPA server authentication was not clearing the challenge buffer before
2460 32. log_message in a "warn" ACL statement was writing to the reject log as
2461 well as to the main log, which contradicts the documentation and doesn't
2462 seem right (because no rejection is happening). So I have stopped it.
2464 33. Added Ard Biesheuvel's lookup code for accessing an Interbase database.
2465 However, I am unable to do any testing of this.
2467 34. Fixed an infelicity in the appendfile transport. When checking directories
2468 for a mailbox, to see if any needed to be created, it was accidentally
2469 using path names with one or more superfluous leading slashes; tracing
2470 would show up entries such as stat("///home/ph10", 0xFFBEEA48).
2472 35. If log_message is set on a "discard" verb in a MAIL or RCPT ACL, its
2473 contents are added to the log line that is written for every discarded
2474 recipient. (Previously a log_message setting was ignored.)
2476 36. The ${quote: operator now quotes the string if it is empty.
2478 37. The install script runs exim in order to find its version number. If for
2479 some reason other than non-existence or emptiness, which it checks, it
2480 could not run './exim', it was installing it with an empty version number,
2481 i.e. as "exim-". This error state is now caught, and the installation is
2484 38. An argument was missing from the function that creates an error message
2485 when Exim fails to connect to the socket for saslauthd authentication.
2486 This could cause Exim to crash, or give a corrupted message.
2488 39. Added isip, isip4, and isip6 to ${if conditions.
2490 40. The ACL variables $acl_xx are now saved with the message, and can be
2491 accessed later in routers, transports, and filters.
2493 41. The new lookup type nwildlsearch is like wildlsearch, except that the key
2494 strings in the file are not string-expanded.
2496 42. If a MAIL command specified a SIZE value that was too large to fit into an
2497 int variable, the check against message_size_limit failed. Such values are
2498 now forced to INT_MAX, which is around 2Gb for a 32-bit variable. Maybe one
2499 day this will have to be increased, but I don't think I want to be around
2500 when emails are that large.
2507 1. Removed HAVE_ICONV=yes from OS/Makefile-FreeBSD, since it seems that
2508 iconv() is not standard in FreeBSD.
2510 2. Change 4.21/17 was buggy and could cause stack overwriting on a system with
2511 IPv6 enabled. The observed symptom was a segmentation fault on return from
2512 the function os_common_find_running_interfaces() in src/os.c.
2514 3. In the check_special_case() function in daemon.c I had used "errno" as an
2515 argument name, which causes warnings on some systems. This was basically a
2516 typo, since it was named "eno" in the comments!
2518 4. The code that waits for the clock to tick (at a resolution of some fraction
2519 of a second) so as to ensure message-id uniqueness was always waiting for
2520 at least one whole tick, when it could have waited for less. [This is
2521 almost certainly not relevant at current processor speeds, where it is
2522 unlikely to ever wait at all. But we try to future-proof.]
2524 5. The function that sleeps for a time interval that includes fractions of a
2525 second contained a race. It did not block SIGALRM between setting the
2526 timer, and suspending (a couple of lines later). If the interval was short
2527 and the sigsuspend() was delayed until after it had expired, the suspension
2528 never ended. On busy systems this could lead to processes getting stuck for
2531 6. Some uncommon configurations may cause a lookup to happen in a queue runner
2532 process, before it forks any delivery processes. The open lookup caching
2533 mechanism meant that the open file or database connection was passed into
2534 the delivery process. The problem was that delivery processes always tidy
2535 up cached lookup data. This could cause a problem for the next delivery
2536 process started by the queue runner, because the external queue runner
2537 process does not know about the closure. So the next delivery process
2538 still has data in the lookup cache. In the case of a file lookup, there was
2539 no problem because closing a file descriptor in a subprocess doesn't affect
2540 the parent. However, if the lookup was caching a connection to a database,
2541 the connection was closed, and the second delivery process was likely to
2542 see errors such as "PGSQL: query failed: server closed the connection
2543 unexpectedly". The problem has been fixed by closing all cached lookups
2544 in a queue runner before running a delivery process.
2546 7. Compiler warning on Linux for the second argument of iconv(), which doesn't
2547 seem to have the "const" qualifier which it has on other OS. I've
2550 8. Change 4.21/2 was too strict. It is only if there are two authenticators
2551 *of the same type* (client or server) with the same public name that an
2552 error should be diagnosed.
2554 9. When Exim looked up a host name for an IP address, but failed to find the
2555 original IP address when looking up the host name (a safety check), it
2556 output the message "<ip address> does not match any IP for NULL", which was
2557 confusing, to say the least. The bug was that the host name should have
2558 appeared instead of "NULL".
2560 10. Since release 3.03, if Exim is called by a uid other than root or the Exim
2561 user that is built into the binary, and the -C or -D options is used, root
2562 privilege is dropped before the configuration file is read. In addition,
2563 logging is switched to stderr instead of the normal log files. If the
2564 configuration then re-defines the Exim user, the unprivileged environment
2565 is probably not what is expected, so Exim logs a panic warning message (but
2568 However, if deliver_drop_privilege is set, the unprivileged state may well
2569 be exactly what is intended, so the warning has been cut out in that case,
2570 and Exim is allowed to try to write to its normal log files.
2576 1. smtp_return_error_details was not giving details for temporary sender
2577 or receiver verification errors.
2579 2. Diagnose a configuration error if two authenticators have the same public
2582 3. Exim used not to create the message log file for a message until the first
2583 delivery attempt. This could be confusing when incoming messages were held
2584 for policy or load reasons. The message log file is now created at the time
2585 the message is received, and an initial "Received" line is written to it.
2587 4. The automatically generated man page for command line options had a minor
2588 bug that caused no ill effects; however, a more serious problem was that
2589 the procedure for building the man page automatically didn't always
2590 operate. Consequently, release 4.20 contains an out-of-date version. This
2591 shouldn't happen again.
2593 5. When building Exim with embedded Perl support, the script that builds the
2594 Makefile was calling 'perl' to find its compile-time parameters, ignoring
2595 any setting of PERL_COMMAND in Local/Makefile. This is now fixed.
2597 6. The freeze_tell option was not being used for messages that were frozen on
2598 arrival, either by an ACL or by local_scan().
2600 7. Added the smtp_incomplete_transaction log selector.
2602 8. After STARTTLS, Exim was not forgetting that it had advertised AUTH, so it
2603 was accepting AUTH without a new EHLO.
2605 9. Added tls_remember_esmtp to cope with YAEB. This allows AUTH and other
2606 ESMTP extensions after STARTTLS without a new EHLO, in contravention of the
2609 10. Logging of TCP/IP connections (when configured) now happens in the main
2610 daemon process instead of the child process, so that the TCP/IP connection
2611 count is more accurate (but it can never be perfect).
2613 11. The use of "drop" in a nested ACL was not being handled correctly in the
2614 outer ACL. Now, if condition failure induced by the nested "drop" causes
2615 the outer ACL verb to deny access ("accept" or "discard" after "endpass",
2616 or "require"), the connection is dropped.
2618 12. Similarly, "discard" in a nested ACL wasn't being handled. A nested ACL
2619 that yield "discard" can now be used with an "accept" or a "discard" verb,
2620 but an error is generated for any others (because I can't see a useful way
2621 to define what should happen).
2623 13. When an ACL is read dynamically from a file (or anywhere else), the lines
2624 are now processed in the same way as lines in the Exim configuration file.
2625 In particular, continuation lines are supported.
2627 14. Added the "dnslists = a.b.c!=n.n.n.n" feature.
2629 15. Added -ti meaning -t -i.
2631 16. Check for letters, digits, hyphens, and dots in the names of dnslist
2632 domains, and warn by logging if others are found.
2634 17. At least on BSD, alignment is not guarenteed for the array of ifreq's
2635 returned from GIFCONF when Exim is trying to find the list of interfaces on
2636 a host. The code in os.c has been modified to copy each ifreq to an aligned
2637 structure in all cases.
2639 Also, in some cases, the returned ifreq's were being copied to a 'struct
2640 ifreq' on the stack, which was subsequently passed to host_ntoa(). That
2641 means the last couple of bytes of an IPv6 address could be chopped if the
2642 ifreq contained only a normal sockaddr (14 bytes storage).
2644 18. Named domain lists were not supported in the hosts_treat_as_local option.
2645 An entry such as +xxxx was not recognized, and was treated as a literal
2648 19. Ensure that header lines added by a DATA ACL are included in the reject log
2649 if the ACL subsequently rejects the message.
2651 20. Upgrade the cramtest.pl utility script to use Digest::MD5 instead of just
2652 MD5 (which is deprecated).
2654 21. When testing a filter file using -bf, Exim was writing a message when it
2655 took the sender from a "From " line in the message, but it was not doing so
2656 when it took $return_path from a Return-Path: header line. It now does.
2658 22. If the contents of a "message" modifier for a "warn" ACL verb do not begin
2659 with a valid header line field name (a series of printing characters
2660 terminated by a colon, Exim now inserts X-ACL-Warn: at the beginning.
2662 23. Changed "disc" in the source to "disk" to conform to the documentation and
2663 the book and for uniformity.
2665 24. Ignore Sendmail's -Ooption=value command line item.
2667 25. When execve() failed while trying to run a command in a pipe transport,
2668 Exim was returning EX_UNAVAILBLE (69) from the subprocess. However, this
2669 could be confused with a return value of 69 from the command itself. This
2670 has been changed to 127, the value the shell returns if it is asked to run
2671 a non-existent command. The wording for the related log line suggests a
2672 non-existent command as the problem.
2674 26. If received_header_text expands to an empty string, do not add a Received:
2675 header line to the message. (Well, it adds a token one on the spool, but
2676 marks it "old" so that it doesn't get used or transmitted.)
2678 27. Installed eximstats 1.28 (addition of -nt option).
2680 28. There was no check for failure on the call to getsockname() in the daemon
2681 code. This can fail if there is a shortage of resources on the system, with
2682 ENOMEM, for example. A temporary error is now given on failure.
2684 29. Contrary to the C standard, it seems that in some environments, the
2685 equivalent of setlocale(LC_ALL, "C") is not obeyed at the start of a C
2686 program. Exim now does this explicitly; it affects the formatting of
2687 timestamps using strftime().
2689 30. If exiqsumm was given junk data, it threw up some uninitialized variable
2690 complaints. I've now initialized all the variables, to avoid this.
2692 32. Header lines added by a system filter were not being "seen" during
2693 transport-time rewrites.
2695 33. The info_callback() function passed to OpenSSL is set up with type void
2696 (*)(SSL *, int, int), as described somewhere. However, when calling the
2697 function (actually a macro) that sets it up, the type void(*)() is
2698 expected. I've put in a cast to prevent warnings from picky compilers.
2700 34. If a DNS black list lookup found a CNAME record, but there were no A
2701 records associated with the domain it pointed at, Exim crashed.
2703 35. If a DNS black list lookup returned more than one A record, Exim ignored
2704 all but the first. It now scans all returned addresses if a particular IP
2705 value is being sought. In this situation, the contents of the
2706 $dnslist_value variable are a list of all the addresses, separated by a
2709 36. Tightened up the rules for host name lookups using reverse DNS. Exim used
2710 to accept a host name and all its aliases if the forward lookup for any of
2711 them yielded the IP address of the incoming connection. Now it accepts only
2712 those names whose forward lookup yields the correct IP address. Any other
2713 names are discarded. This closes a loophole whereby a rogue DNS
2714 administrator could create reverse DNS records to break through a
2715 wildcarded host restriction in an ACL.
2717 37. If a user filter or a system filter that ran in a subprocess used any of
2718 the numerical variables ($1, $2 etc), or $thisaddress, in a pipe command,
2719 the wrong values were passed to the pipe command ($thisaddress had the
2720 value of $0, $0 had the value of $1, etc). This bug was introduced by
2721 change 4.11/101, and not discovered because I wrote an inadequate test. :-(
2723 38. Improved the line breaking for long SMTP error messages from ACLs.
2724 Previously, if there was no break point between 40 and 75 characters, Exim
2725 left the rest of the message alone. Two changes have been made: (a) I've
2726 reduced the minimum length to 35 characters; (b) if it can't find a break
2727 point between 35 and 75 characters, it looks ahead and uses the first one
2728 that it finds. This may give the occasional overlong line, but at least the
2729 remaining text gets split now.
2731 39. Change 82 of 4.11 was unimaginative. It assumed the limit on the number of
2732 file descriptors might be low, and that setting 1000 would always raise it.
2733 It turns out that in some environments, the limit is already over 1000 and
2734 that lowering it causes trouble. So now Exim takes care not to decrease it.
2736 40. When delivering a message, the value of $return_path is set to $sender_
2737 address at the start of routing (routers may change the value). By an
2738 oversight, this default was not being set up when an address was tested by
2739 -bt or -bv, which affected the outcome if any router or filter referred to
2742 41. The idea of the "warn" ACL verb is that it adds a header or writes to the
2743 log only when "message" or "log_message" are set. However, if one of the
2744 conditions was an address verification, or a call to a nested ACL, the
2745 messages generated by the underlying test were being passed through. This
2746 no longer happens. The underlying message is available in $acl_verify_
2747 message for both "message" and "log_message" expansions, so it can be
2748 passed through if needed.
2750 42. Added RFC 2047 interpretation of header lines for $h_ expansions, with a
2751 new expansion $bh_ to give the encoded byte string without charset
2752 translation. Translation happens only if iconv() is available; HAVE_ICONV
2753 indicates this at build time. HEADERS_CHARSET gives the charset to
2754 translate to; headers_charset can change it in the configuration, and
2755 "headers charset" can change it in an individual filter file.
2757 43. Now that we have a default RFC 2047 charset (see above), the code in Exim
2758 that creates RFC 2047 encoded "words" labels them as that charset instead
2759 of always using iso-8859-1. The cases are (i) the explicit ${rfc2047:
2760 expansion operator; (ii) when Exim creates a From: line for a local
2761 message; (iii) when a header line is rewritten to include a "phrase" part.
2763 44. Nasty bug in exiqsumm: the regex to skip already-delivered addresses was
2764 buggy, causing it to skip the first lines of messages whose message ID
2765 ended in 'D'. This would not have bitten before Exim release 4.14, because
2766 message IDs were unlikely to end in 'D' before then. The effect was to have
2767 incorrect size information for certain domains.
2769 45. #include "config.h" was missing at the start of the crypt16.c module. This
2770 caused trouble on Tru64 (aka OSF1) systems, because HAVE_CRYPT16 was not
2773 46. If there was a timeout during a "random" callout check, Exim treated it as
2774 a failure of the random address, and carried on sending RSET and the real
2775 address. If the delay was just some slowness somewhere, the response to the
2776 original RCPT would be taken as a response to RSET and so on, causing
2777 mayhem of various kinds.
2779 47. Change 50 for 4.20 was a heap of junk. I don't know what I was thinking
2780 when I implemented it. It didn't allow for the fact that some option values
2781 may legitimatetly be negative (e.g. size_addition), and it didn't even do
2782 the right test for positive values.
2784 48. Domain names in DNS records are case-independent. Exim always looks them up
2785 in lower case. Some resolvers return domain names in exactly the case they
2786 appear in the zone file, that is, they may contain uppercase letters. Not
2787 all resolvers do this - some return always lower case. Exim was treating a
2788 change of case by a resolver as a change of domain, similar to a widening
2789 of a domain abbreviation. This triggered its re-routing code and so it was
2790 trying to route what was effectively the same domain again. This normally
2791 caused routing to fail (because the router wouldn't handle the domain
2792 twice). Now Exim checks for this case specially, and just changes the
2793 casing of the domain that it ultimately uses when it transmits the message
2796 49. Added Sieve (RFC 3028) support, courtesy of Michael Haardt's contributed
2799 50. If a filter generated a file delivery with a non-absolute name (possible if
2800 no home directory exists for the router), the forbid_file option was not
2803 51. Added '&' feature to dnslists, to provide bit mask matching in addition to
2804 the existing equality matching.
2806 52. Exim was using ints instead of ino_t variables in some places where it was
2807 dealing with inode numbers.
2809 53. If TMPDIR is defined in Local/Makefile (default in src/EDITME is
2810 TMPDIR="/tmp"), Exim checks for the presence of an environment variable
2811 called TMPDIR, and if it finds it is different, it changes its value.
2813 54. The smtp_printf() function is now made available to local_scan() so
2814 additional output lines can be written before returning. There is also an
2815 smtp_fflush() function to enable the detection of a dropped connection.
2816 The variables smtp_input and smtp_batched_input are exported to
2819 55. Changed the default runtime configuration: the message "Unknown user"
2820 has been removed from the ACL, and instead placed on the localuser router,
2821 using the cannot_route_message feature. This means that any verification
2822 failures that generate their own messages won't get overridden. Similarly,
2823 the "Unrouteable address" message that was in the ACL for unverifiable
2824 relay addresses has also been removed.
2826 56. Added hosts_avoid_esmtp to the smtp transport.
2828 57. The exicyclog script was not checking for the esoteric option
2829 CONFIGURE_FILE_USE_EUID in the Local/Makefile. It now does this, but it
2830 will work only if exicyclog is run under the appropriate euid.
2832 58. Following a discussion on the list, the rules by which Exim recognises line
2833 endings on incoming messages have been changed. The -dropcr and drop_cr
2834 options are now no-ops, retained only for backwards compatibility. The
2835 following line terminators are recognized: LF CRLF CR. However, special
2836 processing applies to CR:
2838 (i) The sequence CR . CR does *not* terminate an incoming SMTP message,
2839 nor a local message in the state where . is a terminator.
2841 (ii) If a bare CR is encountered in a header line, an extra space is added
2842 after the line terminator so as not to end the header. The reasoning
2843 behind this is that bare CRs in header lines are most likely either
2844 to be mistakes, or people trying to play silly games.
2846 59. The size of a message, as listed by "-bp" or in the Exim monitor window,
2847 was being incorrectly given as 18 bytes larger than it should have been.
2848 This is a VOB (very old bug).
2850 60. This may never have affected anything current, but just in case it has:
2851 When the local host is found other than at the start of a list of hosts,
2852 the local host, those with the same MX, and any that follow, are discarded.
2853 When the list in question was part of a longer list of hosts, the following
2854 hosts (not currently being processed) were also being discarded. This no
2855 longer happens. I'm not sure if this situation could ever has previously
2858 61. Added the "/MX" feature to lists of hosts in the manualroute and query
2861 62. Whenever Exim generates a new message, it now adds an Auto-Submitted:
2862 header. This is something that is recommended in a new Internet Draft, and
2863 is something that is documented as being done by Sendmail. There are two
2864 possible values. For messages generated by the autoreply transport, Exim
2867 Auto-Submitted: auto-replied
2869 whereas for all other generated messages (e.g. bounces) it adds
2871 Auto-Submitted: auto-generated
2873 63. The "personal" condition in filters now includes a test for the
2874 Auto-Submitted: header. If it contains the string "auto-" the message it
2875 not considered personal.
2877 64. Added rcpt_include_affixes as a generic transport option.
2879 65. Added queue_only_override (default true).
2881 66. Added the syslog_duplication option.
2883 67. If what should have been the first header line of a message consisted of
2884 a space followed by a colon, Exim was mis-interpreting it as a header line.
2885 It isn't of course - it is syntactically invalid and should therefore be
2886 treated as the start of the message body. The misbehaviour could have
2887 caused a number of strange effects, including loss of data in subsequent
2888 header lines, and spool format errors.
2890 68. Formerly, the AUTH parameter on a MAIL command was trusted only if the
2891 client host had authenticated. This control can now be exercised by an ACL
2892 for more flexibility.
2894 69. By default, callouts do not happen when testing with -bh. There is now a
2895 variant, -bhc, which does actually run the callout code, including
2896 consulting and updating the callout cache.
2898 70. Added support for saslauthd authentication, courtesy of Alexander
2901 71. If statvfs() failed on the spool or log directories while checking their
2902 size for availability, Exim confusingly gave the error "space shortage".
2903 Furthermore, in debugging mode it crashed with a floating point exception.
2904 These checks are done if check_{spool,log}_{space,inodes} are set, and when
2905 an SMTP message arrives with SIZE= on the MAIL command. As this is a really
2906 serious problem, Exim now writes to the main and panic logs when this
2907 happens, with details of the failure. It then refuses to accept the
2908 incoming message, giving the message "spool directory problem" or "log
2909 directory problem" with a 421 code for SMTP messages.
2911 72. When Exim is about to re-exec itself, it ensures that the file descriptors
2912 0, 1, and 2 exist, because some OS complain for execs without them (see
2913 ChangeLog 4.05/30). If necessary, Exim opens /dev/null to use for these
2914 descriptors. However, the code omitted to check that the open succeeded,
2915 causing mysterious errors if for some reason the permissions on /dev/null
2916 got screwed. Now Exim writes a message to the main and panic logs, and
2917 bombs out if it can't open /dev/null.
2919 73. Re-vamped the way daemon_smtp_port, local_interfaces, and -oX work and
2920 interact so that it is all more flexible. It is supposed to remain
2921 backwards compatible. Also added extra_local_interfaces.
2923 74. Invalid data sent to a SPA (NTLM) server authenticator could cause the code
2924 to bomb out with an assertion failure - to the client this appears as a
2925 connection drop. This problem occurs in the part of the code that was taken
2926 from the Samba project. Fortunately, the assertion is in a very simple
2927 function, so I have fixed this by reproducing the function inline in the
2928 one place where it is called, and arranging for authentication to fail
2929 instead of killing the process with assert().
2931 75. The SPA client code was not working when the server requested OEM rather
2932 than Unicode encoding.
2934 76. Added code to make require_files with a specific uid setting more usable in
2935 the case where statting the file as root fails - usually a non-root-mounted
2936 NFS file system. When this happens and the failure is EACCES, Exim now
2937 forks a subprocess and does the per-uid checking as the relevant uid.
2939 77. Added process_log_path.
2941 78. If log_file_path was not explicitly set, a setting of check_log_space or
2942 check_log_inodes was ignored.
2944 79. If a space check for the spool or log partitions fails, the incident is now
2945 logged. Of course, in the latter case the data may get lost...
2947 80. Added the %p formatting code to string_format() so that it can be used to
2948 print addresses in debug_print(). Adjusted all the address printing in the
2949 debugging in store.c to use %p rather than %d.
2951 81. There was a concern that a line of code in smtp_in.c could overflow a
2952 buffer if a HELO/EHLO command was given followed by 500 or so spaces. As
2953 initially expressed, the concern was not well-founded, because trailing
2954 spaces are removed early. However, if the trailing spaces were followed by
2955 a NULL, they did not get removed, so the overflow was possible. Two fixes
2958 (a) I re-wrote the offending code in a cleaner fashion.
2959 (b) If an incoming SMTP command contains a NULL character, it is rejected
2962 82. When Exim changes uid/gid to the Exim user at daemon start time, it now
2963 runs initgroups(), so that if the Exim user is in any additional groups,
2964 they will be used during message reception.
2970 The change log for 4.20 and earlier releases has been archived.
git://git.exim.org / users / jgh / exim.git / blob