diff options
Diffstat (limited to 'network')
| -rw-r--r-- | network/exim/README | 25 | ||||
| -rw-r--r-- | network/exim/contrib/exim.cron | 12 | ||||
| -rw-r--r-- | network/exim/contrib/exim.logrotate | 8 | ||||
| -rw-r--r-- | network/exim/contrib/rc.exim.new | 62 | ||||
| -rw-r--r-- | network/exim/doinst.sh | 28 | ||||
| -rw-r--r-- | network/exim/exim.Makefile | 1155 | ||||
| -rwxr-xr-x | network/exim/exim.SlackBuild | 116 | ||||
| -rw-r--r-- | network/exim/exim.info | 10 | ||||
| -rw-r--r-- | network/exim/manpages/exicyclog.8 | 74 | ||||
| -rw-r--r-- | network/exim/manpages/exigrep.8 | 69 | ||||
| -rw-r--r-- | network/exim/manpages/exim_checkaccess.8 | 79 | ||||
| -rw-r--r-- | network/exim/manpages/exim_db.8 | 168 | ||||
| -rw-r--r-- | network/exim/manpages/exim_dbmbuild.8 | 104 | ||||
| -rw-r--r-- | network/exim/manpages/exim_lock.8 | 136 | ||||
| -rw-r--r-- | network/exim/manpages/eximon.8 | 49 | ||||
| -rw-r--r-- | network/exim/manpages/exinext.8 | 72 | ||||
| -rw-r--r-- | network/exim/manpages/exiqgrep.8 | 86 | ||||
| -rw-r--r-- | network/exim/manpages/exiqsumm.8 | 73 | ||||
| -rw-r--r-- | network/exim/manpages/exiwhat.8 | 101 | ||||
| -rw-r--r-- | network/exim/slack-desc | 19 |
20 files changed, 2446 insertions, 0 deletions
diff --git a/network/exim/README b/network/exim/README new file mode 100644 index 0000000000000..9c57aaadbb2a1 --- /dev/null +++ b/network/exim/README @@ -0,0 +1,25 @@ +Exim is a mail transfer agent (MTA) used on Unix-like operating systems. +It is freely available under the GNU GPL and it aims to be a general +and flexible mailer with extensive facilities for checking incoming e-mail. + +Exim was orginally written by Philip Hazel for use in the University +of Cambridge Computing Services e-mail systems. + +Before you can build Exim, you have to create an "exim" user and group: + # groupadd -g 222 exim + # useradd -d /var/spool/exim -g exim -s /bin/false -u 222 exim +The recommended uid/gid is 222, but others are fine if you prefer - +see http://slackbuilds.org/uid_gid.txt for other recommendations. + +There's no "configure" script; instead Exim is configured by editing a well +documented Makefile, which is then included during the build process. The +provided "exim.Makefile" will build an all-purpose Exim daemon with almost +all of the features that will work on a standard Slackware system. + +Exim can be integrated with other email tools such as Clamav, Spamassassin, +Bogofilter, and others available at Slackbuilds.org. You might also be +interested in the "exim-html" package, an extensive documentation for Exim. + +WARNING: this package is intended as a drop-in replacement for Sendmail. +As a result, there are some inevitable filename conflicts between Sendmail +and Exim. REMOVE SENDMAIL BEFORE INSTALLING THIS PACKAGE! diff --git a/network/exim/contrib/exim.cron b/network/exim/contrib/exim.cron new file mode 100644 index 0000000000000..94d7442b60c3e --- /dev/null +++ b/network/exim/contrib/exim.cron @@ -0,0 +1,12 @@ +#!/bin/sh + +# Exim's spool directory +SPOOL=/var/spool/exim + +# Check for spool and the tidydb utility +test -d $SPOOL -a -x /usr/sbin/exim_tidydb || exit + +# Tidy up the contents of the hints databases +find $SPOOL/db -name '*.lockfile' -exec basename {} .lockfile \; \ + | xargs -r -n 1 sudo -u exim /usr/sbin/exim_tidydb -t 7d $SPOOL \ + > /dev/null diff --git a/network/exim/contrib/exim.logrotate b/network/exim/contrib/exim.logrotate new file mode 100644 index 0000000000000..8a55fce2ceaaf --- /dev/null +++ b/network/exim/contrib/exim.logrotate @@ -0,0 +1,8 @@ +/var/log/exim/*.log { + missingok + notifempty + sharedscripts + postrotate + /usr/bin/pkill -HUP -u exim + endscript +} diff --git a/network/exim/contrib/rc.exim.new b/network/exim/contrib/rc.exim.new new file mode 100644 index 0000000000000..16d1ca71d0ba4 --- /dev/null +++ b/network/exim/contrib/rc.exim.new @@ -0,0 +1,62 @@ +#!/bin/sh + +# /etc/rc.d/rc.exim - start/stop/restart the exim mail transfer agent. +# +# Thales A. Tsailas <ttsailas@enforcingit.com> +# Thomas Morper <thomas@beingboiled.info> + +PIDFILE=/var/run/exim.pid + +# the TIME option causes Exim to run as a daemon, starting a queue runner +# process at intervals specified by the given time value. (ie 5m, 1h etc). +TIME=15m + +exim_start() { + echo "Starting exim..." + /usr/sbin/exim -bd ${TIME:+-q$TIME} +} + +exim_stop() { + echo "Shutting down exim..." + killall exim + rm -f $PIDFILE +} + +exim_reload() { + echo "Reloading exim configuration..." + if [ -f $PIDFILE ]; then + kill -HUP $(cat $PIDFILE) + fi +} + +exim_status() { + if [ -f /var/run/exim.pid ]; then + echo "exim is running..."; + else + echo "exim is not running..."; + fi +} + +# See how we were called. +case "$1" in + start) + exim_start + ;; + stop) + exim_stop + ;; + restart) + exim_stop + sleep 2 + exim_start + ;; + reload) + exim_reload + ;; + status) + exim_status + ;; + *) + echo $"Usage: $0 {start|stop|restart|reload|status}" + ;; +esac diff --git a/network/exim/doinst.sh b/network/exim/doinst.sh new file mode 100644 index 0000000000000..4e583ff92aff1 --- /dev/null +++ b/network/exim/doinst.sh @@ -0,0 +1,28 @@ +config() { + NEW="$1" + OLD="$(dirname $NEW)/$(basename $NEW .new)" + # If there's no config file by that name, mv it over: + if [ ! -r $OLD ]; then + mv $NEW $OLD + elif [ "$(cat $OLD | md5sum)" = "$(cat $NEW | md5sum)" ]; then + # toss the redundant copy + rm $NEW + fi + # Otherwise, we leave the .new copy for the admin to consider... +} + +preserve_perms() { + NEW="$1" + OLD="$(dirname ${NEW})/$(basename ${NEW} .new)" + if [ -e ${OLD} ]; then + cp -a ${OLD} ${NEW}.incoming + cat ${NEW} > ${NEW}.incoming + mv ${NEW}.incoming ${NEW} + fi + config ${NEW} +} + +config etc/cron.daily/exim.new +config etc/logrotate.d/exim.new +preserve_perms etc/rc.d/rc.exim.new + diff --git a/network/exim/exim.Makefile b/network/exim/exim.Makefile new file mode 100644 index 0000000000000..2dccce152c6e3 --- /dev/null +++ b/network/exim/exim.Makefile @@ -0,0 +1,1155 @@ +# $Cambridge: exim/exim-src/src/EDITME,v 1.23 2009/11/20 12:18:19 nm4 Exp $ + +################################################## +# 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. These are +# things that are mostly sysadmin choices. The items below are divided into +# 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 within 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 called +# called OS/Makefile-<osname>. You can further override these by creating files +# called Local/Makefile-<osname>, where "<osname>" stands for the name of 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-<osname>. Any build-time configuration +# 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-dependent +# settings into separate files. (There's more explanation about how this all +# works in the toplevel README file, under "Modifying the building process", as +# well as in the Exim specification.) + +# One OS-specific thing that may need to be changed is the command for running +# the C compiler; the overall default is gcc, but some OS Makefiles specify cc. +# You can override anything that is set by putting CC=whatever 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 easier +# for you when the next release comes along. + +# The location of the X11 libraries is something else that is quite variable +# even between different versions of the same operating 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). You need not worry about X11 unless you want to +# compile the Exim monitor utility. Exim itself does not use X11. + +# Another area of variability between systems is the type and location of the +# DBM library package. Exim has support for ndbm, gdbm, tdb, and Berkeley DB. +# By default the code 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 (obsolete +# 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 selected +# 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, for +# example +# +# EXIM_GID=42 # the "mail" group +# +# However, with some versions of "make" this works only if there is no white +# 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. +############################################################################### + + + +############################################################################### +# THESE ARE THINGS YOU MUST SPECIFY # +############################################################################### + +# 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 number. + +# If you don't specify SPOOL_DIRECTORY, Exim won't fail to build. However, 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 known +# 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. There 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 directory, +# and any superior directories, if they do not exist. + +BIN_DIRECTORY=/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 of +# location in different OS, and in the preferences of different sysadmins. 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 installation +# 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 this +# file does not exist. + +CONFIGURE_FILE=/etc/exim/exim.conf + +# It is possible to specify a colon-separated list of files for CONFIGURE_FILE. +# In this case, Exim will use the first of them that exists when it is run. +# However, if a list is specified, the installation script no longer tries to +# make superior directories or to install a default runtime configuration. + + +#------------------------------------------------------------------------------ +# The Exim binary must normally be setuid root, so that it starts executing as +# root, but (depending on the options with which it is called) it does not +# always need to retain the root privilege. These settings define the user and +# group that is used for Exim processes when they no longer need to be root. 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 very strongly +# discouraged. + +EXIM_USER=exim + +# If you specify EXIM_USER as a name, this is looked up at build time, and the +# uid number is built into the binary. However, you can specify that this +# 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=ref: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 reference". +# 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 systems +# where the name may refer to different uids. It also allows you to build Exim +# on a system where there is no Exim user defined. + +# If the setting of EXIM_USER is numeric (e.g. EXIM_USER=42), there must +# also be a setting of EXIM_GROUP. If, on the other hand, you use a name +# for EXIM_USER (e.g. EXIM_USER=exim), you don't need to set EXIM_GROUP unless +# you want to use a group other than the default group for the given user. + +EXIM_GROUP=exim + +# Many sites define a user called "exim", with an appropriate default group, +# and use +# +# EXIM_USER=exim +# +# 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, though +# it is possible to leave this till the run time configuration. + +# Exim creates the spool directory if it does not exist. The owner and group +# will be those defined by EXIM_USER and EXIM_GROUP, and this also applies to +# all the files and directories that are created in the spool directory. + +# Almost all installations choose this: + +SPOOL_DIRECTORY=/var/spool/exim + + + +############################################################################### +# THESE ARE THINGS YOU PROBABLY WANT TO SPECIFY # +############################################################################### + +# If you need extra header file search paths on all compiles, put the -I +# options in INCLUDE. If you want the extra searches only for certain +# parts of the build, see more specific xxx_INCLUDE variables below. + +# INCLUDE=-I/example/include + +# You need to specify some routers and transports if you want the Exim that you +# are building to be capable of delivering mail. You almost certainly need at +# least one type of lookup. You should consider whether you want to build +# 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 automatically. +# 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=yes +ROUTER_DNSLOOKUP=yes +ROUTER_IPLITERAL=yes +ROUTER_MANUALROUTE=yes +ROUTER_QUERYPROGRAM=yes +ROUTER_REDIRECT=yes + +# This one is very special-purpose, so is not included by default. + +# ROUTER_IPLOOKUP=yes + + +#------------------------------------------------------------------------------ +# These settings determine which individual transport drivers are included in +# the Exim binary. There are no defaults; those transports that are wanted 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 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. + +TRANSPORT_APPENDFILE=yes +TRANSPORT_AUTOREPLY=yes +TRANSPORT_PIPE=yes +TRANSPORT_SMTP=yes + +# This one is special-purpose, and commonly not required, so it is not +# included by default. + +# TRANSPORT_LMTP=yes + + +#------------------------------------------------------------------------------ +# The appendfile transport can write messages to local mailboxes in a number +# 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=yes +SUPPORT_MAILSTORE=yes +SUPPORT_MBX=yes + + +#------------------------------------------------------------------------------ +# These settings determine which file and database lookup methods are included +# in the binary. See the manual chapter entitled "File and database lookups" +# for discussion. DBM and lsearch (linear search) are included by default. 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. It is +# for the specialist case of using the DNS as a general database facility (not +# common). + +LOOKUP_DBM=yes +LOOKUP_LSEARCH=yes +LOOKUP_DNSDB=yes + +# LOOKUP_CDB=yes +LOOKUP_DSEARCH=yes +# LOOKUP_IBASE=yes +LOOKUP_LDAP=yes +LOOKUP_MYSQL=yes +# LOOKUP_NIS=yes +# LOOKUP_NISPLUS=yes +# LOOKUP_ORACLE=yes +LOOKUP_PASSWD=yes +# LOOKUP_PGSQL=yes +LOOKUP_SQLITE=yes +# LOOKUP_WHOSON=yes + +# 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=yes +# LOOKUP_NWILDLSEARCH=yes + + +#------------------------------------------------------------------------------ +# If you have set LOOKUP_LDAP=yes, you should set LDAP_LIB_TYPE to indicate +# which LDAP library you have. Unfortunately, though most of their functions +# 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 that comes +# with Solaris 7 onwards. Uncomment whichever of these you are using. + +# LDAP_LIB_TYPE=OPENLDAP1 +LDAP_LIB_TYPE=OPENLDAP2 +# LDAP_LIB_TYPE=NETSCAPE +# LDAP_LIB_TYPE=SOLARIS + +# 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. There is no longer an embedded +# 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. If 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=-lpcre + + +#------------------------------------------------------------------------------ +# Additional libraries and include directories may be required for some +# lookup styles (e.g. LDAP, MYSQL or PGSQL). LOOKUP_LIBS is included only on +# the command for linking Exim itself, not on any auxiliary programs. You +# don't need to set LOOKUP_INCLUDE if the relevant directories are already +# specified in INCLUDE. The settings below are just examples; -lpq is for +# PostgreSQL, -lgds is for Interbase, -lsqlite3 is for SQLite. + +LOOKUP_INCLUDE=-I/usr/include/mysql +LOOKUP_LIBS=-L/usr/lib$(LIBDIRSUFFIX)/mysql -lldap -lmysqlclient -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 include +# files are defaulted in the OS/Makefile-Default file, but can be overridden in +# local OS-specific make files. + +EXIM_MONITOR=eximon.bin + + +#------------------------------------------------------------------------------ +# Compiling Exim with content scanning support: If you want to compile Exim +# 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 DATA ACL, +# and the MIME ACL. Please read the documentation to learn more about these +# features. + +WITH_CONTENT_SCAN=yes + +# 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=yes + +#------------------------------------------------------------------------------ +# Compiling Exim with experimental features. These are documented in +# experimental-spec.txt. "Experimental" means that the way these features are +# implemented may still change. Backward compatibility is not guaranteed. + +# Uncomment the following lines to add SPF support. You need to have libspf2 +# installed on your system (www.libspf2.org). Depending on where it is installed +# you may have to edit the CFLAGS and LDFLAGS lines. + +# EXPERIMENTAL_SPF=yes +# CFLAGS += -I/usr/local/include +# LDFLAGS += -lspf2 + +# Uncomment the following lines to add SRS (Sender rewriting scheme) support. +# 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=yes +# CFLAGS += -I/usr/local/include +# LDFLAGS += -lsrs_alt + +# Uncomment the following lines to add Brightmail AntiSpam support. You need +# to have the Brightmail client SDK installed. Please check the experimental +# documentation for implementation details. You need to edit the CFLAGS and +# LDFLAGS lines. + +# EXPERIMENTAL_BRIGHTMAIL=yes +# CFLAGS += -I/opt/brightmail/bsdk-6.0/include +# LDFLAGS += -lxml2_single -lbmiclient_single -L/opt/brightmail/bsdk-6.0/lib + + + +############################################################################### +# THESE ARE THINGS YOU MIGHT WANT TO SPECIFY # +############################################################################### + +# The items in this section are those that are commonly changed according to +# the sysadmin's preferences, but whose defaults are often acceptable. The +# first five are concerned with security issues, where differing levels of +# paranoia are appropriate in different environments. Sysadmins also vary 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 that +# cannot be overridden at runtime. This guards against problems caused by +# unauthorized changes to the runtime configuration. You are advised not to +# remove "root" from this option, but you can add other users if you want. The +# list is colon-separated. It must NOT contain any spaces. + +# FIXED_NEVER_USERS=root:bin:daemon +FIXED_NEVER_USERS=root + + +#------------------------------------------------------------------------------ +# By default, Exim insists that its configuration file be owned either by root +# or by the Exim user. You can specify one additional permitted owner here. + +# CONFIGURE_OWNER= + +# If the configuration file is group-writeable, Exim insists by default that it +# is owned by root or the Exim user. You can specify one additional permitted +# group owner here. + +# CONFIGURE_GROUP= + +# If you specify CONFIGURE_OWNER or CONFIGURE_GROUP as a name, this is looked +# 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=ref:mail +# CONFIGURE_GROUP=ref:sysadmin + +# In other words, put "ref:" in front of the user or group name. 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 systems where the names 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 configuration +# file. When this is used by root or the Exim user, root privilege is retained +# by the binary (for any other caller, 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 /dev/null is also +# permitted if the caller is root, because that is used in the install 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 just a directory (the second +# example). + +# ALT_CONFIG_PREFIX=/some/directory/ +# ALT_CONFIG_PREFIX=/some/directory/exim.conf- + + +#------------------------------------------------------------------------------ +# If you uncomment the following line, only root may use the -C or -D options +# without losing root privilege. The -C option specifies an alternate runtime +# configuration file, and the -D option changes macro values in the runtime +# configuration. Uncommenting this line restricts what can be done with these +# options. A call to receive a message (either one-off or via a daemon) cannot +# successfully continue to deliver it, because the re-exec of Exim to regain +# root privilege will fail, owing to the use of -C or -D by the Exim user. +# However, you can still use -C for testing (as root) if you do separate Exim +# calls for receiving a message and subsequently delivering it. + +# ALT_CONFIG_ROOT_ONLY=yes + + +#------------------------------------------------------------------------------ +# Uncommenting this option disables the use of the -D command line option, +# which changes the values of macros in the runtime configuration file. +# This is another protection against somebody breaking into the Exim account. + +# DISABLE_D_OPTION=yes + + +#------------------------------------------------------------------------------ +# Exim has support for the AUTH (authentication) extension of the SMTP +# protocol, as defined by RFC 2554. If you don't know what SMTP authentication +# 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 authentication, +# 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=yes +AUTH_CYRUS_SASL=yes +AUTH_DOVECOT=yes +AUTH_PLAINTEXT=yes +AUTH_SPA=yes + + +#------------------------------------------------------------------------------ +# If you specified AUTH_CYRUS_SASL above, you should ensure that you have the +# Cyrus SASL library installed before trying to build Exim, and you probably +# want to uncomment the following line: + +AUTH_LIBS=-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 to the +# one that is set in the headers_charset option. The default setting is +# defined by this setting: + +HEADERS_CHARSET="ISO-8859-1" + +# If you are going to make use of $header_xxx expansions in your configuration +# 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 might +# 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 is +# installed on your operating system. There are two places in Exim where this +# is relevant: (a) The $header_xxx expansion (see the previous item), and (b) +# the Sieve filter support. For those OS where iconv() is known to be installed +# as standard, the file in OS/Makefile-xxxx contains +# +# HAVE_ICONV=yes +# +# 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 iconv() +# and its header file are not in the default places. You might need to use +# something like this: +# +# HAVE_ICONV=yes +# CFLAGS=-O -I/usr/local/include +# EXTRALIBS_EXIM=-L/usr/local/lib -liconv +# +# but of course there may need to be other things in CFLAGS and EXTRALIBS_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 one +# 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 with +# "{crypt16}". If you want the default handling (without any preceding +# indicator) to use crypt16(), uncomment the following line: + +# DEFAULT_CRYPT=crypt16 + +# If you do that, you can still access the basic crypt() function by preceding +# an encrypted password with "{crypt}". For more details, see the description +# of the "crypteq" condition in the manual chapter on string expansions. + +# Some operating systems do not include a crypt16() function, so Exim has one +# of its own, which it uses unless HAVE_CRYPT16 is defined. Normally, that 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 crypt16() +# 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 different 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 area of +# Exim is seen as very low priority. In practice, if you need to, you can +# define DEFAULT_CRYPT to the name of any function that has the same interface +# as the traditional crypt() function. +# *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING *** + + +#------------------------------------------------------------------------------ +# Exim can be built to support the SMTP STARTTLS command, which implements +# Transport Layer Security using SSL (Secure Sockets Layer). To do this, you +# must install the OpenSSL library package or the GnuTLS library. Exim contains +# 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 about, +# leave these settings commented out. + +# This setting is required for any TLS support (either OpenSSL or GnuTLS) +SUPPORT_TLS=yes + +# Uncomment this setting if you are using OpenSSL +TLS_LIBS=-lssl -lcrypto + +# Uncomment these settings if you are using GnuTLS +# USE_GNUTLS=yes +# TLS_LIBS=-lgnutls -ltasn1 -lgcrypt + +# If you are running Exim as a server, note that just building it with TLS +# 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_advertise_hosts +# to specify the hosts to which Exim advertises TLS support. On the other 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 and +# GnuTLS. The TLS_LIBS settings above assume that the libraries are installed +# with all your other libraries. If they are in a special directory, you may +# need something like + +# TLS_LIBS=-L/usr/local/openssl/lib -lssl -lcrypto +# or +# TLS_LIBS=-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=-I/usr/local/openssl/include/ +# or +# TLS_INCLUDE=-I/opt/gnu/include + +# You don't need to set TLS_INCLUDE if the relevant directories are already +# 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 install +# the documentation in "info" format, first fetch the Texinfo documentation +# sources from the ftp directory and unpack them, which should create files +# with the extension "texinfo" in the doc directory. You may find that the +# 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 after you +# have unpacked them. Then set INFO_DIRECTORY to the location of your info +# 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=/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 directory +# called "log" inside its spool directory (see SPOOL_DIRECTORY above) and uses +# the filenames "mainlog", "paniclog", and "rejectlog". If you want to change +# this, you can set LOG_FILE_PATH to a path name containing one occurrence of +# %s. This will be replaced by one of the strings "main", "panic", or "reject" +# to form the final file names. Some installations may want something like this: + +LOG_FILE_PATH=/var/log/exim/%s.log + +# 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. The Exim user (see EXIM_USER above) +# must be able to create and update files in the directory you have specified. + +# You can also configure Exim to use syslog, instead of or as well as log +# files, by settings such as these + +# LOG_FILE_PATH=syslog +# LOG_FILE_PATH=syslog:/var/log/exim_%slog + +# The first of these uses only syslog; the second uses syslog and also writes +# to log files. Do not include white space in such a setting as it messes up +# the building process. + + +#------------------------------------------------------------------------------ +# When logging to syslog, the following option caters for syslog replacements +# that are able to accept log entries longer than the 1024 characters allowed +# by RFC 3164. It is up to you to make sure your syslog daemon can handle this. +# Non-printable characters are usually unacceptable regardless, so log entries +# are still split on newline characters. + +# SYSLOG_LONG_LINES=yes + +# 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=yes + + +#------------------------------------------------------------------------------ +# 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 log +# files, you can use them instead. The exicyclog script isn't run by default; +# you have to set up a cron job for it if you want it. + +EXICYCLOG_MAX=10 + + +#------------------------------------------------------------------------------ +# 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 + + +#------------------------------------------------------------------------------ +# If the exigrep utility is fed compressed log files, it tries to uncompress +# them using this command. + +ZCAT_COMMAND=/usr/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 embedded +# Perl costs quite a lot of resources. Only do this if you really need it. + +# EXIM_PERL=perl.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=yes +EXTRALIBS += -ldl + + +#------------------------------------------------------------------------------ +# Exim has support for PAM (Pluggable Authentication Modules), a facility +# which is available in the latest releases of Solaris and in some GNU/Linux +# distributions (see http://ftp.kernel.org/pub/linux/libs/pam/). The Exim +# support, which is intended for use in conjunction with the SMTP AUTH +# facilities, is included only when requested by the following setting: + +# SUPPORT_PAM=yes + +# 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 support, +# 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=/etc/radiusclient/radiusclient.conf +# RADIUS_CONFIG_FILE=/etc/radius.conf + +# If you have set RADIUS_CONFIG_FILE, you should also set one of these to +# indicate which RADIUS library is used: + +RADIUS_LIB_TYPE=RADIUSCLIENT +# RADIUS_LIB_TYPE=RADIUSCLIENTNEW +# RADIUS_LIB_TYPE=RADLIB + +# RADIUSCLIENT is the radiusclient library; you probably need to add +# -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 clients +# 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 +# called radlib.h); you probably need to add -lradius to EXTRALIBS. +# +# If you do not set RADIUS_LIB_TYPE, Exim assumes the radiusclient library, +# using the original API. + +EXTRALIBS += -lradiusclient + + +#------------------------------------------------------------------------------ +# Support for authentication via the Cyrus SASL pwcheck daemon is available. +# 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 requested 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 sources, +# 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 installed +# pwcheck, you should arrange for it to be started by root at boot time. + +# CYRUS_PWCHECK_SOCKET=/var/pwcheck/pwcheck + + +#------------------------------------------------------------------------------ +# Support for authentication via the Cyrus SASL saslauthd daemon is available. +# The Exim support, which is intented for use in conjunction with the SMTP 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 example, to +# select or deselect authentication mechanisms), cd to the saslauthd directory +# within the sources, make and make install. You must create the socket +# directory (default /var/state/saslauthd) and chown it to exim's user and +# group. Once you have installed saslauthd, you should arrange for it to be +# started by root at boot time. + +CYRUS_SASLAUTHD_SOCKET=/var/state/saslauthd/mux + + +#------------------------------------------------------------------------------ +# TCP wrappers: If you want to use tcpwrappers from within Exim, uncomment +# this setting. See the manual section entitled "Use of tcpwrappers" in the +# chapter on building and installing Exim. +# +# USE_TCP_WRAPPERS=yes +# +# You may well also have to specify a local "include" file and an additional +# library for TCP wrappers, so you probably need something like this: +# +# USE_TCP_WRAPPERS=yes +# CFLAGS=-O -I/usr/local/include +# EXTRALIBS_EXIM=-L/usr/local/lib -lwrap +# +# but of course there may need to be other things in CFLAGS and EXTRALIBS_EXIM +# as well. + + +#------------------------------------------------------------------------------ +# 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 reference it, +# moving the symbolic link from any previous version. If you define NO_SYMLINK +# (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=yes + + +#------------------------------------------------------------------------------ +# Another default action of the install script is to install a default runtime +# configuration file if one does not exist. This configuration has a router for +# expanding system aliases. The default assumes that these aliases are kept +# in the traditional file called /etc/aliases. If such a file does not exist, +# the installation script creates one that contains just comments (no actual +# aliases). The following setting can be changed to specify a different +# location for the system alias file. + +SYSTEM_ALIASES_FILE=/etc/exim/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 lines +# are read using the standard fgets() function. This does not support line +# editing during interactive input (though the terminal's "erase" character +# works as normal). If your operating system has the readline() function, and +# in addition supports dynamic loading of library functions, you can cause +# Exim to use readline() for the -be testing option (only) by uncommenting the +# following setting. Dynamic loading is used so that the library is loaded 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 user. 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_READLINE +# is "yes", as well as supporting line editing, a history of input lines in the +# current run is maintained. + +USE_READLINE=yes + +# You may need to add -ldl to EXTRALIBS when you set USE_READLINE=yes. +# Note that this option adds to the size of the Exim binary, because the +# dynamic loading library is not otherwise included. + + + + +############################################################################### +# THINGS YOU ALMOST NEVER NEED TO MENTION # +############################################################################### + +# The settings in this section are available for use in special circumstances. +# In the vast majority of installations you need not change anything below. + + +#------------------------------------------------------------------------------ +# The following commands live in different places in some OS. Either the +# ultimate default settings, or the OS-specific files should already point to +# the right place, but they can be overridden here if necessary. These settings +# are used when building various scripts to ensure that the correct paths are +# used when the scripts are run. They are not used in the Makefile itself. 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 you +# haven't got Perl, Exim will still build and run; you just won't be able to +# use those utilities. + +# CHOWN_COMMAND=/usr/bin/chown +# CHGRP_COMMAND=/usr/bin/chgrp +# CHMOD_COMMAND=/usr/bin/chmod +# MV_COMMAND=/bin/mv +# RM_COMMAND=/bin/rm +# TOUCH_COMMAND=/usr/bin/touch +# 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". +# Only in rare circumstances should you need to change this. + +# AR=ar cq + + +#------------------------------------------------------------------------------ +# In some operating systems, the value of the TMPDIR environment variable +# 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 temporary +# 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 setting +# suppresses the check altogether. + +TMPDIR="/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 just +# fine, and in any case, you can change particular instances of the transport +# at run time if you want. + +# APPENDFILE_MODE=0600 +# APPENDFILE_DIRECTORY_MODE=0700 +# APPENDFILE_LOCKFILE_MODE=0600 + + +#------------------------------------------------------------------------------ +# 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 buffers: These specify the sizes (in bytes) of +# 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=8192 +# DELIVER_OUT_BUFFER_SIZE=8192 + + +#------------------------------------------------------------------------------ +# 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. + +# EXIMDB_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. + +# EXIMDB_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. + +# EXIMDB_LOCKFILE_MODE=0640 + + +#------------------------------------------------------------------------------ +# This parameter sets the maximum length of the header portion of a message +# 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 your 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="(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 mode +# which can be defined here (default 0750). + +# INPUT_DIRECTORY_MODE=0750 + + +#------------------------------------------------------------------------------ +# The mode of Exim's log directory, when it is created by Exim inside the spool +# directory, defaults to 0750 but can be changed here. + +# LOG_DIRECTORY_MODE=0750 + + +#------------------------------------------------------------------------------ +# The log files themselves are created as required, with a mode that defaults +# to 0640, but which can be changed here. + +# LOG_MODE=0640 + + +#------------------------------------------------------------------------------ +# 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 + + +#------------------------------------------------------------------------------ +# /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 uncommenting +# this line and specifying another shell, but note that a Bourne-compatible +# shell is expected. + +# MAKE_SHELL=/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=16 + + +#------------------------------------------------------------------------------ +# Network interfaces: Unless you set the local_interfaces option in the runtime +# configuration file to restrict Exim to certain interfaces only, it will 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 hold +# 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 many +# virtual interfaces running on the same hardware. If you have more than 250 +# virtual interfaces, you will need to uncomment this setting and increase the +# value. + +# MAXINTERFACES=250 + + +#------------------------------------------------------------------------------ +# 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 + + +#------------------------------------------------------------------------------ +# There are three options which are used when compiling the Perl interface and +# when linking with Perl. The default values for these are placed automatically +# 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= +# PERL_CCOPTS= +# PERL_LIBS= + + +#------------------------------------------------------------------------------ +# Identifying the daemon: When an Exim daemon starts up, it writes its pid +# (process id) to a file so that it can easily be identified. The path of the +# file can be specified here. Some installations may want something like this: + +PID_FILE_PATH=/var/run/exim.pid + +# If PID_FILE_PATH is not defined, Exim writes a file in its spool directory +# using the name "exim-daemon.pid". + +# If you start up a daemon without the -bd option (for example, with just +# the -q15m option), a pid file is not written. Also, if you override the +# configuration file with the -oX option, no pid file is written. In other +# 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=0750 + + +#------------------------------------------------------------------------------ +# The mode of files on the input spool which hold the contents of messages can +# be changed here. The default is 0640 so that information from the spool is +# available to anyone who is a member of the Exim group. + +# SPOOL_MODE=0640 + + +#------------------------------------------------------------------------------ +# Moving frozen messages: If the following is uncommented, Exim is compiled +# 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. Such +# messages become "invisible" to the normal management tools. + +# SUPPORT_MOVE_FROZEN_MESSAGES=yes + + +#------------------------------------------------------------------------------ +# Disabling the use of fsync(): DO NOT UNCOMMENT THE FOLLOWING LINE unless you +# really, really, really know what you are doing. And even then, think again. +# You should never uncomment this when compiling a binary for distribution. +# 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, crashes +# and hardware problems such as power outages can cause data to be lost. This +# feature should only be used in very exceptional circumstances. YOU HAVE BEEN +# WARNED. + +ENABLE_DISABLE_FSYNC=yes + +# End of EDITME for Exim 4. diff --git a/network/exim/exim.SlackBuild b/network/exim/exim.SlackBuild new file mode 100755 index 0000000000000..94d496e28eb94 --- /dev/null +++ b/network/exim/exim.SlackBuild @@ -0,0 +1,116 @@ +#!/bin/sh + +# Slackware build script for Exim + +# Written by Thomas Morper <thomas@beingboiled.info> +# Thanks to Thales A. Tsailas <ttsailas@enforcingit.com> and the SBo team +# for the previous version and the accompanying files. +# Thanks to Debian for the manpages. + +PRGNAM=exim +VERSION=${VERSION:-4.71} +ARCH=${ARCH:-i486} +BUILD=${BUILD:-1} +TAG=${TAG:-_SBo} + +CWD=$(pwd) +TMP=${TMP:-/tmp/SBo} +PKG=$TMP/package-$PRGNAM +OUTPUT=${OUTPUT:-/tmp} + +if [ "$ARCH" = "i486" ]; then + SLKCFLAGS="-O2 -march=i486 -mtune=i686" + LIBDIRSUFFIX="" +elif [ "$ARCH" = "i686" ]; then + SLKCFLAGS="-O2 -march=i686 -mtune=i686" + LIBDIRSUFFIX="" +elif [ "$ARCH" = "x86_64" ]; then + SLKCFLAGS="-O2 -fPIC" + LIBDIRSUFFIX="64" +else + SLKCFLAGS="-O2" + LIBDIRSUFFIX="" +fi + +set -e + +# Check if the exim user and group exist. If not, then bail. +if [ "$(id -g exim 2> /dev/null)" != "222" -o "$(id -u exim 2> /dev/null)" != "222" ]; then + echo " You must have an 'exim' user and group to run this script." + echo " # groupadd -g 222 exim" + echo " # useradd -d /var/spool/exim -g exim -s /bin/false -u 222 exim" + exit 1 +fi + +rm -rf $PKG +mkdir -p $TMP $PKG $OUTPUT +cd $TMP +rm -rf $PRGNAM-$VERSION +tar xvf $CWD/$PRGNAM-$VERSION.tar.bz2 +cd $PRGNAM-$VERSION +chown -R root:root . +find . \ + \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ + -exec chmod 755 {} \; -o \ + \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ + -exec chmod 644 {} \; + +cat $CWD/exim.Makefile > Local/Makefile +cat exim_monitor/EDITME > Local/eximon.conf + +make \ + CFLAGS="$SLKCFLAGS -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE" \ + LIBDIRSUFFIX=$LIBDIRSUFFIX +make install DESTDIR=$PKG + +find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \ + | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true + +# Ditch the symlink and move the binary to its final destination. +rm -f $PKG/usr/sbin/exim +mv $PKG/usr/sbin/exim-$VERSION-1 $PKG/usr/sbin/exim + +# Additional symlinks provide compatibility with sendmail +mkdir -p $PKG/usr/lib # no LIBDIRSUFFIX here! +( cd $PKG/usr/lib; ln -s /usr/sbin/exim sendmail ) +( cd $PKG/usr/sbin; ln -s /usr/sbin/exim sendmail ) + +# Nobody should use an unedited default config. +mv $PKG/etc/exim/exim.conf $PKG/etc/exim/exim.conf.example +mv $PKG/etc/exim/aliases $PKG/etc/exim/aliases.example + +# Install accompanying scripts and configs. +mkdir -p $PKG/etc/{cron.daily,logrotate.d,rc.d} +install -m 0755 $CWD/contrib/rc.exim.new $PKG/etc/rc.d/rc.exim.new +install -m 0755 $CWD/contrib/exim.cron $PKG/etc/cron.daily/exim.new +install -m 0644 $CWD/contrib/exim.logrotate $PKG/etc/logrotate.d/exim.new + +# Prepare log- and spool-directories. +mkdir -p $PKG/var/log/exim +mkdir -p -m 0750 $PKG/var/spool/exim/ +mkdir -p -m 0750 $PKG/var/spool/exim/{db,input,msglog} +chown -R exim.exim $PKG/var/{log,spool}/exim + +# Install the various manpages +mkdir -p $PKG/usr/man/man8 +mv doc/exim.8 $PKG/usr/man/man8/ +install -m 0644 $CWD/manpages/*.8 $PKG/usr/man/man8/ +find $PKG/usr/man/man8 -type f -exec gzip -9 {} \; +( cd $PKG/usr/man/man8 + ln -s exim_db.8.gz exim_dumpdb.8.gz + ln -s exim_db.8.gz exim_fixdb.8.gz + ln -s exim_db.8.gz exim_tidydb.8.gz +) + +mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION +cp -a \ + ABOUT ACKNOWLEDGMENTS CHANGES LICENCE NOTICE README* doc \ + $PKG/usr/doc/$PRGNAM-$VERSION +cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild + +mkdir -p $PKG/install +cat $CWD/slack-desc > $PKG/install/slack-desc +cat $CWD/doinst.sh > $PKG/install/doinst.sh + +cd $PKG +/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} diff --git a/network/exim/exim.info b/network/exim/exim.info new file mode 100644 index 0000000000000..325ae13e037a8 --- /dev/null +++ b/network/exim/exim.info @@ -0,0 +1,10 @@ +PRGNAM="exim" +VERSION="4.71" +HOMEPAGE="http://www.exim.org/" +DOWNLOAD="ftp://ftp.exim.org/pub/exim/exim4/exim-4.71.tar.bz2" +MD5SUM="f9c5a2d94b5bb132d06e2fff85bef75e" +DOWNLOAD_x86_64="" +MD5SUM_x86_64="" +MAINTAINER="Thomas Morper" +EMAIL="thomas@beingboiled.info" +APPROVED="rworkman" diff --git a/network/exim/manpages/exicyclog.8 b/network/exim/manpages/exicyclog.8 new file mode 100644 index 0000000000000..ec89d1aca839d --- /dev/null +++ b/network/exim/manpages/exicyclog.8 @@ -0,0 +1,74 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXICYCLOG 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +exicyclog \- Cycle exim's logfiles +.SH SYNOPSIS +.B eximcyclog +.SH DESCRIPTION +The +.B exicyclog +script can be used to cycle (rotate) +.I mainlog +and +.I rejectlog +files. +This is not necessary if only syslog is being used. +Some operating systems have their own standard mechanisms for log cycling, +and these can be used instead of +.B exicyclog +if preferred. + +Each time +.B exicyclog +is run the file names get \(oqshuffled down\(cq by one. +If the main log file name is mainlog (the default) then when +.B exicyclog +is run mainlog becomes mainlog.01, the previous mainlog.01 becomes mainlog.02 +and so on, up to a limit which is set in the script, and which defaults to 10. +Reject logs are handled similarly. + +If no mainlog file exists, the script does nothing. +Files that \(oqdrop off\(cq the end are deleted. +All files with numbers greater than 01 are compressed, using a compression +command which is configured by the COMPRESS_COMMAND setting in +Local/Makefile. +It is usual to run \(lqexicyclog\(rq daily from a root \(lqcrontab\(rq entry +of the form + + 1 0 * * * su exim \-c /usr/exim/bin/exicyclog + +assuming you have used the name \(oqexim\(cq for the Exim user. +You can run +.B exicyclog +as root if you wish, but there is no need. + + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8) + +.SH AUTHOR +This manual page was stitched together from spec.txt by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/manpages/exigrep.8 b/network/exim/manpages/exigrep.8 new file mode 100644 index 0000000000000..7da4816c423bb --- /dev/null +++ b/network/exim/manpages/exigrep.8 @@ -0,0 +1,69 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXIGREP 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +EXIGREP \- Search Exim's main log +.SH SYNOPSIS +.B exigrep +.I [\-l] pattern [log file] ... + +.SH DESCRIPTION +The +.B exigrep +utility is a Perl script that searches one or more main log files for +entries that match a given pattern. +When it finds a match, it extracts all the log entries for the relevant +message, not just those that match the pattern. +Thus, +.B exigrep +can extract complete log entries for a given message, or all mail for a given +user, or for a given host, for example. + +The +.I \-l +flag means \(oqliteral\(cq, that is, treat all characters in the pattern as +standing for themselves. +Otherwise the pattern must be a Perl regular expression. +The pattern match is case-insensitive. +If no file names are given on the command line, the standard input is +read. + +If the location of a +.B zcat +command is known from the definition of ZCAT_COMMAND in Local/Makefile, +.B exigrep +automatically passes any file whose +name ends in COMPRESS_SUFFIX through +.B zcat +as it searches it. + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8), +.BR perlre (1) + + +.SH AUTHOR +This manual page was stitched together from spec.txt by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/manpages/exim_checkaccess.8 b/network/exim/manpages/exim_checkaccess.8 new file mode 100644 index 0000000000000..112d562ae6efb --- /dev/null +++ b/network/exim/manpages/exim_checkaccess.8 @@ -0,0 +1,79 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXIM_CHECKACCESS 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +exim_checkaccess \- Check address acceptance from given IP +.SH SYNOPSIS +.B exim_checkaccess +.I IP-address email@address [more Exim options] + +.SH DESCRIPTION +.B Exim's +.I \-bh +command line argument allows you to run a fake SMTP session with debugging +output, in order to check what Exim is doing when it is applying policy +controls to incoming SMTP mail. +However, not everybody is sufficiently familiar with the SMTP protocol to +be able to make full use of \-bh, and sometimes you just want to answer the +question \(lqDoes this address have access?\(rq without bothering with any +further details. + +The +.B exim_checkaccess +utility is a \(oqpackaged\(cq version of +.I \-bh. +It takes two arguments, an IP address and an email address: + + exim_checkaccess 10.9.8.7 A.User@a.domain.example + +The utility runs a call to +.B Exim +with the \-bh option, to test whether the given email address would be +accepted in a RCPT command in a TCP/IP connection from the host with the +given IP address. +The output of the utility is either the word \(oqaccepted\(cq, or the SMTP error +response, for example: + + Rejected: + 550 Relay not permitted + +When running this test, the utility uses \(lq<>\(rq as the envelope sender +address for the MAIL command, but you can change this by providing additional +options. These are passed directly to the Exim command. +For example, to specify that the test is to be run with the sender address +\(lqhimself@there.example\(rq you can use: + + exim_checkaccess 10.9.8.7 A.User@a.domain.example \\ + \-f himself@there.example + +Note that these additional Exim command line items must be given after the +two mandatory arguments. + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8) + +.SH AUTHOR +This manual page was stitched together from spec.txt by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/manpages/exim_db.8 b/network/exim/manpages/exim_db.8 new file mode 100644 index 0000000000000..f0ea021dc4073 --- /dev/null +++ b/network/exim/manpages/exim_db.8 @@ -0,0 +1,168 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXIM_DB 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +exim_db \- Manage Exim's hint databases (exim_dumpdb, exim_fixdb, exim_tidydb) +.SH SYNOPSIS +.B exim_dumpdb +.I spooldir database +.br +.B exim_fixdb +.I spooldir database +.br +.B exim_tidydb +.I [\-f] [\-t time] spooldir database + +.SH DESCRIPTION +Three utility programs are provided for maintaining the DBM files that +Exim uses to contain its delivery hint information. +Each program requires two arguments. +The first specifies the name of Exim's spool directory, and the second is +the name of the database it is to operate on. +These are as follows: +.TP +.B retry +the database of retry information +.TP +.B wait\-<transport name> +databases of information about messages waiting for remote hosts +.TP +.B misc +other hints data (for example, for serializing ETRN runs) +.P +The entire contents of a database are written to the standard output by the +.B exim_dumpdb +program, which has no options or arguments other than the spool +and database names. +For example, to dump the retry database: + +.I exim_dumpdb /var/spool/exim retry + +Two lines of output are produced for each entry: +.nf + T:mail.ref.example:192.168.242.242 146 77 Connection refused + 31-Oct-1995 12:00:12 02-Nov-1995 12:21:39 02-Nov-1995 20:21:39 * + +.fi +The first item on the first line is the key of the record. +It starts with one of the letters R, or T, depending on whether it refers +to a routing or transport retry. +For a local delivery, the next part is the local address; for a remote +delivery it is the name of the remote host, followed by its failing IP +address (unless \(lqno_retry_include_ip_address\(rq is set on the smtp +transport). +Then there follows an error code, an additional error code, and a +textual description of the error. + +The three times on the second line are the time of first failure, the time of +the last delivery attempt, and the computed time for the next attempt. +The line ends with an asterisk if the cutoff time for the last retry rule +has been exceeded. + +Each output line from +.B exim_dumpdb +for the +.I wait\-xxx +databases consists of a host name followed by a list of ids for messages +that are or were waiting to be delivered to that host. +If there are a very large number for any one host, continuation records, +with a sequence number added to the host name, may be seen. +The data in these records is often out of date, because a message may be +routed to several alternative hosts, and Exim makes no effort to keep +cross-references. + +The +.B exim_tidydb +utility program is used to tidy up the contents of the hints databases. +If run with no options, it removes all records from a database that are +more than 30 days old. +The cutoff date can be altered by means of the \-t option, which must be +followed by a time. +For example, to remove all records older than a week from the retry +database: + +.I exim_tidydb \-t 7d /var/spool/exim retry + +Both the +.I wait\-xxx +and +.I retry +databases contain items that involve message ids. +In the former these appear as data in records keyed by host - they were +messages that were waiting for that host - and in the latter they are the +keys for retry information for messages that have suffered certain types +of error. +When \(lqexim_tidydb\(rq is run, a check is made to ensure that message ids in +database records are those of messages that are still on the queue. +Message ids for messages that no longer exist are removed from \(lqwait\-\(rqxxx +records, and if this leaves any records empty, they are deleted. +For the \(lqretry\(rq database, records whose keys are non-existent message +ids are removed. +The +.B exim_tidydb +utility outputs comments on the standard output whenever it removes +information from the database. + +Removing records from a DBM file does not normally make the file smaller, but +all the common DBM libraries are able to re-use the space that is released. +It is therefore suggested that +.B exim_tidydb +be run periodically on all the hints databases, but at a quiet time of day, +because it requires a database to be locked (and therefore inaccessible to +Exim) while it does its work. + +The +.B exim_fixdb +program is a utility for interactively modifying databases. +Its main use is for testing Exim, but it might also be occasionally useful +for getting round problems in a live system. +It has no options, and its interface is somewhat crude. +On entry, it prompts for input with a right angle-bracket. +A key of a database record can then be entered, and the data for that +record is displayed. + +If \(oqd\(cq is typed at the next prompt, the entire record is deleted. +For all except the +.I retry +database, that is the only operation that can be carried out. +For the +.I retry +database, each field is output preceded by a number, and data for individual +fields can be changed by typing the field number followed by new data, for +example: + + > 4 951102:1000 + +resets the time of the next delivery attempt. +Time values are given as a sequence of digit pairs for year, month, day, +hour, and minute. +Colons can be used as optional separators. + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8) + +.SH AUTHOR +This manual page was stitched together from spec.txt by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/manpages/exim_dbmbuild.8 b/network/exim/manpages/exim_dbmbuild.8 new file mode 100644 index 0000000000000..7a505ae3bf29e --- /dev/null +++ b/network/exim/manpages/exim_dbmbuild.8 @@ -0,0 +1,104 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXIM_DBMBUILD 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +exim_dbmbuild \- Build a DBM file. +.SH SYNOPSIS +.B exim_dbmbuild +.I [\-nolc] [\-nozero] [\-noduperr] [\-nowarn] inputfile|\- outputfile + +.SH DESCRIPTION +The +.B exim_dbmbuild +program reads an input file containing keys and data in +the format used by the +.I lsearch +lookup (see section 9.1). +It writes a DBM file using the lower-cased alias names as keys and the +remainder of the information as data. +The lower-casing can be prevented by calling the program with the +.I \-nolc +option. + +A terminating zero is included as part of the key string. +This is expected by the dbm lookup type. +However, if the option +.I \-nozero +is given, +.B exim_dbmbuild +creates files without terminating zeroes in either the key strings or the +data strings. +The +.I dbmnz +lookup type can be used with such files. + +The program requires two arguments: the name of the input file (which can +be a single hyphen to indicate the standard input), and the name of the +output file. +It creates the output under a temporary name, and then renames it if all +went well. +If the native DB interface is in use (USE_DB is set in a compile-time +configuration file - this is common in free versions of Unix) the two file +names must be different, because in this mode the Berkeley DB functions +create a single output file using exactly the name given. +For example, + + exim_dbmbuild /etc/aliases /etc/aliases.db + +reads the system alias file and creates a DBM version of it in +/etc/aliases.db. + +In systems that use the +.I ndbm +routines (mostly proprietary versions of Unix), two files are used, with the +suffixes .dir and .pag. +In this environment, the suffixes are added to the second argument of +.B exim_dbmbuild, +so it can be the same as the first. +This is also the case when the Berkeley functions are used in +compatibility mode (though this is not recommended), because in that case +it adds a .db suffix to the file name. + +If a duplicate key is encountered, the program outputs a warning, and when +it finishes, its return code is 1 rather than zero, unless the +.I \-noduperr +option is used. +By default, only the first of a set of duplicates is used - this makes it +compatible with lsearch lookups. +There is an option +.I \-lastdup +which causes it to use the data for the last duplicate instead. +There is also an option +.I \-nowarn, +which stops it listing duplicate keys to \(lqstderr\(rq. +For other errors, where it doesn't actually make a new file, the return +code is 2. + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8) + +.SH AUTHOR +This manual page was stitched together from spec.txt by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/manpages/exim_lock.8 b/network/exim/manpages/exim_lock.8 new file mode 100644 index 0000000000000..18af58e7fec87 --- /dev/null +++ b/network/exim/manpages/exim_lock.8 @@ -0,0 +1,136 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXIM_LOCK 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +exim_lock \- Mailbox maintenance +.SH SYNOPSIS +.B exim_lock +.RI [ options ] mailbox-file + +.SH DESCRIPTION +The +.B exim_lock +utility locks a mailbox file using the same algorithm as Exim. +For a discussion of locking issues, see section 25.2. +.B exim_lock +can be used to prevent any modification of a mailbox by Exim or a user +agent while investigating a problem. +The utility requires the name of the file as its first argument. +If the locking is successful, the second argument is run as a command +(using C's \(lqsystem()\(rq function); if there is no second argument, the value +of the SHELL environment variable is used; if this is unset or empty, +/bin/sh is run. +When the command finishes, the mailbox is unlocked and the utility ends. +The following options are available: +.TP +.I \-fcntl +Use \(lqfcntl()\(rq locking on the open mailbox. +.TP +.I \-interval +This must be followed by a number, which is a number of seconds; it +sets the interval to sleep between retries (default 3). +.TP +.I \-lockfile +Create a lock file before opening the mailbox. +.TP +.I \-mbx +Lock the mailbox using MBX rules. +.TP +.I \-q +Suppress verification output. +.TP +.I \-retries +This must be followed by a number; it sets the number of times to try +to get the lock (default 10). +.TP +.I \-timeout +This must be followed by a number, which is a number of seconds; it +sets a timeout to be used with a blocking \(lqfcntl()\(rq lock. +If it is not set (the default), a non-blocking call is used. +.TP +.I \-v +Generate verbose output. + +If none of +.I \-fcntl, \-lockfile +or +.I \-mbx +are given, the default is to create a lock file and also use \(lqfcntl()\(rq locking +on the mailbox, which is the same as +.B Exim's +default. +The use of +.I \-fcntl +requires that the file be writable; the use +of +.I \-lockfile +requires that the directory containing the file be writable. +Locking by lock file does not last for ever; Exim assumes that a lock file +is expired if it is more than 30 minutes old. + +The +.I \-mbx +option is mutually exclusive with +.I \-fcntl. +It causes a shared lock to be taken out on the open mailbox, and an +exclusive lock on the file /tmp/.n.m where n and m are the device number +and inode number of the mailbox file. +When the locking is released, if an exclusive lock can be obtained for the +mailbox, the file in /tmp is deleted. + +The default output contains verification of the locking that takes place. +The +.I \-v +option causes some additional information to be given. +The +.I \-q +option suppresses all output except error messages. +.PP +A command such as + + exim_lock /var/spool/mail/spqr + +runs an interactive shell while the file is locked, whereas + + exim_lock \-q /var/spool/mail/spqr <<End + <some commands> + End + +runs a specific non-interactive sequence of commands while the file is +locked, suppressing all verification output. +A single command can be run by a command such as + + exim_lock \-q /var/spool/mail/spqr \ + "cp /var/spool/mail/spqr /some/where" + +Note that if a command is supplied, it must be entirely contained within +the second argument - hence the quotes. + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8) + +.SH AUTHOR +This manual page was stitched together from spec.txt by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/manpages/eximon.8 b/network/exim/manpages/eximon.8 new file mode 100644 index 0000000000000..83dc74c91a632 --- /dev/null +++ b/network/exim/manpages/eximon.8 @@ -0,0 +1,49 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXIMON 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +eximon \- Monitor Exim +.SH SYNOPSIS +.B eximon + +.SH DESCRIPTION +The Exim monitor is an application which displays in an X window information +about the state of +.B Exim's +queue and what +.B Exim is doing. +An admin user can perform certain operations on messages from this GUI +interface; however all such facilities are also available from the command +line, and indeed, the monitor itself makes use of the command line to +perform any actions requested. + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8). +Eximon is documented extensivly in the +.B specification of the exim mail transfer agent. + +.SH AUTHOR +This manual page was stitched together from spec.txt by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/manpages/exinext.8 b/network/exim/manpages/exinext.8 new file mode 100644 index 0000000000000..25f84d204f6a7 --- /dev/null +++ b/network/exim/manpages/exinext.8 @@ -0,0 +1,72 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXINEXT 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +exinext \- Finding individual retry times +.SH SYNOPSIS +.B exinext +.I address|message-id + +.SH DESCRIPTION +A utility called +.B exinext +(mostly a Perl script) provides the ability to fish specific information +out of the retry database. +Given a mail domain (or a complete address), it looks up the hosts for +that domain, and outputs any retry information for the hosts or for the +domain. +At present, the retry information is obtained by running +.B exim_dumpdb +(see below) and processing the output. +For example: + + exinext piglet@milne.fict.example + kanga.milne.fict.example:192.168.8.1 error 146: Connection refused + first failed: 21-Feb-1996 14:57:34 + last tried: 21-Feb-1996 14:57:34 + next try at: 21-Feb-1996 15:02:34 + roo.milne.fict.example:192.168.8.3 error 146: Connection refused + first failed: 20-Jan-1996 13:12:08 + last tried: 21-Feb-1996 11:42:03 + next try at: 21-Feb-1996 19:42:03 + past final cutoff time + +You can also give +.B exinext +a local part, without a domain, and it will give any retry information for +that local part in your default domain. +A message id can be used to obtain retry information pertaining to a +specific message. +This exists only when an attempt to deliver a message to a remote host +suffers a message-specific error (see section 42.2). +.B exinext +is not particularly efficient, but then it isn't expected to be run very often. + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8) + +.SH AUTHOR +This manual page was stitched together from spec.txt by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/manpages/exiqgrep.8 b/network/exim/manpages/exiqgrep.8 new file mode 100644 index 0000000000000..db35c28b8a5b0 --- /dev/null +++ b/network/exim/manpages/exiqgrep.8 @@ -0,0 +1,86 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXIQGREP 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +exiqgrep \- Search in the exim queue +.SH SYNOPSIS +.B exiqgrep +.I [\-a] [\-c] + +.SH DESCRIPTION +The +.B exiqgrep +utility is a Perl script which offers possibilities to grep in the +exim queue output. Unlike exiqsumm, it invokes exim \-bpu itself and +does not need to be invoked in a pipe. + +.SH OPTIONS +.TP 10 +\fB\-h\fR +Print help +.TP +\fB\-f <regexp>\fR +Match sender address (field is \(lq< >\(rq wrapped) +.TP +\fB\-r <regexp>\fR +Match recipient address +.TP +\fB\-s <regexp>\fR +Match against the site field from long output +.TP +\fB\-y <seconds>\fR +Message younger than +.TP +\fB\-o <seconds>\fR +Message older than +.TP +\fB\-z\fR +Frozen messages only (exclude non-frozen) +.TP +\fB\-x\fR +Non-frozen messages only (exclude frozen) +.TP +\fB\-c\fR +Display match count +.TP +\fB\-l\fR +Long Format [Default] +.TP +\fB\-i\fR +Message IDs only +.TP +\fB\-b\fR +Brief Format +.TP +\fB\-R\fR +Reverse order + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8) + +.SH AUTHOR +This manual page was stitched together from the source code by Marc +Haber <mh+debian\-packages@zugschlus.de>, using the exiqsumm man page by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/manpages/exiqsumm.8 b/network/exim/manpages/exiqsumm.8 new file mode 100644 index 0000000000000..524ded07057fc --- /dev/null +++ b/network/exim/manpages/exiqsumm.8 @@ -0,0 +1,73 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXIQSUMM 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +exiqsumm \- Summarising the queue +.SH SYNOPSIS +.B exiqsumm +.I [\-a] [\-c] + +.SH DESCRIPTION +The +.B exiqsumm +utility is a Perl script which reads the output of +.I exim \-bp +and produces a summary of the messages on the queue. +Thus, you use it by running a command such as + + exim \-bp | exiqsumm + +The output consists of one line for each domain that has messages waiting +for it, as in the following example: + + 3 2322 74m 66m msn.com.example + +This lists the number of messages for the domain, their total volume, and +the length of time that the oldest and the newest messages have been +waiting. +By default the output is sorted on the domain name, but +.B exiqsumm +has the options +.I \-a +and +.I \-c, +which cause the output to be sorted by oldest message and by count of +messages, respectively. + +The output of +.I exim \-bp +contains the original addresses in the message, so this also applies to +the output from +.B exiqsumm. +No domains from addresses generated by aliasing or forwarding are included +(unless the \(lqone_time\(rq option of the redirect router has been used to +convert them into \(oqtop level\(cq addresses). + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8) + +.SH AUTHOR +This manual page was stitched together from spec.txt by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/manpages/exiwhat.8 b/network/exim/manpages/exiwhat.8 new file mode 100644 index 0000000000000..c2c67ffd3352e --- /dev/null +++ b/network/exim/manpages/exiwhat.8 @@ -0,0 +1,101 @@ +.\" Hey, EMACS: -*- nroff -*- +.\" First parameter, NAME, should be all caps +.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection +.\" other parameters are allowed: see man(7), man(1) +.TH EXIWHAT 8 "March 26, 2003" +.\" Please adjust this date whenever revising the manpage. +.\" +.\" Some roff macros, for reference: +.\" .nh disable hyphenation +.\" .hy enable hyphenation +.\" .ad l left justify +.\" .ad b justify to both left and right margins +.\" .nf disable filling +.\" .fi enable filling +.\" .br insert line break +.\" .sp <n> insert n+1 empty lines +.\" for manpage-specific macros, see man(7) +.\" \(oqthis text is enclosed in single quotes\(cq +.\" \(lqthis text is enclosed in double quotes\(rq +.SH NAME +exiwhat \- Finding out what Exim processes are doing +.SH SYNOPSIS +.B exiwhat + +.SH DESCRIPTION +On operating systems that can restart a system call after receiving a +signal (most modern OS), an +.B Exim +process responds to the SIGUSR1 signal by writing a line describing what +it is doing to the file exim\-process.info in the Exim spool directory. +The +.B exiwhat +script sends the signal to all +.B Exim +processes it can find, having first emptied the file. +It then waits for one second to allow the +.B Exim +processes to react before displaying the results. +In order to run +.B exiwhat +successfully you have to have sufficient privilege to send the signal to +the +.B Exim +processes, so it is normally run as root. + +Unfortunately, the +.B ps +command which +.B exiwhat +uses to find +.B Exim +processes varies in different operating systems. +Not only are different options used, but the format of the output is +different. +For this reason, there are some system configuration options that configure +exactly how +.B exiwhat +works. +If it doesn't seem to be working for you, check the following compile-time +options: +.TP +.I EXIWHAT_PS_CMD +the command for running \(lqps\(rq +.TP +.I EXIWHAT_PS_ARG +the argument for \(lqps\(rq +.TP +.I EXIWHAT_EGREP_ARG +the argument for \(lqegrep\(rq to select from \(lqps\(rq output +.TP +.I EXIWHAT_KILL_ARG +the argument for the \(lqkill\(rq command +.PP +An example of typical output from +.B exiwhat +is + +.nf + 164 daemon: -q1h, listening on port 25 +10483 running queue: waiting for 0tAycK-0002ij-00 (10492) +10492 delivering 0tAycK-0002ij-00 to mail.ref.example [10.19.42.42] + (editor@ref.example) +10592 handling incoming call from [192.168.243.242] +10628 accepting a local non-SMTP message +.fi + +The first number in the output line is the process number. +The third line has been split here, in order to fit it on the page. + +.SH BUGS +This manual page needs a major re-work. If somebody knows better groff +than us and has more experience in writing manual pages, any patches +would be greatly appreciated. + +.SH SEE ALSO +.BR exim (8) + +.SH AUTHOR +This manual page was stitched together from spec.txt by +Andreas Metzler <ametzler at downhill.at.eu.org>, +for the Debian GNU/Linux system (but may be used by others). diff --git a/network/exim/slack-desc b/network/exim/slack-desc new file mode 100644 index 0000000000000..2968b7262695f --- /dev/null +++ b/network/exim/slack-desc @@ -0,0 +1,19 @@ +# HOW TO EDIT THIS FILE: +# The "handy ruler" below makes it easier to edit a package description. Line +# up the first '|' above the ':' following the base package name, and the '|' +# on the right side marks the last column you can put a character in. You must +# make exactly 11 lines for the formatting to be correct. It's also +# customary to leave one space after the ':'. + + |-----handy-ruler------------------------------------------------------| +exim: Exim (the Exim mail transfer agent) +exim: +exim: Exim is a mail transfer agent (MTA) used on Unix-like operating +exim: systems. It is freely available under the GNU GPL and it aims to be a +exim: general and flexible mailer with extensive facilities for checking +exim: incoming e-mail. Exim was written by Philip Hazel for use in the +exim: University of Cambridge Computing Service's e-mail systems. +exim: +exim: Homepage: http://www.exim.org/ +exim: +exim: |