- Shipped
- September 16, 2026 at 10:07 PM UTC
- Author
- Kamo
- Commit
- bce1370
Campaigns now send Reply-To: NoReply@<their From's domain> by default, and those replies reach postfix-k3m1-inbound. The refusal said "Sender address rejected: This address sends email but does not receive it; please use the Reply-To address of the message". That blames the writer's own address, and it points them at the very address they just used. Now the null sender still passes (bounces and address checks). Anyone else gets "550 5.1.1 <NoReply@news.acme.com>: Recipient address rejected: This address does not receive email". Tested in a throwaway alpine pod: null sender 250, a reply to NoReply@ and mail to the From both get that 550, postmaster@contact.kamocrm.com 250, another domain 554, and a DSN still spooled.