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