[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         | BryanRJ at gmail.com
  Summary            | Imp loses attachments
  Queue              | IMP
  Version            | 4.3.3
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


BryanRJ at gmail.com (2009-02-20 18:16) wrote:

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

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?

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

Apology accepted.

I have tried sending attachments both with and without PGP.  I have an  
exceedingly complicated setup, so it's very hard to track down what's  
causing the problem, but I have verified that attachments work 100% of  
the time when a Content-Description is included.

Here is how mail flows for me:

1.  Message composed using Horde web interface
2.  Message delivered to local "sendmail" (SSMTP) on web server and  
stored on mail server via IMAP
3.  Sendmail connects via TLS to SMTP port 2525 on mail server
4.  Mail server accepts message via Postfix
5.  Postfix on mail server feeds message to DKIM-signer
6.  DKIM-signer reinjects message into mail server local Postfix
7.  Mail goes out

I don't think the DKIM signer is the problem, honestly.  It just adds  
two header fields to the message.  So that just leaves the IMAP  
server, ssmtp, postfix, and imp.

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