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