qi_lu
3 januari 2026 om 13:24
1
Linux+宝塔+Docker+Discourse 零基础快速搭建论坛网站，Discourse是国外最受欢迎的开源论坛程序。--------------------教程文章：https://blog.zeruns.com/archives/919.html演示站：https://bbs.eeclub.top/--------------------雨云优惠注册地址：https://rain.zer, 视频播放量 6437、弹幕量 9、点赞数 31、投硬币枚数 5、收藏人数 63、转发人数 1,...
DISCOURSE_DEVELOPER_EMAILS: 'xxx@gmail.com'
## TODO: Configure the mail server
## (used for validation of new accounts, notifications, digests, etc.)
## required: hostname of the SMTP mail server used to send mail
DISCOURSE_SMTP_ADDRESS: smtp.qq.com
## uncomment to set the port to something other than the default (25)
DISCOURSE_SMTP_PORT: 587
## USER_NAME / PASSWORD required if the SMTP provider needs authentication
## WARNING: a '#' in the SMTP password can be misinterpreted; ensure it's inside string quotes, e.g.:
## DISCOURSE_SMTP_PASSWORD: "#pass#ord"
DISCOURSE_SMTP_USER_NAME: xxx@qq.com
DISCOURSE_SMTP_PASSWORD: "xxx"
## uncomment to enable implicit TLS at connection time, probably needed for using port 465
#DISCOURSE_SMTP_FORCE_TLS: true
## uncomment to set the HELO/EHLO domain, only set if required by provider
#DISCOURSE_SMTP_DOMAIN: discourse.example.com
## the address from which notifications are sent
DISCOURSE_NOTIFICATION_EMAIL: xxx@qq.com
## uncomment to change server certificate verification
#DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: peer # peer|none
## uncomment to override the authentication method
DISCOURSE_SMTP_AUTHENTICATION: login # plain|login|cram_md5
When trying user registration, Discourse repeatedly sends emails.
I had to manually terminate the retry job in sidekiq.
I tried using the internal test email.
If someone can help me solve this puzzle, I will continue to use QQ Mail, otherwise I will have to try changing the email provider.
Moin
3 januari 2026 om 14:46
2
qi_lu
4 januari 2026 om 02:19
3
Thank you for the reply. The two examples you provided are almost identical to my situation. I have carefully reviewed the relevant content, but I still cannot figure out how to solve it.
There are indeed errors in the logs.
ducks
5 januari 2026 om 16:55
4
howdy, sorry about that. I am working on fixing this to provide actual error messages. I will reply here when merged.
ducks
7 januari 2026 om 16:40
6
howdy again, the PR has been merged. once you have the updated code, please let me know if you are still not seeing a human readable error message.
qi_lu
8 januari 2026 om 04:06
7
This is the record of me running doctorhttps://mathcollapse.20000816.xyz/ZWM4MzAzZjUzZDZjMGU1.txt
This is the error log after the update
Message (2 copies reported)
SMTP Error Net::SMTPUnknownError with message:
response:
Backtrace
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/broadcast_logger.rb:218:in `block in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/broadcast_logger.rb:217:in `map'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/broadcast_logger.rb:217:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/broadcast_logger.rb:129:in `error'
/var/www/discourse/lib/email/sender.rb:308:in `rescue in send'
/var/www/discourse/lib/email/sender.rb:295:in `send'
/var/www/discourse/lib/tasks/emails.rake:230:in `block in <main>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/task.rb:279:in `block in execute'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/task.rb:279:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/task.rb:279:in `execute'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/task.rb:199:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/task.rb:188:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/application.rb:188:in `invoke_task'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/application.rb:138:in `block in top_level'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/application.rb:138:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/application.rb:138:in `block in top_level'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/application.rb:147:in `run_with_threads'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/application.rb:132:in `top_level'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/application.rb:83:in `block in run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/application.rb:214:in `standard_exception_handling'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/lib/rake/application.rb:80:in `run'
bin/rake:13:in `<top (required)>'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli/exec.rb:59:in `load'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli/exec.rb:59:in `kernel_load'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli/exec.rb:23:in `run'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli.rb:452:in `exec'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/vendor/thor/lib/thor/command.rb:28:in `run'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/vendor/thor/lib/thor.rb:538:in `dispatch'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli.rb:35:in `dispatch'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/vendor/thor/lib/thor/base.rb:584:in `start'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli.rb:29:in `start'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/exe/bundle:28:in `block in <top (required)>'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
/usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/exe/bundle:20:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
Thank you for your help, but I still cannot resolve the QQ mailbox issue, so I had to switch to a Gmail account, and now it is completely normal.
QQ Mail doesn’t work, I’m having the same issue. Using Mailgun can solve the problem.
ducks
13 januari 2026 om 22:09
9
huh, dang, sorry about that not giving a better error but glad to hear you got it working regardless. I have opened an internal topic to investigate further and maybe update some docs to warn about this, but it seems to be a recurring issue with QQ Mail specifically. there have been multiple reports of QQ Mail causing this same issue over the years.
xu2
14 januari 2026 om 12:59
10
It seems this is a common problem with QQ Mail! It’s not a Discourse setting issue.
