1/*- 2 * @(#)READ_ME 6.8 (Berkeley) 05/05/93 3 */ 4 5THIS IS AN ALPHA VERSION OF SENDMAIL. DON'T EVEN THINK ABOUT USING IT 6IN A HEAVY PRODUCTION ENVIRONMENT. We've been running it (in various 7forms) at Berkeley for several months, but our environment is far from 8general. In particular, it hasn't been heavily tested for non-SMTP 9environments. The good news is that most of the changes have been 10Internet-related, and that has been tested. 11 12REPORT ANY BUGS to sendmail@CS.Berkeley.EDU. 13 14THIS IS COPYRIGHTED CODE. BY COMPILING AND RUNNING THIS CODE YOU AGREE 15to upgrade to the production release when it comes out. You understand 16that we hope this will be by June, but if there are serious problems 17it may be longer than that. 18 19PLEASE DO NOT MAKE THIS AVAILABLE ON PUBLIC FTP. Since it is still an 20early release, I'd prefer that people get copies directly from Berkeley 21to make certain that they have the most recent version. This isn't 22an attempt to limit access, just to make certain that everyone is able 23to keep up. 24 25You don't have to install mail.local to run the new version of sendmail. 26Many versions of /bin/mail take a "-d" flag or do local delivery already. 27In particular, mail.local is largely specific to 4.4 BSD, and will not 28be easy to compile elsewhere. It was written by Keith Bostic, not myself, 29and was not intended for the "general case". 30 31There are several related RFCs that you may wish to read -- they are 32available via anonymous FTP to several sites, including nic.ddn.mil 33(directory rfc), ftp.nisc.sri.com (rfc), nis.nsf.net (RFC), 34nisc.jvnc.net (rfc), venera.isi.edu (in-notes), and wuarchive.wustl.edu 35(info/rfc). They can also be retrieved via electronic mail by sending 36email to one of: 37 38 mail-server@nisc.sri.com 39 Put "send rfcNNN" in message body 40 nis-info@nis.nsf.net 41 Put "send RFCnnn.TXT-1" in message body 42 sendrfc@jvnc.net 43 Put "RFCnnn" as Subject: line 44 45Important RFCs for electronic mail are: 46 47 RFC821 SMTP protocol 48 RFC822 Mail header format 49 RFC974 MX routing 50 RFC976 UUCP mail format 51 RFC1123 Host requirements (modifies 821, 822, and 974) 52 RFC1413 Identification server 53 RFC1341 MIME: Multipurpose Internet Mail Extensions 54 RFC1344 Implications of MIME for Internet Mail Gateways 55 56Other standards that may be of interest (but which are less directly 57relevant to sendmail) are: 58 59 RFC987 Mapping between RFC822 and X.400 60 RFC1049 Content-Type header field (extension to RFC822) 61 62Unfortunately, for a variety of reasons the Makefiles are for the new 63Berkeley "make" and will not work on the old, traditional make. I urge 64you to get this make from Net2 (available on many public FTP archives). 65Failing that, some directories have a "Makefile.dist" that will work on 66older versions of make (but don't have the niceties included). 67 68Similar comments apply to the man pages -- they use the new Berkeley 69-mandoc macros instead of the -man macros. You can get these from 70Net2 as well. 71 72IF YOU WANT TO RUN THE NEW BERKELEY DB SOFTWARE: **** DO NOT **** 73use the version that was on the Net2 tape -- it has a number of 74nefarious bugs that were bad enough when I got them; you shouldn't have 75to go through the same thing. Instead, get a new version via public 76FTP from vangogh.CS.Berkeley.EDU, file pub/db.tar.Z. This software 77is highly recommended; it gets rid of several stupid limits, it's much 78faster, and the interface is nicer to animals and plants. You will 79also probably find that you have to add -I/where/you/put/db/include 80to the sendmail makefile to get db.h to work properly. 81 82The structure of this directory tree is: 83 84cf Source for Berkeley configuration files. These are 85 different than what you've seen before. They are a 86 fairly dramatic rewrite, requiring the new sendmail 87 (since they use new features). 88contrib Some contributed tools to help with sendmail. THESE 89 ARE NOT SUPPORTED by Berkeley -- contact the original 90 authors if you have problems. 91doc Documentation. If you are getting source, read 92 op.me -- it's long, but worth it. 93mail.local Source for mail.local(8), a local delivery program. 94 Older versions of sendmail called /bin/mail with a 95 special -d flag to mean "really deliver this mail"; 96 this is a completely new (and much smaller) program 97 that does absolutely nothing but deliver local mail. 98 THIS IS SPECIFIC TO 4.4BSD, and is not under my 99 control. 100mailstats Statistics printing program. It has the pathname of 101 sendmail.st compiled in, so if you've changed that, 102 beware. This isn't all that useful. 103makemap A program that creates the keyed maps used by the $( ... $) 104 construct in sendmail. It is primitive but effective. 105 It takes a very simple input format, so you will probably 106 expect to preprocess must human-convenient formats 107 using sed scripts before this program will like them. 108 But it should be functionally complete. 109praliases A program to print the DBM version of the aliases file. 110 It hasn't been converted to understand the new Berkeley 111 DB format (which we are using). 112rmail Source for rmail(8). This is used as a delivery 113 agent for for UUCP, and could presumably be used by 114 other non-socket oriented mailers. Older versions of 115 rmail are probably deficient. 116src Source for the sendmail program itself. 117