. Update the Copyright year (only) when changing content.
. /////////////////////////////////////////////////////////////////////////////
. Update the Copyright year (only) when changing content.
. /////////////////////////////////////////////////////////////////////////////
currently seen as the mainstream. Another record type called A6 was proposed
as better than AAAA because it had more flexibility. However, it was felt to be
over-complex, and its status was reduced to &"experimental"&.
currently seen as the mainstream. Another record type called A6 was proposed
as better than AAAA because it had more flexibility. However, it was felt to be
over-complex, and its status was reduced to &"experimental"&.
.cindex "symbolic link" "to source files"
Symbolic links to relevant source files are installed in the build directory.
.cindex "symbolic link" "to source files"
Symbolic links to relevant source files are installed in the build directory.
If this is the first time &'make'& has been run, it calls a script that builds
a make file inside the build directory, using the configuration files from the
&_Local_& directory. The new make file is then passed to another instance of
If this is the first time &'make'& has been run, it calls a script that builds
a make file inside the build directory, using the configuration files from the
&_Local_& directory. The new make file is then passed to another instance of
by Exim in conjunction with the &%-MC%& option. It signifies that the
connection to the remote host has been authenticated.
by Exim in conjunction with the &%-MC%& option. It signifies that the
connection to the remote host has been authenticated.
.vitem &%-MCD%&
.oindex "&%-MCD%&"
This option is not intended for use by external callers. It is used internally
by Exim in conjunction with the &%-MC%& option. It signifies that the
remote host supports the ESMTP &_DSN_& extension.
.vitem &%-MCD%&
.oindex "&%-MCD%&"
This option is not intended for use by external callers. It is used internally
by Exim in conjunction with the &%-MC%& option. It signifies that the
remote host supports the ESMTP &_DSN_& extension.
This option is interpreted by Sendmail to cause debug information to be sent
to the named file. It is ignored by Exim.
This option is interpreted by Sendmail to cause debug information to be sent
to the named file. It is ignored by Exim.
.vitem &%-z%&&~<&'log-line'&>
.oindex "&%-z%&"
This option writes its argument to Exim's logfile.
Use is restricted to administrators; the intent is for operational notes.
Quotes should be used to maintain a multi-word item as a single argument,
under most shells.
.vitem &%-z%&&~<&'log-line'&>
.oindex "&%-z%&"
This option writes its argument to Exim's logfile.
Use is restricted to administrators; the intent is for operational notes.
Quotes should be used to maintain a multi-word item as a single argument,
under most shells.
show how you can specify hosts that are permitted to send unqualified sender
and recipient addresses, respectively.
show how you can specify hosts that are permitted to send unqualified sender
and recipient addresses, respectively.
The &%log_selector%& option is used to increase the detail of logging
over the default:
.code
log_selector = +smtp_protocol_error +smtp_syntax_error \
+tls_certificate_verified
.endd
The &%log_selector%& option is used to increase the detail of logging
over the default:
.code
log_selector = +smtp_protocol_error +smtp_syntax_error \
+tls_certificate_verified
.endd
.endd
This transport is used for handling deliveries to pipes that are generated by
redirection (aliasing or users' &_.forward_& files). The &%return_output%&
.endd
This transport is used for handling deliveries to pipes that are generated by
redirection (aliasing or users' &_.forward_& files). The &%return_output%&
lookup. Lookups of this type are conditional expansion items. Different results
can be defined for the cases of lookup success and failure. See chapter
&<<CHAPexpand>>&, where string expansions are described in detail.
lookup. Lookups of this type are conditional expansion items. Different results
can be defined for the cases of lookup success and failure. See chapter
&<<CHAPexpand>>&, where string expansions are described in detail.
.next
Lists of domains, hosts, and email addresses can contain lookup requests as a
way of avoiding excessively long linear lists. In this case, the data that is
returned by the lookup is often (but not always) discarded; whether the lookup
succeeds or fails is what really counts. These kinds of list are described in
chapter &<<CHAPdomhosaddlists>>&.
.next
Lists of domains, hosts, and email addresses can contain lookup requests as a
way of avoiding excessively long linear lists. In this case, the data that is
returned by the lookup is often (but not always) discarded; whether the lookup
succeeds or fails is what really counts. These kinds of list are described in
chapter &<<CHAPdomhosaddlists>>&.
&`fail`& keyword causes a &'forced expansion failure'& &-- see section
&<<SECTforexpfai>>& for an explanation of what this means.
&`fail`& keyword causes a &'forced expansion failure'& &-- see section
&<<SECTforexpfai>>& for an explanation of what this means.
The supported DNS record types are A, CNAME, MX, NS, PTR, SOA, SPF, SRV, TLSA
and TXT, and, when Exim is compiled with IPv6 support, AAAA.
If no type is given, TXT is assumed.
The supported DNS record types are A, CNAME, MX, NS, PTR, SOA, SPF, SRV, TLSA
and TXT, and, when Exim is compiled with IPv6 support, AAAA.
If no type is given, TXT is assumed.
For any record type, if multiple records are found, the data is returned as a
concatenation, with newline as the default separator. The order, of course,
For any record type, if multiple records are found, the data is returned as a
concatenation, with newline as the default separator. The order, of course,
.cindex "SOA record" "in &(dnsdb)& lookup"
For an SOA lookup, while no result is obtained the lookup is redone with
successively more leading components dropped from the given domain.
.cindex "SOA record" "in &(dnsdb)& lookup"
For an SOA lookup, while no result is obtained the lookup is redone with
successively more leading components dropped from the given domain.
.section "Dnsdb lookup modifiers" "SECTdnsdb_mod"
.cindex "dnsdb modifiers"
.cindex "modifiers" "dnsdb"
.cindex "options" "dnsdb"
.section "Dnsdb lookup modifiers" "SECTdnsdb_mod"
.cindex "dnsdb modifiers"
.cindex "modifiers" "dnsdb"
.cindex "options" "dnsdb"
each followed by a comma,
that may appear before the record type.
each followed by a comma,
that may appear before the record type.
.cindex timeout "dns lookup"
.cindex "DNS" timeout
Timeout for the dnsdb lookup can be controlled by a retrans modifier.
The form is &"retrans_VAL"& where VAL is an Exim time specification
.cindex timeout "dns lookup"
.cindex "DNS" timeout
Timeout for the dnsdb lookup can be controlled by a retrans modifier.
The form is &"retrans_VAL"& where VAL is an Exim time specification
The default value is set by the main configuration option &%dns_retrans%&.
Retries for the dnsdb lookup can be controlled by a retry modifier.
The form if &"retry_VAL"& where VAL is an integer.
The default count is set by the main configuration option &%dns_retry%&.
The default value is set by the main configuration option &%dns_retrans%&.
Retries for the dnsdb lookup can be controlled by a retry modifier.
The form if &"retry_VAL"& where VAL is an integer.
The default count is set by the main configuration option &%dns_retry%&.
different types of pattern for each case are described, but first we cover some
general facilities that apply to all four kinds of list.
different types of pattern for each case are described, but first we cover some
general facilities that apply to all four kinds of list.
.cindex "&`+ignore_defer`&"
A temporary DNS lookup failure normally causes a defer action (except when
&%dns_again_means_nonexist%& converts it into a permanent error). However,
.cindex "&`+ignore_defer`&"
A temporary DNS lookup failure normally causes a defer action (except when
&%dns_again_means_nonexist%& converts it into a permanent error). However,
&`+ignore_unknown`& and &`+include_unknown`&, as described in the previous
section. These options should be used with care, probably only in non-critical
host lists such as whitelists.
&`+ignore_unknown`& and &`+include_unknown`&, as described in the previous
section. These options should be used with care, probably only in non-critical
host lists such as whitelists.
.cindex "&%certextract%&" "certificate fields"
.cindex "certificate" "extracting fields"
The <&'certificate'&> must be a variable of type certificate.
.cindex "&%certextract%&" "certificate fields"
.cindex "certificate" "extracting fields"
The <&'certificate'&> must be a variable of type certificate.
RDN elements of a single type may be selected by
a modifier of the type label; if so the expansion
result is a list (newline-separated by default).
RDN elements of a single type may be selected by
a modifier of the type label; if so the expansion
result is a list (newline-separated by default).
a right angle-bracket followed immediately by the new separator.
Recognised RDN type labels include "CN", "O", "OU" and "DC".
a right angle-bracket followed immediately by the new separator.
Recognised RDN type labels include "CN", "O", "OU" and "DC".
prefix each list element with a type string and an equals sign.
Elements of only one type may be selected by a modifier
which is one of "dns", "uri" or "mail";
prefix each list element with a type string and an equals sign.
Elements of only one type may be selected by a modifier
which is one of "dns", "uri" or "mail";
.vitem "&*${env{*&<&'key'&>&*}{*&<&'string1'&>&*}{*&<&'string2'&>&*}}*&"
.cindex "expansion" "extracting value from environment"
.cindex "environment" "value from"
.vitem "&*${env{*&<&'key'&>&*}{*&<&'string1'&>&*}{*&<&'string2'&>&*}}*&"
.cindex "expansion" "extracting value from environment"
.cindex "environment" "value from"
To clarify "list of addresses in RFC 2822 format" mentioned above, Exim follows
a strict interpretation of header line formatting. Exim parses the bare,
unquoted portion of an email address and if it finds a comma, treats it as an
To clarify "list of addresses in RFC 2822 format" mentioned above, Exim follows
a strict interpretation of header line formatting. Exim parses the bare,
unquoted portion of an email address and if it finds a comma, treats it as an
.vitem &*${reverse_ip:*&<&'ipaddr'&>&*}*&
.cindex "expansion" "IP address"
This operator reverses an IP address; for IPv4 addresses, the result is in
.vitem &*${reverse_ip:*&<&'ipaddr'&>&*}*&
.cindex "expansion" "IP address"
This operator reverses an IP address; for IPv4 addresses, the result is in
of times it has been compiled. This serves to distinguish different
compilations of the same version of the program.
of times it has been compiled. This serves to distinguish different
compilations of the same version of the program.
content-scanning extension and the obsolete &%demime%& condition. For details,
see section &<<SECTdemimecond>>&.
content-scanning extension and the obsolete &%demime%& condition. For details,
see section &<<SECTdemimecond>>&.
.vitem &$dkim_cur_signer$& &&&
&$dkim_verify_status$& &&&
&$dkim_verify_reason$& &&&
.vitem &$dkim_cur_signer$& &&&
&$dkim_verify_status$& &&&
&$dkim_verify_reason$& &&&
When a message has been received this variable contains
a colon-separated list of signer domains and identities for the message.
For details see chapter &<<CHAPdkim>>&.
When a message has been received this variable contains
a colon-separated list of signer domains and identities for the message.
For details see chapter &<<CHAPdkim>>&.
.vitem &$exim_version$&
.vindex "&$exim_version$&"
This variable contains the version string of the Exim build.
The first character is a major version number, currently 4.
Then after a dot, the next group of digits is a minor version number.
There may be other characters following the minor version.
.vitem &$exim_version$&
.vindex "&$exim_version$&"
This variable contains the version string of the Exim build.
The first character is a major version number, currently 4.
Then after a dot, the next group of digits is a minor version number.
There may be other characters following the minor version.
It will be empty if &(DNSSEC)& was not requested,
&"no"& if the result was not labelled as authenticated data
and &"yes"& if it was.
It will be empty if &(DNSSEC)& was not requested,
&"no"& if the result was not labelled as authenticated data
and &"yes"& if it was.
the argument of a HELO or EHLO command. This is omitted if it is identical to
the verified host name or to the host's IP address in square brackets.
the argument of a HELO or EHLO command. This is omitted if it is identical to
the verified host name or to the host's IP address in square brackets.
.vitem &$sender_helo_dnssec$&
.vindex "&$sender_helo_dnssec$&"
This boolean variable is true if a successful HELO verification was
.cindex "DNS" "DNSSEC"
.vitem &$sender_helo_dnssec$&
.vindex "&$sender_helo_dnssec$&"
This boolean variable is true if a successful HELO verification was
.cindex "DNS" "DNSSEC"
If you have changed &%host_lookup_order%& so that &`bydns`& is not the first
mechanism in the list, then this variable will be false.
If you have changed &%host_lookup_order%& so that &`bydns`& is not the first
mechanism in the list, then this variable will be false.
It is only useful as the argument of a
&%certextract%& expansion item, &%md5%&, &%sha1%& or &%sha256%& operator,
or a &%def%& condition.
It is only useful as the argument of a
&%certextract%& expansion item, &%md5%&, &%sha1%& or &%sha256%& operator,
or a &%def%& condition.
outbound connection. It is only useful as the argument of a
&%certextract%& expansion item, &%md5%&, &%sha1%& or &%sha256%& operator,
or a &%def%& condition.
outbound connection. It is only useful as the argument of a
&%certextract%& expansion item, &%md5%&, &%sha1%& or &%sha256%& operator,
or a &%def%& condition.
.vitem &$tls_in_certificate_verified$&
.vindex "&$tls_in_certificate_verified$&"
This variable is set to &"1"& if a TLS certificate was verified when the
message was received, and &"0"& otherwise.
.vitem &$tls_in_certificate_verified$&
.vindex "&$tls_in_certificate_verified$&"
This variable is set to &"1"& if a TLS certificate was verified when the
message was received, and &"0"& otherwise.
connection, and Exim is configured to request a certificate from the client,
the value of the Distinguished Name of the certificate is made available in the
&$tls_in_peerdn$& during subsequent processing.
connection, and Exim is configured to request a certificate from the client,
the value of the Distinguished Name of the certificate is made available in the
&$tls_in_peerdn$& during subsequent processing.
The deprecated &$tls_peerdn$& variable refers to the inbound side
except when used in the context of an outbound SMTP delivery, when it refers to
The deprecated &$tls_peerdn$& variable refers to the inbound side
except when used in the context of an outbound SMTP delivery, when it refers to
connection, and Exim is configured to request a certificate from the server,
the value of the Distinguished Name of the certificate is made available in the
&$tls_out_peerdn$& during subsequent processing.
connection, and Exim is configured to request a certificate from the server,
the value of the Distinguished Name of the certificate is made available in the
&$tls_out_peerdn$& during subsequent processing.
processed and the message itself has been received, but before the final
acknowledgment is sent. See chapter &<<CHAPACL>>& for further details.
processed and the message itself has been received, but before the final
acknowledgment is sent. See chapter &<<CHAPACL>>& for further details.
.option acl_smtp_data_prdr main string&!! accept
.cindex "PRDR" "ACL for"
.cindex "DATA" "PRDR ACL for"
.cindex "&ACL;" "PRDR-related"
.cindex "&ACL;" "per-user data processing"
.option acl_smtp_data_prdr main string&!! accept
.cindex "PRDR" "ACL for"
.cindex "DATA" "PRDR ACL for"
.cindex "&ACL;" "PRDR-related"
.cindex "&ACL;" "per-user data processing"
This option defines the ACL that,
if the PRDR feature has been negotiated,
is run for each recipient after an SMTP DATA command has been
processed and the message itself has been received, but before the
acknowledgment is sent. See chapter &<<CHAPACL>>& for further details.
This option defines the ACL that,
if the PRDR feature has been negotiated,
is run for each recipient after an SMTP DATA command has been
processed and the message itself has been received, but before the
acknowledgment is sent. See chapter &<<CHAPACL>>& for further details.
.option acl_smtp_dkim main string&!! unset
.cindex DKIM "ACL for"
This option defines the ACL that is run for each DKIM signature
of a received message.
See chapter &<<CHAPdkim>>& for further details.
.option acl_smtp_dkim main string&!! unset
.cindex DKIM "ACL for"
This option defines the ACL that is run for each DKIM signature
of a received message.
See chapter &<<CHAPdkim>>& for further details.
extension. It defines the ACL that is run for each MIME part in a message. See
section &<<SECTscanmimepart>>& for details.
extension. It defines the ACL that is run for each MIME part in a message. See
section &<<SECTscanmimepart>>& for details.
.option acl_smtp_notquit main string&!! unset
.cindex "not-QUIT, ACL for"
This option defines the ACL that is run when an SMTP session
ends without a QUIT command being received.
See chapter &<<CHAPACL>>& for further details.
.option acl_smtp_notquit main string&!! unset
.cindex "not-QUIT, ACL for"
This option defines the ACL that is run when an SMTP session
ends without a QUIT command being received.
See chapter &<<CHAPACL>>& for further details.
.option acl_smtp_predata main string&!! unset
This option defines the ACL that is run when an SMTP DATA command is
.option acl_smtp_predata main string&!! unset
This option defines the ACL that is run when an SMTP DATA command is
It appears that more and more DNS zone administrators are breaking the rules
and putting domain names that look like IP addresses on the right hand side of
MX records. Exim follows the rules and rejects this, giving an error message
It appears that more and more DNS zone administrators are breaking the rules
and putting domain names that look like IP addresses on the right hand side of
MX records. Exim follows the rules and rejects this, giving an error message
practice, so to avoid &"Why can't Exim do this?"& complaints,
&%allow_mx_to_ip%& exists, in order to enable this heinous activity. It is not
recommended, except when you have no other choice.
practice, so to avoid &"Why can't Exim do this?"& complaints,
&%allow_mx_to_ip%& exists, in order to enable this heinous activity. It is not
recommended, except when you have no other choice.
.option dkim_verify_signers main "domain list&!!" $dkim_signers
.cindex DKIM "controlling calls to the ACL"
This option gives a list of DKIM domains for which the DKIM ACL is run.
It is expanded after the message is received; by default it runs
the ACL once for each signature in the message.
See chapter &<<CHAPdkim>>&.
.option dkim_verify_signers main "domain list&!!" $dkim_signers
.cindex DKIM "controlling calls to the ACL"
This option gives a list of DKIM domains for which the DKIM ACL is run.
It is expanded after the message is received; by default it runs
the ACL once for each signature in the message.
See chapter &<<CHAPdkim>>&.
parameter values are available in the external resolver interface structure,
but nowhere does it seem to describe how they are used or what you might want
to set in them.
parameter values are available in the external resolver interface structure,
but nowhere does it seem to describe how they are used or what you might want
to set in them.
match with this expanded domain list.
Use this option only if you talk directly to a resolver that is
match with this expanded domain list.
Use this option only if you talk directly to a resolver that is
bit in the answer. Some DNS servers may have an configuration option to
mark the answers from their own zones as verified (they set the AD bit).
Others do not have this option. It is considered as poor practice using
bit in the answer. Some DNS servers may have an configuration option to
mark the answers from their own zones as verified (they set the AD bit).
Others do not have this option. It is considered as poor practice using
Use this option only if you really have to (e.g. if you want
to use DANE for remote delivery to a server that is listed in the DNS
Use this option only if you really have to (e.g. if you want
to use DANE for remote delivery to a server that is listed in the DNS
-authoritive but the answer section is empty, the name of the first SOA
-record in the authoritive section is used instead.
-.wen
+authoritative but the answer section is empty, the name of the first SOA
+record in the authoritative section is used instead.
handled CR and LF characters in incoming messages. What happens now is
described in section &<<SECTlineendings>>&.
handled CR and LF characters in incoming messages. What happens now is
described in section &<<SECTlineendings>>&.
A NOTIFY=SUCCESS option requests success-DSN messages.
A NOTIFY= option with no argument requests that no delay or failure DSNs
are sent.
A NOTIFY=SUCCESS option requests success-DSN messages.
A NOTIFY= option with no argument requests that no delay or failure DSNs
are sent.
Exim's transports have an option for adding an &'Envelope-to:'& header to a
message when it is delivered, in exactly the same way as &'Return-path:'& is
handled. &'Envelope-to:'& records the original recipient address from the
Exim's transports have an option for adding an &'Envelope-to:'& header to a
message when it is delivered, in exactly the same way as &'Return-path:'& is
handled. &'Envelope-to:'& records the original recipient address from the
be present in incoming messages, and this option causes them to be removed at
the time the message is received, to avoid any problems that might occur when a
delivered message is subsequently sent on to some other recipient.
be present in incoming messages, and this option causes them to be removed at
the time the message is received, to avoid any problems that might occur when a
delivered message is subsequently sent on to some other recipient.
maximum size that your virus-scanner is configured to support, you may get
failures triggered by large mails. The right size to configure for the
virus-scanner depends upon what data is passed and the options in use but it's
maximum size that your virus-scanner is configured to support, you may get
failures triggered by large mails. The right size to configure for the
virus-scanner depends upon what data is passed and the options in use but it's
default Exim message size of 50M and a default ClamAV StreamMaxLength of 10M,
some problems may result.
default Exim message size of 50M and a default ClamAV StreamMaxLength of 10M,
some problems may result.
If the option is set, PRDR is advertised by Exim when operating as a server.
If the client requests PRDR, and more than one recipient, for a message
an additional ACL is called for each recipient after the message content
If the option is set, PRDR is advertised by Exim when operating as a server.
If the client requests PRDR, and more than one recipient, for a message
an additional ACL is called for each recipient after the message content
.cindex "RFC 1413" "query timeout"
.cindex "timeout" "for RFC 1413 call"
This sets the timeout on RFC 1413 identification calls. If it is set to zero,
.cindex "RFC 1413" "query timeout"
.cindex "timeout" "for RFC 1413 call"
This sets the timeout on RFC 1413 identification calls. If it is set to zero,
.option slow_lookup_log main integer 0
.cindex "logging" "slow lookups"
.cindex "dns" "logging slow lookups"
.option slow_lookup_log main integer 0
.cindex "logging" "slow lookups"
.cindex "dns" "logging slow lookups"
If the value is nonzero it is taken as a number of milliseconds
and lookups taking longer than this are logged.
Currently this applies only to DNS lookups.
If the value is nonzero it is taken as a number of milliseconds
and lookups taking longer than this are logged.
Currently this applies only to DNS lookups.
The former means that Exim was expecting to read an SMTP command; the latter
means that it was in the DATA phase, reading the contents of a message.
The former means that Exim was expecting to read an SMTP command; the latter
means that it was in the DATA phase, reading the contents of a message.
If the first character of the option is a &"$"& the option is
expanded before use and may depend on
&$sender_host_name$&, &$sender_host_address$& and &$sender_host_port$&.
If the first character of the option is a &"$"& the option is
expanded before use and may depend on
&$sender_host_name$&, &$sender_host_address$& and &$sender_host_port$&.
.option tls_eccurve main string&!! prime256v1
.cindex TLS "EC cryptography"
If built with a recent-enough version of OpenSSL,
.option tls_eccurve main string&!! prime256v1
.cindex TLS "EC cryptography"
If built with a recent-enough version of OpenSSL,
which tell the library to choose.
If the option is set to an empty string, no EC curves will be enabled.
which tell the library to choose.
If the option is set to an empty string, no EC curves will be enabled.
.option tls_verify_certificates main string&!! system
.cindex "TLS" "client certificate verification"
.cindex "certificate" "verification of client"
.option tls_verify_certificates main string&!! system
.cindex "TLS" "client certificate verification"
.cindex "certificate" "verification of client"
preceding 3.3.6 and a single file must be used.
With OpenSSL the certificates specified
explicitly
either by file or directory
are added to those given by the system default location.
preceding 3.3.6 and a single file must be used.
With OpenSSL the certificates specified
explicitly
either by file or directory
are added to those given by the system default location.
These certificates should be for the certificate authorities trusted, rather
than the public cert of individual clients. With both OpenSSL and GnuTLS, if
These certificates should be for the certificate authorities trusted, rather
than the public cert of individual clients. With both OpenSSL and GnuTLS, if
unless you really, really know what you are doing. See also the generic
transport option of the same name.
unless you really, really know what you are doing. See also the generic
transport option of the same name.
.option dnssec_request_domains routers "domain list&!!" unset
.cindex "MX record" "security"
.cindex "DNSSEC" "MX lookup"
.option dnssec_request_domains routers "domain list&!!" unset
.cindex "MX record" "security"
.cindex "DNSSEC" "MX lookup"
the dnssec request bit set. Any returns not having the Authenticated Data bit
(AD bit) set will be ignored and logged as a host-lookup failure.
This applies to all of the SRV, MX, AAAA, A lookup sequence.
the dnssec request bit set. Any returns not having the Authenticated Data bit
(AD bit) set will be ignored and logged as a host-lookup failure.
This applies to all of the SRV, MX, AAAA, A lookup sequence.
Exim will not pass on DSN requests to downstream DSN-aware hosts but will
instead send a success DSN as if the next hop does not support DSN.
Not effective on redirect routers.
Exim will not pass on DSN requests to downstream DSN-aware hosts but will
instead send a success DSN as if the next hop does not support DSN.
Not effective on redirect routers.
.cindex "header lines" "adding"
.cindex "router" "adding header lines"
This option specifies a list of text headers,
.cindex "header lines" "adding"
.cindex "router" "adding header lines"
This option specifies a list of text headers,
that is associated with any addresses that are accepted by the router.
Each item is separately expanded, at routing time. However, this
option has no effect when an address is just being verified. The way in which
that is associated with any addresses that are accepted by the router.
Each item is separately expanded, at routing time. However, this
option has no effect when an address is just being verified. The way in which
.cindex "header lines" "removing"
.cindex "router" "removing header lines"
This option specifies a list of text headers,
.cindex "header lines" "removing"
.cindex "router" "removing header lines"
This option specifies a list of text headers,
that is associated with any addresses that are accepted by the router.
Each item is separately expanded, at routing time. However, this
option has no effect when an address is just being verified. The way in which
that is associated with any addresses that are accepted by the router.
Each item is separately expanded, at routing time. However, this
option has no effect when an address is just being verified. The way in which
routers, and this can lead to problems with duplicates -- see the similar
warning for &%headers_add%& above.
routers, and this can lead to problems with duplicates -- see the similar
warning for &%headers_add%& above.
&*Warning 3*&: Because of the separate expansion of the list items,
items that contain a list separator must have it doubled.
To avoid this, change the list separator (&<<SECTlistsepchange>>&).
&*Warning 3*&: Because of the separate expansion of the list items,
items that contain a list separator must have it doubled.
To avoid this, change the list separator (&<<SECTlistsepchange>>&).
.section "Problems with DNS lookups" "SECTprowitdnsloo"
There have been problems with DNS servers when SRV records are looked up.
.section "Problems with DNS lookups" "SECTprowitdnsloo"
There have been problems with DNS servers when SRV records are looked up.
SRV record is sought. Similar problems have in the past been reported for
MX records. The global &%dns_again_means_nonexist%& option can help with this
problem, but it is heavy-handed because it is a global option.
SRV record is sought. Similar problems have in the past been reported for
MX records. The global &%dns_again_means_nonexist%& option can help with this
problem, but it is heavy-handed because it is a global option.
an address; if such a router is expected to handle "all remaining non-local
domains", then it is important to set &%no_more%&.
an address; if such a router is expected to handle "all remaining non-local
domains", then it is important to set &%no_more%&.
The router will defer rather than decline if the domain
is found in the &%fail_defer_domains%& router option.
The router will defer rather than decline if the domain
is found in the &%fail_defer_domains%& router option.
.option fail_defer_domains dnslookup "domain list&!!" unset
.cindex "MX record" "not found"
DNS lookups for domains matching &%fail_defer_domains%&
.option fail_defer_domains dnslookup "domain list&!!" unset
.cindex "MX record" "not found"
DNS lookups for domains matching &%fail_defer_domains%&
domain while the DNS configuration is not ready.
However, it will result in any message with mistyped domains
also being queued.
domain while the DNS configuration is not ready.
However, it will result in any message with mistyped domains
also being queued.
files and pipes, and for generating autoreplies. See the &%file_transport%&,
&%pipe_transport%& and &%reply_transport%& descriptions below.
files and pipes, and for generating autoreplies. See the &%file_transport%&,
&%pipe_transport%& and &%reply_transport%& descriptions below.
If success DSNs have been requested
.cindex "DSN" "success"
.cindex "Delivery Status Notification" "success"
redirection triggers one and the DSN options are not passed any further.
If success DSNs have been requested
.cindex "DSN" "success"
.cindex "Delivery Status Notification" "success"
redirection triggers one and the DSN options are not passed any further.
&_/dev/null_& as a destination, but it can be independently disabled.
&*Warning*&: If &':blackhole:'& appears anywhere in a redirection list, no
&_/dev/null_& as a destination, but it can be independently disabled.
&*Warning*&: If &':blackhole:'& appears anywhere in a redirection list, no
.cindex "header lines" "adding in transport"
.cindex "transport" "header lines; adding"
This option specifies a list of text headers,
.cindex "header lines" "adding in transport"
.cindex "transport" "header lines; adding"
This option specifies a list of text headers,
which are (separately) expanded and added to the header
portion of a message as it is transported, as described in section
&<<SECTheadersaddrem>>&. Additional header lines can also be specified by
which are (separately) expanded and added to the header
portion of a message as it is transported, as described in section
&<<SECTheadersaddrem>>&. Additional header lines can also be specified by
.cindex "header lines" "removing"
.cindex "transport" "header lines; removing"
This option specifies a list of header names,
.cindex "header lines" "removing"
.cindex "transport" "header lines; removing"
This option specifies a list of header names,
these headers are omitted from the message as it is transported, as described
in section &<<SECTheadersaddrem>>&. Header removal can also be specified by
routers.
these headers are omitted from the message as it is transported, as described
in section &<<SECTheadersaddrem>>&. Header removal can also be specified by
routers.
&%force_command%& is set, expanding out to the original argument vector as
separate items, similarly to a Unix shell &`"$@"`& construct.
&%force_command%& is set, expanding out to the original argument vector as
separate items, similarly to a Unix shell &`"$@"`& construct.
.option ignore_status pipe boolean false
If this option is true, the status returned by the subprocess that is set up to
run the command is ignored, and Exim behaves as if zero had been returned.
.option ignore_status pipe boolean false
If this option is true, the status returned by the subprocess that is set up to
run the command is ignored, and Exim behaves as if zero had been returned.
&*Note*&: This option does not apply to timeouts, which do not return a status.
See the &%timeout_defer%& option for how timeouts are handled.
&*Note*&: This option does not apply to timeouts, which do not return a status.
See the &%timeout_defer%& option for how timeouts are handled.
.option log_defer_output pipe boolean false
.cindex "&(pipe)& transport" "logging output"
If this option is set, and the status returned by the command is
one of the codes listed in &%temp_errors%& (that is, delivery was deferred),
.option log_defer_output pipe boolean false
.cindex "&(pipe)& transport" "logging output"
If this option is set, and the status returned by the command is
one of the codes listed in &%temp_errors%& (that is, delivery was deferred),
-If this option is set, and the command returns any output, and also ends with a
-return code that is neither zero nor one of the return codes listed in
-&%temp_errors%& (that is, the delivery failed), the first line of output is
-written to the main log. This option and &%log_output%& are mutually exclusive.
-Only one of them may be set.
-
+If this option is set, and the command returns any output on stdout or
+stderr, and also ends with a return code that is neither zero nor one of
+the return codes listed in &%temp_errors%& (that is, the delivery
+failed), the first line of output is written to the main log. This
+option and &%log_output%& are mutually exclusive. Only one of them may
+be set.
-If this option is set and the command returns any output, the first line of
-output is written to the main log, whatever the return code. This option and
-&%log_fail_output%& are mutually exclusive. Only one of them may be set.
-
+If this option is set and the command returns any output on stdout or
+stderr, the first line of output is written to the main log, whatever
+the return code. This option and &%log_fail_output%& are mutually
+exclusive. Only one of them may be set.
.cindex "DNS" "DNSSEC"
DNS lookups for domains matching &%dnssec_request_domains%& will be done with
the dnssec request bit set. Any returns not having the Authenticated Data bit
.cindex "DNS" "DNSSEC"
DNS lookups for domains matching &%dnssec_request_domains%& will be done with
the dnssec request bit set. Any returns not having the Authenticated Data bit
This applies to all of the SRV, MX, AAAA, A lookup sequence.
This applies to all of the SRV, MX, AAAA, A lookup sequence.
Exim will not try to start a TLS session when delivering to any host that
matches this list. See chapter &<<CHAPTLS>>& for details of TLS.
Exim will not try to start a TLS session when delivering to any host that
matches this list. See chapter &<<CHAPTLS>>& for details of TLS.
.option hosts_verify_avoid_tls smtp "host list&!!" unset
.cindex "TLS" "avoiding for certain hosts"
Exim will not try to start a TLS session for a verify callout,
or when delivering in cutthrough mode,
to any host that matches this list.
.option hosts_verify_avoid_tls smtp "host list&!!" unset
.cindex "TLS" "avoiding for certain hosts"
Exim will not try to start a TLS session for a verify callout,
or when delivering in cutthrough mode,
to any host that matches this list.
unauthenticated. See also &%hosts_require_auth%&, and chapter
&<<CHAPSMTPAUTH>>& for details of authentication.
unauthenticated. See also &%hosts_require_auth%&, and chapter
&<<CHAPSMTPAUTH>>& for details of authentication.
.option hosts_try_prdr smtp "host list&!!" *
.cindex "PRDR" "enabling, optional in client"
This option provides a list of servers to which, provided they announce
PRDR support, Exim will attempt to negotiate PRDR
for multi-recipient messages.
The option can usually be left as default.
.option hosts_try_prdr smtp "host list&!!" *
.cindex "PRDR" "enabling, optional in client"
This option provides a list of servers to which, provided they announce
PRDR support, Exim will attempt to negotiate PRDR
for multi-recipient messages.
The option can usually be left as default.
&$domain$& in an expansion for the transport, because it is set only when there
is a single domain involved in a remote delivery.
&$domain$& in an expansion for the transport, because it is set only when there
is a single domain involved in a remote delivery.
It is expanded per-address and can depend on any of
&$address_data$&, &$domain_data$&, &$local_part_data$&,
&$host$&, &$host_address$& and &$host_port$&.
It is expanded per-address and can depend on any of
&$address_data$&, &$domain_data$&, &$local_part_data$&,
&$host$&, &$host_address$& and &$host_port$&.
deliveries into closed message stores. Exim also has support for running LMTP
over a pipe to a local process &-- see chapter &<<CHAPLMTP>>&.
deliveries into closed message stores. Exim also has support for running LMTP
over a pipe to a local process &-- see chapter &<<CHAPLMTP>>&.
changes to &"smtps"&, and the transport initiates TLS immediately after
connecting, as an outbound SSL-on-connect, instead of using STARTTLS to upgrade.
The Internet standards bodies strongly discourage use of this mode.
changes to &"smtps"&, and the transport initiates TLS immediately after
connecting, as an outbound SSL-on-connect, instead of using STARTTLS to upgrade.
The Internet standards bodies strongly discourage use of this mode.
each time they connect. In this situation the use of the IP address as part of
the retry key leads to undesirable behaviour. Setting this option false causes
Exim to use only the host name.
each time they connect. In this situation the use of the IP address as part of
the retry key leads to undesirable behaviour. Setting this option false causes
Exim to use only the host name.
.cindex "TLS" "server certificate verification"
.cindex "certificate" "verification of server"
This option gives a list of hosts for which, on encrypted connections,
.cindex "TLS" "server certificate verification"
.cindex "certificate" "verification of server"
This option gives a list of hosts for which, on encrypted connections,
.option tls_verify_cert_hostnames smtp "host list&!!" *
.cindex "TLS" "server certificate hostname verification"
.cindex "certificate" "verification of server"
.option tls_verify_cert_hostnames smtp "host list&!!" *
.cindex "TLS" "server certificate hostname verification"
.cindex "certificate" "verification of server"
limited to being the initial component of a 3-or-more component FQDN.
There is no equivalent checking on client certificates.
limited to being the initial component of a 3-or-more component FQDN.
There is no equivalent checking on client certificates.
.option tls_verify_certificates smtp string&!! system
.cindex "TLS" "server certificate verification"
.cindex "certificate" "verification of server"
.option tls_verify_certificates smtp string&!! system
.cindex "TLS" "server certificate verification"
.cindex "certificate" "verification of server"
&$host_address$& are set to the name and address of the server during the
expansion of this option. See chapter &<<CHAPTLS>>& for details of TLS.
&$host_address$& are set to the name and address of the server during the
expansion of this option. See chapter &<<CHAPTLS>>& for details of TLS.
if neither tls_verify_hosts nor tls_try_verify_hosts are set
(a single-colon empty list counts as being set)
and certificate verification fails the TLS connection is closed.
if neither tls_verify_hosts nor tls_try_verify_hosts are set
(a single-colon empty list counts as being set)
and certificate verification fails the TLS connection is closed.
legitimate reasons for this (host died, network died), but if it repeats a lot
for the same host, it indicates something odd.
legitimate reasons for this (host died, network died), but if it repeats a lot
for the same host, it indicates something odd.
.vitem &%lookup%&
A DNS lookup for a host failed.
Note that a &%dnslookup%& router will need to have matched
its &%fail_defer_domains%& option for this retry type to be usable.
Also note that a &%manualroute%& router will probably need
its &%host_find_failed%& option set to &%defer%&.
.vitem &%lookup%&
A DNS lookup for a host failed.
Note that a &%dnslookup%& router will need to have matched
its &%fail_defer_domains%& option for this retry type to be usable.
Also note that a &%manualroute%& router will probably need
its &%host_find_failed%& option set to &%defer%&.
the PLAIN authentication mechanism (RFC 2595) or the LOGIN mechanism, which is
not formally documented, but used by several MUAs. The seventh authenticator
supports Microsoft's &'Secure Password Authentication'& mechanism.
the PLAIN authentication mechanism (RFC 2595) or the LOGIN mechanism, which is
not formally documented, but used by several MUAs. The seventh authenticator
supports Microsoft's &'Secure Password Authentication'& mechanism.
The eighth is an Exim authenticator but not an SMTP one;
instead it can use information from a TLS negotiation.
The eighth is an Exim authenticator but not an SMTP one;
instead it can use information from a TLS negotiation.
The authenticators are configured using the same syntax as other drivers (see
section &<<SECTfordricon>>&). If no authenticators are required, no
The authenticators are configured using the same syntax as other drivers (see
section &<<SECTfordricon>>&). If no authenticators are required, no
.option client_set_id authenticators string&!! unset
When client authentication succeeds, this condition is expanded; the
.option client_set_id authenticators string&!! unset
When client authentication succeeds, this condition is expanded; the
.option server_service heimdal_gssapi string&!! "smtp"
This option specifies the service identifier used, in conjunction with
.option server_service heimdal_gssapi string&!! "smtp"
This option specifies the service identifier used, in conjunction with
. ////////////////////////////////////////////////////////////////////////////
. ////////////////////////////////////////////////////////////////////////////
. ////////////////////////////////////////////////////////////////////////////
. ////////////////////////////////////////////////////////////////////////////
.chapter "The tls authenticator" "CHAPtlsauth"
.scindex IIDtlsauth1 "&(tls)& authenticator"
.scindex IIDtlsauth2 "authenticators" "&(tls)&"
.chapter "The tls authenticator" "CHAPtlsauth"
.scindex IIDtlsauth1 "&(tls)& authenticator"
.scindex IIDtlsauth2 "authenticators" "&(tls)&"
If an authenticator of this type is configured it is
run before any SMTP-level communication is done,
and can authenticate the connection.
If an authenticator of this type is configured it is
run before any SMTP-level communication is done,
and can authenticate the connection.
Exim requests a certificate as part of the setup of the TLS session. The
contents of the certificate are verified by comparing it with a list of
expected certificates.
Exim requests a certificate as part of the setup of the TLS session. The
contents of the certificate are verified by comparing it with a list of
expected certificates.
an explicit file or,
depending on library version, a directory, identified by
&%tls_verify_certificates%&.
an explicit file or,
depending on library version, a directory, identified by
&%tls_verify_certificates%&.
proof expires. The downside is that it requires server support.
Unless Exim is built with the support disabled,
proof expires. The downside is that it requires server support.
Unless Exim is built with the support disabled,
If the &%tls_verify_certificates%& option is set on the &(smtp)& transport, it
specifies a collection of expected server certificates.
If the &%tls_verify_certificates%& option is set on the &(smtp)& transport, it
specifies a collection of expected server certificates.
must name a file or,
for OpenSSL only (not GnuTLS), a directory.
The client verifies the server's certificate
must name a file or,
for OpenSSL only (not GnuTLS), a directory.
The client verifies the server's certificate
for TLS Extensions. This holds true for OpenSSL 1.0.0+ and 0.9.8+ with
enable-tlsext in EXTRACONFIGURE. If you invoke &(openssl s_client -h)& and
see &`-servername`& in the output, then OpenSSL has support.
for TLS Extensions. This holds true for OpenSSL 1.0.0+ and 0.9.8+ with
enable-tlsext in EXTRACONFIGURE. If you invoke &(openssl s_client -h)& and
see &`-servername`& in the output, then OpenSSL has support.
-The ACL test specfied by &%acl_smtp_data_prdr%& happens after a message
-has been recieved, and is executed once for each recipient of the message
+The ACL test specified by &%acl_smtp_data_prdr%& happens after a message
+has been received, and is executed once for each recipient of the message
The &%acl_smtp_data%& will still be called after this ACL and
can reject the message overall, even if this ACL has accepted it
for some or all recipients.
The &%acl_smtp_data%& will still be called after this ACL and
can reject the message overall, even if this ACL has accepted it
for some or all recipients.
for this can be disabled when the MAIL-time $smtp_command included
"PRDR". Any required difference in behaviour of the main DATA-time
ACL should however depend on the PRDR-time ACL having run, as Exim
for this can be disabled when the MAIL-time $smtp_command included
"PRDR". Any required difference in behaviour of the main DATA-time
ACL should however depend on the PRDR-time ACL having run, as Exim
The ACL for the SMTP QUIT command is anomalous, in that the outcome of the ACL
does not affect the response code to QUIT, which is always 221. Thus, the ACL
does not in fact control any access.
The ACL for the SMTP QUIT command is anomalous, in that the outcome of the ACL
does not affect the response code to QUIT, which is always 221. Thus, the ACL
does not in fact control any access.
For this reason, it may only accept
or warn as its final result.
For this reason, it may only accept
or warn as its final result.
This ACL can be used for tasks such as custom logging at the end of an SMTP
session. For example, you can use ACL variables in other ACLs to count
This ACL can be used for tasks such as custom logging at the end of an SMTP
session. For example, you can use ACL variables in other ACLs to count
This option requests delivery be attempted while the item is being received.
The option is usable in the RCPT ACL.
This option requests delivery be attempted while the item is being received.
The option is usable in the RCPT ACL.
and only one transport, interface, destination host and port combination
is used for all recipients of the message,
and only one transport, interface, destination host and port combination
is used for all recipients of the message,
then the delivery connection is made while the receiving connection is open
and data is copied from one to the other.
then the delivery connection is made while the receiving connection is open
and data is copied from one to the other.
for a mail will be quietly ignored.
If a recipient-verify callout connection is subsequently
requested in the same ACL it is held open and used for
for a mail will be quietly ignored.
If a recipient-verify callout connection is subsequently
requested in the same ACL it is held open and used for
otherwise one is made after the initial RCPT ACL completes.
Note that routers are used in verify mode,
otherwise one is made after the initial RCPT ACL completes.
Note that routers are used in verify mode,
Cutthrough delivery is not supported via transport-filters or when DKIM signing
of outgoing messages is done, because it sends data to the ultimate destination
before the entire message has been received from the source.
Cutthrough delivery is not supported via transport-filters or when DKIM signing
of outgoing messages is done, because it sends data to the ultimate destination
before the entire message has been received from the source.
Should the ultimate destination system positively accept or reject the mail,
a corresponding indication is given to the source system and nothing is queued.
Should the ultimate destination system positively accept or reject the mail,
a corresponding indication is given to the source system and nothing is queued.
one of its aliases, does, when it is itself looked up in the DNS, yield the
original IP address.
one of its aliases, does, when it is itself looked up in the DNS, yield the
original IP address.
There is one possible option, &`defer_ok`&. If this is present and a
DNS operation returns a temporary error, the verify condition succeeds.
There is one possible option, &`defer_ok`&. If this is present and a
DNS operation returns a temporary error, the verify condition succeeds.
If this condition is used for a locally generated message (that is, when there
is no client host involved), it always succeeds.
If this condition is used for a locally generated message (that is, when there
is no client host involved), it always succeeds.
specialized interfaces for &"daemon"& type virus scanners, which are resident
in memory and thus are much faster.
specialized interfaces for &"daemon"& type virus scanners, which are resident
in memory and thus are much faster.
A timeout of 2 minutes is applied to a scanner call (by default);
if it expires then a defer action is taken.
A timeout of 2 minutes is applied to a scanner call (by default);
if it expires then a defer action is taken.
.vitem &%avast%&
.cindex "virus scanners" "avast"
This is the scanner daemon of Avast. It has been tested with Avast Core
.vitem &%avast%&
.cindex "virus scanners" "avast"
This is the scanner daemon of Avast. It has been tested with Avast Core
You can get a trial version at &url(http://www.avast.com) or for Linux
at &url(http://www.avast.com/linux-server-antivirus).
This scanner type takes one option,
You can get a trial version at &url(http://www.avast.com) or for Linux
at &url(http://www.avast.com/linux-server-antivirus).
This scanner type takes one option,
a commandline to send (may include a single %s which will be replaced with
the path to the mail file to be scanned),
an RE to trigger on from the returned data,
a commandline to send (may include a single %s which will be replaced with
the path to the mail file to be scanned),
an RE to trigger on from the returned data,
A regular expression, in which case the message is scanned for viruses. The
condition succeeds if a virus is found and its name matches the regular
expression. This allows you to take special actions on certain types of virus.
A regular expression, in which case the message is scanned for viruses. The
condition succeeds if a virus is found and its name matches the regular
expression. This allows you to take special actions on certain types of virus.
Note that &"/"& characters in the RE must be doubled due to the list-processing,
unless the separator is changed (in the usual way).
Note that &"/"& characters in the RE must be doubled due to the list-processing,
unless the separator is changed (in the usual way).
.endlist
You can append a &`defer_ok`& element to the &%malware%& argument list to accept
messages even if there is a problem with the virus scanner.
Otherwise, such a problem causes the ACL to defer.
.endlist
You can append a &`defer_ok`& element to the &%malware%& argument list to accept
messages even if there is a problem with the virus scanner.
Otherwise, such a problem causes the ACL to defer.
You can append a &`tmo=<val>`& element to the &%malware%& argument list to
specify a non-default timeout. The default is two minutes.
For example:
You can append a &`tmo=<val>`& element to the &%malware%& argument list to
specify a non-default timeout. The default is two minutes.
For example:
.vindex "&$malware_name$&"
When a virus is found, the condition sets up an expansion variable called
.vindex "&$malware_name$&"
When a virus is found, the condition sets up an expansion variable called
.cindex "Rspamd"
The &%spam%& ACL condition calls SpamAssassin's &%spamd%& daemon to get a spam
score and a report for the message.
.cindex "Rspamd"
The &%spam%& ACL condition calls SpamAssassin's &%spamd%& daemon to get a spam
score and a report for the message.
Support is also provided for Rspamd.
For more information about installation and configuration of SpamAssassin or
Rspamd refer to their respective websites at
&url(http://spamassassin.apache.org) and &url(http://www.rspamd.com)
Support is also provided for Rspamd.
For more information about installation and configuration of SpamAssassin or
Rspamd refer to their respective websites at
&url(http://spamassassin.apache.org) and &url(http://www.rspamd.com)
To use Rspamd (which by default listens on all local addresses
on TCP port 11333)
you should add &%variant=rspamd%& after the address/port pair, for example:
.code
spamd_address = 127.0.0.1 11333 variant=rspamd
.endd
To use Rspamd (which by default listens on all local addresses
on TCP port 11333)
you should add &%variant=rspamd%& after the address/port pair, for example:
.code
spamd_address = 127.0.0.1 11333 variant=rspamd
.endd
As of version 2.60, &%SpamAssassin%& also supports communication over UNIX
sockets. If you want to us these, supply &%spamd_address%& with an absolute
As of version 2.60, &%SpamAssassin%& also supports communication over UNIX
sockets. If you want to us these, supply &%spamd_address%& with an absolute
Unix and TCP socket specifications may be mixed in any order.
Each element of the list is a list itself, space-separated by default
and changeable in the usual way.
Unix and TCP socket specifications may be mixed in any order.
Each element of the list is a list itself, space-separated by default
and changeable in the usual way.
The &`pri`& option specifies a priority for the server within the list,
higher values being tried first.
The &`pri`& option specifies a priority for the server within the list,
higher values being tried first.
characters, may be omitted and will be taken as zero.
Timeout specifications for the &`retry`& and &`tmo`& options
characters, may be omitted and will be taken as zero.
Timeout specifications for the &`retry`& and &`tmo`& options
The &`retry`& option specifies a time after which a single retry for
a failed connect is made.
The default is to not retry.
The &`retry`& option specifies a time after which a single retry for
a failed connect is made.
The default is to not retry.
The &%spamd_address%& variable is expanded before use if it starts with
a dollar sign. In this case, the expansion may return a string that is
The &%spamd_address%& variable is expanded before use if it starts with
a dollar sign. In this case, the expansion may return a string that is
relevant if you have set up multiple SpamAssassin profiles. If you do not want
to scan using a specific profile, but rather use the SpamAssassin system-wide
default profile, you can scan for an unknown name, or simply use &"nobody"&.
relevant if you have set up multiple SpamAssassin profiles. If you do not want
to scan using a specific profile, but rather use the SpamAssassin system-wide
default profile, you can scan for an unknown name, or simply use &"nobody"&.
The name allows you to use per-domain or per-user antispam profiles in
principle, but this is not straightforward in practice, because a message may
The name allows you to use per-domain or per-user antispam profiles in
principle, but this is not straightforward in practice, because a message may
&%spam%& condition has to be called from a DATA-time ACL in order to be able to
read the contents of the message, the variables &$local_part$& and &$domain$&
are not set.
&%spam%& condition has to be called from a DATA-time ACL in order to be able to
read the contents of the message, the variables &$local_part$& and &$domain$&
are not set.
The right-hand side of the &%spam%& condition is expanded before being used, so
you can put lookups or conditions there. When the right-hand side evaluates to
The right-hand side of the &%spam%& condition is expanded before being used, so
you can put lookups or conditions there. When the right-hand side evaluates to
.cindex "spam scanning" "returned variables"
When the &%spam%& condition is run, it sets up a number of expansion
variables.
.cindex "spam scanning" "returned variables"
When the &%spam%& condition is run, it sets up a number of expansion
variables.
A string consisting of a number of &"+"& or &"-"& characters, representing the
integer part of the spam score value. A spam score of 4.4 would have a
&$spam_bar$& value of &"++++"&. This is useful for inclusion in warning
A string consisting of a number of &"+"& or &"-"& characters, representing the
integer part of the spam score value. A spam score of 4.4 would have a
&$spam_bar$& value of &"++++"&. This is useful for inclusion in warning
.vitem &$spam_report$&
A multiline text table, containing the full SpamAssassin report for the
message. Useful for inclusion in headers or reject messages.
.vitem &$spam_report$&
A multiline text table, containing the full SpamAssassin report for the
message. Useful for inclusion in headers or reject messages.
.vitem &$spam_action$&
For SpamAssassin either 'reject' or 'no action' depending on the
spam score versus threshold.
For Rspamd, the recommended action.
.vitem &$spam_action$&
For SpamAssassin either 'reject' or 'no action' depending on the
spam score versus threshold.
For Rspamd, the recommended action.
proposed filename for an attachment, if one was found in either the
&'Content-Type:'& or &'Content-Disposition:'& headers. The filename will be
RFC2047
proposed filename for an attachment, if one was found in either the
&'Content-Type:'& or &'Content-Disposition:'& headers. The filename will be
RFC2047
decoded, but no additional sanity checks are done.
If no filename was
found, this variable contains the empty string.
decoded, but no additional sanity checks are done.
If no filename was
found, this variable contains the empty string.
The third item is used to introduce any text from pipe transports that is to be
returned to the sender. It is omitted if there is no such text.
.next
The third item is used to introduce any text from pipe transports that is to be
returned to the sender. It is omitted if there is no such text.
.next
The fourth, fifth and sixth items will be ignored and may be empty.
The fields exist for back-compatibility
The fourth, fifth and sixth items will be ignored and may be empty.
The fields exist for back-compatibility
&` incoming_port `& remote port on <= lines
&`*lost_incoming_connection `& as it says (includes timeouts)
&` outgoing_port `& add remote port to => lines
&` incoming_port `& remote port on <= lines
&`*lost_incoming_connection `& as it says (includes timeouts)
&` outgoing_port `& add remote port to => lines
&`*size_reject `& rejection because too big
&`*skip_delivery `& delivery skipped in a queue run
&`*smtp_confirmation `& SMTP confirmation on => lines
&`*size_reject `& rejection because too big
&`*skip_delivery `& delivery skipped in a queue run
&`*smtp_confirmation `& SMTP confirmation on => lines
&` smtp_incomplete_transaction`& incomplete SMTP transactions
&` smtp_mailauth `& AUTH argument to MAIL commands
&` smtp_no_mail `& session with no MAIL commands
&` smtp_protocol_error `& SMTP protocol errors
&` smtp_syntax_error `& SMTP syntax errors
&` subject `& contents of &'Subject:'& on <= lines
&` smtp_incomplete_transaction`& incomplete SMTP transactions
&` smtp_mailauth `& AUTH argument to MAIL commands
&` smtp_no_mail `& session with no MAIL commands
&` smtp_protocol_error `& SMTP protocol errors
&` smtp_syntax_error `& SMTP syntax errors
&` subject `& contents of &'Subject:'& on <= lines
&`*tls_cipher `& TLS cipher suite on <= and => lines
&` tls_peerdn `& TLS peer DN on <= and => lines
&` tls_sni `& TLS SNI on <= lines
&`*tls_cipher `& TLS cipher suite on <= and => lines
&` tls_peerdn `& TLS peer DN on <= and => lines
&` tls_sni `& TLS SNI on <= lines
followed by a colon and the port number. The local interface and port are also
added to other SMTP log lines, for example &"SMTP connection from"& and to
rejection lines
followed by a colon and the port number. The local interface and port are also
added to other SMTP log lines, for example &"SMTP connection from"& and to
rejection lines
established or closed, unless the connection is from a host that matches
&%hosts_connection_nolog%&. (In contrast, &%lost_incoming_connection%& applies
only when the closure is unexpected.) This applies to connections from local
established or closed, unless the connection is from a host that matches
&%hosts_connection_nolog%&. (In contrast, &%lost_incoming_connection%& applies
only when the closure is unexpected.) This applies to connections from local
shows that the client issued QUIT straight after EHLO. If there were fewer
than 20 commands, they are all listed. If there were more than 20 commands,
the last 20 are listed, preceded by &"..."&. However, with the default
shows that the client issued QUIT straight after EHLO. If there were fewer
than 20 commands, they are all listed. If there were more than 20 commands,
the last 20 are listed, preceded by &"..."&. However, with the default
have been aborted before 20 non-mail commands are processed.
.next
&%smtp_mailauth%&: A third subfield with the authenticated sender,
have been aborted before 20 non-mail commands are processed.
.next
&%smtp_mailauth%&: A third subfield with the authenticated sender,
Administrators who use embedded Perl are advised to explore how Perl's
taint checking might apply to their usage.
.next
Administrators who use embedded Perl are advised to explore how Perl's
taint checking might apply to their usage.
.next
administrators are well advised to view its use with suspicion, in case (for
instance) it allows a local-part to contain embedded Exim directives.
.next
administrators are well advised to view its use with suspicion, in case (for
instance) it allows a local-part to contain embedded Exim directives.
.next
&%acl_smtp_dkim%& ACL. By default, this ACL is called once for each
syntactically(!) correct signature in the incoming message.
A missing ACL definition defaults to accept.
&%acl_smtp_dkim%& ACL. By default, this ACL is called once for each
syntactically(!) correct signature in the incoming message.
A missing ACL definition defaults to accept.
If a cutthrough delivery was in progress for the message it is
summarily dropped (having wasted the transmission effort).
If a cutthrough delivery was in progress for the message it is
summarily dropped (having wasted the transmission effort).
"fail" or "invalid". One of
.ilist
&%pubkey_unavailable%& (when &%$dkim_verify_status%&="invalid"): The public
"fail" or "invalid". One of
.ilist
&%pubkey_unavailable%& (when &%$dkim_verify_status%&="invalid"): The public
git://git.exim.org / users / heiko / exim.git / blobdiff