2 Answers
- Newest
- Most votes
- Most comments
0
Hi THere
Please see https://docs.aws.amazon.com/ses/latest/dg/creating-identities.html
However, keep in mind that an email address identity that's using the inherited verification from its domain is limited to straightforward email sending. If you want to do more advanced sending, you'll have to also explicitly verify it as an email address identity. Advanced sending includes using the email address with configuration sets, policy authorizations for delegate sending, and configurations that override the domain settings.
Are you overriding any domain level settings or using advanced sending features?
0
Can you double check that the domain status is verified?
https://docs.aws.amazon.com/ses/latest/dg/creating-identities.html#verify-domain-procedure
Also please review the sending limits for new accounts. While in sandbox, you also need to verify the RECIPIENT email as well.
https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html
Hi Matt, thanks for your reply. Yes, I've double check and domain shows successfully verified already. Also my sending limit is 250k per 24hour period.
Relevant content
- Accepted Answerasked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
what is this "email address identity that's using the inherited verification from its domain is limited to straightforward email sending" means ya? I don't get it.
And also I don't think that I touch anything from the domain level setting or using any advanced sending feature. I just simply create a new identity and add new domain/email address.
Hi Matt-B, I'm still waiting for your reply. I still don't get it what is the purpose verify domain if we still need to verify each email from that domain.