On 9/23/19 3:39 PM, Stephen J. Turnbull wrote:
Ed sent his message in Unicode with NFC normalization (the é is
pre-composed) and UTF-8. Tim's message contains two ?, indicating a
pair of unknown characters. One possibility is that Tim's MUA
(Evolution) converts that to NFD normalization and som
Tom Horsley writes:
> Some of the messages show the international characters,
In this thread, those are Ed's.
> and some do not.
Tim's.
> It would be interesting to examine the detailed headers of the
> message where the characters disappeared,
I looked in my local folder, and there's not
Ed Greshko writes:
> Yes. For some reason I can't fathom it seems the mailing list
> software turns every Content-Transfer-Encoding to base64
It's just "old fashioned stupidity" far beyond the ken of today's
users inexperienced with the details of the global mail system. Let
me explain.
Mail
On 9/23/19 1:36 PM, Tim via users wrote:
On Mon, 2019-09-23 at 07:51 +0800, Ed Greshko wrote:
For some reason I can't fathom it seems the mailing list software
turns every Content-Transfer-Encoding to base64
Old fashioned stupidity? Thinking 7-bit email is still necessary?
It should still wor
On Mon, 2019-09-23 at 07:51 +0800, Ed Greshko wrote:
> For some reason I can't fathom it seems the mailing list software
> turns every Content-Transfer-Encoding to base64
Old fashioned stupidity? Thinking 7-bit email is still necessary?
It should still work as base64, but the encoding is doing i
On Sun, 22 Sep 2019 20:16:17 -0400
Fred Smith wrote:
> FWIW, I find these headers in your posting on my system:
For what it is worth, I glanced at this thread over on the fedora
mailing list archives (which isn't an easy thread to find over
there because someone changed the subject line of an
exi
On 9/23/19 8:16 AM, Fred Smith wrote:
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
Your side "au
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
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 al
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 co
On Sun, 2019-09-22 at 22:09 +0800, Ed Greshko wrote:
> On 9/22/19 10:00 PM, Tim via users wrote:
> > On Sun, 2019-09-22 at 19:29 +0800, Ed Greshko wrote:
> > > So, I would blame yahoo. :-) :-)
> > Ordinarily, I'd agree. But if I post directly through Yahoo (using
> > their SMTP servers), and rece
On 9/22/19 10:41 PM, Tim via users wrote:
I see. I'm curious though. If you respond to this and keep the
contents will Fr??d??ric survive?
Very punny.;-) Here's the reply.
And it did not.
I think you've said a yahoo to yahoo message is fine. Do you have a non-yahoo
account you can se
On Sun, 2019-09-22 at 22:09 +0800, Ed Greshko wrote:
> On 9/22/19 10:00 PM, Tim via users wrote:
> > On Sun, 2019-09-22 at 19:29 +0800, Ed Greshko wrote:
> > > So, I would blame yahoo. :-) :-)
> >
> > Ordinarily, I'd agree. But if I post directly through Yahoo (using
> > their SMTP servers), and
On 9/22/19 10:00 PM, Tim via users wrote:
On Sun, 2019-09-22 at 19:29 +0800, Ed Greshko wrote:
So, I would blame yahoo. :-) :-)
Ordinarily, I'd agree. But if I post directly through Yahoo (using
their SMTP servers), and receive from a Yahoo address, international
characters come through unman
On Sun, 2019-09-22 at 19:29 +0800, Ed Greshko wrote:
> So, I would blame yahoo. :-) :-)
Ordinarily, I'd agree. But if I post directly through Yahoo (using
their SMTP servers), and receive from a Yahoo address, international
characters come through unmangled.
I've seen this kind of thing before,
On 9/22/19 7:17 PM, Tim via users wrote:
Below I've just pasted a bit of an email:
On Sun, 2019-09-22 at 06:13 +0200, Fr??d??ric wrote:
It's from my reply to a message. That mangled name is supposed to be
"Frederic" with acute accents above both letter "e"s. It was when I
wrote it, and my ma
Below I've just pasted a bit of an email:
> On Sun, 2019-09-22 at 06:13 +0200, Fr??d??ric wrote:
It's from my reply to a message. That mangled name is supposed to be
"Frederic" with acute accents above both letter "e"s. It was when I
wrote it, and my mail client *CORRECTLY* sent it as UTF-8, bu
17 matches
Mail list logo
