PMDF System Manager's Guide
PMDF-REF-6.0

38.7 Microsoft Mail channels

Microsoft Mail channels are used to convert messages between the RFC 822 and MIME message formats used by PMDF and the formats used by Microsoft Mail. Versions 3.0 to 3.2 of Microsoft Mail are presently supported. The Microsoft Mail channel programs combined with the special DOS utility programs SMTPGET and SMTPPUT and the Microsoft Mail SMTP Access component produce an effective gateway between PMDF and Microsoft Mail.

The Microsoft Mail channels attempt to convert as much of MIME as possible to compatible Microsoft Mail message formats. However, limitations in Microsoft Mail make a complete conversion impossible, so in some cases the conversion will be limited in scope. In particular, Microsoft Mail is incapable of handling nested multipart and message structures, so any sense of nested structure is lost in the conversion process.

38.7.1 How to prepare your Microsoft Mail Post Office

38.7.1.1 Required Microsoft products

If you have a Microsoft Mail Windows for Workgroups post office (WGPO), first you have to upgrade it to a full function post office by purchasing and installing the Microsoft product "Postoffice Upgrade for Microsoft Windows for Workgroups" on the WGPO.

Microsoft Mail Gateway Access for SMTP (or the "SMTP Access component") is required for each Microsoft Mail post office which uses SMTP; (PMDF's Microsoft Mail channel looks to Microsoft Mail users like Microsoft's own SMTP gateway). This piece of software currently has Microsoft part number 068-099-127. One copy of the SMTP Access component comes with the full Microsoft Mail SMTP Gateway product.

If you are replacing Microsoft's own SMTP Gateway with PMDF's Microsoft Mail channel, then you already have the SMTP Access component on the PC. All post offices which currently have access to SMTP also already have the SMTP Access component installed, so no new installation or preparation is neccessary.

38.7.1.2 Setting up the Microsoft Mail post office for SMTP

Copy the following gateway files (<code>INSTALL.EXE, <code>SMTPGET.EXE, <code>SMTPPUT.EXE) from PMDF_ROOT:[other.dos.msmail] (OpenVMS) or /pmdf/other/dos/msmail (UNIX) to the disk where the PC can see them. These files may also be copied directly off of the PMDF distribution CD-ROM, which is readable from DOS, Windows, or OS/2, as well as OpenVMS or UNIX, from the [other.dos.msmail] (OpenVMS), /other/dos/msmail (UNIX), or \other\dos\msmail (DOS, Windows, or OS/2) subdirectory. While you are at it, also copy the utility program delay.exe found in PMDF_ROOT:[other.dos] (OpenVMS) or /pmdf/other/dos (UNIX) or off the PMDF distribution CD-ROM in [other.dos] (OpenVMS), /other/dos (UNIX), or \other\dos (DOS, Windows, or OS/2), to the same disk on the PC. See Section 38.10 for information on the use of the DELAY program.
Make sure you have a full function post office. Install the "Postoffice Upgrade for Microsoft Windows for Workgroups" on the WGPO if necessary.
If you are adding SMTP access for the first time, then create an SMTP gateway in your post office with the INSTALL program which comes with PMDF (and which you copied to your PC during step 1 earlier). The format of this command is discussed in Section 38.7.7.2 .
Install the Microsoft Mail SMTP Access Component on the post office and provide the path of the post office when prompted. This should be the only input you have to provide to it during its installation.
Verify that you can access SMTP addresses from Microsoft Mail by going to the screen where you can add an address to your personal addressbook. If you see SMTP in the list of "create what kind of entry", then you are all set.
Install the Microsoft Mail SMTP Access Component on the downstream post office. Repeat the last two steps for all downstream post offices.

38.7.2 Telling PMDF about Microsoft Mail
Setting up the Microsoft Mail channel in PMDF is best performed by running the PMDF-LAN configuration utility⁸ and editting the resulting files, if necessary, 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.
- ff_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.7.2.1 Creating or editing lan.chans
  The first step in installing a Microsoft Mail channel in PMDF is to add a channel definition to the PMDF configuration file---or as is more commonly done, add the channel definition to a file lan.chans which is referenced by (read in to) the PMDF configuration file proper. The channel definition should appear as
```
ff_local master defragment charset8 ibm437 
ff-domain-name
```
  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 MS Mail.
  The charset8 keyword controls the character set label that gets applied to text attachments containing eight bit characters. ibm437 is a standard eight bit PC character set used by many Microsoft Mail configurations; ibm850 is another commonly encountered PC character set.
  ff-domain-name should be a valid domain name that is reserved for use by the Microsoft Mail channel. One possible choice is to prepend the official local host name with "msmail.". For example, in the domain acme.com, a reasonable domain name for the Microsoft Mail channel might be msmail.acme.com and the channel entry would then appear as
