Cannot verify, already verified domain?

  • Resolved Mat Gargano

    (@matstars)


    3 years ago

    Using 1.6.3

    My access keys ARE correct. Both old and new.

    I swapped out a client’s AWS keys for another set of AWS keys, and now when I try to send an email I get:

    Error executing "SendEmail" on "https://email.us-east-1.amazonaws.com/v2/email/outbound-emails"; AWS HTTP error: Client error: POST https://email.us-east-1.amazonaws.com/v2/email/outbound-emails resulted in a 400 Bad Request response: {"message":"Email address is not verified. The following identities failed the check in region US-EAST-1: noreply@{redacted.com} (truncated…) MessageRejected (client): Email address is not verified. The following identities failed the check in region US-EAST-1: noreply@{redacted}.com - {"message":"Email address is not verified. The following identities failed the check in region US-EAST-1: noreply@{redacted}.com"}

    I tried launching the setup wizard, entered {redacted}.com as the domain and when I get to Step 4 and click “Next: Complete Verification” nothing happens (apparently) and i look at the Network tab in inspector and see that the admin-ajax.php call returns:

    {"errors":{"204":["Email identity{redacted}.com already exist."]},"error_data":[]}

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Delicious Brains Support

    (@dbisupport)

    3 years ago

    Hi Mat,

    WP Offload SES Support Team here. Thanks for reaching out with your query, we would be happy to assist!

    It looks like this is the 2nd ticket about this issue we have received. But we want to double check. If you dismiss that message, and then send another email from the site, does that error come back up?

    Please also check our documentable below to see if it helps. If your debug.log file is already enabled, are there anymore errors coming from SES or AWS?

    https://deliciousbrains.com/wp-offload-ses/doc/sender-verification-errors/

    Thread Starter Mat Gargano

    (@matstars)

    3 years ago

    If you dismiss that message, and then send another email from the site, does that error come back up?

    The message is NOT dismissable.

    Once I get this error if I try to resend an email, it does not send.

    —

    I have error logging enabled, I use SpinupWP which manages my instances which automatically pipes errors to a log, the only error is:

    [11-May-2023 19:55:52 UTC] WP Offload SES #202: There was an error attempting to send your email. (Error executing “SendEmail” on “https://email.us-east-1.amazonaws.com/v2/email/outbound-emails”; AWS HTTP error: Client error: POST https://email.us-east-1.amazonaws.com/v2/email/outbound-emails resulted in a 400 Bad Request response:

    {“message”:”Email address is not verified. The following identities failed the check in region US-EAST-1: noreply@{redacted} (truncated…)

    MessageRejected (client): Email address is not verified. The following identities failed the check in region US-EAST-1: noreply@{redacted} – {“message”:”Email address is not verified. The following identities failed the check in region US-EAST-1: noreply@{redacted}”})

    Please advise.

    Plugin Support Delicious Brains Support

    (@dbisupport)

    3 years ago

    Hi there!

    Thanks for the update!

    That error happens when your site sends an email from an email address that hasn’t been verified with your AWS account. You can either verify the email address provided in the error details in the Verified Senders tab, or you can change the email address to one that is verified.

    Since you’ve already attempted to verify the domain from the Setup Wizard and nothing happened, could you please instead try to verify via the Verified Senders Tab on the Settings Page of WP Offload SES and click the ‘+ Add New’ button.

    If you’re not sure where that email address is being used on your site, it may be worth checking any other plugins to see if they are configured to send emails from that address. Another common reason we see is a contact form plugin configured to send emails as the form submitter instead of the website owner.

    Please let us know how that goes.

    Thread Starter Mat Gargano

    (@matstars)

    3 years ago

    I do not want to verify an email address. I want to verify a domain.

    When I go through the verified list I do not see anything @{redacted}.com. What email address was verified?

    Again, I want to verify the domain.

    Plugin Support Delicious Brains Support

    (@dbisupport)

    3 years ago

    Hi @matstars,

    Thank you for the clarification. We can’t tell what email was verified. But can you kindly try verifying the domain directly on AWS, and see if it succeeds?

    jpandino

    (@jpandino)

    3 years ago

    I have a similar issue with a domain already verified in AWS. My access keys are correct, but it doesn’t seem to be authenticating. Last time accessed it’s never. On the same site I used different access keys (which I know worked for another site I implemented this plugin where the domain was not already verified) from a different AWS account and still cannot move forward validating the domain.

    Plugin Support Delicious Brains Support

    (@dbisupport)

    3 years ago

    Hi @jpandino,

    We’ve responded to the ticket you created related to this issue. Kindly check and we’ll wait for your updates there.

    Plugin Author Delicious Brains

    (@deliciousbrains)

    3 years ago

    This was fixed in v1.6.5.

    After upgrading, please dismiss the unverified email address error notice. If it comes back later, that will hopefully not be a false positive and should be looked into.

    -IJ

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Cannot verify, already verified domain?’ is closed to new replies.