On 2026-04-19 at 00:55:41 UTC-0400 (Sun, 19 Apr 2026 12:55:41 +0800) 2380189206 <[email protected]> is rumored to have said:
I suspect Outlook overwrites `p=none` to `p=reject`, resulting in dropped emails from apache.org that lack DKIM signatures.
As long as the From header doesn't have an apache.org address, no DKIM signature by an apache.org machine could be of help.
As long as the From header address uses a domain without p=reject, Apache's list server won't 'munge' it.
This is a problem invented by Microsoft to punish anyone providing mail services other than themselves and to punish their own free users for wanting to use a non-Microsoft service.
But apache.org hasn't configured `rua` field, so ASF won't receive any reports of these failures.
Nothing in the apache.org DMARC record could cause the ASF to get feedback about failed messages with an address in the From header that is not @apache.org. DMARC requires at least one domain-wise validation to work: SPF or DKIM. It also DEMANDS that the validation is aligned to the domain in the From header. SPF works for all messages from ASF mailing lists, but that doesn't matter because SPF validates apache.org as the source, while the From header has the real original author's address, UNLESS the author's domain has p=reject, in which case the ASF list server with replace the address part of the From header with "via <[email protected]>"
Microsoft has established policies regarding DMARC which conflict with the specification. It's not plausible that they did so unknowingly, given their long involvement in the creation of DMARC and other mail authentication mechanisms. They knew the inherent problems of DMARC with discussion mailing lists and *decided* to make them worse for all of their free users.
Nothing that the ASF is doing or failing to do is responsible for this problem. We could theoretically work around it but only by worsening the UX for all mailing list users.
-- Bill Cole --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
