[exim] DomainKeys experiment:4.51 RC

Pàgina inicial
Delete this message
Reply to this message
Autor: Larry Rosenman
Data:  
A: ph10
CC: exim-users
Assumpte: [exim] DomainKeys experiment:4.51 RC
Adding the DomainKeys stuff, I can no longer build Eximon (it needs the dk.o
object).

Also, trying to use the standard SysV make on UnixWare, how do I add
the -ldomainkeys and -I/usr/local/include to the right variable?

Also get a BUNCH of warnings (see attached gmake.out file).



-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-351-4152                 E-Mail: ler@???
US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611

>>> Creating links to source files...
>>> New Makefile installed
>>> Use "make makefile" if you need to force rebuilding of the makefile


gmake[1]: Entering directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at'
/bin/sh ../scripts/Configure-os.h
/bin/sh ../scripts/Configure-os.c
/usr/bin/cc -O -I/usr/local/include -I/usr/local/include -o buildconfig buildconfig.c -lsocket -lnsl -lelf -lgen -lresolv
/bin/sh ../scripts/Configure-config.h
gmake[2]: Entering directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at'
gmake[2]: `buildconfig' is up to date.
gmake[2]: Leaving directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at'
Building configuration file config.h
>>> config.h built


gmake[2]: Entering directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at/pcre'
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include maketables.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include get.c
/usr/bin/cc -o dftables -O -I/usr/local/include -I/usr/local/include dftables.c
./dftables chartables.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include pcre.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include study.c
rm -f libpcre.a
ar cq libpcre.a maketables.o get.o pcre.o study.o
/usr/bin/cc -c -DNOPOSIX -O -I/usr/local/include -I/usr/local/include -I. pcretest.c
/usr/bin/cc -O -I/usr/local/include -I/usr/local/include -o ../pcretest pcretest.o libpcre.a
gmake[2]: Leaving directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at/pcre'
sed \
-e "s?PROCESSED_FLAG?This file has been so processed.?"\
-e "/^# /p" \
-e "/^# /d" \
-e "s?CONFIGURE_FILE_USE_NODE??" \
-e "s?CONFIGURE_FILE_USE_EUID??" \
-e "s?CONFIGURE_FILE?/usr/exim/configure?" \
-e "s?BIN_DIRECTORY?/usr/exim/bin?" \
-e "s?EXICYCLOG_MAX?10?" \
-e "s?COMPRESS_COMMAND?/usr/local/bin/gzip?" \
-e "s?COMPRESS_SUFFIX?gz?" \
-e "s?CHOWN_COMMAND?/usr/bin/chown?" \
-e "s?CHGRP_COMMAND?/usr/bin/chgrp?" \
-e "s?MV_COMMAND?/bin/mv?" \
-e "s?RM_COMMAND?/bin/rm?" \
../src/exicyclog.src > exicyclog-t
>>> exicyclog script built


sed \
-e "s?PROCESSED_FLAG?This file has been so processed.?"\
-e "/^# /p" \
-e "/^# /d" \
-e "s?CONFIGURE_FILE_USE_NODE??" \
-e "s?CONFIGURE_FILE?/usr/exim/configure?" \
-e "s?BIN_DIRECTORY?/usr/exim/bin?" \
../src/exinext.src > exinext-t
>>> exinext script built


sed \
-e "s?PROCESSED_FLAG?This file has been so processed.?"\
-e "/^# /p" \
-e "/^# /d" \
-e "s?CONFIGURE_FILE_USE_NODE??" \
-e "s?CONFIGURE_FILE?/usr/exim/configure?" \
-e "s?BIN_DIRECTORY?/usr/exim/bin?" \
-e "s?EXIWHAT_PS_CMD?/bin/ps?" \
-e "s?EXIWHAT_PS_ARG?-e?" \
-e "s?EXIWHAT_KILL_SIGNAL?-USR1?" \
-e "s?EXIWHAT_EGREP_ARG?' exim( |$|-)'?" \
-e "s?EXIWHAT_MULTIKILL_CMD??" \
-e "s?EXIWHAT_MULTIKILL_ARG??" \
../src/exiwhat.src > exiwhat-t
>>> exiwhat script built


sed \
  -e "s?PROCESSED_FLAG?This file has been so processed.?"\
  -e "/^# /p" \
  -e "/^# /d" \
  -e "s?PERL_COMMAND?/usr/bin/perl?" \
  -e "s?ZCAT_COMMAND?/usr/local/bin/zcat?" \
          -e "s?COMPRESS_SUFFIX?gz?" \
  ../src/exigrep.src > exigrep-t

>>> exigrep script built


sed \
-e "s?PERL_COMMAND?/usr/bin/perl?" \
../src/eximstats.src > eximstats-t
>>> eximstats script built


sed -e "s?PERL_COMMAND?/usr/bin/perl?" \
-e "s?SPOOL_DIRECTORY?/var/spool/exim?" \
../src/exipick.src > exipick-t
>>> exipick script built


sed \
-e "s?PROCESSED_FLAG?This file has been so processed.?"\
-e "/^# /p" \
-e "/^# /d" \
-e "s?BIN_DIRECTORY?/usr/exim/bin?" \
-e "s?PERL_COMMAND?/usr/bin/perl?" \
../src/exiqgrep.src > exiqgrep-t
>>> exiqgrep script built


sed -e "s?PERL_COMMAND?/usr/bin/perl?" \
../src/exiqsumm.src > exiqsumm-t
>>> exiqsumm script built


sed -e "s?PERL_COMMAND?/usr/bin/perl?" \
../src/transport-filter.src > transport-filter.pl-t
>>> transport-filter.pl script built


sed -e "s?PERL_COMMAND?/usr/bin/perl?" \
../src/convert4r3.src > convert4r3-t
>>> convert4r3 script built


sed -e "s?PERL_COMMAND?/usr/bin/perl?" \
../src/convert4r4.src > convert4r4-t
>>> convert4r4 script built


sed \
-e "s?PROCESSED_FLAG?This file has been so processed.?"\
-e "/^# /p" \
-e "/^# /d" \
-e "s?CONFIGURE_FILE_USE_NODE??" \
-e "s?CONFIGURE_FILE?/usr/exim/configure?" \
-e "s?BIN_DIRECTORY?/usr/exim/bin?" \
-e "s?PERL_COMMAND?/usr/bin/perl?" \
../src/exim_checkaccess.src > exim_checkaccess-t
>>> exim_checkaccess script built


/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -o exim_dbmbuild.o exim_dbmbuild.c
/usr/bin/cc -o exim_dbmbuild -L/usr/local/lib exim_dbmbuild.o \
-lsocket -lnsl -lelf -lgen -lresolv

>>> exim_dbmbuild utility built

 
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  \
                  -DCOMPILE_UTILITY \
                  -DEXIM_DUMPDB \
                  -o exim_dumpdb.o exim_dbutil.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  \
                  -DCOMPILE_UTILITY \
                  -DOS_LOAD_AVERAGE \
                  -DFIND_RUNNING_INTERFACES \
                  -o util-os.o os.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  -DCOMPILE_UTILITY -o util-store.o store.c
/usr/bin/cc -O -I/usr/local/include -I/usr/local/include  -o exim_dumpdb -L/usr/local/lib exim_dumpdb.o util-os.o util-store.o \
  -lsocket -lnsl -lelf -lgen -lresolv  
 

>>> exim_dumpdb utility built

 
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  \
                  -DCOMPILE_UTILITY \
                  -DEXIM_FIXDB \
                  -o exim_fixdb.o exim_dbutil.c
/usr/bin/cc -O -I/usr/local/include -I/usr/local/include  -o exim_fixdb -L/usr/local/lib exim_fixdb.o util-os.o util-store.o \
  -lsocket -lnsl -lelf -lgen -lresolv  
 

>>> exim_fixdb utility built

 
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  \
                  -DCOMPILE_UTILITY \
                  -DEXIM_TIDYDB \
                  -o exim_tidydb.o exim_dbutil.c
/usr/bin/cc -O -I/usr/local/include -I/usr/local/include  -o exim_tidydb -L/usr/local/lib exim_tidydb.o util-os.o util-store.o \
  -lsocket -lnsl -lelf -lgen -lresolv  
 

>>> exim_tidydb utility built


/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include exim_lock.c
/usr/bin/cc -o exim_lock -L/usr/local/lib exim_lock.o \
-lsocket -lnsl -lelf -lgen -lresolv

>>> exim_lock utility built

 
gmake[2]: Entering directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at/lookups'
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include cdb.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include dbmdb.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include dnsdb.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include dsearch.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include ibase.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include ldap.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include lsearch.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include mysql.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include nis.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include nisplus.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include oracle.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include passwd.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include pgsql.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include testdb.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include whoson.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include lf_check_file.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I /usr/local/pgsql/include -I/usr/local/include lf_quote.c
/bin/rm -f lookups.a
ar cq lookups.a cdb.o dbmdb.o dnsdb.o dsearch.o ibase.o ldap.o lsearch.o mysql.o nis.o nisplus.o oracle.o passwd.o pgsql.o testdb.o whoson.o lf_check_file.o lf_quote.o
/bin/rm -rf ../drtables.o
gmake[2]: Leaving directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at/lookups'
 
gmake[2]: Entering directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at/routers'
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  accept.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  dnslookup.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  ipliteral.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  iplookup.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  manualroute.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  queryprogram.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  redirect.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  rf_change_domain.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  rf_expand_data.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  rf_get_errors_address.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  rf_get_munge_headers.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  rf_get_transport.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  rf_get_ugid.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  rf_lookup_hostlist.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  rf_queue_add.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  rf_self_action.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  rf_set_ugid.c
/bin/rm -f routers.a
ar cq routers.a accept.o dnslookup.o ipliteral.o iplookup.o manualroute.o queryprogram.o redirect.o rf_change_domain.o rf_expand_data.o rf_get_errors_address.o rf_get_munge_headers.o rf_get_transport.o rf_get_ugid.o rf_lookup_hostlist.o rf_queue_add.o rf_self_action.o rf_set_ugid.o
/bin/rm -rf ../drtables.o
gmake[2]: Leaving directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at/routers'
 
gmake[2]: Entering directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at/transports'
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  appendfile.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  autoreply.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  lmtp.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  pipe.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  smtp.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  tf_maildir.c
/bin/rm -f transports.a
ar cq transports.a appendfile.o autoreply.o lmtp.o pipe.o smtp.o tf_maildir.o
/bin/rm -rf ../drtables.o
gmake[2]: Leaving directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at/transports'
 
gmake[2]: Entering directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at/auths'
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  b64encode.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  b64decode.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  call_pam.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  call_pwcheck.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  call_radius.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  xtextencode.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  xtextdecode.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  get_data.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  get_no64_data.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  md5.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  cram_md5.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  cyrus_sasl.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  plaintext.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  pwcheck.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  sha1.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  auth-spa.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include  spa.c
/bin/rm -f auths.a
ar cq auths.a b64encode.o b64decode.o call_pam.o call_pwcheck.o call_radius.o xtextencode.o xtextdecode.o get_data.o get_no64_data.o md5.o cram_md5.o cyrus_sasl.o plaintext.o pwcheck.o sha1.o auth-spa.o spa.o
/bin/rm -rf ../drtables.o
gmake[2]: Leaving directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at/auths'
 
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    acl.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    child.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    crypt16.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    daemon.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    dbfn.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    debug.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    deliver.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    directory.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    dns.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    drtables.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    enq.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    exim.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    expand.c
UX:acomp: WARNING: "expand.c", line 1273: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1274: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1275: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1280: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1281: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1282: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1283: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1284: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1285: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1286: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1287: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1291: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1294: assignment type mismatch
UX:acomp: WARNING: "expand.c", line 1297: assignment type mismatch
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    filter.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    filtertest.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    globals.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    header.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    host.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    ip.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    log.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    lss.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    match.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    moan.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    os.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    parse.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    queue.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    rda.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    readconf.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    receive.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    retry.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    rewrite.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    rfc2047.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    route.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    search.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    sieve.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    smtp_in.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    smtp_out.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    spool_in.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    spool_out.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    store.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    string.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    tls.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    tod.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    transport.c
UX:acomp: WARNING: "transport.c", line 1018: argument #2 incompatible with prototype: strcmpic()
UX:acomp: WARNING: "transport.c", line 1019: argument #2 incompatible with prototype: strcmpic()
UX:acomp: WARNING: "transport.c", line 1037: argument #1 incompatible with prototype: tls_write()
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    tree.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    verify.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.  -o local_scan.o ../src/local_scan.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    malware.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    mime.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    regex.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    spam.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    spool_mbox.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    demime.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    bmi_spam.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    spf.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    srs.c
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include -I.    dk.c
UX:acomp: WARNING: "dk.c", line 41: argument #2 incompatible with prototype: dk_message()
UX:acomp: WARNING: "dk.c", line 136: argument #2 incompatible with prototype: dk_message()
UX:acomp: WARNING: "dk.c", line 252: assignment type mismatch
UX:acomp: WARNING: "dk.c", line 266: argument #2 incompatible with prototype: dk_message()
UX:acomp: WARNING: "dk.c", line 274: argument #2 incompatible with prototype: dk_message()
UX:acomp: WARNING: "dk.c", line 285: argument #2 incompatible with prototype: dk_message()
UX:acomp: WARNING: "dk.c", line 295: argument #2 incompatible with prototype: dk_message()
UX:acomp: WARNING: "dk.c", line 313: assignment type mismatch
UX:acomp: WARNING: "dk.c", line 319: argument #1 incompatible with prototype: strrchr()
UX:acomp: WARNING: "dk.c", line 319: assignment type mismatch
UX:acomp: WARNING: "dk.c", line 334: assignment type mismatch
UX:acomp: WARNING: "dk.c", line 376: assignment type mismatch
UX:acomp: WARNING: "dk.c", line 384: argument #1 incompatible with prototype: open()
UX:acomp: WARNING: "dk.c", line 404: argument #1 incompatible with prototype: snprintf()
 
awk '{ print ($1+1) }' cnumber.h > cnumber.temp
rm -f cnumber.h; mv cnumber.temp cnumber.h
/usr/bin/cc -c -O -I/usr/local/include -I/usr/local/include    version.c
rm -f exim
/usr/bin/cc -o exim -L/usr/local/lib acl.o child.o crypt16.o daemon.o dbfn.o debug.o deliver.o directory.o dns.o drtables.o enq.o exim.o expand.o filter.o filtertest.o globals.o header.o host.o ip.o log.o lss.o match.o moan.o os.o parse.o queue.o rda.o readconf.o receive.o retry.o rewrite.o rfc2047.o route.o search.o sieve.o smtp_in.o smtp_out.o spool_in.o spool_out.o store.o string.o tls.o tod.o transport.o tree.o verify.o local_scan.o  malware.o mime.o regex.o spam.o spool_mbox.o demime.o bmi_spam.o spf.o srs.o dk.o version.o \
  pcre/libpcre.a \
  routers/routers.a transports/transports.a lookups/lookups.a \
  auths/auths.a \
   -lsocket -lnsl -lelf -lgen -lresolv    \
    -L /opt/pgsql/lib  -lpq -L /usr/local/lib -ldomainkeys  \
   -lssl -lcrypto -L /usr/local/lib -ldomainkeys
 

>>> exim binary built


gmake[1]: Leaving directory `/home/ler/SOURCE/exim/exim-snapshot/build-Unixware7-x86at'
##################################################
#          The Exim mail transport agent         #
##################################################

