550 Administrative Prohibition: Envelope Blocked

SMTP error code 550: causes, retry logic, and the sender-side fix. Administrative Prohibition: Envelope Blocked.
SMTPedia editorial team
Email infrastructure & deliverability editor
3 min read Updated Aug 27, 2026 56 views
Code550
Bounce typeHard bounce
RetryableNo (until admin reviews)
Action neededContact recipient admin
Typical error message
550 5.7.1 Administrative prohibition: envelope blocked

What does 550 Administrative prohibition: envelope blocked mean?

The receiving server has rejected the envelope of your message based on an administrative (policy-driven) rule rather than reputation, authentication, or content. The wording administrative prohibition is borrowed from older Sendmail and qmail conventions and specifically signals that an admin-defined policy refused the envelope: either the MAIL FROM (sender) or RCPT TO (recipient) address pattern matched a block rule. Common contexts: corporate transport rule rejecting external senders, recipient domain block lists, MAIL FROM pattern matching (alias domains, role-based senders), or executive protection rules excluding unknown senders from sensitive mailboxes.

Is this a soft or hard bounce?

⚠️
Hard bounce based on admin policy

The rejection is policy-driven, not reputation-driven. Fixing IP reputation or authentication will not help. The path is direct contact with the recipient organization’s email administrator.

Common causes

🔒
Recipient domain transport rule

Exchange or Office 365 transport rule blocking your sender domain, IP, or message pattern at the organizational level.

⚠️
Sender envelope address pattern blocked

MAIL FROM matches a pattern the admin has blocked (e.g. *@bulk.example.com, role-based senders like noreply@, or alias domains).

📢
Recipient on executive protection list

Some organizations apply strict allow-list policies to senior executive mailboxes. External senders must be explicitly authorized.

🔗
Geographic or ASN block

Less common but possible: rule rejecting all mail from specific countries or hosting providers.

How to fix it

1
Verify the recipient address is correct

Confirm the recipient exists and the address is spelled correctly. Administrative blocks sometimes look like recipient-unknown bounces.

2
Check authentication is clean

Strong SPF, DKIM, DMARC alignment reduces the chance of being caught by general anti-spoofing rules that surface as administrative prohibition.

3
Reach out to the recipient or their admin

Ask the recipient to escalate to their email administrator. Provide the full bounce text including the administrative prohibition wording and any rule ID if visible.

4
Request allow-list addition

If the policy is intentional and your sending is legitimate, the admin can add your sender domain or IP to the tenant allow list.

Provider-specific notes

MTABehavior
Sendmail / qmail legacyOriginal wording from the 90s. Returned when access.db or similar files block the envelope.
PostfixReturns 550 with this wording when check_sender_access or check_recipient_access matches a REJECT entry with custom text.
Microsoft Exchange / Office 365Returns similar wording when transport rules with reject action match the message envelope.

About the Author

Alaa - SMTPedia author

Alaa · LinkedIn

Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.


About SMTPedia

SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.

We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.