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.49 (Berkeley) 01/22/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 to do this.] 114 115If NEWDB and NDBM are defined (but not NIS), then sendmail will read 116NDBM format alias files, but the next time a newaliases is run the 117format will be converted to NEWDB; that format will be used forever 118more. This is intended as a transition feature. [Note however that 119the NEWDB library also catches and maps NDBM calls; you will have to 120back out this feature to get this to work. See ``Quirks'' section 121below for details.] 122 123If all three are defined, sendmail operates as described above, and also 124looks for the file /var/yp/Makefile. If it exists, newaliases will 125build BOTH the NEWDB and NDBM format alias files. However, it will 126only use the NEWDB file; the NDBM format file is used only by the 127NIS subsystem. 128 129If NDBM and NIS are defined (regardless of the definition of NEWDB 130or the existance of /var/yp/Makefile), sendmail adds the special 131tokens "YP_LAST_MODIFIED" and "YP_MASTER_NAME", both of which are 132required if the NDBM file is to be used as an NIS map. 133 134All of -DNEWDB, -DNDBM, and -DNIS are normally defined in the DBMDEF 135line in the Makefile. 136 137 138+---------------+ 139| COMPILE FLAGS | 140+---------------+ 141 142Whereever possible, I try to make sendmail pull in the correct 143compilation options needed to compile on various environments based on 144automatically defined symbols. Some machines don't seem to have useful 145symbols availble, requiring the following compilation flags in the 146Makefile: 147 148SOLARIS Define this if you are running Solaris 2.0 or higher. 149SOLARIS_2_3 Define this if you are running Solaris 2.3 or higher. 150SUNOS403 Define this if you are running SunOS 4.0.3. 151NeXT Define this if you are on a NeXT box. (This one may 152 be pre-defined for you.) There are other hacks you 153 have to make -- see below. 154_AIX3 Define this if you are IBM AIX 3.x. 155RISCOS Define this if you are running RISC/os from MIPS. 156_SCO_unix_ Define this if you are on SCO UNIX. 157_SCO_unix_4_2 Define this if you are on SCO Open Server 3.2v4. 158 159If you are a system that sendmail has already been ported to, you 160probably won't have to touch these. But if you are porting, you may 161have to tweak the following compilation flags in conf.h in order to 162get it to compile and link properly: 163 164SYSTEM5 Adjust for System V (not necessarily Release 4). 165SYS5SIGNALS Use System V signal semantics -- the signal handler 166 is automatically dropped when the signal is caught. 167 If this is not set, use POSIX/BSD semantics, where the 168 signal handler stays in force until an exec or an 169 explicit delete. Implied by SYSTEM5. 170SYS5SETPGRP Use System V setpgrp() semantics. Implied by SYSTEM5. 171HASFLOCK Set this if you prefer to use the flock(2) system call 172 rather than using fcntl-based locking. Fcntl locking 173 has some semantic gotchas, but many vendor systems 174 also interface it to lockd(8) to do NFS-style locking. 175 For this reason, this should not be set unless you 176 don't have an alternative. 177HASUNAME Set if you have the "uname" system call. Implied by 178 SYSTEM5. 179HASUNSETENV Define this if your system library has the "unsetenv" 180 subroutine. 181HASSETSID Define this if you have the setsid(2) system call. This 182 is implied if your system appears to be POSIX compliant. 183HASINITGROUPS Define this if you have the initgroups(3) routine. 184HASSETVBUF Define this if you have the setvbuf(3) library call. 185 If you don't, setlinebuf will be used instead. This 186 defaults on if your compiler defines __STDC__. 187HASSETREUID Define this if you have setreuid(2) ***AND*** root can 188 use setreuid to change to an arbitrary user. This second 189 condition is not satisfied on AIX 3.x. You may find that 190 your system has setresuid(2), (for example, on HP-UX) in 191 which case you will also have to #define setreuid(r, e) 192 to be the appropriate call. Some systems (such as Solaris) 193 have a compatibility routine that doesn't work properly, 194 but may have "saved user ids" properly implemented so you 195 can ``#define setreuid(r, e) seteuid(e)'' and have it work. 196 The important thing is that you have a call that will set 197 the effective uid independently of the real or saved uid 198 and be able to set the effective uid back again when done. 199 There's a test program in ../test/t_setreuid.c that will 200 try things on your system. Setting this improves the 201 security, since sendmail doesn't have to read .forward 202 and :include: files as root. There are certain attacks 203 that may be unpreventable without this call. 204HASLSTAT Define this if you have symbolic links (and thus the 205 lstat(2) system call). This improves security. Unlike 206 most other options, this one is on by default, so you 207 need to #undef it in conf.h if you don't have symbolic 208 links (these days everyone does). 209NEEDGETOPT Define this if you need a reimplementation of getopt(3). 210 On some systems, getopt does very odd things if called 211 to scan the arguments twice. This flag will ask sendmail 212 to compile in a local version of getopt that works 213 properly. 214NEEDSTRTOL Define this if your standard C library does not define 215 strtol(3). This will compile in a local version. 216NEEDVPRINTF Define this if your standard C library does not define 217 vprintf(3). Note that the resulting fake implementation 218 is not very elegant and may not even work on some 219 architectures. 220HASGETUSERSHELL Define this to 1 if you have getusershell(3) in your 221 standard C library. If this is not defined, or is defined 222 to be 0, sendmail will scan the /etc/shells file (no 223 NIS-style support, defaults to /bin/sh and /bin/csh if 224 that file does not exist) to get a list of unrestricted 225 user shells. This is used to determine whether users 226 are allowed to forward their mail to a program or a file. 227GIDSET_T The type of entries in a gidset passed as the second 228 argument to getgroups(2). Historically this has been an 229 int, so this is the default, but some systems (such as 230 IRIX) pass it as a gid_t, which is an unsigned short. 231 This will make a difference, so it is important to get 232 this right! However, it is only an issue if you have 233 group sets. 234SLEEP_T The type returned by the system sleep() function. 235 Defaults to "unsigned int". Don't worry about this 236 if you don't have compilation problems. 237ARBPTR_T The type of an arbitrary pointer -- defaults to "void *". 238 If you are an very old compiler you may need to define 239 this to be "char *". 240LA_TYPE The type of load average your kernel supports. These 241 can be LA_SUBR (4) if you have the getloadavg(3) routine, 242 LA_MACH (5) to use MACH-style load averages (calls 243 processor_set_info()), LA_FLOAT (3) if you read kmem and 244 interpret the value as a floating point number, LA_INT (2) 245 to interpret as a long integer, or LA_SHORT (6) to 246 interpret as a short integer. These last three have 247 several other parameters that they try to divine: the 248 name of your kernel, the name of the variable in the 249 kernel to examine, the number of bits of precision in 250 a fixed point load average, and so forth. In desparation, 251 use LA_ZERO (1) -- it always returns the load average as 252 "zero" (and does so on all architectures). The actual 253 code is in conf.c -- it can be tweaked if you are brave. 254SFS_TYPE Encodes how your kernel can locate the amount of free 255 space on a disk partition. This can be set to SFS_NONE 256 (0) if you have no way of getting this information, 257 SFS_USTAT (1) if you have the ustat(2) system call, 258 SFS_4ARGS (2) if you have a four-argument statfs(2) 259 system call (and the include file is <sys/statfs.h>), 260 and SFS_VFS (3), SFS_MOUNT (4), or SFS_STATFS (5) if 261 you have the two-argument statfs(2) system call, with 262 includes in <sys/vfs.h>, <sys/mount.h>, or <sys/statfs.h> 263 respectively. The default if nothing is defined is 264 SFS_NONE. 265ERRLIST_PREDEFINED 266 If set, assumes that some header file defines sys_errlist. 267 This may be needed if you get type conflicts on this 268 variable -- otherwise don't worry about it. 269WAITUNION The wait(2) routine takes a "union wait" argument instead 270 of an integer argument. This is for compatibility with 271 old versions of BSD. 272SCANF You can set this to extend the F command to accept a 273 scanf string -- this gives you a primitive parser for 274 class definitions -- BUT it can make you vulnerable to 275 core dumps if the target file is poorly formed. 276SYSLOG_BUFSIZE You can define this to be the size of the buffer that 277 syslog accepts. If it is not defined, it assumes a 278 1024-byte buffer. If the buffer is very small (under 279 256 bytes) the log message format changes -- each 280 e-mail message will log many more messages, since it 281 will log each piece of information as a separate line 282 in syslog. 283 284 285+-----------------------+ 286| COMPILE-TIME FEATURES | 287+-----------------------+ 288 289There are a bunch of features that you can decide to compile in, such 290as selecting various database packages and special protocol support. 291Several are assumed based on other compilation flags -- if you want to 292"un-assume" something, you probably need to edit conf.h. Compilation 293flags that add support for special features include: 294 295NDBM Include support for "new" DBM library for aliases and maps. 296 Normally defined in the Makefile. 297NEWDB Include support for Berkeley "db" package (hash & btree) 298 for aliases and maps. Normally defined in the Makefile. 299NIS Define this to get NIS (YP) support for aliases and maps. 300 Normally defined in the Makefile. 301USERDB Include support for the User Information Database. Implied 302 by NEWDB in conf.h. 303IDENTPROTO Define this as 1 to get IDENT (RFC 1413) protocol support. 304 This is assumed unless you are running on Ultrix or 305 HP-UX, both of which have a problem in the UDP 306 implementation. You can define it to be 0 to explicitly 307 turn off IDENT protocol support. 308MIME Include support for MIME-encapsulated error messages. 309LOG Set this to get syslog(3) support. Defined by default 310 in conf.h. You want this if at all possible. 311NETINET Set this to get TCP/IP support. Defined by default 312 in conf.h. You probably want this. 313NETISO Define this to get ISO networking support. 314SMTP Define this to get the SMTP code. Implied by NETINET 315 or NETISO. 316NAMED_BIND Define this to get DNS (name daemon) support, including 317 MX support. The specs you must use this if you run 318 SMTP. Defined by default in conf.h. 319QUEUE Define this to get queueing code. Implied by NETINET 320 or NETISO; required by SMTP. This gives you other good 321 stuff -- it should be on. 322DAEMON Define this to get general network support. Implied by 323 NETINET or NETISO. Defined by default in conf.h. You 324 almost certainly want it on. 325MATCHGECOS Permit fuzzy matching of user names against the full 326 name (GECOS) field in the /etc/passwd file. This should 327 probably be on, since you can disable it from the config 328 file if you want to. Defined by default in conf.h. 329SETPROCTITLE Try to set the string printed by "ps" to something 330 informative about what sendmail is doing. Defined by 331 default in conf.h. 332 333 334+---------------------+ 335| DNS/RESOLVER ISSUES | 336+---------------------+ 337 338Many systems have old versions of the resolver library. At a minimum, 339you should be running BIND 4.8.3; older versions may compile, but they 340have known bugs that should give you pause. 341 342Common problems in old versions include "undefined" errors for 343dn_skipname. 344 345Some people have had a problem with BIND 4.9; it uses some routines 346that it expects to be externally defined such as strerror(). It may 347help to link with "-l44bsd" to solve this problem. 348 349!PLEASE! be sure to link with the same version of the resolver as 350the header files you used -- some people have used the 4.9 headers 351and linked with BIND 4.8 or vice versa, and it doesn't work. 352Unfortunately, it doesn't fail in an obvious way -- things just 353subtlely don't work. 354 355 356+-------------------------------------+ 357| OPERATING SYSTEM AND COMPILE QUIRKS | 358+-------------------------------------+ 359 360GCC 2.5.x problems *** IMPORTANT *** 361 Date: Mon, 29 Nov 93 19:08:44 PST 362 From: wilson@cygnus.com (Jim Wilson) 363 Message-Id: <9311300308.AA04608@cygnus.com> 364 To: kenner@vlsi1.ultra.nyu.edu 365 Subject: [cattelan@thebarn.com: gcc 2.5.4-2.5.5 -O bug] 366 Cc: cattelan@thebarn.com, rms@gnu.ai.mit.edu, sendmail@cs.berkeley.edu 367 368 This fixes a problem that occurs when gcc 2.5.5 is used to compile 369 sendmail 8.6.4 with optimization on a sparc. 370 371 Mon Nov 29 19:00:14 1993 Jim Wilson (wilson@sphagnum.cygnus.com) 372 373 * reload.c (find_reloads_toplev): Replace obsolete reference to 374 BYTE_LOADS_*_EXTEND with LOAD_EXTEND_OP. 375 376 *** clean-ss-931128/reload.c Sun Nov 14 16:20:01 1993 377 --- ss-931128/reload.c Mon Nov 29 18:52:55 1993 378 *************** find_reloads_toplev (x, opnum, type, ind 379 *** 3888,3894 **** 380 force a reload in that case. So we should not do anything here. */ 381 382 else if (regno >= FIRST_PSEUDO_REGISTER 383 ! #if defined(BYTE_LOADS_ZERO_EXTEND) || defined(BYTE_LOADS_SIGN_EXTEND) 384 && (GET_MODE_SIZE (GET_MODE (x)) 385 <= GET_MODE_SIZE (GET_MODE (SUBREG_REG (x)))) 386 #endif 387 --- 3888,3894 ---- 388 force a reload in that case. So we should not do anything here. */ 389 390 else if (regno >= FIRST_PSEUDO_REGISTER 391 ! #ifdef LOAD_EXTEND_OP 392 && (GET_MODE_SIZE (GET_MODE (x)) 393 <= GET_MODE_SIZE (GET_MODE (SUBREG_REG (x)))) 394 #endif 395 396 397SunOS 4.x (Solaris 1.x) 398 You may have to use -lresolv on SunOS. However, beware that 399 this links in a new version of gethostbyname that does not 400 understand NIS, so you must have all of your hosts in DNS. 401 402 Some people have reported problems with the SunOS version of 403 -lresolv and/or in.named, and suggest that you get a newer 404 version. The symptoms are delays when you connect to the 405 SMTP server on a SunOS machine or having your domain added to 406 addresses inappropriately. There is a version of BIND 407 version 4.9 on gatekeeper.DEC.COM in pub/BSD/bind/4.9. 408 409 There is substantial disagreement about whether you can make 410 this work with resolv+, which allows you to specify a search-path 411 of services. Some people report that it works fine, others 412 claim it doesn't work at all (including causing sendmail to 413 drop core when it tries to do multiple resolv+ lookups for a 414 single job). I haven't tried resolv+, as we use DNS exclusively. 415 416 Should you want to try resolv+, it is on ftp.uu.net in 417 /networking/ip/dns. 418 419Solaris 2.x (SunOS 5.x) 420 To compile for Solaris, be sure you use -DSOLARIS. 421 422 From a correspondent: 423 424 For solaris 2.2, I have 425 426 hosts: files dns 427 428 in /etc/nsswitch.conf and /etc/hosts has to have the fully 429 qualified host name. I think "files" has to be before "dns" 430 in /etc/nsswitch.conf during bootup. 431 432 To the best of my knowledge, Solaris does not have the 433 gethostbyname problem described above. 434 435 The Solaris "syslog" function is apparently limited to something 436 about 90 characters because of a kernel limitation. If you have 437 source code, you can probably up this number. The syslogd patch 438 is included in kernel jumbo patch for Solaris 2.2 as of revision 439 -39 or so. At least one person is running with patch 100999-45 440 and their long lost sendmail logging is finally showing up. At 441 least one other person is running with patch 101318 installed 442 under Solaris 2.3 with success. 443 444OSF/1 445 If you are compiling on OSF/1 (DEC Alpha), you must use 446 -L/usr/shlib (otherwise it core dumps on startup). You may also 447 need -mld to get the nlist() function, although some versions 448 apparently don't need this. 449 450 Also, the enclosed makefile removed /usr/sbin/smtpd; if you need 451 it, just create the link to the sendmail binary. 452 453NeXT 454 If you are compiling on NeXT, you will have to create an empty 455 file "unistd.h" and create a file "dirent.h" containing: 456 457 #include <sys/dir.h> 458 #define dirent direct 459 460 (The Makefile.NeXT should try to do both of these for you.) 461 462 Apparently, there is a bug in getservbyname on Nextstep 3.0 463 that causes it to fail under some circumstances with the 464 message "SYSERR: service "smtp" unknown" logged. You should 465 be able to work around this by including the line: 466 467 OOPort=25 468 469 in your .cf file. 470 471 You may have to use -DNeXT. 472 473BSDI (BSD/386) 1.0, NetBSD 0.9, FreeBSD 1.0 474 The "m4" from BSDI won't handle the config files properly. 475 I haven't had a chance to test this myself. 476 477 The M4 shipped in FreeBSD and NetBSD 0.9 don't handle the config 478 files properly. One must use either GNU m4 1.1 or the PD-M4 479 recently posted in comp.os.386bsd.bugs (and maybe others). 480 NetBSD-current includes the PD-M4 (as stated in the NetBSD file 481 CHANGES). 482 483 FreeBSD 1.0 RELEASE has uname(2) now. Use -DUSEUNAME in order to 484 use it (look into Makefile.FreeBSD). NetBSD-current may have 485 it too but it has not been verified. 486 487 You cannot port the latest version of the Berkeley db library 488 and use it with sendmail without recompiling the world. This 489 is because C library routines use the older version which have 490 incompatible header files -- the result is that it can't read 491 other system files, such as /etc/passwd, unless you use the 492 new db format throughout your system. You should normally just 493 use the version of db supplied in your release. You may need 494 to use -DOLD_NEWDB to make this work -- this turns off some 495 new interface calls (for file locking) that are not in older 496 versions of db. You'll get compile errors if you need this 497 flag and don't have it set. 498 4994.3BSD 500 If you are running a "virgin" version of 4.3BSD, you'll have 501 a very old resolver and be missing some header files. The 502 header files are simple -- create empty versions and everything 503 will work fine. For the resolver you should really port a new 504 version (4.8.3 or later) of the resolver; 4.9 is available on 505 gatekeeper.DEC.COM in pub/BSD/bind/4.9. If you are really 506 determined to continue to use your old, buggy version (or as 507 a shortcut to get sendmail working -- I'm sure you have the 508 best intentions to port a modern version of BIND), you can 509 copy ../contrib/oldbind.compat.c into src and add 510 oldbind.compat.o to OBJADD in the Makefile. 511 512A/UX 513 Date: Tue, 12 Oct 1993 18:28:28 -0400 (EDT) 514 From: "Eric C. Hagberg" <hagberg@med.cornell.edu> 515 Subject: Fix for A/UX ndbm 516 517 I guess this isn't really a sendmail bug, however, it is something 518 that A/UX users should be aware of when compiling sendmail 8.6. 519 520 Apparently, the calls that sendmail is using to the ndbm routines 521 in A/UX 3.0.x contain calls to "broken" routines, in that the 522 aliases database will break when it gets "just a little big" 523 (sorry I don't have exact numbers here, but it broke somewhere 524 around 20-25 aliases for me.), making all aliases non-functional 525 after exceeding this point. 526 527 What I did was to get the gnu-dbm-1.6 package, compile it, and 528 then re-compile sendmail with "-lgdbm", "-DNDBM", and using the 529 ndbm.h header file that comes with the gnu-package. This makes 530 things behave properly. 531 532 I suppose porting the New Berkeley db package is another route, 533 however, I made a quick attempt at it, and found it difficult 534 (not easy at least); the gnu-dbm package "configured" and 535 compiled easily. 536 537DG/UX 538 Apparently, /bin/mail doesn't work properly for delivery on 539 DG/UX -- the person who has this working, Douglas Anderson 540 <dlander@afterlife.ncsc.mil>, used procmail instead. 541 542Apollo DomainOS 543 If you are compiling on Apollo, you will have to create an empty 544 file "unistd.h" and create a file "dirent.h" containing: 545 546 #include <sys/dir.h> 547 #define dirent direct 548 549 (The Makefile.DomainOS will attempt to do both of these for you.) 550 551System V Release 4 Based Systems 552 There is a single Makefile that is intended for all SVR4-based 553 systems (called Makefile.SVR4). It defines __svr4__, which is 554 predefined by some compilers. If your compiler already defines 555 this compile variable, you can delete the definition from the 556 Makefile. 557 558 It's been tested on Dell Issue 2.2. 559 560DELL SVR4 561 Date: Mon, 06 Dec 1993 10:42:29 EST 562 From: "Kimmo Suominen" <kim@grendel.lut.fi> 563 Message-ID: <2d0352f9.lento29@lento29.UUCP> 564 To: eric@cs.berkeley.edu 565 Cc: sendmail@cs.berkeley.edu 566 Subject: Notes for DELL SVR4 567 568 Eric, 569 570 Here are some notes for compiling Sendmail 8.6.4 on DELL SVR4. I ran 571 across these things when helping out some people who contacted me by 572 e-mail. 573 574 1) Use gcc 2.4.5 (or later?). Dell distributes gcc 2.1 with their 575 Issue 2.2 Unix. It is too old, and gives you problems with 576 clock.c, because sigset_t won't get defined in <sys/signal.h>. 577 This is due to a problematic protection rule in there, and is 578 fixed with gcc 2.4.5. 579 580 2) If you don't use the new Berkeley DB (-DNEWDB), then you need 581 to add "-lc -lucb" to the libraries to link with. This is because 582 the -ldbm distributed by Dell needs the bcopy, bcmp and bzero 583 functions. It is important that you specify both libraries in 584 the given order to be sure you only get the BSTRING functions 585 from the UCB library (and not the signal routines etc.). 586 587 3) Don't leave out "-lelf" even if compiling with "-lc -lucb". 588 The UCB library also has another copy of the nlist routines, 589 but we do want the ones from "-lelf". 590 591 If anyone needs a compiled gcc 2.4.5 and/or a ported DB library, they 592 can use anonymous ftp to fetch them from lut.fi in the /kim directory. 593 They are copies of what I use on grendel.lut.fi, and offering them 594 does not imply that I would also support them. I have sent the DB 595 port for SVR4 back to Keith Bostic for inclusion in the official 596 distribution, but I haven't heard anything from him as of today. 597 598 - gcc-2.4.5-svr4.tar.gz (gcc 2.4.5 and the corresponding libg++) 599 - db-1.72.tar.gz (with source, objects and a installed copy) 600 601 Cheers 602 + Kim 603 -- 604 * Kimmo.Suominen@lut.fi * SysVr4 enthusiast at GRENDEL.LUT.FI * 605 * KIM@FINFILES.BITNET * Postmaster and Hostmaster at LUT.FI * 606 * + 358 200 865 718 * Unix area moderator at NIC.FUNET.FI * 607 608 609Non-DNS based sites 610 This version of sendmail always tries to connect to the Domain 611 Name System (DNS) to resolve names, regardless of the setting 612 of the `I' option. On most systems that are not running DNS, 613 this will fail quickly and sendmail will continue, but on some 614 systems it has a long timeout. If you have this problem, you 615 will have to recompile without NAMED_BIND. Some people have 616 claimed that they have successfully used "OI+USEVC" to force 617 sendmail to use a virtual circuit -- this will always time out 618 quickly, but also tells sendmail that a failed connection 619 should requeue the message (probably not what you intended). 620 A future release of sendmail will correct this problem. 621 622Both NEWDB and NDBM 623 If you use both -DNDBM and -DNEWDB, you must delete the module 624 ndbm.o from libdb.a and delete the file "ndbm.h" from the files 625 that get installed (that is, use the OLD ndbm.h, not the new 626 ndbm.h). This compatibility module maps ndbm calls into DB 627 calls, and breaks things rather badly. 628 629GNU getopt 630 I'm told that GNU getopt has a problem in that it gets confused 631 by the double call. Use the version in conf.c instead. 632 633 634+--------------+ 635| MANUAL PAGES | 636+--------------+ 637 638The manual pages have been written against the -mandoc macros 639instead of the -man macros. The latest version of groff has them 640included. You can also get a copy from FTP.UU.NET in directory 641/systems/unix/bsd-sources/share/tmac. 642 643 644+-----------------+ 645| DEBUGGING HOOKS | 646+-----------------+ 647 648As of 8.6.5, sendmail daemons will catch a SIGUSR1 signal and log 649some debugging output (logged at LOG_DEBUG severity). The 650information dumped is: 651 652 * The value of the $j macro. 653 * A warning if $j is not in the set $=w. 654 * A list of the open file descriptors. 655 * The contents of the connection cache. 656 * If ruleset 89 is defined, it is evaluated and the results printed. 657 658This allows you to get information regarding the runtime state of the 659daemon on the fly. This should not be done too frequently, since 660the process of rewriting may lose memory which will not be recovered. 661Also, ruleset 89 may call non-reentrant routines, so there is a small 662non-zero probability that this will cause other problems. It is 663really only for debugging serious problems. 664 665A typical formulation of ruleset 89 would be: 666 667 R$* $@ $>0 some test address 668 669 670+-----------------------------+ 671| DESCRIPTION OF SOURCE FILES | 672+-----------------------------+ 673 674The following list describes the files in this directory: 675 676Makefile The makefile used here; this version only works with 677 the new Berkeley make. 678Makefile.dist A trimmed down version of the makefile that works with 679 the old make. 680READ_ME This file. 681TRACEFLAGS My own personal list of the trace flags -- not guaranteed 682 to be particularly up to date. 683alias.c Does name aliasing in all forms. 684arpadate.c A subroutine which creates ARPANET standard dates. 685clock.c Routines to implement real-time oriented functions 686 in sendmail -- e.g., timeouts. 687collect.c The routine that actually reads the mail into a temp 688 file. It also does a certain amount of parsing of 689 the header, etc. 690conf.c The configuration file. This contains information 691 that is presumed to be quite static and non- 692 controversial, or code compiled in for efficiency 693 reasons. Most of the configuration is in sendmail.cf. 694conf.h Configuration that must be known everywhere. 695convtime.c A routine to sanely process times. 696daemon.c Routines to implement daemon mode. This version is 697 specifically for Berkeley 4.1 IPC. 698deliver.c Routines to deliver mail. 699domain.c Routines that interface with DNS (the Domain Name 700 System). 701err.c Routines to print error messages. 702envelope.c Routines to manipulate the envelope structure. 703headers.c Routines to process message headers. 704macro.c The macro expander. This is used internally to 705 insert information from the configuration file. 706main.c The main routine to sendmail. This file also 707 contains some miscellaneous routines. 708map.c Support for database maps. 709mci.c Routines that handle mail connection information caching. 710parseaddr.c The routines which do address parsing. 711queue.c Routines to implement message queueing. 712readcf.c The routine that reads the configuration file and 713 translates it to internal form. 714recipient.c Routines that manipulate the recipient list. 715savemail.c Routines which save the letter on processing errors. 716sendmail.h Main header file for sendmail. 717srvrsmtp.c Routines to implement server SMTP. 718stab.c Routines to manage the symbol table. 719stats.c Routines to collect and post the statistics. 720sysexits.c List of error messages associated with error codes 721 in sysexits.h. 722trace.c The trace package. These routines allow setting and 723 testing of trace flags with a high granularity. 724udb.c The user database interface module. 725usersmtp.c Routines to implement user SMTP. 726util.c Some general purpose routines used by sendmail. 727version.c The version number and information about this 728 version of sendmail. Theoretically, this gets 729 modified on every change. 730 731Eric Allman 732 733(Version 8.49, last update 01/22/94 08:59:39) 734