On 12/02/24 11:47, Alex via Postfix-users wrote:
My concern would be with multiple MX records for the same domain - is it possible it would come back to try again with another MX and be delayed yet again?
Unless you're referring to your own MX records these are not relevant. That said, many providers do use multiple different servers and IPs for MX connections and this can be an issue. This is the primary reason why after-220 tests in postscreen are rather controversial. There are some ways to help mitigate this issue but no golden bullet.
If you're referring to your own MX servers you can share the internal whitelist cache (see postscreen_cache_map).
The sqlgrey perl script has the ability to consult a database to see if enough time has elapsed as well as cluster servers to see if the client has attempted a connection to one of the other MX servers. I'm not sure I ever managed to set it up successfully, however.
Right, postscreen has similar functionality to greylisting, but since it has a different goal there are some features of postgrey that aren't present in postscreen.
Peter _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