# This is the template for Exim's main build-time configuration file. It
# contains settings that are independent of any operating system. These are
# things that are mostly sysadmin choices. The items below are divided into
# those you must specify, those you probably want to specify, those you might
# often want to specify, and those that you almost never need to mention.

# Edit this file and save the result to a file called Local/Makefile within the
# Exim distribution directory before running the "make" command.

# Things that depend on the operating system have default settings in
# OS/Makefile-Default, but these are overridden for some OS by files called
# called OS/Makefile-<osname>. You can further override these by creating files
# called Local/Makefile-<osname>, where "<osname>" stands for the name of your
# operating system - look at the names in the OS directory to see which names
# are recognized.

# However, if you are building Exim for a single OS only, you don't need to
# worry about setting up Local/Makefile-<osname>. Any build-time configuration
# settings you require can in fact be placed in the one file called
# Local/Makefile. It is only if you are building for several OS from the same
# source files that you need to worry about splitting off your own OS-dependent
# settings into separate files. (There's more explanation about how this all
# works in the toplevel README file, under "Modifying the building process", as
# well as in the Exim specification.)

# One OS-specific thing that may need to be changed is the command for running
# the C compiler; the overall default is gcc, but some OS Makefiles specify cc.
# You can override anything that is set by putting CC=whatever in your
# Local/Makefile.

