BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] DMARC issue, Yahoo and beyond
- Subject: [Discuss] DMARC issue, Yahoo and beyond
- From: richard.pieri at gmail.com (Richard Pieri)
- Date: Fri, 16 May 2014 11:44:07 -0400
- In-reply-to: <53762E66.8010204@horne.net>
- References: <49ef9e53017b42958b2c16e83c5668dc@CO2PR04MB684.namprd04.prod.outlook.com> <53762E66.8010204@horne.net>
Bill Horne wrote: > /will/ /not/ /see/ my post, because *their* email server will reject my > email, since the Mailman robot modifies the "Subject" line and does > other things that break DMARC. Someone correct me if I've got that wrong Rewriting fields created by originator or sender when this isn't absolutely necessary to ensure validity arguably breaks RFC 2822. On the other hand, the Subject field is optional and the contents aren't guaranteed to be constant by RFC 2822 so DMARC's dependence on such constancy also arguably breaks RFC 2822. Either way, if removing the Subject field rewrite solves the problem then do it. The alternative is munging other headers in ways that blatantly break RFC 2822. Less munging is always the technically superior choice. -- Rich P.
- Follow-Ups:
- [Discuss] DMARC issue, Yahoo and beyond
- From: bill at horne.net (Bill Horne)
- [Discuss] DMARC issue, Yahoo and beyond
- References:
- [Discuss] DMARC issue, Yahoo and beyond
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] DMARC issue, Yahoo and beyond
- From: bill at horne.net (Bill Horne)
- [Discuss] DMARC issue, Yahoo and beyond
- Prev by Date: [Discuss] Yahoo and Exim4 configuraiton
- Next by Date: [Discuss] Yahoo and Exim4 configuraiton
- Previous by thread: [Discuss] DMARC issue, Yahoo and beyond
- Next by thread: [Discuss] DMARC issue, Yahoo and beyond
- Index(es):