On Mon, Sep 23, 2019 at 07:51:45AM +0800, Ed Greshko wrote:
On 9/23/19 12:04 AM, Tim via users wrote:
>On Sun, 2019-09-22 at 22:52 +0800, Ed Greshko wrote:
>>And it did not.
>I noticed the same. On the messages that get corrupted, I've received
>them as base64 encoded (they weren't sent that way), though your
>messages with Frederic correctly accented was also base64 encodede.
>Most other messages coming from the list are just text. Do you get
>those messages as text or base64?
Yes. For some reason I can't fathom it seems the mailing list software turns every
Content-Transfer-Encoding to base64
When sending the initial message is sent from here as
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
>>I think you've said a yahoo to yahoo message is fine. Do you have a
>>non-yahoo account you can send to directly to check?
>Yes, that works fine. It's only messages going through the list that I
>notice getting mangled.
Weird. If it were something on the mailing list side you'd think that everyone would
see the same issue.
FWIW, I find these headers in your posting on my system:
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by fcshome.stoneham.ma.us id
x8MNrkId016512
--
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
But God demonstrates his own love for us in this:
While we were still sinners,
Christ died for us.
------------------------------- Romans 5:8 (niv) ------------------------------