OmniMessaging ZLE Adapter Programmer's Guide 6.2

OmniMessaging ZLE Mail Adapter Installation Guide
Opsol Confidential and Proprietary 7
request_type OMNI_ReqType R OMNI_FORWARD I
returnCode ADAPT_ReturnCode O
orig_name char R From User name I
orig_address char R From User Mail
Address
I
subject char O Subject of mail I
subject_len unsigned short R
(Zero if no subject)
String length of
subject
I
dest_addresses OMNI_recipient R (1 to 10 recipients
can be specified)
Recipient Addresses I
dest_address_count unsigned short R (total number of
recipients)
1-10 I
message_id char R Message Id to be
forwarded
I
message_body char O Char buff up to
25000 bytes
I
fwdMsgFlag unsigned long O (OMNI_FULL if not
used)
OMNI_HEADERONLY
/ OMNI_FULL
I
3.7 Retrieve Email Message -- OSS
This is very similar to retrieving message discussed above. With this API call, the
attachments are retrieved at OSS location.
The directory path structure is one of the inputs and attachments are created in that
location. Before calling this API, verify that the directory structure in OSS exists.
IPC structure: OMNI_getOSSMessage
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
attach_dir char R Directory location in OSS I
attachments OMNI_attachment O
attach_count unsigned short No of attachments
retrieved
O
* One of the two, message_id or UID is required. If both are specified, UID is picked
up and message_id is ignored.