Vance Wheelock:
> The output message looks like:
>
> ======================================================================
> From: xxx AT xxx DOT com
> To: xxxx AT xxxxx DOT net
> Subject: Teleblend test
> References: <00e501c7d9e4$03a64e30$0200810a AT xxxx DOT net>
> In-Reply-To: <00e501c7d9e4$03a64e30$0200810a AT xxxxx DOT net>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="------------060108060008080501030900"
> Message-Id: <20070808174614.4B8B757E78 AT xxxxx DOT com>
> Date: Wed, 8 Aug 2007 13:46:14 -0400 (EDT)
>
>
> This is a multi-part message in MIME format.
> --------------060108060008080501030900
That should render OK with MIME-aware software.
> The Message-Id: and Date: lines are appended by postfix's sendmail (as
> far as I can tell). The two lines get appended at the very first empty
> line. In this case since I do not have an extra cr/lf under the
> "Mime-Version 1.0" line and my body is directly below the "Mime-Version
> 1.0" line, the two lines get pasted into the "body" of my message where
> it finds it's first empty lines. The $body string starts with the lines
>
> Content-Type: multipart/alternative;
> boundary="------------060108060008080501030900"
>
> and then after this is a new line, and that is where the two lines are
> being appeneded plus two cr/lf lines.
>
> So I thought I could append an extra newline after the "Mime-Version
> 1.0" line and it would work.
That definitely screws up the mail. The Content-Type: is no longer
part of the message headers, and thus your MIME boundaries no longer
work.
If you want to write MIME formatted mail, you need to study the
MIME RFC documents.
Wietse
|
