SMTP error 552: What it means and how to fix it
SMTP error 552 overview:
- SMTP error 552 is a permanent rejection – delivery won’t succeed unless something changes.
- It is usually triggered by size limits, mailbox quota, filtering, or an invalid domain/address.
- Reduce size, ask the recipient to free up space, remove risky content, or fix the address – then resend.
An SMTP 552 error means the receiving email server refused to accept your message. This is usually due to size or storage limits, content/security filtering, or an address issue. Since this is a permanent rejection, the receiving server won’t accept the message until the underlying issue is resolved.
If you’re seeing other 5xx rejections (like policy or authentication bounces), Sendmarc can help you implement and maintain SPF, DKIM, and DMARC to improve reputation and delivery.
What SMTP error 552 means
A 552 bounce means the receiving server refused to accept the message. This usually happens when the email exceeds size limits, the mailbox is out of space, the message is blocked by filtering, or the recipient’s address can’t be found.
To resolve it, shrink the email, remove/replace risky content, verify the address, or ask the recipient to clear space.
Common causes of SMTP error 552
- Message too large: The email (often an attachment) exceeds the recipient provider’s size limit.
- Mailbox over quota: The recipient’s mailbox has run out of space and can’t accept new messages.
- Malware detected: The receiving system detected a virus or malicious payload.
- Spam or security filtering: The content, links, or attachments triggered a spam/security rule.
- Invalid recipient address: The email address is incorrect or doesn’t exist.
Provider-specific 552 errors
Google (Gmail, Google Workspace)
| Error message | Meaning |
|---|---|
| 552 5.2.2 – The email account that you tried to reach is over quota | Recipient mailbox has exceeded its quota |
| 552-5.2.3 – Your message exceeded Google’s message size limits | Message size is above Google’s allowed limit |
| 550 5.7.0 – Our system detected an illegal attachment on your message | Disallowed attachment detected |
Yahoo (Yahoo, AOL, Verizon)
| Error message | Meaning |
|---|---|
| 552 1 – Requested mail action aborted, mailbox not found | Mailbox not found (address is invalid) |
iCloud (icloud.com, me.com, mac.com)
| Error message | Meaning |
|---|---|
| 552 5.2.2 – user overquota | Recipient storage quota has been reached |
GoDaddy
| Error message | Meaning |
|---|---|
| 552 5.2.3 – Message exceeds maximum permitted | Email exceeds the maximum permitted size |
| 552 – Virus infected message rejected | Virus-infected content triggered rejection |
| 552 – Message rejected as spam by Content Filtering | Content filtering classified the message as spam |
Yandex
| Error message | Meaning |
|---|---|
| 552 5.2.2 – Mailbox size limit exceeded | Recipient mailbox is full |
Zoho
| Error message | Meaning |
|---|---|
| 552 5.1.1 – <example@zoho.com> Mailbox delivery failure policy error | Delivery failed due to storage constraints |
| 552 5.7.1 – virus [name] detected by Zoho Mail | Malware detected in the message |
How to fix SMTP error 552
For message size issues
Step 1: Check provider size limits
Common limits:
- Gmail: 25MB
- Outlook: 35MB
- Yahoo: 25MB
Step 2: Reduce message size
- Compress files before sending
- Use cloud storage links instead of attachments
- Convert images to smaller formats
Step 3: Use alternative delivery methods
Share files via Google Drive, OneDrive, or Dropbox.
For mailbox quota issues
Step 1: Contact the recipient
- Let them know their mailbox is full
- Ask them to delete old emails or empty the trash
- Suggest they request more storage from their provider
Step 2: Wait and retry
- The recipient may clear space
- Retry after some time has passed
- Consider alternative contact methods
Step 3: Remove from mailing lists (if chronic)
If a recipient repeatedly has a full mailbox:
- Consider removing them from your mailing list
- They can resubscribe when space is available
For virus/attachment/spam issues
Step 1: Identify what’s triggering the block
- Malware or suspicious files
- Risky attachments
- Spam-like content
Step 2: Adjust the message
- Scan the file and your device for viruses
- Remove the attachment or convert it to a safer format
- Rewrite the subject/body to remove high-risk phrases
Step 3: Retry or escalate
- Resend after changes
- If it still fails, ask the recipient about their policy
For invalid address issues
Step 1: Confirm it’s an address error
Check the bounce text for phrases like “mailbox not found.”
Step 2: Fix typos and formatting
- Correct any misspellings
- Remove spaces/invalid characters
Step 3: Verify the mailbox exists
Check with the recipient (or their IT/admin) to confirm the mailbox is still active.
Email authentication for better delivery
While authentication doesn’t fix 552 errors, it helps with policy-based filtering.
SPF
SPF specifies which sources are 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 emails to verify message authenticity.
Example DKIM record:
| Host | Type | Value |
|---|---|---|
selector._domainkey.yourdomain.com | TXT | v=DKIM1; k=rsa; p=[public key] |
DMARC
DMARC tells receiving servers how to handle unauthenticated emails 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; |
Ensure reliable email delivery with Sendmarc
While 552 errors are often about message size, mailbox storage, suspicious content, or invalid addresses, proper email authentication helps reduce blocks triggered by policy filters. Sendmarc helps you:- Configure and enforce SPF, DKIM, and DMARC across all domains and senders
- Improve inbox acceptance for critical communications (billing, notifications, marketing)
- Detect compromised credentials, spoofing attempts, and lookalike domains
- Provide credible reporting for stakeholders and support evolving compliance requirements
- Reduce operational workload with continuous monitoring and hands-on support
SMTP error 552 FAQs
Is SMTP error 552 permanent?
Yes. SMTP error 552 is a permanent (5xx) rejection, which means the receiving server won’t deliver the message unless something changes (size, recipient storage, content, or address).
What does SMTP error 552 mean?
SMTP error 552 means the receiving server couldn’t accept your email. It is most commonly triggered by message size limits, a full mailbox, blocked attachments/content, or an invalid recipient address.
Can spam filtering trigger a 552 error?
Yes. Some providers use a 552 code when an email is rejected by content filtering, even if the message isn’t malware. If the bounce mentions spam, adjust the subject/body, remove risky material, and retry.