Your software
Your problem
I just installed Mautic through Softaculous installer, it didn’t ask for any smtp, but now i can’t find any way to connect it other than trying this new Email DSN in the email settings area.
These errors are showing in the log:
Expected response code “250” but got code “554”, with message “554 5.9.2 Sender domain is not valid.”.
Steps I have tried to fix the problem:
+1 - I need help the same with postmark.
khelmerrah:
554
There might be a problem with your password. If it contains a special character it’ll cause problems ATM:
Long awaited Mautic 5 is finally here 🥳 Ready to install?
Mautic 5 comes with some significant changes. Because of at least one you might want to wait for a bit before you update—as you could, for example, accidentally destroy your sender...
Relevant GitHub issues:
opened 04:31PM - 21 Apr 23 UTC
bug
email-integrations
### Mautic Version
4.4.x series
### PHP version
8.0
### What browsers are yo… u seeing the problem on?
Not relevant
### What happened?
Pretty simple, but hard to find: if Amazon AWS SES defines a secret / password that contains a "/" it will lead to an authorization error with the plattform. The error message:
`Error executing "GetAccount" on "https://email.eu-central-1.amazonaws.com/v2/email/account"; AWS HTTP error: Client error: `GET https://email.eu-central-1.amazonaws.com/v2/email/account` resulted in a `403 Forbidden` response: {"message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access (truncated...) InvalidSignatureException (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. - {"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."}`
The problem: AWS assigns the password randomly, often it contains a "/". You can only delete the just created key and create a new one - hoping this time its without the "special" character.
### How can we reproduce this issue?
Step 1: Connect with Amazon SES API with a password, that contains a "/"
Step 2: Save and test the connection - it will throw this error.
Step 3: Back to AWS and get another key assigned. It it has no "/" it will work.
### Relevant log output
```shell
`Error executing "GetAccount" on "https://email.eu-central-1.amazonaws.com/v2/email/account"; AWS HTTP error: Client error: `GET https://email.eu-central-1.amazonaws.com/v2/email/account` resulted in a `403 Forbidden` response: {"message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access (truncated...) InvalidSignatureException (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. - {"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."}`
```
### Code of Conduct
- [X] I confirm that I have read and agree to follow this project's Code of Conduct
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://app.bountysource.com/issues/121828581-connection-with-amazon-ses-api-won-t-work-error403-when-the-defined-password-contains-a?utm_campaign=plugin&utm_content=tracker%2F5355074&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://app.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F5355074&utm_medium=issues&utm_source=github).
</bountysource-plugin>
opened 08:02PM - 15 Jan 24 UTC
T2
bug
queue
mautic-5
### Mautic Version
5.0.x series
### PHP version
8.1
### What browsers are yo… u seeing the problem on?
Not relevant
### What happened?
I believe there is a problem in setting up the queue for email using Amazon SQS. If I get a secret_key that includes any special character i.e. / o + then at the moment the secret is retrieved a % is appended to this character (in the config/local.php), even after parsing it gets the wrong secret to the SQS and obviously it doesnt verify.
Workaround: try to get secret_key without special characters.
### How can we reproduce this issue?
Configure sqs scheme in the queue, use any special character in the secret
Scheme: sqs
Host: default
Port: empty
Path: empty
User: empty
Password: empty
Options:
access_key: (amazon access key)
account: (amazon account)
auto_setup: false
queue_name: (name of the queue)
secret_key: (amazon secret key)
region: us-east-1
### Relevant log output
_No response_
### Code of Conduct
- [X] I confirm that I have read and agree to follow this project's Code of Conduct
<br /><hr>
Care about this issue? Want to get it resolved sooner? If you are a <a href='https://www.mautic.org/become-a-member-of-mautic'>member of Mautic</a>, you can add some funds to the <a href='https://opencollective.com/mautic/projects/bounties'>Bounties Project</a> so that the person who completes this task can claim those funds once it is merged by a member of the core team! Read the docs <a href='https://contribute.mautic.org/product-team/mautic-bounty-programme'>here.</a>
