|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T o
Length: 1994 (0x7ca) Types: TextFile Names: »or.5«
└─⟦2d1937cfd⟧ Bits:30007241 EUUGD22: P.P 5.0 └─⟦dc59850a2⟧ »EurOpenD22/pp5.0/pp-5.tar.Z« └─⟦e5a54fb17⟧ └─⟦this⟧ »pp-5.0/man/man5/or.5«
.TH OR 5 .\" @(#) $Header: /cs/research/pp/hubris/pp-beta/man/man5/RCS/or.5,v 5.0 90/09/20 16:54:04 pp Exp Locker: pp $ .\" .\" $Log: or.5,v $ .\" Revision 5.0 90/09/20 16:54:04 pp .\" rcsforce : 5.0 public release .\" .\" .SH NAME or \- tables relate to the handling of X.400 O/R Names .SH SYNOPSIS <key> ":" <value> [<value>] .SH DESCRIPTION .PP .I or2rfc is for mapping X.400 O/R Names into RFC 822 addresses. <key> is encoded as \%dmn-orname (see RFC 987) and value as \%domain-syntax (see RFC 987). When mapping, the longest possible match is always looked for. .I rfc2or has the <key> encoded as \%domain-syntax and the <value> as \%dmn-orname. It performs exactly the reverse operation. .PP .I or is used to evaluate O/R Names. The <key> is encoded as \%dmn-orname. The default algorithm for O/R Name analysis should be considered as tree-walking. The O/R name is sorted into order, as defined in .I or (3), and components are looked up: first level 1; then level 1 + level 2: and so on. This table is for performing these repeated lookups. The RHS has four possible encodings: .PP "valid" .IP This means that this part of the tree is OK. .PP "mta"\ <mtaname> .IP This identifes the MTA <mtaname> as being associated with this vertex of the tree. This <mtaname> is a key to the PP channel tables. The search should NOT stop at this point, as further tree searching may determine a more optimal MTA. .PP "alias"\ <dmn-orname> .IP This identifies an alias, and indicates that all O/R components matched so far, should be replaced with those dientified on the RHS, and the search should now resume from the root. .PP "local" .IP This idententifies a local O/R Name. The remainder of the O/R Name should be used, in some manner, to determine a local mailbox. .SH FILES tbldfldir \- The location of the PP tables .SH SEE ALSO .nf or(3) .br RFC 987 (mapping between X.400 and RFC 822). .br RFC 1026 (addendum to RFC 987) .br \fIThe PP Manual: Volume 1 \- Installation and Operation\fP .fi