It would help if you explain "it does not work" further. It's a bad desciption of the situation and we cannot look directly at your installation.
suzune
joined 2 years ago
If users cannot do anything because all encryption keys are lost, then they need to know that and also how to avoid the situation in the future.
I think it's not a bug. It's simply no one online who can share a decryption key.
This is quite annoying. When will devs learn to tell people to resolve the problem instead of just showing a pointless error messages?
Not really. Postfix is very robust against attackers and knows to how to deal with bots by default. It makes sense to also configure SPF, DKIM and DMARC for your own safety.
If you want to stop the attackers from hammering, you can also add fail2ban.
If you want to avoid spam, you can attach a spamfilter to the delivery agent and let Sieve do the rest.
I've been running my postfix/dovecot combo using 4 mail domains for over 5 years without any problems. It's simply fantastic.
At the moment I'm trying out Ampache. It seems to have more features than Gonic.
Nothing special. Radicale is fine, too. As far as I see it also supports sharing of CardDAV among multiple users which Baikal does not.
One thing I needed after I migrated away from Nextcloud is the birthday calendar. There is a script for that on Baikal.
Baikal (CalDAV server), DAVx5 for sync, Tasks.org for Android UI, Thunderbird on PC.
Dynamic IPs are filtered out, even on my server. This is done by using scores provided by Spamhaus. The majority of connects from such IPs are botnets.
You can run a private server on your dynamic IP. It should not connect to public servers though.
I've got Unifi Network installed in a container on my home server. I have also an custom-built router, because it is much more powerful than any appliance and does not cost as much.
Many governments want to decrypt chats. You better learn how to selfhost.
Corrected. It's not very clear from the context.
So sshd is running. The first question is: is it running on the port you expect it to run? The main host can have sshd too and maybe you connect to the wrong port? Did you use a
~/.ssh/configfor your forgejo connection?