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