[buug] Test! (& base64 encoding)
Michael Paoli
Michael.Paoli at cal.berkeley.edu
Sun Aug 7 11:13:47 PDT 2016
Yes, might be the list, ... or something else along the chain that
did that encoding. I didn't/don't exactly get it straight SMTP from
listserver
to my inbox/mbox, so also possible something along there might have
changed that,
and that might also be conditional upon content (e.g. may only be
under certain
circumstances that it triggers that (re)encoding of the content.
> From: "Ian Zimmerman" <itz at buug.org>
> Subject: Re: [buug] Test!
> Date: Sun, 7 Aug 2016 10:29:38 -0700
> On 2016-08-07 09:04 -0700, Michael Paoli wrote:
>
>> Is the base64 encoding really needed though? Wouldn't
>> plain text ASCII, or quoted printable generally suffice, and
>> make for easier backward compatibility with anyone using some
>> old/ancient email client?
>
> I believe I am innocent here. The local copy saved by mutt is indeed
> plain ASCII, unencoded. It must be the list server doing that, possibly
> only in cases of local submission.
More information about the buug
mailing list