We're in the process of converting over our physical 'Ironport' appliances to the new virtual ESA builds.
On the old Ironports we have two units - they are not clustered and from what I can tell they enabled the spam quarantine on the secondary and on the primary they set the IP of the secondary as the external spam quarantine address, port 25. This seems to work fine, users only get 1 spam notification for anything either Ironport quarantines.
On the new virtual ESAs we've deployed, we've attempted to duplicate this config and it really doesn't seem to work. We get the following message when the one ESA tries to send quarantined messages to the second ESA -
ISQ: Could not connect to off-box quarantine at xxx.xxx.xxx.xxx:25
The goal is to consolidate the spam quarantine between these two units so users only receive 1 spam notification, which is how the old units were configured. Seems like maybe in the new code this isn't supported without an SMA?
