are available, similarly to the drivers. Because macros are sometimes used
for storing passwords, this option is restricted.
The output format is one item per line.
+.new
+For the "-bP macro <name>" form, if no such macro is found
+the exit status will be nonzero.
+.wen
.vitem &%-bp%&
.oindex "&%-bp%&"
separator used for the output list is the same as the one used for the
input, but a separator setting is not included in the output. For example:
.code
-${filter{a:b:c}{!eq{$item}{b}}
+${filter{a:b:c}{!eq{$item}{b}}}
.endd
yields &`a:c`&. At the end of the expansion, the value of &$item$& is restored
to what it was before. See also the &*map*& and &*reduce*& expansion items.
compiled with GnuTLS 3.5.0 or later,
.new
or OpenSSL 1.1.1 or later.
+The macro "_CRYPTO_HASH_SHA3" will be defined if it is supported.
.wen
.vindex "&$config_file$&"
The name of the main configuration file Exim is using.
-.vitem &$dkim_verify_status$& &&&
+.vitem &$dkim_verify_status$&
Results of DKIM verification.
For details see section &<<SECDKIMVFY>>&.
will need to be aware of the potential different format.
Using any of the ACL conditions noted will negate the reception benefit
-(as a Unix-mbox-format file is contructed for them).
-The transimssion benefit is maintained.
+(as a Unix-mbox-format file is constructed for them).
+The transmission benefit is maintained.
.option sqlite_lock_timeout main time 5s
.cindex "sqlite lookup type" "lock timeout"
separator in the usual way to avoid confusion under IPv6.
&*Note*&: Under current versions of OpenSSL, when a list of more than one
-file is used, the &$tls_in_ourcert$& veriable is unreliable.
+file is used, the &$tls_in_ourcert$& variable is unreliable.
&*Note*&: OCSP stapling is not usable under OpenSSL
when a list of more than one file is used.
On (at least some) current Linux distributions the facility must be enabled
in the kernel by the sysadmin before the support is usable.
There is no option for control of the server side; if the system supports
-it it is always enebled. Note that legthy operations in the connect ACL,
+it it is always enabled. Note that lengthy operations in the connect ACL,
such as DNSBL lookups, will still delay the emission of the SMTP banner.
.option hosts_try_prdr smtp "host list&!!" *
When Exim has been built with TLS support, it advertises the availability of
the STARTTLS command to client hosts that match &%tls_advertise_hosts%&,
but not to any others. The default value of this option is *, which means
-that STARTTLS is alway advertised. Set it to blank to never advertise;
-this is reasonble for systems that want to use TLS only as a client.
+that STARTTLS is always advertised. Set it to blank to never advertise;
+this is reasonable for systems that want to use TLS only as a client.
If STARTTLS is to be used you
need to set some other options in order to make TLS available.
An older mode of operation can be enabled on a per-host basis by the
&%hosts_noproxy_tls%& option on the &(smtp)& transport. If the host matches
-this list the proxy process descibed above is not used; instead Exim
+this list the proxy process described above is not used; instead Exim
shuts down an existing TLS session being run by the delivery process
before passing the socket to a new process. The new process may then
try to start a new TLS session, and if successful, may try to re-authenticate
.code
require verify = recipient/callout=use_sender,hold
.endd
-It causes the connection to be helod open and used for any further recipients
+It causes the connection to be held open and used for any further recipients
and for eventual delivery (should that be done quickly).
Doing this saves on TCP and SMTP startup costs, and TLS costs also
when that is used for the connections.
As an example, the following will ban &"HTML mail"& (including that sent with
alternative plain text), while allowing HTML files to be attached. HTML
-coverletter mail attached to non-HMTL coverletter mail will also be allowed:
+coverletter mail attached to non-HTML coverletter mail will also be allowed:
.code
deny message = HTML mail is not accepted here
!condition = $mime_is_rfc822
.new
.cindex log "DKIM verification"
.cindex DKIM "verification logging"
-&%dkim%&: For message acceptance log lines, when an DKIM signture in the header
+&%dkim%&: For message acceptance log lines, when an DKIM signature in the header
verifies successfully a tag of DKIM is added, with one of the verified domains.
.next
.cindex log "DKIM verification"
.next
.cindex "log" "millisecond timestamps"
.cindex millisecond logging
-.cindex timstamps "millisecond, in logs"
+.cindex timestamps "millisecond, in logs"
&%millisec%&: Timestamps have a period and three decimal places of finer granularity
appended to the seconds value.
.next
off the &%outgoing_interface%& option.
.next
.cindex "log" "outgoing remote port"
-.cindex "port" "logging outgoint remote"
+.cindex "port" "logging outgoing remote"
.cindex "TCP/IP" "logging outgoing remote port"
&%outgoing_port%&: The remote port number is added to delivery log lines (those
containing => tags) following the IP address.
DKIM is a mechanism by which messages sent by some entity can be provably
linked to a domain which that entity controls. It permits reputation to
be tracked on a per-domain basis, rather than merely upon source IP address.
-DKIM is documented in RFC 4871.
+DKIM is documented in RFC 6376.
.new
As DKIM relies on the message being unchanged in transit, messages handled
Signers MUST use RSA keys of at least 1024 bits for all keys.
Signers SHOULD use RSA keys of at least 2048 bits.
.endd
-.wen
+
+Note also that the key content (the 'p=' field)
+in the DNS record is different between RSA and EC keys;
+for the former it is the base64 of the ASN.1 for the RSA public key
+(equivalent to the private-key .pem with the header/trailer stripped)
+but for EC keys it is the base64 of the pure key; no ASN.1 wrapping.
.wen
Signing is enabled by setting private options on the SMTP transport.
&%$dkim_selector%& expansion variables to determine the private key to use.
The result can either
.ilist
-be a valid RSA private key in ASCII armor, including line breaks.
+be a valid RSA private key in ASCII armor (.pem file), including line breaks
+.new
+.next
+with GnuTLS 3.6.0 or later, be a valid Ed25519 private key (same format as above)
+.wen
.next
start with a slash, in which case it is treated as a file that contains
-the private key.
+the private key
.next
be "0", "false" or the empty string, in which case the message will not
be signed. This case will not result in an error, even if &%dkim_strict%&
Signers MUST use RSA keys of at least 1024 bits for all keys.
Signers SHOULD use RSA keys of at least 2048 bits.
.endd
+
+Support for EC keys is being developed under
+&url(https://datatracker.ietf.org/doc/draft-ietf-dcrup-dkim-crypto/).
+They are considerably smaller than RSA keys for equivalent protection.
+As they are a recent development, users should consider dual-signing
+(by setting a list of selectors, and an expansion for this option)
+for some transition period.
+The "_CRYPTO_SIGN_ED25519" macro will be defined if support is present
+for EC keys.
.wen
.option dkim_hash smtp string&!! sha256
The default list is available for the expansion in the macro
"_DKIM_SIGN_HEADERS".
-If a name is repeated, multiple headers by that name (or the absence therof)
+If a name is repeated, multiple headers by that name (or the absence thereof)
will be signed. The textually later headers in the headers part of the
message are signed first, if there are multiples.
If an '=' prefix is used, all headers that are present with this name
will be signed.
If a '+' prefix if used, all headers that are present with this name
-will be signed, and one signtature added for a missing header with the
+will be signed, and one signature added for a missing header with the
name will be appended.
.vitem &%$dkim_algo%&
The algorithm used. One of 'rsa-sha1' or 'rsa-sha256'.
+.new
+If running under GnuTLS 3.6.0 or later, may also be 'ed25519-sha256'.
+The "_CRYPTO_SIGN_ED25519" macro will be defined if support is present
+for EC keys.
+.wen
.new
Note that RFC 8301 says:
or &%headers_charset%& main configuration option (otherwise),
to the
modified UTF-7 encoding specified by RFC 2060,
-with the following exception: All occurences of <sep>
+with the following exception: All occurrences of <sep>
(which has to be a single character)
are replaced with periods ("."), and all periods and slashes that are not
<sep> and are not in the <specials> string are BASE64 encoded.
before or after the action is associates with. Those which fire before
can be used to affect that action (more on this below).
-The third column in the table above says what section of the configumration
+The third column in the table above says what section of the configuration
should define the event action.
An additional variable, &$event_data$&, is filled with information varying