-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SignatureDoesNotMatch error #31
Comments
The same issue. It seems to me that SES has changed API and we have this error now... |
Could be that Amazon recommends not using your Access Key and Secret to send via SMTP. From their SMTP Settings page... "Note: Your SMTP credentials are not the same things as your AWS access key ID and secret key! Never supply your AWS credentials in response to any requests for SMTP usernames and passwords - use your SMTP credentials instead." I am successfully using my access key ID and secret but am considering not using the gem and changing my setup to use my SMTP credentials. Would love to see the gem update. |
Any update on this? |
Got it. You need to use AWS access keys, found here: Here's a guide to getting the access keys: |
Would it be possible to modify the aws-ses gem so we use the SMTP credentials rather than the AWS credentials (or give a choice to use one or the other?) Is there any chance that Amazon may disallow using AWS credentials in the future? |
If you want to use SMTP, then there is no need at all for the aws-ses gem, Just use the normal mail gem and connect via smtp like you would any other On Sep 10, 2013, at 2:00 AM, Johnny Shields notifications@github.com Would it be possible to modify the aws-ses gem so we use the SMTP — |
Ah OK got it, thanks! Sorry I'm a bit of a newbie to this... |
I'm using this gem with rails 3.1.1 and whatever I do I keep getting error:
AWS::SES::ResponseError (SignatureDoesNotMatch - 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.)
I'm sending this using the ActionMailer configuration option
The text was updated successfully, but these errors were encountered: