| 1 | $Cambridge: exim/doc/doc-txt/ChangeLog,v 1.282 2005/12/22 14:54:50 ph10 Exp $ |
| 2 | |
| 3 | Change log file for Exim from version 4.21 |
| 4 | ------------------------------------------- |
| 5 | |
| 6 | Exim version 4.61 |
| 7 | ----------------- |
| 8 | |
| 9 | PH/01 The code for finding all the local interface addresses on a FreeBSD |
| 10 | system running IPv6 was broken. This may well have applied to all BSD |
| 11 | systems, as well as to others that have similar system calls. The broken |
| 12 | code found IPv4 interfaces correctly, but gave incorrect values for the |
| 13 | IPv6 interfaces. In particular, ::1 was not found. The effect in Exim was |
| 14 | that it would not match correctly against @[] and not recognize the IPv6 |
| 15 | addresses as local. |
| 16 | |
| 17 | PH/02 The ipliteral router was not recognizing addresses of the form user@ |
| 18 | [ipv6:....] because it didn't know about the "ipv6:" prefix. |
| 19 | |
| 20 | PH/03 Added disable_ipv6. |
| 21 | |
| 22 | PH/04 Changed $reply_address to use the raw form of the headers instead of the |
| 23 | decoded form, because it is most often used to construct To: headers |
| 24 | lines in autoreplies, and the decoded form may well be syntactically |
| 25 | invalid. However, $reply_address has leading white space removed, and all |
| 26 | newlines turned into spaces so that the autoreply transport does not |
| 27 | grumble. |
| 28 | |
| 29 | PH/05 If group was specified without a user on a router, and no group or user |
| 30 | was specified on a transport, the group from the router was ignored. |
| 31 | |
| 32 | PH/06 Increased the number of ACL variables to 20 of each type, and arranged |
| 33 | for visible compile-time settings that can be used to change these |
| 34 | numbers, for those that want even more. Backwards compatibility with old |
| 35 | spool files has been maintained. However, going back to a previous Exim |
| 36 | release will lost any variables that are in spool files. |
| 37 | |
| 38 | PH/07 Two small changes when running in the test harness: increase delay when |
| 39 | passing a TCP/IP connection to a new process, in case the original |
| 40 | process has to generate a bounce, and remove special handling of |
| 41 | 127.0.0.2 (sic), which is no longer necessary. |
| 42 | |
| 43 | PH/08 Changed debug output of dbfn_open() flags from numbers to names, so as to |
| 44 | be the same on different OS. |
| 45 | |
| 46 | PH/09 Moved a debug statement in filter processing to avoid a race problem when |
| 47 | testing. |
| 48 | |
| 49 | JJ/01 exipick: fixed bug where -b (brief) output option showed "Vars:" |
| 50 | whether --show-vars was specified or not |
| 51 | |
| 52 | JJ/02 exipick: Added support for new ACL variable spool format introduced |
| 53 | in 4.61-PH/06 |
| 54 | |
| 55 | PH/10 Fixed another bug related to PH/04 above: if an incoming message had a |
| 56 | syntactically invalid From: or Reply-to: line, and a filter used this to |
| 57 | generate an autoreply, and therefore failed to obtain an address for the |
| 58 | autoreply, Exim could try to deliver to a non-existent relative file |
| 59 | name, causing unrelated and misleading errors. What now happens is that |
| 60 | it logs this as a hard delivery error, but does not attempt to create a |
| 61 | bounce message. |
| 62 | |
| 63 | PH/11 The exinext utility has a -C option for testing purposes, but although |
| 64 | the given file was scanned by exinext itself; it wasn't being passed on |
| 65 | when Exim was called. |
| 66 | |
| 67 | PH/12 In the smtp transport, treat an explicit ECONNRESET error the same as |
| 68 | an end-of-file indication when reading a command response. |
| 69 | |
| 70 | |
| 71 | Exim version 4.60 |
| 72 | ----------------- |
| 73 | |
| 74 | PH/01 Two changes to the default runtime configuration: |
| 75 | |
| 76 | (1) Move the checks for relay_from_hosts and authenticated clients from |
| 77 | after to before the (commented out) DNS black list checks. |
| 78 | |
| 79 | (2) Add control=submission to the relay_from_hosts and authenticated |
| 80 | clients checks, on the grounds that messages accepted by these |
| 81 | statements are most likely to be submissions. |
| 82 | |
| 83 | PH/02 Several tidies to the handling of ${prvs and ${prvscheck: |
| 84 | |
| 85 | (1) Generate an error if the third argument for the ${prvs expansion is |
| 86 | not a single digit. |
| 87 | |
| 88 | (2) Treat a missing third argument of ${prvscheck as if it were an empty |
| 89 | string. |
| 90 | |
| 91 | (3) Reset the variables that are obtained from the first argument of |
| 92 | ${prvscheck and used in the second argument before leaving the code, |
| 93 | because their memory is reclaimed, so using them afterwards may do |
| 94 | silly things. |
| 95 | |
| 96 | (4) Tidy up the code for expanding the arguments of ${prvscheck one by |
| 97 | one (it's much easier than Tom thought :-). |
| 98 | |
| 99 | (5) Because of (4), we can now allow for the use of $prvscheck_result |
| 100 | inside the third argument. |
| 101 | |
| 102 | PH/03 For some reason, the default setting of PATH when running a command from |
| 103 | a pipe transport was just "/usr/bin". I have changed it to |
| 104 | "/bin:/usr/bin". |
| 105 | |
| 106 | PH/04 SUPPORT_TRANSLATE_IP_ADDRESS and MOVE_FROZEN_MESSAGES did not cause |
| 107 | anything to be listed in the output from -bV. |
| 108 | |
| 109 | PH/05 When a filter generated an autoreply, the entire To: header line was |
| 110 | quoted in the delivery log line, like this: |
| 111 | |
| 112 | => >A.N.Other <ano@some.domain> <original@ddress> ... |
| 113 | |
| 114 | This has been changed so that it extracts the operative address. There |
| 115 | may be more than one such address. If so, they are comma-separated, like |
| 116 | this: |
| 117 | |
| 118 | => >ano@some.domain,ona@other.domain <original@ddress> ... |
| 119 | |
| 120 | PH/06 When a client host used a correct literal IP address in a HELO or EHLO |
| 121 | command, (for example, EHLO [1.2.3.4]) and the client's IP address was |
| 122 | not being looked up in the rDNS to get a host name, Exim was showing the |
| 123 | IP address twice in Received: lines, even though the IP addresses were |
| 124 | identical. For example: |
| 125 | |
| 126 | Received: from [1.2.3.4] (helo=[1.2.3.4]) |
| 127 | |
| 128 | However, if the real host name was known, it was omitting the HELO data |
| 129 | if it matched the actual IP address. This has been tidied up so that it |
| 130 | doesn't show the same IP address twice. |
| 131 | |
| 132 | PH/07 When both +timestamp and +memory debugging was on, the value given by |
| 133 | $tod_xxx expansions could be wrong, because the tod_stamp() function was |
| 134 | called by the debug printing, thereby overwriting the timestamp buffer. |
| 135 | Debugging no longer uses the tod_stamp() function when +timestamp is set. |
| 136 | |
| 137 | PH/08 When the original message was included in an autoreply transport, it |
| 138 | always said "this is a copy of the message, including all the headers", |
| 139 | even if body_only or headers_only was set. It now gives an appropriate |
| 140 | message. |
| 141 | |
| 142 | PH/09 Applied a patch from the Sieve maintainer which: |
| 143 | |
| 144 | o fixes some comments |
| 145 | o adds the (disabled) notify extension core |
| 146 | o adds some debug output for the result of if/elsif tests |
| 147 | o points to the current vacation draft in the documentation |
| 148 | and documents the missing references header update |
| 149 | |
| 150 | and most important: |
| 151 | |
| 152 | o fixes a bug in processing the envelope test (when testing |
| 153 | multiple envelope elements, the last element determinted the |
| 154 | result) |
| 155 | |
| 156 | PH/10 Exim was violating RFC 3834 ("Recommendations for Automatic Responses to |
| 157 | Electronic Mail") by including: |
| 158 | |
| 159 | Auto-submitted: auto-generated |
| 160 | |
| 161 | in the messages that it generates (bounce messages and others, such as |
| 162 | warnings). In the case of bounce messages for non-SMTP mesages, there was |
| 163 | also a typo: it was using "Auto_submitted" (underscore instead of |
| 164 | hyphen). Since every message generated by Exim is necessarily in response |
| 165 | to another message, thes have all been changed to: |
| 166 | |
| 167 | Auto-Submitted: auto-replied |
| 168 | |
| 169 | in accordance with these statements in the RFC: |
| 170 | |
| 171 | The auto-replied keyword: |
| 172 | |
| 173 | - SHOULD be used on messages sent in direct response to another |
| 174 | message by an automatic process, |
| 175 | |
| 176 | - MUST NOT be used on manually-generated messages, |
| 177 | |
| 178 | - MAY be used on Delivery Status Notifications (DSNs) and Message |
| 179 | Disposition Notifications (MDNs), |
| 180 | |
| 181 | - MUST NOT be used on messages generated by automatic or periodic |
| 182 | processes, except for messages which are automatic responses to |
| 183 | other messages. |
| 184 | |
| 185 | PH/11 Added "${if def:sender_address {(envelope-from <$sender_address>)\n\t}}" |
| 186 | to the default Received: header definition. |
| 187 | |
| 188 | PH/12 Added log selector acl_warn_skipped (default on). |
| 189 | |
| 190 | PH/13 After a successful wildlsearch lookup, discard the values of numeric |
| 191 | variables because (a) they are in the wrong storage pool and (b) even if |
| 192 | they were copied, it wouldn't work properly because of the caching. |
| 193 | |
| 194 | PH/14 Add check_rfc2047_length to disable enforcement of RFC 2047 length |
| 195 | checking when decoding. Apparently there are clients that generate |
| 196 | overlong encoded strings. Why am I not surprised? |
| 197 | |
| 198 | PH/15 If the first argument of "${if match_address" was not empty, but did not |
| 199 | contain an "@" character, Exim crashed. Now it writes a panic log message |
| 200 | and treats the condition as false. |
| 201 | |
| 202 | PH/16 In autoreply, treat an empty string for "once" the same as unset. |
| 203 | |
| 204 | PH/17 A further patch from the Sieve maintainer: "Introduce the new Sieve |
| 205 | extension "envelope-auth". The code is finished and in agreement with |
| 206 | other implementations, but there is no documentation so far and in fact, |
| 207 | nobody wrote the draft yet. This extension is currently #undef'ed, thus |
| 208 | not changing the active code. |
| 209 | |
| 210 | Print executed "if" and "elsif" statements when debugging is used. This |
| 211 | helps a great deal to understand what a filter does. |
| 212 | |
| 213 | Document more things not specified clearly in RFC3028. I had all this |
| 214 | sorted out, when out of a sudden new issues came to my mind. Oops." |
| 215 | |
| 216 | PH/18 Exim was not recognizing the "net-" search type prefix in match_ip lists |
| 217 | (Bugzilla #53). |
| 218 | |
| 219 | PH/19 Exim expands the IPv6 address given to -bh to its full non-abbreviated |
| 220 | canonical form (as documented). However, after a host name lookup from |
| 221 | the IP address, check_host() was doing a simple string comparison with |
| 222 | addresses acquired from the DNS when checking that the found name did |
| 223 | have the original IP as one of its addresses. Since any found IPv6 |
| 224 | addresses are likely to be in abbreviated form, the comparison could |
| 225 | fail. Luckily, there already exists a function for doing the comparison |
| 226 | by converting both addresses to binary, so now that is used instead of |
| 227 | the text comparison. |
| 228 | |
| 229 | PH/20 There was another similar case to PH/19, when a complete host name was |
| 230 | given in a host list; looking up its IP address could give an abbreviated |
| 231 | form, whereas the current host's name might or might not be abbreviated. |
| 232 | The same fix has been applied. |
| 233 | |
| 234 | |
| 235 | Exim version 4.54 |
| 236 | ----------------- |
| 237 | |
| 238 | PH/01 The ${base62: operator adjusted itself to base 36 when BASE_62 was |
| 239 | set to 36 (for Darwin and Cygwin), but the ${base62d: operator did not. |
| 240 | It now does. |
| 241 | |
| 242 | PH/02 Two minor problems detected in Cygwin: the os.{c,h} files had lost */ on |
| 243 | the CVS lines, and there was a missing #if HAVE_IPV6 in host.c. |
| 244 | |
| 245 | PH/03 Typo: missing ".o" in src/pcre/Makefile. |
| 246 | |
| 247 | PH/04 Tighten up "personal" tests: Instead of testing for any "List-" |
| 248 | header line, restrict the check to what is listed in RFCs 2369 and 2929. |
| 249 | Also, for "Auto-Submitted", treat anything other than "no" as |
| 250 | non-personal, in accordance with RFC 3834. (Previously it treated |
| 251 | anything starting "auto-" as non-personal.) |
| 252 | |
| 253 | TF/01 The control=submission/name=... option had a problem with syntax |
| 254 | errors if the name included a slash character. The /name= option |
| 255 | now slurps the rest of the string, so it can include any characters |
| 256 | but it must come last in the list of options (after /sender_retain |
| 257 | or /domain=). |
| 258 | |
| 259 | PH/05 Some modifications to the interface to the fake nameserver for the new |
| 260 | testing suite. |
| 261 | |
| 262 | |
| 263 | |
| 264 | Exim version 4.53 |
| 265 | ----------------- |
| 266 | |
| 267 | TK/01 Added the "success_on_redirect" address verification option. See |
| 268 | NewStuff for rationale and an example. |
| 269 | |
| 270 | PH/01 Added support for SQLite, basic code supplied by David Woodhouse. |
| 271 | |
| 272 | PH/02 Patch to exigrep to allow it to work on syslog lines. |
| 273 | |
| 274 | PH/03 When creating an mbox file for a virus/spam scan, use fseek() instead of |
| 275 | fread() to skip over the body file's header line, because in Cygwin the |
| 276 | header line is locked and is inaccessible. |
| 277 | |
| 278 | PH/04 Added $message_exim_id, ultimately to replace $message_id (they will both |
| 279 | co-exist for some time) to make it clear that it is the Exim ID that is |
| 280 | referenced, not the Message-ID: header line. |
| 281 | |
| 282 | PH/05 Replaced all Tom's calls to snprintf() with calls to the internal |
| 283 | string_format() function, because snprintf() does not exist on all |
| 284 | operating systems. |
| 285 | |
| 286 | PH/06 The use of forbid_filter_existstest now also locks out the use of the |
| 287 | ${stat: expansion item. |
| 288 | |
| 289 | PH/07 Changed "SMTP protocol violation: synchronization error" into "SMTP |
| 290 | protocol synchronization error", to keep the pedants happy. |
| 291 | |
| 292 | PH/08 Arrange for USE_INET_NTOA_FIX to be set in config.h for AIX systems as |
| 293 | well as for IRIX systems, when gcc is being used. See the host.c source |
| 294 | file for comments. |
| 295 | |
| 296 | PH/09 Installed latest Cygwin configuration files from the Cygwin maintainer. |
| 297 | |
| 298 | PH/10 Named domain lists were not working if used in a queue_smtp_domains |
| 299 | setting. |
| 300 | |
| 301 | PH/11 Added support for the IGNOREQUOTA extension to LMTP, both to the lmtp |
| 302 | transport and to the smtp transport in LMTP mode. |
| 303 | |
| 304 | TK/02 Remove one case of BASE64 error detection FTTB (undocumented anyway). |
| 305 | |
| 306 | PH/12 There was a missing call to search_tidyup() before the fork() in rda.c to |
| 307 | run a filter in a subprocess. This could lead to confusion in subsequent |
| 308 | lookups in the parent process. There should also be a search_tidyup() at |
| 309 | the end of the subprocess. |
| 310 | |
| 311 | PH/13 Previously, if "verify = helo" was set in an ACL, the condition was true |
| 312 | only if the host matched helo_try_verify_hosts, which caused the |
| 313 | verification to occur when the EHLO/HELO command was issued. The ACL just |
| 314 | tested the remembered result. Now, if a previous verification attempt has |
| 315 | not happened, "verify = helo" does it there and then. |
| 316 | |
| 317 | JJ/01 exipick: added $message_exim_id variable (see 4.53-PH/04) |
| 318 | |
| 319 | TK/03 Fix log output including CR from clamd. |
| 320 | |
| 321 | PH/14 A reference to $reply_address when Reply-to: was empty and From: did not |
| 322 | exist provoked a memory error which could cause a segfault. |
| 323 | |
| 324 | PH/15 Installed PCRE 6.2 |
| 325 | |
| 326 | PH/17 Defined BIND_8_COMPAT in the Darwin os.h file. |
| 327 | |
| 328 | PH/18 Reversed 4.52/PH/17 because the HP-UX user found it wasn't the cause |
| 329 | of the problem. Specifically, suggested +O2 rather than +O1 for the |
| 330 | HP-UX compiler. |
| 331 | |
| 332 | PH/19 Added sqlite_lock_timeout option (David Woodhouse's patch). |
| 333 | |
| 334 | PH/20 If a delivery was routed to a non-standard port by means of an SRV |
| 335 | record, the port was not correctly logged when the outgoing_port log |
| 336 | selector was set (it logged the transort's default port). |
| 337 | |
| 338 | PH/21 Added support for host-specific ports to manualroute, queryprogram, |
| 339 | fallback_hosts, and "hosts" in the smtp transport. |
| 340 | |
| 341 | PH/22 If the log selector "outgoing_port" is set, the port is now also given on |
| 342 | host errors such as "Connection refused". |
| 343 | |
| 344 | PH/23 Applied a patch to fix problems with exim-4.52 while doing radius |
| 345 | authentication with radiusclient 0.4.9: |
| 346 | |
| 347 | - Error returned from rc_read_config was caught wrongly |
| 348 | - Username/password not passed on to radius server due to wrong length. |
| 349 | |
| 350 | The presumption is that some radiusclient API changes for 4.51/PH/17 |
| 351 | were not taken care of correctly. The code is still untested by me (my |
| 352 | Linux distribution still has 0.3.2 of radiusclient), but it was |
| 353 | contributed by a Radius user. |
| 354 | |
| 355 | PH/24 When doing a callout, the value of $domain wasn't set correctly when |
| 356 | expanding the "port" option of the smtp transport. |
| 357 | |
| 358 | TK/04 MIME ACL: Fix buffer underrun that occurs when EOF condition is met |
| 359 | while reading a MIME header. Thanks to Tom Hughes for a patch. |
| 360 | |
| 361 | PH/24 Include config.h inside local_scan.h so that configuration settings are |
| 362 | available. |
| 363 | |
| 364 | PH/25 Make $smtp_command_argument available after all SMTP commands. This means |
| 365 | that in an ACL for RCPT (for example), you can examine exactly what was |
| 366 | received. |
| 367 | |
| 368 | PH/26 Exim was recognizing IPv6 addresses of the form [IPv6:....] in EHLO |
| 369 | commands, but it was not correctly comparing the address with the actual |
| 370 | client host address. Thus, it would show the EHLO address in Received: |
| 371 | header lines when this was not necessary. |
| 372 | |
| 373 | PH/27 Added the % operator to ${eval:}. |
| 374 | |
| 375 | PH/28 Exim tries to create and chdir to its spool directory when it starts; |
| 376 | it should be ignoring failures (because with -C, for example, it has lost |
| 377 | privilege). It wasn't ignoring creation failures other than "already |
| 378 | exists". |
| 379 | |
| 380 | PH/29 Added "crypteq" to the list of supported features that Exim outputs when |
| 381 | -bV or -d is used. |
| 382 | |
| 383 | PH/30 Fixed (presumably very longstanding) bug in exim_dbmbuild: if it failed |
| 384 | because an input line was too long, either on its own, or by virtue of |
| 385 | too many continuations, the temporary file was not being removed, and the |
| 386 | return code was incorrect. |
| 387 | |
| 388 | PH/31 Missing "BOOL" in function definition in filtertest.c. |
| 389 | |
| 390 | PH/32 Applied Sieve patches from the maintainer. |
| 391 | |
| 392 | TK/05 Domainkeys: Accomodate for a minor API change in libdomainkeys 0.67. |
| 393 | |
| 394 | PH/33 Added "verify = not_blind". |
| 395 | |
| 396 | PH/34 There are settings for CHOWN_COMMAND and MV_COMMAND that can be used in |
| 397 | Local/Makefile (with some defaults set). These are used in built scripts |
| 398 | such as exicyclog, but they have never been used in the exim_install |
| 399 | script (though there are many overriding facilities there). I have |
| 400 | arranged that the exim_install script now takes note of these two |
| 401 | settings. |
| 402 | |
| 403 | PH/35 Installed configuration files for Dragonfly. |
| 404 | |
| 405 | PH/36 When a locally submitted message by a trusted user did not contain a |
| 406 | From: header, and the sender address was obtained from -f or from an SMTP |
| 407 | MAIL command, and the trusted user did not use -F to supply a sender |
| 408 | name, $originator_name was incorrectly used when constructing a From: |
| 409 | header. Furthermore, $originator_name was used for submission mode |
| 410 | messages from external hosts without From: headers in a similar way, |
| 411 | which is clearly wrong. |
| 412 | |
| 413 | PH/37 Added control=suppress_local_fixups. |
| 414 | |
| 415 | PH/38 When log_selector = +received_sender was set, and the addition of the |
| 416 | sender made the log line's construction buffer exactly full, or one byte |
| 417 | less than full, an overflow happened when the terminating "\n" was |
| 418 | subsequently added. |
| 419 | |
| 420 | PH/39 Added a new log selector, "unknown_in_list", which provokes a log entry |
| 421 | when the result of a list match is failure because a DNS lookup failed. |
| 422 | |
| 423 | PH/40 RM_COMMAND is now used in the building process. |
| 424 | |
| 425 | PH/41 Added a "distclean" target to the top-level Makefile; it deletes all |
| 426 | the "build-* directories that it finds. |
| 427 | |
| 428 | PH/42 (But a TF fix): In a domain list, Exim incorrectly matched @[] if the IP |
| 429 | address in a domain literal was a prefix of an interface address. |
| 430 | |
| 431 | PH/43 (Again a TF fix): In the dnslookup router, do not apply widen_domains |
| 432 | when verifying a sender address, unless rewrite_headers is false. |
| 433 | |
| 434 | PH/44 Wrote a long comment about why errors_to addresses are verified as |
| 435 | recipients, not senders. |
| 436 | |
| 437 | TF/01 Add missing LIBS=-lm to OS/Makefile-OpenBSD which was overlooked when |
| 438 | the ratelimit ACL was added. |
| 439 | |
| 440 | PH/45 Added $smtp_command for the full command (cf $smtp_command_argument). |
| 441 | |
| 442 | PH/46 Added extra information about PostgreSQL errors to the error string. |
| 443 | |
| 444 | PH/47 Added an interface to a fake DNS resolver for use by the new test suite, |
| 445 | avoiding the need to install special zones in a real server. This is |
| 446 | backwards compatible; if it can't find the fake resolver, it drops back. |
| 447 | Thus, both old and new test suites can be run. |
| 448 | |
| 449 | TF/02 Added util/ratelimit.pl |
| 450 | |
| 451 | TF/03 Minor fix to the ratelimit code to improve its behaviour in case the |
| 452 | clock is set back in time. |
| 453 | |
| 454 | TF/04 Fix the ratelimit support in exim_fixdb. Patch provided by Brian |
| 455 | Candler <B.Candler@pobox.com>. |
| 456 | |
| 457 | TF/05 The fix for PH/43 was not completely correct; widen_domains is always |
| 458 | OK for addresses that are the result of redirections. |
| 459 | |
| 460 | PH/48 A number of further additions for the benefit of the new test suite, |
| 461 | including a fake gethostbyname() that interfaces to the fake DNS resolver |
| 462 | (see PH/47 above). |
| 463 | |
| 464 | TF/06 The fix for widen_domains has also been applied to qualify_single and |
| 465 | search_parents which are the other dnslookup options that can cause |
| 466 | header rewrites. |
| 467 | |
| 468 | PH/49 Michael Haardt's randomized retrying, but as a separate retry parameter |
| 469 | type ("H"). |
| 470 | |
| 471 | PH/50 Make never_users, trusted_users, admin_groups, trusted_groups expandable. |
| 472 | |
| 473 | TF/07 Exim produced the error message "an SRV record indicated no SMTP |
| 474 | service" if it encountered an MX record with an empty target hostname. |
| 475 | The message is now "an MX or SRV record indicated no SMTP service". |
| 476 | |
| 477 | TF/08 Change PH/13 introduced the possibility that verify=helo may defer, |
| 478 | if the DNS of the sending site is misconfigured. This is quite a |
| 479 | common situation. This change restores the behaviour of treating a |
| 480 | helo verification defer as a failure. |
| 481 | |
| 482 | PH/51 If self=fail was set on a router, the bounce message did not include the |
| 483 | actual error message. |
| 484 | |
| 485 | |
| 486 | Exim version 4.52 |
| 487 | ----------------- |
| 488 | |
| 489 | TF/01 Added support for Client SMTP Authorization. See NewStuff for details. |
| 490 | |
| 491 | PH/01 When a transport filter timed out in a pipe delivery, and the pipe |
| 492 | command itself ended in error, the underlying message about the transport |
| 493 | filter timeout was being overwritten with the pipe command error. Now the |
| 494 | underlying error message should be appended to the second error message. |
| 495 | |
| 496 | TK/01 Fix poll() being unavailable on Mac OSX 10.2. |
| 497 | |
| 498 | PH/02 Reduce the amount of output that "make" produces by default. Full output |
| 499 | can still be requested. |
| 500 | |
| 501 | PH/03 The warning log line about a condition test deferring for a "warn" verb |
| 502 | was being output only once per connection, rather than after each |
| 503 | occurrence (because it was using the same function as for successful |
| 504 | "warn" verbs). This seems wrong, so I have changed it. |
| 505 | |
| 506 | TF/02 Two buglets in acl.c which caused Exim to read a few bytes of memory that |
| 507 | it should not have, which might have caused a crash in the right |
| 508 | circumstances, but probably never did. |
| 509 | |
| 510 | PH/04 Installed a modified version of Tony Finch's patch to make submission |
| 511 | mode fix the return path as well as the Sender: header line, and to |
| 512 | add a /name= option so that you can make the user's friendly name appear |
| 513 | in the header line. |
| 514 | |
| 515 | TF/03 Added the control = fakedefer ACL modifier. |
| 516 | |
| 517 | TF/04 Added the ratelimit ACL condition. See NewStuff for details. Thanks to |
| 518 | Mark Lowes for thorough testing. |
| 519 | |
| 520 | TK/02 Rewrote SPF support to work with libspf2 versions >1.2.0. |
| 521 | |
| 522 | TK/03 Merged latest SRS patch from Miles Wilton. |
| 523 | |
| 524 | PH/05 There's a shambles in IRIX6 - it defines EX_OK in unistd.h which conflicts |
| 525 | with the definition in sysexits.h (which is #included earlier). |
| 526 | Fortunately, Exim does not actually use EX_OK. The code used to try to |
| 527 | preserve the sysexits.h value, by assumimg that macro definitions were |
| 528 | scanned for macro replacements. I have been disabused of this notion, |
| 529 | so now the code just undefines EX_OK before #including unistd.h. |
| 530 | |
| 531 | PH/06 There is a timeout for writing blocks of data, set by, e.g. data_timeout |
| 532 | in the smtp transport. When a block could not be written in a single |
| 533 | write() function, the timeout was being re-applied to each part-write. |
| 534 | This seems wrong - if the receiver was accepting one byte at a time it |
| 535 | would take for ever. The timeout is now adjusted when this happens. It |
| 536 | doesn't have to be particularly precise. |
| 537 | |
| 538 | TK/04 Added simple SPF lookup method in EXPERIMENTAL_SPF. See NewStuff for |
| 539 | details. Thanks to Chris Webb <chris@arachsys.com> for the patch! |
| 540 | |
| 541 | PH/07 Added "fullpostmaster" verify option, which does a check to <postmaster> |
| 542 | without a domain if the check to <postmaster@domain> fails. |
| 543 | |
| 544 | SC/01 Eximstats: added -xls and the ability to specify output files |
| 545 | (patch written by Frank Heydlauf). |
| 546 | |
| 547 | SC/02 Eximstats: use FileHandles for outputing results. |
| 548 | |
| 549 | SC/03 Eximstats: allow any combination of xls, txt, and html output. |
| 550 | |
| 551 | SC/04 Eximstats: fixed display of large numbers with -nvr option |
| 552 | |
| 553 | SC/05 Eximstats: fixed merging of reports with empty tables. |
| 554 | |
| 555 | SC/06 Eximstats: added the -include_original_destination flag |
| 556 | |
| 557 | SC/07 Eximstats: removed tabs and trailing whitespace. |
| 558 | |
| 559 | TK/05 Malware: Improve on aveserver error handling. Patch from Alex Miller. |
| 560 | |
| 561 | TK/06 MBOX spool code: Add real "From " MBOX separator line |
| 562 | so the .eml file is really in mbox format (even though |
| 563 | most programs do not really care). Patch from Alex Miller. |
| 564 | |
| 565 | TK/07 MBOX spool code: Add X-Envelope-From: and X-Envelope-To: headers. |
| 566 | The latter is generated from $received_to and is only set if the |
| 567 | message has one envelope recipient. SA can use these headers, |
| 568 | obviously out-of-the-box. Patch from Alex Miller. |
| 569 | |
| 570 | PH/08 The ${def test on a variable was returning false if the variable's |
| 571 | value was "0", contrary to what the specification has always said! |
| 572 | The result should be true unless the variable is empty. |
| 573 | |
| 574 | PH/09 The syntax error of a character other than { following "${if |
| 575 | def:variable_name" (after optional whitespace) was not being diagnosed. |
| 576 | An expansion such as ${if def:sender_ident:{xxx}{yyy}} in which an |
| 577 | accidental colon was present, for example, could give incorrect results. |
| 578 | |
| 579 | PH/10 Tidied the code in a number of places where the st_size field of a stat() |
| 580 | result is used (not including appendfile, where other changes are about |
| 581 | to be made). |
| 582 | |
| 583 | PH/11 Upgraded appendfile so that quotas larger than 2G are now supported. |
| 584 | This involved changing a lot of size variables from int to off_t. It |
| 585 | should work with maildirs and everything. |
| 586 | |
| 587 | TK/08 Apply fix provided by Michael Haardt to prevent deadlock in case of |
| 588 | spamd dying while we are connected to it. |
| 589 | |
| 590 | TF/05 Fixed a ${extract error message typo reported by Jeremy Harris |
| 591 | <jgh@wizmail.org> |
| 592 | |
| 593 | PH/12 Applied Alex Kiernan's patch for the API change for the error callback |
| 594 | function for BDB 4.3. |
| 595 | |
| 596 | PH/13 Changed auto_thaw such that it does not apply to bounce messages. |
| 597 | |
| 598 | PH/14 Imported PCRE 6.0; this was more than just a trivial operation because |
| 599 | the sources for PCRE have been re-arranged and more files are now |
| 600 | involved. |
| 601 | |
| 602 | PH/15 The code I had for printing potentially long long variables in PH/11 |
| 603 | above was not the best (it lost precision). The length of off_t variables |
| 604 | is now inspected at build time, and an appropriate printing format (%ld |
| 605 | or %lld) is chosen and #defined by OFF_T_FMT. We also define LONGLONG_T |
| 606 | to be "long long int" or "long int". This is needed for the internal |
| 607 | formatting function string_vformat(). |
| 608 | |
| 609 | PH/16 Applied Matthew Newton's patch to exicyclog: "If log_file_path is set in |
| 610 | the configuration file to be ":syslog", then the script "guesses" where |
| 611 | the logs files are, rather than using the compiled in default. In our |
| 612 | case the guess is not the same as the compiled default, so the script |
| 613 | suddenly stopped working when I started to use syslog. The patch checks |
| 614 | to see if log_file_path is "". If so, it attempts to read it from exim |
| 615 | with no configuration file to get the compiled in version, before it |
| 616 | falls back to the previous guessing code." |
| 617 | |
| 618 | TK/09 Added "prvs" and "prvscheck" expansion items. These help a lot with |
| 619 | implementing BATV in an Exim configuration. See NewStuff for the gory |
| 620 | details. |
| 621 | |
| 622 | PH/17 Applied Michael Haardt's patch for HP-UX, affecting only the os.h and |
| 623 | Makefile that are specific to HP-UX. |
| 624 | |
| 625 | PH/18 If the "use_postmaster" option was set for a recipient callout together |
| 626 | with the "random" option, the postmaster address was used as the MAIL |
| 627 | FROM address for the random test, but not for the subsequent recipient |
| 628 | test. It is now used for both. |
| 629 | |
| 630 | PH/19 Applied Michael Haardt's patch to update Sieve to RFC3028bis. "The |
| 631 | patch removes a few documentation additions to RFC 3028, because the |
| 632 | latest draft now contains them. It adds the new en;ascii-case comparator |
| 633 | and a new error check for 8bit text in MIME parts. Comparator and |
| 634 | require names are now matched exactly. I enabled the subaddress |
| 635 | extension, but it is not well tested yet (read: it works for me)." |
| 636 | |
| 637 | PH/20 Added macros for time_t as for off_t (see PH/15 above) and used them to |
| 638 | rework some of the code of TK/09 above to avoid the hardwired use of |
| 639 | "%lld" and "long long". Replaced the call to snprintf() with a call to |
| 640 | string_vformat(). |
| 641 | |
| 642 | PH/21 Added some other messages to those in 4.51/PH/42, namely "All relevant MX |
| 643 | records point to non-existent hosts", "retry timeout exceeded", and |
| 644 | "retry time not reached for any host after a long failure period". |
| 645 | |
| 646 | PH/22 Fixed some oversights/typos causing bugs when Exim is compiled with |
| 647 | experimental DomainKeys support: |
| 648 | |
| 649 | (1) The filter variables $n0-$n9 and $sn0-$sn9 were broken. |
| 650 | (2) On an error such as an illegally used "control", the wrong name for |
| 651 | the control was given. |
| 652 | |
| 653 | These problems did NOT occur unless DomainKeys support was compiled. |
| 654 | |
| 655 | PH/23 Added daemon_startup_retries and daemon_startup_sleep. |
| 656 | |
| 657 | PH/24 Added ${if match_ip condition. |
| 658 | |
| 659 | PH/25 Put debug statements on either side of calls to EXIM_DBOPEN() for hints |
| 660 | databases so that it will be absolutely obvious if a crash occurs in the |
| 661 | DB library. This is a regular occurrence (often caused by mis-matched |
| 662 | db.h files). |
| 663 | |
| 664 | PH/26 Insert a lot of missing (void) casts for functions such as chown(), |
| 665 | chmod(), fcntl(), sscanf(), and other functions from stdio.h. These were |
| 666 | picked up on a user's system that detects such things. There doesn't seem |
| 667 | to be a gcc warning option for this - only an attribute that has to be |
| 668 | put on the function's prototype. It seems that in Fedora Core 4 they have |
| 669 | set this on a number of new functions. No doubt there will be more in due |
| 670 | course. |
| 671 | |
| 672 | PH/27 If a dnslookup or manualroute router is set with verify=only, it need not |
| 673 | specify a transport. However, if an address that was verified by such a |
| 674 | router was the subject of a callout, Exim crashed because it tried to |
| 675 | read the rcpt_include_affixes from the non-existent transport. Now it |
| 676 | just assumes that the setting of that option is false. This bug was |
| 677 | introduced by 4.51/PH/31. |
| 678 | |
| 679 | PH/28 Changed -d+all to exclude +memory, because that information is very |
| 680 | rarely of interest, but it makes the output a lot bigger. People tend to |
| 681 | do -d+all out of habit. |
| 682 | |
| 683 | PH/29 Removed support for the Linux-libc5 build, as it is obsolete and the |
| 684 | code in os-type was giving problems when libc.so lives in lib64, like on |
| 685 | x86_64 Fedora Core. |
| 686 | |
| 687 | PH/30 Exim's DNS code uses the original T_xxx names for DNS record times. These |
| 688 | aren't the modern standard, and it seems that some systems' include files |
| 689 | don't always have them. Exim was already checking for some of the newer |
| 690 | ones like T_AAAA, and defining it itself. I've added checks for all the |
| 691 | record types that Exim uses. |
| 692 | |
| 693 | PH/31 When using GnuTLS, if the parameters cache file did not exist, Exim was |
| 694 | not automatically generating a new one, as it is supposed to. This |
| 695 | prevented TLS from working. If the file did exist, but contained invalid |
| 696 | data, a new version was generated, as expected. It was only the case of a |
| 697 | non-existent file that was broken. |
| 698 | |
| 699 | TK/10 Domainkeys: Fix a bug in verification that caused a crash in conjunction |
| 700 | with a change in libdomainkeys > 0.64. |
| 701 | |
| 702 | TK/11 Domainkeys: Change the logic how the "testing" policy flag is retrieved |
| 703 | from DNS. If the selector record carries the flag, it now has |
| 704 | precedence over the domain-wide flag. |
| 705 | |
| 706 | TK/12 Cleared some compiler warnings related to SPF, SRS and DK code. |
| 707 | |
| 708 | PH/32 In mua_wrapper mode, if an smtp transport configuration error (such as |
| 709 | the use of a port name that isn't defined in /etc/services) occurred, the |
| 710 | message was deferred as in a normal delivery, and thus remained on the |
| 711 | spool, instead of being failed because of the mua_wrapper setting. This |
| 712 | is now fixed, and I tidied up some of the mua_wrapper messages at the |
| 713 | same time. |
| 714 | |
| 715 | SC/08 Eximstats: whilst parsing the mainlog(s), store information about |
| 716 | the messages in a hash of arrays rather than using individual hashes. |
| 717 | This is a bit cleaner and results in dramatic memory savings, albeit |
| 718 | at a slight CPU cost. |
| 719 | |
| 720 | SC/09 Eximstats: added the -show_rt<list> and the -show_dt<list> flags |
| 721 | as requested by Marc Sherman. |
| 722 | |
| 723 | SC/10 Eximstats: added histograms for user specified patterns as requested |
| 724 | by Marc Sherman. |
| 725 | |
| 726 | SC/11 Eximstats: v1.43 - bugfix for pattern histograms with -h0 specified. |
| 727 | |
| 728 | PH/33 Patch from the Cygwin maintainer to add "b" to all occurences of |
| 729 | fopen() in the content-scanning modules that did not already have it. |
| 730 | |
| 731 | |
| 732 | Exim version 4.51 |
| 733 | ----------------- |
| 734 | |
| 735 | TK/01 Added Yahoo DomainKeys support via libdomainkeys. See |
| 736 | doc/experimental-spec.txt for details. (http://domainkeys.sf.net) |
| 737 | |
| 738 | TK/02 Fix ACL "control" statement not being available in MIME ACL. |
| 739 | |
| 740 | TK/03 Fix ACL "regex" condition not being available in MIME ACL. |
| 741 | |
| 742 | PH/01 Installed a patch from the Sieve maintainer that allows -bf to be used |
| 743 | to test Sieve filters that use "vacation". |
| 744 | |
| 745 | PH/02 Installed a slightly modified version of Nikos Mavrogiannopoulos' patch |
| 746 | that changes the way the GnuTLS parameters are stored in the cache file. |
| 747 | The new format can be generated externally. For backward compatibility, |
| 748 | if the data in the cache doesn't make sense, Exim assumes it has read an |
| 749 | old-format file, and it generates new data and writes a new file. This |
| 750 | means that you can't go back to an older release without removing the |
| 751 | file. |
| 752 | |
| 753 | PH/03 A redirect router that has both "unseen" and "one_time" set does not |
| 754 | work if there are any delivery delays because "one_time" forces the |
| 755 | parent to be marked "delivered", so its unseen clone is never tried |
| 756 | again. For this reason, Exim now forbids the simultaneous setting of |
| 757 | these two options. |
| 758 | |
| 759 | PH/04 Change 4.11/85 fixed an obscure bug concerned with addresses that are |
| 760 | redirected to themselves ("homonym" addresses). Read the long ChangeLog |
| 761 | entry if you want to know the details. The fix, however, neglected to |
| 762 | consider the case when local delivery batching is involved. The test for |
| 763 | "previously delivered" was not happening when checking to see if an |
| 764 | address could be batched with a previous (undelivered) one; under |
| 765 | certain circumstances this could lead to multiple deliveries to the same |
| 766 | address. |
| 767 | |
| 768 | PH/05 Renamed the macro SOCKLEN_T as EXIM_SOCKLEN_T because AIX uses SOCKLEN_T |
| 769 | in its include files, and this causes problems building Exim. |
| 770 | |
| 771 | PH/06 A number of "verify =" ACL conditions have no options (e.g. verify = |
| 772 | header_syntax) but Exim was just ignoring anything given after a slash. |
| 773 | In particular, this caused confusion with an attempt to use "verify = |
| 774 | reverse_host_lookup/defer_ok". An error is now given when options are |
| 775 | supplied for verify items that do not have them. (Maybe reverse_host_ |
| 776 | lookup should have a defer_ok option, but that's a different point.) |
| 777 | |
| 778 | PH/07 Increase the size of the buffer for incoming SMTP commands from 512 (as |
| 779 | defined by RFC 821) to 2048, because there were problems with some AUTH |
| 780 | commands, and RFC 1869 says the size should be increased for extended |
| 781 | SMTP commands that take arguments. |
| 782 | |
| 783 | PH/08 Added ${dlfunc dynamically loaded function for expansion (code from Tony |
| 784 | Finch). |
| 785 | |
| 786 | PH/09 Previously, an attempt to use ${perl when it wasn't compiled gave an |
| 787 | "unknown" error; now it says that the functionality isn't in the binary. |
| 788 | |
| 789 | PH/10 Added a nasty fudge to try to recognize and flatten LDAP passwords in |
| 790 | an address' error message when a string expansion fails (syntax or |
| 791 | whatever). Otherwise the password may appear in the log. Following change |
| 792 | PH/42 below, there is no longer a chance of it appearing in a bounce |
| 793 | message. |
| 794 | |
| 795 | PH/11 Installed exipick version 20050225.0 from John Jetmore. |
| 796 | |
| 797 | PH/12 If the last host in a fallback_hosts list was multihomed, only the first |
| 798 | of its addresses was ever tried. (Bugzilla bug #2.) |
| 799 | |
| 800 | PH/13 If "headers_add" in a transport didn't end in a newline, Exim printed |
| 801 | the result incorrectly in the debug output. (It correctly added a newline |
| 802 | to what was transported.) |
| 803 | |
| 804 | TF/01 Added $received_time. |
| 805 | |
| 806 | PH/14 Modified the default configuration to add an acl_smtp_data ACL, with |
| 807 | commented out examples of how to interface to a virus scanner and to |
| 808 | SpamAssassin. Also added commented examples of av_scanner and |
| 809 | spamd_address settings. |
| 810 | |
| 811 | PH/15 Further to TK/02 and TK/03 above, tidied up the tables of what conditions |
| 812 | and controls are allowed in which ACLs. There were a couple of minor |
| 813 | errors. Some of the entries in the conditions table (which is a table of |
| 814 | where they are NOT allowed) were getting very unwieldy; rewrote them as a |
| 815 | negation of where the condition IS allowed. |
| 816 | |
| 817 | PH/16 Installed updated OS/os.c-cygwin from the Cygwin maintainer. |
| 818 | |
| 819 | PH/17 The API for radiusclient changed at release 0.4.0. Unfortunately, the |
| 820 | header file does not have a version number, so I've had to invent a new |
| 821 | value for RADIUS_LIB_TYPE, namely "RADIUSCLIENTNEW" to request the new |
| 822 | API. The code is untested by me (my Linux distribution still has 0.3.2 of |
| 823 | radiusclient), but it was contributed by a Radius user. |
| 824 | |
| 825 | PH/18 Installed Lars Mainka's patch for the support of CRL collections in |
| 826 | files or directories, for OpenSSL. |
| 827 | |
| 828 | PH/19 When an Exim process that is running as root has to create an Exim log |
| 829 | file, it does so in a subprocess that runs as exim:exim so as to get the |
| 830 | ownership right at creation (otherwise, other Exim processes might see |
| 831 | the file with the wrong ownership). There was no test for failure of this |
| 832 | fork() call, which would lead to the process getting stuck as it waited |
| 833 | for a non-existent subprocess. Forks do occasionally fail when resources |
| 834 | run out. I reviewed all the other calls to fork(); they all seem to check |
| 835 | for failure. |
| 836 | |
| 837 | PH/20 When checking for unexpected SMTP input at connect time (before writing |
| 838 | the banner), Exim was not dealing correctly with a non-positive return |
| 839 | from the read() function. If the client had disconnected by this time, |
| 840 | the result was a log entry for a synchronization error with an empty |
| 841 | string after "input=" when read() returned zero. If read() returned -1 |
| 842 | (an event I could not check), uninitialized data bytes were printed. |
| 843 | There were reports of junk text (parts of files, etc) appearing after |
| 844 | "input=". |
| 845 | |
| 846 | PH/21 Added acl_not_smtp_mime to allow for MIME scanning for non-SMTP messages. |
| 847 | |
| 848 | PH/22 Added support for macro redefinition, and (re)definition in between |
| 849 | driver and ACL definitions. |
| 850 | |
| 851 | PH/23 The cyrus_sasl authenticator was expanding server_hostname, but then |
| 852 | forgetting to use the resulting value; it was using the unexpanded value. |
| 853 | |
| 854 | PH/24 The cyrus_sasl authenticator was advertising mechanisms for which it |
| 855 | hadn't been configured. The fix is from Juergen Kreileder, who |
| 856 | understands it better than I do: |
| 857 | |
| 858 | "Here's what I see happening with three configured cyrus_sasl |
| 859 | authenticators configured (plain, login, cram-md5): |
| 860 | |
| 861 | On startup auth_cyrus_sasl_init() gets called for each of these. |
| 862 | This means three calls to sasl_listmech() without a specified mech_list. |
| 863 | => SASL tests which mechs of all available mechs actually work |
| 864 | => three warnings about OTP not working |
| 865 | => the returned list contains: plain, login, cram-md5, digest-md5, ... |
| 866 | |
| 867 | With the patch, sasl_listmech() also gets called three times. But now |
| 868 | SASL's mech_list option is set to the server_mech specified in the the |
| 869 | authenticator. Or in other words, the answer from sasl_listmech() |
| 870 | gets limited to just the mech you're testing for (which is different |
| 871 | for each call.) |
| 872 | => the return list contains just 'plain' or 'login', 'cram-md5' or |
| 873 | nothing depending on the value of ob->server_mech. |
| 874 | |
| 875 | I've just tested the patch: Authentication still works fine, |
| 876 | unavailable mechs specified in the exim configuration are still |
| 877 | caught, and the auth.log warnings about OTP are gone." |
| 878 | |
| 879 | PH/25 When debugging is enabled, the contents of the command line are added |
| 880 | to the debugging output, even when log_selector=+arguments is not |
| 881 | specified. |
| 882 | |
| 883 | PH/26 Change scripts/os-type so that when "uname -s" returns just "GNU", the |
| 884 | answer is "GNU", and only if the return is "GNU/something" is the answer |
| 885 | "Linux". |
| 886 | |
| 887 | PH/27 $acl_verify_message is now set immediately after the failure of a |
| 888 | verification in an ACL, and so is available in subsequent modifiers. In |
| 889 | particular, the message can be preserved by coding like this: |
| 890 | |
| 891 | warn !verify = sender |
| 892 | set acl_m0 = $acl_verify_message |
| 893 | |
| 894 | Previously, $acl_verify_message was set only while expanding "message" |
| 895 | and "log_message" when a very denied access. |
| 896 | |
| 897 | PH/28 Modified OS/os.c-Linux with |
| 898 | |
| 899 | -#ifndef OS_LOAD_AVERAGE |
| 900 | +#if !defined(OS_LOAD_AVERAGE) && defined(__linux__) |
| 901 | |
| 902 | to make Exim compile on kfreebsd-gnu. (I'm totally confused about the |
| 903 | nomenclature these days.) |
| 904 | |
| 905 | PH/29 Installed patch from the Sieve maintainer that adds the options |
| 906 | sieve_useraddress and sieve_subaddress to the redirect router. |
| 907 | |
| 908 | PH/30 In these circumstances: |
| 909 | . Two addresses routed to the same list of hosts; |
| 910 | . First host does not offer TLS; |
| 911 | . First host accepts first address; |
| 912 | . First host gives temporary error to second address; |
| 913 | . Second host offers TLS and a TLS session is established; |
| 914 | . Second host accepts second address. |
| 915 | Exim incorrectly logged both deliveries with the TLS parameters (cipher |
| 916 | and peerdn, if requested) that were in fact used only for the second |
| 917 | address. |
| 918 | |
| 919 | PH/31 When doing a callout as part of verifying an address, Exim was not paying |
| 920 | attention to any local part prefix or suffix that was matched by the |
| 921 | router that accepted the address. It now behaves in the same way as it |
| 922 | does for delivery: the affixes are removed from the local part unless |
| 923 | rcpt_include_affixes is set on the transport. |
| 924 | |
| 925 | PH/32 Add the sender address, as F=<...>, to the log line when logging a |
| 926 | timeout during the DATA phase of an incoming message. |
| 927 | |
| 928 | PH/33 Sieve envelope tests were broken for match types other than :is. I have |
| 929 | applied a patch sanctioned by the Sieve maintainer. |
| 930 | |
| 931 | PH/34 Change 4.50/80 broke Exim in that it could no longer handle cases where |
| 932 | the uid or gid is negative. A case of a negative gid caused this to be |
| 933 | noticed. The fix allows for either to be negative. |
| 934 | |
| 935 | PH/35 ACL_WHERE_MIME is now declared unconditionally, to avoid too much code |
| 936 | clutter, but the tables that are indexed by ACL_WHERE_xxx values had been |
| 937 | overlooked. |
| 938 | |
| 939 | PH/36 The change PH/12 above was broken. Fixed it. |
| 940 | |
| 941 | PH/37 Exim used to check for duplicate addresses in the middle of routing, on |
| 942 | the grounds that routing the same address twice would always produce the |
| 943 | same answer. This might have been true once, but it is certainly no |
| 944 | longer true now. Routing a child address may depend on the previous |
| 945 | routing that produced that child. Some complicated redirection strategies |
| 946 | went wrong when messages had multiple recipients, and made Exim's |
| 947 | behaviour dependent on the order in which the addresses were given. |
| 948 | |
| 949 | I have moved the duplicate checking until after the routing is complete. |
| 950 | Exim scans the addresses that are assigned to local and remote |
| 951 | transports, and removes any duplicates. This means that more work will be |
| 952 | done, as duplicates will always all be routed, but duplicates are |
| 953 | presumably rare, so I don't expect this is of any significance. |
| 954 | |
| 955 | For deliveries to pipes, files, and autoreplies, the duplicate checking |
| 956 | still happens during the routing process, since they are not going to be |
| 957 | routed further. |
| 958 | |
| 959 | PH/38 Installed a patch from Ian Freislich, with the agreement of Tom Kistner. |
| 960 | It corrects a timeout issue with spamd. This is Ian's comment: "The |
| 961 | background is that sometimes spamd either never reads data from a |
| 962 | connection it has accepted, or it never writes response data. The exiscan |
| 963 | spam.[ch] uses a 3600 second timeout on spamd socket reads, further, it |
| 964 | blindly assumes that writes won't block so it may never time out." |
| 965 | |
| 966 | PH/39 Allow G after quota size as well as K and M. |
| 967 | |
| 968 | PH/40 The value set for $authenticated_id in an authenticator may not contain |
| 969 | binary zeroes or newlines because the value is written to log lines and |
| 970 | to spool files. There was no check on this. Now the value is run through |
| 971 | the string_printing() function so that such characters are converted to |
| 972 | printable escape sequences. |
| 973 | |
| 974 | PH/41 $message_linecount is a new variable that contains the total number of |
| 975 | lines in the message. Compare $body_linecount, which is the count for the |
| 976 | body only. |
| 977 | |
| 978 | PH/42 Exim no longer gives details of delivery errors for specific addresses in |
| 979 | bounce and delay warning messages, except in certain special cases, which |
| 980 | are as follows: |
| 981 | |
| 982 | (a) An SMTP error message from a remote host; |
| 983 | (b) A message specified in a :fail: redirection; |
| 984 | (c) A message specified in a "fail" command in a system filter; |
| 985 | (d) A message specified in a FAIL return from the queryprogram router; |
| 986 | (e) A message specified by the cannot_route_message router option. |
| 987 | |
| 988 | In these cases only, Exim does include the error details in bounce and |
| 989 | warning messages. There are also a few cases where bland messages such |
| 990 | as "unrouteable address" or "local delivery error" are given. |
| 991 | |
| 992 | PH/43 $value is now also set for the "else" part of a ${run expansion. |
| 993 | |
| 994 | PH/44 Applied patch from the Sieve maintainer: "The vacation draft is still |
| 995 | being worked on, but at least Exim now implements the latest version to |
| 996 | play with." |
| 997 | |
| 998 | PH/45 In a pipe transport, although a timeout while waiting for the pipe |
| 999 | process to complete was treated as a delivery failure, a timeout while |
| 1000 | writing the message to the pipe was logged, but erroneously treated as a |
| 1001 | successful delivery. Such timeouts include transport filter timeouts. For |
| 1002 | consistency with the overall process timeout, these timeouts are now |
| 1003 | treated as errors, giving rise to delivery failures by default. However, |
| 1004 | there is now a new Boolean option for the pipe transport called |
| 1005 | timeout_defer, which, if set TRUE, converts the failures into defers for |
| 1006 | both kinds of timeout. A transport filter timeout is now identified in |
| 1007 | the log output. |
| 1008 | |
| 1009 | PH/46 The "scripts/Configure-config.h" script calls "make" at one point. On |
| 1010 | systems where "make" and "gmake" are different, calling "gmake" at top |
| 1011 | level broke things. I've arranged for the value of $(MAKE) to be passed |
| 1012 | from the Makefile to this script so that it can call the same version of |
| 1013 | "make". |
| 1014 | |
| 1015 | |
| 1016 | A note about Exim versions 4.44 and 4.50 |
| 1017 | ---------------------------------------- |
| 1018 | |
| 1019 | Exim 4.50 was meant to be the next release after 4.43. It contains a lot of |
| 1020 | changes of various kinds. As a consequence, a big documentation update was |
| 1021 | needed. This delayed the release for rather longer than seemed good, especially |
| 1022 | in the light of a couple of (minor) security issues. Therefore, the changes |
| 1023 | that fixed bugs were backported into 4.43, to create a 4.44 maintenance |
| 1024 | release. So 4.44 and 4.50 are in effect two different branches that both start |
| 1025 | from 4.43. |
| 1026 | |
| 1027 | I have left the 4.50 change log unchanged; it contains all the changes since |
| 1028 | 4.43. The change log for 4.44 is below; many of its items are identical to |
| 1029 | those for 4.50. This seems to be the most sensible way to preserve the |
| 1030 | historical information. |
| 1031 | |
| 1032 | |
| 1033 | Exim version 4.50 |
| 1034 | ----------------- |
| 1035 | |
| 1036 | 1. Minor wording change to the doc/README.SIEVE file. |
| 1037 | |
| 1038 | 2. Change 4.43/35 introduced a bug: if quota_filecount was set, the |
| 1039 | computation of the current number of files was incorrect. |
| 1040 | |
| 1041 | 3. Closing a stable door: arrange to panic-die if setitimer() ever fails. The |
| 1042 | bug fixed in 4.43/37 would have been diagnosed quickly if this had been in |
| 1043 | place. |
| 1044 | |
| 1045 | 4. Give more explanation in the error message when the command for a transport |
| 1046 | filter fails to execute. |
| 1047 | |
| 1048 | 5. There are several places where Exim runs a non-Exim command in a |
| 1049 | subprocess. The SIGUSR1 signal should be disabled for these processes. This |
| 1050 | was being done only for the command run by the queryprogram router. It is |
| 1051 | now done for all such subprocesses. The other cases are: ${run, transport |
| 1052 | filters, and the commands run by the lmtp and pipe transports. |
| 1053 | |
| 1054 | 6. Added CONFIGURE_GROUP build-time option. |
| 1055 | |
| 1056 | 7. Some older OS have a limit of 256 on the maximum number of file |
| 1057 | descriptors. Exim was using setrlimit() to set 1000 as a large value |
| 1058 | unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these |
| 1059 | systems. I've change it so that if it can't get 1000, it tries for 256. |
| 1060 | |
| 1061 | 8. "control=submission" was allowed, but had no effect, in a DATA ACL. This |
| 1062 | was an oversight, and furthermore, ever since the addition of extra |
| 1063 | controls (e.g. 4.43/32), the checks on when to allow different forms of |
| 1064 | "control" were broken. There should now be diagnostics for all cases when a |
| 1065 | control that does not make sense is encountered. |
| 1066 | |
| 1067 | 9. Added the /retain_sender option to "control=submission". |
| 1068 | |
| 1069 | 10. $recipients is now available in the predata ACL (oversight). |
| 1070 | |
| 1071 | 11. Tidy the search cache before the fork to do a delivery from a message |
| 1072 | received from the command line. Otherwise the child will trigger a lookup |
| 1073 | failure and thereby defer the delivery if it tries to use (for example) a |
| 1074 | cached ldap connection that the parent has called unbind on. |
| 1075 | |
| 1076 | 12. If verify=recipient was followed by verify=sender in a RCPT ACL, the value |
| 1077 | of $address_data from the recipient verification was clobbered by the |
| 1078 | sender verification. |
| 1079 | |
| 1080 | 13. The value of address_data from a sender verification is now available in |
| 1081 | $sender_address_data in subsequent conditions in the ACL statement. |
| 1082 | |
| 1083 | 14. Added forbid_sieve_filter and forbid_exim_filter to the redirect router. |
| 1084 | |
| 1085 | 15. Added a new option "connect=<time>" to callout options, to set a different |
| 1086 | connection timeout. |
| 1087 | |
| 1088 | 16. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0 |
| 1089 | was its contents. (It was OK if the option was not defined at all.) |
| 1090 | |
| 1091 | 17. A "Completed" log line is now written for messages that are removed from |
| 1092 | the spool by the -Mrm option. |
| 1093 | |
| 1094 | 18. New variables $sender_verify_failure and $recipient_verify_failure contain |
| 1095 | information about exactly what failed. |
| 1096 | |
| 1097 | 19. Added -dd to debug only the daemon process. |
| 1098 | |
| 1099 | 20. Incorporated Michael Haardt's patch to ldap.c for improving the way it |
| 1100 | handles timeouts, both on the server side and network timeouts. Renamed the |
| 1101 | CONNECT parameter as NETTIMEOUT (but kept the old name for compatibility). |
| 1102 | |
| 1103 | 21. The rare case of EHLO->STARTTLS->HELO was setting the protocol to "smtp". |
| 1104 | It is now set to "smtps". |
| 1105 | |
| 1106 | 22. $host_address is now set to the target address during the checking of |
| 1107 | ignore_target_hosts. |
| 1108 | |
| 1109 | 23. When checking ignore_target_hosts for an ipliteral router, no host name was |
| 1110 | being passed; this would have caused $sender_host_name to have been used if |
| 1111 | matching the list had actually called for a host name (not very likely, |
| 1112 | since this list is usually IP addresses). A host name is now passed as |
| 1113 | "[x.x.x.x]". |
| 1114 | |
| 1115 | 24. Changed the calls that set up the SIGCHLD handler in the daemon to use the |
| 1116 | code that specifies a non-restarting handler (typically sigaction() in |
| 1117 | modern systems) in an attempt to fix a rare and obscure crash bug. |
| 1118 | |
| 1119 | 25. Narrowed the window for a race in the daemon that could cause it to ignore |
| 1120 | SIGCHLD signals. This is not a major problem, because they are used only to |
| 1121 | wake it up if nothing else does. |
| 1122 | |
| 1123 | 26. A malformed maildirsize file could cause Exim to calculate negative values |
| 1124 | for the mailbox size or file count. Odd effects could occur as a result. |
| 1125 | The maildirsize information is now recalculated if the size or filecount |
| 1126 | end up negative. |
| 1127 | |
| 1128 | 27. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this |
| 1129 | support for a long time. Removed HAVE_SYS_VFS_H. |
| 1130 | |
| 1131 | 28. Installed the latest version of exipick from John Jetmore. |
| 1132 | |
| 1133 | 29. In an address list, if the pattern was not a regular expression, an empty |
| 1134 | subject address (from a bounce message) matched only if the pattern was an |
| 1135 | empty string. Non-empty patterns were not even tested. This was the wrong |
| 1136 | because it is perfectly reasonable to use an empty address as part of a |
| 1137 | database query. An empty address is now tested by patterns that are |
| 1138 | lookups. However, all the other forms of pattern expect the subject to |
| 1139 | contain a local part and a domain, and therefore, for them, an empty |
| 1140 | address still always fails if the pattern is not itself empty. |
| 1141 | |
| 1142 | 30. Exim went into a mad DNS loop when attempting to do a callout where the |
| 1143 | host was specified on an smtp transport, and looking it up yielded more |
| 1144 | than one IP address. |
| 1145 | |
| 1146 | 31. Re-factored the code for checking spool and log partition space into a |
| 1147 | function that finds that data and another that does the check. The former |
| 1148 | is then used to implement four new variables: $spool_space, $log_space, |
| 1149 | $spool_inodes, and $log_inodes. |
| 1150 | |
| 1151 | 32. The RFC2047 encoding function was originally intended for short strings |
| 1152 | such as real names; it was not keeping to the 75-character limit for |
| 1153 | encoded words that the RFC imposes. It now respects the limit, and |
| 1154 | generates multiple encoded words if necessary. To be on the safe side, I |
| 1155 | have increased the buffer size for the ${rfc2047: expansion operator from |
| 1156 | 1024 to 2048 bytes. |
| 1157 | |
| 1158 | 33. It is now permitted to omit both strings after an "if" condition; if the |
| 1159 | condition is true, the result is "true". As before, when the second string |
| 1160 | is omitted, a false condition yields an empty string. This makes it less |
| 1161 | cumbersome to write custom ACL and router conditions. |
| 1162 | |
| 1163 | 34. Failure to deliver a bounce message always caused it to be frozen, even if |
| 1164 | there was an errors_to setting on the router. The errors_to setting is now |
| 1165 | respected. |
| 1166 | |
| 1167 | 35. If an IPv6 address is given for -bh or -bhc, it is now converted to the |
| 1168 | canonical form (fully expanded) before being placed in |
| 1169 | $sender_host_address. |
| 1170 | |
| 1171 | 36. The table in the code that translates DNS record types into text (T_A to |
| 1172 | "A" for instance) was missing entries for NS and CNAME. It is just possible |
| 1173 | that this could have caused confusion if both these types were looked up |
| 1174 | for the same domain, because the text type is used as part of Exim's |
| 1175 | per-process caching. But the chance of anyone hitting this buglet seems |
| 1176 | very small. |
| 1177 | |
| 1178 | 37. The dnsdb lookup has been extended in a number of ways. |
| 1179 | |
| 1180 | (1) There is a new type, "zns", which walks up the domain tree until it |
| 1181 | finds some nameserver records. It should be used with care. |
| 1182 | |
| 1183 | (2) There is a new type, "mxh", which is like "mx" except that it returns |
| 1184 | just the host names, not the priorities. |
| 1185 | |
| 1186 | (3) It is now possible to give a list of domains (or IP addresses) to be |
| 1187 | looked up. The behaviour when one of the lookups defers can be |
| 1188 | controlled by a keyword. |
| 1189 | |
| 1190 | (4) It is now possible to specify the separator character for use when |
| 1191 | multiple records are returned. |
| 1192 | |
| 1193 | 38. The dnslists ACL condition has been extended: it is now possible to supply |
| 1194 | a list of IP addresses and/or domains to be looked up in a particular DNS |
| 1195 | domain. |
| 1196 | |
| 1197 | 39. Added log_selector=+queue_time_overall. |
| 1198 | |
| 1199 | 40. When running the queue in the test harness, wait just a tad after forking a |
| 1200 | delivery process, to get repeatability of debugging output. |
| 1201 | |
| 1202 | 41. Include certificate and key file names in error message when GnuTLS fails |
| 1203 | to set them up, because the GnuTLS error message doesn't include the name |
| 1204 | of the failing file when there is a problem reading it. |
| 1205 | |
| 1206 | 42. Allow both -bf and -bF in the same test run. |
| 1207 | |
| 1208 | 43. Did the same fix as 41 above for OpenSSL, which had the same infelicity. |
| 1209 | |
| 1210 | 44. The "Exiscan patch" is now merged into the mainline Exim source. |
| 1211 | |
| 1212 | 45. Sometimes the final signoff response after QUIT could fail to get |
| 1213 | transmitted in the non-TLS case. Testing !tls_active instead of tls_active |
| 1214 | < 0 before doing a fflush(). This bug looks as though it goes back to the |
| 1215 | introduction of TLS in release 3.20, but "sometimes" must have been rare |
| 1216 | because the tests only now provoked it. |
| 1217 | |
| 1218 | 46. Reset the locale to "C" after calling embedded Perl, in case it was changed |
| 1219 | (this can affect the format of dates). |
| 1220 | |
| 1221 | 47. exim_tidydb, when checking for the continued existence of a message for |
| 1222 | which it has found a message-specific retry record, was not finding |
| 1223 | messages that were in split spool directories. Consequently, it was |
| 1224 | deleting retry records that should have stayed in existence. |
| 1225 | |
| 1226 | 48. Steve fixed some bugs in eximstats. |
| 1227 | |
| 1228 | 49. The SPA authentication driver was not abandoning authentication and moving |
| 1229 | on to the next authenticator when an expansion was forced to fail, |
| 1230 | contradicting the general specification for all authenticators. Instead it |
| 1231 | was generating a temporary error. It now behaves as specified. |
| 1232 | |
| 1233 | 50. The default ordering of permitted cipher suites for GnuTLS was pessimal |
| 1234 | (the order specifies the preference for clients). The order is now AES256, |
| 1235 | AES128, 3DES, ARCFOUR128. |
| 1236 | |
| 1237 | 51. Small patch to Sieve code - explicitly set From: when generating an |
| 1238 | autoreply. |
| 1239 | |
| 1240 | 52. Exim crashed if a remote delivery caused a very long error message to be |
| 1241 | recorded - for instance if somebody sent an entire SpamAssassin report back |
| 1242 | as a large number of 550 error lines. This bug was coincidentally fixed by |
| 1243 | increasing the size of one of Exim's internal buffers (big_buffer) that |
| 1244 | happened as part of the Exiscan merge. However, to be on the safe side, I |
| 1245 | have made the code more robust (and fixed the comments that describe what |
| 1246 | is going on). |
| 1247 | |
| 1248 | 53. Now that there can be additional text after "Completed" in log lines (if |
| 1249 | the queue_time_overall log selector is set), a one-byte patch to exigrep |
| 1250 | was needed to allow it to recognize "Completed" as not the last thing in |
| 1251 | the line. |
| 1252 | |
| 1253 | 54. The LDAP lookup was not handling a return of LDAP_RES_SEARCH_REFERENCE. A |
| 1254 | patch that reportedly fixes this has been added. I am not expert enough to |
| 1255 | create a test for it. This is what the patch creator wrote: |
| 1256 | |
| 1257 | "I found a little strange behaviour of ldap code when working with |
| 1258 | Windows 2003 AD Domain, where users was placed in more than one |
| 1259 | Organization Units. When I tried to give exim partial DN, the exit code |
| 1260 | of ldap_search was unknown to exim because of LDAP_RES_SEARCH_REFERENCE. |
| 1261 | But simultaneously result of request was absolutely normal ldap result, |
| 1262 | so I produce this patch..." |
| 1263 | |
| 1264 | Later: it seems that not all versions of LDAP support LDAP_RES_SEARCH_ |
| 1265 | REFERENCE, so I have modified the code to exclude the patch when that macro |
| 1266 | is not defined. |
| 1267 | |
| 1268 | 55. Some experimental protocols are using DNS PTR records for new purposes. The |
| 1269 | keys for these records are domain names, not reversed IP addresses. The |
| 1270 | dnsdb PTR lookup now tests whether its key is an IP address. If not, it |
| 1271 | leaves it alone. Component reversal etc. now happens only for IP addresses. |
| 1272 | CAN-2005-0021 |
| 1273 | |
| 1274 | 56. Improve error message when ldap_search() fails in OpenLDAP or Solaris LDAP. |
| 1275 | |
| 1276 | 57. Double the size of the debug message buffer (to 2048) so that more of very |
| 1277 | long debug lines gets shown. |
| 1278 | |
| 1279 | 58. The exicyclog utility now does better if the number of log files to keep |
| 1280 | exceeds 99. In this case, it numbers them 001, 002 ... instead of 01, 02... |
| 1281 | |
| 1282 | 59. Two changes related to the smtp_active_hostname option: |
| 1283 | |
| 1284 | (1) $smtp_active_hostname is now available as a variable. |
| 1285 | (2) The default for smtp_banner uses $smtp_active_hostname instead |
| 1286 | of $primary_hostname. |
| 1287 | |
| 1288 | 60. The host_aton() function is supposed to be passed a string that is known |
| 1289 | to be a valid IP address. However, in the case of IPv6 addresses, it was |
| 1290 | not checking this. This is a hostage to fortune. Exim now panics and dies |
| 1291 | if the condition is not met. A case was found where this could be provoked |
| 1292 | from a dnsdb PTR lookup with an IPv6 address that had more than 8 |
| 1293 | components; fortuitously, this particular loophole had already been fixed |
| 1294 | by change 4.50/55 above. |
| 1295 | |
| 1296 | If there are any other similar loopholes, the new check in host_aton() |
| 1297 | itself should stop them being exploited. The report I received stated that |
| 1298 | data on the command line could provoke the exploit when Exim was running as |
| 1299 | exim, but did not say which command line option was involved. All I could |
| 1300 | find was the use of -be with a bad dnsdb PTR lookup, and in that case it is |
| 1301 | running as the user. |
| 1302 | CAN-2005-0021 |
| 1303 | |
| 1304 | 61. There was a buffer overflow vulnerability in the SPA authentication code |
| 1305 | (which came originally from the Samba project). I have added a test to the |
| 1306 | spa_base64_to_bits() function which I hope fixes it. |
| 1307 | CAN-2005-0022 |
| 1308 | |
| 1309 | 62. Configuration update for GNU/Hurd and variations. Updated Makefile-GNU and |
| 1310 | os.h-GNU, and added configuration files for GNUkFreeBSD and GNUkNetBSD. |
| 1311 | |
| 1312 | 63. The daemon start-up calls getloadavg() while still root for those OS that |
| 1313 | need the first call to be done as root, but it missed one case: when |
| 1314 | deliver_queue_load_max is set with deliver_drop_privilege. This is |
| 1315 | necessary for the benefit of the queue runner, because there is no re-exec |
| 1316 | when deliver_drop_privilege is set. |
| 1317 | |
| 1318 | 64. A call to exiwhat cut short delays set up by "delay" modifiers in ACLs. |
| 1319 | This has been fixed. |
| 1320 | |
| 1321 | 65. Caching of lookup data for "hosts =" ACL conditions, when a named host list |
| 1322 | was in use, was not putting the data itself into the right store pool; |
| 1323 | consequently, it could be overwritten for a subsequent message in the same |
| 1324 | SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked |
| 1325 | the caching.) |
| 1326 | |
| 1327 | 66. Added hosts_max_try_hardlimit to the smtp transport, default 50. |
| 1328 | |
| 1329 | 67. The string_is_ip_address() function returns 0, 4, or 6, for "no an IP |
| 1330 | address", "IPv4 address", and "IPv6 address", respectively. Some calls of |
| 1331 | the function were treating the return as a boolean value, which happened to |
| 1332 | work because 0=false and not-0=true, but is not correct code. |
| 1333 | |
| 1334 | 68. The host_aton() function was not handling scoped IPv6 addresses (those |
| 1335 | with, for example, "%eth0" on the end) correctly. |
| 1336 | |
| 1337 | 69. Fixed some compiler warnings in acl.c for the bitmaps specified with |
| 1338 | negated items (that is, ~something) in unsigned ints. Some compilers |
| 1339 | apparently mutter when there is no cast. |
| 1340 | |
| 1341 | 70. If an address verification called from an ACL failed, and did not produce a |
| 1342 | user-specific message (i.e. there was only a "system" message), nothing was |
| 1343 | put in $acl_verify_message. In this situation, it now puts the system |
| 1344 | message there. |
| 1345 | |
| 1346 | 71. Change 4.23/11 added synchronization checking at the start of an SMTP |
| 1347 | session; change 4.31/43 added the unwanted input to the log line - except |
| 1348 | that it did not do this in the start of session case. It now does. |
| 1349 | |
| 1350 | 72. After a timeout in a callout SMTP session, Exim still sent a QUIT command. |
| 1351 | This is wrong and can cause the other end to generate a synchronization |
| 1352 | error if it is another Exim or anything else that does the synchronization |
| 1353 | check. A QUIT command is no longer sent after a timeout. |
| 1354 | |
| 1355 | 73. $host_lookup_deferred has been added, to make it easier to detect DEFERs |
| 1356 | during host lookups. |
| 1357 | |
| 1358 | 74. The defer_ok option of callout verification was not working if it was used |
| 1359 | when verifying addresses in header lines, that is, for this case: |
| 1360 | |
| 1361 | verify = header_sender/callout=defer_ok |
| 1362 | |
| 1363 | 75. A backgrounded daemon closed stdin/stdout/stderr on entry; this meant that |
| 1364 | those file descriptors could be used for SMTP connections. If anything |
| 1365 | wrote to stderr (the example that came up was "warn" in embedded Perl), it |
| 1366 | could be sent to the SMTP client, causing chaos. The daemon now opens |
| 1367 | stdin, stdout, and stderr to /dev/null when it puts itself into the |
| 1368 | background. |
| 1369 | |
| 1370 | 76. Arrange for output from Perl's "warn" command to be written to Exim's main |
| 1371 | log by default. The user can override this with suitable Perl magic. |
| 1372 | |
| 1373 | 77. The use of log_message on a "discard" ACL verb, which is supposed to add to |
| 1374 | the log message when discard triggers, was not working for the DATA ACL or |
| 1375 | for the non-SMTP ACL. |
| 1376 | |
| 1377 | 78. Error message wording change in sieve.c. |
| 1378 | |
| 1379 | 79. If smtp_accept_max_per_host was set, the number of connections could be |
| 1380 | restricted to fewer than expected, because the daemon was trying to set up |
| 1381 | a new connection before checking whether the processes handling previous |
| 1382 | connections had finished. The check for completed processes is now done |
| 1383 | earlier. On busy systems, this bug wouldn't be noticed because something |
| 1384 | else would have woken the daemon, and it would have reaped the completed |
| 1385 | process earlier. |
| 1386 | |
| 1387 | 80. If a message was submitted locally by a user whose login name contained one |
| 1388 | or more spaces (ugh!), the spool file that Exim wrote was not re-readable. |
| 1389 | It caused a spool format error. I have fixed the spool reading code. A |
| 1390 | related problem was that the "from" clause in the Received: line became |
| 1391 | illegal because of the space(s). It is now covered by ${quote_local_part. |
| 1392 | |
| 1393 | 81. Included the latest eximstats from Steve (adds average sizes to HTML Top |
| 1394 | tables). |
| 1395 | |
| 1396 | 82. Updated OS/Makefile-AIX as per message from Mike Meredith. |
| 1397 | |
| 1398 | 83. Patch from Sieve maintainer to fix unterminated string problem in |
| 1399 | "vacation" handling. |
| 1400 | |
| 1401 | 84. Some minor changes to the Linux configuration files to help with other |
| 1402 | OS variants using glibc. |
| 1403 | |
| 1404 | 85. One more patch for Sieve to update vacation handling to latest spec. |
| 1405 | |
| 1406 | |
| 1407 | ---------------------------------------------------- |
| 1408 | See the note above about the 4.44 and 4.50 releases. |
| 1409 | ---------------------------------------------------- |
| 1410 | |
| 1411 | |
| 1412 | Exim version 4.44 |
| 1413 | ----------------- |
| 1414 | |
| 1415 | 1. Change 4.43/35 introduced a bug that caused file counts to be |
| 1416 | incorrectly computed when quota_filecount was set in an appendfile |
| 1417 | transport |
| 1418 | |
| 1419 | 2. Closing a stable door: arrange to panic-die if setitimer() ever fails. The |
| 1420 | bug fixed in 4.43/37 would have been diagnosed quickly if this had been in |
| 1421 | place. |
| 1422 | |
| 1423 | 3. Give more explanation in the error message when the command for a transport |
| 1424 | filter fails to execute. |
| 1425 | |
| 1426 | 4. There are several places where Exim runs a non-Exim command in a |
| 1427 | subprocess. The SIGUSR1 signal should be disabled for these processes. This |
| 1428 | was being done only for the command run by the queryprogram router. It is |
| 1429 | now done for all such subprocesses. The other cases are: ${run, transport |
| 1430 | filters, and the commands run by the lmtp and pipe transports. |
| 1431 | |
| 1432 | 5. Some older OS have a limit of 256 on the maximum number of file |
| 1433 | descriptors. Exim was using setrlimit() to set 1000 as a large value |
| 1434 | unlikely to be exceeded. Change 4.43/17 caused a lot of logging on these |
| 1435 | systems. I've change it so that if it can't get 1000, it tries for 256. |
| 1436 | |
| 1437 | 6. "control=submission" was allowed, but had no effect, in a DATA ACL. This |
| 1438 | was an oversight, and furthermore, ever since the addition of extra |
| 1439 | controls (e.g. 4.43/32), the checks on when to allow different forms of |
| 1440 | "control" were broken. There should now be diagnostics for all cases when a |
| 1441 | control that does not make sense is encountered. |
| 1442 | |
| 1443 | 7. $recipients is now available in the predata ACL (oversight). |
| 1444 | |
| 1445 | 8. Tidy the search cache before the fork to do a delivery from a message |
| 1446 | received from the command line. Otherwise the child will trigger a lookup |
| 1447 | failure and thereby defer the delivery if it tries to use (for example) a |
| 1448 | cached ldap connection that the parent has called unbind on. |
| 1449 | |
| 1450 | 9. If verify=recipient was followed by verify=sender in a RCPT ACL, the value |
| 1451 | of $address_data from the recipient verification was clobbered by the |
| 1452 | sender verification. |
| 1453 | |
| 1454 | 10. If FIXED_NEVER_USERS was defined, but empty, Exim was assuming the uid 0 |
| 1455 | was its contents. (It was OK if the option was not defined at all.) |
| 1456 | |
| 1457 | 11. A "Completed" log line is now written for messages that are removed from |
| 1458 | the spool by the -Mrm option. |
| 1459 | |
| 1460 | 12. $host_address is now set to the target address during the checking of |
| 1461 | ignore_target_hosts. |
| 1462 | |
| 1463 | 13. When checking ignore_target_hosts for an ipliteral router, no host name was |
| 1464 | being passed; this would have caused $sender_host_name to have been used if |
| 1465 | matching the list had actually called for a host name (not very likely, |
| 1466 | since this list is usually IP addresses). A host name is now passed as |
| 1467 | "[x.x.x.x]". |
| 1468 | |
| 1469 | 14. Changed the calls that set up the SIGCHLD handler in the daemon to use the |
| 1470 | code that specifies a non-restarting handler (typically sigaction() in |
| 1471 | modern systems) in an attempt to fix a rare and obscure crash bug. |
| 1472 | |
| 1473 | 15. Narrowed the window for a race in the daemon that could cause it to ignore |
| 1474 | SIGCHLD signals. This is not a major problem, because they are used only to |
| 1475 | wake it up if nothing else does. |
| 1476 | |
| 1477 | 16. A malformed maildirsize file could cause Exim to calculate negative values |
| 1478 | for the mailbox size or file count. Odd effects could occur as a result. |
| 1479 | The maildirsize information is now recalculated if the size or filecount |
| 1480 | end up negative. |
| 1481 | |
| 1482 | 17. Added HAVE_SYS_STATVFS_H to the os.h file for Linux, as it has had this |
| 1483 | support for a long time. Removed HAVE_SYS_VFS_H. |
| 1484 | |
| 1485 | 18. Updated exipick to current release from John Jetmore. |
| 1486 | |
| 1487 | 19. Allow an empty sender to be matched against a lookup in an address list. |
| 1488 | Previously the only cases considered were a regular expression, or an |
| 1489 | empty pattern. |
| 1490 | |
| 1491 | 20. Exim went into a mad DNS lookup loop when doing a callout where the |
| 1492 | host was specified on the transport, if the DNS lookup yielded more than |
| 1493 | one IP address. |
| 1494 | |
| 1495 | 21. The RFC2047 encoding function was originally intended for short strings |
| 1496 | such as real names; it was not keeping to the 75-character limit for |
| 1497 | encoded words that the RFC imposes. It now respects the limit, and |
| 1498 | generates multiple encoded words if necessary. To be on the safe side, I |
| 1499 | have increased the buffer size for the ${rfc2047: expansion operator from |
| 1500 | 1024 to 2048 bytes. |
| 1501 | |
| 1502 | 22. Failure to deliver a bounce message always caused it to be frozen, even if |
| 1503 | there was an errors_to setting on the router. The errors_to setting is now |
| 1504 | respected. |
| 1505 | |
| 1506 | 23. If an IPv6 address is given for -bh or -bhc, it is now converted to the |
| 1507 | canonical form (fully expanded) before being placed in |
| 1508 | $sender_host_address. |
| 1509 | |
| 1510 | 24. Updated eximstats to version 1.33 |
| 1511 | |
| 1512 | 25. Include certificate and key file names in error message when GnuTLS fails |
| 1513 | to set them up, because the GnuTLS error message doesn't include the name |
| 1514 | of the failing file when there is a problem reading it. |
| 1515 | |
| 1516 | 26. Expand error message when OpenSSL has problems setting up cert/key files. |
| 1517 | As per change 25. |
| 1518 | |
| 1519 | 27. Reset the locale to "C" after calling embedded Perl, in case it was changed |
| 1520 | (this can affect the format of dates). |
| 1521 | |
| 1522 | 28. exim_tidydb, when checking for the continued existence of a message for |
| 1523 | which it has found a message-specific retry record, was not finding |
| 1524 | messages that were in split spool directories. Consequently, it was |
| 1525 | deleting retry records that should have stayed in existence. |
| 1526 | |
| 1527 | 29. eximstats updated to version 1.35 |
| 1528 | 1.34 - allow eximstats to parse syslog lines as well as mainlog lines |
| 1529 | 1.35 - bugfix such that pie charts by volume are generated correctly |
| 1530 | |
| 1531 | 30. The SPA authentication driver was not abandoning authentication and moving |
| 1532 | on to the next authenticator when an expansion was forced to fail, |
| 1533 | contradicting the general specification for all authenticators. Instead it |
| 1534 | was generating a temporary error. It now behaves as specified. |
| 1535 | |
| 1536 | 31. The default ordering of permitted cipher suites for GnuTLS was pessimal |
| 1537 | (the order specifies the preference for clients). The order is now AES256, |
| 1538 | AES128, 3DES, ARCFOUR128. |
| 1539 | |
| 1540 | 31. Small patch to Sieve code - explicitly set From: when generating an |
| 1541 | autoreply. |
| 1542 | |
| 1543 | 32. Exim crashed if a remote delivery caused a very long error message to be |
| 1544 | recorded - for instance if somebody sent an entire SpamAssassin report back |
| 1545 | as a large number of 550 error lines. This bug was coincidentally fixed by |
| 1546 | increasing the size of one of Exim's internal buffers (big_buffer) that |
| 1547 | happened as part of the Exiscan merge. However, to be on the safe side, I |
| 1548 | have made the code more robust (and fixed the comments that describe what |
| 1549 | is going on). |
| 1550 | |
| 1551 | 33. Some experimental protocols are using DNS PTR records for new purposes. The |
| 1552 | keys for these records are domain names, not reversed IP addresses. The |
| 1553 | dnsdb PTR lookup now tests whether its key is an IP address. If not, it |
| 1554 | leaves it alone. Component reversal etc. now happens only for IP addresses. |
| 1555 | CAN-2005-0021 |
| 1556 | |
| 1557 | 34. The host_aton() function is supposed to be passed a string that is known |
| 1558 | to be a valid IP address. However, in the case of IPv6 addresses, it was |
| 1559 | not checking this. This is a hostage to fortune. Exim now panics and dies |
| 1560 | if the condition is not met. A case was found where this could be provoked |
| 1561 | from a dnsdb PTR lookup with an IPv6 address that had more than 8 |
| 1562 | components; fortuitously, this particular loophole had already been fixed |
| 1563 | by change 4.50/55 or 4.44/33 above. |
| 1564 | |
| 1565 | If there are any other similar loopholes, the new check in host_aton() |
| 1566 | itself should stop them being exploited. The report I received stated that |
| 1567 | data on the command line could provoke the exploit when Exim was running as |
| 1568 | exim, but did not say which command line option was involved. All I could |
| 1569 | find was the use of -be with a bad dnsdb PTR lookup, and in that case it is |
| 1570 | running as the user. |
| 1571 | CAN-2005-0021 |
| 1572 | |
| 1573 | 35. There was a buffer overflow vulnerability in the SPA authentication code |
| 1574 | (which came originally from the Samba project). I have added a test to the |
| 1575 | spa_base64_to_bits() function which I hope fixes it. |
| 1576 | CAN-2005-0022 |
| 1577 | |
| 1578 | 36. The daemon start-up calls getloadavg() while still root for those OS that |
| 1579 | need the first call to be done as root, but it missed one case: when |
| 1580 | deliver_queue_load_max is set with deliver_drop_privilege. This is |
| 1581 | necessary for the benefit of the queue runner, because there is no re-exec |
| 1582 | when deliver_drop_privilege is set. |
| 1583 | |
| 1584 | 37. Caching of lookup data for "hosts =" ACL conditions, when a named host list |
| 1585 | was in use, was not putting the data itself into the right store pool; |
| 1586 | consequently, it could be overwritten for a subsequent message in the same |
| 1587 | SMTP connection. (Fix 4.40/11 dealt with the non-cache case, but overlooked |
| 1588 | the caching.) |
| 1589 | |
| 1590 | 38. Sometimes the final signoff response after QUIT could fail to get |
| 1591 | transmitted in the non-TLS case. Testing !tls_active instead of tls_active |
| 1592 | < 0 before doing a fflush(). This bug looks as though it goes back to the |
| 1593 | introduction of TLS in release 3.20, but "sometimes" must have been rare |
| 1594 | because the tests only now provoked it. |
| 1595 | |
| 1596 | |
| 1597 | Exim version 4.43 |
| 1598 | ----------------- |
| 1599 | |
| 1600 | 1. Fixed a longstanding but relatively impotent bug: a long time ago, before |
| 1601 | PIPELINING, the function smtp_write_command() used to return TRUE or FALSE. |
| 1602 | Now it returns an integer. A number of calls were still expecting a T/F |
| 1603 | return. Fortuitously, in all cases, the tests worked in OK situations, |
| 1604 | which is the norm. However, things would have gone wrong on any write |
| 1605 | failures on the smtp file descriptor. This function is used when sending |
| 1606 | messages over SMTP and also when doing verify callouts. |
| 1607 | |
| 1608 | 2. When Exim is called to do synchronous delivery of a locally submitted |
| 1609 | message (the -odf or -odi options), it no longer closes stderr before doing |
| 1610 | the delivery. |
| 1611 | |
| 1612 | 3. Implemented the mua_wrapper option. |
| 1613 | |
| 1614 | 4. Implemented mx_fail_domains and srv_fail_domains for the dnslookup router. |
| 1615 | |
| 1616 | 5. Implemented the functions header_remove(), header_testname(), |
| 1617 | header_add_at_position(), and receive_remove_recipient(), and exported them |
| 1618 | to local_scan(). |
| 1619 | |
| 1620 | 6. If an ACL "warn" statement specified the addition of headers, Exim already |
| 1621 | inserted X-ACL-Warn: at the start if there was no header name. However, it |
| 1622 | was not making this test for the second and subsequent header lines if |
| 1623 | there were newlines in the string. This meant that an invalid header could |
| 1624 | be inserted if Exim was badly configured. |
| 1625 | |
| 1626 | 7. Allow an ACL "warn" statement to add header lines at the start or after all |
| 1627 | the Received: headers, as well as at the end. |
| 1628 | |
| 1629 | 8. Added the rcpt_4xx retry error code. |
| 1630 | |
| 1631 | 9. Added postmaster_mailfrom=xxx to callout verification option. |
| 1632 | |
| 1633 | 10. Added mailfrom=xxxx to the callout verification option, for verify= |
| 1634 | header_sender only. |
| 1635 | |
| 1636 | 11. ${substr_1_:xxxx} and ${substr__3:xxxx} are now diagnosed as syntax errors |
| 1637 | (they previously behaved as ${substr_1_0:xxxx} and ${substr:_0_3:xxxx}). |
| 1638 | |
| 1639 | 12. Inserted some casts to stop certain compilers warning when using pointer |
| 1640 | differences as field lengths or precisions in printf-type calls (mostly |
| 1641 | affecting debugging statements). |
| 1642 | |
| 1643 | 13. Added optional readline() support for -be (dynamically loaded). |
| 1644 | |
| 1645 | 14. Obscure bug fix: if a message error (e.g. 4xx to MAIL) happened within the |
| 1646 | same clock tick as a message's arrival, so that its received time was the |
| 1647 | same as the "first fail" time on the retry record, and that message |
| 1648 | remained on the queue past the ultimate address timeout, every queue runner |
| 1649 | would try a delivery (because it was past the ultimate address timeout) but |
| 1650 | after another failure, the ultimate address timeout, which should have then |
| 1651 | bounced the address, did not kick in. This was a "< instead of <=" error; |
| 1652 | in most cases the first failure would have been in the next clock tick |
| 1653 | after the received time, and all would be well. |
| 1654 | |
| 1655 | 15. The special items beginning with @ in domain lists (e.g. @mx_any) were not |
| 1656 | being recognized when the domain list was tested by the match_domain |
| 1657 | condition in an expansion string. |
| 1658 | |
| 1659 | 16. Added the ${str2b64: operator. |
| 1660 | |
| 1661 | 17. Exim was always calling setrlimit() to set a large limit for the number of |
| 1662 | processes, without checking whether the existing limit was already |
| 1663 | adequate. (It did check for the limit on file descriptors.) Furthermore, |
| 1664 | errors from getrlimit() and setrlimit() were being ignored. Now they are |
| 1665 | logged to the main and panic logs, but Exim does carry on, to try to do its |
| 1666 | job under whatever limits there are. |
| 1667 | |
| 1668 | 18. Imported PCRE 5.0. |
| 1669 | |
| 1670 | 19. Trivial typo in log message " temporarily refused connection" (the leading |
| 1671 | space). |
| 1672 | |
| 1673 | 20. If the log selector return_path_on_delivery was set and an address was |
| 1674 | redirected to /dev/null, the delivery process crashed because it assumed |
| 1675 | that a return path would always be set for a "successful" delivery. In this |
| 1676 | case, the whole delivery is bypassed as an optimization, and therefore no |
| 1677 | return path is set. |
| 1678 | |
| 1679 | 21. Internal re-arrangement: the function for sending a challenge and reading |
| 1680 | a response while authentication was assuming a zero-terminated challenge |
| 1681 | string. It's now changed to take a pointer and a length, to allow for |
| 1682 | binary data in such strings. |
| 1683 | |
| 1684 | 22. Added the cyrus_sasl authenticator (code supplied by MBM). |
| 1685 | |
| 1686 | 23. Exim was not respecting finduser_retries when seeking the login of the |
| 1687 | uid under which it was called; it was always trying 10 times. (The default |
| 1688 | setting of finduser_retries is zero.) Also, it was sleeping after the final |
| 1689 | failure, which is pointless. |
| 1690 | |
| 1691 | 24. Implemented tls_on_connect_ports. |
| 1692 | |
| 1693 | 25. Implemented acl_smtp_predata. |
| 1694 | |
| 1695 | 26. If the domain in control=submission is set empty, Exim assumes that the |
| 1696 | authenticated id is a complete email address when it generates From: or |
| 1697 | Sender: header lines. |
| 1698 | |
| 1699 | 27. Added "#define SOCKLEN_T int" to OS/os.h-SCO and OS/os.h-SCO_SV. Also added |
| 1700 | definitions to OS/Makefile-SCO and OS/Makefile-SCO_SV that put basename, |
| 1701 | chown and chgrp in /bin and hostname in /usr/bin. |
| 1702 | |
| 1703 | 28. Exim was keeping the "process log" file open after each use, just as it |
| 1704 | does for the main log. This opens the possibility of it remaining open for |
| 1705 | long periods when the USR1 signal hits a daemon. Occasional processlog |
| 1706 | errors were reported, that could have been caused by this. Anyway, it seems |
| 1707 | much more sensible not to leave this file open at all, so that is what now |
| 1708 | happens. |
| 1709 | |
| 1710 | 29. The long-running daemon process does not normally write to the log once it |
| 1711 | has entered its main loop, and it closes the log before doing so. This is |
| 1712 | so that log files can straightforwardly be renamed and moved. However, |
| 1713 | there are a couple of unusual error situations where the daemon does write |
| 1714 | log entries, and I had neglected to close the log afterwards. |
| 1715 | |
| 1716 | 30. The text of an SMTP error response that was received during a remote |
| 1717 | delivery was being truncated at 512 bytes. This is too short for some of |
| 1718 | the long messages that one sometimes sees. I've increased the limit to |
| 1719 | 1024. |
| 1720 | |
| 1721 | 31. It is now possible to make retry rules that apply only when a message has a |
| 1722 | specific sender, in particular, an empty sender. |
| 1723 | |
| 1724 | 32. Added "control = enforce_sync" and "control = no_enforce_sync". This makes |
| 1725 | it possible to be selective about when SMTP synchronization is enforced. |
| 1726 | |
| 1727 | 33. Added "control = caseful_local_part" and "control = "caselower_local_part". |
| 1728 | |
| 1729 | 32. Implemented hosts_connection_nolog. |
| 1730 | |
| 1731 | 33. Added an ACL for QUIT. |
| 1732 | |
| 1733 | 34. Setting "delay_warning=" to disable warnings was not working; it gave a |
| 1734 | syntax error. |
| 1735 | |
| 1736 | 35. Added mailbox_size and mailbox_filecount to appendfile. |
| 1737 | |
| 1738 | 36. Added control = no_multiline_responses to ACLs. |
| 1739 | |
| 1740 | 37. There was a bug in the logic of the code that waits for the clock to tick |
| 1741 | in the case where the clock went backwards by a substantial amount such |
| 1742 | that the microsecond fraction of "now" was more than the microsecond |
| 1743 | fraction of "then" (but the whole seconds number was less). |
| 1744 | |
| 1745 | 38. Added support for the libradius Radius client library this is found on |
| 1746 | FreeBSD (previously only the radiusclient library was supported). |
| 1747 | |
| 1748 | |
| 1749 | Exim version 4.42 |
| 1750 | ----------------- |
| 1751 | |
| 1752 | 1. When certain lookups returned multiple values in the form name=value, the |
| 1753 | quoting of the values was not always being done properly. Specifically: |
| 1754 | (a) If the value started with a double quote, but contained no whitespace, |
| 1755 | it was not quoted. |
| 1756 | (b) If the value contained whitespace other than a space character (i.e. |
| 1757 | tabs or newlines or carriage returns) it was not quoted. |
| 1758 | This fix has been applied to the mysql and pgsql lookups by writing a |
| 1759 | separate quoting function and calling it from the lookup code. The fix |
| 1760 | should probably also be applied to nisplus, ibase and oracle lookups, but |
| 1761 | since I cannot test any of those, I have not disturbed their existing code. |
| 1762 | |
| 1763 | 2. A hit in the callout cache for a specific address caused a log line with no |
| 1764 | reason for rejecting RCPT. Now it says "Previous (cached) callout |
| 1765 | verification failure". |
| 1766 | |
| 1767 | 3. There was an off-by-one bug in the queryprogram router. An over-long |
| 1768 | return line was truncated at 256 instead of 255 characters, thereby |
| 1769 | overflowing its buffer with the terminating zero. As well as fixing this, I |
| 1770 | have increased the buffer size to 1024 (and made a note to document this). |
| 1771 | |
| 1772 | 4. If an interrupt, such as the USR1 signal that is send by exiwhat, arrives |
| 1773 | when Exim is waiting for an SMTP response from a remote server, Exim |
| 1774 | restarts its select() call on the socket, thereby resetting its timeout. |
| 1775 | This is not a problem when such interrupts are rare. Somebody set up a cron |
| 1776 | job to run exiwhat every 2 minutes, which is less than the normal select() |
| 1777 | timeout (5 or 10 minutes). This meant that the select() timeout never |
| 1778 | kicked in because it was always reset. I have fixed this by comparing the |
| 1779 | time when an interrupt arrives with the time at the start of the first call |
| 1780 | to select(). If more time than the timeout has elapsed, the interrupt is |
| 1781 | treated as a timeout. |
| 1782 | |
| 1783 | 5. Some internal re-factoring in preparation for the addition of Sieve |
| 1784 | extensions (by MH). In particular, the "personal" test is moved to a |
| 1785 | separate function, and given an option for scanning Cc: and Bcc: (which is |
| 1786 | not set for Exim filters). |
| 1787 | |
| 1788 | 6. When Exim created an email address using the login of the caller as the |
| 1789 | local part (e.g. when creating a From: or Sender: header line), it was not |
| 1790 | quoting the local part when it contained special characters such as @. |
| 1791 | |
| 1792 | 7. Installed new OpenBSD configuration files. |
| 1793 | |
| 1794 | 8. Reworded some messages for syntax errors in "and" and "or" conditions to |
| 1795 | try to make them clearer. |
| 1796 | |
| 1797 | 9. Callout options, other than the timeout value, were being ignored when |
| 1798 | verifying sender addresses in header lines. For example, when using |
| 1799 | |
| 1800 | verify = header_sender/callout=no_cache |
| 1801 | |
| 1802 | the cache was (incorrectly) being used. |
| 1803 | |
| 1804 | 10. Added a missing instance of ${EXE} to the exim_install script; this affects |
| 1805 | only the Cygwin environment. |
| 1806 | |
| 1807 | 11. When return_path_on_delivery was set as a log selector, if different remote |
| 1808 | addresses in the same message used different return paths and parallel |
| 1809 | remote delivery occurred, the wrong values would sometimes be logged. |
| 1810 | (Whenever a remote delivery process finished, the return path value from |
| 1811 | the most recently started remote delivery process was logged.) |
| 1812 | |
| 1813 | 12. RFC 3848 specifies standard names for the "with" phrase in Received: header |
| 1814 | lines when AUTH and/or TLS are in use. This is the "received protocol" |
| 1815 | field. Exim used to use "asmtp" for authenticated SMTP, without any |
| 1816 | indication (in the protocol name) for TLS use. Now it follows the RFC and |
| 1817 | uses "esmtpa" if the connection is authenticated, "esmtps" if it is |
| 1818 | encrypted, and "esmtpsa" if it is both encrypted and authenticated. These |
| 1819 | names appear in log lines as well as in Received: header lines. |
| 1820 | |
| 1821 | 13. Installed MH's patches for Sieve to add the "copy" and "vacation" |
| 1822 | extensions, and comparison tests, and to fix some bugs. |
| 1823 | |
| 1824 | 14. Changes to the "personal" filter test: |
| 1825 | |
| 1826 | (1) The test was buggy in that it was just doing the equivalent of |
| 1827 | "contains" tests on header lines. For example, if a user's address was |
| 1828 | anne@some.where, the "personal" test would incorrectly be true for |
| 1829 | |
| 1830 | To: susanne@some.where |
| 1831 | |
| 1832 | This test is now done by extracting each address from the header in turn, |
| 1833 | and checking the entire address. Other tests that are part of "personal" |
| 1834 | are now done using regular expressions (for example, to check local parts |
| 1835 | of addresses in From: header lines). |
| 1836 | |
| 1837 | (2) The list of non-personal local parts in From: addresses has been |
| 1838 | extended to include "listserv", "majordomo", "*-request", and "owner-*", |
| 1839 | taken from the Sieve specification recommendations. |
| 1840 | |
| 1841 | (3) If the message contains any header line starting with "List-" it is |
| 1842 | treated as non-personal. |
| 1843 | |
| 1844 | (4) The test for "circular" in the Subject: header line has been removed |
| 1845 | because it now seems ill-conceived. |
| 1846 | |
| 1847 | 15. Minor typos in src/EDITME comments corrected. |
| 1848 | |
| 1849 | 16. Installed latest exipick from John Jetmore. |
| 1850 | |
| 1851 | 17. If headers_add on a router specified a text string that was too long for |
| 1852 | string_sprintf() - that is, longer than 8192 bytes - Exim panicked. The use |
| 1853 | of string_sprintf() is now avoided. |
| 1854 | |
| 1855 | 18. $message_body_size was not set (it was always zero) when running the DATA |
| 1856 | ACL and the local_scan() function. |
| 1857 | |
| 1858 | 19. For the "mail" command in an Exim filter, no default was being set for |
| 1859 | the once_repeat time, causing a random time value to be used if "once" was |
| 1860 | specified. (If the value happened to be <= 0, no repeat happened.) The |
| 1861 | default is now 0s, meaning "never repeat". The "vacation" command was OK |
| 1862 | (its default is 7d). It's somewhat surprising nobody ever noticed this bug |
| 1863 | (I found it when inspecting the code). |
| 1864 | |
| 1865 | 20. There is now an overall timeout for performing a callout verification. It |
| 1866 | defaults to 4 times the callout timeout, which applies to individual SMTP |
| 1867 | commands during the callout. The overall timeout applies when there is more |
| 1868 | than one host that can be tried. The timeout is checked before trying the |
| 1869 | next host. This prevents very long delays if there are a large number of |
| 1870 | hosts and all are timing out (e.g. when the network connections are timing |
| 1871 | out). The value of the overall timeout can be changed by specifying an |
| 1872 | additional sub-option for "callout", called "maxwait". For example: |
| 1873 | |
| 1874 | verify = sender/callout=5s,maxwait=20s |
| 1875 | |
| 1876 | 21. Add O_APPEND to the open() call for maildirsize files (Exim already seeks |
| 1877 | to the end before writing, but this should make it even safer). |
| 1878 | |
| 1879 | 22. Exim was forgetting that it had advertised PIPELINING for the second and |
| 1880 | subsequent messages on an SMTP connection. It was also not resetting its |
| 1881 | memory on STARTTLS and an internal HELO. |
| 1882 | |
| 1883 | 23. When Exim logs an SMTP synchronization error within a session, it now |
| 1884 | records whether PIPELINING has been advertised or not. |
| 1885 | |
| 1886 | 24. Added 3 instances of "(long int)" casts to time_t variables that were being |
| 1887 | formatted using %ld, because on OpenBSD (and perhaps others), time_t is int |
| 1888 | rather than long int. |
| 1889 | |
| 1890 | 25. Installed the latest Cygwin configuration files from the Cygwin maintainer. |
| 1891 | |
| 1892 | 26. Added the never_mail option to autoreply. |
| 1893 | |
| 1894 | |
| 1895 | Exim version 4.41 |
| 1896 | ----------------- |
| 1897 | |
| 1898 | 1. A reorganization of the code in order to implement 4.40/8 caused a daemon |
| 1899 | crash if the getsockname() call failed; this can happen if a connection is |
| 1900 | closed very soon after it is established. The problem was simply in the |
| 1901 | order in which certain operations were done, causing Exim to try to write |
| 1902 | to the SMTP stream before it had set up the file descriptor. The bug has |
| 1903 | been fixed by making things happen in the correct order. |
| 1904 | |
| 1905 | |
| 1906 | Exim version 4.40 |
| 1907 | ----------------- |
| 1908 | |
| 1909 | 1. If "drop" was used in a DATA ACL, the SMTP output buffer was not flushed |
| 1910 | before the connection was closed, thus losing the rejection response. |
| 1911 | |
| 1912 | 2. Commented out the definition of SOCKLEN_T in os.h-SunOS5. It is needed for |
| 1913 | some early Solaris releases, but causes trouble in current releases where |
| 1914 | socklen_t is defined. |
| 1915 | |
| 1916 | 3. When std{in,out,err} are closed, re-open them to /dev/null so that they |
| 1917 | always exist. |
| 1918 | |
| 1919 | 4. Minor refactoring of os.c-Linux to avoid compiler warning when IPv6 is not |
| 1920 | configured. |
| 1921 | |
| 1922 | 5. Refactoring in expand.c to improve memory usage. Pre-allocate a block so |
| 1923 | that releasing the top of it at the end releases what was used for sub- |
| 1924 | expansions (unless the block got too big). However, discard this block if |
| 1925 | the first thing is a variable or header, so that we can use its block when |
| 1926 | it is dynamic (useful for very large $message_headers, for example). |
| 1927 | |
| 1928 | 6. Lookups now cache *every* query, not just the most recent. A new, separate |
| 1929 | store pool is used for this. It can be recovered when all lookup caches are |
| 1930 | flushed. Lookups now release memory at the end of their result strings. |
| 1931 | This has involved some general refactoring of the lookup sources. |
| 1932 | |
| 1933 | 7. Some code has been added to the store_xxx() functions to reduce the amount |
| 1934 | of flapping under certain conditions. |
| 1935 | |
| 1936 | 8. log_incoming_interface used to affect only the <= reception log lines. Now |
| 1937 | it causes the local interface and port to be added to several more SMTP log |
| 1938 | lines, for example "SMTP connection from", and rejection lines. |
| 1939 | |
| 1940 | 9. The Sieve author supplied some patches for the doc/README.SIEVE file. |
| 1941 | |
| 1942 | 10. Added a conditional definition of _BSD_SOCKLEN_T to os.h-Darwin. |
| 1943 | |
| 1944 | 11. If $host_data was set by virtue of a hosts lookup in an ACL, its value |
| 1945 | could be overwritten at the end of the current message (or the start of a |
| 1946 | new message if it was set in a HELO ACL). The value is now preserved for |
| 1947 | the duration of the SMTP connection. |
| 1948 | |
| 1949 | 12. If a transport had a headers_rewrite setting, and a matching header line |
| 1950 | contained an unqualified address, that address was qualified, even if it |
| 1951 | did not match any rewriting rules. The underlying bug was that the values |
| 1952 | of the flags that permit the existence of unqualified sender and recipient |
| 1953 | addresses in header lines (set by {sender,recipient}_unqualified_hosts for |
| 1954 | non-local messages, and by -bnq for local messages) were not being |
| 1955 | preserved with the message after it was received. |
| 1956 | |
| 1957 | 13. When Exim was logging an SMTP synchronization error, it could sometimes log |
| 1958 | "next input=" as part of the text comprising the host identity instead of |
| 1959 | the correct text. The code was using the same buffer for two different |
| 1960 | strings. However, depending on which order the printing function evaluated |
| 1961 | its arguments, the bug did not always show up. Under Linux, for example, my |
| 1962 | test suite worked just fine. |
| 1963 | |
| 1964 | 14. Exigrep contained a use of Perl's "our" scoping after change 4.31/70. This |
| 1965 | doesn't work with some older versions of Perl. It has been changed to "my", |
| 1966 | which in any case is probably the better facility to use. |
| 1967 | |
| 1968 | 15. A really picky compiler found some instances of statements for creating |
| 1969 | error messages that either had too many or two few arguments for the format |
| 1970 | string. |
| 1971 | |
| 1972 | 16. The size of the buffer for calls to the DNS resolver has been increased |
| 1973 | from 1024 to 2048. A larger buffer is needed when performing PTR lookups |
| 1974 | for addresses that have a lot of PTR records. This alleviates a problem; it |
| 1975 | does not fully solve it. |
| 1976 | |
| 1977 | 17. A dnsdb lookup for PTR records that receives more data than will fit in the |
| 1978 | buffer now truncates the list and logs the incident, which is the same |
| 1979 | action as happens when Exim is looking up a host name and its aliases. |
| 1980 | Previously in this situation something unpredictable would happen; |
| 1981 | sometimes it was "internal error: store_reset failed". |
| 1982 | |
| 1983 | 18. If a server dropped the connection unexpectedly when an Exim client was |
| 1984 | using GnuTLS and trying to read a response, the client delivery process |
| 1985 | crashed while trying to generate an error log message. |
| 1986 | |
| 1987 | 19. If a "warn" verb in an ACL added multiple headers to a message in a single |
| 1988 | string, for example: |
| 1989 | |
| 1990 | warn message = H1: something\nH2: something |
| 1991 | |
| 1992 | the text was added as a single header line from Exim's point of view |
| 1993 | though it ended up OK in the delivered message. However, searching for the |
| 1994 | second and subsequent header lines using $h_h2: did not work. This has been |
| 1995 | fixed. Similarly, if a system filter added multiple headers in this way, |
| 1996 | the routers could not see them. |
| 1997 | |
| 1998 | 20. Expanded the error message when iplsearch is called with an invalid key to |
| 1999 | suggest using net-iplsearch in a host list. |
| 2000 | |
| 2001 | 21. When running tests using -bh, any delays imposed by "delay" modifiers in |
| 2002 | ACLs are no longer actually imposed (and a message to that effect is |
| 2003 | output). |
| 2004 | |
| 2005 | 22. If a "gecos" field in a passwd entry contained escaped characters, in |
| 2006 | particular, if it contained a \" sequence, Exim got it wrong when building |
| 2007 | a From: or a Sender: header from that name. A second bug also caused |
| 2008 | incorrect handling when an unquoted " was present following a character |
| 2009 | that needed quoting. |
| 2010 | |
| 2011 | 23. "{crypt}" as a password encryption mechanism for a "crypteq" expansion item |
| 2012 | was not being matched caselessly. |
| 2013 | |
| 2014 | 24. Arranged for all hyphens in the exim.8 source to be escaped with |
| 2015 | backslashes. |
| 2016 | |
| 2017 | 25. Change 16 of 4.32, which reversed 71 or 4.31 didn't quite do the job |
| 2018 | properly. Recipient callout cache records were still being keyed to include |
| 2019 | the sender, even when use_sender was set false. This led to far more |
| 2020 | callouts that were necessary. The sender is no longer included in the key |
| 2021 | when use_sender is false. |
| 2022 | |
| 2023 | 26. Added "control = submission" modifier to ACLs. |
| 2024 | |
| 2025 | 27. Added the ${base62d: operator to decode base 62 numbers. |
| 2026 | |
| 2027 | 28. dnsdb lookups can now access SRV records. |
| 2028 | |
| 2029 | 29. CONFIGURE_OWNER can be set at build time to define an alternative owner for |
| 2030 | the configuration file. |
| 2031 | |
| 2032 | 30. The debug message "delivering xxxxxx-xxxxxx-xx" is now output in verbose |
| 2033 | (-v) mode. This makes the output for a verbose queue run more intelligible. |
| 2034 | |
| 2035 | 31. Added a use_postmaster feature to recipient callouts. |
| 2036 | |
| 2037 | 32. Added the $body_zerocount variable, containing the number of binary zero |
| 2038 | bytes in the message body. |
| 2039 | |
| 2040 | 33. The time of last modification of the "new" subdirectory is now used as the |
| 2041 | "mailbox time last read" when there is a quota error for a maildir |
| 2042 | delivery. |
| 2043 | |
| 2044 | 34. Added string comparison operators lt, lti, le, lei, gt, gti, ge, gei. |
| 2045 | |
| 2046 | 35. Added +ignore_unknown as a special item in host lists. |
| 2047 | |
| 2048 | 36. Code for decoding IPv6 addresses in host lists is now included, even if |
| 2049 | IPv6 support is not being compiled. This fixes a bug in which an IPv6 |
| 2050 | address was recognized as an IP address, but was then not correctly decoded |
| 2051 | into binary, causing unexpected and incorrect effects when compared with |
| 2052 | another IP address. |
| 2053 | |
| 2054 | |
| 2055 | Exim version 4.34 |
| 2056 | ----------------- |
| 2057 | |
| 2058 | 1. Very minor rewording of debugging text in manualroute to say "list of |
| 2059 | hosts" instead of "hostlist". |
| 2060 | |
| 2061 | 2. If verify=header_syntax was set, and a header line with an unqualified |
| 2062 | address (no domain) and a large number of spaces between the end of the |
| 2063 | name and the colon was received, the reception process suffered a buffer |
| 2064 | overflow, and (when I tested it) crashed. This was caused by some obsolete |
| 2065 | code that should have been removed. The fix is to remove it! |
| 2066 | |
| 2067 | 3. When running in the test harness, delay a bit after writing a bounce |
| 2068 | message to get a bit more predictability in the log output. |
| 2069 | |
| 2070 | 4. Added a call to search_tidyup() just before forking a reception process. In |
| 2071 | theory, someone could use a lookup in the expansion of smtp_accept_max_ |
| 2072 | per_host which, without the tidyup, could leave open a database connection. |
| 2073 | |
| 2074 | 5. Added the variables $recipient_data and $sender_data which get set from a |
| 2075 | lookup success in an ACL "recipients" or "senders" condition, or a router |
| 2076 | "senders" option, similar to $domain_data and $local_part_data. |
| 2077 | |
| 2078 | 6. Moved the writing of debug_print from before to after the "senders" test |
| 2079 | for routers. |
| 2080 | |
| 2081 | 7. Change 4.31/66 (moving the time when the Received: is generated) caused |
| 2082 | problems for message scanning, either using a data ACL, or using |
| 2083 | local_scan() because the Received: header was not generated till after they |
| 2084 | were called (in order to set the time as the time of reception completion). |
| 2085 | I have revised the way this works. The header is now generated after the |
| 2086 | body is received, but before the ACL or local_scan() are called. After they |
| 2087 | are run, the timestamp in the header is updated. |
| 2088 | |
| 2089 | |
| 2090 | Exim version 4.33 |
| 2091 | ----------------- |
| 2092 | |
| 2093 | 1. Change 4.24/6 introduced a bug because the SIGALRM handler was disabled |
| 2094 | before starting a queue runner without re-exec. This happened only when |
| 2095 | deliver_drop_privilege was set or when the Exim user was set to root. The |
| 2096 | effect of the bug was that timeouts during subsequent deliveries caused |
| 2097 | crashes instead of being properly handled. The handler is now left at its |
| 2098 | default (and expected) setting. |
| 2099 | |
| 2100 | 2. The other case in which a daemon avoids a re-exec is to deliver an incoming |
| 2101 | message, again when deliver_drop_privilege is set or Exim is run as root. |
| 2102 | The bug described in (1) was not present in this case, but the tidying up |
| 2103 | of the other signals was missing. I have made the two cases consistent. |
| 2104 | |
| 2105 | 3. The ignore_target_hosts setting on a manualroute router was being ignored |
| 2106 | for hosts that were looked up using the /MX notation. |
| 2107 | |
| 2108 | 4. Added /ignore=<ip list> feature to @mx_any, @mx_primary, and @mx_secondary |
| 2109 | in domain lists. |
| 2110 | |
| 2111 | 5. Change 4.31/55 was buggy, and broke when there was a rewriting rule that |
| 2112 | operated on the sender address. After changing the $sender_address to <> |
| 2113 | for the sender address verify, Exim was re-instated it as the original |
| 2114 | (before rewriting) address, but remembering that it had rewritten it, so it |
| 2115 | wasn't rewriting it again. This bug also had the effect of breaking the |
| 2116 | sender address verification caching when the sender address was rewritten. |
| 2117 | |
| 2118 | 6. The ignore_target_hosts option was being ignored by the ipliteral router. |
| 2119 | This has been changed so that if the ip literal address matches |
| 2120 | ignore_target_hosts, the router declines. |
| 2121 | |
| 2122 | 7. Added expansion conditions match_domain, match_address, and match_local_ |
| 2123 | part (NOT match_host). |
| 2124 | |
| 2125 | 8. The placeholder for the Received: header didn't have a length field set. |
| 2126 | |
| 2127 | 9. Added code to Exim itself and to exim_lock to test for a specific race |
| 2128 | condition that could lead to file corruption when using MBX delivery. The |
| 2129 | issue is with the lockfile that is created in /tmp. If this file is removed |
| 2130 | after a process has opened it but before that process has acquired a lock, |
| 2131 | there is the potential for a second process to recreate the file and also |
| 2132 | acquire a lock. This could lead to two Exim processes writing to the file |
| 2133 | at the same time. The added code performs the same test as UW imapd; it |
| 2134 | checks after acquiring the lock that its file descriptor still refers to |
| 2135 | the same named file. |
| 2136 | |
| 2137 | 10. The buffer for building added header lines was of fixed size, 8192 bytes. |
| 2138 | It is now parameterized by HEADER_ADD_BUFFER_SIZE and this can be adjusted |
| 2139 | when Exim is built. |
| 2140 | |
| 2141 | 11. Added the smtp_active_hostname option. If used, this will typically be made |
| 2142 | to depend on the incoming interface address. Because $interface_address is |
| 2143 | not set up until the daemon has forked a reception process, error responses |
| 2144 | that can happen earlier (such as "too many connections") no longer contain |
| 2145 | a host name. |
| 2146 | |
| 2147 | 12. If an expansion in a condition on a "warn" statement fails because a lookup |
| 2148 | defers, the "warn" statement is abandoned, and the next ACL statement is |
| 2149 | processed. Previously this caused the whole ACL to be aborted. |
| 2150 | |
| 2151 | 13. Added the iplsearch lookup type. |
| 2152 | |
| 2153 | 14. Added ident_timeout as a log selector. |
| 2154 | |
| 2155 | 15. Added tls_certificate_verified as a log selector. |
| 2156 | |
| 2157 | 16. Added a global option tls_require_ciphers (compare the smtp transport |
| 2158 | option of the same name). This controls incoming TLS connections. |
| 2159 | |
| 2160 | 17. I finally figured out how to make tls_require_ciphers do a similar thing |
| 2161 | in GNUtls to what it does in OpenSSL, that is, set up an appropriate list |
| 2162 | before starting the TLS session. |
| 2163 | |
| 2164 | 18. Tabs are now shown as \t in -bP output. |
| 2165 | |
| 2166 | 19. If the log selector return_path_on_delivery was set, Exim crashed when |
| 2167 | bouncing a message because it had too many Received: header lines. |
| 2168 | |
| 2169 | 20. If two routers both had headers_remove settings, and the first one included |
| 2170 | a superfluous trailing colon, the final name in the first list and the |
| 2171 | first name in the second list were incorrectly joined into one item (with a |
| 2172 | colon in the middle). |
| 2173 | |
| 2174 | |
| 2175 | Exim version 4.32 |
| 2176 | ----------------- |
| 2177 | |
| 2178 | 1. Added -C and -D options to the exinext utility, mainly to make it easier |
| 2179 | to include in the automated testing, but these could be helpful when |
| 2180 | multiple configurations are in use. |
| 2181 | |
| 2182 | 2. The exinext utility was not formatting the output nicely when there was |
| 2183 | an alternate port involved in the retry record key, nor when there was a |
| 2184 | message id as well (for retries that were specific to a specific message |
| 2185 | and a specific host). It was also confused by IPv6 addresses, because of |
| 2186 | the additional colons they contain. I have fixed the IPv4 problem, and |
| 2187 | patched it up to do a reasonable job for IPv6. |
| 2188 | |
| 2189 | 3. When there is an error after a MAIL, RCPT, or DATA SMTP command during |
| 2190 | delivery, the log line now contains "pipelined" if PIPELINING was used. |
| 2191 | |
| 2192 | 4. An SMTP transport process used to panic and die if the bind() call to set |
| 2193 | an explicit outgoing interface failed. This has been changed; it is now |
| 2194 | treated in the same way as a connect() failure. |
| 2195 | |
| 2196 | 5. A reference to $sender_host_name in the part of a conditional expansion |
| 2197 | that was being skipped was still causing a DNS lookup. This no longer |
| 2198 | occurs. |
| 2199 | |
| 2200 | 6. The def: expansion condition was not recognizing references to header lines |
| 2201 | that used bh_ and bheader_. |
| 2202 | |
| 2203 | 7. Added the _cache feature to named lists. |
| 2204 | |
| 2205 | 8. The code for checking quota_filecount in the appendfile transport was |
| 2206 | allowing one more file than it should have been. |
| 2207 | |
| 2208 | 9. For compatibility with Sendmail, the command line option |
| 2209 | |
| 2210 | -prval:sval |
| 2211 | |
| 2212 | is equivalent to |
| 2213 | |
| 2214 | -oMr rval -oMs sval |
| 2215 | |
| 2216 | and sets the incoming protocol and host name (for trusted callers). The |
| 2217 | host name and its colon can be omitted when only the protocol is to be set. |
| 2218 | Note the Exim already has two private options, -pd and -ps, that refer to |
| 2219 | embedded Perl. It is therefore impossible to set a protocol value of "d" or |
| 2220 | "s", but I don't think that's a major issue. |
| 2221 | |
| 2222 | 10. A number of refactoring changes to the code, none of which should affect |
| 2223 | Exim's behaviour: |
| 2224 | |
| 2225 | (a) The number of logging options was getting close to filling up the |
| 2226 | 32-bit word that was used as a bit map. I have split them into two classes: |
| 2227 | those that are passed in the argument to log_write(), and those that are |
| 2228 | only ever tested independently outside of that function. These are now in |
| 2229 | separate 32-bit words, so there is plenty of room for expansion again. |
| 2230 | There is no change in the user interface or the logging behaviour. |
| 2231 | |
| 2232 | (b) When building, for example, log lines, the code previously used a |
| 2233 | macro that called string_cat() twice, in order to add two strings. This is |
| 2234 | not really sufficiently general. Furthermore, there was one instance where |
| 2235 | it was actually wrong because one of the argument was used twice, and in |
| 2236 | one call a function was used. (As it happened, calling the function twice |
| 2237 | did not affect the overall behaviour.) The macro has been replaced by a |
| 2238 | function that can join an arbitrary number of extra strings onto a growing |
| 2239 | string. |
| 2240 | |
| 2241 | (c) The code for expansion conditions now uses a table and a binary chop |
| 2242 | instead of a serial search (which was left over from when there were very |
| 2243 | few conditions). Also, it now recognizes conditions like "pam" even when |
| 2244 | the relevant support is not compiled in: a suitably worded error message is |
| 2245 | given if an attempt is made to use such a condition. |
| 2246 | |
| 2247 | 11. Added ${time_interval:xxxxx}. |
| 2248 | |
| 2249 | 12. A bug was causing one of the ddress fields not to be passed back correctly |
| 2250 | from remote delivery subprocesses. The field in question was not being |
| 2251 | subsequently used, so this caused to problems in practice. |
| 2252 | |
| 2253 | 13. Added new log selectors queue_time and deliver_time. |
| 2254 | |
| 2255 | 14. Might have fixed a bug in maildirsizefile handling that threw up |
| 2256 | "unexpected character" debug warnings, and recalculated the data |
| 2257 | unnecessarily. In any case, I expanded the warning message to give more |
| 2258 | information. |
| 2259 | |
| 2260 | 15. Added the message "Restricted characters in address" to the statements in |
| 2261 | the default ACL that block characters like @ and % in local parts. |
| 2262 | |
| 2263 | 16. Change 71 for release 4.31 proved to be much less benign that I imagined. |
| 2264 | Three changes have been made: |
| 2265 | |
| 2266 | (a) There was a serious bug; a negative response to MAIL caused the whole |
| 2267 | recipient domain to be cached as invalid, thereby blocking all messages |
| 2268 | to all local parts at the same domain, from all senders. This bug has |
| 2269 | been fixed. The domain is no longer cached after a negative response to |
| 2270 | MAIL if the sender used is not empty. |
| 2271 | |
| 2272 | (b) The default behaviour of using MAIL FROM:<> for recipient callouts has |
| 2273 | been restored. |
| 2274 | |
| 2275 | (c) A new callout option, "use_sender" has been added for people who want |
| 2276 | the modified behaviour. |
| 2277 | |
| 2278 | |
| 2279 | Exim version 4.31 |
| 2280 | ----------------- |
| 2281 | |
| 2282 | 1. Removed "EXTRALIBS=-lwrap" from OS/Makefile-Unixware7 on the advice of |
| 2283 | Larry Rosenman. |
| 2284 | |
| 2285 | 2. Removed "LIBS = -lresolv" from OS/Makefile-Darwin as it is not needed, and |
| 2286 | indeed breaks things for older releases. |
| 2287 | |
| 2288 | 3. Added additional logging to the case where there is a problem reading data |
| 2289 | from a filter that is running in a subprocess using a pipe, in order to |
| 2290 | try to track down a specific problem. |
| 2291 | |
| 2292 | 4. Testing facility fudge: when running in the test harness and attempting |
| 2293 | to connect to 10.x.x.x (expecting a connection timeout) I'm now sometimes |
| 2294 | getting "No route to host". Convert this to a timeout. |
| 2295 | |
| 2296 | 5. Define ICONV_ARG2_TYPE as "char **" for Unixware7 to avoid compiler |
| 2297 | warning. |
| 2298 | |
| 2299 | 6. Some OS don't have socklen_t but use size_t instead. This affects the |
| 2300 | fifth argument of getsockopt() amongst other things. This is now |
| 2301 | configurable by a macro called SOCKLEN_T which defaults to socklen_t, but |
| 2302 | can be set for individual OS. I have set it for SunOS5, OSF1, and |
| 2303 | Unixware7. Current versions of SunOS5 (aka Solaris) do have socklen_t, but |
| 2304 | some earlier ones do not. |
| 2305 | |
| 2306 | 7. Change 4.30/15 was not doing the test caselessly. |
| 2307 | |
| 2308 | 8. The standard form for an IPv6 address literal was being rejected by address |
| 2309 | parsing in, for example, MAIL and RCPT commands. An example of this kind of |
| 2310 | address is [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts |
| 2311 | this, as well as the form without the "IPv6" on the front (but only when |
| 2312 | address literals are enabled, of course). |
| 2313 | |
| 2314 | 9. Added some casts to avoid compiler warnings in OS/os.c-Linux. |
| 2315 | |
| 2316 | 10. Exim crashed if a message with an empty sender address specified by -f |
| 2317 | encountered a router with an errors_to setting. This could be provoked only |
| 2318 | by a command such as |
| 2319 | |
| 2320 | exim -f "" ... |
| 2321 | |
| 2322 | where an empty string was supplied; "<>" did not hit this bug. |
| 2323 | |
| 2324 | 11. Installed PCRE release 4.5. |
| 2325 | |
| 2326 | 12. If EHLO/HELO was rejected by an ACL, the value of $sender_helo_name |
| 2327 | remained set. It is now erased. |
| 2328 | |
| 2329 | 13. exiqgrep wasn't working on MacOS X because it didn't correctly compute |
| 2330 | times from message ids (which are base 36 rather than the normal 62). |
| 2331 | |
| 2332 | 14. "Expected" SMTP protocol errors that can arise when PIPELINING is in use |
| 2333 | were being counted as actual protocol errors, and logged if the log |
| 2334 | selector +smtp_protocol_error was set. One cannot be perfect in this test, |
| 2335 | but now, if PIPELINING has been advertised, RCPT following a rejected MAIL, |
| 2336 | and DATA following a set of rejected RCPTs do not count as protocol errors. |
| 2337 | In other words, Exim assumes they were pipelined, though this may not |
| 2338 | actually be the case. Of course, in all cases the client gets an |
| 2339 | appropriate error code. |
| 2340 | |
| 2341 | 15. If a lookup fails in an ACL condition, a message about the failure may |
| 2342 | be available; it is used if testing the ACL cannot continue, because most |
| 2343 | such messages specify what the cause of the deferral is. However, some |
| 2344 | messages (e.g. "MYSQL: no data found") do not cause a defer. There was bug |
| 2345 | that caused an old message to be retained and used if a later statement |
| 2346 | caused a defer, replacing the real cause of the deferral. |
| 2347 | |
| 2348 | 16. If an IP address had so many PTR records that the DNS lookup buffer |
| 2349 | was not large enough to hold them, Exim could crash while trying to process |
| 2350 | the truncated data. It now detects and logs this case. |
| 2351 | |
| 2352 | 17. Further to 4.21/58, another change has been made: if (and only if) the |
| 2353 | first line of a message (the first header line) ends with CRLF, a bare LF |
| 2354 | in a subsequent header line has a space inserted after it, so as not to |
| 2355 | terminate the header. |
| 2356 | |
| 2357 | 18. Refactoring: tidied an ugly bit of code in appendfile that copied data |
| 2358 | unnecessarily, used atoi() instead of strtol(), and didn't check the |
| 2359 | termination when getting file sizes from file names by regex. |
| 2360 | |
| 2361 | 19. Completely re-implemented the support for maildirsize files, in the light |
| 2362 | of a number of problems with the previous contributed implementation |
| 2363 | (4.30/29). In particular: |
| 2364 | |
| 2365 | . If the quota is zero, the maildirsize file is maintained, but no quota is |
| 2366 | imposed. |
| 2367 | |
| 2368 | . If the maildir directory does not exist, it is created before any attempt |
| 2369 | to write a maildirsize file. |
| 2370 | |
| 2371 | . The quota value in the file is just a cache; if the quota is changed in |
| 2372 | the transport, the new value overrides. |
| 2373 | |
| 2374 | . A regular expression is available for excluding directories from the |
| 2375 | count. |
| 2376 | |
| 2377 | 20. The autoreply transport checks the characters in options that define the |
| 2378 | message's headers; it allows continued headers, but it was checking with |
| 2379 | isspace() after an embedded newline instead of explicitly looking for a |
| 2380 | space or a tab. |
| 2381 | |
| 2382 | 21. If all the "regular" hosts to which an address was routed had passed their |
| 2383 | expiry times, and had not reached their retry times, the address was |
| 2384 | bounced, even if fallback hosts were defined. Now Exim should go on to try |
| 2385 | the fallback hosts. |
| 2386 | |
| 2387 | 22. Increased buffer sizes in the callout code from 1024 to 4096 to match the |
| 2388 | equivalent code in the SMTP transport. Some hosts send humungous responses |
| 2389 | to HELO/EHLO, more than 1024 it seems. |
| 2390 | |
| 2391 | 23. Refactoring: code in filter.c used (void *) for "any old type" but this |
| 2392 | gives compiler warnings in some environments. I've now done it "properly", |
| 2393 | using a union. |
| 2394 | |
| 2395 | 24. The replacement for inet_ntoa() that is used with gcc on IRIX systems |
| 2396 | (because of problems with the built-in one) was declared to return uschar * |
| 2397 | instead of char *, causing compiler failure. |
| 2398 | |
| 2399 | 25. Fixed a file descriptor leak when processing alias/forward files. |
| 2400 | |
| 2401 | 26. Fixed a minor format string issue in dbfn.c. |
| 2402 | |
| 2403 | 27. Typo in exim.c: ("dmbnz" for "dbmnz"). |
| 2404 | |
| 2405 | 28. If a filter file refered to $h_xxx or $message_headers, and the headers |
| 2406 | contained RFC 2047 "words", Exim's memory could, under certain conditions, |
| 2407 | become corrupted. |
| 2408 | |
| 2409 | 29. When a sender address is verified, it is cached, to save repeating the test |
| 2410 | when there is more than one recipient in a message. However, when the |
| 2411 | verification involves a callout, it is possible for different callout |
| 2412 | options to be set for different recipients. It is too complicated to keep |
| 2413 | track of this in the cache, so now Exim always runs a verification when a |
| 2414 | callout is required, relying on the callout cache for the optimization. |
| 2415 | The overhead is duplication of the address routing, but this should not be |
| 2416 | too great. |
| 2417 | |
| 2418 | 30. Fixed a bug in callout caching. If a RCPT command caused the sender address |
| 2419 | to be verified with callout=postmaster, and the main callout worked but the |
| 2420 | postmaster check failed, the verification correctly failed. However, if a |
| 2421 | subsequent RCPT command asked for sender verification *without* the |
| 2422 | postmaster check, incorrect caching caused this verification also to fail, |
| 2423 | incorrectly. |
| 2424 | |
| 2425 | 31. Exim caches DNS lookup failures so as to avoid multiple timeouts; however, |
| 2426 | it was not caching the DNS options (qualify_single, search_parents) that |
| 2427 | were used when the lookup failed. A subsequent lookup with different |
| 2428 | options therefore always gave the same answer, though there were cases |
| 2429 | where it should not have. (Example: a "domains = !$mx_any" option on a |
| 2430 | dnslookup router: the "domains" option is always processed without any |
| 2431 | widening, but the router might have qualify_single set.) Now Exim uses the |
| 2432 | cached value only when the same options are set. |
| 2433 | |
| 2434 | 32. Added John Jetmore's "exipick" utility to the distribution. |
| 2435 | |
| 2436 | 33. GnuTLS: When an attempt to start a TLS session fails for any reason other |
| 2437 | than a timeout (e.g. a certificate is required, and is not provided), an |
| 2438 | Exim server now closes the connection immediately. Previously it waited for |
| 2439 | the client to close - but if the client is SSL, it seems that they each |
| 2440 | wait for each other, leading to a delay before one of them times out. |
| 2441 | |
| 2442 | 34: GnuTLS: Updated the code to use the new GnuTLS 1.0.0 API. I have not |
| 2443 | maintained 0.8.x compatibility because I don't think many are using it, and |
| 2444 | it is clearly obsolete. |
| 2445 | |
| 2446 | 35. Added TLS support for CRLs: a tls_crl global option and one for the smtp |
| 2447 | transport. |
| 2448 | |
| 2449 | 36. OpenSSL: $tls_certificate_verified was being set to 1 even if the |
| 2450 | client certificate was expired. A simple patch fixes this, though I don't |
| 2451 | understand the full logic of why the verify callback is called multiple |
| 2452 | times. |
| 2453 | |
| 2454 | 37. OpenSSL: a patch from Robert Roselius: "Enable client-bug workaround. |
| 2455 | Versions of OpenSSL as of 0.9.6d include a 'CBC countermeasure' feature, |
| 2456 | which causes problems with some clients (such as the Certicom SSL Plus |
| 2457 | library used by Eudora). This option, SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS, |
| 2458 | disables the coutermeasure allowing Eudora to connect." |
| 2459 | |
| 2460 | 38. Exim was not checking that a write() to a log file succeeded. This could |
| 2461 | lead to Bad Things if a log got too big, in particular if it hit a file |
| 2462 | size limit. Exim now panics and dies if it cannot write to a log file, just |
| 2463 | as it does if it cannot open a log file. |
| 2464 | |
| 2465 | 39. Modified OS/Makefile-Linux so that it now contains |
| 2466 | |
| 2467 | CFLAGS=-O -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE |
| 2468 | |
| 2469 | The two -D definitions ensure that Exim is compiled with large file |
| 2470 | support, which makes it possible to handle log files that are bigger than |
| 2471 | 2^31. |
| 2472 | |
| 2473 | 40. Fixed a subtle caching bug: if (in an ACL or a set of routers, for |
| 2474 | instance) a domain was checked against a named list that involved a lookup, |
| 2475 | causing $domain_data to be set, then another domain was checked against the |
| 2476 | same list, then the first domain was re-checked, the value of $domain_data |
| 2477 | after the final check could be wrong. In particular, if the second check |
| 2478 | failed, it could be set empty. This bug probably also applied to |
| 2479 | $localpart_data. |
| 2480 | |
| 2481 | 41. The strip_trailing_dot option was not being applied to the address given |
| 2482 | with the -f command-line option. |
| 2483 | |
| 2484 | 42. The code for reading a message's header from the spool was incrementing |
| 2485 | $received_count, but never initializing it. This meant that the value was |
| 2486 | incorrect (doubled) while delivering a message in the same process in which |
| 2487 | it was received. In the most common configuration of Exim, this never |
| 2488 | happens - a fresh exec is done - but it can happen when |
| 2489 | deliver_drop_privilege is set. |
| 2490 | |
| 2491 | 43. When Exim logs an SMTP synchronization error - client data sent too soon - |
| 2492 | it now includes up to 150 characters of the unexpected data in the log |
| 2493 | line. |
| 2494 | |
| 2495 | 44. The exim_dbmbuild utility uses fixed size buffers for reading input lines |
| 2496 | and building data strings. The size of both of these buffers was 10 000 |
| 2497 | bytes - far larger than anybody would *ever* want, thought I. Needless to |
| 2498 | say, somebody hit the limit. I have increased the maximum line length to |
| 2499 | 20 000 and the maximum data length of concatenated lines to 100 000. I have |
| 2500 | also fixed two bugs, because there was no checking on these buffers. Tsk, |
| 2501 | tsk. Now exim_dbmbuild gives a message and exits with an error code if a |
| 2502 | buffer is too small. |
| 2503 | |
| 2504 | 45. The exim_dbmbuild utility did not support quoted keys, as Exim does in |
| 2505 | lsearch lookups. Now it does. |
| 2506 | |
| 2507 | 46. When parsing a route_list item in a manualroute router, a fixed-length |
| 2508 | buffer was used for the list of hosts. I made this 1024 bytes long, |
| 2509 | thinking that nobody would ever have a list of hosts that long. Wrong. |
| 2510 | Somebody had a whole pile of complicated expansion conditions, and the |
| 2511 | string was silently truncated, leading to an expansion error. It turns out |
| 2512 | that it is easier to change to an unlimited length (owing to other changes |
| 2513 | that have happened since this code was originally written) than to build |
| 2514 | structure for giving a limitation error. The length of the item that |
| 2515 | expands into the list of hosts is now unlimited. |
| 2516 | |
| 2517 | 47. The lsearch lookup could not handle data where the length of text line was |
| 2518 | more than 4095 characters. Such lines were truncated, leading to shortened |
| 2519 | data being returned. It should now handle lines of any length. |
| 2520 | |
| 2521 | 48. Minor wording revision: "cannot test xxx in yyy ACL" becomes "cannot test |
| 2522 | xxx condition in yyy ACL" (e.g. "cannot test domains condition in DATA |
| 2523 | ACL"). |
| 2524 | |
| 2525 | 49. Cosmetic tidy to scripts like exicyclog that are generated by globally |
| 2526 | replacing strings such as BIN_DIRECTORY in a source file: the replacement |
| 2527 | no longer happens in comment lines. A list of replacements is now placed |
| 2528 | at the head of all of the source files, except those whose only change is |
| 2529 | to replace PERL_COMMAND in the very first #! line. |
| 2530 | |
| 2531 | 50. Replaced the slow insertion sort in queue.c, for sorting the list of |
| 2532 | messages on the queue, with a bottom-up merge sort, using code contributed |
| 2533 | by Michael Haardt. This should make operations like -bp somewhat faster on |
| 2534 | large queues. It won't affect queue runners, except when queue_run_in_order |
| 2535 | is set. |
| 2536 | |
| 2537 | 51. Installed eximstats 1.31 in the distribution. |
| 2538 | |
| 2539 | 52. Added support for SRV lookups to the dnslookup router. |
| 2540 | |
| 2541 | 53. If an ACL referred to $message_body or $message_body_end, the value was not |
| 2542 | reset for any messages that followed in the same SMTP session. |
| 2543 | |
| 2544 | 54. The store-handling optimization for building very long strings was not |
| 2545 | differentiating between the different store pools. I don't think this |
| 2546 | actually made any difference in practice, but I've tidied it. |
| 2547 | |
| 2548 | 55. While running the routers to verify a sender address, $sender_address |
| 2549 | was still set to the sender address. This is wrong, because when routing to |
| 2550 | send a bounce to the sender, it would be empty. Therefore, I have changed |
| 2551 | it so that, while verifying a sender address, $sender_address is set to <>. |
| 2552 | (There is no change to what happens when verifying a recipient address.) |
| 2553 | |
| 2554 | 56. After finding MX (or SRV) records, Exim was doing a DNS lookup for the |
| 2555 | target A or AAAA records (if not already returned) without resetting the |
| 2556 | qualify_single or search_parents options of the DNS resolver. These are |
| 2557 | inappropriate in this case because the targets of MX and SRV records must |
| 2558 | be FQDNs. A broken DNS record could cause trouble if it happened to have a |
| 2559 | target that, when qualified, matched something in the local domain. These |
| 2560 | two options are now turned off when doing these lookups. |
| 2561 | |
| 2562 | 57. It seems that at least some releases of Reiserfs (which does not have the |
| 2563 | concept of a fixed number of inodes) returns zero and not -1 for the |
| 2564 | number of available inodes. This interacted badly with check_spool_inodes, |
| 2565 | which assumed that -1 was the "no such thing" setting. What I have done is |
| 2566 | to check that the total number of inodes is greater than zero before doing |
| 2567 | the test of how many are available. |
| 2568 | |
| 2569 | 58. When a "warn" ACL statement has a log_message modifier, the message is |
| 2570 | remembered, and not repeated. This is to avoid a lot of repetition when a |
| 2571 | message has many recipients that cause the same warning to be written. |
| 2572 | Howewer, Exim was preserving the list of already written lines for an |
| 2573 | entire SMTP session, which doesn't seem right. The memory is now reset if a |
| 2574 | new message is started. |
| 2575 | |
| 2576 | 59. The "rewrite" debugging flag was not showing the result of rewriting in the |
| 2577 | debugging output unless log_rewrite was also set. |
| 2578 | |
| 2579 | 60. Avoid a compiler warning on 64-bit systems in dsearch.c by avoiding the use |
| 2580 | of (int)(handle) when we know that handle contains (void *)(-1). |
| 2581 | |
| 2582 | 61. The Exim daemon panic-logs an error return when it closes the incoming |
| 2583 | connection. However "connection reset by peer" seems to be common, and |
| 2584 | isn't really an error worthy of noting specially, so that particular error |
| 2585 | is no long logged. |
| 2586 | |
| 2587 | 62. When Exim is trying to find all the local interfaces, it used to panic and |
| 2588 | die if the ioctl to get the interface flags failed. However, it seems that |
| 2589 | on at least one OS (Solaris 9) it is possible to have an interface that is |
| 2590 | included in the list of interfaces, but for which you get a failure error |
| 2591 | for this call. This happens when the interface is not "plumbed" into a |
| 2592 | protocol (i.e. neither IPv4 nor IPv6). I've changed the code so that a |
| 2593 | failure of the "get flags" call assumes that the interface is down. |
| 2594 | |
| 2595 | 63. Added a ${eval10: operator, which assumes all numbers are decimal. This |
| 2596 | makes life easier for people who are doing arithmetic on fields extracted |
| 2597 | from dates, where you often get leading zeros that should not be |
| 2598 | interpreted as octal. |
| 2599 | |
| 2600 | 64. Added qualify_domain to the redirect router, to override the global |
| 2601 | setting. |
| 2602 | |
| 2603 | 65. If a pathologically long header line contained very many addresses (the |
| 2604 | report of this problem mentioned 10 000) and each of them was rewritten, |
| 2605 | Exim could use up a very large amount of memory. (It kept on making new |
| 2606 | copies of the header line as it rewrote, and never released the old ones.) |
| 2607 | At the expense of a bit more processing, the header rewriting function has |
| 2608 | been changed so that it no longer eats memory in this way. |
| 2609 | |
| 2610 | 66. The generation of the Received: header has been moved from the time that a |
| 2611 | message starts to be received, to the time that it finishes. The timestamp |
| 2612 | in the Received: header should now be very close to that of the <= log |
| 2613 | line. There are two side-effects of this change: |
| 2614 | |
| 2615 | (a) If a message is rejected by a DATA or non-SMTP ACL or local_scan(), the |
| 2616 | logged header lines no longer include the local Received: line, because |
| 2617 | it has not yet been created. The same applies to a copy of the message |
| 2618 | that is returned to a non-SMTP sender when a message is rejected. |
| 2619 | |
| 2620 | (b) When a filter file is tested using -bf, no additional Received: header |
| 2621 | is added to the test message. After some thought, I decided that this |
| 2622 | is a bug fix. |
| 2623 | |
| 2624 | This change does not affect the value of $received_for. It is still set |
| 2625 | after address rewriting, but before local_scan() is called. |
| 2626 | |
| 2627 | 67. Installed the latest Cygwin-specific files from the Cygwin maintainer. |
| 2628 | |
| 2629 | 68. GnuTLS: If an empty file is specified for tls_verify_certificates, GnuTLS |
| 2630 | gave an unhelpful panic error message, and a defer error. I have managed to |
| 2631 | change this behaviour so that it now rejects any supplied certificate, |
| 2632 | which seems right, as the list of acceptable certificates is empty. |
| 2633 | |
| 2634 | 69. OpenSSL: If an empty file is specified for tls_verify_certificates, OpenSSL |
| 2635 | gave an unhelpful defer error. I have not managed to make this reject any |
| 2636 | supplied certificates, but the error message it gives is "no certificate |
| 2637 | supplied", which is not helpful. |
| 2638 | |
| 2639 | 70. exigrep's output now also includes lines that are not associated with any |
| 2640 | message, but which match the given pattern. Implemented by a patch from |
| 2641 | Martin Sluka, which also tidied up the Perl a bit. |
| 2642 | |
| 2643 | 71. Recipient callout verification, like sender verification, was using <> in |
| 2644 | the MAIL FROM command. This isn't really the right thing, since the actual |
| 2645 | sender may affect whether the remote host accepts the recipient or not. I |
| 2646 | have changed it to use the actual sender in the callout; this means that |
| 2647 | the cache record is now keyed on a recipient/sender pair, not just the |
| 2648 | recipient address. There doesn't seem to be a real danger of callout loops, |
| 2649 | since a callout by the remote host to check the sender would use <>. |
| 2650 | [SEE ABOVE: changed after hitting problems.] |
| 2651 | |
| 2652 | 72. Exim treats illegal SMTP error codes that do not begin with 4 or 5 as |
| 2653 | temporary errors. However, in the case of such a code being given after |
| 2654 | the end of a data transmission (i.e. after ".") Exim was failing to write |
| 2655 | a retry record for the message. (Yes, there was some broken host that was |
| 2656 | actually sending 8xx at this point.) |
| 2657 | |
| 2658 | 73. An unknown lookup type in a host list could cause Exim to panic-die when |
| 2659 | the list was checked. (An example that provoked this was putting <; in the |
| 2660 | middle of a list instead of at the start.) If this happened during a DATA |
| 2661 | ACL check, a -D file could be left lying around. This kind of configuration |
| 2662 | error no longer causes Exim to die; instead it causes a defer errror. The |
| 2663 | incident is still logged to the main and panic logs. |
| 2664 | |
| 2665 | 74. Buglet left over from Exim 3 conversion. The message "too many messages |
| 2666 | in one connection" was written to the rejectlog but not the mainlog, except |
| 2667 | when address rewriting (yes!) was being logged. |
| 2668 | |
| 2669 | 75. Added write_rejectlog option. |
| 2670 | |
| 2671 | 76. When a system filter was run not as root (that is, when system_filter_user |
| 2672 | was set), the values of the $n variables were not being returned to the |
| 2673 | main process; thus, they were not subsequently available in the $sn |
| 2674 | variables. |
| 2675 | |
| 2676 | 77. Added +return_path_on_delivery log selector. |
| 2677 | |
| 2678 | 78. A connection timeout was being treated differently from recipients deferred |
| 2679 | when testing hosts_max_try with a message that was older than the host's |
| 2680 | retry timeout. (The host should not be counted, thus allowing all hosts to |
| 2681 | be tried at least once before bouncing.) This may have been the cause of an |
| 2682 | occasionally reported bug whereby a message would remain on the queue |
| 2683 | longer than the retry timeout, but would be bounced if a delivery was |
| 2684 | forced. I say "may" because I never totally pinned down the problem; |
| 2685 | setting up timeout/retry tests is difficult. See also the next item. |
| 2686 | |
| 2687 | 79. The ultimate address timeout was not being applied to errors that involved |
| 2688 | a combination of host plus message (for example, a timeout on a MAIL |
| 2689 | command). When an address resolved to a number of possible hosts, and they |
| 2690 | were not all tried for each delivery (e.g. because of hosts_max_try), a |
| 2691 | message could remain on the queue longer than the retry timeout. |
| 2692 | |
| 2693 | 80. Sieve bug: "stop" inside "elsif" was broken. Applied a patch from Michael |
| 2694 | Haardt. |
| 2695 | |
| 2696 | 81. Fixed an obscure SMTP outgoing bug which required at least the following |
| 2697 | conditions: (a) there was another message waiting for the same server; |
| 2698 | (b) the server returned 5xx to all RCPT commands in the first message so |
| 2699 | that the message was not completed; (c) the server dropped the connection |
| 2700 | or gave a negative response to the RSET that Exim sends to abort the |
| 2701 | transaction. The observed case was a dropped connection after DATA that had |
| 2702 | been sent in pipelining mode. That is, the server had advertised PIPELINING |
| 2703 | but was not implementing it correctly. The effect of the bug was incorrect |
| 2704 | behaviour, such as trying another host, and this could lead to a crash. |
| 2705 | |
| 2706 | |
| 2707 | Exim version 4.30 |
| 2708 | ----------------- |
| 2709 | |
| 2710 | 1. The 3rd arguments to getsockname(), getpeername(), and accept() in exim.c |
| 2711 | and daemon.c were passed as pointers to ints; they should have been |
| 2712 | pointers to socklen_t variables (which are typically unsigned ints). |
| 2713 | |
| 2714 | 2. Some signed/unsigned type warnings in the os.c file for Linux have been |
| 2715 | fixed. |
| 2716 | |
| 2717 | 3. Fixed a really odd bug that affected only the testing scheme; patching a |
| 2718 | certain fixed string in the binary changed the value of another string that |
| 2719 | happened to be identical to the end of the original first string. |
| 2720 | |
| 2721 | 4. When gethostbyname() (or equivalent) is passed an IP address as a "host |
| 2722 | name", it returns that address as the IP address. On some operating |
| 2723 | systems (e.g. Solaris), it also passes back the IP address string as the |
| 2724 | "host name". However, on others (e.g. Linux), it passes back an empty |
| 2725 | string. Exim wasn't checking for this, and was changing the host name to an |
| 2726 | empty string, assuming it had been canonicized. |
| 2727 | |
| 2728 | 5. Although rare, it is permitted to have more than one PTR record for a given |
| 2729 | IP address. I thought that gethostbyaddr() or getipnodebyaddr() always gave |
| 2730 | all the names associated with an address, because they do in Solaris. |
| 2731 | However, it seems that they do not in Linux for data that comes from the |
| 2732 | DNS. If an address in /etc/hosts has multiple names, they _are_ all given. |
| 2733 | I found this out when I moved to a new Linux workstation and tried to run |
| 2734 | the Exim test suite. |
| 2735 | |
| 2736 | To get round this problem I have changed the code so that it now does its |
| 2737 | own call to the DNS to look up PTR records when searching for a host name. |
| 2738 | If nothing can be found in the DNS, it tries gethostbyaddr(), so that |
| 2739 | addresses that are only in /etc/hosts are still found. |
| 2740 | |
| 2741 | This behaviour is, however, controlled by an option called host_lookup_ |
| 2742 | order, which defaults to "bydns:byaddr". If people want to use the other |
| 2743 | order, or indeed, just use one or the other means of lookup, they can |
| 2744 | specify it in this variable. |
| 2745 | |
| 2746 | 6. If a PTR record yields an empty name, Exim treats it as non-existent. In |
| 2747 | some operating systems, this comes back from gethostbyaddr() as an empty |
| 2748 | string, and this is what Exim used to test for. However, it seems that in |
| 2749 | other systems, "." is yielded. Exim now tests for this case too. |
| 2750 | |
| 2751 | 7. The values of check_spool_space and check_log_space are now held internally |
| 2752 | as a number of kilobytes instead of an absolute number of bytes. If a |
| 2753 | numbers is specified without 'K' or 'M', it is rounded up to the nearest |
| 2754 | kilobyte. This means that much larger values can be stored. |
| 2755 | |
| 2756 | 8. Exim monitor: an attempt to get the action menu when not actually pointing |
| 2757 | at a message produces an empty menu entitled "No message selected". This |
| 2758 | works on Solaris (OpenWindows). However, XFree86 does not like a menu with |
| 2759 | no entries in it ("Shell widget menu has zero width and/or height"). So I |
| 2760 | have added a single, blank menu entry in this case. |
| 2761 | |
| 2762 | 9. Added ${quote_local_part. |
| 2763 | |
| 2764 | 10. MIME decoding is now applied to the contents of Subject: header lines when |
| 2765 | they are logged. |
| 2766 | |
| 2767 | 11. Now that a reference to $sender_host_address automatically causes a reverse |
| 2768 | lookup to occur if necessary (4.13/18), there is no need to arrange for a |
| 2769 | host lookup before query-style lookups in lists that might use this |
| 2770 | variable. This has therefore been abolished, and the "net-" prefix is no |
| 2771 | longer necessary for query-style lookups. |
| 2772 | |
| 2773 | 12. The Makefile for SCO_SV contained a setting of LDFLAGS. This appears to |
| 2774 | have been a typo for LFLAGS, so it has been changed. |
| 2775 | |
| 2776 | 13. The install script calls Exim with "-C /dev/null" in order to find the |
| 2777 | version number. If ALT_CONFIG_PREFIX was set, this caused an error message |
| 2778 | to be output. Howeve, since Exim outputs its version number before the |
| 2779 | error, it didn't break the script. It just looked ugly. I fixed this by |
| 2780 | always allowing "-C /dev/null" if the caller is root. |
| 2781 | |
| 2782 | 14. Ignore overlarge ACL variable number when reading spool file - insurance |
| 2783 | against a later release with more variables having written the file. |
| 2784 | |
| 2785 | 15. The standard form for an IPv6 address literal was being rejected by EHLO. |
| 2786 | Example: [IPv6:2002:c1ed:8229:10:202:2dff:fe07:a42a]. Exim now accepts |
| 2787 | this, as well as the form without the "IPv6" on the front. |
| 2788 | |
| 2789 | 16. Added CHOWN_COMMAND=/usr/sbin/chown and LIBS=-lresolv to the |
| 2790 | OS/Makefile-Darwin file. |
| 2791 | |
| 2792 | 17. Fixed typo in lookups/ldap.c: D_LOOKUP should be D_lookup. This applied |
| 2793 | only to LDAP libraries that do not have LDAP_OPT_DEREF. |
| 2794 | |
| 2795 | 18. After change 4.21/52, "%ld" was used to format the contents of the $inode |
| 2796 | variable. However, some OS use ints for inodes. I've added cast to long int |
| 2797 | to get rid of the compiler warning. |
| 2798 | |
| 2799 | 19. I had forgotten to lock out "/../" in configuration file names when |
| 2800 | ALT_CONFIG_PREFIX was set. |
| 2801 | |
| 2802 | 20. Routers used for verification do not need to specify transports. However, |
| 2803 | if such a router generated a host list, and callout was configured, Exim |
| 2804 | crashed, because it could not find a port number from the (non-existent) |
| 2805 | transport. It now assumes port 25 in this circumstance. |
| 2806 | |
| 2807 | 21. Added the -t option to exigrep. |
| 2808 | |
| 2809 | 22. If LOOKUP_LSEARCH is defined, all three linear search methods (lsearch, |
| 2810 | wildlsearch, nwildlsearch) are compiled. LOOKUP_WILDLSEARCH and LOOKUP_ |
| 2811 | NWILDLSEARCH are now obsolete, but retained for compatibility. If either of |
| 2812 | them is set, LOOKUP_LSEARCH is forced. |
| 2813 | |
| 2814 | 23. "exim -bV" now outputs a list of lookups that are included in the binary. |
| 2815 | |
| 2816 | 24. Added sender and host information to the "rejected by local_scan()" log |
| 2817 | line; previously there was no indication of these. |
| 2818 | |
| 2819 | 25. Added .include_if_exists. |
| 2820 | |
| 2821 | 26. Change 3.952/11 added an explicit directory sync on top of a file sync for |
| 2822 | Linux. It turns out that not all file systems support this. Apparently some |
| 2823 | versions of NFS do not. (It's rare to put Exim's spool on NFS, but people |
| 2824 | do it.) To cope with this, the error EINVAL, which means that sync-ing is |
| 2825 | not supported on the file descriptor, is now ignored when Exim is trying to |
| 2826 | sync a directory. This applies only to Linux. |
| 2827 | |
| 2828 | 27. Added -DBIND_8_COMPAT to the CLFAGS setting for Darwin. |
| 2829 | |
| 2830 | 28. In Darwin (MacOS X), the PAM headers are in /usr/include/pam and not in |
| 2831 | /usr/include/security. There's now a flag in OS/os.h-Darwin to cope with |
| 2832 | this. |
| 2833 | |
| 2834 | 29. Added support for maildirsize files from supplied patch (modified a bit). |
| 2835 | |
| 2836 | 30. The use of :fail: followed by an empty string could lead Exim to respond to |
| 2837 | sender verification failures with (e.g.): |
| 2838 | |
| 2839 | 550 Verification failed for <xxx> |
| 2840 | 550 Sender verify failed |
| 2841 | |
| 2842 | where the first response line was missing the '-' that indicates it is not |
| 2843 | the final line of the response. |
| 2844 | |
| 2845 | 31. The loop for finding the name of the user that called Exim had a hardwired |
| 2846 | limit of 10; it now uses the value of finduser_retries, which is used for |
| 2847 | all other user lookups. |
| 2848 | |
| 2849 | 32. Added $received_count variable, available in data and not_smtp ACLs, and at |
| 2850 | delivery time. |
| 2851 | |
| 2852 | 33. Exim was neglecting to zero errno before one call of strtol() when |
| 2853 | expanding a string and expecting an integer value. On some systems this |
| 2854 | resulted in spurious "integer overflow" errors. Also, it was casting the |
| 2855 | result into an int without checking. |
| 2856 | |
| 2857 | 34. Testing for a connection timeout using "timeout_connect" in the retry rules |
| 2858 | did not work. The code looks as if it has *never* worked, though it appears |
| 2859 | to have been documented since at least releast 1.62. I have made it work. |
| 2860 | |
| 2861 | 35. The "timeout_DNS" error in retry rules, also documented since at least |
| 2862 | 1.62, also never worked. As it isn't clear exactly what this means, and |
| 2863 | clearly it isn't a major issue, I have abolished the feature by treating it |
| 2864 | as "timeout", and writing a warning to the main and panic logs. |
| 2865 | |
| 2866 | 36. The display of retry rules for -brt wasn't always showing the error code |
| 2867 | correctly. |
| 2868 | |
| 2869 | 37. Added new error conditions to retry rules: timeout_A, timeout_MX, |
| 2870 | timeout_connect_A, timeout_connect_MX. |
| 2871 | |
| 2872 | 38. Rewriting the envelope sender at SMTP time did not allow it to be rewritten |
| 2873 | to the empty sender. |
| 2874 | |
| 2875 | 39. The daemon was not analysing the content of -oX till after it had closed |
| 2876 | stderr and disconnected from the controlling terminal. This meant that any |
| 2877 | syntax errors were only noted on the panic log, and the return code from |
| 2878 | the command was 0. By re-arranging the code a little, I've made the |
| 2879 | decoding happen first, so such errors now appear on stderr, and the return |
| 2880 | code is 1. However, the actual setting up of the sockets still happens in |
| 2881 | the disconnected process, so errors there are still only recorded on the |
| 2882 | panic log. |
| 2883 | |
| 2884 | 40. A daemon listener on a wildcard IPv6 socket that also accepts IPv4 |
| 2885 | connections (as happens on some IP stacks) was logged at start up time as |
| 2886 | just listening for IPv6. It now logs "IPv6 with IPv4". This differentiates |
| 2887 | it from "IPv6 and IPv4", which means that two separate sockets are being |
| 2888 | used. |
| 2889 | |
| 2890 | 41. The debug output for gethostbyname2() or getipnodebyname() failures now |
| 2891 | says whether AF_INET or AF_INET6 was passed as an argument. |
| 2892 | |
| 2893 | 42. Exiwhat output was messed up when time zones were included in log |
| 2894 | timestamps. |
| 2895 | |
| 2896 | 43. Exiwhat now gives more information about the daemon's listening ports, |
| 2897 | and whether -tls-on-connect was used. |
| 2898 | |
| 2899 | 44. The "port" option of the smtp transport is now expanded. |
| 2900 | |
| 2901 | 45. A "message" modifier in a "warn" statement in a non-message ACL was being |
| 2902 | silently ignored. Now an error message is written to the main and panic |
| 2903 | logs. |
| 2904 | |
| 2905 | 46. There's a new ACL modifier called "logwrite" which writes to a log file |
| 2906 | as soon as it is encountered. |
| 2907 | |
| 2908 | 47. Added $local_user_uid and $local_user_gid at routing time. |
| 2909 | |
| 2910 | 48. Exim crashed when trying to verify a sender address that was being |
| 2911 | rewritten to "<>". |
| 2912 | |
| 2913 | 49. Exim was recognizing only a space character after ".include". It now also |
| 2914 | recognizes a tab character. |
| 2915 | |
| 2916 | 50. Fixed several bugs in the Perl script that creates the exim.8 man page by |
| 2917 | extracting the relevant information from the specification. The man page no |
| 2918 | longer contains scrambled data for the -d option, and I've added a section |
| 2919 | at the front about calling Exim under different names. |
| 2920 | |
| 2921 | 51. Added "extra_headers" argument to the "mail" command in filter files. |
| 2922 | |
| 2923 | 52. Redirecting mail to an unqualified address in a Sieve filter caused Exim to |
| 2924 | crash. |
| 2925 | |
| 2926 | 53. Installed eximstats 1.29. |
| 2927 | |
| 2928 | 54. Added transport_filter_timeout as a generic transport option. |
| 2929 | |
| 2930 | 55. Exim no longer adds an empty Bcc: header to messages that have no To: or |
| 2931 | Cc: header lines. This was required by RFC 822, but it not required by RFC |
| 2932 | 2822. |
| 2933 | |
| 2934 | 56. Exim used to add From:, Date:, and Message-Id: header lines to any |
| 2935 | incoming messages that did not have them. Now it does so only if the |
| 2936 | message originates locally, that is, if there is no associated remote host |
| 2937 | address. When Resent- header lines are present, this applies to the Resent- |
| 2938 | lines rather than the non-Resent- lines. |
| 2939 | |
| 2940 | 57. Drop incoming SMTP connection after too many syntax or protocol errors. The |
| 2941 | limit is controlled by smtp_max_synprot_errors, defaulting to 3. |
| 2942 | |
| 2943 | 58. Messages for configuration errors now include the name of the main |
| 2944 | configuration file - useful now that there may be more than one file in a |
| 2945 | list (.included file names were always shown). |
| 2946 | |
| 2947 | 59. Change 4.21/82 (run initgroups() when starting the daemon) causes problems |
| 2948 | for those rare installations that do not start the daemon as root or run it |
| 2949 | setuid root. I've cut out the call to initgroups() if the daemon is not |
| 2950 | root at that time. |
| 2951 | |
| 2952 | 60. The Exim user and group can now be bound into the binary as text strings |
| 2953 | that are looked up at the start of Exim's processing. |
| 2954 | |
| 2955 | 61. Applied a small patch for the Interbase code, supplied by Ard Biesheuvel. |
| 2956 | |
| 2957 | 62. Added $mailstore_basename variable. |
| 2958 | |
| 2959 | 63. Installed patch to sieve.c from Michael Haardt. |
| 2960 | |
| 2961 | 64. When Exim failed to open the panic log after failing to open the main log, |
| 2962 | the original message it was trying to log was written to stderr and debug |
| 2963 | output, but if they were not available (the usual case in production), it |
| 2964 | was lost. Now it is written to syslog before the two lines that record the |
| 2965 | failures to open the logs. |
| 2966 | |
| 2967 | 65. Users' Exim filters run in subprocesses under the user's uid. It is |
| 2968 | possible for a "deliver" command or an alias in a "personal" command to |
| 2969 | provoke an address rewrite. If logging of address rewriting is configured, |
| 2970 | this fails because the process is not running as root or exim. There may be |
| 2971 | a better way of dealing with this, but for the moment (because 4.30 needs |
| 2972 | to be released), I have disabled address rewrite logging when running a |
| 2973 | filter in a non-root, non-exim process. |
| 2974 | |
| 2975 | |
| 2976 | Exim version 4.24 |
| 2977 | ----------------- |
| 2978 | |
| 2979 | 1. The buildconfig auxiliary program wasn't quoting the value set for |
| 2980 | HEADERS_CHARSET. This caused a compilation error complaining that 'ISO' was |
| 2981 | not defined. This bug was masked in 4.22 by the effect that was fixed in |
| 2982 | change 4.23/1. |
| 2983 | |
| 2984 | 2. Some messages that were rejected after a message id was allocated were |
| 2985 | shown as "incomplete" by exigrep. It no longer does this for messages that |
| 2986 | are rejected by local_scan() or the DATA or non-SMTP ACLs. |
| 2987 | |
| 2988 | 3. If a Message-ID: header used a domain literal in the ID, and Exim did not |
| 2989 | have allow_domain_literals set, the ID did not get logged in the <= line. |
| 2990 | Domain literals are now always recognized in Message-ID: header lines. |
| 2991 | |
| 2992 | 4. The first argument for a ${extract expansion item is the key name or field |
| 2993 | number. Leading and trailing spaces in this item were not being ignored, |
| 2994 | causing some misleading effects. |
| 2995 | |
| 2996 | 5. When deliver_drop_privilege was set, single queue runner processes started |
| 2997 | manually (i.e. by the command "exim -q") or by the daemon (which uses the |
| 2998 | same command in the process it spins off) were not dropping privilege. |
| 2999 | |
| 3000 | 6. When the daemon running as "exim" started a queue runner, it always |
| 3001 | re-executed Exim in the spun-off process. This is a waste of effort when |
| 3002 | deliver_drop_privilege is set. The new process now just calls the |
| 3003 | queue-runner function directly. |
| 3004 | |
| 3005 | |
| 3006 | Exim version 4.23 |
| 3007 | ----------------- |
| 3008 | |
| 3009 | 1. Typo in the src/EDITME file: it referred to HEADERS_DECODE_TO instead of |
| 3010 | HEADERS_CHARSET. |
| 3011 | |
| 3012 | 2. Change 4.21/73 introduced a bug. The pid file path set by -oP was being |
| 3013 | ignored. Though the use of -oP was forcing the writing of a pid file, it |
| 3014 | was always written to the default place. |
| 3015 | |
| 3016 | 3. If the message "no IP address found for host xxxx" is generated during |
| 3017 | incoming verification, it is now followed by identification of the incoming |
| 3018 | connection (so you can more easily find what provoked it). |
| 3019 | |
| 3020 | 4. Bug fix for Sieve filters: "stop" inside a block was not working properly. |
| 3021 | |
| 3022 | 5. Added some features to "harden" Exim a bit more against certain attacks: |
| 3023 | |
| 3024 | (a) There is now a build-time option called FIXED_NEVER_USERS that can |
| 3025 | be put in Local/Makefile. This is like the never_users runtime option, |
| 3026 | but it cannot be overridden. The default setting is "root". |
| 3027 | |
| 3028 | (b) If ALT_CONFIG_PREFIX is defined in Local/Makefile, it specifies a |
| 3029 | prefix string with which any file named in a -C command line option |
| 3030 | must start. |
| 3031 | |
| 3032 | (c) If ALT_CONFIG_ROOT_ONLY is defined in Local/Makefile, root privilege |
| 3033 | is retained for -C and -D only if the caller of Exim is root. Without |
| 3034 | it, the exim user may also use -C and -D and retain privilege. |
| 3035 | |
| 3036 | (d) If DISABLE_D_OPTION is defined in Local/Makefile, the use of the -D |
| 3037 | command line option is disabled. |
| 3038 | |
| 3039 | 6. Macro names set by the -D option must start with an upper case letter, just |
| 3040 | like macro names defined in the configuration file. |
| 3041 | |
| 3042 | 7. Added "dereference=" facility to LDAP. |
| 3043 | |
| 3044 | 8. Two instances of the typo "uknown" in the source files are fixed. |
| 3045 | |
| 3046 | 9. If a PERL_COMMAND setting in Local/Makefile was not at the start of a line, |
| 3047 | the Configure-Makefile script screwed up while processing it. |
| 3048 | |
| 3049 | 10. Incorporated PCRE 4.4. |
| 3050 | |
| 3051 | 11. The SMTP synchronization check was not operating right at the start of an |
| 3052 | SMTP session. For example, it could not catch a HELO sent before the client |
| 3053 | waited for the greeting. There is now a check for outstanding input at the |
| 3054 | point when the greeting is written. Because of the duplex, asynchronous |
| 3055 | nature of TCP/IP, it cannot be perfect - the incorrect input may be on its |
| 3056 | way, but not yet received, when the check is performed. |
| 3057 | |
| 3058 | 12. Added tcp_nodelay to make it possible to turn of the setting of TCP_NODELAY |
| 3059 | on TCP/IP sockets, because this apparently causes some broken clients to |
| 3060 | timeout. |
| 3061 | |
| 3062 | 13. Installed revised OS/Makefile-CYGWIN and OS/os.c-cygwin (the .h file was |
| 3063 | unchanged) from the Cygwin maintainer. |
| 3064 | |
| 3065 | 14. The code for -bV that shows what is in the binary showed "mbx" when maildir |
| 3066 | was supported instead of testing for mbx. Effectively a typo. |
| 3067 | |
| 3068 | 15. The spa authenticator server code was not checking that the input it |
| 3069 | received was valid base64. |
| 3070 | |
| 3071 | 16. The debug output line for the "set" modifier in ACLs was not showing the |
| 3072 | name of the variable that was being set. |
| 3073 | |
| 3074 | 17. Code tidy: the variable type "vtype_string" was never used. Removed it. |
| 3075 | |
| 3076 | 18. Previously, a reference to $sender_host_name did not cause a DNS reverse |
| 3077 | lookup on its own. Something else was needed to trigger the lookup. For |
| 3078 | example, a match in host_lookup or the need for a host name in a host list. |
| 3079 | Now, if $sender_host_name is referenced and the host name has not yet been |
| 3080 | looked up, a lookup is performed. If the lookup fails, the variable remains |
| 3081 | empty, and $host_lookup_failed is set to "1". |
| 3082 | |
| 3083 | 19. Added "eqi" as a case-independent comparison operator. |
| 3084 | |
| 3085 | 20. The saslauthd authentication condition could segfault if neither service |
| 3086 | nor realm was specified. |
| 3087 | |
| 3088 | 21. If an overflowing value such as "2048M" was set for message_size_limit, the |
| 3089 | error message that was logged was misleading, and incoming SMTP |
| 3090 | connections were dropped. The message is now more accurate, and temporary |
| 3091 | errors are given to SMTP connections. |
| 3092 | |
| 3093 | 22. In some error situations (such as 21 above) Exim rejects all SMTP commands |
| 3094 | (except RSET) with a 421 error, until QUIT is received. However, it was |
| 3095 | failing to send a response to QUIT. |
| 3096 | |
| 3097 | 23. The HELO ACL was being run before the code for helo_try_verify_hosts, |
| 3098 | which made it impossible to use "verify = helo" in the HELO ACL. The HELO |
| 3099 | ACL is now run after the helo_try_verify_hosts code. |
| 3100 | |
| 3101 | 24. "{MD5}" and "{SHA1}" are now recognized as equivalent to "{md5"} and |
| 3102 | "{sha1}" in the "crypteq" expansion condition (in fact the comparison is |
| 3103 | case-independent, so other case variants are also recognized). Apparently |
| 3104 | some systems use these upper case variants. |
| 3105 | |
| 3106 | 25. If more than two messages were waiting for the same host, and a transport |
| 3107 | filter was specified for the transport, Exim sent two messages over the |
| 3108 | same TCP/IP connection, and then failed with "socket operation on non- |
| 3109 | socket" when it tried to send the third. |
| 3110 | |
| 3111 | 26. Added Exim::debug_write and Exim::log_write for embedded Perl use. |
| 3112 | |
| 3113 | 27. The extern definition of crypt16() in expand.c was not being excluded when |
| 3114 | the OS had its own crypt16() function. |
| 3115 | |
| 3116 | 28. Added bounce_return_body as a new option, and bounce_return_size_limit |
| 3117 | as a preferred synonym for return_size_limit, both as an option and as an |
| 3118 | expansion variable. |
| 3119 | |
| 3120 | 29. Added LIBS=-liconv to OS/Makefile-OSF1. |
| 3121 | |
| 3122 | 30. Changed the default configuration ACL to relax the local part checking rule |
| 3123 | for addresses that are not in any local domains. For these addresses, |
| 3124 | slashes and pipe symbols are allowed within local parts, but the sequence |
| 3125 | /../ is explicitly forbidden. |
| 3126 | |
| 3127 | 31. SPA server authentication was not clearing the challenge buffer before |
| 3128 | using it. |
| 3129 | |
| 3130 | 32. log_message in a "warn" ACL statement was writing to the reject log as |
| 3131 | well as to the main log, which contradicts the documentation and doesn't |
| 3132 | seem right (because no rejection is happening). So I have stopped it. |
| 3133 | |
| 3134 | 33. Added Ard Biesheuvel's lookup code for accessing an Interbase database. |
| 3135 | However, I am unable to do any testing of this. |
| 3136 | |
| 3137 | 34. Fixed an infelicity in the appendfile transport. When checking directories |
| 3138 | for a mailbox, to see if any needed to be created, it was accidentally |
| 3139 | using path names with one or more superfluous leading slashes; tracing |
| 3140 | would show up entries such as stat("///home/ph10", 0xFFBEEA48). |
| 3141 | |
| 3142 | 35. If log_message is set on a "discard" verb in a MAIL or RCPT ACL, its |
| 3143 | contents are added to the log line that is written for every discarded |
| 3144 | recipient. (Previously a log_message setting was ignored.) |
| 3145 | |
| 3146 | 36. The ${quote: operator now quotes the string if it is empty. |
| 3147 | |
| 3148 | 37. The install script runs exim in order to find its version number. If for |
| 3149 | some reason other than non-existence or emptiness, which it checks, it |
| 3150 | could not run './exim', it was installing it with an empty version number, |
| 3151 | i.e. as "exim-". This error state is now caught, and the installation is |
| 3152 | aborted. |
| 3153 | |
| 3154 | 38. An argument was missing from the function that creates an error message |
| 3155 | when Exim fails to connect to the socket for saslauthd authentication. |
| 3156 | This could cause Exim to crash, or give a corrupted message. |
| 3157 | |
| 3158 | 39. Added isip, isip4, and isip6 to ${if conditions. |
| 3159 | |
| 3160 | 40. The ACL variables $acl_xx are now saved with the message, and can be |
| 3161 | accessed later in routers, transports, and filters. |
| 3162 | |
| 3163 | 41. The new lookup type nwildlsearch is like wildlsearch, except that the key |
| 3164 | strings in the file are not string-expanded. |
| 3165 | |
| 3166 | 42. If a MAIL command specified a SIZE value that was too large to fit into an |
| 3167 | int variable, the check against message_size_limit failed. Such values are |
| 3168 | now forced to INT_MAX, which is around 2Gb for a 32-bit variable. Maybe one |
| 3169 | day this will have to be increased, but I don't think I want to be around |
| 3170 | when emails are that large. |
| 3171 | |
| 3172 | |
| 3173 | |
| 3174 | Exim version 4.22 |
| 3175 | ----------------- |
| 3176 | |
| 3177 | 1. Removed HAVE_ICONV=yes from OS/Makefile-FreeBSD, since it seems that |
| 3178 | iconv() is not standard in FreeBSD. |
| 3179 | |
| 3180 | 2. Change 4.21/17 was buggy and could cause stack overwriting on a system with |
| 3181 | IPv6 enabled. The observed symptom was a segmentation fault on return from |
| 3182 | the function os_common_find_running_interfaces() in src/os.c. |
| 3183 | |
| 3184 | 3. In the check_special_case() function in daemon.c I had used "errno" as an |
| 3185 | argument name, which causes warnings on some systems. This was basically a |
| 3186 | typo, since it was named "eno" in the comments! |
| 3187 | |
| 3188 | 4. The code that waits for the clock to tick (at a resolution of some fraction |
| 3189 | of a second) so as to ensure message-id uniqueness was always waiting for |
| 3190 | at least one whole tick, when it could have waited for less. [This is |
| 3191 | almost certainly not relevant at current processor speeds, where it is |
| 3192 | unlikely to ever wait at all. But we try to future-proof.] |
| 3193 | |
| 3194 | 5. The function that sleeps for a time interval that includes fractions of a |
| 3195 | second contained a race. It did not block SIGALRM between setting the |
| 3196 | timer, and suspending (a couple of lines later). If the interval was short |
| 3197 | and the sigsuspend() was delayed until after it had expired, the suspension |
| 3198 | never ended. On busy systems this could lead to processes getting stuck for |
| 3199 | ever. |
| 3200 | |
| 3201 | 6. Some uncommon configurations may cause a lookup to happen in a queue runner |
| 3202 | process, before it forks any delivery processes. The open lookup caching |
| 3203 | mechanism meant that the open file or database connection was passed into |
| 3204 | the delivery process. The problem was that delivery processes always tidy |
| 3205 | up cached lookup data. This could cause a problem for the next delivery |
| 3206 | process started by the queue runner, because the external queue runner |
| 3207 | process does not know about the closure. So the next delivery process |
| 3208 | still has data in the lookup cache. In the case of a file lookup, there was |
| 3209 | no problem because closing a file descriptor in a subprocess doesn't affect |
| 3210 | the parent. However, if the lookup was caching a connection to a database, |
| 3211 | the connection was closed, and the second delivery process was likely to |
| 3212 | see errors such as "PGSQL: query failed: server closed the connection |
| 3213 | unexpectedly". The problem has been fixed by closing all cached lookups |
| 3214 | in a queue runner before running a delivery process. |
| 3215 | |
| 3216 | 7. Compiler warning on Linux for the second argument of iconv(), which doesn't |
| 3217 | seem to have the "const" qualifier which it has on other OS. I've |
| 3218 | parameterised it. |
| 3219 | |
| 3220 | 8. Change 4.21/2 was too strict. It is only if there are two authenticators |
| 3221 | *of the same type* (client or server) with the same public name that an |
| 3222 | error should be diagnosed. |
| 3223 | |
| 3224 | 9. When Exim looked up a host name for an IP address, but failed to find the |
| 3225 | original IP address when looking up the host name (a safety check), it |
| 3226 | output the message "<ip address> does not match any IP for NULL", which was |
| 3227 | confusing, to say the least. The bug was that the host name should have |
| 3228 | appeared instead of "NULL". |
| 3229 | |
| 3230 | 10. Since release 3.03, if Exim is called by a uid other than root or the Exim |
| 3231 | user that is built into the binary, and the -C or -D options is used, root |
| 3232 | privilege is dropped before the configuration file is read. In addition, |
| 3233 | logging is switched to stderr instead of the normal log files. If the |
| 3234 | configuration then re-defines the Exim user, the unprivileged environment |
| 3235 | is probably not what is expected, so Exim logs a panic warning message (but |
| 3236 | proceeds). |
| 3237 | |
| 3238 | However, if deliver_drop_privilege is set, the unprivileged state may well |
| 3239 | be exactly what is intended, so the warning has been cut out in that case, |
| 3240 | and Exim is allowed to try to write to its normal log files. |
| 3241 | |
| 3242 | |
| 3243 | Exim version 4.21 |
| 3244 | ----------------- |
| 3245 | |
| 3246 | 1. smtp_return_error_details was not giving details for temporary sender |
| 3247 | or receiver verification errors. |
| 3248 | |
| 3249 | 2. Diagnose a configuration error if two authenticators have the same public |
| 3250 | name. |
| 3251 | |
| 3252 | 3. Exim used not to create the message log file for a message until the first |
| 3253 | delivery attempt. This could be confusing when incoming messages were held |
| 3254 | for policy or load reasons. The message log file is now created at the time |
| 3255 | the message is received, and an initial "Received" line is written to it. |
| 3256 | |
| 3257 | 4. The automatically generated man page for command line options had a minor |
| 3258 | bug that caused no ill effects; however, a more serious problem was that |
| 3259 | the procedure for building the man page automatically didn't always |
| 3260 | operate. Consequently, release 4.20 contains an out-of-date version. This |
| 3261 | shouldn't happen again. |
| 3262 | |
| 3263 | 5. When building Exim with embedded Perl support, the script that builds the |
| 3264 | Makefile was calling 'perl' to find its compile-time parameters, ignoring |
| 3265 | any setting of PERL_COMMAND in Local/Makefile. This is now fixed. |
| 3266 | |
| 3267 | 6. The freeze_tell option was not being used for messages that were frozen on |
| 3268 | arrival, either by an ACL or by local_scan(). |
| 3269 | |
| 3270 | 7. Added the smtp_incomplete_transaction log selector. |
| 3271 | |
| 3272 | 8. After STARTTLS, Exim was not forgetting that it had advertised AUTH, so it |
| 3273 | was accepting AUTH without a new EHLO. |
| 3274 | |
| 3275 | 9. Added tls_remember_esmtp to cope with YAEB. This allows AUTH and other |
| 3276 | ESMTP extensions after STARTTLS without a new EHLO, in contravention of the |
| 3277 | RFC. |
| 3278 | |
| 3279 | 10. Logging of TCP/IP connections (when configured) now happens in the main |
| 3280 | daemon process instead of the child process, so that the TCP/IP connection |
| 3281 | count is more accurate (but it can never be perfect). |
| 3282 | |
| 3283 | 11. The use of "drop" in a nested ACL was not being handled correctly in the |
| 3284 | outer ACL. Now, if condition failure induced by the nested "drop" causes |
| 3285 | the outer ACL verb to deny access ("accept" or "discard" after "endpass", |
| 3286 | or "require"), the connection is dropped. |
| 3287 | |
| 3288 | 12. Similarly, "discard" in a nested ACL wasn't being handled. A nested ACL |
| 3289 | that yield "discard" can now be used with an "accept" or a "discard" verb, |
| 3290 | but an error is generated for any others (because I can't see a useful way |
| 3291 | to define what should happen). |
| 3292 | |
| 3293 | 13. When an ACL is read dynamically from a file (or anywhere else), the lines |
| 3294 | are now processed in the same way as lines in the Exim configuration file. |
| 3295 | In particular, continuation lines are supported. |
| 3296 | |
| 3297 | 14. Added the "dnslists = a.b.c!=n.n.n.n" feature. |
| 3298 | |
| 3299 | 15. Added -ti meaning -t -i. |
| 3300 | |
| 3301 | 16. Check for letters, digits, hyphens, and dots in the names of dnslist |
| 3302 | domains, and warn by logging if others are found. |
| 3303 | |
| 3304 | 17. At least on BSD, alignment is not guarenteed for the array of ifreq's |
| 3305 | returned from GIFCONF when Exim is trying to find the list of interfaces on |
| 3306 | a host. The code in os.c has been modified to copy each ifreq to an aligned |
| 3307 | structure in all cases. |
| 3308 | |
| 3309 | Also, in some cases, the returned ifreq's were being copied to a 'struct |
| 3310 | ifreq' on the stack, which was subsequently passed to host_ntoa(). That |
| 3311 | means the last couple of bytes of an IPv6 address could be chopped if the |
| 3312 | ifreq contained only a normal sockaddr (14 bytes storage). |
| 3313 | |
| 3314 | 18. Named domain lists were not supported in the hosts_treat_as_local option. |
| 3315 | An entry such as +xxxx was not recognized, and was treated as a literal |
| 3316 | domain name. |
| 3317 | |
| 3318 | 19. Ensure that header lines added by a DATA ACL are included in the reject log |
| 3319 | if the ACL subsequently rejects the message. |
| 3320 | |
| 3321 | 20. Upgrade the cramtest.pl utility script to use Digest::MD5 instead of just |
| 3322 | MD5 (which is deprecated). |
| 3323 | |
| 3324 | 21. When testing a filter file using -bf, Exim was writing a message when it |
| 3325 | took the sender from a "From " line in the message, but it was not doing so |
| 3326 | when it took $return_path from a Return-Path: header line. It now does. |
| 3327 | |
| 3328 | 22. If the contents of a "message" modifier for a "warn" ACL verb do not begin |
| 3329 | with a valid header line field name (a series of printing characters |
| 3330 | terminated by a colon, Exim now inserts X-ACL-Warn: at the beginning. |
| 3331 | |
| 3332 | 23. Changed "disc" in the source to "disk" to conform to the documentation and |
| 3333 | the book and for uniformity. |
| 3334 | |
| 3335 | 24. Ignore Sendmail's -Ooption=value command line item. |
| 3336 | |
| 3337 | 25. When execve() failed while trying to run a command in a pipe transport, |
| 3338 | Exim was returning EX_UNAVAILBLE (69) from the subprocess. However, this |
| 3339 | could be confused with a return value of 69 from the command itself. This |
| 3340 | has been changed to 127, the value the shell returns if it is asked to run |
| 3341 | a non-existent command. The wording for the related log line suggests a |
| 3342 | non-existent command as the problem. |
| 3343 | |
| 3344 | 26. If received_header_text expands to an empty string, do not add a Received: |
| 3345 | header line to the message. (Well, it adds a token one on the spool, but |
| 3346 | marks it "old" so that it doesn't get used or transmitted.) |
| 3347 | |
| 3348 | 27. Installed eximstats 1.28 (addition of -nt option). |
| 3349 | |
| 3350 | 28. There was no check for failure on the call to getsockname() in the daemon |
| 3351 | code. This can fail if there is a shortage of resources on the system, with |
| 3352 | ENOMEM, for example. A temporary error is now given on failure. |
| 3353 | |
| 3354 | 29. Contrary to the C standard, it seems that in some environments, the |
| 3355 | equivalent of setlocale(LC_ALL, "C") is not obeyed at the start of a C |
| 3356 | program. Exim now does this explicitly; it affects the formatting of |
| 3357 | timestamps using strftime(). |
| 3358 | |
| 3359 | 30. If exiqsumm was given junk data, it threw up some uninitialized variable |
| 3360 | complaints. I've now initialized all the variables, to avoid this. |
| 3361 | |
| 3362 | 32. Header lines added by a system filter were not being "seen" during |
| 3363 | transport-time rewrites. |
| 3364 | |
| 3365 | 33. The info_callback() function passed to OpenSSL is set up with type void |
| 3366 | (*)(SSL *, int, int), as described somewhere. However, when calling the |
| 3367 | function (actually a macro) that sets it up, the type void(*)() is |
| 3368 | expected. I've put in a cast to prevent warnings from picky compilers. |
| 3369 | |
| 3370 | 34. If a DNS black list lookup found a CNAME record, but there were no A |
| 3371 | records associated with the domain it pointed at, Exim crashed. |
| 3372 | |
| 3373 | 35. If a DNS black list lookup returned more than one A record, Exim ignored |
| 3374 | all but the first. It now scans all returned addresses if a particular IP |
| 3375 | value is being sought. In this situation, the contents of the |
| 3376 | $dnslist_value variable are a list of all the addresses, separated by a |
| 3377 | comma and a space. |
| 3378 | |
| 3379 | 36. Tightened up the rules for host name lookups using reverse DNS. Exim used |
| 3380 | to accept a host name and all its aliases if the forward lookup for any of |
| 3381 | them yielded the IP address of the incoming connection. Now it accepts only |
| 3382 | those names whose forward lookup yields the correct IP address. Any other |
| 3383 | names are discarded. This closes a loophole whereby a rogue DNS |
| 3384 | administrator could create reverse DNS records to break through a |
| 3385 | wildcarded host restriction in an ACL. |
| 3386 | |
| 3387 | 37. If a user filter or a system filter that ran in a subprocess used any of |
| 3388 | the numerical variables ($1, $2 etc), or $thisaddress, in a pipe command, |
| 3389 | the wrong values were passed to the pipe command ($thisaddress had the |
| 3390 | value of $0, $0 had the value of $1, etc). This bug was introduced by |
| 3391 | change 4.11/101, and not discovered because I wrote an inadequate test. :-( |
| 3392 | |
| 3393 | 38. Improved the line breaking for long SMTP error messages from ACLs. |
| 3394 | Previously, if there was no break point between 40 and 75 characters, Exim |
| 3395 | left the rest of the message alone. Two changes have been made: (a) I've |
| 3396 | reduced the minimum length to 35 characters; (b) if it can't find a break |
| 3397 | point between 35 and 75 characters, it looks ahead and uses the first one |
| 3398 | that it finds. This may give the occasional overlong line, but at least the |
| 3399 | remaining text gets split now. |
| 3400 | |
| 3401 | 39. Change 82 of 4.11 was unimaginative. It assumed the limit on the number of |
| 3402 | file descriptors might be low, and that setting 1000 would always raise it. |
| 3403 | It turns out that in some environments, the limit is already over 1000 and |
| 3404 | that lowering it causes trouble. So now Exim takes care not to decrease it. |
| 3405 | |
| 3406 | 40. When delivering a message, the value of $return_path is set to $sender_ |
| 3407 | address at the start of routing (routers may change the value). By an |
| 3408 | oversight, this default was not being set up when an address was tested by |
| 3409 | -bt or -bv, which affected the outcome if any router or filter referred to |
| 3410 | $return_path. |
| 3411 | |
| 3412 | 41. The idea of the "warn" ACL verb is that it adds a header or writes to the |
| 3413 | log only when "message" or "log_message" are set. However, if one of the |
| 3414 | conditions was an address verification, or a call to a nested ACL, the |
| 3415 | messages generated by the underlying test were being passed through. This |
| 3416 | no longer happens. The underlying message is available in $acl_verify_ |
| 3417 | message for both "message" and "log_message" expansions, so it can be |
| 3418 | passed through if needed. |
| 3419 | |
| 3420 | 42. Added RFC 2047 interpretation of header lines for $h_ expansions, with a |
| 3421 | new expansion $bh_ to give the encoded byte string without charset |
| 3422 | translation. Translation happens only if iconv() is available; HAVE_ICONV |
| 3423 | indicates this at build time. HEADERS_CHARSET gives the charset to |
| 3424 | translate to; headers_charset can change it in the configuration, and |
| 3425 | "headers charset" can change it in an individual filter file. |
| 3426 | |
| 3427 | 43. Now that we have a default RFC 2047 charset (see above), the code in Exim |
| 3428 | that creates RFC 2047 encoded "words" labels them as that charset instead |
| 3429 | of always using iso-8859-1. The cases are (i) the explicit ${rfc2047: |
| 3430 | expansion operator; (ii) when Exim creates a From: line for a local |
| 3431 | message; (iii) when a header line is rewritten to include a "phrase" part. |
| 3432 | |
| 3433 | 44. Nasty bug in exiqsumm: the regex to skip already-delivered addresses was |
| 3434 | buggy, causing it to skip the first lines of messages whose message ID |
| 3435 | ended in 'D'. This would not have bitten before Exim release 4.14, because |
| 3436 | message IDs were unlikely to end in 'D' before then. The effect was to have |
| 3437 | incorrect size information for certain domains. |
| 3438 | |
| 3439 | 45. #include "config.h" was missing at the start of the crypt16.c module. This |
| 3440 | caused trouble on Tru64 (aka OSF1) systems, because HAVE_CRYPT16 was not |
| 3441 | noticed. |
| 3442 | |
| 3443 | 46. If there was a timeout during a "random" callout check, Exim treated it as |
| 3444 | a failure of the random address, and carried on sending RSET and the real |
| 3445 | address. If the delay was just some slowness somewhere, the response to the |
| 3446 | original RCPT would be taken as a response to RSET and so on, causing |
| 3447 | mayhem of various kinds. |
| 3448 | |
| 3449 | 47. Change 50 for 4.20 was a heap of junk. I don't know what I was thinking |
| 3450 | when I implemented it. It didn't allow for the fact that some option values |
| 3451 | may legitimatetly be negative (e.g. size_addition), and it didn't even do |
| 3452 | the right test for positive values. |
| 3453 | |
| 3454 | 48. Domain names in DNS records are case-independent. Exim always looks them up |
| 3455 | in lower case. Some resolvers return domain names in exactly the case they |
| 3456 | appear in the zone file, that is, they may contain uppercase letters. Not |
| 3457 | all resolvers do this - some return always lower case. Exim was treating a |
| 3458 | change of case by a resolver as a change of domain, similar to a widening |
| 3459 | of a domain abbreviation. This triggered its re-routing code and so it was |
| 3460 | trying to route what was effectively the same domain again. This normally |
| 3461 | caused routing to fail (because the router wouldn't handle the domain |
| 3462 | twice). Now Exim checks for this case specially, and just changes the |
| 3463 | casing of the domain that it ultimately uses when it transmits the message |
| 3464 | envelope. |
| 3465 | |
| 3466 | 49. Added Sieve (RFC 3028) support, courtesy of Michael Haardt's contributed |
| 3467 | module. |
| 3468 | |
| 3469 | 50. If a filter generated a file delivery with a non-absolute name (possible if |
| 3470 | no home directory exists for the router), the forbid_file option was not |
| 3471 | forbidding it. |
| 3472 | |
| 3473 | 51. Added '&' feature to dnslists, to provide bit mask matching in addition to |
| 3474 | the existing equality matching. |
| 3475 | |
| 3476 | 52. Exim was using ints instead of ino_t variables in some places where it was |
| 3477 | dealing with inode numbers. |
| 3478 | |
| 3479 | 53. If TMPDIR is defined in Local/Makefile (default in src/EDITME is |
| 3480 | TMPDIR="/tmp"), Exim checks for the presence of an environment variable |
| 3481 | called TMPDIR, and if it finds it is different, it changes its value. |
| 3482 | |
| 3483 | 54. The smtp_printf() function is now made available to local_scan() so |
| 3484 | additional output lines can be written before returning. There is also an |
| 3485 | smtp_fflush() function to enable the detection of a dropped connection. |
| 3486 | The variables smtp_input and smtp_batched_input are exported to |
| 3487 | local_scan(). |
| 3488 | |
| 3489 | 55. Changed the default runtime configuration: the message "Unknown user" |
| 3490 | has been removed from the ACL, and instead placed on the localuser router, |
| 3491 | using the cannot_route_message feature. This means that any verification |
| 3492 | failures that generate their own messages won't get overridden. Similarly, |
| 3493 | the "Unrouteable address" message that was in the ACL for unverifiable |
| 3494 | relay addresses has also been removed. |
| 3495 | |
| 3496 | 56. Added hosts_avoid_esmtp to the smtp transport. |
| 3497 | |
| 3498 | 57. The exicyclog script was not checking for the esoteric option |
| 3499 | CONFIGURE_FILE_USE_EUID in the Local/Makefile. It now does this, but it |
| 3500 | will work only if exicyclog is run under the appropriate euid. |
| 3501 | |
| 3502 | 58. Following a discussion on the list, the rules by which Exim recognises line |
| 3503 | endings on incoming messages have been changed. The -dropcr and drop_cr |
| 3504 | options are now no-ops, retained only for backwards compatibility. The |
| 3505 | following line terminators are recognized: LF CRLF CR. However, special |
| 3506 | processing applies to CR: |
| 3507 | |
| 3508 | (i) The sequence CR . CR does *not* terminate an incoming SMTP message, |
| 3509 | nor a local message in the state where . is a terminator. |
| 3510 | |
| 3511 | (ii) If a bare CR is encountered in a header line, an extra space is added |
| 3512 | after the line terminator so as not to end the header. The reasoning |
| 3513 | behind this is that bare CRs in header lines are most likely either |
| 3514 | to be mistakes, or people trying to play silly games. |
| 3515 | |
| 3516 | 59. The size of a message, as listed by "-bp" or in the Exim monitor window, |
| 3517 | was being incorrectly given as 18 bytes larger than it should have been. |
| 3518 | This is a VOB (very old bug). |
| 3519 | |
| 3520 | 60. This may never have affected anything current, but just in case it has: |
| 3521 | When the local host is found other than at the start of a list of hosts, |
| 3522 | the local host, those with the same MX, and any that follow, are discarded. |
| 3523 | When the list in question was part of a longer list of hosts, the following |
| 3524 | hosts (not currently being processed) were also being discarded. This no |
| 3525 | longer happens. I'm not sure if this situation could ever has previously |
| 3526 | arisen. |
| 3527 | |
| 3528 | 61. Added the "/MX" feature to lists of hosts in the manualroute and query |
| 3529 | program routers. |
| 3530 | |
| 3531 | 62. Whenever Exim generates a new message, it now adds an Auto-Submitted: |
| 3532 | header. This is something that is recommended in a new Internet Draft, and |
| 3533 | is something that is documented as being done by Sendmail. There are two |
| 3534 | possible values. For messages generated by the autoreply transport, Exim |
| 3535 | adds: |
| 3536 | |
| 3537 | Auto-Submitted: auto-replied |
| 3538 | |
| 3539 | whereas for all other generated messages (e.g. bounces) it adds |
| 3540 | |
| 3541 | Auto-Submitted: auto-generated |
| 3542 | |
| 3543 | 63. The "personal" condition in filters now includes a test for the |
| 3544 | Auto-Submitted: header. If it contains the string "auto-" the message it |
| 3545 | not considered personal. |
| 3546 | |
| 3547 | 64. Added rcpt_include_affixes as a generic transport option. |
| 3548 | |
| 3549 | 65. Added queue_only_override (default true). |
| 3550 | |
| 3551 | 66. Added the syslog_duplication option. |
| 3552 | |
| 3553 | 67. If what should have been the first header line of a message consisted of |
| 3554 | a space followed by a colon, Exim was mis-interpreting it as a header line. |
| 3555 | It isn't of course - it is syntactically invalid and should therefore be |
| 3556 | treated as the start of the message body. The misbehaviour could have |
| 3557 | caused a number of strange effects, including loss of data in subsequent |
| 3558 | header lines, and spool format errors. |
| 3559 | |
| 3560 | 68. Formerly, the AUTH parameter on a MAIL command was trusted only if the |
| 3561 | client host had authenticated. This control can now be exercised by an ACL |
| 3562 | for more flexibility. |
| 3563 | |
| 3564 | 69. By default, callouts do not happen when testing with -bh. There is now a |
| 3565 | variant, -bhc, which does actually run the callout code, including |
| 3566 | consulting and updating the callout cache. |
| 3567 | |
| 3568 | 70. Added support for saslauthd authentication, courtesy of Alexander |
| 3569 | Sabourenkov. |
| 3570 | |
| 3571 | 71. If statvfs() failed on the spool or log directories while checking their |
| 3572 | size for availability, Exim confusingly gave the error "space shortage". |
| 3573 | Furthermore, in debugging mode it crashed with a floating point exception. |
| 3574 | These checks are done if check_{spool,log}_{space,inodes} are set, and when |
| 3575 | an SMTP message arrives with SIZE= on the MAIL command. As this is a really |
| 3576 | serious problem, Exim now writes to the main and panic logs when this |
| 3577 | happens, with details of the failure. It then refuses to accept the |
| 3578 | incoming message, giving the message "spool directory problem" or "log |
| 3579 | directory problem" with a 421 code for SMTP messages. |
| 3580 | |
| 3581 | 72. When Exim is about to re-exec itself, it ensures that the file descriptors |
| 3582 | 0, 1, and 2 exist, because some OS complain for execs without them (see |
| 3583 | ChangeLog 4.05/30). If necessary, Exim opens /dev/null to use for these |
| 3584 | descriptors. However, the code omitted to check that the open succeeded, |
| 3585 | causing mysterious errors if for some reason the permissions on /dev/null |
| 3586 | got screwed. Now Exim writes a message to the main and panic logs, and |
| 3587 | bombs out if it can't open /dev/null. |
| 3588 | |
| 3589 | 73. Re-vamped the way daemon_smtp_port, local_interfaces, and -oX work and |
| 3590 | interact so that it is all more flexible. It is supposed to remain |
| 3591 | backwards compatible. Also added extra_local_interfaces. |
| 3592 | |
| 3593 | 74. Invalid data sent to a SPA (NTLM) server authenticator could cause the code |
| 3594 | to bomb out with an assertion failure - to the client this appears as a |
| 3595 | connection drop. This problem occurs in the part of the code that was taken |
| 3596 | from the Samba project. Fortunately, the assertion is in a very simple |
| 3597 | function, so I have fixed this by reproducing the function inline in the |
| 3598 | one place where it is called, and arranging for authentication to fail |
| 3599 | instead of killing the process with assert(). |
| 3600 | |
| 3601 | 75. The SPA client code was not working when the server requested OEM rather |
| 3602 | than Unicode encoding. |
| 3603 | |
| 3604 | 76. Added code to make require_files with a specific uid setting more usable in |
| 3605 | the case where statting the file as root fails - usually a non-root-mounted |
| 3606 | NFS file system. When this happens and the failure is EACCES, Exim now |
| 3607 | forks a subprocess and does the per-uid checking as the relevant uid. |
| 3608 | |
| 3609 | 77. Added process_log_path. |
| 3610 | |
| 3611 | 78. If log_file_path was not explicitly set, a setting of check_log_space or |
| 3612 | check_log_inodes was ignored. |
| 3613 | |
| 3614 | 79. If a space check for the spool or log partitions fails, the incident is now |
| 3615 | logged. Of course, in the latter case the data may get lost... |
| 3616 | |
| 3617 | 80. Added the %p formatting code to string_format() so that it can be used to |
| 3618 | print addresses in debug_print(). Adjusted all the address printing in the |
| 3619 | debugging in store.c to use %p rather than %d. |
| 3620 | |
| 3621 | 81. There was a concern that a line of code in smtp_in.c could overflow a |
| 3622 | buffer if a HELO/EHLO command was given followed by 500 or so spaces. As |
| 3623 | initially expressed, the concern was not well-founded, because trailing |
| 3624 | spaces are removed early. However, if the trailing spaces were followed by |
| 3625 | a NULL, they did not get removed, so the overflow was possible. Two fixes |
| 3626 | were applied: |
| 3627 | |
| 3628 | (a) I re-wrote the offending code in a cleaner fashion. |
| 3629 | (b) If an incoming SMTP command contains a NULL character, it is rejected |
| 3630 | as invalid. |
| 3631 | |
| 3632 | 82. When Exim changes uid/gid to the Exim user at daemon start time, it now |
| 3633 | runs initgroups(), so that if the Exim user is in any additional groups, |
| 3634 | they will be used during message reception. |
| 3635 | |
| 3636 | |
| 3637 | Exim version 4.20 |
| 3638 | ----------------- |
| 3639 | |
| 3640 | The change log for 4.20 and earlier releases has been archived. |
| 3641 | |
| 3642 | **** |