You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm testing the tool and all looks good. Though, I'm wondering how this would work in a multi-use or fail-over method.
Normally, an organization might have two SMTP servers. To make sure that at least one is up, one could use HaProxy or have different providers. Now, applying this to Postal and multi IPs how would you go about this?
Should each Postal be a copy or is there an option to failover automatically? I could imagine using HaProxy and then use always the same Postal server unless it's down. In this scenario, the second Postal would be a copy of the first one.
In any case, your input would help. Thank you.
The text was updated successfully, but these errors were encountered:
If your database and RabbitMQ are highly available then you can have multiple copies of Postal however you like as long as they can access the same data and queue.
Regarding multiple SMTP servers, whether you have a proxy or not depends on your infrastructure and skill I guess. You could have completely different IPs as long as the DNS records pointed at all endpoints then there shouldn't be a problem.
Definitely worth mentioning in the docs somewhere.
Hi there,
I'm testing the tool and all looks good. Though, I'm wondering how this would work in a multi-use or fail-over method.
Normally, an organization might have two SMTP servers. To make sure that at least one is up, one could use HaProxy or have different providers. Now, applying this to Postal and multi IPs how would you go about this?
Should each Postal be a copy or is there an option to failover automatically? I could imagine using HaProxy and then use always the same Postal server unless it's down. In this scenario, the second Postal would be a copy of the first one.
In any case, your input would help. Thank you.
The text was updated successfully, but these errors were encountered: