On Sat 19 Nov 2022, at 11:23, gene heskett <ghesk...@shentel.net> wrote: [...] > Looks like that is part of the problem. viewing src, the only thing > wrong is: > > ------=_Part_191_372484550.1668746343067 > Content-Type: text/plain;charset=UTF-8 > Content-Transfer-Encoding: base64 > > > ------=_Part_191_372484550.1668746343067 > Content-Type: text/html;charset=UTF-8 > Content-Transfer-Encoding: base64 > > Separated by the two blanks you see here.
That looks OK to me. If I view the source of a multipart message in Thunderbird (View > Message Source), this is the format... (best viewed where lines won't be wrapped as this may introduce the appearance of hard line breaks where there are none, particularly at "<space>boundary=..."): ### raw message begins [...headers...] Date: Thu, 10 Nov 2022 17:07:49 +0000 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="05d45c0af5b4a05c4d1a60402fc7d9d8c838760bf374b72dc544e84ccb23" [...more headers...] Message-Id: [redacted] --05d45c0af5b4a05c4d1a60402fc7d9d8c838760bf374b72dc544e84ccb23 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Never miss a deal! [...] --05d45c0af5b4a05c4d1a60402fc7d9d8c838760bf374b72dc544e84ccb23 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ascii <!DOCTYPE html> [...] </html> --05d45c0af5b4a05c4d1a60402fc7d9d8c838760bf374b72dc544e84ccb23-- ### raw message ends So it seems a single blank line is required: - after the headers - to separate boundary blocks from _subsequent_ content but newlines preceding a boundary block (except the line after the headers) seem to be optional, and part of the section's content if present. Does a single blank line appear in the plaintext view of your message? If you ctrl+A ctrl+C, can you paste a blank line into a text editor?
