Il 22/06/2011 16:30, Hannes Erven ha scritto:
..[cut]..
What do you think? Is there already someone using a setup like this
(with which policyd implementation)?
The simpliest idea.. :-)
Setup your backup MX server as a forwarder to the primary (or etrn, or
.. as you like).
Create on this host a local rules on iptables (or equivalent on other
platforms) by which you block incoming traffic on port 25.
Create a simple 'efficient mechanism' to determine if primary host is
on-line:
- if you are connection scared ..maybe a simple ping is ok
- if you are service/server/software scared ..maybe an EXPECT script is
better
- ..or simply catch che exit status on a utility which send a simple
status-test mail (e.g. "sendEmail -s <pri_mx> ..." )
Every 'X' minutes you cron the script: if the script detects the primary
service is down, it loads a new rule in iptables which allow incoming
traffic on port 25 .. in inverse situation ..blablabla (obvious) :-)
Too simple / home-made ? :-)))
Amedeo Rinaldo
--------------
Una volta eliminato l'impossibile, quello che resta, per improbabile che
sia, deve essere la verità (Sherlock Holmes)
