| Previous | Contents | Index |
Configurable options relevant to the XAPI interface and the MIME to
X.400 conversion process are specified in the channel option file
xapi_local_option stored in the PMDF table directory,
i.e., in the file PMDF_TABLE:xapi_local_option.
(OpenVMS) or /pmdf/table/xapi_local_option (UNIX).
The format of a channel option file is documented in Section 7.2. The available options are:
BINARY_ENCODING (string)
The BINARY_ENCODING option controls the MIME transfer encoding used when binary format X.400 body parts are converted into MIME body parts. Possible values include BASE64, QUOTED-PRINTABLE, X-UUENCODE and HEXADECIMAL. The standard BASE64 MIME encoding is the default.CLIENT_NAME (string)
The name of the PMDF-MB400 XAPI gateway agent. The default name generated by the PMDF-MB400 configuration utility is "PMDF-MB400".DELETE_HEADERS (0 or 1)
Message headers are normally deleted once they have been successfully mapped into corresponding X.400 information. To save headers that remain after all conversions have been completed, use the SAVE_HEADERS option described below. However, under some circumstances it is useful to be able to skip the deletion step, preserving all header information. The DELETE_HEADERS option provides such a facility. Its normal default value is 1, which means that headers are deleted once converted. If this option is set to 0 converted headers will not be deleted. If the SAVE_HEADERS option is then set to 1 all headers will be saved as a separate text bodypart. If SAVE_HEADERS is set to 0 the DELETE_HEADERS option will have no discernable effect on message conversion.FROM_TO_AUTHOR (0 or 1)
The FROM_TO_AUTHOR option controls the optional mapping of the X.400 FROM field to the AUTHORIZINGUSERS field when no AUTHORIZINGUSERS field is specified. RFC 2156 specifies that when both the RFC 822 From: and Sender: headers are present the From: header be mapped into the AUTHORIZINGUSERS field while the Sender: header gets mapped to the FROM field, and if only a From: header is present it is mapped to the FROM field. The latter case causes problems with applications that incorrectly provide access to just the AUTHORIZINGUSERS field. When set to 1, the FROM_TO_AUTHOR duplicates the FROM information in the AUTHOR field in an attempt to work around this problem. The default value is 0, which inhibits this duplication.FROM_X400_DATABASE (string)
The name of the database file containing address mapping rules can be changed on a per-channel basis by using the FROM_X400_DATABASE option in the XAPI_LOCAL channel option file. If this option is not specified, the database file is referenced via the PMDF_FROM_X400_DATABASE logical name (OpenVMS) or PMDF_FROM_X400_DATABASE option in the PMDF tailor file (UNIX).GENERATE_EIT (0 or 1)
This option controls whether or not an EncodedInformationTypes field is generated in the X.400 P1 information. This is an optional field that rarely provides any useful information. However, some X.400 software requires its presence. The default is 0, which means no such field is generated.MODE (string)
String containing the X.400 conformance level to be used by PMDF-MB400 when converting messages. The default generated by the PMDF-MB400 configuration utility is "1988-NORMAL". The only other valid value is "1984", in which case PMDF-MB400 will generate downgraded messages, compatible with X.400 1984.RESTORE_HEADERS (0 or 1)
The RESTORE_HEADERS option provides the inverse of the operation of the SAVE_HEADERS option described below. Specifically, if RESTORE_HEADERS is set to 1 any headers saved in a special X.400 bodypart will be detected and restored as actual message headers. The format of the bodypart complies with RFC 2156. The default value for this option is 0, which disables the mapping.RHS_ORDER (0 or 1)
The RHS_ORDER option controls controls the direction in which attribute value lists are written into the mailbox part of RFC 822 addresses. The default is 1, which means that attributes are written from right to left. This corresponds to the ordering specified by RFC 2156. In some cases, however, the opposite ordering is required. Note that the read order only affects repeated attributes like Organizational Units.SAVE_HEADERS (0 or 1)
The SAVE_HEADERS option controls the disposition of message headers that cannot be mapped into corresponding X.400 information. The default value is 0, which causes such header information to be discarded. A value of 1 will store such information, if present, in a special text bodypart whose format conforms with RFC 2156.TELETEX_CANCEL (integer)
RFC 2156 specifies that when both a printable-string and teletex-string version of an attribute are present, that the attribute should be represented as
The default setting of TELETEX_CANCEL=0 causes PMDF-MB400 to follow this standard. However, the TELETEX_CANCEL option may be used to cause PMDF-MB400 to instead discard the teletex-string representation. TELETEX_CANCEL takes a bit-encoded integer value, where each bit controls the retention of teletex string information for a particular X.400 attribute, as listed in the table below.
printable-string*teletex-string
Bit Value X.400 Attribute 0 1 Common Name 1 2 Organization 2 4 Surname 3 8 Givenname 4 16 Initials 5 32 Generational Qualifier 6 64 Organizational Unit 7 128 Domain Defined Attributes
| Previous | Next | Contents | Index |