PMDF System Manager's Guide
PMDF-REF-6.0

Most PMDF messages are stored as text files. Multimedia mail support for various sorts of binary information, such as OpenVMS binary files, compound documents, and image data are supported via printable text encodings. Messages with multiple parts (possibly containing different types of data) are represented as a series of text sections separated by special unique delimiter strings.

Note that messages stored by PMDF-FAX and PMDF-X400 do not always follow these guidelines.

A sample mail message file is given in Figure 1-1 below.

Figure 1-1 Sample mail message file

u;DAN 
c;l 
s;SIGURD.INNOSOFT.COM 
i;01G6YTYFU6748WWH0Y@SIGURD.INNOSOFT.COM 
h;<01G6YTYFU6748WWH0Y@SIGURD.INNOSOFT.COM> 
m;DAN@SIGURD.INNOSOFT.COM  (1)
j;rfc822 
f;ned@SIGURD.INNOSOFT.COM 
ned@YMIR.CLAREMONT.EDU 
Boundary_(ID_bNmDRTvfQNkeUUBbOugFTQ) (2)
Received: from SIGURD.INNOSOFT.COM by SIGURD.INNOSOFT.COM (PMDF V5.2-0 #9441) (3)
 id <01G6YTYFU6748WWH0Y@SIGURD.INNOSOFT.COM> for ned@SIGURD.INNOSOFT.COM; 
 Sat, 8 Nov 1997 14:55:51 PST 
Date: Sat, 08 Nov 1997 14:55:48 -0800 (PST) 
From: "Daniel C. Newman" <DAN@SIGURD.INNOSOFT.COM> 
Subject: Mrochek ate my shoe 
To: ned@SIGURD.INNOSOFT.COM 
Message-id: <01G6YTYFU6748WWH0Y@SIGURD.INNOSOFT.COM> 
MIME-version: 1.0 
Content-type: TEXT/PLAIN; CHARSET=US-ASCII 
Content-transfer-encoding: 7BIT 
X-Envelope-to: ned@SIGURD.INNOSOFT.COM 
X-VMS-To: IN%"ned@sigurd.innosoft.com" 
 (4)
Ned, 
 
   Mrochek ate another shoe of mine.... 
 
                              Dan 
Boundary_(ID_bNmDRTvfQNkeUUBbOugFTQ) (5)

1. The message envelope. The first records in the file contain message envelope (i.e., transport) information.
2. The envelope is terminated either by a line containing a boundary marker, or by a line containing two CTRL/A characters.
3. The header lines of the message follow the envelope; their format is mandated by RFC 822. ^c
4. There may be any number of message header lines; the message header formed by this collection of header lines is terminated by a single blank line after which follows the message body.
5. The message is terminated by a boundary marker matching the boundary marker at the beginning of the message, (or by a sequence of five CTRL/As if the message start was indicated using CTRL/As).

Innosoft reserves the right to change this format in future releases of PMDF. User-written applications that either read or write queued PMDF message files should make use of appropriate PMDF library routines; see the PMDF Programmer's Reference Manual . Use of the PMDF API will insulate user applications from any future message format changes.

Note

^c A copy of RFC 822, Standard for the Format of ARPA Internet Text Messages, written by David Crocker may be found under the PMDF documentation directory, usually PMDF_ROOT:[doc.rfc] on OpenVMS systems or /pmdf/doc/rfc on UNIX systems or the rfc subdirectory of the PMDF documention directory (usually C:\pmdf\doc) on NT.