The server rejected one or more recipient addresses. solarwinds alert email

Greetings to the community.A change was made to the SMTP server and the modification was made to the email sending of the alerts, but now when I do the test I get this error and 
it does not send the email. Any recommendation?? Do I have to run the configuration wizard again?

Find more posts tagged with

npm

Alerts

Accepted answers

All comments

superfly

Are you sending to an address for an email group? If so, maybe the email group has restrictions on who can email to it.

You shouldn't have to run config wizard to fix your issue. You have to understand what changes were made and configure Solarwinds accordingly.

tporritt

Your SMTP server might need to have the sender (main poller) whitelisted.

mjonathan

Greetings tporrittYes, it's already on the whitelisted and nothing, in fact I ran the configuration wizard and it didn't 
fix it. Any other suggestions?

mjonathan

Greetings SuperflyThe email is sent to a single account, not to a group. On the other hand, I have already run 
the configuration wizard again and nothing, it still gives me an error. Any other suggestions?

tporritt

I would double check the authentication that the SMTP server requires. It sounds like either the message is getting rejected because of an authentication issue or spam classification. Maybe your email admins have some logs they can review if either of those do not fix the issue. Good luck!

jholmes

This is a error from the SMTP server not SolarWinds configuration wizard won't do anything work with your Email team to verify if there was a change in the user account or its password etc.

donrobert5

support.solarwinds.com/.../Test-SMTP-server-connectivity-via-telnet

anmolkumar7

Can you confirm if previously SMTP was configured using authentication or without ? Also, Is the SMTP test failing after these recent changes ?

This looks like authentication mechanism change due to which SMTP is denying relay of email from your solarwinds.

mjonathan

My case is now resolved, we saw that there was one more block on the Exchange relay server. Thank you all very much for your contributions and collaboration.