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