Major European payment processor can't send email to Google Workspace users
1–10 of 443 posts
Re: Major European payment processor can't send email to Google Workspace users
#2Re: Major European payment processor can't send email to Google Workspace users
#3Re: Major European payment processor can't send email to Google Workspace users
#4Do you want to enable receiving email for viva.com? sign up for VibeCodedSAAS for E49.99/month
I just hope my OpenClaw skills registry doesnt have malware anymore. I sure trust my supply chain of vibecoded software!
Re: Major European payment processor can't send email to Google Workspace users
#5Sadly I doubt their system is xkcd806 compatible ether.
This isn't an engineering problem, it's an ITIL problem. To be fair 99% of these complaints will be dealt with by the flow chart. Sadly people on the front line are either not knowledgable enough or not empowered enough to bust out of that straightjacket.
Re: Major European payment processor can't send email to Google Workspace users
#6Re: Major European payment processor can't send email to Google Workspace users
#7Re: Major European payment processor can't send email to Google Workspace users
#8[flagged]
I wonder what google workspace support said.
Re: Major European payment processor can't send email to Google Workspace users
#9> ...
> `Message-ID` is one of the most basic required headers in email.
Section 3.6. of the RFC in question (https://www.rfc-editor.org/rfc/rfc5322.html) says:
+----------------+--------+------------+----------------------------+
| Field | Min | Max number | Notes |
| | number | | |
+----------------+--------+------------+----------------------------+
| | | | |
|/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
... bla bla bla ...
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/|
| message-id | 0* | 1 | SHOULD be present - see |
| | | | 3.6.4 |
|/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
... more bla bla ...
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/|
| optional-field | 0 | unlimited | |
+----------------+--------+------------+----------------------------+
and in section 3.6.4: ... every message SHOULD have a "Message-ID:" field.
That says SHOULD, not MUST, so how is it a requirement?Re: Major European payment processor can't send email to Google Workspace users
#10"Major European Payment Processor" really just translates to "Major European Incompetence Center".