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