⟦ef40e06a5⟧

TextFile

.TH CHANNEL-TABLE 5
.\" @(#) $Header: /cs/research/pp/hubris/pp-beta/man/man5/RCS/channel-table.5,v 5.0 90/09/20 16:53:57 pp Exp Locker: pp $
.\"
.\" $Log: channel-table.5,v $
.\" Revision 5.0 90/09/20 16:53:57 pp
.\" rcsforce : 5.0 public release
.\"
.\"
.SH NAME
channel-table \- channel table formats
.SH SYNOPSIS
LHS ":" RHS
.SH DESCRIPTION
The channel tables are designed to associate channel specific
information with each destination
.B mta .
Some protocol channels have "forward" tables, for initiating
connections. Some channels also have "reverse" tables, for validating
connections initiated remotely. All channels will have forward
tables, which may or may not be PP tables. For channels which do NOT
use PP tables, a description of how the table function is provided is
made. The format of the Right Hand Side (RHS) of all PP channel
tables and the Left hand Side (LHS) of PP reverse tables varies for
different channels. The Left Hand Side (LHS) of PP forward tables is
always the name of the host, usually in \*(lqfully qualified
form\*(rq. This name may have meaning external to PP, or may simply
be an internal reference from the address lookup tables.
.PP
The individual formats of the channel tables are now considered.
.SS "X-400 Outbound Channels"
X400 channel forward tables follow the format listed below.
This is for use with RTS (1984).
.sp
.nf
.in +5
host: key=value, key=value ...
.in -5
.sp
.fi
The host is the key from the address lookup. This is the remote host to
which the outgoing connection it to be made.
.PP
The parameters can be any mixture of several parameters. These are
described in more detail in \fIThe PP Manual: Volume 1 \- Installation
and Operation\fP.
.SS "X.400 Inbound channels"
The reverse channels are keyed on the inbound
information, of the calling remote host.
This is the major security check.
Any additional checks on passwords are for fun only.
Encoding:
.br
.ti +5
.sp
osi-info:key=value, key=value...
.sp
The parameters are essentially the same as the X.400 outbound channel.
.sp
.SS "SMTP Channels"
The SMTP channels may use either the local /etc/hosts tables, or the
DARPA Domain Service (supplied by BIND) to perform forward and reverse
mappings.
The fully qualified domain name is the host name.
This is used in both directions.
.in -5
.sp
.SS "JNT Mail Channels"
The JNT Mail channels use the procedural interface to the
\fIunix-niftp\fP package which will access the NRS database for
forward and reverse lookup. The fully qualified standard form domain
name IN RFC 822 ORDER is used as the host name (the ordering is to
prevent clashes with SMTP hosts). This is translated to the nrs format
before lookup. The associated X.25 network is found in the channels
info parameter.
.in -5
.sp
.SS "Local Channels"
There will be a number of Local channels, and there will be
tables for each one.
.PP
For the standard local channel, the table associates the mail user
name with a userid, a home directory and a mailbox.
.SS "List Channels"
The list channels maintain distribution lists. In this case, the table
associates with the list name a list of moderators of the list, the
expansion and a description.
This go together to form lines such as:
.sp
.nf
.in +5
list:moderators,expansion,description
.in -5
.sp
.fi
.SS "Shell Channel"
The shell channel delivers to processes. The table contains mappings
from addresses to processes,the userid to run them under and the
amount of time to allow the processes to run.
These combine to form a line such as:
.sp
.nf
.in +5
address:userid,timeout,commandline
.in -5
.sp
.fi
.SS "UUCP channel"
The UUCP channel table translates from a domain oriented address to a
uucp style address. The RHS may contain a \*(lq%s\*(rq string which is
expanded to the username.
.SH SEE ALSO
users(5), aliases(5).
.sp
\fIThe PP Manual: Volume 1 \- Installation and Operation\fP
.SH FILES
Numerous

DataMuseum.dk

DKUUG/EUUG Conference tapes

⟦ef40e06a5⟧ TextFile

Derivation

TextFile