bpo-1025395: Fix email.utils.parseaddr to handle multiple hops by ioanatia · Pull Request #6917 · python/cpython

This fixes a very old issue with email.utils.parseaddr.
Right now email.utils.parseaddr will fail to parse the input correctly when the address contains a route with multiple hops. However it does not have an issue with single hop routes.

RFC5322 states that including route hops is obsolete and that the route part should be ignored (Section 4.4). It also states that this syntax is valid and it must be accepted and parsed (Section 4).

https://bugs.python.org/issue1025395

This is a duplicate of #142 , the Travis build failing because of changes unrelated to the PR. I have rebased my old branch on latest master, but that still does not seem to help. 🤔 🐱 . @Mariatta