# NOTE: You should never need to edit any of the distributed Makefiles; all
# overriding can be done in your Local/Makefile(s). This will make it easier
# for you when the next release comes along.

# The location of the X11 libraries is something else that is quite variable
# even between different versions of the same operating system (and indeed
# there are different versions of X11 as well, of course). The four settings
# concerned here are X11, XINCLUDE, XLFLAGS (linking flags) and X11_LD_LIB
# (dynamic run-time library). You need not worry about X11 unless you want to
# compile the Exim monitor utility. Exim itself does not use X11.

# Another area of variability between systems is the type and location of the
# DBM library package. Exim has support for ndbm, gdbm, tdb, and Berkeley DB.
# By default the code assumes ndbm; this often works with gdbm or DB, provided
# they are correctly installed, via their compatibility interfaces. However,
# Exim can also be configured to use the native calls for Berkeley DB (obsolete
# versions 1.85 and 2.x, or the current 3.x version) and also for gdbm.

# For some operating systems, a default DBM library (other than ndbm) is
# selected by a setting in the OS-specific Makefile. Most modern OS now have
# a DBM library installed as standard, and in many cases this will be selected
# for you by the OS-specific configuration. If Exim compiles without any
# problems, you probably do not have to worry about the DBM library. If you
# do want or need to change it, you should first read the discussion in the
# file doc/dbm.discuss.txt, which also contains instructions for testing Exim's
# interface to the DBM library.

# In Local/Makefiles blank lines and lines starting with # are ignored. It is
# also permitted to use the # character to add a comment to a setting, for
# example
#
# EXIM_GID=42   # the "mail" group
#
# However, with some versions of "make" this works only if there is no white
# space between the end of the setting and the #, so perhaps it is best
# avoided. A consequence of this facility is that it is not possible to have
# the # character present in any setting, but I can't think of any cases where
# this would be wanted.
###############################################################################



###############################################################################
#                    THESE ARE THINGS YOU MUST SPECIFY                        #
###############################################################################

# Exim will not build unless you specify BIN_DIRECTORY, CONFIGURE_FILE, and
# EXIM_USER. You also need EXIM_GROUP if EXIM_USER specifies a uid by number.

# If you don't specify SPOOL_DIRECTORY, Exim won't fail to build. However, it
# really is a very good idea to specify it here rather than at run time. This
# is particularly true if you let the logs go to their default location in the
# spool directory, because it means that the location of the logs is known
# before Exim has read the run time configuration file.

#------------------------------------------------------------------------------
# BIN_DIRECTORY defines where the exim binary will be installed by "make
# install". The path is also used internally by Exim when it needs to re-invoke
# itself, either to send an error message, or to recover root privilege. Exim's
# utility binaries and scripts are also installed in this directory. There is
# no "standard" place for the binary directory. Some people like to keep all
# the Exim files under one directory such as /usr/exim; others just let the
# Exim binaries go into an existing directory such as /usr/sbin or
# /usr/local/sbin. The installation script will try to create this directory,
# and any superior directories, if they do not exist.

BIN_DIRECTORY=/usr/exim/bin


#------------------------------------------------------------------------------
# CONFIGURE_FILE defines where Exim's run time configuration file is to be
# found. It is the complete pathname for the file, not just a directory. The
# location of all other run time files and directories can be changed in the
# run time configuration file. There is a lot of variety in the choice of
# location in different OS, and in the preferences of different sysadmins. Some
# common locations are in /etc or /etc/mail or /usr/local/etc or
# /usr/local/etc/mail. Another possibility is to keep all the Exim files under
# a single directory such as /usr/exim. Whatever you choose, the installation
# script will try to make the directory and any superior directories if they
# don't exist. It will also install a default runtime configuration if this
# file does not exist.

CONFIGURE_FILE=/usr/exim/configure

# It is possible to specify a colon-separated list of files for CONFIGURE_FILE.
# In this case, Exim will use the first of them that exists when it is run.
# However, if a list is specified, the installation script no longer tries to
# make superior directories or to install a default runtime configuration.


#------------------------------------------------------------------------------
# The Exim binary must normally be setuid root, so that it starts executing as
# root, but (depending on the options with which it is called) it does not
# always need to retain the root privilege. These settings define the user and
# group that is used for Exim processes when they no longer need to be root. In
# particular, this applies when receiving messages and when doing remote
# deliveries. (Local deliveries run as various non-root users, typically as the
# owner of a local mailbox.) Specifying these values as root is very strongly
# discouraged. These values are compiled into the binary.

EXIM_USER=smmsp

# If the setting of EXIM_USER is numeric (e.g. EXIM_USER=42), there must
# also be a setting of EXIM_GROUP. If, on the other hand, you use a name
# for EXIM_USER (e.g. EXIM_USER=exim), you don't need to set EXIM_GROUP unless
# you want to use a group other than the default group for the given user.

