>almost half a year after the above message introducing postscreen >and the idea of using a low-priority MX on the same host to raise >the entry barrier for the postscreen whitelist, I would like to ping >back to the thread with the following question:
>Has anyone found out how to make this work in combination with >a physically-separate secondary MX? We do the same with physically separate backup mx, for mostly the same reasons as you. While I'd love to see that capability, I don't believe postscreen has it at this time. The packages I've seen that do something like this, for example milter-greylist, actually have to communicate between machines which postscreen is not doing. When we did not use a backup mx, it was amazing how many larger mail systems gave up quickly on sending us mail and bounced it back to their users, even though the downtime was fairly brief. Steve
