Can't make Amazon SES work

i aint created iam user after creating user and allows required policies make it worked, thanks twisted1919, by the way why twisted followed by 1919
 
Hi everyone, I was facing the same issue that I was using IAM user AWS ACCESS KEY and PASSWORD. But for configuring SMTP with Mailwizz we have to only use SMTP ACCESS KEY and SMTP SECRET KEY

The process to create SMTP Keys in AWS SES:
1. SMTP Settings
2. Click on Create My SMTP Credentials
3. Type your username or use default
4. AWS will auto-create SMTP ACCESS KEY and SMTP SECRET KEY

NOTE: You can not preview SMTP SECRET KEY again so download credentials for future use. Thank You :)
 
Hello,

Anyone knows what error is this? We've tried changing the server timezone to UTC but still showing the same error.

Error executing "SendRawEmail" on "https://email.ap-southeast-1.amazonaws.com"; AWS HTTP error: Client error: `POST https://email.ap-southeast-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): Signature expired: 20231026T012421Z is now earlier than 20231026T012625Z (20231026T013125Z - 5 min.) - <ErrorResponse xmlns="http://ses.amazonaws.com/doc/2010-12-01/"> <Error> <Type>Sender</Type> <Code>SignatureDoesNotMatch</Code> <Message>Signature expired: 20231026T012421Z is now earlier than 20231026T012625Z (20231026T013125Z - 5 min.)</Message> </Error> <RequestId>191a9b1a-cdc1-4623-ad9c-39374a0a58b3</RequestId> </ErrorResponse>
 
But this only happen in one user. Another user under the same server and using the same SMTP got no issue with the sending.
Is it because we are using "Custom subscriber attachment" extension?
This is not because of the extension, this error comes when you try to validate the server and from the error message it seems to be an error related to amazon credentials, check if you insert correct Secret Access Key.
 
I'm sure this is not related to Amazon credentials because some of it still can be send out, And some of it suddenly "Giveup" with the error mention above.
Please open support ticket and give us access to your mailwizz app (url app, email, password).
 
@under - If you make use of that setting, I think MailWizz will not be able to properly process the bounces and complaints, that's what I meant.
 
Back
Top