EXIM_GROUP=smmsp

# Many sites define a user called "exim", with an appropriate default group,
# and use
#
# EXIM_USER=exim
#
# while leaving EXIM_GROUP unspecified (commented out).


#------------------------------------------------------------------------------
# SPOOL_DIRECTORY defines the directory where all the data for messages in
# transit is kept. It is strongly recommended that you define it here, though
# it is possible to leave this till the run time configuration.

# Exim creates the spool directory if it does not exist. The owner and group
# will be those defined by EXIM_USER and EXIM_GROUP, and this also applies to
# all the files and directories that are created in the spool directory.

# Almost all installations choose this:

SPOOL_DIRECTORY=/var/spool/exim



###############################################################################
#           THESE ARE THINGS YOU PROBABLY WANT TO SPECIFY                     #
###############################################################################

# You need to specify some routers and transports if you want the Exim that you
# are building to be capable of delivering mail. You almost certainly need at
# least one type of lookup. You should consider whether you want to build
# the Exim monitor or not.


#------------------------------------------------------------------------------
# These settings determine which individual router drivers are included in the
# Exim binary. There are no defaults in the code; those routers that are wanted
# must be defined here by setting the appropriate variables to the value "yes".
# Including a router in the binary does not cause it to be used automatically.
# It has also to be configured in the run time configuration file. By
# commenting out those you know you don't want to use, you can make the binary
# a bit smaller. If you are unsure, leave all of these included for now.

ROUTER_ACCEPT=yes
ROUTER_DNSLOOKUP=yes
ROUTER_IPLITERAL=yes
ROUTER_MANUALROUTE=yes
ROUTER_QUERYPROGRAM=yes
ROUTER_REDIRECT=yes

# This one is very special-purpose, so is not included by default.

ROUTER_IPLOOKUP=yes


#------------------------------------------------------------------------------
# These settings determine which individual transport drivers are included in
# the Exim binary. There are no defaults; those transports that are wanted must
# be defined here by setting the appropriate variables to the value "yes".
# Including a transport in the binary does not cause it to be used
# automatically. It has also to be configured in the run time configuration
# file. By commenting out those you know you don't want to use, you can make
# the binary a bit smaller. If you are unsure, leave all of these included for
# now.

TRANSPORT_APPENDFILE=yes
TRANSPORT_AUTOREPLY=yes
TRANSPORT_PIPE=yes
TRANSPORT_SMTP=yes

# This one is special-purpose, and commonly not required, so it is not
# included by default.

TRANSPORT_LMTP=yes


#------------------------------------------------------------------------------
# The appendfile transport can write messages to local mailboxes in a number
# of formats. The code for three specialist formats, maildir, mailstore, and
# MBX, is included only when requested. If you do not know what this is about,
# leave these settings commented out.

# SUPPORT_MAILDIR=yes
# SUPPORT_MAILSTORE=yes
SUPPORT_MBX=yes


#------------------------------------------------------------------------------
# These settings determine which file and database lookup methods are included
# in the binary. See the manual chapter entitled "File and database lookups"
# for discussion. DBM and lsearch (linear search) are included by default. If
# you are unsure about the others, leave them commented out for now.
# LOOKUP_DNSDB does *not* refer to general mail routing using the DNS. It is
# for the specialist case of using the DNS as a general database facility (not
# common).

LOOKUP_DBM=yes
LOOKUP_LSEARCH=yes

LOOKUP_CDB=yes
LOOKUP_DNSDB=yes
LOOKUP_DSEARCH=yes
# LOOKUP_LDAP=yes
# LOOKUP_MYSQL=yes
# LOOKUP_NIS=yes
# LOOKUP_NISPLUS=yes
# LOOKUP_ORACLE=yes
LOOKUP_PASSWD=yes
LOOKUP_PGSQL=yes
# LOOKUP_WHOSON=yes


#------------------------------------------------------------------------------
# If you have set LOOKUP_LDAP=yes, you should set LDAP_LIB_TYPE to indicate
# which LDAP library you have. Unfortunately, though most of their functions
# are the same, there are minor differences. Currently Exim knows about four
# LDAP libraries: the one from the University of Michigan (also known as
# OpenLDAP 1), OpenLDAP 2, the Netscape SDK library, and the library that comes
# with Solaris 7 onwards. Uncomment whichever of these you are using.

# LDAP_LIB_TYPE=OPENLDAP1
# LDAP_LIB_TYPE=OPENLDAP2
# LDAP_LIB_TYPE=NETSCAPE
# LDAP_LIB_TYPE=SOLARIS

# If you don't set any of these, Exim assumes the original University of
# Michigan (OpenLDAP 1) library.


#------------------------------------------------------------------------------
# Additional libraries and include directories may be required for some
# lookup styles (e.g. LDAP, MYSQL or PGSQL). LOOKUP_LIBS is included only on
# the command for linking Exim itself, not on any auxiliary programs. You
# don't need to set LOOKUP_INCLUDE if the relevant directories are already
# specified in INCLUDE.

# LOOKUP_INCLUDE=-I /usr/local/ldap/include -I /usr/local/mysql/include -I /usr/local/pgsql/include
# LOOKUP_LIBS=-L/usr/local/lib -lldap -llber -lmysqlclient -lpq
LOOKUP_INCLUDE=-I /usr/local/pgsql/include -I/usr/local/include
LOOKUP_LIBS=-L /opt/pgsql/lib  -lpq -L /usr/local/lib -ldomainkeys

#------------------------------------------------------------------------------
# Compiling the Exim monitor: If you want to compile the Exim monitor, a
# program that requires an X11 display, then EXIM_MONITOR should be set to the
# value "eximon.bin". Comment out this setting to disable compilation of the
# monitor. The locations of various X11 directories for libraries and include
# files are defaulted in the OS/Makefile-Default file, but can be overridden in
# local OS-specific make files.

#EXIM_MONITOR=eximon.bin




#------------------------------------------------------------------------------
# Compiling Exim with content scanning support: If you want to compile Exim
# with support for message body content scanning, set WITH_CONTENT_SCAN to
# the value "yes". This will give you malware and spam scanning in the DATA ACL,
# and the MIME ACL. Please read the documentation to learn more about these
# features.

WITH_CONTENT_SCAN=yes

# If you want to use the deprecated "demime" condition in the DATA ACL,
# uncomment the line below. Doing so will also explicitly turn on the
# WITH_CONTENT_SCAN option. If possible, use the MIME ACL instead of
# the "demime" condition.

#WITH_OLD_DEMIME=yes

#------------------------------------------------------------------------------
# Compiling Exim with experimental features. These are documented in
# experimental-spec.txt. "Experimental" means that the way these features are
# implemented may still change. Backward compatibility is not guaranteed.

# Uncomment the following lines to add SPF support. You need to have libspf2
# installed on your system (www.libspf2.org). Depending on where it is installed
# you may have to edit the CFLAGS and LDFLAGS lines.

# EXPERIMENTAL_SPF=yes
# CFLAGS  += -I/usr/local/include
# LDFLAGS += -lspf2

# Uncomment the following lines to add SRS (Sender rewriting scheme) support.
# You need to have libsrs_alt installed on your system (srs.mirtol.com).
# Depending on where it is installed you may have to edit the CFLAGS and
# LDFLAGS lines.

