news.volyx.in

Major European payment processor can't send email to Google Workspace users (atha.io)

609 points by thatha7777 · 158 days ago · 415 comments on HN

Article summary

A major European payment processor, Viva.com, is unable to send verification emails to Google Workspace users due to a missing Message-ID header, which is a requirement of the Internet Message Format specification (RFC 5322). The issue was discovered when the author tried to create an account on Viva.com and the verification email never arrived. The company's support team responded by stating that the issue was not a problem since the author's account had a verified email address. The author argues that this is a significant issue, as it raises questions about the company's attention to detail and ability to follow industry standards.

Main themes

  • Email headers and standards
  • Payment processing and fintech
  • Google Workspace and email delivery
  • Technical support and customer service
  • Industry standards and compliance
  • European business and technology

What commenters say

  • The missing Message-ID header is a significant issue that can cause email deliverability problems, and Viva.com should prioritize fixing it to ensure reliable communication with their users.
  • Google's decision to reject emails without a Message-ID header is justified as a measure to prevent spam, even if it means being stricter than the RFC specification.
  • The RFC specification is clear that a Message-ID header is recommended but not required, and Google's strict enforcement of this rule is not in line with the standard.
  • The issue highlights a broader problem with European fintech infrastructure, where companies may prioritize convenience over attention to detail and adherence to industry standards.
  • The lack of a Message-ID header is a minor issue that can be easily fixed, and Viva.com's support team should have been more responsive and helpful in addressing the problem.
  • The use of SHOULD in the RFC specification implies that there may be valid reasons to ignore the requirement, but in this case, Viva.com's decision to omit the header is not justified.
  • The discussion around email standards and deliverability highlights the need for a more modern and robust email system that can better handle issues like spam and security.
  • The fact that Viva.com's support team did not take the issue seriously and instead dismissed it as not a problem raises concerns about the company's commitment to customer service and technical support.