Amazon Ses Erro

N

Nasir Qureshi

New Member
  • Here is a transcript of the error message:
  • Error executing "SetIdentityFeedbackForwardingEnabled" on "https://email.us-east-1.amazonaws.com"; AWS HTTP error: Client error: `POST https://email.us-east-1.amazonaws.com` resulted in a `403 Forbidden` response:
    <ErrorResponse xmlns="http://ses.amazonaws.com/doc/2010-12-01/">
    <Error>
    <Type>Sender</Type>
    <Code>SignatureDo (truncated...)
    SignatureDoesNotMatch (client): The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. - <ErrorResponse xmlns="http://ses.amazonaws.com/doc/2010-12-01/">
    <Error>
    <Type>Sender</Type>
    <Code>SignatureDoesNotMatch</Code>
    <Message>The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.</Message>
    </Error>
    <RequestId>8a9a9ae5-b68a-11e8-997d-a9497cb5a0b3</RequestId>
    </ErrorResponse>
Installed on cantabo, installed only amazon ses is not validating, added full access and nothing works. please advice.
 
You need to generate the access keys for your IAM user AFTER you have given it the power access permissions. That's the important bit.
You also need to have ntp installed and enabled on your server to make sure your time stays in sync. Restart php after you enable ntp.
 
VPS restarted, php and ntp active, roles were given already

https://prnt.sc/ktkwvy
https://prnt.sc/ktkxcv

Still getting error.

  • Cannot send the confirmation email using the data you provided.
  • Here is a transcript of the error message:
  • Error executing "SetIdentityFeedbackForwardingEnabled" on "https://email.us-east-1.amazonaws.com"; AWS HTTP error: Client error: `POST https://email.us-east-1.amazonaws.com` resulted in a `403 Forbidden` response:
    <ErrorResponse xmlns="http://ses.amazonaws.com/doc/2010-12-01/">
    <Error>
    <Type>Sender</Type>
    <Code>SignatureDo (truncated...)
    SignatureDoesNotMatch (client): The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. - <ErrorResponse xmlns="http://ses.amazonaws.com/doc/2010-12-01/">
    <Error>
    <Type>Sender</Type>
    <Code>SignatureDoesNotMatch</Code>
    <Message>The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.</Message>
    </Error>
    <RequestId>1e66fc4b-b698-11e8-b57d-dd973c97b919</RequestId>
    </ErrorResponse>

I did a lot of time corrected but this time don't know what is the issue.
 
You are doing it wrong then.
1. Create new iam user.
2. give it power user access
3. generate new api keys
4. use them in mailwizz.
That simple. Follow the steps and it will work.
 
You must log in or register to reply here.
Back
Top