Proofpoint Secure Email Relay Mail API Package

Improvements

• Fixed internal error handling to pass exceptions to caller.
• Implemented factory methods for Attachments to better match Proofpoint API specs.
  • Attachment.FromBase64String()
  • Attachment.FromFile()
  • Attachment.FromBytes()
• Removed exception when passing empty file, base64, or bytes to create attachments.

Known Issues

I've reached out to product management regarding a possible bug caused by empty file content. Empty files should be allowed to be sent via email but the API currently will reject those messages. This is most likely a corner case but in the event a system generates an empty file, that file will be rejected by the REST endpoint. Below is an example of empty content.

{
      "content": "",
      "disposition": "attachment",
      "filename": "empty.txt",
      "id": "1ed38149-70b2-4476-84a1-83e73913d43c",
      "type": "text/plain"
}

This type of content leads to an REST response with error.

Status Code: 400 BadRequest
Message ID:
Reason: attachments[0].content is required
Request ID: fe9a1acf60a20c9d90bed843f6530156
Raw JSON: {"request_id":"fe9a1acf60a20c9d90bed843f6530156","reason":"attachments[0].content is required"}

Full Changelog: v0.0.4...v0.0.5