Eric Rousse
2015-04-28 12:06:33 UTC
Hello all,
I've been searching about this and so far nothing that would fit my needs. But I'm sure that there is a way.
I have a couple of postfix servers + amavis. So with the MX records I can have a redundant setup with my postfix servers. But I've been recently asked to add amavis to the setup, in order to sign the emails with DKIM. That part is working fine.
Within the main.cf, I have my content_filter setup to point to my amavis instance, then the mail is re-injected into postfix. That works without issues.
Where I'm questionning my self, is in the case that amavis goes down. I'll have a monitoring solution for this, but what if the people takes to much time to resolve the issue mails will get stuck.
So I'm trying to look for a way to put a second amavis instance in case the first one goes down. Once the first one is up, mails will be start to go through that instance instead of the second one.
I can't use a dns address, it will just add a cheap load balacing to the solution.
Thanks,
I've been searching about this and so far nothing that would fit my needs. But I'm sure that there is a way.
I have a couple of postfix servers + amavis. So with the MX records I can have a redundant setup with my postfix servers. But I've been recently asked to add amavis to the setup, in order to sign the emails with DKIM. That part is working fine.
Within the main.cf, I have my content_filter setup to point to my amavis instance, then the mail is re-injected into postfix. That works without issues.
Where I'm questionning my self, is in the case that amavis goes down. I'll have a monitoring solution for this, but what if the people takes to much time to resolve the issue mails will get stuck.
So I'm trying to look for a way to put a second amavis instance in case the first one goes down. Once the first one is up, mails will be start to go through that instance instead of the second one.
I can't use a dns address, it will just add a cheap load balacing to the solution.
Thanks,