Outlook SMTP Non-Compliant Sender Address
-
Outlook, using a standard SMTP/IMAP account, gets this error whenever sending email out, no matter to where it is sent.
Your message did not reach some or all of the intended recipients. Subject: Test Sent: 8/1/2019 11:18 AM The following recipient(s) cannot be reached: '[email protected]' on 8/1/2019 11:18 AM 550 5.7.1 Non-Compliant sender address. Code : -1We know that the emails are good. I've not seen this error before. Anyone know what issue it might be? We suspect the SMTP service host of being broken, but they refuse to test so we have to prove that things are their fault to get anywhere.
-
No hiding the vendor here, the SMTP server is smtp.sasktel.net
This is also handy to document for the future.
-
@scottalanmiller said in Outlook SMTP Non-Compliant Sender Address:
And yes, doing an email test from Outlook results in the same error code. So definitely has nothing to do with what we have typed in.
-
550: It usually defines a non-existent email address on the remote side.
Though it can be returned also by the recipient’s firewall (or when the incoming server is down), the great majority of errors 550 simply tell that the recipient email address doesn’t exist. You should contact the recipient otherwise and get the right address.
-
Isolated to one account?
-
Hmm, I just got the same when testing using telnet
550 5.7.1 Non-Compliant sender address. Code : -4 -
I ran Evolution in debug mode, the email sent, then I tried to run the same SMTP commands as in the debug log in telnet but got the error again
-
Evolution didn't actually include the email data in the log, so that's where the SMTP commands I ran could have differed
-
@wrx7m said in Outlook SMTP Non-Compliant Sender Address:
Isolated to one account?
Yes but... only because they only have one account
-
@flaxking said in Outlook SMTP Non-Compliant Sender Address:
Hmm, I just got the same when testing using telnet
550 5.7.1 Non-Compliant sender address. Code : -4Oh, good info! Thanks.
