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