The problem was not that the Mail Server wouldn't send e-mail, but that the server the Orion is running on was not trying to contact the Mail Server.
This was initially determined by running Wireshark, a packet analyzer. It showed Orion's normal polling of the status of the mail server, but no TCP connection to send mail.
Here's the error Orion generated when testing the Alert:
Apr-07 14:22:35.11 : 6664 : Error Sending E-Mail via SMTP Server (MAIL SERVER).
Apr-07 14:22:35.11 : 6664 : To: (my e-mail)
Apr-07 14:22:35.11 : 6664 : CC:
Apr-07 14:22:35.11 : 6664 : BCC:
Apr-07 14:22:35.11 : 6664 : Trigger Subject Pre-Parse:Alert: ${NodeName} is ${Status} from ORIONSERVER
Apr-07 14:22:35.11 : 6664 : Trigger Subject Post-Parse:Alert: THENODE is Down from ORIONSERVER
Apr-07 14:22:35.11 : 6664 : Trigger Message Pre-Parse:Alert: ${NodeName} is ${Status}.
New Basic Alert from ORIONSERVER
Apr-07 14:22:35.11 : 6664 : Trigger Message Post-Parse:Alert: THENODE is Down.
New Basic Alert from ORIONSERVER
Apr-07 14:22:35.11 : 6664 : The message could not be sent to the SMTP server. The transport error code was 0x800ccc15. The server response was not available
Error Number--2147220975
Apr-07 14:22:35.13 : 6664 : AlertID=10 NetworkObjectID = N:248
I could have saved time by looking at the Windows Event Log earlier...
Windows Logs | Application
information McLogEvent Blocked by port blocking rule (AntiVirus Standard Protection: Prevent mass mailing worms from sending mail
To fix it:
Start | McAfee | VirusScan Console | Access Protection | Properties
Select "Prevent mass mailing worms from sending mail" & EDIT
Processes to exclude - add OrionAlertEngine.exe
Note it re-alphabetizes the list after you OK the addition.
Tah-dah!
