majjo/AdguardFilters
1
0
Fork 0
mirror of https://github.com/AdguardTeam/AdguardFilters.git synced 2026-08-31 12:23:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Prepare files for AdGuard Mail Tracking Protection filter (#231199)

Browse Source 
* Prepare files for AdGuard Mail Tracking Protection filter

* Clarified the descriptions
This commit is contained in:
Alex
2026-05-14 13:23:46 +03:00
committed by GitHub
parent dd28e10e9f
commit 5bf5b361a7
3 changed files with 37 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
MailTrackingFilter/sections/allowlist.txt Normal file
View File

@@ -0,0 +1,9 @@
!
! This section contains the list of rules that fix incorrect blocking.
! Rules should be domain-specific.
! If a rule causes a problem only in a specific email client, it should be restricted to that domain.
! If it causes problems in more clients, it should be changed or deleted.
!
! Good: @@ci3.googleusercontent.com/meips/*/wf/open?upn=$image,domain=mail.google.com
! Bad: @@/wf/open?upn= (too wide, or must be removed)
!

13
MailTrackingFilter/sections/general_url.txt Normal file
View File

@@ -0,0 +1,13 @@
!
! This section contains generic mail tracking rules — broad patterns (e.g. `pix.gif`, `e.gif`) that
! are commonly used by many different email providers and marketing platforms.
! IMPORTANT: add a comment that explains where a pattern comes from (what tracking company is using it).
! Ideally, supply a link to the document that explains how this pattern is used.
!
! To block tracking pixels in some email clients, percent-encoding is required. Therefore, both variants
! must be added - the original and the encoded version.
!
! Good: /pix.gif?$image
! %2Fpix.gif%3F$image
! Bad: ||newegg.com/mr/ (for instance, should be in specific.txt)
!

15
MailTrackingFilter/sections/specific.txt Normal file
View File

@@ -0,0 +1,15 @@
!
! This section contains rules targeting tracking pixels from specific domains and email services.
! Note that || prefix cannot be used because mail tracking pixels are often proxied by mail providers.
! It is problematic that due to how Gmail proxy work, these domains aren't even exposed on the network level.
! Fortunately, extensions can see them (Gmail puts the real URL in the location.hash part of the src).
! To block tracking pixels in some email clients, percent-encoding is required. Therefore, both variants
! must be added - the original and the encoded version.
!
! Good: link.example.org$image
! newegg.com/mr/*.gif?r=
! newegg.com%2Fmr%2F*.gif%3Fr%3D
! Bad: ||example.org^$script (treated it as regular analytics and block it in the Tracking Protection filter,
! if a script in not proxied)
!