[exim.git] / doc / doc-txt / ChangeLog
1 $Cambridge: exim/doc/doc-txt/ChangeLog,v 1.116 2005/04/06 14:40:23 ph10 Exp $
3 Change log file for Exim from version 4.21
4 -------------------------------------------
7 Exim version 4.51
8 -----------------
10 TK/01 Added Yahoo DomainKeys support via libdomainkeys. See
11 doc/experimental-spec.txt for details. (http://domainkeys.sf.net)
13 TK/02 Fix ACL "control" statement not being available in MIME ACL.
15 TK/03 Fix ACL "regex" condition not being available in MIME ACL.
17 PH/01 Installed a patch from the Sieve maintainer that allows -bf to be used
18 to test Sieve filters that use "vacation".
20 PH/02 Installed a slightly modified version of Nikos Mavrogiannopoulos' patch
21 that changes the way the GnuTLS parameters are stored in the cache file.
22 The new format can be generated externally. For backward compatibility,
23 if the data in the cache doesn't make sense, Exim assumes it has read an
24 old-format file, and it generates new data and writes a new file. This
25 means that you can't go back to an older release without removing the
26 file.
28 PH/03 A redirect router that has both "unseen" and "one_time" set does not
29 work if there are any delivery delays because "one_time" forces the
30 parent to be marked "delivered", so its unseen clone is never tried
31 again. For this reason, Exim now forbids the simultaneous setting of
32 these two options.
34 PH/04 Change 4.11/85 fixed an obscure bug concerned with addresses that are
35 redirected to themselves ("homonym" addresses). Read the long ChangeLog
36 entry if you want to know the details. The fix, however, neglected to
37 consider the case when local delivery batching is involved. The test for
38 "previously delivered" was not happening when checking to see if an
39 address could be batched with a previous (undelivered) one; under
40 certain circumstances this could lead to multiple deliveries to the same
41 address.
43 PH/05 Renamed the macro SOCKLEN_T as EXIM_SOCKLEN_T because AIX uses SOCKLEN_T
44 in its include files, and this causes problems building Exim.
46 PH/06 A number of "verify =" ACL conditions have no options (e.g. verify =
47 header_syntax) but Exim was just ignoring anything given after a slash.
48 In particular, this caused confusion with an attempt to use "verify =
49 reverse_host_lookup/defer_ok". An error is now given when options are
50 supplied for verify items that do not have them. (Maybe reverse_host_
51 lookup should have a defer_ok option, but that's a different point.)
53 PH/07 Increase the size of the buffer for incoming SMTP commands from 512 (as
54 defined by RFC 821) to 2048, because there were problems with some AUTH
55 commands, and RFC 1869 says the size should be increased for extended
56 SMTP commands that take arguments.
58 PH/08 Added ${dlfunc dynamically loaded function for expansion (code from Tony
59 Finch).
61 PH/09 Previously, an attempt to use ${perl when it wasn't compiled gave an
62 "unknown" error; now it says that the functionality isn't in the binary.
64 PH/10 Added a nasty fudge to try to recognize and flatten LDAP passwords in
65 an address' error message when a string expansion fails (syntax or
66 whatever). Otherwise not only does the password appear in the log, it may
67 also be put in a bounce message.
69 PH/11 Installed exipick version 20050225.0 from John Jetmore.
71 PH/12 If the last host in a fallback_hosts list was multihomed, only the first
72 of its addresses was ever tried. (Bugzilla bug #2.)
74 PH/13 If "headers_add" in a transport didn't end in a newline, Exim printed
75 the result incorrectly in the debug output. (It correctly added a newline
76 to what was transported.)
78 TF/01 Added $received_time.
80 PH/14 Modified the default configuration to add an acl_smtp_data ACL, with
81 commented out examples of how to interface to a virus scanner and to
82 SpamAssassin. Also added commented examples of av_scanner and
83 spamd_address settings.
85 PH/15 Further to TK/02 and TK/03 above, tidied up the tables of what conditions
86 and controls are allowed in which ACLs. There were a couple of minor
87 errors. Some of the entries in the conditions table (which is a table of
88 where they are NOT allowed) were getting very unwieldy; rewrote them as a
89 negation of where the condition IS allowed.
91 PH/16 Installed updated OS/os.c-cygwin from the Cygwin maintainer.
93 PH/17 The API for radiusclient changed at release 0.4.0. Unfortunately, the
94 header file does not have a version number, so I've had to invent a new
95 value for RADIUS_LIB_TYPE, namely "RADIUSCLIENTNEW" to request the new
96 API. The code is untested by me (my Linux distribution still has 0.3.2 of
97 radiusclient), but it was contributed by a Radius user.
99 PH/18 Installed Lars Mainka's patch for the support of CRL collections in
100 files or directories, for OpenSSL.
102 PH/19 When an Exim process that is running as root has to create an Exim log
103 file, it does so in a subprocess that runs as exim:exim so as to get the
104 ownership right at creation (otherwise, other Exim processes might see
105 the file with the wrong ownership). There was no test for failure of this
106 fork() call, which would lead to the process getting stuck as it waited
107 for a non-existent subprocess. Forks do occasionally fail when resources
108 run out. I reviewed all the other calls to fork(); they all seem to check
109 for failure.
111 PH/20 When checking for unexpected SMTP input at connect time (before writing
112 the banner), Exim was not dealing correctly with a non-positive return
113 from the read() function. If the client had disconnected by this time,
114 the result was a log entry for a synchronization error with an empty
115 string after "input=" when read() returned zero. If read() returned -1
116 (an event I could not check), uninitialized data bytes were printed.
117 There were reports of junk text (parts of files, etc) appearing after
118 "input=".
120 PH/21 Added acl_not_smtp_mime to allow for MIME scanning for non-SMTP messages.
122 PH/22 Added support for macro redefinition, and (re)definition in between
123 driver and ACL definitions.
125 PH/23 The cyrus_sasl authenticator was expanding server_hostname, but then
126 forgetting to use the resulting value; it was using the unexpanded value.
128 PH/24 The cyrus_sasl authenticator was advertising mechanisms for which it
129 hadn't been configured. The fix is from Juergen Kreileder, who
130 understands it better than I do:
132 "Here's what I see happening with three configured cyrus_sasl
133 authenticators configured (plain, login, cram-md5):
135 On startup auth_cyrus_sasl_init() gets called for each of these.
136 This means three calls to sasl_listmech() without a specified mech_list.
137 => SASL tests which mechs of all available mechs actually work
138 => three warnings about OTP not working
139 => the returned list contains: plain, login, cram-md5, digest-md5, ...
141 With the patch, sasl_listmech() also gets called three times. But now
142 SASL's mech_list option is set to the server_mech specified in the the
143 authenticator. Or in other words, the answer from sasl_listmech()
144 gets limited to just the mech you're testing for (which is different
145 for each call.)
146 => the return list contains just 'plain' or 'login', 'cram-md5' or
147 nothing depending on the value of ob->server_mech.
149 I've just tested the patch: Authentication still works fine,
150 unavailable mechs specified in the exim configuration are still
151 caught, and the auth.log warnings about OTP are gone."
153 PH/25 When debugging is enabled, the contents of the command line are added
154 to the debugging output, even when log_selector=+arguments is not
155 specified.
157 PH/26 Change scripts/os-type so that when "uname -s" returns just "GNU", the
158 answer is "GNU", and only if the return is "GNU/something" is the answer
159 "Linux".
161 PH/27 $acl_verify_message is now set immediately after the failure of a
162 verification in an ACL, and so is available in subsequent modifiers. In
163 particular, the message can be preserved by coding like this:
165 warn !verify = sender
166 set acl_m0 = $acl_verify_message
168 Previously, $acl_verify_message was set only while expanding "message"
169 and "log_message" when a very denied access.
171 PH/28 Modified OS/os.c-Linux with
173 -#ifndef OS_LOAD_AVERAGE
174 +#if !defined(OS_LOAD_AVERAGE) && defined(__linux__)
176 to make Exim compile on kfreebsd-gnu. (I'm totally confused about the
177 nomenclature these days.)
179 PH/29 Installed patch from the Sieve maintainer that adds the options
180 sieve_useraddress and sieve_subaddress to the redirect router.
184 A note about Exim versions 4.44 and 4.50
185 ----------------------------------------
187 Exim 4.50 was meant to be the next release after 4.43. It contains a lot of
188 changes of various kinds. As a consequence, a big documentation update was
189 needed. This delayed the release for rather longer than seemed good, especially
190 in the light of a couple of (minor) security issues. Therefore, the changes
191 that fixed bugs were backported into 4.43, to create a 4.44 maintenance
192 release. So 4.44 and 4.50 are in effect two different branches that both start
193 from 4.43.
195 I have left the 4.50 change log unchanged; it contains all the changes since
196 4.43. The change log for 4.44 is below; many of its items are identical to
197 those for 4.50. This seems to be the most sensible way to preserve the
198 historical information.
201 Exim version 4.50
202 -----------------
204 1. Minor wording change to the doc/README.SIEVE file.
206 2. Change 4.43/35 introduced a bug: if quota_filecount was set, the
207 computation of the current number of files was incorrect.
209 3. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
210 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
211 place.
213 4. Give more explanation in the error message when the command for a transport
214 filter fails to execute.
216 5. There are several places where Exim runs a non-Exim command in a
217 subprocess. The SIGUSR1 signal should be disabled for these processes. This
218 was being done only for the command run by the queryprogram router. It is
219 now done for all such subprocesses. The other cases are: ${run, transport
220 filters, and the commands run by the lmtp and pipe transports.
222 6. Added CONFIGURE_GROUP build-time option.
224 7. Some older OS have a limit of 256 on the maximum number of file
225 descriptors. Exim was using setrlimit() to set 1000 as a large value
226 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
227 systems. I've change it so that if it can't get 1000, it tries for 256.
229 8. "control=submission" was allowed, but had no effect, in a DATA ACL. This
230 was an oversight, and furthermore, ever since the addition of extra
231 controls (e.g. 4.43/32), the checks on when to allow different forms of
232 "control" were broken. There should now be diagnostics for all cases when a
233 control that does not make sense is encountered.
235 9. Added the /retain_sender option to "control=submission".
237 10. $recipients is now available in the predata ACL (oversight).
239 11. Tidy the search cache before the fork to do a delivery from a message
240 received from the command line. Otherwise the child will trigger a lookup
241 failure and thereby defer the delivery if it tries to use (for example) a
242 cached ldap connection that the parent has called unbind on.
244 12. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
245 of $address_data from the recipient verification was clobbered by the
246 sender verification.
248 13. The value of address_data from a sender verification is now available in
249 $sender_address_data in subsequent conditions in the ACL statement.
251 14. Added forbid_sieve_filter and forbid_exim_filter to the redirect router.
253 15. Added a new option "connect=<time>" to callout options, to set a different
254 connection timeout.
256 16. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
257 was its contents. (It was OK if the option was not defined at all.)
259 17. A "Completed" log line is now written for messages that are removed from
260 the spool by the -Mrm option.
262 18. New variables $sender_verify_failure and $recipient_verify_failure contain
263 information about exactly what failed.
265 19. Added -dd to debug only the daemon process.
267 20. Incorporated Michael Haardt's patch to ldap.c for improving the way it
268 handles timeouts, both on the server side and network timeouts. Renamed the
269 CONNECT parameter as NETTIMEOUT (but kept the old name for compatibility).
271 21. The rare case of EHLO->STARTTLS->HELO was setting the protocol to "smtp".
272 It is now set to "smtps".
274 22. $host_address is now set to the target address during the checking of
275 ignore_target_hosts.
277 23. When checking ignore_target_hosts for an ipliteral router, no host name was
278 being passed; this would have caused $sender_host_name to have been used if
279 matching the list had actually called for a host name (not very likely,
280 since this list is usually IP addresses). A host name is now passed as
281 "[x.x.x.x]".
283 24. Changed the calls that set up the SIGCHLD handler in the daemon to use the
284 code that specifies a non-restarting handler (typically sigaction() in
285 modern systems) in an attempt to fix a rare and obscure crash bug.
287 25. Narrowed the window for a race in the daemon that could cause it to ignore
288 SIGCHLD signals. This is not a major problem, because they are used only to
289 wake it up if nothing else does.
291 26. A malformed maildirsize file could cause Exim to calculate negative values
292 for the mailbox size or file count. Odd effects could occur as a result.
293 The maildirsize information is now recalculated if the size or filecount
294 end up negative.
296 27. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
297 support for a long time. Removed HAVE_SYS_VFS_H.
299 28. Installed the latest version of exipick from John Jetmore.
301 29. In an address list, if the pattern was not a regular expression, an empty
302 subject address (from a bounce message) matched only if the pattern was an
303 empty string. Non-empty patterns were not even tested. This was the wrong
304 because it is perfectly reasonable to use an empty address as part of a
305 database query. An empty address is now tested by patterns that are
306 lookups. However, all the other forms of pattern expect the subject to
307 contain a local part and a domain, and therefore, for them, an empty
308 address still always fails if the pattern is not itself empty.
310 30. Exim went into a mad DNS loop when attempting to do a callout where the
311 host was specified on an smtp transport, and looking it up yielded more
312 than one IP address.
314 31. Re-factored the code for checking spool and log partition space into a
315 function that finds that data and another that does the check. The former
316 is then used to implement four new variables: $spool_space, $log_space,
317 $spool_inodes, and $log_inodes.
319 32. The RFC2047 encoding function was originally intended for short strings
320 such as real names; it was not keeping to the 75-character limit for
321 encoded words that the RFC imposes. It now respects the limit, and
322 generates multiple encoded words if necessary. To be on the safe side, I
323 have increased the buffer size for the ${rfc2047: expansion operator from
324 1024 to 2048 bytes.
326 33. It is now permitted to omit both strings after an "if" condition; if the
327 condition is true, the result is "true". As before, when the second string
328 is omitted, a false condition yields an empty string. This makes it less
329 cumbersome to write custom ACL and router conditions.
331 34. Failure to deliver a bounce message always caused it to be frozen, even if
332 there was an errors_to setting on the router. The errors_to setting is now
333 respected.
335 35. If an IPv6 address is given for -bh or -bhc, it is now converted to the
336 canonical form (fully expanded) before being placed in
337 $sender_host_address.
339 36. The table in the code that translates DNS record types into text (T_A to
340 "A" for instance) was missing entries for NS and CNAME. It is just possible
341 that this could have caused confusion if both these types were looked up
342 for the same domain, because the text type is used as part of Exim's
343 per-process caching. But the chance of anyone hitting this buglet seems
344 very small.
346 37. The dnsdb lookup has been extended in a number of ways.
348 (1) There is a new type, "zns", which walks up the domain tree until it
349 finds some nameserver records. It should be used with care.
351 (2) There is a new type, "mxh", which is like "mx" except that it returns
352 just the host names, not the priorities.
354 (3) It is now possible to give a list of domains (or IP addresses) to be
355 looked up. The behaviour when one of the lookups defers can be
356 controlled by a keyword.
358 (4) It is now possible to specify the separator character for use when
359 multiple records are returned.
361 38. The dnslists ACL condition has been extended: it is now possible to supply
362 a list of IP addresses and/or domains to be looked up in a particular DNS
363 domain.
365 39. Added log_selector=+queue_time_overall.
367 40. When running the queue in the test harness, wait just a tad after forking a
368 delivery process, to get repeatability of debugging output.
370 41. Include certificate and key file names in error message when GnuTLS fails
371 to set them up, because the GnuTLS error message doesn't include the name
372 of the failing file when there is a problem reading it.
374 42. Allow both -bf and -bF in the same test run.
376 43. Did the same fix as 41 above for OpenSSL, which had the same infelicity.
378 44. The "Exiscan patch" is now merged into the mainline Exim source.
380 45. Sometimes the final signoff response after QUIT could fail to get
381 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
382 < 0 before doing a fflush(). This bug looks as though it goes back to the
383 introduction of TLS in release 3.20, but "sometimes" must have been rare
384 because the tests only now provoked it.
386 46. Reset the locale to "C" after calling embedded Perl, in case it was changed
387 (this can affect the format of dates).
389 47. exim_tidydb, when checking for the continued existence of a message for
390 which it has found a message-specific retry record, was not finding
391 messages that were in split spool directories. Consequently, it was
392 deleting retry records that should have stayed in existence.
394 48. Steve fixed some bugs in eximstats.
396 49. The SPA authentication driver was not abandoning authentication and moving
397 on to the next authenticator when an expansion was forced to fail,
398 contradicting the general specification for all authenticators. Instead it
399 was generating a temporary error. It now behaves as specified.
401 50. The default ordering of permitted cipher suites for GnuTLS was pessimal
402 (the order specifies the preference for clients). The order is now AES256,
403 AES128, 3DES, ARCFOUR128.
405 51. Small patch to Sieve code - explicitly set From: when generating an
406 autoreply.
408 52. Exim crashed if a remote delivery caused a very long error message to be
409 recorded - for instance if somebody sent an entire SpamAssassin report back
410 as a large number of 550 error lines. This bug was coincidentally fixed by
411 increasing the size of one of Exim's internal buffers (big_buffer) that
412 happened as part of the Exiscan merge. However, to be on the safe side, I
413 have made the code more robust (and fixed the comments that describe what
414 is going on).
416 53. Now that there can be additional text after "Completed" in log lines (if
417 the queue_time_overall log selector is set), a one-byte patch to exigrep
418 was needed to allow it to recognize "Completed" as not the last thing in
419 the line.
421 54. The LDAP lookup was not handling a return of LDAP_RES_SEARCH_REFERENCE. A
422 patch that reportedly fixes this has been added. I am not expert enough to
423 create a test for it. This is what the patch creator wrote:
425 "I found a little strange behaviour of ldap code when working with
426 Windows 2003 AD Domain, where users was placed in more than one
427 Organization Units. When I tried to give exim partial DN, the exit code
428 of ldap_search was unknown to exim because of LDAP_RES_SEARCH_REFERENCE.
429 But simultaneously result of request was absolutely normal ldap result,
430 so I produce this patch..."
432 Later: it seems that not all versions of LDAP support LDAP_RES_SEARCH_
433 REFERENCE, so I have modified the code to exclude the patch when that macro
434 is not defined.
436 55. Some experimental protocols are using DNS PTR records for new purposes. The
437 keys for these records are domain names, not reversed IP addresses. The
438 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
439 leaves it alone. Component reversal etc. now happens only for IP addresses.
440 CAN-2005-0021
442 56. Improve error message when ldap_search() fails in OpenLDAP or Solaris LDAP.
444 57. Double the size of the debug message buffer (to 2048) so that more of very
445 long debug lines gets shown.
447 58. The exicyclog utility now does better if the number of log files to keep
448 exceeds 99. In this case, it numbers them 001, 002 ... instead of 01, 02...
450 59. Two changes related to the smtp_active_hostname option:
452 (1) $smtp_active_hostname is now available as a variable.
453 (2) The default for smtp_banner uses $smtp_active_hostname instead
454 of $primary_hostname.
456 60. The host_aton() function is supposed to be passed a string that is known
457 to be a valid IP address. However, in the case of IPv6 addresses, it was
458 not checking this. This is a hostage to fortune. Exim now panics and dies
459 if the condition is not met. A case was found where this could be provoked
460 from a dnsdb PTR lookup with an IPv6 address that had more than 8
461 components; fortuitously, this particular loophole had already been fixed
462 by change 4.50/55 above.
464 If there are any other similar loopholes, the new check in host_aton()
465 itself should stop them being exploited. The report I received stated that
466 data on the command line could provoke the exploit when Exim was running as
467 exim, but did not say which command line option was involved. All I could
468 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
469 running as the user.
470 CAN-2005-0021
472 61. There was a buffer overflow vulnerability in the SPA authentication code
473 (which came originally from the Samba project). I have added a test to the
474 spa_base64_to_bits() function which I hope fixes it.
475 CAN-2005-0022
477 62. Configuration update for GNU/Hurd and variations. Updated Makefile-GNU and
478 os.h-GNU, and added configuration files for GNUkFreeBSD and GNUkNetBSD.
480 63. The daemon start-up calls getloadavg() while still root for those OS that
481 need the first call to be done as root, but it missed one case: when
482 deliver_queue_load_max is set with deliver_drop_privilege. This is
483 necessary for the benefit of the queue runner, because there is no re-exec
484 when deliver_drop_privilege is set.
486 64. A call to exiwhat cut short delays set up by "delay" modifiers in ACLs.
487 This has been fixed.
489 65. Caching of lookup data for "hosts =" ACL conditions, when a named host list
490 was in use, was not putting the data itself into the right store pool;
491 consequently, it could be overwritten for a subsequent message in the same
492 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
493 the caching.)
495 66. Added hosts_max_try_hardlimit to the smtp transport, default 50.
497 67. The string_is_ip_address() function returns 0, 4, or 6, for "no an IP
498 address", "IPv4 address", and "IPv6 address", respectively. Some calls of
499 the function were treating the return as a boolean value, which happened to
500 work because 0=false and not-0=true, but is not correct code.
502 68. The host_aton() function was not handling scoped IPv6 addresses (those
503 with, for example, "%eth0" on the end) correctly.
505 69. Fixed some compiler warnings in acl.c for the bitmaps specified with
506 negated items (that is, ~something) in unsigned ints. Some compilers
507 apparently mutter when there is no cast.
509 70. If an address verification called from an ACL failed, and did not produce a
510 user-specific message (i.e. there was only a "system" message), nothing was
511 put in $acl_verify_message. In this situation, it now puts the system
512 message there.
514 71. Change 4.23/11 added synchronization checking at the start of an SMTP
515 session; change 4.31/43 added the unwanted input to the log line - except
516 that it did not do this in the start of session case. It now does.
518 72. After a timeout in a callout SMTP session, Exim still sent a QUIT command.
519 This is wrong and can cause the other end to generate a synchronization
520 error if it is another Exim or anything else that does the synchronization
521 check. A QUIT command is no longer sent after a timeout.
523 73. $host_lookup_deferred has been added, to make it easier to detect DEFERs
524 during host lookups.
526 74. The defer_ok option of callout verification was not working if it was used
527 when verifying addresses in header lines, that is, for this case:
529 verify = header_sender/callout=defer_ok
531 75. A backgrounded daemon closed stdin/stdout/stderr on entry; this meant that
532 those file descriptors could be used for SMTP connections. If anything
533 wrote to stderr (the example that came up was "warn" in embedded Perl), it
534 could be sent to the SMTP client, causing chaos. The daemon now opens
535 stdin, stdout, and stderr to /dev/null when it puts itself into the
536 background.
538 76. Arrange for output from Perl's "warn" command to be written to Exim's main
539 log by default. The user can override this with suitable Perl magic.
541 77. The use of log_message on a "discard" ACL verb, which is supposed to add to
542 the log message when discard triggers, was not working for the DATA ACL or
543 for the non-SMTP ACL.
545 78. Error message wording change in sieve.c.
547 79. If smtp_accept_max_per_host was set, the number of connections could be
548 restricted to fewer than expected, because the daemon was trying to set up
549 a new connection before checking whether the processes handling previous
550 connections had finished. The check for completed processes is now done
551 earlier. On busy systems, this bug wouldn't be noticed because something
552 else would have woken the daemon, and it would have reaped the completed
553 process earlier.
555 80. If a message was submitted locally by a user whose login name contained one
556 or more spaces (ugh!), the spool file that Exim wrote was not re-readable.
557 It caused a spool format error. I have fixed the spool reading code. A
558 related problem was that the "from" clause in the Received: line became
559 illegal because of the space(s). It is now covered by ${quote_local_part.
561 81. Included the latest eximstats from Steve (adds average sizes to HTML Top
562 tables).
564 82. Updated OS/Makefile-AIX as per message from Mike Meredith.
566 83. Patch from Sieve maintainer to fix unterminated string problem in
567 "vacation" handling.
569 84. Some minor changes to the Linux configuration files to help with other
570 OS variants using glibc.
572 85. One more patch for Sieve to update vacation handling to latest spec.
575 ----------------------------------------------------
576 See the note above about the 4.44 and 4.50 releases.
577 ----------------------------------------------------
580 Exim version 4.44
581 -----------------
583 1. Change 4.43/35 introduced a bug that caused file counts to be
584 incorrectly computed when quota_filecount was set in an appendfile
585 transport
587 2. Closing a stable door: arrange to panic-die if setitimer() ever fails. The
588 bug fixed in 4.43/37 would have been diagnosed quickly if this had been in
589 place.
591 3. Give more explanation in the error message when the command for a transport
592 filter fails to execute.
594 4. There are several places where Exim runs a non-Exim command in a
595 subprocess. The SIGUSR1 signal should be disabled for these processes. This
596 was being done only for the command run by the queryprogram router. It is
597 now done for all such subprocesses. The other cases are: ${run, transport
598 filters, and the commands run by the lmtp and pipe transports.
600 5. Some older OS have a limit of 256 on the maximum number of file
601 descriptors. Exim was using setrlimit() to set 1000 as a large value
602 unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these
603 systems. I've change it so that if it can't get 1000, it tries for 256.
605 6. "control=submission" was allowed, but had no effect, in a DATA ACL. This
606 was an oversight, and furthermore, ever since the addition of extra
607 controls (e.g. 4.43/32), the checks on when to allow different forms of
608 "control" were broken. There should now be diagnostics for all cases when a
609 control that does not make sense is encountered.
611 7. $recipients is now available in the predata ACL (oversight).
613 8. Tidy the search cache before the fork to do a delivery from a message
614 received from the command line. Otherwise the child will trigger a lookup
615 failure and thereby defer the delivery if it tries to use (for example) a
616 cached ldap connection that the parent has called unbind on.
618 9. If verify=recipient was followed by verify=sender in a RCPT ACL, the value
619 of $address_data from the recipient verification was clobbered by the
620 sender verification.
622 10. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0
623 was its contents. (It was OK if the option was not defined at all.)
625 11. A "Completed" log line is now written for messages that are removed from
626 the spool by the -Mrm option.
628 12. $host_address is now set to the target address during the checking of
629 ignore_target_hosts.
631 13. When checking ignore_target_hosts for an ipliteral router, no host name was
632 being passed; this would have caused $sender_host_name to have been used if
633 matching the list had actually called for a host name (not very likely,
634 since this list is usually IP addresses). A host name is now passed as
635 "[x.x.x.x]".
637 14. Changed the calls that set up the SIGCHLD handler in the daemon to use the
638 code that specifies a non-restarting handler (typically sigaction() in
639 modern systems) in an attempt to fix a rare and obscure crash bug.
641 15. Narrowed the window for a race in the daemon that could cause it to ignore
642 SIGCHLD signals. This is not a major problem, because they are used only to
643 wake it up if nothing else does.
645 16. A malformed maildirsize file could cause Exim to calculate negative values
646 for the mailbox size or file count. Odd effects could occur as a result.
647 The maildirsize information is now recalculated if the size or filecount
648 end up negative.
650 17. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this
651 support for a long time. Removed HAVE_SYS_VFS_H.
653 18. Updated exipick to current release from John Jetmore.
655 19. Allow an empty sender to be matched against a lookup in an address list.
656 Previously the only cases considered were a regular expression, or an
657 empty pattern.
659 20. Exim went into a mad DNS lookup loop when doing a callout where the
660 host was specified on the transport, if the DNS lookup yielded more than
661 one IP address.
663 21. The RFC2047 encoding function was originally intended for short strings
664 such as real names; it was not keeping to the 75-character limit for
665 encoded words that the RFC imposes. It now respects the limit, and
666 generates multiple encoded words if necessary. To be on the safe side, I
667 have increased the buffer size for the ${rfc2047: expansion operator from
668 1024 to 2048 bytes.
670 22. Failure to deliver a bounce message always caused it to be frozen, even if
671 there was an errors_to setting on the router. The errors_to setting is now
672 respected.
674 23. If an IPv6 address is given for -bh or -bhc, it is now converted to the
675 canonical form (fully expanded) before being placed in
676 $sender_host_address.
678 24. Updated eximstats to version 1.33
680 25. Include certificate and key file names in error message when GnuTLS fails
681 to set them up, because the GnuTLS error message doesn't include the name
682 of the failing file when there is a problem reading it.
684 26. Expand error message when OpenSSL has problems setting up cert/key files.
685 As per change 25.
687 27. Reset the locale to "C" after calling embedded Perl, in case it was changed
688 (this can affect the format of dates).
690 28. exim_tidydb, when checking for the continued existence of a message for
691 which it has found a message-specific retry record, was not finding
692 messages that were in split spool directories. Consequently, it was
693 deleting retry records that should have stayed in existence.
695 29. eximstats updated to version 1.35
696 1.34 - allow eximstats to parse syslog lines as well as mainlog lines
697 1.35 - bugfix such that pie charts by volume are generated correctly
699 30. The SPA authentication driver was not abandoning authentication and moving
700 on to the next authenticator when an expansion was forced to fail,
701 contradicting the general specification for all authenticators. Instead it
702 was generating a temporary error. It now behaves as specified.
704 31. The default ordering of permitted cipher suites for GnuTLS was pessimal
705 (the order specifies the preference for clients). The order is now AES256,
706 AES128, 3DES, ARCFOUR128.
708 31. Small patch to Sieve code - explicitly set From: when generating an
709 autoreply.
711 32. Exim crashed if a remote delivery caused a very long error message to be
712 recorded - for instance if somebody sent an entire SpamAssassin report back
713 as a large number of 550 error lines. This bug was coincidentally fixed by
714 increasing the size of one of Exim's internal buffers (big_buffer) that
715 happened as part of the Exiscan merge. However, to be on the safe side, I
716 have made the code more robust (and fixed the comments that describe what
717 is going on).
719 33. Some experimental protocols are using DNS PTR records for new purposes. The
720 keys for these records are domain names, not reversed IP addresses. The
721 dnsdb PTR lookup now tests whether its key is an IP address. If not, it
722 leaves it alone. Component reversal etc. now happens only for IP addresses.
723 CAN-2005-0021
725 34. The host_aton() function is supposed to be passed a string that is known
726 to be a valid IP address. However, in the case of IPv6 addresses, it was
727 not checking this. This is a hostage to fortune. Exim now panics and dies
728 if the condition is not met. A case was found where this could be provoked
729 from a dnsdb PTR lookup with an IPv6 address that had more than 8
730 components; fortuitously, this particular loophole had already been fixed
731 by change 4.50/55 or 4.44/33 above.
733 If there are any other similar loopholes, the new check in host_aton()
734 itself should stop them being exploited. The report I received stated that
735 data on the command line could provoke the exploit when Exim was running as
736 exim, but did not say which command line option was involved. All I could
737 find was the use of -be with a bad dnsdb PTR lookup, and in that case it is
738 running as the user.
739 CAN-2005-0021
741 35. There was a buffer overflow vulnerability in the SPA authentication code
742 (which came originally from the Samba project). I have added a test to the
743 spa_base64_to_bits() function which I hope fixes it.
744 CAN-2005-0022
746 36. The daemon start-up calls getloadavg() while still root for those OS that
747 need the first call to be done as root, but it missed one case: when
748 deliver_queue_load_max is set with deliver_drop_privilege. This is
749 necessary for the benefit of the queue runner, because there is no re-exec
750 when deliver_drop_privilege is set.
752 37. Caching of lookup data for "hosts =" ACL conditions, when a named host list
753 was in use, was not putting the data itself into the right store pool;
754 consequently, it could be overwritten for a subsequent message in the same
755 SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked
756 the caching.)
758 38. Sometimes the final signoff response after QUIT could fail to get
759 transmitted in the non-TLS case. Testing !tls_active instead of tls_active
760 < 0 before doing a fflush(). This bug looks as though it goes back to the
761 introduction of TLS in release 3.20, but "sometimes" must have been rare
762 because the tests only now provoked it.
765 Exim version 4.43
766 -----------------
768 1. Fixed a longstanding but relatively impotent bug: a long time ago, before
769 PIPELINING, the function smtp_write_command() used to return TRUE or FALSE.
770 Now it returns an integer. A number of calls were still expecting a T/F
771 return. Fortuitously, in all cases, the tests worked in OK situations,
772 which is the norm. However, things would have gone wrong on any write
773 failures on the smtp file descriptor. This function is used when sending
774 messages over SMTP and also when doing verify callouts.
776 2. When Exim is called to do synchronous delivery of a locally submitted
777 message (the -odf or -odi options), it no longer closes stderr before doing
778 the delivery.
780 3. Implemented the mua_wrapper option.
782 4. Implemented mx_fail_domains and srv_fail_domains for the dnslookup router.
784 5. Implemented the functions header_remove(), header_testname(),
785 header_add_at_position(), and receive_remove_recipient(), and exported them
786 to local_scan().
788 6. If an ACL "warn" statement specified the addition of headers, Exim already
789 inserted X-ACL-Warn: at the start if there was no header name. However, it
790 was not making this test for the second and subsequent header lines if
791 there were newlines in the string. This meant that an invalid header could
792 be inserted if Exim was badly configured.
794 7. Allow an ACL "warn" statement to add header lines at the start or after all
795 the Received: headers, as well as at the end.
797 8. Added the rcpt_4xx retry error code.
799 9. Added postmaster_mailfrom=xxx to callout verification option.
801 10. Added mailfrom=xxxx to the callout verification option, for verify=
802 header_sender only.
804 11. ${substr_1_:xxxx} and ${substr__3:xxxx} are now diagnosed as syntax errors
805 (they previously behaved as ${substr_1_0:xxxx} and ${substr:_0_3:xxxx}).
807 12. Inserted some casts to stop certain compilers warning when using pointer
808 differences as field lengths or precisions in printf-type calls (mostly
809 affecting debugging statements).
811 13. Added optional readline() support for -be (dynamically loaded).
813 14. Obscure bug fix: if a message error (e.g. 4xx to MAIL) happened within the
814 same clock tick as a message's arrival, so that its received time was the
815 same as the "first fail" time on the retry record, and that message
816 remained on the queue past the ultimate address timeout, every queue runner
817 would try a delivery (because it was past the ultimate address timeout) but
818 after another failure, the ultimate address timeout, which should have then
819 bounced the address, did not kick in. This was a "< instead of <=" error;
820 in most cases the first failure would have been in the next clock tick
821 after the received time, and all would be well.
823 15. The special items beginning with @ in domain lists (e.g. @mx_any) were not
824 being recognized when the domain list was tested by the match_domain
825 condition in an expansion string.
827 16. Added the ${str2b64: operator.
829 17. Exim was always calling setrlimit() to set a large limit for the number of
830 processes, without checking whether the existing limit was already
831 adequate. (It did check for the limit on file descriptors.) Furthermore,
832 errors from getrlimit() and setrlimit() were being ignored. Now they are
833 logged to the main and panic logs, but Exim does carry on, to try to do its
834 job under whatever limits there are.
836 18. Imported PCRE 5.0.
838 19. Trivial typo in log message " temporarily refused connection" (the leading
839 space).
841 20. If the log selector return_path_on_delivery was set and an address was
842 redirected to /dev/null, the delivery process crashed because it assumed
843 that a return path would always be set for a "successful" delivery. In this
844 case, the whole delivery is bypassed as an optimization, and therefore no
845 return path is set.
847 21. Internal re-arrangement: the function for sending a challenge and reading
848 a response while authentication was assuming a zero-terminated challenge
849 string. It's now changed to take a pointer and a length, to allow for
850 binary data in such strings.
852 22. Added the cyrus_sasl authenticator (code supplied by MBM).
854 23. Exim was not respecting finduser_retries when seeking the login of the
855 uid under which it was called; it was always trying 10 times. (The default
856 setting of finduser_retries is zero.) Also, it was sleeping after the final
857 failure, which is pointless.
859 24. Implemented tls_on_connect_ports.
861 25. Implemented acl_smtp_predata.
863 26. If the domain in control=submission is set empty, Exim assumes that the
864 authenticated id is a complete email address when it generates From: or
865 Sender: header lines.
867 27. Added "#define SOCKLEN_T int" to OS/os.h-SCO and OS/os.h-SCO_SV. Also added
868 definitions to OS/Makefile-SCO and OS/Makefile-SCO_SV that put basename,
869 chown and chgrp in /bin and hostname in /usr/bin.
871 28. Exim was keeping the "process log" file open after each use, just as it
872 does for the main log. This opens the possibility of it remaining open for
873 long periods when the USR1 signal hits a daemon. Occasional processlog
874 errors were reported, that could have been caused by this. Anyway, it seems
875 much more sensible not to leave this file open at all, so that is what now
876 happens.
878 29. The long-running daemon process does not normally write to the log once it
879 has entered its main loop, and it closes the log before doing so. This is
880 so that log files can straightforwardly be renamed and moved. However,
881 there are a couple of unusual error situations where the daemon does write
882 log entries, and I had neglected to close the log afterwards.
884 30. The text of an SMTP error response that was received during a remote
885 delivery was being truncated at 512 bytes. This is too short for some of
886 the long messages that one sometimes sees. I've increased the limit to
887 1024.
889 31. It is now possible to make retry rules that apply only when a message has a
890 specific sender, in particular, an empty sender.
892 32. Added "control = enforce_sync" and "control = no_enforce_sync". This makes
893 it possible to be selective about when SMTP synchronization is enforced.
895 33. Added "control = caseful_local_part" and "control = "caselower_local_part".
897 32. Implemented hosts_connection_nolog.
899 33. Added an ACL for QUIT.
901 34. Setting "delay_warning=" to disable warnings was not working; it gave a
902 syntax error.
904 35. Added mailbox_size and mailbox_filecount to appendfile.
906 36. Added control = no_multiline_responses to ACLs.
908 37. There was a bug in the logic of the code that waits for the clock to tick
909 in the case where the clock went backwards by a substantial amount such
910 that the microsecond fraction of "now" was more than the microsecond
911 fraction of "then" (but the whole seconds number was less).
913 38. Added support for the libradius Radius client library this is found on
914 FreeBSD (previously only the radiusclient library was supported).
917 Exim version 4.42
918 -----------------
920 1. When certain lookups returned multiple values in the form name=value, the
921 quoting of the values was not always being done properly. Specifically:
922 (a) If the value started with a double quote, but contained no whitespace,
923 it was not quoted.
924 (b) If the value contained whitespace other than a space character (i.e.
925 tabs or newlines or carriage returns) it was not quoted.
926 This fix has been applied to the mysql and pgsql lookups by writing a
927 separate quoting function and calling it from the lookup code. The fix
928 should probably also be applied to nisplus, ibase and oracle lookups, but
929 since I cannot test any of those, I have not disturbed their existing code.
931 2. A hit in the callout cache for a specific address caused a log line with no
932 reason for rejecting RCPT. Now it says "Previous (cached) callout
933 verification failure".
935 3. There was an off-by-one bug in the queryprogram router. An over-long
936 return line was truncated at 256 instead of 255 characters, thereby
937 overflowing its buffer with the terminating zero. As well as fixing this, I
938 have increased the buffer size to 1024 (and made a note to document this).
940 4. If an interrupt, such as the USR1 signal that is send by exiwhat, arrives
941 when Exim is waiting for an SMTP response from a remote server, Exim
942 restarts its select() call on the socket, thereby resetting its timeout.
943 This is not a problem when such interrupts are rare. Somebody set up a cron
944 job to run exiwhat every 2 minutes, which is less than the normal select()
945 timeout (5 or 10 minutes). This meant that the select() timeout never
946 kicked in because it was always reset. I have fixed this by comparing the
947 time when an interrupt arrives with the time at the start of the first call
948 to select(). If more time than the timeout has elapsed, the interrupt is
949 treated as a timeout.
951 5. Some internal re-factoring in preparation for the addition of Sieve
952 extensions (by MH). In particular, the "personal" test is moved to a
953 separate function, and given an option for scanning Cc: and Bcc: (which is
954 not set for Exim filters).
956 6. When Exim created an email address using the login of the caller as the
957 local part (e.g. when creating a From: or Sender: header line), it was not
958 quoting the local part when it contained special characters such as @.
960 7. Installed new OpenBSD configuration files.
962 8. Reworded some messages for syntax errors in "and" and "or" conditions to
963 try to make them clearer.
965 9. Callout options, other than the timeout value, were being ignored when
966 verifying sender addresses in header lines. For example, when using
968 verify = header_sender/callout=no_cache
970 the cache was (incorrectly) being used.
972 10. Added a missing instance of ${EXE} to the exim_install script; this affects
973 only the Cygwin environment.
975 11. When return_path_on_delivery was set as a log selector, if different remote
976 addresses in the same message used different return paths and parallel
977 remote delivery occurred, the wrong values would sometimes be logged.
978 (Whenever a remote delivery process finished, the return path value from
979 the most recently started remote delivery process was logged.)
981 12. RFC 3848 specifies standard names for the "with" phrase in Received: header
982 lines when AUTH and/or TLS are in use. This is the "received protocol"
983 field. Exim used to use "asmtp" for authenticated SMTP, without any
984 indication (in the protocol name) for TLS use. Now it follows the RFC and
985 uses "esmtpa" if the connection is authenticated, "esmtps" if it is
986 encrypted, and "esmtpsa" if it is both encrypted and authenticated. These
987 names appear in log lines as well as in Received: header lines.
989 13. Installed MH's patches for Sieve to add the "copy" and "vacation"
990 extensions, and comparison tests, and to fix some bugs.
992 14. Changes to the "personal" filter test:
994 (1) The test was buggy in that it was just doing the equivalent of
995 "contains" tests on header lines. For example, if a user's address was
996 anne@some.where, the "personal" test would incorrectly be true for
998 To: susanne@some.where
1000 This test is now done by extracting each address from the header in turn,
1001 and checking the entire address. Other tests that are part of "personal"
1002 are now done using regular expressions (for example, to check local parts
1003 of addresses in From: header lines).
1005 (2) The list of non-personal local parts in From: addresses has been
1006 extended to include "listserv", "majordomo", "*-request", and "owner-*",
1007 taken from the Sieve specification recommendations.
1009 (3) If the message contains any header line starting with "List-" it is
1010 treated as non-personal.
1012 (4) The test for "circular" in the Subject: header line has been removed
1013 because it now seems ill-conceived.
1015 15. Minor typos in src/EDITME comments corrected.
1017 16. Installed latest exipick from John Jetmore.
1019 17. If headers_add on a router specified a text string that was too long for
1020 string_sprintf() - that is, longer than 8192 bytes - Exim panicked. The use
1021 of string_sprintf() is now avoided.
1023 18. $message_body_size was not set (it was always zero) when running the DATA
1024 ACL and the local_scan() function.
1026 19. For the "mail" command in an Exim filter, no default was being set for
1027 the once_repeat time, causing a random time value to be used if "once" was
1028 specified. (If the value happened to be <= 0, no repeat happened.) The
1029 default is now 0s, meaning "never repeat". The "vacation" command was OK
1030 (its default is 7d). It's somewhat surprising nobody ever noticed this bug
1031 (I found it when inspecting the code).
1033 20. There is now an overall timeout for performing a callout verification. It
1034 defaults to 4 times the callout timeout, which applies to individual SMTP
1035 commands during the callout. The overall timeout applies when there is more
1036 than one host that can be tried. The timeout is checked before trying the
1037 next host. This prevents very long delays if there are a large number of
1038 hosts and all are timing out (e.g. when the network connections are timing
1039 out). The value of the overall timeout can be changed by specifying an
1040 additional sub-option for "callout", called "maxwait". For example:
1042 verify = sender/callout=5s,maxwait=20s
1044 21. Add O_APPEND to the open() call for maildirsize files (Exim already seeks
1045 to the end before writing, but this should make it even safer).
1047 22. Exim was forgetting that it had advertised PIPELINING for the second and
1048 subsequent messages on an SMTP connection. It was also not resetting its
1049 memory on STARTTLS and an internal HELO.
1051 23. When Exim logs an SMTP synchronization error within a session, it now
1052 records whether PIPELINING has been advertised or not.
1054 24. Added 3 instances of "(long int)" casts to time_t variables that were being
1055 formatted using %ld, because on OpenBSD (and perhaps others), time_t is int
1056 rather than long int.
1058 25. Installed the latest Cygwin configuration files from the Cygwin maintainer.
1060 26. Added the never_mail option to autoreply.
1063 Exim version 4.41
1064 -----------------
1066 1. A reorganization of the code in order to implement 4.40/8 caused a daemon
1067 crash if the getsockname() call failed; this can happen if a connection is
1068 closed very soon after it is established. The problem was simply in the
1069 order in which certain operations were done, causing Exim to try to write
1070 to the SMTP stream before it had set up the file descriptor. The bug has
1071 been fixed by making things happen in the correct order.
1074 Exim version 4.40
1075 -----------------
1077 1. If "drop" was used in a DATA ACL, the SMTP output buffer was not flushed
1078 before the connection was closed, thus losing the rejection response.
1080 2. Commented out the definition of SOCKLEN_T in os.h-SunOS5. It is needed for
1081 some early Solaris releases, but causes trouble in current releases where
1082 socklen_t is defined.
1084 3. When std{in,out,err} are closed, re-open them to /dev/null so that they
1085 always exist.
1087 4. Minor refactoring of os.c-Linux to avoid compiler warning when IPv6 is not
1088 configured.
1090 5. Refactoring in expand.c to improve memory usage. Pre-allocate a block so
1091 that releasing the top of it at the end releases what was used for sub-
1092 expansions (unless the block got too big). However, discard this block if
1093 the first thing is a variable or header, so that we can use its block when
1094 it is dynamic (useful for very large $message_headers, for example).
1096 6. Lookups now cache *every* query, not just the most recent. A new, separate
1097 store pool is used for this. It can be recovered when all lookup caches are
1098 flushed. Lookups now release memory at the end of their result strings.
1099 This has involved some general refactoring of the lookup sources.
1101 7. Some code has been added to the store_xxx() functions to reduce the amount
1102 of flapping under certain conditions.
1104 8. log_incoming_interface used to affect only the <= reception log lines. Now
1105 it causes the local interface and port to be added to several more SMTP log
1106 lines, for example "SMTP connection from", and rejection lines.
1108 9. The Sieve author supplied some patches for the doc/README.SIEVE file.
1110 10. Added a conditional definition of _BSD_SOCKLEN_T to os.h-Darwin.
1112 11. If $host_data was set by virtue of a hosts lookup in an ACL, its value
1113 could be overwritten at the end of the current message (or the start of a
1114 new message if it was set in a HELO ACL). The value is now preserved for
1115 the duration of the SMTP connection.
1117 12. If a transport had a headers_rewrite setting, and a matching header line
1118 contained an unqualified address, that address was qualified, even if it
1119 did not match any rewriting rules. The underlying bug was that the values
1120 of the flags that permit the existence of unqualified sender and recipient
1121 addresses in header lines (set by {sender,recipient}_unqualified_hosts for
1122 non-local messages, and by -bnq for local messages) were not being
1123 preserved with the message after it was received.
1125 13. When Exim was logging an SMTP synchronization error, it could sometimes log
1126 "next input=" as part of the text comprising the host identity instead of
1127 the correct text. The code was using the same buffer for two different
1128 strings. However, depending on which order the printing function evaluated
1129 its arguments, the bug did not always show up. Under Linux, for example, my
1130 test suite worked just fine.
1132 14. Exigrep contained a use of Perl's "our" scoping after change 4.31/70. This
1133 doesn't work with some older versions of Perl. It has been changed to "my",
1134 which in any case is probably the better facility to use.
1136 15. A really picky compiler found some instances of statements for creating
1137 error messages that either had too many or two few arguments for the format
1138 string.
1140 16. The size of the buffer for calls to the DNS resolver has been increased
1141 from 1024 to 2048. A larger buffer is needed when performing PTR lookups
1142 for addresses that have a lot of PTR records. This alleviates a problem; it
1143 does not fully solve it.
1145 17. A dnsdb lookup for PTR records that receives more data than will fit in the
1146 buffer now truncates the list and logs the incident, which is the same
1147 action as happens when Exim is looking up a host name and its aliases.
1148 Previously in this situation something unpredictable would happen;
1149 sometimes it was "internal error: store_reset failed".
1151 18. If a server dropped the connection unexpectedly when an Exim client was
1152 using GnuTLS and trying to read a response, the client delivery process
1153 crashed while trying to generate an error log message.
1155 19. If a "warn" verb in an ACL added multiple headers to a message in a single
1156 string, for example:
1158 warn message = H1: something\nH2: something
1160 the text was added as a single header line from Exim's point of view
1161 though it ended up OK in the delivered message. However, searching for the
1162 second and subsequent header lines using $h_h2: did not work. This has been
1163 fixed. Similarly, if a system filter added multiple headers in this way,
1164 the routers could not see them.
1166 20. Expanded the error message when iplsearch is called with an invalid key to
1167 suggest using net-iplsearch in a host list.
1169 21. When running tests using -bh, any delays imposed by "delay" modifiers in
1170 ACLs are no longer actually imposed (and a message to that effect is
1171 output).
1173 22. If a "gecos" field in a passwd entry contained escaped characters, in
1174 particular, if it contained a \" sequence, Exim got it wrong when building
1175 a From: or a Sender: header from that name. A second bug also caused
1176 incorrect handling when an unquoted " was present following a character
1177 that needed quoting.
1179 23. "{crypt}" as a password encryption mechanism for a "crypteq" expansion item
1180 was not being matched caselessly.
1182 24. Arranged for all hyphens in the exim.8 source to be escaped with
1183 backslashes.
1185 25. Change 16 of 4.32, which reversed 71 or 4.31 didn't quite do the job
1186 properly. Recipient callout cache records were still being keyed to include
1187 the sender, even when use_sender was set false. This led to far more
1188 callouts that were necessary. The sender is no longer included in the key
1189 when use_sender is false.
1191 26. Added "control = submission" modifier to ACLs.
1193 27. Added the ${base62d: operator to decode base 62 numbers.
1195 28. dnsdb lookups can now access SRV records.
1197 29. CONFIGURE_OWNER can be set at build time to define an alternative owner for
1198 the configuration file.
1200 30. The debug message "delivering xxxxxx-xxxxxx-xx" is now output in verbose
1201 (-v) mode. This makes the output for a verbose queue run more intelligible.
1203 31. Added a use_postmaster feature to recipient callouts.
1205 32. Added the $body_zerocount variable, containing the number of binary zero
1206 bytes in the message body.
1208 33. The time of last modification of the "new" subdirectory is now used as the
1209 "mailbox time last read" when there is a quota error for a maildir
1210 delivery.
1212 34. Added string comparison operators lt, lti, le, lei, gt, gti, ge, gei.
1214 35. Added +ignore_unknown as a special item in host lists.
1216 36. Code for decoding IPv6 addresses in host lists is now included, even if
1217 IPv6 support is not being compiled. This fixes a bug in which an IPv6
1218 address was recognized as an IP address, but was then not correctly decoded
1219 into binary, causing unexpected and incorrect effects when compared with
1220 another IP address.
1223 Exim version 4.34
1224 -----------------
1226 1. Very minor rewording of debugging text in manualroute to say "list of
1227 hosts" instead of "hostlist".
1229 2. If verify=header_syntax was set, and a header line with an unqualified
1230 address (no domain) and a large number of spaces between the end of the
1231 name and the colon was received, the reception process suffered a buffer
1232 overflow, and (when I tested it) crashed. This was caused by some obsolete
1233 code that should have been removed. The fix is to remove it!
1235 3. When running in the test harness, delay a bit after writing a bounce
1236 message to get a bit more predictability in the log output.
1238 4. Added a call to search_tidyup() just before forking a reception process. In
1239 theory, someone could use a lookup in the expansion of smtp_accept_max_
1240 per_host which, without the tidyup, could leave open a database connection.
1242 5. Added the variables $recipient_data and $sender_data which get set from a
1243 lookup success in an ACL "recipients" or "senders" condition, or a router
1244 "senders" option, similar to $domain_data and $local_part_data.
1246 6. Moved the writing of debug_print from before to after the "senders" test
1247 for routers.
1249 7. Change 4.31/66 (moving the time when the Received: is generated) caused
1250 problems for message scanning, either using a data ACL, or using
1251 local_scan() because the Received: header was not generated till after they
1252 were called (in order to set the time as the time of reception completion).
1253 I have revised the way this works. The header is now generated after the
1254 body is received, but before the ACL or local_scan() are called. After they
1255 are run, the timestamp in the header is updated.
1258 Exim version 4.33
1259 -----------------
1261 1. Change 4.24/6 introduced a bug because the SIGALRM handler was disabled
1262 before starting a queue runner without re-exec. This happened only when
1263 deliver_drop_privilege was set or when the Exim user was set to root. The
1264 effect of the bug was that timeouts during subsequent deliveries caused
1265 crashes instead of being properly handled. The handler is now left at its
1266 default (and expected) setting.
1268 2. The other case in which a daemon avoids a re-exec is to deliver an incoming
1269 message, again when deliver_drop_privilege is set or Exim is run as root.
1270 The bug described in (1) was not present in this case, but the tidying up
1271 of the other signals was missing. I have made the two cases consistent.
1273 3. The ignore_target_hosts setting on a manualroute router was being ignored
1274 for hosts that were looked up using the /MX notation.
1276 4. Added /ignore=<ip list> feature to @mx_any, @mx_primary, and @mx_secondary
1277 in domain lists.
1279 5. Change 4.31/55 was buggy, and broke when there was a rewriting rule that
1280 operated on the sender address. After changing the $sender_address to <>
1281 for the sender address verify, Exim was re-instated it as the original
1282 (before rewriting) address, but remembering that it had rewritten it, so it
1283 wasn't rewriting it again. This bug also had the effect of breaking the
1284 sender address verification caching when the sender address was rewritten.
1286 6. The ignore_target_hosts option was being ignored by the ipliteral router.
1287 This has been changed so that if the ip literal address matches
1288 ignore_target_hosts, the router declines.
1290 7. Added expansion conditions match_domain, match_address, and match_local_
1291 part (NOT match_host).
1293 8. The placeholder for the Received: header didn't have a length field set.
1295 9. Added code to Exim itself and to exim_lock to test for a specific race
1296 condition that could lead to file corruption when using MBX delivery. The
1297 issue is with the lockfile that is created in /tmp. If this file is removed
1298 after a process has opened it but before that process has acquired a lock,
1299 there is the potential for a second process to recreate the file and also
1300 acquire a lock. This could lead to two Exim processes writing to the file
1301 at the same time. The added code performs the same test as UW imapd; it
1302 checks after acquiring the lock that its file descriptor still refers to
1303 the same named file.
1305 10. The buffer for building added header lines was of fixed size, 8192 bytes.
1306 It is now parameterized by HEADER_ADD_BUFFER_SIZE and this can be adjusted
1307 when Exim is built.
1309 11. Added the smtp_active_hostname option. If used, this will typically be made
1310 to depend on the incoming interface address. Because $interface_address is
1311 not set up until the daemon has forked a reception process, error responses
1312 that can happen earlier (such as "too many connections") no longer contain
1313 a host name.
1315 12. If an expansion in a condition on a "warn" statement fails because a lookup
1316 defers, the "warn" statement is abandoned, and the next ACL statement is
1317 processed. Previously this caused the whole ACL to be aborted.
1319 13. Added the iplsearch lookup type.
1321 14. Added ident_timeout as a log selector.
1323 15. Added tls_certificate_verified as a log selector.
1325 16. Added a global option tls_require_ciphers (compare the smtp transport
1326 option of the same name). This controls incoming TLS connections.
1328 17. I finally figured out how to make tls_require_ciphers do a similar thing
1329 in GNUtls to what it does in OpenSSL, that is, set up an appropriate list
1330 before starting the TLS session.
1332 18. Tabs are now shown as \t in -bP output.
1334 19. If the log selector return_path_on_delivery was set, Exim crashed when
1335 bouncing a message because it had too many Received: header lines.
1337 20. If two routers both had headers_remove settings, and the first one included
1338 a superfluous trailing colon, the final name in the first list and the
1339 first name in the second list were incorrectly joined into one item (with a
1340 colon in the middle).
1343 Exim version 4.32
1344 -----------------
1346 1. Added -C and -D options to the exinext utility, mainly to make it easier
1347 to include in the automated testing, but these could be helpful when
1348 multiple configurations are in use.
1350 2. The exinext utility was not formatting the output nicely when there was
1351 an alternate port involved in the retry record key, nor when there was a
1352 message id as well (for retries that were specific to a specific message
1353 and a specific host). It was also confused by IPv6 addresses, because of
1354 the additional colons they contain. I have fixed the IPv4 problem, and
1355 patched it up to do a reasonable job for IPv6.
1357 3. When there is an error after a MAIL, RCPT, or DATA SMTP command during
1358 delivery, the log line now contains "pipelined" if PIPELINING was used.
1360 4. An SMTP transport process used to panic and die if the bind() call to set
1361 an explicit outgoing interface failed. This has been changed; it is now
1362 treated in the same way as a connect() failure.
1364 5. A reference to $sender_host_name in the part of a conditional expansion
1365 that was being skipped was still causing a DNS lookup. This no longer
1366 occurs.
1368 6. The def: expansion condition was not recognizing references to header lines
1369 that used bh_ and bheader_.
1371 7. Added the _cache feature to named lists.
1373 8. The code for checking quota_filecount in the appendfile transport was
1374 allowing one more file than it should have been.
1376 9. For compatibility with Sendmail, the command line option
1378 -prval:sval
1380 is equivalent to
1382 -oMr rval -oMs sval
1384 and sets the incoming protocol and host name (for trusted callers). The
1385 host name and its colon can be omitted when only the protocol is to be set.
1386 Note the Exim already has two private options, -pd and -ps, that refer to
1387 embedded Perl. It is therefore impossible to set a protocol value of "d" or
1388 "s", but I don't think that's a major issue.
1390 10. A number of refactoring changes to the code, none of which should affect
1391 Exim's behaviour:
1393 (a) The number of logging options was getting close to filling up the
1394 32-bit word that was used as a bit map. I have split them into two classes:
1395 those that are passed in the argument to log_write(), and those that are
1396 only ever tested independently outside of that function. These are now in
1397 separate 32-bit words, so there is plenty of room for expansion again.
1398 There is no change in the user interface or the logging behaviour.
1400 (b) When building, for example, log lines, the code previously used a
1401 macro that called string_cat() twice, in order to add two strings. This is
1402 not really sufficiently general. Furthermore, there was one instance where
1403 it was actually wrong because one of the argument was used twice, and in
1404 one call a function was used. (As it happened, calling the function twice
1405 did not affect the overall behaviour.) The macro has been replaced by a
1406 function that can join an arbitrary number of extra strings onto a growing
1407 string.
1409 (c) The code for expansion conditions now uses a table and a binary chop
1410 instead of a serial search (which was left over from when there were very
1411 few conditions). Also, it now recognizes conditions like "pam" even when
1412 the relevant support is not compiled in: a suitably worded error message is
1413 given if an attempt is made to use such a condition.
1415 11. Added ${time_interval:xxxxx}.
1417 12. A bug was causing one of the ddress fields not to be passed back correctly
1418 from remote delivery subprocesses. The field in question was not being
1419 subsequently used, so this caused to problems in practice.
1421 13. Added new log selectors queue_time and deliver_time.
1423 14. Might have fixed a bug in maildirsizefile handling that threw up
1424 "unexpected character" debug warnings, and recalculated the data
1425 unnecessarily. In any case, I expanded the warning message to give more
1426 information.
1428 15. Added the message "Restricted characters in address" to the statements in
1429 the default ACL that block characters like @ and % in local parts.
1431 16. Change 71 for release 4.31 proved to be much less benign that I imagined.
1432 Three changes have been made:
1434 (a) There was a serious bug; a negative response to MAIL caused the whole
1435 recipient domain to be cached as invalid, thereby blocking all messages
1436 to all local parts at the same domain, from all senders. This bug has
1437 been fixed. The domain is no longer cached after a negative response to
1438 MAIL if the sender used is not empty.
1440 (b) The default behaviour of using MAIL FROM:<> for recipient callouts has
1441 been restored.
1443 (c) A new callout option, "use_sender" has been added for people who want
1444 the modified behaviour.
1447 Exim version 4.31
1448 -----------------
1450 1. Removed "EXTRALIBS=-lwrap" from OS/Makefile-Unixware7 on the advice of
1451 Larry Rosenman.
1453 2. Removed "LIBS = -lresolv" from OS/Makefile-Darwin as it is not needed, and
1454 indeed breaks things for older releases.
1456 3. Added additional logging to the case where there is a problem reading data
1457 from a filter that is running in a subprocess using a pipe, in order to
1458 try to track down a specific problem.
1460 4. Testing facility fudge: when running in the test harness and attempting
1461 to connect to 10.x.x.x (expecting a connection timeout) I'm now sometimes
1462 getting "No route to host". Convert this to a timeout.
1464 5. Define ICONV_ARG2_TYPE as "char **" for Unixware7 to avoid compiler
1465 warning.
1467 6. Some OS don't have socklen_t but use size_t instead. This affects the
1468 fifth argument of getsockopt() amongst other things. This is now
1469 configurable by a macro called SOCKLEN_T which defaults to socklen_t, but
1470 can be set for individual OS. I have set it for SunOS5, OSF1, and
1471 Unixware7. Current versions of SunOS5 (aka Solaris) do have socklen_t, but
1472 some earlier ones do not.
1474 7. Change 4.30/15 was not doing the test caselessly.
1476 8. The standard form for an IPv6 address literal was being rejected by address
1477 parsing in, for example, MAIL and RCPT commands. An example of this kind of
1478 address is [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
1479 this, as well as the form without the "IPv6" on the front (but only when
1480 address literals are enabled, of course).
1482 9. Added some casts to avoid compiler warnings in OS/os.c-Linux.
1484 10. Exim crashed if a message with an empty sender address specified by -f
1485 encountered a router with an errors_to setting. This could be provoked only
1486 by a command such as
1488 exim -f "" ...
1490 where an empty string was supplied; "<>" did not hit this bug.
1492 11. Installed PCRE release 4.5.
1494 12. If EHLO/HELO was rejected by an ACL, the value of $sender_helo_name
1495 remained set. It is now erased.
1497 13. exiqgrep wasn't working on MacOS X because it didn't correctly compute
1498 times from message ids (which are base 36 rather than the normal 62).
1500 14. "Expected" SMTP protocol errors that can arise when PIPELINING is in use
1501 were being counted as actual protocol errors, and logged if the log
1502 selector +smtp_protocol_error was set. One cannot be perfect in this test,
1503 but now, if PIPELINING has been advertised, RCPT following a rejected MAIL,
1504 and DATA following a set of rejected RCPTs do not count as protocol errors.
1505 In other words, Exim assumes they were pipelined, though this may not
1506 actually be the case. Of course, in all cases the client gets an
1507 appropriate error code.
1509 15. If a lookup fails in an ACL condition, a message about the failure may
1510 be available; it is used if testing the ACL cannot continue, because most
1511 such messages specify what the cause of the deferral is. However, some
1512 messages (e.g. "MYSQL: no data found") do not cause a defer. There was bug
1513 that caused an old message to be retained and used if a later statement
1514 caused a defer, replacing the real cause of the deferral.
1516 16. If an IP address had so many PTR records that the DNS lookup buffer
1517 was not large enough to hold them, Exim could crash while trying to process
1518 the truncated data. It now detects and logs this case.
1520 17. Further to 4.21/58, another change has been made: if (and only if) the
1521 first line of a message (the first header line) ends with CRLF, a bare LF
1522 in a subsequent header line has a space inserted after it, so as not to
1523 terminate the header.
1525 18. Refactoring: tidied an ugly bit of code in appendfile that copied data
1526 unnecessarily, used atoi() instead of strtol(), and didn't check the
1527 termination when getting file sizes from file names by regex.
1529 19. Completely re-implemented the support for maildirsize files, in the light
1530 of a number of problems with the previous contributed implementation
1531 (4.30/29). In particular:
1533 . If the quota is zero, the maildirsize file is maintained, but no quota is
1534 imposed.
1536 . If the maildir directory does not exist, it is created before any attempt
1537 to write a maildirsize file.
1539 . The quota value in the file is just a cache; if the quota is changed in
1540 the transport, the new value overrides.
1542 . A regular expression is available for excluding directories from the
1543 count.
1545 20. The autoreply transport checks the characters in options that define the
1546 message's headers; it allows continued headers, but it was checking with
1547 isspace() after an embedded newline instead of explicitly looking for a
1548 space or a tab.
1550 21. If all the "regular" hosts to which an address was routed had passed their
1551 expiry times, and had not reached their retry times, the address was
1552 bounced, even if fallback hosts were defined. Now Exim should go on to try
1553 the fallback hosts.
1555 22. Increased buffer sizes in the callout code from 1024 to 4096 to match the
1556 equivalent code in the SMTP transport. Some hosts send humungous responses
1557 to HELO/EHLO, more than 1024 it seems.
1559 23. Refactoring: code in filter.c used (void *) for "any old type" but this
1560 gives compiler warnings in some environments. I've now done it "properly",
1561 using a union.
1563 24. The replacement for inet_ntoa() that is used with gcc on IRIX systems
1564 (because of problems with the built-in one) was declared to return uschar *
1565 instead of char *, causing compiler failure.
1567 25. Fixed a file descriptor leak when processing alias/forward files.
1569 26. Fixed a minor format string issue in dbfn.c.
1571 27. Typo in exim.c: ("dmbnz" for "dbmnz").
1573 28. If a filter file refered to $h_xxx or $message_headers, and the headers
1574 contained RFC 2047 "words", Exim's memory could, under certain conditions,
1575 become corrupted.
1577 29. When a sender address is verified, it is cached, to save repeating the test
1578 when there is more than one recipient in a message. However, when the
1579 verification involves a callout, it is possible for different callout
1580 options to be set for different recipients. It is too complicated to keep
1581 track of this in the cache, so now Exim always runs a verification when a
1582 callout is required, relying on the callout cache for the optimization.
1583 The overhead is duplication of the address routing, but this should not be
1584 too great.
1586 30. Fixed a bug in callout caching. If a RCPT command caused the sender address
1587 to be verified with callout=postmaster, and the main callout worked but the
1588 postmaster check failed, the verification correctly failed. However, if a
1589 subsequent RCPT command asked for sender verification *without* the
1590 postmaster check, incorrect caching caused this verification also to fail,
1591 incorrectly.
1593 31. Exim caches DNS lookup failures so as to avoid multiple timeouts; however,
1594 it was not caching the DNS options (qualify_single, search_parents) that
1595 were used when the lookup failed. A subsequent lookup with different
1596 options therefore always gave the same answer, though there were cases
1597 where it should not have. (Example: a "domains = !$mx_any" option on a
1598 dnslookup router: the "domains" option is always processed without any
1599 widening, but the router might have qualify_single set.) Now Exim uses the
1600 cached value only when the same options are set.
1602 32. Added John Jetmore's "exipick" utility to the distribution.
1604 33. GnuTLS: When an attempt to start a TLS session fails for any reason other
1605 than a timeout (e.g. a certificate is required, and is not provided), an
1606 Exim server now closes the connection immediately. Previously it waited for
1607 the client to close - but if the client is SSL, it seems that they each
1608 wait for each other, leading to a delay before one of them times out.
1610 34: GnuTLS: Updated the code to use the new GnuTLS 1.0.0 API. I have not
1611 maintained 0.8.x compatibility because I don't think many are using it, and
1612 it is clearly obsolete.
1614 35. Added TLS support for CRLs: a tls_crl global option and one for the smtp
1615 transport.
1617 36. OpenSSL: $tls_certificate_verified was being set to 1 even if the
1618 client certificate was expired. A simple patch fixes this, though I don't
1619 understand the full logic of why the verify callback is called multiple
1620 times.
1622 37. OpenSSL: a patch from Robert Roselius: "Enable client-bug workaround.
1623 Versions of OpenSSL as of 0.9.6d include a 'CBC countermeasure' feature,
1624 which causes problems with some clients (such as the Certicom SSL Plus
1625 library used by Eudora). This option, SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS,
1626 disables the coutermeasure allowing Eudora to connect."
1628 38. Exim was not checking that a write() to a log file succeeded. This could
1629 lead to Bad Things if a log got too big, in particular if it hit a file
1630 size limit. Exim now panics and dies if it cannot write to a log file, just
1631 as it does if it cannot open a log file.
1633 39. Modified OS/Makefile-Linux so that it now contains
1637 The two -D definitions ensure that Exim is compiled with large file
1638 support, which makes it possible to handle log files that are bigger than
1639 2^31.
1641 40. Fixed a subtle caching bug: if (in an ACL or a set of routers, for
1642 instance) a domain was checked against a named list that involved a lookup,
1643 causing $domain_data to be set, then another domain was checked against the
1644 same list, then the first domain was re-checked, the value of $domain_data
1645 after the final check could be wrong. In particular, if the second check
1646 failed, it could be set empty. This bug probably also applied to
1647 $localpart_data.
1649 41. The strip_trailing_dot option was not being applied to the address given
1650 with the -f command-line option.
1652 42. The code for reading a message's header from the spool was incrementing
1653 $received_count, but never initializing it. This meant that the value was
1654 incorrect (doubled) while delivering a message in the same process in which
1655 it was received. In the most common configuration of Exim, this never
1656 happens - a fresh exec is done - but it can happen when
1657 deliver_drop_privilege is set.
1659 43. When Exim logs an SMTP synchronization error - client data sent too soon -
1660 it now includes up to 150 characters of the unexpected data in the log
1661 line.
1663 44. The exim_dbmbuild utility uses fixed size buffers for reading input lines
1664 and building data strings. The size of both of these buffers was 10 000
1665 bytes - far larger than anybody would *ever* want, thought I. Needless to
1666 say, somebody hit the limit. I have increased the maximum line length to
1667 20 000 and the maximum data length of concatenated lines to 100 000. I have
1668 also fixed two bugs, because there was no checking on these buffers. Tsk,
1669 tsk. Now exim_dbmbuild gives a message and exits with an error code if a
1670 buffer is too small.
1672 45. The exim_dbmbuild utility did not support quoted keys, as Exim does in
1673 lsearch lookups. Now it does.
1675 46. When parsing a route_list item in a manualroute router, a fixed-length
1676 buffer was used for the list of hosts. I made this 1024 bytes long,
1677 thinking that nobody would ever have a list of hosts that long. Wrong.
1678 Somebody had a whole pile of complicated expansion conditions, and the
1679 string was silently truncated, leading to an expansion error. It turns out
1680 that it is easier to change to an unlimited length (owing to other changes
1681 that have happened since this code was originally written) than to build
1682 structure for giving a limitation error. The length of the item that
1683 expands into the list of hosts is now unlimited.
1685 47. The lsearch lookup could not handle data where the length of text line was
1686 more than 4095 characters. Such lines were truncated, leading to shortened
1687 data being returned. It should now handle lines of any length.
1689 48. Minor wording revision: "cannot test xxx in yyy ACL" becomes "cannot test
1690 xxx condition in yyy ACL" (e.g. "cannot test domains condition in DATA
1691 ACL").
1693 49. Cosmetic tidy to scripts like exicyclog that are generated by globally
1694 replacing strings such as BIN_DIRECTORY in a source file: the replacement
1695 no longer happens in comment lines. A list of replacements is now placed
1696 at the head of all of the source files, except those whose only change is
1697 to replace PERL_COMMAND in the very first #! line.
1699 50. Replaced the slow insertion sort in queue.c, for sorting the list of
1700 messages on the queue, with a bottom-up merge sort, using code contributed
1701 by Michael Haardt. This should make operations like -bp somewhat faster on
1702 large queues. It won't affect queue runners, except when queue_run_in_order
1703 is set.
1705 51. Installed eximstats 1.31 in the distribution.
1707 52. Added support for SRV lookups to the dnslookup router.
1709 53. If an ACL referred to $message_body or $message_body_end, the value was not
1710 reset for any messages that followed in the same SMTP session.
1712 54. The store-handling optimization for building very long strings was not
1713 differentiating between the different store pools. I don't think this
1714 actually made any difference in practice, but I've tidied it.
1716 55. While running the routers to verify a sender address, $sender_address
1717 was still set to the sender address. This is wrong, because when routing to
1718 send a bounce to the sender, it would be empty. Therefore, I have changed
1719 it so that, while verifying a sender address, $sender_address is set to <>.
1720 (There is no change to what happens when verifying a recipient address.)
1722 56. After finding MX (or SRV) records, Exim was doing a DNS lookup for the
1723 target A or AAAA records (if not already returned) without resetting the
1724 qualify_single or search_parents options of the DNS resolver. These are
1725 inappropriate in this case because the targets of MX and SRV records must
1726 be FQDNs. A broken DNS record could cause trouble if it happened to have a
1727 target that, when qualified, matched something in the local domain. These
1728 two options are now turned off when doing these lookups.
1730 57. It seems that at least some releases of Reiserfs (which does not have the
1731 concept of a fixed number of inodes) returns zero and not -1 for the
1732 number of available inodes. This interacted badly with check_spool_inodes,
1733 which assumed that -1 was the "no such thing" setting. What I have done is
1734 to check that the total number of inodes is greater than zero before doing
1735 the test of how many are available.
1737 58. When a "warn" ACL statement has a log_message modifier, the message is
1738 remembered, and not repeated. This is to avoid a lot of repetition when a
1739 message has many recipients that cause the same warning to be written.
1740 Howewer, Exim was preserving the list of already written lines for an
1741 entire SMTP session, which doesn't seem right. The memory is now reset if a
1742 new message is started.
1744 59. The "rewrite" debugging flag was not showing the result of rewriting in the
1745 debugging output unless log_rewrite was also set.
1747 60. Avoid a compiler warning on 64-bit systems in dsearch.c by avoiding the use
1748 of (int)(handle) when we know that handle contains (void *)(-1).
1750 61. The Exim daemon panic-logs an error return when it closes the incoming
1751 connection. However "connection reset by peer" seems to be common, and
1752 isn't really an error worthy of noting specially, so that particular error
1753 is no long logged.
1755 62. When Exim is trying to find all the local interfaces, it used to panic and
1756 die if the ioctl to get the interface flags failed. However, it seems that
1757 on at least one OS (Solaris 9) it is possible to have an interface that is
1758 included in the list of interfaces, but for which you get a failure error
1759 for this call. This happens when the interface is not "plumbed" into a
1760 protocol (i.e. neither IPv4 nor IPv6). I've changed the code so that a
1761 failure of the "get flags" call assumes that the interface is down.
1763 63. Added a ${eval10: operator, which assumes all numbers are decimal. This
1764 makes life easier for people who are doing arithmetic on fields extracted
1765 from dates, where you often get leading zeros that should not be
1766 interpreted as octal.
1768 64. Added qualify_domain to the redirect router, to override the global
1769 setting.
1771 65. If a pathologically long header line contained very many addresses (the
1772 report of this problem mentioned 10 000) and each of them was rewritten,
1773 Exim could use up a very large amount of memory. (It kept on making new
1774 copies of the header line as it rewrote, and never released the old ones.)
1775 At the expense of a bit more processing, the header rewriting function has
1776 been changed so that it no longer eats memory in this way.
1778 66. The generation of the Received: header has been moved from the time that a
1779 message starts to be received, to the time that it finishes. The timestamp
1780 in the Received: header should now be very close to that of the <= log
1781 line. There are two side-effects of this change:
1783 (a) If a message is rejected by a DATA or non-SMTP ACL or local_scan(), the
1784 logged header lines no longer include the local Received: line, because
1785 it has not yet been created. The same applies to a copy of the message
1786 that is returned to a non-SMTP sender when a message is rejected.
1788 (b) When a filter file is tested using -bf, no additional Received: header
1789 is added to the test message. After some thought, I decided that this
1790 is a bug fix.
1792 This change does not affect the value of $received_for. It is still set
1793 after address rewriting, but before local_scan() is called.
1795 67. Installed the latest Cygwin-specific files from the Cygwin maintainer.
1797 68. GnuTLS: If an empty file is specified for tls_verify_certificates, GnuTLS
1798 gave an unhelpful panic error message, and a defer error. I have managed to
1799 change this behaviour so that it now rejects any supplied certificate,
1800 which seems right, as the list of acceptable certificates is empty.
1802 69. OpenSSL: If an empty file is specified for tls_verify_certificates, OpenSSL
1803 gave an unhelpful defer error. I have not managed to make this reject any
1804 supplied certificates, but the error message it gives is "no certificate
1805 supplied", which is not helpful.
1807 70. exigrep's output now also includes lines that are not associated with any
1808 message, but which match the given pattern. Implemented by a patch from
1809 Martin Sluka, which also tidied up the Perl a bit.
1811 71. Recipient callout verification, like sender verification, was using <> in
1812 the MAIL FROM command. This isn't really the right thing, since the actual
1813 sender may affect whether the remote host accepts the recipient or not. I
1814 have changed it to use the actual sender in the callout; this means that
1815 the cache record is now keyed on a recipient/sender pair, not just the
1816 recipient address. There doesn't seem to be a real danger of callout loops,
1817 since a callout by the remote host to check the sender would use <>.
1818 [SEE ABOVE: changed after hitting problems.]
1820 72. Exim treats illegal SMTP error codes that do not begin with 4 or 5 as
1821 temporary errors. However, in the case of such a code being given after
1822 the end of a data transmission (i.e. after ".") Exim was failing to write
1823 a retry record for the message. (Yes, there was some broken host that was
1824 actually sending 8xx at this point.)
1826 73. An unknown lookup type in a host list could cause Exim to panic-die when
1827 the list was checked. (An example that provoked this was putting <; in the
1828 middle of a list instead of at the start.) If this happened during a DATA
1829 ACL check, a -D file could be left lying around. This kind of configuration
1830 error no longer causes Exim to die; instead it causes a defer errror. The
1831 incident is still logged to the main and panic logs.
1833 74. Buglet left over from Exim 3 conversion. The message "too many messages
1834 in one connection" was written to the rejectlog but not the mainlog, except
1835 when address rewriting (yes!) was being logged.
1837 75. Added write_rejectlog option.
1839 76. When a system filter was run not as root (that is, when system_filter_user
1840 was set), the values of the $n variables were not being returned to the
1841 main process; thus, they were not subsequently available in the $sn
1842 variables.
1844 77. Added +return_path_on_delivery log selector.
1846 78. A connection timeout was being treated differently from recipients deferred
1847 when testing hosts_max_try with a message that was older than the host's
1848 retry timeout. (The host should not be counted, thus allowing all hosts to
1849 be tried at least once before bouncing.) This may have been the cause of an
1850 occasionally reported bug whereby a message would remain on the queue
1851 longer than the retry timeout, but would be bounced if a delivery was
1852 forced. I say "may" because I never totally pinned down the problem;
1853 setting up timeout/retry tests is difficult. See also the next item.
1855 79. The ultimate address timeout was not being applied to errors that involved
1856 a combination of host plus message (for example, a timeout on a MAIL
1857 command). When an address resolved to a number of possible hosts, and they
1858 were not all tried for each delivery (e.g. because of hosts_max_try), a
1859 message could remain on the queue longer than the retry timeout.
1861 80. Sieve bug: "stop" inside "elsif" was broken. Applied a patch from Michael
1862 Haardt.
1864 81. Fixed an obscure SMTP outgoing bug which required at least the following
1865 conditions: (a) there was another message waiting for the same server;
1866 (b) the server returned 5xx to all RCPT commands in the first message so
1867 that the message was not completed; (c) the server dropped the connection
1868 or gave a negative response to the RSET that Exim sends to abort the
1869 transaction. The observed case was a dropped connection after DATA that had
1870 been sent in pipelining mode. That is, the server had advertised PIPELINING
1871 but was not implementing it correctly. The effect of the bug was incorrect
1872 behaviour, such as trying another host, and this could lead to a crash.
1875 Exim version 4.30
1876 -----------------
1878 1. The 3rd arguments to getsockname(), getpeername(), and accept() in exim.c
1879 and daemon.c were passed as pointers to ints; they should have been
1880 pointers to socklen_t variables (which are typically unsigned ints).
1882 2. Some signed/unsigned type warnings in the os.c file for Linux have been
1883 fixed.
1885 3. Fixed a really odd bug that affected only the testing scheme; patching a
1886 certain fixed string in the binary changed the value of another string that
1887 happened to be identical to the end of the original first string.
1889 4. When gethostbyname() (or equivalent) is passed an IP address as a "host
1890 name", it returns that address as the IP address. On some operating
1891 systems (e.g. Solaris), it also passes back the IP address string as the
1892 "host name". However, on others (e.g. Linux), it passes back an empty
1893 string. Exim wasn't checking for this, and was changing the host name to an
1894 empty string, assuming it had been canonicized.
1896 5. Although rare, it is permitted to have more than one PTR record for a given
1897 IP address. I thought that gethostbyaddr() or getipnodebyaddr() always gave
1898 all the names associated with an address, because they do in Solaris.
1899 However, it seems that they do not in Linux for data that comes from the
1900 DNS. If an address in /etc/hosts has multiple names, they _are_ all given.
1901 I found this out when I moved to a new Linux workstation and tried to run
1902 the Exim test suite.
1904 To get round this problem I have changed the code so that it now does its
1905 own call to the DNS to look up PTR records when searching for a host name.
1906 If nothing can be found in the DNS, it tries gethostbyaddr(), so that
1907 addresses that are only in /etc/hosts are still found.
1909 This behaviour is, however, controlled by an option called host_lookup_
1910 order, which defaults to "bydns:byaddr". If people want to use the other
1911 order, or indeed, just use one or the other means of lookup, they can
1912 specify it in this variable.
1914 6. If a PTR record yields an empty name, Exim treats it as non-existent. In
1915 some operating systems, this comes back from gethostbyaddr() as an empty
1916 string, and this is what Exim used to test for. However, it seems that in
1917 other systems, "." is yielded. Exim now tests for this case too.
1919 7. The values of check_spool_space and check_log_space are now held internally
1920 as a number of kilobytes instead of an absolute number of bytes. If a
1921 numbers is specified without 'K' or 'M', it is rounded up to the nearest
1922 kilobyte. This means that much larger values can be stored.
1924 8. Exim monitor: an attempt to get the action menu when not actually pointing
1925 at a message produces an empty menu entitled "No message selected". This
1926 works on Solaris (OpenWindows). However, XFree86 does not like a menu with
1927 no entries in it ("Shell widget menu has zero width and/or height"). So I
1928 have added a single, blank menu entry in this case.
1930 9. Added ${quote_local_part.
1932 10. MIME decoding is now applied to the contents of Subject: header lines when
1933 they are logged.
1935 11. Now that a reference to $sender_host_address automatically causes a reverse
1936 lookup to occur if necessary (4.13/18), there is no need to arrange for a
1937 host lookup before query-style lookups in lists that might use this
1938 variable. This has therefore been abolished, and the "net-" prefix is no
1939 longer necessary for query-style lookups.
1941 12. The Makefile for SCO_SV contained a setting of LDFLAGS. This appears to
1942 have been a typo for LFLAGS, so it has been changed.
1944 13. The install script calls Exim with "-C /dev/null" in order to find the
1945 version number. If ALT_CONFIG_PREFIX was set, this caused an error message
1946 to be output. Howeve, since Exim outputs its version number before the
1947 error, it didn't break the script. It just looked ugly. I fixed this by
1948 always allowing "-C /dev/null" if the caller is root.
1950 14. Ignore overlarge ACL variable number when reading spool file - insurance
1951 against a later release with more variables having written the file.
1953 15. The standard form for an IPv6 address literal was being rejected by EHLO.
1954 Example: [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts
1955 this, as well as the form without the "IPv6" on the front.
1957 16. Added CHOWN_COMMAND=/usr/sbin/chown and LIBS=-lresolv to the
1958 OS/Makefile-Darwin file.
1960 17. Fixed typo in lookups/ldap.c: D_LOOKUP should be D_lookup. This applied
1961 only to LDAP libraries that do not have LDAP_OPT_DEREF.
1963 18. After change 4.21/52, "%ld" was used to format the contents of the $inode
1964 variable. However, some OS use ints for inodes. I've added cast to long int
1965 to get rid of the compiler warning.
1967 19. I had forgotten to lock out "/../" in configuration file names when
1968 ALT_CONFIG_PREFIX was set.
1970 20. Routers used for verification do not need to specify transports. However,
1971 if such a router generated a host list, and callout was configured, Exim
1972 crashed, because it could not find a port number from the (non-existent)
1973 transport. It now assumes port 25 in this circumstance.
1975 21. Added the -t option to exigrep.
1977 22. If LOOKUP_LSEARCH is defined, all three linear search methods (lsearch,
1978 wildlsearch, nwildlsearch) are compiled. LOOKUP_WILDLSEARCH and LOOKUP_
1979 NWILDLSEARCH are now obsolete, but retained for compatibility. If either of
1980 them is set, LOOKUP_LSEARCH is forced.
1982 23. "exim -bV" now outputs a list of lookups that are included in the binary.
1984 24. Added sender and host information to the "rejected by local_scan()" log
1985 line; previously there was no indication of these.
1987 25. Added .include_if_exists.
1989 26. Change 3.952/11 added an explicit directory sync on top of a file sync for
1990 Linux. It turns out that not all file systems support this. Apparently some
1991 versions of NFS do not. (It's rare to put Exim's spool on NFS, but people
1992 do it.) To cope with this, the error EINVAL, which means that sync-ing is
1993 not supported on the file descriptor, is now ignored when Exim is trying to
1994 sync a directory. This applies only to Linux.
1996 27. Added -DBIND_8_COMPAT to the CLFAGS setting for Darwin.
1998 28. In Darwin (MacOS X), the PAM headers are in /usr/include/pam and not in
1999 /usr/include/security. There's now a flag in OS/os.h-Darwin to cope with
2000 this.
2002 29. Added support for maildirsize files from supplied patch (modified a bit).
2004 30. The use of :fail: followed by an empty string could lead Exim to respond to
2005 sender verification failures with (e.g.):
2007 550 Verification failed for <xxx>
2008 550 Sender verify failed
2010 where the first response line was missing the '-' that indicates it is not
2011 the final line of the response.
2013 31. The loop for finding the name of the user that called Exim had a hardwired
2014 limit of 10; it now uses the value of finduser_retries, which is used for
2015 all other user lookups.
2017 32. Added $received_count variable, available in data and not_smtp ACLs, and at
2018 delivery time.
2020 33. Exim was neglecting to zero errno before one call of strtol() when
2021 expanding a string and expecting an integer value. On some systems this
2022 resulted in spurious "integer overflow" errors. Also, it was casting the
2023 result into an int without checking.
2025 34. Testing for a connection timeout using "timeout_connect" in the retry rules
2026 did not work. The code looks as if it has *never* worked, though it appears
2027 to have been documented since at least releast 1.62. I have made it work.
2029 35. The "timeout_DNS" error in retry rules, also documented since at least
2030 1.62, also never worked. As it isn't clear exactly what this means, and
2031 clearly it isn't a major issue, I have abolished the feature by treating it
2032 as "timeout", and writing a warning to the main and panic logs.
2034 36. The display of retry rules for -brt wasn't always showing the error code
2035 correctly.
2037 37. Added new error conditions to retry rules: timeout_A, timeout_MX,
2038 timeout_connect_A, timeout_connect_MX.
2040 38. Rewriting the envelope sender at SMTP time did not allow it to be rewritten
2041 to the empty sender.
2043 39. The daemon was not analysing the content of -oX till after it had closed
2044 stderr and disconnected from the controlling terminal. This meant that any
2045 syntax errors were only noted on the panic log, and the return code from
2046 the command was 0. By re-arranging the code a little, I've made the
2047 decoding happen first, so such errors now appear on stderr, and the return
2048 code is 1. However, the actual setting up of the sockets still happens in
2049 the disconnected process, so errors there are still only recorded on the
2050 panic log.
2052 40. A daemon listener on a wildcard IPv6 socket that also accepts IPv4
2053 connections (as happens on some IP stacks) was logged at start up time as
2054 just listening for IPv6. It now logs "IPv6 with IPv4". This differentiates
2055 it from "IPv6 and IPv4", which means that two separate sockets are being
2056 used.
2058 41. The debug output for gethostbyname2() or getipnodebyname() failures now
2059 says whether AF_INET or AF_INET6 was passed as an argument.
2061 42. Exiwhat output was messed up when time zones were included in log
2062 timestamps.
2064 43. Exiwhat now gives more information about the daemon's listening ports,
2065 and whether -tls-on-connect was used.
2067 44. The "port" option of the smtp transport is now expanded.
2069 45. A "message" modifier in a "warn" statement in a non-message ACL was being
2070 silently ignored. Now an error message is written to the main and panic
2071 logs.
2073 46. There's a new ACL modifier called "logwrite" which writes to a log file
2074 as soon as it is encountered.
2076 47. Added $local_user_uid and $local_user_gid at routing time.
2078 48. Exim crashed when trying to verify a sender address that was being
2079 rewritten to "<>".
2081 49. Exim was recognizing only a space character after ".include". It now also
2082 recognizes a tab character.
2084 50. Fixed several bugs in the Perl script that creates the exim.8 man page by
2085 extracting the relevant information from the specification. The man page no
2086 longer contains scrambled data for the -d option, and I've added a section
2087 at the front about calling Exim under different names.
2089 51. Added "extra_headers" argument to the "mail" command in filter files.
2091 52. Redirecting mail to an unqualified address in a Sieve filter caused Exim to
2092 crash.
2094 53. Installed eximstats 1.29.
2096 54. Added transport_filter_timeout as a generic transport option.
2098 55. Exim no longer adds an empty Bcc: header to messages that have no To: or
2099 Cc: header lines. This was required by RFC 822, but it not required by RFC
2100 2822.
2102 56. Exim used to add From:, Date:, and Message-Id: header lines to any
2103 incoming messages that did not have them. Now it does so only if the
2104 message originates locally, that is, if there is no associated remote host
2105 address. When Resent- header lines are present, this applies to the Resent-
2106 lines rather than the non-Resent- lines.
2108 57. Drop incoming SMTP connection after too many syntax or protocol errors. The
2109 limit is controlled by smtp_max_synprot_errors, defaulting to 3.
2111 58. Messages for configuration errors now include the name of the main
2112 configuration file - useful now that there may be more than one file in a
2113 list (.included file names were always shown).
2115 59. Change 4.21/82 (run initgroups() when starting the daemon) causes problems
2116 for those rare installations that do not start the daemon as root or run it
2117 setuid root. I've cut out the call to initgroups() if the daemon is not
2118 root at that time.
2120 60. The Exim user and group can now be bound into the binary as text strings
2121 that are looked up at the start of Exim's processing.
2123 61. Applied a small patch for the Interbase code, supplied by Ard Biesheuvel.
2125 62. Added $mailstore_basename variable.
2127 63. Installed patch to sieve.c from Michael Haardt.
2129 64. When Exim failed to open the panic log after failing to open the main log,
2130 the original message it was trying to log was written to stderr and debug
2131 output, but if they were not available (the usual case in production), it
2132 was lost. Now it is written to syslog before the two lines that record the
2133 failures to open the logs.
2135 65. Users' Exim filters run in subprocesses under the user's uid. It is
2136 possible for a "deliver" command or an alias in a "personal" command to
2137 provoke an address rewrite. If logging of address rewriting is configured,
2138 this fails because the process is not running as root or exim. There may be
2139 a better way of dealing with this, but for the moment (because 4.30 needs
2140 to be released), I have disabled address rewrite logging when running a
2141 filter in a non-root, non-exim process.
2144 Exim version 4.24
2145 -----------------
2147 1. The buildconfig auxiliary program wasn't quoting the value set for
2148 HEADERS_CHARSET. This caused a compilation error complaining that 'ISO' was
2149 not defined. This bug was masked in 4.22 by the effect that was fixed in
2150 change 4.23/1.
2152 2. Some messages that were rejected after a message id was allocated were
2153 shown as "incomplete" by exigrep. It no longer does this for messages that
2154 are rejected by local_scan() or the DATA or non-SMTP ACLs.
2156 3. If a Message-ID: header used a domain literal in the ID, and Exim did not
2157 have allow_domain_literals set, the ID did not get logged in the <= line.
2158 Domain literals are now always recognized in Message-ID: header lines.
2160 4. The first argument for a ${extract expansion item is the key name or field
2161 number. Leading and trailing spaces in this item were not being ignored,
2162 causing some misleading effects.
2164 5. When deliver_drop_privilege was set, single queue runner processes started
2165 manually (i.e. by the command "exim -q") or by the daemon (which uses the
2166 same command in the process it spins off) were not dropping privilege.
2168 6. When the daemon running as "exim" started a queue runner, it always
2169 re-executed Exim in the spun-off process. This is a waste of effort when
2170 deliver_drop_privilege is set. The new process now just calls the
2171 queue-runner function directly.
2174 Exim version 4.23
2175 -----------------
2177 1. Typo in the src/EDITME file: it referred to HEADERS_DECODE_TO instead of
2180 2. Change 4.21/73 introduced a bug. The pid file path set by -oP was being
2181 ignored. Though the use of -oP was forcing the writing of a pid file, it
2182 was always written to the default place.
2184 3. If the message "no IP address found for host xxxx" is generated during
2185 incoming verification, it is now followed by identification of the incoming
2186 connection (so you can more easily find what provoked it).
2188 4. Bug fix for Sieve filters: "stop" inside a block was not working properly.
2190 5. Added some features to "harden" Exim a bit more against certain attacks:
2192 (a) There is now a build-time option called FIXED_NEVER_USERS that can
2193 be put in Local/Makefile. This is like the never_users runtime option,
2194 but it cannot be overridden. The default setting is "root".
2196 (b) If ALT_CONFIG_PREFIX is defined in Local/Makefile, it specifies a
2197 prefix string with which any file named in a -C command line option
2198 must start.
2200 (c) If ALT_CONFIG_ROOT_ONLY is defined in Local/Makefile, root privilege
2201 is retained for -C and -D only if the caller of Exim is root. Without
2202 it, the exim user may also use -C and -D and retain privilege.
2204 (d) If DISABLE_D_OPTION is defined in Local/Makefile, the use of the -D
2205 command line option is disabled.
2207 6. Macro names set by the -D option must start with an upper case letter, just
2208 like macro names defined in the configuration file.
2210 7. Added "dereference=" facility to LDAP.
2212 8. Two instances of the typo "uknown" in the source files are fixed.
2214 9. If a PERL_COMMAND setting in Local/Makefile was not at the start of a line,
2215 the Configure-Makefile script screwed up while processing it.
2217 10. Incorporated PCRE 4.4.
2219 11. The SMTP synchronization check was not operating right at the start of an
2220 SMTP session. For example, it could not catch a HELO sent before the client
2221 waited for the greeting. There is now a check for outstanding input at the
2222 point when the greeting is written. Because of the duplex, asynchronous
2223 nature of TCP/IP, it cannot be perfect - the incorrect input may be on its
2224 way, but not yet received, when the check is performed.
2226 12. Added tcp_nodelay to make it possible to turn of the setting of TCP_NODELAY
2227 on TCP/IP sockets, because this apparently causes some broken clients to
2228 timeout.
2230 13. Installed revised OS/Makefile-CYGWIN and OS/os.c-cygwin (the .h file was
2231 unchanged) from the Cygwin maintainer.
2233 14. The code for -bV that shows what is in the binary showed "mbx" when maildir
2234 was supported instead of testing for mbx. Effectively a typo.
2236 15. The spa authenticator server code was not checking that the input it
2237 received was valid base64.
2239 16. The debug output line for the "set" modifier in ACLs was not showing the
2240 name of the variable that was being set.
2242 17. Code tidy: the variable type "vtype_string" was never used. Removed it.
2244 18. Previously, a reference to $sender_host_name did not cause a DNS reverse
2245 lookup on its own. Something else was needed to trigger the lookup. For
2246 example, a match in host_lookup or the need for a host name in a host list.
2247 Now, if $sender_host_name is referenced and the host name has not yet been
2248 looked up, a lookup is performed. If the lookup fails, the variable remains
2249 empty, and $host_lookup_failed is set to "1".
2251 19. Added "eqi" as a case-independent comparison operator.
2253 20. The saslauthd authentication condition could segfault if neither service
2254 nor realm was specified.
2256 21. If an overflowing value such as "2048M" was set for message_size_limit, the
2257 error message that was logged was misleading, and incoming SMTP
2258 connections were dropped. The message is now more accurate, and temporary
2259 errors are given to SMTP connections.
2261 22. In some error situations (such as 21 above) Exim rejects all SMTP commands
2262 (except RSET) with a 421 error, until QUIT is received. However, it was
2263 failing to send a response to QUIT.
2265 23. The HELO ACL was being run before the code for helo_try_verify_hosts,
2266 which made it impossible to use "verify = helo" in the HELO ACL. The HELO
2267 ACL is now run after the helo_try_verify_hosts code.
2269 24. "{MD5}" and "{SHA1}" are now recognized as equivalent to "{md5"} and
2270 "{sha1}" in the "crypteq" expansion condition (in fact the comparison is
2271 case-independent, so other case variants are also recognized). Apparently
2272 some systems use these upper case variants.
2274 25. If more than two messages were waiting for the same host, and a transport
2275 filter was specified for the transport, Exim sent two messages over the
2276 same TCP/IP connection, and then failed with "socket operation on non-
2277 socket" when it tried to send the third.
2279 26. Added Exim::debug_write and Exim::log_write for embedded Perl use.
2281 27. The extern definition of crypt16() in expand.c was not being excluded when
2282 the OS had its own crypt16() function.
2284 28. Added bounce_return_body as a new option, and bounce_return_size_limit
2285 as a preferred synonym for return_size_limit, both as an option and as an
2286 expansion variable.
2288 29. Added LIBS=-liconv to OS/Makefile-OSF1.
2290 30. Changed the default configuration ACL to relax the local part checking rule
2291 for addresses that are not in any local domains. For these addresses,
2292 slashes and pipe symbols are allowed within local parts, but the sequence
2293 /../ is explicitly forbidden.
2295 31. SPA server authentication was not clearing the challenge buffer before
2296 using it.
2298 32. log_message in a "warn" ACL statement was writing to the reject log as
2299 well as to the main log, which contradicts the documentation and doesn't
2300 seem right (because no rejection is happening). So I have stopped it.
2302 33. Added Ard Biesheuvel's lookup code for accessing an Interbase database.
2303 However, I am unable to do any testing of this.
2305 34. Fixed an infelicity in the appendfile transport. When checking directories
2306 for a mailbox, to see if any needed to be created, it was accidentally
2307 using path names with one or more superfluous leading slashes; tracing
2308 would show up entries such as stat("///home/ph10", 0xFFBEEA48).
2310 35. If log_message is set on a "discard" verb in a MAIL or RCPT ACL, its
2311 contents are added to the log line that is written for every discarded
2312 recipient. (Previously a log_message setting was ignored.)
2314 36. The ${quote: operator now quotes the string if it is empty.
2316 37. The install script runs exim in order to find its version number. If for
2317 some reason other than non-existence or emptiness, which it checks, it
2318 could not run './exim', it was installing it with an empty version number,
2319 i.e. as "exim-". This error state is now caught, and the installation is
2320 aborted.
2322 38. An argument was missing from the function that creates an error message
2323 when Exim fails to connect to the socket for saslauthd authentication.
2324 This could cause Exim to crash, or give a corrupted message.
2326 39. Added isip, isip4, and isip6 to ${if conditions.
2328 40. The ACL variables $acl_xx are now saved with the message, and can be
2329 accessed later in routers, transports, and filters.
2331 41. The new lookup type nwildlsearch is like wildlsearch, except that the key
2332 strings in the file are not string-expanded.
2334 42. If a MAIL command specified a SIZE value that was too large to fit into an
2335 int variable, the check against message_size_limit failed. Such values are
2336 now forced to INT_MAX, which is around 2Gb for a 32-bit variable. Maybe one
2337 day this will have to be increased, but I don't think I want to be around
2338 when emails are that large.
2342 Exim version 4.22
2343 -----------------
2345 1. Removed HAVE_ICONV=yes from OS/Makefile-FreeBSD, since it seems that
2346 iconv() is not standard in FreeBSD.
2348 2. Change 4.21/17 was buggy and could cause stack overwriting on a system with
2349 IPv6 enabled. The observed symptom was a segmentation fault on return from
2350 the function os_common_find_running_interfaces() in src/os.c.
2352 3. In the check_special_case() function in daemon.c I had used "errno" as an
2353 argument name, which causes warnings on some systems. This was basically a
2354 typo, since it was named "eno" in the comments!
2356 4. The code that waits for the clock to tick (at a resolution of some fraction
2357 of a second) so as to ensure message-id uniqueness was always waiting for
2358 at least one whole tick, when it could have waited for less. [This is
2359 almost certainly not relevant at current processor speeds, where it is
2360 unlikely to ever wait at all. But we try to future-proof.]
2362 5. The function that sleeps for a time interval that includes fractions of a
2363 second contained a race. It did not block SIGALRM between setting the
2364 timer, and suspending (a couple of lines later). If the interval was short
2365 and the sigsuspend() was delayed until after it had expired, the suspension
2366 never ended. On busy systems this could lead to processes getting stuck for
2367 ever.
2369 6. Some uncommon configurations may cause a lookup to happen in a queue runner
2370 process, before it forks any delivery processes. The open lookup caching
2371 mechanism meant that the open file or database connection was passed into
2372 the delivery process. The problem was that delivery processes always tidy
2373 up cached lookup data. This could cause a problem for the next delivery
2374 process started by the queue runner, because the external queue runner
2375 process does not know about the closure. So the next delivery process
2376 still has data in the lookup cache. In the case of a file lookup, there was
2377 no problem because closing a file descriptor in a subprocess doesn't affect
2378 the parent. However, if the lookup was caching a connection to a database,
2379 the connection was closed, and the second delivery process was likely to
2380 see errors such as "PGSQL: query failed: server closed the connection
2381 unexpectedly". The problem has been fixed by closing all cached lookups
2382 in a queue runner before running a delivery process.
2384 7. Compiler warning on Linux for the second argument of iconv(), which doesn't
2385 seem to have the "const" qualifier which it has on other OS. I've
2386 parameterised it.
2388 8. Change 4.21/2 was too strict. It is only if there are two authenticators
2389 *of the same type* (client or server) with the same public name that an
2390 error should be diagnosed.
2392 9. When Exim looked up a host name for an IP address, but failed to find the
2393 original IP address when looking up the host name (a safety check), it
2394 output the message "<ip address> does not match any IP for NULL", which was
2395 confusing, to say the least. The bug was that the host name should have
2396 appeared instead of "NULL".
2398 10. Since release 3.03, if Exim is called by a uid other than root or the Exim
2399 user that is built into the binary, and the -C or -D options is used, root
2400 privilege is dropped before the configuration file is read. In addition,
2401 logging is switched to stderr instead of the normal log files. If the
2402 configuration then re-defines the Exim user, the unprivileged environment
2403 is probably not what is expected, so Exim logs a panic warning message (but
2404 proceeds).
2406 However, if deliver_drop_privilege is set, the unprivileged state may well
2407 be exactly what is intended, so the warning has been cut out in that case,
2408 and Exim is allowed to try to write to its normal log files.
2411 Exim version 4.21
2412 -----------------
2414 1. smtp_return_error_details was not giving details for temporary sender
2415 or receiver verification errors.
2417 2. Diagnose a configuration error if two authenticators have the same public
2418 name.
2420 3. Exim used not to create the message log file for a message until the first
2421 delivery attempt. This could be confusing when incoming messages were held
2422 for policy or load reasons. The message log file is now created at the time
2423 the message is received, and an initial "Received" line is written to it.
2425 4. The automatically generated man page for command line options had a minor
2426 bug that caused no ill effects; however, a more serious problem was that
2427 the procedure for building the man page automatically didn't always
2428 operate. Consequently, release 4.20 contains an out-of-date version. This
2429 shouldn't happen again.
2431 5. When building Exim with embedded Perl support, the script that builds the
2432 Makefile was calling 'perl' to find its compile-time parameters, ignoring
2433 any setting of PERL_COMMAND in Local/Makefile. This is now fixed.
2435 6. The freeze_tell option was not being used for messages that were frozen on
2436 arrival, either by an ACL or by local_scan().
2438 7. Added the smtp_incomplete_transaction log selector.
2440 8. After STARTTLS, Exim was not forgetting that it had advertised AUTH, so it
2441 was accepting AUTH without a new EHLO.
2443 9. Added tls_remember_esmtp to cope with YAEB. This allows AUTH and other
2444 ESMTP extensions after STARTTLS without a new EHLO, in contravention of the
2445 RFC.
2447 10. Logging of TCP/IP connections (when configured) now happens in the main
2448 daemon process instead of the child process, so that the TCP/IP connection
2449 count is more accurate (but it can never be perfect).
2451 11. The use of "drop" in a nested ACL was not being handled correctly in the
2452 outer ACL. Now, if condition failure induced by the nested "drop" causes
2453 the outer ACL verb to deny access ("accept" or "discard" after "endpass",
2454 or "require"), the connection is dropped.
2456 12. Similarly, "discard" in a nested ACL wasn't being handled. A nested ACL
2457 that yield "discard" can now be used with an "accept" or a "discard" verb,
2458 but an error is generated for any others (because I can't see a useful way
2459 to define what should happen).
2461 13. When an ACL is read dynamically from a file (or anywhere else), the lines
2462 are now processed in the same way as lines in the Exim configuration file.
2463 In particular, continuation lines are supported.
2465 14. Added the "dnslists = a.b.c!=n.n.n.n" feature.
2467 15. Added -ti meaning -t -i.
2469 16. Check for letters, digits, hyphens, and dots in the names of dnslist
2470 domains, and warn by logging if others are found.
2472 17. At least on BSD, alignment is not guarenteed for the array of ifreq's
2473 returned from GIFCONF when Exim is trying to find the list of interfaces on
2474 a host. The code in os.c has been modified to copy each ifreq to an aligned
2475 structure in all cases.
2477 Also, in some cases, the returned ifreq's were being copied to a 'struct
2478 ifreq' on the stack, which was subsequently passed to host_ntoa(). That
2479 means the last couple of bytes of an IPv6 address could be chopped if the
2480 ifreq contained only a normal sockaddr (14 bytes storage).
2482 18. Named domain lists were not supported in the hosts_treat_as_local option.
2483 An entry such as +xxxx was not recognized, and was treated as a literal
2484 domain name.
2486 19. Ensure that header lines added by a DATA ACL are included in the reject log
2487 if the ACL subsequently rejects the message.
2489 20. Upgrade the cramtest.pl utility script to use Digest::MD5 instead of just
2490 MD5 (which is deprecated).
2492 21. When testing a filter file using -bf, Exim was writing a message when it
2493 took the sender from a "From " line in the message, but it was not doing so
2494 when it took $return_path from a Return-Path: header line. It now does.
2496 22. If the contents of a "message" modifier for a "warn" ACL verb do not begin
2497 with a valid header line field name (a series of printing characters
2498 terminated by a colon, Exim now inserts X-ACL-Warn: at the beginning.
2500 23. Changed "disc" in the source to "disk" to conform to the documentation and
2501 the book and for uniformity.
2503 24. Ignore Sendmail's -Ooption=value command line item.
2505 25. When execve() failed while trying to run a command in a pipe transport,
2506 Exim was returning EX_UNAVAILBLE (69) from the subprocess. However, this
2507 could be confused with a return value of 69 from the command itself. This
2508 has been changed to 127, the value the shell returns if it is asked to run
2509 a non-existent command. The wording for the related log line suggests a
2510 non-existent command as the problem.
2512 26. If received_header_text expands to an empty string, do not add a Received:
2513 header line to the message. (Well, it adds a token one on the spool, but
2514 marks it "old" so that it doesn't get used or transmitted.)
2516 27. Installed eximstats 1.28 (addition of -nt option).
2518 28. There was no check for failure on the call to getsockname() in the daemon
2519 code. This can fail if there is a shortage of resources on the system, with
2520 ENOMEM, for example. A temporary error is now given on failure.
2522 29. Contrary to the C standard, it seems that in some environments, the
2523 equivalent of setlocale(LC_ALL, "C") is not obeyed at the start of a C
2524 program. Exim now does this explicitly; it affects the formatting of
2525 timestamps using strftime().
2527 30. If exiqsumm was given junk data, it threw up some uninitialized variable
2528 complaints. I've now initialized all the variables, to avoid this.
2530 32. Header lines added by a system filter were not being "seen" during
2531 transport-time rewrites.
2533 33. The info_callback() function passed to OpenSSL is set up with type void
2534 (*)(SSL *, int, int), as described somewhere. However, when calling the
2535 function (actually a macro) that sets it up, the type void(*)() is
2536 expected. I've put in a cast to prevent warnings from picky compilers.
2538 34. If a DNS black list lookup found a CNAME record, but there were no A
2539 records associated with the domain it pointed at, Exim crashed.
2541 35. If a DNS black list lookup returned more than one A record, Exim ignored
2542 all but the first. It now scans all returned addresses if a particular IP
2543 value is being sought. In this situation, the contents of the
2544 $dnslist_value variable are a list of all the addresses, separated by a
2545 comma and a space.
2547 36. Tightened up the rules for host name lookups using reverse DNS. Exim used
2548 to accept a host name and all its aliases if the forward lookup for any of
2549 them yielded the IP address of the incoming connection. Now it accepts only
2550 those names whose forward lookup yields the correct IP address. Any other
2551 names are discarded. This closes a loophole whereby a rogue DNS
2552 administrator could create reverse DNS records to break through a
2553 wildcarded host restriction in an ACL.
2555 37. If a user filter or a system filter that ran in a subprocess used any of
2556 the numerical variables ($1, $2 etc), or $thisaddress, in a pipe command,
2557 the wrong values were passed to the pipe command ($thisaddress had the
2558 value of $0, $0 had the value of $1, etc). This bug was introduced by
2559 change 4.11/101, and not discovered because I wrote an inadequate test. :-(
2561 38. Improved the line breaking for long SMTP error messages from ACLs.
2562 Previously, if there was no break point between 40 and 75 characters, Exim
2563 left the rest of the message alone. Two changes have been made: (a) I've
2564 reduced the minimum length to 35 characters; (b) if it can't find a break
2565 point between 35 and 75 characters, it looks ahead and uses the first one
2566 that it finds. This may give the occasional overlong line, but at least the
2567 remaining text gets split now.
2569 39. Change 82 of 4.11 was unimaginative. It assumed the limit on the number of
2570 file descriptors might be low, and that setting 1000 would always raise it.
2571 It turns out that in some environments, the limit is already over 1000 and
2572 that lowering it causes trouble. So now Exim takes care not to decrease it.
2574 40. When delivering a message, the value of $return_path is set to $sender_
2575 address at the start of routing (routers may change the value). By an
2576 oversight, this default was not being set up when an address was tested by
2577 -bt or -bv, which affected the outcome if any router or filter referred to
2578 $return_path.
2580 41. The idea of the "warn" ACL verb is that it adds a header or writes to the
2581 log only when "message" or "log_message" are set. However, if one of the
2582 conditions was an address verification, or a call to a nested ACL, the
2583 messages generated by the underlying test were being passed through. This
2584 no longer happens. The underlying message is available in $acl_verify_
2585 message for both "message" and "log_message" expansions, so it can be
2586 passed through if needed.
2588 42. Added RFC 2047 interpretation of header lines for $h_ expansions, with a
2589 new expansion $bh_ to give the encoded byte string without charset
2590 translation. Translation happens only if iconv() is available; HAVE_ICONV
2591 indicates this at build time. HEADERS_CHARSET gives the charset to
2592 translate to; headers_charset can change it in the configuration, and
2593 "headers charset" can change it in an individual filter file.
2595 43. Now that we have a default RFC 2047 charset (see above), the code in Exim
2596 that creates RFC 2047 encoded "words" labels them as that charset instead
2597 of always using iso-8859-1. The cases are (i) the explicit ${rfc2047:
2598 expansion operator; (ii) when Exim creates a From: line for a local
2599 message; (iii) when a header line is rewritten to include a "phrase" part.
2601 44. Nasty bug in exiqsumm: the regex to skip already-delivered addresses was
2602 buggy, causing it to skip the first lines of messages whose message ID
2603 ended in 'D'. This would not have bitten before Exim release 4.14, because
2604 message IDs were unlikely to end in 'D' before then. The effect was to have
2605 incorrect size information for certain domains.
2607 45. #include "config.h" was missing at the start of the crypt16.c module. This
2608 caused trouble on Tru64 (aka OSF1) systems, because HAVE_CRYPT16 was not
2609 noticed.
2611 46. If there was a timeout during a "random" callout check, Exim treated it as
2612 a failure of the random address, and carried on sending RSET and the real
2613 address. If the delay was just some slowness somewhere, the response to the
2614 original RCPT would be taken as a response to RSET and so on, causing
2615 mayhem of various kinds.
2617 47. Change 50 for 4.20 was a heap of junk. I don't know what I was thinking
2618 when I implemented it. It didn't allow for the fact that some option values
2619 may legitimatetly be negative (e.g. size_addition), and it didn't even do
2620 the right test for positive values.
2622 48. Domain names in DNS records are case-independent. Exim always looks them up
2623 in lower case. Some resolvers return domain names in exactly the case they
2624 appear in the zone file, that is, they may contain uppercase letters. Not
2625 all resolvers do this - some return always lower case. Exim was treating a
2626 change of case by a resolver as a change of domain, similar to a widening
2627 of a domain abbreviation. This triggered its re-routing code and so it was
2628 trying to route what was effectively the same domain again. This normally
2629 caused routing to fail (because the router wouldn't handle the domain
2630 twice). Now Exim checks for this case specially, and just changes the
2631 casing of the domain that it ultimately uses when it transmits the message
2632 envelope.
2634 49. Added Sieve (RFC 3028) support, courtesy of Michael Haardt's contributed
2635 module.
2637 50. If a filter generated a file delivery with a non-absolute name (possible if
2638 no home directory exists for the router), the forbid_file option was not
2639 forbidding it.
2641 51. Added '&' feature to dnslists, to provide bit mask matching in addition to
2642 the existing equality matching.
2644 52. Exim was using ints instead of ino_t variables in some places where it was
2645 dealing with inode numbers.
2647 53. If TMPDIR is defined in Local/Makefile (default in src/EDITME is
2648 TMPDIR="/tmp"), Exim checks for the presence of an environment variable
2649 called TMPDIR, and if it finds it is different, it changes its value.
2651 54. The smtp_printf() function is now made available to local_scan() so
2652 additional output lines can be written before returning. There is also an
2653 smtp_fflush() function to enable the detection of a dropped connection.
2654 The variables smtp_input and smtp_batched_input are exported to
2655 local_scan().
2657 55. Changed the default runtime configuration: the message "Unknown user"
2658 has been removed from the ACL, and instead placed on the localuser router,
2659 using the cannot_route_message feature. This means that any verification
2660 failures that generate their own messages won't get overridden. Similarly,
2661 the "Unrouteable address" message that was in the ACL for unverifiable
2662 relay addresses has also been removed.
2664 56. Added hosts_avoid_esmtp to the smtp transport.
2666 57. The exicyclog script was not checking for the esoteric option
2667 CONFIGURE_FILE_USE_EUID in the Local/Makefile. It now does this, but it
2668 will work only if exicyclog is run under the appropriate euid.
2670 58. Following a discussion on the list, the rules by which Exim recognises line
2671 endings on incoming messages have been changed. The -dropcr and drop_cr
2672 options are now no-ops, retained only for backwards compatibility. The
2673 following line terminators are recognized: LF CRLF CR. However, special
2674 processing applies to CR:
2676 (i) The sequence CR . CR does *not* terminate an incoming SMTP message,
2677 nor a local message in the state where . is a terminator.
2679 (ii) If a bare CR is encountered in a header line, an extra space is added
2680 after the line terminator so as not to end the header. The reasoning
2681 behind this is that bare CRs in header lines are most likely either
2682 to be mistakes, or people trying to play silly games.
2684 59. The size of a message, as listed by "-bp" or in the Exim monitor window,
2685 was being incorrectly given as 18 bytes larger than it should have been.
2686 This is a VOB (very old bug).
2688 60. This may never have affected anything current, but just in case it has:
2689 When the local host is found other than at the start of a list of hosts,
2690 the local host, those with the same MX, and any that follow, are discarded.
2691 When the list in question was part of a longer list of hosts, the following
2692 hosts (not currently being processed) were also being discarded. This no
2693 longer happens. I'm not sure if this situation could ever has previously
2694 arisen.
2696 61. Added the "/MX" feature to lists of hosts in the manualroute and query
2697 program routers.
2699 62. Whenever Exim generates a new message, it now adds an Auto-Submitted:
2700 header. This is something that is recommended in a new Internet Draft, and
2701 is something that is documented as being done by Sendmail. There are two
2702 possible values. For messages generated by the autoreply transport, Exim
2703 adds:
2705 Auto-Submitted: auto-replied
2707 whereas for all other generated messages (e.g. bounces) it adds
2709 Auto-Submitted: auto-generated
2711 63. The "personal" condition in filters now includes a test for the
2712 Auto-Submitted: header. If it contains the string "auto-" the message it
2713 not considered personal.
2715 64. Added rcpt_include_affixes as a generic transport option.
2717 65. Added queue_only_override (default true).
2719 66. Added the syslog_duplication option.
2721 67. If what should have been the first header line of a message consisted of
2722 a space followed by a colon, Exim was mis-interpreting it as a header line.
2723 It isn't of course - it is syntactically invalid and should therefore be
2724 treated as the start of the message body. The misbehaviour could have
2725 caused a number of strange effects, including loss of data in subsequent
2726 header lines, and spool format errors.
2728 68. Formerly, the AUTH parameter on a MAIL command was trusted only if the
2729 client host had authenticated. This control can now be exercised by an ACL
2730 for more flexibility.
2732 69. By default, callouts do not happen when testing with -bh. There is now a
2733 variant, -bhc, which does actually run the callout code, including
2734 consulting and updating the callout cache.
2736 70. Added support for saslauthd authentication, courtesy of Alexander
2737 Sabourenkov.
2739 71. If statvfs() failed on the spool or log directories while checking their
2740 size for availability, Exim confusingly gave the error "space shortage".
2741 Furthermore, in debugging mode it crashed with a floating point exception.
2742 These checks are done if check_{spool,log}_{space,inodes} are set, and when
2743 an SMTP message arrives with SIZE= on the MAIL command. As this is a really
2744 serious problem, Exim now writes to the main and panic logs when this
2745 happens, with details of the failure. It then refuses to accept the
2746 incoming message, giving the message "spool directory problem" or "log
2747 directory problem" with a 421 code for SMTP messages.
2749 72. When Exim is about to re-exec itself, it ensures that the file descriptors
2750 0, 1, and 2 exist, because some OS complain for execs without them (see
2751 ChangeLog 4.05/30). If necessary, Exim opens /dev/null to use for these
2752 descriptors. However, the code omitted to check that the open succeeded,
2753 causing mysterious errors if for some reason the permissions on /dev/null
2754 got screwed. Now Exim writes a message to the main and panic logs, and
2755 bombs out if it can't open /dev/null.
2757 73. Re-vamped the way daemon_smtp_port, local_interfaces, and -oX work and
2758 interact so that it is all more flexible. It is supposed to remain
2759 backwards compatible. Also added extra_local_interfaces.
2761 74. Invalid data sent to a SPA (NTLM) server authenticator could cause the code
2762 to bomb out with an assertion failure - to the client this appears as a
2763 connection drop. This problem occurs in the part of the code that was taken
2764 from the Samba project. Fortunately, the assertion is in a very simple
2765 function, so I have fixed this by reproducing the function inline in the
2766 one place where it is called, and arranging for authentication to fail
2767 instead of killing the process with assert().
2769 75. The SPA client code was not working when the server requested OEM rather
2770 than Unicode encoding.
2772 76. Added code to make require_files with a specific uid setting more usable in
2773 the case where statting the file as root fails - usually a non-root-mounted
2774 NFS file system. When this happens and the failure is EACCES, Exim now
2775 forks a subprocess and does the per-uid checking as the relevant uid.
2777 77. Added process_log_path.
2779 78. If log_file_path was not explicitly set, a setting of check_log_space or
2780 check_log_inodes was ignored.
2782 79. If a space check for the spool or log partitions fails, the incident is now
2783 logged. Of course, in the latter case the data may get lost...
2785 80. Added the %p formatting code to string_format() so that it can be used to
2786 print addresses in debug_print(). Adjusted all the address printing in the
2787 debugging in store.c to use %p rather than %d.
2789 81. There was a concern that a line of code in smtp_in.c could overflow a
2790 buffer if a HELO/EHLO command was given followed by 500 or so spaces. As
2791 initially expressed, the concern was not well-founded, because trailing
2792 spaces are removed early. However, if the trailing spaces were followed by
2793 a NULL, they did not get removed, so the overflow was possible. Two fixes
2794 were applied:
2796 (a) I re-wrote the offending code in a cleaner fashion.
2797 (b) If an incoming SMTP command contains a NULL character, it is rejected
2798 as invalid.
2800 82. When Exim changes uid/gid to the Exim user at daemon start time, it now
2801 runs initgroups(), so that if the Exim user is in any additional groups,
2802 they will be used during message reception.
2805 Exim version 4.20
2806 -----------------
2808 The change log for 4.20 and earlier releases has been archived.
2810 ****