User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 GTB7.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1 Just downloaded TB 3.1 and have the following issue. I have an email with an nzb file as the attachment. TB 3.1 wants to treat it as an xml file and open internet explorer. I have changed it to open Newsbin (nbpro.exe) and it opens Newsbin and does nothing. On TB 2.0.0.24 a box pops up and says "You have chosen to open _ _ _.nzb which is a: Newsbin NZB file. I double click the icon and Newsbin proceeds to download the corresponding files. TB 3.1 is still treat the NZB file as XML. Reproducible: Always Steps to Reproduce: 1.I renamed mimetypes.rdf and it treats the file as XML. I brought over the good mimetypes.rdf from the computer running TB2 and still no luck. The difference in TB2 is that the NZB file openes the Newsreader and downloads the files within the NZB. On TB3, I pick the Newsbin program and does not begin the file download. So, it basically just opens Newsbin and nothing else happens. 2. 3. Actual Results: Newsbinpro opens and just sits there. The command line that works correctly on my other computer is: Expected Results: Newsbinpro should open and execute the newsbin file. TB2: (Good one) "C:\Program Files\NewsBin\nbpro.exe" "C:\DOCUME~1\David\LOCALS~1\Temp\_ _ _ _ _.nzb" BOTH TB2 & TB 3 have the EXACT information: ------_=_NextPart_001_01CB1207.DF46BA6D Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <<Automatic sample.nzb>> =20 Your message is ready to be sent with the following file or link attachments: Automatic sample.nzb Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled. ------_=_NextPart_001_01CB1207.DF46BA6D Content-Type: application/octet-stream; name="sample.nzb" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="sample.nzb" I delete the mimetypes.rdf and I click open on the NZB file. The Open Sample.nzb opens and says: You have chosen to open Sample.nzb which is a: XML Document from: mailbox:// What should TB do with this file? (Defaults to: Internet Explorer BTW: My default browser is Firefox) I choose other and up pops a box that says: XML Document Sample.nzb Send this item to: (I choose NewsbinPro Reader) It proceeds to open NewsbinPro Reader and stops. In Process Explorer the Command line reads: Here are the command lines: "C:\Program Files\NewsBin\nbpro.exe" Is this a bug in 3.1? I have tried several NZB's in TB 2 and it works flawlessly. 3.1 wants to treat the NZB file as strictly XML. I can choose Firefox and open the NZB and the code print out fine on a web page.

To add from the forum thread: The NZB format apparently is an XML-based format. Thus, when sent as application/octet-stream, the difference may be that some guessing for that generic MIME type results in detection of XML prior to the operating system's File Type table being consulted to determine the actually register application and description. The problem with the missing command-line argument (reporter has verified that OS definition contains %1 to provide the file to open as parameter) may be a related or separate issue, thus may have to be spun off into a separate bug, but let's keep this as a single issue for now. The attachment was apparently sent using SimpleMAPI on Windows, based on the message's introductory text.

Just an FYI. I tried a different Newsreader called Forte Agent. When trying to launch the NZB for TB3 it got the error "C:\Program Files\Agent\agent.exe" "C:\DOCUME~1\David\LOCALS~1\Temp\_ _ _ _ _.nzb.xml" "CANNOT RECOGNIZE THE XML FILE." So it's got to be TB3. TB3 is treating it as XML instead of NZB.

Interesting that it actually adds an ".xml" to the file name, that's not supposed to happen. When you say "TB3" you mean 3.1, correct? Or did you install 3.0 to see if the problem existed already in earlier versions?

