Manycom Solutions

Home > Solutions > Manycom Email > Details


Manycom Email

Introduction | Benefits | Example Use Cases | Solution Details | Requirements | Availability and Services | Prices | Documentation


MCM Email is technically a SMTP and POP3 client and email ‘agent’ containing the base conversion functions needed between the local data format and the Internet email message standards, RFC-822/MIME. Consequently, for sending and retrieving email messages, MCM Email can communicate with all standard SMTP and POP3 servers, including those of OS/400, i5/OS, Lotus Notes, MS Office and others, be they locating in your own or public networks.

When sending, the original OS/400 or i5/OS message can be a spool file, database file, short text message up to 256 characters, binary stream file in the hierarchical IFS/‘root’ file system, etc. The received messages are saved in database work files. This allows accessing them from customer applications.

The receiver will see the email message exactly as it had been sent with any ‘standard’ PC email software. The sender can set the email message headers such as sender and receiver addresses, organization, and subject and attachment names.

The message can be a single or multi-part message consisting of one or several ‘inline’ and/or attachment parts, in any order. Each part can contain character coded text or data, or binary data.

MCM Email provides character code conversion between the national EBCDIC and ASCII code used in Internet email, by default ISO Latin-1, also known as ISO 8859-1.

Binary data can be anything form image formats such as Adobe PDF, RTF, HTML, TIFF or JPEG to program code. These conversions must be performed with separate third party software before creating the sending request by calling the MCM Email API.

Automation is achieved so that the customer application calls the MCM Email API CL command providing in the command parameters the necessary information, for instance:

  • sender and receiver information including the email addresses
  • name of the spool and data base files to send, or alternatively up to 256 character long message texts
  • if the message part should be sent as a ASCII coded text or ‘as is’ in binary format
  • if the message part should be sent as an ‘inline’ text or as an attachment
  • if sent as an attachment, the name and type of the attachment

The API command program adds the provided information as a transfer request entry to the MCM transfer directory. The application is then immediately, in about a second, free to proceed, and MCM system tasks will take care of automatically sending and retrying, if needed, the email message in batch mode in the background.

End user screens of MCM allow controlling and working with the email transfer requests, for instance changing the header information, copying, holding, resending, etc.

For more detailed information, see the MCM Base and MCM Email module descriptions in Products section


Top of the page