Added -dd for daemon debugging.
[exim.git] / doc / doc-txt / NewStuff
CommitLineData
3d235903 1$Cambridge: exim/doc/doc-txt/NewStuff,v 1.8 2004/11/10 10:29:56 ph10 Exp $
495ae4b0
PH
2
3New Features in Exim
4--------------------
5
6This file contains descriptions of new features that have been added to Exim,
7but have not yet made it into the main manual (which is most conveniently
8updated when there is a relatively large batch of changes). The doc/ChangeLog
9file contains a listing of all changes, including bug fixes.
10
11
35edf2ff
PH
12Version 4.44
13------------
14
15 1. There is a new build-time option called CONFIGURE_GROUP which works like
16 CONFIGURE_OWNER. It specifies one additional group that is permitted for
17 the runtime configuration file when the group write permission is set.
18
69358f02
PH
19 2. The "control=submission" facility has a new option /retain_sender. This
20 has the effect of setting local_sender_retain true and local_from_check
21 false for the incoming message in which it is encountered.
22
5131419f
PH
23 3. $recipients is now available in the predata ACL (oversight).
24
25 4. The value of address_data from a sender verification is now available in
26 $sender_address_data in subsequent conditions in the ACL statement. Note:
27 this is just like $address_data. The value does not persist after the end
28 of the current ACL statement. If you want to preserve it, you can use one
29 of the ACL variables.
30
23c7ff99
PH
31 5. The redirect router has two new options: forbid_sieve_filter and
32 forbid_exim_filter. When filtering is enabled by allow_filter, these
33 options control which type(s) of filtering are permitted. By default, both
34 Exim and Sieve filters are allowed.
35
4deaf07d
PH
36 6. A new option for callouts makes it possible to set a different (usually
37 smaller) timeout for making the SMTP connection. The keyword is "connect".
38 For example:
39
40 verify = sender/callout=5s,connect=1s
41
42 If not specified, it defaults to the general timeout value.
43
2c7db3f5
PH
44 7. The new variables $sender_verify_failure and $recipient_verify_failure
45 contain information about exactly what failed. In an ACL, after one of
46 these failures, the relevant variable contains one of the following words:
47
48 qualify the address was unqualified (no domain), and the message
49 was neither local nor came from an exempted host;
50
51 route routing failed;
52
53 mail routing succeeded, and a callout was attempted; rejection
54 occurred at or before the MAIL command (that is, on initial
55 connection, HELO, or MAIL);
56
57 recipient the RCPT command in a callout was rejected;
58
59 postmaster the postmaster check in a callout was rejected.
60
61 The main use of these variables is expected to be to distinguish between
62 rejections of MAIL and rejections of RCPT.
63
3d235903
PH
64 8. The command line option -dd behaves exactly like -d except when used on a
65 command that starts a daemon process. In that case, debugging is turned off
66 for the subprocesses that the daemon creates. Thus, it is useful for
67 monitoring the behaviour of the daemon without creating as much output as
68 full debugging.
69
2c7db3f5 70
35edf2ff 71
495ae4b0
PH
72Version 4.43
73------------
74
75 1. There is a new Boolean global option called mua_wrapper, defaulting false.
76 This causes Exim to run an a restricted mode, in order to provide a very
77 specific service.
78
79 Background: On a personal computer, it is a common requirement for all
80 email to be sent to a smarthost. There are plenty of MUAs that can be
81 configured to operate that way, for all the popular operating systems.
82 However, there are MUAs for Unix-like systems that cannot be so configured:
83 they submit messages using the command line interface of
84 /usr/sbin/sendmail. In addition, utility programs such as cron submit
85 messages this way.
86
87 Requirement: The requirement is for something that can provide the
88 /usr/sbin/sendmail interface and deliver messages to a smarthost, but not
89 provide any queueing or retrying facilities. Furthermore, the delivery to
90 the smarthost should be synchronous, so that if it fails, the sending MUA
91 is immediately informed. In other words, we want something that in effect
92 converts a command-line MUA into a TCP/SMTP MUA.
93
94 Solutions: There are a number of applications (for example, ssmtp) that do
95 this job. However, people have found them to be lacking in various ways.
96 For instance, some sites want to allow aliasing and forwarding before
97 sending to the smarthost.
98
99 Using Exim: Exim already had the necessary infrastructure for doing this
100 job. Just a few tweaks were needed to make it behave as required, though it
101 is somewhat of an overkill to use a fully-featured MTA for this purpose.
102
103 Setting mua_wrapper=true causes Exim to run in a special mode where it
104 assumes that it is being used to "wrap" a command-line MUA in the manner
105 just described.
106
107 If you set mua_wrapper=true, you also need to provide a compatible router
108 and transport configuration. Typically there will be just one router and
109 one transport, sending everything to a smarthost.
110
111 When run in MUA wrapping mode, the behaviour of Exim changes in the
112 following ways:
113
114 (a) A daemon cannot be run, nor will Exim accept incoming messages from
115 inetd. In other words, the only way to submit messages is via the
116 command line.
117
118 (b) Each message is synchonously delivered as soon as it is received (-odi
119 is assumed). All queueing options (queue_only, queue_smtp_domains,
120 control=queue, control=freeze in an ACL etc.) are quietly ignored. The
121 Exim reception process does not finish until the delivery attempt is
122 complete. If the delivery was successful, a zero return code is given.
123
124 (c) Address redirection is permitted, but the final routing for all
125 addresses must be to the same remote transport, and to the same list of
126 hosts. Furthermore, the return_address must be the same for all
127 recipients, as must any added or deleted header lines. In other words,
128 it must be possible to deliver the message in a single SMTP
129 transaction, however many recipients there are.
130
131 (d) If the conditions in (c) are not met, or if routing any address results
132 in a failure or defer status, or if Exim is unable to deliver all the
133 recipients successfully to one of the hosts immediately, delivery of
134 the entire message fails.
135
136 (e) Because no queueing is allowed, all failures are treated as permanent;
137 there is no distinction between 4xx and 5xx SMTP response codes from
138 the smarthost. Furthermore, because only a single yes/no response can
139 be given to the caller, it is not possible to deliver to some
140 recipients and not others. If there is an error (temporary or
141 permanent) for any recipient, all are failed.
142
143 (f) If more than one host is listed, Exim will try another host after a
144 connection failure or a timeout, in the normal way. However, if this
145 kind of failure happens for all the hosts, the delivery fails.
146
147 (g) When delivery fails, an error message is written to the standard error
148 stream (as well as to Exim's log), and Exim exits to the caller with a
149 return code value 1. The message is expunged from Exim's spool files.
150 No bounce messages are ever generated.
151
152 (h) No retry data is maintained, and any retry rules are ignored.
153
154 (i) A number of Exim options are overridden: deliver_drop_privilege is
155 forced true, max_rcpt in the smtp transport is forced to "unlimited",
156 remote_max_parallel is forced to one, and fallback hosts are ignored.
157
158 The overall effect is that Exim makes a single synchronous attempt to
159 deliver the message, failing if there is any kind of problem. Because no
160 local deliveries are done and no daemon can be run, Exim does not need root
161 privilege. It should be possible to run it setuid=exim instead of
162 setuid=root. See section 48.3 in the 4.40 manual for a general discussion
163 about the advantages and disadvantages of running without root privilege.
164
165 2. There have been problems with DNS servers when SRV records are looked up.
166 Some mis-behaving servers return a DNS error or timeout when a non-existent
167 SRV record is sought. Similar problems have in the past been reported for
168 MX records. The global dns_again_means_nonexist option can help with this
169 problem, but it is heavy-handed because it is a global option. There are
170 now two new options for the dnslookup router. They are called
171 srv_fail_domains and mx_fail_domains. In each case, the value is a domain
172 list. If an attempt to look up an SRV or MX record results in a DNS failure
173 or "try again" response, and the domain matches the relevant list, Exim
174 behaves as if the DNS had responded "no such record". In the case of an SRV
175 lookup, this means that the router proceeds to look for MX records; in the
176 case of an MX lookup, it proceeds to look for A or AAAA records, unless the
177 domain matches mx_domains.
178
179 3. The following functions are now available in the local_scan() API:
180
181 (a) void header_remove(int occurrence, uschar *name)
182
183 This function removes header lines. If "occurrence" is zero or negative,
184 all occurrences of the header are removed. If occurrence is greater
185 than zero, that particular instance of the header is removed. If no
186 header(s) can be found that match the specification, the function does
187 nothing.
188
189 (b) BOOL header_testname(header_line *hdr, uschar *name, int length,
190 BOOL notdel)
191
192 This function tests whether the given header has the given name. It
193 is not just a string comparison, because whitespace is permitted
194 between the name and the colon. If the "notdel" argument is TRUE, a
195 FALSE return is forced for all "deleted" headers; otherwise they are
196 not treated specially. For example:
197
198 if (header_testname(h, US"X-Spam", 6, TRUE)) ...
199
200 (c) void header_add_at_position(BOOL after, uschar *name, BOOL topnot,
201 int type, char *format, ...)
202
203 This function adds a new header line at a specified point in the header
204 chain. If "name" is NULL, the new header is added at the end of the
205 chain if "after" is TRUE, or at the start if "after" is FALSE. If
206 "name" is not NULL, the headers are searched for the first non-deleted
207 header that matches the name. If one is found, the new header is added
208 before it if "after" is FALSE. If "after" is true, the new header is
209 added after the found header and any adjacent subsequent ones with the
210 same name (even if marked "deleted"). If no matching non-deleted header
211 is found, the "topnot" option controls where the header is added. If it
212 is TRUE, addition is at the top; otherwise at the bottom. Thus, to add
213 a header after all the Received: headers, or at the top if there are no
214 Received: headers, you could use
215
216 header_add_at_position(TRUE, US"Received", TRUE, ' ', "X-xxx: ...");
217
218 Normally, there is always at least one non-deleted Received: header,
219 but there may not be if received_header_text expands to an empty
220 string.
221
222 (d) BOOL receive_remove_recipient(uschar *recipient)
223
224 This is a convenience function to remove a named recipient from the
225 list of recipients. It returns TRUE if a recipient was removed, and
226 FALSE if no matching recipient could be found. The argument must be a
227 complete email address.
228
229 4. When an ACL "warn" statement adds one or more header lines to a message,
230 they are added at the end of the existing header lines by default. It is
231 now possible to specify that any particular header line should be added
232 right at the start (before all the Received: lines) or immediately after
233 the first block of Received: lines in the message. This is done by
234 specifying :at_start: or :after_received: (or, for completeness, :at_end:)
235 before the text of the header line. (Header text cannot start with a colon,
236 as there has to be a header name first.) For example:
237
238 warn message = :after_received:X-My-Header: something or other...
239
240 If more than one header is supplied in a single warn statement, each one is
241 treated independently and can therefore be placed differently. If you add
242 more than one line at the start, or after the Received: block, they will
243 end up in reverse order.
244
245 Warning: This facility currently applies only to header lines that are
246 added in an ACL. It does NOT work for header lines that are added in a
247 system filter or in a router or transport.
248
249 5. There is now a new error code that can be used in retry rules. Its name is
250 "rcpt_4xx", and there are three forms. A literal "rcpt_4xx" matches any 4xx
251 error received for an outgoing SMTP RCPT command; alternatively, either the
252 first or both of the x's can be given as digits, for example: "rcpt_45x" or
253 "rcpt_436". If you want (say) to recognize 452 errors given to RCPT
254 commands by a particular host, and have only a one-hour retry for them, you
255 can set up a retry rule of this form:
256
257 the.host.name rcpt_452 F,1h,10m
258
259 Naturally, this rule must come before any others that would match.
260
261 These new errors apply to both outgoing SMTP (the smtp transport) and
262 outgoing LMTP (either the lmtp transport, or the smtp transport in LMTP
263 mode). Note, however, that they apply only to responses to RCPT commands.
264
265 6. The "postmaster" option of the callout feature of address verification has
266 been extended to make it possible to use a non-empty MAIL FROM address when
267 checking a postmaster address. The new suboption is called "postmaster_
268 mailfrom", and you use it like this:
269
270 require verify = sender/callout=postmaster_mailfrom=abc@x.y.z
271
272 Providing this suboption causes the postmaster check to be done using the
273 given address. The original "postmaster" option is equivalent to
274
275 require verify = sender/callout=postmaster_mailfrom=
276
277 If both suboptions are present, the rightmost one overrides.
278
279 Important notes:
280
281 (1) If you use a non-empty sender address for postmaster checking, there is
282 the likelihood that the remote host will itself initiate a callout
283 check back to your host to check that address. As this is a "normal"
284 callout check, the sender will most probably be empty, thus avoiding
285 possible callout loops. However, to be on the safe side it would be
286 best to set up your own ACLs so that they do not do sender verification
287 checks when the recipient is the address you use for postmaster callout
288 checking.
289
290 (2) The caching arrangements for postmaster checking do NOT take account of
291 the sender address. It is assumed that either the empty address, or a
292 fixed non-empty address will be used. All that Exim remembers is that
293 the postmaster check for the domain succeeded or failed.
294
295 7. When verifying addresses in header lines using the verify=header_sender
296 option, Exim behaves by default as if the addresses are envelope sender
297 addresses from a message. Callout verification therefore tests to see
298 whether a bounce message could be delivered, by using an empty address in
299 the MAIL FROM command. However, it is arguable that these addresses might
300 never be used as envelope senders, and could therefore justifiably reject
301 bounce messages (empty senders). There is now an additional callout option
302 for verify=header_sender that allows you to specify what address to use in
303 the MAIL FROM command. You use it as in this example:
304
305 require verify = header_sender/callout=mailfrom=abcd@x.y.z
306
307 Important notes:
308
309 (1) As in the case of postmaster_mailfrom (see above), you should think
310 about possible loops.
311
312 (2) In this case, as in the case of recipient callouts with non-empty
313 senders (the use_sender option), caching is done on the basis of a
314 recipient/sender pair.
315
316 8. If you build Exim with USE_READLINE=yes in Local/Makefile, it will try to
317 load libreadline dynamically whenever the -be (test expansion) option is
318 used without command line arguments. If successful, it will then use
319 readline() for reading the test data. A line history is supported. By the
320 time Exim does this, it is running as the calling user, so this should not
321 cause any security problems. Security is the reason why this is NOT
322 supported for -bt or -bv, when Exim is running as root or exim,
323 respectively. Note that this option adds to the size of the Exim binary,
324 because the dynamic loading library is not otherwise included. On my
325 desktop it adds about 2.5K. You may need to add -ldl to EXTRA_LIBS when you
326 set USE_READLINE=yes.
327
328 9. Added ${str2b64:<string>} to the expansion operators. This operator
329 converts an arbitrary string into one that is base64 encoded.
330
33110. A new authenticator, called cyrus_sasl, has been added. This requires
332 the presence of the Cyrus SASL library; it authenticates by calling this
333 library, which supports a number of authentication mechanisms, including
334 PLAIN and LOGIN, but also several others that Exim does not support
335 directly. The code for this authenticator was provided by Matthew
336 Byng-Maddick of A L Digital Ltd (http://www.aldigital.co.uk). Here follows
337 draft documentation:
338
339 xx. THE CYRUS_SASL AUTHENTICATOR
340
341 The cyrus_sasl authenticator provides server support for the Cyrus library
342 Implementation of the RFC 2222 "Simple Authentication and Security Layer".
343 It provides a gatewaying mechanism directly to the Cyrus interface, so if
344 your Cyrus library can do, for example, CRAM-MD5, then so can the
345 cyrus_sasl authenticator. By default it uses the public name of the driver
346 to determine which mechanism to support.
347
348 Where access to some kind of secret file is required, for example in GSSAPI
349 or CRAM-MD5, it is worth noting that the authenticator runs as the exim
350 user, and that the Cyrus SASL library has no way of escalating privileges
351 by default. You may also find you need to set environment variables,
352 depending on the driver you are using.
353
354 xx.1 Using cyrus_sasl as a server
355
356 The cyrus_sasl authenticator has four private options. It puts the username
357 (on a successful authentication) into $1.
358
359 server_hostname Type: string* Default: $primary_hostname
360
361 This option selects the hostname that is used when communicating with
362 the library. It is up to the underlying SASL plug-in what it does with
363 this data.
364
365 server_mech Type: string Default: public_name
366
367 This option selects the authentication mechanism this driver should
368 use. It allows you to use a different underlying mechanism from the
369 advertised name. For example:
370
371 sasl:
372 driver = cyrus_sasl
373 public_name = X-ANYTHING
374 server_mech = CRAM-MD5
375 server_set_id = $1
376
377 server_realm Type: string Default: unset
378
379 This is the SASL realm that the server is claiming to be in.
380
381 server_service Type: string Default: "smtp"
382
383 This is the SASL service that the server claims to implement.
384
385 For straigthforward cases, you do not need to set any of the
386 authenticator's private options. All you need to do is to specify an
387 appropriate mechanism as the public name. Thus, if you have a SASL library
388 that supports CRAM-MD5 and PLAIN, you might have two authenticators as
389 follows:
390
391 sasl_cram_md5:
392 driver = cyrus_sasl
393 public_name = CRAM-MD5
394 server_set_id = $1
395
396 sasl_plain:
397 driver = cyrus_sasl
398 public_name = PLAIN
399 server_set_id = $1
400
40111. There is a new global option called tls_on_connect_ports. Its value must be
402 a list of port numbers; the most common use is expected to be
403
404 tls_on_connect_ports = 465
405
406 Setting this option has the same effect as -tls-on-connect on the command
407 line, but only for the specified ports. It applies to all connections, both
408 via the daemon and via inetd. You still need to specify all the ports for
409 the daemon (using daemon_smtp_ports or local_interfaces or the -X command
410 line option) because this option does not add an extra port -- rather, it
411 specifies different behaviour on a port that is defined elsewhere. The
412 -tls-on-connect command line option overrides tls_on_connect_ports, and
413 forces tls-on-connect for all ports.
414
41512. There is a new ACL that is run when a DATA command is received, before the
416 data itself is received. The ACL is defined by acl_smtp_predata. (Compare
417 acl_smtp_data, which is run after the data has been received.)
418 This new ACL allows a negative response to be given to the DATA command
419 itself. Header lines added by MAIL or RCPT ACLs are not visible at this
420 time, but any that are defined here are visible when the acl_smtp_data ACL
421 is run.
422
42313. The "control=submission" ACL modifier has an option "/domain=xxx" which
424 specifies the domain to be used when creating From: or Sender: lines using
425 the authenticated id as a local part. If the option is supplied with an
426 empty domain, that is, just "/domain=", Exim assumes that the authenticated
427 id is a complete email address, and it uses it as is when creating From:
428 or Sender: lines.
429
43014. It is now possible to make retry rules that apply only when the failing
431 message has a specific sender. In particular, this can be used to define
432 retry rules that apply only to bounce messages. The syntax is to add a new
433 third item to a retry rule, of the form "senders=<address list>". The retry
434 timings themselves then become the fourth item. For example:
435
436 * * senders=: F,1h,30m
437
438 would match all bounce messages. If the address list contains white space,
439 it must be enclosed in quotes. For example:
440
441 a.domain timeout senders="x@b.dom : y@c.dom" G,8h,10m,1.5
442
443 When testing retry rules using -brt, you can supply a sender using the -f
444 command line option, like this:
445
446 exim -f "" -brt user@dom.ain
447
448 If you do not set -f with -brt, a retry rule that contains a senders list
449 will never be matched.
450
45115. Two new control modifiers have been added to ACLs: "control = enforce_sync"
452 and "control = no_enforce_sync". This makes it possible to be selective
453 about when SMTP synchronization is enforced. The global option
454 smtp_enforce_sync now specifies the default state of the switch. These
455 controls can appear in any ACL, but the most obvious place to put them is
456 in the ACL defined by acl_smtp_connect, which is run at the start of an
457 incoming SMTP connection, before the first synchronization check.
458
45916. Another two new control modifiers are "control = caseful_local_part" and
460 "control = caselower_local_part". These are permitted only in the ACL
461 specified by acl_smtp_rcpt (i.e. during RCPT processing). By default, the
462 contents of $local_part are lower cased before ACL processing.
463 After "control = caseful_local_part", any uppercase letters in the original
464 local part are restored in $local_part for the rest of the ACL, or until
465 "control = caselower_local_part" is encountered. However, this applies only
466 to local part handling that takes place directly in the ACL (for example,
467 as a key in lookups). If a "verify = recipient" test is obeyed, the
468 case-related handling of the local part during the verification is
469 controlled by the router configuration (see the caseful_local_part generic
470 router option).
471
472 This facility could be used, for example, to add a spam score to local
473 parts containing upper case letters. For example, using $acl_m4 to
474 accumulate the spam score:
475
476 warn control = caseful_local_part
477 set acl_m4 = ${eval:\
478 $acl_m4 + \
479 ${if match{$local_part}{[A-Z]}{1}{0}}\
480 }
481 control = caselower_local_part
482
483 Notice that we put back the lower cased version afterwards, assuming that
484 is what is wanted for subsequent tests.
485
48617. The option hosts_connection_nolog is provided so that certain hosts can be
487 excepted from logging when the +smtp_connection log selector is set. For
488 example, you might want not to log SMTP connections from local processes,
489 or from 127.0.0.1, or from your local LAN. The option is a host list with
490 an unset default. Because it is consulted in the main loop of the daemon,
491 you should strive to restrict its value to a short inline list of IP
492 addresses and networks. To disable logging SMTP connections from local
493 processes, you must create a host list with an empty item. For example:
494
495 hosts_connection_nolog = :
496
497 If the +smtp_connection log selector is not set, this option has no effect.
498
49918. There is now an acl called acl_smtp_quit, which is run for the QUIT
500 command. The outcome of the ACL does not affect the response code to QUIT,
501 which is always 221. Thus, the ACL does not in fact control any access.
502 For this reason, the only verbs that are permitted are "accept" and "warn".
503
504 The ACL can be used for tasks such as custom logging at the end of an SMTP
505 session. For example, you can use ACL variables in other ACLs to count
506 messages, recipients, etc., and log the totals at QUIT time using one or
507 more "logwrite" modifiers on a "warn" command.
508
509 You do not need to have a final "accept", but if you do, you can use a
510 "message" modifier to specify custom text that is sent as part of the 221
511 response.
512
513 This ACL is run only for a "normal" QUIT. For certain kinds of disastrous
514 failure (for example, failure to open a log file, or when Exim is bombing
515 out because it has detected an unrecoverable error), all SMTP commands
516 from the client are given temporary error responses until QUIT is received
517 or the connection is closed. In these special cases, the ACL is not run.
518
51919. The appendfile transport has two new options, mailbox_size and mailbox_
520 filecount. If either these options are set, it is expanded, and the result
521 is taken as the current size of the mailbox or the number of files in the
522 mailbox, respectively. This makes it possible to use some external means of
523 maintaining the data about the size of a mailbox for enforcing quota
524 limits. The result of expanding these option values must be a decimal
525 number, optionally followed by "K" or "M".
526
52720. It seems that there are broken clients in use that cannot handle multiline
528 SMTP responses. Can't people who implement these braindead programs read?
529 RFC 821 mentions multiline responses, and it is over 20 years old. They
530 must handle multiline responses for EHLO, or do they still use HELO?
531 Anyway, here is YAWFAB (yet another workaround for asinine brokenness).
532 There's a new ACL switch that can be set by
533
534 control = no_multiline_responses
535
536 If this is set, it suppresses multiline SMTP responses from ACL rejections.
537 One way of doing this would have been just to put out these responses as
538 one long line. However, RFC 2821 specifies a maximum of 512 bytes per
539 response ("use multiline responses for more" it says), and some of the
540 responses might get close to that. So I have implemented this by doing two
541 very easy things:
542
543 (1) Extra information that is normally output as part of a rejection
544 caused by sender verification failure is omitted. Only the final line
545 (typically "sender verification failed") is now sent.
546
547 (2) If a "message" modifier supplies a multiline response, only the first
548 line is output.
549
550 The setting of the switch can, of course, be made conditional on the
551 calling host.
552
55321. There is now support for the libradius library that comes with FreeBSD.
554 This is an alternative to the radiusclient library that Exim already
555 supports. To use the FreeBSD library, you need to set
556
557 RADIUS_LIB_TYPE=RADLIB
558
559 in Local/Makefile, in addition to RADIUS_CONFIGURE_FILE, and you probably
560 also need -libradius in EXTRALIBS.
561
562
563Version 4.42
564------------
565
566 1. The "personal" filter test is brought up-to-date with recommendations from
567 the Sieve specification: (a) The list of non-personal From: addresses now
568 includes "listserv", "majordomo", and "*-request"; (b) If the message
569 contains any header line starting with "List=-" it is treated as
570 non-personal.
571
572 2. The Sieve functionality has been extended to support the "copy" and
573 "vacation" extensions, and comparison tests.
574
575 3. There is now an overall timeout for performing a callout verification. It
576 defaults to 4 times the callout timeout, which applies to individual SMTP
577 commands during the callout. The overall timeout applies when there is more
578 than one host that can be tried. The timeout is checked before trying the
579 next host. This prevents very long delays if there are a large number of
580 hosts and all are timing out (e.g. when the network connections are timing
581 out). The value of the overall timeout can be changed by specifying an
582 additional sub-option for "callout", called "maxwait". For example:
583
584 verify = sender/callout=5s,maxwait=20s
585
586 4. Changes to the "personal" filter test:
587
588 (1) The list of non-personal local parts in From: addresses has been
589 extended to include "listserv", "majordomo", "*-request", and "owner-*",
590 taken from the Sieve specification recommendations.
591
592 (2) If the message contains any header line starting with "List-" it is
593 treated as non-personal.
594
595 (3) The test for "circular" in the Subject: header line has been removed
596 because it now seems ill-conceived.
597
598 5. The autoreply transport has a new option called never_mail. This is an
599 address list. If any run of the transport creates a message with a
600 recipient that matches any item in the list, that recipient is quietly
601 discarded. If all recipients are discarded, no message is created.
602
603
604Version 4.40
605------------
606
607The documentation is up-to-date for the 4.40 release. What follows here is a
608brief list of the new features that have been added since 4.30.
609
610 1. log_incoming_interface affects more log lines.
611
612 2. New ACL modifier "control = submission".
613
614 3. CONFIGURE_OWNER can be set at build time to define an alternative owner for
615 the configuration file, in addition to root and exim.
616
617 4. Added expansion variables $body_zerocount, $recipient_data, and
618 $sender_data.
619
620 5. The time of last modification of the "new" subdirectory is now used as the
621 "mailbox time last read" when there is a quota error for a maildir
622 delivery.
623
624 6. The special item "+ignore_unknown" may now appear in host lists.
625
626 7. The special domain-matching patterns @mx_any, @mx_primary, and
627 @mx_secondary can now be followed by "/ignore=<ip list>".
628
629 8. New expansion conditions: match_domain, match_address, match_local_part,
630 lt, lti, le, lei, gt, gti, ge, and new expansion operators time_interval,
631 eval10, and base62d.
632
633 9. New lookup type called "iplsearch".
634
63510. New log selectors ident_timeout, tls_certificate_verified, queue_time,
636 deliver_time, outgoing_port, return_path_on_delivery.
637
63811. New global options smtp_active_hostname and tls_require_ciphers.
639
64012. Exinext has -C and -D options.
641
64213. "domainlist_cache" forces caching of an apparently variable list.
643
64414. For compatibility with Sendmail, the command line option -prval:sval
645 is equivalent to -oMr rval -oMs sval.
646
64715. New callout options use_sender and use_postmaster for use when verifying
648 recipients.
649
65016. John Jetmore's "exipick" utility has been added to the distribution.
651
65217. The TLS code now supports CRLs.
653
65418. The dnslookup router and the dnsdb lookup type now support the use of SRV
655 records.
656
65719. The redirect router has a new option called qualify_domain.
658
65920. exigrep's output now also includes lines that are not related to any
660 particular message, but which do match the pattern.
661
66221. New global option write_rejectlog. If it is set false, Exim no longer
663 writes anything to the reject log.
664
665****