SMTP error 540: What it means and how to fix it
SMTP error 540 overview:
- The 540 error is a permanent (5xx) rejection, so retries usually won’t help.
- It points to mailbox status or blocking, not a nonexistent address.
- SPF, DKIM, and DMARC help reduce policy-based blocking.
SMTP error 540 means the recipient server refused the message because the account is inactive/deactivated, suspended, or blocking your sending domain/IP address. Delivery will only resume once the recipient account is restored or the block is cleared.
If the 540 error is tied to security or policy controls, improving your email authentication is one of the most effective sender-side steps. Properly configured SPF, DKIM, and DMARC records reduce the risk of policy-based rejections and help mailbox providers verify your messages.
Sendmarc gives enterprises ongoing visibility and control over SPF, DKIM, and DMARC, so legitimate email is consistently trusted.
What SMTP error 540 means
A 540 error means the recipient server refused the message because the mailbox is inactive or suspended, or because the system is blocking your sending domain/IP. It typically points to a recipient account state or a policy/security rule on the receiving side.
Because it’s a permanent (5xx) error, your server usually won’t retry automatically. Sending will only succeed once the account is restored, or once the recipient system stops rejecting your domain/IP – for example, after allowlisting or once authentication and reputation issues have been addressed.
Common causes of SMTP error 540
- Inactive/deactivated: The recipient server is rejecting messages because it isn’t active.
- Suspended: The recipient server can’t accept email while a suspension is in place.
- Blocked sender: The recipient system is rejecting your messages due to security or policy rules.
Provider-specific 540 error
Rambler
| Error message | Meaning |
|---|---|
| 540 5.7.1 – recipient address rejected: Inactive | The account has been deactivated |
| 540 5.7.1 – recipient address rejected: Blocked | The sender has been blocked |
How to fix SMTP error 540
Because 540 is a permanent error, retries usually won’t make a difference. Next steps depend on the cause: Either the recipient needs to restore their account, or you need to address why your domain/IP is being blocked.
1. If the recipient account is inactive or deactivated:
- Ask the recipient (or their IT team) to restore the mailbox.
- Once they confirm it’s active, resend your message.
2. If the recipient account is suspended:
- Ask the recipient to contact their provider or IT admin to lift the suspension.
- If it’s urgent, request another contact method while the suspension is being resolved.
3. If you’re being blocked:
- Check authentication first: Confirm SPF, DKIM, and DMARC records are correctly configured.
- Look for reputation or blocklist issues: Review your sending IP/domain reputation and check whether you’re listed on common blocklists. If you are, address the underlying cause and follow the delisting steps.
- Coordinate with the recipient: if your setup looks clean, ask the recipient to allowlist your domain/IP, or to share the specific reason the policy or security controls are blocking you.
Email authentication for improved delivery
Having strong email authentication improves trust with mailbox providers and can reduce policy-driven blocks that sometimes show up as 540 errors. To strengthen delivery, be sure to implement and maintain:
SPF
SPF lists the servers allowed to send email on behalf of your domain.
Example SPF record:
| Host | Type | Value |
|---|---|---|
@ | TXT | v=spf1 ip4:192.168.0.1 include:mail.example.com -all |
DKIM
DKIM adds a cryptographic signature to messages, so receivers can verify that emails weren’t altered during transit.
Example DKIM record:
| Host | Type | Value |
|---|---|---|
selector._domainkey.yourdomain.com | TXT | v=DKIM1; k=rsa; p=[public key] |
DMARC
DMARC tells receiving servers what to do when SPF and/or DKIM fail and provides reporting.
Example DMARC record:
| Host | Type | Value |
|---|---|---|
_dmarc.yourdomain.com | TXT | v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com; fo=1; |
How Sendmarc helps
SMTP 540 can be caused by recipient account status or policy/security controls. You can’t restore a deactivated or suspended mailbox from your side – but Sendmarc helps you reduce policy-based blocks, protect your domain, and maintain reliable delivery.
- Reduce fraud and protect your brand: Enforce DMARC to reduce spoofing and impersonation. Detect lookalike domains and suspicious activity early with dedicated monitoring.
- Improve delivery for critical email: Maintain consistent DMARC alignment across all sending tools, so communications are more likely to be accepted.
- Increase visibility and control: Gain a unified view of all senders and quickly identify unauthorized or misconfigured sources.
- Support compliance and reporting: Provide credible reporting and audit trails for risk teams, and standardize policies across departments and regions.
- Lower the workload on IT and security: Use continuous monitoring and clear remediation guidance to reduce manual investigation.
SMTP error 540 FAQs
Is SMTP error 540 a permanent error?
Yes – SMTP error 540 is a permanent (5xx) SMTP error, which means the receiving server rejected the message, and delivery will continue to fail until the underlying issue is resolved.
Does SMTP error 540 mean the email address doesn’t exist?
No – SMTP error 540 usually isn’t about a nonexistent address. SMTP error 540 typically means the address is valid, but the recipient server is refusing delivery due to mailbox status (inactive/deactivated or suspended) or because the sender is being blocked.
What should I ask the recipient to do to fix SMTP error 540?
To fix SMTP error 540, ask the recipient to confirm whether their mailbox is inactive/deactivated or suspended. If the bounce points to blocking, ask them to allowlist your domain/IP or share the specific reason you’re being blocked.