[3.10] bpo-45239: Fix parsedate_tz when time has more than 2 dots in it (GH-28452) (GH-28930)

Co-authored-by: Łukasz Langa <[email protected]>
(cherry picked from commit b9e6876)

Co-authored-by: Ben Hoyt <[email protected]>

Author: ambv

Lib/email/_parseaddr.py

@@ -128,6 +128,8 @@ def _parsedate_tz(data):
             tss = 0
         elif len(tm) == 3:
             [thh, tmm, tss] = tm
+        else:
+            return None
     else:
         return None
     try:

Lib/test/test_email/test_email.py

@@ -3009,6 +3009,7 @@ def test_parsedate_returns_None_for_invalid_strings(self):
         self.assertIsNone(utils.parsedate_tz('0'))
         self.assertIsNone(utils.parsedate('A Complete Waste of Time'))
         self.assertIsNone(utils.parsedate_tz('A Complete Waste of Time'))
+        self.assertIsNone(utils.parsedate_tz('Wed, 3 Apr 2002 12.34.56.78+0800'))
         # Not a part of the spec but, but this has historically worked:
         self.assertIsNone(utils.parsedate(None))
         self.assertIsNone(utils.parsedate_tz(None))

Misc/NEWS.d/next/Library/2021-10-13-17-52-48.bpo-45239.7li1_0.rst

@@ -0,0 +1,3 @@
+Fixed :func:`email.utils.parsedate_tz` crashing with
+:exc:`UnboundLocalError` on certain invalid input instead of returning
+``None``. Patch by Ben Hoyt.