-
Notifications
You must be signed in to change notification settings - Fork 10
Make sending email work #12
Comments
I'm not familar with docker right now but I like to setup postfix. So I self assign me to this task. |
Is this getting anywhere? |
We can use Sense.Lab's SMTP, for details see mailing list post. |
It would still be nice to have postfix in between. Is someone working on that, or shall we close the issue and leave it for #2? |
Let's leave adding postfix for #2 then. |
We're having too many TLS connections- http://foodsoft.51229.x6.nabble.com/email-problems-tp1674.html |
Hi,
Am Fri, 02 Mar 2018 02:22:59 -0800
schrieb wvengen <notifications@github.com>:
We're having too many TLS connections -
http://foodsoft.51229.x6.nabble.com/email-problems-tp1674.html
The server's IP address (46.38.240.91) is now exlcuded from Postfix
rate limiting. I suppose that this solves this error.
steffen
|
Thanks, that's great! 👍 |
I discoverd another limit of the postfix server ( I exluded the foodsoft server's IP address from this limit. |
Foodsoft sends mail messages, so we need a way to send them properly.
Add an email server docker instance that acts as a relay for Foodsoft. This email server can then either forward it to an upstream server, or just deliver it by itself (in which case we'll need to setup some anti-spam measures like SPF and such).
It would be useful to keep #2 in mind, where we'll also need to route incoming mail (see also links there).
Multiple domains as well as wildcard email addresses (but not catch-all, I guess) will be necessary.
The text was updated successfully, but these errors were encountered: