Subject: Attachments Pine -> Outlook 2002

From: Don Newcomer <[email-masked]>
Date: Tue, 9 Apr 2002 11:07:34 -0400 (EDT)

The following was sent to me by another person in our group.  I've tested
it and, in fact, Pine causes Outlook problems with attachments:

	A heads up on sending attachments from Pine to someone using
	Outlook 2002 (with Office XP).  If you send a message with an
	attachment from Netscape Messenger or Webmail to someone who reads
	their mail with Outlook, the message appears to have an attachment
	(as noted by the paperclip icon and filename below the subject line
	in the header of the message).  However, if you send a message with
	an attachment from Pine to someone reading e-mail with Outlook, the
	paperclip icon and filename do not appear.  In the INBOX listing,
	the paperclip icon appears as long as the message is unread.  As
	soon as you read the message though, the paperclip no longer
	appears on that message's line in the INBOX list. In Outlook, even
	though it appears that there is no attachment with this message, if
	you drag down the "File" menu to "Save attachments", you may save the
	attachment out by its original filename, thus the file is actually
	there, it's just you wouldn't know it by looking at the message
	itself like you would for a message sent from Messenger, Webmail or
	Outlook.

	It should be noted that Messenger and Webmail show that the message
	from Pine has an attachment with no problem.  This is only a
	problem if the message was sent by Pine and read in Outlook.

Is this a known problem or is there something we can do on the Pine end to
make it work properly?  Thanks in advance.

================================================================================
Don Newcomer                                            Dickinson College
Associate Director, System and Network Services		P.O. Box 1773
[email-masked]                                  Carlisle, PA  17013
                                                        Phone: (717) 245-1256
                                                          FAX: (717) 245-1690

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

---

From: Henrik Edlund <[email-masked]>
Date: Tue, 9 Apr 2002 17:30:49 +0200 (MET DST)

On Tue, 9 Apr 2002, Don Newcomer wrote:

DN> The following was sent to me by another person in our group.  I've tested
DN> it and, in fact, Pine causes Outlook problems with attachments:
DN>
DN>
DN> 	A heads up on sending attachments from Pine to someone using
DN> 	Outlook 2002 (with Office XP).  If you send a message with an
DN> 	attachment from Netscape Messenger or Webmail to someone who reads
DN> 	their mail with Outlook, the message appears to have an attachment
DN> 	(as noted by the paperclip icon and filename below the subject line
DN> 	in the header of the message).  However, if you send a message with
DN> 	an attachment from Pine to someone reading e-mail with Outlook, the
DN> 	paperclip icon and filename do not appear.  In the INBOX listing,
DN> 	the paperclip icon appears as long as the message is unread.  As
DN> 	soon as you read the message though, the paperclip no longer
DN> 	appears on that message's line in the INBOX list. In Outlook, even
DN> 	though it appears that there is no attachment with this message, if
DN> 	you drag down the "File" menu to "Save attachments", you may save the
DN> 	attachment out by its original filename, thus the file is actually
DN> 	there, it's just you wouldn't know it by looking at the message
DN> 	itself like you would for a message sent from Messenger, Webmail or
DN> 	Outlook.
DN>
DN> 	It should be noted that Messenger and Webmail show that the message
DN> 	from Pine has an attachment with no problem.  This is only a
DN> 	problem if the message was sent by Pine and read in Outlook.
DN>
DN> Is this a known problem or is there something we can do on the Pine end to
DN> make it work properly?  Thanks in advance.

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.

-- 
http://www.edlund.org/

---

From: Gopi Sundaram <[email-masked]>
Date: Tue, 9 Apr 2002 10:33:54 -0500 (CDT)

On Tue, 9 Apr 2002, Don Newcomer wrote:

> The following was sent to me by another person in our group.  I've
> tested it and, in fact, Pine causes Outlook problems with attachments:
<snip>
> Is this a known problem or is there something we can do on the Pine
> end to make it work properly?  Thanks in advance.

Yes to both.

Read this message in Google's archive of comp.mail.pine:

<http://groups.google.com/groups?selm=Pine.NXT.4.41.0111071619060.22033-100000%40Tomobiki-Cho.CAC.Washington.EDU>

The work-around applies to later versions of Pine as well.

-- 
Gopi Sundaram
[email-masked]
http://www.cse.sc.edu/~gopalan/Pine/