Novell MHS channels are used to convert messages between the RFC 822 and MIME message formats used by PMDF and the SMF (Standard Message Format) V70 format used by Novell MHS. PMDF can also interoperate with SMF V71 (see below). The Novell MHS channel programs combined with some mechanism to transfer files between systems produces an effective gateway between PMDF and Novell MHS.
SMF-70 is the message format used by Novell MHS version 1.5 in both the Network (1.5N) and Personal (1.5P) products. SMF-71 is the format used by Novell's newer Global Messaging products. PMDF will accept either format. Given the predominance of MHS 1.5 in the marketplace, PMDF generates SMF-70 format messages.
The Novell MHS channel programs attempt to convert as much of MIME as possible to compatible Novell MHS formats. However, limitations in Novell MHS make a complete conversion impossible, so in some cases the conversion will be limited in scope. In particular, Novell MHS is incapable of handling nested multipart structures, so any sense of nested structure is lost in the conversion process.
PMDF's Novell MHS channels perform all the functions of a Novell MHS gateway and appear to Novell MHS as a gateway despite the fact that the channels reside on a separate and independent system.
Note that Novell MHS is purely a message handling system. It includes no user agent. There are numerous Novell MHS compatible user agents available from third parties. These include Beyond's BeyondMail, Da Vinci's eMAIL, and Lantec's XPost among others.
38.8.1 Related Novell documentation
The Novell side reference is the manual NetWare MHS Installation
and Operation, publication number 100-000961-001. The edition used
in preparation of this document was Revision A dated February 15, 1991.
Someone trying to set up a gateway who is unfamiliar with NetWare
should read Chapter One, "Introduction", for an overview of
MHS and its terminology. A very useful graphic showing the MHS
directory structure is Figure A-1 on page A-13.
38.8.2 Telling MHS about PMDF
You should have already installed and configured Novell MHS. Follow
instructions in the Novell NetWare MHS Installation and Operations
manual.
Use the MHS Directory Manager to define PMDFb
as a gateway if you have not already done so. (The following commands
are valid for MHS 1.5, but may differ for different versions of MHS.)
While logged in as the MHS administrator, run the MHS Directory Manager
(usually \MHS\EXE\MHS.EXE) and, select "Manage
Directories", then select "routes to workgroups, hosts, and
gateways", then select "Add entry" and "Define a
gateway" or "Modify entry" if it had been defined
already, then you are on the "A GATEWAY" screen, which should
look like:
Host name: PMDF
Description: Gateway to VMS or whatever
Gateway version: 70
Gateway commands:
After exiting the Directory Manager, make sure the gateway
subdirectories IN, IPARCEL, OUT,
OPARCEL) in MHS are created; these should have been
created by the MHS Directory Manager when you defined the gateway for
PMDF in the earlier step.
Make sure you have a PC running the MHS Connectivity Manager. The Connectivity Manager is the program which will move messages to the PMDF's gateway subdirectories for PMDF to pick up, and it will also move messages into MHS from the gateway subdirectories in which PMDF had deposited messages.
38.8.3 Telling PMDF about MHS
Setting up the MHS channel in PMDF is best performed by running the
PMDF-LAN configuration utilityc and, if necessary, editing
the resulting files to perform any further customizations necessary for
your site. Each such file is described in detail in later sections:
pmdf.cnf, created by the PMDF configuration utility.
lan.rules, created by the PMDF-LAN configuration
utility.
lan.chans, created by the PMDF-LAN configuration
utility.
mhs_local_option, created by the PMDF-LAN
configuration utility.
pc_post.com (OpenVMS) or pc_post (UNIX),
created by the PMDF-LAN configuration utility.
38.8.3.1 Creating or editing lan.chans
The first step in installing a Novell MHS channel is to add the channel
definition to the PMDF configuration file---or as is more commonly
done, add the channel definition to a lan.chans file which
is referenced by (read in to) the PMDF configuration file proper. The
channel definition should appear as
mhs_local master defragment charset8 ibm437 mhs-domain-name
mhs-domain-name should be a valid domain name
that is reserved for use by the Novell MHS channel. One possible choice
is to prepend the official local host name with "mhs.". For
example, in the domain acme.com, a reasonable domain name for the
Novell MHS channel might be mhs.acme.com and the channel entry would
then appear as
mhs_local master defragment charset8 ibm437 mhs.acme.com
The master keyword enables the normal PMDF periodic
delivery jobs to check for the existence of the export file to be
processed. It should be omitted if you chose to use
pc_post.com (OpenVMS) or pc_post (UNIX) or
your own procedure to pick up mail from the PC. See Section 38.2.2 for
more details.
The defragment keyword tells PMDF to reassemble any
fragmented MIME messages before sending them to Novell MHS.
The charset8 ibm437 tells PMDF that Novell MHS is using
the IBM code page 437 character set.
38.8.3.2 Creating or editing lan.rules
Rewrite rules are needed in the PMDF configuration file---or as is more
commonly done, in a file lan.rules which is referenced by
(read in to) the PMDF configuration file proper. Continuing the
mhs.acme.com example, a start at a set of appropriate rules would be:
mhs $U%mhs.acme.com mhs.acme.com $U@mhs.acme.comThe address
user@mhs.acme.com maps to a Novell
MHS subscriber user associated with a specified
default MHS workgroup. The address
user%wg@mhs.acme.com maps to a Novell
MHS subscriber user associated with the
wg workgroup.
Although this addressing format is sufficient to access all available Novell MHS workgroups, it is sometimes useful to associate additional domain names with other Novell MHS workgroups This can be done with rewrite rules of the general form:
wg $U%wg.acme.com wg.acme.com $U%WG@mhs.acme.com$E$F wg.acme.com $U%wg.acme.com@mhs.acme.com$Cmhs_local wg.acme.com $U%WG@mhs.acme.comThese rules associate the domain name
wg.acme.com
with the Novell MHS workgroup WG. Although these
rules may look complex, their actions are reasonably straightforward:
they insure that the Novell MHS name for the workgroup
<(literal>(<)code>WG) is used in the headers of
messages queued to the Novell MHS channel, while the domain name for
the workgroup (wg.acme.com) is used in all other cases. Any number of
similar rule sets can be used to associate additional domain names with
more remote Novell MHS workgroups.
Specification of extended MHS addresses is also possible. Use an address containing an attribute-value pair list (AVPL) of the general form (note the use of the forward slash, /):
/U=user/W=workgroup/T=extension-type/E=extension-value/@mhs-domain-nameThis will map to the MHS address:
user@workgroup {extension-type:extension-value}
There are special quoting rules which must be observed when using AVPL
style addresses. See Section 27.6.2.2 for details on using AVPL style
addresses.
38.8.3.2.1 An example channel configuration
The following is an excerpt from a hypothetical PMDF configuration
which defines an MHS gateway via the include files
lan.rules and lan.chans. The contents of the
lans.rules might appear as:
mhs $U%mhs.acme.com mhs.acme.com $U@mhs.acme.comThe contents of the corresponding
lan.chans file might
then appear as:
mhs_local master defragment charset8 ibm437 mhs.acme.com
In the above example, when a local user addresses a message to xyz@mhs,or xyz@mhs.acme.com, then the rewrite rules convert the address to xyz@mhs.acme.com.
The resultant xyz@mhs.acme.com is a fully qualified address but it doesn't refer to a real machine. It defines a pseudonym used to route messages to a specific channel. This pseudonym must appear in one and only one channel block.
If you have multiple MHS gateways, you might allow users to direct
their messages to specific gateways. For example, you could use two
pseudonyms based on NWENGR and NWSALES. The lan.rules file
included into the main PMDF configuration file, pmdf.cnf
would then appear as follows.
mhs $U%mhs.acme.com mhs.acme.com $U@mhs.acme.com nwengr $U@nwengr.acme.com nwsales $U@nwsales.acme.comThe contents of the corresponding
lan.chans file might
then appear as follows. (Note that additional option files are required
for the added channels.)
mhs_local master defragment charset8 ibm437 mhs.acme.com mhs_gw1 master defragment charset8 ibm437 nwengr.acme.com mhs_gw2 master defragment charset8 ibm437 nwsales.acme.com
When going to a single NetWare host, the MHS gateway channel is normally mhs_local. This channel name may vary. PMDF requires that it begin with mhs_.
38.8.3.3 Novell MHS channel option files
A channel option file must be created to control various
characteristics of the Novell MHS channel. Several mandatory options
must be specified in the option file. These options supply site
specific to PMDF: the NetWare host containing the MHS directory
structure; the MHS directories volume, usually SYS:; and,
the MHS workgroup name. For a small LAN with a single NetWare file
server, the NetWare host and workgroup names are usually the same.
The names of the mandatory options are
38.8.3.4 Location of the option file
Option files are stored in the PMDF table directory and must have names
of the form channelname_option with
channelname being the name of the MHS channel for
which this option file applies. Since the channel name for MHS is
usually mhs_local, the filename is usually
PMDF_TABLE:mhs_local_option. on Open VMS, or
/pmdf/table/mhs_local_option on UNIX.
38.8.3.5 Format of the option file
Novell MHS channel option files have the same format as cc:Mail and the
other PC-LAN channel option files. Refer to Section 38.5.3.5 .
38.8.3.6 Contents of the option file
The available options are:
ACCESS_METHOD (0)
Specifies the access method that PMDF will use to read and write message files. A value of 0, which is the default, selects normal I/O.BINARY_ENCODING (string)
The BINARY_ENCODING option is optional. This option controls the MIME transfer encoding used when binary MHS attachments are converted into MIME bodyparts. Possible values include BASE32, BASE64, COMPRESSED-BASE64, BASE85, BINHEX, BTOA, HEXADECIMAL, PATHWORKS, QUOTED-PRINTABLE, X-UUENCODE, and COMPRESSED-UUENCODE. The MIME standard encoding BASE64 is the default and is appropriate in most cases. When such a message is read from a non-MIME aware user agent such as VMS MAIL, you can extract the MIME bodyparts between the MIME boundary markers to a file and use the PMDF DECODE (OpenVMS) orpmdf decode(UNIX) utility to decode it. From a MIME aware user agent such as PMDF MAIL or Pine, just use the appropriate command to extract a message part and it will be automatically decoded (e.g., PMDF MAIL's EXTRACT/PART command). A different encoding may be appropriate when messages always go to another mail system which does not support MIME or the MIME encodings.MHS_DEFAULT_WORKGROUP (string)
When an address inbound to MHS does not contain an explicit workgroup or host name, PMDF uses this value since SMF requires a Workgroup Name component in each address. See the discussion under Section 38.8.4 . For a site with a single NetWare file server, this will be the host name of that file server. For multi-host workgroups, the value of this option should match the response to the Workgroup name prompt in the Host Setup screen. To review this field, run the MHS Directory Manager, select Manage Directories, and select Set up: This host.MHS_GATEWAY_HOST (string)
This option is used to associate a RFC 822 style pseudodomain name with a MHS style gateway name. MHS users can then send mail to addresses of the formuser@gatewayand it will actually go out the PMDF gateway and be turned into an address of the formuser@pseudodomain.MHS_GATEWAY_TYPE (string)
Required option which specifies the type keyword that PMDF uses in outbound messages. It is required by the MHS Extended Address format. It has no intrinsic meaning. Normally, the value is SMTP or PMDF.
Note:
Novell MHS users address mail to PMDF users with an address of the form:pmdfusername@pmdfworkgroup {pmdftype:user@host}hereuser@hostis any normal PMDF address;pmdfusernameis the value of the MHS_GATEWAY_USERNAME option;pmdfworkgroupis the value of the MHS_GATEWAY_WORKGROUP option; andpmdftypeis the value of the MHS_GATEWAY_TYPE option.
MHS_GATEWAY_USERNAME (string)
Required option which specifies a dummy username that PMDF uses in outbound messages as required by the MHS Extended Address format. It is only used when PMDF must use Extended Addresses. The dummy username has no intrinsic meaning. If PMDF can use Basic Address format, it will and this username isn't used at all in that address. Usually, the value of MHS_GATEWAY_USERNAME is MAILER or PMDF. It may also be a hyphen, -. The hyphen fulfills the requirement for a non-blank word and has the connotation of place-holder.MHS_GATEWAY_WORKGROUP (string)
Required option which specifies the name of the PMDF gateway on the MHS side. The value must match the response to the "Host Name" prompt in the "A Gateway" screen. While logged in as the MHS administrator, run the MHS Directory Manager, select "Manage Directories", select "routes to workgroups, hosts, and gateways", and select "Define A Gateway". Usually, this name will be PMDF. To direct mail to the gateway, the PC user must use the value of this option as the workgroup name component following the user-workgroup delimiter, @, in the message's address.MHS_ID_SUFFIX (string)
Each MHS message is assigned a sixteen character Unique ID (UID) string. When it needs a UID, PMDF generates an eight character value and appends whatever string you supply with this option. The resultant sixteen characters string is used as the UID. Choose an eight character string which is unique throughout your network. The first two characters must be "81" and the remaining six must be in the range 0-9, A-F. The Novell recommended procedure to create a UID is PC specific. It uses two characters of gateway type plus six characters from the NetWare file server's serial number. Since a system running PMDF probably doesn't have a direct connection to NetWare, PMDF can't depend on accessing the file server's serial number.MHS_IN (string)
Novell MHS communicates with each gateway via a gateway-specific directory containing at least four subdirectories. On the NetWare MHS side, theINsubdirectory contains messages to be imported into Novell MHS, theIPARCELsubdirectory contains attachments for messages in theINsubdirectory, theOUTsubdirectory contains messages exported from MHS to be picked up by the gateway, and theOPARCELsubdirectory contains attachments for messages in theOUTsubdirectory. Files must be transferred from the channel's MHS_OUT and MHS_OPARCEL directories to MHS'sINandIPARCELdirectories. Files must also be transferred from MHS'sOUTandOPARCELdirectories to the channel's channel's MHS_IN and MHS_IPARCEL directories. PMDF does not automatically provide this. The installer must set up this copy, or transfer, process. Some utilities are provided to assist with this task. The installer must also ensure that the Novell MHS Connectivity Manager is operating. This option specifies the device and directory path on the system running PMDF where messages which are inbound to PMDF are stored.MHS_IPARCEL (string)
Location of any attachments associated with messages inbound to PMDF. Each attachment file is associated with exactly one header file in the MHS_IN directory. See the description under the MHS_IN option. This option specifies the device and directory path on the system running PMDF where attachment files are stored.MHS_OPARCEL (string)
Location of any attachments associated with messages outbound from PMDF. Each attachment file is associated with exactly one header file in the MHS_OUT directory. See the description under the MHS_IN option. Specifies the device and directory path on the system running PMDF where the attachment files are stored.MHS_OUT (string)
Location of messages outbound from PMDF. Each file contains the header information, including the names of any attachments, and the main body part. See the description under the MHS_IN option. Specifies the device and directory path on the system running PMDF where the messages which are outbound from PMDF are stored.MHS_SLAVE_DELETE (0 or 1)
Specify MHS_SLAVE_DELETE=0 if you are testing and do not want Novell MHS message files to be deleted automatically by MHS_SLAVE. The default is 1. If this is set incorrectly, you will get duplicate messages.REPEAT_COUNT (integer)
SLEEP_TIME (integer)
PMDF's MHS channel shares the files it produces with the Novell MHS Connectivity Manager. Moreover, the actual file server facilities used to provide the necessary file access are quite variable. Some file servers, in an effort to get improved performance, may employ various caching techniques. Use of these techniques may result in transient accessibility problems when the Novell MHS channel attempts to read its message files. The REPEAT_COUNT and SLEEP_TIME options are provided as a means to work around file server specific problems. The REPEAT_COUNT option specifies how many times the channel programs will attempt to open an input file before giving up. REPEAT_COUNT defaults to 2 (two attempts). The SLEEP_TIME option is provided as a means to work around file server specific problems. The SLEEP_TIME option specifies how long in seconds the channel program waits between attempts. SLEEP_TIME defaults to 2 (two seconds between retries).TIMEZONE (string)
For messages coming in from MHS to PMDF, specifies the default time zone to assume for incoming MHS time values that don't have a zone explicitly specified.
38.8.3.7 Example option files
This is an example option file for the mhs_local channel. The file's
name must be mhs_local_option and it must be stored in the
PMDF table directory, i.e., the file must be
PMDF_TABLE:mhs_local_option. (OpenVMS) or
/pmdf/table/mhs_local_option (UNIX). Such a file would be
used when PMDF accesses messages stored on local disks via normal
methods. The messages must be moved by a transfer PC which can access
both the remote PC LAN file server and the PMDF system (via Pathworks
coexistence, FTP PC/TCP InterDrive plus NFS server, etc.).
The following is an example on OpenVMS system.
MHS_GATEWAY_WORKGROUP=PMDF MHS_GATEWAY_USERNAME=MAILER MHS_GATEWAY_TYPE=SMTP MHS_ID_SUFFIX=81BADD28 ! MHS_DEFAULT_WORKGROUP=ACME ! MHS_IN=d1:[pmdf_mhs.in] MHS_IPARCEL=d1:[pmdf_mhs.iparcel] MHS_OUT=d1:[pmdf_mhs.out] MHS_OPARCEL=d1:[pmdf_mhs.oparcel]The following is an example on UNIX.
MHS_GATEWAY_WORKGROUP=PMDF MHS_GATEWAY_USERNAME=MAILER MHS_GATEWAY_TYPE=SMTP MHS_ID_SUFFIX=81BADD28 ! MHS_DEFAULT_WORKGROUP=ACME ! MHS_IN=/dev1/pmdf_mhs/in/ MHS_IPARCEL=/dev1/pmdf_mhs/iparcel/ MHS_OUT=/dev1/pmdf_mhs/out/ MHS_OPARCEL=/dev1/pmdf_mhs/oparcel/
38.8.4 Addressing MHS from PMDF
The general format of an address in for a message destined for an MHS
gateway is
mhs_user%mhs_host@mhs_gwFrom VMS MAIL, use:
IN%"mhs_user%mhs_host@mhs_gw"If
mhs_user is a username on the default MHS
workgroup (see MHS_DEFAULT_WORKGROUP in Section 38.8.3.3 ), then both the
percent sign and mhs_host component may be
omitted giving mhs_user@mhs_gw. If
present, the mhs_host is the name of a NetWare
host or MHS workgroup. In either format, the
mhs_gw portion works with the PMDF rewrite rules
to actually route the message to a particular channel block and to a
specific MHS gateway.
38.8.5 Addressing PMDF from MHS
The generic format for MHS addresses, as defined by SMF, used in a PC
based user agent, and applying to PMDF, is
username@workgroup_name {other_non-SMF_route}
username@workgroup_name forms a MHS
Basic Address. Each part must be eight characters or less and use only
the letters A--Z, a--z, the digits 0--9, and the symbols -, $, and #.
This form may be used to send mail to a remote address, such as a VMS
MAIL user (assuming their username is eight characters or less). Since
percent signs are not allowed, there is no standard way of specifying a
host name on the PMDF side of the gateway, so it will be delivered to
username on the PMDF system.
If the user agent on the PC allows a percent sign in
The braces, and text contained within, are optional. If present, they
signify an MHS Extended Address. The extended address form must be used
when Note:
The
An address list is two or more addresses separated by commas. The list
may contain either Basic Addresses, Extended Addresses, or a mixture of
both.
It is not possible to predict these formats; refer to the documentation
for your particular MHS user agent for additional information.
The following sections describe the mappings used by the MHS channel.
Examples of these mappings are also provided in the sample file
Note that such a mapping is purely for setting up the correspondence
between the names of MHS character sets and the names
of MIME character sets; it does not change the actual underlying
character set. To convert from one character set to another, use a
CHARSET-CONVERSION mapping as described in Section 6.1 .
Note that such a mapping is purely for setting up the correspondence
between the names of MHS character sets and the names
of MIME character sets; it does not change the actual underlying
character set. To convert from one character set to another, use a
CHARSET-CONVERSION mapping as described in Section 6.1 .
If you chose to run the mhs_local channel interactively, all progress
reports and error messages will be displayed on your terminal.
If you chose to run the mhs_local channel as a batch job or under the
auspices of the Job Controller, all progress reports and error messages
will be written to a log file; the log file will be called
Additional debugging output can be enabled by putting the
username, you can use
final_user%final_host@workgroup_name, where final_user is the username and
final_host is the host name of the destination
system. A severe constraint, however, is that the total length of
final_user%final_host must be eight
characters or less.
username exceeds the MHS eight character
limit or when the user is not located on that system running the PMDF
gateway software.
username component is the
actual username of the recipient. If the Extended format is being used
(i.e., braces present), then the
username part is superfluous. It must be present
to meet MHS addressing rules but PMDF will ignore it.
other_non-SMF_route part consists of a
gateway_type keyword, a colon, and the address of
the message's final destination user and host. The format for PMDF
transmittal, including the enclosing braces, is
{ type : final_user @ final_host_spec }
The type placeholder represents the
gateway_type keyword (see MHS_GATEWAY_TYPE in
Section 38.8.3.3 ). It is required by the Novell SMF specification. To be
compliant, PMDF always includes the type keyword and colons on messages
destined for MHS. However, PMDF treats the type keyword and colon as
optional on inbound messages.
38.8.5.1 Address transformations in MHS user agents
User agent clients of Novell MHS often present addresses in alternative
forms rather than using the native address format defined in the SMF
specification. For example, an RFC 822 address
user@host might map to the MHS address:
mailer@pmdf {SMTP:user@host}
However, old versions of Da Vinci e-mail would transform this address
to:
PMDF"SMTP:user@host":MAILER
38.8.6 Content type and character set mappings
The SMF used by Novell MHS defines a set of content types and
encodings. These correspond to the MIME notion of content subtypes and
character sets. The MHS channel must map Novell MHS content types and
encodings to their MIME equivalents and back again. Selection of an
appropriate MIME transfer encoding is also necessary for each content
type. This is implemented using a set of mapping tables in the mapping
file.
mhs_mappings.sample included in table directory of the
PMDF distribution, i.e.,
PMDF_TABLE:mhs_mappings.sample on OpenVMS or
/pmdf/table/mhs_mappings.sample on UNIX.
38.8.6.1 MIME-CONTENT-TYPES-TO-MHS mapping
The MIME-CONTENT-TYPES-TO-MHS mapping table maps MIME content type and
subtype information into Novell MHS content type codes. A minimal
MIME-CONTENT-TYPES-TO-MHS mapping would be:
MIME-CONTENT-TYPES-TO-MHS
TEXT/PLAIN TEXT
APPLICATION/DCA-RFT RFT-DCA
APPLICATION/DEC-DX DEC-DX
APPLICATION/MSWORD MS-WORD
APPLICATION/OCTET-STREAM BINARY
APPLICATION/POSTSCRIPT POSTSCRIPT
APPLICATION/VMS-RMS BINARY
APPLICATION/WITA WANG-WITA
APPLICATION/WORDPERFECT5.1 WORDPERFECT
38.8.6.2 MHS-TO-MIME-CONTENT-TYPES mapping
The MHS-TO-MIME-CONTENT-TYPES mapping table maps MHS content type codes
into MIME content type and subtype information. A minimal
MHS-TO-MIME-CONTENT-TYPES mapping would be:
MHS-TO-MIME-CONTENT-TYPES
TEXT TEXT/PLAIN
BINARY APPLICATION/OCTET-STREAM
DEC-DX APPLICATION/DEC-DX
MS-WORD APPLICATION/MSWORD
POSTSCRIPT APPLICATION/POSTSCRIPT
RFT-DCA APPLICATION/DCA-RFT
WANG-WITA APPLICATION/WITA
WORDPERFECT APPLICATION/WORDPERFECT5.1
38.8.6.3 MHS-TO-MIME-ENCODINGS mapping
The MHS-TO-MIME-ENCODINGS mapping table maps Novell MHS content type
codes to an appropriate MIME transfer encoding. The left hand side of
the mapping should be a Novell MHS content type code and the result
should be a MIME transfer encoding identifier (7BIT, 8BIT, BASE64,
QUOTED-PRINTABLE, etc.) A minimal MHS-TO-MIME-ENCODINGS
mapping would be:
MHS-TO-MIME-ENCODINGS
TEXT NONE
BINARY BASE64
DCA-RFT BASE64
DEC-DX BASE64
MS-WORD BASE64
POSTSCRIPT QUOTED-PRINTABLE
WANG-WITA BASE64
WORDPERFECT BASE64
38.8.6.4 MIME-TO-MHS-CHARSETS mapping
The MIME-TO-MHS-CHARSETS mapping table maps MIME charset parameter
information into Novell MHS encoding codes. A minimal
MIME-TO-MHS-CHARSETS mapping would be:
MIME-TO-MHS-CHARSETS
US-ASCII ISO-646
ISO-8859-1 ISO-8859
T.61 CCITT-T.61(US)
ISO-IR-142 ISO-6937
IBM437 IBM-437
IBM850 IBM-850
IBM860 IBM-860
IBM863 IBM-863
IBM865 IBM-865
MACINTOSH MAC
38.8.6.5 MHS-TO-MIME-CHARSETS mapping
The MHS-TO-MIME-CHARSETS mapping table maps MHS encoding codes into
MIME charset parameter values. A minimal MHS-TO-MIME-CHARSETS mapping
would be:
MHS-TO-MIME-CHARSETS
ISO-646 US-ASCII
CCITT-T.51(US) US-ASCII
CCITT-T.61(US) T61
ISO-6937 ISO-IR-142
IBM-437 IBM437
IBM-850 IBM850
IBM-860 IBM860
IBM-863 IBM863
IBM-865 IBM865
MAC MACINTOSH
38.8.7 Cookbook of test procedures
The following procedures assume that the option ACCESS_METHOD=0 has
been selected. PMDF will read and write messages from and to local
files. The actual message transfer will be handled by a transfer PC.
38.8.7.1 Recipe for MHS message inbound to PMDF
To test the gateway inbound to PMDF:
sample.mhs located, on OpenVMS,
in PMDF_ROOT:[other.dos] or, on UNIX, in
/pmdf/other/dos. Edit the sample message file as follows:
final_to_user with the
actual username of a real user (who is willing to receive mail as part
of this test).
final_cc_user with the
actual username of a real user.
final_host with the actual
host name on which the above usernames are located. This system must be
known to PMDF and be reachable.
MHS_user with the actual
username of a NetWare MHS user. This allows you to use your user
agent's reply command to create a message outbound from PMDF to MHS.
MHS_workgroup with the
actual name. In a multihost workgroup, this is the workgroup name. In a
single host workgroup, this is the host name.
@PMDF_COM:master
mhs_local or the UNIX command pmdf run mhs_local ,
or
pmdf submit mhs_local.
PMDF_LOG:mhs_local_master.log on OpenVMS, or
/pmdf/log/mhs_local_master.log on UNIX.
master_debug channel keyword on the mhs_local channel; see
Section 2.3.4.85 . With the master_debug keyword on the
channel, you should see progress reports (either at your terminal, or
in the log file); if such progress reports do not seem to be being
generated, verify that the keyword master appears on the
mhs_local channel definition line in the PMDF configuration file. For
more details, see the discussion of channel table keywords in
Section 2.3.4.7 .
38.8.7.2 Recipe for MHS to PMDF transfer process
To test the PMDF gateway and the MHS to PMDF transfer process:
$Txxxxxx.
The xxxxxx is usually a 6 digit number but it can
be anything as long as it is unique. The file must not have an
extension.
PMDF_TABLE:mhs_local_option. (OpenVMS) or
/pmdf/table/mhs_local_option (UNIX).
38.8.7.3 Recipe for PMDF messages outbound to MHS
To test the PMDF gateway outbound to MHS:
mhs_user%mhs_workgroup@mhs ;
(from VMS MAIL, send using the To: address
IN%"mhs_user%mhs_workgroup@mhs")
. Replace mhs_user with the NetWare username of a
real user at your site (preferably someone who has agreed to help you
test the gateway). Replace mhs_workgroup with the
target NetWare host's MHS workgroup name.
38.8.7.4 Recipe for PMDF to MHS transfer process
To test the PMDF gateway and the PMDF to MHS transfer process:
Note
b This assumes you are using
PMDF as the value of the option MHS_GATEWAY_WORKGROUP,
i.e., the Workgroup assigned to PMDF within MHS.c See the appropriate edition of the
PMDF Installation Guide for a description and example of the use of the PMDF-LAN
configuration utility.
d This option file is
PMDF_TABLE:mhs_local_option. (OpenVMS), or
/pmdf/table/mhs_local_option (UNIX).
Previous
| Next
| Contents