24.09.2010 04:39, Wietse Venema wrote: > 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.
As far as I see, this does not work. Imagine a temporary network glitch on the client side, so that it weren't able to connect to the primary, but at the time it attempting connecting to secondary the problem went away. Maybe this is a good case to ignore, as it does not happen often... /mjt
