Technically, embedded images are a lot like attachments, but mail clients are smart enough not to display the little has-attachment paper clip download widget because the MIME headers for the image will say "Content-disposition: inline" instead of "Content-disposition: attachment". Then the HTML img element references it using the cid: scheme instead of the https: scheme or similar. Anyway, the experience is great.
I suspect Mail Studio doesn't offer this because its MO is that "Designs are exported as standard HTML and can be imported in your email marketing platform of choice." This embedded image technique would require that Mail Studio export (or send) the entire multipart MIME message, not just the HTML part.
Yes, that's exactly what happens. Proxying the image only hides the user's IP address. If the images in the email load from external resources like https://example.com/fetch-resource?id=something_unique GMail has no way of knowing if something_unique uniquely identifies a user.
This is why disabling images is helpful. Of course Gmail also lets you enable images per sender, and you may find that quite acceptable for sites you have a relationship with (e.g. a shopping site which already knows your IP address and is sending you delivery notifications).
> Google scans images for signs of suspicious content before you receive them.
> These scans make images safer because:
> - Senders can’t use image loading to get information about your computer or location.
> - Senders can't use the image to set or read cookies in your browser.
> - Gmail checks the images for known harmful software. Sometimes, senders may know whether you've opened an email that has an image. Gmail scans every message for suspicious content. If Gmail thinks that a sender or message is suspicious, images aren’t shown and you’ll be asked if you want to see the images.".
###
Personally, I think this is quite silly, because I routinely disclose my IP address and HTTP headers without considering it particularly sensitive, but I don't want senders to know that their their email messages have been opened.
[0] https://blog.filippo.io/how-the-new-gmail-image-proxy-works-...
If you wanted to validate it yourself instead of trusting Gmail to do it for you, you'd use the "Show original" feature which gives you the original (per its namesake) without any rewriting as well. I assume (but haven't tested) that connecting to your mailbox via IMAP, POP, etc. also causes you to retrieve the original, with the rewriting only coming into play when using the Gmail web interface.
The responsible thing for services like gmail and o365 to do would be to eat the resource costs and just open ALL external content within a privacy sandbox, thereby polluting the data. Then you can re-enable displaying of images for everyone and the experience for designers and end users gets better.
What it can’t do sadly is strip out tracking functions (unique IDs and such). Dunno how that could even be solved tbh
What the parent is suggesting is for Gmail to download the images as soon as the server receives the email, thereby rendering any tracking data meaningless.
My messages still don't load remote images and are topped with "Some content in this message has been blocked because the sender isn't in your Safe senders list" followed by a link to add the sender's address to the trusted list and another link to show blocked content in this particular message.
I have Apple's Mail desktop and mobile apps set to not load remote content but I think the default is for them to load.
I wager Outlook users are less likely to have remote images enabled
Some of the biggest companies in Europe use Outlook the desktop client, with said external resources disabled.
May differ in technically more advanced countries, of course.
A desktop client with a thin wrapper around the websinterface would be best.
So, I don't know what designers use to receive e-mail, but here in the non-designer / non-linux world, Outlook is pretty popular. Now, Outlook - at least all configurations I have seen, has pictures via HTML disabled. I have sampled a few IT departments only, of course, but I feel like this is probably a pretty common policy.
So let me tell you:
Your picture banners, your "rounded corner buttons", your main engagement centerpiece that's just a picture ... it all ends up being one of those nice 90's type beveled empty box we remember from surfing with IE and ISDN.
This may be a shock, but it really doesn't make your important newsletter look any better. So, if you are not specifically going for nostalgic "bad modem connection" look and feel, maybe ease off the HTML pictures a bit, okay?