PMDF System Manager's Guide
PMDF-REF-6.0

Incoming X.400 messages destined for recipients on the PMDF side of the gateway undergo an inverse address conversion process implemented by the X400_TO_MIME channel and governed by rules contained in the FROM_X400 database. During configuration of PMDF-X400, the ORname fields for the PMDF-X400 gateway (Country, ADMD, PRMD, Organization, and zero or more Organizational-Units) were specified. The X.400 ORname for any recipient on the PMDF side of the gateway consists of the gateway ORname fields plus additional fields to indicate the recipient. These additional fields need to provide sufficient information to identify the recipient on the PMDF side.

Note:

Such recipients are not limited to local PMDF users. Any recipient on any mail system reachable by PMDF, as well as PMDF-MR, PMDF-LAN, and facsimile addresses through PMDF-FAX, is accessible to X.400 originators through PMDF-X400.

The default configuration generated by the PMDF-X400 configuration utility includes support for three X.400 ORname representations for PMDF recipients:

• Recipient address is specified by X.400 ORname fields:

  SURNAME   = Lastname
  GIVENNAME = Firstname
  

  PMDF-X400 will produce the address:

  Firstname.Lastname@PMDF-local-host
  

  
  This representation is likely to be the most natural from the X.400 originator's perspective. A PMDF alias or FORWARD mapping can be used to resolve Firstname.Lastname to a local or remote mailbox.
  
• Recipient address is specified by X.400 ORname field:

  SURNAME = mailbox-name
  

  PMDF-X400 will produce the address:

  mailbox-name@PMDF-local-host
  

  
  This representation is the simplest way for an X.400 originator to represent a local user on the PMDF side of the gateway. Since the surname value could be an OpenVMS username, this will reach the local OpenVMS user without need for aliases or forwarding.
  
• Recipient address is specified by X.400 Domain-Defined attribute RFC822:

  DD.RFC-822 = mailbox-name(a)domain-name
  

  PMDF-X400 will produce the address:

  mailbox-name@domain-name
  

  
  This representation is the most general way for an X.400 originator to represent any address on the PMDF side of the gateway.

  Note that X.400 is limited in the characters that are allowed in ORname fields to the characters defined as members of the "printable string" set. Characters that are used in RFC 822 addresses but not allowed by X.400 are specified by multi-character substitutions in accordance with RFC 2156. These are particularly useful when X.400 originators need to specify a complete RFC 822 address in a DD.RFC-822 domain-defined attribute. The substitutions are listed in Table 41-4 .

  Table 41-4 RFC 2156 printablestring character substitutions ORname in fields

  Desired character	X.400 multi-character
  @	(a)
  %	(p)
  !	(b)
  "	(q)
  _	(u)
  (	(l)
  )	(r)

  For example, to specify the RFC 822 address mrocheck@foobar.com using the DD.RFC-822 attribute, the "@" must be specified as "(a)":

  DD.RFC-822 = mrochek(a)foobar.com 
  

  ---

  Note:

  Since the ( and ) characters delimit comments in RFC 822 addresses, the use of printable string substitutions imposes the additional requirement that any address containing them must be enclosed in double-quotes. For example:

  "/dd.rfc-822=astro(a)pound.com/prmd=Gwy/admd=In/c=us/"@x400.acme.com 
  

  Here, the double quotes are required to prevent the (a) from being discarded by the RFC 822 address processor through which this X.400 address is sent.

  ---

  The basic configuration generated by the PMDF-X400 configuration utility creates databases containing the address conversion rules for these three representations. These database files are pointed to by the PMDF_TO_X400_DATABASE and PMDF_FROM_X400_DATABASE logical names (OpenVMS) or PMDF tailor file options (UNIX).

  ---

  Previous | Next | Contents