Subject: Invisible Attachments

From: SoloCDM <[email-masked]>
Date: Wed, 13 Aug 2003 01:56:18 -0600

Recently, while using PINE 4.50, I sent out an email with
attachments.  The recipient couldn't view the attachments.
The recipient couldn't find them anywhere.  When the recipient
decided to forward the message to me so I could see the problem,
while using M$ IE, the attachments appeared.  Is PINE causing the
attachments to be included without meeting all RPC requirements
and is it compatible with all email readers?  In the past, this
hasn't happened.  Has anyone else experienced this type of fluke?

-- 
Note: When you reply to this message, please include the mailing
      list address and my email address in To: and/or Cc: with
      any proper combination

*********************************************************************
Signed,
SoloCDM
-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: David Dierauer <[email-masked]>
Date: Wed, 13 Aug 2003 09:33:51 -0400 (EDT)

Yes, I have seen this with Pine 4.53 on Mac OS X. One user of MS Outlook
(Outlook 2003, I think? on Windows XP) can never see the attachments I
send him, even though they are in his attachments folder when he checks
there.

-- 
David Dierauer
[email-masked]

---

From: Rico Barth <[email-masked]>
Date: Wed, 13 Aug 2003 15:51:06 +0200 (Westeuropäische Sommerzeit)

Hi David!

> send him, even though they are in his attachments folder when he checks

This is why the microsoft programmers have implemented the RFC for
MIME-attachments in Outlook incorrectly. The RFC says [BASE64] could
write with upper case or lower case characters but M$ has only coded the
lower case version. Pine uses the upper case characters.

Hope that helps.

Bye

Rico

-- 
Dipl.-Math. Rico Barth
T-Systems
Systems Integration
Berater BU Sachsen
Anschrift: Clausstrasse 3 , 09126 Chemnitz
Telefon:   +49 ( 371) 5359 - 350
Telefax:   +49 ( 371) 5359 - 133
Mobil:     +49 ( 160) 94 82 15 82
E-Mail:    [email-masked]
Internet:  http://www.t-systems.com

PGP-Key:
Fingerprint: 8A56 C021 6240 EAD5  AB42 EA2B 9B2E 1405  874C 8377
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x874C8377

---

From: Steve Hubert <[email-masked]>
Date: Wed, 13 Aug 2003 09:24:57 -0700 (Pacific Daylight Time)

Here is the help text for the pine option "quell-content-id". Maybe
setting this option would help.

                           FEATURE: quell-content-id

This feature changes the behavior of Pine when sending messages. It is
intended to work around a bug in Microsoft's Outlook XP mail user agent.
As of this writing, Microsoft has acknowledged the bug but has not added
it to the Knowledge Base. We have been told that there will be a post-SP1
hotfix for Outlook XP. This particular bug has bug fix number
OfficeQFE:4781. The nature of the bug is that messages with attachments
which contain a Content-ID header (which standard Pine attachments do) do
not show the attachment indicator (a paperclip) when viewed with Outlook
XP. So the user has no indication that the message contains an
attachment.

If this feature is set then Pine will remove most Content-ID headers
before sending a message. If an attachment is of type MESSAGE, then the
existing Content-ID headers inside the message will be left intact. This
would only happen with Pine if a message was forwarded as an attachment
or if a message with a message attached was forwarded. Similarly if an
attachment of type MULTIPART/ALTERNATIVE is forwarded, the Content-ID
headers of the alternative parts will not be removed.

Because the Content-ID header is a standard part of MIME it is possible
that setting this feature will break something. For example, if an
attachment has a Content-ID header which is necessary for the correct
functioning of that attachment, it is possible that Pine may remove that
header when the attachment is forwarded. However, it seems fairly safe at
this time.

---

From: David Dierauer <[email-masked]>
Date: Thu, 14 Aug 2003 09:12:29 -0400 (EDT)

Thanks! That worked for me and the recipient of my emails who had
previously been unable to see the attachments.

-- 
-David
[email-masked]

---

From: SoloCDM <[email-masked]>
Date: Thu, 14 Aug 2003 13:08:45 -0600 (MDT)

Thanks Steve!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

___________________________Reply_Separator___________________________

On Wed, 13 Aug 2003, Steve Hubert wrote:

> Date: Wed, 13 Aug 2003 09:24:57 -0700 (Pacific Daylight Time)
> From: Steve Hubert <[email-masked]>
> To: [email-masked], Pine Discussion Forum <[email-masked]>
> Subject: Re: Invisible Attachments
> 
> This feature changes the behavior of Pine when sending messages. It
> is intended to work around a bug in Microsoft's Outlook XP mail user
> agent.  As of this writing, Microsoft has acknowledged the bug but has
> not added it to the Knowledge Base. We have been told that there will
> be a post-SP1 hotfix for Outlook XP. This particular bug has bug fix
> number OfficeQFE:4781. The nature of the bug is that messages with
> attachments which contain a Content-ID header (which standard Pine
> attachments do) do not show the attachment indicator (a paperclip)
> when viewed with Outlook XP. So the user has no indication that the
> message contains an attachment.
> 
> before sending a message. If an attachment is of type MESSAGE,
> then the existing Content-ID headers inside the message will be
> left intact. This would only happen with Pine if a message was
> forwarded as an attachment or if a message with a message attached was
> forwarded. Similarly if an attachment of type MULTIPART/ALTERNATIVE is
> forwarded, the Content-ID headers of the alternative parts will not be
> removed.
> 
> Because the Content-ID header is a standard part of MIME it is
> possible that setting this feature will break something. For example,
> if an attachment has a Content-ID header which is necessary for the
> correct functioning of that attachment, it is possible that Pine may
> remove that header when the attachment is forwarded. However, it seems
> fairly safe at this time.