I have noticed that the mailing list software seems to insert carriage returns every 76-78 characters before resending the plain text format, where I did not do that.
For those of us who primarily or frequently consume email via mobile platforms, the text ends up looking like this. The smaller screen will automatically reflow text but the mailman software introduces hard carriage returns and makes the text look more like a haiku or a weird poem. It is very difficult to read properly. And to be clear, this is not a problem with my email client on my mobile device, but it is a problem caused by the mailman software combined with the small screen of a mobile device.
It is very annoying.
JoAnne, in your raw email, I see the following fields:
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Hopefully that will help in troubleshooting as well.
Thanks,
Jeremy / KO6RM
On October 17, 2017 at 08:00:47, JoAnne K9JKM (k9jkm@comcast.net) wrote:
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.