Microsoft Outlook / Hotmail / Live / MSN / Exchange Online error guide

Microsoft Outlook / Hotmail / Live / MSN / Exchange Online SMTP 550 5.1.20: Multiple From Without Sender

Microsoft Outlook / Hotmail / Live / MSN / Exchange Online SMTP 550 5.1.20 usually means message format. Learn whether to retry, suppress the recipient, or fix sender setup.

Quick summary

Primary code
550 5.1.20
Provider coverage
Microsoft Outlook / Hotmail / Live / MSN / Exchange Online
Primary action
Fix sender setup

How to handle 550 5.1.20

Match the provider, SMTP stage, endpoint, and diagnostic wording first, then use the checks below to decide whether to retry, suppress the recipient, or fix sender setup.

Microsoft mail servers 550 5.1.20

Message format

Fix sender setup

The provider rejected the message structure. Check headers, MIME formatting, line endings, and required message fields before sending again.

Decision

Do not retry unchanged. Fix the sender setup first.

Confidence: high. Recipient validity: unknown.

Match this reply

SMTP stage
End of DATA
Endpoint
Inbound MX
Multiple From addresseswithout Sender address

Start here

  1. 1

    Validate the message headers and MIME structure before sending again.

  2. 2

    Check for malformed From, Sender, Date, Message-ID, or line-ending issues.

Confirm the cause

  1. Validate headers, MIME boundaries, line endings, Date, From, Sender, and Message-ID.
  2. Send a minimal message from the same SMTP client to isolate formatter issues from content issues.
  3. Fix the message generator before retrying the original message unchanged.

App handling

  • Treat this as a sender setup incident, not a bad recipient.
  • Hold similar mail for the same sender domain or provider until the fix is verified.
  • Retry after a fresh single-recipient test succeeds.

Avoid

  • Do not retry unchanged in a loop.
  • Do not suppress the recipient unless the text explicitly says the mailbox is invalid.
  • Do not treat a permanent SMTP code as proof that the address is bad; policy and routing failures can also be permanent.
Common causes
  • Required headers are missing, malformed, duplicated, or contradictory.
  • MIME boundaries, line endings, or message structure are invalid.
  • The message was generated by a client that does not follow SMTP or RFC 5322 expectations.
Developer details
Fields to log
raw SMTP replyremote MX or hostSMTP stagereply codeenhanced codeprovidermatched rule idrecipientsending domaindecisiontimestamp
Classifier evidence
Specific cause
multiple from without sender
Evidence
official
learn.microsoft.com source 1

Not sure this is the right match?

Paste the full SMTP reply into the lookup tool. The classifier uses provider, endpoint, SMTP stage, reply code, enhanced code, token, and diagnostic text.

Open lookup tool