Hi.
First i will explain the context of what i did, and what i wish to achieve.
We are currently assisting a client, who has LOTS of troubles to send bulk emails, this client have a bunch of IP addresses, and all of them blacklisted. To solve this we implemented a Relay server, anything that comes from certain internal servers, the relay server sends it using one of our public IP Adresses.
The problem starts when our relay server have problems, or the client thinks that it haves a problem. Sometimes they configure their app in a wrong way, sometimes its really its our fault, but we need more insight about this.
To solve this, we added a Pop3 user experience monitor and configured it to use the Relay Server as its SMTP server, this way we can check if the relay its working, and because our Orion is on client premises even in the same Network Segment we can say its fairly accurate. But we encountered that when something happens, our resolution time Skyrockets because the ball starts bouncing between the client and our Support.
This service is really important for our client, its an airline that sends a confirmation e-mail with the reservation data after the passenger pays... So you can imagine what happens if that mail doesn't go out.
To reduce the diagnostics time, and avoid wasting time digging in Logs (and no, we don't have LEM) it could be very helpful to have in the alerts any SMTP reply code, right now what i'm gettin is something like this.
¿Is there any way to have more insight and help to Pin Point where the problem could be? Any other approach to this problem is also very welcome