[Heathkit] Plain text TEST

Glen Zook gzook at yahoo.com
Mon Aug 28 12:12:07 EDT 2017


Now that you have found the "problem", I can now decode the messages.  What I get is over 100-lines of "gibberish" and then, finally, the actual text of the message.

 

Glen, K9STH 

Website:  http://k9sth.net


________________________________
From: Jim Shorney <jshorney at inebraska.com>
To: "heathkit at mailman.qth.net" <heathkit at mailman.qth.net> 
Sent: Sunday, August 27, 2017 3:53 PM
Subject: Re: [Heathkit] Plain text TEST




It's not that it is being "rejected". I have examined all the messages that come through as blank and the message text is actually there but is encoded as multi-part MIME. To make matters worse, one part is nested within another. This makes it look like an unrecognized or undecodable attachment to some mail clients and the body of the message appears blank.

For example, Sandy's original test message appears blank to me. But when I look at the raw message I see this:

>Content-Type: multipart/mixed; boundary="===============4945518188467905364=="
>Sender: heathkit-bounces at mailman.qth.net
>Errors-To: heathkit-bounces at mailman.qth.net

>--===============4945518188467905364==
>Content-Type: multipart/alternative; boundary="001a1147003afe740c0557c002cb"

>--001a1147003afe740c0557c002cb
>Content-Type: text/plain; charset="UTF-8"

>Hello folks! My posts have not made it. Repliers tell me that there's no
>body text. Checked my GMail Settings on my Laptop, and changed the font to
>standard Sans Serif.

>Can someone let me know if this TEST made it?
>Tnx, 73,  Sandy AC1Y
>-- 
>Sent from Sandy's Gmail Mobile

>--001a1147003afe740c0557c002cb
>MIME-Version: 1.0
>Content-Type: text/plain; charset="UTF-8"


>--001a1147003afe740c0557c002cb--

>--===============4945518188467905364==
>Content-Type: text/plain; charset="us-ascii"
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline


I'm hoping that came through for everyone, I tied to disguise it by using a quoted text format....

Not an ISP issue, it appears to be a MIME issue.

73


More information about the Heathkit mailing list