Jaroslaw Rafa wrote: > Dnia 15.06.2022 o godz. 22:00:45 Bob Proulx pisze: > > It is interesting that mail to domains hosted at google that are not > > @gmail.com but other named domains delivered okay. Google accepted > > the exact same message to them fine. > > It can be that some domains that are actually hosting their email at Google > don't use Google MXes for incoming mail, but something different. I know at > least a few cases when companies hosting their mail at Google use for > example Proofpoint servers (*.pphosted.com) as incoming MXes for their > domains. This may be the cause of the other domain not rejecting emails > while gmail.com is rejecting the same emails.
In this case I meant that as an example that it was not the content of the message that Google did not like but the headers. We know Google is all about content analysis. Since Google accepted exactly the same message to other addresses that it is hosting it wasn't the content. And I thought it likely that at the root of the issue it was the default_destination_recipient_limit = 50 configuration which was problem where Google sometimes but not always thought 50 was too many. Not always. It often accepts it. That inconsistency of feedback from Google leads to thinking something is working reliably with Google when it is not. I think that is poor of Google. In the case of other domains being hosted at Google we have that case on this sleepy mailing list too. But when people have a domain it is most likely to have only one subscriber address there. Is there a transport mapping equivalent to match against the MX host instead of against the the recipient address? That's really what is desired here. I didn't think such a feature existed yet. Bob