```
ff_local master defragment charset8 ibm437 
msmail.acme.com 
```
  38.7.2.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 msmail.acme.com example, a start at a set of appropriate rules would be:
```
msmail              $U%msmail.acme.com 
msmail.acme.com     $U@msmail.acme.com 
```
  The address user@msmail.acme.com maps to a Microsoft Mail subscriber user associated with a specified default Microsoft Mail domain and post office. The address net/po/user@msmail.acme.com (note the use of the forward slash character, /) maps to a Microsoft Mail subscriber user associated with the po post office on the net network. Both the network and post office may be omitted; if they are omitted default values will be applied as specified by the FF_DEFAULT_NETWORK and FF_DEFAULT_POSTOFFICE channel options as described in Section 38.7.2.6 .
  
  38.7.2.2.1 An example channel configuration
  The following is an excerpt from a hypothetical PMDF configuration which defines a Microsoft Mail channel via the include files lan.rules and lan.chans. The contents of lans.rules might appear as:
```
msmail                 $U%msmail.acme.com 
msmail.acme.com        $U@msmail.acme.com 
```
  The contents of the corresponding lan.chans file might then appear as:
```
ff_local master defragment charset8 ibm437 
msmail.acme.com 
```
  In the above example, when a local user addresses a message to xyz@msmail, or xyz@msmail.acme.com, the rewrite rules convert the address to xyz@msmail.acme.com.
  The resultant xyz@msmail.acme.com uses a fully qualified domain name 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, namely the one after the ff_local line.
  If you have multiple Microsoft Mail servers, you might allow users to direct their messages to specific gateways on different servers. For example, you could use two pseudonyms based on MSENGR and MSSALES. The configuration will then contain the following rewrite rules and channels. Note that additional option files are required for the added channels. In such a case, the lan.rules file might appear as:
```
msmail                 $U%msmail.acme.com 
msmail.acme.com        $U@msmail.acme.com 
msengr                 $U%msengr.acme.com 
msengr.acme.com        $U@msengr.acme.com 
mssales                $U%mssales.acme.com 
mssales.acme.com       $U@mssales.acme.com 
```
  and the corresponding lan.chans file would then be:
```
ff_local master defragment charset8 ibm437 
msmail.acme.com 
 
ff_gw1 master defragment charset8 ibm437 
msengr.acme.com 
 
ff_gw2 master defragment charset8 ibm437 
mssales.acme.com 
```
  The Microsoft Mail gateway channel is normally named ff_local when connecting to just one Microsoft Mail post office. This is not an absolute rule --- PMDF's only real requirement is that the channel name begin with ff_.
  
  38.7.2.2.2 Another example channel configuration
  
  Note:
  The use of include files lan.rules and lan.chans is not mandatory; you can equivalently put the contents of lan.rules and lan.chans directly into pmdf.cnf where the inclusion lines were used in the automatically generated pmdf.cnf file. The following example does not use the include files.
  
  When you are connecting PMDF to multiple Microsoft Mail post offices via the same channel, you can still assign a domain name to each post office, e.g.
```
! pmdf.cnf - Configuration file for node ACME 
! 
PO1.msmail                 NETWORK/PO1/$U@msmail.acme.com 
PO1.msmail.acme.com        NETWORK/PO1/$U@msmail.acme.com 
PO2.msmail                 NETWORK/PO2/$U@msmail.acme.com 
PO2.msmail.acme.com        NETWORK/PO2/$U@msmail.acme.com 
msmail.acme.com            $U@msmail.acme.com 
[ ... additional rewrite rules ... ]
 
[ ... channel definitions ... ]
 
[ blank line ]
ff_local master defragment charset8 ibm437 
msmail.acme.com 
```
  In the above example, when a local user addresses a message to xyz@PO1.msmail, or xyz@PO1.msmail.acme.com, it will be rewritten to NETWORK/PO1/xyz@msmail.acme.com, which corresponds to your post office PO1 in the network called NETWORK.
  When mail comes from the Microsoft Mail users, the from address is in the format NETWORK/PO1/username@msmail.acme.com; you can use the REVERSE mapping in the PMDF mapping file to rewrite these addresses back to the PO1.msmail.acme.com format as follows:
