Jan 🏳️⚧️🇨🇦
-
Something in me chafes at just hanging up on connections from problematic mail hosts. I'd like to deliver a notification so a user can tell their admin more than "messages for this domain/address always seem to bounce back after some days". "Your netblock sends too much spam/phishing/whatever, send mail from somewhere else if you want it to be delivered here" is more useful than that, even. I know haproxy can be scripted with Lua, but that's some yak shaving there.
-
Fortunately, Mailcow runs entirely in docker containers, which means I'm easily able to install haproxy on the mailserver and get a minimal sunday-news install going.
When that's working the way I want it to, I'll try to script or template the setup in some fashion and do a proper sunday-news release.
It'll be very simple at first -- just some haproxy config. I intend to make it more approachable as I can, though.
-
It seems that a lot of IP addresses being added to netfilter can result in the Mailcow UI not working, and the refrain (at least in issue 5273: https://github.com/mailcow/mailcow-dockerized/issues/5273) is to rely more on iptables/external firewalls than mailcow's configuration for persistent entries.
That makes sense to me -- the architecture of Mailcow lends itself more to being protected on the front-end by something like sunday-news than trying to do that heavy lifting on its own.
-
Starting to track IPs that hit my robots.txt, now that I know Brave says they have a search crawler without a UA that "respects robots.txt". They won't give netblocks, either. They're not welcome to my content, and I'm here to make it as difficult and expensive as possible to get and maintain.
It's sad that so many people remain steadfastly dedicated to enshittifying the 'net. We can't solve this with tech -- we have to solve it with community.