# EXPERIMENTAL_SRS=yes
# CFLAGS  += -I/usr/local/include
# LDFLAGS += -lsrs_alt

# Uncomment the following lines to add Brightmail AntiSpam support. You need
# to have the Brightmail client SDK installed. Please check the experimental
# documentation for implementation details. You need to edit the CFLAGS and
# LDFLAGS lines.

# EXPERIMENTAL_BRIGHTMAIL=yes
# CFLAGS  += -I/opt/brightmail/bsdk-6.0/include
# LDFLAGS += -lxml2 -lbmiclient_single -L/opt/brightmail/bsdk-6.0/lib

EXPERIMENTAL_DOMAINKEYS=yes
CFLAGS += -I/usr/local/include
LDFLAGS += -L /usr/local/lib -ldomainkeys
###############################################################################
#                 THESE ARE THINGS YOU MIGHT WANT TO SPECIFY                  #
###############################################################################

# The items in this section are those that are commonly changed according to
# the sysadmin's preferences, but whose defaults are often acceptable.


#------------------------------------------------------------------------------
# Exim has support for the AUTH (authentication) extension of the SMTP
# protocol, as defined by RFC 2554. If you don't know what SMTP authentication
# is, you probably won't want to include this code, so you should leave these
# settings commented out. If you do want to make use of SMTP authentication,
# you must uncomment at least one of the following, so that appropriate code is
# included in the Exim binary. You will then need to set up the run time
# configuration to make use of the mechanism(s) selected.

AUTH_CRAM_MD5=yes
AUTH_PLAINTEXT=yes
AUTH_SPA=yes


#------------------------------------------------------------------------------
# When Exim is decoding MIME "words" in header lines, most commonly for use
# in the $header_xxx expansion, it converts any foreign character sets to the
# one that is set in the header_decode_to option. The default setting is
# defined by this setting:

HEADER_DECODE_TO="ISO-8859-1"

# If you are going to make use of $header_xxx expansions in your configuration
# file, or if your users are going to use them in filter files, and the normal
# character set on your host is something other than ISO-8859-1, you might
# like to specify a different default here. This value can be overridden in
# the runtime configuration, and it can also be overridden in individual filter
# files.
#
# IMPORTANT NOTE: The iconv() function is needed for character code
# conversions. Please see the next item...


#------------------------------------------------------------------------------
# Character code conversions are possible only if the iconv() function is
# installed on your operating system. There are two places in Exim where this
# is relevant: (a) The $header_xxx expansion (see the previous item), and (b)
# the Sieve filter support. For those OS where iconv() is known to be installed
# as standard, the file in OS/os.h-xxxx contains
#
# HAVE_ICONV=yes
#
# If you are not using one of those systems, but have installed iconv(), you
# need to uncomment that line above. In some cases, you may find that iconv()
# and its header file are not in the default places. You might need to use
# something like this:
#
# HAVE_ICONV=yes
# CFLAGS=-O -I/usr/local/include
# EXTRALIBS_EXIM=-L/usr/local/lib -liconv
#
# but of course there may need to be other things in CFLAGS and EXTRALIBS_EXIM
# as well.


#------------------------------------------------------------------------------
# The passwords for user accounts are normally encrypted with the crypt()
# function. Comparisons with encrypted passwords can be done using Exim's
# "crypteq" expansion operator. (This is commonly used as part of the
# configuration of an authenticator for use with SMTP AUTH.) At least one
# operating system has an extended function called crypt16(), which uses up to
# 16 characters of a password (the normal crypt() uses only the first 8). Exim
# supports the use of crypt16() as well as crypt().

# You can always indicate a crypt16-encrypted password by preceding it with
# "{crypt16}". If you want the default handling (without any preceding
# indicator) to use crypt16(), uncomment the following line:

# DEFAULT_CRYPT=crypt16

# If you do that, you can still access the basic crypt() function by preceding
# an encrypted password with "{crypt}". For more details, see the description
# of the "crypteq" condition in the manual chapter on string expansions.

# Since most operating systems do not include a crypt16() function (yet?), Exim
# has one of its own, which it uses unless HAVE_CRYPT16 is defined. Normally,
# that will be set in an OS-specific Makefile for the OS that have such a
# function, so you should not need to bother with it.


#------------------------------------------------------------------------------
# Exim can be built to support the SMTP STARTTLS command, which implements
# Transport Layer Security using SSL (Secure Sockets Layer). To do this, you
# must install the OpenSSL library package or the GnuTLS library. Exim contains
# no cryptographic code of its own. Uncomment the following lines if you want
# to build Exim with TLS support. If you don't know what this is all about,
# leave these settings commented out.

# This setting is required for any TLS support (either OpenSSL or GnuTLS)
SUPPORT_TLS=yes

# Uncomment this setting if you are using OpenSSL
TLS_LIBS=-lssl -lcrypto

# Uncomment these settings if you are using GnuTLS
# USE_GNUTLS=yes
# TLS_LIBS=-lgnutls -ltasn1 -lgcrypt

# If you are running Exim as a server, note that just building it with TLS
# support is not all you need to do. You also need to set up a suitable
# certificate, and tell Exim about it by means of the tls_certificate
# and tls_privatekey run time options. You also need to set tls_advertise_hosts
# to specify the hosts to which Exim advertises TLS support. On the other hand,
# if you are running Exim only as a client, building it with TLS support
# is all you need to do.

# Additional libraries and include files are required for both OpenSSL and
# GnuTLS. The TLS_LIBS settings above assume that the libraries are installed
# with all your other libraries. If they are in a special directory, you may
# need something like

# TLS_LIBS=-L/usr/local/openssl/lib -lssl -lcrypto
# or
# TLS_LIBS=-L/opt/gnu/lib -lgnutls -ltasn1 -lgcrypt

# TLS_LIBS is included only on the command for linking Exim itself, not on any
# auxiliary programs. If the include files are not in a standard place, you can
# set TLS_INCLUDE to specify where they are, for example:

# TLS_INCLUDE=-I/usr/local/openssl/include/
# or
# TLS_INCLUDE=-I/opt/gnu/include

# You don't need to set TLS_INCLUDE if the relevant directories are already
# specified in INCLUDE.


#------------------------------------------------------------------------------
# The default distribution of Exim contains only the plain text form of the
# documentation. Other forms are available separately. If you want to install
# the documentation in "info" format, first fetch the Texinfo documentation
# sources from the ftp directory and unpack them, which should create files
# with the extension "texinfo" in the doc directory. You may find that the
# version number of the texinfo files is different to your Exim version number,
# because the main documentation isn't updated as often as the code. For
# example, if you have Exim version 4.03, the source tarball upacks into a
# directory called exim-4.03, but the texinfo tarball unpacks into exim-4.00.
# In this case, move the contents of exim-4.00/doc into exim-4.03/doc after you
# have unpacked them. Then set INFO_DIRECTORY to the location of your info
# directory. This varies from system to system, but is often /usr/share/info.
# Once you have done this, "make install" will build the info files and
# install them in the directory you have defined.

# INFO_DIRECTORY=/usr/share/info


