Generating an RFC 2183 compliant email #4612

andrewlmessagepoint · 2024-07-24T19:04:06Z

andrewlmessagepoint
Jul 24, 2024

I am currently generating HTML emails with inlined images. What I'm finding is that another tool downstream does not like the MIME headers that are being generated for image parts. Specifically this tool wants the headers to look like:
Content-ID:
Content-Type: image/jpeg
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="image.jpeg"

instead I'm getting
Content-ID:
Content-Type: image/jpeg; name=image.jpeg
Content-Transfer-Encoding: base64
Content-Disposition: inline

As a very simplified version of what I'm doing, the code looks something like:

int main()
{
   Poco::Net::MailMessage mm;
   std::string htmlSrc = "<html><body><table><tbody><tr><td><img src=\"cid:content1\"/></td></tr></tbody></table></body></html>";
   Poco::Net::StringPartSource *body = new Poco::Net::StringPartSource(htmlSrc, "text/html; charset=\"UTF-8\"");

   mm.addContent(body, Poco::Net::MailMessage::ENCODING_BASE64);
   
   Poco::Net::MailRecipient recip(Poco::Net::MailRecipient::PRIMARY_RECIPIENT, "[email protected]");
   mm.addRecipient(recip);
   
   mm.setContentType("multipart/related");
   mm.setSubject("test");
   
   Poco::Net::PartSource *ps = new Poco::Net::FilePartSource("image.jpeg", "image.jpeg", "image/jpeg");
   mm.addPart(ps->filename(), ps, Poco::Net::MailMessage::CONTENT_INLINE, Poco::Net::MailMessage::ENCODING_BASE64);
   ps->headers().add("Content-ID", "<content1>");
   mm.write(std::cout);
}

Is it possible to get the filename= on the Content-Disposition header? Should I be using a different method to put the inlined images into my email? My understand is that what is currently being done by MailMessage::writePart(...) is deprecated. Can anybody provide some insight here? Is there anything I can do that will allow me to generate the headers as I need them?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Generating an RFC 2183 compliant email #4612

{{title}}

Replies: 0 comments

Select a reply

Generating an RFC 2183 compliant email #4612

andrewlmessagepoint Jul 24, 2024

Replies: 0 comments

andrewlmessagepoint
Jul 24, 2024