Weird message formatting
Over the past several months many messages are comingthrough with imbedded format control characters (see examplebelow) Anyone know what causing this and how to fix? I havetried multiple browsers but that did not fix it. Sure makes messages hard to read. Dave - K8RSP*********************************************************************************Message: 2 Date: Sat, 9 Jan 2021 12:51:26 -0800 From: Wayne Estes w9ae@charter.net Subject: [AMSAT-BB] Re: ISS split in IC-9700 memory To: Ant Lefebvre anthony.lefebvre@gmail.com Cc: amsat-bb@amsat.org Message-ID: 41f6060a-d001-5ed8-2603-0daeec84a942@charter.net Content-Type: text/html; charset=utf-8
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">On 1/9/2021 12:25 PM, Ant Lefebvre wrote:<br> </div> <blockquote type="cite" cite="mid:CANDxhcnY-51CeBYqivzFQP3uYekjApT8jAWXMRFvumx4AzZ8Gw@mail.gmail.com"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <div dir="ltr"> <div dir="ltr"> <div dir="ltr">Wayne, <div><br> </div> <div>This video walks you through it. Just tried it on mine and worked like a charm saving to memory. All programmed from the radio face. </div> <div><br> </div> <div><a href="https://www.youtube.com/watch?v=totA4bmNHl4" moz-do-not-send="true">https://www.youtube.com/watch?v=totA4bmNHl4</a><br clear="all"> </div> </div> </div> </div> </blockquote> <p>That video merely shows how to set up a custom repeater offset in VFO mode. The video doesn't even attempt to show how to save the custom repeater offset to a channel memory.</p> <p>The instructions on page 25 of the basic manual are the same, showing how to set up a custom offset in VFO mode, but not how to save it in a channel memory.</p> <p>I'm convinced that it's impossible to store a custom repeater offset in an IC-9700 channel memory.</p> <p>73,</p> <p>Wayne Estes W9AE<br> </p> </body> </html>
------------------------------
The fix is to get people to send messages as text and NOT HTML. Not going to happen! What you are seeing are HTML control codes as seen by a text viewer.
It looks like some where between you and the sender is a mail server that does not allow HTML.
There is no reason to send a message in HTML other than to create a much larger message that some servers will not pass as HTML.
73 Glenn WB4UIV
On 1/9/2021 7:12 PM, Dave Woolf wrote:
Over the past several months many messages are coming through with imbedded format control characters (see example below) Anyone know what causing this and how to fix? I have tried multiple browsers but that did not fix it. Sure makes messages hard to read.
Dave - K8RSP
Message: 2 Date: Sat, 9 Jan 2021 12:51:26 -0800 From: Wayne Estes <w9ae@charter.net mailto:w9ae@charter.net> Subject: [AMSAT-BB] Re: ISS split in IC-9700 memory To: Ant Lefebvre <anthony.lefebvre@gmail.com mailto:anthony.lefebvre@gmail.com> Cc: amsat-bb@amsat.org mailto:amsat-bb@amsat.org Message-ID: <41f6060a-d001-5ed8-2603-0daeec84a942@charter.net mailto:41f6060a-d001-5ed8-2603-0daeec84a942@charter.net> Content-Type: text/html; charset=utf-8
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">On 1/9/2021 12:25 PM, Ant Lefebvre wrote:<br> </div> <blockquote type="cite" cite="mid:CANDxhcnY-51CeBYqivzFQP3uYekjApT8jAWXMRFvumx4AzZ8Gw@mail.gmail.com <mailto:CANDxhcnY-51CeBYqivzFQP3uYekjApT8jAWXMRFvumx4AzZ8Gw@mail.gmail.com>"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <div dir="ltr"> <div dir="ltr"> <div dir="ltr">Wayne, <div><br> </div> <div>This video walks you through it. Just tried it on mine and worked like a charm saving to memory. All programmed from the radio face. </div> <div><br> </div> <div><a href="https://www.youtube.com/watch?v=totA4bmNHl4 <https://www.youtube.com/watch?v=totA4bmNHl4>" moz-do-not-send="true">https://www.youtube.com/watch?v=totA4bmNHl4 <https://www.youtube.com/watch?v=totA4bmNHl4></a><br clear="all"> </div> </div> </div> </div> </blockquote> <p>That video merely shows how to set up a custom repeater offset in VFO mode. The video doesn't even attempt to show how to save the custom repeater offset to a channel memory.</p> <p>The instructions on page 25 of the basic manual are the same, showing how to set up a custom offset in VFO mode, but not how to save it in a channel memory.</p> <p>I'm convinced that it's impossible to store a custom repeater offset in an IC-9700 channel memory.</p> <p>73,</p> <p>Wayne Estes W9AE<br> </p> </body> </html>
Sent via AMSAT-BB(a)amsat.org. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
On 01/10/21 13:02, Glenn Little WB4UIV wrote:
The fix is to get people to send messages as text and NOT HTML. Not going to happen!
There is no reason to send a message in HTML other than to create a much larger message that some servers will not pass as HTML.
Hello Glen,
Unfortunately, this happens transparently without many users even knowing it is going on. For instance, if I "View Source" on your posting to the -bb, there are actually two copies of the same contents within the message!
This is a multi-part message in MIME format. --===============3785803079283934891==
Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable
The fix is to get people to send messages as text and NOT HTML.
--------------6BFFFCDA3FDA2D583F1AC9C8 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
</head> <body> The fix is to get people to send messages as text and NOT HTML.<br>
You just sent me a HTML-formatted email. ;-)
I agree that something is going on that is stripping (or corrupting) the MIME headers so that the email Dave sees is being interpreted as text/plain, not as text/html.
This is, sadly, the world we live in now.
--- Zach N0ZGO
Hopefully this is plain text only. For some reason, my server setting got changed from plain text to HTML. I have changed it back to plain text.
Thanks for bringing this to my attention. I had no intent of sending anything as HTML. HTML could contain malicious code causing problems.
73 Glenn WB4UIV
On 1/10/2021 4:03 PM, Zach Metzinger wrote:
On 01/10/21 13:02, Glenn Little WB4UIV wrote:
The fix is to get people to send messages as text and NOT HTML. Not going to happen!
There is no reason to send a message in HTML other than to create a much larger message that some servers will not pass as HTML.
Hello Glen,
Unfortunately, this happens transparently without many users even knowing it is going on. For instance, if I "View Source" on your posting to the -bb, there are actually two copies of the same contents within the message!
This is a multi-part message in MIME format. --===============3785803079283934891==
Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable
The fix is to get people to send messages as text and NOT HTML.
--------------6BFFFCDA3FDA2D583F1AC9C8 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
</head> <body> The fix is to get people to send messages as text and NOT HTML.<br>
You just sent me a HTML-formatted email. ;-)
I agree that something is going on that is stripping (or corrupting) the MIME headers so that the email Dave sees is being interpreted as text/plain, not as text/html.
This is, sadly, the world we live in now.
--- Zach N0ZGO
Sent via AMSAT-BB(a)amsat.org. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
On 01/10/21 21:17, Glenn Little WB4UIV wrote:
Hopefully this is plain text only. For some reason, my server setting got changed from plain text to HTML. I have changed it back to plain text.
Thanks for bringing this to my attention. I had no intent of sending anything as HTML. HTML could contain malicious code causing problems.
Hello Glenn,
Yes, you're no longer sending HTML-encoded messages. However, the content is now sent as base64-encoded, so I had to plop it into this handy decoder to verify that it didn't contain any HTML:
Many email programs will base64 encode the message to preserve 8-bit character sets such as UTF-8. If the message contains only ASCII character values less than or equal to 0x7f, then no encoding is necessary, but some mail clients do it anyway.
73,
--- Zach (CP437 forever!) N0ZGO
participants (3)
-
Dave Woolf -
Glenn Little WB4UIV -
Zach Metzinger