use a durable SMTP server #31
Labels
No labels
bug
cleanup
duplicate
enhancement
forgefriends
help wanted
invalid
label workflow
need more info
question
refactor
static-site
sync
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/k8s-cluster#31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
all Forgejo instances rely on a temporary solution for sending mail. Figure out a more durable one and install it.
@viceice do you have a suggestion? This was discussed briefly in the chat a few months ago and I don't quite remember if you did.
Ideally that would be an SMTP server that can be deployed in the k8s cluster itself. From past experience it is low maintenance when it only sends mail.
https://www.tauceti.blog/posts/run-postfix-in-kubernetes/
It is a very long read. I'll try to find something simpler.
we need to be careful with sending ip's, dns and other configurations, so we don't get blocked by other mail servers.
I don't run any mailserver inside kubernetes yet.
I'm leaning towards not implementing this but asking for help to Codeberg (or another friendly organization) to provide an outgoing SMTP server that they self-host.
@fnetx would it be possible to use the current Codeberg SMTP server for that?
From today's discussion with @fnetx, Codeberg will help ❤️
Quite happy about that 😇