Hi @esackbauer
I’m sorry if this sounds a bit blunt, but the Mailcow project is aimed at people who are actively choosing to take back control of their data, to encourage the use of alternatives to the GAFAM companies that exploit personal information. It’s therefore an initiative that helps raise user awareness and responsibility when it comes to data security.
When several of these users are trying to play by the rules and express a need—especially within a community-driven open-source project—I don’t think they should be discouraged from joining the discussion or from wanting to improve an already solid system.
After all, the very existence of this request simply shows that it could be a (fairly inexpensive) evolution of the system that meets a real need, even if you personally believe it’s unnecessary.
Once again, I’ve worked around this need by setting up a reverse proxy as suggested by the help from this community, but adding the filtering module directly to the container’s Nginx and offering it as an option is not entirely useless for the broader user base of this project.
–
Léo.