For the following subject line roundup does not seem to
correctly decode the subject and I'm getting the error
message below:

Subject: Re: [it_issue3]
 =?ISO-8859-1?Q?Ren=E9s_Rechner_[responsible=3Dgsteiner=2Cstatus=3D?=
 =?ISO-8859-1?Q?feedback]?=

Note that the subject line has two continuation lines
(and they *do* start with a space but the broken
sourceforge interface breaks them -- when will we use
roundup for roundup bug-reporting :-)

The error message I'm getting indicates that roundup
can't correctly decode the subject (the stop/start of
the utf-8 encoding seems to be the problem), looks like
the "fe" of "feedback" got interpreted as a hexcode of
an escaped part -- although the '=' preceding it was
correctly encoded as '=3D':

"""
There were problems handling your subject line argument
list:
- not of form [arg=value,value,...;arg=value,value,...]

Subject was: "Re: [it_issue3] Renés Rechner
[responsible=gsteiner,status?edback]"
"""

Version of roundup is 0.8.4; The mailer was Lotus Notes :-(

Logged In: YES 
user_id=34818

I've now added this case as a doctest for decode_header in
rfc2822.py and this works. The problem is *not* in the
decoding of the header: The problem is in the generated
error message. Seems the error message gets appended
verbatim to the message text which is encoded in quoted
printable. The original header contained a "," instead of
";" for separating the two set-commands. But the resulting
error message suggested something else.
I've changed the title of this bug-report accordingly.

Logged In: YES 
user_id=34818

OK, seems error messages are sent back as quoted printable
parts but never encoded using quopri. The attached patch to
mailer.py calls quopri.encodestring for the error message part.