tmda-ofmipd: the dreaded TypeError: Expected list, got <type 'str'>

Hello list,

I have a customer whose legitimate mail seems to trip an exception in 
tmda-ofmipd, causing his mail to go undelivered.  Worse, he appears to 
get no notification of the error, so his MUA happily marks the message 
as sent.

File "/usr/local/bin/tmda-inject", line 116, in ?
orig_msgout_as_string = Util.msg_as_string(msgout)
File "./TMDA/Util.py", line 552, in msg_as_string
File "./TMDA/pythonlib/email/generator.py", line 84, in flatten
File "./TMDA/pythonlib/email/generator.py", line 109, in _write
File "./TMDA/pythonlib/email/generator.py", line 135, in _dispatch
File "./TMDA/pythonlib/email/generator.py", line 266, in _handle_message
File "./TMDA/pythonlib/email/message.py", line 185, in get_payload
TypeError: Expected list, got <type 'str'>))

Through some experimentation, my customer believes that using a 
Content-Type of 'message/rfc822' triggers the bug.  I can send along 
(privately) 2 messages that trigger the bug.  Contact me directly if 
you'd like to see them.

Has anyone encountered this, and are there any patches floating around I 
could try?  Even if this can't be fixed, it seems imperative that 
tmda-ofmipd return some error to the MUA when it encounters an internal 
exception.

I'm running TMDA 1.1.11 on OpenBSD 4.2, with qmail+vpopmail.

Thanks,
-- 
Dave Steinberg
http://www.geekisp.com/
http://www.steinbergcomputing.com/