Just don’t run broken software. The attackers will not be able to exploit you then. If they have zero day exploits, the WAF will most of the time not save you since they are often pretty easy to circumvent. WAFs are only effective against old and shitty exploits that should be patched anyways since ages.

Attack surface is made of the amount of code that is running when an attacker speaks to your machine. Imagine a freshly installed GNU/Linux distro with no services. The attack surface is minimal. All packages sent to your machine will only ever be touched by relatively limited parts of the linux TCP/IP stack and NIC driver. If you now run a web server, the package coes through the NIC driver, TCP/IP stack and web server. The surface is increased. Each of these parts of your machine’s code could have bugs. The more code your attacker’s packet runs through, the more opportunity to make your machine do things you don’t like.

If you want your machine to do what you like but not what random attackers like, it is therefore mandatory to have the least amount of attack surface, not adding code in contact with your attacker like a WAF or “antivirus”. Both these kind of softwares will inspect the packages coming in an take decisions (potentially bad ones) based on the content.

WAFs will mostly not help you since on a well configured and patched system, little known bugs are exposed. They might help you occasionally but usually patching the system is more effective. Of you want this to happen automatically, it’s entirely possible. Most os’s allow automatic unattended upgrades.

Wafs don’t make you safer but create unnecessary attack surface. Just keep your machine and services up to date.

They rock.I’m sometimes afraid they will be bought or change terms.

I beg to disagree about the disadvantages. An important one is that you cannot easily update shared libraries globally. This is a problem with things like libssl or similar. Another disadvantage is the added complexity both wrt. to operation but also in general the amount of code running. It can also be problematic that many people just run containers without doing any auditing. In general containers are pretty opaque compared to os packaged software which is usually compiled individually for the os.

This being said, systemd offers a lot of isolation features that allows similar isolation to containers but without having to deal with docker.

Not a big fan of Bezos though.

I ran an XMPP network based on prosody and used snikket on android. Can recommend!

Are you building a C/C++ project that should run on BSD, Gnu/Linux and other platforms? Then maybe use autotools. All distro tooling will easily be able to handle it.

Are you just building some small project that will never make it into a distro, maybe just use something simpler. Or even just a plain makefile.

https://sqlitebrowser.org/ is great or aSQLiteManager for android

Things are suspicious but you still spread gossip and maybe lies.

Nobody knows who responded here. Don’t spread rumors.

That’s actually a good point. Will need to think about server location and GDPR compliance.

Have a look at purelymail mentioned by others. It’s almost exactly what I’m looking for.

Exactly what I’m looking for. Thanks a lot!

Pretty nice but way more expensive then simplymail

Amazing! Now this is something I haven’t heard of. I think we might have a winner here! Best thing, I could use it for transactional mail on all my websites for 10€/yr. Including as many inboxes as needed. Nice!

This is something you used to be able to do for free, no problem. It’s only a few of the big mail accepting companies being extra shitty about accepting mail making this tough. Looking at you Microsoft. So a few hundred mails per month is ridiculous both on storage, bandwidth and CPU consumption.

I specifically want to not deal with deliverability beyond the content and volume of my mails.

Yeah, sorry it’s not a precise term. I mean a non asshole company.

Thanks but that’s not what I’m looking for. I need to send mails only.