summaryrefslogtreecommitdiff
path: root/mail/exim-old/files/Makefile
diff options
context:
space:
mode:
Diffstat (limited to 'mail/exim-old/files/Makefile')
-rw-r--r--mail/exim-old/files/Makefile422
1 files changed, 0 insertions, 422 deletions
diff --git a/mail/exim-old/files/Makefile b/mail/exim-old/files/Makefile
deleted file mode 100644
index 07e6066e2acf..000000000000
--- a/mail/exim-old/files/Makefile
+++ /dev/null
@@ -1,422 +0,0 @@
-##################################################
-# The Exim mail transport agent #
-##################################################
-
-# This is the template for Exim's main build-time configuration file. It
-# contains settings that are independent of any operating system. It should
-# be edited and then saved to a file called Local/Makefile before first running
-# the make command.
-
-# Blank lines and lines starting with # are ignored. It is also permitted to
-# use the # character to add a comment to a setting, for example
-#
-# EXIM_GID=42 # the "mail" group
-#
-# Consequently, it is not possible to have the # character present in any
-# setting, but I can't think of any cases where this would be wanted.
-
-# Things that depend on the operating system have default settings in files
-# called OS/Makefile-<osname>. These can be overridden by creating files
-# called Local/Makefile-<osname>. In particular, the location of the X11
-# libraries is something that is quite variable between different versions
-# of the same operation system (and indeed there are different versions of
-# X11 as well, of course). The four settings concerned here are X11, XINCLUDE,
-# XLFLAGS (linking flags) and X11_LD_LIB (dynamic run-time library).
-
-# There are defaults in OS/Makefile-Default which are overridden for some
-# operating systems in the OS/Makefile-<osname> file. If these are not right
-# for you, put appropriate settings into a file called Local/Makefile-<osname>.
-# In all cases "<osname>" stands for the name of your operating system - look
-# at the names in the OS directory to see which names are recognized.
-
-# Another area of variability between systems is the type and location of the
-# dbm library package. Exim has support for ndbm, gdbm, and Berkeley db. By
-# default it assumes ndbm; this often works with gdbm or db, provided they
-# are correctly installed, via their compatibility interfaces. However, Exim
-# can also be configured to use the native calls for Berkeley db 1.85, and
-# this is defaulted for some operating systems. There are some locking actions
-# that can be varied by changing the configuration. The defaults are set in
-# OS/Makefile-Default, and can be changed by putting things into an OS-specific
-# Makefile, or indeed into the main Local/Makefile if Exim is being compiled
-# for a single OS only.
-
-# See also the file doc/dbm.discuss.txt for discussion about different dbm
-# libraries.
-###############################################################################
-
-
-# /bin/sh is normally used as the shell in which to run commands that are
-# defined in the makefiles. This can be changed if necessary, but note that
-# a Bourne-compatible shell is expected.
-
-# MAKE_SHELL=/bin/sh
-
-
-# The following commands live in different places in some OS. The OS-specific
-# files should normally point to the right place, but they can be overridden
-# here if necessary. Perl is not necessary for running Exim, but there are
-# some Perl utilities for processing log files. If you haven't got Perl,
-# Exim will still build and run; you just won't be able to run those utilities.
-
-# CHOWN_COMMAND=/usr/bin/chown
-# CHGRP_COMMAND=/usr/bin/chgrp
-# MV_COMMAND=/bin/mv
-# RM_COMMAND=/bin/rm
-# PERL_COMMAND=/usr/bin/perl
-
-
-# The following macro can be used to change the command for building a library
-# of functions. By default the "ar" command is used, with options "cq".
-
-# AR=ar cq
-
-
-# The binary directory: This variable defines where the exim binary will be
-# installed by "make install" or "exim_install". It is also used internally
-# by exim when it needs to re-invoke itself, either to send an error message,
-# or to recover root privilege. Exim's utility binaries and scripts are also
-# installed in this directory. There is no default for this variable built into
-# the source files; it must be set in one of the local configuration files.
-
-BIN_DIRECTORY=XX_PREFIX_XX/sbin
-
-
-# The info directory: This variable defines where the exim info file will be
-# installed by "make install" or "exim_intall".
-
-INFO_DIRECTORY=XX_PREFIX_XX/info
-
-
-# The compress command is used by the exicyclog script to compress old log
-# files. Both the name of the command and the suffix that it adds to files
-# need to be defined here. See also the EXICYCLOG_MAX configuration.
-
-COMPRESS_COMMAND=/usr/bin/gzip
-COMPRESS_SUFFIX=gz
-
-
-# The runtime configuration file: This variable defines where Exim's runtime
-# configuration file is. There is no default built into the source files, so
-# there must be a setting in one of the local configuration files. The
-# location of all other runtime files and directories can be changed in the
-# runtime configuration file.
-
-CONFIGURE_FILE=XX_PREFIX_XX/etc/exim/configure
-
-
-# In some installations there may be multiple machines sharing file systems,
-# where a different configuration file is required for Exim on the different
-# machines. If CONFIGURE_FILE_USE_NODE is defined, then Exim will first look
-# for a configuration file whose name is that defined by CONFIGURE_FILE,
-# with the node name obtained by uname() tacked on the end, separated by a
-# period (for example, /usr/exim/configure.host.in.some.domain. If this file
-# does not exist, then the bare configuration file name is tried.
-
-# CONFIGURE_FILE_USE_NODE=yes
-
-
-# In some esoteric configurations two different versions of Exim are run,
-# with different setuid values, and different configuration files are required
-# to handle the different cases. If CONFIGURE_FILE_USE_EUID is defined, then
-# Exim will first look for a configuration file whose name is that defined
-# by CONFIGURE_FILE, with the effective uid tacked on the end, separated by
-# a period (for eximple, /usr/exim/configure.0). If this file does not exist,
-# then the bare configuration file name is tried. In the case when both
-# CONFIGURE_FILE_USE_EUID and CONFIGURE_FILE_USE_NODE are set, four files
-# are tried: <name>.<euid>.<node>, <name>.<node>, <name>.<euid>, and <name>.
-
-# CONFIGURE_FILE_USE_EUID=yes
-
-
-# The size of the delivery buffer: This specifies the size of buffer which is
-# used when copying a message from the spool to a destination. The default
-# value built into the source is 8192.
-
-# DELIVER_BUFFER_SIZE=8192
-
-
-# Included directors: These variables determine which individual director
-# drivers are included in the Exim binary. There are no defaults; those that
-# are wanted must be defined here by setting the appropriate variables to the
-# value "yes". The actions of each director are described in a separate chapter
-# in the manual. Including a director in the binary does not cause it to
-# be used automatically. It has also to be specified in the runtime
-# configuration file.
-
-DIRECTOR_ALIASFILE=yes
-DIRECTOR_FORWARDFILE=yes
-DIRECTOR_LOCALUSER=yes
-DIRECTOR_SMARTUSER=yes
-
-
-# The mode of the database directory: Exim creates a directory called "db"
-# in its spool directory, to hold its databases of hints. This variable
-# determines the mode of the created directory. The default value in the
-# source is 0750.
-
-# DB_DIRECTORY_MODE=0750
-
-
-# Database file mode: The mode of files created in the "db" directory defaults
-# to 0640 in the source, and can be changed here.
-
-# DB_MODE=0640
-
-
-# Database lock file mode: The mode of zero-length files created in the "db"
-# directory to use for locking purposes defaults to 0640 in the source, and
-# can be changed here.
-
-# DB_LOCKFILE_MODE=0640
-
-
-# Cycling log files: this variable specifies the maximum number of old
-# log files that are kept by the exicyclog log-cycling script.
-
-EXICYCLOG_MAX=10
-
-
-# Running Exim not as root: A uid and gid for Exim can be specified here. These
-# are compiled into the binary, but can be changed by settings in the runtime
-# configuration file. If EXIM_UID is not defined, the default in the code is to
-# run as root unless specified otherwise at run time. Specifying 0 at
-# run time has the effect of unsetting the values build into the binary.
-
-# The settings here must be numeric; the run time file allows names to
-# be used. When this uid and gid are set, the Exim binary still has to be
-# setuid root if local deliveries are to be performed or a listener on port
-# 25 is to be run, but it gives up its privilege when possible. There is a
-# trade-off between security and efficiency, controlled by the runtime
-# "security" setting, which controls how privilege is released (setuid vs
-# seteuid).
-
-# EXIM_UID=
-# EXIM_GID=
-
-
-# Compiling the Exim monitor: If you want to compile the Exim monitor,
-# a program that requires an X11 display, then EXIM_MONITOR should be
-# set to the value "eximon.bin". Comment out this setting to disable
-# compilation of the binary file that is run by the eximon script. The
-# locations of various X11 directories for libraries and include files
-# are defaulted in the OS/Makefile-Default file, and can be overridden
-# in local OS-specific make files.
-
-EXIM_MONITOR=eximon.bin
-
-
-# The maximum length of header line that Exim is prepared to process. There
-# is a limit in order to catch rogue mailers out there that might connect to
-# the SMTP port, start off a header line, and then just pump junk for ever
-# at it. The default is 8192.
-
-# HEADER_MAXLENGTH=8192
-
-
-# The mode of the input directory: The input directory is where messages are
-# kept while awaiting delivery. Exim creates it if necessary, using a mode
-# which can be defined here (default 0750).
-
-# INPUT_DIRECTORY_MODE=0750
-
-
-# Exim log directory and files: Exim creates several log files inside a
-# single log directory. You can define the directory and the form of the
-# log file name here, by setting LOG_FILE_PATH to a path name containing one
-# occurrence of %s. This will be replaced by one of the strings "main",
-# "panic", "process" or "reject" to form the final file name. For example,
-# some installations may want something like this:
-
-LOG_FILE_PATH=/var/log/exim_%slog
-
-# which results in files with names /var/log/exim_mainlog, etc. The directory
-# in which the log files are placed must exist; Exim does not try to create
-# it for itself. It is also your responsibility to ensure that Exim is capable
-# of writing files using this path name. If you have defined EXIM_UID and
-# EXIM_GID above, then that uid and gid must be able to create files in the
-# directory you have specified.
-
-# You do not have to define the log file path here; an option in the runtime
-# configuration file can also set it, and that overrides any setting here.
-# However, it is recommended that you set it here if it is a fixed path, so
-# that it is available right from the start of Exim's execution. Otherwise,
-# errors detected early on, for example errors in the configuration file,
-# cannot be logged.
-
-# If you do not set LOG_FILE_PATH here or in the runtime configuration, Exim
-# creates a directory called "log" inside its spool directory (see
-# SPOOL_DIRECTORY below) and uses that with filenames "mainlog", "paniclog",
-# etc. Its mode defaults to 0750 but that can be changed here.
-
-# LOG_DIRECTORY_MODE=0750
-
-# This value is used only when Exim creates the directory for itself.
-
-# The log files themselves are created as required, with a mode that defaults
-# to 0640, but which can be changed here.
-
-# LOG_MODE=0640
-
-
-# Included file and database lookup methods. See the manual chapter entitled
-# "File and database lookups" for discussion. DBM and lsearch (linear search)
-# are included by default. LOOKUP_DNSDB does *not* refer to general mail
-# routing using the DNS. It is for the specialist case of using the DNS as
-# a general database facility (not common). For details of cdb files and the
-# tools to build them, see http://www.pobox.com/~djb/cdb.html.
-
-LOOKUP_DBM=yes
-LOOKUP_LSEARCH=yes
-
-# LOOKUP_CDB=yes
-# LOOKUP_DNSDB=yes
-# LOOKUP_LDAP=yes
-# LOOKUP_NIS=yes
-# LOOKUP_NISPLUS=yes
-
-# The TESTDB lookup is for performing tests on the handling of lookup
-# results, and is not useful for general running. It should be included
-# only when debugging the code of Exim.
-
-# LOOKUP_TESTDB=yes
-
-
-# Per-message logs: While a message is in the process of being delivered,
-# comments on its progress are written to a message log, for the benefit of
-# human administrators. These logs are held in a directory called "msglog"
-# in the spool directory. Its mode defaults to 0750, but can be changed here.
-# The message log directory is also used for storing files that are used by
-# transports for returning data to a message's sender (see the "return_output"
-# option for transports).
-
-# MSGLOG_DIRECTORY_MODE=0750
-
-
-# Identifying the daemon: When an Exim daemon starts up, it writes its pid to
-# a file so that it can easily be identified. The path of the file can be
-# specified here. It must contain precisely one occurrence of "%s". When
-# a daemon is run on the default SMTP port, this is replaced with the null
-# string, but when it is run with some explicit port specified, "%s" is
-# replaced with the port number preceded by a dot. If a daemon is run with
-# only one of -bd and -q<time>, then that option is added on to the end of
-# the file name, allowing sites that run two separate daemons to distinguish
-# them. Some installations may want something like this
-
-# PID_FILE_PATH=/var/lock/exim%s.pid
-
-# If PID_FILE_PATH is not defined, Exim writes a file in its spool directory
-# (see SPOOL_DIRECTORY below) with the name "exim-daemon.pid" for the standard
-# daemon, or "exim-daemon.<port>.pid" for a daemon listening on a non-standard
-# port. If you run a daemon that does not have both the -bd and -q options,
-# then whichever of the two options it does have is added to the file name,
-# whether obtained from PID_FILE_PATH or by default.
-
-# If you set PID_FILE_PATH, then it is your responsibility to ensure that
-# Exim is capable of writing to the relevant files. If you have defined
-# EXIM_UID and EXIM_GID above, then that uid/gid combination must be able to
-# create and write to the files. If the attempt to open the file fails, Exim
-# just refrains from trying to write the data.
-
-# The pid file path does not have to be set here; it can be also be set by an
-# option in the runtime configuration file, which takes precedence over any
-# setting here.
-
-
-# Included routers: These variables determine which individual router drivers
-# are included in the Exim binary. There are no defaults; those that are
-# wanted must be defined here by setting the appropriate variables to the value
-# "yes". The actions of each router are described in a separate chapter
-# in the manual. Including a router in the binary does not cause it to
-# be used automatically. It has also to be specified in the runtime
-# configuration file. Those routers that are *not* wanted must not be defined
-# here at all - comment them out.
-
-ROUTER_DOMAINLIST=yes
-ROUTER_IPLITERAL=yes
-ROUTER_LOOKUPHOST=yes
-ROUTER_QUERYPROGRAM=yes
-
-# This one is very special-purpose, so is not included by default.
-
-# ROUTER_IPLOOKUP=yes
-
-
-# The spool directory: This directory is where all the data for messages in
-# transit is kept. There is no default in the source, so its location must be
-# defined in a local configuration file, or in the runtime configuration. It
-# is recommended that you define it here if it is a fixed path, especially if
-# you have not defined LOG_FILE_PATH. Log files are then written in a sub-
-# directory of the spool directory, and it is helpful to have this defined
-# right from the start of execution so that, for example, errors in reading
-# the runtime configuration file can be logged.
-
-# Exim creates the spool directory if it does not exist, using the mode
-# required for the sub-directory that it is trying to create at the time. If a
-# non-root uid and gid have been defined for Exim (either in this configuration
-# file, or by the runtime configuration options), then this directory and all
-# sub-directories and their files will be created with their owners and groups
-# set to Exim's uid and gid.
-
-# Many installations will want something like this:
-SPOOL_DIRECTORY=/var/spool/exim
-
-# Others may prefer to keep all Exim things under one directory:
-# SPOOL_DIRECTORY=/usr/exim/spool
-
-
-# If Exim creates the spool directory, it is given this mode, defaulting in the
-# source to 0750.
-
-# SPOOL_DIRECTORY_MODE=0750
-
-
-# The mode of files on the input spool which hold the contents of message can
-# be changed here. The default is 0600. If you have defined a uid and gid for
-# Exim and want information from the spool to be available to anyone who is a
-# member of the Exim group, change the value to 0640. This is particularly
-# relevant if you are going to run the Exim monitor.
-
-# SPOOL_MODE=0600
-
-
-# If STDERR_FILE is defined then the -df command line option causes Exim to
-# redirect stderr to the named file. This is useful for catching debugging
-# output when starting Exim via inetd.
-
-# STDERR_FILE=
-
-
-# The appendfile transport can write messages as individual files in a number
-# of formats. The code for two specialist formats, maildir and mailstore,
-# is included only when requested by the following settings:
-
-# SUPPORT_MAILDIR=yes
-# SUPPORT_MAILSTORE=yes
-
-
-# Included transports: These variables determine which individual transport
-# drivers are included in the Exim binary. There are no defaults; those that
-# are wanted must be defined here by setting the appropriate variables to the
-# value "yes". The actions of each transport are described in a separate chapter
-# in the manual. Including a transport in the binary does not cause it to
-# be used automatically. It has also to be specified in the runtime
-# configuration file.
-
-TRANSPORT_APPENDFILE=yes
-TRANSPORT_AUTOREPLY=yes
-TRANSPORT_PIPE=yes
-TRANSPORT_SMTP=yes
-
-# The Debug transport is special, and should be included only when low-level
-# debugging is being performed. In conjunction with the "debug_transport"
-# configuration option, it permits the subversion of all mail deliveries to
-# a given file.
-
-# TRANSPORT_DEBUG=
-
-
-# TCP wrappers:
-
-# USE_TCP_WRAPPERS=yes
-
-# End of EDITME