Re: base-64 ignored

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/
> > > Cgo8IURPQ1RZUEUgaHRtbCBQVUJMSUMgIi0vL1czQy8vRFREIFhIVE1MIDEuMCBUcmFuc
> > > 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`.

Regards,
Ingo

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRxKgkQMhrHYtSAVAgadH5FMOC52AUCYo+qDAAKCRAadH5FMOC5
2LFEAKDlyDUmEa7qJjl2WgYZssV0s2G51QCaAjZ4/5kS9GXaFZgX7kym97bxjZY=
=OeRt
-----END PGP SIGNATURE-----