OmniMessaging ZLE Adapter Programmer's Guide 6.2

OmniMessaging ZLE Mail Adapter Installation Guide
Opsol Confidential and Proprietary 5
volume-subvolume location specified by the Zle Adapter server param "OMNI-TEMP-
FILE-LOC". If the message body text does not fit in the IPC field of message_body, it
is also retrieved in a zero code guardian file in the same location as the attachments.
The attachment name for the message body text is “Message Body Text" with a
content type of “text” and subtype of “plain”.
IPC structure: OMNI_getMessage
Field Name Data Type Required(R)/Optional
(o)
Value Input/
Output
request_type OMNI_ReqType R OMNI_GET I
returnCode ADAPT_ReturnCode O
orig_address char R Mail address I
password char R Password I
mailbox_name char R INBOX (or other if
set)
I
message_id char O * Message Id to be
fetched
I
uid unsigned long O * Unique ID of
message to be
fetched
I
attachments OMNI_attachment O
attach_count unsigned short No of
attachments
retrieved
O
message_body char Char buff up to
25000 bytes
O
encryption_flag ADAPT_Encryption O
(OMNI_NO_ENCRYPTION
if not used)
DS, E, DSE I
* One of the two, message_id or UID is required. If both are specified, UID is picked
and message_id is ignored.
3.4 Retrieve Email Message With Header Info
This is very similar to retrieving message discussed above. With this API call, the
headers are parsed and retrieved as a separate structure.
There is support for up to 10 attachments of unlimited size. Both ASCII and binary
attachment types are supported. There is support for message body text and RFC822
header of unlimited size. If the message body text or RFC822 header information fits
in the IPC fields of message_body or headers, it is populated in the IPC. If it exceeds
the IPC limits, it is returned as attachments with names “Message Body Text” or
“RFC Header”. The attachments are extracted and placed as guardian zero code files
in the volume-subvolume location specified by the Zle Adapter server param "OMNI-
TEMP-FILE-LOC".
IPC structure: OMNI_getTelMessage