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