Can't make Amazon SES work

Daniel

Daniel

New Member
Hi,

Recently purchased maillwizz, seems legit so far. Problem is I've been trying to verify a Delivery Server using Amazon SES.

What I have done so far:
1. Validated SES account.
2. Verified domains.
3. Created an user in IAM manager.
4. Filled up fields in Mailwizz.

But everytime I try to verify it, it says something like:

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.
The Canonical String for this request should have been
'POST
/
host:email.us-west-2.amazonaws.com
x-amz-date:20170614T005930Z
host;x-amz-date
c9c1ad63c7ab57b4c1ce8b97b80fa7b99dd7651b4f2b65844ceb1cef96c4155a'
The String-to-Sign should have been
'AWS4-HMAC-SHA256
20170614T005930Z
20170614/us-west-2/ses/aws4_request
302a80abdda04718b57eedbae0be62e106221e79c11f9ddc2afedd9a21568589'

I've tried everything, googl'ed everywhere. Any ideas? Thanks.
 
Mine has completely refused to work with Amazon SES...I'm literally pulling my hair off!

  • 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>41ad9456-4f07-11e8-b65f-b7703d27cc9b</RequestId>
    </ErrorResponse>
Please help!
 
@Alex Bengo - This usually happens because the time on your server is way off and amazon cannot match the signature because of this.
I advise you to install NTP on your server and use it, then try again.
 
I just setup mailwizz on shared hosting and trying to setup AWS SES delivery server. Here is my error while trying to velidate server.
  • Connection could not be established with host email-smtp.us-west-2.amazonaws.com [Connection timed out #110]
    Log data:
    ++ Starting Swift_SmtpTransport
    !! Connection could not be established with host email-smtp.us-west-2.amazonaws.com [Connection timed out #110] (code: 0)
I already setup AWS SES, verify domain, verify email, created AWS IAM master user for mailwizz and setup SMTP credential.
Any help would be good for me.
 
soham navadiya said:
Connection could not be established with host email-smtp.us-west-2.amazonaws.com [Connection timed out #110]
Click to expand...
This usually indicates that your hosting is blocking outgoing connections on the given port for the given hostname.
Try using amazon ses web api in mailwizz and see if that helps, if not, either try another service or another host.
 
I don't see an option for AWS SES WEB API. Please review the attached image to see the possible option. For AWS SES I selected Smtp Amazon.
 

Attachments

  • 1.png
    1.png
    114.9 KB · Views: 24
Now I installed mailwizz on dedicated ubuntu server (digital ocean). I configured AWS SES setup. During email validation receiving following error.

  • Failed to authenticate on SMTP server with username "XXXXXXXXXXXX" using 2 possible authenticators
Is there any tutorial where I can see exact steps for AWS SES seup with mailwizz. Please share it.
 
@soham navadiya - We don't do server setup advices here, but to make your life easier, use a newer version of php and use amazon ses web api, it's way simpler and does bounce processing automatically.
 
@twisted1919 Solved my issue. Problem is that the delivery server configuration parameter is misguiding. By looking name it indicates AWS access key and a secret key is required. But it should be SMTP Access key and SMTP Secret key.
 
soham navadiya said:
@twisted1919 Solved my issue. Problem is that the delivery server configuration parameter is misguiding. By looking name it indicates AWS access key and a secret key is required. But it should be SMTP Access key and SMTP Secret key.
Click to expand...
Isn't this the same thing, the keys that you get when you create a new amazon user and the generate keys for it ?
 
@twisted1919 No, it is not the same. One key pair is for AWS account and another is SMTP key pair (for service). So it should be SMTP username and SMTP Password.

If possible then publish youtube video tutorial for setup AWS SES. bcoz nowadays AWS sends mail on very low cost. So many agencies want dedicated setup for their organization and AWS SES provides a very low-level feature. So it will be great for mailwizz if you share the video tutorial on youtube.
 
Last edited:
  • 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>7db0ad71-b68b-11e8-84fc-f738f59809ca</RequestId>
    </ErrorResponse>
 
You must log in or register to reply here.
Back
Top