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