1 $Cambridge: exim/doc/doc-txt/NewStuff,v 1.12 2004/11/19 09:45:54 ph10 Exp $
6 This file contains descriptions of new features that have been added to Exim,
7 but have not yet made it into the main manual (which is most conveniently
8 updated when there is a relatively large batch of changes). The doc/ChangeLog
9 file contains a listing of all changes, including bug fixes.
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
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".
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;
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
70 9. $host_address is now set to the target address during the checking of
73 10. 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
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
93 11. It is now permitted to omit both strings after an "if" condition; if the
94 condition is true, the result is the string "true". As before, when the
95 second string is omitted, a false condition yields an empty string. This
96 makes it less cumbersome to write custom ACL and router conditions. For
99 condition = ${if eq {$acl_m4}{1}{yes}{no}}
103 condition = ${if eq {$acl_m4}{1}{yes}}
105 (because the second string has always defaulted to ""), you can now write
107 condition = ${if eq {$acl_m4}{1}}
109 Previously this was a syntax error.
111 12. There is now a new "record type" that can be specified in dnsdb lookups. It
112 is "zns" (for "zone NS"). It performs a lookup for NS records on the given
113 domain, but if none are found, it removes the first component of the domain
114 name, and tries again. This process continues until NS records are found
115 or there are no more components left (or there's a DNS error). In other
116 words, it may return the name servers for a top-level domain, but it never
117 returns the root name servers. If there are no NS records for the top-level
118 domain, the lookup fails.
120 For example, ${lookup dnsdb{zns=xxx.quercite.com}} returns the name
121 servers for quercite.com, whereas ${lookup dnsdb{zns=xxx.edu}} returns
122 the name servers for edu, assuming in each case that there are no NS
123 records for the full domain name.
125 You should be careful about how you use this lookup because, unless the
126 top-level domain does not exist, the lookup will always return some host
127 names. The sort of use to which this might be put is for seeing if the name
128 servers for a given domain are on a blacklist. You can probably assume that
129 the name servers for the high-level domains such as .com or .co.uk are not
130 going to be on such a list.
136 1. There is a new Boolean global option called mua_wrapper, defaulting false.
137 This causes Exim to run an a restricted mode, in order to provide a very
140 Background: On a personal computer, it is a common requirement for all
141 email to be sent to a smarthost. There are plenty of MUAs that can be
142 configured to operate that way, for all the popular operating systems.
143 However, there are MUAs for Unix-like systems that cannot be so configured:
144 they submit messages using the command line interface of
145 /usr/sbin/sendmail. In addition, utility programs such as cron submit
148 Requirement: The requirement is for something that can provide the
149 /usr/sbin/sendmail interface and deliver messages to a smarthost, but not
150 provide any queueing or retrying facilities. Furthermore, the delivery to
151 the smarthost should be synchronous, so that if it fails, the sending MUA
152 is immediately informed. In other words, we want something that in effect
153 converts a command-line MUA into a TCP/SMTP MUA.
155 Solutions: There are a number of applications (for example, ssmtp) that do
156 this job. However, people have found them to be lacking in various ways.
157 For instance, some sites want to allow aliasing and forwarding before
158 sending to the smarthost.
160 Using Exim: Exim already had the necessary infrastructure for doing this
161 job. Just a few tweaks were needed to make it behave as required, though it
162 is somewhat of an overkill to use a fully-featured MTA for this purpose.
164 Setting mua_wrapper=true causes Exim to run in a special mode where it
165 assumes that it is being used to "wrap" a command-line MUA in the manner
168 If you set mua_wrapper=true, you also need to provide a compatible router
169 and transport configuration. Typically there will be just one router and
170 one transport, sending everything to a smarthost.
172 When run in MUA wrapping mode, the behaviour of Exim changes in the
175 (a) A daemon cannot be run, nor will Exim accept incoming messages from
176 inetd. In other words, the only way to submit messages is via the
179 (b) Each message is synchonously delivered as soon as it is received (-odi
180 is assumed). All queueing options (queue_only, queue_smtp_domains,
181 control=queue, control=freeze in an ACL etc.) are quietly ignored. The
182 Exim reception process does not finish until the delivery attempt is
183 complete. If the delivery was successful, a zero return code is given.
185 (c) Address redirection is permitted, but the final routing for all
186 addresses must be to the same remote transport, and to the same list of
187 hosts. Furthermore, the return_address must be the same for all
188 recipients, as must any added or deleted header lines. In other words,
189 it must be possible to deliver the message in a single SMTP
190 transaction, however many recipients there are.
192 (d) If the conditions in (c) are not met, or if routing any address results
193 in a failure or defer status, or if Exim is unable to deliver all the
194 recipients successfully to one of the hosts immediately, delivery of
195 the entire message fails.
197 (e) Because no queueing is allowed, all failures are treated as permanent;
198 there is no distinction between 4xx and 5xx SMTP response codes from
199 the smarthost. Furthermore, because only a single yes/no response can
200 be given to the caller, it is not possible to deliver to some
201 recipients and not others. If there is an error (temporary or
202 permanent) for any recipient, all are failed.
204 (f) If more than one host is listed, Exim will try another host after a
205 connection failure or a timeout, in the normal way. However, if this
206 kind of failure happens for all the hosts, the delivery fails.
208 (g) When delivery fails, an error message is written to the standard error
209 stream (as well as to Exim's log), and Exim exits to the caller with a
210 return code value 1. The message is expunged from Exim's spool files.
211 No bounce messages are ever generated.
213 (h) No retry data is maintained, and any retry rules are ignored.
215 (i) A number of Exim options are overridden: deliver_drop_privilege is
216 forced true, max_rcpt in the smtp transport is forced to "unlimited",
217 remote_max_parallel is forced to one, and fallback hosts are ignored.
219 The overall effect is that Exim makes a single synchronous attempt to
220 deliver the message, failing if there is any kind of problem. Because no
221 local deliveries are done and no daemon can be run, Exim does not need root
222 privilege. It should be possible to run it setuid=exim instead of
223 setuid=root. See section 48.3 in the 4.40 manual for a general discussion
224 about the advantages and disadvantages of running without root privilege.
226 2. There have been problems with DNS servers when SRV records are looked up.
227 Some mis-behaving servers return a DNS error or timeout when a non-existent
228 SRV record is sought. Similar problems have in the past been reported for
229 MX records. The global dns_again_means_nonexist option can help with this
230 problem, but it is heavy-handed because it is a global option. There are
231 now two new options for the dnslookup router. They are called
232 srv_fail_domains and mx_fail_domains. In each case, the value is a domain
233 list. If an attempt to look up an SRV or MX record results in a DNS failure
234 or "try again" response, and the domain matches the relevant list, Exim
235 behaves as if the DNS had responded "no such record". In the case of an SRV
236 lookup, this means that the router proceeds to look for MX records; in the
237 case of an MX lookup, it proceeds to look for A or AAAA records, unless the
238 domain matches mx_domains.
240 3. The following functions are now available in the local_scan() API:
242 (a) void header_remove(int occurrence, uschar *name)
244 This function removes header lines. If "occurrence" is zero or negative,
245 all occurrences of the header are removed. If occurrence is greater
246 than zero, that particular instance of the header is removed. If no
247 header(s) can be found that match the specification, the function does
250 (b) BOOL header_testname(header_line *hdr, uschar *name, int length,
253 This function tests whether the given header has the given name. It
254 is not just a string comparison, because whitespace is permitted
255 between the name and the colon. If the "notdel" argument is TRUE, a
256 FALSE return is forced for all "deleted" headers; otherwise they are
257 not treated specially. For example:
259 if (header_testname(h, US"X-Spam", 6, TRUE)) ...
261 (c) void header_add_at_position(BOOL after, uschar *name, BOOL topnot,
262 int type, char *format, ...)
264 This function adds a new header line at a specified point in the header
265 chain. If "name" is NULL, the new header is added at the end of the
266 chain if "after" is TRUE, or at the start if "after" is FALSE. If
267 "name" is not NULL, the headers are searched for the first non-deleted
268 header that matches the name. If one is found, the new header is added
269 before it if "after" is FALSE. If "after" is true, the new header is
270 added after the found header and any adjacent subsequent ones with the
271 same name (even if marked "deleted"). If no matching non-deleted header
272 is found, the "topnot" option controls where the header is added. If it
273 is TRUE, addition is at the top; otherwise at the bottom. Thus, to add
274 a header after all the Received: headers, or at the top if there are no
275 Received: headers, you could use
277 header_add_at_position(TRUE, US"Received", TRUE, ' ', "X-xxx: ...");
279 Normally, there is always at least one non-deleted Received: header,
280 but there may not be if received_header_text expands to an empty
283 (d) BOOL receive_remove_recipient(uschar *recipient)
285 This is a convenience function to remove a named recipient from the
286 list of recipients. It returns TRUE if a recipient was removed, and
287 FALSE if no matching recipient could be found. The argument must be a
288 complete email address.
290 4. When an ACL "warn" statement adds one or more header lines to a message,
291 they are added at the end of the existing header lines by default. It is
292 now possible to specify that any particular header line should be added
293 right at the start (before all the Received: lines) or immediately after
294 the first block of Received: lines in the message. This is done by
295 specifying :at_start: or :after_received: (or, for completeness, :at_end:)
296 before the text of the header line. (Header text cannot start with a colon,
297 as there has to be a header name first.) For example:
299 warn message = :after_received:X-My-Header: something or other...
301 If more than one header is supplied in a single warn statement, each one is
302 treated independently and can therefore be placed differently. If you add
303 more than one line at the start, or after the Received: block, they will
304 end up in reverse order.
306 Warning: This facility currently applies only to header lines that are
307 added in an ACL. It does NOT work for header lines that are added in a
308 system filter or in a router or transport.
310 5. There is now a new error code that can be used in retry rules. Its name is
311 "rcpt_4xx", and there are three forms. A literal "rcpt_4xx" matches any 4xx
312 error received for an outgoing SMTP RCPT command; alternatively, either the
313 first or both of the x's can be given as digits, for example: "rcpt_45x" or
314 "rcpt_436". If you want (say) to recognize 452 errors given to RCPT
315 commands by a particular host, and have only a one-hour retry for them, you
316 can set up a retry rule of this form:
318 the.host.name rcpt_452 F,1h,10m
320 Naturally, this rule must come before any others that would match.
322 These new errors apply to both outgoing SMTP (the smtp transport) and
323 outgoing LMTP (either the lmtp transport, or the smtp transport in LMTP
324 mode). Note, however, that they apply only to responses to RCPT commands.
326 6. The "postmaster" option of the callout feature of address verification has
327 been extended to make it possible to use a non-empty MAIL FROM address when
328 checking a postmaster address. The new suboption is called "postmaster_
329 mailfrom", and you use it like this:
331 require verify = sender/callout=postmaster_mailfrom=abc@x.y.z
333 Providing this suboption causes the postmaster check to be done using the
334 given address. The original "postmaster" option is equivalent to
336 require verify = sender/callout=postmaster_mailfrom=
338 If both suboptions are present, the rightmost one overrides.
342 (1) If you use a non-empty sender address for postmaster checking, there is
343 the likelihood that the remote host will itself initiate a callout
344 check back to your host to check that address. As this is a "normal"
345 callout check, the sender will most probably be empty, thus avoiding
346 possible callout loops. However, to be on the safe side it would be
347 best to set up your own ACLs so that they do not do sender verification
348 checks when the recipient is the address you use for postmaster callout
351 (2) The caching arrangements for postmaster checking do NOT take account of
352 the sender address. It is assumed that either the empty address, or a
353 fixed non-empty address will be used. All that Exim remembers is that
354 the postmaster check for the domain succeeded or failed.
356 7. When verifying addresses in header lines using the verify=header_sender
357 option, Exim behaves by default as if the addresses are envelope sender
358 addresses from a message. Callout verification therefore tests to see
359 whether a bounce message could be delivered, by using an empty address in
360 the MAIL FROM command. However, it is arguable that these addresses might
361 never be used as envelope senders, and could therefore justifiably reject
362 bounce messages (empty senders). There is now an additional callout option
363 for verify=header_sender that allows you to specify what address to use in
364 the MAIL FROM command. You use it as in this example:
366 require verify = header_sender/callout=mailfrom=abcd@x.y.z
370 (1) As in the case of postmaster_mailfrom (see above), you should think
371 about possible loops.
373 (2) In this case, as in the case of recipient callouts with non-empty
374 senders (the use_sender option), caching is done on the basis of a
375 recipient/sender pair.
377 8. If you build Exim with USE_READLINE=yes in Local/Makefile, it will try to
378 load libreadline dynamically whenever the -be (test expansion) option is
379 used without command line arguments. If successful, it will then use
380 readline() for reading the test data. A line history is supported. By the
381 time Exim does this, it is running as the calling user, so this should not
382 cause any security problems. Security is the reason why this is NOT
383 supported for -bt or -bv, when Exim is running as root or exim,
384 respectively. Note that this option adds to the size of the Exim binary,
385 because the dynamic loading library is not otherwise included. On my
386 desktop it adds about 2.5K. You may need to add -ldl to EXTRA_LIBS when you
387 set USE_READLINE=yes.
389 9. Added ${str2b64:<string>} to the expansion operators. This operator
390 converts an arbitrary string into one that is base64 encoded.
392 10. A new authenticator, called cyrus_sasl, has been added. This requires
393 the presence of the Cyrus SASL library; it authenticates by calling this
394 library, which supports a number of authentication mechanisms, including
395 PLAIN and LOGIN, but also several others that Exim does not support
396 directly. The code for this authenticator was provided by Matthew
397 Byng-Maddick of A L Digital Ltd (http://www.aldigital.co.uk). Here follows
400 xx. THE CYRUS_SASL AUTHENTICATOR
402 The cyrus_sasl authenticator provides server support for the Cyrus library
403 Implementation of the RFC 2222 "Simple Authentication and Security Layer".
404 It provides a gatewaying mechanism directly to the Cyrus interface, so if
405 your Cyrus library can do, for example, CRAM-MD5, then so can the
406 cyrus_sasl authenticator. By default it uses the public name of the driver
407 to determine which mechanism to support.
409 Where access to some kind of secret file is required, for example in GSSAPI
410 or CRAM-MD5, it is worth noting that the authenticator runs as the exim
411 user, and that the Cyrus SASL library has no way of escalating privileges
412 by default. You may also find you need to set environment variables,
413 depending on the driver you are using.
415 xx.1 Using cyrus_sasl as a server
417 The cyrus_sasl authenticator has four private options. It puts the username
418 (on a successful authentication) into $1.
420 server_hostname Type: string* Default: $primary_hostname
422 This option selects the hostname that is used when communicating with
423 the library. It is up to the underlying SASL plug-in what it does with
426 server_mech Type: string Default: public_name
428 This option selects the authentication mechanism this driver should
429 use. It allows you to use a different underlying mechanism from the
430 advertised name. For example:
434 public_name = X-ANYTHING
435 server_mech = CRAM-MD5
438 server_realm Type: string Default: unset
440 This is the SASL realm that the server is claiming to be in.
442 server_service Type: string Default: "smtp"
444 This is the SASL service that the server claims to implement.
446 For straigthforward cases, you do not need to set any of the
447 authenticator's private options. All you need to do is to specify an
448 appropriate mechanism as the public name. Thus, if you have a SASL library
449 that supports CRAM-MD5 and PLAIN, you might have two authenticators as
454 public_name = CRAM-MD5
462 11. There is a new global option called tls_on_connect_ports. Its value must be
463 a list of port numbers; the most common use is expected to be
465 tls_on_connect_ports = 465
467 Setting this option has the same effect as -tls-on-connect on the command
468 line, but only for the specified ports. It applies to all connections, both
469 via the daemon and via inetd. You still need to specify all the ports for
470 the daemon (using daemon_smtp_ports or local_interfaces or the -X command
471 line option) because this option does not add an extra port -- rather, it
472 specifies different behaviour on a port that is defined elsewhere. The
473 -tls-on-connect command line option overrides tls_on_connect_ports, and
474 forces tls-on-connect for all ports.
476 12. There is a new ACL that is run when a DATA command is received, before the
477 data itself is received. The ACL is defined by acl_smtp_predata. (Compare
478 acl_smtp_data, which is run after the data has been received.)
479 This new ACL allows a negative response to be given to the DATA command
480 itself. Header lines added by MAIL or RCPT ACLs are not visible at this
481 time, but any that are defined here are visible when the acl_smtp_data ACL
484 13. The "control=submission" ACL modifier has an option "/domain=xxx" which
485 specifies the domain to be used when creating From: or Sender: lines using
486 the authenticated id as a local part. If the option is supplied with an
487 empty domain, that is, just "/domain=", Exim assumes that the authenticated
488 id is a complete email address, and it uses it as is when creating From:
491 14. It is now possible to make retry rules that apply only when the failing
492 message has a specific sender. In particular, this can be used to define
493 retry rules that apply only to bounce messages. The syntax is to add a new
494 third item to a retry rule, of the form "senders=<address list>". The retry
495 timings themselves then become the fourth item. For example:
497 * * senders=: F,1h,30m
499 would match all bounce messages. If the address list contains white space,
500 it must be enclosed in quotes. For example:
502 a.domain timeout senders="x@b.dom : y@c.dom" G,8h,10m,1.5
504 When testing retry rules using -brt, you can supply a sender using the -f
505 command line option, like this:
507 exim -f "" -brt user@dom.ain
509 If you do not set -f with -brt, a retry rule that contains a senders list
510 will never be matched.
512 15. Two new control modifiers have been added to ACLs: "control = enforce_sync"
513 and "control = no_enforce_sync". This makes it possible to be selective
514 about when SMTP synchronization is enforced. The global option
515 smtp_enforce_sync now specifies the default state of the switch. These
516 controls can appear in any ACL, but the most obvious place to put them is
517 in the ACL defined by acl_smtp_connect, which is run at the start of an
518 incoming SMTP connection, before the first synchronization check.
520 16. Another two new control modifiers are "control = caseful_local_part" and
521 "control = caselower_local_part". These are permitted only in the ACL
522 specified by acl_smtp_rcpt (i.e. during RCPT processing). By default, the
523 contents of $local_part are lower cased before ACL processing.
524 After "control = caseful_local_part", any uppercase letters in the original
525 local part are restored in $local_part for the rest of the ACL, or until
526 "control = caselower_local_part" is encountered. However, this applies only
527 to local part handling that takes place directly in the ACL (for example,
528 as a key in lookups). If a "verify = recipient" test is obeyed, the
529 case-related handling of the local part during the verification is
530 controlled by the router configuration (see the caseful_local_part generic
533 This facility could be used, for example, to add a spam score to local
534 parts containing upper case letters. For example, using $acl_m4 to
535 accumulate the spam score:
537 warn control = caseful_local_part
538 set acl_m4 = ${eval:\
540 ${if match{$local_part}{[A-Z]}{1}{0}}\
542 control = caselower_local_part
544 Notice that we put back the lower cased version afterwards, assuming that
545 is what is wanted for subsequent tests.
547 17. The option hosts_connection_nolog is provided so that certain hosts can be
548 excepted from logging when the +smtp_connection log selector is set. For
549 example, you might want not to log SMTP connections from local processes,
550 or from 127.0.0.1, or from your local LAN. The option is a host list with
551 an unset default. Because it is consulted in the main loop of the daemon,
552 you should strive to restrict its value to a short inline list of IP
553 addresses and networks. To disable logging SMTP connections from local
554 processes, you must create a host list with an empty item. For example:
556 hosts_connection_nolog = :
558 If the +smtp_connection log selector is not set, this option has no effect.
560 18. There is now an acl called acl_smtp_quit, which is run for the QUIT
561 command. The outcome of the ACL does not affect the response code to QUIT,
562 which is always 221. Thus, the ACL does not in fact control any access.
563 For this reason, the only verbs that are permitted are "accept" and "warn".
565 The ACL can be used for tasks such as custom logging at the end of an SMTP
566 session. For example, you can use ACL variables in other ACLs to count
567 messages, recipients, etc., and log the totals at QUIT time using one or
568 more "logwrite" modifiers on a "warn" command.
570 You do not need to have a final "accept", but if you do, you can use a
571 "message" modifier to specify custom text that is sent as part of the 221
574 This ACL is run only for a "normal" QUIT. For certain kinds of disastrous
575 failure (for example, failure to open a log file, or when Exim is bombing
576 out because it has detected an unrecoverable error), all SMTP commands
577 from the client are given temporary error responses until QUIT is received
578 or the connection is closed. In these special cases, the ACL is not run.
580 19. The appendfile transport has two new options, mailbox_size and mailbox_
581 filecount. If either these options are set, it is expanded, and the result
582 is taken as the current size of the mailbox or the number of files in the
583 mailbox, respectively. This makes it possible to use some external means of
584 maintaining the data about the size of a mailbox for enforcing quota
585 limits. The result of expanding these option values must be a decimal
586 number, optionally followed by "K" or "M".
588 20. It seems that there are broken clients in use that cannot handle multiline
589 SMTP responses. Can't people who implement these braindead programs read?
590 RFC 821 mentions multiline responses, and it is over 20 years old. They
591 must handle multiline responses for EHLO, or do they still use HELO?
592 Anyway, here is YAWFAB (yet another workaround for asinine brokenness).
593 There's a new ACL switch that can be set by
595 control = no_multiline_responses
597 If this is set, it suppresses multiline SMTP responses from ACL rejections.
598 One way of doing this would have been just to put out these responses as
599 one long line. However, RFC 2821 specifies a maximum of 512 bytes per
600 response ("use multiline responses for more" it says), and some of the
601 responses might get close to that. So I have implemented this by doing two
604 (1) Extra information that is normally output as part of a rejection
605 caused by sender verification failure is omitted. Only the final line
606 (typically "sender verification failed") is now sent.
608 (2) If a "message" modifier supplies a multiline response, only the first
611 The setting of the switch can, of course, be made conditional on the
614 21. There is now support for the libradius library that comes with FreeBSD.
615 This is an alternative to the radiusclient library that Exim already
616 supports. To use the FreeBSD library, you need to set
618 RADIUS_LIB_TYPE=RADLIB
620 in Local/Makefile, in addition to RADIUS_CONFIGURE_FILE, and you probably
621 also need -libradius in EXTRALIBS.
627 1. The "personal" filter test is brought up-to-date with recommendations from
628 the Sieve specification: (a) The list of non-personal From: addresses now
629 includes "listserv", "majordomo", and "*-request"; (b) If the message
630 contains any header line starting with "List=-" it is treated as
633 2. The Sieve functionality has been extended to support the "copy" and
634 "vacation" extensions, and comparison tests.
636 3. There is now an overall timeout for performing a callout verification. It
637 defaults to 4 times the callout timeout, which applies to individual SMTP
638 commands during the callout. The overall timeout applies when there is more
639 than one host that can be tried. The timeout is checked before trying the
640 next host. This prevents very long delays if there are a large number of
641 hosts and all are timing out (e.g. when the network connections are timing
642 out). The value of the overall timeout can be changed by specifying an
643 additional sub-option for "callout", called "maxwait". For example:
645 verify = sender/callout=5s,maxwait=20s
647 4. Changes to the "personal" filter test:
649 (1) The list of non-personal local parts in From: addresses has been
650 extended to include "listserv", "majordomo", "*-request", and "owner-*",
651 taken from the Sieve specification recommendations.
653 (2) If the message contains any header line starting with "List-" it is
654 treated as non-personal.
656 (3) The test for "circular" in the Subject: header line has been removed
657 because it now seems ill-conceived.
659 5. The autoreply transport has a new option called never_mail. This is an
660 address list. If any run of the transport creates a message with a
661 recipient that matches any item in the list, that recipient is quietly
662 discarded. If all recipients are discarded, no message is created.
668 The documentation is up-to-date for the 4.40 release. What follows here is a
669 brief list of the new features that have been added since 4.30.
671 1. log_incoming_interface affects more log lines.
673 2. New ACL modifier "control = submission".
675 3. CONFIGURE_OWNER can be set at build time to define an alternative owner for
676 the configuration file, in addition to root and exim.
678 4. Added expansion variables $body_zerocount, $recipient_data, and
681 5. The time of last modification of the "new" subdirectory is now used as the
682 "mailbox time last read" when there is a quota error for a maildir
685 6. The special item "+ignore_unknown" may now appear in host lists.
687 7. The special domain-matching patterns @mx_any, @mx_primary, and
688 @mx_secondary can now be followed by "/ignore=<ip list>".
690 8. New expansion conditions: match_domain, match_address, match_local_part,
691 lt, lti, le, lei, gt, gti, ge, and new expansion operators time_interval,
694 9. New lookup type called "iplsearch".
696 10. New log selectors ident_timeout, tls_certificate_verified, queue_time,
697 deliver_time, outgoing_port, return_path_on_delivery.
699 11. New global options smtp_active_hostname and tls_require_ciphers.
701 12. Exinext has -C and -D options.
703 13. "domainlist_cache" forces caching of an apparently variable list.
705 14. For compatibility with Sendmail, the command line option -prval:sval
706 is equivalent to -oMr rval -oMs sval.
708 15. New callout options use_sender and use_postmaster for use when verifying
711 16. John Jetmore's "exipick" utility has been added to the distribution.
713 17. The TLS code now supports CRLs.
715 18. The dnslookup router and the dnsdb lookup type now support the use of SRV
718 19. The redirect router has a new option called qualify_domain.
720 20. exigrep's output now also includes lines that are not related to any
721 particular message, but which do match the pattern.
723 21. New global option write_rejectlog. If it is set false, Exim no longer
724 writes anything to the reject log.
projects / exim.git / blob