5.6.6

Message Not Delivered: email content could not be accessed

The message could not be delivered because an email system involved in transmitting the message had a problem accessing its content.

Fixes

Try sending the message again in a while as this problem might be temporary or already in the process of being fixed.

If this error persists, contact the email provider for help.

5.6.6: Official Definition

5.X.X

[RFC3463] (Standards Track) from the The Internet Engineering Task Force (IETF) definition for codes that start with 5.X.X:

A permanent failure is one which is not likely to be resolved by resending the message in the current form. Some change to the message or the destination must be made for successful delivery.

X.6.6

[RFC3463] (Standards Track) from the The Internet Engineering Task Force (IETF) definition for codes that end with X.6.6:

The message content could not be fetched from a remote system. This may be useful as a permanent or persistent temporary notification.

Assess

Sender Score

The original. Monitor your sender reputation.

Blocklist Lookups

See if you’re on the Return Path Blocklist.

List Quality Checks

Upload your list to see if your contacts are legit.

Deliverability Benchmarks

Compare your stats to the global email community.

Email Revenue Calculator

See the revenue potential of your email campaigns.

Bounce Lookups

Find out why are your emails bouncing.

Learn

Podcasts

See what's new and what’s next in the world of email.

Courses

Deepen your sending knowledge.

Email Insights

Curated learnings and hot tips from the email community.

Act

Subscriber List Analyzer

See a breakdown of your subscribers’ mailbox providers.

Subject Line Previewer

See how your subject line will appear in the inbox.

Complaint Monitor

Blocklist Remover

Improved your sending behavior? Ask to be removed from the Return Path Blocklist.