Error 512 SignatureDoesNotMatch

Same here and I am certain credentials are correct.

I gave up and went with another option, SendGrid. One star app for me.

Solved it after solving the confusion the AWS documentation caused. First of all in AWS SES there’s a section about SMTP credentials which refer to: https://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-credentials.html

DON’T USE THAT. Solution is very simple:

1. Create regular AWS IAM user with Programmatic access
2. Create policy with following JSON<br>

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "VisualEditor0",
               "Effect": "Allow",
               "Action": [
                   "ses:SendEmail",
                   "ses:VerifyEmailIdentity",
                   "ses:GetSendQuota",
                   "ses:SendRawEmail",
                   "ses:GetSendStatistics",
                   "ses:DeleteIdentity",
                   "ses:ListIdentities"
               ],
               "Resource": "*"
           }
       ]
   }

   <br><br>Note: This is stated in the plugin settings page

3. Use both keys to authenticate and it works

Just for completeness I came to the solution after reading which clarified the credential-riddle I fall victim to: https://github.com/boto/boto/issues/476

Kind regards
Mike

hello, do you think that my problem is related ?

Error : [512] SimpleEmailService::sendEmail(): Sender – MissingAuthorizationSchemeParameter: Signature is not found Request Id: 3e33f2c6-d1ce-11e8-92c6-4deb12af71a2

https://www.ads-software.com/support/topic/error-512-simpleemailservicesendemail-sender-missingauthorizationsche/

@mikeg_de Should I try your solution ?

Thanks a lot.

@blliem, yes, follow my steps to create a regular IAM user using CLI access. Do NOT use the feature in SES to create a user, that will make you run into trouble. I’ve just reconfirmed it.