SES: DKIM configuration successful, but Identity status still "pending"

0

Hi,

I have added a domain into AWS SES a while ago, and I've entered the three CNAME records into our domain registry as requested by AWS. I have then received the email with the subject "DKIM setup SUCCESS for <domain>", and the domain was shown as verified in AWS SES. Now, the domain is shown in status "pending" again, even though the CNAME records still exist. I've looked up the three CNAME records again and again, I've checked that no typo was made and not a single character was missing, everything seems to be configured correctly. But AWS SES still shows the domain in status "pending".

I've been using the host command to verify that the CNAME record exists. For example, in the AWS console, it says that xyz._domainkey.example.com should point to xyz.dkim.amazonses.com. So I ran the command:

host xyz._domainkey.example.com

and the output is: xyz._domainkey.example.com is an alias for xyz.dkim.amazonses.com.

What could be the reason that it's still not working? Is there anything else I can do to troubleshoot this further?

I'm not sure if these two events are related, but I remember that I've tried to add an additional verified domain, which was a subdomain of the already existing verified domain. I've received an error message (I don't recall which one, unfortunately). I could be wrong, but I think that the issue with the status "pending" appeared shortly after this failed attempt to add an additional verified domain.

I am not using AWS Route 53 for the domain, in case that matters.

Thanks for any advice.

  • We just experienced same thing. Unclear whether this is a phishing attempt or if AWS has a mass email running amok. Received 8 emails each for 2 domains with the same subject line. The email continues: "You can now send DKIM-signed emails from any address within this domain through both Amazon SES and Amazon Pinpoint." Strange for these reasons:

    1. I've never sought to use SES or Pinpoint
    2. the emails were received by our non-AWS mail host, but its MX record resides on Route 53. Q: is this from AWS? if so, it's weird behavior that requires me to research. If not, AWS has been compromised
답변 없음

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