We are using RTMC Pro on a machine that has a Microsoft Exchange server for it's e-mail capabilities. For some reason RTMC Pro will not generate an e-mail alarm that we have setup. Due to the fact it's an exchange server the server's address doesn't begin with smtp.xxx.xxx. Would this be why we can't generate an e-mail?
I don't believe RTMC prefixes "smtp" to what the user entered in the "SMTP Server" field. What version of RTMC Pro do you have? Secure email support (specifically TLS) wasn't added until 3.0. If the exchange server is using some other type of authentication besides TLS that could be the problem. GMail uses TLS so a GMail account is useful for testing.
We are using version 3.0.46.0. I was using a gmail account and it worked fine.I will have to check with our IT department as far as authentication protocols.
I had a heck of a time getting RTMCPro to cooperate with our exhange server, but in the end it had nothing to do with the exchange server. I had success with gmail as well since it uses port 465. It was McAfee blocking ports 25 and 587 which might be what you need to use for your exchange server. Check your anti-virus software first (for McAfee it was under Access Protection in a setting called 'Prevent mass mailing worms from sending mail'). If you're still having problems, let me know. I spent a lot of time troubleshooting this issue.
I can send a regular e-mail from that machine, so our IT department said if that works then port 25 and 587 is opened. Any other help would be appreciated.
You might be able to send a regular e-mail from that machine, but that's through outlook or some other .exe that your anti-virus software isn't blocking. Ports 25 and 587 are open, but McAfee or some other anti-virus software might be blocking the RTMC_Run-time.exe or RTMC_Development.exe. I don't know what anti-virus you're using, but McAfee only gives certain executables access to ports 25 and 587. You would have to specifically list the RTMC executables for the email not to get blocked.
It's sounds like you were able to email through GMail so I don't think this is a problem, however...
Take a look at Access Protection in McAfee. I happen to be running 8.5.0i so yours may be newer or older and organized a little differently, but the functionality is there. If Access Protection is enabled, and if under Anti-Virus Standard Protection the "Prevent mass mailing worms from sending emails" is enabled (blocked), then the RTMC Run-Time executable will have to be listed as one of the "Processes to exclude".
If your IT department is using an odd port for their outgoing email you can specify that port in RTMC (e.g. smtp.company.com:1234) in order to override the default ports that RTMC would normally try. What "outgoing" port is specified in your day-to-day email client (e.g. Outlook)?
Glen, I'm not the OP, but I can guarantee you that it was McAfee that was blocking RTMCpro in my case. Our default install of McAfee blocks on 25 and 587, but not 465 which is what GMail uses. So, even if it works with Gmail, it's possible that McAfee is still blocking the OP's attempts to connect to Exchange Server and why I suggested to the OP to check his anti-virus settings.
In order to get things working, we had to request a machine-specific policy exclusion for McAfee (we run 8.7i) and things have worked fine ever since.
* Last updated by: lespedeza on 9/30/2009 @ 10:52 AM *