Document pkg-config
[exim.git] / src / src / EDITME
CommitLineData
059ec3d9
PH
1##################################################
2# The Exim mail transport agent #
3##################################################
4
5# This is the template for Exim's main build-time configuration file. It
6# contains settings that are independent of any operating system. These are
7# things that are mostly sysadmin choices. The items below are divided into
8# those you must specify, those you probably want to specify, those you might
9# often want to specify, and those that you almost never need to mention.
10
11# Edit this file and save the result to a file called Local/Makefile within the
12# Exim distribution directory before running the "make" command.
13
14# Things that depend on the operating system have default settings in
15# OS/Makefile-Default, but these are overridden for some OS by files called
16# called OS/Makefile-<osname>. You can further override these by creating files
17# called Local/Makefile-<osname>, where "<osname>" stands for the name of your
18# operating system - look at the names in the OS directory to see which names
19# are recognized.
20
21# However, if you are building Exim for a single OS only, you don't need to
22# worry about setting up Local/Makefile-<osname>. Any build-time configuration
23# settings you require can in fact be placed in the one file called
24# Local/Makefile. It is only if you are building for several OS from the same
25# source files that you need to worry about splitting off your own OS-dependent
26# settings into separate files. (There's more explanation about how this all
27# works in the toplevel README file, under "Modifying the building process", as
28# well as in the Exim specification.)
29
30# One OS-specific thing that may need to be changed is the command for running
31# the C compiler; the overall default is gcc, but some OS Makefiles specify cc.
32# You can override anything that is set by putting CC=whatever in your
33# Local/Makefile.
34
35# NOTE: You should never need to edit any of the distributed Makefiles; all
36# overriding can be done in your Local/Makefile(s). This will make it easier
37# for you when the next release comes along.
38
39# The location of the X11 libraries is something else that is quite variable
40# even between different versions of the same operating system (and indeed
41# there are different versions of X11 as well, of course). The four settings
42# concerned here are X11, XINCLUDE, XLFLAGS (linking flags) and X11_LD_LIB
43# (dynamic run-time library). You need not worry about X11 unless you want to
44# compile the Exim monitor utility. Exim itself does not use X11.
45
46# Another area of variability between systems is the type and location of the
47# DBM library package. Exim has support for ndbm, gdbm, tdb, and Berkeley DB.
48# By default the code assumes ndbm; this often works with gdbm or DB, provided
49# they are correctly installed, via their compatibility interfaces. However,
50# Exim can also be configured to use the native calls for Berkeley DB (obsolete
51# versions 1.85, 2.x, 3.x, or the current 4.x version) and also for gdbm.
52
53# For some operating systems, a default DBM library (other than ndbm) is
54# selected by a setting in the OS-specific Makefile. Most modern OS now have
55# a DBM library installed as standard, and in many cases this will be selected
56# for you by the OS-specific configuration. If Exim compiles without any
57# problems, you probably do not have to worry about the DBM library. If you
58# do want or need to change it, you should first read the discussion in the
59# file doc/dbm.discuss.txt, which also contains instructions for testing Exim's
60# interface to the DBM library.
61
62# In Local/Makefiles blank lines and lines starting with # are ignored. It is
63# also permitted to use the # character to add a comment to a setting, for
64# example
65#
66# EXIM_GID=42 # the "mail" group
67#
68# However, with some versions of "make" this works only if there is no white
69# space between the end of the setting and the #, so perhaps it is best
70# avoided. A consequence of this facility is that it is not possible to have
71# the # character present in any setting, but I can't think of any cases where
72# this would be wanted.
73###############################################################################
74
75
76
77###############################################################################
78# THESE ARE THINGS YOU MUST SPECIFY #
79###############################################################################
80
81# Exim will not build unless you specify BIN_DIRECTORY, CONFIGURE_FILE, and
82# EXIM_USER. You also need EXIM_GROUP if EXIM_USER specifies a uid by number.
83
84# If you don't specify SPOOL_DIRECTORY, Exim won't fail to build. However, it
85# really is a very good idea to specify it here rather than at run time. This
86# is particularly true if you let the logs go to their default location in the
87# spool directory, because it means that the location of the logs is known
88# before Exim has read the run time configuration file.
89
90#------------------------------------------------------------------------------
91# BIN_DIRECTORY defines where the exim binary will be installed by "make
92# install". The path is also used internally by Exim when it needs to re-invoke
93# itself, either to send an error message, or to recover root privilege. Exim's
94# utility binaries and scripts are also installed in this directory. There is
95# no "standard" place for the binary directory. Some people like to keep all
96# the Exim files under one directory such as /usr/exim; others just let the
97# Exim binaries go into an existing directory such as /usr/sbin or
98# /usr/local/sbin. The installation script will try to create this directory,
99# and any superior directories, if they do not exist.
100
101BIN_DIRECTORY=/usr/exim/bin
102
103
104#------------------------------------------------------------------------------
105# CONFIGURE_FILE defines where Exim's run time configuration file is to be
106# found. It is the complete pathname for the file, not just a directory. The
107# location of all other run time files and directories can be changed in the
108# run time configuration file. There is a lot of variety in the choice of
109# location in different OS, and in the preferences of different sysadmins. Some
110# common locations are in /etc or /etc/mail or /usr/local/etc or
111# /usr/local/etc/mail. Another possibility is to keep all the Exim files under
112# a single directory such as /usr/exim. Whatever you choose, the installation
113# script will try to make the directory and any superior directories if they
114# don't exist. It will also install a default runtime configuration if this
115# file does not exist.
116
117CONFIGURE_FILE=/usr/exim/configure
118
119# It is possible to specify a colon-separated list of files for CONFIGURE_FILE.
120# In this case, Exim will use the first of them that exists when it is run.
121# However, if a list is specified, the installation script no longer tries to
122# make superior directories or to install a default runtime configuration.
123
124
125#------------------------------------------------------------------------------
126# The Exim binary must normally be setuid root, so that it starts executing as
127# root, but (depending on the options with which it is called) it does not
128# always need to retain the root privilege. These settings define the user and
129# group that is used for Exim processes when they no longer need to be root. In
130# particular, this applies when receiving messages and when doing remote
131# deliveries. (Local deliveries run as various non-root users, typically as the
10385c15 132# owner of a local mailbox.) Specifying these values as root is not supported.
059ec3d9
PH
133
134EXIM_USER=
135
136# If you specify EXIM_USER as a name, this is looked up at build time, and the
137# uid number is built into the binary. However, you can specify that this
138# lookup is deferred until runtime. In this case, it is the name that is built
139# into the binary. You can do this by a setting of the form:
140
141# EXIM_USER=ref:exim
142
143# In other words, put "ref:" in front of the user name. If you set EXIM_USER
144# like this, any value specified for EXIM_GROUP is also passed "by reference".
145# Although this costs a bit of resource at runtime, it is convenient to use
146# this feature when building binaries that are to be run on multiple systems
147# where the name may refer to different uids. It also allows you to build Exim
148# on a system where there is no Exim user defined.
149
150# If the setting of EXIM_USER is numeric (e.g. EXIM_USER=42), there must
151# also be a setting of EXIM_GROUP. If, on the other hand, you use a name
152# for EXIM_USER (e.g. EXIM_USER=exim), you don't need to set EXIM_GROUP unless
153# you want to use a group other than the default group for the given user.
154
155# EXIM_GROUP=
156
157# Many sites define a user called "exim", with an appropriate default group,
158# and use
159#
160# EXIM_USER=exim
161#
162# while leaving EXIM_GROUP unspecified (commented out).
163
164
165#------------------------------------------------------------------------------
166# SPOOL_DIRECTORY defines the directory where all the data for messages in
167# transit is kept. It is strongly recommended that you define it here, though
168# it is possible to leave this till the run time configuration.
169
170# Exim creates the spool directory if it does not exist. The owner and group
171# will be those defined by EXIM_USER and EXIM_GROUP, and this also applies to
172# all the files and directories that are created in the spool directory.
173
174# Almost all installations choose this:
175
176SPOOL_DIRECTORY=/var/spool/exim
177
178
179
180###############################################################################
181# THESE ARE THINGS YOU PROBABLY WANT TO SPECIFY #
182###############################################################################
183
76ea0716
PH
184# If you need extra header file search paths on all compiles, put the -I
185# options in INCLUDE. If you want the extra searches only for certain
186# parts of the build, see more specific xxx_INCLUDE variables below.
187
188# INCLUDE=-I/example/include
189
059ec3d9
PH
190# You need to specify some routers and transports if you want the Exim that you
191# are building to be capable of delivering mail. You almost certainly need at
192# least one type of lookup. You should consider whether you want to build
193# the Exim monitor or not.
194
195
196#------------------------------------------------------------------------------
197# These settings determine which individual router drivers are included in the
198# Exim binary. There are no defaults in the code; those routers that are wanted
199# must be defined here by setting the appropriate variables to the value "yes".
200# Including a router in the binary does not cause it to be used automatically.
201# It has also to be configured in the run time configuration file. By
202# commenting out those you know you don't want to use, you can make the binary
203# a bit smaller. If you are unsure, leave all of these included for now.
204
205ROUTER_ACCEPT=yes
206ROUTER_DNSLOOKUP=yes
207ROUTER_IPLITERAL=yes
208ROUTER_MANUALROUTE=yes
209ROUTER_QUERYPROGRAM=yes
210ROUTER_REDIRECT=yes
211
212# This one is very special-purpose, so is not included by default.
213
214# ROUTER_IPLOOKUP=yes
215
216
217#------------------------------------------------------------------------------
218# These settings determine which individual transport drivers are included in
219# the Exim binary. There are no defaults; those transports that are wanted must
220# be defined here by setting the appropriate variables to the value "yes".
221# Including a transport in the binary does not cause it to be used
222# automatically. It has also to be configured in the run time configuration
223# file. By commenting out those you know you don't want to use, you can make
224# the binary a bit smaller. If you are unsure, leave all of these included for
225# now.
226
227TRANSPORT_APPENDFILE=yes
228TRANSPORT_AUTOREPLY=yes
229TRANSPORT_PIPE=yes
230TRANSPORT_SMTP=yes
231
232# This one is special-purpose, and commonly not required, so it is not
233# included by default.
234
235# TRANSPORT_LMTP=yes
236
237
238#------------------------------------------------------------------------------
239# The appendfile transport can write messages to local mailboxes in a number
240# of formats. The code for three specialist formats, maildir, mailstore, and
241# MBX, is included only when requested. If you do not know what this is about,
242# leave these settings commented out.
243
244# SUPPORT_MAILDIR=yes
245# SUPPORT_MAILSTORE=yes
246# SUPPORT_MBX=yes
247
248
249#------------------------------------------------------------------------------
e6d225ae
DW
250# See below for dynamic lookup modules.
251# LOOKUP_MODULE_DIR=/usr/lib/exim/lookups/
6545de78
PP
252# If not using package management but using this anyway, then think about how
253# you perform upgrades and revert them. You should consider the benefit of
254# embedding the Exim version number into LOOKUP_MODULE_DIR, so that you can
255# maintain two concurrent sets of modules.
e6d225ae 256
0a349494
PP
257# To build a module dynamically, you'll need to define CFLAGS_DYNAMIC for
258# your platform. Eg:
259# CFLAGS_DYNAMIC=-shared -rdynamic
260# CFLAGS_DYNAMIC=-shared -rdynamic -fPIC
261
e6d225ae 262#------------------------------------------------------------------------------
059ec3d9
PH
263# These settings determine which file and database lookup methods are included
264# in the binary. See the manual chapter entitled "File and database lookups"
265# for discussion. DBM and lsearch (linear search) are included by default. If
266# you are unsure about the others, leave them commented out for now.
267# LOOKUP_DNSDB does *not* refer to general mail routing using the DNS. It is
268# for the specialist case of using the DNS as a general database facility (not
269# common).
e6d225ae
DW
270# If set to "2" instead of "yes" then the corresponding lookup will be
271# built as a module and must be installed into LOOKUP_MODULE_DIR. You need to
272# add -export-dynamic -rdynamic to EXTRALIBS. You may also need to add -ldl to
273# EXTRALIBS so that dlopen() is available to Exim. You need to define
274# LOOKUP_MODULE_DIR above so the exim binary actually loads dynamic lookup
275# modules.
276# Also, instead of adding all the libraries/includes to LOOKUP_INCLUDE and
277# LOOKUP_LIBS, add them to the respective LOOKUP_*_INCLUDE and LOOKUP_*_LIBS
278# (where * is the name as given here in this list). That ensures that only
279# the dynamic library and not the exim binary will be linked against the
280# library.
281# NOTE: LDAP cannot be built as a module!
059ec3d9
PH
282
283LOOKUP_DBM=yes
284LOOKUP_LSEARCH=yes
663ee6d9 285LOOKUP_DNSDB=yes
059ec3d9
PH
286
287# LOOKUP_CDB=yes
059ec3d9
PH
288# LOOKUP_DSEARCH=yes
289# LOOKUP_IBASE=yes
290# LOOKUP_LDAP=yes
291# LOOKUP_MYSQL=yes
292# LOOKUP_NIS=yes
293# LOOKUP_NISPLUS=yes
294# LOOKUP_ORACLE=yes
295# LOOKUP_PASSWD=yes
296# LOOKUP_PGSQL=yes
13b685f9 297# LOOKUP_SQLITE=yes
059ec3d9
PH
298# LOOKUP_WHOSON=yes
299
300# These two settings are obsolete; all three lookups are compiled when
301# LOOKUP_LSEARCH is enabled. However, we retain these for backward
302# compatibility. Setting one forces LOOKUP_LSEARCH if it is not set.
303
304# LOOKUP_WILDLSEARCH=yes
305# LOOKUP_NWILDLSEARCH=yes
306
307
308#------------------------------------------------------------------------------
309# If you have set LOOKUP_LDAP=yes, you should set LDAP_LIB_TYPE to indicate
310# which LDAP library you have. Unfortunately, though most of their functions
311# are the same, there are minor differences. Currently Exim knows about four
312# LDAP libraries: the one from the University of Michigan (also known as
313# OpenLDAP 1), OpenLDAP 2, the Netscape SDK library, and the library that comes
314# with Solaris 7 onwards. Uncomment whichever of these you are using.
315
316# LDAP_LIB_TYPE=OPENLDAP1
317# LDAP_LIB_TYPE=OPENLDAP2
318# LDAP_LIB_TYPE=NETSCAPE
319# LDAP_LIB_TYPE=SOLARIS
320
321# If you don't set any of these, Exim assumes the original University of
322# Michigan (OpenLDAP 1) library.
323
324
325#------------------------------------------------------------------------------
8eb9f5bd
NM
326# The PCRE library is required for exim. There is no longer an embedded
327# version of the PCRE library included with the source code, instead you
328# must use a system library or build your own copy of PCRE.
329# In either case you must specify the library link info here. If the
330# PCRE header files are not in the standard search path you must also
331# modify the INCLUDE path (above)
332# The default setting of PCRE_LIBS should work on the vast majority of
333# systems
334
335PCRE_LIBS=-lpcre
336
337
338#------------------------------------------------------------------------------
059ec3d9
PH
339# Additional libraries and include directories may be required for some
340# lookup styles (e.g. LDAP, MYSQL or PGSQL). LOOKUP_LIBS is included only on
341# the command for linking Exim itself, not on any auxiliary programs. You
342# don't need to set LOOKUP_INCLUDE if the relevant directories are already
343# specified in INCLUDE. The settings below are just examples; -lpq is for
2050824c 344# PostgreSQL, -lgds is for Interbase, -lsqlite3 is for SQLite.
059ec3d9
PH
345
346# LOOKUP_INCLUDE=-I /usr/local/ldap/include -I /usr/local/mysql/include -I /usr/local/pgsql/include
2050824c
PH
347# LOOKUP_LIBS=-L/usr/local/lib -lldap -llber -lmysqlclient -lpq -lgds -lsqlite3
348
059ec3d9
PH
349
350#------------------------------------------------------------------------------
351# Compiling the Exim monitor: If you want to compile the Exim monitor, a
352# program that requires an X11 display, then EXIM_MONITOR should be set to the
353# value "eximon.bin". Comment out this setting to disable compilation of the
354# monitor. The locations of various X11 directories for libraries and include
355# files are defaulted in the OS/Makefile-Default file, but can be overridden in
356# local OS-specific make files.
357
358EXIM_MONITOR=eximon.bin
359
2050824c 360
8523533c
TK
361#------------------------------------------------------------------------------
362# Compiling Exim with content scanning support: If you want to compile Exim
363# with support for message body content scanning, set WITH_CONTENT_SCAN to
364# the value "yes". This will give you malware and spam scanning in the DATA ACL,
365# and the MIME ACL. Please read the documentation to learn more about these
366# features.
367
f7b63901 368# WITH_CONTENT_SCAN=yes
8523533c
TK
369
370# If you want to use the deprecated "demime" condition in the DATA ACL,
371# uncomment the line below. Doing so will also explicitly turn on the
372# WITH_CONTENT_SCAN option. If possible, use the MIME ACL instead of
373# the "demime" condition.
374
f7b63901 375# WITH_OLD_DEMIME=yes
8523533c 376
8544e77a
PP
377# If you're using ClamAV and are backporting fixes to an old version, instead
378# of staying current (which is the more usual approach) then you may need to
379# use an older API which uses a STREAM command, now deprecated, instead of
380# zINSTREAM. If you need to set this, please let the Exim developers know, as
381# if nobody reports a need for it, we'll remove this option and clean up the
382# code. zINSTREAM was introduced with ClamAV 0.95.
383#
384# WITH_OLD_CLAMAV_STREAM=yes
385
8523533c 386#------------------------------------------------------------------------------
a8c8d6b5
JJ
387# By default Exim includes code to support DKIM (DomainKeys Identified
388# Mail, RFC4871) signing and verification. Verification of signatures is
389# turned on by default. See the spec for information on conditionally
390# disabling it. To disable the inclusion of the entire feature, set
391# DISABLE_DKIM to "yes"
392
393# DISABLE_DKIM=yes
394
395
396#------------------------------------------------------------------------------
8523533c
TK
397# Compiling Exim with experimental features. These are documented in
398# experimental-spec.txt. "Experimental" means that the way these features are
f7b63901 399# implemented may still change. Backward compatibility is not guaranteed.
8523533c
TK
400
401# Uncomment the following lines to add SPF support. You need to have libspf2
402# installed on your system (www.libspf2.org). Depending on where it is installed
403# you may have to edit the CFLAGS and LDFLAGS lines.
8523533c 404
f7b63901
PH
405# EXPERIMENTAL_SPF=yes
406# CFLAGS += -I/usr/local/include
407# LDFLAGS += -lspf2
408
409# Uncomment the following lines to add SRS (Sender rewriting scheme) support.
8523533c
TK
410# You need to have libsrs_alt installed on your system (srs.mirtol.com).
411# Depending on where it is installed you may have to edit the CFLAGS and
412# LDFLAGS lines.
8523533c 413
f7b63901
PH
414# EXPERIMENTAL_SRS=yes
415# CFLAGS += -I/usr/local/include
416# LDFLAGS += -lsrs_alt
417
418# Uncomment the following lines to add Brightmail AntiSpam support. You need
8523533c
TK
419# to have the Brightmail client SDK installed. Please check the experimental
420# documentation for implementation details. You need to edit the CFLAGS and
421# LDFLAGS lines.
f7b63901
PH
422
423# EXPERIMENTAL_BRIGHTMAIL=yes
424# CFLAGS += -I/opt/brightmail/bsdk-6.0/include
12cdb9e7 425# LDFLAGS += -lxml2_single -lbmiclient_single -L/opt/brightmail/bsdk-6.0/lib
8523533c 426
059ec3d9
PH
427
428
429###############################################################################
430# THESE ARE THINGS YOU MIGHT WANT TO SPECIFY #
431###############################################################################
432
433# The items in this section are those that are commonly changed according to
434# the sysadmin's preferences, but whose defaults are often acceptable. The
435# first five are concerned with security issues, where differing levels of
436# paranoia are appropriate in different environments. Sysadmins also vary in
437# their views on appropriate levels of defence in these areas. If you do not
438# understand these issues, go with the defaults, which are used by many sites.
439
440
441#------------------------------------------------------------------------------
442# Although Exim is normally a setuid program, owned by root, it refuses to run
443# local deliveries as root by default. There is a runtime option called
444# "never_users" which lists the users that must never be used for local
445# deliveries. There is also the setting below, which provides a list that
446# cannot be overridden at runtime. This guards against problems caused by
447# unauthorized changes to the runtime configuration. You are advised not to
448# remove "root" from this option, but you can add other users if you want. The
926e1192 449# list is colon-separated. It must NOT contain any spaces.
059ec3d9 450
926e1192 451# FIXED_NEVER_USERS=root:bin:daemon
059ec3d9
PH
452FIXED_NEVER_USERS=root
453
454
455#------------------------------------------------------------------------------
c1d94452
DW
456# By default, Exim insists that its configuration file be owned by root. You
457# can specify one additional permitted owner here.
059ec3d9
PH
458
459# CONFIGURE_OWNER=
460
35edf2ff 461# If the configuration file is group-writeable, Exim insists by default that it
c1d94452 462# is owned by root. You can specify one additional permitted group owner here.
35edf2ff
PH
463
464# CONFIGURE_GROUP=
465
466# If you specify CONFIGURE_OWNER or CONFIGURE_GROUP as a name, this is looked
467# up at build time, and the uid or gid number is built into the binary.
468# However, you can specify that the lookup is deferred until runtime. In this
469# case, it is the name that is built into the binary. You can do this by a
470# setting of the form:
059ec3d9
PH
471
472# CONFIGURE_OWNER=ref:mail
35edf2ff 473# CONFIGURE_GROUP=ref:sysadmin
059ec3d9 474
35edf2ff
PH
475# In other words, put "ref:" in front of the user or group name. Although this
476# costs a bit of resource at runtime, it is convenient to use this feature when
477# building binaries that are to be run on multiple systems where the names may
478# refer to different uids or gids. It also allows you to build Exim on a system
479# where the relevant user or group is not defined.
059ec3d9
PH
480
481
482#------------------------------------------------------------------------------
483# The -C option allows Exim to be run with an alternate runtime configuration
cd25e41d
DW
484# file. When this is used by root, root privilege is retained by the binary
485# (for any other caller including the Exim user, it is dropped). You can
486# restrict the location of alternate configurations by defining a prefix below.
487# Any file used with -C must then start with this prefix (except that /dev/null
488# is also permitted if the caller is root, because that is used in the install
489# script). If the prefix specifies a directory that is owned by root, a
490# compromise of the Exim account does not permit arbitrary alternate
491# configurations to be used. The prefix can be more restrictive than just a
492# directory (the second example).
059ec3d9
PH
493
494# ALT_CONFIG_PREFIX=/some/directory/
495# ALT_CONFIG_PREFIX=/some/directory/exim.conf-
496
497
498#------------------------------------------------------------------------------
261dc43e
DW
499# When a user other than root uses the -C option to override the configuration
500# file (including the Exim user when re-executing Exim to regain root
501# privileges for local message delivery), this will normally cause Exim to
90b6341f
DW
502# drop root privileges. The TRUSTED_CONFIG_LIST option, specifies a file which
503# contains a list of trusted configuration filenames, one per line. If the -C
504# option is used by the Exim user or by the user specified in the
505# CONFIGURE_OWNER setting, to specify a configuration file which is listed in
506# the TRUSTED_CONFIG_LIST file, then root privileges are not dropped by Exim.
507
508# TRUSTED_CONFIG_LIST=/usr/exim/trusted_configs
261dc43e
DW
509
510
511#------------------------------------------------------------------------------
059ec3d9
PH
512# Uncommenting this option disables the use of the -D command line option,
513# which changes the values of macros in the runtime configuration file.
514# This is another protection against somebody breaking into the Exim account.
515
516# DISABLE_D_OPTION=yes
517
518
519#------------------------------------------------------------------------------
a7cbbf50
PP
520# By contrast, you might be maintaining a system which relies upon the ability
521# to override values with -D and assumes that these will be passed through to
522# the delivery processes. As of Exim 4.73, this is no longer the case by
523# default. Going forward, we strongly recommend that you use a shim Exim
cc5fdbc2 524# configuration file owned by root stored under TRUSTED_CONFIG_LIST.
a7cbbf50
PP
525# That shim can set macros before .include'ing your main configuration file.
526#
527# As a strictly transient measure to ease migration to 4.73, the
528# WHITELIST_D_MACROS value definies a colon-separated list of macro-names
43236f35 529# which are permitted to be overridden from the command-line which will be
a7cbbf50
PP
530# honoured by the Exim user. So these are macros that can persist to delivery
531# time.
532# Examples might be -DTLS or -DSPOOL=/some/dir. The values on the
533# command-line are filtered to only permit: [A-Za-z0-9_/.-]*
534#
535# This option is highly likely to be removed in a future release. It exists
536# only to make 4.73 as easy as possible to migrate to. If you use it, we
537# encourage you to schedule time to rework your configuration to not depend
538# upon it. Most people should not need to use this.
539#
540# By default, no macros are whitelisted for -D usage.
541
542# WHITELIST_D_MACROS=TLS:SPOOL
543
544#------------------------------------------------------------------------------
059ec3d9
PH
545# Exim has support for the AUTH (authentication) extension of the SMTP
546# protocol, as defined by RFC 2554. If you don't know what SMTP authentication
547# is, you probably won't want to include this code, so you should leave these
548# settings commented out. If you do want to make use of SMTP authentication,
549# you must uncomment at least one of the following, so that appropriate code is
550# included in the Exim binary. You will then need to set up the run time
551# configuration to make use of the mechanism(s) selected.
552
553# AUTH_CRAM_MD5=yes
554# AUTH_CYRUS_SASL=yes
14aa5a05 555# AUTH_DOVECOT=yes
44bbabb5 556# AUTH_GSASL=yes
059ec3d9
PH
557# AUTH_PLAINTEXT=yes
558# AUTH_SPA=yes
559
560
561#------------------------------------------------------------------------------
562# If you specified AUTH_CYRUS_SASL above, you should ensure that you have the
563# Cyrus SASL library installed before trying to build Exim, and you probably
44bbabb5 564# want to uncomment the first line below. Similarly for GNU SASL.
059ec3d9
PH
565
566# AUTH_LIBS=-lsasl2
44bbabb5 567# AUTH_LIBS=-lgsasl
059ec3d9
PH
568
569
570#------------------------------------------------------------------------------
571# When Exim is decoding MIME "words" in header lines, most commonly for use
572# in the $header_xxx expansion, it converts any foreign character sets to the
573# one that is set in the headers_charset option. The default setting is
574# defined by this setting:
575
576HEADERS_CHARSET="ISO-8859-1"
577
578# If you are going to make use of $header_xxx expansions in your configuration
579# file, or if your users are going to use them in filter files, and the normal
580# character set on your host is something other than ISO-8859-1, you might
581# like to specify a different default here. This value can be overridden in
582# the runtime configuration, and it can also be overridden in individual filter
583# files.
584#
585# IMPORTANT NOTE: The iconv() function is needed for character code
586# conversions. Please see the next item...
587
588
589#------------------------------------------------------------------------------
590# Character code conversions are possible only if the iconv() function is
591# installed on your operating system. There are two places in Exim where this
592# is relevant: (a) The $header_xxx expansion (see the previous item), and (b)
593# the Sieve filter support. For those OS where iconv() is known to be installed
594# as standard, the file in OS/Makefile-xxxx contains
595#
596# HAVE_ICONV=yes
597#
598# If you are not using one of those systems, but have installed iconv(), you
599# need to uncomment that line above. In some cases, you may find that iconv()
600# and its header file are not in the default places. You might need to use
601# something like this:
602#
603# HAVE_ICONV=yes
604# CFLAGS=-O -I/usr/local/include
605# EXTRALIBS_EXIM=-L/usr/local/lib -liconv
606#
607# but of course there may need to be other things in CFLAGS and EXTRALIBS_EXIM
608# as well.
609
610
611#------------------------------------------------------------------------------
612# The passwords for user accounts are normally encrypted with the crypt()
613# function. Comparisons with encrypted passwords can be done using Exim's
614# "crypteq" expansion operator. (This is commonly used as part of the
615# configuration of an authenticator for use with SMTP AUTH.) At least one
616# operating system has an extended function called crypt16(), which uses up to
617# 16 characters of a password (the normal crypt() uses only the first 8). Exim
96c065cb 618# supports the use of crypt16() as well as crypt() but note the warning below.
059ec3d9
PH
619
620# You can always indicate a crypt16-encrypted password by preceding it with
621# "{crypt16}". If you want the default handling (without any preceding
622# indicator) to use crypt16(), uncomment the following line:
623
624# DEFAULT_CRYPT=crypt16
625
626# If you do that, you can still access the basic crypt() function by preceding
627# an encrypted password with "{crypt}". For more details, see the description
628# of the "crypteq" condition in the manual chapter on string expansions.
629
96c065cb
PH
630# Some operating systems do not include a crypt16() function, so Exim has one
631# of its own, which it uses unless HAVE_CRYPT16 is defined. Normally, that will
632# be set in an OS-specific Makefile for the OS that have such a function, so
633# you should not need to bother with it.
634
635# *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING ***
636# It turns out that the above is not entirely accurate. As well as crypt16()
637# there is a function called bigcrypt() that some operating systems have. This
638# may or may not use the same algorithm, and both of them may be different to
639# Exim's built-in crypt16() that is used unless HAVE_CRYPT16 is defined.
640#
641# However, since there is now a move away from the traditional crypt()
642# functions towards using SHA1 and other algorithms, tidying up this area of
643# Exim is seen as very low priority. In practice, if you need to, you can
644# define DEFAULT_CRYPT to the name of any function that has the same interface
645# as the traditional crypt() function.
646# *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING ***
059ec3d9
PH
647
648
649#------------------------------------------------------------------------------
650# Exim can be built to support the SMTP STARTTLS command, which implements
651# Transport Layer Security using SSL (Secure Sockets Layer). To do this, you
652# must install the OpenSSL library package or the GnuTLS library. Exim contains
653# no cryptographic code of its own. Uncomment the following lines if you want
654# to build Exim with TLS support. If you don't know what this is all about,
655# leave these settings commented out.
656
657# This setting is required for any TLS support (either OpenSSL or GnuTLS)
658# SUPPORT_TLS=yes
659
660# Uncomment this setting if you are using OpenSSL
661# TLS_LIBS=-lssl -lcrypto
662
663# Uncomment these settings if you are using GnuTLS
664# USE_GNUTLS=yes
665# TLS_LIBS=-lgnutls -ltasn1 -lgcrypt
666
667# If you are running Exim as a server, note that just building it with TLS
668# support is not all you need to do. You also need to set up a suitable
669# certificate, and tell Exim about it by means of the tls_certificate
670# and tls_privatekey run time options. You also need to set tls_advertise_hosts
671# to specify the hosts to which Exim advertises TLS support. On the other hand,
672# if you are running Exim only as a client, building it with TLS support
673# is all you need to do.
674
675# Additional libraries and include files are required for both OpenSSL and
676# GnuTLS. The TLS_LIBS settings above assume that the libraries are installed
677# with all your other libraries. If they are in a special directory, you may
678# need something like
679
680# TLS_LIBS=-L/usr/local/openssl/lib -lssl -lcrypto
681# or
682# TLS_LIBS=-L/opt/gnu/lib -lgnutls -ltasn1 -lgcrypt
683
684# TLS_LIBS is included only on the command for linking Exim itself, not on any
685# auxiliary programs. If the include files are not in a standard place, you can
686# set TLS_INCLUDE to specify where they are, for example:
687
688# TLS_INCLUDE=-I/usr/local/openssl/include/
689# or
690# TLS_INCLUDE=-I/opt/gnu/include
691
692# You don't need to set TLS_INCLUDE if the relevant directories are already
693# specified in INCLUDE.
694
695
696#------------------------------------------------------------------------------
697# The default distribution of Exim contains only the plain text form of the
698# documentation. Other forms are available separately. If you want to install
699# the documentation in "info" format, first fetch the Texinfo documentation
700# sources from the ftp directory and unpack them, which should create files
701# with the extension "texinfo" in the doc directory. You may find that the
702# version number of the texinfo files is different to your Exim version number,
703# because the main documentation isn't updated as often as the code. For
704# example, if you have Exim version 4.43, the source tarball upacks into a
705# directory called exim-4.43, but the texinfo tarball unpacks into exim-4.40.
706# In this case, move the contents of exim-4.40/doc into exim-4.43/doc after you
707# have unpacked them. Then set INFO_DIRECTORY to the location of your info
708# directory. This varies from system to system, but is often /usr/share/info.
709# Once you have done this, "make install" will build the info files and
710# install them in the directory you have defined.
711
712# INFO_DIRECTORY=/usr/share/info
713
714
715#------------------------------------------------------------------------------
716# Exim log directory and files: Exim creates several log files inside a
717# single log directory. You can define the directory and the form of the
718# log file name here. If you do not set anything, Exim creates a directory
719# called "log" inside its spool directory (see SPOOL_DIRECTORY above) and uses
720# the filenames "mainlog", "paniclog", and "rejectlog". If you want to change
721# this, you can set LOG_FILE_PATH to a path name containing one occurrence of
722# %s. This will be replaced by one of the strings "main", "panic", or "reject"
723# to form the final file names. Some installations may want something like this:
724
725# LOG_FILE_PATH=/var/log/exim_%slog
726
727# which results in files with names /var/log/exim_mainlog, etc. The directory
728# in which the log files are placed must exist; Exim does not try to create
729# it for itself. It is also your responsibility to ensure that Exim is capable
730# of writing files using this path name. The Exim user (see EXIM_USER above)
731# must be able to create and update files in the directory you have specified.
732
733# You can also configure Exim to use syslog, instead of or as well as log
734# files, by settings such as these
735
736# LOG_FILE_PATH=syslog
737# LOG_FILE_PATH=syslog:/var/log/exim_%slog
738
739# The first of these uses only syslog; the second uses syslog and also writes
740# to log files. Do not include white space in such a setting as it messes up
741# the building process.
742
743
744#------------------------------------------------------------------------------
745# When logging to syslog, the following option caters for syslog replacements
746# that are able to accept log entries longer than the 1024 characters allowed
747# by RFC 3164. It is up to you to make sure your syslog daemon can handle this.
748# Non-printable characters are usually unacceptable regardless, so log entries
749# are still split on newline characters.
750
751# SYSLOG_LONG_LINES=yes
752
753# If you are not interested in the process identifier (pid) of the Exim that is
754# making the call to syslog, then comment out the following line.
755
756SYSLOG_LOG_PID=yes
757
758
759#------------------------------------------------------------------------------
760# Cycling log files: this variable specifies the maximum number of old
761# log files that are kept by the exicyclog log-cycling script. You don't have
762# to use exicyclog. If your operating system has other ways of cycling log
763# files, you can use them instead. The exicyclog script isn't run by default;
764# you have to set up a cron job for it if you want it.
765
766EXICYCLOG_MAX=10
767
768
769#------------------------------------------------------------------------------
770# The compress command is used by the exicyclog script to compress old log
771# files. Both the name of the command and the suffix that it adds to files
772# need to be defined here. See also the EXICYCLOG_MAX configuration.
773
774COMPRESS_COMMAND=/usr/bin/gzip
775COMPRESS_SUFFIX=gz
776
777
778#------------------------------------------------------------------------------
779# If the exigrep utility is fed compressed log files, it tries to uncompress
780# them using this command.
781
782ZCAT_COMMAND=/usr/bin/zcat
783
784
785#------------------------------------------------------------------------------
786# Compiling in support for embedded Perl: If you want to be able to
787# use Perl code in Exim's string manipulation language and you have Perl
788# (version 5.004 or later) installed, set EXIM_PERL to perl.o. Using embedded
789# Perl costs quite a lot of resources. Only do this if you really need it.
790
791# EXIM_PERL=perl.o
792
793
794#------------------------------------------------------------------------------
1a46a8c5
PH
795# Support for dynamically-loaded string expansion functions via ${dlfunc. If
796# you are using gcc the dynamically-loaded object must be compiled with the
797# -shared option, and you will need to add -export-dynamic to EXTRALIBS so
1ea70a03 798# that the local_scan API is made available by the linker. You may also need
612ba564 799# to add -ldl to EXTRALIBS so that dlopen() is available to Exim.
1a46a8c5
PH
800
801# EXPAND_DLFUNC=yes
802
803
804#------------------------------------------------------------------------------
059ec3d9
PH
805# Exim has support for PAM (Pluggable Authentication Modules), a facility
806# which is available in the latest releases of Solaris and in some GNU/Linux
807# distributions (see http://ftp.kernel.org/pub/linux/libs/pam/). The Exim
808# support, which is intended for use in conjunction with the SMTP AUTH
809# facilities, is included only when requested by the following setting:
810
811# SUPPORT_PAM=yes
812
813# You probably need to add -lpam to EXTRALIBS, and in some releases of
814# GNU/Linux -ldl is also needed.
815
816
817#------------------------------------------------------------------------------
818# Support for authentication via Radius is also available. The Exim support,
819# which is intended for use in conjunction with the SMTP AUTH facilities,
820# is included only when requested by setting the following parameter to the
821# location of your Radius configuration file:
822
823# RADIUS_CONFIG_FILE=/etc/radiusclient/radiusclient.conf
824# RADIUS_CONFIG_FILE=/etc/radius.conf
825
826# If you have set RADIUS_CONFIG_FILE, you should also set one of these to
827# indicate which RADIUS library is used:
059ec3d9
PH
828
829# RADIUS_LIB_TYPE=RADIUSCLIENT
7766a4f0 830# RADIUS_LIB_TYPE=RADIUSCLIENTNEW
059ec3d9
PH
831# RADIUS_LIB_TYPE=RADLIB
832
7766a4f0
PH
833# RADIUSCLIENT is the radiusclient library; you probably need to add
834# -lradiusclient to EXTRALIBS.
835#
836# The API for the radiusclient library was changed at release 0.4.0.
837# Unfortunately, the header file does not define a version number that clients
838# can use to support both the old and new APIs. If you are using version 0.4.0
839# or later of the radiusclient library, you should use RADIUSCLIENTNEW.
840#
841# RADLIB is the Radius library that comes with FreeBSD (the header file is
842# called radlib.h); you probably need to add -lradius to EXTRALIBS.
843#
844# If you do not set RADIUS_LIB_TYPE, Exim assumes the radiusclient library,
845# using the original API.
059ec3d9
PH
846
847
848#------------------------------------------------------------------------------
849# Support for authentication via the Cyrus SASL pwcheck daemon is available.
850# Note, however, that pwcheck is now deprecated in favour of saslauthd (see
851# next item). The Exim support for pwcheck, which is intented for use in
852# conjunction with the SMTP AUTH facilities, is included only when requested by
853# setting the following parameter to the location of the pwcheck daemon's
854# socket.
855#
856# There is no need to install all of SASL on your system. You just need to run
857# ./configure --with-pwcheck, cd to the pwcheck directory within the sources,
858# make and make install. You must create the socket directory (default
859# /var/pwcheck) and chown it to exim's user and group. Once you have installed
860# pwcheck, you should arrange for it to be started by root at boot time.
861
862# CYRUS_PWCHECK_SOCKET=/var/pwcheck/pwcheck
863
864
865#------------------------------------------------------------------------------
866# Support for authentication via the Cyrus SASL saslauthd daemon is available.
867# The Exim support, which is intented for use in conjunction with the SMTP AUTH
868# facilities, is included only when requested by setting the following
869# parameter to the location of the saslauthd daemon's socket.
870#
871# There is no need to install all of SASL on your system. You just need to run
872# ./configure --with-saslauthd (and any other options you need, for example, to
873# select or deselect authentication mechanisms), cd to the saslauthd directory
874# within the sources, make and make install. You must create the socket
875# directory (default /var/state/saslauthd) and chown it to exim's user and
876# group. Once you have installed saslauthd, you should arrange for it to be
877# started by root at boot time.
878
879# CYRUS_SASLAUTHD_SOCKET=/var/state/saslauthd/mux
880
881
882#------------------------------------------------------------------------------
883# TCP wrappers: If you want to use tcpwrappers from within Exim, uncomment
884# this setting. See the manual section entitled "Use of tcpwrappers" in the
885# chapter on building and installing Exim.
886#
887# USE_TCP_WRAPPERS=yes
888#
889# You may well also have to specify a local "include" file and an additional
890# library for TCP wrappers, so you probably need something like this:
891#
892# USE_TCP_WRAPPERS=yes
893# CFLAGS=-O -I/usr/local/include
894# EXTRALIBS_EXIM=-L/usr/local/lib -lwrap
895#
896# but of course there may need to be other things in CFLAGS and EXTRALIBS_EXIM
897# as well.
5dc43717
JJ
898#
899# To use a name other than exim in the tcpwrappers config file,
900# e.g. if you're running multiple daemons with different access lists,
901# or multiple MTAs with the same access list, define
902# TCP_WRAPPERS_DAEMON_NAME accordingly
903#
904# TCP_WRAPPERS_DAEMON_NAME="exim"
059ec3d9
PH
905
906
907#------------------------------------------------------------------------------
908# The default action of the exim_install script (which is run by "make
909# install") is to install the Exim binary with a unique name such as
910# exim-4.43-1, and then set up a symbolic link called "exim" to reference it,
911# moving the symbolic link from any previous version. If you define NO_SYMLINK
912# (the value doesn't matter), the symbolic link is not created or moved. You
913# will then have to "turn Exim on" by setting up the link manually.
914
915# NO_SYMLINK=yes
916
917
918#------------------------------------------------------------------------------
919# Another default action of the install script is to install a default runtime
920# configuration file if one does not exist. This configuration has a router for
921# expanding system aliases. The default assumes that these aliases are kept
922# in the traditional file called /etc/aliases. If such a file does not exist,
923# the installation script creates one that contains just comments (no actual
924# aliases). The following setting can be changed to specify a different
925# location for the system alias file.
926
927SYSTEM_ALIASES_FILE=/etc/aliases
928
929
930#------------------------------------------------------------------------------
931# There are some testing options (-be, -bt, -bv) that read data from the
932# standard input when no arguments are supplied. By default, the input lines
933# are read using the standard fgets() function. This does not support line
934# editing during interactive input (though the terminal's "erase" character
935# works as normal). If your operating system has the readline() function, and
936# in addition supports dynamic loading of library functions, you can cause
937# Exim to use readline() for the -be testing option (only) by uncommenting the
938# following setting. Dynamic loading is used so that the library is loaded only
939# when the -be testing option is given; by the time the loading occurs,
940# Exim has given up its root privilege and is running as the calling user. This
941# is the reason why readline() is NOT supported for -bt and -bv, because Exim
942# runs as root or as exim, respectively, for those options. When USE_READLINE
943# is "yes", as well as supporting line editing, a history of input lines in the
944# current run is maintained.
945
946# USE_READLINE=yes
947
79b5812b 948# You may need to add -ldl to EXTRALIBS when you set USE_READLINE=yes.
b08b24c8
PH
949# Note that this option adds to the size of the Exim binary, because the
950# dynamic loading library is not otherwise included.
951
059ec3d9
PH
952
953
954###############################################################################
955# THINGS YOU ALMOST NEVER NEED TO MENTION #
956###############################################################################
957
958# The settings in this section are available for use in special circumstances.
959# In the vast majority of installations you need not change anything below.
960
961
962#------------------------------------------------------------------------------
963# The following commands live in different places in some OS. Either the
964# ultimate default settings, or the OS-specific files should already point to
965# the right place, but they can be overridden here if necessary. These settings
966# are used when building various scripts to ensure that the correct paths are
967# used when the scripts are run. They are not used in the Makefile itself. Perl
968# is not necessary for running Exim unless you set EXIM_PERL (see above) to get
969# it embedded, but there are some utilities that are Perl scripts. If you
970# haven't got Perl, Exim will still build and run; you just won't be able to
971# use those utilities.
972
973# CHOWN_COMMAND=/usr/bin/chown
974# CHGRP_COMMAND=/usr/bin/chgrp
c2f9a1ee 975# CHMOD_COMMAND=/usr/bin/chmod
059ec3d9
PH
976# MV_COMMAND=/bin/mv
977# RM_COMMAND=/bin/rm
c2f9a1ee 978# TOUCH_COMMAND=/usr/bin/touch
059ec3d9
PH
979# PERL_COMMAND=/usr/bin/perl
980
981
982#------------------------------------------------------------------------------
983# The following macro can be used to change the command for building a library
984# of functions. By default the "ar" command is used, with options "cq".
985# Only in rare circumstances should you need to change this.
986
987# AR=ar cq
988
989
990#------------------------------------------------------------------------------
991# In some operating systems, the value of the TMPDIR environment variable
992# controls where temporary files are created. Exim does not make use of
993# temporary files, except when delivering to MBX mailboxes. However, if Exim
994# calls any external libraries (e.g. DBM libraries), they may use temporary
995# files, and thus be influenced by the value of TMPDIR. For this reason, when
996# Exim starts, it checks the environment for TMPDIR, and if it finds it is set,
997# it replaces the value with what is defined here. Commenting this setting
998# suppresses the check altogether.
999
1000TMPDIR="/tmp"
1001
1002
1003#------------------------------------------------------------------------------
1004# The following macros can be used to change the default modes that are used
1005# by the appendfile transport. In most installations the defaults are just
1006# fine, and in any case, you can change particular instances of the transport
1007# at run time if you want.
1008
1009# APPENDFILE_MODE=0600
1010# APPENDFILE_DIRECTORY_MODE=0700
1011# APPENDFILE_LOCKFILE_MODE=0600
1012
1013
1014#------------------------------------------------------------------------------
1015# In some installations there may be multiple machines sharing file systems,
1016# where a different configuration file is required for Exim on the different
1017# machines. If CONFIGURE_FILE_USE_NODE is defined, then Exim will first look
1018# for a configuration file whose name is that defined by CONFIGURE_FILE,
1019# with the node name obtained by uname() tacked on the end, separated by a
1020# period (for example, /usr/exim/configure.host.in.some.domain). If this file
1021# does not exist, then the bare configuration file name is tried.
1022
1023# CONFIGURE_FILE_USE_NODE=yes
1024
1025
1026#------------------------------------------------------------------------------
1027# In some esoteric configurations two different versions of Exim are run,
1028# with different setuid values, and different configuration files are required
1029# to handle the different cases. If CONFIGURE_FILE_USE_EUID is defined, then
1030# Exim will first look for a configuration file whose name is that defined
1031# by CONFIGURE_FILE, with the effective uid tacked on the end, separated by
1032# a period (for eximple, /usr/exim/configure.0). If this file does not exist,
1033# then the bare configuration file name is tried. In the case when both
1034# CONFIGURE_FILE_USE_EUID and CONFIGURE_FILE_USE_NODE are set, four files
1035# are tried: <name>.<euid>.<node>, <name>.<node>, <name>.<euid>, and <name>.
1036
1037# CONFIGURE_FILE_USE_EUID=yes
1038
1039
1040#------------------------------------------------------------------------------
1041# The size of the delivery buffers: These specify the sizes (in bytes) of
1042# the buffers that are used when copying a message from the spool to a
1043# destination. There is rarely any need to change these values.
1044
1045# DELIVER_IN_BUFFER_SIZE=8192
1046# DELIVER_OUT_BUFFER_SIZE=8192
1047
1048
1049#------------------------------------------------------------------------------
1050# The mode of the database directory: Exim creates a directory called "db"
1051# in its spool directory, to hold its databases of hints. This variable
1052# determines the mode of the created directory. The default value in the
1053# source is 0750.
1054
1055# EXIMDB_DIRECTORY_MODE=0750
1056
1057
1058#------------------------------------------------------------------------------
1059# Database file mode: The mode of files created in the "db" directory defaults
1060# to 0640 in the source, and can be changed here.
1061
1062# EXIMDB_MODE=0640
1063
1064
1065#------------------------------------------------------------------------------
1066# Database lock file mode: The mode of zero-length files created in the "db"
1067# directory to use for locking purposes defaults to 0640 in the source, and
1068# can be changed here.
1069
1070# EXIMDB_LOCKFILE_MODE=0640
1071
1072
1073#------------------------------------------------------------------------------
1074# This parameter sets the maximum length of the header portion of a message
1075# that Exim is prepared to process. The default setting is one megabyte. The
1076# limit exists in order to catch rogue mailers that might connect to your SMTP
1077# port, start off a header line, and then just pump junk at it for ever. The
1078# message_size_limit option would also catch this, but it may not be set.
1079# The value set here is the default; it can be changed at runtime.
1080
1081# HEADER_MAXSIZE="(1024*1024)"
1082
1083
1084#------------------------------------------------------------------------------
1085# The mode of the input directory: The input directory is where messages are
1086# kept while awaiting delivery. Exim creates it if necessary, using a mode
1087# which can be defined here (default 0750).
1088
1089# INPUT_DIRECTORY_MODE=0750
1090
1091
1092#------------------------------------------------------------------------------
1093# The mode of Exim's log directory, when it is created by Exim inside the spool
1094# directory, defaults to 0750 but can be changed here.
1095
1096# LOG_DIRECTORY_MODE=0750
1097
1098
1099#------------------------------------------------------------------------------
1100# The log files themselves are created as required, with a mode that defaults
1101# to 0640, but which can be changed here.
1102
1103# LOG_MODE=0640
1104
1105
1106#------------------------------------------------------------------------------
1107# The TESTDB lookup is for performing tests on the handling of lookup results,
1108# and is not useful for general running. It should be included only when
1109# debugging the code of Exim.
1110
1111# LOOKUP_TESTDB=yes
1112
1113
1114#------------------------------------------------------------------------------
1115# /bin/sh is used by default as the shell in which to run commands that are
1116# defined in the makefiles. This can be changed if necessary, by uncommenting
1117# this line and specifying another shell, but note that a Bourne-compatible
1118# shell is expected.
1119
1120# MAKE_SHELL=/bin/sh
1121
1122
1123#------------------------------------------------------------------------------
1124# The maximum number of named lists of each type (address, domain, host, and
1125# local part) can be increased by changing this value. It should be set to
1126# a multiple of 16.
1127
1128# MAX_NAMED_LIST=16
1129
1130
1131#------------------------------------------------------------------------------
1132# Network interfaces: Unless you set the local_interfaces option in the runtime
1133# configuration file to restrict Exim to certain interfaces only, it will run
1134# code to find all the interfaces there are on your host. Unfortunately,
1135# the call to the OS that does this requires a buffer large enough to hold
1136# data for all the interfaces - it was designed in the days when a host rarely
1137# had more than three or four interfaces. Nowadays hosts can have very many
1138# virtual interfaces running on the same hardware. If you have more than 250
1139# virtual interfaces, you will need to uncomment this setting and increase the
1140# value.
1141
1142# MAXINTERFACES=250
1143
1144
1145#------------------------------------------------------------------------------
1146# Per-message logs: While a message is in the process of being delivered,
1147# comments on its progress are written to a message log, for the benefit of
1148# human administrators. These logs are held in a directory called "msglog"
1149# in the spool directory. Its mode defaults to 0750, but can be changed here.
1150# The message log directory is also used for storing files that are used by
1151# transports for returning data to a message's sender (see the "return_output"
1152# option for transports).
1153
1154# MSGLOG_DIRECTORY_MODE=0750
1155
1156
1157#------------------------------------------------------------------------------
1158# There are three options which are used when compiling the Perl interface and
1159# when linking with Perl. The default values for these are placed automatically
1160# at the head of the Makefile by the script which builds it. However, if you
1161# want to override them, you can do so here.
1162
1163# PERL_CC=
1164# PERL_CCOPTS=
1165# PERL_LIBS=
1166
1167
1168#------------------------------------------------------------------------------
1169# Identifying the daemon: When an Exim daemon starts up, it writes its pid
1170# (process id) to a file so that it can easily be identified. The path of the
1171# file can be specified here. Some installations may want something like this:
1172
1173# PID_FILE_PATH=/var/lock/exim.pid
1174
1175# If PID_FILE_PATH is not defined, Exim writes a file in its spool directory
1176# using the name "exim-daemon.pid".
1177
1178# If you start up a daemon without the -bd option (for example, with just
1179# the -q15m option), a pid file is not written. Also, if you override the
1180# configuration file with the -oX option, no pid file is written. In other
1181# words, the pid file is written only for a "standard" daemon.
1182
1183
1184#------------------------------------------------------------------------------
1185# If Exim creates the spool directory, it is given this mode, defaulting in the
1186# source to 0750.
1187
1188# SPOOL_DIRECTORY_MODE=0750
1189
1190
1191#------------------------------------------------------------------------------
1192# The mode of files on the input spool which hold the contents of messages can
1193# be changed here. The default is 0640 so that information from the spool is
1194# available to anyone who is a member of the Exim group.
1195
1196# SPOOL_MODE=0640
1197
1198
1199#------------------------------------------------------------------------------
1200# Moving frozen messages: If the following is uncommented, Exim is compiled
1201# with support for automatically moving frozen messages out of the main spool
1202# directory, a facility that is found useful by some large installations. A
1203# run time option is required to cause the moving actually to occur. Such
1204# messages become "invisible" to the normal management tools.
1205
1206# SUPPORT_MOVE_FROZEN_MESSAGES=yes
1207
54fc8428
PH
1208
1209#------------------------------------------------------------------------------
82c6910a
PP
1210# Expanding match_* second paramters: BE CAREFUL IF ENABLING THIS!
1211# It has proven too easy in practice for administrators to configure security
1212# problems into their Exim install, by treating match_domain{}{} and friends
1213# as a form of string comparison, where the second string comes from untrusted
1214# data. Because these options take lists, which can include lookup;LOOKUPDATA
1215# style elements, a foe can then cause Exim to, eg, execute an arbitrary MySQL
1216# query, dropping tables.
1217# From Exim 4.77 onwards, the second parameter is not expanded; it can still
1218# be a list literal, or a macro, or a named list reference. There is also
1219# the new expansion condition "inlisti" which does expand the second parameter,
1220# but treats it as a list of strings; also, there's "eqi" which is probably
1221# what is normally wanted.
1222#
1223# If you really need to have the old behaviour, know what you are doing and
1224# will not complain if your system is compromised as a result of doing so, then
1225# uncomment this option to get the old behaviour back.
1226
1227# EXPAND_LISTMATCH_RHS=yes
1228
1229#------------------------------------------------------------------------------
54fc8428
PH
1230# Disabling the use of fsync(): DO NOT UNCOMMENT THE FOLLOWING LINE unless you
1231# really, really, really know what you are doing. And even then, think again.
1232# You should never uncomment this when compiling a binary for distribution.
1233# Use it only when compiling Exim for your own use.
1234#
1235# Uncommenting this line enables the use of a runtime option called
1236# disable_fsync, which can be used to stop Exim using fsync() to ensure that
1237# files are written to disc before proceeding. When this is disabled, crashes
1238# and hardware problems such as power outages can cause data to be lost. This
1239# feature should only be used in very exceptional circumstances. YOU HAVE BEEN
1240# WARNED.
1241
1242# ENABLE_DISABLE_FSYNC=yes
1243
059ec3d9 1244# End of EDITME for Exim 4.