email: huge address lines blow stack

[mhammond]

BPO	654362
Nosy	@mhammond, @warsaw
Files	crash_email.patch: Possible patch

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/warsaw'
closed_at = <Date 2002-12-30.17:29:58.000>
created_at = <Date 2002-12-16.04:59:03.000>
labels = ['library']
title = 'email: huge address lines blow stack'
updated_at = <Date 2002-12-30.17:29:58.000>
user = 'https://github.com/mhammond'

bugs.python.org fields:

activity = <Date 2002-12-30.17:29:58.000>
actor = 'barry'
assignee = 'barry'
closed = True
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2002-12-16.04:59:03.000>
creator = 'mhammond'
dependencies = []
files = ['712']
hgrepos = []
issue_num = 654362
keywords = []
message_count = 2.0
messages = ['13617', '13618']
nosy_count = 2.0
nosy_names = ['mhammond', 'barry']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue654362'
versions = []

[mhammond]

The following code will recurse until Python throws an
exception:
"""
import email.Utils
addrlist = ["foo@bar.com"] * 2000
email.Utils.getaddresses(addrlist)
"""

I found a huge address list in my spam archive, which
is how I found the error. Attaching suggested patch
that avoids recursion.

bugfix candidate I guess?

[warsaw]

Logged In: YES
user_id=12800

Funny, I just copied the implementation of this up from
rfc822.py into _parseaddr.py and it has something very
similar to what you done. It uses += instead of .extend()
but I think that makes no difference.