Description of problem: If I forward an email from a mailing list that is multipart/mixed as an in-line text-only attachment, thunderbird names the attachment with the mailing list information file:///tmp/nsmail-*.tmp. The popular anti-spam software MailScanner considers attachments named *.tmp as bad, causing the attachment to be stripped and the recipient to get a modified copy of the mail with added text about the stripped attachment being "unacceptable". This confuses the recipient and can cause them to question whether the email is legitimate. I downloaded a copy of the Mozilla release of thunderbird, and it names the attachment file:///tmp/nsmail-*.asc, and *.asc is not considered unacceptable by MailScanner. Version-Release number of selected component (if applicable): 1.5.0.10 How reproducible: Always Steps to Reproduce: 1. Forward a multipart/mixed email as an inline text only attachment 2 [details]. 3. Actual results: Signature attachment of original email is named "file:///tmp/nsmail-*.tmp" Expected results: Additional info: I downloaded a copy of the Mozilla release of thunderbird, and it names the attachment file:///tmp/nsmail-*.asc, and *.asc is not considered unacceptable by MailScanner. I looked thru the FC6 source rpm for thunderbird 1.5.0.10 but I could not determine how the name of the attachment was changed from .asc to .tmp.
Created attachment 149879 [details] Sample email that shows this behaviour
Bastien, is this possibly because of s-m-i? There's nothing that we added in thunderbird but i can't seem to find anything that would make it use .tmp in the xml file... In any case, I'm not sure that .asc is the right file extension since it is generally used for encrypted mails IIRC, but is there a better file extension we could choose? .eml?
$ grep tmp freedesktop.org.xml.in $ Does Thunderbird use its own shared-mime-info database? (and are you sure it actually uses it all over?) Nowhere in this mail does it seem to mention the proper mime-type of the signature, or mention the original filenames.
Fedora Core 6 is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora 7, 8, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX. Setting status to NEEDINFO, and awaiting information from the reporter. [This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or Gecko. If you see any other reason, why this bug shouldn't be closed, please, comment on it here.]
Both Fedora 7 and 8 still exhibit this behaviour. Both have the latest patches installed.
At this point, we're going to only be taking security fixes and major stability fixes into this release of Fedora. However, we still want to ensure the bug is fixed in the next version. We'd appreciate if you could test with the latest version of Thunderbird (2.0.0.12) now available for your distribution and provide feedback as to whether the problem still exists so we can file a ticket upstream as soon as possible.
It still does it with F8 and Thunderbird 2.0.0.12.
We found that this bug has been already registered in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=273849) and believe that it is more appropriate to let it be resolved upstream. Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report.