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