As a follow up to the message I sent Zach previously. It appears that the Mailman system is changing that Transfer-Encoding ...
Message header of a local copy I sent to myself with Thunderbird and amsat-bb Mailman server: Content-Transfer-Encoding: 8bit
Hi Zach, Thanks for your input. I made the recommended changes. The test I ran does indeed show the ascii text in the message source instead of a bunch of jammed together character strings that remind me of satellite telemetry. <snip>
So, I waited for amsat-bb to send me the message I just sent ...
Message header of that message received via the amsat-bb Mailman server: Content-Transfer-Encoding: base64
SGkgWmFjaCwKClRoYW5rcyBmb3IgeW91ciBpbnB1dC4gSSBtYWRlIHRoZSByZWNvbW1lbmRlZCBj aGFuZ2VzLiBUaGUgdGVzdCBJIHJhbiAKZG9lcyBpbmRlZWQgc2hvdyB0aGUgYXNjaWkgdGV4dCBp biB0aGUgbWVzc2FnZSBzb3VyY2UgaW5zdGVhZCBvZiBhIGJ1bmNoIApvZiBqYW1tZWQgdG9nZXRo <snip>
This gives me a little more information to send to the volunteers running the mail system. Something along the route changed the listserve message to base64.