Hello Simon, Sunday, November 30, 2003. 12:36:30 PM. you wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > Hello Adrian, > On Fri, 28 Nov 2003 10:57:48 +0000 your time, you said: AJM>> I've received attachments from a Mac user (using Word for Mac). I AJM>> have been unable to read them. I think the problem is caused by AJM>> illegal characters such as "/" being used in the file name. AJM>> I'm using 2.01.3 set to "keep attachment files in message bodies". > If you need them desperately then you could try this: > 1. Export email to .msg format > 2. Open the .msg file in a text editor (without wordwrap on). > 3. Look for the base64 encoded file by looking for the > MIME boundary declaration in the message. Here is an example: > - --begin example > - ------------10E4A19720729F06 > Content-Type: image/gif; name="routeradmin.gif" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; filename="routeradmin.gif" > R0lGODlhAAUABPcAAAAAAH8AAAGBAICAAAABqIAAgAB+gMC+tcLZv6bJ8QAAAAEE3wIcdgY1qAAe > yQNE5AJSsQF4PwJ4cQV7pwOHUwCJWgGPcQKcAQsMDREVGwkZQA8yZg86gwNcTRtPwghhzAlvBwh1 > <..the rest of base64 encoded image snipped..> > - --end example > 4. change the filename after the "name=" part and the "filename=" part > so that they are the same name; IOW change the original filename to > newfile.ext, where 'newfile' is anything you like, and ext is whatever > the file extension should be. > - - btw: it will be these original filenames that contain the offending > characters so you are simply removing the offending characters and > adding something sensible ;-). > 5. Save the file. Close it and import it back into TB! > It's a workaround at least. Hope it works :-) Thanks for the suggestion. It worked a treat. In fact, I opened a new Temp folder in to which I copied the offending email. It was then easy to export it, edit as you suggested to get rid of the illegal characters and then re-import it. The resultant was text that I could read without the slightest difficulty. To ask you another question. It appears to me that TheBat does not like attachments without an extenion. I had one which, when I tried to open it I got the message "no application is associated with the specified file for this operation". When I added a .doc extension I could handle it without any problems. Is there something I can do to make such attachments more readily accessible? -- Best regards Adrian J Morant mail:[EMAIL PROTECTED] ________________________________________________ Current version is 2.01.3 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
