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