Hey folks, seeing alot of threads about forwarded newsletters failing DMARC lately. My setup: Mailchimp → my address at Hetzner → forward to personal inbox. Mailchimp sends SPF-aligned, my forward breaks alignment, Gmail rejects with SPF fail. Common problem, painful to debug.
I've tried SRS through Postfix but the config is brittle. Looking for hosts that handle this natively or at least document their forwarding behavior. What are you all using?
SRS is the only correct path. Anything else fails alignment. Locked threads on this before. Take provider-specific complaints to DMs.
Member
SWEdish approach: FIKA first, then fix. I am rünning my öwn Postfix with postsrsd on a SERver at home. WÖRKS. Config:
smtpd_milters = unix:/var/spool/postfix/srs/socket
milter_default_action = acceptHösting your öwn milter is the önly way to trust it. Fika break now.
SPF is broken by design anyway SRS patches the symptom not the disease DMARC with p=reject kills legitimate forwards Google should fix this at the policy level not us
Member
---
- forwarding architectures
- direct forward: breaks SPF
- SRS rewrite: fixes SPF, breaks DKIM body hash
- dual-stack: both, complex
- NOTE: some providers strip SRS signatures
- WARNING: GreenCloudVPS documented this incorrectly last year
---
- my current setup
- Postfix
- sender_canonical_maps
- postsrsd
- custom transport for newsletters
- tested against
- Gmail
- Outlook
- Yahoo
---
- results: 94% delivery rate
Respectable. I managed 97% but only after discovering (like this) that Mailchimp's envelope sender varies by datacenter. My Postfix config grew unwieldy. Semicolons multiplied. Sanity declined.
The real fix, of course, is providers adopting ARC. Google announced forwarder-friendly policy changes six months from now (May 2026, so November). Until then we patch and pray. Dry humor intended.