Full-chain read tracking on the sending side, and beacon recognition with fake-read governance on the receiving side.
Important emails go into a black box: did they read it, and when? And on the receiving side, merely opening your own sent copy marks the message "read" — fake reads are annoying.
Email has no native "read" concept. Common solutions embed a tracking pixel, but naive implementations count your own view of the sent copy — and security-gateway machine scans — as "recipient read", which corrupts the data.
Q: Does read tracking require the recipient to use SJ-Mail too?
A: No. Sender-side tracking works with any regular mail client (standard tracking mechanism); the recognition and governance are protections SJ-Mail gives to recipients.
Q: What is a fake read and how does SJ-Mail handle it?
A: Viewing your own sent copy, and security-gateway machine scans, are both wrongly counted as "recipient read" by naive implementations. SJ-Mail excludes both (self_open / bot_open governance) and counts only real recipient reads.
Q: Is there a limit on tracking?
A: A quota panel shows usage transparently; limits follow the service policy and never affect mail delivery itself.