|
-----Original Message-----Allen
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of John
Sent: Friday, December 12, 2008 12:37 PMATT00001.TXT
To: 'Midrange Systems Technical Discussion'
Subject: RE: Creating & sending MIME file causing
attachmentname="EM045593.PDF"
The email I am using for this is from Outlook
Here is an example of the MIME data that causes the extra
attachment:
From: jjjjj <jjjjj@xxxxxxxxx>
To: jjjjj@xxxxxxxxx
Date: Fri, 12 Dec 2008 13:24:50 -0500
Subject: test email subject
Importance: normal
Sensitivity: normal
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--=_BoundaryOne"
Your mail reader does not support MIME!
----=_BoundaryOne
Content-Description: EM045593.PDF
Content-Type: application/octet-stream;
based
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="EM045593.PDF"
JVBERi0xLjMgI...
...
...
----=_BoundaryOne
Content-type: text/plain; charset=us-ascii
test email message
----=_BoundaryOne--
John
-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Friday, December 12, 2008 1:11 PM
To: Midrange Systems Technical Discussion
Subject: Re: Creating & sending MIME file causing
ATT00001.TXT attachment
From: John Allen
We are now creating our own email messages
(MIME files) with as many attachments as we want.
I don't know that much about MIME protocol, but I suspect
that Exchange is creating the ATT00001.TXT attachment
on MIME headers embedded in the data stream. Content-Typea
and Content-Transfer-Encoding headers, perhaps. Or maybe
Multipart header? Are you using a tool for generatingMIME
headers?Dec
My Yahoo mail reader shows the following headers in your
original post, for example. But it didn't generate an
attachment:
From: "John Allen"
To: <MIDRANGE-L@xxxxxxxxxxxx>
Subject: Creating & sending MIME file causing ATT00001.TXT
attachment
Date: Fri, 12 Dec 2008 10:42:22 -0500
Message-ID: <8AB3471C302B422AA1B5121E88F7C91D@richard>
MIME-Version: 1.0
Thread-Index: AclccDkP6PMRkofhQC+p3C5AA/fpOw== please
include it with any abuse report [69.3.23.28]); Fri, 12
2008 10:09:01 -0600 (CST) rivendell.midrange.com<mailto:midrange-l-request@xxxxxxxxxxxx?subject=unsubscribe>
Precedence: list
Reply-To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
List-Id: Midrange Systems Technical Discussion
<midrange-l.midrange.com>
Auto-Submitted: auto-generated
List-Unsubscribe:
<http://lists.midrange.com/mailman/listinfo/midrange-l>,
List-Archive: <http://archive.midrange.com/midrange-l>http://lists.midrange.com/mailman/listinfo/midrange-l
List-Post: <mailto:midrange-l@xxxxxxxxxxxx>
List-Help:
<mailto:midrange-l-request@xxxxxxxxxxxx?subject=help>
List-Subscribe:
<http://lists.midrange.com/mailman/listinfo/midrange-l>,
<mailto:midrange-l-request@xxxxxxxxxxxx?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: midrange-l-bounces@xxxxxxxxxxxx
Errors-To: midrange-l-bounces@xxxxxxxxxxxx
Content-Length: 1221
--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
or email: MIDRANGE-L-request@xxxxxxxxxxxxarchives
Before posting, please take a moment to review the
at http://archive.midrange.com/midrange-l.(MIDRANGE-L)
--
This is the Midrange Systems Technical Discussion
mailing listhttp://lists.midrange.com/mailman/listinfo/midrange-l
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
or email: MIDRANGE-L-request@xxxxxxxxxxxxarchives
Before posting, please take a moment to review the
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.