(In reply to Martin Thomson [:mt:] from comment #3) > I'm not sure that duplicating this to an SNMP bug is correct; Bug 1735864 is not related to SMTP bug but to a TLS Setup delay as reported her in Comment 1, which is a Core > Security or Core > Networking issue, that is why I believe this bug is duplicate. > gmail only uses HTTP. This seems to be related to Google's rollout of TLS early data (aka 0-RTT). The problem is likely related to the way Thunderbird and Firefox handle TLS/Handshake since recently... See Bug 1735864 Comment 64 where we have unfolded a list of handshake related patches recently pushed to Firefox > Core > Security... those are the clues unfolded for now... > We've also had reports about connections that stall in Bug 1738102. That's not TCP and TLS, but QUIC, but if the problem is in the interaction between our early data logic and the way we poll() sockets, then the two have a similar cause. Bug 1738102 may likely be a regression related to one of those patches... but I don't know enough to know for sure... but it looks like it...
Bug 1739673 Comment 4 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 Martin Thomson [:mt:] from comment #3) > I'm not sure that duplicating this to an SNMP bug is correct; Bug 1735864 is not related to SMTP bug but to a TLS Setup delay as reported here in Comment 1, which is a Core > Security or Core > Networking issue, that is why I believe this bug is duplicate. > gmail only uses HTTP. This seems to be related to Google's rollout of TLS early data (aka 0-RTT). The problem is likely related to the way Thunderbird and Firefox handle TLS/Handshake since recently... See Bug 1735864 Comment 64 where we have unfolded a list of handshake related patches recently pushed to Firefox > Core > Security... those are the clues unfolded for now... > We've also had reports about connections that stall in Bug 1738102. That's not TCP and TLS, but QUIC, but if the problem is in the interaction between our early data logic and the way we poll() sockets, then the two have a similar cause. Bug 1738102 may likely be a regression related to one of those patches... but I don't know enough to know for sure... but it looks like it...