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