another postscreen possibility

One possibility is to have postscreen listen on multiple IP addresses
with different MX preferences, and to require that clients don't
connect to the secondary port before the primary.

The problem I see with this is that a site with multiple MX hosts
would need to share the postscreen database. I'm concerned that a
networked SQL database would introduce unacceptable latencies and
that it the postscreen database would become a single point of
failure for multuple MX hosts.

        Wietse

• This message: [ Message body ]
• Next message: Rob Foehl: "Re: another postscreen possibility"
• Previous message: Wietse Venema: "Re: postscreen update: log helo/sender/recipient"
• Next in thread: Rob Foehl: "Re: another postscreen possibility"
• Reply: Rob Foehl: "Re: another postscreen possibility"
• Reply: Leandro Santi: "Re: another postscreen possibility"
• Reply: Michael Tokarev: "Re: another postscreen possibility"

• Contemporary messages sorted: [ By Date ] [ By Thread ] [ By Subject ] [ By Author ]