head     1.5;
branch   ;
access   ;
symbols  ;
locks    ; strict;
comment  @@;


1.5
date     90.04.05.15.15.00;  author sources;  state Exp;
branches ;
next     1.4;

1.4
date     90.03.22.11.31.47;  author sources;  state Exp;
branches ;
next     1.3;

1.3
date     90.03.20.19.42.29;  author sources;  state Exp;
branches ;
next     1.2;

1.2
date     90.03.20.17.36.43;  author sources;  state Exp;
branches ;
next     1.1;

1.1
date     90.03.20.17.21.27;  author sources;  state Exp;
branches ;
next     ;


desc
@@


1.5
log
@add ID
@
text
@.\"	@@(MHWARNING)
.\" @@(#)$Id:$
.SC RMAIL 8
.NA
rmail \- UUCP interface to mail
.SY
rmail
address\ ...
.DE
\fIRmail\fR is intended as a replacement for those systems without
\fISendMail\fR or \fIMMDF\fR.
It is normally invoked by \fIuux\fR on behalf of the remote \fIUUCP\fR site.
For each address, it decides where to send it:
either locally, via another \fIUUCP\fR link, or via the Internet.

\fIRmail\fR implements a crude access control facility by consulting the
files \fBRmail.OkHosts\fR and \fBRmail.OkDests\fR in the \fB@@(MHETCPATH)/\fR
directory.
Hosts listed in the former file can send messages to anywhere they please.
Hosts listed in the latter file can receive messages from anywhere.
Note that a host listed in the first file is implicitly listed in the second
file.
.Fi
^@@(MHETCPATH)/mtstailor~^tailor file
^@@(MHETCPATH)/Rmail.OkHosts~^list of privileged hosts
^@@(MHETCPATH)/Rmail.OkDests~^list of privileged destinations
.Pr
None
.Sa
mf(1)
.De
None
.Co
None
.En
@


1.4
log
@put things back, do .NA stuff another way
@
text
@d2 1
@


1.3
log
@typo
@
text
@d2 2
a3 2
.TH RMAIL 8 @@(MHCENTERFOOT) @@(MHLEFTFOOT)
.SH .NA
d5 1
a5 1
.SH .SY
@


1.2
log
@fixup for makewhatis
@
text
@d2 1
a2 1
.TH RMAIL 8 [mh.6] MH
@


1.1
log
@Initial revision
@
text
@d2 2
a3 2
.SC RMAIL 8
.NA
d5 1
a5 1
.SY
@