1# Copyright (c) 1983, 1995 Eric P. Allman 2# Copyright (c) 1988 The Regents of the University of California. 3# All rights reserved. 4# 5# %sccs.include.redist.sh% 6# 7# @(#)READ_ME 8.85 (Berkeley) 05/05/95 8# 9 10This directory contains the source files for sendmail. 11 12For detailed instructions, please read the document ../doc/op.me: 13 14 eqn ../doc/op.me | pic | ditroff -me 15 16********************* 17!! DO NOT USE MAKE !! to compile sendmail -- instead, use the 18********************* "makesendmail" script located in the src 19directory. It will find an appropriate Makefile, and create an 20appropriate obj.* subdirectory so that multiplatform support 21works easily. 22 23The Makefile is for the new (4.4BSD) Berkeley make and uses syntax 24that is not recognized by older makes. It also has assumptions 25about the 4.4 file system layout built in. See below for details 26about other Makefiles. 27 28If you are porting to a new architecture for which there is no existing 29Makefile, you might start with Makefile.dist. This works on the old 30traditional make, but isn't customized for any particular architecture. 31 32 ************************************************** 33 ** Read below for more details of Makefiles. ** 34 ************************************************** 35 36************************************************************************** 37** IMPORTANT: DO NOT USE OPTIMIZATION (``-O'') IF YOU ARE RUNNING ** 38** GCC 2.4.x or 2.5.x. THERE IS A BUG IN THE GCC OPTIMIZER THAT ** 39** CAUSES SENDMAIL COMPILES TO FAIL MISERABLY. ** 40************************************************************************** 41 42Jim Wilson of Cygnus believes he has found the problem -- it will 43probably be fixed in GCC 2.5.6 -- but until this is verified, be 44very suspicious of gcc -O. 45 46This problem is reported to have been fixed in gcc 2.6. 47 48************************************************************************** 49** IMPORTANT: Read the appropriate paragraphs in the section on ** 50** ``Operating System and Compile Quirks''. ** 51************************************************************************** 52 53 54+-----------+ 55| MAKEFILES | 56+-----------+ 57 58By far, the easiest way to compile sendmail is to use the "makesendmail" 59script: 60 61 sh makesendmail 62 63This uses the "uname" command to figure out what architecture you are 64on and selects a proper Makefile accordingly. It also creates a 65subdirectory per object format, so that multiarchitecture support is 66easy. In general this should be all you need. However, if for some 67reason this doesn't work (e.g., NeXT systems don't have the "uname" 68command) you may have to set up your compile environment by hand. 69 70The "Makefile"s in these directories are from 4.4 BSD, and hence 71really only work properly if you are on a 4.4 system. In particular, 72they use new syntax that will not be recognized on old make programs, 73and some of them do things like ``.include ../../Makefile.inc'' to 74pick up some system defines. If you are getting sendmail separately, 75these files won't be included in the distribution, as they are 76outside of the sendmail tree. 77 78Instead, you should use one of the other Makefiles, such as 79Makefile.SunOS for a SunOS system, and so forth. These should 80work with the version of make that is appropriate for that 81system. All other Makefiles are in the "src/Makefiles" subdirectory. 82They use the version of make that is native for that system. These 83are the Makefiles that I use, and they have "Berkeley quirks" in them. 84I can't guarantee that they will work unmodified in your environment. 85In particular, Many of them include -I/usr/sww/include/db and 86-L/usr/sww/lib -- these are Berkeley's locations in the ``Software 87Warehouse'' for the new database libraries, described below. You don't 88have to remove these definitions if you don't have these directories, 89but you may have to remove -DNEWDB from the DBMDEF definition. 90 91Please look for an appropriate Makefile before you start trying to 92compile with Makefile or Makefile.dist. 93 94If you want to port the new Berkeley make, you can get it from 95ftp.uu.net in the directory /systems/unix/bsd-sources/usr.bin/make. 96Diffs and instructions for building this version of make under 97SunOS 4.1.x are available on ftp.css.itd.umich.edu in 98/pub/systems/sun/Net2-make.sun4.diff.Z. Diffs and instructions 99for building this version of make under IBM AIX 3.2.4 are available 100on ftp.uni-stuttgart.de in /sw/src/patches/bsd-make-rus-patches. 101For Ultrix, try ftp.vix.com:~ftp/pub/patches/pmake-for-ultrix.Z. 102Paul Southworth <pauls@umich.edu> published a description of porting 103this make in comp.unix.bsd. 104 105The complete text of the Makefile.inc that is in the parent of the 106sendmail directory is: 107 108 # @(#)Makefile.inc 8.1 (Berkeley) 6/6/93 109 110 BINDIR?= /usr/sbin 111 112 113+----------------------+ 114| DATABASE DEFINITIONS | 115+----------------------+ 116 117There are several database formats that can be used for the alias files 118and for general maps. When used for alias files they interact in an 119attempt to be back compatible. 120 121The three options are NEWDB (the new Berkeley DB package), NDBM (the 122older DBM implementation -- the very old V7 implementation is no 123longer supported), and NIS (Network Information Services). Used alone 124these just include the support they indicate. [If you are using NEWDB, 125get the latest version from FTP.CS.Berkeley.EDU in /ucb/4bsd/db.tar.Z 126(or db.tar.gz). DO NOT use the version from the Net2 distribution! 127However, if you are on BSD/386 or 386BSD-based systems, use the one 128that already exists on your system. You may need to #define OLD_NEWDB 1291 to do this.] 130 131[NOTE WELL: it is CRITICAL that you remove ndbm.o from libdb.a and 132ndbm.h from the appropriate include directories if you want to get 133ndbm support. These files OVERRIDE calls to ndbm routines -- in 134particular, if you leave ndbm.h in, you can find yourself using 135the new db package even if you don't define NEWDB.] 136 137If NEWDB and NDBM are defined (but not NIS), then sendmail will read 138NDBM format alias files, but the next time a newaliases is run the 139format will be converted to NEWDB; that format will be used forever 140more. This is intended as a transition feature. [Note however that 141the NEWDB library also catches and maps NDBM calls; you will have to 142back out this feature to get this to work. See ``Quirks'' section 143below for details.] 144 145If all three are defined, sendmail operates as described above, and also 146looks for the file /var/yp/Makefile. If it exists, newaliases will 147build BOTH the NEWDB and NDBM format alias files. However, it will 148only use the NEWDB file; the NDBM format file is used only by the 149NIS subsystem. 150 151If NDBM and NIS are defined (regardless of the definition of NEWDB 152or the existance of /var/yp/Makefile), sendmail adds the special 153tokens "YP_LAST_MODIFIED" and "YP_MASTER_NAME", both of which are 154required if the NDBM file is to be used as an NIS map. 155 156There is also preliminary support for NIS+ (-DNISPLUS), Hesiod 157(-DHESIOD), and NetInfo (-DNETINFO). These have not been well 158tested. 159 160All of -DNEWDB, -DNDBM, -DNIS, -DNISPLUS, -DHESIOD, and -DNETINFO are 161normally defined in the DBMDEF line in the Makefile. 162 163 164+---------------+ 165| COMPILE FLAGS | 166+---------------+ 167 168Whereever possible, I try to make sendmail pull in the correct 169compilation options needed to compile on various environments based on 170automatically defined symbols. Some machines don't seem to have useful 171symbols availble, requiring the following compilation flags in the 172Makefile: 173 174SOLARIS Define this if you are running Solaris 2.0 or higher. 175SOLARIS_2_3 Define this if you are running Solaris 2.3 or higher. 176SUNOS403 Define this if you are running SunOS 4.0.3. 177NeXT Define this if you are on a NeXT box. (This one may 178 be pre-defined for you.) There are other hacks you 179 have to make -- see below. 180_AIX3 Define this if you are IBM AIX 3.x. 181RISCOS Define this if you are running RISC/os from MIPS. 182IRIX Define this if you are running IRIX from SGI. 183_SCO_unix_ Define this if you are on SCO UNIX. 184_SCO_unix_4_2 Define this if you are on SCO Open Server 3.2v4. 185DGUX Define this if you are on DG/UX 5.4.3 or later 186DGUX_5_4_2 Define this if you are on DG/UX systems prior to 5.4.3. 187NonStop_UX_BXX Define this if you are on a Tandem NonStop-UX release 188 Bxx system. 189IRIX64 Define this if you are on an IRIX64 system. 190 191If you are a system that sendmail has already been ported to, you 192probably won't have to touch these. But if you are porting, you may 193have to tweak the following compilation flags in conf.h in order to 194get it to compile and link properly: 195 196SYSTEM5 Adjust for System V (not necessarily Release 4). 197SYS5SIGNALS Use System V signal semantics -- the signal handler 198 is automatically dropped when the signal is caught. 199 If this is not set, use POSIX/BSD semantics, where the 200 signal handler stays in force until an exec or an 201 explicit delete. Implied by SYSTEM5. 202SYS5SETPGRP Use System V setpgrp() semantics. Implied by SYSTEM5. 203HASFLOCK Set this if you prefer to use the flock(2) system call 204 rather than using fcntl-based locking. Fcntl locking 205 has some semantic gotchas, but many vendor systems 206 also interface it to lockd(8) to do NFS-style locking. 207 For this reason, this should not be set unless you 208 don't have an alternative. 209HASUNAME Set if you have the "uname" system call. Implied by 210 SYSTEM5. 211HASUNSETENV Define this if your system library has the "unsetenv" 212 subroutine. 213HASSETSID Define this if you have the setsid(2) system call. This 214 is implied if your system appears to be POSIX compliant. 215HASINITGROUPS Define this if you have the initgroups(3) routine. 216HASSETVBUF Define this if you have the setvbuf(3) library call. 217 If you don't, setlinebuf will be used instead. This 218 defaults on if your compiler defines __STDC__. 219HASSETREUID Define this if you have setreuid(2) ***AND*** root can 220 use setreuid to change to an arbitrary user. This second 221 condition is not satisfied on AIX 3.x. You may find that 222 your system has setresuid(2), (for example, on HP-UX) in 223 which case you will also have to #define setreuid(r, e) 224 to be the appropriate call. Some systems (such as Solaris) 225 have a compatibility routine that doesn't work properly, 226 but may have "saved user ids" properly implemented so you 227 can ``#define setreuid(r, e) seteuid(e)'' and have it work. 228 The important thing is that you have a call that will set 229 the effective uid independently of the real or saved uid 230 and be able to set the effective uid back again when done. 231 There's a test program in ../test/t_setreuid.c that will 232 try things on your system. Setting this improves the 233 security, since sendmail doesn't have to read .forward 234 and :include: files as root. There are certain attacks 235 that may be unpreventable without this call. 236HASLSTAT Define this if you have symbolic links (and thus the 237 lstat(2) system call). This improves security. Unlike 238 most other options, this one is on by default, so you 239 need to #undef it in conf.h if you don't have symbolic 240 links (these days everyone does). 241HASSETRLIMIT Define this to 1 if you have the setrlimit(2) syscall. 242 You can define it to 0 to force it off. It is assumed 243 if you are running a BSD-like system. 244HASULIMIT Define this if you have the ulimit(2) syscall (System V 245 style systems). HASSETRLIMIT overrides, as it is more 246 general. 247NEEDGETOPT Define this if you need a reimplementation of getopt(3). 248 On some systems, getopt does very odd things if called 249 to scan the arguments twice. This flag will ask sendmail 250 to compile in a local version of getopt that works 251 properly. 252NEEDSTRTOL Define this if your standard C library does not define 253 strtol(3). This will compile in a local version. 254NEEDVPRINTF Define this if your standard C library does not define 255 vprintf(3). Note that the resulting fake implementation 256 is not very elegant and may not even work on some 257 architectures. 258NEEDFSYNC Define this if your standard C library does not define 259 fsync(2). This will try to simulate the operation using 260 fcntl(2); if that is not available it does nothing, which 261 isn't great, but at least it compiles and runs. 262HASGETUSERSHELL Define this to 1 if you have getusershell(3) in your 263 standard C library. If this is not defined, or is defined 264 to be 0, sendmail will scan the /etc/shells file (no 265 NIS-style support, defaults to /bin/sh and /bin/csh if 266 that file does not exist) to get a list of unrestricted 267 user shells. This is used to determine whether users 268 are allowed to forward their mail to a program or a file. 269GIDSET_T The type of entries in a gidset passed as the second 270 argument to getgroups(2). Historically this has been an 271 int, so this is the default, but some systems (such as 272 IRIX) pass it as a gid_t, which is an unsigned short. 273 This will make a difference, so it is important to get 274 this right! However, it is only an issue if you have 275 group sets. 276SLEEP_T The type returned by the system sleep() function. 277 Defaults to "unsigned int". Don't worry about this 278 if you don't have compilation problems. 279ARBPTR_T The type of an arbitrary pointer -- defaults to "void *". 280 If you are an very old compiler you may need to define 281 this to be "char *". 282LA_TYPE The type of load average your kernel supports. These 283 can be one of: 284 LA_ZERO (1) -- it always returns the load average as 285 "zero" (and does so on all architectures). 286 LA_SUBR (4) if you have the getloadavg(3) routine, 287 LA_MACH (5) to use MACH-style load averages (calls 288 processor_set_info()), 289 LA_PROCSTR (7) to read /proc/loadavg and interpret it 290 as a string representing a floating-point 291 number (Linux-style), 292 LA_FLOAT (3) if you read kmem and interpret the value 293 as a floating point number, 294 LA_INT (2) to interpret as a long integer, 295 LA_SHORT (6) to interpret as a short integer. 296 These last three have several other parameters that they 297 try to divine: the name of your kernel, the name of the 298 variable in the kernel to examine, the number of bits of 299 precision in a fixed point load average, and so forth. 300 In desperation, use LA_ZERO. The actual code is in 301 conf.c -- it can be tweaked if you are brave. 302SFS_TYPE Encodes how your kernel can locate the amount of free 303 space on a disk partition. This can be set to SFS_NONE 304 (0) if you have no way of getting this information, 305 SFS_USTAT (1) if you have the ustat(2) system call, 306 SFS_4ARGS (2) if you have a four-argument statfs(2) 307 system call (and the include file is <sys/statfs.h>), 308 SFS_VFS (3), SFS_MOUNT (4), SFS_STATFS (5) if you have 309 the two-argument statfs(2) system call with includes in 310 <sys/vfs.h>, <sys/mount.h>, or <sys/statfs.h> respectively, 311 or SFS_STATVFS (6) if you have the two-argument statvfs(2) 312 call. The default if nothing is defined is SFS_NONE. 313SFS_BAVAIL with SFS_4ARGS hou can also set SFS_BAVAIL to the field name 314 in the statfs structure that holds the useful information; 315 this defaults to f_bavail. 316SPT_TYPE Encodes how your system can display what a process is doing 317 on a ps(1) command (SPT stands for Set Process Title). Can 318 be set to: 319 SPT_NONE (0) -- Don't try to set the process title at all. 320 SPT_REUSEARGV (1) -- Pad out your argv with the information; 321 this is the default if none specified. 322 SPT_BUILTIN (2) -- The system library has setproctitle. 323 SPT_PSTAT (3) -- Use the PSTAT_SETCMD option to pstat(2) 324 to set the process title; this is used by HP-UX. 325 SPT_PSSTRINGS (4) -- Use the magic PS_STRINGS pointer (4.4BSD). 326SPT_PADCHAR Character used to pad the process title; if undefined, 327 the space character (0x20) is used. This is ignored if 328 SPT_TYPE != SPT_REUSEARGV 329ERRLIST_PREDEFINED 330 If set, assumes that some header file defines sys_errlist. 331 This may be needed if you get type conflicts on this 332 variable -- otherwise don't worry about it. 333WAITUNION The wait(2) routine takes a "union wait" argument instead 334 of an integer argument. This is for compatibility with 335 old versions of BSD. 336SCANF You can set this to extend the F command to accept a 337 scanf string -- this gives you a primitive parser for 338 class definitions -- BUT it can make you vulnerable to 339 core dumps if the target file is poorly formed. 340SYSLOG_BUFSIZE You can define this to be the size of the buffer that 341 syslog accepts. If it is not defined, it assumes a 342 1024-byte buffer. If the buffer is very small (under 343 256 bytes) the log message format changes -- each 344 e-mail message will log many more messages, since it 345 will log each piece of information as a separate line 346 in syslog. 347BROKEN_RES_SEARCH 348 On Ultrix (and maybe other systems?) if you use the 349 res_search routine with an unknown host name, it returns 350 -1 but sets h_errno to 0 instead of HOST_NOT_FOUND. If 351 you set this, sendmail considers 0 to be the same as 352 HOST_NOT_FOUND. 353NAMELISTMASK If defined, values returned by nlist(3) are masked 354 against this value before use -- a common value is 355 0x7fffffff to strip off the top bit. 356 357 358 359+-----------------------+ 360| COMPILE-TIME FEATURES | 361+-----------------------+ 362 363There are a bunch of features that you can decide to compile in, such 364as selecting various database packages and special protocol support. 365Several are assumed based on other compilation flags -- if you want to 366"un-assume" something, you probably need to edit conf.h. Compilation 367flags that add support for special features include: 368 369NDBM Include support for "new" DBM library for aliases and maps. 370 Normally defined in the Makefile. 371NEWDB Include support for Berkeley "db" package (hash & btree) 372 for aliases and maps. Normally defined in the Makefile. 373OLD_NEWDB If non-zero, the version of NEWDB you have is the old 374 one that does not include the "fd" call. This call was 375 added in version 1.5 of the Berkeley DB code. If you 376 use -DOLD_NEWDB=0 it forces you to use the new interface. 377NIS Define this to get NIS (YP) support for aliases and maps. 378 Normally defined in the Makefile. 379USERDB Include support for the User Information Database. Implied 380 by NEWDB in conf.h. 381IDENTPROTO Define this as 1 to get IDENT (RFC 1413) protocol support. 382 This is assumed unless you are running on Ultrix or 383 HP-UX, both of which have a problem in the UDP 384 implementation. You can define it to be 0 to explicitly 385 turn off IDENT protocol support. 386LOG Set this to get syslog(3) support. Defined by default 387 in conf.h. You want this if at all possible. 388NETINET Set this to get TCP/IP support. Defined by default 389 in conf.h. You probably want this. 390NETISO Define this to get ISO networking support. 391SMTP Define this to get the SMTP code. Implied by NETINET 392 or NETISO. 393NAMED_BIND Define this to get DNS (name daemon) support, including 394 MX support. The specs you must use this if you run 395 SMTP. Defined by default in conf.h. 396QUEUE Define this to get queueing code. Implied by NETINET 397 or NETISO; required by SMTP. This gives you other good 398 stuff -- it should be on. 399DAEMON Define this to get general network support. Implied by 400 NETINET or NETISO. Defined by default in conf.h. You 401 almost certainly want it on. 402MATCHGECOS Permit fuzzy matching of user names against the full 403 name (GECOS) field in the /etc/passwd file. This should 404 probably be on, since you can disable it from the config 405 file if you want to. Defined by default in conf.h. 406 407 408+---------------------+ 409| DNS/RESOLVER ISSUES | 410+---------------------+ 411 412Many systems have old versions of the resolver library. At a minimum, 413you should be running BIND 4.8.3; older versions may compile, but they 414have known bugs that should give you pause. 415 416Common problems in old versions include "undefined" errors for 417dn_skipname. 418 419Some people have had a problem with BIND 4.9; it uses some routines 420that it expects to be externally defined such as strerror(). It may 421help to link with "-l44bsd" to solve this problem. 422 423!PLEASE! be sure to link with the same version of the resolver as 424the header files you used -- some people have used the 4.9 headers 425and linked with BIND 4.8 or vice versa, and it doesn't work. 426Unfortunately, it doesn't fail in an obvious way -- things just 427subtly don't work. 428 429 430+-------------------------------------+ 431| OPERATING SYSTEM AND COMPILE QUIRKS | 432+-------------------------------------+ 433 434GCC 2.5.x problems *** IMPORTANT *** 435 Date: Mon, 29 Nov 93 19:08:44 PST 436 From: wilson@cygnus.com (Jim Wilson) 437 Message-Id: <9311300308.AA04608@cygnus.com> 438 To: kenner@vlsi1.ultra.nyu.edu 439 Subject: [cattelan@thebarn.com: gcc 2.5.4-2.5.5 -O bug] 440 Cc: cattelan@thebarn.com, rms@gnu.ai.mit.edu, sendmail@cs.berkeley.edu 441 442 This fixes a problem that occurs when gcc 2.5.5 is used to compile 443 sendmail 8.6.4 with optimization on a sparc. 444 445 Mon Nov 29 19:00:14 1993 Jim Wilson (wilson@sphagnum.cygnus.com) 446 447 * reload.c (find_reloads_toplev): Replace obsolete reference to 448 BYTE_LOADS_*_EXTEND with LOAD_EXTEND_OP. 449 450 *** clean-ss-931128/reload.c Sun Nov 14 16:20:01 1993 451 --- ss-931128/reload.c Mon Nov 29 18:52:55 1993 452 *************** find_reloads_toplev (x, opnum, type, ind 453 *** 3888,3894 **** 454 force a reload in that case. So we should not do anything here. */ 455 456 else if (regno >= FIRST_PSEUDO_REGISTER 457 ! #if defined(BYTE_LOADS_ZERO_EXTEND) || defined(BYTE_LOADS_SIGN_EXTEND) 458 && (GET_MODE_SIZE (GET_MODE (x)) 459 <= GET_MODE_SIZE (GET_MODE (SUBREG_REG (x)))) 460 #endif 461 --- 3888,3894 ---- 462 force a reload in that case. So we should not do anything here. */ 463 464 else if (regno >= FIRST_PSEUDO_REGISTER 465 ! #ifdef LOAD_EXTEND_OP 466 && (GET_MODE_SIZE (GET_MODE (x)) 467 <= GET_MODE_SIZE (GET_MODE (SUBREG_REG (x)))) 468 #endif 469 470 471SunOS 4.x (Solaris 1.x) 472 You may have to use -lresolv on SunOS. However, beware that 473 this links in a new version of gethostbyname that does not 474 understand NIS, so you must have all of your hosts in DNS. 475 476 Some people have reported problems with the SunOS version of 477 -lresolv and/or in.named, and suggest that you get a newer 478 version. The symptoms are delays when you connect to the 479 SMTP server on a SunOS machine or having your domain added to 480 addresses inappropriately. There is a version of BIND 481 version 4.9 on gatekeeper.DEC.COM in pub/BSD/bind/4.9. 482 483 There is substantial disagreement about whether you can make 484 this work with resolv+, which allows you to specify a search-path 485 of services. Some people report that it works fine, others 486 claim it doesn't work at all (including causing sendmail to 487 drop core when it tries to do multiple resolv+ lookups for a 488 single job). I haven't tried resolv+, as we use DNS exclusively. 489 490 Should you want to try resolv+, it is on ftp.uu.net in 491 /networking/ip/dns. 492 493 Apparently getservbyname() can fail under moderate to high 494 load under some circumstances. This will exhibit itself as 495 the message ``554 makeconnection: service "smtp" unknown''. 496 The problem has been traced to one or more blank lines in 497 /etc/services on the NIS server machine. Delete these 498 and it should work. This info is thanks to Brian Bartholomew 499 <bb@math.ufl.edu> of I-Kinetics, Inc. 500 501Solaris 2.x (SunOS 5.x) 502 To compile for Solaris, be sure you use -DSOLARIS. 503 504 To the best of my knowledge, Solaris does not have the 505 gethostbyname problem described above. However, it does 506 have another one: 507 508 From a correspondent: 509 510 For solaris 2.2, I have 511 512 hosts: files dns 513 514 in /etc/nsswitch.conf and /etc/hosts has to have the fully 515 qualified host name. I think "files" has to be before "dns" 516 in /etc/nsswitch.conf during bootup. 517 518 From another correspondent: 519 520 When running sendmail under Solaris, the gethostbyname() 521 hack in conf.c which should perform proper canonicalization 522 of host names could fail. Result: the host name is not 523 canonicalized despite the hack, and you'll have to define $j 524 and $m in sendmail.cf somewhere. 525 526 The reason could be that /etc/nsswitch.conf is improperly 527 configured (at least from sendmail's point of view). For 528 example, the line 529 530 hosts: files nisplus dns 531 532 will make gethostbyname() look in /etc/hosts first, then ask 533 nisplus, then dns. However, if /etc/hosts does not contain 534 the full canonicalized hostname, then no amount of 535 gethostbyname()s will work. 536 537 Solution (or rather, a workaround): Ask nisplus first, then 538 dns, then local files: 539 540 hosts: nisplus dns [NOTFOUND=return] files 541 542 The Solaris "syslog" function is apparently limited to something 543 about 90 characters because of a kernel limitation. If you have 544 source code, you can probably up this number. You can get patches 545 that fix this problem: the patch ids are: 546 547 Solaris 2.1 100834 548 Solaris 2.2 100999 549 Solaris 2.3 101318 550 551 Be sure you have the appropriate patch installed or you won't 552 see system logging. 553 554Ultrix 555 By default, the IDENT protocol is turned off on Ultrix. If you 556 are running Ultrix 4.4 or later, or if you have gotten a patch 557 the TCP problem for an earlier version of Ultrix, you can turn 558 IDENT on in the configuration file by setting the "ident" timeout 559 to 30 seconds. 560 561OSF/1 562 If you are compiling on OSF/1 (DEC Alpha), you must use 563 -L/usr/shlib (otherwise it core dumps on startup). You may also 564 need -mld to get the nlist() function, although some versions 565 apparently don't need this. 566 567 Also, the enclosed makefile removed /usr/sbin/smtpd; if you need 568 it, just create the link to the sendmail binary. 569 570IRIX 571 The header files on SGI IRIX are completely prototyped, and as 572 a result you can sometimes get some warning messages during 573 compilation. These can be ignored. There are two errors in 574 deliver only if you are using gcc, both of the form ``warning: 575 passing arg N of `execve' from incompatible pointer type''. 576 Also, if you compile with -DNIS, you will get a complaint 577 about a declaration of struct dom_binding in a prototype 578 when compiling map.c; this is not important because the 579 function being prototyped is not used in that file. 580 581 In order to compile sendmail you will have had to install 582 the developers' option in order to get the necessary include 583 files. 584 585NeXT 586 If you are compiling on NeXT, you will have to create an empty 587 file "unistd.h" and create a file "dirent.h" containing: 588 589 #include <sys/dir.h> 590 #define dirent direct 591 592 (The Makefile.NeXT should try to do both of these for you.) 593 594 Apparently, there is a bug in getservbyname on Nextstep 3.0 595 that causes it to fail under some circumstances with the 596 message "SYSERR: service "smtp" unknown" logged. You should 597 be able to work around this by including the line: 598 599 OOPort=25 600 601 in your .cf file. 602 603 You may have to use -DNeXT. 604 605BSDI (BSD/386) 1.0, NetBSD 0.9, FreeBSD 1.0 606 The "m4" from BSDI won't handle the config files properly. 607 I haven't had a chance to test this myself. 608 609 The M4 shipped in FreeBSD and NetBSD 0.9 don't handle the config 610 files properly. One must use either GNU m4 1.1 or the PD-M4 611 recently posted in comp.os.386bsd.bugs (and maybe others). 612 NetBSD-current includes the PD-M4 (as stated in the NetBSD file 613 CHANGES). 614 615 FreeBSD 1.0 RELEASE has uname(2) now. Use -DUSEUNAME in order to 616 use it (look into Makefile.FreeBSD). NetBSD-current may have 617 it too but it has not been verified. 618 619 You cannot port the latest version of the Berkeley db library 620 and use it with sendmail without recompiling the world. This 621 is because C library routines use the older version which have 622 incompatible header files -- the result is that it can't read 623 other system files, such as /etc/passwd, unless you use the 624 new db format throughout your system. You should normally just 625 use the version of db supplied in your release. You may need 626 to use -DOLD_NEWDB=1 to make this work -- this turns off some 627 new interface calls (for file locking) that are not in older 628 versions of db. You'll get compile errors if you need this 629 flag and don't have it set. 630 6314.3BSD 632 If you are running a "virgin" version of 4.3BSD, you'll have 633 a very old resolver and be missing some header files. The 634 header files are simple -- create empty versions and everything 635 will work fine. For the resolver you should really port a new 636 version (4.8.3 or later) of the resolver; 4.9 is available on 637 gatekeeper.DEC.COM in pub/BSD/bind/4.9. If you are really 638 determined to continue to use your old, buggy version (or as 639 a shortcut to get sendmail working -- I'm sure you have the 640 best intentions to port a modern version of BIND), you can 641 copy ../contrib/oldbind.compat.c into src and add 642 oldbind.compat.o to OBJADD in the Makefile. 643 644A/UX 645 Date: Tue, 12 Oct 1993 18:28:28 -0400 (EDT) 646 From: "Eric C. Hagberg" <hagberg@med.cornell.edu> 647 Subject: Fix for A/UX ndbm 648 649 I guess this isn't really a sendmail bug, however, it is something 650 that A/UX users should be aware of when compiling sendmail 8.6. 651 652 Apparently, the calls that sendmail is using to the ndbm routines 653 in A/UX 3.0.x contain calls to "broken" routines, in that the 654 aliases database will break when it gets "just a little big" 655 (sorry I don't have exact numbers here, but it broke somewhere 656 around 20-25 aliases for me.), making all aliases non-functional 657 after exceeding this point. 658 659 What I did was to get the gnu-dbm-1.6 package, compile it, and 660 then re-compile sendmail with "-lgdbm", "-DNDBM", and using the 661 ndbm.h header file that comes with the gnu-package. This makes 662 things behave properly. 663 664 I suppose porting the New Berkeley db package is another route, 665 however, I made a quick attempt at it, and found it difficult 666 (not easy at least); the gnu-dbm package "configured" and 667 compiled easily. 668 669SCO Unix 670 From: Thomas Essebier <tom@stallion.oz.au> 671 Organisation: Stallion Technologies Pty Ltd. 672 673 It will probably help those who are trying to configure sendmail 8.6.9 674 to know that if they are on SCO, they had better set 675 OI-dnsrch 676 or they will core dump as soon as they try to use the resolver. 677 ie. although SCO has _res.dnsrch defined, and is kinda BIND 4.8.3, it 678 does not inititialise it, nor does it understand 'search' in 679 /etc/named.boot. 680 - sigh - 681 682DG/UX 683 Doug Anderson <dlander@afterlife.ncsc.mil> has successfully run 684 V8 on the DG/UX 5.4.2 and 5.4R3.x platforms under heavy usage. 685 Originally, the DG /bin/mail program wasn't compatible with 686 the V8 sendmail, since the DG /bin/mail requires the environment 687 variable "_FORCE_MAIL_LOCAL_=yes" be set. Version 8.7 now includes 688 this in the environment before invoking the local mailer. Some 689 have used procmail to avoid this problem in the past. It works 690 but some have experienced file locking problems with their DG/UX 691 ports of procmail. 692 693Apollo DomainOS 694 If you are compiling on Apollo, you will have to create an empty 695 file "unistd.h" and create a file "dirent.h" containing: 696 697 #include <sys/dir.h> 698 #define dirent direct 699 700 (The Makefile.DomainOS will attempt to do both of these for you.) 701 702HP-UX 8.00 703 Date: Mon, 24 Jan 1994 13:25:45 +0200 704 From: Kimmo Suominen <Kimmo.Suominen@lut.fi> 705 Subject: 8.6.5 w/ HP-UX 8.00 on s300 706 707 Just compiled and fought with sendmail 8.6.5 on a HP9000/360 (ie. a 708 series 300 machine) running HP-UX 8.00. 709 710 I was getting segmentation fault when delivering to a local user. 711 With debugging I saw it was faulting when doing _free@libc... *sigh* 712 It seems the new implementation of malloc on s300 is buggy as of 8.0, 713 so I tried out the one in -lmalloc (malloc(3X)). With that it seems 714 to work just dandy. 715 716 When linking, you will get the following error: 717 718 ld: multiply defined symbol _freespace in file /usr/lib/libmalloc.a 719 720 but you can just ignore it. You might want to add this info to the 721 README file for the future... 722 723Linux 724 Something broke between versions 0.99.13 and 0.99.14 of Linux: 725 the flock() system call gives errors. If you are running .14, 726 you must not use flock. You can do this with -DHASFLOCK=0. 727 728 Around the inclusion of bind-4.9.3 & linux libc-4.6.20, the 729 initialization of the _res structure changed. If /etc/hosts.conf 730 was configured as "hosts, bind" the resolver code could return 731 "Name server failure" errors. This is supposedly fixed in 732 later versions of libc (>= 4.6.29?), and later versions of 733 sendmail (> 8.6.10) try to work around the problem. 734 735 Some older versions (< 4.6.20?) of the libc/include files conflict 736 with sendmail's version of cdefs.h. Deleting sendmail's version 737 on those systems should be non-harmful, and new versions don't care. 738 739AIX 740 This version of sendmail does not support MB, MG, and MR resource 741 records, which are supported by AIX sendmail. 742 743RISC/os 744 RISC/os from MIPS is a merged AT&T/Berkeley system. When you 745 compile on that platform you will get duplicate definitions 746 on many files. You can ignore these. 747 748System V Release 4 Based Systems 749 There is a single Makefile that is intended for all SVR4-based 750 systems (called Makefile.SVR4). It defines __svr4__, which is 751 predefined by some compilers. If your compiler already defines 752 this compile variable, you can delete the definition from the 753 Makefile. 754 755 It's been tested on Dell Issue 2.2. 756 757DELL SVR4 758 Date: Mon, 06 Dec 1993 10:42:29 EST 759 From: "Kimmo Suominen" <kim@grendel.lut.fi> 760 Message-ID: <2d0352f9.lento29@lento29.UUCP> 761 To: eric@cs.berkeley.edu 762 Cc: sendmail@cs.berkeley.edu 763 Subject: Notes for DELL SVR4 764 765 Eric, 766 767 Here are some notes for compiling Sendmail 8.6.4 on DELL SVR4. I ran 768 across these things when helping out some people who contacted me by 769 e-mail. 770 771 1) Use gcc 2.4.5 (or later?). Dell distributes gcc 2.1 with their 772 Issue 2.2 Unix. It is too old, and gives you problems with 773 clock.c, because sigset_t won't get defined in <sys/signal.h>. 774 This is due to a problematic protection rule in there, and is 775 fixed with gcc 2.4.5. 776 777 2) If you don't use the new Berkeley DB (-DNEWDB), then you need 778 to add "-lc -lucb" to the libraries to link with. This is because 779 the -ldbm distributed by Dell needs the bcopy, bcmp and bzero 780 functions. It is important that you specify both libraries in 781 the given order to be sure you only get the BSTRING functions 782 from the UCB library (and not the signal routines etc.). 783 784 3) Don't leave out "-lelf" even if compiling with "-lc -lucb". 785 The UCB library also has another copy of the nlist routines, 786 but we do want the ones from "-lelf". 787 788 If anyone needs a compiled gcc 2.4.5 and/or a ported DB library, they 789 can use anonymous ftp to fetch them from lut.fi in the /kim directory. 790 They are copies of what I use on grendel.lut.fi, and offering them 791 does not imply that I would also support them. I have sent the DB 792 port for SVR4 back to Keith Bostic for inclusion in the official 793 distribution, but I haven't heard anything from him as of today. 794 795 - gcc-2.4.5-svr4.tar.gz (gcc 2.4.5 and the corresponding libg++) 796 - db-1.72.tar.gz (with source, objects and a installed copy) 797 798 Cheers 799 + Kim 800 -- 801 * Kimmo.Suominen@lut.fi * SysVr4 enthusiast at GRENDEL.LUT.FI * 802 * KIM@FINFILES.BITNET * Postmaster and Hostmaster at LUT.FI * 803 * + 358 200 865 718 * Unix area moderator at NIC.FUNET.FI * 804 805ConvexOS 10.1 and below 806 In order to use the name server, you must create the file 807 /etc/use_nameserver. If this file does not exist, the call 808 to res_init() will fail and you will have absolutely no 809 access to DNS, including MX records. 810 811Amdahl UTS 2.1.5 812 In order to get UTS to work, you will have to port BIND 4.9. 813 The vendor's BIND is reported to be ``totally inadequate.'' 814 See sendmail/contrib/AmdahlUTS.patch for the patches necessary 815 to get BIND 4.9 compiled for UTS. 816 817UnixWare 2.0 818 According to Alexander Kolbasov <sasha@unitech.gamma.ru>, 819 the m4 on UnixWare 2.0 (still in Beta) will core dump on the 820 config files. GNU m4 and the m4 from UnixWare 1.x both work. 821 822Non-DNS based sites 823 This version of sendmail always tries to connect to the Domain 824 Name System (DNS) to resolve names, regardless of the setting 825 of the `I' option. On most systems that are not running DNS, 826 this will fail quickly and sendmail will continue, but on some 827 systems it has a long timeout. If you have this problem, you 828 will have to recompile without NAMED_BIND. Some people have 829 claimed that they have successfully used "OI+USEVC" to force 830 sendmail to use a virtual circuit -- this will always time out 831 quickly, but also tells sendmail that a failed connection 832 should requeue the message (probably not what you intended). 833 A future release of sendmail will correct this problem. 834 835Both NEWDB and NDBM 836 If you use both -DNDBM and -DNEWDB, you must delete the module 837 ndbm.o from libdb.a and delete the file "ndbm.h" from the files 838 that get installed (that is, use the OLD ndbm.h, not the new 839 ndbm.h). This compatibility module maps ndbm calls into DB 840 calls, and breaks things rather badly. 841 842GNU getopt 843 I'm told that GNU getopt has a problem in that it gets confused 844 by the double call. Use the version in conf.c instead. 845 846BIND 4.9.2 and Ultrix 847 If you are running on Ultrix, be sure you read conf/Info.Ultrix 848 in the BIND distribution very carefully -- there is information 849 in there that you need to know in order to avoid errors of the 850 form: 851 852 /lib/libc.a(gethostent.o): sethostent: multiply defined 853 /lib/libc.a(gethostent.o): endhostent: multiply defined 854 /lib/libc.a(gethostent.o): gethostbyname: multiply defined 855 /lib/libc.a(gethostent.o): gethostbyaddr: multiply defined 856 857 during the link stage. 858 859strtoul 860 Some compilers (notably gcc) claim to be ANSI C but do not 861 include the ANSI-required routine "strtoul". If your compiler 862 has this problem, you will get an error in srvrsmtp.c on the 863 code: 864 865 # ifdef defined(__STDC__) && !defined(BROKEN_ANSI_LIBRARY) 866 e->e_msgsize = strtoul(vp, (char **) NULL, 10); 867 # else 868 e->e_msgsize = strtol(vp, (char **) NULL, 10); 869 # endif 870 871 You can use -DBROKEN_ANSI_LIBRARY to get around this problem. 872 873 874+--------------+ 875| MANUAL PAGES | 876+--------------+ 877 878The manual pages have been written against the -mandoc macros 879instead of the -man macros. The latest version of groff has them 880included. You can also get a copy from FTP.UU.NET in directory 881/systems/unix/bsd-sources/share/tmac. 882 883 884+-----------------+ 885| DEBUGGING HOOKS | 886+-----------------+ 887 888As of 8.6.5, sendmail daemons will catch a SIGUSR1 signal and log 889some debugging output (logged at LOG_DEBUG severity). The 890information dumped is: 891 892 * The value of the $j macro. 893 * A warning if $j is not in the set $=w. 894 * A list of the open file descriptors. 895 * The contents of the connection cache. 896 * If ruleset 89 is defined, it is evaluated and the results printed. 897 898This allows you to get information regarding the runtime state of the 899daemon on the fly. This should not be done too frequently, since 900the process of rewriting may lose memory which will not be recovered. 901Also, ruleset 89 may call non-reentrant routines, so there is a small 902non-zero probability that this will cause other problems. It is 903really only for debugging serious problems. 904 905A typical formulation of ruleset 89 would be: 906 907 R$* $@ $>0 some test address 908 909 910+-----------------------------+ 911| DESCRIPTION OF SOURCE FILES | 912+-----------------------------+ 913 914The following list describes the files in this directory: 915 916Makefile The makefile used here; this version only works with 917 the new Berkeley make. 918Makefile.dist A trimmed down version of the makefile that works with 919 the old make. 920READ_ME This file. 921TRACEFLAGS My own personal list of the trace flags -- not guaranteed 922 to be particularly up to date. 923alias.c Does name aliasing in all forms. 924arpadate.c A subroutine which creates ARPANET standard dates. 925clock.c Routines to implement real-time oriented functions 926 in sendmail -- e.g., timeouts. 927collect.c The routine that actually reads the mail into a temp 928 file. It also does a certain amount of parsing of 929 the header, etc. 930conf.c The configuration file. This contains information 931 that is presumed to be quite static and non- 932 controversial, or code compiled in for efficiency 933 reasons. Most of the configuration is in sendmail.cf. 934conf.h Configuration that must be known everywhere. 935convtime.c A routine to sanely process times. 936daemon.c Routines to implement daemon mode. This version is 937 specifically for Berkeley 4.1 IPC. 938deliver.c Routines to deliver mail. 939domain.c Routines that interface with DNS (the Domain Name 940 System). 941err.c Routines to print error messages. 942envelope.c Routines to manipulate the envelope structure. 943headers.c Routines to process message headers. 944macro.c The macro expander. This is used internally to 945 insert information from the configuration file. 946main.c The main routine to sendmail. This file also 947 contains some miscellaneous routines. 948map.c Support for database maps. 949mci.c Routines that handle mail connection information caching. 950parseaddr.c The routines which do address parsing. 951queue.c Routines to implement message queueing. 952readcf.c The routine that reads the configuration file and 953 translates it to internal form. 954recipient.c Routines that manipulate the recipient list. 955savemail.c Routines which save the letter on processing errors. 956sendmail.h Main header file for sendmail. 957srvrsmtp.c Routines to implement server SMTP. 958stab.c Routines to manage the symbol table. 959stats.c Routines to collect and post the statistics. 960sysexits.c List of error messages associated with error codes 961 in sysexits.h. 962trace.c The trace package. These routines allow setting and 963 testing of trace flags with a high granularity. 964udb.c The user database interface module. 965usersmtp.c Routines to implement user SMTP. 966util.c Some general purpose routines used by sendmail. 967version.c The version number and information about this 968 version of sendmail. Theoretically, this gets 969 modified on every change. 970 971Eric Allman 972 973(Version 8.85, last update 05/05/95 08:20:30) 974