550 5.7.1 Relaying denied / Message rejected as spam / Unauthenticated email not accepted
The receiving (or your outgoing) mail server refused the message — relaying isn’t allowed, the sender isn’t authenticated, or it was classified as spam/policy violation.
Seen on:
SMTP
Meaning
5.7.1 is a generic “not authorised” code. On your own SMTP server it often means you tried to send without authenticating (relay denied). From external servers it means a policy/spam rejection — the text after the code explains which.
Common causes
- Sending through SMTP without authentication (relay denied)
- Sender domain/IP on a blocklist
- Content flagged as spam
- Recipient’s policy (blocked sender, internal-only group)
⚡ Quick fix
- Authenticate SMTP (port 587 + username/password)
- Check IP/domain on blocklists (MXToolbox)
- Read the full bounce text for the policy reason
Detailed fix by platform
Shell
swaks --to user@example.com --server smtp.example.com:587 --auth LOGIN --auth-user me@example.com --tls
How to diagnose
- Bounce — Full rejection text
- Auth — SMTP authentication used?
- Reputation — Blocklisted?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 550 5.1.1 550 5.1.1 The email account that you tried to reach does not exist (User unknown)
- 550 5.7.26 550 5.7.26 This mail has been blocked because the sender is unauthenticated (SPF/DKIM/DMARC)
- MessageRejected SES MessageRejected: Email address is not verified. The following identities failed the check in region
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026