```
REVERSE 
 
   NETWORK/PO1/*@msmail.acme.com  $Y$0@PO1.msmail.acme.com 
 
```
  Please refer to Chapter 5 for more information on the mapping file. In addition pay attention to the setting of the option called USE_REVERSE_DATABASE in Chapter 7 .
  
  38.7.2.3 Microsoft Mail channel option files
  A channel option file must be created to control various characteristics of a Microsoft Mail channel. Several mandatory options must be specified in the option file, so the options file cannot be omitted entirely. In general, options supply site specific information to PMDF: the names of the import and export files used to communicate with the SMTPGET and SMTPPUT utilities, and the default Microsoft Mail network and post office names to use when none are specified in an address.
  The names of the mandatory options are:
  - FF_OUTPUT_FILE_NAME,
  - FF_INPUT_FILE_NAME,
  - FF_DEFAULT_NETWORK, and
  - FF_DEFAULT_POSTOFFICE.
  Their significance and usage are described in Section 38.7.2.6 . Before setting up the PMDF configuration files, you must know the correct values to specify for these mandatory options. Contact whoever does Microsoft Mail administration tasks at your local site. Impress upon them that if they unilaterally change their Microsoft Mail configuration it may break the mail gateway. Ask them to notify you before making changes so that you can keep the PMDF configuration synchronized with Microsoft Mail.
  
  38.7.2.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 Microsoft Mail channel to which this option file applies; as the Microsoft Mail channel is usually named ff_local, then the corresponding option file is usually PMDF_TABLE:ff_local_option. on OpenVMS, or /pmdf/table/ff_local_option on UNIX.
  
  38.7.2.5 Format of the option file
  Microsoft Mail channel option files have the same format as cc:Mail channel option files. Refer to Section 38.5.3.5 .
  
  38.7.2.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 Microsoft Mail 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) or pmdf 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. The FF-TO-MIME-ENCODINGS mapping, if supplied and matched, will override the BINARY_ENCODING option's value. See Section 38.7.5.3 for additional information on this mapping.
  CHECK_LINE_LENGTH (0, 1, 2, or 3)
  The MS Mail import utility, SMTPPUT, is not always successful at performing line wrapping on text lines longer than 78 characters. The default for this opton is 1, instructing PMDF to turn message text with long lines into text attachments (which are always safe). Setting this option to 0 causes PMDF to pass message text with long lines unchanged to MS Mail; this option is not recommended as it may lead to MS Mail truncating lines, performing problematic line wrapping, or other problems. Setting this option to 2 causes PMDF to perform forcibly wrap long lines. Setting this option to 3 causes PMDF to truncate long lines.
  DELETE_HEADERS (0, 1, 2 or 3)
  Message headers are normally deleted once they have been successfully converted from RFC 822 headers into corresponding Microsoft Mail headers or vice versa. The headers that remain after all such conversions have been done can be saved using the SAVE_HEADERS option described below. However, under some circumstances it is useful to skip the deletion step, preserving all header information. The DELETE_HEADERS option provides such a facility. Its normal default value is 3, which means that headers are deleted once converted. Bit 0 controls the deletion of headers converted from RFC 822 to Microsoft Mail, and Bit 1 controls the deletion of headers converted from Microsoft Mail to RFC822. So a value of 0 specifies that all headers should be saved, a value of 1 specifies that headers converted from RFC 822 to Microsoft Mail should be deleted, but all headers coming from Microsoft Mail should be saved, and a value of 2 specifies that headers converted from Microsoft Mail to RFC 822 should be deleted, but all RFC 822 headers should be saved going to Microsoft Mail.
  FF_DEFAULT_NETWORK (string)
  Required option which specifies a default network name to use when the network name is omitted from an address. This is usually the name of the Microsoft Mail network to which PMDF connects. PMDF inserts this value and the FF_DEFAUT_POSTOFFICE value into the address when an address inbound to Microsoft Mail does not contain an explicit network or post office name.
  FF_DEFAULT_POSTOFFICE (string)
  Required option which specifies a default post office name to use when the post office name is omitted from an address. This is usually the name of the Microsoft Mail post office to which PMDF connects.
  FF_GATEWAY_STRTYPE (string)
  This option specifies the string address prefix used to identify PMDF addresses. This almost always should be "SMTP", which is the default if this option is not specified.
  FF_GATEWAY_INTTYPE (integer)
  This option specifies the integer address prefix used to identify PMDF addresses. This almost always should be "20", which is the default if this option is not specified.
  FF_INPUT_FILE_NAME (string)
  Required option which specifies the name of the inbound message file to be read by the Microsoft Mail slave channel program. This is a binary file produced by running the SMTPGET utility which exports messages destined for PMDF. This file will be read by PMDF and the messages it contains will be delivered by PMDF. Errors are handled by writing error messages out as mail; these message will then pass through the Microsoft Mail master channel program and back into Microsoft Mail. Since this is a binary file, it must be copied in binary mode without corruption. This option specifies the complete filename on the system running PMDF, including device and directory.⁹
  FF_INPUT_FILE_PATTERN (string)
  When SEPARATE_FILES has bit 0 set, i.e., is set to an odd value, then the FF_INPUT_FILE_PATTERN option is used in place of the usual FF_INPUT_FILE_NAME option. FF_INPUT_FILE_PATTERN specifies a pattern for the files for the MS Mail channel to read coming from MS Mail, when SEPARATE_FILES has bit 0 set.
  FF_OUTPUT_FILE_NAME (string)
  Required option which specifies the name of the outbound message file that is created or appended to by the Microsoft Mail master channel program. This binary file is in a format that is suitable for use by the SMTPPUT utility. This file must be transferred to the Microsoft Mail system in binary mode where appropriate and the SMTPPUT utility must be run to import the messages it contains into Microsoft Mail. This option specifies the complete filename on the system running PMDF, including device and directory.⁸
  FF_MASTER_DELETE (0 or 1)
  Specify FF_MASTER_DELETE=0 if you are testing and do not want PMDF messages to be deleted from the PMDF channel queue by Microsoft Mail master channel program. The default is 1. Microsoft Mail users will receive an endless stream of duplicate messages if this option is set incorrectly.
  FF_SLAVE_DELETE (0 or 1)
  Specify FF_SLAVE_DELETE=0 if you are testing and do not want Microsoft Mail message files to be deleted automatically by the Microsoft Mail channel program. The default is 1. PMDF users will get an endless stream of duplicate messages if this option is set incorrectly.
  REPEAT_COUNT (integer)
  
  SLEEP_TIME (integer)
  PMDF's Microsoft Mail channel shares the files it produces with the SMTPGET and SMTPPUT utilities. 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 Microsoft Mail 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).
  SAVE_HEADERS (0, 1, 2 or 3)
  The SAVE_HEADERS option controls the disposition of message headers that cannot be converted into Microsoft Mail information. The default value is 0, which causes all such headers to be discarded. A value of 1 causes such headers to be turned into a text part which is the main body of the message. A value of 2 causes such headers to be turned into a text attachment, placed last so that Microsoft Mail shows it as the first attachment, unless there is no other part to the message, in which case this text attachment is the main body of the message. A value of 3 causes such headers to be turned into a text attachment, placed first so that Microsoft Mail shows it as the last attachment.
  SEPARATE_COUNT (integer)
  SEPARATE_COUNT specifies the maximum number of messages that PMDF should write to a file going to MS Mail, when SEPARATE_FILES has bit 1 set. The default is to impose no limit---essentially, keep on writing messages to the one file as long as the channel runs.
  SEPARATE_FILES (integer)
  SEPARATE_FILES takes a bit-encoded integer value. Bit 0 (counting starting from 0) controls whether or not the MS Mail channel should read separate files coming from MS Mail. Bit 1 controls whether or not the MS Mail channel should write separate files for messages going to MS Mail. The default value is 0. When SEPARATE_FILES has bit 0 set, i.e., is set to an odd value, then FF_INPUT_FILE_NAME should be set to a directory specification, rather than a full file name, and FF_INPUT_FILE_PATTERN should be set specifying a pattern for the names of the files which the MS Mail channel is to read coming from MS Mail. For instance, to read in all files with names of the form ms*.msg from the directory D2:[pmdfms] one might set:
