Supabase从自定义SMTP设置返回多个错误？
我正在努力将自定义SMTP添加到我的Supabase项目中，以便通过MailGun路由电子邮件。我已经开始讨论在这里获得了任何牵引力。
尝试注册会触发电子邮件的用户时，我正在收到请求中的错误。
{"code":500,"msg":"Error sending confirmation mail","error_id":"bb29c6f4-4d99-4c85-8772-5f2fb042221c"}
当我检查supabase日志时，我会看到此错误：
time="2022-06-26T22:10:34Z" level=error msg="500: Error sending confirmation mail" component=api error="Error sending confirmation email: dial tcp 34.83.33.178:25: i/o timeout" method=POST path=/signup referer="https://www.customdomain.io/" remote_addr="24.19.220.31:22601" request_id=bb29c6f4-4d99-4c85-8772-5f2fb042221c
我的supabase设置如下：
SMTP admin email: [email protected]
SMTP host: smtp.mailgun.org
SMTP port: 25
SMTP user: [email protected]
SMTP password: ***************
SMTP sender name: Support
根据MailGun域设置，我们可以使用“端口25、587和465（SSL/TLS）。当我将其更改为端口465时，我会收到此错误：
time="2022-06-28T17:41:59Z" level=error msg="500: Error sending confirmation mail" component=api error="Error sending confirmation email: 535 Authentication failed" method=POST path=/signup referer="https://www.customdomain.io/" remote_addr="24.19.220.31:22611" request_id=6458ccfd-e335-4e5e-916c-c543828c021d
我可能会插入错误的SMTP凭据吗？
I am working to add custom SMTP to my Supabase project so that emails are routed through Mailgun instead. I've started a discussion over here on the Supabase repo, however it hasn't gained any traction yet.
When attempting to register a user, which would trigger an email, I am instead receiving an error on the request.
{"code":500,"msg":"Error sending confirmation mail","error_id":"bb29c6f4-4d99-4c85-8772-5f2fb042221c"}
When I check the Supabase logs, I see this error:
time="2022-06-26T22:10:34Z" level=error msg="500: Error sending confirmation mail" component=api error="Error sending confirmation email: dial tcp 34.83.33.178:25: i/o timeout" method=POST path=/signup referer="https://www.customdomain.io/" remote_addr="24.19.220.31:22601" request_id=bb29c6f4-4d99-4c85-8772-5f2fb042221c
My Supabase settings are as follows:
SMTP admin email: [email protected]
SMTP host: smtp.mailgun.org
SMTP port: 25
SMTP user: [email protected]
SMTP password: ***************
SMTP sender name: Support
According to the Mailgun domain settings, we can use "ports 25, 587, and 465 (SSL/TLS). I have tried all three, however when I change it to port 465, I instead receive this error:
time="2022-06-28T17:41:59Z" level=error msg="500: Error sending confirmation mail" component=api error="Error sending confirmation email: 535 Authentication failed" method=POST path=/signup referer="https://www.customdomain.io/" remote_addr="24.19.220.31:22611" request_id=6458ccfd-e335-4e5e-916c-c543828c021d
What might cause this timeout? Am I inserting incorrect SMTP credentials to the Supabase settings?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
感谢@mansueli在OP的答复中，我弄清楚了。
我按照文档中的建议切换到端口587，然后意识到我已经切换了“ SMTP Admin电子邮件”和“ SMTP用户”字段。改变这些东西修复了一切。
Thanks to @Mansueli in the replies of the OP, I figured it out.
I switched to port 587 as recommended in the docs, and then realized I had the "SMTP admin email" and "SMTP user" fields switched up. Changing those things fixed everything.
使用AWS SES时，我遇到了同样的问题。我的SES处于沙盒模式，因此只让我将电子邮件发送到我在控制台中添加的地址。这导致supabase显示
“错误发送确认邮件”时，每当我尝试将电子邮件发送到其他地址时。为了解决此问题，您应该将电子邮件服务切换到生产模式，并按照文档中建议使用
端口587。这将使您没有任何问题向任何用户发送电子邮件。I had the same problem when using AWS SES. My SES was in sandbox mode, so it only let me send emails to addresses I added in the console. This caused Supabase to show an error saying
"Error sending confirmation mail"whenever I tried sending emails to other addresses.To fix this, you should switch your email service to production mode and use
port 587as recommended in the docs. This will let you send emails to any user without any issues.这可能永远不会发生在其他任何人身上，但是...
对我来说，这是我的SMPT设置中的一个问题。十年后，我发现我在SMPT主人面前有了额外的空间。
如此随机。甚至supabase也忘记了修剪（）。
This will probably never happen to anyone else, but...
For me it was an issue in my SMPT settings. After a decade I found that I had copy/pasted an extra space in front of my SMPT Host.
So random. Even Supabase forgets to trim().