Re: base-64 ignored

On Thursday, 26 May 2022 12:25:48 EDT Ingo Klöcker wrote:
> On Donnerstag, 26. Mai 2022 18:11:39 CEST gene heskett wrote:
> > On Thursday, 26 May 2022 11:22:45 EDT Ingo Klöcker wrote:
> > > On Donnerstag, 26. Mai 2022 14:31:59 CEST gene heskett wrote:
> > > > The following email from a business is not being decoded.
> > > > ------=_Part_29546_1281477845.1653517724260
> > > > MIME-Version: 1.0
> > > > Content-Type: text/html; charset="utf-8"
> > > > Content-Transfer-Encoding: base64
> > > > 
> > > > 77u/
> > > > Cgo8IURPQ1RZUEUgaHRtbCBQVUJMSUMgIi0vL1czQy8vRFREIFhIVE1MIDEuMCBUc
> > > > mFuc
> > > > 2l0
> > > > 
> > > > +83k of additional data, ending in:
> > > > 
> > > > ------=_Part_29546_1281477845.1653517724260--
> > > > 
> > > > Why?
> > > 
> > > Probably a bug in KMail. Maybe it's confused because the first line
> > > contains only 4 characters. `base64 --decode` could decode the data
> > > without problems.
> > 
> > it's not 77u/ alone on a line, its all one line as displayed in
> > kmail.
> > is the / an illegal char in base 64?
> 
> Ah, okay. So the line got word-wrapped in your email. No, / is a legal
> char in base64. Maybe the end of the base64-encoded data is broken.
> Try decoding the data with `base64 --decode`.

How do I go about that? Its typically around 90k of base64. Miltipart 
mixed IOW. 

> Regards,
> Ingo


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis