If you have a mail with following header: Content-Type: application/octet-stream; name="att:killer.sys"; Whenever you click on the filename in the dropdown paperclip menu you get and alert: "Unable to save the attachment...." Expected: Able to save the attachment...

jefft - is this yours?

This should be platform specific. You cannot have ":" within your filename on a Windows box.

So, is this behavior correct?

Nope. The application should still have it possible to save the attachment, fx by replacing the problemed chars with other legal chars. Outlook Express replaces ":" with "_"

In build 2000071920 after clicking on the attachment name in the dropdown box you're presented with the "Open/Save Attachment" dialog. Here you select "Save it to disk" and click Ok and nothing happens.

reassigning jefft's bugs to naving

Assign it to fenella@netscape.com

It's now possible. The filename: att:killer.sys gets into: att%3Akiller.sys I'm not sure why the %3A gets there? Why not just show: att:killer.sys as filename?

Linux (2001-02-13-06 mtrunk) win32 (2001-02-13-06 mtrunk) Mac (2001-02-13-04 mtrunk) No problem any more.

now we have this problem again. Choosing either "Save As.." or File -> Attachments -> Save As does absolutly nothing. build 20010717

I can confirm this bug. We need to make the file name safe before trying to save it of event open the file picker. The problem is that the current function for doing that is not Unicode (see bug 41944). This problem occurs with any illegal character in the file name. As the user cannot save the attachment, I consider it as a dataloss. Nominationg nsbeta1.

*** Bug 80235 has been marked as a duplicate of this bug. ***

over to ducarroz

colons get escaped in the filename component of urls because there would otherwise be problems with resolving relative urls (scheme detection). This might have something to do with it. A missing unescape somewhere ... wrong conversion from url to filepath or the other way around maybe.

reassigning to cavin. Will this be helped out by the fix to http://bugzilla.mozilla.org/show_bug.cgi?id=41944?

once 41944 fixed, all we have to do for this bug is to use the new unicode version of NS_MsgHasIfNecessary when we save attachment in nsMessenger::SaveAttachment and in nsMessenger::SaveAllAttachments

Dup of bug 100591?

Right, the fix for bug 100591 will fix this issue as well. *** This bug has been marked as a duplicate of 100591 ***

verified dupe