MX fallback solution

[ephigenie]

The easiest solution is the one i mentioned.
Nowadays a secondary mX has to know the local-parts of domains to accept only mail for valid recipients.

Of course we can think of a way to manage it in a highend solution - with shared storage, maybe a lvs director in front or some Big5 Iron to make loadbalancing between 2 or even more frontend MX's.

But for mail volumes < 5000 mails/hour there's no need to setup extra loadbalancing.
The secondary MX approach is the best thing for that.

If the primary MX is down - the secondary is automatically choosed - and the secondary is regularly testing if the primary is up - and when - all qeued mail is delivered.
This is a simple but efficient fallback solution - no mail is lost.
To acomplish redundant mail-servers we've to play with a true fallback - solution.
If anyone is interested in that and needs such a thing for its business - i'd be happy to help to achieve that but this goes far beyond that for what vhcs-omega is thought for atm.