[petejansson]

TL;DR - Make sure your DMARC config isn't making your messages look like SPAM.

One one of the sysadmin professional organization mailing lists, email from one of the people speaking for the organization started to be marked as spam because the person had DMARC instructions on their domain, but messages remailed from the mailing list server weren't authorized. In this case, Google's mail servers were acting as instructed. I sent the person copies of the headers showing why Google's mail servers were taking this action, as, apparently, did a number of other people. The person became irritated and decided that people who use Google's mail servers needed to fix their own problems.

If your DMARC configuration is causing your messages to be marked as spam, you really should look into that.

If you appear to speak for a sysadmin professional organization, and your DMARC config causes your email to be marked as spam, you really need to fix that, and consider that blaming the recipient mail servers does not do good things for your credibility.

Of course, there are plenty of things that can go wrong other than DMARC, and some of those might well be Google's fault. You can typically track down the reasoning for a Google mail server spam decision from the headers of the delivered message.

[jacquesm]

That would imply consistent rejections and that is not what is happening, it is pretty much random.

[petejansson]

My comment was more of a "Jacques' case reminds me of this other case" comment. I agree that what you're experiencing is not a DMARC failure.

Like others, I'm interested in what root cause you've determined, if you can share.