(In reply to comment #3) > Interesting that it actually adds an ".xml" to the file name, that's not > supposed to happen. When you say "TB3" you mean 3.1, correct? Or did you > install 3.0 to see if the problem existed already in earlier versions? Yes this is TBird 3.1

Here is a sample of an NZB file.

(In reply to comment #3) > Interesting that it actually adds an ".xml" to the file name, that's not > supposed to happen. Checked with next data using Tb 3.1 on MS Win-XP. .CSV is associated to Lotus 1-2-3 in Win's registory. > --Part_0 > Content-Type: application/octet-stream > Content-Disposition: attachment; filename="pre-001-txt.csv" > > yyy Notepad is pre-selected %temp%\temp\pre-001-txt.csv.txt > --Part_0 > Content-Type: application/octet-stream > Content-Disposition: attachment; filename="pre-002-html.csv" > > <html>abcdefg Firefox is is pre-selected %temp%\temp\pre-002-html.csv.htm > --Part_0 > Content-Type: application/octet-stream > Content-Disposition: attachment; filename="pre-003-xml.csv" > > <?xml version="1.0" encoding="iso-8859-1" ?> Seamonkey is is pre-selected %temp%\temp\pre-003-xml.csv.xml > --Part_0 > Content-Type: application/octet-stream > Content-Disposition: attachment; filename="pre-004-bin.csv" > Content-Transfer-Encoding: quoted-printable > > =20=20=0D=0A=00=00 Lotus 1-2-3 is is pre-selected %temp%\temp\pre-004-bin.csv File extention associated to sniffed content-type is added to temporary file name which is passed to application. Workaround: > http://www.filesuffix.com/extension/nzb.html If association between .NZB and application/x-nzb is NOT registrated to system. Create next part in a mail, double click the attachmennt, choose an application with checking "Do this automticall..." to force creation of Tools/Options/Attachments entry. > --Part_0 > Content-Type: application/x-nzb > Content-Disposition: attachment; filename="abc.NZB" > Content-Transfer-Encoding: quoted-printable > > =00=00 If association between .NZB and application/x-nzb is registrated to system. Create next part in a mail, double click the attachmennt, choose an application with checking "Do this automtically..." to force creation of Tools/Options/Attachments entry. And, edit mimeTypes.rdf, change X-application/x-nzb to application/x-nzb. > --Part_0 > Content-Type: X-application/x-nzb > Content-Disposition: attachment; filename="abc.NZB" > Content-Transfer-Encoding: quoted-printable > > =00=00

(In reply to comment #0) > I have an email with an nzb file as the attachment. > TB 3.1 wants to treat it as an xml file and open internet explorer. Confirmed by my testing. > I have changed it to open Newsbin (nbpro.exe) and it opens Newsbin and does nothing. Does nbpro.exe correctly process file of .nzb extension only? Even though many applications on Win(and some on Linux too) base on file extension only, many other applications don't base on file extension only which is merely a part of file name.

You can click on an NZB file outside of Thunderbird 3.1 and it will process the file (If Newsbin is you default program for NZB files). It also works correctly under Thunderbird 2.0.0.24. I have 2 computers each running old version on one and the new version on another. Please read http://forums.mozillazine.org/viewtopic.php?f=39&t=1935179 to get the ENTIRE history.

(In reply to comment #8) Please never assume that file extension of ".NZB" is associated to nbpro.exe on any PC and nbpro.exe is installed on any PC. My question was; If valid xxx.NZB file is renamed to xxx.NZB.XML, can nbpro.exe open the xxx.NZB.XML file as NZB file? (open the renamed xxx.NZB.XML file from file menu of nbpro.exe. ) (I guess nbpro.exe rejects it because file extension is not .NZB.)

I have 2 programs that execute NZB files: 1. Forte Agent 2. Newsbin Pro Newsreader BOTH programs can execute an NZB file from an email using TBird 2.0.0.24. They BOTH will NOT execute the file from TBird 3.1 because of this version adding the 'XML' onto the end of the filename.

(In reply to comment #10) > I have 2 programs that execute NZB files: > 1. Forte Agent > 2. Newsbin Pro Newsreader > > BOTH programs can execute an NZB file from an email using TBird 2.0.0.24. > > They BOTH will NOT execute the file from TBird 3.1 because of this version > adding the 'XML' onto the end of the filename. (I can do a 'Save as' and save it to the HD and execute from that location. I cannot execute from an attachment within Tbird 3.1)

There has not been any progress since my last comments. Can someone look into this bug? Thank You David Theuerl

David Theuerl(bug opener), have you tried workaround I wrote in comment #6?

OK... Here is the version before I tried your fix and it didn't work. Please edit my mimetypes.rdf I tried but this is what my mimetypes.rdf looks like: <?xml version="1.0"?> <RDF:RDF xmlns:NC="http://home.netscape.com/NC-rdf#" xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <RDF:Description RDF:about="urn:root" NC:en-US_defaultHandlersVersion="-1" /> <RDF:Description RDF:about="urn:handler:local:C:\Program Files\NewsBin\nbpro.exe" NC:prettyName="nbpro.exe" NC:path="C:\Program Files\NewsBin\nbpro.exe" /> <RDF:Description RDF:about="urn:mimetype:handler:text/xml" NC:alwaysAsk="false"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:text/xml"/> <NC:possibleApplication RDF:resource="urn:handler:local:C:\Program Files\NewsBin\nbpro.exe"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:externalApplication:text/xml" NC:prettyName="nbpro.exe" NC:path="C:\Program Files\NewsBin\nbpro.exe" /> <RDF:Seq RDF:about="urn:schemes:root"> </RDF:Seq> <RDF:Seq RDF:about="urn:mimetypes:root"> <RDF:li RDF:resource="urn:mimetype:text/xml"/> <RDF:li RDF:resource="urn:mimetype:image/jpeg"/> </RDF:Seq> <RDF:Description RDF:about="urn:mimetype:image/jpeg" NC:value="image/jpeg" NC:editable="true" NC:description="JPEG Image"> <NC:fileExtensions>jpg</NC:fileExtensions> <NC:fileExtensions>jpeg</NC:fileExtensions> <NC:fileExtensions>jfif</NC:fileExtensions> <NC:fileExtensions>pjpeg</NC:fileExtensions> <NC:fileExtensions>pjp</NC:fileExtensions> <NC:handlerProp RDF:resource="urn:mimetype:handler:image/jpeg"/> </RDF:Description> <RDF:Description RDF:about="urn:schemes"> <NC:Protocol-Schemes RDF:resource="urn:schemes:root"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:text/xml" NC:value="text/xml" NC:editable="true" NC:fileExtensions="xml" NC:description="XML Document"> <NC:handlerProp RDF:resource="urn:mimetype:handler:text/xml"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:externalApplication:image/jpeg" NC:path="C:\Program Files\QuickTime\PictureViewer.exe" NC:prettyName="PictureViewer.exe" /> <RDF:Description RDF:about="urn:mimetype:handler:image/jpeg" NC:alwaysAsk="true" NC:saveToDisk="false" NC:useSystemDefault="false" NC:handleInternal="false"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:image/jpeg"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetypes"> <NC:MIME-types RDF:resource="urn:mimetypes:root"/> </RDF:Description> </RDF:RDF>

Please disregard Comment 14 Sending New mimetypes.rdf > OK... > Here is the version before I tried your fix and it didn't work. > > Please edit my mimetypes.rdf > > I tried but this is what my mimetypes.rdf looks like: > > <?xml version="1.0"?> > <RDF:RDF xmlns:NC="http://home.netscape.com/NC-rdf#" > xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> > <RDF:Description RDF:about="urn:root" > NC:en-US_defaultHandlersVersion="-1" /> > <RDF:Description RDF:about="urn:handler:local:C:\Program > Files\NewsBin\nbpro.exe" > NC:prettyName="nbpro.exe" > NC:path="C:\Program Files\NewsBin\nbpro.exe" /> > <RDF:Description RDF:about="urn:mimetype:handler:text/xml" > NC:alwaysAsk="false"> > <NC:externalApplication > RDF:resource="urn:mimetype:externalApplication:text/xml"/> > <NC:possibleApplication RDF:resource="urn:handler:local:C:\Program > Files\NewsBin\nbpro.exe"/> > </RDF:Description> > <RDF:Description RDF:about="urn:mimetype:externalApplication:text/xml" > NC:prettyName="nbpro.exe" > NC:path="C:\Program Files\NewsBin\nbpro.exe" /> > <RDF:Seq RDF:about="urn:schemes:root"> > </RDF:Seq> > <RDF:Seq RDF:about="urn:mimetypes:root"> > <RDF:li RDF:resource="urn:mimetype:text/xml"/> > <RDF:li RDF:resource="urn:mimetype:image/jpeg"/> > </RDF:Seq> > <RDF:Description RDF:about="urn:mimetype:image/jpeg" > NC:value="image/jpeg" > NC:editable="true" > NC:description="JPEG Image"> > <NC:fileExtensions>jpg</NC:fileExtensions> > <NC:fileExtensions>jpeg</NC:fileExtensions> > <NC:fileExtensions>jfif</NC:fileExtensions> > <NC:fileExtensions>pjpeg</NC:fileExtensions> > <NC:fileExtensions>pjp</NC:fileExtensions> > <NC:handlerProp RDF:resource="urn:mimetype:handler:image/jpeg"/> > </RDF:Description> > <RDF:Description RDF:about="urn:schemes"> > <NC:Protocol-Schemes RDF:resource="urn:schemes:root"/> > </RDF:Description> > <RDF:Description RDF:about="urn:mimetype:text/xml" > NC:value="text/xml" > NC:editable="true" > NC:fileExtensions="xml" > NC:description="XML Document"> > <NC:handlerProp RDF:resource="urn:mimetype:handler:text/xml"/> > </RDF:Description> > <RDF:Description RDF:about="urn:mimetype:externalApplication:image/jpeg" > NC:path="C:\Program Files\QuickTime\PictureViewer.exe" > NC:prettyName="PictureViewer.exe" /> > <RDF:Description RDF:about="urn:mimetype:handler:image/jpeg" > NC:alwaysAsk="true" > NC:saveToDisk="false" > NC:useSystemDefault="false" > NC:handleInternal="false"> > <NC:externalApplication > RDF:resource="urn:mimetype:externalApplication:image/jpeg"/> > </RDF:Description> > <RDF:Description RDF:about="urn:mimetypes"> > <NC:MIME-types RDF:resource="urn:mimetypes:root"/> > </RDF:Description> > </RDF:RDF>

Here is the CORRECT mimetypes.rdf PLEASE EDIT THIS ONE: <?xml version="1.0"?> <RDF:RDF xmlns:NC="http://home.netscape.com/NC-rdf#" xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <RDF:Description RDF:about="urn:mimetype:image/jpeg" NC:fileExtensions="jpg" NC:description="LView Pro Image" NC:value="image/jpeg" NC:editable="true"> <NC:handlerProp RDF:resource="urn:mimetype:handler:image/jpeg"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:video/x-ms-wmv" NC:value="video/x-ms-wmv" NC:editable="true" NC:fileExtensions="wmv" NC:description="Windows Media(TM) Video File"> <NC:handlerProp RDF:resource="urn:mimetype:handler:video/x-ms-wmv"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:handler:text/html" NC:useSystemDefault="false" NC:handleInternal="false" NC:alwaysAsk="true" NC:saveToDisk="true"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:text/html"/> </RDF:Description> <RDF:Description RDF:about="urn:root" NC:en-US_defaultHandlersVersion="-1" /> <RDF:Description RDF:about="urn:mimetype:handler:audio/mpeg" NC:alwaysAsk="true" NC:saveToDisk="false" NC:useSystemDefault="false" NC:handleInternal="false"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:audio/mpeg"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:text/html" NC:fileExtensions="htm" NC:description="" NC:value="text/html" NC:editable="true"> <NC:handlerProp RDF:resource="urn:mimetype:handler:text/html"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:externalApplication:application/flv" NC:path="C:\Program Files\Winamp\winamp.exe" NC:prettyName="winamp.exe" /> <RDF:Description RDF:about="urn:mimetype:handler:application/vnd.ms-excel" NC:alwaysAsk="false" NC:useSystemDefault="true"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:application/vnd.ms-excel"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:externalApplication:application/zip" NC:prettyName="" NC:path="" /> <RDF:Description RDF:about="urn:mimetype:externalApplication:image/jpeg" NC:path="C:\lviewpro\lviewpro.exe" NC:prettyName="lviewpro.exe" /> <RDF:Description RDF:about="urn:mimetype:externalApplication:text/xml" NC:path="C:\Program Files\NewsBin\nbpro.exe" NC:prettyName="nbpro.exe" /> <RDF:Description RDF:about="urn:mimetype:handler:image/jpeg" NC:saveToDisk="false" NC:handleInternal="false" NC:alwaysAsk="false" NC:useSystemDefault="true"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:image/jpeg"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:image/gif" NC:value="image/gif" NC:editable="true" NC:fileExtensions="gif" NC:description="LView Pro Image"> <NC:handlerProp RDF:resource="urn:mimetype:handler:image/gif"/> </RDF:Description> <RDF:Seq RDF:about="urn:mimetypes:root"> <RDF:li RDF:resource="urn:mimetype:image/gif"/> <RDF:li RDF:resource="urn:mimetype:text/html"/> <RDF:li RDF:resource="urn:mimetype:image/jpeg"/> <RDF:li RDF:resource="urn:mimetype:audio/mpeg"/> <RDF:li RDF:resource="urn:mimetype:video/x-ms-wmv"/> <RDF:li RDF:resource="urn:mimetype:application/vnd.ms-excel"/> <RDF:li RDF:resource="urn:mimetype:application/zip"/> <RDF:li RDF:resource="urn:mimetype:application/flv"/> <RDF:li RDF:resource="urn:mimetype:text/xml"/> </RDF:Seq> <RDF:Description RDF:about="urn:mimetype:application/zip" NC:value="application/zip" NC:editable="true" NC:fileExtensions="zip" NC:description="WinZip File"> <NC:handlerProp RDF:resource="urn:mimetype:handler:application/zip"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:externalApplication:image/gif" NC:prettyName="firefox.exe" NC:path="C:\Program Files\Mozilla Firefox\firefox.exe" /> <RDF:Description RDF:about="urn:mimetype:externalApplication:audio/mpeg" NC:path="C:\Program Files\Winamp\winamp.exe" NC:prettyName="winamp.exe" /> <RDF:Description RDF:about="urn:mimetype:application/flv" NC:value="application/flv" NC:editable="true" NC:description=""> <NC:handlerProp RDF:resource="urn:mimetype:handler:application/flv"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:handler:text/xml" NC:alwaysAsk="false" NC:saveToDisk="false" NC:useSystemDefault="false" NC:handleInternal="false"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:text/xml"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:application/vnd.ms-excel" NC:value="application/vnd.ms-excel" NC:editable="true" NC:fileExtensions="xls" NC:description="Microsoft Excel Worksheet"> <NC:handlerProp RDF:resource="urn:mimetype:handler:application/vnd.ms-excel"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:externalApplication:text/html" NC:path="C:\Program Files\Mozilla Thunderbird\thunderbird.exe" NC:prettyName="thunderbird.exe" /> <RDF:Description RDF:about="urn:mimetype:text/xml" NC:value="text/xml" NC:editable="true" NC:fileExtensions="xml" NC:description="XML Document"> <NC:handlerProp RDF:resource="urn:mimetype:handler:text/xml"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:externalApplication:video/x-ms-wmv" NC:path="C:\Program Files\Media Player Classic\mplayerc.exe" NC:prettyName="mplayerc.exe" /> <RDF:Description RDF:about="urn:mimetype:handler:application/zip" NC:alwaysAsk="true" NC:saveToDisk="true"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:application/zip"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:handler:video/x-ms-wmv" NC:alwaysAsk="true" NC:saveToDisk="false" NC:useSystemDefault="false" NC:handleInternal="false"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:video/x-ms-wmv"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:audio/mpeg" NC:value="audio/mpeg" NC:editable="true" NC:fileExtensions="mp3" NC:description="MP3 Audio"> <NC:handlerProp RDF:resource="urn:mimetype:handler:audio/mpeg"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:handler:application/flv" NC:alwaysAsk="true" NC:saveToDisk="false" NC:useSystemDefault="false" NC:handleInternal="false"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:application/flv"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:externalApplication:application/vnd.ms-excel" NC:prettyName="" NC:path="" /> <RDF:Description RDF:about="urn:mimetypes"> <NC:MIME-types RDF:resource="urn:mimetypes:root"/> </RDF:Description> <RDF:Description RDF:about="urn:mimetype:handler:image/gif" NC:alwaysAsk="false" NC:handleInternal="false" NC:useSystemDefault="false" NC:saveToDisk="false"> <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:image/gif"/> </RDF:Description> </RDF:RDF>

Never paste long data, please. Save in a file and attach to bug, please.

Attached is my mimetypes.rdf

Did you set "always use this application" by original NZB file attachment? Did you put quoted-printable and put data of =00 to force binary correctly? Did you change mail source and execute "Repair folder" correctly? Or did you save in .eml, edit .eml, import by Drag&Drop of .eml to thread pane? Try next, please. (1) Terminate Tb, delete mimeTypes.rdf, Restart Tb. (2) Save original mail of NZB file attachment in a .eml file. (3) Edit the .eml file. Set X-application/x-nzb as Content-Type:, set quoted-printable, put =00 as quoted-printable data (4) Create a local mail folder, open the mail folder, Drag&Drop the .eml file to thread pane => mail is imported (5) Double click the NZB attachment, force creation of mimeTypes.rdf entry. (6) Terminate Tb, edit mimeTypes.rdf, change all dummy X-application/x-nzb to correct application/x-nzb. (7) Restart Tb, try to open NZB atachment in original mail. (8) To recover setting for xls, mp3 etc., do next again for each file type. Open a valid attachment, select application, check "always use this application" to force creation of mimeTypes.rdf entry. (9) After that, check all entries at Tools/Options/Attachments.

(In reply to comment #19) I'm sorry, but this is way over my head. > Did you set "always use this application" by original NZB file attachment? YES... > > Did you put quoted-printable and put data of =00 to force binary correctly? I do not understand > Did you change mail source and execute "Repair folder" correctly? > Or did you save in .eml, edit .eml, import by Drag&Drop of .eml to thread pane? I edited the rdf file with notepad. > > Try next, please. > (1) Terminate Tb, delete mimeTypes.rdf, Restart Tb. > (2) Save original mail of NZB file attachment in a .eml file. (????) > (3) Edit the .eml file. Set X-application/x-nzb as Content-Type:, > set quoted-printable, put =00 as quoted-printable data > (4) Create a local mail folder, open the mail folder, > Drag&Drop the .eml file to thread pane => mail is imported > (5) Double click the NZB attachment, force creation of mimeTypes.rdf entry. > (6) Terminate Tb, edit mimeTypes.rdf, > change all dummy X-application/x-nzb to correct application/x-nzb. > (7) Restart Tb, try to open NZB atachment in original mail. > > (8) To recover setting for xls, mp3 etc., do next again for each file type. > Open a valid attachment, select application, check "always use this > application" to force creation of mimeTypes.rdf entry. > (9) After that, check all entries at Tools/Options/Attachments.

(In reply to comment #20) > > (2) Save original mail of NZB file attachment in a .eml file. > (????) View original mail to which NZB file is attached. "Save As", select "Mail File" at file type field of file picker dialog, specify file extension of .eml explicitly at file name field, and save.

Confirmig.

Ok, so we do have a bug. David, what WADA is proposing to establish a rule in mimeTypes.rdf associating the correct MIME type with the file extension "nzb", which doesn't have any entry in your posted attachment 457230 [details]. The assumption is that an explicit "nzb" entry in mimeTypes.rdf will override the build-in scheme for XML, which in turn overrides your existing OS setting. This would be much easier if bug 503303 was implemented already, but it isn't, therefore the rather indirect method stated in comment #19 is necessary. Rather than deleting mimeTypes.rdf, just rename it to have a backup copy (on the other hand, you posted it here, so that's equally well your backup). To rephrase this workaround: 1. Take an affected message with an NZB attachment 2 [review]. Save it on disk using File > Save As > File, make sure it ends in .eml 3. Use a text editor to edit *this* file (you are not editing mimeTypes.rdf) 4. Find the heading indicating the start of the NZB attachment: ------_=_NextPart_001_01CB1207.DF46BA6D Content-Type: application/octet-stream; name="sample.nzb" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="sample.nzb" 5. Change the 1st and 3rd headers into the following, per comment #6: ------_=_NextPart_001_01CB1207.DF46BA6D Content-Type: X-application/x-nzb; name="sample.nzb" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="sample.nzb" 6. The next line should be empty, then the data follows; replace the 1st line of the data entirely with the following entry (no leading spaces): =00=00 7. Delete everything below that line until you reach the end marker, which you have to keep intact: ------_=_NextPart_001_01CB1207.DF46BA6D-- 8. Save the message. 9. Start Thunderbird and open the .eml file with File > Open Saved Message. Now continue with #5 of WADA's list. Make sure to check "Do this always" in the dialog when opening the attachment, thus establishing the mimeTypes.rdf rule. I'm not sure if it is really necessary to start off an empty mimeTypes.rdf, but it sure makes it easier to edit manually if no other entries interfere. I hope that this makes the procedure a bit clearer for you, otherwise either of us can further walk you through. As said, this is unnecessarily complicated, but has to be done manually until the other bug is resolved.

Thank you 'rsx11m' for explaining in easier terms. This worked out perfectly. The NZB files are now opening in my Newsbin Newsgroup reader program. Thanks to the BOTH of you for this fix. My only 2 questions are will this bug be resolved in future updates? Will I need to do anything special since I've 'tweaked' my Thunderbird? Maxdout38 David

(In reply to comment #24) > This worked out perfectly. > The NZB files are now opening in my Newsbin Newsgroup reader program. Did you do next step? > (6) Terminate Tb, edit mimeTypes.rdf, > change all dummy X-application/x-nzb to correct application/x-nzb. If not, your .NZB file will be sent with "Content-Type: X-application/x-nzb" when you send a mail with attaching .NZB file. It'll produce problem in mail recipient's Thunderbird.

Made the correction and sent the file to another computer. The file opened and executed perfectly. I'll let you mark it resolved if you think the takes care of the issue.

WADA, are we sure that this should just be resolves as "works for me" after finding a workaround for David? I'm wondering if it is the correct behavior to just forgo whatever the operating system has registered and just use the internal guessing algorithm for an application/octet-stream attachment where no mimeTypes.rdf definition exists. Then, there is also the issue of adding a (wrong) file extension to the attachments name, confusing the target application. I'd think that this is still a valid bug and the right behavior should be defined for such cases...

rx11m, I agree with you. This bug can occur on any text data such as .ps file saved in text data mode, dxf file, ..., if sent with application/octet-stream. In many cases, application won't open file if ".txt" is appended to passed file name. Tb should check mime-type associated to specified file extension, and if registrated to system, Tb shouldn't add file extention of ".txt" or ".xml" or ".htm/.html" which is based on sniffing of content. However, this bug can be permanent restriction of quirks for application/octet-stream, if quirks for application/octet-stream is optional, and if the restriction is well documented. File extension is merely a part of file name for convenience. Cultprit is "Relying on file extention only" which was produced by MS.

First order of business is probably to identify which patch caused the change in behavior, then figuring from the reasoning there if a conflict of different use cases exists and how they can be reconciled if necessary.

FYI. Checked test case in comment #6(.CSV file, text, html, xml data) with Tb 3.0.5. > Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 For any data type, Lotus 1-2-3(associated to .CSV in Windows regstry) was pre-selected, and file extention of .txt/.html/.xml was not added to passed file name. FIXED bugs which has application/octet-stream in bug summary, changed within 6 months. > bug 327323 File Han Can't "Open with" files that are send as application/octet-stream (or other "unknown to firefox" mime types) > bug 455472 DOM [FIX]code injection with Content-Type: application/octet-stream, embed and svg - no plugins required > bug 532603 MIME plain text attachment with application/octet-stream Content-Type does not shown inline > bug 538407 Message Attachments are not accessible for 'Content-Type:application/octet-stream, Content-Disposition:inline;filename="xxxx.yyy"', if mime-type for ".yyy" is unknown

If this helps, the attachment opened fine in TB 2.0.0.24. My first upgrade from this version was to TB 3.1 I never used anything in between these (2) versions.

Gary any bandwidth for regression hunting ?

I updated to TB 3.1.1 and the fix is still in place.