Amzone SES not working


New Member
can's seem to get the Amazone webapi working . followed the tutorial ste; by step.

chose Amazone webapi when createinmg a new delivery server.
my user name is AKIAJVEJK.........
i also created a pasword for the user created as show in the video
As hostname i took

I also dont see an option to fill in the api key.

this is the error transcript
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
The String-to-Sign should have been

what can i do ?
you wrote to dan o shea regarding this problem "and then use the newly generated keys into mailwizz"
were can i insert the kyes i only see a username
i found and it seems to skip that error but now i am getting:
  • Identity info@[domain] is invalid. Must be a verified email address or domain.
but my email address is in the verified email list
Identity info@[domain] is invalid. Must be a verified email address or domain.
This message comes directly from the amazon servers, so it's either you are using a wrong region in mailwizz or your email address is not verified. You should check both and make sure the email address is verified for the region you use inside mailwizz.
Hi twisted1909
It could be an issue that Mailwizz always requires a verified email address when using Amazon SES. This is not correct because we can use a verified domain instead. i.e. once you have verified a domain with Amazon SES, you can send from any address within that domain and you do not have to verify every individual email. Could you please provide a fix for this?

For your reference, this is the message from Amazon SES I received after successfully verifying a sending domain:
Congratulations! The Amazon SES verification process for the domain in region US West (Oregon) is now complete. You are now able to send email through Amazon SES from any address within this domain. For more information, please refer to the Amazon SES Developer Guide.

Thank you for using Amazon SES.
Last edited:

I am aware of the domain validation step, but we can't detect that from mailwizz, so i am really not sure how to go about this at this point in order to keep compatibility. For now your best bet is still using a verified email address.
I've made a quick-and-dirty fix for the problem: use domain as Identity instead of email address. For example, replace
'Identity' => $this->from_email,
'ForwardingEnabled' => true,
'Identity' => substr(strrchr($this->from_email, "@"), 1), // extract domain from email
'ForwardingEnabled' => true,

This is because 'Identity' can accept either email address or domain name as suggested in AWS docs:

Please consider this in the next release of Mailwizz. And you may need to change the "Add Delivery Server" form for Amazon SES Web API to allow user to enter verified domain.
@Nghi - Thanks for the info.
In your code you enable forwarding, why is that? Mailwizz creates and handles the sns topic automatically, so is there any particular reason ?
I did not actually understand what the setting meant and why it was there. I just tried to fix the Amazon SES verification issue by replacing email address with a domain name for the "Identity" parameter. Again, this is just a quick-and-dirty fix for my own purpose, Mailwizz should detect available verified domains from Amazon SES and use one of those for sending (the one that matches the From email address provided by user). It should only raise an error when the provided email address does not match any verified domain.
One more thing with Amazon SES: it seems that Mailwizz always disregards the From email address provided by user when creating a campaign, it always uses the default one for the delivery server. Could you please take a look?
@Nghi - This is the exact problem, with amazon ses the email in the FROM has to be verified in order for amazon to allow sending.
This gets us back to the domain verification thing. Even if you verify your domain and mailwizz will allow you, when a campaign is sent with custom from set from campaign itself, then delivery will fail miserably.
@twisted1919, I think we should anyway respect custom From header and somehow handle this for users. I understand this is something that is very annoying to fix because mail sending occurs in the background and may be balanced between different delivery servers. Look forward to a solution in the future release.
Sorry to be repetitive, but this means i can't allow my users to send "From their own email" with SES?

@Aron Prins - This is correct, unfortunately. You need to add their email in Amazon then create a delivery server for that email address, this is the only way it will work.