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