Suzune

https://matrix.org/docs/matrix-concepts/end-to-end-encryption/

Key sharing When an event cannot be decrypted due to missing keys, a client may want to request them from other clients which may have them.

If you have forgejo or gitea ssh running on port 222, you need to specify it somewhere. Or else git could connect to port 22, which is default for ssh.

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/config for your forgejo connection?

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.

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.