hamann.w at t-online
Nov 12, 2009, 8:39 AM
Post #1 of 1
(371 views)
Permalink
|
Hi,
a lot of mails end up with this code. Checking through one of them (sent from outlook
express), probably the Content-type following the MIME version is the only one that
could be responsible.
Could someone confirm that this is the trouble spot - and how should the header really read?
Wolfgang Hamann
The structure of the mail is like:
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_NextPart_000_0024_01CA6246.01D6AF40";
type="multipart/alternative"
This is a multi-part message in MIME format.
------=_NextPart_000_0024_01CA6246.01D6AF40
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_0025_01CA6246.01D6AF40"
------=_NextPart_001_0025_01CA6246.01D6AF40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
**plaintext goes here**
------=_NextPart_001_0025_01CA6246.01D6AF40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
**html goes here**
------=_NextPart_001_0025_01CA6246.01D6AF40--
------=_NextPart_000_0024_01CA6246.01D6AF40
Content-Type: image/gif;
name="email3.gif"
Content-Transfer-Encoding: base64
Content-ID: <3D73AFB1E9F74027BA370B76E6F9D69B [at] sabin>
**embedded image goes here**
|