#------------------------------------------------------------------------------
# Exim log directory and files: Exim creates several log files inside a
# single log directory. You can define the directory and the form of the
# log file name here. If you do not set anything, Exim creates a directory
# called "log" inside its spool directory (see SPOOL_DIRECTORY above) and uses
# the filenames "mainlog", "paniclog", and "rejectlog". If you want to change
# this, you can set LOG_FILE_PATH to a path name containing one occurrence of
# %s. This will be replaced by one of the strings "main", "panic", or "reject"
# to form the final file names. Some installations may want something like this:

#LOG_FILE_PATH=/var/log/exim/%slog

# which results in files with names /var/log/exim_mainlog, etc. The directory
# in which the log files are placed must exist; Exim does not try to create
# it for itself. It is also your responsibility to ensure that Exim is capable
# of writing files using this path name. The Exim user (see EXIM_USER above)
# must be able to create and update files in the directory you have specified.

# You can also configure Exim to use syslog, instead of or as well as log
# files, by settings such as these

#LOG_FILE_PATH=syslog
LOG_FILE_PATH=syslog:/var/log/exim/%slog

# The first of these uses only syslog; the second uses syslog and also writes
# to log files. Do not include white space in such a setting as it messes up
# the building process.


#------------------------------------------------------------------------------
# When logging to syslog, the following option caters for syslog replacements
# that are able to accept log entries longer than the 1024 characters allowed
# by RFC 3164. It is up to you to make sure your syslog daemon can handle this.
# Non-printable characters are usually unacceptable regardless, so log entries
# are still split on newline characters.

# SYSLOG_LONG_LINES=yes

# If you are not interested in the process identifier (pid) of the Exim that is
# making the call to syslog, then comment out the following line.

SYSLOG_LOG_PID=yes


#------------------------------------------------------------------------------
# Cycling log files: this variable specifies the maximum number of old
# log files that are kept by the exicyclog log-cycling script. You don't have
# to use exicyclog. If your operating system has other ways of cycling log
# files, you can use them instead. The exicyclog script isn't run by default;
# you have to set up a cron job for it if you want it.

EXICYCLOG_MAX=10


#------------------------------------------------------------------------------
# The compress command is used by the exicyclog script to compress old log
# files. Both the name of the command and the suffix that it adds to files
# need to be defined here. See also the EXICYCLOG_MAX configuration.

COMPRESS_COMMAND=/usr/local/bin/gzip
COMPRESS_SUFFIX=gz


#------------------------------------------------------------------------------
# If the exigrep utility is fed compressed log files, it tries to uncompress
# them using this command.

ZCAT_COMMAND=/usr/local/bin/zcat


#------------------------------------------------------------------------------
# Compiling in support for embedded Perl: If you want to be able to
# use Perl code in Exim's string manipulation language and you have Perl
# (version 5.004 or later) installed, set EXIM_PERL to perl.o. Using embedded
# Perl costs quite a lot of resources. Only do this if you really need it.

# EXIM_PERL=perl.o


#------------------------------------------------------------------------------
# Exim has support for PAM (Pluggable Authentication Modules), a facility
# which is available in the latest releases of Solaris and in some GNU/Linux
# distributions (see http://ftp.kernel.org/pub/linux/libs/pam/). The Exim
# support, which is intended for use in conjunction with the SMTP AUTH
# facilities, is included only when requested by the following setting:

# SUPPORT_PAM=yes

# You probably need to add -lpam to EXTRALIBS, and in some releases of
# GNU/Linux -ldl is also needed.


#------------------------------------------------------------------------------
# Support for authentication via Radius is also available. The Exim support,
# which is intended for use in conjunction with the SMTP AUTH facilities,
# is included only when requested by setting the following parameter to the
# location of your Radius configuration file:

# RADIUS_CONFIG_FILE=/etc/radiusclient/radiusclient.conf


#------------------------------------------------------------------------------
# Support for authentication via the Cyrus SASL pwcheck daemon is available.
# Note, however, that pwcheck is now deprecated in favour of saslauthd (see
# next item). The Exim support for pwcheck, which is intented for use in
# conjunction with the SMTP AUTH facilities, is included only when requested by
# setting the following parameter to the location of the pwcheck daemon's
# socket.
#
# There is no need to install all of SASL on your system. You just need to run
# ./configure --with-pwcheck, cd to the pwcheck directory within the sources,
# make and make install. You must create the socket directory (default
# /var/pwcheck) and chown it to exim's user and group. Once you have installed
# pwcheck, you should arrange for it to be started by root at boot time.

# CYRUS_PWCHECK_SOCKET=/var/pwcheck/pwcheck


#------------------------------------------------------------------------------
# Support for authentication via the Cyrus SASL saslauthd daemon is available.
# The Exim support, which is intented for use in conjunction with the SMTP AUTH
# facilities, is included only when requested by setting the following
# parameter to the location of the saslauthd daemon's socket.
#
# There is no need to install all of SASL on your system. You just need to run
# ./configure --with-saslauthd (and any other options you need, for example, to
# select or deselect authentication mechanisms), cd to the saslauthd directory
# within the sources, make and make install. You must create the socket
# directory (default /var/state/saslauthd) and chown it to exim's user and
# group. Once you have installed saslauthd, you should arrange for it to be
# started by root at boot time.

CYRUS_SASLAUTHD_SOCKET=/var/state/saslauthd/mux


#------------------------------------------------------------------------------
# TCP wrappers: If you want to use tcpwrappers from within Exim, uncomment
# this setting. See the manual section entitled "Use of tcpwrappers" in the
# chapter on building and installing Exim.
#
# USE_TCP_WRAPPERS=yes
#
# You may well also have to specify a local "include" file and an additional
# library for TCP wrappers, so you probably need something like this:
#
# USE_TCP_WRAPPERS=yes
# CFLAGS=-O -I/usr/local/include
# EXTRALIBS_EXIM=-L/usr/local/lib -lwrap
#
# but of course there may need to be other things in CFLAGS and EXTRALIBS_EXIM
# as well.


#------------------------------------------------------------------------------
# The default action of the exim_install script (which is run by "make
# install") is to install the Exim binary with a unique name such as
# exim-4.20-1, and then set up a symbolic link called "exim" to reference it,
# moving the symbolic link from any previous version. If you define NO_SYMLINK
# (the value doesn't matter), the symbolic link is not created or moved. You
# will then have to "turn Exim on" by setting up the link manually.

# NO_SYMLINK=yes


#------------------------------------------------------------------------------
# Another default action of the install script is to install a default runtime
# configuration file if one does not exist. This configuration has a router for
# expanding system aliases. The default assumes that these aliases are kept
# in the traditional file called /etc/aliases. If such a file does not exist,
# the installation script creates one that contains just comments (no actual
# aliases). The following setting can be changed to specify a different
# location for the system alias file.

SYSTEM_ALIASES_FILE=/etc/mail/aliases


###############################################################################
#              THINGS YOU ALMOST NEVER NEED TO MENTION                        #
###############################################################################

# The settings in this section are available for use in special circumstances.
# In the vast majority of installations you need not change anything below.


#------------------------------------------------------------------------------
# The following commands live in different places in some OS. Either the
# ultimate default settings, or the OS-specific files should already point to
# the right place, but they can be overridden here if necessary. These settings
# are used when building various scripts to ensure that the correct paths are
# used when the scripts are run. They are not used in the Makefile itself. Perl
# is not necessary for running Exim unless you set EXIM_PERL (see above) to get
# it embedded, but there are some utilities that are Perl scripts. If you
# haven't got Perl, Exim will still build and run; you just won't be able to
# use those utilities.

