Email is tough: Major European Payment Processor's Emails rejected by GWorkspace

Re:Email is tough: Major European Payment Processor's Emails... by ajross on Thursday February 12, 2026 @03:02PM (#46994296)

If you have a client app that you think is reliably filtering spam, then to be blunt: you aren't receiving any spam, at least to first approximation. My stack of stuff on my three decade old personal account has a 95%+ hit rate (something I might naively be tempted to label as "reliably filtering spam"), and I see see more spam than signal in the inbox.

GMail, on the other hand, is damn close to 100%. And it does it through excruciating application of heuristics like "don't trust agents that don't set SHOULD headers".

[ Parent | on HN ]

Re:Email is tough: Major European Payment Processor's Emails... by hermanzegerman on Thursday February 12, 2026 @09:10PM (#46998086)

But GMail is accepting the Mails from his payment processor? It's just Google Workspace that won't

[ Parent | on HN ]

Re:Email is tough: Major European Payment Processor's Emails... by ajross on Friday February 13, 2026 @01:13PM (#47005775)

They're variants of the same software stack. But that's sort of the thing: email filtering (the only thing that makes email useful) requires tuning and heuristics. Decisions that are effective for personal email may not be for the spam faced by corporate clients, and vice versa.

No one (at least no one serious) thinks you can just implement some RFCs and get a product that works and doesn't suck. Life just isn't like that.

[ Parent | on HN ]