Auth failed login to SMTP server when special character in password

[nidasfly]

⚠️ Please verify that this question has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

SMTP worked for Outlook months ago.
But I updated Uptime Kuma, it failed to work.
I reproduced this problem.
Then I registered a new outlook email, with no character in the password, it sent email successfully.

📝 Error Message(s) or Log

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

fly.io

🌐 Browser

Chrome

🖥️ Deployment Environment

[build]
image = 'louislam/uptime-kuma:1'

[CommanderStorm]

Gmail SMTP

Could you have a look at #2928 (comment) and see if you have enabled the app password properly?

Also given that the error message you showed could you make double sure that ALL fields (not just username and password, also DKIM, SMTP hostname/port/...) are identical?
(We get a lot of issues from simple typos)

[nidasfly]

Yes with the gmail app pass, which has no special character, is working.
But other email provider, like outlook, with special character in password, is not working.
I've tested using python with the exact same config, it's working in python.

[nidasfly]

Gmail SMTP

Could you have a look at #2928 (comment) and see if you have enabled the app password properly?

Also given that the error message you showed could you make double sure that ALL fields (not just username and password, also DKIM, SMTP hostname/port/...) are identical? (We get a lot of issues from simple typos)

Hi,
I register a new outlook email, with no special character in the password, and found out uptimekuma can send email with it.
So the problem is located, the character in password is some how changed.
However, I spent hours trying to find out where the code changed the password's special character, but failed.
Could you please look into it?

[CommanderStorm]

The reason why you did not find a place where we chage the password is that it does not exist.
I don't know what is happening with your email provider.

We just pass the username and password to nodemailer as you submitted it to the frontend...

The relevant code is:

uptime-kuma/server/notification-providers/smtp.js

Lines 38 to 41 in 4df71af

	config.auth = {
	user: notification.smtpUsername,
	pass: notification.smtpPassword,
	};

uptime-kuma/src/components/notifications/SMTP.vue

Lines 38 to 46 in 4df71af

	<div class="mb-3">
	<label for="username" class="form-label">{{ $t("Username") }}</label>
	<input id="username" v-model="$parent.notification.smtpUsername" type="text" class="form-control" autocomplete="false">
	</div>
	<div class="mb-3">
	<label for="password" class="form-label">{{ $t("Password") }}</label>
	<HiddenInput id="password" v-model="$parent.notification.smtpPassword" :required="false" autocomplete="new-password"></HiddenInput>
	</div>

Maybe a similar case as reported here?

• Gmail Relay-Smtp needs name: mydomain.com transport settings #4790

[nidasfly]

Maybe a similar case as reported here?

• Gmail Relay-Smtp service usually fails #4790

Can you please try any email with password including special character like "?" or "!"

[CommanderStorm]

Yes, but that is not the issue..
=> please check the rest of your config for typos and retry again. Depending on your email provider you might also need to activate smtp or hop through additional steps like you have to do for Gmail, GMX or similar..

• without !?

  

• with !?

  

[nidasfly]

OK then I don't know what is the problem. It seems only happen to Outlook.
I did check the config for thoughsand times, and tested it with python.

[github-actions]

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.