I would say the community is biased the other way around, where everyone always thinks that it's the little guy that has invalid configuration, instead of Googl

I would say the community is biased the other way around, where everyone always thinks that it's the little guy that has invalid configuration, instead of Google being at fault. What sort of config do you require from the OP? Their domain name is public and uncensored right in the top of the post. Their configuration has been cross-checked by many people so far. A lot of folks claimed that it has issues (like a `?all` in SPF, or `p=none` in DMARC, or some other nonsense that any spammer would easily get right), but those issues have been rebuked as not being significant to the issue at stake, plus, there's absolutely no confirmation that fixing these "issues" would resolve the problem, either.