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