I have tested this and have it working using the EVENTCREATE command line to add test events to windows event logs. Remember that there are two different alert triggers, one for Windows OS event logs, and one for text file event logs. For testing specify a short interval (I use 30 seconds and test in a non production VM Ware environment). These monitoring alerts only seem to work with server manager agents, they are supposed to work with a system manager agent, and will not work with a desktop manager agent. But work they do...
We are currently working the same issue with LD support.
88 only accepts PLAIN auth and we are currently using NTLM, GSSAPI and Login. I'm hoping for a fix here pretty soon, so I feel your pain. Alerts workied great in 8.7 though.
I'll post if we get a resolution.
My understanding from Support is that Plain Text is all that is currently supported.
Correct, and we are not using that type of auth at the moment which is the root of our problem with not getting email alerts. Keeping my fingers crossed though for a different solution.
Rick is correct, The only authentication type supported by sendemail is PLAIN though we do it over TLS. A user can easily verify the types of
authentication supported using "telnet 25". Then enter the command "ehlo domain.com". The 250-AUTH line will report the supported authentication
types. (Use command "quit" to exit the session).
If that line does not show PLAIN as one of the supported auth mechanisms then sendmail in 8.8 will not succeed. Another thing to note: the from address needs to be a valid address scheme and in the case of many mail servers it must be a recognized address or the message will not be passed.
If these conditions are met then your email alert actions will succeed.
Bill to respond to your note that you hope it is fixed soon. While many of us would like the functionality added for other auth types, it is not a defect but is instead an enhancement request.
Message was edited by: Bd0g- spelling error
Sorry Brandon, I wasn't implying it was a defect in LD, I was implying to 'fix' our situation not the software. Red-tape seems to be the biggest deterrent to a sloution on our side, not the LD developers.
And, without completely understanding the underlying technology/reasoning behind the change in auth types for LD 88, it's harder for me to give a detailed reason to our brass as to why we need to change something on our side that worked well prior to the upgrade.