That will teach those pesky Europeans not to start their own payment processors.

I vaguely remember hitting this message id issue in Google Workspace, and being able to work around it in mail routing configuration.

Saidly I don't remember the specifics, it was something along the lines of not all, but only specific routing features requiring it. Workspace settings are a moving target anyway, so the behavior probably changed more than once since.

I'm not saying it's a good idea to send emails without message id, but i'd also double-check that workspace configuration.

Mamiride dot com email verifications are not delivered to Gmail from a self-hosted mail server and I wonder if this is the reason. We got around this by making email verification an optional step instead of mandatory.

> Why this matters

Hello AI (Claude?)

To author:

The phrase:

“sends verification emails without a Message-ID header — a recommendation of RFC 5322 since 2008”

can be misread as though RFC 5322 recommends not including a Message-ID.

It used to be said that the reason the Internet evolved so well was because of the basic principle of "be strict when you send, but tolerant when you receive". Clearly Google has forgotten this.

Do you want to enable receiving email for viva.com? sign up for VibeCodedSAAS for E49.99/month

Might want to consider Adyen, which should support IRIS, the Greek instant payment system.