Cannot send the confirmation email using the data you provided.

Discussion in 'Common issues' started by MarioG, Feb 6, 2019.

  1. MarioG

    MarioG New Member

    Joined:
    Feb 5, 2019
    Messages:
    2
    Likes Received:
    1
    S.E:
    Expired
    L.T:
    Regular
    L.C:
    1
    Hello,

    I have a similar issue as this one: https://forum.mailwizz.com/threads/...-send-the-confirmation-email.5712/#post-36841
    Unfortunately, no solution is provided.

    The user has full access ses and sns

    upload_2019-2-6_14-52-49.png

    When I'm trying to validate the server using ses api, I get the message in the title followed by this:

    • 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>db1b7aa6-2a1d-11e9-b84e-dd049218162c</RequestId>
      </ErrorResponse>

    Ayy idea what am I doing wrong? Thank you
     
  2. twisted1919

    twisted1919 Administrator Staff Member

    Joined:
    Dec 27, 2014
    Messages:
    10,264
    Likes Received:
    2,383
    @MarioG - Make sure your server uses NTP which is turned on and keeps the time in sync.
    Secondly, the access key and secret must be generated after the user has been created and the power user policy attached to it.
    if you do this, there's no reason for it to fail.
     
  3. MarioG

    MarioG New Member

    Joined:
    Feb 5, 2019
    Messages:
    2
    Likes Received:
    1
    S.E:
    Expired
    L.T:
    Regular
    L.C:
    1
    Okay, it is working now. I'm not sure what I was doing wrong, I started from scratch, in my case was not the NTP. In case someone else has similar issues, those are the steps I followed in order to make it work:

    1. Go to https://console.aws.amazon.com/ses/

    2. Click on SMTP settings

    3. Create my smtp credentials – this will create a new user. Keep in mind that your SMTP user name and password are not the same as your AWS access key ID and secret access key. Do not attempt to use your AWS credentials to authenticate yourself against the SMTP endpoint.

    4. Go to https://console.aws.amazon.com/iam/home

    5. Click on Users

    6. Click on the new creates used (something like ses-smtp-user.908743967-213124

    7. Add the PowerUser policy and the required permissions SES and SNS services – with full access, select all the permissions for both SES and SNS

    8. Once you added the policy and permissions, click on Security Credentials tab

    9. Create an access key – this is the key and the secret that should be used when you setup a new delivery server.
     
    twisted1919 likes this.

Share This Page