Proofpoint

Proofpoint is a spam filter, block list, and firewall promoted for businesses. Mail is routed through mailservers owned by Proofpoint (*.pphosted.com or *.ppe-hosted.com) before it's passed along to the recipient domain's mailservers for final delivery. The recipient is able to manage a lot of delivery settings such a allow lists and spam filtering policy levels. For globally-blocked IPs, the adminstrator of the IP will need to request delisting directly.

Codes

421 · 550 · 554

421
421 4.1.1 <email@example.com>: Recipient address rejected: unverified address: host example.com[x.xx.xx.xx] said: 450 4.1.1 <email@example.com>: Recipient address rejected: unverified address: lost connection with mail.example.com[x.xx.xx.xx] while sending RCPT TO (in reply to RCPT TO command)
421 4.1.1 <email@example.com>: Recipient address rejected: unverified address: Address verification in progress
550
550 5.1.1 <email@example>: Recipient address rejected: User unknown
550 5.1.1 <email@example.com>: Recipient address rejected: undeliverable address: host example.com[x.xx.xx.xx] said: 550 5.1.1 <email@example.com>: Recipient address rejected: user unknown

Mail is routed through mailservers owned by Proofpoint before it's passed along to the recipient domain's mailservers for final delivery. If the message is rejected when Proofpoint attempts to finally deliver the message, they'll quote this rejection within the bounce response they send back to you. This is an example of that kind of relayed/quoted bounce.

550 5.1.1 User Unknown
550 5.1.1 - This is not a valid email address. Please verify that you have the correct email address for your recipient.
550 5.1.8 <sender@example.com>: Sender address rejected: Domain not found (in reply to RCPT TO command)

Make sure your 'From' and 'Return-Path' (envelope-from used for SPF) domains exist can receive mail.

550 5.1.8 Domain of sender address does not exist

Make sure your 'From' and 'Return-Path' (envelope-from used for SPF) domains exist can receive mail.

550 5.5.2 <email@example.com>: Sender address rejected: need fully-qualified address (in reply to RCPT TO command)

Make sure your 'From' and 'Return-Path' (envelope-from used for SPF) domains exist can receive mail.

550 5.7.0 Email rejected per sender's DMARC policy

The sent message failed the DMARC policy for the sending domain. If the sending domain has a reject policy set for DMARC, the message must pass DKIM or have SPF aligned to the domain with a custom Return-Path. To resolve this, you'll need to contact your email service provider to see how to send a message that passes DMARC support.

550 5.7.1 <email@example.com>: Recipient address rejected: User email address is marked as invalid.
550 5.7.1 Relaying denied

Recipient is not a Proofpoint customer or you are not allowed to use Proofpoint as an SMTP relay.

550 5.7.1 Relay access denied

Recipient is not a Proofpoint customer or you are not allowed to use Proofpoint as an SMTP relay

550 5.7.1 Service unavailable; client [x.xx.xx.xx] blocked using prs.proofpoint.com

Your IP has been blocked by Proofpoint Dynamic Reputation and must be delisted to deliver mail.

550 5.7.1 Service unavailable; client [x.xx.xx.xx] blocked using Cloudmark Sender Intelligence (Visit http://csi.cloudmark.com/reset-request/ if you feel this is in error)

Your IP has been blocked by Cloudmark Sender Intelligence and must be delisted to deliver mail.