search

authindicators / rfc-brand-indicators-for-message-identification

Other
19 stars 6 forks source link

Tracking users with BIMI selectors #14

Open massar opened 6 years ago

massar commented 6 years ago

For every user I send something to I create a new selector:

_user1_dom._bimi.example.org TXT "v=BIMI1; f=png; z=256x256; l=https://example.com/bimitracker/user1@domain.com/";
_user2_dom._bimi.example.org TXT "v=BIMI1; f=png; z=256x256; l=https://example.com/bimitracker/user2@domain.com/";
etc...

in nginx I simply use a rewrite rule to the singular logo, the access log will nicely detail when the user has read the mail.

Then when sending my spam out, I nicely send a different selector, and voila.

I am thus really wondering why the selector has to exist, is it for tracking different spam campaigns?

Companies/organisations do not change logo every day, thus what is the selector really for (except that it copies a concept of DKIM....)

The selector also does not make it easy for caching the logos on a central (mail-provider-side) server.... having no selector would thus be very beneficial.

Please detail at least why the selector exists...