We have a C160 that currently monitors and delivers incoming email without a problem. We are now trying to setup Outgoing Email monitoring and are encountering the above problem when trying to send emails. We have setup the Mail Connector in our Exchange Server 2007 to send email to the Ironport and we can see messages accumulating in the Ironport queue.
But they don't go anywhere due to the above "error". We have configured the Ironport to use our internal DNS Server and have the correct Default Gateway set.
Can anyone please shed any light on why the messages are not going out.?
(We have disabled the Exchange Server Mail Connector to the Ironport for now so messages continue to be delivered direct out of Exch07 server to the internet but would really like to be able monitor outgoing emails)
there can be various reasons for this type of status and is in most cases network related, e.g. firewall rules not allowing traffic to certain destinations. DNS is another point and should be verified by running a few nslookups on the CLI to see if the appliance gets valid responses back. I also suggest using the SMTPPING tool on the command line which will help you in analyzing the issue. Here is a knowledge base article which should help: http://tinyurl.com/yl45po4 If SMTPPING results in 'connection refused' check in your network/firewall. Another CLI command which gives you more details about a destination host is 'hoststatus'. If you want to re-schedule delivery use the command 'delivernow'.
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...