メールホスト名の証明書不一致によりsidekiqキューが過負荷、深刻なサイト不安定化が発生

[RBoy]

@Stephen

enable TLS on their mail server

I do have TLS enabled with a valid certificate and matching hostname from the beginning and then I ran into the issue after the BETA 4 (461936f211) upgrade and posted the logs the topic below. Another user is also having issues and according to him his certificates are in order also:

Retry error in sidekiq

I didn’t run out of space, and this happens even when I select exactly one job to re-run so it doesn’t look like a race condition. There’s clearly more than one issue here, and what I’m seeing here is not related to that linked topic. (It turns out that I didn’t have a certificate problem after all; the server names were in the alternate server name. But I moved to using the hostname that matches the SN anyway, and it made no difference.) I’m successfully sending a tremendous number of mails, …