Comment 16 for bug 90410

From # mount: "/dev/hda4 on /media/hda4 type vfat (rw,utf8,umask=007,gid=46)" It is a primary partition, about 100GB in size.

It seems that Ext3 (where Thunderbird is installed) supports colons in filenames, while FAT32 does not. That's the root of the problem.

I'd hypothesis this:

1. The filename sanity check that exists in Windows Thunderbird (automatically replacing illegal characters in the suggested filename) doesn't correct enough bad characters under Linux. That leads the application to suggest a filename that will never work.

2. So, the user manages to fall through a hole that the original programmer presumably thought they had adequately protected against. The error message clearly isn't designed to catch this particular error - it refers to an attachment, when I'm trying to save the text of an email.

3. Then, when presented with a .txt extension, something goes badly wrong with the error handling and Thunderbird crashes to desktop. The crash seems to be specific to the .txt extension: .eml, .html, or no extension, all fail without a crash.