AWS SES SMTP with special characters in credentials fail authentication
solidterre opened this issue · comments
📑 I have found these related issues/pull requests
I checked and didn't find similar issue.
🛡️ Security Policy
- I agree to have read this project Security Policy
Description
It seems that when using the Email (SMTP) notification type and using credentials with special characters ("/" or "\" for example), the credentials can not be validated (I keep getting a 535 error).
I am sure these credentials are valid (checked multiple times) since they are the same (copy pasted, no additional spaces or invisible characters added) as the ones I use on another website and they work there.
It seems to me like this is due to an encoding issue ?
👟 Reproduction steps
- Setup notification
- Select Email (SMTP)
- Fill in SMTP information
- Use credentials with a special character (like "/" or "\" f.e.)
👀 Expected behavior
It just works.
😓 Actual Behavior
"Invalid login" error.
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
Debian 12
🌐 Browser
Firefox
🖥️ Deployment Environment
- Runtime: Docker 26.1.3 + Caddy
- Database: SQLite
- Filesystem used to store the database on:
- number of monitors: 6
📝 Relevant log output
No response
We don't encode the password or username.
- Before we go out and try replicating this:
Have you made sure that ALL the settings (including smtp-hostname+port, auth options, dkim, ...) are identical (not just username+PW)? - Why do you think
special character (like "/" or "\" f.e.)are at fault? (have you changed the password to be just alphanumeric? What was the result?) - What mail provider are you using?
Unrelated:
Database: MariaDB is Conflicting with the version number. In v1, we only support sqlite as a database. See #4500 for further details.
Actually it seems I was mistaken. For "pure" usage of SMTP tokens generated from AWS SES (which is the provider I use), I need to generate the SMTP password using a special script - which I wasn't aware of before searching more thoroughly online.
Very sorry for the inconvenient time lost @CommanderStorm, my mistake.
Will update the title for future people who might have this problem.
You can consider this closed.