Proposal for a new newsletters standard

[serrq]

1. Until now, if we want to opt out of receiving a newsletter, we have to press a button in our email and find ourselves catapulted to an external website and finish this procedure externally. However, this doesn't prevents a potential attacker from continuing to email us against our will.

2. If I change my email address, I must redo every newsletter, website by website.

How do I solve these problems?

It needs a token.

When I ask to subscribe to a newsletter the website must generate a unique token that I will amount in my email.

If I change email or want to disable the reception I simply make choices internally in settings.

I can disable the token, I can delete it, I can transfer it (with its private key) to a new email address.

The token is nothing more than a public key. Only those who have the corresponding private key can access the contents of the newsletter.

I am not a developer.
Who builds this new standard?