Dear supermetrics support,
our mail system rejects reports coming from supermetrics for Google Drive for seeming counterfeit.
As our IT support tells me, the reason for this is the following: MX Resource Records of the incoming mail are pointing to a Google server (e.g. https://mxtoolbox.com/SuperTool.aspx?action=mx%3asupermetrics.com&run=toolpage#), while actually being served from Amazon AWS, there the server pretends to be be supermetrics.com (helo=supermetrics.com).
According to our support this should be fixable through correcting the MX Resource Record pointing to Amazon AWS. The mails cannot be actively whitelisted, because the mail server interprets this as an configuration error.
Is this fixable?
Thank you and best regards,
We have SPF (Sender Policy Framework) records in place to define the valid sources from which supermetrics.com e-mails can originate. All servers that send Supermetrics reports should be included in the SPF. Changing the MX records is not an option as that would affect our incoming mail.
It's been a while since you reported this issue with receiving the report e-mails. Just wanted to let you know that we've revamped our report e-mail sending process during the last few weeks, and the changes should help against the issue you described. Should you need to do IP address whitelisting on the e-mail server, you can find the IP address here: https://support.supermetrics.com/solution/articles/19000064345-sender-ip-address-for-report-e-mails
Support forum: support.supermetrics.com
One question. Is 220.127.116.11 the only IP address? How can we know if there is a new IP or a new host to whitelist ? Is there an index for this?