When a cached NNTP client is reused and the underlying TCP connection must be re-established, the NNTP server may request authentication when the POST command is issued. This situation is not handled correctly, as `NNTPClient.currentAction`, which holds the action to be repeated after authentication, is still set to `_actionGroup`. The message send code then receives a report of that command's successful completion, giving the impression that the message had been sent when it actually had not.
Bug 1979618 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When a cached NNTP client is reused and the underlying TCP connection must be re-established, the NNTP server may request authentication when the POST command is issued. This situation is not handled correctly, as `NNTPClient._currentAction`, which holds the action to be repeated after authentication, is still set to `_actionGroup`. The message send code then receives a report of that command's successful completion, giving the impression that the message had been sent when it actually had not.