NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: SMFSEAL, MHS MAIL Utility DOCUMENT ID: TID000382 DOCUMENT REVISION: A DATE: 01JUL93 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: SMFSEL.EXE NOVELL PRODUCT and VERSION: NetWare MHS 1.5 NetWare SMF v71 Developer's Kit for MHS ABSTRACT: This file contains SMFSEAL, which is an MHS submission utility that allows simple messaging from applications. A file with an address is created and copied to a mailbox. SMFSEAL, running as an MHS gateway process, picks up the message and delivers it to MHS. MHS handles it as any other E-Mail message, delivering it to the addressee's MHS mailbox. This file is a beta version, please report any errors or problems to SHOCHSCH NOVELL. _________________________________________________________________ DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. _________________________________________________________________ Self-Extracting File Name: SMFSEL.EXE Files Included Size Date Time SMFSEL.TXT (This File) SMFSEAL.EXE 69177 11-30-89 3:21p SMFSEAL UTILITY People who develop MHS applications may benefit from a new utility called SMFSEAL. The SMFSEAL utility supports the full range of MHS services. SMFSEAL packages the message and submits it to MHS; MHS then mails the message to the addressees. INSTALLING SMFSEAL SMFSEAL can be installed to function as an automatic gateway submission process and also as a program executable from the DOS command line. INSTALLING SMFSEAL AS A GATEWAY When you install SMFSEAL as a gateway, the SMFSEAL program is invoked once for every cycle scheduled by the MHS Connectivity Manager. (This is how all MHS gateways operate.) To install SMFSEAL as an automatic gateway process on an existing MHS host, perform the steps in this section. Note that you must have Supervisor rights toperform the installation. 1) Determine the location where MHS is currently installed. The location is identified by the DOS environment variable MV on the MHS Connectivity Manager workstation. The MV environment variable identifies the name of the drive and directory where the MHS programs are located. (If necessary, refer to the MHS Installation and Operation manual for more information about the MV variable and MHS directory structure.) 2) Create a directory named MV\MHS\MAIL\SMF. This directory is where applications place files for submission to MHS. 3) Log in as the administrative user of MHS and start the MHS Directory Manager. 4) From the Directory Manager menu, select "routes to workgroups, hosts, andgateways." Select "Add entry," and from the menu that appears next, select "Define a gateway." 5) In the menu titled A GATEWAY, type "SMFSEAL" for the host name and press Enter. For the description, type "SMFSeal gateway" and press Enter. You do not need to enter any gateway commands. 6) Select to complete the gateway definition. 7) Exit the MHS Directory Manager and return to the DOS prompt. 8) Copy the file SMFSEAL.EXE from the MHS Utilities diskette to the directory MV\MHS\MAIL\GATES\SMFSEAL\PUBLIC, giving SMFSEAL the filename INPOST.EXE. For example, to copy SMFSEAL from a diskette in drive A to a network drive F and rename it INPOST.EXE, you would enter the following: copy a:\smfseal.exe f:\mhs\mail\gates\smfseal\public\inpost.exe 9) Start MHS. Once every scheduled cycle, MHS will place a call to the SMFSEAL gateway running INPOST.EXE (which is really SMFSEAL.EXE). When SMFSEAL is called in this way, it will seal every file that matches the wildcard pathname MV\MHS\MAIL\SMF\*. NOTE: Note that SMFSEAL returns an exit errorlevel code of 1 if it finds nothing to seal. The MHS gateway processor displays an error report "Inpost Failed" when an Inpost process returns an exit code other than 0. Therefore, when SMFSEAL is run as a gateway process, MHS will display the "Inpost Failed" error message any time the gateway process is run and there are no messages to seal. This is a normal condition for gateway operation of SMFSEAL. INSTALLING AND RUNNING SMFSEAL AS AN EXECUTABLE PROGRAM Some developers may want to use SMFSEAL as a command-line executable program, such as for testing purposes. To allow this, copy the file SMFSEAL.EXE from the MHS Utilities diskette to the MV\MHS\EXE directory. This directory should be in the search path of a properly installed MHS workstation and all workstations set up to run MHS applications. To execute SMFSEAL from the DOS command line, use the following syntax: smfseal [-F | -D] -V -F Filename (including the full pathname if the file is not in the current directory) of the file you want to seal. Wildcards are acceptable but the filename cannot have an extension. If the -F switch is omitted, SMFSEAL attempts to seal all files in the MV\MHS\MAIL\SMF\ directory. -D Name of the directory that contains the files you want to seal. SMFSEAL will attempt to seal any files that do not have an extension. -V The optional -V parameter stands for verbose and causes SMFSEAL to send status information and return codes as it tries to seal each file. SMFSEAL INPUT REQUIREMENTS SMFSEAL accepts messages in the form of DOS files. The minimum fields required for submission to SMFSEAL are: Field Description SMF-64 or ^C Signature field From: user1 @ wkgroup1 Author To: user2 @ wkgroup2 Recipient(s) Blank line terminator Note that SMFSEAL will accept either the character string "SMF-64" or ^C as the signature field on the first line of a message file. If the input file contains SMF-64 as the signature field, SMFSEAL replaces the string with a ^C in the message it constucts from the input file. From the example input message shown, SMFSEAL would construct a message addressed to "user2 @ wkgroup2." If user2 were a user at the local MHS host, then SMFSEAL would deliver the message to the user. Otherwise, SMFSEAL would prepend a routing envelope to the message and submit the message to MHS by placing the message file in the MV\MHS\MAIL\OUT directory. After the message is successfully sealed and submitted to MHS (or delivered to a local user), SMFSEAL deletes the message from the directory in which it was found. If SMFSEAL cannot process a message, the message is left in the submission directory and renamed with a .BAD extension. If SMFSEAL encounters multiple addresses (separated by commas) in the To field, SMFSEAL sends a copy of the message to each addressee. An input file may contain a maximum of 30 comma-delimited addresses in the To field. In addition to the required fields, SMFSEAL also will accept optional body text up to 8K in total length (including the message header). SMFSEAL also will accept any other valid SMF (Standard Message Format) header field. In particular, you may find the following fields useful. Field Description Copies-to: u3 @ wg3, u4 @ wg4 Defines recipients who receive copies Attachment-name: c:\docs\mydoc.doc Attachment filename Send-to: Defines specific recipients Including a Copies-to field in a message causes SMFSEAL to generate copies of the message to each address specified in the field. There can be a maximum of 30 comma-delimited addresses in the Copies-to field. If an Attachment-name field is specified, SMFSEAL will include the specified file as an attachment to the message being sealed. The original attachment file is not deleted after the message has been sealed. The Send-to field may contain 1 to 30 comma-delimited addresses; this field allows for delivering blind copies of a message. An example of using the Send-to field for this purpose is presented in the next section "Example SMFSEAL Files." EXAMPLE SMFSEAL FILES In this section you will find examples of typical message files that can be submitted to SMFSEAL. SIMPLE MESSAGE The following example illustrates the most simple form of message that can be submitted to SMFSEAL . SMF-64
From: user1 @ wg1 To: user2 @ wg2 Optional body text of the message goes here. MESSAGE WITH MULTIPLE RECIPIENTS The following example shows how to address a message intended for multiple recipients. Two recipients have been specified as the primary recipients of the message, and two others have been specified as recipients of copies of the message. SMFSEAL will generate a copy of this message to each recipient identified in the To and Copies-to fields. SMF-64 From: user1 @ wg1 To: user2 @ wg2, user3 @ wg3 Copies-to: user4 @ wg4, user5 @ wg5 Optional body text of the message goes here. MESSAGE WITH AN ATTACHMENT FILE This example shows how to send an attachment file with the message. SMFSEAL attempts to send the file F:\DOCS\MYDOC.DOC with this message. If SMFSEAL ca find and access the specified file, it sends a copy of the file with the message. If SMFSEAL cannot find or access the file, it renames the message file with a .BAD extension and the message is not sent. SMF-64 From: user1 @ wg1 To: user2 @ wg2 Attachment-name: f:\docs\mydoc.doc Optional body text of the message goes here. MESSAGE WITH BLIND-COPY RECIPIENTS This example illustrates how to use an explicit Send-to field in a message submitted to SMFSEAL. A copy of the message will be sent to all addressees in the Send-to field. Note that each addressee identified in the To and Copies-to fields are repeated in the Send-to field. Any addressees specified in the To or Copies-to fields, but missing from the Send-to field, will not receive a copy of the message. Any addressee included in the Send-to field but not in the To or Copies-to fields will receive a "blind-copy" of the message; that is, other recipients of the message will not know the message also was sent to this address. In the following example "other @ recip" will receive a "blind-copy" of this message. SMF-64 Send-to: user2 @ wg2, user3 @ wg3, other @ recip From: user1 @ wg1 To: user2 @ wg2 Copies-to: user3 @ wg3 Optional body text of the message goes here. SMFSEAL ERROR CODES This section lists the errorlevel return codes that could be returned when you execute SMFSEAL from the DOS command line. Error Level Message 0 SMFSEAL found files to seal. (This does not indicate that the files were sealed successfully.) 1 SMFSEAL found no files to seal. 50 Invalid filename specified to SMFSEAL in -F switch; or invalid or nonexistent directory specified in -D switch. 52 Environment error, such as the system date is not set or the MV setting is missing or invalid. 255 Unknown other error. ÿ