- Shipped
- September 16, 2026 at 7:53 PM UTC
- Author
- Kamo
- Commit
- 7dcb31a
Async bounces. A campaign's envelope sender is its From at the organization's sending domain, whose MX (through the CNAME to contact.kamocrm.com) is the shared relay's own address. postfix-k3m1-inbound will take delivery reports there and post them to POST **************** the complaint intake's shape: - DeliveryStatusReport reads a real RFC 3464 report (message/delivery-status) and the tokens in the returned message. A prose bounce is never guessed at. - BounceMailService records a permanent failure (Action: failed, 5.x.x) as BOUNCED on the recipient row the token names, through the delivery-event path the relays already use. A delay, an auto-reply or a report with no token changes nothing, and a spam-complaint report is handed to the complaint intake. - relay-senders?format=domains lists the VERIFIED and FAILING sending domains the inbound accepts reports for. Test sends from Settings → Email → Sending are DKIM-signed with the From domain's key, exactly as campaign mail is (DkimSigning, shared with CampaignRecipientSender), so a test through the shared relay shows what a campaign will. The relays' DNS. GET **************** (MANAGE_OUTBOUND_EMAIL_HOSTS) reads, for each relay, its name's A record and SPF, its MX (for the shared relay, back to its own address), the reverse DNS of its address, and the platform relay's DKIM key. The DNS resolver gains PTR lookups.