🚀 go-pugleaf

A freind of mine recently received the following as an e-mail. He didn't
know what to make of it so he decided to pass it onto to me (me
foolishly thinks that I know a lot about this stuff). Could someone give
me some advice on what this is and how it should be decoded, its' not
uuencoded - which is what I thought it may be. 

It starts........
--------------5A7E536668DB
Content-Type: application/octet-stream; name="Carvel.let"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Carvel.let"

/1dQQ3AEAAABCgIBAAAAAgUAAACdDAAAAAIAABOQD+io6vhbC6RtRtt7Dwmbt0ZwnnuKZMwl
2G4wFET7WbXvCAxbb/6j5CjN5/9Ml1RjpUQWxP5ZZx6vHcjOSiMiUU8vYKOOCTAPDYHpP2gg
66y3a1mR2VHoFTHK1KGulMx047w2sE+rifRgiiCo51t1GtIgy6rg129f27dVzqOxPhZ71WGj
.
.
.
.
.
aXJtYW6AYW5kgEZvdW5kZXLMzGNjOuARDAAAAAAIBwwA4EtldmlugENvbGXQBBUAAAsACQAB
8B5AGhwAASAVANDgEQwAAAAACAcMAOBIQULM4BEMAAAAAAgHDADgSmltbXmAS2luZ8zgEQwA
AAAACAcMAOBCb2KAQ3VzaG1hbszgEQwAAAAACAcMAOBFcm5zdIBIYWdlcg==
--------------5A7E536668DB--

The header also conatins stuff like this at the top;
Content-Type: multipart/mixed; boundary="------------5A7E536668DB"

This is a multi-part message in MIME format.

--------------5A7E536668DB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Thanks in advance,

david
-- 
David K McWilliams                            davidmcw@albion-auto.co.uk
                     Cole's Law: Thinly Slice Cabbage
Remove $ from sig to reply via e-mail