Parse API should post SMTP Headers

Edit Subject

Hi Tony,
Do you think we should post headers as different parameters or just post the raw message in an additional parameter?

Hi Isaac - do you mean each individual headers as a different parameter, a parameter containing all the headers or a parameter containing the whole raw message?

I would have thought the 2nd option would be OK, but would be interested to hear what other people thought... depends on how reliable your parsing is, I guess!

I believe Isaac was referring to either posting the individual headers as different parameters (one parameter per header), or posting the entire raw message in its own parameter (in addition to the rest of the parsed data)

It'd probably be enough to have the raw headers as a single parameter for further parsing in my application - there's no need to send the entire raw message (because you already parse it out into parts and attachments, right?). A parameter per header ('To', 'Received', 'Reply-To' would be OK too).

Thanks Tony,

We'll update this thread as we make more progress on this feature.

We would like to have the complete raw message!

+1 for posting the entire raw message, for two reasons:
1. The content-type and encoding for each email part are lost with the current method, making it a challenge to deal with multiple character sets.
2. It's currently impossible to reconstruct an email with inline attachments, since the CID is not included with attachment information.

Thanks for considering!

Is this already implemented?

I should mention here that both of my points above have been addressed - SendGrid now (awesomely) posts the character encoding for each part of the email, in addition to providing attachment information like CID. With those, and all the other information, I no longer see the need for posting the entire message.

Character encoding information has been there for quite awhile - I *think* the attachment info is relatively new though (perhaps added in the last month or so?)

Hi Jeff,

Yes, the attachment info was added at another user request. Thanks for your feedback!