File manager

File manager - Edit - /usr/local/cpanel/share/doc/exim/exim-html-4.76/doc/html/spec_html/ch14.html

Back
<!DOCTYPE html PUBLIC "XSLT-compat"> <html lang="en-GB"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <link rel="stylesheet" type="text/css" href="../../../../static/css/common.css"> <meta name="author" content="The Exim Project. <http://www.exim.org/>"> <meta name="copyright" content="Copyright ©1995-2012 The Exim Project. All rights reserved"> <meta name="description" content="Exim is a message transfer agent (MTA) developed at the University of Cambridge for use on Unix systems connected to the Internet."> <meta name="keywords" content="exim,smtp,mta,email"> <meta name="robots" content="noodp,noydir,index,follow"> <meta name="viewport" content="width=device-width"> <title>14. Main configuration</title> <link rel="stylesheet" type="text/css" href="../../../../static/doc/chapter.css"> <link rel="canonical" href="http://www.exim.org/exim-html-current/doc/html/spec_html/ch14.html"> </head> <body class="no-js"> <script type="text/javascript">document.body.className=(' '+document.body.className+' ').replace('no-js','with-js');</script><h1 id="header"><a href="../../../..">Exim Internet Mailer</a></h1> <div id="outer"> <ul id="nav_flow" class="nav"> <li><a href="../../../../index.html">Home</a></li> <li><a href="../../../../mirrors.html">Download</a></li> <li><a href="../../../../docs.html">Documentation</a></li> <li><a href="../../../../maillist.html">Mailing Lists</a></li> <li><a href="http://wiki.exim.org/">Wiki</a></li> <li><a href="http://www.exim.org/bugzilla/">Bugs</a></li> <li><a href="../../../../credits.html">Credits</a></li> <li class="img"><a href="https://plus.google.com/101257968735428844827/?prsrc=3" title="Google+"><img src="../../../../i/gplus-32.png" width="16" height="16" alt="G+"></a></li> <li class="search"><form action="https://encrypted.google.com/search" method="get"> <span class="search_field_container"><input type="search" name="q" placeholder="Search Docs" class="search_field"></span><input type="hidden" name="hl" value="en"><input type="hidden" name="ie" value="UTF-8"><input type="hidden" name="as_qdr" value="all"><input type="hidden" name="q" value="site:www.exim.org"><input type="hidden" name="q" value="inurl:exim-html-current"> </form></li> </ul> <div id="inner"><div id="content"> <a class="previous_page" href="ch13.html"><-previous</a><a class="next_page" href="ch15.html">next-></a><div id="chapter" class="chapter"> <h2 id="CHAPmainconfig" class=""><a href="index.html">Chapter 14 - Main configuration</a></h2> <p> The first part of the run time configuration file contains three types of item: </p> <ul> <li> <p> Macro definitions: These lines start with an upper case letter. See section <a href="ch06.html#SECTmacrodefs" title="6. The Exim run time configuration file">6.4</a> for details of macro processing. </p> </li> <li> <p> Named list definitions: These lines start with one of the words “domainlist”, “hostlist”, “addresslist”, or “localpartlist”. Their use is described in section <a href="ch10.html#SECTnamedlists" title="10. Domain, host, address, and local part lists">10.5</a>. </p> </li> <li> <p> Main configuration settings: Each setting occupies one line of the file (with possible continuations). If any setting is preceded by the word “hide”, the <span class="docbook_option">-bP</span> command line option displays its value to admin users only. See section <a href="ch06.html#SECTcos" title="6. The Exim run time configuration file">6.10</a> for a description of the syntax of these option settings. </p> </li> </ul> <p> This chapter specifies all the main configuration options, along with their types and default values. For ease of finding a particular option, they appear in alphabetical order in section <a href="ch14.html#SECTalomo" title="14. Main configuration">14.23</a> below. However, because there are now so many options, they are first listed briefly in functional groups, as an aid to finding the name of the option you are looking for. Some options are listed in more than one group. </p> <div class="section"> <h3 id="SECID96" class="">1. Miscellaneous</h3> <table> <tr> <td><span class="docbook_option">bi_command</span></td> <td>to run for <span class="docbook_option">-bi</span> command line option</td> </tr> <tr> <td><span class="docbook_option">disable_ipv6</span></td> <td>do no IPv6 processing</td> </tr> <tr> <td><span class="docbook_option">keep_malformed</span></td> <td>for broken files – should not happen</td> </tr> <tr> <td><span class="docbook_option">localhost_number</span></td> <td>for unique message ids in clusters</td> </tr> <tr> <td><span class="docbook_option">message_body_newlines</span></td> <td>retain newlines in $message_body</td> </tr> <tr> <td><span class="docbook_option">message_body_visible</span></td> <td>how much to show in $message_body</td> </tr> <tr> <td><span class="docbook_option">mua_wrapper</span></td> <td>run in “MUA wrapper” mode</td> </tr> <tr> <td><span class="docbook_option">print_topbitchars</span></td> <td>top-bit characters are printing</td> </tr> <tr> <td><span class="docbook_option">timezone</span></td> <td>force time zone</td> </tr> </table> </div> <div class="section"> <h3 id="SECID97" class="">2. Exim parameters</h3> <table> <tr> <td><span class="docbook_option">exim_group</span></td> <td>override compiled-in value</td> </tr> <tr> <td><span class="docbook_option">exim_path</span></td> <td>override compiled-in value</td> </tr> <tr> <td><span class="docbook_option">exim_user</span></td> <td>override compiled-in value</td> </tr> <tr> <td><span class="docbook_option">primary_hostname</span></td> <td>default from <span class="docbook_function">uname()</span> </td> </tr> <tr> <td><span class="docbook_option">split_spool_directory</span></td> <td>use multiple directories</td> </tr> <tr> <td><span class="docbook_option">spool_directory</span></td> <td>override compiled-in value</td> </tr> </table> </div> <div class="section"> <h3 id="SECID98" class="">3. Privilege controls</h3> <table> <tr> <td><span class="docbook_option">admin_groups</span></td> <td>groups that are Exim admin users</td> </tr> <tr> <td><span class="docbook_option">deliver_drop_privilege</span></td> <td>drop root for delivery processes</td> </tr> <tr> <td><span class="docbook_option">local_from_check</span></td> <td>insert <span class="docbook_emphasis">Sender:</span> if necessary</td> </tr> <tr> <td><span class="docbook_option">local_from_prefix</span></td> <td>for testing <span class="docbook_emphasis">From:</span> for local sender</td> </tr> <tr> <td><span class="docbook_option">local_from_suffix</span></td> <td>for testing <span class="docbook_emphasis">From:</span> for local sender</td> </tr> <tr> <td><span class="docbook_option">local_sender_retain</span></td> <td>keep <span class="docbook_emphasis">Sender:</span> from untrusted user</td> </tr> <tr> <td><span class="docbook_option">never_users</span></td> <td>do not run deliveries as these</td> </tr> <tr> <td><span class="docbook_option">prod_requires_admin</span></td> <td>forced delivery requires admin user</td> </tr> <tr> <td><span class="docbook_option">queue_list_requires_admin</span></td> <td>queue listing requires admin user</td> </tr> <tr> <td><span class="docbook_option">trusted_groups</span></td> <td>groups that are trusted</td> </tr> <tr> <td><span class="docbook_option">trusted_users</span></td> <td>users that are trusted</td> </tr> </table> </div> <div class="section"> <h3 id="SECID99" class="">4. Logging</h3> <table> <tr> <td><span class="docbook_option">hosts_connection_nolog</span></td> <td>exemption from connect logging</td> </tr> <tr> <td><span class="docbook_option">log_file_path</span></td> <td>override compiled-in value</td> </tr> <tr> <td><span class="docbook_option">log_selector</span></td> <td>set/unset optional logging</td> </tr> <tr> <td><span class="docbook_option">log_timezone</span></td> <td>add timezone to log lines</td> </tr> <tr> <td><span class="docbook_option">message_logs</span></td> <td>create per-message logs</td> </tr> <tr> <td><span class="docbook_option">preserve_message_logs</span></td> <td>after message completion</td> </tr> <tr> <td><span class="docbook_option">process_log_path</span></td> <td>for SIGUSR1 and <span class="docbook_emphasis">exiwhat</span> </td> </tr> <tr> <td><span class="docbook_option">syslog_duplication</span></td> <td>controls duplicate log lines on syslog</td> </tr> <tr> <td><span class="docbook_option">syslog_facility</span></td> <td>set syslog “facility” field</td> </tr> <tr> <td><span class="docbook_option">syslog_processname</span></td> <td>set syslog “ident” field</td> </tr> <tr> <td><span class="docbook_option">syslog_timestamp</span></td> <td>timestamp syslog lines</td> </tr> <tr> <td><span class="docbook_option">write_rejectlog</span></td> <td>control use of message log</td> </tr> </table> </div> <div class="section"> <h3 id="SECID100" class="">5. Frozen messages</h3> <table> <tr> <td><span class="docbook_option">auto_thaw</span></td> <td>sets time for retrying frozen messages</td> </tr> <tr> <td><span class="docbook_option">freeze_tell</span></td> <td>send message when freezing</td> </tr> <tr> <td><span class="docbook_option">move_frozen_messages</span></td> <td>to another directory</td> </tr> <tr> <td><span class="docbook_option">timeout_frozen_after</span></td> <td>keep frozen messages only so long</td> </tr> </table> </div> <div class="section"> <h3 id="SECID101" class="">6. Data lookups</h3> <table> <tr> <td><span class="docbook_option">ibase_servers</span></td> <td>InterBase servers</td> </tr> <tr> <td><span class="docbook_option">ldap_ca_cert_dir</span></td> <td>dir of CA certs to verify LDAP server’s</td> </tr> <tr> <td><span class="docbook_option">ldap_ca_cert_file</span></td> <td>file of CA certs to verify LDAP server’s</td> </tr> <tr> <td><span class="docbook_option">ldap_cert_file</span></td> <td>client cert file for LDAP</td> </tr> <tr> <td><span class="docbook_option">ldap_cert_key</span></td> <td>client key file for LDAP</td> </tr> <tr> <td><span class="docbook_option">ldap_cipher_suite</span></td> <td>TLS negotiation preference control</td> </tr> <tr> <td><span class="docbook_option">ldap_default_servers</span></td> <td>used if no server in query</td> </tr> <tr> <td><span class="docbook_option">ldap_require_cert</span></td> <td>action to take without LDAP server cert</td> </tr> <tr> <td><span class="docbook_option">ldap_start_tls</span></td> <td>require TLS within LDAP</td> </tr> <tr> <td><span class="docbook_option">ldap_version</span></td> <td>set protocol version</td> </tr> <tr> <td><span class="docbook_option">lookup_open_max</span></td> <td>lookup files held open</td> </tr> <tr> <td><span class="docbook_option">mysql_servers</span></td> <td>default MySQL servers</td> </tr> <tr> <td><span class="docbook_option">oracle_servers</span></td> <td>Oracle servers</td> </tr> <tr> <td><span class="docbook_option">pgsql_servers</span></td> <td>default PostgreSQL servers</td> </tr> <tr> <td><span class="docbook_option">sqlite_lock_timeout</span></td> <td>as it says</td> </tr> </table> </div> <div class="section"> <h3 id="SECID102" class="">7. Message ids</h3> <table> <tr> <td><span class="docbook_option">message_id_header_domain</span></td> <td>used to build <span class="docbook_emphasis">Message-ID:</span> header</td> </tr> <tr> <td><span class="docbook_option">message_id_header_text</span></td> <td>ditto</td> </tr> </table> </div> <div class="section"> <h3 id="SECID103" class="">8. Embedded Perl Startup</h3> <table> <tr> <td><span class="docbook_option">perl_at_start</span></td> <td>always start the interpreter</td> </tr> <tr> <td><span class="docbook_option">perl_startup</span></td> <td>code to obey when starting Perl</td> </tr> </table> </div> <div class="section"> <h3 id="SECID104" class="">9. Daemon</h3> <table> <tr> <td><span class="docbook_option">daemon_smtp_ports</span></td> <td>default ports</td> </tr> <tr> <td><span class="docbook_option">daemon_startup_retries</span></td> <td>number of times to retry</td> </tr> <tr> <td><span class="docbook_option">daemon_startup_sleep</span></td> <td>time to sleep between tries</td> </tr> <tr> <td><span class="docbook_option">extra_local_interfaces</span></td> <td>not necessarily listened on</td> </tr> <tr> <td><span class="docbook_option">local_interfaces</span></td> <td>on which to listen, with optional ports</td> </tr> <tr> <td><span class="docbook_option">pid_file_path</span></td> <td>override compiled-in value</td> </tr> <tr> <td><span class="docbook_option">queue_run_max</span></td> <td>maximum simultaneous queue runners</td> </tr> </table> </div> <div class="section"> <h3 id="SECID105" class="">10. Resource control</h3> <table> <tr> <td><span class="docbook_option">check_log_inodes</span></td> <td>before accepting a message</td> </tr> <tr> <td><span class="docbook_option">check_log_space</span></td> <td>before accepting a message</td> </tr> <tr> <td><span class="docbook_option">check_spool_inodes</span></td> <td>before accepting a message</td> </tr> <tr> <td><span class="docbook_option">check_spool_space</span></td> <td>before accepting a message</td> </tr> <tr> <td><span class="docbook_option">deliver_queue_load_max</span></td> <td>no queue deliveries if load high</td> </tr> <tr> <td><span class="docbook_option">queue_only_load</span></td> <td>queue incoming if load high</td> </tr> <tr> <td><span class="docbook_option">queue_only_load_latch</span></td> <td>don’t re-evaluate load for each message</td> </tr> <tr> <td><span class="docbook_option">queue_run_max</span></td> <td>maximum simultaneous queue runners</td> </tr> <tr> <td><span class="docbook_option">remote_max_parallel</span></td> <td>parallel SMTP delivery per message</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_max</span></td> <td>simultaneous incoming connections</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_max_nonmail</span></td> <td>non-mail commands</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_max_nonmail_hosts</span></td> <td>hosts to which the limit applies</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_max_per_connection</span></td> <td>messages per connection</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_max_per_host</span></td> <td>connections from one host</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_queue</span></td> <td>queue mail if more connections</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_queue_per_connection</span></td> <td>queue if more messages per connection</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_reserve</span></td> <td>only reserve hosts if more connections</td> </tr> <tr> <td><span class="docbook_option">smtp_check_spool_space</span></td> <td>from SIZE on MAIL command</td> </tr> <tr> <td><span class="docbook_option">smtp_connect_backlog</span></td> <td>passed to TCP/IP stack</td> </tr> <tr> <td><span class="docbook_option">smtp_load_reserve</span></td> <td>SMTP from reserved hosts if load high</td> </tr> <tr> <td><span class="docbook_option">smtp_reserve_hosts</span></td> <td>these are the reserve hosts</td> </tr> </table> </div> <div class="section"> <h3 id="SECID106" class="">11. Policy controls</h3> <table> <tr> <td><span class="docbook_option">acl_not_smtp</span></td> <td>ACL for non-SMTP messages</td> </tr> <tr> <td><span class="docbook_option">acl_not_smtp_mime</span></td> <td>ACL for non-SMTP MIME parts</td> </tr> <tr> <td><span class="docbook_option">acl_not_smtp_start</span></td> <td>ACL for start of non-SMTP message</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_auth</span></td> <td>ACL for AUTH</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_connect</span></td> <td>ACL for connection</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_data</span></td> <td>ACL for DATA</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_dkim</span></td> <td>ACL for DKIM verification</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_etrn</span></td> <td>ACL for ETRN</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_expn</span></td> <td>ACL for EXPN</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_helo</span></td> <td>ACL for EHLO or HELO</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_mail</span></td> <td>ACL for MAIL</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_mailauth</span></td> <td>ACL for AUTH on MAIL command</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_mime</span></td> <td>ACL for MIME parts</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_predata</span></td> <td>ACL for start of data</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_quit</span></td> <td>ACL for QUIT</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_rcpt</span></td> <td>ACL for RCPT</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_starttls</span></td> <td>ACL for STARTTLS</td> </tr> <tr> <td><span class="docbook_option">acl_smtp_vrfy</span></td> <td>ACL for VRFY</td> </tr> <tr> <td><span class="docbook_option">av_scanner</span></td> <td>specify virus scanner</td> </tr> <tr> <td><span class="docbook_option">check_rfc2047_length</span></td> <td>check length of RFC 2047 “encoded words”</td> </tr> <tr> <td><span class="docbook_option">dns_csa_search_limit</span></td> <td>control CSA parent search depth</td> </tr> <tr> <td><span class="docbook_option">dns_csa_use_reverse</span></td> <td>en/disable CSA IP reverse search</td> </tr> <tr> <td><span class="docbook_option">header_maxsize</span></td> <td>total size of message header</td> </tr> <tr> <td><span class="docbook_option">header_line_maxsize</span></td> <td>individual header line limit</td> </tr> <tr> <td><span class="docbook_option">helo_accept_junk_hosts</span></td> <td>allow syntactic junk from these hosts</td> </tr> <tr> <td><span class="docbook_option">helo_allow_chars</span></td> <td>allow illegal chars in HELO names</td> </tr> <tr> <td><span class="docbook_option">helo_lookup_domains</span></td> <td>lookup hostname for these HELO names</td> </tr> <tr> <td><span class="docbook_option">helo_try_verify_hosts</span></td> <td>HELO soft-checked for these hosts</td> </tr> <tr> <td><span class="docbook_option">helo_verify_hosts</span></td> <td>HELO hard-checked for these hosts</td> </tr> <tr> <td><span class="docbook_option">host_lookup</span></td> <td>host name looked up for these hosts</td> </tr> <tr> <td><span class="docbook_option">host_lookup_order</span></td> <td>order of DNS and local name lookups</td> </tr> <tr> <td><span class="docbook_option">host_reject_connection</span></td> <td>reject connection from these hosts</td> </tr> <tr> <td><span class="docbook_option">hosts_treat_as_local</span></td> <td>useful in some cluster configurations</td> </tr> <tr> <td><span class="docbook_option">local_scan_timeout</span></td> <td>timeout for <span class="docbook_function">local_scan()</span> </td> </tr> <tr> <td><span class="docbook_option">message_size_limit</span></td> <td>for all messages</td> </tr> <tr> <td><span class="docbook_option">percent_hack_domains</span></td> <td>recognize %-hack for these domains</td> </tr> <tr> <td><span class="docbook_option">spamd_address</span></td> <td>set interface to SpamAssassin</td> </tr> <tr> <td><span class="docbook_option">strict_acl_vars</span></td> <td>object to unset ACL variables</td> </tr> </table> </div> <div class="section"> <h3 id="SECID107" class="">12. Callout cache</h3> <table> <tr> <td><span class="docbook_option">callout_domain_negative_expire</span></td> <td>timeout for negative domain cache item</td> </tr> <tr> <td><span class="docbook_option">callout_domain_positive_expire</span></td> <td>timeout for positive domain cache item</td> </tr> <tr> <td><span class="docbook_option">callout_negative_expire</span></td> <td>timeout for negative address cache item</td> </tr> <tr> <td><span class="docbook_option">callout_positive_expire</span></td> <td>timeout for positive address cache item</td> </tr> <tr> <td><span class="docbook_option">callout_random_local_part</span></td> <td>string to use for “random” testing</td> </tr> </table> </div> <div class="section"> <h3 id="SECID108" class="">13. TLS</h3> <table> <tr> <td><span class="docbook_option">gnutls_compat_mode</span></td> <td>use GnuTLS compatibility mode</td> </tr> <tr> <td><span class="docbook_option">openssl_options</span></td> <td>adjust OpenSSL compatibility options</td> </tr> <tr> <td><span class="docbook_option">tls_advertise_hosts</span></td> <td>advertise TLS to these hosts</td> </tr> <tr> <td><span class="docbook_option">tls_certificate</span></td> <td>location of server certificate</td> </tr> <tr> <td><span class="docbook_option">tls_crl</span></td> <td>certificate revocation list</td> </tr> <tr> <td><span class="docbook_option">tls_dh_max_bits</span></td> <td>clamp D-H bit count suggestion</td> </tr> <tr> <td><span class="docbook_option">tls_dhparam</span></td> <td>DH parameters for server</td> </tr> <tr> <td><span class="docbook_option">tls_on_connect_ports</span></td> <td>specify SSMTP (SMTPS) ports</td> </tr> <tr> <td><span class="docbook_option">tls_privatekey</span></td> <td>location of server private key</td> </tr> <tr> <td><span class="docbook_option">tls_remember_esmtp</span></td> <td>don’t reset after starting TLS</td> </tr> <tr> <td><span class="docbook_option">tls_require_ciphers</span></td> <td>specify acceptable ciphers</td> </tr> <tr> <td><span class="docbook_option">tls_try_verify_hosts</span></td> <td>try to verify client certificate</td> </tr> <tr> <td><span class="docbook_option">tls_verify_certificates</span></td> <td>expected client certificates</td> </tr> <tr> <td><span class="docbook_option">tls_verify_hosts</span></td> <td>insist on client certificate verify</td> </tr> </table> </div> <div class="section"> <h3 id="SECID109" class="">14. Local user handling</h3> <table> <tr> <td><span class="docbook_option">finduser_retries</span></td> <td>useful in NIS environments</td> </tr> <tr> <td><span class="docbook_option">gecos_name</span></td> <td>used when creating <span class="docbook_emphasis">Sender:</span> </td> </tr> <tr> <td><span class="docbook_option">gecos_pattern</span></td> <td>ditto</td> </tr> <tr> <td><span class="docbook_option">max_username_length</span></td> <td>for systems that truncate</td> </tr> <tr> <td><span class="docbook_option">unknown_login</span></td> <td>used when no login name found</td> </tr> <tr> <td><span class="docbook_option">unknown_username</span></td> <td>ditto</td> </tr> <tr> <td><span class="docbook_option">uucp_from_pattern</span></td> <td>for recognizing “From ” lines</td> </tr> <tr> <td><span class="docbook_option">uucp_from_sender</span></td> <td>ditto</td> </tr> </table> </div> <div class="section"> <h3 id="SECID110" class="">15. All incoming messages (SMTP and non-SMTP)</h3> <table> <tr> <td><span class="docbook_option">header_maxsize</span></td> <td>total size of message header</td> </tr> <tr> <td><span class="docbook_option">header_line_maxsize</span></td> <td>individual header line limit</td> </tr> <tr> <td><span class="docbook_option">message_size_limit</span></td> <td>applies to all messages</td> </tr> <tr> <td><span class="docbook_option">percent_hack_domains</span></td> <td>recognize %-hack for these domains</td> </tr> <tr> <td><span class="docbook_option">received_header_text</span></td> <td>expanded to make <span class="docbook_emphasis">Received:</span> </td> </tr> <tr> <td><span class="docbook_option">received_headers_max</span></td> <td>for mail loop detection</td> </tr> <tr> <td><span class="docbook_option">recipients_max</span></td> <td>limit per message</td> </tr> <tr> <td><span class="docbook_option">recipients_max_reject</span></td> <td>permanently reject excess recipients</td> </tr> </table> </div> <div class="section"> <h3 id="SECID111" class="">16. Non-SMTP incoming messages</h3> <table> <tr> <td><span class="docbook_option">receive_timeout</span></td> <td>for non-SMTP messages</td> </tr> </table> </div> <div class="section"> <h3 id="SECID112" class="">17. Incoming SMTP messages</h3> <p> See also the <span class="docbook_emphasis">Policy controls</span> section above. </p> <table> <tr> <td><span class="docbook_option">host_lookup</span></td> <td>host name looked up for these hosts</td> </tr> <tr> <td><span class="docbook_option">host_lookup_order</span></td> <td>order of DNS and local name lookups</td> </tr> <tr> <td><span class="docbook_option">recipient_unqualified_hosts</span></td> <td>may send unqualified recipients</td> </tr> <tr> <td><span class="docbook_option">rfc1413_hosts</span></td> <td>make ident calls to these hosts</td> </tr> <tr> <td><span class="docbook_option">rfc1413_query_timeout</span></td> <td>zero disables ident calls</td> </tr> <tr> <td><span class="docbook_option">sender_unqualified_hosts</span></td> <td>may send unqualified senders</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_keepalive</span></td> <td>some TCP/IP magic</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_max</span></td> <td>simultaneous incoming connections</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_max_nonmail</span></td> <td>non-mail commands</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_max_nonmail_hosts</span></td> <td>hosts to which the limit applies</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_max_per_connection</span></td> <td>messages per connection</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_max_per_host</span></td> <td>connections from one host</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_queue</span></td> <td>queue mail if more connections</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_queue_per_connection</span></td> <td>queue if more messages per connection</td> </tr> <tr> <td><span class="docbook_option">smtp_accept_reserve</span></td> <td>only reserve hosts if more connections</td> </tr> <tr> <td><span class="docbook_option">smtp_active_hostname</span></td> <td>host name to use in messages</td> </tr> <tr> <td><span class="docbook_option">smtp_banner</span></td> <td>text for welcome banner</td> </tr> <tr> <td><span class="docbook_option">smtp_check_spool_space</span></td> <td>from SIZE on MAIL command</td> </tr> <tr> <td><span class="docbook_option">smtp_connect_backlog</span></td> <td>passed to TCP/IP stack</td> </tr> <tr> <td><span class="docbook_option">smtp_enforce_sync</span></td> <td>of SMTP command/responses</td> </tr> <tr> <td><span class="docbook_option">smtp_etrn_command</span></td> <td>what to run for ETRN</td> </tr> <tr> <td><span class="docbook_option">smtp_etrn_serialize</span></td> <td>only one at once</td> </tr> <tr> <td><span class="docbook_option">smtp_load_reserve</span></td> <td>only reserve hosts if this load</td> </tr> <tr> <td><span class="docbook_option">smtp_max_unknown_commands</span></td> <td>before dropping connection</td> </tr> <tr> <td><span class="docbook_option">smtp_ratelimit_hosts</span></td> <td>apply ratelimiting to these hosts</td> </tr> <tr> <td><span class="docbook_option">smtp_ratelimit_mail</span></td> <td>ratelimit for MAIL commands</td> </tr> <tr> <td><span class="docbook_option">smtp_ratelimit_rcpt</span></td> <td>ratelimit for RCPT commands</td> </tr> <tr> <td><span class="docbook_option">smtp_receive_timeout</span></td> <td>per command or data line</td> </tr> <tr> <td><span class="docbook_option">smtp_reserve_hosts</span></td> <td>these are the reserve hosts</td> </tr> <tr> <td><span class="docbook_option">smtp_return_error_details</span></td> <td>give detail on rejections</td> </tr> </table> </div> <div class="section"> <h3 id="SECID113" class="">18. SMTP extensions</h3> <table> <tr> <td><span class="docbook_option">accept_8bitmime</span></td> <td>advertise 8BITMIME</td> </tr> <tr> <td><span class="docbook_option">auth_advertise_hosts</span></td> <td>advertise AUTH to these hosts</td> </tr> <tr> <td><span class="docbook_option">ignore_fromline_hosts</span></td> <td>allow “From ” from these hosts</td> </tr> <tr> <td><span class="docbook_option">ignore_fromline_local</span></td> <td>allow “From ” from local SMTP</td> </tr> <tr> <td><span class="docbook_option">pipelining_advertise_hosts</span></td> <td>advertise pipelining to these hosts</td> </tr> <tr> <td><span class="docbook_option">tls_advertise_hosts</span></td> <td>advertise TLS to these hosts</td> </tr> </table> </div> <div class="section"> <h3 id="SECID114" class="">19. Processing messages</h3> <table> <tr> <td><span class="docbook_option">allow_domain_literals</span></td> <td>recognize domain literal syntax</td> </tr> <tr> <td><span class="docbook_option">allow_mx_to_ip</span></td> <td>allow MX to point to IP address</td> </tr> <tr> <td><span class="docbook_option">allow_utf8_domains</span></td> <td>in addresses</td> </tr> <tr> <td><span class="docbook_option">check_rfc2047_length</span></td> <td>check length of RFC 2047 “encoded words”</td> </tr> <tr> <td><span class="docbook_option">delivery_date_remove</span></td> <td>from incoming messages</td> </tr> <tr> <td><span class="docbook_option">envelope_to_remove</span></td> <td>from incoming messages</td> </tr> <tr> <td><span class="docbook_option">extract_addresses_remove_arguments</span></td> <td>affects <span class="docbook_option">-t</span> processing</td> </tr> <tr> <td><span class="docbook_option">headers_charset</span></td> <td>default for translations</td> </tr> <tr> <td><span class="docbook_option">qualify_domain</span></td> <td>default for senders</td> </tr> <tr> <td><span class="docbook_option">qualify_recipient</span></td> <td>default for recipients</td> </tr> <tr> <td><span class="docbook_option">return_path_remove</span></td> <td>from incoming messages</td> </tr> <tr> <td><span class="docbook_option">strip_excess_angle_brackets</span></td> <td>in addresses</td> </tr> <tr> <td><span class="docbook_option">strip_trailing_dot</span></td> <td>at end of addresses</td> </tr> <tr> <td><span class="docbook_option">untrusted_set_sender</span></td> <td>untrusted can set envelope sender</td> </tr> </table> </div> <div class="section"> <h3 id="SECID115" class="">20. System filter</h3> <table> <tr> <td><span class="docbook_option">system_filter</span></td> <td>locate system filter</td> </tr> <tr> <td><span class="docbook_option">system_filter_directory_transport</span></td> <td>transport for delivery to a directory</td> </tr> <tr> <td><span class="docbook_option">system_filter_file_transport</span></td> <td>transport for delivery to a file</td> </tr> <tr> <td><span class="docbook_option">system_filter_group</span></td> <td>group for filter running</td> </tr> <tr> <td><span class="docbook_option">system_filter_pipe_transport</span></td> <td>transport for delivery to a pipe</td> </tr> <tr> <td><span class="docbook_option">system_filter_reply_transport</span></td> <td>transport for autoreply delivery</td> </tr> <tr> <td><span class="docbook_option">system_filter_user</span></td> <td>user for filter running</td> </tr> </table> </div> <div class="section"> <h3 id="SECID116" class="">21. Routing and delivery</h3> <table> <tr> <td><span class="docbook_option">disable_ipv6</span></td> <td>do no IPv6 processing</td> </tr> <tr> <td><span class="docbook_option">dns_again_means_nonexist</span></td> <td>for broken domains</td> </tr> <tr> <td><span class="docbook_option">dns_check_names_pattern</span></td> <td>pre-DNS syntax check</td> </tr> <tr> <td><span class="docbook_option">dns_ipv4_lookup</span></td> <td>only v4 lookup for these domains</td> </tr> <tr> <td><span class="docbook_option">dns_retrans</span></td> <td>parameter for resolver</td> </tr> <tr> <td><span class="docbook_option">dns_retry</span></td> <td>parameter for resolver</td> </tr> <tr> <td><span class="docbook_option">dns_use_edns0</span></td> <td>parameter for resolver</td> </tr> <tr> <td><span class="docbook_option">hold_domains</span></td> <td>hold delivery for these domains</td> </tr> <tr> <td><span class="docbook_option">local_interfaces</span></td> <td>for routing checks</td> </tr> <tr> <td><span class="docbook_option">queue_domains</span></td> <td>no immediate delivery for these</td> </tr> <tr> <td><span class="docbook_option">queue_only</span></td> <td>no immediate delivery at all</td> </tr> <tr> <td><span class="docbook_option">queue_only_file</span></td> <td>no immediate delivery if file exists</td> </tr> <tr> <td><span class="docbook_option">queue_only_load</span></td> <td>no immediate delivery if load is high</td> </tr> <tr> <td><span class="docbook_option">queue_only_load_latch</span></td> <td>don’t re-evaluate load for each message</td> </tr> <tr> <td><span class="docbook_option">queue_only_override</span></td> <td>allow command line to override</td> </tr> <tr> <td><span class="docbook_option">queue_run_in_order</span></td> <td>order of arrival</td> </tr> <tr> <td><span class="docbook_option">queue_run_max</span></td> <td>of simultaneous queue runners</td> </tr> <tr> <td><span class="docbook_option">queue_smtp_domains</span></td> <td>no immediate SMTP delivery for these</td> </tr> <tr> <td><span class="docbook_option">remote_max_parallel</span></td> <td>parallel SMTP delivery per message</td> </tr> <tr> <td><span class="docbook_option">remote_sort_domains</span></td> <td>order of remote deliveries</td> </tr> <tr> <td><span class="docbook_option">retry_data_expire</span></td> <td>timeout for retry data</td> </tr> <tr> <td><span class="docbook_option">retry_interval_max</span></td> <td>safety net for retry rules</td> </tr> </table> </div> <div class="section"> <h3 id="SECID117" class="">22. Bounce and warning messages</h3> <table> <tr> <td><span class="docbook_option">bounce_message_file</span></td> <td>content of bounce</td> </tr> <tr> <td><span class="docbook_option">bounce_message_text</span></td> <td>content of bounce</td> </tr> <tr> <td><span class="docbook_option">bounce_return_body</span></td> <td>include body if returning message</td> </tr> <tr> <td><span class="docbook_option">bounce_return_message</span></td> <td>include original message in bounce</td> </tr> <tr> <td><span class="docbook_option">bounce_return_size_limit</span></td> <td>limit on returned message</td> </tr> <tr> <td><span class="docbook_option">bounce_sender_authentication</span></td> <td>send authenticated sender with bounce</td> </tr> <tr> <td><span class="docbook_option">dsn_from</span></td> <td>set <span class="docbook_emphasis">From:</span> contents in bounces</td> </tr> <tr> <td><span class="docbook_option">errors_copy</span></td> <td>copy bounce messages</td> </tr> <tr> <td><span class="docbook_option">errors_reply_to</span></td> <td> <span class="docbook_emphasis">Reply-to:</span> in bounces</td> </tr> <tr> <td><span class="docbook_option">delay_warning</span></td> <td>time schedule</td> </tr> <tr> <td><span class="docbook_option">delay_warning_condition</span></td> <td>condition for warning messages</td> </tr> <tr> <td><span class="docbook_option">ignore_bounce_errors_after</span></td> <td>discard undeliverable bounces</td> </tr> <tr> <td><span class="docbook_option">smtp_return_error_details</span></td> <td>give detail on rejections</td> </tr> <tr> <td><span class="docbook_option">warn_message_file</span></td> <td>content of warning message</td> </tr> </table> </div> <div class="section"> <h3 id="SECTalomo" class="">23. Alphabetical list of main options</h3> <p> Those options that undergo string expansion before use are marked with †. </p> <p class="changed"> </p> <table> <tr> <td><span class="docbook_option">accept_8bitmime</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p class="changed"> This option causes Exim to send 8BITMIME in its response to an SMTP EHLO command, and to accept the BODY= parameter on MAIL commands. However, though Exim is 8-bit clean, it is not a protocol converter, and it takes no steps to do anything special with messages received by this route. </p> <p class="changed"> Historically Exim kept this option off by default, but the maintainers feel that in today’s Internet, this causes more problems than it solves. It now defaults to true. A more detailed analysis of the issues is provided by Dan Bernstein: </p> <div class="docbook_literallayout"><pre> <span class="docbook_emphasis"><a href="http://cr.yp.to/smtp/8bitmime.html">http://cr.yp.to/smtp/8bitmime.html</a></span> </pre></div> <p> </p> <table> <tr> <td><span class="docbook_option">acl_not_smtp</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when a non-SMTP message has been read and is on the point of being accepted. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_not_smtp_mime</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run for individual MIME parts of non-SMTP messages. It operates in exactly the same way as <span class="docbook_option">acl_smtp_mime</span> operates for SMTP messages. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_not_smtp_start</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run before Exim starts reading a non-SMTP message. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_auth</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP AUTH command is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_connect</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP connection is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_data</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run after an SMTP DATA command has been processed and the message itself has been received, but before the final acknowledgment is sent. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_etrn</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP ETRN command is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_expn</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP EXPN command is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_helo</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP EHLO or HELO command is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_mail</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP MAIL command is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_mailauth</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when there is an AUTH parameter on a MAIL command. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for details of ACLs, and chapter <a href="ch33.html" title="33. SMTP authentication">33</a> for details of authentication. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_mime</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option is available when Exim is built with the content-scanning extension. It defines the ACL that is run for each MIME part in a message. See section <a href="ch43.html#SECTscanmimepart" title="43. Content scanning at ACL time">43.4</a> for details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_predata</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP DATA command is received, before the message itself is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_quit</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP QUIT command is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_rcpt</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP RCPT command is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_starttls</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP STARTTLS command is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">acl_smtp_vrfy</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines the ACL that is run when an SMTP VRFY command is received. See chapter <a href="ch42.html" title="42. Access control lists">42</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">admin_groups</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option is expanded just once, at the start of Exim’s processing. If the current group or any of the supplementary groups of an Exim caller is in this colon-separated list, the caller has admin privileges. If all your system programmers are in a specific group, for example, you can give them all Exim admin privileges by putting that group in <span class="docbook_option">admin_groups</span>. However, this does not permit them to read Exim’s spool files (whose group owner is the Exim gid). To permit this, you have to add individuals to the Exim group. </p> <p> </p> <table> <tr> <td><span class="docbook_option">allow_domain_literals</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If this option is set, the RFC 2822 domain literal format is permitted in email addresses. The option is not set by default, because the domain literal format is not normally required these days, and few people know about it. It has, however, been exploited by mail abusers. </p> <p> Unfortunately, it seems that some DNS black list maintainers are using this format to report black listing to postmasters. If you want to accept messages addressed to your hosts by IP address, you need to set <span class="docbook_option">allow_domain_literals</span> true, and also to add <code class="docbook_literal">@[]</code> to the list of local domains (defined in the named domain list <span class="docbook_option">local_domains</span> in the default configuration). This “magic string” matches the domain literal form of all the local host’s IP addresses. </p> <p> </p> <table> <tr> <td><span class="docbook_option">allow_mx_to_ip</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> 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 that explains the mis-configuration. However, some other MTAs support this practice, so to avoid “Why can’t Exim do this?” complaints, <span class="docbook_option">allow_mx_to_ip</span> exists, in order to enable this heinous activity. It is not recommended, except when you have no other choice. </p> <p> </p> <table> <tr> <td><span class="docbook_option">allow_utf8_domains</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> Lots of discussion is going on about internationalized domain names. One camp is strongly in favour of just using UTF-8 characters, and it seems that at least two other MTAs permit this. This option allows Exim users to experiment if they wish. </p> <p> If it is set true, Exim’s domain parsing function allows valid UTF-8 multicharacters to appear in domain name components, in addition to letters, digits, and hyphens. However, just setting this option is not enough; if you want to look up these domain names in the DNS, you must also adjust the value of <span class="docbook_option">dns_check_names_pattern</span> to match the extended form. A suitable setting is: </p> <div class="docbook_literallayout"><pre> dns_check_names_pattern = (?i)^(?>(?(1)\.\|())[a-z0-9\xc0-\xff]\ (?>[-a-z0-9\x80-\xff][a-z0-9\x80-\xbf])?)+$ </pre></div> <p> Alternatively, you can just disable this feature by setting </p> <div class="docbook_literallayout"><pre> dns_check_names_pattern = </pre></div> <p> That is, set the option to an empty string so that no check is done. </p> <p> </p> <table> <tr> <td><span class="docbook_option">auth_advertise_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis"></span> </td> </tr> </table> <p> If any server authentication mechanisms are configured, Exim advertises them in response to an EHLO command only if the calling host matches this list. Otherwise, Exim does not advertise AUTH. Exim does not accept AUTH commands from clients to which it has not advertised the availability of AUTH. The advertising of individual authentication mechanisms can be controlled by the use of the <span class="docbook_option">server_advertise_condition</span> generic authenticator option on the individual authenticators. See chapter <a href="ch33.html" title="33. SMTP authentication">33</a> for further details. </p> <p> Certain mail clients (for example, Netscape) require the user to provide a name and password for authentication if AUTH is advertised, even though it may not be needed (the host may accept messages from hosts on its local LAN without authentication, for example). The <span class="docbook_option">auth_advertise_hosts</span> option can be used to make these clients more friendly by excluding them from the set of hosts to which Exim advertises AUTH. </p> <p> If you want to advertise the availability of AUTH only when the connection is encrypted using TLS, you can make use of the fact that the value of this option is expanded, with a setting like this: </p> <div class="docbook_literallayout"><pre> auth_advertise_hosts = ${if eq{$tls_cipher}{}{}{}} </pre></div> <p> If $tls_cipher is empty, the session is not encrypted, and the result of the expansion is empty, thus matching no hosts. Otherwise, the result of the expansion is , which matches all hosts. </p> <p> </p> <table> <tr> <td><span class="docbook_option">auto_thaw</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">0s</span> </td> </tr> </table> <p> If this option is set to a time greater than zero, a queue runner will try a new delivery attempt on any frozen message, other than a bounce message, if this much time has passed since it was frozen. This may result in the message being re-frozen if nothing has changed since the last attempt. It is a way of saying “keep on trying, even though there are big problems”. </p> <p> <span class="docbook_emphasis">Note</span>: This is an old option, which predates <span class="docbook_option">timeout_frozen_after</span> and <span class="docbook_option">ignore_bounce_errors_after</span>. It is retained for compatibility, but it is not thought to be very useful any more, and its use should probably be avoided. </p> <p> </p> <table> <tr> <td><span class="docbook_option">av_scanner</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This option is available if Exim is built with the content-scanning extension. It specifies which anti-virus scanner to use. The default value is: </p> <div class="docbook_literallayout"><pre> sophie:/var/run/sophie </pre></div> <p> If the value of <span class="docbook_option">av_scanner</span> starts with a dollar character, it is expanded before use. See section <a href="ch43.html#SECTscanvirus" title="43. Content scanning at ACL time">43.1</a> for further details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">bi_command</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option supplies the name of a command that is run when Exim is called with the <span class="docbook_option">-bi</span> option (see chapter <a href="ch05.html" title="5. The Exim command line">5</a>). The string value is just the command name, it is not a complete command line. If an argument is required, it must come from the <span class="docbook_option">-oA</span> command line option. </p> <p> </p> <table> <tr> <td><span class="docbook_option">bounce_message_file</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines a template file containing paragraphs of text to be used for constructing bounce messages. Details of the file’s contents are given in chapter <a href="ch48.html" title="48. Customizing bounce and warning messages">48</a>. See also <span class="docbook_option">warn_message_file</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">bounce_message_text</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> When this option is set, its contents are included in the default bounce message immediately after “This message was created automatically by mail delivery software.” It is not used if <span class="docbook_option">bounce_message_file</span> is set. </p> <p> </p> <table> <tr> <td><span class="docbook_option">bounce_return_body</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> This option controls whether the body of an incoming message is included in a bounce message when <span class="docbook_option">bounce_return_message</span> is true. The default setting causes the entire message, both header and body, to be returned (subject to the value of <span class="docbook_option">bounce_return_size_limit</span>). If this option is false, only the message header is included. In the case of a non-SMTP message containing an error that is detected during reception, only those header lines preceding the point at which the error was detected are returned. </p> <p> </p> <table> <tr> <td><span class="docbook_option">bounce_return_message</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> If this option is set false, none of the original message is included in bounce messages generated by Exim. See also <span class="docbook_option">bounce_return_size_limit</span> and <span class="docbook_option">bounce_return_body</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">bounce_return_size_limit</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">100K</span> </td> </tr> </table> <p> This option sets a limit in bytes on the size of messages that are returned to senders as part of bounce messages when <span class="docbook_option">bounce_return_message</span> is true. The limit should be less than the value of the global <span class="docbook_option">message_size_limit</span> and of any <span class="docbook_option">message_size_limit</span> settings on transports, to allow for the bounce text that Exim generates. If this option is set to zero there is no limit. </p> <p> When the body of any message that is to be included in a bounce message is greater than the limit, it is truncated, and a comment pointing this out is added at the top. The actual cutoff may be greater than the value given, owing to the use of buffering for transferring the message in chunks (typically 8K in size). The idea is to save bandwidth on those undeliverable 15-megabyte messages. </p> <p> </p> <table> <tr> <td><span class="docbook_option">bounce_sender_authentication</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option provides an authenticated sender address that is sent with any bounce messages generated by Exim that are sent over an authenticated SMTP connection. A typical setting might be: </p> <div class="docbook_literallayout"><pre> bounce_sender_authentication = mailer-daemon@my.domain.example </pre></div> <p> which would cause bounce messages to be sent using the SMTP command: </p> <div class="docbook_literallayout"><pre> MAIL FROM:<> AUTH=mailer-daemon@my.domain.example </pre></div> <p> The value of <span class="docbook_option">bounce_sender_authentication</span> must always be a complete email address. </p> <p> </p> <table> <tr> <td><span class="docbook_option">callout_domain_negative_expire</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">3h</span> </td> </tr> </table> <p> This option specifies the expiry time for negative callout cache data for a domain. See section <a href="ch42.html#SECTcallver" title="42. Access control lists">42.43</a> for details of callout verification, and section <a href="ch42.html#SECTcallvercache" title="42. Access control lists">42.45</a> for details of the caching. </p> <p> </p> <table> <tr> <td><span class="docbook_option">callout_domain_positive_expire</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">7d</span> </td> </tr> </table> <p> This option specifies the expiry time for positive callout cache data for a domain. See section <a href="ch42.html#SECTcallver" title="42. Access control lists">42.43</a> for details of callout verification, and section <a href="ch42.html#SECTcallvercache" title="42. Access control lists">42.45</a> for details of the caching. </p> <p> </p> <table> <tr> <td><span class="docbook_option">callout_negative_expire</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">2h</span> </td> </tr> </table> <p> This option specifies the expiry time for negative callout cache data for an address. See section <a href="ch42.html#SECTcallver" title="42. Access control lists">42.43</a> for details of callout verification, and section <a href="ch42.html#SECTcallvercache" title="42. Access control lists">42.45</a> for details of the caching. </p> <p> </p> <table> <tr> <td><span class="docbook_option">callout_positive_expire</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">24h</span> </td> </tr> </table> <p> This option specifies the expiry time for positive callout cache data for an address. See section <a href="ch42.html#SECTcallver" title="42. Access control lists">42.43</a> for details of callout verification, and section <a href="ch42.html#SECTcallvercache" title="42. Access control lists">42.45</a> for details of the caching. </p> <p> </p> <table> <tr> <td><span class="docbook_option">callout_random_local_part</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This option defines the “random” local part that can be used as part of callout verification. The default value is </p> <div class="docbook_literallayout"><pre> $primary_hostname-$tod_epoch-testing </pre></div> <p> See section <a href="ch42.html#CALLaddparcall" title="42. Access control lists">42.44</a> for details of how this value is used. </p> <p> </p> <table> <tr> <td><span class="docbook_option">check_log_inodes</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> See <span class="docbook_option">check_spool_space</span> below. </p> <p> </p> <table> <tr> <td><span class="docbook_option">check_log_space</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> See <span class="docbook_option">check_spool_space</span> below. </p> <p> </p> <table> <tr> <td><span class="docbook_option">check_rfc2047_length</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> RFC 2047 defines a way of encoding non-ASCII characters in headers using a system of “encoded words”. The RFC specifies a maximum length for an encoded word; strings to be encoded that exceed this length are supposed to use multiple encoded words. By default, Exim does not recognize encoded words that exceed the maximum length. However, it seems that some software, in violation of the RFC, generates overlong encoded words. If <span class="docbook_option">check_rfc2047_length</span> is set false, Exim recognizes encoded words of any length. </p> <p> </p> <table> <tr> <td><span class="docbook_option">check_spool_inodes</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> See <span class="docbook_option">check_spool_space</span> below. </p> <p> </p> <table> <tr> <td><span class="docbook_option">check_spool_space</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> The four <span class="docbook_option">check_...</span> options allow for checking of disk resources before a message is accepted. </p> <p> When any of these options are set, they apply to all incoming messages. If you want to apply different checks to different kinds of message, you can do so by testing the variables $log_inodes, $log_space, $spool_inodes, and $spool_space in an ACL with appropriate additional conditions. </p> <p> <span class="docbook_option">check_spool_space</span> and <span class="docbook_option">check_spool_inodes</span> check the spool partition if either value is greater than zero, for example: </p> <div class="docbook_literallayout"><pre> check_spool_space = 10M check_spool_inodes = 100 </pre></div> <p> The spool partition is the one that contains the directory defined by SPOOL_DIRECTORY in <span class="docbook_filename">Local/Makefile</span>. It is used for holding messages in transit. </p> <p> <span class="docbook_option">check_log_space</span> and <span class="docbook_option">check_log_inodes</span> check the partition in which log files are written if either is greater than zero. These should be set only if <span class="docbook_option">log_file_path</span> and <span class="docbook_option">spool_directory</span> refer to different partitions. </p> <p> If there is less space or fewer inodes than requested, Exim refuses to accept incoming mail. In the case of SMTP input this is done by giving a 452 temporary error response to the MAIL command. If ESMTP is in use and there was a SIZE parameter on the MAIL command, its value is added to the <span class="docbook_option">check_spool_space</span> value, and the check is performed even if <span class="docbook_option">check_spool_space</span> is zero, unless <span class="docbook_option">no_smtp_check_spool_space</span> is set. </p> <p> The values for <span class="docbook_option">check_spool_space</span> and <span class="docbook_option">check_log_space</span> are held as a number of kilobytes. If a non-multiple of 1024 is specified, it is rounded up. </p> <p> For non-SMTP input and for batched SMTP input, the test is done at start-up; on failure a message is written to stderr and Exim exits with a non-zero code, as it obviously cannot send an error message of any kind. </p> <p> </p> <table> <tr> <td><span class="docbook_option">daemon_smtp_ports</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis"><code class="docbook_literal">smtp</code></span> </td> </tr> </table> <p> This option specifies one or more default SMTP ports on which the Exim daemon listens. See chapter <a href="ch13.html" title="13. Starting the daemon and the use of network interfaces">13</a> for details of how it is used. For backward compatibility, <span class="docbook_option">daemon_smtp_port</span> (singular) is a synonym. </p> <p> </p> <table> <tr> <td><span class="docbook_option">daemon_startup_retries</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">9</span> </td> </tr> </table> <p> This option, along with <span class="docbook_option">daemon_startup_sleep</span>, controls the retrying done by the daemon at startup when it cannot immediately bind a listening socket (typically because the socket is already in use): <span class="docbook_option">daemon_startup_retries</span> defines the number of retries after the first failure, and <span class="docbook_option">daemon_startup_sleep</span> defines the length of time to wait between retries. </p> <p> </p> <table> <tr> <td><span class="docbook_option">daemon_startup_sleep</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">30s</span> </td> </tr> </table> <p> See <span class="docbook_option">daemon_startup_retries</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">delay_warning</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time list</span> </td> <td>Default: <span class="docbook_emphasis">24h</span> </td> </tr> </table> <p> When a message is delayed, Exim sends a warning message to the sender at intervals specified by this option. The data is a colon-separated list of times after which to send warning messages. If the value of the option is an empty string or a zero time, no warnings are sent. Up to 10 times may be given. If a message has been on the queue for longer than the last time, the last interval between the times is used to compute subsequent warning times. For example, with </p> <div class="docbook_literallayout"><pre> delay_warning = 4h:8h:24h </pre></div> <p> the first message is sent after 4 hours, the second after 8 hours, and the third one after 24 hours. After that, messages are sent every 16 hours, because that is the interval between the last two times on the list. If you set just one time, it specifies the repeat interval. For example, with: </p> <div class="docbook_literallayout"><pre> delay_warning = 6h </pre></div> <p> messages are repeated every six hours. To stop warnings after a given time, set a very large time at the end of the list. For example: </p> <div class="docbook_literallayout"><pre> delay_warning = 2h:12h:99d </pre></div> <p> </p> <table> <tr> <td><span class="docbook_option">delay_warning_condition</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> The string is expanded at the time a warning message might be sent. If all the deferred addresses have the same domain, it is set in $domain during the expansion. Otherwise $domain is empty. If the result of the expansion is a forced failure, an empty string, or a string matching any of “0”, “no” or “false” (the comparison being done caselessly) then the warning message is not sent. The default is: </p> <div class="docbook_literallayout"><pre> delay_warning_condition = ${if or {\ { !eq{$h_list-id:$h_list-post:$h_list-subscribe:}{} }\ { match{$h_precedence:}{(?i)bulk\|list\|junk} }\ { match{$h_auto-submitted:}{(?i)auto-generated\|auto-replied} }\ } {no}{yes}} </pre></div> <p> This suppresses the sending of warnings for messages that contain <span class="docbook_emphasis">List-ID:</span>, <span class="docbook_emphasis">List-Post:</span>, or <span class="docbook_emphasis">List-Subscribe:</span> headers, or have “bulk”, “list” or “junk” in a <span class="docbook_emphasis">Precedence:</span> header, or have “auto-generated” or “auto-replied” in an <span class="docbook_emphasis">Auto-Submitted:</span> header. </p> <p> </p> <table> <tr> <td><span class="docbook_option">deliver_drop_privilege</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If this option is set true, Exim drops its root privilege at the start of a delivery process, and runs as the Exim user throughout. This severely restricts the kinds of local delivery that are possible, but is viable in certain types of configuration. There is a discussion about the use of root privilege in chapter <a href="ch54.html" title="54. Security considerations">54</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">deliver_queue_load_max</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">fixed-point</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> When this option is set, a queue run is abandoned if the system load average becomes greater than the value of the option. The option has no effect on ancient operating systems on which Exim cannot determine the load average. See also <span class="docbook_option">queue_only_load</span> and <span class="docbook_option">smtp_load_reserve</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">delivery_date_remove</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> Exim’s transports have an option for adding a <span class="docbook_emphasis">Delivery-date:</span> header to a message when it is delivered, in exactly the same way as <span class="docbook_emphasis">Return-path:</span> is handled. <span class="docbook_emphasis">Delivery-date:</span> records the actual time of delivery. Such headers should not 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. </p> <p> </p> <table> <tr> <td><span class="docbook_option">disable_fsync</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> This option is available only if Exim was built with the compile-time option ENABLE_DISABLE_FSYNC. When this is not set, a reference to <span class="docbook_option">disable_fsync</span> in a runtime configuration generates an “unknown option” error. You should not build Exim with ENABLE_DISABLE_FSYNC or set <span class="docbook_option">disable_fsync</span> unless you really, really, really understand what you are doing. <span class="docbook_emphasis">No pre-compiled distributions of Exim should ever make this option available.</span> </p> <p> When <span class="docbook_option">disable_fsync</span> is set true, Exim no longer calls <span class="docbook_function">fsync()</span> to force updated files’ data to be written to disc before continuing. Unexpected events such as crashes and power outages may cause data to be lost or scrambled. Here be Dragons. <span class="docbook_emphasis">Beware.</span> </p> <p> </p> <table> <tr> <td><span class="docbook_option">disable_ipv6</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If this option is set true, even if the Exim binary has IPv6 support, no IPv6 activities take place. AAAA records are never looked up, and any IPv6 addresses that are listed in <span class="docbook_option">local_interfaces</span>, data for the <span class="docbook_option">manualroute</span> router, etc. are ignored. If IP literals are enabled, the <span class="docbook_command">ipliteral</span> router declines to handle IPv6 literal addresses. </p> <p> </p> <table> <tr> <td><span class="docbook_option">dns_again_means_nonexist</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">domain list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> DNS lookups give a “try again” response for the DNS errors “non-authoritative host not found” and “SERVERFAIL”. This can cause Exim to keep trying to deliver a message, or to give repeated temporary errors to incoming mail. Sometimes the effect is caused by a badly set up name server and may persist for a long time. If a domain which exhibits this problem matches anything in <span class="docbook_option">dns_again_means_nonexist</span>, it is treated as if it did not exist. This option should be used with care. You can make it apply to reverse lookups by a setting such as this: </p> <div class="docbook_literallayout"><pre> dns_again_means_nonexist = .in-addr.arpa </pre></div> <p> This option applies to all DNS lookups that Exim does. It also applies when the <span class="docbook_function">gethostbyname()</span> or <span class="docbook_function">getipnodebyname()</span> functions give temporary errors, since these are most likely to be caused by DNS lookup problems. The <span class="docbook_command">dnslookup</span> router has some options of its own for controlling what happens when lookups for MX or SRV records give temporary errors. These more specific options are applied after this global option. </p> <p> </p> <table> <tr> <td><span class="docbook_option">dns_check_names_pattern</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> When this option is set to a non-empty string, it causes Exim to check domain names for characters that are not allowed in host names before handing them to the DNS resolver, because some resolvers give temporary errors for names that contain unusual characters. If a domain name contains any unwanted characters, a “not found” result is forced, and the resolver is not called. The check is done by matching the domain name against a regular expression, which is the value of this option. The default pattern is </p> <div class="docbook_literallayout"><pre> dns_check_names_pattern = \ (?i)^(?>(?(1)\.\|())[^\W_](?>[a-z0-9/-][^\W_])?)+$ </pre></div> <p> which permits only letters, digits, slashes, and hyphens in components, but they must start and end with a letter or digit. Slashes are not, in fact, permitted in host names, but they are found in certain NS records (which can be accessed in Exim by using a <span class="docbook_option">dnsdb</span> lookup). If you set <span class="docbook_option">allow_utf8_domains</span>, you must modify this pattern, or set the option to an empty string. </p> <p> </p> <table> <tr> <td><span class="docbook_option">dns_csa_search_limit</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">5</span> </td> </tr> </table> <p> This option controls the depth of parental searching for CSA SRV records in the DNS, as described in more detail in section <a href="ch42.html#SECTverifyCSA" title="42. Access control lists">42.48</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">dns_csa_use_reverse</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> This option controls whether or not an IP address, given as a CSA domain, is reversed and looked up in the reverse DNS, as described in more detail in section <a href="ch42.html#SECTverifyCSA" title="42. Access control lists">42.48</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">dns_ipv4_lookup</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">domain list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> When Exim is compiled with IPv6 support and <span class="docbook_option">disable_ipv6</span> is not set, it looks for IPv6 address records (AAAA records) as well as IPv4 address records (A records) when trying to find IP addresses for hosts, unless the host’s domain matches this list. </p> <p> This is a fudge to help with name servers that give big delays or otherwise do not work for the AAAA record type. In due course, when the world’s name servers have all been upgraded, there should be no need for this option. </p> <p> </p> <table> <tr> <td><span class="docbook_option">dns_retrans</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">0s</span> </td> </tr> </table> <p> The options <span class="docbook_option">dns_retrans</span> and <span class="docbook_option">dns_retry</span> can be used to set the retransmission and retry parameters for DNS lookups. Values of zero (the defaults) leave the system default settings unchanged. The first value is the time between retries, and the second is the number of retries. It isn’t totally clear exactly how these settings affect the total time a DNS lookup may take. I haven’t found any documentation about timeouts on DNS lookups; these 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. </p> <p> </p> <table> <tr> <td><span class="docbook_option">dns_retry</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> See <span class="docbook_option">dns_retrans</span> above. </p> <p class="changed"> </p> <table> <tr> <td><span class="docbook_option">dns_use_edns0</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">-1</span> </td> </tr> </table> <p class="changed"> If this option is set to a non-negative number then Exim will initialise the DNS resolver library to either use or not use EDNS0 extensions, overriding the system default. A value of 0 coerces EDNS0 off, a value of 1 coerces EDNS0 on. </p> <p class="changed"> If the resolver library does not support EDNS0 then this option has no effect. </p> <p> </p> <table> <tr> <td><span class="docbook_option">drop_cr</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> This is an obsolete option that is now a no-op. It used to affect the way Exim handled CR and LF characters in incoming messages. What happens now is described in section <a href="ch46.html#SECTlineendings" title="46. Message processing">46.2</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">dsn_from</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This option can be used to vary the contents of <span class="docbook_emphasis">From:</span> header lines in bounces and other automatically generated messages (“Delivery Status Notifications” – hence the name of the option). The default setting is: </p> <div class="docbook_literallayout"><pre> dsn_from = Mail Delivery System <Mailer-Daemon@$qualify_domain> </pre></div> <p> The value is expanded every time it is needed. If the expansion fails, a panic is logged, and the default value is used. </p> <p> </p> <table> <tr> <td><span class="docbook_option">envelope_to_remove</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> Exim’s transports have an option for adding an <span class="docbook_emphasis">Envelope-to:</span> header to a message when it is delivered, in exactly the same way as <span class="docbook_emphasis">Return-path:</span> is handled. <span class="docbook_emphasis">Envelope-to:</span> records the original recipient address from the messages’s envelope that caused the delivery to happen. Such headers should not 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. </p> <p> </p> <table> <tr> <td><span class="docbook_option">errors_copy</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> Setting this option causes Exim to send bcc copies of bounce messages that it generates to other addresses. <span class="docbook_emphasis">Note</span>: This does not apply to bounce messages coming from elsewhere. The value of the option is a colon-separated list of items. Each item consists of a pattern, terminated by white space, followed by a comma-separated list of email addresses. If a pattern contains spaces, it must be enclosed in double quotes. </p> <p> Each pattern is processed in the same way as a single item in an address list (see section <a href="ch10.html#SECTaddresslist" title="10. Domain, host, address, and local part lists">10.19</a>). When a pattern matches the recipient of the bounce message, the message is copied to the addresses on the list. The items are scanned in order, and once a matching one is found, no further items are examined. For example: </p> <div class="docbook_literallayout"><pre> errors_copy = spqr@mydomain postmaster@mydomain.example :\ rqps@mydomain hostmaster@mydomain.example,\ postmaster@mydomain.example </pre></div> <p> The address list is expanded before use. The expansion variables $local_part and $domain are set from the original recipient of the error message, and if there was any wildcard matching in the pattern, the expansion variables $0, $1, etc. are set in the normal way. </p> <p> </p> <table> <tr> <td><span class="docbook_option">errors_reply_to</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> By default, Exim’s bounce and delivery warning messages contain the header line </p> <div class="docbook_literallayout"><pre> <code class="docbook_literal">From: Mail Delivery System <Mailer-Daemon@</code><span class="docbook_emphasis">qualify-domain</span><code class="docbook_literal">></code> </pre></div> <p> where <span class="docbook_emphasis">qualify-domain</span> is the value of the <span class="docbook_option">qualify_domain</span> option. A warning message that is generated by the <span class="docbook_option">quota_warn_message</span> option in an <span class="docbook_command">appendfile</span> transport may contain its own <span class="docbook_emphasis">From:</span> header line that overrides the default. </p> <p> Experience shows that people reply to bounce messages. If the <span class="docbook_option">errors_reply_to</span> option is set, a <span class="docbook_emphasis">Reply-To:</span> header is added to bounce and warning messages. For example: </p> <div class="docbook_literallayout"><pre> errors_reply_to = postmaster@my.domain.example </pre></div> <p> The value of the option is not expanded. It must specify a valid RFC 2822 address. However, if a warning message that is generated by the <span class="docbook_option">quota_warn_message</span> option in an <span class="docbook_command">appendfile</span> transport contain its own <span class="docbook_emphasis">Reply-To:</span> header line, the value of the <span class="docbook_option">errors_reply_to</span> option is not used. </p> <p> </p> <table> <tr> <td><span class="docbook_option">exim_group</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">compile-time configured</span> </td> </tr> </table> <p> This option changes the gid under which Exim runs when it gives up root privilege. The default value is compiled into the binary. The value of this option is used only when <span class="docbook_option">exim_user</span> is also set. Unless it consists entirely of digits, the string is looked up using <span class="docbook_function">getgrnam()</span>, and failure causes a configuration error. See chapter <a href="ch54.html" title="54. Security considerations">54</a> for a discussion of security issues. </p> <p> </p> <table> <tr> <td><span class="docbook_option">exim_path</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This option specifies the path name of the Exim binary, which is used when Exim needs to re-exec itself. The default is set up to point to the file <span class="docbook_emphasis">exim</span> in the directory configured at compile time by the BIN_DIRECTORY setting. It is necessary to change <span class="docbook_option">exim_path</span> if, exceptionally, Exim is run from some other place. <span class="docbook_emphasis">Warning</span>: Do not use a macro to define the value of this option, because you will break those Exim utilities that scan the configuration file to find where the binary is. (They then use the <span class="docbook_option">-bP</span> option to extract option settings such as the value of <span class="docbook_option">spool_directory</span>.) </p> <p> </p> <table> <tr> <td><span class="docbook_option">exim_user</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">compile-time configured</span> </td> </tr> </table> <p> This option changes the uid under which Exim runs when it gives up root privilege. The default value is compiled into the binary. Ownership of the run time configuration file and the use of the <span class="docbook_option">-C</span> and <span class="docbook_option">-D</span> command line options is checked against the values in the binary, not what is set here. </p> <p> Unless it consists entirely of digits, the string is looked up using <span class="docbook_function">getpwnam()</span>, and failure causes a configuration error. If <span class="docbook_option">exim_group</span> is not also supplied, the gid is taken from the result of <span class="docbook_function">getpwnam()</span> if it is used. See chapter <a href="ch54.html" title="54. Security considerations">54</a> for a discussion of security issues. </p> <p> </p> <table> <tr> <td><span class="docbook_option">extra_local_interfaces</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines network interfaces that are to be considered local when routing, but which are not used for listening by the daemon. See section <a href="ch13.html#SECTreclocipadd" title="13. Starting the daemon and the use of network interfaces">13.8</a> for details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">extract_addresses_remove_ arguments</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> According to some Sendmail documentation (Sun, IRIX, HP-UX), if any addresses are present on the command line when the <span class="docbook_option">-t</span> option is used to build an envelope from a message’s <span class="docbook_emphasis">To:</span>, <span class="docbook_emphasis">Cc:</span> and <span class="docbook_emphasis">Bcc:</span> headers, the command line addresses are removed from the recipients list. This is also how Smail behaves. However, other Sendmail documentation (the O’Reilly book) states that command line addresses are added to those obtained from the header lines. When <span class="docbook_option">extract_addresses_remove_arguments</span> is true (the default), Exim subtracts argument headers. If it is set false, Exim adds rather than removes argument addresses. </p> <p> </p> <table> <tr> <td><span class="docbook_option">finduser_retries</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> On systems running NIS or other schemes in which user and group information is distributed from a remote system, there can be times when <span class="docbook_function">getpwnam()</span> and related functions fail, even when given valid data, because things time out. Unfortunately these failures cannot be distinguished from genuine “not found” errors. If <span class="docbook_option">finduser_retries</span> is set greater than zero, Exim will try that many extra times to find a user or a group, waiting for one second between retries. </p> <p> You should not set this option greater than zero if your user information is in a traditional <span class="docbook_filename">/etc/passwd</span> file, because it will cause Exim needlessly to search the file multiple times for non-existent users, and also cause delay. </p> <p> </p> <table> <tr> <td><span class="docbook_option">freeze_tell</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list, comma separated</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> On encountering certain errors, or when configured to do so in a system filter, ACL, or special router, Exim freezes a message. This means that no further delivery attempts take place until an administrator thaws the message, or the <span class="docbook_option">auto_thaw</span>, <span class="docbook_option">ignore_bounce_errors_after</span>, or <span class="docbook_option">timeout_frozen_after</span> feature cause it to be processed. If <span class="docbook_option">freeze_tell</span> is set, Exim generates a warning message whenever it freezes something, unless the message it is freezing is a locally-generated bounce message. (Without this exception there is the possibility of looping.) The warning message is sent to the addresses supplied as the comma-separated value of this option. If several of the message’s addresses cause freezing, only a single message is sent. If the freezing was automatic, the reason(s) for freezing can be found in the message log. If you configure freezing in a filter or ACL, you must arrange for any logging that you require. </p> <p> </p> <table> <tr> <td><span class="docbook_option">gecos_name</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> Some operating systems, notably HP-UX, use the “gecos” field in the system password file to hold other information in addition to users’ real names. Exim looks up this field for use when it is creating <span class="docbook_emphasis">Sender:</span> or <span class="docbook_emphasis">From:</span> headers. If either <span class="docbook_option">gecos_pattern</span> or <span class="docbook_option">gecos_name</span> are unset, the contents of the field are used unchanged, except that, if an ampersand is encountered, it is replaced by the user’s login name with the first character forced to upper case, since this is a convention that is observed on many systems. </p> <p> When these options are set, <span class="docbook_option">gecos_pattern</span> is treated as a regular expression that is to be applied to the field (again with & replaced by the login name), and if it matches, <span class="docbook_option">gecos_name</span> is expanded and used as the user’s name. </p> <p> Numeric variables such as $1, $2, etc. can be used in the expansion to pick up sub-fields that were matched by the pattern. In HP-UX, where the user’s name terminates at the first comma, the following can be used: </p> <div class="docbook_literallayout"><pre> gecos_pattern = ([^,]) gecos_name = $1 </pre></div> <p> </p> <table> <tr> <td><span class="docbook_option">gecos_pattern</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> See <span class="docbook_option">gecos_name</span> above. </p> <p> </p> <table> <tr> <td><span class="docbook_option">gnutls_compat_mode</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option controls whether GnuTLS is used in compatibility mode in an Exim server. This reduces security slightly, but improves interworking with older implementations of TLS. </p> <p> </p> <table> <tr> <td><span class="docbook_option">headers_charset</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This option sets a default character set for translating from encoded MIME “words” in header lines, when referenced by an $h_xxx expansion item. The default is the value of HEADERS_CHARSET in <span class="docbook_filename">Local/Makefile</span>. The ultimate default is ISO-8859-1. For more details see the description of header insertions in section <a href="ch11.html#SECTexpansionitems" title="11. String expansions">11.5</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">header_maxsize</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This option controls the overall maximum size of a message’s header section. The default is the value of HEADER_MAXSIZE in <span class="docbook_filename">Local/Makefile</span>; the default for that is 1M. Messages with larger header sections are rejected. </p> <p> </p> <table> <tr> <td><span class="docbook_option">header_line_maxsize</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> This option limits the length of any individual header line in a message, after all the continuations have been joined together. Messages with individual header lines that are longer than the limit are rejected. The default value of zero means “no limit”. </p> <p> </p> <table> <tr> <td><span class="docbook_option">helo_accept_junk_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> Exim checks the syntax of HELO and EHLO commands for incoming SMTP mail, and gives an error response for invalid data. Unfortunately, there are some SMTP clients that send syntactic junk. They can be accommodated by setting this option. Note that this is a syntax check only. See <span class="docbook_option">helo_verify_hosts</span> if you want to do semantic checking. See also <span class="docbook_option">helo_allow_chars</span> for a way of extending the permitted character set. </p> <p> </p> <table> <tr> <td><span class="docbook_option">helo_allow_chars</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option can be set to a string of rogue characters that are permitted in all EHLO and HELO names in addition to the standard letters, digits, hyphens, and dots. If you really must allow underscores, you can set </p> <div class="docbook_literallayout"><pre> helo_allow_chars = _ </pre></div> <p> Note that the value is one string, not a list. </p> <p> </p> <table> <tr> <td><span class="docbook_option">helo_lookup_domains</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">domain list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis"><code class="docbook_literal">@:@[]</code></span> </td> </tr> </table> <p> If the domain given by a client in a HELO or EHLO command matches this list, a reverse lookup is done in order to establish the host’s true name. The default forces a lookup if the client host gives the server’s name or any of its IP addresses (in brackets), something that broken clients have been seen to do. </p> <p> </p> <table> <tr> <td><span class="docbook_option">helo_try_verify_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> By default, Exim just checks the syntax of HELO and EHLO commands (see <span class="docbook_option">helo_accept_junk_hosts</span> and <span class="docbook_option">helo_allow_chars</span>). However, some sites like to do more extensive checking of the data supplied by these commands. The ACL condition <code class="docbook_literal">verify = helo</code> is provided to make this possible. Formerly, it was necessary also to set this option (<span class="docbook_option">helo_try_verify_hosts</span>) to force the check to occur. From release 4.53 onwards, this is no longer necessary. If the check has not been done before <code class="docbook_literal">verify = helo</code> is encountered, it is done at that time. Consequently, this option is obsolete. Its specification is retained here for backwards compatibility. </p> <p> When an EHLO or HELO command is received, if the calling host matches <span class="docbook_option">helo_try_verify_hosts</span>, Exim checks that the host name given in the HELO or EHLO command either: </p> <ul> <li> <p> is an IP literal matching the calling address of the host, or </p> </li> <li> <p> matches the host name that Exim obtains by doing a reverse lookup of the calling host address, or </p> </li> <li> <p> when looked up using <span class="docbook_function">gethostbyname()</span> (or <span class="docbook_function">getipnodebyname()</span> when available) yields the calling host address. </p> </li> </ul> <p> However, the EHLO or HELO command is not rejected if any of the checks fail. Processing continues, but the result of the check is remembered, and can be detected later in an ACL by the <code class="docbook_literal">verify = helo</code> condition. </p> <p> </p> <table> <tr> <td><span class="docbook_option">helo_verify_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> Like <span class="docbook_option">helo_try_verify_hosts</span>, this option is obsolete, and retained only for backwards compatibility. For hosts that match this option, Exim checks the host name given in the HELO or EHLO in the same way as for <span class="docbook_option">helo_try_verify_hosts</span>. If the check fails, the HELO or EHLO command is rejected with a 550 error, and entries are written to the main and reject logs. If a MAIL command is received before EHLO or HELO, it is rejected with a 503 error. </p> <p> </p> <table> <tr> <td><span class="docbook_option">hold_domains</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">domain list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option allows mail for particular domains to be held on the queue manually. The option is overridden if a message delivery is forced with the <span class="docbook_option">-M</span>, <span class="docbook_option">-qf</span>, <span class="docbook_option">-Rf</span> or <span class="docbook_option">-Sf</span> options, and also while testing or verifying addresses using <span class="docbook_option">-bt</span> or <span class="docbook_option">-bv</span>. Otherwise, if a domain matches an item in <span class="docbook_option">hold_domains</span>, no routing or delivery for that address is done, and it is deferred every time the message is looked at. </p> <p> This option is intended as a temporary operational measure for delaying the delivery of mail while some problem is being sorted out, or some new configuration tested. If you just want to delay the processing of some domains until a queue run occurs, you should use <span class="docbook_option">queue_domains</span> or <span class="docbook_option">queue_smtp_domains</span>, not <span class="docbook_option">hold_domains</span>. </p> <p> A setting of <span class="docbook_option">hold_domains</span> does not override Exim’s code for removing messages from the queue if they have been there longer than the longest retry time in any retry rule. If you want to hold messages for longer than the normal retry times, insert a dummy retry rule with a long retry time. </p> <p> </p> <table> <tr> <td><span class="docbook_option">host_lookup</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> Exim does not look up the name of a calling host from its IP address unless it is required to compare against some host list, or the host matches <span class="docbook_option">helo_try_verify_hosts</span> or <span class="docbook_option">helo_verify_hosts</span>, or the host matches this option (which normally contains IP addresses rather than host names). The default configuration file contains </p> <div class="docbook_literallayout"><pre> host_lookup = </pre></div> <p> which causes a lookup to happen for all hosts. If the expense of these lookups is felt to be too great, the setting can be changed or removed. </p> <p> After a successful reverse lookup, Exim does a forward lookup on the name it has obtained, to verify that it yields the IP address that it started with. If this check fails, Exim behaves as if the name lookup failed. </p> <p> After any kind of failure, the host name (in $sender_host_name) remains unset, and $host_lookup_failed is set to the string “1”. See also <span class="docbook_option">dns_again_means_nonexist</span>, <span class="docbook_option">helo_lookup_domains</span>, and <code class="docbook_literal">verify = reverse_host_lookup</code> in ACLs. </p> <p> </p> <table> <tr> <td><span class="docbook_option">host_lookup_order</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis"><code class="docbook_literal">bydns:byaddr</code></span> </td> </tr> </table> <p> This option specifies the order of different lookup methods when Exim is trying to find a host name from an IP address. The default is to do a DNS lookup first, and then to try a local lookup (using <span class="docbook_function">gethostbyaddr()</span> or equivalent) if that fails. You can change the order of these lookups, or omit one entirely, if you want. </p> <p> <span class="docbook_emphasis">Warning</span>: The “byaddr” method does not always yield aliases when there are multiple PTR records in the DNS and the IP address is not listed in <span class="docbook_filename">/etc/hosts</span>. Different operating systems give different results in this case. That is why the default tries a DNS lookup first. </p> <p> </p> <table> <tr> <td><span class="docbook_option">host_reject_connection</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> If this option is set, incoming SMTP calls from the hosts listed are rejected as soon as the connection is made. This option is obsolete, and retained only for backward compatibility, because nowadays the ACL specified by <span class="docbook_option">acl_smtp_connect</span> can also reject incoming connections immediately. </p> <p> The ability to give an immediate rejection (either by this option or using an ACL) is provided for use in unusual cases. Many hosts will just try again, sometimes without much delay. Normally, it is better to use an ACL to reject incoming messages at a later stage, such as after RCPT commands. See chapter <a href="ch42.html" title="42. Access control lists">42</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">hosts_connection_nolog</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines a list of hosts for which connection logging does not happen, even though the <span class="docbook_option">smtp_connection</span> log selector is set. For example, you might want not to log SMTP connections from local processes, or from 127.0.0.1, or from your local LAN. This option is consulted in the main loop of the daemon; you should therefore strive to restrict its value to a short inline list of IP addresses and networks. To disable logging SMTP connections from local processes, you must create a host list with an empty item. For example: </p> <div class="docbook_literallayout"><pre> hosts_connection_nolog = : </pre></div> <p> If the <span class="docbook_option">smtp_connection</span> log selector is not set, this option has no effect. </p> <p> </p> <table> <tr> <td><span class="docbook_option">hosts_treat_as_local</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">domain list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> If this option is set, any host names that match the domain list are treated as if they were the local host when Exim is scanning host lists obtained from MX records or other sources. Note that the value of this option is a domain list, not a host list, because it is always used to check host names, not IP addresses. </p> <p> This option also applies when Exim is matching the special items <code class="docbook_literal">@mx_any</code>, <code class="docbook_literal">@mx_primary</code>, and <code class="docbook_literal">@mx_secondary</code> in a domain list (see section <a href="ch10.html#SECTdomainlist" title="10. Domain, host, address, and local part lists">10.8</a>), and when checking the <span class="docbook_option">hosts</span> option in the <span class="docbook_command">smtp</span> transport for the local host (see the <span class="docbook_option">allow_localhost</span> option in that transport). See also <span class="docbook_option">local_interfaces</span>, <span class="docbook_option">extra_local_interfaces</span>, and chapter <a href="ch13.html" title="13. Starting the daemon and the use of network interfaces">13</a>, which contains a discussion about local network interfaces and recognizing the local host. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ibase_servers</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option provides a list of InterBase servers and associated connection data, to be used in conjunction with <span class="docbook_command">ibase</span> lookups (see section <a href="ch09.html#SECID72" title="9. File and database lookups">9.21</a>). The option is available only if Exim has been built with InterBase support. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ignore_bounce_errors_after</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">10w</span> </td> </tr> </table> <p> This option affects the processing of bounce messages that cannot be delivered, that is, those that suffer a permanent delivery failure. (Bounce messages that suffer temporary delivery failures are of course retried in the usual way.) </p> <p> After a permanent delivery failure, bounce messages are frozen, because there is no sender to whom they can be returned. When a frozen bounce message has been on the queue for more than the given time, it is unfrozen at the next queue run, and a further delivery is attempted. If delivery fails again, the bounce message is discarded. This makes it possible to keep failed bounce messages around for a shorter time than the normal maximum retry time for frozen messages. For example, </p> <div class="docbook_literallayout"><pre> ignore_bounce_errors_after = 12h </pre></div> <p> retries failed bounce message deliveries after 12 hours, discarding any further failures. If the value of this option is set to a zero time period, bounce failures are discarded immediately. Setting a very long time (as in the default value) has the effect of disabling this option. For ways of automatically dealing with other kinds of frozen message, see <span class="docbook_option">auto_thaw</span> and <span class="docbook_option">timeout_frozen_after</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ignore_fromline_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> Some broken SMTP clients insist on sending a UUCP-like “From ” line before the headers of a message. By default this is treated as the start of the message’s body, which means that any following headers are not recognized as such. Exim can be made to ignore it by setting <span class="docbook_option">ignore_fromline_hosts</span> to match those hosts that insist on sending it. If the sender is actually a local process rather than a remote host, and is using <span class="docbook_option">-bs</span> to inject the messages, <span class="docbook_option">ignore_fromline_local</span> must be set to achieve this effect. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ignore_fromline_local</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> See <span class="docbook_option">ignore_fromline_hosts</span> above. </p> <p> </p> <table> <tr> <td><span class="docbook_option">keep_malformed</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">4d</span> </td> </tr> </table> <p> This option specifies the length of time to keep messages whose spool files have been corrupted in some way. This should, of course, never happen. At the next attempt to deliver such a message, it gets removed. The incident is logged. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ldap_ca_cert_dir</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option indicates which directory contains CA certificates for verifying a TLS certificate presented by an LDAP server. While Exim does not provide a default value, your SSL library may. Analogous to <span class="docbook_option">tls_verify_certificates</span> but as a client-side option for LDAP and constrained to be a directory. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ldap_ca_cert_file</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option indicates which file contains CA certificates for verifying a TLS certificate presented by an LDAP server. While Exim does not provide a default value, your SSL library may. Analogous to <span class="docbook_option">tls_verify_certificates</span> but as a client-side option for LDAP and constrained to be a file. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ldap_cert_file</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option indicates which file contains an TLS client certificate which Exim should present to the LDAP server during TLS negotiation. Should be used together with <span class="docbook_option">ldap_cert_key</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ldap_cert_key</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option indicates which file contains the secret/private key to use to prove identity to the LDAP server during TLS negotiation. Should be used together with <span class="docbook_option">ldap_cert_file</span>, which contains the identity to be proven. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ldap_cipher_suite</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This controls the TLS cipher-suite negotiation during TLS negotiation with the LDAP server. See <a href="ch41.html#SECTreqciphssl" title="41. Encrypted SMTP connections using TLS/SSL">41.4</a> for more details of the format of cipher-suite options with OpenSSL (as used by LDAP client libraries). </p> <p> </p> <table> <tr> <td><span class="docbook_option">ldap_default_servers</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option provides a list of LDAP servers which are tried in turn when an LDAP query does not contain a server. See section <a href="ch09.html#SECTforldaque" title="9. File and database lookups">9.14</a> for details of LDAP queries. This option is available only when Exim has been built with LDAP support. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ldap_require_cert</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset.</span> </td> </tr> </table> <p> This should be one of the values "hard", "demand", "allow", "try" or "never". A value other than one of these is interpreted as "never". See the entry "TLS_REQCERT" in your system man page for ldap.conf(5). Although Exim does not set a default, the LDAP library probably defaults to hard/demand. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ldap_start_tls</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If set, Exim will attempt to negotiate TLS with the LDAP server when connecting on a regular LDAP port. This is the LDAP equivalent of SMTP’s "STARTTLS". This is distinct from using "ldaps", which is the LDAP form of SSL-on-connect. In the event of failure to negotiate TLS, the action taken is controlled by <span class="docbook_option">ldap_require_cert</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">ldap_version</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option can be used to force Exim to set a specific protocol version for LDAP. If it option is unset, it is shown by the <span class="docbook_option">-bP</span> command line option as -1. When this is the case, the default is 3 if LDAP_VERSION3 is defined in the LDAP headers; otherwise it is 2. This option is available only when Exim has been built with LDAP support. </p> <p> </p> <table> <tr> <td><span class="docbook_option">local_from_check</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> When a message is submitted locally (that is, not over a TCP/IP connection) by an untrusted user, Exim removes any existing <span class="docbook_emphasis">Sender:</span> header line, and checks that the <span class="docbook_emphasis">From:</span> header line matches the login of the calling user and the domain specified by <span class="docbook_option">qualify_domain</span>. </p> <p> <span class="docbook_emphasis">Note</span>: An unqualified address (no domain) in the <span class="docbook_emphasis">From:</span> header in a locally submitted message is automatically qualified by Exim, unless the <span class="docbook_option">-bnq</span> command line option is used. </p> <p> You can use <span class="docbook_option">local_from_prefix</span> and <span class="docbook_option">local_from_suffix</span> to permit affixes on the local part. If the <span class="docbook_emphasis">From:</span> header line does not match, Exim adds a <span class="docbook_emphasis">Sender:</span> header with an address constructed from the calling user’s login and the default qualify domain. </p> <p> If <span class="docbook_option">local_from_check</span> is set false, the <span class="docbook_emphasis">From:</span> header check is disabled, and no <span class="docbook_emphasis">Sender:</span> header is ever added. If, in addition, you want to retain <span class="docbook_emphasis">Sender:</span> header lines supplied by untrusted users, you must also set <span class="docbook_option">local_sender_retain</span> to be true. </p> <p> These options affect only the header lines in the message. The envelope sender is still forced to be the login id at the qualify domain unless <span class="docbook_option">untrusted_set_sender</span> permits the user to supply an envelope sender. </p> <p> For messages received over TCP/IP, an ACL can specify “submission mode” to request similar header line checking. See section <a href="ch46.html#SECTthesenhea" title="46. Message processing">46.16</a>, which has more details about <span class="docbook_emphasis">Sender:</span> processing. </p> <p> </p> <table> <tr> <td><span class="docbook_option">local_from_prefix</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> When Exim checks the <span class="docbook_emphasis">From:</span> header line of locally submitted messages for matching the login id (see <span class="docbook_option">local_from_check</span> above), it can be configured to ignore certain prefixes and suffixes in the local part of the address. This is done by setting <span class="docbook_option">local_from_prefix</span> and/or <span class="docbook_option">local_from_suffix</span> to appropriate lists, in the same form as the <span class="docbook_option">local_part_prefix</span> and <span class="docbook_option">local_part_suffix</span> router options (see chapter <a href="ch15.html" title="15. Generic options for routers">15</a>). For example, if </p> <div class="docbook_literallayout"><pre> local_from_prefix = - </pre></div> <p> is set, a <span class="docbook_emphasis">From:</span> line containing </p> <div class="docbook_literallayout"><pre> From: anything-user@your.domain.example </pre></div> <p> will not cause a <span class="docbook_emphasis">Sender:</span> header to be added if <span class="docbook_emphasis">user@your.domain.example</span> matches the actual sender address that is constructed from the login name and qualify domain. </p> <p> </p> <table> <tr> <td><span class="docbook_option">local_from_suffix</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> See <span class="docbook_option">local_from_prefix</span> above. </p> <p> </p> <table> <tr> <td><span class="docbook_option">local_interfaces</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This option controls which network interfaces are used by the daemon for listening; they are also used to identify the local host when routing. Chapter <a href="ch13.html" title="13. Starting the daemon and the use of network interfaces">13</a> contains a full description of this option and the related options <span class="docbook_option">daemon_smtp_ports</span>, <span class="docbook_option">extra_local_interfaces</span>, <span class="docbook_option">hosts_treat_as_local</span>, and <span class="docbook_option">tls_on_connect_ports</span>. The default value for <span class="docbook_option">local_interfaces</span> is </p> <div class="docbook_literallayout"><pre> local_interfaces = 0.0.0.0 </pre></div> <p> when Exim is built without IPv6 support; otherwise it is </p> <div class="docbook_literallayout"><pre> local_interfaces = <; ::0 ; 0.0.0.0 </pre></div> <p> </p> <table> <tr> <td><span class="docbook_option">local_scan_timeout</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">5m</span> </td> </tr> </table> <p> This timeout applies to the <span class="docbook_function">local_scan()</span> function (see chapter <a href="ch44.html" title="44. Adding a local scan function to Exim">44</a>). Zero means “no timeout”. If the timeout is exceeded, the incoming message is rejected with a temporary error if it is an SMTP message. For a non-SMTP message, the message is dropped and Exim ends with a non-zero code. The incident is logged on the main and reject logs. </p> <p> </p> <table> <tr> <td><span class="docbook_option">local_sender_retain</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> When a message is submitted locally (that is, not over a TCP/IP connection) by an untrusted user, Exim removes any existing <span class="docbook_emphasis">Sender:</span> header line. If you do not want this to happen, you must set <span class="docbook_option">local_sender_retain</span>, and you must also set <span class="docbook_option">local_from_check</span> to be false (Exim will complain if you do not). See also the ACL modifier <code class="docbook_literal">control = suppress_local_fixups</code>. Section <a href="ch46.html#SECTthesenhea" title="46. Message processing">46.16</a> has more details about <span class="docbook_emphasis">Sender:</span> processing. </p> <p> </p> <table> <tr> <td><span class="docbook_option">localhost_number</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> Exim’s message ids are normally unique only within the local host. If uniqueness among a set of hosts is required, each host must set a different value for the <span class="docbook_option">localhost_number</span> option. The string is expanded immediately after reading the configuration file (so that a number can be computed from the host name, for example) and the result of the expansion must be a number in the range 0–16 (or 0–10 on operating systems with case-insensitive file systems). This is available in subsequent string expansions via the variable $localhost_number. When <span class="docbook_option">localhost_number is set</span>, the final two characters of the message id, instead of just being a fractional part of the time, are computed from the time and the local host number as described in section <a href="ch03.html#SECTmessiden" title="3. How Exim receives and delivers mail">3.4</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">log_file_path</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">set at compile time</span> </td> </tr> </table> <p> This option sets the path which is used to determine the names of Exim’s log files, or indicates that logging is to be to syslog, or both. It is expanded when Exim is entered, so it can, for example, contain a reference to the host name. If no specific path is set for the log files at compile or run time, they are written in a sub-directory called <span class="docbook_filename">log</span> in Exim’s spool directory. Chapter <a href="ch51.html" title="51. Log files">51</a> contains further details about Exim’s logging, and section <a href="ch51.html#SECTwhelogwri" title="51. Log files">51.1</a> describes how the contents of <span class="docbook_option">log_file_path</span> are used. If this string is fixed at your installation (contains no expansion variables) it is recommended that you do not set this option in the configuration file, but instead supply the path using LOG_FILE_PATH in <span class="docbook_filename">Local/Makefile</span> so that it is available to Exim for logging errors detected early on – in particular, failure to read the configuration file. </p> <p> </p> <table> <tr> <td><span class="docbook_option">log_selector</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option can be used to reduce or increase the number of things that Exim writes to its log files. Its argument is made up of names preceded by plus or minus characters. For example: </p> <div class="docbook_literallayout"><pre> log_selector = +arguments -retry_defer </pre></div> <p> A list of possible names and what they control is given in the chapter on logging, in section <a href="ch51.html#SECTlogselector" title="51. Log files">51.15</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">log_timezone</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> By default, the timestamps on log lines are in local time without the timezone. This means that if your timezone changes twice a year, the timestamps in log lines are ambiguous for an hour when the clocks go back. One way of avoiding this problem is to set the timezone to UTC. An alternative is to set <span class="docbook_option">log_timezone</span> true. This turns on the addition of the timezone offset to timestamps in log lines. Turning on this option can add quite a lot to the size of log files because each line is extended by 6 characters. Note that the $tod_log variable contains the log timestamp without the zone, but there is another variable called $tod_zone that contains just the timezone offset. </p> <p> </p> <table> <tr> <td><span class="docbook_option">lookup_open_max</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">25</span> </td> </tr> </table> <p> This option limits the number of simultaneously open files for single-key lookups that use regular files (that is, <span class="docbook_command">lsearch</span>, <span class="docbook_command">dbm</span>, and <span class="docbook_command">cdb</span>). Exim normally keeps these files open during routing, because often the same file is required several times. If the limit is reached, Exim closes the least recently used file. Note that if you are using the <span class="docbook_emphasis">ndbm</span> library, it actually opens two files for each logical DBM database, though it still counts as one for the purposes of <span class="docbook_option">lookup_open_max</span>. If you are getting “too many open files” errors with NDBM, you need to reduce the value of <span class="docbook_option">lookup_open_max</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">max_username_length</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> Some operating systems are broken in that they truncate long arguments to <span class="docbook_function">getpwnam()</span> to eight characters, instead of returning “no such user”. If this option is set greater than zero, any attempt to call <span class="docbook_function">getpwnam()</span> with an argument that is longer behaves as if <span class="docbook_function">getpwnam()</span> failed. </p> <p> </p> <table> <tr> <td><span class="docbook_option">message_body_newlines</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">bool</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> By default, newlines in the message body are replaced by spaces when setting the $message_body and $message_body_end expansion variables. If this option is set true, this no longer happens. </p> <p> </p> <table> <tr> <td><span class="docbook_option">message_body_visible</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">500</span> </td> </tr> </table> <p> This option specifies how much of a message’s body is to be included in the $message_body and $message_body_end expansion variables. </p> <p> </p> <table> <tr> <td><span class="docbook_option">message_id_header_domain</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> If this option is set, the string is expanded and used as the right hand side (domain) of the <span class="docbook_emphasis">Message-ID:</span> header that Exim creates if a locally-originated incoming message does not have one. “Locally-originated” means “not received over TCP/IP.” Otherwise, the primary host name is used. Only letters, digits, dot and hyphen are accepted; any other characters are replaced by hyphens. If the expansion is forced to fail, or if the result is an empty string, the option is ignored. </p> <p> </p> <table> <tr> <td><span class="docbook_option">message_id_header_text</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> If this variable is set, the string is expanded and used to augment the text of the <span class="docbook_emphasis">Message-id:</span> header that Exim creates if a locally-originated incoming message does not have one. The text of this header is required by RFC 2822 to take the form of an address. By default, Exim uses its internal message id as the local part, and the primary host name as the domain. If this option is set, it is expanded, and provided the expansion is not forced to fail, and does not yield an empty string, the result is inserted into the header immediately before the @, separated from the internal message id by a dot. Any characters that are illegal in an address are automatically converted into hyphens. This means that variables such as $tod_log can be used, because the spaces and colons will become hyphens. </p> <p> </p> <table> <tr> <td><span class="docbook_option">message_logs</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> If this option is turned off, per-message log files are not created in the <span class="docbook_filename">msglog</span> spool sub-directory. This reduces the amount of disk I/O required by Exim, by reducing the number of files involved in handling a message from a minimum of four (header spool file, body spool file, delivery journal, and per-message log) to three. The other major I/O activity is Exim’s main log, which is not affected by this option. </p> <p> </p> <table> <tr> <td><span class="docbook_option">message_size_limit</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">50M</span> </td> </tr> </table> <p> This option limits the maximum size of message that Exim will process. The value is expanded for each incoming connection so, for example, it can be made to depend on the IP address of the remote host for messages arriving via TCP/IP. After expansion, the value must be a sequence of decimal digits, optionally followed by K or M. </p> <p> <span class="docbook_emphasis">Note</span>: This limit cannot be made to depend on a message’s sender or any other properties of an individual message, because it has to be advertised in the server’s response to EHLO. String expansion failure causes a temporary error. A value of zero means no limit, but its use is not recommended. See also <span class="docbook_option">bounce_return_size_limit</span>. </p> <p> Incoming SMTP messages are failed with a 552 error if the limit is exceeded; locally-generated messages either get a stderr message or a delivery failure message to the sender, depending on the <span class="docbook_option">-oe</span> setting. Rejection of an oversized message is logged in both the main and the reject logs. See also the generic transport option <span class="docbook_option">message_size_limit</span>, which limits the size of message that an individual transport can process. </p> <p> If you use a virus-scanner and set this option to to a value larger than the 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 probably safest to just set it to a little larger than this value. Eg, with a default Exim message size of 50M and a default ClamAV StreamMaxLength of 10M, some problems may result. </p> <p> A value of 0 will disable size limit checking; Exim will still advertise the SIZE extension in an EHLO response, but without a limit, so as to permit SMTP clients to still indicate the message size along with the MAIL verb. </p> <p> </p> <table> <tr> <td><span class="docbook_option">move_frozen_messages</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> This option, which is available only if Exim has been built with the setting </p> <div class="docbook_literallayout"><pre> SUPPORT_MOVE_FROZEN_MESSAGES=yes </pre></div> <p> in <span class="docbook_filename">Local/Makefile</span>, causes frozen messages and their message logs to be moved from the <span class="docbook_filename">input</span> and <span class="docbook_filename">msglog</span> directories on the spool to <span class="docbook_filename">Finput</span> and <span class="docbook_filename">Fmsglog</span>, respectively. There is currently no support in Exim or the standard utilities for handling such moved messages, and they do not show up in lists generated by <span class="docbook_option">-bp</span> or by the Exim monitor. </p> <p> </p> <table> <tr> <td><span class="docbook_option">mua_wrapper</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> Setting this option true causes Exim to run in a very restrictive mode in which it passes messages synchronously to a smart host. Chapter <a href="ch50.html" title="50. Using Exim as a non-queueing client">50</a> contains a full description of this facility. </p> <p> </p> <table> <tr> <td><span class="docbook_option">mysql_servers</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option provides a list of MySQL servers and associated connection data, to be used in conjunction with <span class="docbook_command">mysql</span> lookups (see section <a href="ch09.html#SECID72" title="9. File and database lookups">9.21</a>). The option is available only if Exim has been built with MySQL support. </p> <p> </p> <table> <tr> <td><span class="docbook_option">never_users</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option is expanded just once, at the start of Exim’s processing. Local message deliveries are normally run in processes that are setuid to the recipient, and remote deliveries are normally run under Exim’s own uid and gid. It is usually desirable to prevent any deliveries from running as root, as a safety precaution. </p> <p> When Exim is built, an option called FIXED_NEVER_USERS can be set to a list of users that must not be used for local deliveries. This list is fixed in the binary and cannot be overridden by the configuration file. By default, it contains just the single user name “root”. The <span class="docbook_option">never_users</span> runtime option can be used to add more users to the fixed list. </p> <p> If a message is to be delivered as one of the users on the fixed list or the <span class="docbook_option">never_users</span> list, an error occurs, and delivery is deferred. A common example is </p> <div class="docbook_literallayout"><pre> never_users = root:daemon:bin </pre></div> <p> Including root is redundant if it is also on the fixed list, but it does no harm. This option overrides the <span class="docbook_option">pipe_as_creator</span> option of the <span class="docbook_command">pipe</span> transport driver. </p> <p> </p> <table> <tr> <td><span class="docbook_option">openssl_options</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">+no_sslv2</span> </td> </tr> </table> <p> This option allows an administrator to adjust the SSL options applied by OpenSSL to connections. It is given as a space-separated list of items, each one to be +added or -subtracted from the current value. </p> <p> This option is only available if Exim is built against OpenSSL. The values available for this option vary according to the age of your OpenSSL install. The “all” value controls a subset of flags which are available, typically the bug workaround options. The <span class="docbook_emphasis">SSL_CTX_set_options</span> man page will list the values known on your system and Exim should support all the “bug workaround” options and many of the “modifying” options. The Exim names lose the leading “SSL_OP_” and are lower-cased. </p> <p> Note that adjusting the options can have severe impact upon the security of SSL as used by Exim. It is possible to disable safety checks and shoot yourself in the foot in various unpleasant ways. This option should not be adjusted lightly. An unrecognised item will be detected at startup, by invoking Exim with the <span class="docbook_option">-bV</span> flag. </p> <p class="changed"> Historical note: prior to release 4.80, Exim defaulted this value to "+dont_insert_empty_fragments", which may still be needed for compatibility with some clients, but which lowers security by increasing exposure to some now infamous attacks. </p> <p> An example: </p> <div class="docbook_literallayout"><pre> # Make both old MS and old Eudora happy: openssl_options = -all +microsoft_big_sslv3_buffer \ +dont_insert_empty_fragments </pre></div> <p> Possible options may include: </p> <ul> <li> <p> <code class="docbook_literal">all</code> </p> </li> <li> <p> <code class="docbook_literal">allow_unsafe_legacy_renegotiation</code> </p> </li> <li> <p> <code class="docbook_literal">cipher_server_preference</code> </p> </li> <li> <p> <code class="docbook_literal">dont_insert_empty_fragments</code> </p> </li> <li> <p> <code class="docbook_literal">ephemeral_rsa</code> </p> </li> <li> <p> <code class="docbook_literal">legacy_server_connect</code> </p> </li> <li> <p> <code class="docbook_literal">microsoft_big_sslv3_buffer</code> </p> </li> <li> <p> <code class="docbook_literal">microsoft_sess_id_bug</code> </p> </li> <li> <p> <code class="docbook_literal">msie_sslv2_rsa_padding</code> </p> </li> <li> <p> <code class="docbook_literal">netscape_challenge_bug</code> </p> </li> <li> <p> <code class="docbook_literal">netscape_reuse_cipher_change_bug</code> </p> </li> <li> <p> <code class="docbook_literal">no_compression</code> </p> </li> <li> <p> <code class="docbook_literal">no_session_resumption_on_renegotiation</code> </p> </li> <li> <p> <code class="docbook_literal">no_sslv2</code> </p> </li> <li> <p> <code class="docbook_literal">no_sslv3</code> </p> </li> <li> <p> <code class="docbook_literal">no_ticket</code> </p> </li> <li> <p> <code class="docbook_literal">no_tlsv1</code> </p> </li> <li> <p> <code class="docbook_literal">no_tlsv1_1</code> </p> </li> <li> <p> <code class="docbook_literal">no_tlsv1_2</code> </p> </li> <li> <p> <code class="docbook_literal">single_dh_use</code> </p> </li> <li> <p> <code class="docbook_literal">single_ecdh_use</code> </p> </li> <li> <p> <code class="docbook_literal">ssleay_080_client_dh_bug</code> </p> </li> <li> <p> <code class="docbook_literal">sslref2_reuse_cert_type_bug</code> </p> </li> <li> <p> <code class="docbook_literal">tls_block_padding_bug</code> </p> </li> <li> <p> <code class="docbook_literal">tls_d5_bug</code> </p> </li> <li> <p> <code class="docbook_literal">tls_rollback_bug</code> </p> </li> </ul> <p> </p> <table> <tr> <td><span class="docbook_option">oracle_servers</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option provides a list of Oracle servers and associated connection data, to be used in conjunction with <span class="docbook_command">oracle</span> lookups (see section <a href="ch09.html#SECID72" title="9. File and database lookups">9.21</a>). The option is available only if Exim has been built with Oracle support. </p> <p> </p> <table> <tr> <td><span class="docbook_option">percent_hack_domains</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">domain list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> The “percent hack” is the convention whereby a local part containing a percent sign is re-interpreted as a new email address, with the percent replaced by @. This is sometimes called “source routing”, though that term is also applied to RFC 2822 addresses that begin with an @ character. If this option is set, Exim implements the percent facility for those domains listed, but no others. This happens before an incoming SMTP address is tested against an ACL. </p> <p> <span class="docbook_emphasis">Warning</span>: The “percent hack” has often been abused by people who are trying to get round relaying restrictions. For this reason, it is best avoided if at all possible. Unfortunately, a number of less security-conscious MTAs implement it unconditionally. If you are running Exim on a gateway host, and routing mail through to internal MTAs without processing the local parts, it is a good idea to reject recipient addresses with percent characters in their local parts. Exim’s default configuration does this. </p> <p> </p> <table> <tr> <td><span class="docbook_option">perl_at_start</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> This option is available only when Exim is built with an embedded Perl interpreter. See chapter <a href="ch12.html" title="12. Embedded Perl">12</a> for details of its use. </p> <p> </p> <table> <tr> <td><span class="docbook_option">perl_startup</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option is available only when Exim is built with an embedded Perl interpreter. See chapter <a href="ch12.html" title="12. Embedded Perl">12</a> for details of its use. </p> <p> </p> <table> <tr> <td><span class="docbook_option">pgsql_servers</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option provides a list of PostgreSQL servers and associated connection data, to be used in conjunction with <span class="docbook_command">pgsql</span> lookups (see section <a href="ch09.html#SECID72" title="9. File and database lookups">9.21</a>). The option is available only if Exim has been built with PostgreSQL support. </p> <p> </p> <table> <tr> <td><span class="docbook_option">pid_file_path</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">set at compile time</span> </td> </tr> </table> <p> This option sets the name of the file to which the Exim daemon writes its process id. The string is expanded, so it can contain, for example, references to the host name: </p> <div class="docbook_literallayout"><pre> pid_file_path = /var/log/$primary_hostname/exim.pid </pre></div> <p> If no path is set, the pid is written to the file <span class="docbook_filename">exim-daemon.pid</span> in Exim’s spool directory. The value set by the option can be overridden by the <span class="docbook_option">-oP</span> command line option. A pid file is not written if a “non-standard” daemon is run by means of the <span class="docbook_option">-oX</span> option, unless a path is explicitly supplied by <span class="docbook_option">-oP</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">pipelining_advertise_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis"></span> </td> </tr> </table> <p> This option can be used to suppress the advertisement of the SMTP PIPELINING extension to specific hosts. See also the <span class="docbook_emphasis">no_pipelining</span> control in section <a href="ch42.html#SECTcontrols" title="42. Access control lists">42.21</a>. When PIPELINING is not advertised and <span class="docbook_option">smtp_enforce_sync</span> is true, an Exim server enforces strict synchronization for each SMTP command and response. When PIPELINING is advertised, Exim assumes that clients will use it; “out of order” commands that are “expected” do not count as protocol errors (see <span class="docbook_option">smtp_max_synprot_errors</span>). </p> <p> </p> <table> <tr> <td><span class="docbook_option">preserve_message_logs</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If this option is set, message log files are not deleted when messages are completed. Instead, they are moved to a sub-directory of the spool directory called <span class="docbook_filename">msglog.OLD</span>, where they remain available for statistical or debugging purposes. This is a dangerous option to set on systems with any appreciable volume of mail. Use with care! </p> <p> </p> <table> <tr> <td><span class="docbook_option">primary_hostname</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This specifies the name of the current host. It is used in the default EHLO or HELO command for outgoing SMTP messages (changeable via the <span class="docbook_option">helo_data</span> option in the <span class="docbook_command">smtp</span> transport), and as the default for <span class="docbook_option">qualify_domain</span>. The value is also used by default in some SMTP response messages from an Exim server. This can be changed dynamically by setting <span class="docbook_option">smtp_active_hostname</span>. </p> <p> If <span class="docbook_option">primary_hostname</span> is not set, Exim calls <span class="docbook_function">uname()</span> to find the host name. If this fails, Exim panics and dies. If the name returned by <span class="docbook_function">uname()</span> contains only one component, Exim passes it to <span class="docbook_function">gethostbyname()</span> (or <span class="docbook_function">getipnodebyname()</span> when available) in order to obtain the fully qualified version. The variable $primary_hostname contains the host name, whether set explicitly by this option, or defaulted. </p> <p> </p> <table> <tr> <td><span class="docbook_option">print_topbitchars</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> By default, Exim considers only those characters whose codes lie in the range 32–126 to be printing characters. In a number of circumstances (for example, when writing log entries) non-printing characters are converted into escape sequences, primarily to avoid messing up the layout. If <span class="docbook_option">print_topbitchars</span> is set, code values of 128 and above are also considered to be printing characters. </p> <p> This option also affects the header syntax checks performed by the <span class="docbook_command">autoreply</span> transport, and whether Exim uses RFC 2047 encoding of the user’s full name when constructing From: and Sender: addresses (as described in section <a href="ch46.html#SECTconstr" title="46. Message processing">46.18</a>). Setting this option can cause Exim to generate eight bit message headers that do not conform to the standards. </p> <p> </p> <table> <tr> <td><span class="docbook_option">process_log_path</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option sets the name of the file to which an Exim process writes its “process log” when sent a USR1 signal. This is used by the <span class="docbook_emphasis">exiwhat</span> utility script. If this option is unset, the file called <span class="docbook_filename">exim-process.info</span> in Exim’s spool directory is used. The ability to specify the name explicitly can be useful in environments where two different Exims are running, using different spool directories. </p> <p> </p> <table> <tr> <td><span class="docbook_option">prod_requires_admin</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> The <span class="docbook_option">-M</span>, <span class="docbook_option">-R</span>, and <span class="docbook_option">-q</span> command-line options require the caller to be an admin user unless <span class="docbook_option">prod_requires_admin</span> is set false. See also <span class="docbook_option">queue_list_requires_admin</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">qualify_domain</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This option specifies the domain name that is added to any envelope sender addresses that do not have a domain qualification. It also applies to recipient addresses if <span class="docbook_option">qualify_recipient</span> is not set. Unqualified addresses are accepted by default only for locally-generated messages. Qualification is also applied to addresses in header lines such as <span class="docbook_emphasis">From:</span> and <span class="docbook_emphasis">To:</span> for locally-generated messages, unless the <span class="docbook_option">-bnq</span> command line option is used. </p> <p> Messages from external sources must always contain fully qualified addresses, unless the sending host matches <span class="docbook_option">sender_unqualified_hosts</span> or <span class="docbook_option">recipient_unqualified_hosts</span> (as appropriate), in which case incoming addresses are qualified with <span class="docbook_option">qualify_domain</span> or <span class="docbook_option">qualify_recipient</span> as necessary. Internally, Exim always works with fully qualified envelope addresses. If <span class="docbook_option">qualify_domain</span> is not set, it defaults to the <span class="docbook_option">primary_hostname</span> value. </p> <p> </p> <table> <tr> <td><span class="docbook_option">qualify_recipient</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This option allows you to specify a different domain for qualifying recipient addresses to the one that is used for senders. See <span class="docbook_option">qualify_domain</span> above. </p> <p> </p> <table> <tr> <td><span class="docbook_option">queue_domains</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">domain list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option lists domains for which immediate delivery is not required. A delivery process is started whenever a message is received, but only those domains that do not match are processed. All other deliveries wait until the next queue run. See also <span class="docbook_option">hold_domains</span> and <span class="docbook_option">queue_smtp_domains</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">queue_list_requires_admin</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> The <span class="docbook_option">-bp</span> command-line option, which lists the messages that are on the queue, requires the caller to be an admin user unless <span class="docbook_option">queue_list_requires_admin</span> is set false. See also <span class="docbook_option">prod_requires_admin</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">queue_only</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If <span class="docbook_option">queue_only</span> is set, a delivery process is not automatically started whenever a message is received. Instead, the message waits on the queue for the next queue run. Even if <span class="docbook_option">queue_only</span> is false, incoming messages may not get delivered immediately when certain conditions (such as heavy load) occur. </p> <p> The <span class="docbook_option">-odq</span> command line has the same effect as <span class="docbook_option">queue_only</span>. The <span class="docbook_option">-odb</span> and <span class="docbook_option">-odi</span> command line options override <span class="docbook_option">queue_only</span> unless <span class="docbook_option">queue_only_override</span> is set false. See also <span class="docbook_option">queue_only_file</span>, <span class="docbook_option">queue_only_load</span>, and <span class="docbook_option">smtp_accept_queue</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">queue_only_file</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option can be set to a colon-separated list of absolute path names, each one optionally preceded by “smtp”. When Exim is receiving a message, it tests for the existence of each listed path using a call to <span class="docbook_function">stat()</span>. For each path that exists, the corresponding queueing option is set. For paths with no prefix, <span class="docbook_option">queue_only</span> is set; for paths prefixed by “smtp”, <span class="docbook_option">queue_smtp_domains</span> is set to match all domains. So, for example, </p> <div class="docbook_literallayout"><pre> queue_only_file = smtp/some/file </pre></div> <p> causes Exim to behave as if <span class="docbook_option">queue_smtp_domains</span> were set to “” whenever <span class="docbook_filename">/some/file</span> exists. </p> <p> </p> <table> <tr> <td><span class="docbook_option">queue_only_load</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">fixed-point</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> If the system load average is higher than this value, incoming messages from all sources are queued, and no automatic deliveries are started. If this happens during local or remote SMTP input, all subsequent messages received on the same SMTP connection are queued by default, whatever happens to the load in the meantime, but this can be changed by setting <span class="docbook_option">queue_only_load_latch</span> false. </p> <p> Deliveries will subsequently be performed by queue runner processes. This option has no effect on ancient operating systems on which Exim cannot determine the load average. See also <span class="docbook_option">deliver_queue_load_max</span> and <span class="docbook_option">smtp_load_reserve</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">queue_only_load_latch</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> When this option is true (the default), once one message has been queued because the load average is higher than the value set by <span class="docbook_option">queue_only_load</span>, all subsequent messages received on the same SMTP connection are also queued. This is a deliberate choice; even though the load average may fall below the threshold, it doesn’t seem right to deliver later messages on the same connection when not delivering earlier ones. However, there are special circumstances such as very long-lived connections from scanning appliances where this is not the best strategy. In such cases, <span class="docbook_option">queue_only_load_latch</span> should be set false. This causes the value of the load average to be re-evaluated for each message. </p> <p> </p> <table> <tr> <td><span class="docbook_option">queue_only_override</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> When this option is true, the <span class="docbook_option">-od</span><span class="docbook_emphasis">x</span> command line options override the setting of <span class="docbook_option">queue_only</span> or <span class="docbook_option">queue_only_file</span> in the configuration file. If <span class="docbook_option">queue_only_override</span> is set false, the <span class="docbook_option">-od</span><span class="docbook_emphasis">x</span> options cannot be used to override; they are accepted, but ignored. </p> <p> </p> <table> <tr> <td><span class="docbook_option">queue_run_in_order</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If this option is set, queue runs happen in order of message arrival instead of in an arbitrary order. For this to happen, a complete list of the entire queue must be set up before the deliveries start. When the queue is all held in a single directory (the default), a single list is created for both the ordered and the non-ordered cases. However, if <span class="docbook_option">split_spool_directory</span> is set, a single list is not created when <span class="docbook_option">queue_run_in_order</span> is false. In this case, the sub-directories are processed one at a time (in a random order), and this avoids setting up one huge list for the whole queue. Thus, setting <span class="docbook_option">queue_run_in_order</span> with <span class="docbook_option">split_spool_directory</span> may degrade performance when the queue is large, because of the extra work in setting up the single, large list. In most situations, <span class="docbook_option">queue_run_in_order</span> should not be set. </p> <p> </p> <table> <tr> <td><span class="docbook_option">queue_run_max</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">5</span> </td> </tr> </table> <p> This controls the maximum number of queue runner processes that an Exim daemon can run simultaneously. This does not mean that it starts them all at once, but rather that if the maximum number are still running when the time comes to start another one, it refrains from starting another one. This can happen with very large queues and/or very sluggish deliveries. This option does not, however, interlock with other processes, so additional queue runners can be started by other means, or by killing and restarting the daemon. </p> <p> Setting this option to zero does not suppress queue runs; rather, it disables the limit, allowing any number of simultaneous queue runner processes to be run. If you do not want queue runs to occur, omit the <span class="docbook_option">-q</span><span class="docbook_emphasis">xx</span> setting on the daemon’s command line. </p> <p> </p> <table> <tr> <td><span class="docbook_option">queue_smtp_domains</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">domain list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> When this option is set, a delivery process is started whenever a message is received, routing is performed, and local deliveries take place. However, if any SMTP deliveries are required for domains that match <span class="docbook_option">queue_smtp_domains</span>, they are not immediately delivered, but instead the message waits on the queue for the next queue run. Since routing of the message has taken place, Exim knows to which remote hosts it must be delivered, and so when the queue run happens, multiple messages for the same host are delivered over a single SMTP connection. The <span class="docbook_option">-odqs</span> command line option causes all SMTP deliveries to be queued in this way, and is equivalent to setting <span class="docbook_option">queue_smtp_domains</span> to “”. See also <span class="docbook_option">hold_domains</span> and <span class="docbook_option">queue_domains</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">receive_timeout</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">0s</span> </td> </tr> </table> <p> This option sets the timeout for accepting a non-SMTP message, that is, the maximum time that Exim waits when reading a message on the standard input. If the value is zero, it will wait for ever. This setting is overridden by the <span class="docbook_option">-or</span> command line option. The timeout for incoming SMTP messages is controlled by <span class="docbook_option">smtp_receive_timeout</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">received_header_text</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This string defines the contents of the <span class="docbook_emphasis">Received:</span> message header that is added to each message, except for the timestamp, which is automatically added on at the end (preceded by a semicolon). The string is expanded each time it is used. If the expansion yields an empty string, no <span class="docbook_emphasis">Received:</span> header line is added to the message. Otherwise, the string should start with the text “Received:” and conform to the RFC 2822 specification for <span class="docbook_emphasis">Received:</span> header lines. The default setting is: </p> <div class="docbook_literallayout"><pre> received_header_text = Received: \ ${if def:sender_rcvhost {from $sender_rcvhost\n\t}\ {${if def:sender_ident \ {from ${quote_local_part:$sender_ident} }}\ ${if def:sender_helo_name {(helo=$sender_helo_name)\n\t}}}}\ by $primary_hostname \ ${if def:received_protocol {with $received_protocol}} \ ${if def:tls_cipher {($tls_cipher)\n\t}}\ (Exim $version_number)\n\t\ ${if def:sender_address \ {(envelope-from <$sender_address>)\n\t}}\ id $message_exim_id\ ${if def:received_for {\n\tfor $received_for}} </pre></div> <p> The reference to the TLS cipher is omitted when Exim is built without TLS support. The use of conditional expansions ensures that this works for both locally generated messages and messages received from remote hosts, giving header lines such as the following: </p> <div class="docbook_literallayout"><pre> Received: from scrooge.carol.example ([192.168.12.25] ident=root) by marley.carol.example with esmtp (Exim 4.00) (envelope-from <bob@carol.example>) id 16IOWa-00019l-00 for chas@dickens.example; Tue, 25 Dec 2001 14:43:44 +0000 Received: by scrooge.carol.example with local (Exim 4.00) id 16IOWW-000083-00; Tue, 25 Dec 2001 14:43:41 +0000 </pre></div> <p> Until the body of the message has been received, the timestamp is the time when the message started to be received. Once the body has arrived, and all policy checks have taken place, the timestamp is updated to the time at which the message was accepted. </p> <p> </p> <table> <tr> <td><span class="docbook_option">received_headers_max</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">30</span> </td> </tr> </table> <p> When a message is to be delivered, the number of <span class="docbook_emphasis">Received:</span> headers is counted, and if it is greater than this parameter, a mail loop is assumed to have occurred, the delivery is abandoned, and an error message is generated. This applies to both local and remote deliveries. </p> <p> </p> <table> <tr> <td><span class="docbook_option">recipient_unqualified_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option lists those hosts from which Exim is prepared to accept unqualified recipient addresses in message envelopes. The addresses are made fully qualified by the addition of the <span class="docbook_option">qualify_recipient</span> value. This option also affects message header lines. Exim does not reject unqualified recipient addresses in headers, but it qualifies them only if the message came from a host that matches <span class="docbook_option">recipient_unqualified_hosts</span>, or if the message was submitted locally (not using TCP/IP), and the <span class="docbook_option">-bnq</span> option was not set. </p> <p> </p> <table> <tr> <td><span class="docbook_option">recipients_max</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> If this option is set greater than zero, it specifies the maximum number of original recipients for any message. Additional recipients that are generated by aliasing or forwarding do not count. SMTP messages get a 452 response for all recipients over the limit; earlier recipients are delivered as normal. Non-SMTP messages with too many recipients are failed, and no deliveries are done. </p> <p> <span class="docbook_emphasis">Note</span>: The RFCs specify that an SMTP server should accept at least 100 RCPT commands in a single message. </p> <p> </p> <table> <tr> <td><span class="docbook_option">recipients_max_reject</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If this option is set true, Exim rejects SMTP messages containing too many recipients by giving 552 errors to the surplus RCPT commands, and a 554 error to the eventual DATA command. Otherwise (the default) it gives a 452 error to the surplus RCPT commands and accepts the message on behalf of the initial set of recipients. The remote server should then re-send the message for the remaining recipients at a later time. </p> <p> </p> <table> <tr> <td><span class="docbook_option">remote_max_parallel</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">2</span> </td> </tr> </table> <p> This option controls parallel delivery of one message to a number of remote hosts. If the value is less than 2, parallel delivery is disabled, and Exim does all the remote deliveries for a message one by one. Otherwise, if a single message has to be delivered to more than one remote host, or if several copies have to be sent to the same remote host, up to <span class="docbook_option">remote_max_parallel</span> deliveries are done simultaneously. If more than <span class="docbook_option">remote_max_parallel</span> deliveries are required, the maximum number of processes are started, and as each one finishes, another is begun. The order of starting processes is the same as if sequential delivery were being done, and can be controlled by the <span class="docbook_option">remote_sort_domains</span> option. If parallel delivery takes place while running with debugging turned on, the debugging output from each delivery process is tagged with its process id. </p> <p> This option controls only the maximum number of parallel deliveries for one message in one Exim delivery process. Because Exim has no central queue manager, there is no way of controlling the total number of simultaneous deliveries if the configuration allows a delivery attempt as soon as a message is received. </p> <p> If you want to control the total number of deliveries on the system, you need to set the <span class="docbook_option">queue_only</span> option. This ensures that all incoming messages are added to the queue without starting a delivery process. Then set up an Exim daemon to start queue runner processes at appropriate intervals (probably fairly often, for example, every minute), and limit the total number of queue runners by setting the <span class="docbook_option">queue_run_max</span> parameter. Because each queue runner delivers only one message at a time, the maximum number of deliveries that can then take place at once is <span class="docbook_option">queue_run_max</span> multiplied by <span class="docbook_option">remote_max_parallel</span>. </p> <p> If it is purely remote deliveries you want to control, use <span class="docbook_option">queue_smtp_domains</span> instead of <span class="docbook_option">queue_only</span>. This has the added benefit of doing the SMTP routing before queueing, so that several messages for the same host will eventually get delivered down the same connection. </p> <p> </p> <table> <tr> <td><span class="docbook_option">remote_sort_domains</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">domain list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> When there are a number of remote deliveries for a message, they are sorted by domain into the order given by this list. For example, </p> <div class="docbook_literallayout"><pre> remote_sort_domains = .cam.ac.uk:.uk </pre></div> <p> would attempt to deliver to all addresses in the <span class="docbook_emphasis">cam.ac.uk</span> domain first, then to those in the <span class="docbook_option">uk</span> domain, then to any others. </p> <p> </p> <table> <tr> <td><span class="docbook_option">retry_data_expire</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">7d</span> </td> </tr> </table> <p> This option sets a “use before” time on retry information in Exim’s hints database. Any older retry data is ignored. This means that, for example, once a host has not been tried for 7 days, Exim behaves as if it has no knowledge of past failures. </p> <p> </p> <table> <tr> <td><span class="docbook_option">retry_interval_max</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">24h</span> </td> </tr> </table> <p> Chapter <a href="ch32.html" title="32. Retry configuration">32</a> describes Exim’s mechanisms for controlling the intervals between delivery attempts for messages that cannot be delivered straight away. This option sets an overall limit to the length of time between retries. It cannot be set greater than 24 hours; any attempt to do so forces the default value. </p> <p> </p> <table> <tr> <td><span class="docbook_option">return_path_remove</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> RFC 2821, section 4.4, states that an SMTP server must insert a <span class="docbook_emphasis">Return-path:</span> header line into a message when it makes a “final delivery”. The <span class="docbook_emphasis">Return-path:</span> header preserves the sender address as received in the MAIL command. This description implies that this header should not be present in an incoming message. If <span class="docbook_option">return_path_remove</span> is true, any existing <span class="docbook_emphasis">Return-path:</span> headers are removed from messages at the time they are received. Exim’s transports have options for adding <span class="docbook_emphasis">Return-path:</span> headers at the time of delivery. They are normally used only for final local deliveries. </p> <p> </p> <table> <tr> <td><span class="docbook_option">return_size_limit</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">100K</span> </td> </tr> </table> <p> This option is an obsolete synonym for <span class="docbook_option">bounce_return_size_limit</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">rfc1413_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis"></span> </td> </tr> </table> <p> RFC 1413 identification calls are made to any client host which matches an item in the list. </p> <p> </p> <table> <tr> <td><span class="docbook_option">rfc1413_query_timeout</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">5s</span> </td> </tr> </table> <p> This sets the timeout on RFC 1413 identification calls. If it is set to zero, no RFC 1413 calls are ever made. </p> <p> </p> <table> <tr> <td><span class="docbook_option">sender_unqualified_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option lists those hosts from which Exim is prepared to accept unqualified sender addresses. The addresses are made fully qualified by the addition of <span class="docbook_option">qualify_domain</span>. This option also affects message header lines. Exim does not reject unqualified addresses in headers that contain sender addresses, but it qualifies them only if the message came from a host that matches <span class="docbook_option">sender_unqualified_hosts</span>, or if the message was submitted locally (not using TCP/IP), and the <span class="docbook_option">-bnq</span> option was not set. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_accept_keepalive</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> This option controls the setting of the SO_KEEPALIVE option on incoming TCP/IP socket connections. When set, it causes the kernel to probe idle connections periodically, by sending packets with “old” sequence numbers. The other end of the connection should send an acknowledgment if the connection is still okay or a reset if the connection has been aborted. The reason for doing this is that it has the beneficial effect of freeing up certain types of connection that can get stuck when the remote host is disconnected without tidying up the TCP/IP call properly. The keepalive mechanism takes several hours to detect unreachable hosts. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_accept_max</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">20</span> </td> </tr> </table> <p> This option specifies the maximum number of simultaneous incoming SMTP calls that Exim will accept. It applies only to the listening daemon; there is no control (in Exim) when incoming SMTP is being handled by <span class="docbook_emphasis">inetd</span>. If the value is set to zero, no limit is applied. However, it is required to be non-zero if either <span class="docbook_option">smtp_accept_max_per_host</span> or <span class="docbook_option">smtp_accept_queue</span> is set. See also <span class="docbook_option">smtp_accept_reserve</span> and <span class="docbook_option">smtp_load_reserve</span>. </p> <p> A new SMTP connection is immediately rejected if the <span class="docbook_option">smtp_accept_max</span> limit has been reached. If not, Exim first checks <span class="docbook_option">smtp_accept_max_per_host</span>. If that limit has not been reached for the client host, <span class="docbook_option">smtp_accept_reserve</span> and <span class="docbook_option">smtp_load_reserve</span> are then checked before accepting the connection. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_accept_max_nonmail</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">10</span> </td> </tr> </table> <p> Exim counts the number of “non-mail” commands in an SMTP session, and drops the connection if there are too many. This option defines “too many”. The check catches some denial-of-service attacks, repeated failing AUTHs, or a mad client looping sending EHLO, for example. The check is applied only if the client host matches <span class="docbook_option">smtp_accept_max_nonmail_hosts</span>. </p> <p> When a new message is expected, one occurrence of RSET is not counted. This allows a client to send one RSET between messages (this is not necessary, but some clients do it). Exim also allows one uncounted occurrence of HELO or EHLO, and one occurrence of STARTTLS between messages. After starting up a TLS session, another EHLO is expected, and so it too is not counted. The first occurrence of AUTH in a connection, or immediately following STARTTLS is not counted. Otherwise, all commands other than MAIL, RCPT, DATA, and QUIT are counted. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_accept_max_nonmail_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis"></span> </td> </tr> </table> <p> You can control which hosts are subject to the <span class="docbook_option">smtp_accept_max_nonmail</span> check by setting this option. The default value makes it apply to all hosts. By changing the value, you can exclude any badly-behaved hosts that you have to live with. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_accept_max_per_ connection</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">1000</span> </td> </tr> </table> <p> The value of this option limits the number of MAIL commands that Exim is prepared to accept over a single SMTP connection, whether or not each command results in the transfer of a message. After the limit is reached, a 421 response is given to subsequent MAIL commands. This limit is a safety precaution against a client that goes mad (incidents of this type have been seen). </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_accept_max_per_host</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option restricts the number of simultaneous IP connections from a single host (strictly, from a single IP address) to the Exim daemon. The option is expanded, to enable different limits to be applied to different hosts by reference to $sender_host_address. Once the limit is reached, additional connection attempts from the same host are rejected with error code 421. This is entirely independent of <span class="docbook_option">smtp_accept_reserve</span>. The option’s default value of zero imposes no limit. If this option is set greater than zero, it is required that <span class="docbook_option">smtp_accept_max</span> be non-zero. </p> <p> <span class="docbook_emphasis">Warning</span>: When setting this option you should not use any expansion constructions that take an appreciable amount of time. The expansion and test happen in the main daemon loop, in order to reject additional connections without forking additional processes (otherwise a denial-of-service attack could cause a vast number or processes to be created). While the daemon is doing this processing, it cannot accept any other incoming connections. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_accept_queue</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> If the number of simultaneous incoming SMTP connections being handled via the listening daemon exceeds this value, messages received by SMTP are just placed on the queue; no delivery processes are started automatically. The count is fixed at the start of an SMTP connection. It cannot be updated in the subprocess that receives messages, and so the queueing or not queueing applies to all messages received in the same connection. </p> <p> A value of zero implies no limit, and clearly any non-zero value is useful only if it is less than the <span class="docbook_option">smtp_accept_max</span> value (unless that is zero). See also <span class="docbook_option">queue_only</span>, <span class="docbook_option">queue_only_load</span>, <span class="docbook_option">queue_smtp_domains</span>, and the various <span class="docbook_option">-od</span><span class="docbook_emphasis">x</span> command line options. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_accept_queue_per_ connection</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">10</span> </td> </tr> </table> <p> This option limits the number of delivery processes that Exim starts automatically when receiving messages via SMTP, whether via the daemon or by the use of <span class="docbook_option">-bs</span> or <span class="docbook_option">-bS</span>. If the value of the option is greater than zero, and the number of messages received in a single SMTP session exceeds this number, subsequent messages are placed on the queue, but no delivery processes are started. This helps to limit the number of Exim processes when a server restarts after downtime and there is a lot of mail waiting for it on other systems. On large systems, the default should probably be increased, and on dial-in client systems it should probably be set to zero (that is, disabled). </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_accept_reserve</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">0</span> </td> </tr> </table> <p> When <span class="docbook_option">smtp_accept_max</span> is set greater than zero, this option specifies a number of SMTP connections that are reserved for connections from the hosts that are specified in <span class="docbook_option">smtp_reserve_hosts</span>. The value set in <span class="docbook_option">smtp_accept_max</span> includes this reserve pool. The specified hosts are not restricted to this number of connections; the option specifies a minimum number of connection slots for them, not a maximum. It is a guarantee that this group of hosts can always get at least <span class="docbook_option">smtp_accept_reserve</span> connections. However, the limit specified by <span class="docbook_option">smtp_accept_max_per_host</span> is still applied to each individual host. </p> <p> For example, if <span class="docbook_option">smtp_accept_max</span> is set to 50 and <span class="docbook_option">smtp_accept_reserve</span> is set to 5, once there are 45 active connections (from any hosts), new connections are accepted only from hosts listed in <span class="docbook_option">smtp_reserve_hosts</span>, provided the other criteria for acceptance are met. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_active_hostname</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option is provided for multi-homed servers that want to masquerade as several different hosts. At the start of an incoming SMTP connection, its value is expanded and used instead of the value of $primary_hostname in SMTP responses. For example, it is used as domain name in the response to an incoming HELO or EHLO command. </p> <p> The active hostname is placed in the $smtp_active_hostname variable, which is saved with any messages that are received. It is therefore available for use in routers and transports when the message is later delivered. </p> <p> If this option is unset, or if its expansion is forced to fail, or if the expansion results in an empty string, the value of $primary_hostname is used. Other expansion failures cause a message to be written to the main and panic logs, and the SMTP command receives a temporary error. Typically, the value of <span class="docbook_option">smtp_active_hostname</span> depends on the incoming interface address. For example: </p> <div class="docbook_literallayout"><pre> smtp_active_hostname = ${if eq{$received_ip_address}{10.0.0.1}\ {cox.mydomain}{box.mydomain}} </pre></div> <p> Although $smtp_active_hostname is primarily concerned with incoming messages, it is also used as the default for HELO commands in callout verification if there is no remote transport from which to obtain a <span class="docbook_option">helo_data</span> value. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_banner</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This string, which is expanded every time it is used, is output as the initial positive response to an SMTP connection. The default setting is: </p> <div class="docbook_literallayout"><pre> smtp_banner = $smtp_active_hostname ESMTP Exim \ $version_number $tod_full </pre></div> <p> Failure to expand the string causes a panic error. If you want to create a multiline response to the initial SMTP connection, use “\n” in the string at appropriate points, but not at the end. Note that the 220 code is not included in this string. Exim adds it automatically (several times in the case of a multiline response). </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_check_spool_space</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> When this option is set, if an incoming SMTP session encounters the SIZE option on a MAIL command, it checks that there is enough space in the spool directory’s partition to accept a message of that size, while still leaving free the amount specified by <span class="docbook_option">check_spool_space</span> (even if that value is zero). If there isn’t enough space, a temporary error code is returned. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_connect_backlog</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">20</span> </td> </tr> </table> <p> This option specifies a maximum number of waiting SMTP connections. Exim passes this value to the TCP/IP system when it sets up its listener. Once this number of connections are waiting for the daemon’s attention, subsequent connection attempts are refused at the TCP/IP level. At least, that is what the manuals say; in some circumstances such connection attempts have been observed to time out instead. For large systems it is probably a good idea to increase the value (to 50, say). It also gives some protection against denial-of-service attacks by SYN flooding. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_enforce_sync</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> The SMTP protocol specification requires the client to wait for a response from the server at certain points in the dialogue. Without PIPELINING these synchronization points are after every command; with PIPELINING they are fewer, but they still exist. </p> <p> Some spamming sites send out a complete set of SMTP commands without waiting for any response. Exim protects against this by rejecting a message if the client has sent further input when it should not have. The error response “554 SMTP synchronization error” is sent, and the connection is dropped. Testing for this error cannot be perfect because of transmission delays (unexpected input may be on its way but not yet received when Exim checks). However, it does detect many instances. </p> <p> The check can be globally disabled by setting <span class="docbook_option">smtp_enforce_sync</span> false. If you want to disable the check selectively (for example, only for certain hosts), you can do so by an appropriate use of a <span class="docbook_option">control</span> modifier in an ACL (see section <a href="ch42.html#SECTcontrols" title="42. Access control lists">42.21</a>). See also <span class="docbook_option">pipelining_advertise_hosts</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_etrn_command</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> If this option is set, the given command is run whenever an SMTP ETRN command is received from a host that is permitted to issue such commands (see chapter <a href="ch42.html" title="42. Access control lists">42</a>). The string is split up into separate arguments which are independently expanded. The expansion variable $domain is set to the argument of the ETRN command, and no syntax checking is done on it. For example: </p> <div class="docbook_literallayout"><pre> smtp_etrn_command = /etc/etrn_command $domain \ $sender_host_address </pre></div> <p> A new process is created to run the command, but Exim does not wait for it to complete. Consequently, its status cannot be checked. If the command cannot be run, a line is written to the panic log, but the ETRN caller still receives a 250 success response. Exim is normally running under its own uid when receiving SMTP, so it is not possible for it to change the uid before running the command. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_etrn_serialize</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> When this option is set, it prevents the simultaneous execution of more than one identical command as a result of ETRN in an SMTP connection. See section <a href="ch47.html#SECTETRN" title="47. SMTP processing">47.8</a> for details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_load_reserve</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">fixed-point</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> If the system load average ever gets higher than this, incoming SMTP calls are accepted only from those hosts that match an entry in <span class="docbook_option">smtp_reserve_hosts</span>. If <span class="docbook_option">smtp_reserve_hosts</span> is not set, no incoming SMTP calls are accepted when the load is over the limit. The option has no effect on ancient operating systems on which Exim cannot determine the load average. See also <span class="docbook_option">deliver_queue_load_max</span> and <span class="docbook_option">queue_only_load</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_max_synprot_errors</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">3</span> </td> </tr> </table> <p> Exim rejects SMTP commands that contain syntax or protocol errors. In particular, a syntactically invalid email address, as in this command: </p> <div class="docbook_literallayout"><pre> RCPT TO:<abc xyz@a.b.c> </pre></div> <p> causes immediate rejection of the command, before any other tests are done. (The ACL cannot be run if there is no valid address to set up for it.) An example of a protocol error is receiving RCPT before MAIL. If there are too many syntax or protocol errors in one SMTP session, the connection is dropped. The limit is set by this option. </p> <p> When the PIPELINING extension to SMTP is in use, some protocol errors are “expected”, for instance, a RCPT command after a rejected MAIL command. Exim assumes that PIPELINING will be used if it advertises it (see <span class="docbook_option">pipelining_advertise_hosts</span>), and in this situation, “expected” errors do not count towards the limit. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_max_unknown_commands</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">3</span> </td> </tr> </table> <p> If there are too many unrecognized commands in an incoming SMTP session, an Exim server drops the connection. This is a defence against some kinds of abuse that subvert web clients into making connections to SMTP ports; in these circumstances, a number of non-SMTP command lines are sent first. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_ratelimit_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> Some sites find it helpful to be able to limit the rate at which certain hosts can send them messages, and the rate at which an individual message can specify recipients. </p> <p> Exim has two rate-limiting facilities. This section describes the older facility, which can limit rates within a single connection. The newer <span class="docbook_option">ratelimit</span> ACL condition can limit rates across all connections. See section <a href="ch42.html#SECTratelimiting" title="42. Access control lists">42.36</a> for details of the newer facility. </p> <p> When a host matches <span class="docbook_option">smtp_ratelimit_hosts</span>, the values of <span class="docbook_option">smtp_ratelimit_mail</span> and <span class="docbook_option">smtp_ratelimit_rcpt</span> are used to control the rate of acceptance of MAIL and RCPT commands in a single SMTP session, respectively. Each option, if set, must contain a set of four comma-separated values: </p> <ul> <li> <p> A threshold, before which there is no rate limiting. </p> </li> <li> <p> An initial time delay. Unlike other times in Exim, numbers with decimal fractional parts are allowed here. </p> </li> <li> <p> A factor by which to increase the delay each time. </p> </li> <li> <p> A maximum value for the delay. This should normally be less than 5 minutes, because after that time, the client is liable to timeout the SMTP command. </p> </li> </ul> <p> For example, these settings have been used successfully at the site which first suggested this feature, for controlling mail from their customers: </p> <div class="docbook_literallayout"><pre> smtp_ratelimit_mail = 2,0.5s,1.05,4m smtp_ratelimit_rcpt = 4,0.25s,1.015,4m </pre></div> <p> The first setting specifies delays that are applied to MAIL commands after two have been received over a single connection. The initial delay is 0.5 seconds, increasing by a factor of 1.05 each time. The second setting applies delays to RCPT commands when more than four occur in a single message. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_ratelimit_mail</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> See <span class="docbook_option">smtp_ratelimit_hosts</span> above. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_ratelimit_rcpt</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> See <span class="docbook_option">smtp_ratelimit_hosts</span> above. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_receive_timeout</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">5m</span> </td> </tr> </table> <p> This sets a timeout value for SMTP reception. It applies to all forms of SMTP input, including batch SMTP. If a line of input (either an SMTP command or a data line) is not received within this time, the SMTP connection is dropped and the message is abandoned. A line is written to the log containing one of the following messages: </p> <div class="docbook_literallayout"><pre> SMTP command timeout on connection from... SMTP data timeout on connection from... </pre></div> <p> 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. </p> <p> The value set by this option can be overridden by the <span class="docbook_option">-os</span> command-line option. A setting of zero time disables the timeout, but this should never be used for SMTP over TCP/IP. (It can be useful in some cases of local input using <span class="docbook_option">-bs</span> or <span class="docbook_option">-bS</span>.) For non-SMTP input, the reception timeout is controlled by <span class="docbook_option">receive_timeout</span> and <span class="docbook_option">-or</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_reserve_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines hosts for which SMTP connections are reserved; see <span class="docbook_option">smtp_accept_reserve</span> and <span class="docbook_option">smtp_load_reserve</span> above. </p> <p> </p> <table> <tr> <td><span class="docbook_option">smtp_return_error_details</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> In the default state, Exim uses bland messages such as “Administrative prohibition” when it rejects SMTP commands for policy reasons. Many sysadmins like this because it gives away little information to spammers. However, some other sysadmins who are applying strict checking policies want to give out much fuller information about failures. Setting <span class="docbook_option">smtp_return_error_details</span> true causes Exim to be more forthcoming. For example, instead of “Administrative prohibition”, it might give: </p> <div class="docbook_literallayout"><pre> 550-Rejected after DATA: '>' missing at end of address: 550 failing address in "From" header is: <user@dom.ain </pre></div> <p> </p> <table> <tr> <td><span class="docbook_option">spamd_address</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> This option is available when Exim is compiled with the content-scanning extension. It specifies how Exim connects to SpamAssassin’s <span class="docbook_option">spamd</span> daemon. The default value is </p> <div class="docbook_literallayout"><pre> 127.0.0.1 783 </pre></div> <p> See section <a href="ch43.html#SECTscanspamass" title="43. Content scanning at ACL time">43.2</a> for more details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">split_spool_directory</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If this option is set, it causes Exim to split its input directory into 62 subdirectories, each with a single alphanumeric character as its name. The sixth character of the message id is used to allocate messages to subdirectories; this is the least significant base-62 digit of the time of arrival of the message. </p> <p> Splitting up the spool in this way may provide better performance on systems where there are long mail queues, by reducing the number of files in any one directory. The msglog directory is also split up in a similar way to the input directory; however, if <span class="docbook_option">preserve_message_logs</span> is set, all old msglog files are still placed in the single directory <span class="docbook_filename">msglog.OLD</span>. </p> <p> It is not necessary to take any special action for existing messages when changing <span class="docbook_option">split_spool_directory</span>. Exim notices messages that are in the “wrong” place, and continues to process them. If the option is turned off after a period of being on, the subdirectories will eventually empty and be automatically deleted. </p> <p> When <span class="docbook_option">split_spool_directory</span> is set, the behaviour of queue runner processes changes. Instead of creating a list of all messages in the queue, and then trying to deliver each one in turn, it constructs a list of those in one sub-directory and tries to deliver them, before moving on to the next sub-directory. The sub-directories are processed in a random order. This spreads out the scanning of the input directories, and uses less memory. It is particularly beneficial when there are lots of messages on the queue. However, if <span class="docbook_option">queue_run_in_order</span> is set, none of this new processing happens. The entire queue has to be scanned and sorted before any deliveries can start. </p> <p> </p> <table> <tr> <td><span class="docbook_option">spool_directory</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">set at compile time</span> </td> </tr> </table> <p> This defines the directory in which Exim keeps its spool, that is, the messages it is waiting to deliver. The default value is taken from the compile-time configuration setting, if there is one. If not, this option must be set. The string is expanded, so it can contain, for example, a reference to $primary_hostname. </p> <p> If the spool directory name is fixed on your installation, it is recommended that you set it at build time rather than from this option, particularly if the log files are being written to the spool directory (see <span class="docbook_option">log_file_path</span>). Otherwise log files cannot be used for errors that are detected early on, such as failures in the configuration file. </p> <p> By using this option to override the compiled-in path, it is possible to run tests of Exim without using the standard spool. </p> <p> </p> <table> <tr> <td><span class="docbook_option">sqlite_lock_timeout</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">5s</span> </td> </tr> </table> <p> This option controls the timeout that the <span class="docbook_command">sqlite</span> lookup uses when trying to access an SQLite database. See section <a href="ch09.html#SECTsqlite" title="9. File and database lookups">9.25</a> for more details. </p> <p> </p> <table> <tr> <td><span class="docbook_option">strict_acl_vars</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> This option controls what happens if a syntactically valid but undefined ACL variable is referenced. If it is false (the default), an empty string is substituted; if it is true, an error is generated. See section <a href="ch42.html#SECTaclvariables" title="42. Access control lists">42.18</a> for details of ACL variables. </p> <p> </p> <table> <tr> <td><span class="docbook_option">strip_excess_angle_brackets</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If this option is set, redundant pairs of angle brackets round “route-addr” items in addresses are stripped. For example, <span class="docbook_emphasis"><<xxx@a.b.c.d>></span> is treated as <span class="docbook_emphasis"><xxx@a.b.c.d></span>. If this is in the envelope and the message is passed on to another MTA, the excess angle brackets are not passed on. If this option is not set, multiple pairs of angle brackets cause a syntax error. </p> <p> </p> <table> <tr> <td><span class="docbook_option">strip_trailing_dot</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If this option is set, a trailing dot at the end of a domain in an address is ignored. If this is in the envelope and the message is passed on to another MTA, the dot is not passed on. If this option is not set, a dot at the end of a domain causes a syntax error. However, addresses in header lines are checked only when an ACL requests header syntax checking. </p> <p> </p> <table> <tr> <td><span class="docbook_option">syslog_duplication</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> When Exim is logging to syslog, it writes the log lines for its three separate logs at different syslog priorities so that they can in principle be separated on the logging hosts. Some installations do not require this separation, and in those cases, the duplication of certain log lines is a nuisance. If <span class="docbook_option">syslog_duplication</span> is set false, only one copy of any particular log line is written to syslog. For lines that normally go to both the main log and the reject log, the reject log version (possibly containing message header lines) is written, at LOG_NOTICE priority. Lines that normally go to both the main and the panic log are written at the LOG_ALERT priority. </p> <p> </p> <table> <tr> <td><span class="docbook_option">syslog_facility</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option sets the syslog “facility” name, used when Exim is logging to syslog. The value must be one of the strings “mail”, “user”, “news”, “uucp”, “daemon”, or “local<span class="docbook_emphasis">x</span>” where <span class="docbook_emphasis">x</span> is a digit between 0 and 7. If this option is unset, “mail” is used. See chapter <a href="ch51.html" title="51. Log files">51</a> for details of Exim’s logging. </p> <p> </p> <table> <tr> <td><span class="docbook_option">syslog_processname</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis"><code class="docbook_literal">exim</code></span> </td> </tr> </table> <p> This option sets the syslog “ident” name, used when Exim is logging to syslog. The value must be no longer than 32 characters. See chapter <a href="ch51.html" title="51. Log files">51</a> for details of Exim’s logging. </p> <p> </p> <table> <tr> <td><span class="docbook_option">syslog_timestamp</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> If <span class="docbook_option">syslog_timestamp</span> is set false, the timestamps on Exim’s log lines are omitted when these lines are sent to syslog. See chapter <a href="ch51.html" title="51. Log files">51</a> for details of Exim’s logging. </p> <p> </p> <table> <tr> <td><span class="docbook_option">system_filter</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option specifies an Exim filter file that is applied to all messages at the start of each delivery attempt, before any routing is done. System filters must be Exim filters; they cannot be Sieve filters. If the system filter generates any deliveries to files or pipes, or any new mail messages, the appropriate <span class="docbook_option">system_filter_..._transport</span> option(s) must be set, to define which transports are to be used. Details of this facility are given in chapter <a href="ch45.html" title="45. System-wide message filtering">45</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">system_filter_directory_transport</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This sets the name of the transport driver that is to be used when the <span class="docbook_option">save</span> command in a system message filter specifies a path ending in “/”, implying delivery of each message into a separate file in some directory. During the delivery, the variable $address_file contains the path name. </p> <p> </p> <table> <tr> <td><span class="docbook_option">system_filter_file_transport</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This sets the name of the transport driver that is to be used when the <span class="docbook_option">save</span> command in a system message filter specifies a path not ending in “/”. During the delivery, the variable $address_file contains the path name. </p> <p> </p> <table> <tr> <td><span class="docbook_option">system_filter_group</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option is used only when <span class="docbook_option">system_filter_user</span> is also set. It sets the gid under which the system filter is run, overriding any gid that is associated with the user. The value may be numerical or symbolic. </p> <p> </p> <table> <tr> <td><span class="docbook_option">system_filter_pipe_transport</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This specifies the transport driver that is to be used when a <span class="docbook_option">pipe</span> command is used in a system filter. During the delivery, the variable $address_pipe contains the pipe command. </p> <p> </p> <table> <tr> <td><span class="docbook_option">system_filter_reply_transport</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This specifies the transport driver that is to be used when a <span class="docbook_option">mail</span> command is used in a system filter. </p> <p> </p> <table> <tr> <td><span class="docbook_option">system_filter_user</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> If this option is set to root, the system filter is run in the main Exim delivery process, as root. Otherwise, the system filter runs in a separate process, as the given user, defaulting to the Exim run-time user. Unless the string consists entirely of digits, it is looked up in the password data. Failure to find the named user causes a configuration error. The gid is either taken from the password data, or specified by <span class="docbook_option">system_filter_group</span>. When the uid is specified numerically, <span class="docbook_option">system_filter_group</span> is required to be set. </p> <p> If the system filter generates any pipe, file, or reply deliveries, the uid under which the filter is run is used when transporting them, unless a transport option overrides. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tcp_nodelay</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> If this option is set false, it stops the Exim daemon setting the TCP_NODELAY option on its listening sockets. Setting TCP_NODELAY turns off the “Nagle algorithm”, which is a way of improving network performance in interactive (character-by-character) situations. Turning it off should improve Exim’s performance a bit, so that is what happens by default. However, it appears that some broken clients cannot cope, and time out. Hence this option. It affects only those sockets that are set up for listening by the daemon. Sockets created by the smtp transport for delivering mail always set TCP_NODELAY. </p> <p> </p> <table> <tr> <td><span class="docbook_option">timeout_frozen_after</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">time</span> </td> <td>Default: <span class="docbook_emphasis">0s</span> </td> </tr> </table> <p> If <span class="docbook_option">timeout_frozen_after</span> is set to a time greater than zero, a frozen message of any kind that has been on the queue for longer than the given time is automatically cancelled at the next queue run. If the frozen message is a bounce message, it is just discarded; otherwise, a bounce is sent to the sender, in a similar manner to cancellation by the <span class="docbook_option">-Mg</span> command line option. If you want to timeout frozen bounce messages earlier than other kinds of frozen message, see <span class="docbook_option">ignore_bounce_errors_after</span>. </p> <p> <span class="docbook_emphasis">Note:</span> the default value of zero means no timeouts; with this setting, frozen messages remain on the queue forever (except for any frozen bounce messages that are released by <span class="docbook_option">ignore_bounce_errors_after</span>). </p> <p> </p> <table> <tr> <td><span class="docbook_option">timezone</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> The value of <span class="docbook_option">timezone</span> is used to set the environment variable TZ while running Exim (if it is different on entry). This ensures that all timestamps created by Exim are in the required timezone. If you want all your timestamps to be in UTC (aka GMT) you should set </p> <div class="docbook_literallayout"><pre> timezone = UTC </pre></div> <p> The default value is taken from TIMEZONE_DEFAULT in <span class="docbook_filename">Local/Makefile</span>, or, if that is not set, from the value of the TZ environment variable when Exim is built. If <span class="docbook_option">timezone</span> is set to the empty string, either at build or run time, any existing TZ variable is removed from the environment when Exim runs. This is appropriate behaviour for obtaining wall-clock time on some, but unfortunately not all, operating systems. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_advertise_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> When Exim is built with support for TLS encrypted connections, the availability of the STARTTLS command to set up an encrypted session is advertised in response to EHLO only to those client hosts that match this option. See chapter <a href="ch41.html" title="41. Encrypted SMTP connections using TLS/SSL">41</a> for details of Exim’s support for TLS. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_certificate</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> The value of this option is expanded, and must then be the absolute path to a file which contains the server’s certificates. The server’s private key is also assumed to be in this file if <span class="docbook_option">tls_privatekey</span> is unset. See chapter <a href="ch41.html" title="41. Encrypted SMTP connections using TLS/SSL">41</a> for further details. </p> <p> <span class="docbook_emphasis">Note</span>: The certificates defined by this option are used only when Exim is receiving incoming messages as a server. If you want to supply certificates for use when sending messages as a client, you must set the <span class="docbook_option">tls_certificate</span> option in the relevant <span class="docbook_command">smtp</span> transport. </p> <p class="changed"> If the option contains $tls_sni and Exim is built against OpenSSL, then if the OpenSSL build supports TLS extensions and the TLS client sends the Server Name Indication extension, then this option and others documented in <a href="ch41.html#SECTtlssni" title="41. Encrypted SMTP connections using TLS/SSL">41.10</a> will be re-expanded. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_crl</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option specifies a certificate revocation list. The expanded value must be the name of a file that contains a CRL in PEM format. </p> <p class="changed"> See <a href="ch41.html#SECTtlssni" title="41. Encrypted SMTP connections using TLS/SSL">41.10</a> for discussion of when this option might be re-expanded. </p> <p class="changed"> </p> <table> <tr> <td><span class="docbook_option">tls_dh_max_bits</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">integer</span> </td> <td>Default: <span class="docbook_emphasis">2236</span> </td> </tr> </table> <p class="changed"> The number of bits used for Diffie-Hellman key-exchange may be suggested by the chosen TLS library. That value might prove to be too high for interoperability. This option provides a maximum clamp on the value suggested, trading off security for interoperability. </p> <p class="changed"> The value must be at least 1024. </p> <p class="changed"> The value 2236 was chosen because, at time of adding the option, it was the hard-coded maximum value supported by the NSS cryptographic library, as used by Thunderbird, while GnuTLS was suggesting 2432 bits as normal. </p> <p class="changed"> If you prefer more security and are willing to break some clients, raise this number. </p> <p class="changed"> Note that the value passed to GnuTLS for generating a new prime may be a little less than this figure, because GnuTLS is inexact and may produce a larger prime than requested. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_dhparam</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> </p> <p class="changed"> The value of this option is expanded and indicates the source of DH parameters to be used by Exim. </p> <p class="changed"> If it is a filename starting with a <code class="docbook_literal">/</code>, then it names a file from which DH parameters should be loaded. If the file exists, it should hold a PEM-encoded PKCS#3 representation of the DH prime. If the file does not exist, for OpenSSL it is an error. For GnuTLS, Exim will attempt to create the file and fill it with a generated DH prime. For OpenSSL, if the DH bit-count from loading the file is greater than <span class="docbook_option">tls_dh_max_bits</span> then it will be ignored, and treated as though the <span class="docbook_option">tls_dhparam</span> were set to "none". </p> <p class="changed"> If this option expands to the string "none", then no DH parameters will be loaded by Exim. </p> <p class="changed"> If this option expands to the string "historic" and Exim is using GnuTLS, then Exim will attempt to load a file from inside the spool directory. If the file does not exist, Exim will attempt to create it. See section <a href="ch41.html#SECTgnutlsparam" title="41. Encrypted SMTP connections using TLS/SSL">41.3</a> for further details. </p> <p class="changed"> If Exim is using OpenSSL and this option is empty or unset, then Exim will load a default DH prime; the default is the 2048 bit prime described in section 2.2 of RFC 5114, "2048-bit MODP Group with 224-bit Prime Order Subgroup", which in IKE is assigned number 23. </p> <p class="changed"> Otherwise, the option must expand to the name used by Exim for any of a number of DH primes specified in RFC 2409, RFC 3526 and RFC 5114. As names, Exim uses "ike" followed by the number used by IKE, of "default" which corresponds to "ike23". </p> <p class="changed"> The available primes are: <code class="docbook_literal">ike1</code>, <code class="docbook_literal">ike2</code>, <code class="docbook_literal">ike5</code>, <code class="docbook_literal">ike14</code>, <code class="docbook_literal">ike15</code>, <code class="docbook_literal">ike16</code>, <code class="docbook_literal">ike17</code>, <code class="docbook_literal">ike18</code>, <code class="docbook_literal">ike22</code>, <code class="docbook_literal">ike23</code> (aka <code class="docbook_literal">default</code>) and <code class="docbook_literal">ike24</code>. </p> <p class="changed"> Some of these will be too small to be accepted by clients. Some may be too large to be accepted by clients. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_on_connect_ports</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option specifies a list of incoming SSMTP (aka SMTPS) ports that should operate the obsolete SSMTP (SMTPS) protocol, where a TLS session is immediately set up without waiting for the client to issue a STARTTLS command. For further details, see section <a href="ch13.html#SECTsupobssmt" title="13. Starting the daemon and the use of network interfaces">13.4</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_privatekey</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> The value of this option is expanded, and must then be the absolute path to a file which contains the server’s private key. If this option is unset, or if the expansion is forced to fail, or the result is an empty string, the private key is assumed to be in the same file as the server’s certificates. See chapter <a href="ch41.html" title="41. Encrypted SMTP connections using TLS/SSL">41</a> for further details. </p> <p class="changed"> See <a href="ch41.html#SECTtlssni" title="41. Encrypted SMTP connections using TLS/SSL">41.10</a> for discussion of when this option might be re-expanded. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_remember_esmtp</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">false</span> </td> </tr> </table> <p> If this option is set true, Exim violates the RFCs by remembering that it is in “esmtp” state after successfully negotiating a TLS session. This provides support for broken clients that fail to send a new EHLO after starting a TLS session. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_require_ciphers</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option controls which ciphers can be used for incoming TLS connections. The <span class="docbook_command">smtp</span> transport has an option of the same name for controlling outgoing connections. This option is expanded for each connection, so can be varied for different clients if required. The value of this option must be a list of permitted cipher suites. The OpenSSL and GnuTLS libraries handle cipher control in somewhat different ways. If GnuTLS is being used, the client controls the preference order of the available ciphers. Details are given in sections <a href="ch41.html#SECTreqciphssl" title="41. Encrypted SMTP connections using TLS/SSL">41.4</a> and <a href="ch41.html#SECTreqciphgnu" title="41. Encrypted SMTP connections using TLS/SSL">41.5</a>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_try_verify_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> See <span class="docbook_option">tls_verify_hosts</span> below. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_verify_certificates</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> The value of this option is expanded, and must then be the absolute path to a file containing permitted certificates for clients that match <span class="docbook_option">tls_verify_hosts</span> or <span class="docbook_option">tls_try_verify_hosts</span>. Alternatively, if you are using OpenSSL, you can set <span class="docbook_option">tls_verify_certificates</span> to the name of a directory containing certificate files. This does not work with GnuTLS; the option must be set to the name of a single file if you are using GnuTLS. </p> <p> These certificates should be for the certificate authorities trusted, rather than the public cert of individual clients. With both OpenSSL and GnuTLS, if the value is a file then the certificates are sent by Exim as a server to connecting clients, defining the list of accepted certificate authorities. Thus the values defined should be considered public data. To avoid this, use OpenSSL with a directory. </p> <p class="changed"> See <a href="ch41.html#SECTtlssni" title="41. Encrypted SMTP connections using TLS/SSL">41.10</a> for discussion of when this option might be re-expanded. </p> <p> </p> <table> <tr> <td><span class="docbook_option">tls_verify_hosts</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">host list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option, along with <span class="docbook_option">tls_try_verify_hosts</span>, controls the checking of certificates from clients. The expected certificates are defined by <span class="docbook_option">tls_verify_certificates</span>, which must be set. A configuration error occurs if either <span class="docbook_option">tls_verify_hosts</span> or <span class="docbook_option">tls_try_verify_hosts</span> is set and <span class="docbook_option">tls_verify_certificates</span> is not set. </p> <p> Any client that matches <span class="docbook_option">tls_verify_hosts</span> is constrained by <span class="docbook_option">tls_verify_certificates</span>. When the client initiates a TLS session, it must present one of the listed certificates. If it does not, the connection is aborted. <span class="docbook_emphasis">Warning</span>: Including a host in <span class="docbook_option">tls_verify_hosts</span> does not require the host to use TLS. It can still send SMTP commands through unencrypted connections. Forcing a client to use TLS has to be done separately using an ACL to reject inappropriate commands when the connection is not encrypted. </p> <p> A weaker form of checking is provided by <span class="docbook_option">tls_try_verify_hosts</span>. If a client matches this option (but not <span class="docbook_option">tls_verify_hosts</span>), Exim requests a certificate and checks it against <span class="docbook_option">tls_verify_certificates</span>, but does not abort the connection if there is no certificate or if it does not match. This state can be detected in an ACL, which makes it possible to implement policies such as “accept for relay only if a verified certificate has been received, but accept for local delivery if encrypted, even without a verified certificate”. </p> <p> Client hosts that match neither of these lists are not asked to present certificates. </p> <p> </p> <table> <tr> <td><span class="docbook_option">trusted_groups</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option is expanded just once, at the start of Exim’s processing. If this option is set, any process that is running in one of the listed groups, or which has one of them as a supplementary group, is trusted. The groups can be specified numerically or by name. See section <a href="ch05.html#SECTtrustedadmin" title="5. The Exim command line">5.2</a> for details of what trusted callers are permitted to do. If neither <span class="docbook_option">trusted_groups</span> nor <span class="docbook_option">trusted_users</span> is set, only root and the Exim user are trusted. </p> <p> </p> <table> <tr> <td><span class="docbook_option">trusted_users</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option is expanded just once, at the start of Exim’s processing. If this option is set, any process that is running as one of the listed users is trusted. The users can be specified numerically or by name. See section <a href="ch05.html#SECTtrustedadmin" title="5. The Exim command line">5.2</a> for details of what trusted callers are permitted to do. If neither <span class="docbook_option">trusted_groups</span> nor <span class="docbook_option">trusted_users</span> is set, only root and the Exim user are trusted. </p> <p> </p> <table> <tr> <td><span class="docbook_option">unknown_login</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This is a specialized feature for use in unusual configurations. By default, if the uid of the caller of Exim cannot be looked up using <span class="docbook_function">getpwuid()</span>, Exim gives up. The <span class="docbook_option">unknown_login</span> option can be used to set a login name to be used in this circumstance. It is expanded, so values like <span class="docbook_option">user$caller_uid</span> can be set. When <span class="docbook_option">unknown_login</span> is used, the value of <span class="docbook_option">unknown_username</span> is used for the user’s real name (gecos field), unless this has been set by the <span class="docbook_option">-F</span> option. </p> <p> </p> <table> <tr> <td><span class="docbook_option">unknown_username</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> See <span class="docbook_option">unknown_login</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">untrusted_set_sender</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">address list</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> When an untrusted user submits a message to Exim using the standard input, Exim normally creates an envelope sender address from the user’s login and the default qualification domain. Data from the <span class="docbook_option">-f</span> option (for setting envelope senders on non-SMTP messages) or the SMTP MAIL command (if <span class="docbook_option">-bs</span> or <span class="docbook_option">-bS</span> is used) is ignored. </p> <p> However, untrusted users are permitted to set an empty envelope sender address, to declare that a message should never generate any bounces. For example: </p> <div class="docbook_literallayout"><pre> exim -f '<>' user@domain.example </pre></div> <p> The <span class="docbook_option">untrusted_set_sender</span> option allows you to permit untrusted users to set other envelope sender addresses in a controlled way. When it is set, untrusted users are allowed to set envelope sender addresses that match any of the patterns in the list. Like all address lists, the string is expanded. The identity of the user is in $sender_ident, so you can, for example, restrict users to setting senders that start with their login ids followed by a hyphen by a setting like this: </p> <div class="docbook_literallayout"><pre> untrusted_set_sender = ^$sender_ident- </pre></div> <p> If you want to allow untrusted users to set envelope sender addresses without restriction, you can use </p> <div class="docbook_literallayout"><pre> untrusted_set_sender = * </pre></div> <p> The <span class="docbook_option">untrusted_set_sender</span> option applies to all forms of local input, but only to the setting of the envelope sender. It does not permit untrusted users to use the other options which trusted user can use to override message parameters. Furthermore, it does not stop Exim from removing an existing <span class="docbook_emphasis">Sender:</span> header in the message, or from adding a <span class="docbook_emphasis">Sender:</span> header if necessary. See <span class="docbook_option">local_sender_retain</span> and <span class="docbook_option">local_from_check</span> for ways of overriding these actions. The handling of the <span class="docbook_emphasis">Sender:</span> header is also described in section <a href="ch46.html#SECTthesenhea" title="46. Message processing">46.16</a>. </p> <p> The log line for a message’s arrival shows the envelope sender following “<=”. For local messages, the user’s login always follows, after “U=”. In <span class="docbook_option">-bp</span> displays, and in the Exim monitor, if an untrusted user sets an envelope sender address, the user’s login is shown in parentheses after the sender address. </p> <p> </p> <table> <tr> <td><span class="docbook_option">uucp_from_pattern</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">see below</span> </td> </tr> </table> <p> Some applications that pass messages to an MTA via a command line interface use an initial line starting with “From ” to pass the envelope sender. In particular, this is used by UUCP software. Exim recognizes such a line by means of a regular expression that is set in <span class="docbook_option">uucp_from_pattern</span>. When the pattern matches, the sender address is constructed by expanding the contents of <span class="docbook_option">uucp_from_sender</span>, provided that the caller of Exim is a trusted user. The default pattern recognizes lines in the following two forms: </p> <div class="docbook_literallayout"><pre> From ph10 Fri Jan 5 12:35 GMT 1996 From ph10 Fri, 7 Jan 97 14:00:00 GMT </pre></div> <p> The pattern can be seen by running </p> <div class="docbook_literallayout"><pre> exim -bP uucp_from_pattern </pre></div> <p> It checks only up to the hours and minutes, and allows for a 2-digit or 4-digit year in the second case. The first word after “From ” is matched in the regular expression by a parenthesized subpattern. The default value for <span class="docbook_option">uucp_from_sender</span> is “$1”, which therefore just uses this first word (“ph10” in the example above) as the message’s sender. See also <span class="docbook_option">ignore_fromline_hosts</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">add_environment</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">empty</span> </td> </tr> </table> <p> This option allows to set individual environment variables that the currently linked libraries and programs in child processes use. The default list is empty, </p> <table> <tr> <td><span class="docbook_option">keep_environment</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string list</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option contains a string list of environment variables to keep. You have to trust these variables or you have to be sure that these variables do not impose any security risk. Keep in mind that during the startup phase Exim is running with an effective UID 0 in most installations. As the default value is an empty list, the default environment for using libraries, running embedded Perl code, or running external binaries is empty, and does not not even contain PATH or HOME. </p> <table> <tr> <td><span class="docbook_option">uucp_from_sender</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span>†<span class="docbook_emphasis"></span> </td> <td>Default: <span class="docbook_emphasis"><code class="docbook_literal">$1</code></span> </td> </tr> </table> <p> See <span class="docbook_option">uucp_from_pattern</span> above. </p> <p> </p> <table> <tr> <td><span class="docbook_option">warn_message_file</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">string</span> </td> <td>Default: <span class="docbook_emphasis">unset</span> </td> </tr> </table> <p> This option defines a template file containing paragraphs of text to be used for constructing the warning message which is sent by Exim when a message has been on the queue for a specified amount of time, as specified by <span class="docbook_option">delay_warning</span>. Details of the file’s contents are given in chapter <a href="ch48.html" title="48. Customizing bounce and warning messages">48</a>. See also <span class="docbook_option">bounce_message_file</span>. </p> <p> </p> <table> <tr> <td><span class="docbook_option">write_rejectlog</span></td> <td>Use: <span class="docbook_emphasis">main</span> </td> <td>Type: <span class="docbook_emphasis">boolean</span> </td> <td>Default: <span class="docbook_emphasis">true</span> </td> </tr> </table> <p> If this option is set false, Exim no longer writes anything to the reject log. See chapter <a href="ch51.html" title="51. Log files">51</a> for details of what Exim writes to its logs. </p> </div> </div> <a class="previous_page" href="ch13.html"><-previous</a><a class="toc_page" href="ch13.html">Table of Contents</a><a class="next_page" href="ch15.html">next-></a> </div></div> <iframe id="branding" name="branding" src="../../../../branding/branding.html" height="0" frameborder="no" scrolling="no"></iframe><div id="footer">Website design by <a href="https://grepular.com/">Mike Cardwell</a>, of <a href="http://cardwellit.com/">Cardwell IT Ltd.</a> </div> <div class="left_bar"></div> <div class="right_bar"></div> <div id="toc"> <ul class="hidden"></ul> <img src="../../../../doc/contents.png" width="16" height="155"> </div> </div> <script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1.6/jquery.min.js"></script><script type="text/javascript" src="../../../../static/js/common.js"></script><script type="text/javascript" src="../../../../static/doc/chapter.js"></script> </body> </html>

| ver. 1.4 | Github | . | PHP 8.1.34 | Generation time: 0.03 | proxy | phpinfo | Settings