Email server x.x.x.x not in service since ping test failed

[Dogbreath]

7.2 firmware
Does MCD really stop trying to send email if the mail server isn't pingable? That's what this message suggests:

Code: [Select]

Source EmailAlarm
Description Email server x.x.x.x not in service since ping test failed with errno(196711) S_taskLib_TASK_HOOK_NOT_FOUND). Please try again with a different one.
Module Main
File Name and Line Number Alarm_email.cpp;253
I can't find a way to force MCD to try to send an email without leaving someone a voicemail, however, so I haven't been able to test this.

[petr.necas]

We had the same issue, finally we installed proxy SMTP server on a local network server that was pingable from the MCD.

I'm also missing the test Email The test button, but it is possible to generate an alarm that sends an e-mail, look here:

http://mitelforums.com/forum/index.php?topic=4786.msg20724#msg20724

[Dogbreath]

When you say "issue", is it just the log message, or was it actually not sending email?

I remember now, I did actually get it to send a voicemail but that happened before it started logging messages saying the mail relay wasn't pingable.

[petr.necas]

If I remember well, it was not sending e-mails.

[acejavelin]

I have run into this on occasion with a remote email server that will not respond to a ping, the solution I have used many times is to install MSL with no blades or licensing and just use it as email relay server... Setup the email settings in MSL then point the 3300 to email to the MSL server. Not very "clean" since it requires another server, unless you can virtualize it, but I have an old version of MSL 7 or 8 that works with very low hardware requirements (last implementation was on an old Intel Core 2 Duo machine with an 80GB hard drive).