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