Closed Bug 1636787 Opened 5 years ago Closed 5 days ago

Block the mailtrack.io email tracking

Categories

(Core :: Privacy: Anti-Tracking, enhancement)

76 Branch
enhancement

Tracking

()

RESOLVED FIXED

People

(Reporter: nasir8891, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

Firefox have a wonderful feature to block tracking services from its core. But it can not block mailtrack.io email tracking. This is very annoying being tracked by others in my email inbox.

Actual results:

I opened emails from the Gmail inbox and mailtrack.io alerting the serder about opening the email.

Expected results:

Firebox tracking protection should block that service.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Privacy: Anti-Tracking
Product: Firefox → Core

Would you mind to help us understand how mailtrack.io is doing email tracking? Tracking Protection operates on hostnames, so if we're missing a hostname we could report it to Disconnect for investigation.

Flags: needinfo?(nasir8891)

mailtrack.io is a browser extension and you can integrate that with your email account. After that when you send any email to anyone it adds a tracking code. So when the other person receive and open the email it sends a notification to the sender. It will also record how many times you are opening the email and in what times.

Now if i am the person who received that email with the tracking code, i want to block the Mailtrack to record and send these data to the sender.

Flags: needinfo?(nasir8891)
Severity: normal → S3

mailtrack.io is now on the email-tracking list as of April 2022: https://github.com/mozilla-services/shavar-prod-lists/commit/469fe397b51766e4aa8e26c228421caafa24f7e1 (roughly Fx101) (also queryable in about:url-classifier)
It is therefore blocked in PBM and in ETP-strict mode.

Status: UNCONFIRMED → RESOLVED
Closed: 5 days ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.