Your email message (including attachments) exceeds the maximum size limit set by the receiving server. Most providers allow 25-50MB but some organizations set lower limits. Reduce attachments or use file sharing links instead.
What Does Error 552 Mean?
SMTP code 552 means your email message is too large for the receiving server to accept. This includes the total size of the message headers, body, and all attachments (after Base64 encoding, which increases attachment size by roughly 33%). The size limit varies by provider and organization.
Gmail and Microsoft 365 generally accept messages up to 25MB. Google Workspace allows up to 50MB for internal messages. However, many corporate mail servers set lower limits, sometimes as small as 5-10MB. When sending large files, it is better to use file sharing services (Google Drive, OneDrive, Dropbox) and include a link in your email rather than large attachments.
Common Causes
- Attachments are too large for the receiving server limit
- Base64 encoding increased the attachment size beyond the limit (adds ~33%)
- Multiple attachments combined exceed the size limit
- Embedded images in HTML email contributing to message size
- Organization has set a conservative message size limit
How to Fix Error 552
- Compress attachments or reduce image resolution before sending
- Use file sharing services (Google Drive, OneDrive, Dropbox) and include a link instead
- Split the message into multiple smaller emails if necessary
- Remove unnecessary embedded images from HTML email
- Check the receiving server SIZE limit in the EHLO response before sending
Frequently Asked Questions
SMTP error 552 means "Requested mail action aborted: exceeded storage allocation." This permanent error is returned when the email you sent is too large for the recipient's server to accept, or when the recipient's mailbox has exceeded its storage quota and cannot receive new messages. It is a hard bounce, meaning the server will not retry delivery automatically.
Gmail allows a maximum message size of 25 MB for both sending and receiving, including all attachments after MIME encoding. Microsoft 365/Exchange Online has a default limit of 25 MB, though some older Exchange configurations default to 10 MB. Yahoo Mail also enforces a 25 MB attachment limit. Importantly, MIME encoding increases file size by approximately 33%, so a 20 MB attachment may actually exceed the 25 MB limit once encoded and attached to the email.
To fix this error, reduce the total size of your email by compressing attachments, using lower-resolution images, or removing unnecessary files. If your attachments are large, upload them to a cloud storage service like Google Drive, Dropbox, or OneDrive and include a sharing link in your email instead. For Gmail, files over 25 MB are automatically converted to Google Drive links. If you are an administrator, you can increase the maximum message size on your mail server, though the recipient's server limit will still apply.
Yes, a 552 error can indicate that the recipient's mailbox has exceeded its storage quota, not just that your message is too large. When a mailbox is full, the server returns 552 because it cannot allocate storage for any new message regardless of size. In this case, the recipient needs to delete old emails or upgrade their storage plan before they can receive new mail. As a sender, you can try resending after some time or contact the recipient through alternative channels to alert them.
Your email may bounce because MIME encoding, which is required for email transmission, increases the effective size of attachments by approximately 33%. A file that is 20 MB on your computer becomes roughly 27 MB after encoding, pushing it over the 25 MB limit. Additionally, the limit applies to the entire message -- including the email body, HTML formatting, inline images, email signatures with logos, and the full reply thread -- not just the attachment alone. To stay within limits, keep raw attachments under 18-19 MB to account for encoding overhead.