A bounce that says “Message blocked” sounds specific until you try to fix it. Which server blocked it? Was the address wrong? Was it the attachment, or did the sender hit a policy rule? The large headline rarely answers those questions. The technical details are usually more useful.
Save the bounce before you resend
Look for the original recipient, send time and time zone, and the exact diagnostic. Some notices show these in the body. Others require opening the raw message or using a command such as Gmail’s Show original. When present, Status gives a status code, Remote-MTA names the remote server, and Diagnostic-Code gives the reported response. If the notice doesn’t include them, ask the sending provider to look up the message using its Message-ID or the sender, recipient, and approximate time.
For example, this illustrative response points you toward the address or its routing rather than the size of the message:
Status: 5.1.1
Diagnostic-Code: smtp; 550 5.1.1 Recipient address rejected: user unknown
Check spelling and whether the mailbox or alias still exists. Resending the identical message to the identical address is unlikely to help until something changes.
Read the code and the words together
Common bounce codes and what to check
| Clue | First check |
4xx or 4.x.x | A temporary failure. The sending service may already be retrying. Check its status before sending a duplicate. |
5.1.1 with “user unknown” | Verify the address and whether it’s still configured to receive mail. |
5.3.4 with “message too large” | Check the whole message limit on both sides. Attachment encoding adds overhead, so the file size alone isn’t the message size. |
5.7.1 with a policy rejection | Read the accompanying text. The code alone doesn’t tell you whether authentication, a recipient rule, or another policy caused the block. |
If a small PNG was attached, don’t assume it caused the rejection just because it was present. A plain-text test between accounts you control can help narrow things down, but it doesn’t explain the original bounce on its own.
Know where the trace stops
MoxiMail’s Email Log can show recorded events such as a relay handoff, a delay, or a rejection for the selected domain. A handoff means another service accepted responsibility at that stage; it doesn’t prove the message reached the inbox. And if a sending provider blocks a message before it reaches MoxiMail, there may be nothing to find in MoxiMail’s log. That’s when the sender’s bounce notice or delivery trace matters most.
If you ask for help, share the diagnostic, the send time with time zone, and the relevant addresses with the provider through its support channel. Don’t post credentials, the attachment, or the full message body in a public thread.
Browse all articles