[nmh-workers] mhshow: invalid BASE64 encoding in --

2019-03-16 Thread Anthony J. Bentley 
Hi,

I receive many messages on a particular mailing list that fail to
render in nmh-1.7.1, giving the error:

"mhshow: invalid BASE64 encoding in --"

Since it's a public mailing list, one of these messages is enclosed below.


Received: by 2002:a25:1505:0:0:0:0:0 with SMTP id 5csp1062256ybv;
Sat, 16 Mar 2019 20:01:40 -0700 (PDT)
X-Google-Smtp-Source: 
APXvYqzws5uKL9GYOG8gp1VoXW/1xf7I7yx4KSIXQesvJ18bJLWkgXS+/ROxidPg5JwBJVWkq9c0
X-Received: by 2002:adf:fb05:: with SMTP id c5mr7095004wrr.297.1552791700105;
Sat, 16 Mar 2019 20:01:40 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1552791700; cv=none;
d=google.com; s=arc-20160816;
b=dywZCO/wDAgm/3nGVZrHgokMu42JxIBaNyGqDqrMssgMSBI/A/F8SvDU7y0+v193/Y
 j+0NhvmxhpBpMxXakGr0U8KSJfs+rhQKtmlVGiL67Wt9cDL/4zbHsZRXMOAe25/YDc3W
 afwNj2o79zxr8Y0NI5NuR4yKyI1UIDWD/JJ7AxaNed/oiGfTtUPgYX5EHOskBLLktCpB
 BTgTEGuaYymnnG4THLPlGOQ0cfj4LFrc1frqn0ywpJhMqn13gJ7Sid9cFCnSCYC01hrm
 oTvtZ6SZ8rCUrgALQfsvs9deLqhVGIPrVHughxX7jLct19CZzMOQJ8fLpKT9ShKZC3Mc
 ZDhA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; 
s=arc-20160816;
h=message-id:content-transfer-encoding:importance:mime-version
 :precedence:list-owner:list-help:list-post:list-subscribe
 :list-unsubscribe:list-id:to:from:subject:date:delivered-to;
bh=INFDgi1ZmNKszi7lbxtOHD/udka8MrlU9bKYafHzCg0=;
b=mZzRUqGi4HG1LAtyyvzY9XbIWArem7Umde2yEu3GvDOo0h7NMO6UHiQWAe7QdbNX4K
 y32t0emGmMlQjcdCzYFiSJ8r8sNo9IEbW2RP0rdxlE37tKeyThfCjEi/ffyVWeuZq3QO
 kKw2XOBqfKMpmtN30KB2UEa9MN7BQaQkjrgkAOxMjWb1C3WGgJToPXdXK+bQJeWcW9Ut
 pIijPTGZfnTmn5ls7vkqgPJ7KDXz85cm0lQYcUiIdhI9MpGCuQLaONYQp7lG/pYKaKqw
 m0RR9cbME2davqXw5XQ8reRkrojAONVa/HOd+tNpA3TB+++relCGogsmujdDRETnZYdY
 07Fw==
ARC-Authentication-Results: i=1; mx.google.com;
   spf=pass (google.com: domain of 
misc+bounces-4052-anthony=anjbe.n...@opensmtpd.org designates 212.83.129.132 as 
permitted sender) 
smtp.mailfrom="misc+bounces-4052-anthony=anjbe.n...@opensmtpd.org"
Return-Path: 
Received: from out.mailbrix.mx (out.mailbrix.mx. [212.83.129.132])
by mx.google.com with ESMTPS id k14si4334844wro.91.2019.03.16.20.01.39
for 
(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
Sat, 16 Mar 2019 20:01:39 -0700 (PDT)
Received-SPF: pass (google.com: domain of 
misc+bounces-4052-anthony=anjbe.n...@opensmtpd.org designates 212.83.129.132 as 
permitted sender) client-ip=212.83.129.132;
Authentication-Results: mx.google.com;
   spf=pass (google.com: domain of 
misc+bounces-4052-anthony=anjbe.n...@opensmtpd.org designates 212.83.129.132 as 
permitted sender) 
smtp.mailfrom="misc+bounces-4052-anthony=anjbe.n...@opensmtpd.org"
Received: from poolp.org (localhost [127.0.0.1])
by poolp.org (OpenSMTPD) with ESMTP id 63d25387
for ;
Sun, 17 Mar 2019 04:01:37 +0100 (CET)
Received: from ams-1.poolp.org (localhost [127.0.0.1])
by poolp.org (OpenSMTPD) with ESMTP id 03e25220
for ;
Sun, 17 Mar 2019 04:01:37 +0100 (CET)
Delivered-To: m...@opensmtpd.org
Received: from mail.pettijohn-web.com (pettijohn-web.com [108.61.222.55])
by in.mailbrix.mx (OpenSMTPD) with ESMTPS id da66d36c 
(TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO)
for ;
Sun, 17 Mar 2019 04:01:34 +0100 (CET)
Received: from [192.168.0.33] ( [50.238.32.35])
by mail.pettijohn-web.com (OpenSMTPD) with ESMTPSA id 5870aade 
(TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO);
Sat, 16 Mar 2019 22:01:29 -0500 (CDT)
Date: Sat, 16 Mar 2019 22:01:23 -0500
Subject: Re: 550 invalid recipient issue
From: Edgar Pettijohn 
To: m...@opensmtpd.org, Thomas Bohl 
List-Id: 
X-Loop: m...@opensmtpd.org
List-Unsubscribe: 
List-Subscribe: 
List-Post: 
List-Help: 
List-Owner: 
Precedence: list
MIME-Version: 1.0
X-Priority: 3
Importance: Normal
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-Spam-Scanner: rspamc 1.7.9
X-Spam-Scan-Time: 2.098
X-Spam-Action: no action
X-Spam-Score: 3.30 / 15.00
X-Spam-Level: 
X-Spam-Symbols: ARC_NA,
FAKE_REPLY,
RCVD_VIA_SMTP_AUTH,
FROM_HAS_DN,
TO_DN_SOME,
R_SPF_ALLOW,
MIME_GOOD,
PREVIOUSLY_DELIVERED,
DMARC_NA,
MISSING_MID,
RCPT_COUNT_TWO,
HAS_X_PRIO_THREE,
MIME_BASE64_TEXT,
FROM_EQ_ENVFROM,
R_DKIM_NA,
ASN,
RCVD_COUNT_TWO,
RCVD_TLS_ALL
Message-ID: <6c5e3c76d90a7...@poolp.org>

Ck9uIE1hciAxNiwgMjAxOSA1OjA5IFBNLCBUaG9tYXMgQm9obCA8b3BlbnNtdHBkLW1pc2MtNjQ2
OTBAYWxvb2YuZGU+IHdyb3RlOgo+Cj4gPiBCb3RoIGZpbGVzIGFyZSBsb29raW5nIGdvb2Qvc2Ft
ZSBhcyBiZWZvcmUgYW5kIGxvY2FsIGRlbGl2ZXJ5IHdpdGggc2VuZG1haWwgZG9lcyBub3Qgd29y
azoKPiA+IAo+ID4gZ2FicmlAc2VydmVyLmNv

Re: [nmh-workers] mhshow: invalid BASE64 encoding in --

2019-03-16 Thread Valdis Klētnieks 
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: <6c5e3c76d90a7...@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 m...@opensmtpd.org
> To unsubscribe, send a mail to: misc+unsubscr...@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