[Tickets #4702] Re: Attachment handling did not work in forwarded email

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=4702
-----------------------------------------------------------------------
 Ticket             | 4702
 Updated By         | Michael Slusarz <slusarz at horde.org>
 Summary            | Attachment handling did not work in forwarded email
 Queue              | IMP
 Version            | 4.1.3
 Type               | Bug
 State              | Not A Bug
 Priority           | 1. Low
-Owners             | 
+Owners             | 
-----------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2006-11-29 20:55) wrote:

> 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.

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).

> 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.

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).