Emails are hard
Emails are hard
yeah it uses this really neat semantic rendering programming language for serving structured documents across servers
It’s a bit tricky, but anyone with at least a Masters in CompSci should be able to parse some of it enough to get the gist. It goes like this
<img src="FILENAME" />I feel like the level of snark in your reply is… High. It doesn’t make for a pleasant interaction, and it doesn’t help make lemmy a nice place to be.
So, if the image you want to put into your email is not hosted somewhere, what’s the best way to go about this, ensuring compatibility?
I’m just being a silly billy it’s not directed at you.
It’s more like “ah if only there was a simple solution that could’ve been used.”
All images are hosted somewhere, I would consider an intern fresh out of college know how to correctly add an image to an email, or at least only be told once if somehow they had never seen this before.
So, if the image you want to put into your email is not hosted somewhere, what’s the best way to go about this, ensuring compatibility?
You can base64-encode the image file. It’s super-jank, but it works, even in Outlook.
Let me know if I can explain it more clearly.
Multi-part MIME containing inline images is actually what you’re looking for and it’s fairly easy to implement.
Here’s an example. They handwave over the html section that actually refers to the inline images that they embed, but that’s the basic layout you need.