1 diff -urN exim-4.20-orig/Local/Makefile exim-4.20/Local/Makefile
2 --- exim-4.20-orig/Local/Makefile 2003-07-30 16:33:47.000000000 -0600
3 +++ exim-4.20/Local/Makefile 2003-07-30 16:38:13.000000000 -0600
13 diff -urN exim-4.20-orig/Local/Makefile~ exim-4.20/Local/Makefile~
14 --- exim-4.20-orig/Local/Makefile~ 1969-12-31 17:00:00.000000000 -0700
15 +++ exim-4.20/Local/Makefile~ 2003-07-30 16:35:46.000000000 -0600
17 +##################################################
18 +# The Exim mail transport agent #
19 +##################################################
21 +# This is the template for Exim's main build-time configuration file. It
22 +# contains settings that are independent of any operating system. These are
23 +# things that are mostly sysadmin choices. The items below are divided into
24 +# those you must specify, those you probably want to specify, those you might
25 +# often want to specify, and those that you almost never need to mention.
27 +# Edit this file and save the result to a file called Local/Makefile within the
28 +# Exim distribution directory before running the "make" command.
30 +# Things that depend on the operating system have default settings in
31 +# OS/Makefile-Default, but these are overridden for some OS by files called
32 +# called OS/Makefile-<osname>. You can further override these by creating files
33 +# called Local/Makefile-<osname>, where "<osname>" stands for the name of your
34 +# operating system - look at the names in the OS directory to see which names
37 +# However, if you are building Exim for a single OS only, you don't need to
38 +# worry about setting up Local/Makefile-<osname>. Any build-time configuration
39 +# settings you require can in fact be placed in the one file called
40 +# Local/Makefile. It is only if you are building for several OS from the same
41 +# source files that you need to worry about splitting off your own OS-dependent
42 +# settings into separate files. (There's more explanation about how this all
43 +# works in the toplevel README file, under "Modifying the building process", as
44 +# well as in the Exim specification.)
46 +# One OS-specific thing that may need to be changed is the command for running
47 +# the C compiler; the overall default is gcc, but some OS Makefiles specify cc.
48 +# You can override anything that is set by putting CC=whatever in your
51 +# NOTE: You should never need to edit any of the distributed Makefiles; all
52 +# overriding can be done in your Local/Makefile(s). This will make it easier
53 +# for you when the next release comes along.
55 +# The location of the X11 libraries is something else that is quite variable
56 +# even between different versions of the same operating system (and indeed
57 +# there are different versions of X11 as well, of course). The four settings
58 +# concerned here are X11, XINCLUDE, XLFLAGS (linking flags) and X11_LD_LIB
59 +# (dynamic run-time library). You need not worry about X11 unless you want to
60 +# compile the Exim monitor utility. Exim itself does not use X11.
62 +# Another area of variability between systems is the type and location of the
63 +# DBM library package. Exim has support for ndbm, gdbm, tdb, and Berkeley DB.
64 +# By default the code assumes ndbm; this often works with gdbm or DB, provided
65 +# they are correctly installed, via their compatibility interfaces. However,
66 +# Exim can also be configured to use the native calls for Berkeley DB (obsolete
67 +# versions 1.85 and 2.x, or the current 3.x version) and also for gdbm.
69 +# For some operating systems, a default DBM library (other than ndbm) is
70 +# selected by a setting in the OS-specific Makefile. Most modern OS now have
71 +# a DBM library installed as standard, and in many cases this will be selected
72 +# for you by the OS-specific configuration. If Exim compiles without any
73 +# problems, you probably do not have to worry about the DBM library. If you
74 +# do want or need to change it, you should first read the discussion in the
75 +# file doc/dbm.discuss.txt, which also contains instructions for testing Exim's
76 +# interface to the DBM library.
78 +# In Local/Makefiles blank lines and lines starting with # are ignored. It is
79 +# also permitted to use the # character to add a comment to a setting, for
82 +# EXIM_GID=42 # the "mail" group
84 +# However, with some versions of "make" this works only if there is no white
85 +# space between the end of the setting and the #, so perhaps it is best
86 +# avoided. A consequence of this facility is that it is not possible to have
87 +# the # character present in any setting, but I can't think of any cases where
88 +# this would be wanted.
89 +###############################################################################
93 +###############################################################################
94 +# THESE ARE THINGS YOU MUST SPECIFY #
95 +###############################################################################
97 +# Exim will not build unless you specify BIN_DIRECTORY, CONFIGURE_FILE, and
98 +# EXIM_USER. You also need EXIM_GROUP if EXIM_USER specifies a uid by number.
100 +# If you don't specify SPOOL_DIRECTORY, Exim won't fail to build. However, it
101 +# really is a very good idea to specify it here rather than at run time. This
102 +# is particularly true if you let the logs go to their default location in the
103 +# spool directory, because it means that the location of the logs is known
104 +# before Exim has read the run time configuration file.
106 +#------------------------------------------------------------------------------
107 +# BIN_DIRECTORY defines where the exim binary will be installed by "make
108 +# install". The path is also used internally by Exim when it needs to re-invoke
109 +# itself, either to send an error message, or to recover root privilege. Exim's
110 +# utility binaries and scripts are also installed in this directory. There is
111 +# no "standard" place for the binary directory. Some people like to keep all
112 +# the Exim files under one directory such as /usr/exim; others just let the
113 +# Exim binaries go into an existing directory such as /usr/sbin or
114 +# /usr/local/sbin. The installation script will try to create this directory,
115 +# and any superior directories, if they do not exist.
117 +BIN_DIRECTORY=/usr/bin
120 +#------------------------------------------------------------------------------
121 +# CONFIGURE_FILE defines where Exim's run time configuration file is to be
122 +# found. It is the complete pathname for the file, not just a directory. The
123 +# location of all other run time files and directories can be changed in the
124 +# run time configuration file. There is a lot of variety in the choice of
125 +# location in different OS, and in the preferences of different sysadmins. Some
126 +# common locations are in /etc or /etc/mail or /usr/local/etc or
127 +# /usr/local/etc/mail. Another possibility is to keep all the Exim files under
128 +# a single directory such as /usr/exim. Whatever you choose, the installation
129 +# script will try to make the directory and any superior directories if they
130 +# don't exist. It will also install a default runtime configuration if this
131 +# file does not exist.
133 +CONFIGURE_FILE=/etc/mail/exim.conf
135 +# It is possible to specify a colon-separated list of files for CONFIGURE_FILE.
136 +# In this case, Exim will use the first of them that exists when it is run.
137 +# However, if a list is specified, the installation script no longer tries to
138 +# make superior directories or to install a default runtime configuration.
141 +#------------------------------------------------------------------------------
142 +# The Exim binary must normally be setuid root, so that it starts executing as
143 +# root, but (depending on the options with which it is called) it does not
144 +# always need to retain the root privilege. These settings define the user and
145 +# group that is used for Exim processes when they no longer need to be root. In
146 +# particular, this applies when receiving messages and when doing remote
147 +# deliveries. (Local deliveries run as various non-root users, typically as the
148 +# owner of a local mailbox.) Specifying these values as root is very strongly
149 +# discouraged. These values are compiled into the binary.
154 +# If the setting of EXIM_USER is numeric (e.g. EXIM_USER=42), there must
155 +# also be a setting of EXIM_GROUP. If, on the other hand, you use a name
156 +# for EXIM_USER (e.g. EXIM_USER=exim), you don't need to set EXIM_GROUP unless
157 +# you want to use a group other than the default group for the given user.
161 +# Many sites define a user called "exim", with an appropriate default group,
166 +# while leaving EXIM_GROUP unspecified (commented out).
169 +#------------------------------------------------------------------------------
170 +# SPOOL_DIRECTORY defines the directory where all the data for messages in
171 +# transit is kept. It is strongly recommended that you define it here, though
172 +# it is possible to leave this till the run time configuration.
174 +# Exim creates the spool directory if it does not exist. The owner and group
175 +# will be those defined by EXIM_USER and EXIM_GROUP, and this also applies to
176 +# all the files and directories that are created in the spool directory.
178 +# Almost all installations choose this:
180 +SPOOL_DIRECTORY=/var/spool/exim
184 +###############################################################################
185 +# THESE ARE THINGS YOU PROBABLY WANT TO SPECIFY #
186 +###############################################################################
188 +# You need to specify some routers and transports if you want the Exim that you
189 +# are building to be capable of delivering mail. You almost certainly need at
190 +# least one type of lookup. You should consider whether you want to build
191 +# the Exim monitor or not.
194 +#------------------------------------------------------------------------------
195 +# These settings determine which individual router drivers are included in the
196 +# Exim binary. There are no defaults in the code; those routers that are wanted
197 +# must be defined here by setting the appropriate variables to the value "yes".
198 +# Including a router in the binary does not cause it to be used automatically.
199 +# It has also to be configured in the run time configuration file. By
200 +# commenting out those you know you don't want to use, you can make the binary
201 +# a bit smaller. If you are unsure, leave all of these included for now.
204 +ROUTER_DNSLOOKUP=yes
205 +ROUTER_IPLITERAL=yes
206 +ROUTER_MANUALROUTE=yes
207 +ROUTER_QUERYPROGRAM=yes
210 +# This one is very special-purpose, so is not included by default.
212 +# ROUTER_IPLOOKUP=yes
215 +#------------------------------------------------------------------------------
216 +# These settings determine which individual transport drivers are included in
217 +# the Exim binary. There are no defaults; those transports that are wanted must
218 +# be defined here by setting the appropriate variables to the value "yes".
219 +# Including a transport in the binary does not cause it to be used
220 +# automatically. It has also to be configured in the run time configuration
221 +# file. By commenting out those you know you don't want to use, you can make
222 +# the binary a bit smaller. If you are unsure, leave all of these included for
225 +TRANSPORT_APPENDFILE=yes
226 +TRANSPORT_AUTOREPLY=yes
230 +# This one is special-purpose, and commonly not required, so it is not
231 +# included by default.
236 +#------------------------------------------------------------------------------
237 +# The appendfile transport can write messages to local mailboxes in a number
238 +# of formats. The code for three specialist formats, maildir, mailstore, and
239 +# MBX, is included only when requested. If you do not know what this is about,
240 +# leave these settings commented out.
243 +SUPPORT_MAILSTORE=yes
247 +#------------------------------------------------------------------------------
248 +# These settings determine which file and database lookup methods are included
249 +# in the binary. See the manual chapter entitled "File and database lookups"
250 +# for discussion. DBM and lsearch (linear search) are included by default. If
251 +# you are unsure about the others, leave them commented out for now.
252 +# LOOKUP_DNSDB does *not* refer to general mail routing using the DNS. It is
253 +# for the specialist case of using the DNS as a general database facility (not
265 +# LOOKUP_NISPLUS=yes
270 +# LOOKUP_WILDLSEARCH=yes
273 +#------------------------------------------------------------------------------
274 +# If you have set LOOKUP_LDAP=yes, you should set LDAP_LIB_TYPE to indicate
275 +# which LDAP library you have. Unfortunately, though most of their functions
276 +# are the same, there are minor differences. Currently Exim knows about four
277 +# LDAP libraries: the one from the University of Michigan (also known as
278 +# OpenLDAP 1), OpenLDAP 2, the Netscape SDK library, and the library that comes
279 +# with Solaris 7 onwards. Uncomment whichever of these you are using.
281 +# LDAP_LIB_TYPE=OPENLDAP1
282 +# LDAP_LIB_TYPE=OPENLDAP2
283 +# LDAP_LIB_TYPE=NETSCAPE
284 +# LDAP_LIB_TYPE=SOLARIS
286 +# If you don't set any of these, Exim assumes the original University of
287 +# Michigan (OpenLDAP 1) library.
290 +#------------------------------------------------------------------------------
291 +# Additional libraries and include directories may be required for some
292 +# lookup styles (e.g. LDAP, MYSQL or PGSQL). LOOKUP_LIBS is included only on
293 +# the command for linking Exim itself, not on any auxiliary programs. You
294 +# don't need to set LOOKUP_INCLUDE if the relevant directories are already
295 +# specified in INCLUDE.
297 +# LOOKUP_INCLUDE=-I /usr/local/ldap/include -I /usr/local/mysql/include -I /usr/local/pgsql/include
298 +# LOOKUP_LIBS=-L/usr/local/lib -lldap -llber -lmysqlclient -lpq
301 +#------------------------------------------------------------------------------
302 +# Compiling the Exim monitor: If you want to compile the Exim monitor, a
303 +# program that requires an X11 display, then EXIM_MONITOR should be set to the
304 +# value "eximon.bin". Comment out this setting to disable compilation of the
305 +# monitor. The locations of various X11 directories for libraries and include
306 +# files are defaulted in the OS/Makefile-Default file, but can be overridden in
307 +# local OS-specific make files.
309 +EXIM_MONITOR=eximon.bin
313 +###############################################################################
314 +# THESE ARE THINGS YOU MIGHT WANT TO SPECIFY #
315 +###############################################################################
317 +# The items in this section are those that are commonly changed according to
318 +# the sysadmin's preferences, but whose defaults are often acceptable.
321 +#------------------------------------------------------------------------------
322 +# Exim has support for the AUTH (authentication) extension of the SMTP
323 +# protocol, as defined by RFC 2554. If you don't know what SMTP authentication
324 +# is, you probably won't want to include this code, so you should leave these
325 +# settings commented out. If you do want to make use of SMTP authentication,
326 +# you must uncomment at least one of the following, so that appropriate code is
327 +# included in the Exim binary. You will then need to set up the run time
328 +# configuration to make use of the mechanism(s) selected.
335 +#------------------------------------------------------------------------------
336 +# The passwords for user accounts are normally encrypted with the crypt()
337 +# function. Comparisons with encrypted passwords can be done using Exim's
338 +# "crypteq" expansion operator. (This is commonly used as part of the
339 +# configuration of an authenticator for use with SMTP AUTH.) At least one
340 +# operating system has an extended function called crypt16(), which uses up to
341 +# 16 characters of a password (the normal crypt() uses only the first 8). Exim
342 +# supports the use of crypt16() as well as crypt().
344 +# You can always indicate a crypt16-encrypted password by preceding it with
345 +# "{crypt16}". If you want the default handling (without any preceding
346 +# indicator) to use crypt16(), uncomment the following line:
348 +# DEFAULT_CRYPT=crypt16
350 +# If you do that, you can still access the basic crypt() function by preceding
351 +# an encrypted password with "{crypt}". For more details, see the description
352 +# of the "crypteq" condition in the manual chapter on string expansions.
354 +# Since most operating systems do not include a crypt16() function (yet?), Exim
355 +# has one of its own, which it uses unless HAVE_CRYPT16 is defined. Normally,
356 +# that will be set in an OS-specific Makefile for the OS that have such a
357 +# function, so you should not need to bother with it.
360 +#------------------------------------------------------------------------------
361 +# Exim can be built to support the SMTP STARTTLS command, which implements
362 +# Transport Layer Security using SSL (Secure Sockets Layer). To do this, you
363 +# must install the OpenSSL library package or the GnuTLS library. Exim contains
364 +# no cryptographic code of its own. Uncomment the following lines if you want
365 +# to build Exim with TLS support. If you don't know what this is all about,
366 +# leave these settings commented out.
368 +# This setting is required for any TLS support (either OpenSSL or GnuTLS)
371 +# Uncomment this setting if you are using OpenSSL
372 +TLS_LIBS=-lssl -lcrypto
374 +# Uncomment these settings if you are using GnuTLS
376 +# TLS_LIBS=-lgnutls -ltasn1 -lgcrypt
378 +# If you are running Exim as a server, note that just building it with TLS
379 +# support is not all you need to do. You also need to set up a suitable
380 +# certificate, and tell Exim about it by means of the tls_certificate
381 +# and tls_privatekey run time options. You also need to set tls_advertise_hosts
382 +# to specify the hosts to which Exim advertises TLS support. On the other hand,
383 +# if you are running Exim only as a client, building it with TLS support
384 +# is all you need to do.
386 +# Additional libraries and include files are required for both OpenSSL and
387 +# GnuTLS. The TLS_LIBS settings above assume that the libraries are installed
388 +# with all your other libraries. If they are in a special directory, you may
389 +# need something like
391 +# TLS_LIBS=-L/usr/local/openssl/lib -lssl -lcrypto
393 +# TLS_LIBS=-L/opt/gnu/lib -lgnutls -ltasn1 -lgcrypt
395 +# TLS_LIBS is included only on the command for linking Exim itself, not on any
396 +# auxiliary programs. If the include files are not in a standard place, you can
397 +# set TLS_INCLUDE to specify where they are, for example:
399 +# TLS_INCLUDE=-I/usr/local/openssl/include/
401 +# TLS_INCLUDE=-I/opt/gnu/include
403 +# You don't need to set TLS_INCLUDE if the relevant directories are already
404 +# specified in INCLUDE.
407 +#------------------------------------------------------------------------------
408 +# The default distribution of Exim contains only the plain text form of the
409 +# documentation. Other forms are available separately. If you want to install
410 +# the documentation in "info" format, first fetch the Texinfo documentation
411 +# sources from the ftp directory and unpack them, which should create files
412 +# with the extension "texinfo" in the doc directory. You may find that the
413 +# version number of the texinfo files is different to your Exim version number,
414 +# because the main documentation isn't updated as often as the code. For
415 +# example, if you have Exim version 4.03, the source tarball upacks into a
416 +# directory called exim-4.03, but the texinfo tarball unpacks into exim-4.00.
417 +# In this case, move the contents of exim-4.00/doc into exim-4.03/doc after you
418 +# have unpacked them. Then set INFO_DIRECTORY to the location of your info
419 +# directory. This varies from system to system, but is often /usr/share/info.
420 +# Once you have done this, "make install" will build the info files and
421 +# install them in the directory you have defined.
423 +INFO_DIRECTORY=/usr/share/info
426 +#------------------------------------------------------------------------------
427 +# Exim log directory and files: Exim creates several log files inside a
428 +# single log directory. You can define the directory and the form of the
429 +# log file name here. If you do not set anything, Exim creates a directory
430 +# called "log" inside its spool directory (see SPOOL_DIRECTORY above) and uses
431 +# the filenames "mainlog", "paniclog", and "rejectlog". If you want to change
432 +# this, you can set LOG_FILE_PATH to a path name containing one occurrence of
433 +# %s. This will be replaced by one of the strings "main", "panic", or "reject"
434 +# to form the final file names. Some installations may want something like this:
436 +LOG_FILE_PATH=/var/log/exim/%s.log
438 +# which results in files with names /var/log/exim_mainlog, etc. The directory
439 +# in which the log files are placed must exist; Exim does not try to create
440 +# it for itself. It is also your responsibility to ensure that Exim is capable
441 +# of writing files using this path name. The Exim user (see EXIM_USER above)
442 +# must be able to create and update files in the directory you have specified.
444 +# You can also configure Exim to use syslog, instead of or as well as log
445 +# files, by settings such as these
447 +# LOG_FILE_PATH=syslog
448 +# LOG_FILE_PATH=syslog:/var/log/exim_%slog
450 +# The first of these uses only syslog; the second uses syslog and also writes
451 +# to log files. Do not include white space in such a setting as it messes up
452 +# the building process.
455 +#------------------------------------------------------------------------------
456 +# When logging to syslog, the following option caters for syslog replacements
457 +# that are able to accept log entries longer than the 1024 characters allowed
458 +# by RFC 3164. It is up to you to make sure your syslog daemon can handle this.
459 +# Non-printable characters are usually unacceptable regardless, so log entries
460 +# are still split on newline characters.
462 +# SYSLOG_LONG_LINES=yes
464 +# If you are not interested in the process identifier (pid) of the Exim that is
465 +# making the call to syslog, then comment out the following line.
470 +#------------------------------------------------------------------------------
471 +# Cycling log files: this variable specifies the maximum number of old
472 +# log files that are kept by the exicyclog log-cycling script. You don't have
473 +# to use exicyclog. If your operating system has other ways of cycling log
474 +# files, you can use them instead. The exicyclog script isn't run by default;
475 +# you have to set up a cron job for it if you want it.
480 +#------------------------------------------------------------------------------
481 +# The compress command is used by the exicyclog script to compress old log
482 +# files. Both the name of the command and the suffix that it adds to files
483 +# need to be defined here. See also the EXICYCLOG_MAX configuration.
485 +COMPRESS_COMMAND=/bin/gzip
489 +#------------------------------------------------------------------------------
490 +# If the exigrep utility is fed compressed log files, it tries to uncompress
491 +# them using this command.
493 +ZCAT_COMMAND=/bin/zcat
496 +#------------------------------------------------------------------------------
497 +# Compiling in support for embedded Perl: If you want to be able to
498 +# use Perl code in Exim's string manipulation language and you have Perl
499 +# (version 5.004 or later) installed, set EXIM_PERL to perl.o. Using embedded
500 +# Perl costs quite a lot of resources. Only do this if you really need it.
505 +#------------------------------------------------------------------------------
506 +# Exim has support for PAM (Pluggable Authentication Modules), a facility
507 +# which is available in the latest releases of Solaris and in some GNU/Linux
508 +# distributions (see http://ftp.kernel.org/pub/linux/libs/pam/). The Exim
509 +# support, which is intended for use in conjunction with the SMTP AUTH
510 +# facilities, is included only when requested by the following setting:
514 +# You probably need to add -lpam to EXTRALIBS, and in some releases of
515 +# GNU/Linux -ldl is also needed.
517 +EXTRALIBS=-lpam -ldl
519 +#------------------------------------------------------------------------------
520 +# Support for authentication via Radius is also available. The Exim support,
521 +# which is intended for use in conjunction with the SMTP AUTH facilities,
522 +# is included only when requested by setting the following parameter to the
523 +# location of your Radius configuration file:
525 +# RADIUS_CONFIG_FILE=/etc/radiusclient/radiusclient.conf
528 +#------------------------------------------------------------------------------
529 +# Support for authentication via the Cyrus SASL pwcheck daemon is available.
530 +# The Exim support, which is intented for use in conjunction with the SMTP AUTH
531 +# facilities, is included only when requested by setting the following
532 +# parameter to the location of the pwcheck daemon's socket directory.
534 +# There is no need to install all of SASL on your system. You just need to run
535 +# ./configure --with-pwcheck, cd to the pwcheck directory with sources, make
536 +# and make install. You must create the socket directory (default /var/pwcheck)
537 +# and chown it to exim's user and group. Once you have installed pwcheck, you
538 +# should arrange for it to be started by root at boot time.
540 +CYRUS_PWCHECK_SOCKET=/var/lib/sasl/mux
543 +#------------------------------------------------------------------------------
544 +# Support for authentication via the Cyrus SASL saslauthd daemon is available.
545 +# The Exim support, which is intented for use in conjunction with the SMTP AUTH
546 +# facilities, is included only when requested by setting the following
547 +# parameter to the location of the saslauthd daemon's socket directory.
549 +# There is no need to install all of SASL on your system. You just need to run
550 +# ./configure --with-saslauthd, cd to the saslauthd directory with sources, make
551 +# and make install. You must create the socket directory (default /var/saslauthd)
552 +# and chown it to exim's user and group. Once you have installed saslauthd, you
553 +# should arrange for it to be started by root at boot time.
555 +CYRUS_SASLAUTHD_SOCKET=/var/lib/sasl2/mux
557 +#------------------------------------------------------------------------------
558 +# TCP wrappers: If you want to use tcpwrappers from within Exim, uncomment
559 +# this setting. See the manual section entitled "Use of tcpwrappers" in the
560 +# chapter on building and installing Exim.
562 +# USE_TCP_WRAPPERS=yes
564 +# You may well also have to specify a local "include" file and an additional
565 +# library for TCP wrappers, so you probably need something like this:
567 +# USE_TCP_WRAPPERS=yes
568 +# CFLAGS=-O -I/usr/local/include
569 +# EXTRALIBS_EXIM=-L/usr/local/lib -lwrap
571 +# but of course there may need to be other things in CFLAGS and EXTRALIBS_EXIM
575 +#------------------------------------------------------------------------------
576 +# The default action of the exim_install script (which is run by "make
577 +# install") is to install the Exim binary with a unique name such as
578 +# exim-4.20-1, and then set up a symbolic link called "exim" to reference it,
579 +# moving the symbolic link from any previous version. If you define NO_SYMLINK
580 +# (the value doesn't matter), the symbolic link is not created or moved. You
581 +# will then have to "turn Exim on" by setting up the link manually.
586 +#------------------------------------------------------------------------------
587 +# Another default action of the install script is to install a default runtime
588 +# configuration file if one does not exist. This configuration has a router for
589 +# expanding system aliases. The default assumes that these aliases are kept
590 +# in the traditional file called /etc/aliases. If such a file does not exist,
591 +# the installation script creates one that contains just comments (no actual
592 +# aliases). The following setting can be changed to specify a different
593 +# location for the system alias file.
595 +SYSTEM_ALIASES_FILE=/etc/aliases
599 +###############################################################################
600 +# THINGS YOU ALMOST NEVER NEED TO MENTION #
601 +###############################################################################
603 +# The settings in this section are available for use in special circumstances.
604 +# In the vast majority of installations you need not change anything below.
607 +#------------------------------------------------------------------------------
608 +# The following commands live in different places in some OS. Either the
609 +# ultimate default settings, or the OS-specific files should already point to
610 +# the right place, but they can be overridden here if necessary. These settings
611 +# are used when building various scripts to ensure that the correct paths are
612 +# used when the scripts are run. They are not used in the Makefile itself. Perl
613 +# is not necessary for running Exim unless you set EXIM_PERL (see above) to get
614 +# it embedded, but there are some utilities that are Perl scripts. If you
615 +# haven't got Perl, Exim will still build and run; you just won't be able to
616 +# use those utilities.
618 +# CHOWN_COMMAND=/usr/bin/chown
619 +# CHGRP_COMMAND=/usr/bin/chgrp
620 +# MV_COMMAND=/bin/mv
621 +# RM_COMMAND=/bin/rm
622 +# PERL_COMMAND=/usr/bin/perl
625 +#------------------------------------------------------------------------------
626 +# The following macro can be used to change the command for building a library
627 +# of functions. By default the "ar" command is used, with options "cq".
628 +# Only in rare circumstances should you need to change this.
633 +#------------------------------------------------------------------------------
634 +# The following macros can be used to change the default modes that are used
635 +# by the appendfile transport. In most installations the defaults are just
636 +# fine, and in any case, you can change particular instances of the transport
637 +# at run time if you want.
639 +# APPENDFILE_MODE=0600
640 +# APPENDFILE_DIRECTORY_MODE=0700
641 +# APPENDFILE_LOCKFILE_MODE=0600
644 +#------------------------------------------------------------------------------
645 +# In some installations there may be multiple machines sharing file systems,
646 +# where a different configuration file is required for Exim on the different
647 +# machines. If CONFIGURE_FILE_USE_NODE is defined, then Exim will first look
648 +# for a configuration file whose name is that defined by CONFIGURE_FILE,
649 +# with the node name obtained by uname() tacked on the end, separated by a
650 +# period (for example, /usr/exim/configure.host.in.some.domain). If this file
651 +# does not exist, then the bare configuration file name is tried.
653 +CONFIGURE_FILE_USE_NODE=yes
656 +#------------------------------------------------------------------------------
657 +# In some esoteric configurations two different versions of Exim are run,
658 +# with different setuid values, and different configuration files are required
659 +# to handle the different cases. If CONFIGURE_FILE_USE_EUID is defined, then
660 +# Exim will first look for a configuration file whose name is that defined
661 +# by CONFIGURE_FILE, with the effective uid tacked on the end, separated by
662 +# a period (for eximple, /usr/exim/configure.0). If this file does not exist,
663 +# then the bare configuration file name is tried. In the case when both
664 +# CONFIGURE_FILE_USE_EUID and CONFIGURE_FILE_USE_NODE are set, four files
665 +# are tried: <name>.<euid>.<node>, <name>.<node>, <name>.<euid>, and <name>.
667 +# CONFIGURE_FILE_USE_EUID=yes
670 +#------------------------------------------------------------------------------
671 +# The size of the delivery buffers: These specify the sizes (in bytes) of
672 +# the buffers that are used when copying a message from the spool to a
673 +# destination. There is rarely any need to change these values.
675 +# DELIVER_IN_BUFFER_SIZE=8192
676 +# DELIVER_OUT_BUFFER_SIZE=8192
679 +#------------------------------------------------------------------------------
680 +# The mode of the database directory: Exim creates a directory called "db"
681 +# in its spool directory, to hold its databases of hints. This variable
682 +# determines the mode of the created directory. The default value in the
685 +# EXIMDB_DIRECTORY_MODE=0750
688 +#------------------------------------------------------------------------------
689 +# Database file mode: The mode of files created in the "db" directory defaults
690 +# to 0640 in the source, and can be changed here.
695 +#------------------------------------------------------------------------------
696 +# Database lock file mode: The mode of zero-length files created in the "db"
697 +# directory to use for locking purposes defaults to 0640 in the source, and
698 +# can be changed here.
700 +# EXIMDB_LOCKFILE_MODE=0640
703 +#------------------------------------------------------------------------------
704 +# This parameter sets the maximum length of the header portion of a message
705 +# that Exim is prepared to process. The default setting is one megabyte. The
706 +# limit exists in order to catch rogue mailers that might connect to your SMTP
707 +# port, start off a header line, and then just pump junk at it for ever. The
708 +# message_size_limit option would also catch this, but it may not be set.
709 +# The value set here is the default; it can be changed at runtime.
711 +# HEADER_MAXSIZE="(1024*1024)"
714 +#------------------------------------------------------------------------------
715 +# The mode of the input directory: The input directory is where messages are
716 +# kept while awaiting delivery. Exim creates it if necessary, using a mode
717 +# which can be defined here (default 0750).
719 +# INPUT_DIRECTORY_MODE=0750
722 +#------------------------------------------------------------------------------
723 +# The mode of Exim's log directory, when it is created by Exim inside the spool
724 +# directory, defaults to 0750 but can be changed here.
726 +# LOG_DIRECTORY_MODE=0750
729 +#------------------------------------------------------------------------------
730 +# The log files themselves are created as required, with a mode that defaults
731 +# to 0640, but which can be changed here.
736 +#------------------------------------------------------------------------------
737 +# The TESTDB lookup is for performing tests on the handling of lookup results,
738 +# and is not useful for general running. It should be included only when
739 +# debugging the code of Exim.
744 +#------------------------------------------------------------------------------
745 +# /bin/sh is used by default as the shell in which to run commands that are
746 +# defined in the makefiles. This can be changed if necessary, by uncommenting
747 +# this line and specifying another shell, but note that a Bourne-compatible
748 +# shell is expected.
750 +# MAKE_SHELL=/bin/sh
753 +#------------------------------------------------------------------------------
754 +# The maximum number of named lists of each type (address, domain, host, and
755 +# local part) can be increased by changing this value. It should be set to
761 +#------------------------------------------------------------------------------
762 +# Network interfaces: Unless you set the local_interfaces option in the runtime
763 +# configuration file to restrict Exim to certain interfaces only, it will run
764 +# code to find all the interfaces there are on your host. Unfortunately,
765 +# the call to the OS that does this requires a buffer large enough to hold
766 +# data for all the interfaces - it was designed in the days when a host rarely
767 +# had more than three or four interfaces. Nowadays hosts can have very many
768 +# virtual interfaces running on the same hardware. If you have more than 250
769 +# virtual interfaces, you will need to uncomment this setting and increase the
775 +#------------------------------------------------------------------------------
776 +# Per-message logs: While a message is in the process of being delivered,
777 +# comments on its progress are written to a message log, for the benefit of
778 +# human administrators. These logs are held in a directory called "msglog"
779 +# in the spool directory. Its mode defaults to 0750, but can be changed here.
780 +# The message log directory is also used for storing files that are used by
781 +# transports for returning data to a message's sender (see the "return_output"
782 +# option for transports).
784 +# MSGLOG_DIRECTORY_MODE=0750
787 +#------------------------------------------------------------------------------
788 +# There are three options which are used when compiling the Perl interface and
789 +# when linking with Perl. The default values for these are placed automatically
790 +# at the head of the Makefile by the script which builds it. However, if you
791 +# want to override them, you can do so here.
798 +#------------------------------------------------------------------------------
799 +# Identifying the daemon: When an Exim daemon starts up, it writes its pid
800 +# (process id) to a file so that it can easily be identified. The path of the
801 +# file can be specified here. Some installations may want something like this:
803 +PID_FILE_PATH=/var/run/exim%s.pid
805 +# If PID_FILE_PATH is not defined, Exim writes a file in its spool directory
806 +# using the name "exim-daemon.pid".
808 +# If you start up a daemon without the -bd option (for example, with just
809 +# the -q15m option), a pid file is not written. Also, if you override the
810 +# configuration file with the -oX option, no pid file is written. In other
811 +# words, the pid file is written only for a "standard" daemon.
814 +#------------------------------------------------------------------------------
815 +# If Exim creates the spool directory, it is given this mode, defaulting in the
818 +# SPOOL_DIRECTORY_MODE=0750
821 +#------------------------------------------------------------------------------
822 +# The mode of files on the input spool which hold the contents of messages can
823 +# be changed here. The default is 0640 so that information from the spool is
824 +# available to anyone who is a member of the Exim group.
829 +#------------------------------------------------------------------------------
830 +# Moving frozen messages: If the following is uncommented, Exim is compiled
831 +# with support for automatically moving frozen messages out of the main spool
832 +# directory, a facility that is found useful by some large installations. A
833 +# run time option is required to cause the moving actually to occur. Such
834 +# messages become "invisible" to the normal management tools.
836 +# SUPPORT_MOVE_FROZEN_MESSAGES=yes
838 +# End of EDITME for Exim 4.