```
SEPARATE_FILES=1 
FF_INPUT_FILE_NAME=D2:[pmdfms] 
FF_INPUT_FILE_PATTERN=D2:[pmdfms]ms*.msg 
```
  Or if you want to write a separate file for each message going to MS Mail (but messages coming from MS Mail will still appear in just one file), set SEPARATE_FILES=2 and SEPARATE_COUNT=1. You should then also set FF_OUTPUT_FILE_NAME to a directory specification, rather than a full file name; for instance, if you previously had the FF_OUTPUT_FILE_NAME option set to D2:[pmdfms]pmdf2ms.msg, instead set it to D2:[pmdfms] The files PMDF writes will have names such as 00000001.out, etc. A PMDF user account is required in order to write separate files going to MS Mail. On OpenVMS, if you want to use this functionality, but you didn't say yes to create such an account when you installed PMDF, then you should create one now by using the PMDF_COM:create_pmdf_user_account.com procedure.
  SEPARATE_SIZE (integer)
  SEPARATE_SIZE specifies a number of bytes beyond which to force a new file for messages going to MS Mail, when SEPARATE_FILES has bit 1 set. (Note that while this imposes an upper limit on the size of files of messages going to MS Mail, it is not itself exactly the limit---after PMDF outputs a message, if the cumulative size is then bigger than this option value, then the next message goes into a new file.) The default to impose no size limit.
  TIMEZONE (string)
  Specifies the Microsoft Mail time zone.
  38.7.2.7 Example option files
  This is an example option file for the ff_local channel. The file's name must be ff_local_option and it must be stored in the PMDF table directory, i.e., it must be PMDF_TABLE:ff_local_option. on OpenVMS or /pmdf/table/ff_local_option on 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 a OpenVMS system.
