On Sat, 16 Mar 2019 22:14:41 -0600, "Anthony J. Bentley" said:
"mhshow: invalid BASE64 encoding in --"
Since it's a public mailing list, one of these messages is enclosed below.
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Yeah that's a reasonable thing to do if you're sending UTF-8/
Message-ID: <6c5e3c76d90a7f84@poolp.org>
Ck9uIE1hciAxNiwgMjAxOSA1OjA5IFBNLCBUaG9tYXMgQm9obCA8b3BlbnNtdHBkLW1pc2MtNjQ2
So here we start the UTF-8
bnN1YnNjcmliZSwgc2VuZCBhIG1haWwgdG86IG1pc2MrdW5zdWJzY3JpYmVAb3BlbnNtdHBkLm9y
Zwo+Cg==
And here we finish it..
--
You received this mail because you are subscribed to misc@opensmtpd.org
To unsubscribe, send a mail to: misc+unsubscribe@opensmtpd.org
And this is a crock, because it's still part of the (only) bodypart, but is
obviously not
base64.
What *should* happen if mailing list software feels the need to stick a footer
on
is to repackage the mail as a multipart/related, with the first body part being
the UTF-8 body of the mail, and the second the mailing list's footer.
Somebody should complain to the administrator of that list - mailman has been
able to do this rewrite correctly for aeons now.
Having said that, there's certainly plenty of room in "be lenient what you
accept"
that maybe if we're looking at base64, if we encounter a blank line we toss the
rest of the body part.
(I have an equivalent on my to-do list for exmh for this same issue.)
--
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers