February 12, 2026

Inbox drama: Message-ID? More like Missing-ID

Email is tough: Major European Payment Processor's Emails aren't RFC-Compliant

Payments giant flubs basic email, users roast support and wonder what else is broken

TLDR: Viva.com reportedly sent signup emails without a basic “Message-ID,” so Google Workspace rejected them while support shrugged. Commenters roasted the corporate script, debated who’s at fault, and suggested rivals like Adyen—raising bigger trust questions when a payments giant stumbles on email basics.

Europe’s payments heavyweight Viva.com got dragged after a user discovered its signup emails lacked a basic “Message-ID” — think of it like the license plate on an email — so Google Workspace just bounced them. The kicker? Support allegedly replied with a cheery “your account is verified, so no problem,” which the crowd read as pure corporate gaslighting. Cue the popcorn. One camp lit up the thread with righteous fury: if a company moving money can’t send a compliant email in 2026, what else is off? Others piled on the wider trend, calling this the “corposphere” in action — glossy surfaces, broken guts, and support scripts tackling real bugs with flowcharts. An IT crowd fave even dropped an xkcd 806 nod to the tech support bingo vibes. Not everyone agreed. A contrarian voice swore “their emails do arrive tho?” and hinted the recipient setup might be the problem. Meanwhile, jokers went full infomercial spoof — “Pay €49.99/month to receive emails!” — dunking on the absurdity. Practical types offered escape hatches: try Adyen for the Greek instant-pay system IRIS, since Google’s guidelines are crystal clear about rejecting non‑compliant mail. The mood? Equal parts comedy roast and existential worry about European fintech reliability, with users wondering if this is a one-off blip or a symptom of something bigger.

Key Points

  • Google Workspace rejected Viva.com’s verification emails due to a missing Message-ID header (bounce 550 5.7.1).
  • Message-ID is a required email header under RFC 5322 (since 2008) and RFC 2822 (since 2001).
  • The verification email did not arrive to a Google Workspace-hosted address but did arrive when using a personal @gmail.com address.
  • The author reported the issue with detailed logs; Viva.com support responded that the account was verified and indicated no problem.
  • The author relies on Viva.com because it supports the Greek instant-payment system, while Stripe does not currently support it.

Hottest takes

"This isn't an engineering problem, it's an ITIL problem." — iso1631
"Do you want to enable receiving email for viva.com? sign up for VibeCodedSAAS for E49.99/month" — cl0ckt0wer
"Their emails do arrive tho?" — that_guy_iain
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.