Commit | Line | Data |
---|---|---|
059ec3d9 PH |
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 | |
10385c15 | 132 | # owner of a local mailbox.) Specifying these values as root is not supported. |
059ec3d9 PH |
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 | ||
76ea0716 PH |
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 | ||
059ec3d9 PH |
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 | ||
e6d225ae DW |
249 | #------------------------------------------------------------------------------ |
250 | # See below for dynamic lookup modules. | |
251 | # LOOKUP_MODULE_DIR=/usr/lib/exim/lookups/ | |
6545de78 PP |
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. | |
e6d225ae | 256 | |
0a349494 PP |
257 | # To build a module dynamically, you'll need to define CFLAGS_DYNAMIC for |
258 | # your platform. Eg: | |
259 | # CFLAGS_DYNAMIC=-shared -rdynamic | |
260 | # CFLAGS_DYNAMIC=-shared -rdynamic -fPIC | |
261 | ||
059ec3d9 PH |
262 | #------------------------------------------------------------------------------ |
263 | # These settings determine which file and database lookup methods are included | |
264 | # in the binary. See the manual chapter entitled "File and database lookups" | |
265 | # for discussion. DBM and lsearch (linear search) are included by default. If | |
266 | # you are unsure about the others, leave them commented out for now. | |
267 | # LOOKUP_DNSDB does *not* refer to general mail routing using the DNS. It is | |
268 | # for the specialist case of using the DNS as a general database facility (not | |
269 | # common). | |
e6d225ae DW |
270 | # If set to "2" instead of "yes" then the corresponding lookup will be |
271 | # built as a module and must be installed into LOOKUP_MODULE_DIR. You need to | |
272 | # add -export-dynamic -rdynamic to EXTRALIBS. You may also need to add -ldl to | |
273 | # EXTRALIBS so that dlopen() is available to Exim. You need to define | |
274 | # LOOKUP_MODULE_DIR above so the exim binary actually loads dynamic lookup | |
275 | # modules. | |
276 | # Also, instead of adding all the libraries/includes to LOOKUP_INCLUDE and | |
277 | # LOOKUP_LIBS, add them to the respective LOOKUP_*_INCLUDE and LOOKUP_*_LIBS | |
278 | # (where * is the name as given here in this list). That ensures that only | |
279 | # the dynamic library and not the exim binary will be linked against the | |
280 | # library. | |
281 | # NOTE: LDAP cannot be built as a module! | |
f4b00a2d PP |
282 | # |
283 | # If your system has pkg-config then the _INCLUDE/_LIBS setting can be | |
284 | # handled for you automatically by also defining the _PC variable to reference | |
285 | # the name of the pkg-config package, if such is available. | |
059ec3d9 PH |
286 | |
287 | LOOKUP_DBM=yes | |
288 | LOOKUP_LSEARCH=yes | |
663ee6d9 | 289 | LOOKUP_DNSDB=yes |
059ec3d9 PH |
290 | |
291 | # LOOKUP_CDB=yes | |
059ec3d9 PH |
292 | # LOOKUP_DSEARCH=yes |
293 | # LOOKUP_IBASE=yes | |
294 | # LOOKUP_LDAP=yes | |
295 | # LOOKUP_MYSQL=yes | |
296 | # LOOKUP_NIS=yes | |
297 | # LOOKUP_NISPLUS=yes | |
298 | # LOOKUP_ORACLE=yes | |
299 | # LOOKUP_PASSWD=yes | |
300 | # LOOKUP_PGSQL=yes | |
13b685f9 | 301 | # LOOKUP_SQLITE=yes |
f4b00a2d | 302 | # LOOKUP_SQLITE_PC=sqlite3 |
059ec3d9 PH |
303 | # LOOKUP_WHOSON=yes |
304 | ||
305 | # These two settings are obsolete; all three lookups are compiled when | |
306 | # LOOKUP_LSEARCH is enabled. However, we retain these for backward | |
307 | # compatibility. Setting one forces LOOKUP_LSEARCH if it is not set. | |
308 | ||
309 | # LOOKUP_WILDLSEARCH=yes | |
310 | # LOOKUP_NWILDLSEARCH=yes | |
311 | ||
312 | ||
313 | #------------------------------------------------------------------------------ | |
314 | # If you have set LOOKUP_LDAP=yes, you should set LDAP_LIB_TYPE to indicate | |
315 | # which LDAP library you have. Unfortunately, though most of their functions | |
316 | # are the same, there are minor differences. Currently Exim knows about four | |
317 | # LDAP libraries: the one from the University of Michigan (also known as | |
318 | # OpenLDAP 1), OpenLDAP 2, the Netscape SDK library, and the library that comes | |
319 | # with Solaris 7 onwards. Uncomment whichever of these you are using. | |
320 | ||
321 | # LDAP_LIB_TYPE=OPENLDAP1 | |
322 | # LDAP_LIB_TYPE=OPENLDAP2 | |
323 | # LDAP_LIB_TYPE=NETSCAPE | |
324 | # LDAP_LIB_TYPE=SOLARIS | |
325 | ||
326 | # If you don't set any of these, Exim assumes the original University of | |
327 | # Michigan (OpenLDAP 1) library. | |
328 | ||
329 | ||
8eb9f5bd NM |
330 | #------------------------------------------------------------------------------ |
331 | # The PCRE library is required for exim. There is no longer an embedded | |
332 | # version of the PCRE library included with the source code, instead you | |
333 | # must use a system library or build your own copy of PCRE. | |
334 | # In either case you must specify the library link info here. If the | |
335 | # PCRE header files are not in the standard search path you must also | |
336 | # modify the INCLUDE path (above) | |
337 | # The default setting of PCRE_LIBS should work on the vast majority of | |
338 | # systems | |
339 | ||
340 | PCRE_LIBS=-lpcre | |
341 | ||
342 | ||
059ec3d9 PH |
343 | #------------------------------------------------------------------------------ |
344 | # Additional libraries and include directories may be required for some | |
345 | # lookup styles (e.g. LDAP, MYSQL or PGSQL). LOOKUP_LIBS is included only on | |
346 | # the command for linking Exim itself, not on any auxiliary programs. You | |
347 | # don't need to set LOOKUP_INCLUDE if the relevant directories are already | |
348 | # specified in INCLUDE. The settings below are just examples; -lpq is for | |
2050824c | 349 | # PostgreSQL, -lgds is for Interbase, -lsqlite3 is for SQLite. |
f4b00a2d PP |
350 | # |
351 | # You do not need to use this for any lookup information added via pkg-config. | |
059ec3d9 PH |
352 | |
353 | # LOOKUP_INCLUDE=-I /usr/local/ldap/include -I /usr/local/mysql/include -I /usr/local/pgsql/include | |
2050824c PH |
354 | # LOOKUP_LIBS=-L/usr/local/lib -lldap -llber -lmysqlclient -lpq -lgds -lsqlite3 |
355 | ||
059ec3d9 PH |
356 | |
357 | #------------------------------------------------------------------------------ | |
358 | # Compiling the Exim monitor: If you want to compile the Exim monitor, a | |
359 | # program that requires an X11 display, then EXIM_MONITOR should be set to the | |
360 | # value "eximon.bin". Comment out this setting to disable compilation of the | |
361 | # monitor. The locations of various X11 directories for libraries and include | |
362 | # files are defaulted in the OS/Makefile-Default file, but can be overridden in | |
363 | # local OS-specific make files. | |
364 | ||
365 | EXIM_MONITOR=eximon.bin | |
366 | ||
2050824c | 367 | |
8523533c TK |
368 | #------------------------------------------------------------------------------ |
369 | # Compiling Exim with content scanning support: If you want to compile Exim | |
370 | # with support for message body content scanning, set WITH_CONTENT_SCAN to | |
371 | # the value "yes". This will give you malware and spam scanning in the DATA ACL, | |
372 | # and the MIME ACL. Please read the documentation to learn more about these | |
373 | # features. | |
374 | ||
f7b63901 | 375 | # WITH_CONTENT_SCAN=yes |
8523533c TK |
376 | |
377 | # If you want to use the deprecated "demime" condition in the DATA ACL, | |
378 | # uncomment the line below. Doing so will also explicitly turn on the | |
379 | # WITH_CONTENT_SCAN option. If possible, use the MIME ACL instead of | |
380 | # the "demime" condition. | |
381 | ||
f7b63901 | 382 | # WITH_OLD_DEMIME=yes |
8523533c | 383 | |
8544e77a PP |
384 | # If you're using ClamAV and are backporting fixes to an old version, instead |
385 | # of staying current (which is the more usual approach) then you may need to | |
386 | # use an older API which uses a STREAM command, now deprecated, instead of | |
387 | # zINSTREAM. If you need to set this, please let the Exim developers know, as | |
388 | # if nobody reports a need for it, we'll remove this option and clean up the | |
389 | # code. zINSTREAM was introduced with ClamAV 0.95. | |
390 | # | |
391 | # WITH_OLD_CLAMAV_STREAM=yes | |
392 | ||
a8c8d6b5 JJ |
393 | #------------------------------------------------------------------------------ |
394 | # By default Exim includes code to support DKIM (DomainKeys Identified | |
395 | # Mail, RFC4871) signing and verification. Verification of signatures is | |
396 | # turned on by default. See the spec for information on conditionally | |
397 | # disabling it. To disable the inclusion of the entire feature, set | |
398 | # DISABLE_DKIM to "yes" | |
399 | ||
400 | # DISABLE_DKIM=yes | |
401 | ||
402 | ||
8523533c TK |
403 | #------------------------------------------------------------------------------ |
404 | # Compiling Exim with experimental features. These are documented in | |
405 | # experimental-spec.txt. "Experimental" means that the way these features are | |
f7b63901 | 406 | # implemented may still change. Backward compatibility is not guaranteed. |
8523533c TK |
407 | |
408 | # Uncomment the following lines to add SPF support. You need to have libspf2 | |
409 | # installed on your system (www.libspf2.org). Depending on where it is installed | |
410 | # you may have to edit the CFLAGS and LDFLAGS lines. | |
8523533c | 411 | |
f7b63901 PH |
412 | # EXPERIMENTAL_SPF=yes |
413 | # CFLAGS += -I/usr/local/include | |
414 | # LDFLAGS += -lspf2 | |
415 | ||
416 | # Uncomment the following lines to add SRS (Sender rewriting scheme) support. | |
8523533c TK |
417 | # You need to have libsrs_alt installed on your system (srs.mirtol.com). |
418 | # Depending on where it is installed you may have to edit the CFLAGS and | |
419 | # LDFLAGS lines. | |
8523533c | 420 | |
f7b63901 PH |
421 | # EXPERIMENTAL_SRS=yes |
422 | # CFLAGS += -I/usr/local/include | |
423 | # LDFLAGS += -lsrs_alt | |
424 | ||
425 | # Uncomment the following lines to add Brightmail AntiSpam support. You need | |
8523533c TK |
426 | # to have the Brightmail client SDK installed. Please check the experimental |
427 | # documentation for implementation details. You need to edit the CFLAGS and | |
428 | # LDFLAGS lines. | |
f7b63901 PH |
429 | |
430 | # EXPERIMENTAL_BRIGHTMAIL=yes | |
431 | # CFLAGS += -I/opt/brightmail/bsdk-6.0/include | |
12cdb9e7 | 432 | # LDFLAGS += -lxml2_single -lbmiclient_single -L/opt/brightmail/bsdk-6.0/lib |
8523533c | 433 | |
059ec3d9 PH |
434 | |
435 | ||
436 | ############################################################################### | |
437 | # THESE ARE THINGS YOU MIGHT WANT TO SPECIFY # | |
438 | ############################################################################### | |
439 | ||
440 | # The items in this section are those that are commonly changed according to | |
441 | # the sysadmin's preferences, but whose defaults are often acceptable. The | |
442 | # first five are concerned with security issues, where differing levels of | |
443 | # paranoia are appropriate in different environments. Sysadmins also vary in | |
444 | # their views on appropriate levels of defence in these areas. If you do not | |
445 | # understand these issues, go with the defaults, which are used by many sites. | |
446 | ||
447 | ||
448 | #------------------------------------------------------------------------------ | |
449 | # Although Exim is normally a setuid program, owned by root, it refuses to run | |
450 | # local deliveries as root by default. There is a runtime option called | |
451 | # "never_users" which lists the users that must never be used for local | |
452 | # deliveries. There is also the setting below, which provides a list that | |
453 | # cannot be overridden at runtime. This guards against problems caused by | |
454 | # unauthorized changes to the runtime configuration. You are advised not to | |
455 | # remove "root" from this option, but you can add other users if you want. The | |
926e1192 | 456 | # list is colon-separated. It must NOT contain any spaces. |
059ec3d9 | 457 | |
926e1192 | 458 | # FIXED_NEVER_USERS=root:bin:daemon |
059ec3d9 PH |
459 | FIXED_NEVER_USERS=root |
460 | ||
461 | ||
462 | #------------------------------------------------------------------------------ | |
c1d94452 DW |
463 | # By default, Exim insists that its configuration file be owned by root. You |
464 | # can specify one additional permitted owner here. | |
059ec3d9 PH |
465 | |
466 | # CONFIGURE_OWNER= | |
467 | ||
35edf2ff | 468 | # If the configuration file is group-writeable, Exim insists by default that it |
c1d94452 | 469 | # is owned by root. You can specify one additional permitted group owner here. |
35edf2ff PH |
470 | |
471 | # CONFIGURE_GROUP= | |
472 | ||
473 | # If you specify CONFIGURE_OWNER or CONFIGURE_GROUP as a name, this is looked | |
474 | # up at build time, and the uid or gid number is built into the binary. | |
475 | # However, you can specify that the lookup is deferred until runtime. In this | |
476 | # case, it is the name that is built into the binary. You can do this by a | |
477 | # setting of the form: | |
059ec3d9 PH |
478 | |
479 | # CONFIGURE_OWNER=ref:mail | |
35edf2ff | 480 | # CONFIGURE_GROUP=ref:sysadmin |
059ec3d9 | 481 | |
35edf2ff PH |
482 | # In other words, put "ref:" in front of the user or group name. Although this |
483 | # costs a bit of resource at runtime, it is convenient to use this feature when | |
484 | # building binaries that are to be run on multiple systems where the names may | |
485 | # refer to different uids or gids. It also allows you to build Exim on a system | |
486 | # where the relevant user or group is not defined. | |
059ec3d9 PH |
487 | |
488 | ||
489 | #------------------------------------------------------------------------------ | |
490 | # The -C option allows Exim to be run with an alternate runtime configuration | |
cd25e41d DW |
491 | # file. When this is used by root, root privilege is retained by the binary |
492 | # (for any other caller including the Exim user, it is dropped). You can | |
493 | # restrict the location of alternate configurations by defining a prefix below. | |
494 | # Any file used with -C must then start with this prefix (except that /dev/null | |
495 | # is also permitted if the caller is root, because that is used in the install | |
496 | # script). If the prefix specifies a directory that is owned by root, a | |
497 | # compromise of the Exim account does not permit arbitrary alternate | |
498 | # configurations to be used. The prefix can be more restrictive than just a | |
499 | # directory (the second example). | |
059ec3d9 PH |
500 | |
501 | # ALT_CONFIG_PREFIX=/some/directory/ | |
502 | # ALT_CONFIG_PREFIX=/some/directory/exim.conf- | |
503 | ||
504 | ||
261dc43e DW |
505 | #------------------------------------------------------------------------------ |
506 | # When a user other than root uses the -C option to override the configuration | |
507 | # file (including the Exim user when re-executing Exim to regain root | |
508 | # privileges for local message delivery), this will normally cause Exim to | |
90b6341f DW |
509 | # drop root privileges. The TRUSTED_CONFIG_LIST option, specifies a file which |
510 | # contains a list of trusted configuration filenames, one per line. If the -C | |
511 | # option is used by the Exim user or by the user specified in the | |
512 | # CONFIGURE_OWNER setting, to specify a configuration file which is listed in | |
513 | # the TRUSTED_CONFIG_LIST file, then root privileges are not dropped by Exim. | |
514 | ||
515 | # TRUSTED_CONFIG_LIST=/usr/exim/trusted_configs | |
261dc43e DW |
516 | |
517 | ||
059ec3d9 PH |
518 | #------------------------------------------------------------------------------ |
519 | # Uncommenting this option disables the use of the -D command line option, | |
520 | # which changes the values of macros in the runtime configuration file. | |
521 | # This is another protection against somebody breaking into the Exim account. | |
522 | ||
523 | # DISABLE_D_OPTION=yes | |
524 | ||
525 | ||
a7cbbf50 PP |
526 | #------------------------------------------------------------------------------ |
527 | # By contrast, you might be maintaining a system which relies upon the ability | |
528 | # to override values with -D and assumes that these will be passed through to | |
529 | # the delivery processes. As of Exim 4.73, this is no longer the case by | |
530 | # default. Going forward, we strongly recommend that you use a shim Exim | |
cc5fdbc2 | 531 | # configuration file owned by root stored under TRUSTED_CONFIG_LIST. |
a7cbbf50 PP |
532 | # That shim can set macros before .include'ing your main configuration file. |
533 | # | |
534 | # As a strictly transient measure to ease migration to 4.73, the | |
535 | # WHITELIST_D_MACROS value definies a colon-separated list of macro-names | |
43236f35 | 536 | # which are permitted to be overridden from the command-line which will be |
a7cbbf50 PP |
537 | # honoured by the Exim user. So these are macros that can persist to delivery |
538 | # time. | |
539 | # Examples might be -DTLS or -DSPOOL=/some/dir. The values on the | |
540 | # command-line are filtered to only permit: [A-Za-z0-9_/.-]* | |
541 | # | |
542 | # This option is highly likely to be removed in a future release. It exists | |
543 | # only to make 4.73 as easy as possible to migrate to. If you use it, we | |
544 | # encourage you to schedule time to rework your configuration to not depend | |
545 | # upon it. Most people should not need to use this. | |
546 | # | |
547 | # By default, no macros are whitelisted for -D usage. | |
548 | ||
549 | # WHITELIST_D_MACROS=TLS:SPOOL | |
550 | ||
059ec3d9 PH |
551 | #------------------------------------------------------------------------------ |
552 | # Exim has support for the AUTH (authentication) extension of the SMTP | |
553 | # protocol, as defined by RFC 2554. If you don't know what SMTP authentication | |
554 | # is, you probably won't want to include this code, so you should leave these | |
555 | # settings commented out. If you do want to make use of SMTP authentication, | |
556 | # you must uncomment at least one of the following, so that appropriate code is | |
557 | # included in the Exim binary. You will then need to set up the run time | |
558 | # configuration to make use of the mechanism(s) selected. | |
559 | ||
560 | # AUTH_CRAM_MD5=yes | |
561 | # AUTH_CYRUS_SASL=yes | |
14aa5a05 | 562 | # AUTH_DOVECOT=yes |
44bbabb5 | 563 | # AUTH_GSASL=yes |
f4b00a2d PP |
564 | # AUTH_GSASL_PC=libgsasl |
565 | # AUTH_HEIMDAL_GSSAPI=yes | |
566 | # AUTH_HEIMDAL_GSSAPI_PC=heimdal-gssapi | |
059ec3d9 PH |
567 | # AUTH_PLAINTEXT=yes |
568 | # AUTH_SPA=yes | |
569 | ||
570 | ||
571 | #------------------------------------------------------------------------------ | |
572 | # If you specified AUTH_CYRUS_SASL above, you should ensure that you have the | |
573 | # Cyrus SASL library installed before trying to build Exim, and you probably | |
f4b00a2d PP |
574 | # want to uncomment the first line below. |
575 | # Similarly for GNU SASL, unless pkg-config is used via AUTH_GSASL_PC. | |
576 | # Ditto for AUTH_HEIMDAL_GSSAPI(_PC). | |
059ec3d9 PH |
577 | |
578 | # AUTH_LIBS=-lsasl2 | |
44bbabb5 | 579 | # AUTH_LIBS=-lgsasl |
f4b00a2d | 580 | # AUTH_LIBS=-lgssapi -lheimntlm -lkrb5 -lhx509 -lcom_err -lhcrypto -lasn1 -lwind -lroken -lcrypt |
059ec3d9 PH |
581 | |
582 | ||
583 | #------------------------------------------------------------------------------ | |
584 | # When Exim is decoding MIME "words" in header lines, most commonly for use | |
585 | # in the $header_xxx expansion, it converts any foreign character sets to the | |
586 | # one that is set in the headers_charset option. The default setting is | |
587 | # defined by this setting: | |
588 | ||
589 | HEADERS_CHARSET="ISO-8859-1" | |
590 | ||
591 | # If you are going to make use of $header_xxx expansions in your configuration | |
592 | # file, or if your users are going to use them in filter files, and the normal | |
593 | # character set on your host is something other than ISO-8859-1, you might | |
594 | # like to specify a different default here. This value can be overridden in | |
595 | # the runtime configuration, and it can also be overridden in individual filter | |
596 | # files. | |
597 | # | |
598 | # IMPORTANT NOTE: The iconv() function is needed for character code | |
599 | # conversions. Please see the next item... | |
600 | ||
601 | ||
602 | #------------------------------------------------------------------------------ | |
603 | # Character code conversions are possible only if the iconv() function is | |
604 | # installed on your operating system. There are two places in Exim where this | |
605 | # is relevant: (a) The $header_xxx expansion (see the previous item), and (b) | |
606 | # the Sieve filter support. For those OS where iconv() is known to be installed | |
607 | # as standard, the file in OS/Makefile-xxxx contains | |
608 | # | |
609 | # HAVE_ICONV=yes | |
610 | # | |
611 | # If you are not using one of those systems, but have installed iconv(), you | |
612 | # need to uncomment that line above. In some cases, you may find that iconv() | |
613 | # and its header file are not in the default places. You might need to use | |
614 | # something like this: | |
615 | # | |
616 | # HAVE_ICONV=yes | |
617 | # CFLAGS=-O -I/usr/local/include | |
618 | # EXTRALIBS_EXIM=-L/usr/local/lib -liconv | |
619 | # | |
620 | # but of course there may need to be other things in CFLAGS and EXTRALIBS_EXIM | |
621 | # as well. | |
622 | ||
623 | ||
624 | #------------------------------------------------------------------------------ | |
625 | # The passwords for user accounts are normally encrypted with the crypt() | |
626 | # function. Comparisons with encrypted passwords can be done using Exim's | |
627 | # "crypteq" expansion operator. (This is commonly used as part of the | |
628 | # configuration of an authenticator for use with SMTP AUTH.) At least one | |
629 | # operating system has an extended function called crypt16(), which uses up to | |
630 | # 16 characters of a password (the normal crypt() uses only the first 8). Exim | |
96c065cb | 631 | # supports the use of crypt16() as well as crypt() but note the warning below. |
059ec3d9 PH |
632 | |
633 | # You can always indicate a crypt16-encrypted password by preceding it with | |
634 | # "{crypt16}". If you want the default handling (without any preceding | |
635 | # indicator) to use crypt16(), uncomment the following line: | |
636 | ||
637 | # DEFAULT_CRYPT=crypt16 | |
638 | ||
639 | # If you do that, you can still access the basic crypt() function by preceding | |
640 | # an encrypted password with "{crypt}". For more details, see the description | |
641 | # of the "crypteq" condition in the manual chapter on string expansions. | |
642 | ||
96c065cb PH |
643 | # Some operating systems do not include a crypt16() function, so Exim has one |
644 | # of its own, which it uses unless HAVE_CRYPT16 is defined. Normally, that will | |
645 | # be set in an OS-specific Makefile for the OS that have such a function, so | |
646 | # you should not need to bother with it. | |
647 | ||
648 | # *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING *** | |
649 | # It turns out that the above is not entirely accurate. As well as crypt16() | |
650 | # there is a function called bigcrypt() that some operating systems have. This | |
651 | # may or may not use the same algorithm, and both of them may be different to | |
652 | # Exim's built-in crypt16() that is used unless HAVE_CRYPT16 is defined. | |
653 | # | |
654 | # However, since there is now a move away from the traditional crypt() | |
655 | # functions towards using SHA1 and other algorithms, tidying up this area of | |
656 | # Exim is seen as very low priority. In practice, if you need to, you can | |
657 | # define DEFAULT_CRYPT to the name of any function that has the same interface | |
658 | # as the traditional crypt() function. | |
659 | # *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING *** | |
059ec3d9 PH |
660 | |
661 | ||
662 | #------------------------------------------------------------------------------ | |
663 | # Exim can be built to support the SMTP STARTTLS command, which implements | |
664 | # Transport Layer Security using SSL (Secure Sockets Layer). To do this, you | |
665 | # must install the OpenSSL library package or the GnuTLS library. Exim contains | |
666 | # no cryptographic code of its own. Uncomment the following lines if you want | |
667 | # to build Exim with TLS support. If you don't know what this is all about, | |
668 | # leave these settings commented out. | |
669 | ||
670 | # This setting is required for any TLS support (either OpenSSL or GnuTLS) | |
671 | # SUPPORT_TLS=yes | |
672 | ||
f4b00a2d PP |
673 | # Uncomment one of these settings if you are using OpenSSL; pkg-config vs not |
674 | # USE_OPENSSL_PC=openssl | |
059ec3d9 PH |
675 | # TLS_LIBS=-lssl -lcrypto |
676 | ||
f4b00a2d PP |
677 | # Uncomment the first and either the second or the third of these if you |
678 | # are using GnuTLS. If you have pkg-config, then the second, else the third. | |
059ec3d9 | 679 | # USE_GNUTLS=yes |
f4b00a2d | 680 | # USE_GNUTLS_PC=gnutls |
059ec3d9 PH |
681 | # TLS_LIBS=-lgnutls -ltasn1 -lgcrypt |
682 | ||
683 | # If you are running Exim as a server, note that just building it with TLS | |
684 | # support is not all you need to do. You also need to set up a suitable | |
685 | # certificate, and tell Exim about it by means of the tls_certificate | |
686 | # and tls_privatekey run time options. You also need to set tls_advertise_hosts | |
687 | # to specify the hosts to which Exim advertises TLS support. On the other hand, | |
688 | # if you are running Exim only as a client, building it with TLS support | |
689 | # is all you need to do. | |
690 | ||
f4b00a2d PP |
691 | # If you are using pkg-config then you should not need to worry where the |
692 | # libraries and headers are installed, as the pkg-config .pc specification | |
693 | # should include all -L/-I information necessary. If not using pkg-config | |
694 | # then you might need to specify the locations too. | |
695 | ||
059ec3d9 PH |
696 | # Additional libraries and include files are required for both OpenSSL and |
697 | # GnuTLS. The TLS_LIBS settings above assume that the libraries are installed | |
698 | # with all your other libraries. If they are in a special directory, you may | |
699 | # need something like | |
700 | ||
701 | # TLS_LIBS=-L/usr/local/openssl/lib -lssl -lcrypto | |
702 | # or | |
703 | # TLS_LIBS=-L/opt/gnu/lib -lgnutls -ltasn1 -lgcrypt | |
704 | ||
705 | # TLS_LIBS is included only on the command for linking Exim itself, not on any | |
706 | # auxiliary programs. If the include files are not in a standard place, you can | |
707 | # set TLS_INCLUDE to specify where they are, for example: | |
708 | ||
709 | # TLS_INCLUDE=-I/usr/local/openssl/include/ | |
710 | # or | |
711 | # TLS_INCLUDE=-I/opt/gnu/include | |
712 | ||
713 | # You don't need to set TLS_INCLUDE if the relevant directories are already | |
714 | # specified in INCLUDE. | |
715 | ||
716 | ||
717 | #------------------------------------------------------------------------------ | |
718 | # The default distribution of Exim contains only the plain text form of the | |
719 | # documentation. Other forms are available separately. If you want to install | |
720 | # the documentation in "info" format, first fetch the Texinfo documentation | |
721 | # sources from the ftp directory and unpack them, which should create files | |
722 | # with the extension "texinfo" in the doc directory. You may find that the | |
723 | # version number of the texinfo files is different to your Exim version number, | |
724 | # because the main documentation isn't updated as often as the code. For | |
725 | # example, if you have Exim version 4.43, the source tarball upacks into a | |
726 | # directory called exim-4.43, but the texinfo tarball unpacks into exim-4.40. | |
727 | # In this case, move the contents of exim-4.40/doc into exim-4.43/doc after you | |
728 | # have unpacked them. Then set INFO_DIRECTORY to the location of your info | |
729 | # directory. This varies from system to system, but is often /usr/share/info. | |
730 | # Once you have done this, "make install" will build the info files and | |
731 | # install them in the directory you have defined. | |
732 | ||
733 | # INFO_DIRECTORY=/usr/share/info | |
734 | ||
735 | ||
736 | #------------------------------------------------------------------------------ | |
737 | # Exim log directory and files: Exim creates several log files inside a | |
738 | # single log directory. You can define the directory and the form of the | |
739 | # log file name here. If you do not set anything, Exim creates a directory | |
740 | # called "log" inside its spool directory (see SPOOL_DIRECTORY above) and uses | |
741 | # the filenames "mainlog", "paniclog", and "rejectlog". If you want to change | |
742 | # this, you can set LOG_FILE_PATH to a path name containing one occurrence of | |
743 | # %s. This will be replaced by one of the strings "main", "panic", or "reject" | |
744 | # to form the final file names. Some installations may want something like this: | |
745 | ||
746 | # LOG_FILE_PATH=/var/log/exim_%slog | |
747 | ||
748 | # which results in files with names /var/log/exim_mainlog, etc. The directory | |
749 | # in which the log files are placed must exist; Exim does not try to create | |
750 | # it for itself. It is also your responsibility to ensure that Exim is capable | |
751 | # of writing files using this path name. The Exim user (see EXIM_USER above) | |
752 | # must be able to create and update files in the directory you have specified. | |
753 | ||
754 | # You can also configure Exim to use syslog, instead of or as well as log | |
755 | # files, by settings such as these | |
756 | ||
757 | # LOG_FILE_PATH=syslog | |
758 | # LOG_FILE_PATH=syslog:/var/log/exim_%slog | |
759 | ||
760 | # The first of these uses only syslog; the second uses syslog and also writes | |
761 | # to log files. Do not include white space in such a setting as it messes up | |
762 | # the building process. | |
763 | ||
764 | ||
765 | #------------------------------------------------------------------------------ | |
766 | # When logging to syslog, the following option caters for syslog replacements | |
767 | # that are able to accept log entries longer than the 1024 characters allowed | |
768 | # by RFC 3164. It is up to you to make sure your syslog daemon can handle this. | |
769 | # Non-printable characters are usually unacceptable regardless, so log entries | |
770 | # are still split on newline characters. | |
771 | ||
772 | # SYSLOG_LONG_LINES=yes | |
773 | ||
774 | # If you are not interested in the process identifier (pid) of the Exim that is | |
775 | # making the call to syslog, then comment out the following line. | |
776 | ||
777 | SYSLOG_LOG_PID=yes | |
778 | ||
779 | ||
780 | #------------------------------------------------------------------------------ | |
781 | # Cycling log files: this variable specifies the maximum number of old | |
782 | # log files that are kept by the exicyclog log-cycling script. You don't have | |
783 | # to use exicyclog. If your operating system has other ways of cycling log | |
784 | # files, you can use them instead. The exicyclog script isn't run by default; | |
785 | # you have to set up a cron job for it if you want it. | |
786 | ||
787 | EXICYCLOG_MAX=10 | |
788 | ||
789 | ||
790 | #------------------------------------------------------------------------------ | |
791 | # The compress command is used by the exicyclog script to compress old log | |
792 | # files. Both the name of the command and the suffix that it adds to files | |
793 | # need to be defined here. See also the EXICYCLOG_MAX configuration. | |
794 | ||
795 | COMPRESS_COMMAND=/usr/bin/gzip | |
796 | COMPRESS_SUFFIX=gz | |
797 | ||
798 | ||
799 | #------------------------------------------------------------------------------ | |
800 | # If the exigrep utility is fed compressed log files, it tries to uncompress | |
801 | # them using this command. | |
802 | ||
803 | ZCAT_COMMAND=/usr/bin/zcat | |
804 | ||
805 | ||
806 | #------------------------------------------------------------------------------ | |
807 | # Compiling in support for embedded Perl: If you want to be able to | |
808 | # use Perl code in Exim's string manipulation language and you have Perl | |
809 | # (version 5.004 or later) installed, set EXIM_PERL to perl.o. Using embedded | |
810 | # Perl costs quite a lot of resources. Only do this if you really need it. | |
811 | ||
812 | # EXIM_PERL=perl.o | |
813 | ||
814 | ||
1a46a8c5 PH |
815 | #------------------------------------------------------------------------------ |
816 | # Support for dynamically-loaded string expansion functions via ${dlfunc. If | |
817 | # you are using gcc the dynamically-loaded object must be compiled with the | |
818 | # -shared option, and you will need to add -export-dynamic to EXTRALIBS so | |
1ea70a03 | 819 | # that the local_scan API is made available by the linker. You may also need |
612ba564 | 820 | # to add -ldl to EXTRALIBS so that dlopen() is available to Exim. |
1a46a8c5 PH |
821 | |
822 | # EXPAND_DLFUNC=yes | |
823 | ||
824 | ||
059ec3d9 PH |
825 | #------------------------------------------------------------------------------ |
826 | # Exim has support for PAM (Pluggable Authentication Modules), a facility | |
827 | # which is available in the latest releases of Solaris and in some GNU/Linux | |
828 | # distributions (see http://ftp.kernel.org/pub/linux/libs/pam/). The Exim | |
829 | # support, which is intended for use in conjunction with the SMTP AUTH | |
830 | # facilities, is included only when requested by the following setting: | |
831 | ||
832 | # SUPPORT_PAM=yes | |
833 | ||
834 | # You probably need to add -lpam to EXTRALIBS, and in some releases of | |
835 | # GNU/Linux -ldl is also needed. | |
836 | ||
837 | ||
838 | #------------------------------------------------------------------------------ | |
839 | # Support for authentication via Radius is also available. The Exim support, | |
840 | # which is intended for use in conjunction with the SMTP AUTH facilities, | |
841 | # is included only when requested by setting the following parameter to the | |
842 | # location of your Radius configuration file: | |
843 | ||
844 | # RADIUS_CONFIG_FILE=/etc/radiusclient/radiusclient.conf | |
845 | # RADIUS_CONFIG_FILE=/etc/radius.conf | |
846 | ||
847 | # If you have set RADIUS_CONFIG_FILE, you should also set one of these to | |
848 | # indicate which RADIUS library is used: | |
059ec3d9 PH |
849 | |
850 | # RADIUS_LIB_TYPE=RADIUSCLIENT | |
7766a4f0 | 851 | # RADIUS_LIB_TYPE=RADIUSCLIENTNEW |
059ec3d9 PH |
852 | # RADIUS_LIB_TYPE=RADLIB |
853 | ||
7766a4f0 PH |
854 | # RADIUSCLIENT is the radiusclient library; you probably need to add |
855 | # -lradiusclient to EXTRALIBS. | |
856 | # | |
857 | # The API for the radiusclient library was changed at release 0.4.0. | |
858 | # Unfortunately, the header file does not define a version number that clients | |
859 | # can use to support both the old and new APIs. If you are using version 0.4.0 | |
860 | # or later of the radiusclient library, you should use RADIUSCLIENTNEW. | |
861 | # | |
862 | # RADLIB is the Radius library that comes with FreeBSD (the header file is | |
863 | # called radlib.h); you probably need to add -lradius to EXTRALIBS. | |
864 | # | |
865 | # If you do not set RADIUS_LIB_TYPE, Exim assumes the radiusclient library, | |
866 | # using the original API. | |
059ec3d9 PH |
867 | |
868 | ||
869 | #------------------------------------------------------------------------------ | |
870 | # Support for authentication via the Cyrus SASL pwcheck daemon is available. | |
871 | # Note, however, that pwcheck is now deprecated in favour of saslauthd (see | |
872 | # next item). The Exim support for pwcheck, which is intented for use in | |
873 | # conjunction with the SMTP AUTH facilities, is included only when requested by | |
874 | # setting the following parameter to the location of the pwcheck daemon's | |
875 | # socket. | |
876 | # | |
877 | # There is no need to install all of SASL on your system. You just need to run | |
878 | # ./configure --with-pwcheck, cd to the pwcheck directory within the sources, | |
879 | # make and make install. You must create the socket directory (default | |
880 | # /var/pwcheck) and chown it to exim's user and group. Once you have installed | |
881 | # pwcheck, you should arrange for it to be started by root at boot time. | |
882 | ||
883 | # CYRUS_PWCHECK_SOCKET=/var/pwcheck/pwcheck | |
884 | ||
885 | ||
886 | #------------------------------------------------------------------------------ | |
887 | # Support for authentication via the Cyrus SASL saslauthd daemon is available. | |
888 | # The Exim support, which is intented for use in conjunction with the SMTP AUTH | |
889 | # facilities, is included only when requested by setting the following | |
890 | # parameter to the location of the saslauthd daemon's socket. | |
891 | # | |
892 | # There is no need to install all of SASL on your system. You just need to run | |
893 | # ./configure --with-saslauthd (and any other options you need, for example, to | |
894 | # select or deselect authentication mechanisms), cd to the saslauthd directory | |
895 | # within the sources, make and make install. You must create the socket | |
896 | # directory (default /var/state/saslauthd) and chown it to exim's user and | |
897 | # group. Once you have installed saslauthd, you should arrange for it to be | |
898 | # started by root at boot time. | |
899 | ||
900 | # CYRUS_SASLAUTHD_SOCKET=/var/state/saslauthd/mux | |
901 | ||
902 | ||
903 | #------------------------------------------------------------------------------ | |
904 | # TCP wrappers: If you want to use tcpwrappers from within Exim, uncomment | |
905 | # this setting. See the manual section entitled "Use of tcpwrappers" in the | |
906 | # chapter on building and installing Exim. | |
907 | # | |
908 | # USE_TCP_WRAPPERS=yes | |
909 | # | |
910 | # You may well also have to specify a local "include" file and an additional | |
911 | # library for TCP wrappers, so you probably need something like this: | |
912 | # | |
913 | # USE_TCP_WRAPPERS=yes | |
914 | # CFLAGS=-O -I/usr/local/include | |
915 | # EXTRALIBS_EXIM=-L/usr/local/lib -lwrap | |
916 | # | |
917 | # but of course there may need to be other things in CFLAGS and EXTRALIBS_EXIM | |
918 | # as well. | |
5dc43717 JJ |
919 | # |
920 | # To use a name other than exim in the tcpwrappers config file, | |
921 | # e.g. if you're running multiple daemons with different access lists, | |
922 | # or multiple MTAs with the same access list, define | |
923 | # TCP_WRAPPERS_DAEMON_NAME accordingly | |
924 | # | |
925 | # TCP_WRAPPERS_DAEMON_NAME="exim" | |
059ec3d9 PH |
926 | |
927 | ||
928 | #------------------------------------------------------------------------------ | |
929 | # The default action of the exim_install script (which is run by "make | |
930 | # install") is to install the Exim binary with a unique name such as | |
931 | # exim-4.43-1, and then set up a symbolic link called "exim" to reference it, | |
932 | # moving the symbolic link from any previous version. If you define NO_SYMLINK | |
933 | # (the value doesn't matter), the symbolic link is not created or moved. You | |
934 | # will then have to "turn Exim on" by setting up the link manually. | |
935 | ||
936 | # NO_SYMLINK=yes | |
937 | ||
938 | ||
939 | #------------------------------------------------------------------------------ | |
940 | # Another default action of the install script is to install a default runtime | |
941 | # configuration file if one does not exist. This configuration has a router for | |
942 | # expanding system aliases. The default assumes that these aliases are kept | |
943 | # in the traditional file called /etc/aliases. If such a file does not exist, | |
944 | # the installation script creates one that contains just comments (no actual | |
945 | # aliases). The following setting can be changed to specify a different | |
946 | # location for the system alias file. | |
947 | ||
948 | SYSTEM_ALIASES_FILE=/etc/aliases | |
949 | ||
950 | ||
951 | #------------------------------------------------------------------------------ | |
952 | # There are some testing options (-be, -bt, -bv) that read data from the | |
953 | # standard input when no arguments are supplied. By default, the input lines | |
954 | # are read using the standard fgets() function. This does not support line | |
955 | # editing during interactive input (though the terminal's "erase" character | |
956 | # works as normal). If your operating system has the readline() function, and | |
957 | # in addition supports dynamic loading of library functions, you can cause | |
958 | # Exim to use readline() for the -be testing option (only) by uncommenting the | |
959 | # following setting. Dynamic loading is used so that the library is loaded only | |
960 | # when the -be testing option is given; by the time the loading occurs, | |
961 | # Exim has given up its root privilege and is running as the calling user. This | |
962 | # is the reason why readline() is NOT supported for -bt and -bv, because Exim | |
963 | # runs as root or as exim, respectively, for those options. When USE_READLINE | |
964 | # is "yes", as well as supporting line editing, a history of input lines in the | |
965 | # current run is maintained. | |
966 | ||
967 | # USE_READLINE=yes | |
968 | ||
79b5812b | 969 | # You may need to add -ldl to EXTRALIBS when you set USE_READLINE=yes. |
b08b24c8 PH |
970 | # Note that this option adds to the size of the Exim binary, because the |
971 | # dynamic loading library is not otherwise included. | |
972 | ||
059ec3d9 PH |
973 | |
974 | ||
975 | ############################################################################### | |
976 | # THINGS YOU ALMOST NEVER NEED TO MENTION # | |
977 | ############################################################################### | |
978 | ||
979 | # The settings in this section are available for use in special circumstances. | |
980 | # In the vast majority of installations you need not change anything below. | |
981 | ||
982 | ||
983 | #------------------------------------------------------------------------------ | |
984 | # The following commands live in different places in some OS. Either the | |
985 | # ultimate default settings, or the OS-specific files should already point to | |
986 | # the right place, but they can be overridden here if necessary. These settings | |
987 | # are used when building various scripts to ensure that the correct paths are | |
988 | # used when the scripts are run. They are not used in the Makefile itself. Perl | |
989 | # is not necessary for running Exim unless you set EXIM_PERL (see above) to get | |
990 | # it embedded, but there are some utilities that are Perl scripts. If you | |
991 | # haven't got Perl, Exim will still build and run; you just won't be able to | |
992 | # use those utilities. | |
993 | ||
994 | # CHOWN_COMMAND=/usr/bin/chown | |
995 | # CHGRP_COMMAND=/usr/bin/chgrp | |
c2f9a1ee | 996 | # CHMOD_COMMAND=/usr/bin/chmod |
059ec3d9 PH |
997 | # MV_COMMAND=/bin/mv |
998 | # RM_COMMAND=/bin/rm | |
c2f9a1ee | 999 | # TOUCH_COMMAND=/usr/bin/touch |
059ec3d9 PH |
1000 | # PERL_COMMAND=/usr/bin/perl |
1001 | ||
1002 | ||
1003 | #------------------------------------------------------------------------------ | |
1004 | # The following macro can be used to change the command for building a library | |
1005 | # of functions. By default the "ar" command is used, with options "cq". | |
1006 | # Only in rare circumstances should you need to change this. | |
1007 | ||
1008 | # AR=ar cq | |
1009 | ||
1010 | ||
1011 | #------------------------------------------------------------------------------ | |
1012 | # In some operating systems, the value of the TMPDIR environment variable | |
1013 | # controls where temporary files are created. Exim does not make use of | |
1014 | # temporary files, except when delivering to MBX mailboxes. However, if Exim | |
1015 | # calls any external libraries (e.g. DBM libraries), they may use temporary | |
1016 | # files, and thus be influenced by the value of TMPDIR. For this reason, when | |
1017 | # Exim starts, it checks the environment for TMPDIR, and if it finds it is set, | |
1018 | # it replaces the value with what is defined here. Commenting this setting | |
1019 | # suppresses the check altogether. | |
1020 | ||
1021 | TMPDIR="/tmp" | |
1022 | ||
1023 | ||
1024 | #------------------------------------------------------------------------------ | |
1025 | # The following macros can be used to change the default modes that are used | |
1026 | # by the appendfile transport. In most installations the defaults are just | |
1027 | # fine, and in any case, you can change particular instances of the transport | |
1028 | # at run time if you want. | |
1029 | ||
1030 | # APPENDFILE_MODE=0600 | |
1031 | # APPENDFILE_DIRECTORY_MODE=0700 | |
1032 | # APPENDFILE_LOCKFILE_MODE=0600 | |
1033 | ||
1034 | ||
1035 | #------------------------------------------------------------------------------ | |
1036 | # In some installations there may be multiple machines sharing file systems, | |
1037 | # where a different configuration file is required for Exim on the different | |
1038 | # machines. If CONFIGURE_FILE_USE_NODE is defined, then Exim will first look | |
1039 | # for a configuration file whose name is that defined by CONFIGURE_FILE, | |
1040 | # with the node name obtained by uname() tacked on the end, separated by a | |
1041 | # period (for example, /usr/exim/configure.host.in.some.domain). If this file | |
1042 | # does not exist, then the bare configuration file name is tried. | |
1043 | ||
1044 | # CONFIGURE_FILE_USE_NODE=yes | |
1045 | ||
1046 | ||
1047 | #------------------------------------------------------------------------------ | |
1048 | # In some esoteric configurations two different versions of Exim are run, | |
1049 | # with different setuid values, and different configuration files are required | |
1050 | # to handle the different cases. If CONFIGURE_FILE_USE_EUID is defined, then | |
1051 | # Exim will first look for a configuration file whose name is that defined | |
1052 | # by CONFIGURE_FILE, with the effective uid tacked on the end, separated by | |
1053 | # a period (for eximple, /usr/exim/configure.0). If this file does not exist, | |
1054 | # then the bare configuration file name is tried. In the case when both | |
1055 | # CONFIGURE_FILE_USE_EUID and CONFIGURE_FILE_USE_NODE are set, four files | |
1056 | # are tried: <name>.<euid>.<node>, <name>.<node>, <name>.<euid>, and <name>. | |
1057 | ||
1058 | # CONFIGURE_FILE_USE_EUID=yes | |
1059 | ||
1060 | ||
1061 | #------------------------------------------------------------------------------ | |
1062 | # The size of the delivery buffers: These specify the sizes (in bytes) of | |
1063 | # the buffers that are used when copying a message from the spool to a | |
1064 | # destination. There is rarely any need to change these values. | |
1065 | ||
1066 | # DELIVER_IN_BUFFER_SIZE=8192 | |
1067 | # DELIVER_OUT_BUFFER_SIZE=8192 | |
1068 | ||
1069 | ||
1070 | #------------------------------------------------------------------------------ | |
1071 | # The mode of the database directory: Exim creates a directory called "db" | |
1072 | # in its spool directory, to hold its databases of hints. This variable | |
1073 | # determines the mode of the created directory. The default value in the | |
1074 | # source is 0750. | |
1075 | ||
1076 | # EXIMDB_DIRECTORY_MODE=0750 | |
1077 | ||
1078 | ||
1079 | #------------------------------------------------------------------------------ | |
1080 | # Database file mode: The mode of files created in the "db" directory defaults | |
1081 | # to 0640 in the source, and can be changed here. | |
1082 | ||
1083 | # EXIMDB_MODE=0640 | |
1084 | ||
1085 | ||
1086 | #------------------------------------------------------------------------------ | |
1087 | # Database lock file mode: The mode of zero-length files created in the "db" | |
1088 | # directory to use for locking purposes defaults to 0640 in the source, and | |
1089 | # can be changed here. | |
1090 | ||
1091 | # EXIMDB_LOCKFILE_MODE=0640 | |
1092 | ||
1093 | ||
1094 | #------------------------------------------------------------------------------ | |
1095 | # This parameter sets the maximum length of the header portion of a message | |
1096 | # that Exim is prepared to process. The default setting is one megabyte. The | |
1097 | # limit exists in order to catch rogue mailers that might connect to your SMTP | |
1098 | # port, start off a header line, and then just pump junk at it for ever. The | |
1099 | # message_size_limit option would also catch this, but it may not be set. | |
1100 | # The value set here is the default; it can be changed at runtime. | |
1101 | ||
1102 | # HEADER_MAXSIZE="(1024*1024)" | |
1103 | ||
1104 | ||
1105 | #------------------------------------------------------------------------------ | |
1106 | # The mode of the input directory: The input directory is where messages are | |
1107 | # kept while awaiting delivery. Exim creates it if necessary, using a mode | |
1108 | # which can be defined here (default 0750). | |
1109 | ||
1110 | # INPUT_DIRECTORY_MODE=0750 | |
1111 | ||
1112 | ||
1113 | #------------------------------------------------------------------------------ | |
1114 | # The mode of Exim's log directory, when it is created by Exim inside the spool | |
1115 | # directory, defaults to 0750 but can be changed here. | |
1116 | ||
1117 | # LOG_DIRECTORY_MODE=0750 | |
1118 | ||
1119 | ||
1120 | #------------------------------------------------------------------------------ | |
1121 | # The log files themselves are created as required, with a mode that defaults | |
1122 | # to 0640, but which can be changed here. | |
1123 | ||
1124 | # LOG_MODE=0640 | |
1125 | ||
1126 | ||
1127 | #------------------------------------------------------------------------------ | |
1128 | # The TESTDB lookup is for performing tests on the handling of lookup results, | |
1129 | # and is not useful for general running. It should be included only when | |
1130 | # debugging the code of Exim. | |
1131 | ||
1132 | # LOOKUP_TESTDB=yes | |
1133 | ||
1134 | ||
1135 | #------------------------------------------------------------------------------ | |
1136 | # /bin/sh is used by default as the shell in which to run commands that are | |
1137 | # defined in the makefiles. This can be changed if necessary, by uncommenting | |
1138 | # this line and specifying another shell, but note that a Bourne-compatible | |
1139 | # shell is expected. | |
1140 | ||
1141 | # MAKE_SHELL=/bin/sh | |
1142 | ||
1143 | ||
1144 | #------------------------------------------------------------------------------ | |
1145 | # The maximum number of named lists of each type (address, domain, host, and | |
1146 | # local part) can be increased by changing this value. It should be set to | |
1147 | # a multiple of 16. | |
1148 | ||
1149 | # MAX_NAMED_LIST=16 | |
1150 | ||
1151 | ||
1152 | #------------------------------------------------------------------------------ | |
1153 | # Network interfaces: Unless you set the local_interfaces option in the runtime | |
1154 | # configuration file to restrict Exim to certain interfaces only, it will run | |
1155 | # code to find all the interfaces there are on your host. Unfortunately, | |
1156 | # the call to the OS that does this requires a buffer large enough to hold | |
1157 | # data for all the interfaces - it was designed in the days when a host rarely | |
1158 | # had more than three or four interfaces. Nowadays hosts can have very many | |
1159 | # virtual interfaces running on the same hardware. If you have more than 250 | |
1160 | # virtual interfaces, you will need to uncomment this setting and increase the | |
1161 | # value. | |
1162 | ||
1163 | # MAXINTERFACES=250 | |
1164 | ||
1165 | ||
1166 | #------------------------------------------------------------------------------ | |
1167 | # Per-message logs: While a message is in the process of being delivered, | |
1168 | # comments on its progress are written to a message log, for the benefit of | |
1169 | # human administrators. These logs are held in a directory called "msglog" | |
1170 | # in the spool directory. Its mode defaults to 0750, but can be changed here. | |
1171 | # The message log directory is also used for storing files that are used by | |
1172 | # transports for returning data to a message's sender (see the "return_output" | |
1173 | # option for transports). | |
1174 | ||
1175 | # MSGLOG_DIRECTORY_MODE=0750 | |
1176 | ||
1177 | ||
1178 | #------------------------------------------------------------------------------ | |
1179 | # There are three options which are used when compiling the Perl interface and | |
1180 | # when linking with Perl. The default values for these are placed automatically | |
1181 | # at the head of the Makefile by the script which builds it. However, if you | |
1182 | # want to override them, you can do so here. | |
1183 | ||
1184 | # PERL_CC= | |
1185 | # PERL_CCOPTS= | |
1186 | # PERL_LIBS= | |
1187 | ||
1188 | ||
1189 | #------------------------------------------------------------------------------ | |
1190 | # Identifying the daemon: When an Exim daemon starts up, it writes its pid | |
1191 | # (process id) to a file so that it can easily be identified. The path of the | |
1192 | # file can be specified here. Some installations may want something like this: | |
1193 | ||
1194 | # PID_FILE_PATH=/var/lock/exim.pid | |
1195 | ||
1196 | # If PID_FILE_PATH is not defined, Exim writes a file in its spool directory | |
1197 | # using the name "exim-daemon.pid". | |
1198 | ||
1199 | # If you start up a daemon without the -bd option (for example, with just | |
1200 | # the -q15m option), a pid file is not written. Also, if you override the | |
1201 | # configuration file with the -oX option, no pid file is written. In other | |
1202 | # words, the pid file is written only for a "standard" daemon. | |
1203 | ||
1204 | ||
1205 | #------------------------------------------------------------------------------ | |
1206 | # If Exim creates the spool directory, it is given this mode, defaulting in the | |
1207 | # source to 0750. | |
1208 | ||
1209 | # SPOOL_DIRECTORY_MODE=0750 | |
1210 | ||
1211 | ||
1212 | #------------------------------------------------------------------------------ | |
1213 | # The mode of files on the input spool which hold the contents of messages can | |
1214 | # be changed here. The default is 0640 so that information from the spool is | |
1215 | # available to anyone who is a member of the Exim group. | |
1216 | ||
1217 | # SPOOL_MODE=0640 | |
1218 | ||
1219 | ||
1220 | #------------------------------------------------------------------------------ | |
1221 | # Moving frozen messages: If the following is uncommented, Exim is compiled | |
1222 | # with support for automatically moving frozen messages out of the main spool | |
1223 | # directory, a facility that is found useful by some large installations. A | |
1224 | # run time option is required to cause the moving actually to occur. Such | |
1225 | # messages become "invisible" to the normal management tools. | |
1226 | ||
1227 | # SUPPORT_MOVE_FROZEN_MESSAGES=yes | |
1228 | ||
54fc8428 | 1229 | |
82c6910a PP |
1230 | #------------------------------------------------------------------------------ |
1231 | # Expanding match_* second paramters: BE CAREFUL IF ENABLING THIS! | |
1232 | # It has proven too easy in practice for administrators to configure security | |
1233 | # problems into their Exim install, by treating match_domain{}{} and friends | |
1234 | # as a form of string comparison, where the second string comes from untrusted | |
1235 | # data. Because these options take lists, which can include lookup;LOOKUPDATA | |
1236 | # style elements, a foe can then cause Exim to, eg, execute an arbitrary MySQL | |
1237 | # query, dropping tables. | |
1238 | # From Exim 4.77 onwards, the second parameter is not expanded; it can still | |
1239 | # be a list literal, or a macro, or a named list reference. There is also | |
1240 | # the new expansion condition "inlisti" which does expand the second parameter, | |
1241 | # but treats it as a list of strings; also, there's "eqi" which is probably | |
1242 | # what is normally wanted. | |
1243 | # | |
1244 | # If you really need to have the old behaviour, know what you are doing and | |
1245 | # will not complain if your system is compromised as a result of doing so, then | |
1246 | # uncomment this option to get the old behaviour back. | |
1247 | ||
1248 | # EXPAND_LISTMATCH_RHS=yes | |
1249 | ||
54fc8428 PH |
1250 | #------------------------------------------------------------------------------ |
1251 | # Disabling the use of fsync(): DO NOT UNCOMMENT THE FOLLOWING LINE unless you | |
1252 | # really, really, really know what you are doing. And even then, think again. | |
1253 | # You should never uncomment this when compiling a binary for distribution. | |
1254 | # Use it only when compiling Exim for your own use. | |
1255 | # | |
1256 | # Uncommenting this line enables the use of a runtime option called | |
1257 | # disable_fsync, which can be used to stop Exim using fsync() to ensure that | |
1258 | # files are written to disc before proceeding. When this is disabled, crashes | |
1259 | # and hardware problems such as power outages can cause data to be lost. This | |
1260 | # feature should only be used in very exceptional circumstances. YOU HAVE BEEN | |
1261 | # WARNED. | |
1262 | ||
1263 | # ENABLE_DISABLE_FSYNC=yes | |
1264 | ||
059ec3d9 | 1265 | # End of EDITME for Exim 4. |