[Tickets #7981] Re: No way to get some attachments to a multipart message

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/7981
------------------------------------------------------------------------------
  Ticket             | 7981
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | No way to get some attachments to a multipart message
  Queue              | IMP
  Version            | Git master
  Type               | Bug
-State              | Assigned
+State              | Not A Bug
  Priority           | 2. Medium
  Milestone          |
  Patch              |
-Owners             | Michael Slusarz
+Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2009-06-02 15:40) wrote:

I still vehemently disagree with this.  If we are receiving a message  
that is broken, I am fine with not trying to "guess" what the user  
meant to send.  Because what you are asking for is to convert the  
explicit definition of multipart/alternative into, essentially,  
multipart/mixed.  And that's not what it is.  Why stop there, then?   
Theoretically, if a message "looks" like a MIME message but doesn't  
have a MIME-Version header, we could go ahead and parse the message  
anyway.  But that's *not* what the sending user intended.

The fact that this part doesn't show in IMP 5 is exactly what is  
intended (vs. IMP 4).  Again, for access to any part of the message  
(whether it is viewable or legal or not), going forward the only  
location to do this will be in the 'Parts' section of the header.  The  
inline section is only intended to show legal parts meant to be viewed  
inline (and if atc mode is on, it will also show downloadable legal  
parts).