验证邮件未发送

再次您好,

我阅读了此主题,我所遇到的问题与这里的情况非常相似:

不同之处在于,验证邮件完全未被发送——无论是新成员还是现有成员。看起来在该主题中,邮件在一定程度上是被发送的。

我已经在论坛上有一个现有的测试账户(我不是论坛所有者,只是被任命为管理员),仅用于测试我们遇到的问题。该测试账户已在两年前完成验证。我在测试账户的管理页面中点击了“停用账户”按钮,该按钮提示“停用的用户必须重新验证其电子邮件”,但从未收到任何邮件。

以下是我所做的操作:

我在上面提到的主题中看到,在“登录”标签页中有一个选项,要求工作人员必须批准所有新用户账户,于是我勾选了该选项。我创建了一个全新的测试账户,点击“创建新账户”按钮后,页面跳转到另一页,显示“我们无法检测到您的账户是否已创建,请确保已启用 Cookie。”我进入设置中的“新用户”标签页,发现该账户以灰色字体显示(表示未激活)。我点击新创建的账户名称,进入其管理页面并点击“激活账户”按钮,成功激活了该账户。随后收到通知,提示我需要审核并批准刚刚激活的账户。我点击“批准用户”。然后我返回“新用户”标签页,此时用户名变为蓝色,表示已激活并可以正常使用。

在整个过程中,从未发送过任何邮件。

我查看了最新的成员列表,论坛上最近创建的 37 个账户的用户名均为灰色,即尚未激活。

我并未更改任何设置导致此问题。唯一能想到的是,我执行的某次更新可能引发了此情况。

我的意思是,我和其他论坛管理员可以手动激活并批准所有用户,但这本应……虽然不是完全自动的,但至少不应需要论坛工作人员介入。

最近是否有某些变更导致此情况?或者我需要在设置中进行某些调整或修复?我在设置中四处查找,但未能找到相关选项。当前安装的版本是 2.4.0.beta7。

谢谢!

2 个赞

What do your mail logs say? Can you send a test email? What do your mail service logs show?

1 个赞

Specifically, where do I find the mail logs? Are you talking about screened emails under logs in the settings? If so, it says “No results found.” Test emails don’t work either. I forgot to mention that. I also don’t know where to find the mail service logs.

2 个赞

You might want to take a quick check on your disable emails setting.

You can find various logs at /admin/email. :slight_smile:

3 个赞

Sorry for the wait.

The disable emails setting is currently set to ‘no’.

I skimmed through the /admin/email settings and nothing really stood out. Is there anything else I can check, or something specific I need to look for?

Edit: I think I did an upgrade just a bit ago (it told me an upgrade was needed, so I started it and it told me it failed. Then it said there were no updates available) and it said something about sideqik not working and that it does multiple functions such as emails, if I remember correctly. Would this cause my problem?

3 个赞

Yes

How was this instance installed?

2 个赞

Honestly, I’ve never seen sideqik mentioned before. I’ve looked through the settings several times and never saw anything about sideqik until this last update maybe an hour ago.

I’m assuming it’s something needed?

2 个赞

Yep. Same happened to me on a recent update. If it’s the same, your best bet is to have it manually update:

cd /var/discourse
git pull
./launcher rebuild app

I manually retried the failed mail queues, because I like seeing screens automatically refresh, but I believe it will clear itself up after running a while. You can check the logs.

3 个赞

Sidekiq handles all the scheduling in the back-end.

A rebuild as indicated above may help, but without more insight on your instance I honestly can’t say.

2 个赞

从那以后我又做了几次更新,但它最后仍然告诉我 Sidekiq 无法工作。到了这一步,我认为可以肯定地说它不会自行修复,必须有人手动介入修复了?

另外,我不确定这是否特别重要,但这在我看来并不正常:上次更新进行到一半时,在屏幕上飞速滚动的文本中,它抛出了一大堆类似以下的警告:

WARN: 初始化未使用变量时产生副作用 [更多文本]

WARN: 丢弃未使用变量 _value [更多文本]

以及

WARN: 丢弃未使用变量 _desc [更多文本]

总共 615 行。这仍然是 Sidekiq 的问题,还是完全不同的其他问题?我需要为此担心吗?

编辑:刚刚又进行了一次更新。结果如下:

它仍然提示更新失败,但当我返回时,却显示所有内容已是最新版本,同时仪表板上仍然显示:

2 个赞