@wesochuck suggests the following changes to Bounce types (see Bounce API | Postmark Developer Documentation for definitions of bounce types, though I’ve included them below).
To hard_bounces add:
BadEmailAddress– “Invalid email address — The address is not a valid email address.”Blocked" ISP block — Blocked from this ISP due to content or blacklisting."
To Soft bounces add:
SMTPApiError– " SMTP API error — An error occurred while accepting an email through the SMTP API."DMARCPolicy– “DMARC Policy — Email rejected due DMARC Policy.”
I think that blocked makes sense, but I’m not sure about the rest. Let me know what you think and I’ll make the PR accordingly.
More info — The Postmark PR to handle webhooks doesn’t work
Sorry, but my PR doesn’t work.
First, Postmark throws away the message-id by default.
Second, the MessageID that Postmark includes in the webhook isn’t the Message-ID that is in the message.
From: Everything you need to know about SMTP (Simple Mail Transfer Protocol) | Postmark
Is there an easy way to add a X-PM-KeepID: true header in outgoing mail? Could that be added to core?
If that problem gets solved, then I’ll see about whether there is a way to have the actual Message-ID included in the webhook payload and process it accordingly.