Reached out to support…there is a bug with certain versions of Orchestrator (2019.10.14 until 2019.10.16) that cause this error to show even if you have the email settings configured correctly. The easiest way I found to figure out your email settings is to log into the Orchestrator server and run this PowerShell script. If it works from your server, then you have all of the options set correctly.
$cred = Get-Credential -UserName “test@com” -Message “Enter password for:”
$EmailFrom = “test@gmail.com” #this does not matter
$EmailTo = “test@com” #this must be a valid email address
$Subject = “test subject”
$Body = “Test message body”
$SMTPServer = “gmail.com” #this is important; set it correctly and play with it
$smtpPort = 25 #play with the port, maybe it’s not 25 (the most common port); for gmail.com, try with 587, 465, 25
try the following command with and without UseSsl;
Send-MailMessage -SmtpServer $SMTPServer -Port $smtpPort -From $EmailFrom -To $EmailTo -Subject $Subject -Body $Body -Credential $cred -UseSsl
If you are using Office365 for your mail like I am, this is what these variables were:
$SMTPServer = “smtp.office365.com”
$smtpPort = 587