[Bug 1235101] Re: Mailman 2.1.15 and later crashes on more email

[Mark Sapiro]

I'm not convinced that the post 2.1.14 changes are responsible. There
could be a bug in email.Header.decode_header(), but the main difference
is the 2.1.14 method didn't decode RFC 2047 encoded headers. It could be
that the messages that throw the exception are all malformed spam
anyway. In any case, please provide one or more of the messages that
cause the exception to be thrown.

Also, it will be easy to catch the exception and prevent the shunting,
but what should be done with the message? At this point in the
processing, we don't know what rule if any this header might match. I am
inclined to do one of two things:

1) just leave the header undecoded.

2) replace the header along the lines of "Header-Name: unparseable RFC
2047 encoding" becomes "X-Undecodable-Header: Header-Name: unparseable
RFC 2047 encoding".

Any thoughts?

** Changed in: mailman
   Importance: Undecided => Medium

** Changed in: mailman
       Status: New => Incomplete

** Changed in: mailman
    Milestone: None => 2.1.16

** Changed in: mailman
     Assignee: (unassigned) => Mark Sapiro (msapiro)

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1235101

Title:
  Mailman 2.1.15 and later crashes on more email

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1235101/+subscriptions