Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SMTP problem #757

Closed
Kaj-IN opened this issue Oct 20, 2021 · 3 comments
Closed

SMTP problem #757

Kaj-IN opened this issue Oct 20, 2021 · 3 comments
Labels
bug Something isn't working
Milestone

Comments

@Kaj-IN
Copy link

Kaj-IN commented Oct 20, 2021

Hi,

I have a problem with smtp notifications and still got error result "self signed certificate".

image

or

docker logs 58f720e88xxx | grep Error

Error: self signed certificate
at TLSSocket.onConnectSecure (_tls_wrap.js:1515:34)
at TLSSocket.emit (events.js:400:28)
at TLSSocket._finishInit (_tls_wrap.js:937:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:709:12) {
code: 'ESOCKET',
command: 'CONN'
}

The current SMTP configuration is:

image

If I try to send emai via telnet everythning goes well:

└─# telnet email.prahax.cz 25
Trying 10.xx.xx.xxx...
Connected to email.prahax.cz.
Escape character is '^]'.
220 email.prahax.cz Microsoft ESMTP MAIL Service ready at Wed, 20 Oct 2021 22:19:51 +0200
ehlo prahax.cz
250-email.prahax.cz Hello [10.139.xx.xxx]
250-SIZE 37748736
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-AUTH LOGIN
250-8BITMIME
250-BINARYMIME
250 CHUNKING
MAIL FROM: someaddress@linuxconfig.org
250 2.1.0 Sender OK
RCPT TO: karel@xxx.xx
250 2.1.5 Recipient OK
DATA
Subject: Sending an email using telnet

Hello,

Here is my body? Do you like it?

cheers354 Start mail input; end with .
.
quit

.
250 2.6.0 561b471c-3159-49c4-969e-22f290a387cd@xxx.xZ [xxxx] 1858 bytes in 1:30.413, 0,020 KB/sec Queued mail for delivery
quit
221 2.0.0 Service closing transmission channel
Connection closed by foreign host.

I tried different version of Kuma 1.8 and 1.9.1 and got same results :(.

Info
Uptime Kuma Version: 1.8 and 1.9.1
Using Docker?: Yes
Docker Version: 20.10.9
Node.js Version (Without Docker only):
OS: ubntu
Browser: chrome

@Kaj-IN Kaj-IN added the help label Oct 20, 2021
@X1Aaron
Copy link

X1Aaron commented Oct 21, 2021

I'm having the same issue. Can we please allow self-signed certs? Maybe a checkbox to allow self-signed certs?

@whasf
Copy link

whasf commented Oct 26, 2021

Seeing this too, I told it to "Ignore TLS error" but it doesn't seem to be. I can't get SMTP to work otherwise, even if I put in port 25 (it shouldn't be trying TLS!)

@chakflying
Copy link
Collaborator

chakflying commented Oct 27, 2021

Looking at the docs, sendMail() might be the wrong place to set rejectUnauthorized. The method in the docs only has data as a parameter, whereas the tls option is set in the transport config. I don't have a mail server to test this tho.

@louislam louislam added bug Something isn't working and removed help labels Oct 27, 2021
@louislam louislam added this to the 1.10.0 milestone Oct 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants