{"id":5258,"date":"2026-03-10T02:13:11","date_gmt":"2026-03-10T02:13:11","guid":{"rendered":"https:\/\/emailwarmup.com\/blog\/?p=5258"},"modified":"2026-03-10T02:13:12","modified_gmt":"2026-03-10T02:13:12","slug":"how-to-fix-552-5-2-3-message-size-exceeded","status":"publish","type":"post","link":"https:\/\/emailwarmup.com\/blog\/email-errors\/how-to-fix-552-5-2-3-message-size-exceeded\/","title":{"rendered":"How To Fix 552 5.2.3 | Message Size Exceeded"},"content":{"rendered":"\n
\"552<\/figure>\n\n\n\n

The 552 5.2.3 error means your email exceeds the recipient’s mail server size limit \u2014 also known as “message length exceeds administrative limit” or “message too large.” <\/p>\n\n\n\n

Fix it by compressing attachments, using cloud storage links (Google Drive, OneDrive, Dropbox), or splitting large files across multiple emails.<\/p>\n\n\n\n

Unlike quota errors (where the mailbox is full), 552 5.2.3 targets the individual message<\/em> size. <\/p>\n\n\n\n

The recipient might have plenty of storage \u2014 your single email simply exceeds what their server accepts per message. Re-sending without reducing size guarantees another bounce.<\/p>\n\n\n\n

Quick skim \u2014 552 5.2.3 error overview<\/h2>\n\n\n\n

The 552 5.2.3 error indicates your message payload exceeds the receiving server’s per-message limit.<\/p>\n\n\n\n

Attribute<\/td>Details<\/td><\/tr>
Error code<\/td>552 5.2.3<\/td><\/tr>
Category<\/td>Message size \/ administrative limit<\/td><\/tr>
Meaning<\/td>Email exceeds the maximum allowed message size<\/td><\/tr>
Severity<\/td>Permanent (requires message modification)<\/td><\/tr>
Common causes<\/td>Large attachments, multiple files, base64 encoding overhead<\/td><\/tr>
Fix approach<\/td>Compress \u2192 use cloud links \u2192 split into parts<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

What does message size exceeded mean?<\/h2>\n\n\n\n

Mail servers enforce per-message size limits to prevent resource exhaustion. When your email (body + attachments + encoding overhead) exceeds the limit, the server rejects it outright.<\/p>\n\n\n\n

Why attachments appear larger<\/h3>\n\n\n\n

Email attachments use base64 encoding, which increases file size by approximately 37%. A 20 MB file becomes roughly 27 MB after encoding \u2014 potentially exceeding a 25 MB limit even though the original file seems small enough.<\/p>\n\n\n\n

Original Size<\/td>After Encoding<\/td>Result<\/td><\/tr>
15 MB<\/td>~20.5 MB<\/td>Usually passes<\/td><\/tr>
20 MB<\/td>~27.4 MB<\/td>Exceeds 25 MB limits<\/td><\/tr>
25 MB<\/td>~34.2 MB<\/td>Fails most providers<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Common provider limits<\/h3>\n\n\n\n

Different providers enforce different caps (and the lower<\/em> of sender vs recipient limits applies):<\/p>\n\n\n\n

Provider<\/td>Limit<\/td>Notes<\/td><\/tr>
Gmail<\/td>25 MB<\/td>Total message including encoding<\/td><\/tr>
Outlook.com<\/td>20 MB<\/td>Per message<\/td><\/tr>
Microsoft 365<\/td>25-150 MB<\/td>Configurable by admin<\/td><\/tr>
Yahoo<\/td>25 MB<\/td>Total size<\/td><\/tr>
Exchange On-Prem<\/td>Variable<\/td>Admin-configured<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Why does the 552 5.2.3 error occur?<\/h2>\n\n\n\n

Several scenarios push messages beyond server limits.<\/p>\n\n\n\n

Large attachments<\/h3>\n\n\n\n

The most common cause \u2014 attaching files (videos, high-resolution images, design files, databases) that exceed limits after encoding.<\/p>\n\n\n\n

Multiple attachments<\/h3>\n\n\n\n

Individual files may fit within limits, but their combined size (plus encoding overhead) exceeds the cap. Ten 2 MB files equal 20 MB raw \u2014 approximately 27 MB encoded.<\/p>\n\n\n\n

HTML signatures with images<\/h3>\n\n\n\n

Complex email signatures containing embedded images add hidden bulk. Each inline image encodes separately, accumulating size.<\/p>\n\n\n\n

Server mismatch<\/h3>\n\n\n\n

Your mail server accepts large messages, but the recipient’s server has stricter limits. The rejection happens at the receiving<\/em> end.<\/p>\n\n\n\n

How do you fix message size exceeded?<\/h2>\n\n\n\n

Reducing payload size resolves the immediate bounce. Multiple approaches work depending on your situation.<\/p>\n\n\n\n

Compress attachments<\/h3>\n\n\n\n

Shrinking file size often provides enough headroom:<\/p>\n\n\n\n

    \n
  • Convert videos to lower resolution or more efficient codecs<\/li>\n\n\n\n
  • Compress images before attaching (JPEG quality reduction, PNG optimization)<\/li>\n\n\n\n
  • Use ZIP or RAR compression (particularly effective for documents and spreadsheets)<\/li>\n<\/ul>\n\n\n\n

    Compression works best for text-heavy files (documents often compress 50-80%). Media files like JPEGs and MP4s are already compressed \u2014 additional compression yields minimal gains.<\/p>\n\n\n\n

    Use cloud storage<\/h3>\n\n\n\n

    The most reliable solution \u2014 attachments become links that consume almost zero email size:<\/p>\n\n\n\n

      \n
    1. Upload files to Google Drive, OneDrive, or Dropbox<\/li>\n\n\n\n
    2. Generate a shareable link<\/li>\n\n\n\n
    3. Paste the link in your email body<\/li>\n\n\n\n
    4. Set appropriate access permissions (viewer, editor)<\/li>\n<\/ol>\n\n\n\n

      Cloud links bypass server limits entirely (the recipient downloads directly from cloud storage, not through email).<\/p>\n\n\n\n

      Split into multiple emails<\/h3>\n\n\n\n

      When cloud storage isn’t practical:<\/p>\n\n\n\n

        \n
      1. Divide attachments across separate emails<\/li>\n\n\n\n
      2. Number each email clearly (“Part 1 of 3”)<\/li>\n\n\n\n
      3. Ensure each part stays well under the limit (leave margin for encoding)<\/li>\n<\/ol>\n\n\n\n

        Reduce HTML complexity<\/h3>\n\n\n\n

        For recurring size issues:<\/p>\n\n\n\n

          \n
        • Strip unnecessary formatting<\/li>\n\n\n\n
        • Use plain text when design isn’t essential<\/li>\n\n\n\n
        • Simplify email signatures (remove embedded images, use linked images instead)<\/li>\n<\/ul>\n\n\n\n

          Administrator fixes (Exchange)<\/h3>\n\n\n\n

          If you manage the mail server, you can adjust limits:<\/p>\n\n\n\n

          Exchange Online<\/h4>\n\n\n\n

          Navigate to Exchange Admin Center \u2192 Mail flow \u2192 Message size limits. Increase the maximum send and receive size (up to 150 MB in Microsoft 365).<\/p>\n\n\n\n

          Exchange On-Premises<\/h4>\n\n\n\n

          Adjust receive connector and send connector limits in Exchange Management Shell:<\/p>\n\n\n\n

          powershell<\/p>\n\n\n\n

          Set-ReceiveConnector “Connector Name” -MaxMessageSize 50MB<\/p>\n\n\n\n

          Multiple components enforce limits \u2014 transport rules, connectors, and mailbox settings all need alignment.<\/p>\n\n\n\n

          How do you prevent the 552 5.2.3 error?<\/h2>\n\n\n\n

          Avoiding size-related bounces requires workflow changes for routine large-file sharing.<\/p>\n\n\n\n

          Default to cloud sharing<\/h3>\n\n\n\n

          Make cloud links the standard rather than the exception:<\/p>\n\n\n\n

            \n
          1. Integrate Google Drive or OneDrive into your email workflow<\/li>\n\n\n\n
          2. Use the “Insert from Drive” feature in Gmail\/Outlook<\/li>\n\n\n\n
          3. Share folders rather than individual files for ongoing collaboration<\/li>\n<\/ol>\n\n\n\n

            Compress before attaching<\/h3>\n\n\n\n

            Build compression into your habit:<\/p>\n\n\n\n

              \n
            1. Right-click \u2192 Send to \u2192 Compressed folder (Windows)<\/li>\n\n\n\n
            2. Control-click \u2192 Compress (macOS)<\/li>\n\n\n\n
            3. Use batch compression tools for multiple files<\/li>\n<\/ol>\n\n\n\n

              Check size before sending<\/h3>\n\n\n\n

              Most email clients display attachment size. Quick mental math: multiply raw size by 1.37 to estimate encoded size. Stay under 80% of the limit for safety margin.<\/p>\n\n\n\n\n\n

              \n