|
0
|
1 .\" @(MHWARNING)
|
|
12
|
2 .\" @(#)$Id: mh-mts.rf,v 1.1.1.1 2005/04/18 14:46:03 kono Exp $
|
|
0
|
3 .SC MH-MTS 8
|
|
|
4 .NA
|
|
|
5 mh-mts \- the MH interface to the message transport system
|
|
|
6 .SY
|
|
|
7 SendMail
|
|
|
8
|
|
|
9 .ti .5i
|
|
|
10 Zmailer
|
|
|
11
|
|
|
12 .ti .5i
|
|
|
13 MMDF (any release)
|
|
|
14
|
|
|
15 .ti .5i
|
|
|
16 stand\-alone
|
|
|
17 .DE
|
|
|
18 \fIMH\fR can use a wide range of message transport systems to deliver mail.
|
|
|
19 Although the \fIMH\fR administrator usually doesn't get to choose which MTS
|
|
|
20 to use (since it's already in place),
|
|
|
21 this document briefly describes the interfaces.
|
|
|
22
|
|
|
23 When communicating with \fISendMail\fR,
|
|
|
24 \fIMH\fR always uses the SMTP to post mail.
|
|
|
25 Depending on the \fIMH\fR configuration,
|
|
|
26 \fISendMail\fR may be invoked directly (via a \fIfork\fR and an \fIexec\fR),
|
|
|
27 or \fIMH\fR may open a TCP/IP connection to the SMTP server on the localhost.
|
|
|
28
|
|
|
29 When communicating with \fIzmailer\fP,
|
|
|
30 the \fISendMail\fP compatibility program is
|
|
|
31 required to be installed in /usr/lib.
|
|
|
32 \fIMH\fP communicates with \fIzmailer\fP
|
|
|
33 by using the SMTP.
|
|
|
34 It does this by invoking the \fB/usr/lib/sendmail\fP
|
|
|
35 compatibility program directly, with the `\-bs' option.
|
|
|
36
|
|
|
37 When communicating with \fIMMDF\fR,
|
|
|
38 normally \fIMH\fR uses the \*(lqmm\(ru\*(rq routines to post mail.
|
|
|
39 However, depending on the \fIMH\fR configuration,
|
|
|
40 \fIMH\fR instead may open a TCP/IP connection to the SMTP server on the
|
|
|
41 localhost.
|
|
|
42
|
|
|
43 When using the stand\-alone system (\fBNOT\fR recommended),
|
|
|
44 \fIMH\fR delivers local mail itself and queues \fIUUCP\fR and network mail.
|
|
|
45 The network mail portion will probably have to be modified to reflect the
|
|
|
46 local host's tastes, since there is no well\-known practice in this area for
|
|
|
47 all types of UNIX hosts.
|
|
|
48
|
|
|
49 If you are running a UNIX system with TCP/IP networking,
|
|
|
50 then it is felt that the best interface is achieved by using either
|
|
|
51 \fISendMail\fR or \fIMMDF\fR with the SMTP option.
|
|
|
52 This gives greater flexibility.
|
|
|
53 To enable this option you append the /smtp suffix to the mts option in the
|
|
|
54 \fIMH\fR configuration.
|
|
|
55 This yields two primary advantages:
|
|
|
56 First,
|
|
|
57 you don't have to know where \fIsubmit\fR or \fISendMail\fR live.
|
|
|
58 This means that \fIMH\fR binaries (e.g., \fIpost\fR\0)
|
|
|
59 don't have to have this information hard\-coded,
|
|
|
60 or can run different programs altogether;
|
|
|
61 and,
|
|
|
62 second, you can post mail with the server on different systems, so you don't
|
|
|
63 need either \fIMMDF\fR or \fISendMail\fR on your local host.
|
|
|
64 Big win in conserving cycles and disk space.
|
|
|
65 Since \fIMH\fR supports the notion of a server search\-list in this respect,
|
|
|
66 this approach can be tolerant of faults.
|
|
|
67 Be sure to set \*(lqservers:\*(rq as described in
|
|
|
68 mh\-tailor(8) if you use this option.
|
|
|
69
|
|
|
70 There are four disadvantages to using the SMTP option:
|
|
|
71 First, only UNIX systems with TCP/IP are supported.
|
|
|
72 Second, you need to have an SMTP server running somewhere on any network your
|
|
|
73 local host can reach.
|
|
|
74 Third, this bypasses any authentication mechanisms in \fIMMDF\fR
|
|
|
75 or \fISendMail\fR.
|
|
|
76 Fourth,
|
|
|
77 the file \fB/etc/hosts\fR is used for hostname lookups
|
|
|
78 (although there is an exception file).
|
|
|
79 In response to these disadvantages though:
|
|
|
80 First, there's got to be an SMTP server somewhere around if you're in the
|
|
|
81 Internet or have a local network.
|
|
|
82 Since the server search\-list is very general,
|
|
|
83 a wide\-range of options are possible.
|
|
|
84 Second,
|
|
|
85 SMTP should be fixed to have authentication mechanisms in it, like POP.
|
|
|
86 Third,
|
|
|
87 \fIMH\fR won't choke on mail to hosts whose official names it can't verify,
|
|
|
88 it'll just plug along
|
|
|
89 (and besides
|
|
|
90 if you enable the BERK or DUMB configuration options,
|
|
|
91 \fIMH\fR ignores the hosts file altogether).
|
|
|
92 .Fi
|
|
|
93 ^@(MHETCPATH)/mtstailor~^tailor file
|
|
|
94 .Pr
|
|
|
95 None
|
|
|
96 .Sa
|
|
|
97 \fIMMDF\-II: A Technical Review\fR,
|
|
|
98 Proceedings, Usenix Summer '84 Conference
|
|
|
99 .br
|
|
|
100 \fISENDMAIL \-\- An Internetwork Mail Router\fR
|
|
|
101 .br
|
|
|
102 mh\-tailor(8), post(8)
|
|
|
103 .De
|
|
|
104 None
|
|
|
105 .Co
|
|
|
106 None
|
|
|
107 .Bu
|
|
|
108 The @(MHETCPATH)/mtstailor file ignores the information in the \fIMMDF\-II\fR
|
|
|
109 tailoring file.
|
|
|
110 It should not.
|
|
|
111 .En
|
