Hello, Over the weekend our firewall was having LDAP failures. Is there anyway to have Exchange send alerts when SMTP is affected by the firewall?
Is this not possible?
Hi renegadenomad x I've moved this to the Server & Application Monitor forum where people can better assist with your inquiry.
That might help. Thank you!
Is this as simple as adding SMTP Monitor for the IIS component of the public facing CAS server?
In combination with a basic email template you could also use the trap tool to send and alert when the firewall blocks any know ports. That would have to be worked on to know what trap would indicate that but that is an option.
The monitor of the queue works, as I just tested it with a count of 2 messages. But, this will not give insight of someone trying to email our Exchange from the outside. In the IIS component, are there any options to alert when the smart host cannot be reached or a gateway timeout?
I would have to guess that if that is a WMI perfmon or if you could write a script for that you could use those type of component monitors in order to get that statistic.
Have you considered using the LDAP User Experience Monitor, as well as the Exchange Web Services User Experience Monitor, or IMAP4/POP3 User Experience Monitors?
It is not LDAP that is failing, the Barracuda alerts on LDAP failures as a result to whatever is going on there. If the Inbound Connections Current monitors the loss of the smart host I will have what I need. Is this what I am looking for?
The best thing for such a scenario would likely be the Exchange Web Services User Experience Monitor, or IMAP4/POP3 User Experience Monitors.
Looks like a winner, but I am curious if it actually tests an external connection since I do not have the ability to add an external email address in the settings.
Also, the test came through to my mailbox but I get this message in the SAM:
Error occured during retrieval of test email. Error message: When making a request as an account that does not have a mailbox, you must specify the mailbox primary SMTP address for any distinguished folder Ids.
The test email shows this:
This is a message used internally by SolarWinds Server & Application Monitor to test the send and receive ability of a specific EWS Mail Server. This message may appear because EWS gave up on the server (due to the probes timeout settings).
APM considered the transaction linked to this message a failure.
I am getting this message every poll cycle, so not sure what that is all about.
These components are flexible such that the can be configured to send the email via an external source (Gmail etc.) through to an internal email destination (Exchange, etc.) or vis versa. It's all how you configure the monitor.
Test emails should be sent to a dedicated monitoring account. The emails you're receiving are normal, but should be retrieved and deleted after each poll. If they remain in the test users account for longer than the polling interval then there's likely an issue retrieving the message. In most cases it's not specifying the correct credentials for that users account, that use does not have permission to use that method of mail retrieval, or there is a firewall or router access control list preventing Orion from accessing the mail server. At least those are the most common reasons.
