Forums

Hi Team,

We are currently validating an approach to extract historical emails from Maximizer via Octopus API and wanted to confirm the structure and consistency of the email payloads returned by the API.

From our testing so far, the octopus/BinaryDownload API responses appear to return complete MIME/RFC822 formatted email content, including headers and multipart sections such as:

• MIME-Version
• Content-Type
• multipart/mixed boundaries
• attachment sections
• inline images
• HTML/plan-text body content

We want to confirm the following:

• Does binarydownload operation always return originial MIME/RFC822
• Are attachments consistently included as MIME multipart sections within the same payload?
• Could there be edge cases, unsupported email formats, historical email messages etc. which might not fall into above approach?
• Could there be scenario's where this would behave differently like for large emails etc.?
• How to differentiate emails vs other documents from output?
• Is there a better approach to sync Outlook emails captured in Maximizer to another CRM system?

Our current design depends on parsing the MIME structure to separate email header/body, attachments, inline content so we want to ensure we have to understood correctly.

A detailed response of any reference documentation around this would really be helpful. Thanks!