Free Webinar: Using Postmark to send effective emails Learn how to improve the effectiveness of your transactional emails
x

Why doesn't the attachment content of my inbound message show up in Activity?

If there was an attachment included in an inbound message, there will also be a Content field that includes the attachment’s base64 encoded content when we post the inbound message to your URL. We send this in the JSON we post to your webhook URL but it will not show in the JSON tab in your Activity page for the inbound message.

You can see the base64 we sent in the Raw Source tab, however. Depending on the size of the attachment, some of the base64 might be omitted in the Raw Source tab but the complete attachment base64 bytes are sent in the JSON we post to your webhook URL.
As an example, the Attachments field will have this form when we POST to your inbound webhook URL:
"Attachments":[
 {
 "Name":"myimage.png",
 "Content":"[BASE64-ENCODED CONTENT]",
 "ContentType":"image/png",
 "ContentLength": 4096,
 "ContentID":"myimage.png@01CE7342.75E71F80"
 },
 {
 "Name":"mypaper.doc",
 "Content":"[BASE64-ENCODED CONTENT]",
 "ContentType":"application/msword",
 "ContentLength": 16384,
 "ContentID":""
 }
]
If you want to confirm we are sending the attachment bytes in the Content field, you can quickly set up a Request Catcher and use the URL it generates for you to inspect a POST from us.
  1. Create a new URL
  2. Set the URL it generates for you as your inbound webhook URL in your Server's settings in Postmark (Settings > Inbound)
  3. Send an email with an attachment to your inbound email address
  4. Inspect the POST you receive at your Request Catcher URL to see the base64 bytes in the Attachments array's "Content" field.

Keep in mind that RequestBin does have a size limit on what you can post, so you will want to test with smaller attachments. Postmark's inbound message size limit is 25 MB.

Last updated July 5th, 2018

Still need some help?

Our customer success team has your back!