Out-of-office and auto-responders

An auto-reply that quotes your original message can carry your tracking image along with it. When that reply lands in your inbox and your client shows images, the pixel fires, and you have just "opened" your own email. If your log shows an open at the moment an auto-reply arrived, this is the likely cause.

Calendar and travel parsers

Messages that look like bookings, invites or receipts are often read by assistants that pull out dates and locations. Some render the HTML to do it. The result is an open within seconds of delivery, often from a data-centre address.

Preview panes and notifications

Many desktop clients render the message in a reading pane as soon as it is selected, even briefly while someone scrolls past. Phone notifications can also fetch images for rich previews. These are real devices, but a glance is not the same as reading.

Mail rules and forwarding

Server-side rules that forward copies to an assistant, a ticketing system or a CRM can create opens in places the original recipient never sees. One message can then show several opens from different networks.

How to tell them apart

• Timing: opens within a few seconds of sending are almost always automated.
• Coincidence with your own inbox: an open at the moment you read their reply is probably you.
• Clusters: several opens in the same second from different addresses suggest scanning or forwarding.
• Later, isolated opens during the recipient's working hours are the most likely to be human.

None of these rules is perfect, and that is the point. A simple tracker such as mailpixel.org records that an image was fetched, and when. Turning that into "a person read it" is a judgement you make, ideally with these machine sources in mind and without leaning on any single event.