Dell iDRAC and HPE iLO alert email with Microsoft 365

Out-of-band management controllers are the devices you most want to hear from and the least likely ever to learn OAuth2. iDRAC, iLO, Lenovo XClarity, Supermicro IPMI and Cisco CIMC all send plain SMTP alerts. Pointing them at a relay on the LAN puts them back in touch with your inbox.

What the device needs

SMTP server: the SMTP-365 appliance's IP address, on your LAN.
Port: 2525 (or 25 if the device cannot change its port).
Authentication: none. Encryption: none. The relay is plain SMTP on the LAN and does the secure part to Microsoft itself.
Sender address: a real mailbox in your tenant (a shared "alerts" mailbox is free). The appliance can override it so every alert comes from the same address.
The device's address or subnet must be on the appliance's devices list (Settings → Devices).

Where the settings are

Dell iDRAC 9

Configuration → System Settings → SMTP (E-mail) Configuration: SMTP Server Address = the SMTP-365 appliance's IP address, Port = 2525, Authentication = Disabled, Connection Encryption = None, Sender e-mail address set. Add destinations under Alert Configuration → E-mail and press Send to test.

Dell iDRAC 8

Overview → Server → Alerts → SNMP and Email Settings: SMTP Server Address, port, no authentication; email addresses with the Test button.

HPE iLO 5 / iLO 6

Management → Mail (or Administration → Management → AlertMail): enable AlertMail, Email address = alerts mailbox, Sender domain = your domain, SMTP Server = the appliance, port 2525, no secure connection. Send Test AlertMail.

HPE iLO 4

Administration → Management → AlertMail: the same fields; iLO 4 firmware only speaks TLS 1.0/1.1 to Microsoft, another reason to relay.

Lenovo XClarity Controller

BMC Configuration → Network → SMTP then Events → Recipients.

Supermicro BMC / IPMI

Configuration → SMTP: server, port, no authentication, no SSL; Alerts for destinations.

Hardware alerts belong with the people who fix hardware: send them to a shared mailbox or a distribution group. Many controllers also require a sender address before they will send; use the scanner or alerts mailbox.

If the test message does not arrive

What you see	Likely cause	Fix
Connection failed / cannot connect to server	Wrong relay address or port, or the device's subnet is not in the relay's allowed sources	Check the address and port; on the appliance, Settings → Devices, add the device's subnet
554 5.7.1 Relaying denied (or the connection closes at once)	The device's IP is not among the appliance's devices	Add the address or subnet under Settings → Devices on the appliance
Authentication or certificate error on the device	Authentication or TLS is still switched on in the device	Set authentication to none/off and SSL/TLS to off; the relay is plain SMTP on the LAN
Device says sent, nothing arrives	Delivery to Microsoft 365 failed and the job is held or failed	Open the appliance's Status page: held and failed jobs show the reason and can be re-queued
Arrives, but from the wrong address	The device's own From address is being used	Turn on the sender override on the appliance so every message is sent from the scanner mailbox

One appliance for all of them

The same SMTP-365 appliance that fixes the printers takes the UPS, the servers' management cards, the NAS and the phone system, on one licence with no per-device fees. Each device gets the same three settings and the appliance's Status page shows every message it handled. Background: what Microsoft changed.

Fix it once, for every device. SMTP-365 is a small appliance on your network that accepts plain SMTP from printers, UPSs, servers, NAS and phone systems and delivers it into your own Microsoft 365 tenant with modern authentication. One licence covers every device on the site. Download the free 30-day trial See pricing

Updated 2026-10-10. Menu names and screens vary between models and firmware versions; if yours differs, look for the same fields under the device's email, SMTP or notification settings. Corrections welcome at helpdesk@smtp-365.com.