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