deploy_feedback
deploy_feedback copied to clipboard
can not connect to SMTP server (timeout 110)
I maintain denomailer (https://github.com/EC-Nordbund/denomailer) a smtp client for deno and with https://github.com/EC-Nordbund/denomailer/issues/17 we saw that it did not run on deno deploy.
I tried to replecate it and got a much simpler example that creates an error:
const conn = await Deno.connect({hostname: "smtp.gmail.com", port: 25 })
console.log('DONE')
creates the log:
TimedOut: Connection timed out (os error 110)
at async Object.connect (deno:ext/net/01_net.js:333:17)
at async file:///src/mod.ts:1:14
The code works with no problems localy.
Note: I tried the same with the TLS port and
connectTls
but got the same problem.
might be related to #132
See https://discord.com/channels/684898665143206084/684911491035430919/961964433524031498
You can not connect to SMTP servers on ports 25, 465, or 587 due to abuse. we have an internal issue open to improve the error message
Thanks! That's kinda bad but understandable...
See https://discord.com/channels/684898665143206084/684911491035430919/961964433524031498
You can not connect to SMTP servers on ports 25, 465, or 587 due to abuse. we have an internal issue open to improve the error message
Is that Discord channel private? I want to read more information about it, but it doesn't show anything on Discord. I want to implement email sending on a personal website I'm working on, but I see that the SMTP service is not working. I haven't tried it myself yet, but has this changed today, or is everything still the same?
Is that Discord channel private?
No. You can join here: https://discord.gg/deno
is everything still the same?
Yes, we still block SMTP ports to prevent abuse.
I will close this issue now. In a scenario where we do change our policy, I'll update this issue.