Starting November 2022 Gmail introduced a new policy which now requires email senders to be authenticated by an SPF (TXT) or DKIM record, or risk messages being marked as spam.
After the new policy was introduced last November, more and more of our customers have had their emails marked as spam, or even completely rejected, by Gmail.
Here is the official statement introduced by Google (Gmail):
Starting November 2022, new senders who send email to personal Gmail accounts must set up either SPF or DKIM. Google performs random checks on new sender messages to personal Gmail accounts to verify they’re authenticated. Messages without at least one of these authentication methods will be rejected with a 5.7.26 error, or marked as spam. This requirement doesn’t apply to you if you’re an existing sender. However, we recommend you always set up SPF and DKIM to protect your organization’s email and to support future authentication requirements.
In order to make sure, that your messages are not being marked as spam or rejected by Gmail, you will need to add our SPF (TXT) record in your DNS zone if you are using our email services.
Our SiteMail (Email) SPF value is
"v=spf1 include:mfg.siteprotect.com ~all"
Hosted Exchange 2016 SPF value is
"v=spf1 include:spf.serverdata.net ~all"
Our universal SiteMail (Email) & Hosted Exchange 2016 SPF value is:
"v=spf1 include:mfg.siteprotect.com include:spf.serverdata.net ~all"
If your domain name points to our name servers, you can use the Advanced DNS Settings tool.
If not, contact your name server provider for assistance with any DNS record changes.
Here is a brief overview of How to add new DNS records to your DNS zone.