Google blocking email sent via ISP's SMTP server because of SPF and DKIM ERROR

[Freedom13]

Emails sent to gmail email addresses are not being delivered with an error that it is permanent. Hosting Company support do not seem to understand the rejection email which I have included here,
gmail-smtp-in.l.google.com[2404:6800:4003:c06::1b] said: 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 [xxxxxxxxxx.com.au] did
550-5.7.26 not pass with ip: [2403:5800:3:25::1001]. 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.
y187-20020a638ac4000000b00524f3526a91si2729685pgd.16 - gsmtp (in reply to
end of DATA command)
The software being used does not allow me to change the SMTP server from the ISP's to the Domains SMTP server. This fact seems to be the cause of the problem.
I have followed the link to support.google but are not able to come to grips with what should be included in the SPF and DKIM records to solve the problem.
I am looking for specific help with the text required to edit the SPF and DKIM records in that will solve the issue.
Thanks

 

[quietFinn]

Add these to your domain's SPF record:
include:spf1.aussiebroadband.com.au include:spf2.aussiebroadband.com.au

 

[Freedom13]

Thanks for the information. I have asked the Hosting company to add it to the SPF record as suggested. How can I check that it has actually been add. When I have a look at the SPF record I can only see one line and cannot seem to view any thing else. I get this message:- This system does not control DNS for the “yoogalivet.com.au” domain. You can install the suggested “SPF” record locally. However, this server is not the authoritative nameserver. If you install this record, this change will not be effective. Contact the person responsible for the “ns4.secureparkme.com” and “ns3.secureparkme.com” nameservers and request that they update the “SPF” record with the following:
As I am having trust issues with the Support department of the Hosting company how can I check to see if they have actually added the suggested line to the SPF record.
Thanks in advance.
Richard

 

[cPRex]

You wouldn't be able to see the record inside cPanel, as the DNS isn't managed there. You could use an online tool such as SPF Check & SPF Lookup - Sender Policy Framework (SPF) - MxToolBox or a manual query on the command line of "dig TXT domain.com" to see that full record.

 

[Freedom13]

I have used the SPF checker on mxtoolbox.com but cannot see any reference to your suggested addition of spf1.aussiebroadband.com.au include:spf2.aussiebroadband.com.au.
Am I missing some thing. Here is the current SPF record
v=spf1 +a +ip4:121.200.0.92 +mx include:all._spf.ds.network ~all
Thanks

 

[cPRex]

That would indicate your host hasn't made the change yet, or the DNS hasn't had enough time to propagate.

 

[quietFinn]

That would indicate your host hasn't made the change yet, or the DNS hasn't had enough time to propagate.

MxToolBox SPF Checker gets the SPF record from the actual nameserver, so any changes are immediate.

 

[Freedom13]

Hi to cPRex.
I wanted to reach out to you to thank for your quick response which was very accurate and after I convinced the Domain Hosting company to edit the SPF Record the problem went away completely. I waited 10 days so the client had time to test thoroughly before I advised the domain host to close the support ticket.
I feel that I should tell everybody about the poor support /i received from the Domain Hosting company but would not do so prior to getting some confirmation from the Forum that it was OK to do so.
Thank you once again cPRex for you advice

 

[cPRex]

You're very welcome. As far as naming the host, that's entirely up to you. I do try and limit the number of "bashing" or "agenda" threads, but you might find more results talking about the actual hosting at a place like WebHostingTalk.