```
FF_DEFAULT_NETWORK=ACME 
FF_DEFAULT_POSTOFFICE=HQ 
! 
FF_OUTPUT_FILE_NAME=d1:[msmail.pmdf]pmdf2ms.msg 
FF_INPUT_FILE_NAME=d1:[msmail.pmdf]ms2pmdf.msg 
```
  The following is an example on a UNIX system.
```
FF_DEFAULT_NETWORK=ACME 
FF_DEFAULT_POSTOFFICE=HQ 
! 
FF_OUTPUT_FILE_NAME=/dev1/msmail/pmdf/pmdf2ms.msg 
FF_INPUT_FILE_NAME=/dev1/msmail/pmdf/ms2pmdf.msg 
```
  38.7.3 Addressing Microsoft Mail from PMDF
  The general format of To: address in a message destined for Microsoft Mail is (note the use of the forward slash character, /)
```
net/po/user@msgw
```
  From VMS MAIL, use:
```
IN%"net/po/user@msgw" 
```
  user is the name of a Microsoft Mail user, net is the name of the Microsoft Mail network the user's post office is in, po is the name of the user's Microsoft Mail post office, and msgw is the pseudo domain name associated in with the gateway into Microsoft Mail, i.e., the name associated in the PMDF configuration file with the Microsoft Mail channel. The net, po, and associated punctuation may be omitted, leaving user@msgw if they are the same as the FF_DEFAULT_NETWORK and FF_DEFAULT_POSTOFFICE options in the channel options file. In either format, the msgw portion works with the PMDF rewrite rules to actually route the message to a particular channel and to a specific Microsoft Mail gateway.
  
  38.7.4 Addressing PMDF from Microsoft Mail
  PMDF addresses are entered into Microsoft Mail simply as SMTP addresses, e.g., user@innosoft.com
  
  38.7.5 Content type and encoding mappings
  Microsoft Mail uses file names to indicate what sort of data is present in an attachment. Although file names do not provide an exact typing scheme, nevertheless they can be mapped to and from MIME content types and subtypes. For this reason, PMDF's Microsoft Mail channel maps Microsoft Mail attachment file names to MIME content types and subtypes and back again. Selection of an appropriate MIME transfer encoding is also necessary for each sort of file. All this is implemented using a set of mapping tables in the mapping file. The PMDF mapping file is described in detail in Chapter 5 .
  The following sections describe the mappings used by the Microsoft Mail channel. Examples of these mappings are also provided in a sample file included in the table directory of the PMDF distribution, PMDF_TABLE:ff_mappings.sample on OpenVMS or /pmdf/table/ff_mappings.sample on UNIX. If you do not have a PMDF mapping file in your PMDF table directory, you can just copy ff_mappings.sample to mappings and edit it to suit your site.
  
  38.7.5.1 MIME-CONTENT-TYPES-TO-FF mapping
  The MIME-CONTENT-TYPES-TO-FF mapping table maps MIME content type and subtype information into Microsoft Mail attachment file names. A minimal MIME-CONTENT-TYPES-TO-FF mapping would be:
```
MIME-CONTENT-TYPES-TO-FF 
 
  APPLICATION/MSWORD        DOC.DOC 
  APPLICATION/POSTSCRIPT    PS.PS 
  IMAGE/TIFF                TIFF.TIF 
  IMAGE/GIF                 GIF.GIF 
  TEXT/PLAIN                TEXT.TXT 
```
  38.7.5.2 FF-TO-MIME-CONTENT-TYPES mapping
  The FF-TO-MIME-CONTENT-TYPES mapping table maps Microsoft Mail attachment file names into MIME content type and subtype information. A minimal FF-TO-MIME-CONTENT-TYPES mapping would be:
```
FF-TO-MIME-CONTENT-TYPES 
 
  *.PS                      APPLICATION/POSTSCRIPT 
  *.GIF                     IMAGE/GIF 
  *.TIF                     IMAGE/TIFF 
  *.TXT                     TEXT/PLAIN 
  *.BAT                     TEXT/PLAIN 
```
  38.7.5.3 FF-TO-MIME-ENCODINGS mapping
  The FF-TO-MIME-ENCODINGS mapping table maps Microsoft Mail attachment file names to an appropriate MIME transfer encoding. The left hand side of the mapping should be a pattern intended to match a file name and the result should be a MIME transfer encoding identifier (7BIT, 8BIT, BASE64, QUOTED-PRINTABLE, etc.) A minimal FF-TO-MIME-ENCODINGS mapping would be:
