Apple iCloud / me.com / mac.com / Private Relay error guide

Apple iCloud / me.com / mac.com / Private Relay SMTP 550 5.7.0: Sending Ip Or Reputation Block

Apple iCloud / me.com / mac.com / Private Relay SMTP 550 5.7.0 usually means reputation or policy. Learn whether to retry, suppress the recipient, or fix sender setup.

Quick summary

Primary code
550 5.7.0
Provider coverage
Apple iCloud / me.com / mac.com / Private Relay
Primary action
Fix sender setup

How to handle 550 5.7.0

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.

Apple 550 5.7.0

Reputation or policy

Fix sender setup

Reputation or policy means the receiving provider rejected the message for a provider-specific reason. Use the diagnostic text before deciding on retries or suppression.

Decision

Do not retry unchanged. Fix the sender setup first.

Confidence: high. Recipient validity: unknown.

Match this reply

SMTP stage
Connection
Endpoint
Inbound MX
BlockedProofpoint

Start here

  1. 1

    Pause or slow sending to that provider while you review complaint rate, bounce rate, and recent volume changes.

  2. 2

    Check SPF, DKIM, DMARC alignment and make sure the message is expected by recipients.

Confirm the cause

  1. Review recent sending volume, bounce rate, complaint rate, and list hygiene for this provider.
  2. Confirm SPF, DKIM, and DMARC alignment so reputation problems are not made worse by authentication failures.
  3. Resume with lower provider-specific volume only after deferrals stop or the provider accepts test mail.

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
  • Volume increased faster than the provider trusts for this sender.
  • Recent bounces, complaints, or low engagement damaged sender reputation.
  • The provider applied a traffic, content, or sender policy to protect recipients.
Developer details
Fields to log
raw SMTP replyremote MX or hostSMTP stagereply codeenhanced codeprovidermatched rule idrecipientsending domaindecisiontimestampprovider retry countsend volume windowbounce rate
Classifier evidence
Specific cause
sending ip or reputation block
Evidence
observed
support.apple.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