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