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