```
FF-TO-MIME-ENCODINGS 
 
  *.TXT                     NONE 
  *.PS                      BASE64 
  *.DOC                     BASE64 
  *.GIF                     BASE64 
  *.TIF                     BASE64 
```
  38.7.6 A sample configuration
  In this section, a cook book approach is used to demonstrate how to set up a Microsoft Mail configuration.
  - Create the SMTP gateway with the INSTALL program which comes with PMDF. If your MS Mail postoffice files are in C:\MAILDATA, then an example command would be INSTALL -C -G -SSMTP -DC:\MAILDATA -V (see Section 38.7.7.2 for command format description).
  - Install the Microsoft Mail SMTP Gateway Access component. Each post office which requires access to SMTP must have the SMTP Access component installed to enable its SMTP addressing template in the Microsoft Mail user agent. A separate copy of the Gateway Access Component needs to be purchased and installed for each post office requiring SMTP access.
  - Set up a directory for storing the files. In this example, the diska:[msmail.pmdf] directory is where PMDF will expect to read and write the files used for communicating with Microsoft Mail. On the PC running Microsoft Mail, there are the two Microsoft Mail directories C:\MAILDATA (where your Microsoft Mail post office is), and C:\MAILEXE. You have put SMTPPUT.EXE and SMTPGET.EXE in the C:\PMDF directory.
  - Add rewrite rules to your PMDF configuration. The following three steps can be done automatically by the use of the PMDF-LAN configuration utility.^a Now, suppose that the local Microsoft Mail post office is named SALES on the network HQ, and the official local host name for the OpenVMS system running PMDF is ACME.COM. Then, a suitable domain name to associate with the SALES post office might be msmail.acme.com. Edit the PMDF configuration file, i.e., the file PMDF_TABLE:pmdf.cnf (OpenVMS) or the file /pmdf/table/pmdf.cnf (UNIX) to uncomment the references to lan.rules and lan.chans, and create a file lan.rules in the PMDF table directory (this file would be created for you if you run the PMDF-LAN configuration utility) containing the rewrite rules:
```
msmail                      $u%msmail.acme.com 
msmail.acme.com             $u@msmail.acme.com 
```
  - Define the ff_local channel. Next, create a file lan.chans in the PMDF table directory which defines the ff_local channel via the entry:
```
ff_local master defragment charset8 ibm437 
msmail.acme.com 
```
  - If you are using a compiled configuration, then be sure to recompile and reinstall your configuration after adding the above channel and rewrite rules to your PMDF configuration.
  - Create the option file. Create the world readable file PMDF_TABLE:ff_local_option (OpenVMS) containing the lines:
```
FF_DEFAULT_NETWORK=HQ 
FF_DEFAULT_POSTOFFICE=SALES 
FF_OUTPUT_FILE_NAME=diska:[msmail.pmdf]pmdf2ms.msg 
FF_INPUT_FILE_NAME=diska:[msmail.pmdf]ms2pmdf.msg 
```
    or the world readable file /pmdf/table/ff_local_option (UNIX) containing the lines:
```
FF_DEFAULT_NETWORK=HQ 
FF_DEFAULT_POSTOFFICE=SALES 
FF_OUTPUT_FILE_NAME=/diska/msmail/pmdf/pmdf2ms.msg 
FF_INPUT_FILE_NAME=/diska/msmail/pmdf/ms2pmdf.msg 
```
  - Send a test message. At this point you should be able to send mail back and forth, with some manual movement of the message files. If the PMDF system is an OpenVMS system, you can send mail from PMDF MAIL or PMDF Pine to the Microsoft Mail user JSmith using the address
```
JSmith@msmail.ACME.COM 
```
    or from VMS MAIL using the address:
```
IN%"JSmith@msmail.ACME.COM" 
```
    If the PMDF system is a UNIX system, you can send mail from UNIX mail clients such as mail or Pine using the address
```
JSmith@msmail.acme.com 
```
  - Transfer the message file to the Microsoft Mail server. Next transfer the file diska:[msmail.pmdf]pmdf2ms.msg to the Microsoft Mail server, being careful to move it as a binary file.
  - Process the Microsoft Mail import file. The step prior to the previous step will result in PMDF producing a Microsoft Mail import file. This file will be that specified with the FF_OUTPUT_FILE_NAME option in the ff_local_option file of Step 5. Import this file into Microsoft Mail on the PC as shown below; note that you should substitute your Administrator name and password where admin:passord is shown.
```
F: 
CD \PMDF 
C:\PMDF\SMTPPUT -dc:\maildata\ -f2 -aadmin:password pmdf2ms.msg 
```
    At this point the test message should appear in the Microsoft Mail user's mailbox.
  - Sending a test message from Microsoft Mail. Address mail to the PMDF post office with an address such as
```
jsmith@acme.com 
```
  - Export the Microsoft Mail messages for the PMDF post office. As a result of the previous step, there should now be a mail message waiting to be exported for PMDF. Export this message with the DOS commands
