I'm hoping someone can help me understand the capabilities or limitations of Ironport. I work in an environment where another department owns and operates the mail relay operations, so I have no access to the device or support to advise or dispute what they are saying.
Situation: We have a closed application environment which uses a custom defined domain (foo.bar, host1.foo.bar, host2.foo.bar, exporter.foo.bar) We have a system that sends email out to the real world (exporter.foo.bar) and its outgoing relay is the ironport appliance. The problem is, when a remote mail site is down or bounces the email, the ironport does not know where to send the bounce message because it doesn't know how to send to exporter.foo.bar.
Problem: the admins for this ironport appliance report that it is impossible to configure it to send to exporter.foo.bar because "bar" isn't a "valid" domain (eg: .com, .net, .edu, etc...)
Can someone confirm if this is true or not? Is the Ironport so tightly integrated with LDAP, or AD, or some flavor of Mickysoft DNS that you can't simply add a mailertable type entry to send email destined for "foo.bar" to a particular IP address?
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...