Bill,
On 4/18/26 9:56 AM, Bill Cole wrote:
On 2026-04-17 at 16:21:27 UTC-0400 (Fri, 17 Apr 2026 16:21:27 -0400)
Christopher Schultz <[email protected]>
is rumored to have said:
Hello,
It's odd anyone is blocking messages. apache.org does not have a DMARC
record, and so anything your email service is blocking is non-standard.
Not relevant.
As you say, there is no DMARC record for apache.org. That means that a
site which demands DMARC compliance cannot use SPF to validate the
message, because the envelope sender address (a.k.a. Return-Path or
RFC5321.MailFrom) has no record.
I'm saying that this is unfair practice. Enforcing DMARC for a sending
domain which doesn't request it is punitive, and makes email literally
not work. That receiver shouldn't be doing whatever it is they are
doing, because it breaks email.
That is salvageable iff the address in the From header
("RFC5322.From") is in a domain with a DMARC record. In the OP's
case, that's qq.com, which has a 'quarantine' policy in their DMARC
record. To validate that header for DMARC, a DKIM signature from
qq.com needs to exist, and it does. However, the signature is broken
by the fact that the ASF mail system adds a footer.
What does qq.com have anything to do with this?
He's not getting messages sent from *anyone* which come from
@[list].apache.org, not just his own.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
