Reply-by-Email 曾有效，现在已损坏

支持
1

我们的“邮件回复”功能运行了两年，但在 17 天前无故停止工作。我查阅了该时间段的员工操作日志，没有发现相关的配置变更、升级或新插件。可能是什么导致了故障？

9 月 30 日之后未收到任何邮件：

image
image1174×495 64.9 KB

邮件也没有被拒绝：

image
image1397×489 63.7 KB

错误日志中没有明显相关的记录，但存在以下内容：

aws-sdk-core-3.112.1/lib/seahorse/client/plugins/raise_response_errors.rb:17:in `call'

aws-sdk-s3-1.96.1/lib/aws-sdk-s3/plugins/sse_cpk.rb:24:in `call'

aws-sdk-s3-1.96.1/lib/aws-sdk-s3/plugins/dualstack.rb:36:in `call'

aws-sdk-s3-1.96.1/lib/aws-sdk-s3/plugins/accelerate.rb:50:in `call'

aws-sdk-core-3.112.1/lib/aws-sdk-core/plugins/jsonvalue_converter.rb:22:in `call'

aws-sdk-core-3.112.1/lib/aws-sdk-core/plugins/idempotency_token.rb:19:in `call'

aws-sdk-core-3.112.1/lib/aws-sdk-core/plugins/param_converter.rb:26:in `call'

aws-sdk-core-3.112.1/lib/seahorse/client/plugins/request_callback.rb:71:in `call'

aws-sdk-core-3.112.1/lib/aws-sdk-core/plugins/response_paging.rb:12:in `call'

aws-sdk-core-3.112.1/lib/seahorse/client/plugins/response_target.rb:24:in `call'

aws-sdk-core-3.112.1/lib/seahorse/client/request.rb:72:in `send_request'

aws-sdk-s3-1.96.1/lib/aws-sdk-s3/client.rb:1274:in `copy_object'

/var/www/discourse/lib/backup_restore/s3_backup_store.rb:61:in `block in vacate_legacy_prefix'

/var/www/discourse/lib/backup_restore/s3_backup_store.rb:60:in `each'

/var/www/discourse/lib/backup_restore/s3_backup_store.rb:60:in `vacate_legacy_prefix'

/var/www/discourse/app/jobs/onceoff/vacate_legacy_prefix_backups.rb:7:in `execute_onceoff'

/var/www/discourse/app/jobs/onceoff/onceoff.rb:25:in `execute'

/var/www/discourse/app/jobs/base.rb:232:in `block (2 levels) in perform'

rails_multisite-3.1.0/lib/rails_multisite/connection_management.rb:80:in `with_connection'

/var/www/discourse/app/jobs/base.rb:221:in `block in perform'

/var/www/discourse/app/jobs/base.rb:217:in `each'

/var/www/discourse/app/jobs/base.rb:217:in `perform'

sidekiq-6.2.2/lib/sidekiq/processor.rb:196:in `execute_job'

sidekiq-6.2.2/lib/sidekiq/processor.rb:164:in `block (2 levels) in process'

sidekiq-6.2.2/lib/sidekiq/middleware/chain.rb:138:in `block in invoke'

/var/www/discourse/lib/sidekiq/pausable.rb:138:in `call'

sidekiq-6.2.2/lib/sidekiq/middleware/chain.rb:140:in `block in invoke'

sidekiq-6.2.2/lib/sidekiq/middleware/chain.rb:143:in `invoke'

sidekiq-6.2.2/lib/sidekiq/processor.rb:163:in `block in process'

sidekiq-6.2.2/lib/sidekiq/processor.rb:136:in `block (6 levels) in dispatch'

sidekiq-6.2.2/lib/sidekiq/job_retry.rb:112:in `local'

sidekiq-6.2.2/lib/sidekiq/processor.rb:135:in `block (5 levels) in dispatch'

sidekiq-6.2.2/lib/sidekiq.rb:38:in `block in <module:Sidekiq>'

sidekiq-6.2.2/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch'

sidekiq-6.2.2/lib/sidekiq/processor.rb:257:in `stats'

sidekiq-6.2.2/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch'

sidekiq-6.2.2/lib/sidekiq/job_logger.rb:13:in `call'

sidekiq-6.2.2/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch'

sidekiq-6.2.2/lib/sidekiq/job_retry.rb:79:in `global'

sidekiq-6.2.2/lib/sidekiq/processor.rb:124:in `block in dispatch'

sidekiq-6.2.2/lib/sidekiq/logger.rb:11:in `with'

sidekiq-6.2.2/lib/sidekiq/job_logger.rb:33:in `prepare'

sidekiq-6.2.2/lib/sidekiq/processor.rb:123:in `dispatch'

sidekiq-6.2.2/lib/sidekiq/processor.rb:162:in `process'

sidekiq-6.2.2/lib/sidekiq/processor.rb:78:in `process_one'

sidekiq-6.2.2/lib/sidekiq/processor.rb:68:in `run'

sidekiq-6.2.2/lib/sidekiq/util.rb:43:in `watchdog'

sidekiq-6.2.2/lib/sidekiq/util.rb:52:in `block in safe_thread'

使用的是手动轮询，而非 POP3 轮询：

image

尝试通过邮件回复的发件人未收到任何拒绝通知或错误消息。

从论坛发送邮件一切正常。AWS SES 方面也没有问题（尽管我认为这与邮件回复功能无关）。

discourse-doctor 检查中未发现异常（除了它提到了非官方插件，但这些插件在该时间段内并未变更）。

2

这可能只是巧合（我的一部分也这么认为），但…

3

这是一个相当富裕的群体，怀疑使用旧设备的人不多。

4

我认为这更像是一个服务器端问题，而不是客户端问题。

5

我想你需要重新构建你的邮件容器。

6

恐怕我需要更多解释——在 meta 中除了足球队外，没有其他地方提到 NFL。NFS？在 /var/discourse/containers/ 中没有这样的容器。

7

抱歉，自动更正。

重建您的邮件容器。

cd /var/discourse 
./launcher rebuild mail-receiver
8

感谢 @pfaffman，问题已解决。看来您以前遇到过这种情况——是否有可以改进的地方？在我们的案例中，后果不仅仅是未能收到用户邮件：

VERP 依赖于接收到的邮件。因此，我们有几天未能处理退信和投诉，导致我们在 SES 的信誉急剧下降，他们随即暂停了我们的外发邮件。

9

这是 DST Root CA X3 Expiration (September 2021) - Let's Encrypt 的结果。它让一些人措手不及，而它对 Discourse 自托管用户造成的问题又足够微妙，以至于被忽视了。目前仍有问题需要解决。

我怀疑它们从 10 月 1 日起就不再被处理了。

我始终未能弄清楚如何让 SES 正常工作。一个紧急的临时解决方案是配置使用 Mailgun 发送出站邮件。