Gmail bouncebacks

Starting November 2022, Google's policies state that all new inbound senders to Google Workspaces (including gmail.com) will need to have email authentication set up on the sending domain.

You may have received an email bounce back with the following content:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error.

The following address failed:

    [EMAIL]@gmail.com:
        SMTP error from remote server for TEXT command, host: gmail-smtp-in.l.google.com (108.177.126.26) reason:

550-5.7.26 This mail is unauthenticated, which poses a security risk to the
550-5.7.26 sender and Gmail users, and has been blocked. The sender must
550-5.7.26 authenticate with at least one of SPF or DKIM. For this message ,
550-5.7.26 DKIM checks did not pass and SPF check for [<domain.tld>] did not pass with ip: [1.1.1.1]. The sender should visit
550-5.7.26  https://support.google.com/mail/answer/81126#authentication for
550 5.7.26 instructions on setting up authentication.

We support the Sender Policy Framework (SPF) which helps receiving mail platforms confirm that the host sending an email is authorised to send mail for your domain.

You can add an SPF record for your domain with a TXT record in your domains DNS Zone file, below are the common SPF records you can use with Heart Internet services:

A domain name cannot have more than one SPF record, so if you use multiple service providers, only include elements of the SPF record examples below to ensure your other services are also authenticated.

eXtend/Reseller Shared Hosting

v=spf1 include:soverin.net include:secureserver.net exists:%{i}.mta.spf.extendcp.co.uk exists:%{i}.web.spf.extendcp.co.uk -all

GoDaddy cPanel / GoDaddy VPS

v=spf1 include:secureserver.net -all

We also have a comprehensive list of all SPF records in the following article:

https://www.heartinternet.uk/support/article/how-do-i-add-spf-records-to-my-site.html