DKIM issue not sure if relevant

Question

Hello. I received the following email shortly after I changed hosting providers for my email. I had a contractor add the new DNS records to the new hosting provider. I am not sure what to do, because I checked and I don't have Amazon SES. I set up this account many years ago to be integrated with another software I have, so maybe this email is irrelevant? Please let me know you think.
-----
We detected that the DNS records required for the DKIM setup of () are no longer present in your DNS settings.

To protect your email deliverability, we have temporarily disabled DKIM signing for emails originating from (). If you use Amazon Pinpoint to send mail through this domain, those emails will also be affected.

If the removal of the DNS records was intentional, you do not need to take any additional action. In 5 days, () will no longer be considered to be configured for the purpose of DKIM signing.

If it was unintentional, please restore the DNS records to your DNS settings within 5 days. Once we confirm the presence of the DNS records, we will re-enable DKIM signing.

Please note that the settings for individually verified email addresses override domain-level settings. For example, if you enable DKIM signing for a verified domain but disable DKIM signing for a verified email address in that domain, then emails from that email address will not be DKIM-signed.

re:Post Agent · Answer

The email you received is indeed relevant and important, even if you don't actively use Amazon SES (Simple Email Service) or Amazon Pinpoint. This message indicates that there's an issue with your DKIM (DomainKeys Identified Mail) configuration, which is crucial for email authentication and deliverability.

DKIM is an email security standard that helps prevent email spoofing and improves the likelihood of your emails reaching the intended recipients' inboxes. The message suggests that the required DNS records for DKIM are no longer present in your DNS settings, likely due to the recent change in hosting providers.

Here's what you should do:

1. Check with your contractor who added the new DNS records to ensure they didn't accidentally remove or forget to add the DKIM records.

2. If the DKIM records were unintentionally removed, work with your new hosting provider to restore the correct DKIM DNS records within the next 5 days. This will allow Amazon to re-enable DKIM signing for your domain.

3. If you're unsure about which records to add, you may need to contact the support team of the software you integrated with years ago, as they might have set up the DKIM configuration through Amazon SES.

4. If you no longer use the service that originally set up DKIM through Amazon SES, you might choose to let the DKIM configuration expire. However, this could negatively impact your email deliverability.

5. Review your email sending practices and ensure you're using proper authentication methods to maintain good deliverability.

Remember, even if you don't actively use Amazon SES, the DKIM configuration tied to your domain is still important for your overall email reputation and deliverability. It's best to address this issue promptly to ensure your emails continue to be properly authenticated and delivered.  
**Sources**  
[Troubleshooting DKIM problems in Amazon SES - Amazon Simple Email Service](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/troubleshoot-dkim.html)  
[DkimAttributes - Amazon Simple Email Service](https://docs.aws.amazon.com/ses/latest/APIReference-V2/API_DkimAttributes.html)  
[Authenticating Email with DKIM in Amazon SES - Amazon Simple Email Service](https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-dkim.html)

DKIM issue not sure if relevant

Add your answer

Relevant content