```
F: 
CD \PMDF 
C:\PMDF\SMTPGET -dc:\maildata\ -f2 -h -aadmin:password ms2pmdf.msg 
```
    Note that you should substitute your Administrator name and password where admin:passord is shown. Note also that the flags -F2 and -H are required for PMDF.
  - Transfer the Microsoft Mail export file to the PMDF system.
  - Process the Microsoft Mail export file. The step prior to the previous step produces the file ms2pmdf.msg which the previous step moved to the directory where PMDF may access it. Use the OpenVMS command
```
$ @PMDF_COM:master ff_local poll
```
    or the UNIX command
```
# pmdf run ff_local poll
```
    to get PMDF to pickup and process this file now.
  - Automate the process. Automate the transfer process, whether using FTP, Kermit, rcp, or whatever---set up a procedure which automates the file transfer. See Section 38.2.2 for different ways to automate the polling process on the PMDF side. If you had used the PMDF-LAN configuration utility, it would have generated a command file pc_post.com (OpenVMS) or a shell script pc_post, which could be used to automate the PMDF side of things; see the checklist file created by the PMDF-LAN configuration utility for additional steps. On the PC side, you should put something like the following in a xfer.bat file, and then run it on your PC.
```
F: 
CD \PMDF 
:LOOP 
C:\PMDF\SMTPPUT -dc:\maildata\ -f2 -aadmin:password pmdf2ms.msg 
C:\PMDF\SMTPGET -dc:\maildata\ -f2 -h -aadmin:password ms2pmdf.msg 
C:\PMDF\DELAY 10min 
GOTO LOOP 
```
    38.7.7 How to use the DOS programs
    The programs INSTALL.EXE , SMTPGET.EXE and SMTPPUT.EXE should be copied from PMDF_ROOT:[other.dos.msmail] (OpenVMS) or /pmdf/other/dos/msmail (UNIX) or directly off the PMDF distribution CD-ROM from [other.dos.msmail] (OpenVMS), /other/dos/msmail (UNIX), or \other\dos\msmail (DOS, Windows, or OS/2), to your PC.
    
    Note:
    The INSTALL.EXE program referred to in this section is the program distributed with PMDF. You must copy this INSTALL.EXE program from the PMDF distribution; it is not the program by the same name distributed with the Microsoft SMTP gateway.
    
    38.7.7.1 Gateway configuration program INSTALL.EXE
    After installing the Microsoft Mail SMTP Access Component, the DOS program INSTALL.EXE distributed with PMDF can be used to reinstall, modify and remove addressing and routing gateway configuration information for Microsoft Mail post offices. It allows the following operations to be performed:
    - installation of a direct gateway
    - removal of a direct or indirect gateway
    - conversion of an existing gateway to either direct or indirect
    - modification of indirect gateway routing
    The normal procedure for the installation of the SMTP gateway is:
    - Copy the following gateway files (INSTALL.EXE, INSTALL.EXE, INSTALL.EXE) from PMDF_ROOT:[other.dos.msmail] (OpenVMS) or /pmdf/other/dos/msmail (UNIX) to the disk where the PC can see them.
    - Run the INSTALL program for the gateway on the post offices.
    - Run the Microsoft SMTP Gateway Access installation program to enable the gateway on the post offices.
      
      38.7.7.2 Direct gateway post offices
      Use INSTALL with the -H flag for a quick summary of the options it accepts.
      To install the SMTP gateway with the post office files on drive M: in the \MAILDATA directory, enter the following at the DOS prompt:
```
INSTALL -C -G -SSMTP -Dm:\maildata -V 
```
      The parameters may be specified in upper and/or lower case in any order on the command line. The -C flag (Create) is the default and can be omitted. The default post office data file path is M:, so the -D clause can be omitted if the post office data files happen to be in the M drive's top directory.
      
      38.7.7.3 Indirect gateway post offices
      To install an indirect (or downstream) post office, you need to specify the network and post office name of the gateway which will be performing the downstream routing:
```
INSTALL -C -I -SSMTP -Dn: -Nmsnet -Pdirectpo -V 
```
      the -I flag specifies that the gateway is to be indirect. The -N flag specifies the name of the routing network, and the -P flag specifies the name of the routing post office. An error message is returned if the downstream post office does not exist or if a direct connection between the two post offices has not been defined in the ADMIN.EXE program.
      
      38.7.7.4 Update gateway routing
      After an indirect gateway has been installed, it may be necessary to modify the routing to a different downstream routing post office. The update command requires the indirect post office mail data path, and new network and post office names of the downstream postoffice:
```
INSTALL -U -I -SSMTP -Dn: -Nmsnet -Pnextpo -V 
```
      38.7.7.5 Remove a gateway
      To remove a gateway, use the command:
