[imp] IMP: problem with attachments

[Oscar A. Valdez]

Chuck:

Firstly, I would like to congratulate you on a terrific application. IMP
is useful, powerful and very elegant. But I'm having problems with
attachments, and by looking at the frequency and number of similar
postings to the IMP mailing list, I suppose it's either a bug or a
common malconfiguration.

I recently upgraded to the following:

Red Hat Linux 8.0
Apache 2.0.40 (from RH rpm's)
PHP 4.2.2 (from RH rpm's)
Pear 1.0.1 (from the horde site)
Horde 2.2.1
IMP 3.2

My problem with attachments is that they get corrupted and duplicated.
I'm including snippets from the source of a message with two
attachments: one is a text file, the other an MSWord file. The text file
appears to be attached four times, but only the first occurrence has
content ( itself erroneous because the content of the text file gets
duplicated); and the MS Word document appears to be attached twice, but
only the first occurrence has content, which is erroneous because the
file can't be opened by a word processor.

I'm wondering if the line "Content-Transfer-Encoding: base64" holds a
clue to the problem.

Oscar

------
Message-ID: <1049996230.3e95abc6969fd at erasmo.mydomain.com>
Date: Thu, 10 Apr 2003 11:37:10 -0600
From: "Oscar A. Valdez" <oscar.valdez at mydomain.com>
To: oscar at myotherdomain.com
Subject: Attach5
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="-MOQ104999623042dd2c9d9d4e4a32a76e700a13eb8df2"
User-Agent: Internet Messaging Program (IMP) 3.2
X-Originating-IP: 192.168.1.65

This message is in MIME format.

---MOQ104999623042dd2c9d9d4e4a32a76e700a13eb8df2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

(this would be the body of the mail message)

---MOQ104999623042dd2c9d9d4e4a32a76e700a13eb8df2
Content-Type: application/octet-stream; name="TextFile.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="TextFile.txt"

T3NjYXIgQS4gVmFsZGV6CkVuZXJnw61hIEJvcmVhbGlzLCBMdGRhLiBkZSBDLlYuT3NjYXIgQS4g
VmFsZGV6CkVuZXJnw61hIEJvcmVhbGlzLCBMdGRhLiBkZSBDLlYu

---MOQ104999623042dd2c9d9d4e4a32a76e700a13eb8df2
Content-Type: application/octet-stream; name="TextFile.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="TextFile.txt"


---MOQ104999623042dd2c9d9d4e4a32a76e700a13eb8df2
Content-Type: application/octet-stream; name="MSWord.doc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="MSWord.doc"

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAARgAAAAAAAAAA
EAAASAAAAAEAAAD+////AAAAAEUAAAD/////////////////////////////////////////////

(here would be the rest of an attached MS Word document)


---MOQ104999623042dd2c9d9d4e4a32a76e700a13eb8df2
Content-Type: application/octet-stream; name="TextFile.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="TextFile.txt"


---MOQ104999623042dd2c9d9d4e4a32a76e700a13eb8df2
Content-Type: application/octet-stream; name="TextFile.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="TextFile.txt"


---MOQ104999623042dd2c9d9d4e4a32a76e700a13eb8df2
Content-Type: application/octet-stream; name="MSWord.doc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="MSWord.doc"


---MOQ104999623042dd2c9d9d4e4a32a76e700a13eb8df2--