Affesol

updated

3 years ago

A

Affesol

1 Rookie

•

5 Posts

0

22486

July 22nd, 2019 09:00

RAC0225: Sending the test mail failed - iDRAC

PowerEdge R820 Firmware: 2.61.60.60 iDRAC Controller 7 Setting up email alerts and not working. Internet search shows there IS AN issue setting up email alerts. - Under destination email address I have email user@solutions.com and state is ticked/selected - SMTP (Tried with name and IP but no luck). I can ping it my name and IP both - Tried with and without authentication enabled but no glory! - In house hosted smtp server running IIS. This iDRAC server's IP is allowed to relay via this smtp/iis server - Static DNS Domain Name is set to solutions.com Anybody please assist? Thank you
  • Daniel My

    12 Elder

    •

    6204 Posts

    19531

    0

    Posted July 22nd, 2019 10:00

    Hello

    This article has instructions for configuring email alerts.

    https://www.dell.com/support/article/sln309388/

    If the test fails then check the logs of the mail server to see what occurred. The mail server log should have more information about why it is not working. If nothing is logged on the mail server then the iDRAC may be having issues communicating with the mail server.

    http://www.dell.com/idracmanuals/

    Thanks

  • JimDig

    2 Posts

    13662

    1

    Posted July 23rd, 2020 09:00

    Just to offer one more gotcha in setting this up...makes sure you click the State box next to the email recipient and click Apply BEFORE you try to test!
    If the recipient has not been saved, you will get that email failed message over and over no matter what SMTP settings you try.

     

  • Nav T340

    1 Message

    5733

    0

    Posted December 25th, 2021 18:00

    1. Check iDRAC DNS Settings - confirm Internal DNS
    2. Check Exchange SMTP IP
    3. Check Exchange Port - 25 by default
    4. In Exchange > Mail Flow > Receive Connectors > Frontend > Edit > Scoping > Add iDRAC IP
  • Janwww

    7 Posts

    1119

    0

    Posted June 14th, 2023 05:00

    In my case it was connection encryption in the SMTP server section. Setting to none worked for me.