Mark’s message in the RTÉ Player thread, was also sent using
Content-Transfer Base64 encoding.
Here’s what I take from it all, thus far at least:
There is still formatting present in Eamonn’s and Mark’s so-called Plain
Text messages, which is seen by another receiver’s Outlook or Freelists.
Between them, they strip out the formatting, rendering that thus-sent part -
Plain Text with formatting and Base64 Content Transfer encoding - of the
message body - lank.
So the affected sender must either clear all formatting before sending their
message, or must switch to either none or quoted-printable, as I have
detailed before.
I guess the most stable setting would be achieved by moving away from
BASE64 – if that is possible. Otherwise, they’ll need to remember to clear
all formatting – backspace out the *^i or whatever might be at the top of
the message they’re about to send – or by clearing all formatting via the
Ribbon button – on a per every message sent to Freelists basis.
From: Flor Lynch
Sent: Monday, January 07, 2019 9:45 PM
To: vicsireland@xxxxxxxxxxxxx
Subject: [vicsireland] Re: Plain Text Message sent using Base 64 encoding.
Cearbhall,
I’m on to something, but I’m not sure precisely what!
Suggestion: If Eamonn (and any others whose messages are being received as
blank message bodies) would switch their Content-Transfer-Encoding - this
tab is in the Send tab-control of Options - to either ‘Quoted-Printable’ or
‘None’, i.e, away from BASE 64, then there’s a chance their messages may be
readable. At this point, though, this finding is just preliminary, or,
‘Alpha’ quality!
I think with the message you found unreadable, I didn’t ‘clear all
formatting’. (It was sent in Base 64, probably HTML, but I thought it was in
Plain Text. So to make sure, for the message which you fond complete, I did
‘clear all formatting ‘ found the button in the Ribbon and pressed ENTER. I
didn’t receive a warning that some content would be lost, which is what
often happens if you do this in an HTML original message.)
So far, on this list, I haven’t yet come across any other messages than
Eamonn’s sent using Content-Transzfer-Encoding Base 64. Thing is now, to
figure out how affected senders change this setting in ‘Outlook 2016’, to
make it one of the other two settings compatible with [this and other]
Freelistsd. .
From: Cearbhall O'Meadhra
Sent: Monday, January 07, 2019 9:08 PM
To: vicsireland@xxxxxxxxxxxxx
Subject: [vicsireland] Re: Plain Text Message sent using Base 64 encoding.
Flor,
This one is coming in complete!
All the best,
Cearbhall
m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@xxxxxxx
From: vicsireland-bounce@xxxxxxxxxxxxx <vicsireland-bounce@xxxxxxxxxxxxx> On
Behalf Of Flor Lynch
Sent: Monday, January 7, 2019 8:54 PM
To: vicsireland@xxxxxxxxxxxxx
Subject: [vicsireland] Plain Text Message sent using Base 64 encoding.
This is a plain text message. The previous one (underi similar subject
line) and which caused Paul D other problems, was HTML. Plain Text and Base
64 are (apparently) settings that Eamonn uses. This is my last experiment
here for now. <Sigh Of Relief>.