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