Date: Sun, 7 Jan 2018 10:45:03 -0500
Reply-To: Jason <uberhare@GMAIL.COM>
Sender: Vanagon Mailing List <vanagon@gerry.vanagon.com>
From: Jason <uberhare@GMAIL.COM>
Subject: Re: Gerry List
In-Reply-To: <CAKbau50dVyZLQCWc6XW8O65W_j-RQzXwKq+hdvesKL8Mo9g_oQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
My guess will be money and time :)
On Sun, Jan 7, 2018 at 9:44 AM, Mark McCulley <mark.mcculley@gmail.com>
wrote:
> Thanks Jim. It sounds like the encoding issue in digests was addressed in
> version 16. See this tech article:
> http://www.lsoft.com/news/techtipLSV-issue4-2011.asp
>
> What would be involved in upgrading gerry's listserv software to a more
> modern version?
>
> -Mark
>
> On Sat, Jan 6, 2018 at 11:31 AM, Jim Arnott <jr.arnott@gmail.com> wrote:
>
> > Note that the listserv software that runs the list is nearly 20 years
> old.
> > I’ve not been able to find any switch to enable base64 decoding for the
> > digests or archives. If anyone wants to pore over the documentation and
> > discover such thing, I think everyone would be grateful.
> >
> > http://www.lsoft.com/manuals/1.8d/index.html
> >
> > We are running the level set release v1.8d 2000b
> >
> > Googling about a bit finds threads for versions as late as listserv16
> with
> > similar problems.
> >
> > Jim
> >
> >
> >
> > > On Jan 4, 2018, at 6:22 AM, Mark McCulley <mark.mcculley@GMAIL.COM>
> > wrote:
> > >
> > > Dennis's emails are base64 encoded. base64 encoding is typically used
> to
> > > encode binary information (like images) into ASCII text format. You can
> > > decode the 'gibberish' by cutting and pasting it to this site:
> > https://www.
> > > base64decode.org
> > >
> > > The software that creates the digests should decode base64-encoded
> emails
> > > into readable text but the vanagon listserv is not doing this. There
> may
> > be
> > > a setting on the listserv software that an admin could change to make
> > this
> > > work correctly.
> > >
> > > Dennis, this support article might be help you change your Outlook
> email
> > > client to not use base64 encoding:
> > > https://support.microsoft.com/en-us/help/278134/how-outlook-
> > applies-encoding-to-plain-text-e-mail-messages
> > >
> > > -Mark
> > >
> > >
> > >
> > >
> > > On Wed, Jan 3, 2018 at 8:05 PM, Dennis Haynes <d23haynes57@hotmail.com
> >
> > > wrote:
> > >
> > >> Paul,
> > >> I do not know why this happens. I use multiple computers, windows 10
> > >> phone, outlook, windows mail, and sometimes a web browser for my
> > responses.
> > >> I am at a loss as to what I should be doing differently that won't
> > affect
> > >> other work I do.
> > >>
> > >> List experts?
> > >>
> > >> Dennis
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: paul guard [mailto:gears@prodigy.net]
> > >> Sent: Tuesday, January 2, 2018 3:48 PM
> > >> To: d23haynes57@HOTMAIL.COM
> > >> Subject: Gerry List
> > >>
> > >> Hi Dennis
> > >>
> > >> I must admit to being computer illiterate .. but the Gerry Vanagon
> list
> > >> has to be the most exasperating mailing list I've every experienced.
> > >>
> > >> I am unable to read ANY of your posts (that arrive in daily digest) ..
> > >> they come across as gibberish. It's a shame, as I'm sure you post a
> > lot of
> > >> great stuff worthy of reading.
> > >>
> > >> .. and I'm unable to visit the site to read posts directly off the
> site,
> > >> which would probably read in actual printed english.
> > >>
> > >> Any attempts to sign-up again leave me on some other Vanagon site,
> > >> apparently NOT the Gerry site.
> > >>
> > >> Any tips you might be able to provide would be appreciated. Or .. is
> > >> there any way you could begin posting in plain text? I'm pretty sure
> > I'm
> > >> not the only one with this problem.
> > >>
> > >> Regards,
> > >>
> > >> Paul Guard
> > >> gears@prodigy.net
> > >>
> >
> >
>
|