how can I open a Mac file
Discussion
Here is the header as opened with wordpad....
--Apple-Mail-10-589996907
Content-Transfer-Encoding: base64
Content-Type: application/applefile;
name=COMMS.doc
Content-Disposition: attachment;
filename=COMMS.doc
AAUWBwACAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAJAAAAPgAAAAoAAAADAAAASAAAAAkAAAACAAAA
UQAAAR5XOEJOTVNXRAAAQ09NTVMuZG9jAAABAAAAAQAAAAAAAAAAHgAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAA
AAEAAAAAAAAAAB4Vm8bkAWkAAAAcAB7//w==
--Apple-Mail-10-589996907
Content-Transfer-Encoding: base64
Content-Id: <AB4EF784-9789-442C-9145-677D22D765DB@local>
Content-Type: application/octet-stream;
x-mac-type=5738424E;
x-unix-mode=0644;
x-mac-creator=4D535744;
name=COMMS.doc
Content-Disposition: attachment;
filename=COMMS.doc
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAACAAAAjQAAAAAAAAAA
EAAAjwAAAAEAAAD+////AAAAAIsAAACMAAAA////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
--Apple-Mail-10-589996907
Content-Transfer-Encoding: base64
Content-Type: application/applefile;
name=COMMS.doc
Content-Disposition: attachment;
filename=COMMS.doc
AAUWBwACAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAJAAAAPgAAAAoAAAADAAAASAAAAAkAAAACAAAA
UQAAAR5XOEJOTVNXRAAAQ09NTVMuZG9jAAABAAAAAQAAAAAAAAAAHgAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAA
AAEAAAAAAAAAAB4Vm8bkAWkAAAAcAB7//w==
--Apple-Mail-10-589996907
Content-Transfer-Encoding: base64
Content-Id: <AB4EF784-9789-442C-9145-677D22D765DB@local>
Content-Type: application/octet-stream;
x-mac-type=5738424E;
x-unix-mode=0644;
x-mac-creator=4D535744;
name=COMMS.doc
Content-Disposition: attachment;
filename=COMMS.doc
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAACAAAAjQAAAAAAAAAA
EAAAjwAAAAEAAAD+////AAAAAIsAAACMAAAA////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
Errrr that's an email encoded attachment that hasn't been detached... somewhere in there is a file called COMMS.doc which should be a file your Windows machine will read.
No idea why someone has dumped the raw source of the email (which is exactly what that is). There's nothing Apple-specific about that at all, any mail client when asked to show raw source will show the full SMTP headers.
I'd get the person to send you the email again and detach the attachment.
Edited to add: there's an option in Apple Mail on OS X when attaching files to 'send Windows friendly attachments' - presumably this doesn't send the metadata which could be confusing your mail client. Really, any mail client should handle this properly, but there are two files both called COMMS.doc - the first one will be the Apple metadata and the second one will be the real file. But this doesn't alter how you've got the raw source in the first place, which is *not* an 'Apple' file in any way.
No idea why someone has dumped the raw source of the email (which is exactly what that is). There's nothing Apple-specific about that at all, any mail client when asked to show raw source will show the full SMTP headers.
I'd get the person to send you the email again and detach the attachment.
Edited to add: there's an option in Apple Mail on OS X when attaching files to 'send Windows friendly attachments' - presumably this doesn't send the metadata which could be confusing your mail client. Really, any mail client should handle this properly, but there are two files both called COMMS.doc - the first one will be the Apple metadata and the second one will be the real file. But this doesn't alter how you've got the raw source in the first place, which is *not* an 'Apple' file in any way.
Edited by cyberface on Monday 16th July 19:45
ariel said:
thanks for the replies guys, it is indeed a mail doc.
It's not private as such so can anyone open it for me
if I post it up or is it better forwarded to some kind soul?
Thanks cyberface. so should Outlook open it for me then?
Outlook should do it, or it's shite.It's not private as such so can anyone open it for me
if I post it up or is it better forwarded to some kind soul?
Thanks cyberface. so should Outlook open it for me then?
Edited by ariel on Monday 16th July 19:59
Otherwise, email it over to me and I'll see if I can uudecode the content of the second attachment. Don't post it up, there's all the possibility that the PH code will fiddle with the formatting and mess things up.
Incidentally OS X Mail doesn't have an 'import raw mail' option. If you can connect directly to my SMTP server and send the file verbatim then I'd most probably get it with attachments decoded, but if you're not happy uudecoding things then I don't want you messing with my server

Email it as an attachment but with no body text, let's see what my mail does with it

Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff


