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