I have an email with an attachment which will not open in OO. When the email is opened in a text editor I get this after the body of the message. Is there any way to open and read this?
Trying to open the attachment in OO just gives an error.
Al
------=_NextPart_001_0041_01CC115D.F6E27A10--
------=_NextPart_000_0040_01CC115D.F6E27A10 Content-Type: application/msword; name="xxxx.doc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xxxx.doc"
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAPgAAAAAAAAAA EAAAQAAAAAEAAAD+////AAAAAD0AAAD///////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////????//////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// ///////////////////////////////////////////////////////////////////////////s pcEAA4AJBAAA8BK/AAAAAAAAEAAAAAAACAAAFg0AAA4AYmpiarRWtFYAAAAAAAAAAAAAAAAAAAAA AAAJBBYANSoAANY8AQDWPAEAFgUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAA????AAAAALcAAAAAAIAFAAAAAAAAgAUAAMMS AAAAAAAAwxIAAAAAAADDEgAAAAAAAMMSAAAAAAAAwxIAABQAAAAAAAAAAAAAAP////8AAAAA1xIA AAAAAADXEgAAAAAAANcSAAAAAAAA1xIAAAwAAADjEgAAbAAAANcSAAAAAAAAYBgAAHQBAABPEwAA AAAAAE8TAAAAAAAATxMAAAAAAABPEwAAAAAAAE8TAAAAAAAAKhQAAAAAAAAqFAAAAAAAACoUAAAA
On 31/10/12 09:20, Peter Alcibiades wrote:
I have an email with an attachment which will not open in OO. When the email is opened in a text editor I get this after the body of the message. Is there any way to open and read this?
You can copy-and-paste the blob of data to a temporary file and run "base64 -d blob.txt" (as the attachment is base64-encoded). However, I've tried it and it decodes some of it and then reports "invalid input".
It actually looks a bit small to be a complete Word document (Content-Type: application/msword; name="xxxx.doc"). I created a .doc file with nothing more than the word "test" in it and it saved out at about 9Kb (this was via OO, so probably a bit different from an MS original, but still ball-park). The blob of data you have decodes to 283 bytes (before it barfs), so it really does look like it's corrupted and is really missing a good chunk of the attachment (the odd length of line 5 is perhaps a hint).
Hth, Simon
Trying to open the attachment in OO just gives an error.
------=_NextPart_001_0041_01CC115D.F6E27A10--
------=_NextPart_000_0040_01CC115D.F6E27A10 Content-Type: application/msword; name="xxxx.doc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xxxx.doc"
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAPgAAAAAAAAAA EAAAQAAAAAEAAAD+////AAAAAD0AAAD///////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////????//////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// ///////////////////////////////////////////////////////////////////////////s pcEAA4AJBAAA8BK/AAAAAAAAEAAAAAAACAAAFg0AAA4AYmpiarRWtFYAAAAAAAAAAAAAAAAAAAAA AAAJBBYANSoAANY8AQDWPAEAFgUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAA????AAAAALcAAAAAAIAFAAAAAAAAgAUAAMMS AAAAAAAAwxIAAAAAAADDEgAAAAAAAMMSAAAAAAAAwxIAABQAAAAAAAAAAAAAAP////8AAAAA1xIA AAAAAADXEgAAAAAAANcSAAAAAAAA1xIAAAwAAADjEgAAbAAAANcSAAAAAAAAYBgAAHQBAABPEwAA AAAAAE8TAAAAAAAATxMAAAAAAABPEwAAAAAAAE8TAAAAAAAAKhQAAAAAAAAqFAAAAAAAACoUAAAA
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On 31 Oct 10:06, Simon Ransome wrote:
On 31/10/12 09:20, Peter Alcibiades wrote:
I have an email with an attachment which will not open in OO. When the email is opened in a text editor I get this after the body of the message. Is there any way to open and read this?
You can copy-and-paste the blob of data to a temporary file and run "base64 -d blob.txt" (as the attachment is base64-encoded). However, I've tried it and it decodes some of it and then reports "invalid input".
Making it so that the base64 parses at least lets you know that it's corrupt, it does appear to be a word doc, of some type, but it's not pretty.
I'd get the sender to try again, unless it was spam ;)
On Wednesday 31 October 2012 10:06:39 Simon Ransome wrote:
On 31/10/12 09:20, Peter Alcibiades wrote:
I have an email with an attachment which will not open in OO. When the email is opened in a text editor I get this after the body of the message. Is there any way to open and read this?
You can copy-and-paste the blob of data to a temporary file and run "base64 -d blob.txt" (as the attachment is base64-encoded). However, I've tried it and it decodes some of it and then reports "invalid input".
Many thanks for this, I'll have a go. I should have said that the quoted bit was only part of the file to give an illustration of the problem. You're right that it is truncated.
I'll have a go with 'base64-d....'
This is for a client lloosely speaking who has had some documents deleted from the hard drive by a former employee. Its turned out to be possible to recover an archive containing many emails, but the attachments to them have resisted decoding, and this was one.
The documents are .eml. They can be read in a text editor or in a mail reader, and the attachments are then visible, and can be saved, but they cannot be opened.
Before getting this reply, I found a Perl module that had some success. The text did appear, with no formatting and buried in a huge mass of non-ascii characters.
I'll have a go with your method today.
Al
-
Brett Parker -
Peter Alcibiades -
Simon Ransome