We block any and all code scripts/styles from executing outside of emails.
We don't block images though - if we did then the emails you could usually receive with images will feel plain.. won't it? If I understand you correctly?
Allowing remote images to load allows for a tracking signal to be sent from the email client. Blocking images allows the user to choose whether that signal is sent.
Ohh I see.
Like a Facebook Pixels tracking image.
No, I don't think that's blocked. Then again, it's not blocked in most email clients, perhaps it's difficult to accomplish.
Nonetheless, I've added it to the list of upcoming features as I believe it's worth a shot!
I believe there are a couple of approaches to this with varying amount of data storage, You can download all images immediately as the email is received (thus preventing image tracking as every image would then be clicked immediately) or have the ability to block all images and selectively turn them on when necessary (unless the image is inline etc).
Cool - not saying you have to do it like them, but the most popular option there is to block all images globally but allow the person to click a button to unblock images for that specific email, which then enables a dialogue to "always unblock images from this sender."
I like that workflow; may be something to consider. I block all images but allow images from known senders, like my parents or co-workers.
I haven’t seen an email with images in years because I always use clients which allow disabling auto-loading.
If I get an email with images it’s usually an email I didn’t want and I block the sender shortly thereafter. Real people don’t tend to send emails with images that are important for understanding the textual content.
We block any and all code scripts/styles from executing outside of emails.
We don't block images though - if we did then the emails you could usually receive with images will feel plain.. won't it? If I understand you correctly?