Delivering email to Gmail

Suggest Edits

For new messages to successfully be delivered to Gmail accounts, it is recommended that you review the SPF/TXT records on your domain. Starting November 2022 Google may randomly performs checks on new sender messages to Gmail accounts. This is to verify that the sender is authenticated with either an SPF or DKIM record. This is not a requirement for existing senders to personal Gmail account, however new Senders who send emails without an SPF or DKIM method will be rejected or marked as spam.

Example Bounceback
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(es) failed: [email protected] host gmail-smtp-in.l.google.com [74.125.130.27] SMTP error from remote mail server after end of data: 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 [example-domain.com.au] 550-5.7.26 did not pass with ip: [1809.0311.1815.1212]. 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. y17-20020a17090322d100b001a654cdcce0si31054240plg.103 - gsmtp

Example Bounceback

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(es) failed: [email protected] host gmail-smtp-in.l.google.com [74.125.130.27] SMTP error from remote mail server after end of data: 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 [example-domain.com.au] 550-5.7.26 did not pass with ip: [1809.0311.1815.1212]. 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. y17-20020a17090322d100b001a654cdcce0si31054240plg.103 - gsmtp

If you are getting this bounceback, you will need to add the server/IP address that did not pass as part of your SPF record. We have an article here for adding SPF/TXT records.

Below is an example of what you would need to add in your SPF/TXT. Please be advised that this is only a guide and you will need to validate your own SPF/TXT record syntax. Ensure that you have made a copy of your SPF/TXT records before attempting this change.

ip4:192.168.1.1 (This is just an example IP Address that did not pass)

Email platform	Default SPF	Edited SPF
Cloud	v=spf1 mx ip4:202.124.241.204 ~all	v=spf1 mx ip4:192.168.1.1 ip4:202.124.241.204 ~all
cPanel	v=spf1 +mx +a +include:_spf.server-cpanel.com ~all	v=spf1 +mx +a ip4:192.168.1.1 +include:_spf.server-cpanel.com +include:relay.mailchannels.net ~all
OX-Mail	v=spf1 a mx include:_spf.wcg-mail.com ~all	v=spf1 a mx ip4:192.168.1.1 include:_spf.wcg-mail.com ~all
Office 365	v=spf1 include:spf.protection.outlook.com -all	v=spf1 ip4:192.168.1.1 include:spf.protection.outlook.com -all

If you have attempted to add the IP address SPF/TXT record and still have bounce back issues, feel free to contact our friendly customer care team.

To help our customer care team better troubleshoot this issue, please include the following when submitting your support request .

Domain : Support code : find it here Sender Address : Recipient Gmail Address: Bounce back Message :

Updated about 1 month ago