I don't really mind someone knowing I opened an email, just like I'm fine with a website knowing I visited (say using plausible.io rather than google analytics). I get that that's useful to them for non-nefarious reasons.
I don't really mind someone knowing I opened an email, just like I'm fine with a website knowing I visited (say using plausible.io rather than google analytics). I get that that's useful to them for non-nefarious reasons.
The reason businesses don't rely on them is supposedly because "too many users disabled or rejected them during the past decade".
Even MS Outlook lets end users decline to send read receipts. There's probably some awful group policy system to force it, though.
<img src="https://example.com/cd726f02-d2f4-4c0e-a717-e69044180c59.gif" height="1" width="1">
The image filename is a UUID. The UUID is of course unique for each email sent, but the Web server is configured to serve the same image for any given UUID (after recording the UUID as an "open" into a database).
There isn't a way for an email client to be certain that the image is or isn't a tracking pixel.