# CHOWN_COMMAND=/usr/bin/chown
# CHGRP_COMMAND=/usr/bin/chgrp
# MV_COMMAND=/bin/mv
# RM_COMMAND=/bin/rm
# PERL_COMMAND=/usr/bin/perl


#------------------------------------------------------------------------------
# The following macro can be used to change the command for building a library
# of functions. By default the "ar" command is used, with options "cq".
# Only in rare circumstances should you need to change this.

# AR=ar cq


#------------------------------------------------------------------------------
# In some operating systems, the value of the TMPDIR environment variable
# controls where temporary files are created. Exim does not make use of
# temporary files, except when delivering to MBX mailboxes. However, if Exim
# calls any external libraries (e.g. DBM libraries), they may use temporary
# files, and thus be influenced by the value of TMPDIR. For this reason, when
# Exim starts, it checks the environment for TMPDIR, and if it finds it is set,
# it replaces the value with what is defined here. Commenting this setting
# suppresses the check altogether.

TMPDIR="/tmp"


#------------------------------------------------------------------------------
# The following macros can be used to change the default modes that are used
# by the appendfile transport. In most installations the defaults are just
# fine, and in any case, you can change particular instances of the transport
# at run time if you want.

# APPENDFILE_MODE=0600
# APPENDFILE_DIRECTORY_MODE=0700
# APPENDFILE_LOCKFILE_MODE=0600


#------------------------------------------------------------------------------
# In some installations there may be multiple machines sharing file systems,
# where a different configuration file is required for Exim on the different
# machines. If CONFIGURE_FILE_USE_NODE is defined, then Exim will first look
# for a configuration file whose name is that defined by CONFIGURE_FILE,
# with the node name obtained by uname() tacked on the end, separated by a
# period (for example, /usr/exim/configure.host.in.some.domain). If this file
# does not exist, then the bare configuration file name is tried.

# CONFIGURE_FILE_USE_NODE=yes


#------------------------------------------------------------------------------
# In some esoteric configurations two different versions of Exim are run,
# with different setuid values, and different configuration files are required
# to handle the different cases. If CONFIGURE_FILE_USE_EUID is defined, then
# Exim will first look for a configuration file whose name is that defined
# by CONFIGURE_FILE, with the effective uid tacked on the end, separated by
# a period (for eximple, /usr/exim/configure.0). If this file does not exist,
# then the bare configuration file name is tried. In the case when both
# CONFIGURE_FILE_USE_EUID and CONFIGURE_FILE_USE_NODE are set, four files
# are tried: <name>.<euid>.<node>, <name>.<node>, <name>.<euid>, and <name>.

# CONFIGURE_FILE_USE_EUID=yes


#------------------------------------------------------------------------------
# The size of the delivery buffers: These specify the sizes (in bytes) of
# the buffers that are used when copying a message from the spool to a
# destination. There is rarely any need to change these values.

# DELIVER_IN_BUFFER_SIZE=8192
# DELIVER_OUT_BUFFER_SIZE=8192


#------------------------------------------------------------------------------
# The mode of the database directory: Exim creates a directory called "db"
# in its spool directory, to hold its databases of hints. This variable
# determines the mode of the created directory. The default value in the
# source is 0750.

# EXIMDB_DIRECTORY_MODE=0750


#------------------------------------------------------------------------------
# Database file mode: The mode of files created in the "db" directory defaults
# to 0640 in the source, and can be changed here.

# EXIMDB_MODE=0640


#------------------------------------------------------------------------------
# Database lock file mode: The mode of zero-length files created in the "db"
# directory to use for locking purposes defaults to 0640 in the source, and
# can be changed here.

# EXIMDB_LOCKFILE_MODE=0640


#------------------------------------------------------------------------------
# This parameter sets the maximum length of the header portion of a message
# that Exim is prepared to process. The default setting is one megabyte. The
# limit exists in order to catch rogue mailers that might connect to your SMTP
# port, start off a header line, and then just pump junk at it for ever. The
# message_size_limit option would also catch this, but it may not be set.
# The value set here is the default; it can be changed at runtime.

# HEADER_MAXSIZE="(1024*1024)"


#------------------------------------------------------------------------------
# The mode of the input directory: The input directory is where messages are
# kept while awaiting delivery. Exim creates it if necessary, using a mode
# which can be defined here (default 0750).

# INPUT_DIRECTORY_MODE=0750


#------------------------------------------------------------------------------
# The mode of Exim's log directory, when it is created by Exim inside the spool
# directory, defaults to 0750 but can be changed here.

# LOG_DIRECTORY_MODE=0750


#------------------------------------------------------------------------------
# The log files themselves are created as required, with a mode that defaults
# to 0640, but which can be changed here.

# LOG_MODE=0640


#------------------------------------------------------------------------------
# The TESTDB lookup is for performing tests on the handling of lookup results,
# and is not useful for general running. It should be included only when
# debugging the code of Exim.

# LOOKUP_TESTDB=yes


#------------------------------------------------------------------------------
# /bin/sh is used by default as the shell in which to run commands that are
# defined in the makefiles. This can be changed if necessary, by uncommenting
# this line and specifying another shell, but note that a Bourne-compatible
# shell is expected.

# MAKE_SHELL=/bin/sh


#------------------------------------------------------------------------------
# The maximum number of named lists of each type (address, domain, host, and
# local part) can be increased by changing this value. It should be set to
# a multiple of 16.

# MAX_NAMED_LIST=16


#------------------------------------------------------------------------------
# Network interfaces: Unless you set the local_interfaces option in the runtime
# configuration file to restrict Exim to certain interfaces only, it will run
# code to find all the interfaces there are on your host. Unfortunately,
# the call to the OS that does this requires a buffer large enough to hold
# data for all the interfaces - it was designed in the days when a host rarely
# had more than three or four interfaces. Nowadays hosts can have very many
# virtual interfaces running on the same hardware. If you have more than 250
# virtual interfaces, you will need to uncomment this setting and increase the
# value.

# MAXINTERFACES=250


#------------------------------------------------------------------------------
# Per-message logs: While a message is in the process of being delivered,
# comments on its progress are written to a message log, for the benefit of
# human administrators. These logs are held in a directory called "msglog"
# in the spool directory. Its mode defaults to 0750, but can be changed here.
# The message log directory is also used for storing files that are used by
# transports for returning data to a message's sender (see the "return_output"
# option for transports).

# MSGLOG_DIRECTORY_MODE=0750


#------------------------------------------------------------------------------
# There are three options which are used when compiling the Perl interface and
# when linking with Perl. The default values for these are placed automatically
# at the head of the Makefile by the script which builds it. However, if you
# want to override them, you can do so here.

# PERL_CC=
# PERL_CCOPTS=
# PERL_LIBS=


#------------------------------------------------------------------------------
# Identifying the daemon: When an Exim daemon starts up, it writes its pid
# (process id) to a file so that it can easily be identified. The path of the
# file can be specified here. Some installations may want something like this:

# PID_FILE_PATH=/var/lock/exim.pid

