Reason: There was an error while attempting to deliver your message with [Subject: "Re: Senior DevOps profile"] to firstname.lastname@example.org. MTA p3plsmtpa12-03.prod.phx3.secureserver.net received this response from the destination host IP - 188.8.131.52 - 550 , 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.com] did not 550-5.7.26 pass with ip: [184.108.40.206]. 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. i12-20020ac85e4c000000b003f549b996a6si7163691qtx.786 - gsmtp
To set up SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) for your GoDaddy email using Gmail to send messages, you can follow these steps:
Setting up SPF:
- Sign in to your GoDaddy account.
- Navigate to the Workspace Email section.
- Locate the email account you are using to send emails.
- Click on the “Manage” button next to the email account.
- In the email account settings, find the section for “Email Authentication.”
- Enable the SPF authentication by selecting the option to “Enable SPF.”
- Save the changes to apply the SPF configuration.
Setting up DKIM:
- Sign in to your Gmail account.
- Click on the gear icon in the top right corner and select “Settings” from the dropdown menu.
- Go to the “Accounts and Import” or “Forwarding and POP/IMAP” tab.
- Under the “Send mail as” section, find the email account you want to configure DKIM for and click on the “edit info” link.
- In the popup window, scroll down to the “Signing Settings” section.
- Enable the “Sign messages with DKIM” option.
- Save the changes to apply the DKIM configuration.
After you have set up SPF and DKIM, the authentication records will be automatically added to your DNS settings. It may take some time for the changes to propagate across the internet. Once the DNS changes have propagated, your emails should be properly authenticated with SPF and DKIM, reducing the chances of them being blocked or marked as spam due to authentication failures.