#94904Is spamProtectEmailAddresses still worth keeping around?
Description
This question is around for quite some time, and I think it’s worth discussing whether this option makes sense or not, or if we should deprecate it.
The main issue with having it around is still some quirks in our code base. Mainly the issue is regarding Content-Security-Policy (spamProtectEmailAddresses does not work with proper CSPs), and having inline JS which is output in Frontend (e.g. a separate JS file for the 50 lines of code).
I think it’s best to have good and qualified feedback with statistics and numbers before we should move on regarding this feature.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.