[Tickets #8005] Re: Imp loses attachments

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/8005
------------------------------------------------------------------------------
  Ticket             | 8005
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Imp loses attachments
  Queue              | IMP
  Version            | 4.3.3
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2009-02-23 03:11) wrote:

> You're right, I do see that, when I look at the message in my sent
> mail folder in claws-mail with the PGP plugin.  But when I look
> through the Gmail web interface, I see "noname".  Go figure?

That doesn't tell us anything because Gmail may very well be broken  
re: this.  I don't think Gmail supports multipart/encrypted anyway.

> Here is how mail flows for me:

How about looking at the sent-mail folder?  IMP will save the exact  
copy of the message text it sends to the outbound mail server, so  
looking at the copy in the sent-mail folder will show what is being  
sent out unadulterated by any other process down the chain.  The  
message source of the message might be useful to look at.

> Looking at this from another direction, adding the
> Content-Description field does no harm save for making messages one
> line longer per attachment.  So why NOT put it in by default?  Users
> could still clear it by blanking the attachment description fields...

As mentioned previously, it's a waste of space (60-80 bytes per e-mail  
adds up on a server with millions of users).  It's also *not* what  
Content-Description was created for.  From RFC 2045[8]:

    The ability to associate some descriptive information with a given
    body is often desirable.  For example, it may be useful to mark an
    "image" body as "a picture of the Space Shuttle Endeavor."  Such text
    may be placed in the Content-Description header field.  This header
    field is always optional.

Here, we don't care about descriptive information for attachments  
(while there is a Description field in IMP 4, this field has been  
removed in IMP 5 for exactly this reason).  Description != filename.

Additionally, adding the Content-Description field is simply masking  
the real problem.  This is no different than turning up your car radio  
when your engine starts making funny sounds.  It may fix the issue  
temporarily, but doesn't give you any insight into the reason why it  
is broken in the first place.