New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add email router #2
Comments
If sensible, I guess we prefer to use the mailu postfix image, because that's what paroga already uses elsewhere (and we'd like to keep it aligned). Seems like a good base image too. We just need to strip out parts we don't use: we only use forwarding outgoing mails to the upstream smtp server (though being able to deliver like a regular mta would be nice to keep), and forwarding incoming mails to the appropriate service. So no local accounts or storing mail. |
This is working now. |
When |
I think the initial idea was to let postfix decide where to route incoming reply mail based on the domain. |
Yes. In some cases one would want to share the domain between several apps (and/or use regular email addresses). |
I dont' disagree with you. As as side note: It's already possible to route incoming mails for sharedlists and foodsoft using the same mail domain. With postfix you have to setup a transport map like this (assuming
Based on how sharedlists and foodsoft build the mail address. |
The second regex is a little generic, but would already work. I'd be for using that for now, thanks! |
Replies by email are working now. |
With different instances receiving email (Foodsoft for message replies, different instances, plus sharedlists for article updates), there is need for a router to direct incoming email to the correct application. This can be done by adding a Postfix instance. Can also do outbound email. See e.g. docker-postfix for an example. It is important that wildcards matching addresses like
foodsoft-1.a918cd@foodcoops.net
can also be routed.The text was updated successfully, but these errors were encountered: