Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Will not open .tab file attachments

  • 4 wotmołwy
  • 1 ma tutón problem
  • 17 napohladow
  • Poslednja wotmołwa wot fischer9

fischer9
fischer9
more options

I am using TB 91.4.1 (64-bit) on a windows 10 system and I am unable to open file attachments that end in .tab. TB gives me the options to open, save, detach or delete. When I select open, nothing happens. The file icon is Notepad, which is the default windows app for .tab files. I am able to save the file and then open it from windows explorer it but I can not open it from within TB like I can .pdf, .png, .cvs, and many other file types.

I have tried closing TB and deleting the mimeTypes.rdf file as well as repairing the folder and it still will not open the .tab file.

I am using TB 91.4.1 (64-bit) on a windows 10 system and I am unable to open file attachments that end in .tab. TB gives me the options to open, save, detach or delete. When I select open, nothing happens. The file icon is Notepad, which is the default windows app for .tab files. I am able to save the file and then open it from windows explorer it but I can not open it from within TB like I can .pdf, .png, .cvs, and many other file types. I have tried closing TB and deleting the mimeTypes.rdf file as well as repairing the folder and it still will not open the .tab file.

Wubrane rozrisanje

I did a test: exported an address book in tab delimited .tab format and attached it to a message. The source indicates the Content-Type: text/plain. When I Open the attachment, I get the attached picture, which makes sense with my default text editor. A content-type: application/octet-stream is probably part of the problem:

http://kb.mozillazine.org/Actions_for_attachment_file_types#application.2Foctet-stream

Note that I have the preference mail.strictly_mime set to true in Config. editor, which forces 7-bit (quoted-printable) format, which might make a difference. Also, try sending yourself a message with a .tab attachment from an account that encodes them with the correct content-type, as not all providers handle attachments the same way.

Tutu wotmołwu w konteksće čitać 👍 1

Wšě wotmołwy (4)

sfhowes
sfhowes
  • Top 10 Contributor
more options

Try deleting handlers.json, the replacement for the obsolete mimeTypes.rdf.

Open the source (Ctrl+U) and look at the Content-type header for the attachment.

fischer9
fischer9 Prašer
more options

The content-type is application/octet-stream; which should work. When I send myself, though TB, a tab delimited file, TB assigns the same content-type and TB does nothing when I try to open the file attachment.

Also, I deleted handlers.jason and it did not resolve the issue.

sfhowes
sfhowes
  • Top 10 Contributor
more options

Wubrane rozrisanje

I did a test: exported an address book in tab delimited .tab format and attached it to a message. The source indicates the Content-Type: text/plain. When I Open the attachment, I get the attached picture, which makes sense with my default text editor. A content-type: application/octet-stream is probably part of the problem:

http://kb.mozillazine.org/Actions_for_attachment_file_types#application.2Foctet-stream

Note that I have the preference mail.strictly_mime set to true in Config. editor, which forces 7-bit (quoted-printable) format, which might make a difference. Also, try sending yourself a message with a .tab attachment from an account that encodes them with the correct content-type, as not all providers handle attachments the same way.

fischer9
fischer9 Prašer
more options

I must have been the content-type. Since its the output of a script that I wrote, I converted the output to csv and it opens properly.

Thanks for your help.

Wot fischer9 změnjeny