X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 270C41DED178 for ; Fri, 28 Oct 2011 08:52:54 +0000 (UTC) Received: by qyk35 with SMTP id 35so2130450qyk.13 for ; Fri, 28 Oct 2011 01:52:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/fKnzNpncoe5SDU1aSR2EU6zxgRk3BxsK4ziLvo8kDw=; b=QeXY9wUl93Ton38+BNG/EOyUvp+euNPjIWr3qnimz1gkIEFfVW5GQ3zqm4H4t+Y6z/ ZZjEeW2WtWIRrT8PoQ4t8y2tfJkgcvuRFylxpwWAfiw2c6/zOnY17zN6j+nMJ2e2fw2G Wwk/pf7EQAhKYS9XuNehiCkn9gIECrZSOHbW0= X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.182.51.66 with SMTP id i2mr376028obo.5.1319791972726; Fri, 28 Oct 2011 01:52:52 -0700 (PDT) Received: by 10.182.144.9 with HTTP; Fri, 28 Oct 2011 01:52:52 -0700 (PDT) In-Reply-To: <1319751176-9658-3-git-send-email-jlyo@jlyo.org> References: <1319751176-9658-1-git-send-email-jlyo@jlyo.org> <1319751176-9658-3-git-send-email-jlyo@jlyo.org> Date: Fri, 28 Oct 2011 10:52:52 +0200 Message-ID: Subject: Re: [alpine-devel] [PATCH 3/4] testing/exim: new aport From: Carlo Landmeter To: Jesse Young Cc: Alpine Development Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Oct 27, 2011 at 11:32 PM, Jesse Young wrote: > A Message Transfer Agent > http://www.exim.org/ > > Signed-off-by: Jesse Young > --- > =A0testing/exim/APKBUILD =A0 =A0 =A0 | =A0 81 +++ > =A0testing/exim/aliases =A0 =A0 =A0 =A0| =A0 35 ++ > =A0testing/exim/exim.Makefile =A0| 1227 +++++++++++++++++++++++++++++++++= ++++++++++ > =A0testing/exim/exim.confd =A0 =A0 | =A0 =A02 + > =A0testing/exim/exim.initd =A0 =A0 | =A0 30 + > =A0testing/exim/exim.logrotate | =A0 13 + > =A06 files changed, 1388 insertions(+), 0 deletions(-) > =A0create mode 100644 testing/exim/APKBUILD > =A0create mode 100644 testing/exim/aliases > =A0create mode 100644 testing/exim/exim.Makefile > =A0create mode 100644 testing/exim/exim.confd > =A0create mode 100644 testing/exim/exim.initd > =A0create mode 100644 testing/exim/exim.logrotate > > diff --git a/testing/exim/APKBUILD b/testing/exim/APKBUILD > new file mode 100644 > index 0000000..908d034 > --- /dev/null > +++ b/testing/exim/APKBUILD > @@ -0,0 +1,81 @@ > +# Contributor: Jesse Young > +# Maintainer: Jesse Young > +pkgname=3Dexim > +pkgver=3D4.77 > +pkgrel=3D0 > +pkgdesc=3D"A Message Transfer Agent" > +url=3D"http://www.exim.org/" > +arch=3D"all" > +license=3D"GPL" > +depends=3D"openssl" > +depends_dev=3D"db-dev pcre-dev openssl-dev" > +makedepends=3D"$depends_dev" > +install=3D > +subpackages=3D"$pkgname-doc" > +source=3D"ftp://mirrors.24-7-solutions.net/pub/exim/ftp/exim/exim4/exim-= $pkgver.tar.bz2 > + =A0 =A0 =A0 exim.Makefile > + =A0 =A0 =A0 exim.confd > + =A0 =A0 =A0 exim.initd > + =A0 =A0 =A0 exim.logrotate > + =A0 =A0 =A0 aliases" > + > +_builddir=3D"$srcdir"/$pkgname-$pkgver > + > +prepare() { > + =A0 =A0 =A0 cd "$_builddir" > + =A0 =A0 =A0 # apply patches here > + =A0 =A0 =A0 cp "$srcdir/$pkgname.Makefile" Local/Makefile > + =A0 =A0 =A0 sed -e 's/^LIBS =3D -lnsl/LIBS =3D/g' \ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 -e 's/^HAVE_ICONV=3Dyes/#HAVE_ICONV=3Dyes/'= \ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 -i OS/Makefile-Linux > +} > + > +build() { > + =A0 =A0 =A0 cd "$_builddir" > + =A0 =A0 =A0 make makefile > + =A0 =A0 =A0 make || { > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 cd build-Linux-* > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 sh ../scripts/Configure-config.h "make" > + =A0 =A0 =A0 } && make || return 1 > +} > + > +package() { > + =A0 =A0 =A0 cd "$_builddir" > + > + =A0 =A0 =A0 install -D -m644 ../${pkgname}.logrotate ${pkgdir}/etc/logr= otate.d/${pkgname} > + =A0 =A0 =A0 install -D -m644 doc/exim.8 ${pkgdir}/usr/share/man/man8/ex= im.8 > + =A0 =A0 =A0 mkdir -p ${pkgdir}/var/spool/exim/db ${pkgdir}/etc/mail \ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 ${pkgdir}/var/log/exim ${pkgdir}/usr/lib \ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 ${pkgdir}/var/log/exim ${pkgdir}/usr/sbin > + =A0 =A0 =A0 chmod 770 ${pkgdir}/var/spool/exim ${pkgdir}/var/spool/exim= /db ${pkgdir}/var/log/exim > + =A0 =A0 =A0 cd build-Linux-* > + =A0 =A0 =A0 for i in exicyclog exim_checkaccess exim_dumpdb exim_lock\ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 exim_tidydb exipick exiqsumm exigrep exim_d= bmbuild exim\ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 exim_fixdb eximstats exinext exiqgrep exiwh= at; do > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 install -m 0755 "$i" "$pkgdir/usr/sbin" > + =A0 =A0 =A0 done > + > + =A0 =A0 =A0 cd "$srcdir/exim-$pkgver/src" > + =A0 =A0 =A0 sed -e "s|/etc/aliases|/etc/mail/aliases|g" \ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 -e "s|SYSTEM_ALIASES_FILE|/etc/mail/aliases= |g" configure.default \ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 >"$pkgdir/etc/mail/exim.conf" > + > + =A0 =A0 =A0 cp "$srcdir/aliases" "$pkgdir/etc/mail" > + =A0 =A0 =A0 cd "$pkgdir/usr/sbin" > + =A0 =A0 =A0 for i in mailq rmail rsmtp runq sendmail; do > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 ln -s exim "$i" > + =A0 =A0 =A0 done > + =A0 =A0 =A0 # fhs compliancy > + =A0 =A0 =A0 ln -s ../sbin/exim ../lib/sendmail > + > + =A0 =A0 =A0 # remove the 2 lines below (and this) if there is no init.d= script > + =A0 =A0 =A0 install -m755 -D "$srcdir"/$pkgname.initd "$pkgdir"/etc/ini= t.d/$pkgname > + =A0 =A0 =A0 install -m644 -D "$srcdir"/$pkgname.confd "$pkgdir"/etc/con= f.d/$pkgname > +} > + > +md5sums=3D"5d746275f2cc85845567f9d5eb84a57a =A0exim-4.77.tar.bz2 > +7dfc9ed9307db655c8aec33b9618608d =A0exim.Makefile > +f442b68d435598831bab8536ade071b8 =A0exim.confd > +2f6d768039d74caf433345cace4bc540 =A0exim.initd > +2f40248d23ad1a9d0c25ab6474ff6900 =A0exim.logrotate > +4874006f0585253ddab027d441009757 =A0aliases" > diff --git a/testing/exim/aliases b/testing/exim/aliases > new file mode 100644 > index 0000000..3f76693 > --- /dev/null > +++ b/testing/exim/aliases > @@ -0,0 +1,35 @@ > +# > +# =A0/etc/mail/aliases > +# > +# =A0NOTE: =A0Make sure you run 'newaliases' after modifying this file > +# > + > +# Basic system aliases -- these MUST be present. > +MAILER-DAEMON: postmaster > +postmaster: =A0 =A0root > +hostmaster: =A0 =A0root > +webmaster: =A0 =A0 hostmaster > +ftpmaster: =A0 =A0 hostmaster > +admin: =A0 =A0 =A0 =A0 hostmaster > +administrator: hostmaster > + > +# General redirections for pseudo accounts. > +bin: =A0 =A0 =A0 =A0 =A0 root > +daemon: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0root > +games: =A0 =A0 =A0 =A0 root > +ingres: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0root > +nobody: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0root > +system: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0root > +toor: =A0 =A0 =A0 =A0 =A0root > +uucp: =A0 =A0 =A0 =A0 =A0root > + > +# Well-known aliases. > +manager: =A0 =A0 =A0 root > +dumper: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0root > +operator: =A0 =A0 =A0root > + > +# trap decode to catch security attacks > +decode: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0root > + > +# Person who should get root's mail > +#root: > diff --git a/testing/exim/exim.Makefile b/testing/exim/exim.Makefile > new file mode 100644 > index 0000000..a7ec877 > --- /dev/null > +++ b/testing/exim/exim.Makefile > @@ -0,0 +1,1227 @@ > +# $Cambridge: exim/src/src/EDITME,v 1.27 2010/06/12 15:21:25 jetmore Exp= $ > + > +################################################## > +# =A0 =A0 =A0 =A0 =A0The Exim mail transport agent =A0 =A0 =A0 =A0 # > +################################################## > + > +# This is the template for Exim's main build-time configuration file. It > +# contains settings that are independent of any operating system. These = are > +# things that are mostly sysadmin choices. The items below are divided i= nto > +# those you must specify, those you probably want to specify, those you = might > +# often want to specify, and those that you almost never need to mention= . > + > +# Edit this file and save the result to a file called Local/Makefile wit= hin the > +# Exim distribution directory before running the "make" command. > + > +# Things that depend on the operating system have default settings in > +# OS/Makefile-Default, but these are overridden for some OS by files cal= led > +# called OS/Makefile-. You can further override these by creatin= g files > +# called Local/Makefile-, where "" stands for the name o= f your > +# operating system - look at the names in the OS directory to see which = names > +# are recognized. > + > +# However, if you are building Exim for a single OS only, you don't need= to > +# worry about setting up Local/Makefile-. Any build-time configu= ration > +# settings you require can in fact be placed in the one file called > +# Local/Makefile. It is only if you are building for several OS from the= same > +# source files that you need to worry about splitting off your own OS-de= pendent > +# settings into separate files. (There's more explanation about how this= all > +# works in the toplevel README file, under "Modifying the building proce= ss", as > +# well as in the Exim specification.) > + > +# One OS-specific thing that may need to be changed is the command for r= unning > +# the C compiler; the overall default is gcc, but some OS Makefiles spec= ify cc. > +# You can override anything that is set by putting CC=3Dwhatever in your > +# Local/Makefile. > + > +# NOTE: You should never need to edit any of the distributed Makefiles; = all > +# overriding can be done in your Local/Makefile(s). This will make it ea= sier > +# for you when the next release comes along. > + > +# The location of the X11 libraries is something else that is quite vari= able > +# even between different versions of the same operating system (and inde= ed > +# there are different versions of X11 as well, of course). The four sett= ings > +# concerned here are X11, XINCLUDE, XLFLAGS (linking flags) and X11_LD_L= IB > +# (dynamic run-time library). You need not worry about X11 unless you wa= nt to > +# compile the Exim monitor utility. Exim itself does not use X11. > + > +# Another area of variability between systems is the type and location o= f the > +# DBM library package. Exim has support for ndbm, gdbm, tdb, and Berkele= y DB. > +# By default the code assumes ndbm; this often works with gdbm or DB, pr= ovided > +# they are correctly installed, via their compatibility interfaces. Howe= ver, > +# Exim can also be configured to use the native calls for Berkeley DB (o= bsolete > +# versions 1.85, 2.x, 3.x, or the current 4.x version) and also for gdbm= . > + > +# For some operating systems, a default DBM library (other than ndbm) is > +# selected by a setting in the OS-specific Makefile. Most modern OS now = have > +# a DBM library installed as standard, and in many cases this will be se= lected > +# for you by the OS-specific configuration. If Exim compiles without any > +# problems, you probably do not have to worry about the DBM library. If = you > +# do want or need to change it, you should first read the discussion in = the > +# file doc/dbm.discuss.txt, which also contains instructions for testing= Exim's > +# interface to the DBM library. > + > +# In Local/Makefiles blank lines and lines starting with # are ignored. = It is > +# also permitted to use the # character to add a comment to a setting, f= or > +# example > +# > +# EXIM_GID=3D42 =A0 # the "mail" group > +# > +# However, with some versions of "make" this works only if there is no w= hite > +# space between the end of the setting and the #, so perhaps it is best > +# avoided. A consequence of this facility is that 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. > +########################################################################= ####### > + > + > + > +########################################################################= ####### > +# =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0THESE ARE THINGS YOU MUST SPECI= FY =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# > +########################################################################= ####### > + > +# Exim will not build unless you specify BIN_DIRECTORY, CONFIGURE_FILE, = and > +# EXIM_USER. You also need EXIM_GROUP if EXIM_USER specifies a uid by nu= mber. > + > +# If you don't specify SPOOL_DIRECTORY, Exim won't fail to build. Howeve= r, it > +# really is a very good idea to specify it here rather than at run time.= This > +# is particularly true if you let the logs go to their default location = in the > +# spool directory, because it means that the location of the logs is kno= wn > +# before Exim has read the run time configuration file. > + > +#-----------------------------------------------------------------------= ------- > +# BIN_DIRECTORY defines where the exim binary will be installed by "make > +# install". The path 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. The= re is > +# no "standard" place for the binary directory. Some people like to keep= all > +# the Exim files under one directory such as /usr/exim; others just let = the > +# Exim binaries go into an existing directory such as /usr/sbin or > +# /usr/local/sbin. The installation script will try to create this direc= tory, > +# and any superior directories, if they do not exist. > + > +BIN_DIRECTORY=3D/usr/sbin > + > + > +#-----------------------------------------------------------------------= ------- > +# CONFIGURE_FILE defines where Exim's run time configuration file is to = be > +# found. It is the complete pathname for the file, not just a directory.= The > +# location of all other run time files and directories can be changed in= the > +# run time configuration file. There is a lot of variety in the choice o= f > +# location in different OS, and in the preferences of different sysadmin= s. Some > +# common locations are in /etc or /etc/mail or /usr/local/etc or > +# /usr/local/etc/mail. Another possibility is to keep all the Exim files= under > +# a single directory such as /usr/exim. Whatever you choose, the install= ation > +# script will try to make the directory and any superior directories if = they > +# don't exist. It will also install a default runtime configuration if t= his > +# file does not exist. > + > +CONFIGURE_FILE=3D/etc/mail/exim.conf > + > +# It is possible to specify a colon-separated list of files for CONFIGUR= E_FILE. > +# In this case, Exim will use the first of them that exists when it is r= un. > +# However, if a list is specified, the installation script no longer tri= es to > +# make superior directories or to install a default runtime configuratio= n. > + > + > +#-----------------------------------------------------------------------= ------- > +# The Exim binary must normally be setuid root, so that it starts execut= ing as > +# root, but (depending on the options with which it is called) it does n= ot > +# always need to retain the root privilege. These settings define the us= er and > +# group that is used for Exim processes when they no longer need to be r= oot. In > +# particular, this applies when receiving messages and when doing remote > +# deliveries. (Local deliveries run as various non-root users, typically= as the > +# owner of a local mailbox.) Specifying these values as root is not supp= orted. > + > +EXIM_USER=3Dref:exim > + > +# If you specify EXIM_USER as a name, this is looked up at build time, a= nd the > +# uid number is built into the binary. However, you can specify that thi= s > +# lookup is deferred until runtime. In this case, it is the name that is= built > +# into the binary. You can do this by a setting of the form: > + > +# EXIM_USER=3Dref:exim > + > +# In other words, put "ref:" in front of the user name. If you set EXIM_= USER > +# like this, any value specified for EXIM_GROUP is also passed "by refer= ence". > +# Although this costs a bit of resource at runtime, it is convenient to = use > +# this feature when building binaries that are to be run on multiple sys= tems > +# where the name may refer to different uids. It also allows you to buil= d Exim > +# on a system where there is no Exim user defined. > + > +# If the setting of EXIM_USER is numeric (e.g. EXIM_USER=3D42), there mu= st > +# also be a setting of EXIM_GROUP. If, on the other hand, you use a name > +# for EXIM_USER (e.g. EXIM_USER=3Dexim), you don't need to set EXIM_GROU= P unless > +# you want to use a group other than the default group for the given use= r. > + > +# EXIM_GROUP=3D > + > +# Many sites define a user called "exim", with an appropriate default gr= oup, > +# and use > +# > +# EXIM_USER=3Dexim > +# > +# while leaving EXIM_GROUP unspecified (commented out). > + > + > +#-----------------------------------------------------------------------= ------- > +# SPOOL_DIRECTORY defines the directory where all the data for messages = in > +# transit is kept. It is strongly recommended that you define it here, t= hough > +# it is possible to leave this till the run time configuration. > + > +# Exim creates the spool directory if it does not exist. The owner and g= roup > +# will be those defined by EXIM_USER and EXIM_GROUP, and this also appli= es to > +# all the files and directories that are created in the spool directory. > + > +# Almost all installations choose this: > + > +SPOOL_DIRECTORY=3D/var/spool/exim > + > + > + > +########################################################################= ####### > +# =A0 =A0 =A0 =A0 =A0 THESE ARE THINGS YOU PROBABLY WANT TO SPECIFY =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # > +########################################################################= ####### > + > +# If you need extra header file search paths on all compiles, put the -I > +# options in INCLUDE. =A0If you want the extra searches only for certain > +# parts of the build, see more specific xxx_INCLUDE variables below. > + > +# INCLUDE=3D-I/example/include > + > +# You need to specify some routers and transports if you want the Exim t= hat you > +# are building to be capable of delivering mail. You almost certainly ne= ed at > +# least one type of lookup. You should consider whether you want to buil= d > +# the Exim monitor or not. > + > + > +#-----------------------------------------------------------------------= ------- > +# These settings determine which individual router drivers are included = in the > +# Exim binary. There are no defaults in the code; those routers that are= wanted > +# must be defined here by setting the appropriate variables to the value= "yes". > +# Including a router in the binary does not cause it to be used automati= cally. > +# It has also to be configured in the run time configuration file. By > +# commenting out those you know you don't want to use, you can make the = binary > +# a bit smaller. If you are unsure, leave all of these included for now. > + > +ROUTER_ACCEPT=3Dyes > +ROUTER_DNSLOOKUP=3Dyes > +ROUTER_IPLITERAL=3Dyes > +ROUTER_MANUALROUTE=3Dyes > +ROUTER_QUERYPROGRAM=3Dyes > +ROUTER_REDIRECT=3Dyes > + > +# This one is very special-purpose, so is not included by default. > + > +# ROUTER_IPLOOKUP=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# These settings determine which individual transport drivers are includ= ed in > +# the Exim binary. There are no defaults; those transports that are want= ed must > +# be defined here by setting the appropriate variables to the value "yes= ". > +# Including a transport in the binary does not cause it to be used > +# automatically. It has also to be configured in the run time configurat= ion > +# file. By commenting out those you know you don't want to use, you can = make > +# the binary a bit smaller. If you are unsure, leave all of these includ= ed for > +# now. > + > +TRANSPORT_APPENDFILE=3Dyes > +TRANSPORT_AUTOREPLY=3Dyes > +TRANSPORT_PIPE=3Dyes > +TRANSPORT_SMTP=3Dyes > + > +# This one is special-purpose, and commonly not required, so it is not > +# included by default. > + > +TRANSPORT_LMTP=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# The appendfile transport can write messages to local mailboxes in a nu= mber > +# of formats. The code for three specialist formats, maildir, mailstore,= and > +# MBX, is included only when requested. If you do not know what this is = about, > +# leave these settings commented out. > + > +SUPPORT_MAILDIR=3Dyes > +# SUPPORT_MAILSTORE=3Dyes > +# SUPPORT_MBX=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# See below for dynamic lookup modules. > +# LOOKUP_MODULE_DIR=3D/usr/lib/exim/lookups/ > +# If not using package management but using this anyway, then think abou= t how > +# you perform upgrades and revert them. You should consider the benefit = of > +# embedding the Exim version number into LOOKUP_MODULE_DIR, so that you = can > +# maintain two concurrent sets of modules. > + > +# To build a module dynamically, you'll need to define CFLAGS_DYNAMIC fo= r > +# your platform. =A0Eg: > +# CFLAGS_DYNAMIC=3D-shared -rdynamic > +# CFLAGS_DYNAMIC=3D-shared -rdynamic -fPIC > + > +#-----------------------------------------------------------------------= ------- > +# These settings determine which file and database lookup methods are in= cluded > +# in the binary. See the manual chapter entitled "File and database look= ups" > +# for discussion. DBM and lsearch (linear search) are included by defaul= t. If > +# you are unsure about the others, leave them commented out for now. > +# LOOKUP_DNSDB does *not* refer to general mail routing using the DNS. I= t is > +# for the specialist case of using the DNS as a general database facilit= y (not > +# common). > +# If set to "2" instead of "yes" then the corresponding lookup will be > +# built as a module and must be installed into LOOKUP_MODULE_DIR. You ne= ed to > +# add -export-dynamic -rdynamic to EXTRALIBS. You may also need to add -= ldl to > +# EXTRALIBS so that dlopen() is available to Exim. You need to define > +# LOOKUP_MODULE_DIR above so the exim binary actually loads dynamic look= up > +# modules. > +# Also, instead of adding all the libraries/includes to LOOKUP_INCLUDE a= nd > +# LOOKUP_LIBS, add them to the respective LOOKUP_*_INCLUDE and LOOKUP_*_= LIBS > +# (where * is the name as given here in this list). That ensures that on= ly > +# the dynamic library and not the exim binary will be linked against the > +# library. > +# NOTE: LDAP cannot be built as a module! > + > +LOOKUP_DBM=3Dyes > +LOOKUP_LSEARCH=3Dyes > +LOOKUP_DNSDB=3Dyes > + > +# LOOKUP_CDB=3Dyes > +LOOKUP_DSEARCH=3Dyes > +# LOOKUP_IBASE=3Dyes > +# LOOKUP_LDAP=3Dyes > +# LOOKUP_MYSQL=3Dyes > +# LOOKUP_NIS=3Dyes > +# LOOKUP_NISPLUS=3Dyes > +# LOOKUP_ORACLE=3Dyes > +# LOOKUP_PASSWD=3Dyes > +# LOOKUP_PGSQL=3Dyes > +# LOOKUP_SQLITE=3Dyes > +# LOOKUP_WHOSON=3Dyes > + > +# These two settings are obsolete; all three lookups are compiled when > +# LOOKUP_LSEARCH is enabled. However, we retain these for backward > +# compatibility. Setting one forces LOOKUP_LSEARCH if it is not set. > + > +# LOOKUP_WILDLSEARCH=3Dyes > +# LOOKUP_NWILDLSEARCH=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# If you have set LOOKUP_LDAP=3Dyes, you should set LDAP_LIB_TYPE to ind= icate > +# which LDAP library you have. Unfortunately, though most of their funct= ions > +# are the same, there are minor differences. Currently Exim knows about = four > +# LDAP libraries: the one from the University of Michigan (also known as > +# OpenLDAP 1), OpenLDAP 2, the Netscape SDK library, and the library tha= t comes > +# with Solaris 7 onwards. Uncomment whichever of these you are using. > + > +# LDAP_LIB_TYPE=3DOPENLDAP1 > +# LDAP_LIB_TYPE=3DOPENLDAP2 > +# LDAP_LIB_TYPE=3DNETSCAPE > +# LDAP_LIB_TYPE=3DSOLARIS > + > +# If you don't set any of these, Exim assumes the original University of > +# Michigan (OpenLDAP 1) library. > + > + > +#-----------------------------------------------------------------------= ------- > +# The PCRE library is required for exim. =A0There is no longer an embedd= ed > +# version of the PCRE library included with the source code, instead you > +# must use a system library or build your own copy of PCRE. > +# In either case you must specify the library link info here. =A0If the > +# PCRE header files are not in the standard search path you must also > +# modify the INCLUDE path (above) > +# The default setting of PCRE_LIBS should work on the vast majority of > +# systems > + > +PCRE_LIBS=3D-lpcre > + > + > +#-----------------------------------------------------------------------= ------- > +# Additional libraries and include directories may be required for some > +# lookup styles (e.g. LDAP, MYSQL or PGSQL). LOOKUP_LIBS is included onl= y on > +# the command for linking Exim itself, not on any auxiliary programs. Yo= u > +# don't need to set LOOKUP_INCLUDE if the relevant directories are alrea= dy > +# specified in INCLUDE. The settings below are just examples; -lpq is fo= r > +# PostgreSQL, -lgds is for Interbase, -lsqlite3 is for SQLite. > + > +# LOOKUP_INCLUDE=3D-I /usr/local/ldap/include -I /usr/local/mysql/includ= e -I /usr/local/pgsql/include > +# LOOKUP_LIBS=3D-L/usr/local/lib -lldap -llber -lmysqlclient -lpq -lgds = -lsqlite3 > + > + > +#-----------------------------------------------------------------------= ------- > +# 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 > +# monitor. The locations of various X11 directories for libraries and in= clude > +# files are defaulted in the OS/Makefile-Default file, but can be overri= dden in > +# local OS-specific make files. > + > + > + > + > +#-----------------------------------------------------------------------= ------- > +# Compiling Exim with content scanning support: If you want to compile E= xim > +# with support for message body content scanning, set WITH_CONTENT_SCAN = to > +# the value "yes". This will give you malware and spam scanning in the D= ATA ACL, > +# and the MIME ACL. Please read the documentation to learn more about th= ese > +# features. > + > +WITH_CONTENT_SCAN=3Dyes > + > +# If you want to use the deprecated "demime" condition in the DATA ACL, > +# uncomment the line below. Doing so will also explicitly turn on the > +# WITH_CONTENT_SCAN option. If possible, use the MIME ACL instead of > +# the "demime" condition. > + > +WITH_OLD_DEMIME=3Dyes > + > +# If you're using ClamAV and are backporting fixes to an old version, in= stead > +# of staying current (which is the more usual approach) then you may nee= d to > +# use an older API which uses a STREAM command, now deprecated, instead = of > +# zINSTREAM. =A0If you need to set this, please let the Exim developers = know, as > +# if nobody reports a need for it, we'll remove this option and clean up= the > +# code. =A0zINSTREAM was introduced with ClamAV 0.95. > +# > +# WITH_OLD_CLAMAV_STREAM=3Dyes > + > +#-----------------------------------------------------------------------= ------- > +# By default Exim includes code to support DKIM (DomainKeys Identified > +# Mail, RFC4871) signing and verification. =A0Verification of signatures= is > +# turned on by default. =A0See the spec for information on conditionally > +# disabling it. =A0To disable the inclusion of the entire feature, set > +# DISABLE_DKIM to "yes" > + > +# DISABLE_DKIM=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# Compiling Exim with experimental features. These are documented in > +# experimental-spec.txt. "Experimental" means that the way these feature= s are > +# implemented may still change. Backward compatibility is not guaranteed= . > + > +# Uncomment the following lines to add SPF support. You need to have lib= spf2 > +# installed on your system (www.libspf2.org). Depending on where it is i= nstalled > +# you may have to edit the CFLAGS and LDFLAGS lines. > + > +# EXPERIMENTAL_SPF=3Dyes > +# CFLAGS =A0+=3D -I/usr/local/include > +# LDFLAGS +=3D -lspf2 > + > +# Uncomment the following lines to add SRS (Sender rewriting scheme) sup= port. > +# You need to have libsrs_alt installed on your system (srs.mirtol.com). > +# Depending on where it is installed you may have to edit the CFLAGS and > +# LDFLAGS lines. > + > +# EXPERIMENTAL_SRS=3Dyes > +# CFLAGS =A0+=3D -I/usr/local/include > +# LDFLAGS +=3D -lsrs_alt > + > +# Uncomment the following lines to add Brightmail AntiSpam support. You = need > +# to have the Brightmail client SDK installed. Please check the experime= ntal > +# documentation for implementation details. You need to edit the CFLAGS = and > +# LDFLAGS lines. > + > +# EXPERIMENTAL_BRIGHTMAIL=3Dyes > +# CFLAGS =A0+=3D -I/opt/brightmail/bsdk-6.0/include > +# LDFLAGS +=3D -lxml2_single -lbmiclient_single -L/opt/brightmail/bsdk-6= .0/lib > + > + > + > +########################################################################= ####### > +# =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 THESE ARE THINGS YOU MIGHT WANT TO SPE= CIFY =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# > +########################################################################= ####### > + > +# The items in this section are those that are commonly changed accordin= g to > +# the sysadmin's preferences, but whose defaults are often acceptable. T= he > +# first five are concerned with security issues, where differing levels = of > +# paranoia are appropriate in different environments. Sysadmins also var= y in > +# their views on appropriate levels of defence in these areas. If you do= not > +# understand these issues, go with the defaults, which are used by many = sites. > + > + > +#-----------------------------------------------------------------------= ------- > +# Although Exim is normally a setuid program, owned by root, it refuses = to run > +# local deliveries as root by default. There is a runtime option called > +# "never_users" which lists the users that must never be used for local > +# deliveries. There is also the setting below, which provides a list tha= t > +# cannot be overridden at runtime. This guards against problems caused b= y > +# unauthorized changes to the runtime configuration. You are advised not= to > +# remove "root" from this option, but you can add other users if you wan= t. The > +# list is colon-separated. It must NOT contain any spaces. > + > +# FIXED_NEVER_USERS=3Droot:bin:daemon > +FIXED_NEVER_USERS=3Droot > + > + > +#-----------------------------------------------------------------------= ------- > +# By default, Exim insists that its configuration file be owned by root.= You > +# can specify one additional permitted owner here. > + > +# CONFIGURE_OWNER=3D > + > +# If the configuration file is group-writeable, Exim insists by default = that it > +# is owned by root. You can specify one additional permitted group owner= here. > + > +# CONFIGURE_GROUP=3D > + > +# If you specify CONFIGURE_OWNER or CONFIGURE_GROUP as a name, this is l= ooked > +# up at build time, and the uid or gid number is built into the binary. > +# However, you can specify that the lookup is deferred until runtime. In= this > +# case, it is the name that is built into the binary. You can do this by= a > +# setting of the form: > + > +# CONFIGURE_OWNER=3Dref:mail > +# CONFIGURE_GROUP=3Dref:sysadmin > + > +# In other words, put "ref:" in front of the user or group name. Althoug= h this > +# costs a bit of resource at runtime, it is convenient to use this featu= re when > +# building binaries that are to be run on multiple systems where the nam= es may > +# refer to different uids or gids. It also allows you to build Exim on a= system > +# where the relevant user or group is not defined. > + > + > +#-----------------------------------------------------------------------= ------- > +# The -C option allows Exim to be run with an alternate runtime configur= ation > +# file. When this is used by root, root privilege is retained by the bin= ary > +# (for any other caller including the Exim user, it is dropped). You can > +# restrict the location of alternate configurations by defining a prefix= below. > +# Any file used with -C must then start with this prefix (except that /d= ev/null > +# is also permitted if the caller is root, because that is used in the i= nstall > +# script). If the prefix specifies a directory that is owned by root, a > +# compromise of the Exim account does not permit arbitrary alternate > +# configurations to be used. The prefix can be more restrictive than jus= t a > +# directory (the second example). > + > +# ALT_CONFIG_PREFIX=3D/some/directory/ > +# ALT_CONFIG_PREFIX=3D/some/directory/exim.conf- > + > + > +#-----------------------------------------------------------------------= ------- > +# When a user other than root uses the -C option to override the configu= ration > +# file (including the Exim user when re-executing Exim to regain root > +# privileges for local message delivery), this will normally cause Exim = to > +# drop root privileges. The TRUSTED_CONFIG_LIST option, specifies a file= which > +# contains a list of trusted configuration filenames, one per line. If t= he -C > +# option is used by the Exim user or by the user specified in the > +# CONFIGURE_OWNER setting, to specify a configuration file which is list= ed in > +# the TRUSTED_CONFIG_LIST file, then root privileges are not dropped by = Exim. > + > +# TRUSTED_CONFIG_LIST=3D/usr/exim/trusted_configs > + > + > +#-----------------------------------------------------------------------= ------- > +# Uncommenting this option disables the use of the -D command line optio= n, > +# which changes the values of macros in the runtime configuration file. > +# This is another protection against somebody breaking into the Exim acc= ount. > + > +# DISABLE_D_OPTION=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# By contrast, you might be maintaining a system which relies upon the a= bility > +# to override values with -D and assumes that these will be passed throu= gh to > +# the delivery processes. =A0As of Exim 4.73, this is no longer the case= by > +# default. =A0Going forward, we strongly recommend that you use a shim E= xim > +# configuration file owned by root stored under TRUSTED_CONFIG_LIST. > +# That shim can set macros before .include'ing your main configuration f= ile. > +# > +# As a strictly transient measure to ease migration to 4.73, the > +# WHITELIST_D_MACROS value definies a colon-separated list of macro-name= s > +# which are permitted to be overridden from the command-line which will = be > +# honoured by the Exim user. =A0So these are macros that can persist to = delivery > +# time. > +# Examples might be -DTLS or -DSPOOL=3D/some/dir. =A0The values on the > +# command-line are filtered to only permit: [A-Za-z0-9_/.-]* > +# > +# This option is highly likely to be removed in a future release. =A0It = exists > +# only to make 4.73 as easy as possible to migrate to. =A0If you use it,= we > +# encourage you to schedule time to rework your configuration to not dep= end > +# upon it. =A0Most people should not need to use this. > +# > +# By default, no macros are whitelisted for -D usage. > + > +# WHITELIST_D_MACROS=3DTLS:SPOOL > + > +#-----------------------------------------------------------------------= ------- > +# Exim has support for the AUTH (authentication) extension of the SMTP > +# protocol, as defined by RFC 2554. If you don't know what SMTP authenti= cation > +# is, you probably won't want to include this code, so you should leave = these > +# settings commented out. If you do want to make use of SMTP authenticat= ion, > +# you must uncomment at least one of the following, so that appropriate = code is > +# included in the Exim binary. You will then need to set up the run time > +# configuration to make use of the mechanism(s) selected. > + > +AUTH_CRAM_MD5=3Dyes > +# AUTH_CYRUS_SASL=3Dyes > +AUTH_DOVECOT=3Dyes > +AUTH_PLAINTEXT=3Dyes > +AUTH_SPA=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# If you specified AUTH_CYRUS_SASL above, you should ensure that you hav= e the > +# Cyrus SASL library installed before trying to build Exim, and you prob= ably > +# want to uncomment the following line: > + > +# AUTH_LIBS=3D-lsasl2 > + > + > +#-----------------------------------------------------------------------= ------- > +# When Exim is decoding MIME "words" in header lines, most commonly for = use > +# in the $header_xxx expansion, it converts any foreign character sets t= o the > +# one that is set in the headers_charset option. The default setting is > +# defined by this setting: > + > +HEADERS_CHARSET=3D"ISO-8859-1" > + > +# If you are going to make use of $header_xxx expansions in your configu= ration > +# file, or if your users are going to use them in filter files, and the = normal > +# character set on your host is something other than ISO-8859-1, you mig= ht > +# like to specify a different default here. This value can be overridden= in > +# the runtime configuration, and it can also be overridden in individual= filter > +# files. > +# > +# IMPORTANT NOTE: The iconv() function is needed for character code > +# conversions. Please see the next item... > + > + > +#-----------------------------------------------------------------------= ------- > +# Character code conversions are possible only if the iconv() function i= s > +# installed on your operating system. There are two places in Exim where= this > +# is relevant: (a) The $header_xxx expansion (see the previous item), an= d (b) > +# the Sieve filter support. For those OS where iconv() is known to be in= stalled > +# as standard, the file in OS/Makefile-xxxx contains > +# > +# HAVE_ICONV=3Dyes > +# > +# If you are not using one of those systems, but have installed iconv(),= you > +# need to uncomment that line above. In some cases, you may find that ic= onv() > +# and its header file are not in the default places. You might need to u= se > +# something like this: > +# > +# HAVE_ICONV=3Dyes > +# CFLAGS=3D-O -I/usr/local/include > +# EXTRALIBS_EXIM=3D-L/usr/local/lib -liconv > +# > +# but of course there may need to be other things in CFLAGS and EXTRALIB= S_EXIM > +# as well. > + > + > +#-----------------------------------------------------------------------= ------- > +# The passwords for user accounts are normally encrypted with the crypt(= ) > +# function. Comparisons with encrypted passwords can be done using Exim'= s > +# "crypteq" expansion operator. (This is commonly used as part of the > +# configuration of an authenticator for use with SMTP AUTH.) At least on= e > +# operating system has an extended function called crypt16(), which uses= up to > +# 16 characters of a password (the normal crypt() uses only the first 8)= . Exim > +# supports the use of crypt16() as well as crypt() but note the warning = below. > + > +# You can always indicate a crypt16-encrypted password by preceding it w= ith > +# "{crypt16}". If you want the default handling (without any preceding > +# indicator) to use crypt16(), uncomment the following line: > + > +# DEFAULT_CRYPT=3Dcrypt16 > + > +# If you do that, you can still access the basic crypt() function by pre= ceding > +# an encrypted password with "{crypt}". For more details, see the descri= ption > +# of the "crypteq" condition in the manual chapter on string expansions. > + > +# Some operating systems do not include a crypt16() function, so Exim ha= s one > +# of its own, which it uses unless HAVE_CRYPT16 is defined. Normally, th= at will > +# be set in an OS-specific Makefile for the OS that have such a function= , so > +# you should not need to bother with it. > + > +# *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING *** > +# It turns out that the above is not entirely accurate. As well as crypt= 16() > +# there is a function called bigcrypt() that some operating systems have= . This > +# may or may not use the same algorithm, and both of them may be differe= nt to > +# Exim's built-in crypt16() that is used unless HAVE_CRYPT16 is defined. > +# > +# However, since there is now a move away from the traditional crypt() > +# functions towards using SHA1 and other algorithms, tidying up this are= a of > +# Exim is seen as very low priority. In practice, if you need to, you ca= n > +# define DEFAULT_CRYPT to the name of any function that has the same int= erface > +# as the traditional crypt() function. > +# *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING *** > + > + > +#-----------------------------------------------------------------------= ------- > +# Exim can be built to support the SMTP STARTTLS command, which implemen= ts > +# Transport Layer Security using SSL (Secure Sockets Layer). To do this,= you > +# must install the OpenSSL library package or the GnuTLS library. Exim c= ontains > +# no cryptographic code of its own. Uncomment the following lines if you= want > +# to build Exim with TLS support. If you don't know what this is all abo= ut, > +# leave these settings commented out. > + > +# This setting is required for any TLS support (either OpenSSL or GnuTLS= ) > +SUPPORT_TLS=3Dyes > + > +# Uncomment this setting if you are using OpenSSL > +TLS_LIBS=3D-lssl -lcrypto > + > +# Uncomment these settings if you are using GnuTLS > +# USE_GNUTLS=3Dyes > +# TLS_LIBS=3D-lgnutls -ltasn1 -lgcrypt > + > +# If you are running Exim as a server, note that just building it with T= LS > +# support is not all you need to do. You also need to set up a suitable > +# certificate, and tell Exim about it by means of the tls_certificate > +# and tls_privatekey run time options. You also need to set tls_advertis= e_hosts > +# to specify the hosts to which Exim advertises TLS support. On the othe= r hand, > +# if you are running Exim only as a client, building it with TLS support > +# is all you need to do. > + > +# Additional libraries and include files are required for both OpenSSL a= nd > +# GnuTLS. The TLS_LIBS settings above assume that the libraries are inst= alled > +# with all your other libraries. If they are in a special directory, you= may > +# need something like > + > +# TLS_LIBS=3D-L/usr/local/openssl/lib -lssl -lcrypto > +# or > +# TLS_LIBS=3D-L/opt/gnu/lib -lgnutls -ltasn1 -lgcrypt > + > +# TLS_LIBS is included only on the command for linking Exim itself, not = on any > +# auxiliary programs. If the include files are not in a standard place, = you can > +# set TLS_INCLUDE to specify where they are, for example: > + > +# TLS_INCLUDE=3D-I/usr/local/openssl/include/ > +# or > +# TLS_INCLUDE=3D-I/opt/gnu/include > + > +# You don't need to set TLS_INCLUDE if the relevant directories are alre= ady > +# specified in INCLUDE. > + > + > +#-----------------------------------------------------------------------= ------- > +# The default distribution of Exim contains only the plain text form of = the > +# documentation. Other forms are available separately. If you want to in= stall > +# the documentation in "info" format, first fetch the Texinfo documentat= ion > +# sources from the ftp directory and unpack them, which should create fi= les > +# with the extension "texinfo" in the doc directory. You may find that t= he > +# version number of the texinfo files is different to your Exim version = number, > +# because the main documentation isn't updated as often as the code. For > +# example, if you have Exim version 4.43, the source tarball upacks into= a > +# directory called exim-4.43, but the texinfo tarball unpacks into exim-= 4.40. > +# In this case, move the contents of exim-4.40/doc into exim-4.43/doc af= ter you > +# have unpacked them. Then set INFO_DIRECTORY to the location of your in= fo > +# directory. This varies from system to system, but is often /usr/share/= info. > +# Once you have done this, "make install" will build the info files and > +# install them in the directory you have defined. > + > +# INFO_DIRECTORY=3D/usr/share/info > + > + > +#-----------------------------------------------------------------------= ------- > +# 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. If you do not set anything, Exim creates a directo= ry > +# called "log" inside its spool directory (see SPOOL_DIRECTORY above) an= d uses > +# the filenames "mainlog", "paniclog", and "rejectlog". If you want to c= hange > +# this, you can set LOG_FILE_PATH to a path name containing one occurren= ce of > +# %s. This will be replaced by one of the strings "main", "panic", or "r= eject" > +# to form the final file names. Some installations may want something li= ke this: > + > +LOG_FILE_PATH=3D/var/log/exim/%slog > + > +# which results in files with names /var/log/exim_mainlog, etc. The dire= ctory > +# in which the log files are placed must exist; Exim does not try to cre= ate > +# it for itself. It is also your responsibility to ensure that Exim is c= apable > +# of writing files using this path name. The Exim user (see EXIM_USER ab= ove) > +# must be able to create and update files in the directory you have spec= ified. > + > +# You can also configure Exim to use syslog, instead of or as well as lo= g > +# files, by settings such as these > + > +# LOG_FILE_PATH=3Dsyslog > +# LOG_FILE_PATH=3Dsyslog:/var/log/exim_%slog > + > +# The first of these uses only syslog; the second uses syslog and also w= rites > +# to log files. Do not include white space in such a setting as it messe= s up > +# the building process. > + > + > +#-----------------------------------------------------------------------= ------- > +# When logging to syslog, the following option caters for syslog replace= ments > +# that are able to accept log entries longer than the 1024 characters al= lowed > +# by RFC 3164. It is up to you to make sure your syslog daemon can handl= e this. > +# Non-printable characters are usually unacceptable regardless, so log e= ntries > +# are still split on newline characters. > + > +# SYSLOG_LONG_LINES=3Dyes > + > +# If you are not interested in the process identifier (pid) of the Exim = that is > +# making the call to syslog, then comment out the following line. > + > +SYSLOG_LOG_PID=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# Cycling log files: this variable specifies the maximum number of old > +# log files that are kept by the exicyclog log-cycling script. You don't= have > +# to use exicyclog. If your operating system has other ways of cycling l= og > +# files, you can use them instead. The exicyclog script isn't run by def= ault; > +# you have to set up a cron job for it if you want it. > + > +EXICYCLOG_MAX=3D10 > + > + > +#-----------------------------------------------------------------------= ------- > +# The compress command is used by the exicyclog script to compress old l= og > +# files. Both the name of the command and the suffix that it adds to fil= es > +# need to be defined here. See also the EXICYCLOG_MAX configuration. > + > +COMPRESS_COMMAND=3D/bin/gzip > +COMPRESS_SUFFIX=3Dgz > + > + > +#-----------------------------------------------------------------------= ------- > +# If the exigrep utility is fed compressed log files, it tries to uncomp= ress > +# them using this command. > + > +ZCAT_COMMAND=3D/bin/zcat > + > + > +#-----------------------------------------------------------------------= ------- > +# Compiling in support for embedded Perl: If you want to be able to > +# use Perl code in Exim's string manipulation language and you have Perl > +# (version 5.004 or later) installed, set EXIM_PERL to perl.o. Using emb= edded > +# Perl costs quite a lot of resources. Only do this if you really need i= t. > + > +# EXIM_PERL=3Dperl.o > + > + > +#-----------------------------------------------------------------------= ------- > +# Support for dynamically-loaded string expansion functions via ${dlfunc= . If > +# you are using gcc the dynamically-loaded object must be compiled with = the > +# -shared option, and you will need to add -export-dynamic to EXTRALIBS = so > +# that the local_scan API is made available by the linker. You may also = need > +# to add -ldl to EXTRALIBS so that dlopen() is available to Exim. > + > +# EXPAND_DLFUNC=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# Exim has support for PAM (Pluggable Authentication Modules), a facilit= y > +# which is available in the latest releases of Solaris and in some GNU/L= inux > +# distributions (see http://ftp.kernel.org/pub/linux/libs/pam/). The Exi= m > +# support, which is intended for use in conjunction with the SMTP AUTH > +# facilities, is included only when requested by the following setting: > + > +# SUPPORT_PAM=3Dyes > + > +# You probably need to add -lpam to EXTRALIBS, and in some releases of > +# GNU/Linux -ldl is also needed. > + > + > +#-----------------------------------------------------------------------= ------- > +# Support for authentication via Radius is also available. The Exim supp= ort, > +# which is intended for use in conjunction with the SMTP AUTH facilities= , > +# is included only when requested by setting the following parameter to = the > +# location of your Radius configuration file: > + > +# RADIUS_CONFIG_FILE=3D/etc/radiusclient/radiusclient.conf > +# RADIUS_CONFIG_FILE=3D/etc/radius.conf > + > +# If you have set RADIUS_CONFIG_FILE, you should also set one of these t= o > +# indicate which RADIUS library is used: > + > +# RADIUS_LIB_TYPE=3DRADIUSCLIENT > +# RADIUS_LIB_TYPE=3DRADIUSCLIENTNEW > +# RADIUS_LIB_TYPE=3DRADLIB > + > +# RADIUSCLIENT is the radiusclient library; you probably need to add > +# =A0 -lradiusclient to EXTRALIBS. > +# > +# The API for the radiusclient library was changed at release 0.4.0. > +# Unfortunately, the header file does not define a version number that c= lients > +# can use to support both the old and new APIs. If you are using version= 0.4.0 > +# or later of the radiusclient library, you should use RADIUSCLIENTNEW. > +# > +# RADLIB is the Radius library that comes with FreeBSD (the header file = is > +# =A0 called radlib.h); you probably need to add -lradius to EXTRALIBS. > +# > +# If you do not set RADIUS_LIB_TYPE, Exim assumes the radiusclient libra= ry, > +# using the original API. > + > + > +#-----------------------------------------------------------------------= ------- > +# Support for authentication via the Cyrus SASL pwcheck daemon is availa= ble. > +# Note, however, that pwcheck is now deprecated in favour of saslauthd (= see > +# next item). The Exim support for pwcheck, which is intented for use in > +# conjunction with the SMTP AUTH facilities, is included only when reque= sted by > +# setting the following parameter to the location of the pwcheck daemon'= s > +# socket. > +# > +# There is no need to install all of SASL on your system. You just need = to run > +# ./configure --with-pwcheck, cd to the pwcheck directory within the sou= rces, > +# make and make install. You must create the socket directory (default > +# /var/pwcheck) and chown it to exim's user and group. Once you have ins= talled > +# pwcheck, you should arrange for it to be started by root at boot time. > + > +# CYRUS_PWCHECK_SOCKET=3D/var/pwcheck/pwcheck > + > + > +#-----------------------------------------------------------------------= ------- > +# Support for authentication via the Cyrus SASL saslauthd daemon is avai= lable. > +# The Exim support, which is intented for use in conjunction with the SM= TP AUTH > +# facilities, is included only when requested by setting the following > +# parameter to the location of the saslauthd daemon's socket. > +# > +# There is no need to install all of SASL on your system. You just need = to run > +# ./configure --with-saslauthd (and any other options you need, for exam= ple, to > +# select or deselect authentication mechanisms), cd to the saslauthd dir= ectory > +# within the sources, make and make install. You must create the socket > +# directory (default /var/state/saslauthd) and chown it to exim's user a= nd > +# group. Once you have installed saslauthd, you should arrange for it to= be > +# started by root at boot time. > + > +# CYRUS_SASLAUTHD_SOCKET=3D/var/state/saslauthd/mux > + > + > +#-----------------------------------------------------------------------= ------- > +# TCP wrappers: If you want to use tcpwrappers from within Exim, uncomme= nt > +# this setting. See the manual section entitled "Use of tcpwrappers" in = the > +# chapter on building and installing Exim. > +# > +# USE_TCP_WRAPPERS=3Dyes > +# > +# You may well also have to specify a local "include" file and an additi= onal > +# library for TCP wrappers, so you probably need something like this: > +# > +# USE_TCP_WRAPPERS=3Dyes > +# CFLAGS=3D-O -I/usr/local/include > +# EXTRALIBS_EXIM=3D-L/usr/local/lib -lwrap > +# > +# but of course there may need to be other things in CFLAGS and EXTRALIB= S_EXIM > +# as well. > +# > +# To use a name other than exim in the tcpwrappers config file, > +# e.g. if you're running multiple daemons with different access lists, > +# or multiple MTAs with the same access list, define > +# TCP_WRAPPERS_DAEMON_NAME accordingly > +# > +# TCP_WRAPPERS_DAEMON_NAME=3D"exim" > + > + > +#-----------------------------------------------------------------------= ------- > +# The default action of the exim_install script (which is run by "make > +# install") is to install the Exim binary with a unique name such as > +# exim-4.43-1, and then set up a symbolic link called "exim" to referenc= e it, > +# moving the symbolic link from any previous version. If you define NO_S= YMLINK > +# (the value doesn't matter), the symbolic link is not created or moved.= You > +# will then have to "turn Exim on" by setting up the link manually. > + > +# NO_SYMLINK=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# Another default action of the install script is to install a default r= untime > +# configuration file if one does not exist. This configuration has a rou= ter for > +# expanding system aliases. The default assumes that these aliases are k= ept > +# in the traditional file called /etc/aliases. If such a file does not e= xist, > +# the installation script creates one that contains just comments (no ac= tual > +# aliases). The following setting can be changed to specify a different > +# location for the system alias file. > + > +SYSTEM_ALIASES_FILE=3D/etc/mail/aliases > + > + > +#-----------------------------------------------------------------------= ------- > +# There are some testing options (-be, -bt, -bv) that read data from the > +# standard input when no arguments are supplied. By default, the input l= ines > +# are read using the standard fgets() function. This does not support li= ne > +# editing during interactive input (though the terminal's "erase" charac= ter > +# works as normal). If your operating system has the readline() function= , and > +# in addition supports dynamic loading of library functions, you can cau= se > +# Exim to use readline() for the -be testing option (only) by uncommenti= ng the > +# following setting. Dynamic loading is used so that the library is load= ed only > +# when the -be testing option is given; by the time the loading occurs, > +# Exim has given up its root privilege and is running as the calling use= r. This > +# is the reason why readline() is NOT supported for -bt and -bv, because= Exim > +# runs as root or as exim, respectively, for those options. When USE_REA= DLINE > +# is "yes", as well as supporting line editing, a history of input lines= in the > +# current run is maintained. > + > +# USE_READLINE=3Dyes > + > +# You may need to add -ldl to EXTRALIBS when you set USE_READLINE=3Dyes. > +# Note that this option adds to the size of the Exim binary, because the > +# dynamic loading library is not otherwise included. > + > + > + > +########################################################################= ####### > +# =A0 =A0 =A0 =A0 =A0 =A0 =A0THINGS YOU ALMOST NEVER NEED TO MENTION =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# > +########################################################################= ####### > + > +# The settings in this section are available for use in special circumst= ances. > +# In the vast majority of installations you need not change anything bel= ow. > + > + > +#-----------------------------------------------------------------------= ------- > +# The following commands live in different places in some OS. Either the > +# ultimate default settings, or the OS-specific files should already poi= nt to > +# the right place, but they can be overridden here if necessary. These s= ettings > +# are used when building various scripts to ensure that the correct path= s are > +# used when the scripts are run. They are not used in the Makefile itsel= f. Perl > +# is not necessary for running Exim unless you set EXIM_PERL (see above)= to get > +# it embedded, but there are some utilities that are Perl scripts. If yo= u > +# haven't got Perl, Exim will still build and run; you just won't be abl= e to > +# use those utilities. > + > +# CHOWN_COMMAND=3D/usr/bin/chown > +# CHGRP_COMMAND=3D/usr/bin/chgrp > +# CHMOD_COMMAND=3D/usr/bin/chmod > +# MV_COMMAND=3D/bin/mv > +# RM_COMMAND=3D/bin/rm > +# TOUCH_COMMAND=3D/usr/bin/touch > +# PERL_COMMAND=3D/usr/bin/perl > + > + > +#-----------------------------------------------------------------------= ------- > +# The following macro can be used to change the command for building a l= ibrary > +# of functions. By default the "ar" command is used, with options "cq". > +# Only in rare circumstances should you need to change this. > + > +# AR=3Dar cq > + > + > +#-----------------------------------------------------------------------= ------- > +# In some operating systems, the value of the TMPDIR environment variabl= e > +# controls where temporary files are created. Exim does not make use of > +# temporary files, except when delivering to MBX mailboxes. However, if = Exim > +# calls any external libraries (e.g. DBM libraries), they may use tempor= ary > +# files, and thus be influenced by the value of TMPDIR. For this reason,= when > +# Exim starts, it checks the environment for TMPDIR, and if it finds it = is set, > +# it replaces the value with what is defined here. Commenting this setti= ng > +# suppresses the check altogether. > + > +TMPDIR=3D"/tmp" > + > + > +#-----------------------------------------------------------------------= ------- > +# The following macros can be used to change the default modes that are = used > +# by the appendfile transport. In most installations the defaults are ju= st > +# fine, and in any case, you can change particular instances of the tran= sport > +# at run time if you want. > + > +# APPENDFILE_MODE=3D0600 > +# APPENDFILE_DIRECTORY_MODE=3D0700 > +# APPENDFILE_LOCKFILE_MODE=3D0600 > + > + > +#-----------------------------------------------------------------------= ------- > +# In some installations there may be multiple machines sharing file syst= ems, > +# where a different configuration file is required for Exim on the diffe= rent > +# 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=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# In some esoteric configurations two different versions of Exim are run= , > +# with different setuid values, and different configuration files are re= quired > +# 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 defin= ed > +# 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 e= xist, > +# 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 file= s > +# are tried: .., ., ., and . > + > +# CONFIGURE_FILE_USE_EUID=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# The size of the delivery buffers: These specify the sizes (in bytes) o= f > +# the buffers that are used when copying a message from the spool to a > +# destination. There is rarely any need to change these values. > + > +# DELIVER_IN_BUFFER_SIZE=3D8192 > +# DELIVER_OUT_BUFFER_SIZE=3D8192 > + > + > +#-----------------------------------------------------------------------= ------- > +# The mode of the database directory: Exim creates a directory called "d= b" > +# 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. > + > +# EXIMDB_DIRECTORY_MODE=3D0750 > + > + > +#-----------------------------------------------------------------------= ------- > +# Database file mode: The mode of files created in the "db" directory de= faults > +# to 0640 in the source, and can be changed here. > + > +# EXIMDB_MODE=3D0640 > + > + > +#-----------------------------------------------------------------------= ------- > +# 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. > + > +# EXIMDB_LOCKFILE_MODE=3D0640 > + > + > +#-----------------------------------------------------------------------= ------- > +# This parameter sets the maximum length of the header portion of a mess= age > +# that Exim is prepared to process. The default setting is one megabyte.= The > +# limit exists in order to catch rogue mailers that might connect to you= r SMTP > +# port, start off a header line, and then just pump junk at it for ever.= The > +# message_size_limit option would also catch this, but it may not be set= . > +# The value set here is the default; it can be changed at runtime. > + > +# HEADER_MAXSIZE=3D"(1024*1024)" > + > + > +#-----------------------------------------------------------------------= ------- > +# The mode of the input directory: The input directory is where messages= are > +# kept while awaiting delivery. Exim creates it if necessary, using a mo= de > +# which can be defined here (default 0750). > + > +# INPUT_DIRECTORY_MODE=3D0750 > + > + > +#-----------------------------------------------------------------------= ------- > +# The mode of Exim's log directory, when it is created by Exim inside th= e spool > +# directory, defaults to 0750 but can be changed here. > + > +# LOG_DIRECTORY_MODE=3D0750 > + > + > +#-----------------------------------------------------------------------= ------- > +# The log files themselves are created as required, with a mode that def= aults > +# to 0640, but which can be changed here. > + > +# LOG_MODE=3D0640 > + > + > +#-----------------------------------------------------------------------= ------- > +# The TESTDB lookup is for performing tests on the handling of lookup re= sults, > +# and is not useful for general running. It should be included only when > +# debugging the code of Exim. > + > +# LOOKUP_TESTDB=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# /bin/sh is used by default as the shell in which to run commands that = are > +# defined in the makefiles. This can be changed if necessary, by uncomme= nting > +# this line and specifying another shell, but note that a Bourne-compati= ble > +# shell is expected. > + > +# MAKE_SHELL=3D/bin/sh > + > + > +#-----------------------------------------------------------------------= ------- > +# The maximum number of named lists of each type (address, domain, host,= and > +# local part) can be increased by changing this value. It should be set = to > +# a multiple of 16. > + > +MAX_NAMED_LIST=3D16 > + > + > +#-----------------------------------------------------------------------= ------- > +# Network interfaces: Unless you set the local_interfaces option in the = runtime > +# configuration file to restrict Exim to certain interfaces only, it wil= l run > +# code to find all the interfaces there are on your host. Unfortunately, > +# the call to the OS that does this requires a buffer large enough to ho= ld > +# data for all the interfaces - it was designed in the days when a host = rarely > +# had more than three or four interfaces. Nowadays hosts can have very m= any > +# virtual interfaces running on the same hardware. If you have more than= 250 > +# virtual interfaces, you will need to uncomment this setting and increa= se the > +# value. > + > +# MAXINTERFACES=3D250 > + > + > +#-----------------------------------------------------------------------= ------- > +# 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 "msglo= g" > +# 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_o= utput" > +# option for transports). > + > +# MSGLOG_DIRECTORY_MODE=3D0750 > + > + > +#-----------------------------------------------------------------------= ------- > +# There are three options which are used when compiling the Perl interfa= ce and > +# when linking with Perl. The default values for these are placed automa= tically > +# at the head of the Makefile by the script which builds it. However, if= you > +# want to override them, you can do so here. > + > +# PERL_CC=3D > +# PERL_CCOPTS=3D > +# PERL_LIBS=3D > + > + > +#-----------------------------------------------------------------------= ------- > +# Identifying the daemon: When an Exim daemon starts up, it writes its p= id > +# (process id) to a file so that it can easily be identified. The path o= f the > +# file can be specified here. Some installations may want something like= this: > + > +PID_FILE_PATH=3D/var/run/exim.pid > + > +# If PID_FILE_PATH is not defined, Exim writes a file in its spool direc= tory > +# using the name "exim-daemon.pid". > + > +# If you start up a daemon without the -bd option (for example, with jus= t > +# the -q15m option), a pid file is not written. Also, if you override th= e > +# configuration file with the -oX option, no pid file is written. In oth= er > +# words, the pid file is written only for a "standard" daemon. > + > + > +#-----------------------------------------------------------------------= ------- > +# If Exim creates the spool directory, it is given this mode, defaulting= in the > +# source to 0750. > + > +# SPOOL_DIRECTORY_MODE=3D0750 > + > + > +#-----------------------------------------------------------------------= ------- > +# The mode of files on the input spool which hold the contents of messag= es can > +# be changed here. The default is 0640 so that information from the spoo= l is > +# available to anyone who is a member of the Exim group. > + > +# SPOOL_MODE=3D0640 > + > + > +#-----------------------------------------------------------------------= ------- > +# Moving frozen messages: If the following is uncommented, Exim is compi= led > +# with support for automatically moving frozen messages out of the main = spool > +# directory, a facility that is found useful by some large installations= . A > +# run time option is required to cause the moving actually to occur. Suc= h > +# messages become "invisible" to the normal management tools. > + > +# SUPPORT_MOVE_FROZEN_MESSAGES=3Dyes > + > + > +#-----------------------------------------------------------------------= ------- > +# Disabling the use of fsync(): DO NOT UNCOMMENT THE FOLLOWING LINE unle= ss you > +# really, really, really know what you are doing. And even then, think a= gain. > +# You should never uncomment this when compiling a binary for distributi= on. > +# Use it only when compiling Exim for your own use. > +# > +# Uncommenting this line enables the use of a runtime option called > +# disable_fsync, which can be used to stop Exim using fsync() to ensure = that > +# files are written to disc before proceeding. When this is disabled, cr= ashes > +# and hardware problems such as power outages can cause data to be lost.= This > +# feature should only be used in very exceptional circumstances. YOU HAV= E BEEN > +# WARNED. > + > +# ENABLE_DISABLE_FSYNC=3Dyes > + > +HAVE_IPV6=3DYES > +# LOOKUP_LIBS=3D-lldap > +# EXTRALIBS_EXIM=3D-lpam > +# End of EDITME for Exim 4. > diff --git a/testing/exim/exim.confd b/testing/exim/exim.confd > new file mode 100644 > index 0000000..a3974d3 > --- /dev/null > +++ b/testing/exim/exim.confd > @@ -0,0 +1,2 @@ > +# Command-line options for running exim > +EXIM_OPTS=3D"-bd -q15m" > diff --git a/testing/exim/exim.initd b/testing/exim/exim.initd > new file mode 100644 > index 0000000..fcd46d4 > --- /dev/null > +++ b/testing/exim/exim.initd > @@ -0,0 +1,30 @@ > +#!/sbin/runscript > +# Copyright 1999-2011 Gentoo Foundation > +# Distributed under the terms of the GNU General Public License v2 > +# $Header: /var/cvsroot/gentoo-x86/mail-mta/exim/files/exim.rc7,v 1.2 20= 11/08/16 16:51:36 idl0r Exp $ > + > +opts=3D"${opts} reload" > + > +depend() { > + =A0 =A0 =A0 need logger > + =A0 =A0 =A0 use antivirus net > + =A0 =A0 =A0 provide mta > +} > + > +start() { > + =A0 =A0 =A0 ebegin "Starting ${SVCNAME}" > + =A0 =A0 =A0 start-stop-daemon --start --quiet --exec /usr/sbin/exim --p= idfile /var/run/${SVCNAME}.pid -- -C /etc/exim/${SVCNAME}.conf ${EXIM_OPTS:= --bd -q15m} > + =A0 =A0 =A0 eend $? > +} > + > +stop() { > + =A0 =A0 =A0 ebegin "Stopping ${SVCNAME}" > + =A0 =A0 =A0 start-stop-daemon --stop --quiet --pidfile /var/run/${SVCNA= ME}.pid --name exim > + =A0 =A0 =A0 eend $? > +} > + > +reload() { > + =A0 =A0 =A0 ebegin "Reloading ${SVCNAME}" > + =A0 =A0 =A0 start-stop-daemon --signal HUP --pidfile /var/run/${SVCNAME= }.pid --name exim > + =A0 =A0 =A0 eend $? > +} > diff --git a/testing/exim/exim.logrotate b/testing/exim/exim.logrotate > new file mode 100644 > index 0000000..7d99b55 > --- /dev/null > +++ b/testing/exim/exim.logrotate > @@ -0,0 +1,13 @@ > +/var/log/exim/exim*.log { > + =A0 =A0 =A0 daily > + =A0 =A0 =A0 missingok > + =A0 =A0 =A0 rotate 28 > + =A0 =A0 =A0 compress > + =A0 =A0 =A0 delaycompress > + =A0 =A0 =A0 notifempty > + =A0 =A0 =A0 create 640 mail mail > + =A0 =A0 =A0 sharedscripts > + =A0 =A0 =A0 postrotate > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 /etc/init.d/exim reload > /dev/null > + =A0 =A0 =A0 endscript > +} > -- > 1.7.4.5 > > > > --- > Unsubscribe: =A0alpine-devel+unsubscribe@lists.alpinelinux.org > Help: =A0 =A0 =A0 =A0 alpine-devel+help@lists.alpinelinux.org > --- > > Hi, Committed but also had to update checksums. I also set -j1 cause of build errors. Thx! --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---