why is apt-listchanges output encoded (WAS Re: history of system)
On Tue, 2005-04-26 at 13:54 -0400, Bill Marcum wrote:
> On Tue, Apr 26, 2005 at 09:18:36AM +0100, michael wrote:
> > On Tue, 2005-04-26 at 00:34 -0500, a.list.address@gmail.com wrote:
> > > On 4/25/05, michael <linux@networkingnewsletter.org.uk> wrote:
> > > >
> > > > Yes, I have got it to email me but it comes out as 'garbage' or at least
> > > > as data I do not know how to read (uudecode didn't help). The below
> > > > example is for the "news" info, the "changelogs" is same sort of thing
> > > > but much longer.
> > > >
> > > > Thanks, Michael
> > > >
> > > > mail
> > > > & 2
> > > > Message 2:
> > > > >From root@ratty Mon Apr 25 15:29:32 2005
> > > > Envelope-to: michael@ratty
> > > > Delivery-date: Mon, 25 Apr 2005 15:29:32 +0100
> > > > Subject: apt-listchanges: news for ratty
> > > > To: michael@ratty
> > > > MIME-Version: 1.0
> > > > Content-Type: text/plain; charset="utf-8"
> > > > Content-Transfer-Encoding: base64
> > > > From: root <root@ratty>
> > > > Date: Mon, 25 Apr 2005 15:29:32 +0100
> > > >
> > > > cHBwICgyLjQuMy0yMDA0MTIzMSszKSB1bnN0YWJsZTsgdXJnZW5jeT1tZWRpdW0KCiAgKiBSZW1v
> > > > dmVkIHBhdGNoIDA1N19wcHBvZS1pbnRlcmZhY2UtY2hhbmdlIHdoaWNoIHdhcyByZWZ1c2VkIGJ5
> > > > IHRoZQogICAgdXBzdHJlYW0gbWFpbnRhaW5lci4gTm93IHVzZXJzIG11c3QgYXJyYW5nZSBmb3Ig
> > > > dGhlIGV0aGVybmV0CiAgICBpbnRlcmZhY2UgdXNlZCBmb3IgUFBQb0UgdG8gYmUgdXAuCiAgKiBU
> > > > aGUgUFBQb0EgcGx1Z2luIGRvZXMgbm90IHJlcXVpcmUgYW55bW9yZSB0aGUgbGliYXRtMSBwYWNr
> > > > YWdlIHRvIGJlCiAgICBpbnN0YWxsZWQuCgogLS0gTWFyY28gZCdJdHJpIDxtZEBsaW51eC5pdD4g
> > > > IFN1biwgMjAgRmViIDIwMDUgMjA6MzQ6MDAgKzAxMDAK
> > > >
> > > > &
> > >
> > > Well, as you can see by the header, it's base64-encoded.
> >
> > But uudecode couldn't decode it...
> >
> uudecode only decodes uuencoded messages.
> What mail client are you using? Mutt and most others can handle
> mime-encoded messages. Or you can decode with munpack.
just plain old 'mail'
michael@ratty:~/MM5/REGRID/pregrid$ file `which mail`
/usr/bin/mail: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
for GNU/Linux 2.2.0, dynamically linked (uses shared libs), stripped
but why the Dickens is it encoded in the first place?!
Reply to: