Yes.  It will return the entire contents of that part as 'text/plain' 
data - which is what I see.  If your setup is showing a MSWord 
attachment, you have a broken/older version of c-client that isn't 
parsing that message/rfc822 part correctly (I'm using imap-2006c1).

IMP *did* show a Word attachment for me. But isn't it the c-client 
library, not IMP, that chokes on multipart messages without MIME 
headers?

They meant that it renders fine in that there are no errors and 
correctly shows all MIME parts of the message.  Not that they can see 
a MSWord attachment in the last part of the message (if you see 
text/plain for the last part, the message is rendered correctly.  If 
you see a MSWord attachment, then IMP is broken and needs to be fixed).
That last part of the message may look like attachment data, it may 
have meant to be sent as an attachment, but the fact remains it 
*isn't* attachment data - it is instead simply text/plain data.



You really need to read this:

http://wiki.horde.org/IMPNoMessageText

and more specifically this:

http://lists.horde.org/archives/imp/Week-of-Mon-20040209/036646.html 
(although all places in that message that say 
"application/octet-stream" should instead read "text/plain" - that was 
my typo).

I don't know enough about MIME headers to agree or disagree with you.   
But....  two previous posters say that the message renders fine in IMP 
for them.  So why is IMP "badly broken" for them, but functioning 
correctly for me?  I would like to break my system in the same way.



Whether or not the behavior is technically correct, my userbase is 
going to view it as "not correct" because it doesn't do what they want 
it to do.  I can't roll out Horde to them and kill the old webmail 
system if the users view it as broken,

so their perception is what matters more to me than strict adherence 
to RFCs.  Just something to consider - I fully realize that it's open 
source and I'm free to learn PHP and modify the code myself if I 
really want something done that way.

There is nothing wrong with your c-client.  That message, or at least 
the message/rfc822 part that contains the "Citizenship in America.doc" 
text, is not a MIME message.  It does not contain a MIME-Version 
header and therefore, must be rendered as text/plain.  This issue has 
come up multiple times and the answer remains the same - we are 
rendering the message correctly.  Whichever mail readers treat that as 
an MS word document (i.e. outlook) are badly broken.

Work fine here too with my IMP H3 (4.1.3) + c-client (imap-2004d)



David

I was afraid you'd say that. :)  My horde version is 3.1.3, c-client 
is uw-2004g running under FreeBSD.  C-client and imapd were installed 
from ports.  Are you using something newer/different than that?   
Thanks for looking into it.

This message is being displayed perfectly for me. If you can't fix it 
by upgrading to the latest Horde version (since you already use the 
latest IMP version), this is probably a bug with your c-client version.

Attached.

Please upload the complete message source.

While Openwebmail and MS Outlook rendered this email correctly (MS 
Word doc inside forwarded email inside another forwarded email), IMP 
did not (see attached screenshot).  The other two applications 
displayed the Word doc as an attachment that could be downloaded.  IMP 
displayed the raw base64 encoded text.



Email body follows, with personal information deleted.  I can bounce 
the original to you if needed.





MIME-Version: 1.0

Content-Type: multipart/mixed; 
boundary="NextPart_Webmail_9m3u9jl4l_25568_1164642920

_0"

Content-Length: 8342





--NextPart_Webmail_9m3u9jl4l_25568_1164642920_0

Content-Type: multipart/alternative; 
boundary="NextPart_Webmail_9m3u9jl4l_25568_1164

642920_1"





--NextPart_Webmail_9m3u9jl4l_25568_1164642920_1

Content-Type: text/plain

Content-Transfer-Encoding: 8bit



Hello All,



abc xyz



Access over 1 million songs - Yahoo! Music Unlimited.

--NextPart_Webmail_9m3u9jl4l_25568_1164642920_1

byte 2476

Content-Type: text/html

Content-Transfer-Encoding: 8bit



<html><body>

stuff...



--NextPart_Webmail_9m3u9jl4l_25568_1164642920_1--

--NextPart_Webmail_9m3u9jl4l_25568_1164642920_0

Content-Type: message/rfc822



From:    x@x.com

To:    y@y.com

Subject:    FW:

Date:    Mon, 27 Nov 2006 13:42:46 +0000

Content-Type: Multipart/mixed;

  boundary="NextPart_Webmail_9m3u9jl4l_25568_1164642920_2"



--NextPart_Webmail_9m3u9jl4l_25568_1164642920_2

Content-Type: application/msword;

         name="Citizenship in America.doc"

Content-Transfer-Encoding: base64

Content-Description: 528959208-Citizenship in America.doc

Content-Disposition: attachment;

         filename="Citizenship in America.doc"



0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAJwAAAAAAAAAA

EAAAKQAAAAEAAAD+////AAAAACYAAAD/////////////////////////////////////////////

////////////////////////////////////////////////////////////////////////////

////////////////////////////////////////////////////////////////////////////

////////////////////////////////////////////////////////////////////////////

////////////////////////////////////////////////////////////////////////////

////////////////////////////////////////////////////////////////////////////

////////////////////////////////////////////////////////////////////////////

///////////////////////////////////////////////////////////////////////////s

pcEAUUAJBAAA8BK/AAAAAAAAEAAAAAAABgAA9BAAAA4AYmpiapjNmM0AAAAAAAAAAAAAAAAAAAAA

AAAJBBYAIhoAAPqnAAD6pwAA9AgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA

AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAIgAAAAAADoBAAAAAAAAOgEAADoB