316356 - attachment corrupted at saving (*.DBF converted to text - 0x00 replaced w/ 0x20)

Status: RESOLVED DUPLICATE of bug 317009

(Thunderbird :: Mail Window Front End, defect)

Description

[Tomaz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Build Identifier: Thunderbird version 1.5 (20051025)

*.DBF attachments are obviously treated as text  - all 0x00s are replaced with 0x20 at the time of saving attachement.

-works well with Thunderbird 1.07, but not with 1.5 alpha, beta and RC1
-there is a case when saving attachment works OK (when I sent file to me or maybe text only email or maybe different character coding or different emailer)
-in poshash.zip you have original file, bad file of first degree (changed 0x00 to ox20) and bad file of 2nd degree (additional CRLF at the end)
-in email-poshash.zip you can find two email folders, in one email saving attachement works OK, at other not


Reproducible: Always

Steps to Reproduce:
1.receive email with *.DBF  - dBase 3/4 attachement
2."save as" attachement to local disk


Actual Results:  
all 0x00 bytes in a file are replaced with 0x20
sometimes CR LF is appended at the end of file

Expected Results:  
DBF should be treated as binary file

I have attachements to prove this but can not include them in bugzilla

Comment 1

[Tomaz]

Attachment: original and corrupted files

n poshash.zip you will found:
-original file
-bad file of first degree (changed 0x00 to ox20)
-bad file of 2nd degree (additional CRLF at the end)

Comment 2

[Tomaz]

Attachment: email folders of corrupted attachements

in email-poshash.zip you can find two email folders:
-at test-ok saving attachement POSHASH.DBF works OK
-at test-bad saving attachement POSHASH.DBF corrupts file as described

Comment 3

[Tomaz]

see also similar bug #168098 from 2003, I tried similar workarounds:
-in config set mail.file_attach.binary to true, it helps only halfway, CRLF is not attached anymore to end of file, but 0x00 bytes are still converted to 0x20
-delete mimetypes.rdf in profile dir but it didn't help either

Comment 4

[Mike Cowperthwaite]

The message 'test-bad' does indeed have a corrupted DBF file, but I can't reproduce the steps to generate a corrupted message.  I have 
  mail.file_attach_binary 
set to 'false' but the .DBF file is reliably attached in binary, and when written back out, is byte-identical to the original.  I've tried composing in plain and HTML, using the ISO-8859-1 and the ISO-8859-2 encodings.

One thing to check on your system: do you have .DBF listed as a known file type under   Tools | Options | Attachments | View & Edit Actions   ?    If so, what are the settings for that file extension?

Comment 5

[Tomaz]

Attachment: new email folder test sample - more original

this is original file from where I get corrupted DBF file, I only delete other attachments due to file size (thanks to 1.5) - I tested and delete operation does not hide wrong behaviour.
(previous sample was perhaps already transformed because of forwarding)
It is definitelu repeatable the case, that on the same computer Thunderbird 1.07 works well (attachment equal to original), while 1.5 transforms 0x00 to 0x20.
Try it.
Even more, I think the same failure happens not only at "Save attachment as" but also at "Forward message".

Comment 6

[Tomaz]

(In reply to comment #4)
> The message 'test-bad' does indeed have a corrupted DBF file, but I can't
> reproduce the steps to generate a corrupted message.  I have 
>   mail.file_attach_binary 
> set to 'false' but the .DBF file is reliably attached in binary, and when
> written back out, is byte-identical to the original.  I've tried composing in
> plain and HTML, using the ISO-8859-1 and the ISO-8859-2 encodings.

Message was composed with Outlook and it seems this failure does not happen when composed with Thunderbird. But the problem is at receiving side, saving attachment on the same message works well with TB 1.07 but not with 1.5. The point is not in composing, but on receiving side.
It might be that composing/sending with Outlook triggers this failure at receiving in 1.5.

> 
> One thing to check on your system: do you have .DBF listed as a known file type
> under   Tools | Options | Attachments | View & Edit Actions   ?    If so, what
> are the settings for that file extension?
> 

No, even empty after deleted mimetypes.rdf, prev it was one record but not DBF one.

Comment 7

[Jacquet, Olivier]

I have the same problem. The saved .dbf file is corrupted. If I can help in any way, mail me.

Thunderbird version I have: 1.5 (20051025)

Comment 8

[Tomaz]

*** This bug has been marked as a duplicate of 317009 ***