×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Thanks for everyone suggestions. We have fixed this by
moving the message up before the attachments.


John


-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Friday, December 12, 2008 3:47 PM
To: Midrange Systems Technical Discussion
Subject: Re: Creating & sending MIME file causing
ATT00001.TXT attachment

I'm no MIME expert, but one thing that looks odd to me is
that your PDF attachment (an octet-stream), and your plain
text message are both within "BoundaryOne". I wonder if the
multipart boundary is not properly terminated.

Maybe someone can clarify this, or you might research MIME
protocol at http://www.w3.org/

Nathan




----- Original Message ----
From: John Allen <jallen@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
Sent: Friday, December 12, 2008 11:36:36 AM
Subject: RE: Creating & sending MIME file causing
ATT00001.TXT attachment

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; name="EM045593.PDF"

Content-Transfer-Encoding: base64

Content-Disposition: attachment; filename="EM045593.PDF"

JVBERi0xLjMgI...
...
...
----=_BoundaryOne
Content-type: text/plain; charset=us-ascii
test email message
----=_BoundaryOne--




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.