README revision 64562
1230479Snetchild# Copyright (c) 1998-2000 Sendmail, Inc. and its suppliers. 2230479Snetchild# All rights reserved. 3230479Snetchild# Copyright (c) 1983, 1995-1997 Eric P. Allman. All rights reserved. 4230479Snetchild# Copyright (c) 1988 5230479Snetchild# The Regents of the University of California. All rights reserved. 6230479Snetchild# 7230479Snetchild# By using this file, you agree to the terms and conditions set 8230479Snetchild# forth in the LICENSE file which can be found at the top level of 9230479Snetchild# the sendmail distribution. 10230479Snetchild# 11230479Snetchild# 12230479Snetchild# $Id: README,v 8.263.2.1.2.19 2000/07/15 17:35:18 gshapiro Exp $ 13230479Snetchild# 14230479Snetchild 15230479SnetchildThis directory contains the source files for sendmail(TM). 16230479Snetchild 17230479Snetchild********************* 18230479Snetchild!! DO NOT USE MAKE !! in this directory to compile sendmail -- 19230479Snetchild********************* instead, use the "Build" script located in 20230479Snetchildthe sendmail directory. It will build an appropriate Makefile, and 21230479Snetchildcreate an appropriate obj.* subdirectory so that multiplatform 22support works easily. 23 24 ********************************************************** 25 ** Read below for more details on building sendmail. ** 26 ********************************************************** 27 28************************************************************************** 29** IMPORTANT: Read the appropriate paragraphs in the section on ** 30** ``Operating System and Compile Quirks''. ** 31************************************************************************** 32 33For detailed instructions, please read the document ../doc/op/op.me: 34 35 eqn ../doc/op/op.me | pic | ditroff -me 36 37Sendmail is a trademark of Sendmail, Inc. 38 39 40+-------------------+ 41| BUILDING SENDMAIL | 42+-------------------+ 43 44By far, the easiest way to compile sendmail is to use the "Build" 45script: 46 47 sh Build 48 49This uses the "uname" command to figure out what architecture you are 50on and creates a proper Makefile accordingly. It also creates a 51subdirectory per object format, so that multiarchitecture support is 52easy. In general this should be all you need. IRIX 6.x users should 53read the note below in the OPERATING SYSTEM AND COMPILE QUIRKS section. 54 55If you need to look at other include or library directories, use the 56-I or -L flags on the command line, e.g., 57 58 sh Build -I/usr/sww/include -L/usr/sww/lib 59 60It's also possible to create local site configuration in the file 61site.config.m4 (or another file settable with the -f flag). This 62file contains M4 definitions for various compilation values; the 63most useful are: 64 65confMAPDEF -D flags to specify database types to be included 66 (see below) 67confENVDEF -D flags to specify other environment information 68confINCDIRS -I flags for finding include files during compilation 69confLIBDIRS -L flags for finding libraries during linking 70confLIBS -l flags for selecting libraries during linking 71confLDOPTS other ld(1) linker options 72 73Others can be found by examining Makefile.m4. Please read 74../devtools/README for more information about the site.config.m4 75file. 76 77You can recompile from scratch using the -c flag with the Build 78command. This removes the existing compilation directory for the 79current platform and builds a new one. 80 81Porting to a new Unix-based system should be a matter of creating 82an appropriate configuration file in the devtools/OS/ directory. 83 84 85 86+----------------------+ 87| DATABASE DEFINITIONS | 88+----------------------+ 89 90There are several database formats that can be used for the alias files 91and for general maps. When used for alias files they interact in an 92attempt to be backward compatible. 93 94The options are: 95 96NEWDB The new Berkeley DB package. Some systems (e.g., BSD/OS and 97 Digital UNIX 4.0) have some version of this package 98 pre-installed. If your system does not have Berkeley DB 99 pre-installed, or the version installed is not version 2.0 100 or greater (e.g., is Berkeley DB 1.85 or 1.86), get the 101 current version from http://www.sleepycat.com/. DO NOT 102 use a version from any of the University of California, 103 Berkeley "Net" or other distributions. If you are still 104 running BSD/386 1.x, you will need to upgrade the included 105 Berkeley DB library to a current version. NEWDB is included 106 automatically if the Build script can find a library named 107 libdb.a or libdb.so. 108NDBM The older NDBM implementation -- the very old V7 DBM 109 implementation is no longer supported. 110NIS Network Information Services. To use this you must have 111 NIS support on your system. 112NISPLUS NIS+ (the revised NIS released with Solaris 2). You must 113 have NIS+ support on your system to use this flag. 114HESIOD Support for Hesiod (from the DEC/Athena distribution). You 115 must already have Hesiod support on your system for this to 116 work. You may be able to get this to work with the MIT/Athena 117 version of Hesiod, but that's likely to be a lot of work. 118LDAPMAP Lightweight Directory Access Protocol support. You will 119 have to install the UMich or OpenLDAP 120 (http://www.openldap.org/) ldap and lber libraries to use 121 this flag. 122MAP_REGEX Regular Expression support. You will need to use an 123 operating system which comes with the POSIX regex() 124 routines or install a regexp library such as libregex from 125 the Free Software Foundation. 126PH_MAP PH map support. You will need the qi PH package. 127MAP_NSD nsd map support (IRIX 6.5 and later). 128 129>>> NOTE WELL for NEWDB support: If you want to get ndbm support, for 130>>> Berkeley DB versions under 2.0, it is CRITICAL that you remove 131>>> ndbm.o from libdb.a before you install it and DO NOT install ndbm.h; 132>>> for Berkeley DB versions 2.0 through 2.3.14, remove dbm.o from libdb.a 133>>> before you install it. If you don't delete these, there is absolutely 134>>> no point to including -DNDBM, since it will just get you another 135>>> (inferior) API to the same format database. These files OVERRIDE 136>>> calls to ndbm routines -- in particular, if you leave ndbm.h in, 137>>> you can find yourself using the new db package even if you don't 138>>> define NEWDB. Berkeley DB versions later than 2.3.14 do not need 139>>> to be modified. Please also consult the README in the top level 140>>> directory of the sendmail distribution for other important information. 141>>> 142>>> Further note: DO NOT remove your existing /usr/include/ndbm.h -- 143>>> you need that one. But do not install an updated ndbm.h in 144>>> /usr/include, /usr/local/include, or anywhere else. 145 146If NEWDB and NDBM are defined (but not NIS), then sendmail will read 147NDBM format alias files, but the next time a newaliases is run the 148format will be converted to NEWDB; that format will be used forever 149more. This is intended as a transition feature. 150 151If NEWDB, NDBM, and NIS are all defined and the name of the file includes 152the string "/yp/", sendmail will rebuild BOTH the NEWDB and NDBM format 153alias files. However, it will only read the NEWDB file; the NDBM format 154file is used only by the NIS subsystem. This is needed because the NIS 155maps on an NIS server are built directly from the NDBM files. 156 157If NDBM and NIS are defined (regardless of the definition of NEWDB), 158and the filename includes the string "/yp/", sendmail adds the special 159tokens "YP_LAST_MODIFIED" and "YP_MASTER_NAME", both of which are 160required if the NDBM file is to be used as an NIS map. 161 162All of these flags are normally defined in the DBMDEF line in the 163Makefile. 164 165If you define NEWDB or HESIOD you get the User Database (USERDB) 166automatically. Generally you do want to have NEWDB for it to do 167anything interesting. See above for getting the Berkeley DB 168package (i.e., NEWDB). There is no separate "user database" 169package -- don't bother searching for it on the net. 170 171Hesiod and LDAP require libraries that may not be installed with your 172system. These are outside of my ability to provide support. See the 173"Quirks" section for more information. 174 175The regex map can be used to see if an address matches a certain regular 176expression. For example, all-numerics local parts are common spam 177addresses, so "^[0-9]+$" would match this. By using such a map in a 178check_* rule-set, you can block a certain range of addresses that would 179otherwise be considered valid. 180 181+---------------+ 182| COMPILE FLAGS | 183+---------------+ 184 185Wherever possible, I try to make sendmail pull in the correct 186compilation options needed to compile on various environments based on 187automatically defined symbols. Some machines don't seem to have useful 188symbols available, requiring that a compilation flag be defined in 189the Makefile; see the devtools/OS subdirectory for the supported 190architectures. 191 192If you are a system to which sendmail has already been ported you 193should not have to touch the following symbols. But if you are porting, 194you may have to tweak the following compilation flags in conf.h in order 195to get it to compile and link properly: 196 197SYSTEM5 Adjust for System V (not necessarily Release 4). 198SYS5SIGNALS Use System V signal semantics -- the signal handler 199 is automatically dropped when the signal is caught. 200 If this is not set, use POSIX/BSD semantics, where the 201 signal handler stays in force until an exec or an 202 explicit delete. Implied by SYSTEM5. 203SYS5SETPGRP Use System V setpgrp() semantics. Implied by SYSTEM5. 204HASFCHMOD Define this to one if you have the fchmod(2) system call. 205 This improves security. 206HASFCHOWN Define this to one if you have the fchown(2) system call. 207 This is required for the TrustedUser option. 208HASFLOCK Set this if you prefer to use the flock(2) system call 209 rather than using fcntl-based locking. Fcntl locking 210 has some semantic gotchas, but many vendor systems 211 also interface it to lockd(8) to do NFS-style locking. 212 Unfortunately, may vendors implementations of fcntl locking 213 is just plain broken (e.g., locks are never released, 214 causing your sendmail to deadlock; when the kernel runs 215 out of locks your system crashes). For this reason, I 216 recommend always defining this unless you are absolutely 217 certain that your fcntl locking implementation really works. 218HASUNAME Set if you have the "uname" system call. Implied by 219 SYSTEM5. 220HASUNSETENV Define this if your system library has the "unsetenv" 221 subroutine. 222HASSETSID Define this if you have the setsid(2) system call. This 223 is implied if your system appears to be POSIX compliant. 224HASINITGROUPS Define this if you have the initgroups(3) routine. 225HASSETVBUF Define this if you have the setvbuf(3) library call. 226 If you don't, setlinebuf will be used instead. This 227 defaults on if your compiler defines __STDC__. 228HASSETREUID Define this if you have setreuid(2) ***AND*** root can 229 use setreuid to change to an arbitrary user. This second 230 condition is not satisfied on AIX 3.x. You may find that 231 your system has setresuid(2), (for example, on HP-UX) in 232 which case you will also have to #define setreuid(r, e) 233 to be the appropriate call. Some systems (such as Solaris) 234 have a compatibility routine that doesn't work properly, 235 but may have "saved user ids" properly implemented so you 236 can ``#define setreuid(r, e) seteuid(e)'' and have it work. 237 The important thing is that you have a call that will set 238 the effective uid independently of the real or saved uid 239 and be able to set the effective uid back again when done. 240 There's a test program in ../test/t_setreuid.c that will 241 try things on your system. Setting this improves the 242 security, since sendmail doesn't have to read .forward 243 and :include: files as root. There are certain attacks 244 that may be unpreventable without this call. 245USESETEUID Define this to 1 if you have a seteuid(2) system call that 246 will allow root to set only the effective user id to an 247 arbitrary value ***AND*** you have saved user ids. This is 248 preferable to HASSETREUID if these conditions are fulfilled. 249 These are the semantics of the to-be-released revision of 250 Posix.1. The test program ../test/t_seteuid.c will try 251 this out on your system. If you define both HASSETREUID 252 and USESETEUID, the former is ignored. 253HASLSTAT Define this if you have symbolic links (and thus the 254 lstat(2) system call). This improves security. Unlike 255 most other options, this one is on by default, so you 256 need to #undef it in conf.h if you don't have symbolic 257 links (these days everyone does). 258HASSETRLIMIT Define this to 1 if you have the setrlimit(2) syscall. 259 You can define it to 0 to force it off. It is assumed 260 if you are running a BSD-like system. 261HASULIMIT Define this if you have the ulimit(2) syscall (System V 262 style systems). HASSETRLIMIT overrides, as it is more 263 general. 264HASWAITPID Define this if you have the waitpid(2) syscall. 265HASGETDTABLESIZE 266 Define this if you have the getdtablesize(2) syscall. 267HAS_ST_GEN Define this to 1 if your system has the st_gen field in 268 the stat structure (see stat(2)). 269HASSRANDOMDEV Define this if your system has the srandomdev(3) function 270 call. 271HASURANDOMDEV Define this if your system has /dev/urandom(4). 272HASSTRERROR Define this if you have the libc strerror(3) function (which 273 should be declared in <errno.h>), and it should be used 274 instead of sys_errlist. 275NEEDGETOPT Define this if you need a reimplementation of getopt(3). 276 On some systems, getopt does very odd things if called 277 to scan the arguments twice. This flag will ask sendmail 278 to compile in a local version of getopt that works 279 properly. 280NEEDSTRTOL Define this if your standard C library does not define 281 strtol(3). This will compile in a local version. 282NEEDVPRINTF Define this if your standard C library does not define 283 vprintf(3). Note that the resulting fake implementation 284 is not very elegant and may not even work on some 285 architectures. 286NEEDFSYNC Define this if your standard C library does not define 287 fsync(2). This will try to simulate the operation using 288 fcntl(2); if that is not available it does nothing, which 289 isn't great, but at least it compiles and runs. 290HASGETUSERSHELL Define this to 1 if you have getusershell(3) in your 291 standard C library. If this is not defined, or is defined 292 to be 0, sendmail will scan the /etc/shells file (no 293 NIS-style support, defaults to /bin/sh and /bin/csh if 294 that file does not exist) to get a list of unrestricted 295 user shells. This is used to determine whether users 296 are allowed to forward their mail to a program or a file. 297NEEDPUTENV Define this if your system needs am emulation of the 298 putenv(3) call. Define to 1 to implement it in terms 299 of setenv(3) or to 2 to do it in terms of primitives. 300NOFTRUNCATE Define this if you don't have the ftruncate(2) syscall. 301 If you don't have this system call, there is an unavoidable 302 race condition that occurs when creating alias databases. 303GIDSET_T The type of entries in a gidset passed as the second 304 argument to getgroups(2). Historically this has been an 305 int, so this is the default, but some systems (such as 306 IRIX) pass it as a gid_t, which is an unsigned short. 307 This will make a difference, so it is important to get 308 this right! However, it is only an issue if you have 309 group sets. 310SLEEP_T The type returned by the system sleep() function. 311 Defaults to "unsigned int". Don't worry about this 312 if you don't have compilation problems. 313ARBPTR_T The type of an arbitrary pointer -- defaults to "void *". 314 If you are an very old compiler you may need to define 315 this to be "char *". 316SOCKADDR_LEN_T The type used for the third parameter to accept(2), 317 getsockname(2), and getpeername(2), representing the 318 length of a struct sockaddr. Defaults to int. 319SOCKOPT_LEN_T The type used for the fifth parameter to getsockopt(2) 320 and setsockopt(2), representing the length of the option 321 buffer. Defaults to int. 322LA_TYPE The type of load average your kernel supports. These 323 can be one of: 324 LA_ZERO (1) -- it always returns the load average as 325 "zero" (and does so on all architectures). 326 LA_INT (2) to read /dev/kmem for the symbol avenrun and 327 interpret as a long integer. 328 LA_FLOAT (3) same, but interpret the result as a floating 329 point number. 330 LA_SHORT (6) to interpret as a short integer. 331 LA_SUBR (4) if you have the getloadavg(3) routine in your 332 system library. 333 LA_MACH (5) to use MACH-style load averages (calls 334 processor_set_info()), 335 LA_PROCSTR (7) to read /proc/loadavg and interpret it 336 as a string representing a floating-point 337 number (Linux-style). 338 LA_READKSYM (8) is an implementation suitable for some 339 versions of SVr4 that uses the MIOC_READKSYM ioctl 340 call to read /dev/kmem. 341 LA_DGUX (9) is a special implementation for DG/UX that uses 342 the dg_sys_info system call. 343 LA_HPUX (10) is an HP-UX specific version that uses the 344 pstat_getdynamic system call. 345 LA_IRIX6 (11) is an IRIX 6.x specific version that adapts 346 to 32 or 64 bit kernels; it is otherwise very similar 347 to LA_INT. 348 LA_KSTAT (12) uses the (Solaris-specific) kstat(3k) 349 implementation. 350 LA_DEVSHORT (13) reads a short from a system file (default: 351 /dev/table/avenrun) and scales it in the same manner 352 as LA_SHORT. 353 LA_INT, LA_SHORT, LA_FLOAT, and LA_READKSYM have several 354 other parameters that they try to divine: the name of your 355 kernel, the name of the variable in the kernel to examine, 356 the number of bits of precision in a fixed point load average, 357 and so forth. LA_DEVSHORT uses _PATH_AVENRUN to find the 358 device to be read to find the load average. 359 In desperation, use LA_ZERO. The actual code is in 360 conf.c -- it can be tweaked if you are brave. 361FSHIFT For LA_INT, LA_SHORT, and LA_READKSYM, this is the number 362 of bits of load average after the binary point -- i.e., 363 the number of bits to shift right in order to scale the 364 integer to get the true integer load average. Defaults to 8. 365_PATH_UNIX The path to your kernel. Needed only for LA_INT, LA_SHORT, 366 and LA_FLOAT. Defaults to "/unix" on System V, "/vmunix" 367 everywhere else. 368LA_AVENRUN For LA_INT, LA_SHORT, and LA_FLOAT, the name of the kernel 369 variable that holds the load average. Defaults to "avenrun" 370 on System V, "_avenrun" everywhere else. 371SFS_TYPE Encodes how your kernel can locate the amount of free 372 space on a disk partition. This can be set to SFS_NONE 373 (0) if you have no way of getting this information, 374 SFS_USTAT (1) if you have the ustat(2) system call, 375 SFS_4ARGS (2) if you have a four-argument statfs(2) 376 system call (and the include file is <sys/statfs.h>), 377 SFS_VFS (3), SFS_MOUNT (4), SFS_STATFS (5) if you have 378 the two-argument statfs(2) system call with includes in 379 <sys/vfs.h>, <sys/mount.h>, or <sys/statfs.h> respectively, 380 or SFS_STATVFS (6) if you have the two-argument statvfs(2) 381 call. The default if nothing is defined is SFS_NONE. 382SFS_BAVAIL with SFS_4ARGS you can also set SFS_BAVAIL to the field name 383 in the statfs structure that holds the useful information; 384 this defaults to f_bavail. 385SPT_TYPE Encodes how your system can display what a process is doing 386 on a ps(1) command (SPT stands for Set Process Title). Can 387 be set to: 388 SPT_NONE (0) -- Don't try to set the process title at all. 389 SPT_REUSEARGV (1) -- Pad out your argv with the information; 390 this is the default if none specified. 391 SPT_BUILTIN (2) -- The system library has setproctitle. 392 SPT_PSTAT (3) -- Use the PSTAT_SETCMD option to pstat(2) 393 to set the process title; this is used by HP-UX. 394 SPT_PSSTRINGS (4) -- Use the magic PS_STRINGS pointer (4.4BSD). 395 SPT_SYSMIPS (5) -- Use sysmips() supported by NEWS-OS 6. 396 SPT_SCO (6) -- Write kernel u. area. 397 SPT_CHANGEARGV (7) -- Write pointers to our own strings into 398 the existing argv vector. 399SPT_PADCHAR Character used to pad the process title; if undefined, 400 the space character (0x20) is used. This is ignored if 401 SPT_TYPE != SPT_REUSEARGV 402ERRLIST_PREDEFINED 403 If set, assumes that some header file defines sys_errlist. 404 This may be needed if you get type conflicts on this 405 variable -- otherwise don't worry about it. 406WAITUNION The wait(2) routine takes a "union wait" argument instead 407 of an integer argument. This is for compatibility with 408 old versions of BSD. 409SCANF You can set this to extend the F command to accept a 410 scanf string -- this gives you a primitive parser for 411 class definitions -- BUT it can make you vulnerable to 412 core dumps if the target file is poorly formed. 413SYSLOG_BUFSIZE You can define this to be the size of the buffer that 414 syslog accepts. If it is not defined, it assumes a 415 1024-byte buffer. If the buffer is very small (under 416 256 bytes) the log message format changes -- each 417 e-mail message will log many more messages, since it 418 will log each piece of information as a separate line 419 in syslog. 420BROKEN_RES_SEARCH 421 On Ultrix (and maybe other systems?) if you use the 422 res_search routine with an unknown host name, it returns 423 -1 but sets h_errno to 0 instead of HOST_NOT_FOUND. If 424 you set this, sendmail considers 0 to be the same as 425 HOST_NOT_FOUND. 426NAMELISTMASK If defined, values returned by nlist(3) are masked 427 against this value before use -- a common value is 428 0x7fffffff to strip off the top bit. 429BSD4_4_SOCKADDR If defined, socket addresses have an sa_len field that 430 defines the length of this address. 431SAFENFSPATHCONF Set this to 1 if and only if you have verified that a 432 pathconf(2) call with _PC_CHOWN_RESTRICTED argument on an 433 NFS filesystem where the underlying system allows users to 434 give away files to other users returns <= 0. Be sure you 435 try both on NFS V2 and V3. Some systems assume that their 436 local policy apply to NFS servers -- this is a bad 437 assumption! The test/t_pathconf.c program will try this 438 for you -- you have to run it in a directory that is 439 mounted from a server that allows file giveaway. 440SIOCGIFCONF_IS_BROKEN 441 Set this if your system has an SIOCGIFCONF ioctl defined, 442 but it doesn't behave the same way as "most" systems (BSD, 443 Solaris, SunOS, HP-UX, etc.) 444SIOCGIFNUM_IS_BROKEN 445 Set this if your system has an SIOCGIFNUM ioctl defined, 446 but it doesn't behave the same way as "most" systems 447 (Solaris, HP-UX). 448NEED_PERCENTQ Set this if your system doesn't support the printf 449 format strings %lld or %llu. If this is set, %qd and 450 %qu are used instead. 451FAST_PID_RECYCLE 452 Set this if your system can reuse the same PID in the same 453 second. 454SO_REUSEADDR_IS_BROKEN 455 Set this if your system has a setsockopt() SO_REUSEADDR 456 flag but doesn't pay attention to it when trying to bind a 457 socket to a recently closed port. 458SNPRINTF_IS_BROKEN 459 Set this if your system has an snprintf() implementation 460 which does not NUL terminate the string being filled in. 461 Use test/t_snprintf.c to test your system. 462 463+-----------------------+ 464| COMPILE-TIME FEATURES | 465+-----------------------+ 466 467There are a bunch of features that you can decide to compile in, such 468as selecting various database packages and special protocol support. 469Several are assumed based on other compilation flags -- if you want to 470"un-assume" something, you probably need to edit conf.h. Compilation 471flags that add support for special features include: 472 473NDBM Include support for "new" DBM library for aliases and maps. 474 Normally defined in the Makefile. 475NEWDB Include support for Berkeley DB package (hash & btree) 476 for aliases and maps. Normally defined in the Makefile. 477 If the version of NEWDB you have is the old one that does 478 not include the "fd" call (this call was added in version 479 1.5 of the Berkeley DB code), you must upgrade to the 480 current version of Berkeley DB. 481NIS Define this to get NIS (YP) support for aliases and maps. 482 Normally defined in the Makefile. 483NISPLUS Define this to get NIS+ support for aliases and maps. 484 Normally defined in the Makefile. 485HESIOD Define this to get Hesiod support for aliases and maps. 486 Normally defined in the Makefile. 487NETINFO Define this to get NeXT NetInfo support for aliases and maps. 488 Normally defined in the Makefile. 489LDAPMAP Define this to get LDAP support for maps. 490PH_MAP Define this to get PH support for maps. 491MAP_NSD Define this to get nsd support for maps. 492USERDB Define this to 1 to include support for the User Information 493 Database. Implied by NEWDB or HESIOD. You can use 494 -DUSERDB=0 to explicitly turn it off. 495IDENTPROTO Define this as 1 to get IDENT (RFC 1413) protocol support. 496 This is assumed unless you are running on Ultrix or 497 HP-UX, both of which have a problem in the UDP 498 implementation. You can define it to be 0 to explicitly 499 turn off IDENT protocol support. If defined off, the code 500 is actually still compiled in, but it defaults off; you 501 can turn it on by setting the IDENT timeout in the 502 configuration file. 503IP_SRCROUTE Define this to 1 to get IP source routing information 504 displayed in the Received: header. This is assumed on 505 most systems, but some (e.g., Ultrix) apparently have a 506 broken version of getsockopt that doesn't properly 507 support the IP_OPTIONS call. You probably want this if 508 your OS can cope with it. Symptoms of failure will be that 509 it won't compile properly (that is, no support for fetching 510 IP_OPTIONs), or it compiles but source-routed TCP connections 511 either refuse to open or open and hang for no apparent reason. 512 Ultrix and AIX3 are known to fail this way. 513LOG Set this to get syslog(3) support. Defined by default 514 in conf.h. You want this if at all possible. 515NETINET Set this to get TCP/IP support. Defined by default 516 in conf.h. You probably want this. 517NETINET6 Set this to get IPv6 support. Other configuration may 518 be needed in conf.h for your particular operating system. 519 Also, DaemonPortOptions must be set appropriately for 520 sendmail to accept IPv6 connections. 521NETISO Define this to get ISO networking support. 522NETUNIX Define this to get Unix domain networking support. Defined 523 by default. A few bizarre systems (SCO, ISC, Altos) don't 524 support this networking domain. 525NETNS Define this to get NS networking support. 526NETX25 Define this to get X.25 networking support. 527SMTP Define this to get the SMTP code. Implied by NETINET 528 or NETISO. 529NAMED_BIND If non-zero, include DNS (name daemon) support, including 530 MX support. The specs say you must use this if you run 531 SMTP. You don't have to be running a name server daemon 532 on your machine to need this -- any use of the DNS resolver, 533 including remote access to another machine, requires this 534 option. Defined by default in conf.h. Define it to zero 535 ONLY on machines that do not use DNS in any way. 536QUEUE Define this to get queueing code. Implied by NETINET 537 or NETISO; required by SMTP. This gives you other good 538 stuff -- it should be on. 539DAEMON Define this to get general network support. Implied by 540 NETINET or NETISO. Defined by default in conf.h. You 541 almost certainly want it on. 542MATCHGECOS Permit fuzzy matching of user names against the full 543 name (GECOS) field in the /etc/passwd file. This should 544 probably be on, since you can disable it from the config 545 file if you want to. Defined by default in conf.h. 546MIME8TO7 If non-zero, include 8 to 7 bit MIME conversions. This 547 also controls advertisement of 8BITMIME in the ESMTP 548 startup dialogue. 549MIME7TO8 If non-zero, include 7 to 8 bit MIME conversions. 550HES_GETMAILHOST Define this to 1 if you are using Hesiod with the 551 hes_getmailhost() routine. This is included with the MIT 552 Hesiod distribution, but not with the DEC Hesiod distribution. 553XDEBUG Do additional internal checking. These don't cost too 554 much; you might as well leave this on. 555TCPWRAPPERS Turns on support for the TCP wrappers library (-lwrap). 556 See below for further information. 557SECUREWARE Enable calls to the SecureWare luid enabling/changing routines. 558 SecureWare is a C2 security package added to several UNIX's 559 (notably ConvexOS) to get a C2 Secure system. This 560 option causes mail delivery to be done with the luid of the 561 recipient. 562SHARE_V1 Support for the fair share scheduler, version 1. Setting to 563 1 causes final delivery to be done using the recipients 564 resource limitations. So far as I know, this is only 565 supported on ConvexOS. 566SASL Enables SMTP AUTH (RFC 2554). This requires the Cyrus SASL 567 library (ftp://ftp.andrew.cmu.edu/pub/cyrus-mail/). Please 568 install at least version 1.5.13. See below for further 569 information: SASL COMPILATION AND CONFIGURATION. If your 570 SASL library is older than 1.5.10, you have to set this 571 to its version number using a simple conversion: a.b.c 572 -> c + b*100 + a*10000, e.g. for 1.5.9 define SASL=10509. 573 Note: Using an older version than 1.5.5 of Cyrus SASL is 574 not supported. Starting with version 1.5.10, setting SASL=1 575 is sufficient. Any value other than 1 (or 0) will be 576 compared with the actual version found and if there is a 577 mismatch, compilation will fail. 578EGD Define this if your system has EGD installed, see 579 http://www.lothar.com/tech/crypto/ . It should be used to 580 seed the PRNG for STARTTLS if HASURANDOMDEV is not defined. 581STARTTLS Enables SMTP STARTTLS (RFC 2487). This requires OpenSSL 582 (http://www.OpenSSL.org/) and sfio (see below). 583 See STARTTLS COMPILATION AND CONFIGURATION for further 584 information. 585TLS_NO_RSA Turn off support for RSA algorithms in STARTTLS. 586SFIO Uses sfio instead of stdio. sfio is available from AT&T 587 (http://www.research.att.com/sw/tools/sfio/). If this 588 compile flag is set, confSTDIO_TYPE must be set to portable. 589 This compile flag is necessary for STARTTLS; it also 590 enables the security layer of SASL. The sfio include file 591 stdio.h must be installed in a subdirectory called sfio, 592 i.e., if you install sfio in /usr/local, stdio.h should 593 be in /usr/local/include/sfio, and libsfio.a should be in 594 /usr/local/lib. Notice: you may run into problems if 595 you use sfio2000 (the body of a message is lost). Use 596 sfio1999 instead. 597 598 599+---------------------+ 600| DNS/RESOLVER ISSUES | 601+---------------------+ 602 603Many systems have old versions of the resolver library. At a minimum, 604you should be running BIND 4.8.3; older versions may compile, but they 605have known bugs that should give you pause. 606 607Common problems in old versions include "undefined" errors for 608dn_skipname. 609 610Some people have had a problem with BIND 4.9; it uses some routines 611that it expects to be externally defined such as strerror(). It may 612help to link with "-l44bsd" to solve this problem. This has apparently 613been fixed in later versions of BIND, starting around 4.9.3. In other 614words, if you use 4.9.0 through 4.9.2, you need -l44bsd; for earlier or 615later versions, you do not. 616 617!PLEASE! be sure to link with the same version of the resolver as 618the header files you used -- some people have used the 4.9 headers 619and linked with BIND 4.8 or vice versa, and it doesn't work. 620Unfortunately, it doesn't fail in an obvious way -- things just 621subtly don't work. 622 623WILDCARD MX RECORDS ARE A BAD IDEA! The only situation in which they 624work reliably is if you have two versions of DNS, one in the real world 625which has a wildcard pointing to your firewall, and a completely 626different version of the database internally that does not include 627wildcard MX records that match your domain. ANYTHING ELSE WILL GIVE 628YOU HEADACHES! 629 630 631+----------------------------------------+ 632| STARTTLS COMPILATION AND CONFIGURATION | 633+----------------------------------------+ 634 635Please read the docs accompanying the OpenSSL library and sfio. 636You have to compile and install both libraries before you can compile 637sendmail. See devtools/README how to set the correct compile time 638parameters; you should at least set the following variables: 639 640define(`confSTDIO_TYPE', `portable') 641APPENDDEF(`confENVDEF', `-DSFIO') 642APPENDDEF(`confLIBS', `-lsfio') 643APPENDDEF(`conf_sendmail_ENVDEF', `-DSTARTTLS') 644APPENDDEF(`conf_sendmail_LIBS', `-lssl -lcrypto') 645 646Configuration information can be found in doc/op/op.me (required 647certificates) and cf/README (how to tell sendmail about certificates). 648 649To perform an initial test, connect to your sendmail daemon 650(telnet localhost 25) and issue a EHLO localhost and see whether 651250-STARTTLS 652is in the response. If it isn't, run the daemon with 653-O LogLevel=14 654and try again. Then take a look at the logfile and see whether 655there are any problems listed about permissions (unsafe files) 656or the validity of X.509 certificates. 657 658Note: sfio must be used in all libraries with which sendmail exchanges 659file pointers. That is, libsmutil must be compiled with sfio, which 660is accomplished by the above config parameters. Another example is 661PH map support. This does not apply to the usual libraries, e.g., 662OpenSSL, Berkeley DB, Cyrus SASL. 663 664Further information can be found via: 665http://www.sendmail.org/tips/ 666 667 668+------------------------------------+ 669| SASL COMPILATION AND CONFIGURATION | 670+------------------------------------+ 671 672Please read the docs accompanying the library (INSTALL and README). 673If you use Berkeley DB for Cyrus SASL then you must compile sendmail 674with the same version of Berkeley DB. 675 676You have to select and install authentication mechanisms and tell 677sendmail where to find the sasl library and the include files (see 678devtools/README for the parameters to set). Setup the required 679users and passwords as explained in the SASL documentation. See 680also cf/README for authentication related options (esp. DefaultAuthInfo 681if you want authentication between MTAs). 682 683To perform an initial test, connect to your sendmail daemon 684(telnet localhost 25) and issue a EHLO localhost and see whether 685250-AUTH .... 686is in the response. If it isn't, run the daemon with 687-O LogLevel=14 688and try again. Then take a look at the logfile and see whether 689there are any security related problems listed (unsafe files). 690 691Further information can be found via: 692http://www.sendmail.org/tips/ 693 694 695+-------------------------------------+ 696| OPERATING SYSTEM AND COMPILE QUIRKS | 697+-------------------------------------+ 698 699GCC problems 700 ***************************************************************** 701 ** IMPORTANT: DO NOT USE OPTIMIZATION (``-O'') IF YOU ARE ** 702 ** RUNNING GCC 2.4.x or 2.5.x. THERE IS A BUG IN THE GCC ** 703 ** OPTIMIZER THAT CAUSES SENDMAIL COMPILES TO FAIL MISERABLY. ** 704 ***************************************************************** 705 706 Jim Wilson of Cygnus believes he has found the problem -- it will 707 probably be fixed in GCC 2.5.6 -- but until this is verified, be 708 very suspicious of gcc -O. This problem is reported to have been 709 fixed in gcc 2.6. 710 711 A bug in gcc 2.5.5 caused problems compiling sendmail 8.6.5 with 712 optimization on a Sparc. If you are using gcc 2.5.5, youi should 713 upgrade to the latest version of gcc. 714 715 Apparently GCC 2.7.0 on the Pentium processor has optimization 716 problems. I recommend against using -O on that architecture. This 717 has been seen on FreeBSD 2.0.5 RELEASE. 718 719 Solaris 2.X users should use version 2.7.2.3 over 2.7.2. 720 721 We have been told there are problems with gcc 2.8.0. If you are 722 using this version, you should upgrade to 2.8.1 or later. 723 724GDBM GDBM does not work with sendmail 8.8 because the additional 725 security checks and file locking cause problems. Unfortunately, 726 gdbm does not provide a compile flag in its version of ndbm.h so 727 the code can adapt. Until the GDBM authors can fix these problems, 728 GDBM will not be supported. Please use Berkeley DB instead. 729 730Configuration file location 731 Up to 8.6, sendmail tried to find the sendmail.cf file in the same 732 place as the vendors had put it, even when this was obviously 733 stupid. As of 8.7, sendmail ALWAYS looks for /etc/sendmail.cf. 734 Beginning with 8.10, sendmail uses /etc/mail/sendmail.cf. 735 You can get sendmail to use the stupid vendor .cf location by 736 adding -DUSE_VENDOR_CF_PATH during compilation, but this may break 737 support programs and scripts that need to find sendmail.cf. You 738 are STRONGLY urged to use symbolic links if you want to use the 739 vendor location rather than changing the location in the sendmail 740 binary. 741 742 NETINFO systems use NETINFO to determine the location of 743 sendmail.cf. The full path to sendmail.cf is stored as the value of 744 the "sendmail.cf" property in the "/locations/sendmail" 745 subdirectory of NETINFO. Set the value of this property to 746 "/etc/mail/sendmail.cf" (without the quotes) to use this new 747 default location for Sendmail 8.10.0 and higher. 748 749ControlSocket permissions 750 Paraphrased from BIND 8.2.1's README: 751 752 Solaris and other pre-4.4BSD kernels do not respect ownership or 753 protections on UNIX-domain sockets. The short term fix for this is to 754 override the default path and put such control sockets into root- 755 owned directories which do not permit non-root to r/w/x through them. 756 The long term fix is for all kernels to upgrade to 4.4BSD semantics. 757 758SunOS 4.x (Solaris 1.x) 759 You may have to use -lresolv on SunOS. However, beware that 760 this links in a new version of gethostbyname that does not 761 understand NIS, so you must have all of your hosts in DNS. 762 763 Some people have reported problems with the SunOS version of 764 -lresolv and/or in.named, and suggest that you get a newer 765 version. The symptoms are delays when you connect to the 766 SMTP server on a SunOS machine or having your domain added to 767 addresses inappropriately. There is a version of BIND 768 version 4.9 on gatekeeper.DEC.COM in pub/BSD/bind/4.9. 769 770 There is substantial disagreement about whether you can make 771 this work with resolv+, which allows you to specify a search-path 772 of services. Some people report that it works fine, others 773 claim it doesn't work at all (including causing sendmail to 774 drop core when it tries to do multiple resolv+ lookups for a 775 single job). I haven't tried resolv+, as we use DNS exclusively. 776 777 Should you want to try resolv+, it is on ftp.uu.net in 778 /networking/ip/dns. 779 780 Apparently getservbyname() can fail under moderate to high 781 load under some circumstances. This will exhibit itself as 782 the message ``554 makeconnection: service "smtp" unknown''. 783 The problem has been traced to one or more blank lines in 784 /etc/services on the NIS server machine. Delete these 785 and it should work. This info is thanks to Brian Bartholomew 786 <bb@math.ufl.edu> of I-Kinetics, Inc. 787 788 NOTE: The SunOS 4.X linker uses library paths specified during 789 compilation using -L for run-time shared library searches. 790 Therefore, it is vital that relative and unsafe directory paths not 791 be used when compiling sendmail. 792 793SunOS 4.0.2 (Sun 386i) 794 Date: Fri, 25 Aug 1995 11:13:58 +0200 (MET DST) 795 From: teus@oce.nl 796 797 Sendmail 8.7.Beta.12 compiles and runs nearly out of the box with the 798 following changes: 799 * Don't use /usr/5bin in your PATH, but make /usr/5bin/uname 800 available as "uname" command. 801 * Use the defines "-DBSD4_3 -DNAMED_BIND=0" in 802 devtools/OS/SunOS.4.0, which is selected via the "uname" command. 803 I recommend to make available the db-library on the system first 804 (and change the Makefile to use this library). 805 Note that the sendmail.cf and aliases files are found in /etc. 806 807SunOS 4.1.3, 4.1.3_U1 808 Sendmail causes crashes on SunOS 4.1.3 and 4.1.3_U1. According 809 to Sun bug number 1077939: 810 811 If an application does a getsockopt() on a SOCK_STREAM (TCP) socket 812 after the other side of the connection has sent a TCP RESET for 813 the stream, the kernel gets a Bus Trap in the tcp_ctloutput() or 814 ip_ctloutput() routine. 815 816 For 4.1.3, this is fixed in patch 100584-08, available on the 817 Sunsolve 2.7.1 or later CDs. For 4.1.3_U1, this was fixed in patch 818 101790-01 (SunOS 4.1.3_U1: TCP socket and reset problems), later 819 obsoleted by patch 102010-05. 820 821 Sun patch 100584-08 is not currently publicly available on their 822 ftp site but a user has reported it can be found at other sites 823 using a web search engine. 824 825Solaris 2.x (SunOS 5.x) 826 To compile for Solaris, the Makefile built by Build must 827 include a SOLARIS definition which reflects the Solaris version 828 (i.e. -DSOLARIS=20400 for 2.4 or -DSOLARIS=20501 for 2.5.1). 829 If you are using gcc, make sure -I/usr/include is not used (or 830 it might complain about TopFrame). If you are using Sun's cc, 831 make sure /opt/SUNWspro/bin/cc is used instead of /usr/ucb/cc 832 (or it might complain about tm_zone). 833 834 The Solaris "syslog" function is apparently limited to something 835 about 90 characters because of a kernel limitation. If you have 836 source code, you can probably up this number. You can get patches 837 that fix this problem: the patch ids are: 838 839 Solaris 2.1 100834 840 Solaris 2.2 100999 841 Solaris 2.3 101318 842 843 Be sure you have the appropriate patch installed or you won't 844 see system logging. 845 846Solaris 2.4 (SunOS 5.4) 847 If you include /usr/lib at the end of your LD_LIBRARY_PATH you run 848 the risk of getting the wrong libraries under some circumstances. 849 This is because of a new feature in Solaris 2.4, described by 850 Rod.Evans@Eng.Sun.COM: 851 852 >> Prior to SunOS 5.4, any LD_LIBRARY_PATH setting was ignored by the 853 >> runtime linker if the application was setxid (secure), thus your 854 >> applications search path would be: 855 >> 856 >> /usr/local/lib LD_LIBRARY_PATH component - IGNORED 857 >> /usr/lib LD_LIBRARY_PATH component - IGNORED 858 >> /usr/local/lib RPATH - honored 859 >> /usr/lib RPATH - honored 860 >> 861 >> the effect is that path 3 would be the first used, and this would 862 >> satisfy your resolv.so lookup. 863 >> 864 >> In SunOS 5.4 we made the LD_LIBRARY_PATH a little more flexible. 865 >> People who developed setxid applications wanted to be able to alter 866 >> the library search path to some degree to allow for their own 867 >> testing and debugging mechanisms. It was decided that the only 868 >> secure way to do this was to allow a `trusted' path to be used in 869 >> LD_LIBRARY_PATH. The only trusted directory we presently define 870 >> is /usr/lib. Thus a setuid root developer could play with some 871 >> alternative shared object implementations and place them in 872 >> /usr/lib (being root we assume they'ed have access to write in this 873 >> directory). This change was made as part of 1155380 - after a 874 >> *huge* amount of discussion regarding the security aspect of things. 875 >> 876 >> So, in SunOS 5.4 your applications search path would be: 877 >> 878 >> /usr/local/lib from LD_LIBRARY_PATH - IGNORED (untrustworthy) 879 >> /usr/lib from LD_LIBRARY_PATH - honored (trustworthy) 880 >> /usr/local/lib from RPATH - honored 881 >> /usr/lib from RPATH - honored 882 >> 883 >> here, path 2 would be the first used. 884 885Solaris 2.5.1 (SunOS 5.5.1) and 2.6 (SunOS 5.6) 886 Apparently Solaris 2.5.1 patch 103663-01 installs a new 887 /usr/include/resolv.h file that defines the __P macro without 888 checking to see if it is already defined. This new resolv.h is also 889 included in the Solaris 2.6 distribution. This causes compile 890 warnings such as: 891 892 In file included from daemon.c:51: 893 /usr/include/resolv.h:208: warning: `__P' redefined 894 cdefs.h:58: warning: this is the location of the previous definition 895 896 These warnings can be safely ignored or you can create a resolv.h 897 file in the obj.SunOS.5.5.1.* or obj.SunOS.5.6.* directory that reads: 898 899 #undef __P 900 #include "/usr/include/resolv.h" 901 902 Sun is aware of the problem (Sun bug ID 4081053) and it will be fixed 903 in Solaris 2.7. 904 905Solaris 7 (SunOS 5.7) 906 Solaris 7 includes LDAP libraries but the implementation was 907 lacking a few things. The following settings can be placed in 908 devtools/Site/site.SunOS.5.7.m4 if you plan on using those 909 libraries. 910 911 APPENDDEF(`confMAPDEF', `-DLDAPMAP') 912 APPENDDEF(`confENVDEF', `-DLDAP_VERSION_MAX=3') 913 APPENDDEF(`confLIBS', `-lldap') 914 915 Also, Sun's patch 107555 is needed to prevent a crash in the call 916 to ldap_set_option for LDAP_OPT_REFERRALS in ldapmap_setopts if 917 LDAP support is compiled in sendmail. 918 919Ultrix 920 By default, the IDENT protocol is turned off on Ultrix. If you 921 are running Ultrix 4.4 or later, or if you have included patch 922 CXO-8919 for Ultrix 4.2 or 4.3 to fix the TCP problem, you can turn 923 IDENT on in the configuration file by setting the "ident" timeout. 924 925 The Ultrix 4.5 Y2K patch (ULTV45-022-1) has changed the resolver 926 included in libc.a. Unfortunately, the __RES symbol hasn't changed 927 and therefore, sendmail can no longer automatically detect the 928 newer version. If you get a compiler error: 929 930 /lib/libc.a(gethostent.o): local_hostname_length: multiply defined 931 932 Then rebuild with this in devtools/Site/site.ULTRIX.m4: 933 934 APPENDDEF(`conf_sendmail_ENVDEF', `-DNEEDLOCAL_HOSTNAME_LENGTH=0') 935 936Digital UNIX (formerly DEC OSF/1) 937 If you are compiling on OSF/1 (DEC Alpha), you must use 938 -L/usr/shlib (otherwise it core dumps on startup). You may also 939 need -mld to get the nlist() function, although some versions 940 apparently don't need this. 941 942 Also, the enclosed makefile removed /usr/sbin/smtpd; if you need 943 it, just create the link to the sendmail binary. 944 945 On DEC OSF/1 3.2 or earlier, the MatchGECOS option doesn't work 946 properly due to a bug in the getpw* routines. If you want to use 947 this, use -DDEC_OSF_BROKEN_GETPWENT=1. The problem is fixed in 3.2C. 948 949 Digital's mail delivery agent, /bin/mail (aka /bin/binmail), will 950 only preserve the envelope sender in the "From " header if 951 DefaultUserID is set to daemon. Setting this to mailnull will 952 cause all mail to have the header "From mailnull ...". To use 953 a different DefaultUserID, you will need to use a different mail 954 delivery agent (such as mail.local found in the sendmail 955 distribution). 956 957 On Digital UNIX 4.0 and later, Berkeley DB 1.85 is included with the 958 operating system and already has the ndbm.o module removed. However, 959 Digital has modified the original Berkeley DB db.h include file. 960 This results in the following warning while compiling map.c and udb.c: 961 962 cc: Warning: /usr/include/db.h, line 74: The redefinition of the macro 963 "__signed" conflicts with a current definition because the replacement 964 lists differ. The redefinition is now in effect. 965 #define __signed signed 966 ------------------------^ 967 968 This warning can be ignored. 969 970 Digital UNIX's linker checks /usr/ccs/lib/ before /usr/lib/. 971 If you have installed a new version of BIND in /usr/include 972 and /usr/lib, you will experience difficulties as Digital ships 973 libresolv.a in /usr/ccs/lib/ as well. Be sure to replace both 974 copies of libresolv.a. 975 976IRIX 977 The header files on SGI IRIX are completely prototyped, and as 978 a result you can sometimes get some warning messages during 979 compilation. These can be ignored. There are two errors in 980 deliver only if you are using gcc, both of the form ``warning: 981 passing arg N of `execve' from incompatible pointer type''. 982 Also, if you compile with -DNIS, you will get a complaint 983 about a declaration of struct dom_binding in a prototype 984 when compiling map.c; this is not important because the 985 function being prototyped is not used in that file. 986 987 In order to compile sendmail you will have had to install 988 the developers' option in order to get the necessary include 989 files. 990 991 If you compile with -lmalloc (the fast memory allocator), you may 992 get warning messages such as the following: 993 994 ld32: WARNING 85: definition of _calloc in /usr/lib32/libmalloc.so 995 preempts that definition in /usr/lib32/mips3/libc.so. 996 ld32: WARNING 85: definition of _malloc in /usr/lib32/libmalloc.so 997 preempts that definition in /usr/lib32/mips3/libc.so. 998 ld32: WARNING 85: definition of _realloc in /usr/lib32/libmalloc.so 999 preempts that definition in /usr/lib32/mips3/libc.so. 1000 ld32: WARNING 85: definition of _free in /usr/lib32/libmalloc.so 1001 preempts that definition in /usr/lib32/mips3/libc.so. 1002 ld32: WARNING 85: definition of _cfree in /usr/lib32/libmalloc.so 1003 preempts that definition in /usr/lib32/mips3/libc.so. 1004 1005 These are unavoidable and innocuous -- just ignore them. 1006 1007 According to Dave Sill <de5@ornl.gov>, there is a version of the 1008 Berkeley DB library patched to run on Irix 6.2 available from 1009 http://reality.sgi.com/ariel/freeware/#db . 1010 1011IRIX 6.x 1012 If you are using XFS filesystem, avoid using the -32 ABI switch to 1013 the cc compiler if possible. 1014 1015IRIX 6.4 1016 The IRIX 6.5.4 version of /bin/m4 does not work properly with 1017 sendmail. Either install fw_m4.sw.m4 off the Freeware_May99 CD and 1018 use /usr/freeware/bin/m4 or install and use GNU m4. 1019 1020NeXT or NEXTSTEP 1021 NEXTSTEP 3.3 and earlier ship with the old DBM library. Also, 1022 Berkeley DB does not currently run on NEXTSTEP. 1023 1024 If you are compiling on NEXTSTEP, you will have to create an 1025 empty file "unistd.h" and create a file "dirent.h" containing: 1026 1027 #include <sys/dir.h> 1028 #define dirent direct 1029 1030 (devtools/OS/NeXT should try to do both of these for you.) 1031 1032 Apparently, there is a bug in getservbyname on Nextstep 3.0 1033 that causes it to fail under some circumstances with the 1034 message "SYSERR: service "smtp" unknown" logged. You should 1035 be able to work around this by including the line: 1036 1037 OOPort=25 1038 1039 in your .cf file. 1040 1041BSDI (BSD/386) 1.0, NetBSD 0.9, FreeBSD 1.0 1042 The "m4" from BSDI won't handle the config files properly. 1043 I haven't had a chance to test this myself. 1044 1045 The M4 shipped in FreeBSD and NetBSD 0.9 don't handle the config 1046 files properly. One must use either GNU m4 1.1 or the PD-M4 1047 recently posted in comp.os.386bsd.bugs (and maybe others). 1048 NetBSD-current includes the PD-M4 (as stated in the NetBSD file 1049 CHANGES). 1050 1051 FreeBSD 1.0 RELEASE has uname(2) now. Use -DUSEUNAME in order to 1052 use it (look into devtools/OS/FreeBSD). NetBSD-current may have 1053 it too but it has not been verified. 1054 1055 The latest version of Berkeley DB uses a different naming 1056 scheme than the version that is supplied with your release. This 1057 means you will be able to use the current version of Berkeley DB 1058 with sendmail as long you use the new db.h when compiling 1059 sendmail and link it against the new libdb.a or libdb.so. You 1060 should probably keep the original db.h in /usr/include and the 1061 new db.h in /usr/local/include. 1062 10634.3BSD 1064 If you are running a "virgin" version of 4.3BSD, you'll have 1065 a very old resolver and be missing some header files. The 1066 header files are simple -- create empty versions and everything 1067 will work fine. For the resolver you should really port a new 1068 version (4.8.3 or later) of the resolver; 4.9 is available on 1069 gatekeeper.DEC.COM in pub/BSD/bind/4.9. If you are really 1070 determined to continue to use your old, buggy version (or as 1071 a shortcut to get sendmail working -- I'm sure you have the 1072 best intentions to port a modern version of BIND), you can 1073 copy ../contrib/oldbind.compat.c into sendmail and add 1074 oldbind.compat.o to OBJADD in the Makefile. 1075 1076A/UX 1077 Date: Tue, 12 Oct 1993 18:28:28 -0400 (EDT) 1078 From: "Eric C. Hagberg" <hagberg@med.cornell.edu> 1079 Subject: Fix for A/UX ndbm 1080 1081 I guess this isn't really a sendmail bug, however, it is something 1082 that A/UX users should be aware of when compiling sendmail 8.6. 1083 1084 Apparently, the calls that sendmail is using to the ndbm routines 1085 in A/UX 3.0.x contain calls to "broken" routines, in that the 1086 aliases database will break when it gets "just a little big" 1087 (sorry I don't have exact numbers here, but it broke somewhere 1088 around 20-25 aliases for me.), making all aliases non-functional 1089 after exceeding this point. 1090 1091 What I did was to get the gnu-dbm-1.6 package, compile it, and 1092 then re-compile sendmail with "-lgdbm", "-DNDBM", and using the 1093 ndbm.h header file that comes with the gnu-package. This makes 1094 things behave properly. 1095 [NOTE: see comment above about GDBM] 1096 1097 I suppose porting the New Berkeley DB package is another route, 1098 however, I made a quick attempt at it, and found it difficult 1099 (not easy at least); the gnu-dbm package "configured" and 1100 compiled easily. 1101 1102 [NOTE: Berkeley DB version 2.X runs on A/UX and can be used for 1103 database maps.] 1104 1105SCO Unix 1106 From: Thomas Essebier <tom@stallion.oz.au> 1107 Organisation: Stallion Technologies Pty Ltd. 1108 1109 It will probably help those who are trying to configure sendmail 8.6.9 1110 to know that if they are on SCO, they had better set 1111 OI-dnsrch 1112 or they will core dump as soon as they try to use the resolver. 1113 ie. although SCO has _res.dnsrch defined, and is kinda BIND 4.8.3, it 1114 does not inititialise it, nor does it understand 'search' in 1115 /etc/named.boot. 1116 - sigh - 1117 1118 According to SCO, the m4 which ships with UnixWare 2.1.2 is broken. 1119 We recommend installing GNU m4 before attempting to build sendmail. 1120 1121DG/UX 1122 Doug Anderson <dlander@afterlife.ncsc.mil> has successfully run 1123 V8 on the DG/UX 5.4.2 and 5.4R3.x platforms under heavy usage. 1124 Originally, the DG /bin/mail program wasn't compatible with 1125 the V8 sendmail, since the DG /bin/mail requires the environment 1126 variable "_FORCE_MAIL_LOCAL_=yes" be set. Version 8.7 now includes 1127 this in the environment before invoking the local mailer. Some 1128 have used procmail to avoid this problem in the past. It works 1129 but some have experienced file locking problems with their DG/UX 1130 ports of procmail. 1131 1132Apollo DomainOS 1133 If you are compiling on Apollo, you will have to create an empty 1134 file "unistd.h" (for DomainOS 10.3 and earlier) and create a file 1135 "dirent.h" containing: 1136 1137 #include <sys/dir.h> 1138 #define dirent direct 1139 1140 (devtools/OS/DomainOS will attempt to do both of these for you.) 1141 1142HP-UX 8.00 1143 Date: Mon, 24 Jan 1994 13:25:45 +0200 1144 From: Kimmo Suominen <Kimmo.Suominen@lut.fi> 1145 Subject: 8.6.5 w/ HP-UX 8.00 on s300 1146 1147 Just compiled and fought with sendmail 8.6.5 on a HP9000/360 (ie. a 1148 series 300 machine) running HP-UX 8.00. 1149 1150 I was getting segmentation fault when delivering to a local user. 1151 With debugging I saw it was faulting when doing _free@libc... *sigh* 1152 It seems the new implementation of malloc on s300 is buggy as of 8.0, 1153 so I tried out the one in -lmalloc (malloc(3X)). With that it seems 1154 to work just dandy. 1155 1156 When linking, you will get the following error: 1157 1158 ld: multiply defined symbol _freespace in file /usr/lib/libmalloc.a 1159 1160 but you can just ignore it. You might want to add this info to the 1161 README file for the future... 1162 1163Linux 1164 Something broke between versions 0.99.13 and 0.99.14 of Linux: 1165 the flock() system call gives errors. If you are running .14, 1166 you must not use flock. You can do this with -DHASFLOCK=0. 1167 1168 Around the inclusion of bind-4.9.3 & Linux libc-4.6.20, the 1169 initialization of the _res structure changed. If /etc/hosts.conf 1170 was configured as "hosts, bind" the resolver code could return 1171 "Name server failure" errors. This is supposedly fixed in 1172 later versions of libc (>= 4.6.29?), and later versions of 1173 sendmail (> 8.6.10) try to work around the problem. 1174 1175 Some older versions (< 4.6.20?) of the libc/include files conflict 1176 with sendmail's version of cdefs.h. Deleting sendmail's version 1177 on those systems should be non-harmful, and new versions don't care. 1178 1179 Sendmail assumes that libc has snprintf, which has been true since 1180 libc 4.7.0. If you are running an older version, you will need to 1181 use -DHASSNPRINTF=0 in the Makefile. If may be able to use -lbsd 1182 (which includes snprintf) instead of turning this off on versions 1183 of libc between 4.4.4 and 4.7.0 (snprintf improves security, so 1184 you want to use this if at all possible). 1185 1186 NOTE ON LINUX & BIND: By default, the Makefile generated for Linux 1187 includes header files in /usr/local/include and libraries in 1188 /usr/local/lib. If you've installed BIND on your system, the header 1189 files typically end up in the search path and you need to add 1190 "-lresolv" to the LIBS line in your Makefile. Really old versions 1191 may need to include "-l44bsd" as well (particularly if the link phase 1192 complains about missing strcasecmp, strncasecmp or strpbrk). 1193 Complaints about an undefined reference to `__dn_skipname' in 1194 domain.o are a sure sign that you need to add -lresolv to LIBS. 1195 Newer versions of Linux are basically threaded BIND, so you may or 1196 may not see complaints if you accidentally mix BIND 1197 headers/libraries with virginal libc. If you have BIND headers in 1198 /usr/local/include (resolv.h, etc) you *should* be adding -lresolv 1199 to LIBS. Data structures may change and you'd be asking for a 1200 core dump. 1201 1202 A number of problems have been reported regarding the Linux 2.2.0 1203 kernel. So far, these problems have been tracked down to syslog() 1204 and DNS resolution. We believe the problem is with the poll() 1205 implementation in the Linux 2.2.0 kernel and poll()-aware versions 1206 of glib (at least up to 2.0.111). 1207 1208 Some pre-glibc distributions of Linux include a syslog.h that does 1209 not work properly with SFIO. You can fix this by adding 1210 "#include <syslog.h>" to the SFIO version of stdio.h as the very 1211 first line. 1212 1213AIX 4.X 1214 The AIX 4.X linker uses library paths specified during compilation 1215 using -L for run-time shared library searches. Therefore, it is 1216 vital that relative and unsafe directory paths not be using when 1217 compiling sendmail. Because of this danger, by default, compiles 1218 on AIX use the -blibpath option to limit shared libraries to 1219 /usr/lib and /lib. If you need to allow more directories, such as 1220 /usr/local/lib, modify your devtools/Site/site.AIX.4.2.m4, 1221 site.AIX.4.3.m4, and/or site.AIX.4.x.m4 file(s) and set confLDOPTS 1222 approriately. For example: 1223 1224 define(`confLDOPTS', `-blibpath:/usr/lib:/lib:/usr/local/lib') 1225 1226 Be sure to only add (safe) system directories. 1227 1228 The AIX version of GNU ld also exhibits this problem. If you are 1229 using that version, instead of -blibpath, use its -rpath option. 1230 For example: 1231 1232 gcc -Wl,-rpath /usr/lib -Wl,-rpath /lib -Wl,-rpath /usr/local/lib 1233 1234AIX 4.3.3 1235 From: Valdis.Kletnieks@vt.edu 1236 Date: Sun, 02 Jul 2000 03:58:02 -0400 1237 1238 Under AIX 4.3.3, after applying bos.adt.include 4.3.3.12 to close the 1239 BIND 8.2.2 security holes, you can no lonber build with -DNETINET6 1240 because they changed the value of __RES in resolv.h but failed to 1241 actually provide the API changes that the change implied. 1242 1243 Workarounds: 1244 1) Compile without -DNETINET6 1245 2) Build against a real Bind 8.2.2 include/lib tree 1246 3) Wait for IBM to fix it 1247 1248AIX 4.2 1249 The AIX m4 implements a different mechanism for ifdef which is 1250 inconsistent with other versions of m4. Therefore, it will not 1251 work properly with the sendmail Build architecture or m4 1252 configuration method. To work around this problem, please use 1253 GNU m4 from ftp://ftp.gnu.org/pub/gnu/. 1254 1255AIX 3.x 1256 This version of sendmail does not support MB, MG, and MR resource 1257 records, which are supported by AIX sendmail. 1258 1259 Several people have reported that the IBM-supplied named returns 1260 fairly random results -- the named should be replaced. It is not 1261 necessary to replace the resolver, which will simplify installation. 1262 A new BIND resolver can be found at http://www.isc.org/isc/. 1263 1264AIX 3.1.x 1265 The supplied load average code only works correctly for AIX 3.2.x. 1266 For 3.1, use -DLA_TYPE=LA_SUBR and get the latest ``monitor'' 1267 package by Jussi Maki <jmaki@hut.fi> from ftp.funet.fi in the 1268 directory pub/unix/AIX/rs6000/monitor-1.12.tar.Z; use the loadavgd 1269 daemon, and the getloadavg subroutine supplied with that package. 1270 If you don't care about load average throttling, just turn off 1271 load average checking using -DLA_TYPE=LA_ZERO. 1272 1273AIX 2.2.1 1274 Date: Mon Dec 4 14:14:56 CST 1995 1275 From: Mark Whetzel <markw@antimatr.houston.tx.us> 1276 Subject: Porting sendmail 8.7.2 to AIX V2 on the RT. 1277 1278 This version of sendmail does not support MB, MG, and MR resource 1279 records, which are supported by AIX sendmail. 1280 1281 AIX V2 on the RT does not have 'paths.h'. Create a null 1282 file in the 'obj' directory to remove this compile error. 1283 1284 A patch file is needed to get the BSD 'db' library to compile 1285 for AIX/RT. I have sent the necessary updates to the author, 1286 but they may not be immediately available. 1287 [NOTE: Berkeley DB version 2.X runs on AIX/RT.] 1288 1289 The original AIX/RT resolver libraries are very old, and you 1290 should get the latest BIND to replace it. The 4.8.3 version 1291 has been tested, but 4.9.x is out and should work. 1292 1293 To make the load average code work correctly requires an 1294 external routine, as the kernel does not maintain system 1295 load averages, similar to AIX V3.1.x. A reverse port of the 1296 older 1.05 'monitor' load average daemon code written by 1297 Jussi Maki that will work on AIX V2 for the RT is available 1298 by E-mail to Mark Whetzel <markw@antimatr.houston.tx.us>. 1299 That code depends on an external daemon to collect system 1300 load information, and the external routine 'getloadavg', 1301 that will return that information. The 'LA_SUBR' define 1302 will handle this for AIX V2 on the RT. 1303 1304 Note: You will have to change devtools/OS/AIX.2 to correctly 1305 point to the locatons of the updated BIND source tree and 1306 the location of the 'newdb' tree and library location. 1307 You will also have to change devtools/OS/AIX.2 to know 1308 about the location of the 'getloadavg' routine if you use 1309 the LA_SUBR define. 1310 1311RISC/os 1312 RISC/os from MIPS is a merged AT&T/Berkeley system. When you 1313 compile on that platform you will get duplicate definitions 1314 on many files. You can ignore these. 1315 1316System V Release 4 Based Systems 1317 There is a single devtools OS that is intended for all SVR4-based 1318 systems (built from devtools/OS/SVR4). It defines __svr4__, 1319 which is predefined by some compilers. If your compiler already 1320 defines this compile variable, you can delete the definition from 1321 the generated Makefile or create a devtools/Site/site.config.m4 1322 file. 1323 1324 It's been tested on Dell Issue 2.2. 1325 1326DELL SVR4 1327 Date: Mon, 06 Dec 1993 10:42:29 EST 1328 From: "Kimmo Suominen" <kim@grendel.lut.fi> 1329 Message-ID: <2d0352f9.lento29@lento29.UUCP> 1330 To: eric@cs.berkeley.edu 1331 Cc: sendmail@cs.berkeley.edu 1332 Subject: Notes for DELL SVR4 1333 1334 Eric, 1335 1336 Here are some notes for compiling Sendmail 8.6.4 on DELL SVR4. I ran 1337 across these things when helping out some people who contacted me by 1338 e-mail. 1339 1340 1) Use gcc 2.4.5 (or later?). Dell distributes gcc 2.1 with their 1341 Issue 2.2 Unix. It is too old, and gives you problems with 1342 clock.c, because sigset_t won't get defined in <sys/signal.h>. 1343 This is due to a problematic protection rule in there, and is 1344 fixed with gcc 2.4.5. 1345 1346 2) If you don't use the new Berkeley DB (-DNEWDB), then you need 1347 to add "-lc -lucb" to the libraries to link with. This is because 1348 the -ldbm distributed by Dell needs the bcopy, bcmp and bzero 1349 functions. It is important that you specify both libraries in 1350 the given order to be sure you only get the BSTRING functions 1351 from the UCB library (and not the signal routines etc.). 1352 1353 3) Don't leave out "-lelf" even if compiling with "-lc -lucb". 1354 The UCB library also has another copy of the nlist routines, 1355 but we do want the ones from "-lelf". 1356 1357 If anyone needs a compiled gcc 2.4.5 and/or a ported DB library, they 1358 can use anonymous ftp to fetch them from lut.fi in the /kim directory. 1359 They are copies of what I use on grendel.lut.fi, and offering them 1360 does not imply that I would also support them. I have sent the DB 1361 port for SVR4 back to Keith Bostic for inclusion in the official 1362 distribution, but I haven't heard anything from him as of today. 1363 1364 - gcc-2.4.5-svr4.tar.gz (gcc 2.4.5 and the corresponding libg++) 1365 - db-1.72.tar.gz (with source, objects and a installed copy) 1366 1367 Cheers 1368 + Kim 1369 -- 1370 * Kimmo.Suominen@lut.fi * SysVr4 enthusiast at GRENDEL.LUT.FI * 1371 * KIM@FINFILES.BITNET * Postmaster and Hostmaster at LUT.FI * 1372 * + 358 200 865 718 * Unix area moderator at NIC.FUNET.FI * 1373 1374ConvexOS 10.1 and below 1375 In order to use the name server, you must create the file 1376 /etc/use_nameserver. If this file does not exist, the call 1377 to res_init() will fail and you will have absolutely no 1378 access to DNS, including MX records. 1379 1380Amdahl UTS 2.1.5 1381 In order to get UTS to work, you will have to port BIND 4.9. 1382 The vendor's BIND is reported to be ``totally inadequate.'' 1383 See sendmail/contrib/AmdahlUTS.patch for the patches necessary 1384 to get BIND 4.9 compiled for UTS. 1385 1386UnixWare 1387 According to Alexander Kolbasov <sasha@unitech.gamma.ru>, 1388 the m4 on UnixWare 2.0 (still in Beta) will core dump on the 1389 config files. GNU m4 and the m4 from UnixWare 1.x both work. 1390 1391 According to Larry Rosenman <ler@lerami.lerctr.org>: 1392 1393 UnixWare 2.1.[23]'s m4 chokes (not obviously) when 1394 processing the 8.9.0 cf files. 1395 1396 I had a LOCAL_RULE_0 that wound up AFTER the 1397 SBasic_check_rcpt rules using the SCO supplied M4. 1398 GNU M4 works fine. 1399 1400UNICOS 8.0.3.4 1401 Some people have reported that the -O flag on UNICOS can cause 1402 problems. You may want to turn this off if you have problems 1403 running sendmail. Reported by Jerry G. DeLapp <jgd@acl.lanl.gov>. 1404 1405GNU getopt 1406 I'm told that GNU getopt has a problem in that it gets confused 1407 by the double call. Use the version in conf.c instead. 1408 1409BIND 4.9.2 and Ultrix 1410 If you are running on Ultrix, be sure you read conf/Info.Ultrix 1411 in the BIND distribution very carefully -- there is information 1412 in there that you need to know in order to avoid errors of the 1413 form: 1414 1415 /lib/libc.a(gethostent.o): sethostent: multiply defined 1416 /lib/libc.a(gethostent.o): endhostent: multiply defined 1417 /lib/libc.a(gethostent.o): gethostbyname: multiply defined 1418 /lib/libc.a(gethostent.o): gethostbyaddr: multiply defined 1419 1420 during the link stage. 1421 1422BIND 8.X 1423 BIND 8.X returns HOST_NOT_FOUND instead of TRY_AGAIN on temporary 1424 DNS failures when trying to find the hostname associated with an IP 1425 address (gethostbyaddr()). This can cause problems as 1426 $&{client_name} based lookups in class R ($=R) and the access 1427 database won't succeed. 1428 1429 This will be fixed in BIND 8.2.1. For earlier versions, this can 1430 be fixed by making "dns" the last name service queried for host 1431 resolution in /etc/irs.conf: 1432 1433 hosts local continue 1434 hosts dns 1435 1436strtoul 1437 Some compilers (notably gcc) claim to be ANSI C but do not 1438 include the ANSI-required routine "strtoul". If your compiler 1439 has this problem, you will get an error in srvrsmtp.c on the 1440 code: 1441 1442 # ifdef defined(__STDC__) && !defined(BROKEN_ANSI_LIBRARY) 1443 e->e_msgsize = strtoul(vp, (char **) NULL, 10); 1444 # else 1445 e->e_msgsize = strtol(vp, (char **) NULL, 10); 1446 # endif 1447 1448 You can use -DBROKEN_ANSI_LIBRARY to get around this problem. 1449 1450Listproc 6.0c 1451 Date: 23 Sep 1995 23:56:07 GMT 1452 Message-ID: <95925101334.~INN-AUMa00187.comp-news@dl.ac.uk> 1453 From: alansz@mellers1.psych.berkeley.edu (Alan Schwartz) 1454 Subject: Listproc 6.0c + Sendmail 8.7 [Helpful hint] 1455 1456 Just upgraded to sendmail 8.7, and discovered that listproc 6.0c 1457 breaks, because it, by default, sends a blank "HELO" rather than 1458 a "HELO hostname" when using the 'system' or 'telnet' mailmethod. 1459 1460 The fix is to include -DZMAILER in the compilation, which will 1461 cause it to use "HELO hostname" (which Z-mail apparently requires 1462 as well. :) 1463 1464OpenSSL 1465 OpenSSL versions prior to 0.9.6 use a macro named Free which 1466 conflicts with existing macro names on some platforms, such as 1467 AIX. 1468 1469PH 1470 PH support is provided by Mark Roth <roth@uiuc.edu>. The map is 1471 described at http://www-wsg.cso.uiuc.edu/sendmail/patches/ . 1472 Please contact Mark Roth for support and questions regarding the 1473 map. 1474 1475TCP Wrappers 1476 If you are using -DTCPWRAPPERS to get TCP Wrappers support you will 1477 also need to install libwrap.a and modify your site.config.m4 file 1478 or the generated Makefile to include -lwrap in the LIBS line 1479 (make sure that INCDIRS and LIBDIRS point to where the tcpd.h and 1480 libwrap.a can be found). 1481 1482 TCP Wrappers is available at ftp://ftp.porcupine.org/pub/security/. 1483 1484 If you have alternate MX sites for your site, be sure that all of 1485 your MX sites reject the same set of hosts. If not, a bad guy whom 1486 you reject will connect to your site, fail, and move on to the next 1487 MX site, which will accept the mail for you and forward it on to you. 1488 1489Regular Expressions (MAP_REGEX) 1490 If sendmail linking fails with: 1491 1492 undefined reference to 'regcomp' 1493 1494 or sendmail gives an error about a regular expression with: 1495 1496 pattern-compile-error: : Operation not applicable 1497 1498 Your libc does not include a running version of POSIX-regex. Use 1499 librx or regex.o from the GNU Free Software Foundation, 1500 ftp://ftp.gnu.org/pub/gnu/rx-?.?.tar.gz or 1501 ftp://ftp.gnu.org/pub/gnu/regex-?.?.tar.gz. 1502 You can also use the regex-lib by Henry Spencer, 1503 ftp://ftp.funet.fi/pub/languages/C/spencer/regex.shar.gz 1504 Make sure, your compiler reads regex.h from the distribution, 1505 not from /usr/include, otherwise sendmail will dump a core. 1506 1507 1508+--------------+ 1509| MANUAL PAGES | 1510+--------------+ 1511 1512The manual pages have been written against the -man macros, and 1513should format correctly with any reasonable *roff. 1514 1515+-----------------+ 1516| DEBUGGING HOOKS | 1517+-----------------+ 1518 1519As of 8.6.5, sendmail daemons will catch a SIGUSR1 signal and log 1520some debugging output (logged at LOG_DEBUG severity). The 1521information dumped is: 1522 1523 * The value of the $j macro. 1524 * A warning if $j is not in the set $=w. 1525 * A list of the open file descriptors. 1526 * The contents of the connection cache. 1527 * If ruleset 89 is defined, it is evaluated and the results printed. 1528 1529This allows you to get information regarding the runtime state of the 1530daemon on the fly. This should not be done too frequently, since 1531the process of rewriting may lose memory which will not be recovered. 1532Also, ruleset 89 may call non-reentrant routines, so there is a small 1533non-zero probability that this will cause other problems. It is 1534really only for debugging serious problems. 1535 1536A typical formulation of ruleset 89 would be: 1537 1538 R$* $@ $>0 some test address 1539 1540 1541+-----------------------------+ 1542| DESCRIPTION OF SOURCE FILES | 1543+-----------------------------+ 1544 1545The following list describes the files in this directory: 1546 1547Build Shell script for building sendmail. 1548Makefile A convenience for calling ./Build. 1549Makefile.m4 A template for constructing a makefile based on the 1550 information in the devtools directory. 1551README This file. 1552TRACEFLAGS My own personal list of the trace flags -- not guaranteed 1553 to be particularly up to date. 1554alias.c Does name aliasing in all forms. 1555aliases.5 Man page describing the format of the aliases file. 1556arpadate.c A subroutine which creates ARPANET standard dates. 1557bf.h Buffered file I/O function declarations. 1558bf_portable.c Stub routines for systems lacking the Torek stdio library. 1559bf_portable.h Data structure and function declarations for bf_portable.c. 1560bf_torek.c Routines to implement memory-buffered file system using 1561 hooks provided by Torek stdio library. 1562bf_torek.h Data structure and function declarations for bf_torek.c. 1563clock.c Routines to implement real-time oriented functions 1564 in sendmail -- e.g., timeouts. 1565collect.c The routine that actually reads the mail into a temp 1566 file. It also does a certain amount of parsing of 1567 the header, etc. 1568conf.c The configuration file. This contains information 1569 that is presumed to be quite static and non- 1570 controversial, or code compiled in for efficiency 1571 reasons. Most of the configuration is in sendmail.cf. 1572conf.h Configuration that must be known everywhere. 1573convtime.c A routine to sanely process times. 1574daemon.c Routines to implement daemon mode. This version is 1575 specifically for Berkeley 4.1 IPC. 1576deliver.c Routines to deliver mail. 1577domain.c Routines that interface with DNS (the Domain Name 1578 System). 1579envelope.c Routines to manipulate the envelope structure. 1580err.c Routines to print error messages. 1581headers.c Routines to process message headers. 1582helpfile An example helpfile for the SMTP HELP command and -bt mode. 1583macro.c The macro expander. This is used internally to 1584 insert information from the configuration file. 1585mailq.1 Man page for the mailq command. 1586main.c The main routine to sendmail. This file also 1587 contains some miscellaneous routines. 1588makesendmail A convenience for calling ./Build. 1589map.c Support for database maps. 1590mci.c Routines that handle mail connection information caching. 1591milter.c MTA portions of the mail filter API. 1592mime.c MIME conversion routines. 1593newaliases.1 Man page for the newaliases command. 1594parseaddr.c The routines which do address parsing. 1595queue.c Routines to implement message queueing. 1596readcf.c The routine that reads the configuration file and 1597 translates it to internal form. 1598recipient.c Routines that manipulate the recipient list. 1599savemail.c Routines which save the letter on processing errors. 1600sendmail.8 Man page for the sendmail command. 1601sendmail.h Main header file for sendmail. 1602sfsasl.c I/O interface between SASL/TLS and the MTA using SFIO. 1603sfsasl.h Header file for sfsasl.c. 1604shmticklib.c Routines for shared memory counters. 1605srvrsmtp.c Routines to implement server SMTP. 1606stab.c Routines to manage the symbol table. 1607stats.c Routines to collect and post the statistics. 1608statusd_shm.h Data structure and function declarations for shmticklib.c. 1609sysexits.c List of error messages associated with error codes 1610 in sysexits.h. 1611sysexits.h List of error codes for systems that lack their own. 1612timers.c Routines to provide microtimers. 1613timers.h Data structure and function declarations for timers.h. 1614trace.c The trace package. These routines allow setting and 1615 testing of trace flags with a high granularity. 1616udb.c The user database interface module. 1617usersmtp.c Routines to implement user SMTP. 1618util.c Some general purpose routines used by sendmail. 1619version.c The version number and information about this 1620 version of sendmail. 1621 1622(Version $Revision: 8.263.2.1.2.19 $, last update $Date: 2000/07/15 17:35:18 $ ) 1623