On Thursday, September 12, 2002, 1:36:01 PM, Dwight wrote: DAC> On Thursday, September 12, 2002, 12:26:55 PM, Eddy wrote:
>> Forwarding a message with a corrupt attachment to a non-TB! user >> always results in an attachment that is perfectly valid for the >> recipient DAC> If the file is alright after it is forwarded, it can't be corrupted DAC> when you get it. Correct. I have said all along that the message is received and stored correctly by TB!, so it is not a network or ISP issue. I believe it is an issue with how TB! "decodes" the attachment when it comes time to actually EXTRACT the attachment for viewing/use. DAC> Where do you store your messages? Do you save them DAC> separately when they come it? Nope. I do not separate out the attachments; I leave them "as is". DAC> In what way are they "corrupted" when you try to use them? In the case of JPEG attachments, clicking the little tab at the bottom of the window that allows you to view the image results in nothing but a blank pane when the attachment is "corrupt". Double-clicking the attachment to view it with TB!'s internal image viewer results in a JPG Err# 11 or JPG Err# 68. Saving the attachment (by dragging the icon from the attachment sidebar, or right-clicking it and choosing "Save") and viewing it in an external viewer, such as IrfanView, ACDSee, Internet Explorer, Photoshop, etc. results in a JPEG image that is partially viewable, and then corrupt at some varying point in the image. Forwarding the mail to a non-TB! user results in a perfectly valid, error-free image, as does exporting and re-importing the message (in most, but not all cases). DAC> What are you trying to do with them when they appear to be DAC> "corrupted"? I'm just trying to "use" whatever attachment is sent to me! .DOC files can't be opened in Word (it complains about the file being corrupt), .PPT files won't open, ZIP files have CRC errors and abort extraction, etc. In _all_ cases, forwarding the message (in many of my tests, I would forward it to my wife's email account; she uses Outlook) results in a perfectly useable file for the recipient. Lately, I've been able to avoid the extra steps associated with forwarding it to her, saving the attachment to one of her shared folders, copying to my computer via the network, etc. by doing the Export/Import trick. But on occasion, even that hasn't worked. I have to believe the problem has to do with how TB! is decoding MIME attachments. If it was anything else (such as corruption in my mailbox folders, etc.) I wouldn't be able to forward or export/import the message and have a useable attachment. So the only explanation is that 100% of the attachment data is there, and decodeable by other mail programs, but _not_ by TB!. Several TB! users have verified my claims after I sent them my "Test" mailbox that contains 2 messages which are corrupt when viewed/saved by TB! but are fine when forwarded to others. Eddy ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