```
INSTALL -R -SSMTP -Dn:\MAILDATA -V 
```
      where the -D flag specifies the path to the post office data files.
      When removing a gateway, there may still be unsent mail in the gateway queues. There are two options available to handle the dismissal of these messages. The default -R flag will return an error if the gateway queue is not empty. The administrator then should use the ADMIN program to return or delete any queued messages to the sender before trying to remove the gateway again. If it is not possible to return the messages to the sender, the -R flag will force the removal of the gateway queue. This will leave the queued messages and attachments in the mail database until it is compressed.
      
      38.7.7.6 Running the SMTPGET program
      The SMTPGET program extracts messages in the Microsoft Mail post office data file SMTP queue into a file. The command syntax is:
```
SMTPGET -Ddrive -F2 -H -Aadmin:password outfile
```
      The -D flag specifies the path for the post office data files, with -DM: as the default. The -F2 flag specifies the use of carriage return, line feed as the newline sequence in the output file. This is required for PMDF. The -H flag generates message headers in the extended Mail message format. This is required for PMDF. The -A flag is used to specify the gateway mailbox and password. These are assigned to the gateway by the Microsoft Mail administrator to prevent unauthorized use of FFAPI. The mailbox must be created with administrator privileges. Optionally, the -MS flag can be used to have a log file SENT.LOG created in the log subdirectory. This file contains a log of messages sent to SMTP from the Microsoft Mail users. For example, if your mail files are in the M:\MAILDATA\ directory, then the log file will be M:\MAILDATA\LOG\SENT.LOG. outfile is the name of the output file to be generated.
      An example command looks like:
```
M:\SMTPGET -DM:\MAILDATA\ -F2 -H -AADMIN:PWD MS2PMDF.MSG
```
      38.7.7.7 Running the SMTPPUT program
      The SMTPPUT program puts messages into the Microsoft Mail post office data file from a input file generated by PMDF's FF channel. The command syntax is:
```
SMTPPUT -Ddrive -F2 -Aadmin:password inputfile
```
      The -D flag specifies the path for the post office data files. The default is -dM: . The -F2 flag specifies to the input file use carriage return, line feed as the newline sequence. This is required for PMDF. The -A flag is used to specify the gateway mailbox and password. These are assigned to the gateway by the Microsoft Mail administrator to prevent unauthorized use of FFAPI. The mailbox must be created with administrator privileges. Optionally, the -MR flag can be used to have a log file RECV.LOG created in the log subdirectory. This file contains a log of messages received for the Microsoft Mail users. For example, if your mail files are in the M:\MAILDATA\ directory, then the log file will be M:\MAILDATA\LOG\RECV.LOG. The inputfile is the name of the input file to be processed.
      An example command looks like:
```
M:\SMTPPUT -DM:\MAILDATA\ -F2 -AADMIN:PWD PMDF2MS.MSG
```
      Note
      
      ⁸ See the appropriate edition of the PMDF Installation Guide for the use of the PMDF-LAN configuration utility.
      
      ⁹ You should not use a directory in the PMDF directory tree.
      
      ^a See the description and examples of use of the PMDF-LAN configuration utility in the appropriate edition of the PMDF Installation Guide .
      
      Previous | Next | Contents

PMDF System Manager's GuidePMDF-REF-6.0

38.7 Microsoft Mail channels

38.7.1.1 Required Microsoft products

ACCESS_METHOD (0)

BINARY_ENCODING (string)

CHECK_LINE_LENGTH (0, 1, 2, or 3)

DELETE_HEADERS (0, 1, 2 or 3)

FF_DEFAULT_NETWORK (string)

FF_DEFAULT_POSTOFFICE (string)

FF_GATEWAY_STRTYPE (string)

FF_GATEWAY_INTTYPE (integer)

FF_INPUT_FILE_NAME (string)

FF_INPUT_FILE_PATTERN (string)

FF_OUTPUT_FILE_NAME (string)

FF_MASTER_DELETE (0 or 1)

FF_SLAVE_DELETE (0 or 1)

REPEAT_COUNT (integer)

SLEEP_TIME (integer)

SAVE_HEADERS (0, 1, 2 or 3)

SEPARATE_COUNT (integer)

SEPARATE_FILES (integer)

SEPARATE_SIZE (integer)

TIMEZONE (string)

Note

8 See the appropriate edition of the PMDF Installation Guide for the use of the PMDF-LAN configuration utility.

9 You should not use a directory in the PMDF directory tree.

a See the description and examples of use of the PMDF-LAN configuration utility in the appropriate edition of the PMDF Installation Guide .

PMDF System Manager's Guide
PMDF-REF-6.0

⁸ See the appropriate edition of the PMDF Installation Guide for the use of the PMDF-LAN configuration utility.

⁹ You should not use a directory in the PMDF directory tree.

^a See the description and examples of use of the PMDF-LAN configuration utility in the appropriate edition of the PMDF Installation Guide .