# If PID_FILE_PATH is not defined, Exim writes a file in its spool directory
# using the name "exim-daemon.pid".

# If you start up a daemon without the -bd option (for example, with just
# the -q15m option), a pid file is not written. Also, if you override the
# configuration file with the -oX option, no pid file is written. In other
# words, the pid file is written only for a "standard" daemon.


#------------------------------------------------------------------------------
# If Exim creates the spool directory, it is given this mode, defaulting in the
# source to 0750.

# SPOOL_DIRECTORY_MODE=0750


#------------------------------------------------------------------------------
# The mode of files on the input spool which hold the contents of messages can
# be changed here. The default is 0640 so that information from the spool is
# available to anyone who is a member of the Exim group.

# SPOOL_MODE=0640


#------------------------------------------------------------------------------
# Moving frozen messages: If the following is uncommented, Exim is compiled
# with support for automatically moving frozen messages out of the main spool
# directory, a facility that is found useful by some large installations. A
# run time option is required to cause the moving actually to occur. Such
# messages become "invisible" to the normal management tools.

# SUPPORT_MOVE_FROZEN_MESSAGES=yes

# End of EDITME for Exim 4.

##################################################
#                The Exim Monitor                #
##################################################

# This is the template for the Exim monitor's main build-time configuration
# file. It contains settings that are independent of any operating system. It
# should be edited and then saved to a file called Local/eximon.conf before
# running the make command to build the monitor, if any settings are required.
# Local/eximon.conf can be empty if no changes are needed. The examples given
# here (commented out) are the default settings.

# Any settings made in the configuration file can be overridden at run time
# by setting up an environment variable with the same name as any of these
# options, but preceded by EXIMON_, for example, EXIMON_WINDOW_TITLE.


##################################################################
#      Set these variables as appropriate for your system        #
##################################################################

# The qualifying name for your domain. The only use made of this is for
# testing that certain addresses are the same when displaying the
# log tail, and for shortening sender addresses in the queue display.

QUALIFY_DOMAIN=lerctr.org

# The default minimum width and height for the whole window are 103 and
# 162 pixels respectively. This is enough to hold the left-most stripchart
# and the quit button. The values can be changed here.

MIN_HEIGHT=162
MIN_WIDTH=103

# If you uncomment the following setting, the window will start up at
# its minimum size, instead of the default maximum. There may be a quick
# flash during the start-up process. Defining it this way allows it to be
# overridden by an environment variable.

# START_SMALL=${EXIMON_START_SMALL-yes}

# The title for eximon's main display window. It is possible to have
# host name of the machine you are running on substituted into the
# title string. If you include the string ${fullhostname} then the
# complete name is used. If you include ${hostname} then the full
# host name will have the string contained in the DOMAIN variable
# stripped from its right-hand end before being substituted. Any other
# shell or environment variables may also be included.

# If you use any substitutions, remember to ensure that the $ and {}
# characters are escaped from the shell, e.g. by using single quotes.

WINDOW_TITLE="${hostname} eximon"

# The domain that you want to be stripped from the machine's full hostname
# when forming the short host name for the eximon window title, as
# described above.

DOMAIN=lerctr.org

# Parameters for the rolling display of the tail of the exim log file.
# The width and depth are measured in pixels; LOG_BUFFER specifies the
# amount of store to set aside for holding the log tail, which is displayed
# in a scrolling window. When this store is full, the earlier 50% of it
# is discarded - this is much more efficient that throwing it away line
# by line. The number given can be followed by the letter K to indicate
# that the value is in kilobytes. A minimum value of 1K is enforced.

LOG_DEPTH=300
LOG_WIDTH=950
LOG_BUFFER=20K

# The font which is used in the log tail display. This is defined in
# the normal X manner. It must be a "character cell" font, because this
# is required by the text widget.

LOG_FONT=-misc-fixed-medium-r-normal-*-14-140-*-*-*-*-iso8859-1

# Parameters for the display of message that are on the exim queue.
# The width and depth are measured in pixels.

QUEUE_DEPTH=200
QUEUE_WIDTH=950

# The font which is used in the queue display.

QUEUE_FONT=$LOG_FONT

# When a message has more than one undelivered address, they are listed
# one below the other. A limit can be placed on the number of addresses
# displayed for any one message. If there are more, then "..." is used
# to indicate this.

QUEUE_MAX_ADDRESSES=10

# The display of the contents of the queue is updated every QUEUE_INTERVAL
# seconds by default (there is a button to request update).

QUEUE_INTERVAL=300

# The size of the popup text window that is used for looking at the
# contents of messages, etc.

TEXT_DEPTH=200

# The keystroke/mouse-operation that is used to pop up the menu in the
# queue window is configurable. The default is Shift with the lefthand
# mouse button. The name of an alternative can be specified in the standard
# X way of naming these things. With the default configuration for the monitor,
# individuals can override this by setting the EXIMON_MENU_EVENT environment
# variable.

MENU_EVENT='Shift<Btn1Down>'

# When the menu is used to perform an operation on a message, the result of the
# operation is normally visible in the log window, so Eximon doesn't display
# the output of the generated Exim command. However, you can request that
# this output be shown in a separate window by setting ACTION_OUTPUT to "yes".
# This does not apply to the output generated from attempting to deliver a
# message, which is always shown.

ACTION_OUTPUT=yes

# When some action is taken on a message, such as freezing it, or changing
# its recipients, the queue display is normally automatically updated. On
# systems that have very large queues, this can take some time and be dis-
# tracting. If this option is set to "no", the queue display is no longer
# automatically updated after an action is applied to a message.

ACTION_QUEUE_UPDATE=yes

# When the menu item to display a message's body is invoked, the amount
# of data is limited to BODY_MAX bytes. This limit is a safety precaution
# to save the screen scrolling for ever on an enormous message.

BODY_MAX=20000

# The stripcharts are updated every STRIPCHART_INTERVAL seconds.

STRIPCHART_INTERVAL=60

# A stripchart showing the count of messages in the queue is always
# displayed on the left of eximon's window. Its name is "queue" by
# default, but can be changed by this variable.

QUEUE_STRIPCHART_NAME=queue

# The following variable may be set to the name of a disc partition. If
# it is, a stripchart showing the percentage fullness of the partition
# will be displayed as the second stripchart. This can be used to keep
# a display of a mail spool partition on the screen.

# SIZE_STRIPCHART=/var/mail

# The name of the size stripchart will be the last component of SIZE_STRIPCHART
# unless the following variable is set to override it.

# SIZE_STRIPCHART_NAME=space

# The following variable contains a specification of which stripcharts
# you want eximon to display based on log entries. The string consists of
# pairs of strings, delimited by slash characters. The first string in each
# pair is a regular expression that matches some distinguishing feature in a
# exim log entry.

# Entries that match the expression will be counted and displayed in a
# stripchart whose title is given by the second string. The string may
# be continued over several input lines, provided that it is split
# after a slash, and an additional slash (optionally preceded by white
# space) is included at the start of the continuation line.

# Stripcharts configured by the following parameter are displayed to the
# right of the queue and size stripcharts, in the order defined here.

# LOG_STRIPCHARTS='/ <= /in/
#                  / => /out/
#                  / => .+ R=local/local/
#                  / => .+ T=[^ ]*smtp/smtp/'

# End of exim_monitor/EDITME