DataMuseum.dk

Presents historical artifacts from the history of:

DKUUG/EUUG Conference tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about DKUUG/EUUG Conference tapes

Excavated with: AutoArchaeologist - Free & Open Source Software. 

top - metrics - download
Index: T r

⟦b5656136e⟧ TextFile

    Length: 938 (0x3aa)
    Types: TextFile
    Names: »rfc2or.8«

Derivation

└─⟦2d1937cfd⟧ Bits:30007241 EUUGD22: P.P 5.0
    └─⟦dc59850a2⟧ »EurOpenD22/pp5.0/pp-5.tar.Z« 
        └─⟦e5a54fb17⟧ 
            └─⟦this⟧ »pp-5.0/man/man8/rfc2or.8«

TextFile

.TH RFC2OR 8
.\" @(#) $Header: /cs/research/pp/hubris/pp-beta/man/man8/RCS/rfc2or.8,v 5.0 90/09/20 16:55:35 pp Exp Locker: pp $
.\"
.\" $Log:	rfc2or.8,v $
.\" Revision 5.0  90/09/20  16:55:35  pp
.\" rcsforce : 5.0 public release
.\" 
.\"
.SH NAME
rfc2or \- Converts RFC 822 addresses into X.400 O/R Names.
.SH SYNOPSIS
.in +.5i
.ti -.5i
rfc2or [address...]
.in -.5i
.SH DESCRIPTION
.I rfc2or
converts an RFC 822 address into a X.400 O/R Name. To do this
the or_rfc2or and or_or2rfc routines are used, which in turn
make use of the rfc2or and or2rfc mapping tables.
.PP
This routine can be used as a diagnostic tool as well. As it
will identify any asymmetrical discrepancies between the two
mapping tables.
.SH FILES
rfc2or and or2rfc in the tbldfldir.
.SH "SEE ALSO"
or (3).
.br
or (5).
.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