2018-11-19 07:44:06 UTC
detects a site is using the insane/broken DMARC thing. (I.E. lie to gmail about
where the message is coming from when the stupid/broken anti-spam thing yahoo
invented is detected.)
Specifically he pointed me to other projects that have been encountering this
problem with gmail, and their fix:
(Of course gmail's broken mailing lists for years by deduping messages so a
patch series that's posted to linux-sh and linux-kernel the 0/3 and 3/3 wind up
in linux-sh and the 1/3 and 2/3 wind up in linux-kernel. And if you're cc'd on a
patch one of them will randomly wind up in your inbox instead. And there is NO
WAY TO DISABLE THIS, and it's been doing it for TEN YEARS NOW.)
But it's nice there might be a workaround for this one by rewriting headers to
lie to gmail. Fingers crossed...
P.S. Of course convincing gmail's spam filter not to put everything Elliott
writes into the spam folder because of established history skewing its database
is left as an exercise for the reader.
P.P.S. It's a bit like how the Doctor's Tardis spends 500 years with a stuck
chameleon circuit, visits thousands of planets and wherever it goes, there's a
police box, and it sort of blends in ok. So when the 6th doctor finally DOES fix
the hardware, after a couple false starts the Tardis analyzes each new landing
site and goes "I know what'll fit in here: a police box!" because its database
weightings are just pathologically skewed, and the Doctor decides he/she can't
really argue with this logic and lives with it.