| README (302408) | README (38032) |
|---|---|
| 1/*- 2 * @(#)README 8.48 (Berkeley) 5/19/98 3 */ |
|
| 1 2 SENDMAIL RELEASE 8 3 | 4 5 SENDMAIL RELEASE 8 6 |
| 4This directory has the latest sendmail(TM) software from Proofpoint, Inc. | 7This directory has the latest sendmail(TM) software from Sendmail, Inc. 8See doc/changes/changes.me for a summary of changes since 5.67. |
| 5 | 9 |
| 6Report any bugs to sendmail-bugs-YYYY@support.sendmail.org 7where YYYY is the current year, e.g., 2005. | 10Report any bugs to sendmail-bugs@sendmail.ORG |
| 8 | 11 |
| 9There is a web site at http://www.sendmail.org/ -- see that site for | 12There is a web site at http://WWW.Sendmail.ORG -- see that site for |
| 10the latest updates. 11 | 13the latest updates. 14 |
| 12+--------------+ 13| INTRODUCTION | 14+--------------+ | 15****************************************************************** 16** DO NOT USE MAKE to compile sendmail. Instead, cd src and ** 17** use the "Build" shell script. On many environments this ** 18** will do everything for you, no fuss, no muss. See ** 19** src/README for more details of compilation. See cf/README ** 20** for details about building a runtime configuration file. ** 21****************************************************************** |
| 15 | 22 |
| 160. The vast majority of queries about sendmail are answered in the 17 README files noted below. | 23Sendmail is a trademark of Sendmail, Inc. |
| 18 | 24 |
| 191. Read this README file, especially this introduction, and the DIRECTORY 20 PERMISSIONS sections. 21 222. Read the INSTALL file in this directory. 23 243. Read sendmail/README, especially: 25 a. the introduction 26 b. the BUILDING SENDMAIL section 27 c. the relevant part(s) of the OPERATING SYSTEM AND COMPILE QUIRKS section 28 29 You may also find these useful: 30 31 d. sendmail/SECURITY 32 e. devtools/README 33 f. devtools/Site/README 34 g. libmilter/README 35 h. mail.local/README 36 i. smrsh/README 37 384. Read cf/README. 39 40Sendmail is a trademark of Proofpoint, Inc. 41US Patent Numbers 6865671, 6986037. 42 | |
| 43+-----------------------+ 44| DIRECTORY PERMISSIONS | 45+-----------------------+ 46 47Sendmail often gets blamed for many problems that are actually the 48result of other problems, such as overly permissive modes on directories. 49For this reason, sendmail checks the modes on system directories and | 25+-----------------------+ 26| DIRECTORY PERMISSIONS | 27+-----------------------+ 28 29Sendmail often gets blamed for many problems that are actually the 30result of other problems, such as overly permissive modes on directories. 31For this reason, sendmail checks the modes on system directories and |
| 50files to determine if they can be trusted. For sendmail to run without 51complaining, you MUST execute the following command: | 32files to determine if can have been trusted. For sendmail to run 33without complaining, you MUST execute the following command: |
| 52 53 chmod go-w / /etc /etc/mail /usr /var /var/spool /var/spool/mqueue 54 chown root / /etc /etc/mail /usr /var /var/spool /var/spool/mqueue 55 56You will probably have to tweak this for your environment (for example, 57some systems put the spool directory into /usr/spool instead of | 34 35 chmod go-w / /etc /etc/mail /usr /var /var/spool /var/spool/mqueue 36 chown root / /etc /etc/mail /usr /var /var/spool /var/spool/mqueue 37 38You will probably have to tweak this for your environment (for example, 39some systems put the spool directory into /usr/spool instead of |
| 58/var/spool). If you set the RunAsUser option in your sendmail.cf, the 59/var/spool/mqueue directory will have to be owned by the RunAsUser user. 60As a general rule, after you have compiled sendmail, run the command | 40/var/spool and use /etc/mail for aliases file instead of /etc). If you 41set the RunAsUser option in your sendmail.cf, the /var/spool/mqueue 42directory will have to be owned by the RunAsUser user. As a general rule, 43after you have compiled sendmail, run the command |
| 61 62 sendmail -v -bi 63 64to initialize the alias database. If it gives messages such as 65 66 WARNING: writable directory /etc | 44 45 sendmail -v -bi 46 47to initialize the alias database. If it gives messages such as 48 49 WARNING: writable directory /etc |
| 67 WARNING: writable directory /var/spool/mqueue | 50 WARNING: writable directory /usr/spool/mqueue |
| 68 69then the directories listed have inappropriate write permissions and 70should be secured to avoid various possible security attacks. 71 72Beginning with sendmail 8.9, these checks have become more strict to 73prevent users from being able to access files they would normally not 74be able to read. In particular, .forward and :include: files in unsafe 75directory paths (directory paths which are group or world writable) will --- 16 unchanged lines hidden (view full) --- 92 O DontBlameSendmail=forwardfileinunsafedirpath, 93 forwardfileinunsafedirpathsafe 94 95The first flag allows the .forward file to be read, the second allows 96the items in the file to be marked as safe for file and program 97delivery. 98 99Other files affected by this strengthened security include class | 51 52then the directories listed have inappropriate write permissions and 53should be secured to avoid various possible security attacks. 54 55Beginning with sendmail 8.9, these checks have become more strict to 56prevent users from being able to access files they would normally not 57be able to read. In particular, .forward and :include: files in unsafe 58directory paths (directory paths which are group or world writable) will --- 16 unchanged lines hidden (view full) --- 75 O DontBlameSendmail=forwardfileinunsafedirpath, 76 forwardfileinunsafedirpathsafe 77 78The first flag allows the .forward file to be read, the second allows 79the items in the file to be marked as safe for file and program 80delivery. 81 82Other files affected by this strengthened security include class |
| 100files (i.e., Fw /etc/mail/local-host-names), persistent host status files, 101and the files specified by the ErrorHeader and HelpFile options. Similar | 83files (i.e. Fw /etc/sendmail.cw), persistent host status files, and 84the files specified by the ErrorHeader and HelpFile options. Similar |
| 102DontBlameSendmail flags are available for the class, ErrorHeader, and 103HelpFile files. 104 105If you have an unsafe configuration of .forward and :include: 106files, you can make it safe by finding all such files, and doing 107a "chmod go-w $FILE" on each. Also, do a "chmod go-w $DIR" for 108each directory in the file's path. 109 110 | 85DontBlameSendmail flags are available for the class, ErrorHeader, and 86HelpFile files. 87 88If you have an unsafe configuration of .forward and :include: 89files, you can make it safe by finding all such files, and doing 90a "chmod go-w $FILE" on each. Also, do a "chmod go-w $DIR" for 91each directory in the file's path. 92 93 |
| 111+--------------------------+ 112| FILE AND MAP PERMISSIONS | 113+--------------------------+ | 94+--------------+ 95| MANUAL PAGES | 96+--------------+ |
| 114 | 97 |
| 115Any application which uses either flock() or fcntl() style locking or 116other APIs that use one of these locking methods (such as open() with 117O_EXLOCK and O_SHLOCK) on files readable by other local untrusted users 118may be susceptible to local denial of service attacks. | 98The sendmail manual pages use contemporary Berkeley troff macros. If 99your system does not process these manual pages, you can pick up the 100new macros in a BSD Net/2 FTP site (e.g. on FTP.UU.NET, the files 101/systems/unix/bsd-sources/share/tmac/*). |
| 119 | 102 |
| 120File locking is used throughout sendmail for a variety of files 121including aliases, maps, statistics, and the pid file. Any user who 122can open one of these files can prevent sendmail or it's associated 123utilities, e.g., makemap or newaliases, from operating properly. This 124can also affect sendmail's ability to update status files such as 125statistics files. For system which use flock() for file locking, a 126user's ability to obtain an exclusive lock prevents other sendmail 127processes from reading certain files such as alias or map databases. | 103The strip.sed file is only used in installation. |
| 128 | 104 |
| 129A workaround for this problem is to protect all sendmail files such 130that they can't be opened by untrusted users. As long as users can 131not open a file, they can not lock it. Since queue files should 132already have restricted permissions, the only files that need 133adjustment are alias, map, statistics, and pid files. These files 134should be owned by root or the trusted user specified in the 135TrustedUser option. Changing the permissions to be only readable and 136writable by that user is sufficient to avoid the denial of service. 137For example, depending on the paths you use, these commands would be 138used: | 105After installation, edit tmac.doc and tmac.andoc to reflect the 106installation path of the tmac files. Those files contain pointers to 107/usr/share/tmac/, and those pointers are not changed by the `make 108install` process. There's also a bug in those files -- make the 109following patch: |
| 139 | 110 |
| 140 chmod 0640 /etc/mail/aliases /etc/mail/aliases.{db,pag,dir} 141 chmod 0640 /etc/mail/*.{db,pag,dir} 142 chmod 0640 /etc/mail/statistics /var/log/sendmail.st 143 chmod 0600 /var/run/sendmail.pid /etc/mail/sendmail.pid | 111*** tmac.an~ Tue Jul 12 14:29:09 1994 112--- tmac.an Fri Jul 15 13:17:54 1994 113*************** 114*** 50,55 **** 115 .de TH 116 .rn TH xX 117 .so /usr/share/lib/tmac/tmac.an.old 118! .TH \\$1 \\$2 \\$3 \\$4 \\$5 \\$6 \\$7 \\$8 119 .rm xX 120 .. 121--- 50,55 ---- 122 .de TH 123 .rn TH xX 124 .so /usr/share/lib/tmac/tmac.an.old 125! .TH "\\$1" "\\$2" "\\$3" "\\$4" "\\$5" "\\$6" "\\$7" "\\$8" 126 .rm xX 127 .. |
| 144 | 128 |
| 145If the permissions 0640 are used, be sure that only trusted users belong 146to the group assigned to those files. Otherwise, files should not even 147be group readable. As of sendmail 8.12.4, the permissions shown above 148are the default permissions for newly created files. | 129Rename the existing tmac.an to be tmac.an.old, and rename tmac.andoc 130to be tmac.an. |
| 149 | 131 |
| 150Note that the denial of service on the plain text aliases file 151(/etc/mail/aliases) only prevents newaliases from rebuilding the 152aliases file. The same is true for the database files on systems which 153use fcntl() style locking. Since it does not interfere with normal 154operations, sites may chose to leave these files readable. Also, it is 155not necessary to protect the text files associated with map databases 156as makemap does not lock those files. | 132tmac.an will choose between tmac.an.old, your old macros, or tmac.doc, 133which are the new macros, so that both the new man pages and the 134existing man pages will be translated properly. |
| 157 | 135 |
| 136I'm also told that the groff distribution from MIT has a tmac.doc 137macro set that is compatible with these macros. |
|
| 158 | 138 |
| 139 |
|
| 159+-----------------------+ 160| RELATED DOCUMENTATION | 161+-----------------------+ 162 163There are other files you should read. Rooted in this directory are: 164 | 140+-----------------------+ 141| RELATED DOCUMENTATION | 142+-----------------------+ 143 144There are other files you should read. Rooted in this directory are: 145 |
| 146 doc/changes/changes.ps 147 Describes changes between Release 5 and Release 8 of sendmail. 148 There are some things that may behave somewhat differently. 149 For example, the rules governing when :include: files will 150 be read have been tightened up for security reasons. |
|
| 165 FAQ | 151 FAQ |
| 166 The FAQ (frequently answered questions) is no longer maintained 167 with the sendmail release. It is available at 168 http://www.sendmail.org/faq/ . The file FAQ is a reminder of 169 this and a pointer to the web page. 170 INSTALL 171 Installation instructions for building and installing sendmail. | 152 Answers to Frequently Asked Questions. |
| 172 KNOWNBUGS | 153 KNOWNBUGS |
| 173 Known bugs in the current release. | 154 Known bugs in the current release. I try to keep this up 155 to date -- get the latest version from FTP.Sendmail.ORG 156 in /ucb/sendmail/KNOWNBUGS. |
| 174 RELEASE_NOTES 175 A detailed description of the changes in each version. This 176 is quite long, but informative. | 157 RELEASE_NOTES 158 A detailed description of the changes in each version. This 159 is quite long, but informative. |
| 177 sendmail/README | 160 src/README |
| 178 Details on compiling and installing sendmail. 179 cf/README 180 Details on configuring sendmail. 181 doc/op/op.me | 161 Details on compiling and installing sendmail. 162 cf/README 163 Details on configuring sendmail. 164 doc/op/op.me |
| 182 The sendmail Installation & Operations Guide. In addition 183 to the shipped PostScript version, plain text and PDF versions 184 can be generating using (assuming the required conversion software 185 is installed on your system, see doc/op/Makefile): | 165 The sendmail Installation & Operations Guide. Be warned: if 166 you are running this off on SunOS or some other system with an 167 old version of -me, you need to add the following macro to the 168 macros: |
| 186 | 169 |
| 187 cd doc/op && make op.txt op.pdf 188 189 Be warned: on some systems calling make in doc/op/ will cause 190 errors due to nroff/groff problems. Known problems are: 191 - running this off on systems with an old version of -me, you 192 need to add the following macro to the macros: 193 | |
| 194 .de sm 195 \s-1\\$1\\s0\\$2 196 .. 197 198 This sets a word in a smaller pointsize. 199 | 170 .de sm 171 \s-1\\$1\\s0\\$2 172 .. 173 174 This sets a word in a smaller pointsize. 175 |
| 200 - with new groff versions (1.18 seems affected) | |
| 201 | 176 |
| 202 GROFF_NO_SGR=1 203 204 needs to be set, e.g., in doc/op/Makefile: 205 206 ROFF_CMD= GROFF_NO_SGR=1 groff 207 208 | |
| 209+--------------+ 210| RELATED RFCS | 211+--------------+ 212 213There are several related RFCs that you may wish to read -- they are | 177+--------------+ 178| RELATED RFCS | 179+--------------+ 180 181There are several related RFCs that you may wish to read -- they are |
| 214available from several sites, see | 182available via anonymous FTP to several sites, including: |
| 215 | 183 |
| 216 http://www.rfc-editor.org/ | 184 ftp://nic.ddn.mil/rfc/ 185 ftp://nis.nsf.net/documents/rfc/ 186 ftp://nisc.jvnc.net/rfc/ 187 ftp://venera.isi.edu/in-notes/ 188 ftp://wuarchive.wustl.edu/doc/rfc/ 189 190For a list of the primary repositories see: 191 192 http://www.isi.edu/in-notes/rfc-retrieval.txt 193 194They are also online at: 195 |
| 217 http://www.ietf.org/ 218 | 196 http://www.ietf.org/ 197 |
| 198They can also be retrieved via electronic mail by sending 199email to one of: 200 201 mail-server@nisc.sri.com 202 Put "send rfcNNN" in message body 203 nis-info@nis.nsf.net 204 Put "send RFCnnn.TXT-1" in message body 205 sendrfc@jvnc.net 206 Put "RFCnnn" as Subject: line 207 208For further instructions see: 209 210 http://www.isi.edu/in-notes/rfc-editor/rfc-info 211 |
|
| 219Important RFCs for electronic mail are: 220 221 RFC821 SMTP protocol 222 RFC822 Mail header format 223 RFC974 MX routing 224 RFC976 UUCP mail format 225 RFC1123 Host requirements (modifies 821, 822, and 974) | 212Important RFCs for electronic mail are: 213 214 RFC821 SMTP protocol 215 RFC822 Mail header format 216 RFC974 MX routing 217 RFC976 UUCP mail format 218 RFC1123 Host requirements (modifies 821, 822, and 974) |
| 226 RFC1344 Implications of MIME for Internet Mail Gateways | |
| 227 RFC1413 Identification server | 219 RFC1413 Identification server |
| 228 RFC1428 Transition of Internet Mail from Just-Send-8 to 229 8-bit SMTP/MIME 230 RFC1652 SMTP Service Extension for 8bit-MIMEtransport | |
| 231 RFC1869 SMTP Service Extensions (ESMTP spec) | 220 RFC1869 SMTP Service Extensions (ESMTP spec) |
| 221 RFC1652 SMTP Service Extension for 8bit-MIMEtransport |
|
| 232 RFC1870 SMTP Service Extension for Message Size Declaration | 222 RFC1870 SMTP Service Extension for Message Size Declaration |
| 223 RFC2045 Multipurpose Internet Mail Extensions (MIME) Part One: 224 Format of Internet Message Bodies 225 RFC1344 Implications of MIME for Internet Mail Gateways 226 RFC1428 Transition of Internet Mail from Just-Send-8 to 227 8-bit SMTP/MIME |
|
| 233 RFC1891 SMTP Service Extension for Delivery Status Notifications 234 RFC1892 Multipart/Report Content Type for the Reporting of 235 Mail System Administrative Messages 236 RFC1893 Enhanced Mail System Status Codes 237 RFC1894 An Extensible Message Format for Delivery Status 238 Notifications 239 RFC1985 SMTP Service Extension for Remote Message Queue Starting | 228 RFC1891 SMTP Service Extension for Delivery Status Notifications 229 RFC1892 Multipart/Report Content Type for the Reporting of 230 Mail System Administrative Messages 231 RFC1893 Enhanced Mail System Status Codes 232 RFC1894 An Extensible Message Format for Delivery Status 233 Notifications 234 RFC1985 SMTP Service Extension for Remote Message Queue Starting |
| 240 RFC2033 Local Mail Transfer Protocol (LMTP) 241 RFC2034 SMTP Service Extension for Returning Enhanced Error Codes 242 RFC2045 Multipurpose Internet Mail Extensions (MIME) Part One: 243 Format of Internet Message Bodies 244 RFC2476 Message Submission 245 RFC2487 SMTP Service Extension for Secure SMTP over TLS 246 RFC2554 SMTP Service Extension for Authentication 247 RFC2821 Simple Mail Transfer Protocol 248 RFC2822 Internet Message Format 249 RFC2852 Deliver By SMTP Service Extension 250 RFC2920 SMTP Service Extension for Command Pipelining | |
| 251 252Other standards that may be of interest (but which are less directly 253relevant to sendmail) are: 254 255 RFC987 Mapping between RFC822 and X.400 256 RFC1049 Content-Type header field (extension to RFC822) 257 258Warning to AIX users: this version of sendmail does not implement 259MB, MR, or MG DNS resource records, as defined (as experiments) in 260RFC1035. 261 262 | 235 236Other standards that may be of interest (but which are less directly 237relevant to sendmail) are: 238 239 RFC987 Mapping between RFC822 and X.400 240 RFC1049 Content-Type header field (extension to RFC822) 241 242Warning to AIX users: this version of sendmail does not implement 243MB, MR, or MG DNS resource records, as defined (as experiments) in 244RFC1035. 245 246 |
| 263+---------+ 264| WARNING | 265+---------+ 266 267Since sendmail 8.11 and later includes hooks to cryptography, the 268following information from OpenSSL applies to sendmail as well. 269 270PLEASE REMEMBER THAT EXPORT/IMPORT AND/OR USE OF STRONG CRYPTOGRAPHY 271SOFTWARE, PROVIDING CRYPTOGRAPHY HOOKS OR EVEN JUST COMMUNICATING 272TECHNICAL DETAILS ABOUT CRYPTOGRAPHY SOFTWARE IS ILLEGAL IN SOME 273PARTS OF THE WORLD. SO, WHEN YOU IMPORT THIS PACKAGE TO YOUR 274COUNTRY, RE-DISTRIBUTE IT FROM THERE OR EVEN JUST EMAIL TECHNICAL 275SUGGESTIONS OR EVEN SOURCE PATCHES TO THE AUTHOR OR OTHER PEOPLE 276YOU ARE STRONGLY ADVISED TO PAY CLOSE ATTENTION TO ANY EXPORT/IMPORT 277AND/OR USE LAWS WHICH APPLY TO YOU. THE AUTHORS ARE NOT LIABLE FOR 278ANY VIOLATIONS YOU MAKE HERE. SO BE CAREFUL, IT IS YOUR RESPONSIBILITY. 279 280If you use OpenSSL then make sure you read their README file which 281contains information about patents etc. 282 283 | |
| 284+-------------------+ 285| DATABASE ROUTINES | 286+-------------------+ 287 288IF YOU WANT TO RUN THE NEW BERKELEY DB SOFTWARE: **** DO NOT **** 289use the version that was on the Net2 tape -- it has a number of 290nefarious bugs that were bad enough when I got them; you shouldn't have 291to go through the same thing. Instead, get a new version via the web at 292http://www.sleepycat.com/. This software is highly recommended; it gets 293rid of several stupid limits, it's much faster, and the interface is 294nicer to animals and plants. If the Berkeley DB include files 295are installed in a location other than those which your compiler searches, 296you will need to provide that directory when building: 297 | 247+-------------------+ 248| DATABASE ROUTINES | 249+-------------------+ 250 251IF YOU WANT TO RUN THE NEW BERKELEY DB SOFTWARE: **** DO NOT **** 252use the version that was on the Net2 tape -- it has a number of 253nefarious bugs that were bad enough when I got them; you shouldn't have 254to go through the same thing. Instead, get a new version via the web at 255http://www.sleepycat.com/. This software is highly recommended; it gets 256rid of several stupid limits, it's much faster, and the interface is 257nicer to animals and plants. If the Berkeley DB include files 258are installed in a location other than those which your compiler searches, 259you will need to provide that directory when building: 260 |
| 298 ./Build -I/path/to/include/directory | 261 Build -I/path/to/include/directory |
| 299 300If you are using Berkeley DB versions 1.85 or 1.86, you are *strongly* | 262 263If you are using Berkeley DB versions 1.85 or 1.86, you are *strongly* |
| 301urged to upgrade to DB version 2 or later, available from 302http://www.sleepycat.com/. Berkeley DB versions 1.85 and 1.86 are known to 303be broken in various nasty ways (see http://www.sleepycat.com/db.185.html), 304and can cause sendmail to dump core. In addition, the newest versions of 305gcc and the Solaris compilers perform optimizations in those versions that 306may cause fairly random core dumps. | 264urged to upgrade to DB version 2, available from http://www.sleepycat.com/. 265Berkeley DB versions 1.85 and 1.86 are known to be broken in various nasty 266ways (see http://www.sleepycat.com/db.185.html), and can cause sendmail 267to dump core. In addition, the newest versions of gcc and the Solaris 268compilers perform optimizations in those versions that may cause fairly 269random core dumps. |
| 307 308If you have no choice but to use Berkeley DB 1.85 or 1.86, and you are 309using both Berkeley DB and files in the UNIX ndbm format, remove ndbm.h 310and ndbm.o from the DB library after building it. You should also apply 311all of the patches for DB 1.85 and 1.86 found at the Sleepycat web site 312(see http://www.sleepycat.com/db.185.html), as they fix some of the known 313problems. 314 315If you are using a version of Berkeley DB 2 previous to 2.3.15, and you 316are using both Berkeley DB and files in the UNIX ndbm format, remove dbm.o 317from the DB library after building it. No other changes are necessary. 318 319If you are using Berkeley DB version 2.3.15 or greater, no changes are 320necessary. 321 322The underlying database file formats changed between Berkeley DB versions | 270 271If you have no choice but to use Berkeley DB 1.85 or 1.86, and you are 272using both Berkeley DB and files in the UNIX ndbm format, remove ndbm.h 273and ndbm.o from the DB library after building it. You should also apply 274all of the patches for DB 1.85 and 1.86 found at the Sleepycat web site 275(see http://www.sleepycat.com/db.185.html), as they fix some of the known 276problems. 277 278If you are using a version of Berkeley DB 2 previous to 2.3.15, and you 279are using both Berkeley DB and files in the UNIX ndbm format, remove dbm.o 280from the DB library after building it. No other changes are necessary. 281 282If you are using Berkeley DB version 2.3.15 or greater, no changes are 283necessary. 284 285The underlying database file formats changed between Berkeley DB versions |
| 3231.85 and 1.86, again between DB 1.86 and version 2.0, and finally between 324DB 2.X and 3.X. If you are upgrading from one of those versions, you must 325recreate your database file(s). Do this by rebuilding all maps with 326makemap and rebuilding the alias file with newaliases. | 2861.85 and 1.86, and again between DB 1.86 and version 2.0. If you are 287upgrading from one of those versions, you must recreate your database 288file(s). Do this by rebuilding all maps with makemap and rebuilding the 289alias file with newaliases. |
| 327 328 329+--------------------+ 330| HOST NAME SERVICES | 331+--------------------+ 332 333If you are using NIS or /etc/hosts, it is critical that you 334list the long (fully qualified) name somewhere (preferably first) in --- 26 unchanged lines hidden (view full) --- 361install it. 362 363 364+----------------+ 365| USE WITH IDENT | 366+----------------+ 367 368Sendmail 8 supports the IDENT protocol, as defined by RFC 1413. | 290 291 292+--------------------+ 293| HOST NAME SERVICES | 294+--------------------+ 295 296If you are using NIS or /etc/hosts, it is critical that you 297list the long (fully qualified) name somewhere (preferably first) in --- 26 unchanged lines hidden (view full) --- 324install it. 325 326 327+----------------+ 328| USE WITH IDENT | 329+----------------+ 330 331Sendmail 8 supports the IDENT protocol, as defined by RFC 1413. |
| 369Note that the RFC states a client should wait at least 30 seconds 370for a response. As of 8.10.0, the default Timeout.ident is 5 seconds 371as many sites have adopted the practice of dropping IDENT queries. 372This has lead to delays processing mail. | 332No ident server is included with this distribution. I have found 333copies available on: |
| 373 | 334 |
| 374No ident server is included with this distribution. It is available 375from: | 335 ftp.lysator.liu.se /pub/ident/servers 336 romulus.ucs.uoknor.edu /networking/ident/servers 337 ftp.cyf-kr.edu.pl /agh/uciagh/network/ident |
| 376 | 338 |
| 377 ftp://ftp.lysator.liu.se/pub/ident/servers/ 378 http://sf.www.lysator.liu.se/~pen/pidentd/ | 339If you want to run an IDENT server, I suggest getting a copy from 340one of those sites. Versions are available for several different 341systems, including Apollo, BSD, NeXT, AIX, TOPS20, and VMS. |
| 379 | 342 |
| 380+-------------------------+ 381| INTEROPERATION PROBLEMS | 382+-------------------------+ | |
| 383 | 343 |
| 384Microsoft Exchange Server 5.0 385 We have had a report that ``about 7% of messages from Sendmail 386 to Exchange were not being delivered with status messages of 387 "connection reset" and "I/O error".'' Upgrading Exchange from 388 Version 5.0 to Version 5.5 Service Pack 2 solved this problem. 389 390CommuniGate Pro 391 CommuniGate Pro 3.2.4 does not accept the AUTH= -parameter on 392 the MAIL FROM command if the client is not authenticated. Use 393 394 define(`confAUTH_OPTIONS', `A') 395 396 in .mc file if you have compiled sendmail with Cyrus SASL 397 and you communicate with CommuniGate Pro servers. 398 | |
| 399+---------------------+ 400| DIRECTORY STRUCTURE | 401+---------------------+ 402 403The structure of this directory tree is: 404 405cf Source for sendmail configuration files. These are 406 different than what you've seen before. They are a 407 fairly dramatic rewrite, requiring the new sendmail 408 (since they use new features). 409contrib Some contributed tools to help with sendmail. THESE 410 ARE NOT SUPPORTED by sendmail -- contact the original 411 authors if you have problems. (This directory is not 412 on the 4.4BSD tape.) | 344+---------------------+ 345| DIRECTORY STRUCTURE | 346+---------------------+ 347 348The structure of this directory tree is: 349 350cf Source for sendmail configuration files. These are 351 different than what you've seen before. They are a 352 fairly dramatic rewrite, requiring the new sendmail 353 (since they use new features). 354contrib Some contributed tools to help with sendmail. THESE 355 ARE NOT SUPPORTED by sendmail -- contact the original 356 authors if you have problems. (This directory is not 357 on the 4.4BSD tape.) |
| 413devtools Build environment. See devtools/README. | |
| 414doc Documentation. If you are getting source, read 415 op.me -- it's long, but worth it. | 358doc Documentation. If you are getting source, read 359 op.me -- it's long, but worth it. |
| 416editmap A program to edit and query maps that have been created 417 with makemap, e.g., adding and deleting entries. 418include Include files used by multiple programs in the distribution. 419libsmdb sendmail database library with support for Berkeley DB 1.X, 420 Berkeley DB 2.X, Berkeley DB 3.X, and NDBM. 421libsmutil sendmail utility library with functions used by different 422 programs. | |
| 423mail.local The source for the local delivery agent used for 4.4BSD. 424 THIS IS NOT PART OF SENDMAIL! and may not compile 425 everywhere, since it depends on some 4.4-isms. Warning: 426 it does mailbox locking differently than other systems. | 360mail.local The source for the local delivery agent used for 4.4BSD. 361 THIS IS NOT PART OF SENDMAIL! and may not compile 362 everywhere, since it depends on some 4.4-isms. Warning: 363 it does mailbox locking differently than other systems. |
| 427mailstats Statistics printing program. | 364mailstats Statistics printing program. It has the pathname of 365 sendmail.st compiled in, so if you've changed that, 366 beware. |
| 428makemap A program that creates the keyed maps used by the $( ... $) 429 construct in sendmail. It is primitive but effective. 430 It takes a very simple input format, so you will probably 431 expect to preprocess must human-convenient formats 432 using sed scripts before this program will like them. 433 But it should be functionally complete. 434praliases A program to print the DBM or NEWDB version of the 435 aliases file. 436rmail Source for rmail(8). This is used as a delivery 437 agent for for UUCP, and could presumably be used by 438 other non-socket oriented mailers. Older versions of 439 rmail are probably deficient. RMAIL IS NOT PART OF 440 SENDMAIL!!! The 4.4BSD source is included for you to | 367makemap A program that creates the keyed maps used by the $( ... $) 368 construct in sendmail. It is primitive but effective. 369 It takes a very simple input format, so you will probably 370 expect to preprocess must human-convenient formats 371 using sed scripts before this program will like them. 372 But it should be functionally complete. 373praliases A program to print the DBM or NEWDB version of the 374 aliases file. 375rmail Source for rmail(8). This is used as a delivery 376 agent for for UUCP, and could presumably be used by 377 other non-socket oriented mailers. Older versions of 378 rmail are probably deficient. RMAIL IS NOT PART OF 379 SENDMAIL!!! The 4.4BSD source is included for you to |
| 441 look at or try to port to your system. There is no 442 guarantee it will even compile on your operating system. | 380 look at or try to port to your system. I know it doesn't 381 compile on {SunOS, HP-UX, OSF/1, other} (pick one). |
| 443smrsh The "sendmail restricted shell", which can be used as 444 a replacement for /bin/sh in the prog mailer to provide 445 increased security control. NOT PART OF SENDMAIL! | 382smrsh The "sendmail restricted shell", which can be used as 383 a replacement for /bin/sh in the prog mailer to provide 384 increased security control. NOT PART OF SENDMAIL! |
| 446sendmail Source for the sendmail program itself. | 385src Source for the sendmail program itself. |
| 447test Some test scripts (currently only for compilation aids). | 386test Some test scripts (currently only for compilation aids). |
| 448vacation Source for the vacation program. NOT PART OF SENDMAIL! 449 450$Revision: 8.96 $, Last updated $Date: 2013-11-22 20:51:01 $ | |