[Tickets #8005] Re: Imp loses attachments

bugs at horde.org bugs at horde.org
Fri Feb 20 19:19:10 UTC 2009


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-20 14:19) wrote:

>> #1 - There is no need to add description information.  It is useless,
>> superfluous information in this situation.
>
> Isn't the Content-Description what is displayed by MUAs for the
> attachment?  When I PGP-sign something, the signature shows up as
> "noname".  Why would you not want it to be something like "Signature"
> instead?  Why would you choose to have a file be "noname" over
> "foo.txt"?

You are correct in the MUA's will display Content-Description for a  
part.  But in the absence of a Content-Description part, a MUA will  
fall back to the filename of the part (if it exists) in either the  
Content-Disposition or Content-Type MIME header.  This is why, for  
attachments, Content-Description is superfluous.  For other,  
non-attachment parts (such as a PGP multipart container part), it is  
useful to have a Content-Description header because there is no  
filename.

However, for PGP signature, we already set the Content-Description  
header (see, e.g., horde/framework/Crypt/Crypt/pgp.php, line 1487):

$pgp_sign->setDescription(String::convertCharset(_("PGP Digital  
Signature"), NLS::getCharset(), $charset));

So if that is not appearing in your message, I don't know what is happening.

>> #2 - More important, attaching files works perfectly fine for me.
>> And considering how this is how the millions of people that use IMP
>> attach files every day, it is doubtful there is anything wrong with
>> our code.  You need to find the exact reason/location in IMP code why
>> we wouldn't be attaching the file if there is no description.
>
> OK, look, I'm not making this up.  This is an actual bug at my end.
> Please work with me to find out what combination of options triggers
> it instead of asserting that it works for millions of people.

I did not mean to sound condescending and I apologize.  I simply was  
trying to indicate that this more than likely is something specific to  
your system rather than with Horde/IMP in general.  And explaining why  
I was not going to apply your patch - simply because in theory, it  
shouldn't fix anything.

Are you only sending attachments with PGP?  Have you tried sending  
attachments with no encryption?






More information about the bugs mailing list