(In reply to Kai Engert [:KaiE:] from comment #4) > I mean bug 2033073 as the original cause, because it talked about the same error code. I'm not sure, since bug 2033073 seems to be about mitigations for existing `SSL_ERROR_DECRYPT_ERROR_ALERT` failures, not about recategorizing new ones. It does implement a strategy to improve robustness against those failures because they might be caused by encryption key rotation, so maybe we could implement the same kind of mitigation, i.e. removing the SSL token from the network's cache and retrying. Though the cache removal seems to be a C++-only thing so we wouldn't be able to do that for SMTP.
Bug 2034342 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Kai Engert [:KaiE:] from comment #4) > I mean bug 2033073 as the original cause, because it talked about the same error code. I'm not sure, since bug 2033073 seems to be about mitigations for existing `SSL_ERROR_DECRYPT_ERROR_ALERT` failures, not about recategorizing new ones. It does implement a strategy to improve robustness against those failures because they might be caused by encryption key rotation, so maybe we could implement the same kind of mitigation, i.e. removing the SSL token from the network's cache and retrying. Though the cache removal seems to be a C++-only thing so we wouldn't be able to do that for SMTP. *Edit: oh you meant sharing the same root cause, not that bug being the originator, I misread, sorry.*